C/C++ with some QT
Beiträge von penfold42
-
-
It’s like riding a bike isn’t it ?
Do it for Hyperion.ng - classic Hyperion is not the future.
Led drivers are here:
https://github.com/hyperion-pr…e/master/libsrc/leddeviceRecent pull request that highlights all the files that need editing:
https://github.com/hyperion-project/hyperion.ng/pull/487 -
What are your coding skills like ?
I don’t have a bulb or the time to do it myself, but happy to provide pointers to what’s needed
-
The protocol looks well documented so it doesn’t look too difficult.
-
Just read the GitHub thread - it looked pretty horrible without that patch.
It’s not quite the issue I described but if something has the device open, the spi clock really needs to be stable and correct. Especially for ws2801 which have no spi chip select pin
-
Sorry I missed this but io now.
There are 4 different common spi modes with differences in how the clock line works.
Namely 1) is a clock pulse and low->high or high->low
2) does the clock idle high or low when finished.My guess is the allwinner spi driver is broken and not settingnofnthe SoC SPI controller correctly
-
Thanks for your help, a question i want to use a nodemcu over wifi i read about hyperion second instance, i have Ws2812b leds strip , wich the correct or Last code for nodemcu ?
With espixelstick ? Any code - the 2812 has been supported forever
-
Yep - nodemcu is fine.
Esp8266 is the micro controller used on a variety of boards.Nodemcu, esp-01, esp-12, Wemos d1 are just some of the boards out there.
GPIO 2 is the pin used for the leds.
When it’s working, you point a browser at it to configure the number of leds and the led type. Use ws2811 (it’s the same as 2813 but with a shorter reset pulse which was altered to cater for the 2813)
-
Yep - systems - at one point I had 3 with espixelstick and 2 with spi on a Pi.
All with ws2812 rather than 2813 but it should work based on:
https://github.com/forkineye/ESPixelStick/issues/29 -
Don’t bother writing your own - I started and then gave up - it worked, but this was better:
https://github.com/forkineye/ESPixelStick
I added sacn e131 support to hyperion to support espixelstick
-
CMOS chips have a very very high input imprudence.
Unnconnected (or “floating”) inputs act like a series of tiny antennas and cause the chip to oscillate at many MHz. -
You should consider a level shifter between the nodemcu and “DI”.
The nodemcu is a 3v3 logic level but the leds specs claim it needs 0.7 * 5v = 3.5v
I prefer 74HCT series chips rather than those cheap mosfet based shifters on eBay
-
You could implement a series of preset lighting scenes as python effects.
You can then launch these effects from the app
-
Nope - the explicit clone is only in Hyperion.ng
In classic 2 (ore more) leds can have the same hscan and vscan I don’t think there’s a performance benefit
-
Try changing the dma channel to 10.
You’ll need to edit the config file manually if Hypercon doesn’t offer that option
-
And here’s the commit that added it:
https://github.com/hyperion-project/hyperion.ng/pull/157 -
I just checked the source - hyperion.ng can “clone” an led by index number.
So you can:
- define led 0 with its hscan and vscan
- define led 1 as “clone 0”
- define led 2 as “clone 0”
- define led 3 with its hscan and vscan
- define led 4 as “clone 3”
- define led 5 as “clone 3” -
How long is “long” ?
I’ve had a 16x16 led matrix running with no issues scraping the screen.
I’ve also had 750 leds driven by the python effect engine (but I can’t remember if I every tried screen grabbing with it )
-
-
1) is done already in Hyperion.ng
2) Hyperion.ng has a webbcofigninterface that will probably make a native app for configuration not worth it