After not being able to find anything with Google I compiled a lookup table below of fault code numbers to fault codes. Shared here for comment, as Im pretty new to VESC, and possibly to help somebody in future if they want to find fault codes using the CSV file in excel or similar.
| Number | Fault Code |
| 0 | FAULT_CODE_NONE = 0, |
| 1 | FAULT_CODE_OVER_VOLTAGE, |
| 2 | FAULT_CODE_UNDER_VOLTAGE, |
| 3 | FAULT_CODE_DRV, |
| 4 | FAULT_CODE_ABS_OVER_CURRENT, |
| 5 | FAULT_CODE_OVER_TEMP_FET, |
| 6 | FAULT_CODE_OVER_TEMP_MOTOR, |
| 7 | FAULT_CODE_GATE_DRIVER_OVER_VOLTAGE, |
| 8 | FAULT_CODE_GATE_DRIVER_UNDER_VOLTAGE, |
| 9 | FAULT_CODE_MCU_UNDER_VOLTAGE, |
| 10 | FAULT_CODE_BOOTING_FROM_WATCHDOG_RESET, |
| 11 | FAULT_CODE_ENCODER_SPI, |
| 12 | FAULT_CODE_ENCODER_SINCOS_BELOW_MIN_AMPLITUDE, |
| 13 | FAULT_CODE_ENCODER_SINCOS_ABOVE_MAX_AMPLITUDE, |
| 14 | FAULT_CODE_FLASH_CORRUPTION, |
| 15 | FAULT_CODE_HIGH_OFFSET_CURRENT_SENSOR_1, |
| 16 | FAULT_CODE_HIGH_OFFSET_CURRENT_SENSOR_2, |
| 17 | FAULT_CODE_HIGH_OFFSET_CURRENT_SENSOR_3, |
| 18 | FAULT_CODE_UNBALANCED_CURRENTS, |
| 19 | FAULT_CODE_BRK, |
| 20 | FAULT_CODE_RESOLVER_LOT, |
| 21 | FAULT_CODE_RESOLVER_DOS, |
| 22 | FAULT_CODE_RESOLVER_LOS, |
| 23 | FAULT_CODE_FLASH_CORRUPTION_APP_CFG, |
| 24 | FAULT_CODE_FLASH_CORRUPTION_MC_CFG, |
| 25 | FAULT_CODE_ENCODER_NO_MAGNET, |
| 26 | FAULT_CODE_ENCODER_MAGNET_TOO_STRONG, |
| 27 | FAULT_CODE_PHASE_FILTER, |
A bit of background; I created a log on my Android device through the Android VESC tool. Connected it to my PC, which cannot run VESC tool due to Open GL graphics error, so I used excel to read the CSV file. After using Power Query to split up the columns I noticed that the error codes where listed as numbers e.g. 0 or 4 hence the requirement for the table below.