Statustext not showing up in Mission Planner

I have a strange problem as no statustexts I send with Raspberry to Cube usb line are not showing up in Mission Planner messages tab. Indications send by autopilot are received and shown correctly there.

Here an example of statustext, I see with Wireshark with Mission Planner connected by UDP.
This text does not show in Mission Planner HUD and neither in the messages tab.
STATUSTEXT::
0000 84 c9 b2 d6 84 a6 dc a6 32 67 8c 2b 08 00 45 00 …2g.+…E.
0010 00 34 16 ab 40 00 40 11 9f e0 c0 a8 01 75 c0 a8 .4…@.@…u…
0020 01 68 38 d7 f0 cd 00 20 42 66 fd 0c 00 00 08 01 .h8… Bf…
0030 08 fd 00 00 00 73 74 61 74 75 73 20 74 65 78 74 …status text
0040 b8 25 .%

Indication of throttle sent by Cube autopilot is displayed correctly when arming the plane.

example message here
AUTOPILOT STATUS message::
0000 84 c9 b2 d6 84 a6 dc a6 32 67 8c 2b 08 00 45 00 …2g.+…E.
0010 00 57 b7 b0 40 00 40 11 fe b7 c0 a8 01 75 c0 a8 .W…@.@…u…
0020 01 68 38 d7 f0 cd 00 43 3b 30 fe 33 62 1f 01 fd .h8…C;0.3b…
0030 06 54 68 72 6f 74 74 6c 65 20 61 72 6d 65 64 00 .Throttle armed.
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0060 00 00 00 74 c9 …t.

What could be reason for this? Statustext message is using source_system = 1 as you can see from example. srcComponent is set as 3. Which I assume is Cube component number.

My Raspberry sw is the same as 6 months ago, when this was fully working. Now I am using latest version of Mission Planner and Arduplane. Both of those have been updated since I las tested the statustext functionality.

Thanks.

so the packet is valid

image

but it doesnt show in MP because you dont have the sysid/compid selected

ie sysid 1, compid 8

if you select that sysid/compid in MP it will show on the message tab

you can verify with “mavlink inspector”

also does your rpi send heartbeats?

I have used sysid = 1 and tried multiple different compid’s but nothing worked. 6 months ago it was working with sysid = 1 & compid = 3. I did also try with sysid =1 &compid = 8. Thanks for noting the mavlink inspector. I have not used that before. Rpi is not sending heartbeats. I can add that if necessary - perhaps only after sending multiple hearbeats, the statustext will work?.
Have there been any changes to Arduplane or Mission Planner recently that might cause issues here , because earlier I had no problems in getting the texts to HUD?

And thanks for showing the structure of statustext. Header is actually 4 bytes longer that for other mavlink messages and statustext messages sent by autopilot.

Now I could finally get text through to Mission Planner. The case is very curious because I had changed Cube id by SYSID_THISMAV changed to 31 = 0x1f. I can get the text through by changing both component id and sysid to 0x1f.

Component ID and system ID seem to be interchanged if comparing autopilot and RPi initiated statustext messages. Autopilot did not convert the message structure yesterday, but today conversion occurred mysteriously.
Autopilot or Misson Planner versions have not been changed. After new boot this strange phenomenon occurred.

Now I get this structure to the RPI originated statustext when system id = 1 and component id = 0x1f It appears now same as autopilot originated statustext except that system id and component id’s are in reversed positions

0000 84 c9 b2 d6 84 a6 dc a6 32 67 8c 2b 08 00 45 00 …2g.+…E.
0010 00 57 6b 85 40 00 40 11 4a e3 c0 a8 01 75 c0 a8 .Wk.@.@.J…u…
0020 01 68 38 d7 fe f5 00 43 e6 66 fe 33 04 01 1f fd .h8…C.f.3…
0030 02 73 74 61 74 75 73 20 74 65 78 74 00 00 00 00 .status text…
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0060 00 00 00 8f ef …

When I set both sys if and componet id = 0x1f, then the message is accepted in Mission Planner. I.e. This format is ok:

0000 84 c9 b2 d6 84 a6 dc a6 32 67 8c 2b 08 00 45 00 …2g.+…E.
0010 00 57 fa fb 40 00 40 11 bb 6c c0 a8 01 75 c0 a8 .W…@.@…l…u…
0020 01 68 38 d7 fe f5 00 43 15 b2 fe 33 08 1f 1f fd .h8…C…3…
0030 02 73 74 61 74 75 73 20 74 65 78 74 00 00 00 00 .status text…
0040 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …
0060 00 00 00 26 bc …&.

Now the text field is constant in both cases.
Yesterday RPI originated statustext used variable length as shown in my first message in this chain.

So now I know how to get text through, but all of this seems very confusing.

Now i have tested this case more thoroughly and decided to give more details how it works. So to make it short:
Statustext to Mission Planner HUD works ok if Raspberry uses autopilot system id as source system id.
That id is of course changed whenever autopilot SYSID_THISMAV is changed - so it would be better to interrogate that first and use it. For source component id, any other id works except 1.