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

Now i have upgraded, my custom Phoenix miner doesn't connect to the interface. Can anyone help please?

Hi, question regarding switching mining pools:

I have several Antminer S9 ASICs in awesomeminer, I configured 2 pools: antpool and BTC.com, i configured API access on S9, when i try to switch pools it disables 1st pool, then switches 2nd and 3rd pools, as result miner not working because 1st pool - disabled, anybody faces similar issues?

Awesome Miner version 4.4.2

- Excavator 1.4 supported as both Managed Miner and Managed Profit Miner. Please note that automatic download isn't supported.
- Performance improvements when performing opertions on many Antminers over SSH, for example setting default pools or configuring the API access.
- Antminer diagnostics, where the cgminer/bmminer configuration of the Antminer can be displayed
- The Managed profit switcher can be configured to detect pool failures and move on to the next pool
- Added support for a total of three modes for profit statistics from pools like zpool, Hash Refinery and AHashpool: Current, 24h average estimate, 24h average actual.
- Notification actions can specify a custom Webhook POST body
- New notification variable to get the Notification ID
- The system notifications can be disabled with a new setting
- Claymore Dual Ethereum Miner 11.0, including the new dual mining algorithms
- Minor corrections

Awesome Miner cannot automatically download the Excavator mining software because of the Nicehash end user license agreement where redistribution of their software isn't allowed. The Excavator mining software needs to be downloaded manually from:
https://github.com/nicehash/excavator/releases
The Excavator software can be downloaded and extracted to any path. To use it from the profit switcher, edit the Profit profile and enable it in the list of software, then click the configure button to specify the path.

The new profit switching feature to detect pools that doesn't give any accepted share can be enabled in the Options dialog, Profit switching section. To see if any pools are listed as a failed, right click on the miner and select View Details to view the profit calculations per pool and also if any of these pools have failed to give accepted shares.

Please note that the pool is listed as failed per miner - it's not global to all miners. The reason is that if a single miner is unstable and doesn't produce any accepted shares, it will not ban the pool for all the other miners. If it's a pool problem, it will be detected for each individual miner about the same time anyway, and each miner will mark the pool as failed.

There are now three modes for profit statistics: Current, 24h average estimate, 24h average actual - configurable in Options dialog, Statistics section. Please note that all of these numbers are still taken directly from the pools, so it's still the responsibility of the pool to provide as accurate numbers as possible.

Looking for some input

I have multiple Baikals and I'm wanting to update the pool and The only way I have been able to do it so the algo switches as well is to have the pool and algo setup in the miner using the webUI.

Is there a faster way of doing it? This will be very time consuming with 30+ machines.


I thought about using MRR and have it setup in the miners for each algo.

then create a coin in AM "MRR-QUARK"

then when I want to mine a specific pool I would make "MRR-QUARK" the most profitable and then go to MRR and change it to the pool I want.

I would like to ask the following question: Would the tifficultly increase in BTC mining if in the future with nuclear computer or quantum computer is minted?

I did the same. I think its the right way.

Thank you for this feature !

Can we see if a pool is actually banned (GUI way) ?

what is the proper way to enable Excavator as a profit miner? I copied the extracted zip to the users\username\awesomeminer folder where the other miners live and enabled/set the path through the edit profit profile, appears to be working

Thank you sir for your amazing support!! I see now that Excavator works with managed profit miner.

third it .
me to it is faster then Claymore ETH Miner just tested it by about 2 MH or was for me .

I think patrike indeed said a while back he was looking at a way to add any custom miner with full stats or what we need to run it in AM and Other OC options that AM can use but that's gonna take some time it's more involved to add. if I understood him wrong ,then I'm being it up again or hint, hint it will make life a lot easier but only if i misunderstood....if there needs to be a one time add on fee i will be then glad to pay for it or any thing to make AM more Universals then it all ready is . .. or Improve it , there is always room for improvement .

if there was a reboot issue maybe try one of these.

https://www.ebay.com/itm/USB-Watchdog-5-0Miner-Crash-Recover-Timer-Module-Auto-Restart-Anti-attack-Server/183005739653?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

and make sure to have AM set to auto start per miner.

Just wanted to say thanks so far for the work you have done Patrike.

If I had one suggestion would be development of a hybrid of current profitability and 24 hour profitability (something like a rolling average of current profitability over the last hour X 24 hr profitability) as an option for profit switching. Ideally it would prevent the one off spikes in profitability that occur for algorithms. If the profitability is indeed real, the rolling average would pick it up.

