[Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD]

[Curtix]

Houston we have a problem.
My Blade is tossing up XXXXXXXX
I wont get into too many details but this blade was sold working, user couldnt get it to work sent back and now its showing me all XXXXX.
http://s14.postimg.org/c2bajzmnl/XXX.png
Its a V2
Anything I can do / test.
I am using a PS setup that works with another V2 blade.

Isn't the port supposed to be 8332? You have 8334. Perhaps that is the problem.

I got the port from here: https://bitcointalk.org/index.php?topic=368656.0
Works on other miners?
Even so will bad port or pool give you XXX instead of OOO?

[Apteryx]

Possible fire hazard with cubes

I have just had my cube totally destroy the fuse and fuse holder.

The cube has been running for 8 days on high clock setting with out an issue, got up this morning, everything fine, went out for about 4 hours, came back the smell of burnt plastic.

The fuse it self : only the stubs of the blades left in the fuse holder.
The Fuse holder : charred remains only
The Board : some damage to the board itself.

It is obvious from the damage that the fault was a bad connection between the the fuse and fuse holder or the fuse holder and the circuit board.

If I could figure out how to insert pictures I would add some.

I would suggest to you all, that you check the fuse and fuse holder on all your cubes as a matter of urgency for signs of heating.

The good news is that I have managed to patch the board temporarily and the cube is apparently running without problem albeit at the low clock speed

[dresdenreader]

Well sadly it finally happened, I've got a cube that turns on with solid green and solid red, and it will start to hash, but eventually it will just stop communicating over the network and will go to the RED led being completely off.

Any suggestions?

I have five cubes all running on the same mining stratum proxy on the same getwork port. None of the other 5 are showing this problem, and this is something that just started happening recently.

Also, I've tried running solo mining with the cubes and I currently can't get it working without using the --http-port #### option. Additionally, no matter what I try, I can't get solo mining to work with just using the cube (no mining software no proxy) or solo mining with the proxy. (Solo mining Sha-256 altcoins not bitcoin I'm not stupid.)

[ksami]

I managed to replace the fan but I can't... it shutdown only the original fan works... weird thing !

[Apteryx]

Does the new fan have 2 wires or 3?  The cube requires a 3 wire fan (the 3rd wire is for the fan tacho, without it the cube thinks there is no fan installed, so it shuts down to stop over heating)

[ksami]

Does the new fan have 2 wires or 3?  The cube requires a 3 wire fan (the 3rd wire is for the fan tacho, without it the cube thinks there is no fan installed, so it shuts down to stop over heating)

3 wires of course ! 12V DC 0.19A

[Ktulu1]

I just wanted to chime in here about the long polling/restarting issue some people have been having. My cube worked fine on one network. When I moved it to a different location/network, I started having the same problem. This is a network problem. I haven't been able to determine what exactly the problem is or how to correct it in my situation, but I do have a kludgie work around that got my cube up and mining again by using two different proxy machines as primary and backup.

The cube mines for a little while, gets stuck on the one proxy, fails over to the other proxy, mines for a little while, and back and forth. It takes a bit of a performance hit this way, but it's currently the only way I can get the thing to mine on the network it's currently on. Hope this helps...

How did you set up your proxy. I tried and got the same result as not using a proxy.

mining_proxy.exe -o stratum.btcguild.com -p 3333

[NME]

Dogie,

This guide was excellent thank you!

I am currently averaging between 30 and 35 GH/s second with my Cube.

I have mined with Slush's pool for three days and only have .03 BTC to show for it?  Does that sound right?  I thought my rate of return would be higher?

-NME

[babaji.ca]

sounds about right

http://www.coinwarz.com/calculators/bitcoin-mining-calculator/?h=30000.00&p=280&pc=0.15&pf=0.00&d=1418481395.26264000&r=25.00000000&er=941.00000000&hc=0.00


you should have been averaging BTC 0.01063632 per day @ 30,000 MH/second over the last three days

network difficulty set to increase today i believe so you can check back at that site for an updated rate of average return once the diff increases from the current 1,418,481,395
you can ofcourse tweek that page to reflect more accurately power and hardware costs, pool fees .

i dont think that calculator accounts for any future increases in difficulty, i have seen better calculators out there that estimate future increases in diff, but not too sure where i have seen them......Bueller......Bueller......Bueller?

[Shaker242]

has anyone evaluated running multiple instances of slush's proxy but on different ports... like the --gp 8332, --gp 8333 etc?

That's what I've been doing all along... Sorry if that was unclear.  A new VM for each cube just sounds like it would eat up waaay too much RAM.

