Jump to content
Corsair Community

Commander Core not showing up. Icue only displaying Lighting Node Pro


Recommended Posts

Recently I upgraded my case to a new 5000D. In the process of doing this case swap I uncovered an issue. The commander controller that came with my H100I had 3 bad RGB connections. Ok no big deal. Ended up ordering a new commander CORE RGB & PWM fan controller. Got the part and replaced it and voila, my RGB to all fans works great... except now I have no control on the fan speeds. They are all going at full blast. Opened Icue and the commander doesnt even show up. All my fan RGB controls are listed under "lighting node pro".

 

Anyone have any insight to how I can fix this situation?

Link to comment
Share on other sites

1 hour ago, CTL said:

Ended up ordering a new commander CORE RGB & PWM fan controller.

A Commander Core?  Or a Commander XT?  The Commander Core that powers the AIO can be hard to source. How does the lighting node pro fit in to this?  That is a separate RGB only controller that used to come with ML-Pro and LL fans.

 

Device detection in CUE is all about the usb connection and motherboard. Is the new controller connected to the same port as the original?

Link to comment
Share on other sites

1 hour ago, c-attack said:

A Commander Core?  Or a Commander XT?  The Commander Core that powers the AIO can be hard to source. How does the lighting node pro fit in to this?  That is a separate RGB only controller that used to come with ML-Pro and LL fans.

 

Device detection in CUE is all about the usb connection and motherboard. Is the new controller connected to the same port as the original?

Yes it is a commander core. CW-8960071 to be exact. 

I have no idea how a lighting node pro fits into this tbh. That's just what shows up on my iCue software.

 

Yes it is connected to the same usb slot on the mobo as before. 

Link to comment
Share on other sites

Are you on the new CUE 5.2?  If f so, look under the “gear” for settings and software modules. Does it show a Commander Core?  Or does it show a lighting node Core?  
 

It may let you uninstall the false Lighting Node Pro module. See if a trash can appears on the end of the module bar. If not, first try a repair install of CUE by going to Windows Settings -> Installed programs -> corsair iCUE. Click under the three dots and select modify. Follow the directions for repair install.
 

Im not sure if that will completely remove the modules or not and we’re still learning how the new modular system works. There were a couple of hardware mismatch issues pre-release, but it was mostly RAM and mice/KB. I have not seen this publicly.  If this is CUE 4, try the same steps but that would then make this truly bizarre. 

Link to comment
Share on other sites

Since the last two updates of iCUE 5.2 is my Commander Core XT in a boot loop. It connects and disconnects every 20-30 sec.

The Issue doesnt shows up when iCUE isnt running or ive never got this before. So i assume that this is a iCUE 5.2 sided software problem.

Also the issue seems to be gone when i restart iCUE. Just want to let u know about it

Link to comment
Share on other sites

9 minutes ago, JohnnyCrank said:

Also the issue seems to be gone when i restart iCUE. Just want to let u know about it

Nevermind, problem isnt gone at all. After i start iCUE again the boot loop of my commander starts again

Link to comment
Share on other sites

On 6/3/2023 at 11:03 AM, c-attack said:

Are you on the new CUE 5.2?  If f so, look under the “gear” for settings and software modules. Does it show a Commander Core?  Or does it show a lighting node Core?  
 

It may let you uninstall the false Lighting Node Pro module. See if a trash can appears on the end of the module bar. If not, first try a repair install of CUE by going to Windows Settings -> Installed programs -> corsair iCUE. Click under the three dots and select modify. Follow the directions for repair install.
 

Im not sure if that will completely remove the modules or not and we’re still learning how the new modular system works. There were a couple of hardware mismatch issues pre-release, but it was mostly RAM and mice/KB. I have not seen this publicly.  If this is CUE 4, try the same steps but that would then make this truly bizarre. 

I am on the new CUE 5.2. 

I was unable to uninstall the lighting node pro module but I am still running into the same issue. The only fan speeds that can be controlled are the 2 for my AIO. 

The other 4 corsair fans cannot be controlled. Only RGB.

Im going to try and attach some screen shots to hopefully provide some insights

Screenshot 2023-06-05 124657.png

Screenshot 2023-06-05 124847.png

Screenshot 2023-06-05 124901.png

Screenshot 2023-06-05 124910.png

Link to comment
Share on other sites

OK, the Commander Core functions are there under the AIO device cover.  That is how it is suppose to look when the pump is connected and it's in "AIO mode".  No problem there since both pump top and Commander Core are detected.

 

RGB - Hardware Lighting tells the fans what to do when CUE is not running -- like boot, shutdown, BIOS, etc.  You can pick one effect and all fans will do the same thing.  For your normal use, go under the 8 LED series and LL RGB series sections.  Here you can add more complex software lighting effects for each group of fans.  This is what will show when you are using the PC in Windows/CUE running mode.  Lots more options here.  

 

The Commander Core and XT both use an auto-detect protocol for the PWM and the RGB side of the controller.  You can force the RGB side to re-run from within CUE, but if it is misses on the PWM side at boot, it turns off that header in the controls.  Try the following to force the Commander Core to re-detect the PWM side.  Shutdown the PC, then flip the PSU switch off.  For good measure, disconnect the power cable from the PSU and immediately reconnect it.  Wait 30-60 seconds, then PSU back on, and start up normally.  This should force the Commander Core to check each PWM port again.  

Link to comment
Share on other sites

On 6/3/2023 at 11:03 AM, c-attack said:

Are you on the new CUE 5.2?  If f so, look under the “gear” for settings and software modules. Does it show a Commander Core?  Or does it show a lighting node Core?  
 

It may let you uninstall the false Lighting Node Pro module. See if a trash can appears on the end of the module bar. If not, first try a repair install of CUE by going to Windows Settings -> Installed programs -> corsair iCUE. Click under the three dots and select modify. Follow the directions for repair install.
 

Im not sure if that will completely remove the modules or not and we’re still learning how the new modular system works. There were a couple of hardware mismatch issues pre-release, but it was mostly RAM and mice/KB. I have not seen this publicly.  If this is CUE 4, try the same steps but that would then make this truly bizarre. 

My Commander Core keeps showing up as a Lightning node Pro, ive removed it and repair installed twice now but it keeps coming back as lightning node. Any ideas what im doing wrong?

MSI z690 mobo btw

Link to comment
Share on other sites

4 hours ago, SpazzyGenius said:

My Commander Core keeps showing up as a Lightning node Pro

Are you sure about this?  The Commander Core should not show up as a device at all when it’s in AIO mode. You should see the pump AIO top like in the cue Home Screen picture above. Does the Lighting Node Core show up in addition to the AIO pump?  Or does the pump top disappear?

 

Did the other fans 1-4 show up for speed control in cooling after the power reset?

Link to comment
Share on other sites

Posted (edited)

No pump in home screen, plugins shows lightning node.  Fans nots spinning and rgbs flash red

image.thumb.png.57e3fc2c7b70f42c6bd8f76da7a8db2c.pngimage.png.1e5751a949d53cde89003620b2e9033f.png

Edited by SpazzyGenius
Link to comment
Share on other sites

Posted (edited)
52 minutes ago, SpazzyGenius said:

No pump in home screen, plugins shows lightning node.  Fans nots spinning and rgbs flash red

I have no idea what is going on here and this is the strangest issue I've seen in any of the CUE 5 builds.  Go to the CUE gear setting and turn on "debug logging".  Then go to the bottom of this page and start a Support Ticket through the main Corsair website.  Whatever this is, it needs to get back to the development team.

 

There were some product misidentifications in early builds, but there were in the UI only and did not affect functionality or even RGB control.  In those instances, the only thing that seemed to straighten it out was a full clean install with the registry clean out.  

https://help.corsair.com/hc/en-us/articles/360025166712-Perform-a-clean-reinstallation-of-the-Corsair-Utility-Engine-iCUE

 

There is a new build out today (5.3.102).  Hopefully this clears things up.  You can try the automatic install over and that takes zero time or effort, but in the prior issues the clean install was necessary to fix the improper UI identifications.  

Edited by c-attack
Link to comment
Share on other sites

  • 1 month later...
Posted (edited)

Maybe someone can help me with my problem and could something understand in my log: https://pastebin.com/Q7SgjBJj

Posted about this issues also here:

 

Edited by JohnnyCrank
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...