Guide

Reading power draw after a firmware change

Firmware writes are easy to celebrate too early. On our Yannawa benches we refuse to call a profile finished until wall watts and reported hash sit still for a full cool-down cycle.

Handwritten measurement log next to a calculator

Start with a stock baseline

Before touching custom firmware, run the miner on stock settings for twenty minutes. Log clamp-meter watts at the wall, the pool’s accepted hash, and board temperatures at the hottest sensor. That triangle becomes the reference every later step is judged against.

Change one lever, then wait

Voltage or frequency moves happen one at a time. After each write we wait for fans to settle and for the meter to stop hunting. A five-minute glance at the pool dashboard is not enough — transient spikes hide behind short samples.

Trust the wall more than the UI

Miner interfaces sometimes report cheerful efficiency numbers that ignore PSU losses. Workshop sheets always privilege the clamp reading. If wall watts fall while hash collapses, the profile is a loss even if the UI looks tidy.

Record the stop rule

Every participant writes the error count or temperature that forced a rollback. That line matters more than the best watt figure of the day when you repeat the sequence at home during a Bangkok heat wave.

See how this shows up in the Firmware Tuning Workshop