Skip to content
AirModuleLink

ISO 11898 and ISO 15765-4

CAN and CAN FD at the OBD-II port

CAN FD (CAN with Flexible Data-rate, ISO 11898-1:2015) is the faster successor to classic CAN: up to 64 bytes in a frame instead of 8, with the data sent at a higher bit rate than the rest of the frame.

Classic CAN in one paragraph

CAN is a two-wire bus that every control unit in the car shares. Any unit may speak when the bus is quiet, each message carries an identifier and up to eight bytes of data, and when two units start together the message with the lower identifier wins without either being damaged. Since model year 2008 it has been the required diagnostic bus on cars and light trucks sold in the United States, on pins 6 and 14 of the OBD-II connector at 250 or 500 kbit/s.

What CAN FD changes

CAN FD keeps the wires, the identifiers and the arbitration, and changes what happens once a message has won the bus. The data part can be sent at a higher bit rate, and it can be up to 64 bytes long. A diagnostic message that needed nine classic frames can cross in one or two.

The catch is that the two are not mutually polite. A CAN FD controller understands classic frames. A classic CAN controller does not understand FD frames: it reads one as a broken message and answers with an error frame, which destroys it for everyone.

What a remote link has to get right

A link that carries a CAN bus to somewhere else has two jobs. The first is to carry every frame exactly: same identifier, same length, same FD and bit-rate-switch flags. A link that quietly turns an FD frame into a classic one has changed what was said.

The second is time. A diagnostic tool waits a fixed time for its answer, and a busy bus carries thousands of frames a second that the tool does not care about. If the tool's question waits in a queue behind that chatter, the tool gives up. AirModuleLink measures the link before a programming sequence may start, and gives diagnostic traffic its own priority lane ahead of the background.

Two CAN buses on one connector

Pins 6 and 14 are the bus the standard requires. Makers are free to put a second one on pins the standard leaves to them, and some do: Ford's medium-speed CAN on pins 3 and 11 is the best known. Body and comfort modules often live there, which matters for key and module work.

AirModuleLink has two CAN FD channels so that both pairs can be carried in the same job. Because pins 3 and 11 are an Ethernet pair on a DoIP car, the box listens there first and joins only if it hears a CAN bus.

What AirModuleLink does with it

The box carries classic CAN and CAN FD on pins 6 and 14, and the second pair on pins 3 and 11 in the same job. A diagnostic tool on one bench has read live fault codes from an engine control module on another, through the link, and diagnostic traffic has its own priority lane ahead of the bus's background chatter.

The proof behind it

Questions

Is CAN FD backwards compatible with classic CAN?

One way only. A CAN FD controller can send and receive classic CAN frames. A classic CAN controller cannot accept CAN FD frames and will flag them as errors, so an interface that is not FD-capable must never be put on an FD bus.

Which cars use CAN FD?

It began reaching production cars around model years 2019 and 2020 and is spreading with each new platform. GM's newer electrical architecture, introduced for model year 2020, is a well-known example. Check the service information for the model in front of you.

Does AirModuleLink carry CAN FD?

Yes. Both ends of the link use CAN FD interfaces, so FD frames with bit-rate switching are carried as FD frames.

What about pins 3 and 11?

The box has a second CAN FD channel for them, carried in the same job as pins 6 and 14. It listens first and joins the pair only when it hears a CAN bus there.

Sources

Keep reading

Launching mid-December 2026

Put your bench in a car that is somewhere else.

Reserve a box from the first batch today for $99, refundable until it ships. Or join the list and get the introductory price before it is public.