ANTMINER S3+ Discussion and Support Thread

[faetos]

Overnight run   so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

[1714621583]

1714621583

[1714621583]

1714621583

[sjc1490]

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

Here is Duce's post: https://bitcointalk.org/index.php?topic=671189.msg8029279#msg8029279

Keep in mind if you aren't comfortable with ssh or Linux I would proceed with caution. You can screw up your unit if you make a mistake.

[smracer]

I put a six gauge wire on a 70 amp circuit breaker, from my main 200 amp fuse box to a spare room, how many s3's will I be able to run on that circuit, air conditioner is on a separate 20 amp breaker.


thanks in advance

70amp double pole?  You can pull 56 constant amps through each wire at 120V each.

You could run about 34-36 S3's off that depending on how good your PSU's are.

It will get warm.

[Biodom]

Overnight run   so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

Ok, I ssh into miner, enter the code above, hit return/enter
then (without exiting ssh?) go to web gui and just restart the miner by "save and apply" in configuration (although change was made by sshing)
right?
you cannot just use :wq or other command while still in ssh mode (after you entered the code string)?

[grn]

I put a six gauge wire on a 70 amp circuit breaker, from my main 200 amp fuse box to a spare room, how many s3's will I be able to run on that circuit, air conditioner is on a separate 20 amp breaker.


thanks in advance

70amp double pole?  You can pull 56 constant amps through each wire at 120V each.

You could run about 34-36 S3's off that depending on how good your PSU's are.

It will get warm.

Stop right now. Call an electrician and get him/her to install a sub panel, tell the electrician your power needs. Do this before you burn your house down and void your insurance

edit: get permits and have it all inspected

[Lowell904]

Overnight run   so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

Ok, I ssh into miner, enter the code above, hit return/enter
then (without exiting ssh?) go to web gui and just restart the miner by "save and apply" in configuration (although change was made by sshing)
right?
you cannot just use :wq or other command while still in ssh mode (after you entered the code string)?

Thanks guys. I think I have it now. Didn't realize that I had to save the settings in the gui plus I was missing part of the code.

[philipma1957]

I put a six gauge wire on a 70 amp circuit breaker, from my main 200 amp fuse box to a spare room, how many s3's will I be able to run on that circuit, air conditioner is on a separate 20 amp breaker.


thanks in advance

70amp double pole?  You can pull 56 constant amps through each wire at 120V each.

You could run about 34-36 S3's off that depending on how good your PSU's are.

It will get warm.

Stop right now. Call an electrician and get him/her to install a sub panel, tell the electrician your power needs. Do this before you burn your house down and void your insurance

edit: get permits and have it all inspected

in New Jersey,  USA

you don't need an electrician if you own the home and you live in it.  You do need a permit and an inspection.

[faetos]

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

Ok, I ssh into miner, enter the code above, hit return/enter
then (without exiting ssh?) go to web gui and just restart the miner by "save and apply" in configuration (although change was made by sshing)
right?
you cannot just use :wq or other command while still in ssh mode (after you entered the code string)?

sed is basically doing what vi does.
1. SSH to miner
2. enter this

Code:

 sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

and press enter
3. exit SSH (CTRL-D) or exit
4. go do the web admin thing

Duce came up with the idea on making the changes. His guide here: https://bitcointalk.org/index.php?topic=671189.msg8029279#msg8029279 goes the vi route. sed/vi accomplish the same task. We're just showing you guys different ways of doing it.

The reason I used sed in my example is that I know that there is only one value `--queue 4096"` that will get changed and it's less daunting than vi.

[Biodom]

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

Ok, I ssh into miner, enter the code above, hit return/enter
then (without exiting ssh?) go to web gui and just restart the miner by "save and apply" in configuration (although change was made by sshing)
right?
you cannot just use :wq or other command while still in ssh mode (after you entered the code string)?

sed is basically doing what vi does.
1. SSH to miner
2. enter this

Code:

 sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

and press enter
3. exit SSH (CTRL-D) or exit
4. go do the web admin thing

Duce came up with the idea on making the changes. His guide here: https://bitcointalk.org/index.php?topic=671189.msg8029279#msg8029279 goes the vi route. sed/vi accomplish the same task. We're just showing you guys different ways of doing it.

The reason I used sed in my example is that I know that there is only one value `--queue 4096"` that will get changed and it's less daunting than vi.

