EMCD Firmware for Antminer S19

EMCD Firmware is software that you install on your Antminer S19 in place of the stock firmware. The miner keeps mining on the pool of your choice, while the firmware handles the routine: it selects the operating mode, monitors temperature, resumes mining after failures, and shows what's happening with each device.

The firmware suits both owners of a single miner and entire farms: the whole farm is installed and updated from one application, with no need to visit each device.

For detailed steps, see the guide "Installing EMCD Firmware Using Antminer FW Flasher".

By default, the device is configured for 95 TH/s. You can select a target between 80 and 110 TH/s in increments of 1 TH/s:

Overclocking above 95 TH/s is performed at your own risk. This mode increases power consumption, heat generation, and the load on the boards and power supply. Before selecting a higher target, make sure your site's cooling and power infrastructure can handle the additional load.

You can select the target in the web interface: Miner Settings → Autotuner card → Target hashrate field → Start tune button. The tuning process takes time. You can monitor its progress in the State field and under Logs → Autotuner.

The tuning results for each target are saved as separate profiles. If you return to a target that already has a saved profile (indicated by a floppy disk icon in the list), the firmware restores it without running the tuning process again. The Reset profile button deletes the profile for the selected target, while Reset tuner deletes all profiles. After a reset, frequencies and voltage return to their default values.

The target is specified for a device with three hashboards. If one hashboard is not detected during startup, the firmware adjusts the remaining boards to a proportionally lower hashrate. For example, with a target of 95 TH/s, two hashboards will produce approximately 63 TH/s. Profiles are linked to specific boards, so the firmware will run the tuning process again after a board is replaced.

Immediately after the initial installation or a target change, the firmware needs time to adjust the parameters. During this period, the hashrate may differ from the selected target. The final result depends on the condition of the boards, power supply, and cooling system. If the boards cannot maintain the selected target reliably, the firmware will settle on a lower value rather than increasing frequencies and voltage at the cost of errors.

These mechanisms reduce the risk of operating at a critical temperature, but they don't replace proper cooling and site monitoring. Protection relies on sensor readings. It may therefore fail to trigger, or trigger late, if several sensors fail at once, there's a poor contact, a board is worn, there are power supply issues, or the temperature rises very quickly.

You can set up to three pools: a primary and two backups. If the primary pool is unavailable, the device switches to a backup and keeps mining. Once the primary pool is back up, the device returns to it.

The firmware checks backup pools in advance, approximately every 10 minutes. If a backup pool's address or worker configuration contains an error, its status on the Dashboard changes to Abnormal before the pool is actually needed. If a pool rejects the worker or password, the device skips that pool for 10 minutes and moves to the next one.

The hashboards are powered on only after at least one pool responds. While all pools are unavailable, the device waits with its hashboards powered off and automatically starts mining once a pool responds.

AsicBoost is supported: if your pool allows it, the device uses less energy for the same work.

The firmware re-verifies every solution the chips find. Solutions with computation errors and duplicates are not sent to the pool. This way, the pool doesn't reject work because of the device's own hardware errors. Rejections for other reasons are still possible, as with any firmware: for example, stale solutions if the pool has changed the job, or rejections caused by pool-side or network issues.

The fee is 2% of mining output. Every 30–60 minutes, the device switches to the EMCD pool for approximately one minute before returning to your selected pool. The connection to your pool remains active, your settings do not change, and there is no need to create a separate worker. On your pool's hashrate chart, this may appear as small, brief drops, which is normal. The fee is calculated only on work actually accepted by the pool.

A separate firmware file is released for each region: Brazil, Europe, Kazakhstan, China, Middle East and North Africa, Russia, USA. The region only determines which EMCD server receives the fee work and doesn't affect your pool. Choose the file for your region: this way, the fee work goes to the nearest server and less is lost to latency.

The device opens in a browser at its network address; logging in requires a username and password. The device interface is in English. It provides:

There is a button on the case:

A reset erases pools, network parameters, the web interface password, and saved autotuning profiles. After rebooting, the device:

A reset doesn't restore Bitmain's stock firmware: EMCD Firmware remains on the device. How to go back to the stock firmware is described in the FAQ section.

The first installation can only be done with FW Flasher (Windows, Linux, macOS). EMCD Firmware can't be installed through Bitmain's stock web interface: it doesn't accept the file.

You specify an address range, and the application finds the miners in it and shows which ones are compatible. You select the ones you need and start the installation on all of them at once. The devices are flashed simultaneously, and you can track progress for each one individually.

After installation, the network parameters and web interface password from the stock firmware are preserved. You can keep your existing pools or switch the miner to the EMCD pool right away by specifying the region and worker name.

There are two ways:

What happens to your settings:

The update file is verified before writing begins. The firmware checks that the file is intended for your model, wasn't corrupted during download, and is signed by EMCD. If any check fails, nothing is written to the device and it continues running on the current version.

The current version is designed for Antminer S19 Xilinx with 76 chips per board (three boards with Bitmain BM1398P chips). The easiest way to check whether your device is compatible is in FW Flasher: compatible miners get the "supported" status. The firmware won't install on other models: the model is checked before writing, and a file for a different model will be rejected.

Not the first installation on a device with stock firmware; that's done only through FW Flasher. Subsequent updates can be installed either through a browser or through FW Flasher.

Yes. Bitmain's stock firmware is written to the device from an SD card. Follow the recovery guide and contact EMCD support if you have any questions. The button on the case and the reset in the web interface don't restore the stock firmware; they only reset EMCD Firmware settings.

No. You can specify any pool. The fee is the same regardless of which pool you choose.

The device will keep trying to connect and will resume work on its own once the connection is restored. It doesn't go into emergency shutdown because of network or pool issues. This is by design: an outage at your provider or pool won't require you to visit every device.

You only need to check that a pool is specified. The firmware automatically tunes the chips for 95 TH/s. If you want a different target, select it in Miner Settings → Autotuner.

Most often, the firmware is still adjusting the parameters. This takes time after the initial installation or a target change. Other possible reasons include a board not being detected during startup, causing the target to be reduced proportionally, or the boards being unable to maintain the selected target reliably, causing the firmware to settle on a lower value. In the latter two cases, check the condition of the boards, power supply, and cooling system.

The firmware uses warnings to notify you of an issue and explain what action it is taking. The reason is displayed below the warning title.

The device usually appears on the network within 2–5 minutes. Right after the first installation, the hashrate may be below target while the firmware tunes chip parameters. If the device isn't on the network after 10 minutes, follow section 9 of the FW Flasher guide.

Mining will stop and power to the boards will be cut. The device will remain accessible on the network, and you'll see the reason for the stop. Most often, it's dust-clogged heatsinks or a stopped fan. After fixing the cause, reboot the device and operation will resume.

The firmware version is displayed in the web interface, both in the sidebar and in System → Administration (Firmware version field). You can also find it in FW Flasher, in the Model / Version column.

We've prepared a guide for you; you can view it at this link.

We've put the firmware files and FW Flasher here:

Firmware:

FW Flasher (latest):