Topic: ANTMINER S3+ Discussion and Support Thread - page 124. (Read 710164 times)
Thanks for the very useful replies guys, now I have a question about frequency. Looking at the datasheet for the BM1382 chip, I see a table for typical hash rate and power, where 225MHz is 0.528 W/GH, and 250MHz is 0.583 W/GH, and 275MHz jumps to 0.702 W/GH. So, what's the sense in bumping the clock up, when the ratio gets worse on power consumption?
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
80℃
That's the thermal shutdown temp. Realistically, you should have 40-50c ideally, but probably won't see any real problems in error rate until over 60c
Do you know or just think?
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
You should keep it between 50 and 60 C or less. My S3+ at stock speed runs between 40 and 50C in over 30C ambient temps. Over 70 C is bad for the hardware. Unless you disable it, the firmware will turn the miner off either chain temp reaches 80 C.
If you stop function - Stop running when temprerature is over 80℃ - then you need to restart with PSU
All depends on the frequency. Miner can work without errors over 80℃ width lower frequency.
frequency 218.75
Antminer C1 , 74-77 ℃ . Noo x or - , 0 hardware errors
proof http://www.perearstike.ee/avatar/C1.jpg
during the summer mine hovered around 60 and didn't see any errors or problems. now that its winter they are running about 40 with the fans barely moving lol
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
80℃
That's the thermal shutdown temp. Realistically, you should have 40-50c ideally, but probably won't see any real problems in error rate until over 60c
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
You should keep it between 50 and 60 C or less. My S3+ at stock speed runs between 40 and 50C in over 30C ambient temps. Over 70 C is bad for the hardware. Unless you disable it, the firmware will turn the miner off if either chain temp reaches 80 C.
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
80℃
What is the maximum temperature an Antminer S3 ASIC can run at without degrading the hardware?
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues...
That they do. I was speaking more of %100 stand alone run your own wallet in server mode and mine mine mine.
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
if you really want to run solo, just use a solo pool like bitsoloMy miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
I see, no cgminer is only running on the antminers and bitcoind is running on a xeon based desktop. I will definitely check the "solo" pool. Thanks.
so: antminer-->cgminer <-- local network --> bitcoind<--desktop.
so: antminer-->cgminer <-- local network --> bitcoind<--desktop.
Maybe you're missing the http:// part on the -o parm?
From the readme.txt in cgminer:
Code:
cgminer -o http://localhost:8332 -u username -p password --btc-address 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ
Note the http:// is mandatory for solo mining.
M
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
The way you describe this, it sounds like you are running cgminer somewhere outside of your Ants. I'm pretty sure that's not going to work for you.
Try editing the cgminer config inside the Ant to have the solo mining options to point it to your Bitcoin instance:
cgminer -o http://
Also, CK (author of cgminer) has a public "solo mining pool" up.. if you don't mind the 0.5% fee:
https://bitcointalksearch.org/topic/yh-solockpoolorg-2-fee-solo-mining-usade-255-blocks-solved-763510
M
I see, no cgminer is only running on the antminers and bitcoind is running on a xeon based desktop. I will definitely check the "solo" pool. Thanks.
so: antminer-->cgminer <-- local network --> bitcoind<--desktop.
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
The way you describe this, it sounds like you are running cgminer somewhere outside of your Ants. I'm pretty sure that's not going to work for you.
Try editing the cgminer config inside the Ant to have the solo mining options to point it to your Bitcoin instance:
cgminer -o http://
Also, CK (author of cgminer) has a public "solo mining pool" up.. if you don't mind the 0.5% fee:
https://bitcointalksearch.org/topic/yh-solockpoolorg-2-fee-solo-mining-usade-255-blocks-solved-763510
M
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues...
I may give p2pool a try, I have more than one machine, so I can dedicate one to serving upa pool if I need to. As for antminers being "hopeless", the reason that I am trying this is I have seen my machines Find two blocks during the last four months, for which the pool I was in gave me diddly squat. Not that I have any thing against the pool, it is a great service, but obviously if I only find on more block the rest of my life (well antminer's life) I will be soooo much better off.
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now:
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
Do you have a firewall running on the system running bitcoind? I have mine on a Linux host and had to add an iptables entry. And I added listen=1 to bitcoin.conf. I've tried solo mining with and S3 (and default cgminer code) and it works fine.
yes, this is a linux machine but it is on my local network and the antminers are also on the same network, all are behind the same external firewall.
sudo iptables --list
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
So, my ip_table is empty, no rules.
Tried -listen=1 but getting the same behaviour. Thanks for the suggestion.
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
They run great on p2pool, have 8 S3's and a few S1's running for a while with 0 issues...
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
I have been involved in a few of the threads related to this topic. Solo mining with an Antminer is essentially hopeless. The only way to get it to run is to setup your own pool and even that is a freaking hassle far beyond what is reasonable or worthwhile for the average person.
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now:
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
Do you have a firewall running on the system running bitcoind? I have mine on a Linux host and had to add an iptables entry. And I added listen=1 to bitcoin.conf. I've tried solo mining with and S3 (and default cgminer code) and it works fine.
Thanks for the suggestion, I failed to note I also have a bitcoin.conf file that contains that line. Adding it to the command line, now:
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
bitcoind -datadir=/home/develop/utility/sophie/exec/.bitcoin -rpcuser=antminer -rpcpassword=yd39628 -rpcallowip=192.168.0.* -blocknotify=%s -alertnotify=%s
does not change the failure. cgminer still quits, actually it appears to start, restart one or two times, then quit for good.
Starting Nmap 6.46 ( http://nmap.org ) at 2014-11-20 12:52 PST
Nmap scan report for 192.168.0.2
Host is up (0.0000050s latency).
Not shown: 9997 closed ports
PORT STATE SERVICE
22/tcp open ssh
8200/tcp open trivnet1
8332/tcp open unknown
8333/tcp open bitcoin
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
I'm pretty sure Bitcoin is not capable of providing work fast enough to any of the recent ASICs. Furthermore, I'm pretty sure Bitcoin only supports the "getwork" protocol, not stratum. So essentially your S3 is starving for work.
I think, but I'm not sure, that there's a way to run cgminer as a "proxy" that your S3 can point to for work. cgminer takes care of converting the getwork data from Bitcoin to stratum for your S3 to use. I don't think you should try to be using cgminer to mine against your S3 as you have it written.
M
Problem with antminer s3+ solo.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O: --verbose --btc-address 1D7CFcY3gYMgNrns6ttRmomyGTLNzZ6XRA --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/.bitcoin -rpcuser= -rpcpassword= -blocknotify=%s -alertnotify=%s
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
My miners work fine for a pool. But when I try to run solo I get either a very, very slow hash rate and super high error rate(s), or the miners may also refuse to connect to the machine running bitcoin-qt/bitcoind and also may incorrectly report connections as being alive or dead.
I have tried upgrading cgminer to the most recent version, to no avail. Often, cgminer quits after a few minutes.
here is my cgminer command line (<> indicate substitutions to protect the innocent):
--bitmain-options 115200:32:8:18:225:0882 -o http://192.168.0.2:8332 -O
here is my bitcoin-qt/bitcoind command line:
-datadir=/home/
The verbose flag did not seem to give any more info, I can find an open port :8332 on the bitcoind machine and netstat will report "ESTABLISHED" then "CLOSE_WAIT".
Any suggestions on how to debug the rpc connection or cgminer would be greatly appreciated. I may have no hair left soon.
Looks like your missing --rpcallowip=
Jump to: