Latency bug in voxl-mavlink-server
-
Hi devs
I encountered this as I moved from SDK0.9.5 to SDK1.0 on the VOXL2:
- UAV and GCS (QGC) communicates over cellular, joystick only (no RC transmitter)
- Fly the UAV. Land. Replace the battery (or for testing purposes you can just sudo reboot the VOXL2)
- Do not turn off the QGC application (tried on both Android and Windows; with physical joysticks)
- Upon reboot, the connection between QGC and UAV will resume. But, you will notice that the latency is say 500ms - 1s higher than usual. It becomes very apparent in flight because the joysticks' sticks movements are no longer considered "real time". You wont be able to notice it just by switching flight modes on the ground.
The workaround to restart voxl-mavlink-server (without rebooting QGC) or QGC itself after the connection has resumed in Step 4 above.
This issue is repeatable every time
Did not experience this in any of the earlier SDK versions.
-
Hi devs
I encountered this as I moved from SDK0.9.5 to SDK1.0 on the VOXL2:
- UAV and GCS (QGC) communicates over cellular, joystick only (no RC transmitter)
- Fly the UAV. Land. Replace the battery (or for testing purposes you can just sudo reboot the VOXL2)
- Do not turn off the QGC application (tried on both Android and Windows; with physical joysticks)
- Upon reboot, the connection between QGC and UAV will resume. But, you will notice that the latency is say 500ms - 1s higher than usual. It becomes very apparent in flight because the joysticks' sticks movements are no longer considered "real time". You wont be able to notice it just by switching flight modes on the ground.
The workaround to restart voxl-mavlink-server (without rebooting QGC) or QGC itself after the connection has resumed in Step 4 above.
This issue is repeatable every time
Did not experience this in any of the earlier SDK versions.
-
Hi.. can any devs confirm that what I encountered was a valid bug and not smth that was unique to my setup only? Thanks
@hmlow We don't normally fly with Mavlink commands. We will attempt to set up a test fixture with this and see if we can replicate the issue.
-
@hmlow We don't normally fly with Mavlink commands. We will attempt to set up a test fixture with this and see if we can replicate the issue.
-
@Eric-Katzfey thank you very much for looking into this
@hmlow Here is a link to an updated version of PX4 that should solve this issue: http://voxl-packages.modalai.com/dists/qrb5165/staging/binary-arm64/voxl-px4_1.14.0-2.0.43_arm64.deb
-
@hmlow Here is a link to an updated version of PX4 that should solve this issue: http://voxl-packages.modalai.com/dists/qrb5165/staging/binary-arm64/voxl-px4_1.14.0-2.0.43_arm64.deb
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login