search

OpenSolo / sololink

Deprecated. This is now a sub-directory in the new repo https://github.com/OpenSolo/OpenSolo
Apache License 2.0
19 stars 16 forks source link

Using MAVLink 1.0 , makes controller stuck at "calibrating sensors" #9

Open AndKe opened 5 years ago

AndKe commented 5 years ago

if I select MAVLink 1 for USB ; SERIAL0_PROTOCOL 1 the Controller is stuck with "Calibrating Sensors, please wait"

AndKe commented 5 years ago

Correction: I have done several tests and this is not related to SERIAL0_PROTOCOL. In short: If Solo boots up first, then controller, everything is fine. If the solo get a battery change (reboot after the controller), the odds are that the controller will be stuck with "Calibrating Sensors"

AndKe commented 5 years ago

@Pedals2Paddles - did I post in the right place?

FLYBYME commented 5 years ago

So setting "SERIAL0_PROTOCOL 1" is not a hard rule. If the pixhawk receives a mavlink2 message it will respond with a mavlink2 message.

What I suspect is happening is the ground station is sending a mavlink2 message and the pixhawk is responding with the same version will artoo is just a passenger to a conversation is does not understand.

An easy fix to the mavlink 2 issue is just to upgrade the artoo mavlink to v2. From what I have tested v2 on the artoo would be a drop-in replacement. Could leave artoo as v2 or just set the status flag as "MAVLINK_STATUS_FLAG_OUT_MAVLINK1"

mavlink1 is not forwards compatible with mavlink2.

Really sould upgrade everything to mavlink2..