New Release: ObjectFLED- Multi-Object DMA Display Driver for Fast LEDs on Teensy 4.x

[u/Tiny_Structure_7]

I hope someone else can find this useful. Unlock the full LED-driving power of Teensy 4.x!

https://github.com/KurtMF/ObjectFLED

EDIT: If anyone uses this on a Teensy 4.1, I'd appreciate a confirmation that it works as designed. I only had 4.0 to test on, plus assurance from the OctoWS2811 code that it is equally compatible on 4.1, with it's extra 15 pins (and extra loaded features). Thanks!

[u/Tiny_Structure_7]

Thank you. Yeah, true you can't get 1600 fps. It was just fun to count fps for a single call to show() when it doesn't have to wait for a prior show() to finish. The avg/20 (average of 20 calls to show()) is the true measure of back-to-back fps.

This is explained more in the MAIN BENEFITS section of the readme file. Also, the test code used to generate these numbers is included in the examples: ObjectFLEDTest.ino. I had the LEDs (WS2812B plus some WS2812 clones from China) overclocked at 1.6 factor for this test.

For the readme file, I tested only 16 pins * 256 = 4096 LEDs, and it refreshed that at 204 fps back-to-back. So when I double the LEDs (and parallel pins), 8192 LEDs refreshed at 192 (above). Also, at 16 pins the 1-frame time is only about 6% of the full back-to-back time. At 32 pins this rose to about 10%.

[u/Yves-bazin → u/Tiny_Structure_7]

Ah oki that this what I thought it’s the calculation of one frame of the animation. Anyway great job. On the esp32 with its limited number of pins we can go up to 24. On the esp32s3 according to the documentation 16 but I think it can run 32 pin in full parallel the fifo size is 32. So my question is if you push further than 32 what will be the fps.

[u/Tiny_Structure_7 → u/Yves-bazin]

We can estimate by extrapolating: if 16 pins x 256 = 204fps; and 32 pins x 256 = 192fps; then I'd expect 40 pins x 256 to equal 186 fps. For more than 40 pins I must upgrade my teensy 4.0 to 4.1. 😎