Changing flight mode terms

Blue Robotics Software Cockpit
1

Is there a way to change the flight mode terms in Cockpit?

We have “Alt_Hold” which is actually depth hold.

We have “Surftrack” which is actually altitude hold.

I appreciate that these terms likely originate from Ardupilot with drones, where they make sense, but for the ROVs, the world is inverted for these terms, and it confuses everyone I teach to use the ROVs.

2

Hi @3dMB,

That functionality is not yet implemented, but we agree it’s a good idea, and there’s an open issue for discussing/tracking it :slight_smile:

3

We will put some work on that. Should be fairly straighforward.

4

@3dMB I’ve opened a PR implementing human-readable defaults and allowing customization.

image
image700×248 25.7 KB

image
image1468×868 83.1 KB

It should be merged in beta 10 or 11.

5

@rafael.lehmkuhl - you are a good man, thank you!

6

@3dMB the feature is now available in 1.19.0-beta10 :smiley:

To edit the names, just right click the mode-selector widget and click options.

7

@rafael.lehmkuhl probably not related directly to this thread, but 1.19.0-beta10 keeps saying “f bad” on both ROVs. Any ideas?

8

Is there a longer incomplete message just before that? MAVLink STATUSTEXT content has the option to be split between multiple messages, which Cockpit doesn’t handle yet (it just treats them as independent).

9

Is that stored in a log that maybe looked at retrospectively?

10

Hi @3dMB -

This is only a change in what cockpit displays- vehicle logs will reflect the default autopilot names. Changing that would require major firmware modification, especially if done on the fly!!

11

The MAVLINK STATUSTEXT, that @EliotBR refers to, @tony-white ?

12

@3dMB -

Those status text messages are recorded in .BIN logs, so if you see the custom name printing there it will indeed be in the logs. However in a log viewer the flight modes will still be named for the original firmware name when highlighting what mode the system was in at different portions of the log.

13

There are downloadable Data Lake logs that were introduced in v1.19-beta.5, but they don’t record every variable by default, so would be relevant to future recordings rather than past ones.

Beyond that your best bets are the MSG messages in the .bin DataFlash logs from the autopilot (as Tony mentioned), or the direct STATUSTEXT messages included in .tlog telemetry logs (which may or may not be recorded in BlueOS depending on your version and MAVLink routing service). Check the BlueOS Log Browser page for what’s available :slight_smile: