CAN-FD troubleshooting
CAN-FD frames may be absent, rejected, unstable, or decoded incorrectly in live traffic or recordings. This guide narrows the failure to configuration, timing, compatibility, bus behavior, or DBC interpretation.
Start the diagnostic workflowObservable symptoms
The expected identifier does not appear in a CAN dump, BLF recording, ASC recording, or live CANoe trace. This differs from a decoding problem because the raw frame itself is missing rather than merely showing an unexpected signal value.
CANoe or a recording shows CAN-FD traffic together with communication errors, repeated retransmission behavior, or interruptions. This differs from a missing-message issue because some traffic is present while the exchange is not stable.
Raw frames are present, but the payload or signals do not produce credible values when interpreted with the DBC. This differs from a bus communication failure because frame reception is observable before decoding.
CAN frames are observed on the same communication path, while CAN-FD frames are absent, rejected, or unusable. This pattern points toward CAN-FD-specific configuration, timing, or compatibility differences rather than a complete loss of CAN communication.
A subset of expected CAN-FD identifiers is received while other traffic remains available. This differs from a complete communication failure because the bus path and at least part of the configuration are functioning.
Possible causes
Incorrect termination, long or damaged wiring, excessive stubs, connector faults, ringing, or transceiver delay can leave Classical CAN traffic usable while faster CAN-FD edges fail. Inspect the CANH/CANL waveform and physical topology before treating the symptom as decoding failure.
A supply drop, ground offset, disabled transceiver, or unsuitable transceiver can corrupt dominant and recessive levels or only the faster data phase. Measure power and ground through the failure and confirm that every active participant is CAN-FD capable.
The participants may disagree on nominal bit timing, data bit timing, sample point, synchronization jump width, BRS use, or transmitter-delay compensation. The result can be stable arbitration followed by errors when the frame enters the faster data phase.
The raw CAN-FD frame is present, but the selected DBC does not describe its identifier, payload, signals, scaling, or node information correctly. This produces incorrect decoded values and can be mistaken for a communication failure.
A Classical-CAN-only controller, disabled FD mode, unsupported BRS setting, or incompatible measurement interface can reject CAN-FD frame format while ordinary CAN remains available. Confirm controller and transceiver capability at every participating node.
Ordered investigation
Record the expected identifier, direction, timing of the failure, and whether the symptom is missing traffic, rejected traffic, unstable traffic, or incorrect decoding. This separates a communication observation from an interpretation problem before changing configuration.
Inspect the BLF recording, ASC recording, CAN dump, or live CANoe trace for the expected raw frame before applying DBC decoding. If the frame is present, prioritize interpretation and compatibility checks; if it is absent, continue with traffic and configuration checks.
Verify harness and connector condition and the installed termination against the network design. Measure ECU and interface supply and ground during the failure, then inspect CANH/CANL edges, ringing, and data-phase waveform quality with an appropriate differential probe.
Check whether ordinary CAN traffic remains available while the CAN-FD exchange fails. Working CAN traffic narrows the investigation toward CAN-FD configuration, timing, compatibility, or payload handling rather than a complete loss of the communication path.
Apply the intended DBC only after confirming that the raw frame is present. Compare the identifier, payload length, signal placement, scaling, and node information with the observed frame to distinguish decoding errors from communication errors.
If the sender-side traffic exists but the receiving-side traffic does not, compare traces around the network gateway or other network boundary. Reproduce the exchange in CANoe where possible to determine whether the failure follows the configuration, the traffic path, or the vehicle communication setup.
Verification gates
Search the BLF recording, ASC recording, CAN dump, or CANoe trace for the expected CAN-FD identifier and record whether the frame appears before decoding.
The expected raw identifier appears at the expected part of the exchange, with CAN-FD traffic distinguishable from ordinary CAN traffic.
Treat the issue as a missing or rejected communication path first; inspect configuration, timing, compatibility, and forwarding before changing the DBC.
Compare the observed CAN-FD payload length with the length expected for the message in the DBC or message definition being used.
The observed payload length matches the expected message definition and remains consistent across valid occurrences.
The message definition, sender configuration, or received frame may not correspond to the selected DBC entry; verify the source data and CAN-FD configuration.
With the network safely de-energized, measure CANH-to-CANL resistance and compare it with the installed termination design. During operation, inspect dominant and recessive levels, ringing, and edge placement in arbitration and data phases.
Termination matches the network design and the waveform settles before each configured sample point without excessive ringing or common-mode movement.
Repair wiring, connectors, terminators, topology, grounding, or the affected transceiver before changing message decoding.
Review the same recording or CANoe trace for ordinary CAN messages during the period in which CAN-FD communication fails.
Ordinary CAN traffic either works consistently or fails in the same interval, providing a clear comparison with the CAN-FD behavior.
If both CAN and CAN-FD traffic fail, investigate the broader communication path before treating the issue as CAN-FD-specific.
Decode a confirmed raw CAN-FD frame with the selected DBC and compare its identifier, payload, signal values, scaling, and node information with the raw data.
The DBC selects the intended message and produces values consistent with the raw frame and the expected message behavior.
The failure may be in the DBC or decoding setup rather than communication; verify the DBC version and message definition against the source data.
Measure supply and ground offset at the affected ECU and interface while confirming transceiver enable, FD-operation enable, BRS configuration, and hardware capability.
Power remains within approved limits and every participant supports and enables the observed CAN-FD and BRS behavior.
Correct the supply, grounding, transceiver, controller mode, or interface capability before repeating the failing frame sequence.
From evidence to action
Align the CAN-FD settings used by the communicating participants and CANoe setup, then repeat the raw-frame and error comparison. Preserve the original recording so the change can be evaluated against the initial failure.
Apply the agreed timing values for the CAN-FD communication, including the faster data phase where applicable. Recheck both ordinary CAN and CAN-FD traffic because improved CAN-FD behavior alone does not establish that all communication is healthy.
Use a CAN-FD-compatible participant or configuration when the current participant cannot support the required frame behavior. If the limitation belongs to vehicle or supplied software, the vehicle, supplier, or OEM owner may need to provide the compatible configuration or implementation.
Correct confirmed harness, connector, termination, topology, transceiver, supply, or grounding faults and validate CANH/CANL waveform margin in both arbitration and data phases. Repeat the original BRS and network-load condition before closing the issue.
FAQ
Diagnostic support
Need a focused engineering analysis of a CAN-FD trace, recording, or DBC? Share the available evidence to narrow the failure and document the findings.