Skip to content
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.

Multiple sensors hard locks Intel NUC 12 Extreme system (NUC12DCMi9) #1950

Open
TomHVR opened this issue Sep 19, 2023 · 2 comments
Open

Multiple sensors hard locks Intel NUC 12 Extreme system (NUC12DCMi9) #1950

TomHVR opened this issue Sep 19, 2023 · 2 comments
Labels
Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members.

Comments

@TomHVR
Copy link

TomHVR commented Sep 19, 2023

Running two Azure Kinects in any configuration causes the system to hard lock after a few seconds with 3D viewing mode (USB-C to C, C - A with separate power or running of the usb ports of the system, with sync cable, without etc.) I have tested with the iGPU by itself and running with a discrete 1660 Super. I've disabled all hosts in device manager except the ones being used by the azures. I've tried to put them on the same controller, one on the 3.1 and second on 3.2 hosts. I've tried changing nvidia drivers from studio to game, I've tried without the nvidia driver. I've also disabled the iGPU in the bios (setting to Auto instead of Enable)

Running a single sensor in 3D mode doesn't lock up the system.

Windows 11 Build 22621
Latest SDK and Firmware from GitHub

@TomHVR TomHVR added Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members. labels Sep 19, 2023
@TomHVR
Copy link
Author

TomHVR commented Sep 19, 2023

Just tried a clean windows 10 install, exact same system lockup behaviour,

Tested the same azure kinects on different PC hardware (a laptop and a ryzen desktop) and confirm the cameras themselves function normally and without issue.

@TomHVR
Copy link
Author

TomHVR commented Sep 19, 2023

What only can be described as an extremely stupid solution through throwing shit at the wall:

using cablematters 3.0 extensions (20 feet) the lockup doesn't appear to occur.

I guess these extensions force the connection down to 3.0 instead of 3.1/3.2 and doesn't trigger whatever hardware fault is happening at the host. I am going to leave it running for an hour and see if it remains stable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Something isn't working Triage Needed The Issue still needs to be reviewed by Azure Kinect team members.
Projects
None yet
Development

No branches or pull requests

1 participant