The following table shows the supported platforms and the corresponding installation archive name:
| Architecture | Package |
| x86 (32-bit) | ImpactAcquire-x86-3.3.0.exe |
| x64 (64-bit) | ImpactAcquire-x86_64-3.3.0.exe |
When starting the desired installation archive the following dialog will be displayed:
Now, follow the instructions of the installation program and adjust the settings to your needs. First the destination folder can be selected:
- Note
- Since version 2.25.0 of this framework ImpactControlCenter is able to check if a new driver version became available on a weekly basis. Deactivate the check box if ImpactControlCenter should not check for updates. You can activate this again in ImpactControlCenter via the help menu.
Next the features to be installed can be customized:
- Note
- The Virtual Device support must be enabled manually if it shall be available!
In case this customization shall be done without user interaction various (optional) command line parameters can be passed to the installation archive. In order to do this the executable must be started from a command shell and additional parameters can be added as needed (bold values define the default for this parameter if omitted):
| Argument | Function | Notes |
FILTER_INSTALL_PARAMS | Allows to customize the installation of the GigE Vision™ filter driver. | Valid parameters are all parameters that can be passed to GigEConfigure on the command line. In case whitespace will become part of this parameter list the complete list of commands must be enclosed by quotation marks. The full set of parameters available can be found here when navigating to the command-line interface chapter. This parameter is only taken into account, if GEV_NDIS_DRIVER_INSTALL is set to yes. |
GEV_SUPPORT | Defines whether GigE Vision™ device support shall be installed or not. | Valid values: yes, no |
GEV_NDIS_DRIVER_INSTALL | Defines whether the GigE Vision™ filter driver shall be installed or not. | GigE Vision™ devices can also be operated with this kernel driver even though at reduced performance. Setting this parameter to no must not be combined with the FILTER_INSTALL_PARAMS parameter. Valid values: yes, no |
MINIMAL_RUNTIME_INSTALLATION | Allows to install only the bare runtime requirements of this framework. | Valid values: yes, no |
PCIE_SUPPORT | Defines whether proprietary PCIe device support shall be installed or not. | Valid values: yes, no |
U3V_SUPPORT | Defines whether USB3 Vision™ device support shall be installed or not. | Valid values: yes, no |
USB2_SUPPORT | Defines whether proprietary USB2 device support shall be installed or not. | Valid values: yes, no |
VIRTUAL_DEVICE_SUPPORT | Defines whether proprietary virtual device support shall be installed or not. | Valid values: yes, no |
How installing Impact Acquire from the command line is also explained in detail in this section: Installation Options.
Finally the installation of the configured framework needs to be confirmed:
After confirmation, the installation will start and copy files and install device drivers.
The installation is finished now you can close the window. If selected during the installation tools like
- ImpactControlCenter
- DeviceConfigure
- IPConfigure (for GigE Vision™ devices)
- GigEConfigure (for GigE Vision™ devices)
can either be found as shortcuts on the desktop or in the Windows start menu under Balluff → Impact Acquire.
- Note
- The tools IPConfigure and GigEConfigure are only relevant when working with GigE Vision™ devices.
Afterwards, DeviceConfigure could be used to update the firmware of the connected devices if needed. Depending on the device family the latest firmware is either part of the Impact Acquire framework or can be downloaded as a separate package from the download section of the product family in question. The current firmware version of a device can be read out using ImpactControlCenter.
