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

[batt01]

I need help guys. I have one cube Im trying to connect to btcguild or ghash. Here are my settings. Pool address has to bee the IP of the PC running the proxy. I am not sure of your Default gateway address. But if you can get to the miner web page, it should be fine. Just make a few changes nad you should be running.

Mining Proxy:
cd C:\Program Files (x86)\Stratum Proxy
mining_proxy.exe -o stratum.btcguild.com

Cube Page:
IP: 192.168.1.201
Mask: 255.255.255.0
Gateway: 0.0.0.0
Web Port: 8000
Primary DNS: 192.168.0.14
Secondary DNS: 8.8.8.8
Pool Ports: 3333,3333
Pool addresses: 192.168.0.14,192.168.0.14
Miner user:pass abc.123,abc.123

Im sure its something simple i just cant figure it out!

I have my cube mining on ghash.io. Your default gateway can not be blank, if blank you have no connection to the internet. Your Pool port setting is likely wrong. Change to match my example. Primary DNS needs to be your router IP, or use a public DNS from somewhere. You have it the same as your Proxy, wont work.

My default gateway is 192.168.1.1
Cube Page:
IP: 192.168.1.111
Mask: 255.255.255.0
Gateway: 192.168.1.1 Make this your router ip
Web Port: 8000
Primary DNS: 192.168.1.1 Make it the same as your router IP.
Secondary DNS: 8.8.8.8
Pool Ports: 3332,3332 Use these Pool Ports, your stratum proxy default listening ports.
Pool addresses: 192.168.1.127,192.168.1.127 IP of the PC running your Proxy Server
Miner user:pass user.Cube1:123,user:Cube1:123

This is what is in my .bat file.\Cube\mining_proxy.exe -o nl1.ghash.io -p 3334
Here a a .bat that should work for you.
C:\Program Files (x86)\Stratum Proxy mining_proxy.exe -o nl1.ghash.io -p 3334

send me a  mbtc is you find this works. 195JqXiE4X9uJ9UG3Vocix2Vh97Rz6CKcz

[1715498759]

1715498759

[1715498759]

1715498759

[1715498759]

1715498759

[jps44]

Yes, the replacement is a 3 pin 120mm fan.
It is having trouble initializing. Sometimes it makes it to the network stage and I can get the web page up before it shuts off. Most times it shuts off before the network port shows activity. I've tried different power supplies and fans. Seems like something with the device itself has gone wrong.

[sidehack]

Fuse is good? Does the relay click over?

[aznatama]

So after 5 hrs, my "overclocked" cub has climbed to 33.9 gh/s (87.21% efficiency), while my standard/low clocked cube is operating at 31.6 gh/s (96.14% efficiency).

Any idea why it won't get anywhere near the 38 gh/s??  voltages all test out correctly too.  Can Cubes be too cold?  the outer case is cold, and the air exiting it is pretty cool as well (feeding it freezing air from a window).

[jps44]

Fuse is good. I'm not sure what the relay is.
If the relay is the clicking noise then yes, it clicks on then after a few seconds it clicks off. The red status led and the green PWR turn off with it.
The strange thing is the variation in the time that it stays on for.

[glassbat]

I need help guys. I have one cube Im trying to connect to btcguild or ghash. Here are my settings. Pool address has to bee the IP of the PC running the proxy. I am not sure of your Default gateway address. But if you can get to the miner web page, it should be fine. Just make a few changes nad you should be running.

Mining Proxy:
cd C:\Program Files (x86)\Stratum Proxy
mining_proxy.exe -o stratum.btcguild.com

Cube Page:
IP: 192.168.1.201
Mask: 255.255.255.0
Gateway: 0.0.0.0
Web Port: 8000
Primary DNS: 192.168.0.14
Secondary DNS: 8.8.8.8
Pool Ports: 3333,3333
Pool addresses: 192.168.0.14,192.168.0.14
Miner user:pass abc.123,abc.123

Im sure its something simple i just cant figure it out!

I have my cube mining on ghash.io. Your default gateway can not be blank, if blank you have no connection to the internet. Your Pool port setting is likely wrong. Change to match my example. Primary DNS needs to be your router IP, or use a public DNS from somewhere. You have it the same as your Proxy, wont work.

My default gateway is 192.168.1.1
Cube Page:
IP: 192.168.1.111
Mask: 255.255.255.0
Gateway: 192.168.1.1 Make this your router ip
Web Port: 8000
Primary DNS: 192.168.1.1 Make it the same as your router IP.
Secondary DNS: 8.8.8.8
Pool Ports: 3332,3332 Use these Pool Ports, your stratum proxy default listening ports.
Pool addresses: 192.168.1.127,192.168.1.127 IP of the PC running your Proxy Server
Miner user:pass user.Cube1:123,user:Cube1:123

This is what is in my .bat file.\Cube\mining_proxy.exe -o nl1.ghash.io -p 3334
Here a a .bat that should work for you.
C:\Program Files (x86)\Stratum Proxy mining_proxy.exe -o nl1.ghash.io -p 3334

send me a  mbtc is you find this works. 195JqXiE4X9uJ9UG3Vocix2Vh97Rz6CKcz

I will gladly tip you but unfortunately that did not work...I feel it was the closest Ive been so far thought thanks for the attempt I will continue to tinker..driving me crazy
if you can think of anything else i will gladly tip ill upload an image of the proxy screen tommorow

[sidehack]

Try this:

Cube Page:
IP: 192.168.0.201
Mask: 255.255.255.0
Gateway: 192.168.0.1
Web Port: 8000
Primary DNS: 192.168.0.1
Secondary DNS: 8.8.8.8
Pool Ports: 8332,8332
Pool addresses: 192.168.0.14,192.168.0.14
Miner user:pass :,???:

command prompt:
>mining_proxy.exe -o stratum.btcguild.com -p 3333


These settings are based on your page, and assuming:
   a) your network is on 192.168.0.x subnet
   b) your computer running mining_proxy.exe is at IP 192.168.0.14

Your user:pass on the config page need to be formatted correctly; make sure to repeat it, with a comma inbetween.

[wedgy2k]

wedgy2k

Thank you.

Name   ID   Temp   MH/s   Accept   Reject   Error   Utility   Last Share
PXY   0   N/A   33118.139   43   11 [24.5%]   69 [4.58%]   13.844   09:37:15
Totals   1      33118.139   43   11 [24.5%]   69 [4.58%]   13.844      

Happy happy Joy joy

Hi Mogrith
Glad its working, and thank you for the tip
(Was not necessary or expected, but thank you - cool vanity address to know it came from you  )

[addzz]

I have an all X problem which I'm assuming is power related.

At first it was hashing away nicely for about 8 hours... then it stopped.  After restarting, and then doing a full factory reset.... it will only run for about 1 hr before stopping.

power supply is a new Corsair CX750M with nothing else plugged in.  Before I ran the cube on it... it was powering a 49 port USB erupter setup with no issues.  :/

I will bet your all xs problem is due to one flaky board.

Try running one board alone and then add back one by one to identify the offending board.

I'm doing this now. Thanks for the suggestion.  So far, 2 boards running with no problems.  I'm adding a new board every 2 hours.  I did notice when I took the boards out that a few of them had loose heat sinks.  Hopefully tightening them will solve all my issues!

[Damnsammit]

Well I can't seem to access the Cube connection page.

Got the thing plugged in and powered up, but when I try to go to "http://192.168.1.254:8000/"

I get his error:

Unable to connect

Firefox can't establish a connection to the server at 192.168.1.254:8000.

    The site could be temporarily unavailable or too busy. Try again in a few moments.
    If you are unable to load any pages, check your computer's network connection.
    If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

[Singlebyte]

Try to ping the cube.  It sounds like you might not have network or subnet set properly.  Possibly an ip conflict.

[Damnsammit]

Try to ping the cube.  It sounds like you might not have network or subnet set properly.  Possibly an ip conflict.

Yeah, I think i found the issue.  My stupid router's IP is 192.168.1.254... unfortunately I am not seeing any way to change the IP for a U-Verse router.

Guess I will just auction this thing off...

[sidehack]

Do you have a crossover cable? Do you have an ethernet switch that is not currently in use?

Unplug your computer and the Cube from the network and plug them together, either with a crossover cable directly or through an unpurposed network switch. You may need to set your machine to a static IP in the 192.168.1.x family. Once done with that, you should be able to talk to the hardware directly. Change the IP address on the Cube to anything else in the 192.168.1.x family (that you aren't already using on another machine) and plug it back into your network/router.

[Damnsammit]

I think I got the cube set up, now working on getting a pool set up.

Had a hard time figuring out where the hell to change the Uverse Router's IP address but I got it squared away... now setting up DVC and NMC for some merged mining (hopefully)

[Miner_2049er]

I'm sure this has been mentioned before, but I have found it easier to
reconfigure your subnet mask from 255.255.255.0 to 255.255.254.0,
which makes accessing the blade or cube default configuration page
much easier. Change the subnet mask on your router once and from then on you can
reach the default page from any browser on your local network, as well as everything else on
your local net, blades, cubes, proxies... Working flawlessly for me for a week or two.

-Mark

[Singlebyte]

I'm sure this has been mentioned before, but I have found it easier to
reconfigure your subnet mask from 255.255.255.0 to 255.255.254.0,
which makes accessing the blade or cube default configuration page
much easier. Change the subnet mask on your router once and from then on you can
reach the default page from any browser on your local network, as well as everything else on
your local net, blades, cubes, proxies... Working flawlessly for me for a week or two.

-Mark

Nice tip....was unaware off this! 

Thanks

[Damnsammit]

Well just swapped out PSUs, but apparently still can't get it to connect to BTC Guild.  It appears that it is restarting every couple of minutes.  It was shutting down completely with my 630W PSU, so I swapped it out to an 850W Antec and it is still clearly resetting every minute or two.   Tried Slush's pool but it kept timing out on me... mining can be so very exhausting...

Was hoping to have gotten it earlier in the day, but I am tired and ready to relax and watch some Football.

Here is what the proxy miner is showing:


Here is the settings on the Cube Miner page:


Thanks for all of the help so far, and hopefully I can get it working tomorrow

[Zoella]

I'm sure this has been mentioned before, but I have found it easier to
reconfigure your subnet mask from 255.255.255.0 to 255.255.254.0,
which makes accessing the blade or cube default configuration page
much easier. Change the subnet mask on your router once and from then on you can
reach the default page from any browser on your local network, as well as everything else on
your local net, blades, cubes, proxies... Working flawlessly for me for a week or two.

-Mark

There is no reason to reconfigure your network because of one device.  If your current network is not in the same range, just plug a PC directly into the cube and change the cube's network settings.

[batt01]

Well just swapped out PSUs, but apparently still can't get it to connect to BTC Guild.  It appears that it is restarting every couple of minutes.  It was shutting down completely with my 630W PSU, so I swapped it out to an 850W Antec and it is still clearly resetting every minute or two.   Tried Slush's pool but it kept timing out on me... mining can be so very exhausting...

Was hoping to have gotten it earlier in the day, but I am tired and ready to relax and watch some Football.

Here is what the proxy miner is showing:


Here is the settings on the Cube Miner page:


Thanks for all of the help so far, and hopefully I can get it working tomorrow

No default gateway. Try setting your default gateway to your router's IP. In your case it looks like 192.168.1.1 would do the trick. For Pool Ports 8332,8332 works for me. If you looks at your proxy output, you will note, it says it listening on Port 8332 and is connected to btc guild on 3333. So you are good to go on the proxy side of thing. Just need to get the cube talking to the proxy. In your pool setting on the cube I dont think that + belongs there. You might consider putting a comma there.

[colemab]

For the past few days I've been using bfgminer as a proxy connecting to ghash.io and I've only been getting 32-33gh/s on high.  Today I switched over to slush's pool using his proxy and I'm getting 37gh/s+ no problem.  (speeds are based on miner not pool)

Why is this?

While I've not used BFG extensively, I do think the barebones proxy is simply more efficient.

First off, thanks to everyone for their suggestions and to Dogie for this great guide!

I decided to take my cube and psu to a different friend's house.  It works perfectly there!  It is like Dogie said,  "mysterious network topology" was my issue.  My friend is going to host my cube until I figure this out.  Thanks again.

One thing you can check is any phones connected to your wifi. Not sure how they interfere, but a few users of V1 blades found phones [android?] were preventing it working correctly.

Not sure if my phone's wifi was the case, but I turned it off and got 3 cubes working after messing with the settings and proxy for hours. I am not gonna turn it on to test since I finally got started hashing. Phone could just be a coincidence though...

edit: phone is an android and my problem was with the cubes resetting every ~2min

Thank you!!!  As soon as my WiFi was turned off on my droid, both units started going full steam at the proxy!  Been driving me crazy for 4 days.