[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[patrike]

new Wildrig Multi version 0.24.1
...

Hi. I've updated all of these now.

[1715029047]

1715029047

[1715029047]

1715029047

[1715029047]

1715029047

[patrike]

Awesome Miner version 7.7.1

 Features
  - Awesome Miner API endpoint for reading and setting GPU clocking properties
 Integration
  - Luxor Mining Pool Equihash pool profit display
  - Nicehash account balance. Requires to be configured in the Options dialog, Balance section
  - Mining Dutch pool list updated
 Changes
  - When adding multiple External Miners by a list of IP addresses, any duplicates compared to what's already added in Awesome Miner will be ignored
 Mining software
  - Kawpow Miner 1.2.3
  - Miniz Miner 1.5t3
  - CpuMiner-Opt 3.13.2
  - WildRig Miner 0.24.1
  - TeamRedMiner 0.7.1
  - NanoMiner 1.9.4
  - Z-enemy Miner 2.6.2
 Corrections
  - Correction to ASIC chip ideal hashrate calculations for Awesome Miner Antminer S9 Dual mode firmware
  - Correction to GPU selection using Claymore Ethereum Miner in systems with a mix of AMD and nVidia GPUs
  - Correction to Mining Profile selection for rule action and added missing 65 TH mining profile selection for Antminer S17 running latest firmware version

[JayDDee]

Awesome Miner version 7.7.1
  - CpuMiner-Opt 3.13.2

v3.13.2 was a test release not intended for production use. Downloads have since been disabled.
Although there were no serious bugs found it should not be used.

cpuminer-opt-3.14.1 is now available with support for segwit.

[patrike]

Awesome Miner version 7.7.1
  - CpuMiner-Opt 3.13.2

v3.13.2 was a test release not intended for production use. Downloads have since been disabled.
Although there were no serious bugs found it should not be used.

cpuminer-opt-3.14.1 is now available with support for segwit.

Thanks for the update!

It was actually a typo in the release notes. I initially had planned for v3.13.2 but revered due to the CpuMiner-Opt release notes indicating it was a test version. The actual version included was v3.13.1 so hopefully all should be fine.

I've also pushed an update for version 3.14.1 now, available for everyone via the "Update mining software definitions".

[NCarter84]

Anyone noticed the USD value of Raven mining daily is out of whack but the daily coins is in line?

IE: Showing I should get 45 coins, but showing daily value at $1.25/day.

Also, since I upgraded I have one rig that randomly stops working on CPU.

Here is what Diagnostics says:

Initialize diagnostics (6)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 7.7.1
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 19.11.3
AMD OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: SrbMinerMulti, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Failed to prepare or save configuration file
Failed to start miner in Diagnostics mode
Diagnostics completed

I hit start, nothing happens. I have to configure a new miner, start new miner and then stop it then go back to my 1st one and it runs OK.

Weirdest thing I've ever seen.

[powerstr]

PhoenixMiner 5.0b

Added support for mining with 4 GB AMD cards beyond the DAG epoch 350. Depending on the OS and driver versions, you will be able to use 4 GB AMD cards until epoch 372-373 under Windows, and 380 under Linux.
Added new -dagrestart command-line option to work around the problems with DAG allocation on 4 GB AMD cards under some driver versions. See Readme.txt for more information.
Added support for latest AMD drivers 20.4.2 under Windows and 20.10-1048554 under Linux
Many other small improvements and fixes

[narousberg]

Hi Patrike, i found profitability calculation bug.
If for some rigs defined electricity cost in EUR and you want see how big profitability in BTC, you electricity price will not be converted to BTC. System calculate electricity cost 1:1 to BTC.
Please check.

[narousberg]

@patrike Please add Equilhash 125.4 for Prohashing.com pool

[patrike]

Anyone noticed the USD value of Raven mining daily is out of whack but the daily coins is in line?

IE: Showing I should get 45 coins, but showing daily value at $1.25/day.

I think these numbers looks fine, but please let me know if I misunderstood your point here.
What is being displayed in Awesome Miner is similar to what both WhatToMine and CoinCalculators.io are reporting. Right now the number of coins per day are a bit higher compared to when you wrote your message.

Also, since I upgraded I have one rig that randomly stops working on CPU.

Here is what Diagnostics says:

Initialize diagnostics (6)
Starting Diagnostics (30s). Awesome Miner Remote Agent version: 7.7.1
OS: Microsoft Windows 10 Pro 64-bit
AMD driver version: 19.11.3
AMD OpenCL Platform ID: 0
Microsoft VC++ 2013 runtime installed: No
Microsoft VC++ 2015 runtime installed: Yes
Starting Mining Software
Setting up Miner Engine. Instance: 2
Engine Type: SrbMinerMulti, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Failed to prepare or save configuration file
Failed to start miner in Diagnostics mode
Diagnostics completed

I hit start, nothing happens. I have to configure a new miner, start new miner and then stop it then go back to my 1st one and it runs OK.

Weirdest thing I've ever seen.

"Failed to prepare or save configuration file" indicates one of the following:
1) Awesome Miner Remote Agent doesn't have permission to write to the folder where SrbMinerMulti is located (%localappdata%\AwesomeMinerService\). It could be some non-default folder permission settings or security software that is blocking this operation.

2) There could also be some internal issue in Remote Agent when it's generating the configuration file. If this is the case I would need the Remote Agent log file, located in the folder listed above.
Thanks!

[patrike]

Hello!

How do I make Awesome Miner detect that Claymore doesn't initialize?

I have a few nasty rigs that may sometimes not initialize properly and Claymore either throws "Miner cannot initialize for 5 minutes, need to restart miner!" error (and freezes) or just stops at GPU initialization.

I don't have enough time right now to deal with these rigs, so I just want AM to detect such behavior and restart the rig using "shutdown -f -r -t 0" because if such a thing happens, only a full reboot helps.

Which rule shall I create for this situation?

And a feature request: sometimes GPUs fall of the bus and are not detected. Right now I have to set up a rule per each farm that detects a number of devices and if it's not the same as specified in the rule, the notification is displayed.

But maybe it is possible to be able to set up a GPU count in the Properties of each rig? Because right now I need to create 50+ rules for each rig.

1) The built-in Offline Detection rule should be able to detect this. By default the rule only provides a notification, but you can modify it to also take an action like reboot. The action name is "Miner command" for this, where you will find Reboot as one of the optioins.

Do you see the notification message when Claymore miner ends up in this state?

2) Good point about specifying a GPU count on the miner. Thanks!

[sxemini]

Hello!

How do I make Awesome Miner detect that Claymore doesn't initialize?

I have a few nasty rigs that may sometimes not initialize properly and Claymore either throws "Miner cannot initialize for 5 minutes, need to restart miner!" error (and freezes) or just stops at GPU initialization.

I don't have enough time right now to deal with these rigs, so I just want AM to detect such behavior and restart the rig using "shutdown -f -r -t 0" because if such a thing happens, only a full reboot helps.

Which rule shall I create for this situation?

And a feature request: sometimes GPUs fall of the bus and are not detected. Right now I have to set up a rule per each farm that detects a number of devices and if it's not the same as specified in the rule, the notification is displayed.

But maybe it is possible to be able to set up a GPU count in the Properties of each rig? Because right now I need to create 50+ rules for each rig.

1) The built-in Offline Detection rule should be able to detect this. By default the rule only provides a notification, but you can modify it to also take an action like reboot. The action name is "Miner command" for this, where you will find Reboot as one of the optioins.

Do you see the notification message when Claymore miner ends up in this state?

2) Good point about specifying a GPU count on the miner. Thanks!

