I’ve discovered a temperature issue with a new ESC - a Skystars KM55A. (thanks to help from folks here) This ESC uses AM32.
As I understand the docs, to enable an ArduPilot ESC temperature failsafe requires the Advanced Failsafe System (AFS) to be included. It read that it’s included in “plane” but not in “copter”.
While ESC telemetry can be received from any ESC with a telemetry port, it seems to me that anyone using the BDshot image is specifically looking to use ESC telemetry - and would likely make use of the advanced failsafes.
Interestingly, when I compare logs from BLHeli_32 copters and my new AM32 copter, BLHeli_32 only reports RPM over BDshot. AM32 reports many more parameters, including temperature.
Meanwhile, if anyone has a current copter image using BDshot and AFS for a Cube Orange they could let me try, I’d really appreciate it.
I am not sure about BLHELI32, but the most basic 8 bit ESCs flashed with Bluejay can report temperature over BDshot.
A failsafe for overtemp for copter is almost useless (what will you do if you a couple of km away?), now if you really want it, just make a short LUA, where you read the temp of the ESCs, and if the Temp goes above a preset value (80 C is reasonable max), the LUA will warn you on the OSD screen through MESSAGE field, and if you still do not respond, than… not sure…maybe flying is not a good idea…
Some BLHeli_32 ESC’s provide extended telemetry, some don’t. It also depends on the firmware rev. Many got caught with 32.9 (or earlier) either because they bought them after the end, didn’t know to update to 32.10 or had the “if it ain’t broke, don’t fix it” mind-set.