Integrating Adamo @trossenrobotics HQ!
Had great fun in chicago a few weeks back with the trossen team.
It's great to see people notice just how fast we are, but highlights how much of an issue it has been with many existing teleop solutions.
If you want to try it out, we are now self serve, so just click 'get started' on our website to feel the @Adamorobotics speed!
This robot is being controlled by someone 5,500 miles away.
This is a demo of our teleoperation stack at @Adamorobotics. The robot is in our London office. The operator is in San Francisco.
The bottleneck in robotics has shifted from R&D to deployment. Robots still can't handle every edge case. When autonomy fails, you need a human in the loop, fast.
We've built the fastest teleoperation stack on the planet for remote human control of any robot, anywhere in the world.
This is what makes real-world deployment possible today.
Every day, we power thousands of interventions for humanoid and autonomous vehicles, and we're only just getting started.
You can now try it yourself for free, at https://t.co/HXNiOT3ZhN
So many teleop folks use WebRTC. Great for Google Meet, not so much for teleop.
This @Adamorobotics demo is a nice showcase of why WebRTC is the wrong choice for teleop.
Long-distance real time teleop.
A lot of people see teleop as a dirty secret in robotics, but only if you're using it whilst saying you're fully autonomous.
It's actually a great step to get to fully autonomy.
We built @Adamorobotics , a low-latency long-distance teleoperation platform for robots to bypass the real-world data bottleneck.
Here's a comparison video of our robot being teleoperated in London
Adamo on the left versus google meets on the right (a WebRTC-based solution)
As you can see there's a big delay. That delay makes teleoperating a lot harder, and the data you capture of far inferior quality.
Adamo is now self-serve so you can feel what low latency long distance teleop feels like for yourself.
WebRTC is designed for Video Conferencing, not Robotics.
This is @IlirAliu_ teleoperating from SF -> London using our software.
At @Adamorobotics, we are able to teleoperate across the Atlantic with 0 buffering using our custom protocol and dedicated network.
Most teleoperation is done through WebRTC. WebRTC-based applications usually add a buffer to smooth out issues from dropped packets and network jitter.
In teleoperation, adding latency through a buffer is not an option. We have to find alternative ways of providing a stable connection. The solution is a custom protocol and dedicated, globally distributed infrastructure.