loki077
loki077
@rmackay9 I would like to avoid a new parameter but I am not sure of a method where we can know which ESC to expect telemetry for.
@rmackay9 I also wanted to add other failure like dropping of telemetry post arming, RPM not responding to demand from RCOUT, temperature failure, or reporting the error status from ESC...
Tested on our Aircraft, it takes few single digit seconds to push the PRE Arm Error once the ESC is disconnected but clear almost instantly once cleared.
@peterbarker should I keep the instance starting from 0 or 1 to print the Error ?
Already being implemented by #27248 so closing this PR.
@peterbarker @tridge FYI
@Pradeep-Carbonix @robertlong13 FYI
@andyp1per it is a custom APD code which is made for us. There is no document for it. Even if ardupilot don't accept the APDF120 custom implementation we would still...
This is the telemetry Structure : The flags: // Enumeration defining bit positions for each flag typedef enum { overTemp_flag = 0, signalLoss_flag, // 200mS since last throttle packet overVoltage_flag,...
https://github.com/dronecan/DSDL/blob/master/uavcan/equipment/esc/1036.StatusExtended.uavcan#L1