ANTMINER S3+ Discussion and Support Thread

[BitBlitz]

I ordered two Antminer S3+ units for delivery to Thailand. The only shipping option was UPS. Both units were shipped last Wednesday. They both came to Thailand on Friday but only one was delivered. Apparently, one unit was left on the plane and went on quite an odyssey. UPS didn't even apologize for their screw-up. So here is the journey one of the units took. For a journey that should have been about 1,733 Km the package traveled approximately 24,146 Km (15,004 miles). I am glad I finally got it today. There was gash that cut through the box but the inner foam protected the unit. Right now it is hashing and seems to be working per specs.

Bangkok, Thailand    11/10/2014    10:31 A.M.    Delivered
Bangkok, Thailand    11/10/2014    1:01 A.M.       Out For Delivery
Bangkok, Thailand    11/09/2014    10:02 P.M.    Import Scan
Bangkok, Thailand    11/09/2014    7:03 A.M.       Arrival Scan
Shenzhen, China    11/09/2014    5:19 A.M.       Departure Scan
Shenzhen, China    11/09/2014    1:55 A.M.       Arrival Scan
Mumbai, India       11/08/2014    6:27 P.M.       Departure Scan
Mumbai, India       11/08/2014    5:25 P.M.       Arrival Scan
Koeln, Germany    11/08/2014    4:23 A.M.       Departure Scan
Koeln, Germany    11/07/2014    8:14 P.M.       Arrival Scan
Mumbai, India       11/07/2014    4:17 P.M.       Departure Scan
Mumbai, India       11/07/2014    12:10 P.M.    Arrival Scan
Bangkok, Thailand    11/07/2014    8:52 A.M.       Departure Scan
Bangkok, Thailand    11/07/2014    6:06 A.M.       Arrival Scan
Shenzhen, China    11/07/2014    4:26 A.M.       Departure Scan
Shenzhen, China    11/07/2014    12:34 A.M.    Export Scan
Shenzhen, China    11/05/2014    11:15 P.M.    Arrival Scan
Shenzhen, China    11/05/2014    10:56 P.M.    Departure Scan
Shenzhen, China    11/05/2014    6:58 P.M.       Origin Scan
Shenzhen, China    11/05/2014    5:18 P.M.       Pickup Scan
Shenzhen, China    11/05/2014    1:31 A.M.       Order Processed: Ready for UPS

the good news is that UPS probably spent $50 of time and jet fuel to transport it all those extra trips

Yea. I kept mentioning to my brother how much extra fuel they are wasting taking it everywhere the plane went for the weekend.

Wow, and you can be sure they were handled like this at each airport: http://www.youtube.com/watch?v=YbNq2xdvU_g

[MissouriMiner]

Thanks for the very useful replies guys, now I have a question about frequency.  Looking at the datasheet for the BM1382 chip, I see a table for typical hash rate and power, where 225MHz is 0.528 W/GH, and 250MHz is 0.583 W/GH, and 275MHz jumps to 0.702 W/GH.  So, what's the sense in bumping the clock up, when the ratio gets worse on power consumption?

Wow.  Those numbers are not right at all.  The lowest I have ever gotten is .80 W/GH.  Bitmain advertises .78W/GH.  Below is my best number vs. advertised.  Most of mine got between .86 and .89.  With a high quality PSU running at less than 80% max current, the efficiency stays consistent (in my tests).   Some PSU advertise on the box their efficiency percentages.  I talked about doing a bigger study with various PSU's, but never got around to it. 

MHz   Avg Gh/s   Watts      Efficiency W/Gh    PSU Model
225   453            363         0.80                  1300W Rosewill Lightening, 80 Plus Gold
225   453            355         0.78                  Bitmain Advertises

[chinesebob]

Wow.  Those numbers are not right at all.  The lowest I have ever gotten is .80 W/GH.  Bitmain advertises .78W/GH.  Below is my best number vs. advertised.  Most of mine got between .86 and .89.  With a high quality PSU running at less than 80% max current, the efficiency stays consistent (in my tests).   Some PSU advertise on the box their efficiency percentages.  I talked about doing a bigger study with various PSU's, but never got around to it. 

MHz   Avg Gh/s   Watts      Efficiency W/Gh    PSU Model
225   453            363         0.80                  1300W Rosewill Lightening, 80 Plus Gold
225   453            355         0.78                  Bitmain Advertises

