Blue Fury Support Thread.

[jdkackley]

I'm having no luck at all with my Blue Fury and BFGMiner  


EDIT: Well I was able to get my miner running but I had to run it on a separate PC with the supplied BFGMiner software. This sucks. I thought the latest version from Luke Jr today was able to run both erupters?

[1714777398]

1714777398

[1714777398]

1714777398

[underachiever]

Using bfgminer 3.4 on Xubuntu I got 2.3Gh/s with no errors.

Moved to bfgminer 3.4 on RedHat (RHEL6) and still get 2.3Gh/s but now see the ~60% error rate.

One interesting thing I noticed:
on Ubuntu I had to use "-S bitfury:/dev/ttyACM0" - but...
on RHEL I had to use "-S bigpic:/dev/ttyACM0"

Yet the Windows miner uses BF1: ...  why all the differences?

[pyra-proxy]

Using bfgminer 3.4 on Xubuntu I got 2.3Gh/s with no errors.

Moved to bfgminer 3.4 on RedHat (RHEL6) and still get 2.3Gh/s but now see the ~60% error rate.

One interesting thing I noticed:
on Ubuntu I had to use "-S bitfury:/dev/ttyACM0" - but...
on RHEL I had to use "-S bigpic:/dev/ttyACM0"

Yet the Windows miner uses BF1: ...  why all the differences?

My windows 7 miner catches them with bigpic lol.....  this is odd indeed......

[Taugeran]

I got my first HUGE problem solved with the help of Epinnoia, Thanks a bunch!  So bfgminer would not for the life of it be able to communicate on these, I'm on Win 7 and followed the op directions to the letter.  The problem was 2 fold, 1st the port had a bad default baud rate (9600 instead of the 115200 which Epinnoia recommended to me), second was even after this changed I had to make sure I pressed the "RST" button to make the change take effect (even unplugging/replugging these in did not cause the change to help).

Now for my next HUGE problem..... 60% + HW error rates an all of these devices....

Thanks for the help in advance!

they really are spitting out the ~2 Ghash/sec in addition to ~60% garbage. cgminer just ignores the garbage but bfgminer reports it as bad nonces


its just fine

[mstang83]

If they can fix the errors with a firmware update, these things will really rock!

[Taugeran]

If they can fix the errors with a firmware update, these things will really rock!

they do rock as is and fixing the garbage won't increase the hashrate like from 2.1 to like 3 something.

bfgminer is just passing along all the extra data they spit out, along as "HW" error even though the ßitfury chip didn't generate it :/ all this is a lot of guestimation based on my embedded systems tinkering. and the fact that these don't support polling functionality (was a bug in bfgminer code that presented itself on mac)

[OleOle]

Ok, 12 miners received with thanks from Dabs. Thanks to all at BPMC for getting these out to us.

I was hoping to post a picture of them working here but having great difficulties loading the driver using the instructions provided above on the OP. Is there any other place that I can access the driver file please? Following the instructions for Win7x32 seems to lead me to a situation where access to the driver is denied 







Any input you have will be greatly appreciated. I'll keep tweaking, I know this is a live situation with a real group effort to get these Blue Furies working to the max. I can't wait to get them working and hashing, then start messing around with them to really amp up their hash rates!

Thanks folks

[ripmax]

Ok, 12 miners received with thanks from Dabs. Thanks to all at BPMC for getting these out to us.

I was hoping to post a picture of them working here but having great difficulties loading the driver using the instructions provided above on the OP. Is there any other place that I can access the driver file please? Following the instructions for Win7x32 seems to lead me to a situation where access to the driver is denied 



http://anonymouse.org/cgi-bin/anon-www.cgi/http://anonymouse.org/cgi-bin/anon-www.cgi/http://img33.imageshack.us/img33/4920/dya9.jpg



Any input you have will be greatly appreciated. I'll keep tweaking, I know this is a live situation with a real group effort to get these Blue Furies working to the max. I can't wait to get them working and hashing, then start messing around with them to really amp up their hash rates!

Thanks folks

You setting up for BFMiner or CGminer as there is different driver methods for each

[tk1337]

Ok, 12 miners received with thanks from Dabs. Thanks to all at BPMC for getting these out to us.

I was hoping to post a picture of them working here but having great difficulties loading the driver using the instructions provided above on the OP. Is there any other place that I can access the driver file please? Following the instructions for Win7x32 seems to lead me to a situation where access to the driver is denied 







Any input you have will be greatly appreciated. I'll keep tweaking, I know this is a live situation with a real group effort to get these Blue Furies working to the max. I can't wait to get them working and hashing, then start messing around with them to really amp up their hash rates!

Thanks folks

that access denied your getting is because the driver file is set to encrypted... see post #46 https://bitcointalk.org/index.php?topic=319419.msg3467670#msg3467670

[OleOle]

You setting up for BFMiner or CGminer as there is different driver methods for each

Ok, well, I'm maybe trying to do the impossible but what I'm wanting to do is to get both Blue Furies and Block Erupters working from the one version of BFGMiner. On the group buy thread that I used to acquire the Blue Furies (big thanks once again to Dabs for all his help), ssinc was kind enough to refer me to this driver link:

Use the Zadig driver : http://sourceforge.net/projects/libwdi/files/zadig/

I've downloaded the drivers, they work flawlessly, these seem to self-install, just make sure that the driver install program that pops up recognises all your Blue Furies, if it doesn't, turn the hub off and on so that the total number you have are visible in the program before hitting 'install'. Anyone who has used more than a handful of Block Erupters will know how to turn hubs on and off until their hands bleed, at least that was my experience getting them to all to be recognised by BFGMiner. But when they do, it's a beautiful thing and BFGMiner works superbly - given that, I'm sticking with BFGMiner and I'm sure that if I can get the target line correct, then, hopefully, both the BF's and BE's will be able to run side by side. And if anyone else uses the Orico 10 port hubs, you know it will be one helluva light show

In case it helps, I've always followed the instructions from BTC Guild who spell it out how to get Block Erupters and BFGMiner working with the BTCG pool here:

https://www.btcguild.com/index.php?page=support&section=blockerupter

So the plan is now, to somehow tweak those parameters so that BFGMiner works with them both BE's and BF's. That could just be naive and if so, at least I get to say it first. Maybe I can run two copies of BFGMiner, one to recognise the BE's and one to recognise the BF's, but that's for later.  In the meantime, there seems to be something worth looking at with regards to - S BF1 or something... I dunno yet, but I think avoiding some conflict with the BE command seems to be where I'm at.

There's plenty of good people working on this, so it might take some time but I'm reasonably confident of a positive outcome.

Thanks to everyone who has posted and helped so far, it's really appreciated.

[Beastlymac]

NEW VERSION 3.5.1, NOVEMBER 7 2013

Human readable changelog:

• Bug fixes only.

Full changelog:

• Bugfix: make-release: Add README.GPU document
• Demote USB string fetch failure to LOG_DEBUG since it is rather common
• Bugfix: RPC: devscan shouldn't be available to read-only access
• Bugfix: bigpic: Ignore the bitfury chip's counter as best we can
• Bugfix: bigpic: Accept other delimiters in Bitfury BF1 product string in autodetection
• Bugfix: Fix VCOM/fpgautils build check
• Bugfix: Only include VCOM code when VCOM/fpgautils support is being built
• Bugfix: Reimplement scan-serial "all" keyword
• Bugfix: bitforce detect: Close device after ZGX failure
• Bugfix: Define lowl_usb even if libusb support is omitted, since VCOM and HID drivers check against it for warnings

[JayCoin]

I have 50 running at 90Gh/s total. Two throw tons of hardware errors. Shares found on same two are very low even though hashrate is reported normal.

These things run very cool. Begging to to overclocked. Hoping to be able to tweak in the future.

[Beastlymac]

I have 50 running at 90Gh/s total. Two throw tons of hardware errors. Shares found on same two are very low even though hashrate is reported normal.

These things run very cool. Begging to to overclocked. Hoping to be able to tweak in the future.

Pictures?  I posted above how it is possible to hardware overclock. Firmware over clocking might be available in the future I just don't want to cause more issues that would then need to be fixed.

[MadHattr]

