Energy Saver FAQ / HELP

What is “Energy Saver”?

Energy Saver is per die voltage tuning given a specific clock speed. Clocks set when energy saver is started will be the clocks the most optimal voltages are found for.

How much electricity can be saved by using “Energy Saver”?

On average between 50-125w per miner. Up to 200w is possible. Of course results not guaranteed.
In detail: if your units are already hand tuned the additional electricity savings wont be significant. In contrast, if your units are “vanilla adjusted”(one clock & voltage for all dies) there is potential for major power savings using “Energy Saver”!

How does “Energy Saver” work?

When energy saver is turned on. Stage 1 of 3 begins: It will restart bfgminer, have an initial 1.5hr cooldown then the first voltage adjustments will be made. All enabled die voltages will be lowered a single “notch”.
Then they will be reevaluated after approximately 40mins.
Evaluation is as follows: if HW% is above 1.1% the voltage will be bumped up a notch and this is considered the optimal voltage for that die.
Otherwise if its below 1.1% then voltage will be lowered again. This process continues till eventually all dies hit higher than 1.1% hw error.
If along the way any dies become unstable, their voltage will be bumped up and tuning will be considered done for that die.
After the initial tuning is “completed” for all dies, 2hr tuning kicks in, all dies hw% are reevaluated for the average of a 2hr window, if any die is still above 1.1% one final voltage bump will be applied. This concludes Stage 1.
Stage 2 then begins: bfgminer is not restarted, but the tuning process runs again in the same manner to further refine the results. After initial tuning & the 2hr window, there is a 4hr window test in the same manner as the 2hr. After the 4hr test completes, Stage 3 begins.
Stage 3 is 4hr per die stability testing. If any die becomes unstable its voltage will be bumped up. After this Stage “Energy Saver” is complete and awaits user saying YES or NO in ADVANCED page.

Is there anything I should do prior to enabling “Energy Saver”?

To get the quickest and most reliable results: Please turn off dies which are very unstable or problematic. Please set dies listed in auto-byass state to “OFF” and clear the bypass list. Please ensure that NO dies are in a throttled state.

Under what circumstances will “Energy Saver” be skipped on a particular die?”

If at any point in the current phase of “Energy Saver” a dies DCDC’s overheat, tuning of that die will be skipped for remainder of that phase – NOTE: if dies are throttled when changing “Energy Saver” settings or applying manual clocks and volts then the original die clock speed will have to be restored manually.
If any stability issues are experienced during tuning, they will be skipped for remainder of “Energy Saver”.
If dies voltages are set outside the range of -0.0366 | -0.1025, tuning will not take place on those dies.
Any dies listed in the auto-bypass/manual-bypass files.
Dies set to OFF.
There may be more situations where tuning will be skipped, but the above listed are the most important.

How long does “Energy Saver” take to complete?

The answer is: it varies wildly.
In bad case scenarios(voltage picky / unstable dies, improperly functioning dies, power issues etc) it can take a few DAYS.
Best case scenario(hardly any stability problems, properly functining dies etc) it will take around an average of 12-16hrs.
Absolute worse case scenario where dies are completely unstable, autotune may not finish at all, by design such dies will eventually make it into the autobypass list and skiped during autotune .. but sometime dies are bad in such a way there is no way to measure their health and they cause autotune to become confused. Recommendation for such conditions: disable the die entirely. Disable then reenable “energy saver”.

Will my unit be stable during the tuning process?

Hopefully yes, most likely no. Many bfgminer restarts may be observed but dont interfere with the process. DONT PANIC!, be patient =). The pi may even reboot a few times or more.
Due to the crappy coding of KNC’s Titan driver and other various software programs that interact w/ the Titan ASICS, all this “unstability” is required in order to achieve an end reult.
Lastly, in some rare cases, hard resetting dies during tuning wont bring them back, eventually they will get added to auto bypass. Please wait till tuning has completed, clear the bypass list, then do a full power cycle of the Titan, this should bring those dies back online.

How will this potential instability affect my hashrate/mining?

When dies are unstable and are in queue to be “reset” there will be a hashrate loss equal to the hashrate of whatever dies are currently not hashing, this is normal. Once they are issued the proper reset theres nearly a 100% chance they will start hashing again w/o requiring manual intervention.
Once again DONT PANIC, let “energy saver” work its magic.
Furthermore, during times of instability, u may see dies not working correctly on the ADVANCED page and u may see odd readings on the STATUS page. Ignore that status unless it appears to be stuck that way for 2hrs or more.

Does it matter where I mine while “Energy Saver” is tuning?

I have not confirmed if it does, but the more stable a pool the better – in either case. I recommend pools that DO NOT have fast changing blocks or many work restarts while tuning is “in progress”.

How do the buttons and status in “Energy Saver” box work?

Start – Starts tuning process using current user specified volts and clocks.
Stop – Stops the tuning process in progress. Restores previous untuned user settings.
Yes or No – These 2 buttons appear when tuning process completes. Yes to accept tuned settings. No to restore previous untuned user settings.
Status – IDLE – when no tuning is in progress. FINISHED! Accept Results? – shows when tuning is complete and awaiting user response. IN PROGRESS – Indicates “Energy Saver” tuning is currently in progress, it will indicate which stage its on. There are 3 stages.
Save Log Files – Allows user to save log files to an archive on local PC, can be submitted for support. Support can be reached via my website http://gentarkincustomtitan.pcriot.com or the litecointalk / bitcointalk Titan threads.

What can I do if Im not happy w/ the results?

One option is to select “NO” when it shows “FINISHED! Save results?”. If you already selected “YES” and wish to revert to previous settings, either apply them by manually or restore them from backup.
“Energy Saver” can always be ran again if desired.

I notice a slight change in some dies voltages regardless if I use or dont use “Energy Saver”, Why?

This is caused by “Per-Die Long Term Stability Checking”. I coded this to make dies which are on the verge of stability .. more stable.
It is active for a period of 2 days whenever the monitoring script is started(power cycle, clock/voltage changes, pi reboot).
If any die is issued a hard reset more than 2 times in this time frame, its voltage will be bumped up a notch.

There is a different version of “Energy Saver” firmware on internet, listed on bitcoinlasvegas.net & ebay using same template as bitcoinlasvegas.net, whats the deal with this?!

This is a fake v1.0 of my firmware. Its an unauthorized release of my previous beta builds for “Energy Saver”. The code is very unstable & buggy and could potentially harm hardware.
AVOID AT ALL COSTS, DO NOT USE FIRMWARE except if obtained from http://gentarkincustomtitan.pcriot.com or elsewhere stated by GenTarkin him/herself.
GenTarkin will NOT SUPPORT firmware purchased from none authorized sources.

What are the licensed terms for GenTarkin’s modified code to the original project?

ALL ORIGINAL CODE in this project retains their respective copyrights & respective licenses.
THE ORIGINAL CODE of this project can be found: https://github.com/KnCMiner/titan


Furthermore, rights granted to me as a licensee through the MIT license chosen by KNC 
(the copyright owner of folder .knc-asic), I sublicense my(GenTarkin) code modifications & additions as follows:

Copyright: (c) 2015 2016 GenTarkin
All rights reserved

    Redistribution and use in source and binary forms, with or without
    modification, are permitted under the terms of the BSD License,
    with the following additional (non-free) restrictions:

    1.)  No portion of this notice shall be removed.
    2.)  Credit shall not be taken for the creation of this source without prior written authorization from GenTarkin.
    3.)  This code is not to be traded or sold without prior written authorization from GenTarkin.
    4.)  Modification of the license activation(if exists) portion of this code is strictly prohibited.

    THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ''AS IS'' AND
    ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
    IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
    ARE DISCLAIMED.  IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE
    FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
    DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
    OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
    HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
    LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
    OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
    SUCH DAMAGE.

On Debian systems, the complete text of the BSD License can be
found in `/usr/share/common-licenses/BSD'.