Roadmap. VDA 5050, OPC UA, joint maps, and the other protocol names on this page are not implemented. There is no custom-bridge service. OhhO is not a certification tool.
OhhO Bridge
Roadmap: protocol adapters beyond ROS 2.
- Category: Foundation
- Accent: violet
- Live app: Open bridge console
The console 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.
Overview (hero)
Bridge is a roadmap console. It lists protocol names. Public code today is the Yahboom serial driver and ROS 2 topics. OPC UA, VDA 5050, and per-model joint maps are not implemented.
Highlights
- Roadmap console — simulated adapter list
- Yahboom serial codec exists in the public driver
- ROS 2 topics are the supported interface today
What you get
- The Bridge page is a simulated adapter list. It does not translate a robot's native protocol into ROS 2.
- Roadmap names include DDS, MAVLink, CANopen, OPC UA, PROFINET, EtherNet/IP, MQTT, VDA 5050, Modbus, EtherCAT, ROS-Industrial, IEC 61131-3, and per-model joint maps. None of those adapters are implemented.
- Public code today is the Yahboom serial driver and ROS 2 topics. The standards page links to those files.
Features
- OPC UA — Roadmap. Not implemented.
- MQTT and VDA 5050 — Roadmap. Not implemented.
- DDS, MAVLink, and CANopen — Roadmap. Not implemented.
- PROFINET, EtherNet/IP, Modbus, EtherCAT — Roadmap. Not implemented.
- ROS-Industrial and IEC 61131-3 — Roadmap. Not implemented.
- Joint maps — Roadmap. Per-model joint maps and impedance defaults are not implemented.
- Yahboom serial codec — The public Yahboom driver is in the OmniBot repository. It is a serial codec, not a general protocol bridge.
How it works
- Open the console — You see a simulated adapter list. It does not install a protocol bridge.
- Read the names as a roadmap — OPC UA, VDA 5050, joint maps, and the other listed protocols are not implemented.
- Use what is public — ROS 2 topics and the Yahboom serial driver are in the OmniBot repository.
- Do not expect every console to follow — A protocol name on this page does not make Pilot, Autonomy, Fleet, or Mind work on that robot.
Specs
| Spec | Value |
|---|---|
| Public code | Yahboom serial driver and ROS 2 topics |
| OPC UA | Roadmap. Not implemented. |
| VDA 5050 | Roadmap. Not implemented. |
| Joint maps | Roadmap. Not implemented. |
| Other named protocols | Roadmap. DDS, MAVLink, CANopen, MQTT, Modbus, EtherCAT, PROFINET, EtherNet/IP, ROS-Industrial, IEC 61131-3. |
Plans
There is no paid plan. The console demo is free. Hosted cloud is a waitlist, not a checkout. There is no custom-bridge service.
FAQ
Do I need Bridge if my robot already speaks ROS 2? No. If your robot publishes standard ROS 2 topics, Connect is the transport that exists today. The other protocol names on this page are roadmap.
Which humanoid models are supported? None. Per-model joint maps are roadmap.
Can Bridge integrate with my factory's PLC and SCADA systems? No. OPC UA, PROFINET, EtherNet/IP, and IEC 61131-3 are roadmap.
Does Bridge support warehouse AGV/AMR fleet standards? No. VDA 5050 and MQTT adapters are roadmap.
Can I write my own bridge? Not as a product. There is no team that builds custom bridges. A new protocol would be new code in the open repository.