Author

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

legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.5.3

 GPU mining
  - Added setting to specify if Ctrl+C should be used to stop a mining process, configurable in the Options dialog, Mining Settings section
  - Show GPU vendor name for nVidia devices when running Remote Agent on Linux
 Features
  - Access to formatting of hashrate using MH/s and similar units via the Customize Progress Field feature
 User interface
  - Added additional coin icons
  - Display number of miners in the Mining History dialog, Mining Performance section
 Rules
  - Increased the maximum delay allowed to be configured for SSH actions
  - Time trigger to display name of day in the trigger summary if only a single day is selected
 API
  - Added API to set Electricity Price via API
 Mining software
  - TeamRedMiner 0.5
  - WildRig Miner 0.17.4
  - CpuMiner-Opt 3.9.2.3
legendary
Activity: 3346
Merit: 1094
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0

and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ...

Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable.

And having seen that the same thing happens to other people, I insist on the problem.
In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas.

After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner?



The OC of winter I have reduced it by 20% for summer, and I have even tried very low OC to see if it happened and if it happens, that was the first thing I did.

What I have not tried has been to remove the Aftherburner until there is a global FAN solution. I can not be defining a curve in each profile when I have 100 or more, and the heat is heat whatever the protocol.

I will try to remove the Aftherburner from 1 machine, the most prone and force several changes. At first you said that it would not affect but it could be.

I ask for a global Fan curve for each rig, regardless of the protocol. That would help me remove Aftherburner.
Perfect that you lowered the OC for the summer - that makes sense. Over the years I've seen the same trend every time it's May or June - I get reports about mining software crashing more frequently with clocking levels that worked fine a few months earlier.
legendary
Activity: 3346
Merit: 1094
https://www.dropbox.com/s/zynzi5nd4ywsk9s/5.png?dl=0

Another sample of bugs from the native OC.

If we see the capture, RIG3 would be 6x1080ti, gives the hash of 6, gives the consumption of 6 cards, but then the Profit is 1 card, also only gives the temperature of 1 card.

I have created a rule that counts the cards in case of missing only 1 reboot. But the curious thing that marks me the hash and consumption of 6, temperature and profit of only 1. Something is not right.

He has been like this all night and has not done auto switch because he marked a hash he was not getting. But of course the Switch does it for the hash profile of the currency not for the hash obtained, otherwise X16r would skip all the time.

AM could bring a predefined rule to detect dropped devices.

It is not shown that AM does not get the data right, it can not be working only 1 card and the hash of 6 and the consumption of 6 remain. So I can not make a rule like "if it consumes less than X trigger"

This is more related to what GPU's are being reported as active from the mining software rather than being OC related. When you run into this issue where Awesome Miner only includes one temperature reading - the following would be interesting to know:

1) On the GPU tab for this selected miner, how many GPU's are the mining software reporting. Only one, because the other failed in some way?
2) Next time the mining software report something that looks strange, please generate an API report and sent it to me via PM or mail. I can then review what the mining software is reporting.
3) Did the mining software console window indicating that it was only mining on a single GPU or all 6 GPU's where mining perfectly fine?

It's possible that there is some case where GPU's are being partially reported correctly from the mining software and the display in Awesome Miner gives a temperature and power summary that looks strange - but we need the information above in order to really tell if that's the case.
jr. member
Activity: 756
Merit: 2
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0

and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ...

Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable.

And having seen that the same thing happens to other people, I insist on the problem.
In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas.

After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner?



The OC of winter I have reduced it by 20% for summer, and I have even tried very low OC to see if it happened and if it happens, that was the first thing I did.

What I have not tried has been to remove the Aftherburner until there is a global FAN solution. I can not be defining a curve in each profile when I have 100 or more, and the heat is heat whatever the protocol.

I will try to remove the Aftherburner from 1 machine, the most prone and force several changes. At first you said that it would not affect but it could be.

I ask for a global Fan curve for each rig, regardless of the protocol. That would help me remove Aftherburner.
jr. member
Activity: 756
Merit: 2
Code:
Version: 6.5.2
API command: /api/v1/status

I've only had a quick look so far, but the interesting part is the first few lines of the API report. It indicates the API command Awesome Miner sends to the mining software and the line after is the response.

In this case Awesome Miner sends a request to:
http://IpAddressOfTheMiner:4028/api/v1/status

For this mining software the API is based on HTTP. There are other software where non-HTTP connections are used.

