@Lance_B Was EKF3 enabled by default? Which parameter names and values did you use to turn EKF3 off? I would appreciate a concise summary of the modified parameters so that I can streamline the testing on my end. This info would also be helpful to anyone who want to know how ot enable/disable EKF3.
Changes to the SRx parameters does not enable/disable or otherwise affect the performance of the Native passthrough FrSky telemetry protocol that FlightDeck relies on. Only the MAVLink protocol is affected by changes to the SRx parameters, and native FrSky telemetry does not use MAVLink protocol for communications.
As discussed here (EKF2 and EKF3 memory issues), if EKF3 uses too much CPU, it delays the responses by ArduPilot to polling requests from the FrSky receiver and that’s what is causing the partial to complete FrSky telemetry loss (ArduPilot has 4ms to respond to polling requests from the receiver)…