Whatsminer Error 110 – Fanin Detect Speed Error

Hard power cycle at the PDU. Full AC disconnect for 60 seconds - not a soft reboot from the web UI. The BTMiner MCU needs a cold start to clear latched fan-governor state. Roughly 1 in 5 `Error 110` events clear here and don't return. If the error does return within an hour, you have a real hardware fault - don't keep rebooting and hoping, you're cooking the hashboards. One reboot, one chance. If it recurs, tear in physically.

Check intake-side obstructions. Walk to the miner. Is anything within 30 cm of the front grille? A stacked miner above? A wall? A pet bed? Dust-bunny drift from a basement floor? The intake fan can spin fine but hit a no-flow condition that the governor interprets as a tach anomaly. Clear 30 cm minimum front-and-back per MicroBT's deployment guide, and verify the filter (if you installed one) isn't clogged. This is a 60-second check that resolves a surprising fraction of field tickets.

Check ambient at the intake with an IR thermometer or shop thermometer at the front grille - not room-middle. Whatsminer M-series spec a `-5 °C to 40 °C` operating envelope. If your garage is at `38 °C` in July and the exhaust fan is already pinned at max to keep up, the governor can flag FANIN as not doing its share and throw `110`. Verify ambient first before you tear the chassis apart. If ambient is borderline, fix that first - ventilation, summer duct, room A/C - and re-test.

Roll back to last known good firmware if the error appeared immediately after a BTMiner upgrade - you may have hit a sensor-polling regression. Via WhatsMinerTool: `Firmware -> Local file -> load the previous build's .bin -> flash`. Match air-cooled vs hydro vs immersion firmware strictly to your hardware - a hydro `.bin` on an air unit will brick the board, and vice versa. MicroBT's firmware archive lives at https://www.whatsminer.com/download. DCENT_OS is not yet available for Whatsminer.