I create 1 rule for every GPU count. 1 Rule for 6 GPU Rigs and 1 rule for 8 GPU Rigs and so on. if a GPU not detected, it add a Tag (GPU Missing). But if you integrate such feature in AM would be nice.

@Patrike:

If you add such feature, keep in mind: 1 Rig with 7 AMD and 6 Nvidia Cards, it runs 2 Miners.
So it must be configurated per Miner and not per Rig, and we must configurate which GPU´s the miner instance use and check.
I hope you understand the problem.

[patrike]

PhoenixMiner 5.0b

Added support for mining with 4 GB AMD cards beyond the DAG epoch 350. Depending on the OS and driver versions, you will be able to use 4 GB AMD cards until epoch 372-373 under Windows, and 380 under Linux.
Added new -dagrestart command-line option to work around the problems with DAG allocation on 4 GB AMD cards under some driver versions. See Readme.txt for more information.
Added support for latest AMD drivers 20.4.2 under Windows and 20.10-1048554 under Linux
Many other small improvements and fixes

Thanks for the update. I've pushed an update of Mining Software Definitions with PhoenixMiner and a few others.

[patrike]

Hi Patrike, i found profitability calculation bug.
If for some rigs defined electricity cost in EUR and you want see how big profitability in BTC, you electricity price will not be converted to BTC. System calculate electricity cost 1:1 to BTC.
Please check.

One limitation right now is that if you use BTC as display currency, you will see that the currencies you can select between for the electricity will be limited to BTC and USD. If you change the elecitricty price from BTC to USD it will at least be closer, although not perfect.

Showing income in BTC makes sense to support in addition to USD/EUR so you don't have to make this configuration change. I will look into if it can be displayed in the Information column in a good way and you can expect this to be part of the next release.

@patrike Please add Equilhash 125.4 for Prohashing.com pool

If I go to the Online Services tab, Prohashing.com Equihash 125.4 is listed. It should have been picked up automatically by Awesome Miner once they added it. Do you see this pool now?

[patrike]

I create 1 rule for every GPU count. 1 Rule for 6 GPU Rigs and 1 rule for 8 GPU Rigs and so on. if a GPU not detected, it add a Tag (GPU Missing). But if you integrate such feature in AM would be nice.

@Patrike:

If you add such feature, keep in mind: 1 Rig with 7 AMD and 6 Nvidia Cards, it runs 2 Miners.
So it must be configurated per Miner and not per Rig, and we must configurate which GPU´s the miner instance use and check.
I hope you understand the problem.

I agree that it must be per Managed Miner (or Managed Profit Miner).

There are more than one way of having a configuration for this:

1) You enter a number for the Managed Miner, like 6 GPUs. The trigger will look if the number of GPUs reported by the mining software are less than 6.

In this case you need to configure this specific number for each miner and this concept is explicit and easy to understand

2) An alternative would be for Awesome Miner to look at the GPU's you have selected for this specific miner. You might have picked 6 nVidia GPUs from the list. The trigger would understand that by selecting exactly 6 GPUs from this list, it should look if the number of reported GPUs from the mining software are less than 6.

In this case you don't need to explicitly configure the number 6, as Awesome Miner can figure it out based on your GPU selection.

However, the default is to use all GPUs so option #2 isn't always possible.

3) A final alternative would be to combine #1 and #2, where you in the GPU selection dialog either select All GPUs and enter the minimum number of GPUs the trigger should expect - or you select specific GPUs and then there is no need to specify the number of GPUs the trigger should look for.


Final thoughts:
The benefit of specifying an explicit number is that it would work fine on CPU and ASIC miners as well. Not be specific for GPU mining. For this reason the most basic solution, #1, is probably the winner.

[NCarter84]

Anyone noticed the USD value of Raven mining daily is out of whack but the daily coins is in line?

IE: Showing I should get 45 coins, but showing daily value at $1.25/day.

I think these numbers looks fine, but please let me know if I misunderstood your point here.
What is being displayed in Awesome Miner is similar to what both WhatToMine and CoinCalculators.io are reporting. Right now the number of coins per day are a bit higher compared to when you wrote your message.

The COIN amount per day is where it should be, but the USD column is showing way higher than it should be. 45 Raven does not equal $1.20 USD a day, its about .90 cents a day.

[patrike]

Anyone noticed the USD value of Raven mining daily is out of whack but the daily coins is in line?

IE: Showing I should get 45 coins, but showing daily value at $1.25/day.

I think these numbers looks fine, but please let me know if I misunderstood your point here.
What is being displayed in Awesome Miner is similar to what both WhatToMine and CoinCalculators.io are reporting. Right now the number of coins per day are a bit higher compared to when you wrote your message.

The COIN amount per day is where it should be, but the USD column is showing way higher than it should be. 45 Raven does not equal $1.20 USD a day, its about .90 cents a day.

Thanks for the clarification. Looking at the Coins tab right now, I see the following for RavenCoin Kawpow at 24MH/s:
Coins per day: 45.88
Revenue per day: $0.93

The revenue $0.93 is also what both CoinCalculators and WhatToMine indicates on their web sites.

Is the Bitcoin price correct on your system? It will affect other calculations as well. It should be around $8800 now.

[NCarter84]

Anyone noticed the USD value of Raven mining daily is out of whack but the daily coins is in line?

IE: Showing I should get 45 coins, but showing daily value at $1.25/day.

I think these numbers looks fine, but please let me know if I misunderstood your point here.
What is being displayed in Awesome Miner is similar to what both WhatToMine and CoinCalculators.io are reporting. Right now the number of coins per day are a bit higher compared to when you wrote your message.

The COIN amount per day is where it should be, but the USD column is showing way higher than it should be. 45 Raven does not equal $1.20 USD a day, its about .90 cents a day.

Thanks for the clarification. Looking at the Coins tab right now, I see the following for RavenCoin Kawpow at 24MH/s:
Coins per day: 45.88
Revenue per day: $0.93

The revenue $0.93 is also what both CoinCalculators and WhatToMine indicates on their web sites.

Is the Bitcoin price correct on your system? It will affect other calculations as well. It should be around $8800 now.

Who knows... now its showing 90 cents haha... I'll keep an eye on it and keep digging and let you know if I find anything strange.

But, it showed 1.20 for a few days, if not since the update on the 21st.

[patrike]

Hello!

How do I make Awesome Miner detect that Claymore doesn't initialize?

I have a few nasty rigs that may sometimes not initialize properly and Claymore either throws "Miner cannot initialize for 5 minutes, need to restart miner!" error (and freezes) or just stops at GPU initialization.

I don't have enough time right now to deal with these rigs, so I just want AM to detect such behavior and restart the rig using "shutdown -f -r -t 0" because if such a thing happens, only a full reboot helps.

Which rule shall I create for this situation?

And a feature request: sometimes GPUs fall of the bus and are not detected. Right now I have to set up a rule per each farm that detects a number of devices and if it's not the same as specified in the rule, the notification is displayed.

But maybe it is possible to be able to set up a GPU count in the Properties of each rig? Because right now I need to create 50+ rules for each rig.

1) The built-in Offline Detection rule should be able to detect this. By default the rule only provides a notification, but you can modify it to also take an action like reboot. The action name is "Miner command" for this, where you will find Reboot as one of the optioins.

Do you see the notification message when Claymore miner ends up in this state?

2) Good point about specifying a GPU count on the miner. Thanks!

No, the deal is that this state doesn't trigger any notifications.

Just to confirm - in the Options dialog, Rules section, you have enabled (checked the check box) the predefined rule called "Offline Detection"? Even when enabled, you don't get any notification?

[NCarter84]

Hello!

How do I make Awesome Miner detect that Claymore doesn't initialize?

