A guy solved a block solo a few months ago with an S3 when difficulty was 51G.  My S3+ is still solo lottery ticket scratching, my best ever is only 1.9G.  

Holy cow, that's downright amazing!

You have got to be kidding.  We are supposed to go 4 weeks without knowing what our balance is?  Don't you think that's a little absurd?  Make it update once a day, that's fine, but every 30 days is just stupid.

Or give users a button they can press every 24 hours that calculates their balance.  Then not everyone would use it every day and "stress the server", but those who need to can at least know their freaking balance - that's not too much to ask.

"Hey, give us all your money, but we won't tell you how much you have for a complete lunar cycle."

They are very large pools with huge %s of the network hash rate; they are bound to find most of the blocks and sometimes they happen to be in a row.  If you had 130PH imagine how many blocks you would solve in a row sometimes.

Ok, I figured out how to see through the R1 to the U3 api.  You have to open port 4029 in the R1 lua interface under Network -> Firewall -> Traffic Rules.  There is already a rule existing for port 4028 (the R1 api port), so just make the same entry for port 4029 and you can access the U3 api.

So I am having an issue with CG talking to my U3 that is now being controlled by an Antminer R1.  The R1 assigns port 4029 to the U3, but CG will not see the U3 no matter what I have done so far.  I have received some tips from Crazyguy here (I have posted some screen caps there as well) as to what may be the culprit, but I thought I would post here, too, and see if anyone else has already blazed this trail so I can just follow suit?  Otherwise I've got a bit of digging to do to figure this out.  Thanks.

Edit

I figured out how to see through the R1 to the U3 api, posting here as well in case anyone else runs into this problem.  You have to open port 4029 in the R1 lua interface under Network -> Firewall -> Traffic Rules.  There is already a rule existing for port 4028 (the R1 api port), so just make the same entry for port 4029 and you can access the U3 api.  Seems to me that they should have had this rule in the firmware already, but oh well, glad I got it going.




It's not hashing at the moment, but that's ok, this exercise was just to be able to monitor it via CG.

Cool, thanks, I will mess around with it tonight.  It seems to me like the port should be open by default to facilitate use, but I'll see what I can dig up.  I've only ssh'd into miners a couple times, I'm really a noob with it, so hopefully the solution presents itself quickly.

Edit - so I couldn't wait to get home and VPN tunneled to my home computer, went into the lua interface and found port opening under the traffic rules tab (Network, Firewall, Traffic Rules).  There was already a rule for port 4028, so I added the same one for 4029 (like I said above, seems to me that the firmware should do this already since it tells the U3 to use port 4029, maybe something you could add to your custom flash in the future?) and viola, cryptoglance can see the U3.  Once I get home I'll figure out why it's not hashing any more, probably just need to unplug/replug.  Thanks again!

I think you meant 361?  I know it was down around 250 for so long that you probably just got used to typing 2.  If you want to sell me any coins at 261 please send a pm. 

I think we're going to see 10% increases all winter, there's a lot of gear coming online, price is strong, and people are getting excited about bitcoin.

Do you have a voltmeter?  If you so can find out if it's 120/240 very easily.

20A home circuits are not uncommon and are often 120v.  240v outlets look much different, as notlist3d linked.

How would I go about opening the port on the R1?  I understand how to do it on my normal router, but I do not see similar functions on the R1.

Also, any idea why the U3 didn't come back when I restarted the R1?  Thanks.

Considering this campaign is closed, it would make sense for new people to chose another one.

Hmm, another user suggested port 4029 to me as well, and I tried it and it didn't work.  I'll dig a little deeper and try to figure it out, thanks.


Edit

I looked into the running processes and it does appear that port 4029 is the correct port, but CryptoGlance does not want to talk to the U3 on that port.  Any other ideas?



On another note, I restarted the R1 and now the U3 isn't hashing at all.  I restarted it several times last night and the U3 always came back hashing, but it's dead now after a restart of the R1 (I'm not at home, I am accessing my home computer over VPN).

Hmm, well I'll look into the processes that are running and see what's what, thanks for the tips.

Edit, ok, I found the process and it does appear that port 4029 is the correct port, but CryptoGlance does not talk to the U3.  Any other ideas?



I restarted the R1 and now the U3 isn't hashing at all.  Hmm...

I have 2 compac sticks in a usb3 hub that is plugged into a usb3 port and I don't seem to have any problems.  It's running on a Win7 machine.

Nope, that didn't do it, still shows it as "off line".  I tried 4027 and 4030, too.  No other ip addresses show on my router so it must be behind the R1 somewhere.

I got my R1 set up and it's solo mining for me and controlling my U3 (237.5/0785).  So far so good, but one thing I am struggling with.  The only ip address I have is for the R1 and CryptoGlance sees it just fine, but how do I get CryptoGlance to see the U3?  When my U3 was hooked up to my computer I could assign it a port via the command line, but there does not appear to be anyway to do that with the R1, and so all I can see at the ip address is the R1 hash and stats.  How do I monitor the U3 in CryptoGlance?

Can anyone tell me how to access the U3 api when it is connected to the R1?  I use CryptoGlance to monitor my miners and it needs an IP address and port to get the api stuff to display stats.  The only IP I have is the R1 and CryptoGlance sees it just fine, but how do I get it to see the U3?  When my U3 was hooked up to my computer I could assign it a port via the command line, but there does not appear to be anyway to do that with the R1.

5.4.0+ bfg supports decimal frequencies, 5.3.0 still used hex, so unless he's building an old version yes, it should be decimal.

I've use https://www.bitquick.co/ a couple of times, very smooth service. I went into a bank both times because there is one across from my work so it's convenient.  Always received the btc faster than I expected.  They have a thread here: https://bitcointalk.org/index.php?topic=262082.0

Sorry, I mean vs solo blocks from other sources on the network (individual nodes, other "solo pools", etc.), not total blocks.

For sure, like willi9974's 51.8G share today would have been a block just a few adjustments ago.

Is it known what percentage of solo blocks solved are solved at cksolo vs. the rest of the network?