What is an embedded controller?
An embedded controller is a specialised control unit, usually built around a microcontroller or System-on-Chip, that is built into a device, machine or vehicle to perform one fixed control task there in real time and reliably. The controller reads sensors, computes with fixed firmware or an RTOS and drives actuators, often thousands of times per second. Embedded controllers are therefore the invisible core of PLCs, variable frequency drives, AGVs, robots, HVAC installations and safety components in the OT world. The broader term embedded systems covers all built-in computers; this article focuses on the controllers that actually control a physical process.
🧠 What exactly does an embedded controller do?
An embedded controller runs a fixed control cycle that repeats endlessly:
- Read - measured values from sensors, encoders and switches via analogue and digital inputs or a fieldbus
- Compute - control algorithms such as PID control, interlocks and state machines
- Write - drive motors, valves, heating elements or relays
- Supervise - diagnostics, fault detection and communication with higher-level systems
The difference from an ordinary computer is not speed but predictability. An embedded controller is optimised for deterministic behaviour, low latency, low jitter, continuous availability and a long service life. A watchdog timer supervises the software: if the program fails to restart the timer in time, the hardware resets the controller or drives the outputs to a safe state.
Within industrial automation, embedded controllers are thus the direct link between software, electronics and the physical process, and they sit at the heart of cyber-physical systems.
Note the second meaning: in laptops and PCs the embedded controller (EC) is a separate microcontroller on the motherboard that manages the battery, fans, keyboard and power button. The operating system talks to this EC through the ACPI specification, traditionally via I/O ports 0x62 and 0x66. In OT, “embedded controller” almost always means the process control unit.
🔄 How does an embedded controller differ from a PLC and an industrial PC?
| Characteristic | Embedded controller (MCU/SoC) | PLC | Industrial PC (IPC) |
|---|---|---|---|
| Hardware | Custom board design inside the device | Standardised, modular controller | PC architecture in a rugged enclosure |
| Programming | C/C++ or model-based, by the manufacturer | IEC 61131-3 languages, by the user | IEC 61131-3 via a soft PLC, C#, Python |
| Operating system | Bare metal or RTOS | Vendor’s own RTOS | Windows or Linux, sometimes with a real-time extension |
| Typical cycle time | Microseconds to milliseconds | 1 to 100 ms | 1 ms to seconds, depending on the software |
| Changeable by the end user | Barely, parameters only | Yes, fully | Yes, fully |
| Service life in the field | 10 to 25 years | 15 to 25 years | 5 to 10 years |
A PLC is itself an embedded controller, but a generic one that the user programs. Most embedded controllers are “hidden”: they sit inside a drive, a smart sensor or an AGV, and the user only sees parameters.
🧱 What are the components of an embedded controller?
The architecture combines hardware and software on a single board or module:
| Component | Function | Examples |
|---|---|---|
| Processor | Computing and control | Microcontroller (Arm Cortex-M), real-time processor (Cortex-R), SoC (Cortex-A), DSP or FPGA |
| Memory | Firmware, parameters and working data | Flash, RAM, EEPROM for calibration |
| I/O | Coupling with the process | ADC/DAC, digital I/O, PWM, encoder inputs |
| Communication | Network and fieldbus | Ethernet, CAN, RS-485, SPI and I²C on the board |
| Supervision | Reliability | Watchdog, voltage monitoring (brown-out), ECC memory |
| Security | Integrity and keys | Secure element, TPM, hardware root of trust |
| Software | Control | Bootloader, firmware, RTOS, drivers, communication stack, diagnostics |
For safety applications, manufacturers often use processors with dual-core lockstep: two cores execute the same instructions and hardware compares the results, so a computing error is detected immediately. This helps meet the requirements of IEC 61508 up to high SIL levels.
Embedded controllers run on three types of platform: bare metal for simple, very fast tasks, an RTOS such as FreeRTOS, Zephyr, VxWorks or QNX for multiple tasks with hard deadlines, and embedded Linux for HMI functions, network services and edge analytics. Since kernel version 6.12, real-time support (PREEMPT_RT) has been part of the mainline Linux kernel. On powerful SoCs, a hypervisor sometimes combines an RTOS and Linux on a single chip.
⏱️ Why does real-time behaviour matter so much?
Real-time does not mean “fast” but “within a guaranteed time”. A control loop that sometimes needs 1 ms and sometimes 20 ms becomes unstable, even when the average is low. Typical values:
| Application | Typical cycle time |
|---|---|
| Current control in a variable frequency drive | Tens to hundreds of microseconds |
| Motion control over EtherCAT or ProfiNET IRT | 0.25 to 1 ms |
| Machine control in a PLC | 1 to 20 ms |
| Process control (temperature, pressure, level) | 100 ms to 1 s |
| Building management and HVAC | Seconds |
The cycle time of the communication also counts. A fast controller on a slow fieldbus does not produce fast control.
🔌 How does an embedded controller communicate with the rest of the installation?
| Protocol | Role for embedded controllers |
|---|---|
| Modbus TCP | Simple register exchange, without security |
| ProfiNET | Real-time Ethernet in Siemens-oriented installations |
| Ethernet IP | Real-time Ethernet in Rockwell-oriented installations |
| EtherCAT | Very fast motion and I/O networks |
| CAN | Vehicles, AGVs, medical equipment and machines |
| RS-485 | Serial communication with older equipment |
| MQTT | Publishing telemetry to edge and cloud |
| OPC UA | Standardised, secure data exchange with an information model |
Via Industrial Ethernet, embedded controllers supply data to SCADA, MES, HMIs and a historian. Increasingly they act as an edge device and run analyses themselves, for example condition monitoring, predictive maintenance or machine vision. This fits edge computing and industrial AI: local processing gives lower latency, less network load and keeps working when the cloud connection drops.
🏭 Where are embedded controllers used in OT?
| Application | Task of the embedded controller |
|---|---|
| PLC and safety PLC | Machine control and safety logic |
| Variable frequency drives | Current, speed and position control of motors |
| Smart sensors | Measurement, linearisation, diagnostics and communication |
| Actuators and valves | Positioning and feedback |
| RTUs and outstations under SCADA | Local control and remote data logging |
| Robots | Synchronised motion control of multiple axes |
| AGVs | Navigation, motor control, LiDAR and vision processing, collision prevention, battery management and communication with the fleet management system |
An AGV usually contains several cooperating embedded controllers: a navigation computer, motor controllers per wheel, a battery management system and a certified safety controller for the laser scanners, often connected via CAN.
🔐 What cybersecurity risks do embedded controllers have?
Embedded controllers are an attractive target in OT cybersecurity, because whoever controls the controller controls the physical process. Two well-known examples: Stuxnet (discovered in 2010) reprogrammed Siemens PLCs that drove centrifuges, and TRITON (2017) attempted to manipulate the firmware environment of Triconex safety controllers in a petrochemical plant.
| Risk | Possible consequence |
|---|---|
| Firmware tampering | Hidden deviating behaviour, loss of integrity |
| Insecure protocols | Unauthenticated commands over the network |
| Default credentials and open services | Unauthorised access |
| Malware via the engineering workstation | Tampered control programs loaded through trusted engineering software, as with Stuxnet |
| Vulnerable shared components | One flaw in a TCP/IP stack affects many vendors at once |
| Supply chain attacks | Compromised hardware or firmware before delivery |
| Debug interfaces (JTAG, UART) | Reading or overwriting firmware with physical access |
Patching is hard because of high availability requirements, retesting and sometimes new safety validation, legacy hardware, vendor dependencies and production continuity. Many controllers therefore run an old firmware version for years.
🛡️ How do you secure embedded controllers?
Security requires several layers, partly in the device itself and partly in the surrounding network:
| Measure | Purpose | Where |
|---|---|---|
| Secure boot | Only boot trusted firmware | Device |
| Firmware signing | Integrity and origin of updates | Vendor and device |
| Disabling debug ports and unused services | Reduce the attack surface | Device |
| Application whitelisting | Only permitted software, mainly on IPC and Linux controllers | Device |
| Network segmentation | Isolate OT zones | Network |
| Zero trust principles | Explicitly allow and verify every connection | Network |
| Patch management | Planned remediation of vulnerabilities | Organisation |
| IDS and logging | Anomaly detection and forensics | Network |
A microcontroller cannot run antivirus or an endpoint agent, so detection almost always happens passively on the network. The component standard IEC 62443-4-2 contains separate requirements for embedded devices (EDRs). EDR 3.14, for example, requires the device to check the integrity of firmware and configuration before use, and from security level 2 also to verify authenticity against the vendor’s root of trust. The manufacturer’s development process falls under IEC 62443-4-1, and the whole under IEC 62443.
📜 Which standards and laws apply to embedded controllers?
| Framework | Meaning for embedded controllers |
|---|---|
| IEC 61131-2 | Hardware requirements and tests for programmable controllers (EMC, temperature, vibration) |
| IEC 61131-3 | PLC programming languages; Instruction List has been deprecated since edition 3 (2013) |
| IEC 61508 | Functional safety of electronics and software, up to SIL 4 |
| MISRA C | Coding rules for safe C code; the current edition, MISRA C:2025, appeared in March 2025 |
| IEC 62443-4-1 and IEC 62443-4-2 | Secure development process and technical security requirements per component |
| Cyber Resilience Act | Reporting of actively exploited vulnerabilities since 11 September 2026, full requirements from 11 December 2027 |
| Machinery Regulation | From 20 January 2027, protection of control systems against corruption, including via software |
For Dutch and European machine builders and OEMs this means an embedded controller is not “finished” at delivery: vulnerabilities must be found, reported and fixed throughout the support period, and an SBOM becomes a normal delivery document.
🧭 How do you select and manage embedded controllers in practice?
- Define the timing requirements - which cycle time and maximum jitter does the process need? That decides between bare metal, an RTOS or Linux.
- Choose the right temperature grade - commercial chips are specified for 0 to 70 °C, industrial ones for -40 to +85 °C and automotive (AEC-Q100 Grade 1) up to +125 °C.
- Check long-term availability - choose components from a chip vendor’s longevity programme, typically 10 to 15 years of supply, to avoid premature legacy systems.
- Require security at procurement - secure boot, signed firmware, debug ports that can be disabled, an SBOM and a support period, preferably with IEC 62443-4-2 certification.
- Record everything - register type, firmware version and network services per controller in the asset inventory.
- Segment and monitor - place controllers in zones according to the Purdue Model and watch the traffic with network monitoring.
- Plan the lifecycle - include firmware updates, spare parts and replacement in lifecycle management, because controllers often run for 15 years or longer.
For organisations covered by NIS2, which the Netherlands implemented through the Cyberbeveiligingswet in force since 15 August 2026, these steps are part of the duty of care for their own OT environment.
❓ Frequently asked questions
Is a PLC an embedded controller?
Yes, a PLC is an embedded controller: the CPU module contains a processor, memory and a real-time operating system that cyclically executes the control program. The difference from a “hidden” embedded controller in a drive or sensor is that the user programs a PLC in IEC 61131-3 languages.
What is an embedded controller in a laptop?
In a laptop, the embedded controller (EC) is a small microcontroller on the motherboard that manages the battery, fans, keyboard and powering on and off. The operating system communicates with it through the ACPI specification. This meaning is separate from embedded controllers in process control.
Which language are embedded controllers programmed in?
Embedded controllers are usually programmed in C or C++, often following the MISRA C coding rules, or with model-based tools that generate code automatically. PLC-like embedded controllers use the IEC 61131-3 languages, for example through a runtime such as CODESYS.
Why does an embedded controller have a watchdog?
An embedded controller has a watchdog timer to detect hung software. If the program does not restart the watchdog within the configured time, the hardware resets the controller or puts the outputs in a safe state. That way a software fault does not lead to an uncontrolled process.
Can you update the firmware of an embedded controller?
The firmware of an embedded controller can usually be updated, but in OT this rarely happens because an update requires downtime, retesting and sometimes new safety validation. Modern controllers only accept signed firmware via secure boot. The Cyber Resilience Act obliges manufacturers to deliver security updates throughout the support period.
What is the difference between a microcontroller and an embedded controller?
A microcontroller is a chip with a processor, memory and I/O on a single piece of silicon. An embedded controller is the complete control unit: the microcontroller plus power supply, I/O circuitry, communication, enclosure and firmware that together perform a control task.
📌 In summary
An embedded controller is a built-in, task-specific control unit that reads sensors, computes in real time and drives actuators, making it the direct link between software and the physical process. Predictable timing, a watchdog and a long service life make embedded controllers reliable; that same long service life, vulnerable firmware and limited update options make security according to IEC 62443, the Cyber Resilience Act and sound lifecycle management essential.