Load Line Calibration: eliminates voltage drop (on my card i get VOUT = VID +- 1mV).
Reading the values is not atomic, so VID and VOUT are not always in sync. VRM monitoring: is disabled by default.They will revert to defaults after the VRM is powered down. Changes to I2C settings are not persistent. I2C access has a large performance impact and causes stuttering (even for dragging a window on the desktop). Access is synchronized with other tools like GPU-Z or HWiNFO, which can sometimes result in missing readings. I2C access: is currently only working for the IR3567B controller on line 4 address 8 on RX470/RX480 cards.Standard monitoring: these values should be identical to the values displayed in WattMan and there is (almost) no performance impact caused by monitoring.My estimate is that values below 2200 are scaled by 2/3. Minimum fan rpm is not limited, I can set values below WattMan’s limit of 1040 rpm. Fan and Power settings: nothing special here.If you overclock the memory, always check for memory errors (can be done with HWiNFO). My guess is that the voltage set here simply is a lower limit for the core voltage. The voltage controllers second loop is not used, so it is questionable, whether the memory controller has an own dynamic voltage plane. The voltage is not the actual memory voltage (which is fixed to about 1.5 V or needs a hardmod)). Memory clock and voltage: works similar to WattMan.Clocks are not restricted to 5 MHz increments, but voltage is limited to 6.25 mV steps (rounding mode is up, so 976 mV will result in 981.25 mV). GPU clock and voltage: works similar to WattMan.Data is entered through the command line. * For each processor, you can add its own, individually configured profile. They can also be loaded and saved through the graphical interface. Profiles can be passed as arguments via the command line.Voltage variation in the range of -300 … + 300 mV.