I have a few nasty rigs that may sometimes not initialize properly and Claymore either throws "Miner cannot initialize for 5 minutes, need to restart miner!" error (and freezes) or just stops at GPU initialization.

I don't have enough time right now to deal with these rigs, so I just want AM to detect such behavior and restart the rig using "shutdown -f -r -t 0" because if such a thing happens, only a full reboot helps.

Which rule shall I create for this situation?

And a feature request: sometimes GPUs fall of the bus and are not detected. Right now I have to set up a rule per each farm that detects a number of devices and if it's not the same as specified in the rule, the notification is displayed.

But maybe it is possible to be able to set up a GPU count in the Properties of each rig? Because right now I need to create 50+ rules for each rig.

1) The built-in Offline Detection rule should be able to detect this. By default the rule only provides a notification, but you can modify it to also take an action like reboot. The action name is "Miner command" for this, where you will find Reboot as one of the optioins.

Do you see the notification message when Claymore miner ends up in this state?

2) Good point about specifying a GPU count on the miner. Thanks!

No, the deal is that this state doesn't trigger any notifications.

Just to confirm - in the Options dialog, Rules section, you have enabled (checked the check box) the predefined rule called "Offline Detection"? Even when enabled, you don't get any notification?

The miner doesn't go offline. It stays online.
http://i.piccy.info/i9/081cf6b9fd441f660ec8dda024132959/1590617631/134093/1380548/fail.png

See the screen. It's not mine, but I get the same error: the miner just hangs on this screen and that's all.
So it is considered as "Online" and "Mining" in AM.

Which rule do I need to create to detect such a situation and execute a reboot?

Accepted shares doesn't increase after x mins?

[patrike]

Hello!

How do I make Awesome Miner detect that Claymore doesn't initialize?

I have a few nasty rigs that may sometimes not initialize properly and Claymore either throws "Miner cannot initialize for 5 minutes, need to restart miner!" error (and freezes) or just stops at GPU initialization.

I don't have enough time right now to deal with these rigs, so I just want AM to detect such behavior and restart the rig using "shutdown -f -r -t 0" because if such a thing happens, only a full reboot helps.

Which rule shall I create for this situation?

And a feature request: sometimes GPUs fall of the bus and are not detected. Right now I have to set up a rule per each farm that detects a number of devices and if it's not the same as specified in the rule, the notification is displayed.

But maybe it is possible to be able to set up a GPU count in the Properties of each rig? Because right now I need to create 50+ rules for each rig.

1) The built-in Offline Detection rule should be able to detect this. By default the rule only provides a notification, but you can modify it to also take an action like reboot. The action name is "Miner command" for this, where you will find Reboot as one of the optioins.

Do you see the notification message when Claymore miner ends up in this state?

2) Good point about specifying a GPU count on the miner. Thanks!

No, the deal is that this state doesn't trigger any notifications.

Just to confirm - in the Options dialog, Rules section, you have enabled (checked the check box) the predefined rule called "Offline Detection"? Even when enabled, you don't get any notification?

The miner doesn't go offline. It stays online.
http://i.piccy.info/i9/081cf6b9fd441f660ec8dda024132959/1590617631/134093/1380548/fail.png

See the screen. It's not mine, but I get the same error: the miner just hangs on this screen and that's all.
So it is considered as "Online" and "Mining" in AM.

Which rule do I need to create to detect such a situation and execute a reboot?

Thanks for the update. I understand the miner process is running, but as it isn't started mining correctly.

1) If the miner shows up as "Interface offline" and no hashrate in Awesome Miner:
The "Offline Detection" rule is still likely to be able to detect this problem. This is why I would like you to confirm that this rule is enabled (Options dialog, Rules section). Please also make sure you clear any notifications you have on the Notification tab, to make sure this rule actually are able to provide new notifications for any issues.

2) If the miner shows up with a hashrate in Awesome Miner, even if it's 0 H/s:
As @NCarter84 pointed out - this one can be found with the rule looking for number of accepted shares