FCC Compliance: EDT devices described herein are in compliance with part 15 of the FCC Rules. Operation is subject to two
conditions: (1) The device may not cause harmful interference, and (2) the device must accept any interference received,
including interference that may cause undesired operation.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of FCC Rules.
These limits are designed to provide reasonable protection against harmful interference in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used as described in the user’s
guide, may cause harmful interference to radio communications. Operating this equipment in a residential area is likely to cause
harmful interference, in which case the user will be required to correct the interference at his or her own expense.
Caution: Changes or modifications not expressly approved by Engineering Design Team, Inc. could void your warranty to
operate this equipment.
EDT, Inc.
3
Terms of Use Agreement
Definitions. This agreement, between Engineering Design Team, Inc. (“Seller”) and the user or distributor (“Buyer”), covers the
use and distribution of the following items provided by Seller: a) the binary and all provided source code for any and all device
drivers, software libraries, utilities, and example applications (collectively, “Software”); b) the binary and all provided source code
for any and all configurable or programmable devices (collectively, “Firmware”); and c) the computer boards and all other physical
components (collectively, “Hardware”). Software, Firmware, and Hardware are collectively referred to as “Products.” This
agreement also covers Seller’s published Limited Warranty (“Warranty”) and all other published manuals and product information
in physical, electronic, or any other form (“Documentation”).
License. Seller grants Buyer the right to use or distribute Seller’s Software and Firmware Products solely to enable Seller’s
Hardware Products. Seller’s Software and Firmware must be used on the same computer as Seller’s Hardware. Seller’s Products
and Documentation are furnished under, and may be used only in accordance with, the terms of this agreement. By using or
distributing Seller’s Products and Documentation, Buyer agrees to the terms of this agreement, as well as any additional
agreements (such as a nondisclosure agreement) between Buyer and Seller.
Export Restrictions. Buyer will not permit Seller’s Software, Firmware, or Hardware to be sent to, or used in, any other country
except in compliance with applicable U.S. laws and regulations.
For clarification on such laws and regulations, see the website for...
•
U.S. Department of Commerce, Bureau of Industry and Security
https://www.commerce.gov/bureau-industry-and-security
...or, if ITAR status is indicated in the product’s documentation (on the title page or near the beginning), see the website for...
•
U.S. Department of State, Bureau of Political-Military (PM) Affairs, Directorate of Defense Trade Controls (DDTC)
https://www.pmddtc.state.gov/regulations_laws/itar.html
Limitation of Rights. Seller grants Buyer a royalty-free right to modify, reproduce, and distribute executable files using the
Seller’s Software and Firmware, provided that: a) the source code and executable files will be used only with Seller’s Hardware;
b)
Buyer agrees to indemnify, hold harmless, and defend Seller from and against any claims or lawsuits, including attorneys’ fees,
that arise or result from the use or distribution of Buyer’s products containing Seller’s Products. Seller’s Hardware may not be
copied or recreated in any form or by any means without Seller’s express written consent.
No Liability for Consequential Damages. In no event will Seller, its directors, officers, employees, or agents be liable to Buyer
for any consequential, incidental, or indirect damages (including damages for business interruptions, loss of business profits or
information, and the like) arising out of the use or inability to use the Products, even if Seller has been advised of the possibility
of such damages. Because some jurisdictions do not allow the exclusion or limitation of liability for consequential or incidental
damages, the above limitations may not apply to Buyer. Seller’s liability to Buyer for actual damages for any cause whatsoever,
and regardless of the form of the action (whether in contract, product liability, tort including negligence, or otherwise) will be
limited to fifty U.S. dollars ($50.00).
Limited Hardware Warranty. Seller warrants that the Hardware it manufactures and sells shall be free of defects in materials
and workmanship for a period of 12 months from date of shipment to initial Buyer. This warranty does not apply to any product
that is misused, abused, repaired, or otherwise modified by Buyer or others. Seller’s sole obligation for breach of this warranty shall be to repair or replace (F.O.B. Seller’s plant, Beaverton, Oregon, USA) any goods that are found to be non-conforming or
defective as specified by Buyer within 30 days of discovery of any defect. Buyer shall bear all installation and transportation
expenses, and all other incidental expenses and damages.
Limitation of Liability. In no event shall Seller be liable for any type of special consequential, incidental, or penal damages,
whether such damages arise from, or are a result of, breach of contract, warranty, tort (including negligence), strict liability, or
otherwise. All references to damages herein shall include, but not be limited to: loss of profit or revenue; loss of use of the goods
or associated equipment; costs of substitute goods, equipment, or facilities; downtime costs; or claims for damages. Seller shall
not be liable for any loss, claim, expense, or damage caused by, contributed to, or arising out of the acts or omissions of Buyer,
whether negligent or otherwise.
No Other Warranties. Seller makes no other warranties, express or implied, including without limitation the implied warranties
of merchantability and fitness for a particular purpose, regarding Seller’s Products or Documentation. Seller does not warrant,
guarantee, or make any representations regarding the use or the results of the use of the Products or Documentation or their
correctness, accuracy, reliability, currentness, or otherwise. All risk related to the results and performance of the Products and
Documentation is assumed by Buyer. The exclusion of implied warranties is not permitted by some jurisdictions. The above
exclusion may not apply to Buyer.
Disclaimer. Seller’s Products and Documentation, including this document, are subject to change without notice. Documentation
does not represent a commitment from Seller.
Included Files ....................................................................................................................................................... 6
Power Over Camera Link (PoCL) ........................................................................................................................ 7
Related Resources ............................................................................................................................................... 7
Setting the Camera Model .......................................................................................................................................... 9
Image Capture and Display GUI ................................................................................................................................. 9
Units, Connectors, and Channels ............................................................................................................................. 11
Serial Communication ............................................................................................................................................... 12
At Initialization .................................................................................................................................................... 12
From Command Line ......................................................................................................................................... 12
From EDT GUI ................................................................................................................................................... 12
From Your Application ........................................................................................................................................ 13
From Camera Manufacturer’s Application ......................................................................................................... 13
Example and Utility Applications .............................................................................................................................. 13
No Triggering – Freerun (Continuous) ............................................................................................................... 16
Triggered by EDT Board (On-Demand) ............................................................................................................. 17
Triggered by EDT Board (Fixed Period)............................................................................................................. 17
Pulse-Width Triggered (Controlled or Level) ...................................................................................................... 18
External Trigger Direct to Camera ..................................................................................................................... 18
Simulation and Testing ............................................................................................................................................. 20
Building or Rebuilding an Application ................................................................................................................ 21
Board Not Seen .................................................................................................................................................. 25
Problems With Software Installation .................................................................................................................. 25
Corrupted Images, Slow Acquisition, Timeouts, Data Loss ............................................................................... 26
Problems With Bandwidth .................................................................................................................................. 27
Problems Acquiring Images With EDT Applications .......................................................................................... 27
Problems With Your Applications ....................................................................................................................... 28
Problems With Threads ...................................................................................................................................... 28
Problems With Firmware .................................................................................................................................... 28
F1 and F4 ..................................................................................................................................................................... 30
Via Berg or Optional Lemo Connector. ........................................................................................................................ 31
Via Optional Cable Assembly ....................................................................................................................................... 31
Via Ribbon Cabling and D9 Connectors....................................................................................................................... 32
Camera Configuration File Directives ................................................................................................................ 33
EDT, Inc.
5
Footer Format .................................................................................................................................................... 33
IRIG API ............................................................................................................................................................. 35
This guide covers EDT VisionLink F-series frame grabbers, which provide fast, high-resolution image capture and DMA
between an external Camera Link camera and a host computer.
These frame grabbers are designed for PCIe Gen2 but can work with other PCIe generations; however, performance
is limited by the generation of the board or slot, whichever is lower.
Companion products include remote camera extenders (RCX) over fiber; for details, see Related Resources on page 7.
Available configurations for the F-series are shown in Table 1.
Table 1. VisionLink F-series frame grabbers for Camera Link
Included Files
For the above products, your EDT installation package includes README files for quick start information and special
cases (README.*), as well as device drivers for supported operating systems and source code and binaries for...
•
GUI capture and display applications (vlviewer, pdvshow)
Command-line capture and display applications (take, simple_take, simplest_take, simple_*)
•
Command-line serial communication tool (serial_cmd)
•
Diagnostic tools (pciload, pciediag, dvinfo, pdb)
•
API libraries (libpdv, libedt, and associated source files)
•
Makefiles for Windows and Linux (makefile)
•
Visual Studio project and solution files (*/*.vcproj, */*.sln)
•
Camera configuration files (camera_config/*.cfg)
•
Board firmware files (flash/* directories)
•
Windows silent install / uninstall example batch files (wdf/install/*.bat)
VisionLink F-series
Overview
EDT, Inc.
2019 April 29
7
For detailed descriptions of selected programs, see Example and Utility Applications on page 13. For a more complete
list of files and quick-start information, consult README.pdv in your EDT installation package (see Installation on
page 8). For programming information, consult the EDT API (see Related Resources on page 7).
Power Over Camera Link (PoCL)
VisionLink frame grabbers support Power over Camera Link (PoCL) via the MSP430 using safe power. PoCL is enabled
via software (implementation TBD). For PoCL pin assignments, see Appendix A: Pin Assignments on page 29.
Related Resources
To find product-specific information that is related to a particular EDT product, go to .edt.com and open the relevant
product page. There you’ll see links to that product’s datasheet (specifications), user’s guide, and other resources.
In addition, the resources below may be helpful or necessary for your applications.
Standard Camera Link SDR
NOTE: Cabling can be from EDT or a third party.
For more documentation on cabling / pins, see
Related Resources on page 7 and Appendix A:
Pin Assignments on page 29.
Windows,
Linux
x1 PCIe, Gen1
175MB/s
VisionLink F4
x4 PCIe, Gen2
1000MB/s
x4 PCIe, Gen1
700MB/s, preliminary
Requirements
EDT boards are high-speed DMA devices that require adequate bandwidth for reliable operation. The requirements will
vary by camera (since different cameras run at different speeds), so you should select and configure your camera and
system with the proper requirements in mind, as shown in Table 2.
Table 2. Requirements for I/O, bus type, throughput, cabling
*
For bus type, observe these considerations to optimize performance...
–
Typically, these products will not work in a bus slot dedicated to graphics (display) cards.
–
Typically, these products will work in a bus slot with more, but not one with fewer, lanes than the number given here.
–
Typically, although these products will work in a bus slot newer than PCIe Gen2 (such as Gen3), performance still will not exceed
Gen2 specifications.
For details on requirements and bandwidth issues, see Problems With Bandwidth on page 27.
Installation
“Installation directory” in this guide refers to the directory in which your EDT installation package was saved.
Unless you opted to save it elsewhere, the package is saved in the default installation directory specified below.
•
The Windows default installation directory is: C:\EDT\pdv
•
The Linux default installation directory is: /opt/EDTpdv
1.
Uninstall any previously installed EDT installation packages.
2.
To use the latest possible package without creating version incompatibility issues, do one of the following...
—
For a new application, download the latest package from the EDT installation disk (included with the product),
or from www.edt.com (see Related Resources on page 7).
To install your frame grabber software, follow the steps below.
—
For an application running third-party software, use the EDT installation package version with which the software was built, or recompile / relink the application with the latest package (see Related Resources on page 7).
—
For a new board used in applications developed for earlier boards (e.g., EDT DV/a series), recompile / relink
the application with libraries / header files from an EDT device driver / SDK, version 5.4.5.8 or later.
3.
Follow the installation instructions from your camera manufacturer and your host computer manufacturer.
4.
Connect the frame grabber, using the cabling specified in Requirements on page 8.
5.
To verify that the driver is installed and the board is recognized, run pciload from the command line (for details,
see Example and Utility Applications on page 13).
NOTE If you need to provide an EDT silent Windows software installation as part of your own installation process, see
the EDT Windows batch (.bat) files in the wdf\install subfolder of the EDT installation folder. The comments
in the files explain how they can be used.
EDT, Inc.
2019 April 29
9
VisionLink F-series
Setting the Camera Model
OS
Configuration via GUI
Configuration via command line
Windows
Click the desktop icon for vlviewer.
When the camera selection dialog box appears, select
your camera. After initial setup, access this dialog box
any time via the Camera>Setup menu.
From the pdv utilities command shell, invoke the
initcam utility...
initcam -f camera_config\filename.cfg
...where filename is the camera configuration file
that matches your camera model and operating mode.
For specifying a non-default unit and channel and other
options, see initcam (Example and Utility
Applications on page 13) and the Camera
Configuration Guide (Related Resources on page 7).
Linux
First, build vlviewer (see Compiling vlviewer on
page 22). Then, in the installation directory (see
Installation on page 8), enter...
vlviewer
When the camera selection dialog box appears, select
your camera. After initial setup, access this dialog box
any time via the Camera>Setup menu.
From a terminal window, navigate to the installation
directory and follow the procedure for Windows,
replacing “\” with “/”.
If you do not have “.” in your path, add “./” before
each command – for example...
./initcam -f camera_config/file.cfg
Setting the Camera Model
Your EDT installation package provides example configuration files for various camera models; if no file is provided for
your camera, or if you wish to modify the directives of an existing configuration file, consult the EDT Camera
Configuration Guide (see Related Resources on page 7).
After installing the board and its driver, configure it for the camera you will use.
Next, initialize (configure) the driver for your camera model, using one of the methods in Table 3.
Table 3. Configuring the driver for your camera
Image Capture and Display GUI
Your EDT software contains the GUI application vlviewer, a GUI application which allows you to:
•
Configure the frame grabber for a specific camera.
•
Capture, display and save (.bmp, .tif, .jpg or .raw) images from cameras connected to the frame grabber.
•
Perform image processing and analysis on captured image data.
•
Communicate with the camera via serial.
•
Display information about the frame grabber hardware and device driver.
The Windows version of vlviewer is shown in Figure 1.
EDT, Inc.
2019 April 29
10
VisionLink F-series
Image Capture and Display GUI
Figure 1. Windows version – vlviewer
NOTE In Windows, the command line is a property of the icon.To use an icon to access a unit or channel other than 0 (the
To run the GUI...
•
For Windows: Click the vlviewer desktop icon, or enter vlviewer at a command prompt.
•
For Linux: Compile vlviewer (see Compiling vlviewer on page 22); then, in the installation directory (see Instal-
lation on page 8), enter...
vlviewer
To invoke with other than the default (0,0) unit and channel, run...
vlviewer -pdvU_C
...replacing U with the unit number (useful if you have more than one VisionLink device) and C with the channel
number for multichannel devices (see Units, Connectors, and Channels on page 11).
For example, to run the GUI using board 0, channel 1, run...
vlviewer -pdv0_1
This example is useful if, for instance, you are using one board with two base-mode cameras and you want the GUI to
access the camera on channel 1.
default): copy and rename the vlviewer icon; then change its shortcut properties to use the command line with the
option -pdvU_C where U is the unit and C is the channel.
If the image window shows incorrect data (usually because the camera model has been changed since the last
configuration), select Camera > Setup and choose the correct camera model.
If you have not yet configured the device for your camera, select your camera or simulator from the list and click OK.
To access camera controls, use the GUI toolbar and menus. For details on available options, run...
vlviewer --help
...or bring up vlviewer and select the Help menu.
EDT, Inc.
2019 April 29
11
VisionLink F-series
Units, Connectors, and Channels
Definition
Usage and Enumeration
unit
physical board
If you install one board in your host system, the system will assign the default unit number (0) to
that board. If you install multiple boards, the system will assign a unique unit number to each
board, starting with 0 (the sequence is system-dependent). Typically, the unit number is an
argument when invoking an application (such as take or vlviewer) or a parameter passed
into one of the EDT subroutines.
connector
physical Camera
Link connector
Each VisionLink board has one or two SDR connectors and one simulation channel.
•
In base mode, each camera requires one SDR connector on the EDT board, and each connector provides one channel. Therefore, in base mode, an EDT frame grabber with two connectors has two channels.
•
In medium or full mode, each camera requires two SDR connectors on the EDT board. In this
case, the two connectors work together to support one channel.
The software enumerates each SDR connector starting from the PCIe bus. So the first (primary)
connector is “0” and the next (secondary) connector is “1.” The simulator channel is“2.”
See Simulation and Testing on page 20.
channel
channel or,
sometimes,
simulation channel
LEDs
LED enumeration is 0, 1, 2, 3 (left to right
in the board’s typical vertical orientation).
0 1 2 3
Units & Connectors
Unit enumeration is system-dependent,
starting with unit 0.
Unit 0,
Connector 1
(secondary
connector)
Unit 1,
Connector 1
(secondary
connector)
Connector enumeration starts at 0 with
the connector nearest the PCIe bus. Unit 0, Unit 1,
This section covers how to work with multiple units, connectors, and channels, defined and used as shown in Table 4.
Table 4. Definition, usage, and enumeration
Figure 2 illustrates enumeration. Units (boards), connectors, and channels are always enumerated from 0. Figure 2 also
shows the status indicator LEDs (see LEDs on page 12), which are enumerated in the same way.
Figure 2. Illustration of enumeration
If you are using multiple EDT boards (units), or multiple connectors on a single EDT board, the software assigns a
unique handle to represent each unit and connector. Unless you specify a different unit number, connector number, or
both, all EDT example and utility applications will default to unit 0, connector 0.
The way that you address the appropriate unit and channel will depend on what you are doing.
•
In the EDT GUI (vlviewer or pdvshow), use -pdvU_C (see Image Capture and Display GUI on page 9.
•
In the EDT example and utility applications, use -u unit and -c channel (see Example and Utility Applica-
tions on page 13).
•
In the EDT API, use pdv_open_channel(..., unit, channel). For each device, the open routine will return
a pointer to the structure that represents the opened device (unit and channel); this pointer appears in EDT examples and documentation as pdv_p. Each unit / channel combination can be opened and manipulated independently by passing the appropriate pointer to the library subroutines. For details, consult the EDT API (see Related
Resources on page 7).
EDT, Inc.
2019 April 29
12
VisionLink F-series
LEDs
LED #
Connector #
Status
0 0
Pixel clock: on = present; off = absent
1 0 PoCL output:: on = 12V; off = GND; fast blink = error; slow blink = floating / open / sensing
2 1
Pixel clock: on = present; off = absent
3 1 PoCL output:: on = 12V; off = GND; fast blink = error; slow blink = floating / open / sensing
LEDs
As shown in Figure 2, each frame grabber’s backpanel has four LEDs (0, 1, 2, 3, left to right) to show status, as below.
Table 5. LED behavior and significance
Serial Communication
Most cameras have a manufacturer-defined serial command set for camera control and status. To utilize this capability,
EDT boards implement serial transmit and receive using standard serial lines as defined by the Camera Link standard.
You can use serial communication in a number of ways, as discussed below.
At Initialization
As mentioned in Installation on page 8, the initialization process uses directives in a configuration file to set the board
registers and the driver variables to match your camera model and your operating mode. Additional directives
(especially serial_baud, serial_init, serial_binit, and other serial_* directives) can be used to
send serial commands when the system is initialized. These are described in the EDT Camera Configuration Guide (see
Related Resources on page 7).
EDT provides several example configuration files that contain the serial commands needed to put a camera into the
desired mode. You can edit these commands or copy them to a new configuration file.
For suggestions, see comments in the example configuration files camera_config/genericXcl.cfg (where X is
replaced by a specific bits-per-pixel value – for example, generic8cl.cfg) in the EDT installation package.
From Command Line
The command-line utility serial_cmd, described in serial_cmd on page 15, allows you to send serial commands to
a camera and receive its response, in either ASCII or hexadecimal format. Command-line help also can be accessed
by entering serial_cmd --help.
If you wish to incorporate this functionality in your own application, see the source code provided in serial_cmd.c
in the EDT installation package.
From EDT GUI
In vlviewer, from the Camera menu, select Programming. The resulting dialog allows you to send and receive serial
commands from the camera. For details, see Image Capture and Display GUI on page 9.
Loading...
+ 26 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.