|
Balluff - BVS CA-GW Technical Documentation
|
The installation script supports various arguments for customizing the installation, the desired functionality and the installation process itself. All arguments are optional:
| Argument | Function | Notes |
-h --help | Display the help. | |
-p --path | Define a custom installation directory. | The target directory name specifies where to place the software package. 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/ImpactAcquire. |
-f --force | Force the installation script to use the package manager of the system to install required packages if the installation script reports inaccessible repositories. | e.g. a package source on local media. |
-a= --add= <tech1>[,<tech2>].. | Install features supporting the given technologies. | See table below for possible values for the 'tech' parameter. |
-e= --exclude= <tech1>[,<tech2>],.. | Do not install features supporting the given technologies. | |
-py --python_support | Compile the Python wrapper and install the required dependencies. Once a version number is passed to this parameter, the installation script will try to install this particular version, if possible. | e.g. --python_support=3.9 |
-r --remove | Remove the previously installed version for ALL devices, if found. | Defaults to no (or yes if a 2.x.x installation is found on the system). |
-x --extract | Extract the embedded files as a tgz archive, testing the checksum, but do not install anything. | |
-u --unattended | Unattended installation with default settings. | By using this parameter the EULA will be accepted automatically. |
-m --minimal | Minimal installation. No tools or samples will be built, and no automatic configuration and/or optimizations will be done. | |
-rt --runtime | Minimal installation. No tools or samples will be built. |
Option A: Possible values for the 'tech' parameter when using '-a', '–add', '-e' and '–exclude':
| Value for <tech> | Description | Will be installed by default? |
gev | GigE Vision™. | yes |
u3v | USB3 Vision™. | |
pcie | BVS CA-BN (mvBlueNAOS) PCIe camera. | |
usb2 | BVS CA-MLC/BVS CA-IGC (mvBlueFOX) USB2 camera. | |
vdev | Virtual Device. | no |
This option allows to select and install all availabe technologies and features.
Option B: Possible values when using bitmask to include or exclude technologies to be installed:
| Technology | Bitmask | Available for Impact Acquire |
gev | 0x01 | 3.6.0 - today |
u3v | 0x02 | 3.6.0 - today |
pcie | 0x04 | 3.6.0 - today |
usb2 | 0x08 | 3.6.0 - today |
vdev | 0x10 | 3.6.0 - today |
| Unattended installation | 0x20 | 3.6.0 - today |
This option allows only to install the technologies specified in the table above. This can be used for automated installations, e.g. in a Docker container or on a virtual machine.
In order to completely remove the software package from the system, the installation script can be called with the -r or --remove option (See Installation Options also). This will remove all files installed by the installation script and all files created by the user during the usage of the software package. The installation script will also try to remove all dependencies that were installed by the installation script itself. The only thing that will remain on the system after this step is custom, user specific settings for the GUI applications belonging to the Impact Acquire package such as ImpactControlCenter. See here for more information about these GUI tools. Since each user will work with his own set of GUI settings, these files cannot be removed automatically by the installation script but instead must be removed manually by the user if desired. These files can be found in the user's home directory under .nameOfTheApplication (e.g. .ImpactControlCenter).