The following is a guide on common reasons why things in the car can fail. This wiki page is designed to be flexible and flowing, new entries can be added whenever new situations come to light.

• Check the CAN network for proper connection
• Check the terminating resistors of the CAN network
• Use GDB to verify that messages should have been sent
• CAN might need to be started in software
• If CAN messages seem to work individually, but act up when the board is integrated with other boards, check the firmware versions and make sure they are the same.

• Check that the USB wire is a data sending wire (not just power), and that it appears as a device on the pi (usually /dev/ttyUSB)
• Check that Hermes is looking at the correct serial port with the correct baudrate configured (115200)

• Use telemetry views to see if driver controls is telling the lights board to turn on a light, and if the lights board thinks that light is turned on (Lights status)
• Check if the light is plugged in correctly, and if there is no damage to the lights board connections

• Check battery status to see if the voltages, currents, and temperatures are too high/low

• Make sure motors are plugged in and connected to the CAN network
• Check driver controls to see if the pedals are registered properly
• Plug into the motor controller with the CAN ethernet bridge to see what's up, use the bridge configuration software

• Always make sure code is up to date

• Use the test tool to see if any messages can get through
• Check the data dongle on the car to see if there is still data
• Check the rabbitmq logs on the pi (/var/log/rabbitmq) for any errors
• Check the rabbitmq logs on the server (/var/log/rabbitmq) for any errors

• Check if it overheated