This document introduces how to use the Slamware configuration tool according to your robot base configuration.
Table of Contents
|Table of Contents|
SLAMWARE module communicate with robot base using Control BUS protocol. Robot base should upload a corresponding configuration to SLAMWARE module, otherwise wrong positioning and navigation will happen.
The above devices should be configured following the robot base coordinate system. The detail of installation will be explained in the following section of this document. In addition, other parameters regarding wheel span, robot size, automatic recharge could be also configured with slamware_config_tool.
Robot Base Coordinate System
In the robot base coordinate system, the positive X points to the forward direction of robot, the positive y points to the left, the positive Z points to the top. In an angle coordinate system, the x positive is the 0°, and an counterclockwise rotation will be considered as positive(see pictures below).
On the Robot page, users can configure basic parameters of the robot. This page consist of 3 sections, Robot,Slamware Core Pose and Dimension. Currently Robot section is irrelevant to robot behavior, you can keep the default settings.
Slamware Core Configuration
On the Robot page, user can configure Slamware core pose. The ‘yaw ’indicates the counterclockwise angle difference between axis x of Slamcore coordinate system(see picture below) and axis x of the robot base coordinate system. The default setting is slamware core head up checked, which means the white side is on the top. if your slamcore has an reverse installation, please do not check the "slamware core head up" item.
Please note that the core should be placed horizontally.
Robot Diameter and Wheel Span Configuration
The diameter of the robot circumscribed circle should be considered as the Robot Diameter. This value is used to filter out obstacles detected by the lidar within the size of the chassis and prevent the objects on the chassis from misdirection and wrong navigation. Robot Wheel Span is the diameter of the circumscribed circle of the wheel of the robot, including the two-wheel and three-wheel omni-directional wheels. The measurement should start from the center of the tire thickness begins to measure.
Bumper/Sonar/Cliff Senor Configuration
In the Sensors page, you can configure sensor IDs, Types, position of installation. Please note that the sensor ID should be unique, which means you cannot assign the same ID number to two sensors, not even for sensor of different types. The coordinate system here is the chassis coordinate system.
In the LIDAR page, you can configure the position of installation of RPLidar. Please note that the “yaw” represents the angle difference between 0 angle of Lidar(see figure XX) and x positive of robot base coordinate system. If you check the “ Lidar Reverse Installation”, the RPLidar should be installed up-side down.
Motion Plan Configuration
On Motion Plan page, uses can configure paramters regarding obstacle avoidance. Due to the uneven shape of the robot, the obstacle avoidance range may not only be limited to the range of the chassis, the side margin is applied to adjust the size of the obstacle avoidance range. The obstacle avoidance range is a circle with a diameter of "Robot diameter + 2 * side margin"
Bump Handle Strategy is set to Default, that is, when bumper is triggered, robot start to move back and find other paths available.
On this page, users could configure the parameters related to infrared charging. this section is not related to motion control and obstacle avoidance, you can keep the default settings. If you have questions about the following parameters, please contact SLAMTEC technical support.
On this page, users could configure the parameters related to charging behavior. This section is not related to motion control and obstacle avoidance, you can keep the default settings. If you have questions about the following parameters, please contact SLAMTEC technical support.
Save Configuration File
There are 3 items on the top-right corner on the interface: