[CMD]FarmWatchBot, Claymore, Bminer, Dstm, CC, Eth, CastXMR, Phoenix, Trex, Gmnr

[Acrefawn]

Also my config was changed! I reliase that now. It happened today 17:30PM GMT+3. Config changed its settings to default or something. I reliased that thaks to telegram notifications. I checked telegram and bot no longer sending notifications to me. I changed config again according my settings.

You using latest script version 1.7.9?

[1715468285]

1715468285

[1715468285]

1715468285

[1715468285]

1715468285

[1715468285]

1715468285

[1715468285]

1715468285

[hexen-zz]

Also my config was changed! I reliase that now. It happened today 17:30PM GMT+3. Config changed its settings to default or something. I reliased that thaks to telegram notifications. I checked telegram and bot no longer sending notifications to me. I changed config again according my settings.

You using latest script version 1.7.9?

Yes. I think it changed own settings after error or something.

[Vispilio]

Acrefawn there was an error this morning in my rigs, after which your Autorun.bat started mining for a completely different mining address !!!

It would be criminal and ridiculous if your updates somehow cause the miner to default to another address !!!! you have to act more professional man, or at least make it very clear in instructions to prevent this.

The Miner should never default to another Zcash address, that is insane, for all users out there, be very careful against cheap tricks like this.

I'm waiting for an explanation from you as to how your autorun.bat can default to another zcash address man...

FINAL NOTE: I think everyone using this program should also modify the original autorun.bat file and make sure that all the addresses there are changed to their own ZCASH address, otherwise in the case of any unexpected errors, the system very likely defaults to the miner address specified by Acrefawn, this looks to be the most likely explanation, but I'm open to being corrected...

I want to notify you that the script is open source, you have the right to make any changes you want.

To run the script correctly, you need: Windows Pro x64; full permission to create, move, rename and delete files in the folder of the miner; placing the script files in a folder that (path name) does not contain special characters and spaces; disabled UAC; use the latest version of the script.

In very rare cases it happens that the config.bat file is damaged by the system and the script recreates it with standard settings. In this case and in any other case, Telegram bot notify you. I strongly recommend using Telegram.

Also, I strongly recommend that you use different pools or different servers of the same pool as additional servers. Because if all the servers that you have contributed will be unavailable - the script will switch (only for a 30 minutes, and then will return) to the address to support the project. Agree, the lack of connection with 5 pools is very rare. Do not prescribe one pool, it is important to remember.

Given this information, we can draw the following conclusion. Even if there were no such options, then in case of an error - the miner would shut off and not work at all until you control this issue yourself. So in any case, the process of mining to your address would not continue.

I want to inform you that personally I have nothing to do with this behavior of the script, I remind you that the script is publicly available and everyone can check the source code before installing it. You can use or not use the script, it's your choice and desire. I just posted my work in free access, and my settings in the script code are spelled out as an example.

The script helps automate the mining process, eliminate most of the errors, solve a number of problems, without your participation in it. But this does not mean that the script solves all errors and problems completely. Human control is needed in any case. With the help of the script, you have a unique opportunity to save more money than without it, even considering such situations. Somehow count how many times the script rebooted your miner or computer while you were sleeping or were busy with your own affairs and kept the stability of your income.

In a specific situation, I once again ask for your forgiveness for what happened. I ask you to be attentive. For greater security, you can change the addresses inside the script to your own, it's not forbidden. You can always write to me on Telegram and I will help you with advice, I'm online practically 24/7.

Thanks for the detailed response. I understand you have every right to demand some form of compensation for your efforts, it just is liable to put people in panic mode when such a behavior happens without 100% transparency because we already had to disable many security checks and prompts to run your program without any interruptions...

For the most part your script does a pretty good job of automating the mining process, so I'm happy to continue using it. I'll be in touch via Telegram if anything unexpected comes up... All the Best.

[lynxy]

Hi, installed you program. It works great, but I cannot get id from Telegram Bot, I sent "/start" and get nothing in response. Thanks.

[Acrefawn]

Hi, installed you program. It works great, but I cannot get id from Telegram Bot, I sent "/start" and get nothing in response. Thanks.

