Page Comparison

response_type: This indicates which format the Realtime Controller will use when sending responses; either CSV or yaml. The default response type is yaml. The argument can be either case insensitive text or its numeric equivalent.

• 0 or csv

• 1 or yaml

set_ip_default:

This command is used to set the response format of the TCP/IP communication with the Realtime Controller. The Realtime controller stores this response type for each client that is connected to it. This command should be called at the beginning of a program to indicate the format in which the responses should be sent. If this command is not sent, the default response type is yaml.

If the set_ip_default argument is enabled, then all new connections from the IP address will use the specified response type. Existing sockets will be unaffected by this change, until they re-establish a connection.

As long as the IP address has at least one open connection, the settings will persist.

This command will return a response to acknowledge the command has been received and executed successfully.

length: This specifies the unit of measure for length. The unit can be specified with a case insensitive string or its corresponding integer value. For example, when a pose is specified this length unit will be used.

• meters

• centimeters

• millimeters

• feet

• inches

angle: This specifies the unit of measure for angles. The unit can be specified with a case insensitive string or its corresponding integer value. For example, when a robot’s joint angles are set or when a frame’s rotation is specified, this angle unit will be used.

• radians

• degrees

GetUnits command returns both units set for the current connection:

• Length (millimeters, centimeters, meters, feet, inches)

• Angle (degrees, radians)

This command will return a response to show the units used by the loaded project.

length: This specifies the unit of measure for length. The unit can be specified with a case insensitive string or its corresponding integer value. For example, when a pose is specified this length unit will be used.

• 0 or m,meter,meters

• 1 or cm,centimeter,centimeters

• 2 or mm,millimeter,millimeters

• 3 or ft,foot,feet,'

• 4 or in,inch,inches,”

angle: This specifies the unit of measure for angles. The unit can be specified with a case insensitive string or its corresponding integer value. For example, when a robot’s joint angles are set or when a frame’s rotation is specified, this angle unit will be used.

• 0 or rad,rads,radian,radians

• 1 or deg,degs,degree,degrees,°

set_ip_default:

This command is used to set the unit convention for API calls made to the Realtime controller. On first project load, the default units of millimeters and degrees will be used, and if this command is called, the units will be stored for that specific client. Subsequent loads for that project will use require the client to reinitialize their unit convention.

If the set_ip_default argument is enabled, then all new connections from the IP address will use these unit preferences. Existing sockets will be unaffected by this change, until they re-establish a connection.

As long as the IP address has at least one open connection, the settings will persist.

This command will return a response to acknowledge the command has been received and executed successfully.

None

This command retrieves the current mode of the Realtime Controller.

This command will return a response code, followed by the current state of the system. The states of the system are: Config mode, Operation mode, Calibration mode and Fault mode.

reset_connection: [ OPTIONAL ] This indicates whether a ClearFaults command will reconnect to the robot controller after the command is issued. The default value is true.

If a robot error/fault state occurs for one of the robots in the currently loaded deconfliction group, the Realtime Controller will enter a fault state. Examples of reasons may be: lost connection to a robot due to an E-stop, or the robot entering a fault state due to excessive speed or force. The ClearFaults command will attempt to recover any faults that the OEM controller allows allows to be cleared programmatically, and transition the Controller back into Config mode if possible. It will fail if there are still active, unresolvable faults.

If reset_connection is true(default value), the Realtime Controller will attempt to reconnect to the robot controller after recovering from a fault state. If reset_connection is false, an explicit Connect ASCII call would be required prior to entering Operation mode.

This command will return a single response code as a result value.

project_name: The name of the project installed on the control panel that you want to load.

upgrade: [ OPTIONAL ] A boolean value that decides if the installed RPC project is from an earlier release version, it will be upgraded for compatibility. Default value is True.

This function loads an RPC project. A load result will be returned once the process has finished and then RapidPlan will be in configuration mode.

This command will return a response code to acknowledge the command has been received.

{topic: LoadProject,type: Response,data: {seq: <value>}}

Once the load is completed, the system will send a delayed response to indicate the project has finished loading.  

{topic: LoadProject,type: DelayedResponse,data: {seq: <value>}}

None

This command retrieves the currently loaded project on the Realtime Controller.

If a project is not currently loaded, an error code will be returned {code: 3009,msg: PROJECT_NOT_LOADED}

This command will return a response code, followed by the currently loaded project or an appropriate error code.

None

This command brings the Realtime Controller out of operation mode and unloads the project. Current motions will be cancelled, and no new motion requests will be accepted. Duplicate calls have no effect. Connection to robot controllers will be terminated.

This command will return a response to acknowledge the command has been received.

{topic: UnloadProject,type: Response}

project_name:[ OPTIONAL ] This indicates which project will be made the default project. If this argument is omitted, any previous setting will be cleared and no project will be the default.

This command is used to define which project is the Default project that will automatically be loaded when RapidPlan powers on or is otherwise not in Operation Mode.

Sending a SetDefaultProject command without specifying the project_name parameter will clear any previous setting.

