Topic: Antminer S3 pool switching problem (Read 1709 times)
I don't see the purpose of using Nice and West at separate thresholds. The threshold is set at where I'd rather mine directly on another pool. But with my hash and choice of alts its worthwhile to mine solo, maybe I'll try that.
How would that setup roll to Nice/West? Unless solo pool goes down, the S3 wouldn't even consider Nice/West. Don't get me wrong, I commend you on throwing an S3 at solo mining in hopes of hitting the big payday, but I don't think it would ever bother going to your second or third choice pools.
do you realize you can make your pools
1)nicehash
2)westhash
3)btcguild
nicehash and westhash are separate but equal . they are the same company. use the same btc addy for payout.
set nicehash via the password at p= 0.0129
set westhash via the password at p =0.0127
then use btcguild
better yet use solo.ckpool.org and go solo as the third choice.
https://bitcointalksearch.org/topic/yh-solockpoolorg-1-fee-solo-mining-usade-251-blocks-solved-763510
I happen to use the solopool on top and I use lower thresholds on westhash and nicehash since they are less likely to be higher then the lowest buyer of hash.
1)nicehash
2)westhash
3)btcguild
nicehash and westhash are separate but equal . they are the same company. use the same btc addy for payout.
set nicehash via the password at p= 0.0129
set westhash via the password at p =0.0127
then use btcguild
better yet use solo.ckpool.org and go solo as the third choice.
https://bitcointalksearch.org/topic/yh-solockpoolorg-1-fee-solo-mining-usade-251-blocks-solved-763510
I happen to use the solopool on top and I use lower thresholds on westhash and nicehash since they are less likely to be higher then the lowest buyer of hash.
What pool are you using as 2nd? Also can you see that it's hashing in 2nd pool with your current setup?
The main WKC pool and the main NEOS pool are the ones that give me the problem all the time. BTCGuild, no problem at all. I can see that it's connected to the pool but not really hashing, and the hashrate indicator on the pool shows a hashrate <1GH. I have the miners split up on a lot of failover pools. When the Nicehash pay rate goes back above the threshold they go back there with no problems. Also if I just Save & Apply my pool settings without changing anything they go the the correct pools and hash normally.
What pool are you using as 2nd? Also can you see that it's hashing in 2nd pool with your current setup?
Hi all, sorry if this has already been asked and answered.
I run S3's on Nicehash, and when the pay goes beneath my chosen pay threshhold they switch to the first failover pool, but they don't always hash. Rather, they hash at a very low speed, under 1 GH. This always happens on some pools and never happens on others, so I suspect it might be pool related. Firmware is 3.10.12
Anybody else have this problem, and is there a fix?
I run S3's on Nicehash, and when the pay goes beneath my chosen pay threshhold they switch to the first failover pool, but they don't always hash. Rather, they hash at a very low speed, under 1 GH. This always happens on some pools and never happens on others, so I suspect it might be pool related. Firmware is 3.10.12
Anybody else have this problem, and is there a fix?
Jump to: