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

[sxemini]

hi and big thx for fixing Z11 custom FW stats display

another request from my side ist: in rules section...can you add ALL "asic tools" commands and menu incl. all the legacy stuff?

Thanks for the nice feedback

There shouldn't be any need of using the Legacy operations. Can you please let me know which operation you would like to use and I can help out how to do it without using the Legacy features?

for example the reboot via web - maybe it works with the checkbox at the miner itself "Performe reboot and pool operations via web instead of SSH"?! cant test yet...but would be much easier if i can choose the actions in the rules section 1:1 like i do when i´m right click on the miner

Like you pointed out, the idea is to configure "Perform reboot and pool operations via web..." here. Then you simply perform the Miner Command action in your rule, where you select Reboot. In the miner list you can also use the normal Reboot button, either via the toolbar or right-click menu.

The benefit of using this concept, instead of Legacy, is that the Reboot operation will either use Web or SSH based on how your miner is configured. So there is no need to design separate rules for the miners that requires Web based reboot compared to those that must use SSH reboot.

i tried today...set a rule with actions "SSH Command" - User and Pass root:root and "Reboot System" ----- wont work. also with "Custom" and entering "reboot" in the box below will not reboot the machine. The trigger was set to "hashrate lower than 1kh" and i also tried to manual trigger the rule...

not SSH command, use Miner Command.
Try rightclick on your ASIC and try the normal reboot button. If this won´t work you have something configurated wrong or locked custom firmware -> i had this in the past with some of my miners.

Did you tried to connect to your asic via SSH? Do you get access?

[1714044656]

1714044656

[patrike]

Awesome Miner version 8.6

 ASIC mining
  - Improved detection of ASIC miner type
 GPU mining
  - Display of GPU memory temperature for AMD is supported on Windows as well (Linux already supported)
 Features
  - Miner Property trigger includes several new properties to detect
  - Web: Compact miner list mode configurable via the Preferences page
  - Web: Double click on a group in the miner list to expand
 Changes
  - Optimizations to requests made by the web interface
  - Removed pool no longer active: Ahashpool
  - Removed the concept of displaying Max values for GPU properties in the System tab
  - Mining history export filenames will by default include current date and time
 Mining software
  - Gminer 2.60
  - T-Rex Miner 0.21.3
  - XmRig 6.13
  - Nanominer 3.3.7
  - Miniz 1.8y3
  - Lolminer 1.31, incl. display of HW errors in Awesome Miner
 Corrections
  - Correction to display of hotspot and memory temperature for supported GPUs
  - Correction to multiple miner selection when the miner list is filtered
  - Correction to Miniz Miner pool connection URL format
  - Correction to IP address sorting of miner list
  - Correction to Pool Balance display
  - Correction to ideal hashrate calculations for Profit Groups

[nordmann666]

hi and big thx for fixing Z11 custom FW stats display

another request from my side ist: in rules section...can you add ALL "asic tools" commands and menu incl. all the legacy stuff?

Thanks for the nice feedback

There shouldn't be any need of using the Legacy operations. Can you please let me know which operation you would like to use and I can help out how to do it without using the Legacy features?

for example the reboot via web - maybe it works with the checkbox at the miner itself "Performe reboot and pool operations via web instead of SSH"?! cant test yet...but would be much easier if i can choose the actions in the rules section 1:1 like i do when i´m right click on the miner

Like you pointed out, the idea is to configure "Perform reboot and pool operations via web..." here. Then you simply perform the Miner Command action in your rule, where you select Reboot. In the miner list you can also use the normal Reboot button, either via the toolbar or right-click menu.

The benefit of using this concept, instead of Legacy, is that the Reboot operation will either use Web or SSH based on how your miner is configured. So there is no need to design separate rules for the miners that requires Web based reboot compared to those that must use SSH reboot.

i tried today...set a rule with actions "SSH Command" - User and Pass root:root and "Reboot System" ----- wont work. also with "Custom" and entering "reboot" in the box below will not reboot the machine. The trigger was set to "hashrate lower than 1kh" and i also tried to manual trigger the rule...

not SSH command, use Miner Command.
Try rightclick on your ASIC and try the normal reboot button. If this won´t work you have something configurated wrong or locked custom firmware -> i had this in the past with some of my miners.

Did you tried to connect to your asic via SSH? Do you get access?

allright...miner command works. thx

[Grumo]

Awesome Miner version 8.6

 ASIC mining
  - Improved detection of ASIC miner type
 GPU mining
  - Display of GPU memory temperature for AMD is supported on Windows as well (Linux already supported)
 Features
  - Miner Property trigger includes several new properties to detect
  - Web: Compact miner list mode configurable via the Preferences page
  - Web: Double click on a group in the miner list to expand
 Changes
  - Optimizations to requests made by the web interface
  - Removed pool no longer active: Ahashpool
  - Removed the concept of displaying Max values for GPU properties in the System tab
  - Mining history export filenames will by default include current date and time
 Mining software
  - Gminer 2.60
  - T-Rex Miner 0.21.3
  - XmRig 6.13
  - Nanominer 3.3.7
  - Miniz 1.8y3
  - Lolminer 1.31, incl. display of HW errors in Awesome Miner
 Corrections
  - Correction to display of hotspot and memory temperature for supported GPUs
  - Correction to multiple miner selection when the miner list is filtered
  - Correction to Miniz Miner pool connection URL format
  - Correction to IP address sorting of miner list
  - Correction to Pool Balance display
  - Correction to ideal hashrate calculations for Profit Groups

with last update my blackminers f1 cannot connect anymore .

[patrike]

with last update my blackminers f1 cannot connect anymore .

Are the miners showing up as Disconnected or as Mining, but without any details? Have you tried to reboot the miner once to ensure it isn't a miner problem?

If you still experience this issue, please send me the API report for this miner via the toolbar Tools -> API Report. Thanks!

[Grumo]

with last update my blackminers f1 cannot connect anymore .

Are the miners showing up as Disconnected or as Mining, but without any details? Have you tried to reboot the miner once to ensure it isn't a miner problem?

If you still experience this issue, please send me the API report for this miner via the toolbar Tools -> API Report. Thanks!

disconnected

[Commie]

Is it possible to set up a downvolt curve in AM, instead of using power limit?

[patrike]

Is it possible to set up a downvolt curve in AM, instead of using power limit?

Hi,
This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?

[Commie]

Is it possible to set up a downvolt curve in AM, instead of using power limit?

Hi,
This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?

Yes, that's it. Would be a very useful feature.

PS Any progress updates on Nvidia mem temperatures, at least in Windows?

[Commie]

Also, while trying to upgrade to 8.6 I receive the message like "the installation package is on the network drive which is unavailable" and process terminates. Starting the installation package instead of upgrading from within the software gives the same result. How can I fix this? Everything is on the local drive, of course.

[patrike]

Also, while trying to upgrade to 8.6 I receive the message like "the installation package is on the network drive which is unavailable" and process terminates. Starting the installation package instead of upgrading from within the software gives the same result. How can I fix this? Everything is on the local drive, of course.

I think this is the uninstall part of the upgrade. The Awesome Miner installer is based on the Windows Installer concept, where the uninstallation requires Windows to keep track of the installed software. In case Windows is unable to perform an upgrade or uninstallation, please use this tool from Microsoft to force the removal.
https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

After removing, run the installer again. All settings will be kept even if you uninstall.

[patrike]

Is it possible to set up a downvolt curve in AM, instead of using power limit?

Hi,
This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?

Yes, that's it. Would be a very useful feature.

PS Any progress updates on Nvidia mem temperatures, at least in Windows?

nVidia has communicated that they are working on a way to officially make the memory temperatures available. As soon this is available, it will be integrated in Awesome Miner as well.

[sxemini]

Is it possible to set up a downvolt curve in AM, instead of using power limit?

Hi,
This is unfortunately not supported. I assume you are asking for the kind of Voltage/Frequency curve you can define in MSI Afterburner?

Yes, that's it. Would be a very useful feature.

PS Any progress updates on Nvidia mem temperatures, at least in Windows?

Why downvolt curve? You can set fixed voltages -> makes more sense 

[Commie]

Why downvolt curve? You can set fixed voltages -> makes more sense 

Old habit, I guess, setting voltages along with freq.

[narousberg]

Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.

[patrike]

Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.

Hello,
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.

[narousberg]

Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.

Hello,
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.

thanks for idea, looks like this work now for normal rig. But this trigger combination not work if physical rig contains two or more virtual miners. In my scenario i have such rig. If one virtual rig perform switching, this action activate trigger and whole rig will be rebooted. How to solve this?

[immolated]

Thank you for updating L3+ Awesome miner firmware to 3.8.8, the fan fix was very important.

Is there a firmware 3.8.8 changelog? I don't see it anywhere.

[narousberg]

Hi Patrike, if i try to download a custom version of MiniZ miner for Linux, the system create wrong file (?smd_process_download=1&download_id=4427_1) instead of normal .gz archive.
Reagards

[patrike]

Hi Patrike, can you please improve a trigger (Device property -> Core clock)
The reaction of this triger is to quick. I try to catch errors of GPU by reading a core clock property, if equals 0 then i do rig reboot. But after starting new mining process not all cards is initialized and triger will be activaed. This offten happens with NBMiner. Maybe some delay can be implemented in this triger? Adjusting Options->Advance->Ignore rules on startups not help for this triger.
Regards.

Hello,
Can you please try to combine it with the trigger "Mining uptime"? This trigger can be used to ensure the mining software has been running for a few minutes. You can have these two triggers (Device Property + Mining uptime) and "Match all" configured in your rule.

thanks for idea, looks like this work now for normal rig. But this trigger combination not work if physical rig contains two or more virtual miners. In my scenario i have such rig. If one virtual rig perform switching, this action activate trigger and whole rig will be rebooted. How to solve this?

Thanks for the update.
So you have one Managed Miner and one Managed Profit Miner? In case of GPU issues, a reboot will affect both miners. Isn't a reboot what you want in case of GPU issues or what is the behavior you would like to see here?