I am experiencing a very weird behavior or doing something completely wrong.
I run roslaunch kinect_nodelets.launch in terminal 1 and the kinect
nodelet driver seems to work just fine.
However, when I launch an attached file (taken from kinect_pcl/launch/
directory) in another terminal the nodelet driver all of suddenly
stops sending all data. So no point clouds, no images, no imu data.
Anyone with an idea what might have gone south?
On Sat, Nov 27, 2010 at 9:07 PM, Patrick Bouffard
<[hidden email]> wrote:
> I meant to reply to the list last time, see below.
> Anyway I'm just trying out the nodelets way now... Wow, kinect + PCL
> filters + dynamic_reconfigure + rviz = SWEET!
> On Fri, Nov 26, 2010 at 2:48 PM, Patrick Bouffard
> <[hidden email]> wrote:
>> Hi Radu,
>> On Fri, Nov 26, 2010 at 1:33 PM, Radu Bogdan Rusu <[hidden email]> wrote:
>>> You need to start the driver with kinect_nodelets.launch. That fires up a
>>> nodelet manager.
>> I just tried that with the same results. How would that be different
>> (aside from not having the static transform publishers) from using
>> kinect_w_tf.launch? In both cases isn't there a nodelet manager called
>>> I'll get some documentation and some examples on the wiki on how to run
>>> those launch files. They should work with CTurtle, however we are doing a
>>> lot of development in unstable, so if you're interested in the latest and
>>> greatest, you can checkout the svn unstable tag -- we are providing full
>>> support for that on the pcl-users@ mailing list.
>> I'll probably do that soon. I thought I'd do some of the initial
>> playing around with what I already have, though.
> Ros-kinect mailing list
> [hidden email] > https://code.ros.org/mailman/listinfo/ros-kinect >