i have just got my kits and i am having problems with the upgrade,the machine turns on with the blinking lights looks like its hashing only to have 0 gh in miner status its connected to my pool because it says alive also in miner status all parts are correct thermal paste as well i used an anti static wrist band when building it looks like the one in the picture after i was finished on the bitmain site only it has green boards i have tried all firmwares S1 AND S3 oldest first and still the same looks like its hashing but not
any help please thanks
I installed this upgrade yesterday. Used the latest firmware (antMiner_S320140826.bin, do not tick 'save settings'). After re-flashing the firmware it returns to 'default' settings (IP 192.168.1.99 and the test pools). You cannot leave both miners at this IP, so you'll need to re-configure the network WAN addresses and your pool configuration. You also need to select the frequency settings at Miner Configuration/Advanced settings, 'save & apply'. In the odd case of a 'stubborn' miner, you might need to perform a system reboot (System tab, reboot, click on 'perform reboot'). My upgrade went smoothly and both S1's are now functioning as S3+. Cheers |
|
|
|
Just received a reply from bitmain BTW this works on S1, just did it see if i could and it did . not everyone should try it , i didn't care if I messed one up . i have a S1 with the S3 firmware . might do them and wait for the upgrade kits to come in on all my S1. What? The S3 firmware? What frequency did you set the S1 for then? After this upgrade the modified S1 is now an S3+, so you set the frequency using the S3+ method from the Miner Configuration/advanced settings gui menu with the drop-down frequency list (which now says that 225 MHz is the default S3+). I started from the S3+ default and all went well. The only minor problem encountered is that a molded RJ45 connector doesn't fit into the LAN socket now, so had to select LAN cables without the molding for the modified S1/3 units. Cheers |
|
|
|
Just received my upgrade kits.
Wanted to shout out how pleased I am with the packaging. Everything looks perfect.
Assembling now.
Thanks!
Kathwren
aka Katie on slush chat
Moar infos!
No problems with assembly, (an electric screwdriver very very helpful) firmware upgrade perfect, followed instructions here on unchecking "save settings" and adjusted the frequency under the miner configuration advanced tab.
Up and running no trouble.
Thanks Bitmaintech!
Congrats! Expecting my kit tomorrow. It is coming at the right time, as my S1's are being turned off for most of the day when their electricity cost is greater than projected BTC earnings. This is with a time-of-use electricity meter and the only time when these less efficient miners can be still used is at night during off-peak rates. Cheers |
|
|
|
|
Just saw that there is a S3-B10 (no price) at Bitmain
Cheers
|
|
|
|
I just got my 2 S3+, they are actually worse than my batch 6 S3
I have overclocked my first S3 to 243,75 MHZ and 250 MHZ,
I can't get the S3+ working above the standard 225 MHZ
they promised th S3+ is better as it should normally be, but I see this is worse !
What settings did you try? |
|
|
|
how this gonna work?tell me more about it.
If you are asking about co-location, there are already various data centres in the ACT (Australian Capital Territory) that offer co-location services. I don't know how much they charge and if any of them accept Bitcoin miners. It's just a thought that someone could do the maths, rent some warehouse/office space and using the relatively lower electricity costs there for co-location of mining. There are probably places in the world with much lower electricity costs, but that would require shipping your miners to some other country, then retrieving them when the co-location contract runs out or is no longer profitable. Cheers |
|
|
|
Return On Investment
As of right now, my Antminer S1 has been hashing nonstop for 147 days. It has generated a shade under 1 BTC. That's good enough for ROI!! This marks an important milestone for my case study, as it proves that money can indeed be made from entry-level mining. Hopefully my ROI timeframe will provide a useful yardstick for other investors, who want to know roughly when they will start turning a profit.
While I don't wish to discourage you, assuming that the electricity prices in the ACT are similar to NSW and that you have a 'time of use' meter, the S1 already consumes more in electricity during Peak and Shoulder times than it can theoretically make in BTC. Most of my S1's are gone and the remaining pair are awaiting their upgrade to S3+. Even the S3 is already in 'negative territory' during Peak electricity times (despite some compensation from solar panels). Looks like we need to either co-locate the hardware to some cheaper electricity place, or say goodbye to mining  Cheers Just looked up some ACT prices, and they are significantly lower than in NSW (Power companies don't want to upset the pollies?!), so you should be still in positive territory (but it may be worth factoring the electricity cost in future difficulty rises). (Maybe someone in the ACT should start a miner co-location business?!) Cheers |
|
|
|
Return On Investment
As of right now, my Antminer S1 has been hashing nonstop for 147 days. It has generated a shade under 1 BTC. That's good enough for ROI!! This marks an important milestone for my case study, as it proves that money can indeed be made from entry-level mining. Hopefully my ROI timeframe will provide a useful yardstick for other investors, who want to know roughly when they will start turning a profit.
While I don't wish to discourage you, assuming that the electricity prices in the ACT are similar to NSW and that you have a 'time of use' meter, the S1 already consumes more in electricity during Peak and Shoulder times than it can theoretically make in BTC. Most of my S1's are gone and the remaining pair are awaiting their upgrade to S3+. Even the S3 is already in 'negative territory' during Peak electricity times (despite some compensation from solar panels). Looks like we need to either co-locate the hardware to some cheaper electricity place, or say goodbye to mining Cheers |
|
|
|
|
My upgrade kit was shipped, due here on 19/09. Looking forward to the efficiency and hash rate improvement compared to the S1's.
Cheers
|
|
|
|
JUST AN FYI.. for all who are waiting to get S3 upgrade kits for your S1's.....
I underclocked my S1's to 250 and they are running at about 125gh. I am running 2 s1's at this speed on a Corsair cx500 using adaptor cables (4 pin MOLEX to 6 pin PCE) and the cables are not hot. The power efficiency should be way better.
Also , the S1's will not run at 200mhz or 193mhz. They connect to the pool but will not hash.
Edit. I use Corsair cx500's on all S3's too. They never burn cables and they only shut down if they get real hot from room temp.
Check the undervolt thread for S1 at https://bitcointalk.org/index.php?topic=526060.0. To improve the efficiency of the S1 you'll need to undervolt it as well as underclocking. You'll gain the efficiency, but at the expense of hash rate. The S1 to S3+ upgrade gives you both an efficiency improvement as well as more than double the hash rate (but the value for money is debatable). Cheers |
|
|
|
|
Wondering if other pool members are experiencing lack of reward payouts.
My confirmed reward has been way over the payout threshold for at least 3 hours. Ticket raised with Slush support.
Maybe this is related to the other 'hiccups' experienced over the last few days.
|
|
|
|
I have 4.6 running and according to TOP it is hashing.
But M's Ant monitor does not talk to it any more.
according to miner status it web page it is hashing fine also.
maybe I'll waiting until M gets the ant monitor updted to the 4.6 API?
I can't live without Ant Monitor.
Fahlcor
I updated all my S3's to 4.6 and they all show up fine on Ant Monitor (v3.1). Cheers |
|
|
|
Thanks.
Is there any way to check the running version from the gui? (it still says that the version is 3.12.0-1 under System, Software on the web gui)
That's just the installed package reference but you've overwritten the binary. If you are on a remote machine, from another copy of cgminer you can do the following command: java API version 192.168.1.99
Where 192.168.1.99 is the S3. Or on the S3 itself run Thanks. Running this from a Win7 command window produces ....[VERSION] => ( [CGMiner] => 4.6.0 ....... Cheers |
|
|
|
Yes, make it executable with that chmod or 'chmod +x' as well. Alternatively you can download it to your pc and copy it to the root directory and then move it across at your leisure. Eg if you're on a linux pc: On your PC: wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminer
scp cgminer root@192.168.1.99: [Or whatever IP address your S3 is]
ssh -l root 192.168.1.99
If you're not on linux you can use winscp for the scp part and putty for the ssh part On the S3 after login: /etc/init.d/cgminer stop
mv /usr/bin/cgminer /usr/bin/cgminer.bak
mv cgminer /usr/bin
/etc/init.d/cgminer start
Even after rebooting the S3 it will continue to use the new binary unless you issue a complete hardware reset. Thanks. Is there any way to check the running version from the gui? (it still says that the version is 3.12.0-1 under System, Software on the web gui) Cheers |
|
|
|
seemed to work to get it there but the permissions are wrong. sorry my nix is rusty. any help?
Tried to follow the same steps, but it doesn't seem to start hashing - the status page parameters remain empty. I reinstated the original cgminer and it is hashing now. Cheers Perhaps chmod 755 cgminer would help? Can you try running cgminer manually from the command line? Thanks, this solved the permissions issue, and the new cgminer is running. Cheers |
|
|
|
I don't have the build environment to create a full binary image, and the code will need a LOT of work to actually become part of mainline cgminer it seems, but for the time being here is a link to a bugfixed binary of cgminer 4.6.0 for the S3 based on the bitmain code. Copy the file into /usr/bin/ on the S3 overwriting the existing one: http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminerIs there an easy way to get this onto our boxes? Do I just get form command line or? Thx Fahlcor did this login root/root cd.. cd /usr/bin mkdir oldcgminer (to keep a copy of the old one) mv cgminer oldcgminer/cgminer wget http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.0-140908/cgminerreboot seemed to work to get it there but the permissions are wrong. sorry my nix is rusty. any help? Tried to follow the same steps, but it doesn't seem to start hashing - the status page parameters remain empty. I reinstated the original cgminer and it is hashing now. Cheers |
|
|
|
|
You don't need a stratum server running, the Antminer S1 can mine standalone. You need the pc only for initial setup and monitoring.
The slush pool settings that work are
stratum.bitcoin.cz:3333
worker_name (usually your login_name.worker1,2,3 etc.)
worker_password (as per your Slush settings).
Note that on Slush you need to create your workers.
It is a good idea to populate the other pool entries with backup pools.
Can you access your web gui?
What does your Status Overview page show? (post a screen shot)
Can you post a screen shot of the Status, Miner Status page?
Cheers
|
|
|
|
Check one of the existing guides, such as https://bitcointalk.org/index.php?topic=344970.0It has instructions how to connect your PC directly to the Antminer S1 (without a router), using a temporary fixed IP on the PC side in the same subnet as the Antminer S1 default IP (192.168.1.99). Once you login to your Antminer you can change its WAN address to a fixed unused value in the subnet supported by your router (say 192.168.2.90). Then change your pc back to its original DHCP setting, connect both to the network and you'll find your Antminer S1 at the new address. Cheers |
|
|
|
|
You are doing fine. With this hash rate you can expect about 0.008 BTC per day. You need to check your electricity cost and factor that in. Check your pool rules in regard to minimum payout and time to payout.
Cheers
|
|
|
|
|
Depending on your electricity cost, the S1 may no longer be profitable. Even if it was possible to re-use the original hashing boards, either already or soon the cost of consumed electricity will be greater than the expected BTC return. One way to extend the S1 life-span would be to under-volt and under-clock them, but the hash rate would drop. The other way is to upgrade them to S3. Economically you could simply sell the S1 and buy a new S3+, but then you'd miss out on the 'tinkering' aspect... I kept a pair of S1's that are waiting for the upgrade.
Cheers
|
|
|
|
|
Show Posts
