Everything seems to be working fine, but that's just way out of range.
Thanks,
Dave
Topic: Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence - page 10. (Read 84827 times)
March 21, 2017, 07:25:01 PM
Anybody have any idea of what is up with this temp?
Everything seems to be working fine, but that's just way out of range.
Thanks,
Dave
Everything seems to be working fine, but that's just way out of range.
Thanks,
Dave
March 20, 2017, 03:08:47 PM
Well, this is an interesting find and I thought I'll share it with you. 
I had a problem booting my Antminer R4 8.0 Th/s, batch 2, autotune-model.
So I went looking in here:
Bitmain.com: Three Ways to Restore Factory Settings (R4/S9/T9)
https://enforum.bitmain.com/bbs/topics/3957
I used the last option in the list, IP Reporter button restore.
My miner restored with firmware Aug. 9 2016 and autotune settings were gone.
I am now suddenly able to control frequency and custom fan settings.
This was not my original problem, but I'm happy with it.
My original problem was that the miner jammed somehow in the booting process and didn't even show up in my router ip list.
I had a problem booting my Antminer R4 8.0 Th/s, batch 2, autotune-model.
So I went looking in here:
Bitmain.com: Three Ways to Restore Factory Settings (R4/S9/T9)
https://enforum.bitmain.com/bbs/topics/3957
I used the last option in the list, IP Reporter button restore.
Quote from: Bitmain
Usage: Please power off the miner, then hold down the IP Reporter and don’t release it. At the same time, please power on the miner.
Releasing the IP Reporter after 5 seconds, the machine will automatically restore factory settings.
Releasing the IP Reporter after 5 seconds, the machine will automatically restore factory settings.
My miner restored with firmware Aug. 9 2016 and autotune settings were gone.
I am now suddenly able to control frequency and custom fan settings.
This was not my original problem, but I'm happy with it.
My original problem was that the miner jammed somehow in the booting process and didn't even show up in my router ip list.
March 14, 2017, 08:06:56 PM
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.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!
One of my b6's lost it 25hrs after getting it. One of these days got to send it off to CO for paid repair...
March 14, 2017, 06:57:16 PM
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.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!
Same thing happened to me
March 14, 2017, 03:50:30 PM
With the difficulty rising nearly exponentially is anyone really making money with this miner? Doing the calculations it seems literally impossible to be profitable.
Maybe your calculations do not include profit from selling used unit before it becomes obsolete 
March 09, 2017, 04:10:48 PM
They shipped my repaired 8.7Th/s unit back with newer firmware version December 9.
Temps are better (lower) than before.
December 2 firmware version is the newest one available at Bitmain.com at the moment.
I asked about download link for the December 9 firmware to update my other 8.7Th/s unit which has high-ish temps, but they said they are still testing it.
They said that it will be available at the support page when it's ready.
Temps are better (lower) than before.
December 2 firmware version is the newest one available at Bitmain.com at the moment.
I asked about download link for the December 9 firmware to update my other 8.7Th/s unit which has high-ish temps, but they said they are still testing it.
They said that it will be available at the support page when it's ready.
March 09, 2017, 09:23:23 AM
Repair finished, R4B4 is being sent back to Hoth... Fingers crossed all is good!
March 08, 2017, 01:59:46 AM
I got my faulty 8.7Th/s unit fixed back here in Finland and mining smoothly again so far
Smooth delivery via Fedex, no need to deal with customs.
Smooth delivery via Fedex, no need to deal with customs.
March 07, 2017, 11:21:53 PM
My sick droid R4B4 has finally arrived at the imperial droid maintenance facility, and hopefully will be repaired and sent back to the btc mine at my Hoth like DC. Ran for about a day before a hashboard died, and that was on December 28th... Was running at half speed for a bit, but seriously folks LAME!
March 04, 2017, 05:16:18 PM
I have a question about shipping an R4 back to bitmain for warranty work because it has stopped hashing on the bottom board. When returning for warranty work do i have to pay any duties or taxes going into Hong Kong? Also does any one have a sample shipping label you could share with me? When trying to add "TUNG-D INTERNATIONAL DEVELOPMENT LIMITED Warehouse No.3811" to the company name on UPS it cuts it off and i just want to make sure it does not get lost in the mail. this whole process is a pain for a miner that is only 60 days old.
You "only" have to pay the shipping costs. For the adress, just use every available field and space and do not take care, which field is for what. The final result should look like this:
Tel. and e.mail come from fields outside the adress space here. And I agree, they should absolutely make this a free pickup service.
March 04, 2017, 02:49:48 PM
I have a question about shipping an R4 back to bitmain for warranty work because it has stopped hashing on the bottom board. When returning for warranty work do i have to pay any duties or taxes going into Hong Kong? Also does any one have a sample shipping label you could share with me? When trying to add "TUNG-D INTERNATIONAL DEVELOPMENT LIMITED Warehouse No.3811" to the company name on UPS it cuts it off and i just want to make sure it does not get lost in the mail. this whole process is a pain for a miner that is only 60 days old.
March 04, 2017, 10:39:02 AM
Well my faulty R4 is now fixed and on the way back to my place. Fedex has it in Cologne (Germany) at the moment.
No details about what was repaired though.
No details about what was repaired though.
March 04, 2017, 01:21:00 AM
or just type in Bitmain.com
March 03, 2017, 11:23:59 PM
Neither of my browsers will log on to www.bitmaintech.com (both state the site is unsafe), anyone else having this problem?
seems they changed their domain?
try this https://shop.bitmain.com/main.htm?lang=en
March 03, 2017, 06:48:06 PM
Neither of my browsers will log on to www.bitmaintech.com (both state the site is unsafe), anyone else having this problem?
Looks like an expired cert on their side. Oops.Meantime question: Would it be worth my looking into these things to see if they can be fixed stateside?
March 02, 2017, 03:46:12 PM
The reason behind that coupons is probably not to make good on the customer, but to leverage sales.
R4=100% failure rate? Coupons for everyone then!
R4=100% failure rate? Coupons for everyone then!
Hey, you guys see that Bitmain is handing out coupons for buyers of certain batches of the S9? We buyers of flaky R4's should be close behind, no?
March 02, 2017, 03:43:08 PM
Neither of my browsers will log on to www.bitmaintech.com (both state the site is unsafe), anyone else having this problem?
March 02, 2017, 12:53:55 PM
Hey, you guys see that Bitmain is handing out coupons for buyers of certain batches of the S9? We buyers of flaky R4's should be close behind, no?
March 01, 2017, 11:28:06 PM
Funny you'd say that, notfuzzy... my R4 stopped sending shares to the pool after 56 days though the gui showed the pool was alive and all was apparently well. Soft reboot got it sending shares to the pool again. I figured it was a register of some sort overflowing and halting the code somewhere in there. Amateur hour if you ask me. 
March 01, 2017, 09:36:09 PM
How often do you guys reboot R4?
Does it matter?
For me, especially with any auto-tune Ant -- only when needed because sustained hash rate dropped substantially. If using miner software like Awesome Miner try restarting just CGminer - not the Bitmain GUI soft-reboot of the whole controller. Should skip the normal initialization needed.Does it matter?
For my s7's and older s9's is good to reboot every month or so. I've noticed that all of my ants from at least s5's get - odd - after 30-50 days. Seem to run fine but things like HW errors gets stuck, maybe hash rates drops several %. Reboot and all is well again.
Jump to: