adept technology SmartFleet EX, Руководство пользователя

Страница: 38 / 54

Chapter 5: Operation
When the Adept Enterprise Manager receives a request, it does the following:
1. Queueing
l
The request is assigned a default priority (unless another priority is
specified) and put into the queue.
Pickup/Dropoff requests are entered as two separate jobs - a pickup, and a
dropoff.
Each segment has a unique queue ID, as well as a job ID that tracks the entire
pickup/dropoff sequence.
l
Allows for canceling the job.
2. Dispatching
l
A robot is selected, based on the criteria you specified.
l
The robot is sent to the goal.
3. Tracking
l
The queueing manager monitors the robot and job status.
l
The job is deleted from the queue when the request has been satisfied, or
requeues the job in the event of failure.
Jobs can be in one of six states:
l
Pending - new, unassigned jobs.
l
In Progress - jobs that are being actively processed.
l
Completed - jobs that were successfully processed.
l
Failed - jobs that failed, due to reasons such as a blocked path or E-Stop. These
jobs will not be retried.
l
Canceled - jobs that were manually canceled with the queueCancel command
l
Interrupted - jobs that have been interrupted by an Operator manually controlling
the robot. These will be reassigned after a brief wait.
Manually Clearing the Entire Queue
If you ever wish to clear the entire queue, you can do so by temporarily adding a special
startup argument to ARAM. The following procedure will clear the queue:
1. In SetNetGo, find the ARAM Custom arguments field.
Enter "-enableEnterpriseManagerFlush" in the field, and click Apply.
2. Wait for the software to restart, then connect with MobileEyes.
3. Use the CentralServerDisplayDeliveryQueue custom command (in MobileEyes) to verify
that the queue has been cleared.
4. In SetNetGo, remove the "-enableEnterpriseManagerFlush" entry, and click Apply.
5. Wait for the software to restart.
Adept SmartFleet EX User’s Guide, Rev. A
Page 38 of 54