Coaxlink Driver 4.3.1 Release Notes -...

Release NotesCoaxlink Driver 4.3.1

© EURESYS s.a. 2015 - Document version 4.3.439 built on 2015-07-17

2 Coaxlink Driver 4.3.1 Release Notes Disclaimer

EURESYS s.a. shall retain all property rights, title and interest of the documentation of the hardware and the software,and of the trademarks of EURESYS s.a. All the names of companies and products mentioned in the documentationmay be the trademarks of their respective owners. The licensing, use, leasing, loaning, translation, reproduction,copying or modification of the hardware or the software, brands or documentation of EURESYS s.a. contained inthis book, is not allowed without prior notice. EURESYS s.a. may modify the product specification or change theinformation given in this documentation at any time, at its discretion, and without prior notice. EURESYS s.a. shallnot be liable for any loss of or damage to revenues, profits, goodwill, data, information systems or other special,incidental, indirect, consequential or punitive damages of any kind arising in connection with the use of the hardwareor the software of EURESYS s.a. or resulting of omissions or errors in this documentation.

3Contents Coaxlink Driver 4.3.1 Release Notes

Contents

Introduction....................................................................................................................................................... 4Supported Products..................................................................................................................................................4Supported Product & Firmware Combinations........................................................................................................ 5Supported Operating Systems................................................................................................................................. 6Supported Development Tools.................................................................................................................................6Supported Memento Versions..................................................................................................................................6Software Tools..........................................................................................................................................................7

What's New?.....................................................................................................................................................8Added Product..........................................................................................................................................................8Added Firmware....................................................................................................................................................... 8Firmware Update...................................................................................................................................................... 9Added/Improved Features...................................................................................................................................... 10Solved Issues......................................................................................................................................................... 18Changes..................................................................................................................................................................20

Known Issues................................................................................................................................................21Deviations from the CoaXPress specification........................................................................................................21Deviations from the GenTL specification...............................................................................................................22Deviations from the PCIe 3.0 specification............................................................................................................23

4 Coaxlink Driver 4.3.1 Release Notes Introduction

Introduction

Supported Products

Product Code & Denomination Description Icon

PC1630 – Coaxlink Mono CXP-6 DIN 1 / 4-lane PCIe Gen2 CoaXPress frame grabber Mono

PC1631 – Coaxlink Duo CXP-6 DIN 2 / 4-lane PCIe Gen2 CoaXPress frame grabber Duo

PC1632 – Coaxlink Quad CXP-6 DIN 4 / 4-lane PCIe Gen2 CoaXPress frame grabber Quad

PC1633 – Coaxlink Quad G3 CXP-6 DIN 4 / 4-lane PCIe Gen3 CoaXPress frame grabber Quad G3

Note: Icons are used in this document for tagging product-specific content.

5Introduction Coaxlink Driver 4.3.1 Release Notes

Supported Product & Firmware Combinations

Coaxlink Driver 4.3.1

Target Product FirmwareVariant

Description Icon

PC1630 – Coaxlink Mono 1-camera One 1-connection area-scan camera 1-cameraMono

1-camera One 1- or 2-connection area-scan camera 1-cameraDuo

PC1631 – Coaxlink Duo

2-camera Two 1-connection area-scan cameras 2-cameraDuo

1-camera One 1- or 2- or 4-connection area-scan camera 1-cameraQuad

2-camera Two 1- or 2-connection area-scan cameras 2-cameraQuad

PC1632 – Coaxlink Quad

1-line-scan One 1- or 2- or 4-connection line-scan camera 1-line-scanQuad

1-camera One 1- or 2- or 4-connection area-scan camera 1-cameraQuad G3

2-camera Two 1- or 2-connection area-scan cameras 2-cameraQuad G3

4-camera Four 1-connection area-scan cameras 4-cameraQuad G3

1-line-scan One 1- or 2- or 4-connection line-scan camera 1-line-scanQuad G3

PC1633 – Coaxlink Quad G3

2-line-scan Two 1- or 2-connection line-scan cameras 2-line-scanQuad G3

Note: Icons are used in this document for tagging product-firmware-variant-specific content.

6 Coaxlink Driver 4.3.1 Release Notes Introduction

Supported Operating Systems

Windows

OS Version Additional Information

x86 (32-bit)Microsoft Windows 7

x86-64 (64-bit)

Service Pack 1

x86 (32-bit)Microsoft Windows 8

x86-64 (64-bit)

-

Linux

The Coaxlink Driver is designed to be distribution-independent on x86 and x64 platforms. It is expected to work witha wide range of distributions.This release has been validated with the following distribution(s):

OS Version Additional Information

x86 (32-bit)Linux distribution Ubuntu 14.04

x86-64 (64-bit)

Kernel Version 3.13

Supported Development Tools

The Coaxlink driver is supplied as GenICam GenTL producer libraries (coaxlink.cti):

An x86 dynamic library designed to be used with ISO-compliant C/C++ compilers for the development of x86applications.An x86_64 dynamic library designed to be used with ISO-compliant C/C++ compilers for the development ofx86_64 applications.A .NET assembly designed to be used with development environments compatible with .NET frameworks version2.0 or higher.

The Coaxlink cards should be usable with any development tool that supports at least one of these interfaces.

Supported Memento Versions

Memento Version 4.0 or later is required when using Coaxlink Driver version 4.0 or later.

7Introduction Coaxlink Driver 4.3.1 Release Notes

Software Tools

The following software tools are delivered together with the Coaxlink Driver:

Tool Name Tool Description

Coaxlink Firmware Manager Command-line tool for installing or upgrading the firmware embedded on theCoaxlink cards.

GenICam Browser (64-bit) 64-bit version of the GUI tool giving access to all the GenICam features exposed bythe GenTL Producer(s) in your system

GenICam Browser 32-bit version of the GenICam browser

GenTL Console (64-bit) 64-bit version of the command-line tool giving access to all the functions andcommands exposed by the Euresys GenTL Producer

GenTL Console 32-bit version of the GenTL Console

8 Coaxlink Driver 4.3.1 Release Notes What's New?

What's New?

Added Product

There are no addition to the list of supported products with this release.

Version 4.0

Product Code & Denomination Description

PC1633 – Coaxlink Quad G3 CXP-6 DIN 4 / 4-lane PCIe Gen3 CoaXPress frame grabber

Added Firmware

Version 4.3.1

Target Product Firmware Denomination Description

PC1633 – Coaxlink Quad G3 2-line-scan Two 1- or 2-connection line-scan cameras

Version 4.2


PC1632 – Coaxlink Quad 2-camera 2 cameras having 1 or 2 connections

PC1633 – Coaxlink Quad G3 2-camera 2 cameras having 1 or 2 connections

Version 4.1


PC1632 – Coaxlink Quad 1-line-scan One 1- or 2- or 4-connection line-scan camera

PC1633 – Coaxlink Quad G3 1-line-scan One 1- or 2- or 4-connection line-scan camera

9What's New? Coaxlink Driver 4.3.1 Release Notes

Version 4.0


PC1633 – Coaxlink Quad G3 1-camera 1 camera having 1, 2 or 4 connections

PC1633 – Coaxlink Quad G3 4-camera 4 cameras having 1 connection

Firmware Update

It is required to apply the firmware update procedure prior to using this Coaxlink Driver.

Note: Older firmware will be rejected by the driver (the only operation available will be a firmware upgrade)

The following table indicates the minimal required firmware version for every available product/firmware variantcombination:

Version 4.3.1

Product / Firmware Variant Combinations Min. Firmware Version Number

1-cameraMono

1-cameraDuo

1-cameraQuad

1-cameraQuad G3

173

2-cameraDuo

2-cameraQuad

2-cameraQuad G3

173

4-cameraQuad G3

173

1-line-scanQuad

1-line-scanQuad G3

173

2-line-scanQuad G3

173


Added/Improved Features

Version 4.3.1 – All firmware variants

EGrabber Application Programming Interface

Feature Name Feature Description

Methods Added resetBufferQueue method

Sample Programs Added "grabn-callbacks" and "events-st-all"

Documentation Improved documentation in header files and sample programs

GenICam Browser


GenAPI scripts Added the possibility to run Euresys GenApi scripts

Status bar Show frame rate, line rate and data rate in image window status bar

Operation logging Improved logging of operations performed

Configuration script Improved coaxlink://configurator script

Memento traces


Camera Detection Decode new traces from FPGA ("Line-scan camera detected")

gentl.exe


Report "report" command now gathers more information about Windows systems (msinfo32, powersaving modes)


Version 4.3 – All firmware variants

Coaxlink Hardware Custom Event Signaling and Counting


Event Sources Large set of Coaxlink hardware event sources:

Interface Module event sources:

All I/O Toolbox eventsCRC errors on each CoaXPress connector

Device Module event sources:

CIC Camera Trigger output signal transition (rising and/or falling)CIC Strobe output signal transition (rising and/or falling)CIC Trigger inputCIC internal events (AllowNextCycle, DiscardedTrigger, PendingTrigger)CoaXPress Host to Device Trigger message acknowledgeCoaXPress Host to Device Trigger message resend

Data Stream Module event sources:

Start of camera readoutEnd of camera readoutStart of scanEnd of scanRejected FrameRejected Scan

Notification control Event notification can be enabled/disabled for each event source

Time-stamp Every event is time-stamped with 1 microsecond accuracy using a system-wide unified timebase (same as Memento)

Event Counters 32-bit event counter on each event source.

Counter Control Counters are individually readable and resettable through GenApi

Notification context Every notification includes three user-configurable 32-bit context words. Possible contextincludes:

Logical state of System I/O linesCount value of any event source belonging to the same branch of the GenTL hierarchy


Application Programming Interface


ImageGetPixelFormat Added ImageGetPixelFormat function to coaxlink.cti

GenTL C++ class Added missing functions devGetInfo, dsGetInfo...

EGrabber C++ Class Added EGrabber C++ Class (see include/EGrabber.h)

The EGrabber Class is a set of C++ header files providing an easy-to-use applicationprogramming interface for Coaxlink products.

Main objects:

EGrabber

GenTL

SharedGenTL

Main methods:

start, stoprunScript

memento

Various event management methods

RGBConverter C++ class Added RGBConverter C++ class (see include/RGBConverter.h)

Custom Events Notification Added notification of custom events:

EVENT_CUSTOM_IO_TOOLBOX for I/O Toolbox eventsEVENT_CUSTOM_CIC for Camera and Illumination Controller eventsEVENT_CUSTOM_DATASTREAM for data stream eventsEVENT_CUSTOM_CXP_INTERFACE for CoaXPress events

Custom Events Info Added custom info commands for custom events:

EVENT_DATA_CUSTOM_TIMESTAMPEVENT_DATA_CUSTOM_CONTEXT_1EVENT_DATA_CUSTOM_CONTEXT_2EVENT_DATA_CUSTOM_CONTEXT_3

Custom Events Time Stamp Added BUFFER_INFO_CUSTOM_EVENT_TIMESTAMP toBUFFER_INFO_CUSTOM_CMD_LIST

Event Control Features Added EventControl GenICam features category to interface, device,and data stream modules: EventSelector, EventNotification,EventNotificationContext1,EventNotificationContext2,EventNotificationContext3, EventCount, EventCountReset

Euresys GenApi Script Added documentation (see scripts/doc)

gentl.exe


event command Added "event" command to show event notifications


Sample Programs


EGrabber collection Added new collection of EGrabber sample programs

Image Converters Use ImageConvert function to perform image conversions if required

Memento Traces


Rejected frame error Decode new traces from FPGA ("Rejected frame" error)

FPGA traces Decode new "Received a CXP packet with unexpected tag" traces from FPGA

FPGA traces Improved "Received a CXP packet with unexpected tag" Memento traces to indicate thetag that was expected, the actual tag received, and the connector on which the packet wasreceived (this also requires Memento 4.3)

General Features

Feature Name Feature Improvement Description

GenICam Browser Improved image buffer bandwidth on Coaxlink Quad G3

Version 4.2 – All firmware variants (unless otherwise specified)

CoaXPress Host Interface – CoaXPress Image Stream Pixel Format


Bayer 10-bit to 16-bit 10-/12-/14-/16-bit Bayer pixel formats

RGB 10-bit to 16-bit 10-/12-/14-/16-bit RGB pixel formats

RGBA 10-bit to 16-bit 10-/12-/14-/16-bit RGBA pixel formats

CoaXPress Host Interface – Connections Mapping


2D22 Connection Map2-device, 1- or 2-connection camera connection map:

2-cameraQuad

2-cameraQuad G3


Data Stream Module – Pixel Processing Features


Unpacking Mode Controls the unpacking of 10-bit, 12-bit, and 14-bit pixel components.

When unpacking 10-bit, 12-bit, and 14-bit pixel components to 16-bit, the significant pixel datacan be aligned to the least significant bit LSB) or to the most significant bit (MSB).

The default alignment option is MSB (i.e., the same behavior as in prior releases).

The default value will be changed (to LSB) in Coaxlink 4.3.

Red / Blue Swap Controls the swapping of the first and the last components of 3-component RGB packed pixeldata.

The default setting is "no swap".

Software Helpers – Image Conversion Functions


Bayer to RGB conversion Converts:

8-bit Bayer to 8-bit RGB or 8-bit BGR10-/12-/14-/16-bit Bayer to 16-bit RGB or 16-bit BGR

Note: If depth reduction is required, another call to ImageConvert is required (eitheron the Bayer source or on the RGB/BGR result).

Bit depth reduction Converts:

10-/12-/14-/16-bit Monochrome to 8-bit Monochrome10-/12-/14-/16-bit Bayer to 8-bit Bayer10-/12-/14-/16-bit LMN to 8-bit LMN10-/12-/14-/16-bit LMNO to 8-bit LMNO

Note: LMN = {RGB, BGR}; LMNO = {RGBa, aBGR, BGRa}

LMN to NML componentswap

Converts:

8-bit LMN to 8-bit NML10-bit LMN to 10-bit NML or 8-bit NML12-bit LMN to 12-bit NML or 8-bit NML14-bit LMN to 14-bit NML or 8-bit NML16-bit LMN to 16-bit NML or 8-bit NML

Note: Bit depth reduction can be performed at the same time

Note: LMN = {RGB, BGR}

Copy Efficient image copy

Raw 1X-2YE line re-ordering Unscramble a raw 1X-2YE image by properly re-ordering the image lines.

Note: Only useful for the Adimec Q-2A750 special 1X-2YE mode (all lines in onebuffer)


GenICam Browser


Adimec Q-2A750unscrambling

If the camera vendor is "Adimec" and the model contains "2A750" then the "Raw 1X-2YE linereordering process" is performed on the fly. This can be disabled via the contextual menu inthe view window.

Performance Improved GenICam Browser performance

Version 4.1 – 1-line-scan

Coaxlink firmware variant

CoaXPress Host Interface


Rectangular Image withYSize = 0

Support of CoaXPress rectangular image data stream format having YSize = 0

Single stream (1X-1Y) Single stream

1D4 Connection Map 1-device, 1- or 2- or 4-connection camera

Image Acquisition


Line-scan acquisition Image acquisition from line-scan cameras.

Acquisition Gating The acquisition gate opens and closes at line boundaries according to the applicationDSStartAcquisition and DSStopAcquisition function calls and, according to the settings of theImage Acquisition Controller, to the Start-Of-Scan and the End-Of-Scan triggers.