Hello. Was a problems with server, sorry for that. Now all is ok. Try again please.

[Acrefawn]

Today version 1.8.0 released!
Changelog:

• Cosmetic changes.
• Ability to adjust the delay after launching the Afterburner.
• Ability to remember the last good bot to send online status.
• Added ETH supporting

Ewbf 0.3.4 version
Claymore 12.6 version
Claymore 10.2 version (ETH)
Dstm 0.5.6 version

[crocozino]

than you man, this is very great and useful scrypt!!
now I'm sure that my rig is working as intended and not masking for a working one))
will share the info about it, if you do not mind!

[Acrefawn]

than you man, this is very great and useful scrypt!!
now I'm sure that my rig is working as intended and not masking for a working one))
will share the info about it, if you do not mind!

Thank you very much!

[charette.mtb]

Hello,
Thank for your code.
Could you add nvidiainspector to your OC software list ?

[zarete]

Hello


How I can reboot computer all days at same hour??, 11.20AM


i put delay to 24 hour and reboot to 11:20 but 1 day later pc is not reboot.


Thank you, very interesting your proyect

[Acrefawn]

Hello,
Thank for your code.
Could you add nvidiainspector to your OC software list ?

Hello! Thx! Will add in 1.8.1

Hello


How I can reboot computer all days at same hour??, 11.20AM


i put delay to 24 hour and reboot to 11:20 but 1 day later pc is not reboot.


Thank you, very interesting your proyect

Delay 24h means 24 RUNNING hours, if your script will be restarted by error or manually from new start time +24h.
Use midday/midnight restart at 12:00/00:00
Thx for reply!

[chufleco]

By any chance can someone make this work for Linux (Ubuntu) running Dstm

[Acrefawn]

Today version 1.8.1 released!
Changelog - [1.8.1]

• Support Palit Thunder Master.
• Error handling: 0 mb, failed to connect.
• Command /report has been added to manage the configuration of hourly notifications via Telegram.
• Error handling in the first block (when the script starts), now if the script can not be started, the script can restart the computer.
• Notification via Telegram in case of config.bat file is damaged.
• Added more messages to the log file.
• Cosmetic and minor fixes.
• Added ETH miner support (test over).

Ewbf 0.3.4 version
Claymore 12.6 version (Equihash)
Claymore 10.2 version (Dagger-Hashimoto)
Dstm 0.5.6 version

[Acrefawn]

By any chance can someone make this work for Linux (Ubuntu) running Dstm

You can use Dstm on Windows with same hashrate

[r3lentleSs]

DSTM miner gets killed due to low hashrate average, even tho i've set the hashrate errors to 99

Code:

[wo 06/12/2017][16:15:00] Config.bat loaded.
[wo 06/12/2017][16:17:39] Miner was started. v.1.8.1.
[wo 06/12/2017][16:21:55] Abnormal hashrate. Average: 1839/1840 Last: 1818/1840.
[wo 06/12/2017][16:22:22] Abnormal hashrate. Average: 1836/1840 Last: 1828/1840.
[wo 06/12/2017][16:23:16] Abnormal hashrate. Average: 1835/1840 Last: 1823/1840.
[wo 06/12/2017][16:23:43] Abnormal hashrate. Average: 1834/1840 Last: 1808/1840.
[wo 06/12/2017][16:24:10] Abnormal hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Low hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Miner restarting... Miner ran for 00:09:06.
[wo 06/12/2017][16:25:16] Process zm.exe was successfully killed.
[wo 06/12/2017][16:28:11] Config.bat loaded.
[wo 06/12/2017][16:28:34] Config.bat loaded.
[wo 06/12/2017][16:29:14] Miner was started. v.1.8.1.
[wo 06/12/2017][16:43:54] Low hashrate. Average: 1826/1820 Last: 1816/1820.
[wo 06/12/2017][16:43:54] Miner restarting... Miner ran for 00:14:46.
[wo 06/12/2017][16:44:30] Process zm.exe was successfully killed.

Windows 10 PRO
6X P106-100 GPU's

Core + 225 MEM + 200 POW limite 67 TEMP 68

