Reorder boxmodes for flight mode priority

[breadoven]

Reorders boxmodes to prioritise flight modes within the first 32 entries. This ensures flight modes and more significant modes are included in blackbox flight logs.

Numbering has been removed from the boxId_e enum since it doesn't appear to serve any useful purpose.

Doesn't appear to cause any issues from testing ...

Change affects Blackbox Explorer which will need updating to ensure correct boxmode mapping is used depending on INAV version (Ref Blackbox change iNavFlight/blackbox-log-viewer#101).

[stronnag]

Why not add an additional field to blackbox?

And will you also provide a PR for INAV blackbox-tools as required?

[breadoven]

Why not add an additional field to blackbox?

Do you mean a separate field for actual "flight" modes and another field for all other modes ?

And will you also provide a PR for INAV blackbox-tools as required?

I have something that works. Not sure if it's the best way of doing it ... but it works.

[stronnag]

Why not add an additional field to blackbox?

Do you mean a separate field for actual "flight" modes and another field for all other modes ?

I was thinking of maybe an flightModeFlags2 which would be the remaining modes right shifted 32 to fit into another uint32_t; but maybe that's overkill (and a pain on the consumer side).

And will you also provide a PR for INAV blackbox-tools as required?

I have something that works. Not sure if it's the best way of doing it ... but it works.

There is an example in src/parser.c from then the VBAT stuff changed in the middle of the development cycle (so version and data dependent). Or just ping me when this is merged and I'll do it.

[breadoven]

Why not add an additional field to blackbox?

Do you mean a separate field for actual "flight" modes and another field for all other modes ?

I was thinking of maybe an flightModeFlags2 which would be the remaining modes right shifted 32 to fit into another uint32_t; but maybe that's overkill (and a pain on the consumer side).

I was thinking maybe it's overkill to include all the modes given most of the remainder aren't that useful for debugging etc.

And will you also provide a PR for INAV blackbox-tools as required?

I have something that works. Not sure if it's the best way of doing it ... but it works.

There is an example in src/parser.c from then the VBAT stuff changed in the middle of the development cycle (so version and data dependent). Or just ping me when this is merged and I'll do it.

I'll do a PR for the change I made, take it from there.

[mmosca]

Will this impact 7->8 upgrades? If so, we should mention it in the release notes.

[breadoven]

Will this impact 7->8 upgrades? If so, we should mention it in the release notes.

Shouldn't have any impact on users other than certain modes selections such as Cruise being recorded in log files.

[breadoven]

Replaced by #10093.