The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Corsair Link

Closed Thread
 
Thread Tools Search this Thread Rating: Thread Rating: 83 votes, 4.87 average. Display Modes
  #1  
Old 05-05-2015, 03:34 AM
red-ray red-ray is offline
Banned
red-ray's PC Specs
 
Join Date: May 2014
Location: England (GMT+1)
Posts: 7,152
POST ID # = 777371
red-ray Reputation: 81
Arrow Using SIV to provide information to diagnose issues or to control CL hardware

To use SIV diagnose issues and/or to control CL hardware see http://rh-software.com/. SIV was designed as a utility to report information and troubleshoot issues. I expect this is all most owners of CL hardware will use it for.

  1. The SIV initial + [USB Bus] + [Link Devices] + [Link Status] + [Link Fans] + [Link LEDs] panels allow the root cause of many hardware issues to be determined and resolved.
  2. If you need help with a CL hardware issue I recommend attaching these screen shots to your post using names such as [Link Devices].png.
  3. You should also ensure your PC Specs are up to date and specify the Windows Build number.
  4. Check the devices are present on Devices and Printers and confirm that Windows Device Manager is not reporting any issues.
  5. ALL of the files in the siv.zip release should be extracted to C:\Program Files\SIV\ or similar and SIV should be run from there.
When there strange or unexpected information is reported I often suggest using SIV to figure out why this is so. Looking at http://forum.corsair.com/forums/showthread.php?p=805421 you will see that CL reported three motherboard fans twice, did not report one at all and did not report many of the temperatures. Next looking at http://forum.corsair.com/forums/showthread.php?p=788225 you can see how SIV helped to deduce the temperature of 85.8°C should not have been reported at all. It also shows what is typically needed to investigate the issue.

