Flight Mode Unknown 1:655360 and Unknown 129:655360

PX4 Autopilot
1

Was running PX4 in SITL and encountered these mid-flight and after disarming. It has never happened since so it’s not a problem for now but just curious what could be the cause of it. Seems that it might be the enum for flight mode?

129:655360
129:6553601296×2304 312 KB

1:655360
1:6553602304×1296 340 KB

2

What’s your QGC version? Have you tried the latest one?

3

Also, what is the PX4 version.

I would guess that this is recent PX4 that uses standard modes, but SITL is outputting a custom mode for which no AVAILABLE_MODES was emitted. Is there a way to work out what mode 655360 corresponds to?

4

Thanks for the reply, it’s version 4.3

5

Thanks for the reply, it is a fork of v1.15. Maybe it’s an added number from a mixture of modes? Not too sure about it

6

You can also see this happen if you send mavlink messages in an incorrect format and type. Definitely done it on prototyping hardware peripherals and custom modes. Sometimes it garbles out stuff like that and I’m sure there’s actually to some logic behind it but it goes away every time you get the code in order.

1 Like
7

I suspect it might be some buffer overflow on some custom message I sent