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

It was enabled. Thanks for your prompt response as always.

Many thanks for the nice review of the new fan curve feature. It's actually a quite basic concept - looking at the individual device temperature and then adjust the fan of each GPU to match the curve you have defined.

Please note that when you enable the fan curve feature, you will no longer be able to adjust the fan in other ways.

The fan curve feature allows a 1% fan speed variation before it changes the fan speed - to reduce the number of fan adjustments. Otherwise you could have changes like 59, 60, 59, 60 very frequently.

If the curve indicates that the fan speed should be 60%, Awesome Miner will not do anything if the current fan speed is between 59% - 61%. It's considered good enough. However, if the current fan speed would be 58% or 62%, Awesome Miner will adjust it to 60%. So if you ever see that the fan speed is 1% different compared to what you expected - this is the reason.

The conditional Clocking Profiles, to support day/night clocking settings, is on the roadmap.

I just tried the fan curve system for OC, and say that it goes silky, perfect, now if you consider each card separately.

Those who use Aftherburner for the fans, you can already remove them. I have already done it and I only use the AM system, the fewer things installed in the rig better.

Thanks Patrike for your continued effort. I'd love to see the double OC night / day, but that's your decision.

Version 6.5.6 (Development preview of 6.6)

 ASIC mining
  - Improved support for Avalon 921 with display of chip temperature and more details
 GPU mining
  - Improved mining software selection where older mining versions can be selected and the supported nVidia CUDA version can be detected
  - Global fan control using a fan/temperature curve with the native overclocking feature. Configurable in the Options dialog, GPU Settings section.
  - Remote Agent on Linux will report nVidia driver version and system memory usage
 Mining software
  - Claymore Ethereum Miner 14.7
  - Ethminer 0.18.0 rc0
  - TeamRedMiner 0.5.2
  - T-Rex Miner 0.12
  - WildRig Miner 0.17.6
 Corrections
  - Added missing Blake2b pools
  - Improved detection of xauthority environment variable on Linux for nVidia clocking


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

I think this is that you are running with Performance Mode enabled (see Options dialog, Advanced section). This one will force "compact list" when you start the application. When running with really large number of miners, the standard List mode is more heavy to update.

Since v6.3.8 my miners view keeps defaulting to "compact list" and I have to reset it to "list"
Is there a way for me to to save my preference?

Hi and thanks for your question. If you want to specify mining software and pool yourself you should create a Managed Miner (not a Managed Profit Miner, which is for profit switching only). The general concept would be:
1) Create the Beam pool just like you did. You should however open the Properties for the pool again and go to the Advanced section and add the additional command line "--ssl 1".
2) Go to the Options dialog, Managed Miner section where you can add a new miner (use the Add button).
3) Specify Gminer as software for the Managed Miner and select your pool.
4) Use the GPU selection to select which GPU's to use for mining by clicking on the Configure button (this will generate the --devices command line automatically)

So the only command line parameter you manually had to enter here was the "--ssl 1" part, required by this specific pool.

Awesome Miner will currently ignore cards where it fails to read any clocking speed information. It should probably include them anyway and I can make that adjustment. However, if the card crashed really badly, it may not even be listed correctly when you query the nVidia driver, and then you will still run into the missing ID problem.

Subvendor (ASUS, MSI, ...) in combination with name (1070, 1080, ...) would make sense to support so I can add this in a future release.

Hi, I am using Awesome miner and Gminer to mine Beam on Leafpool. If I download the Gminer and run the bat file with this command line, there would be no issue (miner.exe --algo 150_5 --server beam-eu.leafpool.com --port 3333 --ssl 1 --user Wallet.User --devices 0 3 4 5). But my issue is with Gminer and Awesome miner. I have added Leafpool to the pool list of Awesome miner and assigned the Gminer to mine equihash 150.5 for Beam. The thing is Gminer follows the pool setting parameters of the pool list, not the additional command arguments! If I put the command in that section, the CMD window gets appear and disappear in a second without showing me and error. If I put the commands in execute batch command section before running the Gminer, miner runs, but it does not read those commands, and only follows the pool setting parameters. I want to the Gminer in Awesome miner to follow my commands, specifically I want it to use Cuda devices only, but it selects both AMD and Nvidia cards at the same time. It does not follow --devices 0 3 4 5 or any optional command.

https://imgur.com/a/48Q5twE

Hey Patrik,

just testing my new boards with 13 cards and the native overclocking, especially the clocking profile groups. Because Afterburner cant handle more than 8 cards.

This is the problem:
- I have a mixed rig with for example 13 cards of 1060s, 1070s and 1080s. One (or more) cards are lost for whatever reason, like crashed, or dropped by windows, or anything else. So only 12 cards are available. The lost card is one of the 1080s with ID 6.
- Because of the lost ID there are only ID 0-11 left. ID 6 is now replaced with another card, for example a 1070 (which was ID 7 previously).
- I have integrated 3 different 1080s clocking profiles into 1 clocking profile group with their ID. Because the 1080 have to clock different and not exactly the same. And I also have different 1060s and 1070s profiles into 1060s and 1070s groups for the same reason.

If now the card with ID 6 is lost, every ID change. The overclocking of AM now clocks the new ID 6 (which is a 1070) with the settings of the 1080 (which is lost). But this will make the system unstable.
Also the GPU selection (in the properties) gets confused and everything gets completely wrong.

I hope you understand, its complicated to describe.

In the clocking profile groups I can edit the GPU expression by the name, but only like 1060, 1070, 1080... So AM would clock every 1080 the same.
Is it somehow possible to edit this expression field more complex? Like nvidia 1080 or asus 1070? If AM cant find that device (because something happend or it is just disabled), then AM just ignors that device for the clocking. AM already can read the GPU details like:
4 (4):GeForce GTX 1080
PCI BusId: 9
PCI Id Device: 7040
PCI Id SubDevice: 0x119E10DE
Subvendor Name: NVIDIA

Dunno if the SubDevice is unique to a specific card. If yes, this would be awesome to use in the expression field. If not, Vendor and Name together would be nice for a good start

PAtrike already sent you 2 internal messages with 3 logs so you have all the possible information.

I'm pretty sure that the failures are causing the latest security version of windows version 1809. It is easy to ask here if those who have older versions of Windows like the 1705 have problems with restarting the machines and if those who have updated the windows today have the problem.

ahh ok I did move the one up and it changed it to more accurate values. Though now I miss it telling me that my LTC miners were making $35 a day, even if it wasnt real lol

Hi Ralf,
Thanks for the update. It more sounds like it's an issue related to the actions (SSH reboot) rather than the trigger. Let's investigate why the reboot operation didn't work.

Can you please contact me via e-mail and provide the Awesome Miner log file (toolbar: Tools -> Log File). Please let me know the time of both the reboot issue above and also when you noticed the miner groups issue.
Thanks!

I will send you a PM in a short while where I will request a few more details on this. Discussion of some log file entries is sometimes better via PM as it doesn't have to be shared with everyone. Thanks!

Good point - I agree that this would make it easier. Your suggestion has been noted and I will consider this for future versions.

Thanks for the update. I do understand that you see all the fan speed values in the View Details window. Awesome Miner do list all properties it get from the ASIC miner here, but Awesome Miner do not understand the meaning of all of them. So a property can have the name like "Fan Speed In", but as this name is made up by the ASIC, Awesome Miner doesn't automatically know that it's related to fan speed.

I do however agree that Awesome Miner can be improved here and allow you to point to any property reported by the ASIC miners, for example the Whatsminer specific properties for fan speed, and display this in the Progress field. This is however not supported today and will require some implementation. But it can for sure be supported in the future. I fully understand your point here. Thanks!

If you for example put WhatToMine on top of CoinCalculators.io in the list, you will see that it most likely will load other exchanges. On the same configuration page you can also configure an Exchange Volume Filter, to exclude low volume exchanges that typically cause these problems. By setting a minimum volume to 0.01 or 0.001 BTC it's more likely to get realistic numbers.

I'm considering to set a minimum exchange volume value by default on new installations, to avoid these issues.

Please also note that Awesome Miner uses the Current coin statistics by default, while the web interfaces of the providers like CoinCalculators may use 24h average values.

Possibly, but it has to be optional.

The drawback I see with automatic software updates is that you will not get a chance to have a quick look at the release notes before upgrading. In almost all cases there is no need to read it, but it could be that we need to include an important message on the first line in the release notes.

Hi Patrike,

i have a second issue with the Version 6.5.5.

now i experince the second time, that some Minergroups are just vanished?!
all the miners out of this group are now located in the default-group.

a new start of AM don't help - i have to create the vanished grougs again and have to check all the rules depending on this groups?!
that's really annoying or better said much work...

can you look into this ASAP? do you need some logfiles?

thank you and BR Ralf

Hi Patrike,

additional detail:
also if i execute the rule through Actions-Button (manual-Activation) the miner is not rebooting - if i reboot through the web-Browser, the miner reboots and work fine again...

BR Ralf