CAN bus baud rate, and how to calculate bus load
What baud rate really means, how long a bit and a frame take, and how to work out how busy your bus is. With two calculators you can try.
Baud rate is how fast bits move on the CAN bus, measured in bits per second. A 500 kbit/s bus carries up to 500,000 bits every second, and that figure covers everything in a message, not just the data. From the baud rate you can work out how long one bit takes, how long a full message takes, and how much of the bus you are actually using. Those last two, frame timing and bus load, are what this guide helps you calculate.
| Quantity | What it tells you | How to get it |
|---|---|---|
| Bit time | How long a single bit lasts on the wire | 1 ÷ baud rate |
| Frame time | How long one full message takes to send | bit time × bits in the frame |
| Bus load | How much of the bus capacity is in use | (bits per second ÷ baud rate) × 100 |
Baud rate vs bit rate
In most CAN tools the two words are used to mean the same thing, and for everyday work that is fine. Strictly, baud rate counts the signal changes on the wire each second, a property of the physical layer, while bit rate counts the bits of information transmitted each second. On a classical CAN bus one signal change carries one bit, so the two numbers are equal, which is why the terms get used interchangeably.
The reason to keep them apart is timing. Each bit is itself divided into small timing segments that decide exactly when the bus is sampled and how nodes stay in step. Those segments matter when you are tuning a controller or chasing a communication fault, but they do not change the overall bit rate. For everything in this guide, treat the configured bus speed, for example 500 kbit/s, as your bit rate.
Common baud rates, and the distance trade-off
Most networks settle on one of four standard speeds. Faster is not always better, because the faster the bus runs, the shorter it has to be. Arbitration needs the signal to travel to the far end of the wiring and back within a single bit, so a higher speed leaves less time for that round trip and limits the cable length.
125 kbit/s
Long cable runs and many industrial systems.
250 kbit/s
Off-road, agricultural and most J1939 networks.
500 kbit/s
The standard in most modern automotive networks.
1 Mbit/s
High-speed or time-sensitive systems, short buses.
Most CAN software lets you pick the bus speed to match the network. In REXDESK, for example, the baud rate is a simple dropdown, so matching a logger to an existing bus is a single setting.
How long is one bit, and one message?
Every calculation starts from the bit time, the duration of a single bit on the wire. It is simply one divided by the baud rate. At 500 kbit/s a bit lasts 2 microseconds, at 250 kbit/s it lasts 4, and at 1 Mbit/s it lasts 1.
Multiply the bit time by the number of bits in a frame and you get the frame time, how long one whole message takes. A standard CAN message with eight data bytes is roughly 110 to 130 bits once you include the identifier, control bits, checksum and the gap before the next frame, so its exact length depends a little on the data. Smaller messages are shorter and faster. The calculator below works it out for you.
Bus load, and how to find it
Bus load is the share of the bus capacity your traffic is using, written as a percentage. The idea is simple: add up all the bits placed on the bus each second, then divide by the bit rate. A message sent more often, or carrying more bytes, puts more bits on the bus and pushes the load up.
To count the bits per second for one group of messages, multiply how often they are sent by how many frames go out each time and by the bits in each frame. Do that for every group, add the results, and divide by the baud rate. The calculator below does the arithmetic, so you can change an interval or a payload and watch the load move.
Keeping a healthy bus
A CAN bus does not fail the instant it gets busy, but high load leaves less room for important messages and makes timing less predictable. In practice, well-behaved networks run comfortably up to around 70 to 80% load, especially when the highest-priority messages are the ones that must never wait.
If your figure is creeping up, the levers are the obvious ones: send slow-changing signals less often, pack more data into fewer messages, or move to a faster bus speed if the cable length allows it. A logger that reports live bus load, as the REBEL range does, makes it easy to see the effect of each change rather than guessing.
Bus load is bits per second divided by the bit rate. Keep it under about 80% and the bus stays predictable.
Baud rate FAQ
What is the most common CAN baud rate?
500 kbit/s is the usual choice in modern automotive networks. Heavy-duty and off-road vehicles using J1939 commonly run at 250 kbit/s, with newer variants at 500 kbit/s. Industrial systems and long cable runs often use 125 kbit/s.
How do I calculate CAN bit time?
Divide one by the baud rate. At 500 kbit/s the bit time is 1 divided by 500,000, which is 2 microseconds. At 250 kbit/s it is 4 microseconds, and at 1 Mbit/s it is 1 microsecond.
How is CAN bus load calculated?
Add up the total bits placed on the bus each second across all your messages, then divide by the bit rate and multiply by 100. For one message group, the bits per second equal how often it is sent, times the frames per send, times the bits in each frame.
What is a safe CAN bus load?
Most networks run reliably up to around 70 to 80%. Beyond that, lower-priority messages can be delayed and timing becomes harder to guarantee, so it is worth keeping headroom for peak traffic.
Why does a higher baud rate mean a shorter bus?
Arbitration requires the signal to reach the most distant node and return within a single bit. A faster bus has a shorter bit, leaving less time for that round trip, so the maximum cable length falls. As a rule of thumb, 1 Mbit/s allows about 40 metres and 125 kbit/s about 500 metres.
Does baud rate include the data only?
No. The baud rate covers every bit on the bus, including the identifier, control bits, checksum and acknowledgement, not just your data bytes. That is why a frame is far longer in bits than the payload alone.
Written by the engineering team at Influx Technology. Frame-length and bus-load figures are nominal estimates. Always confirm against your own configuration and a live bus measurement.
See live bus load on your network
The data loggers from Influx Technology, including the REXGEN and REBEL ranges, report bit rate, message activity and live bus load while they record, so you can confirm your calculations against the real bus. REXDESK handles the configuration and the baud rate setting.
