Hi, I am totally new with only one piece of Antminer U2. BFG shows 2.35 / 2.31 / 2.29Gh/s - but I dont know if it is OK... If I will put next one or two into a powered USB hub, get I more power as from single used miners or equal?
Topic: BFG and Antminer U2 (Read 20146 times)
You need to look at the U2 board and determine which variation of R1 and R2 resistors are physically present. It seems that as the U2 was developed these resistors were changed/upgraded and the values they have will determine ultimately what the OC can achieve. There may be a picture of the board on the Bitmain website under support in the U1 manual with the resistor values and top voltage supported, this will show in the chart what the top OC is for that exact device. Outside of that it may be an issue with the particular Miner program your running as each one behaves a bit different.
Hi all, I'm trying to run my Antminer U2 at 2.4GH/s but they seem to get stuck at 2.2GH/s no matter which clock hex I attempted.
Can someone give me some advice?
THanks.
https://lh3.googleusercontent.com/-A-PCv-V6te8/U5EQI3OkCNI/AAAAAAAAD7g/gsH2_nxyCWk/w1020-h851-no/CAM00034.jpg
Can someone give me some advice?
THanks.
https://lh3.googleusercontent.com/-A-PCv-V6te8/U5EQI3OkCNI/AAAAAAAAD7g/gsH2_nxyCWk/w1020-h851-no/CAM00034.jpg
Greetings.
With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
You're misusing the icarus options and telling it to report double the hashrate. It's actually running at half that speed.With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
Greetings.
With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
You're misusing the icarus options and telling it to report double the hashrate. It's actually running at half that speed. With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
Greetings.
With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
With the "BFGminer ... --set-device antminer:clock=x0A81 --icarus-options 115200:2:2 --icarus-timing long -S all ..." option, I'm getting more or less 4.5 GHash/s from my new Antminer U2. Is it a rist to the health of the miner? I'm cooling it with a Arctic fan...
Quote
bfgminer version 3.99.0 - Started: [2014-05-21 15:17:50] - [ 0 days 00:17:12]
[M]anage devices [P]ool management (S)ettings [D]isplay options [H]elp [Q]uit
Connected to nl1.ghash.io diff 1 with stratum as user ct1aic.RPI5
Block: ...f87cdad1 #301922 Diff:8.85G (63.38Ph/s) Started: [15:35:02]
ST:7 F:0 NB:5 AS:0 BW:[ 62/ 97 B/s] E:10.44 I: 8.30uBTC/hr BS:2.57k
5 | 5.75/ 5.95/ 3.50Gh/s | A:839 R:0+0(none) HW:7/.83%
--------------------------------------------------------------------------------
BES 0: | 335.9/338.1/391.1Mh/s | A: 94 R:0+0(none) HW:1/1.1%
BES 1: | 362.1/339.1/295.4Mh/s | A: 71 R:0+0(none) HW:4/5.3%
BES 2: | 336.0/338.1/316.2Mh/s | A: 76 R:0+0(none) HW:1/1.3%
BES 3: | 336.0/337.8/328.7Mh/s | A: 79 R:0+0(none) HW:1/1.2%
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2014-05-21 15:34:21] Accepted 4c1b0ce8 AMU 0 pool 0 Diff 3/1
[2014-05-21 15:34:22] Accepted d0347c53 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:24] Accepted dd4bfb94 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:25] Accepted a29ed1aa AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:27] Accepted 935c4156 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:27] Accepted f64ef54b BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:30] Accepted ec87d112 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:32] Accepted 808e4bd3 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:34] Accepted acd5daec BES 2 pool 0 Diff 1/1
[2014-05-21 15:34:35] Stratum from pool 0 requested work update
[2014-05-21 15:34:38] Accepted 3ebb9c07 BES 2 pool 0 Diff 4/1
[2014-05-21 15:34:39] Accepted 451e9491 BES 0 pool 0 Diff 3/1
[2014-05-21 15:34:42] Accepted 1e9f909e BES 3 pool 0 Diff 8/1
[2014-05-21 15:34:42] Accepted fa45b6cb AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:43] Accepted b18a52b8 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:44] Accepted 5a070e85 AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:44] Accepted 21367eb4 BES 2 pool 0 Diff 7/1
[2014-05-21 15:34:44] Accepted 8e2a3fd2 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:45] Accepted 663de2fb AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:46] Accepted 3f6039ca BES 2 pool 0 Diff 4/1
[2014-05-21 15:34:47] Accepted 7b422759 AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:48] Accepted 99a2464e BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:49] Accepted 88f57a4d BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:50] Accepted b46c08bb AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:53] Accepted 2183a1a2 BES 2 pool 0 Diff 7/1
[2014-05-21 15:34:53] Accepted 3a612b98 AMU 0 pool 0 Diff 4/1
[M]anage devices [P]ool management (S)ettings [D]isplay options [H]elp [Q]uit
Connected to nl1.ghash.io diff 1 with stratum as user ct1aic.RPI5
Block: ...f87cdad1 #301922 Diff:8.85G (63.38Ph/s) Started: [15:35:02]
ST:7 F:0 NB:5 AS:0 BW:[ 62/ 97 B/s] E:10.44 I: 8.30uBTC/hr BS:2.57k
5 | 5.75/ 5.95/ 3.50Gh/s | A:839 R:0+0(none) HW:7/.83%
--------------------------------------------------------------------------------
BES 0: | 335.9/338.1/391.1Mh/s | A: 94 R:0+0(none) HW:1/1.1%
BES 1: | 362.1/339.1/295.4Mh/s | A: 71 R:0+0(none) HW:4/5.3%
BES 2: | 336.0/338.1/316.2Mh/s | A: 76 R:0+0(none) HW:1/1.3%
BES 3: | 336.0/337.8/328.7Mh/s | A: 79 R:0+0(none) HW:1/1.2%
AMU 0: | 4.47/ 4.61/ 2.17Gh/s | A:521 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2014-05-21 15:34:21] Accepted 4c1b0ce8 AMU 0 pool 0 Diff 3/1
[2014-05-21 15:34:22] Accepted d0347c53 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:24] Accepted dd4bfb94 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:25] Accepted a29ed1aa AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:27] Accepted 935c4156 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:27] Accepted f64ef54b BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:30] Accepted ec87d112 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:32] Accepted 808e4bd3 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:34] Accepted acd5daec BES 2 pool 0 Diff 1/1
[2014-05-21 15:34:35] Stratum from pool 0 requested work update
[2014-05-21 15:34:38] Accepted 3ebb9c07 BES 2 pool 0 Diff 4/1
[2014-05-21 15:34:39] Accepted 451e9491 BES 0 pool 0 Diff 3/1
[2014-05-21 15:34:42] Accepted 1e9f909e BES 3 pool 0 Diff 8/1
[2014-05-21 15:34:42] Accepted fa45b6cb AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:43] Accepted b18a52b8 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:44] Accepted 5a070e85 AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:44] Accepted 21367eb4 BES 2 pool 0 Diff 7/1
[2014-05-21 15:34:44] Accepted 8e2a3fd2 AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:45] Accepted 663de2fb AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:46] Accepted 3f6039ca BES 2 pool 0 Diff 4/1
[2014-05-21 15:34:47] Accepted 7b422759 AMU 0 pool 0 Diff 2/1
[2014-05-21 15:34:48] Accepted 99a2464e BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:49] Accepted 88f57a4d BES 0 pool 0 Diff 1/1
[2014-05-21 15:34:50] Accepted b46c08bb AMU 0 pool 0 Diff 1/1
[2014-05-21 15:34:53] Accepted 2183a1a2 BES 2 pool 0 Diff 7/1
[2014-05-21 15:34:53] Accepted 3a612b98 AMU 0 pool 0 Diff 4/1
I am eagerly awaiting my first U2. These responses will be of great assistance when I throw it in with my U1's and Bfgminer running on a Raspberry Pi system. I had all the same problems trying to get my U1's to work. Two things made a huge difference.
1. Purchased a large 5vdc switching power supply to run my USB hubs... allowing almost 1 amp capacity for each miner.
2. copied the following statements in the following order to my bfg commandline:
--set-device antminer:clock=x0781 --icarus-options 115200:2:2 --icarus-timing long -S all
The icarus timing long statement causes the clock and hashrate to continually correct itself and is not appropriate in computer systems with a cpu load shared with other applications. You could experiment with "--icarus-timing short" which requires full CPU time without delays, and makes the self-corrections, but only for a limited time (~1 hr). Observing this, I saw my hash rate jump all over the place but over the course of a couple days it smoothed out until now after a couple weeks of continuous running, I see 3.16 or 3.17 gh/s on each miner with total errors at 0% and total rejected at .08% Very pleasing.
1. Purchased a large 5vdc switching power supply to run my USB hubs... allowing almost 1 amp capacity for each miner.
2. copied the following statements in the following order to my bfg commandline:
--set-device antminer:clock=x0781 --icarus-options 115200:2:2 --icarus-timing long -S all
The icarus timing long statement causes the clock and hashrate to continually correct itself and is not appropriate in computer systems with a cpu load shared with other applications. You could experiment with "--icarus-timing short" which requires full CPU time without delays, and makes the self-corrections, but only for a limited time (~1 hr). Observing this, I saw my hash rate jump all over the place but over the course of a couple days it smoothed out until now after a couple weeks of continuous running, I see 3.16 or 3.17 gh/s on each miner with total errors at 0% and total rejected at .08% Very pleasing.
I had my main system blow it's power supply so now I've got a dual Coppermine main board handling the connection. In this case, the onboard USB can handle 1 ANT and 1 Erupter, from the outside, I have a 7 port hub ( bought the wrong kind, they are sideways ) and can only have it set as ant, erupter, ant, erupter and between the 2 closest to the power connection a D-Link USB extender ( 4 inch long USB male to female, now I know WHY they made these! ). I cut and soldered an old D-Link wireless's power adapter to get the hub [email protected] and it will do strange things when I don't have 1 ANT per hub IC including sudden and mysterious hashing issues on either the ANT or Erupters. I've yet to use the --icarus-options as all 4 Erupterschug away around the rated 333 khash/sec and I can only go for =x0981 due to not adding the 10K SMD 0603 resistor ( yet ). With what I've got mining, I know I'm going to have to get a new hub ( with proper orientation ) and another used wireless with adapter if/when I get more Ants!
Power issues show up as the weirdest errors and easier to troubble shoot if you can find what part of the hub it's plugged in to.
I am eagerly awaiting my first U2. These responses will be of great assistance when I throw it in with my U1's and Bfgminer running on a Raspberry Pi system. I had all the same problems trying to get my U1's to work. Two things made a huge difference.
1. Purchased a large 5vdc switching power supply to run my USB hubs... allowing almost 1 amp capacity for each miner.
2. copied the following statements in the following order to my bfg commandline:
--set-device antminer:clock=x0781 --icarus-options 115200:2:2 --icarus-timing long -S all
The icarus timing long statement causes the clock and hashrate to continually correct itself and is not appropriate in computer systems with a cpu load shared with other applications. You could experiment with "--icarus-timing short" which requires full CPU time without delays, and makes the self-corrections, but only for a limited time (~1 hr). Observing this, I saw my hash rate jump all over the place but over the course of a couple days it smoothed out until now after a couple weeks of continuous running, I see 3.16 or 3.17 gh/s on each miner with total errors at 0% and total rejected at .08% Very pleasing.
1. Purchased a large 5vdc switching power supply to run my USB hubs... allowing almost 1 amp capacity for each miner.
2. copied the following statements in the following order to my bfg commandline:
--set-device antminer:clock=x0781 --icarus-options 115200:2:2 --icarus-timing long -S all
The icarus timing long statement causes the clock and hashrate to continually correct itself and is not appropriate in computer systems with a cpu load shared with other applications. You could experiment with "--icarus-timing short" which requires full CPU time without delays, and makes the self-corrections, but only for a limited time (~1 hr). Observing this, I saw my hash rate jump all over the place but over the course of a couple days it smoothed out until now after a couple weeks of continuous running, I see 3.16 or 3.17 gh/s on each miner with total errors at 0% and total rejected at .08% Very pleasing.
Just for the record... I plugged in a cheap ($6) USB volt/amp meter between my hub and a Antminer U2 running overclocked at 0x0981.
Voltage = 5.14 - 5.16
Amperage = 0.32 - 0.33
This is with a "Charger Doctor". Most of the reading we at the higher end, but I did see them dip a bit once in awhile.
Also happy to report the U2 works fine behind the Charger Doctor - I had some trouble with U1s being found. Maybe I just was unlucky before.
Cassey
Voltage = 5.14 - 5.16
Amperage = 0.32 - 0.33
This is with a "Charger Doctor". Most of the reading we at the higher end, but I did see them dip a bit once in awhile.
Also happy to report the U2 works fine behind the Charger Doctor - I had some trouble with U1s being found. Maybe I just was unlucky before.
Cassey
I have been trying to save the money for an USB power meter but they cost as much as an Antminer U2, sooo....
For now it seems that as long as they can get a solid 1/2 amp they are stable at default speeds. But if you plan to overclock look at your power adapter and figure 625-900 milliamps each device for stability and leave a little head room to prevent running the wall-wart at 100% 24-7. The new heat-sinks are very efficient but a light breeze from a fan will help keep them happy and probably help reduce power consumption overcoming heat induced resistance.
For now it seems that as long as they can get a solid 1/2 amp they are stable at default speeds. But if you plan to overclock look at your power adapter and figure 625-900 milliamps each device for stability and leave a little head room to prevent running the wall-wart at 100% 24-7. The new heat-sinks are very efficient but a light breeze from a fan will help keep them happy and probably help reduce power consumption overcoming heat induced resistance.
Does anybody know how many milliamps the Antiminer U2s are supposed to require to run stable? It seems like the original Block Erupter ASIC miners took 500-510 ma, recommended.
Well, happy to report (2) of the (3) are merrily chunking along at ~2GHs right alongside the Antminer U1s in the Anker powered USB strip. I did need to use short (4") USB extension cables since those heat-sinks are too large to allow the U2s to be placed in adjacent slots in the Antek.
#3 is running one step lower at 1.8GHs on a cheapie powered USB strip wtih no signs of slowing down after 24 hours.
Having enough power appears to be key to stable run rates.
Cassey
#3 is running one step lower at 1.8GHs on a cheapie powered USB strip wtih no signs of slowing down after 24 hours.
Having enough power appears to be key to stable run rates.
Cassey
I would isolate the bad one alone and verify against your pool that it is really underperforming by that much. My short time always ranges up and down 1.70 Gh/s to 2.6 Gh/s even though after 45 mins to an hour it stabilizes at my pool and slowly ranges between 1.44 Gh/s to 1.65 Gh/s. They usually spend the majority of the time at 1.54 Gh/s. You may try letting it launch without adding the speed argument and let it default on its own. I can't find where I read it but the U2 may draw up to 1.35 Amps when overclocked. The powered hub would be straining to maintain that many devices over an extended period of time. I bet the hubs power supply got smoking hot.
Just received (3) Antminer U2s to augment my (6) Antiminer U1s.
I originally tried running them all together on an Anker 10 port hub with a 5amp 12V power supply, and they started to work, but one was freaking out with hardware errors. All 9 were launched with a x0981 speed parameter.
Move the three news ones to a cheap powered hub with a 2amp 5V power supply and a different miner machine so I could isolate and watch them. At x0981 the problem child still complained, but runs steady at x0881. Alas, after several hours the performance dropped to <0.50Gh/s, even though the short term counter indicated 2Gh/s. No hardware errors.
Have just dropped down to x0681 (the default) to see what the multi-hour impact is. If it runs stable, I'll move the two good ones back to the Anker hub and leave the problem child on the cheapie hub.
I originally tried running them all together on an Anker 10 port hub with a 5amp 12V power supply, and they started to work, but one was freaking out with hardware errors. All 9 were launched with a x0981 speed parameter.
Move the three news ones to a cheap powered hub with a 2amp 5V power supply and a different miner machine so I could isolate and watch them. At x0981 the problem child still complained, but runs steady at x0881. Alas, after several hours the performance dropped to <0.50Gh/s, even though the short term counter indicated 2Gh/s. No hardware errors.
Have just dropped down to x0681 (the default) to see what the multi-hour impact is. If it runs stable, I'll move the two good ones back to the Anker hub and leave the problem child on the cheapie hub.
I am still using my GPU as a hedge against the rejects. Everyone tries to say GPU mining is a waste but if you already have one in place I think its a waste not to at least let it run at default speed and cover your stales and dupes.
Yah not bad.
At the 2.2Gh/s clock setting there are maybe 5 or 10 max errors in a 24 hour period so next to nothing.
Im now getting more than 0 errors on my 333Mh/s USB erupters after starting the newer version
of BFG miner. The super old version I started with always showed 0 errors but it was always crashing
and had a hard time to start up again so using the new version is better and doesnt constantly crash
if there is even the slightest internet hiccup.
Im getting 1 or 2 hour bursts up to 2.3Gh/s per my BTC dashboard. Not bad.
XXXX_1 2.32 GH/s 48976 (99.68%) 158 / 10 / 0 0:00:15
= sexy stable
XXXX_2 0.685 GH/s 15722 (99.73%) 42 / 0 / 0 0:00:15
---------
Totals 3.00 GH/s 64698 (99.69%) 200 / 10 / 0
At the 2.2Gh/s clock setting there are maybe 5 or 10 max errors in a 24 hour period so next to nothing.
Im now getting more than 0 errors on my 333Mh/s USB erupters after starting the newer version
of BFG miner. The super old version I started with always showed 0 errors but it was always crashing
and had a hard time to start up again so using the new version is better and doesnt constantly crash
if there is even the slightest internet hiccup.
Im getting 1 or 2 hour bursts up to 2.3Gh/s per my BTC dashboard. Not bad.
XXXX_1 2.32 GH/s 48976 (99.68%) 158 / 10 / 0 0:00:15
= sexy stable XXXX_2 0.685 GH/s 15722 (99.73%) 42 / 0 / 0 0:00:15
---------
Totals 3.00 GH/s 64698 (99.69%) 200 / 10 / 0
That's good stuff.
Thanks for the advice.
So I plugged it into a powered USB hub at home.
--set-device antminer:clock=x0A81
Got steady 2.2Gh/s all night after that. 0 HW errors so far.
I put a small fan in front of the heatsink and the thing runs
way cooler than the OLD 333Mh/s USB block erupters.
So far these things seem pretty legit for the size and price.
So I plugged it into a powered USB hub at home.
--set-device antminer:clock=x0A81
Got steady 2.2Gh/s all night after that. 0 HW errors so far.
I put a small fan in front of the heatsink and the thing runs
way cooler than the OLD 333Mh/s USB block erupters.
So far these things seem pretty legit for the size and price.
If your trying to run more than one Asic at a time, I would highly recomend using a Powered Hub. Now, if you don't know, keep in mind. Some Powered Hubs will send power thru the USB connector back to the computer if they don't have a diode on the wire inside the hub. Its not a big deal if you remember to turn the hub off before shutting down the computer. It can do weird things to a computer trying to get into sleep mode and interfeer with restarts as the motherboard can't properly power down to the correct S-mode before it tries to start back up. If the hub doesn't have a power switch just use a surge protector that does.
Seem to have found the happy medium
--set-device antminer:clock=x0981
ST:2 F:0 NB:1 AS:0 BW:[ 67/ 36 B/s] E:7.38 I: 7.90uBTC/hr BS:33
1 | 2.17/ 1.97/ 2.00Gh/s | A:22 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------
AMU 0: | 2.08/ 1.96/ 1.94Gh/s | A:22 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------
[2014-03-17 12:05:05] Accepted 51952aaf AMU 0 Diff 3/2
[2014-03-17 12:05:06] Accepted 29f65084 AMU 0 Diff 6/2
[2014-03-17 12:05:11] Accepted 72dbf9e8 AMU 0 Diff 2/2
Tried --set-device antminer:clock=x0B81 and got ALOT of errors immediately.
Gonna try this for a day and see.
Then try --set-device antminer:clock=x0A81 and see if it hashes better with a
USB powered hub and runs stable or if the HW errors come back.
This seems to be alot of trial and error with these things.
--set-device antminer:clock=x0981
ST:2 F:0 NB:1 AS:0 BW:[ 67/ 36 B/s] E:7.38 I: 7.90uBTC/hr BS:33
1 | 2.17/ 1.97/ 2.00Gh/s | A:22 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------
AMU 0: | 2.08/ 1.96/ 1.94Gh/s | A:22 R:0+0(none) HW:0/none
-------------------------------------------------------------------------------
[2014-03-17 12:05:05] Accepted 51952aaf AMU 0 Diff 3/2
[2014-03-17 12:05:06] Accepted 29f65084 AMU 0 Diff 6/2
[2014-03-17 12:05:11] Accepted 72dbf9e8 AMU 0 Diff 2/2
Tried --set-device antminer:clock=x0B81 and got ALOT of errors immediately.
Gonna try this for a day and see.
Then try --set-device antminer:clock=x0A81 and see if it hashes better with a
USB powered hub and runs stable or if the HW errors come back.
This seems to be alot of trial and error with these things.
[2014-03-17 11:55:01] AMU 0: Applying rule antminer:clock==x0881: invalid clock
: '=x0881' data must be prefixed with an x
[2014-03-17 11:55:06] Accepted 58c9b293 AMU 0 Diff 2/2
Ok, figured out I copy pasted something bad when I was messing with clock speeds.
Now I fixed it, and its back to low rates of 1.5Gh/s or lower.
It seems hard to make them all show up with the same around 1.9Gh/s like if Im using a
333Mh/s block erupter and they all show around 335 in all three spots.
May be something to just sit and watch over 3 days and see if the speeds average out
to increase to 1.9Gh/s in all 3.
I've haven't seen anything new published yet. Those numbers are going to bounce when you first launch the Miner. Check the speed at the pool Chart after a complete hour of work . See if the 2.0 + holds up.
The new heat sink is flat out awsome. I got a $3 adapter- 4-pin molex to 3-pin case fan and used an old 80mm Dell rear case fan to blow on the heat sink and at default frequency the U2+ feels like its at room temp.
The new heat sink is flat out awsome. I got a $3 adapter- 4-pin molex to 3-pin case fan and used an old 80mm Dell rear case fan to blow on the heat sink and at default frequency the U2+ feels like its at room temp.
OK, went out on a limb here and set the manual hash rate out of curosity.
As soon as I bumped it manually, it started showing full hash all the way.
It even spiked up as high as 2.2Gh/s on the last of the 3.
Possibly a fix for this one, it seems better than before.
Ill let it run a couple days and see what the average shows.
Did a quick touch test on the heatsinks and they feel quite cool.
WAY cooler than my cheap 333mh/s asic miners.
--set-device antminer:clock=x0881
Block: ...f6787ab6 #290935 Diff:4.25G (30.42Ph/s) Started: [10:48:48]
ST:2 F:0 NB:1 AS:0 BW:[ 49/ 27 B/s] E:10.59 I: 8.47uBTC/hr BS:61
1 | 2.12/ 1.99/ 1.94Gh/s | A:126 R:0+1(.79%) HW:0/none
-------------------------------------------------------------------------------
AMU 0: | 2.01/ 1.98/ 1.84Gh/s | A:127 R:0+1(.78%) HW:0/none
-------------------------------------------------------------------------------
[2014-03-17 10:58:10] Accepted 16775289 AMU 0 Diff 11/2
BTW, are there any U2 specific hardware manuals from BitMain yet?
Or posted anywhere?
Or are we just assuming the settings from the U1?
When I set the x0881 clock manually it actually gave an invalid hex setting but ran better
than without it. Now I wonder if the manual x0881 did anything at all. Ugh.
As soon as I bumped it manually, it started showing full hash all the way.
It even spiked up as high as 2.2Gh/s on the last of the 3.
Possibly a fix for this one, it seems better than before.
Ill let it run a couple days and see what the average shows.
Did a quick touch test on the heatsinks and they feel quite cool.
WAY cooler than my cheap 333mh/s asic miners.
--set-device antminer:clock=x0881
Block: ...f6787ab6 #290935 Diff:4.25G (30.42Ph/s) Started: [10:48:48]
ST:2 F:0 NB:1 AS:0 BW:[ 49/ 27 B/s] E:10.59 I: 8.47uBTC/hr BS:61
1 | 2.12/ 1.99/ 1.94Gh/s | A:126 R:0+1(.79%) HW:0/none
-------------------------------------------------------------------------------
AMU 0: | 2.01/ 1.98/ 1.84Gh/s | A:127 R:0+1(.78%) HW:0/none
-------------------------------------------------------------------------------
[2014-03-17 10:58:10] Accepted 16775289 AMU 0 Diff 11/2
BTW, are there any U2 specific hardware manuals from BitMain yet?
Or posted anywhere?
Or are we just assuming the settings from the U1?
When I set the x0881 clock manually it actually gave an invalid hex setting but ran better
than without it. Now I wonder if the manual x0881 did anything at all. Ugh.
Don't expect BFG Miner numbers and BTC Guild numbers to always match. They use different methods to calculate speed. Keep track of your Valid Shares Average at your pool. Give the miner software time to stablize the numbers also. I've had BFG Miner show hash speeds at three times what they really were but I let it keep on running and even though they never corrected till my next restart, they were stable and the real time +- 0.0? difference / sec was still valid.
Also BFG Miner tends to show speeds a little on the conservative side.
Also BFG Miner tends to show speeds a little on the conservative side.
No hardware errors and the stale rejects are very low.
Im gonna run this on a faster network connection at home and see what happens.
Block: ...465fa511 #290934 Diff:4.25G (30.42Ph/s) Started: [10:28:33]
ST:2 F:0 NB:8 AS:1 BW:[ 48/ 23 B/s] E:10.03 I: 7.55uBTC/hr BS:3.61k
1 | 2.08/ 1.96/ 1.49Gh/s | A:529 R:4+0(.75%) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 1.94/ 1.96/ 1.49Gh/s | A:529 R:4+0(.75%) HW:0/none
--------------------------------------------------------------------------------
[2014-03-17 10:32:45] Accepted 4b29ce85 AMU 0 Diff 3/2
Im gonna run this on a faster network connection at home and see what happens.
Block: ...465fa511 #290934 Diff:4.25G (30.42Ph/s) Started: [10:28:33]
ST:2 F:0 NB:8 AS:1 BW:[ 48/ 23 B/s] E:10.03 I: 7.55uBTC/hr BS:3.61k
1 | 2.08/ 1.96/ 1.49Gh/s | A:529 R:4+0(.75%) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 1.94/ 1.96/ 1.49Gh/s | A:529 R:4+0(.75%) HW:0/none
--------------------------------------------------------------------------------
[2014-03-17 10:32:45] Accepted 4b29ce85 AMU 0 Diff 3/2
1.5 Gh/s at the pool dashboard is right in line with the default value of the Antminer. You need to keep in mind that there will always be a bit of personal varience. If the first two sets of numbers on the dashboard are showing 1.90-2.03/ 1.90-2.03 this is your right now hash speed. The third number will start out way off and zero in with time. At default expect this to be in the 1.48 - 1.62 Gh/s as this will reflect a better indicator of valid accepts. When you check the pool report the speed will usually swing up or down each time you refresh the page this is based on a comparison off difference in time since last accepted valid share. BTC Guild has a chart page and it will give your your average over one hour, for 24 hrs. This is the best indicator of Valid Results. It does no good to hash at umpteen Giga Has per second if you have a high number of rejects. If you start accumilating a lot of Hardware Errors, you have an internal issue for sure. My Ant U2 is currently at 2 days 19 hrs and change with Zero HW errors. Stales and duplicates are going to happen so watch your percentage, right now I'm at (0.39%) for this same time period. When these stale and dupes get out of hand your definatley having communication issues. Sometimes the can be resolved by simply quiting the miner refreshing the OS by restart and launching again . As the new NET connection will likely take a different path with the hope that it is more stable than the one you had been on.
Is this issue being most likely linked to bad internet connection?
I just hooked mine up running at the default hash rate and get the same low
hash rate sent to the pool.
Testing this out on a PC running ONLY the U2 antiminer with BFG 3.10.0
The program shows Im hashing at 2.0Gh/s but at the end shows only 1.2Gh/s - 1.5Gh/s
Is this because of a poor internet connection?
I havent even bothered trying to overlclock even though I have added an extra heatsink to the boards chip since
the pool isnt even seening my device full hash rate.
Any other ideas if this is the real issue here due to internet connection?
I checked my BTC dashboard and its showing this speed
XXX_1 1.50 GH/s
bfgminer-3.10.0-win32\bfgminer.exe" -o http://eu-stratum.btcguild.com:3333 -u XXX_1 -p 123 -S antminer:all
Any ideas how to get the pool to see / accept your full hash speed?
bfgminer version 3.10.0 - Started: [2014-03-17 09:44:25] - [ 0 days 00:10:54]
[M]anage devices [P]ool managementettings [D]isplay options [H]elp [Q]uit
Connected to eu-stratum-lb489kj.btcguild.com diff 2 with stratum as user XXX_1
Block: ...2b51b28d #290928 Diff:4.25G (30.42Ph/s) Started: [09:49:34]
ST:2 F:0 NB:2 AS:0 BW:[ 52/ 25 B/s] E:9.36 I: 7.47uBTC/hr BS:3.61k
1 | 1.95/ 1.95/ 1.46Gh/s | A:114 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 1.91/ 1.95/ 1.46Gh/s | A:115 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2014-03-17 09:53:49] Stratum from pool 0 requested work update
[2014-03-17 09:54:19] Stratum from pool 0 requested work update
[2014-03-17 09:54:28] Accepted 6ac5e657 AMU 0 Diff 2/2
[2014-03-17 09:54:28] Accepted 6ac5e657 AMU 0 Diff 2/2
[2014-03-17 09:54:30] Accepted 30662156 AMU 0 Diff 5/2
[2014-03-17 09:54:32] Accepted 46000346 AMU 0 Diff 3/2
[2014-03-17 09:54:41] Accepted 1b407466 AMU 0 Diff 9/2
[2014-03-17 09:54:46] Accepted 6e8eba18 AMU 0 Diff 2/2
[2014-03-17 09:54:49] Stratum from pool 0 requested work update
[2014-03-17 09:54:53] Accepted 27dd1530 AMU 0 Diff 6/2
[2014-03-17 09:54:54] Accepted 5c2bea3b AMU 0 Diff 2/2
[2014-03-17 09:54:55] Accepted 03896a7a AMU 0 Diff 72/2
[2014-03-17 09:54:59] Accepted 048aa081 AMU 0 Diff 56/2
[2014-03-17 09:55:04] Accepted 0e406b49 AMU 0 Diff 17/2
I just hooked mine up running at the default hash rate and get the same low
hash rate sent to the pool.
Testing this out on a PC running ONLY the U2 antiminer with BFG 3.10.0
The program shows Im hashing at 2.0Gh/s but at the end shows only 1.2Gh/s - 1.5Gh/s
Is this because of a poor internet connection?
I havent even bothered trying to overlclock even though I have added an extra heatsink to the boards chip since
the pool isnt even seening my device full hash rate.
Any other ideas if this is the real issue here due to internet connection?
I checked my BTC dashboard and its showing this speed
XXX_1 1.50 GH/s
bfgminer-3.10.0-win32\bfgminer.exe" -o http://eu-stratum.btcguild.com:3333 -u XXX_1 -p 123 -S antminer:all
Any ideas how to get the pool to see / accept your full hash speed?
bfgminer version 3.10.0 - Started: [2014-03-17 09:44:25] - [ 0 days 00:10:54]
[M]anage devices [P]ool management
Connected to eu-stratum-lb489kj.btcguild.com diff 2 with stratum as user XXX_1
Block: ...2b51b28d #290928 Diff:4.25G (30.42Ph/s) Started: [09:49:34]
ST:2 F:0 NB:2 AS:0 BW:[ 52/ 25 B/s] E:9.36 I: 7.47uBTC/hr BS:3.61k
1 | 1.95/ 1.95/ 1.46Gh/s | A:114 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
AMU 0: | 1.91/ 1.95/ 1.46Gh/s | A:115 R:0+0(none) HW:0/none
--------------------------------------------------------------------------------
[2014-03-17 09:53:49] Stratum from pool 0 requested work update
[2014-03-17 09:54:19] Stratum from pool 0 requested work update
[2014-03-17 09:54:28] Accepted 6ac5e657 AMU 0 Diff 2/2
[2014-03-17 09:54:28] Accepted 6ac5e657 AMU 0 Diff 2/2
[2014-03-17 09:54:30] Accepted 30662156 AMU 0 Diff 5/2
[2014-03-17 09:54:32] Accepted 46000346 AMU 0 Diff 3/2
[2014-03-17 09:54:41] Accepted 1b407466 AMU 0 Diff 9/2
[2014-03-17 09:54:46] Accepted 6e8eba18 AMU 0 Diff 2/2
[2014-03-17 09:54:49] Stratum from pool 0 requested work update
[2014-03-17 09:54:53] Accepted 27dd1530 AMU 0 Diff 6/2
[2014-03-17 09:54:54] Accepted 5c2bea3b AMU 0 Diff 2/2
[2014-03-17 09:54:55] Accepted 03896a7a AMU 0 Diff 72/2
[2014-03-17 09:54:59] Accepted 048aa081 AMU 0 Diff 56/2
[2014-03-17 09:55:04] Accepted 0e406b49 AMU 0 Diff 17/2
I've seen mine slow way down if the computer tries to update something while mining. It can tie up the connection and slow down the update download for extended length of time. ie. automatic anti-virus updates. Till the download clears the miner gets erradic and the download can hang up. Also using certain websites with graphic heavy advertising and pictures like Amazon will get the connection wongo too.
Mine flucuates too but not that extreme, maybe its unstable power issue but then again internet connection issues can be tricky culprits. My wireless broadband router gets unstable if I try to use a combination of different devices like Ant U2 and a GPU. the Ant will usually win out and the GPU will produce next to nothing. Are they both using the same connection?
Yes, they both share the same Internet connection.
Mine flucuates too but not that extreme, maybe its unstable power issue but then again internet connection issues can be tricky culprits. My wireless broadband router gets unstable if I try to use a combination of different devices like Ant U2 and a GPU. the Ant will usually win out and the GPU will produce next to nothing. Are they both using the same connection?
My biggest problem now is that although I *can* get good speed from the Antminer, it doesn't hold. It'll run at 1.6Gh/s for a few hours and then drop down. Then later randomly pick back up. In the chart below, the blue line is a little USB Block Erupter staying steady, but the black line is my flakey Antminer. (different computers)
What is the deal? I'm really hoping this external powered USB hub helps this.
http://i.imgur.com/EsI3PJS.jpg
What is the deal? I'm really hoping this external powered USB hub helps this.
http://i.imgur.com/EsI3PJS.jpg
I have seen plenty of people use the miner software the way you ar ebut you are having some issues. Just as a way to eliminate the possibility its a system issue, consider trying a little different approach.
Unzip BFG Miner 3.10.0 to the C:\ drive. Not the Windows folder.
Place a shortcut to Command Prompt on your desktop.
Open the Command Prompt and Change the directory with cd\bfgminer-3.10.0-win32 or 64 {press enter}
C:\bfgminer-3.10.0-win32>_
now launch with bfgminer -S antminer:all -o http://stratum.btcguild.com:3333 -u XXXX_1 -p XXX {press enter}
I have seen that sometimes using "Windows" folder can cause a conflict, usually not, but sometimes.
Also go over your network cables and devices to make sure that you aren't having interference that is slowing something down, also check windows "system resources" for unexpected extra network activity in the graph.
An unclocked Antminer U2 default setting should return between 1.44 Gh/s - 1.7 Gh/s as reported by BTC Guild about 660 Valid Shares per hour. With a decent, clean, internet connection and when plugged directly to the computers onboard USB port.
Thanks. I'll try checking the cables and windows resources. I had already had bfgminer installed at the root level, but I'll try the rest too. Unzip BFG Miner 3.10.0 to the C:\ drive. Not the Windows folder.
Place a shortcut to Command Prompt on your desktop.
Open the Command Prompt and Change the directory with cd\bfgminer-3.10.0-win32 or 64 {press enter}
C:\bfgminer-3.10.0-win32>_
now launch with bfgminer -S antminer:all -o http://stratum.btcguild.com:3333 -u XXXX_1 -p XXX {press enter}
I have seen that sometimes using "Windows" folder can cause a conflict, usually not, but sometimes.
Also go over your network cables and devices to make sure that you aren't having interference that is slowing something down, also check windows "system resources" for unexpected extra network activity in the graph.
An unclocked Antminer U2 default setting should return between 1.44 Gh/s - 1.7 Gh/s as reported by BTC Guild about 660 Valid Shares per hour. With a decent, clean, internet connection and when plugged directly to the computers onboard USB port.
I have seen plenty of people use the miner software the way you ar ebut you are having some issues. Just as a way to eliminate the possibility its a system issue, consider trying a little different approach.
Unzip BFG Miner 3.10.0 to the C:\ drive. Not the Windows folder.
Place a shortcut to Command Prompt on your desktop.
Open the Command Prompt and Change the directory with cd\bfgminer-3.10.0-win32 or 64 {press enter}
C:\bfgminer-3.10.0-win32>_
now launch with bfgminer -S antminer:all -o http://stratum.btcguild.com:3333 -u XXXX_1 -p XXX {press enter}
I have seen that sometimes using "Windows" folder can cause a conflict, usually not, but sometimes.
Also go over your network cables and devices to make sure that you aren't having interference that is slowing something down, also check windows "system resources" for unexpected extra network activity in the graph.
An unclocked Antminer U2 default setting should return between 1.44 Gh/s - 1.7 Gh/s as reported by BTC Guild about 660 Valid Shares per hour. With a decent, clean, internet connection and when plugged directly to the computers onboard USB port.
Unzip BFG Miner 3.10.0 to the C:\ drive. Not the Windows folder.
Place a shortcut to Command Prompt on your desktop.
Open the Command Prompt and Change the directory with cd\bfgminer-3.10.0-win32 or 64 {press enter}
C:\bfgminer-3.10.0-win32>_
now launch with bfgminer -S antminer:all -o http://stratum.btcguild.com:3333 -u XXXX_1 -p XXX {press enter}
I have seen that sometimes using "Windows" folder can cause a conflict, usually not, but sometimes.
Also go over your network cables and devices to make sure that you aren't having interference that is slowing something down, also check windows "system resources" for unexpected extra network activity in the graph.
An unclocked Antminer U2 default setting should return between 1.44 Gh/s - 1.7 Gh/s as reported by BTC Guild about 660 Valid Shares per hour. With a decent, clean, internet connection and when plugged directly to the computers onboard USB port.
clock=x0981
Anything higher than x0681 (consistently) or x0781 (occasionally) produce slow to no results. x0881 gave slow, x0981 gave no, x0A81 gave no. That's why some people think this is a power issue and why I'm trying the powered hub option. We'll see. If it still doesn't work, I guess it is back to the drawing board.
AntMiner U2
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_2 -S antminer:all --set-device antminer:clock=x0881
clock=x0981
I just ordered one of the recommended three (Rosewill 10-Port RHB-500) and will see how it does on Monday. Seems silly to need an external hub for a single usb miner, but I guess that makes sense if it can supply higher consistent voltage than the on-board USB ports. Heck, if this works, I may just buy another Antminer or two for the fun of it.
If the x0681 option works now, you said this will indicate if I have a weak USB power supply? I'm plugging this device directly into the on-board USB ports. What do you recommend instead?
Powered USB hub. Here is helpfull thread to make choice of:https://bitcointalksearch.org/topic/which-usb-hub-to-use-with-block-erupters-nanofury-nf1-bpmc-red-fury-ant-u1-253749
If this doesn't help, try lowering speed with clock=x0681 just to check do you have weak USB power supply.
If the x0681 option works now, you said this will indicate if I have a weak USB power supply? I'm plugging this device directly into the on-board USB ports. What do you recommend instead?
I'm really having some trouble understanding what's going on here. I've been running a single USB Block Erupter with BFGminer for several weeks and have seen ICA 0: with 337/332/355Mh/s. I just upgraded to an AntMiner U2 and used this guide to configure it, and it seems to be running ok around 2Gh/s, but the third number is always much lower and my pool reports much much lower speeds than even with my USB Block Erupter.
What am I doing wrong with the AntMiner to get slower speeds? And what do those three sets of Gh/s values actually mean?
Block Erupter
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_1 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100
AntMiner U2
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_2 -S antminer:all --set-device antminer:clock=x0881
What am I doing wrong with the AntMiner to get slower speeds? And what do those three sets of Gh/s values actually mean?
Block Erupter
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_1 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100
AntMiner U2
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_2 -S antminer:all --set-device antminer:clock=x0881
My U1s are working OK with bfgminer --icarus-options 115200:2:2
If this doesn't help, try lowering speed with clock=x0681 just to check do you have weak USB power supply.
I'm really having some trouble understanding what's going on here. I've been running a single USB Block Erupter with BFGminer for several weeks and have seen ICA 0: with 337/332/355Mh/s. I just upgraded to an AntMiner U2 and used this guide to configure it, and it seems to be running ok around 2Gh/s, but the third number is always much lower and my pool reports much much lower speeds than even with my USB Block Erupter.
What am I doing wrong with the AntMiner to get slower speeds? And what do those three sets of Gh/s values actually mean?
Block Erupter
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_1 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100
http://i.imgur.com/PnHlCkx.jpg
AntMiner U2
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_2 -S antminer:all --set-device antminer:clock=x0881
http://i.imgur.com/LVERcBG.jpg
What am I doing wrong with the AntMiner to get slower speeds? And what do those three sets of Gh/s values actually mean?
Block Erupter
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_1 -S all --icarus-options 115200:1:1 --icarus-timing 3.0=100
http://i.imgur.com/PnHlCkx.jpg
AntMiner U2
bfgminer.exe -o stratum+tcp://stratum.btcguild.com:3333 -O xxxx_2 -S antminer:all --set-device antminer:clock=x0881
http://i.imgur.com/LVERcBG.jpg
Jump to: