EU Machinery Regulation (2023/1230)

EU Machinery Regulation (2023/1230) – definition

The EU Machinery Regulation, formally Regulation (EU) 2023/1230 on machinery, is the European Union legal framework for the design, conformity assessment, documentation, and placing on the market of machinery and related products. It was published in the Official Journal of the European Union on 29 June 2023 and replaces Machinery Directive 2006/42/EC with effect from 20 January 2027.

For mobile robotics, the Regulation may be relevant when an unmanned ground vehicle (UGV), robotic platform, safety component, or integrated robotic system is placed on the EU market or put into service in the EU. It applies to machinery intended for professional, research, educational, agricultural, construction, inspection, and other field applications, unless a specific exclusion in Article 2 applies, including machinery specifically designed and constructed for military or police purposes.

A Leo Rover or Raph Rover platform can be part of a machinery system under the Regulation when it is supplied with an integrated drive system, sensors, compute hardware, autonomy software, payloads, or safety-related functions. The applicable conformity route depends on the final configuration, intended use, hazards, and whether the system falls under a high-risk machinery category listed in Annex I.

Application to UGV and mobile robotics systems

The Regulation does not classify every development platform as a complete autonomous machine. A basic UGV platform, an add-on sensor kit, and a finished autonomous inspection robot may have different legal roles. The responsible economic operator must determine whether the supplied product is machinery, partly completed machinery, a safety component, another related product defined by the Regulation, or is subject to other applicable legislation.

For a mobile robot, the safety assessment normally considers the complete system rather than only the chassis. This includes mechanical motion, electrical power, battery charging, wireless control, navigation, perception, emergency stopping, payload integration, and software updates.

Manufacturer: the entity placing the finished robotic system on the market under its name or trademark.
Substantial modification: a physical or digital modification made after the machinery has been placed on the market or put into service, which was not foreseen by the manufacturer and creates a new hazard or increases an existing risk, may create new conformity obligations for the modifying party.
Intended use: the operating conditions, terrain, payload, users, environmental limits, and tasks specified in technical documentation and instructions.
Reasonably foreseeable misuse: predictable unsafe use, such as operation beyond a specified slope, payload, weather, speed, or communication range.

A laboratory prototype may fall under the research-use exclusion only where it is specifically designed and constructed for research purposes and temporarily used in laboratories. This exclusion should not be assumed for a UGV deployed in agricultural fields, construction areas, warehouses, campuses, or inspection sites.

Risk assessment for autonomous mobile robots

Article 10, together with the general principles of Annex III, requires manufacturers to perform a risk assessment and apply risk reduction measures before placing machinery on the market or putting it into service. The technical documentation must demonstrate how relevant essential health and safety requirements from Annex III were addressed.

For a differential-drive UGV such as Leo Rover, key hazards usually arise from motion and loss of control. A larger Raph Rover configuration can add hazards related to greater mass, higher payload, increased stopping distance, and the integration of external equipment.

UGV subsystem	Typical safety question	Relevant evidence
Drive control	Can a controller fault cause unintended motion?	Brake or stop behavior, watchdog logic, fault-state tests
Autonomous navigation	What happens when localization or obstacle perception is invalid?	Sensor diagnostics, degraded-mode specification, test logs
Wireless communication	Does loss of command communication lead to a safe state?	Timeout settings, stop-state validation, network architecture
Battery system	Are charging, thermal, short-circuit, and electrical hazards controlled?	Battery specifications, protection circuits, operating instructions
Payload	Does added equipment alter stability, visibility, or emergency access?	Mass, centre-of-gravity analysis, mounting instructions

The Regulation does not prescribe a specific ROS 2 topic rate, LiDAR range, map update frequency, or navigation algorithm. These are engineering parameters. They must, however, be justified where they affect safety functions or risk controls.

ROS 2, autonomy software, and safety-related functions

