Jump to content

c-attack

Members
  • Posts

    20,131
  • Joined

  • Days Won

    268

c-attack last won the day on March 22

c-attack had the most liked content!

Reputation

936 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Switching from PCI-e Gen 4 to Gen 3 was the old solution for the X570/B550 motherboards. Those first generation PCI-e 4.0 boards along with the Intel Z690 counterpart had a tough time keeping steady USB voltage at the socket. Most users chose a powered USB hub to keep the devices connected and many needed one anyway to handle more than 2 connections and side stepping the need to set it to PCI-e gen 3. The bothersome aspect here is there is no way you went X number of years with this thing and then only now does it suddenly decide the USB connection and motherboard pathways are insufficient. Maybe if you have been on a very old BIOS all this time and then recently updated. This was the problem X470 owners ran into. They were just fine for a year, but when new CPU compatible BIOS versions rolled out for the next generation, they got pulled into this as well. Even then, the normal behavior for a cooler that looses it's USB connection is to drop into hardware mode -- that's HW Lighting and the fan curve you were using is automatically written to the device. The fans should not stop. Even if they did, it should take 5-10 min before the zero fan state could elevate your CPU temps to warning zone. If the pump stops, then you have 30 seconds at most. I am not sure which is the case here. A possible but unintentional way the fans might stop when the AIO drops into HW Mode is if you have the fan curve set to a value it cannot obtain without the software -- like CPU temp. They should be running from the coolant temp and that is a value the AIO can read even with no software installed. Still, what should happen with a null value variable is the fans max out rather than stop, so I still have some concerns. I suppose all you can do now is move forward and keep an eye on things.
  2. The LCD and regular pump top connection is by far the most common new set up issue. While it is possible there is a hardware defect, the overwhelming majority are resolved through connection tinkering. You tried the hardware reset version. Sometimes it takes more than one try, but I would now work the other end of the problem -- USB. That is the actual communication path. No LCD usb connection and it won't show in CUE. A lot of motherboards do not like for the Commander and LCD top to share that USB splitter cable. X570 and B550 were famous for this. Improvements on the subsequent platforms and it doesn't come up quite as much, but it is users still run into trouble here. Most boards only have 2 internal USB 2.0 connections and you likely don't have some type of 9 pin to USB A cable lying around. If you can temporarily free up a USB 2 internal to connect the LCD and Com Core separately, try it. If it works, then you know you need a powered USB hub like a lot of AMD owners. If you are not using the other USB 2 internal, then leave them separated, but it seems likely the LN Pro is on the other USB 2.
  3. Yeah, should be safe to continue using it. I wouldn't do any 24 hour stress test silliness, but with any AIO if the pump stops you'll know pretty quick and there are multiple safety systems to shut things down before the CPU gets into thermal jeopardy. It should continue to run from it's firmware based fan curve. I have one in the closet from 3 years ago locked in this state. I can take it out any time and it runs -- I just can't control it and that is the major issue at the moment. See if you can ask for the "Advanced RMA". That's where they ship you the new unit on a credit card hold, which is then released when you ship the defective unit back later. That should cut your down time to zero and make swapping stuff over easier too.
  4. First time you set up the headset you may need to have it wired to properly detect and download it's software module. Go into the CUE Settings Gear -> Software and see if it has the module for the headset listed. With both the receiver connected and HS80 wired, try to pair the headset to the dongle again. You should see both the dongle and the HS80 as separate devices. Similarly, the both LCD and regular pump top must communicate back to the system through the Commander Core. When in AIO mode, you should never see the Commander Core as device (by picture) and it should be the AIO LCD pump instead. The red (!) is a generic warning that can mean several things, but in this case it likely indicates a communication issue between Com Core and pump. This was a very common issue early in the life cycle. Shutdown the PC and flip the PSU off. Go into the back and deliberately disconnect and then reconnect the wide power cable on the end of the Com Core that leads to the pump. This can be a finicky connection but also this process is going force both devices to do a deep connection check on the next power on. The other place this can go wrong is on the LCD case mount on top of the actual CPU block. Might as well pop it off and back on to make sure that is a solid fit. Flip the PSU back on and start normally -- fingers crossed. If this does not resolve it, I would then contact Corsair Support.
  5. Unfortunately this is a known hardware issue and has been luring around since the product launched. This 'false pump fail' error does not seem to have a user side resolution. We have guessed it is some type of tach sensor or related circuit fail that triggers the warning, even though the pump continues on and thus CPU temps are fine. The problem is this error state locks you out of the device controls, so it is effectively bricked in the meantime. You need to contact Corsair Support so they can replace it. However, there have been some other instances that produce what appears to be a similar error but is not fatal. Try the standard power cycle trick. Shut down the PC and flip the PSU off. Wait 30 seconds or hold the case power button down for 10s to drain any residual power. Flip the PSU back on and start normally. Try stopping in the BIOS to rule out any type of software interaction. Occasionally users have posted the unit comes back for a few seconds, before then falling back into the pump fail state when the OS loads. This also is the solution for the originally mentioned 'negative liquid temps', so it is a good first troubleshooting step when things are out of sorts. Unfortunately, if the pump fail comes right back on, that is not likely to change with subsequent attempts.
  6. Generally speaking a D5 pump is a D5 pump and all of them come from the same original manufacturer with variances in top design. So the pump on any distro plate or flat reservoir should be the same specifications and flow as any other D5. Whether or not the distro plate's serpentine design adds to total system flow restriction is another matter. While it must increase resistance by it's very nature, it is likely less than the difference between a restrictive radiator or CPU block and a less restrictive one. That means you simply need to up your pump speed when needed. *Interesting the strip is still only 28. My "old" O11D was 30 from several years back. Must have been bad info in the other post claiming a rather high number. Either way any number from 1-104 is doable without too much fuss.
  7. This came up recently and it had increased from the 30 LEDs on the prior cases. Much higher number now, but it will work with a Lighting Node Pro. If you have non-Link fans and want them speed and RGB controlled through CUE, then the Commander XT is a better option. No speed control on the LN Pro or Core devices. However, if you already have a CUE Link Hub + fans or AIO, that's the direction we're headed. A Commander XT is not overly expensive at $50 USD compared to redoing your case in QX fans, but this is a shift in control technology and most future products will be CUE Link based. That's why it's funny we still don't have a RGB strip adapter for the CUE Link hub and the Lighting Node Pro appears to be on the verge of discontinuance in the interim.
  8. That is the most like for like replacement at the moment. It will come with the Commander Core fan controller (AIO power goes through this - required) but also gives you PWM control for 6 fans and RGB control for 6 Corsair fans. Also be aware Corsair is moving toward the interconnected "one wire" setup like most manufacturers. This is the new CUE Link gear. There is a CUE Link H115i AIO that is controlled through the very small CUE Link hub and gets power via a PCI-e 6 pin. I am not recommended one or the other, but be aware that new CUE Link stuff only works with CUE Link gear and the older dual wire stuff like we've had for the past 5-6 years only works with Commanders, Lighting Node Core/Pros, etc. If you have a case full of current Corsair LL, ML, QL fans, then the Capellix model is an easy transition and everything connects to the one controller. If you are thinking you might update all your case fans to RGB shortly, then it may be worthwhile considering the CUE Link model as most new gear will be configured to run with it.
  9. You might need to clarify your intent a little. However, for custom water cooling any D5 or DDC pump can easily handle the flow resistance from two CPU blocks or a CPU and GPU block (if that is what you mean). What you may want to account for the approximate amount of power you need to dissipate vs the number of radiators. Most water cooling kits are not "bundle deals", so don't be afraid to choose what you need on a piece by piece basis. No such thing as "guaranteed to fit all cases and installations". That's why it's custom cooling.
  10. You need a third party adapter to connect the 'motherboard style' 5v connector into a Corsair controller. This is an example of one for a Lighting Node Pro and it can be used from anything from LED strips to custom water blocks or other 5v bling devices. The trick is CUE will only generate LED strips in CUE sizes, so if you've got more than 60 LEDs, you'll need to use 'external RGB strips" to generate the longer length. The Lighting Node Pro works fine and has two channels for this stuff. Make sure you don't over-pay. That is an inexpensive controller that is in short supply through authorized retailers. I am seeing some ridiculous prices out there. Ebay or the like may offer a much better deal and there are a lot of them out there from when it was a freebie in fan multi-packs. If you have a Commander XT, it already has a RGB channel for this purpose but the Commander Core for AIOs does not as the pump power chain takes its place.
  11. If this pops up again, start a new thread and we can try to work it out. The red triangle of death is a generic warning with multiple possible triggers. Most of the time it's not a fatal flaw -- just communication issues along the SMBus. However, it also can happen with a bad kit making it a little complicated.
  12. There's no device power on the USB connection. That's the SATA, so if fans stop and lights go out that is more likely a device power drop, which then in turn triggers the Windows device disconnect sound because the thing just lost power. This is not normal behavior or something that comes up very often. Definitely follow up with support. This is a serious hardware error. Make sure you emphasize the RGB drops to dark and fans stop in the support ticket. That's the red flag this is not one of the usual run of the mill things and hopefully the agent won't run you around the block a few times with elementary steps.
  13. So the device count has gone from 14 to 24, but something not quite clear yet is if the per side limits remain that same. Meaning if you have more than the 7 devices on any side of any CUE Link Hub, it will trigger the brightness reduction state. I suspect this is going to be true, but something for Corsair to clarify. In the meantime, if you have any CUE Link cables left over, you could try running the AIO to the other side of the hub to see if this drops the message.
  14. Go into the CUE Settings -> Software -> SDK. See if there any active game integrations or simply turn off the Game SDK toggle. Are the fans flashing red? Or just random distorted color patterns?
  15. The "blank" polling field appears to be a visual bug and it should hold the previously set polling rate. I see the same thing with 4000 Hz as the current max setting. I am not sure 8000 is worth anything, but if they have deliberately dropped it from the options they should explain. This is version specific (5.12+), so don't pull your hair out trying to repair/reinstall. Corsair will need to correct.
×
×
  • Create New...