I was very disapointed when I understood that I cannot stop / abort a sequence execution, e.g. due to Tool Mount Error or similar.
But now in V8 there is the new command “Assertion”, which seems to have a possibilty to “recover and continue”, “abort”, … i.e. exactly what I am looking for.
The docu also states that Assertions are only for Developers, but I would like to use them in my regular sequences… What do I need to do to enable them so I can use them in my sequences? Is trhere a way?
Thank you for the feedback @mbuchberger1967. What you’re trying to accomplish is doable in a very specific way with the IF statement: use an IF command to check IF a condition (eg: tool failed to mount) is true and THEN branch to some error handling sequence, ELSE another sequence containing ‘the rest of what you want to do’. Unfortunately there can’t really be any commands after the IF statement because the execution will come back to the main sequence after branching in either case, and you probably wouldn’t want more stuff there that will always execute for both cases.
I think that’s the only way to accomplish what you want without Farmware or Assertion. We’re discussing internally how to better handle use cases like this (and there have been some feature requests for similar issues as well). We’ll likely either be adding support for one or both of the following:
A) An abort or e-stop command that could escape all execution.
B) Extra dropdown options in the IF statement command that allow users to
Abort and Recover . We already essentially support
Recover (via sequence branching) and
Continue, if you’re comparing to the Assertion command.
In the meantime, you can use the Assertion command for your use case. While it is intended for software developers (because you have to write your assertion in code rather than using some inputs and dropdown menus), anyone can use it. Just add the command to your sequence from the commands list on the right side of the sequence editor page. Note: you may need to scroll down the list to see it!
ok, the problem was so simple… I just couldn’t see Assertions because I had to scroll down
assertion code is not a problem, as I am a software developer…