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

[patrike]

Awesome Miner version 6.3.4

 Features
  - Filtering of miner list to only show offline miners on the Miners tab. Available via the Find menu in the Windows application and also as a button in the new web interface.
  - The benchmark feature will save and display the mining software version and date of the most recent benchmark
 Integration
  - Updated block explorer for BTCZ
 Mining software
  - TT-Miner power usage supported via API - will require TT-Miner 2.2.3
  - Bminer 15.5.1
  - Nanominer 1.2.3
  - SrbMiner 1.8.6
  - Gminer 1.39
  - WildRig Miner 0.15.6
 Corrections
  - Correction to saving of power usage after benchmark
  - Correction to parameter names in the Phoenix Miner pool configuration file
  - Correction to how the configured calculation method for number of coins per day is applied
  - Correction to reboot of disconnected miners via the new web interface

Note: When the NetHash-formula is used for a coin and the profit switcher is calculating the profitability - there are still some room for improvements in scenarios where the total network hashrate is low. This is also a scenario where the calculated number of coins per day can be quite different for the NetHash-formula compared to the Difficulty-formula, simply because your own hashrate starts to impact the overall network hashrate.

[Siolim]

Hello, Patricke.

If you select "Network hash rate, block reward and block time" in the properties of the coin, then information from another formula will appear in the details window.
The data from the Coins window is correct.

SWAP
VDL
ANON
GENX

I will correct this in the next release - planned for tomorrow. Thanks for reporting it.

Hello. No changes. Does not work.

[s3c70r]

Hello Awesomeminer,

Could you please add support for SlushPool in the pool balance ?

https://slushpool.com/help/api/

Thank you very much

[joseph32]

Hey Patrik,

for MiniZ miner @ Nicehash 150.5. If I start mining, it will use "--pers auto". I think because it is setup in the Online Services -> Personalization string. So far so good. But this "auto" just produces masses of rejected shares, as I just talked with MiniZ. He said we should use "--pers Beam-PoW", so I edited it in the Online Services / Nicehash Personalization String. But if I start the MiniZ miner, it has still the "auto" string flag. This is the command line AM uses:

--par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --pers auto --telemetry 0.0.0.0:4029

As a workaround I can set in the Profit Profile -> Additional command line arguments "--pers Beam-PoW" and it then use it correctly:

--pers Beam-PoW --par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --telemetry 0.0.0.0:4029

Seems like AM ignores the string in Online Services or uses always the auto flag, can you check that please?

[patrike]

Hello, Patricke.

If you select "Network hash rate, block reward and block time" in the properties of the coin, then information from another formula will appear in the details window.
The data from the Coins window is correct.

SWAP
VDL
ANON
GENX

I will correct this in the next release - planned for tomorrow. Thanks for reporting it.

Hello. No changes. Does not work.

Is this for a coin where the network hashrate is a very small unit (kH/s or MH/s)? If that's the case it's a scenario I'm currently working on improving and it will be part of the next release.

[patrike]

Hello Awesomeminer,

Could you please add support for SlushPool in the pool balance ?

https://slushpool.com/help/api/

Thank you very much

Yes, I will take a look at this one quite soon.

[patrike]

Hey Patrik,

for MiniZ miner @ Nicehash 150.5. If I start mining, it will use "--pers auto". I think because it is setup in the Online Services -> Personalization string. So far so good. But this "auto" just produces masses of rejected shares, as I just talked with MiniZ. He said we should use "--pers Beam-PoW", so I edited it in the Online Services / Nicehash Personalization String. But if I start the MiniZ miner, it has still the "auto" string flag. This is the command line AM uses:

--par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --pers auto --telemetry 0.0.0.0:4029

As a workaround I can set in the Profit Profile -> Additional command line arguments "--pers Beam-PoW" and it then use it correctly:

--pers Beam-PoW --par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --telemetry 0.0.0.0:4029

Seems like AM ignores the string in Online Services or uses always the auto flag, can you check that please?

I just tested the same, to edit Online Services, Nicehash Personalization string and set it to "Beam-PoW". When I start Miniz miner the next time it shows up with the following command line:
--pers Beam-PoW

Can you please go to the Options dialog, Managed Software section, and check the settings for Miniz Miner to make sure there are no "auto" flags here?

[JimBrown462]

Hi Patrike,

Feature request...

Would it be possible to allow benchmarking multiple rigs simultaneously when using remote agent? I have two rigs with dissimilar equipment, requiring that they be individually benchmarked. I have a profit profile for each rig. I would like to be able to open multiple benchmarking dialogues at the same time, each one for a specific rig.

Thanks for your consideration,
...jim


Edit: Never mind. I finally figured out that one needs to select the miner one wants to benchmark before clicking the benchmark button.

Thanks,
...jim

[joseph32]

Hey Patrik,

for MiniZ miner @ Nicehash 150.5. If I start mining, it will use "--pers auto". I think because it is setup in the Online Services -> Personalization string. So far so good. But this "auto" just produces masses of rejected shares, as I just talked with MiniZ. He said we should use "--pers Beam-PoW", so I edited it in the Online Services / Nicehash Personalization String. But if I start the MiniZ miner, it has still the "auto" string flag. This is the command line AM uses:

--par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --pers auto --telemetry 0.0.0.0:4029

As a workaround I can set in the Profit Profile -> Additional command line arguments "--pers Beam-PoW" and it then use it correctly:

--pers Beam-PoW --par 150,5 -l stratum+tcp://beam.eu.nicehash.com:3370 -u xxxxxx.xxx -p x --telemetry 0.0.0.0:4029

Seems like AM ignores the string in Online Services or uses always the auto flag, can you check that please?

I just tested the same, to edit Online Services, Nicehash Personalization string and set it to "Beam-PoW". When I start Miniz miner the next time it shows up with the following command line:
--pers Beam-PoW

Can you please go to the Options dialog, Managed Software section, and check the settings for Miniz Miner to make sure there are no "auto" flags here?

Got the 6.3.3 and did now the 6.3.4 update. With that new version it works  Thanks for your prompt help!

[Burnie]

Hi Patrike,

Feature request...

Would it be possible to allow benchmarking multiple rigs simultaneously when using remote agent? I have two rigs with dissimilar equipment, requiring that they be individually benchmarked. I have a profit profile for each rig. I would like to be able to open multiple benchmarking dialogues at the same time, each one for a specific rig.

Thanks for your consideration,
...jim

I have no problem opening and running multiple benchmarking simultaneously (on Win10).
What kind of problem do you see/have?

hint: select miner1, click "benchmark". select miner2, click "benchmark", and so on.

[Chevy_Roadster]

Hi Patrike

Please add X16r algo (Ravencoin) on miningpoolhub to the online service, thanks a lot and keep your great work!!!!

https://ravencoin.miningpoolhub.com/

[JimBrown462]

Hi Patrike,

Feature request...

Would it be possible to allow benchmarking multiple rigs simultaneously when using remote agent? I have two rigs with dissimilar equipment, requiring that they be individually benchmarked. I have a profit profile for each rig. I would like to be able to open multiple benchmarking dialogues at the same time, each one for a specific rig.

Thanks for your consideration,
...jim

I have no problem opening and running multiple benchmarking simultaneously (on Win10).
What kind of problem do you see/have?

hint: select miner1, click "benchmark". select miner2, click "benchmark", and so on.

Yeah, I figured it out a couple of hours later. Forgot to come back and edit my post.

Thanks,
...jim

[patrike]

Hi Patrike

Please add X16r algo (Ravencoin) on miningpoolhub to the online service, thanks a lot and keep your great work!!!!

https://ravencoin.miningpoolhub.com/

Thanks for the nice feedback. I will add this one in the next release.

[slysir]

Feature request:

Can you please add a Rules- Trigger for Miner power: watts

It is useful to take an Action like "Apply GPU clocking profile" to reduce/increase the power limit.

[trucobit]

There is a small problem with the speed of the fans in Nvida.

Create the rules that when it reaches, for example, 75 degrees, activate the fans to 75%, in fact I have a scale made from more to less, as if it were an MSI Aftherburner curve

But I have noticed that the system sometimes takes the temperature of one and other times of another. I have a rig that now reaches 84 degrees and the fans go to 90%, but suddenly the FANS go down to 75% because it takes the temperature of another card from the same rig.

You can fine tune this so that you only always consider the card with the highest temperature of each rig. It is useless to create temperature rules if sometimes the data is from one card and sometimes it is from another. You must always collect the data for the hottest card rule.

I am preparing the summer, improving extraction, improving card heatsinks and now I am facing this problem. A rig at 84 degrees is set to 90% and then drops to 75% and the card follows 90%, then changes to 90%, and quickly again to 75% without lowering the temperature of the hottest card.

Please Patrike that the rules always take the value of the hottest card or I will finish burning cards.

[trucobit]

At the moment this problem of the OC and temperatures is causing me great problems. there are already two RIGs, the rig of the RTX there is a card, which is more in the background that even reaches 87 and turn off the miner in security.

But I start observing the FAns in GPU, and I see that suddenly I'm at 84 and fans are lowered to 65% because it has picked up the temperature of another card, according to my rules at 84 degrees it would go to 90% fan, and repende is lowered to 65%, because that card reaches the maximum temperature of 87 and turns off the miner.

I hope you have a solution or I will have to drive MSI aftherburner again. But I really like this native solution. You should only take the value of the hottest card in the RIG and do not go changing card reading

At the same time I'm going to have to leave the fixed fans something I do not want, but of course it's a big mistake that I take the temperature data from different cards, so it can not be efficient.

Please, if you are not going to fix it, tell me already and I will change to the old system with Aftherburner or a fixed fan.

[patrike]

Feature request:

Can you please add a Rules- Trigger for Miner power: watts

It is useful to take an Action like "Apply GPU clocking profile" to reduce/increase the power limit.

Thanks for the suggestion. I know that @joseph32 requested something similar a while ago so it's likely to be added in one of the next releases.

[patrike]

At the moment this problem of the OC and temperatures is causing me great problems. there are already two RIGs, the rig of the RTX there is a card, which is more in the background that even reaches 87 and turn off the miner in security.

But I start observing the FAns in GPU, and I see that suddenly I'm at 84 and fans are lowered to 65% because it has picked up the temperature of another card, according to my rules at 84 degrees it would go to 90% fan, and repende is lowered to 65%, because that card reaches the maximum temperature of 87 and turns off the miner.

I hope you have a solution or I will have to drive MSI aftherburner again. But I really like this native solution. You should only take the value of the hottest card in the RIG and do not go changing card reading

At the same time I'm going to have to leave the fixed fans something I do not want, but of course it's a big mistake that I take the temperature data from different cards, so it can not be efficient.

Please, if you are not going to fix it, tell me already and I will change to the old system with Aftherburner or a fixed fan.

The Triggers are currently only passing a list of miners to the Actions, not a list of devices. It's always a miner that is being triggered, not an individual device.

If you have a Trigger configured to look at the device temperature of 85C and one out of 6 GPU's reach this level it will run the Actions defined for the rule. The actions will run with a list of miners produced by the trigger.

The action can be anything like rebooting the computer and setting clocking parameters. The limitation is that the action only know the miner that cause the trigger, not if the trigger itself only fired for a specific GPU.

This is the reason why your trigger condition for a specific device will result in that the actions are executed on a miner level, not device level.

I can agree that it would be good to have a device-concept for the triggers as well. It may however be a bit complex in scenarios where you use multiple triggers and some of them are per-device while other are on a miner level. I don't have any quick solution to this as I need to investigate how this can be supported. It's no quick fix as the entire rule concept would have to be considered, while not breaking anything and keeping backwards compatibility.

