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

Great program!

But is there a way to set it to restart only a single gpu if the hashrate of that gpu is below a certain level? As I am having issues where on startup 1 or 2 random gpus will only be doing 20-30khs for some reason and need to be manually restarted. If I just set to restart the whole program some other gpus may be going slow again anyway so this isn't an option.

For CGRemote support, please contact me via email until I create a post for CGRemote here (which I'll do closer to release date). When reporting a problem, please include the bug report created by clicking 'Report Bug' in the toolbar. Try to describe the problem with as much detail as possible, including the hardware you're using and whether you're accessing the miner(s) from the same LAN or over the Internet - there is no such thing as too much information when reporting a problem.

I'm having trouble connecting to bfgminer rpc. Everything is set up on the server end (Ubuntu). I can ping from the pc I'm trying to connect to but CGRemote says ping failed for some reason.

Ah ok... it was just sent. Once the transaction confirms I'll send you an email. Thanks... I hope you find CGRemote useful.

pm sent.

What is your email address? You can PM me or just tell me the first part (e.g. JohnSmith instead of [email protected]). I've gotten a ton of them today and I think I am keeping caught up, but it's possible I may have missed one.

Sent you an email, waiting on Beta access.

Thanks man! I might just donate for Remote if it can really manage multiple miners natively.

You would need to run two instances of cgminer (or bfgminer) and you can also run two (or more) instances of CGWatcher. See below on how to do this.



See below on how to run multiple instances of CGWatcher.



I think we just got this figured out via email. If this wasn't you, let me know.



Running Multiple Instances of CGWatcher

Running multiple instances of CGWatcher means you can have a CGWatcher instance monitoring each cgminer/bfgminer instance. There are two things you need to do for this to work correctly - have unique folders and have unique ports. I'll explain in detail so although it might be a lot of text, it is very simple. You can run as many instances as you need.

1. Each CGWatcher instance must have its own folder. This is so they do not overwrite each other's settings, and also so the Windows autorun entries will be unique. You can put the folders anywhere, including nesting them inside each other. So if you want to run two instances, A and B, the following examples would work:

• CGWatcher A - C:\Miners\CGWatcherA
• CGWatcher B - C:\Miners\CGWatcherB

or

• CGWatcher A - C:\Miners\CGWatcherA
• CGWatcher B - C:\Miners\CGWatcherA\CGWatcherB

or

• CGWatcher A - C:\Miners\CGWatcher
• CGWatcher B - C:\Miners\CGWatcher\CGWatcher

If you want to share the same profiles between instances, you can set them to use the same profiles.dat file by editing CGWatcher.exe.ini in each folder. In this file, locate the line that says "ProfilesDataFile=" and add the file path of the profiles.dat file you want it to use. Do not use quotes in the file path. Example: ProfilesDataFile=C:\My Miners Folder\CGWatcher\profiles.dat 

When ProfilesDataFile= is blank, CGWatcher will use (or create) the profiles.dat file in the same folder it is in. You can also do the same with CGWatcher variables by setting the VariablesDataFile path.


2. Each instance must use a unique API port so it always communicates with the correct miner. To set the API port, go to the Settings tab in CGWatcher. In the bottom, left, locate 'Miner API Address (IP:port)' textbox. The port is the number after the colon. This number must be unique for each instance. So instance A could be 4028 (cgminer's default API port) and instance B could be 4029. You can use any number between 1024 and 65535 - it just has to be a port that isn't being used by another application. The IP address stays the same - 127.0.0.1 - for all instances. So the textbox for your CGWatcher instances would be:

CGWatcher A:   127.0.0.1:4028
CGWatcher B:   127.0.0.1:4029

Once you have entered a unique port, check the checkbox below it that says 'Use only this API port (override config settings)'. When this is enabled, CGWatcher will ensure that cgminer/bfgminer always uses this port - even if the config file says to use a different port. This ensures that multiple instances will never cross communicate.

Now since each CGWatcher instance has its own file path, if you enable 'Run when Windows starts' an entry will be created for each instance.

Click Save Settings.

I do this on my own computer since it mines scrypt coins with GPUs and Bitcoin with ASICs. I then just create a shortcut to each CGWatcher instance on the desktop and rename them to "CGWatcher GPU" and one "CGWatcher ASIC". I have them sharing the same profiles file, so if you make changes to profiles in one, it is picked up by the other one (it may take up to 15 minutes for this to happen, but it will always check for changes before starting the miner).

Also, you can obviously share config files between instances but you can share config files between miners as well. More info on this and using variables can be found at http://manotechnology.blogspot.com/2013/08/web-config-files.html

In the future I may try to come up with a better way to do this, but it is getting to where CGRemote will probably be a better way to do this since it is built from the ground up to handle multiple miners. CGWatcher was designed to only watch one process at a time, and I think my time would be better spent working on putting CGWatcher features into CGRemote than rewriting CGWatcher.

Its ok fixed it its working like magic haha- It was the Dynamic Intensity at the top right of multiminer it was set to on by default despite checking in the settings and seeing it was off. Saw that in another post and that might be fixed by now not sure if this is a common happening anyway all good now and thanks for making this!

faron

I'm using this on 5 machines right now but will be setting more up. I'm hoping to get cgremote today so I can quit running all over the house to change settings! I emailed you a little bit ago asking if you have coinbase

Hi there I am new to the idea of crypto switching and just found and downloaded the multi miner programme. It looks a lot more intuitive and simpler than CGWatcher but having installed the software when it comes to mine and press start it doesn't do anything. I have one AMD 7950 atm and will scale this up when I can get this working however it mines at 15-17Khs for some reason?

I have not entered any configuration settings save for the pool and coin user and password and type of coin. I've not input any conf. or .bat information like I would normally for CGMiner so I'm a bit stumped really but everyone here seems to confirm on the main it works so it's definitely something I'm not doing right and I was wondering if anyone could be so kind to point me in the right direction?

Many thanks

Faron

it also states that I am mining in GH at times as well which definitely isn't the case??

Is it possible to run 2 different profiles on CGWatcher at the same time? I have 2 GPUs on each profile. I know I can run 2 instances with a different profile in each, but I need it to resume both instances upon a reboot. It will only resume 1 instance.

try it and report

Is it possible to mine SHA and Scrypt simultaneously? I have ASICs hooked up, but mine scrypt on my GPU.

FIIIIIIXED!

Gabriel-... when you change clock or fan speeds in CGWatcher and click 'Apply', it is sending a command to cgminer (or bfgminer) telling it to make those changes.

Do you have auto-gpu enabled? If so, the miner is changing clock speeds automatically to keep the temperature around the temp-target range (default 75C). When the temperature reaches temp-overheat (default 85C) the miner will down-clock the GPU to cool it down... and then it should raise clock speeds back up once it's cool enough. If this is what is happening, you can either raise the temp-overheat setting or disable auto-gpu.

If you already have auto-gpu disabled, I really couldn't tell you why it isn't staying there. I would suggest trying to change clock speeds using something like Trixx or Afterburner and see if the same thing occurs.

Hi Milone,

Im currently mining LTC with CGWatcher with my HD5850.
Core Clock is 725 and Memory clock is 1000.
Hashrate is 270 kh/s while set up to 15 intensity. Temperature is 85C.

I want to edit core and memory clock to enhance gpu power and hashrate. But when I try to edit core from 725 to 730, it only lasts few second before going back to 725 again. I cant maintain my core clock to another amount.

Do you know why and can you please help me out ?

Thanks,
Gabriel.

I'm using this software for about 3 month and it saved me a lot of time. Thanks, Justin!

i noticed that sometimes after ~3-5min cgminer gets back to speed, but sometimes it does not. and also it seems to fail to report card as sick/dead.
i stopped cgwatcher for some time and noticed, that if i run cgminer minimized I get an extra 5kH!

i will keep an eye on that. maybe watching the cpu or memory clock could be a nice option.


will report if I find a pattern

thanks already!