Hello, I am experiencing a problem with my Kinteix 5500 suddenly not configuring. The Ethernet module is displaying an error message: "CIP Motion Drives: Error Code 16#fd05 [Connection Request Error: No Axis or Group Assigned]." Despite this machine running smoothly for months with an axis assigned to it, the issue persists. I have followed suggestions from the Rockwell knowledge base to troubleshoot, including creating a new Ethernet module, remaking the axis, and re-assigning the axis. However, the problem still persists. Any ideas on how to resolve this issue? The controller firmware version is 30.04.
What information is displayed under the axis tag in Linx? Can the drive be viewed in Linx?
It appears that when you attempt to "inhibit" a drive, the module will display the message: "Assigned axis inhibited, connection cannot be established."
Have there been any updates to the programmable logic controller (PLC) program or drive system? Was a new power supply, drive, or servo installed? Does the system incorporate a brake mechanism? I recently handled a similar issue where we encountered a faulty servo, cable, and drive. Despite replacing the servo and cable, the drive continued to encounter errors. After replacing the drive, the same error occurred until we re-established ownership of the drive unit. I hope this information proves helpful. - James
When you suppress the impulse, it triggers the error within that module.
Discover the potential culprit on this engaging Reddit thread discussing inhibited modules and motion axes in PLC systems: https://www.reddit.com/r/PLC/comments/x1wt4e/ive_inhibited_modules_but_how_are_motion_axes/
Hi there! It seems like you've already tried many of the standard troubleshooting methods. One idea that might potentially work is checking the controller's task configuration. I ran into a similar issue once and it turned out the controller's task, where the motion group was assigned, had an insufficient cycle time, causing the controller to be overloaded. Increasing the cycle time in the task properties helped resolve it. Also, if you're noticing this issue amid an operation, check if there's an e-stop or fault condition in effect. Those could also trigger such messages. Hope this helps!
Hey there, it sounds like you've tried a good number of troubleshooting steps already. I remember dealing with a similar issue a while back, and for me, it was a firmware compatibility issue. You mentioned your controller firmware version is 30.04. It's wise to check if there have been newer versions out since then. Also, another thing that comes to mind, is to verify whether any changes were made to the PLC program recently which could affect the assignment configuration. Lastly, ensure that the CIP connection to the drive is correctly configured. You might want to try disabling, then re-enabling the CIP connection as well. Good luck!
Hello. Your problem sounds similar to an issue I faced once with my Kinteix 5500. Updating the firmware version worked for me. Even though firmware 30.04 is relatively current, you never know. There could be some bug fixes or improvements in newer versions that could solve the issue. Also, check the cabling and the physical condition of the Ethernet module. Sometimes an intermittent disconnect can trigger such faults. Or, there might be a chance of an IP conflict in the network. If nothing else works, it might be worth it to contact Rockwell's technical support for further guidance.
It sounds frustrating to deal with that error message after everything was running so well! Since you've already tried the common troubleshooting steps, I'd recommend double-checking a few things: ensure that all your connections are solid and there are no loose cables, and try power cycling the entire system. Sometimes a hard reset can clear lingering issues. Additionally, look into whether there have been any recent firmware changes or updates that might impact compatibility; downgrading to a previous version, if possible, could also help. If none of that works, reaching out to Rockwell support directly might be your best bet—they might have insights into unique issues associated with the 30.04 version. Good luck!
Have you checked to see if there have been any recent firmware updates or changes to your system configuration that might have inadvertently affected how your axes are recognized? Sometimes, reloading the project or even a power cycle of the system can help reset things. If that doesn’t work, consider checking the Ethernet cable and connections as physical issues can sometimes cause these error codes. If the problem persists, reaching out to Rockwell support for deeper diagnostics may be your best bet; they might have insights on specific version-related quirks with the Kinteix 5500.
It sounds really frustrating that you’re dealing with that error after things were running smoothly for so long! Since you’ve already tried a bunch of troubleshooting steps, have you checked if there’s a configuration change or a mismatch in the device IDs? Sometimes even tiny discrepancies, like a wrong parameter or an incorrectly changed connection type, can throw things off. Additionally, verifying that the firmware on all connected devices is compatible with your controller's version could help. If everything seems correct and the issue persists, contacting Rockwell support might be worthwhile—they may have more targeted insights based on your specific setup!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Error code 16fd05 indicates a "Connection Request Error: No Axis or Group Assigned" in the CIP Motion Drives system.
Answer: Answer: You can troubleshoot this issue by creating a new Ethernet module, remaking the axis, and re-assigning the axis as suggested in the Rockwell knowledge base.
Answer: Answer: The sudden appearance of error code 16fd05 could be due to a configuration issue or a change in settings. It is recommended to follow the troubleshooting steps provided and ensure the correct configuration.
Answer: Answer: Updating the controller firmware version to the latest release, if available, may help resolve compatibility issues or bugs causing error code 16fd05.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.