ANTMINER S3+ Discussion and Support Thread

[Atomar]

My B 4 should be here on Monday :-)

[1714616875]

1714616875

[1714616875]

1714616875

[1714616875]

1714616875

[Biodom]

Hey BitMain...

The price of BTC is BACK to $585+...OK...  

Could you adjust your S3's price back to 0.65-.66 BTC ...or lower...

ZiG

you are correct they should drop price.   but the sp30 double miss on gh and on power makes the s-3  the best item to buy.

I would feel happy if it drops to .66 or .65 , but they may raise it more.


 With diff doing 2  under 10 % jumps maybe 3 under 10%   they could move price to .69 and I think it will sell.

I am looking to buy 2 more I want to see it drop to .64  I will not buy until my 2 come on fri and test well.

I will also not buy more until I see how my b5 performs. All four of my b1 are great, one of b2 performs only at 427-428Gh at 212.5, chokes to 415-418 on 218.75 NO matter what I did (BTW, applying AS5 did not do anything good or bad for more than 24hr now). I think that S3 is more like S2, each machine is different and tinkering does not do you any good. You might get an initial pop, but then it all goes to where this particular miner "wants" to be as far as speed is concerned.
I still have a couple of 0.075 coupons, we shall see.

[mrpark]

Are people happy with their S3 units on p2pool?

If you're on p2pool, are you using the stock queue option (4096) or did you change it?

I use http://eligius.st its 0% and you can bring up your wallet address on the site to see what your total hash is.

[jonnybravo0311]

Are people happy with their S3 units on p2pool?

If you're on p2pool, are you using the stock queue option (4096) or did you change it?

I've got units both at stock 4096 and changed to 1.  I haven't noticed any differences in hash rates, although the hardware errors seem to be a bit lower on the units I set to queue of 1, but I need to change the stock units to 1 to see if the lower error rate is truly a result of the change or not.

[muzzyshop]

How to request refund? BTC
B2 still in China

[macgyver007]

This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?

[jonnybravo0311]

This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?

How did you reboot it?  Web UI, or ssh?  I see this whenever I reboot through ssh... or if I just turn off the PSU.  If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.

[windpath]

Are people happy with their S3 units on p2pool?

If you're on p2pool, are you using the stock queue option (4096) or did you change it?

I'm very happy with the performance of my S3s on p2pool so far, my second batch is arriving today and will pointed at p2pool without a doubt.

Its just a better pool

I have been testing the queue set to 1 on a single machine, after 21 hours the results are as follows:


queue=1 error rate:       0.00086971453%
queue=4096 error rate:  0.00180255332 %
 
It is worth noting that both of these are impressively low, I'll keep testing with a couple more machines, but I'm 99% confident queue =1 is the way to go.

[iglasses]

This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?

How did you reboot it?  Web UI, or ssh?  I see this whenever I reboot through ssh... or if I just turn off the PSU.  If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.

I just had one do this for the first time today.  I did a PSU power off reboot and when it came back up it said it was running for 45 minutes so even thought the 5sec hashrate is fine the average is in the toilet.

I hope Bitmain is working on a firmware update for these S3's...lots of little things like this could use to be fixed.

[mrpark]

Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.

[Biodom]

I did a PSU power off reboot and when it came back up it said it was running for 45 minutes so even thought the 5sec hashrate is fine the average is in the toilet.

I hope Bitmain is working on a firmware update for these S3's...lots of little things like this could use to be fixed.

obviously a bug, however, web gui reboot fixes it...Direct PSU reboot messes everything up for me too, so i either use web gui or "poweroff -d 3" command in ssh with 3 being a number of sec before the shutdown and could be different from 3. In the latter case, after disconnect, fans continue to run for 20 sec or so.

[hurricandave]

Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.

Bitmain uses the date the firmware version was created at the start of the file name.

[mrpark]

Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.

Bitmain uses the date the firmware version was created at the start of the file name.

Ok, I guess I can see that where you upload the firmware? I will check it next time I plug in another S3 batch 4. (still have a few to set up)

[squashpile]

Batch 4 in the house - Will update later
Point a few of these S3's to my P2Pool 

[mrpark]

Batch 4 in the house - Will update later
Point a few of these S3's to my P2Pool 

any advantage of P2Pool over eligius?

[Duce]

Are people happy with their S3 units on p2pool?

If you're on p2pool, are you using the stock queue option (4096) or did you change it?

I'm very happy with the performance of my S3s on p2pool so far, my second batch is arriving today and will pointed at p2pool without a doubt.

Its just a better pool

I have been testing the queue set to 1 on a single machine, after 21 hours the results are as follows:


queue=1 error rate:       0.00086971453%
queue=4096 error rate:  0.00180255332 %
 
It is worth noting that both of these are impressively low, I'll keep testing with a couple more machines, but I'm 99% confident queue =1 is the way to go.

I ran for 36 hours with a very low return (I know 3 days to level out) on P2P but I did get a share. The queue was set stock to 4096 (yes I changed it back to test more for those who have read this entire thread) then I changed it back to Queue=1 and within minuets my chart started going up and now starting day 3 from making the change it looks like it is going where it should be. Now could this have been luck/variance/coincidence, not sure some may say yes or just dumb luck. Take it for what it's worth but I made the change around 8 PM. What you do not see is the level remaining below 4.0mBTC for the first ~24 hours. There is also a very good P2P thread https://bitcointalk.org/index.php?topic=18313.9840

[BennyTheBall]

Question: Does this batch 4 come with the new firware? Anyone know which batch has what firmware? How can I tell which firmware my new B4 has on it? I flashed a few of them, but maybe its not smart enough to know it already has the latest firmware on it.

Go to "Status" "Kernel Log". The first line looks like this:[    0.000000] Linux version 3.10.12 (xxl@ubuntu) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #140 Mon Jul 21 17:27:04 CST 2014

The highlighted part is your firmware version. Look at the .bin file name. The date is encoded in the name and you should compare it with this.

[macgyver007]

This is a problem...on this particular boot its showing a time difference of 24 minutes which causes this result...Im sure I have seen as much as 8-9 hour difference between the uptimes
This miner was rebooted only 3 minutes yet the miner status page claims its been running 27 minutes which is impossible and the "hashrate" shows it...so how often is the cgminer process restarting behind the scenes or what is going on here BITMAIN?

How did you reboot it?  Web UI, or ssh?  I see this whenever I reboot through ssh... or if I just turn off the PSU.  If I reboot through the web UI, or if I use the poweroff command in ssh, everything comes back up properly.

I rebooted through the web interface reboot option...when I power off via PSU Im suspecting that is when the multiple hour time difference happens and that is when the times are reversed...the miner status page shows minutes and the main miner uptime claims to be hours...haven't tested that aspect enough...for the record when I first turn the machines on the first thing I also do is go in and reboot them through the UI..have done this since S1 days...so many issues so many miners so little time  

[philipma1957]

Are people happy with their S3 units on p2pool?

If you're on p2pool, are you using the stock queue option (4096) or did you change it?

I'm very happy with the performance of my S3s on p2pool so far, my second batch is arriving today and will pointed at p2pool without a doubt.

Its just a better pool

I have been testing the queue set to 1 on a single machine, after 21 hours the results are as follows:


queue=1 error rate:       0.00086971453%
queue=4096 error rate:  0.00180255332 %
 
It is worth noting that both of these are impressively low, I'll keep testing with a couple more machines, but I'm 99% confident queue =1 is the way to go.

do me a favor clock accepted shares for two days with 1 and for 2 days with  4096   use a diff of 256  test it on p2p  .  mine come today I will run them on btcguild and give my results

[fresca]

I'm a very very satisfied b1 customer.  Miners have been running without a hitch for almost two weeks now with no problem whatsoever.  To get them up and hashing took less effort than what I thought.  I still have the beeping from the original firmware and haven't flashed it yet.  But the beeps aren't too bad, and I don't want to take them offline while they are hashing so well.