How to Overclock Antminer S1 to 200GH/s the Simple Way! updated for 393.75MHz ASIC

Not great news. The S1's wget can't handle https, and Dropbox now won't let http downloads. My bad, folks. No more simple way to overclock. Best of luck.

Nice tool to help folks.  BTW, I've been using the values from the S1 guide to get to 400MHz: Anyone know which of the 400MHz approaches is "best?"

No good.  wget on the S1 does not support https and dropbox had stopped supporting http downloads.  Sorry everyone.  No more easy way to OC.  Good luck.

Early, really?  I just got it a few days ago through sushi's pre-new year 1.9 BTC blowout. Edit to add:  I tried your 400MHz settings anyway (since that matches what was in my default asic-freq as suggested), and it seems to work.  Maybe even +1 GH/s.

*****  We may be having a miscommunication.  I'm thinking you have the latest version but followed an overclock guide that uses the values from the earlier version of the Ant S1, no?  ***** Sorry but below is the original overclock guide from goxed.  As you can see he mentioned your S1 version.  On another note, check your kernel log (under system tab) and see if you have the latest Firmware.  That's most important.  It should say 12-26-2013  on the top right hand corner. https://bitcointalk.org/index.php?topic=348327.msg3730601#msg3730601

The dropbox idea is a good un  I like the approach you have used, I have been scp'ing files between ant's instead. A couple of comments if I may. You might want to change the mv to a cp in case of a problems such as a power outage because then an asic-freq will always exist regardless and the wget with an -O should clobber the original. The last three lines can also be removed as the wget will put the file with workable permissions. Personally I would just add a reboot command to the script but that may freak a few noob users.

Thank you!  We're getting a lot of new people in the mining scene because of the Antminer S1's and I figured anything to help them out.  I'm a huge fan of Bitmaintech, as I bought from the sushi GB5 and now directly from Bitmaintech and both machines are very stable!  No pretty cases, but well-built and performs as advertised (plus more with OC) I used mv as I don't like to mess with factory system files (if I can help it).  It also keeps the date and time of the original files.  The permissions I saw were rw/rw/r  on the original asic-freq file so wanted to change the ones made by cp/wget from rw/r/r  to be the same.  It's probably ok. Can't wait what Bitmaintech will announce after the Chinese New Year!  Maybe cheaper Ant's?  or More powerfule machines?!  The last difficulty adjustment was not crazy (imo) so maybe it's leveling off.... PS:  I forgot to add, if by some coincidence you get a power-out right after the mv command was issued, just ssh to the miner again and execute the copy and paste and it should be ok.  Re-running the process duplicate times should not hurt anything...

This is really a great help!! I got 6x S1 incoming, and this excelent tutorial will serve me well. Gonna tip for sure. I wish someone would have the baals to do a similar tutorial for knc machines... Anyways, big thnks!!

You're very welcome!  Thank you for the nice words.  If you have any questions, just let me know.  I do hope you're not in Southern Cali (or any warm-weather location) as I've had to turn the first Ant S1 inside-out (heatsinks on the outside).  It looks like I may have to do the same on the 2nd Ant... Overclocking makes the Ant's warm.  I don't want the any blade to hit 52C, so I sometimes go back to stock.  Yesterday had to turn the AC on as I didn't want to drop the speed, lol!  I think it's worth it.

Yep, I followed the old guide even with the new version - it worked fine, but I'm now using the correct values that you have (and were in the default asic-freq file as a guide).  My firmware is Dec 12, 2013 actually since I went back one version to avoid the excessive beep/rebooting I was seeing (I have my Ants temporarily far away and sometimes they have difficulty with solid connections.  After this week, I'll have them in a much better place and will be able to bump the firmware back to the most recent.

Thank you for the tip (to the sender)!  First one I ever received!  Very nice.

Good luck. Just fyi...  I have to reboot my Ant's about every 24 hours as I see xx's on the ASIC's.  I'm sure it's just cosmetic (because the hash performance is fine) but I'm still babying these as they cost more than my old beat-up car, lol.  I can connect to my Ant's from anywhere so reboot is very easy using the web interface.

You do not need to reboot on seeing an 'x', it is a display bug, just watch the share rate on the pool of your choice.

option 'freq_value'     '5e82'  #400M         option 'chip_freq'      '387'         option 'timeout'        '37' Temps are 44/41, hashing at 200GHs. For my ant these are the optimal setting

Worked! Thanks for sharing.

I'm not sure if you're responding to op (me) or the poster above you, but if it's to the op, you're welcome

Hey Jeremy, Can you please do a 387.5 version?

I can do it very easily; but I don't even know if it works or it's safe.  I've used 350, 375 and 400 on my Ants. A few questions: 1.  Have you run the code on the OP? 2.  When did you receive your Antminer S1? 3.  I see a 387MHz version from zuqka, not 387.5MHz, is that what you want? I don't know the settings myself for 387MHz.  The ones I'm using were in the original asic-freq file (and checked on the Bitmaintech Antminer FAQ. pdf file) or in the case of the 375MHz, I relied solely on the Bitmaintech pdf file and added it.

i did not use your script, but used mv for backup also Ants are running now fine at 400Mhz, drawing together 800W so that's still 2W/GH and get not even higher temps!

I followed this and my antminer shut off immediately when I restarted cgminer.  It then would shut down whenever I powered it up.  I thought maybe the PSU wasn't powerful enough even though it's a 750w and I thought after OCing they pull 550?  So I tried unplugging blade 2 and blade one booted up and mined perfectly.  It was hashing at slightly over 100 Ghash.  I then just loaded in the factory settings and plugged blade 2 back in.  Working as it was.  So...for anyone who runs into the same issue that's how you fix it lol. My question is, does anyone know why the 750w PSU wasn't enough?  Do you have any recommendations on what PSU to use to OC it to 400?