Unofficial Spondoolies SP20 thread

[Xian01]

Just got an SP20 in from EBay, and looking forward to tinkering with this one, running it "open air", without the stock fan, and a bunch of quieter fans pointing at it.

Fun weekend project ! *crosses fingers*

[Digitalmocking]

I am wondering if it would be possible to run an SP-20 with a single CX-750 with lowered voltage settings any thoughts what the settings would be or if it's feasible?

Easily.

I run two SP20s off of a single EVGA 1300G2 and get around 1.2GH/s each from them.

.63 volts to start
.661 max
units 1/3 160W max
units 2/4 180W max
Auto fan

[Biodom]

I am wondering if it would be possible to run an SP-20 with a single CX-750 with lowered voltage settings any thoughts what the settings would be or if it's feasible?

Easily.

I run two SP20s off of a single EVGA 1300G2 and get around 1.2GH/s each from them.

.63 volts to start
.661 max
units 1/3 160W max
units 2/4 180W max
Auto fan

well, it means that you are using up to 1360W on a 1300W PSU (or 1455-1496W at the wall).
This is probably OK, but I try to keep my power below 1420-1440W (on one 110-120V/15A circuit), also running two on one circuit.

[Digitalmocking]

I am wondering if it would be possible to run an SP-20 with a single CX-750 with lowered voltage settings any thoughts what the settings would be or if it's feasible?

Easily.

I run two SP20s off of a single EVGA 1300G2 and get around 1.2GH/s each from them.

.63 volts to start
.661 max
units 1/3 160W max
units 2/4 180W max
Auto fan

well, it means that you are using up to 1360W on a 1300W PSU (or 1455-1496W at the wall).
This is probably OK, but I try to keep my power below 1420-1440W (on one 110-120V/15A circuit), also running two on one circuit.

I'll have to plug the kill-a-watt in again, but I didn't think it read nearly that high last time.

[networkgeek24]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

[Digitalmocking]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

I'm running 2.6.9 on all mine and have the same issue, cgminer4.7.0

[Duce]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

I'm running 2.6.9 on all mine and have the same issue, cgminer4.7.0

You will see 4.8 if you set the flag to 2, used to mine on nice/west hash with extranonce.subscribe enabled otherwise you will see 4.7 as you are.

EDIT: Taken from nicehash ASIC guide page:You can also download pre-compiled binaries for Spondoolies SP2x and SP3x with cgminer 4.8 and extranonoce.subscribe patch and replace stock Spondoolies cgminer (instructions included in README file). Please note that this cgminer is already included in latest Spondoolies SP2x and SP3x firmware!

[networkgeek24]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

I'm running 2.6.9 on all mine and have the same issue, cgminer4.7.0

You will see 4.8 if you set the flag to 2, used to mine on nice/west hash with extranonce.subscribe enabled otherwise you will see 4.7 as you are.

What am I doing wrong here? Would love to get this resolved!






Multiple reboots have been performed. Thanks in advance!

[PeaMine]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

I'm running 2.6.9 on all mine and have the same issue, cgminer4.7.0

You will see 4.8 if you set the flag to 2, used to mine on nice/west hash with extranonce.subscribe enabled otherwise you will see 4.7 as you are.

EDIT: Taken from nicehash ASIC guide page:You can also download pre-compiled binaries for Spondoolies SP2x and SP3x with cgminer 4.8 and extranonoce.subscribe patch and replace stock Spondoolies cgminer (instructions included in README file). Please note that this cgminer is already included in latest Spondoolies SP2x and SP3x firmware!

I have the flag set to 2 for use on nicehash, but on nicehash I do not have any green checks showing it's working.
Is there something else needed to be done other than set the flag to 2 and run 2.6.9 ?

[philipma1957]

Is cgminer supposed to be upgraded automatically when the firmware is upgraded? I just performed the firmware upgrade on one of my SP20s and it still shows cgminer 4.7.0 on the dashboard page.

Try a Reboot from the miner's home page.  That's what did it (cgminer 4.8.0) for me.

I've upgraded all my SP20's to firmware 2.6.1 and have done reboots on all of them. The dashboard page still shows cgminer4.7.0 .

I'm running 2.6.9 on all mine and have the same issue, cgminer4.7.0

You will see 4.8 if you set the flag to 2, used to mine on nice/west hash with extranonce.subscribe enabled otherwise you will see 4.7 as you are.

What am I doing wrong here? Would love to get this resolved!






Multiple reboots have been performed. Thanks in advance!

your start volts are

 0.660
0.660
0.660
0.660

use 0.665 not 0.700 for max volts


