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

I've never tested running Awesome Miner in a docker environment so unfortunately I don't have an answer to this. The Awesome Miner main application is a Windows desktop application and they are in general not working well in containers.

patrike

CC (coincalculators.io) lately provides incorrect data, you have to write to those who support withdrawing a coin or recalculating
I propose to consider adding CM (coinmarketcap.com) API links below

Public API
https://coinmarketcap.com/api/

Professional API
https://pro.coinmarketcap.com/

Patrike, in mining history, are the periods of
15 m
1 hour
1 day
7 days
1 month

You could consider adding 3 days, to have reliable data without having to wait for 7 days

Hi Patrike or any awesome AM users,

We want to do the following, how do I get started?

Miner: Baikal G28

MON-FRI: Profit switching multi-algo at ZPOOL for 18 hours, then mining only GRS at Suprnova for the remaining 6 hours of the day.
SAT-SUN: Renting multi-algo at Nicehash for 18 hours, then to ZPOOL profit switching multi-algo for the remaining 6 hours.

Can I achieve this using AM scripting etc.

Thanks

https://github.com/trexminer/T-Rex/releases/download/0.8.2/t-rex-0.8.2-win-cuda10.0.zip

x22i  1-3% +

Is it possible to run awesome miner in a docker container, so I don’t have to have a dedicated machine to monitor my Antminers.

new t-rex 0.8.2   improved x22i  + 1-3% , add new version in AW

Awesome Miner is making multiple requests to an Antminer to get all information related to the mining. For Z9 miners they incorrectly report the hashrate unit and Awesome Miner needs to detect that it's an Z9 and then change to another unit (kH/s). It's two different requests for getting the hashrate and for figuring out that it's an Antminer Z9 and I think the second one here is failing every now and then.

Can you please go to the Options dialog, Advanced section and either increase the Miner API connection timeout a bit, or try to set "Enable retry". This will make it less likely that an API request to the Antminer is failing and Awesome Miner should detect it as a Z9 all the time.

T-Rex 0.8.1

Performance improvements: x22i +10-20%

Bug fixes:
Miner hangs on start up when it doesn't receive authorize message response

NOTE: skunk may be slower by 1% than the previous version, will be fixed soon


Linux/Windows
https://github.com/trexminer/T-Rex/releases/tag/0.8.1

Well, if you were right, I added the port in that format. I have mounted it in a conventional way but in advanced I have added --pers BgoldPoW. And working. Your observations and questions have led me to the solution.

It performs much better than EWBF, it is advisable to use it

I have a group for my z9 minis.  In this group occassionaly some of my miners will gave a hashrate reading of Gh/s instead of kh/s.  Of course this is wrong and causes my revenue to shoot up to some unrealistically high value.  All of my z9 minis share the same profit profile and all but about 4 of them work correctly.  The profit profile values are setup correctly with kh/s.  Also this happens to them even when I remove the profit profile from them because it has to do with the hashrate that is being reported in error.  I have removed the miner completely from the system and added it back and it still gives this hashrate error.  From what I can see via the miner status page on the miners themselves it is reporting the correct kh/s reading.  Is this something that needs to be fixed with the software or is there a fix I can perform on my side? 

New z-enemy 1.25 Miner With Additional Improvements Hashrate

https://cryptomining-blog.com/10430-new-z-enemy-1-25-miner-with-additional-improvements-in-terms-of-hashrate/

The only confusing part I can see is the port specification. I don't know where "--port 8866" came from because Awesome Miner is only adding "-n" (which is the same as "--port") for Gminer. However, the value "-1" looks strange here.

1) Did you manually add "--port 8866"?
2) Can you give me the complete Pool URL that you defined in the properties of this pool and I can investigate if Awesome Miner didn't parse it correctly when splitting the hostname part from the port part? This could by why it produces the value "-1" for some reason. Thanks!

@patrike  I was very excited about the Gminer, and after hours and hours, I have come to the conclusion that you have it badly defined

Line that I make through AM

miner.exe  -a 144_5 -s btg.suprnova.cc --port 8866 --pers BgoldPoW -n -1 -u trucobit.rig1 -p patata --api 4028

Line that should be correct
miner.exe --algo 144_5 --pers BgoldPoW --server eu.btgpool.pro --port 1445 --user GZdx44gPVFX7GfeWXA3kyiuXecym3CWGHi.rig0 --pass x --pec

If you see two things in plain sight, -a by --something and -u by --user, --pass   etc...

I tried to put the right thing, but then either repeat it twice or leave a loose. I have tried to change the something in managed sofwtare. I tried to put the complete line in the pool but it puts more text the Gminer configuration

I am therefore unable to configure pools of Zhas or Equihash with this miner. I just got the raw BTCZ test, and the performance is higher.

But I am unable to define other BTG, ZEL and similar currencies. When I have seen that this miner gives more hash than EWBF. Not even Bminer supports it, not in the AW version but in Bitcointalk it is supposed to support 144_5

I hope you can look at it before the next release to correct how Gminer interprets the data, because it does not do well

I have hours and hours. You could do it in the donkey but it does not always work or differ between the different RIGS and then statistics in the pool

Thanks - these will be included in the next release, planned to be available within the next 1 - 2 days.

I see your point and I've had similar feedback in the past. This can be a future improvement.

Thank you for your help, it now works fine with Profile profit. To be honest, i already tried this setting but at my first attempt i confused profit and revenue, so my value was not correct and that was the reason why my rule never triggered...

IF it was my fault, I had customized the route of the .exe of the Z-enemy. Thanks for the help

I think with the builtin triggers, you can't do it with Revenue, but have you tried Profile Profit as the trigger (I know it's profit and not revenue, but there is only one trigger for this)? since the Miner Revenue / Profit triggers only works when your machines are actively hashing.

Hello Patrike,
I created a rule to make my miners stop when revenue is below a certain value.
But, dumb question, what should i do to make start miner again when revenue is back above a defined value ?
I tried some things without success until now...