
User Interface—A simple user interface consists of an LCD screen and four LED indicators. Use the LCD to access system
status and setup, view user selectable events or data, and to bind and perform site surveys for Sure Cross radios.
Configure the user programmable LEDs to indicate the status of the DXM Controller, processes, or equipment.
User programmable LCD
Bind Sure Cross Radios
Site Survey
View Sensor Information
System Status
User Defined LED indicators
1.2 DXM Automation Protocols
The DXM Controller supports the following automation protocols.
Modbus RTU. The DXM Controller manages two separate physical ports running the Modbus RTU protocol. The DXM
Controller is the Modbus Master when operating the Modbus master RTU port. The DXM Controller uses the master Modbus
RTU bus to communicate with locally connected Modbus devices or uses the Banner wireless radio to communicate with
remote Modbus devices. The other Modbus RTU port is used by a host system to access the DXM Controller as a slave
device. The slave Modbus RTU port allows access all the internal registers concurrently with the master RTU port. By
default, the Modbus RTU ports are active. Configure the port parameters using the DXM Configuration Tool.
Modbus TCP/IP. A host system acting as a Modbus client can access the DXM Controller using the Modbus TCP/IP
protocol over Ethernet. Standard Modbus port 502 is used by the DXM Controller for all Modbus TCP/IP requests. All
internal registers are available to the host system concurrently with Modbus RTU. By default, Modbus TCP/IP is active.
EtherNet/IP
™
. The Ethernet port is actively running EtherNet/IP. From the factory the DXM Controller is configured to
read and write registers on DX80 wireless devices 1 through 16. Custom configurations can be set using the DXM
Configuration Tool. By default, EtherNet/IP is active.
1.3 DXM Modbus Overview
The DXM Controller uses internal 32-bit registers to store information. The processor's internal Local Registers serve as the
main global pool of registers and are used as the common data exchange mechanism. External Modbus device registers
can be read into the Local Registers or written from the local data registers.
The DXM Controller, as a Modbus master device or slave device, exchanges data using the Local Registers. Modbus over
Ethernet (Modbus/TCP) uses the Local Registers as the accessible register data.
Using Action, Read/Write, and Threshold Rules allows you to manipulate the processor's Local Registers. The ScriptBasic
programming capabilities extends the use of Local Registers with variables to create a flexible programming solution for
more complex applications.
The processor's Local Registers are divided into three different types: integer, floating point, and non-volatile. When using
Local Registers internally, the user can store 32-bit numbers. Using Local Registers with external Modbus devices follows
the Modbus standard of a 16-bit holding register. Local Registers are accessible as Modbus ID 199.
Accessing the I/O Base and the LCD follows the same communication as an external Modbus device. Each device has an ID
number to uniquely identify itself. The I/O base is Modbus ID 200 and the LCD is Modbus ID 201.
DXM100-Bx Wireless Controller Instruction Manual
6
www.bannerengineering.com - Tel: 763.544.3164