Topic: Diminishing Hash Rate Over Time (Read 297 times)
great thank you for your help. High performance mode is enabled. Something must still be happening that occasionally the TMAX will get high every few days and cause the machine to restart. Will see if that still happens now that I have done the aging.
That's very cool if you have below 60c temp and others have 70+ high with low fan speed but your TMAX is high it means there are still fluctuate on temp.
Watch this at the end of your logs WORKMODE[1] it means it's running at high-performance mode.
Well, you said it's running fine now after the aging process, so keep monitoring the miner for 24hrs and let's hope it will run stable at that speed.
Watch this at the end of your logs WORKMODE[1] it means it's running at high-performance mode.
Well, you said it's running fine now after the aging process, so keep monitoring the miner for 24hrs and let's hope it will run stable at that speed.
After the aging process completed and I wait a few more hours, the hashrate is up to 77TH/s. It seems that the aging did do some good work. As for your suggestion of running the fan speed in the 80-90% range to see if it will run stable for long, if I notice the chip temps dropping below 60 should I end the experiment? I fear that this will keep the chips on average too cool. Seeking your opinion before executing the experiment. I don't believe the ASIC has toggled off of the performance mode before but I also haven't checked to make sure, my only evidence is that in the nomral mode it will hash in the 50TH/s range and in high performance above 70TH/s. At no point did the ASIC ever hash consistently in the 50s, except for the few hours during the aging process. Here are some current logs:
Code:
{'STATUS':[{'STATUS':'S','When':29193,'Code':11,'Msg':'Summary','Description':'cgminer 4.11.1'}],'SUMMARY':[{'Elapsed':29209,'MHS av':76122886.29,'MHS 30s':74740957.55,'MHS 1m':76221291.72,'MHS 5m':76472777.44,'MHS 15m':76236342.81,'Found Blocks':0,'Getworks':1075,'Accepted':6442,'Rejected':13,'Hardware Errors':2164,'Utility':13.23,'Discarded':87473083,'Stale':0,'Get Failures':0,'Local Work':1015515,'Remote Failures':0,'Network Blocks':50,'Total MH':2218914006069.0000,'Work Utility':1063444.79,'Difficulty Accepted':514365359.00000000,'Difficulty Rejected':1064302.00000000,'Difficulty Stale':0.00000000,'Best Share':1429782279,'Device Hardware%':0.0004,'Device Rejected%':0.2056,'Pool Rejected%':0.2065,'Pool Stale%':0.0000,'Last getwork':0}
{'STATUS':[{'STATUS':'S','When':29193,'Code':70,'Msg':'CGMiner stats','Description':'cgminer 4.11.1'}],'STATS':[{'STATS':0,'ID':'AVA100','Elapsed':29209,'Calls':0,'Wait':0.000000,'Max':0.000000,'Min':99999999.000000,'MM ID0':'Ver[1166Pro-81-21030201_4ec6bb0_09b1765] DNA[0201000053ecf2c7] MEMFREE[1443104.0] NETFAIL[0 0 0 0 0 0 0 0] SYSTEMSTATU[Work: In Work, Hash Board: 3 ] Elapsed[29210] BOOTBY[0x08.00000000] LW[29153038] MH[224 301 1639] HW[2164] DH[5.283%] Temp[9] TMax[102] TAvg[64] Fan1[3046] Fan2[3096] Fan3[2963] Fan4[3006] FanR[25%] Vo[314] PS[0 1220 1257 256 3217 1256] PLL0[6357 671 1741 5151] PLL1[4758 495 1151 7516] PLL2[3910 2643 4339 3028] GHSspd[77037.26] DHspd[5.250%] GHSmm[81522.08] GHSavg[76121.12] WU[1063399.77] Freq[488.04] Led[0] MGHS[24374.70 26241.42 25505.00] MTmax[102 81 72] MTavg[68 65 60] TA[360] Core[A3201] PING[27] POWS[0] HASHS[0 0 0] POOLS[0] SoftOFF[0] ECHU[0 0 0] ECMM[0] SF0[456 476 496 516] SF1[456 476 496 516] SF2[456 476 496 516] PVT_T0[ 74 74 74 74 76 76 72 74 78 81 77 76 74 74 79 80 77 74 72 78 78 81 72 72 70 70 76 76 73 69 69 73 78 79 72 68 68 74 76 78 73 65 102 69 77 74 70 64 62 67 73 65 63 61 61 64 64 63 61 59 53 55 55 57 59 55 61 56 61 59 57 56 60 59 60 60 60 60 62 60 61 62 62 64 62 63 62 64 66 65 65 67 62 64 68 65 67 66 67 68 68 68 69 69 69 72 67 70 74 71 69 65 72 69 69 71 67 65 69 72] PVT_T1[ 68 69 66 69 69 68 71 69 73 73 71 69 73 71 72 74 75 73 67 70 77 81 74 69 67 72 78 79 74 69 68 72 77 78 74 69 66 71 76 72 70 65 64 67 70 69 68 63 62 67 69 67 66 61 61 66 64 64 64 61 55 59 54 57 59 58 55 58 57 63 60 59 61 64 63 63 62 61 63 65 66 65 63 62 65 68 65 63 65 64 63 68 64 63 62 63 63 65 63 62 62 63 62 63 63 61 62 62 62 63 63 64 61 64 64 62 62 59 62 63] PVT_T2[ 64 63 67 69 67 64 65 69 69 70 69 63 63 69 69 72 69 63 64 67 69 69 68 62 61 66 66 68 68 60 60 65 69 71 65 60 61 63 69 68 66 61 59 64 66 64 61 58 54 58 64 59 58 57 54 56 55 55 56 55 51 50 51 51 52 51 51 53 54 54 55 55 54 56 54 56 56 58 58 57 57 56 58 57 56 57 57 58 60 57 58 57 59 58 59 60 58 61 59 59 62 62 63 59 60 61 63 61 61 63 63 63 62 62 63 59 63 62 63 61] PVT_V0[286 291 295 289 288 286 289 284 281 294 290 287 289 287 287 280 285 288 279 280 281 277 275 275 287 285 281 281 282 289 287 286 287 282 279 278 291 293 289 283 285 288 309 286 285 290 294 296 298 294 290 286 281 280 290 294 291 291 294 299 305 301 298 297 299 301 298 299 302 298 299 301 300 299 299 298 294 294 298 297 297 300 297 298 294 292 298 295 300 298 293 293 297 295 293 294 289 289 289 292 293 294 288 287 289 288 293 289 286 285 286 289 287 290 290 294 291 288 289 294] PVT_V1[296 299 303 298 294 292 289 288 286 288 293 292 285 286 289 290 292 290 285 289 285 290 294 295 281 281 280 283 286 286 287 285 286 292 286 291 291 291 285 285 282 282 283 287 290 289 287 291 286 287 283 293 290 291 285 285 287 290 291 299 310 305 302 301 299 302 295 301 301 291 291 294 302 297 297 299 299 298 295 302 302 290 291 293 291 292 291 290 289 291 291 290 290 296 295 292 294 292 291 286 287 287 296 295 295 288 285 285 295 297 294 291 293 293 290 291 290 297 298 303] PVT_V2[287 291 296 289 285 282 291 289 289 282 285 282 288 289 288 291 287 287 284 283 281 290 292 293 289 287 294 286 287 288 287 293 291 280 286 289 285 283 286 290 286 286 291 289 285 293 292 291 294 297 290 293 292 291 298 297 295 293 295 302 301 300 298 294 295 299 292 294 292 295 293 293 294 296 297 301 301 299 291 291 295 293 295 297 290 295 297 293 297 297 295 294 293 295 294 290 294 292 291 294 290 290 296 296 294 295 295 294 300 301 298 286 292 292 293 294 293 292 292 295] MW[9721125 9721185 9721243] MW0[1224 1512 1526 1351 1382 916 1444 699 1150 1337 1204 1467 1422 1277 1171 1045 988 1394 1058 856 1181 1193 579 805 1427 1430 1363 984 1458 1269 1313 1237 1137 1347 1181 1151 1412 1356 1248 974 797 1355 1250 1384 625 840 1415 1424 1410 1400 809 1447 1364 1451 1443 1507 1436 1450 1494 1469 1461 1584 1532 1452 1484 1543 1420 1567 1539 1613 1538 1555 1523 1513 1565 1406 1519 1532 1510 1552 1514 1554 1498 1474 1496 1453 1482 1534 1496 1372 1574 1367 1462 1421 1498 1518 1376 1475 1364 1528 1511 1479 1346 1290 1387 1294 1399 1513 1247 1308 1337 1396 1353 1480 1282 1360 1460 1456 1437 1453] MW1[1500 1472 1577 1563 1431 1435 1455 1511 1536 1483 1432 1402 1384 1464 1460 1549 1352 1396 1526 1374 830 1476 1398 1500 1157 1147 1301 1347 1387 1333 1429 1374 1385 1448 1376 1457 1424 1394 1302 1324 1342 1410 1374 1364 1408 1403 1347 1389 1504 1370 1424 1526 1495 1467 1520 1352 1497 1442 1402 1545 1532 1554 1527 1509 1533 1551 1494 1496 1549 1500 1504 1494 1556 1521 1517 1481 1504 1488 1516 1512 1561 1516 1541 1422 1406 1520 1469 1526 1565 1480 1466 1468 1396 1492 1510 1496 1514 1421 1435 1504 1534 1450 1460 1548 1487 1501 1390 1483 1499 1458 1561 1518 1493 1389 1444 1454 1439 1505 1510 1445] MW2[1429 1500 1446 1488 1477 1300 1375 1338 1462 1394 1465 1211 1329 1412 1419 1455 1361 1383 1409 1283 1394 1472 1401 1406 1280 1434 1466 1439 1324 1249 1336 1365 1505 985 1334 1373 1275 1307 1336 1357 1447 1339 1300 1379 1421 1476 1356 1515 1445 1382 1435 1435 1315 1418 1442 1567 1497 1379 1480 1483 1546 1487 1345 1422 1465 1412 1459 1372 1406 1395 1542 1379 1487 1537 1448 1435 1481 1459 1378 1339 1448 1455 1382 1333 1458 1382 1428 1404 1422 1394 1418 1429 1385 1439 1432 1439 1373 1543 1356 1347 1401 1436 1472 1526 1453 1389 1425 1536 1445 1481 1460 1372 1411 1451 1261 1495 1488 1475 1442 1434] ASICCRC0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] CRC[0 0 0] POW_I2C[OK] FACOPTS0[] FACOPTS1[] ATAOPTS0[--avalon10-freq 456:476:496:516 --avalon10-voltage-level 37 ] ATAOPTS1[--avalon10-freq 456:476:496:516 --avalon10-voltage-level 39 ] ADJ[1] COP[0 0 0] MPO[3200] MVL[87] ATABD0[456 476 496 516] ATABD1[456 476 496 516] ATABD2[456 476 496 516] WORKMODE[1]','MM Count':1,'Smart Speed':1,'Voltage Level Offset':0,'Nonce Mask':25}
You didn't follow what I suggested in my previous post as I said try to run the miner at higher fan speed. Because I notice TMAX reach higher temp.
Also, keep updating the API logs here so that we can analyze your issue well.
And normally you can't force this unit to run at high-performance mode but you can prefer to switch work mode to performance mode. You can find it under configuration on Web UI. This unit is not running stable at high-performance mode it automatically switches if they detect high ASIC temp. Look at your previous logs TMAX it shouldn't reach above 85c as a recommended chip temp.
Also, keep updating the API logs here so that we can analyze your issue well.
And normally you can't force this unit to run at high-performance mode but you can prefer to switch work mode to performance mode. You can find it under configuration on Web UI. This unit is not running stable at high-performance mode it automatically switches if they detect high ASIC temp. Look at your previous logs TMAX it shouldn't reach above 85c as a recommended chip temp.
Linked image of a graph showing hash over time and how it dropped down.
https://i.imgur.com/E4wQKbS.png
I see the ADJ field in the logs has a value of 0 which the manual indicates means aging is in progress. Perhaps this hash behavior is a result of the process? Any idea how long aging takes to complete?
update: ADJ[2] now shows indicating aging finished. Do I need to do a restart or do I let her keep running? Hashrate now up to 71 TH/s (still low)
https://i.imgur.com/E4wQKbS.png
I see the ADJ field in the logs has a value of 0 which the manual indicates means aging is in progress. Perhaps this hash behavior is a result of the process? Any idea how long aging takes to complete?
update: ADJ[2] now shows indicating aging finished. Do I need to do a restart or do I let her keep running? Hashrate now up to 71 TH/s (still low)
Ok I installed and ran the aging tool. Now may hashrate is diminishing rapidly. Within 10 mins of reboot it got up to 76 TH/s then over the next 20 mins declined down to 68 TH/s. Fan running at a constant 51% with temps steady between 63 and 68 degrees. Any thoughts on cause or action to take?
I got FMS installed. You suggested using aging which I do not see in the tool (I have tried V2.3.3 and V2.1.0). Do you know where I can find a list of commands or manual to know how to make the commands for the diagnose console? Doesnt seem to be in their manual. Thank you.
Other versions of FMS don't have an aging button there are two FMS v2.3.3 the one is the app version that doesn't have an aging button. You can find that button in the FMS v2.3.3(batch version) you can download it on Canaan technical support.
Or check this link below to download the batch version.
- https://canaan.io/wp-content/uploads/2020/03/FMS_V2.3.3_Windows.zip
If the logs you have are still the same as your previous logs above then I suspected that some chip temp is fluctuating above 85c. Since you have a large number of HW or hardware errors some chips are overheating and the hashboard will automatically disconnect if it happens then you will get ECMM[4] because it's disconnected automatically for protection and it will attempt to restart.
Another thing that I noticed from your previous logs is that the fan speed is not stable.
What I would like to suggest is to try to set the fan speed to at least 80% or 90% and let see if it will run stable for long. Just try even you have low room temp.
To set the fan speed you must have the FMS tool and then go to diagnostic and put this command below
Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.
Another solution that I would like you to try is to use the aging you can find it on the FMS tool along with the Diagnose it can calibrate all ASIC chips.
Another thing that I noticed from your previous logs is that the fan speed is not stable.
What I would like to suggest is to try to set the fan speed to at least 80% or 90% and let see if it will run stable for long. Just try even you have low room temp.
To set the fan speed you must have the FMS tool and then go to diagnostic and put this command below
Code:
[b][{"command":"ascset","parameter":"0,fan-spd,90"}] [/b]Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.
Another solution that I would like you to try is to use the aging you can find it on the FMS tool along with the Diagnose it can calibrate all ASIC chips.
I got FMS installed. You suggested using aging which I do not see in the tool (I have tried V2.3.3 and V2.1.0). Do you know where I can find a list of commands or manual to know how to make the commands for the diagnose console? Doesnt seem to be in their manual. Thank you.
You would be better off having the down right cold outside air mix with the room air and having the miners draw in the now cooler room air. Thing is miners do not like to run at chip temps much below 60C (140F). Reason is that being a power device, high temps are a natural part of the territory and semiconductors behave differently as temp rises. That is why miners have a pre-heat cycle before really starting to ramp up to full speed.
Ja the miner will try to control the temp by adjusting fan speed but that relies on Canaan properly tuning the temp/speed control loop... Point is the miners may just be too cold.
Ja the miner will try to control the temp by adjusting fan speed but that relies on Canaan properly tuning the temp/speed control loop... Point is the miners may just be too cold.
Interesting. I will have to get a Windows machine in order to get FMS running. Likely a weekend project. The ran speed is and has been always fluctuating up and down about every 30 seconds or so. The rooms ambient air is in the 80 degree Fahrenheit range but the machine is drawing outside cool air under 50 degrees Fahrenheit. I would like to get FMS going and set a fixed fan speed.
If the logs you have are still the same as your previous logs above then I suspected that some chip temp is fluctuating above 85c. Since you have a large number of HW or hardware errors some chips are overheating and the hashboard will automatically disconnect if it happens then you will get ECMM[4] because it's disconnected automatically for protection and it will attempt to restart.
Another thing that I noticed from your previous logs is that the fan speed is not stable.
What I would like to suggest is to try to set the fan speed to at least 80% or 90% and let see if it will run stable for long. Just try even you have low room temp.
To set the fan speed you must have the FMS tool and then go to diagnostic and put this command below
Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.
Another solution that I would like you to try is to use the aging you can find it on the FMS tool along with the Diagnose it can calibrate all ASIC chips.
Another thing that I noticed from your previous logs is that the fan speed is not stable.
What I would like to suggest is to try to set the fan speed to at least 80% or 90% and let see if it will run stable for long. Just try even you have low room temp.
To set the fan speed you must have the FMS tool and then go to diagnostic and put this command below
Code:
[b][{"command":"ascset","parameter":"0,fan-spd,90"}] [/b]Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.
Another solution that I would like you to try is to use the aging you can find it on the FMS tool along with the Diagnose it can calibrate all ASIC chips.
Been a few weeks since I last updated here. I have not yet taken the machine apart to ensure all wire connections are snug and screws tightened. Since then I have notice the miner still restarting itself about once every 3 days, even in cold easter (<50 degrees F). Today for the first time it turned off and simple did not restart itself. I had to manually unplug and replug it. Looking at the logs the ECMM[4] is still showing and this error code is not documented in their manual. Additionally I noticed the HW code frequesntly changing with values ranging from 97 to 119 for the few minutes I monitored the logs. The number only increased over time. The manual simple says HW means Hardware Error but provides no guidance on the codes.
If anyone has any idea what is going on here please do advise. Thank you.
If anyone has any idea what is going on here please do advise. Thank you.
Hello Everyone
I had the same issue with 1166 pro-81TH but from yesterday, my miner keeps rebooting itself. Can anyone help me to diagnose the problem?
I had the same issue with 1166 pro-81TH but from yesterday, my miner keeps rebooting itself. Can anyone help me to diagnose the problem?
Yes, both of you have the same ECMM[4] which is abnormal but we do not sure what is ECMM[4] you can't find that number on their description logs.
However, this is what I noticed and found this under your logs WORKMODE[0] which is it's running at normal mode it means the hashrate drop to normal hashrate maybe around 50-60TH/s
What I would like to suggest is to force the miner to the high-performance mode you can find it under configuration then work mode or use the FMS app to force it to high performance.
The ASIC was advertised to get 81 TH/s, but really never performed above 79 TH/s when I first got it. For months it performed in the 76-78 range and now is around 73.6 TH/s and decreasing with each passing day.
I think most asic miners are rated at +-5% so 3-4TH missing on an 81TH miner is pretty normal, what's not normal is the diminishing hash rate, this is a very strange problem, I believe your miner is auto-tuning itself and for some reason, it doesn't see the miner at a stable state with the current hashrate so it tunes the frequency to a lower figure just to keep the miner stable.
I don't own a similar gear but speaking from experience with other miners, the tuning part can go wrong at times, so try to flash a different firmware just to make sure the firmware isn't falling at tunning the hash boards.
Yes, that's pretty much all there is to it.
perfect thank you. Do you suggest I just un-plug and replug the ribbon cable, tighten any screws on the MM board, and ensure the hashboards are slotted in well again? Anything else?
The help is more close than you think, have a look at my Avalon troubleshooting guide https://bitcointalksearch.org/topic/troubleshooting-and-repair-guide-for-avalonminer-models-721-741-761-821-841-3224256
It's the control board for your hashboards.
It's the control board for your hashboards.
I'm not sure what MMboard stands for or even which part of the miner that is. Internet searching hasn't been helpful for this term unfortuantely.
I could not find meaning for number 4.
Can you try tightening the connection between MM board and the hash boards?
Just in case if it is loose after transport or something.
Can you try tightening the connection between MM board and the hash boards?
Just in case if it is loose after transport or something.
The ECMM gives you a number 4
(Error Code MM board).
Maybe the MM board (control board) is loosely connected to the hash boards?
Or maybe the MM board is damaged?
Do you have another MM board to try?
You can find the log text description guide here https://canaan.io/wp-content/uploads/2020/03/log-Description.pdf
Other Canaan documents: https://canaan.io/service/447
(Error Code MM board).
Maybe the MM board (control board) is loosely connected to the hash boards?
Or maybe the MM board is damaged?
Do you have another MM board to try?
You can find the log text description guide here https://canaan.io/wp-content/uploads/2020/03/log-Description.pdf
Other Canaan documents: https://canaan.io/service/447
Reading the doc on ECMM:
Quote
When ECMM
What does 4 mean here? Seems like not specified? I don;t have any extra spare parts - , it means that the MM board is in normal state. When ECMM [1], it means that the MM board may have problems, or it may have poor contact with the hash board. The specific problem of the hash board can be judged by the value returned below. When Echu displays 0 or 512, it means normal. If Echu displays 513, it means abnormal.
Jump to: