#
# CAMERA_MODEL 	"Generic 16"
#
# This is a generic camera configuration file, intended as a starting 
# place for creating a file for a new camera.  See the PCI DV User's
# guide for general information on configuration files, and the Camera
# Configuration Guide for detailed descriptions of the config file
# directives and arguments. 
# Unmodified, this file should work for a single-channel Camera-Link
# camera that outputs data continuously (no trigger required) in
# 1024x1024, 16-bits per pixel with the LSB on VD0 or MSB0.
#

# camera description, for camera selection GUI and apps
# camera_class should be the manufacturer's name
#
camera_class:                  "Generic"
camera_model:                  "Camera Link 16-bit"
camera_info:                   "1024x1024 (single ch., freerun)"

# actual width/height (total pixels) and depth of data from camera
# to only grab high 8-bits, set depth to 8 but leave extdepth set
# to actual depth, and adjust shift and mask accordingly
#
width:                         1024
height:                        1024
depth:                         16
extdepth:                      16

# rbtfile is ignored for std camera link board but needed
# for DV FOX (fiberoptic) (v3.3.4.9 or later)
#
rbtfile: aiagcl.bit

# camera link data path register bits:
# 0-3: number of bits per pixel - 1
# 4-7: number of channels (taps) - 1
#
CL_DATA_PATH_NORM:             0f

# camera link config register bits:
# 0: RGB (on for RGB color cameras only)
# 1: ignore data valid (on for most cameras though not all)
# 2: line scan
# 3: disable ROI (rarely set)
# 4: unused
# 5: data valid invert (rare)
# 6-7: undefined
#
CL_CFG_NORM:                   02

# htaps/vtaps: if dual channel flag is ON (see CL_CFG_NORM) we need to set
# either htaps or vtaps to 2. Which one depends on whether the two pixels
# that come out with each clock are both on the same line (uncomment
# htaps: 2) or on adjacent lines (uncomment vtaps: 2) 
#
#htaps:	2
#vtaps: 2

# interlace method
# only for interleaved and some dual channel cameras
# determines how image is deinterleaved for display -- WORD_INTLV is only
# one of many available methods -- see *_INTLV in pdv_dependent.h and
# camera configuration guide for more
#
#method_interlace:	WORD_INTLV

# the following directives can be used to send us any serial commands
# necessary to put the camera to put it into the expected state.
# serial_init takes a colon-separated list of ASCII commands, and should
# be used for cameras that use an ASCII serial command set. serial_binit
# takes a space-separated list of hex bytes, for cameras that use binary
# serial instead of ASCII.  Examples of commands that should be sent
# include those that put the camera into the desired trigger mode (e.g.
# continuous, triggered, controlled). Be sure to also configure the board
# for the matching mode, via MODE_CNTL_NORM and
# method_camera_shutter_timing.
#
#serial_init "CMD 1:CMD 2:CMD 3"
#serial_binit <00 11 aa bb>

# serial_term defines the termination character(s) that will be sent after each
# serial command sent by the library subroutine pdv_serial_command, including
# those sent by serial_init (above).  If no serial_term is specified, the
# default, carriage return character (0d hex) will be sent. If some other
# sequence is needed, uncomment serial_term and insert the appropriate hex
# byte(s) separated by spaces.  serial_term only applies to EDT's ASCII-specific
# serial directives (e.g. serial_init) and library subroutines (pdv_serial_command),
# NOT binary ones (serial_binit, pdv_serial_binary_command).  To specify no
# serial terminator, call serial_term with an empty list <>
#
#serial_term: <0d>

# shutter timing method. For continuous or triggered cameras, this should be left
# commented out or set to AIA_SERIAL, For controlled, or 'pulse-width' mode, where
# the board's shutter timer controls the exposure, set to AIA_MCL. These are the
# most common methods but not all -- see the manual for more methods.  Also look
# at the shutter_speed_min/max and serial_exposure directives in the camera
# configuration guide.
# NEW FEATURE as of pdvlib version 3.3.3.4 -- if MODE_CNTL_NORM is NOT set
# explicitly, it will be set to appropriate default  based on value of method_
# camera_shutter_timing. Likewise shutter_speed_min/max will be set to min/max
# board shutter timing values (0 and 25500) IF one of the MCL modes is set. So
# for many conditions, method_camera_shutter_timing is all that is needed.
#
#method_camera_shutter_timing: AIA_SERIAL
#method_camera_shutter_timing: AIA_MCL
#method_camera_shutter_timing: AIA_TRIG

# region of interest start and area
# vskip/hskip is how many pixels to skip before ROI, vert and horiz
# vactv/hactv is how many pixels to DMA to memory after skip, vert and horiz
# if full frame is desired, you can leave these commented out or make them the
# same as the camera width/height. hskip/hactv can also be used to trim columns
# for cameras that output non-4-byte-aligned data to multiple of 4 bytes (in
# width) to ensure proper operation of windows applications that depend on
# 4-byte alignment, e.g. pdvshow
#
#hskip: 0
#hactv: 1024
#vskip: 0
#vactv: 1024