Quote from: doctormandrake on January 30, 2014, 02:52:33 AM

you can specify com ports, or if you wanted you could also just run a seperate instance of antminer for the bfl and for the antminers. I find that works best in alot of instances (of course I even seperate individual ants that perform better to give them the 2.1gh clock speed etc lol) I have found bfgminer to be a champ with multiple instances, wherein cgminer simply crashed alot or created conflicts in most multiple instance scenarios.

Oh shoot. Does BEE relate to Antminers? I thought it was the Block Erupters.

Quote from: rmolby on January 30, 2014, 02:59:50 PM

I can confirm that running multiple instance of BFGminer is very doable and stable... I have seperated my BEs from my ANTs (AMU) and BFL... now the BE's are actually submitting hashes since they are only running difficulty 4, when I had them mixed in with the other mining units and I was running difficulty 16, they were always taking too long to process and would submit stale shares

The problem still exists that some of the Erupters won't activate (steady green light) and a 'No Device Found' "error" is thrown when you try and manually add them from within BFGminer.

But they are all found using: sudo ./bfgminer/bfgminer -o [redacted] -u [redacted] -p [redacted] -S -all --icarus-options 115200:1:1 --icarus-timing 3.0=100

Then BFGminer only sees the BFL unit. But going "M" -> "+" -> and typing 'all'

Adds the Erupters, usually ICA 0 to ICA 14 and then BEE 0 to BEE 2. For a total of 18 Erupters. Sometimes it does apply 'AMU' to at least one of them.

*Note: I used the Linux step, obviously, here: https://www.btcguild.com/index.php?page=support§ion=blockerupter