1. ASYS and FSYS blocks’ HW
OK pins are turned off.
2. If configured as a Modbus
master:
ASYS and FSYS blocks’
Modbus Master Fail pins
are turned on.
Slave and read blocks
associated with the slaves
experiencing the failure
have their read pins frozen
to the last value read.
Slave blocks associated
with the slaves
experiencing the failure
have their BAD COMM
and NO SCAN pins turned
on.
IN SCAN STATUS is set to
NO for all slaves
experiencing the failure.
COMM STATUS is set to
BAD for all slaves
experiencing the failure.
The slaves with the data
link errors have a non-zero
data link error count.
The slaves experiencing
the failure are moved to the
background scan rate.
1. Check baud rate
2. Check connectors
3. Check cable polarity
4. Isolate cabling from electrical
interference
5. If RS-232 to RS-485 converter
is used, check its power,
switch/jumper settings, and
polarity.
6. If configured as a Modbus
master, use the slave status
screens to determine which
slaves are experiencing the
problem. For those slaves
check:
Power
Connections
address
baud rate
parity
number of stop bits
for electrical interference
grounding
termination resistor (if at
end of link)
9. The diagnostic is cleared by
clearing the port’s statistics.