GenICam standard
OEVIS® is compatible with all GenTL compliant industrial cameras.
In order to correctly detect and connect to the camera, these three conditions must be met:
- The camera manufacturer SDK and drivers must be correctly installed
- The camera manufacturer SDK package must include the GenTL producer file (
.ctifile) - The
GENICAM_GENTL64_PATHsystem environment variable must contain the path to the folder containing the desired GenTL producer file.
CTI File
The CTI file is an essential component for interfacing with a GenICam camera. It contains configuration details, features, and camera parameters. The CTI file is specific to the camera manufacturer and should be provided by the manufacturer.
GenTL
GenTL is an interface standard for communicating with image acquisition devices such as cameras and frame grabbers. GenTL allows software to communicate with cameras through a standardized API. CTI files are an integral part of GenTL and define how to communicate with a specific camera.
Using CTI Files
CTI files should be placed in one of the specific directories where GenTL searches for them during camera initialization. The software can then load the CTI file and establish communication with the camera based on its specifications.
On the Properties section of the Acquire tab you can select user level and camera's parameters.
CTI remarks & known issues
Here the list of CTI files with known issues and remarks.
| Vendor | Remarks & known issues |
|---|---|
| Daheng Imaging | Devices shown as already busy/open by others (even when they are not) during discovery. |
| Teledyne Dalsa | Does not provide a .cti. |
| JAI | Does not provide a .cti. |
| Pixelink | Issue parsing the GenICam configuration file (.xml). |
| Ximea | Devices are not found by discovery. |