Does the Raspberry Pi support real-time / deterministic operations?
Does the Raspberry Pi support real-time / deterministic operations?
Not fully. The standard Raspberry Pi OS (Linux) is not a real-time system and does not guarantee hard, deterministic response times. However, it is possible to significantly improve latency predictability, and in many applications achieve soft real-time, especially on the Raspberry Pi 5 with the PREEMPT kernel_RT.
What does 'real-time' mean on the Raspberry Pi?
In classic Linux, the task scheduler prioritises general-purpose processes, which is great for office applications, but does not provide an invariant (deterministic) response time to interrupts or I/O events. Therefore, in critical control systems, where latency must be within a fixed time budget, a simple Raspberry Pi OS can sometimes be insufficient. This limitation applies to the 'desktop' Linux kernel architecture itself, not just the hardware.
How to improve determinism and latency1?
A key Tools is patch PREEMPT_RT, which changes the way interrupts and critical sections are handled in the kernel, reducing scheduling times under load conditions. Initial tests for the Raspberry Pi 5 have reported up to 294-fold reductions in maximum latency (worst-case latency) relative to the standard kernel, virtually paving the way for soft real-time applications in Automation, data acquisition or hobbyist robotics. This is still not "hard" real-time, but for many tasks deterministic becomes sufficient.
When is "hard real-time" needed?
If an application requires a strictly guaranteed response time of microseconds or tens of microseconds, the best practice is to use a microcontroller without a full operating system. The RP2040 (Raspberry Pi Pico) is an example of such a chip: it runs bare-metal or under MicroPython/C/C++, has deterministic interrupts and resources for precise timing loops. This is why documentation and good practice recommend to delegate critical timing tasks to the MCU, and leave the Raspberry Pi for higher-level logic, networking, data logging or user interfaces.
Hybrid architecture in practice
In practical projects, both layers are often combined. The Pi controls the system and communicates with the environment, while the RP2040 implements the control loops with precise timing. Communication between the two can be via UART, I²C or SPI. This split reduces the impact of background tasks, disk queues or the Linux network stack on real-time signals, while leaving the convenience of a full operating system. For less time-critical tasks, Pi 5 with PREEMPT_RT and correctly set priorities is completely sufficient, providing stable responses and a reasonable latency budget in terms of soft real-time.
Transfer Multisort Elektronik (TME) is one of the world’s largest global distributors of electronic components, electrotechnical parts, workshop equipment, and industrial automation. The catalog includes over 1,500,000 products from 1,300 leading manufacturers. TME’s modern logistics centers in Łódź and Rzgów (Poland), with a combined area of over 40,000 m², ship nearly 6,000 packages daily to customers in more than 150 countries.
TME also invests in the development of knowledge and skills of young engineers and electronics enthusiasts through the TME Education project, and supports the tech community by organizing the TechMasterEvent series, promoting innovation and experience exchange.
