OhhO Bridge
Roadmap: protocol adapters beyond ROS 2.
Bridge is a roadmap console. It lists protocol names. Public code today is the Yahboom serial driver and ROS 2 topics in the OmniBot repository. DDS, MAVLink, CANopen, OPC UA, VDA 5050, MQTT, and per-model joint maps are not implemented.
- Yahboom serial codec exists in the public driverEvidence
- Roadmap console — simulated adapter list
- ROS 2 topics are the supported interface today
Simulated data — connect a robot via Connect for live data
Concept render — not footage of OmniBot
Works today
- Yahboom serial driver packet codec in public OmniBot repositoryEvidence
In progress
- Protocol adapter framework beyond ROS 2OHH-40
Vision: not built
Connect your robot. Even the ones that don't speak ROS.
OhhO Connect handles the transport; OhhO Bridge handles the language. Bridge is a library of protocol adapters that translate between a robot's native protocol — a DDS LowCmd/LowState interface, a MAVLink autopilot, a CANopen motor bus, an OPC UA factory cell, a Modbus PLC arm — and the standard ROS 2 topics every OhhO product already speaks. One adapter per protocol family, and your robot joins the platform.
- Robot protocols
- DDS, MAVLink, CANopen, Modbus, EtherCAT
- Factory protocols
- OPC UA, PROFINET, EtherNet/IP, IEC 61131-3
- Fleet protocols
- MQTT, VDA 5050
- Industrial arms
- ROS-Industrial compatible, Modbus, EtherCAT
- Humanoid models
- Per-model joint maps, configurable for your robot
- ROS 2 topics
- /cmd_vel, /joint_states, /imu/data, /odom
- Gain profiles
- Default kp/kd per joint per model
- Runtime
- ROS 2 node (onboard PC) + browser codecs
- Integrates
- OhhO Connect, Frame, all consoles
Works better together
Ready to build with OhhO Bridge?
The engine and this console demo are free. Hosted cloud is a waitlist, not a checkout.