Hi there,
Tried searching and came up with nothing
I have a 3dr radio on telemetry 1, and I have a OSD on telemetry 2.
I just brought a Taranis, and I would like to be able to pump telemetry down the FrSky protocol.
Is there any way to re purpose another UART as a third telemetry connection?
Side note: Is it possible to deliver 16 channels to Copter via SBUS? I see mixed reports.
Regards,
James
Replies
Or you could also simply use a Y cable on telem 1 or telem 2
No, that won't work for what he is trying to do. The protocol for that port with the 'y-cable' would have to share the FrSky protocol, as Randy has described.
James, follow the wiki instructions: http://copter.ardupilot.com/wiki/common-frsky-telemetry/
I know that seems obvious, but . . .
As far as the 16 channels, yes, I have an X8R, X6R, and an X4R. All 16 will show up in 'RCINxx' on MP using SBUS connection to the RCIN port. Ch 9-16, 9-14, or 12-14 respectively can be output on the FrSky receiver's PWM pins in addition to the PixHawk seeing all 16.
Cool breezes!!
@Tony, yes it will work, see further responses. It will also work using raw mavlink telemetry piped into a Frsky converter as described here: http://diydrones.com/forum/topics/amp-to-frsky-x8r-sport-converter
ohhhh, OK H. You got me. I was actually going to use the 'Teensy' option for MavLink conversion into the FrSky SmartPort.
No matter, we now all understand. That's the point.
James, yes, but bear in mind that the Pixhawk can output 9-14 on the Aux pins to servos and such, or now with 3.3 Copter, you can use up to 12 channels for flight controller options. As example, I now have 'brake', 'RTL', 'land', 'lost copter alarm', and 'acro trainer' assigned to those higher channels, leaving room for the basic modes on my 6-position. I use a few of the PWM channels for controlling lighting and gimbals, and so 16 channels can get used up pretty quick.
Remember when you dreamed of 4 channels on your fixed-wing RC? Life is good.
Thanks Tony,
Good to hear I can have more than 8 channels into the pixhawk and simultaneously have a few on the PWM pins. Very versatile, I was finding my 9x a little limiting.
I have brought the bits and peices to make the FrSky telemetry work. Looks simple enough.
The Y cable could be used on Telem1 for telemetry and OSD, leaving Telem2 for FrSky. Serial4 is non standard wiring, but I found it easy enough to pull pins from a spare cable and make one (keeping a header for Serial5/console).
The MP "Full Parameter Tree" does show CH7_OPT thru CH12_OPT, Which appear to have all the usual CH7/8 options. There just isn't a drop down config on "Extended Tuning" for them.
I haven't tested this yet, but am curious what the RCx_FUNCTION (x = 1-14) will do, for example "RCPassThru", presumably 9-14 would be the 6 aux outputs. The rest of those options mostly look like Camera and Plane controls.
Ah I didn't realise channels other than 7/8 had OPT settings, that is fantastic.
When my build was last stripped down I had a go at getting the RCPassThru working and had no success, ended up just leading servos straight to the receiver.
I will have another go when I get the new radio setup.
Thanks
If you're using Copter-3.3.1 (latest official release) then it's possible to have 3 telemetry ports. You can set the SERIALX_PROTOCOL (where X is 1,2,3 or 4) to "1" to enable it for MAVLink (other numbers can be used to enable it for FrSky output, GPS, etc).
Fantastic, thanks Randy, thats what I was hoping.
If you have an OTG enabled smartphone you can run Tower and not only will you get telemetry, you get full GCS functionality...
And you can use a modified Walkera Type B phone holder the mount the phone to your radio.
20150901_120522.jpg
-
1
-
2
of 2 Next