FrSky FPort support - testers wanted

[melc (S V)]

A GOOD JOB

Thank you Mark, Alex, Dave , Simon and all other contributeurs

before write in this space, I spent 3 days for test , test , test !!!

[jok250 (Joan Carles)]

Thank you guys such a great job on this project

Here’s my setup:

• Pixhack v3x + ArduCopter 4.0.5

• FrSky R9 SX receiver + R9M 2019 TX, both on Flex ACCESS firmware, EU setup

• RadioMaster TX16s with Access mod, OTX 2.3.11 nightly

• Using the inverter from below…

• SERIAL5_PROTOCOL =23

• SERIAL5_OPTIONS =160

• RSSI_TYPE =3

• RC_OPTIONS=0

• BRD_ALT_CONFIG=0

RC in fully working
No Yaapu telemetry
RSSI at 39% issue

€9.68 5% de DESCUENTO|FrSky yaacu Cable convertidor de telemetría Pixhawk a...

[melc (S V)]

Hi everybody,
After the maiden flight, when I check the logs of the RSSI, I have this :

Need to calibrate ?
An idea ?

Thanks

[melc (S V)]

Finally, After some tests, I think then is all good for me !

Thanks !

[Ozzy (oz ozzy)]

Thanks for the picture Alberto_Ds for the inverter, sorry for the late reply (I thought I already responded, doh).

It looks like this part, but not 100% sure as the small package does not contain the full p/n.
https://www.digikey.com/en/products/detail/on-semiconductor/NL27WZ06DBVT1G/12525361
Looks like a couple 4.7K pull up resistors (for the open drain outputs).

[RizHass (Riz)]

Not sure this link belongs here, but since it involves fport telemetry, I thought I should add this here as well.

Mission Planner Android

I like to open this topic for both @Alex and @Michael. We have now telemetry data over fport protocol (Thanks to Alex) and Michael just released MP for Android. Would it be possible to connect MP to Taranis using either Wifi or Bluetooth link? See the concept diagram below. [image] From a user point of view, there are some advantages: Lighter UAS (No need for extra telemetry device on the UAS) Don’t have to carry laptop to the flying site. Access to telemetry log data on the phone or table…

[Jumbungla (James Hill)]

Hi @tridge,

Thanks for this! Although i’ve tried everything to get FPort telem to work on my Cube Orange and R-XSR with the Q X7 (ACCST), and I cant get it to work.

I had ArduCopter (Cube Orange) 4.1.0 dev firmware installed, I had flashed the R-XSR to FPORT_LBT 2.1.0, and matched the Q X7 Firmware to LBT 2.1.0.

Hardware wise I’ve linked the S.Port pin out of the R-XSR to the TX Pin (next to red VCC) on the Telem2 UART port. TX and RX are bound fine.

In MP, i’ve set the following:

Serial2_Protocol: 23 (RCIN)
Serial2_Options: 7 (InvertRX, InvertTX, half duplex)
RC_Option: 8 (have also tried 0 but no luck)
RSSI_Type: 3

No matter what i try, i dont get any RC link from the Q X7 to MP, but I do get a weird semi-telemetry, but no real information.

When i swap back to SPort (firmware on everything and settings) I get fine RC input (onto the PPM rail) - but my YAAPU screen on the Q X7 is just blocked out with “NO TELEMETRY.”

Any ideas from anyone? I’ve read this whole thread and cant figure it out. I’ve seen something about a pulldown resistor - but no detail. Any tips on whether i need this and what value resistor and is it from the FPort line to earth?

Thanks everyone! Looking forward to contributing to this awesome open source project.

[jok250 (Joan Carles)]

I am having exactly the same issue yet…have tried changing almost every sigle parameter as said in this thread (even configurations for other boards) with no luck; I can’t make the Yaapu widged working as it does with S.port by any means.

With F.port controls appear to be working well, the RSSI signal issue has been solved by flashig de 4.1.0-dev version of arducopter, but the telemetry feedback in the Yaapu widged still appears to be longly delayed and corrupted.

My setup:

SERIAL5_PROTOCOL= 23
SERIAL5_OPTIONS = 4
RSSI_TYPE = 3

Pixhack v3x (fmuv3-heli) with ArduCopter V4.1.0-dev (69C97C15)
R9 Slim+ ACCESS Flex firm. connected to the serial 5 by using the inverted (actually un-inverted) pin.
TX16S OTX 2.3.11 + Yaapu 1.9.1 Beta

I’m using the external access mod for the R9M and all works fine with sbus+sport (telemetry widged included).

I have no chance to test the same setup with a 2.4/ACCST receiver (a R-XSR is on the way).

What else can I try…?

Any imput from you guys will be very appreciated.

Thank you all and merry christmas

[jok250 (Joan Carles)]

Well, I managed to make telemetry to work with Fport by just changing to another uart of the fc… up to date I had tried uarts 4 and 5 but never tested the number 2 (this uses a different connector).

So for those folks with the CUAV Pixhack just use uart 2 to have the telemetry running with Fport; uart 4 or 5 will enable RC control but telemetry does not work with Fport (although with sport it does).

By the way, in my case now I find the Yaapu hud in the transmitter to be more laggy and less responsive with F.port than before… I have confirmed this by changing between fport to sport a couple of times and it is quite noticeable. Is this normal?

Is there any margin to decrease the latency of telemetry with Fport?

I have disabled flow control for serial2 but haven’t experienced any difference.

Thank you,

[Jumbungla (James Hill)]

I finally got FPort working with the Cube Orange and the R-XSR, including telemetry to my Q X7.

Just needed a 10k pull down resistor on the line.

[stavros (Stavros Korokithakis)]

@tridge I am having the opposite problem: Everything works perfectly, except RSSI, which the MAVLink inspector reports as always 255 (and the OSD shows as always 99). The RSSI telemetry value is correct, but the FC only sees 255. I’m using an Omnibus F4 with an XSR receiver.

[Alexey_Degterev]

racerstar f405 wing nano arduplane 4.0.7 stable
r9mm latest accst fport firmware
RC working
yapuu telemetry working
RSSI at 39% issue
SERIAL7_PROTOCOL= 23
SERIAL7_OPTIONS = 4
RSSI_TYPE = 3

[norim (Norimbo)]

Hi for several days I am trying to get telemetry from Arducopter (Cube Orange) on Horus X10S and Archer GR8 receiver by sPort or FPort. Finally I have nice telemetry by FPort but I found strange corelation. Telemetry only works If on other serials the Passthrough FrSky Telemetry Protocol is not active. So I can’t set any SERIAL(2-4)_PROTOCOL:10 If I do that sensors are despairing and there is no telemetry on SERIAL1.
More info here:
https://discuss.cubepilot.org/
Is that normal ?

[Fugazi (Phil c)]

Is it possible to use fport and to add additional s port sensors to another serial port?

Seems as soon as I try and add a sensor and setup that serial port then telemetry stops working

Any ideas ?

Thanks

[yaapu (Alex Apostoli)]

Hi, may I ask what you’re trying to achieve?

[Fugazi (Phil c)]

Very new to ardupilot so probably doing things the wrong way!

Attach a frsky air sensor and vario to a serial port, configure for smart port and then hopefully the sensor values from this will go into the flight controller and then up the connected fport as telemetry back to the receiver and to the radio ?

Thanks

[Simon_Exner]

I dont think it is possible to interface S.Port sensors to ardupilot. Stick to the documentation about which sensors can be used

[Fugazi (Phil c)]

https://ardupilot.org/plane/docs/common-serial-options.html

No 4 says Frsky smart port ?

[Simon_Exner]

yes, that makes the FC behave like a sensor on the Rc-Recivers s.port bus

[yaapu (Alex Apostoli)]

@Fugazi

Attach a frsky air sensor and vario to a serial port, configure for smart port and then hopefully the sensor values from this will go into the flight controller and then up the connected fport as telemetry back to the receiver and to the radio ?

Hi, this is not supported ATM, ardupilot cannot be a master on the SPort bus, a receiver is always needed. FRSky sensor can be chained on the sport bus along ardupilot but ardupilot cannot use them, like @Simon_Exner said ArduPilot acts as a slave.