Trad heli tuning + Fport can’t send telemetry back

Here is a quick summary for you to have all info on the same “page”

I got several drones (fix wing, carol, multicopters) with various FC, most of which matek h743 ( various flavours) with Frsky Rx all running fport firmware and taranis x-lite as radio running opentx and yaapu Lua script.

All model memory on the radio are copy paste or others (multicopters to multicopters and planes to planes) in order to keep consistency with channels, buttons, telemetry)

All of the above working flawlessly.

When I was assembly the heli, I had a spare speedybee f405 v4 with the usual R-xsr Frsky receiver. I modded it to have uninverted fport and connected to the FC running (for the time) latest version of arducopter (traditional Heli)

Once setup the FC to work with fport as per wiki page, I always had data coming from TX to FC but not the opposite. The only thing that my radio receive from the RX is the built-in rssi but absolutely nothing on telemetry.

Since then I changed the following (more or less in order)

  • tons on parameter of the FC
  • rebind the same rx multiple time making sure I selected 1-8ch with telemetry
  • disable and enable script on the Frsky Rx.
  • firmware update on TV (latest arducopter)
  • FC upgrade from speedybee to triumph h743 (same bootloader as Marek h743 slim. (From now one the default FC on the copter)
  • use inverted Fport (standard pin)
  • move from tx6 to rx6 pin
  • use a different non modified rx running same firmware and inverted Fport
  • some other parameters on the FC firmware
  • tested randomly another drone on a different memory ( I correctly receive telemetry)
  • connected the tx to companion to check all possible parameters on the Heli memory)
  • reduced number of channels sent from radio from 16 to 12
  • complained here :slight_smile:

In every single test I have done, I always had the TX sending channels on the FC and able to fly but never received telemetry back a part as mentioned already Frsky built-in rssi meaning that the Rx is able to send back something to the TX

Hope this helps

@rmackay9 any suggestions or is someone already looking into code ?

I hate to say it, but this really seems like user error, and we don’t really have a place to start troubleshooting the firmware, given your own inconsistent results. You’ve changed nearly every variable, including the receiver and autopilot. The addition of self-modified hardware and what appears to be an unsupported autopilot only serves to further muddy the waters.The only common variable is the handheld transmitter, so that’s the place to start troubleshooting on your end.

I’m sorry I don’t have better advice to give, but unless you can reduce the variables, we are going to have a very hard time sorting this out.

I had exactly the same problem. I tried every permutation of port setting. No telemetry data got passed to my Frsky receiver.

I have never had a problem with Fport and telemetry. I just finished setting one up on a TBS Lucid H7.