[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[eminer001]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
 
 

   

[Bob-Bit]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
  
 

  

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

[tf2addict]

Does Claymore 11.3 support Cryptonight7?  I thought it does.  AM is disabling selection of Claymore 11.3 when you select Cryptonight7.

[CreamyG31337]

Why was Sumokoin removed from AM?  Because of the upcoming fork?  Will it be added back in afterward?

All coins listed in Awesome Miner is from the WhatToMain main API. In this specific case it looks like the algorithm of this coin was changed, and that by default Awesome Miner doesn't include Cryptonight-Heavy.

I will look at this in more detail for the next update. It should however be possible to manually add this algorithm in the Options dialog.

I'm mining it fine but I'm not sure why it's showing zero for both the estimated and actual revenue.
I had to add this manually but it doesn't seem to have anything wrong:
https://whattomine.com/coins/196.json
And of course cryptonight-heavy is added to the algos, and even though i can't use the defined pools for xmr-stak I have set the coin to that manually.

[Shazam!!!]

Having an issue with AvalonMiner 841 and  Awesome Miner connection with the 841's API.

I set the W:192.xxx.xx.xxx in cgminer, and Awesome Miner can connect. However, every few minutes, it disconnects for a minute.
It reconnects, with 0 hour/min uptime and does so over and over. While I have the API access set, cgminer shows no info, but when
I reset the API to default and disconnect from AM, the uptime is correct. The 841 is running the entire time, showing no disconnection
from my pool.

Should the API access ip be entered differently?

My other miners, not AvalonMiners, are having no issues with AM at all during this issue. My AM is up to date as well. TIA!!!

[eminer001]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
  
 

  

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

They are at 6k miners from below 1k miners just because of us, AM miners that selected zergpool from AM settings.
ZergPool should be aware that as easy it was to skyrocket to 6k they can go back to below 1k if zergpool is removed from AM.
Miners simply had no option because X17 is one of the most popular algos from all pools.
AM's performance and credibility relies on pool's statistics that if they send for 6 hours statistics for X17 that are 10 times higher than any other pool, than AM did nothing to prevent it and is the one that could be blamed also.
Mining works  as a synergy between Awesome Miner and and pools like zergpool. If the pools send statistics that are 10 times higher for 6 hours, than AM's credibility is affected because its lack of protection and users will try to use any other mining software that offers them stability and reliability. For 6 hours, 4500 miners had no protection from AM and mined on a fork and pool administrators did nothing for 6 hours as you can see from everybody's graphs.

[moppidoo]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
  
 

  

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

They are at 6k miners from below 1k miners just because of us, AM miners that selected zergpool from AM settings.
ZergPool should be aware that as easy it was to skyrocket to 6k they can go back to below 1k if zergpool is removed from AM.
Miners simply had no option because X17 is one of the most popular algos from all pools.
AM's performance and credibility relies on pool's statistics that if they send for 6 hours statistics for X17 that are 10 times higher than any other pool, than AM did nothing to prevent it and is the one that could be blamed also.
Mining works  as a synergy between Awesome Miner and and pools like zergpool. If the pools send statistics that are 10 times higher for 6 hours, than AM's credibility is affected because its lack of protection and users will try to use any other mining software that offers them stability and reliability. For 6 hours, 4500 miners had no protection from AM and mined on a fork and pool administrators did nothing for 6 hours as you can see from everybody's graphs.

don't know how it's all AM's fault and all those extra 5k miners are all AM users....but if you think it's ZergPool that was reporting false data, you were pretty wrong, first XVG forked due to the attack, and major pool shuts down to implement the fork etc. and difficulty reported by WTM also coincides with the btc/mh reported by the active pools. Low difficulty, high profit...there's nothing ppl can do with things out of their control. Sorry if the Zerg hasn't been polite in their discord channels, but maybe the other way round not everyone is tolerant being accused of scammers, hash stealers ... etc.

BTW, I don't use any of the online services except NH pretty much as a failover protection only. So I haven't been zerged....point being...if you care about profits so much, you should really be choosing the pools carefully.

Also, don't assume the pools are making profit over this. Did you see MPH's announcement on MUSIC now? as well as other occassions that chainsplit happens at both HashRefinery, Ahashpool...that they displayed good gestures that they still paid for the orphaned blocks that were mined on the wrong chain...As someone who might predict, dear you would not appreciate it at all since you believe that they made so much money off you by all means through your accusations against them all the time. But TBH, they are not obliged to compensate you when sh*ts like that happens...None of the pool ops, SW devs other than XVG team for example, are responsible for attacks on the XVG network in the past days, and yet, would XVG team compensate you? not at all!

***
Back to topic regarding the solution however, you can simply support my suggestion that the implementation of rules based on profit (globally/individuallly) can be actuated. If I can set miners to profit switch when profit falls below certain threshold, who says I can't do it the other way round? when it got absurdly high that I can disable a pool until the coin's stat return to what I deemed "normal".

Support my proposition, this is not the smartest workaround, but it does what you asked...a safeguard that you could define the threshold values yourself and hopefully works while you are sleeping.

[agente]

I think it's important to update claymore to 11.6 for 3gb cards owners.. thanks

[eminer001]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
  
 

  

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

They are at 6k miners from below 1k miners just because of us, AM miners that selected zergpool from AM settings.
ZergPool should be aware that as easy it was to skyrocket to 6k they can go back to below 1k if zergpool is removed from AM.
Miners simply had no option because X17 is one of the most popular algos from all pools.
AM's performance and credibility relies on pool's statistics that if they send for 6 hours statistics for X17 that are 10 times higher than any other pool, than AM did nothing to prevent it and is the one that could be blamed also.
Mining works  as a synergy between Awesome Miner and and pools like zergpool. If the pools send statistics that are 10 times higher for 6 hours, than AM's credibility is affected because its lack of protection and users will try to use any other mining software that offers them stability and reliability. For 6 hours, 4500 miners had no protection from AM and mined on a fork and pool administrators did nothing for 6 hours as you can see from everybody's graphs.

don't know how it's all AM's fault and all those extra 5k miners are all AM users....but if you think it's ZergPool that was reporting false data, you were pretty wrong, first XVG forked due to the attack, and major pool shuts down to implement the fork etc. and difficulty reported by WTM also coincides with the btc/mh reported by the active pools. Low difficulty, high profit...there's nothing ppl can do with things out of their control. Sorry if the Zerg hasn't been polite in their discord channels, but maybe the other way round not everyone is tolerant being accused of scammers, hash stealers ... etc.

BTW, I don't use any of the online services except NH pretty much as a failover protection only. So I haven't been zerged....point being...if you care about profits so much, you should really be choosing the pools carefully.

Also, don't assume the pools are making profit over this. Did you see MPH's announcement on MUSIC now? as well as other occassions that chainsplit happens at both HashRefinery, Ahashpool...that they displayed good gestures that they still paid for the orphaned blocks that were mined on the wrong chain...As someone who might predict, dear you would not appreciate it at all since you believe that they made so much money off you by all means through your accusations against them all the time. But TBH, they are not obliged to compensate you when sh*ts like that happens...None of the pool ops, SW devs other than XVG team for example, are responsible for attacks on the XVG network in the past days, and yet, would XVG team compensate you? not at all!

***
Back to topic regarding the solution however, you can simply support my suggestion that the implementation of rules based on profit (globally/individuallly) can be actuated. If I can set miners to profit switch when profit falls below certain threshold, who says I can't do it the other way round? when it got absurdly high that I can disable a pool until the coin's stat return to what I deemed "normal".

Support my proposition, this is not the smartest workaround, but it does what you asked...a safeguard that you could define the threshold values yourself and hopefully works while you are sleeping.

What do you think ?
When all the other 4 pools have no issue, and when zergpool has this issue for 6 hours making 4500 miners loose all for 6 hours, it's something from bad management of the pool, right ?
Also AM should implement a protection against this type of  behavior from pools, right ?

[patrike]

where is the button to add a bat.file

ccminer -a x16r  -o stratum+tcp://cryptopool.party:3636 -u RSb332DHgAdb3v5qasj1MEbUtYBRc8Szmb.1060com -p c=RVN,d=12 -i 21 
pause

where to write the second line pause?!

-i 21 & pause
not worket!!!

What you need here is one pool (the New Pool button) where you specify something like:
URL: stratum+tcp://cryptopool.party:3636
Worker: RSb332DHgAdb3v5qasj1MEbUtYBRc8Szmb.1060com
Password: c=RVN,d=12
You can also go to the Command Line section and add "-i 21"

Then you create a Managed Miner, where you select mining software for X16r algorithm and select the pool you added:
http://www.awesomeminer.com/help/managedwizard.aspx

What is the purpose of the pause command? If you need to troubleshoot a miner, please use the Diagnostics button in the toolbar.

[textb0ok]

There seems to be a real problem with X16r.

Every morning I wake up and my most profitable rig is not mining anything at all, because it was mining X16r and then it just stopped overnight and did not start mining anything else.

I am losing a lot of profit because of this.

PLEASE FIX...

[patrike]

Also, an unrelated feature request - and I hope this is something simple to implement. Please make the columns customizable for the compact list. I dont particularly care about accept/reject stats, but there's a lot of other information in the summary tab that I'd like constantly displayed near each miner - such as the windows uptime, miner uptime, software being used, the worker/pool, number of GPUs active, individual GPU temps/fan/hash, etc. When I maximize the window the majority of the main window is whitespace, and I have to constantly click each miner to find out simple information like windows uptime. I just want to be able to tell at a glance which machines have low uptime so I can identify the unstable ones. Or I want to know which wallet its mining to at a glance, or which rigs/profiles I didnt configure to use a new software, etc.

And you really, really need to be able to make it possible to ctrl-click miners in different groups. I manage multiple mining farms and I have to keep them in groups so each client can only see information pertaining to their own miners. But when I want to upload new software, apply templates, start/stop miners etc - I have to literally do everything 5 times. Especially when stuff like uploading custom software locks the UI, when you have 50+ miners to update but you can only do 10 at once, I have to constantly babysit it. Something that I could have clicked once, walked away and came back a few minutes later when its all done instead takes a very long time because I have to wait for one to finish to start the next. If I didnt have them in groups I could do this with ease, so I'm between a rock and a hard place. To a lesser extent this is also a problem with the benchmarking - you've been good about adding new software, but in order for me to know whether this software is worth using I need to bench it. We have profit profiles because every software gives different results on every hardware - so obviously I need to bench it separately for each profile. That wouldnt be a big deal if I could bench all 8 of my profiles simultaneously on 8 different rigs, but instead its another thing that takes over an hour of work to do correctly because it locks up the entire UI and I have to go one by one.

Both of these related issues can be incredibly frustrating because kind of the whole point of AM to me is that it makes managing large farms far more practical - but actually using AM with large farms is an exercise in frustration because of UI/UX decisions that result in SO MUCH manual busywork! It may make managing the farms possible but it also makes it so aggravatingly time consuming that I'll be honest, I'm still constantly looking for alternatives to AM that offer a similar level of configurability but require less time and have more informative/flexible UIs. Like AM has great features, but the UI actively makes me not want to use those features because it takes so long to accomplish simple things.

Please check out this feature that allow you to customize the content of the Progress field:
http://www.awesomeminer.com/help/customizefield.aspx
You can get Windows uptime, miner update and a number of other values. If there are specific fields you miss, like more GPU related information, I can simply expose that as well.

I will enable multi-select of miners across different groups in the next release. It's a very small change and hopefully it will make the experience better for you.

I will also make the benchmark dialog non-modal, making it possible for you to have it running while you continue working with the Awesome Miner main window at the same time. This also makes it possible to benchmarks to different miners at the same time.

Thanks for all feedback.

Absolutely fantastic! I really appreciate your responsiveness to user requests.

Regarding the progress field customization, I'm a coder myself and I tried to achieve this myself a while back, but I found that the documentation of the objects and methods for the C# scripting was somewhat lacking and I couldn't figure it out. I also exclusively use the compact view and it didnt appear to function in that view anyway.

The Customize Progress dialog allows configuration for both the List and Compact List modes. Please let me know what information field that you think I should add to this feature, like GPU fan.

[patrike]

Does Claymore 11.3 support Cryptonight7?  I thought it does.  AM is disabling selection of Claymore 11.3 when you select Cryptonight7.

The very latest development preview (4.6.7) should automatically add the flag for CryptonightV7. Can you please verify?

[patrike]

I think it's important to update claymore to 11.6 for 3gb cards owners.. thanks

Claymore 11.6 is included in the development versions of Awesome Miner, and will also be part of the next official release during next week.

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

[patrike]

Bug v4.6.5 (perhaps in the previous 2 releases ase well
=====

Most of the remote miners will show interface offline error (some green text, some with red text) when you have option window/profile editor opened for a little while (leave it for 3 minutes and it surely kicks in)

The miners are actually still online and API are accessible and so on, just AM not seem to probe, reading them properly while the Options Window is opened so might be an issue with Remote Agent in the latest builds

Just to make sure, is it "Service Offline" as in Awesome Miner is unable to connect to Remote Agent, or "Interface offline" as in Remote Agent is unable to connect to the API of the running mining software?

I wasn't able to reproduce this one. I simply opened the Options dialog and waited for a while. Do you know if there are any additional steps I need to take here?

Can you check the following points as well?
1) Verify that the same version of Awesome Miner and Remote Agent is installed. Mixing versions are not supported and may result in miners being stopped or not started correctly
2) Verify that only a single Awesome Miner main application is connected to the Remote Agent application. Two Awesome Miner applications cannot connect to the same Remote Agent
3) Verify that the remote host is only added once in Awesome Miner. Open the Options dialog, Managed Hosts section and verify that no duplicates exists.

I will investigate any changes in the recent versions that might be related as well.

Update:

I was able to take note on what I was doing when it happens a few more times today, so the symptoms are:

(almost) all miners display "Service Offline", but the stats keep updating for majority of them

Only happens when I have sub-dialog open within the Options...so once I was configuring pool groups in the pools Dialogue

The other times, I was in the middle of creating / editing rules and had the editing dialog open for some time.

Best Regards,

Just in case anyone else also run into this issue - I've managed to find the scenario and made a correction for it in development version 4.6.7.

[patrike]

Having an issue with AvalonMiner 841 and  Awesome Miner connection with the 841's API.

I set the W:192.xxx.xx.xxx in cgminer, and Awesome Miner can connect. However, every few minutes, it disconnects for a minute.
It reconnects, with 0 hour/min uptime and does so over and over. While I have the API access set, cgminer shows no info, but when
I reset the API to default and disconnect from AM, the uptime is correct. The 841 is running the entire time, showing no disconnection
from my pool.

Should the API access ip be entered differently?

My other miners, not AvalonMiners, are having no issues with AM at all during this issue. My AM is up to date as well. TIA!!!

Are the miners on the same local network? If not, it might be that you need to increase the API connection timeout a bit. Even if on the local network, it could be that these Avalon miners are a bit slow in their responses sometimes. Please go to Options dialog, Advanced section and increase "Miner API connection timeout".

[patrike]

Awesome Miner version 4.6.7 (Development preview of 4.7)

- Benchmark feature improved to benchmark and compare multiple mining software using the same algorithm
- Benchmark can run without preventing access to the user interface
- Adjust profit calculations for Yiimp-based pools to actual performance based on past payouts compared to estimates. Configured in Options dialog, Statistics section.
- Added Notes tab at the bottom of the screen to allow any notes to be entered for the selected miner
- Updated user interface for mining software selection
- Updated miner list to allow selection of multiple miners from different groups
- Added buttons to select all or unselect all algorithms in the Properties of a Profit Profile
- Variables for IP addresses in pool worker names supports padding of leading zeros for each segment of the IP address
- Added context menu to copy MAC address of miner on the Summary tab
- Offline detection trigger allows for longer offline duration to be configured
- Updated pool URL's for Mining Dutch
- Performance optimizations
- Support running as a 64 bit application on 64-bit Windows
- Added new algorithms: X16r, X16s, Cryptonight-Lite and Cryptonight-Heavy
- Added mining software: Sgminer X16r for X16r algorithm
- Added mining software: RavenMiner for X16r algorithm
- Claymore Dual Ethereum Miner 11.6
- Claymore Cryptonight Miner 11.3, including CryptonightV7 support
- Claymore NeoScrypt AMD Miner 1.1
- Bminer 6.1
- CastXMR 0.9.2
- PhoenixMiner 2.8c
- Correction to Verify Password for Cloud Services configuration
- Correction to Unicode encoding for sending messages via SMS and Telegram
- Correction to the batch file execution configured to be running before the miner is started
- Minor corrections

