Local Registers updated from Modbus and Ethernet/IP transactions are restricted to a16-bit data value to follow standard
Modbus Holding Register definition.
The Local Registers defined in Action Rules must all be within the same register group. For example, an Action Rule cannot
have inputs from an integer group with the result register defined as a floating point register. To move between integers and
floats, use the Register Copy Rule.
Registers
Description
12001-12845, 17001-19000
32-bit unsigned integer-based registers
12846-12850
Special function registers (can be reset registers)
12851-12900, 19001-20000
Non-volatile register with limited capability for permanent data storage
13001-17000
32-bit IEEE 754 floating point registers. Floating point values require two Local Registers to store a value.
Floating point Local Registers are referenced on the odd numbered register addresses: 13001, 13003, and
13005. When using Action Rules/Read Rules, always reference the odd numbered register addresses.
Local Registers 12001–12845, and 17001–19000
(Internal Processor Memory, 32-bit, Unsigned)—The Local Registers are
the main global pool of registers. Local Registers are used as basic storage registers and as the common data exchange
mechanism. External Modbus device registers can be read into the Local Registers or written from the Local Registers. The
DXMR90-4K, as a Modbus master device or a Modbus slave device, exchanges data using the Local Registers. Modbus
over Ethernet (Modbus/TCP) uses the Local Registers as the accessible register data.
Local Registers 12846–12850
(Reset, Unsigned)—These Local registers are reserved for use as Reset registers. A time
interval can be specified in the configuration software for the DXM to reset. If the data in the register does not change within
the user-specified time interval, the DXM resets.
Local Registers 12851–12900 and 19001–20000
(Data Flash, Non-volatile, 32-bit, Unsigned)—The top 50 Local Registers
are special non-volatile registers. The registers can store constants or calibration type data that must be maintained when
power is turned off. This register data is stored in a data flash component that has a limited write capability of 100,000 cycles,
so these registers should not be used as common memory registers that change frequently.
Local Registers 13001–17000
—These Local Registers are paired together to store a 32-bit IEEE floating point format
number in big endian format. Registers 12001 [31:16], 12002 [15:0] store the first floating point value; registers 12003, 12004
store the second floating point number. There are a total of 2000 floating point values; they are addressed as two 16-bit
pieces to accommodate the Modbus protocol. Use these registers when reading/writing external devices that require Modbus
registers in floating point format. Since Modbus transactions are 16-bits, the protocol requires two registers to form a 32-bit
floating point number.
Virtual Registers
—The DXMR90-4K has a small pool of virtual registers that show internal variables of the main processor.
Some register values will be dependent upon the configuration settings of the DXMR90-4K. Do not use Read Rules to move
Virtual Local Registers data into Local Registers. Use the Action Rule > Register Copy function to move Virtual Local
Registers into Local Registers space (12001–12850).
Table 5: Modbus registers for virtual registers
Registers
Definition
22001
GPS latitude direction (N, S, E, W)
GPS Coordinate Data if the DXM is configured to read an external GPS unit.
22002
GPS latitude
22003
GPS longitude direction (N, S, E, W)
22004
GPS longitude
22015–22016
Reboot cause (Restart Codes above)
Reboot Type
22017–22018
Watchdog reset count
Counter to track how many resets have been caused by the Watchdog
22025–22026
Http Push SSL Acquires
Statistical counts of connections, disconnections and forced disconnects when
the DXMR90-4K creates a connection using SSL/TLS (Encrypted connections)
22027–22028
Http Push SSL Releases
22029–22030
Http Push SSL Forced Releases
22031–22032
Http Push Attempts
Statistical counts of connections, disconnections and forced disconnects when
the DXM controller creates a connection using HTTP non-encrypted
22033–22034
Http Push Successes
22035–22036
Http Push Failures
DXMR90-4K IO-Link Master
www.bannerengineering.com - Tel: + 1 888 373 6767
15
