[ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs

[wanna4fun]

I have spoken with Guy, Collider, and Roadstress on Skype. They're different people.

It might be worth mentioning that the August batches were open for quite a while before the August Group Buy, and the August batches closed shortly after the August Group Buy closed. This suggests that the August group buy orders are near the end of the August shipment queue, and should be expected to ship near the end of August. Many people who ordered SP30s before the August Group Buy have already received their miners. I know this because I have several of theirs in my datacenter.

All I know is if Spondoolies tries a KnC and ships a 'few' SP30 but fails to ship the entire GroupBuy prior to Sept 1, they aren't going to have to worry about Gaza any longer - bitcoin miners all over the world will be shooting 'rockets' there.  Even their beloved Iron Dome won't stop this barrage.

wtf is wrong with you??

What are you talking about?  If they don't deliver by Sept 1, people are going to be pissed.  What is wrong with you?

all sp10s were delivered on time, July SP30s were on time, my early august SP30s were on time. Please trash them when it's the 1st of sept, at the moment it's too early...

[1714048112]

1714048112

[1714048112]

1714048112

[1714048112]

1714048112

[1714048112]

1714048112

[Bowling-balls]

http://s4.postimg.org/4w614qsvx/elig.jpg

My order pre-dates the group order by a week or two and I've had my 3xSP30 hosted with Spondoolies and mining for 6 days now.
One was a bit ropey initially so they replaced it and added an extra node for a day to make up for the few hours downtime.
   
My pre-order experience with Spondoolies has been way better than most suppliers.
They were slightly overconfident to hit such high targets with that form factor on the initial batch, but not so much.
They have delivered good solid kit, on time, and not disastrously off spec. Plus they're giving some compensation.
This makes them a top supplier in my experience.

Pre-orders are a huge risk we choose to take in an attempt to get ahead of the curve.
They always miss spec on batch 1, almost always involve massive delays, and way too frequently the manufacturer delivers obsolete kit or nothing at all.
These guys have done extremely well.

BB

 

[RawDog]

They always miss spec on batch 1, almost always involve massive delays, and way too frequently the manufacturer delivers obsolete kit or nothing at all.
These guys have done extremely well.

This is true.

[zvisha]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

[RawDog]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

Welcome back from vacation!  I hope it was good.  Now get back to work. 

[Collider]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

Obviously spondoolies-tech is solely run by me, and zvi, Guy and RoadStress are all my alter egos.

I am further running my own hosting service and do not need any sleep, which puts me in the perfect position to manage a company, build miners and chips, and write software for said miners
(aswell as instruct and observe people to build my custom datacenter in the meantime).

I am a carbon based lifeform and my namer is Collider the capacious.

[grn]

I have spoken with Guy, Collider, and Roadstress on Skype. They're different people.

It might be worth mentioning that the August batches were open for quite a while before the August Group Buy, and the August batches closed shortly after the August Group Buy closed. This suggests that the August group buy orders are near the end of the August shipment queue, and should be expected to ship near the end of August. Many people who ordered SP30s before the August Group Buy have already received their miners. I know this because I have several of theirs in my datacenter.

All I know is if Spondoolies tries a KnC and ships a 'few' SP30 but fails to ship the entire GroupBuy prior to Sept 1, they aren't going to have to worry about Gaza any longer - bitcoin miners all over the world will be shooting 'rockets' there.  Even their beloved Iron Dome won't stop this barrage.

wtf is wrong with you??

Parents are 1st cousins

[grn]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

Obviously spondoolies-tech is solely run be me, and zvi, Guy and RoadStress are all my alter egos.

I am further running my own hosting service and do not need any sleep, which puts me in the perfect position to manage a company, build miners and chips, and write software for said miners
(aswell as instruct and observe people to build my custom datacenter in the meantime).

I am a carbon based lifeform and my namer is Collider the capacious.

Ahhhhh HA! 

[zvisha]

BTW, I found some stability issues in the code that *may* cause some miners in DC to get stuck. The reason is that the monitoring SW was touching the Minepeon pages every 30 second, and that action used to disable the watchdog for 1 minute, so watchdog was always off. Also some cases of stuck ASICs fixed.

I removed support from OLD Emerson FW - if some of you got it *by mistake - we were supposed to send only new Emerson FW* let me know - your miner will stop working with new FW - and I will return the old FW support.

The miners people will be getting from this week must use the new FW - we have different part (FET) in DC2DC and old FW won't recognise it.

Will release the new version tomorrow - update your miners please )

[zvisha]

