You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey awawa, very thankful for the work you've put in to this project and really happy with the output so far (HyperSPI >>> signaling LEDs via rpi)!!
I have a few thoughts to share after finally getting a working solution for myself:
The pinout/connection diagram for the ESP to rpi was a bit confusing. The diagram shows that the MISO pin needs to be connected, but the default pinout in the readme doesn't list MISO as a necessary connection. Is there a purpose for MISO in this build, or should that get removed from the diagram (or noted as such)?
Also on the connection between ESP and rpi, it would be helpful if the default pinout table also included the corresponding GPIO pins on rpi. I had to have a printout of both the readme and the rpi GIO pinout to make sure i wasn't crossing streams as i was connecting it up. It's not impossible and I still got it right, but this would help streamline the physical connection process.
It's not immediately clear that compiling the firmware is an optional step that's only necessary if you need to change some of the LED driver configuration settings.
I don't know if others had this (dumb) issue, but i had to go into raspi-config to turn SPI on. I was banging my head against a wall for days because my LEDs were dark once i hooked up my ESP32, and only after i dug and dug did i realize i didn't have a spidev in /dev/, which led me to discovering that SPI is disabled by default (at least on the latest raspbian lite release) and i needed to enable it. Might be worth including at least verifying SPI is enabled in raspi-config.
I had to do a good bit of my own digging to troubleshoot the UART chip on my ESP board when i first connected it to my windows host. UART chip dependent on the ESP board, others may find it useful to have a note to ensure proper drivers (and possibly point them to the MFR's driver download page)
what do people do about power management, like when the TV is turned off? I'm using a separate PSU for the rpi, capture device, and LEDs so i was thinking of simply putting a smart plug on the LED PSU so i can control easily via smart assistant (google/alexa). Curious if others have any other creative solutions here, or if i'm overlooking some software capability that's already built in.
Again, I really appreciate all the hard work and time you've put in to this! Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey awawa, very thankful for the work you've put in to this project and really happy with the output so far (HyperSPI >>> signaling LEDs via rpi)!!
I have a few thoughts to share after finally getting a working solution for myself:
Again, I really appreciate all the hard work and time you've put in to this! Thank you!
Beta Was this translation helpful? Give feedback.
All reactions