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

It's true that Awesome Miner is based on the cgminer/bfgminer/bmminer/sgminer API for this. All these have a concept of devices, and in some cases there can also be operations performed on these devices (which is why it can be a bad idea to make up devices that wasn't originally reported by the miner itself).

It's not at all impossible to modify for the API from this specific miner, but it's a different implementation and an effort that is required.

There are unfortunately no API or extensions for this.

Right now Awesome Miner is simply comparing the actual and estimated payout values from the pool API's. That's currently not possible for Nicehash and MPH.

What has been discussed earlier is if Awesome Miner can look at your own payout from the pool, but it can be a bit difficult to measure that in an accurate way.

Let's focus on finding the scenario where this can happen. I wasn't able to reproduce it.

Which version of Awesome Miner are your running? Is the benchmark on a the local computer or a remote miner? Could you send me the log files?

Hello. I just had an Antminer S9 delivered, I hooked it up, mining on Slushpool, then followed the directions for API access, and that all went smooth. The only thing I'm having an issue with is "Define coin" I can select it and a drop down comes up and it says "User defined" and "Unspecified", but it won't let me choose either. I hover over user defined and left click, but nothing happens. Thanks for any insight anyone might have.

In the benchmarking screen it shows Claymore Dual miner.... but instead of opening Claymore it is opening Phoenix miner, why?

I do not have anything changed with Claymore or Phoenix, the miner is doing this all on it's own.

It really is starting to feel like every time you update AwesomeMiner you add new features and break something else.


Edit: Even when I point Claymore to the actual EthDcrMiner64.exe AwesomeMiner STILL opens Phoenix miner!!!! How is that even possible? It's like AwesomeMiner is literally fighting me...

hi Patrick

This is really brilliant and is already giving some interesting information, are there any plans to collect statistics for NiceHash and MiningPoolhub?

Thanks

Patrike,

How about this, is there an extension to the API such that I could externally parse the cgiminer log and push data to AM that could be displayed in the GPU/ASCI/etc area as individual miners?  I'd be up for that if that's an easier approach - perhaps there are other benefits as well, dunno.  I'd forgo the ability to set triggers, etc as long as I could see the data in one place.

Thanks! This feature is implemented in the Awesome Miner cloud servers, where I currently collect statistics from Zpool, Zergpool. AHashpool and HashRefinery every hour. Then it's being processed and a percentage value is calculated.

What's good is that you don't have to run your own Awesome Miner for a period of time to collect this data yourself. I can also make changes and optimizations and everyone will get it right away. Because I store the original pool statistics in the cloud all the time, any new calculations can use all old pool statistics as well.

I'm very much open to any feedback and discussions about how to improve this. At least the infrastructure for the feature is in place now.

Awesome Miner just sends a number (like 2) to the mining software for benchmarking. The GPU name in Awesome Miner may not be correct here and I've actually considered not displaying it at all. It's then up to the mining software to use the GPU based on this number. Please note that some mining software also change their ordering of GPU's between their releases, which also could be the reason for the change.

awesome!

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.

Can I offer an interpretation of the above, you probably implemented the AntMain miners first which caused a specific approach to reporting ASIC miners.  The Avalons are different in that one controller can support up to 20 miners.  Both AntMain and Canaan use the same version of cgminer and both support the same cgminer api.  You just use a different set of variables to pull the antmain data and that would have to change which may be more work that you have available time for currently...

how did I do? ... thanks for at least responding... in my mind, you report one, and you have the mechanism to display GPU's so I thought A+B might be relatively easy to implement C.

But thanks again for the great product and I did buy the premium version because I like it so much, I'm just looking for one *console* for both GPU and ASIC mining is all, and it's *SOOOOO* close there

Looks like GPU order is broken in latest version, at least in 4.6.3. I have 3 1080 cards + 1 is 1080 Ti. When i go to benchmark window, i see all 4 cards GPU0-GPU3 and GPU2 is 1080 Ti. When i run benchmark for GPU0 using AM benchmark window, i see that miner is reporting GPU as 1080 Ti, but i'm benchmarking GPU0, not GPU2! Did not had this happen before.

Awesome Miner version 4.6.6 (Development preview of 4.7)

- Benchmark feature improved to benchmark and compare multiple mining software using the same algorithm
- 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
- Added buttons to select all or unselect all algorithms in the Properties of a Profit Profile
- 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 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
- 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

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

I fully understand your request. The difficulty here is that this miner reports it as one or few ASIC devices, and then there is some non-standard way of reporting more temperatures per ASIC device. It would be possible for Awesome Miner to handle this, but it would require some ugly implementation to fake more devices than what is being reported by the miner. These miners are not really standard compliant in terms of temperature reporting per individual device.

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

Patrike,

I'm going to take a run up this hill one more time.

I would be so awesome if AM could just display all the Canaan avalon miners like it does GPU's on a single rig.



There are 2 currently can be up to 20 on that ASIC rig, all of the data is in the cgminer log/api as well as AM api (in the stats section), the MMCount is the number of miners in the rig, and the MM  IDX is the specifics for each miner, the TEMP[], TMax[], Fan[], GHSmm[] WU[] numbers are for a specific miner.

I'd even be up for trying this via an alternative way if that exists?  C# script maybe?

fingers crossed you'll consider the request.

Thanks in advance, and happy to help with data/testing etc.

Many thanks for all details. I do get your point here.

Thx for the reply Patrike, I tried the profitPerDayValue, but it only displays the profit value that the miner is currently actively running. The idea would be that I can set Rule Based actions on what's being calculated (updated) before the switching interval kicks in. Both Globally (on all miners) and Individual Miner. I have done the global workaround via Excel and it's working great (albeit extremely amateurish in the implementation)

Example would be...that:

The Global Switching Override looks at Total Profit Per Day by all miners and switch away when it hits a user defined threshold to counter a temporary algo profit spike (usually sharp drop in difficulty using "current" statistic) affecting most of the miners in AM for that period of time.

An Individual Switching Override Rule looks at the profit calculated by the "Profit Switching" Tab in "View Details...", that if none of the available algos/pools meets a certain profit threshold defined by user (say if I want this rig to earn at least $2.00 / day) after profit calculation cycle, I can tell the miner to Stop but keep monitoring and start it again when there are algos/pools that have meet the threshold I defined. Also, sometimes individual miners are mining at a loss or not optimal (HW difference between rigs, susceptible to small scale individual spike since mining different algo than powerful rigs), this rule allows it not just to stop, but look at the overall profit rank for this particular profit profile and adjust accordingly. Example, my NVidia rigs might be mining profitably after global profit switch, and the few AMD ones suddenly decided to mine Neoscrypt (due to profit/difficulty fluctuation), 5 minutes later, all NV rigs are happily pulling in profit while the Neoscrypt coins went down drastically but it is still profitable to mine Ethash with the AMD at profit, but there's still 10 minutes left for my say...15min switching cycle, so now I want AM to only switch those AMD rigs which are making loss to another algo that's still making profit above threshold I specified. As I understand, I can still do an overall switching and the rigs that are already mining the most profitable in the switching time interval won't be affected and stay mining away. However, right now, I can't just keep switching say, having a bad day, and certain cards that I have completely stopped making profit altogether (my poor NV 1050 and R7 370 say...affected most directly with most pronounced effect followed by other less power efficient AMD cards with limited choice of profitable algos)....that's why I think it's necessary to have the switching rule look at the entire profit profile's profit + what it is currently pulling in before making a call to "switch" or "pause".

Hope it illustrates what I was trying to get at and not confuses you instead,

Cheers,

1) As you found out, Managed Templates are good to use for Managed Miners. Do you need to switch between using profit switching and a Managed Miner as well? You can make the change if you right click on the miners and select "Convert to Managed Profit Miner" for example.

2) I do see your point about showing the last applied template name, and I've received feedback on this in the past as well. It's currently not being displayed.