Allen-Bradley Kinetix 6200 User Manual page 208

Chapter 8 Troubleshoot the Kinetix 6200 and Kinetix 6500 Drive System
Table 90 - NODE FLT Fault Codes (continued)
Four-character Display Message Logix Designer Fault Message
NODE FLT 03...HARDWARE nn Hardware Fault
NODE FLT 04...DATA FORMAT ERROR
Data Format Error
(Kinetix 6200 drives only)
NODE FLT 06...LOST CTRL CONN
Lost Controller Connection
(Kinetix 6500 drives only)
NODE FLT 08...LOGIC WATCHDOG
Custom Logic Update Timeout
(Kinetix 6500 drives only)
NODE FLT 09...IP ADDRESS
Duplicate IP Address
(Kinetix 6500 drives only)
NODE FLT 128...DRAM TEST DRAM Test Fault
NODE FLT 129...FPGA CONFIG FPGA Configuration Fault
NODE FLT 133...SERCOS ADDRESS
Duplicate Sercos Node Address
(Kinetix 6200 drives only)
NODE FLT 139...SERCOS RING
Sercos Ring Fault
(Kinetix 6200 drives only)
Table 91 - NODE ALARM Fault Codes
Four-character Display Message Logix Designer Fault Message
NODE ALARM 01...CTRL UPDATE Control Connection Update Alarm
NODE ALARM 05...CLOCK SYNC Clock Jitter Alarm
NODE ALARM 128...NODE SWITCH No Quick View message
208
Problem or Symptom
The drive has an internal hardware problem. The nn sub-code is defined as
follows:
01: Invalid slot ID.
02: Cannot read slot ID.
03: Nonvolatile write to memory failed.
04: Nonvolatile memory read failed.
A data format error was discovered in the
controller-to-drive message.
communication with the controller have
been lost
The watchdog circuit monitoring custom
logic operation detected a problem.
This drive and another EtherNet device on
the same subnet have identical IP
addresses.
A power-up test of the DRAM indicated a
memory problem.
The FPGA could not be configured properly.
This axis and one or more other axes have identical sercos addresses.
The sercos ring is not active after being
active and operational.
Problem or Symptom
The Control Update Alarm bit is used to
indicate that updates from the controller
have been late
Sync Variance has exceeded the Sync
Threshold while the device is running in
Sync mode.
The node address switches have been
altered because they were first read after
powerup.
Rockwell Automation Publication 2094-UM002G-EN-P - August 2016
Potential Cause Possible Resolution
• Recycle control power or reset the
drive.
• Replace power module or power
Faulty power rail or power
rail if problem persists
module.
• Recycle control power or reset the
drive.
Faulty memory component.
• Replace control module if problem
persists.
• Recycle control power or reset the
drive.
Faulty memory component.
• Replace control module if problem
persists.
• Faulty Ethernet cable.
• Ethernet cable Check Ethernet connection.
disconnected.
Controller lost power. Check controller operation.
• Recycle control power or reset the
drive.
Faulty control module.
• Replace control module if problem
persists.
Select a node address not already in
Incorrect node switch setting.
use on the network.
• Recycle control power or reset the
drive.
Faulty memory component.
• Replace Control module if
problem persists.
Faulty component. Replace module.
Check Node Switch configuration of
all axes on the sercos ring and adjust
for no overlap of addresses.
Loose or damaged sercos
Check that fiber-optic cable is present
cable. and connected properly.
Potential Cause Possible Resolution
• Remove unnecessary network
devices from the motion network.
• Change the network topology so
Excessive network traffic. that fewer devices share common
paths.
• Use faster/higher performance
network equipment.
• Segregate signal wiring from
power wiring.
Noisy environment.
• Use shielded cables.
• Add snubbers to power devices.
• Switched to grandmaster
clock of significantly • Drive auto-corrects upon time
different frequency. synchronization.
• Lost connection to • Restore network connections.
grandmaster clock.
Node Switches adjusted after Return node switches to power-up
powerup. setting.