MAVLink 1
-
voxl-mavlink seems to support only MAVLink 2.
https://gitlab.com/voxl-public/voxl-sdk/third-party/voxl-mavlink/-/tree/master/filesThe third-party application I use uses MAVLink1 in part, which results in an error (actually no response).
Do you plan to support MAVLink v1.0 in the future? -
To reproduce:
set MAV_PROTO_VER to 1 (always use version 1)
VOXL cannot get any information from PX4.@JP-Drone Until now we didn't know that there was a use case for v1.0. What is the third party application?
-
@JP-Drone Until now we didn't know that there was a use case for v1.0. What is the third party application?
@Eric-Katzfey
It's UgCS.
The default is v1.0.
It's possible to set v2 or auto.
But if I set auto, it fails to connect.
Because it tries to negotiate with v1 at first and VOXL doesn't handle it. -
@Eric-Katzfey
It's UgCS.
The default is v1.0.
It's possible to set v2 or auto.
But if I set auto, it fails to connect.
Because it tries to negotiate with v1 at first and VOXL doesn't handle it.@JP-Drone Does it work if you set it to v2?
-
@JP-Drone Does it work if you set it to v2?
@Eric-Katzfey Yes, it works.
I am not sure if changing the settings on the GCS side will affect the connection to other copter.
But now it seems fine.
Thanks.
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