|
Post by dtarrance on Mar 19, 2019 20:35:10 GMT
Hello,
I just recently found your SIV software, and have been trying to learn how to use it more. I've read through the "Forgotten Manual" a few times, and managed to get it to recognize and control my Corsair H100i Pro, Commander Pro, and Lighting Node Pro as well. I'm also working on trying to get SIV to control my EVGA CLC 280 cooler as well, it reads it as an NZXT Kraken. The software can be a little overwhelming with all of the options, but I'm the type of person that enjoys having too many options as opposed to too few, haha.
The reason for my post today is I was wondering if there is a way to pick and choose which hardware SIV will monitor and attempt to control. The EVGA provided software (EVGA Flow Control) is terrible, so I'd like to use SIV instead. Unfortunately, I also have many other Corsair products that necessitate me to use their iPOO software to control them. I understand SIV and iPOO conflict with one another, so I was wondering if there was a way to tell SIV to ignore specific pieces of hardware? If so, that would enable me to use it to control my EVGA CLC, and still use iPOO to control my other Corsair hardware.
Is this an existing option that I may have overlooked? And if not, would this be something that you could implement? I realize that it may be counter productive to the entire point of your wonderful program. But if this is something you could add, I know there would be many EVGA users who would love an alternative to the frustrating Flow Control software.
Thank you for your time, and I look forward to your reply!
Best Regards
|
|
|
Post by siv on Mar 19, 2019 21:58:02 GMT
Welcome to the forum and thankyou for your post, but why do you wish to run the heap of junk from Corsair at all? If it's just for keyboards/mice then last time I checked if you disable the iPOO service this worked, see spams://siv.boards.net/thread/14/running-same-time-corsair-iPOO. As for controlling the EVGA CLC 280 cooler then I guess it's just a badge engineered NZXT Kraken, please post [ Link Status ] + the screen you get from pressing [ n:0 24 ] which is just to the left of [ Kraken ] so I can compare this to what my X42 reports. Before CL4 correctly implemented support for the Global\CorsairLinkReadWriteGuardMutex lock SIV used to detect CL3 was active and not report any Corsair Link hardware, but once they added support this was not needed. I have just checked and most of the old code is still there, but I would need to add a few extra lines for such as the CLNP + CLCP + H115iPro + H100iPt. I would also need add iPOO detection, but I need to decide if I wish too try and make SIV co-exist with the Corsair bloatware as to do this I would need to install the Corsair junk on this system and I don't really wish to. When Corsair stopped supporting the Global\CorsairLinkReadWriteGuardMutex lock I was to put it mildly displeased and largely lost interest in supporting Corsair hardware so these days focus on other suppliers hardware which I also find rather more reliable. On this system I have a Thermaltake TPG-1250D-T PSU which is way better than the AX1500i I have in my old system as it just works , but on my old system the CLCC firmware keeps crashing when a AX1500i is connected .
|
|
|
Post by dtarrance on Mar 20, 2019 20:17:07 GMT
Thank you for the warm welcome, and for your reply!
I'm currently at work, and I do have the screenshots you asked for, but I'm not seeing a way to attach them to this post from my phone. I'll update the post or add another reply once I get back home later today.
As for why I use Corsair iPOO, I don't have any issues with it (thankfully), and enjoy the flexibility of being able to easily create profiles and control all of the Corsair hardware I own from one interface (keyboard, mouse, headset, H100i Pro RGB, 2x Vengeance Pro RGB RAM modules, Commander Pro, Lighting Node Pro, 12x RGB fans, and 4x RGB strips).
As it stands, the EVGA Flow Control software is so buggy that it won't even start or recognize the cooler is attached. This is a well known issue, and EVGA can't seem to correct it. I've tried all of the "solutions" I've found online, and none of them work for me. Thankfully the default profile stored in the firmware will control the pump speed and fan speed without the need for the software to be running. However that means that I am unable to adjust either the fan or pump speed, or adjust the RGB lighting. So my only recourse is to find another software application to hopefully give me that control.
I have actually been looking into a way to trick iPOO into seeing my EVGA CLC 280 as a Corsair H115i, but I haven't been able to find any way to do so.
Once I found SIV, I was elated to find that it was able to connect and control the fan speed, pump speed, and the RGB LED colors as well. Unfortunately since enabling the -AIOCTL qualifier also makes SIV interact with my Corsair hardware, the conflict between SIV and iPOO causes me several issues.
I completely understand that you don't want to install the Corsair software onto your system. Not having any experience with developing hardware control software though, I may be way off base here. My initial thought was that you could perhaps add another qualifier (something like -NOCORSAIRHW) that would allow the other -AIOCTL functionality to continue to work, but would simply not try to connect to or interact with any Corsair hardware that is installed in the system. That way the existing documentation would still be relevant, and (in my head at least) you wouldn't have to add or implement any kind of auto detection code to look for the hardware; SIV would simply skip the lines of code that attempt to connect to any Corsair hardware.
Hopefully that makes some sense, but if not, I'd be glad to discuss it in more detail or try to phrase it differently if need be!
|
|
|
Post by siv on Mar 21, 2019 8:33:48 GMT
I too am pondering getting SIV to simply skip detecting any Corsair hardware, but I am unsure if this is optimal as AFAIK iPOO can't handle such as the CLCC + H100i +H80i + ... so in a general solution SIV should only skip Corsair hardware that iPOO supports. The detection/skipping is/would be based on the USB VID (Vendor ID) + PID (Product ID) which would work for most devices, the catch is that the H110i (iPOO supported) has the same VID + PID as the CLCC + H100i + H80i (no iPOO support) and the only way to tell the difference is to open and read the Channel IDs from the device, but doing this is unsafe as iPOO fails to correctly use the Global\CorsairLinkReadWriteGuardMutex lock. Further iPOO supports different hardware to CL4. As for getting iPOO to deal with the EVGA CLC 280 then I can't sensibly comment 'till you post the screen shots and also would like [ Link Devices ] as this lists all the VIDs + PIDs. To be clear I need screen shots generated after you have stopped and disabled the iPOO service. I feel that rather than asking me to change SIV you should first ask Corsair to change iPOO + CL4 to enable you to choose which devices iPOO + CL4 control. They should do this so CL4 can be used for devices that iPOO fails to support and if they do this (and pigs fly!) I will then release a SIV that supports this . A sensible implementation would be to have a REG_SZ in such as HKLM\System\CurrentControlSet\Enum\USB\VID_1B1C&PID_0C10\0B05008E541A0A16\Device Parameters called say ControlledBy which would be set to one of iPOO or CL4 and I could then set this to SIV to tell SIV to control the device which would mean iPOO + CL4 did not control it.
|
|
|
Post by dtarrance on Mar 26, 2019 5:23:50 GMT
Hello, and thank you for the reply! I apologize for the late follow up, as I wasn't notified that there was a reply to my last comment! Hopefully I have all of the information you had requested, and then some! I have been trying different drivers for the EVGA CLC 280 on my system in an attempt to get the EVGA Flow Control software to recognize the device. Unfortunately, it still refuses to even open, and says that it cannot detect the device. Here is a link to all of the screenshots I took of SIV in the various Link menus: spams://imgur.com/a/kxSWBO1 It seems that I was mistaken that SIV identifies the EVGA CLC 280 as a Kraken cooler. It is actually HWiNFO64 that detects it as such. I've attached a screenshot showing as much, if for some reason that's helpful. I'm not sure if that is relevant to our conversation, but thought it was worth mentioning. Please do let me know if there is anything else that I can provide to you to assist you with this, or if there are any other questions you may have for me, and I will do my best to reply in a more timely manner. Again, I appreciate your help with this, and I look forward to your reply! Best Regards
|
|
|
Post by siv on Mar 26, 2019 23:13:34 GMT
Here is a link to all of the screenshots I took of SIV in the various Link menus: There are two generations of NZXT Kraken X41/X51/X61 then X42/X52/X62, in the [ Link Devices ] I posted it's a HID x42 that uses the standard Windows HID driver, but the EVGA CLC 280 looks like a USB X41/X51/X61 that uses the basically the same SIUSBXP driver as the H100iPro. The closest Corsair cooler to the EVGA CLC 280 is a H80iGT or H100iGTX, these use basically the same protocol but the are small differences which SIV allows for. The H100iPro uses a totally different protocol, but the same buggy SIUSBXP driver. SIV works around the driver bugs when -AIOCTL is specified as it does for USB connected AXi PSUs. It's strange that SIV does not report a fan speed for the Asetek-6/EVGA CLC 280 unless you don't have one connected. Is a PWM fan connected? I expect it has to be a 4-pin PWM as AFAIK 3-pin voltage fans are not supported by any Asetek-6 AIOs. Given the EVGA CLC 280 successfully ran [ Link Test ] then SIV should have no issues controlling it along with the CLCC + H100iPro. Do as I specified in spam://siv.boards.net/thread/14/running-same-time-corsair-iPOO/ and SIV should have no issues controlling all your AIOs. As both SIV and HWiNFO correctly use the Global\CorsairLinkReadWriteGuardMutex lock it's fine to have both active at the same time.
|
|