I'm still awaiting more info from KNC owners as they get their machines to get information regarding the best way to manage them with CGWatcher. CGRemote will work with anything running cgminer or bfgminer (I believe KNC uses cgminer). CGWatcher, as it is written now, is very dependent on the miner process to be running on the same computer as this gives it the most control over monitoring and resolving problems. While bfgminer may be able to act as a proxy for self-contained mining devices allowing CGWatcher to work, CGWatcher would be monitoring that bfgminer process and not the mining process running on the miner, which is not ideal. CGRemote will ultimately provide almost all of the functionality of CGWatcher, but can do it for multiple miners on any OS and in any location, all in one program.
If you're interested in
trying CGWatcher with a KNC miner, you would setup bfgminer and CGWatcher on the same computer similar to that of a Block Erupter Blade (assuming they work in the same manner). See bfgminer's README.ASIC.txt (more info online, including
this thread). You're basically pointing the mining device at the computer bfgminer (and CGWatcher) is running on. Set bfgminer's http-port to the same port the mining device is set to. The linked thread mentions it is only available for Win32 and Linux, so I would try it with the 32-bit version of bfgminer, not the 64-bit. Please report any problems/results so I can get them fixed. Once running, CGWatcher would then be watching the bfgminer process which would be displaying the device and stats it gets via http. I'm curious as to how API commands work when sent to bfgminer in this case, particularly privileged commands. Make sure to start bfgminer with the mining device's IP address in the api-allow W: group.
I'll also be making changes to CGWatcher and CGRemote that will allow changing profiles without restarting the miner. This feature has been requested even before ASICs as some people prefer to restart the miner as least often as possible. It will work any time the profile is switched to another profile using the same algorithm (sha256->sha256 or scrypt->scrypt). If any problems occur during the switch, it will restart the miner as a failsafe (what it currently does when switching profiles). Aside from changing pools, it will change any other config settings that can be set via API. If too many config settings are changed that cannot be set via API, then the miner can be restarted instead.
Right now I'm back to working on CGRemote's next update, so if anything is needed to add support or functionality in these miners I'll be adding it as quickly as possible. Any information or feedback regarding KNC miners is appreciated.