ANTMINER S3+ Discussion and Support Thread

[dogie]

Hi,
I can not set the voltage chips. In the menu box for tension, but typing in any value after boot S3 + B11 unresponsive and I measured voltage of the chip voltmeter and there is still 0.760 V. Bitmain then somehow forbid editing tension in newer firmwares, right? You have what firmware and editing tension will really work?
The whole history of issued fw is available somewhere for download? Bitmain on site, some fw deleted and not available. Thank you for advice.

Yes its disabled in the software (since around the new year) but depending on your board type it may not be possible on the hardware itself. I have the following if anyone needs them, but not all of them may be good useable firmwares.

2014 07 11
2014 07 21
2014 08 11
2014 08 26
2014 10 13
2014 10 24 <- staple firmware but with broken reset button
2014 12 19 <- reset button fixed
2015 01 09

[1715279094]

1715279094

[connectCORRECT]

Hi,
Thanks for your feedback.
Our S3 + B11 should be able to regulate the voltage below the frequency of in the menu, but I can not. I do not know why.
I think it should work with fw 2014 10xx.

I have these fw:
2014 0711
2014 0721
2014 0811
2014 0826
2014 1013
2014 1216
2014 1219
2015 0109

I got extra 2014 1216
But I have no 2014 1024, and this would like to get. Can we exchanged them?

Thanks and have a nice day!

[dogie]

I got extra 2014 1216
But I have no 2014 1024, and this would like to get. Can we exchanged them?

Thanks and have a nice day!

2014 12 16 was bugged and was quickly replaced by 2014 12 19 so don't worry about that. A copy of 2014 10 24 can be found here, but make sure you heed the warning!

20141024 firmware contains broken reset button functionality. If you set network settings wrong or are unable to access to the UI/SSH, the controller is considered unrecoverable and bricked. It will have to be sent back to Bitmain to be reflashed manually. Use at your own risk.

[aarons6]

I got extra 2014 1216
But I have no 2014 1024, and this would like to get. Can we exchanged them?

Thanks and have a nice day!

2014 12 16 was bugged and was quickly replaced by 2014 12 19 so don't worry about that. A copy of 2014 10 24 can be found here, but make sure you heed the warning!

20141024 firmware contains broken reset button functionality. If you set network settings wrong or are unable to access to the UI/SSH, the controller is considered unrecoverable and bricked. It will have to be sent back to Bitmain to be reflashed manually. Use at your own risk.

plus i think the 1024 and 1219 are exactly the same firmware but with the fixed button.

no need t run 1024, just use 1219.

i use 1219 on my s3s with the updated cgminer from westhash.
they work great..

[MCHouston]

I am having a DNS issue with the pools on a lot of S3+s, wonder if anyone has seen this.  Miner can resolve other web addresses just fine, and if I put just the IP address in the config for the pool it works fine with the proxy on that IP. 

Seems the ants are racist to DNS that resolves an internal IP address.  See below:

[notlist3d]

I am having a DNS issue with the pools on a lot of S3+s, wonder if anyone has seen this.  Miner can resolve other web addresses just fine, and if I put just the IP address in the config for the pool it works fine with the proxy on that IP. 

Seems the ants are racist to DNS that resolves an internal IP address.  See below:

saving space

What DNS are you using on your network settings?

[MCHouston]

I am having a DNS issue with the pools on a lot of S3+s, wonder if anyone has seen this.  Miner can resolve other web addresses just fine, and if I put just the IP address in the config for the pool it works fine with the proxy on that IP. 

Seems the ants are racist to DNS that resolves an internal IP address.  See below:

saving space

What DNS are you using on your network settings?

Used the gateway router 192.168.1.254 for both the PC and the miners, also tried 4.2.2.2.  Same result.  It is a real public DNS server.

[notlist3d]

I am having a DNS issue with the pools on a lot of S3+s, wonder if anyone has seen this.  Miner can resolve other web addresses just fine, and if I put just the IP address in the config for the pool it works fine with the proxy on that IP. 

Seems the ants are racist to DNS that resolves an internal IP address.  See below:

saving space

What DNS are you using on your network settings?

Used the gateway router 192.168.1.254 for both the PC and the miners, also tried 4.2.2.2.  Same result.  It is a real public DNS server.

Might try the 8.8.8.8 one.  I have had no issues with it.  After you give it a try let us know what pools you are having trouble with.

I have router using 8.8.8.8 aswell.  So far no issues resolving pool's over multiple machines.

[MCHouston]

I am having a DNS issue with the pools on a lot of S3+s, wonder if anyone has seen this.  Miner can resolve other web addresses just fine, and if I put just the IP address in the config for the pool it works fine with the proxy on that IP. 

Seems the ants are racist to DNS that resolves an internal IP address.  See below:

saving space

What DNS are you using on your network settings?

Used the gateway router 192.168.1.254 for both the PC and the miners, also tried 4.2.2.2.  Same result.  It is a real public DNS server.

Might try the 8.8.8.8 one.  I have had no issues with it.  After you give it a try let us know what pools you are having trouble with.

I have router using 8.8.8.8 aswell.  So far no issues resolving pool's over multiple machines.

Tried same issue.

You can try it if you want. Just ping proxy-a.brokenshop.net ilfrom an S3 I would be interested if your S3 would resolve it.

So far my other manufacturers work fine. Just Bitmain is having an issue.

[aarons6]

there is a huge problem with your proxy..
its IP is set to 192.168.1.133

which by default is an internal LAN IP..

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

you need to change your dns on your proxy to your EXTERNAL IP.. then setup a forwarded port so you can access the computer on IP 133 from your router.
or if you arent trying to access this from an ouside source, and just on local lan, why not use the IP instead of the internal dns name.

[HerbPean]

Is there any chance to find a cheap S3 controller board around ?

Or the best solution to replace one ?

Thanks

[andyg51]

Is there a place to buy..like the small networking card that the ethernet cable hooks into on the S3+ miners?
several of my miners took a lightening hit, and will not communicate now. Was hoping to repair them.

[HerbPean]

Is there a place to buy..like the small networking card that the ethernet cable hooks into on the S3+ miners?
several of my miners took a lightening hit, and will not communicate now. Was hoping to repair them.

I would start to take one of them and do a factory reset and try to communicate with it using the default IP.

[MCHouston]

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.

[MCHouston]

Is there any chance to find a cheap S3 controller board around ?

Or the best solution to replace one ?

Thanks

Call Bitmain Support, I believe they will replace a board for $25.

[HerbPean]

Is there any chance to find a cheap S3 controller board around ?

Or the best solution to replace one ?

Thanks

Call Bitmain Support, I believe they will replace a board for $25.

Thanks

[aarons6]

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.

just use the ip.

its probably not the s3 fault, its the network dns is windows only.

[MCHouston]

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.

just use the ip.

its probably not the s3 fault, its the network dns is windows only.

No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server.  I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows.

Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work.

[aarons6]

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.

just use the ip.

its probably not the s3 fault, its the network dns is windows only.

No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server.  I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows.

Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work.

um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance.

sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api.

[MCHouston]

even if you have something on that IP, nobody else in the world will be able to access it.. just you.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.

just use the ip.

its probably not the s3 fault, its the network dns is windows only.

No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server.  I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows.

Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work.

um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance.

sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api.

Modding the config via SSH takes a lot longer then just setting something that should work anyways.  I am really surprised no one has run into this before.