Forum Replies Created
Thanks for bringing this up. Unfortunately, this is a bug in 2.3.5 that is already fixed in the master code base, and most likely in the next release of OpenTX: https://github.com/opentx/opentx/pull/7356
We strongly recommend you skip 2.3.5, which was released mainly because of critical issues found in Horus transmitters.
Not to my knowledge. I’ve tested the new firmware on the bench without issues regarding telemetry performance.
Maybe someone else has a different experience so please share…
In reply to: arducopter 4.0.1 hex, not connecting to flight deckFebruary 7, 2020 at 12:25 pm #28947
Is this the issue (race condition)? https://discuss.ardupilot.org/t/critical-issue-with-frsky-sport-passthrough-telemetry-in-4-0-x-releases/50967
I think this would be best addressed on the ArduPilot forum. While we designed the original passthrough protocol, ArduPilot is free to implement changes to it and we’re grateful the community makes improvements to the protocol all the time! The changes are not meant to break the FrSky telemetry capability altogether though. Is protocol “4” working still? Anyway, this does not have to do with the cable but with ArduPilot and hte devs who made the change would have a lot better idea of what’s going on there…
Also please check your parameters. I do believe there are additional serial parameters that have been or will be introduced soon in ArduPilot relating to the signal conditioning, that if not setup properly would prevent communications.
In reply to: arducopter 4.0.1 hex, not connecting to flight deckFebruary 2, 2020 at 11:54 am #28870
Yes, FlightDeck will work only if the “GPS” sensor updates (indicating the link is working).
If not, you could check whether your SERIAL#_OPTIONS ArduPilot parameters are correct and any other serial port parameters (e.g., make sure only one serial port is configured to 3, 4, or 10).
There are additional troubleshooting steps found in the FlightDekc manual: http://www.craftandtheoryllc.com/downloads/FlightDeck_Manual_EN.pdfDecember 23, 2019 at 1:56 pm #27833
I think my emails to you are ending in your spam folder. Can you please check?
RC transmitters such as the Taranis and X8R operate on unlicensed 2.4GHz bands that are yet distinct from Bluetooth. Besides, Bluetooth would not have the multi-mile range displayed by those RC transmitters.
I am not aware of any interference between the two, and in fact, some transmitters such as the X10S has a Bluetooth radio in addition to the radio for RC controls and telemetry. So I think you’re good to go… and you can always check and test the strength of your RC signal.December 14, 2019 at 2:16 pm #27666
Yes, you can use the other pair to power something else, or use the servo rail of the Pixhawk essentially as a power distribution bus (connect the landing gear and gimbal power to it too).
You won’t have trouble pulling the max rated 3A of your BEC out of the servo rail.December 13, 2019 at 12:05 pm #27631
You can connect both reds and both blacks onto the servo rail, to any of the MAIN and AUX pins, without having to modify any cable coming from the BEC:
It’s a rail, so all the AUX and MAIN + are connected together, and all the AUX and MAIN – as well.
You do have unlimited downloads. The download counter is just a way for us to keep track of volumes and flag excessive activity.
I just reset your counter so you’re good to go. You can download again.
Since you see “GPS”, the FrSky telemetry link is working.
In that case, there is a problem with the installation or execution of FlightDeck, so please verify those steps: proper installation and setup of OpenTX to start FlightDeck.
If you see the emulated “GPS” sensor updating, the FrSky telemetry link is working.
If you see the emulated “Alt,” “VSpd,” and “VFAS” sensor updating, FlightDeck is working.
As long as you’re using OpenTX 2.2 or later, FlightDeck will work…
RxBt and RSSI come from your receiver itself.
A “Cels” sensor should be discovered if there’s a working FLVSS or MLVSS on the SmartPort bus, regardless of the discovery of other sensors. In other words, if you’re having issues with your FLVSS sensor, it may be best to start troubleshooting by only having the FLVSS sensor connected to your receiver and attempting discovery (also connect the FLVSS sensor to the LiPo). You don’t need ArduPilot or FlightDeck for the FLVSS sensor to work properly.
Both systems will work with your 6S pack. We don’t have a particular recommendation, although there’s a price difference between the 2-6S and the 4-14S BECs.November 24, 2019 at 11:53 am #26889