Can you update to the latest 3.3.1 firnware?

_________________
Spirit System developer

I already updated to 3.3.1

Sent from my SM-N976Q using Tapatalk

Hello,

can you let me know where we can download F.Port firmware for the Radiomaster receiver?
By default the receiver has support only for S.BUS and S.Port for telemetry.

If it is not really using F.Port then receiver must be configured to a correct type.

_________________
Spirit System developer

The receiver is working fine with the F.Port protocol ( check below link)

I already made more than 6 flight with this receiver working in F.Port Protocol.

My problem is that the app jeeps disconnecting from the fbl also i am not able to view the flight logs.
http://cloud.tapatalk.com/s/60f525ecbf1ae/R161%20F.Port%20FCC.zip

Sent from my SM-N976Q using Tapatalk

Dear Zexx86

Kindly help me resolve this problem.

Sent from my SM-N976Q using Tapatalk

I am not sure how F.Port from RadioMaster is working and how it is compatible with FrSky receivers. Unfortunately we have not tested it yet.
You said there is some kind of improvement when you disconnect receiver.
If yes, then it mean there is some incompatibility issue. In this case I recommend to use S.BUS and S.PORT - official firmware for this reaceiver for now.

Regarding Flight Log issue, it is possible you have too many log parameters enabled for logging. This can create too big requirements for computer and memory might be not enough in your computer.

We will try to optimize our software to handle big logs on all computers with upcoming software update. You can try to select only few log variables. Then I believe it will work for you too. New flight logs with only few telemetry variables should be less demanding.

_________________
Spirit System developer

Dear Zexx86

I have removed the radiomaster receiver and insralled an original Frsky Rxsr receicer flashed with v2 F.Port firmware, the problem in still the same, however when i use my X8R connected with SBUS SPORT the problem disappears.

So it seams that the problem is with FPORT Protocol.

What receiver did you used to test the FPORT?

Sent from my SM-N976Q using Tapatalk

Please note F.Port revision 1 is supported. For revision 2 FrSky is not giving any documentation yet.
For example R-XSR, RX4R receivers and other ACCST receivers were tested.
There is big difference between ACCESS and ACCST F.Port.

_________________
Spirit System developer