Free CAN Tools › Bus Load Calculator

CAN Bus Load Calculator for Classic CAN & CAN FD

Calculate how much of your CAN or CAN FD bandwidth a message schedule uses. Enter messages by hand, import a DBC file to use its cycle times, or load a recorded log to measure real traffic — with worst-case bit stuffing, CAN FD bit-rate switching and a per-message breakdown.

  • Classic CAN, CAN FD and CAN FD + BRS frames, 11-bit or 29-bit IDs
  • Worst-case, typical or no bit stuffing
  • DBC import using GenMsgCycleTime
  • Measure from a log – ASC, BLF, TRC, SLSS, candump – with a load-over-time chart
  • Per-message contribution and design-limit headroom
  • CSV export of the full schedule

Example

A Classic CAN frame with an 11-bit ID and 8 data bytes is 111 bits plus up to 24 stuff bits — 135 bits worst case, or 270 µs at 500 kbit/s. Sent every 10 ms, it uses 270 µs / 10 ms = 2.7 % of the bus. The built-in 500 kbit/s body-network example adds up twelve such messages to about 10.7 %. Switch on the CAN FD example to see how a 32-byte frame with BRS at 2 Mbit/s costs only about 245 µs.

How it works

Bus load is the sum over all messages of frame time / period. For Classic CAN the frame length is 47 + 8n bits (11-bit ID) or 67 + 8n bits (29-bit ID) including the inter-frame space, where n is the number of data bytes. Worst-case bit stuffing adds one bit for every four bits of the stuffed region (start of frame to CRC).

For CAN FD the frame is split into an arbitration phase (identifier, control bits, ACK, end of frame, intermission) sent at the nominal rate and a data phase (ESI, DLC, data, stuff count and a 17- or 21-bit CRC) sent at the data rate when BRS is set. Fixed stuff bits in the CRC field are always counted. Without BRS the whole frame uses the nominal rate. Results are estimates: real stuffing depends on the data, and controller gaps between frames are not modelled.

Frequently asked questions

What bus load is acceptable?

There is no single limit. Many automotive and industrial design guidelines keep the planned worst-case load well below 100 % — often in the 30–70 % range — to leave room for event messages, diagnostics, error frames and future growth. Because CAN uses priority-based arbitration, high load mainly delays the lowest-priority IDs.

Why use worst-case bit stuffing?

After five identical bits the transmitter inserts a stuff bit, so the real frame length depends on the data. Worst-case stuffing gives a guaranteed upper bound, which is what schedule design should use. The typical setting approximates random data.

How is CAN FD with BRS calculated?

The arbitration fields and the end of the frame are counted at the nominal bit rate; ESI, DLC, data, stuff count and CRC are counted at the data bit rate. This is why large CAN FD payloads with BRS use far less bus time per byte than Classic CAN.

Can I import my DBC file?

Yes. Messages, IDs, lengths and CAN FD settings are read from the DBC, and periods come from the GenMsgCycleTime attribute. Messages without a cycle time are listed with a 0 ms period (0 %) so you can enter the period yourself.

Why does the measured load differ from the estimate?

A log contains the real data (so the real stuffing), event-driven messages, retransmissions and timing jitter. The log measurement uses the same frame model on every recorded frame in 100 ms windows, so it shows peaks the average hides.

Is my data uploaded?

No. DBC files and logs are processed locally in your browser.

Related free CAN tools

See all free CAN tools.

Built by SeRoSys Technology. Measure real bus load: capture your network with Desk CAN Pro and SLSS CANAnalyser, then load the log here.

Shopping Cart
Scroll to Top