IOBoard Let's make it better... We need testers...

Awhile ago we made first translating program for IOBoard and since that people have been using it as it was and/or modifying its open software. Now that we have more and more devices supporting FrSky telemetry, converting becomes more fun.

So let's make it. Current roadmap for IOBoard is:

- Have full support for MAVLink/FrSky conversion

- LED driver with configurable patterns

- OpenTX, er9X support

- TLD-02 display support

- Updated Configurator

Currently tested features on Taranis radio:

Heading, Temperature 1, Temperature 2 (shows satellites/fix type), Armed/Disarmed and Throttle values,

Lat/Lon, Altitude, Voltage, Cell volt (avg), Speed

jD-IOBoard can be found from jDrones store

Latest MAVLink/FrSky software is IOBoard_FrSkyMAVLink.v03a 

software can also be found from arducodes repository at google code

Let us know how it works and if you have ideas, post it on..

Views: 28135

Comment by Jani Hirvinen on July 26, 2013 at 11:08am

Ok so how to connect. LTMNO made a great picture on that.

Connect cable from your telemetry distribution board or directly from APM2.5+ (or other MAVLink capable flight controller) to IOBoards FTDI connector. Connect D5, D6 and GND to your FrSky telemetry receiver. D5 goes to Rx, D6 to Tx and G = GND. 

IOBoard starts to listen MAVLink packets from it's main serial port and with speed of 57600 and converts most important messages to FrSky protocol and send them out from pins D5/D6 with speed of 9600. 

I you want to debug your board, v0.3 and other alpha versions will have 38400 debug feed coming out from pins 11,12 (MIS, MOS on board). Connect another FTDI cable on these pins. Don't forget GND. GND, Tx, Rx. 

If you don't remember FTDI connector pin order, take a look this quick memo from SparkFUN

Comment by Magnus Persson on July 26, 2013 at 11:37am
would this work with openlrs for telemetry?
Comment by Ralph Weitzer on July 26, 2013 at 11:54am

WOW. I just tested this the new .03a hex with my Frsky Taranis and I got altitude, speed and all the other values seemed to work great. I will have to do more testing but it seems like most of the telemetry functions were functional. Thank You for all your dedication.

Comment by Jani Hirvinen on July 26, 2013 at 8:23pm

Magnus I have not looked OpenLRS lately but after whole base software is done for IOBoard adding additional protocol is not too difficult. Can you point to some OpenLRS protocol specs so I can take a look at it.

Happy to hear that it starts to work for all of you. We still need field testing for speeds and altitudes etc to be sure that they work as expected. 

Comment by Jani Hirvinen on July 26, 2013 at 9:03pm

Values that are running and known to be correct:

Accel - X, Y, Z = Accelerometer values, -+ values

Temperature 1 = Flight controller internal temperature, Celsius

Temperature 2 = Visible satellite count and GPS Fix style, 2-3 digits where LAST digit is fix status 0-1 No fix, 2 2D Fix, 3 3D Fix. FRONT digits are amount of satellites. For example "63" = 6 satellites, 3D FIx or "103" is 10 satellites, 3D fix or "32" = 3 satellites, 2D fix

Heading = Your current compass heading

RPM = Armed/Disarmed status and approximate throttle value when armed. 0 = Disarmed/Motors off, Values between 1020 - 1960 are shown when motors are armed and throttle position. Number represents pulse width so for example around 1500 is middle throttle. This value is NOT exactly same what Mission Planner might show for your throttle channel as we need to use special scaling made by FrSky but it's close to it. Accuracy is -+30 uS.

Altitude = Altitude detected by your flight controller (works on tabletop tests, not confirmed on real flight yet. Anyone??)

Lat/Lon = GPS Latitude/Longitude details with N/S, W/E indicators

Time = Sec/Min/Hours since last reboot of IOBoard

Things that needs to be fixed/confirmed are:

Voltage = Battery voltage. It seems to work but startis drifting after awhile. 

Current = It's seen by IOBoard but not forwarded correctly

Fuel Level = Seen by IOBoard but not confirmed yet

Speed = Seen by IOBoard but not confirmed yet

LED outputs and patterns. Currently still untouched. Work with these begins after FrSky converter is ok.

There seems to be huge amount of extra parameters that Taranis and er9x style radios can show, anyone happen to have simple document of these?


Comment by LTMNO on July 26, 2013 at 9:07pm

Ignore my previous posts.. now that I have re-read your initial post, I see exactly what you are transmitting from the APM to IOBoard to the FrySky Receiver.  All that information is being transmitted to the Receiver.

It seems that the follows values are correct.. 







And the following are incorrect...



I color matched the FTDI Capture to the APM Screen.  Hope that makes sense?  Midnight here, will take a look again tomorrow.


Comment by LTMNO on July 26, 2013 at 9:13pm

Not sure if this was what you were looking for regarding OpenTx Telemetry Values

Each field can be one of the various available parameters, of course the corresponding sensors and/or hub must be installed in the model:

  • Tmr1,2: Both timers
  • SWR: Transmitter antenna quality. Should always be below 51, or a popup warning will appear and an audio alarm will sound to warn you to check the radio's antenna. The value itself is of little meaning.
  • RSSI: Lowest of the RSSI values from the radio and receiver in D8 mode. In X16 mode, RSSI of the receiver.
  • A1,2: Analog ports on D receivers (only A1 available on X8R receivers, with receiver voltage)
  • Alt: Barometric altitude sensor
  • Rpm: Engine speed, number of blades is adjusted in the settings above
  • Fuel: Fuel level
  • T1,T2: Temperature sensors 1 and 2
  • Spd, Dist, GAlt: GPS speed, distance from starting point and GPS altitude
  • Cell: Lowest cell on FLVS-01
  • Cels: Sum of all cells on FLVS-01
  • Vfas: FAS-40/100 voltage measurement
  • Curr: Current, source configured in the settings above (FAS or analog)
  • Cnsp: mAh used totalizer (needs current source configured correctly)
  • Powr: Power, voltage and current sources configured above
  • AccX,Y,Z: Acceleration values from TAS-01
  • Hdg: GPS heading
  • Vspd: Vertical speed (either calculated by the radio or reported by the sensor, depending on the sensor type chosen above)
  • xxx+/xxx-: Min and max values of the available parameters

Comment by Jani Hirvinen on July 26, 2013 at 9:14pm

Oh yeah i forget Modes :)

Yes there are currently debug feed running from Miso/Mosi pins that you can hook up with FTDI cable. I will add more functionality on that later but now it shows atleast most important values and you can check that IOBoard will receive real values from APM/FC. If MAVLink rates are not set correctly most of those values are 0000.

I have hardware for external display (GLCD 128x64) too but currently no software for it. Anyone willing to help on that? I plan that to be replacement for FLD-02 display as all it's screens are Fixed and we need to change their data :)

Comment by Simon on July 27, 2013 at 7:21am


Please explain why you think that Lat/Lon are incorrect.

Comment by LTMNO on July 27, 2013 at 7:33am

Hi Simon.... perhaps I don't understand how to read the Lon/Lat?

I am only comparing the values that are on the screen depicted above.  They are not matching... however... perhaps i am not understanding the translation from IOBoard to FrySky?

43.9188384  != 4355.08

-79.8005184 != 7948.02

43.9188384,-79.8005184 - This value in fact is the coordinates to my home.


You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2019   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service