Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 36. (Read 1193208 times)

You have a huge hardware error rate.  What clock are you trying to use?

update

Set up a 12v PSU fan (powered by a 240v to 12v power pack) to blow cool air at the ASIC (see screenshot).

http://i57.tinypic.com/207wzfb.jpg

Below is screenshot of BFGminer at the 1hr mark, and another at the 2hr mark.

http://i60.tinypic.com/29qk606.png
http://i60.tinypic.com/rby520.png

Clearly the ASIC is getting slightly warmer as time goes on. At least with the fan it doesn't get to 100% HW failure after 5 minutes. But I'm still a very long way away fro the standard 333MH/s value, yet alone the claimed 435MH/s value the seller said he was running it at (I'm getting the sneaky suspicion that his long-term overclocking has largely killed the ASIC.

I will try a smaller (USB powered) fan so it concentrates the cooling directly at the ASIC.

Will report back later.

It might not be recommended but I run three different instances of BFGMiner on the same machine:

3.2.1 for Block Erupters
3.5.1 for Blue Furies
3.10.0 for Antminer U1's

It works very well and allows me to power down all the Blue Furies when one inevitably hangs while leaving the other miner types running without interruption. I run the Blue Furies and the Antminers in the same hubs, works fine. I used to run all three types of miners in the same hubs but there was some complication which caused a conflict between the Antminers and the Block Erupters although I'm pretty sure that if I had burned my brain some more I could have resolved what I think was a conflict generated by the command line on the miners.

It's going to be fun as I'll be endeavouring to add some DualMiners into the mix which are being shipped as we speak, although I'm not sure that they'll be supported yet by BFGMiner so I might have to run some other miner for a while but you can bet that I'll be switching to BFG when the DualMiners are supported, so that will probably be a fourth instance of BFG running on the one machine.

Good luck with it.

Thank you,

I'm starting to feel that I don't have the correct prefix (NFY)
Tried (with different port for the chips):

-S bifury:\\.\COM3
-S bigpic:\\.\COM3
-S NFY:\\.\COM3

Still all of them start

Here where I have two bluFuries and one erupter in one hub

Win7 64

bfgminer.exe -S bigpic:\\.\COM9 -S bigpic:\\.\COM4 -S erupter:\\.\COM6

Hummm All the chips always run whatever the config I use

-S NFY@\\.\USB1
-S NFY@\\.\USBSNumber
-S bifury:SNumber
-S bfl:SNumber
-S SNumber
-S NFY@/dev/ttyUSBSNumber
-S \\.\COMn (where n were replace by possible numbers)

and some other that I don't remember (was too excited to write them down at first)
Either all chips ran or bfgminer wouldn't start.

What would be the correct syntax?
(Btw I've read that USB root could change number when rebooting, hence why I'd prefer the Serial Number solution if possible)
(Read twice the manual, read readmeASIC.txt don't get it, what am I missing?)

Thank you

"bfl" (or any other TLA) will select all drivers providing said TLA devices.

Does -S bfl:all work?  I thought we had to use -S bitforce:all for the Butterfly Labs gear (bitforce is the name of their current gen chip)?

Here is a selection

bfgminer.exe --set-device antminer:clock=x0981 --icarus-options 115200:2:2 -o http://stratum.bitcoin.cz:3333 -O worker:password -S antminer:all (this allows fore some clocking)

bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S erupter:all

bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S bfl:all

bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S bpm:all

Or if you need a basic catch all line:-       bfgminer.exe -o http://stratum.bitcoin.cz:3333 -O worker:pasword -S all

Hey all,

I was wondering if someone would be so kind as to post their command line for a mining setup that includes multiple types of hardware (specifically one that runs an antminer U1 and a BFL miner)? I've been mining for a little while and got a lot of info off this thread when i made the switch from cgminer to BFGminer, but now that i'm experimenting with multiple miners I could use some help with the command lines.

I'm sure that if i went back through all 131 pages of this post again, I would be able to find this information....

Sorry in advance for sounding like a lazy n00b

C13

This is what I've found in a previous thread (and will change the -S parameter accordingly):




I will also give it a try with that (it seems easier to do):

I've seen the serial when running bfgminer. What would the parameter looks like? -S SerialNFY1 SerialNFY2 SerialNFY4 (not using #3 for the other instance)

Thank you both of you I'll check those out tonight.
Feel happy again! 

NFY are not assigned a com port since they use the HID driver

You would need the USB path and/or serial number of each device. S/N can be seen from manage panel in bfgminer and use dentify to see which is which

yes it marks the device as "off"

your next session will then auto detect this device as available.

when your second session is running, you can stop the first session, then re start it.

the other way is to define the com ports. you need to go back into this thread for details.

Hummm from what I recall this put off the chip only, but my memory could also be wrong I'll test that tonight to make sure.
Any possible way to parametrize that instead of starting BFGMiner first?

Thank you

use the (M)anage command to access them in the first session. then (D)elete

then your second session should auto detect

Hello,

First, let me thank you about your dedicated time in BFGminer project.

I was wondering if it was possible to run multiple instance of BFGMiner on a single machine to mine different coin with different pool, both having their proper fail over pool.
(In other words, on the same machine, BFGMiner Instance 1 mine X coin on Y pool having Z fail over pool, BFGMiner Instance 2 min A coin on B pool having C fail over pool)
I'm calling BFGMiner from a batch file (if that can help) so I can configure switchs as needed.


FYI: I'm using the NanoFury USB chip only (for the fun of it)

1- I've tried the -d and / or --device switch to turn off some of the devices on instance 1 of BFGMiner and enable them on a second instance
Result -> First instance still showed all the USB device even those NFY that were turned OFF. Second instance -> ran but detect no device

2- I've also tried the -S switch to scan device and try to "separate" them from the command line, wasn't successful.
3- I thought using the --set switch to set default parameters on the wanted NFY on each instance but didn't succeeded.
4- I've also tried to "release" a NFY chip when BFGMiner was running but it only turned it OFF

Is it possible to run BFGMiner like I was trying to do, is it a configuration issue or that particular scenario isn't supported?
Thank you

Its a nice place to live, but I am told it is a bit remote.

It is sounding more like a defective device, internet bandwidth restriction or power problems.

Have you tried Multiminer?      still uses BFG but may give you some more info.

@Mudbankkeith - I wish I knew someone   I live in the Blue Mountains, West of Sydney, Australia.

you need access to another fellow miner with a known good setup.

@HellDiverUK

I have tried both 3.10.0-win32 (which is what I tried first), then tried 3.2.1-win32. Both have yielded the same result.

I purchased a powered 4-port USB 2.0 hub - same result, 100% HW errors (on both bgfminer 3.10.0 & 3.2.1 *and* cgminer 3.7.2 and 3.12.3) after just a couple of minutes.

I tried one of the other USB ports on the other side on my laptop (2 on one side and 1 on the other side). At first I thought that had done the trick - BFG 3.10.0 started off at 477MH/s, then dropped to 390, then HW:1 occured, then we dropped to 301, then HW:2 occured, then it dropped ... you get the idea. After 3 mins I'm looking at HW:15 and 143MH/s. 4 mins in and we have HW:26 with 102MH/s. Clearly it's going south like all the other tests.

http://i62.tinypic.com/8z1yjb.png

My BFGminer 3.10.0-win32 script looks liek this:


So, either the laptop *and* the hub isn't supplying enough juice, or the (2nd hand) device is faulty.

I've emailed the seller twice and he hasn't responded.