Quote from: Slipknot79 on January 08, 2014, 07:09:08 AM

Thank you milone, cgwatcher isnt installed in one of those folders. Dunno what happend, but i downloaded the program again and now its working. Seems a config file was messed up.

Another problem i am having:
Sometimes windows detects only 3 of my 4 R9 280X. And sometimes, if 4 devices have been detected, one of them crashes after few hours of mining (its always the same card and in both cases i dont gain the expected hashrate). Then cgwatcher restarts cgminer and the crashed device runs with half hashrate (dunno why), so my total hashrate is about 2300kh/s. I set up treshhold to 2500 or below to force a restart of cgminer.

To solve the problem with this crashed device i have to restart the computer coz restarting cgminer doesnt solve this. How do i setup cgwatcher to restart the computer when hashrate drops below 2500kh/s? "Restart computer when sick or dead devices are detected" doesnt help.

I will add this option soon, it's been on the to-do list.

Quote from: ellave on January 08, 2014, 08:15:37 AM

Hi.

Firstly thank you so much for your wonderful App, however i too am having the startup problems in Win 8.1 like a few other users. I had to rebuild my rig so thought I would try Win 8 but the only good thing I can see is it boots quickly!! I'm using the newest version, tried as admin, not admin, the registry start up & standing on my head while turning my pc on Shocked

I'm going to reinstall Win 7 but thought I should report as seems to be a common issue with Win 8.

ta

I have one more idea for trying to fix the startup problem in Windows 8. I don't know why it has problems with the current method because it does create the entries properly, Windows just doesn't launch it. So I'll have one more option in the next update that will hopefully work around this.

Quote from: calandro on January 08, 2014, 09:21:14 AM

Hi milone,
thank you for the great tool. One feature request for a further version:

If you have enabled a time scheduled switching of the intensity and restart cgminer from CGWatcher into the low-activity period cgminer runs with the high intensity and you must reduce the intensity by hand. Specifically, I have the following scenario: every weekday at 18:00 cgwatcher increases the intensity to 17 for mining over the night. Every weekday at 8:00 the intensity will be reduced to 11 because I need the pc for my profession. Now...If cgwatcher restart the mining process during the day between 8:00 and 18:00 it will start with intensity of 17 although it is in the range of low activity. This is not good because the GPU fan revs up and in the office you put up with ridiculous questions. It would be nice if the program checks after the start of cgminer immediately whether a rule with non-default-settings from the cgminer.conf is active and the parameter is changed immediately by itself so the rule parameter for this specific time are valid.

Regards

If you're setting the intensity to change in the Schedule tab (below the scheduled actions list) then you're correct, I need to fix it so it looks here after restarting the miner. If you create scheduled actions to lower and raise intensity at certain times, then you would check the box that says "persist action through restarts" when creating the scheduled action, which would make sure the action is re-applied any time the miner is restarted.

Quote from: MIRQ3 on January 09, 2014, 09:44:28 AM

I have the question: did anyone noticed performance issues after few days of mining?
With every single day, CGWatcher.exe process consumes more and more RAM. It starts with aprox. 30MB, and growing about 15MB per day.
After 5 days of continuous mining, process reached almost 100MB consumed memory :/
Also, my PC is running slower and slower, while CPU usage is minimal.
I think this application has severe resource leaks...

CGWatcher's memory usage will grow a little after it has been running a while, but it will level off. On my desktop right now CGWatcher has been running for 11+ days and its memory usage is at 68MB. This is on par with the average of 70MB I've seen throughout testing. CGWatcher is a .NET application using .NET's garbage collection, which makes it very difficult to have a memory leak because the framework is managing resources. Nevertheless, I do take steps to release resources anyway and don't rely entirely on the garbage collector.

I would suggest checking for other applications on your system if it is slowing down over the course of several days.

Quote from: ammi84 on January 09, 2014, 09:51:35 PM

Hi,

