Pages:
Author

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

member
Activity: 81
Merit: 10
Thanks Pistachio. Tried as you suggested using gwp on bitparking and bitminter. Still no hashes.
Settings:

Ports = 8332,8332
Server addresses   = mint.bitminter.com,mint.bitminter.com
user:pass = enginehead_blade:pass,enginehead_blade:pass

also keeps restarting every minute or so!

user and pass are correct.

I haven't tried a stratum proxy yet. Will try that next.



Since you are running linux you can use the latest version of BFGminer and it has an internal getwork server.
Was easy to set up and has been working flawlessly. It's nice to control all of my ASIC's from one "miner."
Slushs mining proxy is also very easy to set up.

Either way it's going to work best to run something local on your network as a "bridge" between your getwork blade and a stratum server.
newbie
Activity: 48
Merit: 0
Thanks Pistachio. Tried as you suggested using gwp on bitparking and bitminter. Still no hashes.
Settings:

Ports = 8332,8332
Server addresses   = mint.bitminter.com,mint.bitminter.com
user:pass = enginehead_blade:pass,enginehead_blade:pass

also keeps restarting every minute or so!

user and pass are correct.

I haven't tried a stratum proxy yet. Will try that next.

legendary
Activity: 1470
Merit: 1000
Can anybody help. My blade is running, however I am having problems updating the server & user:pass details. Whenever I enter the details and click the update/restart button the web interface is showing a garbled version of the server. Example of the output after the update her
Quote
stratum+tcp://mmpool.bitparking.update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R,update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R
the more I try to update the more gibberish I get. Help! I would love to get this hashing tonight.

After you "update/Restart"... have you tried giving it a 30sec to a minute to restart and then rebrowse to the config page? Mine won't connect at all while restarting. Doesn't take long for the blades to restart, but maybe your browser is not interpreting the restart correctly?

It is my understanding that you need to use a mining proxy to connect to a stratum pool.

Try entering mmpool.bitparking.com,mmpool.bitparking.com for the server with port 15098,15098 for get work or running a mining proxy from your PC with the command mmpool.bitparking.com -p3333
newbie
Activity: 48
Merit: 0
You and me both! I've got the interface sorted. Using firefox on ubuntu. I think it was because I didn't have the trailing comma on the server and user:pass fields. Now that's sorted, next question stratum or gwp? I'm using bitminter.com as from previous posts this pool works with these blades.
member
Activity: 81
Merit: 10
Thanks buyer99. Was using chome, tried firefox and win explorer all with slightly different results, but still no joy. I agree it looks like a browser issue because the posted info does not seem to be applied to the correct fields. What browser (and OS) are you using?

I am using Win7 64bit and using chrome to talk to it.

So..... Is the interface screwed up or does it look correct right now? I guess I'm a little confused as to what exactly is happening.
newbie
Activity: 48
Merit: 0
Thanks buyer99. Was using chome, tried firefox and win explorer all with slightly different results, but still no joy. I agree it looks like a browser issue because the posted info does not seem to be applied to the correct fields. What browser (and OS) are you using?
member
Activity: 81
Merit: 10
Can anybody help. My blade is running, however I am having problems updating the server & user:pass details. Whenever I enter the details and click the update/restart button the web interface is showing a garbled version of the server. Example of the output after the update her
Quote
stratum+tcp://mmpool.bitparking.update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R,update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R
the more I try to update the more gibberish I get. Help! I would love to get this hashing tonight.

After you "update/Restart"... have you tried giving it a 30sec to a minute to restart and then rebrowse to the config page? Mine won't connect at all while restarting. Doesn't take long for the blades to restart, but maybe your browser is not interpreting the restart correctly?
newbie
Activity: 48
Merit: 0
Can anybody help. My blade is running, however I am having problems updating the server & user:pass details. Whenever I enter the details and click the update/restart button the web interface is showing a garbled version of the server. Example of the output after the update her
Quote
stratum+tcp://mmpool.bitparking.update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R,update=Update/Restart,USPA=enginehead-two:pass&update=Update/Restart&USPA=Update/Restart,updatupdate=Update/Restart,USPA=enginehead-two:pass&update=Update/R
the more I try to update the more gibberish I get. Help! I would love to get this hashing tonight.
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Just got my 3 new blades this morning. But this green one is not include:



Did they forget to ship them to me ? Or They are not include ?
Should have been included.
member
Activity: 102
Merit: 10
Just got my 3 new blades this morning. But this green one is not include:



Did they forget to ship them to me ? Or They are not include ?
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Typically blade interface is more accurate than pool interface, but you could look at the accepted shares as the absolute value.
full member
Activity: 238
Merit: 100
I was getting low hash rates using port 8332 and 192.31.187.114 for the server. It did not seem to want to connect directly with port 3333. What settings have you found that work? I would much rather just run them directly.    

I'm using

Ports: 8332,8332
Server: mint.bitminter.com,mint.bitminter.com
User:Pass: user_worker:pass,user_worker:pass

EDIT: And the blade itself always reports a low  hash for me, yet after a few minutes I can see on the pool that they are hashing fine
legendary
Activity: 1470
Merit: 1000
I was getting low hash rates using port 8332 and 192.31.187.114 for the server. It did not seem to want to connect directly with port 3333. What settings have you found that work? I would much rather just run them directly.   

mining_proxy -o mint.bitminter.com:8332 -u Pistachio_worker1 -p x

Just wondering why you are using a proxy in this case? I am able to mine on bitminter directly from the blade.

50btc and others don't appear to play nice.. but bitminter does.
full member
Activity: 238
Merit: 100
mining_proxy -o mint.bitminter.com:8332 -u Pistachio_worker1 -p x

Just wondering why you are using a proxy in this case? I am able to mine on bitminter directly from the blade.

50btc and others don't appear to play nice.. but bitminter does.
full member
Activity: 238
Merit: 100
Hey guys I just got one of the older blades the first revision (red fuse) and I had it hashing away at 10.7gh right out of the box, chip read all 0 and everything was alright. I got a multimeter and started tuning all the voltages to 1.2 so that I could change the clock setting to high and mine at 13gh like everyone else.  After adjusting about 4 chips on the 5th on it started ticking, the blade. I'm not sure what exactly is ticking, It sounds like its coming from the green power connector, but its ticking away now. Still accepting shares, but ticking. So I finished tuning all the chips to 1.2v, carefully making sure with the voltage meter. And when I went to the ipadress:8000/main I now have 0000xxxxxxxx00000000000000000000

So does this mean that my PSU isn't providing enough power or that those chips can't operate at that voltage and need more or less power?

It should be noted that I'm using a small crappy diablotek psu that is only 350w, it is also powering a small htpc that is idling while I test the blade. However the +12v connection (i'm assuming the single strand with 2 molex and and one sata plug) is rated for 20A so I should be ok I thought? Especially given that it used to work without ticking or throwing x's in the chip row, before adjusting the voltages.

Yes, a larger name brand PSU is on the way. But in the event that isn't the issue, what could be causing this??

Thanks,
Greg

take 2 mm thick wires and solder it to your wires from PSU, then connect those wires to green connector. dont worry about 0000xxxxxxxx once you will connect your blade  properly and restart it will be gone.

Be careful do not touch board with screwdriver.

Ok, I'll do that when I get home. In the event that the screwdriver did touch the board what could happen? Also, before I went to bed last night I turned all the cards back down to 1.07v, but one of the cards is only reading 0.378v and wont go any higher. On the config file it now says

Chip: xxxxxxxxxxxxxOxOxxOOxOOOOxxOOOOO
legendary
Activity: 1470
Merit: 1000
Guys you dont need to set login information in the proxy, the blade is already sending that:

Code:
mining_proxy.exe -o eu-stratum.btcguild.com -p 3333
Just edit pool address and port.

Thanks. That got it working. Now if only there was a way to change the voltage to overclock ...  Tongue
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Guys you dont need to set login information in the proxy, the blade is already sending that:

Code:
mining_proxy.exe -o eu-stratum.btcguild.com -p 3333
Just edit pool address and port.
sr. member
Activity: 290
Merit: 250

mining_proxy -sh mint.bitminter.com:8332 -u Pistachio_worker1 -p x

But, it keeps getting an error message "argument -p/--port: invalid int value: 'x'. How should the pool information be formatted for mining_proxy? Or, do I need to download the mining_proxy file somewhere else?

Looks to me like the -p option is to set the port and not for the password.

I don't use windows but is there a -h option that lists all of them?
legendary
Activity: 1470
Merit: 1000
I am going to try switching the super small fuse that it came with to see if that helps.

They are very small.... Good luck man, sorry to hear about the trouble.

Got both blades to power on Cheesy. Now I just have to figure out how to configure the stratum proxy. The Windows download link for mining_proxy.exe from OP does not work. I found one here, http://ltcmine.ru/mining_proxy.exe. In command prompt I tried,

mining_proxy -o mint.bitminter.com:8332 -u Pistachio_worker1 -p x

and

mining_proxy -sh mint.bitminter.com:8332 -u Pistachio_worker1 -p x

But, it keeps getting an error message "argument -p/--port: invalid int value: 'x'. How should the pool information be formatted for mining_proxy? Or, do I need to download the mining_proxy file somewhere else?
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Just got my V.2 blade this morning. Got everything hooked up and configured. Dogie your guide has helped me get this far and for this I thank you and have sent you a small tip..

Problem I am running into with the blade is that it keeps restarting right around 2 minutes 15 seconds. Does this sound like a power issue to anyone? 750w supply dual rail.. I used a dual molex into PCIe splitter and attached the two yellow wires on the positive screws of the green plug and two black on the negative side screws.

EDIT: I have attached each side of the molex-PCIe power splitter to two different power "chains." Honestly I don't know if the power is being pulled from two different rails or not. Has anyone used the PCIe power, like with a PCI express power extension cable as the splice straight to one PCIe power line?

Update: All is well, I guess it was just having a network/configuration problem? Seems that these blades will just keep restarting themselves if they think something is wrong... I went ahead and rebuilt BFGminer on my pi, and added libmicrohttpd-dev this time around. This runs an internal getwork server when the --http-port xxxx option is used. Pointed the blade to my pi and now all my USB sticks along with my blade are hashing together on one worker with a diff of 16 and over 19GH!
Received thanks. Splitting rails is a good thing, but the most important thing is splitting CABLE rails. Cables are the limitations for most decent PSUs.
Pages:
Jump to: