Topic: [Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD] - page 72. (Read 187363 times)

I was thinking the same thing - 648W seems like more than enough power, and I forgot to mention I have it on "low" clock speed as well.

I guess I'll try a more beefy power supply, maybe the 850W from Corsair...

I was thinking the same thing - 648W seems like more than enough power, and I forgot to mention I have it on "low" clock speed as well.

I guess I'll try a more beefy power supply, maybe the 850W from Corsair...

I'm not sure if anyone else is having issues like that, but mine wouldn't work properly with a 630W supply.  It runs flawlessly at 38GH/s ever since I switched to the 850W supply.

Seems like over-kill with that supply for one cube, but maybe the 650W is just not cutting it?  Doesn't make any sense to me. 

My cube and a blade that I have keep restarting every 10 minutes or so. They hash fine during the 10 minutes, but then they just decide to restart. They're not overheating, they just stop getting work for some reason. Anyone know what might be wrong here? .1 BTC bounty if you can please help me fix this

The laptop has 8 GB of RAM. Its a brand new HP Probook running Win7 x64 with nothing else installed (fresh install).

The IP of the machine running the proxy is static (192.168.1.50) and the IP of the miners are static (192.168.1.100 and 192.168.1.101), and there is nothing else on this network. The entire network is just 1 laptop, 2 miners, a small switch (which I tried replacing already to rule that out), and a DSL modem which acts as the router.

Yes, the hardware is rebooting itself, but to answer your question, the proxy does eventually pick it back up and it starts to mine again automatically. But these constant disconnects are keeping my average hash rate much lower than what it should be.

When I run bfgminer I get a strange message which sates "Pool 0 is hiding blocks from us" and then BFGMiner closes. I am running it with these command line switches:
bfgminer.exe --http-port 8332 -o http://stratum.btcguild.com:3333 -u bark0de_proxy -p x

I execute this via a batch file which I run from the same directory as BFGminer.

I reached out to CanaryInTheMine and he told me that the miners are hardcoded to reboot themselves if they stop receiving work for a while. The question is, why do they stop receiving work?

When the miners stop getting work, I check the proxy console and I see that it stops showing the really fast messages that say " Submitting ####### from bark0de_cube accepted" and it only shows messages that say something like "new job #######" i forget what exactly it says, but basically it stops mentioning the ASICs and seems to just show messages that say something to the effect of "I just got another job from the pool and I am waiting for a worker to take this job"


Thanks for your help. I hope someone can help me get to the bottom of this

The IP of the machine running the proxy is static (192.168.1.50) and the IP of the miners are static (192.168.1.100 and 192.168.1.101), and there is nothing else on this network. The entire network is just 1 laptop, 2 miners, a small switch (which I tried replacing already to rule that out), and a DSL modem which acts as the router.

Yes, the hardware is rebooting itself, but to answer your question, the proxy does eventually pick it back up and it starts to mine again automatically. But these constant disconnects are keeping my average hash rate much lower than what it should be.

When I run bfgminer I get a strange message which sates "Pool 0 is hiding blocks from us" and then BFGMiner closes. I am running it with these command line switches:
bfgminer.exe --http-port 8332 -o http://stratum.btcguild.com:3333 -u bark0de_proxy -p x

I execute this via a batch file which I run from the same directory as BFGminer.

I reached out to CanaryInTheMine and he told me that the miners are hardcoded to reboot themselves if they stop receiving work for a while. The question is, why do they stop receiving work?

When the miners stop getting work, I check the proxy console and I see that it stops showing the really fast messages that say " Submitting ####### from bark0de_cube accepted" and it only shows messages that say something like "new job #######" i forget what exactly it says, but basically it stops mentioning the ASICs and seems to just show messages that say something to the effect of "I just got another job from the pool and I am waiting for a worker to take this job"


Thanks for your help. I hope someone can help me get to the bottom of this

Your caps are too small.  2x10000uF at least.  I got 4 of them for less than £5 off eBay.

I've tried with 2x 16v 1000uF and 2 x 16v 2200uF capacitors wedged into PCIe connectors.

Basically, just find a relatively large (at least 1000uF, at least 16V) capacitor or two, and wedge them into the PCIe connectors. Marked lead is the negative, so black wire side; unmarked lead (which should be a bit longer) is positive so yellow wire side. These will charge up to 12V during the time the Cube is initializing, then when the relay clicks over they'll discharge into the Cube to help provide immediate current in assistance to the output capacitors already built into the power supply.
I got two Cubes a while ago, one off a 460W ATX supply with a stupidly strong 12V rail, and the other off a 500W server supply. The ATX would light things up just fine, but the server supply either had too small capacitance, or too much inbetween its caps and the outputs because it dropped out. One 1000uF 16V cap in each 6-pin connector did the trick just fine, and others have reported similar results.

You think this might be a issue where I need to take time to take it apart and reseat and tighten everything down ? Or just bad chips? running off a Corsair TX850M

http://i40.tinypic.com/2h73qr6.png

Unless something has changed, BFG win64 doesn't have the proxy built in.

BLOCK ERUPTER BLADE
-------------------
Blades communicate over Ethernet using the old but simple getwork mining
protocol. If you build BFGMiner with libmicrohttpd, you can have it work with
one or more blades. First, start BFGMiner with the --http-port option. For
example:
    bfgminer --http-port 8330
Then configure your blade to connect to your BFGMiner instance on the same port,
with a unique username per blade. It will then show up as a SGW device and
should work more or less like any other miner.

Is your IP for the proxy static?

On the web config, I notice that the running time for both the blade and the cube are always the same, meaning that they are restarting themselves at the exact same time.

--http-port 8330

C:\mine\bfgminer-3.8.0-win32\bfgminer.exe --http-port 8330

can someone help me?

Hi friends! For 1 cube is possible to use 2 adapters photo with a power 400w?
http://img841.imageshack.us/img841/1339/4pin.jpg