Pretty discouraging to see the updated ship date. This means we will be 4-5 days into the next difficulty before getting them plugged in.
Topic: ANTMINER S3+ Discussion and Support Thread - page 498. (Read 710164 times)
You guys are wonderful. Do we actually need to discuss this now?
Take a look at the HWE (Not HWE%) in the bitmains product page, the last image, its the miner stats screenshot.
I expect an HWE% above 1 when overclocked to 504Ghs.
Take a look at the HWE (Not HWE%) in the bitmains product page, the last image, its the miner stats screenshot.
I expect an HWE% above 1 when overclocked to 504Ghs.
Ant S3 Overclocking asic-freq File
Once you have un-commented your options restart the Ant.
Once you have un-commented your options restart the Ant.
It's not necessary to reboot the ant (at least assuming the S3 functions like the S1 or S2) just reload the process:
Code:
/etc/init.d/cgminer reload
Does anyone know if Bitmain are going to release Batch4 soon?
The third batch is sold out:(
Thanks
The third batch is sold out:(
Thanks
Thanks windpath. I'll give them a try once my Batch1 order arrives.
I hope they'll start shipping today or tomorrow.
I hope they'll start shipping today or tomorrow.
I thought that Bitmain commented that they will start shipping on 14th.
They said:
Quote
The bulk PCB will be arriving tonight, and we will start first batch production tomorrow. First batch usually takes a longer time than later. We may ship the S3 -B1 on or before 14th.
Which doesn't particularly sound assuring.
Thanks windpath. I'll give them a try once my Batch1 order arrives.
I hope they'll start shipping today or tomorrow.
I hope they'll start shipping today or tomorrow.
I thought that Bitmain commented that they will start shipping on 14th.
Thanks windpath. I'll give them a try once my Batch1 order arrives.
I hope they'll start shipping today or tomorrow.
I hope they'll start shipping today or tomorrow.
Ant S3 Overclocking asic-freq File
I put this together from the BM1382 datasheet provided by Bitmain here:
https://bitmaintech.com/files/download/BM1382_Datasheet_v3.0.pdf
I have no idea what the default settings will be; so be sure to rename, save, and take a look at the default asic-freq settings from Bitmain...
Assuming the S3 has the same file structure as the S1 follow these instructions:
SSH to your miner and run:
Note: As I don't know the default values yet all settings in this file are commented out!
You MUST use vi to un-comment at least 1 setting by removing the "#" from before the 3 options.
Once you have un-commented your options restart the Ant.
Here is the complete file in the wget above:
Once batch 1 arrives from Bitmain I'll update this with default values and any other frequency settings provided in the default file...
I put this together from the BM1382 datasheet provided by Bitmain here:
https://bitmaintech.com/files/download/BM1382_Datasheet_v3.0.pdf
I have no idea what the default settings will be; so be sure to rename, save, and take a look at the default asic-freq settings from Bitmain...
Assuming the S3 has the same file structure as the S1 follow these instructions:
SSH to your miner and run:
Code:
clear
cd /etc/config
mv asic-freq asic-freq.original
wget -O asic-freq http://minefast.coincadence.com/ant-s3-asic-freq.txt
chmod 664 asic-freq
Note: As I don't know the default values yet all settings in this file are commented out!
You MUST use vi to un-comment at least 1 setting by removing the "#" from before the 3 options.
Once you have un-commented your options restart the Ant.
Here is the complete file in the wget above:
Code:
#####################################
# Coin Cadence P2Pool Mining #
# http://minefast.CoinCadence.com #
# #
# Ant Miner S3/BM1382 asic-freq #
# Based on BM1382 datasheet #
# (uncomment the desired setting) #
# USE AT YOUR OWN RISK #
#####################################
package 'cgminer'
config 'asic-freq' 'default'
##
# Clock Frequency 100 (M)
##
#option 'chip_freq' '100'
#option 'freq_value' '0783'
#option 'timeout' '38'
##
# Clock Frequency 125 (M)
##
#option 'chip_freq' '125'
#option 'freq_value' '0983'
#option 'timeout' '31'
##
# Clock Frequency 150 (M)
##
#option 'chip_freq' '150'
#option 'freq_value' '0b83'
#option 'timeout' '26'
##
# Clock Frequency 175 (M)
##
#option 'chip_freq' '175'
#option 'freq_value' '0d83'
#option 'timeout' '22'
##
# Clock Frequency 200 (M)
##
#option 'chip_freq' '200'
#option 'freq_value' '0782'
#option 'timeout' '19'
##
# Clock Frequency 225 (M)
##
#option 'chip_freq' '225'
#option 'freq_value' '0882'
#option 'timeout' '17'
##
# Clock Frequency 250 (M)
##
#option 'chip_freq' '250'
#option 'freq_value' '0982'
#option 'timeout' '15'
##
# Clock Frequency 275 (M)
##
#option 'chip_freq' '275'
#option 'freq_value' '0a82'
#option 'timeout' '14'
##
# Clock Frequency 300 (M)
##
#option 'chip_freq' '300'
#option 'freq_value' '0b82'
#option 'timeout' '13'
##
# Clock Frequency 325 (M)
##
#option 'chip_freq' '325'
#option 'freq_value' '0c82'
#option 'timeout' '12'
##
# Clock Frequency 350 (M)
##
#option 'chip_freq' '350'
#option 'freq_value' '0d82'
#option 'timeout' '11'
##
# Clock Frequency 375 (M)
##
#option 'chip_freq' '375'
#option 'freq_value' '0e82'
#option 'timeout' '10'
##
# Clock Frequency 400 (M)
##
#option 'chip_freq' '400'
#option 'freq_value' '08f2'
#option 'timeout' '10'
Once batch 1 arrives from Bitmain I'll update this with default values and any other frequency settings provided in the default file...
It important to ship a large quantity not just 500-1000 pcs and the rest of the buyers wait and wait and wait...
S3- batch 3 sold out 
(
( Quote
Well, the IP on the pic of the S3 hashing points to BTCGuild....
And then there's the antpool: https://blockchain.info/blocks/AntPool which seems to be pretty busy :-)
And then there's the antpool: https://blockchain.info/blocks/AntPool which seems to be pretty busy :-)
LOL, 'we only have one S3' ... and it's on a test bench.
They don't say how many benches ... won't shoot them though for that. If their farm 'is' entirely populated with S2s, it will be interesting to see how the price drops when they swap them out for S4's, or S2's with upgraded boards.
"We have been using S2 machine to deploy a mining farm, and that is how we own the hash rate."
What does this part mean exactly?
What does this part mean exactly?
'We only have S2s in our mining farm and that is all we use to get our hash rate.'
Is how I would translate the Google translation or I would make the inference that their entire hash rate is from the S2's they have on their farm and nothing else. They stated they only have 1 - S3 running for testing purposes.
Nobody is/was there to VERIFY this statement...But we could track their Antminer pool activities...maybe NOT the only one they have...Most of my S1 have private IP mining pool address...
ZiG
Well, the IP on the pic of the S3 hashing points to BTCGuild....
And then there's the antpool: https://blockchain.info/blocks/AntPool which seems to be pretty busy :-)
I'll take the under (shipping before 7.14).
"We have been using S2 machine to deploy a mining farm, and that is how we own the hash rate."
What does this part mean exactly?
What does this part mean exactly?
'We only have S2s in our mining farm and that is all we use to get our hash rate.'
Is how I would translate the Google translation or I would make the inference that their entire hash rate is from the S2's they have on their farm and nothing else. They stated they only have 1 - S3 running for testing purposes.
Nobody is/was there to VERIFY this statement...But we could track their Antminer pool activities...maybe NOT the only one they have...Most of my S1 have private IP mining pool address...
ZiG
"We have been using S2 machine to deploy a mining farm, and that is how we own the hash rate."
What does this part mean exactly?
What does this part mean exactly?
'We only have S2s in our mining farm and that is all we use to get our hash rate.'
Is how I would translate the Google translation or I would make the inference that their entire hash rate is from the S2's they have on their farm and nothing else. They stated they only have 1 - S3 running for testing purposes.
I don't know which I'm bothered by more, the delivery delay or the fact that the S3 will have somewhere around a 1.25 petahash impact on the network. Previously I (and others, I suspect) had assumed that their recent surge in hash rate was due to S3 testing.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Next difficulty is in 4.5 days ...like July 11 ...I guess ...
S3 will start shipping on July 11 or July 14 ...Friday or Monday...weekend in between...IMHO ...
ZiG
I'd bet almost anything its going to be the 14th before they start shipping them out, if then even.
They they did say earliest 10th latest 20th i think. anywhere in there it could be really.
Very true, I will wait to post my emotions once I get the miners.. This is my first new purchase straight from a company, and it was bitmain for a reason.
Somebody could organize a bet on this...
My bet is July 14...
ZiG
I don't know which I'm bothered by more, the delivery delay or the fact that the S3 will have somewhere around a 1.25 petahash impact on the network. Previously I (and others, I suspect) had assumed that their recent surge in hash rate was due to S3 testing.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Next difficulty is in 4.5 days ...like July 11 ...I guess ...
S3 will start shipping on July 11 or July 14 ...Friday or Monday...weekend in between...IMHO ...
ZiG
I'd bet almost anything its going to be the 14th before they start shipping them out, if then even.
They they did say earliest 10th latest 20th i think. anywhere in there it could be really.
Very true, I will wait to post my emotions once I get the miners.. This is my first new purchase straight from a company, and it was bitmain for a reason.
I don't know which I'm bothered by more, the delivery delay or the fact that the S3 will have somewhere around a 1.25 petahash impact on the network. Previously I (and others, I suspect) had assumed that their recent surge in hash rate was due to S3 testing.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Next difficulty is in 4.5 days ...like July 11 ...I guess ...
S3 will start shipping on July 11 or July 14 ...Friday or Monday...weekend in between...IMHO ...
ZiG
I'd bet almost anything its going to be the 14th before they start shipping them out, if then even.
They they did say earliest 10th latest 20th i think. anywhere in there it could be really.
I don't know which I'm bothered by more, the delivery delay or the fact that the S3 will have somewhere around a 1.25 petahash impact on the network. Previously I (and others, I suspect) had assumed that their recent surge in hash rate was due to S3 testing.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Both of these factors work against ROI, which was on the hairy edge anyway. This is disappointing. Just how disappointing will depend on when the units are actually delivered and what the network difficulty will look like then.
Next difficulty is in 4.5 days ...like July 11 ...I guess ...
S3 will start shipping on July 11 or July 14 ...Friday or Monday...weekend in between...IMHO ...
ZiG
I'd bet almost anything its going to be the 14th before they start shipping them out, if then even.
"We have been using S2 machine to deploy a mining farm, and that is how we own the hash rate."
What does this part mean exactly?
What does this part mean exactly?
Jump to: