Specifications

405-00024-00GEVA User’s Reference
68 Rev 02; 9 November 2010
On the GEVA there are two “Gio” ports for I/O to the Camera and Power connectors, and one or
more “Gige” ports for the Cameras connected, shown in the left panel (see Figure 44). If you have
more Genie cameras connected through the network, or through GigE switches, there will be
more “Gige” ports, one for each camera. If you have a DCI-100 connected to the serial port, the
Digital I/O will also appear.
CamPort1 I/O connector
CamPort2 I/O connector
Genie Camera (1)
Genie Camera (2)
Figure 44. I/O Ports and 2 Cameras in VA-Genie Setup
iNspect uses the order of cameras as they appear in the “Gige” tree in the left panel of the VA-Ge-
nie Setup utility. They are normally ordered by their IP Addresses.
2. You can delete cameras, and change the order of cameras by right-clicking on the “Board #”
under the “Gige” tree. Correct the tree so you have only
the cameras controlled by this ap-
pliance, and they are in the correct order.
3. Pull down the File menu and select “Generate Portable Config File”. Navigate to the
D:iNspect\CameraFiles directory and save your configuration as “GEVcustom.txt”. The
“GEV” prefix is needed to make the file appear in the Camera and Language selector under
the GigE camera group.
4. Close the VAGenie Camera Setup utility.
5. Open the Camera Selector and select the “Custom” GEV file. Click “Set”.
iNspect uses the camera configuration file as a starting point, mainly for the camera order. The
Sensor Setup panel settings override the configuration file settings, and are saved in your Solu-
tion file. The GIO port settings in your GEVtest.txt file are not used by iNspect. The GEVA does
not use the GIOtest.txt file (used by the VA61).
The Configuration file created by VA-Genie Setup contains much more information than is actu-
ally used by the iNspect program. You can examine the default GEVtest.txt file in the iNspect
directory (original copy in the iNspect\CamFiles directory), and edit out the unnecessary infor-
mation in your custom configuration file.