This strategy increases the number of measurements when some environmental condition changes; ontherwise, it performs just one or two measurement per day when the conditions are stable. Probably the whole unit is less stressed in this way and the outcome is roughly the same.
As this discussion on AutoCal has evolved, I think it would be helpful to reiterate a few points and clarify certain misconceptions to wit:
1) AutoCal can only run when the V2 is turned off while connected to power.
2) When AutoCal runs, the audio input/ouput signals are physically disconnected from the V2. Some amps (while turned on) may hum when their audio input/output are disconnected. The Job 225 comes to mind as a specific example. Thus, having AutoCal run all the time when the V2 is turned off may be unacceptable for a subset of users who wish to keeps their amps on all the time.
3) The V2 absolutely does not "need" to have AutoCal to run continuously when the unit is off. This was simply a default approach as in "why not, it's off, just let AutoCal run, can't hurt...". There's no definitive guidance as to how often AutoCal needs to run to keep the V2 calibrated. Once a month may be sufficient. But if needed, it's there.
4) AutoCal does not in any way "stress" the V2 when it's active. One possible exception to this statement is that each AutoCal cycle writes the results into flash memory and after about 1,000,000 writes flash memory can wear out. But we're talking over 20 years of continuous AutoCal for that to happen. No worries.
5) AutoCal, at least as initially conceived and implemented, does not use measurements and related criteria to determine if/when AutoCal is necessary. It simply runs when told which initially at least was all the time when the V2 was turned off. It's now been updated to wait 5 minutes between each cycle. In this respect, AutoCal is "dumb". Introducing a "smart" approach is conceptually interesting but would take considerable testing to prove out its efficacy and even then this begs the question of what problem is this "smart" solution actually solving?
Perhaps the simplest and most flexible approach to AutoCal is to make it possible for the user to decide how best to employ it. I mentioned something along these lines in a prior post. Here's an updated summary.
When the V2 is off and AutoCal is disabled....
* Pressing Enter button on remote - Enables AutoCal
a) starts a single AutoCal cycle
b) after completion, unit waits 5 minutes, and then starts the next cycle.....process repeats indefinitely
c) You can tell AutoCal is enabled because the decimal point on the DM1 Display Module remains lit even when the V2 is off and blinks anytime an AutoCal cycle is active.
* Pressing Enter button (again) - Disables AutoCal
a) AutoCal is off and never runs unless re-enabled
b) You can tell AuoCal is disabled because the decimal point on the DM1 Display Module is off.
