question about block eruptor flag

[realestone]

i noticed some people say to use this flag

--icarus-options 115200:1:1 --icarus-timing 3.0=100

in cgminer of bfgminer for usb block eruptors what exactly does it do im just curious

[Taugeran]

Explanation straight from bfgminer read me docs:
https://github.com/luke-jr/bfgminer/blob/bfgminer/README.FPGA#L134

Let me know if you have any other questions

[realestone]

Explanation straight from bfgminer read me docs:
https://github.com/luke-jr/bfgminer/blob/bfgminer/README.FPGA#L134

Let me know if you have any other questions

thanks

[HellDiverUK]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

[Taugeran]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

+1.

Forgot to add that bit. Though if using cgminer may still have to.

[realestone]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

thanks for the info

[-ck]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

+1.

Forgot to add that bit. Though if using cgminer may still have to.

Only if using the old cgminer (3.1.1). 3.3.2+ you don't specify anything.

[HellDiverUK]

Yep, forgot that - both miners are coming on leaps and bounds in support for ASICs. 

[CrashX]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

Just

"-S all"

You don't need the erupter

[ssateneth]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

Just

"-S all"

You don't need the erupter

But it annoys me to see the devices detected as icarus. I'd rather have it detected as a block erupter.

[Taugeran]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

Just

"-S all"

You don't need the erupter

But it annoys me to see the devices detected as icarus. I'd rather have it detected as a block erupter.

Luke-JR found/made a slabs rebranding tool. that can be used to set some flags on the erupters so they are auto recognized as such by -S all in bfgminer...

will edit if i can find the link

[CrashX]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

Just

"-S all"

You don't need the erupter

But it annoys me to see the devices detected as icarus. I'd rather have it detected as a block erupter.

Luke-JR found/made a slabs rebranding tool. that can be used to set some flags on the erupters so they are auto recognized as such by -S all in bfgminer...

will edit if i can find the link

Don't see why you'll want to waste time. They still run at the same speed. I might be wrong correct me if I am.

[realestone]

Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.

Just

"-S all"

You don't need the erupter

But it annoys me to see the devices detected as icarus. I'd rather have it detected as a block erupter.

Luke-JR found/made a slabs rebranding tool. that can be used to set some flags on the erupters so they are auto recognized as such by -S all in bfgminer...

will edit if i can find the link

Don't see why you'll want to waste time. They still run at the same speed. I might be wrong correct me if I am.

that was going to be my question does it matter if you do get them to recognize as block erupter instead of icarus

[-ck]

They all use the icarus communication method, however cgminer automatically detects and lists them as AMU.

[CrashX]

They all use the icarus communication method, however cgminer automatically detects and lists them as AMU.

BFG detects them as ICA, and sometime it doesn't.

[r3wt]

They all use the icarus communication method, however cgminer automatically detects and lists them as AMU.

yep, i've had no problems with them in 3.3.1 although it was a little finnicky to get cgminer to pick them up. had to install the drivers multiple times until it would pick them up, one at a time.

side note: when i download things from your website, chrome blocks the download with "network error" when i download from the github, avast quarantines the javascript api file. whats the deal with this? have your repos been rooted?