Commander Pro "Operation timed out."

Hi

 

I've recently added a set of Corsair RGB fans & strips to an older PC. Full specs below.

Everything works as expected, most of the time. But once in a while, the fan-speed control elements are missing in Link. I've tried attaching some images showing how the fan speed elements simply go missing.

 

In the Link "Service_Error.log" file I see this over and over again:

 

2018-07-20 14:57:18.4838 | 4 | SIMON | 4.9.7.35 | DevicesMonitor | -> 
CorsairLink4.Module.ProDevices.Common.Exceptions.ProDeviceException: No response ---> System.TimeoutException: Operation timed out.
  ved HidSharp.Platform.Windows.NativeMethods.OverlappedOperation(IntPtr ioHandle, IntPtr eventHandle, Int32 eventTimeout, IntPtr closeEventHandle, Boolean overlapResult, NativeOverlapped* overlapped, UInt32& bytesTransferred)
  ved HidSharp.Platform.Windows.WinHidStream.Write(Byte[] buffer, Int32 offset, Int32 count)
  ved HidSharp.HidStream.Write(Byte[] buffer)
  ved CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteOutputBufferBuilderData(ProDeviceOutputBufferBuilder builder)
  --- **** på staksporing af indre undtagelser ---
  ved CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteOutputBufferBuilderData(ProDeviceOutputBufferBuilder builder)
  ved CorsairLink4.Module.ProDevices.Common.ProDeviceHidCommunicationHandler.WriteAndRead(ProDeviceOutputBufferBuilder builder)
  ved CorsairLink4.Module.ProDevices.Common.ProDeviceDataProcessor.WriteLedGroupsClear(ProDeviceLedStripIndexType index)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.SetDefaultPresetEffect(ProDeviceLedStripIndexType ledStripIndex, LedStripMode mode, Byte brightness, Int32 groupCount)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.WriteDirect(ProDeviceLedStripIndexType ledStripIndex, List`1 parts, LedStripMode mode, Byte brightness)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.WriteChannel(ProDeviceLedStripIndexType ledStripIndex, List`1 parts, LedStripMode mode, Byte brightness)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.WriteChannels(List`1 firstParts, LedStripMode firstMode, Byte firstBrightness, List`1 secondParts, LedStripMode secondMode, Byte secondBrightness)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.HandleLed(Byte[] bytes)
  ved CorsairLink4.Module.ProDevices.Common.ProDevice.ProcessControlData(DeviceCommunicationData data)
  ved CorsairLink4.Module.ProDevices.Antigua.AntiguaDeviceComponent.ProcessControlData(DeviceCommunicationData data)
  ved CorsairLink4.Module.ProDevices.ProDevicesComponent.<InternalProcessControlData>d__11.MoveNext()
--- Af****ningen på staksporingen fra den tidligere placering, hvor undtagelsen blev udløst ---
  ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  ved CorsairLink4.Module.Common.BaseControlledComponent.<ProcessControlData>d__0.MoveNext()
--- Af****ningen på staksporingen fra den tidligere placering, hvor undtagelsen blev udløst ---
  ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  ved CorsairLink4.Service.Common.Utils.DeviceControlExtentions.<ProcessDeviceRequest>d__0.MoveNext()
--- Af****ningen på staksporingen fra den tidligere placering, hvor undtagelsen blev udløst ---
  ved System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
  ved System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
  ved CorsairLink4.Service.Common.Core.DevicesMonitor.<RunTask>d__29.MoveNext()

 

So it seems that when a timeout occurs contacting the Commander Pro, all fans go missing. The fans may re-appear on their own a few minutes later. Any ideas on how to troubleshoot the timeout issue further?

 

 

Setup:

Commander Pro, with 5 fans connected:

3 * LL120

CPU fan (Cooler Master Hyper 212 Evo stock fan)

Fractal Design Dynamic X2 GP-12 120 mm fan (3-pin)

 

All 5 fans are connected directly to the Commander Pro (using ports 1-4 and 6).

 

The 3 RGB fans are also connected to an RGB hub, which is then connected to the Commander Pro on RGB port 2.

There are also 4 Corsair RGB strips, which are serially connected, and connected to RGB port 1 on the Commander Pro.

 

 

PC spec (2012 build with a few upgrades along the way):

Motherboard: Gigabyte GA-EX58-UD4P

CPU: Intel Core i7-920

RAM: OCZ Platinum 3 x 2 GB

GPU: ASUS Strix GTX 970 OC 4GD5

OS: Windows 10 Enterprise 1803 Build 17134.167

 

Corsair LINK version: 4.9.7.35

 

Corsair Commander PRO

Firmware version: 0.8.210

Bootloader version: 0.5

That typically happens when another piece of software is also accessing the Commander Pro. Do you have anything running that also reads the CoPro values? HWInfo perhaps?

Thanks. I had SpeedFan installed, but not running. It might have had some services running anyway though. Also have Asus GPU Tweak II installed (also not running), as well as Razers Synapse 2.

 

I've tried closing all services and apps that might be reading sensor/fan data, but nothing helps. Fans still come and go.

 

By tailing the "Service_Trace.log" file I notice that the fans seem to appear correctly when it logs "31 sens.", and disappear when it logs "36 sens.":

 

2018-07-29 09:45:09.7298 | 29 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:09.7298 | 29 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:10.7318 | 14 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:10.7318 | 14 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:11.7428 | 14 | INFO: DevicesMonitor | TIME = 1009(avg: 1000) ms 
2018-07-29 09:45:11.7428 | 14 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:12.7468 | 32 | INFO: DevicesMonitor | TIME = 1002(avg: 1000) ms 
2018-07-29 09:45:12.7468 | 32 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 09:45:13.7498 | 12 | INFO: DevicesMonitor | TIME = 1001(avg: 1000) ms 
2018-07-29 09:45:13.7498 | 12 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 09:45:14.7518 | 13 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:14.7518 | 13 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 09:45:15.7578 | 20 | INFO: DevicesMonitor | TIME = 1004(avg: 1000) ms 
2018-07-29 09:45:15.7578 | 20 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 09:45:16.7598 | 20 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:16.7598 | 20 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:17.7627 | 29 | INFO: DevicesMonitor | TIME = 1001(avg: 1000) ms 
2018-07-29 09:45:17.7627 | 29 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:18.7647 | 34 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:18.7647 | 34 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 09:45:19.7667 | 5 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 09:45:19.7667 | 5 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

The "Operation timed out" messages occur much less frequently than the fans appearing and disappearing, but they do occur:

 

2018-07-29 10:06:41.7320 | 26 | INFO: DevicesMonitor | TIME = 1016(avg: 1000) ms 
2018-07-29 10:06:41.7320 | 26 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 10:06:42.7360 | 5 | INFO: DevicesMonitor | TIME = 1001(avg: 1000) ms 
2018-07-29 10:06:42.7360 | 5 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 10:06:43.7389 | 28 | INFO: DevicesMonitor | TIME = 1001(avg: 1000) ms 
2018-07-29 10:06:43.7389 | 28 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 10:06:44.7539 | 5 | INFO: DevicesMonitor | TIME = 1012(avg: 1000) ms 
2018-07-29 10:06:44.7539 | 5 | INFO: DevicesMonitor | Devices: 7(31 sens.) 

2018-07-29 10:06:45.3349 | 20 | FATAL: DevicesMonitor | -> An exception CorsairLink4.Module.ProDevices.Common.Exceptions.ProDeviceException (No response) has occurred. Please see the errors log file for details.
2018-07-29 10:06:45.7659 | 19 | INFO: DevicesMonitor | TIME = 1009(avg: 1000) ms 
2018-07-29 10:06:45.7659 | 19 | INFO: DevicesMonitor | Devices: 5(22 sens.) 

2018-07-29 10:06:46.7689 | 27 | INFO: DevicesMonitor | TIME = 1000(avg: 1000) ms 
2018-07-29 10:06:46.7689 | 27 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 10:06:47.7719 | 26 | INFO: DevicesMonitor | TIME = 1001(avg: 1000) ms 
2018-07-29 10:06:47.7719 | 26 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

2018-07-29 10:06:48.7829 | 20 | INFO: DevicesMonitor | TIME = 1009(avg: 1000) ms 
2018-07-29 10:06:48.7829 | 20 | INFO: DevicesMonitor | Devices: 7(36 sens.) 

None of those packages typically cause an issue ... that I've heard, at least.

 

Odd, to say the least. I'm out of ideas at the moment except, perhaps, your USB drivers. But it's unlikely that they've been updated.