more

your watts are
 1100
 1100
 1100
 1100

use
220
220
220
220

lastly what firmware are you on now?

[networkgeek24]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

[mike9]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

As you have, plus adding #xnsub to the end of the URL and a restart worked for me on all miners.  i.e.

Code:

stratum+tcp://stratum.westhash.com:3334#xnsub

[PeaMine]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

As you have, plus adding #xnsub to the end of the URL and a restart worked for me on all miners.  i.e.

Code:

stratum+tcp://stratum.westhash.com:3334#xnsub

Thanks, this allows the green checkmark on Nicehash, but breaks the secondary pool as Nicehash, even when pricing is below p=value, stays Alive and never fails over to the secondary pool.
Also when using p=value in this way, once the price is no longer met, the miner simply stops sending any shares, and does not fail over to the secondary.
Firmware 2.6.9, tested on multiple SP20s and also affects S5 the same way.

[philipma1957]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

As you have, plus adding #xnsub to the end of the URL and a restart worked for me on all miners.  i.e.

Code:

stratum+tcp://stratum.westhash.com:3334#xnsub

Thanks, this allows the green checkmark on Nicehash, but breaks the secondary pool as Nicehash, even when pricing is below p=value, stays Alive and never fails over to the secondary pool.
Also when using p=value in this way, once the price is no longer met, the miner simply stops sending any shares, and does not fail over to the secondary.
Firmware 2.6.9, tested on multiple SP20s and also affects S5 the same way.

okay I will try to mirror your problem.

stratum+tcp://stratum.westhash.com:3334#xnsub   ---  url

1JdC6Xg3aj_________________53Vbtje.1  ------- btc addy

p=0.0112 -------------------------------------------- price limit


firmware is 2.6.9

cgminer is 4.8

extranonce subscription check mark shows at westhash.

[mike9]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

As you have, plus adding #xnsub to the end of the URL and a restart worked for me on all miners.  i.e.

Code:

stratum+tcp://stratum.westhash.com:3334#xnsub

Thanks, this allows the green checkmark on Nicehash, but breaks the secondary pool as Nicehash, even when pricing is below p=value, stays Alive and never fails over to the secondary pool.
Also when using p=value in this way, once the price is no longer met, the miner simply stops sending any shares, and does not fail over to the secondary.
Firmware 2.6.9, tested on multiple SP20s and also affects S5 the same way.

Are you using anything in addition to p=value in the password field?  Does your rollover pool show Alive, even while mining on Nicehash?  

My settings are similar to philipma's, and work exactly as expected on multiple miners.  I'm on fw v2.6.9 - I don't know where *it* went to, or why it was pulled (edit: current fw shows v2.6.1)

(another edit) only use the #xnsub on Nicehash and Westhash, not on your fallover pool(s).

[PeaMine]

Whoops, wasn't asking for advice on the power settings. BTW if you select any of the "Basic" settings, it auto puts those super high wattage figures in. Anyways, I'm happy with my current power to hashrate figures so not going to muck with those.

My pictures were intended to point out that I had the extranonce setting on 2 and was still seeing cgminer4.7.0 in contrast to what the previous poster mentioned. Trying to get that issue resolved.

As you have, plus adding #xnsub to the end of the URL and a restart worked for me on all miners.  i.e.

Code:

stratum+tcp://stratum.westhash.com:3334#xnsub

Thanks, this allows the green checkmark on Nicehash, but breaks the secondary pool as Nicehash, even when pricing is below p=value, stays Alive and never fails over to the secondary pool.
Also when using p=value in this way, once the price is no longer met, the miner simply stops sending any shares, and does not fail over to the secondary.
Firmware 2.6.9, tested on multiple SP20s and also affects S5 the same way.

Are you using anything in addition to p=value in the password field?  Does your rollover pool show Alive, even while mining on Nicehash?  

My settings are similar to philipma's, and work exactly as expected on multiple miners.  I'm on fw v2.6.9 - I don't know where *it* went to, or why it was pulled (edit: current fw shows v2.6.1)

(another edit) only use the #xnsub on Nicehash and Westhash, not on your fallover pool(s).

I only have the p=0.0121 setting in the password field.
The other secondary pool shows as Alive as well, but with stratum+tcp://stratum.westhash.com:3334#xnsub in the primary pool, and 2 in the Miner Setting flags, it will never fail over to the secondary pool.
Remove #xnsub, I lose checkmark on westhash but failover works perfectly, including switching back when westhash meets price requirement from the secondary pool.
This is on three SP20E plus my friend's as well.

