LukeB

Just the Attitude object.

No it doesn't pass through the GPS to the DOSD. It would be nice to but their firmware sources the barometer and imu data via i2c, and I assume their GPS data is via a serial protocol of some sort.

Not sure if you listen to the All Things that Fly podcast, but they recently had an episode on batteries. It's quite an involved topic so it's worth listening to. It's http://allthingsthatfly.com/ episode 212.

The main reason for the 3.3v board was that I had one lying around already. Also I believe the DOSD uses 3.3v i2c but could be wrong. I remember seeing it somewhere but I just had a quick look and couldn't find the reference. It may still work with 5v but I'm not sure on this.

The sendAttitudeRequest function requested the attitude UAVObject from CC and the processMessage function parses the UAVObject response. I do recall seeing somewhere in the forum that someone has written an something a bit more complete for parsing UAVObjects for the Arduino. That's probably a better place to start than my code as I've just done it quick and dirty for this specific purpose. The other thing to note is that if the object id or structure of the attitude UAVObject change my code will break as I've hard coded these values.

Sure here's a link to the source code. https://bitbucket.or...b2208/osdbridge

It runs on an Arduino Pro Mini (3.3v ATMega 328).  You'll need to connect the tx, rx, ground and power pins to the telemetry port on the CC. The Arduino is then connected to the dragon OSD i2c.

I checked it again this morning and it works with the code attached. I hope it's of some use to you, let me know if you have any questions.

HI Guys,

Not sure if anyone is still interested in this but I did get my dragon OSD working with CC through a bit of a hack. Instead of changing the code in CC, I used an arduino mini connected to the telemetry port and requesting the attitude information using UAVTalk. The mini connects to the dragon OSD as an i2c slave and outputs the attitude information. It's a quick and dirty (with the emphasis on dirty) implementation and I haven't tested it much but it seems to work ok.

Anyway, if anyone is interested in using this whilst waiting for the OP OSD to come along, then I'm happy to pass it along.