Why is the Chroma addressing command designed that way?
Well, I needed to find a way to specify which Chromas were the target of a given command. It would have been unwieldy to do it in the server by sending the same command multiple times with an address byte, and it would have resulted in timing errors (albeit small). There were unused numbers in the Chroma command space, so I’m using these and trusting in the Chroma’s spec to ignore bad commands. (It works) A more involved question is why use the least significant 4 bits as a bit map to control 4 Chromas, as opposed to an address controlling 16 Chromas (or add another byte to control 256 Chromas, or combine the two to control 4098 Chromas). First, this way only a single byte command is necessary to set the state of all the Chromas; were the bits used as an address, there would be need to be a defined ON command and a defined OFF command, and a separate command would need to be issued for each Chroma to change its ON/OFF state. Second, I don’t have an immediate application for more than 4
