VNISH GLOBAL / Field guide
RPM, fan %, target: read the cooling signals
Start with the role of the number: a requested target, a reported reading or a control condition. Then check its unit and measurement point.
This map explains documented interface relationships, not a device wiring diagram. Fields and sensors depend on the model, firmware build and cooling mode. Do not transfer settings between Air, Hydro and Immersion.
Control map
The selected mode changes what the fan percentage means. Read the path left to right; the text carries the same information as the arrows.
Auto: a temperature goal drives adjustment
- Inputs
Target Temperature (°C): requested goal.
Chip temperature (°C): feedback reading. - Control
Automatic fan adjustment.
Fan Speed Limit: allowed percentage range. - Readback
Speed (%): reported fan level.
Fan RPM: reported rotations per minute.
Manual: a percentage is set directly
- Input
Fan Speed (%): fixed requested setting.
- Control
Manual fan control does not automatically maintain a chip-temperature target.
- Readback
Read fan RPM and chip temperature separately. The setting is not a temperature reading.
Separate condition: Critical Chip Temperature
This is a protection threshold associated with stopping mining in the documented logic. It is neither the normal temperature target nor a current sensor reading.
Control definitions: HashCore Mining, Cooling and Control sections.
Field dictionary
| Field / unit | What to keep with the value |
|---|---|
| Fan RPM / rev/minReading | Keep the fan identifier. A status word such as Error is not a numerical RPM reading. |
| Speed / %Reading or setting | On Overview it is reported fan level; Fan Speed in Manual is a setting. Keep the screen and mode. |
| Target Temperature / °CRequested goal | Compare it with the corresponding chip-temperature reading, not with a PSU or liquid temperature. |
| Chip temperature / °CReading | Keep the chip or board label and any min/max qualifier. Do not silently turn a range into one number. |
| PFC / LLC / °CReading | PSU component temperatures, when the PSU supplies this telemetry. Keep PFC and LLC distinct. |
| Inlet / outlet / °CReading | Liquid measurement locations in the documented Immersion view. The same unit does not make them chip temperatures. |
| Critical Chip Temperature / °CProtection condition | Record it as a threshold, separate from the actual temperature and the ordinary target. |
Field definitions: HashCore Overview, PSU, Cooling and Hashboards sections.
Keep the measurement point
A temperature needs a location as well as a unit. Label each reading before comparing it. The groups below are not a promise that every miner exposes all of these fields.
Chip / board
Which chip or board? Minimum, maximum or another labelled value?
PSU
PFC or LLC? Is the field actually reported?
Liquid
Inlet or outlet? Which labelled block or circuit?
An unavailable or absent field stays “not available” in your notes. Do not fill it with zero or substitute a temperature from a different location.
One useful observation
Use the same observation structure twice, at the times you want to compare. Fill only the fields your interface actually reports. This is an observation note, not a configuration form.
Time and time zone:
Model / firmware build:
Screen / cooling mode:
Field label and location:
Role: target / reading / condition
Value and unit, or not available:If two records differ, check whether their label, mode, location and time context match before explaining the difference. Preserve status words as status words.
Common questions
Does 50% mean half the maximum RPM?
The percentage alone does not establish that conversion. Read RPM separately; this guide supplies no universal percentage-to-RPM formula.
Is Target the current temperature?
No. Target is the requested goal in Auto. Use the reported chip-temperature field for the observation.
Can I compare any two values marked °C?
First identify what each value describes. A chip reading, a PSU component and liquid at an inlet are different measurement points.