Topic: ANTMINER S3+ Discussion and Support Thread - page 113. (Read 710164 times)

What I got from bitmaintech was

"After you finish the firmware, please go to "Miner Configuration-->Advanced settings" and set the frequency to default value, click "Save&Apply", all would be better."

hello, after the last update firmware, my rate was 60GH / s, I looked and after several attempts I handed voltage textbox and then after a reboot everything is back ok.
I have all the updates to make
Sorry for the bad English, I use a translator

Yep, and going by the bits they seem to have broken, now that they fixed the reset button, I think it is time to test that feature for those who took the plunge.

Yes, this new update is supposed to fix the reset button which can be important, especially down the line so " if it ain't broke" doesn't apply because it was broke...

The well established paradigm of "if it ain't broken, do not fix it" then ....Actually, I think bitmain were fixing something with the reset thingybob, now look.

Can you flash back to the old firmware? Seems like this new firmware has a problem. Many people are complaining about low hashing rates on the new firmware.

So, two of my 6 S3+'s are back down to about 50Gh/s, this has only started since the newest firmware upgrade the day before yesterday.  Prepare for others to start noticing this update causing this.  Talk about new untested problems with every firmware update.

You might be able to send your controller into Bitmain and have them jtag flash the firmware and send it back to you?

Losing power during a firmware update will brick the unit. sorry for the loss.

This is why I choose not to update the firmware ever especially if it hasn't paid itself off yet.... maybe after it pays itself off I will take the risk, cause that way I won't be out the buying cost of the unit.

I am having a little trouble with one of my S3's.   I was updating the firmware and the unit lost power during it.  I have tried the reset settings with reset button but I have not been able to fix it.

With losing power during update am I now out of luck with unit where it's a hardware issue or am I just not doing reset right?

https://bitmaintech.com/files/download/antMiner_S320141126.bin just dropped all my miners' hashrate to double digits...

It never made sense, some problems seemed heat related and others didn't. There was a guy who had his units in a data center with the sides off and extra fans that had your same problem. Here is a quote from a PM he sent me July 27th:

 "Chip temps are 31 degrees, DC/DC modules are cool to the touch.
I do see 475+ for about 30-45 minutes on one unit but it tapers off below 430 after more than 10 hours.
Using server power supplies and a separate PWS for the fans. (They are 12V 2A each)"

I have one that did the same thing so I ended up just clocking it lower and it runs stable for weeks. Just need to find the sweet spot and let them run.

The thing that doesn't make sense, with mine anyway, is that a simple restart of cgminer without rebooting or anything will instantly get the hash rate back up.  I would think if it were a heat issue they'd need a bit more time to cool down to get back to the initial performance level.

anyone knows?

thanks, that was the information i was looking for, to me, its a hobby, same goes with undervolting, underclocking my antminer s1 blades  :-)

I have been here since this discussion started as a B1/B2 owner and continue to read daily. A batch of regulator chips did not meet the specifications, though some did. Most of us in the beginning tried about all you could think of with various results. The voltage on some were lower, some did not like heat and others just did not want to work. What some of us also found was this degrade of speed. Various members came up with methods to restart the units at different intervals in an attempt to maintain speed, this did work to a degree. What others found was that if you just satisfy the chips your units came with you could get by with the speed they would produce that would run for weeks. Some of us ran units at lower speeds such as 212.5, at this frequency one my units will run non-stop with very low HW errors and stay within the BITMAIN spec of the advertised +/- speed. Other units could run higher than the S3 stock clock of 218.75.

As an engineer I understand the need to play around and try to fix the units to work faster, this is what we do. In some cases though it might not be worth the effort for the amount of return such as replacing chips. But again for some of us this is a hobby. I hope this sheds a little light on the subject, but from what I remember from this thread the difference between the S3 and S3+ seems to be a different batch of regulators.

I woke up this morning an noticed on my pool 2 of the 3 S3's I firmware updated yesterday were only running around 50 Gh/s.  I went in and hit save and apply to the Advanced frequency controls and rebooted and they went back to normal.  Might have something to do if you over or underclocked the settings?

That is not an immature rant, it is just a rant. Grow up and snap out of your self importance!

If you do end up changing the regulators, please report the results as, I'm having the same issue with some of my S3s.

I think you should take your own advice.  You're attacking people for no reason, I may be new to this forum but, am certainly not new to tech or bitcoin, you have no authority over me and thus cannot bark orders at me.  As usual there are a number of immature people on this forum that have a big head because they figured out something technical, as-if they've discovered something noone else could possibly do,  none of that gives you the right to yell at people you don't know.  Its highly likely that you and many of the people on this forum use some of the hardware and software that I've played a direct or indirect role in bringing to the world over the last couple decades, and I've probably held bitcoin for longer than most here but, regardless of the question, I'm not going to start attacking someone for not knowing something that I might already know.  I won't respond to you again.