The next few lines in the report are empty - indicating that the mining software didn't respond to this request. One you get to the lines further below (starting with "
There are two things you can do to find out why Awesome Miner didn't get any API response from the miner:

1) As this specific mining software happen to run HTTP, you could try to open a web browser and navigate to:
http://IpAddressOfTheMiner:4028/api/v1/status
Replace with the correct IP address of the miner.

This suggestion will however not be applicable for all mining software - which is why the point below can be of interest.

2) You could add an External Miner in Awesome Miner, where you select the mining software you want to connect to and specify the "Remote Host" like:
192.168.0.123:4028
Use the IP address of the Remote Agent computer where the mining is running. The port may not be 4028, please right click on the Managed Miner and select View Details to find the mining software API port number in the command line.

If the External Miner shows up as Disconnected, it's a sign that it's not possible to get any response from the mining software.



I take note of these two urls to execute them when I have problems. But in principle it works, because when you reboot everything goes well, it is when you make some change ... It stops working well.

I have it written down and waiting for a failure to see, or I provoke the failure, I will report the ruling here. But keep in mind that it is not a fixed fault, which is sporadic. Because if it were fixed, it would not work or reboot.
jr. member
Activity: 756
Merit: 2
https://www.dropbox.com/s/zynzi5nd4ywsk9s/5.png?dl=0

Another sample of bugs from the native OC.

If we see the capture, RIG3 would be 6x1080ti, gives the hash of 6, gives the consumption of 6 cards, but then the Profit is 1 card, also only gives the temperature of 1 card.

I have created a rule that counts the cards in case of missing only 1 reboot. But the curious thing that marks me the hash and consumption of 6, temperature and profit of only 1. Something is not right.

He has been like this all night and has not done auto switch because he marked a hash he was not getting. But of course the Switch does it for the hash profile of the currency not for the hash obtained, otherwise X16r would skip all the time.

AM could bring a predefined rule to detect dropped devices.

It is not shown that AM does not get the data right, it can not be working only 1 card and the hash of 6 and the consumption of 6 remain. So I can not make a rule like "if it consumes less than X trigger"
member
Activity: 277
Merit: 23
Hi.
I had another thought along these lines. would it be possible to add support for turning on these wifi activated power switches to turn an ASIC miner on after sun up(for solar users), or during a cheap power period(like this user has) and then off again as needed?
i guess this could be done with a C# script... so to set the asic miner as enabled, then turn the power switch on.
anyone done this?
Hi,
As I don't have too much experience in this area I will only to be able to give a general answer form an Awesome Miner point of view, but hopefully someone else with more experience in this field can give additional details.

There are some power switches that can be controlled via HTTP requests and there are some that requires an command line application to be executed that will send the command to the power plug/switch. I do know that there are a number of users that uses Awesome Miner to interact with different kinds of smart plugs/switches.

From an Awesome Miner point of view you can define your own rules (Options dialog, Rules section) and add them to the Action toolbar button, where you can either have actions to send HTTP requests (Webhook action) or to run an executable. You can also use the rules to schedule these operations to run at a specific time if needed.
This is what i use for reboting ASIC and GPU

https://www.aliexpress.com/item/32960089281.html?spm=2114.search0104.3.15.391c71cdJAc3m1&ws_ab_test=searchweb0_0%2Csearchweb201602_6_10065_10068_319_10059_10884_317_10887_10696_321_322_10084_453_10083_454_10103_10618_10307_537_536%2Csearchweb201603_52%2CppcSwitch_0&algo_expid=4fa1849b-c4f6-44c8-a649-725a218ef69b-2&algo_pvid=4fa1849b-c4f6-44c8-a649-725a218ef69b

There is also a software that you can put on AM server and reboot/power onoff miners
legendary
Activity: 3346
Merit: 1094
Hi.
I had another thought along these lines. would it be possible to add support for turning on these wifi activated power switches to turn an ASIC miner on after sun up(for solar users), or during a cheap power period(like this user has) and then off again as needed?
i guess this could be done with a C# script... so to set the asic miner as enabled, then turn the power switch on.
anyone done this?
Hi,
As I don't have too much experience in this area I will only to be able to give a general answer form an Awesome Miner point of view, but hopefully someone else with more experience in this field can give additional details.

There are some power switches that can be controlled via HTTP requests and there are some that requires an command line application to be executed that will send the command to the power plug/switch. I do know that there are a number of users that uses Awesome Miner to interact with different kinds of smart plugs/switches.

From an Awesome Miner point of view you can define your own rules (Options dialog, Rules section) and add them to the Action toolbar button, where you can either have actions to send HTTP requests (Webhook action) or to run an executable. You can also use the rules to schedule these operations to run at a specific time if needed.
legendary
Activity: 3346
Merit: 1094
New TRM - TeamRedMiner Version 0.5
Thanks for your assistance in collecting all the new/missing algorithm names.
legendary
Activity: 3346
Merit: 1094
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
This miner is supported, at least previous revisions of it.

Even in the past this ASIC has always reported crazy number for the total number or share and total hashrate. What Awesome Miner do is to detect that it's a miner of this kind and then recalculate everything based on each individual ASIC device to get numbers that are accurate.

It might be that more recent revisions of this ASIC is a bit different and Awesome Miner isn't able to detect it correctly. Could you please send me the API report (toolbar: Tools -> API Report) via mail or PM and I will see what changes they might have introduced and how to do another workaround. Thanks!
newbie
Activity: 23
Merit: 0
Hey Patrike,
Is there a way to set the Global Electricity Price (per kWh) via HTTP API?
Thank you!
There are no feature to set the value via API today.

You can set the price via the Rules, where you can use the Action called Set Property. You can for example use the rules to define different electricity prices depending on time or day. Rule actions can also be triggered via the API if needed.

I do understand this doesn't give as much flexibility as having an API method for setting an exact price from an external application. Please let me know if you still prefer the API method and I will look into supporting it when possible. Thanks!
Hey Patrike,

If you could add it to your ever expanding "to-do list" that would be awesome! That would help me a lot!

Here in Texas we have the option to go with a variable rate electricity plan that changes the price per kWh every 5 minutes. I'm currently monitoring the real-time price and have different rules and profiles setup in AM for my miners. For example, if the price per kWh goes crazy, up to say $1.00 /kWh, then my mine basically shuts down until the price drops. If the price goes negative (which happens often at night), the miners will overclock and go nuts!

One more thought that might open up a whole new world of possibilities for AM: What if you gave us the option to pass a variable into AM via API that could be used elsewhere in the application? Maybe just a few empty variable slots (Var1, Var2, Var3, etc.) then those variables could be used as "Triggers" inside a rule. Just a thought.

Thanks again!
The API method for electricity price should be possible to include in the near future as it's only a matter of exposing a feature already available.

Thanks for the suggestion about variables, that would make sense as well. Another concept available already today via the triggers are Miner Tags. You can set Tags on miners via the API and you can have trigger looking at certain tags.




Hi.
I had another thought along these lines. would it be possible to add support for turning on these wifi activated power switches to turn an ASIC miner on after sun up(for solar users), or during a cheap power period(like this user has) and then off again as needed?
i guess this could be done with a C# script... so to set the asic miner as enabled, then turn the power switch on.
anyone done this?
member
Activity: 204
Merit: 10


New TRM - TeamRedMiner Version 0.5
legendary
Activity: 2254
Merit: 2419
EIN: 82-3893490
does AM properly support the bw L21 miners? my AM detected the miners and shows that they are mining but the stats are all wrong - no temps, doesnt show pool info, the accepted shares are in the trillions with zero rejected and zero hw errors - it also does not show the hash rate.
legendary
Activity: 3346
Merit: 1094
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0

and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ...

Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable.

And having seen that the same thing happens to other people, I insist on the problem.
In addition to my previous response about troubleshooting - I also see that you list quite a number of potential problematic areas.

After you made the troubleshooting I suggested earlier - please also consider to try to eliminate all these factors that could have an impact on the overall system stability. What happens if you modify you overclocking to only be a single percent of overclocking (so the overclocking code is used, but doesn't do much)? What happens if you remove all clocking for one of the miners? What happens if you close down Afterburner?

legendary
Activity: 3346
Merit: 1094
Code:
Version: 6.5.2
API command: /api/v1/status

I've only had a quick look so far, but the interesting part is the first few lines of the API report. It indicates the API command Awesome Miner sends to the mining software and the line after is the response.

In this case Awesome Miner sends a request to:
http://IpAddressOfTheMiner:4028/api/v1/status

For this mining software the API is based on HTTP. There are other software where non-HTTP connections are used.

The next few lines in the report are empty - indicating that the mining software didn't respond to this request. One you get to the lines further below (starting with "
There are two things you can do to find out why Awesome Miner didn't get any API response from the miner:

1) As this specific mining software happen to run HTTP, you could try to open a web browser and navigate to:
http://IpAddressOfTheMiner:4028/api/v1/status
Replace with the correct IP address of the miner.

