Antminer D3 Blissz firmware (10/12 v1.12 update)

[Grizy2033]

---

Dec 14 04:59:15 (none) local0.err cgminer[376]: low hashrate detection trigger: 31.464000 Gh/s
Dec 14 04:59:15 (none) local0.notice cgminer[376]: set voltage = 1143.942031  real:255 mv
Dec 14 04:59:15 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.err cgminer[376]: cgminer time error total_secs = 1513227556.664247 last_total_secs = 1.000000
Dec 14 04:59:17 (none) local0.err cgminer[376]: D1 0: work 7f not find error

i see 31,4GH/s at @1150W  that its true? its constant?

[blissz]

---

Dec 14 04:59:15 (none) local0.err cgminer[376]: low hashrate detection trigger: 31.464000 Gh/s
Dec 14 04:59:15 (none) local0.notice cgminer[376]: set voltage = 1143.942031  real:255 mv
Dec 14 04:59:15 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.notice cgminer[376]: set_PIC16F1704_voltage_new ok, voltage = 0xff
Dec 14 04:59:16 (none) local0.err cgminer[376]: cgminer time error total_secs = 1513227556.664247 last_total_secs = 1.000000
Dec 14 04:59:17 (none) local0.err cgminer[376]: D1 0: work 7f not find error

i see 31,4GH/s at @1150W  that its true? its constant?

No this is the low hashrate trigger for triggering the reboot when needed, but I see it's not correct during startup as it's still tuning the frequency.

[blissz]

v2.02 beta :: 14/12 :: test version

Download:

https://mega.nz/#!DghG2KwC!OJEK4_d47skRB6yrLRE2bfzlX7FWXLXzgoKA_q5dKco


Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected


Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status

and last but not least...

- added a first version of the auto tune!  

When enabled this will search for the best possible frequency at the given voltage setting. The first 5 to 10 minutes it will search for a good base to start from. After that it checks for excessive HW errors every 15 minutes and adjusts the frequency accordingly.

Important: This feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:

set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information

Thank you!

Please test and give feedback / a kernel log how it works for you. I need some feedback on this version guys 

[iamqw]

what version is that?
i tried your 1.12 and gives HW every minute or so, at lowest voltage and 400 freq.

[sanitariu]

Hello,
to be on the safe side is it possible to add something like this.

if temp > 100 degrees ; killall -9 cgminer

I will soon test version 2.

[blissz]

Hello,
to be on the safe side is it possible to add something like this.

if temp > 100 degrees ; killall -9 cgminer

I will soon test version 2.

Will make it a bit more advanced as sometimes one chip can give a bad reading, but something like that is useful yes

[mkmfins]

v2.02 beta :: 14/12 :: test version

Download:

https://mega.nz/#!DghG2KwC!OJEK4_d47skRB6yrLRE2bfzlX7FWXLXzgoKA_q5dKco


Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected


Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status

and last but not least...

- added a first version of the auto tune!  

When enabled this will search for the best possible frequency at the given voltage setting. The first 5 to 10 minutes it will search for a good base to start from. After that it checks for excessive HW errors every 15 minutes and adjusts the frequency accordingly.

Important: This feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:

set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information

Thank you!

https://img15.hostingpics.net/pics/453940Untitled.jpg

Please test and give feedback / a kernel log how it works for you. I need some feedback on this version guys 

My test is up there.

[blissz]

what version is that?
i tried your 1.12 and gives HW every minute or so, at lowest voltage and 400 freq.

This beta can automatically find the best frequency for the voltage you selected (see how to setup in the screen shot)

[iamqw]

is your firmware reversible or not?
I mean it can be rolled back to original bitmain version?

[lashatatu]

is your firmware reversible or not?
I mean it can be rolled back to original bitmain version?

it is, check first post

[blissz]

...

And now, what should I do, Blissz?

You definitely didn't win the lottery with your boards... they perform really bad (all of them). I am not sure if it can be a control board problem. Try swapping the bad chain cable and position with another one would be a good test

[wkhash]

Poor performance on auto tune. Creates a mess of my machine heh. Once it finds "stable" settings it is still very unstable. I don't think the system waits long enough for each test to perform fully. Looks like it takes a full minute just for the chain to get up to the new set speed before the errors can start rolling in. Also even at stable settings I adjusted to manually the interface would report "x" on several random ASIC chains after a short while. Rolled back to v1.12.

Messaged you the logs blissz

[blissz]

Poor performance on auto tune. Creates a mess of my machine heh. Once it finds "stable" settings it is still very unstable. I don't think the system waits long enough for each test to perform fully. Looks like it takes a full minute just for the chain to get up to the new set speed before the errors can start rolling in. Also even at stable settings I adjusted to manually the interface would report "x" on several random ASIC chains after a short while. Rolled back to v1.12.

Messaged you the logs blissz

Thanks for the logs! Looking at it I can conclude it is a little too aggressive maybe but you didn't wait for the second part of the auto tuning long enough. (where it lowers the frequencies). I have ideas to speed up the second part, as it's not really clear now. Maybe I can highlight the UI as well, so you can see it's still busy.

[wkhash]

I noticed it slowly pulling them back down to previous known good lower frequencies but those other freq were not stable either. Basically one of my chains is stable at 375. It tuned it up to 475 then spent forever slowly rolling it back while it had a very large number of errors and continual asic failures being thrown.

Made me uncomfortable to watch it fail so often and only slowly be pulled back.

[blissz]

I noticed it slowly pulling them back down to previous known good lower frequencies but those other freq were not stable either. Basically one of my chains is stable at 375. It tuned it up to 475 then spent forever slowly rolling it back while it had a very large number of errors and continual asic failures being thrown.

Made me uncomfortable to watch it fail so often and only slowly be pulled back.

ok thanks for the input

[samshanna]

Blissz from what I am seeing I can put each miner on autotune and allow it to determine which card can take more.  I already know all my rigs are good at minimum 450 and 7 or 8.  Mostly 456.   Once it goes thru the process I can then go back in and adjust each card to either the new higher frequency or revert back to the old stable settings.   On the first try the autotune actually took one of my cards and lowered it way lower than was actually stable so I went back in after it was finished and changed it back to the higher setting.   Make sense?   

[david916]

Blissz from what I am seeing I can put each miner on autotune and allow it to determine which card can take more.  I already know all my rigs are good at minimum 450 and 7 or 8.  Mostly 456.   Once it goes thru the process I can then go back in and adjust each card to either the new higher frequency or revert back to the old stable settings.   On the first try the autotune actually took one of my cards and lowered it way lower than was actually stable so I went back in after it was finished and changed it back to the higher setting.   Make sense?   

did you send the kernel log ?  I hope everyone opining also sent the log like the dev asked.

[Knightslugger]

after you set autotune, are you guys rebooting or just letting it be after clicking Save&Apply?

[martyshmoo]

after you set autotune, are you guys rebooting or just letting it be after clicking Save&Apply?

I am trying autotune on 14Volts now for a good daytime setting.

It never really mines though...

All shares rejected but 2.

I found 11 Blocks for you though?

Man this version not cool yet.

My Miner never actually mines!

What to do!???

Patient one.

M

[blissz]

after you set autotune, are you guys rebooting or just letting it be after clicking Save&Apply?

I am trying autotune on 14Volts now for a good daytime setting.

It never really mines though...

All shares rejected but 2.

I found 11 Blocks for you though?

Man this version not cool yet.

My Miner never actually mines!

What to do!???

Patient one.

M

Sorry this beta version is definitely not yet ready for that as it starts at a way too low frequency which will mess things up. I am working on a next beta version that should improve the things I've seen. Can you PM your kernel log? Thanks