Robotics & ROS Development
ROS and ROS2 software for robot prototypes and simulations, from node architecture and sensor integration to motion and navigation logic.
Custom quote after a short consultation · Timeline agreed in your quote
Scope: Prototype, simulation and research-level robotics where technically appropriate. We do not offer production hardware engineering.
Overview
We develop robot software on ROS and ROS2 for prototypes, simulations and research platforms. Typical work includes structuring a ROS2 workspace, writing nodes in Python, integrating sensors such as cameras, lidar and IMUs, implementing motion control and basic navigation, and migrating older ROS code to ROS2.
Robotics projects vary too much for fixed packages, so every engagement starts with a consultation about your robot, its sensors, the behaviour you need and whether simulation or hardware testing is appropriate. We then propose a scoped plan and custom quote. Development is organised into clear, documented packages, with Docker used to keep the build environment reproducible where that helps.
You receive source packages, launch files, configuration and documentation explaining how to build, run and extend the system. This is prototype, simulation and research-level work where technically appropriate; we do not offer production hardware engineering.
Who it’s for
- Research groups building or extending a robot platform on ROS or ROS2
- Start-ups developing a robot prototype that needs structured, maintainable software
- Engineering teams moving existing ROS code to ROS2
- Companies evaluating a robotic task in simulation before committing to hardware
Problems it solves
- Turn a hardware prototype into a robot that responds to sensors and commands
- Replace scattered scripts with a clean, documented ROS2 package structure
- Test robot behaviour in simulation before risking hardware
- Bring ageing ROS code onto a supported ROS2 distribution
What RF ETS delivers
- ROS or ROS2 packages with nodes, interfaces and launch files
- Sensor integration and configuration for the agreed devices
- Motion control or navigation logic within the agreed scope
- Simulation set-up or test scenarios where appropriate
- Build, run and architecture documentation
How we work
Consultation
We discuss the robot, its sensors and compute platform, the target behaviour and how it will be tested.
Scope and architecture
We propose a node and topic architecture and confirm deliverables in a custom quote.
Develop and simulate
Packages are developed in stages and tested in simulation or on your hardware, as agreed.
Integrate and document
We support integration on your robot remotely and hand over code with build and run documentation.
What we need from you
- A robot description, including URDF or CAD where available, sensors and compute hardware
- Your ROS or ROS2 distribution and any existing code
- A clear description of the behaviour or task the robot must perform
- Someone who can run tests on the physical robot, if hardware testing is needed
How pricing works
This work varies too much for fixed packages. We scope it with you, then send a written quote with price, timeline and deliverables before any work starts.
Tell us what you need
Use the quote form or book a consultation and describe your goal, constraints and deadline.
We scope it with you
We review your material and agree deliverables, assumptions and what is out of scope.
Written quote
You receive a fixed price or milestone plan, timeline and revision terms before any work starts.
Not included
- Third-party costs: domains, hosting, paid plugins and themes, software licences, API or AI-model usage fees, data-provider credits
- Work outside the written scope agreed before work starts (handled as an add-on or a custom quote)
- Ongoing support after the delivery and launch-support window unless a support package is bought
Need something different?
Tell us what you need, and we’ll prepare a solution and pricing based on your requirements.
Robotics & ROS Development: common questions
How is robotics development priced?
Robotics work is quote-only. After a consultation about your robot, sensors and goals, we send a custom quote describing the packages, behaviours and documentation to be delivered. There are no fixed packages because scope differs so much between robots.
Do you design or build robot hardware?
No. We work on prototype, simulation and research-level robot software where technically appropriate, and we do not offer production hardware engineering. Mechanical, electrical and safety design of the physical robot remain with you or your hardware partner.
What happens if the robot's requirements change during development?
Adjustments inside the agreed scope are covered by the revision rounds in your quote. New behaviours, sensors or platforms are scoped as a change request with updated cost and timing, which you approve before we proceed.
Can you migrate our ROS code to ROS2?
Yes. We review the existing packages, map nodes, messages and launch files to their ROS2 equivalents, and restructure where needed. The quote sets out which packages are migrated and how they will be tested.
Do you work with real robots or only in simulation?
Both, where technically appropriate. Many projects start in simulation to check behaviour safely, then move to your hardware, with your team running physical tests while we support remotely and adjust the code.
Often combined with
Arduino, ESP32 & Embedded Prototyping
Prototype firmware for Arduino, ESP32 and ATmega boards: sensors, actuators, displays and Wi-Fi or BLE, with wiring diagrams and Proteus simulation.
Custom quoteView service →AI & Machine LearningComputer Vision
Custom computer vision in Python for object detection, image classification and visual inspection, quoted after a review of your sample images.
Custom quoteView service →Engineering & CAD/CAMMATLAB & Simulink Engineering
MATLAB analysis and Simulink system models for engineers, businesses and researchers, delivered with commented files, result plots and a written explanation.
Custom quoteView service →