rtabmap+vinsfusion,The problem encountered when running rtabmap.launch. about rtabmap

[matlabbe]

The vins estimator should use camera_link as camera frame instead of camera. Maybe there is a config in vins to change it.

[t1tqq]

Thank you for your reply. I have already solved that issue.
However, it seems that the map I obtained has some problems.
This map is saved in ~/.ros/rtabmap.db. When I check Cloud and Odom under the image, the map coordinate system appears to be incorrect.

But when I only check Cloud, the map looks fine.

Is this a normal phenomenon, or do I need to perform coordinate transformations somewhere? Another question is, I plan to use this map for navigation in the next step. How can I utilize rtabmap.db? What should I do next? Could you please give me some help or suggestions? Thank you!

[matlabbe]

That Odom checkbox is to see the cloud in odom frame (roll, pitch) instead of base frame. That cloud is only visualizing a single node in the map. Open the database in rtabmap app instead, it will show the 3d point cloud of all nodes in map frame.

To use the map for navigation, we often relaunch rtabmap in localization mode. See Advanced section here.

[t1tqq]

I have already saved rtabmap.db. Could you please provide more details on how to open the database in the rtabmap app? What is this rtabmap app?

[matlabbe]

Are you using ROS?

$ rtabmap rtabmap.db

[t1tqq]

I used the command rtabmap-databaseViewer ~/.ros/rtabmap.db to view the map. The 3D point cloud of individual nodes seems fine, but the Occupancy grid formed by the 3D point clouds of all nodes is too messy, and the 2D map is also messy.

So, is my rtabmap.db file normal? If it is normal, how can I obtain a 2D map that can be used for navigation? This is my rtabmap.db compressed file.
rtabmap.zip

Thank you for your help.

[matlabbe]

The odometry pose looks wrong:

For that that particular node by looking at the actual image, I would have expected a roll and pitch value around 0.1 rad at most (slightly rotated on right, slight pitch towards ground), not -1.88 rad in roll.

It feels like the odometry is giving the pose of the IMU frame instead of the camera frame. There could be a 90 deg offset between these two frames. You could change the frame_id of rtabmap node to use the same frame than vins-fusion is using (e.g., imu frame).