Topic: ANTMINER S3+ Discussion and Support Thread - page 244. (Read 710164 times)

Cool. But PLEASE - provide us also with new S2 (not only S3 since this is S3's thread...) firmware containing this new Cgminer version. Big thanx in advance! 

I've just seen that there is some free miner management software out there. Is anybody here using such a management software to manage a couple of S3s, which software and what's the experience?

Minera looks interesting, running an own Raspberry PI just for the management software or install onto a regular computer running Linux? Is there any catch with that software?

Good work guys!

Cgminer 3.12.0 has been uploaded, https://github.com/bitmaintech/cgminer. The latest version will be updated in 2 weeks.

Good news for you

BITMAIN has issued an RMA #.  Things are looking up =)  I will report back when RMA arrives.

Thank you for elaborating on the process.  This is what I needed to understand it.

Having access is not everything that's needed, there's knowledge/experience and development time and QA effort etc. Having the driver out in the open will hopefully expedite the process.

I told you I figured it out by studying the available patterns in the oem  guide.


the jumps provided are 6.25  or 12.50

so a chart was made

256.25
250.00
243.75
237.5
231.25
225
218.75
212.5

the key to figure this out is to see how the hex code moves  with the provided freqs  then  try what should work in the newer numbers.

the hex code for 212.5 is  1086  provided

the hex code for 218.75 is 1106      so a jump of 6.25    jumped code  0020

so i looked for a freq  that ended in 86  and 237.5 the code   was  1286       so add 6.25 get 243.75     jump the 1286 to 1306

  so I figured the 243.75 as 1306   the timeout was  a guess as to use 16 or 17.

 this is how I got  

 freq 243.75  and code 1306 and time out 16   now I had 1 extra working config


now look at more patterns





       #option  'freq_value'   '1406'     #Freq at 256.25M = 512 gh uses  410 watts
       #option  'chip_freq'     '256.25'
       #option  'timeout'        '15'

       #option 'freq_value'    '0982'  # Freq at 250M = 500gh uses 400 watts
        #option 'chip_freq'     '250'
        #option 'timeout'       '16'

       #option  'freq_value'    '1306' # Freq at 243.75M = 490gh uses 390watts
        #option  'chip_freq'     '243.75'
        #option  'timeout'       '16'

        option 'freq_value'    '1286'  # Freq at 237.5M = 480gh uses 380 watts
        option 'chip_freq'     '237.5'
        option 'timeout'       '17'

        #option  'freq_value'    '1206'   # Freq at 231.25M = 465gh uses 375 watts
        #option  'chip_freq'     '231.25'
        #option   'timeout'       '17'



        #option 'freq_value'    '0882'  #225M
        #option 'chip_freq'     '225'
        #option 'timeout'       '18'

        #option 'freq_value'    '1106'  #218.75M
        #option 'chip_freq'     '218.75'
        #option 'timeout'       '18'

        #option 'freq_value'    '1086'  #212.5M
        #option 'chip_freq'     '212.5'
        #option 'timeout'       '18'

        #option 'freq_value'    '1006'  #206.25M
        #option 'chip_freq'     '206.25'
        #option 'timeout'       '19'

        #option 'freq_value'    '0782'  #200M
        #option 'chip_freq'     '200'
        #option 'timeout'       '20'

        #option 'freq_value'    '1f07'  #196M
        #option 'chip_freq'     '196'
        #option 'timeout'       '20'

        #option 'freq_value'    '0f03'  #193M
        #option 'chip_freq'     '193'
        #option 'timeout'       '20'

        #option 'freq_value'    '0d83'  #175M
        #option 'chip_freq'     '175'
        #option 'timeout'       '23'

        #option 'freq_value'    '0b83'  #150M
        #option 'chip_freq'     '150'
        #option 'timeout'       '27'

        #option 'freq_value'    '0983'  #125M
        #option 'chip_freq'     '125'
        #option 'timeout'       '33'

        #option 'freq_value'    '0783'  #100M
        #option 'chip_freq'     '100'
        #option 'timeout'       '40'




200 = 0782

225 = 0882

250 = 0982




243.75 = 1306

231.25 = ?        so  these are all counting systems   the patterns must repeat.  the freq is base 10  the code is base 16    so   what is that question mark  1206  tried it with timeout of 17  bingo worked

218.75 =1106


once

218.75 = 1106
231.25 = 1206
243.75 = 1306



finding   256.25 = 1406   was easy  used timeout of 15 since 250 uses 16   

 feel free to play with the time out numbers  they may be off by 1

the code in hex is correct for

256.25
250
243.75
237.5
231.25
225
218.75
212.5
206.25
200.00

I did not test lower then 200.

If you meant the /etc/config/asic-freq file, 231.25M is not in it which obviously lies in between 237.5M and 225M, hence my questions about it's source or how it is derived.

So if cgminer in the S3 is based on an older (buggy?) version and not the current one from ckolivas, and Bitmaintech indeed is now releasing the source code of their version, who is going to update the S3 firmware then?

After all Bitmaintech has (had) access to the source code of ckolivas' current version all along, so that issue never was depending on the release of their patches and/or driver.

PM sent.

Dear eoakland,

May you PM your email box?

Wow thats sad

Bitmain, what about my RMA...i have been dealing with someone named "Tim"...who requested/forced me to purchase a multimeter device to perform tests...then he never responds with information about my RMA.  he says they have to look for courier tracking information to prove my s3 is from your factory.  And this is after i gave him the order ID.

I am sitting on an expensive paperweight...2 weeks already.  Can i please get a muthafucking RMA

Thanks for responding to the community. We all look forward to the posted code.

But next time you release a product, can you make sure that posting the source is part of your release plan? Do it early and not as an afterthought. You could save all of us a great deal of wasted time and anxiety.

"Fool me once, foo on you. Fool me twice, foo on me".

When CK posts that he has access to the code and it's what runs in the S3 then I'm a believer.

Great news! Will there be documentation as well?

Great news, thank-you!