Hi everyone,
I wanted to share a project I’ve been working on called simport.
GitHub: GitHub - karon-kali/simport: Run your real robot drivers against simulation. · GitHub
Why I built it ?
Simulation rarely tests what actually ships.
When running full-stack tests, hardware drivers are often modified to work with simulation or bypassed altogether. This means the very code responsible for communicating with the actual hardware never gets tested in the simulation loop.
Teleoperation often has a similar problem: one implementation is used for simulation and another for the real robot, and over time, the two begin to drift apart.
I wanted to address this gap.
simport puts simulated sensors and motors behind emulated hardware interfaces that speak each device’s real communication protocol. This allows the unmodified ROS 2 driver, along with the same teleoperation stack, to run both in simulation and on the physical robot.
Device configurations are described in YAML, while device-specific simulation logic lives in a small ROS 2 node.
What can simport do?
-
Emulate serial, UDP, TCP, SocketCAN and CAN-FD interfaces.
-
Define device communication protocols through YAML configurations.
-
Support binary and text-based protocols, including checksums, counters and packet framing.
-
Simulate two-way communication, including device commands and responses.
-
Connect simulated sensors and actuators to existing ROS 2 drivers.
Some working examples
I’ve implemented and tested examples for:
-
RPLIDAR A1
-
Bosch BNO055
-
NMEA GPS
-
Ouster OS1-64
-
Dynamixel XM430
-
Damiao motors
These examples demonstrate how existing ROS 2 drivers can communicate with simulated hardware through their original communication interfaces, without modifying the drivers.
The project currently targets ROS 2 Jazzy on Ubuntu 24.04.
Project repository
GitHub: GitHub - karon-kali/simport: Run your real robot drivers against simulation. · GitHub
The project is open source under the Apache 2.0 license.
I’d love to hear your thoughts, feedback and suggestions. In particular, I’d be interested in hearing about other hardware interfaces, devices or protocols that would be useful to support.
If you’re working on ROS 2 drivers, simulation or hardware integration, I’d be happy to discuss potential use cases and collaborations.
Cheers,
Karon
