Banner Sure Cross Performance DX80 Instruction Manual page 77

Wireless i/o networks
Hide thumbs Also See for Sure Cross Performance DX80:
Table of Contents

Advertisement

LED 1
LED 2
Flashing red
Flashing red
Not blinking amber
No LED 1
No LED 2
All manuals and user guides at all-guides.com
Definition/Solution
Gateway, DX85: Modbus communication error
For a Gateway system, a Modbus communications error indicates a bad
transmission or checksum error between the host and the Gateway device. For a
GatewayPro system, a Modbus communications error indicates a communications
problem internal to the GatewayPro. For a Gateway and Ethernet Bridge system, a
Modbus communication error indicates a communication problem between the
Gateway and the Ethernet Bridge.
Solutions:
1. The default communications settings for the RS485 port are: 1 start bit, 8
data bits, no parity, 1 stop bit, and 19.2k baud. The DX80 Gateway uses
Modbus RTU protocol for all communications. Supported Modbus function
codes are 3, 6, and 16.
2. Verify the DX80 model supports RS485 serial communications.
3. RS485 termination or biasing is not supplied on the Gateway and should
be provided externally to the DX80. (Termination is not required by the
Gateway, proper biasing of the serial lines is required.)
4. Bad connection or bad cable.
Node: No radio communication
There are two settings on every Node device used to synchronize to the Gateway
device:
The Node must be bound to the Gateway.
Each Node ID within that network must be set to a unique number.
Solutions:
1. If the Gateway and Node are less than two meters apart, device
communication may fail (radios may saturate). If the Gateway is less
than two meters from another Gateway, send and receive transmissions
between all devices the Gateways communicate with fails.
2. The Gateway and Node may be too far apart to achieve synchronization –
consult the factory for options.
3. Use a qualified antenna on both the Gateway and Node devices.
4. After any system parameter change, cycle the power to re-synchronize all
devices.
5. When a Node loses synchronization, it is programmed to attempt re-
synchronization for five seconds, then sleep for fifteen seconds.
Synchronizing may require up to twenty seconds.
6. Re-cycle power on the Gateway and Node devices.
GatewayPro: No Modbus communication
Solution:
1. The GatewayPro's LED 2 should always be blinking amber to indicate
Modbus communication. If the LED 2 does not blink amber, verify the
baud rates, slave IDs, parity, and stop bits are set correctly.
2. Check the cables connecting the GatewayPro to the host device.
All DX80 devices display "POWER" on the LCD for the first five to ten seconds
after applying power. A DX80 Gateway always has a green LED 1 on when power
is connected. DX80 Node devices flash a red LED 2 every three seconds or a
green LED 1 every second depending on the RF Link status.
If no LEDs are lighting up:
1. Put battery powered devices into power-down mode by pressing and
holding button 1 for three to five seconds. To return from power-down
mode, press and hold button 1 for three to five seconds.
2. Recheck the power connections and power requirements. Battery-
powered devices require 3.6–5.5V dc. Non-battery powered devices
require 10–30V dc.
3. After replacing the battery, allow up to sixty seconds for the device to
power up.
4. The GatewayPro cannot be attached to another Modbus master device or
a Modbus slave ID 1 via RS-485. Special configuration using the Web
page configuration tool allows the GatewayPro to become a slave unit
when necessary.
www.bannerengineering.com - Tel: 763.544.3164
®
Sure Cross
Performance DX80 Wireless I/O Networks
77

Advertisement

Table of Contents
loading

Table of Contents