Oldish thread, but I tough I'd chip in, just in case... I tried a RX6R with the latest FW (2.1.7, I think) and couldn't get the F.port to work until I realised I had to look for the (un)inverted signal. Once I connected the Brain2 to the uninverted signal pad (oval pad, under the connector) it worked. At least I think it works, I have channel movement and found two extra sensors : Fuel and CPU temp. Curiously fuel reacts when I move the unit so I guess it's not the right name...
Weird thing is : the channel order is completely different than when connected via Sbus to the same receiver... This might be something to do with the new ETHOS fw that's on the Tandem X20 I've started to use.
"FUEL" is used to transmit the Global Vibrations value because OpenTX has never provided (until now) a sensor for telemetric transmission of model vibrations by assigning a correct name to it. But in the transmitter you can change the name from "Fuel" to "GVib" or whatever you like.
For automatic channel assignment, the multiprotocol icon must be selected while the transmitter is powered on and the receiver is already binded, connected and powered. Only in this way can the routine recognize the correctly received protocol. If after selecting the multiprotocol icon the control unit is switched off, the automatic recognition is no longer performed.
To perform the automatic recognition again with the transmitter on and the receiver binded and powered on, you have to select another protocol (for example standard receiver) and then select again the multiprotocol icon.
If instead you are using the new icon "F.Port / F.Port2 Inverted", the channel assignment is fixed and is the standard one of the S,Bus protocol (exactly like selecting S.Bus protocol icon or OpenTX protocol icon) "AETR".
If the channels are inverted it means that they are set incorrectly in the transmitter.
Yesterday brain forced me to update. Now I'm constantly getting a "sensor lost" warning. Very annoying, especially since I've been flying without any issues for the past 2 months (over 300 flights).
Yesterday brain forced me to update. Now I'm constantly getting a "sensor lost" warning. Very annoying, especially since I've been flying without any issues for the past 2 months (over 300 flights).
Me too, went out yesterday to have few flights and put me right off.
Version 3.4.013 is now available online.
For now it has to be loaded manually.
Just gone to update firmware manually and release notes show Version 3.4.012 and version 3.4.13 and not updating the app to Version 3.4.0.13 and won't update to FC.
Just gone to update firmware manually and release notes show Version 3.4.012 and version 3.4.13 and not updating the app to Version 3.4.0.13 and won't update to FC.
Problem solved, took few attempts but sorted now....and no annoying, sensor lost ?