[Guide] Dogie's Comprehensive ASICMiner Blade Setup - page 38.

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: pidge on September 19, 2013, 06:13:44 AM

Quote from: vulgartrendkill on September 19, 2013, 04:29:23 AM

Can I just say, that the latest bfgminer (released today) has native support for blades so a proxy may not be needed. I've yet to try it myself, but it sounds promising.

The Windows binaries don't provide the http-port option, so I went to the trouble of building an Ubuntu workstation and building bfgminer 3.2 - and that didn't make a difference. Or maybe I was to impatient with it?

The latest Win32 release of BFGMiner DOES support the http-port option. Read the release notes.

pidge

member

Activity: 101

Merit: 10

Quote from: vulgartrendkill on September 19, 2013, 04:29:23 AM

Can I just say, that the latest bfgminer (released today) has native support for blades so a proxy may not be needed. I've yet to try it myself, but it sounds promising.

The Windows binaries don't provide the http-port option, so I went to the trouble of building an Ubuntu workstation and building bfgminer 3.2 - and that didn't make a difference. Or maybe I was to impatient with it?

CroverNo01

sr. member

Activity: 588

Merit: 269

Hi,

Just wondering I have my replacement blade coming today for the backplane but I am kinda feared to add it in as currently there is 9 blades running and the PSU is at max speed to try keep it's self cool.

I have another power supply powering the V1 Blades just wondering can you 2X Sata Power cables to power the blades ? So you would still have the 4 Black and 2 Yellow wires ?

Not sure of the power rating of Sata cables or the Amp

Any advice ?

Cheers

vulgartrendkill

hero member

Activity: 518

Merit: 500

Quote from: pidge on September 19, 2013, 02:55:08 AM

Hmm, I may have solved it by specifying a custom user and password in mining_proxy for share submission:

Code:

mining_proxy.exe -o stratum.btcguild.com -p 3333 -gp 8342 -sp 3342 -cu pjnield_4 -cp 1234

how bloody annoying

Can I just say, that the latest bfgminer (released today) has native support for blades so a proxy may not be needed. I've yet to try it myself, but it sounds promising.

pidge

member

Activity: 101

Merit: 10

Hmm, I may have solved it by specifying a custom user and password in mining_proxy for share submission:

Code:

mining_proxy.exe -o stratum.btcguild.com -p 3333 -gp 8342 -sp 3342 -cu pjnield_4 -cp 1234

how bloody annoying

LarryFossil

newbie

Activity: 28

Merit: 0

Quote from: Stack on September 18, 2013, 07:54:37 PM

Quote from: LarryFossil on September 18, 2013, 05:25:56 PM

Update 3:

I switched around my + & - and put them in series with the ASIC chip. I turn on PSU; Fan starts up then quits & the PSU shuts off. What could be my problem? I am using a 12V rail that is meant for 12A and I only need 1.2Watts / 10Amps per blade.

Problem:
Led light behind the ethernet port starts blinking when I initially power the board, but it shuts off.
PSU works when not connected to ASIC board.
PSU Specs: https://www.dropbox.com/s/9ymyq88joxuv38o/2013-09-18%2011.08.39.jpg

Possibilities:
Bad PSU
Pulling to many amps from ASIC board
PSU not supplying advertised voltage

Other:
Fuse is working (tested em with diode checker)
Fans come on when not plugged into ASIC (using other 12V Rail to power the fans)
Only reading about 11.5-11.3V on multimeter when no fans are plugged in.
No smoking of the equipment as of yet =P

That doesn't sound right. Don't they need 120Watts per blade? as per OP

Yea, Your right. That is a typo. Its suppose to be 1.2Volts @10 amps / 120 Watts, but thanks for the help..

Update 4:
I found out my PSU problem with the help of Wizkid on IRC. He gave me the idea to connect my two 5v extra wires to a 5-6v fan. (Older PSU's won't work properly unless power is distributed.) I joined both 5v wires from the modified molex splitter (per OP) & used one ground wire from same rail to power the 6v fan. Plugged it in and boom everything worked. Including the two 120mm fans I have on another rail.
Seen IP connectivity and Connected to the ASIC through the browser at ease =P Now, I need to figure out how to input the settings perfectly =P to mine on slush's pool. Hopefully that is a bit simpler... I have been fiddling with this stuff since yesterday. Should of been much simpler, but I paid 50 bucks for a cheapo pwr supply and ended up wasting valuable time cause of a different power distributing configuration.

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: jml on September 18, 2013, 08:32:13 PM

Quote from: RicRock on September 18, 2013, 07:37:22 PM

Quote from: jml on September 18, 2013, 07:12:58 PM

After the update, I would expect values to be updated from the last POST sent from browser. The user would then have to redirect (not hit the back key) to the home page of the blade which would be http://192.168.x.x:8000.

A POST would only work that way if you weren't restarting the httpd server which is what you are doing when restarting the blade after the config.

Much like when you update the configuration of a router or whatever from a web interface

I am assuming it uses POST as I don't see arguments on the address which would be GET.

I totally understand what your saying... it restarts the webserver so there is no way it can post "back" to the config screen once your "session" is broken by a restart.

xstr8guy

hero member

Activity: 784

Merit: 1004

Glow Stick Dance!

Quote from: mdopro1 on September 18, 2013, 03:46:27 PM

I just received 3 of Gen2 blades, two work fine but the third one seems to be connected but not hashing at all. It may also be restarting, right now it's 1m 57s running. Voltages on both terminal are showing exactly 12.04V and power is coming from two separate rails of molex with a splitter to support 10AMP - so 2 yellow and 3 black in each connector respectively.

I can access the config page and all chips show OOO. This means that I have an IP, no conflict and I can connect to the hasher. Hash rate sitting at 0 all the time so far.

I copied/pasted stratum proxy and pool user info from a working blade so that shouldn't be a problem either.

Any suggestions?

EDIT:
- I have two proxies running on two separate machines which connect to two different pools and neither one are working.
- PSU is a 850W Corsair Professional series, voltages are ok and 2 other miners are working off the same PSU.

Try a hardware reset. I had a similar issue and that fixed it.

Quote from: xstr8guy on September 15, 2013, 12:39:33 AM

Btw, got the bad Blade working by doing a hardware reset by shorting the two pins as shown in this illustration...

jml

full member

Activity: 238

Merit: 100

Quote from: RicRock on September 18, 2013, 07:37:22 PM

Quote from: jml on September 18, 2013, 07:12:58 PM

After the update, I would expect values to be updated from the last POST sent from browser. The user would then have to redirect (not hit the back key) to the home page of the blade which would be http://192.168.x.x:8000.

A POST would only work that way if you weren't restarting the httpd server which is what you are doing when restarting the blade after the config.

Much like when you update the configuration of a router or whatever from a web interface

I am assuming it uses POST as I don't see arguments on the address which would be GET.

Stack

full member

Activity: 238

Merit: 100

Quote from: LarryFossil on September 18, 2013, 05:25:56 PM

Update 3:

I switched around my + & - and put them in series with the ASIC chip. I turn on PSU; Fan starts up then quits & the PSU shuts off. What could be my problem? I am using a 12V rail that is meant for 12A and I only need 1.2Watts / 10Amps per blade.

Problem:
Led light behind the ethernet port starts blinking when I initially power the board, but it shuts off.
PSU works when not connected to ASIC board.
PSU Specs: https://www.dropbox.com/s/9ymyq88joxuv38o/2013-09-18%2011.08.39.jpg

Possibilities:
Bad PSU
Pulling to many amps from ASIC board
PSU not supplying advertised voltage

Other:
Fuse is working (tested em with diode checker)
Fans come on when not plugged into ASIC (using other 12V Rail to power the fans)
Only reading about 11.5-11.3V on multimeter when no fans are plugged in.
No smoking of the equipment as of yet =P

That doesn't sound right. Don't they need 120Watts per blade? as per OP

RicRock

sr. member

Activity: 290

Merit: 250

Quote from: jml on September 18, 2013, 07:12:58 PM

After the update, I would expect values to be updated from the last POST sent from browser. The user would then have to redirect (not hit the back key) to the home page of the blade which would be http://192.168.x.x:8000.

A POST would only work that way if you weren't restarting the httpd server which is what you are doing when restarting the blade after the config.

Much like when you update the configuration of a router or whatever from a web interface

jml

full member

Activity: 238

Merit: 100

Quote from: RicRock on September 17, 2013, 11:53:19 PM

Quote from: jml on September 17, 2013, 10:52:38 PM

Code:

The parameters are updated or the system is simply restarted! 517

That's what I get when I update and restart my blades.

What are you expecting to see? I don't believe it auto-refreshes back to original url or anything.

After the update, I would expect values to be updated from the last POST sent from browser. The user would then have to redirect (not hit the back key) to the home page of the blade which would be http://192.168.x.x:8000.

For some reason unknown, the update function does not work from my laptop and had to use the browser on my phone to make the update work! I will try and update to see what was the exact cause for chrome and IE9 not to update the settings on the blade.

notlist3d

legendary

Activity: 1456

Merit: 1000

Quote from: gaboo08 on September 18, 2013, 06:03:04 PM

Anyone else having similar issues with the new blade version where it won't hash when using the same IP address for the stratum proxy? And when using two separate proxies, it seems to switch between the two? My hash rate is still ranging from 2000 to 3800 at the moment and I can't figure out how to get it to work.

Try slush pool from the first page. Dogie did a kick ass job on guide. I was getting the same 2-3kish then downloaded file from first page, ran it and mining at slush at great speeds.

gaboo08

newbie

Activity: 14

Merit: 0

Anyone else having similar issues with the new blade version where it won't hash when using the same IP address for the stratum proxy? And when using two separate proxies, it seems to switch between the two? My hash rate is still ranging from 2000 to 3800 at the moment and I can't figure out how to get it to work.

LarryFossil

newbie

Activity: 28

Merit: 0

Swimmer63

legendary

Activity: 1593

Merit: 1004

Quote from: xyzzy099 on September 18, 2013, 03:55:13 PM

Quote from: Swimmer63 on September 18, 2013, 03:49:57 PM

Quote from: enginehead on September 13, 2013, 01:15:53 PM

Quote from: ezview on September 13, 2013, 02:35:12 AM

Quote from: RicRock on September 13, 2013, 02:21:59 AM

not enough subnet mask to go from 192.168.x.x to 10.x.x.x

Do you have a separate switch? You can manually change your PC's IP address to be 192.168.1.x just so you can connect to blade and change it's config

Yes, thx and just got pc to show 192.168.0.1 as gateway, however, I never got docs with new blade and do not know the blade IP plus if it is 192.168.1.x I am still off some with 192.168.0.x.

Also, good idea to change the blade and then can go back to 10.0.0.1 if needs be.

thx

ip should be 192.168.1.254 as long as your router gives that range. 1-254

I am trying to connect a blade to my office network and I think I have a similar issue to above.
The Default Gateway is 192.168.0.1. The router goes to 254.
But I can't access the config page using 192.168.1.254:8000 or 192.168.0.254:8000. Tried from both a wireless and direct connection on a networked PC. The blade is plugged right into the router and it's flashing green.
Any suggestions?

You need to be on a network with 192.168.1.x. Can you temporarily change your router's IP address to 192.168.1.1 instead of 192.168.0.1? You will be able to connect if you do that.

EDIT: You will need to change your PC's IP address to 192.168.1.(whatever) also. If you want to stay on the 192.168.0.x net, you can change the blade to 192.168.0.x, and then set your other IPs back to normal.

OK -thanks for the info. That will be challenging.

mdopro1

sr. member

Activity: 308

Merit: 250

Double your Personal Bitcoin Funds.

Quote from: Rishodi on September 18, 2013, 04:36:29 PM

Quote from: dogie on September 18, 2013, 03:29:11 PM

Quote from: Rishodi on September 18, 2013, 03:17:33 PM

My new-gen blades periodically restart all at once. There are 10 of them connected to a backplane and powered by one of the plug-in PSU models. The uptime never seems to go higher than a couple of hours, so that's approximately how long they're going before restarting. It happens to all of them at the same time. What might the issue be?

