May I ask what you mean by custom sensors? Do you mean just things like setting a color and thresholds for Red color, units, etc. I am running v7.15-4640 beta and have not noticed any issues.
Ah OK. Thanks for clarifying that. I recall reading about this but have never tried to set one up. Is this something that you set up in HWINFO or are you doing it outside of the program? Just curious.No. There are physical sensors and derived custom sensors. Custom sensors can be created in the windows registry as new sensors that are mathematical manipulations of physical sensors or other custom sensors. You can do simple operations of addition, subtraction, division and MIN and MAX on a set of sensors.
Custom user sensors in HWiNFO
HWiNFO since version 6.10 introduces a new feature - ability to display custom user sensors in the sensors window. This feature allows users with basic programming skills to show any sensor values. This might be useful in case of custom-made devices, or sensor values not implemented in HWiNFO by...www.hwinfo.com
Ah I see. So the math operations happen in the registry, and the result can be displayed in HWINFO like any other sensor. I am going to try this. Aquasuite has a lot of built in math and logic functions that can be performed on sensor data in all sorts of interesting ways. I never thought about doing it this way. I want to know what math / statistical / logic functions are supported in the Value line. I'm going to read up at bit on editing the registry in this way and see what trouble I can get myself into. Thanks for sharing this.
Thanks for the tips. I figured the sensor names in the quotes must match the names in HWINFO so it can pull in the values to perform the math operations on. I also was hoping for some statistical functions and maybe some Boolean functions, but maybe am getting carried away. Even with the limited functions available, there are still a lot of possibilities.Only the operations I listed.
np
If you do play with it, keep this in mind:
1. The names of the sensors you use in a custom user sensor must be those that are displayed in the HWInfo sensor display. So if you have renamed a sensor you must use its new name.
2. The sensors used in the custom user sensor must be visible, they cannot be hidden.
3. Arithmetic operations flow from left to right, as you can see in my examples for averages.
Wish there were and AVG function for averages that would take the average of all the sensors that are valid.
Can you please check if this build fixes the custom sensors? www.hwinfo.com/beta/hwi64_715_4642.zip
I have a flow meter using a fan input that I previously (715.4625) was able to rename from RPM to mL/M.
I can no longer rename it with 715.4640 or 716.4650.