Safety & Control
Stop, e-stop, and motion commands. Lowest latency, and duplicated across paths so a single link loss never drops control.
- Duplicated across the two best links.
- Pre-empts every lower class.
Robot Connectivity · Link-Bonding
Robot fleets ride Wi-Fi, LTE, and 5G that drift under load. Benison adapts its own link-bonding IP — field-proven in thousands of constrained edge devices — to robot edge connectivity, scoring every path in real time and steering each traffic class to the link that fits. Proven IP, adapted to robotics — not built from scratch.
The Evidence
Our Customers
Traffic Classes
Bonding starts by classifying flows. Safety can't wait and can't drop; bulk can. Each class gets the path — or paths — that fit.
Stop, e-stop, and motion commands. Lowest latency, and duplicated across paths so a single link loss never drops control.
Human-in-the-loop control and operator video. Latency- and jitter-sensitive.
Pose, health, battery, and task state. Steady and loss-tolerant.
Updates, log sync, and recorded video. Lowest priority and cost-aware.
Our Approach
We adapt a proven algorithm to your robot's flows and links, then prove failover before it ships.
Map each robot flow to a class with its own priority and path policy.
Continuously score each transport on the signals that predict failure.
Route each class to the link that fits — and duplicate what can't drop.
When a path degrades, traffic re-steers before control is affected.
Where The Work Sits
The robot application never changes. Bonding is a transport- and dataplane-level concern, implemented where the packets actually are.
What You Own
Every link-bonding engagement leaves your team owning the policy, the package, and the evidence.
Every robot flow mapped to a class, priority, and path policy for your fleet.
The scoring weights and thresholds, tuned to your transports and environment.
The packaged bonding agent for your ARM/edge runtime, with a validation harness.
Link-loss scenarios, failover timing, per-class route decisions, and degradation behavior.
Common Questions
Straight answers to the questions that decide whether we get a technical call.
Real IP. It already runs in thousands of constrained networking devices. The robotics work is adapting it to robot traffic classes and edge conditions — not inventing bonding from scratch.
Yes. The IP is built for ARM CPE-class hardware, 256 MB–1 GB RAM. Classification and enforcement run in the kernel dataplane (tc/XDP), so steering stays low-overhead.
No. Bonding is a transport- and dataplane-level concern. The ROS 2 application is unchanged; we work below it.
You own the agent, configs, scoring policy, and validation harness. It’s delivered for your runtime and your fleet.
Get Started
Tell us how your robots connect, and we’ll scope a bonding engagement with failover evidence you own.
If you're a tech geek or know someone who is, fill in the form to work with us.