Quote from: Luke-Jr on October 31, 2013, 04:23:39 PM

Quote from: Nemo1024 on October 31, 2013, 11:15:32 AM

Luke, can you comment on the following, regarding BlueFuries:

Quote from: Beastlymac on October 31, 2013, 11:04:42 AM

Quote from: Nemo1024 on October 31, 2013, 10:54:51 AM

Quote from: Beastlymac on October 31, 2013, 10:43:10 AM

They draw 0.5A from what the EE has told me.
The command would be along the lines of.

Code:

bfgminer -S bigpic:all -o pool -u user -p pass

Also if you are using bfgminer from Luke's build you won't be able to probe for both block eruptor and blue fury as both probes will break each other. If that makes sense?

Hmm. I plan to run two separate instances of bfgminer, where one instance would only control/probe for Erupters (-S erupter:all), and the other - only BFs (-S bigpic:all). Hope this works. If not, I'd need to plan for all BlueFuries running from a separate machine. Huh

I don't think cgminer has the same issue. One option would be use a old version of bfgminer sub 3.3.0 so it is only compatiable with the block eruptors and then use our version of bfgminer. Theoretically that should work. Luke might know a better idea or he might have some kind of fix in the works I am not sure.

Just don't use -S :all
This tells BFGMiner to probe every port for the device.
Erupters can't handle BigPic probes, and BigPic can't handle Icarus probes.

Hi Luke-Jr
So does this mean I need to specify all the com ports, if I am mixing Erupters and BlueFurys?

I use -S all for my erupters, when I added a Fury I used the :\\.\COMn. but the Fury was not found.
If I run the Fury on its own then it works ok.