Line Scan Acquisition Control The LineScanAcquisitionControl GenICam features category of the Data Streammodule is dedicated to the control of line-scan acquisition.

Line-scan Acquisition Control – Start-of-scan Control


Immediate Start Starts immediately after DSAcquistionStart() is called

Software Start Starts on execution of StartScan GenICam command

Hardware Start Starts on any of the following IO Toolbox event sources (or StartScan command):

Any Line Input Tool: LIN1, LIN2, LIN3, LIN4


Line-scan Acquisition Control – End-of-scan Control


Automatic Stop Stops after having acquired ScanLength lines.

Software Stop Starts on execution of StopScan GenICam command

Hardware Stop Stops on any of the following IO Toolbox event sources (or StopScan command):

Any Line Input Tool: LIN1, LIN2, LIN3, LIN4

Camera Control – Start Cycle Trigger


Immediate Starts immediately after DSStartAcquisition() is called and then repeatedly everyCycleTargetPeriod period.

Software On execution of the StartCycle command

Hardware Starts on any of the following IO Toolbox event sources (or StartCycle command):

Any Line Input Tool: LIN1, LIN2, LIN3, LIN4The Multiplier/Divider Tool: MDV1

I/O Toolbox


Multiplier/Divider Tool The MDV tool is capable of converting upwards or downwards the rate of incoming events byany Rate Conversion Ratio ranging from 1.0E-3 up to 1.0E3.

The MDV can be sourced by any Line Input Tool: LIN1, LIN2, LIN3, LIN4

Note: The MDV tool is typically used for generating camera cycle triggers fromtrigger events delivered by a motion encoder.

Toolbox Composition 4 Line Input Tools, 1 Multiplier/Divider Tool

Version 4.1 – All Coaxlink firmware variants

CoaXPress Host Interface – Power over CoaXPress Features


Output I/V indicators Reporting of the output voltage and the output current of each connection through GenICamfeatures:CxpPoCxpCurrent and CxpPoCxpVoltage


CoaXPress Host Interface – Connection test


Host to Device ConnectionTest

Capable of performing the "Host to Device Connection Test" procedure defined in section 8.7of the CoaXPress 1.1 standard.

Device to Host ConnectionTest

Capable of performing the "Device to Host Connection Test" procedure defined in section 8.7of the CoaXPress 1.1 standard.

Image Acquisition – Stream Statistics


Stream Statistics Reporting of the average frame rate (area-scan) or line rate (line-scan) and data rate at thelevel of the PCI Express interface.

StreamStatisticsCategory

GenICam features category of the Data Stream module dedicated to the stream statistics.

I/O Toolbox


Common Tool Set 4 Line Input Tools are available in all Firmware variants

Miscellaneous Features


Auxiliary 12 V status Reporting of the availability of a valid 12 V on the auxiliary power distribution network

gentl.exe


script command

--setup option New option added to view, play and grab commands

Version 4.0

General Features


Time base accuracy The hardware timers of the Coaxlink card are now using a more accurate time base. Thisleads to a significant improvement of the time accuracy for the Camera and IlluminationController signals:

Camera Trigger (period and pulse width)Strobe (duration and delay)


GenICam Browser Features


Zoom control Capability of controlling the zoom factor of the displayed image

CoaXPress Host Interface – Host to Device Trigger Features


Latency compensation Trigger messages includes the delay information enabling the Device to compensate thevariable trigger latency.

PCI Interface – PCI Express Gen 3 x 4 Features


Image data output rate Up to 3,200 Megabytes/sec effective image data transfer rate to Host PC memory

Link speed Support of PCIe Gen 2 (5.0 GT/s) and PCIe Gen 3 (8.0 GT/s) link speeds

Miscellaneous Features


FPGA temperature Reporting of the FPGA temperature

Fan status Reporting of the fan rotation status

Solved Issues

Fixed Notification of Write Access Failures to Camera

Prior to release 4.3.1, failing write accesses to the camera were not notified.

Fixed Memento Message Reporting

