The following subpages are categories of frequently asked questions on Seirios.
There are 4 categories of questions;
For faster search and indexing, use the 'Search' bar at the top to find questions most relevant to your needs.
If you have questions, please feel free to ask by reaching us at sales@movel.ai
Use the Mapping feature to create your first map. Please refer to the mapping instructions in the above sections in full detail to start mapping
Seirios supports Differential, Omnidirectional or Ackermann drives. For Ackermann steering, users are required to input a radius value in the Settings section;
The radius value is your robot's turning radius in meters
Integration is possible; however, as localization is not done via Seirios (SLAM), there will be no map and therefore most features will not be accessible or usable.
Q: Unable to do mapping, it stuck in loading the logo A: Check your LiDAR data points, if the data points are above 3000, you have to downsample it. You can downsample it by configuring your LiDAR if possible, otherwise, you can use the Laser Scan Sparsifier ROS Package.
Q: When start localization, no scan data shows on the UI
A: Check your tf, the transformations between scan tf to base_link should be not tf static. Please use broadcast a transformation instead of static transformation publisher. (see number 7 point 1 in the Hardware Integration section.
Q: The autocorrection on the localization process seems so slow, how can I make it faster?
A: Please try to tune the parameters of the localization as well,
Follow these steps:
Navigate to the following directory in your robot's workspace: /home/<USER>/catkin_ws/movel_ai/config/movel/config/
.
Open the parameter file named amcl.yaml
(If amcl is current your localization algorithm).
Verify that the inflation layer is defined correctly within this file.
Try to reduce some values below:
update_min_d
: Translational movement required before performing a filter update (in meters).
update_min_a
: Rotational movement required before performing a filter update (in rad).
resample_interval
: Number of filter updates required before resampling.
You can see more about details the parameters on this ros wiki.
Please reload the map to apply the changes.
A: You can choose the local planner you want to use for the robot by following the steps below:
Go into the folder /home/<USER>/catkin_ws/movel_ai/config/movel/config/
In the parameter file move_base_params.yaml, change the base_local_planner
to the local planner that you want to use.
For my recommendation, if you want an optimal local planner and you don’t worry about the backward movement of the robot, you can go with TEB (Time Elastic Band) as your local planner.
But if you want a local planner that is designed to follow the global plan closely (which shows on the UI), you can go with Pebble Planner as your Local Planner.
You can just choose your local planner by uncommenting the line base_local_planner.
Q: How can I make the robot navigate through narrow paths?
A: To enable your robot to navigate through narrow paths, you need to adjust the configuration settings related to obstacle avoidance. Follow these steps:
Navigate to the following directory in your robot's workspace: /home/<USER>/catkin_ws/movel_ai/config/movel/config/
.
Open the parameter file named costmap_common_params.yaml
.
Verify that the inflation layer is defined correctly within this file.
To facilitate navigation through narrow spaces, you'll need to reduce the inflation radius. The inflation_radius
is measured in meters and determines how much the map inflates obstacle cost values. To make your robot more capable of navigating through narrow passages, consider setting the inflation_radius
to a value that represents the width of your robot, plus some additional space.
By adjusting the inflation_radius
parameter, you can fine-tune your robot's ability to navigate tight spaces and ensure smoother movement through narrow paths.
You can see the pictures below to explain how the inflation_radius
affecting the navigation path width.
Please reload the map to apply the changes.
In the picture above, the red cells represent obstacles in the costmap. For the robot to avoid collision, the footprint of the robot should never intersect a red cell.
To view the user interface of Seirios RNS, enter localhost:4000 or <IPaddress>:4000 in your browser of choice
The following devices and resolutions are recommended to optimally use Seirios RNS user interface
Check if everything is set up correctly in docker-compose.yaml
See if containers are running in docker ps
Use admin:admin in both username and password fields
Device | Recommended Devices | Min Screen Size (W x L) | Orientation |
---|---|---|---|
Desktop
Windows or Mac
1440 x 1024
Landscape
Tablet
iPad mini or above
768 x 1024
Portrait & Landscape
Mobile
iPhone 8 or above
375 x 667
Portrait