Rockwell Automation iTRAK, User Manual

Page: 105 / 124

Rockwell Automation Publication 2198T-UM002C-EN-P - March 2019 105
Troubleshooting Chapter 6
10 0
Headway Fault. Two movers cmd or actual pos
is under headway setting. Increase amt
This error indicates that at the end of the next Coarse Update Period
two movers can crash into each other. The following are possible
causes.
• Two motion commands are not synchronized to run in the same
Coarse Update Period.
• A mover was applied over another mover.
• Tasks have overlapped and cannot finish in allocated time.
The iTRAK_Control.Status.SectionNumberFaulted tag contains the
motor module that is reporting this fault.
If the iTRAK_Control.Status.SectionFaultData tag =
0, then the headway fault happened between mover 0 and the mover
with the largest mover number.
7, then the neighbor movers did not trigger the fault.
Check for task overlaps. Verify proper motion instruction execution
order.
11 0 or 7
Displayed Text varies according to the value of
iTRAK_Control.Status.SectionNumberFaulted:
Value 0:
Wrong Number of movers reported. A mover
has been lost on the system or the wrong
number specified in the active axis tag. Check
magnets or re-number with HMI tag.
Value 7:
iTRAK could not find all movers at their last
reported positions. The movers have been
automatically renumbered.
This error indicates the following.
• The number of movers exceeds the maximum number that is
specified in the iTRAK_Control.Data.ActiveMovers tag.
• A mover was lost in the middle of the track.
• Movers have been moved when the gateway is off.
If the iTRAK_Control.Status.SectionFaultData tag = 0, then the
number of movers that are specified in the Logix Designer application
doesn't match the number of movers actually found.
To reset this fault, complete these steps.
1. Correct the value in the iTRAK_Control.Data.ActiveMovers tag.
2. Renumber the movers by latching
iTRAK_Control.Cmd.RenumberMovers.
3. Reset the fault by latching iTRAK_Control.Cmd.FaultReset
If the iTRAK_Control.Status.SectionFaultData tag = 7, then upon
start-up, the movers were not found in the same positions as they
were when the track was shut down. The movers on the track have
been automatically renumbered.
Check position magnets. Check specified movers and licenses. Check
track for debris.
12
0
Fault_InternalComm - Data could not be
written to sections.
This error indicates that a motor module is not responding to
commands. The following are possible causes.
• Low-voltage power loss
• Communication cables are not connected
• Communication cables are loose
• Electrical noise
The iTRAK_Control.Status.SectionNumberFaulted tag contains the
motor module that is reporting this fault.
If the iTRAK_Control.Status.SectionFaultData tag =
0, then writing data to a motor module failed.
1, then the motor module received too many communication errors.
2, then the force command was not received or the neighborhood
command was not received.
This fault can cause the gateway to lose movers; therefore, the movers
must be renumbered before clearing this fault.
Check power connections. Cycle power.
2
ERR_OVERCURRENT_FAULT: Section has an
overcurrent fault. Reset system.
This error indicates that the current in the motor module has risen to
an unacceptable level.
The iTRAK_Control.Status.SectionNumberFaulted tag contains the
motor module that is reporting this fault.
The iTRAK_Control.Status.SectionDeviceFaulted tag is the PWM board
number.
The iTRAK_Control.Status.SectionFaultData tag is the bad coil.
Verify that the sizing of system is correct. Reduce the acceleration and
deceleration.
Table 23 - iTRAK System Error Codes (Continued)
iTRAK_Control.Status.
GatewayFaultCode iTRAK_Control.Status.
SectionFaultCode Displayed Text Description and Solution