Teledyne DALSA Xtium-CL MX4 frame grabber User's Manual
The Xtium-CL MX4 is a high-performance frame grabber designed for use with Camera Link cameras. This board supports a wide range of Camera Link camera types and features high-speed data transfer rates. The Xtium-CL MX4 is ideal for applications that require high-resolution, high-speed image acquisition.
advertisement
Xtium-CL MX4
™
User's Manual
Edition 1.01
sensors | cameras | frame grabbers | processors | software | vision solutions
P/N: OC-Y4CM-MUSR0
www.teledynedalsa.com
NOTICE
© 2015 Teledyne DALSA, Inc. All rights reserved.
This document may not be reproduced nor transmitted in any form or by any means, either electronic or mechanical, without the express written permission of TELEDYNE DALSA. Every effort is made to ensure the information in this manual is accurate and reliable. Use of the products described herein is understood to be at the user’s risk. TELEDYNE DALSA assumes no liability whatsoever for the use of the products detailed in this document and reserves the right to make changes in specifications at any time and without notice.
Microsoft® is a registered trademark; Windows®, Windows® 7, Windows® 8 are trademarks of
Microsoft Corporation.
All other trademarks or intellectual property mentioned herein belongs to their respective owners.
Edition 1.01 released on June 15, 2015
Document Number:
Printed in Canada
OC-Y4CM-MUSR0
About Teledyne DALSA
Teledyne DALSA is an international high performance semiconductor and electronics company that designs, develops, manufactures, and markets digital imaging products and solutions, in addition to providing wafer foundry services.
Teledyne DALSA Digital Imaging offers the widest range of machine vision components in the world. From industry-leading image sensors through powerful and sophisticated cameras, frame grabbers, vision processors and software to easy-to-use vision appliances and custom vision modules.
Contents
User Programmable Configurations
ACUPlus: Acquisition Control Unit
DTE: Intelligent Data Transfer Engine
Sapera LT Library & Xtium-CL MX4 Driver Installation
Firmware Update: Automatic Mode
Executing the Firmware Loader from the Start Menu
Running a Silent Mode Installation
Running a Silent Mode Uninstall
Silent Mode Installation Return Code
Installation Setup with CorAppLauncher.exe
Custom Driver Installation using install.ini
Run the Installation using install.ini
Upgrading both Sapera and Board Driver
Viewing Installed Sapera Servers
Increasing Contiguous Memory for Sapera Resources
Contiguous Memory for Sapera Messaging
First Step: Check the Status LED
Possible Installation Problems
Xtium-CL MX4 User's Manual
Contents • i
Diagnostic Tool Self Test Window
Diagnostic Tool Live Monitoring Window
Checking for PCI Bus Conflicts
BSOD (blue screen) Following a Board Reset
Sapera and Hardware Windows Drivers
Recovering from a Firmware Update Error
Driver Information via the Device Manager Program
On-board Image Memory Requirements for Acquisitions
Symptoms: CamExpert Detects no Boards
Symptoms: Xtium-CL MX4 Does Not Grab
Symptoms: Card acquisition bandwidth is less than expected
CamExpert Example with a Monochrome Camera
Overview of Sapera Acquisition Parameter Files (*.ccf or *.cca/*.cvi)
Parameter Values Specific to the Xtium-CL MX4
Synchronization Signals for a 10 Line Virtual Frame
Supported Events and Transfer Methods
Supported Transfer Cycling Methods
General Outputs #1: Related Capabilities (for GIO Module #0)
General Outputs #1: Related Parameters (for GIO Module #0)
General Inputs #1: Related Capabilities (for GIO Module #1)
General Inputs #1: Related Parameters (for GIO Module #1)
ii • Contents
Xtium-CL MX4 User's Manual
Bidirectional General I/Os: Related Capabilities (for GIO Module #2)
Bidirectional General I/Os: Related Parameters (for GIO Module #2)
Xtium-CL MX4 Board Layout Drawing
Connector / LED Description List
Xtium-CL MX4 End Bracket Detail
Status LED Functional Description
Camera Link Camera Control Signal Overview
J1: External Signals Connector (Female DH60-27P)
J4: Internal I/O Signals Connector (26-pin SHF-113-01-L-D-RA)
Note 1: General Inputs / External Trigger Inputs Specifications
Block Diagram: Connecting External Drivers to General Inputs on J1 or J4
External Driver Electrical Requirements
Note 2: General Outputs /Strobe Output Specifications
Block Diagram: Connecting External Receivers to the General Outputs
External Receiver Electrical Requirements
Note 3: RS-422 Shaft Encoder Input Specifications
Example: Connecting to the RS-422 Shaft Encoder Block Diagram
Example: Connecting a TTL Shaft Encoder to RS-422 Inputs
J5: Multi-Board Sync / Bi-directional General I/Os
Configuration via Sapera Application Programming
Configuration via Sapera CamExpert
DH40-27S Cable to Blunt End (OR-YXCC-27BE2M1, Rev B1)
DH40-27S Connector Kit for Custom Wiring
Cable assemblies for I/O connector J4
Teledyne DALSA I/O Cable (part #OR-YXCC-TIOF120)
Board Sync Cable Assembly OR-YXCC-BSYNC40
Power Cable Assembly OR-YXCC-PWRY00
Xtium-CL MX4 User's Manual
Contents • iii
iv • Contents
Xtium-CL MX4 User's Manual
Tables
Table 1: Xtium-CL MX4 Board Product Numbers
Table 2: Xtium-CL MX4 Software Product Numbers
Table 3: Xtium-CL MX4 Cables & Accessories
Table 4: Xtium-CL MX4 Device Drivers
Table 5: Grab Demo Workspace Details
Table 6: Acquisition Timing Specifications
Table 7: CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE – Parameter Values
Table 8: Output LUT Availability
Table 9: Camera Related Capabilities
Table 10: Camera Related Parameters
Table 11: VIC Related Parameters
Table 12: Acquisition Related Parameters
Table 13: Transfer Related Capabilities
Table 14: Transfer Related Parameters
Table 15: GIO-0 Related Capabilities
Table 16: GIO-0 Related Parameters
Table 17: GIO-1 Related Capabilities
Table 18: GIO-1 Related Parameters
Table 19: GIO-2 Related Capabilities
Table 20: GIO-2 Related Parameters
Table 21: Xtium-CL MX4 - Servers and Resources
Table 22: Board Specifications
Table 23: Environment Specifications
Table 24: Power Specifications
Table 25: Board Connector List
Table 26: D1 Boot-up/PCIe Status LED
Table 27: Camera Link LED Status
Table 28: Camera Link Connector 1
Table 29: Camera Link Connector 2
Table 30: J1 & J4 Connector Signals
Table 31: External Trigger Timing Specifications
Table 33: OR-YXCC-H270000 Custom Wiring Kit
Table 34: Camera Link Cables Suppliers
Xtium-CL MX4 User's Manual
Contents • v
Figures
Figure 1: Automatic Firmware Update
Figure 2: Manual Firmware Update
Figure 3: Create an install.ini File
Figure 4: Sapera Configuration Program
Figure 5: Board Information via Device Manager
Figure 6: PCI Diagnostic Program
Figure 7: PCI Diagnostic Program – PCI bus info
Figure 8: Using Windows Device Manager
Figure 9: Board Firmware Version
Figure 10: PCI Diagnostic – checking the BUS Master bit
Figure 12: Saving a New Camera File (.ccf)
Figure 13: Grab Demo – Server Selection
Figure 14: Grab Demo Main Window
Figure 15: Xtium-CL MX4 Model Block Diagram
Figure 17: Encoder Input with Pulse-drop Counter
Figure 18: Using Shaft Encoder Direction Parameter
Figure 19: Synchronization Signals for a 10 Line Virtual Frame
Figure 22: End Bracket Details
Figure 23: CamExpert - Camera Link Controls
Figure 24: General Inputs Electrical Diagram
Figure 25: External Trigger Input Validation & Delay
Figure 26: General Outputs Electrical Diagram
Figure 27: RS-422 Shaft Encoder Input Electrical Diagram
Figure 28: Connecting TTL to RS-422 Shaft Encoder Inputs
Figure 29: Generating a DC Bias Voltage
Figure 30: DH60-27P Cable No. OR-YXCC-27BE2M1 Detail
Figure 31: Photo of cable OR-YXCC-27BE2M1
Figure 32: I/O Cable #OR-YXCC-TIOF120
Figure 33: Photo of cable OR-YXCC-BSYNC40
Figure 34: Photo of cable assembly OR-YXCC-PWRY00
vi • Contents
Xtium-CL MX4 User's Manual
Overview
Product Part Numbers
Xtium-CL MX4 Board
Item
Xtium-CL MX4
For OEM clients, this manual in printed form, is available on request
Table 1: Xtium-CL MX4 Board Product Numbers
Product Number
OR-Y4C0-XMX00
OC-Y4CM-MUSR0
Xtium-CL MX4 Software
Item
Sapera LT version 7.40 or later for full feature support (required but sold separately)
1. Sapera LT: Provides everything needed to build imaging application.
2. Current Sapera compliant board hardware drivers
3. Sapera documentation (compiled HTML help, Adobe Acrobat®
(PDF)
(optional) Sapera Processing Imaging Development Library includes over 600 optimized image-processing routines.
Table 2: Xtium-CL MX4 Software Product Numbers
Optional Xtium-CL MX4 Cables & Accessories
Item
DH60-27S cable assembly to blunt end:
6 ft cable I/O 27 pin Hirose connector to blunt end.
This cable assembly connects to J1.
(see "J1: External Signals Connector (Female DH60-27P) " on page 77)
Cable set to connect to J4 Internal I/O Signals connector
(J4: 26-pin SHF-113-01-L-D-RA)
DH40-27S Connector Kit for Custom Wiring:
Comprised of a DH40-27S connector plus screw lock housing kit
Cable assembly to connect to J5 (Board Sync)
Connecting 2 boards
Connection 3 or 4 boards
Power interface cable required when supplying power to cameras and/or
J1/J4
Power Over Camera Link (PoCL) Video Input Cable
2 meter HDR to MDR
2 meter HDR to HDR
Table 3: Xtium-CL MX4 Cables & Accessories
Product Number
OC-SL00-0000000
Contact Sales at
Teledyne DALSA
Product Number
OR-YXCC-BSYNC20
OR-COMC-POCLD2
OR-COMC-POCLDH
Xtium-CL MX4 User's Manual
Overview • 7
About the Xtium-CL MX4 Frame Grabber
Series Key Features
• Compliant with Camera Link specification version 2.0
•
Uses a PCIe x4 Gen2 slot to maximize transfers to host computer buffers
•
Acquire from Monochrome, RGB, Bayer and Bi-Color cameras, both area scan and linescan
• Supports multiple tap formats, in multiple pixels depths
• Pixel clock range from 20 to 85 MHz
•
Output lookup tables
•
White Balance Gain for RGB pixels
• Vertical and Horizontal Flip supported on board
•
External Input Triggers and Shaft Encoder inputs, along with Strobe outputs
•
Supports a number of acquisition events in compliance with "Trigger to Image Reliability"
•
RoHS compliant
• Supports Power Over Camera Link (PoCL)
See Technical Specifications for detailed information.
User Programmable Configurations
Use the Xtium-CL MX4 firmware loader function in the Teledyne DALSA Device manager utility to select firmware for one of the supported modes. Firmware selection is made either during driver
installation or manually later on (see Firmware Update: Manual Mode).
Firmware choices are:
• One Full Camera Link Input (installation default selection):
•
1 Base, 1 Medium or 1 Full Camera Link monochrome or bayer camera, 1/2/3/4/8 tap segmented, 2 taps alternate, or 2/3/4/8 taps parallel.
•
1 Base or 1 Medium Camera Link RGB camera, 1 tap and 2 taps segmented/parallel.
•
1 Full Camera Link packed RGB camera.
• One 80-bit Camera Link Input, with following support:
•
One 10 Tap @ 8-bit monochrome or bayer camera
•
One 8 Tap @ 10-bit monochrome or bayer camera
• One 80-bit packed RGB camera
• One 80-bit packed Bi-Color camera.
•
Two Base Camera Link Input, any 2 of the supported configuration:
•
Base Camera Link monochrome or Bayer camera, 1/2/3 tap segmented, 2 taps alternate,
2/3 taps parallel.
•
Base Camera Link RGB camera, 1 tap
ACUPlus: Acquisition Control Unit
ACUPlus consists of a grab controller, one pixel packer, and one time base generator per camera input. ACUPlus delivers a flexible acquisition front end and supports pixel clock rates of up to
85MHz.
ACUPlus acquires variable frame sizes up to 64KB per horizontal line and up to 16 million lines per frame. ACUPlus can also capture an infinite number of lines from a line scan camera without losing a single line of data.
8 • Overview
Xtium-CL MX4 User's Manual
DTE: Intelligent Data Transfer Engine
The Xtium-CL MX4 intelligent Data Transfer Engine ensures fast image data transfers between the board and the host computer with zero CPU usage. The DTE provides a high degree of data integrity during continuous image acquisition in a non-real time operating system like Windows.
DTE consists of multiple independent DMA units, Tap Descriptor Tables, and Auto-loading Scatter-
Gather tables.
PCI Express x4 Gen2 Interface
The Xtium-CL MX4 is a universal PCI Express x4 Gen2 board, compliant with the PCI Express 2.0 specification. The Xtium-CL MX4 board achieves transfer rates up to 1.7 Gbytes/sec. to host memory. Note that performance can be lower depending on PC and/or programmed configuration.
The Xtium-CL MX4 board occupies one PCI Express x4 Gen2 expansion slot and one chassis opening.
Important:
•
To obtain maximum transfer rate to host memory, make sure the Xtium-CL MX4 is in a Gen2 slot. Although the board will work in a Gen1 slot, only half the performance is achieved.
•
If the computer only has a PCI Express x16 slot, test directly or review the computer documentation to know if the Xtium-CL MX4 is supported. Many computer motherboards only support x16 products in x16 slots, which are commonly graphic video boards.
Advanced Controls Overview
Visual Indicators
Xtium-CL MX4 features 3 LED indicators to facilitate system installation and setup. These indicators provide visual feedback on the board status and camera status.
External Event Synchronization
Trigger inputs and strobe signals precisely synchronize image captures with external events.
Camera Link Communications Ports
One PC independent communication port per camera input provides Camera Link camera configuration. This port does not require addition PC resources like free interrupts or I/O address space. Accessible via the board device driver, the communication port presents a seamless interface to Windows-based standard communication applications like HyperTerminal, etc. The communication port is accessible directly from the Camera Link connectors.
Quadrature Shaft Encoder
An important feature for web scanning applications, the Quadrature Shaft Encoder inputs allow synchronized line captures from external web encoders. The Xtium-CL MX4 provides an RS-422 input that supports a tick rate of up to 5 MHz.
Xtium-CL MX4 User's Manual
Overview • 9
Development Software Overview
Sapera++ LT Library
Sapera++ LT is a powerful development library for image acquisition and control. Sapera++ LT provides a single API across all current and future Teledyne DALSA hardware. Sapera++ LT delivers a comprehensive feature set including program portability, versatile camera controls, flexible display functionality and management, plus easy to use application development wizards.
Applications are developed using either C++ or .NET frameworks.
Sapera++ LT comes bundled with CamExpert, an easy to use camera configuration utility to create new, or modify existing camera configuration files.
Sapera Processing Library
Sapera Processing is a comprehensive set of C++ classes or .NET classes for image processing and analysis. Sapera Processing offers highly optimized tools for image processing, blob analysis, search (pattern recognition), OCR and barcode decoding.
10 • Overview
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4
Warning! (Grounding Instructions)
Static electricity can damage electronic components. Please discharge any static electrical charge by touching a grounded surface, such as the metal computer chassis, before performing any hardware installation. If you do not feel comfortable performing the installation, please consult a qualified computer technician.
Important: Never remove or install any hardware component with the computer power on. Disconnect the power cord from the computer to disable the power standby mode.
This prevents the case where some computers unexpectedly power up when a board is installed.
Installation
The Sapera LT Development Library (or ‘runtime library’ if application execution without development is preferred) must be installed before the Xtium-CL MX4 device driver.

Turn the computer off, disconnect the power cord (disables power standby mode), and open the computer chassis to allow access to the expansion slot area.

Install the Xtium-CL MX4 into a free PCI Express x4 Gen2 expansion slot (or an available x8 slot). Note that some computer's x16 slot may support the Xtium-CL MX4.

Connect a spare power supply connector to J7 for PoCL cameras or when DC power is required
on the external signals connector J1 or J4. See Power Cable Assembly OR-YXCC-PWRY00 for
information about an adapter for older computers.

Close the computer chassis and turn the computer on.

Logon to the workstation as administrator or with an account that has administrator privileges.

Windows will find the Xtium-CL MX4 and start its Found New Hardware Wizard. Click on the
Cancel button to close the Wizard.
Sapera LT Library & Xtium-CL MX4 Driver Installation

Insert the Teledyne DALSA Sapera Essential CD-ROM. If AUTORUN is enabled on your computer, the installation menu is presented.

If AUTORUN is not enabled, use Windows Explorer and browse to the root directory of the CD-
ROM. Execute autorun.exe to start the installation menu.

From the CD Browser menu, select the Software Installation menu to install the required
Sapera components. Select the Xtium-CL MX4 Driver and required Sapera package. Click the
Next button to cycle through the various board product families.

If the installation of Sapera and Board Drivers is not done through the CD Browse applet, make sure Sapera LT is installed before any board drivers.

The installation program may prompt to reboot the computer. It is not necessary to reboot the computer between the installation of Sapera LT and the board driver. Simply reboot once all the software and board drivers are installed.

During the late stages of the installation, the Xtium-CL MX4 firmware loader application starts.
This is described in detail in the following section.

If Windows displays any unexpected message concerning the installed board, power off the system and verify the Xtium-CL MX4 is installed in the slot properly.
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 11
Refer to Sapera LT User’s Manual for additional details about Sapera LT.
Xtium-CL MX4 Firmware Loader
The Device Manager-Firmware Loader program automatically executes at the end of the driver installation and on every subsequent reboot of the computer. It will determine if the Xtium-CL MX4 requires a firmware update. If firmware is required, a dialog displays. This dialog also allows the user to load firmware for alternate operational modes of the Xtium-CL MX4.
Important: In the rare case of firmware loader errors please see Recovering from a Firmware
Firmware Update: Automatic Mode
Click Automatic to update the Xtium-CL MX4 firmware. The Xtium-CL MX4 supports various firmware configurations with the default being a Full, Medium, or Base camera.
See Series Key Features and User Programmable Configurations for details on all supported modes,
selected via a manual firmware update.
With multiple Xtium-CL MX4 boards in the system, all are updated with new firmware. If any installed Xtium-CL MX4 board installed in a system already has the correct firmware version, an update is not required. In the following screen shot, a single Xtium-CL MX4 Full board is installed and ready for a firmware upgrade.
Figure 1: Automatic Firmware Update
Firmware Update: Manual Mode
Select Manual mode to load firmware other then the default version or when, in the case of multiple Xtium-CL MX4 boards in the same system, if each requires different firmware.
The following figure shows the Device Manager manual firmware screen. Displayed is information on all installed Xtium-CL MX4 boards, their serial numbers, and their firmware components.
Do a manual firmware update as follows:
• Select the Xtium-CL MX4 to update via the board selection box (if there are multiple boards in the system)
• From the Configuration field drop menu select the firmware version required (typical required to support different cameras)
• Click on the Start Update button
•
Observe the firmware update progress in the message output window
•
Close the Device manager program when the device reset complete message is shown
12 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual
Figure 2: Manual Firmware Update
Executing the Firmware Loader from the Start Menu
If required, the Xtium-CL MX4 Firmware Loader program is executed via the Windows Start Menu shortcut Start • Programs • Teledyne DALSA • Xtium-CL MX4 Driver • Firmware Update. A firmware change after installation would be required to select a different configuration mode. See
User Programmable Configurations.
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 13
Requirements for a Silent Install
Both Sapera LT and the Xtium-CL MX4 driver installations share the same installer technology.
When the installations of Teledyne DALSA products are embedded within a third party’s product installation, the mode can either have user interaction or be completely silent. The following installation mode descriptions apply to both Sapera and the hardware driver.
Note: You must reboot after the installation of Sapera LT. However, to streamline the installation process, Sapera LT can be installed without rebooting before installing the board hardware device drivers. The installations then complete with a single final system reboot.
Perform Teledyne DALSA embedded installations in either of these two ways:

Normal Mode
The default mode is interactive. This is identical to running the setup.exe program manually from Windows (either run from Windows Explorer or the Windows command line).

Silent Mode
This mode requires no user interaction. A preconfigured “response” file provides the user input.
The installer displays nothing.
Silent Mode Installation
A Silent Mode installation is recommended when integrating Teledyne DALSA products into your software installation. The silent installation mode allows the device driver installation to proceed without the need for mouse clicks or other input from a user.
Preparing a Silent Mode Installation requires two steps:

Prepare the response file, which emulates a user.

Invoke the device driver installer with command options to use the prepared response file.
Creating a Response File
Create the installer response file by performing a device driver installation with a command line switch "-r". The response file is automatically named setup.iss and is saved in the \windows folder. If a specific directory is desired, the switch –f1 is used.
As an example, to save a response file in the same directory as the installation executable of the
Xtium-CL MX4, the command line would be:
Xtium-CL_MX4_1.00.00.0000 –r –f1”.\setup.iss”
Running a Silent Mode Installation
A device driver silent installation, whether done alone or within a larger software installation requires the device driver executable and the generated response file setup.iss.
Execute the device driver installer with the following command line:
Xtium-CL_MX4_1.00.00.0000 -s -f1".\setup.iss"
Where the –s switch specifies the silent mode and the –f1 switch specifies the location of the response file. In this example, the switch –f1".\setup.iss" specifies that the setup.iss file be in the same folder as the device driver installer.
Note: On Windows 7 and 8, the Windows Security dialog box will appear unless one has already notified Windows to ‘Always trust software from “Teledyne DALSA Inc.” during a previous installation of a driver.
14 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual
Silent Mode Uninstall
Similar to a silent installation, a response file must be prepared first as follows.
Creating a Response File
The installer response file is created by performing a device driver un-installation with a command line switch "-r". The response file is automatically named setup_uninstall.iss which is saved in the \windows folder. If a specific directory is desired, the switch “–f1” is used.
As an example, to save a response file in the same directory as the installation executable of the
Xtium-CL MX4, the command line would be:
Xtium-CL_MX4_1.00.00.0000 –r –f1”.\setup_uninstall.iss”
Running a Silent Mode Uninstall
Similar to the device driver silent mode installation, the un-installation requires the device driver executable and the generated response file setup.iss.
Execute the device driver installer with the following command line:
Xtium-CL_MX4_1.00.00.0000 -s -f1".\setup_uninstall.iss"
Where the –s switch specifies the silent mode and the –f1 switch specifies the location of the response file. In this example, the switch –f1".\setup_uninstall.iss" specifies that the
setup_uninstall.iss
file be in the same folder as the device driver installer.
Silent Mode Installation Return Code
A silent mode installation creates a file “corinstall.ini” in the Windows directory. A section called
[SetupResult] contains the ‘status’ of the installation. A value of 1 indicates that the installation has started and a value of 2 indicates that the installation has terminated.
A silent mode installation also creates a log file “setup.log” which by default is created in the same directory and with the same name (except for the extension) as the response file. The /f2 option enables you to specify an alternative log file location and file name, as in
Setup.exe /s /f2"C:\Setup.log"
.
The “setup.log” file contains three sections. The first section, [InstallShield Silent], identifies the version of InstallShield used in the silent installation. It also identifies the file as a log file. The second section, [Application], identifies the installed application name, version, and the company name. The third section, [ResponseResult], contains the ‘ResultCode’ indicating whether the silent installation succeeded. A value of 0 means the installation was successful.
Installation Setup with CorAppLauncher.exe
The installation setup can be run with the CorAppLauncher.exe tool provided with the driver.

Install the board driver and get CorAppLauncher.exe from the \bin directory of the installation.

When running the installation, CorAppLauncher.exe will return only when the installation is finished.

When run from within a batch file, obtain the installation exit code from the ERRORLEVEL value.

The arguments to CorAppLauncher.exe are
-l: Launch application
-f: Application to launch. Specify a fully qualified path.
As an example:

CorAppLauncher –l –f”c:\driver_install\Xtium-cl_MX4_1.00.00.0000.exe”

IF %ERRORLEVEL% NEQ 0 goto launch error
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 15
Note: There is a 32-bit and 64-bit version of CorAppLauncher.exe. When installing the driver, only the version related to the OS is installed. However, the 32-bit version is usable on either 32-bit or
64-bit Windows.
Custom Driver Installation using install.ini
Customize the driver installation by parameters defined in the file “install.ini”. By using this file, the user can:

Select the user default configuration.

Select different configurations for systems with multiple boards.

Assign a standard Serial COM port to board.
Creating the install.ini File

Install the driver in the target computer. All Xtium-CL MX4 boards required in the system must be installed.

Configure each board’s acquisition firmware using the Teledyne DALSA Device Manager tool
(see Device Manager – Board Viewer).

If a standard Serial COM port is required for any board, use the Sapera Configuration tool (see

When each board setup is complete, using the Teledyne DALSA Device Manager tool, click on the Save Config File button. This will create the “install.ini” file.
Figure 3: Create an install.ini File
Run the Installation using install.ini
Copy the install.ini file into the same directory as the setup installation file. Run the setup installation as normal. The installation will automatically check for an install.ini file and if found, use the configuration defined in it.
16 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual
Upgrading Sapera or Board Driver
When installing a new version of Sapera or a Teledyne DALSA acquisition board driver in a computer with a previous installation, the current version must be un-installed first. Described below are two upgrade situations. Note that if the board is installed in a different slot, the new
hardware wizard opens. Answer as instructed in section Installation.
Board Driver Upgrade Only
Minor upgrades to acquisition board drivers are distributed as ZIP files available in the Teledyne
DALSA web site www.teledynedalsa.com/mv/support . Board driver revisions are also available on the next release of the Sapera Essential CD-ROM.
Often minor board driver upgrades do not require a new revision of Sapera. To confirm that the current Sapera version will work with the new board driver:
•
Check the new board driver ReadMe file before installing, for information on the minimum
Sapera version required.
•
If the ReadMe file does not specify the Sapera version required, contact Teledyne DALSA
Technical Support (see Technical Support ).
To upgrade the board driver only:
•
Logon the computer as an administrator or with an account that has administrator privileges.
•
In Windows XP, from the start menu select Start • Settings • Control Panel • Add or
Remove Programs. Select the Teledyne DALSA Xcelera board driver and click Remove.
•
Windows XP only:
•
When the driver un-install is complete, reboot the computer.
•
Logon the computer as an administrator again.
•
In Windows 7, from the start menu select Start • Settings • Control Panel • Programs
and Features. Double-click the Teledyne DALSA Xcelera board driver and click Remove.
• In Windows 8, just type Control Panel while in the start screen, or click the arrow in the lower left side to bring up the all applications window. Select Programs and Features, then double-click the Teledyne DALSA Xcelera board driver and click Remove.
•
Install the new board driver. Run Setup.exe if installing manually from a downloaded driver file.
•
If the new driver is on a Sapera Essential CD-ROM follow the installation procedure
described in & Xtium-CL MX4 Driver.
•
Important: You cannot install a Teledyne DALSA board driver without Sapera LT installed on the computer.
Upgrading both Sapera and Board Driver
When upgrading both Sapera and the acquisition board driver, follow the procedure described below.
•
Logon the computer as an administrator or with an account that has administrator privileges.
•
In Windows XP, from the start menu select Start • Settings • Control Panel • Add or
Remove Programs. Select the Teledyne DALSA Xcelera board driver and click Remove.
Follow by also removing the older version of Sapera LT.
•
In Windows 7, from the start menu select Start • Settings • Control Panel • Programs
and Features. Double-click the Teledyne DALSA Xcelera board driver and click Remove.
Follow by also removing the older version of Sapera LT.
• In Windows 8, just type Control Panel while in the start screen, or click the arrow in the lower left side to bring up the all applications window. Select Programs and Features, then double-click the Teledyne DALSA Xcelera board driver and click Remove.
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 17
•
Reboot the computer and logon the computer as an administrator again.
•
Install the new versions of Sapera and the board driver as if this was a first time
installation. See Sapera LT Library & Xtium-CL MX4 Driver Installation and & Xtium-CL MX4
Driver for installation procedures.
Using the Camera Link Serial Control Port
The Camera Link cabling specification includes a serial communication port for direct camera
control by the frame grabber (see J3: Camera Link Connector 1 ). The Xtium-CL MX4 driver
supports this serial communication port either directly (such as the Serial Command window in
CamExpert) or by mapping it to a host computer COM port. Any serial port communication program, such as Windows HyperTerminal, can connect to the camera in use and modify its function modes via its serial port controls. The Xtium-CL MX4 serial port supports communication speeds from 9600 to 921600bps. The serial port is created by the kernel driver, so it will be available even if no Sapera LT application has started.
Note: if the serial communication program can directly select the Xtium-CL MX4 serial port then mapping to a system COM port is not necessary.
When required, map the Xtium-CL MX4 serial port to an available COM port by using the Sapera
Configuration tool. Run the program from the Windows start menu: Start • Programs • DALSA •
Sapera LT • Sapera Configuration.
COM Port Assignment
The lower section of the Sapera Configuration program screen contains the serial port configuration menu. Configure as follows:
•
Use the Physical Port drop menu to select the Sapera board device from all available
Sapera boards with serial ports (when more then one board is in the system).
•
Use the Optional COM Ports Mapping drop menu to assign an available COM number to that Sapera board serial port.
•
Click on the Save Settings Now button then the Close button. Reboot the computer at the prompt to enable the serial port mapping.
18 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual
Figure 4: Sapera Configuration Program
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 19
Displaying Xtium-CL MX4 Board Information
The Device Manager program also displays information about the Xtium-CL MX4 boards installed in the system. To view board information run the program via the Windows Start Menu shortcut Start
• Programs • Teledyne DALSA • Xtium-CL MX4 Device Driver • Device Manager.
Device Manager – Board Viewer
The following screen image shows the Device Manager program with the Information/Firmware tab active. The left window displays all Teledyne DALSA boards in the system and their individual device components. The right window displays the information stored in the selected board device.
This example screen shows the Xtium-CL MX4 board information.
Generate the Xtium-CL MX4 device manager report file (BoardInfo.txt) by clicking File • Save
Device Info. Teledyne DALSA Technical Support may request this report to aid in troubleshooting installation or operational problems.
Figure 5: Board Information via Device Manager
Information Field Description

Serial Number [Read-Only]: Serial Number of the board

Hardware ID [Read-Only]: This field will identify future hardware changes that affect the operation of the board. Currently there are no such changes.

Hardware Configuration [Read-Only]: This field will state the presence or absence of optional components. Currently there are no optional components available.

User Data [Read/Write]: This is a 64 byte general purpose user storage area. For information on how to read/write this field at the application level, contact Teledyne DALSA Technical
Support.

User Interface GIOs Reservation [Read/Write]: Use this field to reserve User Interface GIOs for use by the acquisition module. By default, boards are shipped with User Interface General
Inputs 1 & 2 reserved for External Triggers and User Interface General Outputs 1 & 2 reserved for Strobe Outputs.
Click on the ‘Value’ field to open the dialog box shown below. Disable any GIO reservations that are not required. Click the OK button to update the value field.
20 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual

User Interface GIOs Default Input Level [Read/Write]: Use this field to select the default input level of the User Interface GIOs. By default, boards are shipped with User Interface
General Inputs set to 24V. Note that the input level can also be modified at the application level.
Click on the ‘Value’ field to open the drop selection box shown below. Select the input signal level detection required.

Open Interface GIOs Reservation [Read/Write]: Use this field to reserve Open Interface
GIOs for use by the acquisition module. By default, boards are shipped with Open Interface
GIOs 1 & 2 reserved for Board Sync 1 & 2.
Click on the ‘Value’ field to open the dialog box shown below. Disable any GIO reservations that are not required. Click the OK button to update the value field.
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 21
Configuring Sapera
Viewing Installed Sapera Servers
The Sapera configuration program (Start • Programs • Teledyne DALSA • Sapera LT •
Sapera Configuration) allows the user to see all available Sapera servers for the installed
Sapera-compatible boards. The System entry represents the system server. It corresponds to the host machine (your computer) and is the only server that should always be present.
Increasing Contiguous Memory for Sapera Resources
The Contiguous Memory section lets the user specify the total amount of contiguous memory (a block of physical memory, occupying consecutive addresses) reserved for the resources needed for
Sapera buffers allocation and Sapera messaging. For both items, the Requested value dialog box shows the ‘CorMem’ driver default memory setting while the Allocated value displays the amount of contiguous memory allocated successfully. The default values will generally satisfy the needs of most applications.
The Sapera buffers value determines the total amount of contiguous memory reserved at boot time for the allocation of dynamic resources used for frame buffer management such as scattergather list, DMA descriptor tables plus other kernel needs. Adjust this value higher if your application generates any out-of-memory error while allocating host frame buffers or when connecting the buffers via a transfer object. You can approximate the worst-case scenario amount of contiguous memory required as follows:
•
Calculate the total amount of host memory used for one frame buffer
[number of pixels per line • number of lines • (2 - if buffer is 10/12/14 or 16 bits)].
•
Provide 200 bytes per frame buffer for Sapera buffer resources.
• Provide 64 bytes per frame buffer for metadata. Memory for this data is reserved in chunks of 64kB blocks.
• Provide 48 bytes per frame buffer for buffer management. Memory for this data is reserved in chunks of 64kB blocks.
• For each frame buffer DMA table, allocate 24 bytes + 8 bytes for each 4kB of buffer. For example, for a 120x50x8 image: 120x50 = 6000 = 1.46 4kB blocks -> roundup to 2 4kB blocks. Therefore 24 bytes + (2 * 8 bytes) = 40 bytes for DMA tables per frame buffer.
Memory for this data is reserved in chunks of 64kB blocks. If vertical flipping is enabled, one must add 16 bytes per line per buffer. For example, for an image 4080x3072 image: 16 bytes * 3072 = 49152 bytes.
• Note that Sapera LT reserves the 1 st
5MB of its own resources, which includes the 200 bytes per frame buffer mentioned above.
• Test for any memory error when allocating host buffers. Simply use the Buffer menu of the
Sapera Grab demo program (see Grab Demo Overview) to allocate the number of host
buffers required for your acquisition source. Feel free to test the maximum limit of host buffers possible on your host system – the Sapera Grab demo will not crash when the requested number of host frame buffers is not allocated.
•
The following calculation is an example of the amount of contiguous memory to reserve beyond 5MB with 80,000 buffers of 2048x1024x8: a) (80000 * 64 bytes) b) (80000 * 48 bytes) c) (80000 * (24 + (((2048*1024)/4kB) * 8))) = 323MB d) Total = a (rounded up to nearest 64kB) + b (rounded up to nearest 64kB) + c (rounded up to nearest 64kB).
22 • Installing Xtium-CL MX4
Xtium-CL MX4 User's Manual
Host Computer Frame Buffer Memory Limitations
When planning a Sapera application and its host frame buffers used, plus other Sapera memory resources, do not forget the Windows operating system memory needs.
A Sapera application using the preferred scatter gather buffers could consume most of the remaining system memory, with a large allocation of frame buffers. If using frame buffers allocated as a single contiguous memory block, Windows will limit the allocation dependent on the installed system memory. Use the Buffer menu of the Sapera Grab demo program to allocate host buffer memory until an error message signals the limit allowed by the operating system used.
Contiguous Memory for Sapera Messaging
The current value for Sapera messaging determines the total amount of contiguous memory reserved at boot time for messages allocation. This memory space stores arguments when a
Sapera function is called. Increase this value if you are using functions with large arguments, such as arrays and experience any memory errors.
Xtium-CL MX4 User's Manual
Installing Xtium-CL MX4 • 23
Troubleshooting Problems
Overview
The Xtium-CL MX4 (and the Xtium family of products) is tested by Teledyne DALSA in a variety of computers. Although unlikely, installation problems may occur due to the constant changing nature of computer equipment and operating systems. This section describes what the user can verify to determine the problem or the checks to make before contacting Teledyne DALSA Technical
Support.
If you require help and need to contact Teledyne DALSA Technical Support, make detailed notes on
your installation and/or test results for our Technical Support to review. Importantly, please be
clear about the problem being an installation issue or functional issue, and which of the following test tools were used.
Problem Type Summary
Xtium-CL MX4 problems are either installation types where the board hardware is not recognized on the PCIe bus (i.e. trained), or function errors due to camera connections or bandwidth issues.
The following links jump to various topics in this troubleshooting section.
First Step: Check the Status LED
Status LED D1 should be GREEN or flashing GREEN just after boot up. If it remains flashing RED, the board firmware did not load correctly. If LED D1 is BLUE or flashing BLUE, the board is running from the safe mode load.
Camera Link status is indicated by the two LEDs (D3, D4) mounted next to each Camera Link connector. These LEDs show the presence of the pixel clock and an active acquisition.
The complete status LED descriptions are available in the technical reference section (see Status
Possible Installation Problems

Hardware PCI bus conflict: When a new installation produces PCI bus error messages or the board driver does not install, it is important to verify that there are no conflicts with other PCI or system devices already installed. Use the Teledyne DALSA PCI Diagnostic tool as described in
Checking for PCI Bus Conflicts. Also verify the installation via the Windows Device Manager.

BSOD (blue screen) following a board reset: After programming the board with different
firmware, the computer displays the BSOD when the board is reset (see BSOD (blue screen)

Verify Sapera and Board drivers: If there are errors when running applications, confirm that
all Sapera and board drivers are running. See Sapera and Hardware Windows Drivers for
details. In addition, Teledyne DALSA technical support will ask for the log file of messages by
Teledyne DALSA drivers. Follow the instructions describe in Teledyne DALSA Log Viewer.

Firmware update error: There was an error during the Xtium-CL MX4 firmware update
procedure. The user can usually easily correct this. Follow the instructions Recovering from a

Installation went well but the board doesn't work or stopped working. Review these steps
described in Symptoms: CamExpert Detects no Boards.
Xtium-CL MX4 User's Manual
Troubleshooting Problems • 24
Possible Functional Problems

Driver Information: Use the Teledyne DALSA device manager program to view information
about the installed Xtium-CL MX4 board and driver. See Driver Information via the Device

On-Board Image Memory Requirements: The Xtium-CL MX4 on-board memory can provide
two frame buffers large enough for most imaging situations. See On-board Image Memory
Requirements for Acquisitions for details on the on board memory and possible limitations.

Inconsistent Acquisition Issues: Acquisition or functional problems that might be random or become frequent might point to a board temperature issue or hardware voltage instabilities.
Use the Board Hardware Diagnostic Tool to monitor and report these parameters, as described
in section Diagnostic Tool Overview.
Sometimes the problem symptoms are not the result of an installation issue but due to other system issues. Review the sections described below for solutions to various Xtium-CL MX4 functional problems.

Symptoms: Xtium-CL MX4 Does Not Grab


Symptoms: Card acquisition bandwidth is less than expected
Xtium-CL MX4 User's Manual
Troubleshooting Problems • 25
Troubleshooting Procedures
The following sections provide information and solutions to possible Xtium-CL MX4 installation and functional problems. The previous section of this manual summarizes these topics.
Diagnostic Tool Overview
The Xtium-CL MX4 Board Diagnostic Tool provides a quick method to see board status and health.
It additionally provides live monitoring of FPGA temperature and voltages, which may help in identifying problems.
Diagnostic Tool Main Window
The main window provides a comprehensive view of the installed Xtium board. Toolbar buttons execute the board self test function and open a FPGA live status window.
Important parameters include the PCI Express bus transfer supported by the host computer and the internal Xtium FPGA temperature. The bus transfer defines the maximum data rate possible in the computer, while an excessive FPGA temperature may explain erratic acquisitions due to poor computer ventilation.
26 • Troubleshooting Problems
Xtium-CL MX4 User's Manual
Diagnostic Tool Self Test Window
Click the Start button to initiate the board memory self test sequence. A healthy board will pass all memory test patterns.
Diagnostic Tool Live Monitoring Window
The three FPGA parameters listed on the main window can also be monitored in real time.
Choosing a parameter puts that graph at the top where the user can select the time unit and time range. Clicking the Output button will open a window displaying any error messages associated with that parameter.
Xtium-CL MX4 User's Manual
Troubleshooting Problems • 27
Checking for PCI Bus Conflicts
One of the first items to check when there is a problem with any PCI board is to examine the system PCI configuration and ensure that there are no conflicts with other PCI or system devices.
The PCI Diagnostic program (cpcidiag.exe) allows examination of the PCI configuration registers and can save this information to a text file. Run the program via the Windows Start Menu shortcut
Start • Programs • Teledyne DALSA • Sapera LT • Tools • PCI Diagnostics.
As shown in the following screen image, use the first drop menu to select the PCI device to examine. Select the device from Teledyne DALSA. Note the bus and slot number of the installed board (this will be unique for each system unless systems are setup identically). Click on the
Diagnostic button to view an analysis of the system PCI configuration space.
28 • Troubleshooting Problems
Xtium-CL MX4 User's Manual
Figure 6: PCI Diagnostic Program
Clicking on the Diagnostic button opens a new window with the diagnostic report. From the PCI
Bus Number drop menu, select the bus number that the Xtium-CL MX4 is installed in—in this example the slot is bus 10.
The window now shows the I/O and memory ranges used by each device on the selected PCI bus.
The information display box will detail any PCI conflicts. If there is a problem, click on the Save button. A file named ‘pcidiag.txt’ is created (in the Sapera\bin directory) with a dump of the PCI configuration registers. Email this file when requested by the Teledyne DALSA Technical Support group along with a full description of your computer.
Figure 7: PCI Diagnostic Program – PCI bus info
Windows Device Manager
An alternative method to confirm the installation of the Xtium-CL MX4 board and driver is to use the Windows Device manager tool. Use the Start Menu shortcut Start • Control Panel • System
• Device Manager. As shown in the following screen images, look for Xtium-CL MX4 board under
“Imaging Devices”. Double-click and look at the device status. You should see “This device is
Xtium-CL MX4 User's Manual
Troubleshooting Problems • 29
working properly.” Go to “Resources” tab and make certain that the device has an interrupt assigned to it, without conflicts.
Figure 8: Using Windows Device Manager
BSOD (blue screen) Following a Board Reset
Teledyne DALSA engineering has identified cases where a PC will falsely report a hardware malfunction when the Xtium-CL MX4 board is reset. The symptoms will be a Windows blue screen or PC that freezes following a board reset.
The 1 st
solution to this problem is to use the Xtium-CL MX4 driver 1.00 or higher along with Sapera
LT 7.40 or higher. If this still does not resolve the issue, then uninstall the driver and reinstall it using the switch “/cr”, which will not reset the board at the end of the installation but requires a reboot of the computer instead.

Example: Xtium-CL_MX4_1.00.00.0000.exe /cr
Sapera and Hardware Windows Drivers
Any problem seen after installation, such as an error message running CamExpert, first make certain the appropriate Teledyne DALSA drivers have started successfully during the boot sequence. Example, click on the Start • Programs • Accessories • System Tools • System
Information • Software Environment and click on System Drivers. Make certain the following drivers have started for the Xtium-CL MX4.
Device Description Type Started
CorXtiumCLMX4
CorLog
CorMem
CorPci
CorSerial
Xtium-CL MX4 messaging
Sapera Log viewer
Sapera Memory manager
Sapera PCI configuration
Sapera Serial Port manager
Kernel Driver
Kernel Driver
Kernel Driver
Kernel Driver
Kernel Driver
Table 4: Xtium-CL MX4 Device Drivers
Yes
Yes
Yes
Yes
Yes
Teledyne DALSA Technical Support may request that you check the status of these drivers as part of the troubleshooting process.
30 • Troubleshooting Problems
Xtium-CL MX4 User's Manual
Recovering from a Firmware Update Error
This procedure is required if any failure occurred while updating the Xtium-CL MX4 firmware on installation or during a manual firmware upgrade. If on the case the board has corrupted firmware, any Sapera application such as CamExpert or the grab demo program will not find an installed board to control.
Possible reasons for firmware loading errors or corruption are:
•
Computer system mains power failure or deep brown-out
•
PCI bus or checksum errors
•
PCI bus timeout conditions due to other devices
• User forcing a partial firmware upload using an invalid firmware source file
When the Xtium-CL MX4 firmware is corrupted, the board will automatically run from the Safe load after a board and/or PC reset.
Solution: Update the board using the standard method described in section Firmware Update:
Driver Information via the Device Manager Program
The Device Manager program provides a convenient method of collecting information about the installed Xtium-CL MX4. System information such as operating system, computer CPU, system memory, PCI configuration space, plus Xtium-CL MX4 firmware information is displayed or written to a text file (default file name – BoardInfo.txt). Note that this program also manually uploads firmware to the Xtium-CL MX4 (described elsewhere in this manual).
Execute the program via the Windows Start Menu shortcut Start • Programs • Teledyne DALSA
• Xtium-CL MX4 Device Driver • Device Manager. If the Device Manager Program does not run, it will exit with a board was not found message. Possible reasons for an error are:
•
Board is not in the computer
•
Board driver did not start or was terminated
• PCI conflict after some other device was installed
Information Window
The following figure shows the Device Manager Information screen. Click to highlight one of the board components and its information shows in the right hand window, as described below.
Xtium-CL MX4 User's Manual
Figure 9: Board Firmware Version
Troubleshooting Problems • 31
•
Select Information to display identification and information stored in the Xtium-CL MX4 firmware.
•
Select Firmware to display version information for the firmware components.
• Select one of the firmware components to load custom firmware when supplied by Teledyne
DALSA engineering for a future feature.
• Click on File • Save Device Info to save all information to a text file. Email this file when requested by Technical Support.
Teledyne DALSA Log Viewer
The third step in the verification process is to save in a text file the information collected by the
Log Viewer program. Run the program via the Windows Start Menu shortcut Start • Programs •
Teledyne DALSA • Sapera LT • Tools • Log Viewer.
The Log Viewer lists information about the installed Teledyne DALSA drivers. Click on File • Save and you will be prompted for a text file name to save the Log Viewer contents. Email this text file to Teledyne DALSA Technical Support when requested or as part of your initial contact email.
On-board Image Memory Requirements for Acquisitions
The Xtium-CL MX4 by default will allocate the maximum number of buffers that can fit in on-board memory based on the size of the acquired image before cropping, to a maximum of 65535 buffers.
Note that an application can change the default number of on-board frame buffers using the
Sapera LT API. Usually two buffers will ensure that the acquired video frame is complete and not corrupted in cases where the image transfer to host system memory may be interrupted and delayed by other host system processes. That is, there is no interruption to the image acquisition of one buffer by any delays in transfer of the other buffer (which contains the previously acquired video frame) to system memory.
If allocation for the requested number of buffers fails, the driver will reduce the number of onboard frame buffers requested until they can all fit.

For area scan cameras, a minimum of 2 on-board frame buffers is needed for proper operation.

For line scan cameras, if there is not enough memory for 2 on-board buffers, the driver will reduce the size such that it allocates two partial buffers. This mode is dependent on reading out the image data to the host computer faster than the incoming acquisition.
The maximum number of buffers that can fit in on-board memory can be calculated as follows:
(Total On-Board memory / (Buffer Size in Bytes + 256 Bytes used to store the DMA)). Note that when using the dual camera input configuration, the total on-board memory is divided evenly between the 2 inputs.
For example, assuming 512MB of on-board memory and acquiring 1024 x 1024 x 8 bit images, the number of on-board buffers would be: 512 MB / [(1024 x 1024) + 256] = 511.875 => 511 on- board buffers.
When running the board in the two Base Camera Link configuration, each input is assigned half of the on-board memory. In the case where there are 512 MB of on-board memory, each input will be assigned 256 MB.
Symptoms: CamExpert Detects no Boards
•
When starting CamExpert, with no Teledyne DALSA board detected, CamExpert will start in offline mode. There is no error message and CamExpert is functional for creating or modifying a camera configuration file. If CamExpert should have detected an installed board frame grabber, troubleshoot the installation problem as described below.
Troubleshooting Procedure
When CamExpert detects no installed Teledyne DALSA board, there could be a hardware problem, a system bus problem, a kernel driver problem, or a software installation problem.
32 • Troubleshooting Problems
Xtium-CL MX4 User's Manual
•
Make certain that the card is properly seated in PCIe slot.
•
Perform all installation checks described in this section before contacting Technical Support.
• Try the board in a different PCIe slot if available.
Symptoms: Xtium-CL MX4 Does Not Grab
You are able to start Sapera CamExpert but you do not see an image and the frame rate displayed is 0.
• Verify the camera has power.
•
Verify the Camera Link cable is connected to the camera.
•
Verify the camera and timing parameters with the camera in free run mode.
• Verify you can grab with the camera in free run mode.
• Make certain that you provide an external trigger if the camera configuration file requires one. Use the software trigger feature of CamExpert if you do not have a trigger source.
• Make certain that the camera configuration is the required mode. This must match the camera configuration file. Refer to your camera datasheet.
• Try to snap one frame instead of continuous grab.
•
Perform all installation checks described in this section before contacting Technical Support.
Symptoms: Card grabs black
You are able to use Sapera CamExpert, the displayed frame rate is as expected, but the display is always black.
•
Set your camera to manual exposure mode and set the exposure to a longer period, plus open the lens iris.
•
Try to snap one frame instead of continuous grab.
•
Make certain that the input LUT is not programmed to output all ‘0’s.
• A PCIe transfer issue sometimes causes this problem. No PCIe transfer takes place, so the frame rate is above 0 but nevertheless no image is displayed in CamExpert.
• Make certain that BUS MASTER bit in the PCIe configuration space is activated. Look in PCI
Diagnostics for BM button under “Command” group. Make certain that the BM button is activated.
Xtium-CL MX4 User's Manual
Figure 10: PCI Diagnostic – checking the BUS Master bit
Troubleshooting Problems • 33
•
Perform all installation checks described in this section before contacting Technical Support.
Symptoms: Card acquisition bandwidth is less than expected
The Xtium-CL MX4 acquisition bandwidth is less than expected.
•
Review the system for problems or conflicts with other expansion boards or drivers.
• Remove other PCI Express, PCI-32 or PCI-64 boards and check acquisition bandwidth again.
Engineering has seen this case where other PCI boards in some systems cause limitations in transfers. Each system, with its combination of system motherboard and PCI boards, will be unique and must be tested for bandwidth limitations affecting the imaging application.
•
Is the Xtium-CL MX4 installed in a PCI Express x16 slot?
Note that some computer's x16 slot may only support non x16 boards at x1 or not at all.
Check the computer documentation or test an Xtium-CL MX4 installation. The speed at which the board is running can be viewed using the Diagnostic Tool provided with the driver.
• Is the Xtium-CL MX4 installed in a PCI Express Gen1 slot?
Some older computers only have PCIe Gen1 slots. The Generation at which the board is running can be viewed using the Sapera LT PCI Diagnostic or the Diagnostic Tool provided with the driver.
34 • Troubleshooting Problems
Xtium-CL MX4 User's Manual
CamExpert Quick Start
Interfacing Cameras with CamExpert
CamExpert is the camera-interfacing tool for Teledyne DALSA frame grabber boards supported by the Sapera library. CamExpert generates the Sapera camera configuration file (yourcamera.ccf) based on timing and control parameters entered. For backward compatibility with previous versions of Sapera, CamExpert also reads and writes the *.cca and *.cvi camera parameter files.
Every Sapera demo program starts with a dialog window to select a camera configuration file. Even when using the Xtium-CL MX4 with common video signals, a camera file is required. Therefore,
CamExpert is typically the first Sapera application run after an installation. Obviously existing .ccf files can be copied to any new board installations when similar cameras are used.
CamExpert Example with a Monochrome Camera
The image below shows CamExpert controlling the Xtium-CL MX4. The camera (a Teledyne DALSA
Falcon) is outputting an internal monochrome 8-bit test pattern. After selecting the camera model, the timing parameters are displayed and the user can test by clicking on Grab. Descriptions of the
CamExpert sections follow the image.
Xtium-CL MX4 User's Manual
Figure 11: CamExpert Program
CamExpert Quick Start • 35
CamExpert groups parameters into functional categories. The parameters shown depend on the frame grabber used and what camera is connected. The parameter values are either the camera defaults or the last stored value when the camera was used. The descriptions below are with the
Xtium-CL MX4 and the Teledyne DALSA Falcon camera.

Device Selector: Two drop menus allow selection of which device and which saved configuration to use.
•
Device: Select which acquisition device to control and configure a camera file. Required in cases where there are multiple boards in a system and when one board supports multiple acquisition types. Note in this example, the installed Xtium-CL MX4 has firmware to support a monochrome Camera Link camera.
• Configuration: Select the timing for a specific camera model included with the Sapera installation or a standard video standard. The User's subsection is where user created camera files are stored.
•
Detection: The Settings button opens a menu to select the form of automatic camera detection, such as serial port text based controls or GenCP for Camera Link. The Detect
Camera button attempts to identify the connected camera.

Parameter Groups: Select a function category and change parameter values as required.
Descriptions for the camera parameters change dependent on the camera. The following information pertains to a Teledyne DALSA Falcon camera.
• Basic Timing: Provides or change static camera parameters.
•
Advanced Controls: Advanced parameters used to select various integration methods, frame trigger type, Camera Link controls, etc.
•
External Trigger: Parameters to configure the external trigger characteristics.
•
Image Buffer and ROI: Allows control of the host buffer dimension and format.
•
Display: An important component of CamExpert is its live acquisition display window, which allows immediate verification of timing or control parameters without the need to run a separate acquisition program. Grab starts continuous acquisition (button then toggles to
Freeze to stop). Snap is a single frame grab. Trigger is a software trigger to emulate an external source.
•
Output Messages and Video Status Bar: Events and errors are logged for review. Camera connection status is displayed where green indicates signal present.
•
Camera Link Serial Command: Select this Tab to open a serial command port to the camera.
This allows the user to issue configuration commands if supported by the camera.
The CamExpert tool is described more fully in the Sapera Getting started and Sapera Introduction manuals.
CamExpert Demonstration and Test Tools
The CamExpert utility also includes a number of demonstration features, which make CamExpert the primary tool to configure, test and calibrate your camera and imaging setup. Display tools include, image pixel value readout, image zoom, and line profiler.
Functional tools include support for either hardware based or software Bayer filter camera decoding with auto white balance calibration.
Camera Types & Files
The Xtium-CL MX4 supports digital area scan or line scan cameras using the Camera Link interface standard. Browse our web site [ http://www.teledynedalsa.com/imaging/ ] for the latest information on Teledyne DALSA Camera Link cameras.
36 • CamExpert Quick Start
Xtium-CL MX4 User's Manual
Camera Files Distributed with Sapera
The Sapera distribution includes camera files for a selection of Xtium-CL MX4 supported cameras.
Using the Sapera CamExpert program, you may use the camera files (CCA) provided to generate a camera configuration file (CCF) that describes the desired camera and frame grabber configuration..
Teledyne DALSA continually updates a camera application library composed of application information and prepared camera files. Camera files are ASCII text, readable with Windows
Notepad on any computer without having Sapera installed.
Overview of Sapera Acquisition Parameter Files (*.ccf or
*.cca/*.cvi)
Concepts and Differences between the Parameter Files
There are two components to the legacy Sapera acquisition parameter file set: CCA files (also called cam-files) and CVI files (also called VIC files, i.e. video input conditioning). The files store video-signal parameters (CCA) and video conditioning parameters (CVI), which in turn simplifies programming the frame-grabber acquisition hardware for the camera in use. Sapera LT 5.0 introduces a new camera configuration file (CCF) that combines the CCA and CVI files into one file.
Typically, a camera application will use a CCF file per camera operating mode (or one CCA file in conjunction with several CVI files, where each CVI file defines a specific camera-operating mode).
An application can also have multiple CCA/CCF files to support different image format modes supported by the camera or sensor (such as image binning or variable ROI).
CCF File Details
A file using the “.CCF” extension, (Camera Configuration files), is the camera (CCA) and frame grabber (CVI) parameters grouped into one file for easier configuration file management. This is the default Camera Configuration file used with Sapera LT 5.0 and the CamExpert utility.
CCA File Details
Teledyne DALSA distributes camera files using the legacy “.CCA” extension, (CAMERA files), which contain all parameters describing the camera video signal characteristics and operation modes
(what the camera outputs). The Sapera parameter groups within the file are:
• Video format and pixel definition
•
Video resolution (pixel rate, pixels per line, lines per frame)
•
Synchronization source and timing
• Channels/Taps configuration
•
Supported camera modes and related parameters
•
External signal assignment
CVI File Details
Legacy files using the “.CVI” extension contain all operating parameters related to the frame grabber board - what the frame grabber can actually do with camera controls or incoming video.
The Sapera parameter groups within the file are:
•
Activate and set any supported camera control mode or control variable.
•
Define the integration mode and duration.
• Define the strobe output control.
•
Allocate the frame grabber transfer ROI, the host video buffer size and buffer type
(RGB888, RGB101010, MONO8, and MONO16).
•
Configuration of line/frame trigger parameters such as source (internal via the frame grabber /external via some outside event), electrical format (TTL, RS-422, OPTO-isolated), and signal active edge or level characterization.
Xtium-CL MX4 User's Manual
CamExpert Quick Start • 37
Saving a Camera File
Use CamExpert to save a camera file (*.ccf ) usable with any Sapera demo program or user application. An example would be a camera file, which sets up parameters for a free running camera (i.e. internal trigger) with exposure settings for a good image with common lighting conditions.
When CamExpert is setup as required, click on File•Save As to save the new .ccf file. The dialog that opens allows adding details such as camera information, mode of operation, and a file name for the .ccf file. The following image is a sample for a Teledyne DALSA Falcon camera. Note the default folder where User camera files are saved.
Figure 12: Saving a New Camera File (.ccf)
Camera Interfacing Check List
Before interfacing a camera from scratch with CamExpert:
•
Confirm that Teledyne DALSA has not already published an application note with camera files [ www.teledynedalsa.com
].
•
Confirm that the correct version or board revision of Xtium-CL MX4 is used. Confirm that the required firmware is loaded into the Xtium-CL MX4.
•
Confirm that Sapera does not already have a .cca file for your camera installed on your hard disk. If there is a .cca file supplied with Sapera, then use CamExpert to generate the .ccf file with default parameter values matching the frame grabber capabilities.
•
Check if the Sapera installation has a similar type of camera file. A similar .cca file can be loaded into CamExpert and modified to match timing and operating parameters for your camera, and lastly save them as Camera Configuration file (.ccf).
• Finally, if there is no file for your camera, run CamExpert after installing Sapera and the acquisition board driver, select the board acquisition server, and manually enter the camera parameters.
38 • CamExpert Quick Start
Xtium-CL MX4 User's Manual
Sapera Demo Applications
Grab Demo Overview
Program Start•Programs•DALSA•Sapera LT•Demos•Frame Grabbers•Grab Demo
Program file
…\...\Sapera\Demos\Classes\vc\GrabDemo\Release\GrabDemo.exe
Workspace …\...\Sapera\Demos\Classes\vc\SapDemos.dsw
.NET
Solution
…\...\Sapera\Demos\Classes\vc\SapDemos_2003.sln
…\...\Sapera\Demos\Classes\vc\SapDemos_2005.sln
…\...\Sapera\Demos\Classes\vc\SapDemos_2008.sln
…\...\Sapera\Demos\Classes\vc\SapDemos_2010.sln
Description This program demonstrates the basic acquisition functions included in the Sapera library. The program either allows you to acquire images, in continuous or in onetime mode, while adjusting the acquisition parameters. The program code may be extracted for use within your own application.
Remarks
Based on Sapera C++ classes. See the Sapera User’s and Reference manuals for more information.
Table 5: Grab Demo Workspace Details
Using the Grab Demo
Server Selection
Run the grab demo from the start menu:
Start•Programs•Sapera LT•Demos•Frame Grabbers•Grab Demo.
The demo program first displays the acquisition configuration menu. The first drop menu displayed permits selecting from any installed Sapera acquisition servers (installed Teledyne DALSA acquisition hardware using Sapera drivers). The second drop menu permits selecting from the available input devices present on the selected server.
Xtium-CL MX4 User's Manual
Figure 13: Grab Demo – Server Selection
Sapera Demo Applications • 39
CCF File Selection
Use the acquisition configuration menu to select the required camera configuration file for the connected camera. Sapera camera files contain timing parameters and video conditioning parameters. The default folder for camera configuration files is the same used by the CamExpert utility to save user generated or modified camera files.
Use the Sapera CamExpert utility program to generate the camera configuration file based on timing and control parameters entered. The CamExpert live acquisition window allows immediate verification of those parameters. CamExpert reads both Sapera *.cca and *.cvi for backward compatibility with the original Sapera camera files.
Grab Demo Main Window
The Grab Demo program provides basic acquisition control for the selected frame grabber. The loaded camera file (.ccf) defines the Frame buffer defaults.
Figure 14: Grab Demo Main Window
Refer to the Sapera LT User's Manual (OC-SAPM-USER), in section "Demos and Examples –
Acquiring with Grab Demo", for more information on the Grab Demo and others provided with
Sapera LT.
40 • Sapera Demo Applications
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference
Block Diagram
SDR26 #1
Data &
Grab Controls
4
CLK
2
CC1
CC2
CC3
CC4
TX
RX
SDR26 #2
Data &
Grab Controls
4
CLK
2
SerDes
Receiver
LVDS
Drivers and
Receiver
UART #1
SerDes
Receiver
4
Time Base
24
24
Data &
Grab Controls
4
CLK
2
SerDes
Receiver
Indicators
Camera On/Grab On
Camera On/Grab On
Acquisition Status Indicator 1
Acquisition Status Indicator 2
J1 — DH60-27P
J4 — 26-pin SHF-113-01-L-D-RA
* Caution — connect only to one, never both
Quad Trigger /
General Inputs
Opto-coupled
Quad Strobe /
General Outputs
TTL
Dual Shaft Encoder
RS-422
I/O Controller
Power Out
Power Gnd
500 mA/reset
12V
24
D1
Board Status
Xtium-CL MX4
Simplified Block Diagram
Data
FVAL
LVAL
DVAL
SPARE
CLK
TX
RX
Data
FVAL
LVAL
DVAL
SPARE
CLK
ACU-Plus
Data
FVAL
LVAL
DVAL
SPARE
CLK
Control
Frame Buffer and
DMA table Memory
(512 MB)
Data
Data
DTE
Data-Transfer-Engine with OLUT
Data Control
PCI Express Gen2 X4 Controller
Host PCI Express X4 (or greater) Slot
Figure 15: Xtium-CL MX4 Model Block Diagram
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 41
Xtium-CL Flow Diagram
The following diagram represents the sequence in which the camera data acquired is processed through the Xtium-CL.
ACU-Plus
Camera Link
Front-End
Image
Buffer
Color
Conversion
(Bayer or Bi-
Color)
White-Balance
Gain (RGB
Pixels)
Horizontal Flip Cropper
Look Up
Table
Host
Computer
DTE

Camera Link Front End: Extracts the clock, LVAL, FVAL and data from the Camera Link ports based on the Camera Link configuration selected.

Memory: Stores the video data using the model of video frames.

Color Conversion: When enabled for particular cameras, converts Bayer and Bi-Color video data into RGB data.

White Balance Gain: Applies White Balance Gain to RGB data.

Cropper: Crops the resulting image when used, using a 4-byte resolution.

Horizontal Flip: Performs the line data flip process.

Lookup Tables: Applies lookup table transformation to the data going to the host memory.

Host DMA: Transfers the data from frame grabber into the host buffer memory. This module will also perform the vertical flip if enabled.
42 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
Acquisition Timing
DATA
first
7 last
8
PCLK
2
Pixel Clock Range: 20 MHz up to 85 MHz
LVAL/FVAL setup time
1
: Minimum 15ns
Min/Max
9
HB
5
LVAL
3
(Hsync)
FVAL
(Vsync)
Min/Max
4,9
VB
6
Figure 16: Acquisition Timing


1
The setup times for LVAL and FVAL are the same. Both must be high and stable before the rising edge of the Pixel Clock.
2
Pixel Clock must always be present





3
LVAL must be active high to acquire camera data
4
Minimum of 1
5
HB - Horizontal Blanking:
Minimum: 1 clock cycle
Maximum: no limits

6
VB - Vertical Blanking:
Minimum:
Maximum:
1 line no limits
7
First Active Pixel (unless otherwise specified in the CCA file – "Horizontal Back invalid = x" where ‘x’ defines the number of pixels to be skipped).


8
Last Active Pixel – defined in the CCA file under “Horizontal active = y" – where ‘y’ is the total number of active pixels per tap.
9
Maximum Valid Data:

8-bits/pixel x 64k Pixels/line (LVAL)

16-bits/pixel x 32k Pixels/line (LVAL)

32-bits/pixel x 16k Pixels/line (LVAL)

16 Million lines (FVAL)
Table 6: Acquisition Timing Specifications
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 43
Line Trigger Source Selection for Line scan
Applications
Line scan imaging applications require some form of external event trigger to synchronize line scan camera exposures to the moving object. This synchronization signal is either an external trigger source (one exposure per trigger event) or a shaft encoder source composed of a single or dual phase signal (also known as a quadrature).
The Xtium-CL MX4 shaft encoder inputs provide additional functionality with pulse drop, pulse multiply, and pulse direction support.
The following table describes the line-trigger source types supported by the Xtium-CL MX4. Refer to the Sapera Acquisition Parameters Reference Manual (OC-SAPM-APR00) for descriptions of the
Sapera parameters.
Parameter Values Specific to the Xtium-CL MX4
2
3
4
5
0
1
PRM Value Input used as:
External Line Trigger
Input used as:
External Shaft Encoder
if
CORACQ_PRM_EXT_LINE_
TRIGGER_ENABLE = true
From Shaft Encoder Phase A (default)
From Shaft Encoder Phase A
From Shaft Encoder Phase B n/a
From Board Sync #1
From Board Sync #2
if
CORACQ_PRM_SHAFT_
ENCODER_ENABLE =true
From Shaft Encoder Phase A & B (default)
From Shaft Encoder Phase A
From Shaft Encoder Phase B
From Shaft Encoder Phase A & B n/a n/a
Table 7: CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE – Parameter Values
CVI/CCF File Parameters Used
•
External Line Trigger Source = prm value
• External Line Trigger Enable = true/false
•
Shaft Encoder Enable = true/false
44 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
Shaft Encoder Interface Timing
Dual Balanced Shaft Encoder RS-422 Inputs:
• Input Phase A: Connector J1/J4: Pin 3 (Phase A +) & Pin 2 (Phase A -)
•
Input Phase B: Connector J1/J4: Pin 6 (Phase B+) & Pin 5 (Phase B-)
•
See J1: External Signals Connector (Female DH60-27P) for complete connector signal
details)
Web inspection systems with variable web speeds typically provide one or two synchronization signals from a web mounted encoder to coordinate trigger signals. These trigger signals are used by the acquisition linescan camera. The Xtium-CL MX4 supports single or dual phase shaft encoder signals. Dual encoder signals are typically 90 degrees out of phase relative to each other and provide greater web motion resolution.
Example using any Encoder Input with Pulse-drop Counter
When enabled, the triggered camera acquires one scan line for each shaft encoder pulse-edge. To optimize the web application, a second Sapera parameter defines the number of triggers to skip between valid acquisition triggers. The figure below depicts a system where a valid camera trigger is any pulse edge from either shaft encoder signal. After a trigger, the two following triggers are ignored (as defined by the Sapera pulse drop parameter).
K = Keep
D = Drop or Skip
K D D K D D K D D K D D K D D
Shaft Encoder phase A
Shaft Encoder phase B
Line acquired
Note: in this example, Number of trigger to drop = 2
Figure 17: Encoder Input with Pulse-drop Counter
Example using Sequential Encoder Input
Support of a dual phase encoder should consider the direction of motion of one phase signal to the other. Such a case might exist where system vibrations and/or conveyor backlash can cause the encoder to briefly travel backwards. The acquisition device must in those cases count the reverse steps and subtract the forward steps such that only pulses after the reverse count reaches zero are considered. By using the event “Shaft Encoder Reverse Counter Overflow”, an application can monitor an overflow of this counter.
The example figure below shows shaft encoder signals with high jitter. If the acquisition is triggered when phase B follows phase A, with jitter present phase B may precede phase A. Use of the Shaft Encoder Direction parameter will prevent false trigger conditions.
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 45
Shaft Encoder phase A
Shaft Encoder phase B
Figure 18: Using Shaft Encoder Direction Parameter
Note: Modify camera file parameters easily with the Sapera CamExpert program.
CVI/CCF File Parameters Used
Shaft Encoder Enable = X, where:
• If X = 1, Shaft Encoder is enabled
•
If X = 0, Shaft Encoder is disabled
Shaft Encoder Pulse Drop = X, where:
•
X = number of trigger pulses ignored between valid triggers
Shaft Encoder Pulse Multiply = X, where:
• X = number of trigger pulses generated for each shaft encoder pulses
Shaft Encoder Pulse Drop/Multiply Order = X, where:
•
If X = 1, the drop operation will be done first, followed by the multiplier operation
•
If X = 0 or 2, the multiplier operation will be done first, followed by the drop operation
Shaft Encoder Direction = X, where:
•
X = 0, Ignore direction
• X = 1, Forward steps are detected by pulse order A/B (forward motion)
•
X = 2, Forward steps are detected by pulse order B/A (reverse motion)
Note: For information on camera configuration files, see the Sapera Acquisition Parameters
Reference Manual (OC-SAPM-APR00).
Virtual Frame Trigger for Line Scan Cameras
When using line scan cameras, a frame buffer is allocated in host system memory to store captured video lines. To control when a video line is stored as the first line in this “virtual” frame buffer, an external frame trigger signal is used. For fixed length frames, the Sapera vertical cropping parameter controls the number of lines sequentially grabbed and stored in the virtual frame buffer. For variable length frames, the External Frame Trigger (when a level or dual input type is selected) controls the number of lines sequentially grabbed up to the maximum of lines in the virtual frame buffer.
Virtual Frame Trigger Timing Diagram
The following timing diagram shows an example of grabbing 10 video lines from a line scan camera and the use of a virtual frame trigger to define when a video line is stored at the beginning of the virtual frame buffer. The virtual frame trigger signal (generated by some external event) connects to the Xtium-CL MX4 trigger input.

Virtual frame trigger can be TTL, 12V, or 24V industry standard, and be rising or falling edge active, active high or low, or double pulse rising or falling edge.

In this example, virtual frame trigger control is configured for rising edge trigger.
46 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual

Virtual frame trigger connects to the Xtium-CL MX4 via the External Trigger Input 1 & 2 inputs.
•
Trigger Input #1 on connector J1: pin 8
•
Trigger Input #2 on connector J1: pin 9

Camera control signals are active at all times. These continually trigger the camera acquisition in order to avoid corrupted video lines at the beginning of a virtual frame.

The camera control signals are either timing controls on Xtium-CL MX4 shaft encoder inputs, or line triggers generated internally by the Xtium-CL MX4.

The Sapera vertical cropping parameter specifies the number of lines captured.
Synchronization Signals for a 10 Line Virtual Frame
The following timing diagram shows the relationship between External Frame Trigger input,
External Shaft Encoder input (one phase used with the second terminated), and camera control output to the camera.
Virtual Frame
Trigger
In
Shaft Encoder
In
Camera
Control
Out
LVAL
In
Video Line
In
10 Lines
Acquired
n Lines
Ignored
Notes: • In this example -- 10 lines are acquired
• The Maximum frame rate = Max. Line Rate / nb lines (Hz)
• In / Out signal reference is relative to frame grabber
Figure 19: Synchronization Signals for a 10 Line Virtual Frame
CVI File (VIC) Parameters Used
The VIC parameters listed below provide the control functionality for virtual frame reset. Sapera applications load pre-configured CVI files or change VIC parameters during runtime.
Note: Sapera camera file parameters are easily modified by using the CamExpert program.
External Frame Trigger Enable = X, where: (with Virtual Frame Trigger enabled)
•
If X = 1, External Frame Trigger is enabled
• If X = 0, External Frame Trigger is disabled
External Frame Trigger Detection = Y, where:
If Y= 1, External Frame Trigger is active low
• If Y= 2, External Frame Trigger is active high
•
If Y= 4, External Frame Trigger is active on rising edge
•
If Y= 8, External Frame Trigger is active on falling edge
•
If Y= 32, External Frame Trigger is dual-input rising edge
• If Y= 64, External Frame Trigger is dual-input falling edge
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 47
Note:. For dual-input triggers, Trigger Input #1 signals the start of the frame trigger, Trigger
Input #2 signals the end of the frame trigger.
External Frame Trigger Level = Z, where: (with Virtual Frame Trigger signal type)
• If Z= 1, External Frame Trigger is a TTL signal
• If Z = 8, External Frame Trigger is a 24V signal
•
If Z = 64, External Frame Trigger is a 12V signal
Note: For information on camera configuration files, see the Sapera Acquisition Parameters
Reference Manual (OC-SAPM-APR00).
Sapera Acquisition Methods
Sapera acquisition methods define the control and timing of the camera and frame grabber board.
Various methods are available, grouped as:
•
Camera Trigger Methods (method 1 supported)
•
Line Trigger Methods (method 1)
•
Line Integration Methods (method 1 through 4 supported)
• Time Integration Methods (method 1, 3, 5, 6, 8)
•
Strobe Methods (method 1, 3, 4 supported)
Refer to the Sapera LT Acquisition Parameters Reference manual (OC-SAPM-APR00) for detailed information concerning camera and acquisition control methods.
Trigger to Image Reliability
Trigger-to-image reliability incorporates all stages of image acquisition inside an integrated controller to increase reliability and simplify error recovery. The trigger-to-image reliability model brings together all the requirements for image acquisition to a central management unit. These include signals to control camera timing, on-board frame buffer memory to compensate for PCI bus latency, and comprehensive error notification. If the Xtium-CL MX4 detects a problem, the application can take appropriate action to return to normal operation.
The Xtium-CL MX4 is designed with a robust ACU (Acquisition and Control Unit). The ACU monitors in real-time, the acquisition state of the input plus the DTE (Data Transfer Engine) which transfers image data from on-board memory into PC memory. In general, these management processes are transparent to end-user applications. With the Xtium-CL MX4, applications ensure trigger-to-image reliability by monitoring events and controlling transfer methods as described below:
48 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
Supported Events and Transfer Methods
Listed below are the supported acquisition and transfer events. Event monitoring is a major component to the Trigger-to-Image Reliability framework.
Acquisition Events
Acquisition events pertain to the acquisition module. They provide feedback on the image capture phase.
•
External Trigger (Used/Ignored)
Generated when the external trigger pin is asserted, which indicates the start of the acquisition process. There are two types of external trigger events: ‘Used’ or ‘Ignored’.
Following an external trigger, if the event generates a captured image, an External Trigger
Used event will be generated (CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER).
If there is no captured image, an External Trigger Ignored event will be generated
(CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER_IGNORED). An external trigger event is ignored if the event rate is higher than the possible frame rate of the camera.
• Start of Frame
Event generated during acquisition, with the detection of the start of a video frame by the board acquisition hardware. The Sapera event value is
CORACQ_VAL_EVENT_TYPE_START_OF_FRAME.
•
End of Frame
Event generated during acquisition, with the detection of the end of a video frame by the board acquisition hardware. The Sapera event value is
CORACQ_VAL_EVENT_TYPE_END_OF_FRAME.
•
Data Overflow
The Data Overflow event indicates that there is not enough bandwidth for the acquired data transfer without loss. Data Overflow would occur with limitations of the acquisition module and should never occur.
The Sapera event value is CORACQ_VAL_EVENT_TYPE_DATA_OVERFLOW.
•
Frame Valid
Event generated on detection of the start of a video frame by the board acquisition hardware. Acquisition does not need to be active; therefore, this event can verify a valid signal is connected. The Sapera event value is
CORACQ_VAL_EVENT_TYPE_VERTICAL_SYNC.
• Pixel Clock (Present/Absent)
Event generated on the transition from detecting or not detecting a pixel clock signal. The
Sapera event values are CORACQ_VAL_EVENT_TYPE_NO_PIXEL_CLK and
CORACQ_VAL_EVENT_TYPE_PIXEL_CLK.
•
Frame Lost
The Frame Lost event indicates that an acquired image failed to transfer to on-board memory. An example is if there are no free on-board buffers available for the new image.
This may be the case if the image transfer from onboard buffers to host PC memory is not sustainable due to bus bandwidth issues or no host buffers are available to receive an image.
The Sapera event value is CORACQ_VAL_EVENT_TYPE_FRAME_LOST.
•
External Line Trigger Too Slow
Event which indicates that the detected shaft encoder input tick rate is too slow for the device to take into account the specified shaft encoder multiplier value. The Sapera event value is CORACQ_VAL_EVENT_TYPE_EXT_LINE_TRIGGER_TOO_SLOW.
• Shaft Encoder Reverse Count Overflow
Event which indicates that the shaft encoder has travelled in the opposite direction expected and that the number of pulses encountered during that travel has exceeded the acquisition device counter. The acquisition device will thus not be able to skip the appropriate number of pulses when the expected direction is detected. The Sapera event value is
CORACQ_VAL_EVENT_TYPE_SHAFT_ENCODER_REVERSE_COUNT_OVERFLOW
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 49
Transfer Events
Transfer events are the ones related to the transfer module. Transfer events provide feedback on image transfer from onboard memory frame buffers to PC memory frame buffers.
• Start of Frame
Start of Frame event generated when the first image pixel is transferred from on-board memory into PC memory.
The Sapera event value is CORXFER_VAL_EVENT_TYPE_START_OF_FRAME.
•
End of Frame
End of Frame event generated when the last image pixel is transferred from on-board memory into PC memory.
The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_FRAME.
•
End of Transfer
End of Transfer event generated at the completion of the last image transfer from on-board memory into PC memory. Issue a stop command to the transfer module to complete a transfer (if transfers are already in progress). If a frame transfer of a fixed number of images is requested, the transfer module will stop transfer automatically. The Sapera event value is CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER.
Trigger Signal Validity
The ACU ignores external trigger signal noise with its programmable debounce control. Program the debounce parameter for the minimum pulse duration considered as a valid external trigger
pulse. For more information see Note 1: General Inputs / External Trigger Inputs Specifications.
Supported Transfer Cycling Methods
The Xtium-CL MX4 supports the following transfer modes, which are either synchronous or asynchronous. Note that the Xtium does not make any use of the trash buffer. Images are accumulated in on-board memory in a FIFO type manner. When no memory is available for a new image to be stored, the image is discarded and the CORACQ_VAL_EVENT_TYPE_FRAME_LOST is generated. On-board memory can get filled up if the rate at which the images are acquired is greater than the rate at which the DMA engine can write them to host buffer memory. On-board memory can also get filled-up if there are no more empty buffers available to transfer the on-board images.
When stopping the image acquisition, the event CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER will occur once all images currently in the on-board memory are transferred to host buffer memory.
Note that if the application does not provide enough empty buffers, the Xtium event will not occur and an acquisition abort will be required.
•
CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_WITH_TRASH
Before cycling to the next buffer in the list, the transfer device will check the next buffer's state. If its state is full, the transfer will keep the image in on-board memory until the next buffer’s state changes to empty. If the on-board memory gets filled, frame lost events will be generated.
•
CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_NEXT_EMPTY_WITH_TRASH
When starting an acquisition, the buffer list is put in an empty buffer queue list in the exact order they were added to the transfer. Whenever a user sets a buffer to empty, it is added to the empty buffer queue list, so that after cycling once through the original buffer list, the buffers acquired into will follow the order in which they are put empty by the user. So in this mode, the on-board images will be transferred to host buffer memory as long as there are buffers in the empty buffer queue list. If the on-board memory gets filled, the frame lost event will start occurring.
•
CORXFER_VAL_CYCLE_MODE_ASYNCHRONOUS
The transfer device cycles through all buffers in the list without concern about the buffer state.
50 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
Output LUT Availability
The following table defines the supported output LUT (look up tables) for the Xtium-CL MX4. Note that unsupported modes are not listed.
Number of Digital
Bits
Output Pixel
Format
LUT Format Notes*
8
8
10
10
12
12
8 x 3 (RGB)
8 x 3 (RGB)
MONO 8
MONO 16
MONO 8
MONO 16
MONO 8
MONO 16
RGB888
RGB8888
8-in, 8-out
8-in, 16-out
10-in, 8-out
10-in, 16-out
12-in, 8-out
12-in, 16-out
8-in, 8-out
8-in, 8-out
8 bits in 8 LSBs of 16-bit
10 bits in 10 LSBs of 16-bit
8 MSB
12 bits in 12 LSBs of 16-bit
10 x 3 (RGB) RGB888
RGB8888
RGB101010
RGB16161616
10-in, 8-out
10-in, 8-out
10-in, 10-out
10-in, 16-out 10 bits in 10 LSBs of 16-bit
12 x 3 (RGB) RGB888
RGB8888
RGB101010
RGB16161616
12-in, 8-out
12-in, 8-out
12-in, 10-out
12-in, 16-out 12 bits in 12 LSBs of 16-bit
*When no LUTs are available or LUTs are disabled, the data is packed in the LSBs of the target destination.
Table 8: Output LUT Availability
Xtium-CL MX4 Supported Parameters
The tables below describe the Sapera capabilities supported by the Xtium-CL MX4. Unless specified, each capability applies to all configuration modes and all acquisition modes.
The information here is subject to change. The application needs to verify capabilities. New board driver releases may change product specifications.
Sapera describes the Xtium-CL MX4 family as:
• Board Server: Xtium-CL_MX4_1
• Acquisition Module: dependent on firmware used
Camera Related Capabilities
Capability
CORACQ_CAP_CONNECTOR_TYPE
CORACQ_CAP_CONNECTOR_CAMLINK
(Pin – 01, Pin – 02, Pin – 03, Pin - 04)
Values
CORACQ_VAL_CONNECTOR_TYPE_CAMLINK (0x2)
CORACQ_VAL_SIGNAL_NAME_NO_CONNECT (0x1)
CORACQ_VAL_SIGNAL_NAME_PULSE0 (0x8)
CORACQ_VAL_SIGNAL_NAME_PULSE1 (0x10)
CORACQ_VAL_SIGNAL_NAME_GND (0x4000)
Table 9: Camera Related Capabilities
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 51
Camera Related Parameters
Parameter
CORACQ_PRM_CHANNEL
CORACQ_PRM_FRAME
CORACQ_PRM_INTERFACE
CORACQ_PRM_SCAN
CORACQ_PRM_SIGNAL
CORACQ_PRM_VIDEO
CORACQ_PRM_PIXEL_DEPTH
CORACQ_PRM_VIDEO_STD
CORACQ_PRM_FIELD_ORDER
CORACQ_PRM_HACTIVE
CORACQ_PRM_HSYNC
CORACQ_PRM_VACTIVE
CORACQ_PRM_VSYNC
Values
Base/Full Mono
10T8B Mono / 8T10B Mono
Base/Medium Color RGB
Full Packed RGB
80B Packed RGB
Base/Full Bayer
10T8B Bayer
8T10B Bayer
80B Packed Bi-Color
Base/Full mono
10T8B Mono
8T10B Mono
Base/Medium Color RGB
Base/Full Bayer
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
Base/Full Mono
Base/Full Bayer
10T8B Mono
10T8B Bayer
8T10B Mono
8T10B Bayer
Base/Medium Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
CORACQ_VAL_CHANNEL_SINGLE (0x1)
CORACQ_VAL_FRAME_PROGRESSIVE (0x2)
CORACQ_VAL_INTERFACE_DIGITAL (0x2)
CORACQ_VAL_SCAN_AREA (0x1)
CORACQ_VAL_SCAN_LINE (0x2)
CORACQ_VAL_SIGNAL_DIFFERENTIAL (0x2)
CORACQ_VAL_VIDEO_MONO (0x1)
CORACQ_VAL_VIDEO_BAYER (0x10)
CORACQ_VAL_VIDEO_RGB (0x8)
CORACQ_VAL_VIDEO_BAYER (0x10)
CORACQ_VAL_VIDEO_BICOLOR (0x20)
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO8
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO16
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO8
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO16
12 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO8
12 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO16
14 bits, # LUT = 0, LUT format = CORDATA_FORMAT_MONO16
16 bits, # LUT = 0, LUT format = CORDATA_FORMAT_MONO16
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO8
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_MONO16
10 bits, # LUT = 1, LUT format = CORDATA_FORMATMONO8
10 bits, # LUT = 1, LUT format = CORDATA_FORMATMONO16
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI8
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI8
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI10
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI16
12 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI8
12 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI10
12 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI16
8 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI8
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI8
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI10
10 bits, # LUT = 1, LUT format = CORDATA_FORMAT_COLORNI16
CORACQ_VAL_VIDEO_STD_NON_STD (0x1)
CORACQ_VAL_FIELD_ORDER_NEXT_FIELD (0x4) min = 4 pixel, max = 65536 pixel, step = 1 pixel min = 4 pixel, max = 6553 pixel, step = 1 pixel min = 4 pixel, max = 4096 pixel, step = 1 pixel min = 4 pixel, max = 16384 pixel, step = 1 pixel min = 4 pixel, max = 21845 pixel, step = 1 pixel min = 4 pixel, max = 32768 pixel, step = 1 pixel min = 1 pixel max = 4294967295 pixel step = 1 pixel min = 1 line max = 16777215 line step = 1 line min = 0 line max = 4294967295 line step = 1 line
52 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
CORACQ_PRM_HFRONT_INVALID
CORACQ_PRM_HBACK_INVALID
CORACQ_PRM_VFRONT_INVALID
CORACQ_PRM_VBACK_INVALID
CORACQ_PRM_PIXEL_CLK_SRC
CORACQ_PRM_PIXEL_CLK_EXT
CORACQ_PRM_SYNC
CORACQ_PRM_HSYNC_POLARITY
CORACQ_PRM_VSYNC_POLARITY
CORACQ_PRM_TIME_INTEGRATE_METHOD
CORACQ_PRM_CAM_TRIGGER_METHOD
CORACQ_PRM_CAM_TRIGGER_POLARITY
CORACQ_PRM_CAM_TRIGGER_DURATION
CORACQ_PRM_CAM_NAME Base/Full Mono
10T8B Mono
8T10B Mono
Base/Medium Color RGB
Base/Full Bayer
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
CORACQ_PRM_LINE_INTEGRATE_METHOD
CORACQ_PRM_LINE_TRIGGER_METHOD
CORACQ_PRM_LINE_TRIGGER_POLARITY
CORACQ_PRM_LINE_TRIGGER_DELAY
CORACQ_PRM_LINE_TRIGGER_DURATION
CORACQ_PRM_TAPS
Base/Full Mono
Base/Full Bayer
10T8B Mono
10T8B Bayer
8T10B Mono
8T10B Bayer
Base/Medium Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
min = 0 pixel max = 65535 pixel step = 1 pixel min = 0 pixel max = 65535 pixel step = 1 pixel min = 0 line max = 16777215 line step = 1 line min = 0 line max = 16777215 line step = 1 line
CORACQ_VAL_PIXEL_CLK_SRC_EXT (0x2) min = 20000000 Hz max = 85000000 Hz step = 1 Hz
CORACQ_VAL_SYNC_SEP_SYNC (0x4)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_TIME_INTEGRATE_METHOD_1 (0x1)
CORACQ_VAL_TIME_INTEGRATE_METHOD_3 (0x4)
CORACQ_VAL_TIME_INTEGRATE_METHOD_5 (0x10)
CORACQ_VAL_TIME_INTEGRATE_METHOD_6 (0x20)
CORACQ_VAL_TIME_INTEGRATE_METHOD_8 (0x80)
CORACQ_VAL_CAM_TRIGGER_METHOD_1 (0x1)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 1 µs max = 85899345 µs step = 1 µs
Default Area Scan 1 tap Mono
Default Area Scan 10 taps Parallel Mono
Default Area Scan 8 taps Parallel Mono
Default Area Scan 1 tap Color
Default Bayer Area Scan 1 tap Color
Default Area Scan Full Packed RGB
Default Area Scan 80-bit Packed RGB
Default Area Scan 80-bit Packed Bi-Color
Default Bayer Area Scan 10 taps Parallel Color
Default Bayer Area Scan 8 taps Parallel Color
CORACQ_VAL_LINE_INTEGRATE_METHOD_1 (0x1)
CORACQ_VAL_LINE_INTEGRATE_METHOD_3 (0x4)
CORACQ_VAL_LINE_INTEGRATE_METHOD_4 (0x8)
CORACQ_VAL_LINE_TRIGGER_METHOD_1 (0x1)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 pixel max = 85899345 pixel step = 1 pixel min = 0 pixel max = 85899345 pixel step = 1 pixel min = 1 tap, max = 8 taps, step = 1 tap min = 10 taps, max = 10 taps, step = 1 tap min = 8 taps, max = 8 taps, step = 1 tap min = 1 tap, max = 2 taps, step = 1 tap min = 1 tap, max = 1 tap, step = 1 tap
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 53
CORACQ_PRM_TAP_OUTPUT
CORACQ_PRM_TAP_1_DIRECTION
CORACQ_PRM_TAP_2_DIRECTION
CORACQ_PRM_TAP_3_DIRECTION
CORACQ_PRM_TAP_4_DIRECTION
CORACQ_PRM_TAP_5_DIRECTION
CORACQ_PRM_TAP_6_DIRECTION
CORACQ_PRM_TAP_7_DIRECTION
CORACQ_PRM_TAP_8_DIRECTION
CORACQ_PRM_PIXEL_CLK_DETECTION
CORACQ_PRM_CHANNELS_ORDER
CORACQ_PRM_CAM_LINE_TRIGGER_FREQ_MIN
CORACQ_PRM_CAM_LINE_TRIGGER_FREQ_MAX
CORACQ_PRM_CAM_TIME_INTEGRATE_DURATION_MIN
CORACQ_PRM_CAM_TIME_INTEGRATE_DURATION_MAX
CORACQ_PRM_TIME_INTEGRATE_PULSE1_POLARITY
CORACQ_PRM_TIME_INTEGRATE_PULSE1_DELAY
CORACQ_PRM_TIME_INTEGRATE_PULSE1_DURATION
CORACQ_PRM_CAM_IO_CONTROL (*)
Base/Full Mono
Base/Full Bayer
Full Packed RGB
10T8B Mono
8T10B Mono
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
Base Medium Color RGB
Medium Color RGB
CORACQ_VAL_TAP_OUTPUT_ALTERNATE (0x1)
CORACQ_VAL_TAP_OUTPUT_SEGMENTED (0x2)
CORACQ_VAL_TAP_OUTPUT_PARALLEL (0x4)
CORACQ_VAL_TAP_OUTPUT_PARALLEL (0x4)
CORACQ_VAL_TAP_OUTPUT_SEGMENTED (0x2)
CORACQ_VAL_TAP_OUTPUT_ALTERNATE (0x1)
CORACQ_VAL_TAP_OUTPUT_SEGMENTED (0x2)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_RL (0x2)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_PRM_TIME_INTEGRATE_PULSE0_POLARITY
CORACQ_PRM_TIME_INTEGRATE_PULSE0_DELAY
CORACQ_PRM_TIME_INTEGRATE_PULSE0_DURATION
CORACQ_VAL_RISING_EDGE (0x4)
CORACQ_VAL_CHANNELS_ORDER_NORMAL (0x1)
1 Hz
16777215 Hz
1 µs
85899345 µs
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 µs max = 85899345 µs step = 1 µs min = 1 µs max = 85899345 µs step = 1 µs
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 µs max = 85899345 µs step = 1 µs min = 1 µs max = 85899345 µs step = 1 µs
54 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
CORACQ_PRM_LINE_INTEGRATE_PULSE1_POLARITY
CORACQ_PRM_LINE_INTEGRATE_PULSE1_DELAY
CORACQ_PRM_LINE_INTEGRATE_PULSE1_DURATION
CORACQ_PRM_LINE_INTEGRATE_PULSE0_POLARITY
CORACQ_PRM_LINE_INTEGRATE_PULSE0_DELAY
CORACQ_PRM_LINE_INTEGRATE_PULSE0_DURATION
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 pixel max = 85899345 pixel step = 1 pixel min = 1 pixel max = 85899345 pixel step = 1 pixel
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 pixel max = 85899345 pixel step = 1 pixel min = 1 pixel max = 85899345 pixel step = 1 pixel
CORACQ_PRM_CAMLINK_CONFIGURATION
CORACQ_PRM_DATA_VALID_ENABLE
Base Mono
Base Bayer
Full Mono
Full Bayer
10T8B Mono
10T8B Bayer
8T10B Mono
8T10B Bayer
Base Color RGB
Medium Color
RGB
Full Packed RGB
80B Packed RGB
80B Packed
Bi-Color
Base/Full Mono
Base/Medium Color
RGB
Full Packed RGB
10T8B Mono
8T10B Mono
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
CORACQ_PRM_DATA_VALID_POLARITY
CORACQ_PRM_TAP_9_DIRECTION
CORACQ_PRM_TAP_10_DIRECTION
CORACQ_PRM_TIMESLOT
CORACQ_PRM_COLOR_ALIGNMENT
CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1)
CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1)
CORACQ_VAL_CAMLINK_CONFIGURATION_MEDIUM (0x2)
CORACQ_VAL_CAMLINK_CONFIGURATION_FULL (0x4)
CORACQ_VAL_CAMLINK_CONFIGURATION_10TAPS_FORMAT2 (0x40)
CORACQ_VAL_CAMLINK_CONFIGURATION_8TAPS_10BITS (0x80)
CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1)
CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1)
CORACQ_VAL_CAMLINK_CONFIGURATION_MEDIUM (0x2)
CORACQ_VAL_CAMLINK_CONFIGURATION_FULL_PACKED (0x100)
CORACQ_VAL_CAMLINK_CONFIGURATION_FLAG_BGR (0x80000000)
CORACQ_VAL_CAMLINK_CONFIGURATION_80BITS_PACKED (0x200)
CORACQ_VAL_CAMLINK_CONFIGURATION_FLAG_BGR (0x80000000)
CORACQ_VAL_CAMLINK_CONFIGURATION_80BITS_PACKED (0x200)
TRUE
FALSE
Not available
10T8B Mono
10T8B Bayer
CORACQ_VAL_ACTIVE_HIGH (0x2)
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
10T8B Mono
10T8B Bayer
CORACQ_VAL_TAP_DIRECTION_LR (0x1)
CORACQ_VAL_TAP_DIRECTION_UD (0x4)
CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10)
CORACQ_VAL_TIMESLOT_1 (0x1)
Base/Full Bayer
10T8B Bayer
8T10B Bayer
80B Packed Bi-Color
CORACQ_PRM_CAM_CONTROL_DURING_READOUT
CORACQ_VAL_COLOR_ALIGNMENT_GB_RG (0x1)
CORACQ_VAL_COLOR_ALIGNMENT_BG_GR (0x2)
CORACQ_VAL_COLOR_ALIGNMENT_RG_GB (0x4)
CORACQ_VAL_COLOR_ALIGNMENT_GR_BG (0x8)
CORACQ_VAL_COLOR_ALIGNMENT_RGBG (0x10)
CORACQ_VAL_COLOR_ALIGNMENT_BGRG (0x20)
TRUE
FALSE
Table 10: Camera Related Parameters
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 55
VIC Related Parameters
Parameter
CORACQ_PRM_CAMSEL
CORACQ_PRM_CROP_LEFT
CORACQ_PRM_CROP_TOP
CORACQ_PRM_CROP_WIDTH
CORACQ_PRM_CROP_HEIGHT
CORACQ_PRM_DECIMATE_METHOD
CORACQ_PRM_LUT_ENABLE
CORACQ_PRM_LUT_NUMBER
CORACQ_PRM_STROBE_ENABLE
CORACQ_PRM_STROBE_METHOD
CORACQ_PRM_STROBE_POLARITY
CORACQ_PRM_STROBE_DURATION
CORACQ_PRM_STROBE_DELAY
CORACQ_PRM_TIME_INTEGRATE_ENABLE
Base/Full Mono
10T8B Mono
8T10B Mono
Full Packed RGB
Base/Full Bayer
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
Base/Medium Color RGB
80B Packed RGB
Base/Full Mono
10T8B Mono
Base/Full Bayer
10T8B Bayer
8T10B Mono
8T10B Bayer
Base/Medium Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Base/Full Mono
10T8B Mono
Base/Full Bayer
10T8B Bayer
8T10B Mono
8T10B Bayer
Base/Medium Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Values
CAMSEL_MONO = from 0 to 0
CAMSEL_RGB = from 0 to 0 min = 0 pixel, max = 65512 pixel, step = 2 pixel min = 0 pixel, max = 65506 pixel, step = 4 pixel min = 0 pixel, max = 65512 pixel, step = 1 pixel min = 0 pixel, max = 65512 pixel, step = 1 pixel min = 0 pixel, max = 32744 pixel, step = 2 pixel min = 0 pixel, max = 32744 pixel, step = 4 pixel min = 0 pixel, max = 16380 pixel, step = 1 pixel min = 0 pixel, max = 16380 pixel, step = 1 pixel min = 0 pixel, max = 32764 pixel, step = 1 pixel min = 0 line max = 16777215 line step = 1 line min = 24 pixel, max = 65536 pixel, step = =2 pixel min = 24 pixel, max = 65530 pixel, step = =4 pixel min = 24 pixel, max = 65536 pixel, step = 1 pixel min = 24 pixel, max = 65536 pixel, step = 1 pixel min = 24 pixel, max = 32768 pixel, step = 2 pixel min = 24 pixel, max = 32768 pixel, step = 1 pixel min = 4 pixel, max = 16384 pixel, step = 1 pixel min = 4 pixel, max = 16384 pixel, step = 1 pixel min = 4 pixel, max = 32768 pixel, step = 1 pixel min = 1 line max = 16777215 line step = 1 line
CORACQ_VAL_DECIMATE_DISABLE (0x1)
TRUE
FALSE
Default = 0
TRUE
FALSE
CORACQ_VAL_STROBE_METHOD_1 (0x1)
CORACQ_VAL_STROBE_METHOD_3 (0x4)
CORACQ_VAL_STROBE_METHOD_4 (0x8)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2) min = 1 µs max = 85899345 µs step = 1 µs min = 0 µs max = 85899345 µs step = 1 µs
TRUE
FALSE
56 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
CORACQ_PRM_TIME_INTEGRATE_DURATION
CORACQ_PRM_CAM_TRIGGER_ENABLE
CORACQ_PRM_OUTPUT_FORMAT
CORACQ_PRM_EXT_TRIGGER_ENABLE
CORACQ_PRM_VIC_NAME
CORACQ_PRM_LUT_MAX
CORACQ_PRM_EXT_TRIGGER_DETECTION
Base/Full Mono
10T8B Mono
8T10B Mono
Base/Medium Color RGB
Base/Full Bayer
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
CORACQ_PRM_LUT_FORMAT
CORACQ_PRM_VSYNC_REF
CORACQ_PRM_HSYNC_REF
CORACQ_PRM_LINE_INTEGRATE_ENABLE
Base/Full mono/10T8B
8T10B
Base/Medium Color RGB
Base/Full Bayer
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
CORACQ_PRM_LINE_INTEGRATE_DURATION
CORACQ_PRM_LINE_TRIGGER_ENABLE
Base/Full Mono
10T8B / 8T10B
Base/Medium Color RGB
Base/Full Bayer
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
CORACQ_PRM_EXT_FRAME_TRIGGER_ENABLE min = 1 µs max = 85899345 µs step = 1 µs
TRUE
FALSE
CORACQ_VAL_OUTPUT_FORMAT_MONO8
CORACQ_VAL_OUTPUT_FORMAT_MONO16
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_RGB101010
CORACQ_VAL_OUTPUT_FORMAT_RGB16161616
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_RGB101010
CORACQ_VAL_OUTPUT_FORMAT_RGB16161616
CORACQ_VAL_OUTPUT_FORMAT_MONO8
CORACQ_VAL_OUTPUT_FORMAT_MONO16
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_BICOLOR88
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_MONO8
CORACQ_VAL_OUTPUT_FORMAT_RGB8888
CORACQ_VAL_OUTPUT_FORMAT_RGB888
CORACQ_VAL_OUTPUT_FORMAT_RGB101010
CORACQ_VAL_OUTPUT_FORMAT_RGB16161616
CORACQ_VAL_OUTPUT_FORMAT_MONO16
CORACQ_VAL_EXT_TRIGGER_OFF (0x1)
CORACQ_VAL_EXT_TRIGGER_ON (0x8)
Default Area Scan 1 tap Mono
Default Area Scan 10 taps Parallel Mono
Default Area Scan 8 taps Parallel Mono
Default Area Scan 1 tap Color
Default Bayer Area Scan 1 tap Color
Default Area Scan Full Packed RGB
Default Area Scan 80-bit Packed RGB
Default Area Scan 80-bit Packed Bi-Color
Default Bayer Area Scan 10 taps Parallel Color
Default Bayer Area Scan 8 taps Parallel Color
1
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2)
CORACQ_VAL_RISING_EDGE (0x4)
CORACQ_VAL_FALLING_EDGE (0x8)
Default = CORDATA_FORMAT_MONO8
Default = CORDATA_FORMAT_MONO16
Default = CORDATA_FORMAT_COLORNI8
Default = CORDATA_FORMAT_COLORNI8
Default = CORDATA_FORMAT_COLORNI8
Default = CORDATA_FORMAT_COLORNI8
Default = CORDATA_FORMAT_COLORNI10
CORACQ_VAL_SYNC_REF_END (0x2)
CORACQ_VAL_SYNC_REF_END (0x2)
TRUE
FALSE min = 1 pixel max = 85899345 pixel step = 1 pixel
TRUE
FALSE
TRUE
FALSE
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 57
CORACQ_PRM_EXT_FRAME_TRIGGER_DETECTION
CORACQ_PRM_EXT_LINE_TRIGGER_ENABLE
CORACQ_PRM_EXT_LINE_TRIGGER_DETECTION
CORACQ_PRM_SNAP_COUNT
CORACQ_PRM_INT_LINE_TRIGGER_ENABLE
CORACQ_PRM_INT_LINE_TRIGGER_FREQ
CORACQ_PRM_BIT_ORDERING
CORACQ_PRM_EXT_TRIGGER_LEVEL
CORACQ_PRM_STROBE_LEVEL
CORACQ_PRM_EXT_FRAME_TRIGGER_LEVEL
CORACQ_PRM_EXT_LINE_TRIGGER_LEVEL
CORACQ_PRM_INT_LINE_TRIGGER_FREQ_MIN
CORACQ_PRM_INT_LINE_TRIGGER_FREQ_MAX
CORACQ_PRM_MASTER_MODE
CORACQ_PRM_SHAFT_ENCODER_DROP
CORACQ_PRM_SHAFT_ENCODER_ENABLE
CORACQ_PRM_EXT_TRIGGER_FRAME_COUNT
CORACQ_PRM_INT_FRAME_TRIGGER_ENABLE
CORACQ_PRM_INT_FRAME_TRIGGER_FREQ
CORACQ_PRM_FRAME_LENGTH
CORACQ_PRM_FLIP
CORACQ_PRM_EXT_TRIGGER_DURATION
CORACQ_PRM_TIME_INTEGRATE_DELAY
CORACQ_PRM_CAM_RESET_DELAY
CORACQ_PRM_CAM_TRIGGER_DELAY
CORACQ_PRM_SHAFT_ENCODER_LEVEL
CORACQ_PRM_LUT_NENTRIES 8-bit/pixel component
10-bit/pixel component
12-bit/pixel component
14/16-bit/pixel component
CORACQ_PRM_EXT_FRAME_TRIGGER_SOURCE (*)
CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE (*)
CORACQ_VAL_ACTIVE_LOW (0x1)
CORACQ_VAL_ACTIVE_HIGH (0x2)
CORACQ_VAL_RISING_EDGE (0x4)
CORACQ_VAL_FALLING_EDGE (0x8)
CORACQ_VAL_DOUBLE_PULSE_RISING_EDGE (0x20)
CORACQ_VAL_DOUBLE_PULSE_FALLING_EDGE (0x40)
TRUE
FALSE
CORACQ_VAL_RISING_EDGE (0x4)
CORACQ_VAL_FALLING_EDGE (0x8)
Not available
TRUE
FALSE
Default = 5000 Hz
CORACQ_VAL_BIT_ORDERING_STD (0x1)
CORACQ_VAL_LEVEL_TTL (0x1)
CORACQ_VAL_LEVEL_12VOLTS (0x040)
CORACQ_VAL_LEVEL_24VOLTS (0x8)
CORACQ_VAL_LEVEL_TTL (0x1)
CORACQ_VAL_LEVEL_TTL (0x1)
CORACQ_VAL_LEVEL_12VOLTS (0x040)
CORACQ_VAL_LEVEL_24VOLTS (0x8)
CORACQ_VAL_LEVEL_422 (0x2)
8 Hz
500000 Hz
Not available min = 0 tick max = 254 tick step = 1 tick
TRUE
FALSE min = 1 frame max = 262142 frame step = 1 frame
Note: Infinite not supported
TRUE
FALSE min = 1 milli-Hz max = 1000000000 milli-Hz step = 1 milli-Hz
CORACQ_VAL_FRAME_LENGTH_FIX (0x1)
CORACQ_VAL_FRAME_LENGTH_VARIABLE (0x2)
CORACQ_VAL_FLIP_OFF (0x00)
CORACQ_VAL_FLIP_HORZ (0x01) min = 0 µs max = 255 µs step = 1 µs min = 0 µs max = 85899345 µs step = 1 µs min = 0 µs max = 0 µs step = 1 µs min = 0 µs max = 85899345 µs step = 1 µs
CORACQ_VAL_LEVEL_422 (0x2)
256 entries
1024 entries
4096 entries
0 entries min = 0 max = 5 step = 1 min = 0 max = 5 step = 1
58 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
CORACQ_PRM_EXT_TRIGGER_SOURCE (*)
CORACQ_PRM_SHAFT_ENCODER_MULTIPLY
CORACQ_PRM_EXT_TRIGGER_DELAY
CORACQ_PRM_EXT_TRIGGER_DELAY_TIME_BASE
CORACQ_PRM_COLOR_DECODER_ENABLE
CORACQ_PRM_COLOR_DECODER_METHOD
CORACQ_PRM_WB_GAIN
CORACQ_PRM_WB_GAIN_RED
Base/Full Mono
10T8B/8T10B
Base/Medium Color
RGB
Full Packed RGB
80B Packed RGB
Base/Full Bayer
10T8B Bayer
8T10B Bayer
80B Packed
Bi-Color
Full Bayer
10T8B Bayer
8T10B Bayer
80B Packed
Bi-Color
Base/Full Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Base/Full Bayer
10T8B Bayer
8T10B Bayer
Base/Full Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Base/Full Bayer
10T8B Bayer
8T10B Bayer
CORACQ_PRM_WB_GAIN_GREEN
CORACQ_PRM_WB_GAIN_BLUE
Base/Full Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Base/Full Bayer
10T8B Bayer
8T10B Bayer
Base/Full Color RGB
Full Packed RGB
80B Packed RGB
80B Packed Bi-Color
Base/Full Bayer
10T8B Bayer
8T10B Bayer
CORACQ_PRM_EXT_TRIGGER_IGNORE_DELAY
CORACQ_PRM_BOARD_SYNC_OUTPUT1_SOURCE (*)
CORACQ_PRM_BOARD_SYNC_OUTPUT2_SOURCE (*)
CORACQ_PRM_EXT_TRIGGER_SOURCE_STR min = 0 max = 5 step = 1 min = 1 max = 32 step = (2
N
) min = 0 max = 16777215 step = 1
CORACQ_VAL_TIME_BASE_LINE_VALID (0x4)
CORACQ_VAL_TIME_BASE_LINE_TRIGGER (0x8)
CORACQ_VAL_TIME_BASE_SHAFT_ENCODER (0x40)
CORACQ_VAL_TIME_BASE_NS (0x80)
Not available
TRUE
FALSE
CORACQ_VAL_COLOR_DECODER_METHOD_1 (0x1)
CORACQ_VAL_COLOR_DECODER_METHOD_7 (0x40)
Min = 100000, max = 900000, step = 1
Min = 100000, max = 900000, step = 1
Min = 100000, max = 900000, step = 1
Min = 100000, max = 900000, step = 1
Not available min = 0 max = 6 step = 1 min = 0 max = 6 step = 1
[0] = Automatic
[1] = External Trigger #1
[2] = External Trigger #2
[3] = Board Sync #1
[4] = Board Sync #2
[5] = Software Trigger
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 59
CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE_STR
CORACQ_PRM_VERTICAL_TIMEOUT_DELAY
CORACQ_PRM_POCL_ENABLE
CORACQ_PRM_SHAFT_ENCODER_DIRECTION
CORACQ_PRM_LINE_TRIGGER_AUTO_DELAY
CORACQ_PRM_TIME_STAMP_BASE
CORACQ_PRM_BOARD_SYNC_OUTPUT1_SOURCE_STR
CORACQ_PRM_BOARD_SYNC_OUTPUT2_SOURCE_STR
CORACQ_PRM_SHAFT_ENCODER_ORDER
CORACQ_PRM_CAM_FRAMES_PER_TRIGGER
CORACQ_PRM_LINE_INTEGRATE_TIME_BASE
[0] = Automatic
[1] = Shaft Encoder Phase A
[2] = Shaft Encoder Phase B
[3] = Shaft Encoder Phase A & B
[4] = Board Sync #1
[5] = Board Sync #2
Not available
TRUE
FALSE
CORACQ_VAL_SHAFT_ENCODER_DIRECTION_IGNORE (0x00)
CORACQ_VAL_SHAFT_ENCODER_DIRECTION_FORWARD (0x01)
CORACQ_VAL_SHAFT_ENCODER_DIRECTION_REVERSE (0x02)
Not Available
CORACQ_VAL_TIME_BASE_US (0x1)
CORACQ_VAL_TIME_BASE_LINE_VALID (0X4)
CORACQ_VAL_TIME_BASE_LINE_TRIGGER (0X8)
CORACQ_VAL_TIME_BASE_SHAFT_ENCODER (0X40)
CORACQ_VAL_TIME_BASE_100NS (0x200)
[0] = Disabled
[1] = External Frame Trigger
[2] = Reserved
[3] = CC1
[4] = CC2
[5] = CC3
[6] = CC4
[0] = Disabled
[1] = External Frame Trigger
[2] = Reserved
[3] = CC1
[4] = CC2
[5] = CC3
[6] = CC4
CORACQ_VAL_SHAFT_ENCODER_ORDER_AUTO (0X0)
CORACQ_VAL_SHAFT_ENCODER_ORDER_DROP_MULTIPLY (0X1)
CORACQ_VAL_SHAFT_ENCODER_ORDER_MULTIPLY_DROP (0X2)
Not available
CORACQ_VAL_TIME_BASE_PIXEL_CLK (0X100)
Table 11: VIC Related Parameters
60 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
ACQ Related Parameters
Parameter Values
CORACQ_PRM_LABEL
CORACQ_PRM_EVENT_TYPE
CORACQ_PRM_EVENT_TYPE_EX
CORACQ_PRM_SIGNAL_STATUS
CORACQ_PRM_FLAT_FIELD_ENABLE
CORACQ_PRM_TIME_STAMP
CORACQ_CAP_SERIAL_PORT_INDEX
Base Mono
Base Color RGB
Base Bayer
Full mono
Medium Color RGB
Full Packed RGB
Full Bayer
8T10B
10T8B
80B Packed RGB
80B Packed Bi-Color
10T8B Bayer
8T10B Bayer
Camera Link Base Mono
Camera Link Base Color RGB
Camera Link Base Bayer
Camera Link Full Mono
Camera Link Medium Color RGB
Camera Link Full Packed RGB
Camera Link Full Bayer
Camera Link 8-Tap/10-Bit Mono
Camera Link 10-Tap/8-Bit Mono
Camera Link 80-Bit Packed/8-Bit RGB
Camera Link 80-Bit Packed/8-Bit Bi-Color
Camera Link 10-Tap/8-Bit Bayer
Camera Link 8-Tap/10-Bit Bayer
CORACQ_VAL_EVENT_TYPE_START_OF_FRAME
CORACQ_VAL_EVENT_TYPE_END_OF_FRAME
CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER
CORACQ_VAL_EVENT_TYPE_VERTICAL_SYNC
CORACQ_VAL_EVENT_TYPE_NO_PIXEL_CLK
CORACQ_VAL_EVENT_TYPE_PIXEL_CLK
CORACQ_VAL_EVENT_TYPE_FRAME_LOST
CORACQ_VAL_EVENT_TYPE_DATA_OVERFLOW
CORACQ_VAL_EVENT_TYPE_EXTERNAL_TRIGGER_IGNORED
CORACQ_VAL_EVENT_TYPE_EXT_LINE_TRIGGER_TOO_SLOW
CORACQ_VAL_EVENT_TYPE_SHAFT_ENCODER_REVERSE_COUNT_OVERFLOW
CORACQ_VAL_SIGNAL_HSYNC_PRESENT
CORACQ_VAL_SIGNAL_VSYNC_PRESENT
CORACQ_VAL_SIGNAL_PIXEL_CLK_1_PRESENT
CORACQ_VAL_SIGNAL_PIXEL_CLK_2_PRESENT
CORACQ_VAL_SIGNAL_PIXEL_CLK_3_PRESENT
CORACQ_VAL_SIGNAL_PIXEL_CLK_ALL_PRESENT
CORACQ_VAL_SIGNAL_POWER_PRESENT
CORACQ_VAL_SIGNAL_POCL_ACTIVE
CORACQ_VAL_SIGNAL_POCL_ACTIVE_2
Not Available
Available
Supported
Table 12: Acquisition Related Parameters
Transfer Related Capabilities
Capability Values
CORXFER_CAP_NB_INT_BUFFERS
CORXFER_CAP_MAX_XFER_SIZE
CORXFER_CAP_MAX_FRAME_COUNT
CORXFER_CAP_COUNTER_STAMP_AVAILABLE
CORXFER_VAL_NB_INT_BUFFERS_AUTO (0x2)
4294967040 Bytes
16777215 Frames
FALSE
Table 13: Transfer Related Capabilities
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 61
Transfer Related Parameters
Parameter Values
CORXFER_PRM_EVENT_TYPE
CORXFER_PRM_EVENT_TYPE_EX
CORXFER_PRM_START_MODE
CORXFER_PRM_CYCLE_MODE
CORXFER_PRM_FLIP
CORXFER_PRM_INT_BUFFERS
CORXFER_PRM_EVENT_COUNT_SOURCE
CORXFER_PRM_BUFFER_TIMESTAMP_MODULE
CORXFER_PRM_BUFFER_TIMESTAMP_EVENT
CORXFER_PRM_LINE_MERGING
CORXFER_VAL_EVENT_TYPE_START_OF_FRAME
CORXFER_VAL_EVENT_TYPE_END_OF_FRAME
CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER
CORXFER_VAL_START_MODE_ASYNCHRONOUS (0x0)
CORXFER_VAL_START_MODE_SYNCHRONOUS (0x1)
CORXFER_VAL_START_MODE_HALF_ASYNCHRONOUS (0x2)
CORXFER_VAL_START_MODE_SEQUENTIAL (0x3)
CORXFER_VAL_CYCLE_MODE_ASYNCHRONOUS (0x0)
CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_WITH_TRASH (0x2)
CORXFER_VAL_CYCLE_MODE_OFF (0x3)
CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_NEXT_EMPTY_WITH_TRASH (0x5)
CORXFER_VAL_FLIP_OFF (0x0)
CORXFER_VAL_FLIP_VERT (0x2)
* Depends on acquired image size.
By default driver will optimize the number of on-board buffers.
CORXFER_VAL_EVENT_COUNT_SOURCE_DST (0x1)
CORXFER_VAL_EVENT_COUNT_SOURCE_SRC (0x2)
CORXFER_VAL_BUFFER_TIMESTAMP_MODULE_XFER (0x13)
CORXFER_VAL_EVENT_TYPE_END_OF_FRAME
CORXFER_VAL_LINE_MERGING_AUTO (0x0)
CORXFER_VAL_LINE_MERGING_OFF (0x2)
Table 14: Transfer Related Parameters
General Outputs #1: Related Capabilities (for GIO Module #0)
Outputs available on connector J1 and J4.
Capability Values
CORGIO_CAP_IO_COUNT
CORGIO_CAP_DIR_OUTPUT
CORGIO_CAP_DIR_TRISTATE
CORGIO_CAP_EVENT_TYPE
CORGIO_CAP_READ_ONLY
4 I/Os
0xf
0xf
Not Available
0x03 (* depends on strobe outputs reserved for acquisition device)
Table 15: GIO-0 Related Capabilities
62 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
General Outputs #1: Related Parameters (for GIO Module #0)
Parameter Values
CORGIO_PRM_LABEL
CORGIO_PRM_DEVICE_ID
CORGIO_PRM_OUTPUT_TYPE
CORGIO_PRM_CONNECTOR
General Outputs #1
0
CORGIO_VAL_OUTPUT_TYPE_TTL (0x10)
CORGIO_VAL_CONNECTOR_1 (0x1)
Table 16: GIO-0 Related Parameters
General Inputs #1: Related Capabilities (for GIO Module #1)
Inputs available on connector J1 and J4.
Capability
CORGIO_CAP_IO_COUNT
CORGIO_CAP_DIR_OUTPUT
CORGIO_CAP_DIR_TRISTATE
CORGIO_CAP_EVENT_TYPE
CORGIO_CAP_READ_ONLY
Values
4 I/Os
0x0
0x0
CORGIO_VAL_EVENT_TYPE_RISING_EDGE (0x1)
CORGIO_VAL_EVENT_TYPE_FALLING_EDGE (0x2)
0x03 (* depends on external trigger inputs reserved for acquisition device)
Table 17: GIO-1 Related Capabilities
General Inputs #1: Related Parameters (for GIO Module #1)
Parameter Values
CORGIO_PRM_LABEL
CORGIO_PRM_DEVICE_ID
CORGIO_PRM_INPUT_LEVEL
CORGIO_PRM_CONNECTOR
General Inputs #1
1
CORGIO_VAL_INPUT_LEVEL_TTL (0x1)
CORGIO_VAL_INPUT_LEVEL_24VOLTS (0x8)
CORGIO_VAL_INPUT_LEVEL_12VOLTS (0x40)
CORGIO_VAL_CONNECTOR_1 (0x1)
Table 18: GIO-1 Related Parameters
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 63
Bidirectional General I/Os: Related Capabilities (for GIO Module
#2)
These I/Os are available on connector J5
Capability
CORGIO_CAP_IO_COUNT
CORGIO_CAP_DIR_OUTPUT
CORGIO_CAP_DIR_TRISTATE
CORGIO_CAP_EVENT_TYPE
CORGIO_CAP_READ_ONLY
Values
8 I/Os
0xff
0xff
Not Available
0x03 (* depends on board syncs reserved for acquisition device)
Table 19: GIO-2 Related Capabilities
Bidirectional General I/Os: Related Parameters (for GIO Module
#2)
Parameter Values
CORGIO_PRM_LABEL
CORGIO_PRM_DEVICE_ID
CORGIO_PRM_OUTPUT_TYPE
CORGIO_PRM_INPUT_LEVEL
CORGIO_PRM_CONNECTOR
Bidirectional General I/Os #1
2
CORGIO_VAL_OUTPUT_TYPE_LVTTL (0x20)
CORGIO_VAL_INPUT_LEVEL_LVTTL (0x20)
CORGIO_VAL_CONNECTOR_2 (0x2)
Table 20: GIO-2 Related Parameters
64 • Xtium-CL MX4 Reference
Xtium-CL MX4 User's Manual
Windows Embedded 7 Installation
Windows Embedded 7 is not officially supported by Teledyne DALSA due to the number of possible configurations. However, Sapera LT and other Teledyne DALSA products should function properly on the Windows Embedded 7 platform provided that the required components are installed.
Teledyne DALSA provides answer files (.xml) for use during Windows Embedded 7 installation that install all necessary components for running Sapera LT 32-bit or 64-bit versions (SDK or Runtime),
Sapera Processing 32-bit or 64-bit versions (SDK or Runtime), and Teledyne DALSA frame grabbers.
For each platform (32 or 64-bit), the answer file provided is:

SaperaFrameGrabbers.xml:
Configuration for Sapera LT, Sapera Processing and Teledyne DALSA framegrabbers
The file is located in the following directory dependent on the platform used:
<Install Directory>\Sapera\Install\Win7_Embedded\Win32
<Install Directory>\Sapera\Install\Win7_Embedded\Win64
The OS footprint for these configurations is less than 1 GB. Alternatively, the Windows Thin Client configuration template provided by Microsoft in the Windows Embedded 7 installation also provides the necessary dependencies for Sapera LT, and Teledyne DALSA framegrabbers (with an OS footprint of approximately 1.5 GB).
If you are installing other applications on the Windows Embedded 7 platform, it is recommended that you verify which components are required, and if necessary, create a corresponding “Answer
File”.
For more information on performing dependency analysis to enable your application on Windows
Embedded 7, refer to the Microsoft Windows Embedded 7 documentation.
Xtium-CL MX4 User's Manual
Xtium-CL MX4 Reference • 65
Sapera Servers & Resources
Servers and Resources
The following table describes the Xtium-CL MX4 board
Servers Resources
Name
Xtium-
CL_MX4_1
(Full firmware)
Xtium-
CL_MX4_1
(Dual firmware)
Xtium-
CL_MX4_1
(80-bit firmware)
All
Type Name Index Description
Acquisition
GIO
Camera Link Full Mono
Camera Link Medium
Color RGB
Camera Link Full Packed
RGB
Camera Link Full Bayer
Acquisition Camera Link Base Mono
#1
Camera Link Base Mono
#2
Camera Link Base Color
RGB #1
Camera Link Base Color
RGB #2
Camera Link Base Bayer
#1
Camera Link Base Bayer
#2
Acquisition CameraLink 10-Tap/8-Bit
Mono
CameraLink 8-Tap/10-Bit
Mono
CameraLink 80-Bit
Packed/8-Bit RGB
CameraLink 80-Bit
Packed/8-Bit Bi-Color
Camera Link 10-Tap/8-
Bit Bayer
Camera Link 8-Tap/10-
Bit Bayer
General Outputs #1
General Inputs #1
Bidirectional General
I/Os
0
1
2
3
0
1
2
3
4
5
5
2
3
4
0
1
0
1
2
Base, Medium and Full configuration,
Monochrome Camera
Base and Medium configuration,
RGB Camera
Full packed 8-bit RGB Camera
Base, Medium and Full configuration,
Bayer Camera
Base Monochrome Camera #1
Base Monochrome Camera #2
Base RGB Camera #1
Base RGB Camera #2
Base Bayer Camera #1
Base Bayer Camera #2
80-bit configuration, Monochrome
10 Taps @ 8 bits Camera
80-bit configuration, Monochrome
8 Taps @ 10 bits Camera
80-bit configuration, RGB
80-bit packed 8-bit Camera
80-bit configuration, Bi-Color
80-bit packed 8-bit Camera
80-bit configuration, Bayer
10 Taps @ 8 bits Camera
80-bit configuration, Bayer
8 Taps @ 10 bits Camera
4 General Outputs
4 General Inputs
8 Bidirectional General I/Os
Table 21: Xtium-CL MX4 - Servers and Resources
Xtium-CL MX4 User's Manual
Sapera Servers & Resources • 66
Technical Specifications
Xtium-CL MX4 Board Specifications
Digital Video Input & Controls
Input Type
Common Pixel Formats Camera Link tap configuration:
8, 10, 12, 14 and 16-bit mono
8, 10, 12-bit RGB
8, 10, 12-bit Bayer
8-bit Bi-Color
Tap Format Details
Camera Link Specifications Rev 2.0 compliant;
2 Base or 1 Full or 1 Medium or 1 80-bit
(using SDR-26 Camera Link connectors — MiniCL)
Supports PoCL cameras in:
Camera Link Base, Medium, Full/80-Bit Configurations
1 Tap – 8/10/12/14/16-bit mono
2 Taps – 8/10/12-bit mono
3 Taps – 8/10/12-bit mono
4 Taps – 8/10/12-bit mono
8 Taps – 8-bit mono
8 Taps – 10-bit mono
10 Taps – 8-bit mono
1 Tap – 8/10/12-bit RGB
2 Taps – 8-bit RGB
Full packed 8-bit RGB/BGR
80-bit packed 8-bit RGB/BGR
Scanning
Scanning Directions
Resolution
note: these are Xtium-CL
MX4 maximums, not
Camera Link
specifications
Pixel Clock Range
80-bit packed 8-bit Bi-Color
Area scan and Line scan: Progressive, Segmented, Multi-Tap, Tap reversal,
Alternate Tap Configuration
Left to Right, Right to Left, Up-Down,
From Top
Horizontal Minimum:
8 Pixels per tap (8-bits/pixel)
Horizontal Maximum:
8-bits/pixel x 64k Pixels/line
16-bits/pixel x 32k Pixels/line
32-bits/pixel x 16k Pixels/line
64-bits/pixel x 8k Pixels/line
Vertical Minimum:
1 line
Vertical Maximum: up to 16,000,000 lines—for area scan sensors infinite line count—for linescan sensors
20 MHz to 85 MHz
Synchronization
Minimums
Image Buffer
Bandwidth to Host
System
Serial Port
Horizontal Sync minimum: 1 pixel
Vertical Sync minimum: 1 line
Available with 512 MB
Approximately 1.7GB/s (maximum obtained is dependent on firmware loaded and PC characteristics)
Supports communication speeds from 9600 to 921600 bps
Xtium-CL MX4 User's Manual
Technical Specifications • 67
Controls
Processing
Dependant on user loaded firmware
configuration
Compliant with Teledyne DALSA Trigger-to-Image Reliability framework
Comprehensive event notifications
Timing control logic for camera triggers and strobe signals
External trigger latency less than 100 nsec
Supports multi-board / multi-camera synchronization
Quadrature (phase A & B) shaft encoder inputs for external web synchronization: RS-422 input maximum frequency is 5 MHz
4 opto-coupled general inputs (TTL/12V/24V).
Can be used as opto-coupled external trigger inputs programmable as active high or low (edge or level trigger).
1 input can be connected to a differential input signal.
4 TTL general outputs. Can be used as Strobe outputs.
I/O available on a DH60-27P connector (J1) and on 26-pin SHF-113-01-L-D-RA (J4)
Output Lookup Table
Bayer Mosaic Filter
Bi-Color Conversion (for TDALSA P4)
Table 22: Board Specifications
Host System Requirements
Xtium-CL MX4 Dimensions
Approximately 4 in. (10 cm) wide by 4 in. (10 cm) high
General System Requirements for the Xtium-CL MX4
•
PCI Express Gen2 x4 slot compatible;
(will work in Gen1 x4 slot with reduced bandwidth to host)
•
On some computers the Xtium-CL MX4 may function installed in a x16 slot. The computer documentation or direct testing by the user is required.
•
Xtium-CL MX4 operates correctly when installed in a multi-processor system (including
Hyper-Threading multi-core processors).
Operating System Support
Windows XP, Windows 7 and Windows 8, each in either 32-bit or 64-bit
68 • Technical Specifications
Xtium-CL MX4 User's Manual
Environment
Ambient Temperature:
Relative Humidity:
MTBF @40°C
10° to 50°C (operation)
-40° to 75°C (storage)
5% to 90% non-condensing (operating)
0% to 95% (storage)
36.4 years
Table 23: Environment Specifications
Note: Ensure adequate airflow for proper functioning of the board across the entire temperature range of 10 – 50°C . Airflow measuring 80 LFM (linear feet per minute) across the surface of the board is recommended.
Power Requirements during Acquisitions
+3.3V:
+12V:
0.9A
0.54A
Table 24: Power Specifications
Xtium-CL MX4 User's Manual
Technical Specifications • 69
EMI Certifications
70 • Technical Specifications
Figure 20: EMI Certifications
Xtium-CL MX4 User's Manual
Connector and Switch Locations
Xtium-CL MX4 Board Layout Drawing
Figure 21: Board Layout
Connector / LED Description List
The following table lists components on the Xtium-CL MX4 board. Detailed information concerning the connectors/LEDs follows this summary table.
Location Description Location Description
External Signals connector
DH60-27P
Camera Link 2 Connector
Multi Board Sync
P2
Camera Link 1 Connector
PCIe x4 computer bus connector
(Gen2 compliant slot preferred)
PC power to camera interface and/or J1
Boot-up/PCIe Status LED
(refer to text)
Camera status LEDs
Internal I/O Signals connector
(26-pin SHF-113-01-L-D-RA)
J6, P1
Table 25: Board Connector List
Reserved
Xtium-CL MX4 User's Manual
Technical Specifications • 71
Connector and Switch Specifications
Xtium-CL MX4 End Bracket Detail
Xtium-CL MX4
Board
Status
LED
I/O – DH60-27P female connector
Camera Link 2
LED/connector
Camera Link 1
LED/connector
Figure 22: End Bracket Details
The hardware installation process is completed with the connection of a supported camera to the
Xtium-CL MX4 board using Camera Link cables (see Camera Link Cables).
• The Xtium-CL MX4 board supports a camera with one or two Camera Link connectors (one
Base, one Medium or one Full – see Data Port Summary for information on Camera Link
configurations).
• Connect the camera to the J3 connector with a Camera Link cable. When using a Medium or
Full camera, connect the second camera connector to J2.
Note: If the camera is powered by the Xtium-CL MX4, refer to J7: Power Connector for power
connections.
Contact Teledyne DALSA or browse our web site www.teledynedalsa.com/mv for information on
Xtium-CL MX4 supported cameras.
72 • Technical Specifications
Xtium-CL MX4 User's Manual
Status LED Functional Description
D1 Boot-up/PCIe status LED
Color State Description
Red
Green
Green
Y e l l l l l l o w
Y e l l l l l l o w
Blue
Blue
Red
Solid
Solid
Flashing
Solid
Flashing
Solid
Flashing
Flashing
FPGA firmware not loaded
Normal FPGA firmware loaded, Gen2 speed, link width x4
Normal FPGA firmware loaded, Gen1 speed, link width x4
Normal FPGA firmware loaded, Gen2 speed, link width not x4
Normal FPGA firmware loaded, Gen1 speed, link width not x4
Safe FPGA firmware loaded, Gen2 speed
Safe FPGA firmware loaded, Gen1 speed
PCIe Training Issue – Board will not be detected by computer
Table 26: D1 Boot-up/PCIe Status LED
Camera Link LEDs
(D4 = Camera Link connector #1, D3 = Camera Link connector #2)
Color
Red
Green
Green
State
Solid
Solid
Slow Flashing
~1 Hz
Description
No Camera Link pixel clock detected
Camera Link pixel clock detected. No line valid detected.
Note: for D3, when configuring for Full CameraLink, both pixel clock on the 2 nd
cable must be detected.
Camera Link pixel clock and line valid signal detected
Note: for D3, when configuring for Full CameraLink, both line valid on the
2 nd
cable must be detected.
Acquisition in progress
Green
Fast Flashing
~8 Hz
Table 27: Camera Link LED Status

Notes 1: When using a Full configuration, if the input on CL1 is configured as Camera Link
Base, the D3 (for CL2) will remain RED at all times.

Note 2: LED D3 and D4 are independent.

Note 3: Full FPGA defaults to Camera Link Medium configuration.

Note 4: For a Pixel Clock and Line Valid to be detected, the following rules apply:
•
CL1: Requires 1 clock and 1 LVAL
•
CL2: Camera Link Base configuration: N/A
• CL2: Camera Link Medium configuration requires 1 clock and one LVAL
•
CL2: Camera Link Full/80-bit configurations requires 2 clocks and 2 LVAL
Xtium-CL MX4 User's Manual
Technical Specifications • 73
J3: Camera Link Connector 1
Name
BASE_X0-
BASE_X0+
BASE_X1-
BASE_X1+
BASE_X2-
BASE_X2+
BASE_X3-
BASE_X3+
BASE_XCLK-
BASE_XCLK+
SERTC+
SERTC-
SERTFG-
SERTFG+
CC1-
CC1+
CC2+
CC2-
CC3-
CC3+
CC4+
CC4-
PoCL
GND
Pin #
21
8
22
9
20
7
19
25
12
24
11
23
10
6
18
5
17
4
16
3
15
2
1,26
13, 14
Type Description
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Output
Output
Input
Input
Output
Output
Output
Output
Output
Output
Output
Output
Table 28: Camera Link Connector 1
Neg. Base Data 0
Pos. Base Data 0
Neg. Base Data 1
Pos. Base Data 1
Neg. Base Data 2
Pos. Base Data 2
Neg. Base Data 3
Pos. Base Data 3
Neg. Base Clock
Pos. Base Clock
Pos. Serial Data to Camera
Neg. Serial Data to Camera
Neg. Serial Data to Frame Grabber
Pos. Serial Data to Frame Grabber
Neg. Camera Control 1
Pos. Camera Control 1
Pos. Camera Control 2
Neg. Camera Control 2
Neg. Camera Control 3
Pos. Camera Control 3
Pos. Camera Control 4
Neg. Camera Control 4
+12 V (see note following table)
Ground
Notes on PoCL support:

Refer to Sapera’s parameter CORACQ_PRM_POCL_ENABLE to enable PoCL and
CORACQ_PRM_SIGNAL_STATUS/CORACQ_VAL_SIGNAL_POCL_ACTIVE to verify if the POCL is active. See also Sapera++ reference parameter SapAcquisition::SignalPoCLActive for the current state.

PoCL state is maintained as long as the board is not reset
74 • Technical Specifications
Xtium-CL MX4 User's Manual
J2: Camera Link Connector 2
Medium and Full Camera Link sources require cables connected to both J2 and J3.
Name Pin # Type Description
MEDIUM _X0-
MEDIUM _X0+
MEDIUM _X1-
MEDIUM _X1+
MEDIUM _X2-
MEDIUM _X2+
MEDIUM _X3-
MEDIUM _X3+
MEDIUM _XCLK-
MEDIUM _XCLK+
TERM
TERM
FULL_X0-
FULL _X0+
FULL _X1-
FULL _X1+
FULL _X2-
FULL _X2+
FULL _X3-
FULL _X3+
FULL _XCLK-
FULL _XCLK+
PoCL
GND
5
17
4
15
2
20
7
19
6
18
25
12
24
11
23
10
21
8
22
9
16
3
1,26
13, 14
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Input
Table 29: Camera Link Connector 2
Neg. Medium Data 0
Pos. Medium Data 0
Neg. Medium Data 1
Pos. Medium Data 1
Neg. Medium Data 2
Pos. Medium Data 2
Neg. Medium Data 3
Pos. Medium Data 3
Neg. Medium Clock
Pos. Medium Clock
Term Resistor
Term Resistor
Neg. Full Data 0
Pos. Full Data 0
Neg. Full Data 1
Pos. Full Data 1
Neg. Full Data 2
Pos. Full Data 2
Neg. Full Data 3
Pos. Full Data 3
Neg. Full Clock
Pos. Full Clock
+12 V (see note following table)
Ground
Notes on PoCL support:

Refer to Sapera’s parameter CORACQ_PRM_POCL_ENABLE to enable PoCL and
CORACQ_PRM_SIGNAL_STATUS/CORACQ_VAL_SIGNAL_POCL_ACTIVE_2 to verify if the POCL is active. See also Sapera++ reference parameter SapAcquisition::SignalPoCLActive for the current state.

PoCL state is maintained as long as the board is not reset
Xtium-CL MX4 User's Manual
Technical Specifications • 75
Camera Link Camera Control Signal Overview
Four LVDS pairs are for general-purpose camera control, defined as camera inputs / frame grabber outputs by the Camera Link Base camera specification. These controls are on J3 connector.
• Camera Control 1 (CC1)
•
Camera Control 2 (CC2)
•
Camera Control 3 (CC3)
• Camera Control 4 (CC4)
Each camera manufacture is free to define the signals input on any one or all 4 control signals.
These control signals are used either as camera control pulses or as a static logic state. Control signals not required by the camera are simply assigned as not used. Refer to your camera's user manual for information on what control signals are required.
Note 1: The Xtium-CL MX4 pulse controller has a minimum resolution of 20ns.
Note 2: The internal line trigger frequency has a 2µs resolution.
The Xtium-CL MX4 can assign any camera control signal to the appropriate Camera Link control.
The following screen shot shows the Sapera CamExpert dialog where Camera Link controls are assigned (signals shown are not specific to any camera).
76 • Technical Specifications
Figure 23: CamExpert - Camera Link Controls
Xtium-CL MX4 User's Manual
J1: External Signals Connector (Female DH60-27P)
Warning: J1 and J4 have the same pinout assignment. Signals are routed to both connectors directly from their internal circuitry. Therefore never connect both J1 and J4 to external devices at the same time.
J4: Internal I/O Signals Connector (26-pin SHF-113-01-L-D-RA)
Important: The table below describes the I/O signals available on both J1 and J4.
(applies to Xtium-CL MX4 rev. A1)
Use only one of the two I/O connectors.
Description Pin # Pin # Description
Ground
RS-422 Shaft Encoder Phase A (-)
RS-422 Shaft Encoder Phase A (+)
Ground
RS-422 Shaft Encoder Phase B (-)
RS-422 Shaft Encoder Phase B (+)
General Input Common
External Trigger Input 1 (-)
General Input 1 (-)
External Trigger Input 1 (+)
General Input 1 (+)
External Trigger Input 2
General Input 2
Ground
Strobe 1 / General Output 1
General Output 2
Ground
Power Output 12 Volts, 350mA max
(from Aux Power Connector, see J7 below)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
General Input 3
General Input 4
Reserved
Reserved
Reserved
Reserved
General Output 3
General Output 4
Reserved
Reserved
Reserved
Reserved
Reserved
Table 30: J1 & J4 Connector Signals
Xtium-CL MX4 User's Manual
Technical Specifications • 77
Note 1: General Inputs / External Trigger Inputs Specifications
Each of the four General Inputs are opto-coupled and able to connect to single ended source signals. General Input 1 and 2 can also act as External Trigger Inputs. See “Board Information” user settings. These inputs generate individual interrupts and are read by the Sapera application.
The following figure is typical for each Genera Input. General Input 1 can be connected to a differential input signal. Note that in this specific case, the other 3 General Inputs cannot be used.
3.3V
649Ω
68.1K
0.01uF
EMI
Filter
From User
Interface
Connector
Figure 24: General Inputs Electrical Diagram
Input Details:
• The switch point is software programmable to support TTL, 12V or 24V input signals.
•
Maximum input signal frequency is 100 KHz.
•
Each input has a 649-ohm series resistor on the opto-coupler input.
•
The 0.01uF capacitor provide high frequency noise filtering.
• Maximum input voltage is 26V.
•
Minimum current is dependent on input voltage applied: I optoin
(min) = (V optoin
- 0.5)/649Ω
Input Level Switch Point Propagation Delay
(rising edge signal ↑ )
Propagation Delay
(falling edge signal ↓ )
TTL
1.6V 1.75 µs 5.5 µs
12V
6V 2.6 µs 2.6 µs
24V
12V 1.9 µs 3.1 µs
For External Trigger usage:
•
Input signal is “debounced” to ensure that no voltage glitch is detected as a valid transition.
This debounce circuit time constant can be programmed from 1
µ s to 255
µ s. Any pulse smaller than the programmed value is blocked and therefore not seen by the board. If no debounce value is specified (value of 0µs), the minimum value of 1µs will be used.
•
Refer to Sapera parameters:
CORACQ_PRM_EXT_TRIGGER_SOURCE
CORACQ_PRM_EXT_TRIGGER_ENABLE
CORACQ_PRM_EXT_TRIGGER_LEVEL
CORACQ_PRM_EXT_FRAME_TRIGGER_LEVEL
CORACQ_PRM_EXT_TRIGGER_DETECTION
CORACQ_PRM_EXT_TRIGGER_DURATION
•
See also *.cvi file entries:
External Trigger Level, External Frame Trigger Level, External Trigger Enable, External Trigger
Detection.
• External Trigger Input 2 used for two pulse external trigger with variable frame length line scan acquisition.
78 • Technical Specifications
Xtium-CL MX4 User's Manual
Trigger Signal Total Delay
External Trigger t(et)
Opto-Coupler t(oc)
Debouncer
1..255 us t(d)
Validated Trigger t(vt) = t(et) + t(oc) + t(d)
Figure 25: External Trigger Input Validation & Delay
Let t(et) = time of external trigger in µs t(oc) = time opto-coupler takes to change state (time varies dependent on input voltage) t(d) = user set debounce duration from 1 to 255µs t(vt) = time of validated trigger in µs
Table 31: External Trigger Timing Specifications
Note: Teledyne DALSA recommends using the fastest transition to minimize the time it takes for the opto-coupler to change state.
If the duration of the external trigger is > t(oc) + t(d), then a valid acquisition trigger is detected.
It is possible to emulate an external trigger using the software trigger which is generated by a function call from an application.
Xtium-CL MX4 User's Manual
Technical Specifications • 79
Block Diagram: Connecting External Drivers to General Inputs on J1 or J4
External Signals Xtium-CL MX4
User Signal Ground / Input 1 (-)
V (+)
Compatible
Driver
1
V (+)
Compatible
Driver
2
V (+)
Compatible
Driver
3
V (+)
Compatible
Driver
4
11 :
12 :
13 :
14 :
15 :
16 :
17 :
18 :
19
20 :
:
21 :
22 :
23 :
24 :
25 :
26
27
:
:
1 :
2 :
3 :
4 :
5 :
6 :
7 :
8 :
9 :
10 :
Ground
Shaft Encoder A (-)
Shaft Encoder A (+)
Ground
Shaft Encoder B (-)
Shaft Encoder B (+)
Input Common Ground
General Input 1 / Trigger 1 (+)
General Input 2 / Trigger 2
Ground
General Output 1 / Strobe
General Output 2
Ground
Power (12 Volts)
General Input 3
General Input 4
Reserved
Reserved
Reserved
Reserved
General Output 3
General Output 4
Reserved
Reserved
Reserved
Reserved
Reserved
J1/J4: External Signals
Connectors
External Driver Electrical Requirements
The Xtium-CL allows user selected (software programmable) input switching points to support TTL,
12V or 24V input signals. The following table defines the external signal voltage requirements from the driver circuits connected to the Xtium external inputs.
Input Level Description MIN MAX
TTL
12V
24V
Output Voltage High
(V
OH
)
Output Voltage Low
(V
OL
)
Output Voltage High
(V
OH
)
Output Voltage Low
(V
OL
)
Output Voltage High
(V
OH
)
Output Voltage Low
(V
OL
)
2.4 V
0 V
9 V
0 V
18 V
0 V
5.5 V
0.8 V
13.2 V
3 V
26.4 V
6 V
80 • Technical Specifications
Xtium-CL MX4 User's Manual
Note 2: General Outputs /Strobe Output Specifications
Each of the four General Outputs are TTL (3.3V) compatible. General Output 1 also functions as the
Strobe Output controlled by Sapera strobe control functions. See “Board Information” user settings. The following figure is typical for each General Output.
3.3V
Output
Buffer
LVTTL
75Ω
To User
Interface
Connector
Enable
EMI
Filter
Figure 26: General Outputs Electrical Diagram
Output Details:
•
Each output has a 75-ohm series resistor
•
The 2 diodes protects the LVTTL buffer against overvoltage
• Each output is a tri-state driver, enabled by software
•
Minimum guaranteed output current is +/- 24mA @ 3.3V
•
Maximum output current is 50mA
• Maximum short circuit output current is 44mA
•
Minimum voltage for output level high is 2.4V, while maximum voltage for output low is 0.55V
•
Maximum output switching frequency is limited by driver and register access on the PCIe bus.
For Strobe Usage:
• Refer to Sapera Strobe Methods parameters:
CORACQ_PRM_STROBE_ENABLE
CORACQ_PRM_STROBE_POLARITY
CORACQ_PRM_STROBE_LEVEL
CORACQ_PRM_STROBE_METHOD
CORACQ_PRM_STROBE_DELAY
CORACQ_PRM_STROBE_DURATION
•
See also *.cvi file entries:
Strobe Enable, Strobe Polarity, Strobe Level, Strobe Method, Strobe Delay, Strobe Duration.
Xtium-CL MX4 User's Manual
Technical Specifications • 81
Block Diagram: Connecting External Receivers to the General Outputs
To External Devices Xtium-CL MX4
Vcc
Compatible
Receiver
1
Vcc
Compatible
Receiver
2
Vcc
Compatible
Receiver
3
Vcc
Compatible
Receiver
4
User Signal Ground
11 :
12 :
13 :
14 :
15 :
16 :
17 :
18 :
19
20
21 :
22 :
23 :
24 :
25 :
26
27
:
:
:
:
1 :
2 :
3 :
4 :
5 :
6 :
7 :
8 :
9 :
10 :
Ground
Shaft Encoder A (-)
Shaft Encoder A (+)
Ground
Shaft Encoder B (-)
Shaft Encoder B (+)
Input Common Ground
General Input 1 / Trigger 1
General Input 2 / Trigger 2
Ground
General Output 1 / Strobe
General Output 2
Ground
Power (12 Volts)
General Input 3
General Input 4
Reserved
Reserved
Reserved
Reserved
General Output 3
General Output 4
Reserved
Reserved
Reserved
Reserved
Reserved
J1: External Signals Connector
(DH60-27P)
External Receiver Electrical Requirements
External receiver circuits connected to the Xtium General Outputs must be compatible to TTL signals.
Input Level Description MIN MAX
TTL
Input Voltage High
(V
IH
)
Input Voltage Low
(V
IL
)
2.0 V
–
–
0.8 V
82 • Technical Specifications
Xtium-CL MX4 User's Manual
Note 3: RS-422 Shaft Encoder Input Specifications
Dual Quadrature Shaft Encoder Inputs (phase A and phase B) connect to differential signals (RS-
422) or single ended TTL 5V source signals. The figure below shows the simplified representation of these inputs.
Phase B
PhaseB+
PhaseB-
From User
Interface
Connector
PhaseA+
Phase A
PhaseA-
Figure 27: RS-422 Shaft Encoder Input Electrical Diagram
•
Maximum input voltage is +/- 7V with a differential voltage level of +/- 200mV.
•
All inputs have a 100-ohm differential resistor.
• Maximum input signal frequency is 10 MHz.
•
The Xtium-CL provides ESD filtering on-board.
•
See Line Trigger Source Selection for Line scan Applications for more information.
•
Refer to Sapera parameters:
CORACQ_PRM_SHAFT_ENCODER_ENABLE CORACQ_PRM_SHAFT_ENCODER_DROP or refer to CORACQ_PRM_EXT_LINE_TRIGGER_ENABLE
CORACQ_PRM_EXT_LINE_TRIGGER_DETECTION
CORACQ_PRM_EXT_LINE_TRIGGER_LEVEL (fixed at RS-422)
CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE
• See also *.cvi file entries:
Shaft Encoder Enable, Shaft Encoder Pulse Drop, or see External Line Trigger Enable, External Line Trigger Detection, External Line Trigger Level,
External Line Trigger Source.
•
For TTL single ended signals, connect a bias voltage to the RS-422 (-) input to ensure correct detection of the logic state of the signal connected to the RS-422 (+) input. See the following section for connection methods.
Xtium-CL MX4 User's Manual
Technical Specifications • 83
Example: Connecting to the RS-422 Shaft Encoder Block Diagram
External Signals Xtium-CL MX4
V (+)
RS-422
Compatible
Driver
1
V (+)
RS-422
Compatible
Driver
2
User Signal Ground
1 :
2 :
3 :
4 :
5 :
6 :
7 :
8 :
9 :
10 :
11 :
12 :
13 :
14 :
15 :
16 :
17 :
18 :
19
20
21 :
22 :
23 :
24 :
25 :
26
27
:
:
:
:
Ground
Shaft Encoder A (-)
Shaft Encoder A (+)
Ground
Shaft Encoder B (-)
Shaft Encoder B (+)
Input Common Ground
General Input 1 / Trigger 1
General Input 2 / Trigger 2
Ground
General Output 1 / Strobe
General Output 2
Ground
Power (12 Volts)
General Input 3
General Input 4
Reserved
Reserved
Reserved
Reserved
General Output 3
General Output 4
Reserved
Reserved
Reserved
Reserved
Reserved
J1: External Signals Connector
(DH60-27P)
•
External shaft encoder circuits using RS-422 output drivers must meet the following Xtium-CL signal requirements for proper board control:
RS-422 External Driver MIN TYP
Differential Output Voltage High (
V
ODH
)
Differential Output Voltage Low (
V
ODL
)
2 V
-14 V
14 V
-2 V
84 • Technical Specifications
Xtium-CL MX4 User's Manual
Example: Connecting a TTL Shaft Encoder to RS-422 Inputs
Connecting TTL Signals to
RS-422 Inputs
TTL signal source
GND
Bias Voltage
+1V to +2V
DC
RS-422 (+) input
RS-422 (-) input
Frame Grabber System
FG/system GND
Figure 28: Connecting TTL to RS-422 Shaft Encoder Inputs
• RS-422 (-) input is biased to a DC voltage from +1 to +2 volts.
•
This guarantees that the TTL signal connected to the RS-422 (+) input will be detected as a logic high or low relative to the (-) input.
•
The TTL shaft encoder ground, the bias voltage ground, and the Xtium-CL MX4 computer system ground must be connected together.
Example for Generating a RS-422 (-) Input Bias Source
Examples on Generating a DC voltage for the RS-422 (-) Input
+5V +12V +24V
Battery
+1.5V
330
220
+2V
680
100
+1.5V
2.2K
150
+1.5V
Figure 29: Generating a DC Bias Voltage
•
DC voltage for the RS-422 (-) input can be generated by a resister voltage divider.
• Use a single battery cell if this is more suitable to your system.
J5: Multi-Board Sync / Bi-directional General I/Os
There are 8 bi-directional General I/Os that can be interconnected between multiple boards. These bi-directional I/Os can be read/written by Sapera application. Bi-directional General I/Os no.1 and no.2 also can also act as the multi-board sync I/Os.
The multi-board sync feature permits interconnecting multiple Xtium boards to synchronize acquisitions to one or two triggers or events. The trigger source origin can be either an external signal or a software control signal. The board sending the trigger(s) is the “Sync Master” board, while the one or more boards receiving the control signal(s) are “Sync Slaves”.
Setup of the boards is done either by setting parameters via a Sapera application or by using
CamExpert to configure two camera files (.ccf). For testing purposes, two instances of CamExpert
(one for each board) can be run on the system where the frame grabbers are installed.
Xtium-CL MX4 User's Manual
Technical Specifications • 85
Hardware Preparation

Interconnect two, three, or four Xtium boards via their J5 connector using the OR-YXCC-
BSYNC20 cable (for 2 boards) or the OR-YXCC-BSYNC40 cable (see Board Sync Cable Assembly
OR-YXCC-BSYNC40 for 3 or 4 boards).
Configuration via Sapera Application Programming

Sync Master Board Software Setup: Choose one Xtium as “Sync Master”. The Sapera parameter
CORACQ_PRM_BOARD_SYNC_OUTPUT1_SOURCE and/or
CORACQ_PRM_BOARD_SYNC_OUTPUT2_SOURCE select the signal(s) to send to the “Sync Slave” boards
.

Other “Sync Master” board parameters are set as for any external trigger application, such as
External Trigger enable, detection, and level. See Sapera documentation for more details.

Sync Slave Board Software Setup: The Sapera parameter
CORACQ_PRM_EXT_TRIGGER_SOURCE and/or
Board Sync #1 or #2.
CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE
are set to
Configuration via Sapera CamExpert

Start the first instance of CamExpert and select one installed Xtium board to be the sync
master. As shown in the following image, this board is configured to use an external trigger on input #1.

The Sync Master Xtium board is also configured to output the external trigger on board sync
#1, as shown in the following image.
86 • Technical Specifications
Xtium-CL MX4 User's Manual

The Sync Slave Xtium board is configured to receive its trigger on the board sync signal. As an example the following image shows the Xtium board configured for an external sync on board sync #2.

Test Setup: Start the acquisition on all slave boards. The acquisition process is now waiting for the control signal from the master board. Trigger master board acquisition and the acquisition start signal is sent to each slave board.
J7: Power Connector
DC Power Details
Warning: Never remove or install any hardware component with the computer power on.
Never connect a power cable to J7 when the computer is powered on.
•
Connect a computer 6-pin PCI Express power connector to J7 to supply DC power to the
Camera Link connectors for PoCL operation and/or to supply power to connector J1. Older
computers may need a power cable adapter (see Power Cable Assembly OR-YXCC-PWRY00).
• The 12 Volt can supply up to 8W of power to the cameras (4W per connector) and 6W to J1 or
J4. Note that J1 and J4 has a 500 mA re-settable fuse on the board. If the fuse trips open, turn off the host computer power. When the computer is powered again, the fuse is automatically reset.
Xtium-CL MX4 User's Manual
Technical Specifications • 87
Cables & Accessories
The following cables and accessories are available for purchase. Contact sales at Teledyne DALSA.
DH40-27S Cable to Blunt End (OR-YXCC-27BE2M1, Rev B1)
Cable assembly consists of a 2000 mm (~6 ft.) blunt end cable to mate to Xtium external connector J1. Note: The applicable wiring color code table is included with the printed Product
Notice shipped with the cable package — no other wiring table should be used.
Important: Cable part number OR-YXCC-27BE2M0 rev.3 is obsolete and should not be used with any Xtium series boards.
Figure 30: DH60-27P Cable No. OR-YXCC-27BE2M1 Detail
88 • Technical Specifications
Figure 31: Photo of cable OR-YXCC-27BE2M1
Xtium-CL MX4 User's Manual
DH40-27S Connector Kit for Custom Wiring
Teledyne DALSA makes available a kit comprised of the DH40-27S connector plus a screw lock housing package, for clients interested in assembling their own custom I/O cable. Order part number “OR-YXCC-H270000”, (package as shown below).
Xtium-CL MX4 User's Manual
Table 32: OR-YXCC-H270000 Custom Wiring Kit
Technical Specifications • 89
Cable assemblies for I/O connector J4
Flat ribbon cables for connecting to J4 can be purchased from Teledyne DALSA or from third part suppliers, as described below.
Teledyne DALSA I/O Cable (part #OR-YXCC-TIOF120)
Contact Teledyne DALSA Sales to order the 12 inch (~30cm) I/O cable with connectors on both ends, as shown in the following picture.
Figure 32: I/O Cable #OR-YXCC-TIOF120
Third Party I/O Cables for J4
Suggested third party cables are available from SAMTEC. Below are two examples:

Connector to connector (FFSD-13-D-xx.xx-01-N)

Connector to blunt end (FFSD-13-S-xx.xx-01-N)

Note: xx.xx denotes length, where 06.00 is a 6 inch (~15 cm) length cable

URL: http://cloud.samtec.com/catalog_english/FFSD.PDF
90 • Technical Specifications
Xtium-CL MX4 User's Manual
Board Sync Cable Assembly OR-YXCC-BSYNC40
This cable connects 3 to 4 Xtium boards for the board sync function as described in section J5:
Multi-Board Sync / Bi-directional General I/Os. For a shorter 2 board cable, order cable assembly
OR-YXCC-BSYNC20.
For a third part source of cables, see http://cloud.samtec.com/catalog_english/FFSD.PDF
.
Figure 33: Photo of cable OR-YXCC-BSYNC40
Xtium-CL MX4 User's Manual
Technical Specifications • 91
Power Cable Assembly OR-YXCC-PWRY00
When the Xtium-CL MX4 supplies power to cameras via PoCL and/or when power is supplied to external devices via the J1 I/O connector, PC power must be connected to the Xtium external power source connector (J7).
Recent computer power supplies provide multiple 6-pin power source connectors for PCI Express video cards, where one is connected to J7 on the Xtium-CL. But if the computer is an older model, this power supply adapter converts 2 standard 4-pin large power connectors to a 6-pin power connector.
Figure 34: Photo of cable assembly OR-YXCC-PWRY00
This is an industry standard adapter cable which can be purchased from Teledyne DALSA.
92 • Technical Specifications
Xtium-CL MX4 User's Manual
Camera Link Interface
Camera Link Overview
Camera Link is a communication interface for vision applications developed as an extension of
National Semiconductor's Channel Link technology. The advantages of the Camera Link interface are that it provides a standard digital camera connection specification, a standard data communication protocol, and simpler cabling between camera and frame grabber.
The Camera Link interface simplifies the usage of increasingly diverse cameras and high signal speeds without complex custom cabling. For additional information concerning Camera Link, see
http://en.wikipedia.org/wiki/Camera_Link
.
Rights and Trademarks
Note: The following text is extracted from the Camera Link Specification 1.1 (January 2004).
The Automated Imaging Association (AIA), as sponsor of the Camera Link committee, owns the U.S. trademark registration for the Camera Link logo as a certification mark for the mutual benefit of the industry. The AIA will issue a license to any company, member or non-member, to use the Camera Link logo with any products that the company will self-certify to be compliant with the Camera Link standard. Licensed users of the Camera Link logo will not be required to credit the AIA with ownership of the registered mark.
3M™ is a trademark of the 3M Company.
Channel Link™ is a trademark of National Semiconductor.
Flatlink™ is a trademark of Texas Instruments.
Panel Link™ is a trademark of Silicon Image.
Data Port Summary
The Camera Link interface has three configurations. A single Camera Link connection is limited to
28 bits requiring some cameras to have multiple connections or channels. The naming conventions for the three configurations are:
•
Base: Single Channel Link interface, single cable connector
• Medium: Two Channel Link interface, two cable connectors
• Full: Three Channel Link interface, two cable connectors
A single Camera Link port is defined as having an 8-bit data word. The "Full" specification supports eight ports labeled as A to H.
Xtium-CL MX4 User's Manual
Camera Link Interface • 93
Camera Signal Summary
Video Data
Four enable signals are defined as:
• FVAL
• LVAL
•
DVAL
•
Spare
Frame Valid (FVAL) is defined HIGH for valid lines
Line Valid (LVAL) is defined HIGH for valid pixels
Data Valid (DVAL) is defined HIGH when data is valid
A spare has been defined for future use
The camera provides the four enables on each Channel Link. All unused data bits must be set to a known value by the camera.
Camera Controls
Four LVDS pairs are reserved for general-purpose camera control, defined as camera inputs and frame grabber outputs.
•
Camera Control 1 (CC1)
•
Camera Control 2 (CC2)
• Camera Control 3 (CC3)
•
Camera Control 4 (CC4)
Note: the Xtium-CL MX4 by default implements the control lines as follows,
(using Teledyne DALSA terminology):
(CC1) EXYNC
(CC2) PRIN
(CC3) FORWARD
(CC4) HIGH
Communication
Two LVDS pairs are allocated for asynchronous serial communication to and from the camera and frame grabber. Cameras and frame grabbers should support at least 9600 baud.
•
SerTFG Differential pair with serial communications to the frame grabber
•
SerTC Differential pair with serial communications to the camera
The serial interface protocol is one start bit, one stop bit, no parity, and no handshaking.
Camera Link Cables
For additional information on Camera Link cables and their specifications, visit the following web sites:
3 M
Nortech Systems http://www.3m.com/interconnects /
(enter Camera Link as the search keyword) http://www.nortechsys.com/intercon/CameraLinkMain.htm
Table 33: Camera Link Cables Suppliers
94 • Camera Link Interface
Xtium-CL MX4 User's Manual
Contact Information
Sales Information
Visit our web site:
Email:
Canadian Sales
Teledyne DALSA — Head office
605 McMurray Road
Waterloo, Ontario, Canada, N2V 2E9
Tel: 519 886 6000
Fax: 519 886 8023
USA Sales
Teledyne DALSA — Billerica office
700 Technology Park Drive
Billerica, Ma. 01821
Tel: (978) 670-2000
Fax: (978) 670-2010
Asian Sales
Teledyne DALSA Asia Pacific
Ikebukuro East 13F
3-4-3 Higashi Ikebukuro,
Toshima-ku, Tokyo, Japan
Tel: +81 3 5960 6353
Fax: +81 3 5960 6354 www.teledynedalsa.com/mv mailto:[email protected]
Teledyne DALSA — Montreal office
880 McCaffrey
St. Laurent, Quebec, Canada, H4T 2C7
Tel: (514) 333-1301
Fax: (514) 333-1388
European Sales
Teledyne DALSA GMBH
Lise-Meitner-Str. 7
82152 Krailling (Munich), Germany
Tel: +49 – 89 89545730
Fax:+49 – 89 895457346 [email protected]
Shanghai Industrial Investment Building
Room G, 20F, 18 North Cao Xi Road,
Shanghai, China 200030
Tel: +86-21-64279081
Fax: +86-21-64699430
Technical Support
Submit any support question or request via our web site:
Technical support form via our web page:
Support requests for imaging product installations,
Support requests for imaging applications
Camera support information
Product literature and driver updates http://www.teledynedalsa.com/mv/support
Xtium-CL MX4 User's Manual
Contact Information • 95
Index
A
Acquisition and Control Unit 48 acquisition bandwidth 34
Acquisition events 49 acquisition module 49 acquisition parameters 39
ACUPlus 8 administrator 17
AUTORUN 11
B
Block Diagram 41
BoardInfo.txt 20, 31
C
cables 72 calibration information 32 camera configuration file 35 camera control 18, 76
Camera file 40, 46, 47
Camera Link 9, 72, 76, 93
Camera Link cabling 18
Camera Link control 76 camera power 72 camera timing 35
CamExpert 40, 46, 47
CamExpert parameters 36 communication ports 9 computer administrator 11
Contiguous Memory 22
CORACQ_PRM_EXT_LINE_TRIGGER_DETECTION 83
CORACQ_PRM_EXT_LINE_TRIGGER_ENABLE 83
CORACQ_PRM_EXT_LINE_TRIGGER_LEVEL 83
CORACQ_PRM_EXT_LINE_TRIGGER_SOURCE 83
CORACQ_PRM_EXT_TRIGGER_DETECTION 78
CORACQ_PRM_EXT_TRIGGER_ENABLE 78
CORACQ_PRM_EXT_TRIGGER_LEVEL 78
CORACQ_PRM_SHAFT_ENCODER_DROP 83
CORACQ_PRM_SHAFT_ENCODER_ENABLE 83
CORACQ_PRM_SHAFT_ENCODER_LEVEL 83
CORACQ_PRM_STROBE_DELAY 81
CORACQ_PRM_STROBE_DURATION 81
CORACQ_PRM_STROBE_ENABLE 81
CORACQ_PRM_STROBE_LEVEL 81
CORACQ_PRM_STROBE_METHOD 81
CORACQ_PRM_STROBE_POLARITY 81
D
Data Overflow event 49
Data Transfer Engine 9
Device Manager 12, 20, 31 device report 20 driver upgrade 17
E
Embedded Windows answer files 65
End of Frame event 50
End of Transfer event 50
External Signals Connector 45, 47
External Signals Connector Bracket Assembly 45
F
failure - firmware upgrade 31
Firmware Loader 12 firmware revision 20 firmware selection 8
Found New Hardware Wizard 11 frame buffer 22, 46
Frame Lost event 49
Frame Sync 47
FRAME_RESET 46
H
HyperTerminal 9, 18
I
image processing 7
Imaging drivers 30 installer response file 14, 15 launch.exe 11
Line Scan 8, 45
Log Viewer program 32
LVDS pairs 76
L
MDR-26 72 multi-board sync 85, 86
M
N
National Semiconductor 93 out-of-memory error 22
O
P
PCI bus latency 48
PCI Bus Number 29
PCI configuration registers 28
PCI configuration space 28, 31, 33
PCI conflict 31
Phase A 45 physical dimensions 68
Q
Quadrature Shaft Encoder 9
96 • Index
Xtium-CL MX4 User's Manual
S
Sapera buffers allocation 22
Sapera CamExpert 33
Sapera CD-ROM 11, 17
Sapera configuration program 18, 22
Sapera LT Development Library 11
Sapera LT User’s manual 12
Sapera messaging 22 scatter gather buffers 23
Scatter-Gather 9 serial communication port 18 serial port speeds 18 shaft encoder 9, 45 software trigger 33, 79
Static electricity 11 system COM port 18
T
technical support 17, 20, 30, 33 transfer module 50 trigger 9, 45, 46
V
viewer program 32 virtual frame buffer 46 visual LED indicators 9
W
Web inspection 45
Windows Embedded 7 65
Windows HyperTerminal 18
Windows operating system memory 23 workstation 17
X
X64-CL serial port 18
Xtium-CL MX4 User's Manual
Index • 97
advertisement
Key Features
- Camera Link 2.0 compliant
- PCI Express x4 Gen2 interface
- Supports area scan and line scan cameras
- Acquisition from monochrome, RGB, Bayer, and Bi-Color cameras
- External input triggers
- Shaft encoder inputs
- Strobe outputs
- Power Over Camera Link (PoCL) support
