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..
Comments
Hi-
for testing the new FW I used the jd io board configurator and an arduino mini pro connected via ftdi.
Flashed v0.5 with that tool correctly.
The odd thing is: when I connect USB (also gives power to the board) the green LED is blinking for a few seconds- and only then I am able to access the board. Otherwise I get "Failed to talk to bootloader". Need to power cycle to connect again while new blinking...
It also does not seem to work on my copter (the old FW 191012 works). It is connected to an telemetry module also so I only connected RX of the board to the APM. Is this still correct?
On http://www.jdrones.com/wiki/guide-jd-ioboard/#sthash.3mMSctvs.uHF6K...
it looks like RX and TX should be connected now but the link to the pictures is broken...
Thanks
RPM is showing 1560 on initialising and 3060 after a few seconds (plane mode, armed but throttle on zero)
T1 is showing 1 or 2 even in my room at 20°Celsius.
Thanks
Kai
I like to use the mini pros without pins- so a bit of effort to connect FDtI (though done quickly...).
For ISP I simply use: http://www.hobbyking.com/hobbyking/store/__42120__Atmel_Atmega_Sock...
so hardware- wise this is much faster ;-)
Just read the fuse settings before flashing:
avrdude -P <comport> -b <baudrate> -c <programmer> -p <chip> -U lfuse:r:-:h -U hfuse:r:-:h -U efuse:r:-:h -U lock:r:-:h
If you are going to use a programmer to flash I strongly suggest you read up on fuses and avrdude to know what you are doing. Otherwise you will end up bricking some chips.
By why not use a FTDI cable? Makes life a lot easier.
I want to program the latest .hex file to an Arduino Pro Mini 5V (no USB).
(The files available as source code sort of work for me but give wrong GPS coordinates on my Taranis)
To do so I want to use a Usbasp programmer with the Atmega Socket Flashing Tool (connects Usbasp ISP pins directly to the chip).
Here I am stuck because I HATE avrdude (already bricked few Chips with wrong fuse settings...)!
Can anybody help me here?
.hex --> usbasp --> Socket Tool --> Arduino Pro Mini
I know- beginner question but I do not want to ruin more chips nor use FTDI ....
If there is no tool- what ARE the correct fuse settings to do so (complete command line would be awesome....)
Thanks a lot
Roman
Will post on GItHub, thanks Jani..
Regarding the IOBoard.. I have two of them… I was mainly worried about when I was not using FPV/OSD to see telemetry data.. so the IOBoard works great for that case.
But on my other radio I have FAS so it uses the same port… where as the AttoPilot doesn't. ;-)
All good.
Thanks!
@LTMNO i will add those to github page or you can do that too. Just fork our repo, edit comments and make a pull request so we can update changes. Contributions are welcome, that's how opensource works :)
Yes Low batt alarm will start blinking left/right leds when event is triggered. Cell count is counted when you connect power on the system.
FAS and FrSky Hub use. True you do not need IOBoard if you have FrSky hub with sensors and/or FAS current sensor. IOBoard is mean to connect to your flight-controller, it reads MAVLink protocol from FC and converts that to FrSky protocol.
@Bo, actually it is v0.5. Heading is normally in Hdg message. It really depends from what device you try to look those values. If you use Taranis radio, it's Hdg value. How you try to show them?
quad!
Alright, I have been giving it some thought and I think that I might have it now... the Batt Volt setting is for the LED portion of the IOBoard and will trigger an event that can be used for LED Display Patterns?
One thing I did not notice when configuring another solution with IOBOard so that others don't make the same mistake, but if you have the FAS-100 Amp/Power Meeter for your Radio/Receiver, don't buy the IOBoard to do the same as they both use the TX/RX port of the FrSky Telemetry Port. On my other Copter, I have AttoPilot which uses the A1/A2 slots and I can use the IOBoard in conjunction for other messaging. Just an FYI...
Hello Jani, uploaded and tested and everything is working fine…
I have/was looking for documentation on what has changed and or fixed.. Looking at the commit logs in GitHub but and noticing a few things… but is there anything you can share?
Question, what does the Battery Alarm setting do? will that alert or prompt something on Radio? Not really sure… or is it some handy calculator on the Configuration tool?
p.s. the Volt Reading is much more stable now. ( no twitching )
Thanks for the information.
Cheers.
-
4
-
5
-
6
-
7
-
8
of 15 Next