2 How to Modify the dm.config File to Change Camera and System Assignments System Components 14:01:49 Channel 0 (Filter Driver): Microscan VISIONSCAPE CMG20 (1624x618) MAC="00-06-BE-00-09-4B" IP="192.168.254.2" Connected 14:01:49 Creating SW System 1: SoftSys1 14:01:50 Creating IO Server for System GigEVision1 14:01:51 Creating IO Server for System GigEVision2 14:01:52 Creating IO Server for System SoftSys1 You can now use the two cameras and systems independently. You could load the same job on both systems. Remember that, if using the Visionscape PCIe digital IO card, all systems share this resource. Make sure that you're not trying to use the same output line for two or more things.
Switching Out a Camera Imagine you have a production system with several cameras. All is working well but then someone manages to break one of the cameras. A spare camera is procured and put on the network in place of the damaged device. Will Visionscape automatically detect this change for you? The answer is no, not in the current version of Visionscape. What will happen is that the new camera will be added to the end of the resources list in the dm.config file. The uid for the new camera will be automatically added to the end of the GigEVision1 list. This probably isn't what you want.
In addition, the original, broken camera will still have entries in the dm.config file – the software doesn't know it is broken. Let's go back to our original dm.config file. We have one camera attached as shown in the listing below: instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> 8899 http://localhost DM true C:\dev\EngineSolution\EngineProcess\bin\Debug\Vision scape.EngineProcess.exe 9a2948d18361" /> Visionscape GigE Camera Guide 2-43