This command will return a response to acknowledge the command has been received and executed successfully.

{topic: SetDefaultProject,data: {project_name: DemoProject}}

or

{topic: SetDefaultProject}

connect [ OPTIONAL ]: this boolean argument, if true, will connect all robots upon entering Operation mode. Default is false.

This command indicates that the project is ready to begin operation. This call is blocking, until all active robots have been connected. Once all participating robots have indicated readiness, return messages will be sent, and subsequent Move calls will be accepted.

This command will return a response to acknowledge the command has been received and executed successfully.

None

This command brings the Realtime Controller out of operation mode back into Config Mode. Current motions will be cancelled, and no new motion requests will be accepted. Duplicate calls have no effect. Connection to robot controllers will be maintained when returning to CONFIG mode.

This command will return a response to acknowledge the command has been received and executed successfully.

None

This command issues an asynchronous system call, systemctl poweroff -i, which shuts the appliance down, if in Fault or Configuration Mode.
Should the appliance be in operation or in calibration mode, this command will be rejected.

Between this call and the system shutting down, the appliance will be in a “Shutdown” state and refuse any further ASCII commands.
If this system call results in an error, rather than shutting down the following will occur:

• An additional delayed response will be returned, with the command and error status

• The controller will enter Fault mode

This command will return a response to acknowledge the command has been received and queued for execution.

If the shutdown command fails during execution, a delayed response will be sent with the command’s error status.

message:A string to be written to the RapidPlan logs. Must be less than 500 characters and may only contain letters, numbers, - and ..

This function allows the user to write a simple string to the RapidPlan logs.

This command will return immediately with a response indicating whether or not the string could be written to the log.

None

This command indicates to RTR that for the upcoming cycle, RTR should record motion data for interlock calculations. This command is only accepted in CONFIG mode. To generate an interlock report, issue BeginInerlockRecording, execute all the robot motions, call EnterConfigMode, and then call GenerateInterlockData to retrieve the result.

This command will return a response to acknowledge the command has been received and executed successfully.

None

This command indicates to RTR to that the simulation tool wishes to retrieve the interlock data for the preceding cycle. This command is only accepted in CONFIG mode.

The response is a report of interlock data for each edge taken by a robot while interlock recording was active in YAML format. The report contains keys for each robot, and for each robot there is a key for every motion it takes.

• Each motion taken by the robot is represented as a sequence_number

• For each sequence_number, a path is provided which contains a list of waypoints.

  • The first waypoint is always the starting position of the robot during the move.

  • The last waypoint is always the position the robot when the move finishes.

• For each sequence_number an interlock list is provided.

  • Each interlock is given a unique name.

  • An empty list indicates that no interlocks are required for that motion.

  • The begin_interlock key indicates the furthest point the robot can proceed to before it is required to obtain the specific interlock.

  • The end_interlock key indicates which point the robot must reach in order to release the interlock.

  • It is possible for the end_interlock key to be achieved through a different move.

  • Sometimes, the interlocks starting position is the first waypoint of the move which means the robot cannot move at all until the interlock is obtained.

  • Interlocks are not robot specific, so the same interlock can appear for multiple robots motions.

  • A null value for end_interlock indicates that the robot was still in a position that required an interlock when the recording was terminated.

robot_names: [ OPTIONAL ] An array specifying which robots should be activated. If not passed, all inactive robots in the project will be activated.

project_name: [ OPTIONAL ] The name of the project you’d like to activate the robot in. This is required if the robot you want to deactivate is not in the loaded project.

This command will re-activate a robot. After this command, when Connect is called, the activated robot will be connected to, and when in OPERATION mode this robot will be controlled by RTR.
This command must be called when the controller is in CONFIG mode.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: Specifies which robot should be deactivated.
project_name: [ OPTIONAL ] The name of the project you’d like to deactivate the robot in. This is required if the robot you want to deactivate is not in the loaded project. If the project is not loaded robot_name is the only other valid key.
preset_name: [ OPTIONAL ] A string specifying the preset of the robot to be used in the inactive state. The preset will determine the collision geometry as well as the number of joints. If not specified, the active preset will be used.

treat_as_obstacle: [ OPTIONAL ] A boolean value that specifies if the deactivated robot should be treated for collisions by the other robots in the work cell. Default value is true.
If treat_as_obstacle is enabled, then the following keys are mutually exclusive to specify the behavior of the deactivated robot:

• joint_config: An array of floats specifying the angle for each joint of the robot. If the robot’s preset includes user defined joints, they must be provided as well, sorted by the driver index.

• target_name: A string specifying the name of the target that the robot will be positioned at. A user is also able to update a deactivated robot position using DeactivateRobot command with a new target specified by target_name: <new target> and treat_as_obstacle: True.

• use_last_known_config: Default option. A boolean flag that specifies the last known joint configuration of the robot should be used. A robot must have been Connected at least once for there to be known joint angles. These values are saved to disk, so on project reload, this option can still be used.

This command ‘deactivates’ a robot which means the RTR controller will ignore it when connecting to the robots within a project. Subsequent Connect commands will only connect to activated robots, and when in Operation mode, only the activated robots will be controlled by RTR. In order to prevent collisions, the deactivated robots can be configured for collision checking by setting the appropriate preset and joint angles. Optionally, the robot can be ignored during collision checking if it is not present in the workcell.
This command must be called when the controller is in CONFIG mode.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name:

This command connects to all active robots in the loaded project, or optionally a single robot. After this command executes, the Realtime Controller will begin monitoring the position of the robot/s.

This command should normally be called near the beginning of a robot program, before attempting to make any Move commands. If the robot/s have already been connected, this command will return successfully.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name:

This command disconnects from all robots in the project (unless a robot is specified) and returns them to the Initialized status. Disconnect can only be called successfully when in CONFIG mode.
This command is useful for saving time by keeping the project loaded on the controller while allowing the robots to perform tasks independent of Realtime control like rebooting.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: The name of the robot to acquire control of.
preset_name:

This command allows the user to signal that they are done with an operation that required RTR to release external control of the robot, and the Realtime Controller should resume control, with the last active robot preset or a specified preset.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: The name of the robot to release control of.
preset_name:

This command is intended to enable the user to take temporary control of the robot to get/set IOs, or execute a portion of their robot program that is not suitable for RTR control at this point. This may be gluing, welding, or some other time-dependent, sensitive process. 
While a robot is in Released mode, the rest of the Realtime Controller system will use the last known joint state of the paused robot as an obstacle, and will use the robot preset that was active (or optionally set) when that call was made. 
After completing the desired operation, the user should call AcquireControl. Until that call, the robot will not accept any Move commands from this API.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: The name of the robot this command is for.
max_accel: A value from 1mm/s^2 to 10,000,000mm/s^2 that defines the maximum acceleration allowed for the specified robot. The clients active units will be used, or the default units of mm/s^2.

reset:

This command limits the linear acceleration of a robots TCP. A user can specify the max acceleration allowed for a robot using this command, or reset to the default value using the reset flag. This command can only be sent when the specified robot is stationary, and all subsequent motions will adhere to the provided limit.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: The name of the robot this command is for.
max_speed: A value from 0.1mm/s to 100,000mm/s that defines the max linear speed allowed for a specified robots TCP. The clients active units will be used, or the default units of mm/s.

reset:

This command limits the max linear speed of a specified robot. In following move commands, the speed parameter will move the robot at a percent of this specified speed. For example, if this command is called and 500 (in mm/s) is passed for the max_speed parameter, a move command with a speed parameter of 0.5 will move the robot at up to 250mm/s.

A user can specify the max linear speed allowed for a robot using this command, or reset to the default value using the reset flag.

This command can only be sent when the specified robot is stationary, and all subsequent motions will adhere to the provided limit.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: This indicates which robot this call pertains to .
enabled: Accepts 0 to disable alternate behavior or 1 to enable alternate behavior at the specified goal. If enabled is being set to 0, no other arguments are required.

complete_move: [ OPTIONAL ] Default value is 1 or true. This Boolean specifies if the robot should continuously try to plan a motion to the original goal after it has successfully moved to the alternate location. If true, a robot for which a move timed out will first move to the alternate location. If this alternate move is successful it will continuously try to plan a motion from the alternate location to the original move request location. If False, a robot for which a move timed out will move to the alternate location and wait there for the next command.

mode: [ OPTIONAL ] Specifies what the robot should do if the original motion fails.

• 0: Default behavior. Move to a different, specified, position.

• 1: Partial Execution. If this option is selected, the robot will move along its path as far as it can before a robot-based obstruction is present. If the obstruction is removed before deceleration, the robot will not stop at this point and continue smoothly towards the goal. If the obstruction is still present, the robot will come to a stop and automatically resume motion when the robot-based obstruction is removed. This behavior does not trigger for static-obstacle obstructions. When Partial Execution is enabled, complete_move is always set to true.

• multirobot: If this option is selected, the robot will automatically be entered into a multi robot plan to try to get out of deadlock. Only other robots that are also configured to use multirobot avoidance will be used in this planning.

goal: [ OPTIONAL ] If mode is set to 0, this argument specifies the position that will act as the alternate position for the specified robot. Goal is a placeholder, and the actual key value pair would correspond to the acceptable positions which are:

• target_name: <target_name>

• pose: [x,y,z,r,p,y]

timeout: [ OPTIONAL ] -1 or 0.05 to 1000. Default value is -1. A value of -1 indicates infinite time. Otherwise, this value specifies the time a robot waits for the next move.

This command is used to enable and set

the alternate location for a robot

