PrimaryClient

The Primary Client serves as an interface to the robot’s primary interface, present on port 30001. The PrimaryClient class supports, among other things, sending URScript code for execution on the robot through the primary interface. Currently it offers two methods of script execution: sendScript and sendScriptBlocking.

Script execution without feedback

Method signature:

bool sendScript(std::string program);

The sendScript method will accept valid URScript code, and send it to the robot through the primary interface. This is a non-blocking method, as it will return as soon as the program has been transferred to the robot. It returns true when the program is successfully transferred to the robot, and false otherwise. There is no feedback on whether the program is actually executed on the robot.

Script execution with feedback

Method signature:

bool sendScriptBlocking(
  std::string program,
  std::string script_name = "",
  std::chrono::milliseconds timeout = std::chrono::seconds(1),
  bool fail_on_warnings = true
);

The sendScriptBlocking method will also accept valid URScript code, but blocks until the execution result of the given program is available.

Prior to transferring the program it will first check that the robot is in a state where it can execute programs, if not it returns false.

If the robot is ready, the program is then transferred, and the method will wait for the robot to report that the program has either started, finished or encountered an error.

If the program has not started within the given timeout, the method returns false.

If the robot encounters an error or runtime exception during program execution the method also returns false.

If fail_on_warnings is true, it will also return false, if the robot reports a warning during program execution. Note: protective stops are reported as warnings by the robot.

The method only returns true if the program is successfully executed on the robot.

This method also accepts secondary programs, but no feedback is available for those, so it will behave similarly to the sendScript method in those cases, except for the pre-transfer checks.