Skip to content
This repository has been archived by the owner on Apr 10, 2022. It is now read-only.

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

Open
AndKe opened this issue Apr 5, 2019 · 3 comments
Open

Comments

@AndKe
Copy link

AndKe commented Apr 5, 2019

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

@AndKe AndKe changed the title Using MAVLink 1.0 , makes controller display "calibrating sensors" Using MAVLink 1.0 , makes controller stuck at "calibrating sensors" Apr 5, 2019
@AndKe
Copy link
Author

AndKe commented Apr 27, 2019

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
Copy link
Author

AndKe commented Apr 27, 2019

@Pedals2Paddles - did I post in the right place?

@FLYBYME
Copy link

FLYBYME commented Jun 17, 2019

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..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants