12/19/2023 0 Comments Kinect for windows usb audio error![]() ![]() Asus Intel Core i7-7500U, up to GHz, 12 Gb RAM, HDD 1 Tb, Nvidia Geforce 940MX, OS as Free DOS and under UEFI. Sorry, I forgot to mention laptop and some specs: Just ROS, freenect_camera, launch and openni_camera and launch, and obviously another packages I'm working with like rosserial, navigation, nav2d, teleoptwistkeyboard, etc. This time I haven't installed OpenNI, nor SensorKinect, and similar things related to interfacing with kinect. A crashing report that probably will make a new one pops up next time I restart ubuntu. 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.Īnother symptom I've always had just after killing freenect_launch or openni_launch is this one from imgur. Xbox NUI Motor, but not always the three of them, even after formating. I mean, it recognizes the three sources Microsoft Corp. Xbox NUI Camera by typing lsusb on terminal repeatedly. After that I noticed that like 5% of time, data transmission from kinect doesn't recognize Microsoft Corp. So I had a huge kinect compatibility and drivers interface problem after installing openni_camera. I solved it partially by reinstalling ubuntu with dualboot again and making new supply circuit according to kinect powering. ![]() I couldn't do that as a normal user cause it didn't let me.Īfter that, openni and freenect started getting worse and now I'm unable to launch correctly both of them. So I followed the steps from here and here which are practically the same, and managed installing those but unfortunately as a super user. At first I started using that without OpenNi unstable nor SensorKinect, cause I didn't noticed that at the end from openni_camera documentation it was needed to have the kinect working properly. By the way everytime I started freenect_launch this message appeared at the end Stopping device RGB and Depth stream flush (after the typical calibrations warns, the ones that tell you haven't calibrate your camera), what does that mean? is it irrelevant?īecause of that, I started using openni_launch and I had the same issues that freenect_launch, but rarely. I'm working with depth sensor so I'm also using depthimage-to-laserscan package, with the following parameters I think should be fine: Īnother common error I got like these. And supplied by the following ros document kinect supply.on port USB 2.0 cause I know it has some tricky behavior with transfer rates.I'm using kinect V1 model 1414, under ros-kinetic and obviously freenect-camera and openni-camera.I don't know what could be wrong with freenect_launch or if it's on my kinect or something I missed, but everything should work fine. Or the kinect device is not connected and turns out that I have to restart the laptop in order it recognizes kinect. For example, when I was using freenect_launch everything seemed work fine most of time, but I noticed every time I used that group of nodes, more common I got camera/camera_nodelet_manager errors, or such as escalating to SIGTERM | escalating to SIGTERM or a Sorry, the application nodelet has stopped unexpectedly (which turns out on a log file error at startup every time I turn on my laptop, fortunately I managed to erase those logging errors). I mean, I got good results when I mapped a close indoor room, but always getting some kind of error for openni and freenect I never understood and which sometimes get solved by restarting my laptop. The thing is, I tried several ways to have the most stable data transmission between rgb and depth sensors through ros without sucess. I'm struggling with those nodes for connecting to my kinect. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |