4/13/2018 9:36 AM | |
Joined: 4/28/2015 Last visit: 10/9/2023 Posts: 394 Rating: (55)
|
Hello, I do not know any functionality of the technology objects to do that. In this case, you have to write a little program to check error of slave axis and, if an error occurs, to stop master axis with a motion control function. To check each axis on error, you could use bit 1 of status word (see chapter A.2.35 of S7-1500T manual) of the technology object. As motion control function to stop master axis, you could use "MC_Halt". If you send "MC_Halt" to slave axis, the synchronous operation will be cut off (See chapter 10.13.2 in S7-1500 manual or chapter 10.16.2 of S7-1500T manual!). |
This contribution was helpful to2 thankful Users |
4/13/2018 11:06 AM | |
Joined: 9/12/2016 Last visit: 11/6/2023 Posts: 45 Rating: (1) |
My dear friend, The program I wrote here will stop other axes with the HALT command if an error occurs on the SLAVE axis. But when the SLAVE jumps to the wrong axis and stops the MASTER axis by the error of the SLAVE axis, there is an axis shift of about 5-10 centimeters in between. This is breaking my mechanical system. If summarization is needed, I can not get a rigid posture with the HALT command. I've tried everything you said. But I could not get healthy results. If the SLAVE axis is stopped due to any error, unfortunately MASTER is not in the same position. We need to find another solution. My problem is going on and it hurts me. Respect and love.
|
4/16/2018 7:09 AM | |
Joined: 4/28/2015 Last visit: 10/9/2023 Posts: 394 Rating: (55)
|
Hello, in what Organization block (OB) do you detect the slave error and set up the stop command of the master axis. Is it fast enough - all the time? If it is not fast enough to detect all errors, maybe it could be better to use Synchronous-OB with fast time rate or OB "MC_PreServo" to detect an error of the slave and stop master before calculating the next set value of axis master in OB "MC_Servo". For more information, please have al look to the manual (chapter 3.2.12.1 and 3.2.12.3) |
This contribution was helpful to1 thankful Users |
Follow us on