FrSky FPort Protocol | IT'S GOOD, BUT I WISH IT WERE BETTER

Uncertain about what to buy? Check out THE ULTIMATE FPV SHOPPING LIST: www.fpvknowita...
SUPPORT ME ON PATREON at: bit.ly/2Ep5Sia
THIS IS MY FULL TIME JOB. Here are other ways that you can support me: www.fpvknowita...
---
People are asking me, "What is FrSky FPort Protocol?" And the answer is simpler than you might think. And that's part of the problem. I'll tell you what FPort is: it's good, but I wish it were better.
If you want to try FPort now, instructions are on the Betaflight Wiki:
github.com/bet...

[@bwanaPele]

FrSky just released an updated R9 module with xt30 support that goes up to 1 watt and tiny Crossfire like R9 Slim receiver that runs on 900mhz. It has lower latency like Crossfire and is fantastic. It doesn't require any hacks and just works out of the box after firmware updates of course. The other day I flew out 700 meters on 100mw with 99 RSSI the entire time. In fact it's tough to test it's limits because I am outflying my video feed. With the R9 Slim it's great to not have to worry about fail-safes anymore. The other plus over Crossfire is that it's about $50 cheaper. I bought my system from Rotorgeeks.

[@TheSummer750]

Staying away from it until all the bugs are worked out- good that TBS has competition though. Reading the RCGroups thread on it it is pretty clear that buyers are guinea pig beta testers. A stretch to say it works "out of the box" when there are weekly fixes/firmware updates all as a result of owners having problems.

[@bwanaPele]

J B The latest firmware update fixed most issues.

[@ToddSalpen]

yes that module is just PERFECT!! i love it but i wont lie i am using the TBS inmortal T antenna with the FrSky R9M hahaha, feels weird don't reach the 60% RSSI i loose Video before RSSI is just Awesome!!!

[@KCQuadTronX]

just when I thought I have watched all of ur vids lol...thanks for all the commitment

[@JulianGoesPro]

FPort is FrSky's answer to Spektrums bi-directional SRXL :)

[@ToddSalpen]

I am using it FPort and it works very smooth and nicely i have no complains, and i can use 16 channels, Crossfire just use up to 12 and the difference in the speed resolution is not to big, FrSky FPort is 115.2 Khz and TBS CRSF is 150 Khz, FPort clock cycle is 8.68 microseconds, and CRSF clock cycle in 6.66 microseconds, seriously for "2 microseconds"... i don't really care!!! both systems are great!!, Spektrum is 22 miliseconds or 11 miliseconds hahaha (joking i have no idea what those spektrum miliseconds means but if that is the signal resolution they are already out of the business)

[@AdamPyschny]

Frsky latency problems are not refresh rate related (btw, fport runs 12% faster then sbus, 100kbaud vs 112kbaud) but there is some software fuckup in the communication with the internal transmitter module. frsky tries to fix that in opentx since december but it somehow does not succeed. You can check out opentx github for details.

[@mojetreningi]

Adam Pyschny i

[@Terazuk]

And CRSF is currently 3 times (200%) faster than SBus, FrSky have dropped the ball and missed golden opportunity to get ahead of the curve. A 12% increase is a pathetic joke by comparison!

[@AdamPyschny]

nah, its only 50%... TBS likes to compare best case crossfire reception to 18 channel worst case sbus setup no one uses. additionally crossfire steps down dynamically in flight when conditions change, ans I dunno if mid flight changing control delay is really what you want. If Frsky would get their shit together and solve their tx module sync problem, we'd see ~3ms difference or so between frsky and tbs in their fastest modes, a difference I can live with, considering the fact that I save some grams due to much smaller antennas on frsky and sacrificing long range capabilities I don't need flying my racer never more far away then 100m or so.

[@mdrbal]

Can you point me directly to commit what tries to solve the latency issue?

[@AdamPyschny]

github.com/opentx/opentx/pull/5508

[@TexasWaters]

SUCCESS! I got it working on the Frsky R9 slim+. with a Matek F411-Wing Here is what I did, I used the RX1 reversed S.port signal on the Slim+ to the TX1 pin on the F411-Wing. No hack,Full telemetry Set CLI command to. # get serial serialrx_provider = FPORT Allowed values: SPEK1024, SPEK2048, SBUS, SUMD, SUMH, XB-B, XB-B-RJ01, IBUS, JETIEXBUS, CRSF, FPORT serialrx_inverted = OFF Allowed values: OFF, ON serialrx_halfduplex = ON Allowed values: OFF, ON I hope this helps others. Thanks, Regan

[@pargoff]

I always enjoy your videos. East to understand and very informative. Thanks!

[@mu2004]

Are we sure about no more inverter hassle? The last time I checked, I still can't get fport to work on most F4 FC, without applying the "uninverted hack" by soldering a wire to some tiny pad or chip leg. That's if the RX has an uninverted pad to solder. The new RX like R9 Mini doesn't seem to have an uninverted pad to hack, and fport didn't really solve the inverter issue.

[@JoshuaBardwell]

Yeah I think you're right. I was under the impression they were going to release an uninvert-hack FPort firmware. But it seems that hasn't happened.

[@rl2109]

Once again, thanks for your technical insight...! ;)

[@tehllama42]

So, the XM+ is now the best FrSky receiver for the money - got it. Thanks JB!

[@thekuz1982]

tehllama42 XSR-E is imo. Also known as XSR-M but the eachine is the same. Goes on sale on Banggood for like $10 sometimes.

[@tehllama42]

I'm just too slow to catch those. I've been wanting to try one.

[@reptethetetlen]

XM+ does not have telemetry, so it's got nothing to do with FPort by the way

[@tehllama42]

Yup - figured it out, XM+ still works great for ones where I don't care about tlementry. R-XSR is the answer in that form factor.

[@norgtube]

Complaining about fport not being like CRSF is fundamentally misunderstanding what they do. CRSF is the over-the-air protocol, the receiver just spits sbus at the FC. If anything, a crossfire receiver could possibly be made to talk CRSF to the radio, and fport to the FC. The wish for frsky to do something like crossfire already exists (the 9-series modules and receivers) and by all accounts it works well, but the latency isn't reduced, and the slim receiver isn't quite down to r-xsr size.

[@KCQuadTronX]

Happy New Year!!!!!!

[@gitech7450]

Still happy with my thin/light/fancy TGY-i10 with the lowest latency of them all, i-bus that is known to be "more stable", and can be installed to any non-inverted uart. It's like I won this race before it even started. ;) :D Devils advocate here... but no joke tho. *Tnx for the vid as always Josh!* Cheers

[@JoshuaBardwell]

Yeaaahh but where's that opentx port? And you have literally one choice for receivers that is worth anything (the i6, IMO) since the i8 has problems.

[@gitech7450]

I do appreciate the protocol flexibility that the opentx port (you mean the mod bay right?) affords, and I hate FlySky for crawling under a rock when it comes to their RX's (and for neither having a marketing department to get their f'n name on the board)! As for opentx FW exlusives like Lua Script, I'm not sure I currently see its' benefits as so much is possible through OSD now. The i6 is good. The i8 cost more and has less features than the i10 so it's all fail. For me the TYG-i10 was a one time $99 investment and it's worked... with the huge X6B Rx's that is... ;) lol :)

[@wyvern4588]

I wanted to love my evolution, but 2 brown-outs, one fried RX and 1 unexplained failsafes was hard to live with, the final nail was the inability to build a hyperlow frame due to the massive RX size. I feel a tiny bit of lag from my new Qx7, but my hands no longer shake from the stress of a failsafe going 100mph past a light pole.

[@renzevenir4853]

Will we have the same thing with ESC? A single wire on addressable protocol like i²C for all ESC like ESC telemetry wiring but now it can both transmit commands and receive telemetry. Less port needed and much cleaner build!

[@JoshuaBardwell]

There are currently ESCs that can use i2c to communicate, and also CAN bus I think. But they're pretty obscure.

[@vaphualfpv]

Josh, pls do long range build and suggestions. It would be so helpful to many!!!

[@DanboFPV]

Off topic slightly Josh, but looking forward to you testing out Crossfire, i'll keep an eye out for those vids. You also mentioned that you were going to branch out to iNav and Wings in one of your previous livestreams, is this still on the cards? What wing will you get? Capi2 perhaps? ... Anyhoo, great videos, i seem to have been watching alot of your vids recently, keep it up :)

[@JoshuaBardwell]

Hmm I said maybe a 7" long distance quad, not a wing.

[@DanboFPV]

Joshua Bardwell ok ok mibbi I heard it wrong lol .. why not a wing though?

[@harpalyke4659]

I think that the main reason folks are expecting latency improvements with fport is all those videos out there where people are talking about comparing CRSF and SBUS rather than comparing crossfire and FrSky's D16 protocol. Its at the link level communication where crsf wins out over FrSky, but because of inaccurate crsf/sbus comparisons, people are then hoping for gains in crsf vs fport as fport is a successor to sbus.

[@hateeternalmaver]

Thanks Joshua!

[@piloterror]

I mostly logged in to let you know I finally got around to dropping some coin in the tip jar but the original link you gave me wasn't exactly correct but it got me close enough to find it. Also though, this video follows along another question I've had for a while now; why don't FC's with OSD also include a pads for audio in and out so we can mix the regular audio mic signal with some on board warning sounds? I know, we get them through the RC receiver and the Tx Rx pads but...seems like there's an audio channel on the Vtx so why not have it available for another option?

[@JoshuaBardwell]

The FC doesn't have any function for audio processing at this time.

[@Sir_Brennan]

One could flip your argument around and say why does Crossfire not support RC and telemetry on a single wire like FPort does if you're comparing CRSF and FPort protocols. FPort might not be groundbreaking, but it's still a big deal in that it solves every issue FrSky receivers had. Namely, inversion and requiring separate wires and UARTs to accomplish RC and telemetry. And although FPort isn't any faster, at least it isn't any slower. It's still the same 9ms latency as running standard sbus. It's nice they didn't have to increase latency just to get everything on one wire.

[@JoshuaBardwell]

Crossfire does need both TX and RX pads, instead of a single wire, but I think it's not a lot to ask. What were you going to do with the un-used pad anyway, if it was a single wire? And theoretically using two pads gives more throughput (full duplex vs. half).

[@Sir_Brennan]

I'm not saying that crossfire isn't a better protocol. Just that FPort is unique in that it accomplishes what crossfire does using a single wire. Of course crossfire is still faster than FPort, but still, FPort is a pretty big deal for people who are using FrSky receivers. It just isn't a big deal for people who have already purchased crossfire systems.

[@nathanoliver5680]

I can’t wait for your crossfire videos!!!

[@k1f02]

Ouh I have waited for this! :D

[@JohnSmith-sr8ex]

Joshua, I have been visiting your web page. I don't know if you do it on purpose, but I recomend ( if allowed ) to open the links outside your main page. I find it more convenient. Happy to be one of your followers. Regards

[@JoshuaBardwell]

You can do that by using your center mouse button or by ctrl-clicking the link. I prefer to let people have the choice rather than opening a zillion windows.

[@JohnSmith-sr8ex]

Hi. Yes, that is the option, but I was meaning your own (economic) interests. I have a question for you regarding your own JBardwell flight controller. Will it allow to trigger a servo or auxiliary item ( from the same radio used for fliying, ideally )?

[@RcReviewsLt]

I think it's time for BF make not FPort capable, but normal TX-RX on one UART, as it's possible to do!

[@drkastenbrot]

thats what fport is

[@thebridgeninja]

The R-XSR has the “un-inverted” pads to solder to. So signal and s.port on an F4 is no big deal. I’m happy with what I have. F.port isn’t for me at this time.

[@scooterfpv8864]

Pretty cool stuff man . Mah friend wants his laptop back . Been looking at tablets "kinda" for me drone configure "In field" with no hassles . But LUA scripts as well from radio . Betaflight configurator . Ubuntu No bueno por nada .

[@sajjad3]

hi.... im new to this hobby..i cant setup r9m mini receiver on my fc ( mamba f405). joshua can you please tell me the connections of receicver on fc...usually it has 3 pins... sbus in ,sbus out,sport/fport...i shall be greatful to you joshua!

[@zeebeefpv2273]

Hey JB I am liking CRSF protocol a lot, but I am running into a lack of information on how to run it on some raceflight quads I have lying around. There is just nothing on how to wire up a micro crsf rx to a Millivolt FC, but it is easy enough to set it up on uart3 (ininverted), however it does not autodetect in RFOne. I also have a Revolt which I would like to run crsf on as well, is there a series of terminal (cli) commands I can follow?? PS HeliNation has triple packs of crsf rx’s in stock! (Through Amazon)

[@JoshuaBardwell]

Sorry, but I don't know the answer either. You really have to get support for that stuff from the RF team.

[@zeebeefpv2273]

Joshua Bardwell thanks JB, I swear the mostvaluable part of this Millivolt/Spark combo is the xt60. I kept that and threw the rest in the trash. I have a 20x20 HGLrc F4 40a stack that I know will work.

[@edwardMcrichy]

I'm guessing with fport you don't have set up a channel on the radio to get rssi on the osd? Or run a wire from rssi pin?

[@JoshuaBardwell]

Ummm I think I heard something about FPort being able to do RSSI via Lua Script, but I don't know for sure if that got implemented and works.

[@thekuz1982]

I’ve flashed and set up Fport to two different quads now. Both boards I could not get telemetry to work. The problem is that your inverted uart needs to be bidirectional. So the inversion issue is still an issue. If you want to use an uninverted uart you need to perform the uninversion hack on your receiver. Bit of a let down. The first quad I just went back to standard sbus/smartport. Second one I’ll do the same. You can assign any uart to be a softserial for smartport and it’ll fix that issue. Pretty let down by Fport. Inversion is stupid.

[@JoshuaBardwell]

I advise using the SmartPort pad. Since SmartPort is bidirectional, it should have a bidirectional inverter.

[@thekuz1982]

Joshua Bardwell well. That’s a great idea. I’ll try that and report back!

[@ViperFPV]

FYI Frysky already came out with a long range faster protocol look it up

[@JoshuaBardwell]

I want them to make 2.4 GHz faster.

[@beeradfpv]

Once you go crossfire its hard to go back...

[@DrOne-sw6oz]

True

[@WarChest]

High speed CRSF, full Bi-Directional Telemetry, and miles and miles of ridiculous range sold me on Crossfire. But to be honest, I hope FR Sky gives TBS some non-cloned, honest competition. After all, healthy competition helps us all progress.

[@timtoney6672]

Hey you do know there is the frsky R9 slim right? brand new just came out operates at 900mhz so it needs it own module, the R9. They say it has a low latency very similar to crossfires. You should also give that a try and compare it to crossfire see if it matches up as a cheaper alt. The receiver is 26 and the module is 50.

[@timtoney6672]

On getfpv

[@francisroan]

So which port do you use for fport? Tx or RX? Or tie both of the same UART?

[@JoshuaBardwell]

For bidirectional communication with a single pin, you typically use the TX pad only.

[@TheMadmacs]

you know how flysky get battery telemetry? they connect rx directly to battery, one wire. transmitter has two stage beep alarm, job done.

[@WildpixFPV]

So how much slower is the refresh frequency / latency on the f-port signal? Bummer if it still makes a noticeable difference, totally agree with "a big thing, but not a really big thing actually" lol! Think I'm going to wait, still have your JB-FC to build and a CL_Racing F4. So I am lucky to have that uninverter onboard ;) -Or get Xfire, sooner or later.. =)

[@JoshuaBardwell]

Crossfire is supposed to have 150 Hz refresh rate and like 6 ms latency. FrSky SBUS is in the range of like 40 to 60 ms latency if my memory is correct.

[@WildpixFPV]

Yep, Crossfire is.. YUMMIE! I just checked back to Drone Mesh's test video.. i THINK it's 24ms on zero throttle and around 30 on full throttle.. but I don't have the time and head right now to study his complicated thinking and talking, sorry xD Edit: Oh, my bad..that was frsky latency.. not sbus.. difference huh? lol

[@WildpixFPV]

sry Josh, I'm just one of those kids (used to be in school, long time ago, like that too) that do have enthusiasm for the stuff but 2much chaos in my head to get it back out in order lolzz

[@DennisKrger]

Nope. It's 9ms. 3ms frames with 6 ms pause between frames.

[@DennisKrger]

Oh man, I'm wrong. The frames might be that short, but it takes several frames for it to actually change.

[@TheAngryAstronomer]

You say maybe we should all get crossfire but wouldn't it be nice for all that functionality to just be native in the radio and receivers rather than needing a module? I'm kinda old school I guess. If I want hella range I just use my Dragonlink.

[@JoshuaBardwell]

That's my point. FrSky should make their native 2.4 GHz protocol faster.

[@Stinngerr]

Just to add on some F4 boards dedicated Sbus pad is not bidirectional. So no telemetry on single pad with Fport for me. I tried to wire it to UART1 TX smart port and no luck. Still have to use another UART for it. My board is Omnibus f4 pro v2.

[@erdemk0]

So does this mean that xm+ supports telemetry? You mentioned that it can be flashed with fport firmware , if it’s not for telemetry what advantage does it have over the regular firmware?

[@JoshuaBardwell]

Inversion.

[@NarcolepticLTD]

Looks like it'll be after chinese new year before xfire RX's are back in stock - hopefully you've got one slated for ya :)

[@DerickPelser]

Hey Joshua, I do not agree with your statement that you cannot use one UART for two functions as Raceflight is achieving this on the Revolt. For example if I flash my Revolt with RF1, I then use the same UART for sbus and smart audio. However if I flash my Revolt with BF I need to use two UARTs which means I have to move my smartport wire to an unused UART. I shared this with the BF developers and they said the same your are stating in this video. I think the BF developers are relying on UART library which introduces this limitation and its not a limitation of the STM32 processor. 💡

[@JoshuaBardwell]

You're correct that it is possible to do this, just that Betaflight doesn't make it possible.

[@DerickPelser]

Joshua Bardwell It would be awesome if BF can support it. Then this whole inverted 💩 can be avoided. I forgot to mention I needed to use the inverted hack on the frsky receiver when using Betaflight.

[@krishan8170]

I use kiss gear only because one of them is an f3 board while the other fc is an f7 and plus kiss is great!

[@AdamPyschny]

Its not problem to use uart RX and TX for seperate functions, but as its ONE uart you have to set it to ONE baudrate. sadly sbus needs 100kbaud and sport 56kbaud. thats why it does not work. It works on raceflight because the revolt FCs simply connect the pads to both uart and pwm pin and simply run softserial when needed.

[@beebakrizzle]

@Derick Pelser Supporting using a single uart for two things is not gonna solve the inversion problem. It has nothing to do with it. The inverters we have on sbus pins are unidirectional, they only work on the RX pin in the RX direction. Same with the inverters on s.port pins, they only invert the signal in one direction. None of the flight controllers I know provide a bidirectional inverter or inversion on both the TX and RX pins of a single uart. By the way, even if you flash your R-XSR to use Fport, you still need to use an inverted uart because the inversion inside the R-XSR is done by a hardware inverter and cannot be "cancelled".

[@brandonderrick3545]

Hi Josh. Do you have a suggestion for the best cheap FC?

[@JoshuaBardwell]

www.fpvknowitall.com/fpv-shopping-list-parts/#flight-controllers

[@brandonderrick3545]

Thanks! Woops, Sorry, I totally forgot about the list.

[@thekuz1982]

I honestly think the Bardwell FC is the best bang for your buck. Seriously not trying to be a kiss ass on his channel. But it’s true.

[@FourthWayRanch]

is it normal for the taranis x-lite pro to pulse every second when you use F.Port telemetry? It seems to do a sweep of the data every second and the signal meter on the main display turns on and off. It didn't do this on SBus. The signal stays constant on the OSD though. The RSSI must be more realistic with F.Port cause it drops below 99 pretty quick, when it was on S.Bus it just stayed at 99 all the time.

[@JoshuaBardwell]

No, that doesn't seem normal to me.

[@FourthWayRanch]

@@JoshuaBardwell I wonder if I have a bad R9mLite pro module, it seems to get a little warm, didn't seem to do that on SBus. it flies ok though, no failsafe yet, the bars for receiver signal on the Tx turn on and off every second, there's something screwy. I have F.Port setup on my tandem X20 and it's not doing that and the Taranis Xlite pro Tx doesn't do it for a 2.4 receiver either. Something is definitely shutting on and off with the R9 module (but it still seems to fly ok) weird

[@madforit9661]

Josh my motor gets to just over 1300 revs and starts spluttering, I have changed the esc and tested the motor with another It does the same thing It is like the signal from the board is getting interrupted. Is there any code i can use in the cli to check this Many thanks Sorry it's not related to this vid ,but needed you to see it asap. Cheers

[@JoshuaBardwell]

If you changed the motor, the next step is to change the ESC. If that still has the problem, then it points to the FC.

[@madforit9661]

Thanks That confirms It's the Fc. Oh nice vid

[@mikej8940]

Joshua since you wrote the manual for the holybro kakaute v2 which uarts would you use, smartaudio is u6, u5 is esc telemetry which uarts are bidirectional , can you use the smart port pad and one other?

[@JoshuaBardwell]

I'm not sure about that, but I feel pretty sure that T6 or T3 pads would work.

[@mikej8940]

t6 is smart audio thats out t3 is automatic sbus inversion

[@MachuPichuu]

on my Kakaute v2 AIO it worked perfectly on the dedicated S.port. apparently it has a bi-directional inverter. its UART 1 i think.

[@trond9000]

What we need is for someone to make an awesome OPEN PROTOCOL. Then it wouldn't matter which radio or receiver vendor you're using and the vendors can compete in making the best hardware that supports that protocol. Closed protocols hinder real competition and innovation where it matters.

[@Ununpentius]

After I flash the receiver for F.Port, I can still plug a SBUS gimbal into the pins on the receiver yes?

[@JoshuaBardwell]

I don't know the answer to that.

[@devel666x]

thanks for clearing this up JB was mention on the RR fb grp and was like wtf is f port thanks for clearing this up for us and yea its a big deal

[@Robert67909]

Now I got a question I use butterflight and did the hack on the x4rsb now I went to the CLI command and change two inverted or uninverted on, I can't remember which one but I wonder if butterflight has already got this switched where I don't have to do anything in the CLI after doing the hack

[@dbrokenbone]

josh...is telemetry on s.port make the distance drop so much... cuz i get 50db at 200m with R-XSR

[@bozosni]

Thank you for the info joshua but i am really confused and i need your help. You said that with f port we dont care about inversion. But at the link you added says that it is inveryed signal. Also, the sport pin of the r9mm that i have ordered also says fport. It just uses the same pin and the change is what you choose in the port tab in BF? Thank you.

[@JoshuaBardwell]

When I first learned about FPort I read that it solved the inversion issue. But as I learned more about it, I think that's incorrect. FPort is inverted and must be used with a bidirectional inverter pad. If you are using the R9MM however, it has un-inverted output of SmartPort and FPort so you can simply use a regular RX pad on your FC.

[@bozosni]

@@JoshuaBardwell thank you so much. That is what i nedeed to hear. I have ruined the sbus pad on my Hglrc f4 osd and that is the reason that i ordered the r9mm. So the inverted sport(so-> uninverted) that r9mm has can be also used as fport? Is that right? Thank you very much. I love your videos, always watch them and you have halped me alot at my first steps(6 months ago) in the hobby. Love fro Greece!

[@JoshuaBardwell]

Yes correct. The "inverted' (actually un-inverted stupid FrSky) SPort pad also works for FPort.

[@bozosni]

@@JoshuaBardwell Yeahhhh ,😍

[@MBorga]

Hi Joshua did you ever try f port? I saw a German Video about that f Port thing but i think nobody bring it to work. I burned that tiny small shit p pad from my R xsr so i found your Video and give it a try. Thanks for your Video.👍Best regards Marc

