CANtrip v0.2 - Dawn

Highlights

Vector Informatik hardware support. Added a full backend for Vector's XL Driver Library (VN-series interfaces), alongside the existing PEAK backend. Verified against a real Vector VN1640A: all 4 channels plus Vector's virtual channels enumerate correctly, and live capture runs stable through the app.
Verified against real hardware. Both the PEAK PCAN-USB FD and Vector VN1640A were tested against actual devices this release (previous release was verified only via the synthetic test source).
Fixed a real correctness bug in the PEAK backend. The vendored PCAN-Basic header had incorrect parameter IDs and forced byte-packing on structs the real driver expects at natural alignment — the latter caused an out-of-bounds write on every real CAN_Read/CAN_ReadFD/channel-enumeration call. Fixed and verified against a real PCAN-Basic 5.1 driver.
Fixed capture failing against real device names containing spaces. Interface IDs are now sanitized before being used in tshark's -i/-o arguments (a real device name like "PCAN-USB FD" was breaking tshark's preference parser).

Sortable columns. Click a column header to sort, click again to reverse. ID/DLC/Data sort by actual value, not text.
Two display modes, switchable from a dropdown:
- Waterfall — a scrolling log, newest frame on top.
- Periodic — one row per CAN ID, updated in place, grayed out after 2 seconds without a new frame.
Bus error detection. Errors (stuffing, form, bit, overload, etc.) decoded from the real SocketCAN error-frame protocol and shown in red. In Periodic mode, errors aggregate per error type instead of flooding the view.
Application icon.

CAN FD has not been tested against real hardware (PEAK supports it in code; Vector does not implement FD yet).
No Kvaser or ETAS backend yet.
Graphing, message transmission, and gateway mode are still deferred to a later phase.
No automated test suite.

cantrip.exe, pcan2pcap.exe, all required Qt/dbcppp runtime DLLs, and test/sample.dbc for trying DBC decoding immediately.