Robotics · R-05
Off ROS 1, with your robots still running.
A move from ROS 1 to ROS 2 in stages: a workspace audit, a map of every dependency, a port package by package, and simulation regression tests before any code reaches a robot. The workspace scan is free, and the written quote comes after it.
- Free scanof one ROS 1 workspace
- Dependency mapevery package and what it needs
- Staged portpackage by package
- Simulation testsbefore code reaches a robot
What we do
A move in stages, not a rewrite
The robots keep running on the old stack until each stage passes its tests. Each stage is quoted after the scan.
Workspace audit
Every package, custom message, launch file and build setting in the workspace, with what each one does and who still uses it.
Dependency map
Which packages depend on which, which outside packages have a ROS 2 version and which do not, and the order the port has to follow.
Staged port
Packages move one group at a time, bridged to the ROS 1 side while both run, so a stage can ship without waiting for the whole stack.
Simulation regression tests
Test scenes for the robot's real jobs, run in CI on every change and compared with the ROS 1 behaviour before a stage reaches a robot.
Drivers and launch files
Hardware drivers and launch files ported or rewritten for ROS 2, tested on one robot on a bench before the fleet.
Handover
A written record of every decision, CI that runs without us, and a runbook your team can follow for the next release.
How it starts
A free scan, then a written quote
- NDA first. Then read access to one ROS 1 workspace, or an export of it
- The free scan: packages, dependencies, custom messages, launch files and what has no ROS 2 equivalent yet
- A written summary of the scan and a quote per stage, with the people on the job named
- Port in stages: simulation first, then one robot, then the fleet
- Handover with CI and a runbook, or we stay on
What the scan is
- One ROS 1 workspace
- A written summary you keep
- A quote, with no obligation to take it
Questions about a ROS 2 move
What does the free scan cover?
One ROS 1 workspace: packages, dependencies, custom messages, launch files and build setup. You get a written summary and a quote, and you keep the summary whether or not you go ahead.
Do our robots stop during the move?
The plan is built so they keep running. Each stage runs in simulation first, then on one robot, and the ROS 1 side stays in service until the stage that replaces it passes.
Which ROS 2 distribution do we move to?
The one that fits your hardware, your outside packages and your support window. The scan names it and writes down the reason.
Do you port motor firmware or safety controllers?
No. Those stay with your team or a partner. We port the ROS software around them and keep their interfaces as they are, or change them only with their owner in writing.
More robotics service lines: North America launch for robot makers · Fleet console and remote operations · Signed software updates for robots · Connect robots to your systems. All ten on the Robotics page.
Ask for a free workspace scan.
Send a note on the robot and the workspace. After the NDA, we scan it and reply in writing with a summary and a quote.
Ask for a scan All robotics lines
Reply within one business day