iCUE and Commander Pro - Fans not showing up

So my commander pro does not always show my fans as available to control. I haven't changed anything in my hardware to cause this - they just started sort of blinking in and out in the UI and not they do not show up at all.

 

The firmware is up to date. The only items I see in the Commander Pro list is graphing, lighting setup, lighting channel 1 and 2. The Performance tab pops up every now and then, with only 2 fans available, and then blinks away.

 

Any ideas?

 

Edit - my most recent log may show some issues but I do not know how to read it!

 

2020-04-04T18:09:15 I cue.init: iCUE version: 3.27.68
2020-04-04T18:09:15 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V3/
2020-04-04T18:09:15 I cue.init: Build type: Public Release
2020-04-04T18:09:15 I cue.init: Applicaiton ID: 29304
2020-04-04T18:09:15 W cue.locale: Cannot find dir for qt *.qm files
2020-04-04T18:09:15 I cue.init.font: Using Regular text font family: "Open Sans"
2020-04-04T18:09:15 I cue.init.font: Using Title text font family: "Gotham Bold"
2020-04-04T18:09:16 I cue.hid_device_detector: Start worker thread.
2020-04-04T18:09:16 I cue.devices.enum.hid: Leaving working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session disallowed.
2020-04-04T18:09:16 I cue.devices.enum.router: Leaving working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session disallowed.
2020-04-04T18:09:16 I cue.devices.enum.clink: Leaving working state.
2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/ASUS/asus_motherboard_plugin.dll"
2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "ASUS/asus_motherboard_plugin.dll"
2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/Lenovo/CUEPlugin.dll"
2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "Lenovo/CUEPlugin.dll"
2020-04-04T18:09:16 I cue.plugin: Trying to load library: "C:/Program Files (x86)/Corsair/CORSAIR iCUE Software/plugins/OriginPC/CUEOPCPlugin.dll"
2020-04-04T18:09:16 I cue.plugin: Library is loading, will check if it's plugin: "OriginPC/CUEOPCPlugin.dll"
2020-04-04T18:09:16 I cue.devices.enum.phost: Leaving working state.
2020-04-04T18:09:16 W cue.plugin: Processing already finished
2020-04-04T18:09:16 W cue.plugin: Processing already finished
2020-04-04T18:09:16 W cue.plugin: Processing already finished
2020-04-04T18:09:16 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\skylined45\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder"
2020-04-04T18:09:16 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\skylined45\\AppData\\Roaming\\Corsair\\CUE/profiles/tree.cueprofileorder"
2020-04-04T18:09:16 I cue.actions.macro.win: Init time: 0.402395 (init: 1e-07 reset: 0.0019598 )
2020-04-04T18:09:16 I cue.devices.enum.dram: Leaving working state.
2020-04-04T18:09:16 I cue.ro_helpers: LLAccessIpcClient(0x1dd94c88) Start connecting to host QUrl("tcp://127.0.0.1:58508")
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 W cue.library: Lightings load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 I cue.ro_helpers: LLAccessIpcClient(0x1dd94c88) Successfully connected to host node at QUrl("tcp://127.0.0.1:58508")
2020-04-04T18:09:16 W cue.library: Actions load failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:16 I cue.llaccess: Controller 0 : Bus capabilities: 7 Max block size: 32
2020-04-04T18:09:16 I cue.llaccess: Northbridge: Intel Coffee Lake
2020-04-04T18:09:16 I cue.llaccess: Southbridge: Z390
2020-04-04T18:09:16 I cue.llaccess: Slot count: 4
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 W QObject::disconnect: Unexpected null parameter
2020-04-04T18:09:16 I cue.session: Locked changed to false
2020-04-04T18:09:16 I cue.session: Local changed to true
2020-04-04T18:09:16 I cue.session.win: Will notify 'connected changed to' with delay
2020-04-04T18:09:17 I cue.hw_profile.manager: Start worker thread.
2020-04-04T18:09:17 C cue.button_content_storage: "Loading of devices properties failed!" Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:17 C cue.button_content_storage: "Loading of library property failed!" Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:17 C cue.buttons_lib: "Loading of buttons library failed!" Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:17 W cue.screens.data_provider: Widget data storage failed: Could not detect cereal root node - likely due to empty or invalid input
2020-04-04T18:09:17 I cue.core.init_ui: Starting UI.
2020-04-04T18:09:17 W QObject::connect(MobileServerSettingsModel, ProgramSettingsModel): invalid null parameter
2020-04-04T18:09:19 W qrc:/qml/delegate/MarkLinedAssignmentListDelegate.qml:22:23: Invalid property assignment: int expected - Assigning null to incompatible properties in QML is deprecated. This will become a compile error in future versions of Qt.
2020-04-04T18:09:19 W MainWindow_QMLTYPE_560(0x2c3ffeb0) must be a top level window.
2020-04-04T18:09:19 W MainWindow_QMLTYPE_560(0x2c3ffeb0) must be a top level window.
2020-04-04T18:09:19 W Model size of -1 is less than 0
2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile
2020-04-04T18:09:20 W qrc:/qml/ui/assignment/HorizontalTouchScreenAssignmentView.qml:153: TypeError: Cannot read property 'activeItemIndex' of null
2020-04-04T18:09:20 W qrc:/qml/ui/TouchscreenElementsInfo.qml:89:2: QML ColumnLayout: Possible anchor loop detected on vertical anchor.
2020-04-04T18:09:20 W qrc:/qml/ui/accordion/ButtonsLibraryAccordionItem.qml:258:2: QML Connections: Cannot assign to non-existent property "onCurrentIndexChanged"
2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile
2020-04-04T18:09:20 W libpng warning: iCCP: known incorrect sRGB profile
2020-04-04T18:09:20 I cue.session: Connected changed to true
2020-04-04T18:09:20 I cue.sdk: Entering working state, session connected.
2020-04-04T18:09:20 I cue.sdk: Starting router.
2020-04-04T18:09:20 I cue.sdk.device_watcher: Start prepare RestoreDeviceOrderState
2020-04-04T18:09:20 I cue.sdk.device_watcher: Finish prepare RestoreDeviceOrderState
2020-04-04T18:09:20 I cue.clink.device.hw_lightings: Working state about to change, lock hw lights preview.
2020-04-04T18:09:20 I cue.sdk.automation.server: User session about to be unlocked. Starting a listening
2020-04-04T18:09:20 I cue.sdk.automation.server: Successfully started listening
2020-04-04T18:09:20 I cue.devices.enum.hid: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed.
2020-04-04T18:09:20 W cue.hid_device_detector: Device detector already disabled.
2020-04-04T18:09:20 I cue.devices.enum.router: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed.
2020-04-04T18:09:20 I cue.devices.enum.clink: Entering working state.
2020-04-04T18:09:20 I cue.devices.enum.phost: Entering working state.
2020-04-04T18:09:20 I cue.devices.enum.dram: Entering working state.
2020-04-04T18:09:20 I cue.clink.device.hw_lightings: Entering working state, unlock and disable hw lights preview.
2020-04-04T18:09:20 C cue.plugin.aura_sdk_controller: Failed call to create instance of AuraSdk with HRESULT: "0xFFFFFFFF80040154"
2020-04-04T18:09:20 I cue.plugin: Received deviceStatusChanged
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=c76, pid=161f) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=424, pid=274a) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c10 ignored by HidDeviceEnumerator
2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c0b ignored by HidDeviceEnumerator
2020-04-04T18:09:20 I cue.devices: Device vid=1b1c pid=c0b ignored by HidDeviceEnumerator
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=46d, pid=c52b) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=48d, pid=8297) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=48d, pid=8297) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d8, pid=eed2) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=4d9, pid=a0f8) not found.
2020-04-04T18:09:20 I cue.devices: Manifest for device (vid=262a, pid=1100) not found.
2020-04-04T18:09:21 I cue.devices.dram: Module created (0:58) CMW32GX4M2C3200C16 Slot:  0
2020-04-04T18:09:21 I cue.devices.dram: Module created (0:59) CMW32GX4M2C3200C16 Slot:  1
2020-04-04T18:09:21 I cue.devices.dram: Module created (0:5a) CMW32GX4M2C3200C16 Slot:  2
2020-04-04T18:09:21 I cue.devices.dram: Module created (0:5b) CMW32GX4M2C3200C16 Slot:  3
2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:58]"
2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:59]"
2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:5a]"
2020-04-04T18:09:21 I cue.devices.dram.pro: Choosing v4 block implementation for: "Dram [0:5b]"
2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::SetDpiBrightnessLevel
2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetAutoDetectedLedChannelTypes
2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetConnectedLedChannelCounts
2020-04-04T18:09:21 W cue.devices.dram: Unsupported command in DramPhysicalDevice: AbstractCommand::GetLightingMode
2020-04-04T18:09:21 I cue.sdk.device_watcher: Dram counts: 4 ; Serial: "vid<1b1c>pid<000004>serial<VENGEANCERGBPRO>index<0>"
2020-04-04T18:09:21 I cue.lightings.direct_player: Started lighting worker in 0x1b88
2020-04-04T18:09:21 I cue.devices: Device insertion processing complete for VENGEANCE RGB PRO (vid=1b1c, pid=403)
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode
2020-04-04T18:09:21 I cue.lightings.direct_player: Started lighting worker in 0x2850
2020-04-04T18:09:21 I cue.devices: Device insertion processing complete for Lighting Node Pro (vid=1b1c, pid=c0b)
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts
2020-04-04T18:09:21 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode
2020-04-04T18:09:22 I cue.lightings.direct_player: Started lighting worker in 0x1a74
2020-04-04T18:09:22 I cue.devices: Device insertion processing complete for Commander Pro (vid=1b1c, pid=c10)
2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::SetDpiBrightnessLevel
2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetAutoDetectedLedChannelTypes
2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetConnectedLedChannelCounts
2020-04-04T18:09:22 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::GetLightingMode
2020-04-04T18:09:22 I cue.lightings.direct_player: Started lighting worker in 0x15f4
2020-04-04T18:09:22 I cue.devices: Device insertion processing complete for Lighting Node Pro (vid=1b1c, pid=c0b)
2020-04-04T18:09:22 W cue.devices.enum.demo: Registration of device with unsupported DemoUsbId:  (vid=0, pid=0)
2020-04-04T18:09:22 I cue.sdk.device_watcher: Start prepare WorkingStateState
2020-04-04T18:09:22 I cue.sdk.device_watcher: Finish prepare WorkingStateState
2020-04-04T18:09:22 C cue.firmware.index: Skipping package: "VENGEANCERGBPRO" requires other version of CUE: QJsonValue(string, "<3.24") current is: 3.27.68
2020-04-04T18:09:22 I cue.firmware.index: "VENGEANCE RGB PRO" no newer FW version was found, selecting package with maximal verion
2020-04-04T18:09:22 I cue.firmware.index: "VENGEANCE RGB PRO" no newer FW version was found, package: QJsonObject({"integrity":"sha512-CrrQmeGiZTuy5TEx/IOj3vDVYLztlQUrf7fodKm5xCYHRb6ldwci4N+t+cNxGUNQz4vtifbcYaiTYGm7fwYkIQ==","provides":{"application":"1.02.64"},"release-date":"2019-05-17T15:07:00.000Z","requires":{"software":">=3.24"},"source":"VENGEANCERGBPRO_pr4.zip","version":"2.0"})
2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image"
2020-04-04T18:09:22 I cue.firmware.index: "Lighting Node Pro" firmware update, expected version: 0.10.4 same version found, on device: bootloader: 3.0 firmware: 0.10.4
2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image"
2020-04-04T18:09:22 I cue.firmware.index: "Commander Pro" firmware update, expected version: 0.9.212 same version found, on device: bootloader: 0.5 firmware: 0.9.212
2020-04-04T18:09:22 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image"
2020-04-04T18:09:22 I cue.firmware.index: "Lighting Node Pro" firmware update, expected version: 0.10.4 same version found, on device: bootloader: 3.0 firmware: 0.10.4
2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<2>"
2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<3>"
2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<4>"
2020-04-04T18:09:23 W cue.devices.clink: "Sensor not found: vid<1b1c>pid<000c10>serial<BDD78854>index<0>senstype<Fan>sensindex<5>"
2020-04-04T18:09:23 C cue.devices: Unknown command in CLinkDeviceProtocolBase: AbstractCommand::CommitHwSettings
2020-04-04T18:17:52 W qrc:/qml/collection/ColorPicker.qml:42: TypeError: Cannot call method 'updateCurrentColor' of null
2020-04-04T18:17:52 W qrc:/qml/collection/ColorPicker.qml:48: TypeError: Cannot call method 'updateCurrentColor' of null
2020-04-04T18:17:52 I cue.models.present_device: Lighting mode changed to SW for "VENGEANCE RGB PRO"
2020-04-04T18:17:52 W qrc:/qml/ui/settings/DeviceSettings.qml:233:7: Unable to assign [undefined] to double
2020-04-04T18:17:52 W qrc:/qml/delegate/TabViewTabDelegate.qml:21: TypeError: Cannot read property 'top' of null

Edited April 4, 2020 by skylined45

I'm sorry I'm not able to read this log too, but to my experience when items in iCUE pop up and disappear is a power-related issue.

Do you use any SATA splitter to connect the CoPro SATA cable?

Did you try to change the USB 2.0 motherboard header for the CoPro USB cable?

Did you try a repair installation of iCUE? Sometimes it works better then uninstall/reinstall.

 

If you have run your system well for sometimes, I suppose you correctly configured the fans in Lighting Setup section.

 

Baio

I don't use any splitters and the commander pro is connected directed to a USB header on my motherboard, and powered by its own SATA connection. I just recently updated iCUE and that didn't fix; neither did a fresh uninstall/install.

Can you try a different USB header?

On my board there are 2 apparently identical headers, but if I use the first, only the CoPro shows up, using the second I can see also the AIO and the PSU.

If I was you, I’d try also a repair installation, no fear to loose your actual configuration.

 

Baio

Just bumping this - fans are plugged into the CoPro which is plugged directly into a USB header on my motherboard. I still do not have any fans showing up to edit a fan curve in my CoPro.

Bumping this - I removed HWInfo and the performance tab stays put now, but the compro is only recognizing 4 fans. Doesn't want to see anything plugged into port 3 or 5. I've set the pinout to 4-pin and auto; 4-pin at least shows the fans at 0 RPM, but auto doesn't show the fans at all.

 

I've narrowed it down to the compro not recognizing any fan connected to ports 3 and 5. I've removed all other connections from the compro - USB, LED fans on ports 1, 2, 4, 6, temp sensors - nothing seems to get ports 3 and 5 to recognize and control fans. Is it possible to just have 2 of the 6 fan control ports burn out?

Edited July 17, 2020 by skylined45

Bumping this - I removed HWInfo and the performance tab stays put now, but the compro is only recognizing 4 fans. Doesn't want to see anything plugged into port 3 or 5. I've set the pinout to 4-pin and auto; 4-pin at least shows the fans at 0 RPM, but auto doesn't show the fans at all.

 

I've narrowed it down to the compro not recognizing any fan connected to ports 3 and 5. I've removed all other connections from the compro - USB, LED fans on ports 1, 2, 4, 6, temp sensors - nothing seems to get ports 3 and 5 to recognize and control fans. Is it possible to just have 2 of the 6 fan control ports burn out?

 

You could try resetting the Commander Pro to see if this restores functionality of the offending fan ports (I've fixed a fan port on one of mine this way):

1. Ensure your PC running, unplug the SATA connection from the CoPro,
   
2. On the front of the CoPro, there is a small hole. Using a straightened paperclip or similar, press the reset button found in the hole described and whilst continuing to hold the reset button down, reconnect the SATA cable (three hands would come in useful here).
   
3. Release the reset button.
   

After a brief-ish period, the Commander Pro should be recognised by the system. Check ICUE and update the firmware as required.

running any other monitor software? hwinfo and such like?

You could try resetting the Commander Pro to see if this restores functionality of the offending fan ports (I've fixed a fan port on one of mine this way):

1. Ensure your PC running, unplug the SATA connection from the CoPro,
   
2. On the front of the CoPro, there is a small hole. Using a straightened paperclip or similar, press the reset button found in the hole described and whilst continuing to hold the reset button down, reconnect the SATA cable (three hands would come in useful here).
   
3. Release the reset button.
   

After a brief-ish period, the Commander Pro should be recognised by the system. Check ICUE and update the firmware as required.

 

Don't I risk frying the whole CoPro if I do this while power is on?

 

running any other monitor software? hwinfo and such like?

 

Nope, I uninstalled HWInfo completely and am not running any others in the background, though a few are currently installed. I'd be more inclined to think it was software related if it wasn't specifically ports 3 and 5 that aren't recognizing fans, no matter which fan is hooked up to them.

wait sorry... i must have miss read... this sounds like dead fan headers. open a support ticket buddy.

 

not saying you have but this can result from hot swopping

Don't I risk frying the whole CoPro if I do this while power is on?

 

<snip>

 

No, that's the procedure required for a hardware reset of the Commander Pro.

I was having the exact same problem. When I would open up iCUE I couldn't see any fans not could I see the performance tab. I figured it out, other temp and speed monitoring software such as HW were interfering with iCUE. As soon as I removed the other programs and restarted iCUE my performance tab came right back and I could see all my fans again.