Description of LV-SDS installation process and various LV-SDS configuration options
Leutron Vision
Revision: 1.0. Leutron Vision documentation set.
Copyright © 1995-2009 Leutron Vision
All Information in this document is subject to change without notice and does not represent a commitment on the part of Leutron Vision. The software products described in this document are furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of agreement.
It is against the law to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement. The licensee may make one copy of the software for backup purposes. No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or information storage and retrieval systems, for any purpose other than the licensee’s personal use, without the express written permission of Leutron Vision.
Product names mentioned in this manual may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.
04 July 2009
Table of Contents
- General information
- 1. Before installation
- 2. LV-SDS components
- 3. LV-SDS Installation
- 3.1. Installing LV-SDS under Windows
- 3.2. Installing frame grabber device driver under Windows
- 3.3. Installing the USB driver under Windows
- 3.4. Installing network filter driver under Windows
- 3.5. Testing the installation under Windows
- 3.6. Installing LV-Driver Kit under Windows
- 3.7. Installing LV-SDS under Windows Embedded
- 3.8. Installing LV-SDS under Linux
- 3.9. Installing and starting device driver under Linux
- 3.10. Testing the installation under Linux
- 3.11. Installing LV-SDS under VxWorks
- 4. LV-SDS configuration options
- 4.1. Configuring overall LV-SDS behavior
- 4.2. Configuring individual LV-SDS components
- Contacting Leutron Vision
This manual walks you through the LV-SDS installation process on various operating systems, suggests how to test the installation and provides information about various configuration options for LV-SDS and its components.
LV-SDS support and troubleshooting guide — how to get support and troubleshoot Leutron Vision products.
LV-SDS custom setup — how to customize LV-SDS setup for redistribution.
Index — entry point for Leutron Vision documentation.
Depending on which Leutron Vision hardware you plan to use, some additional notes may apply. It is highly recommended that you read the “Getting Started” document(s) for your hardware products (frame grabbers and cameras) before you start installing or otherwise using the hardware and software. The links to the individual manuals can be found in the “Main” document (entry point) of Leutron Vision documentation. Without this step
Especially, if you plan to use Leutron Vision frame grabber(s), it is recommended that you mount it (them) before LV-SDS installation. The installation program installs and registers the device driver corresponding with your hardware.
However if you plan to use only the Leutron Vision GigE Vision or USB PicSight® cameras, the note above does not apply (because they do not require a dedicated device driver) and you can freely connect them after the successful LV-SDS installation.
The standard 32–bit PC architecture (i386) is supported for Windows, Linux and VxWorks (see Section 1.2.2, “Operating system”).
The AMD 64–bit PC architecture (x86-64) is supported for 64–bit Windows and Linux. Please contact Leutron Vision to learn more details about the x86-64 architecture support.
Query Leutron Vision for information about possible support of other architectures.
Windows: all 32–bit version of Windows operating system are supported by LV-SDS, including Windows Embedded systems. 64–bit Windows are supported on the x86-64 architecture (see Section 1.2.1, “Architecture”). Starting with version 1.96.227, Windows 9x and Windows ME are no longer supported.
Linux: all flavors of 32–bit and 64–bit Linux systems are supported. We support kernel lines 2.6 and 2.4 (although kernel 2.6 is highly recommended). LV-SDS runs also on kernel 2.2, however we no longer provide any support for that version. Please check information on our website to learn which kernel versions and distributions were already successfully tested with LV-SDS for Linux. Additional Linux related information can also be found in the
lvrel.htmfile delivered together with LV-SDS for Linux.VxWorks: please contact Leutron Vision to get more information about LV-SDS for VxWorks.
Query Leutron Vision for information about possible support of other operating systems.
Other requirements or recommendations might apply, based on which particular hardware products you plan to use. Please check the documentation of your hardware products for such recommendations. For example, when using our PicSight®-GigE cameras, certain recommendations might apply for selecting the network card and other network equipment, as well as it might be necessary to re-configure some network related software, such as a firewall.
For on screen acquisitions (available when using Leutron Vision frame grabbers), the VGA board has to support linear addressing of its on-board video memory.
When upgrading LV-SDS to a newer version under Windows,
some important files that might be modified by the user are stored
in a Backup directory. The backed-up files include
the camera definition files (lvcamusr.bin and lvcamera.dat) and LV-SDS configuration file (leutron.ini). If you want to keep those modifications
in the new LV-SDS.
Under Linux the situation is a bit different. New version of LV-SDS is installed alongside the existing one, to a separate subdirectory. Multiple versions thus may be used concurrently on the same PC. The decision on which version should be active is made through Unix style soft links pointing to the active installation. See more details in Section 3.8, “Installing LV-SDS under Linux”.
The LV-SDS (Leutron Vision Software Development Suite) is a unified set of libraries and associated tools, which enable to work in the same way with all the Leutron Vision hardware products, frame grabbers (that interface to Camera Link or analog cameras) and “bus” cameras (with GigE Vision or USB interface).
LV-SDS consists of basic set of libraries, drivers and tools and from some additional higher-level tools and interfaces. Not all of them might be available on all operating systems, see especially Section 2.3, “LV-SDS for Linux — differences”. You might want to check documentation for individual software products to learn more details.
Daisy library, which is used as a programming interface in C++ for all Leutron Vision frame grabbers and cameras. Daisy includes DLLs, device drivers, import libraries, header files, source files of sample programs and complete documentation.
Camera Editor, which enables to create custom camera definitions and browse through the system defined ones.
DRAL, set of libraries for handling time critical tasks like image sequence acquisition.
Camera Control Library, providing uniform interface for communication and detection of all Leutron Vision cameras and wide range of popular (especially Camera Link) cameras from other vendors.
Orchid is a high level library (sitting on the top of Daisy) enabling fast and efficient development with visual tools like MS Visual Basic, Borland Delphi or C++ Builder, .Net Framework, etc.
PicPort® and PicProdigy® demo, PicSight® demo and UNIdemo programs are supplied to guide the novice users of LV-SDS and Leutron Vision hardware through the functionality range of the products via an intuitive user interface. It is also a good tool for first test, whether the hardware functions correctly.
Interfaces for 3rd party software include for software interface layers (usually DLL or OCX) assuring cooperation of our hardware products (frame grabbers and cameras) with various 3rd party image processing software products (especially Halcon and NeuroCheck).
Windows multimedia drivers allowing to access our hardware from various Windows applications through standard interfaces such as TWAIN, DirectShow and others.
The list of LV-SDS components above is valid for Windows versions only. Linux version of LV-SDS contains Daisy, DRAL, support for 3rd party software (Halcon), and a set of source code examples. It does not contain the Orchid library, Camera Editor, PicPort® and PicProdigy® demo, and the Windows related multimedia drivers.
Current version of Linux LV-SDS also does not support PicSight®-USB cameras yet.
Similar notes apply as for Linux LV-SDS version, see Section 2.3, “LV-SDS for Linux — differences”.
After purchasing the LV-SDS, please send us completed registration form with License-Number label stuck on it. This will assure you the access to the download area on our web-server and you will be also entitled to get support from us. Please note that while Windows and Linux versions of LV-SDS are covered by the same licence, a separate licence is required for the LV-SDS for VxWorks.
There are two ways to run the installation program: from the installation CD-ROM or using the files downloaded from LV-SDS download page.
If you are installing the LV-SDS from the installation CD,
just insert it to your CD-ROM drive, the setup program is started
automatically (in case that no program is started, please run the LvAuto.exe application from the root directory of the
CD).
The setup program's main window appears. The program checks the components present on the CD and displays a list of corresponding links in the window.
Clicking the link will start the installation procedure. Please follow the instructions described in the next chapters. LV-SDS, including all the necessary drivers, will be installed to your computer.
To start the installation, just run the appropriate file downloaded
from our LV-SDS download page, for example lvsds200005.exe. Please note that “200005” in the file
name stands for LV-SDS version 2.00, build 258.
LV-SDS, including all the necessary drivers, will be installed to your computer.
![[Note]](../../../images/icons/note.png){kind=icon} | |
The LV-SDS documentation (consisting of multiple manuals) is not included in the setup program described above. To install it together with LV-SDS, please download the required manuals from download area on our web server as well and put it to the directory with the setup program before starting the installation process. |
The installation procedure is common for all supported versions of Windows operating system. Installation procedure described in this manual is shown on Windows Vista operating system. Some differences which are specifics for older version of Windows will be explained separately.
The LV-SDS setup program inspects your system and allows you to install the appropriate LV-SDS components. The installation procedure itself is described below:
After starting the installation, either from the installation CD-ROM or from the downloaded files, you will see two introduction windows informing you about the software you are going to install. Please click the button to proceed.
In the following window you can read terms of license agreement. Confirm to proceed to the next step of the installation which is the selection of the destination directory for LV-SDS files. The setup program inspects your system and if it finds an older version of LV-SDS, it offers this directory to be used as the destination location. If you are satisfied with the destination suggested by the setup program, just click to proceed. If you want to change it, please click the button to specify your destination.
After selecting the destination directory, you may choose the components that should be included in your installation. Please select the desired options and click the button. If some of the components may not be installed (eg. because the component is not available for your operating system), the option will be disabled (grayed).
| |
The setup program looks for the documentation files stored in |
The LV-SDS supports both the frame grabbers and PicSight® “bus” cameras (with GigE Vision and USB interfaces).
In case you are using only one of these devices, you can disable the
others. In case you disable the frame grabbers, the library will not search
for frame grabbers through the startup. In case you disable PicSight®-GigE cameras,
the library will not search on the network subnet for connected cameras,
which can significantly speed up the startup. Note that these options
influence only the leutron.ini file, so if you
need to change them later on, there is no need to reinstall LV-SDS.
Instead you can use the QuickSettings.exe program to modify the settings.
When you choose all the required components please click on the Install button to proceed rest of installation.
| |
LV-SDS needs some additional components to run properly. It is the NET Framework 2.0™ or higher and Microsoft Visual C++ 2005 Redistributable™. If these component's are not installed yet, setup makes offer to install additional software from CD-ROM or runs an internet browser with an appropriate download link.  Figure 3.6. LV-SDS installation, automatic installation of additional components from the setup program |
In Windows Vista and latter, as the next step of installation is activated the device driver installation wizard. Please click on it's button to proceed. After the successful installation you can see a list of installed drivers. Let's click on button to go on.
After copying all the files to your system, the installation is completed. Please choose Reboot now and click on button. After restarting, LV-SDS is ready to use.
A new menu is added to the → menu in Windows. It contains shortcuts for the Camera Editor application, for the LV-SDS documentation, as well as for several compiled sample programs.
In the location, specified during installation (default is C:\), the folder structure with LV-SDS files is created.
The main folder is named LV-SDS.
Under the destination folder the LV-SDS setup program creates the
3rdPartyfolder: supporting software for use of 3rd party vision tools with our hardware (eg. Halcon/ActivVisionTools of MVTec Software GmbH, NeuroCheck of NeuroCheck GmbH).Backupfolder: when you install a new version of LV-SDS, original files which could be modified by the user are copied there before they are overwritten by the new installation. Typically it is theleutron.inifile orPP_Demo_CommCtl.inifile.Binfolder, containing DLLs, executables (Camera Editor, sample and demo programs) and various data files belonging to Daisy/Orchid and other libraries (camera definition files, real time application libraries, configuration files etc.).Docfolder, optionally containing documentation to LV-SDS.Driversfolder, including setup programs of kernel drivers.Includefolder, containing header files for Daisy, Orchid and other libraries.Libfolder, containing import libraries for the Daisy, Orchid and other DLLs in versions for Borland C++ and Microsoft Visual C++.Linksfolder, containing links to installed programs (can be used when installing to menu is disabled).Samplesfolder, containing special versions of some DLL's..Toolsfolder, containinglvddw.dllandclserLTV.dll.
The kernel device drivers are updated with the new installation of LV-SDS.
The Leutron Vision frame grabber boards require a device driver. In Windows Vista and latter, it is installed automatically during the LV-SDS installation by the setup program. When a board is added to the computer, however, it is necessary to install manually the driver for the newly added board as described below.
| |
All information in this section is relevant only for Leutron Vision frame grabbers. Any specific driver related issues regarding the “bus” cameras (such as PicSight®-GigE and PicSight®-USB) are described in a dedicated section (Section 3.3, “Installing the USB driver under Windows”, Section 3.4, “Installing network filter driver under Windows”) and/or in the “getting started” manual for the corresponding camera family. Also the additional device drivers required for individual components of the LVmPC system are described in the LVmPC manual. |
First step you have to do before plugging new board in the PC is install LV-SDS, so that also the drivers are installed in the system. Power off your computer and put the new board in the PCI slot. After PC start up , Windows Vista will detect the new hardware and install the appropriate driver automatically . Small dialog appears and informs the user about the installation result.
After plugging anew frame grabber in the PC, Windows will detect the new hardware and it will prompt you to select the driver to be used with the device. If LV-SDS is already installed in your PC, you should select the driver to be used manually in the wizard. The procedure is described below for Windows XP system, however it is very similar also for other versions of the Windows operating system.
If LV-SDS is not yet installed on your PC, you will find the driver files on the installation CD, in the Drivers folder.
When Windows XP detect the new hardware, following series of messages appear during the start-up:
The first one is just a welcome screen, allowing you to select the way how to install the driver. Please select the Install from a list or specific location (Advanced) option and click .
The second dialog appears. Please insert the LV-SDS installation
CD-ROM to the computer and be sure that the Search removable
media (floppy, CD-ROM...) option in the dialog is enabled.
Alternatively (and especially if you downloaded LV-SDS from the web
and don't have the installation CD-ROM), use the driver location created
during a previous LV-SDS installation. The directory with device
driver files is LVSDSHOME\drivers\Win_2000_XPLVSDSHOME is LV-SDS installation directory, C:\LVSDS by default. In such case select Include this location
in the search option in the second dialog and specify proper
path to the drivers' directory via the button. Then click .
| |
For 64-bit Windows the driver files are located in |
| |
The driver consists of 3 files that should in any case be available
to the system in the same directory (that you need to locate in the Found New Hardware Wizard as described above). The files
are: the |
After that, the third dialog might appear (depending on the LV-SDS version), informing the user that the driver did not pass the Windows logo testing. Please ignore this message and click to continue the installation. Finally, in the last (fourth) dialog simply click and the driver setup is done.
The Leutron Vision PicSight®-USB cameras require a device driver. In the Windows Vista and latter it is installed automatically during LV-SDS installation by the setup program. When a PicSight®-USB camera is connected to the computer for the first time, however, it is necessary to register the driver for the PicSight®-USB devices as described below. Next time you connect a PicSight®-USB camera, it will be recognized automatically by the system.
After connecting the PicSight®-USB camera to the PC, Windows Vista will detect the new hardware and automatically install the appropriate driver. A small dialog appears and informs the user about the installation result. To have the device automatically recognized, it is necessary to install LV-SDS first, so that also the drivers are preinstalled in the system.
After connecting the PicSight®-USB camera to the PC, Windows will
detect the new hardware and it will prompt you to select the driver
to be used with the device. If LV-SDS is already installed in your
PC, you should select the driver to be used manually from the location
on the hard disk, otherwise you should use the Drivers folder on the setup CD. The procedure is described below for Windows XP SP2
system, however it is very similar also for other versions of the Windows operating
system.
After connecting the camera to a USB connector, Windows XP will detect the new hardware and following series of messages will appear:
The first two are just welcome screens, allowing you to select the way how to install the driver. Please select the No, not this time, then the Install from a list or specific location (Advanced) option and click in each dialog.
The third dialog appears. Please insert the LV-SDS installation
CD-ROM to the computer and be sure that the Search removable
media (floppy, CD-ROM...) option in the dialog is enabled.
Alternatively (and especially if you downloaded LV-SDS from the web
and don't have the installation CD-ROM), use the driver location created
during a previous LV-SDS installation. The directory with device
driver files is LVSDSHOME\drivers\Win_2000_XPLVSDSHOME is LV-SDS installation directory, C:\LVSDS by default. In such case select Include this location
in the search option in the second dialog and specify proper
path to the drivers' directory via the button. Then click .
| |
For 64-bit Windows the driver files are located in |
| |
The driver consists of 3 files that should in any case be available
to the system in the same directory (that you need to locate in the Found New Hardware Wizard as described above). The files
are: the |
After that, the fourth dialog might appear (depending on LV-SDS version), informing the user that the driver did not pass the Windows logo test. Please ignore this message and click to continue the installation. Finally, in the last dialog simply click and you are through.
To use the PicSight®-GigE cameras with Leutron Vision filter driver, follow the installation instructions listed below. Before doing that, you might want to learn more information about the filter driver. Note that the instructions below assume that LV-SDS is already successfully installed in the system.
Open the Network Connections applet
in the Control Panel.
Click with the right mouse button on the network connection, which is used to connect the PicSight®-GigE cameras, select from the context menu.
In the Properties dialog box, General tab select button to start the installation.
The Select Network Component Type dialog box appear. Select Service as the new network component type and click the button.
In the Select Network Service dialog box ignore the options possibly offered by the system and click the button to specify the driver location.
In the next dialog browse to the location where the filter driver
files are stored. The directory is LVSDSHOME\drivers\Win_2000_XPLVSDSHOME is LV-SDS installation directory, C:\LVSDS by default. When located,click .
| |
For 64-bit Windows the driver files are located in |
| |
The driver consists of 4 files that should in any case be available
to the system in the same directory (that you need to locate in the
dialog as described above). The files are: |
Windows should successfully find the proper driver and offer it for installation as “Leutron Vision Filter Driver”. Select that option and click the button. Depending on LV-SDS and Windows versions used one or more dialogs might appear to inform you that the driver is not tested for Windows compatibility. In such case, just click through them, allowing to finish the installation successfully.
When finished the filter driver will be successfully installed and ready to use. You should see it listed in the Local Area Connection properties dialog box.
Configuration options related to the LV-SDS network filter driver (including enabling/disabling it) as well as other PicSight®-GigE related options are listed in the corresponding section of Installation and configuration guide.
Make sure that the Leutron Vision hardware you plan to use for verification is installed and all the cameras are connected with the appropriate cables, properly powered and adjusted in proper working mode (consult camera manuals if you need more advice). Check the “Getting started” document(s) for your hardware products (frame grabbers and cameras) to see more details about using each product whenever needed. The links to the individual manuals can be found in the “Main” document (entry point) of Leutron Vision documentation.
Now you can test the installation using one of the demo programs delivered with the installation. The general purpose UNIdemo program is to test any Leutron Vision hardware. For testing our PicSight®-GigE cameras, the dedicated PicSight® demo program can be even better suited. We will use UNIdemo program for the description below.
Start the UNIdemo program from the → → menu. The UNIdemo main control window appears.
In the main window, click on option to select appropriate source of image acquisition. If all LV-SDS software and Leutron Vision hardware are installed correctly, you can select connected devices directly from → submenu of UNIdemo program. submenu displays all devices possible to be used.
| |
The devices listed in the Grabber listbox are not just physical frame grabbers, but rather logical grabbers as viewed by LV-SDS. Every “bus” camera (eg. a PicSight®-GigE camera) is listed here as well. LV-SDS libraries documentation provides more information about the device selection. |
While on PicSight®-USB and PicSight®-GigE cameras it is enough to select it as the grabber, for frame grabbers and generic ”GigE” and “USB” grabbers it is necessary to select the appropriate camera. Please click on → submenu a select your camera.
Now is all prepared to test image transfer. First is necessary to initialize camera by pressing the button. If no error arises, so the device is preparing for image acquisition which can be started by pressing the or the button.
If you get an unexpected image, no image or an error message such as the one shown on the figure below, verify that the grabber/camera/connector selection you made really corresponds with your hardware, that the camera is properly connected, powered and configured (it should be set in free running mode for this test). If you still have problems, please check documentation of all the hardware components you are using to see if everything is connected properly.
LV-Driver Kit is software package which can be utilized by users who need to control the Leutron Vision PicSight® cameras with Camera Link interface by using Camera Control Library, acquire images via TWAIN interface, save video using Video for Windows or DirectShow or run applications based on the MCI interface. Package also includes tool for updating camera firmware. It may be downloaded for free from LV-Driver Kit download page or purchased just for manipulation costs on a CD-ROM.
The installation is practically identical to installation of full LV-SDS (refer to Section 3.1, “Installing LV-SDS under Windows”). The few minor differences are:
To start the installation from the installation CD-ROM, you have to click the link instead of that is used for full LV-SDS installation. To start the installation using a file downloaded from internet, note that the setup programs for the LV-Driver Kit have “rt” appendix behind the version number, for example
lvsds200005rt.exe.
The options irrelevant for the multimedia drivers are not available during LV-Driver Kit installation. They might be grayed or completely hidden during the installation.
Only necessary files relevant to the Leutron Vision multimedia drivers, tools, documentation and demo applications are installed into your system. The development files (such as library and header files) are not installed and thus the installation tree does not include all the directories installed with full LV-SDS installation. Exception are only development files belonging to the Camera Control Library.
For additional information about installed components please
have a look into Main.pdf file which is entry
point of Leutron Vision documentation. There you can find links to documents
with specific information.
Windows XP Embedded operating system is binary compatible, componentized version of Windows XP. The very same LV-SDS version can thus be used for both systems.
Extensive tests of our hardware (especially LVmPC including all its components) operation with Windows XP Embedded were done, covering all the LVmPC components/interfaces.
To get more information about various aspects of Windows XP Embedded operating system, please refer to Windows XP Embedded documentation and to other Microsoft information sources.
LV-SDS components may be installed in the Windows XP Embedded using two different attempts: using common LV-SDS setup program in a running Windows XP Embedded system, or including LV-SDS parts directly during design of the image using the components delivered by Leutron Vision.
Definitions (by means of a .sld file) for Windows XP Embedded components
corresponding to different parts of LV-SDS are ready on request.
You can include the components in your Windows XP Embedded image during design-time.
The package contains a readme.txt file providing
instructions for using the components. In future, the Windows XP Embedded components
might be delivered as a part of standard LV-SDS setup program for Windows (platforms
that may be used for design of an Windows XP Embedded image).
LV-SDS setup program works under Windows XP Embedded same as on other platforms (as described in Section 3.1, “Installing LV-SDS under Windows”).
However, there is one known limitation occurring in current LV-SDS version: the device driver for Leutron Vision frame grabbers fails to get installed in Windows XP Embedded. Also the driver update using Device manager fails. The rest of LV-SDS setup program (libraries, includes, etc.) works without problems.
The problem may be solved either by using driver component for Windows XP Embedded (see Section 3.7.1.1, “Windows XP Embedded components for LV-SDS”) or by adapting the driver's .inf file and then installing it “manually” using Device manager.
To adapt the relevant .inf file for driver
installation from your existing LV-SDS setup on your Windows XP/Windows 2000 system,
please follow the instructions given hereafter. The needed driver .inf file is located in the LVSDSHOME\drivers\Win_2000_XPlvpkxw2k.inf for PicPort®-Pro-CL frame grabbers and lvrelw2k.inf for PicPort®-Exp-CL and PicPort®-Elite frame grabbers. You need to add one more line in the [Version] section of the file:
ClassGUID={6bdd1fc6-810f-11d0-bec7-08002be2092f}Further on, you should remove the “Class” directive from the same [Version] section, or just quote its value:
Class="Image"
Carrying out these adaptations, the .inf file may be successfully used in the Device manager's “Update
driver” wizard in an existing Windows XP Embedded image. However,
to be able to install and use the driver, your Windows XP Embedded system
must anyway contain following components:
Windows Image Acquisition Core(groupSoftware/System/Printing & Imaging/Infrastructure/)Class Installer — Imaging Devices(groupSoftware/System/System Services/Base/)
When using the LV-SDS installation .sld file (Section 3.7.1.1, “Windows XP Embedded components for LV-SDS”), these components
are added automatically during dependency auto-resolution.
The Linux LV-SDS setup consists of two files, no matter whether you downloaded the LV-SDS from web or received them on the installation CD. The files are:
lvsds-(eg.VERSION.runlvsds-2.00.008-02.runfor LV-SDS 2.00.008-02) — a compressed package containing all the LV-SDS files to be installed in your system.lvrel.htm— HTML file containing release notes for the corresponding LV-SDS version.LV-SDS documentation is delivered independently, please download it from download area on our web server.
![[Important]](../../../images/icons/important.png){kind=icon} | |
The kernel 2.6 source tree (or kernel headers for kernel line
2.4) corresponding with the installed and active kernel version you
are using has to be installed with proper links on your computer so
that the device driver can be properly built during the LV-SDS setup.
In most off-the-shelf distributions it can be installed using a package
named Before starting the installation, it is strongly recommended
to read the latest release notes in When installing LV-SDS, some additional actions (such as installing
kernel source tree as described above) may be required before the
installation to ensure successful driver compilation. Please check
the The |
Collecting the installation files and preparing your system
for the installation according the release notes in lvrel.htm, you are ready to install LV-SDS.
Please run the self-executable script lvsds- with root privileges. If the
script does not execute, maybe it does not have set the appropriate
permissions — so please add them (VERSION.runchmod +x ). After that, the script should execute.lvsds-VERSION.run
The script unpacks the installation archive, stores the LV-SDS files
in /usr/LeutronVision directory, creates some links
to the LV-SDS libraries and to the LV-SDS include and lib directories, builds the driver and
starts the driver. If the installation was successful, LV-SDS is
ready to use.
In case the installation was not successful, please inspect
the error messages reported by the setup script — they should
contain hints to find out what is going wrong. Please check also again
the lvrel.htm file to be sure you have performed
all the actions required before the installation. If it did not help,
please collect the output (stdout & stderr) of the setup script and ask Leutron Vision support for
help. To run the setup script, collecting all the output to a file,
use command ./lvsds-.VERSION &>setup.log
Following subdirectories are created under the LV-SDS destination
directory (/usr/LeutronVision) by the setup script:
bindirectory, containing some.datand.inifiles used by LV-SDS, and especially the LV-SDS libraries themselves (.sofiles). Thedriver26/driver24subdirectory then contains source and object files needed to make the driver for the kernels version 2.6 resp. 2.4.
helpdirectory, that can hold LV-SDS documentation (currently the documentation is delivered independently from the setup script).
includedirectory, containing C++ header files for LV-SDS libraries.
samplesdirectory, containing the tutorials and other source code examples to help the developers starting with LV-SDS libraries.
Please note that the
binandincludedirectories contain different versions of the files, corresponding with different LV-SDS versions you have installed in past. The setup script then also creates links to the last installed version within the file system, please use these links for compilation. The links are/usr/include/lvsds(LV-SDS include files), and/usr/lib/lvsds(LV-SDS library files).
All the libraries exist in multiple variants, each compatible
with a different compiler version. Currently we deliver a version
compatible with gcc (g++) 4.x/3.4,
a version compatible with g++ 3.3/3.2. The default
links to the libraries point to those versions compatible with your
default gcc (g++) version (as
it was during LV-SDS installation). If you use multiple gcc (g++) versions, please make sure
you always use proper library links during compilation.
The device driver for Leutron Vision frame grabbers is also installed to Linux. See also more notes about driver installation and startup.
As mentioned in Section 3.8.2.1, “Installation results”, LV-SDS is
installed in few variants, each compatible with a different compiler
version. Links to those libraries are created in /usr/lib during the setup. You should always link your application with the
library variant that is binary compatible with the compiler version
you use for compilation, otherwise you can get unpredictable results.
This is usually OK if you link manually against a specific library
name (such as liblvsds.40.so) but if you
link against the generic name (liblvsds.so), you have to be careful. LV-SDS setup creates this link to point
to the library variant compatible with the compiler version that was
default at the time the setup was run (gcc --version) or (g++ --version). If you upgrade the compiler,
this link may become invalid and you might be linking your application
against incorrect library (binary incompatible with your compiler).
To fix it, you can
link always against a specific library variant (such as
liblvsds.40.so)fix the links in
/usr/libmanually so that they match your new compiler versionreinstall LV-SDS completely (the new correct links will be created during the setup)
re-run the
lvmklinksscript (this will just update all the links created usually by the setup, including the driver links, without need to run the complete setup again)
The last option is probably the most flexible one. To do it you simply type following commands on the command line:
cd /usr/LeutronVision ./lvmklinks
The Leutron Vision frame grabber boards require a device driver. It is compiled and installed automatically during LV-SDS installation by the setup script. When more hardware is added to the computer later, no additional actions are required, the driver is associated with it automatically.
| |
The driver compilation and installation is a system specific process. It is possible that a problem occurs during driver compilation if you use a kernel version not yet tested/supported by Leutron Vision. It is also possible that the driver installation can fail if you use a distribution not yet tested/supported by Leutron Vision. Such situations happen only rarely, because LV-SDS for Linux was tested with wide range of distributions and kernel versions. If it anyway happens, solving the problem is usually matter of just a very small fix of the driver or its startup script. In such case please contact directly Leutron Vision or make the fix yourself if it is trivial. Any feedback is of course always very welcome. |
The LV-SDS kernel driver should be recompiled whenever a kernel update or patch has been applied. Before recompilation, make sure the kernel source tree corresponding with your updated kernel is properly installed as described above in the note about installation prerequisites.
To start the compilation, move to the driver source directory,
which is /usr/lib/lvsds/driver26 on systems running
kernel version 2.6 and /usr/lib/lvsds/driver24 on kernel 2.4 based systems. Then run make in
the driver source directory. If the driver is recompiled successfully
without any problems, just restart
the driver and you are done.
The driver can be manually started using command (assuming you are running a system based on kernel version 2.6)
/usr/lib/lvsds/lvpicport26 start
and stopped using
/usr/lib/lvsds/lvpicport26 stop
You can also restart it using
/usr/lib/lvsds/lvpicport26 restart
or get driver status via
/usr/lib/lvsds/lvpicport26 status
If you happen to use a Gentoo distribution or its clone, lvpicport26 should be replaced with lvpicport26_gentoo. In case you are running a system based on kernel version 2.4, it
should be replaced with lvpicport24.
Make sure that the Leutron Vision hardware you plan to use for verification is installed and all the cameras are connected with the appropriate cables, properly powered and adjusted in proper working mode (consult camera manual if you need more advice). Check the “Getting started” document(s) for your hardware products (frame grabbers and cameras) to see more details about using each product whenever needed. The links to the individual manuals can be found in the “Main” document (entry point) of Leutron Vision documentation.
Now you can test the installation using one of the sample programs
delivered with the installation. As an example, we will show here
step 5 of the Daisy tutorial (located in tutorial subdirectory of /usr/LeutronVision/samples). The tutorial
is delivered in three versions, the basic Xlib version (should work
on all systems) and versions for Qt or GKT+ libraries — please
choose that one fitting best your needs and switch to its step_04 directory.
Before making (building) the example, you have to do a small
update of the main.cpp source file first: by
the top of the file, you will see definitions of three string variables, ConnectGrabber, ConnectCamera, ConnectConnector. Please adjust the strings, so that they
fit the names of grabber/camera/connector you are actually using (you
can find out the needed names using the CamEdLookUp utility, present also among the LV-SDS samples). Check Daisy user guide if you need more information
about the camera name selection.
Now you can make and run the example. Below you see brief description of the Xlib and Qt versions, the GKT+ version is very similar to the Qt one.
After starting the example, you can control the application by keystrokes suggested in the text-menu.
If you adjusted the names of your grabber/camera/connector properly, as suggested above, you can press C to connect the camera to the grabber.
Having the camera connected, you can activate the acquisition to the CPU memory: press M. If all went right, you should be able to start the acquisition by clicking the left mouse button (right-click to freeze). If not, you should see an error message in the standard output. In this example, the live image is stored in the CPU memory, showing a snap periodically (based on a timer) in the application window.
In general these samples are mentioned only for illustration,
how Qt and GKT+ interface should be implemented. Please open Readme file included in /usr/LeutronVision/samples/daisy/tutorial directory to get additional information about installation hints
and versions for which the samples are designed.
| |
Please read carefully |
If for some reason (e.g. unsupported Qt or GKT+ version,
problems during installation of the libraries) compilation of the
sample fails, please move to the /usr/LeutronVision/samples/daisy/tutorial/xlib directory and use Xlib sample instead of it. This is an easiest
way how to be sure that LV-SDS is installed correctly. Otherwise
it should be necessary to modify Makefile according
to your operating system.
Please contact Leutron Vision to get detailed information about LV-SDS for VxWorks.
The LV-SDS provides configuration options to change the default behavior of its software components. These options may be stored either in the Windows Registry (for Windows systems only), or in an initialization file. The user does not need to change any of these options unless some specific behavior or functionality is required from the LV-SDS.
On Windows systems the LV-SDS determines the location of the initialization options using the following sequence:
The Windows Registry is checked for the entry
HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy(value name:UseIni, data type:REG_DWORD, data:0or1). When this entry is0(zero), the entries are taken from the Windows Registry. WhenUseIniis1the LV-SDS will search for a file namedleutron.inifile in the following locations:The
win.inifile is searched for an entry in the form[Leutron Vision] IniPath=C:\LVSDS\bin\myinidir
If found, the
leutron.inifile is searched in the specified directory.If the file is not found at that location or no
IniPathentry is found inwin.ini, theleutron.inifile is searched in the directory where the LV-SDS DLLs were started.If the file is not found the
Windowsdirectory will be searched.If the file does not exist in the above locations, the LV-SDS will use predefined values.
On Linux systems the location of the initialization
file is not configurable. The LV-SDS searches for a file named leutron.ini in the home directory of the currently logged
user under the subdirectory .LeutronVision. If not found, the file is searched in the /usr/lib/lvsds directory. This is normally a symbolic link to the binary directory
of the last installation of the LV-SDS. Any options stored in win.ini file under Windows should be stored in the leutron.ini file instead on Linux systems. The only
exception to the leutron.ini search location
is when user manually adapts LV-SDS installation so that it is located
in a custom directory. Such directory has to be marked by environment
variable LEUTRONBASE and leutron.ini file is then searched through this location as well. This is not
recommended attitude, however, it should be used only for serious
reasons.
These options affect some aspects of the behavior of the Windows device driver for Leutron Vision frame grabber. They are neither related to the PicSight® cameras, nor even to the frame grabbers under other operating systems (such as Linux).
The driver related settings are always stored in the Windows
Registry, the options are stored in the key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LvPpx\PrvPh.
It is not possible to control the device driver options through
the leutron.ini file.
| |
Options from the |
MaxCPUBufferBy default, LV-SDS allocates a buffer to allow DMA transfer to CPU memory. This buffer is allocated during runtime and deallocated when Daisy unloads.
The buffer size can be changed by user applications during runtime by calling the
LvGrabberNode::SetDMABufferSizemethod.In order to use DMA transfer, this buffer has to be treated in a special way by Daisy and the device driver. The driver has to allocate a special block of memory to handle the buffer. Therefore, the size of the handling memory block in the driver limits the maximum size the image buffer can have.
The default maximum size for the image buffer is
32MB. If your system provides more physical memory that could be used for image transfers and you want to use it, it is possible to increase the maximum size of the image buffer by entering the new value in MB in the Registry for this parameter. The new setting will take effect the next time the driver starts, usually after rebooting the system.Default value:
32(hexadecimal20).LastScanBusBy default, LV-SDS (and its driver) only searches first 16 devices (number 0..15) on the PCI. The reason is to prevent incorrect behavior on some systems where the PCI BIOS reports wrong devices for bus number above 15.
On the other side, if a Leutron Vision frame grabber is connected to the PCI at the position (slot) above number 15, it will not be recognized by LV-SDS and thus it could not be used by user applications (even if the driver is properly loaded and the device reported as working properly in the Device manager.
To fix this problem (if it can apply on your system), set the
LastScanBusregistry entry to a higher value, for example 31. If you are not sure, locate the Leutron Vision frame grabberin the Device manager and select its from the Device manager's context menu. The dialog that will show up lists (among other info) also location of the device on the PCI bus.Default value:
15(hexadecimal0F).
These options affect the behavior of the physical library, therefore related to low level aspects of hardware access. The user should not change these options.
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\PVP.
In case the leutron.ini file is used,
the options are grouped in the section [PVP.Options].
OutputDebugStringSetting to a value greater than zero will cause any LV-SDS log entry to be reported to the system by calling the Windows API function
OutputDebugString. This could help the developer to coordinate the behavior of the LV-SDS with calls to the same function performed by the main application.To catch the debug strings, you can use any debugger, such as Turbo Debugger or CodeView. Please refer to the documentation for these products to properly configure your Windows environment.
For Linux systems, this option, when set, generates the output to the
stderrstream.Default value:
0.LogBufferSizeDetermines the internal buffer size for the LV-SDS log. The log file is written to the disk in chunks of the specified size. This will cause a general speed up of the software but some lines (depending on the buffer size) could be lost on exiting the application (eg. after a crash).
If a size of
0(the default) is specified, each line is written to the disk whenever the LV-SDS requires to log a string.We suggest turning on this option (specifying a proper size of the buffer, eg.
10480) when you are sure you have no problem with the hardware and software.Default value:
0.IRQCheckDlgControls the error dialog box display in case an IRQ conflict between ISA and PCI busses is detected. When set to
0, no dialog box is displayed but the eventual conflicts are still reported in the log file.Default value:
0.ErrorReportDlgDuring startup, Daisy checks the system for conditions preventing it to work properly. This entry controls the error dialog box display in case some “strange” conditions are detected.
The dialog box is displayed when a message of the specified or higher importance needs to be displayed. The user is given the possibility to continue the Daisy loading or terminate the application. While critical errors are always displayed, other error conditions may be ignored by setting this entry to
3(critical error) so that even if a configuration error is detected, Daisy continues loading with eventually limited functionality.Possible values are:
0The dialog box is displayed when any message is reported by Daisy startup even if they do not prevent Daisy to work properly.
1Warning. Daisy detected a possible configuration error but it could fix it properly. The Daisy behavior could differ from the expected, since Daisy used default attributes for the offending configuration.
2Error. Daisy detected a configuration error and could not fix it properly. Some of the Daisy functionality may not be available but Daisy would still work and retain most of its capabilities.
3Critical error. Daisy detected a configuration error that could not be fixed and prevents Daisy to work properly.
Default value:
2.
When application using LV-SDS is started with the autorun feature or from the Startup group, the library load can happen before the LV-SDS kernel driver
is completely loaded, resulting in not recognized boards and general
application errors. Using these options, the LV-SDS can try to access
the driver for the specified number of times.
WaitDriverCountNumber of attempts made by the LV-SDS libraries to access the LV-SDS driver.
Default value:
1.WaitDriverDelayAmount of time in milliseconds between successive attempts to access the LV-SDS driver.
Default value:
0.
These options which kind(s) of devices supported by LV-SDS should be actually used. If support for some device type is switched off, those devices will not be searched/detected during LV-SDS startup and thus no access to them can be made. These options are initially set during LV-SDS setup.
AdditionalBusDllList of (semicolon separated) DLL names. The DLLs are used to search for “bus” cameras supported by LV-SDS.
Possible entries are:
Default value:
lvBusCamNet.dll.ScanDevicesControls, whether LV-SDS should scan for frame grabber and VGA devices during startup.
Possible values are:
Default value: 1.
These options affect the behavior of the Daisy library and provide configuration for higher level topics. The user should change them with care.
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\DSY.
In case the leutron.ini file is used,
the options are grouped in the section [DSY.Options].
RXX_MemorySizeDetermines the amount of on-board memory (in MB) used for image storage before sending over the PCI bus. When
0, LV-SDS will use all the available on-board memory. The amount specified cannot be greater than the physical amount of the installed memory. In this case, theRXX_MemorySizehas no effect and LV-SDS will still use all the available memory for image storage.Default value:
0.RXX_Ch0_MemRatioDetermines the amount of on-board memory (in percents, range
10–90) assigned to the first channel of the board. On “Stereo” models the remaining memory is assigned to the second channel. This option is ignored on the “Mono” models, where the entire memory is always assigned to the single channel of the board.Default value:
50.RXX_FMBFillOn-board memory fill warning. The board generates an interrupt when line number difference between input (camera) and output (PCI) exceeds this value.
Default value:
256.MultipleInstanceWhen set to 1, Daisy shares the frame grabbers' DMA buffers in the CPU memory among individual instances (applications using Daisy), allowing better resource management and preventing pointer mismatch. This option should be used whenever you intend to run multiple Daisy applications at the same time. However, it uses more virtual memory, affecting the size of the Windows page file, so it should be used only when needed.
Other Daisy features like camera connections or boards settings are never shared between the instances, however, all applications are still responsible for handling them separately.
Default value: 0.
For easier debugging of grabber to Camera Link camera communication,
the Camera Link API Library can log the characters it has sent and received as well
as other useful information. The logging functionality is controlled
by the following entry in the win.ini file
(leutron.ini under Linux):
[Leutron Vision] clserLog=0/1
When this entry is set to 1, the library logs all the communication requests to a file named clser.log. The log file will be created in the starting
directory of the application using the Camera Link communication functions.
Similarly as for the Camera Link API Library, the configuration options are
located in the win.ini file (leutron.ini under Linux), in section [Leutron Vision]. The options are:
clallLogWhen set to
1, the library logs all the communication requests and other important diagnostics to a file namedclall.log. The log file will be created in the starting directory of the application using the Camera Link communication functions.Default value:
0.clallSearchSysDirWhet set to
1, the library will search for the manufacturer specific Camera Link API libraries also in the system directory. Otherwise only the standard Camera Link directory (located through Windows registry as described by the Camera Link standard) is searched.Default value:
0.clallDLLsThis entry can contain explicit list of file names of the Camera Link API libraries to be loaded (in other case all found libraries would be used). The list can be colon or semicolon separated and it should contain file names without paths. The library will search for the files in the same directories as usual (i.e. in the standard Camera Link directory and optionally also in the system directory).
Default value: empty string.
These options affect the low-level behavior and communication with the PicSight®-GigE cameras.
Because these options are very tightly coupled with the PicSight®-GigE cameras, more of them might be listed or further discussed directly in the PicSight®-GigE getting started manual, together with additional detailed explanations and within appropriate context. If in doubts, please try to search more information in that manual
Options for the library responsible for enumerating, communication and register access for the PicSight®-GigE cameras.
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\LvBusCamNet.
In case the leutron.ini file is used,
the options are grouped in the section [LvBusCamNet].
EnableLogWhet set to
1, thelvbusnet.logfile will be created in thebindirectory of your LV-SDS installation next time the application runs. Otherwise the log will not be created.Default value:
0.FixDiscoverIPAllows LV-SDS to discover PicSight®-GigE cameras residing in different subnet(s). Specify IP addresses (semicolon separated) of the PicSight®-GigE cameras that should be discovered.
Default value: (empty).
Example:
[LvBusCamNet] FixDiscoverIP=10.0.0.23;10.0.0.27;10.0.5.15
Options for the subsystem implementing the GigE Vision standard protocols (GVCP and GVSP).
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\LvGvp.
In case the leutron.ini file is used,
the options are grouped in the section [LvGvp].
EnableLogWhet set to
1, thelvgvp.logfile will be created in thebindirectory of your LV-SDS installation next time the application runs. Otherwise the log will not be created.Default value:
0.UseFiltDrvWhet set to
1, the Leutron Vision network filter driver is enabled, when set to0, it is disabled (not used for communication/streaming with the camera. If the filter driver is not installed or if it is explicitly disabled in the system network configuration, this option is ignored and the data will be routed through the common network stack.Default value:
1.DefGvspPktSizeStreaming packet size — maximum size of individual packets. Increasing this value can significantly improve the streaming performance. Note however, that this value must correspond with MTU settings on both camera and PC (it must be at least 50 bytes less than MTU) side and that the desired packet size must be supported by all network components involved in the communication. See full details about this and related options in PicSight®-GigE getting started.
Default value:
1400.InterPktDelayInter-packet delay — delay in microseconds between sending individual packets. Increasing the delay may slow down the streaming. This can be useful when the path between the PicSight®-GigE camera and the PC contains a segment with lower bandwidth than rest of the network. In such case the PicSight®-GigE camera could stream data faster than the narrow segment would handle, which would result in loosing data.
Default value:
0.HBRateA factor allowing to increase the heartbeat rate. For example using the value of
2, the heartbeat rate is doubled. Increasing the heartbeat rate can help to survive situations with very high network load and loosing packets — by decreasing the chance of loosing the essential heartbeat packets which would result in breaking the connection.Default value:
1.LogRateSecAllows to specify the log rate cycle in seconds. When doing long-term tests it may be useful to increase this time to get smaller log files.
Default value:
10.
These options allow to control behavior of the LV-SDS Halcon driver.
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\Halcon.
In case the leutron.ini file is used,
the options are grouped in the section [Halcon].
The LV-SDS for non-Windows operating systems does not support the data file name redirection. The user can still redirect the data files by using Unix symbolic links, which are much more flexible. The rest of this section is therefore not valid for Unix users.
In these sections, the user can specify different paths and names for each of the data component of the LV-SDS. Please be careful when altering these options, incorrect settings could result in unpredictable behavior of the libraries.
In case the Windows Registry is used, the options are stored
in the key HKEY_LOCAL_MACHINE\Software\Leutron Vision\Daisy\UserPath32.
In case the leutron.ini file is used,
the options are grouped in the section [UserPath32].
Each entry has to be in the form
DefaultFileName=NewPath\NewName
where
NewPathis the full DOS path where the file is located. This path must exist.NewNameis optional and, when specified, instructs LV-SDS to useNewNameto open the corresponding file. TheNewNamefile must exist in theNewPathdirectory. When changing only the file path be sure that the path is terminated with a backslash. This instructs LV-SDS to use the default file name.Possible values for
DefaultFileName(files whose location can be configured) are listed below.
prvphlib.logThe log file generated by Daisy (and physical library). In this case, it is not necessary that the file exists since it will be anyway created by Daisy on startup.
lvcamsys.binOne of the data files containing the settings for the configured cameras. This one holds data for the system-defined cameras in Camera Editor.
lvcamusr.binOne of the data files containing the settings for the configured cameras. This one holds data for the user-defined cameras in Camera Editor.
lvcamera.datOne of the data files containing the settings for the configured cameras. This one holds data maintained by Camera Editor (legacy version).
lvisp.datInformation related to firmware updates.
lvreg.datHardware related information.
lvrps.dat
In Section 4.1, “Configuring overall LV-SDS behavior” we have covered the overall
configuration options covering all (or most) LV-SDS components. Most
individual higher-level LV-SDS components and tools have their own
configuration options, allowing to adapt their behavior through .ini files, command-line options or different way. These
options are listed in documentation for each such respective tool.
Address: Industriestrasse 57, CH-8152, Glattbrugg, Switzerland
Phone: ++41 44 809 88 22
Fax: ++41 44 809 88 29
E-mail (sales): <intsales@leutron.com>, e-mail (support): <intsupport@leutron.com>
Web: www.leutron.com
Address: Macairestrasse 3, D-78467 Konstanz, Germany
Phone: ++49 7531 53 42 0
Fax: ++49 7531 59 42 99
E-mail (sales): <desales@leutron.com>, e-mail (support): <desupport@leutron.com>
Web: www.leutron.com/de/
Address: 25 Mall Road - Suite 300, Burlington MA 01803, USA
Phone (sales): ++1 888 442 22 69 (1), phone (support): ++1 888 442 22 69 (2)
Fax: ++1 781 353 39 43
E-mail (sales): <ussales@leutron.com>, e-mail (support): <ussupport@leutron.com>
Address: Rokycanska 27, CZ-31200 Plzen, Czech Republic
Phone: ++420 377 260 342
Fax: ++420 377 260 944
E-mail (sales): <czsales@leutron.com>, e-mail (support): <czsupport@leutron.com>
Customers residing in other countries should have a look at the list of our representatives for a distributor in their country. If no distributor exists in their country, they should contact the headquarter office directly.
To download software, documentation and other stuff, please visit our download area. If you want only download software updates, go directly to software download area.
Get more information about our support. If you need to return some (defective) material to Leutron Vision, please visit the Return Material Authorization (RMA) page.
Get information about prices and ordering.
Find out detailed information about our hardware and software product range.