Knowing the code pretty well, i dont' think that it will take too much effort to use the 'standard'...
Good useful message, i'm sure JEC will take this on board.
Easy enough to switch to 0x91. Thanks for the link.
Will do some digging to see what it takes to get a proper vendor ID.
Considered using RDM but decided against it because - though I have Wybron's code for the RDM stack - it's written in C. Nothing against C, but the current processor is small and slow enough as-is that the overhead of any higher-level language is just too much.
Adding a 20 MHz crystal to each pixel would totally solve the problem, but at a cost of $0.40 and a half square inch of board space.
Plus, for better or for worse there are thousands(!) of existing pixel boards out there which only support RS-485 in receive mode.
Anyway... Thanks for the advice.
What have you been doing with RDM?
What have you been doing with RDM?
So far just studying the standard to see if the benefits are worth the overhead in a custom controller. Your alternate start code idea may be a better solution in many cases, especially for things like the DMX firmware for Renard boards that don't have bidirectional hardware.
This started with an idea for an alternative SSR and it sorta grew. You know how it goes.
One of my other hats is advocating free/open source software, so anything I create is likely to be released that way. BTW, I understand the Wybron code is no longer free.
