I just bought an FrSky Taranis for my quad copter and needed to get the Mavlink data up on the Taranis LCD telemetry display. So here is my solution using a Teensy3.1 as a converter between MavLink and the S.Port on FrSky X8R.
See attached file below...
I am looking for a ***short and simple*** piece of code in order to get my sensors (battery, my own arduino RPM) on my taranis through the X8R (no APM on all planes). Has anybody already done such a thing ?
It sounds to me like I "just" have to extract FrSkySPort.ino code (from MavLink_FrSkySPort_1.3.zip) and plug it in a standalone sketch. In principle, the sketch should be short, and thus reasonably easy to digest by me. Such a short (and simple) piece of code is what I am dreaming to get started with. Any good man out there ?
very nice job,
I am waiting for my Tanaris radio. I am wondering why it is not possible to directly link the SBUS to the APM2.5 with a software modification ? There are a lot of serial ports available on APM ?
I am having an issue with my Teensy 3.1 board and telemetry to my Taranis. I am using Teensy 3.1 on my Walkera QR X350 PRO which uses an APM board.
1) When I power up the quad with the battery I get no Telemetry.
2) When I power up my quad using a USB to my computer. I get no Telemetry.
3) When I'm connected to the the PC by USB and start up and connect to Mission Planner, I then get full Telemetry on my Taranis.
I have checked all connections on the Teensy board. Since the QR X350 does not have a telemety port I have to solder to the APM board.(GND,TX,RX). Like I said everything works when I am connected by USB and connect to mission planner.? I am using a Frsky 8XR receiver.
Any Ides? This is driving me crazy.
First of all thanks for this great work.
I hope my X8R RX arrvies today.
IS it ok to power the teensy via the x8r. The RX has no own BEC, its powered by the APM wich ist connected to a 5V 3A UBEC.
Is this save? Or should i install another BEC?
Thx a lot.
Please, any ideas on my post above with the strange telemetry behavior. Could it be a voltage issue?
Did you cut the circuit trace to separate VIN from VUSB?
Thank you Roger for your reply.
I actually have two Teensy 3.1 boards The trace is cut on one and not on the other. They both demonstrate the same symptoms, only working when I am plugged into the usb port on the computer and Mission planner is running and I am connected. On one of the boards...the one with the trace cut the LED is not working but it still sends telemetry to my Transmitter when again...plugged into USB and connected to mission planner.
I either use USB or battery, never the two together. Does the trace need to be cut for me? I have read different opinions on this.
it is strange that you guys have all these issues with cutting the trace etc, I have not cut the trace on my teensy, it is wired to be powered from the RX with ground and signal wires to the APM.
it works fine when i power by the the APM via usb or battery or even power the teensy via USB
Same here Jared.
My Teensy came from you :)
Anyone reviewing, adding stuff to the Teensy code, because of the newer features of the OpenTX 2.x custom telemetry screens capability??
How do you have the Teensy wired to the APM? You need Tx, Rx, and GND. If you don't have Tx connected, then the APM doesn't know there is something listening as it's waiting for the heartbeat and won't send telemetry until then. I had what seems like a similar issue three pages back.
Once it gets the heartbeat, it'll send information to the Taranis but not until then.
I do have TX, RX and GND connected from APM to Teensy. I am going to try to use just the TX and GND pin or the RX and GND pin. Maybe Thats why I only get things working when I am connected to mission planner.
Any way, I read your posts and I will give things a try.
Make sure to get the Tx->Rx and Rx->Tx correct as people seem to overlook that all the time. My guess is you have it right since you do get telemetry on your Taranis once it connects but the APM isn't sending anything until it gets that heartbeat.