Config Files

Some files in the distribution config directory are expected to be modified.

These files are all in the config subdirectory, e.g.,

cfgNeon.0.0        configuration file for Neon w/SW value 0, master
cfgNeon.0.1        configuration file for Neon w/SW value 0, 1st slave
cfgNeon.0.2        configuration file for Neon w/SW value 0, 2nd slave
cfgNeon.0.3        configuration file for Neon w/SW value 0, 3rd slave
cfgNeon.1.0        configuration file for Neon w/SW value 1, master
etc.
cfgNeon.2.0        configuration file for Neon w/SW value 2, master
etc.
cfgNeon.3.0        configuration file for Neon w/SW value 3, master
etc.
cfgKarbon.0.0      configuration file for Karbon w/SW value 0, master
cfgKarbon.0.1      configuration file for Karbon w/SW value 0, 1st slave
etc.
cfgCtnCXP.0.0      configuration file for CtnCXP w/SW value 0, master
cfgCtnCXP.0.1      configuration file for CtnCXP w/SW value 0, 1st slave
etc.
cfgClxCXP.0.0      configuration file for ClxCXP w/SW value 0, master
cfgClxCXP.0.1      configuration file for ClxCXP w/SW value 0, 1st slave
etc.
cfgClxFXP.0.0      configuration file for ClxFXP w/SW value 0, master
cfgClxFXP.0.1      configuration file for ClxFXP w/SW value 0, 1st slave
etc.
cfgNeonDIF.0.0     configuration file for NeonDIF w/SW value 0, master
etc.

Config file naming convention

cfg<boardType>.<SW><.VFG>

where,
  boardType     - board type you want to configure. Like Neon, Karbon, CtnCXP, ClxCXP, ClxFXP etc.
  SW            - SW register value. Can be set using the two DIP switches on top of the frame grabber board. Can be 0, 1, 2 or 3.
  VFG           - Virtual Frame Grabber (VFG) to which the master link (CXP) or the Base link (CameraLink) from the camera is connected.

Config File Contents

A sample config file is as shown below:

#
#       All keys and values are case sensitive.
#
###
#
#       Filename for the camera attached to this VFG.
#
CameraFile      Ctn_BitFlow-Synthetic-AreaScan-1024x1024.bfml # default camera
#
#       NOTE:   A .bfml camera file may contain multiple modes of operation.
#                       To specify a mode by name use <name>@<camerafile>.bmfl, e.g.,
#CameraFile     StaticDiagonalWedge@BitFlow-Synthetic-AreaScan-1024x1024.bfml
#

The SW value is determined by the DIP switches on the BitFlow frame grabber PCI card. A configuration file is needed for each Virtual Frame Grabber (VFG) on each board.

The distribution files specify artificial data from the VFG w/o any camera attached. This is useful for testing the distribution file suite and kernel compatibility.

There are distribution files sufficient for all possible boards with up to 4 VFGs. Your actual hardware may support 1, 2, or 4 VFGs on the boards.

Using the config file to attach a camera file

The most reliable method of accessing any specific camera hardware is to

1. set the BitFlow frame grabber board SW register to 0, 1, 2, or 3

   (up to 4 identical boards installed in one PC are supported; the

   SW value for each board should be unique)

2. edit the config/cfg<boardType>.<SW><.VFG> file

   • insert a ‘#’ character in front of the existing “CameraFile” line

   • add a “CameraFile” line specifying the appropriate camera file

   • file specified must exist in the $BITFLOW_INSTALL_DIRS/camf directory or in the directory where you unzipped the camera files.

Setting the configuration file’s CameraFile line to the .r64/.anlg/.bfml/.ndif file matching the appropriate camera will easily and automatically initialize the BitFlow frame grabber interface for the specified camera.

Warning

NO OTHER FILES IN THE DISTRIBUTION DIRECTORY SHOULD BE MODIFIED IN ANY WAY.