![background image](http://html.mh-extra.com/html/omron/ld-60/ld-60_user-manual_742958070.webp)
70
LD Platform Peripherals Guide
13732-000 Rev J
5.5 MobilePlanner Configuration
5.5 MobilePlanner Configuration
A number of configuration tasks need to be performed after the hardware is installed. All of
these tasks are performed using the MobilePlanner software.
Host Software
The host software component needs to have been loaded onto the EM for a fleet installation or
onto the AMR for a single-AMR installation. It is part of the FLOW Core, which includes sup-
port for the call/door box. The FLOW Core can be uploaded using the SetNetGo OS 5.0.0 or
later. This needs to happen before any of the steps in the next Configuration section are attemp-
ted. See SetNetGo - Managing Software Packages on page 26.
Factory-installed firmware is maintained by the call/door box host software, if needed. No user
action is required.
Overview of Tasks
l
Enter the IP address of each Ethernet device.
l
Assign a goal to each call button.
l
Enable the Mobile Call-Button/GPIO software.
l
For call buttons:
o
Configure the parameter BeepSeconds to set how long the node beeps when the
robot arrives. This parameter applies to all call buttons.
o
For a single-AMR installation, enable the Queuing Manager.
l
For door boxes:
o
Configure the external digital output used to signal the door actuator.
NOTE:
Door boxes can be used as two generic digital inputs and
two generic digital outputs, rather than used to trigger a door actu-
ator.
o
Add the door-related AMR control features to the map.
l
Configure any external I/O that you have connected.
Configuring Call/Door Boxes
Each call/door box needs to have its IP address entered in the MobilePlanner software. For call
buttons, you also need to enter a goal and the goal's priority. Fields that are auto-populated or
do not apply will be grayed out, and you will not be able to change them.