Which MSI Afterburner settings are you using to get this behavior in the way you want? I know that Afterburner have the Voltage/Frequency curve dialog and on the 1000-series you only have Frequency/Voltage while the 2000-series GPU's also have Frequency/Temperature. Awesome Miner doesn't have these "curve" features yet.

[trucobit]

At the moment this problem of the OC and temperatures is causing me great problems. there are already two RIGs, the rig of the RTX there is a card, which is more in the background that even reaches 87 and turn off the miner in security.

But I start observing the FAns in GPU, and I see that suddenly I'm at 84 and fans are lowered to 65% because it has picked up the temperature of another card, according to my rules at 84 degrees it would go to 90% fan, and repende is lowered to 65%, because that card reaches the maximum temperature of 87 and turns off the miner.

I hope you have a solution or I will have to drive MSI aftherburner again. But I really like this native solution. You should only take the value of the hottest card in the RIG and do not go changing card reading

At the same time I'm going to have to leave the fixed fans something I do not want, but of course it's a big mistake that I take the temperature data from different cards, so it can not be efficient.

Please, if you are not going to fix it, tell me already and I will change to the old system with Aftherburner or a fixed fan.

One of the two is wrong. Right now, like this one, you do not look at just one card, you look at all of them. Then a card, the hottest one that should be sent, is activated at 90% fan at 80 degrees, but now it turns out that another card of the same rig reaches 75 degrees and I lower the fans to 70% .. Is it more important to reduce 75 degrees or reduce 80 degrees?

Therefore the concept of temperature for a rig, should take into account only 1 card, the hottest. Because the change of speed is applied to ALL THE RIG. If the speed of the fans was independent by card, his vision would be accurate, but as it is not so, it is wrong.

I suppose I could use Atherburner only for the fans, its solution to put rules that jump at different temperatures is not valid. It can not be that I have a card at 84 degrees that would correspond to 100% of FAN, and suddenly because another card of the rig reaches 75 degrees, I lower all the rig to 75% of Fan. Obviously the card that is in 84 degrees will rise and to 86 I turn the miner to avoid problems of breakage by temperature.

Here there are only 3 solutions:

1- that the rules affect each card independently, it would be very good.

2 - Always take the value of the hottest card, this would be the optimal point, that always in the rules send the FAN the card with the highest temperature. This would be the best solution and faster in programming.

3.- re-use Aftherbuner at the same time as the native, only to control the fans.

You understand that as it is now, even with rules, if I have not activated the heat protection rule, I could have damaged cards. I like your native OC a lot, but the temperature should send the card with more heat, whatever it is inside the rig, and just follow that. If suddenly another card in the same rig exceeds the previous one in temperature, then that new card is the one that would take control of the entire RIG. TAl as it is now, yesterday I skipped the rigs every few minutes and they stopped. I could not give credit to my eyes, to see cards at 84 degrees to 100% and suddenly went down to 65% because another card had reached the goal of a rule and applied to the whole rig, that does not matter as you explain it But it's not good.

You give a greater control of fan as aftherburner or you guide by the card of more temperature of the rig, because if not, cards of those people who do not have rules of stopping the miner can be broken if it reaches 86 degrees as I have.

This kind of situations did not happen with the complete solution of aftherburner, although the connection with the main program is very bad, so I will use the native and I will see that I think so, use a fan speed curve in aftherburner, but this is already ahead of time It will be a problem for many as soon as the heat arrives.

[trucobit]

I just tried a rig with native OC + aftherburner for the fans and it's another world. The much lower temperatures.

The temperature change is such that now I can increase the OC, because the temperatures are very low.

It has to improve the temperature system of native OC. I already happened to Aftherburner to control the fans. We are talking about almost 10 degrees less per card with a car curve in Aftherburner.