awawa-dev / hyperserialesp32 Goto Github PK

Hi,

I have a strange issue which I cannot pinpoint. Maybe you can point me to the right direction.
My Setup:
LG OLED55C7D with HyperHDR and Piccap running.
157 LEDs with external powersupply which also drives the esp32 (running WLED).

This setups works fine.

So I tried to replace it with the HyperSerial solution and HyperHDR successfully detects the esp(32 and8266 I tried both) but somehow the LEDs flash/flicker white inbetween changing color. I tried different Baudrates/Cables/ESPs but somehow the Issue persists.

But WLED works fine. I did not try HyperSerialWLED since I wanted to ditch WLED.

I am kinda confused why this happens.

Discussed in #32

When screen is dimmed by UAC in windows, or when refresh rate or resolution changed, or when i alt+tab from exclusive fullscreen game, esp32 board turn leds off and won't turn on until i replug the board's usb and restart the program.

Hi,

I'm trying to get rid of wifi and migrate to HyperSerialESP32 from my old ESP32 with CP2102 which is flashed with WLED vanilla and drives SK9822 (GPIO 02 & 04) + power relay (GPIO12).

I got two board:

• ESP32 D1 Mini with CP2104 https://www.az-delivery.de/en/products/esp32-d1-mini
• ESP32S with CH340C https://www.az-delivery.de/en/products/nodemcu-esp-32s-kit

And this relay: https://www.az-delivery.de/en/products/relais-modul

I made a fork with a branch for each board:

• ESP32D1-4000000
• ESP32S-200000

Each one has platformio.ini edited with corresponding baud rate and "LED_POWER_PIN = 12".
Compiled from github and everything went fine. Flashing with HomeFlasher is ok. They're both recognized by HyperHDR. They both output 3.3V on 3.3V dedicated pin when plugged into USB.

Problem is there's no output current on GPIO 12. Also tried with relay set on GPIO 32 on platformio.ini and it's the same for both board.

My old board has WLED configured to "invert" on power relay pin, and outputs 3.3V from GPIO 12 when plugged on USB.
I bet it's the issue with HyperSerialESP32.

I can't change this behaviour as the relay is here to power off leds power supply when board is powered off from USB (actually plugged on my monitor)

Thanks for you work and for your help !

Hi, forgive the dumb question, I am completely new to ESP boards. Would the board below be compatible with HyperSerialESP32?
ESP32-S2 seems to have much better power efficiency, and the board's serial port advertises a maximum speed of 4.6Mbps.

https://www.kubii.fr/micro-controleurs/3651-carte-de-developpement-nodemcu-esp-12k-avec-wifi-3272496309937.html

I have been trying all night to properly edit the platformio file to make the firmware for my esp32-s2 mini. I'm attempting to run a multi segment setup with an sk6812 rgbw cold white led strip, lolin esp32-s2 mini, 74AHCT125 level shifter, Rpi 4, hyperserialesp32, and HyperHDR 19.0. I have windows 11 desktops to use to get all the programming done. I know that you are busy, but if you could please just hold my hand and walk me through this, I would appreciate it greatly!!!! The wiring isn't an issue, I've got that I'm fairly certain, and I'm pretty sure that I can get it taken care of after it's all loaded up. I had an old setup that was just the rpi4 and a ws2812b strip for a while, but chose to upgrade it due to instability. Thank you so much for your time!!

Jason

Hi,

Setup:
I have ESP32-S2 Lolin mini and apa107/hd107 LED strip, the power goes from a 5v external power supply to buffer SN74AHCT125N connected to a smart socket.

Issue:
Unfortunately, when I power off the power supply the s2 mini still ignites the blue standby led and some LEDs from the strip, I think the SN74AHCT125N passes some current to the strip.

My main question is, can I turn off s2 mini when I don't need it, using API or something? When I connect ESP to USB, the standby led and LEDs don't spark until I turn on the LED device under Remote Control on the dashboard

