==============================================================================
==============================================================================
==============================================================================
X X V V LLL LLL IIIII BBBBBB
X X V V L L III B B
X X V V L L I B B
X V V L L I BBBBB
X X V V L L I B B
X X V V L L L L III B B
X X V LLLLLLL LLLLLLL IIIII BBBBBB
==============================================================================
==============================================================================
Notes:
A) The release requires 42 megs of disk space on a disk with 16K block size.
B) Compiler versions:
DSP: TMS320 C/ASM - 4.7
XVL Software: xpg.out, xpg.lib, fpg.out, fpg.lib
and DSP samples.
DOS: MSVC 1.0 (Microsoft C/C++ Compiler 8.0) and ML 6.1 (Assembler)
XVL Software: xpgmlib.lib.
Borland C 4.5 and Tasm 3.1 (Borland Assembler)
XVL Software: xpgblib.lib, inter.exe, ppmhist.exe, pdemo.exe,
rtdemo.exe and PC samples.
Windows 3.1: MSVC 1.0 (Microsoft C/C++ Compiler) 8.0 and ML 6.1
XVL Software: wxpgmlib.lib, wxpgmlib.dll and wdemo.exe.
Windows NT and Windows 95: MSVC 4.0 (Microsoft C/C++ Compiler 10.0)
XVL Software: w32xpgml.dll, w32xpgml.lib and w32demo.exe.
- Borland 5.0
XVL Software: w32xpgbl.lib, w32xpgbl.dll
Direct Draw: DirectX V3.0
C) Note to DSP programmers using the DIPIX xpg.lib. The library uses
the TMS320C40 Parallel Runtime Support Library and some of it's
header files. This library and it's header files are stored in the
PRTS40.SRC file of the TI software package. To build this library
read chapter 1 of the "TMS320C4x Parallel Runtime Support Library"
manual. Use maker instead of make if using make from BORLAND 4.0.
D) The DSP DIPIX printf functions are not currently supported.
E) The JPEG image compression software is not currently supported.
F) PCI board notes:
- emm386.exe must be version 4.49 or greater for use under DOS.
- Use of the 16 bit DLL under Windows 95 is not tested or officially
supported. Use of the 32 bit DLL is recommended.
==============================================================================
XVL-Library Software Revisions
==============================================================================
XVL-BuildVersion: 00271
==============================================================================
Revision 3.22-30 (20-May-1998)
1. New
A) PC samples in DIPXPG\pc\samples:
A1) es1samp.c: This sample demonstrates grabbing an image from a
linepair camera and remapping the data to show the
image properly. It uses Kodak Megaplus ES 1.0 camera.
A2) rempsamp.c: This samples demonstrates how to set up for using the
EG & G 4013, with data remapping.
A3) fftsamp.c: This sample has been modified to run as a console
application under Windows 95 and Windows NT.
Compile with fftsamp.mak to create 32 bit .exe for Windows.
B) CPF files:
B1) egg4256.cpf: for EG&G MD4256C cameras
(requires 2 XPGs and 2 DCMs, each using this file).
B2) ham4880.cpf: for Hamamatsu 4880-85 areascan camera,
10 or 12 bits/pixel.
B3) temet.cpf : for Temet Vision Industry MSC camera (8 bits/pixel).
2. Bug fixes.
A) PC code:
A1) Account for 24 bit data in DPK_XDCGetImage and DPK_XDCPutImage.
A2) Fixes to DPS_TiffCopyImageToDisk to handle colour images properly.
A3) In DPK_InitXPG detect board variants which are running clocks speeds
other than 50mhz, and call DBK_SetDspClockSpeed to set the proper
DSP clock speed.
A4) Fix cpf loader for EOSRC bug which did not allow for detecting
externally supplied EvenOdd signal from camera.
A5) In DIPXPG\pc\samples\pcdirect\rtprcess fixed processing algorythm
to handle 16 bit data.
A6) Fixed all pcdirect samples and related DLL functions to close
handles properly.
A7) Fixed bug in Windows 95 VXD which hung the PC and required a hard
reboot. This problem occured when doing a transfer to or from a PC
buffer which started on a 4k boundary and had a multiple of 4k byte
length. This problem only occured when the buffer was created using
CreateDIBSection. The computation for the number of memory pages
(of 4K) was off by one causing the driver to try and lock a page
beyond the end of the buffer which when created with CreateDIBSection
appears to be non-existant memory.
A8) In DPU_GetEnvironmentVar check for validity of the path and return
P_ERROR_ENV_INVALID_PATH if it is not valid. The error was docu-
mented but the code was not implemented.
A9) The PC direct function DPW_RTStart now performs a check to determine
the number of com ports used by the camera. The PC direct software
only supports cameras with 1 or 2 com ports, so if the camera uses
more than 2 com ports then an error is returned
P_ERROR_RT_TOOMANY_COMPORTS.
A10)Fixes to DPW_DDDisplayPCImageInWindows to retry locking down the
display area if the first try failed.
B) DSP code:
B1) In DBK_MmtGetImageInfo account for 24 bit data. The PRO_MappedAddress
is computed the same as 8 bit data. Similarly the calculation
windows PRO_WindowStartOffset and PRO_NextWLineOffset are byte
offsets.
B2) In XDCSndImage and XDCRcvImage fix the LineOffset value when dealing
with 24 bit data for a calculation window.
B3) The app1 sample msvcapp1.mak was modified to reference the
w32xpgml.lib instead of the defunct wntxpgml.lib. The .exe file
has been renamed to app132.exe from ntapp1.exe.
B4) Fixed DBK_MmtReportFreeMemory to properly detect SRAM memory on a
XPG-PCI (it was always reported as 0).
B5) In DDF_FlushFifos shutdown unified mode. This fixes the problem
of the EDB hanging the system if the grab timed out or was aborted.
B6) Fixed Grab functions to only cause image resynchronization
for PCDirect.
B7) Fixed Grab bug did not allow acquisition to VGA for linescan cameras
under PCDirect.
B8) In DBI_WarpWithTable added a check to make sure that the images
calculation windows match. Also made sure that the warp buffer
has enough entries to process the calculation window.
B9) Fixed grab for interlaced cameras to handle 1 field grabs properly.
When grabbing a single field if you use the following cpf file
parameters:
[CAMERA CONTROL]
ImageFormat =P_IMAGE_FORMAT_RASTER
Field =P_FIELDS_IGNORE
NumFields =1
you may need to adjust the VVideoStart in the [FRAME TIMING].
If the NumField parameters is set to 1 then the grab will only
require a image size large enough for 1 field to work.
If the ImageFormat is raster and the Field value is ODD only or
even only then the image size only needs to be large enough for
that field instead of a full size image.
B10)Fixed intermittent grab time out problem for analog cameras on a
XPG, introduced in V3.21.
B11)Fixed DBF_SetInterlaceField function to set up the Module structure
register properly. The field value was being setup in the QGS
structure but the Module register values were not being recomputed.
C) Documentation.
C1) Divided Readme.txt file to two files: Readme.txt and ReadHist.txt.
Readme.txt contains information about latest release version only.
ReadHist.txt contains information about previous release versions.
3. Modified.
A) PC direct samples.
A1) DIPXPG\pc\samples\pcdirect\rtprcess\rtproc32.exe
- Modified to allow the disabling of the PC processing.
A2) The PC Direct samples DIPXPG\pc\samples\pcdirect\rtprcess\rtproc32.exe
has been modified to allow a user to display the images in memory. This
This option is the menu item called "DisplayImage" in the "File"
menu.
B) CPF Files.
B1) In egg2040.cpf changed LineSize value from 2048 to 2052 in
[FRAME TIMING] section.
B2) ntsc24.cpf, ntsc32.cpf, ntsc555.cpf, ntsc565.cpf,
rgb24.cpf, rgb32.cpf, rgb555.cpf, rgb565.cpf have been modified
to support burst mode and BRGB mode.
D) PC source.
D1) Modified PC source and include to replace FCHAR
(which means CHAR far) by CHAR PTRTYPE, for Borland Builder
compatibility.
D2) Modified w32xpgbl.mak which makes w32xpgbl.dll Borland DLL for 32
bit windows to link with cw32.lib instead of cw32i.lib, so that now
this library is linked in statically.
D3) New function DPW_XDCToWindowsDisplay:
This function receives an image from the XDC directly to the
display using DirectDraw. It uses GPDRTGrab instead of line by
line copying.
==============================================================================
For revision 3.21-09 (02-Dec-1997) and previous revisions see file ReadHist.txt
==============================================================================
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.