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

Regarding the 24v input discussion

I took a closeup of the power lane section of the blade, presuming the chip I'm focusing on is schematically what we're looking for. It's a buck controller (DC to DC step down converter, often used in dropping 12v computer power down to CPU levels).

Here is a closeup of the area:



It's a Sipex 6133 model, 5-24VDC input, handles up to 30A.

Here's one of several datasheet links/possibilities: http://www.alldatasheet.com/datasheet-pdf/pdf/173439/SIPEX/SP6133.html

More than likely 24VDC could be used, however I wouldn't want to simply try it without examining the circuit to ensure everything else could take more than 12. Most components are rated 13-400VDC but, you never know.

Hopefully that helps with the discussion.

Have either of you tried it?  I've downloaded version 3.2.0, both x86 and AMD64 builds.


the --http-port option is not listed in the help reported by bgfminer.exe, nor in the linux build, although the feature is s listed in the release notes, and instructions in README.ASIC.txt.

But it's accepted on the linux build I did, and runs quite happily, though the speed reported in Blade config page never seems to reach >10GH like it does with mining_proxy.

I'm confused!

If your blades are anything like mine, it will happen again. I agree it sounds like we're having similar issues, as are some others on the forums. Mine will get to 10.7, 11ish for a good couple hours, then switch proxies, and usually sit in the 300mh-2gh range for awhile, then switch and they die off and constantly reboot.

There's something not right in the firmware in my estimation. Sometimes, even on a cold boot, they just don't send packets out, and sometimes they do. Sometimes after not sending packets out for hours, they'll suddenly start. There's clearly a bug. It's happening on the new blades as well from what I've read in a few places, so it's not just a blade1 thing.

I have also noticed a pattern, if I disconnect blades from the network and let only one come online, generally speaking it works like a champ, 10-13gh. Within a minute or two of putting another blade on the same network (regardless of if its connecting to the same proxy/pool), they both go down. I continue to suspect something is up with how it's talking on the network.

Since this has occured, they seem most stable if they're allowed to hop between getwork and stratum (ie, put a getwork pool IP & a stratum proxy IP in the server line). If you force it to choose one or the other, it seems to simply fail to hash.

I see there's what appears to be a jtag/serial port on the NIC, I'm going to probe that tonight to see if I can find tty access.

Not normal.  No.

Where are you reading your hash rate?  If it's pool stats, most pools take a long time to average out your speed so they will read low at first.  If you are reading your hash rate from the Blade's configuration, maybe wait a bit and check after your Blade has run for a while.  I can't recall, but I think they may take a while to get up to speed.

And no, the new style blades aren't officially overclocking.  I'm sure some hardware hacker will come up with something soon though. 

Alright, I've been hashing for a good several hours now, but my Blade seems to be averaging 8GH/s, I see all "O"s in the web config, so, from what I understand, all the chips are hashing. Is this normal for a board rated 10.7GH/s? Is the Rev 2.01 overclockable?

I bought a couple of blades from an ebay reseller and I asked him if I could buy a backplane too.  It wasn't free but I thought it was a fair price.

Is anyone selling one of those backplane by itself? I'd like to start building on it. Already have 3 gen2 blades and couple more coming in.

What's weird is, now all of the blades are mining at 10.7 ghash with the same configurations and I have no idea what caused the issue earlier.  Now I'm waiting to see if it comes up again.

Couldn't get more simple than the PSU above.  The blade gets the power directly from the backplane... no mo' molex!

Power supply is fine I would just rather have something I plug into a molex and out to the  blade eroupter.

I ordered this...  http://www.amazon.com/850WATT-Redundant-Power-Supply-DPS800GBA/dp/B004MU7MEQ/ref=pd_cp_pc_3

It hasn't arrived yet so I don't know if it's as simple as plug-and-play.  But you can't beat the price!

Is there just a more simple modular power supply adapter for less hack and slash as it seems needed for this. If I have to use a power supply like that I don't want to fudge to much to put it back together or make a mess. That's one reason I like the usb eroupters.

Is there one like this that uses normal connectors?
Something that more naturally does something like this
  (found at http://amzn.com/B002CZANA8 )

I tried that before, same IP/user info twice for main and backup always seem to restart the blade within an hour. I can try again to see if it will act any different now.

What's the deal with BFG supporting blade? How does that even work since it would never be running on the blade itself.

Mdopro1 &  Mountainjam,

  Use this format to input details into the server & user:pass. (After connecting to the config page @ 192.168.1.254:8000) --Config Page for each blade is xxx.xxx.x.254. If you don't change each IP to   ..etc .250,.251,.253,.254 should be different for each blade or you will have an IP conflict.

If you have more than one ASIC rig or blade, then I would go with the proxy... Extremely easy and simple to setup. I used slush's pool and found his proxy good. Here's the link: http://mining.bitcoin.cz/mining-proxy-howto

Eligius supports both getwork and stratum. Is it more efficient to set up a stratum proxy for the blade, or go direct to Eligius getwork?

I'm also experiencing proxy swapping on a regular basis and here's my scenario.

- PSU: 850W Corsair pro series
- Gen1 blade (single blade) worked great on this CPU with OC and never gave any problems.
- I changed the switch to 16 port 100MBps for make room for more blades coming in. My only blade working great.
- One proxy on each computer, in total 2 proxies on different IPs, both on Windows 7 64-bit
- I get 3 X gen2 blades, I rig them up and they all hash happily.
- Same PSU. Voltages showing 12.04 on each blade's terminal. No PSU resets or anything out of the ordinary.

Now all 4 (1Xgen1, 3Xgen2) on same switch and PSU are switching proxy constantly Yup, including gen1 which was a happy hasher until now.

Hash rate sticking around 10k on gen2 and 12.8k on gen1.

So if anyone figures out why these things are switching proxies then use the above info and hopefully provide some assistance too.

What specifically did you do to get it working?  Please share.  You may help others with your experience.

Everything is working fine with my blade now! Just trying to get it connected to a pool.

Here is a picture of my config for one of the blades, I'm using two different proxy IPs on each blade.  If I use the same proxy IP twice on a blade, it appears to receive 8 shares then return little or none of them:
http://s23.postimg.org/kgdvdt4ez/miner.jpg

Here is a picture of what happens when I use a single proxy IP in the miner config:
http://s18.postimg.org/7070dzi9l/miner2.jpg


Thanks!

Edit: I also notice back on page 34 that people were reporting low speeds and the miners switching between pools randomly.  It sounds like I'm probably having the same issue .

I had an unresponsive Blade.  I shorted the pins (see illustration) while the power was on... shut down, restarted and then was able to configure the Blade.