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

Thanks for the report.

I've identified the scenario. If you have multiple addresses and the check for one of them fail, the failure will not be indicated in the user interface. The last balance for the address will still be displayed, but no longer part of the total.

I will correct this in the next release, to indicate if there was a failure and let the total value assume the last known balance for the address that failed once. After this change, you will always see the total balance correctly.

Right now your mining software is launched and controlled by Ethos and you are using the External Miner concept in Awesome Miner to monitor the mining details.

In order to be in full control of the mining, you need to:
1) Install Awesome Miner Remote Agent on Linux
https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linux
2) Instead of using an External Miner, you add your miner as a Managed Miner, where you can define mining software and mining pool to use. At this point, Awesome Miner will be responsible for launching and controlling the mining software.
https://support.awesomeminer.com/support/solutions/articles/35000085995-add-managed-miners-using-the-wizard

I don't have have experience with EthOS myself, but the concept above are the general steps to run Awesome Miner Remote Agent on Linux.

Can you please go to the Options dialog, Statistics Provider section and see if "Keep coins even when no longer listed by provider" is enabled? If not, please check it to make sure Awesome Miner keeps coins from being removed.

Hey Patrik,

the Core Voltage (%) is just a very small boost, maybe 1% or so with +100. But I really like that option. It will boost the hashrate a little bit with just a bit higher voltage, but the GPU clock stays at the same number. If I just increase the voltage to the same value, the hashrate will be lower. So I have to increase the core clock too to match the higher hashrate. But if the card is already running with the highest clock, I cant increase it any higher. Thats my observations to that setting.

Its nothing big here, but a few more cents per hour per card could be worth asking you But if its not possible to edit that setting with the native overclocking, it will be no problem. The native OC is one of the greatest tools inside AM. So keep up the great work!

is there a way to use ETHOS with AM?

I can see the reports on AM, but can not control the miners and the hardware using ETHOS...

Is there a way?

Cant understand why profit statistic data for Cortex coin come and gone randomly? Anyone have the same issue? Is this statistic provider problem or AM problem? This happens only with Cortex. If this behavior come from provider, maybe is a good idea to store last recived statistic data and mark the outdated data with another color till new actual data will be recived from provider. Otherwise this made profit switching process crazy. I see that the mining of Cortex is profitable, but if AM has not recived data, AM switch my rigs to other coin.

Hey Patrik,

the Core Voltage (%) is just a very small boost, maybe 1% or so with +100. But I really like that option. It will boost the hashrate a little bit with just a bit higher voltage, but the GPU clock stays at the same number. If I just increase the voltage to the same value, the hashrate will be lower. So I have to increase the core clock too to match the higher hashrate. But if the card is already running with the highest clock, I cant increase it any higher. Thats my observations to that setting.

Its nothing big here, but a few more cents per hour per card could be worth asking you But if its not possible to edit that setting with the native overclocking, it will be no problem. The native OC is one of the greatest tools inside AM. So keep up the great work!

Hi Joseph and thanks for your question.

I'm not aware how to set Core Voltage (%) like MSI Afterburner. On nVidia 2000-series it isn't supported at all. On the 1000-series nVidia will enforce a number of limits the voltage anyway so you will never get 100% higher voltage even if configured. This is why the nVidia drivers mainly focus on the "Core voltage limit" these days.

What kind of voltage behaviors do you get when you set it to +100% compared to 0% in MSI Afterburner? How does that compare to setting a voltage limit in Awesome Miner instead (at keep the setting in MSI Afterburner at 0%)?

Hello, new here.

I'm having a very strange issue with AM. I am using a paid license for AM and my boss asked me to switch to mining ETH directly a couple of weeks ago. The easiest way to do what he requested was to recreate all of my miners as managed miners. To do this, I had used the  network scan to bulk create all the miners based on any machines the manager found on the network running Awesome Miner Remote Agent. However, that plan was short lived and I was soon asked to switch it all back. After removing all of the managed miners I created, I am now having issues getting the original managed profit miners to start properly. I seem to only be able to get a few of them to start at a time and when I tell the ones that are stopped to start, it stops a bunch of the ones that were already mining and this just keeps going around in circles. I have recreated some of the miners but that has had little effect.  I've RDP'd into each one and manually restarted the remote agent and I've rebooted each and every mining rig as well as the manager rig and nothing seems to be resolving this problem. Also. the Start and Stop buttons sometimes have absolutely no effect on the miner I actually have highlighted when I click the button. It is absolutely mind-boggling.

Does anyone have any suggestions?

Thanks.

EDIT: On closer examination, it appears that a some of these rigs that AM says are "stopped" are actually mining but it doesn't show up in AM.

If I could just get the Start/Stop buttons to stop appearing to control more than one rig at a time, that would be great.

EDIT AGAIN: It appears that simply changing the description of one of my miners can have a pretty big effect on the rest of the miners, making them stop or start. It makes no sense.

FINAL EDIT: TL;DR: NONE of my miners are duplicates but the Start/Stop buttons in AM seem to affect more than one miner anyway. How do I fix this?

ACTUAL FINAL EDIT: Alright nevermind. I've fixed it. Turns out there were a bunch of duplicate miners in the Managed Hosts section of Options. This software really sucks.

I can clearly see that you are running some pirate/hacked version of Awesome Miner that you didn't pay for.

1) Uninstall Awesome Miner and run an anti-virus check on your computer. Hopefully you don't have any viruses at this point
2) Remove your Awesome Miner configuration files. Remove all files in this folder: %appdata%\AwesomeMiner\
3) Download and install Awesome Miner from our web site:
https://www.awesomeminer.com/download
4) Sign up for a subscription on our web site:
https://www.awesomeminer.com/signup
5) Once you have a valid subscription, I'm more than happy to help you. At this point, please create the setup again with your Ethermine pool. If it isn't working correctly, please start the miner with the Diagnostics button and share the output with me via the contact form below:
https://www.awesomeminer.com/contact

Thanks!

Windows rig? Change network properties from public to privat.

One of my machines (specifically a 1070 eight card rig) keeps having an intermittent issue where AwesomeMiner says "interface offline" but the machine is still working fine. I uninstalled and re-installed the remote agent and the problem keeps occuring.
Any ideas?
No firewall / anti-virus / etc running. Windows 10 ver 2004.
I have three machines and only this one is having this particular issue.

Thanks!

https://i.ibb.co/WtcyXLL/interface-offline.jpg

Hi Joseph and thanks for your question.

I'm not aware how to set Core Voltage (%) like MSI Afterburner. On nVidia 2000-series it isn't supported at all. On the 1000-series nVidia will enforce a number of limits the voltage anyway so you will never get 100% higher voltage even if configured. This is why the nVidia drivers mainly focus on the "Core voltage limit" these days.

What kind of voltage behaviors do you get when you set it to +100% compared to 0% in MSI Afterburner? How does that compare to setting a voltage limit in Awesome Miner instead (at keep the setting in MSI Afterburner at 0%)?

Hi Patrik,

I have a question. I have a few rigs left with nVidia GTX 1080 Ti's and MSI Afterburner and wanted them switching finally to the native overclocking like my other RTX rigs.

In Afterburner the first line is "Core Voltage (%)". I have set this on all cards to +100.

In AM in the GPU overclocking panel I cant find such "Core Voltage (%)". Its only the "Core voltage limit" in the lower advanced section, but I think this setting means I set the real numbers directly, like 1075 mV or 1040 mV or so.
In the GPU Clocking Profiles I can find the same "Core voltage limit (mV)" and "Core voltage boost (mV)". But none of them affect the first line in Afterburner. Is it possible somehow in AM to set that "Core Voltage (%)" to a number between +0 to +100? Without, the hashrate is lower and I really like that option.

Thanks for the answer!

I am having issues where the balance page does not add up correctly - for example, I have 4 litecoin addresses and it shows all 4 with their correct balances however - the total omits one of the balances and thus is wrong.

this issue comes and goes - and with different coins at different times - in an hour the above may be reflected correctly and my bitcoin balances will be wrong instead.

One of my machines (specifically a 1070 eight card rig) keeps having an intermittent issue where AwesomeMiner says "interface offline" but the machine is still working fine. I uninstalled and re-installed the remote agent and the problem keeps occuring.
Any ideas?
No firewall / anti-virus / etc running. Windows 10 ver 2004.
I have three machines and only this one is having this particular issue.

Thanks!