I've tried to modify MinimOSD-Extra to show me current APM Copter 3.3 status message on screen. The problem is that I get only couple of messages at startup and then it stops.

This is how I approximately do it:

case MAVLINK_MSG_ID_STATUSTEXT:
{
mavlink_msg_statustext_get_text(&msg, osd_warning);
int length = strlen(osd_warning);
memset(osd_formatted_warning, 0x20, WARNING_PANEL_WIDTH);
memcpy(osd_formatted_warning, osd_warning, length);
};
break;

What happens is that on startup I do get:
Calibrating barometer

Ground start

However if I launch QGroundStation then I see that it gets other messages like "PreArm: GPS horiz error 9.0".

The subscription code looks like this:

void request_mavlink_rates()
{
const int maxStreams = 6;
const uint8_t MAVStreams[maxStreams] = {MAV_DATA_STREAM_RAW_SENSORS,
MAV_DATA_STREAM_EXTENDED_STATUS,
MAV_DATA_STREAM_RC_CHANNELS,
MAV_DATA_STREAM_POSITION,
MAV_DATA_STREAM_EXTRA1,
MAV_DATA_STREAM_EXTRA2};
const uint16_t MAVRates[maxStreams] = {0x02, 0x02, 0x05, 0x02, 0x05, 0x02};
for (int i=0; i < maxStreams; i++) {
mavlink_msg_request_data_stream_send(MAVLINK_COMM_0,
apm_mav_system, apm_mav_component,
MAVStreams[i], MAVRates[i], 1);
}
}

Should I do some extra steps in order to get status text messages?

-----------------------

Update from my experiments:

It looks as if some statustext messages are not set to all GCSs, but the presence of e.g. MAVProxy GCS triggers broadcasting to all stations. Looking at the arducopter code I don't see anything which could trigger such behavior. I do see different ways of sending messages e.g. 

const char *reason = ahrs.prearm_failure_reason();
if (reason) {
GCS_MAVLINK::send_statustext_all(MAV_SEVERITY_CRITICAL, "PreArm: %s", reason);
} else {
gcs_send_text(MAV_SEVERITY_CRITICAL,"PreArm: Need 3D Fix");
}

but those methods look ok internally at first glance.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • I have same problem with my Mav2Leds project, I can't get the severity info to manage my leds when prearm errors occurs.

    Found any solution ?

    • My workaround was to send hearbeats to Pixhawk from OSD.

  • OK, after some more experiments I've fixed (or workarounded the issue in my forked Copter-3.3 version): https://github.com/diydrones/ardupilot/issues/3513

  • The interesting this is that if I connect MAVProxy as well, I see all statustext updates via MiminOSD!

  • I've also added a code to display me number of times I've got MAVLINK_MSG_ID_STATUSTEXT and it stuck at 4.

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @SmallpixelCar: First time at @wsraceways. After tuning @HokuyoUsa lidar signal and camera sensor on @NVIDIAEmbedded, my car was able to…
Sunday
DIY Robocars via Twitter
RT @breadcentric: The handy bit about racing with self-driving cars is that one can type while the car is racing. Report from #AWSDeepRacer…
Friday
DIY Robocars via Twitter
RT @chr1sa: Our Bay Area @DIYRobocars meetup is now at 2,700 members. Next in-person events (in Oakland) are training day on July 17 and…
Friday
DIY Robocars via Twitter
Videos from the ICRA autonomous racing workshop are now available: https://linklab-uva.github.io/icra-autonomous-racing/
Jun 10
DIY Robocars via Twitter
RT @SmallpixelCar: Prepared race track for Warm Spring Raceways @wsraceways and looking forward to test my new car at RAMS RC @ramsaicar fa…
Jun 6
DIY Robocars via Twitter
RT @f1tenth: Trying out some nasty blocking maneuvers 🏎️🤖 #f1tenth #autonomousracing https://t.co/nMTstsaogM
Jun 5
DIY Robocars via Twitter
May 27
DIY Robocars via Twitter
RT @araffin2: I will talk this Saturday from 18:00 to 19:00 Paris time for the @diyrobocars community about learning to race in hours using…
May 27
DIY Robocars via Twitter
RT @a1k0n: Luckily the infeasible hairpin problem was easily reproducible in simulation and I could test the fix before bringing the car ba…
May 26
DIY Robocars via Twitter
RT @a1k0n: Another problem was that I was over-constraining the car's allowed accelerations, so it didn't think it could turn as tight as i…
May 26
DIY Robocars via Twitter
RT @a1k0n: Breaking the map up into two halves worked, but I had to be more careful about separating the inner track from outer. There's se…
May 26
DIY Robocars via Twitter
RT @a1k0n: Here's a datalog for my fastest lap of the day. Lap timer is tiny window lower-left. https://t.co/myrlWWrKUY
May 26
DIY Robocars via Twitter
May 26
DIY Robocars via Twitter
RT @a1k0n: Here was my car's POV. Man this track is confusing in first-person! After the incident my camera was all scuffed up and I was af…
May 23
DIY Robocars via Twitter
RT @circuitlaunch: Loved seeing so many familiar (masked) faces at Circuit Launch today for our first in person @diyrobocars in over a year…
May 22
DIY Robocars via Twitter
RT @circuitlaunch: Last but not least, mystery guest @BostonDynamics Spot took to the track @diyrobocars He enjoyed the #brazilianbbq too 😂…
May 22
More…