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

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

Chapter 5: Operation
in the Adept Motivity User's Guide .
The tasks involved are generally:
l
Generate a map, using a single robot.
l
Upload the map to the Adept SmartFleet EX and make it the current map.
The map will automatically get downloaded to each robot in your fleet
The Adept SmartFleet EX communicates with each robot individually, rather than doing a
broadcast. In addition to maps, it can download configuration parameters to each robot.
NOTE : If you are doing a trial with a single robot, you should save the data and
configuration to your PC, and then download from your PC to the Adept SmartFleet
EX.
5.5 Managing Queueing (Adept Enterprise Manager only)
The Adept Enterprise Manager includes the ability to queue jobs (goals and their associated
tasks). It can accept multiple requests for robots, and then select the best robot for each job,
based on the criteria you specify. It sends the selected robot to the requested location, per-
forming any associated tasks. It tracks the status of jobs and robots as they perform their
assigned jobs.
The requests that are queued include:
l
a request for any robot to be sent for a pickup (PICKUP) for which the delivery des-
tination (DROPOFF) is not yet known (queuePickup ARCL command).
It is assumed that the delivery destination will be communicated directly to the robot
that responds, prior to completion of the pickup.
l
a request that a specific robot drive to a particular goal (DROPOFF) (queueDropoff
ARCL command).
This is communicated directly to the robot, but is queued and tracked by the queue on
the Adept Enterprise Manager.
l
a request that a robot be sent for a job that has predetermined pickup and dropoff des-
tinations (queuePickupDropoff ARCL command).
In this case, no further job commands need to be given to the robot in order to complete
this job.
The Adept Enterprise Manager manages jobs associated with either a PICKUP or a DROPOFF
goal. Robot tasks that are associated with the goals will be executed at the proper times,
though they are not managed as separate jobs in the queue.
Though not managed by the queue, it is recommended and assumed that the robot task
"pause" will be used to pause the robot at its destination. The associated "pauseTaskCancel"
task should be used to signal dismissal once the robot has been loaded or unloaded. This can
be triggered either by a manually-activated button, or by an automated system.
Adept SmartFleet EX User’s Guide, Rev. A
Page 37 of 54