Hi Acrefawn,

Thanks for the update, looks good.

Since the update I have not experienced the issue where too many cards were detected. Well done.

Low Hashrate detection
In response to nuisance restarts from low hashrate, I have reduced my input for "average" hashrate down significantly from the real average (-~7%).
Unfortunately, I am still experiencing nuisance restarting of the miner when hashrate drops momentarily due to difficulty changes.
I understand that I could further drop the "average" hashrate to remedy this but I feel like that is starting to defeat the point of monitoring it in the first place.

To expand on my previous suggestion and above issue; the hashrate monitoring could be more sophisticated and less hypersensitive with the following features:
-Automatic calculation of real average hashrate
-Acceptable hashrate tolerance determined as a configurable % of real average hashrate
-Require several events of NON acceptable hashrate before initiating a restart or other corrective action

There could be a problem with that though. If the software is calculating the average hashrate automatically, it may need to ignore the first reported hashrate after each miner launch (first report is often an outlier)


Regarding over-temperature protection:
In the case of DSTM's ZM Miner: when --temp-target is defined, the miner starts reducing the workload to prevent the GPU from exceeding the set temperature.
It seems(please confirm?) that autorun currently takes the set temperature as defined for the miner and uses this as the temperature limit for its own purpose.
So, the miner never gets the opportunity to respond because autorun shuts it down at the same point where the miner should start down-regulating the workload.

Can autorun be modified to allow the max GPU temp to be set by the user rather than taken from the config parameters used for the miner?
For example: miner set to reduce workload at 76 degrees and autorun resets machine at 80 degrees. That way, autorun does not interfere with the miner.


ZM Version 0.5.7 has been released. I'm going to give it a whirl on one rig with autorun and see what happens.