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

[patrike]

@patrike

Z-ENEMY 2.4  From: Dk & Enemy (z-enemy)

IMPORTANT:
For maximum performance make sure you have latest drivers
http://www.nvidia.com/Download/index.aspx

Changes:
-  Fixed high CPU load with latest nVidia drivers, you can expect higher hashrate on the mining rigs with lower end CPUs
-  Fixed nvml.dll load error with latest nVidia drivers

Thanks - I've pushed a software definition update for this.

[GoRdiE]

@patrike


How to get the value of 'buy_price' on this?

{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },

[patrike]

Awesome Miner version 7.2.7

 ASIC mining
  - Support for pool changes on Avalon 10 miners where the standard management interface isn't available
 GPU mining
  - Added Gminer dual mining support
  - Possible to configure empty personalization string for algorithms and software where a default value is used
 Features
  - Awesome Miner can update coin exponential factors and algorithm overrides without having to install a new software version
 Integration
  - Improved Mining Dutch mining information
 Mining software
  - CpuMiner-Opt 3.11.3
  - XmRig 5.5.1
  - Z-enemy Miner 2.4
 Corrections
  - Correction to profit switching calculations for dual mining

[patrike]

How to get the value of 'buy_price' on this?

{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },

I think it should work with:
markets[0].buy_price

The reason for

Code:

[0]

is that markets is an JSON array, starting with

Code:

[

. In your case you pick the first element in the array.

[narousberg]

Hi boss, AM need some improvements
example: I have rig with 8 GPUs, if i use GPU selection and use only 7 GPUs (GPU ID 6 switched off), AM show me in GPU tab this GPU ID order: 0, 1, 2, 3, 4, 5, 6 (that is not correct) it must be: 0, 1, 2, 3, 4, 5, 7
If i check GPU ID in miner (GMiner) console output, GPU ID assigned properly.

And please add "Clone" function to "GPU clocking profile groups" and "Profile groups"

Regards

[GoRdiE]

How to get the value of 'buy_price' on this?

{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },

I think it should work with:
markets[0].buy_price

The reason for

Code:

[0]

is that markets is an JSON array, starting with

Code:

[

. In your case you pick the first element in the array.

Ok. But how to get the value of:

Coin:

Ankh Electrum
buy_price


{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },
        {
            "coin_name": "Ankh Electrum",
            "coin_tck": "0AE",
            "market": "0AE/BTC",
            "buy_price": "0.0000002200",
            "sell_price": "0.0000002300",
            "volume24h": 0,
            "price24hago": "0.0000002200",
            "latest_price": "0.0000002200"
        },
        {
            "coin_name": "ABCMint",
            "coin_tck": "ABCM",
            "market": "ABCM/BTC",
            "buy_price": null,
            "sell_price": "0.0000040000",
            "volume24h": 0,
            "price24hago": "0.0000007500",
            "latest_price": "0.0000007500"
        },

[moppidoo]

Awesome Miner version 7.2.7

 ASIC mining
  - Support for pool changes on Avalon 10 miners where the standard management interface isn't available
 GPU mining
  - Added Gminer dual mining support
  - Possible to configure empty personalization string for algorithms and software where a default value is used
 Features
  - Awesome Miner can update coin exponential factors and algorithm overrides without having to install a new software version
 Integration
  - Improved Mining Dutch mining information
 Mining software
  - CpuMiner-Opt 3.11.3
  - XmRig 5.5.1
  - Z-enemy Miner 2.4
 Corrections
  - Correction to profit switching calculations for dual mining

Thank you Patrike, dual mining with NBMiner now works in profit switcher, one bug though:

The per-algo commandline argument in profit profile does not get parsed to NBMiner during normal mining, it does get parsed during benchmarking however.

Best Regards,

[patrike]

How to get the value of 'buy_price' on this?

{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },

I think it should work with:
markets[0].buy_price

The reason for

Code:

[0]

is that markets is an JSON array, starting with

Code:

[

. In your case you pick the first element in the array.

Ok. But how to get the value of:

Coin:

Ankh Electrum
buy_price


{
    "markets": [
        {
            "coin_name": "Ankh Credit",
            "coin_tck": "0AC",
            "market": "0AC/BTC",
            "buy_price": "0.0000003300",
            "sell_price": "0.0000012300",
            "volume24h": 100,
            "price24hago": "0.0000003300",
            "latest_price": "0.0000003300"
        },
        {
            "coin_name": "Ankh Electrum",
            "coin_tck": "0AE",
            "market": "0AE/BTC",
            "buy_price": "0.0000002200",
            "sell_price": "0.0000002300",
            "volume24h": 0,
            "price24hago": "0.0000002200",
            "latest_price": "0.0000002200"
        },
        {
            "coin_name": "ABCMint",
            "coin_tck": "ABCM",
            "market": "ABCM/BTC",
            "buy_price": null,
            "sell_price": "0.0000040000",
            "volume24h": 0,
            "price24hago": "0.0000007500",
            "latest_price": "0.0000007500"
        },

In this case it works with:
markets[1].buy_price

However, as the order of the coins might change, I think this solution is better:
markets[?(@.coin_name=='Ankh Electrum')].buy_price

[patrike]

Thank you Patrike, dual mining with NBMiner now works in profit switcher, one bug though:

The per-algo commandline argument in profit profile does not get parsed to NBMiner during normal mining, it does get parsed during benchmarking however.

Best Regards,

Thanks for the feedback. I wasn't able to reproduce this issue. I opened the Edit Profit Profile dialog, selected NbMiner as only software and then selected Ethereum and specified the "Additional command line argument" as "--fee 3". When starting the Managed Profit Miner, I do see that "--fee 3" is included.

Please let me know if I misunderstood the scenario.

One note - some profit switching properties are only applied if you actually start the miner, allowing the profit switcher to run once. If you add a command line parameter for an algorithm and just click the Diagnostics button for example - it may not be applied until the profit switcher has processed it.

[patrike]

Hi boss, AM need some improvements
example: I have rig with 8 GPUs, if i use GPU selection and use only 7 GPUs (GPU ID 6 switched off), AM show me in GPU tab this GPU ID order: 0, 1, 2, 3, 4, 5, 6 (that is not correct) it must be: 0, 1, 2, 3, 4, 5, 7
If i check GPU ID in miner (GMiner) console output, GPU ID assigned properly.

Thanks for the feedback. This is an area where I agree that Awesome Miner should be smarter and I intend to improve this. Today you need to use the "Map to system monitoring" dialog on the GPU tab to move GPU#6 to the bottom.

And please add "Clone" function to "GPU clocking profile groups" and "Profile groups"

This is very fast for me to add so you can expect it soon.

[moppidoo]

Thank you Patrike, dual mining with NBMiner now works in profit switcher, one bug though:

The per-algo commandline argument in profit profile does not get parsed to NBMiner during normal mining, it does get parsed during benchmarking however.

Best Regards,

Thanks for the feedback. I wasn't able to reproduce this issue. I opened the Edit Profit Profile dialog, selected NbMiner as only software and then selected Ethereum and specified the "Additional command line argument" as "--fee 3". When starting the Managed Profit Miner, I do see that "--fee 3" is included.

Please let me know if I misunderstood the scenario.

One note - some profit switching properties are only applied if you actually start the miner, allowing the profit switcher to run once. If you add a command line parameter for an algorithm and just click the Diagnostics button for example - it may not be applied until the profit switcher has processed it.

I'll have to try again tomorrow, but I now suspect it's the dual mining implementation with NBMiner, my scenario is when mining ckb+eth, where I needed to specify dual intensity for Ethereum not to lose hashrate and nbminer treated eth as the secondary algo instead of primary. So I input

Code:

 --di 8,8 

for a 2 gpu rig under eaglesong algo instead of eth algo, then I don't see the argument gets parsed to the rig.

[Binary100100]

So I had to transfer 8 of my NVIDIA 1070 cards to my (WIP) rig that already had 3 RX 5700 cards on it because I was having a problem with the PSU on the 1070 rig.
But after I did, everything got all messed up on the GPU tab and it won't display watts for my NVIDIA cards.
As you'll see GPU 0 and 1 (5700 XT) is reading the hashrate of a 1070
GPU 2 (5700 XT) is reading for a 5700 XT (but the right one?)
GPU 5 and 6 are 1070 cards but read the hashrate of my 5700 XT cards
None of the cards 3 - 10 are displaying the wattage.
Advice?

[SiddFan]

Please change MiningPoolHub "Cryptonight-Monero" to "randomx-hub.miningpoolhub.com"  and algo to RandomX, Monero hardforked and MPH stoped mining Electroneum
https://monero.miningpoolhub.com/

[patrike]

So I had to transfer 8 of my NVIDIA 1070 cards to my (WIP) rig that already had 3 RX 5700 cards on it because I was having a problem with the PSU on the 1070 rig.
But after I did, everything got all messed up on the GPU tab and it won't display watts for my NVIDIA cards.
As you'll see GPU 0 and 1 (5700 XT) is reading the hashrate of a 1070
GPU 2 (5700 XT) is reading for a 5700 XT (but the right one?)
GPU 5 and 6 are 1070 cards but read the hashrate of my 5700 XT cards
None of the cards 3 - 10 are displaying the wattage.
Advice?

Could you please click the "View GPU Details" button in this GPU tab and send me the output? Please send via PM or mail because of the size. Thanks!
To some extent the "Map to system monitoring" button can be used to reorder the GPU's, but that will not resolve the missing power display.

[patrike]

Please change MiningPoolHub "Cryptonight-Monero" to "randomx-hub.miningpoolhub.com"  and algo to RandomX, Monero hardforked and MPH stoped mining Electroneum
https://monero.miningpoolhub.com/

Thanks for reporting this - Cryptonight Monero profit switching pool should be removed for MPH.

However, I think the Monero pool here isn't part of the MPH profit switching concept at all - it's just a pool for XMR only.

[Binary100100]

So I had to transfer 8 of my NVIDIA 1070 cards to my (WIP) rig that already had 3 RX 5700 cards on it because I was having a problem with the PSU on the 1070 rig.
But after I did, everything got all messed up on the GPU tab and it won't display watts for my NVIDIA cards.
As you'll see GPU 0 and 1 (5700 XT) is reading the hashrate of a 1070
GPU 2 (5700 XT) is reading for a 5700 XT (but the right one?)
GPU 5 and 6 are 1070 cards but read the hashrate of my 5700 XT cards
None of the cards 3 - 10 are displaying the wattage.
Advice?

Could you please click the "View GPU Details" button in this GPU tab and send me the output? Please send via PM or mail because of the size. Thanks!
To some extent the "Map to system monitoring" button can be used to reorder the GPU's, but that will not resolve the missing power display.

Check your messages. Thanks.

The "map to system monitoring" seems to have something crossed though.
My RX 5700 XT cards are 1780 MHz Memory and the 1070 cards are 4428 MHz. Significant difference. But where is posts the "Performance" is where it's interesting.
GPU 0 is displayed as hashing ETH at 31.42MH/s and GPU 1 is 30.53. Both are 5700 XT cards.
But GPU 2 is a 5700 XT card and hashes at 50.64 MH/s.
GPU 3 is a 1070 which reads properly at 31.66 MH/s
But GPU 5 is a 1070 which is reading at 50.8 MH/s. (Which is impossible. It's obviously a 5700 XT card.) Same with GPU 6.

Regarding the "Map Device Order" I'm thinking that the problem is from the PCI Bus ID:
The order is
PCI Bus ID: 11
PCI Bus ID: 5
PCI Bus ID: 14
PCI Bus ID: 1
PCI Bus ID: 2
PCI Bus ID: 6
PCI Bus ID: 8
...
etc.
Is that normal?

[narousberg]

GMiner1.93 after hardfork of Grin29 impossible to mine on Nicehash, watchdog in miner not activated, all shares are above the target or rejected.

How to enable native GMiner watchdog? Adding "-w 1" not help because  "-w 0" is set internally in AM

[patrike]

So I had to transfer 8 of my NVIDIA 1070 cards to my (WIP) rig that already had 3 RX 5700 cards on it because I was having a problem with the PSU on the 1070 rig.
But after I did, everything got all messed up on the GPU tab and it won't display watts for my NVIDIA cards.
As you'll see GPU 0 and 1 (5700 XT) is reading the hashrate of a 1070
GPU 2 (5700 XT) is reading for a 5700 XT (but the right one?)
GPU 5 and 6 are 1070 cards but read the hashrate of my 5700 XT cards
None of the cards 3 - 10 are displaying the wattage.
Advice?

Could you please click the "View GPU Details" button in this GPU tab and send me the output? Please send via PM or mail because of the size. Thanks!
To some extent the "Map to system monitoring" button can be used to reorder the GPU's, but that will not resolve the missing power display.

Check your messages. Thanks.

The "map to system monitoring" seems to have something crossed though.
My RX 5700 XT cards are 1780 MHz Memory and the 1070 cards are 4428 MHz. Significant difference. But where is posts the "Performance" is where it's interesting.
GPU 0 is displayed as hashing ETH at 31.42MH/s and GPU 1 is 30.53. Both are 5700 XT cards.
But GPU 2 is a 5700 XT card and hashes at 50.64 MH/s.
GPU 3 is a 1070 which reads properly at 31.66 MH/s
But GPU 5 is a 1070 which is reading at 50.8 MH/s. (Which is impossible. It's obviously a 5700 XT card.) Same with GPU 6.

Regarding the "Map Device Order" I'm thinking that the problem is from the PCI Bus ID:
The order is
PCI Bus ID: 11
PCI Bus ID: 5
PCI Bus ID: 14
PCI Bus ID: 1
PCI Bus ID: 2
PCI Bus ID: 6
PCI Bus ID: 8
...
etc.
Is that normal?

Thanks for sharing all details.

For the power usage the nVidia drivers are indicating an error when Awesome Miner query for the power usage. In case you have more mining rigs, is this the only one where you don't get nVidia power usage? If you restart Awesome Miner and select the System tab at the bottom for this miner - do you see any power usage?

For the device ordering - in the dialog "Map to system monitoring" you can manually set the correct order by using the Up and Down arrows (in upper right corner). I do intent do improve how Awesome Miner automatically tries to sort out the ordering of the GPU's, but the difficulty is that many mining software report the hashrate for the GPU's in their own order - and Awesome Miner isn't yet smart enough to sort this out.

[patrike]

GMiner1.93 after hardfork of Grin29 impossible to mine on Nicehash, watchdog in miner not activated, all shares are above the target or rejected.

How to enable native GMiner watchdog? Adding "-w 1" not help because  "-w 0" is set internally in AM

You can manually set the command line parameter "-w 1". It's true that Awesome Miner do add "-w 0" by default, but it will not be added if Awesome Miner see that you already have a "-w" parameter.

For most of the default parameters Awesome Miner set, you can manually override it by setting another value and Awesome Miner will use your parameter value instead.

[narousberg]

we need integration of Nichehash Coockaroom service in AM.
At the moment profit switcher dont get profitability info for this algo.