Contents

Applications on a smart node / LIN slave

A small smart node performs one local job, such as moving a motor, controlling a lamp or reporting a sensor value, under commands from another controller.

3 min read · Discipline stake: Hardware Software Networks Safety

What runs here

The application is a small, fixed set of behaviors close to the physical device. A lamp node applies a requested brightness; a motor node drives toward a requested position; a sensor node measures a quantity and reports it. Each implements only the behaviors its hardware and requirements support.

There may be no separately packaged application layer. On a small MCU, the behavior can be a state machine within one firmware image. In an ASIC, dedicated logic may implement some or all of it. The application still exists as a responsibility, even when it has no separate software module.

Component Role
Command interpretation Turns a received request into a permitted local action.
Local behavior or control loop Applies brightness, regulates motion or processes measurements.
Operating limits and fault reaction Handles conditions such as overtemperature, stalled motion or invalid inputs, where supported.
Status generation Reports measured values, achieved state and relevant faults.

Protocol handling, configuration storage and peripheral access belong to adjacent layers conceptually, even when implemented in the same source file.

Why it looks like this

Small memory, limited processing capacity and unit cost favor bounded behavior with few dependencies. Dedicated timers, PWM peripherals, converters and protection circuits can perform work that would otherwise consume CPU time. An ASIC can encode behavior directly, trading software flexibility for a hardware implementation suited to a stable function.

Timing follows the physical device. A motor may need local feedback between network commands; a sensor needs a defined sampling and filtering strategy. The communication schedule and the local control rate are separate design decisions. The controller above supplies intent, while the node handles the physical response assigned to it.

This grid describes a QM implementation. QM must follow the vehicle-level safety assessment and allocation; a small MCU or LIN connection does not establish that classification. A safety-related use may require a different implementation, external monitoring or additional mechanisms. The relevant framework is ISO 26262 — Road vehicles — Functional safety.

A stable function may need infrequent software changes, but fixed function does not mean immutable. Calibration, defect correction and replacement compatibility still need consideration. Some devices provide reprogramming; others require replacement to change behavior.

How it connects

Above this node, a zone controller or another ECU usually decides the vehicle behavior and sends a target or enable request. Below the application, drivers or ASIC interfaces expose measurements, output stages and protection status. Configuration and diagnostic services provide parameters and access to faults.

On LIN, the commander, traditionally called the master, controls frame scheduling. A responder, traditionally called a slave, publishes its assigned response when the corresponding header arrives. Application timing must account for signal availability and scheduled transmission opportunities. These relationships are defined in the LIN Specification Package Revision 2.2A.

Define the command contract explicitly: units, range, validity, startup values, maximum age and the reaction to missing updates. Return useful status, including whether a request was achieved. The LIN checksum does not authenticate a command or establish its freshness for the application.

Compared with other node classes

  • HPC application processor: Runs broader feature services, HMI or ADAS applications, with substantially richer deployment and runtime facilities.
  • HPC safety island: Runs allocated real-time control and safety monitoring, with assurance obligations determined by its safety requirements.
  • Zone controller: Coordinates many endpoints and performs gateway and I/O logic; this node executes a narrow local behavior.
  • MCU-based ECU: Can host multiple application software components, including AUTOSAR Classic SWCs; this node may implement its behavior in one compact firmware image or dedicated logic.

Best practices

  • Specify startup, normal operation, command timeout, fault recovery and sleep transitions as explicit states.
  • Budget local sampling, control execution and network latency together against the required physical response.
  • Define output behavior during reset, brownout and communication loss, including what hardware enforces before firmware starts.
  • Validate commands and configuration values before applying them; report saturation or rejection when useful.
  • Test with representative loads and injected faults, including stalled actuators, disconnected sensors and interrupted commands.
  • Record firmware, hardware and calibration compatibility, including how replacement nodes receive their configuration.

Common pitfalls

  • Treating “fixed function” as permission to leave exceptional behavior unspecified.
  • Assuming the last received command remains appropriate indefinitely after communication stops.
  • Equating an electrical protection action with the correct vehicle-level fault response.
  • Assuming a QM node needs no system-level safety analysis or cybersecurity consideration.

What it means for your discipline

  • Hardware & silicon Core

    Select peripherals, output stages and protection circuits that support the local behavior. Verify output states during reset, supply disturbances and hardware faults.

  • HPC & application software Core

    Implement the state machine, local control or measurement processing, command validation and fault reactions. Keep execution time and memory use within the node's limits.

  • Networks & communication Partial

    Define signal encoding, scheduled update opportunities and timeout expectations with the commanding ECU. Check that communication timing supports the required physical response.

  • Functional safety Partial

    Check whether the proposed QM implementation fits the vehicle-level safety allocation. Define any required external monitoring and fault-response assumptions.

No direct stake: E/E architecture · Cybersecurity · Base software · Diagnostics & lifecycle · Software update & OTA

Where it sits in the software stack

Generic layered software of a central HPC (application processor with hypervisor, plus a safety island) and of a classic MCU-based ECU (AUTOSAR Classic). Highlighted modules matter for this topic. Click any module to open its page.

HPC · application processor (MPU) and safety island (MCU)

Not directly involved on this node type.

MCU-based ECU · AUTOSAR Classic
  • Application layer — Equivalent application responsibilities include command validation, local control, status reporting and defined reactions to stale commands or hardware faults.