Balance will treat all pools with equal priority so in your case it'll split the hash rate 50/50.  Load balance is where it takes into account quotas which is what I believe you would want anyway.

Yes selecting 'load balance' should balance out your hashing power appropriately.  

It should work but if not replace the solo quota to '1' and your other main pool to '9' and see if that helps.  Or just replace the 'quota' part of your solo pool with "url" as it would normally be.  Actually in hindsight that may be how to fix it since I use a 1:4 ratio with my BFGMiner config and it also has the pool with the '1' quota as just "url".  Also are you using the latest BFGMiner build (3.10.0)?

I'm using Windows 8 64-bit so I don't think I can directly compare our setup.  Try running it in Admin mode and see.

Also try using the command prompt if you aren't already - see if that will give you an idea as to why it's not loading properly.  I assume that the test builds for 3.09.00 that are listed in the Antminer U1 Tips and Tricks thread works fine?

How long do you give it?  Try giving it a minute or two to load.  Are you running it in a command prompt or a shortcut/.bat file?  If it's the latter try using the command prompt directly since the window closes if the shortcut or .bat file runs into an error.  Using a command prompt lets you see what the error message is.

You could try to start BFG Miner with just the '--set-device antiminer:clock=x0981' command and see if that works or with no commands at all.

Also make sure the pool details are correct as it will auto close the window if it is not.

So.....with my puny 12 Gh/s rig I might as well forget P2Pool right?  Expect share is somewhere around 4 days right now and payout per block is BTC0.00143.  So that's something like BTC0.00143 every 4 days?  Am I reading this right?

Thanks for the extra commands.  I'm trying those now on v3 but I think 1.8 Gh/s per U1 is the max my hub can take right now - we'll see in a few hours time.  I am running 3 BE's on the same hub so that could be affecting the overall hash rate. 

Regarding HW errors, you're right, v3 is far more stable even at 0981 - gotten 1 HW error on one U1 so far.  Very happy still with the results.

Received my two U1's today.  Thanks for the fast delivery!   

Better to use the modded version of BFG Miner here for U1's: https://www.dropbox.com/s/c7movpxohewides/bfgminer-npw-antminerV3.7z

I run four right now with the regular CP2102 drivers listed in the U1 manual which means you don't need to overwrite the drivers and plug in each U1 everytime you start up.

Far simpler imo.  Give it a try.  Just uninstall the U1's on your device manager and replug the U1's to install the regular drivers.  After that run BFG Miner with the command '--set-device antiminer:clock=xHEX' where 'HEX' would be the speed you wish to set.  The default is 0781 but if you look in the manual it goes quite high.  I'm running mine at 0881 with no problems.

Hope this helps.

Yes I know don't worry.   I may try 0981 again on v3 soon but using v2 at 0981 I got loads of HW errors so I'd like to avoid them for now.  Also I don't have any active cooling so I wouldn't want to run the U1's too hot right now.

Ok after letting v3 run for a bit longer I'm getting no more HW errors compared to oc'ing with v2 which is a relief!  Below is my four U1's running at 0881, the rate is slightly off but I'm happy with it now.

 Block: ...5aae6b5d #280517  Diff:1.79G (12.81Ph/s)  Started: [22:32:57]
 ST:15  F:0  NB:5  AS:2  BW:[ 67/ 63 B/s]  E:25.08  I:81.01uBTC/hr  BS:1.27k
 4             |  8.20/ 8.02/ 7.18Gh/s | A:1489 R:5+9(.92%) HW:0/none
--------------------------------------------------------------------------------
 AMU 0 :       |  2.07/ 2.01/ 1.78Gh/s | A: 353 R:2+2(1.1%) HW:0/none
 AMU 1 :       |  2.01/ 2.00/ 1.88Gh/s | A: 405 R:1+5(1.3%) HW:0/none
 AMU 2 :       |  1.99/ 2.01/ 1.82Gh/s | A: 378 R:1+1(.51%) HW:0/none
 AMU 3 :       |  2.03/ 2.01/ 1.70Gh/s | A: 353 R:1+1(.74%) HW:0/none
--------------------------------------------------------------------------------

I'm still confused with all the 'unknown freq' blurb when I use the new '--set-device antiminer:clock=xHEX' but so long as it works... 

Well v3 doesn't do much better than v2 for me.  Same as you I can't OC the U1's even with the new '--set-device antminer:clock=x0981' command.  BFG Miner returns an ' unknown option' and cycles through different frequencies before defaulting to 0781.  

Are you guys using a .bat file or a regular shortcut?

Cheers!    I'll give the v3 a go and see what happens.

I didn't know there was a version 3.  I'm currently on version 2 of the BFG Miner that supports Antminer.  Do you have a link to the version 3 because I must have missed that one?

Btw, currently at 13~11% HW right now when clocked to 0881 with BFG Miner.  I think I need to move then U1's further apart on the hub.

You're not the only one, I too and getting slower speeds with BFG Miner.  I've made some improvement but it's a hassle to do everytime.  Check out my post here: https://bitcointalk.org/index.php?topic=390929.msg4503625#msg4503625

Update:

I'm starting to think my '--set-device antminer:freq=0981' command in BFG Miner isn't working properly.  Before I was looking at an average hash rate of 5.5 Gh/s with that setting with BFG Miner. 

After trying the CG Miner provided by BitMain I reverted the drivers back to the regular ones to use the U1's with BFG Miner.  After using the same .bat file with the above freq command I'm now getting more HW errors but a faster speed similar to what I would expect the U1's to do at 2 Gh/s. 

 Block: ...3b2c1f04 #280440  Diff:1.79G (12.81Ph/s)  Started: [11:13:50]
 ST:15  F:0  NB:2  AS:1  BW:[ 69/ 61 B/s]  E:28.05  I:90.22uBTC/hr  BS:1.25k
 4             |  8.22/ 8.18/ 7.59Gh/s | A:328 R:1+1(.50%) HW:112/8.7%
--------------------------------------------------------------------------------
 ANT 0 :       |  2.06/ 2.05/ 1.70Gh/s | A: 87 R:0+0(none) HW: 46/ 15%
 ANT 1 :       |  2.07/ 2.04/ 2.15Gh/s | A: 78 R:0+0(none) HW:  8/2.4%
 ANT 2 :       |  2.07/ 2.05/ 1.71Gh/s | A: 68 R:1+0(1.6%) HW: 21/7.3%
 ANT 3 :       |  2.06/ 2.04/ 2.00Gh/s | A: 95 R:0+1(.58%) HW: 38/ 11%
--------------------------------------------------------------------------------

My procedure was to uninstall the WinUSB drivers after using the U1's with CG Miner and 'rescan for hardware changes' in the device manager without unplugging and replugging the U1's again. 

After that I ran my BFG Miner bat file.  If I'm right, setting the freq using CG Miner and the WinUSB drivers would properly set the overclock on the U1's but the BFG Miner command doesn't seem to work - for me at least.

A bit more testing is needed but at least I'm getting somewhere.

I'm not sure if it's the power as I've tested the hub with only one U1 and I get the same hash rate at 0981 using BFG Miner. 

To compare I reverted back to the CG Miner recommended by BitMain for the U1 and after all the plugging in one U1 at a time it's sitting steady at 2Gh/s each.  I can confirm this by the reported hash rate that the pool tells me.

For some reason BFG Miner doesn't allow the U1's to go above 1.6 Gh/s for me, often less than that.  But since I'm using the same BFG Miner version as everyone else here and CG Miner does set the hash rate of the U1's properly I'm unsure what to think.

Got new USB 3 powered hub and I think the U1's are running ok now at 0981 (2 Gh/s) but BFG Miner lists the 'effective' hash rate at only 1.5 Gh/s.

Is this something I can adjust or is it simply a pool issue?  I've got hardly any hardware errors on all four units (2 have only 1 HW error).

Any ideas?

Let's never speak of that again...I see red underwear everytime I think of it! 

Payment and PM sent.

I've tried to find a newer version of the BFG Miner that supports the U1's but everyone I've tried has a compile date of the 9th leading me to believe there's only one version currently out?

I've restart my U1's a few times, trying different port configurations on my laptop and I've managed to get them stable for 2.5 hours.  Unfortunately the speeds aren't what they really should be - even when overclocked to 2 Gh/s.  I'm hoping this is just a power issue, I have a TechNet 10-port hub on it's way with a 48W rated PSU so when that arrives I expect the U1's to perform as they should. 

This image is with the '--set-device antminer:freq=0981' command which just highlights what the problem is.
 

Oh and before I forget, I was having BFG Miner 'load balance' between 3 separate pools but it seems to have stabilized with the 'balance' option between two instead.  Not sure if this is down to the power, BFG Miner or a mixture of the two but I've yet to test them using only one pool since I'm afraid that whatever luck has gotten the U1's to hash near their rated speed may run out and I may not get these speeds again until my new hub arrives.