How malkevich2-ux/scanmatik_logger works
Scanmatik CAN/J1939 Logger is a Windows diagnostic application with two user workflows: passively capture bus traffic to CSV, or actively query ECUs over UDS for identifiers and DTCs. The active tool also monitors traffic, scans visible ECU addresses, supports custom requests, and provides Volvo-reference lookup; saved captures can be decoded into reports. The Python interfaces use a command-line bridge to reach J2534 hardware, while UDS framing, decoding, and DTC reference/reporting form the diagnostic logic. Relationships for unsampled GUI capabilities follow the README; implementation details beyond shown excerpts are not assumed.
Main entry points: can_dtc_reader_gui.py Diagnostic GUI · can_logger_gui.py Logger GUI · dtc_report.py Capture report · Program.cs Bridge runtime
Components 19
Bus capture
- Logger GUI
can_logger_gui.py - CSV capture
can_logger_gui.py
J2534 bridge
- Device discovery
bridge_common.py - Bridge process
bridge_common.py - Bridge runtime
bridge/Program.cs - J2534 API
bridge/J2534.cs
UDS diagnostics
- Live monitor
can_dtc_reader_gui.py - Diagnostic GUI
can_dtc_reader_gui.py - ECU address scan
can_dtc_reader_gui.py - Custom UDS requests
can_dtc_reader_gui.py - UDS request builder
uds_tx.py
Decode and reference
- UDS decoder
uds_decoder.py - ISO-TP reassembly
uds_decoder.py - Volvo DTC reference
dtc_reference.py - Reference data
dtc_reference_ru.json - Capture report
dtc_report.py - Saved capture
logs
Other components
- Operator
- J2534 adapter
Connections 24
- Operator → Logger GUI: starts capture
README.md - Logger GUI → Device discovery: lists devices
README.md - Logger GUI → Bridge process: launches bridge
README.md - Bridge process → Bridge runtime: controls process
README.md - Bridge runtime → J2534 API: calls API
bridge/Program.cs - J2534 API → J2534 adapter: opens channel
- J2534 adapter → Bridge runtime: returns frames
- Bridge runtime → Bridge process: streams frames
bridge_common.py - Logger GUI → CSV capture: writes frames
README.md - Operator → Diagnostic GUI: queries ECU
README.md - Diagnostic GUI → Device discovery: selects device
README.md - Diagnostic GUI → Bridge process: sends commands
can_dtc_reader_gui.py - Diagnostic GUI → UDS request builder: builds requests
can_dtc_reader_gui.py - Diagnostic GUI → UDS decoder: decodes responses
can_dtc_reader_gui.py - Diagnostic GUI → Live monitor: monitors traffic
README.md - Diagnostic GUI → ECU address scan: scans addresses
README.md - Diagnostic GUI → Custom UDS requests: builds custom
README.md - Diagnostic GUI → Volvo DTC reference: looks up codes
can_dtc_reader_gui.py - UDS decoder → ISO-TP reassembly: reassembles frames
uds_decoder.py - Volvo DTC reference → Reference data: loads data
dtc_reference.py - Operator → Capture report: analyzes capture
README.md - Capture report → Saved capture: reads CSV
dtc_report.py - Capture report → UDS decoder: feeds frames
dtc_report.py - Capture report → Operator: shows report
dtc_report.py