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

[sidehack]

Did you pull the cards out and make sure all the heatsinks were tight? In Blades, low efficiency is usually due to chips overheating from poor heatsink contact, and these Cubes are notorious for loose screws upon delivery.

[Damnsammit]

Did you pull the cards out and make sure all the heatsinks were tight? In Blades, low efficiency is usually due to chips overheating from poor heatsink contact, and these Cubes are notorious for loose screws upon delivery.

Yeah, mine had 3 screws loose.  Just undo the front/back of the Cube, disconnect the fan, and then slide the main board out to check them all. 

[J_Dubbs]

Having difficulty getting my new cubes set up.  I am fairly confident I have everything set correctly but it is not connecting to my proxy and not hashing. 

What do the LEDs on the back mean?  I have a solid RED one for status. (I assume it just means it is offline and not working)

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O O
ASIC_81-96: O O O O O O O O O O O O O O O O

M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000000000 Accepted:0000000000 Rejected:0000000002 (0:0) F1 F2 F3

MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,00m,51s
Current pool: 192.168.1.129 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive

IP   192.168.1.200
Mask   255.255.255.0
Gateway   192.168.1.1 (have also tried 0.0.0.0)
WEB Port   8000
Primary DNS   192.168.1.1
Secondary DNS   8.8.8.8
Pool ports   8332,8332
Pool addresses   192.168.1.129,192.168.1.129
Miners user:pass   asicminer_test:x,asicminer_test:x


I am just using default setup right now, but I did change ports to 8332 because the proxy showed this is the port it is listening to.

I have have a 1000W 80 plus gold power supply - Plenty of juice and nothing else on it.

I have turned off all software firewalls on proxy host and in router.  Also disabled antivirus settings.

I am not using WIFI...everything is over cat5.

I can ping cube & proxy machine both directions

I received two cubes, and have tried both.  And only trying to get one going right now on power supply.  They both seem to be properly functioning.  Same lights/indicators

I can log into web interface and make changes with no problem

I quickly tried "getwork" on OZ pool to bypass stratum proxy, but no luck either.  (But I was pretty hammered/frustrated by now!)

Ok guys, any ideas???

I've been seeing a lot of people setting their DNS to the same thing as the Gateway and setting the secondary DNS to 8.8.8.8.

Try using Open DNS as someone suggested earlier, I did this and it's been working fantastically:
Primary DNS   208.67.220.220
Secondary DNS   208.67.222.222

Run ipconfig on the machine running the miningproxy.exe just to make 100% sure that your IPv4 Address is exactly the same as what you're setting both of your pool addresses to.

Also, your miningproxy port does not have to be identical to the pool ports on the cube. I'm running 8332,8332 on both of my cubes with the following as a miningproxy.exe batch file and its running just fine:
mining_proxy.exe -o nl1.ghash.io -p 3334
Insert whatever pool above you're using.

For ozcoin try this:

mining_proxy.exe -o stratum.ozco.in -p 3333

I have primary and secondary set to 8.8.8.8 and everything works, why is that?

[bitcoiner49er]

Have you tried a separate router apart from the Uverse gateway module? Easier to control and configure.

[qwertyasdfg]

Did you pull the cards out and make sure all the heatsinks were tight? In Blades, low efficiency is usually due to chips overheating from poor heatsink contact, and these Cubes are notorious for loose screws upon delivery.

Right, I got no more X's and efficiency up to 50% but declining
MHS 04764

I unscrewed both sides of the cube but found it rather tight to push the board out, so I just made sure that the cards were properly slotted in place, they were not screwed to the main board and seemed to be wedged in place by the groves aligned at the top of the cubes structure, I just made sure these lined up correctly and put the device back together.

Any other advice on how I can get the optimum performance from this unit?

[babaji.ca]

if the cards are not in the machined aluminium grooves at the top of the unit, then the board assembly and all the attached cards will not slide easily. What helps tons is if you can push the 'tops' of all the cards evenly at the same time (an in same direction , duh) as you push the motherboard. It should slide out nicely after that.

