We’re noticing a large amount of delay in everything related to the UART (Telemetry) connection. Arming the drone, disarming, loading missions, everything has an extremely inconsistent delay ~10-20 seconds. The RC inputs to the flight controller, however, are working as expected.
Looking through a flight log reveals that the commander, navigator, and mavlink loggers are logging vehicle_command lost messages around 30 times a second.
Is anyone else experiencing this issue? Is CubePilot aware of it?
The delay in the telemetry signal is there whether or not I use the streaming fix for the workswell camera.
We’ve been following standard procedure in that manual, using the flasher. Not sure how I would even load anything other than standard firmware. Is there an instruction guide/github on that?
One thing that I’ve noted this morning on further inspection is that the flight modes tab remains red in QGC when we don’t have any flight modes/buttons assigned. It also throws the preflight warning “One Or more vehicle components require setup prior to flight.” Wondering if this is part of the issue flooding QGC.
Does not say anything about the Flight modes page within QGC. I’m starting to become more sure that this is the problem, but your documentation doesn’t say what to do with this page. Is there a recommended procedure here?
Hi, we are experiencing the same latency but we are using arducopter latest beta version. Both in Solex and in QGroundcontrol we have the same proplem, 10 to 15 second delay for UART/telemetry.
Video stream is okay and also remote RC functions.
Any ideas what can be the reason for this?
Cheers from Norway
More information: We’ve started pinpointing it down to a parameter within PX4 that has been causing this lag. MNT_MODE_IN: RC, when turned on, makes the delay appear. We were not experiencing this issue with previous firmware versions. (We are using a gremsy gimbal). I’m wondering how we can go about getting older versions of the firmware to try to track it backwards?