Balluff - BVS CA-MLC / BVS CA-IGC / mvBlueFOX Technical Documentation
|
All necessary drivers are available from the Balluff website: https://www.balluff.com/en-de/downloads/software/mvbluefox-usb-2-0.
Starting the installer application
ImpactControlCenter is able to check the availability of new driver versions weekly. Deactivate the check box if ImpactControlCenter should not check for updates. You can activate this again in ImpactControlCenter via the help menu.
You will find all tools like
either as shortcuts on the desktop or in the Windows start menu under Balluff -> Impact Acquire
.
Afterwards, you can use DeviceConfigure 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 ImpactControlCenter.
Additional packages will be needed to use all features of Impact Acquire.
Compiler etc. for building applications:
wxWidget release 3.0 or 3.2 packages, e.g.
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 Impact Acquire installation won't be available.
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 runtime.
To develop applications that can use the device an API is needed, containing header files, makefiles, samples, and a few libraries.
Both file collections are distributed in a single package which is available in the Support section of the Balluff 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.
Architecture | Package | Installation Script |
ARM64 | mvBlueFOX ARM64_gnu 3.0.0.tgz | install_mvBlueFOX_ARM |
ARMhf | mvBlueFOX ARMhf_gnueabi 3.0.0.tgz | install_mvBlueFOX_ARM |
x86_64 | mvBlueFOX x86_64_ABI2 3.0.0.tgz | install_mvBlueFOX |
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.
/home/username/Downloads
: cd /home/username/Downloads
chmod a+x install_mvGenTL_Acquire.sh
./install_mvGenTL_Acquire.sh
During installation the script will ask, if it should build all tools and samples.
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.
install_mvBlueFOX.sh
) and the archive (mvBlueFOX
x86_64_ABI2 3.0.0.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.The script supports various arguments, which allow to customize the installation, the desired functionalities and the installation process itself. All arguments are optional:
Argument | Function |
-h or --help | Display the help. |
-p or --path | Define a custom installation directory. |
-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/Impact Acquire.