[J_Dubbs]

if the cards are not in the machined aluminium grooves at the top of the unit, then the board assembly and all the attached cards will not slide easily. What helps tons is if you can push the 'tops' of all the cards evenly at the same time (an in same direction , duh) as you push the motherboard. It should slide out nicely after that.

Mine was majorly jammed off track, had to really push it quite a bit! Got it out and tightened everything, lined up correctly it's a smooth slide in (bow chica wow wow, couldn't not add that in).

[sidehack]

I'd pull the whole assembly all the way out and make sure the heatsink screws are tight, then reassemble it making sure to keep the boards in the slots. Make sure not to constrict airflow in or out, make sure you have a high-quality power supply and thick cables so you get good voltage/current at the unit.

[qwertyasdfg]

Thanks for your advice and suggestions, will give them a go!

[wedgy2k]

I have primary and secondary set to 8.8.8.8 and everything works, why is that?

Devices on the same subnet (192.168.x.x/24) will resolve via broadcast provided no firewall or other blocking software / device is in the way

The gateway is where unresolved destinations are routed and the DNS resolves the IP addresses to NAMES

so a typical home setup will looks like
IP   192.168.1.200 --> cube IP Address
Mask   255.255.255.0 --> the /24 subnet mask
Gateway   192.168.1.1 --> Home router address
WEB Port   8000 --> http://192.168.1.200:8000 brings up the CUBE's management web page from your PC / Laptop
Primary DNS   192.168.1.1 --> Home router address
Secondary DNS   8.8.8.8 --> Will only use this if the Primary DNS does not respond - but cannot be blank
Pool ports   8332,8332 --> This is the port your Stratum Proxy is accepting connections (Listening) on
Pool addresses   192.168.1.129,192.168.1.129 --> IP Address of the device running the Stratum Proxy
Miners user:pass   asicminer_test:x,asicminer_test:x --> for BFGMiner Proxy these are fine, for SLUSH Proxy I believe you need your pool credentials (!Can someone confirm this please as I've not used SLUSH Proxy!)

Hope this helps.

[sidehack]

That's all accurate information. Slush proxy does route multiple workers, so you need your worker credentials on the Cube config. You'd also need this (as well as an accurate DNS and Gateway) if you wanted to connect directly to a pool's getwork node via internet.

[Apteryx]

@ Damnsammit

a) 192.168.1.254
b) Cube Config:
IP    192.168.1.201
Mask   255.255.255.0
Gateway   0.0.0.0          <--- should this not be the same as the Primary DNS, both pointing to the router??
WEB Port   8000
Primary DNS   192.168.1.254
Secondary DNS   8.8.8.8
Pool ports   8332, 8332
Pool addresses   192.168.1.76, 192.168.1.76
Miners user:pass   Damnsammit:x, Damnsammit:x
c) 192.168.1.76
d) C:\proxyminer\mining_proxy.exe -o stratum.bitcoin.cz -p 3333

[Damnsammit]

@ Damnsammit

a) 192.168.1.254
b) Cube Config:
IP    192.168.1.201
Mask   255.255.255.0
Gateway   0.0.0.0          <--- should this not be the same as the Primary DNS, both pointing to the router??
WEB Port   8000
Primary DNS   192.168.1.254
Secondary DNS   8.8.8.8
Pool ports   8332, 8332
Pool addresses   192.168.1.76, 192.168.1.76
Miners user:pass   Damnsammit:x, Damnsammit:x
c) 192.168.1.76
d) C:\proxyminer\mining_proxy.exe -o stratum.bitcoin.cz -p 3333

Thank you so much!  I was having the hardest time with this...

Went through about 20 different settings to get it set up.  I have all of the pictures now and will create a new post for my solution with UVerse and post it here in case anyone else is having the same problem.  It all has to do with the default IP for the UVerse router being 192.168.1.254 though, methinks.

[juggalodarkclow]

