
5.8 Entering Binding Mode
Under the ISM Radio menu, use the down arrow button to highlight the Binding menu. Click ENTER.
The ISM Radio menu is slightly different for the two different types of internal radio. The ISM Type displays 'MultiHop'
when the MultiHop radio board is installed and 'DX' when the DX80 star architecture radio board is installed.
Use the up/down arrows to enter the device number to bind to. When binding to devices with rotary dials, the device
number has no effect. To bind to devices without rotary dials, the device number is saved as the device Modbus slave ID in
the MultiHop network or the Node number in a DX80 network.
After entering binding mode on the DXM Controller, put the end device into binding mode to execute the binding process.
Most end devices enter binding by triple-clicking button 2 on the device. For specific instructions on entering binding for a
specific device, refer to the individual datasheet for that device.
To bind more devices, click the back button, change the device number (if needed), then enter binding again.
5.8 Conducting a Site Survey
Although the MultiHop and DX80 devices are architecturally different, the site survey process is similar when conducted
from the DXM LCD menu. From the ISM Radio menu, use the down arrow to highlight the Site Survey menu. Click
ENTER.
Use the Up or Down arrows to select the Node number (DX80 network) or Modbus Slave ID (MultiHop network). Click
ENTER to run the site survey with that Node or slave.
For a DX80 network, the Gateway controls the site survey and the results display on the LCD. Running Site Survey on a
DX80 network does not affect the throughput of the DX80 network.
For a MulitHop network, the master device passes the site survey request to the intended Modbus slave device. The Site
Survey runs and the results display on the LCD. Running Site Survey on a MultiHop network stops all network traffic to
that device.
5.9 Setting Up EtherNet/IP
™
Use the DXM Configuration Tool to configure the DXM Controller to run the EtherNet/IP
™
4
protocol.
5.9 Configuring the Host PLC
On the host PLC, install the DXM Controller using an EDS file or by using the following parameters:
•
Assembly1: Originator to Target = Instance 112, 456 bytes (228 words)
•
Assembly2: Target to Originator = Instance 100, 456 bytes (228 words)
The Originator is the host PLC system, and the Target is the DXM Controller. The host system sees the DXM Controller as a
generic device with the product name of Banner DXM (ProdType: 43 - Generic Device, ProdName: Banner DXM).
5.9 Configuring the DXM Controller
Use the DXM Configuration Tool to define each local register to be Originator -> Target or as a Target -> Originator.
•
Define a DXM local register as Originator -> Target when the host PLC (Originator) will send data to the DXM
Controller local register (Target).
•
Define a DXM local register as Target -> Originator when that register data will be sent from the DXM Controller
(Target) to the host PLC (Originator).
Data from an EIP controller in assembly instance 112 is data destined for the DXM Controller local registers. The first two
bytes of the assembly instance are stored in the first local register defined as an Originator -> Target register. The next
two bytes of the assembly instance are stored in the next local register defined as an Originator -> Target register. For
example, if DXM local registers 5, 12, 13, and 15 are configured as Originator -> Target, the first eight bytes (four
words) of data from the assembly instance are stored into these registers in order (5, 12, 13, and 15). The system ignores
the rest of the bytes in the assembly instance.
Data from the DXM Controller local registers is sent to the EIP controller using assembly instance 100. Each local register
in the DXM Controller defined as Target -> Originator is collected in numerical order and placed into the data buffer
destined for assembly instance 100. DXM local registers are capable of 32-bits, but only the lower 2-bytes for each local
register are transferred. For example, if DXM registers 1, 10, 20, and 21 are defined as Target -> Originator registers,
the assembly instance 100 will have the first eight bytes of data coming from the DXM local registers 1, 10, 20, and 21.
The rest of the data is in assembly instance 100 is zero.
4
EttherNet/IP is a trademark of Rockwell Automation.
DXM100 Controller Instruction Manual
34
www.bannerengineering.com - Tel: 763.544.3164