In terms of measurement of pools side vs client side shares - is there any realistic way for AM to detect at YIMMP pools (or even other pools) if consecutive orphaned blocks were found and then disable that pool for X hours to hopefully dodge a problem at the pool? I realize that ultimately pool side results are what matters and that pools should be more responsible for that detection (ex: chain split protection if >50% of blocks are mined at a single pool), however, if it's even possible and you were able to come up with a solution for that I think you'd add something very unique to the mining market.

huh ? noting is wrong like your saying with Awesome miner ...You sure you know wtf your doing ? . sounds like user error or lack of not reading or understanding what you read to well .....

I'll second this

Pretty demanding for a first post

Good afternoon!

I'm testing your Awesome Miner ver 4.4 program and you have a lot of big problems with the program.
1. the disconnection of the miner does not work when the threshold temperature is exceeded, for this reason, the owner of the equipment was greatly harmed.

2. disabling the graphics core does not work ...

3. Redo the Online services tab and associated Profit Swithing - make a pool table so that users can add the pools they deem necessary, and those that you have will be added by default with the ability to change or delete them. The base of the pools is obtained.
4. In the absence of communication between the miner and the pool during the mining in connection with the load of the pool itself and the constant disruption of communication with it, it is necessary to think over switching to another pool with a stable connection. Otherwise, there is a lengthy downtime of the equipment due to the program being dropped on this pool due to the receipt of a good statistics on the yield by the program, but the impossibility will connect to the pool due to its congestion.
5. Make the correct sorting of video cards, the possibility of their selection when mining and group them into the same model.
 6. Correct the list of video cards in the video card testing window for profitability, the video card model is replaced and the measured values ​​are not correctly stored.
7. Why do not you fix anything? Why do we pay money for you?

The full version of the message was sent to [email protected]

Thanks for the improvements.

The problem was that accepted shares that was reported by ccminer was between 19000 and 53000 and the method you described won't work, because accepted shares on pool's reports was zero, see this : https://www.dropbox.com/s/4obw9jkx0s8l84g/Screenshot%202018-02-09%2011.53.34.png?dl=0
 
I opened www.zpool.ca/api/walletEx?address=WALLET_ADDRESS and the miner's array are not uniquely identified by AM with ID fields from miner's array (you leave it empty) and also accepted field from each miner remained to zero even if AM was mining for 3 hours.  

So from my point of view you are not reading and you are not using the real values from the pools that are the most important, because only the registered hash-rate on the pool's side is that transforms to payments.  

The implementation is simple and will fix a lot of issues all caused by the fact that you read what miners are reporting (that many times miner lie and report misleading values to hide the developer / or hacker's stealing fee) instead of reading values recorded from the pool that many times, with many miners are lower.

I also think that you should use total_earned field from /api/walletEx?address= and add checks like :
1) if value decreased it means you were mining an orphaned fork - this happened last week, and was reported on this forum and also we saw that on all pools 8 hours of income vanished because all MA users with 24 hours statistics were mining on ahashpool orphaned CRC coin . Also AM could cause 51% attack and soft fork that means all AM users will loose all the money on that branch (I hope you know what I am talking about).
2) if the value increases you have the difference and you will have to show a new column for each miner with pool's earnings reports the statistics with income per unit of time (make the difference between 2 requests from the pool in seconds and if the reports are not identical (because pools refresh statistics every few minutes) divide the income to the number of seconds and you have real income from the pool in $.
3) Add in rules triggers and actions (a very useful part of AM, congrats for that, btw) new items based on the accepted and total_earned fields from pool's statistics (all you need is some associative arrays to store values for each pool. New rules will be much better than flawed "accepted" rules we have now.

Am users will compare values from the pool with values from the statistics and will notice that :
1) the miner is stealing and reporting inflated hash rates that is a practice these days and you are ignoring it;
2) a specific pool is stealing or is not functioning correctly for any reason (errors, restart, ddos).
3) AM users will really appreciate you because they feel you are on their side, because they have together millions of dollars on your hands and you have a huge responsibility to protect their inestment

So, do you understand, Patrike ?

How much "money" did you lose at Zpool in those 4 hours?

sent via PM

The error message also indicates that the Windows service IntelliBreeze Maintenance Service isn’t running correctly. Can you please correct and verify? You could also try to change the port via Options dialog, Web section.