With the new Siemens and Nav architecture, if you have mapped an interlock (for example) to the axis safety block, when that interlock condition is triggered, the axis goes to Not Rdy state.
If you run a cue that contains a custom move of that axis, that cue will keep waiting until it times out, instead of skipping it like axis disable.
Therefore requesting that the cue takes into consideration of the axis state, only when it's out of estop and move ready, it waits for it to move. If this condition is not met, the cue skip this axis move, similar to when the axis is disabled (rule or command).
Please sign in to leave a comment.