Topic: [CLOSED] batch #20/21 .31 - .35 btc for USB miners & 10.25 blades - USA only (Read 72388 times)

How I did it.

1. PAYMENT STEP.
I got enough BTC into my local Bitcoin-Qt wallet for the purchase of 5x ASIC Erupters, which Canary is selling at 0.31 per at THIS TIME. I sent the payment and it asked me to pay extra 0.0002 BTC for transaction. I clicked OK and it went through. After some time I went into Transactions tab in Bitcoin-Qt, right clicked on the -1.5502 transaction and selected show transaction details, which gave me Transaction ID:



2. ONLINE NOTIFICATION OF PAYMENT STEP
I posted in this thread per Canary's instructions:

BorisAlt; 5; 1.55; 15aJAPshhWsNJRYx4FnjYPd9fer8XM1cNT

The 15aJAPshhWsNJRYx4FnjYPd9fer8XM1cNT was the address that I use to receive my coins from other sources (more on this later).

3. PAYING FOR SHIPMENT STEP (optional, if you don't want to pay BTC for shipping)
I went to USPS and selected Ship a Package --> Print a Label:


Navigated to specifying address. Note, check the box to specify ZIP code to ship FROM ANOTHER ZIP CODE:



A few clicks later related to weight and size and shipping options and entering my credit card info, I got a window to print or save it as PDF. I saved it as PDF.

4. ASSOCIATING YOUR PAYMENT ADDRESS WITH YOUR PHYSICAL MAIL ADDRESS
Followed previous instructions on signing a message (physical shipping address) with my (bitcoin) address.
Will repeat briefly, that's what it looked like in my case:



Clicked "Sign Message" and got green confirm that it was done. Note, it creates a Signature at the bottom.

5. NOTIFYING CANARY OF ASSOCIATION BETWEEN PAYING and PHYSICAL ADDRESSES STEP:
Sent an email per instructions to [email protected] containing the following:

1. 15aJAPshhWsNJRYx4FnjYPd9fer8XM1cNT
2:
----start below------
Same address as in the Signed message from previous step
----end above-------
3: LongAssSignatureString...RFfQ3koovqa0Hr9xfIJTk7lMKmFIOlk3fO4FZ11tzHeOT51Hfo=

6. FINAL STEP, SEND SHIPPING LABEL PDF TO CANARY

I sent another email to Canary's [email protected], this time attaching PDF from STEP 3 and the following body:

d9192cc3d48721355e897317d6164be6702b5d26bd38e613fc1b973a7c157a7b (from STEP 1)
15aJAPshhWsNJRYx4FnjYPd9fer8XM1cNT (sending/receiving bitcoin address)
940550XX9930002541XXX (USPS tracking number from shipping label PDF from STEP 3)
LongAssSignatureString...RFfQ3koovqa0Hr9xfIJTk7lMKmFIOlk3fO4FZ11tzHeOT51Hfo= (from STEP 4)

What confused me by far the most was, what was my "sending address"? I receive botcoins with 15aJAPshhWsNJRYx4FnjYPd9fer8XM1cNT, but is it the same as my "sending address"? It turns out, Canary's instructions had the explanation but it was a bit too vague for me. He stated, "first sending address", which I was able to discover right here:

http://blockexplorer.com/tx/d9192cc3d48721355e897317d6164be6702b5d26bd38e613fc1b973a7c157a7b

It turns out that my sending address is the same one as my "receiving address". It may or may not be true for you, but for me it was the case since I use the same address for receiving bitcoins. Regardless, first address from  blockexplorer associated with the transaction should be provided on second line. The blockexplorer site also verifies that indeed 1.55 was transferred from my bitcoin address to Canary's bitcoin address:



It all really makes sense, but getting their is confusing at first. Once you did it once, it's super super easy and fool proof.

Thank you.

So you have some machine x running software y with router z with blades.  

Do you have any evidence that xyz works?  EG, one blade that runs correctly.

Because if not, your problem is in xyz and not the blades.

Anyway, what is X, Y and Z?

************

Went back and looked at your posts.  You are using guilds that I don't know how they work.

I am running Slush's fund no options on command line windows 7,machine is 192.168.0.15

mining.proxy.exe

At slush's fund I set up account and password, like....Acct/ps

Then I set up a worker like Acct.1/ps.1

These values plug into bottom line of blade
Acct.1:ps.1,Acct.1:ps.1

Server address as shown on blade must match IP address of server on network.
192.168.0.15

This is good advice,   Though all three of my blades are exhibiting the exact same behavior so I don't know how to play them off against each other.  I did however try to move the strongest PSU around them and it made no difference.  I'm convinced the blades themselves have a reset timer built in.  As if a condition exists that is causing them to re-start in an attempt to mine.

I am fairly certain it is not a heat issue, I have the three blades mounted about 2" apart vertically and I have a extremely strong blower blowing between/around and through all three.   It is thousands of CFM.  It is the style you would see at a store to dry off the floor after a long rain.  I have to run it on the lowest setting otherwise I risk blowing the blades across the room!     When I reach into the gale force winds, the blades are warm only.   on all surfaces.

My 'gut' is telling me there is a connection issue causing my blades not to recieve proof of work/submission etc from the pool and they are auto-restarting.   I am going to try to get into my router and make sure I open all ports (if they are not) and see what gives.  I have a feeling these blades think they need to restart because they think they are hashing without reward?    Are they smart enough to check for that and restart?!

Yeah all this chatter about hooking up pc power supplies is a pursuit of the damned, for additional pain and misery.  Just get real power supplies and be done with it.

I do not know how these units were designed, but let's assume for a sec they have a thermal cutoff.  Then some of the sections may shut down if they get too hot.  Inconsistent fan on your three blades could cause that.  Laying them flat on a surface with no airflow to one of the sides could do that.  Too close together, etc.

To determine if it is a hardware problem, swap the little board with the RJ45 connector between known good and suspect.  Then swap the power board.  Then swap the RJ45 cables, which can definitely go bad.

 If you move a part around and the problem follows the part, you have a bad part.  The only exception would be special handling of that part's IP address by the router.  Obviously each of the blades needs a discrete IP and it must be in the addressing range of the router.  They all came as 192.168.1.254, iirc.

I set mine to 192.168.1.200/201/202...

Note there is a reset switch between two pins, it reset back to default IP.

I messed around with PC power supplies, found they had inconsistent behavior and were way too complex.  Here is the solution, $27 delivered, gives 30A clean 12V, no other voltages, no hassles.   The screw down block even has 3 screws for + and 3 screws for ground (labeled V-).  

You get these babies, some 16 or 14 gauge stranded, use one power wire and one ground wire per blade.  

 I have three of these running 9 blades.

http://www.ebay.com/itm/261198916470?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1497.l2649

By the way I've got a lab power supply that tells me the draw from these blades at LOW speed is 4.5-5.5 A, less than what's been claimed...

....but while two of the PSU's are cheapo ones, but I've cut all the  molex connectors and directly wired them in.  The wires don't even get warm.      Maybe its a conflict, but why do they restart all the time?  All 3 blades do it, and they are each on different PSU's... hmm.

Here is the weird part, when on LOW and pointed directly the pool it restarts every 2 minutes and 15-30 seconds.    Everytime.  This blade has stock voltages,  The other blade next to it, at 1.195V and a different PSU also restarts on nearly the same interval.  Both blades on low produce between 4-8Ghash roughly.

I just setup my third (and last) blade on a much stronger PSU, and it is currently at stock voltages and I am running it through the same paces.  On LOW pointing straight to the pool it also is doing the exact same behavior and speed.

that does seem like a power issue. did you adjust the voltage on your blade? if so, where did you touch the multimeter leads? if not, try your blade on "low" and pointed directly at the pool not through the proxy and restart it. see if it looks normal. if so, change the clock to high and see if it looks normal.

if both look normal then try the proxy. the x's likely mean there is not enough power though.

Hey, So I just took an hour to figure out how to setup the proxy with the arguments for the pool, and it looks like Deepbit won't talk to the proxy, but I appear to have been able to connect the proxy to EclipseMC.

However, after I configured the blade, it immediately went to CHIP: xxxxxxxxxOxxxxOxxxxxxxx

Thats weird, and I got no hashing on the config page, or in the pool even after 10 minutes.    What gives?