how to use ueye_cam to drive my UI1221-m camera
hi all i have an ueye UI-1221-M camera and i am trying to use ueye_cam to drive it. i have installed the IDS driver and can use the driver to open the camera. when i use "roslaunch ueye_cam rgb8.launch" the erro comes as follow.
process[nodelet_manager-1]: started with pid [2384]
process[ueye_cam_nodelet-2]: started with pid [2385]
[ INFO] [1383891971.818538867]: Initializing nodelet with 4 worker threads.
[ERROR] [1383891971.834649094]: Failed to load nodelet [/ueye_cam_nodelet] of type [ueye_cam/include/ueye_cam_nodelet]: According to the loaded plugin descriptions the class ueye_cam/include/ueye_cam_nodelet with base class type nodelet::Nodelet does not exist. Declared types are asctec_autopilot/AutoPilotNodelet asctec_proc/AsctecProcNodelet depth_image_proc/convert_metric depth_image_proc/disparity depth_image_proc/point_cloud_xyz depth_image_proc/point_cloud_xyzrgb depth_image_proc/register image_proc/crop_decimate image_proc/debayer image_proc/rectify image_view/disparity image_view/image nodelet_tutorial_math/Plus pcl/BAGReader pcl/ExtractIndices pcl/NodeletDEMUX pcl/NodeletMUX pcl/PCDReader pcl/PCDWriter pcl/PassThrough pcl/PointCloudConcatenateDataSynchronizer pcl/PointCloudConcatenateFieldsSynchronizer pcl/ProjectInliers pcl/StatisticalOutlierRemoval pcl/VoxelGrid stereo_image_proc/disparity stereo_image_proc/point_cloud stereo_image_proc/point_cloud2 ueye_cam/ueye_cam_nodelet
[FATAL] [1383891971.834927628]: Service call failed!
[ueye_cam_nodelet-2] process has died [pid 2385, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load ueye_cam/include/ueye_cam_nodelet nodelet_manager __name:=ueye_cam_nodelet __log:=/home/uav/.ros/log/91855d0c-483e-11e3-9892-9c4e3647a14c/ueye_cam_nodelet-2.log].
log file: /home/uav/.ros/log/91855d0c-483e-11e3-9892-9c4e3647a14c/ueye_cam_nodelet-2*.log
* It seems that missing lib file how to deal with the problem? any help is appriciate*
[Update] Hi, thanks for your reply I have re-cloned the code and the error didn't disappear:
[ INFO] [1383981887.637572692]: Initializing nodelet with 4 worker threads.
[ERROR] [1383981887.726106300]: Failed to load nodelet [/ueye_cam_nodelet] of type [ueye_cam/ueye_cam_nodelet]: Could not find library corresponding to plugin ueye_cam/ueye_cam_nodelet. Make sure the plugin description XML file has the correct name of the library and that the library actually exists.
[FATAL] [1383981887.726402185]: Service call failed!
[ueye_cam_nodelet-2] process has died [pid 6465, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load ueye_cam/ueye_cam_nodelet nodelet_manager __name:=ueye_cam_nodelet __log:=/home/uav/.ros/log/fda46e70-490f-11e3-bba7-9c4e3647a14c/ueye_cam_nodelet-2.log].
log file: /home/uav/.ros/log/fda46e70-490f-11e3-bba7-9c4e3647a14c/ueye_cam_nodelet-2*.log
And i find problems when i build the package"rosmake ueye_cam" The MAKE process is really fast , i think many of the file did not MAKE correctly...
[ rosmake ] rosmake starting...
[ rosmake ] Packages requested are: ['ueye_cam']
[ rosmake ] Logging to directory /home/uav/.ros/rosmake/rosmake_output-20131109-153613
[ rosmake ] Expanded args ['ueye_cam'] to:
['ueye_cam']
[rosmake-0] Starting >>> catkin [ make ]
[rosmake-0] Finished <<< catkin ROS_NOBUILD in package catkin
No Makefile in package catkin
[rosmake-0] Starting >>> genmsg [ make ]
[rosmake-0] Finished <<< genmsg ROS_NOBUILD in package genmsg
No Makefile in package genmsg
[rosmake-0] Starting >>> genpy [ make ]
[rosmake-1] Starting >>> cpp_common [ make ]
[rosmake-2] Starting >>> genlisp [ make ]
[rosmake-3] Starting >>> gencpp [ make ]
[rosmake-0] Finished <<< genpy ROS_NOBUILD in package genpy
No Makefile in package genpy
[rosmake-1] Finished <<< cpp_common ROS_NOBUILD in package cpp_common
No Makefile in package cpp_common
[rosmake-1] Starting >>> rostime [ make ]
[rosmake-1] Finished <<< rostime ROS_NOBUILD in package rostime
No Makefile in package rostime
[rosmake-1] Starting >>> roscpp_traits [ make ]
[rosmake-1] Finished <<< roscpp_traits ROS_NOBUILD in package roscpp_traits
No Makefile in package roscpp_traits
[rosmake-1] Starting >>> roscpp_serialization [ make ]
[rosmake-0] Starting >>> rospack [ make ]
[rosmake-1] Finished <<< roscpp_serialization ROS_NOBUILD ...
@anqixu please help me with it
Your new run shows the correct nodelet type of ueye_cam/ueye_cam_nodelet rather than ueye_cam/include/ueye_cam_nodelet. Also, the default repo branch is for catkin, not rosmake. So either use catkin_make (groovy&up) or switch branch: git clone https://github.com/anqixu/ueye_cam.git --branch fuerte
hi anqixu thanks i am useing the groovy but i can't config the catkin_make (i'm new here), so i downloaded the fuerte code and it works with my ueye.
Hi anqixu. I'm using ROS hydro, compiling the package with catkin_make, but I still have the same problem: [ERROR] [1389397299.178431342]: Failed to load nodelet [/ueye_cam_nodelet] of type [ueye_cam/ueye_cam_nodelet]: Could not find library corresponding to plugin ueye_cam/ueye_cam_nodelet. Make sure the plugin description XML file has the correct name of the library and that the library actually exists. ------ The library exist and it is in the right path. How can I solve this problem?
@Vero: hmm that's very weird. try checking out the fuerte branch and compiling (with rosbuild). Please also confirm that under the path [catkin_ws]/devel/lib, you have the files libueye_cam_nodelet.so libueye_wrapper.so
The package ueye_came-fuerte compiles and runs. The hydro version still has a problem. I can confirm that under the path [catkin_ws]/devel/lib there are the files libueye_cam_nodelet.so libueye_wrapper.so
Since the libraries exist but are not getting found we need some more information to narrow it down. Can you please add the output of the following commands from the shell where your roslaunch invocation failed to your question? "rospack plugins --attrib=plugin nodelet | grep ueye" and "env | grep CMAKE_PREFIX_PATH" and "".
Since your CMAKE_PREFIX_PATH does not contain the path of your workspace it looks like that you have not sourced the workspace/devel/setup.bash file. Can you make sure to do that and try again?