This suggestion will however not be applicable for all mining software - which is why the point below can be of interest.

2) You could add an External Miner in Awesome Miner, where you select the mining software you want to connect to and specify the "Remote Host" like:
192.168.0.123:4028
Use the IP address of the Remote Agent computer where the mining is running. The port may not be 4028, please right click on the Managed Miner and select View Details to find the mining software API port number in the command line.

If the External Miner shows up as Disconnected, it's a sign that it's not possible to get any response from the mining software.

jr. member
Activity: 756
Merit: 2
https://www.dropbox.com/s/k05h0exde8qljrx/4.png?dl=0

and again, and all day like that. That miner has stayed offline, has reboot and it works. But I already said that I reboot too many times a day, every rig more than 20 or 30 times a day, practically every change. Normally they are the Rig3 and 5 that are 1080TI, but also it happens with less frequency in other rigs of RTX, 1070 etc ...

Or the native OC does not go well with administration, the aftherburner influences, I do not know if the others that happen to him have the same aftherburner, or there some different fault, but that makes this has become unstable.

And having seen that the same thing happens to other people, I insist on the problem.
jr. member
Activity: 756
Merit: 2
for a couple of version I have been experiencing a very recurring failure, and almost always happens in the 1080ti rigs. When you change from AL-GO and you go to another currency, the miner mine, I see it in the console but in the AM screen it indicates "Miner offline", but it is working. At the end, the offline mining rule is applied to me, reboot rig and then it works.

It's been happening since the OC was implemented with administrator permissions. It is rare that the miner is mining, but the panel figured as offline, without time, temperature, hash or anything, but in the console you see the miner working. It's clear how the program does not read it, it detects offline, and reboot. It is very uncomfortable.

I see this on one of my mixed 1070/1080 rigs too and very, very rarely on my 1080 Ti rig. So I think its not an issue of 1080 Ti's, but of the used mining software and/or the combination which one will be exited first and which one will be opened right after. Iam sure its T-Rex and/or CryptoDredge, never realized that with different miners.

I deactivated the restart in the Offline-Rule, I only get a message when it happens. Just started logging again and will try to catch that case.


dethating that rule is a patch. Because without a real rig it fails and is offline and you do not detect it, and you are in bed 8 hours, because it is 8 hours of lack of mining.

Also, without these data, they are not reflected in the statistics of the rig. So it's just a patch until stability is again because I guess something Patrike could do to control this problem.
Do you also mainly see this for T-Rex (and possibly CryptoDredge) or is it for all mining software? Based on your other post it sounds like it was mainly for T-Rex, but please confirm if this is the only software you run into these problems.

1) If this is an issue with the API of the mining software, please generate an API report for the miner next time you see the issue (toolbar Tools -> API Report). If the API doesn't respond, Awesome Miner might indicate "Mining" but you don't see any other details. The API Report would be able to confirm if this is the case.

2) (I don't think this second point is relevant in your case, but I leave it here as general information). If you also experience that Awesome Miner considers the miner to have crashed completely while it's still running, please also consider the following:
The Remote Agent log file will indicate the Process ID (PID) when it launches mining software. It will look something like this in the log file "Mining Engine Process started, PID: 11524". If you run into this problem where Awesome Miner doesn't think the mining software is running anymore - could you please compare the PID of the process in the Remote Agent log file with what the Windows Task Manager indicates for the mining software? When all is working fine, they should of course be the same, as Awesome Miner monitors the process with this PID. If no process with this PID is found, Awesome Miner considers it a mining software crash.


I already have the fault. I have tried to ignore it by adding more time to the OFFLINE rule that is by default to leave more margin.

In the screenshots you will see that all the miners have been reset when changing to x16rt but rig3 and rig5 both of 1080ti have failed me. One shows even temperature data but not mine, and the other has remained directly on Offline without doing anything until it has been restarted. After restart it works without problems. Not only does it happen with Trex, it also happens with other miners like cryptodredge, nor do I use a wide variety of miners.

The problem persists even having increased the Offline rule to 6 minutes, time to spare. But the rig ends up restarting.

I attached captures with link to not fill the forum of images and I paste the report of RIG 3, which came to work but badly, and restarted, the RIG5 did not arrive or start the miner. Then it restarts and works as if nothing. This took about two or three weeks, coincides with the administrator changes in the native OC and also coincides with the fact that I use Aftherburner for the fan curve.

I leave the api of RIG 3 that if it worked but badly and re-re-established the same

https://www.dropbox.com/s/ys5rztu2k480w5g/1.png?dl=0

https://www.dropbox.com/s/95jpe8wusodbg8i/2.png?dl=0

After 5 minutes later he has made another change and he has also failed, this is the catch belonging to RIG5 that also the api below is just that image. Look how is OFFLINE in AM, no data, but down in console is undermining or so it seems.

https://www.dropbox.com/s/reedfrb4r344jub/3.png?dl=0

Api for RIG5. Belonging to the previous catch

Version: 6.5.2
API command: /api/v1/status



http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  26
  false
  0
 
 
      -i 21 --no-watchdog -a x16rt -o stratum+tcp://eu.blockmasters.co:3696 -u 3NhW4ZakVjn3FFgbzxG81MwSYzSBEhrKso.rig5 -p c=BTC --api-bind-http 0.0.0.0:4028
    5080
    2019-06-05T14:04:37.5845064Z
    1
    131784
 

 
    Microsoft Windows 10 Pro 64-bit
    DESKTOP-I67T6BB
    false
    false
    602
    589531
    4.7.1
   
     
        Intel Pentium G4400
        2
        1
       
         
            -1
            -1
         

         
            -1
            -1
         

       

       
          -1
          -1
       

       
         
            -1
            -1
         

         
            -1
            -1
         

       

       
          30.769229888916016
          100
       

       
         
            27.218936920166016
            100
         

         
            34.319526672363281
            100
         

       

       
          -1
          -1
       

       
          -1
          -1
       

     

   

   
     
        GeForce GTX 1080 Ti
        Gigabyte
        true
        1
        0
        0
       
          200.69324252820957
          212
       

       
          0.793
          0.812
       

       
          1582
          1620
       

       
          5200
          5200
       

       
          64
          65
       

       
          100
          100
       

       
          3096
          3149
       

       
          81
          82
       

     

     
        GeForce GTX 1080 Ti
        MSI
        true
        3
        1
        1
       
          225.74179722791007
          235
       

       
          0.825
          0.843
       

       
          1708
          1746
       

       
          5200
          5200
       

       
          73
          73
       

       
          99
          100
       

       
          2396
          2450
       

       
          92
          92
       

     

     
        GeForce GTX 1080 Ti
        Gigabyte
        true
        6
        2
        2
       
          198.74162292956834
          210
       

       
          0.812
          0.825
       

       
          1556
          1582
       

       
          5200
          5200
       

       
          71
          71
       

       
          100
          100
       

       
          3440
          3451
       

       
          90
          90
       

     

     
        GeForce GTX 1080 Ti
        NVIDIA
        true
        7
        3
        3
       
          199.47619501371184
          216
       

       
          0.781
          0.825
       

       
          1607
          1708
       

       
          5400
          5400
       

       
          74
          74
       

       
          100
          100
       

       
          1570
          1920
       

       
          93
          93
       

     

     
        GeForce GTX 1080 Ti
        MSI
        true
        8
        4
        4
       
          225.69252474635243
          234
       

       
          0.862
          0.875
       

       
          1733
          1759
       

       
          5200
          5200
       

       
          68
          69
       

       
          99
          100
       

       
          2263
          2304
       

       
          86
          87
       

     

     
        GeForce GTX 1080 Ti
        MSI
        true
        9
        5
        5
       
          222.89175980859869
          238
       

       
          0.85
          0.862
       

       
          1733
          1759
       

       
          5200
          5200
       

       
          64
          64
       

       
          99
          100
       

       
          1899
          2012
       

       
          80
          81
       

     

   

   
      2544947200
      6011482112
   

   
     
        Local Disk (C:\)
        12238794752
        63376977920
     

     
        cache (E:\)
        437055524864
        500105736192
     

   

    419.67
    309C23614AD8
    false
 

  false



http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  26
  Managed
  Rig5
  true
  BtMiner
  Disabled
  0
  CuckaToo31
  5
  4
  0
 
  None
 
 
    0
 

 
  true
  rig5
  22
  false
  Single
  17
 
  309C23614AD8
  true
  11
  Group
  0
  0
  GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

 
  false
 
  false
 
  true
  "Coins/day: " + Math.Round(miningHelper.GetCoinsPerDay(), 4)
 
  false
 
 
 
   
      api-listen
      true
   

   
      api-allow
      W:127.0.0.1/32
   

   
      api-network
      false
   

   
      expiry
      120
   

   
      log
      5
   

   
      queue
      1
   

   
      scan-time
      60
   

   
      temp-hysteresis
      3
   

 

  ConsoleFormat
  Normal
 
  true
  false
  false
  false
 
  0
  true
  0
 
    true
    BtMiner
    CuckaToo31
    Disabled
    false
   
 

  2019-06-04T14:50:24.7028997Z
 
 
  true
 
    712
    744
    571
    390
    188
    770
    864
    759
    870
    869
 

 
   
      NiceHash
      3AYwhcya4KktWxM8BQ47qTNhnXjMsNfpGy
   

   
      BlockMasters
      3NhW4ZakVjn3FFgbzxG81MwSYzSBEhrKso
   

 

 
  false
 
 
  true
  175
  Single
  true
  160
  Single
  All
 
  false
  true
  true
 
    0
    1
    2
    3
    4
    5
 

  false
  false
  false
  true
  true
  false
  -1
  Single
  false
  -1
  Single


jr. member
Activity: 756
Merit: 2
Another PAtrike suggestion. In the OC theme, it is becoming more complete, although I use the Aftherburner fan system.

The OC that is saved is for the whole rig, not card to card. I have some multi-brand rigs and also all the same cards. But it happens that there is always 1 that heats more than others with difference and just that card is the one that marks me the maximums of OC that I can do in that machine.

If you could save OC that you keep the OC for each card separately, I could to that card lower the CORE or Power of source disintinta to the others. That way I could take more advantage of the RIG and above all avoid being stopped by reaching the limit marked by my 84 degrees that only 1 card does, the others may be at 70 degrees or less.

The menu we have it, where we operate on each card separately in the new quick menu, now the ideal would be to save that configuration with the data of each card by independent and many problems solved. I'm lazy to put captures but right now I have a rig with

59 62 78 65 63 66

Obviously the card at 78 degrees is limiting me, if I could make that hot card work less, at least I could be calmer if I did not reach the temperature limit, which almost never arrived, but there is still a lot of summer left. In even the rest of the cards could be slightly raised while under power at 78 degrees, it would have stability and more hash.

I repeat about the OFFLINE in the miners and reboot, almost always the culprit is Trex miner, but I have it with a low intensity and still keeps doing it, every change of currency that implies Trex and be the 1080ti, stays in OFFLINE although is working, after a while the rule, reboot rig and it works, I can restart the rig 20-40 times a day, that is not ideal for the machine or to take advantage of all the time in mining. and this is only happening to me since I activated native OC with administrator, which I need because I use the Limit voltage function to control the power to the cards and not reach the point of heat shutdown, at the same time I reduce TDP and core , but many times there are cards in the same rig that some consume 790 and other 900 mv, with this I put a general limit and I avoid a lot of unnecessary heat.
Right now the only way to apply different fan or clocking settings per GPU is to make use of the "Clocking profile groups" in the Options dialog, GPU Clocking Profiles section. For a Clocking Group you can define that you want one Clocking Profile for GPU 0,1,3,4,5 and another Clocking Profile for GPU 2.

I can agree that it would be nice to have an easier way to setup this (like you refer to as 'new quick menu'), to make this setup process easier. This can be a future improvement.

I also have a question to you about the Fan curve concept, as I've received similar feedback from other users. In recent version of Awesome Miner you can define a Fan/Temperature curve for AMD GPU's, as AMD provides this feature in their recent drivers. For nVidia there are no similar concept and instead it has to become an application feature where for example Awesome Miner could look as the temperature all the time and individually adjust the fan of each GPU based on this. If Awesome Miner would have a global Fan/Temperature concept similar to MSI Afterburner that could work on both AMD and nVidia - would that be useful? Or is there a need for more flexibility than a global setting?

an oversight I have not looked at the ID of the remote, because a priori it's fine. We are talking about the rig is working well and giving the correct information, with which the remote is correct. But when you change the protocol to another there are high chances that it will happen that you stay in Miner offline, although in console you see that it is undermining. IF the remote Agent was wrong, I would always do it at all times, there would never be communication. But without reboot, start using a coin, and suddenly change miner offline but the console is undermining.

Parace more something that has to do with the administrator mode or have to see that something interferes as Aftherburner that I have in each machine set, only for the curve of two points of fans.
jr. member
Activity: 756
Merit: 2
Another PAtrike suggestion. In the OC theme, it is becoming more complete, although I use the Aftherburner fan system.

The OC that is saved is for the whole rig, not card to card. I have some multi-brand rigs and also all the same cards. But it happens that there is always 1 that heats more than others with difference and just that card is the one that marks me the maximums of OC that I can do in that machine.

If you could save OC that you keep the OC for each card separately, I could to that card lower the CORE or Power of source disintinta to the others. That way I could take more advantage of the RIG and above all avoid being stopped by reaching the limit marked by my 84 degrees that only 1 card does, the others may be at 70 degrees or less.

The menu we have it, where we operate on each card separately in the new quick menu, now the ideal would be to save that configuration with the data of each card by independent and many problems solved. I'm lazy to put captures but right now I have a rig with

59 62 78 65 63 66

Obviously the card at 78 degrees is limiting me, if I could make that hot card work less, at least I could be calmer if I did not reach the temperature limit, which almost never arrived, but there is still a lot of summer left. In even the rest of the cards could be slightly raised while under power at 78 degrees, it would have stability and more hash.

I repeat about the OFFLINE in the miners and reboot, almost always the culprit is Trex miner, but I have it with a low intensity and still keeps doing it, every change of currency that implies Trex and be the 1080ti, stays in OFFLINE although is working, after a while the rule, reboot rig and it works, I can restart the rig 20-40 times a day, that is not ideal for the machine or to take advantage of all the time in mining. and this is only happening to me since I activated native OC with administrator, which I need because I use the Limit voltage function to control the power to the cards and not reach the point of heat shutdown, at the same time I reduce TDP and core , but many times there are cards in the same rig that some consume 790 and other 900 mv, with this I put a general limit and I avoid a lot of unnecessary heat.
Right now the only way to apply different fan or clocking settings per GPU is to make use of the "Clocking profile groups" in the Options dialog, GPU Clocking Profiles section. For a Clocking Group you can define that you want one Clocking Profile for GPU 0,1,3,4,5 and another Clocking Profile for GPU 2.

I can agree that it would be nice to have an easier way to setup this (like you refer to as 'new quick menu'), to make this setup process easier. This can be a future improvement.

I also have a question to you about the Fan curve concept, as I've received similar feedback from other users. In recent version of Awesome Miner you can define a Fan/Temperature curve for AMD GPU's, as AMD provides this feature in their recent drivers. For nVidia there are no similar concept and instead it has to become an application feature where for example Awesome Miner could look as the temperature all the time and individually adjust the fan of each GPU based on this. If Awesome Miner would have a global Fan/Temperature concept similar to MSI Afterburner that could work on both AMD and nVidia - would that be useful? Or is there a need for more flexibility than a global setting?


It seems that also occure with Cryptodredge, I have a notification tonight.

Also sometimes there are cards that I have left at 0 hash. I had to do a relay for when it detects 5 minutes with hash or reboot and fixes.

Personally I do not think that they are the miners, as there would be complaints from all the users whether they are AM users or not. Something happens when administering the native OC.

On temperature curve. I personally do not think that a curve is needed for each AL-GO, the heat is heat, be it MTP or X16R. And I only have one curve in Aftherburner, with two points, one empiza in 40 gratos and the other ends in 82 degrees at 100% fan, is a single line with two points. I do not care about the protocol that is mining, the heat is heat, so I think that a general adjustment would be better, although I do not use it, but the other users. I use a single curve of Aftherburner and I have no complaint, I repeat, heat is heat regardless of what one mine.

The problem that was before is that the native OC reads the temperature well but does not send the fans well, could have a card at 76 degrees and the fan only at 60%, insufficient, that's why I put aftherburner. I think that only one curve is valid for the whole mining company, so we did it in afthrburner and there was no problem, I see excessive programming, having to program the fan speed for each OC, it is a bit ad hoc. A single ventilation curve is valid for all protocols. If you put this globally and it works well, I'll be able to remove another aftherburner because I would not need it.

Look at when I fail to remember to get the report out of the api, now I leave a question.

Can this failure of miner offline but that really works and does not read it AM, can be caused by having Aftherburner installed in each RIG, even if only used for fans?
Jump to: