Author

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

full member
Activity: 558
Merit: 194
Thanks.  That did the trick!
legendary
Activity: 3346
Merit: 1094
Are there any plans to support Ethminer?

https://github.com/ethereum-mining/ethminer/releases

I find it more efficient than Claymore.


Bump.  I use HIVE OS primarily but monitor the rigs using AM with each HIVE Rig configured as an external miner.  Works great, but now that I'm running Ethminer on some of the rigs, I can't monitor from AM due to lack of support.

Is Ethminer on the roadmap for AM?
In the past Ethminer had an API compatible to Claymore Ethereum miner. If you enable the API of Ethminer and use an External Miner in Awesome Miner where you specify Claymore Ethereum as software - is that configuration working?
full member
Activity: 558
Merit: 194
Are there any plans to support Ethminer?

https://github.com/ethereum-mining/ethminer/releases

I find it more efficient than Claymore.


Bump.  I use HIVE OS primarily but monitor the rigs using AM with each HIVE Rig configured as an external miner.  Works great, but now that I'm running Ethminer on some of the rigs, I can't monitor from AM due to lack of support.

Is Ethminer on the roadmap for AM?
legendary
Activity: 3346
Merit: 1094
Patrick,

Can we choose to order the coins value and online services by profit and not by revenue? Some algos take more power and the profit is lower than the revenue...
I will make Revenue and Profit two separate columns in the next release. This will make it possible to sort on any of them.
legendary
Activity: 3346
Merit: 1094
Quark Bug:

There is a bug when using Quark algo. It is not calculating profit correctly. If I set my profit profile to 50MH/s with Quark the coins profit is far higher than if i were to change the coins set algo to something else and set that algo to 50MH/s in the profit profile.
The formula for calculating coins per day (which is part of the profitability calculations) are different on the Quark algorithm compared to almost any other algorithm. For this reason, entering the same coin properties for two coins, specifying Quark as algorithm for one of them and for example X11 on the other, the results will be different.

It might be that some specific Quark-based coin uses yet another formula - please let me know any details if you run into this.
legendary
Activity: 3346
Merit: 1094
coins again to update whattomine, many thanks to those who repaired the API
It looks like it was resolved on the WhatToMine side, where their API now works like it used to. Let's keep an eye on this.
legendary
Activity: 3346
Merit: 1094
v 4.5.5

Profit switching calculation seemed bugged. right clicking details of each miner now shows profit per day which works for individual coins/algos profit calculation, but mix that up with Online Services which I think give revenue per day or due to MH/GH calculation (this was not Yiimp, but NiceHash) my miners were mining random Sha3 and Blake2s..

Online Services shows
Eth
Equi
Neoscrypt
Lyra
Nist

Details Tab:
Sha3
Blake2s
random coins
and everything else negative

On the same profit profile....disabling all online services restored more or less normal behaviour....looks like profit/revenue conflict and online services (predefined or User Defined) took precedence regardless coins tab profit info.
Hi,
Can you send me some additional details about this issue or maybe the log file? I would like to investigate this a bit more.

Keep in mind that Online Services can show more algorithms, that actually will be ignored by the miner because the Profile doesn't have any mining software enabled for this specific algorithm. If for example Claymore Ethereum miner is disabled in the profile, Ethereum will not be considered by the profit switcher and will not be displayed in View Details. The Online Services tab do still list Ethereum in this scenario.
newbie
Activity: 117
Merit: 0
coins again to update whattomine, many thanks to those who repaired the API
legendary
Activity: 3346
Merit: 1094
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.

Is this issue resolved ?

Should we stop Awesome Miner and start using Nemos Miner  because of that one has many more miners and with default configuration Nemos Miner uses the best miner for each algo, providing the best possible hashrates, having more than 10 ccminer forks with the best default preconfigured values for each algo.

What do you think ?
No official statement has been made from the WhatToMine team yet, so I don't think anyone knows the exact status or the way forward yet. I'm getting a very large number of request about this issue right now, so I will of course implement any solution that WhatToMine present - but hopefully they simply resolve it on their side.

It's also important to understand that WhatToMine owns their data, so I cannot try to "steal" it in some smart but unsupported way.

All profit information from Nicehash, zpool, MPH and so on still works fine. It's only individual coins listed on WhatToMine.com that cannot be accessed at the moment. Everyone using the WhatToMine API's are affected, so a change to another application would be of no use.
newbie
Activity: 117
Merit: 0
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.

Is this issue resolved ?

Should we stop Awesome Miner and start using Nemos Miner  because of that one has many more miners and with default configuration Nemos Miner uses the best miner for each algo, providing the best possible hashrates, having more than 10 ccminer forks with the best default preconfigured values for each algo.

What do you think ?
I think we should wait, the developers will find a solution.
newbie
Activity: 140
Merit: 0
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.

Is this issue resolved ?

Should we stop Awesome Miner and start using Nemos Miner  because of that one has many more miners and with default configuration Nemos Miner uses the best miner for each algo, providing the best possible hashrates, having more than 10 ccminer forks with the best default preconfigured values for each algo.

What do you think ?
full member
Activity: 258
Merit: 104
OK I found the solution.  Claymore insists on needing something in the wallet field or else it drops the pool and then complains no pool specified.  So what should I put in the wallet field?  I'd like to put my MPH username and worker e.g. username.worker but I would ideally like it to match the rig that is mining.  Is there a variable/template thing like [USERNAME].[WORKER]  that I can use?  Or does it not matter what junk you put in wallet?

Apparently it does matter so how to make AM automagically put the username.worker in the wallet field when using claymore?  It works if set in the pool but I want the worker to be replaced with each rig name and avoid having to set a separate pool for each rig.

I did say you need the wallet field populated with the ewal value....

again, didn't use templates and MPH, but what if in managed template you use the "add to worker name" field...dunno if that'll work (doubt it will tbh, but worth a shot if you really insisting. or change hub worker default job to only mine eth on MPH

Yeah you were right, the solution is to populate the wallet field.  It looks like I will need a separate pool for each rig and can't use a template.  It's either a bug or an oversight that the software doesn't automatically configure the wallet field for claymore.
full member
Activity: 270
Merit: 100
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.

So it's all blind flight still it is solved I guess...
jr. member
Activity: 348
Merit: 5
OK I found the solution.  Claymore insists on needing something in the wallet field or else it drops the pool and then complains no pool specified.  So what should I put in the wallet field?  I'd like to put my MPH username and worker e.g. username.worker but I would ideally like it to match the rig that is mining.  Is there a variable/template thing like [USERNAME].[WORKER]  that I can use?  Or does it not matter what junk you put in wallet?

Apparently it does matter so how to make AM automagically put the username.worker in the wallet field when using claymore?  It works if set in the pool but I want the worker to be replaced with each rig name and avoid having to set a separate pool for each rig.

I did say you need the wallet field populated with the ewal value....

again, didn't use templates and MPH, but what if in managed template you use the "add to worker name" field...dunno if that'll work (doubt it will tbh, but worth a shot if you really insisting. or change hub worker default job to only mine eth on MPH
member
Activity: 115
Merit: 12
with the 4.5.5 bug still can do autoswitch??? cause I've been mining BTG and didn't switch to other like ZEC or ZEN
newbie
Activity: 117
Merit: 0
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.
why not use winsockets and just download the whole page in a std::string then parse values for each coin and display ?
it is a bad idea.
newbie
Activity: 55
Merit: 0
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.
why not use winsockets and just download the whole page in a std::string then parse values for each coin and display ?
legendary
Activity: 3346
Merit: 1094
I'm trying to work out a solution for the WhatToMine.com API's with their dev. Right now the API's are blocked with Cloudflare where you only can access them via a Javascript-enabled web browser, but not from an application. This will result in that Awesome Miner, and other applications and services using the WhatToMine API, cannot get any coin statistics from WhatToMine.com.
full member
Activity: 258
Merit: 104
OK I found the solution.  Claymore insists on needing something in the wallet field or else it drops the pool and then complains no pool specified.  So what should I put in the wallet field?  I'd like to put my MPH username and worker e.g. username.worker but I would ideally like it to match the rig that is mining.  Is there a variable/template thing like [USERNAME].[WORKER]  that I can use?  Or does it not matter what junk you put in wallet?

Apparently it does matter so how to make AM automagically put the username.worker in the wallet field when using claymore?  It works if set in the pool but I want the worker to be replaced with each rig name and avoid having to set a separate pool for each rig.
full member
Activity: 258
Merit: 104

It says no pool specified so I think it's not reading the pool parameter.  Is there no way to clone a miner and simply change the port??  It really shouldn't be so complicated and require setting up all the parameters.  I want to use everything as is from mining etihash, and just change the port so only mine ethereum.  There is no easy way to do this??

Description:  (whatever you want to name it...)
Server URL:  asia.ethash-hub.miningpoolhub.com:20535
Worker Name:  puwaha  (or whatever your account name is at MPH)
Worker Password: x   (or whatever you used as the password when you setup the worker at MPH)
Coin:  Etherium
Wallet:  blank


On the Advanced tab, make sure the Worker Name Separater is the dot.

Then on your Managed Miner, make sure the Add to worker name is ticked, and your rig name that you setup as part of the worker name at MPH.

You need to setup the workers on MPH before you try to connect to pools like MPH or Suprnova.  You create the worker on MPH so that Awesome Miner can pass it along in the username.rigname format.



Geeze I wish it was that easy!  First thing I tried, didn't work.  Claymore complains no pool specifed.
Jump to: