Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence

[VRobb]

If you were to leave kano now and block(s) are found after you leave but within the 5nd period, yes you would still receive payments based on how much 5nd is still active at the time the block is found.  It's a way to reduce variance overall, but doesn't help much when you run into a 500%+ block tho!!

[Make-A-Buck]

If you were to leave kano now and block(s) are found after you leave but within the 5nd period, yes you would still receive payments based on how much 5nd is still active at the time the block is found.  It's a way to reduce variance overall, but doesn't help much when you run into a 500%+ block tho!!

When you say '5nd period' do you mean a 5 day period?

[VRobb]

Not exactly though it could be.  It's actually 5 times the current diffuculty, or 500% block if that helps, and based on the pool's average hash rate at the time the block is solved, currently it's 3.x 2.x days.

[philipma1957]

If you were to leave kano now and block(s) are found after you leave but within the 5nd period, yes you would still receive payments based on how much 5nd is still active at the time the block is found.  It's a way to reduce variance overall, but doesn't help much when you run into a 500%+ block tho!!

When you say '5nd period' do you mean a 5 day period?

no

current diff is 310,000,000,000

 so that is 1nd

  5nd is   1,550,000,000,000

so if at kano pool  we are on a huge bad block

2,156,374,303,376 (695.26%)

that is about 7nd

86h 41m

kano is doing 100% or 1 nd every 14 hours or so.

the odds of a shit block like this are 2 in 1000

[Make-A-Buck]

If you were to leave kano now and block(s) are found after you leave but within the 5nd period, yes you would still receive payments based on how much 5nd is still active at the time the block is found.  It's a way to reduce variance overall, but doesn't help much when you run into a 500%+ block tho!!

When you say '5nd period' do you mean a 5 day period?

no

current diff is 310,000,000,000

 so that is 1nd

  5nd is   1,550,000,000,000

so if at kano pool  we are on a huge bad block

2,156,374,303,376 (695.26%)

that is about 7nd

86h 41m

kano is doing 100% or 1 nd every 14 hours or so.

the odds of a shit block like this are 2 in 1000

Thanks for helping my noob mining arse.
So, I should prob tough it out and stay in kano.is pool until this block is over - then jump ship?
Slush daily stats are lookin' great right now.

[elokk]

maybe you should research the slush debacle from earlier in the year before you jump to conclusions.....and get back on topic. This is the r4 thread, not a mining pool discussion 

[Make-A-Buck]

maybe you should research the slush debacle from earlier in the year before you jump to conclusions.....and get back on topic. This is the r4 thread, not a mining pool discussion  

Ooops, sorry. Guess I did stray off topic.
The slush debacle is news to me - thanks, I'll go do some homework on it.
Hopefully my new R4 will keep hashing along like a champ.
Who knows, it might even find a block someday. I can dream! lol
Even though I got lucky with a cooler running unit, it does still throw off a fair amount of heat.
Next on the list is for next week is to re-home the R4 so I'll have free electricity & no surplus heat in my home.

[ps_jb]

Are any news on next batch?

[VRobb]

Hey gang, just learned that you can still play with the frequency control if you want by going direct to the advanced tab like this:

http://192.168.x.x/cgi-bin/minerAdvanced.cgi

Haven't tried it yet myself since my R4 has been running fine, but there you are.  Thanks to ComputerGenie for posting this in the kani.is pool thread.

[reelen]

Hey gang, just learned that you can still play with the frequency control if you want by going direct to the advanced tab like this:

http://192.168.x.x/cgi-bin/minerAdvanced.cgi

Haven't tried it yet myself since my R4 has been running fine, but there you are.  Thanks to ComputerGenie for posting this in the kani.is pool thread.

So it does take you to that tab, but before you change anything it says that it will take 3 hours on search frequency before mining.  I also don't want to void the 90 day warranty so didn't try it.

[elokk]

One of my R4's that stopped hashing on one board has stopped hashing completely after trying to restore the original firmware. The hardware version listed under system overview says "   Socket connect failed: Connection refused".

I have tried powering off several times, reboots, updating firmware, etc. No more hashing. There has to be an easy fix to this without sending to Hong Kong or letting sit in Denver for weeks on end. Any thoughts?

EDIT:  unplugged the original board that did not hash and fired back up, the one remaining board is hashing again at 4th/s!

[Micky25]

Hey gang, just learned that you can still play with the frequency control if you want by going direct to the advanced tab like this:

http://192.168.x.x/cgi-bin/minerAdvanced.cgi

Haven't tried it yet myself since my R4 has been running fine, but there you are.  Thanks to ComputerGenie for posting this in the kani.is pool thread.

So it does take you to that tab, but before you change anything it says that it will take 3 hours on search frequency before mining.  I also don't want to void the 90 day warranty so didn't try it.

