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?
What’s your QGC version? Have you tried the latest one?
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?
Thanks for the reply, it’s version 4.3
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
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
I suspect it might be some buffer overflow on some custom message I sent
Hi, I have the same issue, have you solved it? I have no send custom Mavlink massage.
Are you building on top of v1.15 and above? I suspect it might be the new position slow mode introduced in v1.15. Old versions of QGC may not register this mode and display that unknown code instead. For me it doesn’t affect what I am doing so I just ignore it
Agreed. Try QGC v4.4.3.
1 Like
I still see the issue with QGC v4.4.4
I am using v1.15. This specifically happens with Position Slow mode. I could not find where exactly in the code this is taking place. Ideally the QGC version should not affect this since flight mode is a standard message.
Any fix for this?
In the QGC logs:
Flight mode group not set
How do I test this? How do you get Position Slow mode? Sorry, that’s the first time I hear this 
In PX4 v1.15v, Position Slow Mode was introduced. When I shift to this mode, QGC shows unknown flight mode (as seen here).
I can reproduce this with QGC v4.4.4 downloaded but it works with v4.4.4 built on my system, so that’s confusing.
Ok, I’ve found the issue. Back when QGC v4.4.x was initially developed, the standard modes MAVLink spec was still marked as “work in progress” and therefore it was only enabled for developer/daily builds but not for release. This explains why it works locally when I build it in debug build.
I will update MAVLink and get this into v4.4.5.
1 Like
Thank you so much for the update — that’s great news that this will be fixed in v4.4.5!
Is the fix on the QGC side or the PX4 side? If possible, could you please share the details of the fix so I can try integrating it myself while waiting for the official v4.4.5 release?
Thanks again in advance!
QGC side.
Look at the pull request I shared above, that’s all you need.