Droidzor Posted February 3, 2017 Share Posted February 3, 2017 The same here , intel 7700k and asus maximus ix code Link to comment Share on other sites More sharing options...
denisgcarvalho Posted February 3, 2017 Share Posted February 3, 2017 I had answers from Corsair: Criado por: Francois TS (2/1/2017 2:45 PM) Hello Denis, We'll have our team look into this. Please look forward to the next update. Link to comment Share on other sites More sharing options...
red-ray Posted February 3, 2017 Share Posted February 3, 2017 I had answers from Corsair: Criado por: Technical Support Rep (2/1/2017 2:45 PM) Hello Denis, We'll have our team look into this. Please look forward to the next update. I just don't get this. Why don't they just make a later C:\Program Files (x86)\CorsairLink4\cpuidsdk.dll available for download? It's not exactly rocket science, would take 30 seconds and this should fix the lack of Kaby Lake reporting in CL 4.3.0.154.I guess he just taked to Corsair Support.zip Link to comment Share on other sites More sharing options...
RiflemanFirst Posted February 3, 2017 Share Posted February 3, 2017 I just don't get this. Why don't they just make a later C:\Program Files (x86)\CorsairLink4\cpuidsdk.dll available for download? It's not exactly rocket science, would take 30 seconds and this should fix the lack of Kaby Lake reporting in CL 4.3.0.154. Maybe Corsair is developing a brand new version of Link from the ground up and not releasing a hotfix? That's my only reasonable explanation for the delays, but who knows? Link to comment Share on other sites More sharing options...
red-ray Posted February 3, 2017 Share Posted February 3, 2017 Maybe Corsair is developing a brand new version of Link from the ground up and not releasing a hotfix? That's my only reasonable explanation for the delays, but who knows? You mean just like with CL4? You may find the following quote of interest. I get the impression some within Corsair don't realise how poor CL4 is. As far as CL4 development goes, like I said, it's being rearchitected by a solid team. I can't say much more than that. I suspect a lot of your concerns will be alleviated by then and if they aren't, well, we'll keep working. Honestly, the interlock is an issue that even I've run into. Link to comment Share on other sites More sharing options...
RiflemanFirst Posted February 3, 2017 Share Posted February 3, 2017 You mean just like with CL4? You may find the following quote of interest. I get the impression some within Corsair don't realise how poor CL4 is. Good point. I never used CL3 since CL4 was already released when I bought my H115i. Link to comment Share on other sites More sharing options...
red-ray Posted February 3, 2017 Share Posted February 3, 2017 Good point. I never used CL3 since CL4 was already released when I bought my H115i. I also seem to recall the same fairy tale about CL3 resolving all the CL2 issues. I have just ordered a Kaby Lake CPU for my test system and it will be interesting to see if CL 4.3.0.154 does any better for me, I suspect it will ;): Link to comment Share on other sites More sharing options...
denisgcarvalho Posted February 4, 2017 Share Posted February 4, 2017 Unfortunately we have to wait for the corsair team. I think they are doing a new program Link to comment Share on other sites More sharing options...
red-ray Posted February 9, 2017 Share Posted February 9, 2017 I had answers from Corsair: Criado por: Technical Support Rep (2/1/2017 2:45 PM) Hello Denis, We'll have our team look into this. Please look forward to the next update. How come Corsair have not addressed this after 7 days when it took me maybe 7 minutes? Below is the original CL4 4.3.0.154 release and what I managed to get CL4 4.3.0.154 to report after < 7 minutes. Link to comment Share on other sites More sharing options...
Truitaman Posted February 10, 2017 Share Posted February 10, 2017 Hi red-ray could you share with us how did you fix the corsair link under z270 and kaby lake? thanks for taking care, Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Hi red-ray could you share with us how did you fix the corsair link under z270 and kaby lake? Why did you not just read my post? I specified how to do this some time ago and you need Corsair to do as I specified. What's totally outrageous is that CL 4.5.0.55 still has the issue :mad:. I just don't get this. Why don't they just make a later C:\Program Files (x86)\CorsairLink4\cpuidsdk.dll available for download? It's not exactly rocket science, would take 30 seconds and this should fix the lack of Kaby Lake reporting in CL 4.3.0.154. Link to comment Share on other sites More sharing options...
DevBiker Posted February 10, 2017 Share Posted February 10, 2017 Why did you not just read my post? I specified how to do this some time ago and you need Corsair to do as I specified. What's totally outrageous is that CL 4.5.0.55 still has the issue :mad:. Well, from reading your post, we need to get our paws on the CPUID SDK dll. Now, how do we mere mortals get our grubby paws on that so we can replace it? Link to comment Share on other sites More sharing options...
red-ray Posted February 10, 2017 Share Posted February 10, 2017 Well, from reading your post, we need to get our paws on the CPUID SDK dll. Now, how do we mere mortals get our grubby paws on that so we can replace it? I very much doubt you can unless Corsair provide it. I posted simply to show it would be trivial for Corsair to fix this. I have a test version as a result of working out what the issues with my DIMMs + NVMe disks not getting reported were and it would be unprofessional of me to pass it on. I have also known the CPUIDSDK developers for longer than I care to mention. It's a pity you can't use the CPUIDSDK that comes with CAM as that is a far later version that does support Kaby Lake, but each .DLL is tied to the product it's licensed for. Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 Hi,i setup new pc I7 7700k kaby lake + ASUS ROG Maximus IX Hero + Intel SSD 600p Series M.2 NVMe My corsaire 110i gt no report. Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 Siv report Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 Hi,i setup new pc I7 7700k kaby lake + ASUS ROG Maximus IX Hero + Intel SSD 600p Series M.2 NVMe My corsaire 110i gt no report. What does CL not report? I can see the H110iGT is reported, so guess it's the Intel SSD 600p Series M.2 NVMe that CL 4.5.0.00 fails to report that you are asking about. I guess SIV is reporting it, but I need to see Menu->Devices->SMART Drives to comment further. Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 This is the report but corsair link does not read any temperatures of z270 hero . Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 This is the report but corsair link does not read any temperatures of z270 hero . Once Corsair release a later cpuidsdk.dll then I expect your NVMe disk will be reported as will the missing Kaby Lake information. This may not address the motherboard though. I advise you to check what HWM reports and if needed work with the HWM/CPUIDSDK developers to get support for your motherboard added to HWM. This will mean an even later cpuidsdk.dll will be able to report your motherboard. If you post the HWM screen shot and Save Monitoring Data file I could comment further. Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 this is the reportHWMonitor.txt Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 NCT6793D support looks to be there, but I am none too sure how good it is. VCore being 2.592 is obviously incorrect. I need to see one screen shot showing both as above + Menu->Hardware->Sensor Debug to tell more. I don't what two .PNG files, but rather one showing both programs so the values should be the same. I fixed a couple of NCT6793D Maximus IX reporting issues in SIV 5.16 so it would be ideal if you used the latest 5.16 beta, do Menu->File->Download->SIV Beta to get it. Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 As I suspected HWM needs improvement. I advise you to e-mail it's developers attaching the screen shot + HWMonitor.txt file and ask if they can improve things. It should be trivial for them to report TA CPU BIOS + TE CPU PECI, add the missing fan and correct the voltages. Most of the other information is reported via the EC (Embedded Controller) and is far harder to report. Is the SIV 5 AMP Fan the correct name? Is that fan plugged into the H_AMP header ? Link to comment Share on other sites More sharing options...
URSU76 Posted February 11, 2017 Share Posted February 11, 2017 If the SIV 5 AMP Fan the correct name? Is that fan plugged into the H_AMP header ? No i don,t have fan plugged in to the H_amp is plugged in to Aio_pump header Link to comment Share on other sites More sharing options...
red-ray Posted February 11, 2017 Share Posted February 11, 2017 If the SIV 5 AMP Fan the correct name? Is that fan plugged into the H_AMP header ? No i don,t have fan plugged in to the H_amp is plugged in to Aio_pump header Thank you. I should have fixed the name in Beta-23, please will you post new [sensor Debug] screen shots? Ideally leave SIV running for >= 10 minutes so there are a reasonable number of samples. Better still post/e-mail me the save files, see http://forum.corsair.com/forums/showthread.php?p=788225 for how to do this. Do all the other fan names look to be correct? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.