12v pixel for holiday lighting and permiter lighting

[Wiredace]

Hi everyone,

Im very new to the pixel and coding world. Im an electrician but still trying to wrap my head around fpp and xlights.
I've started installing 12v pixels, ar 2" spacing under all my soffit.

I want to be able to do sequences but also maybe just have certain pixels light up for normal lighting.
Ia this possible with xlights or similar software?

I knew govvee and similar lights can slecet which lights tou want on and I'm hoping I can do something similar. In the end, I'd like to be comfortable enough to sell this to customers.

I currently have 12v pixels and wb1616 from wally lights.

Thanks for any help

[MikeKrebs]

Investigate the WLED  addin to FPP or the Display testing menu under status/control. You can create models that include every second, third, fourth, etc pixel and then turn those on in the test menu.

[algerdes]

Getting your head around any of this hobby can be daunting, no matter what your experience.
Take for instance, many of us up here are/were computer guys (of varying levels) before we found this stuff.

Most sequencers treat your display like either a single large matrix, or several matrix layouts per prop.  When you add a prop to your show, take a moment and look at the wiring diagram for that prop.  Then take a look at the node layout.  The wiring diagram shows you where the wires are supposed to go.  The node layout shows you which pixels are in what row and column in memory.  It is this that is used to send data to the pixels.  Usually treating each position for 3 LEDs (RGB). So, if you want the top pixel of a column on a megatree to turn on white, the sequencer looks at the node layout, finds the first row (for that prop) and then sends three commands.  255-255-255 is full on white. (Colors are just different blends of the three.)

Once you have the props doing what you want them to do, then you send the completed sequence to your "show player".  For a lot of us, that is a FPP (in one or another configuration.)  The sequence is usually in a format that we call .fseq.  (There are others, but I'll keep this simple down to this one.) .fseq is simply what the sequencer feels should be sent.  The sequencer does the compiling ("Rendering").  It then puts each sequence into order and stores it (the .fseq, again).

The show player quite simply takes the recorded sequence (.fseq) and sends it down the line to a device we know as a controller.  The controller then uses the information that it received from the setup to break apart the codes sent to it and send them out to the proper line (connection) that holds that particular pixel.  As a long time DIYC person told me, there is no magic to this.  It is in the planning.

Thankfully, unlike the early days, we no longer have to keep track of what pixel for what prop is on what connection.  Our sequencers can do this for us.  (Heck, even I threw away my spreadsheets-not that long ago- but I have.   )

As a sparky (I believe you said you are one) you have an advantage in that you already know about "separate signals".

Do some searching on the Internet and you will find a wealth of knowledge.  You decide how deep you want to go.