Skip to content

[Feature request]: Figure out what to do in the event of loss of odometry from a single agent. #31

Description

@arjo129

Before proceeding, is there an existing issue or discussion for this?

Description

A critical challenge in production environments is handling robots that unexpectedly go offline or lose localization. The current prototype implementation handles connectivity loss by stalling the fleet, which is unsustainable for real-world deployments where intermittent network dropouts are common. A robust framework is required to manage these scenarios effectively.

Implementation Considerations

The optimal behavior should be highly configurable, as different operational use cases demand distinct solutions. For example, in a high-density, highly controlled environment with a robust wireless network, it may be appropriate to issue a localized stop-work order and reroute other robots so a technician can safely retrieve the non-responsive agent. Conversely, in public service deployments like hotels or hospitals with minimal human support, controlling Wi-Fi quality is more challenging, and robots may continue operating normally despite intermittent connectivity.

To accommodate these varied scenarios, we must design an API that empowers system integrators to define and configure the appropriate error-handling behavior for their specific deployment needs.

Alternatives

No response

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions