MATRIX VISION - mvBlueFOX3 Technical Documentation
Installing The mvGenTL-Acquire Package

Table of Contents

All necessary drivers are available from the MATRIX VISION website at https://www.matrix-vision.de, section "Products -> Cameras -> your interface -> your product -> Downloads".

Windows

Starting the installer application

  • mvGenTL_Acquire-x86-n.n.n.msi (for 32-bit systems) or
  • mvGenTL_Acquire-x86_64-n.n.n.msi (for 64-bit systems): will display the following dialog:
Figure 1:Driver installation - Start Window
  • Now, follow the instructions of installation program and adjust the settings to your needs:
Figure 2:Driver installation - Select Installation Folder
Since
mvIMPACT Acquire 2.25.0

wxPropView is able to check if new driver version became available on a weekly basis. Deactivate the check box if wxPropView should not check for updates. You can activate this again in wxPropView via the help menu.

Figure 3:Driver installation - Select Features
  • After confirmation, the installation will start and copy files and install device drivers.
Figure 4:Driver installation - Installation Completed

You will find all tools like

either as shortcuts on the desktop or in the Windows start menu under "MATRIX VISION -> mvIMPACT Acquire".

Note
You can ignore the other tools mvIPConfigure and mvGigEConfigure, because they are only necessary in combination with GigE Vision™ devices like the mvBlueCOUGAR-X.

Afterwards, you can use mvDeviceConfigure to update the firmware if needed. The latest firmware image is available on the web - please check for updates. The current firmware version can be read out using wxPropView.

Linux

The following (additional) packages will be needed to use all features of mvIMPACT Acquire:

  • libwxbase3.0-0
  • libwxbase3.0-dev
  • libwxgtk3.0-0
  • libwxgtk3.0-dev
  • wx3.0-headers
  • build-essential (meta package)
  • libgtk2.0-dev
  • gcc 4.8.5 (4.9.4 for ARM versions) environment or newer
Note
The names of the packages as mentioned above are the Ubuntu specific ones. Other distributions (e.g. Debian, Arch, Redhat, ...) might use different names.

The installation script will ask if the packages should be downloaded during the installation process. If some of the packages are not installed some features might not be available. If the e.g. wxWidgets related packages are missing on the target system then all GUI application coming as part of the mvIMPACT Acquire installation won't be available.

Note
If you are going to install the mvGenTL-Acquire package on an ARM device, please read this section first.

To use a (camera) device in Linux (capture images from it and change its settings), a driver is needed, consisting of several libraries and several configuration files. These files are required during run time.

To develop applications that can use the device an API is needed, containing header files, makefiles, samples, and a few libraries. These files are required at compile time.

Both file collections are distributed in a single package which is available in the Support section of the MATRIX VISION website. In addition to that an installation script is provided which can be downloaded from the same location. Using this script makes installing the driver package a lot easier.

Note
The following table shows the supported platforms and the corresponding package and installation script name:
ArchitecturePackageInstallation Script
ARM64mvGenTL_Acquire-ARM64_gnu-n.n.n.tgz install_mvGenTL_Acquire_ARM.sh
ARMhfmvGenTL_Acquire-ARMhf_gnueabi-n.n.n.tgzinstall_mvGenTL_Acquire_ARM.sh
x86_64mvGenTL_Acquire-x86_64_ABI2-n.n.n.tgzinstall_mvGenTL_Acquire.sh

The following example explains the installation process for the x86_64 package. The installation process for other packages will work almost identical except different names as mentioned in the previous table.

  • Please start a console and change into the directory where the installation script and the installation package are located e.g. /home/username/Downloads :
    cd /home/username/Downloads 
    Note
    If root permissions are needed, the script will ask for the permissions. There is no need to call it with root permissions.
  • You might need to enable the execute flag with:
    chmod a+x install_mvGenTL_Acquire.sh 
  • Run the install script:
    ./install_mvGenTL_Acquire.sh

During installation the script will ask, if it should build all tools and samples.

Note
The installation scripts is developed for Ubuntu/Debian, SUSE Linux and Red Hat Linux based distributions. On other distributions some features of the installation script may or may not work. Get in touch with us if you encounter any problems!

The installation script checks for package dependencies described above and installs them with the respective standard package manager (e.g. apt-get) if necessary. So an Internet connection is recommended.

Note
The installation script (install_mvGenTL_Acquire.sh) and the archive (mvGenTL_Acquire-x86_64_ABI2-n.n.n.tgz) must reside in the same directory. Nothing is written to this directory during script execution, so no write access to the directory is needed in order to execute the script.

You need Internet access in case one or more of the packages on which the GenICam libs depend are not yet installed on your system. In this case, the script will install these packages, and for that, Internet access is required.

The script supports various arguments, which allow to customize the installation, the desired functionalities and the installation process itself. All arguments are optional:

ArgumentFunction
-h or –help Display the help.
-p or –path Define a custom installation directory.
-ogev or –only_gev Install only the GigE Vision related features of the driver.
-ou3v or –only_u3v Install only the USB3 Vision related features of the driver.
-u or –unattended Unattended installation with default settings. By using this parameter you explicitly accept the EULA.
-m or –minimal Minimal installation. No tools or samples will be built, and no automatic configuration and/or optimizations will be done. By using this parameter you explicitly accept the EULA.

The target directory name specifies where to place the driver. If the directory does not yet exist, it will be created. The path can be either absolute or relative; i.e. the name may but need not start with / .

If no path is specified, the package will be installed to /opt/mvIMPACT_Acquire.