Hey there. I've been trying for the past couple of hours to get two instances of CGWatcher/CGMiner up and have been unsuccessful. I have two copies of CGWatcher in different folders. They both point to IP 127.0.0.1, but one points to port 4020 and the other to 4029. The is reflected in the CGMiner config files as well. When starting the miner, the CGWatcher mining log shows that the miner has started activity on the desired port, but when starting the second instance of CGWatcher, it immediately picks up on it and asks to create a profile even though the "require this API port" box is checked. Any suggestions?
To give some more information: I start one instance of CGWatcher (port 4029).
[6/28/2013 10:30:11 PM] CGMiner (4644): Process started using "7970 Single" profile on port 4029.
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 0 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 1 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 2 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 3 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 4 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Pool 5 (pool) status is ALIVE
[6/28/2013 10:30:17 PM] CGMiner (4644): Current pool is Pool 0 (pool)
[6/28/2013 10:30:17 PM] CGMiner (4644): Network difficulty is now 52,989,060.
[6/28/2013 10:30:25 PM] CGMiner (4644): GPU0 (AMD Radeon HD 7900 Series) status is ALIVE
[6/28/2013 10:30:25 PM] CGMiner (4644): GPU1 (AMD Radeon HD 7900 Series) status is ALIVE
When everything is running, I open the second instance of CGWatcher (set on port 4020). It detects the first instance of CGWatcher on 4020 as seen here.
[6/28/2013 10:30:24 PM] CGMiner (4644): Process started using "Unknown" profile on port 4020.
[6/28/2013 10:30:24 PM] CGMiner (4644): Current pool is Pool 0 (@)
[6/28/2013 10:30:24 PM] CGMiner (4644): Network difficulty is now 0.
Somewhat a workaround (for anyone else running into this problem).
I created a bat file to just run the second instance of CGminer that I wanted. I already have a profile for it set up in CGWatcher. When the CGMiner instance was running from the bat file, I opened CGWatcher and it detected the profile I had already set for it. It monitors the one GPU properly while giving no stats for the second (which is good because each instance is running a separate GPU)
One thing I would like to see added to CGWatcher in the future is the ability to tune CGWatchers overheat temps, but it's thrown into the CGMiner config easily enough.