Result: The HWiNFO Kraken sensors get greyed out in the sensor window and stop refreshing half a second after the NZXT CAM splashscren pops up.
Result: HWiNFO Kraken sensors are displayed and refreshed. I just quadruple checked with several reboots, using latest HWiNFO 7.22-4731 and CAM 4.34.2. That does not work on my system I'm afraid. version Display version I would really love for HWiNFO to be able to handle the Kraken with NZXT CAM running, without needing my tool. d, -ShowDebugOutput (Default: false) Print HID connection r, -ShowRawDataOutput (Default: false) Print raw data bytes to t, -ClearTerminalOnRefresh (Default: true) Clears console output onĮvery refresh. Via autostart, to exit after a while onceĬAM has started in non-greedy-mode. c, -AutoCloseAfterSeconds (Default: 0) Automatically exit after n a, -AutoStartReadingMeasurement (Default: true) Automatically start i, -MeasurementRefreshInterval (Default: 1000) Interval to refresh the Run HWiNFO and NZXT CAM at the same time! Start this tool BEFORE starting NZXT CAM. This worked great for some short tests with burning the CPU, running cooling at max or min, etc. I just have to skip the readings where byte != 117. Again, I did not have time to analyze this in any detail.īut still, as long byte = 117, I can reliably read the liquid temps, no matter the order of applications starting, no matter CAM running or not. Once CAM started, the fluctuations seem to cool down, and byte seems to toggle between 117 and 255. The values in the byte array fluctuate wildly when CAM is starting, I suppose because of running some initialization. I didnt have time yet to dig up the pump/fan RPM data. The values are identical with HWiNFO when it reads data (which it does not in the screenshot), and perfectly matches the rounded value in CAM. In the screenshot, the left window shows the data of the 64 bytes read from the USBHID device.Īs long as byte = 117, the data is reliable for the liquid temp (32.4C in the screenshot).
#Nzxt cam button shortcuts code#
This is using exactly the same code used to prevent CAM from blocking HWiNFO, except for the data reading loop. I am able to reliably read the liquid temp, while HWiNFO does not read the Kraken sensor at all. It seems CAM is not completely at fault here. Keep pestering NZXT on all their support channels to fix shared access to the Kraken sensors! P.S.: That all this is even needed is 100% NZXT's fault, not HWiNFO's. I got the USB product id from the fine folks' git over at liquidctl. I'm sure all these Z models will work as they share the same USB product id. NZXT Kraken data will be shown and continually refreshed in it's own category in the HWiNFO sensor window, while NZXT CAM is working as usual. Take a look at the available command line parameters for more advanced usage (use the -help flag). Exit my program after NZXT CAM is started completely.Use the "-k" parameter to specify your Kraken (user either "X" or "Z").Run NZXT-Kraken-Sensor-Unlocker.exe from my download.NET Desktop Runtime as you will need it soon anyway) NET Runtime is all you need, but you are best served with the. The version attached to the thread is obsolete.
If there is still interest in this I will clean up the code and publish this in a more clean manner. Thanks to the hints in this old thread, I was able to sling a bit of code to finally beat NZXT CAM, and makeĬan anyone confirm this is working on your system?
0 kommentar(er)
