Robotics

Deadline-Aware Runtime Assurance for Autonomous Mobile Robots Under Sensor Degradation

An independent research study combining a mathematical recoverability model, a conservative braking supervisor, numerical simulation and measured software execution.

Reduced-order simulation researchCase study 7 of 10

Research architecture connecting timestamped observations to a recovery certificate and command-lease braking watchdog.
Engineering diagramFull-size image ↗

The challenge

A mobile robot can lose its ability to recover safely before an immediate collision warning. Localisation uncertainty, ageing measurements and delayed commands must be considered together.

How the system works

Timestamped observations and command records form a bounded position estimate. A recovery certificate combines uncertainty, geometry, response delay and braking capability to select continue, restrict or recover. Command leases and a separately scheduled watchdog trigger braking when an approved command expires.

Design decisions

  1. Preserved a feasible braking manoeuvre through a state-dependent clearance envelope and admissible-speed limit.
  2. Propagated measurement age and outstanding commands into the recovery calculation.
  3. Kept the simulated plant moving during delayed computation and compared matched fault schedules across six supervisor variants.
  4. Evaluated learned anticipation separately from the model-based safety certificate.

What the evidence shows

Evaluated 100,000 sampled boundary states, 32,400 navigation episodes, 3,900 supplementary episodes, 24,000 wall approaches and four process-based timing cases. Joint supervision completed 5,268 of 5,400 navigation episodes versus 2,674 for a global worst-case supervisor. Both recorded zero collisions in 3,000 bounded wall approaches; beyond-bound tests exposed failures when braking or response-delay assumptions were violated. The study uses a reduced-order model and static obstacles.

Research publication

Read the research report on Zenodo

Contact

Let's make the next system work.

Discuss an engineering role, a project or a research collaboration. Tell me what you are building, where it gets difficult and what a useful result would look like.

  1. Send the formIt is sent from this page, without publishing my email address.
  2. I reply to youTo the address you give, with questions or a next step.
  3. Project work starts with DefineA short, fixed-fee phase that sets the scope and the tests.

0 of 4000 characters

Sent from this page, so my email address is never published.