Reply To: Kinect resets after 10 seconds

Home Forums AR Sandbox Forum Kinect resets after 10 seconds Reply To: Kinect resets after 10 seconds

#103084
eclipsegeo
Participant

thanks for your response Oliver. I’ve switched out the power cable for the kinect, and still running into the same issue. I also switched out the kinect 1414 with a different 1414 but no success. the lsusb command produces the following output:

eclipse@eclipse-XPS-13-9360:~/src/SARndbox-2.3$ lsusb
Bus 004 Device 002: ID 05ac:100e Apple, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 05ac:1460 Apple, Inc.
Bus 003 Device 002: ID 05ac:100f Apple, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0cf3:e301 Atheros Communications, Inc.
Bus 001 Device 045: ID 045e:02ae Microsoft Corp. Xbox NUI Camera
Bus 001 Device 041: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 001 Device 044: ID 045e:02ad Microsoft Corp. Xbox NUI Audio
Bus 001 Device 040: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 102: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

AND then about 10 seconds later, the output from the lsusb command:

eclipse@eclipse-XPS-13-9360:~/src/SARndbox-2.3$ lsusb
Bus 004 Device 002: ID 05ac:100e Apple, Inc.
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 05ac:1460 Apple, Inc.
Bus 003 Device 002: ID 05ac:100f Apple, Inc.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0cf3:e301 Atheros Communications, Inc.
Bus 001 Device 041: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor
Bus 001 Device 040: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 102: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Running the Sandbox in verbose mode produces the following output:
eclipse@eclipse-XPS-13-9360:~/src/SARndbox-2.3$ ./bin/SARndbox -uhm -fpv -vruiVerbose
Vrui: Entering verbose mode
Vrui: Run-time version 4.2-006 installed in:
libraries : /usr/local/lib/x86_64-linux-gnu/Vrui-4.2
executables : /usr/local/bin
plug-ins : /usr/local/lib/x86_64-linux-gnu/Vrui-4.2
config files: /usr/local/etc/Vrui-4.2
shared files: /usr/local/share/Vrui-4.2
Vrui: Reading system-wide configuration file /usr/local/etc/Vrui-4.2/Vrui.cfg
Vrui: Merging configuration file /home/eclipse/.config/Vrui-4.2/Vrui.cfg… does not exist
Vrui: Merging configuration file /usr/local/etc/Vrui-4.2/Applications/SARndbox.cfg… does not exist
Vrui: Merging configuration file /home/eclipse/.config/Vrui-4.2/Applications/SARndbox.cfg… does not exist
Vrui: Merging configuration file ./Vrui.cfg… does not exist
Vrui: Going to root section /Vrui/Desktop
Vrui: Initializing Vrui environment… Ok
Vrui: Command line passed to application: “-uhm” “-fpv”
Vrui: Unable to inhibit screen saver due to exception Vrui::ScreenSaverInhibitorDBus: Unable to inhibit screen saver
Vrui: Starting graphics subsystem…
Vrui: Opening window SARndbox from configuration section Window:
Unable to bypass the compositor; compositing may be disabled
Auto-detecting screen size as 11.5748×6.49606
Window position 1024×768+128+96, aspect ratio 1.33333
Panning domain 1152×864+0+0, aspect ratio 1.33333
Screen size 11.5748×6.49606, aspect ratio 1.78182
Refresh rate 59.9971
VRWindow::VRWindow: Vertical retrace synchronization requested but not supported
Vrui: Opened 1 window
Vrui: Graphics subsystem Ok
Vrui: Preparing main loop… Ok
Vrui: Entering main loop
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation
glPrintError: Invalid framebuffer operation

I’m trying to track down a kinect model 1473 or 1517 to see if that makes any difference. It appears others have had luck switching kinect models so it’s worth a try.

Comments are closed.