Corsair Commander CORE XT not showing T Sensor or Fans in Hwinfo64. Help?

[sk417]

Hi all,

Hoping someone can help me out here... I've been using Hwinfo for quite some time to monitor and display (RTSS/Tray, etc) temps and RPMs, power, voltage, and all the good stuff that Hwinfo can do. Recently I picked up a Corsair Commander CORE (not Commander PRO) as a fan hub and T sensor due to my motherboard not having enough of either. The core is plugged directly into the motherboard's USB2.0 and all the fans into the core along with the temp sensor for my coolant temp. All fans are indexed to the T sensor. Hwinfo reads all the usual values from the drive, gpu, cpu, motherboard, DIMMs, etc, but it does not pick up the Commander Core XT, therefore it will not show my coolant temp or my fan RPMs. I can see both of them in iCue, but not in Hwinfo?

Would any of you kind people out there have any info to share regarding this device / topic, or ideas to try?I've received no support from any Corsair forums and no Google searches have helped or shown that others have had this issue. I'd love to use an Octo or something, but availability of the Octo is so sparse that it's not realistic. Thank you.

 

[Martin]

I'm sorry but we don't have information about the protocol used by this device so we don't know how to retrieve this information. And Corsair obviously won't tell as they don't cooperate with anyone and have no intention to support other tools (which is quite rare but it's their choice).

 

[Overclocking newcomer]

Hi all,

Hoping someone can help me out here... I've been using Hwinfo for quite some time to monitor and display (RTSS/Tray, etc) temps and RPMs, power, voltage, and all the good stuff that Hwinfo can do. Recently I picked up a Corsair Commander CORE (not Commander PRO) as a fan hub and T sensor due to my motherboard not having enough of either. The core is plugged directly into the motherboard's USB2.0 and all the fans into the core along with the temp sensor for my coolant temp. All fans are indexed to the T sensor. Hwinfo reads all the usual values from the drive, gpu, cpu, motherboard, DIMMs, etc, but it does not pick up the Commander Core XT, therefore it will not show my coolant temp or my fan RPMs. I can see both of them in iCue, but not in Hwinfo?

Would any of you kind people out there have any info to share regarding this device / topic, or ideas to try?I've received no support from any Corsair forums and no Google searches have helped or shown that others have had this issue. I'd love to use an Octo or something, but availability of the Octo is so sparse that it's not realistic. Thank you.

Did you solve this problem later

 

[Overclocking newcomer]

I'm sorry but we don't have information about the protocol used by this device so we don't know how to retrieve this information. And Corsair obviously won't tell as they don't cooperate with anyone and have no intention to support other tools (which is quite rare but it's their choice).

Hello, this is the response I received using the Chinese intelligent AI question answering software "deepseek". As a software professional, please take a look and consider whether it is feasible. I encountered the same problem as the author.
Q: Can the temperature monitoring function of the four temperature monitoring ports on the Pirate Ship Commander PRO hub be skipped and directly read using HWiNFO software, bypassing the ICUE software of the pirate ship
A: At present, the data from the four temperature sensor interfaces of the Commander PRO hub on pirate ships cannot be directly read through HWiNFO bypassing iCUE for the following reasons:

1. Hardware communication relies on iCUE
The Commander PRO hub of the pirate ship communicates with iCUE using a private USB protocol, and temperature sensor data is managed by the hub's MCU (microcontroller) and is not directly exposed as system standard sensors (such as SMBus or HID devices).

HWiNFO typically supports standard hardware sensors such as motherboards and GPUs, but for custom hardware from peripheral manufacturers (such as pirate ships), official SDK or reverse engineering support is required.

2. HWiNFO's support for pirate ship equipment
Some pirate ship equipment (such as power supply and partial water cooling) has been supported by HWiNFO through reverse engineering, but Commander PRO's temperature sensor interface still relies on iCUE.

In HWiNFO, sensor data from pirate ship equipment is typically displayed in:

Under the category of "Sensor" → "Corsair" or "USB device" (if detected).

If it is not displayed, it indicates that HWiNFO has not yet cracked the communication protocol of the device.

3. Possible alternative solutions
Plan A: iCUE+HWiNFO data sharing
Keep iCUE running in the background and allow it to read the temperature data of the hub normally.

Enable 'Shared Memory Support' in HWiNFO (Settings → Security and Interfaces → Check 'Corsair Link/Asetek Support').

Check if HWiNFO has obtained temperature data through iCUE's shared memory (usually displayed as "Corsair Commander PRO" or similar entries).

Option B: Virtual Sensor (Indirect Reading)
Use tools such as LibreHardwareMonitor or AIDA64 to attempt reading through iCUE plugin or shared memory, and then obtain it through HWiNFO's "external sensor" function.

Option C: Third party tools developed by the community
A few developers have attempted to reverse engineer the pirate ship protocol (such as the OpenCorsairLink project on GitHub), but Commander PRO's support is incomplete and stability is questionable.

Why can't iCUE be completely bypassed?
Encryption/Private Protocol: The pirate ship did not disclose the USB communication protocol of the hub, making it difficult for third-party tools to decode directly.

Hardware dependency: The firmware of the hub may require iCUE initialization before sending sensor data.

5. Alternative suggestions
Using the motherboard temperature sensor interface: If the motherboard has a 2-pin or 10k Ω thermistor interface, a third-party probe can be connected, and HWiNFO/AIDA64 can directly read it.

Feedback to HWiNFO developers: Request support for Commander PRO through the HWiNFO forum.

conclusion
At present, it is necessary to rely on iCUE to read the temperature sensor data of Commander PRO, and HWiNFO cannot bypass it directly. The best solution is to keep iCUE running and indirectly obtain data through HWiNFO's shared memory function. If completely abandoning iCUE is necessary, it may be necessary to switch to other hardware solutions.