Good afternoon.
Here are the old requests for which I did not receive an answer:
1. See the photo. Add this for each farm and you can select wallets and pools for each miner separately!!
2. The most ancient mistake that you do not eliminate. Your program sees that my farm consists of 4 maps and why if one card when the transition from one algorithm to another died the farm does not reboot - it's elementary - there were 4 cards became 3 means you need to reboot.
3. Still the same ancient trouble arises with ccmainer Alexis - when in the manner of the error occurs, the error message is displayed. In this case, mining stops and the program does nothing until I manually click on this error on the farm (((
1. I'm not sure what we are looking at here. The first picture shows that you are using a custom pool group for profit mining, and the second picture is showing an empty override directly on the Managed Profit Miner. You would want to leave the override empty, unless you wanted this particular Managed Profit Miner to do something different from the global settings. Or are you pointing out that the override is missing the option for a custom pool group? 2. I think you should troubleshoot why you have a card that is dying first. Do you have adequate power from your PSU? How many watts is it? Do you use risers? Have you tried moving the risers around to see if the problem follows the riser? Do you have your overclock or underclock settings set too far out of range for the new algorithm when it switches to it? 3. What does the error message say? You may want to set a rule that if hashrate falls below a threshold then to reboot the computer. This may help with your missing GPU problem in #2 above as well. Make sure that you set the Managed Miner, or the Managed Profit Miner to autostart so that it will resume mining after the reboot. 1. Yes, the override is missing the option for a custom pool group. Please add as this is a very necessary option. 2. This problem occurs when you go from one algorithm to another. MSIAfterburnerRemoteServer not on all farms, I get into autoloading ((the system either removes it or just does not start it in autorun.) I think eventually you will find a durable replacement for MSIAfterburner and build control into the body of your program.In the meantime, I ask you to add to the monitoring section the ability to determine how many cards are working and if one of them has shut down to reboot the system! 3. I'll try to solve this problem by setting a low hashrate, thanks. 1) "Add to worker name" can be set individually for each Manage Profit Miner. It will however only change the last part of the worker name. Your request is about changing the full worker name? 2) Detection of missing GPU (change from 4 to 3 all of a sudden) is very high on the priority list. I know you have requested this in the past, but I do get a very large number of requests for feature right now so I'm trying to prioritize everything. |
|
|
|
I agree that it would be a nice improvement to add a trigger that is looking at hashrate for a specific time like you suggest.
If you look at the actual hashrate in your scenario, is it dropping below 200MH/s that many times within a few minutes? What's the standard hashrate when everything is working fine?
Hi Patrike, Yes it is on this 8 GPU rig I have 2 troublesome GPUs (2 570’s in a 580 rig) that like to drop significantly every now and then (which is what’s triggering the only rule I have available for hashrate). Usually they recover fine in seconds but every few days its seems like they stay in that dropped state which is what made me try your rules out. It rolls at ~205MH/s 99% of the time. Is there any way you can add something like that to the roadmap? Or is that too much of an overhaul? Thanks. I will make a note of this request. The rules are quite sensitive and requires some effort to get correct, so it's not a quick fix. |
|
|
|
Thanks for your feedback. The software definition file is only made available when there are supported definitions available for upgrades, if not, this error can be found in the log file but doesn't do any harm. This one is Signatum that recently went from being possible to mine into POS. No longer listed on WhatToMine and next version of Awesome Miner will remove this request http://whattomine.com/coins/191.json |
|
|
|
Can you please tell us how to use Putty to put the privileged API rights in Terminator A2 and Dominator A4 ?
I don't know how to do this. Maybe there is some forum thread for these miners where you can find the answer? |
|
|
|
Is it possible to set the price manually (or at least profit) for the coins that are not present on wtm or even exchange?
You can add custom coins in Options dialog, Coins&Profit section. You can define either coin properties and exchange rate or simply profit per MH/day. Yes there I can set manually all or simply profit. But is it possible to set only price. So that difficulty will be taken from the pool? Setting an exact price like that is not possible. You can set a factor if you want the price to be adjusted compared to the exchange rate - but it will still depend on the exchange rate. |
|
|
|
okay I got the premium addition
I am trying to attach to a rasp pi 3 that runs 2 avalon 741's
so settings would help me since I have never used this
the rasp pi is set here
API Allow (Default: W:127.0.0.1)
its ip on my network is
192.168.0.100
so what do i do to connect to it.
I think the rule you are looking for is something like the following: W:127.0.0.1/32,W:192.168.0.0/24 |
|
|
|
Is it possible to set the price manually (or at least profit) for the coins that are not present on wtm or even exchange?
You can add custom coins in Options dialog, Coins&Profit section. You can define either coin properties and exchange rate or simply profit per MH/day. |
|
|
|
SO it would be nice to know what I need to run bitmain s-9 at a remote location and Avalon 721 and 741 at remote locations.
looks like at least professional at 70
anyone running Avalon 721's 741's with this software s-9s and gpus.
I have 3 rasp pi's at 2 different ip's---- this is 3
I have s-9s at the same ip's ----------- this is 4-5
I have gpus rigs at three ip's ----------- this is 7
comes to 15 so maybe premium at 140 is the way to go.
does this software do the avalons via rasp pi's
So we had a mail conversation on this, but just to let everyone else know, Avalon miners are supported via the Raspberry Pi device. |
|
|
|
Is there any easy way to add many pools/coins? Some kind of text/json file?
Or may be I can download config with most used pools/coins somewhere?
The same with algo/miners for Nvidia GPUs. There are no defaults for many algos.
So you don't want to use the user interface in Awesome Miner to do this? There are no configuration files ready to be downloaded with what you request. If you really want a text file interface, you need to manually modify the Awesome Miner configuration file (%appdata%\AwesomeMiner\ConfigData.xml) when the software isn't running. You do need to follow the same pattern and give unique ID number to each entry. There is no documentation available for how to do this. |
|
|
|
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. Thanks Patrike, I have 3 time triggers now, current, 1 minute ago and 3 minutes ago and tested for over 24 hours now. It’s the same situation (of course triggered a little less often adding the 3rd time variable). Still though if I dip under 200 "3 minutes ago" and "1 minute ago", then again "currently" for even a second in all of those timeframes, it triggers. I can’t believe no one has brought this up before. Do you have any other thoughts on how to implement a simple trigger of “below x hashrate for x time”? In my situation I was just after “below 200MH/s for 30 seconds consecutive” then trigger to restart the miner. Thanks again. I agree that it would be a nice improvement to add a trigger that is looking at hashrate for a specific time like you suggest. If you look at the actual hashrate in your scenario, is it dropping below 200MH/s that many times within a few minutes? What's the standard hashrate when everything is working fine? |
|
|
|
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) Ty Patrike, i'm trying enterpise version. In "gpu settings" i see - Power Limit - Core Clock - Memory Cloock - Fan Speed But i have not "Max GPU Temp", culd be possible have this setting? Ty Thanks for the feedback. Right now that's not supported beacuse I don't think it's exposed via the Afterburner API when doing GPU clocking over that interface. |
|
|
|
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. What are you talking about?! In my group there are only two tick marks - on Ethereum and Sia. By any logic, Ethereum + Sia is more than Ethereum! Please look at your profit profile (Options dialog, Profile profile, edit the profile you use, for example AMD or nVidia), and see the Hashrate and Dual Hashrate for Ethereum and SIA. What does these hashrates look like? Depending on these settings, Awesome Miner will either go for Ethereum mining or Ethereum+Sia mining. If you have a low Dual Hashrate configured, just plain Ethereum mining can be more profitable than Ethereum + Sia. If you have identical hashrates, of course Ethereum + Sia is most profitable. |
|
|
|
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? |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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) |
|
|
|
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. 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. |
|
|
|
|
Show Posts
