...

1. Safety Precautions

2. Cameras

   1. general considerations for camera positioning?<TODO>Describe how camera CAD with the field of view (FOV) of the camera visible can be imported into RPC (CAD obtained from sensor provider for now) with “ignore collisions” checked to be able to verify aruco tags could be visible to the camera. A picture here could help

3. Aruco Calibration Tag Mounting

   1. Static mounted

   2. Robot mounted

...

• Calibration
  The calibration process requires a cal.json file which contains the cameras' serial numbers, Aruco markers' ids and measurements, and calibration targets. For the calibration process to work as expected, every project needs to have a home target named as robotname_home, for example, if we have a Fanuc robot in the project and we will use it for calibration we need to have a Fanuc_home target. The calibration targets should be connected on Roadmap to the home pose in RPC project in order for the calibration to succeed.

  For the further information and instruction, refer to cal.json

• Configuration
  A rapidsense.json is another file which is required to start rapidsense. This configuration file defines the volumes in the scene.

User Guide

Get started

(Happy path of a user workflow)

...

• Layout description

Features

• Scene Update
  This feature is used for obstacle detection. This is the main functionality of Beta release

• RapidSense Filters

  How to apply the different filters with their API and what they can do

Integration with Other Systems

• API Documentation

  • ScanScene (Obstacle Detection) filter

    • <TODO>description of the function and API. Streaming, Snapshot, and Clear RS voxel data modes

• API

Maintenance/ Repair

Troubleshooting and Support

• FAQ

• Common Problems and Solutions

  • Error code

    • <TODO> error code table with description, common causes, and common solutions.

• Contact Information

Legal and Compliance

...

Appendices

• Glossary

• Release Notes

...