From BitmainWarranty: "C1 uses a similar looking PCB to S3 or S3+ hashing PCB, but it is little different, so Please DO NOT mix them as the connector even facing differently."

So the C1 boards are NOT S3 boards just a bit clocked up correct? Just for clarification please.

I have a Rosewell 1300 watt gold rated power supply http://www.rosewill.com/products/1799/ProductDetail_Overview.htm that uses the same connectors for the "Modular" design termination to the power supply. I can tell you that at stock settings for an SP20, they were getting very hot in an 25C ambient environment. I clocked the unit down and have already ordered a replacement power supply for it (and took a little "heat" for doing so). I use an EVGA 1300G2 on the other unit with no issues. I used the Rosewell with my Gridseeds before but due to the low current draw had no issues. I haven't looked up the spec on that particular connector but apparently due to the closed environment of the connector it is not conducive for heat dissipation. This just justifies my action about replacing the power supply when I saw the picture this morning (in case my wife asks).

Did anybody notice the BM1384 spec sheet. Still 28nm but reporting lower power consumption. I assume this is the chip for the S5? Or did I miss something?
https://www.bitmaintech.com/files/download/BM1384_Datasheet_v2.0.pdf

Did anybody notice the BM1384 spec sheet. Still 28nm but reporting lower power consumption. I assume this is the ship chip for the S5? Or did I miss something?
https://www.bitmaintech.com/files/download/BM1384_Datasheet_v2.0.pdf

They have now inundated the the site. At least they waited until the end.

There were always two OCT versions but the 141013 version had problems, see page 379. This version did contain cgminer 4.6.1 version. The 141024 came out to fix that problem and to work with other browsers, but as I recall this one apparently introduced the reset button issue. Regardless CK's cgminer version for S3 units could be loaded on top of the current version, this can be found around page 375. Wish we could just get one that works.

Well you have the correct frequency from what I saw on your screen shot, but as asked before, not sure why you are putting in the voltage, you can leave that blank for now. When the miner shuts down is the fan still turning on the power supply?

Maybe BITMAIN can try it on a unit and provide screen shots of the results? Or if Dogie has a unit that was provided maybe he could update that one and provided an update to the S3 review.

I find that placing my address in the "find" function of your browser works like a champ for me. If the browser you are using has that feature.

Not correct, look at the site right now and you will not find S3 Firmware. Maybe it will be back later.

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.

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.

Is it just me or did the LSTime stop reporting?
EDIT: The time is not an issue for me. Thank you CK for taking the time to help the S3 units.

Exactly what dawned on me this morning. I recently changed routers so I need to change the DNS on the ants. Since I am on a private node this has not raised it's head yet. Truly appreciate the support.

you are being blocked to ck.kolivas.org or ck.kolivas.org is not resolving
do
nslookup ck.kolivas.org

Name:    reaver.kolivas.org
Address:  193.19.136.183
Aliases:  ck.kolivas.org

and do
ping 193.19.136.183

That worked with terminal before I logged into one of the ants but once in the ant I tried again this time it came back with the 127.0.0.0, local bitcoind, not sure why it resolved to this. I can download the file so I guess I will just need to go about this a different way. Thank you for the quick reply.

Any reason why I keep getting this:
root@antMiner:/usr/bin# wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
wget: bad address 'ck.kolivas.org'
root@antMiner:/usr/bin#

I have tried this with terminal on a MAC and putty on a windows platform and get the same results.

I thought the peer's came in on port 9333 and the workers on 9332? Well both ports have been forwarded when I started months ago so this is a little perplexing. I just looked at the P2P node listing and it looks like I may not be alone so I guess I will let it ride for now. I know I could go add peers but as I am still getting shares so it is not broken. I contribute this to something strange. Guess it is time to use the search feature to see if this was addressed in the past.

EDIT: After further research I guess this is nothing to worry about. I find it strange how I lost all of them at the same time and did not find a smoking gun in the router logs such as a loss of service. Oh well back to the regularly scheduled program.

Nice work Windpath on the new site.

No restart, I did get one back then he dropped. I guess I need to check the router logs when I get home to see what other traffic maybe going on.

Is there a reason why I would lose all of my incoming peers? I still have 6 going out, internet connectivity and was able to get another share after the peers were lost. I had 10 prior to this morning. I am running the current P2P version, 13.4-52-g8cffc88, and also running the C++ relay client (which should not have an effect but provided as FYI).

Wow thanks guys, I didn't think about just copying the old web-static folder over but relied on just making a new one. I did rename the existing p2pool folder so I do have the old files. That was easy, thanks again!