OhhO Connect
One link. Any robot. Any transport.
One link to any robot. OhhO Connect is the transport abstraction that lets every OhhO console — Pilot, Autonomy, Fleet, Mind — talk to any robot over whatever link the hardware exposes: Wi-Fi via ROSBridge, USB via Web Serial, Bluetooth Low Energy, or a built-in simulator. No SDK install, no Python, no robot-specific setup.
- Wi-Fi · ROSBridge WebSocket
- USB · Web Serial (firmware-direct)
- Bluetooth · BLE (Nordic UART)
- MQTT · IoT & cloud fleet connectivity
- Built-in simulator (no hardware)
- Robot-agnostic — one console, any robot
What you get
Every robot speaks a different language on a different wire. A DDS-native humanoid talks Cyclone, a mecanum base speaks a serial protocol over USB, a drone speaks MAVLink, an industrial arm speaks Modbus. OhhO Connect is the layer that makes all of them look the same to every OhhO product.
Connect exposes a single transport interface — connect, send velocity, send joint commands, emergency stop, subscribe to telemetry — and implements it for each protocol. A console built against Connect works on a mecanum manipulator over Wi-Fi today and a humanoid over USB tomorrow, with zero code changes.
Because Connect runs in the browser, there's nothing to install on the operator's machine. Web Serial and Web Bluetooth are feature-detected at runtime, and a deterministic simulator is always available — so you can explore every console before you ever wire up real hardware.
Built to do the hard parts for you
ROSBridge WebSocket (Wi-Fi), Web Serial (USB), Web Bluetooth (BLE), MQTT (IoT/cloud fleet), and a built-in simulator — all behind the same RobotTransport interface, feature-detected at runtime.
Connect speaks generic velocity and joint commands, not robot-specific SDK calls. A console built against Connect works on any robot with a transport implementation.
Web Serial and Web Bluetooth run in Chromium browsers over a secure context — no driver install, no Python SDK, no desktop app. Open a URL and drive.
Connect detects the HTTPS-to-ws mismatch and guides the operator to a secure rosbridge or a LAN connection, so the link just works instead of failing silently.
Each robot in the garage remembers its last protocol, address and baud rate — so reconnecting is one click, not a setup wizard every time.
A deterministic in-browser robot streams telemetry on every protocol slot, so you can demo, develop and test consoles without hardware on the bench.
How it works
Select a robot from your OhhO Garage — Connect loads its saved transport settings.
Connect shows the protocols available in your browser and on your robot — Wi-Fi, USB, BLE or Sim.
Connect establishes the transport, runs capability checks and streams live telemetry to every console.
Every OhhO console reads the live connection and never needs to know which protocol is underneath.
Specifications
- Transports
- ROSBridge (WS), Web Serial (USB), Web BLE, MQTT, Simulator
- Interface
- RobotTransport — connect, velocity, joints, e-stop, telemetry
- Browser
- Chromium (Chrome / Edge) for Serial + BLE; any for WS
- Persistence
- Per-robot config saved to garage (Supabase + localStorage)
- Simulator
- Deterministic in-browser telemetry stream
- Integrates
- OhhO Pilot, Autonomy, Fleet, Mind, all consoles
Which plan do I need for OhhO Connect?
We recommend the Spark plan. Connect is foundational and included on every plan, including free. You only need a paid plan for the consoles that sit on top of Connect — Pilot, Autonomy, Fleet and Mind.
Common questions
No. Connect runs entirely in the browser. Web Serial and Web Bluetooth are built into Chromium browsers (Chrome, Edge) — no driver, no SDK, no desktop app.
Yes. Web Serial talks the firmware protocol directly — no ROS needed. For DDS-native robots, pair Connect with OhhO Bridge to translate between DDS and ROS topics.
Connect feature-detects each protocol at runtime and shows only the ones your browser supports. Wi-Fi (ROSBridge) and the simulator work in any modern browser.
Works better together
Ready to build with OhhO Connect?
Start free and simulate first — no hardware required. Upgrade when you're ready to deploy.