SIV can help tell if the H100iGTX firmware has been loaded into an H80iGT (http://forum.corsair.com/forums/showthread.php?p=785129) or the H80iGT into a H100iGTX (http://forum.corsair.com/forums/showthread.php?p=806167).

Another common use of SIV is to resolve issues with CL hardware reporting. In http://forum.corsair.com/forums/showthread.php?p=791779 you can see that the EnhancedPowerManagementEnabled registry edit had not been done and how this was resolved. This was also the situation in http://forum.corsair.com/forums/showthread.php?p=784898. With issues such as http://forum.corsair.com/forums/showthread.php?p=805646 it's less obvious to know what to do, though I sometimes guess correctly.

To use SIV to manually do the EnhancedPowerManagementEnabled registry edit simply uncheck it and then press [Restart]. None of the other Device Parameters need to be changed/set to zero though there are many misleading posts that say they should.

ALL of the files in the siv.zip release should be extracted to C:\Program Files\SIV\ or similar and SIV should be run from there.

Some users like AIDA64, others HWiFO, others OHM, others SpeedFan, ... With CL hardware CL was the only option and I feel users should have a choice. SIV is not a good choice for some users, though some have used SIV as they had hardware CL could not report. Examples are 2 x CLCC and the old Link Commander on Windows 10.

When initially using SIV there is a bit-of-a-steep learning curve. Once you are over this things get easier and some still use SIV even though the issue they had with CL has been resolved.

I added full CL support to SIV as CL did not report all my hardware. I also feel CL is resource hungry, not reliable, has no facilities to diagnose some common issues and needing to recreate profiles for every new release is unacceptable . Some advantages of SIV are:
  1. The SIV [USB Bus], [Link Devices] and [Link Status] panels allow the root cause of many hardware issues to be determined and resolved. If you need help with a CL hardware issue I recommend posting these screen shots.
  2. SIV will never have a "pretty UI" as this would promote SIV as a CL4 replacement and do not wish to promote SIV as a CL4 replacement.
  3. SIV is a native x64 application and uses less CPU and memory resources than CL4. In my testing SIV typically uses about 5% of one CPU @ 1.20GHz and CL4 uses about 92% @ 2.10GHz which is about 30 times as much. I tested with 4 x CLCC + 1 x Cooling Node + 3 x Lighting Nodes + 1 x AX1500i + 1 x AX760i + 2 x RM PSU + 1 x H110iGT + 1 x H100i + 1 x H80iGT + 1 x H80 . I could not use 2 x Cooling Nodes as CL4 does not support the old Commander they are connected to .
  4. When I tested against CL3 SIV typically used about 4% of one CPU @ 1.30GHz and CL3 used about 70% @ 1.70GHz which is about 20 times as much. I tested with 4 x CLCC + 2 x Cooling Nodes + 3 x Lighting Nodes + 1 x AX1500i + 2 x RM PSU + 1 x H110iGT + 1 x H100i + 1 x H80iGT + 1 x H80 + 1 x old Link Commander .
  5. SIV reports all 9 of my RAID and USB attached disk temperatures, CL reports none
  6. SIV reports all 6 of my motherboard fans, CL only reports 4
  7. SIV reports all 8 of my DIMM temperatures, CL3 reports none, CL 4.2.3.41 and earlier report them and then fail to update the temperatures.
  8. SIV reports all 8 of my PWM temperatures, CL reports none
  9. SIV reports all 4 of my CL Minis. CL 3.2.5695 and earlier did not.
  10. SIV reports all 2 of my old Link Commanders. CL only reports one and some CL v3.2 releases and CL4 report none. See http://forum.corsair.com/forums/showthread.php?p=794533.
  11. SIV reports all 4 of my GPU temperatures and fan speeds, CL did not. SIV can also change the GPU Illumination so I can tell which card corresponds to GPU-n.
  12. SIV reports multiple C-Link attached AXi + HXi + RMi PSUs and USB attached HXi + RMi + RM PSUs, CL3 can only report one. See http://forum.corsair.com/forums/showthread.php?p=740245.
  13. SIV controls the fan speeds on all 4 of my NVidia GTX 980 GPUs using 6 point Custom Curves. CL cannot.
  14. SIV will report the GPU fan PWM % if the GPU does not report the fan RPM. CL only reports the GPU RPM.
  15. SIV can use any temperature source to control PSU Fan Custom Curves. CL3 + CL4 do not support PSU Fan Custom Curves. See http://forum.corsair.com/forums/showthread.php?p=813546 and http://forum.corsair.com/forums/showthread.php?p=816945.
  16. SIV reports the Current, Average, Minimum and Maximum sensor values. CL3 + CL4 only report the Current value.
  17. SIV can use a PWM %, RPM or Custom Curve for the H110iGT and H110i pump, CL cannot. There seems to be a firmware issue with pump Custom Curves, so maybe this is why CL does not support this.
  18. SIV can use any temperature source to control all Asetek coolers. CL3 + CL4 can only use the cooler temperature on some (H80iGT + H100iGTX + H110iGTX). See http://forum.corsair.com/forums/showthread.php?p=795986.
  19. SIV can use multiple temperatures to control a custom curve. CL3 + CL4 can only use one temperature.
  20. SIV correctly reports systems with more than 32 CPUs, as CL3 + CL4 are 32-bit programs it may not. See http://forum.corsair.com/forums/showthread.php?p=833699 and http://forum.corsair.com/forums/showthread.php?p=782582.
  21. SIV reports and controls CL hardware on all of Windows 2000 to Windows 10. For Windows 10 I validate SIV on the insider builds.
  22. SIV reports and controls hardware from multiple companies. CL can only report and control Corsair hardware.
  23. SIV can be used in the Windows PE environment, so can report and configure CL hardware before Windows in installed on a new system.
  24. SIV correctly interlocks access to the motherboard hardware sensors and can safely be used at the same time as AIDA64, HWiNFO and SpeedFan. For how to check if a program uses the correct locks see http://forum.corsair.com/forums/showthread.php?t=141037.
  25. Interlocking access to Corsair Link hardware, the history:
    1. 22-Sep-2014 - I propose a lock and ask for CL3 to support this, see http://forum.corsair.com/forums/showthread.php?p=729115
    2. 31-Dec-2014 – by now HWiNFO + SIV correctly interlock access to CL hardware using the Global\Access_CorsairLink named mutex so both can report my CL hardware at the same time.
    3. 01-Aug-2015 - I created a thread showing all of AIDA64 + HWiNFO + SIV all reporting CL hardware and pushing for Corsair to implement support. This used to be http://forum.corsair.com/forums/showthread.php?p=792672 before Corsair deleted the thread .
    4. 19-Nov-2015 - Corsair specify CL4 uses "something similar", see http://forum.corsair.com/forums/showthread.php?p=820892 .
    5. 27-Jan-2016 - CL 4.2.0.162 does not use the Global\Access_CorsairLink named mutex , see http://forum.corsair.com/forums/showthread.php?p=833499.
    6. 24-Feb-2016 - I learn that CL does implement a lock, but it's a named Binary Semaphore rather than a named Mutex.
      1. Using a Binary Semaphore rather than a Mutex is a poor decision and indicates the CL4 developers need aditional training.
      2. I ask for it to be changed.
      3. I also point out all the errors in the Corsair supplied specification.
    7. 14-Mar-2016 - SIV V5.08 released which supports Global\CorsairLinkReadWriteGuard. Note I used Global\Access_CorsairLink to interlock access to the semaphore so SIV could recover CL4 messing up.
    8. 15-Apr-2016 - I contact Corsair again and explain why they should use a Mutex. They declined to change to use a Mutex.
    9. 12-May-2016 - I discover 4.2.3.41 sometimes exits while still holding the lock. Had Corsair used a Muted this would be impossible as the thead cleanup code in Windows would set the Mutex state to abandoned. This is why a Mutex should be used, see http://forum.corsair.com/forums/showthread.php?p=851701.
    10. 19-May-2016 - I recieve an e-mail from Corsair which specifies "Corsair will not be implementing the Mutex as requested and this is not a bug or issue as you call it."
    11. 23-May-2016 - I post http://forum.corsair.com/forums/showthread.php?p=854006 all about why Corsair should use a Mutex and I e-mail Corsair.
    12. 02-Jun-2016 - I get a reply to my e-mail and again Corsair decline to change to use a Mutex.
    13. 02-Jun-2016 - Corsair specify "In the future George will assign someone moving forward for you to contact with your concerns on an ongoing basis.". I am still waiting for this to happen.
    14. 20-Jul-2016 - Corsair notify me the next CL4 release will use a Mutex , but rather than using Access_CorsairLink a different name of CorsairLinkReadWriteGuardMutex is implemented meaning all of AIDA64 + HWiNFO + SIV needed to be changed.
    15. 21-Jul-2016 - CL 4.2.4.25 is released less than 24 hours after I was notified of the change.
    16. 26-Jul-2016 - CL 4.2.4.25 thread is created, see http://forum.corsair.com/forums/showthread.php?p=864130.
    17. 08-Aug-2016 - I discovered that CL 4.2.4.25 probably fails to correctly implement the defined locking semantics, see http://forum.corsair.com/forums/showthread.php?p=866159.
    18. 14-Aug-2016 - SIV V5.13 released which uses Global\CorsairLinkReadWriteGuardMutex rather than Global\Access_CorsairLink.
    19. 16-Sep-2016 - CL 4.3.0.154 is released and the issue I reported on 08-Aug-2016 and not been addressed, see http://forum.corsair.com/forums/showthread.php?p=871675
    20. 10-Feb-2017 - CL 4.5.0.55 is released and the issue I reported on 08-Aug-2016 has been partially fixed, see http://forum.corsair.com/forums/showthread.php?p=892949.
    21. 21-Mar-2017 - CL 4.6.0.86 is released and the issue I reported on 27-Feb-2017 has not been addressed, see http://forum.corsair.com/forums/showthread.php?p=896054.
    22. 06-May-2017 - I update this post with the itemised list showing all the avoidable issues there were with the Corsair Link 4 locking.
    23. Currently SIV can be used at the same time as CL 4.2.4.25 and later with minimal issues, but Corsair should fix CL4.
  26. SIV has the per Drive Minimum SMART setting that can be set to defer the SMART polling and allow Disk Drives to spin down. CL does not.
  27. SIV typically takes < 1 second to start-up (1.7 on my system as I have a UPS 2200) and start controlling CL hardware whereas CL takes far longer. On my ASRock X79 Champion it's about 30 seconds.
  28. SIV will automatically zero EnhancedPowerManagementEnabled and restart the USB device when -AIOCTL is specified so the user does not need to manually edit the registry or reboot the system.
  29. SIV will automatically re-initialise C-Link hardware about 30 seconds after resuming from sleep/hibernate when running in -AIOCTL mode, CL does not, see http://forum.corsair.com/forums/showthread.php?p=834755.
  30. SIV can estimate how much CL hardware can be supported. CL cannot and Corsair do not specify this information. See http://forum.corsair.com/forums/showthread.php?p=794763.
  31. The -UPDATE=<seconds> command line qualifier can be used to select the polling/update rate to use. The default is every 2 seconds.
  32. New versions of SIV use the same saved profile information as earlier ones. With CL you need to recreate the profile every new release.
  33. SIV does not suffer from "Duplicate Devices after PC Reset" as the profile information is accessed via the Corsair USB Bridge device Windows PnP ID which never changes. See http://forum.corsair.com/forums/showthread.php?t=141043.
  34. SIV will automatically update the profile when you move a Corsair Link USB Bridge type device to a different USB port.
  35. SIV does not cause high DPC Latencies (http://www.thesycon.de/deu/latency_check.shtml) when it is just monitoring and controlling hardware, though MmUnmapIoSpace() calls cause a few when doing [Save Local]. CL can cause issues, see http://forum.corsair.com/forums/showthread.php?p=826570.
  36. SIV does not constantly write information to the Windows Registry. See http://forum.corsair.com/forums/showthread.php?p=786625.
  37. SIV will automatically tell you when a new release is available. CL3 does not. See http://forum.corsair.com/forums/showthread.php?p=792729.
  38. SIV can be used to easily enable IgnoreHWSerNum. See http://forum.corsair.com/forums/showthread.php?p=793207.
  39. Using SIV I can display my CL hardware information on my GOverlay LCDSysInfo display.
  40. When there is an issue with SIV this is typically addressed with a SIV Beta release within a few days. Some CL issues have not been addressed after 28 months.
If you are just using SIV to control your CL hardware rather than specifying -AIOCTL on the command line you may wish to use [SIV Qualifiers] as below.




If you have an old Link Commander you may need to use Device Manager to update the driver. Below is how you can do this.
  1. from Device Manager Right/Click and choose Update Driver Software...
  2. press Browse my Compiler for driver software
  3. press Let me pick from a list of device drivers on my computer
  4. select the inbuilt USB Input Device
  5. press [Next]
  6. This is all that is needed to get SIV to report the old Link Commander connected devices.
  7. With CL this may not be so and on W10 TH2 + RS1 + RS2 if you get the endless reboot popups from CL 3.2.5742 see http://forum.corsair.com/forums/showthread.php?p=822047.
Attached Images
File Type: png SIV Corsair Link.png (99.1 KB, 3385 views)
File Type: png SIVDEF.png (29.2 KB, 2952 views)
File Type: png [SIV Qualifiers].png (58.9 KB, 19934 views)
File Type: png [Link Devices].png (32.0 KB, 14006 views)
File Type: png siv_sup.png (77.8 KB, 2285 views)
File Type: png [Link Limits].png (71.6 KB, 1731 views)

Last edited by red-ray; 08-16-2017 at 09:28 AM. Reason: History of locking + CLCP support


3 members found this post helpful.
  #2  
Old 05-05-2015, 03:40 PM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 777446
StealthGaming Reputation: 20
Default

Explain as why anyone should use your SIV software with their Corsair Hardware. Appears the only thing it does is automatically disable the Enhanced Power Management vs having to do it manually.

I've had a successfully working LINK with Windows 8.1 since 2013 by making simple modification to the USB registry.

For more information check out my post Successfully working LINK with Windows 8.1.


  #3  
Old 05-05-2015, 06:05 PM
wytnyt's Avatar
wytnyt wytnyt is offline
`~~`
wytnyt's PC Specs
 
Join Date: Jun 2012
Location: Roanoke, Virginia
Posts: 8,108
POST ID # = 777470
wytnyt wytnyt Reputation: 159
Send a message via ICQ to wytnyt Send a message via AIM to wytnyt Send a message via Yahoo to wytnyt Send a message via Skype™ to wytnyt
Default

Quote:
Originally Posted by StealthGaming View Post
Explain as why anyone should use your SIV software with their Corsair Hardware. Appears the only thing it does is automatically disable the Enhanced Power Management vs having to do it manually.

I've had a successfully working LINK with Windows 8.1 since 2013 by making simple modification to the USB registry.

For more information check out my post Successfully working LINK with Windows 8.1.
Ray and his hard work is offering users that cant get the Link software another option with his Siv so they can get their hardware working as intended.
The only dis-advantage I see with SIV over Link sw is the Link has much more exposure to the mass which in turn obviously generates more issues but siv appears to be having a good track record so far...
Even users with working Link software have another option to choose from if they want..
__________________
My 4930k Air 540 Custom Loop Build Pics
http://s39.photobucket.com/user/wytn...?sort=3&page=1

Last edited by wytnyt; 05-05-2015 at 06:11 PM.


2 members found this post helpful.
  #4  
Old 05-06-2015, 09:59 AM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 777578
StealthGaming Reputation: 20
Default

Everyone person has the right to a working software and choice to use what ever software they wish.

I'm a minimalist who likes my systems lean and clean without excess software bloating.

Corsair LINK software will work properly with a simple edit to the Corsair registry (disabling the power management features in Windows 8.1). Windows 8.1 power management improvements is the root cause of the issues people are experiencing with the LINK software. For more information see my post Successfully working LINK with Windows 8.1.

Last edited by StealthGaming; 05-06-2015 at 10:02 AM.


  #5  
Old 05-06-2015, 11:35 AM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 777588
StealthGaming Reputation: 20
Default

To funny, i've had a working LINK since the release of Windows 8.1 in 2013 on multiple computer without issue.

Same result can be accomplished without your software by a simple modification to the Corsair registry, hence "Disabling the power management features for the USB device". It is a know problem with Windows 8.1 suspending a USB device and not recharge it, this feature was developed for portable computers not desktops.


  #6  
Old 05-06-2015, 11:57 AM
wytnyt's Avatar
wytnyt wytnyt is offline
`~~`
wytnyt's PC Specs
 
Join Date: Jun 2012
Location: Roanoke, Virginia
Posts: 8,108
POST ID # = 777596
wytnyt wytnyt Reputation: 159
Send a message via ICQ to wytnyt Send a message via AIM to wytnyt Send a message via Yahoo to wytnyt Send a message via Skype™ to wytnyt
Default

Quote:
Originally Posted by StealthGaming View Post
To funny, i've had a working LINK since the release of Windows 8.1 in 2013 on multiple computer without issue.

Same result can be accomplished without your software by a simple modification to the Corsair registry, hence "Disabling the power management features for the USB device". It is a know problem with Windows 8.1 suspending a USB device and not recharge it, this feature was developed for portable computers not desktops.
The reg fix does work for some but not everyone ,others need different ''fixes'' which I think it all comes down to how the computer is setup and what all has been installed.When it comes to my builds,,each has Asus boards and relatively the same software programs so my issues are usually the same over each build.
__________________
My 4930k Air 540 Custom Loop Build Pics
http://s39.photobucket.com/user/wytn...?sort=3&page=1


1 members found this post helpful.
  #7  
Old 05-07-2015, 10:18 AM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 777809
StealthGaming Reputation: 20
Default

Quote:
Originally Posted by wytnyt View Post
The reg fix does work for some but not everyone ,others need different ''fixes'' which I think it all comes down to how the computer is setup and what all has been installed.When it comes to my builds,,each has Asus boards and relatively the same software programs so my issues are usually the same over each build.

The Issue with CLINK and Windows 8 has nothing to due with chipset nor mainboard. I've tested it thoroughly in the past 1 1/2 years on Z77, Z87, Z97, X79, X99 Mainboards by different Manufacturers and have had success with every platform after the Power Management Features were disabled. The problem lays within the configuration of the OS during installation for Windows 8.1.

Since Windows 8.1 is a multi platform software, there are many features enabled for portable pc and tablets that aren't used on desktops. Every experienced system builder knows by default Core Parking, Hibernation and power management features are all enabled. The issue with the CLINK installation is related to the coding being done incorrectly, hence not disabling the power management features.

Last edited by StealthGaming; 05-08-2015 at 03:06 PM.


  #8  
Old 05-07-2015, 01:40 PM
CircuitWizardry CircuitWizardry is offline
Registered User
 
Join Date: Jun 2014
Posts: 107
POST ID # = 777848
CircuitWizardry Reputation: 21
Default

Quote:
Originally Posted by StealthGaming View Post
The Issue with CLINK and Windows 8 has nothing to due with chipset nor mainboard. I've tested it thoroughly in the past 1 1/2 years on Z77, Z87, Z97, X79, X99 Mainboards by different Manufacturers and have had success with every platform after the Power Management Features were disabled. The problem lays within the configuration of the OS during installation for Windows 8.1.

Since Windows 8.1 is a multi platform software, there are many features enabled for portable pc and tablets that aren't used on desktops. Every experienced system builders knows by default Core Parking, Hibernation and power management features are all enabled. The issue with the CLINK installation is related to the coding being done incorrectly, hence not disabling the power management features.
If this is true, then why do we still not have a correctly functioning version of Corsair Link? Your comment is that the only issue causing Link to not work correctly are the registry entries. If this was true, any competent programmer could fix this in a day.

The truth, is that this isn't the only problem with Corsair Link, and lots of issues persist. Issues with not supporting multiples of some Corsair products, issues with foreign language settings in the OS, issues with not correctly reading temperature sensors attached to Link hardware, as well as issues with multiple GPU's, and not being able to set the LED color correctly on certain Link coolers. These were promised capabilities, yet they persist, even when the registry is manually edited.

I'm sure some people appreciate your information on the registry edits, but if you think that is all that is required in all cases, you are misinformed.


3 members found this post helpful.
  #9  
Old 05-07-2015, 03:04 PM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 777870
StealthGaming Reputation: 20
Default

Quote:
Originally Posted by CircuitWizardry View Post
If this is true, then why do we still not have a correctly functioning version of Corsair Link? Your comment is that the only issue causing Link to not work correctly are the registry entries. If this was true, any competent programmer could fix this in a day.

The truth, is that this isn't the only problem with Corsair Link, and lots of issues persist. Issues with not supporting multiples of some Corsair products, issues with foreign language settings in the OS, issues with not correctly reading temperature sensors attached to Link hardware, as well as issues with multiple GPU's, and not being able to set the LED color correctly on certain Link coolers. These were promised capabilities, yet they persist, even when the registry is manually edited.

I'm sure some people appreciate your information on the registry edits, but if you think that is all that is required in all cases, you are misinformed.

I would recommend you go to MSDN and search for USB device suspending and not charging when it presents itself as Human Interface Device (HID). Here is the article no. 2900614 dated 22 October 2013, it applies to Windows 8.1 & 8.1 Pro.

So no i'm not misinformed.

You should ask Red-Ray how effective his software would be without disabling the Power Management Features in Windows 8. The answer is not very effective and would operate the same as the Corsair LINK in current state.

Red-Ray please stop sending me private messages, anything you have to say can be presented in the open forum for review by all peers.

Last edited by StealthGaming; 05-08-2015 at 10:26 AM. Reason: Spelling error Peer not Pear


  #10  
Old 05-07-2015, 07:15 AM
Krachbummente Krachbummente is offline
Registered User
 
Join Date: Feb 2015
Posts: 12
POST ID # = 777782
Krachbummente Reputation: 10
Default

Quote:
Originally Posted by red-ray View Post
It's good to hear you have things working. If you have 64-bit windows you should use SIV64X.

I am not sure what VRM1 and VRM2 are. What GPU do you have? Does Menu->Machine->GPU Info list them? In SIV 5.00 you can use the maximum of multiple temperatures to control a custom curve. I may well miss a post to this general thread and feel posting on http://forum.corsair.com/forums/showthread.php?t=140665 would be a good idea.

Half the problem is SIV has about 360 things in the menu! I guess I could consider SIV64X -SIMPLE that hides most things as the CL reporting/control is only about 2% of what SIV does. My problem is that I never have an issue so don't know what changes would help new user's.
Hey,

thanks again for your reply in the Link discussion thread!
First thing: I have already tried using 64X before but the program somehow could not access my commander mini device. Surprisingly the 64X seems to work for today... I might check some things here again and give you some well-founded feedback later[...].

As for the GPU (mine is a R9 290 from ASUS) I was wondering whether there was any chance to implement the sensors of the voltage regulator modules (VRM). Graphics cards from AMD appear to have frequent issues with these modules heating up a lot.
And at the moment I miss a feature to integrate these temps (that are usually much greater than the core-temp, as for my VRM1) into my fan cooling setup.
Usually I read out these with GPU-Z and watch them manually - but I cannot affect them with my fan curve on the commander mini at the moment.
Note: the SIV GPU info does not show VRM temps at present.

Another thing I realized is that the tool does not properly work with my autostart (I need the CL fan control running all the time now).
I have already configurated an entry with the autostart feature (with -NOWIZARD -TRAY -CRLCTL set) but the tool somehow does not run after boot.
So I manually added it to my W7 autostart folder but the issue is still present and the .exe refuses to start at this point if not run manually by the user. Maybe this is another problem with the 32X mode, I will check this once more later again.

Regarding the GUI I would appreciate a more user-friendly interface - not being necessarily shortened but visually better structured and accessible. Maybe its that quantity of values im overwhelmed with but I could imagine maybe a clear main menu and some rasterization for the other screens and pages showing too much information without any graphical separation/structure atm.

I hope you understand what I am trying to tell you. My English is not the yellow from the egg, as we germans would say :)

Nonetheless, keep up the good work, SIV is obviously the much better CL!

Edit:
The autostart is still not working, even with the 64X version.
But at least the 64X itself does work now and can control the commander mini. I actually do not know what caused the problems I had with it earlier.

Last edited by Krachbummente; 05-07-2015 at 12:07 PM.


  #11  
Old 05-08-2015, 07:35 AM
Krachbummente Krachbummente is offline
Registered User
 
Join Date: Feb 2015
Posts: 12
POST ID # = 778024
Krachbummente Reputation: 10
Default

Quote:
Originally Posted by red-ray View Post
This evening I solved this issue on another system. The actual cause was that -CLRCTL had been specified rather than -CRLCTL. I spotted this as [Link Fans] was displaying BLUE rather than PINK blobs. This thread started out by saying which screen shots I need to see so it would be good if you posted them.
Actually I have the -CRLCTL set just as specified in the list of qualifiers.
Here is a current screen of my settings:



Note: only fan 1 and 3 are plugged in at the moment.

Regards,
Krachbummente


1 members found this post helpful.
  #12  
Old 05-08-2015, 01:11 PM
Krachbummente Krachbummente is offline
Registered User
 
Join Date: Feb 2015
Posts: 12
POST ID # = 778105
Krachbummente Reputation: 10
Default

Quote:
Originally Posted by red-ray View Post
Thank you, but the screens do not add up. [Link Status] is reporting the CLCC, but it's not listed on [Link Devices], further [Link Fans] has BLUE blobs, so -CRLCTL mode is not in effect. What do [USB Bus] and [About] report?

PS If you attach the .PNGs and insert links they are full size and can be read them in-line. Have a look at the first post in this thread.
I know that the device is officially not shown in the (both 32x and 64X) Link Devices tab but as far as my custom curve works I thought it should be fine. The USB Bus tells me that there is a Corsair Integrated USB Bridge. I could not find any suspicious information so far...



Are there any additional screens you need?

Last edited by Krachbummente; 05-08-2015 at 01:14 PM.


  #13  
Old 05-07-2015, 11:25 AM
mittelk mittelk is offline
Registered User
mittelk's PC Specs
 
Join Date: Feb 2014
Posts: 35
POST ID # = 777823
mittelk Reputation: 12
Default

I have SIV x64 controlling my H80i and AX860i, works great and have full control, CL was a nightmare on my machine. Great work Red Ray.


1 members found this post helpful.
  #14  
Old 05-08-2015, 04:15 AM
Technobeard's Avatar
Technobeard Technobeard is offline
Bearded Corsair Employee
 
Join Date: Oct 2012
Posts: 4,286
POST ID # = 777994
Technobeard Reputation: 68
Default

He meant PEER, not PEAR.
__________________
“Humor is reason gone mad.” - Groucho Marx
"I suggest a full frontal assault with automated laser monkeys, scalpel mines and acid." - Psychotic potato dwarf
"Do not meddle in the affairs of wizards, especially simian ones. They are not all that subtle." - Terry Pratchett


  #15  
Old 05-08-2015, 10:26 AM
StealthGaming StealthGaming is offline
Registered User
StealthGaming's PC Specs
 
Join Date: Oct 2014
Posts: 371
POST ID # = 778057
StealthGaming Reputation: 20
Default

Quote:
Originally Posted by Technobeard View Post
He meant PEER, not PEAR.

Thanks for pointing out the spelling error.


Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 01:03 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.