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