Open mindThomas opened 7 years ago
Hi,
Are you streaming /camera/rgb/image_rect_color
, /camera/depth_registered/image_raw
and /camera/rgb/camera_info
on WiFi? Make sure they are received on your computer:
$ rostopic hz /camera/rgb/image_rect_color
$ rostopic hz /camera/depth_registered/image_raw
$ rostopic hz /camera/rgb/camera_info
You may want to stream them as compressed too. You can use argument compressed
for convenience. This will add relays to limit the bandwidth used, see tutorial Remote Mapping.
$ roslaunch rtabmap_ros rgbd_mapping.launch rtabmap_args:="--delete_db_on_start" compressed:=true
PS: I suggest to update the code from source if you cloned master branch after April 6 (after this commit https://github.com/introlab/rtabmap/commit/1d8952867d8b98ee3b0e5ad5390e7400fe5a7858 that caused this issue https://github.com/introlab/rtabmap_ros/issues/162).
cheers, Mathieu
Source code has been pulled from master today with which a clean build has been performed. Yes, the image topics are streamed over WiFi which can be seen/visualized either using Rviz or using the image viewer of rqt. The data refresh rate (FPS) is very slow though (<5 Hz).
OBS. The depth image is contained within "/camera/depth/image_raw" Can't remember if it was also contained within "/camera/depth_registered/image_raw", but I have tried adding the argument "depth_registered_topic:=/camera/depth/image_raw" without luck.
Do you have warnings like that after 5 seconds you started the launch?
[ INFO] [1491863470.494017006]: rtabmap 0.12.5 started...
[ WARN] [1491863474.292900716]: /rtabmap/rgbd_odometry: Did not receive data since 5 seconds!
Make sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header
are set.
/rtabmap/rgbd_odometry subscribed to (approx sync):
/camera/rgb/image_rect_color,
/camera/depth_registered/image_raw,
/camera/rgb/camera_info
[ WARN] [1491863475.005535189]: /rtabmap/rtabmapviz: Did not receive data since 5 seconds! Make
sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are
set. If topics are coming from different computers, make sure the clocks of the computers are
synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size"
parameter (current=10).
/rtabmap/rtabmapviz subscribed to (approx sync):
/rtabmap/odom,
/camera/rgb/image_rect_color,
/camera/depth_registered/image_raw,
/camera/rgb/camera_info,
/rtabmap/odom_info
[ WARN] [1491863475.486579636]: /rtabmap/rtabmap: Did not receive data since 5 seconds! Make
sure the input topics are published ("$ rostopic hz my_topic") and the timestamps in their header are
set. If topics are coming from different computers, make sure the clocks of the computers are
synchronized ("ntpdate"). If topics are not published at the same rate, you could increase "queue_size"
parameter (current=10).
/rtabmap/rtabmap subscribed to (approx sync):
/rtabmap/odom,
/camera/rgb/image_rect_color,
/camera/depth_registered/image_raw,
/camera/rgb/camera_info
Or any other errors/warnings?
cheers
If I do not set /use_sim_time to true I get the above mentioned warnings after 5 seconds. In both cases though I get nothing in the RTAB-MAP visualizer. Keep in mind that I want Visual Odometry only so I have no external odometry sensors publishing.
Here an output of the rates (with /use_sim_time set to false) after waiting/averaging for about 10 seconds:
/camera/rgb/image_rect_color
average rate: 10.101
min: 0.071s max: 0.621s std dev: 0.03016s window: 585
/camera/depth/image_rect_raw
average rate: 30.035
min: 0.024s max: 0.077s std dev: 0.00533s window: 328
/camera/rgb/camera_info
average rate: 30.006
min: 0.000s max: 0.082s std dev: 0.00276s window: 990
With /use_sim_time set to true I don't get any rate.
Hi,
use_sim_time=true
should be used only with a rosbag (and maybe with a simulation environment too).
The warnings don't appear when use_sim_time=true
because the simulated clock is not published, so never reaching 5 seconds of clock time. We should then fix the warnings when use_sim_time=false
(don't need to explicitly set it to false).
Can you try the Hand-held tutorial for RealSense R200? If realsense_camera package is used, the registered depth image is called /camera/depth_registered/sw_registered/image_rect_raw
. The launch would be:
$ roslaunch rtabmap_ros rgbd_mapping.launch rtabmap_args:="--delete_db_on_start" depth_registered_topic:=/camera/depth_registered/sw_registered/image_rect_raw
cheers, Mathieu
Hi. I have been trying to get rtabmap working with the R200 camera connected to our Intel Aero drone. For now I have not been trying to get it working on the Intel Aero board but rather using the distributed/networked structure of ROS and trying to run rtabmap on my computer running Ubuntu 14.04.
I have built rtabmap and rtabmap-ros from source, both trying the indigo-devel branch and latestly the master branch, but none of them with any success. I am afraid that the problem has something to do with the TF's not being published, as I can only see parts related to camera_link etc. being published in the /tf_static topic.
Everytime I try to run rtabmap it loads fine without any errors but the visualization screen stays blank.
This is the output of the latest run built from the master branch:
And this is the output when I ran the build from the indigo-devel branch (doesn't seem like a huge difference though):
Any suggestions or hints?