1. Manuals
  2. Brands
  3. Dalsa Manuals
  4. Computer Hardware
  5. Everywhereyoulook Xtium2-CL MX4
  6. User manual

Dalsa Everywhereyoulook Xtium2-CL MX4 User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
™
Xtium2-CL MX4
User's Manual
Edition 1.00
sensors | cameras | frame grabbers | processors | software | vision solutions
P/N: OC-A4CM-MUSR0
www.teledynedalsa.com

Advertisement

Table of Contents
loading

Related Manuals for Dalsa Everywhereyoulook Xtium2-CL MX4

Summary of Contents for Dalsa Everywhereyoulook Xtium2-CL MX4

  • Page 1 ™ Xtium2-CL MX4 User's Manual Edition 1.00 sensors | cameras | frame grabbers | processors | software | vision solutions P/N: OC-A4CM-MUSR0 www.teledynedalsa.com...
  • Page 2 Teledyne DALSA Digital Imaging of f ers 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 sof tware to easy-to-use vision appliances and custom vision modules.

  • Page 3: Table Of Contents

    NSTALLATION VERVIEW Hardware Installation Multi-board Sync & I/O Setup Sapera LT Library & Xtium2-CL MX4 Driver Installation Teledyne DALSA Device Drivers Installation Procedure Xtium2-CL MX4 Firmware Loader Firmware Update: Automatic Mode Firmware Update: Manual Mode Performing a Manual Firmware Update...
  • Page 4 APERA AMERA ONFIGURATION ILES Camera Types & Files Camera Files Distributed with Sapera Overview of Sapera Acquisition Parameter Files (*.ccf or *.cca/*.cvi) Concepts and Differences between the Parameter Files CCF File Details CCA File Details CVI File Details Saving a Camera File Camera Interfacing Check List 2-CL MX4 SING...
  • Page 5 RIGGER TO MAGE ELIABILITY Supported Events and Transfer Methods Acquisition Events Transfer Events Trigger Signal Validity Supported Transfer Cycling Methods LUT A UTPUT VAILABILITY ETADATA HEORY OF PERATION Metadata Data Structure IELD ORRECTION HEORY OF PERATION Flat Field Correction Lists Flat Field Correction Sets Xtium2-CL MX4 specif ic limitations Programming the sets...
  • Page 6 DH40-27S Cable to Blunt End (OR-YXCC-27BE2M1, Rev B1) DH40-27S Connector Kit for Custom Wiring Cable assemblies for I/O connector J1 Teledyne DALSA I/O Cable (part #OR-YXCC-TIOF120) Third Party I/O Cables for J1 Cable assemblies for I/O connector J2 External Signals Connector Bracket Assembly...
  • Page 7 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 Teledyne DALSA Log Viewer On-board Image Memory Requirements for Acquisitions Dual Camera Input Conf iguration Symptoms: CamExpert Detects no Boards...

  • Page 8: Product Part Numbers

    Item Product Number Sapera LT version 8.60 or later for full feature support (available as a free OC-SL00-0000000 download from the Teledyne DALSA website.). 1. Sapera LT: Provides everything needed to build imaging application. 2. Current Sapera-compliant board hardware drivers 3.

  • Page 9: Xtium2-Cl Mx4 Frame Grabber Features

    Flat Field and Flat Line correction: pixel replacement using either neighborhood pixels or 3x2 cluster replacement. • External Input Triggers and Shaf t Encoder inputs, along with Strobe outputs • Supports a number of acquisition events in compliance with "Teledyne DALSA’s Trigger to Image Reliability" • RoHS compliant •...

  • Page 10: User Programmable Configurations

    Base Camera Link RGB camera, 1 tap Use the Xtium2-CL MX4 f irmware f irmware loader f unction in the Teledyne DALSA Device manager utility to select f irmware f or one of the supported modes. Firmware selection is made either during driver installation or manually later on (see Firmware Update: Manual Mode).

  • Page 11: Dte: Intelligent Data Transfer Engine

    DTE: Intelligent Data Transfer Engine The Xtium2-CL MX4 intelligent Data Transfer Engine ensures f ast 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.

  • Page 12: Development Software Overview

    Sapera++ LT is a powerful development library f or image acquisition and control. Sapera++ LT provides a single API across all current and f uture Teledyne DALSA hardware. Sapera++ LT delivers a comprehensive f eature set including program portability, versatile camera controls, f lexible display f unctionality and management, plus easy to use application deve lopment wizards.

  • Page 13: Quick Start Setup & Installation

    Quick Start Setup & Installation The f ollowing procedure outlines the basic steps required to install the Teledyne DALSA Xtium2-CL MX4. For complete installation details and inf ormation, see Installing Xtium2-CL MX4. Install the Xtium2-CL MX4 in an available PCIe x4 (or x8) slot on the host computer.
  • Page 14 To complete the installation, update the Xtium2-CL MX4 firmware when prompted; select Automatic to update with the default configuration (Full Camera Link) or Manual to select another option (2 Base Camera Link or 80-Bits Camera Link). Reboot when all sof tware and board drivers are installed. Launch Sapera LT CamExpert to verify the installation;...
  • Page 15 Xtium2-CL MX4 User's Manual Quick Start Setup & Installation • 13...
  • Page 16 In CamExpert, click Detect Camera. If the Detect Camera button is disabled, click Settings to open the the Communication Settings dialog to conf igure CamExpert to detect attached cameras using a serial port. When CamExpert detects a camera (if GenCP compliant), camera parameters are displayed along with the board parameters.
  • Page 17 Click Grab to acquire a test image to validate the setup. Modif y the board and camera parameters as necessary. When completed, save the camera configuration f ile. The Xtium2-CL MX4 can be conf igured using the the parameter settings in this f ile w hen using the Sapera LT API in your application to acquire images Xtium2-CL MX4 User's Manual Quick Start Setup &...

  • Page 18: Installing Xtium2-Cl Mx4

    Installing Xtium2-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 f eel comfortable performing the installation, please consult a qualif ied computer technician.

  • Page 19: Sapera Lt Library & Xtium2-Cl Mx4 Driver Installation

    Installation Procedure Sapera LT is installed bef ore Teledyne DALSA board drivers. ▪ Download the Sapera LT SDK f rom the Teledyne DALSA website and run the executable f ile; the ▪ installation menu is presented. The installation program may prompt to reboot the computer. It is not necessary to reboot the ▪...

  • Page 20: Xtium2-Cl Mx4 Firmware Loader

    Xtium2-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 Xtium2-CL MX4 requires a f irmware update. If f irmware is required, a dialog displays. This dialog also allows the user to load f irmware f or alternate operational modes of the Xtium2-CL MX4.

  • Page 21: Firmware Update: Manual Mode

    Firmware Update: Manual Mode Select Manual mode to load f irmware other then the def ault version or when, in the case of multiple Xtium2-CL MX4 boards in the same system, if each requires dif ferent f irmware. The f ollowing f igure shows the Device Manager manual f irmware screen. Displayed is inf ormation on all installed Xtium2-CL MX4 boards, their serial numbers, and their f irmware components.

  • Page 22: Executing The Firmware Loader From The Start Menu

    If required, the Xtium2-CL MX4 Firmware Loader program is executed via the Windows Start Menu shortcut Start • Programs • Teledyne DALSA • Xtium2-CL MX4 Driver • Firmware Update. A f irmware change af ter installation is required to select a dif f erent configuration mode. For...

  • Page 23: Upgrading Sapera Or Board Driver

    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 f irst. Described below are two upgrade situations. Note that if the board is installed in a dif f erent slot, the new hardware wizard opens.

  • Page 24: Preserving Board Parameters During Driver Upgrade

    Preserving Board Parameters during Driver Upgrade User def ined parameter settings f or previously installed boards can be preserved when upgrading a device driver by using an install.ini f ile as described in Custom Driver Installation using install.ini. Clicking Automatic on the Device Manager Start-up dialog will apply the settings specif ied in the install.ini f ile.

  • Page 25: Preserving Board Parameters During Board Replacement Or System Cloning

    “User Def ined” or “Manual Configuration” in the Teledyne DALSA Device Manager start-up dialog under the Device Inf o column. User-defined settings are specific to the PCI Express slot on the system.

  • Page 26: Device Manager - Board Viewer

    The f ollowing screen image shows the Device Manager program with the Inf ormation/Firmware tab active. The lef t window displays all Teledyne DALSA Xtium2-CL MX4 boards in the system and their individual device components. The right window displays the inf or mation stored in the selected board device.

  • Page 27: Information Field Description

    [Read/Write]: This is a 64 byte general purpose user storage area. User Data For inf ormation on how to read/write this f ield at the application level, contact Teledyne DALSA Technical Support. User Interf ace GIOs [Read/Write]: Use this f ield to select the def ault input level of the Def ault Input Level User Interf ace GIOs.
  • Page 28 By def ault, boards are shipped with Open Interf ace GIOs 1 & 2 reserved for Board Sync 1 & User Interf ace GIOs [Read/Write]: Use this f ield to select the def ault Output State of the Def ault Output State User Interf ace GIOs.

  • Page 29: Changing Device Settings

    Changing Device Settings When device settings are changed, the board must be programmed and reset to effect the changes. If board programming is required, the Program button is displayed in green; click the button to start programming. When programming is complete, the Reset button is displayed in green, click the button to reset the board.

  • Page 30: Device Information Report

    Device Information Report Teledyne DALSA Technical Support may request device inf ormation report to aid in troubleshooting installation or operational problems. Generate the Xtium2-CL MX4 device manager report f ile (BoardInfo.txt) by clicking File • Save Device Info. Figure 9: Device Manager File Menu Save Device Info Command 28 •...

  • Page 31: Using The Camera Link Serial Control Port

    When required, map the Xtium2-CL MX4 serial port to an available COM port by using the Sapera Conf iguration tool. Run the program f rom the Windows start menu: Start • Programs • DALSA • Sapera LT • Sapera Configuration.

  • Page 32: Configuring Sapera

    Configuring Sapera The Sapera configuration program (Start • Programs • Teledyne DALSA • Sapera LT • Sapera Configuration) allows the user to see all available Sapera servers f or 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 alway s be present.

  • Page 33: Host Computer Frame Buffer Memory Limitations

    Memory f or this data is reserved in chunks of 64kB blocks. If vertical f lipping is enabled, one must add 16 bytes per line per buf f er. For example, f or an image 4080x3072 image: 16 bytes * 3072 = 49152 bytes. Note 1: Sapera LT reserves the 1st 5MB for its own resources, which includes the 200 bytes per frame buffer mentioned above.

  • Page 34: Camexpert Quick Start

    CamExpert Quick Start Interfacing Cameras with CamExpert CamExpert is the camera-interfacing tool f or Teledyne DALSA frame grabber boards supported by the Sapera library. CamExpert is the primary tool to conf igure, test and calibrate your camera and imaging setup. Display tools include, image pixel value readout, image zoom, and histogram.
  • Page 35 CamExpert groups parameters into f unctional categories. The parameters shown depend on the f rame grabber used and what camera is connected. The parameter values are either the camera def aults or the last stored value when the camera was used. Device Selector: Two drop menus allow selection of which device and which saved ▪...

  • Page 36: Sapera Camera Configuration Files

    (CCF) that describes the desired camera and f rame grabber configuration. Teledyne DALSA continually updates a camera application library composed of application inf ormation and prepared camera f iles. Camera files are ASCII text, readable with Windows Notepad on any computer without having Sapera installed.

  • Page 37: Ccf File Details

    Camera Configuration f ile used with Sapera LT 5.0 and the CamExpert utility. CCA File Details Teledyne DALSA distributes camera f iles using the legacy “.CCA” extension, (CAMERA f iles), which contain all parameters describing the camera video signal characteristics and operation modes (what the camera outputs).

  • Page 38: Saving A Camera File

    The dialog that opens allows adding details such as camera inf ormation, mode of operation, and a f ile name f or the .ccf f ile. The f ollowing image is a sample f or a Teledyne DALSA Falcon camera.

  • Page 39: Using Camexpert With Xtium2-Cl Mx4

    Using CamExpert with Xtium2-CL MX4 The Sapera CamExpert tool is the interf acing tool f or Xtium2-CL MX4 f rame grabbers and connected cameras; it is supported by the Sapera library and hardware. CamExpert allows a user to test f rame grabber and camera f unctions. Additionally CamExpert saves the f rame grabber settings conf iguration as individual camera parameter files on the host system (*.ccf).

  • Page 40: Basic Timing Category

    Basic Timing Category The Basic Timing category groups parameters such as camera type, the active image size, and other settings related to basic timing. Parameter Descriptions The f ollowing table describes the CamExpert Basic Timing category of Sapera LT parameters. Acquisition server notes, if applicable, indicate if parameter availablility or supported values are dependent on the selected f rame grabber acquisition server and acquisition device.
  • Page 41 Pixel Clock Input Specifies the external pixel clock CORACQ_PRM_PIXEL_CLK_EXT frequency, in MHz. Valid range is 20- Frequency (MHz) 85MHz. Specifies if the acquisition board uses the Data Valid CORACQ_PRM_DATA_VALID_ENABLE camera data valid signal. Boolean parameter (TRUE or FALSE). Camera Sensor CORACQ_PRM_TAPS Defines the number of taps output and For application server...

  • Page 42: Advanced Control Category

    Advanced Control Category The Advanced Control category groups parameters f or configuring camera control signals, board sync outputs and other advanced settings. Parameter Descriptions The f ollowing table describes the CamExpert Advanced Control category of Sapera LT parameters. Acquisition server notes, if applicable, indicate if parameter availablility or supported values are dependent on the selected f rame grabber acquisition server and acquisition device.
  • Page 43 Time Integration CORACQ_PRM_TIME_INTEGRATE_METHOD When the Camera Control method is Time CORACQ_PRM_TIME_INTEGRATE_DELAY Integration, select and configure the control Method Setting CORACQ_PRM_TIME_INTEGRATE_PULSE0_DELAY method required. CORACQ_PRM_TIME_INTEGRATE_PULSE1_DELAY Click on the parameter field to open the CORACQ_PRM_TIME_INTEGRATE_PULSE0_DURATION configuration dialog. CORACQ_PRM_TIME_INTEGRATE_PULSE1_DURATION CORACQ_PRM_TIME_INTEGRATE_PULSE0_POLARITY CORACQ_PRM_TIME_INTEGRATE_PULSE1_POLARITY Camera Trigger When an asynchronous trigger pulse to a CORACQ_PRM_CAM_TRIGGER_METHOD Method Setting camera is required, select and configure the...

  • Page 44: External Trigger Category

    External Trigger Category The External category groups parameters f or configuring an external trigger f or controlling image acquisition. Parameter Descriptions The f ollowing table describes the CamExpert External Trigger category of Sapera LT parameters. Acquisition server notes, if applicable, indicate if parameter availablility or supported values are dependent on the selected f rame grabber acquisition server and acquisition device.
  • Page 45 Triggers and User Interface General Outputs 1 & 2 reserved for Strobe Outputs. Refer to User Interface GIOs Reservation for more information on using the Teledyne DALSA Device Manager tool to reserve GPIOs. External Trigger Minimum external trigger pulse duration (in µs), needed CORACQ_PRM_EXT_TRIGGER_DURATION...

  • Page 46: Image Buffer And Roi Category

    Image Buffer and ROI Category The Image Buf fer and ROI category groups parameters f or the conf iguring the image buffer f ormat, size and of fset settings, as well as image f lipping. Parameter Descriptions The f ollowing table describes the CamExpert Image Buffer and ROI category of Sapera LT parameters.
  • Page 47 Image Top Offset Number of lines to crop from the top of the CORACQ_PRM_CROP_TOP Note: image data is not scaled. acquisition image before transfer to the frame (in Lines) buffer. The maximum top offset is the active vertical height of the image source less one increment step.

  • Page 48: Using The Flat Field Correction Tool

    Sapera Classes and CamExpert will be available in Sapera LT 8.20, therefore contact Teledyne DALSA Technical Support f or any inquiry regarding this f eature. Note that this process requires a cluster map f ile def ining bad pixels, provided by the camera manufacturer.

  • Page 49: Verify A Bright Acquisition

    Indicates one or more “hot” pixels Average dark pixel value Important: In this example, the average pixel value f or the f rame is close to black. Also note that most sensors will show a much higher maximum pixel value due to one or more "hot pixels". The sensor specification accounts f or a small number of hot or stuck pixels (pixels that do not react to light over the f ull dynamic range specified f or that sensor).

  • Page 50: Flat Field Correction Calibration Procedure

    Minimum should not be black unless there is a “dead” pixel Maximum should not be peak white unless there is a “hot” pixel (i.e. 255 for 8-bit, 1023 for 10-bit) Average bright pixel value (bright gray but not white) Important: In this example, the average pixel value f or the f rame is bright gray. Also note that sensors may show a much higher maximum or a much lower minimum pixel value due to one or more "hot or dead pixels".

  • Page 51: Using Flat Field Correction

    • Setup the camera to capture a unif orm black image. Black paper with no illumination and the camera lens’ iris closed to minimum can provide such a black image. • Click on Acquire Black Image. The f lat f ield demo will grab a video f rame, analyze the pixel gray level spread, and present the statistics.

  • Page 52: Using The Bayer Filter Tool

    Using the Bayer Filter Tool CamExpert supports the use of Bayer Filter cameras by providing a tool to select the Bayer f ilter mosaic pattern and to perf orm an auto white balance. Color calibration can then be manually f ine tuned with RGB gain and gamma adjustments.

  • Page 53: Sapera Demo Applications

    Sapera Demo Applications Grab Demo Overview The Grab Demo program demonstrates the basic acquisition f unctions included in the Sapera library. The program either allows you to acquire images, in continuous or in one -time mode, while adjusting the acquisition parameters. The program code may be extracted f or use within your own application.

  • Page 54: Using The Grab Demo

    The demo program f irst displays the acquisition conf iguration menu. The f irst drop menu displayed permits selecting f rom any installed Sapera acquisition servers (installed Teledyne DALSA acquisition hardware using Sapera drivers). The second drop menu per mits selecting f rom the available input devices present on the selected server.

  • Page 55: Grab Demo Main Window

    Grab Demo Main Window The Grab Demo program provides basic acquisition control f or the selected f rame grabber. The loaded camera f ile (.ccf) defines the Frame buffer defaults. Figure 14: Grab Demo Main Window Ref er to the Sapera LT User's Manual (OC-SAPM-USER), in section "Demos and Examples – Acquiring with Grab Demo", f or more inf ormation on the Grab Demo and others provided with Sapera LT.

  • Page 56: Xtium2-Cl Mx4 Reference

    Xtium2-CL MX4 Reference Block Diagram SDR26 #1 Data Data & FVAL Grab Controls SerDes LVAL Receiver DVAL SPARE LVDS Drivers and Receiver Frame Buffer and UART #1 DMA table Memory (1 GB) Time Base SDR26 #2 Data FVAL Data & SerDes LVAL Grab Controls...

  • Page 57: Xtium2-Cl Flow Diagram

    Xtium2-CL Flow Diagram The f ollowing diagram represents the sequence in which the camera data acquired is processed through the Xtium2-CL. ACU-Plus Camera Link Image Cropper (Coarse) Front-End Buffer Color White-Balance FFC/FLC Conversion Gain (RGB (Bayer) Pixels) Image Filter Look Up Table 3x3 (Mono Horizontal Flip Pixels)

  • Page 58: Acquisition Timing

    Acquisition Timing DATA last first PCLK Pixel Clock Range: 20 MHz up to 85 MHz LVAL/FVAL setup time : Minimum 15ns LVAL Min/Max (Hsync) FVAL Min/Max (Vsync) Figure 17: Acquisition Timing The setup times for LVAL and FVAL are the same. Both must be high and stable before the rising ▪...

  • Page 59: Line Trigger Source Selection For Line Scan Applications

    Line Trigger Source Selection for Line scan Applications Line scan imaging applications require some f orm 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 shaf t encoder source composed of a single or dual phase signal (also known as a quadrature).

  • Page 60: Shaft Encoder Interface Timing

    Shaft Encoder Interface Timing Dual Balanced Shaft Encoder RS-422 Inputs: • J1: Internal I/O Signals Connector (26-pin SHF-113-01-L-D-RA), J5: External Signals Connector (Female DH60-27P) and J2: Internal I/O Signals Connector (40-pin TST-120-01- G-D) f or complete connector signal details. Web inspection systems with variable web speeds typically provide one or two synchronization signals f rom a web mounted encoder to coordinate trigger signals.

  • Page 61: Example Using Sequential Encoder Input

    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 brief ly travel backwards. The acquisition device must in those cases count the reverse steps and subtract the f orward steps such that only pulses af ter the reverse count reaches zero are considered.

  • Page 62: Virtual Frame Trigger For Line Scan Cameras

    Virtual Frame Trigger for Line Scan Cameras When using line scan cameras, a f rame buffer is allocated in host system memory to store captured video lines. To control when a video line is stored as the f irst line in this “virtual” f rame buf fer, an external f rame trigger signal is used.

  • Page 63: Synchronization Signals For Fixed Frame Length Acquisition

    Virtual Frame Trigger Shaft Encoder Camera Control LVAL Video Line 10 Lines n Lines Acquired 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 20: Synchronization Signals for a 10 Line Virtual Frame Synchronization Signals for Fixed Frame Length Acquisition A trigger event is only generated when a grab is active;...

  • Page 64: Synchronization Signals For Variable Frame Length Acquisition

    Grab Start (SapTransfer) called before trigger Grab Start Trigger (Active High) Frame Valid Grab Start (SapTransfer) called after trigger Grab Start Trigger event issued at grab start Trigger (Active High) Frame Valid Figure 23: Line scan, Fixed Frame, Level Trigger (Roll-Over to Next Frame) Synchronization Signals for Variable Frame Length Acquisition For variable length f rames, trigger ignored events are not issued (SapAcquisition::EventExternalTriggerIgnored);...
  • Page 65 CVI File (VIC) Parameters Used The VIC parameters listed below provide the control f unctionality f or virtual f rame trigger. Sapera applications load pre-configured CVI f iles or change VIC parameters during runtime. Note: Sapera camera file parameters are easily modified by using the CamExpert program.

  • Page 66: Sapera Acquisition Methods

    Sapera Acquisition Methods Sapera acquisition methods define the control and timing of the camera and f rame 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) •...

  • Page 67: Acquisition Events

    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 f ramework. Acquisition Events Acquisition events pertain to the acquisition module and provide f eedback on the image capture phase.

  • Page 68: Transfer Events

    Transfer Events Transfer events are related to the transf er module and provide f eedback on image transfer f rom onboard memory f rame buffers to PC memory f rame buffers. Event Description Start of Frame Start of Frame event generated when the first image pixel is transferred from on - board memory into PC memory.

  • Page 69: Trigger Signal Validity

    Trigger Signal Validity The ACU ignores external trigger signal noise with its programmable debounce control. Program the debounce parameter f or the minimum pulse duration considered as a valid external trigger pulse. For more inf ormation see Note 1: General Inputs / External Trigger Inputs Specif ications. Supported Transfer Cycling Methods The Xtium2-CL MX4 supports the f ollowing transfer modes, which are either synchronous or asynchronous.

  • Page 70: Frame Lost

    The f ollowing table describes the possible buffer states and resulting behavior: Trash Buffer Xtium2 On-Board Host Sapera Buffer Resulting Event (cycling mode Memory State State with trash) Empty buffer available Empty buffer available Normal acquisition events (at least 1) (at least 1) Empty buffer available Full...

  • Page 71: Output Lut Availability

    Output LUT Availability The f ollowing table def ines the supported output LUT (look up tables) f or the Xtium2-CL MX4. Note that unsupported modes are not listed. Number of Digital Output Pixel LUT Format Notes* Bits Format MONO 8 8-in, 8-out MONO 16 8-in, 16-out...

  • Page 72: Metadata: Theory Of Operation

    I/Os (f or example, Low, bit = 0 or High, bit = 1). ▪ reserved: 25 bytes reserved f or f uture usage. ▪ For a demo application showing this f eature, please contact Teledyne DALSA technical support. 70 • Xtium2-CL MX4 Reference Xtium2-CL MX4 User's Manual...

  • Page 73: Flat Field Correction: Theory Of Operation

    Flat Field Correction: Theory of Operation The f ollowing provides additional details on the Flat Field Correction and Flat Line Correction (FFC/FLC) implementation. Flat Field Correction Lists The Xtium2-CL MX4 supports defining more than one Flat Field Correction (FFC) / Flat Line Correction (FLC) data sets.

  • Page 74: Flat Field Correction Sets

    Flat Field Correction Sets The concept of sets allows a user to def ine multiple lists of FFC/FLC correction data. The FFC/FLC API allows users to allocate and pre-program those FFC/FLC sets. When acquiring images, the board driver will cycle through the FFC/FLC list of the selected set. During that operation, users can upload new FFC/FLC data to non-active sets without any ill ef fects.

  • Page 75: Xtium2-Cl Mx4 Supported Parameters

    Xtium2-CL MX4 Supported Parameters The tables below describe the Sapera capabilities supported by the Xtium2-CL MX4. Unless specif ied, each capability applies to all conf iguration modes and all acquisition modes. The inf ormation here is subject to change. The application needs to verif y capabilities.

  • Page 76: Camera Related Parameters

    Camera Related Parameters Parameter Values CORACQ_VAL_CHANNEL_SINGLE (0x1) CORACQ_PRM_CHANNEL CORACQ_VAL_CHANNEL_DUAL (0x2) CORACQ_PRM_FRAME CORACQ_VAL_FRAME_PROGRESSIVE (0x2) CORACQ_PRM_INTERFACE CORACQ_VAL_INTERFACE_DIGITAL (0x2) CORACQ_VAL_SCAN_AREA (0x1) CORACQ_PRM_SCAN CORACQ_VAL_SCAN_LINE (0x2) CORACQ_PRM_SIGNAL CORACQ_VAL_SIGNAL_DIFFERENTIAL (0x2) Base/Full Mono CORACQ_VAL_VIDEO_MONO (0x1) CORACQ_PRM_VIDEO 10T8B Mono / CORACQ_VAL_VIDEO_BAYER (0x10) 8T10B Mono Base Color RGB CORACQ_VAL_VIDEO_RGB (0x8) Medium Color Full Packed RGB 80B Packed RGB...
  • Page 77 Base/Full Mono min = 4 pixel, max = 65536 pixel, step = 1 pixel CORACQ_PRM_HACTIVE Base/Full Bayer 10T8B Mono min = 4 pixel, max = 6553 pixel, step = 1 pixel 10T8B Bayer 8T10B Mono min = 4 pixel, max = 4096 pixel, step = 1 pixel 8T10B Bayer Base Color RGB min = 4 pixel, max = 16384 pixel, step = 1 pixel...
  • Page 78 CORACQ_VAL_ACTIVE_LOW (0x1) CORACQ_PRM_LINE_TRIGGER_POLARITY CORACQ_VAL_ACTIVE_HIGH (0x2) min = 0 pixel CORACQ_PRM_LINE_TRIGGER_DELAY max = 85899345 pixel step = 1 pixel min = 0 pixel CORACQ_PRM_LINE_TRIGGER_DURATION max = 85899345 pixel step = 1 pixel Base Mono min = 1 tap, max = 3 taps, step = 1 tap CORACQ_PRM_TAPS Base Bayer Full Mono...

  • Page 79: External Line Trigger

    CORACQ_VAL_TAP_DIRECTION_LR (0x1) CORACQ_PRM_TAP_6_DIRECTION CORACQ_VAL_TAP_DIRECTION_RL (0x2) CORACQ_VAL_TAP_DIRECTION_UD (0x4) CORACQ_VAL_TAP_DIRECTION_DU (0x8) CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10) CORACQ_VAL_TAP_DIRECTION_FROM_MID (0x20) CORACQ_VAL_TAP_DIRECTION_FROM_BOT (0x40) CORACQ_VAL_TAP_DIRECTION_LR (0x1) CORACQ_PRM_TAP_7_DIRECTION CORACQ_VAL_TAP_DIRECTION_RL (0x2) CORACQ_VAL_TAP_DIRECTION_UD (0x4) CORACQ_VAL_TAP_DIRECTION_DU (0x8) CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10) CORACQ_VAL_TAP_DIRECTION_FROM_MID (0x20) CORACQ_VAL_TAP_DIRECTION_FROM_BOT (0x40) CORACQ_VAL_TAP_DIRECTION_LR (0x1) CORACQ_PRM_TAP_8_DIRECTION CORACQ_VAL_TAP_DIRECTION_RL (0x2) CORACQ_VAL_TAP_DIRECTION_UD (0x4) CORACQ_VAL_TAP_DIRECTION_DU (0x8) CORACQ_VAL_TAP_DIRECTION_FROM_TOP (0x10) CORACQ_VAL_TAP_DIRECTION_FROM_MID (0x20) CORACQ_VAL_TAP_DIRECTION_FROM_BOT (0x40) CORACQ_PRM_PIXEL_CLK_DETECTION...
  • Page 80 Base Mono CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1) CORACQ_PRM_CAMLINK_CONFIGURATION Base Bayer Full Mono CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1) Full Bayer CORACQ_VAL_CAMLINK_CONFIGURATION_MEDIUM (0x2) CORACQ_VAL_CAMLINK_CONFIGURATION_FULL (0x4) 10T8B Mono CORACQ_VAL_CAMLINK_CONFIGURATION_10TAPS_FORMAT2 (0x40) 10T8B Bayer 8T10B Mono CORACQ_VAL_CAMLINK_CONFIGURATION_8TAPS_10BITS (0x80) 8T10B Bayer Base Color RGB CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1) Medium Color CORACQ_VAL_CAMLINK_CONFIGURATION_BASE (0x1) CORACQ_VAL_CAMLINK_CONFIGURATION_MEDIUM (0x2) CORACQ_VAL_CAMLINK_CONFIGURATION_FULL_PACKED (0x100) Full Packed RGB CORACQ_VAL_CAMLINK_CONFIGURATION_FLAG_BGR (0x80000000)

  • Page 81: Vic Related Parameters

    VIC Related Parameters Parameter Values Base/Full Mono CAMSEL_MONO = from 0 to 0 CORACQ_PRM_CAMSEL 10T8B Mono 8T10B Mono Full Packed RGB CAMSEL_RGB = from 0 to 0 Full Packed RGBY Base/Full Bayer 80B Packed Bi-Color 10T8B Bayer 8T10B Bayer Base Color RGB Medium Color RGB 80B Packed RGB CORACQ_PRM_CROP_LEFT...
  • Page 82 TRUE CORACQ_PRM_TIME_INTEGRATE_ENABLE FALSE min = 1 µs CORACQ_PRM_TIME_INTEGRATE_DURATION max = 85899345 µs step = 1 µs TRUE CORACQ_PRM_CAM_TRIGGER_ENABLE FALSE CORACQ_VAL_OUTPUT_FORMAT_MONO8 CORACQ_PRM_OUTPUT_FORMAT Base/Full Mono CORACQ_VAL_OUTPUT_FORMAT_MONO16 CORACQ_VAL_OUTPUT_FORMAT_MONO8P2 CORACQ_VAL_OUTPUT_FORMAT_MONO8P3 CORACQ_VAL_OUTPUT_FORMAT_MONO8P4 CORACQ_VAL_OUTPUT_FORMAT_MONO16P2 CORACQ_VAL_OUTPUT_FORMAT_MONO16P4 CORACQ_VAL_OUTPUT_FORMAT_MONO8 10T8B CORACQ_VAL_OUTPUT_FORMAT_MONO16 8T10B CORACQ_VAL_OUTPUT_FORMAT_MONO16 Base/Full Bayer 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_YUY2...
  • Page 83 CORACQ_VAL_ACTIVE_LOW (0x1) CORACQ_PRM_EXT_TRIGGER_DETECTION CORACQ_VAL_ACTIVE_HIGH (0x2) CORACQ_VAL_RISING_EDGE (0x4) CORACQ_VAL_FALLING_EDGE (0x8) CORACQ_PRM_LUT_FORMAT Base/Full mono/10T8B Default = CORDATA_FORMAT_MONO8 8T10B Default = CORDATA_FORMAT_MONO16 Base Color RGB Default = CORDATA_FORMAT_COLORNI8 Medium Color RGB Base/Full Bayer Full Packed RGB 80B Packed RGB 80B Packed Bi-Color 10T8B Bayer 8T10B Bayer Default = CORDATA_FORMAT_COLORNI10 Full Packed RGBY...
  • Page 84 min = 1 frame CORACQ_PRM_EXT_TRIGGER_FRAME_COUNT max = 262142 frames step = 1 frame Note: Infinite not supported TRUE CORACQ_PRM_INT_FRAME_TRIGGER_ENABLE FALSE min = 1 milli-Hz CORACQ_PRM_INT_FRAME_TRIGGER_FREQ max = 41000000 milli-Hz step = 1 milli-Hz CORACQ_VAL_FRAME_LENGTH_FIX (0x1) CORACQ_PRM_FRAME_LENGTH CORACQ_VAL_FRAME_LENGTH_VARIABLE (0x2) CORACQ_PRM_FLIP Full Packed RGBY Not Available CORACQ_VAL_FLIP_OFF (0x00) All other modules...
  • Page 85 Base Color RGB CORACQ_PRM_WB_GAIN min = 100000, max = 900000, step = 1 Medium Color RGB Full Packed RGB Full Packed RGBY 80B Packed RGB 80B Packed Bi-Color Base/Full Bayer 10T8B Bayer 8T10B Bayer Base Color RGB CORACQ_PRM_WB_GAIN_RED min = 100000, max = 900000, step = 1 Medium Color RGB Full Packed RGB Full Packed RGBY...
  • Page 86 CORACQ_VAL_TIME_BASE_US (0x1) CORACQ_PRM_TIME_STAMP_BASE 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 CORACQ_PRM_BOARD_SYNC_OUTPUT1_SOURCE_STR [1] = External Frame Trigger [2] = Reserved [3] = CC1 [4] = CC2 [5] = CC3 [6] = CC4 [7] = Ext Trigger Ignore Region [8] = Shaft Encoder Before Mult/Drop [9] = Shaft Encoder After Mult/Drop [10] = Internal Line Trigger...

  • Page 87: Acq Related Parameters

    ACQ Related Parameters Parameter Values Base Mono Camera Link Base Mono CORACQ_PRM_LABEL Base Color RGB Camera Link Base Color RGB Base Bayer Camera Link Base Bayer Full mono Camera Link Full Mono Medium Color RGB Camera Link Medium Color RGB Full Packed RGB Camera Link Full Packed RGB Full Bayer...
  • Page 88 CORACQ_CAP_FLAT_FIELD_GAIN 8-bit Mono min = 0 max = 255 step = 1 10-bit Mono min = 0 max = 4095 step = 1 12-bit Mono min = 0 max = 16383 step = 1 14-bit Mono min = 0 max = 65535 step = 1 16-bit Mono Not Available...

  • Page 89: Transfer Related Capabilities

    Transfer Related Capabilities Capability Values CORXFER_CAP_NB_INT_BUFFERS CORXFER_VAL_NB_INT_BUFFERS_AUTO (0x2) CORXFER_CAP_MAX_XFER_SIZE 4294967040 Bytes CORXFER_CAP_MAX_FRAME_COUNT 16777215 Frames CORXFER_CAP_COUNTER_STAMP_AVAILABLE FALSE CORXFER_CAP_TRANSFER_SYNC CORXFER_VAL_TRANSFER_SYNC_SUPPORTED (0x1) Transfer Related Parameters Parameter Values CORXFER_PRM_EVENT_TYPE CORXFER_VAL_EVENT_TYPE_START_OF_FRAME CORXFER_VAL_EVENT_TYPE_END_OF_FRAME CORXFER_PRM_EVENT_TYPE_EX CORXFER_VAL_EVENT_TYPE_END_OF_TRANSFER CORXFER_VAL_EVENT_TYPE_END_OF_LINE CORXFER_VAL_EVENT_TYPE_END_OF_NLINES CORXFER_VAL_START_MODE_ASYNCHRONOUS (0x0) CORXFER_PRM_START_MODE 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_PRM_CYCLE_MODE CORXFER_VAL_CYCLE_MODE_SYNCHRONOUS_WITH_TRASH (0x2)

  • Page 90: General Outputs #1: Related Capabilities (Gio Module #0)

    General Outputs #1: Related Capabilities (GIO Module #0) These are the User Interf ace Outputs available on connector J1, J2 and J5. Capability Values CORGIO_CAP_IO_COUNT 9 I/Os CORGIO_CAP_DIR_OUTPUT 0x1ff CORGIO_CAP_DIR_TRISTATE 0x1ff CORGIO_CAP_EVENT_TYPE Not Available CORGIO_CAP_READ_ONLY 0x03 (* depends on strobe outputs reserved for acquisition device) General Outputs #1: Related Parameters (GIO Module #0) Parameter Values...

  • Page 91: Bidirectional General I/Os: Related Capabilities (Gio Module #2)

    Bidirectional General I/Os: Related Capabilities (GIO Module These are the Open Interf ace I/Os available on connector J3. Capability Values CORGIO_CAP_IO_COUNT 8 I/Os CORGIO_CAP_DIR_OUTPUT 0xff CORGIO_CAP_DIR_TRISTATE 0xff CORGIO_CAP_EVENT_TYPE Not Available CORGIO_CAP_READ_ONLY 0x03 (* depends on board syncs reserved for acquisition device) Bidirectional General I/Os: Related Parameters (GIO Module Parameter Values...

  • Page 92: Sapera Servers & Resources

    Sapera Servers & Resources Servers and Resources The f ollowing table describes services and resources available f or the Xtium2-CL MX4 board. Servers Resources Name Type Name Index Description Xtium2- Acquisition Camera Link Full Mono Base, Medium and Full configuration, CL_MX4_1 Monochrome Camera (Full firmware)

  • Page 93: Technical Specifications

    Technical Specifications Xtium2-CL MX4 Board Specifications Digital Video Input & Controls Input Type Camera Link Specifications Rev 2.1 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 Common Pixel Formats Camera Link tap configuration:...
  • Page 94 Serial Port Supports communication speeds from 9600 to 921600 bps Controls 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 &...

  • Page 95: Host System Requirements

    Host System Requirements Xtium2-CL MX4 Dimensions Approximately 6.5 in. (14 cm) wide by 4 in. (10 cm) high General System Requirements for the Xtium2-CL MX4 • PCI Express Gen3 x4 slot compatible; (will work in Gen1 or Gen 2 x4 slot with reduced bandwidth to host) •...

  • Page 96: Declarations Of Conformity

    This equipment is intended to be a component of a larger industrial system. EU and UKCA Declaration of Conformity Teledyne DALSA declares that this product complies with applicable standards and regulations. Changes or modif ications not expressly approved by the party responsible f or compliance could void the user's authority to operate the equipment.

  • Page 97: Connector And Switch Locations

    Connector and Switch Locations Xtium2-CL MX4 Board Layout Drawing Figure 26: Board Layout Connector / LED Description List The f ollowing table lists components on the Xtium2-CL MX4 board. Detailed inf ormation concerning the connectors/LEDs follows this summary table. Location Description Location Description...

  • Page 98: Connector And Switch Specifications

    Full camera, connect the second camera connector to CL-2. Note: If the camera is powered by the Xtium2-CL MX4, ref er to J4: Power Connector f or power connections. Contact Teledyne DALSA or browse our web site https://www.teledynedalsa.com/en/products/imaging/ f or inf ormation on Xtium2-CL MX4 supported cameras.

  • Page 99: Status Led Functional Description

    Status LED Functional Description S Boot-up/PCIe status LED Color State Description Solid FPGA firmware not loaded Green Solid Normal FPGA firmware loaded, Gen3 speed, link width x4 Green Flashing Normal FPGA firmware loaded, Gen1/Gen2 speed, link width x4 Solid Normal FPGA firmware loaded, Gen3 speed, link width not x4 Flashing Normal FPGA firmware loaded, Gen1/Gen2 speed, link width not x4 Blue...
  • Page 100 CL-1: Camera Link Connector 1 Name Pin # Type Description BASE_X0- Input Neg. Base Data 0 BASE_X0+ Input Pos. Base Data 0 BASE_X1- Input Neg. Base Data 1 BASE_X1+ Input Pos. Base Data 1 BASE_X2- Input Neg. Base Data 2 BASE_X2+ Input Pos.

  • Page 101: Cl-2: Camera Link Connector 2

    CL-2: Camera Link Connector 2 Medium and Full Camera Link sources require cables connected to both CL-1 and CL-2. Name Pin # Type Description MEDIUM _X0- Input Neg. Medium Data 0 MEDIUM _X0+ Input Pos. Medium Data 0 MEDIUM _X1- Input Neg.

  • Page 102: Camera Link Camera Control Signal Overview

    Camera Link Camera Control Signal Overview Four LVDS pairs are f or general-purpose camera control, defined as camera inputs / f rame grabber outputs by the Camera Link Base camera specification. These controls are on CL-1 connector and CL-2 connector when used as a 2 base Camera Link input.

  • Page 103: J5: External Signals Connector (Female Dh60-27P)

    J5: External Signals Connector (Female DH60-27P) Warning: J1, J2 and J5 have the same signal assignments. Signals are routed to all 3 connectors directly from their internal circuitry. Therefore never connect J1 , J2 and/or J5 to external devices at the same time. See DH40-27S Cable to Blunt End (OR-YXCC-27BE2M1, Rev B1) and Cable assemblies for I/O connector J1 for available cables.

  • Page 104: J2: Internal I/O Signals Connector (40-Pin Tst-120-01-G-D)

    J2: Internal I/O Signals Connector (40-pin TST-120-01-G-D) Warning: J1, J2 and J5 have the same signal assignments. Signals are routed to both connectors directly from their internal circuitry. Therefore, never connect J1, J2 and/or J5 to external devices at the same time. Table 7: 40-pin TST-120-01-G-D Connector Signals Description Pin #...

  • Page 105: Note 1: General Inputs / External Trigger Inputs Specifications

    Note 1: General Inputs / External Trigger Inputs Specifications Each of the f our General Inputs are opto-coupled and able to connect to dif f erential or single ended source signals. General Input 1 to 4 can also act as External Trigger Inputs. See “Board Inf ormation”...
  • Page 106 s 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.

  • Page 107: Block Diagram: Connecting External Drivers To General Inputs

    Block Diagram: Connecting External Drivers to General Inputs Using J1/J5 External Signals Xtium2-CL MX4 User Signal Ground V (+) Ground Shaft Encoder RS-422 A (-) Shaft Encoder RS-422 / TTL A (+) Differential Ground Driver Shaft Encoder RS-422 B (-) Shaft Encoder RS-422 / TTL B (+) General Input 1 / Trigger 1 (-) V (+)
  • Page 108 Using J2 External Signals Xtium2-CL MX4 Power Output (5 Volts) User Signal Ground V (+) Power Output (12 Volts) Ground Ground Differential Shaft Encoder RS-422 / TTL A (+) Driver Shaft Encoder RS-422 A (-) : Shaft Encoder RS-422 / TTL B (+) Shaft Encoder RS-422 B (-) Ground 10 :...

  • Page 109: External Driver Electrical Requirements

    External Driver Electrical Requirements The Xtium2-CL allows user selected (software programmable) input switching points to support dif f erential (RS-422) input signals and single ended (TTL, 12V, 24V) input signals. The f ollowing table def ines the external signal voltage requirements f rom the driver circuits connected to the Xtium2 external inputs.

  • Page 110: Note 2: General Outputs /Strobe Output Specifications

    Note 2: General Outputs /Strobe Output Specifications Each of the 9 General Outputs are TTL (3.3V) compatible. All of the General Outputs can also f unction as Strobe Outputs controlled by Sapera strobe control f unctions. See “Board Inf ormation” user settings.

  • Page 111: Block Diagram: Connecting External Receivers To The General Outputs

    Block Diagram: Connecting External Receivers to the General Outputs Using J1/J5 To External Devices Xtium2-CL MX4 User Signal Ground Compatible Receiver Ground Shaft Encoder RS-422 A (-) Shaft Encoder RS-422 / TTL A (+) Compatible Ground Receiver Shaft Encoder RS-422 B (-) Shaft Encoder RS-422 / TTL B (+) General Input 1 / Trigger 1 (-) General Input 1 / Trigger 1 (+)

  • Page 112: External Receiver Electrical Requirements

    Using J2 To External Devices Xtium2-CL MX4 Power Output (5 Volts) User Signal Ground Compatible Power Output (12 Volts) Receiver Ground Ground Shaft Encoder RS-422 / TTL A (+) Shaft Encoder RS-422 A (-) Compatible : Shaft Encoder RS-422 / TTL B (+) Receiver Shaft Encoder RS-422 B (-) Ground...

  • Page 113: Note 3: Rs-422/Ttl Shaft Encoder Input Specifications

    Note 3: RS-422/TTL Shaft Encoder Input Specifications Dual Quadrature Shaft Encoder Inputs (phase A and phase B) connect to dif f erential signals (RS-422), single ended signals, or TTL signals. The f igure below shows the simplif ied representation of these inputs. WARNING: When connecting shaft encoders to Xtium2-CL MX4, make sure to connect a common ground between the shaf t encoder and the f rame grabber.
  • Page 114 • RS-422 dif f erential line receiver used is am26lv32. • Maximum input signal f requency is 5 MHz. • The Xtium2-CL provides ESD f iltering on-board. • See Line Trigger Source Selection f or Line scan Applications f or more inf ormation. •...

  • Page 115: Note 3.1: Interfacing To An Rs-422 Driver Output

    Note 3.1: Interfacing to an RS-422 Driver Output Using J1/J5 External Signals Xtium2-CL MX4 V (+) Ground RS-422 Shaft Encoder RS-422 A (-) Compatible Shaft Encoder RS-422 / TTL A (+) Driver Ground Shaft Encoder RS-422 B (-) Shaft Encoder RS-422/ TTL B (+) V (+) General Input 1 / Trigger 1 (-) General Input 1 / Trigger 1 (+)
  • Page 116 Using J2 External Signals Xtium2-CL MX4 Power Output (5 Volts) User Signal Ground V (+) Power Output (12 Volts) Ground Ground RS-422 Shaft Encoder RS-422 / TTL A (+) Compatible Shaft Encoder RS-422 A (-) Driver : Shaft Encoder RS-422 / TTL B (+) Shaft Encoder RS-422 B (-) Ground V (+)

  • Page 117: Note 3.2: Interfacing To A Line Driver (Also Called Open Emitter) Output

    Note 3.2: Interfacing to a Line Driver (also called Open Emitter) Output Interfacing Line Driver/Open Emitter Output to RS-422 Inputs Generic Line Driver/Open Emitter Output RS-422 (+) input 100 ohm RS-422 (-) input Pull-down resistor needed if it is not already present in the Shaft Encoder.

  • Page 118: Note 3.3: Interfacing To An Open Collector Output

    Note 3.3: Interfacing to an Open Collector Output Interfacing Open Collector Output to RS-422 Inputs Pull-up resistor needed if it is not already present in the Shaft Encoder. Value depends on the characteristics of the Shaft Encoder Output. Generic Open Collector Output RS-422 (+) input 100 ohm RS-422 (-) input...

  • Page 119: Note 3.5: Interfacing To A Ttl Using A Bias Voltage

    Note 3.5: Interfacing to a TTL using a Bias Voltage Interfacing TTL Output to RS-422 Inputs via a Line Buffer/Driver TTL signal source & Buffer Driver (example: 74ACT244) RS-422 / TTL (+) input 100 ohm RS-422 (-) input Bias Voltage Frame Grabber System FG/system GND Figure 42: Interfacing TTL to RS-422 Shaft Encoder Inputs using a Bias Voltage...

  • Page 120: J3: Multi-Board Sync / Bi-Directional General I/Os

    3 or 4 boards). Warning: Multi-Board Sync / Bi-directional General I/Os are only for use with Teledyne DALSA frame grabbers within the same PC, otherwise electrical damage to boards can occur. Configuration via Sapera Application Programming Sync Master Board Software Setup: Choose one Xtium2 as “Sync Master”. The Sapera ▪...

  • Page 121: Configuration Via Sapera Camexpert

    Configuration via Sapera CamExpert Start the f irst instance of CamExpert and select one installed Xtium2 board to be the sync ▪ master. As shown in the f ollowing image, this board is conf igured to use an external trigger on input #1.

  • Page 122: J4: Power Connector

    The Sync Slave Xtium2 board is conf igured to receive its trigger on the board sync signal. As ▪ an example the f ollowing image shows the Xtium2 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 f or ▪...

  • Page 123: Cables & Accessories

    Cables & Accessories The f ollowing 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 f t.) blunt end cable to mate to Xtium2 external connector J3.

  • Page 124: Dh40-27S Connector Kit For Custom Wiring

    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, f or clients interested in assembling their own custom I/O cable. Order part number “OR-YXCC-H270000”, (package as shown below).

  • Page 125: Cable Assemblies For I/O Connector J1

    Cable assemblies for I/O connector J1 Flat ribbon cables f or connecting to J1 can be purchased f rom Teledyne DALSA or f rom 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 f ollowing picture.

  • Page 126: Cable Assemblies For I/O Connector J2

    Cable assemblies for I/O connector J2 Flat ribbon cables f or connecting J2 to a DB37 bracket can be purchased from Teledyne DALSA or f rom third party suppliers. External Signals Connector Bracket Assembly The External Signals bracket (OC-X4CC-IOCAB) provides a simple way to bring out the signals f rom the External Signals Connector J2 to a bracket mounted DB37.
  • Page 127 Strobe 5 / General Output 5 Strobe 6 / General Output 6 Strobe 7 / General Output 7 Strobe 8 / General Output 8 Ground Ground External Trigger Input 1/General Input 1 (+) External Trigger Input 1/General Input 1 (-) External Trigger Input 2/General Input 2 (+) External Trigger Input 2/General Input 2 (-) External Trigger Input 3/General Input 3 (+)

  • Page 128: Board Sync Cable Assembly Or-Yxcc-Bsync40

    Board Sync Cable Assembly OR-YXCC-BSYNC40 This cable connects 3 to 4 Xtium2 boards f or the board sync function as described in section. For a shorter 2 board cable, order cable assembly OR-YXCC-BSYNC20. For a third party source of cables, see http://cloud.samtec.com/catalog_english/FFSD.PDF. Figure 48: Photo of cable OR-YXCC-BSYNC40 126 •...

  • Page 129: Power Cable Assembly Or-Yxcc-Pwry00

    2 standard 4-pin large power connectors to a 6-pin power connector. Figure 49: Photo of cable assembly OR-YXCC-PWRY00 This is an industry standard adapter cable which can be purchased f rom Teledyne DALSA. Xtium2-CL MX4 User's Manual Declarations of Conformity • 127...

  • Page 130: Camera Link Interface

    Camera Link Interface Camera Link Overview Camera Link is a communication interface f or vision applications developed as an extension of National Semiconductor's Channel Link technology. The advantages of the Camera Link interf ace are that it provides a standard digital camera connection specification, a standard data communication protocol, and simpler cabling between camera and f rame grabber.

  • Page 131: Camera Signal Summary

    Camera Control 2 (CC2) • Camera Control 3 (CC3) • Camera Control 4 (CC4) Note: The Xtium2-CL MX4 by def ault implements the control lines as f ollows, (using Teledyne DALSA terminology): • (CC1) EXYNC • (CC2) PRIN • (CC3) FORWARD •...

  • Page 132: Camera Link Cable Manufacturer Contact Information

    Camera Link Cable Manufacturer Contact Information For additional inf ormation on Camera Link cables and their specif ications, visit the f ollowing web sites: For Information contact: Alysium-Tech GmbH Andernacher Strasse 31b (see their website for worldwide offices) 90411 Nuremberg Phone: +49 [0] 911 93 78 78 0 Fax: +49 [0] 911 93 78 78 93 https://www.alysium.com/...

  • Page 133: Appendix A: Silent Installation

    Both Sapera LT and the Xtium2-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 f ollowing installation mode descriptions apply to both Sapera and the hardware driver.

  • Page 134: Running A Silent Mode Installation

    Note: On Windows 7, 8 and 10, the Windows Security dialog box will appear unless one has already notif ied Windows to ‘Always trust software f rom “Teledyne DALSA Inc.” during a previous installation of a driver.

  • Page 135: Silent Mode Installation Return Code

    Silent Mode Installation Return Code A silent mode installation creates a f ile “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 f ile “setup.log”...

  • Page 136: Custom Driver Installation Using Install.ini

    If a standard Serial COM port is required f or any board, use the Sapera Configuration tool (see ▪ COM Port Assignment). When each board setup is complete, using the Teledyne DALSA Device Manager tool, click on ▪ the Save Conf ig File button. This will create the “install.ini” f ile.

  • Page 137: Appendix B: Troubleshooting Installation Problems

    Installation Problems Overview The Xtium2-CL MX4 (and the Xtium2 f amily 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 verif y to determine the problem or the checks to make before contacting Teledyne DALSA Technical Support.

  • Page 138: Possible Installation Problems

    Sapera and board drivers are running. See Sapera and Hardware Windows Drivers f or details. In addition, Teledyne DALSA technical support will ask f or the log f ile of messages by Teledyne DALSA drivers. Follow the instructions describe in Teledyne DALSA Log Viewer.

  • Page 139: Troubleshooting Procedures

    Troubleshooting Procedures The f ollowing sections provide inf ormation and solutions to possible Xtium2-CL MX4 installation and f unctional problems. The previous section of this manual summarizes these topics. Diagnostic Tool Overview The Xtium2-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 identif ying problems.

  • Page 140: Diagnostic Tool Self Test Window

    Diagnostic Tool Self Test Window Click the Start button to initiate the board memory self test sequence. A healthy boar d will pass all memory test patterns. Figure 52: Diagnostic Tool Self Test Window 138 • Appendix B: Troubleshooting Installation Problems Xtium2-CL MX4 User's Manual...

  • Page 141: Diagnostic Tool Live Monitoring Window

    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.

  • Page 142: Checking For Pci Bus Conflicts

    As shown in the f ollowing screen image, use the f irst 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 f or each system unless systems are setup identically). Click on the Diagnostic button to view an analysis of the system PCI conf iguration space.
  • Page 143 A f ile named ‘pcidiag.txt’ is created (in the Sapera\bin directory) with a dump of the PCI conf iguration registers. Email this f ile when requested by the Teledyne DALSA Technical Support group along with a f ull description of your computer.

  • Page 144: Windows Device Manager

    BSOD (blue screen) Following a Board Reset Teledyne DALSA engineering has identif ied cases where a PC will f alsely report a hardware malf unction when the Xtium2-CL MX4 board is reset. The symptoms will be a Windows blue screen or PC that f reezes f ollowing a board reset.

  • Page 145: Sapera And Hardware Windows Drivers

    CorSerial Sapera Serial Port manager Kernel Driver Teledyne DALSA Technical Support may request that you check the status of these drivers as part of the troubleshooting process. Recovering from a Firmware Update Error This procedure is required if any f ailure occurred while updating the Xtium2-CL MX4 f irmware on installation or during a manual f irmware upgrade.

  • Page 146: Driver Information Via The Device Manager Program

    Xtium2-CL MX4 (described elsewhere in this manual). Execute the program via the Windows Start Menu shortcut Start • Programs • Teledyne DALSA • Xtium2-CL MX4 Device Driver • Device Manager. If the Device Manager Program does not run, it will exit with a board was not f ound message.

  • Page 147: Teledyne Dalsa Log Viewer

    Teledyne DALSA • Sapera LT • Tools • Log Viewer. The Log Viewer lists inf ormation about the installed Teledyne DALSA drivers. Click on File • Save and you will be prompted f or a text f ile name to save the Log Viewer contents. Email this text f ile to Teledyne DALSA Technical Support when requested or as part of your initial contact email.

  • Page 148: Symptoms: Camexpert Detects No Boards

    If CamExpert should have detected an installed board f rame 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 sof tware installation problem. •...

  • Page 149: Symptoms: Card Grabs Black

    Symptoms: Card grabs black You are able to use Sapera CamExpert, the displayed f rame 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.

  • Page 150: Symptoms: Card Acquisition Bandwidth Is Less Than Expected

    Symptoms: Card acquisition bandwidth is less than expected The Xtium2-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 transf ers.

  • Page 151: Contact Information

    Sales Information Visit our web site: www.teledynedalsa.com Email: info@teledynedalsa.com Canadian Sales Teledyne DALSA — Head office Teledyne DALSA — Montreal office 605 McMurray Road 880 Rue McCaffrey Waterloo, Ontario, Canada, N2V 2E9 Saint-Laurent, Quebec, Canada, H4T 2C7 Tel: 519 886 6000...

Table of Contents