Error log
When the driver detects an error, it logs its human-readable string representation in the non-volatile system log memory. If the log is full, the oldest record is removed.
The log can be printed using log command.
Example output
SC-felix#>log
AUX(err 1, run 8, 25 s): #16445, 46.4932V, 16.6112A, 40.4155C, 16.0112RPM, level E stage 0 pass 0 : phase C positive over-current
Error log structure
The error log string is structured as follows:
| Error Log Field | Description |
|---|---|
| AUX | Source of the log. |
| err 1 | Error criticality. |
| run 8 | Current run from permanents. |
| 25s | Time from controller start. |
| #16445 | Error number. (equals to /driver/error) |
| 46.4932V | Battery voltage at the time of the error. |
| 16.6112A | Battery current at the time of the error. |
| 40.4155C | Controller temperature at the time of the error. |
| 16.0112RPM | Motor speed at the time of the error. |
| level E stage 0 pass 0 : phase C positive overcurrent | Decoded error number. |
note
If you see over-voltage errors (such as 'Input voltage abs max'), but the reported voltage is below the 'Critical voltage' threshold: Controller averages the voltage measurement, nevertheless the over-voltage protection reacts much faster than the averaging speed. Therefore, the error might be raised even though the recorded value is not exceeding the limit.