code, the higher the priority. For more information about how Site Survey data is stored in registers 7 and 8, refer to the Site Survey
section.
The following are Modbus message codes, shown in hex, that may appear on the SureCross devices' I/O 8 Modbus register.
Device Register 8 (Hex)
Message Code
[15:8]
Data Field
[7:0]
Description
00
80
Normal operation. Device message register contents 0x0080 indicates the particular Node is
synchronized to the Gateway. (Decimal value 128.) A value of zero (0) indicates there is no
device present.
01
00-FF
Unknown message. The message was received correctly (correct checksum), but it is not a
recognized command. This type of message is usually caused by devices with poor radio links
or collocated networks that are not uniquely separated by binding codes and Network IDs. This
message does not affect the performance of the network. (Decimal values 256 through 511.)
35
01
Radio Device (polling/heartbeat) Timeout. (Decimal value 13569.) A Node is determined to be
out of the wireless network based on the parameters defined for polling or heartbeat. See the
documentation in the UCT for polling or heartbeat parameters and the timeout operation. When
the least significant bit is on (1), an error condition exists.
• Run site survey to determine the quality of the RF link. If no communications exist between
the Gateway and Node, verify the power at the Node and all antenna connections. The
blocking of RF communications may also be a result of environmental conditions that may
have changed.
• The battery of a battery powered Node may need to be replaced. Although the LCD and
device may appear functional, the battery may not have enough capacity to handle the cur-
rent requirements of RF communications.
36
01
Modbus time-out. A Gateway timeout (time of inactivity on the serial channel) was detected.
(Decimal value 13825.) When the least significant bit is on (1), an error condition exists.
FE
--
Modbus register 8 device messages are disabled. The Modbus register 8 clears or disables
messages using the Gateway’s Modbus register 15. (Decimal values 65024 through 65279.)
Inputs and Outputs
Problem
Solution
Some inputs or outputs are not
working
1. From the Node, access the menu system and use manual scrolling mode within *RUN to freeze
the I/O status on the LCD display for the device in question. Verify that when the input device
changes state or changes value, the LCD mirrors the behavior.
If the Node is in a hazardous location, access the Node's I/O from the Gateway by changing the
Gateway's right rotary dial to the Node number in question. For example, to view the I/O status of
Node 3, move the Gateway's right rotary dial to 3. The Gateway's LCD now scrolls through Node
3's I/O. To freeze the display on a particular I/O point, double-click button 2. The autoscrolling on
the Gateway stops at the *RUN screen. Single-click button 1 to advance through the Node's I/O
points.
2. Verify that the LCD on the output side mirrors the linked input’s behavior. If the input device state
LCD on the origination DX80 and the LCD on the destination DX80 behave the same, there may be
a wiring issue or an interfacing problem. Consult the factory.
3. Nodes will not sample inputs unless they are in sync with a Gateway. Verify your Node is in sync
with its Gateway.
SureCross Wireless I/O Network Manual
90
www.bannerengineering.com - tel: 763-544-3164
rev. I
