Skip to content

CANtrip v0.4 - Mai

Pre-release
Pre-release

Choose a tag to compare

View all tags
@avmolaei avmolaei released this 05 Jul 18:24
v0.4_mai
1df39f4

CANtrip v0.4 - Mai

A ribbon UI overhaul and real CAN FD bit timing land in this release,
alongside Vector CAN FD support and a capture status indicator.

Highlights

New ribbon-style UI. The old single-row control bar is gone. CANtrip
now organizes everything into tabs across the top, Office-style:

  • Home - Start/Stop capture, Waterfall/Periodic display mode
  • Hardware - pick a channel, open the new CAN Controller dialog
  • Analysis & Measurement - Import DBC, CAN Trace, Graphics (coming later)
  • Stimulation / Logging - reserved for upcoming message-sending and
    disk-logging features
  • About - GitHub link and license info

Real CAN FD bit timing. The CAN Controller dialog replaces the old
free-text "expert init string" field with three proper modes:

  • CAN - classic bitrate only
  • ISO CAN FD - set a target bitrate + sample point, CANtrip computes the
    actual BRP/TSEG1/TSEG2/SJW register values live and shows the achieved
    sample point
  • Expert CAN FD - type the raw register values directly, for full manual
    control

The calculator is ported from python-can's bit-timing implementation and
verified against real PEAK PCAN-USB FD hardware.

Vector CAN FD support. The Vector XL Driver Library backend now
supports CAN FD in addition to classic CAN, verified against a real Vector
VN1640A.

Capture status LED. A small round indicator at the bottom-left of the
window - red when idle, blinking green while a capture is running.

What's Changed

  • Add Vector XL Driver Library backend for classic CAN
  • Fix erratic Periodic-mode timing caused by tshark stdout buffering
  • Add capture status LED indicator
  • Add CAN FD support to the Vector backend
  • Replace inline controls with a ribbon UI and add real CAN FD bit timing

Installation

Grab CANtrip-windows-x64-1df39f4.zip below, extract it anywhere, and
follow the README -
it bundles cantrip.exe, pcan2pcap.exe, and every DLL both need. You'll
still need Wireshark installed (for tshark)
and a driver package for your CAN hardware (PEAK PCAN-Basic or a Vector
driver package) - or skip both and pick the built-in synthetic test source
to try CANtrip with zero hardware.

Assets 3
Loading