Interpreting Driver Errors

get_error_id() returns the selected driver's error cache. Use the definitions below for the actual driver; the same numeric value can have different meanings in different drivers.

DOWN/UP indicate states; the other listed codes indicate their corresponding faults.

LRO interprets the 5-bit error field in type-1 feedback:

EVO codes 0x00–0x10 include definitions related to voltage, drivers, current, temperature, encoders, position/speed, and communication. Codes 0x81–0x89 include encoder, firmware, and gate-driver initialization definitions; 0xFF means unknown.

The CAN-FD implementation maps the underlying fault bitmap to the closest 8-bit code, rather than preserving the complete bitmap without loss. Retain the original source and driver type during diagnosis.

Both source enumerations define codes 0x00–0x09, covering overvoltage, overcurrent, motor/board temperature, undervoltage, encoders, communication, and temperature warnings. They must still be interpreted according to the selected driver's implementation.

RP feedback combines two error bytes, while the public error_id uses 8-bit storage. Python retrieves it through get_error_id(); interpret the result according to the actual driver. These enumerations are not exposed as Python types.

After diagnosing the physical root cause, follow the recovery requirements for the applicable model and firmware. clear_motor_error() / clear_errors() only send clear requests; continue checking feedback and device state afterward.