Overview
ISO/TR 17987-5:2016 specifies the Local Interconnect Network (LIN) application programmer’s interface (API) for road vehicles. Published as a Technical Report, it defines an informative (non‑normative) API layer that hides LIN network configuration details from application software on Electronic Control Units (ECUs). The report complements the ISO 17987 series by describing the LIN core API, node configuration & identification services, and an optional transport‑layer API.
Key topics and technical requirements
- API scope and structure
- Defines three API areas: LIN core API, LIN node configuration & identification API, and LIN transport layer API (optional).
- All API symbols and functions use an “l_” prefix to provide a dedicated namespace.
- LIN cluster generation
- Workflow: the LIN Description File (LDF) is parsed by tools to generate driver configuration. The Node Capability Format (NCF) is typically not required for API generation.
- Concepts of operation
- Signal-based interaction between applications and LIN core; applications work with signals rather than frames.
- Static vs. dynamic calls: calls can embed signal/interface names or accept them as parameters.
- Node configuration and identification is service‑based (request/response) handled automatically by the slave driver.
- Transport layer options
- Two alternative transport APIs: a raw frame control API and a message‑based API that performs full transport functions (used for larger payloads such as diagnostics).
- API conventions and data types
- Conventions for data types, driver & cluster management, signal interaction, notifications, schedule management, and interface management are described to standardize application behavior.
Practical applications
- Designed for low‑speed automotive control applications (e.g., door modules, HVAC/climate control, simple body electronics).
- Supports LIN characteristics such as signal‑based communication, schedule table‑based frame transfer, master/slave communication, and bit rates from 1 kb/s to 20 kb/s.
- Enables tool vendors to generate LIN driver code from LDF and simplifies ECU application development by abstracting frame handling.
- Facilitates diagnostic transport over LIN via the optional transport API.
Who should use this standard
- ECU and embedded software developers building LIN client or slave applications
- LIN stack and device-driver implementers
- Tool vendors creating LDF‑to‑code generators
- System architects and test engineers working on body electronics and low‑speed in‑vehicle networks
- Architects comparing LIN APIs (e.g., AUTOSAR vs. ISO TR approach)
Related standards
- ISO 17987 series: Parts 1–4, 6–7 (overview, transport protocol, logical protocol, physical layer, and conformance tests)
- ISO 17987-2 and ISO 17987-3 are especially relevant for transport-layer and logical-level requirements referenced by this Technical Report
Keywords: ISO/TR 17987-5:2016, LIN API, Local Interconnect Network, LIN protocol, LDF, ECU, transport layer, node configuration, automotive networking.
Open preview (PDF)Road vehicles — Local Interconnect Network (LIN) — Part 5: Application programmers interface (API)