Great, thanks...not a coder, but I think I got it... big thanks to Duce and you.

[faetos]

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I see that your discards are very low. Did you change any other settings besides the frequency when you OCed?

I am sure he did the cgminer parameter changes as many of us did, go back a couple of pages and read through the previous posts.

I have read this entire thread over the last couple of weeks and I have been trying. What do I have to type into putty to access the parameter that need changing?

We've covered this in depth today. The thread is messy, but this one liner will change what you need once you've SSHed onto your miner:

Code:

sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

Go restart cgminer in the web interface by going to miner configuration and hitting save and apply. That will restart cgminer with the new config above.

Ok, I ssh into miner, enter the code above, hit return/enter
then (without exiting ssh?) go to web gui and just restart the miner by "save and apply" in configuration (although change was made by sshing)
right?
you cannot just use :wq or other command while still in ssh mode (after you entered the code string)?

sed is basically doing what vi does.
1. SSH to miner
2. enter this

Code:

 sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' /etc/init.d/cgminer

and press enter
3. exit SSH (CTRL-D) or exit
4. go do the web admin thing

Duce came up with the idea on making the changes. His guide here: https://bitcointalk.org/index.php?topic=671189.msg8029279#msg8029279 goes the vi route. sed/vi accomplish the same task. We're just showing you guys different ways of doing it.

The reason I used sed in my example is that I know that there is only one value `--queue 4096"` that will get changed and it's less daunting than vi.

Great, thanks...not a coder, but I think I got it... big thanks to Duce and you.

Always willing to help - Duce deserves the credit

[WheresWaldo]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.
***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

Thanks for this post ! Going to try this on one of my units and see how it works out.

This was default on the new firmware:

PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"

I tried it on one by adding the --scan-time 1 --expiry 1 flags, but didn't see any difference in discards or load. Maybe some of you will have better luck.

Did you change the Queue to 0?

that I did not do - misread what you wrote. YES!! Just changed it and am seeing really good numbers. Discards are negligible now - 20 accepts and 3 discards. Load dropped from high 2s to under 2. AWESOME!!!!! You rock!

Since I've never SSH one of these, I don't want to risk bricking it.

If this fix turns out to be solid though, I hope Bitmain will include it in the next firmware release.

Or maybe I'll learn to SSH. On a side note. Does anyone know if you can get a better GHS/watt ratio by under-clocking the S1?

I'll tell you how to do it, but not going to go into every detail (how to SSH, sed, etc). Not responsible for you f'ing your stuff up.

1. SSH into the miner
2. cd /etc/init.d
3. cp cgminer cgminer.bak (in case you really muck it up, cgminer.bak will be your backup)
4. Enter this in the terminal:  sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' cgminer
5. press enter
6. go to the web interface of the miner - Status > Miner Configuration > Save & Apply  - this will restart cgminer with the new settings
7. go tip Duce for figuring this out for us

Duce, where's your tip jar? I owe you.

This is what you're changing:

Original --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096"
   
New & Improved --> PARAMS="$AOPTIONS $POOL1 $POOL2 $POOL3 $_pb $_ow $_bec --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 0 --scan-time 1 --expiry 1"

//S1 undervolt guide - https://bitcointalk.org/index.php?topic=526060.msg5838713#msg5838713

I'm attempting this mod, but when I enter sed -i 's/--queue 4096"/--queue 0 --scan-time 1 --expiry 1"/g' cgminer into putty, I get "no such file or directory". Does anyone know what I am doing wrong, I'm afraid to go much further.

this guide is better https://bitcointalk.org/index.php?topic=671189.msg8040869#msg8040869

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Did you mod this machine?
Looks awesome

I did not! set it to 250 frequency and let it run.


I am surprised at the low HW errors, problem is, just like shares, is the HW need to be multiplied by any value? or is it 100 HW errors at 256diff then 256,000 HW errors?
Things are difficult without the cgminer software window open 

Overnight run  so far so good...

~450watts for ~500gh/s

I think the massive HW spike is from internet outtage, it was at 40HW very early in the morning. Who knows. Either way it's minimal compared to 22,000 shares at 256 diff ( ~5mil shares )

Do you have any special cooling?

stock, running it in a 26C ambient with no additional airflow anywhere

[R4v37]

[grn]

I put a six gauge wire on a 70 amp circuit breaker, from my main 200 amp fuse box to a spare room, how many s3's will I be able to run on that circuit, air conditioner is on a separate 20 amp breaker.


thanks in advance

70amp double pole?  You can pull 56 constant amps through each wire at 120V each.

You could run about 34-36 S3's off that depending on how good your PSU's are.

It will get warm.

Stop right now. Call an electrician and get him/her to install a sub panel, tell the electrician your power needs. Do this before you burn your house down and void your insurance

edit: get permits and have it all inspected

in New Jersey,  USA

you don't need an electrician if you own the home and you live in it.  You do need a permit and an inspection.

Thats true in most US and Canadian jurasdictions. Still Call an electrician

[Lowell904]

Nice. Please let us know if you see improvements.

[-ck]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.

***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results.
  
SSH in then:

Code:

vim /etc/init.d/cgminer
--scan-time 1 --expiry 1

Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation.

***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT****

Please stop telling people  to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though.

[ZiG]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.

***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results.
  
SSH in then:

Code:

vim /etc/init.d/cgminer
--scan-time 1 --expiry 1

Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation.

***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT****

Please stop telling people  to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though.

What is your recommendation(s), Boss...

ZiG

[R4v37]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.

***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results.
  
SSH in then:

Code:

vim /etc/init.d/cgminer
--scan-time 1 --expiry 1

Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation.

***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT****

Please stop telling people  to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though.

i agree with this boss  

without modifying anything...
tested at Ghash, the discarded will be 10times of accepted              <<best share will be a big 0
tested at Eligius, the Discarded will be as low as 0.01 x accepted      <<it'll showing ur best shares
tested at P2pool, same result as eligius..                                                         <<same as eligius

so... dont pay any attention to the "discarded", i dont know why, but maybe because of the pool that the "discarded" is pretty high at our miner

[Lowell904]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.

***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results.
  
SSH in then:

Code:

vim /etc/init.d/cgminer
--scan-time 1 --expiry 1

Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation.

***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT****

Please stop telling people  to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though.

I was having other issues before this mod like wrong hash rates at the gui and more HW errors than I would have liked. While load balancing I was getting a lot of discards at the pool I was using. Maybe it doesn't make much difference, but after this mod things look good at the pools, discards and HW look great, but hash rates seem way off still. I think the firmware is buggy and could be improved.

Edit: hash rates look good now on failover. Testing load-balancing now. Results = not hashing well at the pools. sticking to failover until we figure this out.

How should we revert back if need be, or what would be ideal parameters. I'm hoping that I could always just re-flash the firmware if need be.

[WheresWaldo]

Nice. Please let us know if you see improvements.

He put heatsinks on the chokes, there really isn't any performance to gain by doing this.
Hopefully those have good thermal adhesive and dont fall off and short his board to kill his unit.
Would be more beneficial to have heatsinks on the actual small chip above the chokes. Either way, none of this should affect hashrate but may increase the longevity of the unit.

[Duce]

I was able to get the discarded amount lowered as well as the load. I changed the queue to 0 from 4096 and added --scan-time 1 --expiry 1 to the cgminer file.

***IF YOU ARE NOT SURE WHAT THIS MEANS DO NOT TRY AS YOU WILL BRICK YOUR UNIT***

This is the first attempt, not sure if 0 is the optimal queue value for all pools but if you are a P2P miner you may want to try this out. I use a smaller pool and my numbers have gone up. This is along the same tune you could do for an S1 but a far cry from what we did in the GPU days. I have another unit running at a lower speed but have the same results.
  
SSH in then:

Code:

vim /etc/init.d/cgminer
--scan-time 1 --expiry 1

Find line 75 PARAMS...at the end change --queue 0 and add --scan-time 1 --expiry 1 before the quotation.

***DO NOT TRY THIS UNLESS YOU FULLY UNDERSTAND AS YOU WILL BRICK YOUR UNIT****

Please stop telling people  to do anything but change the queue. Artificially lowering the discarded value serves no purpose whatsoever. Decreasing scan time and expiry are for the dark ages of CPU mining - paying any attention to the "discarded work" value is completely pointless and actually harmful. The only thing here that's making a difference to CPU load is decreasing the queue which they have set far too high by default. Please do not decrease it below 1 though.

Perfect so the queue should be set to 1.
For the P2P folks, scan time and expiry settings will not help them as there were no settings included? (yes/no)

I truly appreciate and respect your inputs both positive and negative.