New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teensy3.1 unusual behavior beyond ~60 leds #545

Closed
VoswijkC opened this Issue Dec 29, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@VoswijkC

VoswijkC commented Dec 29, 2017

I loaded up a very simple rainbow test, but the strip behaved rather unusual and i have no possible explanation as to Why.
-The entire string and code works perfectly fine with a normal arduino so the strip,Code and power supply aren't faulty.
-A small 24led string connected to the Teensy work well aswell. So my level shifter seems to be working normal too.
-Also works pretty well if the program is set to assume the strip is pretty small.
-when it is asked to add more than ~65 leds it goes haywire with flickering and whatnot. This is regardless if i only ask it to use a small portion of the string or all of it. Which suggests a problem within the software

Apparantly once i ask the library to add more than a certain amount of leds (around 60) on the Teensy it stops working properly with the set amount of leds turning off and the rest showing random colours. Perhaps there is a bug in the Fastled code itself?

This is with fastled release 3.1.6, arduino IDE 1.8.5,Teensyduino 1.4 (and 1.4.1-beta1)

@VoswijkC VoswijkC changed the title from WS2813 Teensy3.1 unusual behavior beyond ~60 leds to Teensy3.1 unusual behavior beyond ~60 leds Dec 29, 2017

@focalintent

This comment has been minimized.

Show comment
Hide comment
@focalintent

focalintent Dec 29, 2017

Member

Try disabling interrupts and see if that helps. See https://github.com/FastLED/FastLED/wiki/Interrupt-problems - the ws2813 changed some of the timings around reset, and the code hasn’t been fully updated to account for that (and probably won’t be for a while, still).

Member

focalintent commented Dec 29, 2017

Try disabling interrupts and see if that helps. See https://github.com/FastLED/FastLED/wiki/Interrupt-problems - the ws2813 changed some of the timings around reset, and the code hasn’t been fully updated to account for that (and probably won’t be for a while, still).

@VoswijkC

This comment has been minimized.

Show comment
Hide comment
@VoswijkC

VoswijkC Dec 29, 2017

Ah. that seems to do the trick! Did not know fastled allowed interrupts to be handled between each led on ARM devices. if lucky this will not interfere with the teensy audio libraries.

Thank you very much for the assistance!

VoswijkC commented Dec 29, 2017

Ah. that seems to do the trick! Did not know fastled allowed interrupts to be handled between each led on ARM devices. if lucky this will not interfere with the teensy audio libraries.

Thank you very much for the assistance!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment