Topic: ANTMINER S3+ Discussion and Support Thread - page 35. (Read 710164 times)

I occasionally get such bugs. Sometimes the temperature line disappears. You can try another firmware, but I think you are good that way as well.

You can also install the firmware without keeping your settings, or reset the miner.

I upgraded to the latest firmware and now the second fan speed no longer shows up in the Bitmain or M's monitor GUI.

Is this common and is there a fix?

I just depress the reset while powering on, keeping it depressed 90 seconds, release the button and power down, wait 45 seconds then power up and I find the default stuff.

Yes that's exactly what I do. No problems with my other s3 when resetting.

It should be:


I think your doing it right.  The main thing is giving it time after the reset to go back.  But if it's faulty you could try this all day and it will not recover.

Nope, I have only tried the 10 second x 3 min method.

So I guess I have to power it and let it blink red for 3 minutes then press the reset for 90 seconds?

Have your tried a 90 second depression of the reset button?

Thanks I have ordered usb to serial/TTL converter and will try this method out. Bitmain is asking for 30€ for a replacement. You have to send them the defective pbc.

I paid for a replacement once, but wish I would have tried a few thing's.   I suggest looking into serial connection over usb - https://bitcointalksearch.org/topic/bitmain-s3-serial-connect-889206 is one example.  It is possible you might be able to recover it.

If you cannot recover it contact Bitmain Support and ask to buy a replacement.  I know I did this long ago and they got it to me quick.  It was out of warranty so I paid for the part.

Hello,

one of my Antminer S3 control PBC is fried. Red LED is blinking constantly and the miner is not accessible via Ethernet. Reset button is not working anymore.


Where can I send the board for repairs? How much would it cost to order a new board? I am located in Germany.

I added the #s from here, but the only freq I run is 250: https://bitcointalksearch.org/topic/m.8370071

I mine for hobby, not profit, so the S3+ is a great machine for me.  It's quiet and uses less power than my S1.

undervolt and underclock is good...but I like to take shots at new coins not just beat the dead horse of btc but grab a startup 256 coin quick and hope it pays off.
some will some wont but faster ghz at start = more block found :>) mining arbit coin rt now solo and have found 4 blocks in a few hours:>)
but yes I agree not much time foe btc mining and I run .11 per Kw....but I bought a solar panel and plan to get system totally off grid to run from sun!

i think you are beating a dead horse here..

these s3s are near the end of life.
at .10c per KWH you have until 65b difficulty before they start costing more than they make. its not that far away..


what needs to be found is a way to undervolt and underclock them.

ive add a lot of steps....
pb:value("10:400:0f82", translate("400M"))
pb:value("10:375:oe82", translate("375M"))
pb:value("12:352.5:0e08", translate("352.5M"))   .....
pb:value("11:350:0d82", translate("350M"))
   pb:value("12:348.75:2106", translate("348.75M"))   ........
   pb:value("12:327.5:0d08", translate("327.5M"))   ......
pb:value("12:325.25:0c82", translate("325M"))
   pb:value("12:323.75:1906", translate("323.75M"))   ........
   pb:value("12:302.5:0c02", translate("302.5M"))   .......
pb:value("13:300:0b82", translate("300M"))
pb:value("14:293.75:1706", translate("293.75M"))
pb:value("14:287.5:0b02", translate("287.5M"))
pb:value("14:281.25:1606", translate("281.25M"))
pb:value("14:275:0a82", translate("275M"))                   
pb:value("15:268.75:1506", translate("268.75M"))
pb:value("15:262.5:0a02", translate("262.5M"))
pb:value("16:256.25:1406", translate("256.25M"))
pb:value("16:250:0982", translate("250M"))
pb:value("16:243.75:1306", translate("243.75M"))
pb:value("17:237.5:1286", translate("237.5M"))
pb:value("17:231.25:1206", translate("231.25M"))
pb:value("18:225:0882", translate("225M"))
   pb:value("18:225:1156", translate("225M (test)"))            ........................
   pb:value("18:218.75:1131", translate("221.875M (test2)"))     ............................
pb:value("18:218.75:1106", translate("218.75M (default)"))
pb:value("18:212.5:1086", translate("212.5M"))
pb:value("19:206.25:1006", translate("206.25M"))
   pb:value("19:193.75:0906", translate("193.75M (test3)"))      ..........................
pb:value("20:200:0782", translate("200M"))
pb:value("20:196:1f07", translate("196M"))
pb:value("20:193:0f03", translate("193M"))
pb:value("23:175:0d83", translate("175M"))
pb:value("27:150:0b83", translate("150M"))
pb:value("33:125:0983", translate("125M"))
pb:value("40:100:0783", translate("100M"))

the ones with dots are very experimental..... I do not suggest anyone else try...

Sadly you will lose sleep then.   Some are just better then others at overclocking.  Granted you void warrenty doing it, so not all do it.

But you can have two working S3's.  It could be lots of reason's, but it is common for some to OC better then others.  That is why it is suggested doing it in steps not just jump up to a frequency someone else posted.

I don't like the use of "temperamental" it's all hard ware and science they don't have moods they have bad chip or brown caps that explode or resistors that swing wide in there tollance range or parts that get to hot and the resistance goes up so performance go down but just moody?  I've been OC'ing from back in the days of 600mhz amd's to the first 1ghz cpu......It's bothering me to see it boot and run at 500 +  only to have that speed disaper with no good reson......I'll be losing sleep till I understand what is occurring. 

Also if it's just a S3 and not a S3+ 430-440 is normal range I would say.   And it is true each has it's own personality and some are much better at OC then others.

nope some S3s just dont OC.. out of the 3 i have, 2 are temperamental.


i have one that will barely do 218.. it runs at 425-438 ghs, if i clock it to 225 or higher it actually goes slower.

i have one that wont go below 225 without putting x's in one of the chains.
it runs at 225 just fine with 453 ghs, but if i switch it to 218 it runs at 300-320 ghs and has x's

and the last one will clock to 237 with 0 hwe and runs 470 ghs.

I would love to see ur  vim /usr/lib/lua/luci/model/cbi/cgminer/cgminer.lua  file to make sure of my ##'s

I can only get burst of Oc's for 10-15 min's then the bottom drops out and it goes down to 200-360 range no good but still stable at 218 @ 430 GH/s

I'm missing something!