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

The problem I see with the overclock groups is that I should do many, but many. I already have about 100 individual profiles, type

85 90 +400
85 85 +400
85 85 -400

PL - Core - MEM

and they are called like that, and then from each miner in each protocol or AL-GO to be able to choose an OC that just by reading the name on the OC that I am going to apply. But do 100 groups and customize card to card is not an idea, because then a group would only serve for a rig in question, for their cards and their independent oce. At the end there would be many more groups, a lot of extra work

I have no choice but to work with fixed speed, but it seems like a savage to have 80% a whole year a fan, that's why I like the automatic one more. What I propose are two easier solutions for everyone.

At the time of defining an OC, I know that I can choose either fixed or auto, but inside the car there could be a box marked something like "aggressive" where the AUTO is higher than normal. Or a rule that really works in real time with the rig GPU without resigning.

With aftherburner if you changed from auto to manual the fan, it did it without stopping to mine, because you can not do that AM through a rule ?. They have already passed the Nvidia documentation on the commands they use, sure there is a way to do it.

That will allow an automatic use of the fan, and only if a card exceeds the limit, raise the speed to the whole rig, without having to restart mining. Creating Groups is not feasible for me having more than 100 profiles already made of OC, and OC groups are taking into account card by card, which would be many more. There must be something simpler, Just for that reason I'm rethinking Aftherburner although I know it has problems, but I can define an aggressive line of Automatico and leave the problem aside, but then every X time does not work and I have to change the folder The remote server is very messy.

If all my rigs were equal, their option would be valid, but since each rig is different in card and power brands, I can not stop making OC groups that should be customized to that rig, and then other dozens of OC groups to another rig etc ...

Could this be that you have one default SSH username and password defined in the Options dialog, Mining Settings section, and then the SSH action is configured for another password? Leaving the username and password fields blank in the SSH action will result in the default settings being used.

The username and password can also be configured per miner if needed.

If you run into a failure with the reboot, you will typically see some details about the issue in the Awesome Miner log file. You can go to the toolbar Tools -> Log File right after you run into one of these failures to see if you find more details.

When you use the GPU Clocking dialog and select Save As, you can specify which GPU parameters to save to the profile. You can for example save only the fan speed property set to a value like 85%. I can agree that the usability should be improved a bit here.

You can then have a rule to apply this "Fan 85%" clocking profile to a running miner. It will not change the Clocking Profile permanently, but it will change the fan to 85% for a running mining.

It should be possible to use the Clocking Groups to combine different Clocking Profiles as well. Not only about having different Clocking Profiles for different GPU types, but also to apply multiple Clocking Profiles to the same GPU - where one profile could apply Fan speed only and another one the GPU/mem clocking.

If this is the "Device command" action, it's only operations intended for ASIC miners and SgMiner - not for GPU mining in general. This is where you need to apply clocking profiles instead.

Thanks! I was looking too fast at the screenshot in the original question and only noticed the incorrect uptime. I didn't notice the more issue related to the personalization string as you pointed out. The next release of Awesome Miner will correct both these issues.

Hi Patrike
I have a problem with rebooting the external miners through rules. i guess this should have been answered already but the search didn't help and I'm not going to read through 470+ pages.
the problem is when I set rules to reboot my antminer S9 by ssh command->reboot system, the rule is triggered, even the notification which i have set for the action will pop up but the reboot action does not happen. more interesting is, when I select the miner and go through tools-> Antminer & ASIC-> reboot (via SSH), that works and the miner reboots pretty awesome!

would you or any other friend here help me with this problem? or could you please tell me how i should write the custom ssh command for the rule to reboot just like the "reboot (via SSH)" function?

thanks in advance

@Patrike, in the rules, you can know the temperature of the cards and put a rule. But I do not see that it works. The rule can detect the temperature, 80 degrees in my case, and I indicate that the fan works fixed at 80%, but it does not. It seems to me that this one more thought for asic, surely it would have to restart miner in GPU, but to do it also it lowers the temperature and the rule does not shoot.

There some way to do what I indicate, and to apply a fixed speed to all the cards of the rig, without having to restart miner ?, would be an ideal solution for this situation, and summer is near.

It is not feasible to do so, power can be, but it is not appropriate. I have 6 rigs, and I use about 20 Algos. I have established about 100 OC profiles.

What you are saying is that you make another 100 OC profiles with a fixed fan speed. I'm sorry but that's Chinese work.

There must be simpler options than what is proposed, which for an RIG may be worth and even so, there would be several profiles, at least 2 for each SOMETHING.

See the recent dev releases, currently you can already add dynamic updates to difficulty, block reward and soon after next major release addition of nethash, block time + specifying calculation method will follow suit. so soon you can do this all in AM.

hi, you must set --peers auto. See image

https://i.imgur.com/u3qR1ta.jpg

The best is probably to choose 3-4 mining options and switch between them manually. Or example, at night in China, one project is more profitable, and in the afternoon, another. This market is changing very quickly, and automation can fail or be hacked. For large or medium players in this market this is relevant.

Is there a way to add custom coins? I remember there was a script maybe?

It's the mining uptime reported over the MiniZ API that sometimes give very high numbers. I run into the same issue yesterday.
What I will do for the next release is to use the mining uptime calculated by Awesome Miner instead.

Is this the same fan speed behavior explained by @darkneorus here?
https://bitcointalksearch.org/topic/m.50287336

Hi Patrike,

Got some weirdness with MiniZ miner... See pic. Any ideas?

Thanks,
...jim

https://1drv.ms/u/s!Askmi-GpbnHlissLuiCexHRhdytuGw

Use rules, fixed fans and 2 or more profiles. If the temperature reach 70°C for example make a rule to change to another profile with faster fixed fans. I think it is the easiest way. And in my opinion, if you mining, never use automatic fan control.

Well, what a silly problem, I have corrected it, but this poses another problem.

Because using an OC profile with automatic FAN, some cards reach 80 degrees and do not exceed 60% of FAN? it is assumed that at that temperature in automatic, the fan should go much faster than 60%.

We know that in Aftherburner you can create a speed line based on temperature and it would go automatically. Here it does not exist, but there could be a slider button or a number from 1 to 10, where the FANS were more aggressive, that means they go faster than revolutions at a lower temperature, or higher. Being 10 very aggressive and 1 very soft. Or something similar. Because although native OC works very well, its big problem is the automatic control of the fans.

As I say I see more than one card at 80 degrees and the fan at 60%. This happens to me in several cards of different rigs, it is as if some mark of Nvidia is not controlled well. In the capture you can see one at 80 degrees and 60%, but you will see others that have more speed and less temperature. I really do not know how to correct that, unless I use fixed fan speeds

Thanks for the suggestion.

You do have a rule action called "Run profit switching", but there are not really any triggers like those you request. The current Revenue/Profit trigger can only compare with a static value.

It's possible to manually trigger the profit switching to run for the selected miners. You can create a rule and enable "Support manual activation via the toolbar". You can then add the action called "Run profit switching". Not a nice automatic solution, but in case you ever need to force it manually.

The post you quoted is almost 5 years old. It's referring to mining software (CcMiner, Claymore Miner, ...) that often requires a configuration of Anti-virus software to not be considered threat - resulting in that it's being removed after Awesome Miner downloaded them.

Since the last ~2 years Awesome Miner automatically configures exclusions for Windows Defender and since then it's less common to run into these problems.

Thanks for letting me know. I actually found similar information via another source as well. Awesome Miner do already have one way of setting voltage for nVidia, but it's not supported by all nVidia GPU's so this will be a good addition.

It should be fully possible to implement something like this so you can expect this to be available later on.

Thanks for the feedback Ralf. If needed, the Offline Detection could probably be improved to separate these cases if needed. Please let me know your feedback once you tested it a bit. Thanks!