Arm status

[r1000ru]

I suggest adding an ARM status to the frame 0x21 Flight Mode, which can be used for voice alerts, timer resets, and other tasks.

Before that, I created an issue about it. It was proposed to supplement the status with reasons for failure, but they may vary and vary depending on the flight controllers.

For message about problem, i suggest add "message" frame

[haslinghuis]

Suggest splitting the PR into

• adding arm status
• adding airspeed sensor

In Betaflight we use Flight Mode flag to indicate arm status

• betaflight/betaflight@698b861

[bkleiner]

Airspeed changes are caused by a rebase on our end and were not originally introduced in this PR

[JimB40]

• adding arm status
  @haslinghuis could you have a look at discussion in ARM, FS, RemoteID #17 and comment. Thx

[bkleiner]

I dislike the idea of „glueing“ this information onto a existing frame. @JimB40 idea of creating a dedicated payload seems more suitable in my mind. @JimB40 would you like to come up with a PR for this?

[haslinghuis]

• See current implementation (in BF) for 0x21 Flight Mode payload: CRSF Flight Mode Sensor Value update betaflight/betaflight#13854

[JimB40]

• See current implementation (in BF) for 0x21 Flight Mode payload

I know this. We worked together to improve it. :)
In above mentioned #17 we work to separate "Arming Status" from 0x21 frame and move it to a new unique CRSF frame.

[JimB40]

I dislike the idea of „glueing“ this information onto a existing frame. @JimB40 idea of creating a dedicated payload seems more suitable in my mind. @JimB40 would you like to come up with a PR for this?

Frame 0x23 Arming status?

[bkleiner]

I dislike the idea of „glueing“ this information onto a existing frame. @JimB40 idea of creating a dedicated payload seems more suitable in my mind. @JimB40 would you like to come up with a PR for this?

Frame 0x23 Arming status?

Jup. Basically put what you describe in #17 into a PR.

[r1000ru]

Hi. Is there an understanding of whether there will be a separate frame for the ARM status and the reason for its failure? I would like to draw your attention to the fact that if the reasons are given by a bit field, it would be nice to have a flight controller software identifier. Since the lua widget linked to the model can show errors, but behind the hardware (transmission of telemetry via Bluetooth/USB/UART), there is no longer any binding to the model and the application will not be able to process the bit mask correctly.