Kinect resets after 10 seconds

Home Forums AR Sandbox Forum Kinect resets after 10 seconds

This topic contains 2 replies, has 2 voices, and was last updated by  eclipsegeo 1 month, 2 weeks ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #103046

    eclipsegeo
    Participant

    Thanks Oliver, for all the effort put into the Sandbox! We have a sandbox setup and are looking at using it for educational purposes. The Sandbox works well except for one problem, where the kinect seems to reset it self every 10 seconds. It’s difficult to run the sandbox with this problem as the Sandbox freezes after the first resest. We are running a Dell XPS13, Intel Core i5-7200U CPU 2.50 GHz x 4. The graphics is an Intel Kabylake G2.
    We have installed Ubuntu 16.04 LTS. The Kinect is a 1414 model run through a USB 2.0 port. The projector is a BenQ as recommended in the instructions.
    When running the lsusb command, I can see the kinect motor, camera, and audio until the device resets itself, then it seems to drop the camera and audio connections momentarily, and then pick them back up again about a second later.

    I did have once successful run with the Sandbox yesterday where the kinect did not freeze, but I have no idea why it worked as I don’t recall doing anything different. Has anyone run into this problem before? Thanks,

    #103068

    Oliver Kreylos
    Moderator

    Not sure, but this sounds like a cable or power issue. Check that the connection between the Kinect’s proprietary cable and the USB/AC adapter is tight, and ideally try another cable if you have one.

    #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.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Comments are closed.