L3+ Hash rate is low or a hash board is faulty

Please try reloading the firmware: 

L3+:

https://s3.cn-north-1.amazonaws.com.cn/shop-bitmain/download/Antminer-L3%2B-201708251737-384M.tar.gz

 

Run the miner for 20 minutes after loading.

 

Please first check the PSU and the controller. To check the PSU you can test the machine with a known good PSU. If you do not have another PSU then check by switching the cables between hash boards. If the issue follows the cable then the PSU may be faulty. Please reply to this email for more instructions.

 

To test the controller, switch the controller cables between hash boards. If the same hash board shows the issue then the hash board is faulty. If the issue follows the cable then the controller may be faulty. Please contact us for further instructions.

 

If it still is not solved please test each hash board separately to determine which one is defective.

 

To test each hash board separately: keep the PSU connectors and controller cable on one of the hash boards connected and disconnect the cables from the other two hash boards. With the miner running you can see the status of the connected hash board.

 

Here is more detail: http://support.bitmain.com/hc/en-us/articles/226142788-Testing-hash-board-one-by-one

 

On the miner status screen defective chips are displayed as "xxx", "---" or " ASIC≠72

 

Once you know which part is defective please create a Repair ticket and ship the part back to us according to these instructions: https://shop.bitmain.com/workOrderGuide.htm

 

http://support.bitmain.com/hc/en-us/articles/222648028-How-to-disassemble-miners

 

Please pack the hash boards carefully. If the PINs are lost due to shipping damage it will void the warranty. Here is a video demonstrating how to pack the boards: https://youtu.be/Z0LdykALhxI

 

You may disassemble the miner and break the warranty seal to follow these instructions. 

Have more questions? Submit a request

1 Comments

  • 0
    Avatar
    Dexter Patrick

    Thank you for responding. I will do the above troubleshooting instruction and update you again.

Article is closed for comments.