Jump to content

cc10101

Members
  • Posts

    72
  • Joined

  • Days Won

    1

cc10101 last won the day on September 27 2018

cc10101 had the most liked content!

Reputation

13 Good
  1. Responding to my own post just to confirm that yes, two EKWB XE480 rads will fit on the front of the Obsidian 1000D in a push/pull config (using LL120 RGB fans). Clearance even seems pretty decent, maybe 8-12 mm or so. Important Note: the two rads WILL NOT FIT onto a 1000D fan tray without having the fans installed between the rads and the fan tray. The rads are too wide given the bent edges of the fan trays. The fans raise the rads high enough away from the fan tray to make it work. Having said that, I have no idea what the manufacturing tolerances are for either the 1000D or the LL120s or the XE480 rads. So clearances might be far tighter, or it might not even fit w/other combinations of those things. I'd give it a cautious thumbs up for others looking to use those rads in this case in a push/pull config. Tolerances would have pretty bad among the various manufacturers to not fit.
  2. Thanks for the info. I'll give the export/import approach a try. Haven't ever exported a profile before. But it seems straightforward enough. I actually tried the single CoPro w/multiple PWM hub approach first. Using DeepCool FH10s. But I couldn't get the fan speeds working right. The reported fan speeds were all over the place (with some being 3 or 4 times higher than the max RPMs for LL120 RGB fans). So I ordered more CoPros. I had planned on hooking up 1 or 2 water temp sensors to one of the CoPros and basing my custom performance curves off one of them. So I'll be pretty irritated if it turns out that won't work reliably. Having bought the extra CoPros, I'll see how things work. If I run into problems, I can always try another brand of PWM fan hub.
  3. I have 3, soon to be 4, Commander Pros. They all have the default performance curves for fans: silent, balanced and extreme default curves. I also defined a custom curve that I want to use for all 32 fans across all 4 CoPros. I see ways to export entire profiles. I also see a way to apply a custom curve from one fan to all other fans in the profile, or in all profiles in a folder (whatever a folder is). But I do not see a way to copy an existing performance curve for a fan on one CoPro to a fan (or fans) on another CoPro. Seems like that would be a common desire. So I figure I'm just misunderstanding how either the export/import thing works, or how the apply to other fans feature works. Or I'm missing some other functionality via drag and drop or something. Can anybody shed light on how to copy a custom curve between CoPros? Or do I have to recreate it on each CoPro?
  4. That makes sense. I have the pattern (Visor over static color) applied to all the RGB devices: keyboard, mouse, memory, case fans, 1000D front panel, and sails logo. I had the system up and running w/a H150i Pro, 8 fans in front, 3 on top, and 2 at the back, plus the other devices listed above. The Visor pattern would start at one end of the chain of devices and fans, work it's way through them all to the last device (the mouse), then work backwards the way it came until it reached the first device again. So it cycled forwards and backwards; not around in a circle, apparently. Or at least that's what appeared to me to be happening. Given that, I'm thinking that, for the Visor pattern at least, the order of the fans doesn't matter so much because the lighting will visit them in one direction and then visit them in the opposite direction.
  5. I saw that you did that in your chart. But I misunderstood how the signals worked with the CoPro and therefore also misunderstood which fans your wiring approach would synchronize during lighting patterns. I get it now, though, and it makes perfect sense. If I weren't switching to using 4 CoPros, I'd be switching my wiring to match yours because I definitely would want the 1s, 2s, 3s, and 4s to be synchronized (although I'd put the 1s at the top and the 4s at the bottom). Unless there's a problem with having the LED wiring all funnel into the 1000D's CoPro using Y-splitters, while having the PWM wiring split across 4 CoPros, I might still do it your way because the pattern (two by two, front and back of the rads) is probably nicer than having each individual fan light by itself. I already ordered the additional 2 CoPros or I'd give the Silverstone 8-port PWM hubs a try. They might work better than the DeepCool hubs are working for me.
  6. Yep, the way it's lighting up seems largely in line with what you said: A1 and A3 are synchronized, as are B1 and B3. There are a couple not working that way, but I probably crossed wires somewhere, perhaps at one of the splitters or something. This all makes more sense to me now. Wired correctly, each RGB LED hub channel gets the same signal. So all the hub port #1s connected to the CoPro lighting channel will be treated as a single fan. Kind of obvious to me now; in hindsight. So yes, Zotty's wiring approach would appear to give me what I was going for which was to have A1,B1 do whatever lighting thing, then A2,B2, and so on, moving in "spreadsheet rows" across the surface of a radiator. Having now figured it out (with your help, thanks), it may all be for naught as I cannot get the DeepCool FH-10s to work reliably. Fans speeds are all over the place. And RPM sensing is clearly not working as some reported RPMs get to 3000 or 4000 RPMs, which obviously isn't possible on LL120 RGB fans (max ~1500). So, since I already have two CoPros (the 1000D one, and one I bought awhile ago), and for the sake of expediency, I ordered two more CoPros to wire everything up. With 4 CoPros, I can wire up 32 fans without using LED splitters (although perhaps, for cable mgmt purposes, I might still combine them all down per Zotty's approach anyway). I will have 8 PWM splitters (2 per CoPro). But the max fan PWN connections per CoPro will be 8, which should be okay. I want to also add the EKWB res/pump combo to a CoPro (so a 9th PWM connection). But I'll have to figure out the amperage and make sure it stays under the limit. If not, hopefully I can take 2 fans from 1 CoPro and add them as 9th PWM connections to 2 other CoPros, and that will give me 6 PWM fan connections plus the EKWB pump PWM connection on a single CoPro. Otherwise, I guess I'll be ordering a 5th CoPro. This build has grown truly, embarrassingly, ridiculous in cost. LOL Thanks again for all your help.
  7. Thanks, DevBiker. So basically, iCUE will see 4 fans as 1 for patterns. I mostly assumed that would be the case, so I was careful to wire the batches of 8 fans up to led hubs in exactly the same way. Or at least I think I did, I will verify. Considering just the 8 fans at the very front of the case, Zotty wired all the fans on the front-side of one rad to a hub, then all the fans on the other rad to a hub. I did it a bit differently, but consistently across all 6 fan hubs (all 24 fans): If you view the front 8 fans as spreadsheet cells (viewed from the front of the case), then I wired them like this: A1|B1 --> hub A, ports 1 and 2 A2|B2 --> hub A, ports 3 and 4 A3|B3 --> hub B, ports 1 and 2 A4|B4 --> hub B, ports 3 and 4 Zotty's is: A1|B1 --> hub A, port 1 / hub B port 1 A2|B2 --> hub A, port 2 / hub B port 2 A3|B3 --> hub A, port 3 / hub B port 3 A4|B4 --> hub A, port 4 / hub B port 4 But what I'm noticing, with my fans at least, is that the fans aren't lighting four fans at a time in a logical or consistent pattern at all. I would've expected that A1 and B1 (from my spreadsheet above) would light in the same time at the same point in the lighting pattern. Then A2, B2, etc. But that's not happening. The batches of 4 are not adjacent most of the time (although for some fans, they are). I'll play with different wiring schemes to see what happens. I don't need each fan addressed individually. But it would be nice to get some degree of logical addressing within sequential lighting patterns. I'm very glad I decided to test all this out while everything is still outside the box, and before I made the water-loop connections. Makes it *way* easier to rewire stuff. :biggrin:
  8. Responding to my own post to fill in some more findings... I'm now noticing that, even in my low RPM custom curve performance mode, the fan RPM values shown in iCUE are jumping all over the place. Including seeming some crazy values (like 8000+ RPMs). This is now happening on fan #s 1 and 2, while fan #3 seems relatively stable, by comparison at least. The fans themselves don't seem to be spinning up to crazy RPMs. Just seems like the sensing isn't working quite right.
  9. Zotty, I wired up 24 fans (16 in PP w/a couple 480 rads plus 8 in another tray). I'm using a wiring approach almost exactly like what you're doing in your current 1000D build, per your chart). So, for CoPro lighting channel #1, I have 16 fans, 4 per RGB LED hub, for a total of 4 hubs, that use 3 y-splitters to feed into the built in CoPro connector at the front/top of the case (same as you). All the fans are lighting up. But the pattern (I have a pattern that cycles across all RGB devices) is not what I expected. I'm confused about a few things. (1) Although I have 16 fans wired up to CoPro lighting channel 1, iCUE only allows me to specify a maximum of 6 fans connected. Is there a way to tell iCUE there are 16 fans connected? (2) If the answer to question #1 is no, then how many fans do you tell iCUE there are on each lighting channel? I've tried all possibilities (1 - 6) and only setting to 4 - 6 causes all 16 fans to light up, and so far as I can tell, there's no difference to iCUE if I say 4, 5 or 6. (3) Using the Y-splitters causes iCUE to apply a pattern to multiple fans at the same time, as opposed individually. I thought that might happen. Is this unavoidable? (4) If the answer to #3 is that yes, multiple fans will share a "location" in the pattern, then it seems that I should specify 4 total fans per lighting channel (as 16 is evenly divisible by 4). But I'm unclear on how to get iCUE to allow me to specify which 4 fan are in each group? How did you do that? Thanks.
  10. I have 16 fans wired up to 2 EK XE480 rads on a tray that's intended to go in front. I am currently testing my fan wiring while outside the box. And running into some issues. But once I have that sorted out, hopefully in a day or so, I will insert the tray and see if it fits. I'll report back if it works or not for me. Theoretically, it should. Others out there have done it w/these rads (as revealed by a couple web-searches). But it's going to be very close.
  11. I'm currently using 3 DeepCool FH-10's w/24 LL120 RGB fans plugged in to them (8 per FH-10 hub). I'm in the midst of testing the wiring before fully installing everything into the case. I figure it'll be easier to deal with replacing a faulty fan or a faulty hub or cable outside the box than inside. Anyway, in iCUE, under Performance, they show up as 3 connected fans (which is expected since their are 3 hubs wired to CoPro PWM ports 1, 2 and 3). Fans #1 and #3 seem to work partially okay, RPM-wise. I can change the cooling mode around and the fans adapt. However, at higher RPM settings (using the Extreme performance mode, for example), while the RPMs increase, they seem to jump all over the place, including showing RPMs the LL120 RGB cannot possibly achieve (well over 1500 RPM). Fan #2 seems stuck at 650 or so RPMs which is running roughly 200 RPMs under the other two, despite sharing the exact same performance mode. Not really sure what's going on there yet. I'm also having some RGB lighting issues. So I definitely have some wiring kinks to sort out. I'm going to check that all the connections are secure and try again.
  12. Okay, that makes it a lot clearer. Thanks. I can see the cable connected to the sails logo as it runs up to the top to the front IO panel. But I cannot see a pass-through coming back down anywhere. It must be hidden behind something at the moment; so I'm sure I'll spot it when I swap in the custom loop stuff. On an entirely unrelated note, I just noticed the EKWB has a 1000D distro plate that covers the entire front fan tray area. For a bit less than $800. Seems to me it makes no sense because it eliminates all that airflow and/or radiator space at the front of the case. Seems to me a distro plate would make more sense if it fit elsewhere in the case, without being so disruptive of rad/fan/airflow. Anyway, I've strayed far off-topic. Thanks again.
  13. I'm confused about the use of the RGB pass-through cable at the front-top of the 1000D. If I understand correctly, that cable is currently used to route the RGB signals from the LEDs on the front of the case (sail logo, buttons and so forth). So out of the box, it would have been already plugged into the 1000D CoPro LED port #1. I'd be able to confirm this for myself, but at the moment, I cannot trace the port #1 cable to it's source (it's hidden behind fans and an H150i pro cooler). From your diagram, it appears that you are routing your 16 front fans, using Y splitters, into a single cable that somehow connects into the same cable (pass-through cable) used for the front panel lighting, and into the 1000D CoPro LED #1. Is this correct? If so, what's not clear to me is: (1) How do you connect the fans cable into the pass through cable, if the pass-through is used for the front panel LEDs too? (2) Can you still individually address the front-panel LEDs in iCUE? Or are the 16 fans on your front rads, plus the front-panel LEDs, all forced to share a single lighting setup (eliminating the possibility of a sequencing lighting setup)? I've read through this thread (and others) several times. And done searches. But somehow, I'm missing something here (I mean, I'm missing IQ points obviously :):, but maybe some bit information too).
  14. That makes sense. Thanks. I've been using Y splitters to combine PWM cables into the CoPro, and figured that as long as I stay below the published limits on the CoPro's PWM amperage capacities, that I'm okay doing that as well. Anyway, thanks again for the help. Now I need to figure out the right lengths to order for extensions and splitters.
  15. Thanks, Zotty. It'll be tight, but I'll give it a test fit. Edit: I deleted the follow-up question I had asked. I got the answer from DevBiker over in his cables thread. Thanks again. You probably hear this a lot around 'these forums, but you (and DevBiker) are awesome.
×
×
  • Create New...