When debugging a CAN system, communication errors can be difficult to isolate without visibility into the bus. Issues like improper termination, bitrate mismatches, corrupted frames, missing acknowledgments, or a heavily loaded bus can interrupt communication between nodes and make it challenging to determine the root cause of a failure. Since CAN is widely used in automotive and industrial systems, where nodes share a single bus without a central host, identifying and understanding these error conditions is an important part of validating and troubleshooting embedded systems.
The Komodo CAN Duo Interface provides real-time visibility into the CAN bus, allowing users to capture, monitor, and debug CAN communication. It is a dual-channel USB-to-CAN adapter and analyzer capable of simultaneous active CAN transmission and non-intrusive bus monitoring, with support for CAN bus speeds up to 1 Mbps. Using Data Center Software, users can detect and troubleshoot a wide range of protocol-related issues directly within captured bus activity in real time.
Within the Transaction Log, users can find protocol-related errors and quickly identify abnormal bus behavior and communication failures.
Several common issues can interfere with proper CAN communication, including:
Improper Bus Termination: CAN buses depend on proper termination at the ends of the bus. When termination is missing or the impedance is mismatched, nodes can see corrupted data and a flood of error messages.
Bitrate Mismatch: Every node on a CAN bus needs to be configured for the same bitrate. When one is not, communication may be interpreted incorrectly, resulting in errors and corrupted data.
Bit Errors: A transmitting node also monitors the bus. A bit error generally occurs when the value it reads back differs from the value it sent, such as transmitting a dominant (0) bit and detecting a recessive (1) bit.
Bit Stuffing Errors: To keep nodes synchronized, a transmitter inserts an opposite bit after five consecutive identical bits. If a node detects a sixth consecutive bit at the same level in a portion of the CAN frame where bit stuffing rules apply, a stuff error occurs.
Form Errors: The CRC delimiter, ACK delimiter, and End of Frame are fixed-format fields that are always recessive. If a node detects a dominant bit in any of them, a form error is flagged.
High Bus Load: A bus that is close to saturation raises the risk of added latency for messages.
When a CAN node detects a protocol error, it may transmit an error flag depending on its error state. Other nodes may also detect the resulting error condition, causing the affected frame to be discarded and potentially retransmitted.
When analyzing CAN traffic in Data Center Software, protocol-related issues are identified using error code indicators displayed in the Err column of the Transaction Window. This column lists abnormal conditions that occurred while capturing a transaction. For CAN, there are four protocol-specific error types: B (Bit), F (Form), S (Stuff), and O (Other). Each error packet provides additional information, including the direction of the error (RX or TX), the error type, and the field position where it occurred. The Info tab in the Navigator pane adds the timestamp, channel, bitrate, and error type for the selected packet.
These errors are often associated with issues such as improper termination, bitrate mismatches, noise, or wiring faults. The following sections highlight several common CAN bus issues and how they can appear during debugging.

Data Center Software - CAN data capture in Transaction Window
Data Center Software uses general error codes to identify abnormal conditions during protocol analysis, including:
A “U” Error indicates that a packet or event occurred outside of the expected context. This typically means that the analyzer detected bus activity at an unexpected point during the transaction process.
A “T” error indicates that a capture for a transaction timed out while waiting for additional data. Possible causes of this could be a node stopping mid-frame or wiring issues.
An “M” error indicates that data collection began in the middle of an active transaction. Since the Start of Frame (SOF) and earlier portions of the packet were not captured, the software may not be able to fully interpret the transaction. The first packet may appear corrupted if the Komodo CAN Duo Interface is only able start monitoring a transmission midway.
In addition to general error codes, the Data Center Software can detect protocol-specific CAN communication issues during analysis.
A “B” error indicates that the observed state (level) of a transmitted bit was different from the known transmitted value. Because a transmitting node also monitors the bus, it can detect this mismatch. For example, a node transmitting a dominant (0) bit detects a recessive (1) bit.
An “F” error indicates that a fixed-form bit field contained one or more illegal bits. In CAN, the End of Frame, ACK Delimiter, and CRC Delimiter are fixed-format fields that are always recessive. If a node detects a dominant bit in any of them, a form error is flagged.
An “O” error indicates that an error other than a bit, form, or stuff error was observed on the bus.
An “S” error indicates that a bit stuff error occurred, where more than five consecutive bits with the same level were received. CAN uses bit stuffing to keep nodes synchronized: after five consecutive identical bits, the transmitter inserts a sixth, opposite bit. If any node detects that the sixth bit remains at the same level, an error is broadcast on the bus.
Understanding CAN bus error codes is an important part of identifying communication issues and maintaining reliable system performance. By using the Komodo CAN Duo Interface with the Data Center Software, engineers can capture and analyze CAN traffic, identify protocol errors, and investigate potential causes such as improper termination, bitrate mismatches, and high bus load.
With real-time visibility into CAN communication, engineers can more efficiently isolate issues and validate system behavior during development and testing.