Instruction manual

support/drivers and updates.
5.1.6. Industrial requirements
Frame Grabber configuration tools has an extensive built-in camera support making it extremely easy to
use non-standard camera features (e.g. restart/reset).
Further, all signals essential to industrial applications are integrated into the Frame Grabber configuration
tools. Signals for pixel synchronous acquisition (external clock) and process control (external trigger) are
supported.
5.1.7. Cameras
With the default jumpering the board is set up for the use of CCIR/EIA-Cameras with no special features.
The software supports this camera types by default.
A list of cameras with special features which are already adapted to the software can be found in
Appendix A.
5.1.8. Developing own applications
The supplied software includes all the files you need to develop applications. It is required that you
include only one header file. This file includes all constant definitions, type definitions and function
prototypes. After compiling your application you need to link it with one of the different libraries. if your
application is to run under Windows, you need to link it with the import library eleye516.lib and run it using
the dll eleye516.dll. Note that the camera file eleye516.cam ( see Appendix A ) has to reside in the same
directory as eleye516.dll. see ELTEC Elektronik AG [http://www.eltec.de] selecting support/drivers and
updates for examples of application development using VC++
5.1.9. Allocating Image Memory
The advanced security-technique and virtual address-concepts of modern operation systems makes it
more difficult to request image memory which is accessible on fixed addresses or by multiple applications.
Additionally, modern video hardware is using flexible and fast DMA data transfers to move the images to
memory. But using DMA means that access to physical memory is needed to transfer the image data into
on board or system memory.
There are several solutions to provide the video hardware with necessary physical addresses. With
ELTEC Elektronik AG's imaging API there are different possibilities to request or to create image memory.
Dependent on the operating system used the library function el_InitHW() and el_NewMemBuffer() are
able to work with user defined or internal defined image buffers.
In general the library function mentioned above are allocating image memory and the user needs not to
care about requesting access permission and organizing and mapping the physical image memory to the
virtual address space of a user program. After the acquisition is finished the application is able to access
images in a very transparent way by using the supplied image pointers to walk through the image.
But there are different conditions depending on the operating system used to work with image memory
allocated by the application. For example if an application must use fixed memory addresses or more
than one application must access the image data to process different areas of the image simultaneous.
For this purposes the functions el_InitHW() and el_NewMemBuffer() are able to work with user defined
image buffers in the same way as they work with buffers defined inside these functions.
5.1.10. Multiple Grabbers
The software can handle multiple grabbers using the same library. The grabbers need not to be of the
Chapter 5. Programmers
Reference
49