JB; as you probably have seen. I had struggled this entire weekend trying to get the receiver configured. UGH! Even went out and purchased another RX thinking mine was AFU! This video solved my issue. Thank you so much! Now, I can call PriroFlipRC and tell them to cancel my order. Nah! I'll have a receiver to give to someone when they need one. I was given a whole bunch of free GOOD advice when I started. It's the least I can do to help another individual just starting out.
Hmm, this is cool. Joshua, please keep these great videos coming! I just did added SmartPort capability on a Flycolor S-Tower (F3), using Pin 6 of the PWM (10-Pin) connector to a FrSky XSR. Supposedly on this FC, if you use the supplied SmartPort pad, it's shared with the USB bus and complications ensue using them simultaneously, so better to use a free TX pin and SoftSerial. I'll have to try this F.Port mod soon, but since everything is working now, I'll wait. ;)
I guess that's the price for a massive, powerful, feature loaded piece of software that can run on even very simple (and cheap) electronics and can be controlled by just 6 buttons. When I got my Taranis I tried to not change anything that I had no clue of... that worked well for me.
Hahaha. Subjected to watching videos while I'm saving for my new build. Yes, I lost my 1st one. I think someone snagged it faster than I could get over to where it went down. But in my setup, I was having trouble with the telemetry. It kinda worked. This explains what I did wrong and how to set it up correctly. Thanks JB! Hense "FPV knowitall". Title well earned.
thx for the video. for anyone that this doesn't work. if you dont have a telem/sp labled pad and using a generic uart, make sure you're on the TX pad and not RX. If you are using an rxsr and a generic tx pad you will need to use the uninverted p pad on the rxsr to get telemetry to work
It's still not working for me on HGLRC XJB F428. I've tried all 4 combinations for inverted/half duplex as well as inverted and un-inverted hacks...No change. Not receiving any stick input on BF 3.3.2
Quick tip I love: long press on page button moves backward in the menus. So telemetry screen is easily accessible after short pressing menu then long pressing page. :)
Thanks for the great videos. I am using Inav 7.1.2, Frsky R-XSR with firmware Accst 2.1.1 Fport LBT (for Europe). My transmitter is the Radiomaster Zorro with 4 in 1 internal module. The Smart port (S Port) I am using to connect to the Speedybee F405 WING MINI is the uninverted S Port pad (letter P with bar on it) on the Frsky R-XSR. The ground, +, uninverted S Port from R-XSR all connected to the port listed as the TELEMETRY port with the GH 1.25 6 Pin connector (wire and connector was not included with my SpeedyBee F405WING MINI). The uninverted S Port from the Frsky Rxsr is connected t 0:15 o the TX2. Other than TX2 to uninverted SPort, + and ground there is nothing else connected, so the sbus cable from the receiver is not connected. On Inav it is not necessary to use the Soft Serial mode. On Inav: Ports section; Uart2 Serial RX is selected, on Configuration; Enable CPU based serial is NOT selected, Gps for telemetry and Telemetry output are selected, on Receiver section of Inav; Receiver type is Serial, Serial Receiver provider is FPORT, Serial port inverted is On and Serial Receiver half-duplex is set to Auto. I am receiving all telemetry just fine on the transmitter. PLEASE NOTE: SPEEDYBEE WEB SITE as of the date of this comment has the GH 1.25mm 6P connector listed upside down. In other words where it says 4v5 is actually the ground and where it says ground is the 4v5. The small brochure that came with the f405wing mini is correct but the web site is wrong as of the date of this comment so please pay special attention as this also changes the actual location of the TX2 pin.
Also, be careful not to accidentally enable PPM when first binding your receiver. Otherwise, you gonna have a bad time. On the R-XSR if your inputs do nothing in the receiver tab, check that you a blue led and a green led, both solid.
On your other F-port video you said you only need 3 wires from rxsr, how come here at 3:05 it shows you have 4 wires, the green still being connected to the sbus pad. I'm trying to connect an RSXR to a Talon F7, I can get my QX7 to bind to rx, but I can't get any stick inputs through betaflight and getting an RX_Failsafe error. Using Tx4 as my fport . Thanks for the video though it still helped answer a few other questions.
Joshua Bardwell, thank you sooo much for the quick response! i found my problem, must have read pinout wrong, but had signal wire connected to TX1 not TX4. Btw. since the quarantine, catching up on quad repairs, my newly made JB smoke stopper saved two different quads from magic smoke. Thanks again!!
Have never got telemetry to work on a F4 with a FrSky XRS. Have tried on a CLRacing F4S and RTFQ Freestyle F4. Considering changing this Quad to a Omnibus F3 which I have working a few older quads. Will try this f port first, thanks for this video.
Thanks for this video!! I feel like you made it just for me after our conversation about freeing UARTs for GPS. Regardless, thanks for the great info JB!!!
So cool Josh! I need one extra uart and run an x4r. I Can't wait to get home and give this a try. I can't say thanks enough. Going to start using your links for all my shopping! Thanks so much!
Great info. I got my r xsr hooked up to my kakute F7 (f port) and it works awesome. I did remove the sbus from the r xsr, Problem is the barometer on the F7 is now not recognized in betaflight and not showing. Any thought how to recover the baro?
Thanks Josh, was stuck for a while with a R-SXR on a babyhawk r pro. FC wasn't like anything in the manual and (Mini Magnum F4 v2 lite? ) I couldn't find any open pads for smartport, but fport is working on sbus wire. Awesome videos!! Thanks again.
Hi Joshua. First of all, I am very grateful for all the work you put into your videos. I gained a lot of useful knowledge from them! I have a rather unusual problem. My fc is AIRB/OMNIBUSF4SD(STM32F405) BF version 4.3.2 (it doesn't work at all on other newer BF versions) Radio X9D+ se, soft RF module XJT_ACCST_2.1.0_FCC FrSky XSR ACCST receiver (X4RXSR_ACCST_2.1.0_Fport_FCC) s.port not modified, connected to FC on a dedicated s.Bus pad. The controls in the receiver tab work (sliders move) but telemetry does not work. As for CLI, I checked all configurations. The set serialrx_inverted option doesn't change anything in my case. The set serialrx_halfduplex option must be set to OFF for the control to work. I'm at a loss because before updating to the latest BF version, everything worked fine, I had all the telemetry (it worked normally on software 3.2.2). I will be grateful for any help :] Regards !
So are you using F Port on all of your personal models? I ask as I'd imagine that it essentially halves your input signals now. Is that right? Or am I looking at it wrong?
I'm trying to use a Jumper R8II controller (which is like the R8 but has a duplex pin for RX/TX, plus Sbus RX port) to make LUA telemetry work on my TX16s.
Hey Joshua, I am using your RDQ F4-AIO, and the FrSky R-XSR. I have quadruple check my wiring, and it seems correct for the setup. In Betaflight I have set UART3 with Serial RX on, and UART 1 serial RX disabled. Receiver configuration is set as serial based and FrSky FPort. My XD9+ and the receiver are bound as indicated by the solid green light. On my transmitter my channels are set as AETR, and in the outputs they all put out the correct uS range when going through the throws. My problem is on the Betaflight screen when on and connected, my channels do not move. All channels are at 1500uS except throttle, Aux 13, and Aux 14. I am just coming over to FrSky from Spektrum, so there are quite a few new features to me. I also went through the New Taranis+ setup video to see of I was missing something on my initial radio setup. Edit: Using Betaflight 3.3.2, and configurator 10.2.0
Hi Joshua, thanks for all the great videos. Do you ever see issues binding for the first time with an f-port setup? I just set up an r-xsr on my matek f7 and I cannot get it to bind to my QX7. I am about to rewire it to s-bus and try again but I wanted to get your thoughts. All my firmware on my QX7, FC, and receiver are all up to date
spektrum did it like a year ago ;) glad to see the frsky guys catch up :) thinking of getting a qx7 to go alongside my dx8 gen 2 so I can get some crsf action going :D
Hi Joshua, I did my first build with Fport ... and it works great ...exept the Lua script ?!?! I did all the same you did in the video ... fpvdontknowitall :-) maybe you got a tip. btw F722 mini board with an RushTank and a R-xsr @ firmware November of 2019 ... I tried the 2.0 version ... can't bind it .. Taranis 9 is showing everthing except the Lua stuff .. regards Derek
I used to use the same model for all until recently as mid and end points would always be exact. Do you play with this? I imagine you could adjust it from with FC instead of controller if you wanted?
I'm seldom the first to review these things but I try to be as thorough as possible. My money would be on Stew to get the first video out as he seems to have connections to get product on the day of release and he is very quick to produce content about it.
@@lililililililili8667 On f-port or s-bus? Almost all the race pilots I fly with have crossfire for low latency. I am looking for those official latency numbers and see if it is worth buying crossfire or r9m for my taranis. I have x4 rsx-r on my race quads and want to know if f-port is worth it?
Anthony Jones before you tried the 4 possible cli config, was there no reactions in the reciever tab? Maybe I should try this. I gave up the whole thing eventually 🙄
Hey Joshua do you think it's possible use an r-xsr with fport firmware a gps and a tramp with telemetry with a mamba f405 flight controller? Great video, I learned something today, thanks!
You would need three UARTs for that. The Tramp Telemetry could be handled with softserial so only 2 hardware UARTs needed. The FPort requires a hardware inverter or you can use the RXSR P pad which outputs inverted smartport. I think probably it can be done.
Joshua Bardwell mh sad... but thank you soo much! You helped me so many times! w/o I would not have been able to get that damn drone up and running! Thank you
@@JoshuaBardwell I already did that. But I use fport for a reason. The reason is that the normal sbus doesn't work anymore. Also I wired the fport to the SBus pad on my F4 so that could be the problem
I WAS WORKING ON THIS YESTERDAY. Are you some sort of omnipotent quad-god? Either way, I got it working on one quad, and killed an RX trying to be smart and hook up the uninverted s.port pad to the sbus-in pin (on the RX, not on my FC.) so I could just use the connector. I don’t know if it’s just bricked or totally fried.
Joshua, I am having a very similar issue to @Snorkl FPV. I am brand new to FrSky from Spektrum as well. I have the R9M with the R9MM rx. I have it connected with the f-port pad on the RX and he sbus bad on my hobbywing omnibus f4. The RX responds and I can fly the kwad, but I get no Telemetry on my Qx7. Telemetry is enabled in BF and I do get RSSI, but that is it. I feel like I am missing something simple... Also I still want to send you a kwadgrabber!
@@JoshuaBardwell If there is no SmartPort pad on the FC, that means I would need a UART tx then right? in that case, would I need the "inverted s.port" pad on the RX?
Hey Josh. I'll be building my first quad later this summer. I have a Frsky X-Lite and an R-XSR on order and I'll be using an HGLRC F4 Flight controller+ESC combo. If I use the F-Port method, does this mean I won't have to do the uninvert/invert solder hack on the R-XSR's tiny solder pads? I haven't touched anything RC since the mid 80's when I raced 1/10 scale on/off road cars(a carbon fiber Predator) and buggies(Tamiya Hornet)with crystal radios,pot style servo controlled speed controls, and brushed motors(who remembers "Reedy" in a can? Haha I'm trying to do tons of research way ahead of my build(getting my ducks in a row) I'm so thankful for UA-cam and all your videos! I can't wait to get on a sim and then fly FPV!!
If the HGLRC F4 has a smartport pad then you do not need to do the uninvert hack. From the question, I am guessing it does not have a smartport pad, and then you have to do the uninvert hack.
When I got my X4RSB I was looking into using Fport because I have an F4 but I found the uninvert hack less of a hassle than flashing new firmware to the receiver.
Whats up bardwell? I need some help with getting my qx7 to work with my r-xsr. Im using the pyro f4 osd fc and flashed the firmware to the r-xsr for fport and lua scripts. Im bound to the rx and appear to get telemetry but dont get any stick movement in bf. I tried the tele pad and tx4 on the fc and neither worked. I've also tried the serialrx permutations in the cli. I'm new to taranis and not getting any help from my fb groups that I'm a member of. Please help me! Thanks bud
Dear Joshua, thanks for all you do for us. I finally succeeded to wire the f.port. I still have a question. As I use the tele pad for fport, I wanted to use the the sbus pad to wire a gps beitian bn220. For doing this a need a free rx tx. I currently use tx4 for my tramp, rx6 for esc telemetry. Is there a solution to wire it on your fc. By the way the design of your board is awesome. So easy to wire.....thanks. Florent from France. Take care....
The SBUS pad on my FC has a switchable inverter so you can use it as a generic RX. But the corresponding TX is not broken out so it's not as useful as you might prefer.
Joshua Bardwell think you can you please let us know or maybe do a video on if port on raceflight if they do support it that would be much appreciated thank you
Sorry out of topic.. I see you use a single coper wire, for your Rx wire... is it any special reason? which is better, compare to the common use 28AWG multi filament coper ? Thank you...
Have you ever seen where the Receiver tab isn't live but stutters? First time ever I have seen this. Just flashed my XSR to FPort since I needed to update it anyway. previous was SBus and I didn't see the issue then. Going to try and go back to see if it helps. Doesn't help I am on a Matek F405 AIO
Hey josh. Can you please do a video on the R9mm with the SpeedyBee fc please. I can’t figure this out any help would be great. Thanks man. Iv already download the software thanks again for what you do man.
@@JoshuaBardwell Confused... F.Port uses hardware inverted S.Port connection on Rx. Wired to FC via hardware inverted S.Port. I've read that F.Port solves inversion issue on F4 processors. Theoretically F.Port software could be written inverted then sent to S.Port and un inverted and no need for an invert on flight board. This is what I thought F.Port accomplished. Luv the KIA on yer OSD... lol and your vids I'm having lotta fun with this stuff.
Hey Bud! Thank you for all the videos you are always such a great help. Unfortunately I have not been able to bind my RXSR to my QX7. I've updated the firmware on my transmitter and have tried flashing almost all of the firmware updates for RXSR. I've tried all the ACCESS updates because thats what my transmitter asks for. The closest Ive gotten to binding is up to the register point but then it won't bind. This is my second receiver because i busted the first one which was a diatone msr. PLEASE HELP. Thank you very much!
How are the stock antennas on R-XSR? Is it a good idea to straight up just strip them to 33mm instead of leaving them however short they come out of the box?
R9MM should be currently F_PORT enabled right? And the pin should be the same for S_PORT... (trying to understand how to wire it up on my Matek F405-CTR)
You can do exactly as you see here with R9MM. It does support FPort. The main advantage of R9MM is that it also has an inverted S.Port pin if your FC doesn't have an inverted UART for SmartPort or FPort. If you use the inverted S.Port pin you must go into the CLI and type set serialrx_inverted=on (if you are using FPort) set tlm_inverted=on (if you are using SmartPort) save
@@JoshuaBardwell thanks a lot for your reply. Unfortunately I've got a quite bigger problem... I've bought a Jumper T12 basically for the form factor since my FPV backpack is not that big. In order to make long range (as an upgrade for my Flysky FS-i6) I've also bought a Frsky module R9M plus R9MM receivers. When I go through the binding procedure, if I select and execute the "Bnd" command (page 2 of model pages) it does not blink or make any sound either... Really don't know what to do since if I use the crappy multimodule shipped with the T12 itself, binding command does work correctly (blinking and beeping while looking for a receiver). Thanks again anyway, cheers.
Hey Joshua, thanks for all great videos, they are really great when you are new to this hobby, even me as an embedded software engineer for two decades stumble on these things sometimes. I have a question about this, which may be to specific, IDK. I have a Diatone GT M530, which has their Mamba F405 FC. It's good, but it's woefully lacking in documentation. It has three UARTs, none of them specifically labeled for a specific use - I've been able to discern that UART1 seems to be able to handle inverted signals since I can hook S.Bus directly to it and it works: So currently I have S.Bus at UART1 and SmartAudio on UART3. For SmartPort I had to solder a wire to the non-inverted pad on my R-XSR receiver, It had me scratching my head for a while since it got delivered with a harness wired up seemingly to fit an R-XSR, but with SmartPort going to the normal, inverted SmartPort pin on the receiver. Anyways, given this FC, which has no Telemetry/SmartPort/Whatever name for an inverted UART, do you think F-Port would work if wired to UART1, which now is wired to S.Bus without any external inversion? Cheers
This is a good question, and would answer my dilemma also with the DYS F4 Pro V2 ..... Should we just flash F.Port FW to R-XSR , then connect the S.Port wire from R-XSR to the same TX-1 pad that is working out of the box with Sbus ??? (And modify BetaFlight etc) But as it's an old video, I don't think Joshua Barwell will hear our cry's in the wilderness that is UA-cam. He must get literally thousands of notifications every day :) Joshuaaaaaa ;)
hi JB, what I'm missing. I have no telemetry apart from RxBt and RSSI after Discover new sensors. I've installed an R9 MM with latest firm FLEX_20190201. and OpenTx 2.2.3 on my Taranis Qx7. The channels are working great. The problem is the lack of sensors in the telemetry
Thank you for your fast answer. I have flashed FLEX_20190201 on R9 MM and R9M_FLEX in the TX module (Taranis QX7). My FC is a HAKRC Flying F4 v3. I have telemetry selected in BF. I don't have UART selected because I'm using F.port. Is it necessary to assign UART with F.PORT? I'm using the S.PORT/F.POT pin on R9 MM.
My guess is the port you're using only has a unidirectional inverter. Did you use the Smartport telemetry pad on the FC? Have you tried adjusting tlm_halfduplex?
Joshua Bardwell I haven’t tried the inverted pad - I have tried all different variations of the inverted and halfduplex settings - as soon as you change any of those settings the RC stops working - tomorrow I’ll try the s-port inverted pad tomorrow and see how it goes - thanks so much for writing back yet again mate !!
On the New Mamba F411 AIO 25A ESC, they have both, RC tx pad and Inverted pad(s.port) on UART 1. Do I have to desolder the RC signal for f port to work?
what I use and also recommend is to use the normal Sbus protocol on its pad and in addition to that, use SoftSerial for SmartPort-Telemetry. SoftSerial is great, but it's a bad idea to use it with a receiver.
I don't think betaflight will allow serail rx over softserial. If they do allow it, you shouldn't do it. Does your F4 board not have a smartport or telemetry pad to use? Most do these days.
I tried Fport on a quad a couple months ago. X4RSB rx and Beerotor F4 fc. RSSI displayed really low numbers but the quad flew fine, for a couple minutes, then it just dropped out of the sky. I was only a couple hundred yards away and had been farther.
Joshua I added a r-xsr to my babyhawk r. I watched 3 of ur videos to help so I upgraded firmware and setup fport. I get rssi and rxbt telemetry and it works but I cannot at all arm the quad or setup switched on betaflight. I did cli status and just says RXLOSS. not sure what i missed since u am getting telemetry signal I know it's wired correct. thx!
I have f port working soldered on the pad on r-xsr and have serial rx UART 1 and connect that wire to sbus on mamba f405 mini. In your reciever tab you have telemetry set to aux 3. It's that because you're using uart3 or... What? I don't know what to set that aux to. I have an x-lite so I need to do something with that? I get rssi and vbat but don't know if I'm missing something out...? I also did nothing with inversion. I have no clue about that. It works and flies so it didn't fry anything...
@@JoshuaBardwellThanks for the reply. On the mini mamba or any other f4 fc I've come across there's never been a pinout titled 'smartbus' so I guess I'm not understanding it. In the ports tab I need to select and solder to the corresponding UART port and just select serial rx. And not select smartport on that selected port. Currently it's working as far as I can tell going through sbus. It flies and I have telemetry. Is betaflight not telling the fc that the sbus port is being used as fport in the configuration tab? goo.gl/images/qbJqnP
great video as always. i tryed this without any luck for days. I ended up flashing an older Fport firmwate for my R-XSR and it worked! dont know why the latest FW-RXSR-ACCST_v191112 didnt work know matter what i did. Any ideas?
Yes. Do just like I showed in the video. Connect the SmartPort wire to the Telemetry pad on your FC. The Telemetry pad will have a bidirectional inverter and Fport will work. Or if you are using F3 or F7, use any UART TX pad because they can handle inversion no problem.
However, for an F4 board with no telemetry pad, you are stuck. You would have to cut the trace from the inverter to the jack and solder a bypass wire. Possible, but not at all easy (no instructions given on how to do this - and you cannot just bridge the inverter).
Just saw this question because I may have to do the hack. You may be able to desolder the plug, cut the smartport pin off flush with the plug, resolder the plug to the board, then solder a short jumper wire from the backside of the pin to the P pad. However this may prevent you from flashing firmware since the normal smartport connection is necessary for flashing. Doesn't avoid soldering to the tiny P pad but makes for a cleaner install. A lot of work and better have skills soldering. Lol
I found a R9MM, flashed the firmware R9Mini_FCC_Fport.frk, and connected the Inverted SPort to TX1 on a new F411-Wing (flashed with the F411 softserial firmware). I set Fport as the serial receiver source in iNav, and now the Taranis X9D works the channels on the Receiver tab in iNav. However, I can't get the telemetry to work. My R9M is flashed with R9M_FCC.frk, version 20190117. Per the Matek Fport page, I have entered: set serialrx_provider = FPORT set serialrx_inverted = ON set serialrx_halfduplex = ON Per Oscar Liang, I have also tried turning serialrx_halfduplex off and on again. Same with serialrx_inverted. I have gone to the Taranis telemetry page, deleted all sensors, but when I choose Discover New Sensors, it doesn't find any. Does anyone see what I'm doing wrong?
I finally got it working by going to an earlier version of the F411-WING firmware and trying a newer version of the R9MM firmware. Thanks for your reply!
I wonder if Joshua or anybody else can help. My new Archer GR8 receiver does not allow me to plug a sensor using the standard servo plug anymore. I had it working with the pre-ACCESS RX8R Pro as the Smart Port plug was for standard servo plugs. Do I have to use that new 4-pins F.Port connection now? If so, I guess I need to change the plug on the sensor side. Just a bit unsure, as it is, as usual, difficult to get clear info from FrSky. Any help is highly appreciated.
So I’m wondering should I try to reflash the rxsr receivers or should I update the firmware on my x lite radio And see if that helps me connect and get good signal out of the receivers
Hello Mr Bardwell I have your first f4 FC and using R XSR f.port. I got f.port to work I had to turn off halfduplex and invert both off. My question is can I use the sbus pad for smart audio sadly I burned off my tx4
SBUS pad is rx. SmartAudio needs TX. That's a no go. You can use ledstrip remapped to softserial. Instructions are in the Troubleshooting section of the manual.
Hello Josh, im new to open tx after yrs of spectrum im trying to get a 5 inch setup qx7 the receiver your using in this video. I have the lux V2 FC. I wired the rec as you described. My problem is i cant get the rec. tab in BF to work. On the lux v2 the serial rx is uart 4 the tx is uart 5 i have the serial turned on uart 4 and in config i have serial rx and sbus on, is that wrong?
Hey Josh, when you bind an F port RXSR reciever, do you do it in accst d16 or in access? I have the firmware updated but it wont bind for some reason.. Thanks man!!
Hi, quick question if I understood correctly, on f4 like JB AIO, connect the smart port wire after flashing to fport to the T on the f4 board? Thanks !
Flashed my rxsr and my qx7s accst. Works for that particular drone, but now none of my other drones will bind to that transmitter. They are all xm+ and a Mobula 6. What do I do to get them to work again?
I have an x-lite running opentx 2.2.4 and a crazybee F4 board trying to add an R-XSR. I can bind and fly the quad using sbus with the rxsr firmware 191112, but when I flash the fport firmware 191128 I can bind but I can't get activity in the receivers tab. I'm using the "inverted" pad on the R-XSR and set serial inverted off as well as half duplex on. Telemetry is turned on in betaflight as well as fport is selected as the protocol. Not sure if i'm missing something...
Hi joshua Jumper r1 f-port receiver fault as on most i have seen online when binding both lights light up but you have green led on outer edge of board and red on inner which flashes in bind mode and green goes solid after power cycle the receiver i have was got last week and when i put in bind mode red is on outer edge of board and green on inner when binding green light flashes and after power cycle red light goes solid it seems to be connected Another point was to get it to bind i had to change RF fine tune freq to -15 it will not bind at RF fine freq at 0 should i trust this receiver i have heard of other people having problems with bind procedures on this reciver
In the FrSky firmware downloads it says "4:Redundancy function is still valid;". So it will still have SOME function but there is no information how it works exactly.
Yes it still works. The question is, what happens when the receiver failsafes over? Does it pass through SBUS or does it convert to FPort? You can test it and let us know!
Joshua Bardwell yes I will test this tonight or tomorrow with my x8r. Because I only have one x9d my test will be to hook everything up and then set model 01 to r-xsr and model 02 to the x8r, then switch between the selected receivers.
If you flash F.Port firmware to the R-XSR, S-Bus is not longer transmitted on the S-Bus wire. This is from experience. Both Firmware 180111 and 180228 disable S-Bus output.
So my setup never worked after flashing the FC and the r-xsr...I couldn't get fport to work with all inverted/uninverted hacks and inverted/halfduplex. I was able to simply re-wire my sbus wire and it worked immediately after changing back from Fport to sbus
If you didn't change the wiring from an old board, that was set up for Sbus and Smart Port telemetry, then you didn't save any UARTs because you would have had it wired to use two different UARTs in the first place, right?
Is there any drawback for using this like increase of latency since now 2 types of signals are being communicated with the same wire? This seems just too good to be true?
Thank you Joshua for this video. I'm having an issue. I have FLirt working and seem to have telemetry working "sort of" 😲 Since my craft is down and out awaiting a new FPV camera. I decided to upgrade my TX "SE Plus" to the latest firmware as well and as I stated, everything seemed to work just fine. I was able to see all the lua menu screens and the vtx screen. But now for some reason I get that annoying syntax error / out of memory error just before I get to the vtx settings. Any clue how to fix this. Thank you in advance for any input.
Joshua if I flash my X4R-SB for F.Port will I still be able to use the original SBUS connection on the end of the receiver for controlling a gimbal for example?
JB; as you probably have seen. I had struggled this entire weekend trying to get the receiver configured. UGH! Even went out and purchased another RX thinking mine was AFU! This video solved my issue. Thank you so much! Now, I can call PriroFlipRC and tell them to cancel my order. Nah! I'll have a receiver to give to someone when they need one. I was given a whole bunch of free GOOD advice when I started. It's the least I can do to help another individual just starting out.
YES the intro is back, I'm so happy.
Bought some R-XSR last week, this "HOW TO" video is on point ! :D
Thank you Joshua from the past. This video saved me a lot of time.
Hmm, this is cool. Joshua, please keep these great videos coming!
I just did added SmartPort capability on a Flycolor S-Tower (F3), using Pin 6 of the PWM (10-Pin) connector to a FrSky XSR. Supposedly on this FC, if you use the supplied SmartPort pad, it's shared with the USB bus and complications ensue using them simultaneously, so better to use a free TX pin and SoftSerial.
I'll have to try this F.Port mod soon, but since everything is working now, I'll wait. ;)
Holy moly, opentx looks so complicated, each time you are trying to setup anything. So Many menues and setup options
I guess that's the price for a massive, powerful, feature loaded piece of software that can run on even very simple (and cheap) electronics and can be controlled by just 6 buttons. When I got my Taranis I tried to not change anything that I had no clue of... that worked well for me.
Hahaha. Subjected to watching videos while I'm saving for my new build. Yes, I lost my 1st one. I think someone snagged it faster than I could get over to where it went down. But in my setup, I was having trouble with the telemetry. It kinda worked. This explains what I did wrong and how to set it up correctly. Thanks JB! Hense "FPV knowitall". Title well earned.
thx for the video. for anyone that this doesn't work. if you dont have a telem/sp labled pad and using a generic uart, make sure you're on the TX pad and not RX. If you are using an rxsr and a generic tx pad you will need to use the uninverted p pad on the rxsr to get telemetry to work
It's still not working for me on HGLRC XJB F428. I've tried all 4 combinations for inverted/half duplex as well as inverted and un-inverted hacks...No change. Not receiving any stick input on BF 3.3.2
Nevin, i had the same problem, you have to disable serial on the sbus ,
Quick tip I love: long press on page button moves backward in the menus. So telemetry screen is easily accessible after short pressing menu then long pressing page. :)
Thanks for the great videos. I am using Inav 7.1.2, Frsky R-XSR with firmware Accst 2.1.1 Fport LBT (for Europe). My transmitter is the Radiomaster Zorro with 4 in 1 internal module. The Smart port (S Port) I am using to connect to the Speedybee F405 WING MINI is the uninverted S Port pad (letter P with bar on it) on the Frsky R-XSR. The ground, +, uninverted S Port from R-XSR all connected to the port listed as the TELEMETRY port with the GH 1.25 6 Pin connector (wire and connector was not included with my SpeedyBee F405WING MINI). The uninverted S Port from the Frsky Rxsr is connected t 0:15 o the TX2. Other than TX2 to uninverted SPort, + and ground there is nothing else connected, so the sbus cable from the receiver is not connected. On Inav it is not necessary to use the Soft Serial mode. On Inav: Ports section; Uart2 Serial RX is selected, on Configuration; Enable CPU based serial is NOT selected, Gps for telemetry and Telemetry output are selected, on Receiver section of Inav; Receiver type is Serial, Serial Receiver provider is FPORT, Serial port inverted is On and Serial Receiver half-duplex is set to Auto. I am receiving all telemetry just fine on the transmitter. PLEASE NOTE: SPEEDYBEE WEB SITE as of the date of this comment has the GH 1.25mm 6P connector listed upside down. In other words where it says 4v5 is actually the ground and where it says ground is the 4v5. The small brochure that came with the f405wing mini is correct but the web site is wrong as of the date of this comment so please pay special attention as this also changes the actual location of the TX2 pin.
Great video. This is super exciting news about Fport. I'll be trying this tonight. Fingers-crossed.
worked! had to try each serial Rx for all UART ports until i got live receiver values in betaflight !
Also, be careful not to accidentally enable PPM when first binding your receiver. Otherwise, you gonna have a bad time. On the R-XSR if your inputs do nothing in the receiver tab, check that you a blue led and a green led, both solid.
Dude, THANK YOU, have been troubleshooting for the past two hours trying to get my receiver bars to do something in Betaflight, working great now!
Is that cppm on the receiver? Mines off and I'm still not getting stuck inputs in BF
On your other F-port video you said you only need 3 wires from rxsr, how come here at 3:05 it shows you have 4 wires, the green still being connected to the sbus pad. I'm trying to connect an RSXR to a Talon F7, I can get my QX7 to bind to rx, but I can't get any stick inputs through betaflight and getting an RX_Failsafe error. Using Tx4 as my fport . Thanks for the video though it still helped answer a few other questions.
I left it connected since there was not benefit to removing it. I was originally running SBUS and it was required.
Joshua Bardwell, thank you sooo much for the quick response! i found my problem, must have read pinout wrong, but had signal wire connected to TX1 not TX4. Btw. since the quarantine, catching up on quad repairs, my newly made JB smoke stopper saved two different quads from magic smoke. Thanks again!!
Have never got telemetry to work on a F4 with a FrSky XRS. Have tried on a CLRacing F4S and RTFQ Freestyle F4. Considering changing this Quad to a Omnibus F3 which I have working a few older quads. Will try this f port first, thanks for this video.
Thanks for this video!! I feel like you made it just for me after our conversation about freeing UARTs for GPS. Regardless, thanks for the great info JB!!!
So cool Josh! I need one extra uart and run an x4r. I Can't wait to get home and give this a try. I can't say thanks enough. Going to start using your links for all my shopping! Thanks so much!
Thx. for sharing great inf. but i just wanna know does it make the latency slower than before? If it is not, this is pretty much cool!
It's supposedly a little slower than S.Bus but most people probably won't notice.
Great info. I got my r xsr hooked up to my kakute F7 (f port) and it works awesome. I did remove the sbus from the r xsr, Problem is the barometer on the F7 is now not recognized in betaflight and not showing. Any thought how to recover the baro?
Thanks Josh, was stuck for a while with a R-SXR on a babyhawk r pro. FC wasn't like anything in the manual and (Mini Magnum F4 v2 lite? ) I couldn't find any open pads for smartport, but fport is working on sbus wire. Awesome videos!! Thanks again.
Awesome, Joshua! Great info! 😊
Hi Joshua.
First of all, I am very grateful for all the work you put into your videos. I gained a lot of useful knowledge from them!
I have a rather unusual problem.
My fc is AIRB/OMNIBUSF4SD(STM32F405) BF version 4.3.2 (it doesn't work at all on other newer BF versions)
Radio X9D+ se, soft RF module XJT_ACCST_2.1.0_FCC
FrSky XSR ACCST receiver (X4RXSR_ACCST_2.1.0_Fport_FCC) s.port not modified, connected to FC on a dedicated s.Bus pad.
The controls in the receiver tab work (sliders move) but telemetry does not work.
As for CLI, I checked all configurations.
The set serialrx_inverted option doesn't change anything in my case.
The set serialrx_halfduplex option must be set to OFF for the control to work.
I'm at a loss because before updating to the latest BF version, everything worked fine, I had all the telemetry (it worked normally on software 3.2.2).
I will be grateful for any help :]
Regards !
So are you using F Port on all of your personal models? I ask as I'd imagine that it essentially halves your input signals now. Is that right? Or am I looking at it wrong?
A bit off-topic here but damn look at those perfect solder joints, haha
Credit where credit is due: Armattan built this quad.
While adequate, they are far from perfect. The green wire is about the only one that does not have excessive solder.
I'm trying to use a Jumper R8II controller (which is like the R8 but has a duplex pin for RX/TX, plus Sbus RX port) to make LUA telemetry work on my TX16s.
Hey Joshua, I am using your RDQ F4-AIO, and the FrSky R-XSR. I have quadruple check my wiring, and it seems correct for the setup. In Betaflight I have set UART3 with Serial RX on, and UART 1 serial RX disabled. Receiver configuration is set as serial based and FrSky FPort. My XD9+ and the receiver are bound as indicated by the solid green light. On my transmitter my channels are set as AETR, and in the outputs they all put out the correct uS range when going through the throws. My problem is on the Betaflight screen when on and connected, my channels do not move. All channels are at 1500uS except throttle, Aux 13, and Aux 14. I am just coming over to FrSky from Spektrum, so there are quite a few new features to me. I also went through the New Taranis+ setup video to see of I was missing something on my initial radio setup. Edit: Using Betaflight 3.3.2, and configurator 10.2.0
Hi Joshua, thanks for all the great videos. Do you ever see issues binding for the first time with an f-port setup? I just set up an r-xsr on my matek f7 and I cannot get it to bind to my QX7. I am about to rewire it to s-bus and try again but I wanted to get your thoughts. All my firmware on my QX7, FC, and receiver are all up to date
I figured it out! Needed to update internal XJT module. Didn’t realize that was a thing. Hope this helps someone else.
Excellent video. did you also remove the sbus wire from the harness.
I didn't. But it's not hurting anything.
Finally got it working on a r-xsr and omnibus f4 v3... solder the p tab on the r-xsr and connect it to header rx1 for uart1
set serialrx_halfduplex = OFF got rx to work.
set tlm_inverted = OFF
Set tlm_halfduplex = OFF
got telemetry to work.
Thanks JB
Glad you got it working!
spektrum did it like a year ago ;) glad to see the frsky guys catch up :) thinking of getting a qx7 to go alongside my dx8 gen 2 so I can get some crsf action going :D
Hi Joshua, I did my first build with Fport ... and it works great ...exept the Lua script ?!?! I did all the same you did in the video ... fpvdontknowitall :-) maybe you got a tip. btw F722 mini board with an RushTank and a R-xsr @ firmware November of 2019 ... I tried the 2.0 version ... can't bind it .. Taranis 9 is showing everthing except the Lua stuff .. regards Derek
I used to use the same model for all until recently as mid and end points would always be exact.
Do you play with this? I imagine you could adjust it from with FC instead of controller if you wanted?
hey can you make sure you are one of the first to review the ev200 eachine goggles when they come out, they actually don't look half bad
I'm seldom the first to review these things but I try to be as thorough as possible. My money would be on Stew to get the first video out as he seems to have connections to get product on the day of release and he is very quick to produce content about it.
thanks man
Wonder how much effect it has on latency?
suposedly its suposed to be the same latency, around 20ms or so
I'm interested as well. Is there a Latency difference between F-Port an SBUS ?
@@lililililililili8667 On f-port or s-bus? Almost all the race pilots I fly with have crossfire for low latency. I am looking for those official latency numbers and see if it is worth buying crossfire or r9m for my taranis. I have x4 rsx-r on my race quads and want to know if f-port is worth it?
Trying the 4 possible configurations in cli finally fixed my issue with my newest build. Thank you =]
Anthony Jones before you tried the 4 possible cli config, was there no reactions in the reciever tab? Maybe I should try this. I gave up the whole thing eventually 🙄
@@christera2686 I believe there were no reactions, hope it works
Hey Joshua do you think it's possible use an r-xsr with fport firmware a gps and a tramp with telemetry with a mamba f405 flight controller? Great video, I learned something today, thanks!
You would need three UARTs for that. The Tramp Telemetry could be handled with softserial so only 2 hardware UARTs needed. The FPort requires a hardware inverter or you can use the RXSR P pad which outputs inverted smartport. I think probably it can be done.
Can I do this same thing using Mission Planner? I can't get betaflight connected to my PX4.
Will it work with a xm+?
No. There is no FPort firmware for XM+.
Joshua Bardwell mh sad... but thank you soo much! You helped me so many times! w/o I would not have been able to get that damn drone up and running! Thank you
Can't get the Lua working on fport. I'm also only got rssi and rxbt
Go to telemetry screen in the Taranis and "discover new sensors".
@@JoshuaBardwell I already did that. But I use fport for a reason. The reason is that the normal sbus doesn't work anymore. Also I wired the fport to the SBus pad on my F4 so that could be the problem
@@JoshuaBardwell tryed that , but no new sensors shows up :/
I WAS WORKING ON THIS YESTERDAY. Are you some sort of omnipotent quad-god? Either way, I got it working on one quad, and killed an RX trying to be smart and hook up the uninverted s.port pad to the sbus-in pin (on the RX, not on my FC.) so I could just use the connector. I don’t know if it’s just bricked or totally fried.
Great video as always!!! What if I use the uninverted SmartPort pad on the R-XSR and wire it to a TX pad of an F4 FC??
Did that work?
@@JeffreyJudy yes
Joshua, I am having a very similar issue to @Snorkl FPV. I am brand new to FrSky from Spektrum as well. I have the R9M with the R9MM rx. I have it connected with the f-port pad on the RX and he sbus bad on my hobbywing omnibus f4. The RX responds and I can fly the kwad, but I get no Telemetry on my Qx7. Telemetry is enabled in BF and I do get RSSI, but that is it. I feel like I am missing something simple... Also I still want to send you a kwadgrabber!
The SBUS pad is receive only. You need to use the SmartPort pad on the FC.
@@JoshuaBardwell If there is no SmartPort pad on the FC, that means I would need a UART tx then right? in that case, would I need the "inverted s.port" pad on the RX?
Hey Josh. I'll be building my first quad later this summer. I have a Frsky X-Lite and an R-XSR on order and I'll be using an HGLRC F4 Flight controller+ESC combo. If I use the F-Port method, does this mean I won't have to do the uninvert/invert solder hack on the R-XSR's tiny solder pads? I haven't touched anything RC since the mid 80's when I raced 1/10 scale on/off road cars(a carbon fiber Predator) and buggies(Tamiya Hornet)with crystal radios,pot style servo controlled speed controls, and brushed motors(who remembers "Reedy" in a can? Haha I'm trying to do tons of research way ahead of my build(getting my ducks in a row) I'm so thankful for UA-cam and all your videos! I can't wait to get on a sim and then fly FPV!!
If the HGLRC F4 has a smartport pad then you do not need to do the uninvert hack.
From the question, I am guessing it does not have a smartport pad, and then you have to do the uninvert hack.
So, you don't have to select the telemetry option for your uart in the ports tab? Is that done automatically?
Correct.
@@JoshuaBardwell Thank you sir!
When I got my X4RSB I was looking into using Fport because I have an F4 but I found the uninvert hack less of a hassle than flashing new firmware to the receiver.
Whats up bardwell? I need some help with getting my qx7 to work with my r-xsr. Im using the pyro f4 osd fc and flashed the firmware to the r-xsr for fport and lua scripts. Im bound to the rx and appear to get telemetry but dont get any stick movement in bf. I tried the tele pad and tx4 on the fc and neither worked. I've also tried the serialrx permutations in the cli. I'm new to taranis and not getting any help from my fb groups that I'm a member of. Please help me! Thanks bud
Hi JB, Great video!! Wondering if Fport can be connected to SBUS pad of a F4 board?
No. TX pad only, with bidirectional inverter. SmartPort is the most likely choice to work.
Dear Joshua, thanks for all you do for us. I finally succeeded to wire the f.port. I still have a question. As I use the tele pad for fport, I wanted to use the the sbus pad to wire a gps beitian bn220. For doing this a need a free rx tx. I currently use tx4 for my tramp, rx6 for esc telemetry. Is there a solution to wire it on your fc. By the way the design of your board is awesome. So easy to wire.....thanks. Florent from France. Take care....
The SBUS pad on my FC has a switchable inverter so you can use it as a generic RX. But the corresponding TX is not broken out so it's not as useful as you might prefer.
Hey Joshua will this work on raceflight
Have to ask the raceflight devs if they support Fport. I don't know.
Joshua Bardwell think you can you please let us know or maybe do a video on if port on raceflight if they do support it that would be much appreciated thank you
Joshua, I read somewhere in the documentation that receiver #0 is not recommended, have you had any issues?
Zero issues whatsoever.
Sorry out of topic..
I see you use a single coper wire, for your Rx wire... is it any special reason?
which is better, compare to the common use 28AWG multi filament coper ?
Thank you...
Canb we get rssi to osd with f.port?
Have you ever seen where the Receiver tab isn't live but stutters? First time ever I have seen this. Just flashed my XSR to FPort since I needed to update it anyway. previous was SBus and I didn't see the issue then. Going to try and go back to see if it helps. Doesn't help I am on a Matek F405 AIO
Went back to SBus and SmartPort config = back to normal. Not too bad because I was already wired this way.
I like the display page Vfas setting I am going to set that up, thanks Josh
Saved me much annoyance, thanks man. :)
thank you very much 👍😁🙏👍❤
Thank you :D
is it still worth it to use f.port nowadays ? I still see everyone using sbus on betaflight
Hey josh. Can you please do a video on the R9mm with the SpeedyBee fc please. I can’t figure this out any help would be great. Thanks man. Iv already download the software thanks again for what you do man.
Hey KIA... is Fport inverted...?
Yes.
@@JoshuaBardwell Confused... F.Port uses hardware inverted S.Port connection on Rx. Wired to FC via hardware inverted S.Port. I've read that F.Port solves inversion issue on F4 processors. Theoretically F.Port software could be written inverted then sent to S.Port and un inverted and no need for an invert on flight board. This is what I thought F.Port accomplished. Luv the KIA on yer OSD... lol and your vids I'm having lotta fun with this stuff.
Yikes that seemed like more of a rant than question... thx to Samuel Adams.
Can you please make a radiomaster zorro yaapu vid???
Saved me with this one!
got my r9mm working on s port on an omnibus f4 FC had to use the cli commands. wonderfail range had failsafe at well under 100m
Hey Bud! Thank you for all the videos you are always such a great help. Unfortunately I have not been able to bind my RXSR to my QX7. I've updated the firmware on my transmitter and have tried flashing almost all of the firmware updates for RXSR. I've tried all the ACCESS updates because thats what my transmitter asks for. The closest Ive gotten to binding is up to the register point but then it won't bind. This is my second receiver because i busted the first one which was a diatone msr. PLEASE HELP. Thank you very much!
2020 calling, can we have f-port standard now please.
How are the stock antennas on R-XSR? Is it a good idea to straight up just strip them to 33mm instead of leaving them however short they come out of the box?
ua-cam.com/video/8nFkRks2dOs/v-deo.html
R9MM should be currently F_PORT enabled right? And the pin should be the same for S_PORT... (trying to understand how to wire it up on my Matek F405-CTR)
You can do exactly as you see here with R9MM. It does support FPort. The main advantage of R9MM is that it also has an inverted S.Port pin if your FC doesn't have an inverted UART for SmartPort or FPort. If you use the inverted S.Port pin you must go into the CLI and type
set serialrx_inverted=on (if you are using FPort)
set tlm_inverted=on (if you are using SmartPort)
save
@@JoshuaBardwell thanks a lot for your reply. Unfortunately I've got a quite bigger problem... I've bought a Jumper T12 basically for the form factor since my FPV backpack is not that big.
In order to make long range (as an upgrade for my Flysky FS-i6) I've also bought a Frsky module R9M plus R9MM receivers.
When I go through the binding procedure, if I select and execute the "Bnd" command (page 2 of model pages) it does not blink or make any sound either...
Really don't know what to do since if I use the crappy multimodule shipped with the T12 itself, binding command does work correctly (blinking and beeping while looking for a receiver).
Thanks again anyway, cheers.
Hey Joshua, thanks for all great videos, they are really great when you are new to this hobby, even me as an embedded software engineer for two decades stumble on these things sometimes. I have a question about this, which may be to specific, IDK. I have a Diatone GT M530, which has their Mamba F405 FC. It's good, but it's woefully lacking in documentation. It has three UARTs, none of them specifically labeled for a specific use - I've been able to discern that UART1 seems to be able to handle inverted signals since I can hook S.Bus directly to it and it works: So currently I have S.Bus at UART1 and SmartAudio on UART3. For SmartPort I had to solder a wire to the non-inverted pad on my R-XSR receiver, It had me scratching my head for a while since it got delivered with a harness wired up seemingly to fit an R-XSR, but with SmartPort going to the normal, inverted SmartPort pin on the receiver.
Anyways, given this FC, which has no Telemetry/SmartPort/Whatever name for an inverted UART, do you think F-Port would work if wired to UART1, which now is wired to S.Bus without any external inversion?
Cheers
This is a good question, and would answer my dilemma also with the DYS F4 Pro V2 ..... Should we just flash F.Port FW to R-XSR , then connect the S.Port wire from R-XSR to the same TX-1 pad that is working out of the box with Sbus ??? (And modify BetaFlight etc) But as it's an old video, I don't think Joshua Barwell will hear our cry's in the wilderness that is UA-cam. He must get literally thousands of notifications every day :) Joshuaaaaaa ;)
hi JB, what I'm missing. I have no telemetry apart from RxBt and RSSI after Discover new sensors. I've installed an R9 MM with latest firm FLEX_20190201. and OpenTx 2.2.3 on my Taranis Qx7. The channels are working great. The problem is the lack of sensors in the telemetry
It means that SmartPort is not working. Did you use the FPort firmware or the regular firmware?
Thank you for your fast answer. I have flashed FLEX_20190201 on R9 MM and R9M_FLEX in the TX module (Taranis QX7). My FC is a HAKRC Flying F4 v3. I have telemetry selected in BF. I don't have UART selected because I'm using F.port. Is it necessary to assign UART with F.PORT? I'm using the S.PORT/F.POT pin on R9 MM.
Hey Josh , I have a DALRC F405 FC , and a R-XSR flashed with FPORT, RC works great! but no telemetry only RSSI, any help would be AWESOME! Thanks mate
My guess is the port you're using only has a unidirectional inverter. Did you use the Smartport telemetry pad on the FC?
Have you tried adjusting tlm_halfduplex?
Joshua Bardwell I haven’t tried the inverted pad - I have tried all different variations of the inverted and halfduplex settings - as soon as you change any of those settings the RC stops working - tomorrow I’ll try the s-port inverted pad tomorrow and see how it goes - thanks so much for writing back yet again mate !!
On the New Mamba F411 AIO 25A ESC, they have both, RC tx pad and Inverted pad(s.port) on UART 1. Do I have to desolder the RC signal for f port to work?
Can you run F.Port through SOFTSERIAL on F4 boards to get past the inversion issue?
.
You can BUT not a good idea as your control link is going over it
what I use and also recommend is to use the normal Sbus protocol on its pad and in addition to that, use SoftSerial for SmartPort-Telemetry. SoftSerial is great, but it's a bad idea to use it with a receiver.
I don't think betaflight will allow serail rx over softserial. If they do allow it, you shouldn't do it.
Does your F4 board not have a smartport or telemetry pad to use? Most do these days.
On an F4 Board, what are the advantages of FPort? If the pad is already inverted, you can't use it for anything else anyway, right?
I tried Fport on a quad a couple months ago. X4RSB rx and Beerotor F4 fc. RSSI displayed really low numbers but the quad flew fine, for a couple minutes, then it just dropped out of the sky. I was only a couple hundred yards away and had been farther.
IMO there is something wrong with your receiver or setup. I don't think FPort should cause failsafes if SBUS does not.
Same for me die you find a solution? My range is low about 200m. The drone droped From Sky. Using fport and Flex Firmware.
@@XPSyan I've used Fport on other receivers and flight controllers and it worked fine. Just that one was a problem.
Joshua I added a r-xsr to my babyhawk r. I watched 3 of ur videos to help so I upgraded firmware and setup fport. I get rssi and rxbt telemetry and it works but I cannot at all arm the quad or setup switched on betaflight. I did cli status and just says RXLOSS. not sure what i missed since u am getting telemetry signal I know it's wired correct. thx!
I think you still need the sbus wire hooked up
Type SAVE after them commands. I missed that and it drove me nuts why nothing worked.
Also, on my xlite, I don't show the vfas change in display page.
XLite can't show VFAS on the display because it has a smaller display.
I have f port working soldered on the pad on r-xsr and have serial rx UART 1 and connect that wire to sbus on mamba f405 mini. In your reciever tab you have telemetry set to aux 3. It's that because you're using uart3 or... What? I don't know what to set that aux to. I have an x-lite so I need to do something with that? I get rssi and vbat but don't know if I'm missing something out...? I also did nothing with inversion. I have no clue about that. It works and flies so it didn't fry anything...
If you are using FPort, don't wire to the SBUS pad on the FC. Wire to the SmartPort pad.
@@JoshuaBardwellThanks for the reply. On the mini mamba or any other f4 fc I've come across there's never been a pinout titled 'smartbus' so I guess I'm not understanding it. In the ports tab I need to select and solder to the corresponding UART port and just select serial rx. And not select smartport on that selected port. Currently it's working as far as I can tell going through sbus. It flies and I have telemetry. Is betaflight not telling the fc that the sbus port is being used as fport in the configuration tab? goo.gl/images/qbJqnP
great video as always. i tryed this without any luck for days. I ended up flashing an older Fport firmwate for my R-XSR and it worked! dont know why the latest FW-RXSR-ACCST_v191112 didnt work know matter what i did. Any ideas?
Which one did you use? can't get my rsxr to bind..
Is there a way to keep the Jack and avoid to solder on the small uninverted S.Port pad?
Yes. Do just like I showed in the video. Connect the SmartPort wire to the Telemetry pad on your FC. The Telemetry pad will have a bidirectional inverter and Fport will work.
Or if you are using F3 or F7, use any UART TX pad because they can handle inversion no problem.
However, for an F4 board with no telemetry pad, you are stuck.
You would have to cut the trace from the inverter to the jack and solder a bypass wire. Possible, but not at all easy (no instructions given on how to do this - and you cannot just bridge the inverter).
Just saw this question because I may have to do the hack. You may be able to desolder the plug, cut the smartport pin off flush with the plug, resolder the plug to the board, then solder a short jumper wire from the backside of the pin to the P pad. However this may prevent you from flashing firmware since the normal smartport connection is necessary for flashing. Doesn't avoid soldering to the tiny P pad but makes for a cleaner install. A lot of work and better have skills soldering. Lol
I found a R9MM, flashed the firmware R9Mini_FCC_Fport.frk, and connected the Inverted SPort to TX1 on a new F411-Wing (flashed with the F411 softserial firmware). I set Fport as the serial receiver source in iNav, and now the Taranis X9D works the channels on the Receiver tab in iNav. However, I can't get the telemetry to work.
My R9M is flashed with R9M_FCC.frk, version 20190117. Per the Matek Fport page, I have entered:
set serialrx_provider = FPORT
set serialrx_inverted = ON
set serialrx_halfduplex = ON
Per Oscar Liang, I have also tried turning serialrx_halfduplex off and on again. Same with serialrx_inverted. I have gone to the Taranis telemetry page, deleted all sensors, but when I choose Discover New Sensors, it doesn't find any.
Does anyone see what I'm doing wrong?
Did you enable the Telemetry feature in the Configuration tab?
I finally got it working by going to an earlier version of the F411-WING firmware and trying a newer version of the R9MM firmware. Thanks for your reply!
I wonder if Joshua or anybody else can help. My new Archer GR8 receiver does not allow me to plug a sensor using the standard servo plug anymore. I had it working with the pre-ACCESS RX8R Pro as the Smart Port plug was for standard servo plugs. Do I have to use that new 4-pins F.Port connection now? If so, I guess I need to change the plug on the sensor side. Just a bit unsure, as it is, as usual, difficult to get clear info from FrSky. Any help is highly appreciated.
So I’m wondering should I try to reflash the rxsr receivers or should I update the firmware on my x lite radio And see if that helps me connect and get good signal out of the receivers
Hello Mr Bardwell I have your first f4 FC and using R XSR f.port. I got f.port to work I had to turn off halfduplex and invert both off. My question is can I use the sbus pad for smart audio sadly I burned off my tx4
SBUS pad is rx. SmartAudio needs TX. That's a no go.
You can use ledstrip remapped to softserial. Instructions are in the Troubleshooting section of the manual.
@@JoshuaBardwell thanks I already used the Led pad for it . I wasn't sure about what the sbus pad was RX OR TX thanks again.
Hello Josh, im new to open tx after yrs of spectrum im trying to get a 5 inch setup qx7 the receiver your using in this video. I have the lux V2 FC. I wired the rec as you described. My problem is i cant get the rec. tab in BF to work. On the lux v2 the serial rx is uart 4 the tx is uart 5 i have the serial turned on uart 4 and in config i have serial rx and sbus on, is that wrong?
Hey Josh, when you bind an F port RXSR reciever, do you do it in accst d16 or in access? I have the firmware updated but it wont bind for some reason.. Thanks man!!
Accst D16 or access depends on which firmware is on the receiver. Both types of firmware can output fport.
Hi, quick question if I understood correctly, on f4 like JB AIO, connect the smart port wire after flashing to fport to the T on the f4 board? Thanks !
Yes that's correct
Is it possible to wire a Ublox GPS to the same Uart as the smart port wire since they both transmit some kind of information?
No, you cannot have two devices on the same UART.
Flashed my rxsr and my qx7s accst. Works for that particular drone, but now none of my other drones will bind to that transmitter. They are all xm+ and a Mobula 6. What do I do to get them to work again?
ua-cam.com/video/09g5MfTdiyw/v-deo.html
Does this explain it?
I have an x-lite running opentx 2.2.4 and a crazybee F4 board trying to add an R-XSR. I can bind and fly the quad using sbus with the rxsr firmware 191112, but when I flash the fport firmware 191128 I can bind but I can't get activity in the receivers tab. I'm using the "inverted" pad on the R-XSR and set serial inverted off as well as half duplex on. Telemetry is turned on in betaflight as well as fport is selected as the protocol. Not sure if i'm missing something...
Hi joshua
Jumper r1 f-port receiver fault as on most i have seen online when binding both lights light up but you have green led on outer edge of board and red on inner which flashes in bind mode and green goes solid after power cycle
the receiver i have was got last week and when i put in bind mode red is on outer edge of board and green on inner when binding green light flashes and after power cycle red light goes solid it seems to be connected
Another point was to get it to bind i had to change RF fine tune freq to -15 it will not bind at RF fine freq at 0 should i trust this receiver i have heard of other people having problems with bind procedures on this reciver
Needing to frequency fine tune is normal for the multiprotocol module. You can find a tutorial on how to do it on Grayson Hobby youtube channel.
Specifically on the r-xsr, does the S-Bus-in still work?
In the FrSky firmware downloads it says "4:Redundancy function is still valid;". So it will still have SOME function but there is no information how it works exactly.
Yes it still works. The question is, what happens when the receiver failsafes over? Does it pass through SBUS or does it convert to FPort? You can test it and let us know!
Joshua Bardwell yes I will test this tonight or tomorrow with my x8r. Because I only have one x9d my test will be to hook everything up and then set model 01 to r-xsr and model 02 to the x8r, then switch between the selected receivers.
If you flash F.Port firmware to the R-XSR, S-Bus is not longer transmitted on the S-Bus wire.
This is from experience.
Both Firmware 180111 and 180228 disable S-Bus output.
So my setup never worked after flashing the FC and the r-xsr...I couldn't get fport to work with all inverted/uninverted hacks and inverted/halfduplex. I was able to simply re-wire my sbus wire and it worked immediately after changing back from Fport to sbus
Thanks
If you didn't change the wiring from an old board, that was set up for Sbus and Smart Port telemetry, then you didn't save any UARTs because you would have had it wired to use two different UARTs in the first place, right?
That's kind of the point. On an F4 board you may not save anything because the UARTs are inverted for SBUS and Smartport.
Is there any drawback for using this like increase of latency since now 2 types of signals are being communicated with the same wire? This seems just too good to be true?
Actually, Fport has lower latency than SBUS.
dose emax hawk5 have a smart audio function
No. For now it is push-button only.
Joshua Bardwell thanks.
Keep up the good work.
Thank you Joshua for this video. I'm having an issue. I have FLirt working and seem to have telemetry working "sort of" 😲 Since my craft is down and out awaiting a new FPV camera. I decided to upgrade my TX "SE Plus" to the latest firmware as well and as I stated, everything seemed to work just fine. I was able to see all the lua menu screens and the vtx screen. But now for some reason I get that annoying syntax error / out of memory error just before I get to the vtx settings. Any clue how to fix this.
Thank you in advance for any input.
ua-cam.com/video/1Ccz5gxAX2M/v-deo.html
what pad to connect r9 slim+ smart port with matek f405 ctr? please!
So with a R9 slim+ the s-port/f-port wire goes to the ‘T’ pad on the JBF4 and the SBus out would go to the ‘S’ pad?
Thanks
Correct.
@@JoshuaBardwell Thank you sir. I'm off to break a quad. :-)
Joshua if I flash my X4R-SB for F.Port will I still be able to use the original SBUS connection on the end of the receiver for controlling a gimbal for example?
Can you show me how to do it on Ominbus F4 V2.1 with a R9mini flashed with fport. I don't think it can be done.