[@slavikarg]

Hey Joshua, is it possible to remap the vin / vout pads in a Kakute FC? I suspect not, but it's better to ask.

[@JoshuaBardwell]

No.

[@marko5766]

FrSky has tried to make their own Crossfire-style 900MHz system, and there has been nothing but problems with it...starting with sending the first modules out with 2.4GHz antennas! After nearly a year, they still can't seem to get firmware figured out, and I've not seen anybody have much success with long-range flight yet. Meanwhile, one of the first real owners of Crossfire, shortly after they released, went over 12 miles almost by accident on what was supposed to be a short test flight. I think your dreams will be better realized with OpenTx and TBS in this case.

[@JoshuaBardwell]

I just want faster refresh rates and lower latency from the regular old 2.4 GHz system.

[@djmoto5505]

Joshua I know it sounds stupid but can you do a video on setting up F Port I've watched all the videos I can find and been stuck with this for over a week but I still can't get mine to work on my new build FC = matek f405 with the fchub running BF 3.3.1 ......... receiver = R XSR connected 3 wires + - and soldered to the P on the baord to tx pad on uart 3.......... taranis running 2.2.1 with Lua scripts

[@djmoto5505]

With the above set up my reciver is bound to my taranis and my radio link IS working . I have only 2 sensors showing but nothing in my Lua scripts there all blank

[@djmoto5505]

Forgot to say I have the similar set up on my other quad The difference is I'm using a de pinned x4rsb using 2 uarts sbus and S port and are RSSI soldered on the baord And the Lua scripts work on this build I'm not using the LBT firmware

[@JoshuaBardwell]

I think it's that you have used the uninverted P pad that is messing you up. The FC may be expecting I'm inverted signal. If your FC is an F4 use the Smartport pad.

[@djmoto5505]

Hello Joshua thanks for getting back to me I am using the uninverted pad on the rxsr to uart 3 tx I have also have typed set serialrx_halfduplex = ON set serialrx_inverted = OFF To the cli My radio link works but I have no PID or unify control I know I could just wire it up the old way but it just bugs me to why the hell don't it work I'm happy this is your full time job .there's only yourself and Bruce Simpson who I watch on KZbin Your helps much appreciated Dave

[@psydafke]

+Joshua Bardwell Got excited to try out this FPort protocol on a new build. Sadly my Taranis' internal XJT has EU-LBT, and the beta-FW for the XSR is non-LBT... so cannot bind. Seems quite a hassle to flash the internal module to non-LBT FW (using the external XJT header, and SPort flash app), then also flash all my current receivers to non-LBT... just to try this one.. :( FrSky should also build a EU-LBT version of the F.Port FW. No idea where to contact them about this.

[@psydafke]

Mailed FRSky, and the EU LBT is currently only available for the R-XSR, while a EU version for the XSR will come in the near future.

[@FPVish]

Please when you get a chance, could you review the NEW F7 Betaflight Board.

[@SmokinMesa]

Wondering about this. For me was/is more about telemetry and inverted signal

[@zymurgyjwt]

Why would Frsky care about competing with CRFS? They sell the same amount of radios but don't have to worry about supporting their connection. I doubt they make money on their receivers anyways.

[@renzevenir4853]

Because FrSky isn't a greedy ass company like $pektrum, they listen and care to the costumer.

[@renzevenir4853]

Sorry, misunderstood. I don't know either, but we can agree on one thing though. Manufacturer competition is good for us customer.

[@0Gravity1966]

Can you do a video on installing this and setting it up? Not finding any great vids out there on the subject!

[@0Gravity1966]

Basically, I can get thru the flashing of the receiver, but can't decipher how the wiring goes....do you solder both the SBUS wires and the old Smart Port wire to the same Uart? If so, do they both go to UART TX?

[@JoshuaBardwell]

It's a single wire. So it should use the SBUS wire I think but not sure. And it goes to a single UART TX pad on the FC. Typically I think the pad that is most likely to work will be the SmartPort telemetry pad, because that is guaranteed to have a bidirectional inverter on it like FPort needs.

[@0Gravity1966]

This is on a HGLRC F4 Omnibus FC, I already have the RSXR connected to the SBUS TX which I believe is the only uninverted UART available, and this bird is already flying, so what your saying is that my connections should already be installed, so all I would need to do is flash the firmware and make the necessary changes in CLI?

[@0Gravity1966]

Well, I gave it my best shot, I just spent the better part of 5 hours fiddling with it trying to get it to work...I loaded BF 3.3.0 RC 1&2 (Which are both buggy as hell) which I believe was most of the issue...I was able to get BF to see the receiver but had no telemetry being sent...I guess I'll wait until they work out the bugs! BTW, you have to actually use the SPort connection on the receiver instead of the SBUS connector! Oh well...I tried!

[@27isanum]

I read everywhere that RSSi is support on Fport on the XSR. Flashed the beta firmware and its all working but I just can't figure out how to get RSSI back.

