The AVP BackPlane Output Window provides useful data explained below. a. License Key Detection - When the AVP Backplane is launched, it first looks tor the HASP Software License. This can be seen in top two rows. The critical information is that it has found the license and detected that Visionscape GigE (x8) is detected. b. GigE Vision System Creation – The next step once is has found the GigE license is to create the GigE Vision System to contain all the discovered cameras. In this case, the system is called GigEVision1 . c. Adding Cameras to GigE System – In the next step, all discovered cameras are added to the GigEVision1 .
IP Addresses are automatically set into each camera based on the base NIC IP address. A system can have up to a total of 8 cameras, Cameras 1-8 (Channel 0-7). d. Warnings and Errors – Any informational warnings will be printed into the Backplane Output window in Yellow. Any errors will be printed into the Backplane in Red. The GigEVision1 System and the DM.Config File The AVPBackplane detects all cameras on the GigE and USB ports, and then organizes them into a single “vision system”. The system appears in the programming UIs as “ GigEVision1 ”. The c:\omron\vscape\DM\DM.Config file contains all the data for what cameras are connected, and for the order that they are connected in.
This can be seen in the AVPBackplane Debug window. If cameras are added to the system, they will be discovered and added to the DM.Config file the next time the AVPBackplane is started. See below. If cameras are disconnected from the system, they will continue to exist in the DM.Config file, and will be searched for when the AVPBackplane starts. For permanent removal, or when a different set of cameras is plugged into the system, it is recommended to delete the c:\omron\vscape\DM\DM.Config file, shut down the AVPBackplane, and then restart. The system will once again scan for all connected cameras and then create a new DM.Config file.
Using Sentech STC-M Cameras with AutoVISION and Visionscape Page 12 of 32