Author

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

jr. member
Activity: 238
Merit: 3
Awesome Miner shows exaggerated pool hashrates for new Nicehash stratums on Online Services tab, they should be at least ~100000x lower.
jr. member
Activity: 58
Merit: 5
Hi Patrike,

I'm using Russian (vnish 3.8.6) of the custom S9 firmware you are offering in the last AwesomeMiner. I want to migrate to your version to support you, but don't want to lose all the setting/tuning I've already done. Is it possible and what is the best way to do it?

P.S. Uploaded your version of the firmware on one machine for testing. All the settings remained the same, but there is something wrong: Antminer keeps restarting every few minutes (the auto tuning part is not activated).
member
Activity: 277
Merit: 23
@Patrik

The AM S9 firmware (vnish) has a pretty precise consumption in logs and monitoring menu, would it be possible for AM to obtain this info directly from miner?

good job on the keystroke feature, this will help a lot
Yes, Awesome Miner can actually read the estimated power usage provided by the firmware API.

In Awesome Miner, please go to the Options dialog, Profitability section, and change "Power usage mode" to "Actual Usage". On new Awesome Miner installations this is the default, but on existing installations it's not. With "Actual Usage" you will get the power usage from the API of the miner instead of the power usage values you manually configured in Awesome Miner.

Thanks for the feedback on the keystroke feature as well!

Just set it up, couple of miners on the web monitor show 1260W on AM 1300W, the rest are in pair with the web monitor
legendary
Activity: 3346
Merit: 1094
Hello,

I'd like to swtich 300 miners S9i on latest official firmware "Working Mode" from normal to hashrate-unchanged - lower voltage. via the web custom command interface.

How would I do it since ssh is locked ?

thank you
With the standard Bitmain firmware, Awesome Miner doesn't have any feature to change the "Working mode" for different hashrate/power levels.

As @nordmann666 and @Lunga Chung correctly pointed out, with the custom firmware for Antminers you can set multiple levels of hashrate/power modes and these can be set via Awesome Miner. More information:
https://www.awesomeminer.com/antminerfirmware

Please let me know if running the custom firmware would be an option for you. Otherwise I can plan for supporting the "Working mode" on Bitmain firmware in the future.

If you need help to enable SSH access or disable the firmware signature check on your Antminers, just let me know and I will of course help out. Awesome Miner can do that on Antminer S9.
legendary
Activity: 3346
Merit: 1094
@Patrik

The AM S9 firmware (vnish) has a pretty precise consumption in logs and monitoring menu, would it be possible for AM to obtain this info directly from miner?

good job on the keystroke feature, this will help a lot
Yes, Awesome Miner can actually read the estimated power usage provided by the firmware API.

In Awesome Miner, please go to the Options dialog, Profitability section, and change "Power usage mode" to "Actual Usage". On new Awesome Miner installations this is the default, but on existing installations it's not. With "Actual Usage" you will get the power usage from the API of the miner instead of the power usage values you manually configured in Awesome Miner.

Thanks for the feedback on the keystroke feature as well!
legendary
Activity: 3346
Merit: 1094
I have a Patrike doubt about the new power temperature system. The first thing I've noticed is that I get more hash. I use both power and core systems. I have the power one at 75 and the Core one at 76 degrees.

Using both systems, power should have more priority than Core.

In the interface I do not define a default power because if not all rigs would start with the same power, but then I see that you have to specify a minimum Power, right now in my case it is 70%.

My question is, I have a rig running at 85 power, when it reaches the target temperature that occurs.

1.- The power falls directly from 85 to 70 (I don't see it right)

2.- When you approach the target temperature, the power is gradually reduced, suppose the case of 5 in 5, which would be 85 is as it was, 80, 75 and finally 70.

The option that I commented is the two, because to make a fall from 85 to 70 it happens that the rig reaches 77 and suddenly falls to 72 degrees, then rises again to 75-77, then falls again.

I should have hysteresis. I don't know if that word exists in English. It is that the system acts a couple of degrees before dropping 5 a degree before the target, wait 30 seconds to see if temperature falls, if not, again lower it 5 degrees, etc. If after reaching the minimum defined by me, in this case 70, and if I have temperature activated also by the core, then at that time the core fall would be activated. OSea first give priority to see if the power drop produces the desired effect, and if you do not get it with my minimum, then pay attention to the Core drop, if defined in the OC.
It's a good job anyway, but I think it lacks this little detail that I tell you.
Thanks for testing out the new feature. It's a bit basic at the moment, but the idea was to give you something to try with to see if the concept is working. I didn't want to implement something too complex in case the entire concept of Power Limit control wasn't found useful.

I fully understand your point about not making too frequent changes and not too large changes. Having multiple multiple temperature targets would also be an improvement. I will look into making some improvement here. Thanks for the feedback!


It really works quite well, now I have the power temperature limit at 74 degrees and the core limit at 76 degrees.

The only thing is that you didn't answer me. Is that if I have set a minimum of 70% and throw a miner at 85% power, if the power drops suddenly from 85 to 70, or it does so little by little and maybe the power stays for example at 75% in time of 70 because it already maintains the temperature.

Really more hash is obtained by reducing power than Core, the only thing I ask is that the power reduction be gradual until the minimum marked. You don't have to hit the 85% jump I'm working at 70%. Going down in 3 or 5 point jumps would be great.

Combine both systems, power and core already, you just have to give it two different temperatures, setting the core temperature higher in case the power reduction is not enough.

It has certainly been a success. The only thing that worries me, is when I gradually lower the power do it every 10 seconds or so, I do not continue fast because it can destabilize the Rig. If for a few moments it exceeds 76 degrees, the core system works, which then cancels itself when the temperature drops again and the power continues to drop to the minimum point I have set.

It would only be going down little by little and with 10-second jumps between them so as not to destabilize the rig, and for me it would already be perfect and leave the problem of forgotten heat, in fact heat is no longer a problem for me nor does it take double oc or anything Both systems simultaneously control the temperature excellently, my congratulations.
The Power Limit will not change in small steps. It can drop from 85 to 70 right away.

I did however introduce two improvments in version 6.8 compared to the development release. You can now define two pair of temperature and power limits instead of one. This makes it possible to define one temperature where the Power Limit should drop to 75% and another temperature where it should drop to 70%. It can make the adjustments a bit smoother. The latest version also uses a 30 second concept where changes will never be applied more often than 30 seconds - to reduce too frequent changes as you had in the development release.
member
Activity: 277
Merit: 23
Hello,

I'd like to swtich 300 miners S9i on latest official firmware "Working Mode" from normal to hashrate-unchanged - lower voltage. via the web custom command interface.

How would I do it since ssh is locked ?

thank you

send him PM or Mail and you will get replay what you have to do (it works)

got 14.5TH with 8.4V/675MHz (1200W) OR 15.6TH at 8.9V/725MHz (1450W)


try 725mhz/8.7V with autotune set to 12h on good ASIC you should get 1380W, also put the target temp on 60c
full member
Activity: 1148
Merit: 132
Awesome Miner version 6.8

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware
 ASIC mining
  - Antminer S15/T15 power mode configuration
 GPU mining
  - GPU power limit control based on temperature, configurable in the Options dialog, GPU Settings section
 Features
  - Keystrokes can be sent to mining software via the Console tab and also via the rule actons (Configurable via the Miner Command action)
  - Miner highlight feature includes 5 additional colors
  - Configurable if a double click on an External Miner should open the ASIC miner web interface. Configurable via the Options dialog, General section.
  - Improved wallet balance feature to handle more data formats
 User interface
  - Antminer&ASIC menu renamed to ASIC tools
  - Temperature sorting improved for miner list in compact mode
 Mining software
  - XmRig CPU 2.99.3 beta incl. RandomXL
  - XmRig AMD 2.14.5
  - CpuMiner-Opt 3.9.6.2
  - Phoenix MIner 4.5c
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer 1.5.3
  - Nanominer integration updated for RandomHash algorithm
  - Bminer 15.7.6
  - CcMiner Zcoin Official 1.1.26
  - Z-enemy miner 2.1


Very nice , I’ll try the random x , when I update today
member
Activity: 363
Merit: 16
Hello,

I'd like to swtich 300 miners S9i on latest official firmware "Working Mode" from normal to hashrate-unchanged - lower voltage. via the web custom command interface.

How would I do it since ssh is locked ?

thank you

send him PM or Mail and you will get replay what you have to do (it works)

got 14.5TH with 8.4V/675MHz (1200W) OR 15.6TH at 8.9V/725MHz (1450W)
newbie
Activity: 13
Merit: 0
Hello,

I'd like to swtich 300 miners S9i on latest official firmware "Working Mode" from normal to hashrate-unchanged - lower voltage. via the web custom command interface.

How would I do it since ssh is locked ?

thank you
member
Activity: 418
Merit: 21
Hey Patrik,

is it somehow possible to use different mining software for different pools?

For example: Mining MTP @ 2Miners with the CCminer and @ Nicehash with T-rex/Cryptodredge.

Dunno how this could be realized without making it to complicated, but maybe you or anyone else have a great idea how.
member
Activity: 277
Merit: 23
@Patrik

The AM S9 firmware (vnish) has a pretty precise consumption in logs and monitoring menu, would it be possible for AM to obtain this info directly from miner?

good job on the keystroke feature, this will help a lot
jr. member
Activity: 756
Merit: 2
I have a Patrike doubt about the new power temperature system. The first thing I've noticed is that I get more hash. I use both power and core systems. I have the power one at 75 and the Core one at 76 degrees.

Using both systems, power should have more priority than Core.

In the interface I do not define a default power because if not all rigs would start with the same power, but then I see that you have to specify a minimum Power, right now in my case it is 70%.

My question is, I have a rig running at 85 power, when it reaches the target temperature that occurs.

1.- The power falls directly from 85 to 70 (I don't see it right)

2.- When you approach the target temperature, the power is gradually reduced, suppose the case of 5 in 5, which would be 85 is as it was, 80, 75 and finally 70.

The option that I commented is the two, because to make a fall from 85 to 70 it happens that the rig reaches 77 and suddenly falls to 72 degrees, then rises again to 75-77, then falls again.

I should have hysteresis. I don't know if that word exists in English. It is that the system acts a couple of degrees before dropping 5 a degree before the target, wait 30 seconds to see if temperature falls, if not, again lower it 5 degrees, etc. If after reaching the minimum defined by me, in this case 70, and if I have temperature activated also by the core, then at that time the core fall would be activated. OSea first give priority to see if the power drop produces the desired effect, and if you do not get it with my minimum, then pay attention to the Core drop, if defined in the OC.
It's a good job anyway, but I think it lacks this little detail that I tell you.
Thanks for testing out the new feature. It's a bit basic at the moment, but the idea was to give you something to try with to see if the concept is working. I didn't want to implement something too complex in case the entire concept of Power Limit control wasn't found useful.

I fully understand your point about not making too frequent changes and not too large changes. Having multiple multiple temperature targets would also be an improvement. I will look into making some improvement here. Thanks for the feedback!


It really works quite well, now I have the power temperature limit at 74 degrees and the core limit at 76 degrees.

The only thing is that you didn't answer me. Is that if I have set a minimum of 70% and throw a miner at 85% power, if the power drops suddenly from 85 to 70, or it does so little by little and maybe the power stays for example at 75% in time of 70 because it already maintains the temperature.

Really more hash is obtained by reducing power than Core, the only thing I ask is that the power reduction be gradual until the minimum marked. You don't have to hit the 85% jump I'm working at 70%. Going down in 3 or 5 point jumps would be great.

Combine both systems, power and core already, you just have to give it two different temperatures, setting the core temperature higher in case the power reduction is not enough.

It has certainly been a success. The only thing that worries me, is when I gradually lower the power do it every 10 seconds or so, I do not continue fast because it can destabilize the Rig. If for a few moments it exceeds 76 degrees, the core system works, which then cancels itself when the temperature drops again and the power continues to drop to the minimum point I have set.

It would only be going down little by little and with 10-second jumps between them so as not to destabilize the rig, and for me it would already be perfect and leave the problem of forgotten heat, in fact heat is no longer a problem for me nor does it take double oc or anything Both systems simultaneously control the temperature excellently, my congratulations.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.8

 Awesome Miner Antminer S9 firmware
  - Better performance and flexible hashrate and power configuration when mining with Antminer S9
  - Integrates with Awesome Miner by providing: LED flash, pause and resume mining in a power efficient way, antivirus scan and apply mining profiles (hashrate and power usage).
  - The features are available via the ASIC tools menu and as rule actions in Awesome Miner
  - Display of power usage
  - SSH access to the Antminer
  - Mining fee 2%
  - Awesome Miner can install this firmware even when the Antminer is locked with signature check and SSH is disabled (contact us for instructions)
  - For more information, see the web site: https://www.awesomeminer.com/antminerfirmware
 ASIC mining
  - Antminer S15/T15 power mode configuration
 GPU mining
  - GPU power limit control based on temperature, configurable in the Options dialog, GPU Settings section
 Features
  - Keystrokes can be sent to mining software via the Console tab and also via the rule actons (Configurable via the Miner Command action)
  - Miner highlight feature includes 5 additional colors
  - Configurable if a double click on an External Miner should open the ASIC miner web interface. Configurable via the Options dialog, General section.
  - Improved wallet balance feature to handle more data formats
 User interface
  - Antminer&ASIC menu renamed to ASIC tools
  - Temperature sorting improved for miner list in compact mode
 Mining software
  - XmRig CPU 2.99.3 beta incl. RandomXL
  - XmRig AMD 2.14.5
  - CpuMiner-Opt 3.9.6.2
  - Phoenix MIner 4.5c
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer 1.5.3
  - Nanominer integration updated for RandomHash algorithm
  - Bminer 15.7.6
  - CcMiner Zcoin Official 1.1.26
  - Z-enemy miner 2.1
legendary
Activity: 3346
Merit: 1094
This bug is pissing me off to no end but I have no idea where the fault is..

You can see below, the first entry is not show temps, accepts, or hashrate. This effects reports, rules, etc, everything. BUT. The miner is working fine! If I click the console command tab everything is happy, it is running fine.
I will investigate and get back to you.
hero member
Activity: 1151
Merit: 528
This bug is pissing me off to no end but I have no idea where the fault is..

You can see below, the first entry is not show temps, accepts, or hashrate. This effects reports, rules, etc, everything. BUT. The miner is working fine! If I click the console command tab everything is happy, it is running fine.


Remote Miner Logs and AM Recent Logs: https://drive.google.com/open?id=18IJGZKAh8Lt0CnSoCWDYjWelbeOoi_py
legendary
Activity: 3346
Merit: 1094
So after using this software for so many years you'd think I'd know the answer to this.. is there a way to unset a miner highlight after a rule/error is cleared?

For example, if miner does not increase accept progress in 8 minutes it is highlighted yellow. If that then ends up increasing, the miner is rebooted, or the notification is cleared, I would want that highlight to be cleared.
BUT
I don't want a blanket rule to clear all highlights.. because other highlights might still apply.. I only want to unset the yellow highlight if the accept increases.. does this make sense? Is this possible?
I fully understand your question and what you are looking for.

There are unfortunately no perfect solution to this, but what you could try out is to add a trigger called "Detect miner API connection established" and then use an action to set the Highlight back to "None". It's not a complete solution for what you are asking for, but if the miner is rebooted and then started again, this rule could at least remove the highlight once the miner is up and running again.
legendary
Activity: 3346
Merit: 1094
I have a Patrike doubt about the new power temperature system. The first thing I've noticed is that I get more hash. I use both power and core systems. I have the power one at 75 and the Core one at 76 degrees.

Using both systems, power should have more priority than Core.

In the interface I do not define a default power because if not all rigs would start with the same power, but then I see that you have to specify a minimum Power, right now in my case it is 70%.

My question is, I have a rig running at 85 power, when it reaches the target temperature that occurs.

1.- The power falls directly from 85 to 70 (I don't see it right)

2.- When you approach the target temperature, the power is gradually reduced, suppose the case of 5 in 5, which would be 85 is as it was, 80, 75 and finally 70.

The option that I commented is the two, because to make a fall from 85 to 70 it happens that the rig reaches 77 and suddenly falls to 72 degrees, then rises again to 75-77, then falls again.

I should have hysteresis. I don't know if that word exists in English. It is that the system acts a couple of degrees before dropping 5 a degree before the target, wait 30 seconds to see if temperature falls, if not, again lower it 5 degrees, etc. If after reaching the minimum defined by me, in this case 70, and if I have temperature activated also by the core, then at that time the core fall would be activated. OSea first give priority to see if the power drop produces the desired effect, and if you do not get it with my minimum, then pay attention to the Core drop, if defined in the OC.
It's a good job anyway, but I think it lacks this little detail that I tell you.
Thanks for testing out the new feature. It's a bit basic at the moment, but the idea was to give you something to try with to see if the concept is working. I didn't want to implement something too complex in case the entire concept of Power Limit control wasn't found useful.

I fully understand your point about not making too frequent changes and not too large changes. Having multiple multiple temperature targets would also be an improvement. I will look into making some improvement here. Thanks for the feedback!
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.7.4 ( Development preview of 6.8 )

 ASIC mining
  - Antminer S15/T15 power mode configuration
 Features
  - Keystrokes can be sent to mining software via the rule actons. Configurable via the Miner Command action.
 Mining software
  - CpuMiner-Opt 3.9.6.2
  - Phoenix Miner integration improved to display share information per GPU
  - Nanominer integration updated for RandomHash algorithm

Can the keystrokes be sent without rules ? like from a menu in the console tab?
I will add it to the Console tab in the next release.
legendary
Activity: 3346
Merit: 1094
When you added the nheqminer, did you add it via the Options dialog, Managed Software section, and configured it with Command Line as compatibility mode? In that case Awesome Miner shouldn't try the API and should understand that it cannot get hashrate/share information.

Yes, I added nheqminer in compatibility mode (EWBF CUDA Zcash Miner) and added additional command line arguments in profit profile properties:
-v -l mine.zergpool.com:3300 -u BTCaddress -t 7 -a 4029 -p c=BTC,ID=NAME
Thanks for the details. The Compatibility Mode provides several options. Have you tried using "None"?
Jump to: