Blue Fury Support Thread.

[ssinc]

I just pencil modded a unit that was hashing around 500 MH/s... now it's running at 2.8-3 GH/s!

HW errors were about 20% at first and after 2 hours they're at 8%

[Slesh]

Hi
I just plugged 8 pcs. today.
1 of 8 do not use the Win driver as others (under WIn7) but shows me name of device "ATmega32U2 DFU".
And LED is not blinkinkg or shining ... seems to be death
Can someone help?

The others works around 2,4-2,5 in BFGMiner 3.2

thanks Slesh

[albon]

So when might we get a better firmware?

[HellDiverUK]

Pencil trick working here too.  Shame about the HW errors.

[Epinnoia]

I had 1 fury working seamlessly with 2 BEs on the same win7 x64 machine, running the most recent versions of cgminer.  Got my replacement fury today (for a total of 2), and AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.  And neither BE produces any results with that 2nd fury in the hub.  They just don't get along at all, and it seems more like a hardware conflict than code.  

So, I figured, let's go back to running the BEs with cgminer and the BF with bfgminer.  Still, same problem.  

Why would 1 fury work just fine with the two BEs, but not 2 furies?  

It's not a huge problem.  I can move the BEs to another computer if I absolutely must.  Is there's a special trick anyone has found to get more than one fury working with BEs in win7?

[Mudbankkeith]

I had 1 fury working seamlessly with 2 BEs on the same win7 x64 machine, running the most recent versions of cgminer.  Got my replacement fury today (for a total of 2), and AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.  And neither BE produces any results with that 2nd fury in the hub.  They just don't get along at all, and it seems more like a hardware conflict than code.  

So, I figured, let's go back to running the BEs with cgminer and the BF with bfgminer.  Still, same problem.  

Why would 1 fury work just fine with the two BEs, but not 2 furies?  

It's not a huge problem.  I can move the BEs to another computer if I absolutely must.  Is there's a special trick anyone has found to get more than one fury working with BEs in win7?

Check the power output on your hub.

[HellDiverUK]

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.  

Check the power output on your hub.

Agreed.  This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff.  Never any issues with power.   I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

[Epinnoia]

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.  

Check the power output on your hub.

Agreed.  This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff.  Never any issues with power.  I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

It's a 10 port hub with only 2 erupters and 2 furies in it.  And the erupters are the nearest to the power input, so likely to be getting their power before the BFs at the far end.

It doesn't feel like power issues.  It feels like a hardware conflict.  And I think I adequately isolated power from being the cause/issue.  I took the erupters out of the same hub, and put them onto a 4port unpowered usb hub plugged directly into the computer.  The issue persists.

It seems that one, and only one, of my two BEs is unaddressable while this newest fury is plugged in.  And it doesn't matter if they're even on the same root hub, or powered separately.

On a fresh reboot, BEs in one HUB, BFs in another (each hub plugged into the back of computer), both lights on the BEs were on until I started bfgminer which is configured only to use the BFs.  Once I started bfgminer, and the furies spun up, the light on one of the erupters turned OFF -- even though nothing was talking to it, and it's on another hub.  I closed out bfgminer, so nothing is mining now.  And now that light on the erupter is alternating between out and on for a little blink every so often (between 2 to 10 seconds).

And, just as I guessed it would do, as soon as I just removed the latest BF from its completely different HUB, the BE's light (on another USB port completely) went solid green.  It's just one of the two erupters, not both -- which baffles the hell out of me.  I am sure there is a logical explanation, but I don't think it has to do with power.  There's plenty of power.  This is a USB conflict of some sort, I think.

[Mudbankkeith]

AS SOON as I put it into the HUB, my AMU 1 (BE) unit gets continuous HW errors, and reports speeds of like 500+ ghps.  

Check the power output on your hub.

Agreed.  This screams power issues.

I run my hubs off the same PSU I run my Blades off, so there's 80A getting rammed up the hub's chuff.  Never any issues with power.  I did have similar issues when I ran the hubs off the power bricks supplied with the hub.

It's a 10 port hub with only 2 erupters and 2 furies in it.  And the erupters are the nearest to the power input, so likely to be getting their power before the BFs at the far end.

It doesn't feel like power issues.  It feels like a hardware conflict.  And I think I adequately isolated power as being the issue.  I took the erupters out of the same hub, and put them onto a 4port unpowered usb hub plugged into the computer.  The issue persists.

It seems that one of my BEs is unaddressable while this newest fury is plugged in.  And it doesn't matter if they're even on the same root hub, or powered separately.  

On a fresh reboot, BEs in one HUB, BFs in another, both lights on the BEs were on until I started bfgminer which is configured only to use the BFs.  Once I started bfgminer, and the furies spun up, the light on one of the erupters turned OFF -- even though nothing was talking to it, and it's on another hub.  I closed out bfgminer, so nothing is mining now.  And now that light on the erupter is alternating between out and on for a little blink every so often (between 2 to 10 seconds).

And, as just I guessed it would do, as soon as I just removed the latest BF from it's completely different HUB, the BE's light (on another USB port completely) went solid green.  

I have a 10 port hub that craps out with only one device plugged in.  The 4amp brick is now only feeding 0.4amp. (Binned the brick) The new brick fixed it.

try 2 erupters                          if it works:-
then 2 erupters + 1 BF              if it works:-
then 2 erupters + the other BF   if it works:-
then 2 BF                                    "
then 2 BF + 1 erupter                    "
then 2 BF + the other erupter          "        
then 2 BF + 2 erupters                   "

Post your results, but it still shouts power problems.

Edit:- USE ONLY YOUR USB2 PORTS on the PC

[Epinnoia]

I have a 10 port hub that craps out with only one device plugged in.  The 4amp brick is now only feeding 0.4amp. (Binned the brick) The new brick fixed it.

try 2 erupters                          if it works:-
then 2 erupters + 1 BF              if it works:-
then 2 erupters + the other BF   if it works:-
then 2 BF                                    "
then 2 BF + 1 erupter                    "
then 2 BF + the other erupter          "        
then 2 BF + 2 erupters                   "

Post your results, but it still shouts power problems.

Perhaps I was unclear.  

2 erupters works.  2 erupters with 1 fury works.  2 erupters with 2 furies causes one, not both, of the erupters to go incommunicado -- regardless of where that erupter is (ie. on another hub completely).  The 2 furies work with no erupters.  The BEs are not being fed the same power as the furies.  I have isolated the furies power from the erupters power.  I get the same behavior when the BEs are on the same powered hub as the BFs as I get when the BEs are on a completely different hub.  Both BEs look to be of the same type, with both saying rev 3.00.

I'll check on the USB version of the various ports being used, but I am pretty sure they're all 2.0.  It's a fairly old msi g33m mobo.

ON EDIT:  Yep.  USB 1.1/2.0 |  6 x USB 2.0  (http://www.newegg.com/Product/Product.aspx?Item=N82E16813130120)

ON EDIT(2):  With only 1 erupter, the results are actually interesting.  I had both furies hashing.  Added an erupter to another port/hub entirely, and the 2nd fury stops working.  Bizarre.  I'm back to my original determination:  1 fury works with erupters.  More than 1 fury doesn't (in my Win7 x64, at least).  

``cgminer.exe --usb "BF1:2"`` is what I am using to launch, since I have two furies. 

[zamot]

I've put up a new version of cgminer, 3.8.1 with improvements to the blue/red fury devices.

Any idea why i get this errors on BF1s ?

Code:

[2013-11-12 23:08:58] Hotplug: bitfury added BF1 5
 [2013-11-12 23:08:58] BF1 5 BF1RequestWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2013-11-12 23:08:58] BF1 5: Device disappeared, disabling thread
 [2013-11-12 23:08:58] BF1 5 failure, disabling!

And it is random on time and also on device.
I run cgminer 3.8.1 on Debian 7.1. It is not runing on RPi. There is no pencil mod.
There are 5 BEs and 5 BF1s, each od them on its own USB hub ( 3,5A powered).
It was try with connection of hubs into cascade ( BF1s hub connected to BEs hub and this to computer) and also try to connect hubs directly to computer and always the same result.
If i reset BF1s with reset switch on board it comes back.

[NocTurNalFX]

Got 2 red furys in the mail today.   Hashing away on cgminer  with 15 be's.  seem to be running good i suppose.   one is about 2.2g's  and the other hovering 2.0  both ~30% hardware errors.    Is there something  i can do to see less hardware errors?   they have been hashing for about 3 hours now.  one of them seems to be putting out a bunch of stale shares. 

[NocTurNalFX]

Just started to get Comms errors on the block erupters.   never had this problem before running them with the red furys.   I have them running on 2 Anker 9+1 hubs  if that makes a difference.  

every few minutes the green light on the BE's will come on steady for about 5 or so seconds.  not all of them at once,  but half of them  here and there.   Never had this problem before.  

Is there any commands I should be running with all of them running from the same cgminer instance ?  

[MaxGen]

Just got my miner tonight, shutdown minepeon and connected the BF.  Booted Mionepeon and it was mining at 145Mh.  Gradually went up to 500Mhz, then started dropping until it was no longer detected.

I cannot get this thing to mine on Mineoepn, Win7 or Win8.  Usign the WinUSB drivers on windows machines.  Tried BFGMiner on Minepeon,

All systems just throwing 100% HW errors.

Tries the reset on Windows systems, but it isn't helping at all

Any suggestions?

Code:

cgminer version 3.8.1 - Started: [2013-11-12 20:06:57]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:660  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 69  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 2 with stratum as user User_2
 Block: 676b62e1...  Diff:511M  Started: [20:06:57]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BF1 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:660 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-11-12 20:06:50] Started cgminer 3.8.1
 [2013-11-12 20:06:56] Probing for an alive pool
 [2013-11-12 20:06:56] Pool 0 difficulty changed to 2
 [2013-11-12 20:06:57] Network diff set to 511M
 [2013-11-12 20:06:57] Pool 1 difficulty changed to 3

Code:

bfgminer version 3.6.0 - Started: [2013-11-12 21:09:14] - [  0 days 00:00:20]
 [M]anage devices [P]ool management [S]ettings [D]isplay options  [H]elp [Q]uit
 Connected to stratum.btcguild.com diff 2 with stratum as user User_2
 Block: ...eb64e589 #269323  Diff:511M ( 3.66Ph/s)  Started: [21:09:14]
 ST:2  F:0  NB:1  AS:0  BW:[175/129 B/s]  E:0.00  I: 0.00 BTC/hr  BS:0
 1            |  1.35/ 1.62/ 0.00Gh/s | A:0 R:0+0(none) HW:137/100%
--------------------------------------------------------------------------------
 BPM 0:       |  1.31/ 1.59/ 0.00Gh/s | A:0 R:0+0(none) HW:153/100%
--------------------------------------------------------------------------------
ing():396
 [2013-11-12 21:09:13] Probing for an alive pool
 [2013-11-12 21:09:14] Pool 0 http://stratum.btcguild.com:3333 alive
 [2013-11-12 21:09:14] Network difficulty changed to 511M ( 3.66Ph/s)
 [2013-11-12 21:09:14] Pool 1 http://stratum.bitcoin.cz:3333 alive
 [2013-11-12 21:09:14] Pool 1 is hiding block contents from us

[loumatrix]

Hi,

Just wanted to say thanks to all that helped me getting the BlueFury's working. I got it working on the PC (Win8.1x64) and Minepeon.

Also now that it is working. After running a sample run for 10 minutes there are a load of errors. Is this normal or do I have defective miners?

Here is a screenshot.

https://i.imgur.com/UvrHrsL.jpg

Thanks.

[eousphoros]

Code:

cgminer version 3.8.1 - Started: [2013-11-12 21:43:52]
----------------------------------------------------------------------------
 (5s):16.88G (avg):16.77Gh/s | A:84239  R:352  HW:3356  WU:233.8/m
 ST: 2  SS: 0  NB: 45  LW: 108588  GF: 0  RF: 0
 Connected to pool diff 16 with stratum as user 1
 Block: 446cc771...  Diff:511M  Started: [03:46:42]  Best share: 213K
----------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 AMU 0:                | 335.8M/336.2Mh/s | A: 1660 R:  0 HW:  17 WU:  4.7/m
 AMU 1:                | 335.6M/336.1Mh/s | A: 1770 R:  0 HW:  20 WU:  4.5/m
 BAJ 0:  max 50C 3.34V | 8.328G/8.144Gh/s | A:40541 R:208 HW: 473 WU:112.7/m
 BF1 0:                | 2.666G/2.632Gh/s | A:13398 R: 48 HW:1002 WU: 37.4/m
 BF1 1:                | 2.602G/2.616Gh/s | A:13086 R: 64 HW: 917 WU: 36.6/m
 BF1 2:                | 2.701G/2.703Gh/s | A:13832 R: 32 HW: 929 WU: 37.9/m
----------------------------------------------------------------------------

All of the hw errors make me kinda sad.

[jml]

I am using bfgminer 3.6 and I have noticed the following with a D-Link 7 port hub 3Amp. OS is Raspbian wheezy.

- I am only able to plug in 2 bluefury (BF) USB sticks within one USB hub.
- Plugging more than 2 BF's on a D-Link USB hub will not work with bfgminer; I get 2 sticks with red LED's and the other 2 either yellow or orange LED's.
- BF USB sticks cannot live within the same USB hub with any combination of erupter USB stick; BE sticks won't be detected. They must be plugged elsewhere on a different hub but not within the same hub.

