CANtrip v1.3.0 - Yukari

CANtrip v1.3.0 - Yukari

The logging update! Logging finally lands, and the Graph view grows up: export, and real
multi-window support.

Logging

• Capture straight to disk in two formats:
  • .asc — built to be indistinguishable from real Vector CANalyzer
    output structurally (header block, trigger blocks, classic and CAN FD
    frame lines with DBC-resolved names). The one deliberate omission is
    the Length/BitCount telemetry suffix some CANalyzer configs show —
    that field is genuine hardware-measured transceiver timing no vendor
    API exposes, so CANtrip targets the equally-real "baseline" ASC
    variant instead of fabricating a number. Verified by opening a
    stripped real CANalyzer trace back in CANalyzer itself with no visible
    difference.
  • .csv — CANtrip's own schema (time, channel, ID, flags, DLC, data,
    resolved message name).
• Filename templating — [user]/[bus]/[date]/[time] tokens,
  editable live with a preview, default output folder
  Documents/CANtrip/captures.
• Logging options — max file size with auto-split, existing-file
  policy (overwrite/auto-increment/prompt), and auto-start-with-capture.
• Log Replay — load a saved .asc/.csv back in and it feeds the
  Trace and Graph views exactly like a live capture, paced by the
  original timestamps.

Graph view: export + multi-window

• Export any graph to PNG, SVG, or PDF from a new button right on the
  chart's own toolbar. Default output folder Documents/CANtrip/graphs.
• Multiple graph windows — up to 6 at once, each fully independent
  (own signals, own axes), all reading from the same live capture.
• Stacked or Grid layout, toggled with one button — Stacked gives
  every pane a real, readable height and scrolls for the rest rather than
  squishing everything to fit; Grid auto-arranges into a square-ish grid.
• Export All — one click exports every open graph window to its own
  file in a chosen folder.
• .rune config files now save/restore the full multi-window layout
  (old single-graph rune files still load fine).

Also in this release

• No more console window popping up next to the GUI on launch.
• The About dialog now shows the actual running version and codename
  (CANtrip - v1.3.0 "yukari") instead of a static string.
• Logging moved ahead of Stimulation in the ribbon tab order.

Known limitations

• .mf4 export is still a disabled placeholder — real ASAM MDF4 support
  is a bigger undertaking, tracked for later.
• Bus-error frames aren't written to .asc output (no verified mapping
  from CANtrip's error classes to CANalyzer's chip-status convention
  exists yet).
• CAN FD real-hardware logging wasn't field-tested this round (no bus
  stimulus available) — the synthetic test source and structural format
  verification are covered, but treat real-hardware FD logging as
  unverified until confirmed against actual traffic.

Getting started (step by step)

CANtrip doesn't capture CAN traffic itself - it hands that job to
Wireshark's own capture engine, then decodes and displays what comes back.
So there are two things to install, not one. Here's the whole path from
zero to seeing live CAN data, no hardware required:

1. Install Wireshark. Download and install it from
   wireshark.org using the
   defaults. You don't need to know how to use Wireshark itself - CANtrip
   just needs it present on the machine, since it runs Wireshark's tshark
   under the hood instead of talking to hardware directly.

2. Download CANtrip. Grab the latest zip from the
   Releases page and
   extract it anywhere (e.g. your Desktop or C:\CANtrip).

3. Tell Wireshark about CANtrip's capture helper. Inside CANtrip's
   extracted folder there's a file called can2pcap.exe - copy it into
   Wireshark's personal extcap folder: press Win+R, type
   %AppData%\Wireshark\extcap, and press Enter - this opens the exact
   folder directly (Windows creates it automatically if it doesn't exist
   yet). Copy can2pcap.exe into it.

   This is a one-time step. Without it, CANtrip's hardware/test-source list
   will simply be empty.

4. Launch cantrip.exe from the extracted folder.

5. Pick a source. On the Hardware tab, open the "Network Hardware"
   dropdown:

   • No CAN adapter yet, just want to try it out? Pick
     "CANtrip synthetic test source (no hardware needed)" - it fakes
     realistic traffic so you can explore everything below with zero wires.
   • Have a real PEAK or Vector CAN adapter plugged in (with its driver
     installed)? Pick that channel instead - everything else works exactly
     the same way.

6. (Optional) Set the bus speed. Still on Hardware, click
   CAN Controller... if you need to change the bitrate (defaults are
   fine for the synthetic source).

7. (Optional) Load a DBC file so raw frames decode into named signals
   with real units. On the Analysis & Measurement tab, click
   Import DBC... and pick a .dbc file - the bundled sample.dbc
   matches the synthetic source out of the box.

8. Hit Start on the Home tab. Live frames start streaming into the
   table immediately; click the arrow next to a row to expand it into
   decoded signal values (if a DBC was loaded). Try the Graphics button
   to switch to the Graph view and plot a signal over time. On a busy real
   bus, use the Display Rate dropdown (also on Home) if the UI feels
   sluggish - it defaults to 30 Hz, which should be smooth on most buses.

9. (Optional) Log the capture to disk. On the Logging tab, pick a
   format (.asc to open later in real CANalyzer, or .csv for
   spreadsheets/scripts), optionally click Output file... to choose
   where it's saved (defaults to Documents\CANtrip\captures), then hit
   Start Logging - it runs independently of Start/Stop Capture, so you
   can start/stop it whenever you want during a session. Load a saved log
   back in later with Log Replay, on that same tab.

That's the whole loop - swapping the synthetic source for real hardware
later needs no extra setup beyond having that vendor's driver installed.
See the README for further
detail.