Module Faults: 16#fd00 - 16#fdff

The module faults: 16#fd00 - 16#fdff.
Code
String
Explanation and Possible Causes/Solutions
16#fd03
Connection Request Error: Required Connection missing
The controller is attempting to set up a connection with the module and has received an error - this module requires a particular set of connections and connection types, and one of those connection types is missing.
16#fd04
Connection Request Error: No CST Master Detected
The controller is attempting to set up a connection with the module and has received an error - this module requires a CST master in the chassis.
  • Configure a module (typically a controller) in this chassis to be the CST master.
  • Contact Rockwell Automation technical support at Rockwellautomation.com.
16#fd05
Connection Request Error: No Axis or Group Assigned.
The controller is attempting to set up a connection with the module and has received an error - this module requires an axis or group table assigned.
16#fd06
Transition Fault
The controller command to transition the SERCOS ring to a new phase returned an error from the module. Check for duplicate Drive Nodes.
16#fd07
Incorrect SERCOS Data Rate
An attempt to configure the SERCOS ring failed. The baud rate for all devices must be the same and supported by the drives and the SERCOS module.
16#fd08
SERCOS Comm Fault
Mainly two sets of faults may cause a Comm. Fault - Physical and interface faults.
A possible source of physical faults is:
  • Broken ring
  • Loose connector
  • Fiber optics not clean
  • Electrical noise due to improper drive grounding
  • Too many nodes on the ring
Interface errors are encountered when you are configuring third party drives.
A possible source of interface errors is:
  • No SERCOS MST (Protocol Error)
  • Missed AT (drive did not send data when expected)
  • SERCOS timing error in phase 3
  • Error in drive data returned to SERCOS module
16#fd09
Node Initialization Fault
An attempt by the controller to configure the node for cyclic operation returned an error.
16#fd0a
Axis Attribute Error
A bad response was received from a motion module.
16#fd0c
Error Different Grandmaster Fault
The end device has a different grandmaster than the controller.
16#fd1f
Bad Safety Protocol Format
An error occurred adding the safety network segment to a route.
16#fd20
No Safety Task
No safety task appears to be running.
16#fd22
Chassis Size Mismatch
Verify the number of physical expansion I/O modules configured for the controller and then update the number of modules selected from the Expansion I/O list on the General page in the Controller Properties dialog.
16#fd23
Chassis Size Exceeded
To verify the number of physical expansion I/O the controller supports, open the Controller Properties dialog and expand the Expansion I/O list on the General page.
Configure the number of physical expansion I/O modules to match the selection in the Expansion I/O list.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.