Make it configurable to require recovery mode after any e-stop, plus roll or manual movement. I know there is currently a tolerance built in, but some customers would like it to be a requirement.
Problem/opportunity trying to be solved
There are times when a bot is e-stopped and rolls or is moved that the e-stop can be disengaged and the bot released. This is causing some bots to be mis-localized and cause congestion in queues and pick areas. |
|
Quantify the problem/opportunity
This issue is contributing to motor faults, increased mission time and congestion |
|
What is the root cause of the problem/opportunity
Recovery mode is not always triggered after e-stop |
|
Customer need date | Aug 31, 2023 |
Urgent request | No |
Report Tag | CSM |
This is typically a good feature for Locus. We need to solve the motor fault due to robot loading issue separately.