Professional Documents
Culture Documents
Guiaingles PDF
Guiaingles PDF
Table of Contents
List of Figures and Tables
This is an official troubleshooting and repair guide for AvalonMiner 7 and AvalonMiner 8 series.
All rights to fix or improve this document are reserved to Canaan Creative.
In this guide you will see how to disassemble and separate all miner components and it will help you to
understand how to replace a faulty miner component like for example a broken cooling fan or faulty PCB
board.
You will also learn how to do the fault diagnosis to your miner in a case of a miner malfunction and how to
find out which miner component is most likely not working correctly.
This guide is made using an AvalonMiner 841 unit, but same principles apply with other compatible models
mentioned in this guide as well.
2. Troubleshooting
In this chapter you will see the common methods for the troubleshooting process and you will also see
example cases about the most common issues.
The goal is to help understand how to determine which miner component is causing the miner operation
malfunction.
You can find the indicator LED switch button location by following these steps:
1. Go the controller web configuration page by using your web browser and login.
2. Click ’Advanced Version’ to access the advanced user features in the OpenWrt firmware.
3. Click ’CGMiner Status’ to see status for all the devices connected to the controller.
4. Choose the AvalonMiner unit which you would like to locate and click ’LED OFF’ button located in
the Indicator field. Now you should see that status change into ’LED ON’. Further observations
about this situation are shown in two figures below (Figure 12 and Figure 13).
Figure 12 Normal miner operation before pressing the indicator LED button - the indicator LED color is blue.
Figure 13 After pressing the indicator LED button the miner in question changes the indicator LED color to white.
Page 9 / 29
These following instructions will tell you how to locate and open the CGMiner API Log.
By reading the log text you are able to see lots of technical information related to the miner performance.
Step 1.
Use your web browser and access to the controller web configuration page.
Step 2.
Click ’Advanced Version’ to access all user features.
Step 3.
You are now able to see all the features available.
Now you need to click ’CGMiner API Log’ to access the log text.
Step 4.
Click ’Debug Switch’ and after that you are ready to read and examine the CGMiner API Log.
Information about indicator LED colors and CGMiner API Log error codes
2.2 Information about indicator LED colors and CGMiner API Log error codes
During the troubleshooting it is best to find and use all the information available, so that the repair is a
quick and straight forward process.
The miner is able to report about specific issue with different LED colors and error codes.
In these following tables you can see a description for each LED color and error code.
Please remember to click ’Debug Switch’ button before reading and examining the CGMiner API Log.
This error can happen because of numerous different things, but here is a list showing few of them.
Miner is still in the startup process
Incorrect pool settings
Wrong OpenWrt firmware version
Communication error.
Page 12 / 29
WARN: It designates potentially harmful situations, but you can ignore it.
FATAL: It designates very severe error events that will presumably lead the AvalonMiner to crash.
Page 13 / 29
2.3 How to read the abbreviations and values found in the CGMiner API Log
In this following table you can see the CGMiner API Log thoroughly explained, row by row.
This provides you a lot of help in the troubleshooting process, as you are able to determine possible issues
based on the values seen in the CGMiner API Log. The information is divided into three parts, part 1-3.
Table 5 List of codes found in the CGMiner API Log. Part 1.
Code Description
Miner Log Description.
[Firmware Version] => Avalon Firmware - OpenWrt firmware version you are running.
20180305
luci: 62d814c The github source code tag.
cgminer: b5b497e The github source code tag.
cgminer-packages: 960e108 The github source code tag.
[STATS] => 0
[ID] => AV80 Miner Model: 8, AUC ID: 0.
[Elapsed] => 134 Unit: s. Time elapsed.
[Calls] => 0
[Wait] => 0.000000
[Max] => 0.000000
[Min] => 99999999.000000
[MM ID1] => Ver[8411802-1e73b80] Raw Cgminer log output.
DNA[0133796fb64c9538] Unique Machine ID. Last four letters are shown in
the miner status page. This is tied to Miner
Management board (MM ) -- DNA read from FPGA.
Elapsed[108] Unit: s. The elapsed hashing time for the miner.
MW[26335 26109 26186 26247] Hash boards’ works. One work means one block
header.
LW[104877] Local Work (Same definition as Cgminer).
MH[0 0 0 0] Hardware errors on each Hash board.
HW[0] Sum of the error number values in the MH field.
Temp[27] Unit: °C. Intake temperature.
TMax[62] Unit: °C. Maximum temperature. This is the
temperature value for the hottest ASIC chip.
Fan[5820] Unit: rpm. Fan speed, read from the fan
tachometer.
FanR[100%] Unit: %. Control value for the fan speed. Set by the
CGMiner.
Vi[1208 1208 1207 1207] Unit: VDC. PMU board input voltage value.
Vo[3806 3812 3787 3812] Unit: VDC. PMU board output voltage value.
PLL0[1 2 42 4427] Core counts distribution on Hash board 0, 1, 2 and
3. Core counts on different PLL . There are 4 PLLs in
PLL1[3 1 92 4376] A3210, the PLL setting can be found in SF[xx xx xx
xx]. The number is the [inside chip hash core
PLL2[0 0 7 4465] amount] that running at which PLL. So, for example
PLL3[0 1 14 4457] in this configuration: 1 runs at PLL0, 2 runs at PLL1,
24 cores run at PLL2, the rest all runs at PLL3.
GHSmm[13736.88] Unit: Gh/s. Hash rate calculated through average
frequency.
Page 14 / 29
Code Description
WU[121295.33] WU: The Work Utility defined as the number of
diff1 shares work / minute.
Freq[767.94] Unit: Hz. Average frequency. Every core in the chip
will work at different frequency, so this is the
average frequency.
PG[15] PMU output status (Power Good). If the value is
low, please start by checking your power supply
health.
Led[0] LED indicator color code.
MW0[5 2 4 2 6 2 5 3 0 3 3 8 7 5 2 8 8 6 3 7 4 9 7 4 The work that has been accepted of each chip on
9 4] the Hash board 0.
MW1[2 5 7 5 4 5 3 4 2 3 5 2 4 4 1 5 1 5 5 2 7 3 5 3 The work that has been accepted of each chip on
3 2] the Hash board 1.
MW2[4 1 7 1 3 6 6 8 7 1 4 6 5 5 4 6 2 4 5 1 5 8 6 6 The work that has been accepted of each chip on
2 4] the Hash board 2.
MW3[4 1 4 6 5 2 3 4 3 4 3 3 0 5 3 3 3 5 3 5 5 4 3 7 The work that has been accepted of each chip on
4 3] the Hash board 3.
TA[0] Total available chips.
Error code of Hash board 0 – 3.
ECHU[0 0 0 0] https://github.com/Canaan-Creative/avalon8-
docs/wiki/AvalonMiner-error-code
Error code of Miner Management (MM) board.
ECMM[0] https://github.com/Canaan-Creative/avalon8-
docs/wiki/AvalonMiner-error-code
FAC0[4] Voltage level (Factory information).
OC[0] Over clocking flag (0/1).
SF0[0 0 0 775] Frequency set by CGMiner (it should be 25x, or it
SF1[0 0 0 775] will change to 25x). Only use settings that are
SF2[0 0 0 775] multiples of 25 Hz.
SF3[0 0 0 775]
PMUV[0000 0000] PMU version.
PVT_T0[54 56 57 58 58 59 60 60 61 59 60 60 60 Unit: °C. Chip temperature for the chips on Hash
62 57 59 60 61 60 61 61 59 57 57 54 53] Board 0.
PVT_T1[53 54 55 55 56 56 57 57 58 58 58 58 57 Unit: °C. Chip temperature for the chips on Hash
57 58 59 59 58 57 58 57 56 55 55 54 53] Board 1.
PVT_T2[54 55 55 56 57 58 57 58 59 59 60 59 59 Unit: °C. Chip temperature for the chips on Hash
59 60 60 59 59 59 59 58 58 57 56 55 54] Board 2.
PVT_T3[56 56 57 58 58 59 60 59 59 59 60 59 60 Unit: °C. Chip temperature for the chips on Hash
58 59 60 59 59 59 61 59 59 57 57 55 56] Board 3.
PVT_V0_0[751 751 376 376 1 896 897 743] The voltage of the 1st chip on Hash board 0.
PVT_V0_1[751 751 365 365 1 899 703 744] The voltage of the 2nd chip on Hash board 0.
PVT_V0_2[757 757 366 366 1 893 711 750] The voltage of the 3rd chip on Hash board 0.
PVT_V0_3[749 749 362 362 1 904 703 740] The voltage of the 4th chip on Hash board 0.
-//- -//-
Page 15 / 29
Code Description
PVT_V1_0[755 755 364 364 1 900 897 746] The voltage of the 1st chip on Hash board 1.
PVT_V1_1[752 752 358 358 1 907 713 743] The voltage of the 2nd chip on Hash board 1.
PVT_V1_2[747 746 367 367 1 896 722 737] The voltage of the 3rd chip on Hash board 1.
PVT_V1_3[751 751 370 370 1 894 705 741] The voltage of the 4th chip on Hash board 1.
-//- -//-
PVT_V2_0[753 753 364 364 1 899 893 743] The voltage of the 1st chip on Hash board 2.
PVT_V2_1[755 755 367 367 1 900 711 746] The voltage of the 2nd chip on Hash board 2.
PVT_V2_2[754 754 357 357 1 898 711 745] The voltage of the 3rd chip on Hash board 2.
PVT_V2_3[752 752 353 354 1 901 712 742] The voltage of the 4th chip on Hash board 2.
-//- -//-
PVT_V3_0[753 753 362 362 1 906 885 743] The voltage of the 1st chip on Hash board 3.
PVT_V3_1[749 749 362 362 1 900 718 741] The voltage of the 2nd chip on Hash board 3.
PVT_V3_2[756 756 354 354 1 897 714 747] The voltage of the 3rd chip on Hash board 3.
PVT_V3_3[749 749 366 366 1 896 713 740] The voltage of the 4th chip on Hash board 3.
-//- -//-
According to the ATX specification, the measured voltage should be from 11.4 to 12.6 VDC.
Please also take into account the rated input voltage for your AvalonMiner.
The most safe area for the input voltage is 12.0 to 12.5 VDC.
You can easily measure the voltage by applying one multimeter test lead to the +12V (yellow) and one
multimeter test lead to the COM (black).
First you need to select the right measuring mode by using the selection knob in the middle of the
multimeter. Make sure that your test leads are connected correctly to the multimeter for voltage
measurement setup.
Figure 19 Selecting the right measuring mode for the 12 VDC voltage measurement.
Page 17 / 29
You can use any safe methods, tools or tape you need to hold the power connector still so that it is easy for
you to hold the test leads safely in position.
If you find a miner with fan reading at 0 rpm or close to it, then it is quite clear that you need to replace
that miner’s cooling fan.
Please also see if there are any indicator LED colors or log error codes related to a cooling fan issue.
If the cooling fan failure occurs during the warranty period, you can request a replacement cooling fan from
Canaan Creative.
If your miner is out of warranty, here is a list of few compatible replacement cooling fan models:
Please also make sure that the 5 VDC wall wart is in ok condition and that it is able to provide at least 5 VDC
2.5 A power for the controller unit.
You can look at the LED colors and log error codes and try to figure out the issue that way.
You can try a spare AUC3 converter if you have another one.
You can easily troubleshoot if it is the AUC3 which is faulty, if you have a ten miners or more in your setup.
This means that you have at least two AUC3 converters in your setup. You can swap those two AUC3
converters and try to see if the issue moves to the another group of miners. If it does, you should be able to
know which one is the faulty AUC3 converter.
Another example of possible control board malfunction is that if there is a huge number hash boards down
suddenly.
One good hint is that you have for example five miners connected to one AUC3 converter, and you are only
able to connect four of them, it indicates that there might be issues with one miner control board.
You can look at the LED colors and log error codes and try to figure out the issue that way.
You can try using a spare control board (MM board) for the miner in question if you have another one.
Page 20 / 29
If you have one or more hash boards down and without power, it is a good idea to figure out how is the
PMU board condition. You can do this by looking at the CGMiner API Log.
If you any values zero or values having an odd number, it is possible that you have a faulty PMU board.
When you look at the log, please pay attention to Vi and Vo values (voltage in and voltage out).
One PMU board has two power terminals, so there is a total number of four values visible in the log. There
are four digits presenting the measured input voltage and output voltage. For example value 1199 means
11.99 VDC.
In this next image you can see how to identify which PMU board is the first one and which is the second.
Hash board
To find out if you have a hash board issue, you can look at two things in the CGMiner API log.
Your miner might also have issues with constant rebooting because one of the ASIC chips overheats.
In this case you can first try to clean the old thermal paste and then apply new thermal paste.
If new thermal paste does no good, you need a new hash board.
Figure 26 Number of works shown in the log. This miner is working normally.
In this next image you can see how to identify which ID number is for which hash board.
3. Tear down
You mostly need only one tool for the tear down process and it is a screwdriver.
Make sure you have a good quality Phillips head screwdriver and right sized,
to avoid damaging the small bolts.
Please also be careful not to use too much force which can potentially damage your
screwdriver, bolt or the thread.
Please pay attention using the right type of a bolt when assembling it all back together.
Unplug the 4-pin fan cable connector and remove the cooling fan.
Figure 34 Unplugging the 4-pin fan extension cable from the control board.
Page 25 / 29
There are two small bolts to be removed, after which you can gently detach the control board which is
connected to both two PMU boards (Power Management Unit).
There are six small bolts holding one frame parts against the heat sinks, so a total number of twelve bolts.
There are six bolts per PMU board and four of them connect the power from the PMU board to the hash
board, so a total number of twelve bolts.
Figure 40 Two hash boards with one shared large heat sink and two invidual heat sinks.
Page 28 / 29
Please remove the old thermal paste if needed, if it is hardened or damaged in any different way. You
should do this by using pure isopropyl alcohol and a soft cloth or paper.
After the surfaces are cleaned, you can apply new thermal paste. Do not use your finger or anything else
that causes impurities to mix with the thermal paste when applying the new thermal paste.
Now we have gone through how to tear down the miner, how to separate all the miner components and
how to replace each invidual miner component.
Assembling it all back together is essentially doing this same process backwards.
Page 29 / 29
4. Conclusion
These instructions should be able to help you with most of the issues that might occur,
even though AvalonMiner failure rate in field is close to 1%, which is a low number compared to the
competitors.
But please remember that if you need help with an miner issue, you can always also do these two things:
Submit a support ticket at Canaan Creative website
Join the discussion thread at Bitcointalk.org forum to get comments and instructions on your issue.
Any questions, suggestions or comments are welcome to be posted in the Bitcointalk.org forum thread,
or asked by submitting a support ticket at Canaan Creative website.