I was able to get this working with my usb erupters fairly easily, win7x64. I only have 1 of the BF and 25 of the usb erupters they are currently playing well with each other. Using bfgminer 3.2 the BF was found with the -S BF1:all to start then after it loads I just do M then + to add more devices doing erupter:all and it adds my 25 along side the BF. Was running on 3.2.0 for about 5 hours today with 2.3GH/s from the BF. With 3.5.1 it does report some HW errors (just after 5 min of running), 3.2.0 did not during its run.

[philipma1957]

I have 1 red fury and it has the time out issue on bit minter. i did get it to be recognized and the device manager says the device is ruining properly.  does anyone have a blue or red fury running on bitminter

[Zeek_W]

I have 1 red fury and it has the time out issue on bit minter. i did get it to be recognized and the device manager says the device is ruining properly.  does anyone have a blue or red fury running on bitminter

Yeah but I use BFG - the java app doesn't seem to like them on my windows computer.

[mijanur]

Bluefury trial one
test on

Windows 7 - CGminer 3.7.2 (Hotplug after running zadig)










cgminer cmd used
cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u pssSuperTedpss -p x

  gradually built up speed to 2.2 gigahash

note:
1. Notice the different length of heatsinks in each bluefury...
2. a 10port hub can run 5 (you can run 10 but chips will touch heatsinks) hence the dual reset switch on each bluefury.
3. LED at least 80& brighter then asic usb.(is there a way to shut down led??)

[Beastlymac]

Bluefury trial one
test on

Windows 7 - CGminer 3.7.2 (Hotplug after running zadig)


cgminer cmd used
cgminer -o stratum+tcp://stratum.mining.eligius.st:3334 -u pssSuperTedpss -p x

  gradually built up speed to 2.2 gigahash

note:
1. Notice the different length of heatsinks in each bluefury...
2. a 10port hub can run 5 (you can run 10 but chips will touch heatsinks) hence the dual reset switch on each bluefury.
3. LED at least 80& brighter then asic usb.(is there a way to shut down led??)

The switches are reset and program they aren't both reset.
Currently no the led can't be turned off as it is used by the majority of people to make sure that the device is working properly.

[kabopar]

NEW VERSION 3.5.1, NOVEMBER 7 2013

Human readable changelog:

• Bug fixes only.

Full changelog:

• Bugfix: make-release: Add README.GPU document
• Demote USB string fetch failure to LOG_DEBUG since it is rather common
• Bugfix: RPC: devscan shouldn't be available to read-only access
• Bugfix: bigpic: Ignore the bitfury chip's counter as best we can
• Bugfix: bigpic: Accept other delimiters in Bitfury BF1 product string in autodetection
• Bugfix: Fix VCOM/fpgautils build check
• Bugfix: Only include VCOM code when VCOM/fpgautils support is being built
• Bugfix: Reimplement scan-serial "all" keyword
• Bugfix: bitforce detect: Close device after ZGX failure
• Bugfix: Define lowl_usb even if libusb support is omitted, since VCOM and HID drivers check against it for warnings

Tried bfgminer 3.5.1 on Win 7 64:

The hashing performance is similar to previous tests.  Also tried to increase the port speed to 115200 as suggested earlier, it works but the benefit is unclear.
With bfgminer 3.5.1 there is no display of the BF serial number (this is fine), but the HW error seems to creep higher and higher (maybe this is the 'truth' which was previously 'masked out'?)
Performance over time:
Time   ####/####/####   A   R   HW
06:00   2.26/2.26/2.22   173   5   9
00:08   2.26/2.26/2.21   247   8   11/3.6%
00:10   2.26/2.26/2.17   282   8   14/4.3%
00:14   2.27/2.26/2.17   397   8/2.7%   23/4.8%
00:20   2.27/2.26/2.16   585   8/1.9%   32/4.8%

This is running with a batch file:
bfgminer.exe -S bigpic:all -o (pool url) -u (user name) -p (password)

Cheers

Edit:  Later, after restart had quite a lower submitted shares average, changed the Com port speed setting back to the original 9600, and the rate restored to about 2.14 GH/sec  (2.26/2.26/2.14 on bfgminer 3.5.1)

[Beastlymac]

The main aim of 3.5.1 is to correct the hw error count. It will give a tiny bit extra hash rate but nothing overly significant.