Wattool 0.92 is a program designed for users who are interested in overclocking and tuning their graphics cards, specifically those in the RX 400 series. It is a simple and secure tool that offers a variety of features to help users achieve better performance and efficiency.
The program allows users to monitor the performance of their graphics card and adjust various settings, such as core and memory clocks, voltage, and power limit, to achieve higher performance. It also has a VRM tuning feature that can help optimize the voltage regulation module to ensure stability during overclocking.
- Overclocking: Wattool 0.92 allows users to adjust core and memory clocks, voltage, and power limit to achieve higher performance.
- Monitoring: The program includes monitoring capabilities to help users keep track of their graphics card’s performance.
- VRM tuning: Wattool 0.92 has a VRM tuning feature that can help optimize the voltage regulation module to ensure stability during overclocking.
- Simple and secure: The program is designed to be simple and secure, making it easy for users to use.
- Compatibility: Wattool 0.92 is specifically designed for the RX 400 series of graphics cards and does not work on NVIDIA cards.
- Timing shift: The program allows users to shift timings when setting up with an additional program.
- Dedicated to overclocking: Wattool 0.92 is a program dedicated solely to overclocking, making it a convenient tool for users who are interested in this aspect of graphics card performance.
- VRM monitoring / configuration.
- Profile support.
- Small and simple interface.
- GPU Frequency and Voltage: Works similar to WattMan. The clock is not limited to 5 MHz increments, but the voltage is limited to 6.25 mV steps (rounding mode is enabled, so 976 mV will result in 981.25 mV).
- Memory clock and voltage: works similar to WattMan. The voltage is not the actual memory voltage (which is set at around 1.5V or needs to be hardwired). The second circuit of the voltage controllers is not used, so it is doubtful whether the memory controller has its own dynamic voltage plane.
- Fan and power settings: nothing special here. The minimum fan speed is not limited. It is possible to set values below the WattMan limit of 1040 rpm. Minimum RPMs are not used directly
- Standard Monitoring: These values should be identical to the values displayed in WattMan, and monitoring has (almost) no performance impact.
- I2C access: currently only works for IR3567B controller at line 4, address 8 on RX470/RX480 cards. Access is synchronized with other tools such as GPU-Z or HWiNFO, which can sometimes lead to missing readings. I2C access has a big performance impact and causes stuttering (even when dragging a window on the desktop). Changes in I2C settings are not permanent. They will return to their default values after the VRM is turned off.
- VRM Monitoring: Disabled by default. Reading values is not atomic, so VID and VOUT are not always in sync. VDDC resolution is only 7.8mV.
- Load line calibration: Eliminates voltage drop (I get VOUT = VID + – 1mV on my card). Actually not very helpful.
- Current Power Demand Scale: Scales the current reported by the VRM. On the RX480 reference, the default value is 60 (hexadecimal). If you set it to 20 you will see that GPU-Z reports half the power consumption. This will double the available power before you hit the power goal. But other things will also only see half the current. Don’t rely on current protection to work with this setting. The encoding of this value is unknown, and non-reference cards use different values. If you want to bypass the power limit, it might be safer to use EMBD or a custom bios (der8auer unlocked airbus for reference cards signed by AMD).
- Voltage Offset: -300mV to +300mV available (not tested across full range). The input is decimal and multiplied by 6.25 mV. So the valid range is -48 to 48
GPU clock and voltage: Functions similarly to WattMan. Clock speeds can be adjusted in increments smaller than 5 MHz, while voltage adjustments are limited to steps of 6.25 mV (rounded up, so 976 mV becomes 981.25 mV).
Memory clock and voltage: Operates in a manner similar to WattMan. The voltage setting does not directly affect the memory voltage (which is typically fixed at around 1.5 V or requires a hardmod). It’s unclear if the memory controller has its own dynamic voltage plane since the voltage controller’s second loop is unused. My assumption is that the set voltage serves as a lower limit for the core voltage. When overclocking memory, it is recommended to check for any memory errors using tools like HWiNFO.
Fan and Power settings: Nothing particularly noteworthy here. The minimum fan rpm is not constrained; values lower than WattMan’s limit of 1040 rpm can be set. The minimum rpm is not used directly. It appears that values below 2200 are scaled by 2/3. For instance, 2500 results in 2200 * 2/3 + 300 = 1760 (as shown in the screenshot), while 1800 would give 1800 * 2/3 = 1200.
Standard monitoring: These values should be identical to those displayed in WattMan, and monitoring them has (almost) no impact on performance.
I2C access: Currently, it only functions for the IR3567B controller on line 4 address 8 on RX470/RX480 cards. Access is synchronized with other tools like GPU-Z or HWiNFO, which can occasionally result in missing readings. I2C access significantly impacts performance and can cause stuttering, even during simple tasks like dragging a window on the desktop. Changes to I2C settings are not saved persistently and will revert to defaults after the VRM is powered down.
VRM monitoring: By default, it is disabled. The values are not always in sync, as reading VID and VOUT is not atomic. The VDDC resolution is only 7.8 mV.
Load Line Calibration: Helps eliminate voltage drop (on my card, I observe VOUT = VID ± 1mV). However, it is not particularly useful in practice.
Phase gain: In the reference RX 480, the first three VRM phases are connected to the 6-pin connector, while the remaining three phases are connected to the slot. After reviews revealed power draw exceeding 80 W from the slots, AMD implemented a fix that shifted the load to the 6-pin connector. The default value for this setting is DDD000 (in hexadecimal). The maximum possible shift would be FFF000. Distributing the load equally (000000) slightly improves VRM efficiency. With 000000, I observe around 3°C lower VRM temperatures, and power savings could be in the range of 2-3W. On non-reference cards, all or most phases are likely connected to the 8-pin, rendering this setting irrelevant.
Current scale: Adjusts the current reported by the VRM. The default value for the reference RX480 is 60 (in hexadecimal). Setting it to 20 will result in GPU-Z reporting approximately half the power draw. This effectively doubles the available power before reaching the power target. However, other components will also observe only half the current. It should be noted that over current protection may not function properly with this setting. The encoding of this value is unknown, and non-reference cards use different values. If you wish to bypass the power limit, it is likely safer to use EMBD or a custom BIOS (such as der8auer’s unlocked air BIOS for reference cards, which is signed by AMD).
Voltage offset: Can be adjusted from -300mV to +300mV (not tested across the entire range). The input is in decimal format and is multiplied by 6.25mV. Therefore, the valid range is -48 to 48.