Author

Topic: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs - page 573. (Read 1260354 times)

hero member
Activity: 742
Merit: 500
The "Spondoolies hero of the day" medal goes to user Klondike_bar, for discovering a problem of high error rate on his machine. We released a fix (1.4.3) that should bring the HW error rate down from ~8% to 2%.

Please update ASAP and let me know if the fix works.

my HW errors on firmware version 1.4.2 settled down to about 5%

I will try 1.4.3 and report back tomorrow with results.

thanks zvisha and klondike_bar

BTW, what did klondike_bar discover?

His machine had exceptionally high error rate of over 10%. I have error rate of about 3-4%. He let me use his machine to understand the situation, and I found out that the fix for his machine improves HW errors in all my machines too. It is the way I use BIST to find optimal point, the BIST I did was too weak for many ASICs.
 

Firmware rev 1.4.3 looks like a real winner. I also have a SP10 that was registering around 100 GH/s lower at the pool due to high hardware errors, but firmware rev 1.4.3 seems to have raised the pool hash rate of this unit substantially.

Thanks zvisha!
hero member
Activity: 560
Merit: 500
...
Any other information that I can provide for you, please let me know.

Ok, thanks!
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Ok, Con knows of the issue, it will be fixed soon.
For now use previous version for p2p.

Did the 1.4.2 firmware update do something to disable mining on p2pool?  I have updated, and now my SP10 will not connect to ANY p2pool node.  I can connect to Eligius, BTCGuild, GHash, etc.  My local p2pool node?  No.  Any other p2pool node?  No.  Before anyone asks... yes, my local node is up.  I can confirm this because my 2 S1s are happily hashing away on it.  I have also pointed those two to another p2pool node and they hashed there as well.

Thanks for the help.


Thanks Zvisha.  I tried 1.4.3, and it also does not see any p2pool node.  I'll go back to 1.3.49 until a fix can be made.

