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

[MoparMiningLLC]

patrike -

thanks! it does now show the hash rate and thus the estimated revenue/profit for the BW L21 now - the only other thing I notice is that the pool that shows is the pool #2 - it does not show what pool the miner is actually on. for example, if I put one pool in - it shows nothing. If I put two pools in, it shows the second one, even if the miner is mining on the first one.

[joseph32]

Hey Patrik,

I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.

- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.

Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:

- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.

I think because there is no miner API established because of the crash, even if the mining window is still open?

Hey Patrik,

just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM.

I think I know why this can happen:

- The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate).
- So there are 2 miners now and AM can't show the numbers for the T-Rex.

Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe).

Hi,
Thanks for sharing the details. I can see from the API Report the T-Rex doesn't return anything and the reason is likely that NBminer uses the API port already, preventing T-Rex from using this port.

Would it be possible for you to also send me the Remote Agent log file for the time where NBMiner was supposed to be closed? You should be able to see log messages like "Closing process" and maybe even "Killing process".

What Awesome Miner do when closing mining software is to first send a friendly request to close down. Awesome Miner will then wait for the process to terminate (a number of seconds, configurable in the Options dialog, Mining Settings section), and if the process is still running, Awesome Miner tells Windows to kill the process.

Hey Patrik,

sent you the log file by PM and some more thoughts about that problem.

[rampaige]

my antivirus keeps on blocking the miners...never had any problems with any miners except those downloaded by your program....

When using the automatic download feature in Awesome Miner, a zip-file will be downloaded from the official download location if still available. As a fallback, an identical copy of the original zip-file can be automatically downloaded from the Awesome Miner web site.

However, most anti-virus software warn about cgminer and similar mining software because they are being used by trojans and other malware. If you run into this problem, you can always manually download cgminer / sgminer and configure Awesome Miner to that use that downloaded instance instead.

Thanks for your great software. There is a feature that I think Awesomeminer lacks. Please consider adding “Auto Update" feature to Awesomeminer, like any other applications even with schedule. It is a pain in the neck if you have multiple rigs, and every week, you use a remote session to go and click on update manually with high pings and delays. It is so easy for you to add this feature.

[patrike]

patrike -

thanks! it does now show the hash rate and thus the estimated revenue/profit for the BW L21 now - the only other thing I notice is that the pool that shows is the pool #2 - it does not show what pool the miner is actually on. for example, if I put one pool in - it shows nothing. If I put two pools in, it shows the second one, even if the miner is mining on the first one.

I do understand your point here. The priority of the first pool has a higher number (crazy high as in 16842752) when reported from the ASIC miner, when it in fact should be priority 0. The second pool has priority 1. For this reason Awesome Miner will consider the second pool to be active.

This is another case where the BW L21 ASIC doesn't report correct information, but I will adjust Awesome Miner to consider very high priority numbers to be 0 instead. Priority 0 is the current active pool.

[patrike]

my antivirus keeps on blocking the miners...never had any problems with any miners except those downloaded by your program....

When using the automatic download feature in Awesome Miner, a zip-file will be downloaded from the official download location if still available. As a fallback, an identical copy of the original zip-file can be automatically downloaded from the Awesome Miner web site.

However, most anti-virus software warn about cgminer and similar mining software because they are being used by trojans and other malware. If you run into this problem, you can always manually download cgminer / sgminer and configure Awesome Miner to that use that downloaded instance instead.

Thanks for your great software. There is a feature that I think Awesomeminer lacks. Please consider adding “Auto Update" feature to Awesomeminer, like any other applications even with schedule. It is a pain in the neck if you have multiple rigs, and every week, you use a remote session to go and click on update manually with high pings and delays. It is so easy for you to add this feature.

Thanks for the suggestion.

The general idea is to have a single Awesome Miner installed on one computer, and then run Remote Agent on all other computers you do GPU mining on. Then you only need to have one Awesome Miner to upgrade, and upgrading each Remote Agent is only a matter of clicking the 'Upgrade Remote Agent' button in the toolbar.

[MoparMiningLLC]

patrike -

thanks! it does now show the hash rate and thus the estimated revenue/profit for the BW L21 now - the only other thing I notice is that the pool that shows is the pool #2 - it does not show what pool the miner is actually on. for example, if I put one pool in - it shows nothing. If I put two pools in, it shows the second one, even if the miner is mining on the first one.

I do understand your point here. The priority of the first pool has a higher number (crazy high as in 16842752) when reported from the ASIC miner, when it in fact should be priority 0. The second pool has priority 1. For this reason Awesome Miner will consider the second pool to be active.

This is another case where the BW L21 ASIC doesn't report correct information, but I will adjust Awesome Miner to consider very high priority numbers to be 0 instead. Priority 0 is the current active pool.

ahh understood - they kinda just did their firmware so different than everyone else's lol

[ar.miranian]

Hi guys

I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.

Can anybody help me how I can get the right piece of code to get fan speed or workername?

For more information, below is part of the AIP report generated by Awesome Miner.

