Why industrial controllers lose data after power interruptions
Industrial controllers may restart after a power interruption but return with missing, stale, or inconsistent data. This article explains the...
We are here to help
Have a question or need guidance? Whether you’re searching for resources or want to connect with an expert, we’ve got you covered. Use the search bar on the right to find what you need.
From 20 January 2027, every robot placed on the EU market has a new record-keeping duty. The Machinery Regulation (EU) 2023/1230 asks robot control systems to keep a tracing log of interventions and of each safety software version uploaded after the robot leaves the factory, for five years after each upload.
That record is written across thousands of power cycles and years of field updates, on flash that wears with use, and it has to be complete on the day an authority asks for it. That makes the data layer part of a robot OEM’s safety case.
The Machinery Regulation (EU) 2023/1230 applies from 20 January 2027 and replaces the Machinery Directive 2006/42/EC. For the first time, two of its essential health and safety requirements address software and data directly.
The Commission’s draft guide chapter on these sections, dated 18 October 2026, adds that each event must be stored for at least five years after a change in the safety software, and that the log should be kept in a reliable storage location. The draft is non-binding and still awaits endorsement (TESTPLUS, Notified Body 2908).
For machinery with self-evolving behavior, control systems must also record safety-related decision data for one year (VamiSec). AI-driven robots therefore have the same storage problem to solve.
Robot controllers already log a great deal: axis positions, servo data and event logs that let a robot resume after a power event. Much of that critical state has traditionally lived in battery-backed SRAM, which needs battery maintenance over the robot’s long service life (Electronic Design).
The tracing log is a record that grows for years on the same flash or SSD that holds the robot’s software. Over five years it has to stay intact through brownouts and unplanned shutdowns, and through every safety software update the OEM ships.
Embedded engineering firm Bluefruit notes that five years of intervention records must survive power loss, flash wear and firmware updates, and the log must be protected from the tampering it exists to record. Where the log lives (on the device, on a gateway or off the machine) shapes the memory budget and the update design, so it is decided early (Bluefruit).
The reliability of a tracing log depends on the file system that writes it to flash. Four properties decide whether a record written in 2027 is still intact and readable in 2032.
| Requirement | What it means for the log | How Tuxera supports it |
|---|---|---|
| Atomic records | Each entry is written whole or not at all; a power cut never leaves a half-written record | Tuxera EdgeFS never overwrites live data and keeps metadata consistent with user data; Tuxera NitroFS brings the same power-fail safety to Linux and VxWorks controllers |
| Clean recovery | The controller mounts and boots cleanly after every interruption, with the log intact | Opto 22 tested NitroFS through hundreds of thousands of power-fail events, with clean reboots throughout (success story) |
| Integrity across updates | A failed safety software update returns to a known-good state, and the log survives it | Tuxera SnapFS rolls back to a known-good snapshot; it is in active development, with early access ahead of general availability |
| Tamper evidence | Silent corruption or manipulation of the log is detected | SnapFS protects user data and metadata with a Merkle tree, so tampering is caught and a bad read fails safely |
Where the safety controller itself owns the log on a microcontroller, EdgeFS CERT follows MISRA C and comes with a complete set of certification artifacts. EdgeFS runs on RTOSes including FreeRTOS and SafeRTOS, from as little as 4 KB of RAM.
The log exists to demonstrate conformity when a national authority makes a reasoned request. It is the OEM’s evidence, and a gap in it weakens that evidence when the request arrives.
The regulation describes the tracing log as conformity evidence rather than a liability record. Even so, an OEM with a complete, trustworthy history of safety software changes is better placed in a liability claim as well.
Robot OEMs have started to prepare. In July 2026, KUKA announced that its iiQKA.OS2 robot systems meet the requirements of the Machinery Regulation, alongside IEC 62443-4-2 Security Level 2 certification (KUKA). Universal Robots is targeting ISO 10218-1:2025 certification for all PolyScope 5 and PolyScope X products by January 2027, aligned with the Machinery Regulation date (Universal Robots).
Five questions help an engineering team check its own readiness:
Tuxera’s file systems already protect data through power loss in industrial controllers, including PLCs and pharmaceutical machinery.
This article is general information on the regulation and is not legal advice.
Suggested content for: