CAN ID (arbitration ID)

CAN identifierarbitration IDmessage ID11-bit identifier29-bit identifierextended ID

A CAN ID is the identifier at the start of every CAN frame that names the message and sets its priority on the bus. Standard frames use 11-bit IDs and extended frames 29-bit IDs. When nodes transmit at once, the frame with the numerically lowest ID wins arbitration and continues without delay.123

How it works

CAN is message-based rather than address-based.

The ID describes the content, such as engine speed or wheel speeds, and every node receives every frame and decides from the ID whether to use it. An 11-bit ID allows 2,048 values (0x000 to 0x7FF); a 29-bit ID allows over 536 million.23

Arbitration is bitwise. A 0 bit is dominant and a 1 bit is recessive, so if two nodes start together, the one sending a 1 while the bus reads 0 stops and retries later. The lower ID therefore wins without corrupting the frame, which makes ID choice a priority decision.231

The ID sits right after the start-of-frame bit, followed by the RTR and IDE bits. RTR is dominant in data frames, so a data frame beats a remote frame with the same ID. IDE is dominant for 11-bit frames, so a standard frame beats an extended frame that shares its first 11 bits.28

Some higher-layer protocols structure the ID. SAE J1939, used on heavy vehicles, packs a priority, a parameter group number and a source address into the 29-bit ID. OBD-II on CAN uses fixed IDs, with functional requests sent on 0x7DF.Medium45

Old CAN 2.0A controllers only understand 11-bit IDs, and some react badly to 29-bit frames on the same bus. Kvaser notes mixed buses work as long as nodes stay passive toward extended frames, so check every node before introducing 29-bit traffic.Medium6

Typical values

Standard ID range11 bits, 0x000-0x7FF2,048 IDsSourced23
Extended ID range29 bits, 0x00000000-0x1FFFFFFFabout 537 million IDsSourced2
OBD-II diagnostic IDs (11-bit)
  • 0x7DF functional request
  • Responses on 0x7E8-0x7EF
Sourced · medium511
Heavy-duty functional diagnostic request (29-bit)0x18DB33F1Sourced · medium11
8-byte frame, 11-bit ID
  • 108 bits before stuffing
  • Up to 132 with stuffing
Sourced2
8-byte frame, 29-bit ID
  • 128 bits before stuffing
  • Up to 157 with stuffing
Sourced2
Maximum 8-byte, 11-bit frames at 500 kbit/s
  • About 4,500 per second unstuffed
  • About 3,700 worst case
Includes the 3-bit interframe spaceSourced · medium2

How an ECU uses it

A CAN controller filters frames in hardware by ID, so the ECU's software only sees messages it has been set up to use.

That is why a receiver set for an 11-bit ID ignores a 29-bit frame with the same number.Medium61

On transmit, the ECU sends each ID at its own repeat rate. A lower ID helps urgent data win arbitration when the bus is busy, but it does not make the bus faster; high load still delays the highest-numbered IDs first.Medium23

Diagnostic IDs sit apart from broadcast IDs. An ECU answers OBD-II requests on fixed IDs such as 0x7E8, while its normal broadcast messages use IDs chosen by its maker.Medium57

How to test it

4 checks, in order.

  1. Log the bus with a USB CAN interface in listen-only mode for a minute at key-on and at idle. List every ID seen with its length and repeat rate; that list is your ID map.8
  2. Before adding a device, compare its planned transmit IDs with the map. Move any overlap, because two transmitters on one ID cause bit errors whenever their frames collide.92
  3. Check the frame format of each ID in the log. A tool may display 0x100 for both an 11-bit and a 29-bit frame; only the IDE flag tells them apart.Medium210
  4. Measure bus load with the CAN tool and check that the highest-numbered IDs still arrive at their expected rates. Late or irregular high IDs are the first sign of an overloaded bus.Medium23

Symptoms and causes

Error frames appear after adding a device.

Likely causes Duplicate CAN ID, or a termination change from the new device.

Check Unplug the device; if errors stop, compare its IDs with the bus map and measure termination.

9

A receiver ignores a message visible on a CAN tool.

Likely causes 11-bit versus 29-bit mismatch, receive filter not set, or the ID entered in decimal instead of hex.

Check Check the IDE flag and convert the ID between hex and decimal.

Medium210

Slow channels update late or irregularly.

Likely causes High bus load; high-numbered IDs keep losing arbitration.

Check Measure bus load and the interval of each high ID.

Medium2

A node goes bus-off.

Likely causes Repeated transmit errors from collisions or wiring faults push its error counter past 255.

Check Log error frames and look for duplicate IDs and termination faults.

92

In tuning

Two devices must never transmit the same ID on one bus.

Before adding a controller or logger, list the IDs already in use and pick unused ones for new broadcasts. Give time-critical data, such as engine speed and throttle, lower IDs than slow data like temperatures.Medium23

