• Maximum power output – each SP20 requires 1152 W RMS continuous power. Spoondoolies-Tech recommends adding a 20% margin to handle power peaks.

       You can use combinations of power supplies to power the unit, such as 4 x 360 W, 2 X 720 W or 1 x 1400 W, by connecting the power supply/supplies rails to the SP20 accordingly.

In previous revision of the SP20 mechanical kit, the hashing boards may shift during transit due to the fact that they were not secured enough inside the box.
Most of the customers that were encountered the issue were able to solve by simply opening the box and press down the hashing board.

Some machines work fine at low temperatures. I've seen a few operate just dandy at intake temperatures as low as 2°C. However, others will show problems at intake temperatures as high as 8°C.

When a machine has trouble at low temperatures, it's often specific ASICs that show the problem (often #2 and #17). It's not always the ASICs in the front that have issues, though it seems more common to be those. Once an ASIC has trouble at low temperatures, it sometimes has trouble even when warmed up. Sometimes it has to be disabled permanently; other times it can be enabled once the machine is warmer.

In previous revision of the SP20 mechanical kit, the hashing boards may shift during transit due to the fact that they were not secured enough inside the box.
Most of the customers that were encountered the issue were able to solve by simply opening the box and press down the hashing board.

The mechanical problem with the SP20 was completely solved. We've tested and confirmed.

Issue for SP20... noisy?

I have had 39 SP30s running 2.5.12 so far for about 12 hours 16 minutes with no apparent issues. If I see no problems with 2.5.12 by next morning, I will probably move the rest of our machines over to it. Otherwise, I will probably move everything back to 2.4.23.

I've had a plethora of "disabled (bist cant start, stuck X)" errors on the remaining 100 or so SP30s we have running 2.5.6 in the mean time. It seems every few hours, I have to restart cgminer on 5% or 10% of our machines to get them back to full hashrate. Very annoying, but so far the issue has always been resolved by restarting minergate.

I've also had several reports of machines on 2.5.6 showing half hashrate at the pool even though I see full hashrate. These issues have always been restarted by a minergate restart.

I saw some much more serious problems on 2.5.7 during the 36 hours we had machines using that version. We saw about 10 machines get "Loop serial failed x" error messages (where x is a loop number, between 0 and 9 inclusive) and fail to start until one or sometimes two ASICs on that loop were disabled. After a few hours, many of these ASICs could be enabled again, but about 25% of the ones that failed are still non-operational. Currently, I think there are 9 ASICs which we lost on 2.5.7 which have not recovered.

It's possible that the potential ASIC-damaging bug in 2.5.7 might still be present in 2.5.12. I haven't seen any indications of it yet, but I also haven't had enough machines running on it for long enough to be certain. On 2.5.7, I saw the loop serial failed ASIC damage thing with about 5% of our machines per day. At that rate, there's only about a 63% chance that I would have seen it if it were present at the same rate in 2.5.12 with 39 machines running half a day.

Hi. I got my miner November 7th. Got it all plugged in and the 2nd board would cause a halt in cgminer. Miner would not hash. Eventually, I disabled all the ASICS on the 2nd board, and the miner would hash with only the first module.

Noticed that the boards sat at an angle inside the case, so I opened it up and re-aligned. The boards are not screwed in or secured with anything except some grooves raised up from the enclosure. Pretty cheap design, which is prone to board shifting if handled rough in transit.

After re-aligning, I manually enabled and disabled each ASIC on board 2, and figured out that ASIC 4 will not work under any voltage, the other ASICs on the board work fine. Getting 1300 GH/s with 7 ASICS...so not too bad at max 225w per module setting. I'll turn up the juice once all the problems have been worked out, hopefully.

Got an e-mail tonight from Barbara saying they will refund 0.12 BTC because the SP20s shipped late. I'm cool with that, so I thanked her and also told her to forward my diagnosis to tech support. Also filed a form for tech support asking for directions as to how to proceed. Requested they send me a replacement board.

I'd rather not ship the whole thing back and lose hashing time. I can do major surgery on just about any electronic device without a problem.

I have an SP10 Dawson also that has been going without a problem for months now. I can't really say I'm impressed with the SP20, because I'm so far pretty underwhelmed.

Firmware is still 2.5.6, not really sure about any other versions. Hopefully they will get all the bugs worked out soon.

That's our roadmap. It based on tech we're developing.

I have patient with your weekend trolling, started after I didn't agree to a deal you requested privately.

I don't have patient for your inappropriate and wicked comments here and before.

Guy

True when they called about the fire. I can see in the miner stats that the fire was already 1 hour going. So they where all sleeping ;-).  and stupid me trusted them with all this equipment. That's my big mistake. But again, I can't turn back time. No one hurt and a lesson learned.