Tuning Wiki

A LIN responder is reached from the diagnostic socket through the commander that already sits on CAN, K-line or Ethernet. The scan tool does not get its own pair of LIN pins. The commander either answers for the responder from the signals it already polls, or it copies a diagnostic request onto the LIN cluster and copies the reply back. The frame that carries the copy, and the three levels of responder that understand it, are this page. The wire, the header and the schedule are on the LIN page. The services, once the bytes are on CAN, are on the diagnostic communication protocols page.

Two reserved identifiers

Frame identifiers 60 and 61 decimal, 3C and 3D hexadecimal, are the diagnostic pair. 3C is the master request frame, sent when the commander has a request to pass on. 3D is the slave response frame. The commander transmits the 3D header even when nobody is waiting to answer, and the slot stays empty if the responder has nothing to send. Both frames are always eight data bytes. A short message is padded out. Both always use the classic checksum, the one over the data bytes only, including on a cluster whose signal frames use the enhanced checksum.

The first data byte of a master request is the node address, the NAD. Only responders have one. The same number is the source address in the response. A NAD of zero in a master request is the go-to-sleep command, which is network management rather than a diagnostic service. The wildcard NAD is 7F hexadecimal, used when a configuration request is allowed to match every responder. One physical module can carry more than one logical responder, and each logical responder has its own NAD.

The transport inside those eight bytes

Node configuration uses only single frames. Diagnostics on a class II or class III responder use the LIN transport, which can reassemble a message of up to 4,095 bytes from a run of these eight-byte frames. The layout follows the same idea as ISO-TP: a node address, a control nibble that says single frame, first frame or consecutive frame, and then the payload. The commander is the node that has to speak both this transport and the transport of the backbone. On CAN that backbone transport is ISO 15765-2. The commander can pass the network-layer message through without interpreting the service, provided both sides are using a transport it implements.

A diagnostic schedule is a schedule table of its own. The commander switches to the request table when a tester frame is waiting, and to the response table to collect the reply, then returns to the signal table. A slot with no pending tester frame is silent. The signal schedule keeps its own slots for the flap motors and the switches.

Three diagnostic classes

Every responder is built to one class. The class is what a tester can expect, and it is what the commander must implement on that cluster.

Class IClass IIClass III
What it isA sensor or an actuator. The commander reads it and stores its faults.The same, plus the identification a manufacturer tester asks for.A small controller, with its own fault memory. It may be reprogrammable.
TransportSingle frame onlyFull multi-frame transportFull multi-frame transport
Faults and measurementsIn the signal framesIn the signal framesIts own services. The commander routes them.
UDS on the responderNoneRead data by identifier, 22 hexadecimal, for the hardware, software, part and diagnostic versions. Write by identifier, 2E hexadecimal, where a parameter is writable.Those, plus session control 10, input/output control 2F, fault read and clear 19 and 14, and routine control 31 where the function exists.

Class I and class II responders run their normal job with the signal frames alone. A class II responder may be used as a class I responder on a commander that has no multi-frame transport. A class III responder is its own diagnostic server. The commander routes the request. The measurements that class III node keeps to itself were never placed in the signal frames, so the commander cannot answer for them.

Flash programming over LIN is possible only on a class III node, and only if that node implements the bootloader services. The LIN documents name the possibility and leave the programming sequence to the manufacturer. A commander that can assign frame identifiers cannot, from that ability alone, write a responder's application.

Configuration and the product identity

Off-the-shelf responders ship with a product identity and an initial NAD, and the commander gives them the frame identifiers this cluster uses. The product identity is a supplier number, a function number and a variant. The supplier number is 16 bits with the top bit clear, issued to the maker of the finished node. The function number is 16 bits, changed when the behaviour changes, and kept when two parts do the same job. The variant is one byte, changed when the part changes and the function does not. An optional four-byte serial number identifies one physical unit. Wildcards let a request leave a field open: NAD 7F hexadecimal, supplier 7FFF hexadecimal, function FFFF hexadecimal.

The configuration services, and the positive response which is the service plus 40 hexadecimal, are:

ServiceRequestWho must implement it
Assign NADB0 hexadecimalOptional on every class
Read by identifier, product idB2 hexadecimal, identifier 00Every class
Read by identifier, otherB2 hexadecimalOptional on class I and II, required on class III
Conditional change NADB3 hexadecimalOptional on every class
Assign frame identifier rangeB7 hexadecimalEvery class

A responder that stores that configuration in volatile memory comes up unconfigured after a reset and will not answer signal frames until the commander assigns them again. A preconfigured responder has a valid set after reset and loses any later change at the next reset. A fully configured responder keeps the assigned NAD and frame identifiers in non-volatile memory. Until a responder has a configuration, every signal frame is invalid. The diagnostic pair stays available, which is how the commander configures it.

The cluster file the vehicle builder and the suppliers share is the LIN description file. A supplier of a standard responder can publish a node capability file, and a design tool turns a set of those files into the description file. The capability file is also where the supported configuration and diagnostic services are listed. Two responders with the same function and different frame identifiers are settled in that file before the car is built.

Sources

  • LIN Specification Package, revision 2.2A, 31 December 2010. Diagnostic classes I to III, the master request and slave response frames, the NAD, and the configuration services B0, B2, B3 and B7 hexadecimal. The package was later published as ISO 17987.
  • ISO 17987-3:2025. Protocol specification, including the schedule and the node-configuration services carried on the diagnostic frames. Accessed 2026-11-12.
  • LIN technology. LIN Consortium. Frame identifiers, checksum and the commander and responder roles. Accessed 2026-11-12.