Topic: [Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 27. (Read 580773 times)

You should have atleast the blade(now:192.168.2.109) and the proxy(now:192.168.147.130) in the same subnet, like 192.168.2.100 for the machine running the proxy (Server Address) and 192.168.2.101 for the blade.

For some reason, BFGminer 3.2.1 (too lazy to update  ) slows down my V2 blades to 75%-80% max, approx 100-110 shares per minute! That's why i run the stratum proxy on my desktop (IP:192.168.1.200)

Take a look at my configuration:
http://i.imgur.com/DrwDtez.jpg

The IP 192.168.1.202 is assigned to the blade (i run 3 of them: 201,202, 203)
Gateway is the Device that routes to the internet, all blades connect via a hub to the network card with the IP 192.168.1.200. You should set this as a static IP in the network properties of your Windows!

I've set this IP as the primary DNS, too! Secondary DNS belongs to a google DNS server
Server addresses: the machine the proxy is running, 192.168.1.200 too!
You might extend the pass up to 4 chars since there were problems with passwords shorter than 3 chars in the past. Since it isn't really needed, nothing to worry about "1234" or "abcd"

My desktop connects to the Router/Modem/Internet over a 2nd network interface (WLAN)

If you have further questions, i'd do a quick drawing of my setup and used IPs later!

Give this a shot

bfgminer -o stratum.bitcoin.cz:3333 -u shefflad.worker1 -p 1234 --http-port 8332

http://imageshack.us/photo/my-images/823/cs2j.png/

bfgminer -o mining.bitcoin.cz -u shefflad.worker1 -p 1234 --http-port 8332

if i type the ip address into browser so 192.168.147.130:8332 it acknowledges something wants to connect to bfg miner but when blades connected it just keeps requesting update for work

Here's something to try:

For my example I'll pretend i'm connecting to Slush's pool, my worker is named 'myloginname.blade', and the password is 'testpassword', my computer is a Win7 32bit system with an IP of '192.168.5.5'.

Download BFGMiner - the best Blade Proxy

First step is to download the Windows7 BFGminer: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.2.3/bfgminer-3.2.3-win32.zip

Setup the blade

Next, go to the blade's setup menu, make sure your gateway and both dns entries are correct (they usually point to your router). For my example they would point to 192.168.5.1 (yours will be different)

Third step is to point the blade to your BFGMiner proxy. I would set '8332,8332' for the ports. For the Server addresses I point to the windows machine, '192.168.5.5,192.168.5.5'. Finally I make up a username and password on the blade, something like 'myblade:mypass,myblade:mypass' (it shouldnt match what you use for your pool connection, nor should it match any other blade).

Press the 'update/restart' button on the blade.

Prepare the computer

Now to setup the BFGMiner software, it's easy to give a test run. First thing to do is make sure your Windows machine isn't  blocking port 8332. Easiest way to do this is to disable all firewalls (if only to test, you want to make sure to properly set the firewall up later). Once you're sure it won't block the port (or you tell it to unblock if it asks you), then move to the proxy itself:

Starting the proxy

Slush's pool url is 'mining.bitcoin.cz', and my pool worker info is 'myloginname.blade' / 'testpassword'. Knowing this, and knowing I told the blade to connect to port 8332 of the proxy, here would be my command line:

bfgminer -o mining.bitcoin.cz -u myloginname.blade -p testpassword --http-port 8332

Debugging Issues

If BFG starts up and it connects to slush's pool, then you know the software proxy is working. You'll see a line which says 'HTTP server listening in port 8332', this lets you know the proxy is running. This means BFG is good to go. If it doesn't connect or doesn't run, then debug that first.

You should shortly after see a worker connect (usually shows up as PXY) and it'll start hashing. BFG will show connected to slush's pool with your worker settings. Wait 3 minutes if needed.

If you don't see anything connect, log into the blade and make sure it's pointing to your computer's IP on the proper port, and then hit 'update/restart'. This will force the blade to try again.

Let us know how it goes.


[/quote]

right done all that still not connecting, can get bfg to run proxy it gets connccted but the blades will not communicate back seems like something is blocking it switched all antivirus and firewall off

I'd set the clock to low, and then would choose a VRM (I usually start left), see what its reading is, and adjust down to 1.05. Continue right and do that to all of them, then go back and check each one to make sure they're ~1.05x. I'd reboot the blade and see what happens, while monitoring the left most VRM. If they haven't come online, I would up the VRM another 0.05 and see if it comes online. If not, reboot, and try again.

I'd repeat this process up to 1.20. If they don't come online at all on low clock between 1.05-1.20 I'd say something is definitely toast.


I  believe you contact friedcat.

Here's something to try:

For my example I'll pretend i'm connecting to Slush's pool, my worker is named 'myloginname.blade', and the password is 'testpassword', my computer is a Win7 32bit system with an IP of '192.168.5.5'.

Download BFGMiner - the best Blade Proxy

First step is to download the Windows7 BFGminer: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/3.2.3/bfgminer-3.2.3-win32.zip

(revision: use this link to grab the latest copy for your windows build: http://luke.dashjr.org/programs/bitcoin/files/bfgminer/latest/ )

Setup the blade

Next, go to the blade's setup menu, make sure your gateway and both dns entries are correct (they usually point to your router). For my example they would point to 192.168.5.1 (yours will be different)

Third step is to point the blade to your BFGMiner proxy. I would set '8332,8332' for the ports (or 8339 if you have wallet software on the proxy computer). For the Server addresses I point to the windows machine, '192.168.5.5,192.168.5.5'. Finally I make up a username and password on the blade, something like 'myblade:mypass,myblade:mypass' (it shouldnt match what you use for your pool connection, nor should it match any other blade).

Press the 'update/restart' button on the blade.

Prepare the computer

Now to setup the BFGMiner software, it's easy to give a test run. First thing to do is make sure your Windows machine isn't  blocking port 8332 (or whichever port you are using). Easiest way to do this is to disable all firewalls (if only to test, you want to make sure to properly set the firewall up later). Once you're sure it won't block the port (or you tell it to unblock if it asks you), then move to the proxy itself:

Starting the proxy

Slush's pool url is 'mining.bitcoin.cz', and my pool worker info is 'myloginname.blade' / 'testpassword'. Knowing this, and knowing I told the blade to connect to port 8332 of the proxy, here would be my command line:

bfgminer -o mining.bitcoin.cz -u myloginname.blade -p testpassword --http-port 8332

Debugging Issues

If BFG starts up and it connects to slush's pool, then you know the software proxy is working. You'll see a line which says 'HTTP server listening in port 8332', this lets you know the proxy is running. This means BFG is good to go. If it doesn't connect or doesn't run, then debug that first.

You should shortly after see a worker connect (usually shows up as PXY) and it'll start hashing. BFG will show connected to slush's pool with your worker settings. Wait 3 minutes if needed.

If you don't see anything connect, log into the blade and make sure it's pointing to your computer's IP on the proper port, and then hit 'update/restart'. This will force the blade to try again.

Let us know how it goes.

Yep, the problem is, with all "xxxxxxxxxxxx", the board never goes under load, so I'm not sure how I can meter in this state.

What's the process for getting a replacement board?

hi i have a good power supply all wiring as to the pictures 4 black 2 yellow on a splitter. the blade powers up for about 2 min 15 sec and then restarts.
i have installed virtual machine with win 7 32bit and ran in mining proxy then directed the blades to my pc in virutal machine but still no luck. i use the mining proxy download from bitcoin.cz and use bat file with my details, i have bitminter,slush pool and btcguild tried all different setting but still same.
can any one setup a proxy for me (via instructions or remote)and i will give 0.2 btc as a reward 

Make sure the blade is properly connected to power. You'll want 16gauge wiring at least, and make sure you have 2 grounds and 2 positive going to each connector, using each port on the green connector. Once you verify your wiring is proper and the connections are not loose, verify your 12V rail can support 110watts for each blade you have. I'm sure it does.

I use a 330watt AC to DC convertor (not a computer PSU) and it works perfectly for me, running each blade at 14GH. Cooling and proper power connection is critical for these tempermental things.


Is slush's proxy x64 compatible?

now i get the following error

Failure: stratum.custom_exceptions.TransportException Failure:

Are you using the mining proxy for Slushs pool or are you setting the proxy some where else..


Here is my Miner.bat
mining_proxy.exe -o stratum.btcguild.com -p 3333 -cu i3lome_1 -cp x -gp 8331

Just edit the pool with you info.

-p  Is the port you are trying to connect the pool to
-gp is the Port you would like to set you miner/blade too for the proxy.

This method works best for me.

For blade setting. the Server is the IP of the Computer running Mining Proxy.
Port is what you set the -gp too
User can be whatever you like but, I usualy set the user and pass the same. Just to remove variables

So i need some help i have downloaded stratums proxy download and run it and pointed the blade to my pc which is running the proxy but on the proxy it just keeps saying clean=false and blade keeps restarting  can anyone help me what am i doing wrong on bf g miner the usb are hashing away nicely

Problem solved!!

I was really annoyed about my V2 blades sometimes not connecting to my stratum proxy/resetting on their own, resulting in low efficiency and uptime. Few times they went down for 1 or 2 hours without any reason.

Someone mentioned to keep mobiles with enabled WiFi/WLAN away from the blades. Followed that hint and the connection to my proxy got more stable, decreasing the downtime! As next, i changed the physical network by connecting the blades to the machine running the proxy using good old cheap ethernet cable instead of plugging them to the WLAN-router to connect via WLAN to my proxy.

By now, i have an uptime of 4 days on my blades without any problems connecting to the proxy (my desktop) anymore 

Depends on the PSU! Its now how many Watts in total the PSU delivers, its about the Amperes on 12V it can provide! How many Amps does does your PSU deliver on the 12V rail(s)?! Each Blade pulls about 10A at 12V, so if the PSU only delivers 15A at 12V there is a problem if you try to run 2 Blades on that 12V rail! Can you post a picture of the that sticker on your PSU?

For example, one of my PSUs has 560W in total, but only 348W at 12V which is sufficient to run 2 V2 blades (2x 120W). Connecting a 3rd would 'cause the PSU to overheat and shutdown!
You might look as well for a 12V DC LED-driver with about 250-300W to run your 2 blades, those LED-drivers are much cheaper than a PSU for your desktop!

windows 7 64bit

I have two of the old style blades. one has been chugging along nicely at 10 Gh/s with the low clock. today i started the second one. They are both sharing a 490 watt supply. the second one came up with a bunch of Xs. powering on and off got it down to 4 Xs it was running at about 4Gh/s and after the last restart is running at 1Gh/s. is this a power supply issue? do i need to give each it's own Power supply? Both are using the same Slush proxy with unique workers.

What OS are you on?

how do i set up the proxy tried slushs download still no luck

I just set my blade with you bit minter settings. I have it hashing for me



Hash rate is a little low, took screenshot right after it connected. works fine