I'm a little late to the game but thanks for the write-up Dogie!!

[Damnsammit]

Here is my solution for that stupid UVerse Router.  I don't think many will have the issue, but it made me want to break things, so hopefully it helps at least one person out

https://bitcointalk.org/index.php?topic=375093.0

[Swimmer63]

PSU issue with the Cubes.  Hopefully someone has insight.

I have three cubes and bought a new Seasonic 1050 to run the three of them.
Finally got around to plugging it all in today (I had them running on a 750(2) and old 650(1).
The seasonic is totally modular so only plugged in the motherboard cable (with an ATX switch) and 3 PCI-E cables each with 2x 6+2 plugs.  Total of 6 cables/plugs.
I plugged each on in, 2 per Cube.
Start up the PSU and all three cubes go on for 3 seconds and then the psu shuts down.
Messed with it some more, same result.  I unplugged one of the Cubes and it still did it.
It only worked with one Cube.

I then took the psu to another miner that required 6x 6 pin PCI-e cables.  It worked fine and is still going.

Any idea why it's shutting down with the Cubes?

[sidehack]

Capacitor trick. I bet they're all kicking on at the same time and the sudden current draw is briefly undervolting/overcurrenting your supply.

One thing you might try, is plugging one in fully and plugging the other two in with just the right 6pin. Then plug the left 6pin on one and wait for it to fully power up, then plug the left 6pin in the third. I think that might help?

[Swimmer63]

Capacitor trick. I bet they're all kicking on at the same time and the sudden current draw is briefly undervolting/overcurrenting your supply.

One thing you might try, is plugging one in fully and plugging the other two in with just the right 6pin. Then plug the left 6pin on one and wait for it to fully power up, then plug the left 6pin in the third. I think that might help?

Thanks Sidehack.  I'll give it a shot.

[J_Dubbs]

I have primary and secondary set to 8.8.8.8 and everything works, why is that?

Devices on the same subnet (192.168.x.x/24) will resolve via broadcast provided no firewall or other blocking software / device is in the way

The gateway is where unresolved destinations are routed and the DNS resolves the IP addresses to NAMES

so a typical home setup will looks like
IP   192.168.1.200 --> cube IP Address
Mask   255.255.255.0 --> the /24 subnet mask
Gateway   192.168.1.1 --> Home router address
WEB Port   8000 --> http://192.168.1.200:8000 brings up the CUBE's management web page from your PC / Laptop
Primary DNS   192.168.1.1 --> Home router address
Secondary DNS   8.8.8.8 --> Will only use this if the Primary DNS does not respond - but cannot be blank
Pool ports   8332,8332 --> This is the port your Stratum Proxy is accepting connections (Listening) on
Pool addresses   192.168.1.129,192.168.1.129 --> IP Address of the device running the Stratum Proxy
Miners user:pass   asicminer_test:x,asicminer_test:x --> for BFGMiner Proxy these are fine, for SLUSH Proxy I believe you need your pool credentials (!Can someone confirm this please as I've not used SLUSH Proxy!)

Hope this helps.

even though it was working fine I decided to put the router IP into my primary DNS as you outlined... seems to be working fine with the change. I don't fully understand it all, but wanted to let you know I gave it a shot and it's working, thanks. Please feel free to give me a "for dummies" version because I am actually interested in understanding it, if possible of course.

[HellDiverUK]

I've been having fun with my Cube.  The CX750 I have (which runs my two V1 Blades fine) won't run the Cube - the Cube shows all X. 

I'm running the Cube at the moment off an old Dell workstation PSU - it runs OK on this at Low speed, but at High it just sits there, eventually reboots and shows all X again.  Though, the Dell PSU only has 18A per rail.

So, I've ordered a few 10000uF caps and PCI-E extension leads, and will make up a 'capacitive leads' and see how that goes with the CX750.

I've also replaced the snow-blower stock fan with a SilentTyphoon 1500rpm unit, which is MUCH quieter and moves more air.