|
Title: Multiple BFGMiners by Block Erupter Post by: dmpotter on December 17, 2013, 07:32:01 PM I'm not certain if this was answered elsewhere, but I had a problem finding a solution as well.
The Orginal Post that I found was -> https://bitcointalk.org/index.php?topic=329170.msg3531207#msg3531207 Quote My Setup: ------------------------------------------------------------- Miner: BFG Miner (v3.5.1) ASICs: 45 Block Erupters, 1 Butterfly Labs SC 60 GH/s ------------------------------------------------------------- Configuration: ------------------------------------------------------------- C:\mining\bfgminer.exe -o http://POOL -u USER -p PASSWORD -G -S erupter:all The Question: ------------------------------------------------------------- This configuration is simple and works great however what I would relly like to do is run two (Eventully More) concurrent BFGminer instances on the same computer with each accessing the pool as a seperate worker... or eventaully different pools. I dont want to switch to cgminer as some will probably suggest. So with this in mind... can someone help me figure out how to include only the erupters and exclude the BFL because my command line attributes actually detects and runs all 45 Erupters and the Butterfly Labs SC. I tried messing with this command line option as listed in the readme.txt ----> --device|-d <arg> Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all But I could not find a way to make this work and found no examples with many searches. I may not have had the paramters corrct so advice on how this works is welcomed. There are several reasons that I would like to split them to different workers but the biggest is that I would like to know exactly how well each "device type" is performing. Eventually I may want to even have each my future BFLs assigned to a specific worker but run on from a single machine. Any advice would greatly be appreciated. And to share a tip. I have seen configurations for the erupters that use the --icarus timing options. I ran that for a few days and to be honest my numbers showed better results just using the simple -S erupter:all paramter and letting bfgminer take care of the timing. I also seemed to get better results if I upped my queue to reduce the number of times I had to fetch work. I set 25 for the queue size but did not notice if more or a few less would be better. If was indeed better than using the default queue size picked by BFGminer Thanks Mushin77 Most of the posts I have found just stated use --scan-serial erupter:all For Example: Code: bfgminer -o "CONNTYPE://URL:PORT" -u USERNAME -p USERPASS --scan-serial erupter:all Well, I wanted to do individual erupters. After messing with several different arguments this is what I have done.
Code: bfgminer -o "CONNTYPE://URL:PORT" -u USERNAME -p USERPASS --scan-serial erupter:COM4
Only issue I had was if a bfgminer.conf was present, it would load that too. So, I had to remove that file |