If it's the Arduino approach that is taken, then I'll step aside (except for design reviews, if asked). It's largely Barnaby's baby, and to be honest, it doesn't really tickle my fancy (nothing wrong with it, though).
Before that, some thoughts:
1) I don't like adding AC circuitry to boards if at all possible. I like BarnabyBear's approach for a pix2ac function better.
2) Why the external counter? I think that the Atmega part is adequate as it is, even if one of the splitter outputs has to be given up when the pix2ac feature is enabled.
3) A large chunk of BarnabyBears' board is dedicated to handling DC power for the pixel strings. Is this a desired feature for here?
4) I wonder if an Arduino Beetle could be used in place of the Nano.
5) There needs to be a 5V regulator installed to handle the 12V pixel case.
6) Providing adequate high-drive for the pixel output signal(s) needs to be examined.
No onboard AC makes sense. Vanilla GPIO or PWM outputs would suffice. I see--combining AC at least under the same weatherproof enclosure might be less work, but you expose a potentially more expensive board to more risk. Same principle as Mueller's leaving the DC V+ injection off of the controller board. Of course, if I'm breadboarding, I'm primarily only concerned about protecting myself.
P. Short wrote:Aren't there pixel strings out there that have two parallel data paths so that if one goes bad, the other signals can still go down the second path? Or am I just imagining that these exist, that they aren't outside of your budget?Also, at the moment I don't see how these pixel splitters would help. Could you walk me through a scenario?
There are pixel that has parallel data, but not interested in them because I already have single data pixels for repair(and price), and I don't see many vendor selling them. Let's take BB's board for example, if I have a segment of 20 pixels prop goes out in the middle of my run, I could flash his board with the B (second out) with 20 pixels, plug Input to one side, B output to the rest of the string, so the data for 20 pixels will be skipped and sending the correct data to the rest of my string. Does that make sense? my understanding is port A has all the data, port B has all the data after X pixels, then Port C is just like port B can be with different amount of pixels.
pakeonoahu wrote:There are pixel that has parallel data, but not interested in them because I already have single data pixels for repair(and price), and I don't see many vendor selling them. Let's take BB's board for example, if I have a segment of 20 pixels prop goes out in the middle of my run, I could flash his board with the B (second out) with 20 pixels, plug Input to one side, B output to the rest of the string, so the data for 20 pixels will be skipped and sending the correct data to the rest of my string. Does that make sense? my understanding is port A has all the data, port B has all the data after X pixels, then Port C is just like port B can be with different amount of pixels.
So if the segment that went bad was 5 feet long (assuming 3" between pixels, so 4 pixels/foot) you would take a spare 5' cable, unplug both ends of the broken 5' segment and bypass it with the spare 5' cable with the 'splitter' at one end or the other of the bypass cable. You would then fix the broken pixel segment or find a replacement for it? Is this what you have in mind? The point here is that you would have spare bypass cable(s) on hand.
P. Short wrote:So if the segment that went bad was 5 feet long (assuming 3" between pixels, so 4 pixels/foot) you would take a spare 5' cable, unplug both ends of the broken 5' segment and bypass it with the spare 5' cable with the 'splitter' at one end or the other of the bypass cable. You would then fix the broken pixel segment or find a replacement for it? Is this what you have in mind? The point here is that you would have spare bypass cable(s) on hand.
That's correct, would have spare cables for it (whatever the max data length the 74125 can drive), the point is I don't want to do repair in the rain and just want the bad prop to go dark but not the rest of them and still in the correct sequences. The variable is the number of pixels I can quickly program into the unit, I could just plug in an Espixelstick to the correct starting channel, but that need to change FPP configuration, wanted something simple to swap out until the show ends.
