Author

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

legendary
Activity: 3892
Merit: 4331
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.

Out of the first two S3, one beeps once in 20 min, another does not. It's just getting used to the workload, I figure  Smiley.
BTW, I also had a "beeper" S1 ant, with beeping disappearing after a couple of days.
It takes a bit longer for S3 to accept settings change in comparison with S1, but just a few sec more.
It also emits a loud beep to tell you-"I've got it-let's the hashing commence".
Interestingly, only a portion of heat is being released through fans judging by the intensity of air flow and heat of what comes out, with the rest dissipating probably from the metal covers, which are 3-5oC warmer than ambient air (33oC max with 28oC ambient).
I did not try to overclock them yet, with one hashing at 446Gh and another 436Gh, average 441Gh, right on the spot.
Fans do sound quiet, but oddly whiny sometimes despite the low rpm
The machine looks professional-will appeal to family mass market for sure if there will ever be one.
Wife's comment-"nice" while S1 was "it looks like a computer board"
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'

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.

Yes by MAC @ your router..

Well after 5 hours of testing all I have to say is BLAH!!  Overclocking even with 4 PCI-e connections does little.

218.75 Clock:

miner 1 / 444.95 @ Miner / 463.36 @ Pool
miner 2 / 427.78 @ Miner / 432.18 @ Pool
miner 3 / 443.52 @ Miner / 454.49 @ Pool
miner 4 / 410.05 @ Miner / 410.58 @ Pool  --- Indicates 1 chip as " - "
miner 5 / 427.41 @ Miner / 413.85 @ Pool

250 Clock:

miner 6 / 464.32 @ Miner / 479.65 @ Pool  --- Indicates 1 chip as " x "
miner 7 / 450.27 @ Miner / 417.84 @ Pool

will continue to mess with timeouts to see if anything works as for now not getting a stable 441 GH/s, but on a few. ;(

Hope B2 is better!




please try to underclock to 215.625

and to 206.25






the above codes were from my hand calculations, GH speeds added. 215.625 gives me 1100Gh and less than 1.1% error rate



https://bitcointalksearch.org/topic/m.6485048

so 206.25

and 215.625   were both developed by klondike_bar

        option 'freq_value'    '6206'  #215.625M
        option 'chip_freq'     '215.625'        
        option 'timeout'       '18'   maybe 17

        #option 'freq_value'    '5002'  #206.25M  
        #option 'chip_freq'     '206.25'          
        #option 'timeout'       '19'  maybe 20


these 2 can be tested
legendary
Activity: 1150
Merit: 1004
A few people have mentioned using their B1 S3's on p2pool. I thought that p2pool was being worked on by Bitmain but did not work yet.

I've watched this thread pretty religiously. Did I miss something and did Bitmain say that they've got p2pool working for b1 units?
newbie
Activity: 9
Merit: 0
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

Well, my Batch1s still are unshipped... ordered and paid June 30. Back then, July 10 was the date....

Well mine finally shipped

and are now sitting in customs exception waiting to clear - in China Grin


what was you blockchain time?
sr. member
Activity: 379
Merit: 250

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.

Yes by MAC @ your router..

Well after 5 hours of testing all I have to say is BLAH!!  Overclocking even with 4 PCI-e connections does little.

218.75 Clock:

miner 1 / 444.95 @ Miner / 463.36 @ Pool
miner 2 / 427.78 @ Miner / 432.18 @ Pool
miner 3 / 443.52 @ Miner / 454.49 @ Pool
miner 4 / 410.05 @ Miner / 410.58 @ Pool  --- Indicates 1 chip as " - "
miner 5 / 427.41 @ Miner / 413.85 @ Pool

250 Clock:

miner 6 / 464.32 @ Miner / 479.65 @ Pool  --- Indicates 1 chip as " x "
miner 7 / 450.27 @ Miner / 417.84 @ Pool

will continue to mess with timeouts to see if anything works as for now not getting a stable 441 GH/s, but on a few. ;(

Hope B2 is better!


sr. member
Activity: 434
Merit: 250
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

Well, my Batch1s still are unshipped... ordered and paid June 30. Back then, July 10 was the date....

Well mine finally shipped

and are now sitting in customs exception waiting to clear - in China Grin
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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.
Well, that didn't solve it on my side unfortunately.  Still random beeps.  That's going to get annoying quick...
legendary
Activity: 2338
Merit: 1124
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

Well, my Batch1s still are unshipped... ordered and paid June 30. Back then, July 10 was the date....
legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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.
sr. member
Activity: 379
Merit: 250
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.

legendary
Activity: 1344
Merit: 1024
Mine at Jonny's Pool
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).
legendary
Activity: 1050
Merit: 1001
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
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
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
hero member
Activity: 546
Merit: 500
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.
sr. member
Activity: 259
Merit: 250
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,

Quote
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  Roll Eyes
legendary
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
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.
hero member
Activity: 744
Merit: 514
gotta let a coin be a coin
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.
legendary
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
legendary
Activity: 966
Merit: 1003
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.
legendary
Activity: 1946
Merit: 1006
Bitcoin / Crypto mining Hardware.
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 Wink. It's covered by a shroud




Jump to: