I propose the use of a SBC (single board computer; like a Raspberry PI) with a camera module (think of inexpensive, commodity hardware) that could be configured with the minimum amount of software required to connect to the LocusOne system and read Locus Points as they pass by, and report the location to the LocusOne system. The SBC and camera module would be in its own box and would be fastened to the MHE, probably pointed to the side so that it could see the LPs on the shelves.
An interesting alternative or extension of this idea would be to implement the MassRobotics Interoperability standard on this SBC, or in the LocusOne system, so that in addition to being able to deconflict with our own bots, we would have what could hypothetically be a standalone product, which could be used to locate MHE in warehouses, and share its location and status using the standard, allowing ALL bots and MHE to play nicely together.
Phase two or three could include outputs, such as lights or sounds, on the MHE locator box, so that feedback could be given to the MHE operators if a bot is in close proximity to the MHE.
Problem/opportunity trying to be solved
Bots get damaged by interactions with MHE. |
|
Quantify the problem/opportunity
In addition to preventing damage to our bots from MHE interactions, there's also a big opportunity to track and report the location and activities of MHE within our Dashboards and reporting tools. Also lots of opportunities to optimize traffic around MHE. And in some cases, have MHE interact with bots intentionally (such as the rare cases when we might want a Max to be directly loaded by a fork truck.) |
|
What is the root cause of the problem/opportunity
We don't know where the MHE is. |
|
Customer need date | Apr 1, 2023 |
Urgent request | No |
Report Tag | Deployment |
Upvote.