# This is a configuration file to launch the camera application configured for
# the CIS2521 sensor with CameraLink IO board. This should also act as a sample
# for how to create a configuration file that configures the application for 
# other sensors and IO boards.
#
# There can not be empty lines; # lines are comments and are ignored.
#
# The general format is TEXT_TAG for what the lines are.
# Valid TEXT_TAGS:
#      COMMAND_INTERFACE - says the following flag is a CommandInterface
#      SENSOR - says the sensor to instantiate
#      REPORT_INTERFACE - says the following flag is a StatusReporter
#      IO_CHANNEL - the method by which images are output.
#      TEC - declares a TEC is present for control.
#
# Launch the application by executing:
#     camera_application -f CIS2521_CAMLINK
#
# --------------------------------------------------------------------------- #
#
# Sensor:
#      There can only be one "sensor" object per board as this represents the
#      headboard. SENSOR must be the first TEXT_TAG or the -f must be preceded
#      by a valid -s command.
#  
# Valid Sensors:
#     0 - CIS2521; MUST be followed by a 1 to limit the clock or a 0 to not 
#         limit it (286 MHz)
#     1 - CMV300; MUST be followed by the /dev/ node for the spi device.
#
#     10000 - Add this before the real sensor flag and the camera will save off
#             the state when you change parameters (ROI, Exposure time etc) and
#             reload it on start up.
#
#     10001 - Debug "sensor" that prints out the functions being called.
SENSOR
0
0
#
# MityViewer acts over USB without interfering to other components.
COMMAND_INTERFACE
2
3
# IO Channel:
#      There can be N IO Channels for each method of IO. These should be placed
#      before the Command Interface(s) which controls them.
#
# Valid IO Channels:
#      0 - CameraLink; This currently is for both Expanded and Base modes.
#          Following line should be the start address of the CameraLink FPGA 
#          component with the proper prefix for the base (0x - hex, 0 - octal).
#      1 - Filesystem; This outputs to the filesystem. Configuration support is
#          possible through CameraLink Serial and stdin currently.
IO_CHANNEL
0
0xFF240000
# Command Interfaces:
#      There can be N CommandInterface objects for each possible mode of 
#      command entry. The command interface will control the IO channel 
#      preceeding it if applicable. There can be many CommandInterface objects 
#      after a single IO Channel. CommandInterface objects may also be an 
#      IO Channel; in these cases, just instantiate the CommandInterface and it
#      it will automatically use itself as the IO Channel. MityViewer will use
#      a provided IOChannel by default if one is provided.
#
#      Each CommandInterface MUST be preceeded by an IO_CHANNEL to control
#
# Valid command interfaces:
#      0 - CameraLink serial interface; should be followed by the /dev/ path to
#          the serial port device.
#      1 - stdin console interface.
#      2 - MityViewer acts as the interface.
COMMAND_INTERFACE
0
/dev/ttyS1
# Report Interface:
#     There can be N StatusReporter objects for each possible way of reporting
#
# Valid report interface flags:
#     0 - A PCA9553; next line should be "bus_addr_r_g_b"
REPORT_INTERFACE
0
1_0x62_1_2_0
