Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running FanControl causes Elgato Facecam to disconnect and reconnect sporadically when the camera is idle. #1360

Closed
notthatwillsmith opened this issue Dec 12, 2022 · 3 comments

Comments

@notthatwillsmith
Copy link

Describe the bug
Running FanControl causes my Elgato FaceCam to disconnect and reconnect sporadically when it's idle, causing Windows to make the "device disconnected/device reconnected chimes". I'm running Windows 11 Pro.

When the camera is in use (OBS on, etc), it doesn't happen. I've confirmed that when FanControl is off, it doesn't happen. I'm using FanControl v.139, Elgato Cam Hub software is 1.5.0.801 and the camera firmware is v4.06. The only plugin I'm using with FanControl is the Liquidctl Plugin to pull liquid temps from my Kraken Z53.

Is there a log.txt file next to FanControl.exe with recent date entries?
The recent date entries are due to me removing and reinstalling the Kraken drivers, because I thought it was the culprit. Here's a representative entry, just in case.

` at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
12/11/2022 5:00:24 PM: Unhandled exception in FanControl v1.0.0.0
12/11/2022 5:00:24 PM: System.Exception: liquidctl returned non-zero exit code 1. Last stderr output:
WARNING: python -m liquidctl.cli is deprecated, prefer python -m liquidctl
ERROR: unexpected OS error with NZXT Kraken Z (Z53, Z63 or Z73): OSError('read error')

at FanControl.Liquidctl.LiquidctlCLIWrapper.LiquidctlCall(String arguments)
at FanControl.Liquidctl.LiquidctlCLIWrapper.ReadStatus(String address)
at FanControl.Liquidctl.LiquidctlDevice.LoadJSON()
at FanControl.Liquidctl.LiquidctlPlugin.Update()
at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Update()
at System.Collections.Generic.List1.ForEach(Action1 action)
at FanControl.Domain.ComputerAccessLayer.Update()
at FanControl.Domain.ApplicationClock.DoActions()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)`

Relevant hardware specs and setup
Motherboard is a ROG Maximum Z790 Apex, there are Fractal RGB Aspect fans plugged into the motherboard headers, and the cooler/AIO is a NZXT Kraken Z53 with nothing else plugged into it.

@Rem0o
Copy link
Owner

Rem0o commented Dec 12, 2022

Have you tried without the plugin? I do believe liquidctl uses usb stuff to communicate with various devices.

@notthatwillsmith
Copy link
Author

That seems like the culprit. Running FanControl without the liquidctl plugin for the last half hour didn't disconnect the camera. I'll repost over at the repo for the plugin.

@notthatwillsmith
Copy link
Author

FYI, I was able to fix this by using one of the USB 3.1 ports on the computer for the camera, vs the USB 3.2 ports. I believe the internal header the pump is connected to is on the USB 3.2 bus.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants