-
|
My toddler son likes to throw his toys behind the TV stand. So yesterday I was cleaning them up and yanked my HyperHDR setup off the TV. (the RPI and and ESP8266 got disconnected). I didnt think it was a big issue as I have had to tinker with the cabling every once and a while. So I begin reconnecting everything and now I cant get the LEDs to work at all and I think somehow I blew out a ESP8266 board. My issue: At some point I thought the ESP might have got wiped in my troubleshooting, so I thought I should reflash it. I connected it to my PC and couldn't flash it. I've tried resetting it by holding the RST button but nothing seems to work. So I figured it got killed somehow. I flashed another ESP board and connected it into the rest of the setup. Now the best I can get is the first 3, maybe 4, LEDS to light up. I've double checked the power connection, even re-soldered the wires connecting into the barrel connector to make the connection was solid. Checked the connection from the RPI to the ESP like a thousand times. Power cycled everything multiple times, So any help would be greatly appreciated. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 31 replies
-
|
LEDs are usually very hard to kill since they are on 5V (even data line). Esp8266 or Rpi GPIO are a lot easier to fried operating 5V power supply nearby since they are 3.3V. For the old Esp8266 you may give a try to put GPIO0 to the ground to force it into the bootloader after the reset. But since it stopped to work is not a good sign. If you checked everything the is still one possibility that you have a short-circuit on the LED input. I never trust them,remove them and make my own instead. Here where 6 cables are attached to the beginning of the LED strip. Maybe +5V is touching inside one of the data line? |
Beta Was this translation helpful? Give feedback.
-
|
How is the ESP powered? Are you using a USB connection with the Rpi? Then you should use the serial port it provides (at some /dev/tty* port), not the SPI device path. Since your previous board is dead there is a risk that the Rpi GPIO is also damaged and you need these stats to prove otherwise. |
Beta Was this translation helpful? Give feedback.
-
|
The ESP is powered by a USB cable plugged into a power strip. |
Beta Was this translation helpful? Give feedback.
-
|
To run diagnostic you need disconnect it from power strip temporarily (SPI cables stay in place) and connect ESP to Rpi using full USB data cable. LED power supply should be turned off. |
Beta Was this translation helpful? Give feedback.
-
|
I got this garbled text a couple times: and now every time I try to run it it just says: And just to be clear, I connected the ESP directly to the RPI with a good USB cable and the LEDS were not plugged with their power. I toggled the ESP device on and off in HyperHDR and ran the screen command after toggling. |
Beta Was this translation helpful? Give feedback.
-
|
Are you sure you have selected proper com port for |
Beta Was this translation helpful? Give feedback.
-
|
Yea I think its the right port. From |
Beta Was this translation helpful? Give feedback.
-
|
Then such result means this ESP doesn't run valid HyperSPI firmware or it's also damaged. At least I have no other explanation if screen is configured properly including ttyUSB0 port and 115200 speed. |
Beta Was this translation helpful? Give feedback.
-
|
I have forgotten which repo I should be using. I'm getting confused. Should I be using HyperSPI or HyperSerialEsp8266? |
Beta Was this translation helpful? Give feedback.
-
|
You used HyperSPI before and you have SPI cabled between esp and Rpi, dont you? HyperSPI also has a serial port exposed but only for diagnostic statistics (which you are trying to acquire) and uses SPI for data communication. HyperSerialEsp8266 is using serial port for both. |
Beta Was this translation helpful? Give feedback.
-
|
If you have a PC with Windows, flash ESP using v6 version (it has more debug messages than v9) https://github.com/awawa-dev/HyperSPI/releases/tag/v6.0.0.0 , with ESP still connected to the PC without SPI cables attached, use Putty to connect to its serial port on Windows using 115200 speed, you should see some output then. |
Beta Was this translation helpful? Give feedback.
-
|
Logs from V6 |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that's good. Connect it to Rpi now (only USB, no SPI) and test if the |
Beta Was this translation helpful? Give feedback.
-
|
Okay I'm getting the same result with the RPI USB -> ESP. I had to change USB ports on the RPI to get a result. After connecting the SPI cables and turning on the LED device and turning on an effect: In the HyperHDR GUI: |
Beta Was this translation helpful? Give feedback.
-
|
Test the performance using this procedure (color as effect and continues output enabled) |
Beta Was this translation helpful? Give feedback.
-
|
do you have a ground cable connection Rpi pinout ground to the Esp pinout ground? |
Beta Was this translation helpful? Give feedback.
-
|
Okay I reduced SPI speed to 10 000 000 in HypderHDR and connected a ground cable from the RPI to the ESP. I previously just had the SPI cables connected. Looking better |
Beta Was this translation helpful? Give feedback.
-
|
For 99% is was a missing ground, not the speed |
Beta Was this translation helpful? Give feedback.
-
|
So now you can back to testing the LED strip. If wont work I suggest replacing 4 or 5 first LEDs unless you have a better idea. |
Beta Was this translation helpful? Give feedback.
-
|
With the USB cable directly connected from the RPI to the ESP, I connected the data cable to the LEDs and powered on the LED strips. THEY ARE STILL WORKING! 100% it was a ground issue. Now I just need to figure out how to get the USB grabber plugged into the RPi because the grabber is kinda bulky. Thank you so much for all your help in debugging this issue! |
Beta Was this translation helpful? Give feedback.
-
|
When you finish restart the Rpi, take HyperHDR full log and post it here. There is a lot of dropped frames from HyperHDR side. |
Beta Was this translation helpful? Give feedback.
-
Logs after restart023-02-11T22:11:12.064Z [MAIN] Database path: '/.hyperhdr/db/hyperhdr.db', readonlyMode = disabled |
Beta Was this translation helpful? Give feedback.
-
|
As a final wrap up for anyone else who stumbles upon this thread. My ESP was experiencing a grounding issue causing it a failure to properly drive the LEDs. I previously was powering my ESP with a simple Apple USB charger connected to a power strip. Something happened and it was not sufficiently getting a solid ground connection. What resolved my issue with powering the ESP directly from the RPi with a USB cable. In addition with the USB cable there are ground connections from the RPi GPIO to the ESP and another GND from the ESP to the LEDs strip. |
Beta Was this translation helpful? Give feedback.
As a final wrap up for anyone else who stumbles upon this thread.
My ESP was experiencing a grounding issue causing it a failure to properly drive the LEDs.
I previously was powering my ESP with a simple Apple USB charger connected to a power strip. Something happened and it was not sufficiently getting a solid ground connection.
What resolved my issue with powering the ESP directly from the RPi with a USB cable.
In addition with the USB cable there are ground connections from the RPi GPIO to the ESP and another GND from the ESP to the LEDs strip.