There is not an explicit jump command, no. You can, however, put everything from line 76 on in a loop, and loop while restart == True instead. Then any code after this loop would only execute when restart == False. This should accomplish what you’re looking for.
As for adding to the count, if I’m understanding you right, all you have to do is just use an Assignment node and say var = var + 1. Logically, it sounds like you’re asking if(True OR False) which is ALWAYS true. Therefore you don’t need to make it a conditional at all, just increment the variable on its own line all the time.
Well. I guess it’s also a bit unpractical given that it looks at line numbers and not actual labels. So if a new node is inserted in the beginning of a program, you’d have to shift all your labels.
Woah, I’ve been looking into how to achieve something similar to a Jump to label on the UR. Can you share some more on this. what does the actual script look like to achieve this?
I mean you’re looking at it. That’s the whole script. It just jumps you to that line number. As efn points out, it’s not super great, since anything that changes your line numbering will in turn change where the jump instruction goes to. I spent a little time a while ago trying to guess my way into a hidden “label” instruction but didn’t find one.
Awesome, thanks for the information! That gives me a few options to try out. Still mind-blowing how UR is the only Robot Manufacturer I’ve dealt with without a jump/label command. I get why to some degree for simple applications, but for more complicated applications where you need to add in a check/retry/additional process based off certain conditions (especially after a deployment) it can become frustrating having to restructure the entire program to make it functional. It is what it is. Thanks Again!