[@JoshuaBardwell]

kzbin.info/www/bejne/ql7Ip4J3iJ6Aock In BF 3.3. I am hearing that the Lua script will send RSSI and real-time-clock automatically.

[@anashbear2608]

Hi, I have a DYS f4 pro v2 FC and apparently only Uart1on this board has a "bi-directional inverter", typically used by the S.Bus signal wire on the RX pad on Uart1. My question is, does anyone know if the Uart1 TX pad is also effected by this "bi-directional inverter"? If so does it sound correct I can move my S.Audio wire to Uart1 TX pad and flash f.port firmware to my R-XSR and settings in beta flight etc, and it will work out? Or am I 100% going to have to do the Hack to my receiver to access the un-inverted signal in the first place?? Thanks anyone out there

[@keydell4utube]

Is FPort compatible with F1 FCs, like CC3D?

[@JoshuaBardwell]

I don't see what would stop it from working but I haven't personally verified it either.

[@QurttoRco]

Heres what I dont understand, why is sbus only 1 way? Receiver is sending data back to radio so why cant it send rssi batv and other stuff you want?

[@JoshuaBardwell]

That's kind of the whole point of FPort isn't it?

[@QurttoRco]

Ok thanks, you made it sound like it's just sbus but without inverted port restriction.

[@quadbrofpv9727]

I think FrSky recently came out with a system similar to crossfire called r9 or something like that. It runs on 900mhz and supposedly has lower latency. Not sure how good it is compared to crossfire tho.

[@Soundboy61088]

I know when they sent bruce from rcmodelreviews a unit to test they sent a 2.4ghz antenna on the 900mhz unit. And someone else made mention of that happening to them too. So if that's any indicator..........

[@quadbrofpv9727]

Steve Blaski if that did happen im sure 900mhz antennas are cheap. I think a tbs crossfire immortal t is like 5 bucks.

[@scotty562]

It doesn't do telemetry which is a big downside.

[@KrotowX]

TBS is faster and have larger range and... is totally illegal for unlicensed use in countries where 915 MHz frequency is already used for something else. At least in my country this frequency already is leased for cellphone operators from year 2010. Recently one of our local drone pilots with TBS in my city experienced unexpected guests - police together with guys from RF spectrum monitoring. However I agree that FrSky still did only a half of job for F.port although that what they did, is already awesome I hope that their next move will be F.port v2 something - faster and with full duplex serial communication using both TX/RX wires if available.

[@renzevenir4853]

What happened then?

[@Cornflakes691]

What happened??

[@robbinkoot2154]

So I can solder the sbus and smartport from my receiver to the SBus on my F4?

[@JoshuaBardwell]

SBUS to SBUS. SmartPort to Telemetry/SmartPort. FPort to Telemetry/SmartPort.

[@PaneInTheGlass]

have you seen the new armattan frame called the mongoose? its like 40 bucks i think

[@die_hertz]

FPORT is not an air protocol, why would someone expect it to reduce latency or increase refresh rate?

[@JoshuaBardwell]

Because they don't realize that it's not an air protocol.

[@dronepunkfpv1424]

What about half duplex?

[@jayward7536]

hi josh useing your fc have r9m lite mod useing r9 mini rec with f port wired to t pad sticks switches all work no telemetry thoug any idea

[@JoshuaBardwell]

did you go to the CLI and type set tlm_halfduplex=off save

[@jayward7536]

Joshua Bardwell yes i did it both ways on shuts off stick controls when i leave halfduplex set to off my sticks and switches are good but in not t getting any telemetry .im runnig beta 3.5 should i maybe change it

[@jayward7536]

I got to work im still learning on this xlight i had internal and external modes on at same time my mistake . All working good now thanks joshua

[@chrismichaels5216]

From the wiki "must be able to run inverted bidirectional", looks like it still requires a flight controller with at least one inverted UART still.

[@JoshuaBardwell]

I don't think so. One of the whole points of FPort is that it gets rid of the inversion requirement. I suspect that's a mis-type on the wiki.

[@DennisKrger]

AFAIK, that's because current hardware does not support uninverted. The protocol does, the hardware doesn't... Which makes sense, since the inversion is done by dedicated but stupid components on current receivers.

[@chrismichaels5216]

Just ready the F.Port spec, I'm thinking it still requires inversion which doesn't make sense. "1. Physical Definition Tri-State TTL is implemented as communication level, 2.5v/3.3V as digit “0”, 0V as digit “1”, the voltage between 1V and 2V is not distinguished." github.com/betaflight/betaflight/files/1491056/F.Port.protocol.betaFlight.V2.1.2017.11.21.pdf I'm flashing now to validate.

[@thekuz1982]

It’s likely that they will be releasing Fport receivers that are hardware uninverted at a later date. The inversion issue is still an inversion issue. And for it to work, your inverted uart must be bidirectional and I’m 0/2 on the two boards I’ve tried so far. May perform uninversion hack or just go back to standard protocol as I have extra uarts. Just wanted to experiment.

[@BrianPage_78666_]

Chris Michaels that is odd. In the semiconductor world, and most digits applications, a voltage of 2.5/3.3v is a logic 1, and 0v is a logic 0. All they really need is a preamble in the packet header and they would be able to tell whether or not signal is inverted. The rest gets taken care of in the firmware.

[@blade10w40]

6:27 - I LOST MY SHIT LOL!!!!

[@sigvaldithor]

Fport is kinda meh. one less wire means nothing to me but less latency is the dream.

[@krishan8170]

If you want on your x4r rx, when binding you can cut the latency in half from one of joshua's videos on what to do when your first get a taranis

[@sigvaldithor]

BoomoFPV i have already switched from D16 to D8 mode but i still want it lower :D

[@MindOfBoomBoom]

I always wonder why people enunciate "FrSKY" as Free Sky. I always thought it was FrySky because the Y is imaginary and silent? :P tomato toMAHtoe i guess :P

[@carveking]

Their taranis manual literally says something to the extent of "We are FrSky, pronounced 'freesky'". So people say free sky because its the official name!

[@leecyrille]

CRSF runs 400k I think?

[@j.finesseflights1403]

Lol, my trusty ol' FlySky Ibus is hanging in there ok... Only because I can't afford frsky and the TBS equipment!!

[@ronbo422]

I'll hang loose until it becomes more popular and more RX's come with it. Not been an issue for me, thus far. Thanks for the info, though, Josh. de K5RPM

[@1337flite]

FPort - Meh too little too late. Too hard too, flashing FRsky kit is a bit of a nightmare. TBS have this problem fixed. Install CRSF. Done. Updates easy, telemetry easy, RC more reliable. The only downside is cost. But save one quad and you get your Crossfire money back.

[@krishan8170]

Agreed

[@VilleF1N]

I disagree with flashing FRSky being hard. All you need to do is: 1. Take 1 of those 3 pin cables which come with x4r-sb and modify it by moving the wires around a bit. 2. Load the receiver firmware into your transmitter. 3. Flash using your transmitter. Project Blue Falcon has a video on how to do this called: FrSky X4R-SB: How To Change EU / Non EU Firmware. That said, i'll be switching to Crossfire as soon as i have the money to buy the module and 4 receivers for all my quads and maybe 1 or 2 spare receivers.

[@isaacfpv9742]

for crossfire you just 1)plug the tx module into the computer, 2)update it, 3)re-bind your receivers, and it will update the rx over the air(no need to remove the rx and create a special cable and pray to god you dont brick it or short circuit it)... so if flashing FRSky is not hard, flashing CRSF must be super easy lol

[@VilleF1N]

The way updating works with Crossfire sure is a huge convenience, but why would you need to remove your rx? At the most you'll have to power up your quad, if your FC powers up while you power up your rx and just plug in the telemetry wire to your tx if that happens. Even that may not be necessary, but it sure is a bit dodgy if your Tx powers up your entire quad while flashing the firmware(Happened to me once :D). And making that special cable is also super easy, you just move the pins around.

[@deadmoo83]

Huh, I just plug the receiver into the bottom of my X7 and flash it. It is really easy. And once it is finalized, it will be preloaded on the receiver anyway.

[@ericdolphy8320]

FrSky stopped innovating when then began to sell radios

[@Away907]

exactly my case at 3:30

[@moochasas]

Once you go TBS frsky will be a thing of the past...........

[@PeterDenTV]

Inverted serial? There's alternate ways to solder your things man!

[@firejeep2009]

i see frsky coming out with Gspot port:-) you ask what is Gspot port... is where there hit it just right and knock TBS out :-)

[@BuzZ.]

Nope, I fly flysky 😛😜

[@cmulder002]

Joshua ; you did not mention if there are any changes needed at the transmitter side like an updated firmware for the module and / or open tx version

[@JoshuaBardwell]

No. Just receiver and Betaflight. Check the wiki page linked in the video description.

[@sgtsimplycrispy7749]

"too much detail*

[@SEQMONITORS]

hahhahahahhaa oh bardwell you're gold!

[@nathankadria8953]

hyperlite f4 osd

[@scotty562]

+1 for crossfire.

[@simonwiksell]

The title is misspelled, it should say "I wish it WAS better". Not writing tgis to be a d*ck, just informing.

[@MrStevegibb]

Honestly considering the price gouging from tbs and iftrontech crossfire and clearview should be banned from racing otherwise it becomes a rich man/kids sport.

[@JoshuaBardwell]

It's already a rich man/kids sport. Don't kid yourself.

[@tehllama42]

Even considering the prices of those things - drones are the cheapest sport you can get into with the performance figures we're talking about. Even comparing it to racing bicycles, a reeeeeeally simple mechanical device, racing quads are cheap.