I'm using 1830 as ~

DSTM miner always start with a higher hashrate, and starts to drop. Thats why i'm getting alot of hashrate erros.
So how to fix this, i've set 99 hashrate error, and after 20 minutes. zm.exe miner gets killed
http://prntscr.com/hjxkyp
Why doest it say "hashrate error = 0/99 and then 57/99
Should i set it to 1000 or what?

[ramarval]

DSTM miner gets killed due to low hashrate average, even tho i've set the hashrate errors to 99

Code:

[wo 06/12/2017][16:15:00] Config.bat loaded.
[wo 06/12/2017][16:17:39] Miner was started. v.1.8.1.
[wo 06/12/2017][16:21:55] Abnormal hashrate. Average: 1839/1840 Last: 1818/1840.
[wo 06/12/2017][16:22:22] Abnormal hashrate. Average: 1836/1840 Last: 1828/1840.
[wo 06/12/2017][16:23:16] Abnormal hashrate. Average: 1835/1840 Last: 1823/1840.
[wo 06/12/2017][16:23:43] Abnormal hashrate. Average: 1834/1840 Last: 1808/1840.
[wo 06/12/2017][16:24:10] Abnormal hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Low hashrate. Average: 1832/1840 Last: 1819/1840.
[wo 06/12/2017][16:24:40] Miner restarting... Miner ran for 00:09:06.
[wo 06/12/2017][16:25:16] Process zm.exe was successfully killed.
[wo 06/12/2017][16:28:11] Config.bat loaded.
[wo 06/12/2017][16:28:34] Config.bat loaded.
[wo 06/12/2017][16:29:14] Miner was started. v.1.8.1.
[wo 06/12/2017][16:43:54] Low hashrate. Average: 1826/1820 Last: 1816/1820.
[wo 06/12/2017][16:43:54] Miner restarting... Miner ran for 00:14:46.
[wo 06/12/2017][16:44:30] Process zm.exe was successfully killed.

Windows 10 PRO
6X P106-100 GPU's

Core + 225 MEM + 200 POW limite 67 TEMP 68

I'm using 1830 as ~

DSTM miner always start with a higher hashrate, and starts to drop. Thats why i'm getting alot of hashrate erros.
So how to fix this, i've set 99 hashrate error, and after 20 minutes. zm.exe miner gets killed
http://prntscr.com/hjxkyp
Why doest it say "hashrate error = 0/99 and then 57/99
Should i set it to 1000 or what?

Hello there, try  lowering the average speed to 1780-1800 on the config.bat then u will not have any problems (script sensing avg hashing speed is below the normal), you dont need to mess with the hashing errors at all.

hope this help you.

[starkinsaur]

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.

[r3lentleSs]

Yeh, i've set it to 1750 and working good so far.

[Acrefawn]

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.

Hello! Thank you very much for your reply and detailed info. I fixed some issues what you talking about in 1.8.2, please try it and report to me.
About hashrate - good idea - i will think about it, thank you! But please try to use not exact value but a little bit lower.

Yeh, i've set it to 1750 and working good so far.

Hello! Thank you for reply and using my script! Yes, try to use little bit lower hashrate, not exact value but with ~2%-5% difference.
Thank you very much!

[Acrefawn]

Today version 1.8.2 released!
Changelog - [1.8.2]

• Significant code optimization.
• Clear the error list.
• Fix server switching. Added a message to which server number the miner switched.
• Added ignoring of additional coins during ether mining. Added support for classic ether.
• The restrictions for the config file and the file are increased.
• Most likely, the bug of the configuration file is completely fixed.
• The MSIA timeout setting has been moved to the configuration file. The waiting time is reduced by 20 seconds.
• Fixed the problem of determining 0 H/s (Sol/s).
• Added error handling of type: unknown error, cuda failed.
• Added support for XMR.
• The timeout of shares is increased to 15 minutes.

Ewbf 0.3.4 version
Dstm 0.5.6 version
Claymore 12.6 version (Equihash)
Claymore 10.2 version (CryptoNote)
Claymore 10.2 version (Dagger-Hashimoto)