Well it was a really exciting year and I think all involved in RGB pixels learned a TON of new things. So, while it is fresh in my mind, I though I'd throw out suggestions on improvments to the TP3244. Of course I maybe jumping the gun but...I can dream can't I?
HARDWARE:
* The ability to have CAT5 and/or small screw terminals instead of solder pads for outputs (I did see that tabor had connectors on his). The reason is that I found it hard to swap out (for testing) one board with another. It would also make it a little less DIY. I like the combo used by the ECG with the CAT5+screw terminals. This would include +/- power output.
* Screw terminals for power input
* RJ45 jack and/or screw terminals for signal input.
* The ability to supply power for the pixels AND the board through a single input so you don't need to make jumper cables from the board power input to the light string outputs.
* Built in "test button"/jumper like d-Light/Lynx have so that it can either run a canned sequence (see below) or trigger all channels on then a chase. This would aid in troubleshooting out in the yard or triggering pre-canned sequences.
FIRMWARE:
* The ability to upload a vixen/LSP sequence for stand-alone operation
* Pre-canned macros like CCR (on the fence for this one if we have good sequencing software)
* The ability to turn on built-in canned sequences like the little $6 DMX controllers do
* Embedded "MAC" addresses so that you can re-program a board while it is on the same line with other protocol birdges. David P did this in his controllers and it works great. It also would allow you to "pull back" the settings from the controller like other controllers are able to do (LOR, d-light)...yes there is lots of other RDM complications here.
I want to thank Phil and Tabor for all their hard work this year on the TP3244 - next year is going to even be better!
