Quote from: blissz on January 06, 2018, 08:52:51 AM

v2.06 beta :: 05/01 :: test version

Download:
https://mega.nz/#!mxwhmCZb!8Xsj5c2bfvuaK_fSI2av3zrqv3dFz-w3AoSt7W-MD8U

Changes 05/01:
- more stable autotune / reset of ASIC chains (HW errors will be reset to zero after changing a board's frequency)
- ~15 to 20 seconds faster startup of the miner after changing a setting
- optimized cgminer binary size
- fixed browser caching issue when changing between stock and blissz firmware

Changes 22/12:
- reboots the D3 on high temperatures (> 85 deg PCB temp). This feature will save your unit in case your fans will fail.
- improved auto tune algorithm stability
- Increased the chip starting frequency of the autotune algorithm for higher voltages.

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 Cheesy

- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status

Important: The autotune 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, or if it doesn't fit, focus on the last part
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

Hi Blissz

Thanks for all your hard work - much appreciated !

With the latest beta releas, I cannot connect to the Prohashing pool ...... stratum+tcp://prohashing.com:3333
The Miner Status shows the pool as Dead, but on the prev release I can connect without issues.

Regards

Hi Blissz

After searching some forums I found a link that suggested that this is a random error/issue :
https://forums.prohashing.com/viewtopic.php?f=5&t=2796

I rebooted the miners a few times and can now connect again ;-)