Greetings, I am currently utilizing an Ethernet-controlled Kinetix 5100 in Studio 5000 with the help of Add-On Instructions. At the moment, I am testing a program that involves toggling bits to initiate motor movement. I have noticed that the On and Off functions are working properly, and I am able to use the Jog feature as well. However, I encounter an error when attempting to use the Stop Add-on instruction, forcing me to stop the Jog using the Off Add-on instruction instead. Subsequently, I am unable to resume jogging as there is now an error. I am employing a One Shot to initiate the jog. The error code I am receiving on the Stop and Jog blocks is 127, indicating that the previous motion has not been completed. Is it necessary for the jog to be "completed" before the stop function can be successfully executed? I am seeking additional information as I am not very familiar with this topic. Any guidance would be greatly appreciated.
PLCDude1994 recently shared his experience with controlling a Kinetix 5100 via Ethernet in Studio 5000 using Add-On Instructions. Despite successful On and Off functions, he encountered an error with the Stop Add-on when trying to stop the motor after using the Jog function. The error code 127 indicated that the previous motion was not completed. Is it necessary for the jog to be "completed" before using the stop function? One responder suggested that the jog runs indefinitely and pointed out a potential race condition where multiple motion commands may be issued simultaneously. It was advised to double-check the oneshots for duplicates and ensure that none of the motion commands share the same control word.
Thank you for your response. However, I don't believe this is the issue. I have confirmed that this program is only running in one specific location. My testing approach for this motor involves simple logic: an on toggle, an off toggle, a jog toggle, and a stop toggle.
It's important to heed Robertmee's advice and ensure that each control word used for commands is unique to avoid encountering strange issues. Avoid using the same control word for multiple commands.
In response to PLCDude1994, thank you for your input. However, I have confirmed that the program is only running in one specific location. The logic for testing the motor is quite simple - a toggle bit for activation, one for deactivation, another for jogging, and a final one for stopping. It is important to remember that motion instructions require a rising edge, rather than maintained bits. Are you toggling the bits on and off? This could be causing issues with the motor control.
Two months ago, I encountered a similar issue while configuring AOIs. I can't recall the exact root cause, but I can share how I configured my job. In my setup, I used a Jog bit XIC and an ONS to activate the jog AOI. In the following rung, I utilized a Jog bit XIO ONS with an indirect tag for the MAS instruction. As robertmee mentioned, these instructions necessitate an ONS preceding them.
In my experience with Kinetix drives, error 127 does indeed usually mean the previous motion command was not completed. However, since you're able to move onto and off of jogging without issue, the error seems unusual. To clarify one thing: the Stop Add-On instruction is generally used to stop an ongoing motor operation, like Jogging. Therefore, using the Stop instruction while the motor's jogging shouldn't be an issue, theoretically. The problem might be related to your program's sequence or perhaps the way you're handling jogging completion. Try checking if the One Shot is properly allowing a jog command to complete before the Stop instruction is activated. Let us know how it goes!
It sounds like the issue might have to do with a sequencing problem in your code. The error code you're receiving typically indicates that an attempt to execute a new motion command happened while a previous motion command was still in progress. In this case, trying to stop the jog before it was completed seems to be the issue. To mitigate this, you could consider incorporating a status feedback loop from your Kinetix controller into your programming logic. This would allow your logic to check if a motion command has been executed fully before attempting to run a new command, thus avoiding clashes and the error you're encountering. Remember, safety is paramount in any movement, so having checks like these in place is good practice.
Yes, it's typically necessary to ensure the jog operation "completes" before executing the stop instruction, as referencing it prematurely can cause an error. While it might seem counterintuitive, the motor drive may be still processing the jog motion even when you're sending the stop signal. What you might want to consider is implementing more rugged or robust error handling to QoS the signals you're sending. For instance, a delay to wait for the jog to finish could help. Also, if you haven't already, it could be beneficial to take a look at the detailed documentation of the Kinetix 5100. Rockwell Automation has comprehensive whitepapers and FAQs that could give specifics about the unique behaviors and best practices for leveraging this hardware.
It sounds like you're on the right track in understanding the problem. The error code 127 indeed indicates that the previous motion is still in process. Consequently, the Stop Add-on instruction cannot override an in-process Jog. When you mention using a One Shot to initiate the jog, are you making sure that the duration of the One Shot is adequate for the motor to complete its action before receiving the Stop command? If the Stop command is sent too quickly after the Jog command, the motor might still be in the middle of its action, and hence the error. So yes, the jog does need to be "completed" before the stop function can be successfully executed. I'd suggest troubleshooting by increasing the duration of the One Shot or adding a delay before the Stop command, to allow time for the jog action to complete. Keep us updated, and good luck!
It sounds like you’re on the right track with the Kinetix 5100, but that error code suggests that the system is still processing the previous jogging command when you attempt to stop it. Yes, typically, the jog operation needs to be in a state where it can be safely stopped before executing the Stop command; it might be necessary to check if there’s a specific condition in your program that ensures the motor has fully halted before calling the Stop function. You might consider using a state tracking mechanism or a feedback loop to verify if the motor is indeed stopped before initiating another jog. Additionally, reviewing the Add-On Instructions' documentation regarding the expected behaviors could provide more insights into handling these transitions smoothly. Good luck!
It sounds like you're dealing with a classic issue when working with motion control systems. The error code 127 typically means that the controller is programmed to wait for a motion to finish before it can accept a stop command, so it's likely that the jog motion needs to reach a designated state before you can successfully initiate a stop. You might want to incorporate a check to ensure that the jog command has fully completed before executing the stop instruction. Also, consider reviewing the state of your motion commands in logic; sometimes, using a state machine or additional feedback can help you handle transitions more effectively. If you can, try adding some monitoring in your program to capture the status of the motor to better manage the transitions between jog and stop. Good luck!
✅ 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: The error code 127 you are receiving indicates that the previous motion has not been completed before attempting to stop the motor. This error may occur if the jog operation has not finished before issuing a stop command.
Answer: Answer: In the case of Kinetix 5100 in Studio 5000, it is necessary for the jog operation to be completed before the stop function can be successfully executed. Attempting to stop the motor before the previous motion completes can lead to errors, such as the one you are experiencing.
Answer: Answer: To resume jogging after encountering an error with the Stop Add-on instruction, you may need to ensure that the previous motion has been completed before attempting to jog again. Proper sequencing of instructions and ensuring completion of one operation before initiating another can help prevent errors and enable smooth functionality.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.