. With this feature enabled, in the event a Move command fails or is interrupted, the Realtime Controller will not return a response code immediately, and will instead automatically plan to the specified alternate position. Depending on the behavior of complete move the Realtime Controller will either return a response Error code indicating the robot reached the alternate location, or continue to plan to the location that was first specified in the move command.
Only one target can be set as the alternate location, so if that target does not exist in all of the robots presets, when a preset it changed, the alternate location should be updated.
Enabling the alternate location behavior changes the way a robot will execute a move, therefore a SetAlternateLocation command can only be sent while a robot is stationary and while the Realtime Controller is in either CONFIG or OPERATION mode.
When this behavior is enabled, the robot will execute motions using the same parameters as the original move. For example, if a move is sent using move_type: roadmap then the robot will make a roadmap move to the alternate location. If the original move is a move_type: direct then a direct move will be made to the alternate location.
When partial execution is enabled (mode: 1) or the default behavior (mode: 0) with complete move enabled, the timeout value is used.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: This indicates which robot this call pertains to. 

timeout: -1 or 0.05 to 1000.0. This indicates how long the Realtime Controller should continue trying to find a path if one cannot currently be found. A value of -1 indicates an infinite timeout. Otherwise, any non-zero floating point value specifies the time (in seconds) before a timeout response is sent.
max_replans:

This function should be invoked towards the beginning of a robot program. It sets the behavior for the robot with respect to replanning and timeout behavior. This function must be called when a project is already loaded. If this function is not called, the default behavior for a project will be: timeout = 0 and max_replans=-1.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: The name of the robot this command is for.
preset_name: Specifies which preset to switch to as defined in RPC.

This command changes the active robot preset for a specific robot. When a preset is changed, current robot motions are not re-validated, but new Move commands will respect the new active preset.

A robot must be stationary in order to call this command explicitly. SetRobotPreset commands will be rejected if sent between a user issuing move request to the RTR controller, and the final response being sent from the RTR controller to the user for a given bot . If a preset change is needed, it can be accomplished using the preset_name key within a queued move or combined move request. In the case of switching presets using the preset_name key, there is a requirement that changes in preset during queued moves or CombinedMoves must not change the TCP or the controllable axes. This requirement is in effect if there are any current motions that the user has issued to RTR, that RTR has not yet returned the final API response to the user.

If the new preset has a different number of controlled axes than the current preset, ReleaseControl must be called for that robot prior to the SetRobotPreset command. Once the preset change has succeeded, AcquireControl can be called again.

When called, the selected preset is stored to disk so upon project reload, the last active preset will be used.

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: Specifies the name of the robot to return the presets for.

This command will return a response with a comma separated array of the robot preset names (preset_names) and the active preset name (active_preset). 

active_preset: This response will return the name of the active robot preset.

robot_presets: This response will return the names of all presets from the same robot.

For CSV responses, after the acknowledgement codes, i.e., GetRobotPresets, 0, the response code will return with the name of the active preset, followed by the number of the robot presets, and then followed by the name of each robot preset.

robot_name: The name of the robot controlled by the Move command.

goal: Where the robot will move to, either a target or pose or joint configuration. Goal is a placeholder key, and the acceptable keys are either pose or target or joint_config. The target value can be a named target. The goal may include external axes that are specified as part of a named target or a joint configuration, or as external_axes of a pose move. Unless the external axes value is provided as an argument in external_axes, external axes will either remain fixed during a move, or switch to different setpoint values defined by roadmap moves. Valid key values are as following, pose: [x,y,z,r,p,y] or target: target_name or joint_config: [j1, j2, j3, j4, j5, j6] to move robot native joints, or [j1, j2, j3, j4, j5, j6, j7, j8...] to move robot pose + external joints.

speed: The speed at which the robot will move on a scale from 0.01 to 1.0. This scales max velocity but not acceleration or jerk.

move_type: [ OPTIONAL ] The type of move the robot will make. Either direct, roadmap, or planning. Default move type is a roadmap move. The arguments are case insensitive or can use the assigned numeric value.

• 0 or direct

• 1 or roadmap

• 2 or planning

smoothing: [ OPTIONAL ] A value from 0.0 mm to 500 mm indicating how far from a node the robot should attempt to begin smoothing its trajectory. Default value is 0.0 mm. Note that a higher smoothing value does not necessarily mean faster movement.

interp: [ OPTIONAL ] Specifies the interpolation type for the robot when making a direct move, or any time it must leave the roadmap. Use the case insensitive string, or its integer equivalent to specify joint or linear interpolation. This parameter does not apply to a planning move. Default is joint space interpolation.

• 0 or J (default)

• 1 or L

collision_check: [ OPTIONAL ] This flag overrides collision checking against the static scene for Direct move types. Robot to robot collisions will always be checked regardless of this flag, but robot self collisions will not be checked. A value of 1 specifies collisions should be checked, and a value of 0 specifies collisions will not be checked. Default value is 1.

collision_check_dsm: [ OPTIONAL ] This flag overrides collision checking against the dynamic scene model for Direct move types. A value of 1 specifies collisions should be checked, and a value of 0 specifies collisions will not be checked. Default value is 1.

timeout: [ OPTIONAL ] This timeout only applies to planning move types when the interrupt behavior is not applicable. This value is the amount of time given to plan a path to the specified goal, in seconds. If not provided, the default value is 10 seconds. The minimum value is 0.01 seconds and the maximum value is 120.0 seconds.

relative: [ OPTIONAL ] A boolean flag indicating that a pose or joint_config move should be performed relative to the last commanded robot pose or joint configuration. Default value is false. All move types are supported when using the relative flag. A reference frame name, ref_frame, can be specified as well for the pose to be in.

A relative move can be performed on all robot joints and external axes if it’s a direct, joint_config or a pose move. A full joint configuration including external axes, e.g., [j1, j2, j3, j4, j5, j6, j7, j8...], or, a full pose including external axes, e.g., pose: [0,0,0,0,0,0], external_axes: {rail: 50}}, should be given to specify a relative direct move. Multi-axis relatives are supported.

ref_frame: [ OPTIONAL ] The name of a frame in the RPC project that should be used as a reference for relative moves. The default reference frame is world.

preset_name: [ OPTIONAL ] This argument specifies which preset the robot should switch to before executing the motion. Including this argument has the same effect as calling SetRobotPreset before the Move command. If included, the robot cannot have any moves in its queue with a different TCP or number of controlled axes.

external_axes: [ OPTIONAL ] This argument, including all the related parameters that are defined within this argument, specifies the names of the external axes, the external axes position values for a direct move or a roadmap move to a goal pose.

If a robot's external axes remain fixed during a move, or switch to different setpoint values defined by a target, external_axes should be left unspecified.

external_axes argument is not used when the goal type is joint_config, because joint_config could include all robot native joints and external axes values.

Robot pose value plus external_axes can be used for relative direct pose moves.

• external_axes is defined as {<axis name>: active} or {<axis name>: <value>}. The names of the external axes must match what is already defined in the RapidPlan Create project.

• use {<axis name>: active} if an external axis is used by RapidPlan software when solving a move to a goal pose.

• use {<axis name>: <value>} if an external axis is used for a move to a goal pose with a specific external axis position value.

shortest_path_only: [ OPTIONAL ] for roadmap moves only, this optional argument only allows the robot use what would be the shortest path through the roadmap. If that path isn’t available, robot would wait, or use partial moves settings if that option is specified.

costs : [ OPTIONAL ] for planning moves only, this argument defines the cost penalty values of the individual cost terms. At least one cost term is required for the costs argument.

• The combined value of external_axis, paths_cost and waypoints_costshould be = 1.0.

• external_axis : [ OPTIONAL ] how much external axes motions are penalized. The default value is 0.0, which puts no penalty on using the external axes. The range of this float-point value is between 0.0 and 1.0.

• path_length: [ OPTIONAL ] this argument defines the cost penalty value for a planning move using the shortest path. The range of the value is between 0.0 and 1.0.

• via_points: [ OPTIONAL ] this argument defines the cost penalty value for a planning move using the fewest via points (waypoints). The range of the value is between 0.0 and 1.0.

constraints : [ OPTIONAL ]

for planning moves only, this argument defines an array of user specified orientation constraints that only allow the TCP to rotate along certain axes but not the others between targets.

• type : Specifies a type of constraint. Currently, only orientation constraint is supported.

  • 0 or orientation

• axis : an array of 3 integer values that specifies which axis to be constrained. 1 means the robot TCP would not rotate along this axis during the motion, but a deviation of 1 degree will be allowed which gives the planner a bit of "slack" to find solutions quicker without much detrimental effect on output paths. 0 means the robot TCP allows to rotate along this axis. Two axes are required to be constrained. If there is no offset specified, the vector axis [1 0 1] represents the x-y-z axis of the TCP frame. Otherwise, they are x-y-z axis of the ref frame from the TCP frame with offset.

• offset: [ OPTIONAL ] an array of 6 floats that specifies an offset that will be applied to the frame relative to TCP frame. The client's active units and rotation convention are used, or the default of millimeters, degrees, and roll pitch yaw.
  For example, if a gripper holding a cup of water like the following cases:
  

  Image Added

  the constraint would be:

  a. no offset, and constraints: [{type: orientation, axis: [ 1, 1, 0 ] }]

  b. no offset, and constraints: [{type: orientation, axis: [ 0, 1, 1 ] }]

  c. constraints: [{type: orientation, offset:[delta_x,0,0,0,delta_pitch,0], axis: [ 1, 1, 0 ] }]

trigger: [ OPTIONAL ] This argument, including all the related parameters that are defined within this object, specifies an output based on the timing of a move or a move segment of a combined move. trigger is an object with 3 fields:

• name: Only one trigger can be included for each move command, or each move segment of a combined move command. The trigger should have a user defined, stateless, globally unique name, to identify the signal for the receiver of the trigger.

• output: The trigger output should be configured during runtime as part of a move command, to turn on or off the output signal as an 1-shot event, until the signal is overridden by either another API command. If the output key is not specified, this trigger is disabled and trigger time is ignored. If output is specified, trigger time must be defined and cannot be omitted.

  • 0 or false: output is off

  • 1 or true: output is on

