Author

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

legendary
Activity: 3346
Merit: 1094
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?
legendary
Activity: 3346
Merit: 1094
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.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.5.2

 Features
  - Access to miner power usage via the Customize Progress Field feature


Thank You !!  Grin Grin Any tips on how to make it run the units shown in the performance column ? eg: in Cryptonight KH is good, but on Raven it would be nice if it switches to MH based on the units(KH or MH) reported by the performance column.

Feature Request :
The Power usage mode could be refactored to the Profit Profiles.
Eg:
AMD - Power detection is poor, but based on wall power monitor the power is constant - So need "Static Mode"
Nvidia - Power detection is accurate, So need "Actual GPU Mode(Fallback to Static)"

As of now, the mode is globally fixed, would like to have the flexibility as an override ~~  Cheesy Cheesy
I think it would be easier if Awesome Miner would do the hash unit formatting. I will look into exposing a helper method for that.

Thanks for the additional suggestions as well. It's correct that AMD power usage isn't very accurate, where the AMD drivers reports lower power usage than what you measure from the well. To some extent you can compensate by specifying a percent increase for AMD in Options -> GPU Settings.
legendary
Activity: 3346
Merit: 1094
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.
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.
member
Activity: 418
Merit: 21
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.
member
Activity: 204
Merit: 10
Awesome Miner version 6.5.2

 Features
  - Access to miner power usage via the Customize Progress Field feature


Thank You !!  Grin Grin Any tips on how to make it run the units shown in the performance column ? eg: in Cryptonight KH is good, but on Raven it would be nice if it switches to MH based on the units(KH or MH) reported by the performance column.

Feature Request :
The Power usage mode could be refactored to the Profit Profiles.
Eg:
AMD - Power detection is poor, but based on wall power monitor the power is constant - So need "Static Mode"
Nvidia - Power detection is accurate, So need "Actual GPU Mode(Fallback to Static)"

As of now, the mode is globally fixed, would like to have the flexibility as an override ~~  Cheesy Cheesy
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.
jr. member
Activity: 756
Merit: 2
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.5.2

 Features
  - Access to miner power usage via the Customize Progress Field feature
  - Added a new setting to keep older console output logs (generated when running mining software as Administrator)
 Integration
  - Added support for URL handlers to add External Miners and setting up mining software via web links
 User interface
  - Native overclocking controls available in a new tab GPU Clocking for the selected miner to give faster access to overclocking operaitons.
 Mining software
  - CryptoDredge 0.20.1, including support on Linux
  - GMiner 1.45
  - Nanominer 1.3.4
  - TT-Miner 2.2.5
 Corrections
  - Correction to benchmark feature where it in some scenarios could stop running
  - Correction to NbMiner implementation on Linux
  - Correction to feature for setting Antminer default pools via the web interface when using the Antminer S9 March 2019 firmware
legendary
Activity: 3346
Merit: 1094
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.

legendary
Activity: 3346
Merit: 1094
I think this is a TRM issue about not being consistent in how it closes down when using the X-button. I do get a close down message on my system when I do this - while you don't.

It's quite easy to expose the power usage so I can do that in one of the next versions. You can expect the following to work once available:
status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)

As the Power Usage might be 0 in the very beginning, using the Math.Max operation will ensure that we never go below '1' in assumed power usage.

When you press (X) you trigger a CTRL_CLOSE signal rather than CTRL_BREAK or CTRL_C. This one is a little special under Windows, it will send the signal to all processes connected to the console, then also proceed to kill the process(es) after some timeout.

Only 95% sure about this, but I after a quick test it seems Windows actually proceeds to kill the process after the signal handler(s) for all processes has returned, not after a timeout. We have an async shutdown procedure, i.e. the signal handler just sets a flag and triggers a cond var, then returns, and other threads in the process take care of the shutdown. Unfortunately, Windows kills the process before those threads even have gotten started. Sometimes you'll see the first log message, other times you don't. We need to add a block in the Windows signal handler and don't return before the shutdown has completed, or you can send CTRL_BREAK/CTRL_C or char input 'q' to the process, all those fixes should have the effect of a proper shutdown taking place.

-- K
Many thanks for sharing the details about this close behavior. It's correct that Windows eventually will terminate the process after sending the Close signal, but the software receiving the signal is given some time to terminate in a nice manner.

I've explored the CTRL-C approach a bit, and that would be possible for Awesome Miner to support if neededl. It's a bit more complicated as it's based on a concept where you release and attach console handlers, but should be fully possible.
newbie
Activity: 6
Merit: 0
Hey Patrike,
Is there a way to set the Global Electricity Price (per kWh) via HTTP API?
Thank you!
https://imgur.com/s27p4vJ
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!

member
Activity: 658
Merit: 86

When I stop TeamRedMiner via Awesome Miner, the console window of TeamRedMiner says "Shutting down..." and then it will exit right away. Don't you get any console message at all?

Awesome Miner do have a behavior to kill the mining process if it didn't resond to the first request to shutdown. Maybe you can increase the time Awesome Miner will wait to see if TeamRedMiner just needed a bit more time to close down in a nice manner? Increase the value of: Options -> Mining Settings -> Wait for process before terminating.

Thanks for describing the case about dev fee as well. Awesome Miner doesn't have any feature today to do this on a mining software basis. Some mining software also have different dev fee depending on algorithm.

Yeah in my case, awesome miner does an insta-kill, i tried the timeout but no avail.
I tried closing TRM with a ctrl+c, works normally, the thread shudown and miner closes
I'm not able to reproduce the problem - although I do see that TeamRedMiner terminate very fast, it says "Shutting down" for a very show moment before doing so. Not easy to see that message because the process is so fast.

The fact that TeamRedMiner terminates very fast in your case as welll indicates that it did respond to the friendly Window close message from Awesome Miner. If it didn't respond, the close process would have taken about 5 seconds (configurable) before Awesome Miner took the next action where the process is killed.

To compare with SrbMiner, it says "Releasing GPU resources", but it takes 2 seconds so it's easier to see that message.

Awesome Miner is first sending a friendly request to close the mining window to the mining software - and this is the same for all mining software. You can try the same behavior by closing the mining software with the X-button in the  mining window. When you click X to close the window, it should be the same concept as when Awesome Miner requests to close the mining window. When I try this with TeamRedMiner and SrbMiner, I do get the exact same behavior as when Awesome Miner do it. Could you compare with this as well?

I tried logging the exit process, and confirm that the TRM isnt shutting down normally.
TRM shutdown works only with Ctrl+C and not when clicking close in the CMD windows.

Feature Request : Allow Total miner power usage value as a property in the status object.
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-field
Trying to bring this value to Progess Field
Code:
"Efficiency: " + Math.Round(status.KHashAvg / {{{status.PowerUsage}}}, 2) +" KHash/Watt"

Thanks !!
I think this is a TRM issue about not being consistent in how it closes down when using the X-button. I do get a close down message on my system when I do this - while you don't.

It's quite easy to expose the power usage so I can do that in one of the next versions. You can expect the following to work once available:
status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)

As the Power Usage might be 0 in the very beginning, using the Math.Max operation will ensure that we never go below '1' in assumed power usage.

When you press (X) you trigger a CTRL_CLOSE signal rather than CTRL_BREAK or CTRL_C. This one is a little special under Windows, it will send the signal to all processes connected to the console, then also proceed to kill the process(es) after some timeout.

Only 95% sure about this, but I after a quick test it seems Windows actually proceeds to kill the process after the signal handler(s) for all processes has returned, not after a timeout. We have an async shutdown procedure, i.e. the signal handler just sets a flag and triggers a cond var, then returns, and other threads in the process take care of the shutdown. Unfortunately, Windows kills the process before those threads even have gotten started. Sometimes you'll see the first log message, other times you don't. We need to add a block in the Windows signal handler and don't return before the shutdown has completed, or you can send CTRL_BREAK/CTRL_C or char input 'q' to the process, all those fixes should have the effect of a proper shutdown taking place.

-- K


legendary
Activity: 3346
Merit: 1094
https://github.com/technobyl/CryptoDredge/releases/tag/v0.20.1

CryptoDredge v0.20.1
@CryptoDredge CryptoDredge released this 13 hours ago

Thanks for the notice. There will soon be a new version with this one included.
legendary
Activity: 3346
Merit: 1094
Thanks for the update. I will take another look at this.

It's basically the difficulty to set only specific properties on this Antminer web page - as the page itself requires you to construct about 15 parameters with correct values and if any value is blank it can affect other parameters. Did you have 1, 2 or 3 default pools defined before you run into this issue?


I see the btc.com app for Antminer setup works fine (it can change LPM,ELPM mode and on latest firmware even OC) so until we  resolve this in AM this tool can be handy.

Yes all pools previously where defined via SSH, and after new firmware via web it just the web tool for default mining pools fill's in this data at pool 3 if you left it blank (no need for 3 pools anyway).

The part that I miss the most is ability to manually change mining pools on the fly or via profit switching rule. From this perspective on the latest firmware every time I would need to apply new default and reboot the miner Sad  

Thanks for the details.

I just noticed that the Antminer S9 firmware from May 31st has a new concept for the low power mode settings as well. It's not configured the same was as the previous firmware.

Update: I did identify a case with the Antminer S9 firmware from March where Awesome Miner didn't set the parameters correctly if you only had 1 or 2 default pools defined. I will correct that scenario.
member
Activity: 277
Merit: 23
Thanks for the update. I will take another look at this.

It's basically the difficulty to set only specific properties on this Antminer web page - as the page itself requires you to construct about 15 parameters with correct values and if any value is blank it can affect other parameters. Did you have 1, 2 or 3 default pools defined before you run into this issue?


I see the btc.com app for Antminer setup works fine (it can change LPM,ELPM mode and on latest firmware even OC) so until we  resolve this in AM this tool can be handy.

Yes all pools previously where defined via SSH, and after new firmware via web it just the web tool for default mining pools fill's in this data at pool 3 if you left it blank (no need for 3 pools anyway).

The part that I miss the most is ability to manually change mining pools on the fly or via profit switching rule. From this perspective on the latest firmware every time I would need to apply new default and reboot the miner Sad  
newbie
Activity: 52
Merit: 0
https://github.com/technobyl/CryptoDredge/releases/tag/v0.20.1

CryptoDredge v0.20.1
@CryptoDredge CryptoDredge released this 13 hours ago

Fix MTP issue related to many rejected shares
Improve Argon2d algorithms
Other minor fixes
Assets
10
Pre-release
 v0.20.0
 d26110d
CryptoDredge v0.20.0
@CryptoDredge CryptoDredge released this 7 days ago · 2 commits to master since this release

Improve MTP algorithm
Improve Argon2d algorithm
New Argon2d (NIM) algorithm (Dumb mode only)
Add --hashrate option to set expected hashrate in kh/s and calculate start difficulty (Argon2d (NIM) only)
Add watchdog for Linux
Other minor fixes
legendary
Activity: 3346
Merit: 1094
Hi Patrike,
the blockchain driver will be unrecognized again.
Although I don't recommend to use the AMD Blockchain Beta drivers in general, from what I can see you do get the AMD GPU's listed in Awesome Miner system tab even with this driver. The Native Overclocking will however not work.

Can you please let me know if it's a specific AMD GPU I should verify with, where it's not working in your case? Thanks!
Jump to: