Cabana: analyze CAN messages

Cabana inspects raw CAN messages and decodes DBC signals. It is a development tool, separate from normal settings.

Prepare

• Original logs around the event
• Vehicle, year, bus and harness information
• Current branch and commit
• A DBC appropriate to that configuration

A message being present does not establish its meaning, vehicle support or wiring suitability.

Current examples

Use the built cabana executable in a prepared development environment. Source is under openpilot/tools/cabana.

cabana --demo
cabana "<route-name>"

Check current help for --data_dir and --dbc. Commands provided by a public log-view page can also be used.

View CAN on the same network

On the device shell:

cd /data/openpilot
./openpilot/cereal/messaging/bridge

On the PC:

cabana --zmq DEVICE-IP

Current help includes msgq, panda, socketcan and zmq inputs. The historical --stream argument is not mandatory for every current version. The executable's --help and current README take precedence.

Inspection order

Bus → message address → period/counter/checksum → DBC decoding → comparison with vehicle state and time. These examples read and analyze data; they do not transmit CAN commands or write ECUs.

Signal graphs with PlotJuggler · Prepare support logs.

---

Source reference

Reference checked 2026-10-30 · carrot-wip · 10bf0a56.

openpilot/tools/cabana/README.md · docs/user/ko/dashcam-log-sharing.md

The development branch continues to change. Check your device’s branch, commit and current settings together.