Troubleshooting
Automotive troubleshooting workflows
Follow structured, evidence-led workflows for isolating communication, diagnostic, network, and ECU behavior problems
Available troubleshooting
CAN Bus Error Troubleshooting
Diagnose CAN bus errors by correlating error frames, bus-off events, controller counters, recordings, and network configuration evidence.
CAN gateway issue
Diagnose a CAN gateway issue by tracing missing, altered, or misrouted messages across networks and isolating configuration, software, and bus causes.
CAN-FD communication issue
Diagnose CAN-FD communication issues by separating configuration, timing, compatibility, bus traffic, and DBC decoding faults.
DBC Does Not Match CAN Traffic
Diagnose why a DBC does not match observed CAN traffic by separating database version, message layout, bus mode, and decoding errors.
Diagnostic session failure
Diagnose why an ECU rejects or leaves the required diagnostic session by tracing requests, timing, configuration, prerequisites, and security access.
DID read failure
Diagnose UDS DID read failures by separating data definition, session, access, transport, ECU, and response-decoding causes.
DoIP connection failure
Diagnose DoIP connection failure by separating Ethernet, discovery, routing activation, TCP, ECU, and diagnostic data issues.
DTC keeps returning
Diagnose a DTC that returns after clearing by separating persistent faults, event-status logic, diagnostic data issues, and communication problems.
ECU flashing failure with UDS
Diagnose UDS ECU flashing failure by isolating transport, session, security, bootloader, and programming-sequence faults.
ECU Not Responding to UDS
Troubleshoot an ECU that does not respond to UDS requests by checking transport, addressing, session state, network communication, timing, and diagnostic configuration.
Incorrect CAN signal value
Diagnose an incorrect CAN signal value by separating DBC decoding errors, sender data faults, COM configuration, and gateway mapping issues.
Intermittent CAN communication
Diagnose intermittent CAN communication by correlating operating conditions, timestamped recordings, message timing, CAN-FD behavior, and gateway traffic.
Intermittent vehicle behavior with MF4
Diagnose intermittent vehicle behavior in MF4 recordings by correlating signals, timestamps, metadata, and CAN evidence across events.
ISO-TP communication failure
Diagnose ISO-TP communication failure by separating CAN, addressing, flow-control, and timing faults in UDS diagnostic traffic.
J1939 decoding issue
Diagnose unreliable J1939 decoding by separating capture, CAN configuration, DBC definitions, and parameter-group interpretation errors.
Measurement event hard to locate with MF4
Diagnose why a relevant vehicle event is difficult to locate in long or numerous MF4 recordings using structured signal analysis.
Missing CAN Messages
Diagnose missing CAN messages by separating capture, sender, gateway, database, and bus-configuration causes with practical checks.
Network timing issue with CAN
Diagnose CAN network timing issues by comparing message periods, latency, ordering, and timeouts against recordings, DBC expectations, and system context.
OBD data unavailable with OBD-II
Diagnose unavailable OBD-II data by separating interface, CAN communication, ISO-TP transport, ECU response, and diagnostic configuration faults.
UDS request fails
Diagnose failed UDS requests by separating ECU, transport, session, data-description, and security-access causes from bus evidence.
Unexpected UDS Negative Response
Diagnose unexpected UDS negative responses by separating session, security, request-data, transport, and ECU behavior issues.
Unknown signal correlation with MF4
Diagnose unknown signal correlation in MF4 measurements by aligning events, validating DBC decoding, and narrowing signals with repeatable analysis.