Primary CAN troubleshooting tips

The below can be used in troubleshooting the CANmod primary CAN (DB9).

Check your basic setup

  1. Check your pinout: Verify that your CANmod, adapter cable and application pinouts match
  2. Check your wiring: Confirm that the CAN L/H wires are both connected
  3. Check your power supply: Verify that you provide a 7-26V power supply to the DB9 connector
  4. Check that the green PWR LED lights up when power is provided
  5. Check that the CAN bus is properly terminated (incl. if the device termination should be on/off)
  6. Check that another CAN node is actively acknowledging CAN frames from the CANmod

Check your Configuration File

  1. Ensure that you are using a valid Configuration File created via the editor
  2. Ensure that the Configuration File is named correctly[1]
  3. Ensure that the configured CANmod bit-rate matches your application CAN bus
  4. Ensure that at least some CAN messages are enabled in the Configuration File

Check your CAN recording device

  1. Double check that you’ve correctly setup the recording device
  2. If using a CANedge, see our guide on using the CANedge with a CANmod[2]
  3. Ensure that the recording device does not apply filters and is not in ‘silent mode’
  4. Ensure that you are not applying a DBC file during the evaluation[3]

Try USB streaming via SavvyCAN

  1. Test if you are able to stream data via SavvyCAN as per our guide

Contact us

If you’re still unable to record data, please contact us. In this case, please share the below:

  1. Full details on your CANmod installation setup incl. pictures
  2. Details on the power supply, termination and adapter cables
  3. The CANmod Configuration File you’re using and a screenshot of your CONFIG volume
  4. Detailed explanation of your observed vs. expected behavior
[1]If you’re e.g. using FW 01.03.01, the Configuration File must be named config-01.03.json as explained in the CANmod Docs.
[2]See our CANedge Intro (Record/CANmod section)
[3]Some recording devices/software may directly attempt to DBC decode the data from the CANmod. It is generally best to avoid this during troubleshooting and instead determine if the raw CAN frames are coming through as expected