[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[insaniak]

My rig keeps crashing when doing autoprofit mining. I was previously mining etherium just fine. What could be the problem?

If you have your rig tuned to do Eth, then start it as a profit miner... when it changes to a different algorithm, the GPU settings could be wrong.  Your over/underclocks for Eth could be the wrong settings for a different more stressful algorithm.  Also, if you have your rig running on the edge of what your PSU can handle... you may be running into an issue with the PSU not being able to deliver enough power for a stressful algo based on your previous tuning for Eth.  How many, and what kind of GPUs are you running?  What PSU are you running?

I am using 8x GTX 1070 with 1600 Watt EVGA plat PSU. I have restored the settings in msi and they are default with not OC. Not sure what the issue is I did notice that my CPU usage is very high around 70-80% when i was mining eth it was 30-40%

[ordimans]

@dev :

About Nicehash pool, if i switch to the pool by AM, the worker name is not take by Nicehash stats....
Bug, no in the feature, or problem from nicehash

For example :

IF i put worker name S9_1 in AM, no worker name in stats.


If i use antminer webpage, it's OK.



Have an idea ?

I use minera 0.8.0 to run my miner. Could i also use AM to monitor and manage also remote control it?

No success with Minera and S9 for me. I prefer AM

[patrike]

@dev :

About Nicehash pool, if i switch to the pool by AM, the worker name is not take by Nicehash stats....
Bug, no in the feature, or problem from nicehash

For example :

IF i put worker name S9_1 in AM, no worker name in stats.


If i use antminer webpage, it's OK.

Have an idea ?

I use minera 0.8.0 to run my miner. Could i also use AM to monitor and manage also remote control it?

No success with Minera and S9 for me. I prefer AM

I know that some characters cannot be used when setting worker names on the Antminers over the management interface. Even if these may work directly in the web for the Antminer, it may not work as expected from external applications like Awesome Miner.

I can't recall how the support for is for _ (underscore), but as a first try you could try to change from "S9_1" to just "S91" or similar.

[patrike]

My rig keeps crashing when doing autoprofit mining. I was previously mining etherium just fine. What could be the problem?

If you have your rig tuned to do Eth, then start it as a profit miner... when it changes to a different algorithm, the GPU settings could be wrong.  Your over/underclocks for Eth could be the wrong settings for a different more stressful algorithm.  Also, if you have your rig running on the edge of what your PSU can handle... you may be running into an issue with the PSU not being able to deliver enough power for a stressful algo based on your previous tuning for Eth.  How many, and what kind of GPUs are you running?  What PSU are you running?

I am using 8x GTX 1070 with 1600 Watt EVGA plat PSU. I have restored the settings in msi and they are default with not OC. Not sure what the issue is I did notice that my CPU usage is very high around 70-80% when i was mining eth it was 30-40%

Can you try to click the Diagnostics button to see if you get any additional information? Like what mining software is being selected, which algorithm and then the output from the mining software. It could be that your GPU/drivers/system isn't compatible with this mining software, and then it can be unselected from the profit switcher. The first step is however to use Diagnostics to figure out more details.

[patrike]

Hi, I bought the Enterprise version.
I've used it with different miners with no problems. Only mining with autoswitch that could not make it work in any way.

My doubt is:
I use the NHML (Nicehash Mining Legacy). I installed the AM agent and tried to connect the miner, also ip, however unsuccessfully. How to make AM just see Nicehash mining?

I'm currently using AM just as a monitoring my rigs of which are managed by NHML 1.8.1.3

Thanks

I assume you are using External Miner concept in Awesome Miner to connect to the mining software started by the Nicehash mining software. In order for this to work, the mining software must have API enabled and you need to know on which port the Nicehash software uses for this. Once you found this information in the Nicehash software, it should simply be to connect to the IP and port from Awesome Miner.

I have the API but it's from the website (it's just one API for all miners together) , local software do not have one, how can I insert this API in the AM software so that I can monitor my rigs?

Awesome Miner can connect to the API's of the mining software (Claymore miner, Ccminer, ...) that is running on your mining rigs. Awesome Miner is not connecting to any website for this.

If you use the Managed Miner concept in Awesome Miner, all this will work out of the box. If you want to use the Nicehash application to launch mining software and only monitor from Awesome Miner with an External Miner, you do need to make sure that the Nicehash software enables the API (and which port) on the mining software for Awesome Miner to connect.

[patrike]

Feature request:

Add dual mining revenue under Coins and Online services for secondary coins.

Example:

Thanks for the suggestion. This could be an improvement for future versions.

[Kronny]

Hi, is there any solution about Ewbf 0sol?
the miner does not restart with this error 

What kind of problem is that? Are other mining software working on you system? Can you please share more details.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

[puwaha]

My rig keeps crashing when doing autoprofit mining. I was previously mining etherium just fine. What could be the problem?

If you have your rig tuned to do Eth, then start it as a profit miner... when it changes to a different algorithm, the GPU settings could be wrong.  Your over/underclocks for Eth could be the wrong settings for a different more stressful algorithm.  Also, if you have your rig running on the edge of what your PSU can handle... you may be running into an issue with the PSU not being able to deliver enough power for a stressful algo based on your previous tuning for Eth.  How many, and what kind of GPUs are you running?  What PSU are you running?

I am using 8x GTX 1070 with 1600 Watt EVGA plat PSU. I have restored the settings in msi and they are default with not OC. Not sure what the issue is I did notice that my CPU usage is very high around 70-80% when i was mining eth it was 30-40%

Well... 8x 1070s running at full power limit will be 1200W.  Add in say 150W for the rest of the system, and you are at 1350.  You are running the PSU at 85% of it's maximum load.  I'd back the power limit down to 80% using Afterburner to give your PSU a little more breathing room.

[puwaha]

Hi, is there any solution about Ewbf 0sol?
the miner does not restart with this error 

What kind of problem is that? Are other mining software working on you system? Can you please share more details.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

How hard are you pushing your rig?  From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard.  Thus, the GPUs are crashing and EWBF is trying to recover.  Back off your power limits and or overclocks 5% here and there until you have a stable rig.  You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit.

[Kronny]

Hi, is there any solution about Ewbf 0sol?
the miner does not restart with this error 

What kind of problem is that? Are other mining software working on you system? Can you please share more details.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

How hard are you pushing your rig?  From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard.  Thus, the GPUs are crashing and EWBF is trying to recover.  Back off your power limits and or overclocks 5% here and there until you have a stable rig.  You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit.

Yes i have 1070s card, but i'm not talking about ewbf's problem, i'm asking if awesome miner should know when the 0sol error appears and restart the miner.

[insaniak]

I ran diagnostics not showing anything bad.
I also reduced power to 80% still same thing is happening. I dont know what to do. Its very frustrating.


Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe
C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe  -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u 1GtNWJLVDQHHmvmE4HwrTyUkU5pRTLNeED -p x -b 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: CcMiner)
Configuration:

Mining Engine Process started, PID: 4692

====================================================================================================
> *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
>     Built with VC++ 2013 and nVidia CUDA SDK 8.0 64-bits
>
>   Originally based on Christian Buchner and Christian H. project
>   Include some algos from alexis78, djm34, sp, tsiv and klausT.
>
> BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
>
> [2017-09-24 10:04:49] Starting on stratum+tcp://lyra2v2.mine.zpool.ca:4533
> [2017-09-24 10:04:49] NVML GPU monitoring enabled.
> [2017-09-24 10:04:49] NVAPI GPU monitoring enabled.
> [2017-09-24 10:04:49] 8 miner threads started, using 'lyra2v2' algorithm.
> [2017-09-24 10:04:50] Stratum difficulty set to 64 (0.25000)
> [2017-09-24 10:04:50] lyra2v2 block 794692, diff 25795.206
> [2017-09-24 10:04:50] API open to the network in read-only mode on port 4028
> [2017-09-24 10:04:51] GPU #1: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #3: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #5: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #7: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #2: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #0: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #6: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #4: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:55] GPU #5: EVGA GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #7: Gigabyte GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #1: EVGA GTX 1070, 987.04 kH/s
> [2017-09-24 10:04:55] GPU #3: EVGA GTX 1070, 924.75 kH/s
> [2017-09-24 10:04:55] GPU #4: EVGA GTX 1070, 923.93 kH/s
> [2017-09-24 10:04:55] GPU #6: Gigabyte GTX 1070, 909.73 kH/s
> [2017-09-24 10:04:55] GPU #0: EVGA GTX 1070, 895.71 kH/s
> [2017-09-24 10:04:56] GPU #2: EVGA GTX 1070, 883.60 kH/s
> [2017-09-24 10:04:57] accepted: 1/1 (diff 0.537), 107.62 MH/s yes!
> [2017-09-24 10:05:01] GPU #5: EVGA GTX 1070, 25.10 MH/s
> [2017-09-24 10:05:01] accepted: 2/2 (diff 0.452), 197.93 MH/s yes!

====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed

[patrike]

Hi, is there any solution about Ewbf 0sol?
the miner does not restart with this error 

What kind of problem is that? Are other mining software working on you system? Can you please share more details.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

How hard are you pushing your rig?  From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard.  Thus, the GPUs are crashing and EWBF is trying to recover.  Back off your power limits and or overclocks 5% here and there until you have a stable rig.  You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit.

Yes i have 1070s card, but i'm not talking about ewbf's problem, i'm asking if awesome miner should know when the 0sol error appears and restart the miner.

You can use the Rules in Awesome Miner to detect low hashrate. You can see an example of this in the section "Example: Show notification on low hashrate" on this page:
http://www.awesomeminer.com/help/rules.aspx
The example is only showing a notification, but you can also add an action of the type "Miner Command" and set it to Restart or Reboot.

[patrike]

I ran diagnostics not showing anything bad.
I also reduced power to 80% still same thing is happening. I dont know what to do. Its very frustrating.


Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe
C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe  -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u 1GtNWJLVDQHHmvmE4HwrTyUkU5pRTLNeED -p x -b 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: CcMiner)
Configuration:

Mining Engine Process started, PID: 4692

====================================================================================================
> *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
>     Built with VC++ 2013 and nVidia CUDA SDK 8.0 64-bits
>
>   Originally based on Christian Buchner and Christian H. project
>   Include some algos from alexis78, djm34, sp, tsiv and klausT.
>
> BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
>
> [2017-09-24 10:04:49] Starting on stratum+tcp://lyra2v2.mine.zpool.ca:4533
> [2017-09-24 10:04:49] NVML GPU monitoring enabled.
> [2017-09-24 10:04:49] NVAPI GPU monitoring enabled.
> [2017-09-24 10:04:49] 8 miner threads started, using 'lyra2v2' algorithm.
> [2017-09-24 10:04:50] Stratum difficulty set to 64 (0.25000)
> [2017-09-24 10:04:50] lyra2v2 block 794692, diff 25795.206
> [2017-09-24 10:04:50] API open to the network in read-only mode on port 4028
> [2017-09-24 10:04:51] GPU #1: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #3: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #5: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #7: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #2: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #0: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #6: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #4: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:55] GPU #5: EVGA GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #7: Gigabyte GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #1: EVGA GTX 1070, 987.04 kH/s
> [2017-09-24 10:04:55] GPU #3: EVGA GTX 1070, 924.75 kH/s
> [2017-09-24 10:04:55] GPU #4: EVGA GTX 1070, 923.93 kH/s
> [2017-09-24 10:04:55] GPU #6: Gigabyte GTX 1070, 909.73 kH/s
> [2017-09-24 10:04:55] GPU #0: EVGA GTX 1070, 895.71 kH/s
> [2017-09-24 10:04:56] GPU #2: EVGA GTX 1070, 883.60 kH/s
> [2017-09-24 10:04:57] accepted: 1/1 (diff 0.537), 107.62 MH/s yes!
> [2017-09-24 10:05:01] GPU #5: EVGA GTX 1070, 25.10 MH/s
> [2017-09-24 10:05:01] accepted: 2/2 (diff 0.452), 197.93 MH/s yes!

====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed

This one doesn't indicate any crash as you also pointed out. When it crashes, is it right away when the mining starts or after a while?
Maybe it was another mining software or algorithm when it crashed. You could run the Diagnostics right away after it crashes next time to see if there are any difference in the output.

In general, crashes has very little to do with Awesome Miner as it only launches the different mining software. There can always be compatibility issues between different GPUs, clocking settings, drivers, systems and specific mining software or algorithms.

[insaniak]

I ran diagnostics not showing anything bad.
I also reduced power to 80% still same thing is happening. I dont know what to do. Its very frustrating.


Starting Diagnostics
Starting Mining Software
Setting up Miner Engine. Instance: 1
Engine Type: CcMiner, Auto Download: True, EnginePath: , Subtype: Disabled, CustomExecutable:
Added rule for: C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe
C:\Users\Rig2\AppData\Roaming\AwesomeMinerService\ccminer-2.2_1\ccminer-2.2\ccminer-x64.exe  -a lyra2v2 -o stratum+tcp://lyra2v2.mine.zpool.ca:4533 -u 1GtNWJLVDQHHmvmE4HwrTyUkU5pRTLNeED -p x -b 0.0.0.0:4028   (WindowMode: ConsoleFormat, EngineType: CcMiner)
Configuration:

Mining Engine Process started, PID: 4692

====================================================================================================
> *** ccminer 2.2 for nVidia GPUs by tpruvot@github ***
>     Built with VC++ 2013 and nVidia CUDA SDK 8.0 64-bits
>
>   Originally based on Christian Buchner and Christian H. project
>   Include some algos from alexis78, djm34, sp, tsiv and klausT.
>
> BTC donation address: 1AJdfCpLWPNoAMDfHF1wD5y8VgKSSTHxPo (tpruvot)
>
> [2017-09-24 10:04:49] Starting on stratum+tcp://lyra2v2.mine.zpool.ca:4533
> [2017-09-24 10:04:49] NVML GPU monitoring enabled.
> [2017-09-24 10:04:49] NVAPI GPU monitoring enabled.
> [2017-09-24 10:04:49] 8 miner threads started, using 'lyra2v2' algorithm.
> [2017-09-24 10:04:50] Stratum difficulty set to 64 (0.25000)
> [2017-09-24 10:04:50] lyra2v2 block 794692, diff 25795.206
> [2017-09-24 10:04:50] API open to the network in read-only mode on port 4028
> [2017-09-24 10:04:51] GPU #1: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #3: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #5: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #7: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #2: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #0: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #6: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:51] GPU #4: Intensity set to 20, 1048576 cuda threads
> [2017-09-24 10:04:55] GPU #5: EVGA GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #7: Gigabyte GTX 1070, 1035.13 kH/s
> [2017-09-24 10:04:55] GPU #1: EVGA GTX 1070, 987.04 kH/s
> [2017-09-24 10:04:55] GPU #3: EVGA GTX 1070, 924.75 kH/s
> [2017-09-24 10:04:55] GPU #4: EVGA GTX 1070, 923.93 kH/s
> [2017-09-24 10:04:55] GPU #6: Gigabyte GTX 1070, 909.73 kH/s
> [2017-09-24 10:04:55] GPU #0: EVGA GTX 1070, 895.71 kH/s
> [2017-09-24 10:04:56] GPU #2: EVGA GTX 1070, 883.60 kH/s
> [2017-09-24 10:04:57] accepted: 1/1 (diff 0.537), 107.62 MH/s yes!
> [2017-09-24 10:05:01] GPU #5: EVGA GTX 1070, 25.10 MH/s
> [2017-09-24 10:05:01] accepted: 2/2 (diff 0.452), 197.93 MH/s yes!

====================================================================================================
Stopping miner process ...
Stopping Mining Software
Diagnostics completed

This one doesn't indicate any crash as you also pointed out. When it crashes, is it right away when the mining starts or after a while?
Maybe it was another mining software or algorithm when it crashed. You could run the Diagnostics right away after it crashes next time to see if there are any difference in the output.

In general, crashes has very little to do with Awesome Miner as it only launches the different mining software. There can always be compatibility issues between different GPUs, clocking settings, drivers, systems and specific mining software or algorithms.

Its not right away. Its only using cc miner and I noticed that I saw once it said "cc miner has stopped working" and that was right after setting gpu intensities.

[ordimans]

@dev :

About Nicehash pool, if i switch to the pool by AM, the worker name is not take by Nicehash stats....
Bug, no in the feature, or problem from nicehash

For example :

IF i put worker name S9_1 in AM, no worker name in stats.


If i use antminer webpage, it's OK.

Have an idea ?

I use minera 0.8.0 to run my miner. Could i also use AM to monitor and manage also remote control it?

No success with Minera and S9 for me. I prefer AM