It doesn't seem to have any effect.

[LASERminer]

One of my R4's that stopped hashing on one board has stopped hashing completely after trying to restore the original firmware. The hardware version listed under system overview says "   Socket connect failed: Connection refused".

I have tried powering off several times, reboots, updating firmware, etc. No more hashing. There has to be an easy fix to this without sending to Hong Kong or letting sit in Denver for weeks on end. Any thoughts?

EDIT:  unplugged the original board that did not hash and fired back up, the one remaining board is hashing again at 4th/s!

Exactly same fault here - I think we discovered common issue.

[mindtrip]

Hey does anyone have the original R4 Firmware for the batch 1 unit?

[Make-A-Buck]

Uptime... (I'm running a single R4 B2) how often should these miners be rebooted?  (or do you even need to?)
Today about 35min ago (after uptime of 6d19h21m24s) I updated to the new stratum+tcp://nya.kano.is:3333 which after saving the new config caused a reboot.
This is the first reboot I've done after two initial reboots when it was brand new a week ago and was setup & running for a solid week on kano.
Is any work 'lost' because of a reboot or does it pick up right where it left off?
Also, I've checked the 'Kernel Log' tab & the 'Monitor' tab - but no luck finding what I'm looking for.
Does the miner keep a log file of the past stats as seen here http://192.168.x.x/cgi-bin/minerStatus.cgi
or, do those stats get erased on every reboot?
Thanks all.

[gt_addict]

As far as im aware they get erased and a new file created to store current data. Hence why the stats on the status page get reset.

[tbonetony]

Uptime... (I'm running a single R4 B2) how often should these miners be rebooted?  (or do you even need to?)
Today about 35min ago (after uptime of 6d19h21m24s) I updated to the new stratum+tcp://nya.kano.is:3333 which after saving the new config caused a reboot.
This is the first reboot I've done after two initial reboots when it was brand new a week ago and was setup & running for a solid week on kano.
Is any work 'lost' because of a reboot or does it pick up right where it left off?
Also, I've checked the 'Kernel Log' tab & the 'Monitor' tab - but no luck finding what I'm looking for.
Does the miner keep a log file of the past stats as seen here http://192.168.x.x/cgi-bin/minerStatus.cgi
or, do those stats get erased on every reboot?
Thanks all.

Reboots ( sw or hw wise) always happen if you change frequency or pool configuration. I reboot my R4 once a week but for my S9 i just leave it running till it gets drunk, usually 3~4 weeks per say. For monitoring purpose, I usually hook up my miners to MRR that way you can store hashing information for up to a week in their graphical interface.

[elokk]

One of my R4's that stopped hashing on one board has stopped hashing completely after trying to restore the original firmware. The hardware version listed under system overview says "   Socket connect failed: Connection refused".

I have tried powering off several times, reboots, updating firmware, etc. No more hashing. There has to be an easy fix to this without sending to Hong Kong or letting sit in Denver for weeks on end. Any thoughts?

EDIT:  unplugged the original board that did not hash and fired back up, the one remaining board is hashing again at 4th/s!

Exactly same fault here - I think we discovered common issue.

What are you doing about a fix? Sending back to Hong Kong? Denver? Entire unit or only board? Bitmainwarranty is not answering the phone or replying to emails

[LASERminer]

What are you doing about a fix? Sending back to Hong Kong? Denver? Entire unit or only board? Bitmainwarranty is not answering the phone or replying to emails

They replied to me asking to send whole unit to HK. I submited a ticket here: http://support.bitmain.com/hc/en-us/requests/new

[Make-A-Buck]

Uptime... (I'm running a single R4 B2) how often should these miners be rebooted?  (or do you even need to?)
Today about 35min ago (after uptime of 6d19h21m24s) I updated to the new stratum+tcp://nya.kano.is:3333 which after saving the new config caused a reboot.
This is the first reboot I've done after two initial reboots when it was brand new a week ago and was setup & running for a solid week on kano.
Is any work 'lost' because of a reboot or does it pick up right where it left off?
Also, I've checked the 'Kernel Log' tab & the 'Monitor' tab - but no luck finding what I'm looking for.
Does the miner keep a log file of the past stats as seen here http://192.168.x.x/cgi-bin/minerStatus.cgi
or, do those stats get erased on every reboot?
Thanks all.

Reboots ( sw or hw wise) always happen if you change frequency or pool configuration. I reboot my R4 once a week but for my S9 i just leave it running till it gets drunk, usually 3~4 weeks per say. For monitoring purpose, I usually hook up my miners to MRR that way you can store hashing information for up to a week in their graphical interface.

Thanks for the reply tbonetony
What is MRR?