wytnyt Posted September 23, 2015 Share Posted September 23, 2015 I suspect they shoulda and they woulda if they coulda but constantly asking wont speed things up ;):,it's better to wait than have another release that got forced out the door ...like in evidence of other pushed releases I also suspect nothing would please them more than to have a proper release just for the sake of peaceful harmony... Link to comment Share on other sites More sharing options...
tmiland Posted September 23, 2015 Share Posted September 23, 2015 Are there any timeline to get this working? I just bought a CL Mini, and i am pretty much depending on it to control my fans. :) Link to comment Share on other sites More sharing options...
AlphaBravo Posted September 27, 2015 Share Posted September 27, 2015 Based on that info, when I get some time, I am going to plug my temperature sensor into the probe 4 slot and see if I can get the fans to respond based on that reported temperature. I finally moved my temperature probe over to the probe 4 slot (thanks for the info Ray). If the temperature sensor is in temp probe slot 4, I *can* get the fans to respond to a custom curve. So the obvious question is......why can't temp probe slots 1, 2, and 3 control the fans? Link to comment Share on other sites More sharing options...
red-ray Posted September 27, 2015 Share Posted September 27, 2015 So the obvious question is......why can't temp probe slots 1, 2, and 3 control the fans? There must be a bug in the CLCC firmware. When setting up the mode select register Sensor 4 is index 0 and I guess this is why it works, but the others are none zero and fail. The mode select register is also not correctly reported. For SIV I found it easy enough to do a software work-a-round for this firmware bug, but I assume CL does not do this. The correct solution is to fix the firmware and Corsair should have done this several months ago :mad:. I suspect if you had 2 x CLCC then CL could use CLCC-A Sensors 1, 2 and 3 to control the fans on CLCC-B :laughing:. Link to comment Share on other sites More sharing options...
red-ray Posted October 20, 2015 Share Posted October 20, 2015 I was wishfully hoping CL 3.2.5742 would have some new CLCC firmware that fixed this, but it did not. When are these issues scheduled to be fixed please? Link to comment Share on other sites More sharing options...
Corsair Employees Corsair Dustin Posted October 20, 2015 Corsair Employees Share Posted October 20, 2015 We're more or less at the mercy of the original hardware/firmware vendor, which is why this hasn't been updated. We're keeping on them. Link to comment Share on other sites More sharing options...
red-ray Posted November 20, 2015 Share Posted November 20, 2015 We're more or less at the mercy of the original hardware/firmware vendor, which is why this hasn't been updated. We're keeping on them. I feel no fix after 12 months is not acceptable. On what date will there be a fix? What actions are Corsair planning to ensure there are firmware fixes in sensible timescales? Link to comment Share on other sites More sharing options...
martyzzz Posted November 22, 2015 Share Posted November 22, 2015 Hey all, I have read this thread but i still dont understand if the commander mini works. I have seen that it doesnt work 100%. At this moment i have 4 fans in my PC appart frm my CPU fans (H100I), 3 intake in the front and 1 out in the back. These 4 fans are hooked up to a fan hub (which came in the NZXT H440 case) but i cant regulate them through my bios. The fanhub in my case is connected to CPU2 header but since its only a hub the fans are at 100% all the time. Im not planning to use the temp probes or anything on the commander mini i just want to hook up 4 (3 pin) fans to the commander to regulate the fans according to cpu/gpu temp through the link software. Can someone confirm the commander can do this? Thanks. Marty Link to comment Share on other sites More sharing options...
red-ray Posted November 22, 2015 Share Posted November 22, 2015 i just want to hook up 4 (3 pin) fans to the commander to regulate the fans according to cpu/gpu temp through the link software. That should work. You could use CLCC Temp 4, it's Temp 1->3 that don't work as they should. The CL software could work-a-round the firmware bugs, but it does not. Link to comment Share on other sites More sharing options...
martyzzz Posted November 22, 2015 Share Posted November 22, 2015 That should work. You could use CLCC Temp 4, it's Temp 1->3 that don't work as they should. The CL software could work-a-round the firmware bugs, but it does not. Hey thanks for the reply :) So your telling me that if im not going to hook up temp 1-4 i still can make all my fans spin slower? Im dont have to make complicated profiles based upon temp readings all over the case i just want my fans to spin slower when my pc is idling. When im gaming or doing other cpu/gpu intens stuff i want them to spin 100% and i think if the commander lets me i can just do this due to temps given by the motherboard, So am i correct here ? If yess ill order the commander mini for this purpose since i already have the HX100i CPU cooler and a HX1000 PSU. Should work nice with the link software. Cheers ! Link to comment Share on other sites More sharing options...
red-ray Posted November 22, 2015 Share Posted November 22, 2015 Yes, you should be able to do all you wish once you get a CL Mini. Link to comment Share on other sites More sharing options...
red-ray Posted December 20, 2015 Share Posted December 20, 2015 We're more or less at the mercy of the original hardware/firmware vendor, which is why this hasn't been updated. We're keeping on them. I feel no fix after 13 months is not acceptable. On what date will there be a fix? http://forum.corsair.com/forums/showthread.php?t=137364 also needs fixing. What actions are Corsair planning to ensure there are firmware fixes in sensible timescales? Link to comment Share on other sites More sharing options...
k3mist Posted January 11, 2016 Share Posted January 11, 2016 I feel no fix after 13 months is not acceptable. On what date will there be a fix? http://forum.corsair.com/forums/showthread.php?t=137364 also needs fixing. What actions are Corsair planning to ensure there are firmware fixes in sensible timescales? Hi Ray, I have the Corsair Commander and I wish I would have found these forums prior to purchase. However, water under the bridge. I am using SIV at this point because of the issues in CL. Hardware detection issues and it constantly resetting and adding all the devices over and over again with previous devices being inactive/blank not reporting anything. Which you then have to go through and delete. Plus other issues, like LED flicker, etc. I'm guessing I really don't need to explain any of this. Anyway, my question, is it possible to control the fan curve from different temp sensors using SIV? For example, the internal temp of my CPU to control the speed of the rad fans? I see SIV easily detects all temps, devices, fans, etc but I can not figure out how to "bind" these two separate controls, if its even possible. I read the directions on your site, etc, but can not find anything. Please let me know. Anyway, I really appreciate your work on SIV, its a life savor at the moment. Link to comment Share on other sites More sharing options...
red-ray Posted January 11, 2016 Share Posted January 11, 2016 Anyway, my question, is it possible to control the fan curve from different temp sensors using SIV? This is really a SIV question so see http://forum.corsair.com/forums/showthread.php?p=830342 Link to comment Share on other sites More sharing options...
red-ray Posted February 16, 2016 Share Posted February 16, 2016 We're looking into this for future versions, at this time we don't have an ETA on when it will be implemented. Adding 0 RPM and < 40% PWM support will require CLCC + H110i + H110iGT + H100i + H80i firmware changes. If firmware changes were not required I would have implemented support for this a long time ago. The Asetek cooler firmware can't be updated how do you propose to do this for Asekek based coolers? I feel no fix after 12 months is not acceptable. On what date will there be a fix? What actions are Corsair planning to ensure there are firmware fixes in sensible timescales? The firmware bugs specified in this thread have been outstanding for well over 12 months I feel these should have been fixed by now and need to be fixed first. Link to comment Share on other sites More sharing options...
red-ray Posted April 1, 2016 Share Posted April 1, 2016 The CL 4.2.2.27 release has failed to fix this issue. When might this be fixed? It was first reported on 20-Nov-2014 and it not being fixed 16 months later is to say the least rather poor. Link to comment Share on other sites More sharing options...
red-ray Posted May 13, 2016 Share Posted May 13, 2016 The CL 4.2.3.41 release has failed to fix this issue. When might this be fixed? It was first reported on 20-Nov-2014 and it not being fixed 17 months later is to say the least rather poor. I wonder does the Corsair CEO Andy Paul knows this has not been fixed after 17 months? It's about time he made a similar post to http://forum.corsair.com/v3/showthread.php?p=763184 about Corsair Link bugs that are not fixed in a timely manor. Link to comment Share on other sites More sharing options...
Starkinsaur Posted June 4, 2016 Share Posted June 4, 2016 Red-Ray, thanks for your efforts on this issue. It's nice to see there is someone who cares about this when the manufacturer clearly doesn't. I am having the same problem which renders this device a complete waste of money. Unfortunately Link version 4.2.3.41 fails to be able to communicate with the commander mini at all so I'm stuck using an old version (3.2.5742) where the fans can't be controlled... Corsair, the fact that you continue to market and sell this garbage is a disgrace. I used to regard Corsair as a quality brand, that is clearly no longer the case. For anyone who is thinking about buying any of this hardware; save yourself the time, expense and heart ache - buy from a respectable manufacturer instead. The advertising is false; the hardware does not provide the functionality they tell you it does because it's so very broken. Link to comment Share on other sites More sharing options...
red-ray Posted June 4, 2016 Share Posted June 4, 2016 Unfortunately Link version 4.2.3.41 fails to be able to communicate with the commander mini at all so I'm stuck using an old version (3.2.5742) where the fans can't be controlled... CL3 should work for the temp 4 input, see http://forum.corsair.com/forums/showthread.php?p=810730 CL 4.2.3.41 talks OK to my 4 x CLCC, but I obviously don't use CL4 to control them as I use my SIV utility. Have you checked the CL4 log file that is in C:\Users\All Users\CLink4\ to find out why it does not report your CLCC? It took be a couple of days to work-a-round the firmware bugs in SIV on 04-Feb-2015, but it would be far better if Corsair fixed the CLCC firmware bugs. Link to comment Share on other sites More sharing options...
mcr1878 Posted July 22, 2016 Share Posted July 22, 2016 The CL 4.2.3.41 release has failed to fix this issue. When might this be fixed? It was first reported on 20-Nov-2014 and it not being fixed 17 months later is to say the least rather poor. I wonder does the Corsair CEO knows this has not been fixed after 17 months? It's about time he made a similar post to http://forum.corsair.com/v3/showthread.php?p=763184 about Corsair Link bugs that are not fixed in a timely manor. Consumer protection law would tend to say that if the device is not working as advertised and is not going to be fixed (2 years) almost after that bug being reported Then theres an argument that its not performing as advertised. There's such a thing in the EU as the Unfair Commercial Practices Directive 2005/29/EC This device is advertised as: http://www.corsair.com/en-gb/corsair-commander-mini A New Level of Control Manage fan speeds individually, set up customized cooling profiles, or program fans to respond to changes in ambient temperature – the choice is yours. You can program lighting to relay critical system information, change the look of your system to provide an instant visual indicator of your selected cooling profile, or just have fun. And with Corsair Link Dashboard, you can do it all without opening your PC’s case. These fans are not obviously able to be controlled based on ambient temperatures; temperature probes attached to the device. That is clearly misleading advertising. I'm having problems with my CPU cooler H110i blinking every now and again when cycling. Not working as intended. Link to comment Share on other sites More sharing options...
Thatualle1970 Posted October 20, 2016 Share Posted October 20, 2016 I have been doing some more testing and I think I have a handle on what is happening. I have noted the following: 1) When I write 0xFF to the mode register it reads back as 0x8F, so my code thought the command had failed to enable manual feedback mode. This happens for the H100i/H110iGT/CL Mini, but the old Cooling node/H100/H80 which read back as the 0x00FF that I wrote. 2) If I ignore the unexpected returned mode and update the feedback temperature anyway then the fan speeds change. 3) SIV only writes the temperature feedback when the temperature changes. I have noticed that the firmware changes the feedback temperature I set to the internal temperature. The net effect is that I think there are two firmware bugs: 1) The mode is not returned correctly. 2) The feedback temperature gets overwritten when it should not be. Please will you pass this onto the development manager and provide feedback to me? 1 -- you're correct, the returned fan mode is omitting the temperature channel bits (bits 6~4); note that bits 7 and 0 are read-only, so writing 0xFF to a fan that's not detected will never return 0xFF. 2 -- feedback temperature is whatever you wrote to it last, regardless of channel, it's a "write only" register. Link to comment Share on other sites More sharing options...
red-ray Posted October 20, 2016 Share Posted October 20, 2016 1 -- you're correct, the returned fan mode is omitting the temperature channel bits (bits 6~4); note that bits 7 and 0 are read-only, so writing 0xFF to a fan that's not detected will never return 0xFF. 2 -- feedback temperature is whatever you wrote to it last, regardless of channel, it's a "write only" register. Yes, but it's the none RO bits that are incorrect. With the Cooling Node it works as it should. Maybe, but unless I keep writing the same temperature the fan speeds change when they should not, so I think a timeout is coming into play. What is the URL where Corsair specify what should happen. Note the issue has not been visibly addressed after 23 months which shows Corsair totally lack professional diligence Link to comment Share on other sites More sharing options...
red-ray Posted November 22, 2016 Share Posted November 22, 2016 I feel no fix after 12 months is not acceptable. On what date will there be a fix? What actions are Corsair planning to ensure there are firmware fixes in sensible timescales? No fix after 12 months was rather poor and no fix after 24 months is even worse. Do Corsair totally lack professional diligence or are they just incompetent? Link to comment Share on other sites More sharing options...
red-ray Posted March 3, 2017 Share Posted March 3, 2017 I received a report that SIV failed to change the pump speed on a H110i and when I double checked I see the same issue on my H110iGT. Below you can see that in the SIV 5.17 Beta-10 screen shots the fan speeds changed, but the pump did not. Corsair, please will you fix the H110iGT 1.1.08 + H110i 2.0.00 firmware? You should also implement pump custom curves in CL4 for both Asetek and CoolIT coolers. As I suspect Corsair will fail to do this in a timely manor, if at all, I added a work around for SIV 5.17 Beta-11 which as you can see below does what the firmware should do. Link to comment Share on other sites More sharing options...
Bob Pilette Posted March 3, 2017 Share Posted March 3, 2017 My first Commander Mini quit sensing FAN 2 after a couple of months. My second (replacement) Commander Mini stops responding after approx less than 30 mins shortly after I got it. After stopping, it shows Channel IDs of 1F 00 00 00 00 00 00 00 instead of 05 00 00 00 01 00 00 00 on the Link Devices page of SIV. Only a Power Cycle of the CM resets it. Awaiting reply from Corsair on second ticket. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.