Quote from: JBT on February 25, 2014, 04:41:11 PM

ok so start slow and go faster slowly. thats one thing cgwatcher lack is that type of thing

It can be done. Reboot CGWatcher every day at the same time, and setup multiple profiles for each clock/voltage setting.

Eg. In the scheduler section:

* Set default profile to 45:1:750
* Restart CGWatcher everyday at 6pm (to start with 45:1:750 as it's the default)
* Change profile to 48:1:850 at 6:10pm
* Change profile to 53:2:950 at 6:20pm

If you get LIBUSB errors after a couple of days that require the PC to be rebooted, then set CGWatcher to automatically reboot the PC each day, and tick the box to run CGWatcher on startup with the default (45:1:750) profile.

This worked great for me for a few weeks, until my boards absolutely needed manual stuffing around to get them running at 950mV... I'm now just running them at 54:2:850 for 76.7GH/s total (three of them at 20.4GH/s each, the last one lagging behind at 15.4GH/s...). It's stable for at least a week at a time, if not more. Just need to stop playing with the settings and let it run for a few weeks.