Skip to content

WireTAP v0.11.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 05 Sep 00:41
· 332 commits to main since this release
v0.11.2
73ebdf1

Highlights

Multi-bus adapters now offer every bus they have, and serial sessions run with the framing you picked rather than whatever the device profile had saved. Sessions are also more honest about their own state — a device that disappears is reported as an error, and one that has finished no longer claims to be running.

New

  • Choose CAN or CAN FD per bus when you start a session, without changing the saved device.
  • Drag an unused bus onto a running session in Sessions → Visual to start carrying it.

Fixed

  • A multi-bus GVRET offers all of its buses — in the source picker, in the session graph, when added to a running session, and over USB as well as TCP. Pick your device again; no profile changes needed.
  • Re-probe any GVRET you set up while its bus was live — the probe gave up early on a busy bus and reported a single bus. A GVRET that cannot answer the bus-count query at all now connects and carries the buses its profile declares.
  • The source picker's serial settings reach the device: framing, Capture raw bytes, Require valid CRC-16 and the frame-length limits all apply to the session, overriding the saved device for that run. Remove any workaround you made in Settings.
  • A serial session stays a serial session after you frame its bytes, and re-framing no longer leaves a trail of discarded captures behind it.
  • Ticking Enable CAN FD now sets the session up as CAN FD, not just the way the device is shown.
  • Catalogue coverage counts the way the catalogue does — a J1939 catalogue that ignores the sending node's address no longer reports every frame as missing.
  • An unreachable MQTT broker or WireTAP backend fails within ten seconds and says why, instead of sitting in "connecting" for minutes.
  • A failed GVRET bus-count query names the real problem — refused, dropped or silent — rather than blaming the device's firmware.
  • The Modbus poll switch reads the session itself, so every panel agrees and a reload shows the real state.
  • A device saved before the GVRET rename can transmit again, with no change on your part.

See the CHANGELOG for details.

Assets 17
Loading