Rockwell Automation Allen-Bradley ControlNet 1734-ACNR User Manual page 128

8-8 Troubleshoot Your ControlNet Communication Modules
If The OK With This
Indicator Is Module Status
Display
Flashing red BOOT
ROM
UPDT
SNGL KPR!
Steady green OK
INIT
BW >MAX
CMPT
DSNP
PwDS
PwQg
PwQS
PwNS
Qfng
QS
SW
ERR
Flashing green CNFG ERR
NET
ERR
OK
Publication CNET-UM001C-EN-P - November 2005
It Means
Module has invalid firmware.
Flash update is in progress.
Module detected that it has been connected to
a Cnet 1.0 or 1.25 (single-keeper) network.
Normal operation
Module is initializing.
Module is receiving too much network traffic
and connections are timing out. The network
bandwidth has been exceeded.
Secondary CNB is compatible with its partner.
Secondary CNB is disqualified with no partner.
CNB is primary with a disqualified secondary
partner.
CNB is primary with a qualifying secondary
partner.
CNB is primary with a qualified secondary
partner.
CNB is primary with no secondary partner.
Secondary CNB is qualifying.
Secondary CNB is qualified.
Node address switch changed after power-up.
ControlNet configuration error.
Network cabling error or no other active nodes
on network.
Normal operation
Take This Action
Update module firmware with ControlFlash
Update Utility.
None required.
Update the firmware of module at node address
01 and reschedule the network.
None required. In this case, at least one
connection has been made to or through the
module.
None required.
None required (temporary condition).
If this happens frequently, add another module
and split the traffic between them.
None required.
Check corresponding slot of primary chassis for
type and revision of module.
Check the type and revision of the module.
Redundant system status. No action required.
Check corresponding slot of secondary chassis
for correct module.
Redundant system status. No action required.
None required, but we recommend that you
either return switches to their original settings
or replace the module, since this could indicate
a latent hardware problem.
Recheck configuration.
Re-check your network cabling and make sure
another node on the network is active (on line).
None required. In this case, no connections
have been made to or through the module.