Quote from: DrYM on February 19, 2018, 07:47:57 AM

Quote from: Acrefawn on February 18, 2018, 03:50:23 PM

The ability to update the script via the Telegram command is added.

Everything works great! One minor comment - in the Telegram bot, when you click "/" there is no "update" in the auto-complete options. Also, "update" is not in the "/help" result. I tried the "/update" and it worked just fine, it's just not in the list (using the premium 1.9.2). Thanks!

Fixed.

Quote from: sebushi113 on February 19, 2018, 08:55:40 PM

Quote from: Acrefawn on February 18, 2018, 03:50:23 PM

Today version 1.9.1 released!

Ewbf Equihash
Dstm Equihash
Claymore Equihash
Claymore CryptoNote
Claymore Dagger-Hashimoto
Ccminer tpruvot, alexis (palgin), KlausT

Awesome little script Acrefawn!
You should make one for hsrminer! Grin

Quote from: az001 on February 27, 2018, 02:36:38 PM

Hi,

I use the PhoenixMiner.exe ver 2.6,
Link - https://bitcointalk.org/index.php?topic=2647654.0

And HSRMINER
Link - https://bitcointalk.org/index.php?topic=2565979.0

which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future

Thanks again for the great work!

Thank you. Will think about it. On this weekends update i will share some other miners.

Quote from: Siddxa on February 20, 2018, 05:25:46 AM

Hello!

Im got error Sad

use dstm 0.6 win10

zm.log is missing. Probably zm.exe hangs...

Hello i hope you fixed this error, if not - contact me in Telegram t.me/acrefawn

Quote from: BrazilianGirl on February 20, 2018, 07:41:36 AM

How can we remove thE GPU | Power usage and Efficiency, its wasting of time.. ! I don't know why its keeping showing.
Huh

Dont understand what you are talking about. Sorry.

Quote from: Spiralx on February 24, 2018, 04:04:44 PM

Can we get an option to disable the scheduled miner restart messages? I have multiple rigs with audio alerts on the telegram bot chat in case of problems so it is annoying to be spammed with "scheduled miner restart" and "miner started" messages only to find out there is nothing that requires my attention when I check the app.

Done. Will be added in 1.9.4 version.

Quote from: Mapuo on February 26, 2018, 12:08:22 PM

Hi, do you planning to add phoenix miner support?

Yes.

Quote from: xberg on February 26, 2018, 02:39:06 PM

Hi,
I have a bug with the Claymore zcash 12.6 version of autorun:
When Claymore generates the error "GPU 0 mining has stopped because -tstop temerature reached" autorun closes. Claymore continues running but autorun does not.

Thank you for report I will test it now and fix.

Quote from: zeef on February 27, 2018, 11:00:51 PM

Hi,

Nice work on bat

Im testing the functionality, but i have two doubts.

If i want to add an backup pool i add this on Config_xClay:

# =================================================== [Miner]
# Set the main server mining command here to auto-create Clay_miner.bat file if it is missing or wrong. [keep default order]
commandserver1=NsGpuCNMiner.exe -xpool stratum+tcp://eu.xxxxmine.graft.network:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# When the main server fails, ClayXMRautorun.bat will switch to the additional server below immediately. [in order]
commandserver2=NsGpuCNMiner.exe -xpool stratum+tcp://pool.graftpool.online:4444 -xwal xxxx -xpsw x -allpools 1 -tstop 80 -logfile miner.log -wd 0
# Configure miner command here. Old Clay_miner.bat will be removed and a new one will be created with this value. [keep default order] internetcheck=1 required.
# The default number of servers is 5, however, you can add or remove as many as you need. e.g. you can have servers 1 2 3 or you can have 1 2 3 4 5 6 7 8 9. There is no upper limit - e.g. you can have 1000 if you want. The minimum is 1.
# =================================================== [Overclock program]

But when for example i put purposely an error in my first server1, the program doesn t shift to commandserver2! Cool

Its ok my syntax? or have to change the ClayXMRautorun instead of Config_xClay..

Another thing is If i tried to change :

# Set how many GPU devices are enabled.
gpus=1

and have 8 gpus, doens t gives me any error too..

and why it comes with default valor of 0, and worked good with 0 value?

Even if i have more gpus installed..

Regards

Thank you!
1) For test server failover put an mistake in server name or server port in commandserver1, then wait for 2 minutes, then server will be switched. Program can recognize if it is server problem or internet. So just cable disconnecting will not help to test. And program wait for 2 minutes because of miner self reconnect period.
2) Because if you use gpus=0 it will count them automatically, and if you use gpus=NUMBER program knows EXACT value. About "doesnt gives me any error" you probably disabled allowrestart function.

Quote from: logitech69 on February 28, 2018, 03:18:21 AM

Quote from: starkinsaur on December 06, 2017, 11:13:08 PM

Hi Acrefawn,

Thanks for your excellent work here.

I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.

Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.

Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.

I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)

2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362

As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.

Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.

Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.

Hi
Firstly, I would like to thank you for this wonderful script. You are awesome.
I've been testing it for the past few hours and I came across the same problem as posted above.

I am using MiningPoolHub and auto-switching coins within the Equihash algorithm using DSTM on Windows 10 and Nvidia 1070s.
When the difficulty changes or when DSTM is switching from one coin to another, my hashrate temporarily drops by 2000 sol/s for about 15 seconds but the script recognizes it as an error and begins to restart the miner. If I change the "average hashrate" to something very low, it won't make any sense because then there would be no point in monitoring it. Is there anyway I can add a delay or a temporary buffer for those 15 seconds while the difficulty is changing or when it's changing the coin being mined?

I appreciate all of your help and thank you for making this script. Once this gets resolved, I will donate and go for the premium

Thank you for detailed report, I will think about it. But in generally it is hard to realyse because we cant predict hashrate drop timeout or value. So your suggestion may not work...

Quote from: flatounet on March 01, 2018, 09:54:17 AM

Quote from: az001 on February 27, 2018, 02:36:38 PM

Hi,

I use the PhoenixMiner.exe ver 2.7b,
Link - https://bitcointalk.org/index.php?topic=2647654.0

which of the scripts versions will fit, if any? if not, I would LOVE if you'll support those in the very near future

Thanks again for the great work!

+1

same here ..

if you can limit log file size,
i dont have big disk ...

Do not worry program self clean Logs and Screenshots folders.