ANTMINER U3 Discussion and Support Thread

[Blackbird0]

I've found there is no single answer to these units.  I have 2 currently, one of them doesn't respond to OCing at all, and always has about 2% error.  The other will OC up to about 58GH/s, but it won't hold it for long.

Indeed. This is just a bum product. I will probably not buy any of the U-series from Bitmain anymore until they're far more proven. Of course ... they'll be useless if I wait. If others replicate my experience no one will buy this crap anymore. Not a good move by Bitmain.

[1715305886]

1715305886

[1715305886]

1715305886

[1715305886]

1715305886

[1715305886]

1715305886

[Rockett0]

I have a U3. It says it is version 2 on the box, but is a solid cover.

It runs fine hashing ~60-70. I leave it running when I go on trips and it's still up when I return.


Note:
1. I'm using the USB cord it shipped with
2. I'm using the power adapter it shipped with, no issues.
3. cgminer 4.9.1
4. "au3-freq" : "250.0",
5. "au3-volt" : "800",
6. It's as lucky as all the lottery tickets I've ever purchased, as well as all the tickets my family and everyone I've met has purchased.

If I swap it from one machine to another or undock the laptop, I do occasionally need to pull power and usb before it is picked up. It is typically running off a docked tablet or laptop.

For whatever reason 4.9.0 seems to find it faster than 4.9.1.


Any recommendations on the below would be great. But I solved the problem by launch order.

*I have to launch the u3 batch file before I launch the gridseed batch file (cgminer 4.3.5). If the gridseed launches first it picks up a "Zus: Blizzard"
1: ZUS 2:27        : Blizzard         2 MHz   | 8.029K / 194.1Mh/s WU:0.0/m
 I've tried to blacklist this, but the write to conf file just crashes.

[Mikestang]

I have a U3. It says it is version 2 on the box, but is a solid cover.

I was literally re-zadiging my U3 as I read this.  Grrr.... 

[Mikestang]

Use cgminer 4.9.0 and the correct au3 parameters from readme (not bmsc junk).  Readme tells you what each parameter does.

[Jake-R]

For some reason 4.9.1 doesn't see my U3's but 4.9.0 does.

If you want to overclock just from a batch file try this, it works for me (not the greatest pool though...)

• cgminer -o stratum+tcp://us2.coinking.io:9999 -O <your wallet address> --au3-volt 850 --au3-freq 250

Starting Parameters Conf file works great too.

[Mikestang]

So I should use cgminer 4.9.0 instead of 4.9.1? Were there any drastic changes made?
Those settings were the default settings I got from the U3 support website.
So in other words every parameter should be replaced by one in the README.txt?

edit: Instead of starting parameters I've decided to use the cgminer.conf. Are there any disadvantages by doing so instead of writing a detailed script?

4.9.1 doesn't work with the U3, but 4.9.0 does.

The U3 support site gives parameters to use with their hacked cgminer, they're not valid with the current software.

I use a .bat file to launch cgminer and have all my config stuff there.

au3-volt 850 --au3-freq 250

Those are the maximum settings, a good way to burn out your U3 and its stock power supply.  If you're going to overclock, don't use the stock power supply.  Also, don't just set volt/freq to the max, it's unnecessary.  Every U3 is different, play around with voltages ~765~830 and freqs 237.5, 244.75, and 250 and see what works for you.  Warning, the U3s are garbarge and you'll find out quickly enough that almost no matter what you do the U3 will do what it wants, zombie out, LIBSUB error, etc etc.

[Mikestang]

edit: How do I assign a valid worker_name to my device (type)? (by that I mean grouping my U3s and U2s in different workers each)

Your pool will have instruction how to do that, usually its [btc address].[worker name] or something similar.

[Mikestang]

so by using "stratum+tcp://mint.bitminter.com:3333.worker_name" I can tell the pool what worker to use?

No, the worker name is not part of the pool address, it's usually part of the btc address (user name) as I stated.

If your pool supports the naming convention I mentioned then that's how you do it.  Check your pool for how to assign worker names.

[TheRealSteve]

so by using "stratum+tcp://mint.bitminter.com:3333.worker_name" I can tell the pool what worker to use? Thanks.

No.  For bitminter, you'll have to read through the Getting Started bit:

stratum+tcp://mint.bitminter.com:3333. As user name put your Bitminter user name, an underscore, then a worker name, e.g. DrHaribo_asic3

( usually the user name is specified after the -u flag on the command line, if not specified in a separate GUI field )

You can manually set up worker names at: https://bitminter.com/members/workers
( You can also select auto-generate there, but you'll need the appropriate perk enabled )

[movellan]

I have 5 x Antminers U3

They are working 24/7 for more than a month

No problem. Not even one. Sometimes HW happens but max 0-2 per device per day

I have 6 running steady with CGMiner. Anyone else tried with the new BFGMiner 5.20? Can't get it to detect the U3's.

[Rockett0]

[/quote]

I have 6 running steady with CGMiner. Anyone else tried with the new BFGMiner 5.20? Can't get it to detect the U3's.

[/quote]

I've not tried BFGminer, but I have read that you need to remove the driver we use with CGminer to get this to work.  I have not had the time to mess with a working system yet.

[movellan]

I have 6 running steady with CGMiner. Anyone else tried with the new BFGMiner 5.20? Can't get it to detect the U3's.

[/quote]

I've not tried BFGminer, but I have read that you need to remove the driver we use with CGminer to get this to work.  I have not had the time to mess with a working system yet.


[/quote]

Thanks for replying. I tried all the usual tricks, uninstalling drivers, reboot, re-install; install silab driver alone or install zadig then silab, etc. 5.20 will not recognize the U3; manual installation is a no-go also. Any help appreciated. Thanks.

[hurricandave]

I have 6 running steady with CGMiner. Anyone else tried with the new BFGMiner 5.20? Can't get it to detect the U3's.

I've not tried BFGminer, but I have read that you need to remove the driver we use with CGminer to get this to work.  I have not had the time to mess with a working system yet.


[/quote]

Thanks for replying. I tried all the usual tricks, uninstalling drivers, reboot, re-install; install silab driver alone or install zadig then silab, etc. 5.20 will not recognize the U3; manual installation is a no-go also. Any help appreciated. Thanks.

[/quote]

Uninstalling the drivers from the devices alone won't work. You will need to take the extra step of removing Zadig from the computer as well.

[Rockett0]

Which Pools are working for you with the U3?


The following pools work for me.

stratum+tcp://solo.ckpool.org:3333
stratum+tcp://stratum.solo.nicehash.com:3334
stratum+tcp://stratum1.altnuts.com:3333


Does not work for me:

stratum+tcp://us1.ghash.io:3333


I'd be interested in other pools that work with the u3.
I run cgminer 4.9. 0 or 4.9.1

[Ecnad]

Antpool does really well for me on the U3 and all my low-hash miners

[movellan]

Which Pools are working for you with the U3?


The following pools work for me.

stratum+tcp://solo.ckpool.org:3333
stratum+tcp://stratum.solo.nicehash.com:3334
stratum+tcp://stratum1.altnuts.com:3333


Does not work for me:

stratum+tcp://us1.ghash.io:3333


I'd be interested in other pools that work with the u3.
I run cgminer 4.9. 0 or 4.9.1

Been working for years wiith all Antiminer units:

stratum+tcp://stratum.mining.eligius.st:3334

Use BTC address as username, anything for PW.

[alh]

If you were to increase the clock frequency to 400 MHz, you should expect the power draw to double. You might also find that the fan attached to the U3 is NOT able to handle the increased heat.

Proceed with care in attempting to "overclock" your U3.

[-ck]

I've released a new version of cgminer 4.9.2 which should hopefully work a little better with these, but there's only so much software can do to compensate for hardware designs...

[jlauzon]

My two U3s (V2 w/wire cage) bricked a few days ago using the included 7.5 amp laptop-style power supplies. I did not overclock and was getting a consistent 43+ GH/s hash from both using cgminer for windows.

If I plug them into the original 7.5 amp power, the fan "pulses like a heartbeat, but that's it. I tried a new 10 amp psu and they do nothing at all.

Are these dead for good? I have my doubts that Bitmain will do anything about it...suggestions welcome.

[pinhead666]

I don't have U3 but sounds like blown fet.Saw that with 5-chip gridseeds.