The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Try increasing initMemoryPool(4). This will allocate more frame buffers.
The call to is_WaitEvent() is set to timeout after 2*frame_rate. Either decrease your frame rate or increase the timeout.
Play around with the pixel_clock parameter. This affects how the uEye camera interacts with the USB bus.
Have you tried visualizing the uEye camera with the manufacture's demo program while also visualizing the OpenNi camera in ROS? This would eliminate either the ueye ROS driver or the manufacture's driver as the problem.
| | 2 | No.2 Revision |
Try increasing initMemoryPool(4). This will allocate more frame buffers.
The call to is_WaitEvent() is set to timeout after 2*frame_rate. Either decrease your frame rate or increase the timeout.
Play around with the pixel_clock parameter. This affects how the uEye camera interacts with the USB bus.
Have you tried visualizing the uEye camera with the manufacture's demo program while also visualizing the OpenNi camera in ROS? This would eliminate either the ueye ROS driver or the manufacture's driver as the problem.
Edit: Also, run ueyecameramanager in a separate tab. It will give 'camera removed' and 'camera connected' notifications.
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.
