Today I had to switch my testing over from the Vocore to the C.H.I.P. due to not actually having any free 3.3v outputs. They were all taken up by the attached dock... whoops... I'll have to figure out how to work my way around that one.

Good news is, the code when run on the C.H.I.P. worked flawlessly, the sysfs code works on both platforms without have to add any sort of macro logic, which is wonderful.

Today was the first time I actually plugged the radio into one of the devices and nothing caught on fire thankfully. Work is a little slower than I'd like because instead of just bit-bashing this together in python I'm using a new language to me, and writing it in a fashion where I won't be embarrassed if another human looks at it.

Here is the datasheet for the radio I'm using in particular http://www.inhaos.com/uploadfile/otherpic/DS-RF-TTL-100-V01-EN.pdf

I completed the ability to change the mode the radio operates in, because in order to configure the internal settings of the radio, I need to place it into "sleep" mode and send it a specially crafted string over its UART connection (still currently unconnected).

Now comes the question of what I want to work on next... I'm not sure if I'd like to continue down the configuration route and make sure I can tweak all the settings in the radio, or just take the plunge and try to send a packet of data between the two radios hosted on the C.H.I.P. and the Vocore. I'll have to figure out the power supply problem though... and the pins on the Vocore aren't in a regular header form factor, I can barely squeeze prototype wires one next to the other. I'm not sure I'd be able to wedge all required wires in safely.

All in all a good day.