WTC MedWeld 3005, Operator'S Manual

Page: 27 / 206

=UTGU\T# %?fUbfYUg
=UTGU\T# %?`UbQd_bµc7eYTUD)## " !!!
= #" "%1`bY\" "
1XPHULF6WDWXV&RGHV
The numeric display (below the two bi-color indicators) also
provides diagnostic information about the status of the module.
The display flashes at 1-second intervals.
The table below summarizes the meanings of the numeric codes:
Code Description Remedy
Network
Address
Displays 0–63 Normal operation. The numeric display
matches the scanner’s node address
on the DeviceNet network. None.
70 Module failed Duplicate Node Address
check. The node address you selected
is already in use on that channel. Change the module channel address to
another available address.
71 Illegal data in Scan List table (node
number alternately flashes). Re-configure the Scan List table and
remove any illegal data.
72 Slave device stopped communicating
(node number alternately flashes). Inspect the field devices and verify the
connections.
73 Device ID does not match Scan List
table entry (node number alternately
flashes). Enter a matching Scan List device ID.
74 Data overrun on port detected. Modify your configuration and check for
invalid data.
75 No network traffic has been detected. Verify connections.
76 No direct network traffic for module
detected. None. The module hears other network
communication.
77 Data size returned does not match Scan
List’s entry (node number alternately
flashes). Reconfigure your module and change
the addressing.
78 Slave device in Scan List table does
not exist (node number alternately
flashes). Add the device to the network, or delete
the Scan List entry for that device.
79 Module has failed to transmit a
message. Make sure your module is connected to
a valid network. Check for bad cable
connections or disconnected cables.
80 Module is in IDLE mode. None.
81 Module is in FAULT mode. None.
82 Error detected in sequence of
fragmented I/O messages from device
(node number alternately flashes). Check Scan List entry table for slave
device to make sure that input and
output data lengths are correct. Check
slave device configuration.