Open the chassis and inspect FANIN visually. Kill power at the PDU. Remove the top cover (Phillips #2 on most M-series, Torx T10 on later M60/M66 revisions). Remove the fan-guard grille if present. Try to spin the FANIN impeller by hand - it should spin freely with no grind, rattle, or catch. A stiff fan = bearing failure. A fan that spins fine but is dead under power = electrical fault. This single 60-second check splits your whole diagnostic tree.

Blow out the fan with canned air. Upright can, short bursts. Hold the impeller still with a plastic probe while blasting - letting canned air backspin the fan induces back-EMF that stresses an already-tired bearing further. Dust caked on the hub is a surprisingly common cause of a FANIN that reads `0 RPM` but looks visually fine. In any home-mining setup with pets, carpet, or a dusty basement, this step resolves a meaningful fraction of `Error 110` tickets on its own.

Reseat the FANIN connector at the BTMiner control board. Power off at the PDU, wait 60 s for caps to bleed, locate the 4-pin header labelled `FAN_IN` or similar (silkscreen varies M30S vs M50S vs M60 generations). Disconnect, visually inspect shell for bent pins or a crushed latch, reseat firmly until you feel the positive click. Apply a trace of dielectric grease to the pins. Vibration backed the connector out once - it will do it again without help. This fix alone clears a meaningful fraction of field tickets.

Measure `+12 V` at the FANIN header under load. Multimeter on DC volts, probe `V+` to `GND` on the FANIN header while the miner is powered on and the governor is commanded to spin the fan. Expect `11.8 - 12.2 V` steady. Below `11 V` or zero = control-board rail fault, go to Tier 3. Pulsing means the PWM driver is glitching, also Tier 3. Healthy `12 V` with a still-dead fan = fan or harness fault, continue.

Continuity-test the fan harness end-to-end. Multimeter on continuity (beep) mode. Unplug the harness at both ends. Probe TACH, PWM, GND, `+12 V` across the length of the cable. Any wire that doesn't beep = broken conductor, typically at a strain-relief bend point. Replace the harness - MicroBT uses a standard 4-pin JST-PH pinout on most M-series but verify your specific revision before ordering. A broken tach wire alone throws `Error 110` even if the fan itself is fine.

Swap the suspect fan into the known-good (FANOUT) slot. Four-minute test, zero parts. Power off, unplug both fans, swap physical positions on the control board, power on. If the error migrates from `110` to `111`, the fan is dead and followed itself - order a replacement. If `110` stays on the FANIN side regardless of which fan is plugged in, the board-side rail is the problem - go to Tier 3. This is the single most decisive diagnostic in the whole tree.

Replace the FANIN fan with the correct industrial part. Stock M30S / M30S+ / M30S++ and most M50 / M50S / M60-series air-cooled units use a `140 x 140 x 38 mm` 4-pin PWM fan - `YD14038B2G` or equivalent, rated `12 V / ~2.9 A / ~6,000 RPM / ~285 CFM / dual-ball-bearing axial`. Do NOT substitute a 120 mm or 140 x 25 mm consumer PC fan - most top out at `2,000 RPM / 60-90 CFM` and you'll be back at this diagnostic in two weeks. Confirm polarity against the control-board silkscreen before re-powering.

Replace the fan-rail SMD fuse. If Step 8 showed the `+12 V` rail dead on the FANIN header while FANOUT was healthy, a fast-blow SMD fuse popped when a previous fan seized and drew stall current. The fuse is typically a 1206-package fast-blow in the `3-5 A` range, sitting on the fan rail between the `12 V` supply trace and the header. Follow the rail back with a continuity probe. Reflow the replacement with hot air at `290 °C`, Kapton-tape adjacent plastics, verify rail voltage returns to `12 V` before reconnecting a real fan.

Rework the PWM driver transistor on the BTMiner control board. Each fan header is fed by a small MOSFET the MCU toggles at `25 kHz` for PWM duty. A failed MOSFET reads either permanently-on rail (fan spins 100%, tach may still work) or a dead rail (fan stays off, `Error 110`). Identify the offending part by visual match against the nearest transistor footprint to the FANIN header. Hot-air remove, clean pads with braid, reflow a matching replacement. Exact MOSFET part numbers aren't published by MicroBT - D-Central identifies by cross-reference against salvaged reference boards. Without a reference unit, escalate to Tier 4.

Flash or re-flash firmware via SD card or WhatsMinerTool if sensor subsystem is flaky. Download the correct image - air vs hydro vs immersion, exact model match - from https://www.whatsminer.com/download. For SD recovery: write the `.img` to a microSD with Rufus or BalenaEtcher, insert into the control board's SD slot, power-cycle, wait for the flash routine (LED pattern varies by model). For WhatsMinerTool network flash: select miner -> Firmware upgrade -> local `.bin`. If the miner is bricked past network recovery, SD is the only path. Wrong firmware variant bricks the board.

Stop DIY when any of these are true: `+12 V` rail dead on multiple fan headers, visible heat damage or discoloration on the control board, two fan failures in the same rig within 30 days (points upstream to PSU / grounding / ambient excursion), fan failure coinciding with a hashboard going dark or throwing `Error 530/540/550`, you attempted SMD rework and lifted a pad, or both fans report `0` with garbage sensor readings. That's D-Central repair-bench territory. Book a repair slot at https://d-central.tech/services/asic-repair/ - Canadian / US / international welcomed.

What D-Central does at the bench for `Error 110`. Diagnosis against a known-good M-series reference rig, component-level BTMiner control board repair including SMD fuse and MOSFET replacement, fan harness remake with dielectric-greased connectors, full hashboard thermal service if overheat events cascaded from the fan fault, and 24-hour nameplate burn-in (M30S ~88 TH/s / 3,344 W; M50S ~126 TH/s / 3,276 W; M60S ~172 TH/s / 3,440 W) with both fans monitored via continuous API polling before we ship the unit back. Pulled control boards in inventory for most M-series generations.

Ship the whole miner, not the fan alone. The M-series fan assembly is fiddly to pack safely separated from the chassis. Double-box the full unit, remove and separately wrap the hashboards in anti-static bags, include a printed note with your full `status/summary` API output, BTMiner firmware version, and observed symptoms. That saves diagnostic hours on our side, which saves repair dollars on yours. Canadian customers ship to our Quebec bench and have the miner back in a week. US and international welcomed - contact the repair desk for international shipping paperwork.