Sub-sub blade?

ProffieOS
1

I just came across this situation.
Looking to do data1 → blade PCB that has 2 rings (NPXL V3) → Main blade
Ideally, the PCB would get setup like

    SubBladeWithStride(0, 14, 2, WS281XBladePtr<16, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()),
    SubBladeWithStride(1, 15, 2, NULL)

but, we’d need to then continue on to the main blade that should NOT use subblade.
Is this how that’s done then? (main blade set to 144 pixels)

 { 0, SubBlade(16, 159,WS281XBladePtr<160, bladePin, Color8::GRB, PowerPINS<bladePowerPin2, bladePowerPin3> >()),
    SubBladeWithStride(1, 15, 2, NULL),
    SubBladeWithStride(0, 14, 2, NULL),
    CONFIGARRAY(presets) }
2

Yes?

I’m not sure what the question is here.

3

I guess the question was if it’s correct / ok to mix SubBlade with SubBladeWithStride in the same data path. Seems like yes.
Thanks.

4

That’s funny I just did the same thing, because the parts I had for a thin neck saber only had one data route to the emitter pcb. Amazing stuff!

1 Like
5

I did some digging into how subblades work not too long ago because I had this question (or one similar, rather).

Whenever you setup subblades, the factory functions all reference a global variable for “last subblade” (basically). So all subblade functions are interchangeable with another. That’s why some of the syntax (especially for some of the more complex subblade types) is there afaics, because that way it still works.

If you have a start of a subblade, from there you can put subblades in any order, mixing types, mixing positions, etc., and it will work.

It takes some care to make sure what you want to happen actually happens, but virtually anything is possible!

2 Likes