| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi, I am using Ubuntu 12.04 with ROS hydro . Currently ,i am stuck with a error in rviz which states that " no image received" in status field under camera. I am using iball usb_cam. I tried all the camera drivers like gscam,uvc_camera,usb_cam . But , this error still exists . [Note: The image window does not produce any error. but camera window only produce this error .] Please give me any suggestions, Thank you
Two days ago, i meet this problem too. And below is how i solved it :
1, using rosconsole to open rviz node debugging mode.
rosconsole set /rviz_1492690688381763966 ros.rviz.message_filter debug
rviz_1492690688381763966 was your rviz node's name
and it shown the messages came from your camera with the frame name was head_camera(i used [usb_cam](http://wiki.ros.org/usb_cam) driver)
2, modify map to head_camera in Fixed Frame field of rviz.
Is your camera driver publishing CameraInfo as well as Image data?
The rviz Camera display requires calibration information, while the Image display does not.
[head_camera] does not match name narrow_stereo in file /home/user/.ros/camera_info/head_camera.yaml.....yes usb_cam is publishing camera_info . I think the problem may be because of this error . I manually put the camera calibration file in .ros/camera_info folder .
Resolved that name does not match error by renaming . But still "no image received" error esxists
i edited and resolved that name error .My camera driver publishes camera_info .but still that "no image problem exists".
Asked: 2016-03-10 12:45:34 -0600
Seen: 11,589 times
Last updated: Mar 11 '16
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Can you see the image with
image_view?yes , i can see image with image_view
I had the same problem. I was publishing the image and the camera_info correctly, but the image would still not show up. Solution: republishing my static tfs at 10 Hz, using tf instead of using tf2_ros. This solved the issue. I think that similar problems are common with rviz in ROS Indigo.