Hi Jon, have you tried a terminating resistor on the DO pin, maybe (unlikely) a reflection. As an aside we have been running hundreds of the LEDs on strips with no failures. David Mc.
I hadn't thought of that, but I don't think it'll be the problem. This happens just as often when the WS2813 then drives the input of a WS2811, so the output pin is connected (to a high-impedance input, at least)
@@SuperHouseTV Mmm, I saw the schematic after I posted. Another thought is to use filament dryer (3d printing), if you can get it hot enough, they will run for at least 12 hours.
@@macca1945 After the livestream there was a bit of brainstorming with a few people at the BBQ, and we talked about crazy things like making a dehydrator that wraps around the back of the feeder. Loading and unloading the reel from the feeder is annoying, but mounting / unmounting the feeder only takes a few seconds so the approach I'm going to take is turning an old chest freezer into a dehydrator box and store the entire feeder in it with the reel mounted. Then I can put it on the machine right before running a batch, and take it off immediately afterwards and put it back in the box. If it lives in a drybox whenever it's not actively feeding parts I think it will help a lot.
Hi Jon, not sure if this is of any help, but i had a strip of 12 leds set to amber in colour, that were turned on by PIR and arduino. The code would fade leds up then down after a minute. This worked perfectly for 6 years, Then i updated various libraries including the one for the WS2812B. After this I would occasionally get purple flashes sometime white on fade up or down. If i tried the same code on 16 segment circular led module, everything was perfect ! I didn't try to fault find as I assumed the library was at fault ? and something to do with tolerance ? Hope this helps 🙂
![เจ็บที่ยังฮัก - ม่อน วรวิทย์ [ Official Mv ] จอนนี่มิวสิค](http://i.ytimg.com/vi/KALIGSRSjFs/mqdefault.jpg)
Hi Jon, have you tried a terminating resistor on the DO pin, maybe (unlikely) a reflection. As an aside we have been running hundreds of the LEDs on strips with no failures.
David Mc.
I hadn't thought of that, but I don't think it'll be the problem. This happens just as often when the WS2813 then drives the input of a WS2811, so the output pin is connected (to a high-impedance input, at least)
@@SuperHouseTV Mmm, I saw the schematic after I posted. Another thought is to use filament dryer (3d printing), if you can get it hot enough, they will run for at least 12 hours.
@@macca1945 After the livestream there was a bit of brainstorming with a few people at the BBQ, and we talked about crazy things like making a dehydrator that wraps around the back of the feeder. Loading and unloading the reel from the feeder is annoying, but mounting / unmounting the feeder only takes a few seconds so the approach I'm going to take is turning an old chest freezer into a dehydrator box and store the entire feeder in it with the reel mounted. Then I can put it on the machine right before running a batch, and take it off immediately afterwards and put it back in the box. If it lives in a drybox whenever it's not actively feeding parts I think it will help a lot.
Hi Jon, not sure if this is of any help, but i had a strip of 12 leds set to amber in colour, that were turned on by PIR and arduino.
The code would fade leds up then down after a minute.
This worked perfectly for 6 years, Then i updated various libraries including the one for the WS2812B.
After this I would occasionally get purple flashes sometime white on fade up or down.
If i tried the same code on 16 segment circular led module, everything was perfect !
I didn't try to fault find as I assumed the library was at fault ? and something to do with tolerance ?
Hope this helps 🙂
I've been using the Adarfruit Neopixel library and assumed that it wouldn't be a software issue, but perhaps it is. Thanks for the idea 🙂