BTW, do you know how much bandwidth P2P node takes in cgminer for SP10? What hash rate it provides and what is the leading zeroes?
Here's a snapshot of my ASIC stats page from just a few seconds ago:
Code:
----------
AC2DC power=1096[1100], temp=0, leading zeroes=39
L |Vtrm/max  |vlt|Wt|Am|DCt|crt|Gh|Ov|ID |aTMP|Freq |Th|Bt|Engn|Wn |ID |aTMP|Freq |Th|Bt|Engn|Wn |ID |aTMP|Freq |Th|Bt|Engn|Wn |ID |aTMP|Freq |Th|Bt|Engn|Wn
 0|ffec(fff6)|661|32|49| 71|  0|55| 0|  0: 77c 480hz( 0/ 0) 7fff 15|  1: 77c 480hz( 0/ 0) 7fff 16|  2: 77c 465hz( 0/ 0) 7fff 25|  3: 77c 450hz( 0/ 0) 7fff 17
                                     |  4: 77c 480hz( 0/ 0) 7fff 14|  5: 77c 435hz( 0/ 0) 7fff 10|  6: 77c 465hz( 0/ 0) 7fff 18|  7: 77c 450hz( 0/ 0) 7fff 16
 1|ffeb(fff6)|658|32|49| 64|  0|55| 0|  8: 77c 450hz( 0/ 0) 7fff 10|  9: 77c 495hz( 0/ 0) 7fff 15| 10: 77c 495hz( 0/ 0) 7fff 12| 11: 77c 450hz( 0/ 0) 7fff  9
                                     | 12: 77c 450hz( 0/ 0) 7fff 19| 13: 77c 450hz( 0/ 0) 7fff 16| 14: 77c 450hz( 0/ 0) 7fff 10| 15: 77c 450hz( 0/ 0) 7fff  9
 2|ffeb(fff6)|658|31|48| 62|  0|54| 0| 16: 77c 435hz( 0/ 0) 7fff 14| 17: 77c 480hz( 0/ 0) 7fff 12| 18: 77c 450hz( 0/ 0) 7fff 11| 19: 77c 450hz( 0/ 0) 7fff 11
                                     | 20: 77c 480hz( 0/ 0) 7fff 18| 21: 77c 465hz( 0/ 0) 7fff 22| 22: 77c 480hz( 0/ 0) 7fff 12| 23: 77c 420hz( 0/ 0) 7fff 12
 3|ffeb(fff6)|658|32|49| 65|  0|54| 0| 24: 77c 465hz( 0/ 0) 7fff 15| 25: 77c 420hz( 0/ 0) 7fff 15| 26: 77c 450hz( 0/ 0) 7fff  7| 27: 77c 450hz( 0/ 0) 7fff 10
                                     | 28: 77c 465hz( 0/ 0) 7fff 12| 29: 77c 465hz( 0/ 0) 7fff 20| 30: 77c 480hz( 0/ 0) 7fff 20| 31: 77c 465hz( 0/ 0) 7fff 18
 4|ffea(fff6)|656|32|49| 72|  0|54| 0| 32: 77c 480hz( 0/ 0) 7fff 15| 33: 77c 450hz( 0/ 0) 7fff 16| 34: 77c 435hz( 0/ 0) 7fff 18| 35: 77c 465hz( 0/ 0) 7fff 25
                                     | 36: 77c 450hz( 0/ 0) 7fff 15| 37: 77c 450hz( 0/ 0) 7fff 11| 38: 77c 465hz( 0/ 0) 7fff 17| 39: 77c 465hz( 0/ 0) 7fff 18
 5|ffea(fff6)|656|32|50| 67|  0|55| 0| 40: 77c 450hz( 0/ 0) 7fff 14| 41: 77c 480hz( 0/ 0) 7fff 13| 42: 77c 480hz( 0/ 0) 7fff  6| 43: 77c 465hz( 0/ 0) 7fff 14
                                     | 44: 77c 465hz( 0/ 0) 7fff 12| 45: 77c 435hz( 0/ 0) 7fff  5| 46: 77c 465hz( 0/ 0) 7fff 13| 47: 77c 480hz( 0/ 0) 7fff 14
 6|ffea(fff6)|656|33|50| 56|  0|53| 0| 48: 77c 435hz( 0/ 0) 7fff 17| 49: 77c 465hz( 0/ 0) 7fff  9| 50: 77c 405hz( 0/ 0) 7fff 15| 51: 77c 465hz( 0/ 0) 7fff 20
                                     | 52: 77c 450hz( 0/ 0) 7fff 13| 53: 77c 435hz( 0/ 0) 7fff 12| 54: 77c 465hz( 0/ 0) 7fff 18| 55: 77c 450hz( 0/ 0) 7fff 11
 7|ffea(fff6)|656|33|50| 82|  0|54| 0| 56: 77c 435hz( 0/ 0) 7fff 11| 57: 77c 480hz( 0/ 0) 7fff 18| 58: 77c 480hz( 0/ 0) 7fff 15| 59: 77c 465hz( 0/ 0) 7fff 23
                                     | 60: 77c 435hz( 0/ 0) 7fff 17| 61: 77c 465hz( 0/ 0) 7fff 11| 62: 77c 465hz( 0/ 0) 7fff 14| 63: 77c 420hz( 0/ 0) 7fff 21
 8|ffea(fff6)|656|33|51| 76|  0|55| 0| 64: 77c 450hz( 0/ 0) 7fff 12| 65: 77c 480hz( 0/ 0) 7fff 11| 66: 77c 450hz( 0/ 0) 7fff 14| 67: 77c 465hz( 0/ 0) 7fff 14
                                     | 68: 77c 435hz( 0/ 0) 7fff 11| 69: 77c 465hz( 0/ 0) 7fff 12| 70: 77c 465hz( 0/ 0) 7fff 15| 71: 77c 465hz( 0/ 0) 7fff 13
 9|ffea(fff6)|656|33|51| 72|  0|54| 0| 72: 77c 480hz( 0/ 0) 7fff 24| 73: 77c 450hz( 0/ 0) 7fff 16| 74: 77c 435hz( 0/ 0) 7fff  9| 75: 77c 480hz( 0/ 0) 7fff 21
                                     | 76: 77c 435hz( 0/ 0) 7fff 10| 77: 77c 435hz( 0/ 0) 7fff 11| 78: 77c 465hz( 0/ 0) 7fff  8| 79: 77c 465hz( 0/ 0) 7fff 17
10|ffea(fff6)|656|33|50| 69|  0|55| 0| 80: 77c 480hz( 0/ 0) 7fff 13| 81: 77c 465hz( 0/ 0) 7fff 10| 82: 77c 450hz( 0/ 0) 7fff 15| 83: 77c 435hz( 0/ 0) 7fff  9
                                     | 84: 77c 450hz( 0/ 0) 7fff 21| 85: 77c 465hz( 0/ 0) 7fff 15| 86: 77c 465hz( 0/ 0) 7fff 19| 87: 77c 480hz( 0/ 0) 7fff 12
11|ffe9(fff6)|653|32|50| 73|  0|54| 0| 88: 77c 465hz( 0/ 0) 7fff 17| 89: 77c 450hz( 0/ 0) 7fff 12| 90: 77c 435hz( 0/ 0) 7fff 11| 91: 77c 450hz( 0/ 0) 7fff 11
                                     | 92: 77c 450hz( 0/ 0) 7fff 14| 93: 77c 465hz( 0/ 0) 7fff 12| 94: 77c 435hz( 0/ 0) 7fff 13| 95: 77c 495hz( 0/ 0) 7fff 10
12|ffeb(fff6)|658|32|49| 68|  0|55| 0| 96: 77c 480hz( 0/ 0) 7fff  9| 97: 77c 480hz( 0/ 0) 7fff 13| 98: 77c 435hz( 0/ 0) 7fff  6| 99: 77c 465hz( 0/ 0) 7fff 16
                                     |100: 77c 450hz( 0/ 0) 7fff 14|101: 77c 465hz( 0/ 0) 7fff 12|102: 77c 450hz( 0/ 0) 7fff 18|103: 77c 450hz( 0/ 0) 7fff 18
13|ffeb(fff6)|658|34|52| 74|  0|57| 0|104: 77c 495hz( 0/ 0) 7fff 14|105: 77c 435hz( 0/ 0) 7fff 14|106: 77c 510hz( 0/ 0) 7fff  9|107: 77c 510hz( 0/ 0) 7fff 10
                                     |108: 77c 450hz( 0/ 0) 7fff 13|109: 77c 465hz( 0/ 0) 7fff 14|110: 77c 435hz( 0/ 0) 7fff 13|111: 77c 525hz( 0/ 0) 7fff 14
14|ffeb(fff6)|658|35|54| 79|  0|58| 0|112: 77c 480hz( 0/ 0) 7fff 11|113: 77c 495hz( 0/ 0) 7fff 14|114: 77c 510hz( 0/ 0) 7fff 11|115: 77c 480hz( 0/ 0) 7fff 14
                                     |116: 77c 480hz( 0/ 0) 7fff 18|117: 77c 495hz( 0/ 0) 7fff 11|118: 77c 465hz( 0/ 0) 7fff 13|119: 77c 510hz( 0/ 0) 7fff 22
15|ffeb(fff6)|658|35|53| 74|  0|56| 0|120: 77c 495hz( 0/ 0) 7fff 15|121: 77c 450hz( 0/ 0) 7fff  5|122: 77c 480hz( 0/ 0) 7fff 14|123: 77c 480hz( 0/ 0) 7fff 17
                                     |124: 77c 495hz( 0/ 0) 7fff 17|125: 77c 450hz( 0/ 0) 7fff 20|126: 77c 465hz( 0/ 0) 7fff 11|127: 77c 480hz( 0/ 0) 7fff 10
16|ffea(fff6)|656|36|56| 72|  0|57| 0|128: 77c 465hz( 0/ 0) 7fff 21|129: 77c 465hz( 0/ 0) 7fff  7|130: 77c 480hz( 0/ 0) 7fff 16|131: 77c 480hz( 0/ 0) 7fff 16
                                     |132: 77c 510hz( 0/ 0) 7fff 19|133: 77c 495hz( 0/ 0) 7fff 12|134: 77c 480hz( 0/ 0) 7fff 15|135: 77c 480hz( 0/ 0) 7fff 22
17|ffea(fff6)|656|35|54| 79|  0|56| 0|136: 77c 480hz( 0/ 0) 7fff 21|137: 77c 435hz( 0/ 0) 7fff  9|138: 77c 450hz( 0/ 0) 7fff 15|139: 77c 510hz( 0/ 0) 7fff 18
                                     |140: 77c 480hz( 0/ 0) 7fff 11|141: 77c 465hz( 0/ 0) 7fff 11|142: 77c 495hz( 0/ 0) 7fff 19|143: 77c 480hz( 0/ 0) 7fff 11
18|ffea(fff6)|656|36|55| 73|  0|56| 0|144: 77c 480hz( 0/ 0) 7fff 10|145: 77c 480hz( 0/ 0) 7fff 22|146: 77c 480hz( 0/ 0) 7fff 10|147: 77c 450hz( 0/ 0) 7fff 18
                                     |148: 77c 480hz( 0/ 0) 7fff 17|149: 77c 450hz( 0/ 0) 7fff 12|150: 77c 480hz( 0/ 0) 7fff 16|151: 77c 465hz( 0/ 0) 7fff 11
19|ffea(fff6)|656|35|54| 74|  0|57| 0|152: 77c 480hz( 0/ 0) 7fff 16|153: 77c 480hz( 0/ 0) 7fff  9|154: 77c 480hz( 0/ 0) 7fff 15|155: 77c 480hz( 0/ 0) 7fff 16
                                     |156: 77c 465hz( 0/ 0) 7fff 12|157: 77c 465hz( 0/ 0) 7fff 14|158: 77c 510hz( 0/ 0) 7fff 25|159: 77c 465hz( 0/ 0) 7fff 13
20|ffe9(fff6)|653|36|55| 78|  0|57| 0|160: 77c 480hz( 0/ 0) 7fff 12|161: 77c 495hz( 0/ 0) 7fff 14|162: 77c 465hz( 0/ 0) 7fff 14|163: 77c 510hz( 0/ 0) 7fff 17
                                     |164: 77c 450hz( 0/ 0) 7fff 12|165: 77c 465hz( 0/ 0) 7fff 13|166: 77c 495hz( 0/ 0) 7fff  8|167: 77c 465hz( 0/ 0) 7fff 24
21|ffe9(fff6)|653|34|52| 74|  0|55| 0|168: 77c 495hz( 0/ 0) 7fff 20|169: 77c 480hz( 0/ 0) 7fff 18|170: 77c 495hz( 0/ 0) 7fff 20|171: 77c 450hz( 0/ 0) 7fff 18
                                     |172: 77c 450hz( 0/ 0) 7fff 10|173: 77c 375hz( 0/ 0) 7fff 12|174: 77c 480hz( 0/ 0) 7fff 11|175: 77c 465hz( 0/ 0) 7fff 14
22|ffe9(fff6)|653|34|53| 81|  0|56| 0|176: 77c 480hz( 0/ 0) 7fff 12|177: 77c 435hz( 0/ 0) 7fff  8|178: 77c 480hz( 0/ 0) 7fff 23|179: 77c 495hz( 0/ 0) 7fff 18
                                     |180: 77c 450hz( 0/ 0) 7fff 19|181: 77c 465hz( 0/ 0) 7fff 18|182: 77c 480hz( 0/ 0) 7fff  8|183: 77c 450hz( 0/ 0) 7fff 21
23|ffe8(fff6)|650|36|55| 76|  0|56| 0|184: 77c 480hz( 0/ 0) 7fff 15|185: 77c 495hz( 0/ 0) 7fff 14|186: 77c 465hz( 0/ 0) 7fff 15|187: 77c 495hz( 0/ 0) 7fff 16
                                     |188: 77c 465hz( 0/ 0) 7fff 16|189: 77c 450hz( 0/ 0) 7fff 12|190: 77c 465hz( 0/ 0) 7fff 14|191: 77c 465hz( 0/ 0) 7fff  9
[H:HW:1341Gh/Th:1341Gh/W:1341Gh,W:819,L:24,A:192,ER:1341,EP:1030,MMtmp:23]
Pushed 543 jobs , in queue 75 jobs!
wins:2747[fp:0], leading-zeroes:39 idle:0/0 :)
Adapter queues: rsp=78, req=270

Here's DCR:
Code:
DC2DC DCR inductor flag loop 0 (0xD0) = 1
DC2DC DCR inductor flag loop 1 (0xD0) = 1
DC2DC DCR inductor flag loop 2 (0xD0) = 1
DC2DC DCR inductor flag loop 3 (0xD0) = 1
DC2DC DCR inductor flag loop 4 (0xD0) = 1
DC2DC DCR inductor flag loop 5 (0xD0) = 1
DC2DC DCR inductor flag loop 6 (0xD0) = 1
DC2DC DCR inductor flag loop 7 (0xD0) = 1
DC2DC DCR inductor flag loop 8 (0xD0) = 1
DC2DC DCR inductor flag loop 9 (0xD0) = 1
DC2DC DCR inductor flag loop 10 (0xD0) = 1
DC2DC DCR inductor flag loop 11 (0xD0) = 1
DC2DC DCR inductor flag loop 12 (0xD0) = 1
DC2DC DCR inductor flag loop 13 (0xD0) = 1
DC2DC DCR inductor flag loop 14 (0xD0) = 1
DC2DC DCR inductor flag loop 15 (0xD0) = 1
DC2DC DCR inductor flag loop 16 (0xD0) = 1
DC2DC DCR inductor flag loop 17 (0xD0) = 1
DC2DC DCR inductor flag loop 18 (0xD0) = 1
DC2DC DCR inductor flag loop 19 (0xD0) = 1
DC2DC DCR inductor flag loop 20 (0xD0) = 1
DC2DC DCR inductor flag loop 21 (0xD0) = 1
DC2DC DCR inductor flag loop 22 (0xD0) = 1
DC2DC DCR inductor flag loop 23 (0xD0) = 1

Temps, load, etc:


Stats:


Pool data:


Any other information that I can provide for you, please let me know.
sr. member
Activity: 434
Merit: 250
pools report hashrates using packet data sent from your miner, so the hashrate showing at your pool is likely to be showing on a slight delay, and usually not exact. Best always to go by the stats showing on the UI / Cgminer.

The stats in the UI are definitely lower than before.  The pool - you're right, there's variance because it's based on data packets sent.  It's now at 3.9 TH.  Still better than before though, which ranged from 3.7 to 4 TH (super lows and super highs).

Right now my super lows and highs are 3.8 TH and 4.1 TH.  You can never go by those numbers of course.  Avg seems to be about 100 GH more on the pool (or about 33 GH faster each miner when you divide by 3).

yup... you should try mining on a DGM pool, the highs and lows are ridiculously off! I've seen my SP10 showing as much as 1.7TH/s on Ozcoin... currently showing 1.56TH/s on mmpool.
hero member
Activity: 677
Merit: 500
pools report hashrates using packet data sent from your miner, so the hashrate showing at your pool is likely to be showing on a slight delay, and usually not exact. Best always to go by the stats showing on the UI / Cgminer.

The stats in the UI are definitely lower than before.  The pool - you're right, there's variance because it's based on data packets sent.  It's now at 3.9 TH.  Still better than before though, which ranged from 3.7 to 4 TH (super lows and super highs).

Right now my super lows and highs are 3.8 TH and 4.1 TH.  You can never go by those numbers of course.  Avg seems to be about 100 GH more on the pool (or about 33 GH faster each miner when you divide by 3).
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
can we have a status update on June batch please? thanks

Didn't you hear the news, they sold all remaining Sp-10 to Taras [LNU].

Biodom, I have an order for 2 SP10 from June batch, i guess you were just too late. that's how it is mucker  Cheesy
a s-t-a-t-u-s update - you perceive this to mean something other than a s-t-a-t-u-s update.

Don't act so butt-hurt about it.


hey, i am hurt about it because i communicated with them on saturday night and was given no indication that I have to do it in BTC that very moment and when I was about to go to the bank on Monday am and was checking the forum-boom, they had sold it.

"Callum decided to call his father-in-law the "Exorcist" because every time he came to visit he made the spirits disappear"



Biodom, the sold-out was very fast due to several large orders we got. We didn't expect it either. On Saturday night we had solid stock.

Regards,
Guy
hero member
Activity: 560
Merit: 500
Ok, Con knows of the issue, it will be fixed soon.
For now use previous version for p2p.

Did the 1.4.2 firmware update do something to disable mining on p2pool?  I have updated, and now my SP10 will not connect to ANY p2pool node.  I can connect to Eligius, BTCGuild, GHash, etc.  My local p2pool node?  No.  Any other p2pool node?  No.  Before anyone asks... yes, my local node is up.  I can confirm this because my 2 S1s are happily hashing away on it.  I have also pointed those two to another p2pool node and they hashed there as well.

Thanks for the help.


Thanks Zvisha.  I tried 1.4.3, and it also does not see any p2pool node.  I'll go back to 1.3.49 until a fix can be made.

BTW, do you know how much bandwidth P2P node takes in cgminer for SP10? What hash rate it provides and what is the leading zeroes?
hero member
Activity: 560
Merit: 500
Hey Zvi,

One miner is working at :
26C/72C (in/out) - 227V - AC2DC power=1256[1265], temp=0, leading zeroes=41
[H:HW:1446Gh/Th:1446Gh/W:1446Gh,W:945,L:24,A:192,ER:1446,EP:1222,MMtmp:26]

The other is working at:
27C/77C (in/out) - 222V - AC2DC power=1254[1265], temp=0, leading zeroes=40
[H:HW:1397Gh/Th:1398Gh/W:1397Gh,W:944,L:24,A:192,ER:1397,EP:1222,MMtmp:27]

Just wondering how come the second miner never breaks that 1.42TH and is around 1.4TH all the time - while the first is stuck at 1.46TH....
I know it is within the 10% tolerance - just wondering...

Both miners overclocked according to your post.

It depends on the HW you got. Our first batch was our best and with low variance between machines, it gets to 1.5 easy with the over-clocking (and even 1.57 in iceland temperatures Smiley ) and 1.35 for 110V. The second batch was much more diverse and very temperature dependant, ranging from 1.36 to 1.48 for 220V and 1.25 to 1.33 for 110V.
hero member
Activity: 560
Merit: 500

I just upgraded all 3 SP10s to 1.4.2 and they are now much slower at 1.2TH.  They were getting 1.3TH before the firmware upgrade (1.3.49).

As I checked for the previous version number I noticed you just promoted 1.4.3 from test version to stable.  What is the changelog between all 3 versions?

Please try 1.4.3 and let me know how it behaves as self-reported rate, rate in pool and error rate.
Also please send me your Webpages with DCRs, ASICs shots and front page of the version you have now (I guess 1.4.2) and 1.4.3.

Note that at start miners always work slower, and then rise their rate till they find optimal point.

Nevermind the changelog.  I read in your previous post.  I can't wait to test the 110v limit lift.  The cables I am using are 14 gauge, so they should be ok.

I can't do screenshots yet because I'm at work.  Well, I can, but I can't... (can't have anything too obvious on my screen to show I'm not working, lol).

I was able to remote in to check the hashrate and the miners report a slower rates than before by about 10 to 30 GH.  One is 10 GH less, another is 20 GH less, and the 3rd is 30 GH less.  However, BTC Guild reports FASTER rates than before.  I don't know what they were individually, but normally all 3 would give me around 3.8 TH, but now it's 4 TH.

Maybe there were more HW errors in 1.3.49 than in 1.4.3?  Who knows.  I honestly didn't pay attention to the HW errors.


This is exactly what I would expect. Great news, we just gained ~5%!
legendary
Activity: 3892
Merit: 4331
can we have a status update on June batch please? thanks

Didn't you hear the news, they sold all remaining Sp-10 to Taras [LNU].

Biodom, I have an order for 2 SP10 from June batch, i guess you were just too late. that's how it is mucker  Cheesy
a s-t-a-t-u-s update - you perceive this to mean something other than a s-t-a-t-u-s update.

Don't act so butt-hurt about it.


hey, i am hurt about it because i communicated with them on saturday night and was given no indication that I have to do it in BTC that very moment and when I was about to go to the bank on Monday am and was checking the forum-boom, they had sold it.

"Callum decided to call his father-in-law the "Exorcist" because every time he came to visit he made the spirits disappear"

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
Ok, Con knows of the issue, it will be fixed soon.
For now use previous version for p2p.

Did the 1.4.2 firmware update do something to disable mining on p2pool?  I have updated, and now my SP10 will not connect to ANY p2pool node.  I can connect to Eligius, BTCGuild, GHash, etc.  My local p2pool node?  No.  Any other p2pool node?  No.  Before anyone asks... yes, my local node is up.  I can confirm this because my 2 S1s are happily hashing away on it.  I have also pointed those two to another p2pool node and they hashed there as well.

Thanks for the help.


Thanks Zvisha.  I tried 1.4.3, and it also does not see any p2pool node.  I'll go back to 1.3.49 until a fix can be made.
sr. member
Activity: 434
Merit: 250
pools report hashrates using packet data sent from your miner, so the hashrate showing at your pool is likely to be showing on a slight delay, and usually not exact. Best always to go by the stats showing on the UI / Cgminer.
hero member
Activity: 677
Merit: 500

I just upgraded all 3 SP10s to 1.4.2 and they are now much slower at 1.2TH.  They were getting 1.3TH before the firmware upgrade (1.3.49).

As I checked for the previous version number I noticed you just promoted 1.4.3 from test version to stable.  What is the changelog between all 3 versions?

Please try 1.4.3 and let me know how it behaves as self-reported rate, rate in pool and error rate.
Also please send me your Webpages with DCRs, ASICs shots and front page of the version you have now (I guess 1.4.2) and 1.4.3.

Note that at start miners always work slower, and then rise their rate till they find optimal point.

Nevermind the changelog.  I read in your previous post.  I can't wait to test the 110v limit lift.  The cables I am using are 14 gauge, so they should be ok.

I can't do screenshots yet because I'm at work.  Well, I can, but I can't... (can't have anything too obvious on my screen to show I'm not working, lol).

I was able to remote in to check the hashrate and the miners report a slower rates than before by about 10 to 30 GH.  One is 10 GH less, another is 20 GH less, and the 3rd is 30 GH less.  However, BTC Guild reports FASTER rates than before.  I don't know what they were individually, but normally all 3 would give me around 3.8 TH, but now it's 4 TH.

Maybe there were more HW errors in 1.3.49 than in 1.4.3?  Who knows.  I honestly didn't pay attention to the HW errors.
hero member
Activity: 546
Merit: 500
Owner, Minersource.net
I have not had any problems with p2p on any firmware on any of my sp10s.
full member
Activity: 196
Merit: 100
Hey Zvi,

One miner is working at :
26C/72C (in/out) - 227V - AC2DC power=1256[1265], temp=0, leading zeroes=41
[H:HW:1446Gh/Th:1446Gh/W:1446Gh,W:945,L:24,A:192,ER:1446,EP:1222,MMtmp:26]

The other is working at:
27C/77C (in/out) - 222V - AC2DC power=1254[1265], temp=0, leading zeroes=40
[H:HW:1397Gh/Th:1398Gh/W:1397Gh,W:944,L:24,A:192,ER:1397,EP:1222,MMtmp:27]

Just wondering how come the second miner never breaks that 1.42TH and is around 1.4TH all the time - while the first is stuck at 1.46TH....
I know it is within the 10% tolerance - just wondering...

Both miners overclocked according to your post.
hero member
Activity: 560
Merit: 500
The "Spondoolies hero of the day" medal goes to user Klondike_bar, for discovering a problem of high error rate on his machine. We released a fix (1.4.3) that should bring the HW error rate down from ~8% to 2%.

Please update ASAP and let me know if the fix works.

my HW errors on firmware version 1.4.2 settled down to about 5%

I will try 1.4.3 and report back tomorrow with results.

thanks zvisha and klondike_bar

BTW, what did klondike_bar discover?

His machine had exceptionally high error rate of over 10%. I have error rate of about 3-4%. He let me use his machine to understand the situation, and I found out that the fix for his machine improves HW errors in all my machines too. It is the way I use BIST to find optimal point, the BIST I did was too weak for many ASICs.
 
hero member
Activity: 574
Merit: 500
1.21 GIGA WATTS
The "Spondoolies hero of the day" medal goes to user Klondike_bar, for discovering a problem of high error rate on his machine. We released a fix (1.4.3) that should bring the HW error rate down from ~8% to 2%.

Please update ASAP and let me know if the fix works.

my HW errors on firmware version 1.4.2 settled down to about 5%

I will try 1.4.3 and report back tomorrow with results.

thanks zvisha and klondike_bar

BTW, what did klondike_bar discover?
hero member
Activity: 560
Merit: 500
Please write to me and remo, i would like to investigate. Did others here get degradation or hw error increase with some specific version?
My test miners show up to 3% difference between self reported and pool. Do you see more?


I just upgraded all 3 SP10s to 1.4.2 and they are now much slower at 1.2TH.  They were getting 1.3TH before the firmware upgrade (1.3.49).

As I checked for the previous version number I noticed you just promoted 1.4.3 from test version to stable.  What is the changelog between all 3 versions?

Please try 1.4.3 and let me know how it behaves as self-reported rate, rate in pool and error rate.
Also please send me your Webpages with DCRs, ASICs shots and front page of the version you have now (I guess 1.4.2) and 1.4.3.

Note that at start miners always work slower, and then rise their rate till they find optimal point.
hero member
Activity: 677
Merit: 500
Please write to me and remo, i would like to investigate. Did others here get degradation or hw error increase with some specific version?
My test miners show up to 3% difference between self reported and pool. Do you see more?


I just upgraded all 3 SP10s to 1.4.2 and they are now much slower at 1.2TH.  They were getting 1.3TH before the firmware upgrade (1.3.49).

As I checked for the previous version number I noticed you just promoted 1.4.3 from test version to stable.  What is the changelog between all 3 versions?
hero member
Activity: 560
Merit: 500
The "Spondoolies hero of the day" medal goes to user Klondike_bar, for discovering a problem of high error rate on his machine. We released a fix (1.4.3) that should bring the HW error rate down from ~8% to 2%.

Please update ASAP and let me know if the fix works.
Jump to: