Jump to content
Corsair Community

c-attack

Members
  • Posts

    14,539
  • Joined

  • Days Won

    31

Everything posted by c-attack

  1. You don’t want to blow exhaust from one radiator into the intake of another. Exhaust air temp is approximately equal to the liquid temp passing through it and so you are then blowing 37C air at 37C water and the result is nothing changes. You effectively loose the top radiator as a cooling apparatus. You’ll see people do this often because they are unsure how to work a dual radiator system in a standard shape case, but the all exhaust, “negative pressure”, passive rear intake is the way to go — in or out of the cabinet. If you are going to stay in the cabinet, the trick will be to manage the exhaust flow and that will happen best with the top/front exhaust. You probably need some type of venting for the heat to escape the top and right side. In a worst case scenario a standard house fan blowing air into the cabinet may displace the warmer air.
  2. So this is PSU detection and not PSU data availability? That may not be related the current issue. If the PSU is not detected in CUE, that normally is a USB path problem. There is no specific reason the HX1000i shouldn't display in CUE 3 or 4 and others are using it. My ancient AX1200i with its funny little dongle sled was recognized in both programs as well. If it shows in the USB list but not CUE, I would submit a ticket to Corsair Support regarding this. Turn on debug logging in the CUE settings so it can capture error logs.
  3. It’s most likely a hardware problem with one bad fan. The Commander Core is a little different than the other controllers as it’s not serial, but you will need to run the RGB auto-detect or power cycle the device after swapping headers. Try to narrow it down by swapping to a known working header then run the auto-detect. The stuck LED was the early warning something was wrong.
  4. This is unusual. Typically lack of control is because the device is not detected and thus there is nothing to interact with. Both entries here show as they should and the UI appears to behave as it should. Aside from interference from another RGB control or hardware monitoring program, I can’t think of a reason for this to happen. It’s possible there is an issue with the Commander Core itself, but I am not sure we’ve seen loss of control on both sides of the controller without a whole unit power fail and that’s not the case here. I would turn on debug logging in the CUE settings and then contact Corsair Support. If there is an application fault perhaps they can unravel it. If you need hardware replacements, then that step is going to be required as well.
  5. Fan speed - try setting a fixed RPM or PWM% in a custom curve as the test. Not all fans or controllers are capable of running a zero RPM. The presets can be hard to analyze since they don’t show their data points. You can replicate them in any custom curve by using the shape tools in the lower corner of the graph. Now you can see and move specific points. Make sure you change the sensor value to H100i Temp (coolant temp). RGB - The UI is showing a proper sequential lighting effect (pump-fan-fan). What you see in the actual case? Rainbows? If so, try two things: 1) restart the Corsair service from the cue settings menu. 2) Go to the lighting setup tab and change from auto-detect to “8 LED fan”. Those should produce the same result, but I am curious if the controller reloads or it is frozen/locked somehow.
  6. Connecting another CUE managed USB device is likely to trigger a temporary screen freeze as the program appears to reassess all connected devices. This has been happening for several versions now and perhaps it is necessary for functionality, Nexus or the other device. However, the screen should resume after a couple seconds and likely with the fast forward effect. If it does not recover, turn on debug logging in the settings and try and grab the logs from when this happens. This temporary freeze on new device connect is expected, but any kind of permanent freeze like described above or from connecting a new device is not. The new device connect should not require a screen touch to correct itself.
  7. That post is from CUE 2 and likely there is little left to connect that program to this. However, if I understand you correctly what’s really happening is the mouse is changing profiles and executing the assigned action. That is a little different and something of an ongoing issue. Users have reported this for several different mice, but it can be difficult to replicate. User A’s Scimitar always does this and User B’s never does it — same CUE version, same firmware. The Scimitar is the one Corsair mouse I don’t have, so I can’t add much beyond the above. I do know other users have had issues with this. I would send in a support ticket to Corsair. Also, go to cue settings and turn on debug logging. Theoretically a forced firmware update might help, but most other users affected have done that without success.
  8. You probably need to show us your CUE screens with fan control and Lighting Effects. Most issues regarding this are basic first time UI issues. Another possibility is GA Fusion is interfering, but that should not affect fan speed control.
  9. I believe there is an issue for some users with PSU data on CUE 4.14 and a fix is in the works. However, be careful using HWiNFO and CUE at the same time. For internal devices they often lock up trying to access the same hardware. The i PSU series is generally not affected as severely as Commanders and AIOs, but missing UI elements is once consequence along with garbage data. HWiNFO often wins out and CUE loses, which is one possible explanation of your current circumstances.
  10. H150i Temp (or insert AIO model#) is coolant temperature. This is the measure of the cooling systems efficiency, but since local ambient temperature is always going to be the base minimum, it's best measured as a delta or change in coolant temp (+6C etc) and coolant temp and CPU temp have a +1 to +1 relationship. A +2 increase to coolant temp will increase CPU temp by +2. H150i Temp is the proper control variable for the radiator fans. The CPU is cooled by conductive heat transfer. The liquid, radiator, and fans are the trash removal department. Pick up the heat at the block, bring to the radiator, expel it somewhere else. That means the fans only need to respond when the coolant temp increases - you must raise the coolant temp to impact the CPU temp. The trick is finding a baseline fan speed since everyone is going to have different environmental conditions that change with the room and seasons as well. Take note of the coolant temp when sitting on the desktop, non-load conditions. It's usually about 4-7C above room temperature or at a minimum the same as the case internal temperature. That is as low as you go. Set a quiet and comfortable fan speed for that level. Also take note of the peak coolant temp you see when gaming or running heaving CPU loads. Gaming is often going to be the higher of the two because of the increase in the case temperature resulting from the GPU blowing its waste heat everywhere. Set your fans at that coolant temp to a tolerable middle fan speed. This becomes your normal ceiling. There is little to be gained by running really high fan speeds vs a moderate one, so make the decision based on noise. What you do in between the points won't matter. Other fans on the Commander Core can use coolant temp as a control variable (different curve or same) as a way to balance fan speeds around the case. The Commander Pro can pick up this value as well, but it requires the CUE software to be running. Without it, no data and the fans either max out or hold their last known speed. You definitely want off the presets on the C-Pro (Quiet, balanced, extreme) immediately. It uses CPU temp with no hysteresis as the control variable on a curve meant for water cooling. Your fans will sit there at 1400 rpm all day long with occasional spikes even higher. Using the H150i temp is one option, as is GPU or motherboard temp. All are better than the defaults. However, the intended use is to take one or more of the thermistor temp probes from the Commander and take an ambient air temp. You can stick the other end wherever you want (rear exhaust makes the most sense for gaming loads). You'll need to discover the normal range of operation as it is both hardware and exact location specific. Pick a place and leave it. Moving it may change the range. I used to slide it out the back of the case and it was taped behind the rear exhaust where I couldn't see it. That is a good measure of the internal case temp and whether you need more air cycling.
  11. Try running a repair install of the app from the Windows Settings menu. Click on Corsair iCUE and select modify. This often cleans up weird button fails like ignoring reassignments, spouting out numbers, etc. If still stuck, try deleting the current action assigned to those buttons and then re-create them. Which iCUE version are you referring to? 4.14? Or did they release 4.15 in the app update server?
  12. Unfortunately environment always has the final say in overall performance. If you are in a hot room in Summer at 30C, your temps are not going to look like that guy with the windows open in Winter. As mentioned above, with the case in the cabinet, you are recycling all your waste heat. That will cause the coolant temp to increase as long as it is under load. With it removed from the cabinet, the coolant temp rise of +6C is spot on for that hardware and 2x360. For that case, I would keep that front/top exhaust and passive rear intake if you can. Coolant temp will always be minimum possible component temperature. The GPUs usually do a pretty good job as stepping down at idle, so you will see a match there most of the time. The CPU is always carrying some activity (and AMD Ryzen even more than Intel), so unless you tranquilize it with a bunch of power saving features, the CPU will only equal coolant temp when the Vcore is zero -- or powered down.
  13. Pumps and fans don’t count revolutions in the same way. The CUE software is using a divider of 2 to turn the raw count back into the expected RPM. So CUE is correct, but you can always take half of the raw MB header value into the number. There was a lot more that went along with this, but I’m now assuming that is just a background picture and we’re talking about the H100i XT and not an XD5 custom loop.
  14. Go to Windows Settings -> Apps and find Corsair iCUE. Click on it and select “Modify”. Then follow the prompts for a repair install. Most of the time when you loose basic mouse functions and/or when you start getting the numbers thing, there is a corrupt install. The repair process will not erase your profiles or settings. Hopefully that cleans things up, but that bit about not being able to open start menu is more unusual.
  15. If the fans on the Commander are not spinning, check the SATA connection for it. Software or not, usb connection or not, the fans should be forced into motion at power up.
  16. I would stick to basic troubleshooting for now. I have not heard of any other Dominator issues like this with random lighting issues and I have not seen it for my 4 module Dominators either. 30 days in on 4.14 we should have a pile of complaints if there was a version specific issue. What you're describing does sound like what happens when another RGB program is interfering. What MB brand is this and is the RGB software in use? As for immediate steps, start with the basic repair install (Windows Apps -> Corsair iCUE -> Modify). This will not delete your profiles and settings. If it continues, try a creating a new test profile with something like a color wave, color pulse lighting link (or whatever). If there is a problem with either RAM or programming, a pattern that turns the LEDs on and off may reveal it quicker. It's also possible there were some profile import issues coming over, particularly if you were on an older version of CUE 3.
  17. Not on Intel or older AMD platforms (pre x470), but those are genuine pass through ports (no power or additional bandwidth). This why they tend not to work on the recent AMD boards since you are stacking 1-3 devices on the same line without supplemental aid. Also, it is a pass through and not a device to device control scheme so the Commander does not take control over a Lighting Node Pro or PSU connected to it. All devices with usb connections will show up in cue as individual devices.
  18. Just use the normal software profiles. Remember you can turn off a global lighting link effect on a per device basis, so you can set the color shift, pulse, whatever as a lighting link, then go to the AIO and click on it to hide/turn it off. Then add the temp specific lighting profile for the pump LEDs only.
  19. Is it something native to the case model itself? There are definitely cases that come with RGB strips are part of the chassis and not as a 3rd party add-on.
  20. Take your time and evaluate what you have. There won’t be any additional hardware required if you add a different fan type. If you really like the LL, then it may be enjoyable to add them to the front, but then I suspect it won’t be long until you want 2 more for the top. On the other hand, one more SP-Elite makes the case uniform from front to back. You’ll have to see.
  21. If you just have 1 internal USB hub on the board, then the hub connects to the MB and everything else to it. It’s essentially a powered splitter. In this case, I think you should put both on the hub even if there are 2 motherboard ports. The Platinum and Commander Pro are the most affected by this issue, presumably because they draw more power than other devices. Case LED strip - You need to be careful here. Some are 12v RGB and some are 5v D-RGB. Your MB will have both types of RGB headers. All Corsair gear is 5v so don’t connect anything from them to the board. The strip may not have any helpful markings, but hopefully it’s already connected to the board on the right type. The strimmer is 5v RGB and will connect to the D-RGB header. It is possible to connect it to a Corsair controller with a 3rd party adapter, but I am not sure if you are interested in that at this point. You would need the adapter and a RGB channel on the Commander.
  22. The powered USB hub is typically 4-5 USB 2 ports in a row, but then there is a direct link to the board USB 2 port. It should be about the size of your thumb. The last bit is the most important -- it needs to have a SATA or molex power cable to connect back to the PSU. If it doesn't, then it's just a passive USB 2 splitter and that's where the problems arise. The board does not output enough to handle the traffic from some of these devices. Using passive connectors (like those on the Commander Pro) just compounds the issue. The your number of internal USB 2 headers (1 or 2) will determine how you need to hook up. If just one, then all the devices go on the USB hub. That is their communication method with the board. If two internal, you can use one device direct to the board or save that for something else if needed. I think I might connect the Commander Pro directly since we know that one uses a bit more power and just maybe it's passthroughs could be used in a emergency. However, we've seen it work the other way too. The board output is so weak that no components work on direct connection and they need the hub's power to function. In that case, the Commander might be better off on the hub. Which "H100i" do you have? Platinum models appeared to be more affected compared to coolers with less going on.
  23. It should be the first option for most people. A powered USB 2.0 hub is about $20. Half of us need one anyway because the board may only have 1-2 internal USB 2 ports. As for the remedy, it's not something Corsair can fix. This is on the MB end. A clear example of this is x470 owners who had no issues with this, then took the BIOS update that went along with the arrival of the x570 boards and CPUs. The voltage spec was altered. If stands to reason if you can be fine before a BIOS update and not after, that is a MB issue. Same thing on the other end with any recent fixes. Finger crossed on that, but the issue is limited to recent AMD motherboards only.
  24. No, they will show up as different devices and thus different "pages or tabs" within the CUE app. You can have any combination of controllers. The only limiting factor is the number of USB 2.0 port available. In this case, it should be all on one for you anyway with the Commander Core. You will have to use the Commander Core as one controller since it is required to power/control the Elite series AIO. That's not a problem and it gives you 6 PWM and 6 RGB ports on the other side. The Lighting Node Core that comes with the case can be saved for later expansion or something else. In the 5000X, you should have the hardware you need unless you are ready to add RGB strips. Those types of devices require a Pro controllers. The Core controllers only accept fans by default. Your ML-Elite and SP-Elite are a perfect match, 8 LEDs center and same color tone. The LL is going to be the oddball in the mix. It may look just fine (rear exhaust?), but be aware nothing can make the other fans do the "ring style" effects native to the LL or QL series.
×
×
  • Create New...