Looks like DOA (dead on arrival) to me... I hope you can get them replaced/refunded.
Good luck

Can you try the 'problem' boards one at a time on a separate PC?  (just to avoid the USB port assignment and potential conflicts with other boards/devices).

Another issue that I had is that I saved the cgminer settings (into cgminer.conf), but I was changing the Drillbit board settings through a batch file, so there was a conflict between the saved conf file and the instructions in the batch file.  This resulted in a few cases of ZOMBIE when I restarted cgminer after some drillbit option changes.  Renaming (or deleting) the .conf file solves this.

Good luck

With added cooling, tried some overclocking

Now with fans on both sides of the 8board.

Don't use the miniplane for now.  See Swimmer63's post before your one (each board connected separately to power and USB)

looks like you need to connect each board separately to USB2, without the mini-plane that still has a firmware fix on the way.

I run a single board, so did not have this issue.

Running a mix of BE's, RF/BF and other devices on Win7/64.  Each type is on a separate instance of bfgminer (or cgminer for the Drillbit Thumb which doesn't have bfgminer support yet).  Just using the erupter:all for the BE's and bigpic:all for the RF/BF devices.  When the 1st instance is running (in my case BE's), the 2nd instance of bfgminer has a brief message that some COM port (which is used by the 1st instance) is not accessible, but otherwise it runs fine.  Each instance is invoked by a simple batch file, but you can probably also create a standard 'short cut' where the target line has the same parameters.

Cheers

same here, threshold crossed some hours ago, but the payout is still not happening....

Managed to run 2 separate instances of cgminer using the --usb :1 addition to the batch files calling up the Thumb and the 8Board.  Now the Thumb can have its different setting and the board its unique setting.
The single board is connected to a spare PC power supply, the 4 pin Molex powers the board and the USB connector goes to the controlling PC.  A small fan cools the heatsink side.  My board came without the small heatsinks on the MosFETs (QF1 - QF3) which are getting quite hot.  I tried some overclocking, but now wound it back to stock settings as I feel that it is getting too hot with the present cooling arrangement.

Cheers

I have one problem when trying to run the Drillbit8 board on the same pc that runs the Drillbit Thumb - can't get 2 separate instances of cgminer to run with separate settings for the 8board and Thumb.  The 1st instance 'captures' both devices and the 2nd instance is left with 'nothing'.  Does anyone know how to convince cgminer to run a single device out of a few similar ones?  (on Win7).  Both are seen by device manager as 'thumb', the only difference being in the detailed properties where the hub/port are listed, but I don't know how to apply this in Cgminer.

This is necessary if you want to run non-stock settings, which are different for each.  If I run them both in 'stock settings' there is no problem (other than the Thumb getting quite modest hashing rate).

Cheers

I'm in Sydney.  It's getting warm but not very hot.  I have a small fan that is pointed at the heatsink.

Cheers

Just got my 8 board and it's hashing away... first few minutes...


Thanks Barn!!!

 

I'm running many BE's, 2 RF's, 1 BF using separate instances of bfgminer 3.6.0 one for the BE's and one for the BF/RF.  The BF/RF are on a separate hub (but I don't think that this is essential).  On the same hub of the BF/RF there is also a Drillbit Thumb (also using the Bitfury chip, but with a different interface and driver), which runs under cgminer (and Zadig installed winusb driver).  This combination has been running well for days.  The only 'hiccup' was with detection of some of the RF/BF after restart, which requires removing sticks, re-insertion one by one and re-starting bfgminer.  Also running the device manager 'cleanup' procedure (see [url]https://bitcointalk.org/index.php?topic=300638.0]ich requires removing sticks, re-insertion one by one and re-starting bfgminer.  Also running the device manager 'cleanup' procedure (see https://bitcointalk.org/index.php?topic=300638.0) helps.  All this runs under Win7/64.  I described the batch files used for the different instances earlier in this thread.

Cheers

Congratulations!!!
(and hope to have my 8 board soon

The minimum payout threshold used to be 0.01 BTC, however the FAQ now says 0.05 BTC.  This is why people including me thought that automatic payouts are not happening.
This is higher threshold unfair to most of us, who are small miners and would take a week or more to get to this threshold.  Slush, please go back to the original minimum threshold of 0.01.

Kabopar

The OP of this thread has instructions how to reflash the device https://bitcointalk.org/index.php?topic=319419.0.  This maybe what you are looking for.  (It's the target binary file for the micro-controller running the Red Fury (which is supposed to be identical to the Blue Fury, except for pcb/heat sink color scheme)).

Cheers

Enjoy your new toy!  Check out the overclocking results on the previous page, these thumbs can Fly!

Cheers

tk1337,
Thanks for this update.  I share the appreciation of the Big Picture team and others behind the BitFury based USB miners, hoping that they will improve in future production runs.  It is understandable that with the time pressures and small production run such quality 'bugs' can occur. If the copper tracks had incorrect dimensions on some boards causing partial shorts, that could also be production quality issue that needs to be addressed for the future runs.  It is great that you managed to revive the non-performing sticks and uncovered these additional issues in the process.

Cheers

tk1337,
Thanks for the photos (and the improved ones ), as well as the rest of the investigation.  Looks like the Quality Assurance department was asleep as the rush to build and ship the units took priority.  Hopefully Beastlymac and other members of the Blue/Red Fury organization will take this into account if/when there are additional batches built.
Just wondering if some of the inconsistencies that you found were in the 'solder mask' (the paint layer that covers the copper tracks to prevent solder adhesion during wave soldering or SMT placement) or were the tracks partially missing or shorting?

Cheers

Reward payouts not happening again.... now more than 2 hours above the threshold.... Slush, pleaaaaase

You could try the device manager 'clean up' procedure described in https://bitcointalk.org/index.php?topic=300638.0
I'm running more than 40 USB devices, with 8 hubs.  You need to be patient and connect them gradually, make sure that they are recognized before connecting the next lot.

Cheers