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. |
|
|
|
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? |
|
|
|
More examples for setting up RulesI'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. |
|
|
|
|
This release was made available yesterday: Awesome Miner Version 4.0.3
- Improved branding support of Awesome Miner
- Awesome Miner API introduces a new method for getting the same summary information as being displayed on the dashboard
- Awesome Miner API methods supports filtering the responses to only include information that the specified user is allowed to see
- Several minor corrections
|
|
|
|
More examples for setting up RulesI'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
|
|
|
|
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
If there are pending upgrades for Windows Update, Windows may prevent other installation software from running. The solution is to reboot the computer, where Windows Update will perform the required tasks. After the reboot, it will be possible to upgrade Awesome Miner. In addition to using the upgrade feature inside Awesome Miner, the latest version of the software can also be downloaded and installed from the web site. |
|
|
|
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. |
|
|
|
|
Show Posts