• time: Specifies the timing of the output, i.e. the time before the target position is reached, or after the move has started. The unit is in seconds and whose absolute value must be greater than 0.1.

  • time must be a none-zero value, and should always be >= 0.1 or <= -0.1. The move command will return an error code if 0.1 < time < 0.1.

  • A positive value ( time>=0.1) indicates the time after the move starts, ie., a "time-after trigger".

  • A negative value (time<=-0.1) indicates the time before reaching the goal, ie., a “time-before trigger”.

  • If time is longer than the actual move time, a time-after trigger will turn on when reaching the goal, a time-before trigger will turn on when the move starts. The MoveFeedback response message for the trigger will arrive before the MoveResult message for the move.

  • If alternate location is used(mode=0 in SetAlternateLocation), and if complete_move = true:

    • Only time-after triggers will apply to the move to the alternate location, time-before triggers will take no effect.

    • Only time-before triggers will apply to the move to the goal, time-after triggers will take no effect.

  • If alternate location is used(mode=0 in SetAlternateLocation), and if complete_move = false:

    • Only time-after triggers will apply to the move to the alternate location, time-before triggers will take no effect.

  • A trigger will not be re-activated if a Move command is issued when the robot is already at the goal position.

With this new generic Move command and the key value syntax, you can specify any of the former Blind Moves, MoveToXXX, and OffroadtoXXX commands with this one command.

A direct move moves the robot directly from its current position to its goal position with a given interpolation type. This command is efficient, but can easily be blocked by other robots. It is very useful for final motions, especially if collision checking needs to be disabled.

A roadmap move will follow the edges defined in the RPC project. This is expected to be the most common move type since the robots will use the roadmap to dynamically avoid obstacles. If pose is specified, and there is no target in the roadmap as that pose, the robot will leave the roadmap to reach the actual pose. The offroadmap portion will be collision checked, and will use the interpolation type specified (or joint interpolation by default).

A planning move calculates a path for the robot at runtime to reach the goal. This is primarily used to put a robot on the roadmap in the beginning of a task. When called, the requested robot must not be executing any current requests, otherwise it will immediately return an error. If any other robots are currently executing move requests when a planning move request is called, the robot attempting the planning move will be blocked with an Error code. If no collision free path to the goal can be found, the server will return an error by the end of the given timeout period.

Caution: There are risks involved with mixing RTR moves with non -RTR moves(for example, native moves from a robot teach pendant program). The user must make sure that a RTR move has completed successfully if the completion of that move is necessary for the next non-RTR move to be collision-free.

Caution: There are collision risks involved with stopping a robot from a robot teach pendant program when multi-robot moves are controlled by a RapidPlan controller. The user must make sure that all RTR move commands and stop signals from a different command source are programed and processed in a coordinated fashion, for collision-free operations in a multi-robot workcell.

When a Move request is received, path planning occurs before a response is sent. If a path is found, this command will return a response code to acknowledge the command has been received, the name of the robot that this move is for, and a unique sequence ID for this specific move. If planning fails, an appropriate error code will be returned, and no delayed response will be sent.

{topic: Move,type: Response,data: {robot_name: <value>,seq: <value>}}

If a path was found, the system will send a MoveResult message along with a response code to indicate when the move completes. The name of the robot that the move was for, and the unique sequence ID for that move will be returned in the message. If the move is interrupted, the delayed response will contain an appropriate error code.

{topic: Move,type: DelayedResponse,data: {robot_name: <value>,seq: <value>}}

or, for a trigger a feedback response will be sent to indicate that trigger output is activated to on, or off. The trigger feedback responses will include the same seq as the Move it is a part of.

{topic: Move,type: Feedback, data: {robot_name: <value>,seq: <value>, trigger: {name: <value>, output: <value>}}}

robot_name: The robot that this combined move is for. A combined move, can only included motions for one robot, and therefoer the robot_name key from the individual move commands can be omitted. If the robot_name is included in the individual Move commands, it will be ignored.

moves: An array of up to 10 Move commands to be concatenated together. The move commands can only be direct or roadmap move types, and must adhere to the Move command specification. However, redundant keys from the Move command can optionally be omitted, since they are arguments of the CombinedMove.

preset_name:

HoldMove is also able to be sent as a segment of a CombinedMove command.

CombinedMove allows multiple move commands to be executed as if it was one motion, and the individual segments can optionally be blended together to maintain a higher velocity.

The smoothing argument of each individual move command will specify if it will blend into the next move in the list, and at what distance from the end of the current move.

In the event a CombinedMove is interrupted, an error will be returned in the delayed response. In order to resume the CombinedMove from its current position, it is expected that the user maintains a list of the completed individual moves and then send a new CombinedMove with the moves that didn’t complete.

If move queuing is being used, a CombinedMove can be added to the queue just like any other move.

HoldMove is also able to be sent as a segment of a CombinedMove command to hold before executing a section of movement until a ResumeMove command has been sent.

This command will return an initial response to indicate that the command has been processed and a collision free path has been found for all moves, smoothing included. A unique sequence number will be included to identify the CombinedMove responses. When a move in the sequence is completed, a Feedback response will be returned, and upon completion of the full move sequence, additionally a DelayedResponse will be send.

{topic: CombinedMove,type: Response,data: {robot_name: <value>, seq: <value>}}

For every Move in the CombinedMove a feedback response will be sent to indicate that segment has completed. The feedback responses will include the same seq as the CombinedMove they are a part of, as well as a zero index index key to identify which segment the move result is for.

If a trigger output is specified for a move segment, a feedback message will be sent as soon as the trigger output is activated to on or off. Different segments of the same CombinedMove command are allowed to re-use the same trigger name, if the same trigger needs to be updated for each move segment. The feedback message contains the seq value but no index value.

{topic: CombinedMove,type: Feedback,data: {robot_name: <value>, seq: <value>, index: <value>}}
... additional Move DelayedResults ...
{topic: CombinedMove,type: DelayedResponse,data: {robot_name: <value>, seq: <value>}}

{
  topic: CombinedMove,
  data: {
   robot_name: robot_1,
    moves: [
      {move_type: roadmap,target: staging,speed: 1.0,smoothing: 0.25, trigger: {name: output_1, output: 1, time: -0.5}},
      {move_type: roadmap,target: pre_pick,speed: 1.0,smoothing: 0.1, trigger: {name: output_1, output: 0, time: -0.5}},
      {move_type: direct,pose: [0,0.5,0,0,180,0],speed: 1.0,smoothing: 0.0}
    ]
  }
}

Note: the new line (\n) and tab (\t) characters have been added for readability, the actual request format does not include them.

CombinedMove (including a HoldMove segment): {topic: CombinedMove, data: { robots: robot1, moves: [{<move>}, Hold, {<move>}]}}

robot_name: The name of the robot for which a move is being canceled.
acceleration_factor [ OPTIONAL ] : The acceleration factor at which the robot will move on a scale from 0.5(50%) to 1.0(100%), when the move is being canceled. The default value is 0.8.

This function tells the Realtime Controller to abort planning and motion for the specified robot. After calling this, a robot may be left in an off roadmap location and will require a planning move command.
This command is only accepted when the RTR Controller is in OPERATION mode.
If a series of Move commands are queued for the robot in question, they will all be canceled simultaneously. The delayed responses of these commands are not guaranteed to be in queue order.

If CancelMove is called before planning is finished for a Move command, robot preset of the canceled move will still be applied because the preset had changed before planning started.

If a move is canceled mid-motion after a Move command which also sets the robot preset, the robot preset will be maintained.|

This command will return a response to acknowledge the command has been received and executed successfully.

robot_name: Specifies which robot to hold move

This command blocks a robot from executing pre-sent or combined moves for a defined robot until a ResumeMove command is sent.

HoldMove is also able to be sent as a segment of a CombinedMove command. 

A robot that is holding will return an error while holding.

HoldMove: {topic: HoldMove, data: { robot_name: robot1}}

CombinedMove (including a blocked segment): {topic: CombinedMove, data: { robots: robot1, moves: [{<move>}, Hold, {<move>}]}}

HoldMove: {topic: HoldMove, type: Response, data: {}}

HoldMove: HoldMove, 0

robot_name: Specifies which robot to continue move

ResumeMove: This command continues robot the through combined or pre-set moves for a defined robot.

ResumeMove: {topic: ResumeMove, data: { robots: robot1}}

ResumeMove: {topic: ResumeMove, type: Response, data: {}}

ResumeMove: ResumeMove, 0

moves: An array of move commands for different robots. The move commands must adhere to the Move command specification.

For now, MultiRobotMoves only support moves of type Roadmap. At most one move is allowed per robot.

MultiRobotMove allows planning for multiple robots to occur at once if, for instance, you’d like robots to purposefully avoid blocking each other when trying to reach their target destinations. This is compared to normal motions where one robot motion is received at a time and is planned without consideration for what other robots may need to do. Note that normal motions will avoid colliding with other robots but cannot take into account the desired motions of robots whose paths have not yet been planned.

The command will return an initial response to indicate that the command has been processed and a collision free path has been found

.

A unique sequence number will be included to identify

the MultiRobotMove responses. The response will also include a list of robots that were unable to plan motions if the mode flag indicated that the motion should succeed anyway.

