Quote from: mjmvisser on May 24, 2013, 02:11:25 AM

Hi, just chiming in with my experience with power distribution to my BE after seeing all the melted wire posts.

Instead of using a molex splitter, I used one of these:

Cut the 6-pin connector off the end and remove the third (not yellow, not black) wire from the molex plugs. Don't cut it -- just reach in with a pair of tweezers or needle-nose pliers and gently squeeze the pin at the base and you should be able to slide it right out.

You'll now have two molex connectors that you can wire to the power plug: two yellow to the + side, two black to the -. Double-check with a multi-meter before you plug it in -- always double-check! You can get a multi-meter for less than $10.

Use two molex connectors on the same feed from your PSU. I've been running like this for 2 days now at "high" clock and the cables are barely warm. Don't skimp on fans, either. I have 4, two against the heat sink and another two on the other side of the board. I'm going to add two more on the back of the power board, too, it's quite warm.

Absolutely no different to the recommended setup, its still 2 lives and 2 neutrals [actually compared with my 2 lives and 4 neutrals]. The problem with burnt cables is some brands are selling knockoff cabling which isn't sufficient.

Quote from: sveetsnelda on May 24, 2013, 02:24:44 AM

Has anyone had an issue with their blade(s) where they'll mine for a while (minutes or hours) and reboot on a regular basis? Both of mine will run for an hour or so, stop hashing for a couple minutes, and reboot (triggers the failsafe). It's great that they reset automatically, but I'm losing a few minutes of hashing each hour. I'm running them through slush's stratum proxy and they maintain ethernet communication the entire time (the web page stays accessible and they're connected to the proxy).

I tried moving one to another pool (under another instance of the proxy using a different port) and it still does the same thing, although they now reset at different times. It seems like a stratum proxy or pool issue, but I'd expect it to pick back up after a disconnect (if that's what's happening). When the blades go down for a couple minutes, my GPUs keep hashing (although they aren't using the proxy).

I'm going to start digging into it, but I wanted to check to see if someone else ran into the same thing.

This is heat based.