I guess the numbers in the datasheet are for the chip by itself, whereas your numbers are for the system as a whole

[MissouriMiner]

Wow.  Those numbers are not right at all.  The lowest I have ever gotten is .80 W/GH.  Bitmain advertises .78W/GH.  Below is my best number vs. advertised.  Most of mine got between .86 and .89.  With a high quality PSU running at less than 80% max current, the efficiency stays consistent (in my tests).   Some PSU advertise on the box their efficiency percentages.  I talked about doing a bigger study with various PSU's, but never got around to it. 

MHz   Avg Gh/s   Watts      Efficiency W/Gh    PSU Model
225   453            363         0.80                  1300W Rosewill Lightening, 80 Plus Gold
225   453            355         0.78                  Bitmain Advertises

I guess the numbers in the datasheet are for the chip by itself, whereas your numbers are for the system as a whole

Ah.  I see now.  That makes sense.   This link below is an old post of mine where I shared some stats.  You will see that on the better PSU, the efficiency stayed the same when increasing the Mhz.  But you have to consider the price difference on the PSU's.
https://asktom.cf/index.php?topic=671189.msg9236641#msg9236641

[Nite]

What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?

You should keep it between 50 and 60 C or less. My S3+ at stock speed runs between 40 and 50C in over 30C ambient temps. Over 70 C is bad for the hardware. Unless you disable it, the firmware will turn the miner off if either chain temp reaches 80 C.

thats a bit on the high side for stock, mine is at 453Ghz stock as well, one board is at 41c and other is at 35c

[jackbox]

What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?

You should keep it between 50 and 60 C or less. My S3+ at stock speed runs between 40 and 50C in over 30C ambient temps. Over 70 C is bad for the hardware. Unless you disable it, the firmware will turn the miner off if either chain temp reaches 80 C.

thats a bit on the high side for stock, mine is at 453Ghz stock as well, one board is at 41c and other is at 35c

Ambient room temp has a big affect. If aircon is on temps are much lower. Anything below 50 C is quite safe. Usually in mid 40s when no aircon is on. Room heats up to 32 C  with Antminer running and no aircon on.

[jackbox]

If anyone emails info@bitmaintech.com and requests a coupon they will give them as many as they want. No reason to pay for them. Just email them with bitmaintech id and which coupon you want and qty.

[Nite]

What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?

You should keep it between 50 and 60 C or less. My S3+ at stock speed runs between 40 and 50C in over 30C ambient temps. Over 70 C is bad for the hardware. Unless you disable it, the firmware will turn the miner off if either chain temp reaches 80 C.

thats a bit on the high side for stock, mine is at 453Ghz stock as well, one board is at 41c and other is at 35c

Ambient room temp has a big affect. If aircon is on temps are much lower. Anything below 50 C is quite safe. Usually in mid 40s when no aircon is on. Room heats up to 32 C  with Antminer running and no aircon on.

yea my Room is 76F (24c) right now and still only around the 35 - 40c range, will find out how it runs when summer hits next year

[sepehr]

I have the miner plugged in to the router directly.  I originally had it running on static IP 192.168.1.98.  Router setting is default 192.168.1.1.  I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware.  I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31.  Web interface works great on all three IPs but the thing just wont start hashing.  The Red LED stays red when all my other miners red LED go out once its connected to pool.  I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

yes, but he said it did not work, which is strange. maybe OP did not "save and apply"

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.

oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another.

Any clue to solve this?

I have the exact same issue and did everything but not succeeded!
Please help!

[jackbox]

I have the miner plugged in to the router directly.  I originally had it running on static IP 192.168.1.98.  Router setting is default 192.168.1.1.  I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware.  I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31.  Web interface works great on all three IPs but the thing just wont start hashing.  The Red LED stays red when all my other miners red LED go out once its connected to pool.  I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

yes, but he said it did not work, which is strange. maybe OP did not "save and apply"

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.

oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another.

Any clue to solve this?

I have the exact same issue and did everything but not succeeded!
Please help!

An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices.

[unkers]

