Prolly being biased, but you guys should throw away the Rpi and switch to Lightningasic firmware, we now have an auto-overclocking feature that will overclock each individual chip (5 chips per Gridseed miner). Also the reject rate is close to 0, I've been getting 99.91% accepted running over 24 hours at Ghash.io.
BTW, Jack is making a test rig with 100 miners connected on a single controller, I will have a pic up to prove it.

18 awg would do, as are 3 wires x 7 amps (amp limit) = 21 amps.
Each blade will not absorb more than 15-17 amps overclocked.

But, still are close to the limit and the 18 awg will get a little warm.

I would go for 16awg to be safe for any unpredictable reason. 

thanks - hashing homes for us all

originally I was just going to shove them all in a PC case but they looked too good not to make it a display.. and without the fans and it being wireless networked I can move it and plug it in anywhere    

it runs Win7 so I just remote desktop into it to kick off the cgminers (will make a startup script on boot as well)

My advice for a simple non-reversible modification:
1) PS-ON : achieve this by using a tiny flattip to pop up pins 3&4 and bend them into contact with eachother. add a quick hit of solder to make this permanent

IMO 25 MHz increments work the best, one of my miners runs stable at 925 MHz, but throws HW errors at 856 MHz. The 25 MHz increments have the lowest PLL frequency and other PLL dividers set at 0. I have also found that the cgminer forks does not take in account the hashing time lost when finding an invalid nonce (HW error).

hm im on mac so this wont work! tried running that command but it doesnt work

redownloaded and it works but got a question mark next to a transaction, how and where do i run the salvagewallet command? really appreciate the help

So what about a thread of most profitable / best working pool to use with our Gridseeds?

what's working the best for you

However, this was an issue with KGW, which a lot of coins have implemented...as there aren't many Kgw coins out there that aren't effected by the timewarp.  

Use the salvagewallet command via console if you have stuck coins.

Your post is confusing. Lack of notice? Besides the giant red text and them blasting about how they are fixing the exploit on every avenue of social media they are involved with what type of notice would you like? A personal telegram  ? All the other scrypt coins that use kgw were having a melt down too, so if you didn't read about it through potcoin then perhaps you could have read about it while doing research on another coin. Perhaps you just don't read anything about the community, although a sr memeber with over 300 posts leads me to believe you are just upset that you lost coins and are striking out.

To answer your question, i don't think you can get them back. Live and learn and be more diligent in the future.

p2pool seems to be on a different fork than the official blockchain explorer.

Do I need to update the networks.py file?

What's wrong with scrypt hardware?  Thread title says mining rigs, not Bitcoin-only mining rigs....

the maximum custom difficulty you can set

hmm, nm, i'm not 100% sure about that actually, would have to look at the source again.   i think that's what it is, though.

btw, for any coin with, say, block times of 2 or 3 minutes or less, you should remove the following in data.py:

if best is not None:
            best_share = self.items[best]
            punish, punish_reason = best_share.should_punish_reason(previous_block, bits, self, known_txs)
            if punish > 0:
                print 'Punishing share for %r! Jumping from %s to %s!' % (punish_reason, format_hash(best), format_hash(best_share.previous_hash))
                best = best_share.previous_hash

...  first off, these blocks are too fast to have that anyway.  not to mention that the vast majority of the time this will be beneficial to your node.  if you build off of that old valid *share that's just getting punished because of a new block, all the other clients will follow your chain (as it'll be the longest).  this way you don't end up making a share some 3 seconds later and have some slow (or modified, heh heh) node build off the original share

    def should_punish_reason(self, previous_block, bits, tracker, known_txs):
#       if (self.header['previous_block'], self.header['bits']) != (previous_block, bits) and self.header_hash != previous_block and self.peer_addr is not None:
#           return True, 'Block-stale detected! height(%x) < height(%x) or %08x != %08x' % (self.header['previous_block'], previous_block, self.header['bits'].bits, bits.bits)