visualSound
Well-known member
Hi everyone!
I've been off this forum for a couple years and right now I'm just getting my self up to speed about the 3.6 and it's led driving capabilities - I've used the 3.2 heavily until the last couple years with the octo adapter board etc and had great results but hit a pretty consistent bottleneck of 3200 pixels per teensy3.2 (streaming pixel data via usb) and about 3-4 teensys per usb card/group
I just wanted to get clarification on some things I've been reading if possible!
1) I'm reading that the 3.6 has 32 dma channels - can we use more than 8 to drive ws2811/12b style strips in parallel now?
https://www.pjrc.com/teensy/techspecs.html
1a) If so, is this as simple(doubtful!) as declaring more dma friendly pins somewhere in the code?
1b) If not, what changes need to happen and where, generally speaking? Is it just a complicated feature to add?
I'm aware of fastLED and it's bit banging approach to surpass 8 but looking at dma based options only.
NOTE: I realize that the suggestion people usually have is if you can afford that many pixels just buy another teensy. True!
However I'm looking to understand the new limitations and I also see value in using many short strips vs fewer longer strips in quite a few situations.
2) Can the faster 480mb "Usb1" be used instead of the standard 12mb "Usb0" to stream say led data to the teensy faster?
Ultimately, my reason for asking - if we can push data to the teensy faster can we have more teensy 3.6's connected to a single multi-tt hub at similar frame rates?
3) What's the recommended model/type RJ45 breakout for maximum data streaming / throughput currently?
I've used the wiz820io before, and I'm hearing a bit about the wiz850io but what's the latest and greatest recommendation here?
Appreciate your time - thanks.
Lucas
I've been off this forum for a couple years and right now I'm just getting my self up to speed about the 3.6 and it's led driving capabilities - I've used the 3.2 heavily until the last couple years with the octo adapter board etc and had great results but hit a pretty consistent bottleneck of 3200 pixels per teensy3.2 (streaming pixel data via usb) and about 3-4 teensys per usb card/group
I just wanted to get clarification on some things I've been reading if possible!
1) I'm reading that the 3.6 has 32 dma channels - can we use more than 8 to drive ws2811/12b style strips in parallel now?
https://www.pjrc.com/teensy/techspecs.html
1a) If so, is this as simple(doubtful!) as declaring more dma friendly pins somewhere in the code?
1b) If not, what changes need to happen and where, generally speaking? Is it just a complicated feature to add?
I'm aware of fastLED and it's bit banging approach to surpass 8 but looking at dma based options only.
NOTE: I realize that the suggestion people usually have is if you can afford that many pixels just buy another teensy. True!
However I'm looking to understand the new limitations and I also see value in using many short strips vs fewer longer strips in quite a few situations.
2) Can the faster 480mb "Usb1" be used instead of the standard 12mb "Usb0" to stream say led data to the teensy faster?
Ultimately, my reason for asking - if we can push data to the teensy faster can we have more teensy 3.6's connected to a single multi-tt hub at similar frame rates?
3) What's the recommended model/type RJ45 breakout for maximum data streaming / throughput currently?
I've used the wiz820io before, and I'm hearing a bit about the wiz850io but what's the latest and greatest recommendation here?
Appreciate your time - thanks.
Lucas