It might go that low, but IMO you have to be careful trying to bottom fish this one. All it will take is a positive update report from friedcat on gen3 and the price will instantly go to 0.5+. Will friedcat make such an announcement before gen3 ships? I don't know, but if you are trying to bottom fish that is the risk.

I consider anything from 0.3 or lower a good value. At 0.1 I will load up the dump truck (although for an investor of my size it is more like the glove box of a mini cooper) for shares.

I wouldn't jump to that conclusion. This is a troubleshooting thread for the Cubes so we are hearing about the problems some miners have encountered. But we don't know what percentage of people have no problems at all.

Overall I'm quite happy with the cubes I have. They are running well and the build quality is very nice (I really like the solid aluminum enclosure).

-dmc

Of course they are. And it would be nice if FC chimed in with any info he might have. But it isn't his obligation/duty/etc.

I'm afraid he is just stating the facts. I hope it does work out for PT owners, but I agree FC shouldn't be the mediator here.

My order arrived and is hashing away. Thanks SSB!

Is 192.168.1.1 really a DNS server?

I recommend using OpenDNS servers. Their IP addresses are:

208.67.220.220
208.67.222.222

-dmc

I'm trying to switch over from slush to eligius, but I'm positive it is working correctly. I'm using the stratum-mining-proxy like this:

mining_proxy.py -nm -q -p 3334 -o stratum.mining.eligius.st -cu 1MY_BTC_WALLET_ADDR -cp foo1

On the client side it appears to be working, but on the Eligius stats page for my wallet:

http://eligius.st/~wizkid057/newstats/userstats.php/1MY_BTC_WALLET_ADDR

I get the "not found in database. Please try again later, as stats sever is probably overloaded" error.

Is there anything I can do besides hitting the stats page to see if it is working (that I'm correctly authenticated with my wallet address)? I've waited a couple of hours now and it still is coming up as not found. I'm just trying to make sure I have everything configured correctly and I'm not just using the miners as space heaters here. TIA.

EDIT: Seems to be working now. I removed the -nm arg (no mid state) from stratum-mining-proxy. I was hashing with that arg earlier (AM Cubes), but I'm not so sure they are really compatible with it.

-dmc

Looks like latest confirm problem is fixed. I sure would like an official "hey we are still here" post from slush though. I don't like that there doesn't seem to be any communication channel to the pool operators when there is a problem.

The problem is I haven't seen any sign recently of things sorting themselves out. Round 21027 never got fixed and there has been no reply on the issue from slush. Sorry, but I need a pool operator that is at least responsive to problems.

I noticed that one as well.

I'm thinking about switching pools. I can understand glitches/bugs, but it looks like no one is manning the store here. Slush hasn't logged in in over a month and my email to the site goes unanswered. Meanwhile every time I check there is another glitch. I sure wish someone from the site would chime in and explain WTF is up. If they don't soon then I'm bailing.

Unfortunately the C10 cap popped on one of my cube boards today:



I was powering it up after rearranging some cables and saw the flash of light and heard an audible pop.

It sounds like the resellers don't yet have a warranty swap supply from Friedcat, so fingers crossed here that gets figured out ASAP.

The good news is, as dogie said, the cube hashes just fine with missing cards (with 1/6 less hashing goodness, of course).

BTW, I noticed while I was inside the cube that some of the boards were not seated in the casing slots (probably popped out during shipping). I also was missing a heat sink screw and some of the other heat sink screws were pretty loose. Be careful tightening them though -- heat sinks are pretty easy to strip.

-dmc

Geez, this bad luck streak is killing our average. Pool luck for 7 days is now 89% and 95% for 30 days.

Has there been a history of the problem taking this long to fix itself though? I mean that round was 100+ confirmed a long time ago and is now about to drop off of the stats round history page (so it will be much harder to track when/if it is fixed).

Correct dividends received today here. Thanks SJ.

Note to folks: the fuse burned out very slowly which caused the arc to melt the fuse casing which slightly welded the fuse into the fuse holder. I got it out, but it was a pain.

I think I'm going to replace it with an ACO (closed on bottom versus open) fast fuse instead:

www.amazon.com/Bussmann-VP-ATC-30-Acting-Blade/dp/B000AZ7SW8/

I just had the 30 amp fuse blow on my Cube.

Faulty fuse, faulty cube, or does the fuse just need to be higher rated than 30A for high clock setting?

+1 here as well.

So what is the story with how to get this resolved? I've sent an email, there are several posts here reporting the problem, and I've tried IRC. The actual BTC involved here is negligible, but it isn't confidence inspiring that these problems happen *and* then don't get resolved. Looks like slush hasn't logged in here in over a month. How is one supposed to file a support ticket request with him exactly?

Okay, I'm trying to figure out the numbers on this. Hopefully, SB can chime in with clarification. Let's take a Fully Assembled Unit with Hosting as an example:

$ 95.00 Assembly ($35 PCB + $60 PCB Assembly)
$123.50 DIY Kit (so Fan, Heatsink, etc. is $28.50 ($123.50 - $95))
$133.50 Full Unit (assembly of all parts and testing is therefore another $10)

$ 15.00 Hosting Setup

I'm a bit confused as to what are "assembly costs" (refunded at 25%) and "assembly fees" (refunded at 100%). A couple of possibilities:

Scenario 1:

 25% of $95.00 (where assembly is defined as the $35 PCB + $60 PCB assembly cost)
 25% of $28.50 (fan/heatsink/etc.)
100% of $10.00 (full unit assembly)
100% of $15.00 (hosting setup)
  Total $55.875

Scenario 2 (PCB and fan/heatsink costs not included as part of assembly costs, since they are purchased parts):

 25% of $60.00 ($60 PCB assembly cost only)
100% of $10.00 (full unit assembly)
100% of $15.00 (hosting setup)
  Total $40.00

Scenario 3

Other permutations? Am I making this more complicated than it really is or something?


If I understand this correctly, this is indeed epic. Using numbers above:

Scenario 1: $55.875 / $126.61 = 0.441315852 BTC refunded per hosted miner
Scenario 2: $40.00  / $126.61 = 0.315930811 BTC refunded per hosted miner

-dmc

You'll change the IP address and you'll need a different username/password combo (presuming you are using slush).

A couple of times now I've had my cubes reset from High clock to Low clock while unattended. Anyone else seen this? In High clock mode they seem to run fine (occasionally get 1 "x" on a chip, rejects and efficiency look great).

Related to this, is there any type of HTTP API to get the status of the cubes and/or control the clock rate? I'd like to setup a monitoring script that gets the reported hash rate (to log/graph) and automatically switches the clock back to High if it ends up on Low. The HTTP request that the "Clock" button uses toggles between Low and High, so I wonder if there is a better HTTP mechanism that allows discrete Low/High control (otherwise I'll have to screen scrape the current Clock state to make sure I don't toggle it to Low).

I just realized I probably didn't press the Update/Restart button after changing the clock to High. It looks like pressing that may be required for the High clock setting to stick? Note though I didn't restart the unit -- it spontaneously went to Low and/or restated itself.