Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 537. (Read 703113 times)

Very good suggestion. Today there is a Detect Dead Device trigger, but that one is only looking for if the mining software reports a GPU as not working. It doesn't handle the scenario where a GPU is completely missing. I have this high on the priority list for future versions.

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.

Update to 4.0.3 isn't working, after restart still in 4.0.2 asking to update to 4.0.3 @ UTC time 3:53 am Saturday

SUGGESTION

Add the feature to detect if a single GPU goes offline. This would require you to set how many GPUs the miner should have. ie RIG01  GPUs: 8. If RIG01 ends up only having 7 it would give a notification. This would be very helpful with people who have auto reboot features and auto start scripts. My rigs switch often so its hard to look at a hash rate and know if its good or not or know if a GPU was not recognized by the system.

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,
As chanberg pointed out, you need at least two triggers with "Match all" configured. Can you please provide a screenshot of your rule?

Hi,
OK, that feature requires Professional Edition or above. What you can do is to manually do SSH to each Antminer and setup the API access. You need to modify cgminer.conf (or bmminer.conf if you have any S9's). You will see a line about "api-allow" that you modify according to the IP rule I suggested above.

Hi chanberg,

I did exactly that initially and all it does is delay the trigger for that amount of time. It’s still the situation that if I hit 199MH/s for even 1 second in that 10 minute window it still fires the trigger to restart the miner every 10 minutes. Because technically it was under 200MH/s at some point during that 10 minute window.

To my knowledge there is not a functional rule that truly means “if at x hashrate for x amount of time then trigger”.

Add a time trigger that checks every 10 minutes, then select the option “match all”
So the two triggers have to match in order for action to occur

Hi Patrike,

I’ve been using your paid edition of AM for about 4 months and loving it. I have a lot of rules and notifications set and am just now starting to try the hashrate trigger rules and think there’s not one for this situation.

I have tried both triggers to attempt to restart claymore:

(hashrate kH, avg)  -> current -> less than or equals -> 200,000

(hashrate kH, 5s) -> current -> less than or equals -> 200,000


Also tried to change “current” to “1 minute ago” and up to “10 minutes ago”.

It seems that as soon as the miner falls under 200MH it triggers the restart. I do have fluctuation on this rig for a few seconds every now and then so its literally triggering a restart as often as I set it to check.

I was hoping that choosing the “interval” to check the trigger for 30 seconds or a minute would mean the average over that time, or if it's under the target hashrate for that long. But if I touch 199MH for 1 second anywhere in that “interval” range no matter what timeframe I chose it will trigger.

In the end I’m just trying to set a trigger to restart the miner if “under 200MH/s for longer than 10 seconds” or something to that effect.

Thanks!

Hi Patrick,

        few questions regarding ASIC D3 and L3+ miners.


1. Do I have to set up in external switching mode (using ASIC) for nicehash only BTC address or can be also DASH wallet address (when I'm mining DASH)
2. How to set up when using Zpool to automaticaly switch between X11 coins. Because when I use unspecified X11 coin it shows lower coin per day as when I choose the highest X11 coin from COIN TAB (I can send screensots if necessary)
3. I'm in no way able to enable Multi pool hub (coin switching for DASH). It's still dead.

What am I doing wrong, is their pool for DASH active ? I tried ton of combinations

This is what they recommend

HOST:   hub.miningpoolhub.com
PORT:   20465
Username:   weblogin.workername

What is the correct setting for using it on Awesome miner as coin switching on X11 ?

Thank you for answers.

I apologize for this question, but where to prescribe this rule? After all, Tools -> Antminer -> Configure API access not active.

Now I understand the scenario. You should follow this guide here, describing how Awesome Miner can configure your Antminers for Privileged API access:
http://www.awesomeminer.com/help/antminerapi.aspx
You should enter your IP rule here as:
W:192.168.0.0/24,W:127.0.0.1/32

I use Antmayner S7 and L3.
I am adding devices, as indicated here
http://www.awesomeminer.com/help/profitswitching.aspx

And they show only their parameters, there is no switching over the pools.

If you use a Managed Miner, Awesome Miner will setup all API access for you so you don't need those command line arguments. Can you explain a bit more about what isn't working in that scenario? What mining software are you using?

In which field do you need to insert parameters manually?
Because in the automatic mode there is no access.

Do you need to insert this record?
--api-allow W:192.168.0.0/24,W:127.0.0.1

That's possible with the Free Edition as well. I think your miner is running in Restricted API Mode, which you can see on the Summary tab in Awesome Miner when you have selected your Antminer.

By default, Antminers are configured with Restricted API access, which only makes it possible to monitor the mining statistics, but not performing operations like changing pool. Awesome Miner can help with configuring your Antminers to run with Privileged API access instead. See:
http://www.awesomeminer.com/help/antminerapi.aspx

Hello.
I decided to download a free version of the program and try to connect to it Antminer S7 for switching profitability.
Nothing happens. Or is it only possible in a paid version?
Help please with the settings.
Here is the configuration API.

Version: 4.0.2
API command: config
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1506520775,
      "Code": 45,
      "Msg": "Access denied to 'config' command",
      "Description": "cgminer 4.8.0"
    }
  ],
  "id": 1
}
API command: summary
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1506520775,
      "Code": 11,
      "Msg": "Summary",
      "Description": "cgminer 4.8.0"
    }
  ],
  "SUMMARY": [
    {
      "Elapsed": 3755,
      "GHS 5s": 4697.23,
      "GHS av": 4729.14,
      "Found Blocks": 0,
      "Getworks": 80,
      "Accepted": 353,
      "Rejected": 4,
      "Hardware Errors": 19,
      "Utility": 5.64,
      "Discarded": 1288,
      "Stale": 0,
      "Get Failures": 0,
      "Local Work": 8204094,
      "Remote Failures": 0,
      "Network Blocks": 5,
      "Total MH": 17759859500.0,
      "Work Utility": 66065.27,
      "Difficulty Accepted": 3616768.0,
      "Difficulty Rejected": 40960.0,
      "Difficulty Stale": 0.0,
      "Best Share": 0,
      "Device Hardware%": 0.0005,
      "Device Rejected%": 0.9906,
      "Pool Rejected%": 1.1198,
      "Pool Stale%": 0.0,
      "Last getwork": 1506520775
    }
  ],
  "id": 1
}
API command: privileged
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1506520775,
      "Code": 45,
      "Msg": "Access denied to 'privileged' command",
      "Description": "cgminer 4.8.0"
    }
  ],
  "id": 1
}
API command: devs
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1506520775,
      "Code": 9,
      "Msg": "1 ASC(s)",
      "Description": "cgminer 4.8.0"
    }
  ],
  "DEVS": [
    {
      "ASC": 0,
      "Name": "BTM",
      "ID": 0,
      "Enabled": "Y",
      "Status": "Alive",
      "Temperature": 56.67,
      "MHS av": 4729135.81,
      "MHS 5s": 4982470.8,
      "Accepted": 353,
      "Rejected": 4,
      "Hardware Errors": 19,
      "Utility": 5.64,
      "Last Share Pool": 0,
      "Last Share Time": 1506520743,
      "Total MH": 17759859500.0,
      "Diff1 Work": 4135040,
      "Difficulty Accepted": 3616768.0,
      "Difficulty Rejected": 40960.0,
      "Last Share Difficulty": 16384.0,
      "No Device": false,
      "Last Valid Work": 1506520775,
      "Device Hardware%": 0.0005,
      "Device Rejected%": 0.9906,
      "Device Elapsed": 3755
    }
  ],
  "id": 1
}
API command: pools
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1506520775,
      "Code": 7,
      "Msg": "3 Pool(s)",
      "Description": "cgminer 4.8.0"
    }
  ],
  "POOLS": [
    {
      "POOL": 0,
      "URL": "stratum+tcp://stratum.antpool.com:3333",
      "Status": "Alive",
      "Priority": 0,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 75,
      "Accepted": 353,
      "Rejected": 4,
      "Discarded": 1288,
      "Stale": 0,
      "Get Failures": 0,
      "Remote Failures": 0,
      "User": "edmal3",
      "Last Share Time": "0:00:32",
      "Diff": "16.4K",
      "Diff1 Shares": 4135040,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 3616768.0,
      "Difficulty Rejected": 40960.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 16384.0,
      "Has Stratum": true,
      "Stratum Active": true,
      "Stratum URL": "stratum.antpool.com",
      "Has GBT": false,
      "Best Share": 0,
      "Pool Rejected%": 1.1198,
      "Pool Stale%": 0.0
    },
    {
      "POOL": 1,
      "URL": "stratum+tcp://stratum.antpool.com:443",
      "Status": "Alive",
      "Priority": 1,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 2,
      "Accepted": 0,
      "Rejected": 0,
      "Discarded": 0,
      "Stale": 0,
      "Get Failures": 0,
      "Remote Failures": 0,
      "User": "edmal3",
      "Last Share Time": "0",
      "Diff": "",
      "Diff1 Shares": 0,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 0.0,
      "Difficulty Rejected": 0.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 0.0,
      "Has Stratum": true,
      "Stratum Active": false,
      "Stratum URL": "",
      "Has GBT": false,
      "Best Share": 0,
      "Pool Rejected%": 0.0,
      "Pool Stale%": 0.0
    },
    {
      "POOL": 2,
      "URL": "stratum+tcp://stratum.antpool.com:25",
      "Status": "Alive",
      "Priority": 2,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 3,
      "Accepted": 0,
      "Rejected": 0,
      "Discarded": 0,
      "Stale": 0,
      "Get Failures": 0,
      "Remote Failures": 0,
      "User": "edmal3",
      "Last Share Time": "0",
      "Diff": "",
      "Diff1 Shares": 0,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 0.0,
      "Difficulty Rejected": 0.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 0.0,
      "Has Stratum": true,
      "Stratum Active": false,
      "Stratum URL": "",
      "Has GBT": false,
      "Best Share": 0,
      "Pool Rejected%": 0.0,
      "Pool Stale%": 0.0
    }
  ],
  "id": 1
}
API command: coin
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1506520775,
      "Code": 45,
      "Msg": "Access denied to 'coin' command",
      "Description": "cgminer 4.8.0"
    }
  ],
  "id": 1
}
API command: notify
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1506520775,
      "Code": 45,
      "Msg": "Access denied to 'notify' command",
      "Description": "cgminer 4.8.0"
    }
  ],
  "id": 1
}
API command: stats
{"STATUS":[{"STATUS":"S","When":1506520775,"Code":70,"Msg":"CGMiner stats","Description":"cgminer 4.8.0"}],"STATS":[{"CGMiner":"4.8.0","Miner":"3.5.3.0","CompileTime":"Mon May 23 14:53:27 CST 2016","Type":"Antminer S7"}{"STATS":0,"ID":"BTM0","Elapsed":3755,"Calls":0,"Wait":0.000000,"Max":0.000000,"Min":99999999.000000,"GHS 5s":4697.23,"GHS av":4729.14,"baud":115200,"miner_count":3,"asic_count":8,"timeout":5,"frequency":"700","voltage":"0.706","hwv1":3,"hwv2":5,"hwv3":3,"hwv4":0,"fan_num":6,"fan1":3720,"fan2":0,"fan3":3600,"fan4":0,"fan5":0,"fan6":0,"fan7":0,"fan8":0,"fan9":0,"fan10":0,"fan11":0,"fan12":0,"fan13":0,"fan14":0,"fan15":0,"fan16":0,"temp_num":3,"temp1":58,"temp2":58,"temp3":54,"temp4":0,"temp5":0,"temp6":0,"temp7":0,"temp8":0,"temp9":0,"temp10":0,"temp11":0,"temp12":0,"temp13":0,"temp14":0,"temp15":0,"temp16":0,"temp_avg":56,"temp_max":59,"Device Hardware%":0.0005,"no_matching_work":19,"chain_acn1":45,"chain_acn2":45,"chain_acn3":45,"chain_acn4":0,"chain_acn5":0,"chain_acn6":0,"chain_acn7":0,"chain_acn8":0,"chain_acn9":0,"chain_acn10":0,"chain_acn11":0,"chain_acn12":0,"chain_acn13":0,"chain_acn14":0,"chain_acn15":0,"chain_acn16":0,"chain_acs1":"oooooooo ooooo oooooooo oooooooo oooooooo oooooooo ","chain_acs2":"oooooooo ooooo oooooooo oooooooo oooooooo oooooooo ","chain_acs3":"oooooooo ooooo oooooooo oooooooo oooooooo oooooooo ","chain_acs4":"","chain_acs5":"","chain_acs6":"","chain_acs7":"","chain_acs8":"","chain_acs9":"","chain_acs10":"","chain_acs11":"","chain_acs12":"","chain_acs13":"","chain_acs14":"","chain_acs15":"","chain_acs16":"","USB Pipe":"0"}],"id":1}

