ANTMINER S3+ Discussion and Support Thread

[Mr.Beetr00t]

Question about PSU:
Bought a cheaper 900w PSU by FSP Power with just 4 PCI-E connectors. (6+2 type connectors)
Do you guys think this type of PSU would be sufficient to run the 2 devices smoothly or is it more reasonable to throw it out the window and spend another $300 to get a Corsair AX1200i?

[whonesta]

Happily hashing away at ~500GH/s


I am posting setup / support / oc tidbits in this thread https://bitcointalk.org/index.php?topic=699064.0

These numbers are Great. I am not seeing ANY where near that with mine. I am giving it a few more minutes before passing judgement but so far very disappointed.

I am testing across a few pools so..  time will tell..  

I have only been able to get upto 225 with 2 PCI-e cables without chips getting crazy, anything more needs 4 PCI-e connections.

[bvall]

Happily hashing away at ~500GH/s
https://i.imgur.com/eIh0Uyh.jpg

I am posting setup / support / oc tidbits in this thread https://bitcointalk.org/index.php?topic=699064.0

!! dont play with me, that looks awesome considering what I have been seeing itt

[jonnybravo0311]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

[whonesta]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

Same experience with Eligius.

While GHash, BTCGuld both get 500+.. Looks like they run to spec, but P2Pool is 14-15% less at the moment

[xstr8guy]

I was order #8 in batch 1. Received all 4 S3's today.

Did some power measurements for those who might be curious. Kill-a-watt is showing power draw at the wall for two S3's as they come out of the box.

where can i buy that device for showing power draw?

Pay with BTC!
http://www.newegg.com/Product/Product.aspx?Item=N82E16882715001

[bitfor8888]

For the coupon offered, any one know whether it has a time limited. If not, I may opt that.  All my bitocoin is used to buy their machines so far and hence it is better.  However, if there is a time limit, not sure how long to get my 1.45 bitcoin to get the next batch, may get the refund instead.

Any one got experience?

there is a time limit... i think it was the 22nd from memory

you can choose refund before then or it will default to coupon after cutoff

also, one coupon per purchase

Thanks.  Is the coupon itself has time limit?

[xstr8guy]

still waiting on my B1 orders too.. this is brutal, hopefully we get a coupon for the delay

What delay? They said they were shipping by the 20th. Last time I checked it was only the 17th.

[goxed]

Packaging of the S3 is the same great foam packaging as the S1s.



The miner now has push-pull fan config, using Bitmain branded fans . It's covered by a shroud

[hurricandave]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

[goxed]

[faetos]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

The config now allows you to turn it off if it is really annoying.

[goxed]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

The config now allows you to turn it off if it is really annoying.

[hobbymd]

still waiting on my B1 orders too.. this is brutal, hopefully we get a coupon for the delay

What delay? They said they were shipping by the 20th. Last time I checked it was only the 17th.

Last time I checked BITMAIN said,

on: July 14, 2014, 02:08:30 AM

Shipping schedule updated:

Batch 1: The shipping will be finished in 14th and 17th.
Batch 2: It will be shipping out between 18th and 19th.
Batch 3: It will be shipping out between 19th and 22nd.

so when was the last time you checked again  

[sjc1490]

Can one of you lucky bastards who've received an S3 already please supply the part number for the buck regulator component? It's not the big grey square, that's a coil - instead it'll be a small IC right beside and will have a code (or codes) written in ridiculously small letters which indicate the part and manufacturer.

Trying to get a head start on sourcing a suitable replacement with more headroom.

Check out https://bitcointalk.org/index.php?topic=656461.new#new I repeated your request there.

[philipma1957]

Question about PSU:
Bought a cheaper 900w PSU by FSP Power with just 4 PCI-E connectors. (6+2 type connectors)
Do you guys think this type of PSU would be sufficient to run the 2 devices smoothly or is it more reasonable to throw it out the window and spend another $300 to get a Corsair AX1200i?

the evga `1300'   will do the trick


http://www.rakuten.com/prod/evga-supernova-1300-g2-1300w-power-supply-110-v-ac-220-v-ac-input/249973555.html


use code shopowner   10% off for later      195 usd


 it will do the 2 no problems most likely it should run 3

[-droid-]

still waiting on my B1 orders too.. this is brutal, hopefully we get a coupon for the delay

What delay? They said they were shipping by the 20th. Last time I checked it was only the 17th.

They were quoted here saying batch 1 shipped 14th thru 17th and batch 2 after, look it up

[jonnybravo0311]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

The config now allows you to turn it off if it is really annoying.

I did turn it off, yet it still will randomly just let out a beep.  It hashes away happily...then BEEP...still hashing...I think I'll beep now...

It happens at all clock speeds on every pool I've configured (my local p2pool node, another p2pool node, Eligius, BTCGuild, and yes, the pool that shall not be named).

[whonesta]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

The config now allows you to turn it off if it is really annoying.

I did turn it off, yet it still will randomly just let out a beep.  It hashes away happily...then BEEP...still hashing...I think I'll beep now...

It happens at all clock speeds on every pool I've configured (my local p2pool node, another p2pool node, Eligius, BTCGuild, and yes, the pool that shall not be named).

My miners were doing the same random beep as you describe, I setup the dchp server to fix an ip for each and the beeping stopped. Too many iDevices on the network seemed to cause too much conflict for temp. leases.

[jonnybravo0311]

General questions about the S3 now that mine have been hashing for a few hours...

1) Why in the name of all that's holy does it randomly beep?  Every now and then it just goes "BEEEEEP!" It's not like it's rebooting... it just decides to let everyone know, "Hey, I'm here!  Pay attention to me!"
2) I know the "o" in the miner status means "OK" and that "x" means "error".  What does "-" mean?

General comments:

1) At stock clocks it hashes almost exactly to spec on p2pool (my local node).  Initially it was around 450GH/s, but after settling down and going for a few hours now, it's about 439GH/s.
2) Overclocking it has far less effect on p2pool than on another pool.  For example, at 250, I get about 455GH/s on p2pool.  I get 500GH/s elsewhere with the same settings.

The beep is internet connection lost or failed to get work. It will retry to get work or listen for the internet connection up to a point. If it keeps hashing then its doing what its supposed too.

The config now allows you to turn it off if it is really annoying.

I did turn it off, yet it still will randomly just let out a beep.  It hashes away happily...then BEEP...still hashing...I think I'll beep now...

It happens at all clock speeds on every pool I've configured (my local p2pool node, another p2pool node, Eligius, BTCGuild, and yes, the pool that shall not be named).

My miners were doing the same random beep as you describe, I setup the dchp server to fix an ip for each and the beeping stopped. Too many iDevices on the network seemed to cause too much conflict for temp. leases.

When you setup the fixed address, did you do it at your router by mac address, or on the S3?

EDIT: Never mind... I re-read what you wrote.  Since you included the comment about setting up the DHCP server, you obviously didn't just put a static IP in the S3.  Duh... sorry about the stupid question back at you.