Skip to content

The five-year log: what the EU Machinery Regulation asks of your robot’s data layer

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.


Key takeaways

  • The Machinery Regulation (EU) 2023/1230 applies from 20 January 2027 and replaces the Machinery Directive 2006/42/EC.
  • Annex III 1.2.1(f) requires a tracing log of interventions and of each safety software version uploaded after the machine is placed on the market, kept for 5 years after each upload.
  • The log sits on the same flash or SSD as the robot’s software, so it has to stay intact through power loss, flash wear and failed updates.
  • The file system needs 4 properties to keep it reliable: atomic records, clean recovery, integrity across updates and tamper evidence.
  • A gap in the log weakens the OEM’s conformity evidence, and German law provides fines of up to €100,000 for failing to take required corrective action.

What the regulation asks for

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.

  • Annex III 1.1.9, protection against corruption. Software and data critical to safety must be identified and protected against accidental or intentional corruption. The machine must also collect evidence of legitimate and illegitimate interventions (Bluefruit summary of Annex III).
  • Annex III 1.2.1(f), the tracing log. The control system must enable a tracing log of the data generated by any intervention, and of each safety software version uploaded after the machine was placed on the market or put into service. Each entry stays available for five years after the upload it relates to.

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.

Why a five-year log is a storage question

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).

What the file system has to guarantee

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.

RequirementWhat it means for the logHow Tuxera supports it
Atomic recordsEach entry is written whole or not at all; a power cut never leaves a half-written recordTuxera 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 recoveryThe controller mounts and boots cleanly after every interruption, with the log intactOpto 22 tested NitroFS through hundreds of thousands of power-fail events, with clean reboots throughout (success story)
Integrity across updatesA failed safety software update returns to a known-good state, and the log survives itTuxera SnapFS rolls back to a known-good snapshot; it is in active development, with early access ahead of general availability
Tamper evidenceSilent corruption or manipulation of the log is detectedSnapFS 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.

Enforcement and liability

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.

  • Conformity on request. Manufacturers must provide an authority, on reasoned request, with all the information needed to demonstrate conformity. Where a product is out of conformity, they must bring it into conformity, withdraw it or recall it (Articles 10(9) and 10(10), consolidated text).
  • Market measures. If corrective action is not taken in time, market surveillance authorities ensure the product is withdrawn or recalled, or its availability is prohibited or restricted (Article 43(4)).
  • National penalties. Each member state sets its own. In Germany, the implementing act provides fines of up to €100,000 for failing to take required corrective action, and up to €10,000 for other offenses, including failing to provide requested information (§ 9 MaschinenDG).
  • Product liability. The revised Product Liability Directive applies to products placed on the market after 9 December 2026 and covers software, including updates. Courts can order disclosure of relevant evidence, and a presumption of defectiveness can arise where a defendant fails to disclose it or a product breaches mandatory safety requirements (A&L Goodbody).

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.

Getting ready before 20 January 2027

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:

  1. Where does the tracing log live? Decide whether it sits on the controller, in the safety element, on a gateway or off the machine, and who owns it.
  2. Will every record survive a power cut? Test the log under random power interruptions, including during writes and during boot.
  3. Will the log outlive five years of writes? Size the write budget and flash endurance for the full five-year retention period.
  4. Will it survive a failed update? A safety software update that rolls back must leave the log, and the record of that update, intact.
  5. Can you show it is untampered? Plan how integrity is verified when an authority asks for the log.

Tuxera’s file systems already protect data through power loss in industrial controllers, including PLCs and pharmaceutical machinery.

References

  1. Regulation (EU) 2023/1230 on machinery, consolidated version 27 July 2026, EUR-Lex (PDF copy)
  2. Machinery Regulation guide: what the first draft chapters say, TESTPLUS, November 2026
  3. EU Machinery Regulation 2023/1230, IEC 62443, and the CRA, Bluefruit Software, October 2026
  4. Machinery Regulation (EU) 2023/1230: duties, VamiSec
  5. § 9 Maschinenverordnung-Durchführungsgesetz (MaschinenDG), German Federal Ministry of Justice
  6. EU revised Product Liability Directive: what you need to know, A&L Goodbody, March 2026
  7. KUKA first in robotics to achieve Security Level 2 certification, KUKA, July 2026
  8. Safety FAQ, Universal Robots, May 2026
  9. Industry 4.0 and IIoT: the rise of industrial robots, Electronic Design, February 2022
  10. Opto 22 keeps its industrial controllers power-fail safe with Tuxera NitroFS, Tuxera

This article is general information on the regulation and is not legal advice.

Next step
Test your tracing log under power loss
If your team is designing for the five-year log, we offer a power-cycle test on your platform.

Suggested content for:

Our products

Your mission-critical systems demand uncompromising reliability. Tuxera products mean absolute data integrity. We specialize in file systems, software flash controllers, and secure networking and connectivity solutions. We are the perfect fit for data-intensive, mission-critical workloads. Using Tuxera’s time-proven solutions means that your data is safe and secure – always.

Proven success

Our solutions are trusted by major brands worldwide. When you need reliable, scalable, and lightening-fast data access and transfer across any system or device, Tuxera delivers. Our track record speaks for itself. We’ve been in this business for decades with a clear mission: to be the partner you can trust. Read on to find out more.

Related pages and blog posts
Technical Articles
Datasheets & Specs
Whitepapers