What makes an application “real-time”?
An application is real-time when some of its results are only correct if they arrive on time. That’s different from simply being fast or being embedded. A calculator is an embedded system, but nothing goes wrong if it takes a little longer to show a result. A motor controller that updates its outputs late can overheat the motor or lose control of it.
For each example below, we name the timing-critical function and the kind of deadline it usually has. The hard/firm/soft labels are typical rather than universal, since the same product can be designed with different requirements. For what the labels mean, see hard vs soft real-time systems.
(If you searched for “real-time features” in web or mobile apps, such as live chat or push notifications, that’s a different use of the term. Those are about low-latency updates to users, not guaranteed deadlines in control systems.)
Real-time applications by industry
Automotive
Modern vehicles contain many electronic control units (ECUs), and several of them are hard real-time systems.
- Engine control: fuel injection and ignition timing must be synchronized to crankshaft position. As engine speed rises, the time available per revolution shrinks, so the software has to keep up across the whole RPM range.
- Anti-lock braking (ABS) and stability control: wheel-speed sensors are read continuously, and brake pressure is modulated quickly enough to prevent wheels locking.
- Airbag control: the module has to recognize a crash and fire the inflators within a short window after impact for the airbag to be effective.
- Electric power steering and EV motor inverters: these run fast current-control loops that directly affect what the driver feels and what the motor does.
- In-vehicle networks: CAN, CAN FD, and automotive Ethernet carry messages with timing requirements between ECUs.
- Infotainment: mostly soft real-time. Audio and navigation should be responsive, but a delay isn’t a safety issue.
Automotive software is commonly developed under ISO 26262, and many ECUs use AUTOSAR-based software platforms.
Aerospace and defense
- Flight control computers read sensors and command control surfaces in a fixed cycle. Fly-by-wire systems are classic hard real-time examples.
- Engine controllers (FADEC) manage fuel flow and other engine parameters continuously.
- Navigation and guidance fuse data from inertial sensors and GPS at fixed rates.
- Radar and signal processing must process returns within each pulse or frame interval.
- Satellites and spacecraft run attitude control, power management, and communication scheduling, often far from any chance of a physical repair.
Airborne software is typically developed under DO-178C. Many avionics platforms use partitioned operating systems, often following the ARINC 653 standard, so that functions of different criticality can share hardware without interfering with each other’s timing.
Medical devices
- Infusion pumps must deliver precise doses at controlled rates and raise alarms promptly when something goes wrong, such as an occlusion or air in the line.
- Ventilators control pressure and flow within each breath cycle, synchronized to the patient’s breathing.
- Pacemakers and implantable defibrillators sense the heart’s activity and respond within the timing of the cardiac cycle.
- Patient monitors sample ECG, blood oxygen, and other signals continuously, and must raise alarms without undue delay.
- Imaging equipment such as ultrasound requires tightly synchronized transmit and receive timing.
Medical device software is commonly developed under IEC 62304, alongside risk-management standards.
Industrial automation and robotics
- Programmable logic controllers (PLCs) run a scan cycle: read inputs, execute logic, write outputs, repeat. Cycle times are commonly in the millisecond range, and the whole cycle must complete every time.
- Motion control and CNC machines coordinate several axes along a path. Position, velocity, and current loops run at fixed rates, with the inner loops being fastest.
- Industrial robots combine motion control with safety functions such as stopping when a person enters a protected zone.
- Industrial networks such as EtherCAT, PROFINET, and EtherNet/IP carry I/O data in fixed cycles. Some can run cycles well under a millisecond, and Time-Sensitive Networking (TSN) extends standard Ethernet with timing guarantees.
- Machine vision inspection must finish analyzing each part before it reaches the reject gate, a typical firm deadline.
Power electronics and energy
- Motor drives and inverters run current-control loops that are often synchronized to the PWM switching frequency, which can be tens of kilohertz. That leaves only tens of microseconds per control cycle.
- Solar inverters and battery chargers track power points and regulate output voltage and current continuously.
- Grid protection relays must detect faults and trip breakers quickly to protect equipment.
- Battery management systems monitor cell voltages and temperatures and must act within a bounded time if a cell goes out of its safe range.
Telecommunications and networking
- Cellular base stations and modems process radio frames on strict schedules. In 5G NR, depending on the configuration, transmission slots can be a millisecond or shorter, and baseband processing must keep pace.
- Network switches and routers forward packets at line rate. Much of this is done in hardware, but control-plane timing still matters.
- Wireless protocols such as Bluetooth Low Energy rely on precisely timed connection events. Radio firmware stacks are some of the most timing-sensitive code in consumer devices.
Audio, video, and consumer electronics
- Audio interfaces, digital mixers, and effects units process sample buffers at fixed rates, such as 48,000 samples per second. A 64-sample buffer at 48 kHz gives about 1.3 ms to process each block. Miss it and you hear a click.
- Video encoders and decoders must produce each frame within the frame interval, about 33 ms at 30 frames per second.
- Game controllers, keyboards, and mice are expected to report input with low and consistent latency.
- Printers coordinate print heads with paper movement, where timing affects print quality.
- Digital cameras use precise timing for exposure control, autofocus, and image stabilization.
Most consumer timing requirements are soft or firm, but users notice problems immediately.
Drones and hobby robotics
- Flight controllers read gyroscopes and accelerometers, run attitude-control loops, and update motor outputs at fixed rates. Popular open-source flight stacks run their fastest loops at hundreds of hertz to several kilohertz.
- Balancing robots and 3D printers rely on regularly timed control and stepper-motor pulses. A late step pulse on a 3D printer can show up as a visible defect.
Test, measurement, and scientific instruments
- Oscilloscopes, data acquisition systems, and logic analyzers capture samples at precise intervals. Hardware does the fastest work, but firmware has to keep up with buffers and triggers.
- Laboratory automation coordinates pumps, valves, and sensors on defined schedules.
- Particle accelerators and telescopes use distributed timing systems to synchronize equipment over large distances.
Summary table
| Application | Timing-critical function | Typical class |
|---|---|---|
| Airbag module | Fire inflators within the crash window | Hard |
| ABS / stability control | Modulate brake pressure | Hard |
| Engine control | Injection and ignition tied to crank angle | Hard |
| Fly-by-wire flight control | Fixed-rate control of surfaces | Hard |
| Motor drive / inverter | Current loop each PWM cycle | Hard |
| Grid protection relay | Detect fault and trip | Hard |
| Infusion pump | Dose delivery and alarms | Hard (alarms and dose limits) |
| PLC | Complete each scan cycle | Hard or firm, depending on the process |
| Vision inspection | Decide before the reject gate | Firm |
| Cellular baseband | Process each radio slot | Firm |
| Audio interface | Fill each buffer before playback | Firm or soft |
| Video playback | Decode each frame | Soft |
| Infotainment UI | Respond to touches | Soft |
Real-time systems that aren’t embedded
Real-time doesn’t always mean embedded. Some timing-critical systems run on servers or desktops:
- Trading systems must react to market data quickly, and some have regulatory timing requirements.
- Flight and driving simulators must update visuals and motion platforms consistently to avoid disorienting the user.
- Live broadcast and streaming infrastructure must deliver content on schedule.
- Air traffic control systems process radar and flight data on fixed update cycles.
These often run on real-time Linux or specialized operating systems on general-purpose hardware. Our pillar article on real-time embedded systems explains how embedded and real-time are separate properties that often, but not always, overlap.
What these applications have in common
Across industries, the same patterns repeat:
- A sense → decide → act loop that has to complete within a bounded time.
- Several deadlines of different strictness in one product. A car’s brake controller and its infotainment screen live in the same vehicle but have very different requirements.
- Priority-based scheduling, so urgent work can preempt less urgent work. See real-time scheduling and multitasking.
- Careful sharing of resources between tasks and interrupts. See RTOS task synchronization and inter-task communication.
- Domain standards that govern how timing and safety are demonstrated, in automotive, aerospace, medical, and industrial work.
Which RTOS do these applications use?
There’s no single answer, because the choice depends on the industry, the chip, and certification needs:
- Microcontroller-based products commonly use FreeRTOS, Zephyr, ThreadX, or vendor-supplied kernels. FreeRTOS is frequently reported among the most widely used in industry surveys. For a comparison, see FreeRTOS vs Zephyr vs ThreadX.
- Safety-certified and high-end systems often use commercial RTOSes such as VxWorks, QNX, INTEGRITY, or certified variants like SafeRTOS.
- Automotive ECUs frequently use AUTOSAR Classic platform operating systems.
- Many simpler devices use no RTOS at all, just interrupts and a carefully designed main loop. See RTOS vs super loop.
Frequently asked questions
What is an example of a real-time system?
An anti-lock braking system is a classic example. It reads wheel speeds and adjusts brake pressure continuously, and a late adjustment can let a wheel lock. Others include airbag controllers, pacemakers, flight controllers, and industrial motor drives.
Are all embedded systems real-time?
No. Many embedded systems, like a digital photo frame or a TV remote, have only loose timing expectations. For a broader look at everyday embedded devices, real-time or not, see real-life applications of embedded systems.
Is a smartphone a real-time system?
Parts of it are. The cellular modem and Bluetooth radio have strict timing requirements and typically run their own real-time firmware on dedicated processors. The main application processor runs a general-purpose operating system where most timing is soft.