Passive evidence workbench

J1939 capture diagnostics

Inspect the bytes you recorded before drawing conclusions about an ECU. Four focused tools connect message selection, transport integrity, diagnostic records and network identity.

01 · Select

J1939 PGN Filter Mask Checker

Derive a PDU1 or PDU2 PGN mask and test multiple 29-bit CAN IDs with optional source, priority and destination matching.

02 · Interpret

J1939 DM1 Payload Decoder

Decode a complete J1939 DM1 payload into lamp fields and multiple SPN, FMI, OC and CM records without a DBC file or upload.

03 · Verify

J1939 BAM Capture Checker

Find missing, duplicate and out-of-order J1939 BAM packets in candump or CSV captures and reassemble only consistent observed payloads.

04 · Identify

J1939 Address Claim Analyzer

Analyze J1939 Address Claimed capture history for multiple NAMEs at one source address, address movement and Cannot Claim events.

Start with the question, not a generic conversion

If expected messages are absent, test the PGN filter and its source/destination assumptions. If a diagnostic payload spans several frames, audit its BAM sequence before decoding the reassembled bytes. If addresses appear to change, inspect Address Claimed history separately; a source address is not a permanent physical ECU identity.

No DBC, login or hardware connection required

Paste a small incident window from an authorized capture. These tools do not connect to a bus, request messages, clear DTCs, configure an ECU or upload your input. They use protocol field layouts, not a proprietary fault-code catalog. Site analytics do not receive the pasted fields.

Know when a result must be withheld

A missing or duplicated BAM packet cannot be repaired by a plausible SPN. A legacy diagnostic conversion bit cannot be ignored to produce a familiar number. A lower NAME has arbitration priority but is not proof that a node successfully settled ownership. Each tool keeps those boundaries visible.