i have a weird problem on my Windows 8.1 Test-Rig

When i use my config with a batch-file a get about 40-50 kh/s more
when i use cgwatcher with the same cgminer.exe / config-file i loose the 40-50kh/s

even if define a config it always uses E:\CGWatcher-1.3.4\temp.conf instead of the E:\CGMiner-LTCRabbit-V1\CGMiner LTCRabbit V1\cgminer-3.7.2-windows\cgminer.conf (value in profile)

ok - this is just my test-rig (main rig PSU is broken) ... but i can't figure out what is the problem!?

can i deliver something to investigate this bug?

When using CGWatcher it will always set the miner to use a config file in its own folder (temp.conf) but this config file is created using the settings in your config file. The reason it uses this temporary config file is that some users share config files between miners, and then use variables to tweak individual machine settings. So a temporary config file has to be written so multiple instances of CGWatcher do not interfere with each other. You can see the exact config settings used to launch the miner by going to the Tests tab, locate the utilities drop-down list in the middle of the window, and select "Show last miner start configuration" and click "Run".

If you are experiencing a different in hashrate with and without CGWatcher, it is probably due to the gpu-threads value. The cgminer readme states that the default value for gpu-threads is 2, when in reality it uses 1 as default. So when CGWatcher launches the miner, it uses 2 as the default to match what the cgminer readme says and what the user should expect. This means when you start the miner outside of CGWatcher, you are using 1 gpu-thread, and when you start the miner with CGWatcher you are using 2, unless you explicitly set it to 1.

In other words, make sure the gpu-threads is set to 1 in your config file or arguments.

If you believe running your batch file also improves performance, you can set CGWatcher to launch the batch file instead of the miner's executable in Profile Manager.

Quote from: bullus on January 11, 2014, 12:11:04 AM

First of all great software

Got some troubles using profitable mining.

I set a schedule for switch profile to 1st most profitable every 6min.
But sometimes if he switch the next run time isn't update to the next 6min and it don't switch anymore.
Why is that?

Also the device settings is using the default settings for my card and can not change the vddc.
Is it overruling my config file?

I have 3 different rigs and want to use only 1 cgwatcher , is that possible?
I use an api from coinswarz and if I install it on the 3 rigs than the api calls is 3 times faster empty if u understand what I mean. So like to install it to 1 rig and control the 2 other rigs with 1 cgwatcher.

When using the settings "switch to profile without restarting miner when possible (beta)" the fan of my cards goes to a lower state and is overheating my card. Now I just don't use that settings and it's ok and its using the user defined fan profile of asus gpu tweak when Switching to another profile.

Thanks.

If the scheduler is not working correctly, please email me two things: a debug report, which can be created by going to the Tests tab and clicking the 'Create Debug Report' button. And also, the file called cgwatcher.log in your CGWatcher folder. Keep in mind that if you create a scheduled action to switch profiles based on profitability, if it finds that the profile it should switch to is the profile already in use it will ignore the action.

When you change a GPU setting in CGWatcher, it is simply sending a command to cgminer telling it to change that setting. CGWatcher does not attempt to change clock speeds, fan speeds, or voltages itself because this can interfere with the miner doing it, as they both use the same method of getting device info. Some GPUs have locked voltages and you need to flash them with modified BIOS in order to change... but flashing a BIOS incorrectly can brick your card so it is not something I advise you doing unless you know exactly what you're doing.

You can use CGRemote to manage all three of your miners from one program. The next update of CGRemote will be able to get API data from CoinWarz or CoinChoose and send it to all miners it is connected to that are running CGWatcher in order to reduce API calls.

The "Switch to profile without restarting miner" setting will try to set any settings in the new profile. So if it switches to a profile where the fan settings are "50-100", it will send a command to cgminer telling it to change fan speed to "50-100". Any changes should be temporary if auto-fan is enabled, but I can't say for certain that the expected behavior occurs and need to do more testing, which is why this setting is considered experimental/beta.