Has anyone noticed the same problem with my configuration?

[jml]

Code:

cgminer version 3.8.1 - Started: [2013-11-12 21:43:52]
----------------------------------------------------------------------------
 (5s):16.88G (avg):16.77Gh/s | A:84239  R:352  HW:3356  WU:233.8/m
 ST: 2  SS: 0  NB: 45  LW: 108588  GF: 0  RF: 0
 Connected to pool diff 16 with stratum as user 1
 Block: 446cc771...  Diff:511M  Started: [03:46:42]  Best share: 213K
----------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 AMU 0:                | 335.8M/336.2Mh/s | A: 1660 R:  0 HW:  17 WU:  4.7/m
 AMU 1:                | 335.6M/336.1Mh/s | A: 1770 R:  0 HW:  20 WU:  4.5/m
 BAJ 0:  max 50C 3.34V | 8.328G/8.144Gh/s | A:40541 R:208 HW: 473 WU:112.7/m
 BF1 0:                | 2.666G/2.632Gh/s | A:13398 R: 48 HW:1002 WU: 37.4/m
 BF1 1:                | 2.602G/2.616Gh/s | A:13086 R: 64 HW: 917 WU: 36.6/m
 BF1 2:                | 2.701G/2.703Gh/s | A:13832 R: 32 HW: 929 WU: 37.9/m
----------------------------------------------------------------------------

All of the hw errors make me kinda sad.

Same as me, I am getting a lot of HW errors. PXY0 is an ASICminer blade overclocked and has a far less ratio between accepted shares and HW errors.

Code:

PXY 0:       |  9.87/12.82/12.46Gh/s | A:2724 R:56+14(1.9%) HW: 393/.91%
 BPM 0:       |  2.38/ 2.38/ 2.28Gh/s | A: 486 R: 3+ 0(.63%) HW: 302/3.8%
 BPM 1:       |  2.35/ 2.34/ 2.17Gh/s | A: 465 R: 0+ 0(none) HW: 310/4.1%
 BPM 2:       |  2.36/ 2.36/ 2.14Gh/s | A: 425 R: 0+ 0(none) HW: 293/3.9%
 BPM 3:       |  2.32/ 2.32/ 2.21Gh/s | A: 443 R: 3+ 0(.68%) HW: 334/4.3%

[mogrith]

Huuuummmm may have used a little too much pencil
bfgminer version 3.5.1 - Started: [2013-11-12 21:11:42] - [  0 days 00:37:44]
 [M]anage devices [P]ool management S ettings [D]isplay options  [H]elp [Q]uit
 Connected to pool1.us.multipool.us diff 96 with stratum as user mogrith59.mogri
 Block: ...6886a3ab #214221  Diff:143k ( 1.02Th/s)  Started: [22:48:40]
 ST:2  F:0  NB:31  AS:0  BW:[ 11/  0 B/s]  E:65.29  I:  240mBTC/hr  BS:698
 1            |  3.28/ 3.19/ 2.12Gh/s | A:9 R:1+0( 10%) HW:379/ 23%
--------------------------------------------------------------------------------
 BPM 0:       |  3.19/ 3.19/ 2.12Gh/s | A:9 R:1+0( 10%) HW:379/ 23%
--------------------------------------------------------------------------------

this one has less (On Minepeon 0.2.4)
Devices
Name   ID   Temp   MH/s   Accept   Reject   Error   Utility   Last Share
BPM   0   N/A   2572.598   3527   29 [0.81%]   427 [5.63%]   16.824   22:51:46
Totals   1      2572.598   3527   29 [0.81%]   427 [5.63%]   16.824   

[Mudbankkeith]

I am using bfgminer 3.6 and I have noticed the following with a D-Link 7 port hub 3Amp. OS is Raspbian wheezy.

- I am only able to plug in 2 bluefury (BF) USB sticks within one USB hub.
- Plugging more than 2 BF's on a D-Link USB hub will not work with bfgminer; I get 2 sticks with red LED's and the other 2 either yellow or orange LED's.
- BF USB sticks cannot live within the same USB hub with any combination of erupter USB stick; BE sticks won't be detected. They must be plugged elsewhere on a different hub but not within the same hub.

Has anyone noticed the same problem with my configuration?

9 Blues + 1 Red on 2 D-Link hubs using a Pi with MinePeon (angled extenders on sockets 1 & 7) no space to try erupters