Pages:
Author

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

legendary
Activity: 1753
Merit: 1007
@patrike
Hi boss, i have problems with firmware replace on my Antminer L3+, actually i have installed original Bitmain firmware 10 July 2019
I have tried different methods with SD card (yours and Bitmains tool), but nothing help, i cant replace firmware (Cant find signature error). And no SSH ((((
Maybe someone know a trick.
Regards
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 7.5.4

 Features
  - Display of power efficiency in the miner list and displayed as an average per miner group. Configurable in the Options dialog, General section.
 Mining software
  - TT-miner 4.0.0
  - XmRig 5.11.1
 Corrections
  - Correction to triggers detecting the current Firmware Mining Profile for Antminer S17/T17
  - Correction to profit factors calculations for user defined pools in specific scenarios
legendary
Activity: 3346
Merit: 1094
Hi, guys. Does AMD wattage consumption is shown being core only? Or it includes memory
The AMD drivers reports a power usage of the Core only, so it's lower than the actual value. The nVidia drivers on the other hand are reporting more realistic numbers that represents the entire card.

What we do for AMD to make the number a bit more realistic is to increase it by 35% by default. So if the AMD drivers tells us that a card consume 100W, we display that as 135W by default in Awesome Miner as it's closer to the true usage. This is configurable in the Options dialog, GPU Settings section.
legendary
Activity: 3346
Merit: 1094
I am having a small problem with Awesome Miner when I update it. I have 2 machines with one GPU each. When I update Awesome Miner it does not stop the local miner. After the update Awesome Miner detects the remote miner and reconnects to it. Unfortunately it does not detect the local miner, so it starts a new instance of it. I have to either stop the miner before I update, or use task manager to kill the old miner instance after the update. Will you please look into this? Thank you.
Thanks for your report. Are you able to reproduce this problem if you have local mining running and you exit and then restart Awesome Miner? Or only during upgrades?
Thank you for your response. I tried exiting and then restarting Awesome Miner, and it does the same thing. It does not seem to matter what miner is running.
I'm not able to reproduce this issue. May I ask for your Awesome Miner log file (toolbar: Tools -> Log File). Please send via e-mail or https://www.awesomeminer.com/contact
jr. member
Activity: 236
Merit: 1
Hi, guys. Does AMD wattage consumption is shown being core only? Or it includes memory
newbie
Activity: 15
Merit: 0
I am having a small problem with Awesome Miner when I update it. I have 2 machines with one GPU each. When I update Awesome Miner it does not stop the local miner. After the update Awesome Miner detects the remote miner and reconnects to it. Unfortunately it does not detect the local miner, so it starts a new instance of it. I have to either stop the miner before I update, or use task manager to kill the old miner instance after the update. Will you please look into this? Thank you.
Thanks for your report. Are you able to reproduce this problem if you have local mining running and you exit and then restart Awesome Miner? Or only during upgrades?
Thank you for your response. I tried exiting and then restarting Awesome Miner, and it does the same thing. It does not seem to matter what miner is running.
legendary
Activity: 3346
Merit: 1094
I am having a small problem with Awesome Miner when I update it. I have 2 machines with one GPU each. When I update Awesome Miner it does not stop the local miner. After the update Awesome Miner detects the remote miner and reconnects to it. Unfortunately it does not detect the local miner, so it starts a new instance of it. I have to either stop the miner before I update, or use task manager to kill the old miner instance after the update. Will you please look into this? Thank you.
Thanks for your report. Are you able to reproduce this problem if you have local mining running and you exit and then restart Awesome Miner? Or only during upgrades?
newbie
Activity: 15
Merit: 0
I am having a small problem with Awesome Miner when I update it. I have 2 machines with one GPU each. When I update Awesome Miner it does not stop the local miner. After the update Awesome Miner detects the remote miner and reconnects to it. Unfortunately it does not detect the local miner, so it starts a new instance of it. I have to either stop the miner before I update, or use task manager to kill the old miner instance after the update. Will you please look into this? Thank you.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 7.5.3

 Features
  - Added HTTP API for modifying configuration file properties on Antminers
  - The Information column can include power efficiency expressed as Watt/TH
  - Show Antminer firmware date on the Summary tab for a selected miner
  - The use of MiningWorker variable in the pool password field can be used even when 'Add to worker name' is disabled on the miner
 Mining software
 - CpuMiner-Opt 3.12.8.1
  - XmRig 5.11
newbie
Activity: 52
Merit: 0
Hi Patrike,

we have now another problem in the current version.

in the pool properties under Advanced we entered a Profit factor (for some Pools) of - for example 0,49 - but this factor is now not effective anymore?! if we change to 1 nothing happens?!

BR Ralf
Hi Ralf,

Please select this miner in the list of miners and click on the Pools tab at the bottom of the screen. Do you see the pool description, as defined in Awesome Miner, here? Or only the Pool URL?

An ASIC miner is reporting a pool URL and worker name and Awesome Miner is trying to match this with the pool you have defined in Awesome Miner. If the URL and worker name are the same, it's a match. Once matched, Awesome Miner can apply Profit Factors defined on the pool.

Thanks!

Hi Patrike,

the pool description is exactly matching with the AM-Pool
we also checked the ignore the miner property: add to worker name in the Advanced definition of the pool
but still no success...

BR Ralf
Hi Ralf,

Can you please send me the API report for this miner (toolbar: Tools -> API Report) together with your Awesome Miner configuration file (%appdata%\AwesomeMiner\ConfigData.xml)? I would need to review the complete scenario in order to find out what causing the problem. Please send these details via mail (or Contact Us on the web site).

I assume it's the Revenue/Profit display in the miner list that doesn't take the Profit Factor into consideration correctly?

Thanks!

Hi Patrike,

i just sent you the files...

BR Ralf
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

we have now another problem in the current version.

in the pool properties under Advanced we entered a Profit factor (for some Pools) of - for example 0,49 - but this factor is now not effective anymore?! if we change to 1 nothing happens?!

BR Ralf
Hi Ralf,

Please select this miner in the list of miners and click on the Pools tab at the bottom of the screen. Do you see the pool description, as defined in Awesome Miner, here? Or only the Pool URL?

An ASIC miner is reporting a pool URL and worker name and Awesome Miner is trying to match this with the pool you have defined in Awesome Miner. If the URL and worker name are the same, it's a match. Once matched, Awesome Miner can apply Profit Factors defined on the pool.

Thanks!

Hi Patrike,

the pool description is exactly matching with the AM-Pool
we also checked the ignore the miner property: add to worker name in the Advanced definition of the pool
but still no success...

BR Ralf
Hi Ralf,

Can you please send me the API report for this miner (toolbar: Tools -> API Report) together with your Awesome Miner configuration file (%appdata%\AwesomeMiner\ConfigData.xml)? I would need to review the complete scenario in order to find out what causing the problem. Please send these details via mail (or Contact Us on the web site).

I assume it's the Revenue/Profit display in the miner list that doesn't take the Profit Factor into consideration correctly?

Thanks!
newbie
Activity: 52
Merit: 0
Hi Patrike,

we have now another problem in the current version.

in the pool properties under Advanced we entered a Profit factor (for some Pools) of - for example 0,49 - but this factor is now not effective anymore?! if we change to 1 nothing happens?!

BR Ralf
Hi Ralf,

Please select this miner in the list of miners and click on the Pools tab at the bottom of the screen. Do you see the pool description, as defined in Awesome Miner, here? Or only the Pool URL?

An ASIC miner is reporting a pool URL and worker name and Awesome Miner is trying to match this with the pool you have defined in Awesome Miner. If the URL and worker name are the same, it's a match. Once matched, Awesome Miner can apply Profit Factors defined on the pool.

Thanks!

Hi Patrike,

the pool description is exactly matching with the AM-Pool
we also checked the ignore the miner property: add to worker name in the Advanced definition of the pool
but still no success...

BR Ralf
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

we have now another problem in the current version.

in the pool properties under Advanced we entered a Profit factor (for some Pools) of - for example 0,49 - but this factor is now not effective anymore?! if we change to 1 nothing happens?!

BR Ralf
Hi Ralf,

Please select this miner in the list of miners and click on the Pools tab at the bottom of the screen. Do you see the pool description, as defined in Awesome Miner, here? Or only the Pool URL?

An ASIC miner is reporting a pool URL and worker name and Awesome Miner is trying to match this with the pool you have defined in Awesome Miner. If the URL and worker name are the same, it's a match. Once matched, Awesome Miner can apply Profit Factors defined on the pool.

Thanks!
legendary
Activity: 3346
Merit: 1094
How often does the software make backup of configuration? I made a bunch of changes tonight, had everything running.. Main system had a blip of power and now I'm back to where I started 3 hours ago.
All configuration data is stored in the folder: %appdata%\AwesomeMiner\
You will find multiple backup files created every month.

In addition, Awesome Miner uses two additional backup files for recent configuration in case the primary configuration file becomes corrupt. In your case it sounds like the primary configuration file became corrupt as part of the power failure. This is why Awesome Miner picked up an older backup file as a fallback. This is probably the most recent valid configuration available.

Every time you click OK in the Options dialog, add new miners and so on, Awesome Miner writes this to the primary configuration file.

If you want, please send me your Awesome Miner log file (via PM or mail) as it will always print the failed configuration file content to the log file before moving on to a backup file. In some cases the primary configuration file is completely corrupt, while it in other cases can be possible to extract some data.
legendary
Activity: 3346
Merit: 1094
Running Linux mining AM adds to Command line parameters:   --no-watchdog. How to remove "--no watchdog" Huh
Which mining software is it? NbMiner?
yes...
It's currently not configurable. The reason Awesome Miner disable the watchdog of mining software like Nbminer is because in case of a crash of Nbminer, the Nbminer watchdog would restart the Nbminer process. Awesome Miner will not have any idea of what's going on here and just notice the crash (original process no longer running) and restarts Nbminer. You would end up with two Nbminer processes.

Because Awesome Miner automatically restarts mining software that is crashing, the use of watchdogs built-in the mining software generally causes more problems than they solve.
newbie
Activity: 52
Merit: 0
Hi Patrike,

we have now another problem in the current version.

in the pool properties under Advanced we entered a Profit factor (for some Pools) of - for example 0,49 - but this factor is now not effective anymore?! if we change to 1 nothing happens?!

BR Ralf
newbie
Activity: 52
Merit: 0
Hi Patrike,

we installed the AM-Firmware for the S17+ - everything fine except 1 thing:
we set Target chip temperature to 80 (°C) but the Fan's run almost full speed and don't let the temperature going over 75...

BR Ralf
Hi Ralf,

Can you please increase "Disable chains at CHIP temperature" (overheat feature) from the default 90 to 93 C for example. This will make the overheat temperature compared to the Target chip temperature more than 10 C and the fans will behave like you want.

Hi Patrike,

thank you - that worked!

BR Ralf
jr. member
Activity: 195
Merit: 4
How often does the software make backup of configuration? I made a bunch of changes tonight, had everything running.. Main system had a blip of power and now I'm back to where I started 3 hours ago.
newbie
Activity: 52
Merit: 0
Running Linux mining AM adds to Command line parameters:   --no-watchdog. How to remove "--no watchdog" Huh
Which mining software is it? NbMiner?
yes...
legendary
Activity: 3346
Merit: 1094
Hi Patrike,

we installed the AM-Firmware for the S17+ - everything fine except 1 thing:
we set Target chip temperature to 80 (°C) but the Fan's run almost full speed and don't let the temperature going over 75...

BR Ralf
Hi Ralf,

Can you please increase "Disable chains at CHIP temperature" (overheat feature) from the default 90 to 93 C for example. This will make the overheat temperature compared to the Target chip temperature more than 10 C and the fans will behave like you want.
Pages:
Jump to: