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

[patrike]

Version 6.7.3 ( Development preview of 6.8 )

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware
 GPU mining
  - GPU power limit control based on temperature, configurable in the Options dialog, GPU Settings section (Beta preview features)
 Features
  - Miner highlight feature includes 5 additional colors
  - Configurable if a double click on an External Miner should open the ASIC miner web interface. Configurable via the Options dialog, General section.
 User interface
  - Antminer&ASIC menu renamed to ASIC tools
  - Temperature sorting improved for miner list in compact mode
 Mining software
  - Bminer 15.7.6
  - CcMiner Zcoin Official 1.1.26
  - Z-enemy miner 2.1

-Thanks Patrike for more highlight colors. Can you change this feature that we can set our own description per color? Example i will set red = offline, yellow = temperature over 80°c. At the moment the names are Information 1, Information 2 and so on. I hope you understand my question 

-Other stuff what i expect are groups for balance section. Because i use awesomeminer with a friend and so we can make our own groups or we can make several groups for exchange, wallet and so on.

-Dual Mining Support for Phönixminer must be also possible, it is not very different from claymore.

-And CPU only mode for Nanominer, at the moment i can´t mine only with CPU because Awesomeminer say it is for nvidia and amd not for cpu.

Thanks for all suggestions.

Although Awesome Miner indicate Nanominer to be AMD and nVidia, isn't it still working to mine RandomHash with CPU only?

[patrike]

Testing Beta feature "Enable GPU global power limit":

setting Default power limit 80%, overrides the GPU clocking profile when starting, so all GPU clocking now starts at 80%.

Then try Disable Global power limit and the GPU start profile works again.

I would like to have option to set Default power limit for the normal GPU clocking profile when starting since the my RTX 2060
always starts at 100% no matter what.

The new power limit control is a feature is on a global level, so setting the default power to 80%, it will be 80% all the time unless your temperature condition indicates something else.

When you define your Clocking Profile, Power Limit is one of the properties. If you set this one to 90%, isn't that applied for your RTX 2060 GPU?

[patrike]

Version 6.7.3 ( Development preview of 6.8 )

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware

Way cool dude! I don't own any, but awesome to see your rolling your own firmware like that!

Thanks!

I can however not take credit for the firmware - I'm not the developer of it. It's developed by vnish that is behind many different brands of Antminer firmware. Awesome Miner Antminer S9 firmware is just another brand name for it.

I have however been working close with vnish for some time now to make sure we get a good integration in Awesome Miner. Already with this release there are a number of features integrated, for example the mining profiles to get better control of the hashrate and power levels. Both by manually making the changes but also to allow the rules in Awesome Miner to control it.

The plan is of course to continue improving the integration with more features.

[patrike]

Own Antminer Software is very cool, but in my opinion it must be without dev fee for the higher Awesomeminer Editions. We have now a 40 Miner License and we want to upgrade to the next step (100 Miners). This is a very big step and it cost so much that i believe it is better to release a Firmware without devfee for the Awesomeminer Editions with 100 and more miners.

Was thinking the same, well maybe not without but from 2% to lower it to standard 0.85% like Phoenix

Thanks for the feedback. The firmware mining fee will be 2% and this will not change. I'm not in charge of this part of the firmware and the business model for the firmware. (A small note on the fee is that it's at most 2%, the average is a bit lower)

Please also note that most custom Antminer firmware out there have the same mining fee, and there are already a number of Awesome Miner users that are running those solutions. With this release you will get much better integration with Awesome Miner at the same fee as these kind of firmwares already have.

This firmware gives a new alternative for those running Antminers and I think many users will consider it to be well worth the fee because of the increased hashrate for a given power level. Awesome Miner will of course continue to support the Bitmain firmware, BraiinsOS firmware and so on for users that doesn't want to have a mining fee.

[slysir]

Testing Beta feature "Enable GPU global power limit":

setting Default power limit 80%, overrides the GPU clocking profile when starting, so all GPU clocking now starts at 80%.

Then try Disable Global power limit and the GPU start profile works again.

I would like to have option to set Default power limit for the normal GPU clocking profile when starting since the my RTX 2060
always starts at 100% no matter what.

The new power limit control is a feature is on a global level, so setting the default power to 80%, it will be 80% all the time unless your temperature condition indicates something else.

When you define your Clocking Profile, Power Limit is one of the properties. If you set this one to 90%, isn't that applied for your RTX 2060 GPU?

Yes my Clocking Profile Power Limit normally gets set, but if the Power Limit does not get applied like in the case of my RTX 2060, Then the _Default_ Power Limit value of 100%  is applied.

 This setting  would need to be Added to the Clocking Profile Properties in Edit - Clocking Profiles :
Property - Default Power Limit (%) ....not the Power Limit (%)
Value - (%)

This acts as a fail safe value (like the Global power limit but only for my RTX 2060 profile)  in case the Clocking Profile fails.



 

[Marvell2]

When will you be adding random xl for Loki

[patrike]

Testing Beta feature "Enable GPU global power limit":

setting Default power limit 80%, overrides the GPU clocking profile when starting, so all GPU clocking now starts at 80%.

Then try Disable Global power limit and the GPU start profile works again.

I would like to have option to set Default power limit for the normal GPU clocking profile when starting since the my RTX 2060
always starts at 100% no matter what.

The new power limit control is a feature is on a global level, so setting the default power to 80%, it will be 80% all the time unless your temperature condition indicates something else.

When you define your Clocking Profile, Power Limit is one of the properties. If you set this one to 90%, isn't that applied for your RTX 2060 GPU?

Yes my Clocking Profile Power Limit normally gets set, but if the Power Limit does not get applied like in the case of my RTX 2060, Then the _Default_ Power Limit value of 100%  is applied.

 This setting  would need to be Added to the Clocking Profile Properties in Edit - Clocking Profiles :
Property - Default Power Limit (%) ....not the Power Limit (%)
Value - (%)

This acts as a fail safe value (like the Global power limit but only for my RTX 2060 profile)  in case the Clocking Profile fails.

Thanks for the update. So this specific RTX2060 is not applying the Power Limit property correctly - but it works for all other GPUs? Is it working if you manually apply it via the clocking dialog? Is it never applied correctly when being part of a Clocking Profile?

Based on your description it sounds like the new Power Limit control feature was able to set the Power Limit correctly for this GPU - but this feature is setting the same Power Limit property as when you manually apply it or set it via a Clocking Profile.

The Power Limit control feature is intended to dynamically adjust the Power Limit based on GPU temperature and it's not at all related to the clocking profiles.

[patrike]

When will you be adding random xl for Loki

Is it a fork and change of algorithm for this coin?
https://www.coincalculators.io/coin/loki

It looks like XmRig will support this one. I will look into it.

Update: It's supported by XmRig 2.99 but this one introduces command line and API changes as well. For this reason I cannot push the update yet - but I will add support for it within the next few days.

[patrike]

Awesome Miner version 6.7.4 ( Development preview of 6.8 )

 ASIC mining
  - Antminer S15/T15 power mode configuration
 Features
  - Keystrokes can be sent to mining software via the rule actons. Configurable via the Miner Command action.
 Mining software
  - CpuMiner-Opt 3.9.6.2
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer integration updated for RandomHash algorithm

[Globalboosty]

Which nheqminer version is using by the mining community these days? This one looks very outdated:
https://github.com/nicehash/nheqminer/releases

nheqminer-Windows-v0.7.2

[Globalboosty]

When you added the nheqminer, did you add it via the Options dialog, Managed Software section, and configured it with Command Line as compatibility mode? In that case Awesome Miner shouldn't try the API and should understand that it cannot get hashrate/share information.

Yes, I added nheqminer in compatibility mode (EWBF CUDA Zcash Miner) and added additional command line arguments in profit profile properties:
-v -l mine.zergpool.com:3300 -u BTCaddress -t 7 -a 4029 -p c=BTC,ID=NAME

[GKumaran]

Awesome Miner version 6.7.4 ( Development preview of 6.8 )

 ASIC mining
  - Antminer S15/T15 power mode configuration
 Features
  - Keystrokes can be sent to mining software via the rule actons. Configurable via the Miner Command action.
 Mining software
  - CpuMiner-Opt 3.9.6.2
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer integration updated for RandomHash algorithm

Can the keystrokes be sent without rules ? like from a menu in the console tab?

[Marvell2]

When will you be adding random xl for Loki

Is it a fork and change of algorithm for this coin?
https://www.coincalculators.io/coin/loki

It looks like XmRig will support this one. I will look into it.

Update: It's supported by XmRig 2.99 but this one introduces command line and API changes as well. For this reason I cannot push the update yet - but I will add support for it within the next few days.

awseomse @patrike thanks , this is important because in October XMR is forking to the same algo

[trucobit]

I have a Patrike doubt about the new power temperature system. The first thing I've noticed is that I get more hash. I use both power and core systems. I have the power one at 75 and the Core one at 76 degrees.

Using both systems, power should have more priority than Core.

In the interface I do not define a default power because if not all rigs would start with the same power, but then I see that you have to specify a minimum Power, right now in my case it is 70%.

My question is, I have a rig running at 85 power, when it reaches the target temperature that occurs.

1.- The power falls directly from 85 to 70 (I don't see it right)

2.- When you approach the target temperature, the power is gradually reduced, suppose the case of 5 in 5, which would be 85 is as it was, 80, 75 and finally 70.

The option that I commented is the two, because to make a fall from 85 to 70 it happens that the rig reaches 77 and suddenly falls to 72 degrees, then rises again to 75-77, then falls again.

I should have hysteresis. I don't know if that word exists in English. It is that the system acts a couple of degrees before dropping 5 a degree before the target, wait 30 seconds to see if temperature falls, if not, again lower it 5 degrees, etc. If after reaching the minimum defined by me, in this case 70, and if I have temperature activated also by the core, then at that time the core fall would be activated. OSea first give priority to see if the power drop produces the desired effect, and if you do not get it with my minimum, then pay attention to the Core drop, if defined in the OC.
It's a good job anyway, but I think it lacks this little detail that I tell you.

[trucobit]

Testing Beta feature "Enable GPU global power limit":

setting Default power limit 80%, overrides the GPU clocking profile when starting, so all GPU clocking now starts at 80%.

Then try Disable Global power limit and the GPU start profile works again.

I would like to have option to set Default power limit for the normal GPU clocking profile when starting since the my RTX 2060
always starts at 100% no matter what.

The new power limit control is a feature is on a global level, so setting the default power to 80%, it will be 80% all the time unless your temperature condition indicates something else.

When you define your Clocking Profile, Power Limit is one of the properties. If you set this one to 90%, isn't that applied for your RTX 2060 GPU?

Yes my Clocking Profile Power Limit normally gets set, but if the Power Limit does not get applied like in the case of my RTX 2060, Then the _Default_ Power Limit value of 100%  is applied.

 This setting  would need to be Added to the Clocking Profile Properties in Edit - Clocking Profiles :
Property - Default Power Limit (%) ....not the Power Limit (%)
Value - (%)

This acts as a fail safe value (like the Global power limit but only for my RTX 2060 profile)  in case the Clocking Profile fails.

Thanks for the update. So this specific RTX2060 is not applying the Power Limit property correctly - but it works for all other GPUs? Is it working if you manually apply it via the clocking dialog? Is it never applied correctly when being part of a Clocking Profile?

Based on your description it sounds like the new Power Limit control feature was able to set the Power Limit correctly for this GPU - but this feature is setting the same Power Limit property as when you manually apply it or set it via a Clocking Profile.

The Power Limit control feature is intended to dynamically adjust the Power Limit based on GPU temperature and it's not at all related to the clocking profiles.

I am 2080 and it works well for me, what is strange to me is that I do not see the power changes in GPU clocking while mine.

What should not be done is to establish a general Power for all rigs from the option there is, I have it unchecked and I use a custom OC, with its Power, core, and mem. But if I set the lowest limit where the power can fall, in my case up to 70%

Either I haven't noticed or it doesn't happen to me. but now I get more hash than just dropping the core. Although I use both systems, power at 75 degrees and Core at 76 or 77 as a second barrier because of something, and then another rule in case it reaches 82 to stop the miner.

[soothaa]

So after using this software for so many years you'd think I'd know the answer to this.. is there a way to unset a miner highlight after a rule/error is cleared?

For example, if miner does not increase accept progress in 8 minutes it is highlighted yellow. If that then ends up increasing, the miner is rebooted, or the notification is cleared, I would want that highlight to be cleared.
BUT
I don't want a blanket rule to clear all highlights.. because other highlights might still apply.. I only want to unset the yellow highlight if the accept increases.. does this make sense? Is this possible?

[patrike]

When you added the nheqminer, did you add it via the Options dialog, Managed Software section, and configured it with Command Line as compatibility mode? In that case Awesome Miner shouldn't try the API and should understand that it cannot get hashrate/share information.

Yes, I added nheqminer in compatibility mode (EWBF CUDA Zcash Miner) and added additional command line arguments in profit profile properties:
-v -l mine.zergpool.com:3300 -u BTCaddress -t 7 -a 4029 -p c=BTC,ID=NAME

Thanks for the details. The Compatibility Mode provides several options. Have you tried using "None"?

[patrike]

Awesome Miner version 6.7.4 ( Development preview of 6.8 )

 ASIC mining
  - Antminer S15/T15 power mode configuration
 Features
  - Keystrokes can be sent to mining software via the rule actons. Configurable via the Miner Command action.
 Mining software
  - CpuMiner-Opt 3.9.6.2
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer integration updated for RandomHash algorithm

Can the keystrokes be sent without rules ? like from a menu in the console tab?

I will add it to the Console tab in the next release.

[patrike]

I have a Patrike doubt about the new power temperature system. The first thing I've noticed is that I get more hash. I use both power and core systems. I have the power one at 75 and the Core one at 76 degrees.

Using both systems, power should have more priority than Core.

In the interface I do not define a default power because if not all rigs would start with the same power, but then I see that you have to specify a minimum Power, right now in my case it is 70%.

My question is, I have a rig running at 85 power, when it reaches the target temperature that occurs.

1.- The power falls directly from 85 to 70 (I don't see it right)

2.- When you approach the target temperature, the power is gradually reduced, suppose the case of 5 in 5, which would be 85 is as it was, 80, 75 and finally 70.

The option that I commented is the two, because to make a fall from 85 to 70 it happens that the rig reaches 77 and suddenly falls to 72 degrees, then rises again to 75-77, then falls again.

I should have hysteresis. I don't know if that word exists in English. It is that the system acts a couple of degrees before dropping 5 a degree before the target, wait 30 seconds to see if temperature falls, if not, again lower it 5 degrees, etc. If after reaching the minimum defined by me, in this case 70, and if I have temperature activated also by the core, then at that time the core fall would be activated. OSea first give priority to see if the power drop produces the desired effect, and if you do not get it with my minimum, then pay attention to the Core drop, if defined in the OC.
It's a good job anyway, but I think it lacks this little detail that I tell you.

Thanks for testing out the new feature. It's a bit basic at the moment, but the idea was to give you something to try with to see if the concept is working. I didn't want to implement something too complex in case the entire concept of Power Limit control wasn't found useful.

I fully understand your point about not making too frequent changes and not too large changes. Having multiple multiple temperature targets would also be an improvement. I will look into making some improvement here. Thanks for the feedback!

[patrike]

So after using this software for so many years you'd think I'd know the answer to this.. is there a way to unset a miner highlight after a rule/error is cleared?

For example, if miner does not increase accept progress in 8 minutes it is highlighted yellow. If that then ends up increasing, the miner is rebooted, or the notification is cleared, I would want that highlight to be cleared.
BUT
I don't want a blanket rule to clear all highlights.. because other highlights might still apply.. I only want to unset the yellow highlight if the accept increases.. does this make sense? Is this possible?

I fully understand your question and what you are looking for.

There are unfortunately no perfect solution to this, but what you could try out is to add a trigger called "Detect miner API connection established" and then use an action to set the Highlight back to "None". It's not a complete solution for what you are asking for, but if the miner is rebooted and then started again, this rule could at least remove the highlight once the miner is up and running again.