Hey there, many thanks for the software, once again.

Finally the level shifter arrived (SN74AHCT125N) and I got to time to connect everything.

I've done according to the instructions here https://github.com/awawa-dev/HyperHDR/wiki/How-to-build-a-new-LED-system-or-to-upgrade-it.-Needed-components.#e-33v-to-5v-level-shifter , I think the instructions are written quite nice and a go to for manz who are starting with HzperSerial's, but these instruction use GPIO16 and GPIO33. Now, I know it makes sense to also recheck the original thread for HyperSerialESP32 and I barely stumbled upon the Pinout mentioned there https://github.com/awawa-dev/HyperSerialESP32#pinout

Since the afformentioned instructions are great and detailed, I suggest to make a statement that highlights that this setup is primarily oriented towards Multisegment setup where a GPIO pin for driving led can be set when compiling and perhaps even mention the wiki on how to use actions to compile for this particular GPIO pins.

With that said, can I set a GPIO pin in the firmware_esp32_s2_mini_WS281x_RGB.bin or firmware_esp32_s2_mini_WS281x_RGB.factory.bin, or should I proceed with re/soldering the wire towards the level shifter?

EDIT1: I have searched and found the answer to changing pinout https://github.com/awawa-dev/HyperSerialESP32/wiki#how-to-compile-project-using-github-action-and-change-the-speed-or-pinout-for-your-board

many thanks and have a great and healthy year 🙏

Hi

I have been unable to get HyperHDR to recognise my S2-Mini.

On the logs I get the line

2023-06-19T16:31:50.026Z [LEDDEVICE_ADALIGHT] Device disabled, device 'adalight' signals error: 'Permission denied'

I have serial connections on both /dev/ttyS0 and /dev/ttyS1 and neither work
The user running HyperHDR is part of both the tty and dialout groups

I have tried flashing the S2-mini with the baudrate set to 5000000 and 2000000 and neither work

My platformio.ini configuration is here: (https://raw.githubusercontent.com/mattsmithuk/HyperSerialESP32/master/platformio.ini) - compiled using the GitHub Action

My HyperHDR log is here: (https://pastebin.com/hzVuzSVD)

Any thoughts?

Hello! Thanks for a great project! :)
I'm trying to make it work on my rooted lg tv using esp32 dev kit with CH9102F usb2uart chip, which is supported natively by tv os.
But it doesn't work some how. In hyperhdr logs I can see that it successfully opens uart interface and manages to complite handshake, but after that nothing happens, no colour changes on led strip. I'm using latest v19.0.0.0beta2 hypehdr and v8.0.0.0 hyperserial driver.
I've verified that this board and hyperhr works using my laptop running mac os, everything works as expected but when board is hocked to tv it doesn't work. I've checked serial and clock pins using my scope, and there's not signals there

webosbrew/hyperhdr-webos-loader#9

2022-12-20T17:48:54.182Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM1
2022-12-20T17:48:54.182Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:174) _rs232Port.open(QIODevice::ReadWrite): ttyACM1, Baud rate [2000000]bps
2022-12-20T17:48:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:179) portName:          ttyACM1
2022-12-20T17:48:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:180) systemLocation:    /dev/ttyACM1
2022-12-20T17:48:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:181) description:       USB Single Serial
2022-12-20T17:48:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:182) manufacturer:      1a86
2022-12-20T17:48:54.205Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:183) productIdentifier: 0x55d4
2022-12-20T17:48:54.206Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:184) vendorIdentifier:  0x1a86
2022-12-20T17:48:54.206Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:185) serialNumber:      5539028341
2022-12-20T17:48:54.520Z [LEDDEVICE_ADALIGHT] DETECTED DEVICE USING HYPERSERIALESP8266/HYPERSERIALESP32 FIRMWARE (Welcome! Awa driver 8. SPI APA102 compatible type (BGR).) at 47 msec
2022-12-20T17:48:54.520Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:329) Switch on
2022-12-20T17:48:54.521Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:405) Power On
2022-12-20T17:48:54.521Z [COMPONENTREG0] LED device: enabled
2022-12-20T17:48:57.798Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.4.23
2022-12-20T17:49:20.949Z [WEBSOCKET] (JsonAPI.cpp:1259) log streaming deactivated for client  ::ffff:192.168.4.23
2022-12-20T17:49:20.950Z [WEBSOCKET] (JsonAPI.cpp:1250) log streaming activated for client ::ffff:192.168.4.23

root@LGwebOSTV:/tmp/var/log# uname -a
Linux LGwebOSTV 5.4.96-266.mlt4tv.1 #1 SMP PREEMPT Tue Nov 8 12:52:11 UTC 2022 aarch64 GNU/Linux

System info

None
- Database:        read/write

HyperHDR Server OS: 
- Distribution:   webOS TV 7.2.0
- Architecture:   arm64
- Kernel:         linux (5.4.96-266.mlt4tv.1 (WS: 32))
- Qt Version:     5.15.8

I'm excited to try out the mutli-segment feature, as I'm just about to replace my existing led strip with a 144/m strip in the next week. I'm able to run a full 144 lights, so I know it's communicating with HyperHDR but I don't know how to check if it's using multi-segment.

I've flashed my device with the latest build, but what I'm not sure of is if we need to wire in an additional GPIO for the second segment data?

The only note in the read me is this:

Multi-segments can double your large sk6812/ws2812b setup refresh rate for free. All you need is to properly project & construct the LED strip and use HyperSerialESP32 v8.

But you haven't noted what "properly" means here, nor if there's any other configuration needed.

Thanks for any additional notes or documentation!

I had an issue with the pre compiled bin file. (specifically this one: https://github.com/awawa-dev/HyperSerialESP32/releases/download/v8.0.0.0/firmware_esp32_SK6812_RGBW_COLD.bin)

When compiling it myself it worked fine, I did change the platform version to the latest 5.3.0 (https://github.com/awawa-dev/HyperSerialESP32/blob/master/platformio.ini#L32) so far it has been absolutely incredible! Is there a reason you build it using version 3.5.0 or is it a typo?

Heya,

Apologies if this is the incorrect place to send over this query. I've just swapped out my ESP-WROOM-32E for an ESP-WROOM-32 assuming I could get the baud rate of '2000000'. On the first boot up funnily enough the logs mentioned the whole 'DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32 FIRMWARE', but after an additional reboot (and any subsequent) its now not (logs below). The led's still work fine and other than the expected error message it all works. I just wondered why it would of said it the first time round but then decide its not happy with it afterwards?

Below is the current logs after the latest reboot. Unsure if I need to purchase another ESP32 or not.

Kind regards in advanced for all your help.

I also performed a video benchmark with following results:

Perfect minimal latency (related to FPS):: 16.67ms
Average measured latency:: 58.89ms

Internal latency: 13.44ms

Logs starting:

2023-01-18T20:22:28.140Z [LEDDEVICE_ADALIGHT] Received: '�
Welcome!
Awa driver 8.
NeoPixelBus SK6812 cold GRBW.

RGBW => Gain: 255/255, red: 160 , green: 160 , blue: 160' (117)
2023-01-18T20:22:28.141Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:106) Close UART: ttyACM0
2023-01-18T20:22:28.228Z [EFFECTENGINE0] (EffectEngine.cpp:174) Start the effect: name [Rainbow swirl fast], smoothCfg [2]
2023-01-18T20:22:28.228Z [MUXER0] Register new input 'System/EFFECT' with priority 0 as inactive
2023-01-18T20:22:28.228Z [HYPERHDR] Initial foreground effect 'Rainbow swirl fast' started
2023-01-18T20:22:28.228Z [SMOOTHING0] Using alternative smoothing input (0)
2023-01-18T20:22:28.229Z [COMPONENTREG0] LED device: disabled
2023-01-18T20:22:28.283Z [MUXER0] Set visible priority to 0
2023-01-18T20:22:28.283Z [HYPERHDR0] New priority[0], previous [255]
2023-01-18T20:22:28.283Z [HYPERHDR0] New source available -> switch LED-Device on
2023-01-18T20:22:28.283Z [SMOOTHING0] Clearing queued colors before: enabling
2023-01-18T20:22:28.283Z [SMOOTHING0] Smoothing queue is cleared
2023-01-18T20:22:28.284Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:102) Enable device
2023-01-18T20:22:28.284Z [LEDDEVICE_ADALIGHT] Opening UART: ttyACM0
2023-01-18T20:22:28.284Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:183) _rs232Port.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:188) portName: ttyACM0
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:189) systemLocation: /dev/ttyACM0
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:190) description: USB Single Serial
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:191) manufacturer: 1a86
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:192) productIdentifier: 0x55d4
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:193) vendorIdentifier: 0x1a86
2023-01-18T20:22:28.323Z [LEDDEVICE_ADALIGHT] (ProviderRs232.cpp:194) serialNumber: 537E053428
2023-01-18T20:22:28.344Z [EFFECT0(Rainbo...)] Begin playing the effect with priority: 0
2023-01-18T20:22:28.580Z [LEDDEVICE_ADALIGHT] Could not detect HyperSerialEsp8266/HyperSerialESP32 device
2023-01-18T20:22:28.580Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:329) Switch on
2023-01-18T20:22:28.581Z [LEDDEVICE_ADALIGHT] (LedDevice.cpp:405) Power On
2023-01-18T20:22:28.581Z [MUXER0] Priority 0 is now active
2023-01-18T20:22:28.581Z [COMPONENTREG0] LED device: enabled
2023-01-18T20:22:28.582Z [SMOOTHING0] Clearing queued colors before: enabling. Smoothing configuration changed: restarting timer.
2023-01-18T20:22:28.582Z [SMOOTHING0] Smoothing queue is cleared
2023-01-18T20:22:28.582Z [SMOOTHING0] Selecting config (2) => type: Linear, dirMode: false, pause: false, settlingTime: 200ms, interval: 40ms (25Hz), antiFlickTres: 0, antiFlickStep: 0, antiFlickTime: 0
2023-01-18T20:22:28.582Z [SMOOTHING0] Using linear smoothing input (2)

