Open jeking04 opened 8 years ago
Actually, I forgot one other step we did: rosclean purge
. This seemed to do the trick now too. Perhaps we need to add something to do this regularly?
We should try upgrading libusb
, as per @DavidB-CMU's post on Slack:
I took a look at the Kinect2 setup on HERB's computer. I think a step was missed when installing the driver. This may explain why the libfreenect driver or the USB port drops-out sometimes. $ apt-cache show libusb-1.0-0 says libusb-1.0-0_1.0.17, which is around two years old. v19 was the recommended version last year, now the iai Kinect2 guys are recommending v20. There's instructions at the bottom of this thread: https://github.com/code-iai/iai_kinect2/issues/91 Because there are important demos this week, I did not upgrade anything. I will leave that as an exercise to the reader :wink:
Not sure this is the correct place for this issue...
Recently we are having issues with getting the kinect properly started. In particular, when running
on herb2 we see a spew of this error:
And then no depth data published:
Rachel and I experienced this earlier in the week and I am seeing it again now. The previous fix was to unplug/replug the USB into herb2 and then reboot the whole machine. This has not worked this time.
Note: A quick google of the error shows many people having this problem. Some of the proposed solutions might work for us. I didn't try because I don't think I know enough about how we have
herb2
setup.