{topic: 

For every Move

in the MultiRobotMove, a feedback response will be sent when that robot completes its motion.

{topic: 

The following example shows how MultiRobotMove can be used to resolve a deadlock at runtime.

In the case of a deadlock, normal Move commands will return failure. Using MultiRobotMove combining the targets of the deadlocked robots will resolve the deadlock and move the robots to their targets.

robot_names = ["robA", "robB", "robC"]
target_map = {"robA":[A1,A2,A3,...], "robB":[B1,B2,B3,...], "robC":[C1,C2,C3,...]}
move_failed_robots = []
finish_all_targets = false
while(!finish_all_targets):
  if move_failed_robots.empty():
    for robot_name in robot_names:
      rtr_move_to_target(robot_name, next_targets[robot_name])
      if delay_response == succeed:
        update_target(robot_name, target_map[robot_name])
      else:
        move_failed_robots.insert(robot_name)
  else:
    rtr_multi_robot_move(robot_names, next_targets)
    if delay_response == succeed:
      update_targets(robot_names, target_map)
      move_failed_robots.clear()
  finish_all_targets = are_all_targets_finished(next_targets, target_map)

robot_name: Specifies which robot’s targets will be returned.

preset_name:

This command retrieves the targets for a given robot in a specific preset in the loaded project. The default behavior is to return the targets in the active robot preset, but a different preset can be specified.

This command will return a response code, followed by a comma separated array of the target names.

target_name: Specifies the name of the new target to be created.
robot_name: This indicates which robot will be assigned to the new target.

This command creates a target in the active robot preset for the specified robot.

The target is created using the robot’s current joint angles. To ensure consistent joint angle readings, the robot must stay stationary while the target is created. Therefore, the controller must be in CONFIG mode and the robot state must be connected.

No connections will be created automatically for the new target.

This command will return an acknowledgement with a status code indicating the command was received and executed. 

target_name: Specifies which target will have its position updated.
robot_name: This specifies which robots TCP will be used at the new target location.
retrigger_autoconnect: [ OPTIONAL ] This boolean argument specifies if the auto-connect should be regenerated when updating the targets position. If the target is not part of an auto-connect, then this argument will have no effect. The default value is False.

object_states:: [ OPTIONAL ] This argument specifies whether the validation of the updated target position should take consideration of all object states or only the active objects. This argument can be set to either all or active.

If object_states is set to all, path validation will check all object states when updating a target. This is the default setting. If object_states is set to active, path validation of will check active object states when updating a target.

pose: [ OPTIONAL ] , if pose values [x, y, z, r, p, y] are specified, the pose values will be used to update the target position, instead of the specified robot TCP location.

joint_config: [ OPTIONAL ] , the joint configuration values will be used to update the target position instead of the specified robot TCP location, even if the robot is disconnected. The joint configuration values should include all robot links and external axes.

ref_frame: [ OPTIONAL ] , if specified, this frame is used as a reference for the pose value. ref_frame can be either a frame defined in RPC or a DSM frame.

validation: [ OPTIONAL ] , if specified this allows ignoring edge validities when updating a target, accepts values:

• require_valid or 0 [default]: the command fails if a node or edge that was valid become invalid;

• allow_invalid or 1: the command succeeds even if a node or edge becomes invalid. A warning message is shown.

This command updates the specified targets position to be at the specified robot TCP location in its current preset, or using an optional pose value. The target’s new position will be used for all assigned robots.
The target is created using the robot’s current joint angles which means the controller must be in CONFIG mode and the robot state must be connected.

A target’s position will only be updated, if all of its connections remain valid, otherwise the command fails and returns an error code EDGE_INVALIDATED. This could result from the new position being unreachable, the new position being in collision, or one of the motions to the new position resulting in a collision.

Only one target can be updated at a time. While a target is updating, any subsequent UpdateTarget commands will be rejected.

With the retrigger_autoconnect argument set to true, the targets position will be updated, and then the auto-connect will be re-run using the same parameters as set in RapidPlan Create. With retrigger_autoconnect set to false, just the target’s position will change, and all via point locations will remain the same. The edges leading to the new target location will be validated against the constraints of the auto-connect, and the UpdateTarget command will fail if all constraints are not met.

This command will return an acknowledgement with a status code indicating the command was received and is being executed.

This command will also return a delayed response when the update has completed or failed.

target_name: Specifies the name of the target to be renamed.

new_target_name: Specifies the new name of the target.

This command renames a target. To rename a target, the Realtime Controller must be in CONFIG mode.

RapidPlan Create naming conventions must be followed. Duplicate names are not allowed. Any invalid names will be rejected by the command.

This command will return an acknowledgement with a status code indicating the command was received and executed.

target_name: Specifies the name of the target to be removed.

This command removes a target in the active robot preset for the specified robot.

To remove the target, Realtime Controller must be in CONFIG mode.

Removing the target will remove any manually created connections , and any connections created by auto-connect, between this target and other targets.

This command will return an acknowledgement with a status code indicating the command was received and executed.

robot_name: Specifies which robot to add the connection to.

preset:

targets: A list of targets to connect. At least 2 targets must be included. If the type is joint or cartesian then only 2 targets are allowed.

type: Specifies the type of connection to create. Acceptable values are joint (0), cartesian (1), or auto (2).

autoconnect_name:

validation:

• require_valid or 0: Run validation and require it to succeed, otherwise the change would be rolled back and an error code returned. This is the default option if validation option is unspecified for a manual connection or an autoconnect.

• allow_invalid or 1: Run validation but allow it to fail, with no error code.

This command creates new connections within a given roadmap. It can be used to create manual connections or auto-connects.

This command will return a response code.