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

[Shaker242]

...

https://i.imgur.com/KhlZ8GN.jpg?2

-herener

That's some setup, and here I was excited about having 3 Cubes...

[stewdk]

EDIT: Okay, seems to be working, only thing is the --help option didn't work out, window just opened then closed immediately when I did that. I added the quiet switch, seems to cut down the messaging. Thanks again.

The --help option did work, it's just that the command quit after it was done printing all the info.  Try running this particular command in an actual command prompt window instead of a batch file, or adding "pause" at the end of the batch file.

Everybody asking about PSUs, please have a read through this thread.  I have already written what PSUs did and didn't work for me and so have others.  Dogie, how's that table of PSUs in the OP coming along?

[Shaker242]

I've seen a couple posts about stratum proxies only being used for 1 to 2 cubes, but after monitoring my slush proxy while a single cube is running at 31Ghash/s... I'm seeing a very small load, thus one could reason that I should be able to run a lot more cubes through it.  I just ordered a couple more, so when they get in... I'll update this with the proxies performance.  Based on the numbers I'm seeing, there is no reason the proxies couldn't handle quite a few cubes. 

* I am switching everything over from monitoring on SSH to SNMP; so please ignore the "?" on physical memory... the SSH Meminfo 3 shows that only 25% of 1GB is being utilized currently.  Load average is < 1, CPU utilization is only 8% and network traffic is only 261kbits/sec (that is 0.03 MB).

http://s28.postimg.org/xcpema1ml/bcproxy1.png

Shaker

[qwertyasdfg]

Evening All,

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.

I am currently mining on Slush's pool and another pool using a windows 7 64bit laptop as a proxy machine and am using mining_proxy.exe in order to do so, if I want to mine on the other pool I just open up the command prompt, navigate to the mining proxy directory and execute the following command
mining_proxy.exe -o (host) -p (port)

My cube is setup with the standard settings with the ports being 8332, 8332, pool address being the IP address of my proxy machine and the username and password of my pool worker credentials.

I have tried to use cgminer and bfg miner on numerous occasions but have been unsuccessful in making them work for me.

Yesterday I downloaded the latest cgminer 3.90 but after entering my pool address:port and leaving the username and password blank and hitting enter, the program would encounter a problem and shutdown, I tried again but this time I populated the username and password fields but I encountered the same problem.

bfg miner seems to get me to a page where I can start tinkering with some settings but always says that no devices were found, once I've managed to get it connected to a pool I think and it said something along the lines of "pool is hiding blocks", or something along those lines.

So now, as proxy miner seems to be the only one working for me, is their any way for me to set it up to achieve my purpose?

Also what does diff 64, 128 and 256 mean? The other pool that I am on offers me various different ports to choose from with the options of diff 64, 128 or 256.

Thanks in advance for your time and help.

Can anyone offer me some advise on any of the above mentioned?

[Shaker242]

Corsair 850W

All three of them just shut off after a couple seconds. Is there anything else I can try before buying another PSU? I'm kind of tired of buying new PSUs for this thing.

The Corsairs sometimes have a low power mode where the fan stops spinning... you can test your power supply and do the paper clip method here: http://www.corsair.com/us/blog/testing-your-corsair-power-supply/

I use this one "http://www.amazon.com/Corsair-Professional-Digital-Platinum-AX860i/dp/B00A0HZNDW/ref=lp_1161760_1_8?s=pc&ie=UTF8&qid=1389186412&sr=1-8" to power two cubes.

[stewdk]

I've seen a couple posts about stratum proxies only being used for 1 to 2 cubes, but after monitoring my slush proxy while a single cube is running at 31Ghash/s... I'm seeing a very small load, thus one could reason that I should be able to run a lot more cubes through it.  I just ordered a couple more, so when they get in... I'll update this with the proxies performance.  Based on the numbers I'm seeing, there is no reason the proxies couldn't handle quite a few cubes.  

* I am switching everything over from monitoring on SSH to SNMP; so please ignore the "?" on physical memory... the SSH Meminfo 3 shows that only 25% of 1GB is being utilized currently.  Load average is < 1, CPU utilization is only 8% and network traffic is only 261kbits/sec (that is 0.03 MB).

The problem with running multiple cubes through a single instance of slush's proxy isn't bandwidth, or even CPU time necessarily (unless you're running it on a raspberry pi).  It's when you have the proxy pointed to a pool with vardiff (like slush's pool) and each worker gets assigned a different share difficulty.  This happens even if each worker has the same hashing power.  The proxy gets confused by different share difficulties per worker (software bug) and doesn't submit any shares with a difficulty lower than the difficulty of the worker with the highest share difficulty assigned by the pool, even if that lower difficulty share is valid for that particular worker.  This may seem like a corner case, but it most definitely results in lost/unsubmitted shares, which directly affects your worker hashrate and profits.  twib2 reported a 5% increase in total hashrate when switching 5 cubes from a single proxy to a proxy for each cube.

[Shaker242]

I've seen a couple posts about stratum proxies only being used for 1 to 2 cubes, but after monitoring my slush proxy while a single cube is running at 31Ghash/s... I'm seeing a very small load, thus one could reason that I should be able to run a lot more cubes through it.  I just ordered a couple more, so when they get in... I'll update this with the proxies performance.  Based on the numbers I'm seeing, there is no reason the proxies couldn't handle quite a few cubes. 

* I am switching everything over from monitoring on SSH to SNMP; so please ignore the "?" on physical memory... the SSH Meminfo 3 shows that only 25% of 1GB is being utilized currently.  Load average is < 1, CPU utilization is only 8% and network traffic is only 261kbits/sec (that is 0.03 MB).

The problem with running multiple cubes through a single instance of slush's proxy isn't bandwidth, or even CPU time necessarily (unless you're running it on a raspberry pi).  It's when you have the proxy pointed to a pool with vardiff (like slush's pool) and each worker gets assigned a different share difficulty.  This happens even if each worker has the same hashing power.  The proxy gets confused by different share difficulties per worker (software bug) and doesn't submit any shares with a difficulty lower than the difficulty of the worker with the highest share difficulty assigned by the pool, even if that lower difficulty share is valid for that particular worker.  This may seem like a corner case, but it most definitely results in lost/unsubmitted shares, which directly affects your worker hashrate and profits.  twib2 reported a 5% increase in total hashrate when switching 5 cubes from a single proxy to a proxy for each cube.

Now that does put things in a different light, thank you.  The software's punitive features seem like a pain then; has anyone evaluated running multiple instances of slush's proxy but on different ports... like the --gp 8332, --gp 8333 etc?  Or do you believe this would likely not  provide better results?  I'm curious to try spinning up multiple instances in this case, along with splitting out the workers (obviously) would be a 'work around'?  It's not really a big deal, since I'm running VM's anyway... but I'd like to have a systems that's efficient.

[Defender666]

I've got my block errupter, set my Mining Proxy. However the Problem is the device restarts every 2 min. I geht very lo Hashrate of 200mhs or so...i trief different power supplies but no Luck.

All cards are correctly installed and show in the miner config with "  o "

[otsaku]

Problem solved!!

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: 313 463 313 363 294 375 294 263 388 338 357 457 388 338 231 375
M_17-32: 338 319 175 313 319 275 325 288 300 288 275 350 294 313 350 319
M_33-48: 313 281 269 331 238 331 357 369 263 281 463 319 338 319 212 482
M_49-64: 269 413 482 369 319 425 231 319 344 212 363 244 432 325 225 212
M_65-80: 413 194 212 388 400 425 225 219 281 363 206 231 144 206 056 031
M_81-96: 025 000 068 043 000 012 000 000 006 000 000 000 000 000 000 000
Jobs:0000003975 Accepted:0000003980 Rejected:0000000005 (0:5) F1 F2 F3
MHS:24930 Utility:341 Efficieny:100.12%

Though some of the chips are showing 000 I'm getting 31ghs in the pool!

Still using the stratum proxy, couldn't get the cube to connect to bfgminer on the RPi.

Final solution for me is as follows:

Gateway set to 127.0.0.0
DNS set to external as provided by my isp
Switched from a 550 corsair to the cx 750m
I was using to cables from the cx750m - two separate but changed to using two plugs on the same cable.

Thanks for everybody's help and to Dogie for the thread.

[Shaker242]

I've got my block errupter, set my Mining Proxy. However the Problem is the device restarts every 2 min. I geht very lo Hashrate of 200mhs or so...i trief different power supplies but no Luck.

All cards are correctly installed and show in the miner config with "  o "

You've come to the right thread... I had issues too, my saga started at post #725.  However, I'd recommend going through the thread completely to rule out as much as you can. (not sure from your message if you have yet or not)

[stewdk]

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.
Also, it's -gp or --getwork-port, not --gp.

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.

[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.

Thanks, and I like it.  However, it also appears that your directing to two different pools - did you try proxy2.bat using stratum.bitcoin.cz as well, but with a --getwork-port of 8331 so that each cube would connect to a different proxy port?  If I misunderstood, sorry.  Right now, I'm only using slush's pool, I can use someone else too... but call me lazy, I'd like to visit as few web pages as possible

[stewdk]

... it also appears that your directing to two different pools - did you try proxy2.bat using stratum.bitcoin.cz as well, but with a --getwork-port of 8331 so that each cube would connect to a different proxy port?

Yes, see post #805 https://bitcointalk.org/index.php?topic=352658.msg4378157#msg4378157

[Shaker242]

... it also appears that your directing to two different pools - did you try proxy2.bat using stratum.bitcoin.cz as well, but with a --getwork-port of 8331 so that each cube would connect to a different proxy port?

Yes, see post #805 https://bitcointalk.org/index.php?topic=352658.msg4378157#msg4378157

Great!  I'll do that, thanks again!

[Defender666]

I've got my block errupter, set my Mining Proxy. However the Problem is the device restarts every 2 min. I geht very lo Hashrate of 200mhs or so...i trief different power supplies but no Luck.

All cards are correctly installed and show in the miner config with "  o "

You've come to the right thread... I had issues too, my saga started at post #725.  However, I'd recommend going through the thread completely to rule out as much as you can. (not sure from your message if you have yet or not)

Hi Shaker242, I read through your post but my problem is not only slow mining it simply does reboot all the time. After 2 min. reboot.Actually you do not tell how you solved the problem.

The LED stays red on some powersupply. On the other it goes off but also after 2 min restart it connects to my windows binary proxy. And also I tried to compile the slush proxy on ubuntu which connects now the same way, but no luck getting this brick to mine.

[Damnsammit]

Hi Shaker242, I read through your post but my problem is not only slow mining it simply does reboot all the time. After 2 min. reboot. Actually you do not tell how you solved the problem.

The LED stays red on some powersupply. On the other it goes off but also after 2 min restart it connects to my windows binary proxy. And also I tried to compile the slush proxy on ubuntu which connects now the same way, but no luck getting this brick to mine.

What PSU are you using?  Everyone that has had this issue seems to have resolved it by getting a new PSU.

12V @ 25A seems to be the minimum requirement as far as I can gather.

Edit:  Also be sure to take off the case and ensure all heatsinks are screwed on properly and all boards are seated correctly.

[Defender666]

Tried different PSUs from 500-650-700 Watt

Tried brand new Cougar Power X 700 Watt. Id does not even start with this one. Just the fan turns shortly then off.



I now ordered a new one: Corsair CX750

Hope this will work.

[Damnsammit]

Tried different PSUs from 500-650-700 Watt

Tried brand new Cougar Power X 700 Watt. Id does not even start with this one. Just the fan turns shortly then off.



I now ordered a new one: Corsair CX750

Hope this will work.

Well, based off of Newegg(http://www.newegg.com/Product/Product.aspx?Item=N82E16817553002), it certainly looks like that PSU should get the job done. 

+3.3V@24A, +5V@20A, +12V1@30A, +12V2@30A, -12V@0.3A, +5VSB@3.0A

Have you already removed the main board and made sure all of the blades and heatsinks are secured?

[Defender666]

yes the screws are well tied. Two where lying in the case when the packaged arrived. This was the first thing I did prior to booting up the device.

[Defender666]

However the 500Watt and 650 Watt PSU can start the cube.

The 500Watt the LED stays red.
The 650Watt the LED goes off and it seems to start mining but also after exactly 2 min it reboots.