Pages:
Author

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

legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
I think an undervolt is more likely to blow the fuse - if the input power is constant, and the input voltage is reduced then the input current draw goes up. Given it's behaved the same on two different power supplies that's sorta unlikely.
One possibility is one of the VRMs isn't tuned quite right and it's getting shoot-through currents through the switching transistors. Could be erratic, could be low enough to strain the fuse but not blow it straightaway. My first test blade ran for 30 hours pulling 11+A through the supposed 8A fast-blow fuse, so it's also unlikely but possible that the fuses he's using are underspec.
legendary
Activity: 1946
Merit: 1035
Ugh. No fans attached. And I have used 2 different power supplies with the unit, so -- it probably isn't them, as fuses have been blown while attached to each. And it is running vertically.

Thanks.

How long have you been running them on average before the fuses got burnt?

If you have a multimeter, did you try to measure the amperage drawn from the 12V lines by the Blade?
hero member
Activity: 711
Merit: 532
I have a V2 blade which has gone through three of those tiny fuses. It runs great other than that. What am I doing wrong?

Obviously you board is drawing too much current, so you must find the sucker. V2 Blades don't have voltage tuning unlike V1s, so I would rule out too high voltage. If you have connected fans to the white 2-pin power connectors, or anything else, they would be my first suspects.

Otherwise, if you are running the Blade vertically and/or there is nothing under the board that could create any ghost current, I would check the PSU voltage, for some reason it might be above 12V (would be weird, never seen that). If the PSU is okay, I would blame faulty components on the power lanes (inductors, capacitors, etc) or maybe even faulty chips. It that's the cause indeed, I'm afraid you'll have to go for a RMA.

Ugh. No fans attached. And I have used 2 different power supplies with the unit, so -- it probably isn't them, as fuses have been blown while attached to each. And it is running vertically.

Thanks.
legendary
Activity: 1946
Merit: 1035
I have a V2 blade which has gone through three of those tiny fuses. It runs great other than that. What am I doing wrong?

Obviously you board is drawing too much current, so you must find the sucker. V2 Blades don't have voltage tuning unlike V1s, so I would rule out too high voltage. If you have connected fans to the white 2-pin power connectors, or anything else, they would be my first suspects.

Otherwise, if you are running the Blade vertically and/or there is nothing under the board that could create any ghost current, I would check the PSU voltage, for some reason it might be above 12V (would be weird, never seen that). If the PSU is okay, I would blame faulty components on the power lanes (inductors, capacitors, etc) or maybe even faulty chips. It that's the cause indeed, I'm afraid you'll have to go for a RMA.
hero member
Activity: 711
Merit: 532
I have a V2 blade which has gone through three of those tiny fuses. It runs great other than that. What am I doing wrong?
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Ah, you're running them both out of a single batch file instead of straight from multiple consoles. Good to hear you got it figured out.
DKO
newbie
Activity: 13
Merit: 0
After about an hour now it has averaged out about 98%. All good.

Got my head around this now I think haha.
newbie
Activity: 23
Merit: 0
I set mine like this in a .Bat file:
mining_proxy -o eu-stratum.btcguild.com -p 3333 -cu USER -cp 1234 -q

Got 98%
DKO
newbie
Activity: 13
Merit: 0
I have it working now, I added start to the beginning of each line.

start C:\miner\mining_proxy.exe -o stratum.bitcoin.cz -p 3333 -gp 8332

start C:\miner\mining_proxy.exe -o eu-stratum.btcguild.com -p 3333 -gp 8333


I'm not sure if that's an obvious thing or not.

Thanks for your help with this.

I have noticed that the efficiency of my blade set to BTCguild is around 93% now when it used to be around 98-100% on Slush. Is that to be expected? My two other blades on Slush are still around 99%.

legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
What's your command line for the Guild proxy?
DKO
newbie
Activity: 13
Merit: 0
If you wait a moment, does it start listening for work? Sometimes mine give errors like that but then fire up just fine.

Also I was testing a bit with running two proxies the other day, and was having some issues with the second one connecting on 8333. 8332 and 8335 work just fine on my setup, not sure if using two ports so close is messing it up or what.

Yes it finds work on the slush mining port, 8332. That works fine, but the blade I have setup for BTCguild doesn't find any work. The ports on the blade are set to 8333,8333 and correct user:pass but it just never finds any work. I've tried 8335 as well.

I've had the BTCguild settings working through a cloud proxy but just not through my own proxy.

Thanks for your help though, I'll keep at it. Smiley
newbie
Activity: 46
Merit: 0
Up to nearly 100,000 viewers. Congrats guys!

Congrats to you for creating the useful guide Smiley

Much better than the flyer manual (no longer?) provided with the Blades.

I know, seriously, a one pager that says the ip and how to factory reset?  Thanks Dogie.
legendary
Activity: 1946
Merit: 1035
Up to nearly 100,000 viewers. Congrats guys!

Congrats to you for creating the useful guide Smiley

Much better than the flyer manual (no longer?) provided with the Blades.
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Up to nearly 100,000 viewers. Congrats guys!
full member
Activity: 164
Merit: 100
Is there any way to run mining_proxy.exe as a service and still be able to monitor it?
I know I can set a .bat file to run as a service, but that would run in a hidden Admin account...
(unless there is some magic way of viewing this task... maybe a WebUI or something?)

I'm probably shooting in the dark since new miners don't really use this, so probably hasn't been updated to allow features such as this.
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
If you wait a moment, does it start listening for work? Sometimes mine give errors like that but then fire up just fine.

Also I was testing a bit with running two proxies the other day, and was having some issues with the second one connecting on 8333. 8332 and 8335 work just fine on my setup, not sure if using two ports so close is messing it up or what.
DKO
newbie
Activity: 13
Merit: 0
Thankyou for your reply. Here's the text I get.

C:\Users\DKO\Desktop>C:\miner\mining_proxy.exe -o stratum.bitcoin.cz -p 3333 -
gp 8332
C:\miner\mining_proxy.exe\twisted\web\util.py:372: DeprecationWarning: Passing f
ilenames or file objects to XMLFile is deprecated since Twisted 12.1.  Pass a Fi
lePath instead.
2013-12-12 20:32:10,542 INFO proxy jobs. # C extension for midstate not
available. Using default implementation instead.
2013-12-12 20:32:10,543 WARNING proxy mining_proxy.main # Stratum proxy version:
 1.5.2
2013-12-12 20:32:10,546 WARNING proxy mining_proxy.test_update # Checking for up
dates...
2013-12-12 20:32:13,177 WARNING proxy mining_proxy.main # Trying to connect to S
tratum pool at stratum.bitcoin.cz:3333
2013-12-12 20:32:14,450 INFO stats stats.print_stats # 1 peers connected, state
changed 1 times
2013-12-12 20:32:14,450 INFO proxy mining_proxy.on_connect # Connected to Stratu
m pool at stratum.bitcoin.cz:3333
2013-12-12 20:32:14,451 INFO proxy mining_proxy.on_connect # Subscribing for min
ing jobs
2013-12-12 20:32:15,188 WARNING proxy mining_proxy.main # ----------------------
-------------------------------------------------
2013-12-12 20:32:15,190 WARNING proxy mining_proxy.main # PROXY IS LISTENING ON
ALL IPs ON PORT 3333 (stratum) AND 8332 (getwork)
2013-12-12 20:32:15,190 WARNING proxy mining_proxy.main # ----------------------

legendary
Activity: 1946
Merit: 1035
Hello, I had a question if you don't mind. (or anyone else) Smiley

I've types in the below but I seem to get an error. Am I doing this right?

C:\miner\mining_proxy.exe -o stratum.bitcoin.cz -p 3333 -gp 8332

C:\miner\mining_proxy.exe -o eu-stratum.btcguild.com -p 3333 -gp 8333

A deprecation error? I'm new to this stuff, slowly getting my head around it all.

The syntax seems correct, you should paste the error by copying it from cmd.exe, use the app menu (upper left corner on the icon) to select (mark) the error text and hit Enter to copy, then paste here.
DKO
newbie
Activity: 13
Merit: 0
You need the -gp option on the stratum proxy, so each one is listening on a different pool.

mining_proxy.exe -o pool1 -p port1 -gp 8332
mining_proxy.exe -o pool2 -p port2 -gp 8333

Configure your pool1 blades to Ports 8332,8332 and the pool2 blades to Ports 8333,8333

I had a setup exactly like that running for a day earlier this week, mining for a friend; two stratum proxies on the same machine pointed to different pools.

Hello, I had a question if you don't mind. (or anyone else) Smiley

I've types in the below but I seem to get an error. Am I doing this right?

C:\miner\mining_proxy.exe -o stratum.bitcoin.cz -p 3333 -gp 8332

C:\miner\mining_proxy.exe -o eu-stratum.btcguild.com -p 3333 -gp 8333

A deprecation error? I'm new to this stuff, slowly getting my head around it all.
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
Overvolting the V2 blades and changing the clock speed requires a bit of SMD soldering.
If you want to get an idea of what's being done, here's the instructions writeup for the overclock kit that I sell. It's probably similar to what user27 does.

http://www.gekkoscience.com/be_ins/blade_ins.html

Good to hear you're 8 hours clean running, hope it stays that way.
Pages:
Jump to: