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

[moppidoo]

Hi Patrike,

my previous request probably been overlooked, could we add ability to batch update power consumption for profit profiles? (mining farm with old computers + mixture of cards means shuffling of hardware needed at times when old parts fail...pita when updating the power consumption one by one...) ... + when one forget to update due to hw change or added several new algos...things don't turn out too well with profit switching)

Cheers,

Just to make sure I understand the request - Is it batch update of power usage for all algorithms within a profile, or do you have multiple profiles where you want to change for example the Neoscrypt power usage for all selected profiles?

Hi Patrike,

Sorry for the confusion, yes it's to batch update power usage for all/multiple algos at once within a profit profile.

[patrike]

Thanks for the answer. Don't you think that a websocket type solution as I described above will help? With that you can do without any issues one single request every 5 or 10 seconds and after that send the response to all AM users and  you can free a lot the load on pool API requests. Also you will have past hours information about pools that miners do not have when initially connecting that will be useful also.

From my point of view additional delay after current pool statistics is refreshed (current pool statistics is refreshed every 30 seconds) will only make AM's performance lack behind Nemos miner or other software that can switch my miners faster than AM after pool statistics informed me that Tribus profitability just decreased 10 times and AM keeps me mining on Tribus for another 2 or more minutes (until statistics will work) instead of a few seconds how NemosMiner does now. 

Do you agree ?

You are correct that websockets could reduce the load as it doesn't require the same frequent polling for new information. However, I don't think any of these pools provides any websocket interfaces today. It's only standard HTTP as far as I know.

Today the minimum profit switching interval is 60 seconds in Awesome Miner, as the profit switching interval can only be set in number of miners. I have received feedback a few times in the past about being able to define the profit switching interval in seconds as well. By allowing the user to specify 30 seconds (that's very frequent), you would also be able to get faster updates from the pools. However, I think it's a quite small gain in updating every 30 seconds compared to 60 seconds - but the best is of course to leave that decision to the user of the software.

The minimum value is 2 minutes. I can not set 1 minute. Can you check ? We need at least 1 minute to avoid mining on unprofitable algo that is volatile (tribus, skunk, timetravel).

So there are actually two values here.

The lowest value for the profit switcher (Options dialog, Profit Switching section) is 1 minute.
The lowest value for the coin statistics (Options dialog, Statistics section) is 2 minutes. This one mainly makes sense if you don't use the profit switcher or if your profit switcher is on a slow interval.

However, if you set your profit switcher to 1 minute, Awesome Miner will use 1 minute for all statistics updates as well (WhatToMine, Nicehash, zpool, ...).

[Bob-Bit]

Ok, I have what would seem to be a simple request. Can we have different profit switching intervals on different miners that can be set on individual profit profiles independently? I have a GPU miner, CPU miner, and AMD miner on my local main machine, and then I have 4 Baikal ASIC miners setup as remote miners also. Also just added a remote mining pc with one AMD card.(for now) I have the profit switching interval set to 27 minutes. If I notice that the profit from the main GPU miner has tanked, and I hit restart on it, the timer resets, and the other miners won't profit switch till the main miner timer gets to 28 minutes. If the profit tanks again, the whole process repeats, and if the other miners look like they are doing badly, they have to be restarted manually as well, and it isn't clear (at least with the Baikals) that they are going to the most profitable coin (It seems like they switch to miningpoolhub no matter what, then do an actual profit switch maybe 15 minutes later) It would be invaluable to have separate timers on each profit profile that work independently. Sometimes I see the main miner is doing great, and I change the profit switching interval to 45 minutes (basically doubling it) so it doesn't switch, but this affects all the miners, and obviously it would be much better if they were independent of one another. Thanks for all your hard work and improvements Patrike! They don't go unnoticed on this end!

[akadamson]

patrike,

Found a little annoyance, first 6.0 bminer is out.

second, and the annoyance. if you define a custom version of software, tell it it's api and command compatible, and then define the path, when you start it the first time it doesn't take any specifically entered command line parameters that you may have entered. 

Third it doesn't show the pool name in the main display for the miner, in fact if it's using the built in version it does and if you select a user installed version and save that, it will drop the pool name and never show it again until you switch back to the built in version.

1) Bminer 6.0 will be included in the next release that soon will be made available.

2) I was trying to reproduce this without success. Was it in the Managed Software Properties you specified a command line argument for one of the algorithms - and then creating a Managed Miner, and once started the configured command line wasn't added?

3) I will do some additional testing of this. In general, if Awesome Miner has multiple pools matching a URL from the mining software, it will not display the name of the pool, only the URL.

2) happened only the first time I started the miner it didn't pick up the addition of a command line arg for a managed miner, it did on the second start however. (note the miner was running when I made that change so this might have had something to do with it)

I wonder if on 3) above, it's because it's a stratum+ssl not tcp?  It doesn't show the name or the url

[powerstr]

Hello!
the reaction rate on pampas fell...
auto-switching does not always happen when you select a profit coin!

[patrike]

Ok, I have what would seem to be a simple request. Can we have different profit switching intervals on different miners that can be set on individual profit profiles independently? I have a GPU miner, CPU miner, and AMD miner on my local main machine, and then I have 4 Baikal ASIC miners setup as remote miners also. Also just added a remote mining pc with one AMD card.(for now) I have the profit switching interval set to 27 minutes. If I notice that the profit from the main GPU miner has tanked, and I hit restart on it, the timer resets, and the other miners won't profit switch till the main miner timer gets to 28 minutes. If the profit tanks again, the whole process repeats, and if the other miners look like they are doing badly, they have to be restarted manually as well, and it isn't clear (at least with the Baikals) that they are going to the most profitable coin (It seems like they switch to miningpoolhub no matter what, then do an actual profit switch maybe 15 minutes later) It would be invaluable to have separate timers on each profit profile that work independently. Sometimes I see the main miner is doing great, and I change the profit switching interval to 45 minutes (basically doubling it) so it doesn't switch, but this affects all the miners, and obviously it would be much better if they were independent of one another. Thanks for all your hard work and improvements Patrike! They don't go unnoticed on this end!

Thanks for the feedback on this. I agree that having a setting for the interval per profile would make sense.

[patrike]

Hi Patrike,

A small and quick request, in your next release can you include that your benchmarking window be expandable instead of a fixed size on Windows?
I occasionally take screenshots to do comparisons when miners get updated or when I'm trying to tweak the GPUs.  Or even better if you could allow it to export to an excel or CSV file.

Much thanks and great work!

Thanks for your nice feedback. I was just doing a few minor UI corrections to the benchmark dialog and I will make it resizable as well. The export feature will have to be a future improvement.

[patrike]

Hello
is there somewhere a link for setup Baikal X10 and B?
thanks Thomas

Hi. I don't have any experience in using this miner myself, by I do know that there are a number of users running Awesome Miner together with Baikal miners. There might a Baikal specific thread where more experienced users can help out as well.

From an Awesome Miner point of view, you add it as an External Miner:
http://www.awesomeminer.com/help/externalwizard.aspx

[patrike]

Awesome Miner version 4.6.1

- Antminer V9 supported
- Added several new algorithms, including CryptonightV7
- Performance History export via CSV file includes miner IP address if no description is set
- User interface improvements to the Benchmark dialog
- D3pool integration disabled
- Excavator miner is instructed to print the speed of all workers in the console window by default
- Bminer 6.0
- CastXMR 0.9.1
- Correction to SIA block explorer integration to handle large balance numbers
- Correction to profit switcher when all available Ethereum pools was marked to be ignored due to no increase in number of accepted shares
- Minor corrections

[puwaha]

The minimum value is 2 minutes. I can not set 1 minute. Can you check ? We need at least 1 minute to avoid mining on unprofitable algo that is volatile (tribus, skunk, timetravel).

I can't see any reason you'd want to profit-switch every 1 minute.  Depending on the mining software, it can take a few minutes to ramp up to maximum hash rate.  BMiner and CCminer are great examples of this.  Plus most block times are longer than 1 minute.  The pool doesn't have any fresh information about the statistics of that coin until the next block.

And depending on the pool's share mechanism (PPS vs PPLNT) you can actually be penalized for mining so shortly.

[akadamson]

The minimum value is 2 minutes. I can not set 1 minute. Can you check ? We need at least 1 minute to avoid mining on unprofitable algo that is volatile (tribus, skunk, timetravel).

I can't see any reason you'd want to profit-switch every 1 minute.  Depending on the mining software, it can take a few minutes to ramp up to maximum hash rate.  BMiner and CCminer are great examples of this.  Plus most block times are longer than 1 minute.  The pool doesn't have any fresh information about the statistics of that coin until the next block.

And depending on the pool's share mechanism (PPS vs PPLNT) you can actually be penalized for mining so shortly.

I've come to the same conclusions.  Can't remember what the default is, but I've set the switch interval to 10 mins and the threshold to 3%  Experience shows that *NOT* chasing the high price of the minute (or in this case 10 mins) and due to most of the multi/multi's being PPLNS, I stay ramped which more than makes up for chasing

[akadamson]

Patrike,

Can you update the WTM coin symbols in the next release, there are a number that are there currently that don't have a symbol in AM - thanks for all the hardwork, it's really a pleasure to use.

[zergbitcore]

Patrike,
The latest AM update has the bug with bitcore.
https://yadi.sk/i/uqfHdHCe3TkFyE
It worked well on 5 rigs before. I tried to delete my bitcore settings and keep only yours, also tried to restart the software, restart the rigs, tried to disable/enable bitcore algo with no effect. Ahashpool and Zpool bitcore profit looks ok. the problem is exist only with bitcore profit for Hasrefinery and Zergpool.

Please, make fix

[streaml1ne]

I've got a new rig and for some reason I'm not able to benchmark anything with Excavator (the new version). I keep getting the error:

Code:

=========================== www.nicehash.com =========================
           Excavator v1.4.4a_nvidia GPU Miner for NiceHash.
           Copyright (C) 2018 NiceHash. All rights reserved.
                              Developed by
                djeZo, dropky, voidstar, and agiz
                   with help and contributions from
           zawawa, pallas, Vorksholk, bitbandi, ocminer, and Genoil.
=========================== www.nicehash.com =========================

Build time: 2018-02-16 13:11:25
Build number: 4645
Provided startup commandline:
        "C:\Users\user\AppData\Roaming\AwesomeMinerService\excavator\excavator.exe"     -c awesome.json -p 4028

[01:03:31][0x00000f20][info] Log started
[01:03:31][0x00000f20][info] core | Found CUDA device: GeForce GTX 1070
[01:03:31][0x00000f20][info] core | Found CUDA device: GeForce GTX 1060 3GB
[01:03:31][0x00000f20][info] api | Listening on 127.0.0.1:4028
[01:03:31][0x00000f20][error] core | Command file - invalid JSON: [
[01:03:31][0x00000f20][info] core | Initialized!

The json file includes:

Code:

[
	        {"time":0,"commands":[
		        {"id":1,"method":"algorithm.add","params":["lyra2rev2","benchmark",""]}
	        ]},
	        {"time":3,"commands":[
		        {"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","4"]},
{"id":1,"method":"worker.add","params":["0","5"]},
{"id":1,"method":"worker.add","params":["0","6"]},
{"id":1,"method":"worker.add","params":["0","7"]},
{"id":1,"method":"worker.add","params":["0","8"]},
{"id":1,"method":"worker.add","params":["0","9"]},
{"id":1,"method":"worker.add","params":["0","10"]},
{"id":1,"method":"worker.add","params":["0","11"]},
{"id":1,"method":"worker.add","params":["0","12"]}
	        ]},
	        {"time":10,"loop":10,"commands":[
		        {PrintWorkerSpeed},
		        {"id":1,"method":"algorithm.print.speeds","params":["0"]}
	        ]}
        ]

[segotiwul]

if we are going to play on the windows screen and have difficulties because the sever is still spinning, then we can open Windows 8.1 / 10 WHQL right away, because of the severity of the sever and the growing knowledge.

[Globalboosty]

Patrike,
The latest AM update has the bug with bitcore.
https://yadi.sk/i/uqfHdHCe3TkFyE
It worked well on 5 rigs before. I tried to delete my bitcore settings and keep only yours, also tried to restart the software, restart the rigs, tried to disable/enable bitcore algo with no effect. Ahashpool and Zpool bitcore profit looks ok. the problem is exist only with bitcore profit for Hasrefinery and Zergpool.

Please, make fix

It seems the problem is not the AM software. HR and ZP display 0 for actual profit for bitcore. If choose estimate profit instead it works well.

[zergbitcore]

It seems the problem is not the AM software. HR and ZP display 0 for actual profit for bitcore. If choose estimate profit instead it works well.

Yes, bitcore actual profit turned to zero. Thanks for your attention. AM has no problem.
But Awesome miner has another problem after update. Bitcore, HSR, Keccakc and X16r were added, but I already had them in awesome miner before. After deleting my manual settings of these algos I have several problems with zpool algos:
https://yadi.sk/i/oZXRSgSU3TmAXj
Patrike, Do you have any ideas how to repair this? Thanks.

[DKu]

Patrike,

Can you check out the code in Awesome Miner for a bug.

Some new users have joined zpool, used a bitcoin wallet (BTC), but in the wallet (stats page) at zpool it's set as BCH.

Awesome Miner is not doing anything for this scenario and simply assuming that zpool will go for BTC if nothing is specified explicitly. Awesome Miner do not specify payout coin at all, so this must be investigated from a zpool point of view.

The zpool instructions have always been a bit unclear on this.

-o stratum+tcp://<algo>.mine.zpool.ca:<PORT> -u <WALLET_ADDRESS> [-p c=<SYMBOL>,<OPTIONS>]
<WALLET_ADDRESS> must be a valid address. Incorrect addresses will result in forfit of earning.
You can also use any valid wallet address from any of the coins we mine. This feature has had minimal testing so use at your own risk

Awesome Miner is setting the Bitcoin wallet address the user specified. I interpret that you can specify any coin for payout, but that specifying like that is "at your own risk". For that reason, Awesome Miner is not specifying this "c=" parameter. In the past zpool always went for Bitcoin payouts in that scenario.

You can still configure Awesome Miner to add this parameter if you want (via Options dialog, Online Services, modify the zpool entries and add command line "-p c=ABC" or similar).

Further reading on zpool instructions:

c=<SYMBOL> doesn't always work

This is yet another reason why Awesome Miner isn't trying to set this parameter at all.

Can you please make this option more visible or even required? 99% of the time having the proper c=BTC set (or whatever symbol is for the wallet their using) will choose BTC. As it is now.... it's 50/50 with nothing set.

Could anyone explain to me how to setup awesome miner with Zpool? I've tried to check Select BTC Payout option in Profit Switching, add c=BTC parameter in the password filed in Online Services fo Zpool (all algos), add c=BTC to command-line and to the Zpool template. Pool also show me right version of my miner and Extra c=BTC is correct. But payouts only in SYS coins. Of course I added BTC wallet address to the Zpool filed and the address is correct. What I'm doing wrong? How to make awesomeminer to work with Zpool correctly?

[devilrub]

Hi
I bought awesome miner for 10 miners, very great tool, eventhough i still have lot too learn to master it
I have 7 rigs, but awesome miner can only detect those running claymore, but not DTSM, even if i put the option -- telemetry 2222, is there anything else to set up so he can see them as external miner from a computer that is not mining ?

[soothaa]

Is it just me or does ZergPool just seem to suck? I am getting WAY less BTC payouts than I think I should be...