search

equinor / flotilla

Flotilla is the main point of access for operators to interact with multiple robots in a facility.
Eclipse Public License 2.0
16 stars 38 forks source link

Robot status not updating reliably during heartbeat handling #1383

Open andchiind opened 9 months ago

andchiind commented 9 months ago

Describe the bug Robots often get stuck in busy even though Isar reports both the missionStatus as being idle and robotStatus as being available. This is because we do not reach the end of 'OnIsarRobotStatus' even when the status is not consistent. This could also be an Isar issue where the event is not sent each time it should be.

To Reproduce The robot gets stuck in busy when, for instance, Isar completes a mission as soon as it's received. This happens for instance when localisation is not required for the given Isar instance. Currently the workaround is to make Isar sleep briefly after receiving such missions.

Expected behavior If Isar reports itself as being available, then this should be relayed to the Flotilla data model in when looking at the heartbeat messages.

Screenshots

aeshub commented 4 months ago

This issue has automatically been marked as stale as there has been no activity for 60 days.

Christdej commented 3 months ago

Waiting for new status solution in ISAR

aeshub commented 1 month ago

This issue has automatically been marked as stale as there has been no activity for 60 days.