Driver Module for the SSI Mobile Racking#

This module will integrate an SSI Mobile Racking system into SHARK. It allows aisles to be opened automatically when needed.

Configuration of the Mobile Rack#

The Mobile Rack must support remote control by the NGKP2 protocol.

Enable the interface option as shown.

Check and configure if needed the communication setup. These parameters must also be set in SHARK

The IP address is required

The configuration of the module is done in the SHARK Registry:

The device is created below Devices.MobileRack.

The instance name must be the zone name.

Parameter	Value	Description
IP		IP Address of the Mobile Rack PLC Controller
ReceiverID	101	Receiver ID of the Mobile Rack used by the NGKP2 protocol. Default is 101
SenderID	201	Sender ID of the Mobile Rack used by the NGKP2 protocol. Default is 201
ReceiverPort	2012	IP Port used by the NGKP2 protocol, default is 2012
SenderPort	2011	IP Port used by the NGKP2 protocol, default is 2011
SystemID	1	Is default 1
Destination	101	Used by the NGKP2 protocol, default is 101
Type	MobileRackSSI	Driver name
TelegramLogFolder		Folder where a telegram log file can be stored
TelegramLogLevel	None	Normal/None/Detailed
Instance	GATOR	The instance name depends on which Shark Control should run the module. Set to GATOR.

Configuration for a mobile rack in zone A

A mapping table from the SHARK aisle number to the mobile rack number must be specified. They might be a one-to-one mapping as the example below.

Mapping of SHARK aisle numbers to the numbers used by the mobile rack

The normal way is that the PDA client is controlling the mobile rack. This is enabled by enabling "Shark Control Embedded" in the SHARK Web Server.

Configure Gator to load the drivers to run embedded in the Web Server

Aisles can be opened directly from the SHARK WCS interface, either by Telnet or by opening a SHARK WCS client. Accepted commands:

MOBILERACK:A:OPEN <aisle number>