The CAN bus load is based on the used capacity divided by maximum capacity. For example, the maximum capacity in a 125 KHz rate CAN system is 1 s * 125 KHz = 125000 bits/s. Using the Komodo CAN Duo Interface and the Komodo Software API command km_read(), users can calculate the CAN bus load. Here is an example based on accumulating the data frames and then calculating the bus load:
Call km_read() in a 5-second loop.
Accumulate all the packets returned by the Komodo interface within that time frame.
Use the timestamp of the first packet, which we’ll name t0.
Use the timestamp of the last packet, t1.
Calculate the total capture time t: (t1 - t0) + time for last packet.
Calculate the total number of bits in this time frame, which is based on the data returned by km_read() (total_bits): bus load = total_bits / t * 125000.
An overflow occurs when the Komodo CAN Duo Interface receives asynchronous messages faster than the rate at which they are processed: the receive link becomes saturated. This condition can also affect synchronous communication with the tool. To resolve the saturation, you can either reduce the amount of traffic that is sent by all CAN nodes, or poll the CAN channel to collect pending messages more frequently. You also can use the Komodo Software API to create a wrapper for the asynchronous submit and collect functions by using the command km_can_write. Find out more: How Can I Resolve Buffer Overflow for Asynchronous CAN Messages?
The Komodo CAN Duo Interface has two independent, customizable CAN channels, as well as two virtual USB ports. You can use two instances of the Komodo GUI Software or the Data Center Software (or one of each) with channel A and channel B of the Komodo CAN Duo Interface to monitor two CAN buses separately. Within the Data Center Software, you can select a specific bus to be monitored in Device Settings. Within the Komodo GUI Software, you can select a specific bus in the Connect window. Learn more: How Do I Use One CAN Interface to Communicate and Monitor Two Independent CAN Buses?
The Komodo CAN Interface can monitor your bus and detect errors such as bit errors, stuff errors, and form errors, which may indicate protocol violations, wiring or termination issues, or timing problems. Using Data Center Software, engineers can see which frames caused errors and correlate them with overall bus activity to diagnose and resolve communication issues. Users can observe when and where CAN bus errors occur, and learn more about viewing CAN communication errors.
Simulating and sending custom CAN messages is essential for testing and validating device behavior on a CAN network. With the Komodo CAN Duo Interface and the Komodo GUI Software, users can use General CAN Mode to simulate and send CAN messages. The CAN Control group box offers a way to send customized packets over a CAN bus. Users can enter up to eight bytes of data in the Message field that will be sent to the destination node. Additional options like Extended ID, Remote Request, and One-Shot allow further control over the message format and behavior. All executed commands will be displayed in the Transaction log. Find out more on using this function: Using General CAN Mode in the Komodo GUI Software
Synchronizing CAN data and errors with external test equipment helps correlate bus activity with hardware events for deeper analysis. This can be done using the Komodo CAN Duo Interface’s 8 configurable GPIOs. To sync with a logic analyzer, connect the GPIOs as digital input channels. For an oscilloscope, connect GPIO to one channel, and probe CAN_H/CAN_L on separate other channels to compare signals in real time.
To continuously log and save CAN traffic over time, you can use the Komodo CAN Duo Interface with the Data Center Software to log messages into the buffer and manually save them. However, for long-term data collection without personal attention, you can use a remote telnet console and a script to automate starting the capture, saving the data, and clearing the buffer at intervals. To learn about specific commands, check out this support blog: What Do I Need for Continuously Logging CAN Messages with the Komodo CAN Duo Interface?
Arbitration loss is a normal part of CAN when multiple nodes transmit at once and the lower-priority message yields. With the Komodo CAN Duo Interface, you can analyze this for the Komodo interface’s own transmissions: if it loses arbitration, the Data Center Software will show the retries. While the Komodo interface cannot report arbitration loss for other nodes, this still lets you verify your message priorities and analyze bus contention. Learn more: How Do I Use the Komodo CAN Interface to View Retried Transmissions on the CAN Bus?
Testing multiple CAN channels simultaneously allows you to efficiently troubleshoot and verify communication across complex systems with multiple networks or devices. With the Komodo CAN Duo Interface’s two independently customizable CAN channels—Channel A and Channel B—users can actively send CAN messages on one channel while monitoring bus traffic in real time on the other. This setup also allows monitoring two independent CAN buses simultaneously, making it easy to test and debug multiple CAN networks or nodes at once. Find out more: Monitor and Transmit CAN Traffic Using the Komodo CAN Duo Interface
With the Data Center Software, a free, user-friendly, bus monitoring GUI compatible with the Komodo CAN Duo Interface, users can easily capture, view, filter, and search CAN bus data in real time. This software leverages unique technology to provide unmatched visibility into the bus, including LiveDisplay, LiveSearch, and LiveFilter:
LiveDisplay shows CAN traffic in true real time with captured data organized into columns such as timestamp, arbitration ID, data length code (DLC), and message data.
LiveSearch allows users to easily find specific CAN messages or events using text strings, hexadecimal values, and ASCII data patterns within a capture.
LiveFilter allows users to isolate specific CAN messages or error types by filtering on fields such as fields such as arbitration ID, data payload, data length, or bus errors like ACK or CRC failures. Users can seamlessly switch between filtered and non-filtered views with a single click.
Yes, with the Komodo CAN Duo Interface and the Data Center Software, users can monitor two CAN channels simultaneously. Each transaction is labeled by channel in the Transaction window, and all connected channels are listed in the Navigator window. To isolate traffic from a specific channel, simply right click on the device and click “Filter and Show Only”. Learn more: Analyze and Capture CAN Traffic Using the Komodo CAN Interface
The Komodo CAN Duo Interface with the Komodo GUI Software allows users to send and receive custom CAN messages in real time enabling users to easily test and simulate ECU communication. With the free API, users can also automate test sequences to validate ECU responses. When paired with Data Center Software, users can monitor, filter, and decode CAN traffic live to analyze and diagnose communication issues. For sensor data testing on automotive networks, our I2C/SPI tools let users simulate and monitor sensor communications alongside CAN bus activity.
Have Questions?
Have a question about any of our CAN tools and how they can help develop and debug your CAN system? Please email us at sales@totalphase.com or request a demo.