I'm after some advise on how I can get my cube to successfully mine on two separate pools, as in the primary/backup function, so if one looses connectivity or times out for any reason, it switches to the other pool.

...

Also what does diff 64, 128 and 256 mean?

Here's an example.

proxy1.bat:

Code:

mining_proxy.exe --host stratum.bitcoin.cz --port 3333 --getwork-port 8332 --stratum-port 3333

proxy2.bat:

Code:

mining_proxy.exe --host stratum.btcguild.com --port 3333 --getwork-port 8331 --stratum-port 3332

Then in your cube config page, set the ports to 8332,8331


The various difficulty settings are simply a way to control the bandwidth used by limiting the number of shares submitted.  Lower difficulty shares means a more accurate hashrate reported by the pool, vs higher difficulty shares means less bandwidth but higher variance.

I ended up building a small Ubuntu VM per Cube for a proxy; it actually doesn't use much ram or disk space so it's not too much of a big deal.  It is a pain in the ass since I'd like a single instance to cover all cubes and direct them all to slush's pool.  Anyway, with 4 cubes, I have 4 proxies and they will fail over to one of the other cubes should their primary fail.  I noticed when I was sharing one proxy, even with different ports and workers - I was getting ~25Gh/s, but once it's on a dedicated proxy it jumped over 30Gh/s.  I may have to alter things once again when I start adding more cubes.

[kern]

I hope someone can help me out on this.https://i.imgur.com/7C44R9k.png 

[mchu168]

I hope someone can help me out on this. 

I don't think you need the = sign on the command line:  "--http-port 3333" should do.

[dresdenreader]

I hope someone can help me out on this. 

Also, you're going to get a lot faster hashrate if you use stratum mining proxy with the following:

mining_proxy.exe -o stratum.btcguild.com -p 3333 -gp 8333 -q

For Primary and Secondary DNS I would recommend using OpenDNS instead.
Primary DNS: 208.67.220.220
Secondary DNS: 208.67.222.222

Also is your Gateway really 0.0.0.0?

run ipconfig in a command prompt and make sure your Default Gateway actually says 0.0.0.0.

[dresdenreader]

Well sadly it finally happened, I've got a cube that turns on with solid green and solid red, and it will start to hash, but eventually it will just stop communicating over the network and will go to the RED led being completely off.

Any suggestions?

I have five cubes all running on the same mining stratum proxy on the same getwork port. None of the other 5 are showing this problem, and this is something that just started happening recently.

Also, I've tried running solo mining with the cubes and I currently can't get it working without using the --http-port #### option. Additionally, no matter what I try, I can't get solo mining to work with just using the cube (no mining software no proxy) or solo mining with the proxy. (Solo mining Sha-256 altcoins not bitcoin I'm not stupid.)

Found my problem, it was the power supply.

The Corsair GS 800 has this annoying attribute where it will go into "power saving" mode randomly and stop supplying power to the cube.

I bought another Corsair HX 850 yesterday and hooked it up this morning and I've had no issues so far.

[Shaker242]

I hope someone can help me out on this.https://i.imgur.com/7C44R9k.png  

Also, you're going to get a lot faster hashrate if you use stratum mining proxy with the following:

mining_proxy.exe -o stratum.btcguild.com -p 3333 -gp 8333 -q

For Primary and Secondary DNS I would recommend using OpenDNS instead.
Primary DNS: 208.67.220.220
Secondary DNS: 208.67.222.222

Also is your Gateway really 0.0.0.0?

run ipconfig in a command prompt and make sure your Default Gateway actually says 0.0.0.0.

DNS doesn't matter if your using IP addresses, nor does the gateway if your using a local net proxy.  

http://s11.postimg.org/isdrel7hf/BE_Cube_Miner_21_png.png

[Shaker242]

Well sadly it finally happened, I've got a cube that turns on with solid green and solid red, and it will start to hash, but eventually it will just stop communicating over the network and will go to the RED led being completely off.

Any suggestions?

I have five cubes all running on the same mining stratum proxy on the same getwork port. None of the other 5 are showing this problem, and this is something that just started happening recently.

Also, I've tried running solo mining with the cubes and I currently can't get it working without using the --http-port #### option. Additionally, no matter what I try, I can't get solo mining to work with just using the cube (no mining software no proxy) or solo mining with the proxy. (Solo mining Sha-256 altcoins not bitcoin I'm not stupid.)

Found my problem, it was the power supply.

The Corsair GS 800 has this annoying attribute where it will go into "power saving" mode randomly and stop supplying power to the cube.

I bought another Corsair HX 850 yesterday and hooked it up this morning and I've had no issues so far.

