If you read the last log I have to apologize. The issue was not with how the serial was framed. I read the documentation more and sending it byte by byte was perfectly acceptable.

The issue I was having was a physical one. I had wired up the radio to the C.H.I.P. with a man in the middle, a USB-RS232 converter. I set it up that was just assuming that would work, turns out it's very much not the case. You need some special hardware and a couple of components to make that work well.

However, I did finish up the code to communicate with the radio and send configuration data to it, and it receives it and makes the changes to itself, yay!

I ended up using a serial library for rust that I do NOT like. I disagree with how he set up the objects that represent the serial connection. It makes it bulky and hard to work with.

The only positive I can get from it is it has a "timeout" feature that throws an error if we're waiting for data for too long, but that's the ONLY feature I can't replicate myself with a lot less code/complexity.

If I get free time I'm going to rewrite that portion.

Good news though, the next step is writing the simple routines to send a block of data to the radio through the UART connection and have it transmit it wirelessly!

If all goes well, I should have some picture/video of that working in the next couple of days.

And once the driver code is at a point where I don't feel ashamed calling it version 0.0.1, I'll put it into its own library and start on the half-duplex to full duplex portion!