Quote:
|
Originally Posted by Pat Fairbank
If you need even more bandwidth, you could probably set up some interlacing of your own (e.g. use one of the user bytes to describe what data is in the other five).
|
That's what I was planning LED Byte 2 has 5 unused bits. That gives me 6 bytes, and 5 bits to describe what they are. I'm trying to stay away from the PWMs because I want it to be as modular as possible. My goal is to just get all the ports through the dashboard interface then figure out how to interpret that information in my dashboard program. So far, I've figured that 6 bytes can get me all of the digital ports and the relay ports. I'm still trying to decide on how to handle the analog ports because each of the 16 would take a full byte. Does anyone know of any interesting encoding/compression algorithms?
Quote:
|
Originally Posted by Billfred
CTRL_A and CTRL_C both have information in them that differentiates the frames.
|
Well, that only gives me the information on my dashboard program. It doesn't tell me which packet is being sent during this given program loop on the RC, so that I can encode the correct data into the packet. As far as I can tell, they accessible to the user on the RC. EDIT: Oops, they are NOT accessible to the user on the RC.