Antminer u2 Easy Setup Guide

[Cyberus145]

Yea I tried all the ports.... what coyuld possibly be wrong? also I would be mining rimbits

[mannyg]

I've been trying to get my 10 U1 & U2's to run at 2.0GH/s but the best they hit is 1.9~.

I had them configured with the 115200:1:1 and 250 freq and started tinkering around with the settings and found that if i did 115200:2:2, they would spike to 4 - 5 GH/s.  I had 10 AntMiners running at an average of 4.5GH/s each but my pool was only reporting at best 20GH/s and not the 45GH/s I was seeing in cgminer.

I noticed a few different options too in cgminer aside from the ones I was already tweaking:

ASIC OPTIONS:
--anu-freq  (I have to keep this between 250-262.5 or some of them dont get recognized)
--bitmain-auto
--bitmain-cutoff
--bitmain-fan
--bitmain-freq
--bitmain-hwerrors
--bitmain-options
--bitmain-temp

DEVICE OPTIONS:
--icarus-options (this is what i was changing from 115200:1:1 to 115200:2:2)
--icarus-timing (i keep this set to 'short)

Anybody know if the --bitmain- commands are what we should be using?  I've switched between cgminer 3.12 and 4.10 and the only difference I've seen is USB options.


UPDATE:

I also found modified versions of cgminer for U1/U2 usb devices that use the following options:

--bmsc-freq (hex value)
--bmsc-options (baud:timeout)
--bmsc-rdreg (??)


So many different options for the same chip manufacturer

[-ck]

With the official cgminer, use only --anu-freq and nothing else.

[mannyg]

With the official cgminer, use only --anu-freq and nothing else.

Using official cgminer version 4.1.0, just using --anu-freq 250 works just fine, but doesn't break the 2.0GH/s barrier.  It stays around 1.9GH/s.

Using Bitmain cgminer version 3.12, using --bmsc-freq 0981 --bmsc-options 115200:20 , it takes a very long time to get up to speed and still barely breaks 1.9GH/s.  I also cannot start this version of cgminer with the AntMiners plugged in, I have to launch it then plug them in one at a time else I get send nonce messages and cgminer never connects to the pool.  Their version is on their github here: https://github.com/AntMiner/AntGen1/tree/master/cgminer , it claims to reduce HW errors.


UPDATE:

Using official cgminer 3.12 version with just --anu-freq 250, they can sustain a rate of 2.0GH/s~ .   I have had all 10 AntMiners running for about an hour solid reporting 20GH/s

[-ck]

With the official cgminer, use only --anu-freq and nothing else.

Using official cgminer version 4.1.0, just using --anu-freq 250 works just fine, but doesn't break the 2.0GH/s barrier.  It stays around 1.9GH/s.

Using Bitmain cgminer version 3.12, using --bmsc-freq 0981 --bmsc-options 115200:20 , it takes a very long time to get up to speed and still barely breaks 1.9GH/s.  I also cannot start this version of cgminer with the AntMiners plugged in, I have to launch it then plug them in one at a time else I get send nonce messages and cgminer never connects to the pool.  Their version is on their github here: https://github.com/AntMiner/AntGen1/tree/master/cgminer , it claims to reduce HW errors.


UPDATE:

Using official cgminer 3.12 version with just --anu-freq 250, they can sustain a rate of 2.0GH/s~ .   I have had all 10 AntMiners running for about an hour solid reporting 20GH/s

The older cgminer counted errors in the hashrate, artificially raising it, so it's not actually higher.

[Cyberus145]

Can you help me please? I would highly appreciate it.



Cheers

[pmienke]

I'm running 10 u2's on a good powered usb hub cgminer vs. 4.5.0 no problem with u2's being recognized but having one hell of a time with the config file no mater what I do it dose not work   same with a Bat file  so I can't over clock them any help ?