Could be power interruption or both pools appearing down, ie internet problems.

I have a server PC right next to the blades, running off the same power strip, running a stratum proxy which the blades all use. The server hasn't been restarting, so it's not the power blinking, at least not at the wall. If the proxy restarts could that cause the blades to reset?

Try this, run all blades and have them hashing. While they are running, restart the proxy that they connect to. Simply CTRL+C and immediately restart the proxy. I have 4 blades and they kept restarting every 20 minutes until I did this and now they run for as long as they can... I'm new to it all, so far my record was 7 days running. But be quick so your blades don't connect to backup server.

Rishodi

member

Activity: 77

Merit: 10

Quote from: dogie on September 18, 2013, 03:29:11 PM

Quote from: Rishodi on September 18, 2013, 03:17:33 PM

My new-gen blades periodically restart all at once. There are 10 of them connected to a backplane and powered by one of the plug-in PSU models. The uptime never seems to go higher than a couple of hours, so that's approximately how long they're going before restarting. It happens to all of them at the same time. What might the issue be?

Could be power interruption or both pools appearing down, ie internet problems.

I have a server PC right next to the blades, running off the same power strip, running a stratum proxy which the blades all use. The server hasn't been restarting, so it's not the power blinking, at least not at the wall. If the proxy restarts could that cause the blades to reset?

xyzzy099

legendary

Activity: 1065

Merit: 1077

Quote from: Swimmer63 on September 18, 2013, 03:49:57 PM

Quote from: enginehead on September 13, 2013, 01:15:53 PM

Quote from: ezview on September 13, 2013, 02:35:12 AM

Quote from: RicRock on September 13, 2013, 02:21:59 AM

not enough subnet mask to go from 192.168.x.x to 10.x.x.x

Do you have a separate switch? You can manually change your PC's IP address to be 192.168.1.x just so you can connect to blade and change it's config

Yes, thx and just got pc to show 192.168.0.1 as gateway, however, I never got docs with new blade and do not know the blade IP plus if it is 192.168.1.x I am still off some with 192.168.0.x.

Also, good idea to change the blade and then can go back to 10.0.0.1 if needs be.

thx

ip should be 192.168.1.254 as long as your router gives that range. 1-254

I am trying to connect a blade to my office network and I think I have a similar issue to above.
The Default Gateway is 192.168.0.1. The router goes to 254.
But I can't access the config page using 192.168.1.254:8000 or 192.168.0.254:8000. Tried from both a wireless and direct connection on a networked PC. The blade is plugged right into the router and it's flashing green.
Any suggestions?

You need to be on a network with 192.168.1.x. Can you temporarily change your router's IP address to 192.168.1.1 instead of 192.168.0.1? You will be able to connect if you do that.

EDIT: You will need to change your PC's IP address to 192.168.1.(whatever) also. If you want to stay on the 192.168.0.x net, you can change the blade to 192.168.0.x, and then set your other IPs back to normal.

Swimmer63

legendary

Activity: 1593

Merit: 1004

Quote from: enginehead on September 13, 2013, 01:15:53 PM

Quote from: ezview on September 13, 2013, 02:35:12 AM

Quote from: RicRock on September 13, 2013, 02:21:59 AM

not enough subnet mask to go from 192.168.x.x to 10.x.x.x

Do you have a separate switch? You can manually change your PC's IP address to be 192.168.1.x just so you can connect to blade and change it's config

Yes, thx and just got pc to show 192.168.0.1 as gateway, however, I never got docs with new blade and do not know the blade IP plus if it is 192.168.1.x I am still off some with 192.168.0.x.

Also, good idea to change the blade and then can go back to 10.0.0.1 if needs be.

thx

ip should be 192.168.1.254 as long as your router gives that range. 1-254

I am trying to connect a blade to my office network and I think I have a similar issue to above.
The Default Gateway is 192.168.0.1. The router goes to 254.
But I can't access the config page using 192.168.1.254:8000 or 192.168.0.254:8000. Tried from both a wireless and direct connection on a networked PC. The blade is plugged right into the router and it's flashing green.
Any suggestions?

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