The items in blue have been updated since the previous development preview two days ago. There are also a few additional corrections in this release.

Development versions are intended for users that want to try the latest features before they are made available in the official releases. Development versions are not intended to be deployed at large scale as they have not been tested as much as the official releases. Please make sure that both Awesome Miner and Remote Agent are upgraded to the same version. Also note that once upgraded to a development preview, it isn't possible to downgrade to an older version.

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates

Direct download links if needed:
http://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
http://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

The plan is to release the official version 4.7 during next week.

[patrike]

Patrike,
I have a question for you and anyone else who can help.

Yesterday night 4500 miners lost 6 hours of mining on all rigs on ZERGPOOL that was added last month by Patrike in default configuration. see: https://bitcointalk.org/index.php?topic=2759935.new#new

The issue we all have is that Awesome Miner does not have any protection against this type of problem, when X17 algo, an algo that has almost NO VOLATILITY, suddenly increased profitability by 10 times, from 1 to 15k.

I think that Awesome Miner can implement an option to protect miners from forks by saving average volatility for a coin/algo by storing the min & max values for profitability and computing volatility. If the algo exceeds double of previous maximum  profitability AM can send a warning message of a possible FORK and if it exceeds 3 times the maximum previous profitability it can disable that algo for a number of minutes (all parameters can be configurable). Something similar to the functionality we have in AM to disable pools without accepted shares for a number of minutes.

When users told ZERGPOOL moderators on Discord channel about the issue that they had for 6 hours and about their loss, the moderators from zergpool Discord channel started swearing and said that it is only miner's fault that miners did not disable X17 / XVG, but miners said that it was pool's administrator responsibility to disable the coins with problems, because miners can't monitor 180 coins all the time, that's why miners pay the pool fee, right ?

Patrike, I do think that zergpool went from 1k miners to 6k miners only thanks to you, it happened when you was kind and added their pool to default AM configuration. We, the miners and users who selected zergpool from AM's configuration feel that the pool does not respect us when they are talking with a lot of bad words to us ans swearing us when we told them that they did nothing for 6 hours the Discord channel moderator answered on their Discord channel (please check) this "phear - Today at 11:19 AM : you just spreading sh*t on ventilator" .  I do think it's not fair to be treated with such lack of respect from their end after we informed them that they should disable XVG from their pool. We, the 4500 miners from zergpool at that time on x17, lost 6 hours of mining and we deserve some apologies at least, because we had thousands of rigs loosing money, not them.

Patrike, can you please send them a message, because you added that pool on AM's default configuration, and you can remove them from AM, and you helped them to have so many miners, miners that are AM's miners, miners that deserve respect from their end,  maybe they will understand that at least we deserve some respect and we do not deserve to be sweated like that.

Thank you very much, I hope you understand us, we spent a lot of money to buy the RIGs.
  

I understand your frustration, but you should just deselect Zergpool yourself from your list if they have crossed a line for you. I don't think it should just be removed from Awesome miner. Some people may only be using it for a couple algorithms, (and they may be ones you don't even use) but those people may really want it as an option. I'd like to see MORE pools added (Blazepool, and Yiimp pool for starters) Even if you hate a pool and never want to use it, it will help you to have it in the list because other people who do have it selected will switch to that pool, leaving less miners at the pool that you DO prefer, and also, everybodys miners won't all go to the same place at the same time if there are more pools available.

