Search results

Ah... Interesting! Thanks for looking into it.

Yes, that's correct. When the flashing stops is when the USB crash happens. The script is still running, but the serial port is no longer accessible.

I worked through a large set of possible options, but unfortunately haven't found a perfect solution with the USB. But thought I'd put here some findings. The leds.show() does indeed take 9ms in practice - and this is what is causing the USB crashes. If I comment it out the crashes stop, or if...

At the moment, I'm only transmitting data at around 20fps, meaning each frame has 50ms, so should be well within the display time if the update is 9ms for show(), however it still crashes every 20 mins or so. In terms of the 9msec limit - I've also had it working at 100 fps with no problems so...

Was wondering if anyone had any thoughts on the above? I've managed to improve the situation a bit in terms of only calling led.show() after a third of the LEDs have been updated, but it still hangs roughly every hour. I can also provide a Python demo script if the C++ one above isn't easily...

I've attached the C++ code which just sends fixed patterns. It's quite intense as it doesn't attempt to limit the data rate (the actual data rate is much lower in practice), but it quickly demonstrates the USB serial lockup I've been having. Thanks for the help!

Thanks for the suggestion. I gave it a go and implemented as you suggested, without a buffer or loop but unfortunately it still seems to have the same problem! Yes it's a good point about loosing sync. I did wonder about that and that's why I put the check than N is an acceptable number...

In terms of the Teensy, I know the loop is still running as I when I implement a 1 second blink in the loop, the LED carries on blinking, even after the USB dies. I also know that no data is being received as the USB serial port on the Raspberry Pi side basically closes itself and refuses to...

Thanks for the tip Mark! Yes, good idea - I wrote a very basic test in C++ instead or Python to test, and had the same problem unfortunately on both Raspberry Pi and x64 platforms when I tested it. The problem seems to be caused by the leds.show(), when this is commented out there's no problem...

I'm working on a project with OctoWS2811 and a Teensy 4.1. I have a LED matrix running using 32 separate pins as outputs, each with a strip length of 300 LEDs. I'm sending packets of data over USB to the Teensy from a Python script on a Raspberry Pi in the following format: {led number low byte...

I've got a project coming up where I need to control a large number (2000) of WS2812 LEDs, and a smaller number (few hundred) WS2811s. What would be the best approach to this on the Teensy 4.1 - can I use multiple instances of OctoWS2812, or will that not work, and theres a better approach...

I'm trying to find out how to work with the Teensy 2 on a lower power project. Ideally I'd like to put it into a deep sleep/hibernation for about an hour, at which point it will wake up. I've noticed the Snooze library, but this is not compatible with the Teensy 2, and also seems like any of...

I'd also love to have access to a gate effect - I've tried to merge in the changes macaba made above into the latest release, but have been unable to get the effect to work. I've noticed there's a few people above asking for a pull request for this - wondering if it would be possible to add...