Kanos Antminer Updates gone?

[gt_addict]

Hi everyone,

So ive got another S3+ arriving soon and would like to update it to Kanos wonderful update, but its not accessible through the github website. Does anyone have a different link or have it saved on there computer (stupid me I didn't save it  ) so I can update my next S3?

Thanks.

[1714115680]

1714115680

[1714115680]

1714115680

[1714115680]

1714115680

[1714115680]

1714115680

[1714115680]

1714115680

[1714115680]

1714115680

[toptek]

Hi everyone,

So ive got another S3+ arriving soon and would like to update it to Kanos wonderful update, but its not accessible through the github website. Does anyone have a different link or have it saved on there computer (stupid me I didn't save it   ) so I can update my next S3?

Thanks.

This works or just did for me i was able to download the tar to a pi.

http://kano.is/AntS3/cgminer-ants3-4.9.2-94e04f6-3.tgz

Code:

 cd /
 wget http://kano.is/AntS3/cgminer-ants3-4.9.2-94e04f6-3.tgz
 tar -xvzf cgminer-ants3-4.9.2-94e04f6-3.tgz
 rm cgminer-ants3-4.9.2-94e04f6-3.tgz
 cgset
 sync
 reboot

[kano]

Oh, I guess someone didn't like that fact that I had binaries there for about 4 years
I've also put the git here:
https://bitbucket.org/TheKano/cgminer-binaries/src

[gt_addict]

Fantastic thank you both. It should be arriving tomorrow so I'll get it updated asap 

[gt_addict]

kano, ive flashed new bitmain firmware to my new (to me) s3+ in an attempt to bring the HW% down from 0.225% and I want to flash you update over the top but when I putty in it and type in the wget command line, it returns with "server returned error HTTP/1.1 404 not found".

Is this something ive done wrong or something to do with where the updates are stored?

Thanks for you help in advance  

Edit:-   I didn't put the capital "A & S" in AntS3. Blimey ssh can be a touchy mistress 

[kriptokyng]

I updated this to my current S3 and now my hash rates displayed in Awesome Miner are all over the place. I did a couple of reboots and no change. It would display 1.1+ THs and drop down to nothing. I am currently running on firmware antMiner_S320150109.bin. I am Solo Mining and was looking to try this out. Do I need down grade my firmware to a older version?

Thanks in Advance

3X Bitmain S3
Awesome Miner 7.1.1
1.33 THs

[philipma1957]

I updated this to my current S3 and now my hash rates displayed in Awesome Miner are all over the place.

this is a very old thread. it may be out of date.

maybe kano will reply if it still works with awesome miner and the s-3

[kriptokyng]

I tried -2 version and it did the same thing.

[Biffa]

Forget awesome miner, what does it show on the miner interface, and what does it show on the pool?

[kriptokyng]

It's bounce all over the place as well on the web interface.

OK, let it run for about 6 Hours. Pretty happy with it. They settle down to the 480's.
Yeah, Awesome Miner doesn't like something with this firmware.
The average data is correct, but the 5 Second Report is all over the place.

But Gonna Let them Eat

Kripto01 - 4875.57 GHs
Kripto02 - 500.31 GHs
Kripto03 - 492.85 Ghs

All Running at 40 C Degrees and Freq 250 MHz

Thanks For the Help Guys

Code:

 "hashrate1m": "1.52T",
 "hashrate5m": "1.49T",
 "hashrate1hr": "1.46T",
 "hashrate1d": "846G",
 "hashrate7d": "596G",
 "lastshare": 1575330818,
 "workers": 3,
 "shares": 246088392,
 "bestshare": 773031278.0672181,
 "bestever": 773031278,

[NotFuzzyWarm]

Sorta surprised Kano hasn't popped in here One thing he'd probably mention to keep in mind is that the default polling rate that AM uses is something like 10 sec or so which is far far more than needed. Per his advice long ago I have AM set to poll my farms miners once every 240sec. (been ages since I changed it so don't remember the default). Increasing the polling interval will of course also smooth out AM's hash rate graph.

Using faster polling give ya more instantaneous snapshots but as you are seeing, it is the average rates that matters. There is a lot of diff bounce among the shares being sent and that translates into apparent instantaneous speed differences. Using AM I mainly only care about the shares being accepted. Most pools will adj miner diff to produce an average of 18 shares/minute so setting a trigger for no shares accepted over say 3 min or more is prudent.

[kriptokyng]

Yeah, still pretty happy with the numbers.
3 BitMain S3

#3 is the Big Worker
Average 488.34
Freq 250
Best 2,711,823,571

#1  
Average 477.03
Freq 237
Best 16,426,915

#2
Average 483.23
Freq 237
Best 13,765,322

Wish I could get the other 2 to the 250 Freq without dropping a chip.

Code:

{
   "workername": "3KbZg8kao8AEeXEG7C97Z6XNMGFiT5Ue6k",
   "hashrate1m": "1.36T",
   "hashrate5m": "1.52T",
   "hashrate1hr": "1.49T",
   "hashrate1d": "1.42T",
   "hashrate7d": "878G",
   "lastshare": 1575568669,
   "shares": 327193492,
   "bestshare": 2711823570.637253,
   "bestever": 2711823570
  }

[kano]

...
The average data is correct, but the 5 Second Report is all over the place.
...

Should be true of every miner on the planet.
The variance on 5 Seconds should be high.

The 'average' takes time to level out, probably an hour or two.

As I've mentioned before somewhere ... I once had something like a 1 hour runtime on an S3 average around 150% performance due to variance.

Shares are statistical results, so expecting them to provide short term consistent averages is simply misunderstanding what a miner is doing
(or fudging the data)