Could not detect HyperSerialEsp8266/HyperSerialESP32. No LED output. #61
Replies: 4 comments 20 replies
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
I appreciate the quick response. I compiled a new firmware at the 1Mb speed and set the baud rate in the LED hardware section of HyperHDR to 1Mb as well. I'm getting different results now and the logs are showing a detected device yet I still cannot get the LEDs to output anything whether it's via USB capture, screen capture or setting them to a color. Oddly enough, the UART on the ESP32 is labelled as 2104. Logs:
|
Beta Was this translation helpful? Give feedback.
-
There is a communication now so I dont know what could the problem be. When you tested HyperSerialWLED esp had exactly the same cabling including USB connection to the PC?
In the past, there was a plague of counterfeit ch340g chips in esp8266, maybe now they are trying to stuff cp2102 whose parameters lag behind competing systems. who knows? |
Beta Was this translation helpful? Give feedback.
-
|
It might be a little tricky but I'll attempt it. Thanks again for all the help! |
Beta Was this translation helpful? Give feedback.
-
|
BTW
I think it's better to use rp2040 and HyperSerialPico. They all use the USB-CDC virtual driver instead of physical UART, so they all support high speeds. |
Beta Was this translation helpful? Give feedback.
-
Thanks, I'll go this route instead. Does multi segment require a speed of 4000000? I just configured my multi segment LED strip, compiled and flashed a firmware at 1500000 (known working speed of the current ESP32 I have) and I can't seem to get the second half to output anything. The first segment is perfect. |
Beta Was this translation helpful? Give feedback.
-
The higher the better because we will never waste time waiting for data when the LED "rendering unit" is ready. For multisegment 2 x Neopixel speed (800Kb) + some protocol overhead => 2Mb is bare minimum, but some frames may be lost from time to time.
Did you configure HyperHDR exactly for 222 LEDs in your case? |
Beta Was this translation helpful? Give feedback.
-
|
Awesome! It was just a solder bridge I missed. All is good now. Super excited to install on the TV! Thanks for all your hard work on this project and for taking the time to help. |
Beta Was this translation helpful? Give feedback.
-
|
Strange but its change logs says: maybe its about newer CP2102N that is superior to older CP2102, but seems there was a problem with CP2104 also |
Beta Was this translation helpful? Give feedback.
-
|
Hi there i have a Similar Problem. Pleas see the following screenshots: And the following Log: I think my ESP (Wemos D1 mini) is an CP2104, atleast there is the number 2104 printed on in. Any Idea what i do wrong? Thank you in advance. |
Beta Was this translation helpful? Give feedback.
-
|
I think that might be the problem
when using it with Adalight driver in HyperHDR. I suspect you mixed-up projects ;-) this is HyperSerialESP32 project, not HyperSPI. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I've been trying to get HyperSerialESP32 set up for the past couple of days without luck and was hoping someone had some insight as to what could be going wrong.
The "device discovery" section on the overview page of HyperHDR sees ESP board COM4 Silicon Labs CP210x USB to UART Bridge but I am unable to get any output to the LEDs via screen capture or USB capture. Logs display "Could not detect HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico device."
My testing configuration is as follows:
LED controller set to adalight with Silicon Labs CP210x USB to UART Bridge (\.\COM4) as output
Esp8266/ESP32/Rp2040 handshake checked
Baudrate 2000000
HyperSerialWLED firmware is functional with the same hardware setup and data pin.
Thank you in advance.
Some logs:
Beta Was this translation helpful? Give feedback.
All reactions