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

[patrike]

More examples for setting up Rules

I've been updating the documentation about rules recently, where I have added several examples of what the rules can do and how to configure it. This can serve as good inspiration of what Awesome Miner can be used for. See:
http://www.awesomeminer.com/help/rules.aspx

i was trying to edit the pool prioritys and didnt find a way i guess i have to add rules to switch to another pool if main pool is down?
i just added 2 pools in a pool group but the miner didnt switch.

how can we help get the ebang ebit e9 and e9+ support done?

Most mining software should automatically switching to the next pool if the main pool is down. This is the responsibility of the mining software and the reason why a list of pools can be provided. Which software was it that didn't do failover correctly?

I've not received any reports about ebang ebit yet. As soon as I get an API report (Toolbar: Tools -> API Report), I can look into if any adjustments are required in Awesome Miner to support this ASIC.

[Laamohaa]

Hi , i have added My miner ( Whatsminer M2  9.3th ) to your application . but the problem the miner reboot automatically after few minutes and doesn't reach The Max Hash speed 9.3Th , it only reach 3 to 4Th and then shut down and reboot after few minutes .

and the miner show 83 C temperature

What's The problem

[Lowernlower]

Thanks for the super quick response. I've done this and what happens and the way I understand this rule is it checks every 30 seconds and if in that time frame the hashrate is less than 200 for even 1 second it triggers. I have tried a few variations of this. I don't think this rule necessarily means "if the hashrate is less than 200 FOR 30 seconds". Rather, it means if in this 30 seconds the hashrate ever drops below 200 which isn't exactly the same.

Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.

Do I need a comma? Or a decimal or something odd like that?

Thanks for your help.

https://s26.postimg.org/cc0dg2389/200.jpg

Hi,
In the screenshot, it's still only one Check statistics trigger. I've updated the instructions on the web site for the example how to configure this with multiple check statistics trigger. See "Example: Show notification on low hashrate" which is similar to what you want:
http://www.awesomeminer.com/help/rules.aspx

The triggers are checked about every 5 seconds. With only a time trigger included, and not a second trigger for Check statistics, you are basically changing this to checking once per 30 seconds. However, even here you can hit a low hashrate when it's checked, so as you stated above it's not a check for that it must be lower than 200 for 30 seconds.

Thanks a lot for getting back to me Patrike,

That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.


https://postimg.org/image/xns7ji6tn/

https://postimg.org/image/pjoos6hej/


I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.

Thanks again for the help!

[Kronny]

Hi Patrike, i have a noob question.
i'm trying the free edition with 2 miner, it's possible have 1 temporary code (1 week for example) to try enterprise features?

[insaniak]

I'm tuning into an issue and it keeps just shutting down it will run for awhile but then shut down my rig. Same settings as I had previously and it worked. I havnt changed anything on the rig or awesome miner. Not sure what's going on this is for etherium

[tf2addict]

I see a lot of fluctuation in the profit calculation for Zcash.  I'm running a GTX 1060 and 1070 and the profit per day will swing from a lot $2.17 or so to sometimes over $3, and then back down again within a period of an hour or several hours and my hash rate is steady.  I don't see how any of the factors that account for the profit calculation could be changing that much.  And the Flypool per day estimate is pretty steady.

As an example, at the present moment A.M. is telling me per day is $2.18 while WhatToMine says $2.57 and Flypool says $2.70 (though Flypool's hash rate is a bit high).  So A.M. is low by about 20%.

Any idea why such wild swings?

[bonosurgut]

after upgrade to 4 version, a lot of times i see mining interface offline, or disconnected, but mining process running well on the farm. Restart agent and restart awesome miner helps sometimes, sometimes not, need to stop miner and start again

[AtraxPool]

Why is the awesome miner website not in https?

[Turok2000]

Please tell me how to configure Ethereum Dual mining in Profit Switching. That only I did not try anything ((

[patrike]

Hi , i have added My miner ( Whatsminer M2  9.3th ) to your application . but the problem the miner reboot automatically after few minutes and doesn't reach The Max Hash speed 9.3Th , it only reach 3 to 4Th and then shut down and reboot after few minutes .

and the miner show 83 C temperature

What's The problem

I'm not really familiar with this kind of miner. But what you are saying is that when Awesome Miner monitor it, it gives less than half the hashrate and reboots? If you don't monitor it - it works great? Never heard of an ASIC behaving like that before. Can you please share more details?

[patrike]

Thanks for the super quick response. I've done this and what happens and the way I understand this rule is it checks every 30 seconds and if in that time frame the hashrate is less than 200 for even 1 second it triggers. I have tried a few variations of this. I don't think this rule necessarily means "if the hashrate is less than 200 FOR 30 seconds". Rather, it means if in this 30 seconds the hashrate ever drops below 200 which isn't exactly the same.

Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.

Do I need a comma? Or a decimal or something odd like that?

Thanks for your help.

Hi,
In the screenshot, it's still only one Check statistics trigger. I've updated the instructions on the web site for the example how to configure this with multiple check statistics trigger. See "Example: Show notification on low hashrate" which is similar to what you want:
http://www.awesomeminer.com/help/rules.aspx

The triggers are checked about every 5 seconds. With only a time trigger included, and not a second trigger for Check statistics, you are basically changing this to checking once per 30 seconds. However, even here you can hit a low hashrate when it's checked, so as you stated above it's not a check for that it must be lower than 200 for 30 seconds.

Thanks a lot for getting back to me Patrike,

That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.


https://postimg.org/image/xns7ji6tn/

https://postimg.org/image/pjoos6hej/


I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.

Thanks again for the help!

I guess it's possible to have a dip both "now" and "3 minutes ago". Can you try to add a third trigger as well, where you also check for example "5 minutes ago"? Just to test the scenario.

[patrike]

Hi Patrike, i have a noob question.
i'm trying the free edition with 2 miner, it's possible have 1 temporary code (1 week for example) to try enterprise features?

Sure, just contact me by e-mail (info at awesomeminer.com)

[patrike]

I'm tuning into an issue and it keeps just shutting down it will run for awhile but then shut down my rig. Same settings as I had previously and it worked. I havnt changed anything on the rig or awesome miner. Not sure what's going on this is for etherium

Can you describe in more detail what "shut down" is here? Is the entire computer crashing and restarts? Is this only for Ethereum mining? Do you have this problem on a single computer or many?

In general, these kind of issues are not related to Awesome Miner itself, but to the GPU's, drivers, the mining software and so on.

[patrike]

I see a lot of fluctuation in the profit calculation for Zcash.  I'm running a GTX 1060 and 1070 and the profit per day will swing from a lot $2.17 or so to sometimes over $3, and then back down again within a period of an hour or several hours and my hash rate is steady.  I don't see how any of the factors that account for the profit calculation could be changing that much.  And the Flypool per day estimate is pretty steady.

As an example, at the present moment A.M. is telling me per day is $2.18 while WhatToMine says $2.57 and Flypool says $2.70 (though Flypool's hash rate is a bit high).  So A.M. is low by about 20%.

Any idea why such wild swings?

Awesome Miner uses the current profit information by default. You get less variations if you change it to the 24 hour average. You find this setting in Options dialog, Statistics section.

[patrike]

after upgrade to 4 version, a lot of times i see mining interface offline, or disconnected, but mining process running well on the farm. Restart agent and restart awesome miner helps sometimes, sometimes not, need to stop miner and start again

Are these Managed Miners or Managed Profit Miners? Any information in the log file for the mining computer where this happens?

Remote Agent log file can be accessed from the Remote Agent icon in the lower right corner of the screen, where the right-click menu has the option Log File.

[patrike]

Why is the awesome miner website not in https?

The Cloud Services web site and all purchase pages uses HTTPS. The main web site, where you mainly have information and documentation, is currently HTTP only. It's probably a good idea to change that to HTTPS at some point as well.

[patrike]

Please tell me how to configure Ethereum Dual mining in Profit Switching. That only I did not try anything ((

The profit switcher will automatically do Dual mining if it's more profitable. Please note that Dual Hashrate value for Ethereum and the secondary coins (Decred, Lbry, ...) will be used in these calculations.

When you have a Managed Profit Miner running, you can right click on it and select View Details. In that dialog you will see more information about profitability for each pool and combinations of Ethereum and secondary coins. This gives an understanding of how the profit decisions are made.

[Blogster]

i think theres a major bug with creating a reboot rule.
i deactivated all other rules to make sure its the cause.

I created a rule which should reboot the rig every 8 hours as soon as i saved the rule and clicked ok the Rig shutdown and rebooted windows.
ok....

Few minutes later i added an algo clicked in options ok ago rick shutdown and rebooted...
EVERYTIME i change something under options the rig reboots when the 8 hours reboot rule is activate.
When i deativate it everything is fine again no reboots

[patrike]

i think theres a major bug with creating a reboot rule.
i deactivated all other rules to make sure its the cause.

I created a rule which should reboot the rig every 8 hours as soon as i saved the rule and clicked ok the Rig shutdown and rebooted windows.
ok....

Few minutes later i added an algo clicked in options ok ago rick shutdown and rebooted...
EVERYTIME i change something under options the rig reboots when the 8 hours reboot rule is activate.
When i deativate it everything is fine again no reboots

Do you have this in the latest version 4.0.3 as well?

[Blogster]

i think theres a major bug with creating a reboot rule.
i deactivated all other rules to make sure its the cause.

I created a rule which should reboot the rig every 8 hours as soon as i saved the rule and clicked ok the Rig shutdown and rebooted windows.
ok....

Few minutes later i added an algo clicked in options ok ago rick shutdown and rebooted...
EVERYTIME i change something under options the rig reboots when the 8 hours reboot rule is activate.
When i deativate it everything is fine again no reboots

Do you have this in the latest version 4.0.3 as well?

yes