You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
andchiind
changed the title
Update Robot status during heartbeat handling
Update Robot status reliably during heartbeat handling
Feb 1, 2024
andchiind
changed the title
Update Robot status reliably during heartbeat handling
Robot status not updating reliably during heartbeat handling
Feb 1, 2024
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
The text was updated successfully, but these errors were encountered: