XD3 pump not detected by Commander Core XT/iCue on first boot

[Bingl]

Hi, I have a odd problem. I have a XD3 pump connected to fan port 6 of a Commander Core XT, and on first boot (after say 12 hours of computer being off) iCue does not show the the presence of the XD3, its like it not installed. I look at the pump and I can see it running (no ideal how fast, but its not at full speed based on noise and feel). So the pump will not be responding to the temp changes in my system.

The only way I have been able to get it detected is to turn off the computer for 10 sec and restart, then its all ok. One thing to note on this second boot I hear the fans and pump go high on start up then settle down, but I don't ever hear that on the first cold boot. Far as I can tell the sensor wire is plugged into the XT firmly (its a bit tight cause its squeezed into a ITX case)

It may be unrelated, but this only started to happen once I upgraded iCue to the latest 4.30.162 last month (had the full setup over 6 months now). Command Core XT is v1.3.54 (also an iCUE NEXUS v2.2.6.0 but I think thats unrelated, but I can use that to see if the pump is detected without having to open iCUE)

[c-attack]

The Commander Core and Commander XT run an auto-detect of both PWM and RGB port population at power on. Someone else was inquiring about this a few weeks back with the same combination. I suspect there is an issue with the auto-detect. The XD3 uses a delayed start (fraction of a second), something not uncommon for water pumps, but it might miss the PWM check. Flipping the PSU off and then back on forces the Com XT to do a full deep check on the next boot. That’s also why you hear everything max out for a moment. CUE version should not matter as this happens long before the program loads. Firmware changes to the Com XT could have an impact. 
 

When it loads without detecting the XD3, does the pump then max out or keep running its last known speed after CUE opens?

 

I think you should create a support ticket and send this issue in. 

Edited December 20, 2022 by c-attack

[Bingl]

22 hours ago, c-attack said:

When it loads without detecting the XD3, does the pump then max out or keep running its last known speed after CUE opens?

The pump seems to run at the last speed at the previous shutdown (currently set to 25% at its lowest value, which it may be at depending on the last thing I was doing before shutting down).

[c-attack]

Ok, that means the XD3 knows it’s on a header so the problem is not on that end. It appears to be a Commander XT issue. Maybe they can lengthen the detection window on power on. 

[Smokester]

On 12/19/2022 at 7:03 AM, Bingl said:

iCue does not show the the presence of the XD3

Are you using any other kind of monitoring software? Fan Control / HWinfo64 for example?   iCue apparently is notoriously bad at working with other monitors and in my specific case, with a Commander Pro, will either give inaccurate information or randomly change which inputs are connected/shown and often with unreal numbers when other monitoring software being used.

Possibly unrelated to your issue, but throwing it out there in case it helps.  GL 🙂

Edited December 22, 2022 by Smokester

[Bingl]

On 12/23/2022 at 5:40 AM, Smokester said:

Are you using any other kind of monitoring software? Fan Control / HWinfo64 for example?   iCue apparently is notoriously bad at working with other monitors and in my specific case, with a Commander Pro, will either give inaccurate information or randomly change which inputs are connected/shown and often with unreal numbers when other monitoring software being used.

Possibly unrelated to your issue, but throwing it out there in case it helps.  GL 🙂

No, no other monitoring software is launching on boot. I specificy when down the Corsair route to have only one piece of software for all monitoring/cooling/rgb solution, though not perfect is better that the others I've played with.