Guide how to Setup F.Port with FrSky R-XSR and Betaflight 3.3 (English)
Вставка
- Опубліковано 8 жов 2024
- F.Port (often written FPort) is the combination of the serial protocols SBUS and S.Port. While it was previously required to connect two cables and use up two UARTs, we only need one cable and one UART now. Why did you take so long? Thanks in any case to FrSky and Betaflight for this achievement!
It is important to know, for F.Port we need a firmware upgrade of the receiver. In a Betaflight version below 3.3 the option for "FrSky FPort" is unavailable. So, we need a firmware upgrade for both, the flight controller and the receiver. In the video we go through both processes.
Let's start with the hardware setup. F3 and F7 users can skip this step, this only affects the F4 users because the F3 and F3 can handle the inverted signal.
There are several options. Depending on which option we choose, we will configure Betaflight accordingly. Either we take the inverted S.Port signal from the standard output, for example from the plug. Or we use the uninverted signal. In the case of the R-XSR this signal comes from the solder pad marked P. We now connect the single F.Port cable with a free UART. Details are shown in video now on the top right. The second option works fine for the R-XSR and F4 Flame Race. We use the uninverted signal from the soldering pad P and connected it to the UART3.
We now continue with the software. Let's go to the FrSky homepage. The link is in the description. www.frsky-rc.com/. If we search for F.Port, we will easily find out for which receivers there already is a F.Port firmware version available. It should work with any X model from FrSky (R-XSR, XSRF3PO, XSRF4O, XSRF4PO, XSR-M, XSR, X4R and X4RSB).Please take care, in some cases the firmware it is still a beta version. So, use at own risk. We have an R-XSR here, there is already an official release of the F.Port firmware.
Download the "F.Port PROTOCOL FRIMWARE", not the "normal" firmware. Please take in mind, with the F.Port firmware SBUS and S.Port do not work anymore, only F.Port. The redundancy function however stays unaffected. Download and save. How a firmware upgrade is done is show in the video now on the top right. For now, I we go through the process in fast forward.
Extract the firmware .zip and copy the .frk file to the SD card of the remote control. FCC for the international version. LBT for the EU version, depending on which firmware you have on your transmitter. Connect the FrSky Reveiver to the FrSky Taranis and start flashing. That's it for the RX. Of course you can reflash with the SBUS / S.Port firmware if necessary.
In the next step, we need a Betaflight version on the flight controller that supports F.Port. At the time of the video, the current version is a Betaflight 3.3.0 release candidate. Details on the firmware flashing and configuring Betaflight can be found here, the card is now in the upper right corner. We go though the process in fast forward. Plug in FC, flash in firmware in the firmware flasher tab. Done. In the Ports tab we select the UART to which we have connected our F.Port cable from the receiver.
Let's go to the config tab and select “Receiver Serial RX” and “FrSky F.Port” as protocol. The option is only available above version 3.2.5. Unfortunately, that was not all. We still need to hack a few more commands into the CLI. Or better, copy & paste from the description.
I have a F4 Flame Race in use. Other than the F3 and F7, it cannot handle the inverted signal. Therefore, depending on the method of the hardware wiring, we either have to invert via the software or activate half duplex.
If we use the inverted signal cable from the standard output, we set half duplex off and inversion on.
set serialrx_halfduplex = OFF
set serialrx_inverted = ON
Or, if we use the uninverted signal cable from soldering pad P - formerly S.Port - then we set halfduplex on and disable the software inversion.
set serialrx_halfduplex = ON
set serialrx_inverted = OFF
If you have a F3 or F7 you do not need to worry about inversion, it can be both set to ON.
set serialrx_halfduplex = ON
set serialrx_inverted = ON
Do not forget to save the settings with ”Save”. A note, the telemetry data must be rediscovered in the Frsky Taranis.
That’s it. We have now successfully set up the F.Port protocol. I’m thankful for thumbs up and especially I am happy if you subscribe to the cannel.
michael.o.navigator
Drohnen360: goo.gl/m776bm
Instagram: goo.gl/yaJC57
Twitter: goo.gl/xFTsv4
Facebook: goo.gl/DXYtx9
![✔ Избавляемся от проводов! Новый протокол от FRSky. Телеметрия, sbus, RSSI по одному проводу [FPORT]](/img/n.gif)
I'm on an F3 board and I was following the standard instructions and getting nowhere. Your 'If we use the inverted signal cable from the standard output, we set half duplex off and inversion on.' was what I needed and now my new RXSR works in Fport mode. Thanks!
Many thanks for this, good sir.
Thank you.
This video was helpful, keep it up, danke!
I've been trying for weeks to get tel on the hglrc f4 pro to work and nothing would work. I about gave up on this method too but soldering to the P pad worked and everything came to life! Thanks. Also im using Butterflight 3.4.2 if anyone was wondering if this would work with ButterFlight.
Id be curious how you did it....I've tried with the F428 and the Zeus and Fport / R-XSR with updated firmware to the FCC and BF 3.3.2. Nothing in receiver tab will respond. I've tried using the R-XSR telemetry wire from the harness as well as the uninvert hack "p". And all 4 combinations of (set serialrx_inverted = OFF / set serialrx_halfduplex = ON). It works find with resource remapping but I'd prefer to not have to use the plug for the Zeus board....
thnx!!!
When you say resource remapping you're talking about Softserial? Could you help me on that? I have tried the uninvert hack "p", but I've stupidly damaged the solder "p" pad and now my R-xsr doesn't have one anymore. So I'm looking for a solution. I use f4 hglrc F440
By remapping, I mean resource remapping, not soft serial. Go into the CLI and type "resource". You will see the resources. This was you can switch the resource mapping, (with limitations).
nice tutorial, why do you connect the green wire to tx3 and not on sbus pad? in my case the sbus is uart 6 , the uart 3 is used for ir tramp and uart 1 is free
the sbus pad (normally) has hardware inversion. a normal uart (w/o hardware anything) will work fine (w/o hacking or software inversion). that's the reason I chose TX3. In your case, I would recommend using uart 1 (TX1). You can also use TX6.
just as a remark: sbus is RX , receiving signal from the receiver. s.port ist TX for transmitting signal to the receiver. for f.port you need TX in (half-)duplex mode, not RX. (Ofc you can remap ressources in BF, but using the right soldering pads is the easiest approach).
I have r-xrs bound to x-lite it has soild green light, and when I unplug battery the radio says telemitry lost. When i plug it back in it says telemitry found. But in betaflight it has no stick or switch movement, and says arming disabled. I checked and it says, RXLOSS CLI MSP. Any help and I would be very greatfull!
Telemetry is one direction. Stick commands the other. It seems, your TX and RX are bound, but there is no working link between the RX and the FC.
So, it seems your F.Port Link between RX and FC do not work. Make sure the correct firmware is flashed (explicitly F.Port compatible firmware), the hardware connection is right (UART on FC, Port on the RX) and the FC Firware is configured correctly (F.Port Protocol, CLI Commands).
I have this exact same issue it's such a headache :( everything was wired up by a pro it's all solid and he was flying it but my qx 7 will only get telemetry but no stick inputs :( plz help
If you followed the video exactly, there is not much left to go wrong. First thing to try is, using another UART. Somethimes UARTs are shared, f.e. with LED Control or ESC Telemetry. Sometimes UARTs are hardware inverted, others are not. In my experience, it's rarely documented well, f.e. with the racepit mini, which is a great FC, but UART2 is shared with ESC Telemetry. I hooked Cam Control to it and wondered, why it would not work. This took me a while to figure out.
So, what I do in this case, go through the tutorial or manual again and double check if you wired everything right. Sometimes I just try to switch cables in case I (or the manual ;-)) mixed RX and TX up. Then I try a different UART. If that does not work, I replace the cables, in race cases they are broken.
If I am 100% sure the wiring should work, try software configuration. Try a different firmware version, or even firmware, just to rule that out. Try on another flight controller, to rule out that your FC has a defect, which may happen (more often than one my expect).
Thanks for the reply. It is wired up correctly flashed to fport firmware yadayada for some reason it only works on 1 wire mode? Not fport in the config tab so progress I guess? But now more confusion haha about to throw the fricken reciever in the dumps an buy a new one. Everything tested with another receiver works fine. It's just stuck with only working on one wire mode
hello, i tried to follow you tuto but it doesn't work. Can I solder the F port wire on the Sbus pad or do I have to do it on the RX1 or TX1 pad? Thanks a lot.
In all of my tests with different FC, the dedicated SBus soldering pad did not work. Also, the UART1 did only work for the controls, but not for telemetry, despite all variations of the CLI commands.
So, yes, in my experience, you have to use a free UART other than UART1 (at least for the F4 and F7 I used in my experiments).
In your video you left the S.Bus cable (white) connected to the FC pad but it's not necessary to have it still connected. I'm right ??
Thanks in advance
Yes, it's either or. White is the inverted F.Port signal cable, green is the uninverted F.Port signal cable.
Thanks for asking... that was the same question I had:)
I wired my Emax F4 mini magnum for sbus thinking rssi would work. I’m going to do fport procedure now. Can I leave the white wire S port in place while I test out fport?
hi
i have a emax hawk5 and i remove the mx+ and install the r-xsr so i just connect 3 wire to uart6 on the magnum f4 FC . (receiver s.port to TX in uart6) and .
i did all the rest in betaflight like your video . but the FC channels wont move in the Receiver tab?
what i am doing wrong here ? pls help
You need the uninverted S.Port Signal for F.Port to work, as well ast he F.Port Firmware on your Receiver. Did you do that?
Michael Orter Navigator
I did the software in the receiver with f port protocol. But i didn't do the uninvited pad signal.
I will try it tonight and let you know
Michael Orter Navigator
Thanks man its work now .
I have a Tmotor f7 HD board with the r9MX receiver, i have hooked up the F port wire to TX5 on the FC and set half duplex to On, and inverted to OFF but nothing is showing in betaflight. anyone know how to get this working as there isnt alot of info on the r9mx receiver on the internet and how to setup
Can this same thing be done with the HGLRC F438? Which pad do I solder the green wire too?
I suppose so. F.Port goes to any free and uninverted TX UART (not RX!). Do not forget to switch to half duplex when using F.Port.
This is great thank you. I only seem to get RSSI and battery, no other sensors are found. Is this correct? cheers :)
RSSI and battery comes directly from your receiver. So, you have bound transmitter and receiver successfully. But that's it. There seems to be no transmission between your flight controller and your receiver. If you are certain, that you have the F.Port firmware an your RX and the wiring is right, make sure the Setting on your FC (Config Tab, Receiver, Serial Based RX, FrSky F.Port) is set.
@@N4V1G4T0R im getting the same sort of thing, my rx is working as in the fc is seeing it and i can arm and do what i need to but the tx wont discover any sensors??
If you have F.Port signal working then it's all or nothing, it's a bidirectional signal (duplex). Other than S.Bus (from RX to FC for control) and S.Port (From RC to RX for telemetry) which work in one direction. If you do not discover any senors at all, then it's extremely strange, because your RX sends basic telemetry data, like RSSI and Voltage. At least the RX i know do that like the R-XSR and Crossfire Nano. Maybe you have a RX, that is not capable of telemetry?
If you only miss the telemetry from your FC, make sure that "Telemetry" is activated in the betaflight config tab.
@@N4V1G4T0R I do get rssi and Rx voltage but no sensors, telemetry is activated in inav, I have the R9 mini, maybe I'm just having compatibility issues?!?
The R9 should work as well. But, I am not sure about inav. Just to make sure, make a dump of your inav config, flash betaflight and check if it's working there.
So you're using the UART3, now what can you do with the SBUS UART? So are you actually freeing up a UART?
You can use the "SBUS" UART for anything you wan't. It's just another UART. ;-) With one minor difference, UART1 on F4 can normally handle the inverted signal. The other UARTS don't. (afaik)
I guess the inverter would only be on the RX portion of the UART huh? Sounds good!
I've installed and runs ok except the Lua Script for BF Pid config. Have you had the same problem?
I have not yet found the time to check out F.Port with LUA scipts.
hey, have you found the solution? I'm having the same issue.
hablo español, por si acaso.
Thanks Michael, I learned something else.
I have a problem though:
- FrSky Horus X12S
- FC F4 "hglrc xjb-f428-tx20.v2"
- R-xsr
- S.Port on the pad
- Uart 3
Everything works except to see RSSI on OSD!
No channel on Betaflight that can resemble an RSSI
I can see Volt-Fas also on the radio, so it works.
Can I or should I do some things to get the RSSI signal on OSD?
Thanks and congratulations.
If I understand you correctly, all you have to do is to send the RSSI Signal from your Transmitter back to the FC via one free channel (e.g. Channel 14). In the receiver tab, you assign that channel to RSSI (RSSI Channel e.g. AUX10). That's it. There are several videos on how to config your Transmitter. If not, just give me a call, I'll create one.
Today I try again and let you know! I think I'm working correctly, but I'm definitely missing something. I have to re-check the setting of the HalfDuplex on Betaflight, maybe that's it and I do not get the signal back! Thank you.
I sent you a help message on Facebook with a link to the photos I made of the setting. It seems to me all right but maybe I make some mistakes that escapes me! Thank you
ok, let me know the outcome. I'm curious.
The RSSI Signal is measured between RX and TX. So, it does not really have anything to do with F.Port, or S.Port. The three sensor data are sent from the receiver RX (the R-XSR i'm talking about) to the transmitter TX directly. Without the need of the FC telemetry to work.
Wow, I did it! Thanks to you I focused more on the radio: on FrSky FrOS there is a telemetry menu where set the range of values accepted: RSSI was the default 0-0; I set 0-100 and here is the magic RSSI returned from the radio! Many thanks Michael I will continue to follow your videos with much interest! Good night!
i'm having a hard time understanding it all. XD I have the same FC as in the video and want to use the TX6 pad for smarport which i understand is uart 6? What do i need to do? can't find any facts that the TX6 pad is linked to uart 6 and ore if i need uninverted signal or can i use inertion in cli? My bord is waterprooft so downt want to do any soldering.
FPORT did not show pids on my taranis with the xsr so i had to use sbus and rx invert hack to get lua to work
yes, you can use uart 6 for F.Port. This means, you have to connect the uninverted signal from the RX, which which will be your F.Port after the RX firmare flash, to TX6 on your FC.
when using f4 flight controller the only option is to use the uninverted smartport output? i followed your instructions to use the normal inverted output and set the first option that you show in the CLI and it didnt worked when soldering to a UART 6 TX (command changed to 5).
Yes, that is my experience, at least with that specific FC. Only the uninverted signal works. But that works on any UART I tried (1, 3, 6)
I also tried to use the inverted S.Port signal from the plug. I was able to get former S.Bus signal via F.Port. But I never got the telemetry to work, whatever settings I tried (BF inverted ON/OFF duplex ON/OFF in all combinations).
Thanks!
Same happens on my side
It's outdated now, the new firmware somehow combines both configurations in one file.
They fail to explain how to enable fport, so with the current firmware only employees of frsky know how to use fport. Other need to use old firmware.
When flashing do we use the S-port signal or the S-bus signal to flashing firmware to Taranis
S.Port
Nice, danke für das Video, konnte dank dir mit diesem Video einen RXSR weiter nutzen da ich das uninvertierte sbus pad abgebrochen habe (vermutlich beim letzten crash) 😅
Echt hilfreicher Content hier, lasse dir gern mal ein Abo + Like da 😉
Grüße SkyHogRC 🐷
Pls help, I got f-port on my r-xsr with x9d taranis with an omnibus f4 v3. I got it on tx3. I got rc working, but no telemetry. Any suggestions anyone? I've tried multiple times discover new sensors
Hello, ok, that should work. You obviously have the right firmware on your R-XSR.
Make sure you have telemetry activated in betaflight configuration tab.
If that's on, and still no telemetry, try the uninverted signal from the soldering Pad marked "P" on your R-XSR and connect it to TX3. Do not switch on Smartport or anything in the ports tab. But make sure UART3 has Serial RX activated (which you have, otherwise it would not work even for the rc.
If you have the uninverted F.Port signal, the correct settings should be
serialrx_provider = FPORT
set serialrx_inverted = OFF
set serialrx_halfduplex = ON
I hope that helps
Michael Orter Navigator Did anyone ever get this to work on Omnibus f4 v3? I was also only able to get rc to work but no telemetry. With the uninverted pad I get nothing. Tried all combinations of inverted/halfduplex settings in CLI to no avail.
So that green wire...if I dont do that it wont work with my transmitter huh
Can I connect sbus to sbus for rx signal and s.port to uart3 for telemetry or does that not work?
you can do that, sbus-sbus-uart and s.port to uart3. That's the "normal" way before F.Port.
If you use F.Port, you only need one cable for both, rx signal and telemetry.
@@N4V1G4T0R ok thx!
thx
Way too fast....
Thanks for the feedback. That is intentionally to have a short video with a lot of information. The compression rate prevents scrolling through endless "blabla" for the relevant information. So, a high density of information actually is a brandmark of my (newer) videos. Please, just do not watch them if you rather fast forward instead of making good use of the pause button.