Topic: FermTools, a whole new level of monitoring your farms. (Read 59 times)

FermTools, a whole new level of monitoring your farms. The current stable version.
For Windows 7, Microsoft .NET Framework 4.5.2 must be installed

Screenshot:

https://imgur.com/5BQsSd7 https://imgur.com/E4nUbBj


Compiled version https://dropmefiles.com/9EJFR

Password: fermtools
 
Project link on github: https://github.com/Dimasin/fermtools

Description of the possibilities:

Program for convenient display of video card parameters, monitoring, statistics and notifications.

Opportunities:

- convenient display of parameters for all video cards at the same time,

- the ability to determine in which slot a given video card is installed, when you hover the mouse over a window with a frequency, a hint with the identifiers and name of the video card is displayed,

- all parameters can be read from the named pipe (pipe) "pipefermtools" (disabled by default), enabled by the parameter "cb_startPipe": True, in the configuration file,

- reliable (does not react to short-term changes in monitored parameters) and customizable monitoring algorithm: setting is carried out by selecting the averaging time interval and coefficient, monitoring will be triggered if the average parameter value for the specified time interval is less than the maximum (in the same interval) divided by coefficient, for example, the frequency of the memory bus in the operating mode 1500, in the failure mode 150, if the change occurred abruptly, then using the last 60 values to calculate the average (the average is calculated once per second), the average value will continuously decrease and reach half the maximum ( coefficient is 2) after 33 seconds,

- the ability to estimate the response time of monitoring with a jump-like change in parameters: tau = T * Max (1 - 1 / K) / (Max-Min), where: tau is the response time of monitoring, T is the averaging time interval, Max is the operating value of the parameter, Min is the value of the parameter in case of failure, K is the specified coefficient.

- support for some hardware watchdog timers to automatically restart the computer when the computer freezes or the video card fails (watchdog control requires administrator mode to load drivers), support for USB watchdog timers https://shop.open-dev.ru/collection/storozhevye-taymery (Administrator mode is not required),

- manual reset from the context menu, remote reset via the Telegram / reset FermName command,

- recording of events about crashes and errors in the windows application log (requires administrator mode),

- sending notifications by e-mail when you restart your computer due to video card failures,

- sending notifications to a specific user of the Telegram messenger (you need to register your own Telegram bot with the BotFather bot by sending it the / start command and then following its prompts), http proxy is supported without authentication,

- when registering your own bot, you can enable the command mode in which the bot will, upon request, send the parameters of the video cards to the specified user using the commands: / fgpu, / fmem, / lgpu, / lmem, / tgpu, / fanr, / fanp or / all,

- when monitoring is triggered, you can remotely, via Telegram, disable the reboot by sending the / resetoff command to the bot, the command must be sent before initiating the reboot process: "Timeout display the message of fault, sec" + "Timeout display the next message of fault, sec", in this case, monitoring will also be disabled (messages will not come anymore), but the parameters of video cards can also be received manually through the Telegram bot, you can re-enable monitoring and activate the reboot option with the bot command / reseton, the / resetget command will display the current state of the reboot flag,

- execution of a command from the console (cmd) when monitoring is triggered (disabled by default), the command is specified in the value of the "cmd_Script" parameter: "",

- manual editing of the fermtools.json configuration file in the program directory, the configuration file template is created when the program is first started,

- a backup configuration file in case of "damage" to the main fermtools0.json in the program directory, you need to create it manually or copy the main one,

- it is possible to monitor the mining program Claymore's Dual Ethereum + Decred / Siacoin / Lbry / Pascal / Blake2s / Keccak AMD + NVIDIA GPU Miner, the commands / miner and / stat are used to receive data via Telegramm (displays statistics only for ethereum), the program can be reloaded remotely mining with the / mreset FermName command, without restarting the computer,

- the / stat command allows you to compare the mining efficiency of different video cards and farms: by the coefficients (ef) you can judge the mining efficiency of each video card, ef_s is the total efficiency of the farm. The coefficient is calculated by dividing the found balls by the operating time. It has a statistical character, therefore, it is correct to evaluate it only after a sufficiently long time, at least after 1000 balls. In general, the more reliable the ratio will be, the longer the farm has been running. The absolute value of the coefficient depends on the difficulty set by the pool. If we compare the coefficients of farms working on a dwarf and on an etermine, then a dwarf will have twice as much. the difficulty of the dwarf is half that of the etermine.

The drivers for controlling the watchdog are taken "as is" from the openhardwaremonitor project. Also from this project, some code fragments were used to read the parameters of video cards and determine the presence of watchdog timers.

http://openhardwaremonitor.org

https://github.com/openhardwaremonitor

The commands for controlling the USB watchdog timer are taken from project "USB WatchDog Monitor".

https://bitbucket.org/Rdmr/usb-watchdog-monitor/

Brief installation instructions:

1. In the root of the disk, create a folder, for example, Fermtools.
2. Download the archive with the program. It is recommended to download the latest stable version.
3. Unpack the archive into the created folder.
4. Set the e-mail parameters on the appropriate tab, if necessary. Test, if everything is good, save the config.
5. Register your own bot in Telegramm, set the parameters on the appropriate tab, if necessary. Test, if everything is good, save the config.
6. On the first tab, mark with checkboxes the parameters that are critical for changing, which you need to monitor. On the second tab, if necessary, adjust the coefficients. Save the configuration. Testing. Correct the coefficients, test, etc. until the desired result is achieved. Save the config.
7. Register the program to startup. I recommend using the scheduler. Reload the farm. Wait for real failures, if necessary, return to step 6.
8. To use sending requests and receiving commands via Telegram, you can use a regular http proxy without authentication. To do this, check the "Use proxy" box and enter something like "http://proxy.name:port" in the "Proxy:" field, check the connection with the Telegram server by clicking "Test Bot", save the configuration by clicking "Save" and restart the program. To use more advanced proxy servers or services, you can use a local proxy server. For example, http://shadowsocks.org and a sample setup https://blog.wtigga.com/shadowsocks/.
9. It is recommended to restart the program when changing the configuration.
I actually monitor only one parameter - the memory frequency. Default odds.
I highly do not recommend monitoring the temperature. if the card overheats, no monitoring will save it. In any case, the temperature should not be higher than the acceptable for a given video card model and this should be achieved not by monitoring, but by correctly created operating conditions.


Compiled version https://dropmefiles.com/9EJFR

Password: fermtools