| Supported Operating Systems | |
| ▼Supported Device Families And Technologies | |
| Supported Balluff Device Families | |
| Using Third-Party GigE Vision™ and/or USB3 Vision™ Devices | |
| Using Third Party GenICam™ GenTL Producers | |
| Supported Compilers | |
| ▼Installing The Impact Acquire Package | |
| ▼Windows | |
| Unattended Setups | |
| Installation Options | |
| ▼Linux | |
| Installation Options | |
| Unattended Setups | |
| Optimizing The Overall System Performance | |
| Software Concept | |
| GUI Tools | |
| Building, Linking And Running Applications Using Impact Acquire | |
| Typical Usage Scenarios And Example Applications | |
| ▼Image Acquisition | |
| Getting A Single Image | |
| Getting A Triggered Image | |
| Working With Settings | |
| Chunk Data Format | |
| Payload Types | |
| GenICam™ GenDC Format | |
| Multi-Part Format | |
| Acquiring Data | |
| Image Processing | |
| ▼Changing Device Settings | |
| Common Objects Available For Every Device In Every Interface Layout | |
| Device Specific Interface Layout | |
| GenICam™ Interface Layout | |
| Locating Properties | |
| Locating And Using Methods | |
| Bind Features Of An Unknown Type | |
| Iterate Over A Tree Of Features | |
| Logging | |
| ▼Advanced Topics | |
| ▼Installation From Private Setup Routines | |
| ►Windows® | |
| MSI Based Private Setup Routines | |
| ►Non-MSI Based Setup Routines | |
| Locating Runtime Libraries | |
| Common Files Needed For Every Device Family | |
| General Considerations When Shipping Kernel Drivers | |
| Displaying Image Data | |
| Load/Store Settings | |
| Log-file Support | |
| Camera Description Files Support (Frame Grabbers) (deprecated) | |
| .NET Support | |
| .NET Standard Support | |
| Java Support | |
| Python Support | |
| FreeImage Support | |
| FFmpeg Support | |
| GenICam™ GenTL Device Specific | |
| USB2 Devices | |
| Virtual Devices | |
| ►Linux | |
| Locating Runtime Libraries | |
| Common Files Needed For Every Device Family | |
| Log-file Support | |
| Camera Description Files Support (Frame Grabbers) (deprecated) | |
| .NET Standard Support | |
| Java Support | |
| Python Support | |
| FreeImage Support | |
| FFmpeg Support | |
| GenICam™ GenTL Device Specific | |
| Virtual Devices | |
| Embedded Linux | |
| ►Information Applying To Every Platform (Except MSI Based Installer Packages) | |
| Environment Variables | |
| GenICam™ vs. DeviceSpecific Interface Layout | |
| Callbacks Triggered By GenICam™ Events | |
| GigE Vision™ | |
| Working With Frame Grabber Boards (deprecated) | |
| Related Manuals | |
| ▼Known Issues | |
| ▼General Issues | |
| A Balluff device Such As A BVS CA-G* (mvBlueCOUGAR-X) Or BVS CA-SF (mvBlueFOX3) Is Detected As A 3rd Party GigE Vision™/USB3 Vision™ Device Only | |
| A GenICam™ Device Supporting The 'ValidValueSet' Node Inside Its XML File Cannot Be Initialised | |
| A GenICam™ Device With A Floating Enum Entry Node Inside Its XML File Cannot Be Initialised | |
| A Setting Of A GenICam™ Device Cannot Be Loaded Or Not All Features That Are Part Of The Setting Are Actually Applied To The Device | |
| Calling 'imageRequestWaitFor' Never Returns / An Application No Longer Terminates After Upgrading To Impact Acquire 2.32.0 Or Greater | |
| Checking For Updates No Longer Detects Updates | |
| Random 'bad_alloc' Exceptions When Running With Active Image Processing Filters | |
| The Presence Of A 3rd Party GenTL Producer Results In Impact Acquire To Crash | |
| ▼Windows® | |
| Images Cannot Be Loaded Or Saved By The Impact Acquire API Nor Loaded By The VirtualDevice Library | |
| Handle Leak When Updating The Device List | |
| Bluescreen (BSOD) On Windows 8.1 When Uninstalling, Updating Or Disabling The GigE Vision™ capture filter driver | |
| Bluescreen (BSOD) When GigE Vision™ Network Data Is Lost | |
| No More Network Connections Are Displayed | |
| The Driver Signature Verification Failure Dialog Box Appears When Installing A Driver On Windows® 7 Or Windows® Server 2008 R2 | |
| The 'Untrusted publisher' Dialog Box Appears When Installing A Driver On Windows® 7 Or Windows® Server 2008 R2 | |
| ►GigE Vision™ | |
| The 'LostImagesCount' increases | |
| ►USB3 Vision™ | |
| Calling AcquisitionStart For The First Time In A Process Takes A Longer Time | |
| After installing updating an existing version of Impact Acquire or after initially installing the Impact Acquire package, USB3 Vision™ devices are not accessible | |
| BVS CA-SF or other USB3 Vision™ devices connected to the system are not detected by Impact Acquire or cannot be initialised | |
| ▼Linux | |
| Applications using internal image processing algorithms use a lot of CPU time | |
| ►GenICam™ GenTL | |
| No GenICam™ devices are detected on a Linux system | |
| No USB3 Vision™ Devices Are Detected / 3rd Party Products Also Using libusb Cannot Be Used Together With The mvGenTLProducer Library | |
| Image transfer From USB3 Vision™ Devices Stops Randomly On A Linux System | |
| ▼Migration Guide | |
| Migrating Applications To Impact Acquire 3.0.0 And Higher | |
| Migrating Installers | |
| Migration Guide For GenICam™ Compliant Library And Firmware Combinations | |
| Migration Guide For mvBlueFOX Devices And Drivers | |
| Porting Existing Code | |
| Porting Applications Written With The Generic interface Layout To Use The GenICam™ Interface Layout | |
| Notes About Impact Acquire Version 1.11.32 Or Higher And/Or Using mvBlueCOUGAR-X With Firmware 1.2.0 Or Higher | |
| Error code list | |
| Deprecated List | |
