The script takes two arguments, both of which are optional:
target directory name•
version•
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 / .
Note:
This directory is only used for the files that are run time required.
The files required at compile time are always installed in
$HOME/mvimpact-acquire-n.n.n
. The script also creates a convenient softlink to this directory:
mvimpact-acquire -> mvIMPACT_acquire-2.6.0
If this argument is not specified, the driver will be placed in the default directory /opt .
The version argument is entirely optional. If no version is specified, the most recent
mvGenTL_Acquire-x86-n.n.n.tgz
found in the current directory will be installed.
7.3.3 Connecting the camera
After the driver installtion you have to connect the mvBlueFOX3 using a USB 3.0 cable.
You can check connection by using tool mvDeviceConfigure. In the program's window, your camera
should be listed.
Afterwards, you can start wxPropView to configure the mvBlueFOX3.
Since driver version 2.11.3, starting wxPropView the first time, the Quick Setup Wizard , a tiny and
powerful configuration tool, will be started.
7.3.4 Defining udev rules
Most Linux system nowadays use the udev device manager, which is responsible for dynamically
managing the /dev tree. In order to be able to use the MATRIX VISION mvBlueFOX3 USB3 Vision
camera as non-root user, a special set of rules has to be handed to the udev device manager.
On older systems this could be done by directly editing the contents of a "/etc/udev/rules" file,
however nowadays a "/etc/udev/rules.d" directory exists, which may contain several different
files, each defining the behavior of a system device.
In the specific case of the mvBlueFOX3 camera, if the camera has been installed through the
respective installation script install_mvGenTL_Acquire.sh , a suitable set of rules has been
installed automatically. However if for some reason the rules have to be created manually it should
be done according to the following steps:
7 Quickstart
41