Using CANtrip

CANtrip

A two-minute how-to, from install to first capture

v1.5.0 - Yukari · Windows · no hardware needed
0:00 / 1:58

    The interface is redrawn from CANtrip v1.5.0's own labels and layout, and the traffic is what its built-in synthetic source sends. Sending frames needs a real PEAK or Vector adapter.

    Transcript
    1. Using CANtrip. Install, capture, decode, plot, send and log. No hardware needed to follow along.
    2. Install it once. Install Wireshark (Npcap is not needed). Unzip the CANtrip release anywhere. Copy can2pcap.exe into %APPDATA%\Wireshark\extcap\, and copy it again after every update. Launch cantrip.exe.
    3. Find your way. Home: display mode, display rate and runes. Hardware: channel, bus timing and bus load. Analysis & Measurement: DBC import, trace and graphs. Logging: record and replay. Stimulation: send frames. Start and Stop stay pinned on every tab.
    4. Pick a channel and bus timing. Choose a channel; the synthetic source needs no hardware. CAN Controller sets the mode, bitrate and sample point and computes the timing registers. Uncheck Request bus configuration to listen only. Autodetect tries the classic CAN presets on real hardware.
    5. Start capturing. Press Start. Waterfall puts every frame on its own row, newest first, with bus errors in red. Periodic keeps one row per ID. Display Rate limits redraws; logging still gets every frame.
    6. Decode with a DBC. Import DBC on the Analysis & Measurement tab; sample.dbc ships with the release. Frames show their message names, and expanding a row shows its signals in real units.
    7. Plot signals live. Open Graphics, add a Y axis and drag signals onto it in the Axes list. Ctrl-click several to drag them together. The cursor tool reads values and measures deltas. Up to six graph windows; export as PNG, SVG or PDF.
    8. Watch the bus load. Bus Load on the Hardware tab shows a live gauge, a history graph, statistics and a per-ID table. The synthetic source uses about 0.5% of a 500 kbit/s bus.
    9. Send frames. With a PEAK or Vector adapter: New Message sets the ID, length and data, FD frames go up to 64 bytes in a grid editor, cycle time 0 sends once. Start Sending runs cyclic messages, Send Now fires the selected one, and your own frames come back tagged TX.
    10. Log it, replay it. Pick .asc or .csv, set the filename template, splitting and auto-start under Other options, then Start. Start Replay plays a saved log back through the same views.
    11. Save it as a Rune. Save Rune writes your whole setup to one .rune file; Load Rune restores it.
    12. Or run it headless. The same capture runs from a terminal with --headless, for CI and test benches.
    13. That's the tour. Documentation at avmolaei.github.io/CANtrip, including troubleshooting. Source at github.com/avmolaei/CANtrip.