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.
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. |
|
|
|
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.aspxThe 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. |
|
|
|
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 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”. Hi, As chanberg pointed out, you need at least two triggers with "Match all" configured. Can you please provide a screenshot of your rule? |
|
|
|
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
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? I use Antmayner S7 and L3. I am adding devices, as indicated here http://www.awesomeminer.com/help/profitswitching.aspxAnd they show only their parameters, there is no switching over the pools. 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.aspxYou should enter your IP rule here as: W:192.168.0.0/24,W:127.0.0.1/32 I apologize for this question, but where to prescribe this rule? After all, Tools -> Antminer -> Configure API access not active. 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. |
|
|
|
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
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? I use Antmayner S7 and L3. I am adding devices, as indicated here http://www.awesomeminer.com/help/profitswitching.aspxAnd they show only their parameters, there is no switching over the pools. 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.aspxYou should enter your IP rule here as: W:192.168.0.0/24,W:127.0.0.1/32 |
|
|
|
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
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? |
|
|
|
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.
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 |
|
|
|
More accurate profit calculation and switching seems like the next big thing to be tackled in mining. There is a lot of opportunity for improvement. I don't want to depend on profit switching decisions from pools like Mining Pool Hub, that's too limiting. Ideally the algorithm should take into account past history of your actual mining hardware, performance of the pools used, and everything.
I'd also like to see just an easier to use mining front end. Awesome Miner is a very good application but configuring all the pools, miners, and templates gets a bit tedious because of all the different screens and mouse clicking involved. I'd also like to see A.M. more easily handle mixed mining rigs where you want AMD cards to mine one thing and Nvidia cards another thing. That's doable in A.M. but it could be a lot easier.
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. |
|
|
|
I´m wondering how reliable the profit profile switching is and if it picks the right coin to mine. The numbers jump from $5 per day to $0.8 per day.
I´ve tested Awesome Miner with 2x GTX 1070 and the software reported a profit of $2 per day wheras Nicehash generates $2.90 per day. The profile groups show also weird results. I´ve benchmarked one GTX 1070 and saved the profile. When selecting that profile in the Coins tab it shows $1.70 profit per day. Then I created a profile group, added the single GPU profile and set the profile count to 2. When I select the group profile the profit jumps to $11 per day. Honestly, the software looks great and has amazing features, but those weird numbers make me doubt.
/Doc
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? |
|
|
|
Hey patrike,
I've finally got a profit switching miner going nicely, and it truly is 'awesome'. I love it, except for one thing. I can't see a way to change GPU clock/mem settings before each algo switch.
The hashrate difference between the least and most optimal GPU setting can be quite big, or a setting will run fine with one miner/algo, but crash with another. I don't need MSI Afterburner integration or any of the extra features that come with the expensive versions. All I need is a way to run a few batch commands before each miner & algo starts. Like -
nvidiaInspector.exe -setBaseClockOffset:0,0,140 -setMemoryClockOffset:0,0,600 -setPowerTarget:0,75 -setTempTarget:2,0,83
I can see the option for batch commands with managed miners, but not with a profit switching miner. It would be nice if there was an option in the Algorithms section to run batch commands before each algo. Without this function I have to either run the GPU's at lower clock settings and lose profit, or manually run a batch file with optimal settings every time AM switches algo's. Most miners have options to set clocks, but they can't query 10 series cards. I'm happy to pay for this program, but I'm mining mostly for fun with just 4 cards. I don't need all the features that come with the expensive versions. Just a way to change GPU settings.
Cheers.
Thanks for your feedback on this. I will use this as input for future development and improvements |
|
|
|
Im new to this software and mining, i got a baikal giant plus and should i trust the profitability estimation in the online service of zpool x13 for profit switching?
Those numbers are the current profitability information from zpool, and those numbers can change quite fast. |
|
|
|
@Dev
it qould be nice if i could add some kind of description or comments to each miner
also it qould be perfect if there where any kind of team viewer integration (add a field for the teamviewer id and right click to connect).
thanks so far for this great piece of software
About launching Team Viewer, I don't know the supported command line arguments for that one, but I do have an example on the web site how you can launch Remote Desktop for the selected miner. Maybe this concept can be adjusted to work with Team Viewer as well? See "Example: Launch Remote Desktop for selected Managed Miner" on this page: http://www.awesomeminer.com/help/rules.aspx |
|
|
|
Hi,
a beginners question.
How did you handle adding the workers name?
I am using nanopool and ethermine for example:
ethermines username should be 0x11aaasd3225a7275a4968B7076895F0B19e48C5b.MinerName
nanopools username should be 0x11aaasd3225a7275a4968B7076895F0B19e48C5b/MinerName/name@mail.com
I didnt find a way to setup 2 pools as pool group to have a failover scenario.
if i use "Add to worker name" then the MinerName is on the end of the username. Its ok for ethermine but not for nanopool
any ideas? how did you handle this?
thanks
This is actually a bit complex, as some pools have their very own ways of specifying worker names. I think the very last section on this page will be of help in this scenario: http://www.awesomeminer.com/help/workername.aspx |
|
|
|
I ran diagnostics not showing anything bad.
I also reduced power to 80% still same thing is happening. I dont know what to do. Its very frustrating.
Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe
C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u 1GtNWJLVDQHHmvmE4HwrTyUkU5pRTLNeED -p x -b 0.0.0.0:4028 (WindowMode: ConsoleFormat, EngineType: CcMiner)
Configuration:
Mining Engine Process started, PID: 4692
====================================================================================================
> *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
> Built with VC++ 2013 and nVidia CUDA SDK 8.0 64-bits
>
> Originally based on Christian Buchner and Christian H. project
> Include some algos from alexis78, djm34, sp, tsiv and klausT.
>
> BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
>
> [2017-09-24 10:04:49][36m Starting on stratum+tcp://lyra2v2.mine.zpool.ca:4533[0m
> [2017-09-24 10:04:49] NVML GPU monitoring enabled.[0m
> [2017-09-24 10:04:49] NVAPI GPU monitoring enabled.[0m
> [2017-09-24 10:04:49] 8 miner threads started, using 'lyra2v2' algorithm.[0m
> [2017-09-24 10:04:50][33m Stratum difficulty set to 64 (0.25000)[0m
> [2017-09-24 10:04:50][36m lyra2v2 block 794692, diff 25795.206[0m
> [2017-09-24 10:04:50] API open to the network in read-only mode on port 4028[0m
> [2017-09-24 10:04:51] GPU #1: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #3: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #5: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #7: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #2: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #0: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #6: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:51] GPU #4: Intensity set to 20, 1048576 cuda threads[0m
> [2017-09-24 10:04:55] GPU #5: EVGA GTX 1070, 1035.13 kH/s[0m
> [2017-09-24 10:04:55] GPU #7: Gigabyte GTX 1070, 1035.13 kH/s[0m
> [2017-09-24 10:04:55] GPU #1: EVGA GTX 1070, 987.04 kH/s[0m
> [2017-09-24 10:04:55] GPU #3: EVGA GTX 1070, 924.75 kH/s[0m
> [2017-09-24 10:04:55] GPU #4: EVGA GTX 1070, 923.93 kH/s[0m
> [2017-09-24 10:04:55] GPU #6: Gigabyte GTX 1070, 909.73 kH/s[0m
> [2017-09-24 10:04:55] GPU #0: EVGA GTX 1070, 895.71 kH/s[0m
> [2017-09-24 10:04:56] GPU #2: EVGA GTX 1070, 883.60 kH/s[0m
> [2017-09-24 10:04:57][01;37m accepted: 1/1 (diff 0.537), 107.62 MH/s [32myes![0m
> [2017-09-24 10:05:01] GPU #5: EVGA GTX 1070, 25.10 MH/s[0m
> [2017-09-24 10:05:01][01;37m accepted: 2/2 (diff 0.452), 197.93 MH/s [32myes What kind of problem is that? Are other mining software working on you system? Can you please share more details.  no other software, but this is a "normal" problem of ewbf, happen on all my miner random. How hard are you pushing your rig? From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard. Thus, the GPUs are crashing and EWBF is trying to recover. Back off your power limits and or overclocks 5% here and there until you have a stable rig. You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit. Yes i have 1070s card, but i'm not talking about ewbf's problem, i'm asking if awesome miner should know when the 0sol error appears and restart the miner. You can use the Rules in Awesome Miner to detect low hashrate. You can see an example of this in the section "Example: Show notification on low hashrate" on this page: http://www.awesomeminer.com/help/rules.aspxThe example is only showing a notification, but you can also add an action of the type "Miner Command" and set it to Restart or Reboot. |
|
|
|
Feature request:
Add dual mining revenue under Coins and Online services for secondary coins.
Example:
Thanks for the suggestion. This could be an improvement for future versions. |
|
|
|
Hi, I bought the Enterprise version.
I've used it with different miners with no problems. Only mining with autoswitch that could not make it work in any way.
My doubt is:
I use the NHML (Nicehash Mining Legacy). I installed the AM agent and tried to connect the miner, also ip, however unsuccessfully. How to make AM just see Nicehash mining?
I'm currently using AM just as a monitoring my rigs of which are managed by NHML 1.8.1.3
Thanks
I assume you are using External Miner concept in Awesome Miner to connect to the mining software started by the Nicehash mining software. In order for this to work, the mining software must have API enabled and you need to know on which port the Nicehash software uses for this. Once you found this information in the Nicehash software, it should simply be to connect to the IP and port from Awesome Miner. I have the API but it's from the website (it's just one API for all miners together) , local software do not have one, how can I insert this API in the AM software so that I can monitor my rigs? Awesome Miner can connect to the API's of the mining software (Claymore miner, Ccminer, ...) that is running on your mining rigs. Awesome Miner is not connecting to any website for this. If you use the Managed Miner concept in Awesome Miner, all this will work out of the box. If you want to use the Nicehash application to launch mining software and only monitor from Awesome Miner with an External Miner, you do need to make sure that the Nicehash software enables the API (and which port) on the mining software for Awesome Miner to connect. |
|
|
|
My rig keeps crashing when doing autoprofit mining. I was previously mining etherium just fine. What could be the problem?
If you have your rig tuned to do Eth, then start it as a profit miner... when it changes to a different algorithm, the GPU settings could be wrong. Your over/underclocks for Eth could be the wrong settings for a different more stressful algorithm. Also, if you have your rig running on the edge of what your PSU can handle... you may be running into an issue with the PSU not being able to deliver enough power for a stressful algo based on your previous tuning for Eth. How many, and what kind of GPUs are you running? What PSU are you running? I am using 8x GTX 1070 with 1600 Watt EVGA plat PSU. I have restored the settings in msi and they are default with not OC. Not sure what the issue is I did notice that my CPU usage is very high around 70-80% when i was mining eth it was 30-40% Can you try to click the Diagnostics button to see if you get any additional information? Like what mining software is being selected, which algorithm and then the output from the mining software. It could be that your GPU/drivers/system isn't compatible with this mining software, and then it can be unselected from the profit switcher. The first step is however to use Diagnostics to figure out more details. |
|
|
|
@dev : About Nicehash pool, if i switch to the pool by AM, the worker name is not take by Nicehash stats.... Bug, no in the feature, or problem from nicehash  For example : IF i put worker name S9_1 in AM, no worker name in stats. If i use antminer webpage, it's OK. Have an idea ? I use minera 0.8.0 to run my miner. Could i also use AM to monitor and manage also remote control it?
No success with Minera and S9 for me. I prefer AM  I know that some characters cannot be used when setting worker names on the Antminers over the management interface. Even if these may work directly in the web for the Antminer, it may not work as expected from external applications like Awesome Miner. I can't recall how the support for is for _ (underscore), but as a first try you could try to change from "S9_1" to just "S91" or similar. |
|
|
|
|
Show Posts
