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

darkneorus

jr. member

Activity: 238

Merit: 3

Quote from: patrike on March 26, 2019, 09:45:00 AM

Version 6.2.9 (Development preview of 6.3)

Mining softare
- PhoenixMiner 4.2c, including ProgPow support
- TT-Miner 2.2.0

the auto-generated config for PhoenixMiner+ProgPoW sets wrong protocol type for the pool.

Code:

POOL: stratum+tcp://progpow.mine.zergpool.com:3200, WALLET: wallet, PSW: c=BTC, PROTO: 2, ALLPOOLS: 1

PROTO value should be set to 1 here, also COIN: bci should be added.

patrike

legendary

Activity: 3346

Merit: 1094

Version 6.2.9 (Development preview of 6.3)

ASIC mining
- Updates to Antminer T15 support to include temperatures
Features
- Define custom data sources for coin properties; Difficulty, Block Reward and Exchange rate. Use expressions to load values from any JSON data source.
- Reboot button in main toolbar will be available for External Miners as well, performing a reboot over SSH
- Custom filter expressions configurable per User Group when accessing the local web interface
User interface
- Coins with modified properties will be indicated with a blue color for the coin name on the Coins tab, even when running in Compact List mode
- Updated coin images
Integration
- Adjustments to CuckaRoo29s calculations
- Adjustments to new API for CoinCalculators.io
- Updated Exp. Factor for ARRR coin
Mining softare
- PhoenixMiner 4.2c, including ProgPow support
- TT-Miner 2.2.0
Corrections
- The combinaton of using CoinCalculators.io, non-default exchange rate mode and exchange filtering could result in incorrect exchange rate for BTC.
- Correction to JCE GPU Miner selection of GPUs to use
- Correction to Bminer command line for specific combinations of pool algorithms
- Improved detection of mining software crashes and recovery for the Managed Profit Switcher

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on March 26, 2019, 08:32:58 AM

Quote from: sxemini on March 26, 2019, 07:42:08 AM

Quote from: MoparMiningLLC on March 26, 2019, 07:32:09 AM

also how do i specify different power consumption rates for different miners - when i change it for one asic it changes it for all my asics and they do not all have the same power consumption

You must create different profit profiles.

i have tried - each time leads to me just screwing something up - I am too ignorant in how this works I think.

i also am having so many issues with cloud services due to that the software keeps requiring me to reboot (30 to 40 a day) my miners just to keep them showing up. I had hoped the software would save time of using google remote desktop to view the miners directly -- works perfectly but requires looking at each one separately so time consuming. but I think it might require less time the reboots. the reboots also lead to considerable down time which is a loss of revenue/profit as miner is working but not hashing during reboot (miners are working while AM reports them as offline)

1) You can define one more Profit Profile in the Options dialog, Profit Profile section. If you create a profile called "Antminer S9" for example, you can enter your hashrate and power usage in this profile. Later on you can right click on a miner and select Properties, where you can set the Profile Profile to be the newly created "Antminer S9" profile.
You can of course assign many miners to use the same Profit Profile, as long as they have similar hashrate and power usage.

2) For the Antminer issues you have reported earlier, my recommendation is still to use the Diagnostics feature and check out if the issue could be the pool as suggested by the troubleshooting guide:
https://support.awesomeminer.com/support/solutions/articles/35000094734-troubleshooting-antminer-and-asic-miners

I fully understand that it can be annoying run into these problems, but it's always a good idea to confirm the exact issue to begin with. Based on your description so far, it sounds like the Antminer monitoring interface isn't responding after a while, but it would be good to get a confirmation on that.

sxemini

member

Activity: 1558

Merit: 69

Quote from: MoparMiningLLC on March 26, 2019, 08:32:58 AM

Quote from: sxemini on March 26, 2019, 07:42:08 AM

Quote from: MoparMiningLLC on March 26, 2019, 07:32:09 AM

also how do i specify different power consumption rates for different miners - when i change it for one asic it changes it for all my asics and they do not all have the same power consumption

You must create different profit profiles.

i have tried - each time leads to me just screwing something up - I am too ignorant in how this works I think.

i also am having so many issues with cloud services due to that the software keeps requiring me to reboot (30 to 40 a day) my miners just to keep them showing up. I had hoped the software would save time of using google remote desktop to view the miners directly -- works perfectly but requires looking at each one separately so time consuming. but I think it might require less time the reboots. the reboots also lead to considerable down time which is a loss of revenue/profit as miner is working but not hashing during reboot (miners are working while AM reports them as offline)

Then learn more, read the awesomeminer documentation. 30 to 40 reboots lol XD

Awesomeminer save so much time for me, but you have to understand what you are doing there.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

Quote from: sxemini on March 26, 2019, 07:42:08 AM

Quote from: MoparMiningLLC on March 26, 2019, 07:32:09 AM

also how do i specify different power consumption rates for different miners - when i change it for one asic it changes it for all my asics and they do not all have the same power consumption

You must create different profit profiles.

i have tried - each time leads to me just screwing something up - I am too ignorant in how this works I think.

i also am having so many issues with cloud services due to that the software keeps requiring me to reboot (30 to 40 a day) my miners just to keep them showing up. I had hoped the software would save time of using google remote desktop to view the miners directly -- works perfectly but requires looking at each one separately so time consuming. but I think it might require less time the reboots. the reboots also lead to considerable down time which is a loss of revenue/profit as miner is working but not hashing during reboot (miners are working while AM reports them as offline)

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on March 26, 2019, 07:30:22 AM

Quote from: patrike on March 26, 2019, 04:45:41 AM

Quote from: trucobit on March 25, 2019, 01:57:56 PM

Quote from: patrike on March 25, 2019, 05:43:16 AM

Quote from: trucobit on March 24, 2019, 06:29:02 PM

PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double

I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.

There will be a development release with the new Dynamic Update feature for Coin Properties - it's not that far away now.

You will find the documentation here:
https://support.awesomeminer.com/support/solutions/articles/35000115480-load-coin-properties-from-a-custom-source

For what I read in documentation, there will not be as you indicated above to be able to add an Explorer url or at least the most popular, to read directly the difficulty in real time there. That would be a very important point.

I mention it because you commented it like that before. There is nothing better than reading the difficulty without delay in the explorer of each coin
example

http://explorer.choosebitcash.com/api/getdifficulty

for me there is no better data provider, the vast majority use Inquidus as the default browser. It would be nice to add the difficulty of this source. Because although CC is more accurate than CTM at this point, nothing is more immediate and real than reading the difficulty of the coin explorer. I know that in all you can not do it because of the type of explorer you use, but in 80 or 90% of the coins you can do it.

What changes the most fundamental data is the difficulty, this data to obtain it directly is a very good bonus. I hope everything can be done from the panel and are not options just for the api.

This is fully supported. This is referred to as a "plain value" in the documentation. You can simply enter a URL like the one above and you don't have to enter anything else - and Awesome Miner will load the difficulty based on the response.

Awesome Miner do however not provide any of these URL's for you - you still need to find a data source and then enter the URL in Awesome Miner.

You are correct that the documentation didn't have any specific example for this scenario, so I will add that as well. Please see the updates on the same documentation link. Thanks for your feedback!

GRacias Patrike. If you do not worry, I'm not maimed, I'll set up the explorer's urls. I use intensely AM.

How much more or less do you think that will launch this update?

A development release will be available within the next 1 - 2 hours.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on March 26, 2019, 07:20:01 AM

T15 API log

Thanks for sharing the details. I will include an update for this in the next release.

sxemini

member

Activity: 1558

Merit: 69

Quote from: MoparMiningLLC on March 26, 2019, 07:32:09 AM

also how do i specify different power consumption rates for different miners - when i change it for one asic it changes it for all my asics and they do not all have the same power consumption

You must create different profit profiles.

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

also how do i specify different power consumption rates for different miners - when i change it for one asic it changes it for all my asics and they do not all have the same power consumption

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on March 26, 2019, 04:45:41 AM

Quote from: trucobit on March 25, 2019, 01:57:56 PM

Quote from: patrike on March 25, 2019, 05:43:16 AM

Quote from: trucobit on March 24, 2019, 06:29:02 PM

PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double

I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.

There will be a development release with the new Dynamic Update feature for Coin Properties - it's not that far away now.

You will find the documentation here:
https://support.awesomeminer.com/support/solutions/articles/35000115480-load-coin-properties-from-a-custom-source

For what I read in documentation, there will not be as you indicated above to be able to add an Explorer url or at least the most popular, to read directly the difficulty in real time there. That would be a very important point.

I mention it because you commented it like that before. There is nothing better than reading the difficulty without delay in the explorer of each coin
example

http://explorer.choosebitcash.com/api/getdifficulty

for me there is no better data provider, the vast majority use Inquidus as the default browser. It would be nice to add the difficulty of this source. Because although CC is more accurate than CTM at this point, nothing is more immediate and real than reading the difficulty of the coin explorer. I know that in all you can not do it because of the type of explorer you use, but in 80 or 90% of the coins you can do it.

What changes the most fundamental data is the difficulty, this data to obtain it directly is a very good bonus. I hope everything can be done from the panel and are not options just for the api.

This is fully supported. This is referred to as a "plain value" in the documentation. You can simply enter a URL like the one above and you don't have to enter anything else - and Awesome Miner will load the difficulty based on the response.

Awesome Miner do however not provide any of these URL's for you - you still need to find a data source and then enter the URL in Awesome Miner.

You are correct that the documentation didn't have any specific example for this scenario, so I will add that as well. Please see the updates on the same documentation link. Thanks for your feedback!

GRacias Patrike. If you do not worry, I'm not maimed, I'll set up the explorer's urls. I use intensely AM.

How much more or less do you think that will launch this update?

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

T15 API log

Code:

Version: 6.2.8
API command: config
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1553598484,
      "Code": 45,
      "Msg": "Access denied to 'config' command",
      "Description": "cgminer 4.9.0"
    }
  ],
  "id": 1
}
API command: summary
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1553598484,
      "Code": 11,
      "Msg": "Summary",
      "Description": "cgminer 4.9.0"
    }
  ],
  "SUMMARY": [
    {
      "Elapsed": 52069,
      "GHS 5s": "23726.76",
      "GHS av": 23364.39,
      "Found Blocks": 0,
      "Getworks": 1724,
      "Accepted": 14855,
      "Rejected": 82,
      "Hardware Errors": 2723,
      "Utility": 17.12,
      "Discarded": 27700,
      "Stale": 113,
      "Get Failures": 4,
      "Local Work": 4463721,
      "Remote Failures": 4,
      "Network Blocks": 90,
      "Total MH": 1216536919506.0,
      "Work Utility": 327011.06,
      "Difficulty Accepted": 282197809.0,
      "Difficulty Rejected": 1587839.0,
      "Difficulty Stale": 0.0,
      "Best Share": 744156028,
      "Device Hardware%": 0.001,
      "Device Rejected%": 0.5595,
      "Pool Rejected%": 0.5595,
      "Pool Stale%": 0.0,
      "Last getwork": 1553598483
    }
  ],
  "id": 1
}
API command: privileged
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1553598484,
      "Code": 45,
      "Msg": "Access denied to 'privileged' command",
      "Description": "cgminer 4.9.0"
    }
  ],
  "id": 1
}
API command: devs
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1553598484,
      "Code": 9,
      "Msg": "1 ASC(s)",
      "Description": "cgminer 4.9.0"
    }
  ],
  "DEVS": [
    {
      "ASC": 0,
      "Name": "BTM_SOC",
      "ID": 0,
      "Enabled": "Y",
      "Status": "Alive",
      "Temperature": 0.0,
      "MHS av": 23363938.61,
      "MHS 5s": 22896685.61,
      "Accepted": 14855,
      "Rejected": 82,
      "Hardware Errors": 2723,
      "Utility": 17.12,
      "Last Share Pool": 0,
      "Last Share Time": 1553598480,
      "Total MH": 1216536919506.0,
      "Diff1 Work": 0,
      "Difficulty Accepted": 282197809.0,
      "Difficulty Rejected": 1587839.0,
      "Last Share Difficulty": 19960.0,
      "Last Valid Work": 1553598480,
      "Device Hardware%": 100.0,
      "Device Rejected%": 0.0,
      "Device Elapsed": 52069
    }
  ],
  "id": 1
}
API command: pools
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1553598484,
      "Code": 7,
      "Msg": "3 Pool(s)",
      "Description": "cgminer 4.9.0"
    }
  ],
  "POOLS": [
    {
      "POOL": 0,
      "URL": "stratum+tcp://nya.kano.is:3333",
      "Status": "Alive",
      "Priority": 0,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 1703,
      "Accepted": 14694,
      "Rejected": 81,
      "Discarded": 27560,
      "Stale": 109,
      "Get Failures": 4,
      "Remote Failures": 4,
      "User": "MoparMiningLLC.005",
      "Last Share Time": "0:00:04",
      "Diff": "20K",
      "Diff1 Shares": 0,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 280343569.0,
      "Difficulty Rejected": 1583743.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 19960.0,
      "Has Stratum": true,
      "Stratum Active": true,
      "Stratum URL": "nya.kano.is",
      "Has GBT": false,
      "Best Share": 744156028,
      "Pool Rejected%": 0.5618,
      "Pool Stale%": 0.0
    },
    {
      "POOL": 1,
      "URL": "stratum+tcp://us-east.stratum.slushpool.com:3333",
      "Status": "Alive",
      "Priority": 1,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 15,
      "Accepted": 63,
      "Rejected": 0,
      "Discarded": 72,
      "Stale": 4,
      "Get Failures": 0,
      "Remote Failures": 0,
      "User": "Moparminer.005",
      "Last Share Time": "0:09:15",
      "Diff": "26.2K",
      "Diff1 Shares": 0,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 1166112.0,
      "Difficulty Rejected": 0.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 26248.0,
      "Has Stratum": true,
      "Stratum Active": false,
      "Stratum URL": "",
      "Has GBT": false,
      "Best Share": 1501832,
      "Pool Rejected%": 0.0,
      "Pool Stale%": 0.0
    },
    {
      "POOL": 2,
      "URL": "stratum+tcp://bitcoin.viabtc.com:3333",
      "Status": "Alive",
      "Priority": 2,
      "Quota": 1,
      "Long Poll": "N",
      "Getworks": 6,
      "Accepted": 98,
      "Rejected": 1,
      "Discarded": 68,
      "Stale": 0,
      "Get Failures": 0,
      "Remote Failures": 0,
      "User": "moparminingllc.005",
      "Last Share Time": "12:20:55",
      "Diff": "32.8K",
      "Diff1 Shares": 0,
      "Proxy Type": "",
      "Proxy": "",
      "Difficulty Accepted": 688128.0,
      "Difficulty Rejected": 4096.0,
      "Difficulty Stale": 0.0,
      "Last Share Difficulty": 32768.0,
      "Has Stratum": true,
      "Stratum Active": false,
      "Stratum URL": "",
      "Has GBT": false,
      "Best Share": 655283,
      "Pool Rejected%": 0.5917,
      "Pool Stale%": 0.0
    }
  ],
  "id": 1
}
API command: coin
{
  "STATUS": [
    {
      "STATUS": "E",
      "When": 1553598484,
      "Code": 45,
      "Msg": "Access denied to 'coin' command",
      "Description": "cgminer 4.9.0"
    }
  ],
  "id": 1
}
API command: stats
{
  "STATUS": [
    {
      "STATUS": "S",
      "When": 1553598484,
      "Code": 70,
      "Msg": "CGMiner stats",
      "Description": "cgminer 4.9.0"
    }
  ],
  "STATS": [
    {
      "BMMiner": "4.9.0",
      "Miner": "13.16394.1.3",
      "CompileTime": "Tue Dec 18 11:04:09 CST 2018",
      "Type": "Antminer T15"
    },
    {
      "STATS": 0,
      "ID": "BTM_SOC0",
      "Elapsed": 52069,
      "Calls": 0,
      "Wait": 0.0,
      "Max": 0.0,
      "Min": 99999999.0,
      "GHS 5s": "23726.76",
      "GHS av": 23364.39,
      "Voltage": "19.50",
      "Mode": "H",
      "miner_count": 3,
      "frequency": "",
      "freq1": "496",
      "freq2": "525",
      "freq3": "504",
      "freq4": "0",
      "freq5": "0",
      "freq6": "0",
      "freq7": "0",
      "freq8": "0",
      "fan_num": 2,
      "fan1": 4800,
      "fan2": 4800,
      "fan3": 0,
      "fan4": 0,
      "fan5": 0,
      "fan6": 0,
      "fan7": 0,
      "fan8": 0,
      "temp_num": 3,
      "temp1": 52,
      "temp2": 55,
      "temp3": 52,
      "temp4": 0,
      "temp5": 0,
      "temp6": 0,
      "temp7": 0,
      "temp8": 0,
      "temp9": 0,
      "temp10": 0,
      "temp11": 0,
      "temp12": 0,
      "temp13": 0,
      "temp14": 0,
      "temp15": 0,
      "temp16": 0,
      "temp2_1": 48,
      "temp2_2": 52,
      "temp2_3": 47,
      "temp2_4": 0,
      "temp2_5": 0,
      "temp2_6": 0,
      "temp2_7": 0,
      "temp2_8": 0,
      "temp2_9": 0,
      "temp2_10": 0,
      "temp2_11": 0,
      "temp2_12": 0,
      "temp2_13": 0,
      "temp2_14": 0,
      "temp2_15": 0,
      "temp2_16": 0,
      "temp3_1": 67,
      "temp3_2": 69,
      "temp3_3": 64,
      "temp3_4": 0,
      "temp3_5": 0,
      "temp3_6": 0,
      "temp3_7": 0,
      "temp3_8": 0,
      "temp3_9": 0,
      "temp3_10": 0,
      "temp3_11": 0,
      "temp3_12": 0,
      "temp3_13": 0,
      "temp3_14": 0,
      "temp3_15": 0,
      "temp3_16": 0,
      "temp_pcb1": "33-52-33-52",
      "temp_pcb2": "37-54-37-55",
      "temp_pcb3": "32-49-33-52",
      "temp_pcb4": "-",
      "temp_pcb5": "-",
      "temp_pcb6": "-",
      "temp_pcb7": "-",
      "temp_pcb8": "-",
      "temp_pcb9": "-",
      "temp_pcb10": "-",
      "temp_pcb11": "-",
      "temp_pcb12": "-",
      "temp_pcb13": "-",
      "temp_pcb14": "-",
      "temp_pcb15": "-",
      "temp_pcb16": "-",
      "temp_chip1": "48-67-48-67",
      "temp_chip2": "52-69-52-70",
      "temp_chip3": "47-64-48-67",
      "temp_chip4": "-",
      "temp_chip5": "-",
      "temp_chip6": "-",
      "temp_chip7": "-",
      "temp_chip8": "-",
      "temp_chip9": "-",
      "temp_chip10": "-",
      "temp_chip11": "-",
      "temp_chip12": "-",
      "temp_chip13": "-",
      "temp_chip14": "-",
      "temp_chip15": "-",
      "temp_chip16": "-",
      "freq_avg1": 0.0,
      "freq_avg2": 0.0,
      "freq_avg3": 0.0,
      "freq_avg4": 0.0,
      "freq_avg5": 0.0,
      "freq_avg6": 0.0,
      "freq_avg7": 0.0,
      "freq_avg8": 0.0,
      "freq_avg9": 0.0,
      "freq_avg10": 0.0,
      "freq_avg11": 0.0,
      "freq_avg12": 0.0,
      "freq_avg13": 0.0,
      "freq_avg14": 0.0,
      "freq_avg15": 0.0,
      "freq_avg16": 0.0,
      "total_rateideal": 23000.0,
      "total_freqavg": 0.0,
      "total_acn": 180,
      "total_rate": 23726.76,
      "chain_rateideal1": 0.0,
      "chain_rateideal2": 0.0,
      "chain_rateideal3": 0.0,
      "chain_rateideal4": 0.0,
      "chain_rateideal5": 0.0,
      "chain_rateideal6": 0.0,
      "chain_rateideal7": 0.0,
      "chain_rateideal8": 0.0,
      "chain_rateideal9": 0.0,
      "chain_rateideal10": 0.0,
      "chain_rateideal11": 0.0,
      "chain_rateideal12": 0.0,
      "chain_rateideal13": 0.0,
      "chain_rateideal14": 0.0,
      "chain_rateideal15": 0.0,
      "chain_rateideal16": 0.0,
      "temp_max": 55,
      "Device Hardware%": 0.001,
      "no_matching_work": 2723,
      "chain_acn1": 60,
      "chain_acn2": 60,
      "chain_acn3": 60,
      "chain_acn4": 0,
      "chain_acn5": 0,
      "chain_acn6": 0,
      "chain_acn7": 0,
      "chain_acn8": 0,
      "chain_acn9": 0,
      "chain_acn10": 0,
      "chain_acn11": 0,
      "chain_acn12": 0,
      "chain_acn13": 0,
      "chain_acn14": 0,
      "chain_acn15": 0,
      "chain_acn16": 0,
      "chain_acs1": " oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo",
      "chain_acs2": " oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo",
      "chain_acs3": " oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooo",
      "chain_acs4": "",
      "chain_acs5": "",
      "chain_acs6": "",
      "chain_acs7": "",
      "chain_acs8": "",
      "chain_acs9": "",
      "chain_acs10": "",
      "chain_acs11": "",
      "chain_acs12": "",
      "chain_acs13": "",
      "chain_acs14": "",
      "chain_acs15": "",
      "chain_acs16": "",
      "chain_hw1": 203,
      "chain_hw2": 509,
      "chain_hw3": 2011,
      "chain_hw4": 0,
      "chain_hw5": 0,
      "chain_hw6": 0,
      "chain_hw7": 0,
      "chain_hw8": 0,
      "chain_hw9": 0,
      "chain_hw10": 0,
      "chain_hw11": 0,
      "chain_hw12": 0,
      "chain_hw13": 0,
      "chain_hw14": 0,
      "chain_hw15": 0,
      "chain_hw16": 0,
      "chain_rate1": "7564.42",
      "chain_rate2": "8312.06",
      "chain_rate3": "7850.28",
      "chain_rate4": "",
      "chain_rate5": "",
      "chain_rate6": "",
      "chain_rate7": "",
      "chain_rate8": "",
      "chain_rate9": "",
      "chain_rate10": "",
      "chain_rate11": "",
      "chain_rate12": "",
      "chain_rate13": "",
      "chain_rate14": "",
      "chain_rate15": "",
      "chain_rate16": "",
      "chain_xtime1": "{}",
      "chain_xtime2": "{}",
      "chain_xtime3": "{}",
      "chain_offside_1": "0",
      "chain_offside_2": "0",
      "chain_offside_3": "0",
      "chain_opencore_1": "0",
      "chain_opencore_2": "0",
      "chain_opencore_3": "0",
      "miner_version": "13.16394.1.3",
      "miner_id": "80308d801c208814"
    }
  ],
  "id": 1
}

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: danielocdh on March 25, 2019, 05:25:52 PM

So I was finally able to catch and collect data on the miners stopping issue I had before.

Both miners are managed profit miners.
The "offline detection" emails were sent at around 11:16:20 (as expected/configured).
The status on the awesome miner manager was "Stopped" (at around 14:40).
There wasn't any miner software running when I VNCed to the miner (at around 14:40).
The miners can mine Equihash 150,5 correctly most of the time(with gminer).
If I'm reading the logs correctly I think awesome miner used bminer but it is configured to use gminer for Equihash 150,5.
I tested setting it to bminer for Equihash 150,5, screenshot below.

I replaced my bitcoin addresses for "xxx" on the logs.
I replaced repeated "nVidia driver version" entries for "..." on the logs.
On the screenshots Z270XP1 uses profit profile 1070-1, Z270XP3 uses profit profile 1070-3

screenshots:
https://imgur.com/a/zr85dwb

logs:
https://pastebin.com/Lzxh4T2Y
https://pastebin.com/AXpRk6mm

I understand the miner software tried to restart 3 times (as configured), I'm not sure what failed but I think awesome miner should just keep going, jump to the next algorithm(retry again x times if needed) or something like that.

Is there any reason bminer was used for Equihash 150,5 when gminer is configured? or maybe I'm misreading the logs?

Thanks

Thanks for the details.

Would it also be possible for your to send me the Awesome Miner log file for the same period of time (around 25/3/2019 11:13)? Please send the log file by mail to make sure no sensitive information is shared. Thanks!

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: MoparMiningLLC on March 25, 2019, 02:17:42 PM

any way to add support to read temps for the Antminer T15's? I can see it when directly on miner UI but AM reads temps as zero.

Can you please send me the API report for this miner and I can review and correct the problem. Please select the T15 miner and go to the toolbar Tools -> API Report and send me the output via mail or PM. Thanks!

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on March 25, 2019, 01:57:56 PM

Quote from: patrike on March 25, 2019, 05:43:16 AM

Quote from: trucobit on March 24, 2019, 06:29:02 PM

PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double

I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.

There will be a development release with the new Dynamic Update feature for Coin Properties - it's not that far away now.

You will find the documentation here:
https://support.awesomeminer.com/support/solutions/articles/35000115480-load-coin-properties-from-a-custom-source

For what I read in documentation, there will not be as you indicated above to be able to add an Explorer url or at least the most popular, to read directly the difficulty in real time there. That would be a very important point.

I mention it because you commented it like that before. There is nothing better than reading the difficulty without delay in the explorer of each coin
example

http://explorer.choosebitcash.com/api/getdifficulty

for me there is no better data provider, the vast majority use Inquidus as the default browser. It would be nice to add the difficulty of this source. Because although CC is more accurate than CTM at this point, nothing is more immediate and real than reading the difficulty of the coin explorer. I know that in all you can not do it because of the type of explorer you use, but in 80 or 90% of the coins you can do it.

What changes the most fundamental data is the difficulty, this data to obtain it directly is a very good bonus. I hope everything can be done from the panel and are not options just for the api.

This is fully supported. This is referred to as a "plain value" in the documentation. You can simply enter a URL like the one above and you don't have to enter anything else - and Awesome Miner will load the difficulty based on the response.

Awesome Miner do however not provide any of these URL's for you - you still need to find a data source and then enter the URL in Awesome Miner.

You are correct that the documentation didn't have any specific example for this scenario, so I will add that as well. Please see the updates on the same documentation link. Thanks for your feedback!

danielocdh

newbie

Activity: 22

Merit: 0

So I was finally able to catch and collect data on the miners stopping issue I had before.

Both miners are managed profit miners.
The "offline detection" emails were sent at around 11:16:20 (as expected/configured).
The status on the awesome miner manager was "Stopped" (at around 14:40).
There wasn't any miner software running when I VNCed to the miner (at around 14:40).
The miners can mine Equihash 150,5 correctly most of the time(with gminer).
If I'm reading the logs correctly I think awesome miner used bminer but it is configured to use gminer for Equihash 150,5.
I tested setting it to bminer for Equihash 150,5, screenshot below.

I replaced my bitcoin addresses for "xxx" on the logs.
I replaced repeated "nVidia driver version" entries for "..." on the logs.
On the screenshots Z270XP1 uses profit profile 1070-1, Z270XP3 uses profit profile 1070-3

screenshots:
https://imgur.com/a/zr85dwb

logs:
https://pastebin.com/Lzxh4T2Y
https://pastebin.com/AXpRk6mm

I understand the miner software tried to restart 3 times (as configured), I'm not sure what failed but I think awesome miner should just keep going, jump to the next algorithm(retry again x times if needed) or something like that.

Is there any reason bminer was used for Equihash 150,5 when gminer is configured? or maybe I'm misreading the logs?

Thanks

MoparMiningLLC

legendary

Activity: 2254

Merit: 2419

EIN: 82-3893490

any way to add support to read temps for the Antminer T15's? I can see it when directly on miner UI but AM reads temps as zero.

trucobit

jr. member

Activity: 756

Merit: 2

Quote from: patrike on March 25, 2019, 05:43:16 AM

Quote from: trucobit on March 24, 2019, 06:29:02 PM

PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double

I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.

There will be a development release with the new Dynamic Update feature for Coin Properties - it's not that far away now.

You will find the documentation here:
https://support.awesomeminer.com/support/solutions/articles/35000115480-load-coin-properties-from-a-custom-source

For what I read in documentation, there will not be as you indicated above to be able to add an Explorer url or at least the most popular, to read directly the difficulty in real time there. That would be a very important point.

I mention it because you commented it like that before. There is nothing better than reading the difficulty without delay in the explorer of each coin
example

http://explorer.choosebitcash.com/api/getdifficulty

for me there is no better data provider, the vast majority use Inquidus as the default browser. It would be nice to add the difficulty of this source. Because although CC is more accurate than CTM at this point, nothing is more immediate and real than reading the difficulty of the coin explorer. I know that in all you can not do it because of the type of explorer you use, but in 80 or 90% of the coins you can do it.

What changes the most fundamental data is the difficulty, this data to obtain it directly is a very good bonus. I hope everything can be done from the panel and are not options just for the api.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: Sibtigr on March 24, 2019, 10:43:07 PM

Patrick
Describe in more detail the process of installing a second agent on a computer to create a manga CPU and GPU on a single computer

The general concept is that you run the Awesome Miner main application on one computer, and on all other mining computers where you want to do GPU/CPU mining you install one instance of Remote Agent per mining computer.

When you have installed and started the Remote Agent application on the mining computer(s), you can use the "New miner" button in the toolbar to add one or many GPU/CPU mining instances for this mining computer. When selecting "Managed Miner" or "Managed Profit Miner" in the wizard, you can define "Miner host" where you can add a new entry pointing to your remove mining computer.

You can create one Managed Miner for GPU mining and another Managed Miner for CPU mining. Both point to the same "Miner host" where Remote Agent is running.

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: trucobit on March 24, 2019, 06:29:02 PM

PAtrike this like crazy waiting for your update, where we can specify the url of the Explorer and get the direct difficulty. Today I have been mining a coin, which days ago if the difficulty worked well, but today it stops at a predetermined value and the profit is very high. I have mined badly, that coin has been put and then the difficulty with the coin explorer was more than double

I hope you give priority to that new function, because it is sorely needed. Any function that helps obtain such fundamental data well, will be a great improvement. And I think that right now is the most important for AM, from my point of view.

There will be a development release with the new Dynamic Update feature for Coin Properties - it's not that far away now.

You will find the documentation here:
https://support.awesomeminer.com/support/solutions/articles/35000115480-load-coin-properties-from-a-custom-source

patrike

legendary

Activity: 3346

Merit: 1094

Quote from: darkneorus on March 23, 2019, 06:11:16 PM

@patrike besides that I would suggest adding core voltage lock to NVIDIA clocking profiles. that should be easy to implement, with just one NvAPI call.

also I've found a bug with native OC on mixed AMD/NVIDIA rigs - in my case, when applying the profiles for AMD GPUs, some of them like fan speed, fan mode and power limit are applied to NVIDIAs as well.

Thanks for the suggestions.

I'm actually not familiar with this NVAPI call related to core voltage lock. Do you have any more information about this feature?

If you have a Clocking Profile that contains properties supported by both AMD and nVidia (fan speed and a few more), they will be applied to all GPU's that support these properties. A profile is not specific for AMD or nVidia, it's just a number of GPU properties to be set. You may need to define Group Clocking Profiles on mixed systems, where you define that one Clocking Profile should be applied to the AMD cards and another one to the nVidia cards.

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