- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi there,
Testing out the RealSense camera on current release of Windows 10 - 1.4 of the drivers.
Initially it functioned without issue (for about an hour). Detected by the OS without issue and set up (learn face etc.) worked without issue. Accessing the camera from Windows own Camera app was fine, worked perfectly.
After testing the camera a few times for accuracy - I'd lock the machine and test from there, it worked fine for the first few attempts and then I noticed a problem.
When I lock the machine (Windows Key + L) it seems that the OS temporarily "drops" the USB connection with the camera (I hear the USB disconnected sound for a moment and then I hear the USB connected sound seconds later) which renders the camera inaccessible on the login screen and so I have to login using a PIN instead.
When I do login, the camera is certainly there and accessible via the Windows Camera app.
I've tested this out 4-5 times now and the same thing happens each time. Lock the computer, connection to camera drops, "Looking For you" shows on the login screen but nothing happens.
I'd appreciate if someone could shed some light on what might be wrong and perhaps a solution?
Thank you,
Tom
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
http://www.pcauthority.com.au/News/335598,intels-upcoming-z87-chipset-has-an-annoying-usb-3-bug.aspx
Sounds similar to this bug... maybe a few firmware upgrades could fix it? Possible description of the fix below
http://www.tomshardware.com/news/Haswell-S3-Sleep-Problem-PCN,21896.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the response Philip.
Unfortunately this doesn't appear to be the cause.
I spoke to the manufacturer support and they have confirmed that the chipset isn't affected by this.
I've updated the chipset, ATK, USB either way and it hasn't made any different.
Tom
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem... Very disappointing since windows hello is why I night this camera.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I finally got it to work by upgrading my motherboard BIOS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I formatted the machine and freshly flashed the BIOS.
I was excited to see it was working again.
Then after several reboots - Dead again.
Now it won't even pick up the camera properly when I try to set Face recognition up, green light flashes on it for a second on camera, USB connect / disconnect sound and that's it.
Very disappointing experience.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You're right! Very very disappointing! But economize your nerves.
I've played this game (install, reinstall, updating, rebooting, downgrading, changing BIOS adjustments, refreshing drivers, etc) 2 month ever and ever and every day. Never anyone access! Other USB 3.0 devices are working fine.
I've asked for this problem by the manufacturers supports - even the same respons: The problem must solved by the device manufacturer Intel. Without correct drivers of your device it cannot work.
And Intel? The solution would be referred for ever and a day .... The number of disappointed users is growing from day to day! It's only an experience of patience! I am waiting ....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem with USB3... Sometimes the device is disconnected or not recognized....
Some idea how we can fix this problem??
Thank you in advance,
Manu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Exactly the same problem here. Have a new motherboard and Intel 6th generation chip. Was hoping to find a solution...damn.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
there are some "always on" settings in power management, have you tried that out?
also there are "some always on settings" in the bios. afaik those purple usb slots are always on 3.1 usb
i am using external usb 3.0 hub and this seems to cause no problem with r200
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
John H. wrote:
Exactly the same problem here. Have a new motherboard and Intel 6th generation chip. Was hoping to find a solution...damn.
John, try this : https://software.intel.com/en-us/forums/realsense/topic/632457#comment-1879602
And try Disabling "USB selective suspend setting" within Power Options -> Advanced :
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think I'm seeing the same thing. I'm using an F200 on Windows 10 with the Anniversary Update installed.
Every time something tries to use the depth camera, I get the unplug/replug noise, and the device fails. This is true both when Windows Hello tries to connect, and in GraphStudioNext. The driver is 1.4.27.52404, which is what Windows offers me.
RGB is fine, only depth has a problem.
It's possible that my processor is just too old or something.
![](/skins/images/7FC17B7B85029576C25F1E43CE255B51/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page