Good day guys! I need your help .. my s3 + ceased to see one card ... it is now running at half power board ... cold .. that it is possible to do .. or have everything firmware me ... cut off the charge ... ((

[jackbox]

Good day guys! I need your help .. my s3 + ceased to see one card ... it is now running at half power board ... cold .. that it is possible to do .. or have everything firmware me ... cut off the charge ... ((

Mine did that once. Turning off the power supply, waiting a bit and then turning back on fixed it.

[unkers]

I tried, nothing changes? !!

[sepehr]

I have the miner plugged in to the router directly.  I originally had it running on static IP 192.168.1.98.  Router setting is default 192.168.1.1.  I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware.  I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31.  Web interface works great on all three IPs but the thing just wont start hashing.  The Red LED stays red when all my other miners red LED go out once its connected to pool.  I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

yes, but he said it did not work, which is strange. maybe OP did not "save and apply"

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.

oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another.

Any clue to solve this?

I have the exact same issue and did everything but not succeeded!
Please help!

An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices.

I have 26 S3's running on the same network all with static IP and same settings.

This S3 have problem and the problem exactly as above user:

The Red LED stays red when all my other miners red LED go out once its connected to pool.

And Not hashing at all. I have access to GUI but hashing is 0 and fans are working fast.

Any clue?

[sepehr]

I have the miner plugged in to the router directly.  I originally had it running on static IP 192.168.1.98.  Router setting is default 192.168.1.1.  I can see status through web browser on that IP and also on defalut IP 192.168.1.99 after I factory restore firmware.  I also can see it when I set the IP to DHCP and the router set IP to 192.168.1.31.  Web interface works great on all three IPs but the thing just wont start hashing.  The Red LED stays red when all my other miners red LED go out once its connected to pool.  I even did a ping test on openwrt.org diagnostic and is send 5 packets out but none received.

Log into the unit's web UI and change network to DHCP. Remember to apply the settings.
It may change it's address after this, but that is all you have to do.

yes, but he said it did not work, which is strange. maybe OP did not "save and apply"

You probably should have thought to tell OP to do that in the first place. The only strange thing that was stated is that the unit was hashing properly and then simply stopped, that is VERY strange.
I suspect OP got intoa panic, reflashed the firmware, changed to DHCP and did not apply before rebooting again (in a panic again ...?). The only reason I know of that an S3+ will refuse to start hashing is when it is on a static IP. I can not explain why that happens, but it does.

oh, well, he has enough info to figure it now. sometimes doing twice the same thing brings "them" to life for one mysterios reason or another.

Any clue to solve this?

I have the exact same issue and did everything but not succeeded!
Please help!

An S3 will hash on a static IP but the subnet must be the same. For example if the static IP of the S3 is 198.162.1.99 then the network it is on must be 198.162.1.xxx. Many new routers come set to .2, .3 or another subnet to avoid IP conflicts with other devices.

I have 26 S3's running on the same network all with static IP and same settings.

This S3 have problem and the problem exactly as above user:

The Red LED stays red when all my other miners red LED go out once its connected to pool.

And Not hashing at all. I have access to GUI but hashing is 0 and fans are working fast.

Any clue?

Also in diagnostics my S3 can ping outside networks!

[imagina]

Hello,

I have a new s3+ that i am strugling to configure the load balance settings in the miner's web page.

Once i activate the load balance profile and configure the miner like:

"80;stratum_url:3333",
"20;stratum_url:3333" and
"0;stratum_url:3333"

the miner does not stratum to work.

I have tried to flash different firmware versions and the output is always the same.

Is anyone else having the same problem?

Cheers

[hagbase]

Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.

[unkers]

himself a miner works, produces half the power ... a miner .. two boards in the menu there are two aysika .. I have not determined a capacity of 250 ... ((

[imagina]

Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.

I did.. I am now running with the Balanced profile with three pools, but the pool that is placed on 3rd place is not very stable, it goes from 0Ghs to 130Ghs max, most of the time the pool is reporting that worker with 0Ghs..

Shouldn't the load balance profile work as it should?

Is it a firmware/cgminer issue?

Thank you

[jackbox]

Did u try balance instead of load balance? I'm using load balance with 2 pools without quota, both get 50% shares/ Gh/s. No Problem at all, works even with 3 pools.

I did.. I am now running with the Balanced profile with three pools, but the pool that is placed on 3rd place is not very stable, it goes from 0Ghs to 130Ghs max, most of the time the pool is reporting that worker with 0Ghs..

Shouldn't the load balance profile work as it should?

Is it a firmware/cgminer issue?

Thank you

Did you try another stratum server? It could just be a flakey stratum. I tested out load balancing on mine the other day and it seemed to work pretty well with one stratum having a slower hash rate.