X64CL CZM Driver 
for
Sapera LT Imaging Library 
for
Windows XP / Vista / 7 / 8
(32/64 bit)
Version 1.10.01.3250 [Wow64]
Teledyne DALSA Inc., April 22nd, 2015
				
Table of Contents

•	Installation Notes
•	Disk Contents
•	Hardware Supported
•	Key Features
•	New Features
•	Fixes
·	Backward Compatibility
•	Notes
•	
•	
•	Installation Notes
•	
•		Please consult the X64-CL CZM User's manual for detailed installation procedure for the supported Operating Systems.
•	
•	
•	Disk Contents
•	
•	<X64CZMDIR>\
•		readme.rtf (this file)
•		history.rtf
•	
•	<X64CZMDIR>\Bin
•		Teledyne DALSA Device Manager utility program
•	X64-CL CZM Viewer program
•		
•	<X64CZMDIR>\FPGAs
•		Firmware Files
•	
•	<X64CZMDIR>\Help
•		X64-CL CZM User Manual in PDF format 
•	
•	<X64CZMDIR>\Inf
•		Windows XP/VISTA/7 Plug & Play driver files
•	
•	Windows system directory (windows\system32)                       
•		Dynamic Link Libraries (DLL's) 
•	
•	Windows driver directory (windows\system32\drivers)       
•		Device driver files   
•	
•	
•	
•	Hardware Supported
•	
•	·	X64-CL CZM and X64-CL CZM\Lite (with 32MB of on-board memory)
•	
•	
•	
•	Key Features
•	
•	·	Key Features for X64-CL CZM
•	·	Windows XP, VISTA, 7 and 8 (32/64 bits)
•	·	2 Base or 1 Medium Camera Link cameras
•	·	Linescan & areascan Camera Link cameras
•	Horizontal and vertical flipping
•	·	Monochrome 8, 10, 12, 14 and 16 bits per pixel
•	RGB 8, 10 and 12 bits per pixels 
•	Up to 4 taps
•	·	On-board serial port accessible as a standard PC COM port (1 per camera)
•	·	Dual-phase quadrature shaft encoder input
•	·	External Trigger input (2)
•	·	Internal frame trigger
•	·	Strobe output (2)
•	·	Input LUTs
•	Mono: 256x8-bit, 1024x10-bit, 1024x8-bit, 4096x12-bit, 4096x10-bit, 4096x8-bit Input LUTs per tap
•	Color: 3x256x8-bit (Base), 3x1024x10-bit or 3x4096x12-bit (Medium)
•	·	Time Slot (Time Multiplexing)
•	·	Bayer Decoding
•	·	Flat Field Correction
•	·	Frame Integration
•	
•	
•	·	Key Features for X64-CL CZM Lite
•	·	Windows XP, VISTA, 7 and 8 (32/64 bits)
•	·	1 Base Camera Link camera
•	·	Linescan & areascan Camera Link cameras
•	·	Monochrome 8, 10, and 12 bits per pixel
•	RGB 8 bits per pixels
•	·	On-board serial port accessible as a standard PC COM port
•	·	Dual-phase quadrature shaft encoder input
•	·	External Trigger input (2)
•	·	Internal frame trigger
•	·	Strobe output (1)
•	·	Input LUTs
•	Mono: 256x8-bit, 1024x10-bit, 1024x8-bit, 4096x12-bit, 4096x10-bit, 4096x8-bit Input LUTs per tap
•	Color: 3x256x8-bit
•	·	Bayer Decoding
•	·	Flat Field Correction
•	
•	
•	New Features
•	
•	Added support for Wow64 (Win7)
•	Added support for Windows 8 32-bit
•	
•	
•	Fixes

•	Because of a timing issue that has been introduced in  the FPGA firmware 1.10.1.3230 and later, the FPGA firmware included in this driver version is taken from the driver 1.10.01.3220 so it does not contain the “spectral dips” fix.
•	
•	This new driver has the fix for  the “BSOD” issue that was fixed with the driver 1.10.1.3240.
•	
•	Backward Compatibility
•	
•	Compatible with Sapera LT version 5.20 and later (XP), 6.02 and later (Windows Vista & Windows 7), 
6.02 and later (Windows 8 64-bit), 7.30 and later (Windows 8 32-bit)
7.10 and later (Windows 64-bit when using buffer type Scatter-Gather/Physical)
•	For Wow64 driver installation under 64-bit OS,  compatible with Sapera LT version 7.11.02.1057
•	

•	
•	Notes
•	
•	·	Cropping width must be a multiple of 8 pixels.
•	·	Horizontal active must be a multiple of 8 pixels/Taps with multi-tap camera
•	Serial ports are only available once a Sapera application has started/executed. This will be the case in most instances as Device Manager runs on every bootup. 
•	·	External Trigger Acquisition Callback
•	Line scan: edge and level trigger
•	Area scan: edge trigger only
•	·	Multi-board System: All X64-CL CZM boards must have the same configuration (2 Base or 1 Medium)
•	·	After a logoff, the user must reboot the system if he wants to use the serial port.
•	·	When windows prompt "Find new hardware X64-CL CZM board", the user must reboot the system in order to use the serial port.
•	Acquiring an image with one less line then the crop height will not set the buffer state with "CORBUFFER_VAL_STATE_OVERFLOW" bit.
•	DMA engine can only access 1st 4GB of PC memory. So under 64-bit OS,  Sapera frame buffer type supported are 'Contiguous' and 'Scatter-Gather/Physical'. Both of these buffer type guarantees that the buffer memory will be allocated in the 1st 4GB of PC memory. For Scatter-Gather/Physical support, SaperaLT 7.10.01.01003 and later is needed.
•	Note 1: Sapera classes will automatically detect buffer type supported and create the buffers accordingly.
•		Note 2: To know which buffer type driver supports:
•	- In C API application, use the function CORSTATUS CORAPIFUNC CorManIsBufferTypeSupported(CORSERVER server, UINT32 bufType, PUINT32 isSupported);
•	- In C++ application: Use SapBuffer::IsBufferTypeSupported(). 
•	Note 3: Sapera 7.10.01.1019 fixes ‘speed’ issue accessing Scatter-Gather/Physical memory.
•	·	Horizontal flip of a two alternated color taps is not supported.
•	·	4 taps of 8 bits with alternated taps and cameralink configuration "two bases" is not supported.
•	·	When doing a vertical flip, the transfer 'Start of Frame' event if requested will not be generated.
•	The buffer parameter CORBUFFER_PRM_SPACE_USED is updated only if the transfer event 'End of Frame' is registered.
•	The buffer state CORBUFFER_VAL_STATE_OVERFLOW is set only if the transfer event 'End of Frame' is registered.
•	Software Trigger is not available if an external trigger delay other than 0 is specified and the external trigger source is not set to 'Software Trigger'.
•