Hello everyone,
In our factory automations, we use Siemens or LS (XG5000) PLCs. On the HMI, we usually have a button used to home/reference the robot before pressing Start on the cycle.
The logic works like this: when the ‘Home’ button is pressed on the HMI, the PLC sends a signal (System Input) that triggers an interrupt in the robot. This routine should move the PP (Program Pointer) to Main, turn Motors On, and execute the homing trajectory.
However, from time to time, we face an issue: the robot simply rejects the ‘PP to Main’ or ‘Motors On’ commands coming from the PLC. I have tried monitoring the signals to understand what is blocking the action, but with no success.
An important detail for troubleshooting: if we switch the robot to Manual mode, turn on the motors using the FlexPendant, and then switch back to Auto mode, the HMI button executes its function perfectly again.
Has anyone experienced this or knows how to resolve it? Could it be a prerequisite safety condition that is not being met, a missing specific pulse in the System Input, or is it a system bug?
Thanks in advance for your help!
One very important thing for the PP to Main system input to work and not be rejected is that the program must not be executing. I see that there is not a system input to stop program execution. Do you truly have an interrupt routine triggered by the system input PP to Main? This would be unnecessary and problematic. The system input will do as you need on its own, no interrupt is required. Add a system input to stop the program execution.
If motors on is rejected, then perhaps first check to see if the run chain is OK first and that the motors are not actually ON already and that motors off is not being sent at the same time.
Thank you for the reply!
I am sure the robot is stopped when I try to reference it because it drops to a ‘Motors Off’ state. The homing routine is quite extensive, which is why I didn’t explain it in detail before. Regarding the interrupt, the ‘PP to Main’ is a signal I configured as a System Input mapped to an action, as shown in my previous image.
In the attached image, you can see the event log showing the ‘20140: Motors On rejected’ and ‘20409: PP to Main rejected’ warnings. From what I checked, the safety run chain was OK, and there was no apparent reason for it to reject the commands. It only worked again after switching to Manual mode, turning the motors on, and returning to Auto.
Do you have any other tips on what might be causing this lock-up or how to bypass it?
What system outputs do you have in use?
I have these System Outputs
We should know the generation of the controller and which version of Robotware is installed. Nevertheless, I don’t see a system output for Run chain OK. You should use it and incorporate it into the PLC program logic. It would be useful also to use execution error, motors off state and system input busy. To sum things up, there should be handshakes in which a system input is sent, and then wait for the output to acknowledge the desired action or state. Then, the PLC can give the next system input as required or appropriate.
This happens on any IRC5 controller, whether it is running RobotWare 5 or 6.
Just to clarify: the error actually happens even after the robot has been completely stopped for a few minutes. Given this condition, do you think the root cause could still be what you suggested (the lack of handshakes and unmonitored system states)?
I will evaluate the situation with my team and see how we can improve our logic based on your tips. Thank you very much!
Definitely. If the robot is already in the desired state, there should be no input to go into the state in which it already is in, for example. It is good practice to assume nothing, and use more of the inputs and outputs for the PLC to issue valid commands.