Patrick, can you suport Xmrig ? i cant have it to run... Must we config anyting? i checked the treads detected and they are fine but always geting cuda error... and it dont start mining.

I tested Nicehash aplication with current gpu clocks and it works fine. 2.2Khs on my 5 GPU

Also can you give suport for escavator 1.5? that would work.

Starting Diagnostics. Awesome Miner version: 4.7
Starting Mining Software
Setting up Miner Engine. Instance: 3
Engine Type: XmRigNvidiaMiner, Auto Download: True, EnginePath: C:\Users\migue\AppData\Local\AwesomeMiner\xmrig-nvidia-2.5.2_2\xmrig-nvidia.exe, Subtype: Disabled, CustomExecutable:
Set clocking start profile: 4, ETH Rig1 (when stopping, the following will be used: -1, type: Single, Use: False)
Added rule for: C:\Users\migue\AppData\Local\AwesomeMiner\xmrig-nvidia-2.5.2_3\xmrig-nvidia.exe
C:\Users\migue\AppData\Local\AwesomeMiner\xmrig-nvidia-2.5.2_3\xmrig-nvidia.exe  -o stratum+tcp://cryptonightv7.eu.nicehash.com:3363 -u 36UA5oFjrKkf7AodthsMA4ZrhPtHgM5txE -p x --api-port 4030    (WindowMode: ConsoleFormat, EngineType: XmRigNvidiaMiner, IsProfitMiner: False)
Configuration:

Mining Engine Process started, PID: 11620

====================================================================================================
>  * VERSIONS:     XMRig/2.5.2 libuv/1.19.2 CUDA/9.10 MSVC/2015
>  * CPU:                  Intel(R) Core(TM) i3-3240 CPU @ 3.40GHz (1) x64 -AES-NI
>  * GPU #0:       GeForce GTX 1060 3GB @ 1784/4004 MHz 26x27 6x25 arch:61 SMX:9
>  * GPU #1:       GeForce GTX 1060 3GB @ 1759/4004 MHz 26x27 6x25 arch:61 SMX:9
>  * GPU #2:       GeForce GTX 1060 3GB @ 1759/4004 MHz 26x27 6x25 arch:61 SMX:9
>  * GPU #3:       GeForce GTX 1060 3GB @ 1784/4004 MHz 26x27 6x25 arch:61 SMX:9
>  * GPU #4:       GeForce GTX 1060 3GB @ 1759/4004 MHz 26x27 6x25 arch:61 SMX:9
>  * ALGO:         cryptonight, donate=5%
>  * POOL #1:      cryptonightv7.eu.nicehash.com:3363
>  * API PORT:     4030
>  * COMMANDS:     'h' hashrate, 'e' health, 'p' pause, 'r' resume
> [2018-04-09 17:59:21] use pool cryptonightv7.eu.nicehash.com:3363 159.8.13.236
> [2018-04-09 17:59:21] new job from cryptonightv7.eu.nicehash.com:3363 diff 100001
> [CUDA] Error gpu 1: <cryptonight_extra_cpu_final>:277 "the launch timed out and was terminated"

====================================================================================================
Unexpected exit of mining software. Possible cause: Incorrect configuration
Diagnostics completed

lots of HW Error. shows not the correct speed. 380kh/s.
6RX480 8Gb. there must be a minimum of 42Mh/s

Thanks. Finally I managed to do what I wanted by editing custom profiles.
I have another cuestion. Is it possible to set up a new pool without a coin asociated? And add it later, or choose between some.
As fas as I've seen, there is no way to link coins and wallets, isn't it?

6xRX480 "x16r" sgminer on zergpool, does not work.
help

Hi patrike. I think I'm experiencing a bug in the latest version. I'm trying to mine CryptonightV7 with nVidia GPU's but I can't get the benchmark going.
Here are the steps I've taken. in the setting I've enabled the CryptonightV7 algorythm. In managed software I enabled XMRig nVidia Miner 2.5.2. In the nVidia GPU profit profile I do see the CryptonightV7 algorythm and the XMRig nVidia Miner mining software is enabled too.
Still when I go to the benchmark menu CryptonightV7 is not there. I've also tried to point AM to manually downloaded miner to no avail. Any help would be greatly appreciated.

EDIT: just for testing I tried configuring Cryptonight-Lite and it IS showing up in the benchmark menu! So there is definitely something werid going on.

Thanks for answering. Finally I followed a video someone suggested in another post and could make ir work.
Another question... I've seen that free version allows a maximun of two miners. Do I need to set up a miner for each coin/pool pair I want to mine?
Or may I choose different pools / coins before starting a miner

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...

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 ?

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!!!

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,

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

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

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.

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!!!

Since the latest development release v4.6.6, it is no longer possible to monitor stats from Excavator v1.4.4a as AM shows "Interface Offline".

Hello Patrike, I Got 4.6.6 Version with some remote miners (agent updated to 4.6.6 too) configured in profit miner.

Sometimes, when one of my miners  (still the same) switch to Ethrereum with Claymore,  the Awesome Gui shows me the "interface offline" message.

I configured "claymores dual ethereum miner"  section in the profit switching profile  with command line options -platform 2 -mport -4028 (to get read only management)

Looking at the agent log I noticed some errors; i would like to know if it could be related with interface offline error i get.

05/04/2018 11:20:25.120 [008] [ManagedMiner#8 - Test Profit Miner -Rigo2] Configured command line:
-platform 2 -mport -4028
05/04/2018 11:20:25.448 [008] Saving configuration to: C:\Users\Rigo2\AppData\Roaming\AwesomeMinerService\ServiceData.xml.tmp
05/04/2018 11:20:25.464 [008] --> C:\Users\Rigo2\AppData\Roaming\AwesomeMinerService\ServiceData.xml
05/04/2018 11:20:25.464 [008] [ManagedMiner#8 - Test Profit Miner -Rigo2] Mining Engine Process started, PID: 8000
05/04/2018 11:20:30.058 [014] [E]Failed to process API request (time: 1016 ms): {"id":0,"jsonrpc":"2.0","method":"miner_getstat2"}
Impossibile stabilire la connessione. Rifiuto persistente del computer di destinazione 127.0.0.1:4028  (  Traslation: Impossible to establish connection. Persistent Deny Destination Host 127.0.0.1:4028)

P.S  127.0.0.1:4028  was  correctly reacheable via browser

Thank you in Advance

Massimiliano

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.

This is definitely a great step - its good to have this information, however it begs the question of how to properly use this information.

I've never thought the pools were necessarily stealing or anything, just that the delay between the mining and exchange and the occasional difficulty spikes and drops accounted for most of the variation between them. So looking over the instances where all the pools are mining the same algo, there isnt a clear pattern where one pool has consistently better performance than the other.

Anyway, from the description given, it sounds like all AM is doing is taking the reported 24hr actual, the reported 24hr estimate, and then comparing the two over time to give a score for how close the estimate is getting to the actual.  

If this is correct, there are then two obvious questions:

First...this feature was highly requested because of mistrust of the pools. If all that's being done is comparing statistics reported by the pool, does this really solve the problem? How do we know the pools are actually reporting an honest 24/hr estimate or actual?

Second - what does this say about which option we should choose now? Does this correction factor modify the reported actual rate to come to a theoretically more accurate estimate - meaning that we should now choose actual to get this more accurate estimate? Or does it correct the 24hr estimate to a now more accurate estimate - meaning that we should choose 24hr estimate? Or is choosing current more viable now, because the stats collected by AM now account for the variation - so if a coin is being reported as currently being super profitable, if it remains more profitable after the AM correction, it's probably legitimate and worth taking advantage of?

Overall I think it would be helpful if you could be more specific about how this calculation is made, what the time window is, etc. It's a step in the right direction but it's not really clear at all how to best take advantage of it.

Also, along the same lines, I think it would be potentially even more useful if AM were to calculate some sort of variance factor for pools/algos - in other words how much profitability varies throughout the hour/day. There are some coins/algos that are very stable, and some that constantly fluctuate between high and low profitability on what seems like a minute by minute basis. I've had to disable a few algorithms simply because they keep causing constant switches for no good reason. Even with a 1 minute interval, I could watch revenue go from an extremely high number to a ridiculously low one. It'd be nice to put a number on that so I could have some data as to which algos/pools are too inconsistent to be worth my time. I want to be mining the most profitable coin I can be at any given time - and 24hrs is too long a time window for most of the coins on yiimp pools.

This information is critical because these pools are reporting averages, and outliers throw off averages. (Using simple and unrealistic numbers to make the point) Two algos could report 10 mBTC/GH for 24 hours - but one could be getting to this number by being within +/- 5% of 10 mBTC/GH for 24hrs straight, and the other could be .01 mBTC/GH for 23.9 of those hours with a few minutes or even seconds of 1000 mBTC/GH every day. Mining the latter is a waste of my time when even a 1 minute interval leaves my miners on the wrong side of that for up to a minute - those minutes add up when you've got lots of algos acting like this. I mean I certainly wouldn't want to use 24/hr estimates or averages if it meant my miners were potentially making nearly nothing 99% of the time and hoping that 1% of extreme profitability actually delivers enough to make up for it.

Anyway, this is still good data once it's clear what to do with it. Eventually I'd hope for it to get to a point where AM can identify between consistent earners and inconsistent earners, and use that information to help us exploit legitimate profitability spikes while mitigating the harm of profitability drops. Even something as simple as the profit switching being much more responsive and cutting a poor earner off early would be useful. Like as far as I can tell the stats update and switching intervals are not even in sync - there is absolutely no good reason it should continue to mine something for another second when the stats update showed profitability fell off a cliff, but there's still up to a minute left before it hits the switching interval and does something about it.