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

[Damnsammit]

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.

Ahhhh, sorry I misread that the PSU was shutting off.  If the mining is rebooting then it could be a different issue.

Post up the info on your Cube page, your batch file to run the proxy miner, and also what you get when you run "ipconfig"

We should hopefully be able to assist from there

[ksami]

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.

Long poll : inactive ?

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

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.

Sorry, I meant look through the whole thread not just my issues.  My final resolution turned out to be my proxy / network configuration (to the best of my knowledge) - there wasn't anything wrong with the cube.  I also didn't have any power supply issues, like the rebooting your having. 

[qwertyasdfg]

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.

Thanks for your advice, will give it a try!

[HellDiverUK]

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? 

This is the way I do it, so I have multiple workers.  I've got 2 instances of the proxy for two pools - so it's 4 instances of the proxy running.  The Blades and the Cube go to their own pair of proxies.

So, I have 4 shortcuts in Windows startup - Cube Eligius, Cube BTCGuild, Blades Eligius and Blades BTCGuild.  This allows the miners to swap between pools automatically if one pool is down.  All 4 shortcuts point to the same .exe so no real issues.

[stewdk]

I've got 2 instances of the proxy for two pools - so it's 4 instances of the proxy running.  The Blades and the Cube go to their own pair of proxies.

So, I have 4 shortcuts in Windows startup - Cube Eligius, Cube BTCGuild, Blades Eligius and Blades BTCGuild.  This allows the miners to swap between pools automatically if one pool is down.  All 4 shortcuts point to the same .exe so no real issues.

2 blades sharing a proxy? Eligius is vardiff last i checked, so you may want to consider having yet another proxy instance or two so the blades aren't sharing... I will reiterate yet again that slush's proxy does not handle well multiple workers with different share difficulties, resulting in unsubmitted shares and lost profits.

Luke-JR, please please please add long poll to the bfgminer proxy so we don't have to deal with this...  Or if slush would fix the stratum proxy, that would be great too. Or ASICminer could implement stratum natively in the firmware - I'd be okay with that too.

[Defender666]

My configuration is really not complicate:

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

Also tried 50btc and btcguild no real difference.

tried also different but I really don't think it is the proxy.

Concerning the Long Polling. It starts with long polling then disables it then a little bit later it makes restart.

Can you tell me what is normal state of the Miner? LED OFF or LED RED ??

I wait for the 750 corsair PSU hope this can help or I have an expensive brick.

The real problem is the restart. Is there possibility to login to the device and see more info with USB or this other service port?

[ksami]

My configuration is really not complicate:

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

Also tried 50btc and btcguild no real difference.

tried also different but I really don't think it is the proxy.

Concerning the Long Polling. It starts with long polling then disables it then a little bit later it makes restart.

Can you tell me what is normal state of the Miner? LED OFF or LED RED ??

I wait for the 750 corsair PSU hope this can help or I have an expensive brick.

The real problem is the restart. Is there possibility to login to the device and see more info with USB or this other service port?

You have a network issue not PSU ! I had the same thing restarting every 2 minutes with long poll inactive, you have to see carefully that your cube is still changing pool (A to B, B to A) at every refresh...

Normal state is LED RED at start, then when you mine it will off & on...

[Defender666]

Then please tell me what I can try to change to get the network issue fixed?

The Miner is connected directly to the router same is the PC.

Is the network defective in the Miner?

[ksami]

Then please tell me what I can try to change to get the network issue fixed?

The Miner is connected directly to the router same is the PC.

Is the network defective in the Miner?

Disconnect all network device (I mean really all), shutdown WiFi & disconnect all wireless devices. Let only the miner, cube and router ON.

Then try again if you see any difference !

[Defender666]

With miner you mean the proxy? The PC is not mining just for proxy

[ksami]

With miner you mean the proxy? The PC is not mining just for proxy

Yes mining proxy !

[spiler]

Hello,


I can use the cube on coinex.pw?

[alexrossi]

Hello,


I can use the cube on coinex.pw?

of course

[spiler]

but using the mining proxy? what ip should I enter for the POOL coinex?

[twib2]

but using the mining proxy? what ip should I enter for the POOL coinex?

??  Coinex.pw has a lot of pools, each with their own port number.  Just click on any pool at this page and it will tell you the mining address to use:
https://coinex.pw/mining/pools

[spiler]

Of course, I already know coinex use and I use it with the bifury using cgminer. But with the blade cube or not how.

[twib2]

Of course, I already know coinex use and I use it with the bifury using cgminer. But with the blade cube or not how.

Ah, then you just have to invoke the proxy with the correct switches to use your pool of choice.  For setting it for the UNO pool on linux, it's:

Code:

python mining_proxy.py -gp 8332 -o stratum.coinex.pw -p 9026 -cu username -cp userpass

where:
-gp sets the port you point your blades or cube at
-o sets the pool address
-p sets the pool port
-cu (if needed) sets the username for any miner using that proxy
-cp (if needed) sets the password for the above user

Hope this helps!
- Tye

[twib2]

You can also try the "-nm" and "-rt" switches if your pool supports that.  Most pools seem to support "-rt", which allows the pool's transmitted difficulty to pass through and cuts down your local network handshaking, usually improving throughput.  I have not had much luck with the cubes and "-nm", but it seems to work fine for the blades, though not much noticeable improvement (if any).

[Damnsammit]

My configuration is really not complicate:

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

Batch file looks fine.  Can you take a screen shot of your Cube config page?  Also a screenshot of "ipconfig" would be helpful, but if you don't want to include that, please run it (command prompt -> "cd\windows\system32\" enter then "ipconfig") and tell us what the IP address, subnet mask, and gateway IP is...