I know that some characters cannot be used when setting worker names on the Antminers over the management interface. Even if these may work directly in the web for the Antminer, it may not work as expected from external applications like Awesome Miner.

I can't recall how the support for is for _ (underscore), but as a first try you could try to change from "S9_1" to just "S91" or similar.

Good idea, i will try.

About xnsub, don't know if it's work correctly with Nicehash.
on one in FAS, they say add /#xnsub and another just #xnsub.... in URL...


EDIT: Perfect it's worked. Thanks you.

[Kronny]

Hi, is there any solution about Ewbf 0sol?
the miner does not restart with this error 

What kind of problem is that? Are other mining software working on you system? Can you please share more details.

no other software, but this is a "normal" problem of ewbf, happen on all my miner random.

How hard are you pushing your rig?  From the picture, your GPUs are pushing 480+ sols... sounds like you have GTX 1070s or maybe 1080s... but are pushing them way too hard.  Thus, the GPUs are crashing and EWBF is trying to recover.  Back off your power limits and or overclocks 5% here and there until you have a stable rig.  You can use Awesome Miner (if you have the correct edition) to control Afterburner Server... this will allow you to control GPU/Mem clocks, and power limit.

Yes i have 1070s card, but i'm not talking about ewbf's problem, i'm asking if awesome miner should know when the 0sol error appears and restart the miner.

You can use the Rules in Awesome Miner to detect low hashrate. You can see an example of this in the section "Example: Show notification on low hashrate" on this page:
http://www.awesomeminer.com/help/rules.aspx
The example is only showing a notification, but you can also add an action of the type "Miner Command" and set it to Restart or Reboot.

Yeah! really ty!!

[tf2addict]

On the GPUs tab in Awesome Miner my AMD cards are showing 0 for the Accepted progress even though I have plenty of accepted shares that show in the Miners list above it.  My Nvidia cards show the Accepted values ok.

Bug?

[toptek]

On the GPUs tab in Awesome Miner my AMD cards are showing 0 for the Accepted progress even though I have plenty of accepted shares that show in the Miners list above it.  My Nvidia cards show the Accepted values ok.

Bug?

go to GPU tab make sure you have Map to system monitoring on using claymore .... I'm guessing your mining ZEC/zcash and using Claymore for the AMD cards ?.

That Might be why you don't see the AMD Card/s shares but do for the NV card sense Claymore zec miner doesn't support NV cards .
you have to use a different Software miner for the NV card/s mining Zec/zcash.. that has API access and Claymore doesn't have API access.




other wise, no idea why, mine all ways show when i turn on Map to system monitoring.

[rxracer]

Hey patrike,

I've finally got a profit switching miner going nicely, and it truly is 'awesome'.  I love it, except for one thing.  I can't see a way to change GPU clock/mem settings before each algo switch.  

The hashrate difference between the least and most optimal GPU setting can be quite big, or a setting will run fine with one miner/algo, but crash with another.  I don't need MSI Afterburner integration or any of the extra features that come with the expensive versions.  All I need is a way to run a few batch commands before each miner & algo starts.  Like -

nvidiaInspector.exe -setBaseClockOffset:0,0,140 -setMemoryClockOffset:0,0,600 -setPowerTarget:0,75 -setTempTarget:2,0,83

I can see the option for batch commands with managed miners, but not with a profit switching miner.  It would be nice if there was an option in the Algorithms section to run batch commands before each algo.  Without this function I have to either run the GPU's at lower clock settings and lose profit, or manually run a batch file with optimal settings every time AM switches algo's.  Most miners have options to set clocks, but they can't query 10 series cards.  I'm happy to pay for this program, but I'm mining mostly for fun with just 4 cards.  I don't need all the features that come with the expensive versions.  Just a way to change GPU settings.  

Cheers.

[SvensenHensen]

Hi,

just buying the pro version. Everything looks fine but i cant connect to any miner with EWBF Cuda Zcash mining. API is enabled on standardport, status webpage is shown. But Awesome is responding "Failed to connect".

Changing to other port is the same.

API Report
Version: 4.0.2
API command: {"id":1, "method":"getstat"}

Any ideas?

Thanks

After setting --api 0.0.0.0:42000 and 2 minutes waiting (?) everything is sortet out now.