Autotuning is a process in which firmware tests and adjusts frequencies and voltages in response to chips or boards. It seeks an operating profile under given conditions, not proof of a global optimum or higher profit.
Braiins describes ASIC differences caused by manufacturing, condition and temperature. Tuning tries frequencies and voltages and allocates work according to response. Uniform settings are not individual calibration; do not automatically extrapolate one machine’s results to a fleet. [Braiins OS — Autotuning]
Braiins tunes for a selected power level; LuxOS distinguishes target draw from its constraints. Higher hashrate, lower J/TH and meeting a limit are different goals. Autotuning can accompany lower or higher performance profiles; it is not synonymous with Overclocking or permission to exceed PSU and cooling limits. [Braiins OS — Autotuning] [LuxOS — powertargetset]
The Braiins FAQ makes duration dependent on model and control board and allows several hours. Check Stable per board: an aggregate disabled status can reflect one disabled board while others are tuned. Do not treat intermediate hashrate fluctuations as the final result. [Braiins OS — DPS and Autotuning FAQ]
The Braiins FAQ describes an S19 target of 3000 W with one functioning hashboard: it receives 1000 W based on three expected boards. This does not mean the tuner must redirect all 3000 W to the remaining board. Respect board, PSU and circuit limits. [Braiins OS — DPS and Autotuning FAQ]
Braiins distinguishes traditional profiles from Continuous Tuning, labeled beta at the review date. DPS changes power levels; that does not itself recalculate a saved profile’s frequencies and voltages for a new temperature. The continuous tuner keeps adapting settings, with thermal safety ahead of performance targets. [Braiins OS — Continuous Tuning beta]
LuxOS AutoTuner does not adjust custom profiles with explicitly chosen frequency and voltage. Power targeting and profile-based tuning cannot run simultaneously; manual frequency and voltage commands are unavailable during power targeting. One mode’s behavior cannot be generalized to every tuner. [LuxOS — AutoTuner]
LuxOS powertargetset distinguishes power_target, power_limit and power_min. Legacy power sets both target and ceiling. Changing a target therefore need not change every constraint; check active values and model support, and distinguish settings from accurate wall-power measurements. [LuxOS — powertargetset]
The model 3000 W / 100 TH/s = 30 J/TH and 2700 W / 90 TH/s = 30 J/TH shows that reducing both quantities by ten percent leaves efficiency unchanged. Compare equal temperatures, whole-device measurement, accepted work and errors. Neither Autotuning nor Stable alone guarantees savings or profit. [Braiins OS — DPS and Autotuning FAQ] [LuxOS — AutoTuner]
For the clearest picture, read this entry together with ASIC Miner, Mining Firmware, ASIC Efficiency, Underclocking. The reverse links also lead from ASIC Efficiency, Mining Firmware, Underclocking, Overclocking.