iNavFlight
Quad works well if SBUS FCB-RX comms are used but it does not reliably work if FCB-RX comms use F-Port.
In particular:
- using F-Port the connection between FCB and RX does not always work at startup.
- even when by chance it works, shortly after the connection goes, and stays, down (requiring off/on for recovery).
The FCB is MAMBA_Basic_F405_MK3_F50. The RX is Frsky R9 Slim+, that I loaded with R9Slim+_OTA_FCC_Fport.frk firmware (taken by FRSky site) The schematic diagram of the quad is attached. In particular, notice the connection between Receiver and FCB, where usage of either SBUS or F-Port is done by different sw configuration. (the two configurations are the two attached dumps).
It is expected that F-Port supports control and telemetry and it is reliable. Instead, receiver and FCB do communicate after power-up, but ONLY sometimes. Once established, communication proves NOT reliable (it may stop in seconds or minutes, requiring then always to cycle the power to TRY recovery).
Note that, I used two equal receivers and observed same behavior. One of the receiver has been used for long in another model and worked well, providing telemetry. (in that model INAV was v.2.6.1).
It is instead the first time I use this type of Mamba FCB (and I do not have another one, at the moment).
Attached dumps contain SW versions.
dump (RX1 port).txt dump (F-Port).txt
A problem of F.Port of board Mamba f405 mk3 has been described in [(https://github.com/iNavFlight/inav/issues/7217)].