Revision history [back]

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. But I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. But I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. But So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. AFter that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. AFter After that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. After that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

------------EDIT 1----------------

Hey guys, I noticed the usb 2.0 and 3.0 data transfer is veeeeery slow. I've got used to that, but that must be the problem! My laptop have an uefi mode, not like most of BIOS systems, so if I managed to set it correctly for a normal or better usb data transmission, maybe this problem is solved.

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. After that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

------------EDIT 1----------------

Hey guys, I noticed the usb 2.0 and 3.0 data transfer is veeeeery slow. I've got used to that, but that must be the problem! My laptop have an uefi mode, not like most of BIOS systems, so if I managed to set it correctly for a normal or better usb data transmission, maybe this problem is solved.

I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. After that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera, Microsoft Corp. Xbox NUI Audio and Microsoft Corp. Xbox NUI Motor, but not always the three of them, even after formating.

I think it's goona work fine most of time since now, but I want it to work properly and without concerning about how much time I have left before it starts behaving wrong and having every time more conflicts with camera/nodelet_camera.

Another symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. A crashing report that probably will make a new one pops up next time I restart ubuntu.

This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc.

Sorry, I forgot to mention laptop and some specs:

-Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI.

-It has installed dualtboot with Windows 10 at first and ubuntu 16.04.4 LTS.

-ROS Kinetic version.

-Two kinects, model 1414 which are in perfect conditions supposedly.

-In order to installing ubuntu I had to use usb2.0 and enable security mode and change some starting parameters which I don't remember at this moment, but I guess that doesn't matter, right?

Is there any clue to resolve this problem?

Thanks

------------EDIT 1----------------

Hey guys, I noticed the usb 2.0 and 3.0 data transfer is veeeeery slow. I've got used to that, but that must be the problem! My laptop have an uefi mode, not like most of BIOS systems, so if I managed to set it correctly for a normal or better usb data transmission, maybe this problem is solved.

------------EDIT 2----------------

I managed to improve usb transmission data through windows, and ubuntu inside BIOS, but that wasn't the problem. it has to be nodelet the problem. After installing all libfreenect dependencies, seems there is no longer any problems with usb transmission and lsusb always shows up three kinect components.

The problem definitely resides on camera/camera_nodelet_manager. Most of times I kill freenect camera nodes it shows this error .

I hope you can help me with that