Best Of

These are not unique to URScript, there is a section in the manual that describes their logic operators. The ‘!’ is a rather unique operator. You could also use the keyword ‘not’ in its place. The main operators we use daily are ‘not’ ‘or’ ‘and’   

The question I would ask is why a thread in the function?   Do you need this to be processed in the background?  If not, this is a quick function call and so could easily be inline.  If you need to know always what tool is loaded, like if someone paused the robot and swapped tools then you need the thread to loop so that it is always running. The way it's written it's a single execution background function.

The function would simply be as below, notice I am using a return statement and not assigning the global variable directly.

def toolStatus():
  if (get_standard_digital_in(0)):  
     return 1
  elif (get_standard_digital_in(1)):
     return 2
  end
  return 0
end

Use it like this:

ToolAct=toolStatus()

Couple of things to point out, since this function is not dependent on global state its easily tested and secondly, get_digital_in was deprecated quite a while ago and replaced with more specific calls which you see represented in the code above.  Since the function has been officially deprecated they will most likely remove it from the language in the future which would cause your code to break when the update comes out.

Since the status of the `get_standard_digital_in(n)` call is a boolean return value I do not need to compare it to True or False as it is True or False, I can simply state in my logic that it either is that value by stating it directly or I can negate it by saying something like this

if (!get_standard_digital_in(0)):  #Read as "if not true" or in more common vernacular "if false"

ignore my last post, i ended up figuring it out!

I would assume that the vector is showing the acceleration of the tool axes relative to the base system. Just stating that the acceleration in X is relative to the x-axis of the tool coordinate. Since there are no rotations around the base frame I’m not sure how you’d translate these to align the forces relative to the base frame axes. 

Thanks for all the help guys, definitely helped me out! 

If it a thread you use run command. Otherwise just call the function direct. 

That variable is an execution step counter that is being added by either UR behind the scenes or possibly a URCap if you have one installed.  What version of polyscope are you running?  Since this is defined as a thread you have to use the run command to cause it to start, you can see that in the code below

Thread definition