Thanks for your feedback. There is always a balance between flexibility/features and ease of use.

GPU mining is a very complex operation as it involves multiple kinds of mining software, none of them compatible with the others, different kind of pools that have their own ways they want worker names and wallets configured and so on. New mining software, algorithms and pools are constantly made available, and all this just needs to work together. In addition to that, all should work in a distributed solution involving multiple computers and networks in between, and of course with rules, web access and cloud, multi-user support and so on. There will always be some configuration and reading on the web site to learn all these concept, but it gives a lot of flexibility and makes it possible to scale the solution to large farms. The mining industry is still very young and I think that's why we still have so many incompatible concepts (software, pools, miner API's, ...) and that creates complexity.

It's fully possible to simply use the Wizard the first time you run Awesome Miner, select profit switching, enter your bitcoin address for Nicehash and start the miner. So it doesn't have to be more complex than that.

As you point out, the current profit numbers change a lot. What you can do is to change from current profit values to 24h average values instead. You find this setting in Options dialog, Statistics section. Then you will get more stable numbers.

These questions about profit switching is constantly being discussed and there are for sure drawbacks with doing profit switching. What you mine will in many cases be dumped on an exchange and when that is done at a larger scale, the pool will get much less profit that first expected. These are some of the reasons that profit switching isn't always the best strategy for mining. These are general issues with profit switching and not specific to Awesome Miner.

I've not received any other reports on v4.0.2 for the Group Profile profits. Back in 4.0.0 I know there as a calculation issue with the groups. Can this be reproduced all the time?