ESC Status Toolbar

[dakejahl]

Toolbar icon for ESC status. Requires reception of ESC_INFO and ESC_STATUS mavlink messages.

TODO

• clean up messy claude logic in qml code
• any way to have a vector/array of facts instead of first/second/third/etc naming?
• test with 8 motors
• add RPM to Ardupilot MotorComponent
• test with Ardupilot

Closes #12947

[Davidsastresas]

Thanks Jake, I will try to take a look at it this week

[Davidsastresas]

About the vector thing, I think if you check how batteryfactgroup is done we could do something similar maybe here

[DonLakeFlyer]

About the vector thing, I think if you check how batteryfactgroup is done we could do something similar maybe here

Yup

[DonLakeFlyer]

@dakejahl Can you add screenshots?

[dakejahl]

Added screenshots to the PR description

[dakejahl]

The "max temp" and "max current" are just what QGC has seen... I'm not sure if it's that useful. If we cared about max values the FC should report that explicitly.

[DonLakeFlyer]

@dakejahl Do you mind if I take over the ESC_STATUS and ESC_INFO telemetry handling part of this? I'd like to create a generic FactGroup list mechanism which will handle multiples. The battery FactGroup code already has most of what is needed, it's just not done in a fully generic way. If so, just sit on this for a bit and I'll create the telemetry backend for all of it. Then you can adjust the rest to that.

[dakejahl]

I would love if you did that! Thank you! I will rework this as needed once you have the backend implemented

[dakejahl]

I've also got a PR here for adding a new mavlink message ESC_EEPROM. This would just be an array of uint8.
https://github.com/mavlink/mavlink/pull/2324/files

Similar to BatteryFactGroup should I just use a uint8 pointer Fact and allocate an array?

[DonLakeFlyer]

Sorry for the delay, I was out of town. I'll get this done by end of day today.