Logs Finished

Not sure if this is the right place to ask this, but it appears that my LG C2 can't load the driver for the USB to serial converter on the ESP32.
After connecting, the device is detected, but not linked to any serial port (like /dev/ttyUSB0).

root@LGwebOSTV:~# dmesg | grep -i usb
[ 8370.608208] usb 3-1: USB disconnect, device number 6
[ 8373.111113] usb 3-1: new full-speed USB device number 7 using xhci-hcd
[ 8373.285690] usb 3-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[ 8373.285694] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 8373.285696] usb 3-1: Product: USB Serial

On my laptop it does appear to work:

[24818.042767] usb 2-7: new full-speed USB device number 21 using xhci_hcd
[24818.184695] usb 2-7: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.34
[24818.184706] usb 2-7: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[24818.184710] usb 2-7: Product: USB Serial
[24818.190786] usb 2-7: ch341-uart converter now attached to ttyUSB0

So the main difference is that last line, where it attaches it to ttyUSB0.
Afterwards I can read the serial port at 2Mbaud:

$ picocom /dev/ttyUSB0 -b 2000000
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 2000000
(...)

Type [C-a] [C-h] to see available commands
Terminal ready

Welcome!
Awa driver 9.
SPI APA102 compatible type (BGR).

I have a similar issue with an ESP8266.
The raspberry pi pico does seem to get attached on the LG C2 (but it shows as /dev/ttyACM0 instead of /dev/ttyUSB0, so maybe different driver?), but that platform is not supported :)

Is there some trick to getting the /dev/ttyUSB0 to appear? Do I need to modprobe some driver?