◄ Home

Getting Car Unrecognized: Dashcam Mode on your Comma 2, Comma 3, or similar device but have a supported make and model of car? Use the following guides to add support.

Note: You may want to run and check if the latest, unstable, cutting edge, and developer master branch already has your fingerprint. If so, the next stable release of openpilot will likely successfully identify your vehicle.

Getting firmware versions with these instructions requires an official device. Users without an official device can get firmware versions by running some scripts with alternative instructions and then use the car firmware retrieved in place of the instructions for official devices.

Used for all officially supported makes such as Honda, Toyota, and is also supported for Hyundai and Volkswagen.

🙋: Hey! If you need help, consult your make's channel at the comma.ai community discord. Try to at least get to Step 3 on your own though but if you can't, that's OK, go reach out.

Ensure your comma power v2 is hooked up to your car harness. Drive around your neighborhood for a bit, then return to upload the drive on WiFi to the comma servers.

https://my.comma.ai/useradmin

Login to the same account you paired your comma device with.

Click the most recent drive:

Click the first segment (segment 0)

In the log dropdown select carParams

Search the page for carFw = [

If "carFw = [" is empty, please check your harness's CAT5 connection to the comma power that is on the OBD-II port. If it is still empty after another drive, then try reseating and/or flipping the USB-C/ODB-C cable between the harness and your comma device. If the connections look good and it is still empty after yet another drive, check fuses. If that looks good, try a known good CAT5 cable. If that looks good but the entry is still empty and it is after another drive, maybe ask your make's Discord channel for guidance.

SSH into the comma device and navigate to /data/openpilot/selfdrive/car/<car make>. You want to edit the values.py file here.

In your values.py file, add the firmware in this format. Use a decimal to hex converter to get the correct string to place after 0x.

  CAR.MODEL: {
    (Ecu.type, 0xAddress-converted-to-hex, 0xSub-address-converted-to-hex-'None'-if-0): [
      b'fwVersion',
      b'existingFirmware',
    ],
  },

Here is a filled out example for the Honda Civic. Notice the eps firmware from above is already in this list.

  CAR.CIVIC: {
    (Ecu.eps, 0x18da30f1, None): [
      b'39990-TBA,A030\x00\x00',
      b'39990-TBA-A030\x00\x00',
      b'39990-TBG-A030\x00\x00',
      b'39990-TEG-A010\x00\x00',
    ],
  },

Ensure that every single ecu has its firmware in this file.

Save the file and reboot

1. Fork openpilot into your own GitHub account
2. Clone the repo on your computer
3. Navigate to /selfdrive/car/<car make>/values.py and add the firmware from step #4
4. After changes are made, push to your repo
5. Create a pull request to ensure the car is supported in the next release

In general, these instructions are to get the carFw that comma.ai device users would normally get through Comma Connect.

This does not require login to Comma Connect, in case it is down, you are unable to pair, or unable to use:

1. Setup SSH in your device

2. Open one SSH connection/session/window:

cd /data/openpilot/selfdrive/boardd
pkill ./manager.py
./boardd

3. In another connection/session/window:

cd /data/openpilot/selfdrive/car/
python fw_versions.py

4. Start Car when message shows getting Vin then run python fw_versions.py again.

5. Use information from the script outputs like the main set of instructions for fingerprinting 2.0 above as the carFw.

The deprecated version of fingerprinting. Used for most other community supported makes.

Fingerprint 1.0 updates on makes where Fingerprint 2.0 are supported will not be merged into official code. Perform Fingerprint 2.0 on supported makes where possible.

1. Turn off car, connect Panda to car (normally via Giraffe or car harness) and connect Panda to comma device running openpilot.

2. If you have the car harness, disable openpilot in UI settings so that your car is using the stock system. If you have a giraffe, set the switches so that the stock system is enabled. For this procedure you want to collect the messages sent by the stock system, not openpilot.

3. Run these commands in 2 separate sessions (SSH into comma device, run "tmux a" and press "` + c" to create new sessions)...
   in first session run:
   /data/openpilot/selfdrive/boardd/boardd
   in second session run (one line):
   PYTHONPATH=/data/openpilot PREPAREONLY=1 /data/openpilot/selfdrive/debug/get_fingerprint.py

4. Turn on the car's ignition, and wait up to ~20 seconds to ensure all the appropriate DBC messages are seen, like this...

   number of messages 53:
fingerprint 2: 8, 64: 8, 65: 8, 72: 8, 73: 8, 280: 8, 281: 8, 290: 8, 312: 8, 313: 8, 314: 8, 315: 8, 316: 8, 326: 8, 544: 8, 545: 8, 546: 8, 552: 8, 554: 8, 557: 8, 576: 8, 577: 8, 722: 8, 801: 8, 802: 8, 805: 8, 808: 8, 816: 8, 826: 8, 837: 8, 838: 8, 839: 8, 842: 8, 912: 8, 915: 8, 940: 8, 1614: 8, 1617: 8, 1632: 8, 1650: 8, 1657: 8, 1658: 8, 1677: 8, 1697: 8, 1743: 8, 1759: 8, 1785: 5, 1786: 5, 1787: 5, 1788: 8, 2015: 8, 2016: 8, 2024: 8

5. Turn on and off the car few times (some messages are only sent on start) and run the car for at least a minute to make sure all messages are received.

6. <CTRL> + C to break out of the process.

7. Copy the DBC messages obtained in step 4 into the "FINGERPRINTS" section of
   /data/openpilot/selfdrive/car/<car make>/values.py
   Create new sub-section for car or overwrite pre-existing fingerprint of similar car.

8. Turn off car's ignition, then reboot comma device.