Cannot get cameras to show images #9
Comments
|
hi Did you configured your ROS environment? $ source (your ros workspace path)/devel/setup.bash http://wiki.ros.org/ROS/Tutorials/InstallingandConfiguringROSEnvironment#Managing_Your_Environment thx |
|
Yes, I source the following path |
|
FYI, here's my directory hierarchy and here are the terminal messages when I run <$ roslaunch realsense_camera realsense_rviz.launch > Thanks again! |
|
did catkin_make run without any errors? |
|
I didn't try catkin_make, I used rosbuild. The process I went through is: As I said, I'm pretty new to ROS, was there a step I missed? |
|
I don't use rosbuild, but i think you are forgot do rosmake. http://wiki.ros.org/ROS/Tutorials/BuildingPackages rosbuild tag |
|
Got it to work, basically I didn't setup the workspace / directories properly. I got this to work for both catkin and rosmake. |
|
I too am facing this problem, would you mind elaborating on what you changes specifically with respect to workspace and directory setup? Update: It occurs to me that my problem might be to do with the camera I am using? I have the R200, which I am guessing is not supported by this? |
|
hi, i don't have the R200 camera, so i don't test it. Can you show me the 'dmesg' print info in terminal on ubuntu when the R200 camera plug in the computer. thx |
If it helps, this works fine: [http://wiki.ros.org/RealSense_R200] |
|
@isclayton do you use catkin or rosmake? |
|
@isclayton can you paste the results of the command. lsusb -v -d 8086:0a80 It might return different results if run as root. I think the R200 camera is almost the same as the F200, but there are some magic numbers I may need to include in the kernel patch, or udev rules to make it work. Getting the full USB headers might be enough information for me. |
|
catkin |
|
@isclayton Up until here are all workspace setup. Next: At this point, clone this git repository, and copy + paste its contents into ~/catkin_ws/src/realsense_camera, replacing all files Let me know if it works. |
Did not work |
|
It seems like it compiles and executes properly, but your device was not recognized: Which camera model are you using / what system are you running it on? |
|
I just realized I was not replying to BlazingForests :P. I am using the R200 camera...this was the problem I think. As I noted above for anyone interested...the Realsense-ROS R200 nodelet linked above works well for some basic functions. |
|
I wrote the kernel patch that gets the IR feed from the F200. I might be able to help if you send me the USB headers. I'll even make an ubuntu vivid kernel package. |
|
@isclayton yeah, I'm using the F200 model. I'll test out the R200 when I get the chance. |
|
@teknotus ya, I played around with your F200 stuff a little (your blog posts gave a great overview of the platform btw) and ended up using the Intel solution for the R200. I was particularly interested in the configuration utility you wrote, though I haven't yet got it working. I would be interested in doing the same for the R200, though I (somewhat embarrassingly) only just realized that the device is not publicly available yet, which probably makes development for it difficult. I'll shoot you an email to connect @sthsher thanks for your help all the same :) |
|
@isclayton thank you. @teknotus hi, daniel, Is there another way to get ir stream without kernel patch through v4l lib？ |
|
@BlazingForests I don't think so. USB Video Class accesses formats by index, but Video4Linux accesses by fourcc format identifier. It would be possible to modify the kernel to just accept the mystery format codes reported by USB cameras so that they don't have to be specifically supported, but that would be it's own patch. There is also a few libuvc forks patched to support realsense. The most maintained one looks to be. |
|
This is interesting. Looks like intel wrote their own ROS module. It seems to have a direct port of the windows driver to support the F200, but the R200 installer includes a kernel patch that looks a lot like mine. That kernel patch would give it access to the video, but there isn't a patch to fetch the factory calibration so it is probably getting that via a similar means to how it gets it for the F200. In any case it exports the camera projection via a ros topic. |
|
My Intel F200 can not run.,how can I do? ... logging to /home/zlt/.ros/log/b26d8f72-6046-11e5-92bd-68f728cbda34/roslaunch-zlt-5992.log started roslaunch server http://zlt:52470/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to b26d8f72-6046-11e5-92bd-68f728cbda34 realsense_camera_type = Intel(R) RealSense(TM) 3D Camer debug_depth_unit = 0depthWithIRStream - NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO Intel(R) RealSense(TM) 3D Camera lists PCI: usb-0000:00:14.0-1 /dev/video2use camera 010150076206 ============ start read UVMap ============ end read UVMap ============== VIDIOC_QUERYCAP VIDIOC_G_INPUT error 25, Inappropriate ioctl for device v4l2_munmap error 22, Invalid argument VIDIOC_REQBUFS error 22, Invalid argument |
|
@zltrock Hi, I was disabled some unused ioctl function, Please try again. Thx. |
|
I am sorry to tell you that it was still not running. SUMMARYPARAMETERS
NODES ROS_MASTER_URI=http://localhost:11311 core service [/rosout] found realsense_camera_type = Intel(R) RealSense(TM) 3D Camer debug_depth_unit = 0depthWithIRStream - NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO Intel(R) RealSense(TM) 3D Camera lists PCI: usb-0000:00:14.0-1 /dev/video2use camera 010150076206 ============ start read UVMap ============ end read UVMap ============== VIDIOC_QUERYCAP ======================== get ======================== set VIDIOC_S_PARM error 25, Inappropriate ioctl for device v4l2_munmap error 22, Invalid argument VIDIOC_REQBUFS error 22, Invalid argument and then I deleted the src/capturer.cpp Maybe that was some other wrong I did? I have one more question to ask you, can the F200 run in the ubuntu-arm? |
|
@zltrock I think the issue is ARM platform. I don't have test it on ARM platform. Can you show me the 'dmesg' print info in terminal when the F200 camera plug in the computer.? |
|
Thank you for your reply.It's night now...the issue is on the X86-64bit platform.I'll show you the 'dmesg' print info on Monday. I had tried it on arm platform,it also had some issues,but different from x86.And I can see the depth raw and colour raw by 'rqt'. my English is not good,I hope you can understand what I say. 发自我的小米手机在 DD [email protected]，2015年9月25日 下午8:37写道：@zltrock I think the issue is ARM platform. I don't have test it on ARM platform. Can you show me the 'dmesg' print info in terminal when the F200 camera plug in the computer.? —Reply to this email directly or view it on GitHub. |
|
@zltrock 哈哈 你可以用中文说明白。你那是 x86 和 ARM 平台都有问题吗？你有测试过别的F200吗？ |
|
I have a similar issue. My R200 works under librealsense. All examples are working find. My ROS application is under ~/catkin_ws/src. When I run Still cannot figure out why I did "source ~/catkin_ws/devel/setup.bash" |
|
you might need to run realsense_r200_rviz.launch |
|
a little bit better. Now 2 out of 3 images windows have image, one still no image. However, I cannot see what those images are. The tail of the terminal is this: video depth w,h - 314, 938 |
|
The errors about controls not being supported are because this dependency is not installed |
|
I followed the instruction exactly. What is the command to install the dependency? I guess is under ROS, right? |
The camera should still work with or without the controls though. |
|
Thanks. Under ~/catkin_ws ? I did the install without error. But it is the same. Yes, the IR image is missing. Why depth image is black and white, RGB is green? |
|
Sorry, The R200 support not complete. Now, I have some high level things to do. So i can't promise the time point. Sorry! Thx |
When I run
None of the image screens show anything (just displays "No Image")
and when I run
I get the error
I'm running Ubuntu 14.04 on VirtualBox via MacOSX 10.10.5 and using ROS Indigo
I'm new to ROS, so any help will be greatly appreciated. Thanks!
The text was updated successfully, but these errors were encountered: