Quote from: shefflad on October 28, 2013, 04:22:27 PM

Quote from: vesperwillow on October 28, 2013, 01:41:29 PM

Quote from: Trongersoll on October 25, 2013, 10:28:09 PM

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

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.

Quote from: shefflad on October 28, 2013, 01:16:57 PM

now i get the following error

Failure: stratum.custom_exceptions.TransportException Failure:

Is slush's proxy x64 compatible?

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

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.