Topic: Blue Fury Support Thread. - page 12. (Read 89623 times)

Wow, terrible pictures.    Putting yellow boxes round blurs doesn't really help either. 

getting more sticks around thanksgiving I will try then

Probably just trigger happy then for slower hardware. I've relaxed the timeout duration in git master but if you've lost interest that's fine.

fuck it I will stick with bg miner the pencil mod has been rock solid 2.61  4% error rate.   nice spot on the resistor issues

I think I may have identified a production issue...

While replacing the resistors on R15, I noticed the furies with extremely high error rate or extremely low GH/s rate all had one thing in common versus the ones that sat comfortably around 2.2GH/s-2.3GH/s with 1-3% errors.

What I found wasn't limited to just Blue Fury either, also Red Fury.

Now, I'm not entirely sure this would be the cause of the issues, but I can say if the production machine was the slightest off during production, it could have caused an issue. On the ones that seeming were hashing fine, the solder points for R15 were spot on rectangular points for each end. Now for the ones that all had issues, the soldering points, well, weren't... see the pictures below. Each picture is of a different fury, the first one was the one that I would see 900MH/s to 1.3GH/s with 41% errors, the second one I would 35-50% errors, the third one 25-35% errors -- apologies for the shitty cell phone camera, was all I could find while in the middle of replacing the resistors.







I'm pretty sure you can see the obvious differences between the pictures, where as the other furies I replaced the resistor were non-problematic had no issues and R15 looked to be a dead-on rectangular solder point, no randomness like what is found in these pictures.


Edit:
After replacing 9 R15 resistors with 9.53k ohms, running for 30 minutes (and being extra careful on the soldering points for the ones above mentioned):


I am very happy with the results thus far...

I replaced R15 with a Vishay 9.53k ohms SMD 0805 Resistor Part No# TNPW08059K53BEEN from Mouser (link) also available at DigiKey (link).

Update:

Since I haven't heard from ssinc in awhile concerning my replacement for at least one of my fury's (which would always sit at around 1GH/s with 41% errors, always 41% errors, even after pencil mod).

After a 9.53k resistor, 2.50GH/s with 7.5% errors...  (and the error % keeps going down the more it's hashing atm)
So, I'm considering that one fixed...


I've got two with some insanely high error %'s, which I'm going to put a 9.53k resistor on and see if that cures their issue. Granted they are running at 3.62GH/s and 3.34GH/s, however if the 9.53k resistor fixes the high error rate and calms it down to 2.6GH/s I'll be a happy person.

Just got a new shipment of resistors in...

Decided to go with 9.53k on R15, looks like it's a sweet spot 2.6GH/s after errors, sometimes jumps as high as 3.13GH/s, but for the most part sits at 2.6xGH/s with 1% HW Errors. So far it seems to be the steadiest out of all the other furies (some with 10k ohms resistors, some with pencil mod) in terms of GH/s and error %.

Kind of awkward in a way, as with 10k on R15, they sit at a high hash rate, but jump a lot and sometimes a high error rate. Wish I would have bought more 9.53k resistors, as I think I only picked up 10 to play with.

That's strange, cgminer re-hotplugs soon and that happens few times but on the end BF1s are ZOMBIEs
If i start cgminer -n in another windows and this cgminer with ZOMBIEs is still running it see all BF1s, and also with lsusb i can see BF1s, just in the "working" cgminer they are disconnected.
Damm and with 3.8.3 it looks even worser than with 3.8.1

If the device disappears and shows up as ZOMBIE and never re-hotplugs, there's nothing there on the USB any more for cgminer to talk to, so something is causing USB flakiness there. Check what 'dmesg' shows you after this has happened. There's not much the software can do if the device is effectively disappearing from the USB hub. If on the other hand the device is still there and it's just cgminer dropping out, it's possible that cgminer is too trigger happy - but if that were the case it would re-hotplug soon after.

Today i "upgraded" to version 3.8.3 and i still get this LIBUSB error:
Does anyone else have this issue ?

I would like to know whom it is who makes these Red Fury and Blue Fury USB miners.

So far my experience of them has been absolutely rubbish.

So far I've had 3 Blue Fury usb sticks, 1 was DoA, the other died inside a few days.  Had 1 replacement so far, waiting for an RMA for the other..

The one I do have does a measly 1.981 Ghps through CG Miner. I thought the Blue Fury was supposed to do 2.2 to 2.7 Ghps?

So far also had 3 Red Fury sticks.. 2 working , 1 @ 2.15 Ghps and the other 1.98 to 2 Ghps when they are supposed to be 2.4 to 2.6 Ghps.

The third one arrived today and is DOA.

Getting really annoyed with the poor quality of these miners considering they cost over £100 a piece.

Is there some reason why they do not get their advertised speed?

And would also like to know why, even after installing/extracting and using the BF1.ini file, the Virtual COM port driver and a WCA driver etc BFGMiner still can't find them on my computer and so I've had to use zadig to overwrite the driver to the winusb one and mine with CG Miner, which I have to restart several times whenever I need to restart because it won't/can't get onto the pool I'm with (Bitminter)

I'm starting to think there is something dodgy going on when everything is so cloak and dagger - like who makes these things.

I've tried all of the miners on 3 different computers. The old Core 2 Duo one I'm using as the mining rig, my old 1366 rig which I gave my dad and my new 1155 gaming rig. Same problems across all three.

Well, I updated MinePeon was CGMiner 3.8.3 also, was helping out Maidak with his setup & both systems (his and mine) keep zombie'ing all devices within several minutes of running on 3.8.3...

I will have to give cgminer a try.

as for the pencil mod  2.73 gh/ 2.70 gh  /2.58 gh   vs   2.37 gh /2.35gh/ 2.29gh     


    for newbies the third number is the after error number and is the money number.  whomever invented the mod deserves my thanks.

New version of cgminer out, 3.8.3 with minor improvements for these devices.

did the pencil mod jumped to 2.62 from 2.29.  my hub has 9 be's and one red fury. i am using a 10 port aitech black all aluminum hub with a 5amp 12 volt brick.  before the mod my k-watt meter was 34.7 watts it is now 35.1 watts. i did 3 pencil rubs with light pressure.  i need to get more sticks.  but .4 watt = .4gh boost not bad.

I went back traced the spot 3 more times now read 2.73/2.62/2.51.  the  power went up some  more and a fan is a must.  but looks like running this at 2.6 is possible with pencil trick.
  I did the second mod hot since I am a bit more comfortable with doing it. I am thinking ten of these at will pull around 38 watts  at the plug hashing at 26gh.  pretty good numbers

ok so  I have them working in cgminer the only problem now is that they are only running at like 1GH and another running at 900MH/s and one that seems to be ok.

Any ideas how to fix this problem as works perfectly fine using bfgminer

You took out GPU mining? I'm disappointed. 

just speaking with a colleague, if the current draw is correct, we could see some USB hubs get overload with too many modded furies.

I'm going to check the draw against a usb 2 port tonight when I get home.

Current cgminer has no GPU mining code so it will only mine on devices you consciously set up by associating the WinUSB driver with them.

This keeps happening how do I fix it? http://gyazo.com/3ee21d9ec6e4984c6b6d5e51a6ef665e