Generating an new camera definition file (camdefs.ini)

mvAcquireControl, mvCAM3, mvCAM4, mvDELTA, mvGAMMA-G, mvSIGMA-SLC, mvSIGMA-SLG, mvSIGMA-SQ, mvTITAN-C16, mvTITAN-C8, mvTITAN-CL, mvTITAN-DIG, mvTITAN-G1, mvTITAN-RGB/G4, pcIMAGE-SC, pcIMAGE-SDIG, pcIMAGE-SG/SGVS, pcIMAGE-SRGB

You can use a simple and empty text file for generating the camera definition file. Its name must be camdefs.ini and must be in the directory ..windowsmatrix or ..winntmatrix. Only if these points are given the mvAcquireControl can read this file.

At the beginning of this file there can be unformated notes.

The camera definitions must be written after the mark [CameraDefs]. If this mark is not there no camera definition can be interpreted!
If this is the case only the standard definitions like PAL, SVHS, etc. are shown in the dialog "Select Camera" of the mvAcquireControl. These definitions are stored in the driver itself. In other programs not using the mvAcquireControl no camera definition except the standard ones can be selected by the command SelCamera.

After this mark all defintions can be insert which should be usable.

A simple camdefs.ini can be the following:

...
notes
...
[CameraDefs]

// notes

/* -------------------------- PAL ------------------------------------ */
/* Standard PAL */
DefCamType "PAL" VM_PAL INTERLACED 50 15625 13500 PCLK_INTERN
DefCamAcquireSetup "PAL" STANDARD NOT_INV NEXT_FIELD
DefCamAnalogParam "PAL" PAL 1 0 0 1200
DefHorizontalUnit "PAL" PIXEL
DefVerticalUnit "PAL" LINES
DefCamHorizontalAcquire "PAL" 140L 720L 1
DefCamVerticalAcquire "PAL" 19L 288L 1
DefCamClamp "PAL" 92L 5L
DefCamZero "PAL" 92L 5L
DefCamFieldGate "PAL" 288L 370L
...

Standard camera defintions like PAL, CCIR, NTSC etc are stored within the Windows32 driver and can be used although the file could not be read or the mark is missing.

Back