The PCB program shows:

Component Class:      IC
Device Type:          FERRITE BEAD_FB0805_300OHM@100M
Value:              300ohm@100MHz,1.5A

Nice job jekv2!  I know how hard it was to do mine.  You have good skills to keep it so professional looking.

Thanks ZiG. 

-----------------------------

Anyone going to undo the vmod 3?  I plugged in 100kh/s (gain), 12 watts (extra watts), 10 cents kw/h (my cost) in coinwarz. 

For LTC:  Revenue $0.04 / Profit $0.01 / $0.03 for electricity

I think I'll just solder the two bridges for vmod1 to undo vmod3 on all my gridseeds when I have time.

One of my modded gridseeds quit yesterday. There's no real obvious signs of a short or any damage.
The fan doesn't spin.  When I plug in 12v the fan moves a fraction.  USB seems to work.
If I plug this gridseed into the psu with all the other gridseeds the psu shuts off.

Would a failed mofset mosfet cause symptoms like this?  I ask because there is a very small bump on the top of one of the mofsets mosfets.

Any ideas?
Are there any tests I can do?

What versions / builds of cgminer or bfgminer? 
The cmds are different.  Could be -S zus:all or -S zeus:/dev/ttyUSB2 (notice zus & zeus) depending on which version of bfgminer for example.

I just learned something looking at your screen shot.  I didn't realize the coinking graph keeps tracking hashrate as long as you're logged on.  I've been logging on and checking then exiting.  the graph was only a couple of minutes.

It'll smooth out with cgminer.  I'm still running the first release. 

That's annoying. I hope you find the extenders quickly.

Looks like Zeus has posted some software updates:
http://zeusminer.com/user-manual-ver-1-0/

Still CGMiner 3.1.1

Updates: 2014.06.20
Use Zeus driver instead of Icarus.
Use ncurses as default.

I think it is the source they posted on Github.

There's something different with BFGMiner (all builds).  It can work fantastic on some pools, probably most pools.  But, on some other pools, it doesn't perform as well as CGMiner.   It could be problems on the pools.

I left 2 BFGMiner instances and 1 CGMiner instance running today on the same pool (3 Fury's).  I came back to a "wall of rejects" on the the two BFGMiner instances and both miners were temporarily banned from the pool.  The CGMiner instance was still running ok.

Well a Fury would net like 64 cents a day mining straight LTC right now according to CoinWars. 71 cents mining Doge. It goes lower every couple of days.  So it won't surprise me at all if people stop buying equipment at current prices.

1,601 kH/s 24hr average on the pool................. actual run time 24 hrs and 40 minutes.  That's about the same as previous builds for me.
3rd hash rate number was 1.63 Mh/s, then 1.62 Mh/s, now 1.61 Mh/s.  

Wish I could help but I only have Fury's.....
Someone should be able to post a photo of how the dip switches should be set.

That's a good summary Ktulu1.
This post has a photo of the resistor: https://bitcointalk.org/index.php?topic=644921.msg7205108#msg7205108

The frequency limit is 382 in most software builds now.  It is either caused by Zeus chip design or Zeus chip driver I think. 

With darkwinde's build:
--scrypt then the pool and user info, then --zeus-cc 6 --zeus-clk 382 --zeus-rc 300 -S zeus:\\.\COMXX

With nwoolls / Luke-jr 4.30 build I had to specify the com port to get it working as it didn't detect either Fury.  If anyone is having trouble getting it going maybe try that.
bfgminer.exe --scrypt -o (pool user & password) --set zus:chips=6 --set zus:freq=382 -S zus:\\.\COMXX
However, it did not work well with the multi coin pool I tried.  

382 clock is for volt modded.  Try 340 for stock.

I put 1 Fury on a very stable straight LTC pool running the new Darkwinde BFGMiner 4.3.1https://litecointalk.org/index.php?topic=20477.0 to test for 24 hrs.
So far, at 10 hours, it seems a bit faster.  The 3rd hashrate number in BFGMiner is steady on 1.63 Mh/s. I'll post the 24 hr average number when I get it.

These are harder to get running the way you like right away than Gridseeds for example. (my opinion)
But, once you find the right combo of pool & software they run well.

I don't set diff on either pool.  The pool adjusts automatically based on my miners.

Get a copy of beta 1 too.  You might find it works best on some pools.

350 might be too high.  Try 340 or try a different build.
Your rejects are high:
A: 593920 R: 26624

Mine look this after approx 12 hrs.
A:1067162 R:7752 WU:1507.6  Beta 1
A:1134848 R:1536 WU:1489.2  Beta 2

That's two different pools.  Beta 1 or 2 will work on one pool.  The other pool get a lot of rejects with beta 2 so I use beta 1.
Are you getting what people are calling a wall of rejects once in a while?  That's what I got on one pool with beta 2.  But beta 1 works on that pool.

Beta 3 was released last night: - Dmaxl's CGminer-4.3.5 Beta 3

I like your numbers!

I downloaded and burned the Starminer image yesterday.  I haven't mined with it yet - just booted up the Pi.  I think I'll end up using it.

Dmaxl's beta 2 is pushing the 24hr avg up for me.



I think it was 1,586 kh/s when I started using it 4+ hrs ago and now it is 1,601 kh/s.  WU is at 1,542/m after running 4+ hrs.
I was going to switch pools but I think I'll let this run 24 hrs just to see what it peaks at.

Have you tried different pools?  I've found that with these Zeus chip devices you really have to find the right combo of pool + miner software.

Is your OS Windows?

This BFGMiner 4.2.2 https://litecointalk.org/index.php?topic=20477.0 as noted by jekv2 can work really great on some pools.  I can get 1,600 kh/s average on Litecoinpool (straight LTC) with my overvolted Fury.

Dmaxl's first windows cgminer build also works well for me: CGMiner v4.3.5.beta1release  I managed to get one Fury to 1,588 kh/s average on Litecoinpool so almost as fast as BFGMiner 4.2.2.  Cgminer 4.3.5 seems to be compatible with more pools though.  I'm running 1 Fury on CoinKING with Cgminer 4.3.5 beta 1.  I couldn't with BFGMiner 4.2.2.

I tried Dmaxl's second windows cgminer build -> CGMiner v4.3.5.beta2 release on CoinKING but switched back to the first release because it looks like I was getting a few more errors.  It might work better for you.

The options are set differently in BFGMiner 4.2.2 and CGMiner 4.3.5

CGMiner 4.3.5 --zeus-clock 328 --zeus-nocheck-golden --zeus-chips 6 --scan-serial //./COM4
BFGMiner 4.2.2 --zeus-cc 6 --zeus-clk 328 --zeus-rc 300 -S zeus:\\.\COM4

Edit: dmaxl's CGMiner v4.3.5.beta2 release might make it to 1,600 kh/s for me.  My 24 hr avg poolside is heading up.  1,591 kH/s right now.   

That's volt modded.  Approx 7.67k resistor value. 1.4v to the chips.  And extra fans for cooling https://bitcointalk.org/index.php?topic=644921.msg7354916#msg7354916