1. xvl322cdinst.zip Driver
2. DSPAPP1.TXT File Contents

DSPAPP1.TXT Driver File Contents (xvl322cdinst.zip)

09-Apr-1997             APPLICATION 1
                        =============


This directory contains a sample which demonstrates a real time grab and
process application with continuous PC updates. It has been updated to
use the new Packet I/O routines to communicate with the PowerGrabber software.
The Send and Receive packet routines will use interrupt driven I/O under
Windows NT and Windows 95, and polling I/O under Windows 3.1 and MS-DOS.

The CPF file provided with this application requires an Analog Camera
Module (ACM) with the Power Bus address switch set to 0 and an analog
composite RS170 signal source.

This application calculates the average pixel value of each incoming
image in real time and returns the image number and average pixel value
to the PC for display. This program continues until the user hits a
key.

There are three concepts displayed in this sample application:

1) Double buffered continuous grabbing.
2) Use of the USER FIFO provided by the Packet I/O layer to provide
   application specific, user-definable communications between the host
   software and user software running on the DSP. This communications
   mechanism is interrupt driven under NT and 95.
3) The use of the Mask RAM's UserMask bits attached to DSP interrupts to
   provide frame synchronization with the frame grab.


The following files are contained in this directory.

dspapp1.txt  -  This file.

DSPAPP1.C    -  This is the DSP source code that contains the user function
                for this application.

DSPAPP1.MAK  -  This is the DSP make file for the dsp executable XDSPAPP1.OUT
                and FDSPAPP1.OUT.

XDSPAPP1.LNK -  This is the DSP link file for the dsp executable XDSPAPP1.OUT
FDSPAPP1.LNK -  This is the DSP link file for the dsp executable FDSPAPP1.OUT

DSPISR.ASM   -  This file contains the Interrupt Service Routine(ISR) that
                is attached to the IIOF0 interrupt resource in DSPAPP1.C.

USERFDT.ASM  -  This is the DSP's user function dispatcher table.

PROTOCOL.H   -  Contains protocol definitions for the PC and the DSP
                for application synchronization while the XCC is in
                asynchrounous mode.

PCAPP1.C     -  Source code for the PC side of this application.

MSVCAPP1.MAK -  Make file for MSVC V4.0 to create app132.exe, a Windows NT and
                Windows 95 Console Application.

PCMAKE.BAT   -  Batch file to compile and link the PC source file PCAPP1.C to
                create PCAPP1.EXE.
                This batch file compiles for the Borland C compiler.

RS170USE.CPF -  Camera parameter file for an analog RS170 camera with
                composite sync

pcapp1.ini:     Contains default initialization parameters.  Set for
                rs170 defaults.
                Use this file to specify the CPF file and the desired
                calculation window to use.  Commenting out the calculation
                window will cause the entire image frame to be processed.


Continuous image processing with a linescan camera:
===================================================

The application calculates the average pixel value per frame and displays the
result on the PC screen.  Because the PC display has such a slower update
rate than the line rate of a standard linescan camera, the application will
not run using single line frames.  (The PC display can not
keep up with the amount of information it must display and therefore the
entire application lags behind in lines.)  To account for this limitation,
the application grabs a frame of data with multiple lines from the linescan
camera and calculates the average of the 2D image.

Note that the DSP can keep up with the averaging on a line by line basis;
the PC simply can not keep up with the display all of the results for every
line.  In an actual application, this should not be a problem, because the PC
requirements will be different.


CPF File Modifications: (for a linescan camera CPF file)
-----------------------

The following parameter settings must be adhered to for the continuous mode
linescan example:

[FRAME TIMING]
...
HVideoStart             =must be > 0
HVideoActive            =X
VVideoStart             =0
VVideoActive            =Y
EndOfFrame              =1
EndOfLine               =1
HUserMask0Start         =HVideoStart + HVideoActive - 1
HUserMask0Active        =1
VUserMask0Start         =VVideoStart + VVideoActive - 1
VUserMask0Active        =1

[CAMERA CONTROL]
...
MultiImageGrab          =P_CONTINUOUS_IMAGE_GRAB


Where:
X is the number of pixel clocks of active video data per line
Y is the number of lines of data

Notes:
a. VVideoStart can be > 0.  However, this will result in VVideoStart
   lines being skipped per frame.
b. If HVideoStart = 0, the grabbed data will not be correct.
c. The linesync period must be greater than:
        (HVideoStart + HVideoActive) * pixel_clock_period
d. The end of frame synchronization interrupt will be ahead by
   one line, because the mask RAM skips line 0 on the very first frame.
   This means that the last line of data will be incomplete when the main
   DSP processing loop calculates the average.  However, by the time the DSP
   calculates the average sum for the first n-1 lines, the last line should
   have been grabbed from the camera.