Doceva hardware

Edge networking for remote robots

We’re building a separate way for teams to reach a robot when its main computer freezes or its network goes down

First prototype in development

Explore the hardware

System overview

A separate connection to the robot

A robot’s main link carries its everyday traffic

Our network gives the recovery module its own connection, so your team has another way in when the usual link fails

Fleet teamRobot computerRecovery moduleMain linkSeparate link

Fleet team

Main link
Robot computer
Separate link
Recovery module

Hardware families

The hardware on the robot

We design the network, the recovery module and the small computers that bring them together

Recovery process

What happens when a robot goes quiet

A lost connection and a frozen computer can look the same from the site office

  1. Spot the failure

    The recovery module checks whether the main computer is still answering

  2. Check the robot

    The team uses the separate link to check what went wrong before deciding on a restart

  3. Restart the computer

    If a restart is enough, the team can do it without sending someone to the site

See the recovery steps

Design limits

When someone still needs to go

Safety controls stay on

The lifeline never goes around the robot’s own safety controls

Physical repairs stay on site

Broken parts and robots that tip over still need someone on site

Applications

Sites far from the repair bench

We’re designing the lifeline for small robotics teams whose fleets work far from a technician

Solar farms

Robots work across wide fields of panels, far from the site office

Agriculture

Farm robots spread out over large fields, a long way from the nearest technician

Mining

Mine sites are remote and slow to reach, so every trip takes a person off other work

Development status

Building the first recovery module

The circuit drawings are ready and we’re sourcing parts for the first prototype

Our hardware is not for sale yet

See our progress