CAN troubleshooting
An expected CAN frame is absent from live traffic or a BLF, ASC, or CAN dump recording. This guide helps establish whether the failure is in observation, transmission, routing, interpretation, or the bus itself.
Start the diagnostic workflowObservable symptoms
A CAN ID expected from the problem description is absent when the bus is observed over the reproduction interval. This differs from a decoding issue because the raw frame is missing rather than merely showing an empty or implausible signal.
The expected CAN ID appears during some intervals but has gaps, changed repetition behavior, or disappears under a specific vehicle state. This distinguishes a conditional sender or routing issue from a consistently incorrect DBC interpretation.
The expected CAN ID is visible in a CAN dump or recording, but the signal is not shown as expected after applying the DBC. This points toward message or signal definition mismatch rather than a missing CAN frame.
The expected ID is present in traffic near the sender but absent on the connected segment. This pattern makes network gateway routing or gateway conditions more likely than a sender-side transmission failure.
Possible causes
The recording may cover the wrong bus, interval, or traffic view, or the expected frame may be excluded by the capture setup. The system can be transmitting correctly while the evidence appears to show a missing message.
The sender may transmit only after a vehicle condition, operating state, or reproduction step is reached. If that condition is absent, the expected periodic or event-driven frame will not be placed on the CAN bus.
A gateway may route the frame only for selected network states or may not have the expected route active. The frame can therefore exist on the source segment while remaining absent from the destination segment.
If the traffic uses CAN-FD characteristics but the observation path interprets it as ordinary CAN, the expected frame may be rejected, misclassified, or omitted from the recorded result.
Physical or communication problems can prevent reliable frame transmission or reception, producing gaps and inconsistent observations rather than a clean, repeatable absence. This requires correlation with the bus trace and the reproduction conditions.
An incorrect message identifier, node association, or DBC version can make a present frame appear absent from a decoded view. Raw CAN traffic must be checked before treating a DBC result as evidence of missing transmission.
Ordered investigation
Use the problem description to record the expected CAN ID, expected occurrence or condition, bus location, reproduction interval, and whether the claim comes from raw traffic or a decoded view. This prevents a signal-definition issue from being treated as a transmission failure.
Inspect the complete CAN dump or recording for the expected identifier during the exact reproduction interval. Compare the result with the decoded view; if the raw frame exists, the primary issue is interpretation or filtering rather than message transmission.
Check that the recording represents the intended bus traffic and that CAN or CAN-FD traffic is being interpreted consistently with the expected message. This rules out a large class of capture and protocol-selection errors before vehicle changes are made.
Where a network gateway is involved, compare traffic on the segment containing the sender with traffic on the destination segment under the same condition. Presence only on the source side narrows the investigation toward gateway routing or gateway state.
Repeat the defined vehicle or system condition while monitoring the expected ID over a sufficient interval. Determine whether the sender transmits consistently, only after a state change, or not at all; this rules out assumptions about when the message should exist.
Review the trace for gaps, inconsistent timing, and other communication disturbance indicators around the failure, then compare them with a known working interval if available. This cannot by itself identify a physical root cause, but it separates a broader bus problem from an isolated sender or route issue.
Only after raw presence is established, compare the observed identifier and payload interpretation with the supplied DBC. Correct the database or decoding workflow if the frame is present but the expected signal or message is represented incorrectly.
Verification gates
Search the complete BLF, ASC recording, or CAN dump for the expected CAN identifier during the stated reproduction interval.
The identifier appears at the expected condition or repetition behavior.
If it is absent, continue with recording, sender-state, gateway, and bus checks; do not conclude that the DBC is the cause yet.
Select an observed raw frame and compare its identifier and payload with the message selected in the DBC-based view.
The raw frame maps to the expected message without an identifier or message-selection discrepancy.
A present raw frame with no expected decoded message indicates a DBC or decoding mismatch rather than a missing transmission.
Measure whether the expected identifier appears throughout the interval in which the system is expected to transmit it, and compare gaps with the problem description.
The frame appears consistently when its stated transmission condition is active.
Conditional or intermittent appearance directs attention to sender state, gateway state, or communication disturbance.
Read the same reproduction interval on the bus segment before and after the network gateway, using matching time context.
The frame is present on each segment where the architecture requires it to be routed.
Presence on the source segment and absence on the destination segment indicates a gateway route, gateway condition, or gateway integration issue.
Compare the expected traffic type with the recording and analysis configuration used to observe the frame.
The observation path handles the traffic using the same CAN or CAN-FD interpretation expected by the system.
A mismatch can cause valid traffic to be rejected or omitted; correct the observation configuration before changing vehicle software.
Compare identifiers, occurrence pattern, and surrounding traffic for the affected condition against a recording in which the message is known to be present.
The affected capture differs only in the failure condition being investigated.
Broader differences indicate that the reproduction, bus context, or capture setup is not controlled enough for a sender conclusion.
From evidence to action
If raw traffic is present, correct the selected bus, capture interval, CAN or CAN-FD handling, message selection, or DBC association. Re-run the comparison against raw frames to confirm that the apparent absence was an analysis artifact.
If the sender does not transmit when its expected condition is active, inspect the responsible software state and integration inputs with the team owning that node. The resolution may require a software correction, configuration change, or controlled vehicle reproduction rather than a change to the analysis workflow.
If the frame exists on the source segment but not the destination segment, review the network gateway route and the conditions controlling that route. Gateway software or configuration changes may require the vehicle integration or OEM team responsible for the affected network.
If multiple expected frames show gaps or inconsistent behavior, preserve the recordings and compare affected and working intervals before replacing components or changing message definitions. Vehicle-level electrical or communication investigation may be required, with the final corrective action owned by the appropriate vehicle or supplier team.
FAQ
Diagnostic support
Need a focused review of a missing CAN frame? Share the available recording, CAN dump, DBC, and reproduction details for an evidence-based engineering analysis.