Edit:
Seems that they are currently swapping pools after around 20 minutes.
Will monitor more.

[philipma1957]

  both my sp20's rolled over.  I will look for roll back.  as of now they should roll back since they are set for 0.0121

and the lowest pool is 0.0135  but if some one is renting at 0.0120  they will stay ahead of me.

this may be the issue you are having.  I will keep checking back.








full size image

http://imageshack.com/a/img911/8673/VU4WJO.png

[macgyver007]

version 2.6.10 (test version) has been released and seems better than 2.6.1 to me but power usage reports higher...give it a whirl if you like I have been testing it for the last few hours
On another note 2.6.9  didn't work very well on 2 test rigs here
I am also seeing similar symptoms with the price value and #xnsub on nicehash and no rollback so for now I took the price option out   I suspect it is what philipma said regarding rollover and rollback
As for extranonce working I have not had any problems with that only when adding the price field into the equation

[edonkey]

 both my sp20's rolled over.  I will look for roll back.  as of now they should roll back since they are set for 0.0121

and the lowest pool is 0.0135  but if some one is renting at 0.0120  they will stay ahead of me.

this may be the issue you are having.  I will keep checking back.

Forgive me if this has been asked earlier. Unfortunately searching on the forum at large seems to be broken.

Like you I'm using NiceHash (or rather WestHash) as the primary with a profitability value set to flat BTC/THs/Day. I'm not having any problems with the miner switching. I've got 2.5.52 firmware.

My concern is that switches happen fairly frequently. That means that my miner sporadically points at WestHash and the secondary throughout the day, which results in automated pool-hopping.

While it's nice to take advantage of NiceHash's profitability, I'm concerned that the sporadic hash rate pointed at my secondary pool results in an effective penalty while it charges up. Since it's hard to track this split profitability, I'm not sure if I'm actually ahead, or if I'd be better off just pointing at a non-rental pool and be done with it.

I noticed that you're using Kano.is as the failover pool. I currently have BTCGuild as my secondary. I switched from Slush because from what I gather, the score method used by that pool penalizes pool hopping.

Any particular reason why you chose Kano as the secondary to WestHash?

On a related note, I wish that NiceHash would let us specify profitability as a percentage instead of a constant. That way we wouldn't have to keep changing the value after each difficulty change. I posted this as a request on the the NiceHash forum thread a while back, but got no reply from them.

[philipma1957]

 both my sp20's rolled over.  I will look for roll back.  as of now they should roll back since they are set for 0.0121

and the lowest pool is 0.0135  but if some one is renting at 0.0120  they will stay ahead of me.

this may be the issue you are having.  I will keep checking back.

Forgive me if this has been asked earlier. Unfortunately searching on the forum at large seems to be broken.

Like you I'm using NiceHash (or rather WestHash) as the primary with a profitability value set to flat BTC/THs/Day. I'm not having any problems with the miner switching. I've got 2.5.52 firmware.

My concern is that switches happen fairly frequently. That means that my miner sporadically points at WestHash and the secondary throughout the day, which results in automated pool-hopping.

While it's nice to take advantage of NiceHash's profitability, I'm concerned that the sporadic hash rate pointed at my secondary pool results in an effective penalty while it charges up. Since it's hard to track this split profitability, I'm not sure if I'm actually ahead, or if I'd be better off just pointing at a non-rental pool and be done with it.

I noticed that you're using Kano.is as the failover pool. I currently have BTCGuild as my secondary. I switched from Slush because from what I gather, the score method used by that pool penalizes pool hopping.

Any particular reason why you chose Kano as the secondary to WestHash?

On a related note, I wish that NiceHash would let us specify profitability as a percentage instead of a constant. That way we wouldn't have to keep changing the value after each difficulty change. I posted this as a request on the the NiceHash forum thread a while back, but got no reply from them.

yes Kano's method make the shares dropoff 5x slower then btcguild or slush.   you can use him or


https://www.f2pool.com/  this pool every share you earn you get paid  fees are 4%

kano's pool fees are 0.9 %   better then above.  but if you spend a lot of time on westhash and kano's pool does 2 really bad blocks in a row you lose some shares.

I did a lot of math  and I do

1) westhash set for a p=0.016
2) kano--------------------------------------- 0.9% fee should work over the chance of two 500% blocks in a row.
3) f2pool--------------------------------------4.0% fee is not as good as 0.9% with no penalty until two 500% blocks in  row


I used https://mining.bitcoinaffiliatenetwork.com/   but they have been paying too slow


this is their thread

https://bitcointalk.org/index.php?topic=854368.0;all