FrSky FPort support - testers wanted

Blog
367

I had the very same problem with an r9mm and a kakutef7 and managed to get it to work by swapping rx/tx and enabling built in pullups An Open Source Frsky Telemetry Script for the Horus X10,X12 and Taranis X9D,X9E and QX7 radios

368

Alex, thanks, I saw that. No luck. Tried different port, with both swapped and non-swapped pins, with both brd_alt_config = 0 and 1. Same result. I get 2 messages in your script:
00:00 INF ArduPlane V4.1.0dev (e727d082)
00:00 DBG RCInput: decoding FPORT

If I reconnect RX on live FC I might get one message through (random) but that’s all.

369

I have H743 and a Jumper FPORT RX. :-s

370

Anyone tell me what’s wrong here , i set as wiki say , it’s kakute f7v1.2 , RXSR + jumper t16pro , i do serval change fw version but nothing else

372

Hi ,

I got following situation about FPort with 4.1. For my dual motor plane on XUAV goose frame with Pixhawk 2.4.8 + Frsky X9d Pluse (OpenTX 2.2.3) with R9M Flex + R9mm (Flex). but not work with fport config.

Following are my config:
FC: pixhawk 2.4.8 from China
Receiver: R9MM with R9M Module (Flex F/W + FCC)
Arduplan fmuv3 4.1 dev(2021/05/15)

Wiring : R9MM Inverted F.Port pin --> TELEM1 TX
SERIAL1_BAUD:Tried 57,115
SERIAL1_OPTION : Tried 4 , 7 , 160
SERIAL1_PROTOCOL: Tried 4, 10 , 23
RSSI_TYPE = Tried 0,3

Symptoms:

  1. Radio No Signal on FC (Servo can not move and No response on Mission Planner)
  2. Transmitter got connection and have telemetry signal
  3. run Discover new sensor on x9d plus alway got 2 sensors only (RXBT ID:248/ RSSI ID:248)

any idea how to resolve ? thanks

373

Hi. I have no Ground speed data on my radio. Im using r9mm on F.port with arduplane 4.1.0 dev. Fc f405 wing All other sensor work on radio telemetry on taranis and i have Gspeed data on Mission planner but No on the radio. I ve tried to delete and add discover new sensor but no success…any idea?

374

both of 405 and 765 working now. I am waiting for 4.1 stable now.

375

Matek F765 R9m Slim plus OTA receiver Fport settings/setup.

For matekf65 with R9m Slim plus OTA Telemetry, below settings works.
Using Arduplane 4.1 Beta

  • SERIAL7_PROTCOL=23
  • SERIAL7_OPTIONS=15
  • RC_OPTIONS=0 (8 didnt work as developer advised)
  • RSSI_TYPE=3
    And make sure:
  1. Change the receiver settings from Sport to Fport.
    2)Sport/Fport cable connect to RX6 ( Same as you do connect for SBUS, as Serial7_options settings swap the pins)

How to change the receiver settings in open TX
Go to Model>>Scroll down to your receiver 1 tab>>click to open and select options>>on top change sport to Fport. ( make sure you have the latest firmware)

376

Just tested on an orange cube with 4.10 dev beta 3 with an archer M+
On X12S with isrm module installed and X7Q access radio works great

  • SERIAL1_PROTCOL=23
  • SERIAL1_OPTIONS=47
  • RC_OPTIONS=8
  • RSSI_TYPE=3
    Note: rx/tx swapping means FPort has to be wired to the RX pin!

image

377

Matek F405 Wing - FPORT
No external converter required with R9 Slim plus receiver or with any Frsky receiver, can support inverted Sport/Fport (mostly does).
R9 Slim plus:
RX1 port on the receiver need to be connected/use instead of Sport/Fport. As RX1 is inverted S.port port not the Sport/Fport. Sport/F.port is for F7 flight controller.
Make sure receiver has latest firmware and you have enable the Fport from open tx option.

  1. Connect receiver RX1 to TX2 (UART 2)on flight controller.
  2. Config below settings for serial7 ( serial 7 maps to Uart2 as BRD_ALT_config=1)
    BRD_ALT_CONFIG =1
    SERIAL7_PROTOCOL =23
    SERIAL7_OPTIONS = 4 (Half Duplex) RSSI_TYPE =3
    Serial7_BUD = 115 ( mine is works perfectly with 115, try 57)

Enjoy the yappu telemetry on your transmitter. Dont forget to delete all sensors and discover again under openTX system settings.

378

@Sunnyfx79
If connnect r9slim+ RX1 to TX on Uart6 of F765wing, how to setup?

379

By reading the Wiki. Page down to where is says Matek F765-Wing

Fport

380

@dkemxr
Hi Dave,
I did read it. and tried many other setting. it is not same setting with the link says.

  1. Connect receiver RX1 to TX6 (UART 6)on flight controller.
    2.BRD_ALT_CONFIG =1
    SERIAL7_PROTOCOL =23
    SERIAL7_OPTIONS = 4
    RSSI_TYPE` =3
    Serial7_BUD = 57
    RC_OPTIONS= 0

or Connect receiver RX1 to RX6 (UART 6)on flight controller.
2.BRD_ALT_CONFIG =1
SERIAL7_PROTOCOL =23
SERIAL7_OPTIONS = 12
RSSI_TYPE` =3
Serial7_BUD = 57
RC_OPTIONS= 0

Matek F765wing with Frsky R9slim+(Fport flashed)

381

Hello,

Any specific reason to connect to tx6 ? As better connect to rx6 as negative, positive and live wire all 3 aligned.

If you still want to use tx6 just uncheck the swap check box under serial 7 option.(I didn’t try it but it should word as swap check box swap the tx and rx pin, which translates rx become tx and tx become rx.

382

Thank you for your reply.

The reason I wanna use tx 6 first I wanna give a try, just for the curiosity. Second I use inav which TX on fport. So I don’t need to change the wire when I switching the firmware.

383

Ok. Just make sure r9slim has fport protocol selected. Protocol can only be changed from opentx transmitter menu selection.

384

yes my r9slim+ is old version of Fport. It cannot be selected from the radio. But they are both fport flashed.

385

I read this entire thread twice and still spent a very long time this morning trying to successfully use FPort on a Cube Orange with an R-SXR receiver, Horus X12S (OpenTx) transmitter, and the Yaapu telemetry scripts. The Cube is presently running Rover 4.1.0-beta7.

The biggest issue is that FrSky’s ACCST 2.1.0 firmware appears to be incompatible with ArduPilot’s FPort implementation. I finally found a copy of the 1.9-series iXJT firmware for the X12S, flashed that, reverted the R-XSR to the 1.9-series as well, and everything worked immediately without any hiccups.

The receiver is wired via its DF13 connector (not the solder pads) with a 10k pulldown resistor. The following recommended settings worked on both SERIAL2 and SERIAL3:
SERIAL2_OPTIONS = 7
SERIAL2_PROTOCOL = 23
RC_OPTIONS = 8
RSSI_TYPE = 3

I’m very happy to have FPort working, but it’s slightly frustrating to have to revert my other receivers to ACCST 1.9x if I want to keep this rover working as-is.

386

Reference my previous post just above, I was very happy to get FPort working with the firmware reversion, but that has created another problem for me.

With the older firmware on my transmitter, I’m either forced to downgrade my X8R receivers to a version that does not support pass-through telemetry, or rewrite the firmware on my transmitter every time I switch from the R-XSR model to an X8R one (of which I have two).

Have I done something terribly wrong by downgrading to 1.9x in order to get FPort working, or is ACCST 2.1 FPort support forthcoming?

EDIT (SOLVED):
See immediately below. The issue is not an ArduPilot one, but rather a FrSky one.

387

Hi, there’s no such thing as a specific accts 2.1 fport, what you experience appears to be a frsky firmware issue and you’re not alone https://github.com/FrSkyRC/Firmware-Test/issues/118

1 Like