For clarity ("because I'm a bit thick"),

Archive FastLED Archive
,
1

For clarity (“because I’m a bit thick”), if I’m using 16-way parallel output on the Teensy 3.1 as per the demo example (https://github.com/FastLED/FastLED/blob/FastLED3.1/examples/Multiple/ParallelOutputDemo/ParallelOutputDemo.ino), are the strips ordered as stated in the comment?

i.e., the first NUM_LEDS_PER_STRIP in your LEDs array are connected to pin 2, the next NUM_LEDS_PER_STRIP are on pin 14, the next on pin 7 (and so on, through “WS2811_PORTDC: 2,14,7,8,6,20,21,5,15,22,23,9,10,13,11,12”)?

I assume the reason for this has something to do with the Teensy’s hardware, but it will certainly make the wiring a bit odd.

2

Yes, it’s because of the position of the bits for each pin in their relative ports, and no there is nothing I can do about the orderings (I’m already pushing clock limits as it is)

3

Notably, indexing from 0, only pin 13 lines up correctly with the 13th segment :slight_smile:

4

Given that I need to hook these up to a couple of 74HCT245s, I’m not even sure what makes most sense as a physical arrangement.

5

What are your concerns? Are you making a custom PCB? If you run the outputs from the 74HCT245s to some sort of terminal block and then on to the backs of your plugs (that go out to the light sticks) you could easily reorder outputs if needed.

6

Not a custom PCB as such, but building it myself on “3 hole” perfboard. I’d like to have one 74HCT45 on either side of the Teensy, but at least one signal wire is going to have to “wrap around” to the other side.

7

I see. Yes, you’ll have to do some routing with some short wire bits. It’s all going to be sealed in a black box though so don’t try to make it too pretty (or more complicated then needed) :wink: