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

RTDEMO.TXT Driver File Contents (xvl322cdinst.zip)

Real-Time Grab and Display Demo (RTDEMO) for DOS
------------------------------------------------

Version:
--------
V3.00, 96/7/19   Initial release.

Files:
------
        RTDEMO.EXE      - executable
        RTDEMO.C        - main
        GETINI.C,.H     - routines to extract data from .INI files
        VESA256.C,.H    - VESA graphics driver loader
        MAKEFILE        - make file
        VESA256.BGI     - VESA graphics driver
        RTDEMO.INI      - initialization parameters
        *.TIF           - Dipix logos

Description:
------------

This program grabs and displays images as fast as possible using XVL commands
from the host.

The demo has many options, all configurable from the file RTDEMO.INI.  All of
the .INI options are explained here.  In summary, the program can use single
buffering or double buffering.  A subimage within each image can be processed
using either an Arith or Filter transformation.  The results can optionally
be displayed as well.

Command Line Parameters:
------------------------

The program has the following command line sequence.  "rtdemo ?" will display
this usage message.

    Usage: rtdemo -b<BusMaster> -c<CpfName> -i<IoBase> -m<VesaMode>

        BusMaster : PCI bus mastering mode on = 1, off = 0 (default 1)
        CpfName   : Camera Parameter File name (default RS170ANA.CPF)
        IoBase    : ISA bus I/O base address (default 0x300)
        VesaMode  : VESA Video Mode (default 0x101)

More notes on command line parameters:

    BusMaster:  The flag is ignored on ISA or VLB systems.  There must
                be a memory manager running in order for this switch to
                take effect.

    CpfName:    If the file extension is not entered, .CPF is assumed.

    IoBase:     This is ignored on PCI bus.

    VesaMode:   The following VESA modes may be supported:
                    0x100, 640x400
                    0x101, 640x480
                    0x103, 800x600
                    0x105, 1024x768
                    0x107, 1280x1024

RTDEMO.INI
----------

The following are the sections of RTDEMO.INI and their descriptions.  The
comments in the .INI file itself explain the meaning of the variables.
These are some further comments and notes.

[Args]
The defaults of the command line arguments are set here.

[Image]
The options related to image grabbing, buffers and display are specified.
If bDoGrabbing is TRUE, then RTDEMO will grab using the specified CPF.

lNumImages specifies the number of image buffers will be allocated on
the DSP.  If 1 is selected, then single buffering will be performed.  This
is much slower because simultaneous grab and copy cannot be performed.
If set to 2, double buffering will be performed, but there is no working
buffer for Filter, so bProcessInPlace must be set to TRUE.  If set to 3,
double buffering will be performed and a working buffer may be used for
Filter.

[Graphics]
Specifies the graphics to be displayed.

If bUseXvlGraphics is TRUE, then graphics are drawn into the image on
the DSP.  If FALSE, they are drawn to the VGA after the image has been
displayed.  The advantage of using XVL graphics is that there is no
flicker.  The advantage of using VGA graphics is that it is faster.

[Logo]
If bDisplayLogo is TRUE, then use the file specified, and display at the
location specified.

[Processing]
Specifies which types of subimage processing to do.  If bDoArith and
bDoFilter are both FALSE, then the others are ignored.  bModifyKernel and
bProcessInPlace apply only to filters.

[CalculationWindow]
Specifies the initial location and size of the calculation window.  The
X upper left should be on a 4 byte boundary and the size should be a
multiple of 4 since DBK_MmtSetCalculationWindow rounds to the nearest
4 pixel boundary.

[Arith]
If bDoArith is TRUE, then use these values as parameters to DBI_Arith.

[Filter]
If bDoFilter is TRUE, then use these values as parameters to DBI_Filter.

[Kernel3]
If bModifyKernel is TRUE, and lKernelSize=3, then use this kernel definition.
The numbers must be separated by commas and no spaces.

[Kernel5]
If bModifyKernel is TRUE, and lKernelSize=5, then use this kernel definition.
The numbers must be separated by commas and no spaces.

[Kernel7]
If bModifyKernel is TRUE, and lKernelSize=7, then use this kernel definition.
The numbers must be separated by commas and no spaces.

[Bouncing]
If bBouncing is TRUE, then use these values to define the bouncing pattern.
The lXStep should be a multiple of 4 for the same reasons as setting the
initial calculation window position and size to a multiple of 4.

Note: In RTDEMO.INI, comments may not extend beyond 79 characters and
comments may not contain '='.

Notes on performance:
---------------------

The performance of RTDEMO varies widely.  The grab and display can do full
frame rate with RS-170 or CCIR on most PCI bus systems.  However, there
are PC configuration issues which affect performance.  See the separate
note on PCI bus BIOS options.

Reducing the number of lines to get full frame rate:
----------------------------------------------------

Because the program is running from the host, there is a command latency
which causes the top of frame to be missed when grabbing.  In order to
get full frame rate, it is necessary to reduce the number of lines grabbed.
This is done by changing the field VVideoActive in the CPF file.  The
following values should work:
    RS-170:     220 (440 lines)
    CCIR:       246 (492 lines)

Graphics:
---------

RTDEMO uses Borland GRAPHICS.LIB to display the live results.  If compiling
with another compiler, the graphics calls must be commented out.

The graphics requires the VESA graphics driver called VESA256.BGI.  The
file is located in the root of the XVL directory and must be copied to
the current directory.

Notes specific to running on the XPG-1000:
------------------------------------------

When running on the XPG and doing double buffering, there must be a bank
of memory on each of the Local and Global buses.

Notes specific to running on the FPG-44:
----------------------------------------

When running on the FPG-44 with only 512K, the program will only run
single buffered with a very small frame.  With 1 Mbyte, the program can
run double buffered, but no intermediate buffer unless the frame size
is reduced.