9
3.1. System module
The system module (also referred to as
TLSystem
), represents the GenTL producer (the
coaxlink.cti
library). This module is at the top of the parent/child tree.
The system module provides basic information about the GenTL producer: things like the
complete path to
coaxlink.cti
and the vendor name (Euresys).
The real point of the system module is to list the
(or frame grabbers) present in the
system. The most important functions of the system module are
TLGetNumInterfaces
(to
retrieve the number of frame grabbers in the system) and
TLOpenInterface
(to get access to
one of the frame grabbers).
3.2. Interface module
The GenTL standard calls frame grabbers
interfaces
. The system module has one child interface
for each frame grabber: if there are 2 Coaxlink cards in the computer, the system module will
have two child interfaces.
Each interface represents a frame grabber. Global frame grabber features such as digital I/O
lines belong in the interface module. This means that the
features controlling the I/O
lines are attached to the interface.
Each interface also acts as parent to one or several
. The most important functions of the
interface module are
IFGetNumDevices
(to retrieve the number of cameras that can be
connected to the interface) and
IFOpenDevice
(to get access to one of the devices).
3.3. Device module
The GenTL standard uses the terms
device
and
remote device
for two related but different
concepts. A
remote device
is a real camera, physically connected to a frame grabber. This is
different from the device module we describe here.
The device module is the module that contains the frame grabber settings relating to the
camera. This includes things like triggers and strobes.
The device module also acts as parent to one
, and can be viewed as the sibling of
the
remote device
. The most important functions of the device module are
DevOpenDataStream
(to get access to the data stream) and
DevGetPort
(to get access to the remote device).
3. GenTL
Coaxlink
Programmer Guide
