Is there a way to apply the GPU overclocking settings by algo and by card ? It sucks to have to change the settings for each card when i switch algos
buying the license for 20 machines you have OC that you can define for each al-go. Smaller licenses do not benefit from AL-GO with OC 20 machine licence does not allow overclocking if I recall. Ok now I’m confused lol Premium Edition (20 miners) includes all overclocking features. Both Native Overclocking and the MSI Afterburner integration. Lower editions doesn't include any overclocking features. |
|
|
|
Hey Patrik,
I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.
- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.
Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:
- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.
I think because there is no miner API established because of the crash, even if the mining window is still open? Hey Patrik, just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM. I think I know why this can happen: - The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate). - So there are 2 miners now and AM can't show the numbers for the T-Rex. Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe). Hi, Thanks for sharing the details. I can see from the API Report the T-Rex doesn't return anything and the reason is likely that NBminer uses the API port already, preventing T-Rex from using this port. Would it be possible for you to also send me the Remote Agent log file for the time where NBMiner was supposed to be closed? You should be able to see log messages like "Closing process" and maybe even "Killing process". What Awesome Miner do when closing mining software is to first send a friendly request to close down. Awesome Miner will then wait for the process to terminate (a number of seconds, configurable in the Options dialog, Mining Settings section), and if the process is still running, Awesome Miner tells Windows to kill the process. Hey Patrik, sent you the log file by PM and some more thoughts about that problem. This problem we are suffering a lot of. CAsi always have to restart to work well. I have a rule for dropped cards if they have 5 cards or less, reboot, when all my rigs are 6 But it would be a good thing to incorporate something that can be launched after each change to limit memory and processes caused by the miner. I have everything updated to the latest version of Windows both in rig and in the AM computer. The latest security update of cuda 10.1, latest driver. I even launch a VHL at the end of each mining to clean memory. But even so, the teams suffer frequent restarts, it is such, I have had to reduce the number of protocols and currencies, raise the% change so that there are fewer changes per day. I had some discussions with joseph32 on this topic and one change in the recent Awesome Miner release was to disable the NbMiner watchdog. The difficulty here is that there often are so many mining software involved and often changes between them so it's not always possible to tell if it's only one our of all mining software that are the cause for the instability. |
|
|
|
Hi Patrike,
since we installed the new version of AM, the trigger "Disconnected - API Access Denied" is not working anymore?
did you change anything regarding this behaviour?
BR Ralf
Hi Ralf, Thanks for your question. There are no changes to this feature since it was introduced, but I will investigate if I can find out any scenario where it's not working. If you find any additional details, please let me know. Thanks! |
|
|
|
Hey Patrike, love the addition of the glow notification! However, the two are reversed. It should blink when it hasn't been checked, and stay steady when notifications haven't been cleared. Blinking is more annoying then just being orange, so order of annoyance and severity basically.
Thanks!
Thanks for the feedback. If you enabled this feature and have at least one non-acknowledged notification, the icon will blink a few times and then constantly glow - until you activate the main window. This is currently not two separate concepts and it will only blink for a short time. I agree that constant blinking would be more annoying. Was your point that it should blink until you looked at the notification tab once? |
|
|
|
AM is now reporting LTC with a 544.04 value - can we pick the exchange that gets used? for both the ticker down below and for the profit per day calculations?
it is also reporting bchsv as having a daily revenue of $3,696.39 - it should be more like $205 range
Right now there is only a concept of priority order for coin statistics sources (see the Options dialog, Statistics Provider section) and it could be that for example CoinCalculators reported incorrect value for a while. By changing the priority you may resolve a temporary issue like this. |
|
|
|
So this isn't at all related to AwesomeMiner but wanted to share it if nobody has read it yet: https://thenextweb.com/hardfork/2019/06/11/nicehash-fbi-mariposa-cryptocurrency-dark-web-malware-mining/It's basically regarding Nicehash founder Matjaz Skorjanc and his connection with Darkode which is known for selling malware, botnets and hacking services. I'm not sure about you but I definitely don't want to run software on my machines that have any kind of connection with that. With AwesomeMiner you can still mine with Nicehash but without the risk of having your machines/computers compromised. Nicehash has quickly released a statement defending the allegations by saying that it's not related to them. https://www.nicehash.com/news/nicehash-statement-regarding-latest-allegationsStill I wouldn't feel safe with having their software on my network. @Patrike this is a great marketing opportunity for you sir! I'm attempting to sign up for the affiliate program but it says my application is under review. I've been a solid supporter of your program for several months now. Your prompt responses to inquiries, troubleshooting and open-mindedness for ideas/suggestions is excellent and I actually enjoy promoting your work on social media platforms. Thanks again for your dedication and all of your hard work. Thanks for sharing the information. It's good with information from both sides so everyone can form their own opinion. Your application has been approved now! It's a manual approve process. I appreciate your very nice feedback and also would like to say thanks for promoting the software and for being a part of this mining community. |
|
|
|
Here is a preview of what's in the pipeline. Next week you will be able to define a global fan curve where Awesome Miner will monitor the temperature of each individual GPU and adjust the fan speed individually to match the curve. There will be 5 points that you can move in any direction. This will work for both AMD and nVidia. If enabled, it will control the fan as long as Remote Agent (or Awesome Miner if you do local mining) is running. When you enable this feature it will completely disable all other fan operations you do via Awesome Miner.  |
|
|
|
I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.
Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.
Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example
X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00
With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.
In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.
Thanks for the suggestion, I see your point. This will add some complexity to the configuration, so it has to be some kind of advanced mode where you can specify additional conditions. As you point out it has to be per algorithm in the Profit Profile. Ditto to this, would be a nice thing right about now. Gets to about 32C in the day in Ohio but can drop in the low teens easy. Thanks for the suggestions. There is also another kind of flexibility that I would like to consider when looking into the clocking profiles. Today you can define a Clocking Profile per Profit Profile per Algorithm. But there should also be a per Miner concept in here. It's of course possible to create multiple Profit Profiles with the same settings but different Clocking Profiles - but that's not too user friendly. In addition to that - we also have the Time/Schedule concept both of you suggested. |
|
|
|
I would like to make a suggestion for AM. The software should make it easy for us to maximize revenue. The problem that I have now in Spain, in summer, is that of day we reach 40 - 42 degrees and at night between 18-24 degrees Celsius. With which a single OC is not the most appropriate. I have a single OC in each profile and in each al-go.
Right now I have a low OC so that by day it does not exceed 75 degrees, but at night the rigs go down to 50 degrees, since the ambient temperature is not the same. As happens in Spain will happen in other countries, against more tropical but it happens. In the countries of Eastern Europe the change is less noticeable.
Then my suggestion would be that in each profit profile and in each protocol, and optionally to be able to choose 2 OC with two hours of activation, for example
X16R day, 70 tdp 80 core -300 mem, activation time 10:00
X16R night, 85 TDP 100 core -300 mem, activation time 23:00
With which at night I have less environmental temperature to be able to extract more power, and to be able to lower day power. Now I only have 1 OC for the night and the day.
In winter it is less noticeable but also useful, it is not the same 13 degrees of day and -5 at night. I take the air from outside to cool and then I take it out again.
Thanks for the suggestion, I see your point. This will add some complexity to the configuration, so it has to be some kind of advanced mode where you can specify additional conditions. As you point out it has to be per algorithm in the Profit Profile. |
|
|
|
Hi guys
I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.
Can anybody help me how I can get the right piece of code to get fan speed or workername?
Hi, I did see your recent e-mail on this topic as well. For Fan speed there are no solution for Whatsminer yet. I will have to investigate that a bit more before I have a solution. For worker name you can use this expression: "Worker: " + (miningHelper.GetMainPoolStatus() != null ? miningHelper.GetMainPoolStatus().User : "") Hi Partike Thanks for your help. I tried your code, but got the following error: error CS1061: 'AwesomeMiner.Components.Intelligence.ProgressField.ProgressMiningHelper' does not contain a definition for 'GetMainPoolStatus' and no extension method 'GetMainPoolStatus' accepting first ... I Would appreciate if you double check the code. Hi, I think you are running on a quite old version of Awesome Miner. Please upgrade and it should work fine. |
|
|
|
Hi guys
I'm using Awesome Miner to manage some Whatsminer M3x ASICs. I'm trying to get some useful info, e.g. fan speed and worker name on Customization Progress Field. I tried "Fan Speed" +stats.Fan1 or "Fan Speed" +stats.FanSpeedOut, but none of them is working.
Can anybody help me how I can get the right piece of code to get fan speed or workername?
Hi, I did see your recent e-mail on this topic as well. For Fan speed there are no solution for Whatsminer yet. I will have to investigate that a bit more before I have a solution. For worker name you can use this expression: "Worker: " + (miningHelper.GetMainPoolStatus() != null ? miningHelper.GetMainPoolStatus().User : "") |
|
|
|
|
Awesome Miner version 6.5.5
ASIC mining
- Adjust the reported pool priority for BW L21 ASIC
GPU mining
- Improved detection of environment variables for nVidia commands via Remote Agent on Linux
Features
- Added a way to detect duplicated IP addresses for External Miners in the Options dialog, External Miner section
Mining Software
- CcMiner KlausT 1.25
Corrections
- Correction to exact IP address match in the Find Miner dialog
- NbMiner console correction for Remote Agent on Linux and disable watchdog
- Correction to the console tab to correctly clear the display when selecting a miner without any console output
|
|
|
|
my antivirus keeps on blocking the miners...never had any problems with any miners except those downloaded by your program....
When using the automatic download feature in Awesome Miner, a zip-file will be downloaded from the official download location if still available. As a fallback, an identical copy of the original zip-file can be automatically downloaded from the Awesome Miner web site. However, most anti-virus software warn about cgminer and similar mining software because they are being used by trojans and other malware. If you run into this problem, you can always manually download cgminer / sgminer and configure Awesome Miner to that use that downloaded instance instead. Thanks for your great software. There is a feature that I think Awesomeminer lacks. Please consider adding “Auto Update" feature to Awesomeminer, like any other applications even with schedule. It is a pain in the neck if you have multiple rigs, and every week, you use a remote session to go and click on update manually with high pings and delays. It is so easy for you to add this feature. Thanks for the suggestion. The general idea is to have a single Awesome Miner installed on one computer, and then run Remote Agent on all other computers you do GPU mining on. Then you only need to have one Awesome Miner to upgrade, and upgrading each Remote Agent is only a matter of clicking the 'Upgrade Remote Agent' button in the toolbar. |
|
|
|
patrike -
thanks! it does now show the hash rate and thus the estimated revenue/profit for the BW L21 now - the only other thing I notice is that the pool that shows is the pool #2 - it does not show what pool the miner is actually on. for example, if I put one pool in - it shows nothing. If I put two pools in, it shows the second one, even if the miner is mining on the first one.
I do understand your point here. The priority of the first pool has a higher number (crazy high as in 16842752) when reported from the ASIC miner, when it in fact should be priority 0. The second pool has priority 1. For this reason Awesome Miner will consider the second pool to be active. This is another case where the BW L21 ASIC doesn't report correct information, but I will adjust Awesome Miner to consider very high priority numbers to be 0 instead. Priority 0 is the current active pool. |
|
|
|
|
Awesome Miner version 6.5.4
ASIC mining
- Improved support for recent revisions of BW L21 ASIC
GPU mining
- Show nVidia fan speed as RPM (in addition to percent) when running Remote Agent on Linux
User interface
- Dark mode for the main window of Awesome Miner. Configurable in the Options dialog, General section.
Mining software
- TeamRedMiner 0.5.1
- WildRig Miner 0.17.5
- T-Rex 0.11.1
Corrections
- Correction to GPU selection for TeamRedMiner
- Correction to the use of screen command on Linux
|
|
|
|
I shouldn't have to set any power usage for my miners. I'm getting power usage from the firmware. As you can see in the summary, since I'm running asicFW firmware, I have power usage for each board. As per https://support.awesomeminer.com/support/solutions/articles/35000104685-power-consumption-and-profitabilityPower consumption and profitability
Introduction
Awesome Miner can read and display the current power usage of both nVidia and AMD GPU's, independent of which mining software being used.
ASIC miners in general doesn't have any feature where they can report the power usage and for this reason Awesome Miner cannot display the actual power usage, only manually configured values for power usage together with linear power scaling based on the current hashrate.
It's currently only ASIC miners running the custom firmware AsicFW that can report power usage to Awesome Miner.
It's very nice to have power usage per board. I'm looking to have an easy way to get the total of all three boards. Though I could do it with a custom progress field. The actual power usage should be displayed in the Performance column as well, so I think the reason it doesn't show up is that Awesome Miner may not be configured to show the Actual Power usage (instead of the Static values that typically are used for ASIC's). Please go to the Options dialog, Profitability section, and change the "Power usage mode" to one of the Actual Usage settings. |
|
|
|
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
This miner is supported, at least previous revisions of it. Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate. It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks! pm sent with the API log Perfect - thanks for the log! I had to make a small adjustment to get Awesome Miner to detect this miner as a BW-L21. Once that detection was updated, it shows up fine. nice! so in a future update? Yes, it will be included in the next release. eta on that update? just so I know when to use AM again for looking at profitability - it currently puts me in the red due to the 3 miners showing as using power but with zero hash rate. it doesnt even show the right pool - maybe thats why the hash rate is zero... hmm, let me try to delete the second pool. nope that does not work. down in the bottom area where the summary area is, if i click asic it shows them hashing, it just doesnt translate up to the top. the top area seems to want the second pools information. but i cant leave pool one blank . I will soon make a release with the BW-L21 updates. With the changes I do see hashrate, accepted shares and pools displayed correctly. |
|
|
|
Hey Patrik,
I think I already asked this sometime before, but couldnt show a picture and details because this happens very rare.
- One or more cards are crashed. The mining window is still open, but isnt mining anymore.
- In AM it still shows "mining", but without any informations. AM will not restart that miner.
- The "GPU" tab is empty, also the "Pools" tab.
Is it possible to setup a rule to catch this? Or maybe AM can handle this automatically? I already tried some rules, but none works. Neither a single rule, or combined rules. For example:
- The trigger "Detect Miner State -> Mining" doesnt work.
- "Detect Device Count -> 0" doesnt work.
- "Power Usage -> 0" doesnt work.
I think because there is no miner API established because of the crash, even if the mining window is still open? Hey Patrik, just got that situation again with the new T-Rex version in one of my single miners. Will send you the API-report by PM. I think I know why this can happen: - The profit switcher switched from NBminer to T-Rex, but NBminer wasn't closed for real. It is already running in the background (but depending to the pool with 0 hashrate). - So there are 2 miners now and AM can't show the numbers for the T-Rex. Is it somehow possible to double check (and kill) old unneeded tasks? Tried it with a batch command when NBminer stops, but this doesn't work all the time (taskkill /F /IM nbminer.exe). Hi, Thanks for sharing the details. I can see from the API Report the T-Rex doesn't return anything and the reason is likely that NBminer uses the API port already, preventing T-Rex from using this port. Would it be possible for you to also send me the Remote Agent log file for the time where NBMiner was supposed to be closed? You should be able to see log messages like "Closing process" and maybe even "Killing process". What Awesome Miner do when closing mining software is to first send a friendly request to close down. Awesome Miner will then wait for the process to terminate (a number of seconds, configurable in the Options dialog, Mining Settings section), and if the process is still running, Awesome Miner tells Windows to kill the process. |
|
|
|
Does anyone know which pool in Awesome Miner is most profitable for Nvidia gpus lately?
Thanks
For the predefined pools in Awesome Miner, the recommendation is to run the Benchmark once to make the profit switcher aware of what is most profitable. You can also view the Online Services tab in Awesome Miner at this point if you want to get an overview of the profitability of the predefined pools. There can of course be other pools with even higher profit than those predefined in Awesome Miner as there are other mining pools for more recent coins on less common algorithms - but it requires a bit more work to keep up with all the latest and smaller coins. |
|
|
|
Just asking I guess awesome miner doesn't Support AMD Radeon VII ?. I don't expect it to be added right now just want to know.
it only shows the hash rate no fan speed, temps etc.
I will verify the support within the next few days and get back to you. |
|
|
|
|
Show Posts