Also, the new FW has a button to prepare report about your system for support.
If your system failing or under-performing, please send the report to us.
How to create a report in a few clicks:

---- Reproduce the issue to the logs ------
1) Press "Stop Miner"
2) Wait 30 seconds
3) Press "Start Miner"
4) Wait 1 minute for the log to fillup
----- Create report dump and send it to us --------
5) Just press the report button in the settings tab - it will download report file to your computer.
6) Send it to us with your support request.

That's it.

[edgar]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

Welcome back from vacation!  I hope it was good.  Now get back to work. 

Ha!

Now theyre both funny!


nothing wrong with me, but ive seen people get fkd by asic manufacturers since avalon batch 2 and not one of them has had any concerns with pitchfork wielding miners...

so essentially you are not only wrong, you're also intentionally being a shit-stirrer/dickhead.

its not needed.

how long before the 1000th rig gets shipped??

im in the 11xx area so kinda expecting some personal shipping news in my inbox....

have you guys (SP Tech) considered NOT taking regular 2-3 days off during , seemingly the most critical point of your multi-million dollar endeavour?

seems the logical thing to do...

[psahx]

Zvi, I have a problem...

One of my SP10s stopped mining several hours ago. Restart and reboot won't help. What are the suggestions?

Please help. Thanks.

[Collider]

@edgar
Please tell me how the software lead on a 3-day vacation (during which he was answering questions) slows production down.

I find it important to get a vacation here and there, especially in todays hamster-wheel work environment.

In case you didn´t know, Zvi was probably the hardest working guy for the last months, as most of the software work was done before release.


If Zvi got burnout because of your shitty "nobody gets a day off" strategy, you would have a much bigger problem on your hands.

[Collider]

@psahx
What does the asics tab say?

Also, have you tried a hardreset?

[psahx]

ASIC stats are empty, DCR all errors. Tried updating the firmware, went well, but still does not mine...

Code:

7797: i2c write 0x71 = 0x1 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 0 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x2 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 1 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x4 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 2 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x8 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 3 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x10 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 4 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x20 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 5 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x40 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 6 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x80 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 7 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x1 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 8 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x2 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 9 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x4 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 10 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x8 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 11 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x1 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 12 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x2 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 13 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x4 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 14 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x8 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 15 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x10 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 16 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x20 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 17 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x40 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 18 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x71 = 0x80 error2
7797: i2c write 0x72 = 0x0 error2
DC2DC DCR inductor flag loop 19 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x1 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 20 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x2 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 21 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x4 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 22 (0xD0) = 0xFFFFFFFF
7797: i2c write 0x72 = 0x8 error2
7797: i2c write 0x71 = 0x0 error2
DC2DC DCR inductor flag loop 23 (0xD0) = 0xFFFFFFFF

[Collider]

Power supply okay?

Have you tried the hardreset?

[psahx]

Power supply okay?

Have you tried the hardreset?

It is in the Data center. Cant try it till morning EST. 

[zvisha]

Why am I always left out?
I want to by Guy/Collider/RoadStress too!

Welcome back from vacation!  I hope it was good.  Now get back to work. 

Ha!

Now theyre both funny!


nothing wrong with me, but ive seen people get fkd by asic manufacturers since avalon batch 2 and not one of them has had any concerns with pitchfork wielding miners...

so essentially you are not only wrong, you're also intentionally being a shit-stirrer/dickhead.

its not needed.

how long before the 1000th rig gets shipped??

im in the 11xx area so kinda expecting some personal shipping news in my inbox....

have you guys (SP Tech) considered NOT taking regular 2-3 days off during , seemingly the most critical point of your multi-million dollar endeavour?

seems the logical thing to do...

Well, Edgar, being a SW developer there is not that much I can do on the production line. This is actually the most relaxed time for me since the beginning of this "endeavour", but I understand your concern

[zvisha]

Power supply okay?

Have you tried the hardreset?

It is in the Data center. Cant try it till morning EST. 

It looks like the i2c bus is not working properly.
It can be fixed by a power cycle usually.
Please try a full power cycle - if it`s not helping open an ssh tunnel for us so that we can look.

[zvisha]

@edgar
Please tell me how the software lead on a 3-day vacation (during which he was answering questions) slows production down.

I find it important to get a vacation here and there, especially in todays hamster-wheel work environment.

In case you didn´t know, Zvi was probably the hardest working guy for the last months, as most of the software work was done before release.


If Zvi got burnout because of your shitty "nobody gets a day off" strategy, you would have a much bigger problem on your hands.

Thank you very much. Exactly!