|
Post by siv on Oct 10, 2018 4:50:33 GMT
Thank you for the links and I have looked at the code and it all seems simple enough. I have just adjusted the SIV 5.34 code to report the firmware version using Beta-17 please check it's correct in the tooltip.
I also noted the script uses a timeout of 2000 ms so I have also changed 5.34 to force a minimum of 1500 ms.
|
|
|
Post by llamatron on Oct 10, 2018 9:37:10 GMT
Ha the fact fact the timeout is so high in thoses kinda makes me feel better, was starting to wonder if I didn't have a faulty unit or system.
Is there any way of getting mail alerts when there's new posts in a thread on thoses boards ? It would make following new releases easyer.
|
|
|
Post by siv on Oct 10, 2018 9:55:12 GMT
Is there any way of getting mail alerts when there's new posts in a thread on thoses boards ? Probably, but as yet I don't know how to. If you find out how to please post how to do this.
You could setup Menu->File->Latest Releases to automatically check once an hour as specified in the Forgotten Manual. BTW have you read it?
|
|
|
Post by llamatron on Oct 10, 2018 11:41:09 GMT
You could setup Menu->File->Latest Releases to automatically check once an hour as specified in the Forgotten Manual. BTW have you read it?
I did read only the part at the start about AIO control, but been stuck trying to understand what was wrong when I saw that the fan/pump speed didn't change, now I see it tells about the supported hardware further in the manual. But to my defence, the friend who told me about SIV was pretty positive that it would be able to control the Kraken ! My bad for not fully RTFM before diving in config.
Just downloaded beta 17, and the firmware version show in the tooltip, it's displayed differently than in CAM, but I guess it doesn't matter much (SIV says V4.0.03, and CAM says V4.03).
|
|
|
Post by siv on Oct 10, 2018 14:15:05 GMT
it's displayed differently than in CAM, but I guess it doesn't matter much (SIV says V4.0.03, and CAM says V4.03). It's easy enough to adjust, but I wonder what does liquidctl report as the version?
|
|
|
Post by llamatron on Oct 10, 2018 14:24:54 GMT
liquidctl reports 4.0.3
just figured liquidctl doesn't need a specific driver to be installed like krakenx, just Python and libusb, guess I'll use that for now.
|
|
|
Post by siv on Oct 22, 2018 8:06:34 GMT
Thank you, how did you manage to update the firmware? CAM 3.7.3 says I should update then fails to update it! All in all CAM seems rather poor, it only reports 4 of my 6 motherboard fans and can't report any my disk temperatures! Using SIV 5.35 Beta-08 or later please will you post a dump from your X62? I suspect you may wish to look at Link LEDs. Attachments:
|
|
|
Post by llamatron on Oct 24, 2018 19:10:05 GMT
I updated mine through CAM, it worked at first try, it's weird that yours doesn't. And yes, CAM is really very bad, they even require you signup to their site to be able to save your fan/pump curves, use their (pretty useless) overlay, and... save some graphs of your FPS over time to their server... That's why control through SIV would be a godsend for a lot of people.
Here is my dump (without CAM running):
And good job on the LEDs btw
|
|
|
Post by siv on Oct 30, 2018 18:19:02 GMT
How does 5.35 Beta-14 do please? Attachments:
|
|
|
Post by llamatron on Oct 31, 2018 23:14:09 GMT
I can't get SIV to change the speeds, tried the pump and the fans with custom curve and pwm values, he's my :
|
|
|
Post by siv on Oct 31, 2018 23:46:17 GMT
I can't get SIV to change the speeds, tried the pump and the fans with custom curve and pwm values Given Apply does not have focus did you press it? Below is what I get and I now also have the V4.0.03 firmware so I can't think what else it could be. I also noticed the V4.0.03 firmware is even slower and Link Status now reports Peak Times 1.370 when it was 0.950 with the V4.0.02 firmware.
|
|
|
Post by siv on Nov 1, 2018 12:23:51 GMT
I have logged the 214197 support call with NZXT about the appalling firmware performance attaching the following screen shot, pointed out the H115iPro is much faster and will see what they say.
|
|
|
Post by llamatron on Nov 1, 2018 17:19:08 GMT
Given Apply does not have focus did you press it? Below is what I get and I now also have the V4.0.03 firmware so I can't think what else it could be. I also noticed the V4.0.03 firmware is even slower and Link Status now reports Peak Times 1.370 when it was 0.950 with the V4.0.02 firmware. Yes, I tried for a good amount of time, with the aio control guide to figure if I was doing something wrong, but I get no sign of fan or pump speed change (which I would hear).
|
|
|
Post by siv on Nov 1, 2018 17:36:06 GMT
Given Apply does not have focus did you press it? Below is what I get and I now also have the V4.0.03 firmware so I can't think what else it could be. I also noticed the V4.0.03 firmware is even slower and Link Status now reports Peak Times 1.370 when it was 0.950 with the V4.0.02 firmware. Yes, I tried for a good amount of time, with the aio control guide to figure if I was doing something wrong, but I get no sign of fan or pump speed change (which I would hear). Please will you use CAM to set different PWM % and check the speeds change. Assuming they do exit CAM and try SIV again. Can you get a USB trace of what CAM sends? I used spam://www.usblyzer.com/
|
|
|
Post by llamatron on Nov 1, 2018 19:44:21 GMT
It works in CAM, but I had uninstalled it for a while. I have been using liquidctl with a small startup script, it works perfectly and doesn't need to have anything running as it sends the curve to the device with interpolated 2°C steps. Unfortunately, still no luck with SIV. I noticed that when I press apply the PWM value I had set resets to 0, if it can be usefull info.
I have been trying to get an USB log with USBlyzer, and Wireshark as I know it a bit for using it for networking, but didn't really manage to be sure I was logging relevant informations. When CAM runs there is a lot of traffic.
|
|
|
Post by siv on Nov 1, 2018 20:40:08 GMT
It works in CAM. I have been trying to get an USB log with USBlyzer. What works with CAM ? I need to see the USB log and you need to tell be what you did. It's just the issue of the out packets, 4C are for the LEDs and 4D for the Pump/Fans. 02 4D 00 00 19 ... sets the fan to 25% PWM. See the attached. Attachments:
|
|
|
Post by llamatron on Nov 1, 2018 22:19:44 GMT
Here's the usblyzer output file, apparently it's not filtered, but you can open in usblyzer and set the filter.
I did:
- set fan fixed speed to 100%, then 50%, then 70%, then 35% - set pump fixed speed to 100%, then 70%, then 60%, then 80%
Attachments:KrakenCamFixed.ulz (382.5 KB)
|
|
|
Post by siv on Nov 2, 2018 11:17:36 GMT
All the packets are getting traced 3 time, just select USBHUB3 and deselect USBPcap + ACPI.
CAM is sending much the same as SIV, but SIV sends 02 2D 80 ... rather than 02 2D 00 ... as by using 80 rather than 00 the value sticks. When SIV sent 00 the speed changed and then reverted after several seconds. What CAM seems to do is keep sending the command every few seconds.
Please get a trace of what happens when you press Apply.
|
|
|
Post by llamatron on Nov 3, 2018 16:58:07 GMT
Do you mean to uncheck them in the device stack of the USB device ? I see HidUsb, ACPI, and USBHUB3 there, I assume it's what you mean (I changed motherboard model yesterday too, which might have changed names, probably not optimal to change it while testing stuff, but I had to). But when I select only USBHUB3 it looks like everything is logged twice.
There's a fair amount of traffic going on, so it's hard to tell what's triggered by applying, but by selecting only the output I can see that when I press Apply to set the pump speed to 85%, it sends 02 4D 00 55 00 00 00 ...
The fact it keeps sending the message every few seconds and that it sends a message for an apparently "temporary" setting reminds me some complains I red, about CAM and the Kraken controlling the fans using software, instead of sending the curve and letting the hardware change speeds, like liquidctl seems to do, as it doesn't seem to have any process running after setting the curve. The problem with software control is that in case of heavy computer stress, the software could freeze and stop adjusting the speed.
|
|
|
Post by siv on Nov 3, 2018 17:47:14 GMT
when I press Apply to set the pump speed to 85%, it sends 02 4D 00 55 00 00 00 ... I doubt it does and that it actually sends 02 4D C0 00 55 00 00 00 as for what you need to setup then I can't see your screen so you need to post a screen shot, in general telling me what you see is not ideal and with a screen shot I may notice things you have not mentioned. Below the highlighted line is setting the pump speed and the out 5 lines later is the fan speed. I did not have any filters and as you can see all the transfers were successful. Attachments:
|
|
|
Post by llamatron on Nov 3, 2018 18:44:44 GMT
Sorry for that, and btw, just to be sure, you want me to test with CAM right ? Here's the capture when applying 75% on the pump, then 44% on the fan, and the corresponding Usblyzer file.
Attachments:Pump75Fan44.ulz (24.5 KB)
|
|
|
Post by siv on Nov 4, 2018 12:26:54 GMT
Sorry for that, and btw, just to be sure, you want me to test with CAM right ? No, you had already provided a trace of what CAM sends. I said "Please get a trace of what happens when you press Apply" and meant Apply on the SIV Link Fans panel so we can check SIV is sending what it should and the transfer worked. You should also select the out transfer so the whole of the 64 byte packet is in visible in the raw data at the bottom of the screen.
|
|
|
Post by llamatron on Nov 4, 2018 13:27:54 GMT
Here are the capture of the SIV settings when I press apply, and the two out messages in USBlyzer:
|
|
|
Post by siv on Nov 4, 2018 13:56:25 GMT
Something is very strange. The SIV transfers seem to work and send the same data as on this system, so the fan/pump speeds should change!
I wonder if nzxt-kraken-x-3rd-generation.md is putting the Kraken into a strange state and SIV needs to send a command to enable PWM % control.
Did you run it after running CAM and before running SIV? What happens in you set the fan + pump PWM % with CAM, exit CAM and run SIV? What about if you re-flash the firmware and don't run nzxt-kraken-x-3rd-generation.md?
|
|
|
Post by llamatron on Nov 4, 2018 16:23:55 GMT
I assume that by nzxt-kraken-x-3rd-generation.md you mean liquidctl. Yes it looks like you're right and it's doing something to the Kraken to make it "hardware controlled": after I disabled my startup script, turned the computer off, then turn it back on, SIV can change the PWM values and the Kraken changes its speeds. Note that just rebooting the computer wasn't enough.
CAM doesn't seem to be affected, maybe the way it sends its messages is ment to temporary override hardware control ?
|
|
|
Post by siv on Nov 4, 2018 19:29:07 GMT
Thank you, the mystery is half solved. My guess is that CAM send something to undo what liquidctl sets.
A reboot won't restart the Kraken firmware, but power cycling the system will and I suspect when restarted the Kraken can then be controlled.
I will get a trace of what CAM sends on start-up tomorrow and get SIV to do similar.
|
|
|
Post by llamatron on Nov 4, 2018 19:41:37 GMT
CAM is sending much the same as SIV, but SIV sends 02 2D 80 ... rather than 02 2D 00 ... as by using 80 rather than 00 the value sticks. When SIV sent 00 the speed changed and then reverted after several seconds. What CAM seems to do is keep sending the command every few seconds. That's what makes me think it's rather the purpose of thoses 00 messages, to have temporary adjustements, that would explain why it keeps sending them. That way when cam is closed (or crashes or any other problem preventing it to send the message), the Kraken resumes to whatever hardware profile is loaded, which is safer than having the value set forever. Might be interesting to have the option to send a profile to the hardware in SIV.
|
|
|
Post by siv on Nov 4, 2018 23:09:04 GMT
That's what makes me think it's rather the purpose of thoses 00 messages, to have temporary adjustements, that would explain why it keeps sending them. That way when cam is closed (or crashes or any other problem preventing it to send the message), the Kraken resumes to whatever hardware profile is loaded, which is safer than having the value set forever. Might be interesting to have the option to send a profile to the hardware in SIV. SIV can't sensibly use a hardware profile as AFAIK the protocol does not support using an external control temperature and SIV needs the protocol to support this so that any temperature can be used to control the pump and fan speeds. Many SIV users use a synthetic temperature to control the fan/pump speeds. I suspect if I get SIV to send as follows then the speeds may change and stick after liquidctl has been running. Please try 5.35 Beta-19 or later and let me know what happens. D:\SIV>siv64x -dbgaio -aioctl -exit=8 | find " -> 02 4D" Kraken @ 22:39:30.789 seq 04 -> 02 4D 40 00 3C 00 00 00 - note: only get's sent for the first pump speed setup Kraken @ 22:39:31.009 seq 05 -> 02 4D C0 00 3C 00 00 00 Kraken @ 22:39:31.119 seq 06 -> 02 4D 00 00 19 00 00 00 - note: only get's sent for the first fans speed setup Kraken @ 22:39:31.329 seq 07 -> 02 4D 80 00 19 00 00 00 I suggest setting both to 100%, press Save, exit SIV, run liquidctl, end liquidctl and finally restart SIV.
|
|
|
Post by llamatron on Nov 5, 2018 12:42:27 GMT
It changes the speeds when launching SIV, but it doesn't stick, and trying to apply settings from the Link Fans page doesn't work.
|
|
|
Post by siv on Nov 5, 2018 20:24:24 GMT
Thank you and I feared this would happen. I have run out of ideas for now so if you wish to use SIV to control then don't run liquidctl.
|
|