Topic: CGWatcher 1.4.0, a GUI/monitor for CGMiner & BFGMiner to help minimize downtime - page 21. (Read 402544 times)

all these micro-updates.  Next thing you know it'll be CGWatcher Version 1.3.1.2.9.5.7.3.2.2.4.5.6.6.7.1.2.4.3.8 !

If anyone has experienced problems with more recent versions of CGWatcher not starting the miner successfully, please try 1.3.0.2, which has fixed the (known) issues regarding this. I just updated the auto-update version number so if you have auto-update enabled it should take care of this for you the next time you start CGWatcher or in the next 24 hours, or you can initiate it manually by going to the About tab and clicking "Check for Update", then once it sees an update is available, "Auto-Update"... or something along those lines (I can't remember the exact wording I used.)

If you're still having problems with this, or any other features, please let me know.

Thanks.

As it turns out, the motherboard WASN'T the problem.  I did a total zeroes wipe of the hard drive, reinstalled 12.8 and SDK 2.7, and the thing is humming away right now with 2 7950's in it and a 3rd poised to start soon.  CGMiner 3.3.0, MSI Afterburner.

Sorry, I had hard-coded the path to try to reproduce a reported bug and forgot to remove it before compiling. It has been fixed, please download 1.2.8.1 again. I apologize for any inconvenience.

I only got the latest version of the program to run after manually creating the folder "C:\coinware\miners\cgminer with spaces".   

Sorry, no immediate plans for a Linux version. If a Linux dev would be willing to attempt porting it to Linux, I'm open to that (though a lot of changes are being made right now, including some complete re-writes to clean up some of the ugliness that resulted from features being added over time.)

CGRemote works with any cgminer or bfgminer, regardless of OS. However CGRemote is also a Windows .NET application. I haven't tried either with WINE, and in the future if there are changes I can make so that it works with WINE I'll try to make them. A Linux version is on the to-do list, but nowhere near the top unfortunately. Significantly higher up is a small listener utility for Linux and OSX will be written to work with CGRemote, so it can handle problems should the miner's API go down or the few times where things can't be done via the API. CGRemote obvioulsy requires a Windows PC but fortunately most people probably have at least one. Even an old laptop would provide one interface for all miners with the features of CGWatcher. It can be used to control miners on the same computer, local network, or over the Internet.

I have tried it with wine, but no go
anyone success?
TIA

I'm not at home right now so can't look at the code, but this was probably a bug introduced when I added a separate hashrate setting for each algorithm. I think if you set scrypt to 1khs it should be happy without affecting anything (unless you're mining a scrypt coin on your 3dfx voodoo.)

Thanks, I'll make sure this is fixed in 1.2.8.

Hey, I have some trouble with cgwatcher

Menu "monitor"

"restart if current total hashrate falls below this:" I added 79 Ghash under SHA256 and 0 khash/s under the section scrypt.

I get this error message: "Restart if current total hashrate falls below this "scrypt value must be greater the zero (or zero to disable).. Do you want to disable this option"

When I hit "ok" then the option gets disabled.. when I hit cancel than it keeps repeating the error message as soon as I go to "monitor menu"

Yeah you can use decimals for that. When I was originally testing it I had it switching profiles every 3 minutes (0.05 hours). Once you save it it will give you a better description (e.g. "3 min" instead of "0.05 hours")

Thank you for such a detailed response!

I was referring to the Scheduled Action settings > Every... x hour(s)
(set to 30 by default)

Coins that are linked to a profile (coins that you mine) are not removed even if they disappear from coinchoose. Their profitability data will just go to zero, as was initially requested and thought to be the best way to handle this (though at the time the assumption was that coins dropping off had no buy orders, not because of block explorers going down). I believe coinchoose has corrected the litecoin issue, at least for now. I just made changes to record the last updated date/time for each coin to at least be able to tell if a coin is not on coinchoose, but what a user would want to do in that case depends on why the coin is gone. I think the safer thing to do is to reset all of its values to zero, because more often than not coins are going to drop because they are dying. I don't expect what happened with litecoin to be a common enough issue to warrant any changing this, and even if it did there is no easy way to automatically tell a) why the coin is gone, and b) if the coin is still most profitable.

Coins that you don't mine are removed if they drop off coinchoose.

I'm not sure what interval you're referring to. By default coin profitability data is updated every 15 minutes. You can change that by changing the CoinRefreshInterval value in CGWatcher.exe.ini. The value is in minutes, no decimals. Minimum value is 5, anything below that will just be reset to 5.

If you schedule CGWatcher to switch profiles to most profitable, for example, it will update the profitability data before switching if it has not been updated within the last 15 minutes. As requested that will change in 1.2.7, where it will always update profitability data right before selecting a profile unless the data was already updated within the past 5 minutes.

Let me know if that's not the interval you were referring to.

I know it was discussed but what is the result if a coin falls off coinchoose?

Litecoin has been falling off lately and it is usually the most profitable (adjusted for stales) of the coins I mine.

Also, can you set the interval to less than 1 hour? If so does it accept decimals (i.e. 0.5 for half an hour)?

Version 1.2.6 has a ton of improvements and bug fixes, and anyone using CGRemote should update to this version with the new CGRemote update (1.0.3).

I've made some changes to this that will be in the next update, but you've found one way it currently has a problem. It knows there may be other lines in batch files (setx, etc) so it has to find what it believes is the line containing the miner executable and arguments.

It does this by checking if a) the line has the name of a miner + .exe (cgminer.exe, bfgminer.exe, cgminer-nogpu.exe, or any other miner executables you've used in the past) or b) the beginning of the line starts with the name of a miner, in case the .exe is missing. By using "start cgminer" it is missing both of those.

I'm not sure that I want to go so far as to assume any line containing a miner name (cgminer, bfgminer, etc) is the executable line, so for now I've added additional handling for "start" at the beginning before the miner name.

For now I'd suggest changing the line in your batch file to say either "start cgminer.exe ..." or remove the word start so "cgminer ..." (or also starting the line with "cgminer.exe ..." of course) will work. I can't say this will resolve the issue entirely as there have been some other bugs I've fixed, including accepting pools with no password (which should not affect cgminer but CGWatcher may nag you about not having any pools when you save a profile without pool passwords). I'm assuming you omitted your pool username for posting, but a URL and username are required for CGWatcher to consider it a valid pool in some circumstances when no config file is used.

If CGWatcher makes changes to your config file or batch file before launching the miner, it saves them, starts the miner, then restores the originals. If you want to see exactly the files used when the miner started, go to the Tests tab and click the 'Miner Start' button. It will show the last used config file and batch file (if applicable), and the times they were used, among other info.

I'm pushing to have release this update today, it has a lot of fixes and some new features. If not today in the next day or two.

CGwatcher brings up an error parsing this command line
while cgminer via batch works perfectly

start cgminer  --scrypt -u -o stratum+tcp://stratum.give-me-ltc.com:3333 --gpu-platform 0 -d 0,1,2,3,4 -w 256 -v 1 -I 16 -g 1  --thread-concurrency 8000,6144,6144,6144,6144 --auto-fan --temp-overheat 82 --temp-cutoff 90

without threads cgminer crashes, those params are essential.
Please make parser more robust


Also app is not saving GPU core clocks in DEVICEs tab, have to readjust manually every time start or restart app

I will use this when I get my miner. Looks good, good job!

Fixed.  The motherboard itself was the problem.  Installed 12.8 drivers and SDK 2.7 on an Asus P8P67 Revision 3b with Windows 7 Home Premium and it fired up and worked right away.  Same CPU, same RAM sticks, same hard drive, same GPUs.  It's mining LiteCoin for me now with 3 6950's cranking 383 Khash/sec each at stock clocks and intensity 16.

Hmm... that is the downside of supporting multiple instances... I can't just say if there is one open, don't start another one. Although it should only do this if the 'Ensure miner stays running' option is enabled and something is causing it to not connect to each one it starts. I'm not sure why it would open so many though, it should give up after a few consecutive failed attempts (though there was a bug in previous versions where it wouldn't keep count correctly). What version was it?

If you can email me any log files (*.log) from the CGWatcher folder, I'll see if I can find what happened.


Also, check your email... I just sent out download links.

i had a multiple error when my internet disconnected for 30+ minutes. the cgwatcher seems to create duplicates cgminers. One time, the internet was offline for 6 hrs and the cgwatcher seems to create 20+ duplicates cgminer.