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

RawDog

legendary

Activity: 1596

Merit: 1026

Quote from: wh00per on August 01, 2014, 07:15:28 PM

Quote from: Marvell1 on August 01, 2014, 07:07:43 PM

We are unlucky and you were lucky lets leave it at that ok?

He's lucky if he's mining as he said. Somehow, I doubt it.

Doubt away suckers! S3s are cranking away day and night while Spondoolies is giving their people nothing but lies and sub 4TH.

I am fucking shocked that Spondoolies let everyone down. I was 100% convinced they nailed it. In the very earliest days, I wrote to them: "yeah, but that is what BFL, KnC and others were saying too". They were 100% confident they knew what they are doing. Hahahahaha. What a sucker I was to believe that crap.

Now, we don't hear anything about fair compensation nor shipping numbers. Just like KnC who shipped out 5 units - they report "we are currently shipping on time". Sure they are. Fool me once, shame on me. Fool me twice - well, you know.

wh00per

hero member

Activity: 572

Merit: 500

Quote from: Marvell1 on August 01, 2014, 07:07:43 PM

We are unlucky and you were lucky lets leave it at that ok?

He's lucky if he's mining as he said. Somehow, I doubt it.

Powell

sr. member

Activity: 486

Merit: 262

rm -rf stupidity

Whats funny is every time someone brings up PSU's they act like they don't have any just sitting around. If you've had any miner for the most part you have PSU's laying around.

I mean I have 11 on the shelf and 2 on miners. One of them is a 750W and the rest are 1000-1500W.

Actually I threw away 22 DELL PSU's the other day just because they were wasting space (have 22 boards if I ever needed the PSU's again).

So if I (or anyone whos owned a miner) wanted to compare $4500 in S3 vs $4500 the preorder why would you need to factor in the PSU cost.

jtoomim

hero member

Activity: 818

Merit: 1006

Roadstress, opentoe, Marvell1, everybody: please stop feeding the trolls.

Marvell1

legendary

Activity: 2408

Merit: 1102

Leading Crypto Sports Betting & Casino Platform

Quote from: opentoe on August 01, 2014, 07:05:46 PM

Quote from: Marvell1 on July 23, 2014, 12:47:49 AM

Quote from: Collider on July 22, 2014, 10:57:17 PM

They are still very much on time, as it is still July Wink

It is also understandable that they dont comment at this point, as they are probably pulling 24/7 working days to get everything running.

Even if DHL couldn´t ship, they would be able to locally host your units in their datacenter (atleast for the July batch, as it is very small).

I also find it highly disrespectful and inhumane to reduce an armed conflict to "I hope my stuff wil ship in time".

dude get off your high horse, yeah its terrible what is going on out there but a lot of us have a lot riding on this investment we have 110% the right to be concerned

This is the nature of the pre-order. Can't blame anyone but themselves if the shit hits the fan.

No we can't but we can at least expect our vendor to make it right, and we are still hoping they will.

Marvell1

legendary

Activity: 2408

Merit: 1102

Leading Crypto Sports Betting & Casino Platform

Quote from: RoadStress on August 01, 2014, 06:57:45 PM

Quote from: RawDog on August 01, 2014, 06:52:46 PM

Why the silence? Why won't Spondoolies comment about how many are shipped and how many are likely to be shipped next week? They are just like KnC. Total silence in the storm of failure.

Because they don't need to report to you as a non-customer about their status. I see that people are reporting having units in hand so units are shipping.

As for the silence we had 2 Sp-Tech members post here in the last 24 hours so stop lying.

How about you show us some proof of the S3 that you just purchased?

lol I'm a customer and I have got zero contacts since they sent the apology email about not meeting their spec. We are also still waiting for REAL compensation package not some stupid 1 or 2 btc discount
they need to replace our missing hash rate and efficiency losses. Yeah I get that is pre-order and we took a risk but they pretty much assured us they would meet spec so when the s3s came out a lot of us passed on the early batched.

@Rawdog - come on dud you happened to get lucky that bitmain ninja launched their 28nm hardware , don't act like you knew what u were doing when you passed on the sp30. In April and may the sp30 was the hands down BEST deal out there, even if they had listed the spec at 4.5TH it was the best thing out there at the time and they at that time also had a proven record with the sp10. You got lucky dude don't act like you are smarter than any of us who pre-ordered. Now we are seeing shipped units hashing at 4.1 TH that makes it look worse.

The BTC game has turned in a random game of chance luck and god knows what else. We are unlucky and you were lucky lets leave it at that ok?

opentoe

legendary

Activity: 1274

Merit: 1000

Personal text my ass....

Quote from: Marvell1 on July 23, 2014, 12:47:49 AM

Quote from: Collider on July 22, 2014, 10:57:17 PM

They are still very much on time, as it is still July Wink

It is also understandable that they dont comment at this point, as they are probably pulling 24/7 working days to get everything running.

Even if DHL couldn´t ship, they would be able to locally host your units in their datacenter (atleast for the July batch, as it is very small).

I also find it highly disrespectful and inhumane to reduce an armed conflict to "I hope my stuff wil ship in time".

dude get off your high horse, yeah its terrible what is going on out there but a lot of us have a lot riding on this investment we have 110% the right to be concerned

This is the nature of the pre-order. Can't blame anyone but themselves if the shit hits the fan.

RoadStress

legendary

Activity: 1904

Merit: 1007

Quote from: RawDog on August 01, 2014, 06:52:46 PM

Why the silence? Why won't Spondoolies comment about how many are shipped and how many are likely to be shipped next week? They are just like KnC. Total silence in the storm of failure.

Because they don't need to report to you as a non-customer about their status. I see that people are reporting having units in hand so units are shipping.

As for the silence we had 2 Sp-Tech members post here in the last 24 hours so stop lying.

How about you show us some proof of the S3 that you just purchased?

RawDog

legendary

Activity: 1596

Merit: 1026

Quote from: RoadStress on August 01, 2014, 06:50:27 PM

Quote from: ZiG on August 01, 2014, 06:32:15 PM

4.153GH / 441GH = ~ 9 x S3 * ~$400 each = #3600 as we speak...

And you paid what...$5,600...to $11,500 for this "deliver on time and on specs" thingy... Huh

Where are the 5 PSUs included in that price?

S3 PSU's cost $69 each. I am happy to pay that to have a working miner instead of promises of coupons and delivery dates which are being pushed way out to god knows when.

Why the silence? Why won't Spondoolies comment about how many are shipped and how many are likely to be shipped next week? They are just like KnC. Total silence in the storm of failure.

RoadStress

legendary

Activity: 1904

Merit: 1007

Quote from: ZiG on August 01, 2014, 06:32:15 PM

4.153GH / 441GH = ~ 9 x S3 * ~$400 each = #3600 as we speak...

And you paid what...$5,600...to $11,500 for this "deliver on time and on specs" thingy... Huh

Where are the 5 PSUs included in that price?

RawDog

legendary

Activity: 1596

Merit: 1026

Quote from: ZiG on August 01, 2014, 06:32:15 PM

4.153GH / 441GH = ~ 9 x S3 * ~$400 each = #3600 as we speak...
And you paid what...$5,600...to $11,500 for this "deliver on time and on specs" thingy... Huh

No shit. What a great deal from the guys who say: 'Seriously, we know what we are doing. You can take that uncertainty out of the equation".

Antminer is killing Spondoolie. That is fucking embarrassing. Lucky for me, I am sitting in a room full of S3s. Sad for me - I also have a shitload of Neptunes and Yukons I have to eat. Fuck.

opentoe

legendary

Activity: 1274

Merit: 1000

Personal text my ass....

Quote from: kendog77 on July 21, 2014, 11:15:59 AM

jimmothy is just bitter because ASICMiner botched the design of their Gen3 chip and ended up with increased power usage and a chip that is no longer competitive with Bitmain. The ASICMiner Gen3 miners I've seen to date look like amateur, second rate products compared to the S3. ASICMiner shareholders are very biased and seem to lack objectivity when looking at the current mining landscape.

It looks like folks who gambled on the Roadstress SP30 group buy may end up having their bet pay off. I still very much doubt that a SP30 for 5k with a September delivery is a good buy, but a 4.5k SP30 with an early August delivery is looking like a very good buy.

Simulations are one thing, and final performance often differs from simulated numbers, but it sounds like we'll know if the SP30 performs according to specification within a week.

I can understand where's he coming from. Some people are just tired of pre-orders and biting their nails hoping they actually make their money back. The bitcoin market is so big now manufacturers don't have to worry about not selling out their pre-order gear. There will always be the new kid on the block that will dump out however much money regardless if they break even or not. People that have been in the "hobby" more and are more aware of what's going on are able to make better decisions. Instead of giving SPTECH my $10k I gave it to another company that actually had the hardware in stock and didn't have to worry about "IF" I would make all my money back or not since it only took 6 days to get to me and been hashing for quite some time now. In the future if SPTECH does change their business model to a conventional one (where you pay for something that is available) then I'll give them my money. It is all about making good decisions based on the information you have. Good luck!

hdbuck

legendary

Activity: 1260

Merit: 1002

Quote from: ZiG on August 01, 2014, 06:32:15 PM

4.153GH / 441GH = ~ 9 x S3 * ~$400 each = #3600 as we speak...
And you paid what...$5,600...to $11,500 for this "deliver on time and on specs" thingy... Huh

touché ^^

ZiG

sr. member

Activity: 406

Merit: 250

blaiser

member

Activity: 99

Merit: 10

Thank you for sharing your (early) experience with the SP30.

Regards,

~Blaise

jtoomim

hero member

Activity: 818

Merit: 1006

I received my first SP30. It's got the Emerson PSUs. I'm running it on 122V in our office space because our DC isn't ready yet. It's running at 3383 GH/s right now, and using 1954 W, or 0.577 J/GH. I haven't gotten around to tweaking it yet, or configuring it to ignore the firmware limit on power consumption for 120V supplies. I saw 3800 GH/s at one point, but I think I changed around the settings afterwards and I can't remember what I had it at that gave 3800. I'll figure that out later.

I have it connected to two separate 20A circuits, and I haven't had any breakers trip. It seems it restarts cgminer frequently, which makes it hard to configure. When the fans shut down, you don't know if it's because of something you did or just because it's doing its thing.

ASIC #23 seems to be damaged somehow. It's usually clocked at a lower frequency, and at one time I saw it disabled by the system.

I'll give reports later on how supply voltage and other settings changes performance. I'm going to try the "touch /etc/mg_ignore_110_fcc" mod to see if I can get some moar powr our of the machine.

Edit: Something I did boosted hashrate up to around 3.9 TH/s (and maybe still climbing?). It seems that you may need to click on the "Restart Minergate" button on the main page in order to get new clockspeed settings to be enabled. Clicking the text on the Settings page to restart Minergate might not work. Not sure yet what's going on. More later. Edit 5: Nope, it's just that the custom settings don't work, as mentioned in Edit 4.

Edit 2: 4158 GH/s now on 122 V using 2688 W at the wall for 0.646 J/GH.

Edit 3: I think the issue I've been observing is that the file /etc/mg_custom_mode exists and had the following contents:

FAN:90 VST:660 VSB:660 VMAX:770 AC_TOP:1150 AC_BOT:1150 DC_AMP:150

The WebUI wasn't updating that file when I entered new settings, so I'm going to change it now by SSH and see what happens. I'm changing them to this:

FAN:90 VST:670 VSB:670 VMAX:780 AC_TOP:1250 AC_BOT:1250 DC_AMP:150

Edit 4: Okay, so I changed it, then hit Restart Minergate, then checked the file again, and it's back to VST: 660 etc. Something in the firmware is rewriting the custom mode values with conservative values when Minergate is restarted, it seems. Running the SP30 in Turbo mode (instead of the advanced settings custom mode) seems to produce 4.1 TH/s, but the custom mode is stuck at very conservative settings which give me around 3.4 TH/s.

Edit 6: It turns out there's some real bullshit in /etc/init.d/S90spondoolies. Take a look if you get a chance, and see if you can spot it. Oh hey, there's a new firmware version (Current firmware version: 2.2.13, Latest available firmware version: 2.2.22). I guess I'll try that.

Edit 7: The new firmware seems to allow me to edit mg_custom_mode and have those changes persist through minergate restarts. However, the second PSU is stuck at a max voltage of 1080 W as reported in the stats page and the main page, despite a value of 1340 W stored in mg_custom_mode.

---

Old stats, when I was getting 3.4 TH/s. Note the "PSU-TOP[EMERSON1200]: 944->812w" line, which indicates that the top PSU was only using 944 W.

Code:

