|================================================================================== Bandit-II Driver for Sapera Imaging Library for Windows NT/2000/XP 2.10.01.0126 February 22nd, 2006 Table of Contents - General Installation Notes - Windows 2000/XP Installation Notes - Disk Contents - Hardware Supported - New Features - Fixes - Driver Notes General Installation Notes: 1) First install Sapera LT if it is not already installed. Consult the Sapera LT User's Manual for more information. 2) Install the Bandit II board into the computer. Note: Consult the Bandit II User's Manual for detailed hardware and driver installation information. Windows 2000/XP Installation Notes: The Device Driver installation is slightly different than under Windows NT due to Plug & Play technology. When you reboot after installing the board, the "Found New Board" Wizard will be activated. Click CANCEL to stop the wizard. 3) Install the Bandit II Driver as follows: After inserting the Sapera LT CD, a CD browser screen will appear. Select the "Software Installation" menu and launch the Bandit II Device Driver installation. Follow the installation program's on-screen instructions. When you reboot, the "Found New Board" Wizard will find the correct driver for the Bandit II board. Finally, the Wizard will not find a Digital Signature. Ignore this warning. Click YES to continue the installation. Disk Contents Install root dir readme.txt history.txt \Bin Bandit II Viewer program Bandit II Fpga Loader \Sapera\CamFiles\User Frequently used CCF files for the Bandit II \Demos Demonstration Program \DisplayDriver Bandit II VGA Display Driver \FPGAs FPGAs Firmware \GraphicDriver Bandit II Independent Display Driver \Help Bandit II User Manual in Help format Bandit II User Manual in PDF format \Winnt\System32 Backup Dynamic Link Libraries (DLL's) \Winnt\System32\Drivers Backup Device driver files Windows system directory (winnt\system32) Dynamic Link Libraries (DLL's) Windows driver directory (winnt\system32\drivers) Device driver files Hardware Supported - Bandit II, CV Model, AGP/PCI - Bandit II, MV Model, AGP/PCI - Bandit II, RGB Model, AGP/PCI - Bandit II, Digital Model, AGP/PCI - Hirose Optional Module (for MV Model only) - I/O Optional Module (for MV and RGB model) - Digital Optional Module (for MV and RGB model) New Features - Multi-Processor support for Bandit II CV/MV models, Bandit II as the system display, 2000 & XP only. - Multi-Processor support for Bandit II, all models, Bandit II as an independent display device. - Buffer timestamp is now using same time base as the standard "Performance Counter" Fixes - Maximum allowable pixel clock for the Digital Module is now 4Mhz instead of 500kHz. - When Primary monitor is in 800x600 and the default 2nd monitor is set to PAL, bad synchronization signals could be output to the 2nd monitor. - TV settings: Flicker, Contraction & Position are now saved properly. Their values will be retain between reboots of the system. Driver Notes What is supported: All Models - Compatible with SAPERA version 4.00 and later (except where mentioned). - Support for Windows NT/2000/XP. - Buffer cycling: asynchronous, synchronous with/without trash buffer to host only - Frames or Fields acquisition: odd/even, even/odd, odd only, even only, next 2 fields. - Odd or Even field decimation. - Continuous acquisition, ‘n’ frames acquisition to overlay memory and/or host memory - Supports transfer events: End of Field, End of Frame, End of Odd, End of Even, End of Transfer - Dual Display support: VGA on primary, NTSC/PAL/VGA on secondary, same image or different image on both outputs, CV/PCI & MV model only Different image on monitors requires Sapera 4.10 and later. - Vertical Flipping, host memory only, requires Sapera 4.10 and later CV Model and RGB Model/CV Acquisition - Composite Video and Y/C - NTSC/PAL video format - Camera selector: Composite Video = 6, Y/C = 2 - Brightness, Contrast, Hue, Saturation control - Cropping/Scaling of input image - Pixel format of acquired images: YUY2 and Mono8. Note: Only YUY2 can be displayed using color key overlays - Grab Enable (active high only) - External Trigger (rising edge only) - Horizontal Flipping of acquired images (overlay & host memory) MV & RGB Model/Monochrome Acquisition - Monochrome Video - RS170/CCIR and non-standard video format - 30 kHz line rate - Camera selector: Monochrome = 3 - Brightness, Contrast control - Cropping of input image - Pixel format of acquired images: Mono8 or YUY2. Note: Only YUY2 can be displayed using color key overlays - Grab Enable (active high or low) - External Trigger (rising or falling edge) - 2 x 256 entry LUTs - Camera control: frame trigger, asynchronous reset, time integration - Strobe control RGB Model/RGB Acquisition - RGB Video - RS170/CCIR and non-standard video format - 30 kHz line rate - Brightness, Contrast control - Cropping of input image - Pixel format of acquired images: RGB-32. - Grab Enable (active high or low) - External Trigger (rising or falling edge) - 2 x 256 entry RGB LUTs - Camera control: frame trigger, asynchronous reset, time integration - Strobe control Digital Acquisition - Monochrome Video - Progressive video format - Number of input bits: 8, 10, 12 - Single channel, 8-bits in, monochrome 8-bit output format, up to 60MHz - Single channel, 8-bits in, monochrome 16-bit or YUV output format, up to 30MHz - Single channel (10 or 12 bits) up to 30 MHz per channel. - Dual channel 8 bits: Up to 30 MHz per channel, monochrome 8-bit output format. Up to 15 MHz per channel, YUV output format - Dual channel 10 bits up to 15 MHz per channel. - Dual Tap 8 bits, pixel alternate: up to 30 MHz per tap, monochrome 8-bit output format. Up to 15 MHz per tap, YUV output format. - Dual Tap 10 bits, pixel alternate, up to 15 MHz per tap. - Cropping of input image - Pixel format of acquired images: Mono8, Mono16 or YUY2. Note: Only YUY2 can be displayed using color key overlays - Grab Enable (active high or low) - External Trigger (rising or falling edge) - 2 x 8-bit in, 8-bit out LUTs, or 1 x 10-bit in, 8-bit out. - LUT bypass - Camera control: frame trigger, asynchronous reset, time integration - Strobe control Demo: - BanditIIPro executable demo was compiled with the Sapera 5.00 classes. What is not supported: - Multiple board support with one or more Bandit II as VGA boards. - Dual Display support with the RGB Model and all Bandit II AGP Models (WNT only). Known Limitations - Primary Display Driver must NOT be set to 256 color mode for proper acquisition to host buffers, as the conversion of images to 256 color will consume most of the CPU time. - Composite Video Input: maximum number of pixels per line before running out of bandwidth is 848 in YUV and 1040 in monochrome. - If using DMA transfers from a Host buffer to a Video buffer or from a Video Buffer to a Host buffer using a Transfer module, it is recommended to disable any animated cursors as this will reduce the performance of the system (increase of CPU usage). - When getting the HDC for the primary surface of the second monitor (function CorDisplayGetDC), the returned HDC has the properties of the 1st monitor (width, height and pixel depth). To get the actual values, use the Display module parameters CORDISPLAY_PRM_WIDTH/HEIGHT & PIXEL_DEPTH of the proper monitor. Note that if both monitors have a different pixel depth, some Windows device context functions might need to be tweaked to work properly. See the Bd2DualDisplay demo. - When the primary monitor is set to 800x600, the secondary monitor (Live image with overlay) does not support PAL output mode. - When acquiring images using the Bandit II optional Digital module on a Bandit II MV or RGB, the external trigger input signal must be connected to the connector of the digital daughter card. The external trigger input on the DIN-8 is used when acquiring images with the base board (ie. from the monochrome or RGB module). - Use of DirectDraw 3D functions under W2000/XP works properly as long as no DMA transfers of images are done (host buffer to video buffer or video buffer to host). - When running W2000/XP with more than one VGA card in Extended Desktop mode, the Bandit II must be the main VGA card on which the PC boots on by default. Once in Windows, the Bandit II must be selected as the Primary VGA card. Also, when creating video/overlay buffers using the Bandit II server, these buffers will be created on the Bandit II and not on any other VGA card present in the PC. If the Bandit II is not the primary VGA card: - one needs the Sapera Library version 5.00 or greater. - the 2nd monitor output "Live Image With Overlay" is not supported. - Floppy access fails on some computers when grabbing: added a registry entry (2.00 Build 102 and greater) HKLM\SYSTEM\CurrentControlSet\Services\CorBdii\Parameters\ForceOneDmaEntryPerLine) which enables a user to force one DMA entry per line. This will give enough breaks on the PCI bus for the floppy to work. Registry Value: 0 = Don't force one DMA entry per line, 1 = Force one DMA entry per line - Multi-Processor systems is supported under the following conditions only: - All Bandit II models when the Bandit II is used as an independent display device, WNT/W2000/XP. - Bandit II CV/MV when the Bandit II is used a system display, W2000/XP. Known Issues - Acquisition with the Bandit II MV/RGB, using separate sync, does not recognize the odd/even fields properly in the case of an interlaced video source. - The serial port will not work properly if the digitization clock is greater than 40 Mhz for single channel/tap cameras, 20 MHz for dual channel/dual tap cameras and 20 MHz if the output pixel format is RGB32. Symptoms are duplicated characters and/or missing characters. - In BanditIIPro demo, displaying the frame count in the video buffer will cause an error to occur after a certain number of frames acquired due to a memory leak in the Sapera LT 5.00 Classes. To fix the problem, recompile the demo with Sapera LT 5.10 classes. - If running BanditIIPro demo with the Bandit II as an independent display driver and with Sapera 5.10, you will need to recompile the demo with the Sapera LT 5.10 classes otherwise you will get the following error message: "Sapera Error", Error in "CorBufferNewEx" , Argument invalid value(7).