![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 29, 2014, 04:38:03 PM Last edit: April 30, 2014, 08:55:24 PM by huachis |
|
Hi everyone In the CG miner API LOG there are two match work count that appears as 0:
[frequency] => 1300 [fan1] => 3840 [fan2] => 4080 [fan3] => 4080 [temp1] => 31 [temp2] => 55 [temp3] => -1 [temp_max] => 56 [Device Hardware%] => 1.8309 [no_matching_work] => 1489 [match_work_count1] => 10575 [match_work_count2] => 10579 [match_work_count3] => 10519 [match_work_count4] => 10540 [match_work_count5] => 10330 [match_work_count6] => 10475 [match_work_count7] => 10391 [match_work_count8] => 10581 [match_work_count9] => 0 [match_work_count10] => 10475 [match_work_count11] => 0 [match_work_count12] => 10610 [match_work_count13] => 10439 [match_work_count14] => 10294 [match_work_count15] => 10472 [match_work_count16] => 10522 [Controller Version] => 2013110865 [Avalon Chip] => 55 [USB Pipe] => 0 [USB Delay] => r0 0.000000 w0 0.000000 [USB tmo] => 877133 0 ) [STATS1] =>
After this two match work counts turned into 0 the miner is not giving me full hash speed at the most give me 170GHS Any idea why is this happening? I have other miner with the match work count 9 = 0, this one have like one month running now with the match work 9 = 0, but the count 11 have only 4 days that it went 0.
How could i fix it?? Thaankss
|