ROS 2 is middleware and a software development framework. It is not a conformity certificate and does not itself establish compliance with Regulation (EU) 2023/1230. A ROS 2 stack based on Nav2, SLAM Toolbox, robot_localization, RViz, or custom perception nodes requires system-level verification when its outputs influence vehicle movement.

A typical UGV architecture separates operational autonomy from independently assessed safety functions. For example, a navigation node can publish velocity commands, while the motor interface applies limits, timeout handling, emergency-stop logic, and fault monitoring.

# Example concept only - not a compliance configuration
cmd_vel_timeout_ms: 300
on_command_timeout: stop
max_linear_velocity_mps: defined_by_risk_assessment
max_angular_velocity_radps: defined_by_risk_assessment
require_estop_release: true
require_valid_motor_feedback: true

Where a safety function depends on software, the manufacturer should define the function, inputs, expected response, failure behavior, diagnostic coverage, and validation method. Common engineering references include ISO 12100:2010 for risk assessment and risk reduction, ISO 13849-1:2023 for safety-related parts of control systems, and IEC 62061:2021 for functional safety of machinery control systems. Their applicability must be evaluated for the specific machine and conformity route.

Cybersecurity and software integrity

Annex III includes requirements concerning protection against corruption for machinery products with digital elements. Such products must be designed and constructed so that connection to another device or remote communication does not lead to a hazardous situation. This is relevant to UGV systems using Wi-Fi, Ethernet, cellular links, remote teleoperation, OTA updates, ROS 2 DDS networking, or cloud-connected fleet tools.

For Leo Rover and Raph Rover integrations, the technical file should identify safety-relevant software components and document controls against accidental or intentional modification. Practical controls may include authenticated update procedures, access control, software version records, secure configuration backups, network segmentation, and verification of safety-critical parameters after deployment.

Conformity assessment and technical documentation

The manufacturer must select the applicable conformity assessment procedure under the Regulation. The procedure depends on the product category, including whether the machinery falls within Annex I, and on the use and coverage of applicable harmonised standards. Annex I identifies categories of machinery subject to specific assessment conditions, while the Regulation’s conformity assessment provisions define the applicable procedures.

A completed UGV system normally requires technical documentation under Annex IV and an EU declaration of conformity under Annex V. The documentation should be retained for at least 10 years after the machinery has been placed on the market or put into service.

Risk assessment and list of applicable Annex III requirements.
Mechanical, electrical, and software architecture documentation.
ROS 2 package versions, firmware versions, and configuration records where relevant to safety.
Test reports for emergency stop, command timeout, obstacle response, stability, and fault handling.
Instructions covering intended use, residual risks, maintenance, charging, transport, and safe integration of payloads.
EU declaration of conformity and CE marking, where required for the final product.

Use with Leo Rover and Raph Rover

Leo Rover is a four-wheel differential-drive mobile platform with an integrated Raspberry Pi compute unit and ROS 2 support. It is not an autonomous vehicle out of the box. A developer integrating Nav2, LiDAR, depth cameras, IMU data, or remote control must define the resulting system’s intended use and safety measures.

Raph Rover can support larger payloads and field-oriented integrations. Its use may require additional analysis of dynamic stability, payload retention, stopping behavior, operator separation, and sensor coverage. A larger platform does not remove the need for validation of the autonomy and safety architecture.

Normative references and standards

The following sources define the legal framework and provide commonly used engineering references. Harmonised standards must be checked in the current Official Journal citations because their status can change.

Regulation (EU) 2023/1230, European Parliament and Council, 2023.
Directive 2006/42/EC, repealed with effect from 20 January 2027.
ISO 12100:2010, Safety of machinery – General principles for design – Risk assessment and risk reduction.
ISO 13849-1:2023, Safety of machinery – Safety-related parts of control systems – Part 1: General principles for design.
IEC 62061:2021, Safety of machinery – Functional safety of safety-related control systems.
Leo Rover technical documentation, Fictionlab.

EU Machinery Regulation (2023/1230)