1. I decided to skip uptimes, as without a specific time-based format the resulting displayed values would be fairly ugly (e.g. 752.342 h, or even worse if I were to stick to SI seconds).
2. Perhaps a middle-ground of polling for new devices, but not new sensors? Also, for users not using any...
Another small thing I notice: HWiNFO is not able to recover if a custom sensor (i.e. its registry key) goes away, even after if has become available again. The real world scenario is the user closes or experiences a crash in the third-party application, which clears its stuff from the registry...
1. But what is the appropriate format for time/uptime values?
2. Would it be possible to HWiNFO to check for new custom devices/sensors after it has started? Otherwise users that autostart HWiNFO will need to orchestrate the initialization order by themselves, which is tricky. A single...
Hi Martin,
I started to implement a "export to HWiNFO" mode in liquidctl, and while it already mostly works I still have a few issues:
Is it possible to pass time (uptime) data to HWiNFO and, if so, how?
It seems that HWiNFO must be started after the application providing the custom sensors...
Both CAM (the official software by NZXT) and krakenx report equal temperatures to me.
Comparing the two and also checking the raw USB messages, krakenx's conversion seem to work well during both steady state and transient tests: byte1 + 1/10*byte2.
The division by 10, which could otherwise...
Great to know. Looking forward to the updated version.
I would still appreciate a recommendation for a good USB analyzer, because I would like to add krakenx support for setting fan/pump profiles.
Pump and fan speeds are working perfectly : )
The liquid temperature is slightly off though.
What USB tracing/sniffing tool you recommend?
Edit: It took me so long to reply because I was trying to get Microsoft Message Analyzer to work; but, in the end, it shows everything except the...
I am sorry, I actually meant this open-source project: https://github.com/KsenijaS/krakenx
My point is that the protocol does not appear to have changed too much, since the small part that tool needs still works.
I do not have experience developing software that interacts with USB devices...
I would love to help! Maybe we can do a collaboration of sorts?
By the way, krakenx can still read (seemly sensible) fan and pump speeds out of my unit.
I have been experiencing the same issue with a brand new unit. Debug log attached.
Firmware version is 4.0.2.
Edit: could not attach the log, so uploaded it to Google Drive: https://drive.google.com/file/d/1tfbAqjTxGK30InZwSyIjqM-Rhlp4m-EC