![]() D:\x\sdk\k4a.c (269): capturesync_get_capture(device->capturesync, capture_handle, timeout_in_ms) returned failure in k4a_device_get_capture() Queue "Queue_capture" waiting for blocking call to complete. Queue "Queue_capture" stopped, shutting down and notifying consumers. D:\x\capturesync\capturesync.c (200): capturesync_add_capture(). Pipeline propagate error to callback: 0x800700c1 D:\x\color\mfcamerareader.cpp (1126): OnReadSample(). D:\x\deloader\deloader.cpp (51): verify_plugin(). Depth Engine loaded C:\Program Files\Azure Kinect SDK v1.4.0\tools\depthengine_2_0.DLL D:\x\dynlib\dynlib_windows.c (131): dynlib_create(). Starting camera's with the following config. D:\x\depth\depth.c (253): Signature type: MSFT D:\x\depth\depth.c (248): Build type: Release D:\x\usbcommand\usbcommand.c (224): populate_serialnumber(). D:\x\usbcommand\usbcommand.c (343): find_libusb_device(). Else, maybe some sort of dependency issue? I'd think uninstalling and reinstalling or repairing would handle that. No warnings or fishy looking USB items though. I'm wondering if it's a USB controller issue as I once got a "not enough USB controller resources" error when I had a few too many things plugged in. I've been hitting my head against this for a while, so hoping someone has seen this before. Nothing of note in the system Event Viewer either. Tried updating the firmware of the camera (it was on the version that shipped w/ 1.3), reset the camera w/ the paperclip trick, uninstalled/reinstalled and repaired the SDK too. I tried different USB ports (it's currently on a dedicated 3.1 port with external power), checked device manager for weirdness with no changes. If I only select microphone in the Azure Kinect Viewer, the sound shows up. The camera also no longer works in the Windows Camera application. The Ros_driver node is stable most of the time, but sometimes these unexpected errors will kick in randomly.I've been working with the SDK for a couple months and with the 1.4 release for a few weeks, but recently started getting this error when running either my code OR the Azure Kinect Viewer. Is there anyway to solve this? or maybe raise an exception under the ros_driver when this happen, to make sure the node is able to recover soon after the TS is back in synced? However sometimes it will also happen while the gpu usage is still low. ![]() As error will happen occasionally, I not able to reproduce it.Īccording to some previous this raised issue: ![]() When this error msg happens, it is not possible to recover, in which a forceful restart of the node is needed. ![]() capturesync_drop, releasing capture early due to full queue TS: 1186877 type:Depth src/capturesync/capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS: 986877 type:Depth capturesync_drop, releasing capture early due to full queue TS: 786877 type:Depth capturesync_drop, releasing capture early due to full queue TS: 594122 type:Depth src/capturesync/capturesync.c (142): replace_sample().
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |