There are specific hardware requirements for RapidSense to function successfully. Special attention should be given in to the following the requirements to achieve best optimal performance possible.

PC/controller and OS requirements

Minimum required PC specifications

• Intel i7 or equivalent or better

• 128GB RAM minimum

• I/O ports for sensors (either USB or Ethernet)

• SSD hard drive preferred

• nVidia or AMD GPU required (mandatory)

OS Requirements

• Ubuntu Linux 22.04+

Native sensor support

RapidSense provides native support for a set of sensors.

Supported Sensors

• Lower-resolution/budget Standard applications: Intel RealSense D455

• High-resolution applications (requiring tight tolerances ~2-10mm): Photoneo (coming soon)

• Safety-applications: SICK safeVisionary2 (coming soon)

Note: The architecture is built to currently support 2 cameras (Photoneo for high-resolution applications requiring tight tolerances ~2-10mm and willing to spend more or Intel RealSense cameras for a budget-friendly solution where resolution can be relaxed more).

• Motioncam 3D depth + IR cameras (any size, both color and non-color)

Calibration requirements

Aruco tags are required to calibrate the sensors. RapidSense supports the April 36H11 tag format. See section "Calibration Tag Information" for further information.

Mounting calibration tags

Image Added

In order to ensure a robust and repeatable calibration process, it is required that the calibration tag be fixed to the robot.

Users must design and install a mount for the calibration tag. It is recommended that the mount be attached to the end-effector.

The following are examples of robot-mounted tags.

Sensor Mounting and Occlusions

Occlusions are the parts of the environment that are not in view of the sensor due to an obstruction. The goal in placing your sensors, therefore, is to minimize occlusions. What positions will give the sensors as complete a view as possible of the robot setup at all times?a camera cannot see due an obstruction. It is recommended that sensor placement is made so as to minimize occlusions (e.g., it is not optimal to place a sensor directly behind a robot).

Sensor placement also depends on the robot application. For example, for a pick and place application, ask yourself, where will the robot move? Where will the occlusions be, and for which sensors? 

You should expect this This process tends to be somewhat trial-and-error. 

To get the achieve optimal performance out of the RapidSense system, keep the following guidelines in mind when mounting your sensors:

1. Make sure to position the sensors in your workspace to maximize the likelihood that obstacles will appear within the rated Field of View (FOV) of the sensor that is selected. Most coverage of the environment. Most sensor providers provide CAD models of the sensors and include the field-of-view (FOV) in the model, which this can be used to visualize and verify the sensor ability to see the Volume of interest.

2. The Intel Realsense specifications are for +/- 2% depth accuracy when they’re within 2 meters of an obstacle, so we recommend placing cameras across the workspace so that obstacles are within this distance. 

3. Space the sensors apart from one another and at different angles to provide different perspectives of the scene. 

4. Mount the sensors securely and rigidly. If a sensor vibrates relative to robot motion, it will return noisy data resulting in false positives for obstacles. It can also cause sensors to shift and invalidate the calibration data.

5. Connect the sensor cables with strain relievers. 

   

Lighting Conditions

It is recommended to control lighting conditions as best as possible for applications through adding covers to deflect direct overhead lighting, sunlight, or other direct ambient light sources. Lighting that is directed directly into Ambient lighting directly cast onto the sensors and the environment or that is reflected off of very highly reflective surfaces can cause issues with sensor detections introduce noise and wash out images needed by the sensors and should be avoided and/or controlled (i.e., minimized). Changes in lighting conditions during operation, such as the effects of sunlight, should be prevented. Depending on sensor selection, the effects of lighting to the system will may vary.

.

Aruco tags will be necessary to acquire in order to perform calibration of the sensors to the RTR system.

At least (2) different Aruco tag patterns are required per application:

1. One mounted on the robot end effector (TCP location of tag will need to be provided)

2. One mounted static in the scene that is visible to the sensors

Additional Aruco tags may be required depending on the system configuration.

See section "Calibration Tag Information" for further information.

Calibration Tag Mounting

When you mount the calibration tags on the robot end effector, note the orientation of the tag. In the photo below, the one with the text is down.

Image Removed

In order to the calibration repeatable with accuracy, you may need to purchase or create a fixture of the tag and its CAD model like below.

Image Removed

Here are some examples of tags attached to robots.

Target positions for each camera must be created in RapidPlan. Set the target at a location that is easily recognized by the camera. Once the target points are decided, auto-connect the targets for the calibration sequence.

3. PC spec and OS requirements

Required PC specification

• Intel i7 or equivalent or better

• 128GB RAM minimum

• I/O ports for sensors (either USB or Ethernet)

• SSD hard drive preferred

• nVidia or AMD GPU preferred but not required

OS Requirements