Jump to content
Corsair Community

A couple issues with iCue and Commander Pro


Margucci
 Share

Recommended Posts

I have:

- 6x ML120 Pro RGB on one lighting node (controlled with the 6 PWM headers on the Commander Pro

- 1x ML140 Pro RGB on another lighting node (fan speed set by PWM mobo header)

- Water temperature sensor connected to mobo

- Windows 10 Pro 64-bit

- iCue 3.1.133

 

How it's set up:

- All lighting is controlled by the iCue software through the Commander Pro. I want them just set solid white.

- The 6xML120 Pro fans are connected to radiators and I want their speed to be controlled by the water temperature reading from the motherboard.

- The speed of the ML140 Pro is not adjusted by corsair software or hardware.

 

The Issues:

- When my System is under load the iCue software stops monitoring and adjusting fan speeds based on the water temperature reading. They will just stay at the same RPM as when the CPU was put under load. Thus before I run any stress tests or benchmarks I need to manually max out the fans because the software won't do it during the run.

- When I put the computer to sleep and then wake it again, the fans stop obeying the lighting effects I have set for them, but each in different ways. The three ML120 Pro's on my top rad have their lights turn off (these are connected to the first lighting node ports 4-6). The three ML120 Pro's on my front rad go rainbow (these are connected to the first lighting node ports 1-3). And the ML140 Pro still stays white, as it should be.

- Occasionally during PC use or resuming from sleep the fans are either spinning REALLY slow (currently they are set to 450RPM, and I would estimate that they are probably in the range of 300RPM), although the iCue is stating they are at the correct speed. Sometimes they are running above the speed they should be for a given temperature as well.

- This last one is more of a QOL improvement than anything. On the dashboard you are able to rename the sensor fields from your motherboard (for example). When you rename these on the dashboard, please have it also change in the rest of the application. For example, although I have changed the name of the temperature sensor 4 from the motherboard to "Water" this does not change on the sensor drop down list when you are creating a custom fan curve. in fact, the drop down list of the sensors is so narrow that for every one of my motherboard temperature sensors I just see "ASUSTeK COMPUT..." on every line. Thankfully the sensors are in numerical order so I can just count through them to select the correct one for my water temperature sensor. IMO two changes need to be made. The first being when you rename something on the dashboard, the same of the sensor should also change in the rest of the program. Or if that isn't possible, make the sensor drop down wider. even at the smallest possible width of the window, you could easily make it three times longer.

 

Overall, I like the direction the iCue software is taking. However, with the exception of my last issue, these problems severely limit the functionality of both the Commander Pro as well as iCue software. Although the RGB LED's having a mind of their own is annoying, it isn't going to impact performance and it doesnt take more than a minute to fix. The fan speed issue is of much more concern to me. I wanted to give this a try through the commander pro. However, if it is not resolved before full release I will need to get PWM splitters and control the fan speed through motherboard headers instead of the Commander Pro.

Link to comment
Share on other sites

For the fan speed issue, your best solution is to put that temp sensor on the Commander Pro (CoPro)'s temp sensors. The same temp sensor that works with your motherboard will work with the CoPro (it's a standard 10K sensor). If the temperature source for the fan is one of the native, onboard sensors, it can be controlled by the hardware itself rather than requiring the software to control it. This should resolve the problem (it's how it worked in Link as well and I'm fairly certain that it works like this in iCue too). iCue and Link both have issues with software based control of both sensors and LEDs when under heavy load - I've noted and reported this as well.

 

This issue with the LEDs, this has to do with the hardware playback of LEDs. You'll see some progress on this front shortly. It may not be exactly what your looking for it it'll be a step forward. I believe that they are continuing to work this as well.

 

I'm totally with you on the width of the drop-downs.

Link to comment
Share on other sites

what would be amazing is if static lighting profiles could be saved to the commander pro just like you can store them on keyboards and mice. but that would be a hardware change. just something to keep in mind for the next revision of the commander pro.

 

thanks for the heads up on the temp sensor. i need to find some way to extend the cable in order to reach the commander pro. its just a standard 2 pin jumper like the power switch header for your motherboard. but i havent been able to find an extension

Link to comment
Share on other sites

Another thing I have noticed is the iCue application crashing after being minimized to the system tray. This is not after the system resumes from sleep or anything. You were using it fine. It minimized to the system tray. Later, you want to open it. You double click on the tray icon and nothing happens. You wait a few seconds and try again. As soon as your cursor moves over the icon it disappears and there is nothing in system processes. There was no error code. There is no problem opening it again.
Link to comment
Share on other sites

what would be amazing is if static lighting profiles could be saved to the commander pro just like you can store them on keyboards and mice. but that would be a hardware change. just something to keep in mind for the next revision of the commander pro.

 

thanks for the heads up on the temp sensor. i need to find some way to extend the cable in order to reach the commander pro. its just a standard 2 pin jumper like the power switch header for your motherboard. but i havent been able to find an extension

 

Something like this: http://www.xoxide.com/2-pinextensionfemaleplug-.html

 

You can also use jumper cables, like are used for breadboard development on Arduino/RasPi

Link to comment
Share on other sites

exactly like that. which amazon.ca doesnt seem to have. so then it comes down to what is easier, trying to track down and extension or just buy 2 PWM splitters that will be here tomorrow.....

 

well, performance-pcs has them and i need to order some stuff from there anyways

Edited by Margucci
Link to comment
Share on other sites

 Share

×
×
  • Create New...