Public Protocol
Platform

Element 9.28

Robot software and simulation

Sheet
9.28
Chapter
9 Manufacturing and repair
State
Drafted
Release
16 November 2026
Editor
Contributed by Praecise as open research
Reviewers
To be named at review
Safety
S2, as the chapter
Licence
CC BY-SA 4.0
Resources
9

The element

Requirement

The community's robots run on open, documented software that more than one member can install, update and repair, and new behaviour is tried in simulation before it runs on a real machine near people.

How to tell
  • The software stack is named and its versions recorded, with a supported release. ROS 2 releases and target platforms are set out in REP-2000 (ROS 2 (Robot Operating System)); the Gazebo simulator lists Jetty as its long-term release, supported from September 2025 to May 2031, and pairs each Gazebo release with a ROS 2 distribution (Gazebo).
  • Arm planning, navigation and flight use maintained frameworks: MoveIt for arms, stating use on over 150 robots (MoveIt); Nav2 for ground navigation (Nav2); ArduPilot or PX4 for vehicles (ArduPilot, PX4 Autopilot).
  • Each change is tested in simulation first, and the test is recorded.
Options
  • ROS 2 as the common layer for sensors, control and tools (ROS 2 (Robot Operating System)).
  • Motion planning, kinematics and collision checking for arms (MoveIt).
  • Navigation with behaviour trees and plugin planners for mobile robots (Nav2).
  • Simulation: Gazebo for general robotics (Gazebo); Isaac Lab for robot learning, with documented examples of moving policies from simulation to real robots, under BSD-3-Clause with some parts Apache-2.0 (Isaac Lab).
  • Learning-based control with a standard dataset format and policies (LeRobot).
  • Industrial logic for machines in IEC 61131-3 languages (OpenPLC Runtime v4).
Settled, open, contested

Settled: ROS 2, MoveIt, Nav2 and the open autopilots are maintained, documented and in industrial use (MoveIt, Nav2, ArduPilot). Open: how well behaviour learned in simulation holds on real robots in the community's conditions; projects document examples (Isaac Lab) but each transfer must be tested. Contested: one framework for everything or the simplest tool for each machine. ROS 2 gives a shared language; a microcontroller or PLC program is simpler to keep for a single machine.

The four stages

Resources at each stage

1 Learn

Understand

2 Design

Size and choose

3 Build

Build or obtain

4 Deploy

Install, run and measure

What changes between 30 adults and 300 people

At 30 adults, one member who knows ROS 2 and one simulation set-up are enough, and robots are projects. At 300 people, robots are infrastructure: versions are pinned, updates are tested in simulation and on one robot before all, and at least two people can restore each robot's software.

Reference designs

Open for contributions Designs with drawings, specifications and a bill of materials. Add to it

Parts list

Every resource that supports this element. Those marked External carry the label “External resource. Not made or verified by Public Protocol”.

ResourceTypeOriginMaturitySafetyLicence, as stated at its source
ArduPilotToolExternalEstablishedS3GPLv3
GazeboToolExternalEstablishedS0Website pages CC BY 4.0; software licence not stated on the page opened
Isaac LabToolExternalWorkingS0BSD-3-Clause, with certain parts under Apache-2.0
LeRobotLibraryExternalWorkingS2Apache-2.0
MoveItToolExternalEstablishedS2BSD
Nav2ToolExternalEstablishedS2Not stated on the page opened
OpenPLC Runtime v4ToolExternalWorkingS2GPLv3, with a commercial licence available
PX4 AutopilotToolExternalEstablishedS3Not stated on the page opened
ROS 2 (Robot Operating System)LibraryExternalEstablishedS0Not stated on the page opened

Depends on, and completes

Depends on 13.1, 9.6.

It is one of 34 elements that complete Manufacturing and repair.

The standing questions

Who keeps the software current. Who may push a change to a robot that works near people. Who pays for the computer that runs simulation.

Environments

No source found on how robot software changes with environment; the hardware and sensors carry the environmental limits. Where internet access is poor, keep installers, packages and documentation offline (13.1).

Safety

State and evidence

Drafted

An editor has written the element's text from the resources listed under it, citing them. It is checked when it is reviewed.

Evidence from a real place or system is recorded here, with what did not work. What the states mean

History