They are at 6k miners from below 1k miners just because of us, AM miners that selected zergpool from AM settings.
ZergPool should be aware that as easy it was to skyrocket to 6k they can go back to below 1k if zergpool is removed from AM.
Miners simply had no option because X17 is one of the most popular algos from all pools.
AM's performance and credibility relies on pool's statistics that if they send for 6 hours statistics for X17 that are 10 times higher than any other pool, than AM did nothing to prevent it and is the one that could be blamed also.
Mining works  as a synergy between Awesome Miner and and pools like zergpool. If the pools send statistics that are 10 times higher for 6 hours, than AM's credibility is affected because its lack of protection and users will try to use any other mining software that offers them stability and reliability. For 6 hours, 4500 miners had no protection from AM and mined on a fork and pool administrators did nothing for 6 hours as you can see from everybody's graphs.

don't know how it's all AM's fault and all those extra 5k miners are all AM users....but if you think it's ZergPool that was reporting false data, you were pretty wrong, first XVG forked due to the attack, and major pool shuts down to implement the fork etc. and difficulty reported by WTM also coincides with the btc/mh reported by the active pools. Low difficulty, high profit...there's nothing ppl can do with things out of their control. Sorry if the Zerg hasn't been polite in their discord channels, but maybe the other way round not everyone is tolerant being accused of scammers, hash stealers ... etc.

BTW, I don't use any of the online services except NH pretty much as a failover protection only. So I haven't been zerged....point being...if you care about profits so much, you should really be choosing the pools carefully.

Also, don't assume the pools are making profit over this. Did you see MPH's announcement on MUSIC now? as well as other occassions that chainsplit happens at both HashRefinery, Ahashpool...that they displayed good gestures that they still paid for the orphaned blocks that were mined on the wrong chain...As someone who might predict, dear you would not appreciate it at all since you believe that they made so much money off you by all means through your accusations against them all the time. But TBH, they are not obliged to compensate you when sh*ts like that happens...None of the pool ops, SW devs other than XVG team for example, are responsible for attacks on the XVG network in the past days, and yet, would XVG team compensate you? not at all!

***
Back to topic regarding the solution however, you can simply support my suggestion that the implementation of rules based on profit (globally/individuallly) can be actuated. If I can set miners to profit switch when profit falls below certain threshold, who says I can't do it the other way round? when it got absurdly high that I can disable a pool until the coin's stat return to what I deemed "normal".

Support my proposition, this is not the smartest workaround, but it does what you asked...a safeguard that you could define the threshold values yourself and hopefully works while you are sleeping.

What do you think ?
When all the other 4 pools have no issue, and when zergpool has this issue for 6 hours making 4500 miners loose all for 6 hours, it's something from bad management of the pool, right ?
Also AM should implement a protection against this type of  behavior from pools, right ?

Once I get the current development release done and released as v4.7 I will start investigating how Awesome Miner can be improved to detect more of these pool related issues.

I agree that Awesome Miner should be able to analyze and find pools that are reporting unrealistic numbers in terms of profitability. Please keep in mind that when you mine on Zergpool and similar, Awesome Miner may not have full insight in the coin details of what you are actually mining. The profit information is however always known.

[CryptoLocalATM]

not have an version for linux?

[patrike]

There seems to be a real problem with X16r.

Every morning I wake up and my most profitable rig is not mining anything at all, because it was mining X16r and then it just stopped overnight and did not start mining anything else.

I am losing a lot of profit because of this.

PLEASE FIX...

Has the mining software crashed multiple times? If crashed, it will be noted on the Notifications tab and you will see what mining software, algorithm and pool that was active then the crash happend. By default Awesome Miner will restart a crashed mining process, but if it fails too many times within a few minutes, Awesome Miner will give up. You can configure how many times Awesome Miner should try to restart a miner with frequent crashes in the Options dialog, Advanced section: "Restart attemps on process crash".