Refresh

This website oscarliang.com/fport-latency-testing/ is currently offline. Cloudflare's Always Online™ shows a snapshot of this web page from the Internet Archive's Wayback Machine. To check for the live version, click Refresh.

FPort Latency Testing

by Oscar

In this post we will share some findings and results regarding the latency of FPort receiver protocol. Separate tests were run on the XSR and R-XSR RX’s, using a logic analyser.

Some of the links on this page are affiliate links. I receive a commission (at no extra cost to you) if you make a purchase after clicking on one of these affiliate links. This helps support the free content for the community on this website. Please read our Affiliate Link Policy for more information.

FPort and SBUS Latency Measurement and Comparison

The latency stated in the table were measured at the gimbal/switch output, and the receiver output. It includes latency from OpenTX and iXJT->XSR.

Latency (ms) Mean Stddev Min Max 25% 50% 75% 95% Refresh rate (Hz) Notes
iXJT – XSR – SBUS 19.748 3.852 11.789 42.749 17.100 19.409 21.774 25.766 111 add 2.97ms for SBUS frame
iXJT – XSR – FPORT 15.078 3.628 8.244 35.896 12.547 14.967 17.303 20.272 111 add 2.65ms for FPORT frame
iXJT – R-XSR – FPORT 16.724 3.354 10.039 29.761 14.346 16.804 19.134 21.820 111 add 2.65ms for FPORT frame

Interesting Findings

As the result suggests, FPort is slightly better than SBUS in terms of latency. However the protocol design is not yet optimal which means it will only get better in the future.

When testing FPort on the XSR, we found it has more erratic refresh rate. Hopefully reliability will improve in future software updates.

There were some performance difference between receivers when using FPort. For example, we found XSR was slightly better than R-XSR, that’s probably because of the different micro controllers. XSR has a more advanced 32-bit MCU while the R-XSR is using an 8-bit MCU.

Anyway, FPort firmware is newer and it’s expected to have better performance in general.

Credit: Andrey Mironov

Leave a Comment

By using this form, you agree with the storage and handling of your data by this website. Note that all comments are held for moderation before appearing.

5 comments

famtory 1st October 2018 - 3:38 am

Many “f4” users will use “soft serial” to use “f.port”.
I would like to know latency.
“soft serial” and ” h/w serial”

Reply
Oscar 1st October 2018 - 5:05 pm

latency is not a problem, update rate is.

Reply
sevet 6th August 2018 - 10:15 pm

Read this three times and i can’t understand the conclusions vs the data….
You say SBUS is better?
The Fport latency is lower on all tests!
how is this conclusion logical?
If higher results (if im reading this wrong somehow) are better then how come RXSR worse than XSR when it has mostly higher values?
Very confusing.
Considering some other tests show Fport to be less latency…..

Reply
John Daniels 26th February 2019 - 11:53 pm

What he is saying is Fport is faster better than sbus but it is erratic on the R-sxr works better on the sxr but in future updates it will change hopefully.

Reply
oermens 24th December 2021 - 6:52 am

Late reply but for latency lower numbers are better, not higher numbers. Ideally we want zero latency but that is impossible, so we go for the lowest miliseconds possible.

Reply