2.9 RapidPlan Setup
RapidPlan Project
RapidPlan - Realtime Robotics' motion planning software - is used in combination with RapidSense perception technology to adjust robot motion in response to sensed information. RapidPlan handles moving robots in a deconflicted manner. RapidPlan generates paths for all active robots so as to avoid collisions with one another and the modeled scene (i.e. the digital representation of the work cell). RapidSense adds an additional layer of collision avoidance with perceived (unmodeled and/or unexpected objects) in the scene.
To use RapidSense, the following is needed in the RapidPlan project
The project must represent the physical scene as closely as possible including accurate robot models with all necessary CAD data, presets and object states
For known poses/locations, targets should be created in the project
The project must have no invalid edges
The project must be loaded into the RTR Runtime Controller (Control Panel)
Calibration: TCP and Robot Target Positions
The following must also be included in the RapidPlan project, if the user is using RapidSense’s native sensor support.
Create a robot preset named “Calibration”.
Model the Aruco tag with the accurate thickness on the robot mount.
Set the default TCP of the preset to the center of the tag. Tag orientation is vital and must be correct to ensure successful calibration. See here for details.
Create a target for the “Home” position of each robot. These target names must follow the naming convention [robotname]_home. For instance, if the robot is named “Fanuc” in the RPC project, then it’s home position would be Fanuc_home.
Create target positions for calibration which have the Aruco tag on the robot within the field of view of each camera. Once the target points are decided, auto-connect the targets for the calibration sequence.
To determine whether a target position is “good”, you must run RapidSense with the
-f
option. In other words,rapidsense -f
. Then place RapidSense into “Configuring” mode via a REST tool such as Postman. See RS API for details.
See section 2.9 Sensor Calibration | Calibration Requirements for more details.