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

Have a Ryzen 1700X overclocked at 4ghz, with xmrig on awsome miner i get 450h/s, but when i mine with xmr stack i get 640h/s xmr stack use 15 threads.

I have updated my rigs to the latest but I am still having that silly issue with Mining Dutch.

If I have all of my pools enabled and the most profitable algo becomes skein on Mining Dutch, then for some reason Awesome Miner starts mining x11 on Mining Dutch, and only on Mining Dutch.

I had to disable skein and x11 on Mining Dutch to deal with the problem 

graphics just put appropriate image file in %appdata% AM folder as BTCP.png

coin isn't listed in the whattomine coins.json, you have to add it yourself if haven't done so, no need for external program unless whattomine info is borked (such as LUXcoin)
http://whattomine.com/coins/230.json

Patrike, BTCP included by default in the 4.7.3?  How is it shown?  I doesn't exist in the coin listing, I can't select it and add it as a pool coin, etc?

Do tell?  Cuz I mine this all the time, and have been using the external api program to pull in the data

UPDATE: are you just talking about the coin graphic, because indeed that works now, but the coin isn't listed in any listing until I ran the external api program that pulls the data

Patrike:

Any new updates on you checking into the code of NemoMiner to improve the profit switching of AwesomeMiner?

The reason i ask is im nearing my 2 month mark of running 1 GPU on AM and 1 GPU on NM from the same watercooled PC using the same miners per algo comparison test. The margin of actual payout between the 2 wallets has grown wider.....

@patrike

suggestion: like we add pool on yiimp base in Online service, to be able to add the balances of this pools or other pools with API

Great software, great work!!!

It's even better than before.. because MPH has all of pools SSL but not all software supported it.. Now we can manuali select whitch algo uses SSL and whitch not
Best feature

Is it possible to verify from the Awesome Miner log file (toolbar: Tools -> Log File) if Awesome Miner is sending any clocking commands to MSI Afterburner? Search for "Executing GPU clocking command".

Prohashing is very special as it uses the password field to specify algorithm information, and the Pool URL is always "prohashing.com:3333" no matter of what is being mined. Because of this special design of prohashing, it's not possible for any software to look at the Pool URL and see which coin or algorithm is being mined - all of them look identical. This is a major drawback in the design of prohashing and it will for that reason be difficult supported with profit information from Awesome Miner. I'm not saying that's impossible, just that this pool has a special design that doesn't work well with any management application.

In the latest release I added a feature when you can set URL prefix (like ssl://) for each entry in Options dialog, Online Services. This should be a more flexible solution. Please let me know your feedback on this.

Thanks for your feedback. Setting Profit Factor to 0.001 should have been the solution. It can be set per entry in the Options dialog, Online Services section and will only be applicable for that pool. You may have to hit the Update Now button in the Online Services tab and wait a moment before the numbers are updated.

When adding some custom pools, Awesome Miner simply doesn't know the unit the pool uses, and that's why it you sometimes get 1000 times too large numbers. When these pools are reporting profitability, it can look like "0.00123" when Awesome Miner get the information. But for some algorithms this indicates BTC/MH/s while it represents BTC/GH/s for others - and there is no way of telling from the numbers.

This is also the reason why whenever there is a change at the pools to report in GH/s instead MH/s, the profit numbers becomes incorrect in Awesome Miner and I need to release a new version to adjust to it. In a perfect world, the pools would tell which unit (MH or GH) there were reporting in, but that's not the case.

Blazepool is also included by default in the latest release.

The indication with gray text is just a way for Awesome Miner to indicate what mining software it thinks you can use for a specific algorithm. You can still select XMR-Stak even if it's gray - it's not disabled.

I will update the next release to not make CNv7 gray for XMR-Stak.

It's correct that if you have mixed cards, you need to define several profiles, and then one group profile to bring them together and specify which GPU (either by name or ID) that should get the different profiles you defined.

You can define that a clocking profile (or group) should be applied when a miner is started to stopped. For a Managed Miner, you define this in the Properties of the miner, GPU Clocking Profiles section. If you are using the profit switcher, this can be configured in the Edit Profit Profile dialog, where you for each algorithm in the list can define a profile to use when starting and stopping.

There are probably many opinions on this. In general, Current should be the best, but it can result in a little higher estimates than what you actually get paid for.

Awesome Miner version 4.7.3

- Predefined Online Services can be configured with a custom URL prefix, to support ssl-based URL's
- New pool for Managed Profit Switcher and profitability information: Blazepool
- New pool for Managed Profit Switcher and profitability information: Block Masters
- Fan speed trigger configurable to also trigger on too high fan speed
- Bitcoin Private (BTCP) coin information included by default
- XMRig parameter for donation level made configurable via Managed Software settings
- Adjust to new Mining Dutch Nist5 unit reporting

It's important to upgrade Awesome Miner Remote Agent to the latest version as well.

i see there is 4.7.3 update and also want to know whats the best option to mine using online services static settings: Current, 24 hour avarage estimate or 24 hour avarage actual?

I've read through the GPU Clocking page and am unable to find how Clocking Profiles Groups are applied.  I'm assuming I can create the profiles and apply it to a specific rig and it will set the various OC settings since it's a mixed-card rig?  Am I understanding this feature wrong or how do I go about applying the profile groups I created?

Hi Patrike,

just a suggestion, would it be possible to add a way to bulk enable/disable (maybe via context menu or checkboxes) pools on the Options->Poos window? basically on a global scale and not just individual pool groups. Since you can already filter pools via that window, it is very handy when a particular pool/multipool is down and you don't have to manually go and scroll through a list of pools in each pool group to disable them and when pools are back up and running, you don't have to go through the same chore...

(example, right now BSOD.pw is down, I had like 10+ various coins through the pool...double that by factor of 2 since 2 pool groups, makes it...a bit of a pain to scroll and tick/untick just for the next few hours till it's back up again, I'm not sure exactly how failover works or if it works well at all with ccminer...last I tried, I had difficulty even getting priority working, I know the tooltip says failover/priority only works on cgminer/sgminer so I'm not surprised it doesn't quite work here)

Of course, another way is to avoid pools without accepted shares for x hours which is already available, but I was weary that it might be too aggressive (weak rigs, shabby internet so haven't figured out optimal difficulty for all algos) and besides, it's at least an alternative dealing with these occassional pool instability issue(s).

Hey guys,

I have a Ryzen 7 1700 hashing at approx. 270kH/s on M7M in HashRefinery. Although the hash rate reported in AM (4.7.2) matches the one reported on HashRefinery, the payout seems to be way off: AM reports approx. 10 times higher. Any suggestions?

You have 8 cores/16 threads and 16MB of cache. Cryptonight likes 2 megabytes of cache per thread and as such 8 threads used is normal for a Ryzen 7. What hashrate are you getting?