Check whether each device sends standard or extended frames. A receiver configured for 11-bit IDs will ignore 29-bit frames with the same numeric value.Medium16

Formula and worked example

Try it

Hz

The clock feeding the prescaler (the CAN kernel or peripheral clock).

Some register fields store prescaler − 1; Microchip MCP2515 divides by 2 × (BRP + 1). Enter the real divide ratio.

Controllers with a single TSEG1 field: enter TSEG1 here and 0 below; tolerance then assumes PhaseSeg1 = TSEG1.

Result

Bitrate (kbit/s)500.00
Sample point87.5 %
Time quanta per bit16
Time quantum (ns)125.0
Bit time (µs)2.000
Max oscillator tolerance0.313 %each node's clock must stay within this

Planning estimate from the formula below, not a measurement.

Open the full can bus bit timing calculator →

Common mistakes

Mistake Confusing hex and decimal, such as entering 256 when 0x256 was meant.

Do instead Write IDs with the 0x prefix and check each tool's number format.Medium10

Mistake Giving slow temperature messages low IDs and engine speed a high ID.

Do instead Assign the lowest IDs to time-critical, high-rate messages.Medium32

Mistake Using the OBD-II diagnostic ID range for custom broadcasts.

Do instead Keep 0x7DF and 0x7E0-0x7EF free for diagnostics.Medium5

Myths vs facts

Myth A CAN ID is the address of a device.

Fact In classical CAN the ID names the message, not the sender or receiver. A device can send many IDs and every node sees every frame. Protocols such as J1939 add addressing on top by encoding a source address in the ID.24

Myth A higher ID number means higher priority.

Fact It is the reverse. Dominant bits are zeros, so the numerically lowest ID wins arbitration.21

Myth Extended 29-bit IDs are faster or better.

Fact A 29-bit frame carries 20 more overhead bits (128 versus 108 for 8 bytes), so the same data takes longer. Use extended IDs where a protocol such as J1939 requires them.24

Frequently asked

What is a CAN ID?

A CAN ID is the identifier at the start of each CAN frame. It names the message, such as engine speed or wheel speeds, rather than a device, and it sets priority: when two nodes transmit together, the lower ID wins. Standard IDs are 11 bits and extended IDs are 29 bits.21

What is the difference between 11-bit and 29-bit CAN IDs?

Standard CAN frames use an 11-bit identifier with 2,048 possible values. Extended frames, added in CAN 2.0B, use 29 bits for over 536 million values. Both can share a bus. Passenger-car powertrain networks commonly use 11-bit IDs, while SAE J1939 heavy-vehicle networks use 29-bit IDs.Medium234

Does a lower CAN ID have higher priority?

Yes. During arbitration a 0 bit overrides a 1 bit on the wire, and each transmitter checks the bus as it sends. A node that sends a 1 but sees a 0 stops transmitting. The frame with the lowest numeric ID therefore always wins and is sent without delay.21

What happens if two devices use the same CAN ID?

If both send the same ID at the same time with different data, arbitration cannot separate them, and the data bits collide, producing bit errors and retransmissions. Even without collisions, receivers cannot tell the two sources apart. Each ID should have exactly one transmitter on a bus.Medium23

Which CAN ID does an OBD-II scanner use?

On CAN-based OBD-II, a scan tool sends functional requests to ID 0x7DF so every emissions-related module can answer. Responses typically come back on IDs 0x7E8 to 0x7EF, one per responding module. These IDs are defined for diagnostics and are separate from the vehicle's normal broadcast messages.Medium57

Used in these guides

Sources

Numbered as cited above. Hover or tap a citation chip to preview it.

11 sources
  1. ISO 11898-1:2024 Road vehicles, Controller area network (CAN), Part 1: Data link layer and physical coding sublayer · International Organization for Standardization · standard · retrieved 2026-10-27
  2. CAN bus · Wikipedia · reference · retrieved 2026-10-27
  3. Introduction to the Controller Area Network (CAN), SLOA101B · Texas Instruments · vendor-doc · retrieved 2026-10-27
  4. SAE J1939: Serial Control and Communications Heavy Duty Vehicle Network, top level document · SAE International · standard · retrieved 2026-10-27
  5. OBD-II PIDs · Wikipedia · reference · retrieved 2026-10-27
  6. Controller Area Network (CAN BUS) Protocol tutorial · Kvaser · vendor-doc · retrieved 2026-10-27
  7. SAE J1979: E/E Diagnostic Test Modes · SAE International · standard · retrieved 2026-10-27
  8. CAN Bus Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  9. CAN Bus Errors Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  10. CAN DBC File Explained: A Simple Intro · CSS Electronics · vendor-doc · retrieved 2026-10-27
  11. UDS Explained: A Simple Intro (Unified Diagnostic Services) · CSS Electronics · vendor-doc · retrieved 2026-10-27