Actually WU is what you get paid for. U is denominated in whatever pool difficulty you have while WU is denominated in difficulty 1.
No, WU: includes rejects - which you do not get paid for.
U: is exactly what you get paid for - accepted shares.
I am mining at 1diff so in this case it is even the exact share count when multiplied by the elapsed time and divided by 60.
If you are not mining at 1diff then yes you don't know how much you will be paid, but it still does tell you how many payable shares you have submitted.
The API "Difficulty Accepted" will tell you exactly how many 1diff shares you have submitted
Hm... OT, but I always thought U was adjusting to diff, so if you have a pool with varying difficulty, it wouldn't show accurate numbers, while WU, minus rejects, would always denominate in diff 1.
Oh well, one learns every day.
.b
No you are confusing my comment about shares with difficulty.
As I said above, "I am mining at 1diff so in this case ..."
If you want to work out how much you are paid, you need to know the "Accepted Difficulty" - but if you just want to know how many shares (be they 1diff or 256diff) you have submitted then that's what U: is.
So, yes you cannot guarantee to work out how much you will be paid with U:, but you do know how many 'shares' you have submitted.
Firstly, yes a dev unit, I'm one of the people friedcat contacted last year about sending out dev units
My ASICMINER USB Erupter showed up about an hour ago.
Been playing with the Icarus timing settings still not quite got it right yet.
Obviously yes I'm getting around 300MH/s out of it.
Currently best settings are for anyone wondering while I sort it out:
--icarus-options 115200:2:1 --icarus-timing shortA pic or 2
Click for bigger
Edit: the USB chip is: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
OK after messing with it for quite a while, I've decided that the optimal settings to use for my one for now are:
--icarus-options 115200:2:1 --icarus-timing 3.0=80It's definitely getting around 300MH/s (or more) but I'd need to let it run for a few hours at least to get a rough idea.
The MH/s that my Icarus driver reports is affected by the timing numbers - if the 3.0ns number is wrong (which it is) it will affect the reported MH/s
Best way to get an unbiased slightly under-estimate timing is U: after at least a few hours (a day or two is best) - since U: is what you get paid for
Here's a screen grab after running for 10 minutes
Had 1 hardware error in there.
Seems it might get as many as a few an hour - we'll see.
Mine has no heat sink and gets hot to touch so that may be part of it.
... and after asking friedcat about the internals of the chip ... another adjustment to the settings:
--icarus-options 115200:1:1 --icarus-timing 3.0=80
After I let this run for at least a few hours I should see how far above 300MH/s it really is - coz it certainly seems to be above 300.