ANTMINER S3+ Discussion and Support Thread

[RealMalatesta]

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....

[jonnybravo0311]

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...

[jimrome]

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

[whonesta]

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!

[maxweldrr]

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

what was you blockchain time?

[edonkey]

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?

[philipma1957]

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://bitcointalk.org/index.php?topic=589429.msg6485048#msg6485048

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

[Biodom]

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  .
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"

[smiti444]

nice miner!

[whonesta]

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://bitcointalk.org/index.php?topic=589429.msg6485048#msg6485048

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

That is a NEGATIVE on both clocks, chips would not run.

[philipma1957]

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://bitcointalk.org/index.php?topic=589429.msg6485048#msg6485048

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

That is a NEGATIVE on both clocks, chips would not run.

thanks for trying much appreciated

[Meech]

The S1's beeped if they lost connection to the pool or internet, must be an ip conflict like discussed earlier.

[Lowell904]

Anyone get their 7.7% refund yet?

[whonesta]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

[Biodom]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

Can't OC to 225mhz as well?

[whonesta]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

Can't OC to 225mhz as well?

225mhz was not very stable ton of HW errors

250mhz is a mixed bag as well, I have one that has low HW errors another with really high #'s. MAX sustained speed @ Miner = 470GH/s @ Pool = 464GH/s

Both of the above settings required 4 PCI-e connections to be "stable".

GOOD NEWS...  250mhz - 470GH/s - 358W

[philipma1957]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

Can't OC to 225mhz as well?

225mhz was not very stable ton of HW errors

250mhz is a mixed bag as well, I have one that has low HW errors another with really high #'s. MAX sustained speed @ Miner = 470GH/s @ Pool = 464GH/s

Both of the above settings required 4 PCI-e connections to be "stable".

GOOD NEWS...  250mhz - 470GH/s - 358W

what psu did you use to get that set of numbers? it comes to .76 watts a gh!

[whonesta]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

Can't OC to 225mhz as well?

225mhz was not very stable ton of HW errors

250mhz is a mixed bag as well, I have one that has low HW errors another with really high #'s. MAX sustained speed @ Miner = 470GH/s @ Pool = 464GH/s

Both of the above settings required 4 PCI-e connections to be "stable".

GOOD NEWS...  250mhz - 470GH/s - 358W

what psu did you use to get that set of numbers? it comes to .76 watts a gh!

I have a single S3 powered by the enermax 1000w that I took out of the S2. Using 4 PCI-e connections Kill-a-watt reads 357W

[HerbPean]

I got two miners, one looks like to handle both 237.5 and 250 quite well.

The other one ... not so much...

[philipma1957]

Anyone get their 7.7% refund yet?

Nope and these miners are not running anywhere near -7.7%..  more like -14%

Hopefully there is a FW update soon.

Can't OC to 225mhz as well?

225mhz was not very stable ton of HW errors

250mhz is a mixed bag as well, I have one that has low HW errors another with really high #'s. MAX sustained speed @ Miner = 470GH/s @ Pool = 464GH/s

Both of the above settings required 4 PCI-e connections to be "stable".

GOOD NEWS...  250mhz - 470GH/s - 358W

what psu did you use to get that set of numbers? it comes to .76 watts a gh!

I have a single S3 powered by the enermax 1000w that I took out of the S2. Using 4 PCI-e connections Kill-a-watt reads 357W

good news. I had one of the enermaxes and the seasonic plats are better for power savings

 i have some plat 750 seasonics .  i am thinking maybe 340 watts for 470gh  that would be  .72 watts at the plug!