Repository navigation
WireTAP v0.11.3
Highlights
Modbus RTU comes into its own: a real RS-485 line — vendor function codes, broadcasts and all — can now be framed, decoded and read back from a WireTAP Backend archive, and Test Pattern can prove a link is really carrying CAN FD.
New
- A WireTAP Backend profile can read a Modbus archive: pick the database, the protocol follows, and each message shows as unit/function with its CRC set apart
- The Query app has a Frame Inventory query — every id a source holds, with counts and first/last sightings, for an archive or a capture
- Serial framing takes vendor function codes and a broadcast tick, or frames every function code on a line you don't yet know
- Discovery's Serial Framing tool names the codes and broadcasts it couldn't frame, and Apply declares them for you
- An agent can hand WireTAP a stream of bytes over MCP (
ingest_bytes) and analyse it with no device attached - Test Pattern's Sweep mode checks every CAN payload length, including the CAN FD ones — the only test that proves a link is really FD
- Test Pattern finds the other end before it starts; a responder can be left running and serves every phase of an Auto suite
Changed
- A backend connection failure says why — refused, timed out, no route, or the gateway's own words
- Framing detection runs the same framer the port does, so its counts and coverage reflect what you will actually get
- The Decoder's Modbus tab uses the current spec's exception names
- WireTAP and the capture server share one implementation of every wire protocol between them
- The
transport_test.pyTest Pattern peer is gone; Loopback mode against a Virtual Device covers it with no hardware
Fixed
- Catalogue coil and discrete-input signals read the coil they name, and the Decoder's Modbus tab no longer shows coils as mangled register values
- Selecting a byte capture in Discovery shows its bytes instead of waiting forever
- Transmitting a CAN FD frame over SLCAN or gs_usb sends the frame you asked for
- A Test Pattern run that lost every frame now reports FAIL, and its extended-ID option really sends extended IDs
CI / Infrastructure
- macOS builds no longer crash in bindgen on the Xcode 27 headers
See the CHANGELOG for details.