-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errors when roslaunch with LR200 #2103
Comments
Hi @wenyan96 The LR200 (a variant of the R200) is listed in the Legacy Librealsense SDK's front-page documentation as being officially compatible with that SDK. My recollection is that R200 ROS launch files could be used with the ZR300 (the successor to the R200), so using a launch file designed for the R200 with the LR200 model is not necessarily a problem. I note though that in regard to realsense_camera, its documentation does list support for ZR300 but not LR200 specifically. http://wiki.ros.org/realsense_camera#Supported_Camera_Types Are you able to launch successfully if you use r200_nodelet_default.launch instead of r200_nodelet_rgbd.launch |
@MartyG-RealSense Hi, i tried r200_nodelet_default.launch but had the same error.
From issue #245 i thought he/she can run roslaunch with LR200, and i checked the mentioned constants.h file, there are indeed some constants of LR200 in the code.. To avoid the case that i build realsense_camera incorrectly, i'd like to write down what i did as following:
|
I will highlight your case to Doronhi the RealSense ROS wrapper developer. Thanks very much for your patience! |
@MartyG-RealSense Ok! Thank you and look forward to your good news! |
Hi, |
Hi @wenyan96 Do you require further assistance with this case, please? Thanks! |
@doronhi Thanks for your reply! But it may not work for me now since i have to work with lots of codes in newer opencv versions... Modifying them could be an extra task.. |
@MartyG-RealSense Sorry for the late reply. I tried to use librealsense to grab images and etc.. It works for me. maybe i'll try the method mentioned by doronhi afterwards. Thank you all! |
No problem at all, @wenyan96 - good luck with your tests! |
Hi @wenyan96 Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Hi, recently i'm using LR200 to capture some rgb and depth images and want to use them in visual slam.
For this sensor LR200, i used librealsense-legacy and realsense-ros-indigo-devel. I tried mainly two method to build them.
Method 1
http://wiki.ros.org/realsense_camera/Tutorials/Building_librealsense_from_Sources
like the reference i tried to put them in the same workspace
Method 2
#386
i tried what doisyg said in this issue
For both methods i can run the examples file of librealsense like ./cpp-capture successfully. BUT i met the same error as following when i roslaunch :
roslaunch realsense_camera r200_nodelet_rgbd.launch
SUMMARY
PARAMETERS`
NODES
/camera/
camera_nodelet_manager (nodelet/nodelet)
depth_metric (nodelet/nodelet)
depth_metric_rect (nodelet/nodelet)
depth_points (nodelet/nodelet)
depth_rectify_depth (nodelet/nodelet)
depth_registered_sw_metric_rect (nodelet/nodelet)
disparity_depth (nodelet/nodelet)
disparity_registered_sw (nodelet/nodelet)
driver (nodelet/nodelet)
ir_rectify_ir (nodelet/nodelet)
points_xyzrgb_sw_registered (nodelet/nodelet)
register_depth_rgb (nodelet/nodelet)
ROS_MASTER_URI=http://localhost:11311
I did find similar errors in some issues, but no one's error like undefined symbol: _ZN2cv6String10deallocateEv), and librealsense_camera_nodelet.so exists in the folder... After check the difference between R200 and LR200, i'm not sure if the error is caused by wrong sensor type? i shouldn't use launch file of r200 but of lr200? For the sensor LR200, i found this issue #245, but i'm still confused about how i should change the files in realsense-ros folder.. Could you give me more details?
OR maybe it's not the reason, there are still other problems?
Really looking forward to any response and appreciate for your help in advance!!!
System Configuration
The text was updated successfully, but these errors were encountered: