2.2 Binding the ISM Radio of a Modbus Slave
A DXM100 (for example, model
DXM1x0-S*R2
) contains two boards: a MultiHop ISM radio and an I/O base board. Each
board is a separate Modbus device and requires a unique Modbus ID.
•
The ISM radio is not required to have a Modbus ID because there are no registers to manage, but it generally does
have a Modbus ID assigned to it.
•
The I/O board must have a Modbus ID to access the I/O register data and configuration data.
To bind the DXM100 (as either a repeater or slave radio) to its master radio, follow the MultiHop binding instructions. If the
binding instructions are not included in the master radio datasheet, refer to the MultiHop Quick Start Guide (p/n
).
The ISM radio board's Modbus ID is assigned from the master radio during binding using the master radio's rotary dials or
the DXM Controller's LCD Binding menu. For example, if the master's binding number is 25, the DXM Slave ISM radio's
Modbus ID is set to 25.
By default, the I/O board's Modbus ID is set to 11. To change the Modbus ID, use the I/O board DIP switches. For
applications requiring Modbus IDs outside the range of the DIP switches, write a Modbus ID to a Modbus register on the I/O
Setting the Modbus Slave ID on the I/O Base Board
Use the MultiHop Configuration Software to display and configure a MultiHop radio network. With the DXM100, only the ISM
radio displays on the Network View screen. The Modbus ID of the I/O board is a separate device that is not a part of the radio
network. Although the I/O board does not show up in the Network View, it is accessible when using the Register View
functions.
Sure Cross
®
DXM100-Sx Wireless Modbus Slave
www.bannerengineering.com - Tel: + 1 888 373 6767
9