Title: S17+ chip failure
Post by: NGrainy on August 09, 2022, 05:49:56 AM
I use the test fixture to check the S17+, it shows error asic, and there is more than one. Do all of the chips shown need to be replaced? Or is it just one chip failure that affects other chips? 2022-08-08 08:32:04 temperature.c:488:temp_statistics_show: pcb temp 30~35 chip temp 51~60 2022-08-08 08:32:04 single_board_test.c:2522:do_single_board_test: Begin send test pattern 2022-08-08 08:32:04 single_board_test.c:1291:show_status_thread: g_nonce_valid = 1224 2022-08-08 08:32:06 single_board_test.c:1291:show_status_thread: g_nonce_valid = 16912 2022-08-08 08:32:07 single_board_test.c:1291:show_status_thread: g_nonce_valid = 35259 2022-08-08 08:32:08 single_board_test.c:1291:show_status_thread: g_nonce_valid = 50126 2022-08-08 08:32:09 single_board_test.c:1291:show_status_thread: g_nonce_valid = 54964 2022-08-08 08:32:10 single_board_test.c:1291:show_status_thread: g_nonce_valid = 67876 2022-08-08 08:32:11 single_board_test.c:1291:show_status_thread: g_nonce_valid = 86822 2022-08-08 08:32:12 single_board_test.c:1291:show_status_thread: g_nonce_valid = 99657 2022-08-08 08:32:13 single_board_test.c:1291:show_status_thread: g_nonce_valid = 118818 2022-08-08 08:32:14 single_board_test.c:1291:show_status_thread: g_nonce_valid = 132615 2022-08-08 08:32:15 single_board_test.c:1291:show_status_thread: g_nonce_valid = 143642 2022-08-08 08:32:16 single_board_test.c:1291:show_status_thread: g_nonce_valid = 161437 2022-08-08 08:32:17 single_board_test.c:1291:show_status_thread: g_nonce_valid = 179857 2022-08-08 08:32:18 single_board_test.c:1291:show_status_thread: g_nonce_valid = 198753 2022-08-08 08:32:19 single_board_test.c:1291:show_status_thread: g_nonce_valid = 217712 2022-08-08 08:32:20 single_board_test.c:1291:show_status_thread: g_nonce_valid = 236774 2022-08-08 08:32:22 single_board_test.c:1291:show_status_thread: g_nonce_valid = 254827 2022-08-08 08:32:23 single_board_test.c:1291:show_status_thread: g_nonce_valid = 273951 2022-08-08 08:32:24 single_board_test.c:1291:show_status_thread: g_nonce_valid = 286816 2022-08-08 08:32:24 single_board_test.c:1538:send_pattern_thread: send test pattern done 2022-08-08 08:32:25 single_board_test.c:1291:show_status_thread: g_nonce_valid = 289434 2022-08-08 08:32:26 single_board_test.c:1291:show_status_thread: g_nonce_valid = 289434 2022-08-08 08:32:27 single_board_test.c:1291:show_status_thread: g_nonce_valid = 289434 2022-08-08 08:32:28 single_board_test.c:1291:show_status_thread: g_nonce_valid = 289434 2022-08-08 08:32:29 temperature.c:488:temp_statistics_show: pcb temp 36~47 chip temp 64~67 2022-08-08 08:32:29 single_board_test.c:1072:parse_pattern_result: every ASIC require nonce number: 5376 IC[00]=5356 IC[01]=2274 IC[02]=5045 IC[03]=5370 IC[04]=5366 IC[05]=5339 IC[06]=5280 IC[07]=3437 IC[08]=5368 IC[09]=5360 IC[10]=2290 IC[11]=2689 IC[12]=0 IC[13]=1784 IC[14]=2 IC[15]=5315 IC[16]=3373 IC[17]=3938 IC[18]=5360 IC[19]=5363 IC[20]=5239 IC[21]=5290 IC[22]=1 IC[23]=4603 IC[24]=5272 IC[25]=5346 IC[26]=5362 IC[27]=5372 IC[28]=5362 IC[29]=5358 IC[30]=2681 IC[31]=2675 IC[32]=2621 IC[33]=2686 IC[34]=2684 IC[35]=5321 IC[36]=5362 IC[37]=5337 IC[38]=5240 IC[39]=3948 IC[40]=4982 IC[41]=5302 IC[42]=5346 IC[43]=5313 IC[44]=5290 IC[45]=5327 IC[46]=5334 IC[47]=5348 IC[48]=5368 IC[49]=5317 IC[50]=5369 IC[51]=5304 IC[52]=5336 IC[53]=5296 IC[54]=4342 IC[55]=5339 IC[56]=5309 IC[57]=5360 IC[58]=5364 IC[59]=5362 IC[60]=5332 IC[61]=4977 IC[62]=1 IC[63]=5042 IC[64]=4705
2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 1, 413 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 7, 294 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 10, 398 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 11, 336 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 12, 672 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 13, 469 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 14, 672 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 16, 310 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 17, 229 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 22, 672 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 23, 213 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 30, 338 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 31, 341 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 32, 349 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 33, 336 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 34, 337 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 39, 186 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 54, 170 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 61, 112 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 62, 672 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 63, 91 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1130:parse_pattern_result: error asic is 64, 180 core not receive all nonce 2022-08-08 08:32:29 single_board_test.c:1149:parse_pattern_result: every Domain require nonce number: 6720 2022-08-08 08:32:29 single_board_test.c:1151:parse_pattern_result: every Domain require nonce number: 6720 2022-08-08 08:32:29 single_board_test.c:1153:parse_pattern_result: every Big Domain require nonce number: 26880 D[00]:5041 D[01]:6717 D[02]:5365 D[03]:6288 D_BIG[00]:23411 D[04]:6315 D[05]:6159 D[06]:6192 D[07]:6118 D_BIG[01]:24784 D[08]:3038 D[09]:1 D[10]:2681 D[11]:1045 D_BIG[02]:6765 D[12]:5791 D[13]:5510 D[14]:5956 D[15]:6092 D_BIG[03]:23349 D[16]:5138 D[17]:5099 D[18]:5084 D[19]:5084 D_BIG[04]:20405 D[20]:6701 D[21]:6699 D[22]:6702 D[23]:6698 D_BIG[05]:26800 D[24]:6708 D[25]:6637 D[26]:2 D[27]:0 D_BIG[06]:13347 D[28]:6669 D[29]:5213 D[30]:6686 D[31]:6640 D_BIG[07]:25208 D[32]:6610 D[33]:6482 D[34]:6525 D[35]:6616 D_BIG[08]:26233 D[36]:6648 D[37]:6692 D[38]:6688 D[39]:6666 D_BIG[09]:26694 D[40]:6222 D[41]:6142 D[42]:6654 D[43]:6629 D_BIG[10]:25647 D[44]:6678 D[45]:6692 D[46]:6680 D[47]:6684 D_BIG[11]:26734 D[48]:5136 D[49]:5104 D[50]:4838 D[51]:4979 D_BIG[12]:20057 2022-08-08 08:32:29 single_board_test.c:1178:parse_pattern_result: asic domain status: asic[ 0]-->[YYYY] asic[ 1]-->[XYXX] asic[ 2]-->[YYYY] asic[ 3]-->[YYYY] asic[ 4]-->[YYYY] asic[ 5]-->[YYYY] asic[ 6]-->[YYYY] asic[ 7]-->[XXXX] asic[ 8]-->[YYYY] asic[ 9]-->[YYYY] asic[10]-->[YXXY] asic[11]-->[YXYX] asic[12]-->[XXXX] asic[13]-->[XXYX] asic[14]-->[XXXX] asic[15]-->[YYYY] asic[16]-->[XXXX] asic[17]-->[YXXY] asic[18]-->[YYYY] asic[19]-->[YYYY] asic[20]-->[YYYY] asic[21]-->[YYYY] asic[22]-->[XXXX] asic[23]-->[YYYY] asic[24]-->[YYYY] asic[25]-->[YYYY] asic[26]-->[YYYY] asic[27]-->[YYYY] asic[28]-->[YYYY] asic[29]-->[YYYY] asic[30]-->[YYXX] asic[31]-->[YYXX] asic[32]-->[YYXX] asic[33]-->[YYXX] asic[34]-->[YYXX] asic[35]-->[YYYY] asic[36]-->[YYYY] asic[37]-->[YYYY] asic[38]-->[YYYY] asic[39]-->[YXYY] asic[40]-->[YYYY] asic[41]-->[YYYY] asic[42]-->[YYYY] asic[43]-->[YYYY] asic[44]-->[YYYY] asic[45]-->[YYYY] asic[46]-->[YYYY] asic[47]-->[YYYY] asic[48]-->[YYYY] asic[49]-->[YYYY] asic[50]-->[YYYY] asic[51]-->[YYYY] asic[52]-->[YYYY] asic[53]-->[YYYY] asic[54]-->[XXYY] asic[55]-->[YYYY] asic[56]-->[YYYY] asic[57]-->[YYYY] asic[58]-->[YYYY] asic[59]-->[YYYY] asic[60]-->[YYYY] asic[61]-->[YYYY] asic[62]-->[XXXX] asic[63]-->[YYYY] asic[64]-->[YYYY] 2022-08-08 08:32:29 single_board_test.c:247:handle_asic_domain_result: hashboard level:1, no domain ng times:0, one asic little domain ng times:0, only one big domain ng times:0, more than one big domain ng times:1
2022-08-08 08:32:29 single_board_test.c:1234:parse_pattern_result: hashboard level 1, satisfy rate lower limit times 0, satisfy rate upper limit times 0
2022-08-08 08:32:29 single_board_test.c:1237:parse_pattern_result: 65 asic not receive all nonce, Conf.Invalid_Asic_Num = 65 2022-08-08 08:32:29 single_board_test.c:1239:parse_pattern_result: total valid nonce number: 289434, lost 60006 nonce 2022-08-08 08:32:29 single_board_test.c:1241:parse_pattern_result: Nonce rate = 82.827950% 2022-08-08 08:32:29 single_board_test.c:1243:parse_pattern_result: HW number = 0, Conf.Most_HW_Num = 128 2022-08-08 08:32:32 single_board_test.c:941:save_eeprom_error_info: --- write eeprom error info --- Level: 1 Pattern NG ChainID 1 Vol 1950 Freq 625 Pattern 0 Temper 2 Eeprom 4 NonceRate 82.827950% 2022-08-08 08:32:34 thread.c:852:cancel_pic_heart_beat_thread: cancel thread 2022-08-08 08:32:35 single_board_test.c:1558:kill_hashboard: ****power off hashboard****
Title: Re: S17+ chip failure
Post by: BitMaxz on August 09, 2022, 12:35:12 PM
I use the test fixture to check the S17+, it shows error asic, and there is more than one. Do all of the chips shown need to be replaced? Or is it just one chip failure that affects other chips?
I suggest you check them one by one chips that you see some errors if you don't know how to locate and test them there is a guide on ZeusBTC that will help troubleshoot and repair the whole s17+ hashboard. You can follow the guide from this link "Antminer s17 plus Hashboard Repair Guide (https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp)" Or download the repair guide here https://www.zeusbtc.com/articles/information/182-antminer-s17-manual-download
Title: Re: S17+ chip failure
Post by: philipma1957 on August 09, 2022, 12:36:25 PM
S17+ boards are known to be hard to repair good luck.
Title: Re: S17+ chip failure
Post by: GFDhd on August 10, 2022, 05:44:09 AM
My insight is to use a programmer to rewrite the contents of the EEPROM first, then solder the chip again, and if the problem still persists, the faulty ASIC chip needs to be replaced.
Title: Re: S17+ chip failure
Post by: mikeywith on August 11, 2022, 03:12:23 AM
I can't really understand the logs you posted, but to answer your question, one bad chip can stop the whole board from working, and usually or most often I might say, it's one bad chip that needs repair, using the text fixture alone isn't enough, you will need to measure the voltage on each chip, you may also visually inspect the chips and look for solder balls that are shorting a chip or two.
Title: Re: S17+ chip failure
Post by: Rodemi on August 18, 2022, 09:09:34 AM
You may need to re-solder all the chips that show the failure, because the 17 series miners use the low-temperature tin for soldering, so many chips have the problem of virtual soldering. In many cases, you only need to re-solder them to solve the problem. If it still doesn't work, you may need to replace the chip. If the number of chips that need to be replaced is large, it is obviously not cost-effective.
Title: Re: S17+ chip failure
Post by: MinerMEDIC on August 22, 2022, 03:33:28 AM
Given the age of these Hashboards and their poor design, that is a good hashboard. You go mucking about with that just to get a few more cores and you’re gonna find yourself with zero ASIC very quickly.
|