Closed dzervas closed 3 years ago
cp2004
commented
3 years ago Hi, WS2813 strips are not supported by this plugin or the underlying library explicitly. You've selected WS2812, presumably because WS2813 is not in the list, the only way it may work is if any of the other options (WS2811, SK6182) are compatible.
You can see the list of supported/recommended hardware here: https://cp2004.gitbook.io/ws281x-led-status/guides/setup-guide-1/supported-hardware#led-strips
dzervas
commented
3 years ago Oh forgot to mention that the underlying library seems to work with WS2813: https://github.com/jgarff/rpi_ws281x/issues/152
dzervas
commented
3 years ago I connected to the wrong side of the strip -.- I now have flickering leds but that's probably due to doing nothing about the voltage difference (I'm currently testing so I haven't hooked either a diode or a level shifter)
cp2004
commented
3 years ago Flickering can be a whole number of issues, commonly grounding, but also OS configuration and just generally dodgy wiring. Incorrect voltage tends to cause dropouts where the strip stops updating, or maybe some colours don't update quite right.
Anyway, at least you got the WS2813 strip working right. I may add that to the documentation page of hardware that it works defined as a WS2812. Are there any other settings you had to tweak?
dzervas
commented
3 years ago you're right! I tested by quickly soldering 2 jumper cables on the other side of the 2m strip and that was causing the flicker (I found that out just after I made a circuit with a transistor for the level shifting). When I properly soldered the 4 cables on the right side (where BI and DI are), the whole strip worked without any level shifting.
takeaway for you to add in the docs: WS2813 works, just select WS2812 and everything else default. 800khz, DI to GPIO10 with SPI, etc. The only difference is in the wiring where BI pin should be grounded. Add a warning that wiring DO to GPIO10 will not work! Needs to be DI.
out of topic but do you know a plugin where I can just change the led strip effects? the whole setup is for a sand table, so there's no actual printing taking place, thus most features of this plugin do not apply to me, only the torch
awesome plugin, I'll definitely add a strip to my prusa and use this plugin like it's meant to!
cp2004
commented
3 years ago out of topic but do you know a plugin where I can just change the led strip effects? the whole setup is for a sand table, so there's no actual printing taking place, thus most features of this plugin do not apply to me, only the torch
I don't, to my knowledge this is the most advanced LED strip control plugin available for OctoPrint. In future, I have plans to go for custom effect triggers, so you can trigger it through gcode, events, anything else that I can think of that would be a trigger. Not coming soon though, 0.7.0 is right around the corner and there's still loads for me to do around OctoPrint. Sand table installation sounds interesting!
takeaway for you to add in the docs: WS2813 works, just select WS2812 and everything else default. 800khz, DI to GPIO10 with SPI, etc. The only difference is in the wiring where BI pin should be grounded. Add a warning that wiring DO to GPIO10 will not work! Needs to be DI.
Thank you! I have updated the supported hardware section for the 0.7.x branch.
Description of the bug
I just got a 2 meter (60 leds/m) WS2813 LED strip and it doesn't seem to do anything. I use a Pi 0w (it's not for a 3D printer but for a kind of 2D plotter so even Pi 0 is more than enough) and connected DO to GPIO10 and BO to GND.
Steps to reproduce Tried torch, test red/green/blue/white, nothing.
What did you expect to happen
Logs and screenshots
.octoprint/logs/plugin_ws281x_led_status_debug.log.octoprint/logs/octoprint.logVersion of plugin and OctoPrint
OctoPrint (using OctoPi): 1.5.3 plugin: 0.6.0