The GS (Gaming Series) does that?  How annoying... I chose the AX series, also works great and I use the 860 to power two cubes.  Glad you figured it out.

[dresdenreader]

DNS doesn't matter if your using IP addresses, nor does the gateway if your using a local net proxy.  

You seem "in the know".

So far, I've only been able to solo mine other SHA-256 coins with a cube by using BFG Miner and the --http-port #### option.

Is it even possible to use stratum proxy for solo mining?

Also, I've tried just using the cube by itself but it won't communicate with the wallet by setting the "Pool ports" to the rpcport in the wallet .conf file. Any suggestions? (I've probably asked this question about 3-5 times on this thread and once in its own thread, but people just said "point the cube at the wallet" which obviously so far has not worked.)

[Shaker242]

DNS doesn't matter if your using IP addresses, nor does the gateway if your using a local net proxy.  

You seem "in the know".

So far, I've only been able to solo mine other SHA-256 coins with a cube by using BFG Miner and the --http-port #### option.

Is it even possible to use stratum proxy for solo mining?

Also, I've tried just using the cube by itself but it won't communicate with the wallet by setting the "Pool ports" to the rpcport in the wallet .conf file. Any suggestions? (I've probably asked this question about 3-5 times on this thread and once in its own thread, but people just said "point the cube at the wallet" which obviously so far has not worked.)

Cube's need a stratum proxy since they use the "get work" protocol; my understanding is... a stratum proxy is only used for pooled mining.  They don't link to your wallet, you register your wallet address as the "send to, pay to, or something..." so that when you pool mine and get to a specific threshold, say 1.0 bitcoin, it automatically sends it to your registered wallet address.  Solo mining is a little impractical unless you invested in a Neptune (or a few of them).  I'd recommend you look for a pool that you'd like to join.  Some of the popular ones are Slush's pool; which you need a stratum proxy with... or Eligius's pool; which you can mine direct using "GBT Host: gbt.mining.eligius.st Port: 9337".

Eligius has a great graph that shows your effort via a "Hash Graph": I only used it for testing...

http://s27.postimg.org/knao4halv/0_00480130_BTC_1_Gw_Zsad2r_WSygov7wk4_DGL3u_Ta_Uf_Yi4.png

Here is an example of Slush's pool:

http://s27.postimg.org/xlp1revhv/My_account_mining_bitcoin_cz_6.png

Here's some pools you can research:
https://en.bitcoin.it/wiki/Comparison_of_mining_pools

[dresdenreader]

DNS doesn't matter if your using IP addresses, nor does the gateway if your using a local net proxy.  

You seem "in the know".

So far, I've only been able to solo mine other SHA-256 coins with a cube by using BFG Miner and the --http-port #### option.

Is it even possible to use stratum proxy for solo mining?

Also, I've tried just using the cube by itself but it won't communicate with the wallet by setting the "Pool ports" to the rpcport in the wallet .conf file. Any suggestions? (I've probably asked this question about 3-5 times on this thread and once in its own thread, but people just said "point the cube at the wallet" which obviously so far has not worked.)

Cube's need a stratum proxy since they use the "get work" protocol; my understanding is... a stratum proxy is only used for pooled mining.  They don't link to your wallet, you register your wallet address as the "send to, pay to, or something..." so that when you pool mine and get to a specific threshold, say 1.0 bitcoin, it automatically sends it to your registered wallet address.  Solo mining is a little impractical unless you invested in a Neptune (or a few of them).  I'd recommend you look for a pool that you'd like to join.  Some of the popular ones are Slush's pool; which you need a stratum proxy with... or Eligius's pool; which you can mine direct using "GBT Host: gbt.mining.eligius.st Port: 9337".

Eligius has a great graph that shows your effort via a "Hash Graph".

Here is an example of Slush's pool:



Here's some pools you can research:
https://en.bitcoin.it/wiki/Comparison_of_mining_pools

I think you misunderstood my question

solo mine other SHA-256

I'm not trying to solo mine bitcoin. I'm trying to solo mine other coins like Tigercoin or Zetacoin or something like that.

Do we know how to get a cube to solo mine something like Zetacoin without using BFG Miner?

[Shaker242]

I think you misunderstood my question

solo mine other SHA-256

I'm not trying to solo mine bitcoin. I'm trying to solo mine other coins like Tigercoin or Zetacoin or something like that.

Do we know how to get a cube to solo mine something like Zetacoin without using BFG Miner?

Ah, yes... sorry.  I only deal in Bitcoin (ASIC) and Litecoin (GPU) mining.