Version: 5.2.2
API command: config
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1560348227,
      "Code": 33,
      "Msg": "CGMiner config",
      "Description": "cgminer 4.9.2"
    }
  ],
  "CONFIG": [
    {
      "ASC Count": 3,
      "PGA Count": 0,
      "Pool Count": 3,
      "Strategy": "Failover",
      "Log Interval": 5,
      "Device Code": "SM ",
      "OS": "Linux",
      "Hotplug": "None"
    }
  ],
  "id": 1
}
API command: summary
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1560348227,
      "Code": 11,
      "Msg": "Summary",
      "Description": "cgminer 4.9.2"
    }
  ],
  "SUMMARY": [
    {
      "Elapsed": 20447,
      "MHS av": 12482416.6,
      "MHS 5s": 11983833.6,
      "MHS 1m": 12435743.1,
      "MHS 5m": 12481650.52,
      "MHS 15m": 12612915.98,
      "Found Blocks": 0,
      "Getworks": 549,
      "Accepted": 1657,
      "Rejected": 0,
      "Hardware Errors": 30,
      "Utility": 4.86,
      "Discarded": 100843,
      "Stale": 0,
      "Get Failures": 0,
      "Local Work": 85905887,
      "Remote Failures": 0,
      "Network Blocks": 38,
      "Total MH": 255222926659.0,
      "Work Utility": 174377.42,
      "Difficulty Accepted": 56385536.0,
      "Difficulty Rejected": 0.0,
      "Difficulty Stale": 0.0,
      "Best Share": 35916773,
      "Temperature": 88.0,
      "freq_max": 672,
      "freq_min": 671,
      "freq_avg": 671,
      "Fan Speed In": 6270,
      "Fan Speed Out": 6270,
      "fan_stop_count": 0,
      "fan_stop_turnoff_threshold": 5,
      "fan_stop_turnoff_times": 0,
      "Fan set_get_err_turnoff_threshold": 15,
      "fan[0] set_get_err_turnoff_count": 0,
      "fan[1] set_get_err_turnoff_count": 0,
      "Voltage": 9,
      "Device Hardware%": 0.0001,
      "Device Rejected%": 0.0,
      "Pool Rejected%": 0.0,
      "Pool Stale%": 0.0,
      "Last getwork": 1560348227,
      "Uptime": 20880
    }
  ],
  "id": 1

[patrike]

Awesome Miner version 6.5.5

 ASIC mining
  - Adjust the reported pool priority for BW L21 ASIC
 GPU mining
  - Improved detection of environment variables for nVidia commands via Remote Agent on Linux
 Features
  - Added a way to detect duplicated IP addresses for External Miners in the Options dialog, External Miner section
 Mining Software
 - CcMiner KlausT 1.25
 Corrections
  - Correction to exact IP address match in the Find Miner dialog
  - NbMiner console correction for Remote Agent on Linux and disable watchdog
  - Correction to the console tab to correctly clear the display when selecting a miner without any console output

[MoparMiningLLC]

Awesome Miner version 6.5.5

 ASIC mining
  - Adjust the reported pool priority for BW L21 ASIC
 GPU mining
  - Improved detection of environment variables for nVidia commands via Remote Agent on Linux
 Features
  - Added a way to detect duplicated IP addresses for External Miners in the Options dialog, External Miner section
 Mining Software
 - CcMiner KlausT 1.25
 Corrections
  - Correction to exact IP address match in the Find Miner dialog
  - NbMiner console correction for Remote Agent on Linux and disable watchdog
  - Correction to the console tab to correctly clear the display when selecting a miner without any console output

thanks! will update and verify for the BW L21

***EDIT***

verified that it is now reporting the correct pool! thanks!

[patrike]

Hi guys

I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.

Can anybody help me how I can get the right piece of code to get fan speed or workername?

Hi,

I did see your recent e-mail on this topic as well. For Fan speed there are no solution for Whatsminer yet. I will have to investigate that a bit more before I have a solution.

For worker name you can use this expression:

Code:

"Worker: " + (miningHelper.GetMainPoolStatus() != null ? miningHelper.GetMainPoolStatus().User : "")

[ar.miranian]

Hi guys

I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.

Can anybody help me how I can get the right piece of code to get fan speed or workername?

Hi,

I did see your recent e-mail on this topic as well. For Fan speed there are no solution for Whatsminer yet. I will have to investigate that a bit more before I have a solution.

For worker name you can use this expression:

Code:

"Worker: " + (miningHelper.GetMainPoolStatus() != null ? miningHelper.GetMainPoolStatus().User : "")

Hi Partike

Thanks for your help.
I tried your code, but got the following error:

error CS1061: 'AwesomeMiner.Components.Intelligence.ProgressField.ProgressMiningHelper' does not contain a definition for 'GetMainPoolStatus' and no extension method 'GetMainPoolStatus' accepting first ...

I Would appreciate if you double check the code.

[trucobit]

I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.

Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.

Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example

X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00

With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.

In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.

[patrike]

Hi guys

I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.

Can anybody help me how I can get the right piece of code to get fan speed or workername?

Hi,

I did see your recent e-mail on this topic as well. For Fan speed there are no solution for Whatsminer yet. I will have to investigate that a bit more before I have a solution.

For worker name you can use this expression:

Code:

"Worker: " + (miningHelper.GetMainPoolStatus() != null ? miningHelper.GetMainPoolStatus().User : "")

Hi Partike

Thanks for your help.
I tried your code, but got the following error:

error CS1061: 'AwesomeMiner.Components.Intelligence.ProgressField.ProgressMiningHelper' does not contain a definition for 'GetMainPoolStatus' and no extension method 'GetMainPoolStatus' accepting first ...

I Would appreciate if you double check the code.

Hi,
I think you are running on a quite old version of Awesome Miner. Please upgrade and it should work fine.

[patrike]

I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.

Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.

Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example

X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00

With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.

In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.

Thanks for the suggestion, I see your point. This will add some complexity to the configuration, so it has to be some kind of advanced mode where you can specify additional conditions. As you point out it has to be per algorithm in the Profit Profile.

[trucobit]

I have commented that it should be optional, it should not be in view. It can be an option in each something that when clicked is displayed. Thank you for your attention.

[soothaa]

I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.

Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.

Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example

X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00

With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.

In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.

Thanks for the suggestion, I see your point. This will add some complexity to the configuration, so it has to be some kind of advanced mode where you can specify additional conditions. As you point out it has to be per algorithm in the Profit Profile.

Ditto to this, would be a nice thing right about now. Gets to about 32C in the day in Ohio but can drop in the low teens easy.

[patrike]

I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.

Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.

Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example

X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00

With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.

In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.

Thanks for the suggestion, I see your point. This will add some complexity to the configuration, so it has to be some kind of advanced mode where you can specify additional conditions. As you point out it has to be per algorithm in the Profit Profile.

Ditto to this, would be a nice thing right about now. Gets to about 32C in the day in Ohio but can drop in the low teens easy.

Thanks for the suggestions.

There is also another kind of flexibility that I would like to consider when looking into the clocking profiles. Today you can define a Clocking Profile per Profit Profile per Algorithm. But there should also be a per Miner concept in here. It's of course possible to create multiple Profit Profiles with the same settings but different Clocking Profiles - but that's not too user friendly. In addition to that - we also have the Time/Schedule concept both of you suggested.

[patrike]

Here is a preview of what's in the pipeline. Next week you will be able to define a global fan curve where Awesome Miner will monitor the temperature of each individual GPU and adjust the fan speed individually to match the curve. There will be 5 points that you can move in any direction.

This will work for both AMD and nVidia. If enabled, it will control the fan as long as Remote Agent (or Awesome Miner if you do local mining) is running.

When you enable this feature it will completely disable all other fan operations you do via Awesome Miner.

[Binary100100]

So this isn't at all related to AwesomeMiner but wanted to share it if nobody has read it yet:
https://thenextweb.com/hardfork/2019/06/11/nicehash-fbi-mariposa-cryptocurrency-dark-web-malware-mining/

It's basically regarding Nicehash founder Matjaz Skorjanc and his connection with Darkode which is known for selling malware, botnets and hacking services.
I'm not sure about you but I definitely don't want to run software on my machines that have any kind of connection with that. With AwesomeMiner you can still mine with Nicehash but without the risk of having your machines/computers compromised.
Nicehash has quickly released a statement defending the allegations by saying that it's not related to them.
https://www.nicehash.com/news/nicehash-statement-regarding-latest-allegations

Still I wouldn't feel safe with having their software on my network.
@Patrike this is a great marketing opportunity for you sir! I'm attempting to sign up for the affiliate program but it says my application is under review.
I've been a solid supporter of your program for several months now. Your prompt responses to inquiries, troubleshooting and open-mindedness for ideas/suggestions is excellent and I actually enjoy promoting your work on social media platforms. Thanks again for your dedication and all of your hard work.

[patrike]

So this isn't at all related to AwesomeMiner but wanted to share it if nobody has read it yet:
https://thenextweb.com/hardfork/2019/06/11/nicehash-fbi-mariposa-cryptocurrency-dark-web-malware-mining/

It's basically regarding Nicehash founder Matjaz Skorjanc and his connection with Darkode which is known for selling malware, botnets and hacking services.
I'm not sure about you but I definitely don't want to run software on my machines that have any kind of connection with that. With AwesomeMiner you can still mine with Nicehash but without the risk of having your machines/computers compromised.
Nicehash has quickly released a statement defending the allegations by saying that it's not related to them.
https://www.nicehash.com/news/nicehash-statement-regarding-latest-allegations

Still I wouldn't feel safe with having their software on my network.
@Patrike this is a great marketing opportunity for you sir! I'm attempting to sign up for the affiliate program but it says my application is under review.
I've been a solid supporter of your program for several months now. Your prompt responses to inquiries, troubleshooting and open-mindedness for ideas/suggestions is excellent and I actually enjoy promoting your work on social media platforms. Thanks again for your dedication and all of your hard work.

Thanks for sharing the information. It's good with information from both sides so everyone can form their own opinion.

Your application has been approved now! It's a manual approve process.

I appreciate your very nice feedback and also would like to say thanks for promoting the software and for being a part of this mining community.