Prior to release 4.3.1, Memento messages were disabled in line-scan firmware variants

Fixed CoaXPress Test Mode

Prior to release 4.3.1, the CoaXPress connection test (gentl run cxptest) was not operating correctly.

Fixed Memento Message Decoding – Data Packet Numbering

Prior to release 4.3.1, the message indicating a discontinuity in the stream data packet numbering (packet tag) wasnot properly decoded.


Fixed Memento Message Decoding – Internal Memory Read/Write Error

Prior to release 4.3.1, the message indicating a read/write access error in the Coaxlink internal memory (MIG AXIread/write error) was not properly decoded.

Fixed CycleLostTriggerCount

Prior to release 4.3, the first cycle trigger lost by the Camera and Illumination controller was not taken into account.

Fixed GenICam browser crash

Prior to release 4.3, genicam-browser.exe crashes when different camera models are connected.

Fixed BUFFER_INFO_PIXELFORMAT and BUFFER_INFO_PIXELFORMAT_NAMESPACEby taking UnpackingMode into account

Prior to release 4.2, the 16-bit pixel format reported in the CoaXPress image header was reported as is inBUFFER_INFO_PIXELFORMAT. In release 4.2, this pixel format is corrected according to the selected pixeltransformation settings (UnpackingMode and RedBlueSwap).For example: Mono10pmsb is transformed to Mono10 (when UnpackingMode is LSB) or Mono16 (whenUnpackingMode is MSB).

Camera and Illumination Controller Stops sending Camera Triggers

With releases prior to 4.2, the Camera and Illumination controller stopped sending Camera Triggers ifCameraControlMethod is RG, ExposureReadoutOverlap is Off, and the data stream is stopped during acamera readout.

Compatibility issue between GenApi XML files and GenApi reference implementation

The Coaxlink GenApi XML files delivered with the Coaxlink Driver 4.1 were incompatible with the GenApi referenceimplementation.

Stream packet FIFO overflow

With releases prior to 4.2 and firmware version prior to 168, "Stream packet FIFO overflow" errors were encounteredwhen using the VC-4MX camera in full resolution.

Stopping acquisitions

With releases prior to 4.1, timeout issues were observed when stopping acquisitions.

Stopping a data stream

With releases prior to 4.0, stopping a data stream was not reliable.


Changes

Version 4.3 – GenICam Feature Change

Data Stream Module

GenICam Feature Feature Improvement Description

UnpackingMode Changed default value to LSB (instead of MSB)

Version 4.1 – GenICam Features Changes

Device Module – Cycle Control Category

Deprecated GenICam Features Change Description New or updated GenICam Feature

CycleHardwareTriggerSource Merged with existingCycleTriggerSource feature

CycleTriggerSource

CyclePeriodTarget Renamed CycleTargetPeriod

CycleSoftwareTrigger Renamed StartCycle

Device Module – Errors Category


ErrorCounter Renamed ErrorCount

ErrorCounterReset Renamed ErrorCountReset

Data Stream Module – Errors Category


ErrorCounter Renamed ErrorCount

ErrorCounterReset Renamed ErrorCountReset

Since version 4.1, the deprecated features were removed from the drivers API. Existing applications must be edited,to use the updated feature names.

21Known Issues Coaxlink Driver 4.3.1 Release Notes

Known Issues

Deviations from the CoaXPress specification

Device to Host Connection

The CoaXPress standard suggests that Devices (cameras) can be connected to the Host (frame grabber) using afree connection scheme.Instead, the Host Interface of Coaxlink requires a specific assignment of the Device connections to the Hostconnectors (A, B, C, D).The Host Connection Map is hard-coded in the product/firmware variant. The Coaxlink product and firmware variantmust be selected according to the required mapping!

Available Coaxlink Host Connection Maps

1D1 Connection Map

Device 0 A0 Connection 0

1D1 applies to: 1-camera

Mono

1D2 Connection Map

Device 0

01

Connection 0Connection 1 B

A0 Connection 0 AOR

B


Duo

1D4 Connection Map

Device 0

01


A0 Connection 0 A

OR

01


A

OR23

Connection 2Connection 3 D

CBCD

CD


Quad 1-cameraQuad G3

1-line-scanQuad

1-line-scanQuad G3

22 Coaxlink Driver 4.3.1 Release Notes Known Issues

2D11 Connection Map


Device 1 B0 Connection 0


Duo

2D22 Connection Map

Device 0

01


A0 Connection 0 AOR

B

Device 1

01

Connection 0Connection 1 D

C0 Connection 0OR

DC


Quad 2-cameraQuad G3

2-line-scanQuad G3

4D1111 Connection Map


Device 1 B0 Connection 0

Device 2 C0 Connection 0

Device 3 D0 Connection 0

4D1111 applies to: 4-cameraQuad G3

Deviations from the GenTL specification

EventKill

The GenTL specification states that:

In case of multiple pending wait operations EventKill causes one wait operation to return with a GC_ERR_ABORTerror code.This means that if more than one thread waits for an event, the EventKill function terminates only one waitoperation and other threads will continue execution.Therefore in order to cancel all pending wait operations EventKill must be called as many times as waitoperations are pending.In case this function is called while no wait operation was pending the next call to EventGetData will return aGC_ERR_ABORT.

This specification is nothing but the behavior description of a particular implementation based on a Windows auto-reset event.

23Known Issues Coaxlink Driver 4.3.1 Release Notes

This implementation is prone to race conditions: calling EventKill N times in a row to kill exactly N waiting threadsis not guaranteed to work as expected because signaling an event that is already in the signaled state has no effect.In other words, some of the EventKill calls could have no effect.EventKill as specified is not easy to use: How many EventKill calls are required? How many EventGetDatacalls should we expect to return GC_ERR_ABORT? Note that race conditions affect these questions.The Euresys GenTL implementation solves these issues, but differs slightly:

EventKill aborts all pending wait operations on the event handle.EventKill has no impact on subsequent wait operations.

DSStopAcquisition

The GenTL specification states that:

Each call to DSStartAcquisition must be accompanied by a call to DSStopAcquisition.Argument iNumToAcquire passed to DSStartAcquisition sets the number of filled/delivered buffers afterwhich the acquisition engine stops automatically.There must be a call to DSStopAcquisition accompanying each call to DSStartAcquisition even thoughthe stream already stopped because the number of frames to acquire was reached.DSStopAcquisition returns GC_ERR_RESOURCE_IN_USE when the acquisition engine has already beenterminated or has not been started.

The reasons for this behavior is not clear.The Euresys GenTL implementation differs slightly:

DSStopAcquisition will not return GC_ERR_RESOURCE_IN_USE if the data stream hasn't been started.DSStopAcquisition will not return GC_ERR_RESOURCE_IN_USE if the data stream has already been stoppedby a prior call to DSStopAcquisition.DSStopAcquisition will not return GC_ERR_RESOURCE_IN_USE if the data stream has stopped automaticallyafter iNumToAcquire images have been captured.

In other words, DSStopAcquisition is idempotent.With the Euresys implementation, it is not necessary to treat some errors as normal, and race conditions (betweenDSStopAcquisition and the automatic stop of the data stream are avoided. Furthermore, if the data stream hasstopped automatically after acquiring iNumToAcquire images, DSStartAcquisition can be called without firstcalling DSStopAcquisition.

Deviations from the PCIe 3.0 specification

The PCI Express 3.0 interface of PC1633 – Coaxlink Quad G3 operates only at PCIe 2.0 and PCIe 3.0 link speeds.Consequently, it cannot be used in PCIe 1.x slots.

Note: When inserted in a PCIe 1.x slot, normal board operation is not possible, but the board is detected andappears in the device manager and only firmware install/upgrade actions are supported.

Coaxlink Driver 4.3.1 Release Notes -...

Documents

Transcript of Coaxlink Driver 4.3.1 Release Notes -...