----------
leading zeroes=42
-----TOP-BOARD-----
PSU-TOP[EMERSON1200]: 944->812w[812 812 812] (lim=1150) 0c cooling:0
LOOP[0] ON :)
 0: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 47W  71A  42c] ASIC:[ 80c  565hz(TL:1245/BL: 565)  42 (193)]
 1: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 44W  67A  42c] ASIC:[ 80c  545hz(TL:1245/BL: 545)  48 (193)]
 2: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  40c] ASIC:[ 80c  585hz(TL:1245/BL: 585)  45 (193)]
LOOP[1] ON :)
 3: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 48W  73A  44c] ASIC:[ 80c  555hz(TL:1245/BL: 555)  51 (193)]
 4: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 43W  66A  46c] ASIC:[ 80c  545hz(TL:1245/BL: 545)  45 (193)]
 5: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 48W  73A  48c] ASIC:[ 80c  590hz(TL:1245/BL: 590)  45 (193)]
LOOP[2] ON :)
 6: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 45W  69A  50c] ASIC:[ 80c  575hz(TL:1245/BL: 575)  41 (193)]
 7: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 47W  72A  50c] ASIC:[ 80c  575hz(TL:1245/BL: 575)  41 (193)]
 8: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 44W  67A  42c] ASIC:[ 80c  530hz(TL:1245/BL: 530)  37 (180)]
LOOP[3] ON :)
 9: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 50W  76A  52c] ASIC:[ 80c  575hz(TL:1245/BL: 575)  43 (193)]
10: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 51W  78A  54c] ASIC:[ 80c  605hz(TL:1245/BL: 605)  53 (193)]
11: DC2DC/1/:[vlt1:652 vlt2:658(DCl:794 Tl:794 Ul:778) 48W  73A  54c] ASIC:[ 80c  595hz(TL:1245/BL: 595)  39 (193)]
LOOP[4] ON :)
12: DC2DC/1/:[vlt1:652 vlt2:658(DCl:794 Tl:794 Ul:778) 46W  71A  56c] ASIC:[ 80c  575hz(TL:1245/BL: 575)  33 (193)]
13: DC2DC/1/:[vlt1:652 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  56c] ASIC:[ 80c  605hz(TL:1245/BL: 605)  49 (193)]
14: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 50W  77A  47c] ASIC:[ 80c  585hz(TL:1245/BL: 585)  43 (193)]
----BOTTOM BOARD------
PSU-BOT[EMERSON1200]: 1008->868w[864 868 856] (lim=1150) 0c cooling:0
LOOP[5] ON :)
15: DC2DC/1/:[vlt1:652 vlt2:658(DCl:794 Tl:794 Ul:778) 44W  67A  41c] ASIC:[ 80c  565hz(TL:1245/BL: 565)  53 (193)]
16: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 43W  66A  41c] ASIC:[ 80c  560hz(TL:1245/BL: 560)  48 (193)]
17: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 50W  76A  40c] ASIC:[ 80c  605hz(TL:1245/BL: 605)  36 (193)]
LOOP[6] ON :)
18: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  74A  48c] ASIC:[ 80c  610hz(TL:1245/BL: 610)  52 (193)]
19: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 47W  72A  48c] ASIC:[ 80c  595hz(TL:1245/BL: 595)  53 (193)]
20: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 43W  66A  48c] ASIC:[ 80c  550hz(TL:1245/BL: 550)  42 (193)]
LOOP[7] ON :)
21: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 44W  67A  52c] ASIC:[ 80c  570hz(TL:1245/BL: 570)  50 (193)]
22: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 50W  76A  54c] ASIC:[ 80c  630hz(TL:1245/BL: 630)  56 (193)]
23: DC2DC/1/:[vlt1:652 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  45c] ASIC:[ 80c  620hz(TL:1245/BL: 620)  33 (192)]
LOOP[8] ON :)
24: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 39W  59A  48c] ASIC:[ 80c  495hz(TL:1245/BL: 495)  33 (191)]
25: DC2DC/1/:[vlt1:654 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  55c] ASIC:[ 80c  615hz(TL:1245/BL: 615)  34 (193)]
26: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  57c] ASIC:[ 80c  620hz(TL:1245/BL: 620)  43 (193)]
LOOP[9] ON :)
27: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 49W  75A  60c] ASIC:[ 80c  620hz(TL:1245/BL: 620)  53 (193)]
28: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 48W  74A  61c] ASIC:[ 80c  625hz(TL:1245/BL: 625)  40 (193)]
29: DC2DC/1/:[vlt1:656 vlt2:658(DCl:794 Tl:794 Ul:778) 50W  77A  51c] ASIC:[ 80c  645hz(TL:1245/BL: 645)  48 (193)]

[H:HW:3383Gh[1660+1722],W:1426,L:0,A:30,MMtmp:0 TMP:(26)=>=>=>(52,53)]
Pushed 30 jobs , in HW queue 4 jobs (sw:3, hw:3)!
min:26 wins:1329[this/last min:17/40] bist-fail:81, hw-err:0
leading-zeroes:42 idle promils[s/m]:0/0, rate:2796gh/s
Fan:90, conseq:200
I2C BUSY with BUG: 0
Adapter queues: rsp=3, req=20

New stats, with 4153 GH/s. Note that it's being limited to about 1150 or 1144 W per PSU right now. Need to figure out how to bypass that soon

Code:


----------
leading zeroes=43
-----TOP-BOARD-----
PSU-TOP[EMERSON1200]: 1328->1152w[1140 1152 1152] (lim=1150) 0c cooling:0
LOOP[0] ON :)
 0: DC2DC/1/:[vlt1:679 vlt2:682(DCl:794 Tl:794 Ul:727) 63W  93A  53c] ASIC:[ 80c  720hz(TL:1245/BL: 720)  26 (193)]
 1: DC2DC/1/:[vlt1:675 vlt2:682(DCl:794 Tl:794 Ul:727) 60W  88A  52c] ASIC:[ 80c  700hz(TL:1245/BL: 700)  26 (193)]
 2: DC2DC/1/:[vlt1:681 vlt2:682(DCl:794 Tl:794 Ul:727) 65W  95A  49c] ASIC:[ 80c  725hz(TL:1245/BL: 725)  26 (193)]
LOOP[1] ON :)
 3: DC2DC/1/:[vlt1:675 vlt2:682(DCl:794 Tl:794 Ul:727) 63W  93A  53c] ASIC:[ 80c  710hz(TL:1245/BL: 710)  28 (193)]
 4: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 58W  85A  58c] ASIC:[ 80c  685hz(TL:1245/BL: 685)  32 (193)]
 5: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 64W  94A  61c] ASIC:[ 80c  730hz(TL:1245/BL: 730)  43 (193)]
LOOP[2] ON :)
 6: DC2DC/1/:[vlt1:679 vlt2:682(DCl:794 Tl:794 Ul:727) 61W  90A  63c] ASIC:[ 80c  720hz(TL:1245/BL: 720)  25 (193)]
 7: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 61W  90A  63c] ASIC:[ 80c  710hz(TL:1245/BL: 710)  32 (193)]
 8: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 60W  88A  51c] ASIC:[ 80c  680hz(TL:1245/BL: 680)  26 (180)]
LOOP[3] ON :)
 9: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 66W  97A  63c] ASIC:[ 80c  720hz(TL:1245/BL: 720)  32 (193)]
10: DC2DC/1/:[vlt1:671 vlt2:680(DCl:794 Tl:794 Ul:727) 66W  97A  69c] ASIC:[ 80c  740hz(TL:1245/BL: 740)  33 (193)]
11: DC2DC/1/:[vlt1:675 vlt2:680(DCl:794 Tl:794 Ul:727) 62W  92A  68c] ASIC:[ 80c  735hz(TL:1245/BL: 735)  38 (193)]
LOOP[4] ON :)
12: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 62W  91A  73c] ASIC:[ 95c  725hz(TL:1245/BL: 725)  33 (193)]
13: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 66W  97A  73c] ASIC:[ 95c  765hz(TL:1245/BL: 765)  41 (193)]
14: DC2DC/1/:[vlt1:677 vlt2:682(DCl:794 Tl:794 Ul:727) 68W 100A  58c] ASIC:[ 80c  740hz(TL:1245/BL: 740)  36 (193)]
----BOTTOM BOARD------
PSU-BOT[EMERSON1200]: 1344->1144w[1144 1144 1140] (lim=1144) 0c cooling:0
LOOP[5] ON :)
15: DC2DC/1/:[vlt1:669 vlt2:674(DCl:794 Tl:794 Ul:727) 53W  80A  49c] ASIC:[ 80c  660hz(TL:1245/BL: 660)  36 (193)]
16: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 55W  81A  48c] ASIC:[ 80c  680hz(TL:1245/BL: 680)  32 (193)]
17: DC2DC/1/:[vlt1:673 vlt2:677(DCl:794 Tl:794 Ul:727) 63W  94A  49c] ASIC:[ 80c  730hz(TL:1245/BL: 730)  34 (193)]
LOOP[6] ON :)
18: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 62W  92A  57c] ASIC:[ 80c  735hz(TL:1245/BL: 735)  42 (193)]
19: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 61W  91A  58c] ASIC:[ 80c  730hz(TL:1245/BL: 730)  32 (193)]
20: DC2DC/1/:[vlt1:675 vlt2:677(DCl:794 Tl:794 Ul:727) 55W  82A  57c] ASIC:[ 80c  670hz(TL:1245/BL: 670)  35 (193)]
LOOP[7] ON :)
21: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 55W  82A  63c] ASIC:[ 80c  685hz(TL:1245/BL: 685)  32 (193)]
22: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 62W  91A  68c] ASIC:[ 80c  740hz(TL:1245/BL: 740)  24 (193)]
23: DC2DC/1/:[vlt1:671 vlt2:677(DCl:794 Tl:794 Ul:727) 63W  93A  56c] ASIC:[ 80c  745hz(TL:1245/BL: 745)  26 (192)]
LOOP[8] ON :)
24: DC2DC/1/:[vlt1:673 vlt2:677(DCl:794 Tl:794 Ul:727) 50W  73A  56c] ASIC:[ 80c  595hz(TL:1245/BL: 595)  29 (191)]
25: DC2DC/1/:[vlt1:671 vlt2:674(DCl:794 Tl:794 Ul:727) 62W  92A  67c] ASIC:[ 80c  735hz(TL:1245/BL: 735)  40 (193)]
26: DC2DC/1/:[vlt1:669 vlt2:674(DCl:794 Tl:794 Ul:727) 62W  92A  70c] ASIC:[ 80c  745hz(TL:1245/BL: 745)  34 (193)]
LOOP[9] ON :)
27: DC2DC/1/:[vlt1:669 vlt2:674(DCl:794 Tl:794 Ul:727) 63W  94A  75c] ASIC:[ 80c  770hz(TL:1245/BL: 770)  29 (193)]
28: DC2DC/1/:[vlt1:673 vlt2:674(DCl:794 Tl:794 Ul:727) 60W  90A  73c] ASIC:[ 80c  735hz(TL:1245/BL: 735)  35 (193)]
29: DC2DC/1/:[vlt1:671 vlt2:674(DCl:794 Tl:794 Ul:727) 63W  94A  63c] ASIC:[ 80c  760hz(TL:1245/BL: 760)  48 (193)]

[H:HW:4153Gh[2085+2067],W:1847,L:0,A:30,MMtmp:0 TMP:(27)=>=>=>(65,65)]
Pushed 30 jobs , in HW queue 4 jobs (sw:3, hw:3)!
min:0 wins:985[this/last min:39/55] bist-fail:547, hw-err:0
leading-zeroes:43 idle promils[s/m]:0/0, rate:7689gh/s
Fan:90, conseq:200
I2C BUSY with BUG: 0
Adapter queues: rsp=1, req=21

tzortz

hero member

Activity: 728

Merit: 500

I did not expect to be like that, to be honest.

Syke

legendary

Activity: 3878

Merit: 1193

Quote from: jtoomim on July 31, 2014, 10:39:05 PM

You don't have to run it at that power level. If you use the Quiet mode in the firmware, you'll get a max voltage for the ASICs of 642 mV instead of 750 mV. I would guess that would reduce your J/GH by a factor of about (642^2 / 750^2) = 0.73 to about 0.47 J/GH, and reduce performance by a factor of about 642./750 = 0.856 to around 3.8 TH/s at 1900 W.

Nice idea, but dropping the machine all the way down to 3.8 TH/s will massively hurt profitability. Which is why Spondoolies' $/GH current compensation plan is inadequate.

Marvell1

legendary

Activity: 2408

Merit: 1102

Leading Crypto Sports Betting & Casino Platform