Violations

If an error occurs and is detected by the MCU, it will set a violation to report the error and it may also change to the ERROR or CRITICAL_ERROR state depending on the severity. This information is transmitted over the CAN Bus. Note: The violation numbers may change with updates.

VIOL_NONE	0x00	No violations
STAT_STDBY	0x01	In STANDBY state
VIOL_CAN_TMO	0x02	CAN bus detected offline for more than 100mSec
VIOL_MAXLKAS	0x03	LKAS command is out of range.
VIOL_NOSTART	0x05	First LKAS command is not 0
VIOL_RESET_BOR	0x13	Brown out reset detected
VIOL_RESET_CM	0x14	pin config mismatch.
VIOL_RESET_SW	0x15	software trigger reset
VIOL_RESET_WDT	0x16	internal watchdog timer has fired
VIOL_RESET_IC	0x17	Illegal Condition Device Reset
VIOL_RESET_TRP	0x18	Trap Reset
VIOL_CPU_NUM	0x19	Invalid cpu number
VIOL_EPS_PULSE	0x23	EPS pulse is not received but MCLR is still high
VIOL_CRC_ERROR	0x26	SENT1 received a CRC error
VIOL_FRM_ERROR	0x27	SENT1 received a frame error
VIOL_CRC_CRIT	0x31	SENT1 received too many consecutive CRC errors. TIMode is in ERROR state
VIOL_FRM_CRIT	0x32	SENT1 received too many consecutive frame errors. TIMode is in ERROR state
VIOL_SENSOR	0x33	sensor not responding and the EPS is still requesting. No RX on Sent1 for some time.
VIOL_CANTX	0x34	CAN TX queue is full
VIOL_CAN_ERR	0x35	any other CAN
VIOL_CANDUP	0x36	CAN counter duplicate message
VIOL_CANCS	0x38	CAN checksum error
VIOL_I2C	0x41	I2C queue is full
VIOL_PEND	0x42	I2C pending timeou
VIOL_NACK	0x43	I2C no ack
VIOL_DNACK	0x44	I2C data no ack
VIOL_LOST_STATE	0x45	I2C lost state
VIOL_SKSRT	0x46	I2C stuck start
VIOL_UNKOWN	0x47	I2C unknown
STAT_BTLD	0x51	Enter bootloader mode
VIOL_MAIN_LP	0x53	Out of main loop