=============================================================================================== version info mvIMPACT Acquire =============================================================================================== Date: Release: Changes: Affected modules, files or packages: -------------------------------------------------------------------------------------------------------------------------------------------- 06.12.2023 3.0.2 NEW FEATURES: - The Linux installation script is able to compile the Python wrapper during the (install_ImpactAcquire.sh) installation process, if desired. BUGS FIXED: - Race condition: When a GEV device did disappear and later reappear (e.g. when (mvGenTLProducer.cti) calling the 'DeviceReset' function ) while keeping the device driver instance open and calling the 'updateDeviceList' function in parallel could result to write access to the device not being possible anymore. - Unplugging an open GenICam device in ImpactControlCenter then selecting another (mvGenTLConsumer-lib) device and switching back to the unplugged one did result in a crash. - Devices that don't support the properties 'DeviceModelName' or 'DeviceFamilyName' (DeviceConfigure) do no longer cause 'DeviceConfigure' to crash CHANGED BEHAVIOUR: - LabVIEW_acquire *.msi packages will no longer be shipped separately but have been (all shipped MSI based packages) integrated as an optional component into the Impact Acquire installation packages. Existing previous packages will be removed automatically. - Due to the new installation mechanism introduced within Python 3.12, the Impact (Python API) Acquire Python API can only be built for Python versions newer than 3.5. 22.10.2023 3.0.1 UPDATES: - All signed files are signed with an updated DigiCert EV certificate now, reflecting (all shipped MSI-based packages) the new company name 'Balluff MV GmbH'. Kernel mode drivers will keep using the previous certificate until actual changes in the sources become necessary. CHANGED BEHAVIOUR: - From this version onwards, there will be a single installation package for all (all shipped packages) devices supported by this framework. See migration guide for details. - Color correction (Color+) and gamma are enabled on either the device or the host (ImpactControlCenter) BUGS FIXED: - The NDIS filter driver is installed correctly during the installation for 64-bit (ImpactAcquire*.exe) versions of Windows 7 or below. (Bug introduced in 3.0.0) - Rare assertions (e.g. when updating the device list) stating that a (ImpactControlCenter) 'wxPropertyGridItem with the name "XYZ" already exists'. - On Linux hosts with an ARM CPU the performance when converting pixel formats has (Linux packages for ARM hosts) been improved by (re)enabling OpenMP for the conversion routines. - Some message dialogs did confuse the dialog's caption with the actual message. (IPConfigure) (Bug introduced in 2.48.0) 13.10.2023 3.0.0 NEW FEATURES: - New properties 'DeviceModelName' and 'DeviceFamilyName' added to the device class (all shipped packages) or feature list. These supersede the properties 'Product' and 'Family' which became invisible for backward compatibility. - If a network interface has multiple IP addresses in different subnets and a GEV (IPConfigure, mvGenTLProducer.cti) device resides in one of these subnets, an IP address from that subnet instead of that from the first subnet will be assigned to the device when performing "auto-assign IPv4 address". UPDATES: - Updated integrated U3VBootProgrammer to 0.54.3650.2. (mvGenTLProducer.cti) - The Impact Acquire Python API can now be built for Python 3.12. (Python API) CHANGED BEHAVIOUR: - From this version onwards, various things in the API have been declared deprecated (all shipped packages) and quite a few other changes have been applied to the SDK. Have a good look at the corresponding sections in the migration guide! - From this version onwards, third party GenICam imaging devices require a license when (all shipped packages for GenICam compliant devices) they shall be used with Impact Acquire. Without a license, an overlay will be added to each image once 200 have been captured. If you are interested in using third party imaging devices with this SDK, please get in touch with us. - The BVS CA-BN (mvBlueNAOS) firmware files have been renamed to reflect the (mvBlueNAOS.*-lib -> BVS_CA-BN.*.lib) Balluff camera type name. There is no functional or API change for the user. - From this version onwards, the official support for Python 2.x will stop. This became (Python API) necessary because more recent Python versions of Python required a different installation approach and maintaining both seemed not to make sense anymore. - The deprecated Linux installer options -ogev, -ou3v and -onaos have been removed (install_mvBlueFOX.sh, install_mvBlueFOX_ARM.sh) (along with their log versions). A new option -r (--remove) has been added to (install_mvGenTL_Acquire.sh, install_mvGenTL_Acquire_ARM.sh) uninstall a previous installation for ALL devices, if found. (install_mvVirtualDevice.sh) BUGS FIXED: - On Linux hosts, GigE Vision ACTION_CMD responses have not been fetched. (mvGenTLProducer.cti) - When building the Impact Acquire Python API on Windows, an error indicating that the (Python API) required Microsoft Visual C++ Compiler is not found might appear even if the compiler exists on the system. - In IPConfigure the error -1007 might occure when there are more than one network (IPConfigure) interfaces on the system. (Bug introduced in 2.50.0) - If a network interface has multiple IP addresses, only the first IP address is shown (IPConfigure, mvGenTLProducer.cti) and can be selected when manually assigning a temporary IPv4 address to a GEV device. 28.08.2023 2.50.1 NEW FEATURES: - Calling DSGetBufferInfo( ..., BUFFER_INFO_DATA_LARGER_THAN_BUFFER, ... ) no longer (mvGenTLProducer.cti) returns GC_ERR_NOT_IMPLEMENTED but the actual information requested. (mvGenTLProducer.PCIe.cti) - GenDC data streams in 'GenDC Container Mode' can be captured from U3V devices now. (mvGenTLProducer.cti) UPDATES: - The logs now contain the local time instead of the OS-dependent time stamp in (all shipped packages) milliseconds that was displayed in previous packages. The previous behavior can be configured for individual log files in mvDebugFlags.mvd. - Improved timeout handling when sending GigE Vision ACTION_CMDs and waiting for (mvGenTLProducer.cti) responses. - mvBlueNAOS Linux kernel module now compiles and works on aarch64 (mvpci Linux kernel module) Raspberry Pi OS/Raspbian systems. BUGS FIXED: - BSOD when resend commands were triggered by the receive path either on a LAG (mvGigECapture2.sys, version 3.3.1.76) group or in combination with various versions of Wireshark or similar network sniffers. - When capturing GigE Vision Multipart or Multizone data using the NDIS 6.x based (mvGigECapture2.sys, version 3.3.1.76) filter driver every request was tagged as being incomplete. (Bug introduced in 2.50.0) - Various compilation issues appeared on Ubuntu based distributions older than (all shipped Linux packages) version 20.04. - Storage of flat field correction data for an image depth of more than eight bits (all shipped packages) was corrected. 28.07.2023 2.50.0 NEW FEATURES: - mvIMPACT Acquire is now also delivered for macOS 12 ARM64 platforms. Initially, only (additional macOS package) GEV devices are supported. - Initial version with GEV 2.2 support. (mvGenTLProducer.cti) (mvGigECapture2.sys, version 3.3.0.74) - Migration to version 1.6 of the GenICam GenTL spec. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - GenDC data streams can be captured from GEV devices now. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - New properties added 'BufferPart::regionID', 'BufferPart::groupID'. (all shipped packages) - The library learned to display Mono32 buffers. (mvDisplay-lib) - The application learned to display Mono32 buffers. (wxPropView) - The library learned to generate test images in ibpfMono32. (mvVirtualDevice-lib) - In case the network adapter has multiple IP addresses in different subnets, the (mvGenTLProducer.cti) library will automatically decide and bind the GEV device to the interface subnet that fits the best. CHANGED BEHAVIOUR: - The enum 'TBufferPartDataType' has been moved from (C/C++ API) 'DriverBase/Include/mvDriverBaseEnums.h' to 'common/TBufferPartDataType.h'. Some typedefs have been moved from 'mvPropHandling/Include/mvPropHandlingDatatypes.h' to 'common/mvCommonDataTypes.h'. - Internal migration to gcc 5.5.0 / glibc 2.21 for all Linux platforms. (C++ API, all shipped Linux packages) N.B. In the GCC 5.1 release libstdc++ introduced a new library ABI that includes new implementations of std::string and std::list. These changes were necessary to conform to the 2011 C++ standard which forbids Copy-On-Write strings and requires lists to keep track of their size. The minimum system requirements for using mvIMPACT Acquire have therefore been changed to include systems built with at least gcc 5.5 and glibc 2.21. - Internal migration to Visual Studio 2019 for all Windows platforms. (all shipped Windows packages) The whole SDK will be built using Visual Studio 2019 now. This might require some changes for private setup routines. See corresponding sections in the documentation. - From this version onwards on Windows all the installation packages will be shipped (mvVirtualDevice*.exe) as an executable package. The underlying technology will still be the same but the (mvBlueFOX*.exe) is wrapper inside a bootstrapper now. This results in 'per user' installations not being supported anymore. - Improved robustness of packet size negotiation for GEV devices, (mvGenTLProducer.cti) depending on the read back value after packet size request. - Action Commands can now be sent via limited broadcast address(255.255.255.255) (mvGenTLProducer.cti) UPDATES: - Migration to version 3.4.1 of the GenApi runtime. (all shipped packages for GenICam compliant devices) BUGS FIXED: - mvVirtualDevice instances did report an incorrect payload size when 'BufferPartCount' (mvVirtualDevice-lib) was greater than 1. - On some Linux systems in the applications 'mvIPConfigure' and 'wxPropView' some of (Linux: wxPropView, mvIPConfigure) the text and icon colours were unsuitable when using dark theme. - Setting up the stream channel for a GEV device now writes the destination (mvGenTLProducer.cti) port register last since this is a hard requirement in the GigE Vision specification. - Support for the PFNC format 'Coord3D_C32f' was incomplete while 'Coord3D_A32f' and (mvGenTLConsumer-lib) 'Coord3D_B32f' could be handled correctly. - GEV devices streaming multi-part data starting with a non-2D part could cause (mvGenTLConsumer-lib) crashes. - When opening a GEV stream channel the destination port is actually the last register (mvGenTLProducer.cti) written to. - After accessing a mvBlueFOX3 camera on a Linux host using a producer from another (mvGenTLProducer.cti) manufacturer the camera was sometimes left in a state where it was no longer recognizable as a U3V device by the MATRIX VISION producer. This is no longer the case.. - Creating a compressed video stream using FFmpeg with a pixel format of YUV422Packed (mvDeviceManager-lib) for encoding did result in swapped red and blue color components in the resulting video stream. (Bug introduced in 2.46.0) - The BUFFER_INFO_IS_QUEUED query did sometimes return false even though the buffer was (mvGenTLProducer.cti) indeed inside the acquisition engine. This could even result in deadlocks when 3rd party consumers used this information to decide whether to re-queue a buffer or not. - Due to a regression in wxWidgets the file selector editors in wxPropViews property (wxPropView) grid did contain the file name without the path. (Bug introduced in 2.49.0) - Correction of algorithm to convert pixel format YUV422Packed to YUV420P (all shipped packages) within the 'ContinuousCaptureFFmpeg' example. 03.03.2023 2.49.0 NEW FEATURES: - New C++ and C# example added to all packages: 'FirmwareUpdate'. (all shipped packages) CHANGED BEHAVIOUR: - FirmwareUpdater class (introduced in 2.41.0) moved from mvIMPACT::acquire::labs to (all shipped packages) mvIMPACT::acquire namespace. UPDATES: - The online version of the documentation for mvIMPACT Acquire as well as product (All Doxygen based HTML documentation) manuals make use of the 'Doxygen Awesome' project now (https://jothepro.github.io/doxygen-awesome-css/). - Internal migration to libexpat 2.5.0. (all shipped packages) - Migration to wxWidgets 3.2.2.1 (Windows only). All wxWidgets based applications (all shipped MSI based packages) are built using wxWidgets 3.2.2.1 now. - mvBlueNAOS Linux kernel module now compiles and works with kernel versions up to at least 5.19. This kernel version is used, for example, by Ubuntu 22.04.02 LTS. (mvpci Linux kernel module) - Ships with mvBlueNAOS firmware 2.52.3416.0. (mvBlueNAOS.*-lib) BUGS FIXED: - So far, a call of IFUpdateDeviceList with an infinite timeout would freeze the (mvGenTLProducer.cti) GEV GenTL producer. The maximum for the timeout is now identical with the maximum of the Interface's property DeviceUpdateTimeout, which is typically 5 seconds. - Destroying a 'ComponentCallback' instance that has callbacks registered for features (mvIMPACT_Acquire.h) that have already been destroyed (e.g. properties of a device instance that has been closed in the meantime) an exception was generated within the destructor. (Bug introduced in 2.48.0) - The 'Update Info' dialog will correctly inform about updates for discontinued (wxPropView) packages as well now. - Fixed a bug where an application compiled on Windows using GCC in 64-bit mode (API headers used on Windows) could crash due to the compiler using a different layout for structs in the API than those produced by Visual Studio. 17.01.2023 2.48.0 NEW FEATURES: - mvBlueNAOS devices now have preliminary support for the 'mvBlockScan' feature. (mvBlueNAOS.*-lib) - mvBlueCOUGAR-XT devices are supported by the 'Quick Setup Wizard' now. (wxPropView) - 'Acquisition Start Time', 'Acquisition Active Time' and 'Last Buffer Received' output (wxPropView) added to the 'Info Plot' of the 'Analysis Tabs'. CHANGED BEHAVIOUR: - From this version onwards the official support for all frame grabber boards supported (all shipped packages) by mvIMPACT Acquire will end. This affects the mvHYPERION package on both Linux and Windows as well as the mvTITAN/mvGAMMA and mvSIGMA/mvDELTA package on Windows. - Added new parameter to the 'update' function of the FirmwareUpdater class. (all shipped packages) When leaving the update function successfully the device just updated will be closed. When this new parameter keeps it's default value the device lists will be updated as needed as well to refresh the values containing firmware version and GenICam XML file information during the update process. - The GigE Vision specific 'All In' mode is no longer enabled by default since this (mvGenTLProducer.cti) results in buffers that don't fit into a single network packet not being transmitted completely from devices supporting the 'All In' mode. - Calling mvIPConfigure won't show any warning once called via command line interface (mvIPConfigure) using the 'hidden' parameter. - Slightly improved device detection for MATRIX VISION GEV and U3V devices. (mvGenTLConsumer-lib) (mvDeviceConfigure) UPDATES: - Added chapter 'Camera support' to all API manuals containing a table that shows the (mvIMPACT_Acquire_API_XXX_manual) support for camera families and frame grabbers with respect to host platforms. - All user mode files are signed with a new DigiCert EV certificate now since the old (all shipped MSI-based packages) one has expired. Newly shipped files (*.exe, *.dll, *.msi) will no longer carry a SHA1 signature since these certificates are no longer available. Older Windows 7 installations without the latest security updates might have trouble with this. Until further notice Windows kernel modules will no longer receive updates for Windows versions smaller than Windows 10 from this version onwards since driver signing requirements for these systems have been changed by Microsoft in a way that makes the release of updates almost impossible. - The system requirements for mvBlueNAOS have changed: The newly shipped driver and (mvBlueNAOS.sys, version 0.4.3.0) all future updates will no longer support legacy Windows installations (Windows 7 or Windows 8.1). The mvBlueNAOS Windows Kernel Driver is signed with a new DigiCert EV certificate now, since the old one has expired, and no longer carries a SHA1 signature. - Internal migration to Doxygen 1.9.6. - Updated integrated U3VBootProgrammer to 0.52.3345.2. (mvGenTLProducer.cti) - Ships with mvBlueNAOS firmware 2.52.3348.0. (mvBlueNAOS.*-lib) BUGS FIXED: - Calling 'DSGetBufferInfo( ..., BUFFER_INFO_PIXEL_ENDIANNESS, ...) did not always (mvGenTLProducer.cti) return correct results for GEV data streams. - Some errors reported by GEV devices have not been forwarded correctly to upper layers (mvGenTLProducer.cti) and some slight improvements applied to packet size negotiation. - The 'All in' formats for GEV data streams have not been processed correctly with (mvGenTLProducer.cti) 'extended block id' switched off. (mvGigECapture.sys, version 2.4.4.73) (mvGigECapture2.sys, version 3.2.4.73) - The 'Force IP' command ('Manually assign temporary IP address') in mvIPConfigure can (mvIPConfigure) be used without selecting a device again in order to re-configure devices that cannot be reached otherwise. (Bug introduced in version 2.12.0) - When ComponentCallbacks where created, deleted or configured from multiple threads (mvPropHandling-lib) deadlocks could occur when unregistering a callback that was being executed in parallel. - Trying to use a mvBlueNAOS on a Windows system with a very small AOI and very short (mvBlueNAOS.sys, version 0.4.3.0) exposure time to achieve frame rates of several thousand frames per second could crash the Windows Driver i.e. a "Bluescreen" showing an IOMMU exception. - The 'SystemLogicalProcessorCount' property on Windows did contain the number of (all shipped MSI-based packages) logical processors available to the current process, not the number of processors available to the system. - The installation on ARM64 systems which don't use Linux 4 Tegra (l4t) could fail as (install_mvGenTL_Acquire_ARM.sh) the system always tried to download the wrong kernel headers in order to compile the mvBlueNAOS kernel module. - The Multi-Core-Acquisition-Optimizer now works correctly with the Mellanox ConnectX family network card on Linux. (mvGenTLProducer.cti) 28.07.2022 2.47.0 NEW FEATURES: - The 'GenICam' namespace now contains the full SFNC 2.7 feature set as well as (C++, .NET, Java and Python API) various rc_visard related properties. - Added support for all UserData related features (e.g. CreateUserDataEntry, (mvGenTLConsumer-lib) DeleteUserDataEntry, ...) for the mvBlueFOX3 device family. - Added support for PFNC formats 'YCbCr422_8', 'YCbCr422_10', 'YCbCr422_10_CbYCrY' and (mvGenTLConsumer-lib) 'YCbCr601_10_CbYCr'. - Added more filter presets for firmware update files in the file selection dialog (mvDeviceConfigure) of the firmware update 'from specific local firmware package'. - mvBlueNAOS: Preliminary support for Thunderbolt 3 using a Thunderbolt-PCIe adapter. (mvpci Linux kernel module) (mvBlueNAOS.sys, version 0.4.2.0) - mvBlueNAOS devices support the value 'Default' for 'AcquisitionStartStopBehaviour' (mvGenTLConsumer-lib) now. - Added 'RequestQueue' property to the 'ImageControl' object in order to allow to state (all shipped packages) to which data stream of a GenICam device supporting multiple streaming channels a request shall be sent. CHANGED BEHAVIOUR: - mvIMPACT Acquire running on Linux platforms no longer requires 'ip' or 'ifconfig' (all shipped packages) to be installed in order for network functions to work correctly. - The structs 'ImageBuffer' and 'ChannelData' have been moved from (C/C++ API) 'mvDeviceManager/Include/mvDeviceManager.h' into a new header file 'common/mvImageBuffer.h', the enums 'TImageBufferPixelFormat' and 'TBayerMosaicParity' have been moved from 'DriverBase/Include/mvDriverBaseEnums.h' to 'common/TImageBufferPixelFormat.h' and 'common/TBayerMosaicParity.h'. - Slightly improved 'isDefault' behaviour of GenICam/GenApi properties. (mvGenTLConsumer-lib) - Firmware validation based on checksums within the firmware archives and the device's (mvDeviceConfigure) ability to calculate a checksum for the firmware inside the device's non-volatile (mvGenTLConsumer-lib) memory as added to the firmware update API in version 2.46.0 has been changed! The validation can now be called as a separate function from the firmware update API and is no longer done during the actual firmware update. This verification has also been added as a separate feature to mvDeviceConfigure. - Calling the 'update' method of the firmware update API for the same GenICam device (all shipped packages) multiple times using the same updater instance could result in unexpected behaviour. This has been fixed by closing and re-opening (and rebinding all features) in between now. - Removed everything related to the following classes from the C++ interface: (mvIMPACT_acquire.h) mvIMPACT::acquire::EventSubSystem, mvIMPACT::acquire::EventWaitResults, mvIMPACT::acquire::EventData. Refer to the C++ API migration guide for details. - Removed everything related to the following classes from the C interface: (mvDeviceManager.h) DMR_EventWaitFor(), DMR_EventGetData() and EventData. Refer to the C API migration guide for details. UPDATES: - Internal migration to CMake 3.23.2. - Ships with mvBlueNAOS firmware 2.49.3173.0. (mvBlueNAOS.*-lib) BUGS FIXED: - mvBlueNAOS: Buffer corruption for a few AOIs. (mvBlueNAOS.*-lib) - Allowed compileWrapperCode.bat to use two-digit Python version numbers (Python API) - Potential crash when using the 'AdaptiveHomogeneityDirected' de-Bayer algorithm on (all shipped packages) an image with a width or height of 5. - Images with pixel format 'ibpfRGBx888Packed' and a line pitch that is not a multiple (mvDisplay-lib) of 4 can be displayed correctly now. - Potential crash when the height of the image was 1 and the pixel format was either (mvVirtualDevice-lib) 'ibpfMono12Packed_V1' or 'ibpfMono12Packed_V2'. - Added security patch for zlib. Zlib version is now 1.2.12 (March 27, 2022) (all shipped packages) - On Linux systems with just a single processor/CPU core device intialization could (all shipped packages for Unix/Linux systems) fail with an error message related to the 'ImageProcessingMaximumThreadCount' property. (Bug introduced in version 2.41.0) - Non-GenICam devices will no longer complain about a bootloader firmware if the (wxPropView) firmware version major is 0. - mvBlueNAOS: Linux kernel module, if selected, will be built by the installer again. (install_mvGenTL_Acquire_ARM.sh) (Bug introduced in version 2.46.2) - mvBlueNAOS: Linux and Windows drivers now work when an IOMMU (e.g. Intel VT-d) is (mvpci Linux kernel module) being used. The Windows Driver also works when 'DMA Remapping Protection' is turned (mvBlueNAOS.sys, version 0.4.2.0) on in the BIOS. - For buffers that did arrive with varying values for 'PaddingX' while all other image (mvGenTLConsumer-lib) dimension related parameters remained the same sometimes the resulting request did return invalid line pitch values. - Fixed a small memory leak when using the FirmwareUpdater API with GenICam devices. (mvGenTLConsumer-lib) - When calling a version of the 'imageRequestReset' function when working with (all shipped packages) multiple result queues only result queue 0 got cleared. - wxPropView: Properties with a text/numeric field and spin button now work correctly (wxPropView) on Linux systems. The displayed value used to be incremented sometimes when pressing the 'down' part of the spin button. - wxPropView: Edit field sliders, if turned on in options, are now visible and usable (wxPropView) on Linux platforms that use Gtk3. - mvBlueNAOS: A corrupted image could be returned at the next attempt when an (mvpci Linux kernel module) application had previously requested a new image during acquisition and then stopped (mvBlueNAOS.sys, version 0.4.2.0) acquisition immediately, without fetching the image associated with the request. - The DirectShow interface did not take the value of the property (DirectShow_acquire.ax) 'AcquisitionStartStopBehaviour' into account, thus if a device did only support 'assbUser' the actual acquisition was not started and therefore no images could be acquired. - Potential deadlock when calling 'DSStopAcquisition' for a GEV device running with the (mvGenTLProducer.cti) socket implementation. (Bug introduced in version 2.40.3) - A 'TLS Initialization Error' could occasionally occur when multiple instances of (mvGenTLProducer.cti) mvIMPACT Acquire were used by separate processes with U3V or GEV devices on Windows systems. (Bug introduced in version 2.46.0) 07.03.2022 2.46.2 CHANGED BEHAVIOUR: - mvBlueCOUGAR-X(D) devices that are running a BootSection firmware during a firmware (mvGenTLConsumer-lib) update can corrupt the uploaded firmware if a soft reset (reboot) would be performed (mvDeviceConfigure) after writing it into the persistent memory. - Added another callback for the FirmwareUpdater class that is called if the device (mvGenTLConsumer-lib) needs an external hard reset during the update. UPDATES: - Ships with mvBlueNAOS firmware 2.47.3020.0. (mvBlueNAOS.*-lib) BUGS FIXED: - Writing the same blob of binary data to a GenICam property specifying the cache (mvPropHandling) attribute 'NoCache' did not result in the data being sent to the device multiple times but only once every time the data did change. (Bug introduced in version 2.15.1) - When an 'ctOnWriteData' callback was attached to a string property containing binary (mvPropHandling) data and new binary data was written to the property the callback was not fired. (Bug introduced in version 2.15.1) - Writing the same blob of binary data to a GenICam property specifying the cache (mvGenTLConsumer-lib) attribute 'WriteAround' did not result in the data being sent to the device multiple times but only once every time the data did change. - Explicitly checking for online updates in wxPropView did only display an info dialog (wxPropView) when a newer version was available but didn't provide any feedback if not. (Bug introduced in version 2.43.0) - An Internet connection was always required for the installation script to succeed if (install_mvBlueFOX_ARM.sh) additional packages were needed (e.g. wxWidgets). (Bug introduced in 2.12.1) (install_mvGenTL_Acquire_ARM.sh) - After issuing DeviceReset to a mvBlueNAOS camera on a Windows system: sometimes no (mvBlueNAOS.*-lib) image data was available until the application was restarted. - mvBlueNAOS: When 'mvDeviceTimeSync' is set to 'mvSystemTime' (i.e. default value) (mvBlueNAOS.*-lib) the camera reacts more quickly to changes in the PC's timestamp. 18.02.2022 2.46.1 NEW FEATURES - mvBlueNAOS cameras show the property 'DeviceStreamChannelPacketSize', which is the (mvBlueNAOS*-lib) packet size being used on the PCIe link. This value affects the efficiency of image data transfer and may explain differences in the maximum frame rate on different systems. UPDATES: - Ships with mvBlueNAOS firmware 2.47.3000.0. (mvBlueNAOS.*-lib) BUGS FIXED: - Accessing GenICam remote device registers frequently while also capturing data from (mvGenTLConsumer-lib) this remote device at high frequencies could result in buffer/request queue underruns. - mvBlueNAOS: firmware update using Windows is sometimes not possible when mvBlueNAOS2 (mvGenTLProducer.PCIe.cti, mvBlueNAOS*.dll) and mvBlueNAOS4 camera types are simultaneously connected to a system. 02.02.2022 2.46.0 NEW FEATURES: - Added color correction matrix for Sony IMX535, IMX536, IMX537 based products. (all shipped packages) - ibpfRaw became a fully supported pixel format. This will now be used for unknown (all shipped packages) pixel formats coming from third party devices in order to bypass processing filters that would otherwise modify or destroy the data and will also make the integration of GenDC containers a lot easier later. - mvHYPERION driver became 'updateDeviceList' aware. (mvHYPERIONfg-lib) - Reduced memory usage for mvBlueNAOS Linux kernel module and Windows driver. (mvBlueNAOS.sys, version 0.3.1.3) (mvpci Linux kernel module, version 0.3.2) (mvGenTLProducer.PCIe.cti) - The number of mvBlueNAOS cameras that may be connected to a system is no longer (mvpci Linux kernel module, version 0.3.2) restricted to 4. Now only system resources limit how many cameras may be used. (mvGenTLProducer.PCIe.cti) - Firmware validation based on checksums within the firmware archives and the devices (mvDeviceConfigure) ability to calculate a checksum for the firmware inside the devices non-volatile (mvGenTLConsumer-lib) memory added to firmware update API. - Added support for mvBlueNAOS4 camera BVS CA-BN4-0124BG (IMX535 sensor). (mvBlueNAOS.sys, version 0.3.1.3) (mvpci Linux kernel module, version 0.3.2) (mvBlueNAOS.S-lib) (mvGenTLProducer.PCIe.cti) - mvBlueNAOS cameras support debounced inputs. The 'mvLineDebounceTime*' (mvBlueNAOS*-lib) properties can now be used to control the debounce feature. - mvBlueNAOS cameras support a new 'mvDeviceTimeSync' property to turn on automatic (mvBlueNAOS*-lib) synchronization of the camera's timestamp with the PC's system time, and this is turned on by default. Alternatively it is possible to write time values to 'mvDeviceTimeSyncPushValue' in order to implement a synchronization method within a user application. - Added package installation for Linuxmint distribution. (install_mvBlueFOX.sh) (install_mvGenTL_Acquire.sh) (install_mvGenTL_Acquire_ARM.sh) (install_mvHYPERION.sh) (install_mvVirtualDevice.sh) - 'Multi-Core Acquisition' related driver features are available on Linux as well now. (mvGenTLProducer.cti) However the overall behaviour is not yet comparable with Windows. So far only interrupt routing is implemented. - The 'InterfaceModule' for GigE Vision cameras now contains additional features for (mvGenTLProducer.cti) making use of the acknowledge(s) for generated Action commands. CHANGED BEHAVIOUR: - Removed mvBlueCOUGAR-S_technical_manual.chm from installation packages. It will be (mvGenTL_Acquire*.exe) still available here: https://www.balluff.com/en-de/online-manuals-mv. - Loading the system's libusb and libudev if they are newer than our minimum (mvGenTLProducer.cti for Linux) requirement. - Whenever no more resend credits are available for buffer reconstruction a buffer will (mvGigECapture.sys, version 2.4.3.72) time out automatically when no more network packets are received for this buffer for (mvGigECapture2.sys, version 3.2.3.72) a period of 100ms no matter what timeout value has been specified for that particular buffer. - Packet size negotiation for GEV devices is now about 20ms faster, in cases where the (mvGenTLProducer.cti) device rounded the value due to incompatibility with the requested packet size. BUGS FIXED: - The 32-bit version of mvGigEConfigure did try to install a 32-bit kernel driver when (mvGigEConfigure) executed on a 64-bit version of Windows. - Starting a second mvIMPACT Acquire application whilst a mvBlueNAOS camera was (mvBlueNAOS.sys, version 0.3.1.3) streaming images would stop the streaming. - When opening a GenICam device not supporting a streaming channel in its current (wxPropView) configuration the property tree has not been created. (Bug introduced in version 2.42.0) - When wxPropView is opened the AOI of the selected Analysis Tab was shown once it has (wxPropView) been disabled in the previous session. - Reading 'EVENT_NUM_FIRED' for the error event using the 'EventGetInfo' function did (mvGenTLProdu*.cti) return an incorrect value. - Starting a second mvIMPACT Acquire application whilst a mvBlueNAOS camera was (mvBlueNAOS*-lib) streaming images would change the colour shown by the camera's LED. (mvpci Linux kernel module, version 0.3.2) (mvBlueNAOS.sys, version 0.3.1.3) (mvGenTLProducer.PCIe.cti) - Calling mv.impact.acquire.EnumPropertyI64.getTranslationDictString on 32-bit (mv.impact.acquire.dll) operating systems and mv.impact.acquire.Component.selectingFeatures or mv.impact.acquire.Component.selectedFeatures on 64-bit operating systems could result in random crashes. - When installing the mvIMPACT Acquire driver package on Linux in an attended mode, (install_mvBlueFOX.sh) installation for g++ compiler, libexpat and wxWidgets were skipped. (install_mvGenTL_Acquire.sh) (install_mvHYPERION.sh) (install_mvVirtualDevice.sh) - Some non-U3V USB composite devices have been incorrectly detected as U3V devices on (mvGenTLProducer.cti) Linux. (Bug introduced in version 2.44.0) - Missing Visual Studio runtime libs required by the GenICam runtime 3.3.0 added to (mvGenTL_Acquire*.exe) installation. Without them VS 2019 redist packages need to be installed on the target system. 07.09.2021 2.45.0 NEW FEATURES: - Added support for BinningHorizontal and BinningVertical to CustomCommandGenerator (all shipped packages) generator class. Might need a firmware update on the device to be usable. - Linux installers will try to sign the mvBlueNAOS kernel module on x86_64 platforms (mvGenTL Linux installer and mvBlueNAOS manual) if appropriate keys are found. The manual contains detailed instructions on using the kernel module on systems with UEFI SecureBoot enabled. - RGB pixel formats now working for IMX540 mvBlueNAOS camera. (mvBlueNAOS.sys, version 0.1.7.1) (mvpci Linux kernel module, version 0.1.16) (mvBlueNAOS*-lib, version 2.44.2754.0) - 'Multi-Core Acquisition' wizard and related driver features are available for (wxPropView) mvBlueCOUGAR-X(D) devices with firmware version 2.44.0 or higher as well now. (mvGenTLProducer.cti) (Windows only) - Complete overhaul of Internet based firmware update functionality. Now also the new (mvDeviceConfigure) mvBlueCOUGAR-XT way of performing firmware updates is supported. Release notes will be displayed in a new viewer. Therefore the additional package 'webview' for wxWidgets is necessary and will be installed. - Silent/unattended firmware update is possible for mvHYPERION devices as well now. (mvDeviceConfigure) UPDATES: - Migration to version 3.3.0 of the GenApi runtime. (all shipped packages for GenICam compliant devices) - On Linux systems, the 'genicam-cache' directory will now be read- and writable (mvGenTLProducer.cti for Linux) by any system user. - Internal migration to IPP 2021.2. (all shipped packages) - MSI packages will be built using WiX 3.11.2 now. (all shipped MSI based packages) - Improved execution speed of the 'acquisitionStart' and 'acquisitionStop' function (mvGenTLProducer.cti) for USB3 Vision devices. - New GUI visualization for setting up and controlling the video stream recording (wxPropView) via FFmpeg functionality. - Added check for detecting Visual Studio 2015 or later when building the mvIMPACT (Python API) Acquire Python package. CHANGED BEHAVIOUR: - From this version onwards specific interface technologies can be assigned for (mvGenTL Linux installer scripts) installation by using new command line parameters. The old parameters: "only_gev", "only_u3v", "only_naos" have been declared deprecated for new versions. - From this version onwards it is possible to combine a minimal and an unattended (all Linux installer scripts) installation using the '-m' and '-u' parameter of the installation scripts. BUGS FIXED: - Driver update info box will only be shown on program start, if the option for (wxPropView) 'Auto-Check For Updates Every Week...' is enabled. - Driver packages will now be downloadable with the 'Update' button within the (wxPropView) driver update info box. (Bug introduced in version 2.37.1) - The Linux installer will try to install Kernel header packages before building the (mvGenTL Linux installer) mvBlueNAOS kernel module. - All 3 histogram plots did display incorrect data and pixel sums. (wxPropView) (Bug introduced in version 2.41.0) - AGC/AEC/AWB used to stop working on reopening a mvBlueNAOS camera running on (mvBlueNAOS.sys, version 0.1.7.1) Windows. (mvBlueNAOS*-lib, version 2.44.2754.0) - Devices not allowing a width smaller than 640 or a height smaller than 480 could not (mvIMPACTAcquire_Cognex_Adapter-lib) be operated. - Queuing a single buffer using 'imageRequestSingle' and calling 'SoftwareSignalPulse' (mvGenTLConsumer-lib) or writing to a UserOutput directly afterwards to trigger an image could result in lost buffers for GEV devices. 22.06.2021 2.44.0 NEW FEATURES: - Initial support for the new mvBlueNAOS camera family (PCIe) added. (mvGenTLProducer.PCIe.cti) (mvBlueNAOS.sys, version 0.1.6.0) (mvBlueNAOS*-lib, version 2.42.2698.1) - Added new C# example: ContinuousSaveImage. (all shipped MSI based packages) - Added the properties 'SystemPhysicalProcessorCount' and'SystemLogicalProcessorCount' (all shipped packages) to the Info list. - Added 'mvMultiCoreAcquisition' related features to the nodemap of the (mvGenTLProducer.cti) 'DataStreamModule'. (Windows only, mvBlueCOUGAR-XT only) - Added 'Multi-Core Acquisition' wizard. (wxPropView) (Windows only, mvBlueCOUGAR-XT only) - Added color correction matrix for Sony IMX545, IMX546, IMX547 based products. (all shipped packages) NEW FIRMWARE: - Firmware version 0x35(53) for mvBlueFOX devices added. (mvBlueFOX-lib) Changes: - The I2C interface of mvBlueFOX-MLC devices did always return success on read even if no external device was connected and no sub-address was specified. UPDATES: - Once the cursor is placed over a scrollbar of the image canvas, using the mouse wheel (wxPropView) will cause scrolling into the corresponding orientation of the scrollbar instead of zooming now. - Internal migration to CMake 3.20.2. BUGS FIXED: - USB composite devices that are a U3V device as well as something else (e.g. a UVC) (mvGenTLProducer.cti) could only be used if the IAD describing the U3V device was described by the last IAD (on Windows) or the first IAD (on Linux). 04.05.2021 2.43.0 NEW FEATURES: - If an image is loaded into wxPropView, the file name will now be visible in the (wxPropView) status bar and also with the 'Request Info' overlay. - On Linux systems, all mvIMPACT Acquire log files are now read- and writable by any (all shipped packages for Unix/Linux systems) system user, no matter which user created them first. - Linux installation scripts will install dependencies (e.g. wxWidgets, ...) on x86_64 (all shipped Linux x86_64 packages) Red Hat Linux and Fedora systems now. - The Java wrapper for mvIMPACT Acquire added in version 2.36.0 is now shipped for (all shipped Linux ARM64 and ARMhf packages) ARM64 and ARMhf platforms as well. - Resend requests can be sent to devices residing in different subnets now. (mvGigECapture.sys, version 2.4.2.71) (mvGigECapture2.sys, version 3.2.2.71) BUGS FIXED: - mvBlueFOX devices were not reported by the mvDeviceManager library if another process (mvBlueFOX-lib) has opened this device already. (Linux only) - Checking if a certain device is in use or opening a device from multiple processes in (mvGenTLConsumer-lib) parallel could results in false positives for the 'is in use' state or a failure when trying to open an unused device. 09.04.2021 2.42.0 NEW FEATURES: - It is now possible to choose, if image meta data is saved beside the image data, (wxPropView) when the 'Save Image...' or 'Save All Recorded Images' feature is used - Support for mvBlueFOX-ML/IGC202vG devices added. (mvBlueFOX-lib) - Support for permanent Unicast device discoveries added. (mvGenTLProducer.cti) - Added a menu to configure permanent Unicast device discoveries. (mvIPConfigure) BUGS FIXED: - Creating a System.Drawing.Bitmap object from a RGB888Packed request buffer did (mv.impact.acquire.dll) result in a corrupt bitmap if the source image width was divisible by 4. (Linux only) - When an image was loaded from hard drive into wxPropView, the analysis plots were (wxPropView) not automatically refreshed with data from that image. - If the device was closed before the destruction of the corresponding FirmwareUpdater (all shipped packages) object, undefined behavior could occur. (Bug introduced in version 2.41.0) - The parameters of the FirmwareUpdater class constructor in .NET didn't change the (mv.impact.acquire.dll) behaviour of the following update. Only default update settings were used. (Bug introduced in version 2.41.0) - Failing to rename or re-create existing log files could result in a crash. (all shipped packages) This could happen e.g. on Linux when 'root' did create a set of log-files and then later a standard user tried to override them with a new mvIMPACT Acquire process. - wxPropView could crash when 'Synchronous Method Execution' was switched off. (wxPropView) (Bug introduced in version 2.41.0) 05.03.2021 2.41.0 NEW FEATURES: - mvIMPACT Acquire is now capable of updating the firmware of our GenICam devices and (all shipped packages) the mvBlueFOX devices. For further information see the 'FirmwareUpdater' class in the SDK manuals. - Added color correction matrix for Sony IMX530, IMX531, IMX532 based products. (all shipped packages) - Property 'ImageProcessingMaximumThreadCount' added to 'SystemSettings'. See (all shipped packages) 'Image Processing' chapter in the API manuals. - GEV devices can be discovered in subnets different from the host's subnet via unicast (mvGenTLProducer.cti) device discoveries now. - 'Capture -> Set Image Processing Thread Count' option added. See 'Advanced Operation' (wxPropView) in the wxPropView chapter of the GUI tools manual. - Certain serial numbers can be passed inside a 'update firmware file' to define a (mvDeviceConfigure) subset of devices to be updated for a certain product type. See command-line interface documentation of mvDeviceConfigure for details. UPDATES: - Added support for the GEV_FLAG_RESEND_RANGE_ERROR flag specified in the GigE Vision. (mvGigECapture.sys, version 2.4.1.70) (mvGigECapture2.sys, version 3.2.1.70) - JPEG data coming from a device is no longer deflated within the capture thread since (wxPropView) this could result in the capture queue to run empty. BUGS FIXED: - When using the Bayer filter "RawToPlanes" on color images with an even width, the (all shipped packages) resulting image ended up being one pixel to wide. (Bug introduced in version 2.36.0) - The environment variable MVIMPACT_ACQUIRE_DATA_DIR was not correctly evaluated on (all shipped packages) Windows. As a consequence it e.g. was not possible to configure the log-output based on that variable. - Without elevated rights DirectShow related information was not available. Now there (mvDeviceConfigure) is a hint on how to get this information. The menu item to change the DirectShow friendly name is only enabled, if the application is running with elevated rights and the device is already registered as DirectShow device. - When a mvBlueFOX3 booted with bootprogrammer firmware version 0.33.1693.2, the (all shipped packages) device could not be initialized to update the firmware, if device specific settings were present on the host system. 25.11.2020 2.40.3 UPDATES: - When running 'mvDeviceConfigure' with the 'hidden' parameter no more progress dialogs (mvDeviceConfigure) will pop up. - Calling acquisitionStop() for GEV devices took up to 50ms on Linux. (mvGenTLProducer.cti) BUGS FIXED: - When an error in the LSFR pattern was detected during the first iteration of the GEV (mvGenTLProducer.cti) packet size auto-negotiation when 'AutoNegotiatePacketSizeMode' was set to 'HighToLow' (the default) the algorithm did terminate and 576 was used as the packet size potentially resulting in poor performance. - GEV multicast reception of streaming data did not work on Linux systems. (mvGenTLProducer.cti) (Bug introduced in 1.12.59) - When constantly starting and stopping the acquisition on Linux systems sometimes even (mvGenTLProducer.cti) though the device did start streaming data nothing was received by the driver. - Clicking on the 'Enable AWB' checkbox of the AOI wizard could result in a crash. (wxPropView) 09.11.2020 2.40.2 UPDATES: - Only the first call to 'DMR_InitVideoStreamAPI' will result in an actual load (mvDeviceManager-lib) attempt to the FFmpeg libraries. Previous releases did result in a failure message when the libraries could not be found on every function call. BUGS FIXED: - When running an mvIMPACT Acquire application as root and then later trying to run (all shipped packages for Unix/Linux systems) another mvIMPACT Acquire application as a non-root user the application did not start until the file /dev/shm/sem.4ED0DA5F-C112-49a2-A313-E80B9F259830 has been removed from the system. 22.10.2020 2.40.1 NEW FEATURES: - All mvIMPACT Acquire packages for Linux will also use OpenMP for internal image (all shipped packages for Unix/Linux systems) processing algorithms. Displaying image in wxPropView will also make use of OpenMP now. See 'Known Issues -> Linux' for additional details and how this might affect your application. - The 'FirmwareUpgrade' console application is capable of updating the firmware of (all shipped packages for Unix/Linux systems) mvBlueFOX3 devices now. - 'CaptureToOpenGLMemory' example added to the documentation of the C++ API. This (mvIMPACT_Acquire_API_CPP_manual) can serve as a starting point for displaying images using OpenGL. BUGS FIXED: - On ARM platforms only 1000 images could be captured from MATRIX VISION GEV devices (all shipped packages for GenICam compliant devices, Linux/ARM) until an annoying overlay was displayed. (Bug introduced in version 2.40.0) - On Windows platform the gray values of pixels did not match the exact position in the (wxPropView) image due to unprecise scaling in case of high zoom levels. 15.10.2020 2.40.0 NEW FEATURES: - The .NET Standard 2.0 build of the mvIMPACT Acquire .NET runtime has been added to (all shipped packages for Unix/Linux systems) all Linux installers. This runtime will allow to write .NET Core applications with mvIMPACT Acquire. See .NET API manual for details. - Added the ability to store image metadata beside the image in a *.xml file. This (wxPropView) feature is available for 'Snapshot' and 'Hard Disk' mode. - Added 'CorrectionModeReverseX' and 'CorrectionModeReverseY' properties to flat field (all shipped packages) filter. - New example added to all packages: 'TimestampFeatures'. (all shipped packages) - Added updated versions of the GEV filter driver that provide additional analysis (mvGigECapture.sys, version 2.4.0.68) data and a slightly optimized default behaviour of the packet resend algorithm (mvGigECapture2.sys, version 3.2.0.68) especially for LAG configurations. - Property 'mvLinkCommandTimeoutCheckGranularity' added to 'DeviceModule' API. (all shipped packages) - The 'ColorTwist' is available for every platform now thus also for ARM. (all shipped packages) - Added API functions to pause and resume compressed video stream recording. (all shipped packages) - The tooltips are now visible twice as long. That should make it easier to read (wxPropView, mvDeviceConfigure) through the longer information. UPDATES: - Internal migration to libexpat 2.2.9. (all shipped MSI-based packages) BUGS FIXED: - Gains were not taken into account for Bayer to mono conversions within the de-Bayer (all shipped packages) filter on Linux or 64-bit Windows systems. - When using version 3.x of the FFmpeg libraries together with mvIMPACT Acquire H.264 (mvDeviceManager-lib) or H.265 encoding the resulting files did use a different encoder than selected. This was caused by a major change in FFmpeg with release 4.0. Therefore the support for FFmpeg 3.x was removed from mvIMPACT Acquire. - The FFmpeg libraries were not detected on Linux. (mvDeviceManager-lib) - The experimental Birger EF-232 mount interface provides correct focus values after (all shipped packages) initialization. - When the same producer file name was detected in more than a single location it was (mvGenTLConsumer-lib) loaded into the process multiple times. - When the final output pixel format was one of the more exotic YUV formats the Bayer (all shipped packages) filter did not process images carrying a Bayer attribute. So the resulting image did never carry any color information. - Finding the system's libusb did not work correctly on Debian systems. (mvGenTLProducer.cti) - Calling acquisitionStop() for GEV devices took up to 500ms on Linux and Windows (mvGenTLProducer.cti) systems not utilizing the NDIS filter driver. - Using the 'Quick Setup Wizard' on ARM based platforms could result in crashes. (wxPropView) - The 'Quick Setup Wizard' did not always configure the highest possible frame rate (wxPropView) when the 'Highest Speed' option was selected. - In some cases the 'Quick Setup Wizard' disabled the camera's AEC once it was (wxPropView) enabled in the wizard before. - On Linux 'Update firmware from online package' did use a wrong directory to store (mvDeviceConfigure) the package and therefore the update did not work. 15.07.2020 2.39.0 NEW FEATURES: - The 'GenICam' namespace now contains the full SFNC 2.6 feature set. (mvIMPACT_acquire_GenICam.h) - 'CaptureToMegaBuffer' example added to the documentation of the C++ API. This (mvIMPACT_Acquire_API_CPP_manual) can serve as a starting point for making optimal use of the mvBlockscan mode. - New command line parameter added to mvIPConfigure: 'log_file' which allows to (mvIPConfigure) specify a log file that will contain the output, after the tool is closed. - mvIMPACT Acquire learned how to connect to the FFmpeg project. As a result with (all shipped packages) an installed version of FFmpeg present on the system compressed video streams can now be created. Have a look at the FFmpeg section in the 'Legal Notice' chapter of the SDK manual for details. - All Windows binaries are shipped with a digital signature now! (all shipped MSI-based packages) BUGS FIXED: - Capturing images into user supplied memory could crash for various pixel and test (mvVirtualDevice-lib) modes(vdtmLeakyPixelTestImageMono8Bayer, vdtmHotAndColdPixelTestImageRGB888Packed as well as all packed RGB/BGR formats and test modes). - Calling 'DMR_AllocImageBuffer' with an invalid/unsupported pixel format could result (mvDeviceManager-lib) in a crash. - In some cases using the 'forceAutoConfigurePersistent' and 'forceAutoConfigureDHCP' (mvIPConfigure) command line parameters did not work correctly. - Using the 'Polarized Data Extraction' filter mode 'PseudoColorRepresentation' (all shipped packages) on Linux systems could result in a crash. 10.06.2020 2.38.0 NEW FEATURES: - A .NET Standard 2.0 build of the mvIMPACT Acquire .NET runtime has been added to (all shipped MSI-based packages) all Windows installers. This runtime will allow to write .NET Core applications with mvIMPACT Acquire. See .NET API manual for details. - 'Synchronous Method Execution' check-box added to the 'Options' dialog. The new (wxPropView) default is 'Off', the previous behaviour was 'On'. When 'On' methods in the property grid will be executed synchronously thus will block all other window messages until the method has been executed thus will e.g. also block the image display. - Three more modes added to 'Polarized Data Extraction' filter. (all shipped packages) 'DegreeOfPolarization': The degree of the polarization in the image is visualized. 'AngleOfPolarization': The angle of the polarization in the image is visualized. 'PseudoColorRepresentation': The degree and the angle of the polarization in the image are used to calculate a pseudo-color image. - 'ContinuousCaptureFFmpeg' example added to the documentation of the C++ API. This (mvIMPACT_Acquire_API_CPP_manual) can serve as a starting point for creating compressed video streams. - New command line parameter added to mvDeviceConfigure, mvGigEConfigure and (mvDeviceConfigure) mvIPConfigure: 'hidden' which might be useful e.g. during silent installation (mvGigEConfigure) procedures as it will not show the splash screen or the application window while the (mvIPConfigure) application can still be used to install or remove the filter driver. - Experimental support for Birger EF-232 mount added to (all shipped packages) mvIMPACT::acquire::GenICam::labs namespace. - 'GammaInverter' property added to LUT filter. (all shipped packages) UPDATES: - Updated integrated U3VBootProgrammer to 0.38.2344.2. (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - From this version onwards the mvIMPACT Acquire .NET API be built for the target (all .NET related libraries and projects) framework 4.5.1. Previous versions did target version 3.5 of the .NET framework which was released with Visual Studio 2008. Since modern Windows 10 systems are no longer shipped with the .NET 3.5 framework using the mvIMPACT Acquire .NET runtime therefore became impractical. .NET 4.5.1 was introduced with Visual Studio 2013 so should work flawless on most systems. Applications still need .NET 3.5 have to use the .NET API shipped with mvIMPACT Acquire 2.37.1 or below. - During installation and removal of the GEV filter driver the new 'hidden' parameter (mvGenTL_Acquire*.exe) is passed to mvGigEConfigure. The tool therefore will not be visible while the installation is running. - The 'workerPriority' property of the SystemSettings class as well as the enumeration (all shipped packages) 'TThreadPriority' has been removed from the public interface. It had been declared deprecated in 2.24.0 in 2017. See 'Porting Existing Code' in the corresponding API manual for details. BUGS FIXED: - Trying to open a GenICam device with an incorrect 'AcquisitionMode' property setup (wxPropView) could result in a crash. - The DirectShow interface finally works with VLC versions >= 3.0.0 now. (mvDeviceManager-lib) - If the 'FFC Calibration'-tab of the 'AOI Wizard' is selected for a monochrome camera (wxPropView) wxPropView might crash. - If images are saved using the "Snapshot To Hard Disk" or "Hard Disk Recording" mode (wxPropView) the resulting images were stored in the wrong file format. (Bug introduced in version 2.37.0) - Downloading firmware files on Linux systems did not work as a result of an incorrect (mvDeviceConfigure) path used to store the downloaded file. 19.03.2020 2.37.1 NEW FEATURES: - The 'Quick Setup Wizard' allows to define if the color processing should be done (wxPropView) within the camera or on host side now. - Besides 8- and 10-bit pixel formats the 'Quick Setup Wizard' supports 12-bit pixel (wxPropView) formats for devices utilizing a Sony IMX sensor. This will be the new 'Best Quality' setting for the previously mentioned Sony IMX sensors now. - wxPropView's 'Update Info' dialog allows to download and update each MATRIX VISION (wxPropView) software package by just a few clicks now. - Color correction matrix for Sony IMX540, IMX541, IMX542 based products added. (all shipped packages) BUGS FIXED: - When not calling mvDispSetBitmapRectangle or ImageDisplay::SetDisplayRectangle no (mvDisplay-lib) image was displayed(or the display image in fact had a size of 0 by 0). (Bug introduced in version 2.37.0) - The 'PtpEnable' property was incorrectly mapped as an integer property while in fact (mvIMPACT_acquire_GenICam.h) it is a 'PropertyIBoolean'. (mv.impact.acquire.dll) - The 'GevGVCPExtendedStatusCodesSelector' property was incorrectly mapped as a (mvIMPACT_acquire_GenICam.h) 'PropertyIBoolean' while in fact is an enumerated property. (mv.impact.acquire.dll) 03.03.2020 2.37.0 NEW FEATURES: - Initial version of the Python API manual for mvIMPACT Acquire added. See (all shipped packages) mvIMPACT_Acquire_API_PYTHON_manual.chm or https://www.balluff.com/en-de/online-manuals-mv for additional details. - Ported all code snippets from the C++ documentation to Java and Python. (all shipped packages) - The Java wrapper for mvIMPACT Acquire added in version 2.36.0 is now shipped for (all shipped packages) x86 platforms as well. - The Windows version of wxPropView supports different scaling modes now. Right-click (wxPropView) on the display and select 'Scaling Mode' from the context menu. - Storing the current image during the acquisition is possible now. Either right-click (wxPropView) on the display and select 'Save Current Image' or 'Copy Current Image To Clipboard' from the context menu or press 'CTRL+C' to immediately copy the current image into the clipboard. - Storing images via a single hit on the space bar is possible now as well. (wxPropView) Just enable the 'Snapshot' mode via the 'Setup Snapshot Mode' option from 'Capture' menu. Select the display window you want to capture snapshots from by left-clicking into the display area. - The 'Quick Setup Wizard' allows to define if the color processing should be done (wxPropView) within the camera or on host side now. - Defective pixel filter: Property 'DefectivePixelsMaxDetectionCount' added. See (all shipped packages) documentation of the property for additional information. - The way the packet size auto negotiation for GEV devices is handled can be configured (mvGenTLProducer.cti) by the user now. - Added 'AutoNegotiatePacketSize' and 'AutoNegotiatePacketSizeMode' property to mvIMPACT::acquire::Device (C++) and (mvIMPACT_acquire.h) mv.impact.acquire.Device (.NET) (mv.impact.acquire.dll) UPDATES: - Internal migration to Doxygen 1.8.17. - Improved error recovery when cameras did send data with non-continuous block IDs. (mvGigECapture.sys, version 2.3.9.67) (mvGigECapture2.sys, version 3.1.9.67) - Some very small changes to allow compilation with the latest version of Visual Studio (exampleHelper.h) 2019 with /std:c++17 and /std:c++latest. - Updated integrated U3VBootProgrammer to 0.37.2227.2. (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - From this version onwards the official support for Linux 32-bit x86/i386 systems as (all shipped packages for Unix/Linux systems) well as Linux ARMsf will end. Until further notice the required installation packages will still be build but will only be provided on special request. - Removed support for features that have been declared deprecated for centuries: C++: FunctionInterface::isRequestOK: Use Request::isOK instead. (mvIMPACT_acquire.h) FunctionInterface::saveSystemToDefault: Use FunctionInterface::saveSettingsToDefault instead C: 'DMR_SaveSystemToDefault': This function is no longer needed since calling (mvDeviceManager.h) 'DMR_SaveSettingToDefault' also stores the data previously stored by 'DMR_SaveSystemToDefault' since version 1.12.58. 'DMR_UpgradeDeviceFeatures': This function did never do anything useful! Simply remove all occurrences! - Performing a white balance calibration with 'WBAoiMode' set to 'amCentered' uses (all shipped packages) a center quarter of the original image instead of just 50 by 50 pixels now. - Lists without any visible children will become invisible as well now in the property (wxPropView) grid control. - The property grid will remember its state for each device when switching between (wxPropView) devices now. - The auto negotiation process of the MTU for GigEVision devices starts with the (mvGenTLProducer.cti) network interface's MTU and iterates downwards now. Until now it worked reverse by starting at the minimal value and iterating upwards. BUGS FIXED: - Calling 'mvDispSetInterpolationMode' (C-API) or 'ImageDisplay::SetInterpolationMode' (mvDisplay-lib) (other APIs) after calling 'mvDispSetImage' (C-API) or 'ImageDisplay::SetImage' (other APIs) could result in the image being displayed with an incorrect pitch. - Using interpolation modes different from 'IM_NEAREST_NEIGHBOUR' in combination with (mvDisplay-lib) dynamic changes in the AOI and pixel formats could result in incorrectly displayed images and even crashes. - Defective pixel filter: When calibrating a sensor directly after initialising a (all shipped packages) device before calling 'Reset Calibration Data' at least once the list of detected defective pixels did always contain pixel 0/0. - When 'DMR_ImageRequestSingle' or 'imageRequestSingle' of the FunctionInterface did (mvGenTLConsumer-lib) fail calling 'AcquisitionStop' afterwards did never return. - When switching between devices using the combo-box in the upper left section of the (wxPropView) window wxPropView could crash randomly. - The camera based color correction configured by the 'Quick Setup Wizard' did not (wxPropView) work if the camera was transmitting Bayer pixel data. - The 'Quick Setup Wizard' could crash when started by using the "Show 'Quick Setup' (wxPropView) Wizard now"-Button of the "Welcome to the Quick Setup Wizard" dialog. (Bug introduced in version 2.36.0) - On Linux using sliders with logarithmic behaviour in the property grid could result (wxPropView) in the application to lock up. - The LUT Wizard allowed to check the 'Enable'-check-box even if the selected LUT could (wxPropView) not be enabled due to another LUT which is currently active and using the same resources on the device. - When deriving from mvIMPACT.acquire.ComponentCallback and application did crash when (Python API) the 'execute' method was called for the first time. - The 'state' property of the class 'mvIMPACT.acquire.DigitalOutput' could not be (Python API) written. - Functions like 'mvIMPACT.acquire.FunctionInterface.getCurrentRequestLayout' and some (Python API) versions of 'mvIMPACT.acquire.FunctionInterface.imageRequestSingle' and 'mvIMPACT.acquire.ImageDisplay.GetImage' could not be called. 19.12.2019 2.36.0 NEW FEATURES: - Initial version of a full Java wrapper for mvIMPACT Acquire added. See product (all shipped packages) specific manuals as well as the mvIMPACT_Acquire_API_JAVA_manual.chm or https://www.balluff.com/en-de/online-manuals-mv for additional details. - The mvIMPACT Acquire Python wrapper now exposes the same exception class hierarchy (Python API) as the C++/C# API thus not only 'acquire.ImpactAcquireException' objects but also all the derived types can be caught. - New functions added to API: - C++ API: mvIMPACT::acquire::WhiteBalancer::highQualityWhiteBalance (mvIMPACT_acquire.h) - .NET API: mv.impact.acquire.WhiteBalancer.highQualityWhiteBalance (mv.impact.acquire.dll) Those convenience functions allow to perform a white balance calibration using the highest possible bit depth for the used device to get more precise correction gain values. UPDATES: - If possible the 'Quick Setup Wizard' will use the device's color transformation (wxPropView) feature to apply color corrections and saturation if available. This reduces load on the host CPU then. - The overall size of the source code of the mvIMPACT Acquire Python wrapper has been (Python API) reduced to about a third of its previous size thus should be easily digestible by smaller systems as well now. - mvHYPERION Linux kernel driver and the respective installers now support kernel 5.3. (low level mvHYPERION driver, Linux) CHANGED BEHAVIOUR: - Some incompatible changes have been applied to the Python interface. Please refer (Python API) to the migration guide in the 'Python developers' chapter of your product. E.g.: https://www.balluff.com/en-de/online-manuals-mv/mvBlueCOUGAR-X/Python_page_0.html - The directory containing the Python interface moved from 'mvIMPACT_Python' to (Python API) 'LanguageBindings/Python'. - The C++ member mvIMPACT::acquire::CameraSettingsBlueDevice::autoControlParameters (mvIMPACT_acquire.h) became private like in all other language bindings. Use the corresponding 'getter' instead. - When using the defective pixel filter in 'dpfm3x1Average' the algorithm doing the (all shipped packages) actual pixel correction can deal with locally connected clusters of defective pixels. - When a MATRIX VISION device offers defective pixel correction and this correction is (all shipped packages) active then the driver based defective pixel correction filter is no longer switched on automatically when defective pixel data is present on the device. - In case a U3V capture buffer could not be queued(e.g. because the system is running (mvGenTLProducer.cti) low on memory) the request object will be returned with the 'requestState' property set to 'rrNotEnoughMemory' instead of 'rrRequestAborted' now. BUGS FIXED: - Potential blue screen (BSOD) when working with the NDIS filter driver on Windows (mvGigECapture.sys, version 2.3.7.66) when resend commands were initiated by the filter driver while new data was received (mvGigECapture2.sys, version 3.1.8.66) in parallel. - Potential crash when building Mono12Packed_V1/V2 buffers with Bayer attributes and (all shipped packages) and a width not divisible by 2. - Potential crashes in the channel split filter when working with (all shipped packages) 'ibpfYUV411_UYYVYY_Packed' the format on an image with a width not divisible by 4. - Potential crash when feeding buffers with an odd width into the Bayer conversion (all shipped packages) filter with the 'RawToPlanes' mode selected. - Detection of defective pixels did sometimes produce unexpected results when the (all shipped packages) illumination was not perfect especially when in a color image one channel was in saturation. (Bug introduced in version 2.22.1) - Opening the 'Quick Setup Wizard' for a GenICam device which did not support the (wxPropView) Gamma feature the wizard closed immediately without further notice. (Bug introduced in version 2.35.0) - Images using the 'ibpfMono12Packed_V1' format could not be displayed. (wxPropView) (Linux only) - After changing parameters in the 'LUT Wizard' and selecting a different device the (wxPropView) 'LUT Wizard' showed LUT values of the previously used device. - Downloading firmware automatically did not work because of missing write rights to (mvDeviceConfigure) MVIMPACT_ACQUIRE_DIR as a result of missing elevated privileges. The firmware will be downloaded to MVIMPACT_ACQUIRE_DATA_DIR/FirmwareUpdates from now. (Windows only) (Bug introduced in version 2.35.0) - Potential crashes when using user supplied capture memory in combination with image (mvVirtualDevice-lib) processing like the defective pixel filter. - Fixed a memory leak of about 256 bytes per network interface when GEV interfaces have (mvGenTLProducer.cti) been enumerated. This leak only occurred once per dlopen/LoadLibrary of the 'mvDeviceManager-lib'. (Bug introduced in version 2.33.0) - Calling 'TLOpen' after calling 'GCGetInfo' did return 'GC_ERR_RESOURCE_IN_USE'. (mvGenTLProducer.cti) (Bug introduced in version 2.35.0) - Under some conditions the Linux libusb driver put the event endpoint in the stalled (mvGenTLProducer.cti) state without canceling queued event buffers which was causing a 'USBDEVFS_CLEAR_HALT for active endpoint 0x82' message in the kernel debug messages. - The GenICam registers for the 'InterfaceID' feature could just store 128 bytes which (mvGenTLProducer.cti) was not enough on some systems. This value has been increased to the MAX_PATH value now. - Requesting images using the 'ircmTrial' sometimes did return incorrect information (mvGenTLConsumer-lib) when the device would return a Bayer format. - Sometimes when reading/writing properties from 2 threads (e.g. when processing an (mvGenTLConsumer-lib) event callback while also setting a properties value) the write access to the property has been ignored. - Calling mvIMPACT::acquire::helper::ThreadSafeQueue::terminateWait did not always (mvIMPACT_acquire_helper.h) wake up mvIMPACT::acquire::helper::ThreadSafeQueue::pop when both functions where called more or less in parallel. 02.10.2019 2.35.0 NEW FEATURES: - The mvIMPACT Acquire Python wrapper is delivered for ARMhf and ARM64 platforms now. (all shipped packages for Unix/Linux systems) - mvDeviceConfigure now also informs about an available firmware update for mvBlueFOX2 (mvDeviceConfigure) devices. - When passing 'online' as the value for the 'fw_file' parameter the latest firmware (mvDeviceConfigure) version from the MATRIX VISION website will be downloaded and stored on supported devices. This can e.g. be used to update ALL devices connected to a system without user interaction with the latest firmware available. - Initial version of the AOI Wizard which will allow to configure AOIs for many (wxPropView) different features like auto exposure and auto gain controllers, white balance calibration or flat field filter. UPDATES: - PFNC format YCbCr2020_411_8_CbYYCrYY will be treated as 'ibpfYUV411_UYYVYY' (mvGenTLConsumer-lib) YCbCr601_422_8, YCbCr709_422_8, YCbCr2020_422_8 will be treated as 'ibpfYUV422Packed' and YCbCr601_422_8_CbYCrY, YCbCr709_422_8_CbYCrY, YCbCr2020_422_8_CbYCrY will be treated as 'ibpfYUV422_UYVYPacked' now thus data in these formats can be fully dealt with. - If possible the 'Quick Setup Wizard' will use the device's gamma feature if (wxPropView) available. This reduces load on the host CPU then. - Internal migration from swig 3.0.12 to 4.0.1. CHANGED BEHAVIOUR: - mvIMPACT Acquire is not statically linked with libstdc++ and libgcc anymore, so (all shipped packages for Unix/Linux systems) the Linux systems have to use at least the version of gcc mvIMPACT Acquire has been compiled with. This means in detail: - gcc 4.8.5 (GLIBCXX 3.4.19, libstdc++ 6.0.19) for x64 and x86_64 packages. - gcc 4.9.4 (GLIBCXX 3.4.20, libstdc++ 6.0.20) for ARMsf and ARMhf packages. - gcc 4.9.4 (GLIBCXX 3.4.20, libstdc++ 6.0.20) for ARM64 packages. See 'Building, linking and running...' chapter in the 'Supported compilers' section for additional details. - A firmware update from the Internet can be enforced even if the firmware version is (mvDeviceConfigure) the same as the one currently running on the device. This can e.g. be useful to get rid of any user sets stored on the device. - mvDeviceConfigure no longer enforces elevated privileges on Windows systems. Most (mvDeviceConfigure) operations (like firmware updates for GenICam devices) can be done as a normal user now. Whenever elevated privileges are required but not available the application will inform the user. - Some incompatible changes have been applied to the Python interface. Please refer (Python API) to the migration guide in the 'Python developers' chapter of your product. E.g.: https://www.balluff.com/en-de/online-manuals-mv/mvBlueCOUGAR-X/Python_page_0.html BUGS FIXED: - Calling 'GCGetInfo' without calling 'TLOpen' before did result in a crash! (mvGenTLProducer.cti) (Bug introduced in version 2.33.0) - In very rare cases the 'State' property was not set to 'Absent' when a U3V device was (mvGenTLProducer.cti) unplugged on Windows when it had been unplugged at least one time before. - Common module including some helper functions of the mvIMPACT Acquire Python wrapper (all shipped packages) is now installed in a Python 2.7 and 3.7 compatible way. - Exception handling in Python API was broken on Windows systems. When an mvIMPACT (setup.py) Acquire related exception was raised the application did terminate. (Bug introduced in version 2.22.0) - When the width of the AOI is smaller than 640 the host based AEC/AGC will be used (mvBlueFOX-lib) for mvBlueFOX-x02dx devices now even if 'DeviceSpecific' has been selected. This is a little slower but the 'DeviceSpecific' version does not work then due to a sensor limitation. - Devices with whitespace characters in their serial number can be initialised using (wxPropView) wxPropView. - mvDeviceConfigure correctly informs about an available firmware update if a package (mvDeviceConfigure) using the old naming scheme is found (_Update-a.b.c.d.mvu) containing a more recent firmware for a detected device. (Bug introduced in version 2.31.0) - Calling mvIMPACT::acquire::Property::readS or mvIMPACT::acquire::Property::readSArray (mvIMPACT_acquire.h) did never terminate if the returned string was longer than 8192 characters. - mvIMPACT::acquire::EnumPropertyF::getTranslationDictValue did return the internal (mvIMPACT_acquire.h) error code casted to a double instead of the requested value. - Requesting images using the 'ircmTrial' sometimes did return incorrect information (mvGenTLConsumer-lib) e.g. a different pixel format as an internal exception was raised by e.g. the format convert filter. (Bug introduced in version 2.22.0) - Some interface functions (TLIMV_MACFromSerial, TLIMV_IsValidIPv4Address, (mvGenTLProducer.cti) TLIMV_ForceIP and TLIMV_DoAddressesMatch) where no longer exported on Linux systems. (Bug introduced in version 2.33.0) 09.08.2019 2.34.0 NEW FEATURES: - API added to configure the enumeration behaviour of third party GenTL producer (mvGenTLConsumer-lib) libraries. See 'General SDK functionality' in the 'Typical Usage Scenarios And (wxPropView) Example Applications' section of the SDK manual for details. - The 'GenICam' namespace now contains the full SFNC 2.5 feature set. (mvIMPACT_acquire_GenICam.h) - New overload for mvIMPACT::acquire::Method::call/mv.impact.acquire.Method.call (mvIMPACT_acquire.h) added that accepts a list of strings. (mv.impact.acquire.dll) - New example added to all packages: 'GenICamI2cUsage'. (all shipped packages) UPDATES: - wxPropView became 'DeviceRegistersValid' aware. (wxPropView) - Improved compatibility with 3rd party GenTL producers. (mvGenTLConsumer-lib) - Removed all occurrences of 'std::auto_ptr' since this class has been deprecated in (all shipped packages) C++11 and removed in C++17 and therefore applications built with up to date compilers did receive a lot of warnings. - Improved and enhanced 'Typical Usage Scenarios And Example Applications' chapter. (all shipped packages) CHANGED BEHAVIOUR: - From this version onwards mvBlueLYNX-X, mvBlueLYNX-M7 and mvBlueCOUGAR-P devices (all shipped packages for GenICam compliant devices) will no longer be supported. As a consequence the following example applications have been removed from the SDK: 'CaptureFromMultipleChannelsUsingMultipleSettings', 'SynchronousCaptureMultipleInputs' and 'SynchronousCaptureMultipleInputsFLTK'. The class 'IOSubSystemBlueCOUGAR' has also been removed. Use 'IOSubSystem' instead. - From this version onwards PPC based platforms will no longer be supported. (all shipped packages) - GEV adapters will report a more unique interface ID now. It used to be the MAC (mvGenTLProducer.cti) address. Weird systems reporting the same MAC address for multiple adapters however did enumerate devices on the first of these adapters only then. - Known technologies from third party GenTL producers mvIMPACT Acquire has built-in (mvGenTLConsumer-lib) support for will be ignored by default now in order not to pollute the list of devices with duplicated entries. Using the new API these can enabled by the user. - When running Windows 8 or greater a reboot of the system after installing the (mvGenTL_Acquire*.exe) mvGenTL_Acquire package is no longer necessary. In previous versions when not logging on as an administrator AFTER the reboot the NDIS filter driver for GigE Vision devices was not properly installed. - Removed 'PowerDownTest' example from mvBlueFOX Linux installation packages. Please (mvBlueFOX-*.tgz) refer to the 'Typical Usage Scenarios And Example Applications' in the documentation instead. - Merged the Linux example 'LiveSnap' with the 'ContinuousCapture' example. Now there (all shipped packages) is a common 'ContinuousCapture' example. - 'LiveSnapFLTK' became 'ContinuousCaptureFLTK'. (all shipped packages for Unix/Linux systems) BUGS FIXED: - When 2 or more processes using mvIMPACT Acquire have been started in parallel this (all shipped packages) could result in all processes to lock up when accessing the *.bak files. (Bug introduced in version 2.19.0) - Potential crash on systems with more logical CPU cores than the height of the current (all shipped packages) image in the image processing pipeline. - The functions 'acquistionStart' and 'acquisitionStop' did not always propagate all (mvGenTLConsumer-lib) internal errors up to the application. (mvGenTLProducer.cti) - When a GenTL producer did report an invalid image size that was larger than the (mvGenTLConsumer-lib) buffer currently allocated this buffer was incorrectly been re-allocated without revoking it from the GenTL producer resulting in a crash the next time this buffer was queued. - Sometimes when starting the application for the very first time no images were (wxPropView) displayed while the status bar did suggest the acquisition is running just fine. (Bug introduced in version 2.32.0) - mvVirtualDevice displays BMP files with a custom palette correctly now. (mvVirtualDevice-lib) - In some cases "Junk After Document Element" messages showed up in mvDeviceConfigure (mvDeviceConfigure) once the "Firmware Update from Online Package" option has been used. - In some cases the LostImageCount property showed negative values once the (mvBlueFOX-lib) RequestCount value was increased during a running acquisition. - Device specific AGC/AEC mode features were not always properly updated inside the (mvBlueFOX-lib) device. - 'DesiredAverageGreyValue' for AGC/AEC was not taken into account for mvBlueFOX-x02dx (mvBlueFOX-lib) devices. 26.06.2019 2.33.1 UPDATES: - Improved compatibility with 3rd party GenTL producers. (mvGenTLConsumer-lib) 05.06.2019 2.33.0 NEW FEATURES: - The defective pixel filter now supports also the following pixel formats: (all shipped packages) BGR888Packed, RGB888Packed, RGB101010Packed, RGB121212Packed, RGB141414Packed, RGB161616Packed, RGBx888Packed, YUV444_UYVPacked, YUV444_UYV_10Packed, YUV444Packed and YUV444_10Packed. - New correction mode added to defective pixel filter: (all shipped packages) dpfmReplaceDefectivePixelAfter3x3Filter. See SDK documentation for additional details. - New header file added to C++ interface: mvIMPACT_acquire_helper.h. This file adds the (all shipped packages) classes 'mvIMPACT::acquire::helper::RequestProvider' and 'mvIMPACT::acquire::helper::ThreadSafeQueue' to the public interface. - Added 64-bit Borland import libraries to 32-bit installers as well: (all shipped MSI-based packages) mvDeviceManagerb.lib and mvDisplayb.lib. - PFNC formats YCbCr411_8_CbYYCrYY, YCbCr601_411_8_CbYYCrYY and YCbCr709_411_8_CbYYCrYY (mvGenTLConsumer-lib) will be treated as 'ibpfYUV411_UYYVYY_Packed' now thus data in these formats can be fully dealt with. BUGS FIXED: - When running out of USB kernel memory on Linux queuing a request can fail. However (mvGenTLProducer.cti) it took 'ImageRequestTimeout_ms' for this unsuccessful operation to return and in case this timeout was INFINITE the operation did never return. (Linux only) - BF3-3 and BF3-4 devices will also be recognized as being 'Quick Setup Wizard' (wxPropView) compatible. - Switching on 'Gamma' in the 'Quick Setup Wizard', leaving it with 'Ok' and (wxPropView) re-entering it switched off the gamma control but did show the 'Gamma' button as being active. - LUT wizard displays the interpolated LUT values and not only the LUT's sampling (wxPropView) points in case of interpolated LUTs - Calling 'DMR_SaveImageBuffer' with 'iffAuto' and a *.bmp, *.jpg or *.jpeg file (mvDeviceManager-lib) extension did result in the creation of files not readable for almost every other image viewer. - Calling 'DMR_UpdateDeviceList' when new interfaces have appeared since the last call (mvGenTLConsumer-lib) could result in inconsistent interface to device reports (e.g. in wxPropViews 'Info' dialog). - The NeuroCheck 6.x interface did crash when enumerating third party interfaces within (mv.impact.acquire.NeuroCheck6.dll) NeuroCheck's device manager. (mv.impact.acquire.NeuroCheck6_1.dll) (Bug introduced in version 2.31.0) - On Windows when installing the mvGenTL-Acquire package and then restarting the system (all shipped MSI-based packages) and logging in with a non administrator account GEV and U3V interfaces where not be enumerated. Therefore it seems like no devices are connected to the system. UPDATES: - Internal migration from (all shipped packages for Unix/Linux systems) - gcc 4.2.4 to gcc 4.8.5 for x64 and x86_64 packages. - gcc 4.6.3 to gcc 4.9.4 for ARMsf and ARMhf packages. - gcc 4.8.3 to gcc 4.9.4 for ARM64 packages. See 'Building, linking and running...' chapter in the 'Supported compilers' section for additional details. - Internal migration from swig 2.0.12 to 3.0.12. - The status bar tooltip introduced in version 2.32.0 can be switched on and off now (wxPropView) within the 'Settings -> Options' dialog and will only be displayed if the mouse stays at least one second on the status bar. CHANGED BEHAVIOUR: - The socket based GigE Vision driver will no longer start in the middle of a running (mvGenTLProducer.cti) block when it did run out of capture buffers and gets a fresh one in between. When not listening on an LAG group it will now wait for the next start of a block. On LAG groups it will start with packets with an ID smaller than the value of 'mvResendCaptureWindowSize'. - When a GenICam device returns an error in the middle of a 'load setting' operation (mvGenTLConsumer-lib) the load operation as a whole no longer fails but only the particular feature is not written then. 08.05.2019 2.32.0 NEW FEATURES: - mvIMPACT Acquire supports all 3rd party devices and 3rd party GenTL producers now (mvGenTLConsumer-lib) even though right now some of them will only work for a trial period. Get in touch (mvGenTLProducer.cti) with us if you have questions about that. - New error codes added: DMR_BUSY and DMR_OUT_OF_MEMORY. (all shipped packages) - New function added: 'OBJ_GetBinaryEx'. See PropertyS::readBinary for additional (mvDeviceManager-lib) information! (mvIMPACT_Acquire.h) - Added 64-bit Borland import libraries: mvDeviceManagerb.lib and mvDisplayb.lib. (all shipped MSI-based packages) - wxPropView shows a 'Welcome' dialog before the 'Quick Setup' wizard is opened now to (wxPropView) allow the user to show, not to show or disable the 'Quick Setup' wizard completely. - Added 'Default Acquisition Start/Stop Behaviour' menu. (wxPropView) - The defective pixel filter learned how to process the following pixel formats: (all shipped packages) BGR888Packed, RGBx888Packed, RGB888Packed, RGB101010Packed, RGB121212Packed, RGB141414Packed, RGB161616Packed, YUV444_UYVPacked, YUV444_UYV_10Packed, YUV444Packed, YUV444_10Packed. - Test image format 'vdtmHotAndColdPixelTestImageRGB888Packed' added. (mvVirtualDevice-lib) UPDATES: - Improved translation of GenTL error codes into mvIMPACT Acquire error ones. (all shipped packages) - Improved cache efficiency when accessing GenICam properties containing binary data. (mvPropHandling-lib) (mvGenTLConsumer-lib) - In order to increase the awareness for the 'ImageRequestTimeout_ms' property (wxPropView) wxPropView will warn when buffer timeouts occur and will recommend to adjust the timeout property then. - All files (kernel mode and user mode) are signed with a DigiCert EV certificate now (all shipped MSI-based packages) as the new COMODO certificate still resulted in Windows SmartScreen warnings. (Windows only) - All installer scripts report errors and warnings in case of issues during (all shipped packages for Unix/Linux systems) installation and their result at the end of the installation. CHANGED BEHAVIOUR: - The default value of 'ImageRequestTimeout_ms' has been changed from 2000 to 0 (infinite). In very rare cases this might result in the function 'imageRequestWaitFor' not returning anymore depending on how the application is written. See 'Calling 'imageRequestWaitFor' never returns / An application no longer terminates after upgrading to mvIMPACT Acquire 2.32.0 or greater' in the 'Known Issues' section of the documentation to make sure this does NOT affect you! - Examples for Borland C++ Builder are no longer shipped as part of the installation. (all shipped MSI-based packages) However Borland Makefiles for the example applications can be generated with CMake now. See documentation in the 'building and linking' section for details. BUGS FIXED: - wxPropView did not scale LUT values once they were copied within the LUT wizard. (wxPropView) - The LUT wizard calculates the correct gamma correction values instead of it's inverse (wxPropView) values now. - Firmware downgrade notifications showed incorrect version numbers in some cases. (mvDeviceConfigure) - mvBlueFOX devices with an MT9M021 sensor(e.g. mvBlueFOX-ML/IGC202bC) sometimes did (mvBlueFOX-lib) not apply the gain when exposure time and gain where changed at the same time and the new exposure time was greater than the previous one. - PFNC pixel formats 'Coord3D_A12p', 'Coord3D_B12p' and 'Coord3D_C12p' have been (mvGenTLConsumer-lib) treated as 'ibpfMono12' instead of 'ibpfMono12Packed_V1' resulting in crashes and all sorts of other problems. - Some small changes in the interface header files in order to compile applications (all shipped packages) with Embarcadero C++ 7.40. - The black level slider in the 'Quick Setup' wizard can be used again. (wxPropView) (Bug introduced in version 2.31.0) - Reducing the 'RequestCount' property and then increasing it again without calling (mvIMPACT_acquire.h) 'FunctionInterface::getRequest' in between at least once did result in invalid (mv.impact.acquire.dll) request properties and could result in exception being thrown at runtime. - clGetSerialPortIdentifier returned portID without portIndex. (clsermv-lib) (Bug introduced in version 2.26.0) 15.03.2019 2.31.1 UPDATES: - Files will be signed using a COMODO certificate now since the StartCom certificate (all shipped MSI-based packages) used previously is no longer trusted by Windows. (Windows only) 07.03.2019 2.31.0 NEW FEATURES: - mvIMPACT Acquire is now shipped with CMake support! See the 'Building and linking' (all shipped packages) chapter of the documentation for details. - mvIMPACT Acquire example applications will now be shipped with C++11 features. CMake (all shipped packages) users using an appropriate compiler and users using the Visual Studio 2013 solution will automatically get the new versions of the example applications, all others will continue to see the legacy C++03 code. As a result a lot of new example applications are therefore available as part of the Linux installation as well now. - 'RemoveImage' function added to 'ImageDisplay' class. (mv.impact.acquire.display.dll) (mvIMPACT_acquire_display.h) - New calibration modes added to defective pixel filter: 'dpfmCalibrateHotPixel' and (all shipped packages) 'dpfmCalibrateHotAndColdPixel'. - New example added to all packages: 'GenICamCommonSettingsUsage'. (all shipped packages) - 'formatReinterpreterBayerMosaicParity' property added. This will allow to modify, (all shipped packages) add or remove the 'Bayer' attribute from an image buffer. - The 'Quick Setup' wizard will display images coming from a polarized sensor in 2by2 (all shipped packages) mode now and is able to display these image in color when they come from a color sensor. - mvDeviceConfigure learned to apply firmware updates by downloading the latest version (mvDeviceConfigure) from the MATRIX VISION GmbH website. - The flat field filter became AOI aware. It is now possible to calibrate only a part (all shipped packages) of the image and then only apply the flat field correction to that part of the image. Furthermore a calibration AOI can be selected which basically defines the AOI that is process. This results in reduced CPU load. Refer to the 'Image Processing' chapter in the documentation. - Color correction matrix for Sony IMX226 based products added. (all shipped packages) UPDATES: - Updated integrated U3VBootProgrammer to 0.33.1693.2. (mvGenTLProducer.cti) - Internal migration to Doxygen 1.8.15. CHANGED BEHAVIOUR: - Test image format 'vdtmColdPixelTestImageBayer' changed to (mvVirtualDevice-lib) 'vdtmHotAndColdPixelTestImageBayer'. - Examples for Visual Studio 2008 are no longer shipped as part of the installation. (all shipped MSI-based packages) Project files for the example applications for arbitrary Visual Studio can be generated with CMake now. - The Linux example application 'SingleSnap' is no longer shipped as part of the (all shipped packages for Unix/Linux systems) installation. It has long been replaced by 'SingleCapture'. - The Linux example application 'testserial' is no longer shipped as part of the (all shipped packages for Unix/Linux systems) installation. - On Linux the driver will try to use the systems native libusb and libudev if possible (mvGenTLProducer.cti) if an environment variable 'MVIMPACT_ACQUIRE_FAVOUR_SYSTEMS_LIBUSB' is specified now. If no matching compatible pair can be detected the libraries that are installed in the $MVIMPACT_ACQUIRE_DIR/Toolkits directory will be used(this was the previous behaviour). See 'known issues' section in the API manuals for details. - When saving a setting in GenICam interface layout without specifying that sequencer (mvGenTLConsumer-lib) or user set data shall be stored the old file format of GenApi 3.0.x and smaller will be used in order to allow old software to load these settings as well. - Internal buffer layout changed for U3V devices as certain USB3 host controllers (mvGenTLProducer.cti) due to bugs in their driver cannot deal with large (>16MB) transfer sizes. This e.g. fixes potential problems when using certain sequencer sets with high resolution devices. BUGS FIXED: - mvDeviceConfigure did not always allow to update the firmware of a device even if a (mvDeviceConfigure) suitable firmware was present in the selected archive(*.mvu). - Random crashes when a U3V device was unplugged and closed more or less (mvGenTLProducer.cti) simultaneously. (Linux only) - Fixed a couple of small issues in the installation scripts. (all shipped packages for Unix/Linux systems) (Linux only) - The property mv.impact.acquire.ImageProcessing.flatFieldFilterCorrectionMode had an (mv.impact.acquire.dll) invalid handle. - Added missing build dependency which could result in the build of (samples.NET.VC12.sln) 'GenICamCommonSettingsUsage' to fail when building the .NET examples. 14.12.2018 2.30.1 NEW FEATURES: - New test image format added: 'vdtmColdPixelTestImageBayer'. (mvVirtualDevice-lib) - New example added to all packages: 'ContinuousCaptureQt'. (all shipped packages) UPDATES: - Updated integrated U3VBootProgrammer and U3VBootLoader to 0.32.1667.2. (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - From this version onwards on Windows the mvGenTL_Acquire installation package will (mvGenTL_Acquire*.exe) be shipped as an executable package. The underlying technology will still be the same but the package is wrapper inside a bootstrapper now. Also when mvGigEConfigure is launched after the reboot no more user interaction will be required by default. BUGS FIXED: - In rare cases when 'userControlledImageProcessingEnable' was active the processing (all shipped packages) result of the 'Decoupler' node was 'iprSkipped' instead of 'iprApplied'. 10.12.2018 2.30.0 NEW FEATURES: - New example added to all packages: 'GenICamSequencerUsageWithPaths'. (all shipped packages) - Color correction matrix for Sony IMX183 based products added. (all shipped packages) UPDATES: - The driver no longer reads back gain and exposure time with the GenICam attribute (mvGenTLConsumer-lib) 'NoCache' when written. Instead a faster internal caching mechanism is used now. - Internal migration to IPP 2019.1. This effectively changes the runtime installations (all -x86_*.tgz packages) on Linux systems slightly. Instead of linking statically all IPP related code has been extracted into a dynamic library 'mvImageProcessing' which is now part of the installation packages. CHANGED BEHAVIOUR: - The multi-AOI wizard will correctly restore the current camera AOI when exited with (wxPropView) 'OK' now. BUGS FIXED: - mvIPConfigure did crash when mvGenTLProducer.cti was not located in the same folder. (mvIPConfigure) The crash no longer occurs and also the GENICAM_GENTL32_PATH or GENICAM_GENTL64_PATH variable is evaluated when looking for the library. - Raise condition that could result in an mvBlueFOX3 device to move into standby mode (mvGenTLConsumer-lib) while being in use by an application. - When the NDIS filter driver was used for GEV devices, 'acquisitionStartStopBehaviour' (mvGenTLProducer.cti) was set to 'assbUser' and the time that passed between the first 'imageRequestSingle' call and the first 'acquisitionStart' call was higher than the value of the property 'imageRequestTimeout_ms' for that buffer, the buffer was returned with a timeout. Now the timeout period will start not until 'acquisitionStart' is called. - Some mvBlueFOX devices (e.g. mvBlueFOX-121) did no longer deliver images. (mvBlueFOX-lib) (Bug introduced in version 2.29.0) - Cold pixel detection in the defective pixel filter did not work correctly with Bayer (all shipped packages) images. In case of error usually lots of cold pixels have been detected within the first line of the image. 07.11.2018 2.29.1 NEW FEATURES: - 2 by 2 mode added to 'Polarized Data Extraction' filter. (all shipped packages) - Color correction matrix for Sony IMX342 based products added. (all shipped packages) UPDATES: - Internal migration to CMake. All Linux based builds are generated using CMake now. (all shipped packages for Unix/Linux systems) - Internal migration to IPP 2019.0. (all shipped packages) (Windows only) - MSI packages will be built using WiX 3.11.1 now. (all shipped MSI based packages) CHANGED BEHAVIOUR: - From this version onwards ppc603e based platforms will no longer be supported. (all shipped packages for GenICam compliant devices) - From this version onwards the mvBlueCOUGAR-X/(D) and mvBlueFOX3 firmware will no longer be shipped as part of mvIMPACT Acquire. However the firmware can of course still be downloaded from the MATRIX VISION website separately. This is meant to speed up the release cycle times for both the firmware and the mvIMPACT Acquire SDK. BUGS FIXED: - Potential blue screen (BSOD) when working with the NDIS filter driver on Windows (mvGigECapture.sys, version 2.3.6.65) with Stream Channel Packet Size (SCPS) values smaller than 576 bytes. (mvGigECapture2.sys, version 3.1.7.65) (mvGenTLProducer.cti) - On some systems where multiple network adapters did have multiple IP addresses (mvGenTLProducer.cti) assigned sometimes the MTU of the network adapter was reported incorrectly. - Potential deadlock when calling updateDeviceList after another network adapter had (mvGenTLProducer.cti) appeared. - Potential crash after another network adapter had appeared. (mvDeviceConfigure) - Random crashes when at least on mvBlueFOX device was present in a Linux system. (mvBlueFOX-lib) - Incorrect 'Invalid command line parameter: 'postinstallmessage'' error message after (mvGigEConfigure) the installation of the GEV filter driver when selecting 'No' when asked whether to show NIC setup hints. (Bug introduced in version 2.11.3) - From this version onwards on Windows 7 the NDIS 5.x based GEV filter driver will be (mvGenTL_Acquire*.msi) used again as since the last changes the NDIS 6.x based version did cause problems. With version 2.29.0 after rebooting the system on Windows 7 the filter driver had to be disabled and then enabled again to get a working network connection. (Bug introduced in version 2.29.0) 02.10.2018 2.29.0 NEW FIRMWARE: - Firmware version 2.31.1567.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - IMX: Improved frame rate exactness in continuous mode for all IMX sensors except for IMX178. - mvBlueCOUGAR-XD107G/C: AOI and binning/decimation can now be used with the sequencer - Support for new cameras mvBlueCOUGAR-X102kG/C with IMX432 sensor. Changed behaviour: - mvBlueFOX3-2XXX: SmartFrameRecall can only be enabled if the image width is a multiple of 8 - USB 3.0 devices will now act as USB 3.1 Gen 1 devices. Bugs Fixed: - Sequencered Binning had problems when the width changed and the height was also scaled. - mvBlueCOUGAR-XD102fG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD107G/C, mvBlueCOUGAR-XD109bG/C, mvBlueCOUGAR-XD1012bG/C: fixed a bug, that led to corrupted images in SmartFrameRecall mode if the image width was not a multiple of 16 - mvBlueFOX3-2XXX: SmartFrameRecall in combination with USB 2.0 / High Speed did not work as expected. - mvBlueCOUGAR-XD107G/C: Changing PixelFormat or mvSensorDigitizationBitDepth when mvDualAdcMode is already on led to bad images. NEW FEATURES: - 'Polarized Data Extraction' filter added. (all shipped packages) - Color correction matrix for mvBlueCOUGAR-X102kC devices added. (all shipped packages) - Color correction matrix for mvBlueCOUGAR-X102mC devices added. (all shipped packages) UPDATES: - Support for newer kernel versions(up to 4.15) added to mvHYPERION modules. (low level mvHYPERION driver, Linux) - Improved reconnection behaviour for GEV devices connected to a network adapter whose (mvGenTLProducer.cti) IPv4 address has been changed after a device has been initialised. - Updated integrated U3VBootProgrammer to 0.31.1553.2 (mvGenTLProducer.cti) BUGS FIXED: - GEV devices sometimes did not change their 'State' property anymore when being (mvGenTLConsumer-lib) re-connected/disconnected when the link was lost again at a certain point during a previous re-connection event. - GenICam devices sometimes appeared under a wrong interface in 'Current Driver, (wxPropView) Interface and Device Information' dialog. - Fixed handle leaks. (clsermv-lib) (Windows only) - On Linux systems devices with NO firmware did only appear in the device manager when (mvBlueFOX-lib) the initial device manager instance was deleted and a new one was created. - Potential blue screen (BSOD) when changing network adapter parameters such as the (mvGigECapture.sys, version 2.3.6.63) link speed while at least one device was either streaming or when at least one image (mvGigECapture2.sys, version 3.1.6.63) has been captured on this adapter before since the system did start. - Capturing into user supplied memory did always result in an additional internal copy. (mvGenTLConsumer-lib) (mvVirtualDevice-lib) - Sometimes old white balance parameters have been applied to the image when using the (all shipped packages) host based processing when an application did change the gain values in parallel with calling 'imageRequestReset'. - When the 'Multi AOI' wizard was opened while an analysis tool was selected and this (wxPropView) analysis tool was operated in 'Full AOI' mode the AOIs in the 'Multi AOI' could not be dragged. (Bug introduced in version 2.25.0) - U3V devices could not be found on ARM64 boards running on Linux OSes that do not (all shipped packages for GenICam compliant devices, Linux/ARM64) ship with libcgmanager.so (e.g. Ubuntu 18.04) - Fixed a memory leak when calling the 'getCurrentCaptureBufferLayout' function more (mvGenTLConsumer-lib) than once for GenICam compliant devices. 05.07.2018 2.28.0 NEW FIRMWARE: - Firmware version 2.30.1463.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-2XXX: Enabled SmartFrameRecall - mvBlueFOX3-MXXXX: Enabled user i2c interface for module version - mvBlueFOX3-2064G/C: GlobalReset mode implemented. Changed behaviour: - Additional flash space of mvBlueCOUGAR-X/XD, Rev.5 and mvBlueFOX3-2 is now reserved, to ensure that the theoretic possible amount of defective pixel positions of our larger sensors can be stored. IMX420, IMX428, IMX253 and IMX304 sensor now support up to 1536 defective pixel. - Cameras with IMX sensors: First image after switching to TriggerMode 'Off' is done faster. - 'mvDeviceSensorName' became 'SensorName', 'mvDeviceSensorPixelWidth' became 'SensorPixelWidth' and 'mvDeviceSensorPixelHeight' became 'SensorPixelHeight' according to the SFNC 2.4. Also the features have been moved from the 'DeviceControl' category into the 'ImageFormatControl' category. 'mvDeviceSensorName' remains as an invisible property for backward compatibility. Bugs Fixed: - BCX(D)s with IMX sensors when using LUTs in combination with Mono8/Bayer8 delivered reduced quality image (missing codes). - Frame rate was halved when using ReverseY. Bug introduced in 2.29.1385.0. - mvBlueCOUGAR-XD107G/C: fixed bug, that caused images being displaced by a few lines when enabling vertical binning/decimation in comparison to the same image without vertical binning/decimation - mvBlueCOUGAR-X102eG/C/GE, mvBlueCOUGAR-X104eG/C, mvBlueFOX3-1013G/C/GE, mvBlueFOX3-1020G/C, mvBlueFOX3-1020aG/C: LineScan mode did not work with OffsetX != 0. FrameActive was not set correctly. - SmartFrameRecall didn't work since 2.24, currently the user has to ensure that thumbnail width is a multiple of 8. - mvBlueCOUGAR-X105G/C: Disturbed images could occur at high temperatures when using maximum device clock frequency (98Mhz). - mvBlueFOX3, mvBlueCOUGAR-X(D) all models: Code for mutual exclusion of triggers FrameStart, FrameBurstStart and FrameBurstActive was triggered even if one of these triggers was switched off. NEW FEATURES: - Multiple firmware versions are available for updating mvBlueFOX USB2 devices now. (mvBlueFOX-lib) - The 'GenICam' namespace now contains the full SFNC 2.4 feature set. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) UPDATES: - Migration to version 3.1.0 of the GenApi runtime. (all shipped packages for GenICam compliant devices) This will allow to store UserSets as well as SequencerControl programs within a setting file(see 'FunctionInterface::loadSetting' or 'DMR_LoadSetting' for details), improves execution speed and also fixes a couple of other issues. - Internal migration to IPP 2018.3. (all shipped packages) - Updated integrated U3VBootProgrammer to 0.30.1438.2 (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - The default format string for pointer properties (vtPtr) is "0x%p" now, while it (mvPropHandling-lib) used to be "0x%x" which does not work with 64-bit addresses. - Whenever an 'AcquisitionStart' command is executed the link speed for a GigE Vision (mvGenTLProducer.cti) is read back from the device in order to respond correctly on changing link speeds in terms of resend behaviour. - Removed all device/sensor specific values from (mvDriverBaseEnums.h) 'TColorTwistInputCorrectionMatrixMode'. Use 'DeviceSpecific' if you did use a value (mv.impact.acquire.dll) that is no longer available now. It will automatically select the best match for your device. - Maximum number of defective pixels that can be processed by the host based defective (all shipped packages) pixel filter will automatically adjust to the maximum number of pixel that can be processed by a device supporting the 'mvDefectivePixelCorrectionControl' category now. - Weird jumps in block IDs caused by malfunctioning devices are reported by the driver (mvGigECapture.sys, version 2.3.5.62) by increments of the LostFrame counter and log messages now. The stream of data (mvGigECapture2.sys, version 3.1.5.62) will continue after losing 1 or multiple frames. Previous driver versions did more or less stop streaming. BUGS FIXED: - The 'Callback' examples for C++/.NET did raise an 'invalid interface layout' (Callback) exception when used with a GenICam device. (Bug introduced in version 2.27.0) - Missing header files added to MSI based installation packages: wxIncludeEpilogue.h, (all shipped MSI-based packages) wxIncludePrologue.h, wxIncluder.h. (Bug introduced in version 2.26.0) - When operating the scaler with cubic interpolation and 10, 12 or 14 bit pixel formats (all shipped packages) the resulting buffer could contain values slightly larger than the maximum value for that pixel format. - When logging in to windows from the login screen, and wxPropView is already running (wxPropView) in the background in full screen mode, it did no longer respond. - Calling the 'ResetStatistics' function did not reset the 'LostImagesCount' when the (mvGenTLConsumer-lib) NDIS based driver was used. (mvGenTLProducer.cti) - Cameras operated in 'DeviceSpecific' interface layout no longer raise internal (mvGenTLConsumer-lib) exceptions when a camera did set 'mvExposureAutoUpperLimit' to 'not available'. - Potential crash when working with one of the adaptive edge sensing debayering (all shipped packages) algorithms. - Heap corruption when using the 'AdaptiveHomogeneityDirected' de-Bayer algorithm on (all shipped packages) an image with a height of 5. - On Windows the installers incorrectly did create a sub-folder 'MATRIX VISION' within (all shipped MSI-based packages) the target directory of the installation. (Bug introduced in version 2.24.0) - U3V devices specifying multiple IADs and the USB 3 Vision descriptor is not the first (mvGenTLProducer.cti) IAD can be operated now. - GenICam devices streaming multi-part data with multiple images using different pixel (mvGenTLConsumer-lib) formats for each part where not always correctly processed resulting e.g. in incorrect display output. - Moving Mono12 packed Bayer test images with an odd width have not been created (mvVirtualDevice-lib) correctly. - For test images with a an odd width AND height using the pixel format (mvVirtualDevice-lib) 'ibpfMono12Packed_V1' the last pixel of the last row of the image was incorrect. - Images with a height of 1 could result in a crash when the defective pixel filter was (all shipped packages) configured to perform calibration on the next image. 17.05.2018 2.27.0 NEW FIRMWARE: - Firmware version 2.29.1385.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-X225G/C: Exact frame rate in continuous mode. - IMX sensors with 12 and 9 MPixel now support RGB/YUV-Modes in BF3 and BCXD - mvBlueCOUGAR-XD107G/C: 60 fps instead of 44 fps at full AOI in burst mode. - mvBlueFOX3-2089G/C, mvBlueFOX3-2089aG/C, mvBlueCOUGAR-XD109bG/C: ReverseX and ReverseY implemented. Changed behaviour: - mvBlueCOUGAR-X225G/C: Improved AcquisitionStart behaviour. - mvBlueCOUGAR-X(D), mvBlueFOX3 (models with IMX sensors): Improved AcquisitionStart behaviour. - mvBlueFOX3, mvBlueCOUGAR-X(D) all models: Enabling one of the following triggers automatically disables the other ones: FrameStart, FrameBurstStart, FrameBurstActive. Bugs Fixed: - mvBlueCOUAGR-XD104G/C: Changing the exposure time could crash the camera firmware. - mvBlueFOX-2064G/C: Streaming could stop during auto exposure mode. - Firmware version 0x34(52) for mvBlueFOX devices added. (mvBlueFOX-lib) Changes: - Fixed "device descriptor read/64, error -110" message in the kernel ring buffer of Linux systems when plugging in the camera. NEW FEATURES: - On Linux systems the priority of certain threads has been adjusted. All Linux (all shipped packages for Unix/Linux systems) installer scripts take care of the necessary settings automatically. - 'AdaptiveHomogeneityDirected' Bayer conversion mode added for very high quality (all shipped packages except ARM platforms) debayering. UPDATES: - Improved execution speed of the 'imageRequestReset' function for USB3 Vision devices. (mvGenTLProducer.cti) - Internal migration to CMake. All Visual Studio projects for Visual Studio are (all shipped MSI-based packages) generated using CMake now. - Internal migration to Doxygen 1.8.14. - Added sensor specific CIECAM16 color correction matrices for all supported sensors. (all shipped MSI-based packages) CHANGED BEHAVIOUR: - Removed support for features that have been declared deprecated for centuries. (mvIMPACT_acquire_GenICam.h) An 'XYZRaw' feature should be replaced by the same feature without the 'Raw' in its name. If your application really still depends on the removed feature derive from the class the feature has been in and add the relevant code(copy it from an older release) there. - TransportLayerControl: gevSupportedOptionalCommandsUserDefinedName, gevSupportedOptionalCommandsSerialNumber, gevSupportedOptionalCommandsEVENTDATA, gevSupportedOptionalCommandsEVENT, gevSupportedOptionalCommandsPACKETRESEND, gevSupportedOptionalCommandsWRITEMEM, gevSupportedOptionalCommandsConcatenation, gevSupportedIPConfigurationLLA, gevSupportedIPConfigurationDHCP, gevSupportedIPConfigurationPersistentIP gevCurrentIPConfiguration, all gevManifest related properties. A device should offer gevSupportedOptionSelector and gevSupportedOption flavors of gevCurrentIPConfigurationXYZ and deviceManifestXYZ properties instead. - AcquisitionControl: acquisitionFrameRateRaw, acquisitionLineRateRaw, triggerDelayRaw, exposureTimeRaw. - AnalogControl: gainRaw, blackLevelRaw, whiteClipRaw. - CounterAndTimerControl: timerDurationRaw, timerDelayRaw, timerValueRaw. - Instantiating classes with an incompatible interface layout will raise an exception (all shipped packages) now. So classes from the GenICam namespace can only be used with devices operated in 'GenICam' interface layout and classes that state they can only be used with 'Device Specific' interface layout can only be used with devices operated in device specific interface layout now. BUGS FIXED: - On Linux USB3 Vision devices that have been opened in a another process are no longer (mvGenTLConsumer-lib) report 'Unreachable' in the 'State' property of the current process. - Potential crash when using the 'AdaptiveEdgeSensingPlus' Bayer conversion mode when (all shipped packages) the channel bit depth did change from one request to the next. - Moving Mono12 packed test images did use a different start pixel value for each color (mvVirtualDevice-lib) color bar. - Network interfaces with more than one IP address could lead to error messages (all shipped packages for Unix/Linux systems) appearing on the console. - Updating the DirectShow interface without uninstalling all previous versions of (DirectShow_acquire.ax) mvIMPACT Acquire did not install the latest version since version 2.17.0. (Bug introduced in version 2.17.0) - Unchecking the 'automatically check for updates' checkbox within the MSI installer (all shipped MSI based packages) did result in an installation error. (Bug introduced in version 2.26.0) - .NET 'Request' property hasProcessingBeenSkipped always returned false. (mv.impact.acquire.dll) 12.04.2018 2.26.0 NEW FIRMWARE: - Firmware version 2.28.1323.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Maximum exposure time increased to up to 20s for all ICX and IMX sensors except the IMX178. - New properties 'mvDeviceSensorRevisionMajor', 'mvDeviceSensorRevisionMinor', 'mvDeviceSensorPixelWidth', 'mvDeviceSensorPixelHeight' added. - Support for multiple paths in sequencer using old properties 'SequencerPathSelector', 'SequencerTriggerSource' and new property 'SequencerTriggerActivation'. 'SequencerTriggerSource' now also supports 'UserOutput0' as a trigger. - mvBlueCOUGAR-XD107: SONY IMX420 Dual Gain feature now available Dual Gain feature is only usable in combination with Multi-AOI mode. Changed behaviour: - Nodes with attribute 'ValidValueSet' are no longer used in the GenICam XML file. Therefore this and future versions can also be used with software that is linked with the GenApi 2.0 - 2.3(e.g. mvIMPACT Acquire 1.10.95 - 2.6.3, MIL 9, etc..). - 'mvFeatureMode' and 'ImageCompressionMode' will only be available if JPEG compression is available now. - mvBlueFOX3: Cameras do no longer go into standby while streaming. - CIECAM16 instead of WPPLS color correction matrices are now used in all cameras. - mvBlueCOUGAR-X(D), mvBlueFOX3 (models with IMX sensors): Improved AquisitionStart behaviour. Bugs Fixed: - UserOutputValues and LineSources were not set correctly when calling UserSetLoad(). Bug introduced in 2.27.1231.0. - mvBlueCOUGAR-X(D) (all models): fixed bug that could crash the camera firmware when enabling/disabling the serial interface - mvBlueCOUGAR-X(D), mvBlueFOX3 (models with IMX sensors): In random cases acquisition could stop when changing exposure time. - mvBlueCOUGAR-XD107G/C: Sequencer could stop when changing image size. - Sequencer frame rate no longer depends on exposure time of last configured sequencer set. - Writing to the binning/decimation registers sometimes did take quite some time for some IMX sensor based cameras. Bug introduced in 2.27.1231.0. - The 'device mode' register did contain an invalid value for 'current link configuration' in static LAG mode resulting in invalid data in the 'GevCurrentPhysicalLinkConfiguration' property when a GEV device then. NEW FEATURES: - 'mvGainMode' and 'mvGainHorizontalZoneDivider' property added to the 'AnalogControl' (mvIMPACT_acquire_GenICam.h) class of the GenICam namespace. (mv.impact.acquire.dll) - Added a checkbox to allow to configure whether wxPropView shall automatically check (all shipped MSI based packages) for updates or not. - All Linux installer scripts now support a minimal installation option, which can be (all shipped packages for Unix/Linux systems) achieved with the '-m' or '--minimal' command line argument. - The sequencer wizard can now cope with multiple sequencer paths per sequencer set. (wxPropView) - 'AdaptiveEdgeSensingPlus' Bayer conversion mode added for high quality debayering. (all shipped packages) UPDATES: - Checking for updates now is 'proxy setting aware'. (wxPropView) - Migration to wxWidgets 3.0.4 (Windows only). All wxWidgets based applications (all shipped MSI based packages) are built using wxWidgets 3.0.4 now. - Internal migration to IPP 2018.2. (all shipped packages) CHANGED BEHAVIOUR: - From this version onwards the initial mvBlueFOX kernel driver for 32-bit Windows (mvBlueFOX.sys) that was removed in version 1.10.66 can no longer be updated to the mvBlueFOX2.sys driver that was added in version 1.6.10 (2006). When you still have 32-bit systems using this old driver use mvDeviceConfigure to update the driver BEFORE migrating to mvIMPACT Acquire 2.26.0 or newer. - From this version onwards Windows XP is no longer supported by mvIMPACT Acquire. (all shipped MSI based packages) Official support stopped a while ago, since this release GUI applications as well as some of the underlying libraries will no longer load on Windows versions older than Windows Vista. - The ColorTwist filters 'DeviceSpecific' input matrix now uses CIECAM16 color (all shipped packages) correction matrices, in contrast to WPPLS color correction matrices used until now. Furthermore, CIECAM16 color correction matrices can now also be manually selected for all products. - The ColorTwist filter's output matrix default preset has been changed from (all shipped packages) XYZToAdobeRGB_D50 to XYZTosRGB_D50 since most use-cases use the sRGB colorspace. - Writing a GenICam feature no longer blocks the acquisition engine. When writing to a (mvGenTLConsumer-lib) device feature took a long time (e.g. did generate PENDING_ACKs) during that time no new requests could be queued which could result in the acquisition engine to starve. - The default visibility of the infoFrameID property of a request has been changed from (all shipped packages) 'invisible' to 'visible'. - Low level errors reported by a GenTL producer when reading and writing properties (mvPropHandling-lib) will be reported to the application now. BUGS FIXED: - Updating mvBlueCOUGAR-X(D) devices running with firmware version 1.1.3.0 or smaller (mvDeviceConfigure) did not work properly and resulted in various messages with information that did not actually apply. - Some bugs and warnings fixed for mvIMPACT_Python wrapper scripts. (all shipped packages) - Potential crash when no GenICam device has been detected, the 'warn on potential (wxPropView) firewall issues' option was active, and the user selected 'No' in the message dialog. - On Linux systems the various settings of the options dialog could not be changed. (wxPropView) (Bug introduced in version 2.25.0) - Crash when shutting down a Windows 7 system while wxPropView was still open. (wxPropView) - When moving wxPropView around or minimizing and then maximizing the application again (wxPropView) the display overlay messages haven't been repainted. (Windows only) - The example applications 'CaptureToUserMemory_C' and 'ContinuousCaptureOnlyProcessLatest' have been missing some files after the (all shipped MSI based packages) installation. (Windows only) - Potential crash in defective pixel filter when feeding it with images with either the (all shipped packages) width or the height being smaller than 20. (Bug introduced in version 2.22.1) 09.02.2018 2.25.0 NEW FIRMWARE: - Firmware version 2.27.1231.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR: FFC Calibration is now possible with configured AOI. In this case the average value is calculated for the AOI only while the FFC values are calculated for the full sensor area. - New camera mvBlueCOUGAR-XD107C with sensor IMX420. Changed behaviour: - mvBlueFOX3-2064G/C: Minimum AOI height is 320 now, minimum AOI width is 376 now. - Deprecated some features with respect to the latest SFNC 2.3: 'mvGevSCBWControl' (use 'DeviceLinkThroughputLimitMode' instead), 'mvGevSCBW'(use 'DeviceLinkThroughputLimit' instead) - Removed support for features that have been declared deprecated for centuries. All the information can be accessed using 'GevSupportedOptionSelector' and 'GevSupportedOption': - 'GevSupportedOptionalCommandsUserDefinedName' - 'GevSupportedOptionalCommandsSerialNumber' - 'GevSupportedOptionalCommandsEVENTDATA' - 'GevSupportedOptionalCommandsEVENT' - 'GevSupportedOptionalCommandsPACKETRESEND' - 'GevSupportedOptionalCommandsWRITEMEM' - 'GevSupportedOptionalCommandsConcatenation' - 'GevSupportedIPConfigurationLLA' - 'GevSupportedIPConfigurationDHCP' - 'GevSupportedIPConfigurationPersistentIP' - 'GevSupportedOptionalCommandsUserDefinedName' - mvBlueCOUGAR-X125aG/C: Minimum width is 18 instead of 16 now. Bugs Fixed: - mvBlueCOUGAR-X(D): Wrong frame rate after startup. Bug introduced in 2.26.1138.0. - mvBlueFOX3-2064G/C: Fixed bug that could crash the camera firmware. - mvBlueSIRIUS: Wrong pixels could occur at 56Mhz device clock. - mvBlueCOUGAR-X102e/102eGE/104e(since 2.15), mvBlueCOUGAR-X100/102b/105/1010(since 2.23), mvBlueCOUGAR-XD12xG/C: Actual TimerDelay and TriggerDelay were too short by ~3.5%. NEW FEATURES: - Users now can manually check or enable automatic weekly checking for updates. This (wxPropView) can be done with options found in the 'Help' menu. - 'Set Parameter Delimiter' option added to the context menu for methods in the (wxPropView) property grid. - Outdated fall-back boot programmers on mvBlueFOX3 devices can be updated using (mvDeviceConfigure) mvDeviceConfigure now. A message box directly before starting a firmware update will inform the user about this. - Devices can now be selected based on a string Device ID (e.g. 'UserDefinedName' for (mvIMPACT_acquire.h) GenICam devices) with the functions 'DMR_GetDeviceWithStringID()', (mvDeviceManager-lib) 'mvIMPACT::acquire::DeviceManager::getDeviceByProductAndID()' or (mv.impact.acquire.dll) 'mv.impact.acquire.DeviceManager.getDeviceByProductAndID()'. - Devices can be operated in GenICam interface layout as well now. (mvIMPACTAcquire_Cognex_Adapter-lib) - New color correction matrix added: 'cticmmBlueCOUGAR_XDx07C_CIECAM16'. It will be (all shipped packages) used by mvBlueCOUGAR-XD107C devices. UPDATES: - Added missing features to the 'mvFFCControl' class: 'mvFFCImageLoad', (mvIMPACT_acquire_GenICam.h) 'mvFFCImageSave' and 'mvFFCAutoLoadMode'. (mv.impact.acquire.dll) - On Linux systems just like on windows systems, all GEV cameras with bad network (mvIPConfigure) configurations will now appear on the device list. CHANGED BEHAVIOUR: - The following classes have been removed from the GenICam namespace of the public (all shipped packages) interface: mvSPIControl, mvDACParams, mvOMAPPreviewConfig, mvXLampControl and mvACCControl. All these features where only supported by discontinued products. - The following features have been removed from the GenICam namespace of the public (all shipped packages) interface - DeviceControl: mvDeviceSensor. - ImageFormatControl: mvDebayerAlgorithm, mvOffsetYSensorB, mvSensorLineOffsetSelector, mvSensorLineOffset, mvSensorLinePeriod. - AnalogControl: mvVCAL, mvVBLACK, mvVOFFSET. All these features where only supported by discontinued products. - From this version onwards mvIMPACT Acquire will no longer serve as a valid license (all shipped packages) provider for the discontinued mvIMPACT SDK. As a consequence mvIMPACT SDK licenses bound to a specific MATRIX VISION device can only be used with mvIMPACT Acquire packages < 2.25.0. BUGS FIXED: - Writing from an application to the 'DefectivePixelOffsetX' or 'DefectivePixelOffsetY' (all shipped packages) did not always become effective. - When updating an mvIMPACT Acquire package other than mvGenTL_Acquire to 2.24.0 or (wxPropView) newer while having an installed version of mvGenTL_acquire < 2.24.0 on the system as (mvDeviceConfigure) well, mvDeviceConfigure did crash upon starting and wxPropView when opening the driver information dialog. (Bug introduced in version 2.24.0) - Various minor bug fixes and improvements of the Linux installers of mvGenTL_Acquire (mvGenTL_Acquire-*.tgz) with regard to the plugdev group management and Linux capabilities for arping. (mvGenTL_Acquire-ARM*.tgz) - Warning regarding ignored interfaces could pop up even if there weren't any. (mvIPConfigure) - Changing the property 'ImageFormatControl/PixelFormat' did not automatically (mvGenTLConsumer-lib) update the visibility of the color processing properties in the 'ImageProcessing' list in GenICam interface layout. - Fixed some minor issues in the Multi-AOI wizard. When entering the wizard with Multi- (wxPropView) AOI already active, the behaviour is correct now, incorrect labels when deleting an AOI fixed, some hints added. - Clicking on the bitmaps left and right of the optimization slider of the Quick Setup (wxPropView) Wizard now also selects the min/max value for the slider. - On Linux systems saving camera settings natively works again. (mvGenTLConsumer-lib) (Bug introduced in version 2.19.0) 06.12.2017 2.24.0 NEW FIRMWARE: - Firmware version 2.26.1138.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Improved Interface of Flat Field Correction Feature: Loading/Storing the FFC data in non-volatile can be done now manually too. - The Flat Field Correction in mvBlueCOUGAR-X CMOS color cameras (all but CMV and V034) is done now color aware and won't interfere with the normal white balance settings anymore. - The new feature 'mvTimestampPPSSync' allows synchronizing the Timestamp by a 'Pulse Per Second' signal. It is available in all mvBlueCOUGAR-X(D) and mvBlueFOX3 devices. - mvBlueCOUGAR-XD107G: Upper and lower part of an image can be acquired with different exposure times. Changed behaviour: - mvBlueFOX3-2064G/C: Minimum width is 640 instead of 512 now. - Deprecated some features with respect to the latest SFNC 2.3: 'GevVersionMajor' (use 'DeviceTLVersionMajor' instead), 'GevVersionMinor'(use 'DeviceTLVersionMinor' instead), 'GevDeviceModeIsBigEndian' (use 'DeviceRegistersEndianness' instead), 'GevDeviceClass' (use 'DeviceType' instead), 'GevDeviceModeCharacterSet' (use 'DeviceCharacterSet' instead), 'GevNumberOfInterfaces' (use 'DeviceLinkSelector' instead), 'GevMessageChannelCount' (use 'DeviceEventChannelCount' instead), 'GevStreamChannelCount' (use 'DeviceStreamChannelCount' instead), 'GevHeartbeatTimeout' (use 'DeviceLinkHeartbeatTimeout' instead), 'GevTimestampControlLatch' (use 'TimestampLatch' instead), 'GevTimestampControlReset' (use 'TimestampReset' instead), 'GevTimestampControlLatchReset' (use 'TimestampLatch' and 'TimestampReset' instead), 'GevTimestampValue' (use 'TimestampLatchValue' instead), 'GevSCPDirection' (use 'DeviceStreamChannelType' instead), 'GevSCPSBigEndian' (use 'DeviceStreamChannelEndianness' instead), 'GevLinkSpeed' (use 'DeviceLinkSpeed' instead), 'mvDeviceStatusLEDEnable' (use 'DeviceIndicatorMode' instead) - mvBlueFOX3: Sequencer can be used up to 500 fps. Bugs Fixed: - GevMCSP was always reported as 0. - mvBlueCOUGAR-X/XD: Loading of default user set could lead to wrong bandwidth (mvGevSCBW) settings. - AOI used for AEC, AGC, AWB algorithms was not updated when the actual capture AOI was changed. NEW FEATURES: - Added a 3rd part (Mono8 ramp) to the multi-part mode of the virtual device (mvVirtualDevice-lib) for testing purposes. - Interfaces can now be ignored as a group, based on their transport layer technology (mvGenTLProducer.cti) type by using the properties 'mvInterfaceTechnologyToIgnoreEnable' and 'mvInterfaceTechnologyToIgnoreSelector'. - mvDeviceConfigure can detect ignored GenICam interfaces, and recommend a fix. (mvDeviceConfigure) - mvIPConfigure can detect ignored GenICam interfaces, and recommend a fix. (mvIPConfigure) UPDATES: - Some U3V devices set their 'event_size' in multi-event mode to invalid values (e.g. (mvGenTLProducer.cti) 0). This could result in an internal infinite loop resulting in no more events being delivered to the application. - For GEV devices supporting the message channel source port the driver will now send (mvGenTLProducer.cti) dummy packets to the devices message channel in order to open up the message channel if blocked by a firewall. - Optimized packet size auto negotiation algorithm for GEV devices. (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - The 'workerPriority' property of the SystemSettings class/category has been declared (all shipped packages) deprecated. - Property 'mvIgnoreInterfaceWhenEnumerating', is no longer a bool but a tri-state (mvGenTLProducer.cti) enum, and it has been renamed to 'mvDeviceUpdateListBehaviour'. This change was necessary for seamless operation with the new 'mvInterfaceTechnologyToIgnoreEnable' and 'mvInterfaceTechnologyToIgnoreSelector' features. - When the 'Bayer' filter did return an incorrect result buffer if a device claimed (all shipped packages) to send one format but then did actually deliver a different one. - The check for the presence of KB3033929 which is needed on Windows 7 and (all shipped MSI based packages) earlier for the processing of SHA256 signatures introduced in version 2.16.0 is now also done during silent installations. - The Quick Setup Wizard no longer automatically changes any device settings if (wxPropView) manually started from the button or the menu. Furthermore, feature selectors as well as scrollbar positions and zoom factor of the displayed image will be reverted to their original setting when closing the wizard. - The 'Driver Information dialog' now resides in the 'Action' category of the menu, and (wxPropView) is called 'Interface Configuration and Driver Information' dialog. If there are GenICam interfaces on the system the user can ignore or un-ignore them graphically in this dialog. BUGS FIXED: - Several bugs fixed in the scripts that build the mvIMPACT for Python wrapper. (all shipped packages) - Potential crash when the application was running in 'full tree' mode, a property was (wxPropView) selected within the grid and the application was closed then. - Error message when pressing 'OK' after dragging an area to the left or lower end of (wxPropView) the image after reducing the width/height of that area in the 'Multi AOI' wizard. - Firmware update is possible again for mvBlueCOUGAR-S devices. (mvGenTLConsumer-lib) (Bug introduced in version 2.18.0) - Potential BSOD when the operating system did run extremely low on resources. (mvGigECapture.sys, version 2.3.4.61) (mvGigECapture2.sys, version 3.1.4.61) - Sometimes when opening/closing a GEV device while calling 'updateDeviceList' from a (mvGenTLProducer.cti) separate thread opening the device the next time could fail. - For some RGB packed to ibpfBGR101010Packed_V2 conversions the resulting image did (all shipped packages) incorrectly exchange the red and blue component. - For internal pixel format conversions of buffers using a line pitch with padding (all shipped packages) bytes when the conversion was done on the fly (within the existing buffer) the resulting image could have an incorrect pitch after the conversion. - White balance calibration for multi-byte data did take the current gain into account (all shipped packages) resulting in the white balance gains to change every time 'CalibrateNextFrame' was selected and applied to the next image. - The Bayer filter did not process data if the final output format was set to (all shipped packages) 'ibpfBGR101010Packed_V2'.' - When reading a value as string from a property storing n values, reading at index n (mvPropHandling-lib) not return an error. The returned data however was arbitrary memory content. - When leaving the 'Color Correction' dialog without pressing 'OK' the previous (wxPropView) settings will be restored now. 18.10.2017 2.23.0 NEW FIRMWARE: - Firmware version 2.25.1029.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New camera mvBlueCOUGAR-XD107G with sensor IMX420. Changed behaviour: - Improved configuration speed of sequencer. Bugs Fixed: - mvBlueFOX3-1020G/C, mvBlueFOX3-1020aG/C, mvBlueCOUGAR-X104eG/C: One corrupt column could appear. - mvBlueCOUGAR-X(D)*: Block ID in legacy mode (16 bit) did not wrap correctly in some special cases. - mvBlueFOX3-2124G: In multi-AOI mode these cameras operated at a reduced frame rate (half) and with slightly incorrect AOIs. - mvBlueCOUGAR-X(D) and mvBlueFOX3: When loading different trigger configurations by use of "Load Active Device Settings -> From a File" it was not guaranteed that the trigger settings were loaded correctly. UPDATES: - Opening multiple devices in parallel is much faster now. (all shipped packages) NEW FEATURES: - Added public interface for accessing the Opto Engineering Stepper and the Invenios (mvIMPACT_acquire.h) Liquid Lens. (mv.impact.acquire.dll) - Added new functions to load/store images in TIFF, JPEG, PNG and BMP format. TIFF and (mv.impact.acquire.dll) PNG supports multi-byte thus lossless storage of formats like e.g. Mono12. For (mvDeviceManager-lib) formats not supporting multi-byte data the data will be converted into an appropriate (wxPropView) single-byte format during the file I/O operation. The new functions for the 'C' interface are 'DMR_LoadImageBuffer', 'DMR_SaveImageBuffer' and 'DMR_ImageRequestSave'. For the C++ interface 'mvIMPACT::acquire::Request::save', 'mvIMPACT::acquire::ImageBufferDesc::save' and a new constructor for 'mvIMPACT::acquire::ImageBufferDesc' taking a file name have been added. For the .NET interface so far only 'mv.impact.acquire.Request.save' is available. - 16-bit mono and RGB images in TIFF or PNG format can be imported from a directory (mvVirtualDevice-lib) now. - New constructors added to mv.impact.acquire.GenICam.SystemModule (mv.impact.acquire.dll) and mv.impact.acquire.GenICam.InterfaceModule. They can be used without a valid pointer to a device class instance. - Interfaces can now selectively be ignored when updating the device list, by using (mvGenTLProducer.cti) the feature 'mvIgnoreInterfaceWhenEnumerating' in the GenICam System module. CHANGED BEHAVIOUR: - Linux installers of mvGenTLAcquire no longer install U3V-related libraries if only (mvGenTL_Acquire-*.tgz ) GEV support has been explicitly requested. (mvGenTL_Acquire-ARM*.tgz ) - The 'Pending Timeout' register of a GEV device is now used for determining the (mvGenTLProducer.cti) default value of 'LinkCommandTimeout' of the 'DeviceModule' instance. BUGS FIXED: - Potential blue screen (BSOD) on 64-bit Windows systems running 32-bit applications. (mvGenTLProducer.cti) 20.09.2017 2.22.1 NEW FIRMWARE: - Firmware version 2.24.975.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New cameras: mvBlueFOX3-2064G/C - Serial Interface: Opto Engineering stepper support added for MTDV3CH-00A1 - Serial Interface: Invenios Liquid Lens support added for Caspian C-39N0-160 - mvBlueFOX3-2064G/C: FrameStart trigger implemented. - mvBlueFOX3-2064G/C: new mvRollingShutterFlash mode provides an exposure signal to flash all lines simultaneously, avoiding motion effects.(only for exposure > 300usec). - Added support for the 'DeviceFeaturePersistenceStart' and 'DeviceFeaturePersistenceEnd' features. Bugs Fixed: - mvBlueFOX3-2004G/C, mvBlueFOX3-2016G/C, mvBlueFOX3-2024(a)G/C, mvBlueFOX3-2032(a)G/C, mvBlueFOX3-2051(a)G/C,mvBlueFOX3-2064G/C, mvBlueFOX3-2089(a)G/C, mvBlueFOX3-2124(a)G/C, mvBlueCOUGAR-X100fG/C,mvBlueCOUGAR-X102fG/C, mvBlueCOUGAR-X(D)104d/f/h/iG/C, mvBlueCOUGAR-X(D)105a/bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-X1012bG/C, respect exposure time step width in auto exposure mode to prevent flickering that occurred when using small exposure times. mvBlueCOUGAR-X(D) cameras had boot problems when real UART traffic or I/O crosstalk was present at startup (Bug introduced in version 2.22.883.0) NEW FEATURES: - New sample added to all packages: 'ContinuousCaptureMultiPart'. (all shipped packages) - Most samples typically installed on Linux x86/x86_64 systems are now available for (mvBlueFOX-ARM*.tgz) ARM systems too. (mvGenTL_Acquire-ARM*.tgz ) CHANGED BEHAVIOUR: - Defective Pixels algorithms now do not check against a whole image average, but (all shipped packages) rather against a local average, eliminating false positives in case of e.g. uneven lighting of the sensor. - The deprecated libraries 'mvBlueCOUGAR-lib' and 'mvTLIClientGigE.cti' will no longer (all shipped packages for GEV/U3V devices) be loaded. Their usage had been declared deprecated in version 2.3.0. Since version 2.7.2 these libraries are no longer shipped anyway. BUGS FIXED: - Pressing the greyscale preset of the 'Quick Setup' wizard when streaming from a color (wxPropView) camera could lead to unhandled exceptions. (Bug introduced in version 2.22.0) - 'Defective pixel filter' did not take AOI/Offset changes into account. (all shipped packages) - mv.impact.acquire.GenICam.DevFileStream: After calling the Read/Write method with a (mv.impact.acquire.dll) 'count' value that was not the full file size the 'Position' property was not always updated correctly. 10.08.2017 2.22.0 NEW FIRMWARE: - Firmware version 2.23.928.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-X(D): Migration to GEV 2.1. This includes support for extended block ID. - mvBlueCOUGAR-X102bG/C, mvBlueCOUGAR-X102dG/C, mvBlueFOX3-1012bG/C, mvBlueFOX3-1012dG/C: Frame rate increased up to 45fps at full AOI if using new DeviceClockFrequency 74,25MHz. - mvBlueCOUGAR-X100fG/C, mvBlueCOUGAR-X102fG/C, mvBlueCOUGAR-X104f/iG/C, mvBlueCOUGAR-X105bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-X1012bG/C: Flat field correction implemented. Changed behaviour: - mvBlueCOUGAR-X102bG/C, mvBlueCOUGAR-X102dG/C: Maximum BinningHorizontal is 2 now (was 8 before), maximum DecimationHorizontal is 4 now (was 16 before), maximum DecimationVertical is 4 now (was 2 before). Bugs Fixed: - mvBlueCOUGAR-X102bG/C, mvBlueCOUGAR-X102dG/C, mvBlueFOX3-1012bG/C, mvBlueFOX3-1012dG/C: Trigger problems with 66MHz DeviceClockFrequency solved. - mvBlueFOX3-2089aG/C, mvBlueFOX3-2124aG/C: Cameras sometimes crashed for long exposure times. - mvBlueFOX3-2124G: Displacement of 0.5 vertical pixels of binned image corrected. NEW FEATURES: - Initial version of a full Python wrapper for mvIMPACT Acquire added. Before the (all shipped packages) samples or any self written code can be executed the wrapper code needs to be compiled for the installed version of Python. See product specific manuals for additional details. - New color correction matrix added: 'cticmmBlueFOX3_x064C_WPPLS'. This matrix will (all shipped packages) be used by 'mvBlueFOX3_x064C' devices. - Added new command line option 'allWithAtLeastOneDevice' to enable the filter driver (mvGigEConfigure) on all network interfaces that have at least one GigE Vision device connected to it. See tool output window for details. BUGS FIXED: - Certain YUV422Packed formats now display correctly. (mvDisplay-lib) (Bug introduced in version 2.20.0) - In the (deprecated) DeviceSpecific interfaceLayout, in case of multiple gains, the (mvBlueCOUGAR-lib) 'Gain_dB' property now refers to the 'AnalogAll' Gain of the device, and not arbitrarily to the first gain in the list. - Calling 'updateDeviceList' after a previous call to (mvGenTLProducer.cti) 'InterfaceModule::GevDeviceForceIPCommand' did never return. (Bug introduced in version 2.20.0) - When a GEV device did stream in the deprecated extended chunk format with 64-bit (mvGenTLProducer.cti) block ID enabled the reported timestamp was always 0. - When a GEV device did stream in 'image extended chunk' format with 64-bit block ID (mvGenTLProducer.cti) disabled the chunk data could not be decoded resulting in 'rrInconsistentBufferContent' errors. - The GEV format 'JPEG_ExtendedChunk' (0x4006) can be decoded correctly now. (mvGenTLProducer.cti) - Resend commands for GEV streams using the 64-bit block ID mode did use an incorrect (mvGenTLProducer.cti) layout. As a consequence resend did not work then. (mvGigECapture.sys, version 2.3.3.60) (mvGigECapture2.sys, version 3.1.3.60) - Requesting images using the 'ircmTrial' did return incorrect information (e.g. a (mvGenTLConsumer-lib) width of 0). - When a GEV device was opened with RO access while another process had established (mvGenTLProducer.cti) control access already the properties in the RO process appeared to be writeable. (Bug introduced in version 2.15.0) - Fixed ArgumentNullException that could occur if LibraryPath.init() was called and (mv.impact.acquire.dll) an assembly without a public key was resolved afterwards. - Sometimes properties belonging to the 'BufferPart' class did change their handles (mvIMPACT_acquire.h) but the API still referred to old ones resulting in 'INVALID_LIST_ID' exceptions. (mv.impact.acquire.dll) - A Bayer image in a multi-part buffer was not automatically converted into an RGB (mvGenTLConsumer-lib) image(it did loose its Bayer attribute before being delivered to an application). - The new enum value 'dc3DCamera' did use an incorrect numerical value. This could (mvDriverBaseEnums.h) cause problems with applications compiled with older versions of the header file. (mv.impact.acquire.dll) 3D cameras might be reported as frame grabbers and vice versa. (Bug introduced in version 2.21.1) - Firmware update for mvBlueSIRIUS devices is possible again. (mvDeviceConfigure) (Bug introduced in version 2.21.1) 10.07.2017 2.21.1 NEW FIRMWARE: - Firmware version 2.22.883.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3, mvBlueCOUGAR-X(D): mvSerialInterface support added. - mvBlueFOX3-2024aG/C, mvBlueCOUGAR-X104fG/C: Higher frame rates with reduced image width. - mvBlueFOX3-2, FrameAverage now available for all cameras with SONY Pregius sensors Changed behaviour: - In ExposureMode TriggerWidth trigger sources only triggers defined by a pulse are allowed. Triggers generated by logical events (e.g. CounterEnd) don't make sense and so they can no longer be configured. Bugs Fixed: - mvBlueCOUGAR-X1010G/C: Maximum for AcquisitionFrameRate was reduced to 135Hz. (Bug introduced in version 2.21.833.0) - mvBlueCOUGAR-X225G/C: Corrupt images. (Bug introduced in version 2.20.774.0) - mvBlueFOX3 and mvBlueCOUGAR-X(D) with IMX sensors: ExposureMode TriggerWidth did not work in some cases. (Bug introduced in version 2.10.326.0) - mvBlueCOUGAR-XD129G/C: Corrupt images could occur when using highest DeviceClockFrequency. - mvBlueFOX3, mvBlueCOUGAR-X(D): Cameras that were updated from a software prior to 2.21.833.0 had shown the Firmware Hash Code only after calling mvCalculateHashCode(). NEW FEATURES: - New color correction matrices added: 'cticmmBlueCOUGAR_Xx00fC_WPPLS', (all shipped packages) 'cticmmBlueCOUGAR_Xx02fC_WPPLS', 'cticmmBlueFOX3_x004C_WPPLS' and 'cticmmBlueFOX3_x016C_WPPLS'. These will be used by 'mvBlueCOUGAR-X100fC', 'mvBlueCOUGAR-X102fC', 'mvBlueFOX3_x004C' and 'mvBlueFOX3_x016C'devices respectively. UPDATES: - Updated target color space matrices for ColorTwist filter. (all shipped packages) - Previous versions of the GigE Vision filter driver did generate a lot of DPCs even (mvGigECapture.sys, version 2.3.2.59) when no device was actually streaming data. Now DPCs will only be generated for (mvGigECapture2.sys, version 3.1.2.59) adapters that currently receive data from at least one GEV device. CHANGED BEHAVIOUR: - The default value of the 'GEV_NDIS_DRIVER_INSTALL' parameter for the installer is now (mvGenTL_Acquire*.msi) 'yes' in order to restore the previous behaviour of custom installations. - An EULA has been added to mvIMPACT Acquire that needs to be accepted before you can (all shipped packages) install the software. BUGS FIXED: - Certain combinations of AOI and pitch could result in crashes in the mvDisplay (mvDisplay-lib) library on 32-bit Windows systems. - Potential freeze when using mvBlueFOX devices with no on-board memory in parallel, (DirectShow_acquire.ax) in combinations that exceed the total bandwidth limit of the USB channel. - Storing properties containing binary data in a setting did not always work. (mvPropHandling-lib) This did e.g. result in FFC calibration data not being written to a XML-file. (Bug introduced in version 2.15.1) - When capturing data with 'ImageProcessingMode' set to 'ipmProcessLatestOnly' while (all shipped packages) the flat field filter or the dark current filter are in calibration mode dropped frames did result in incomplete calibration results. 01.06.2017 2.21.0 NEW FIRMWARE: - Firmware version 2.21.833.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - 'BalanceWhiteAuto' and 'BlackLevelAuto' automatically switch back from e.g. 'Once' to 'Off' once the calibration has been performed. - mvBlueFOX3: Added command to reset the PHY and LINK error counters. - mvBlueFOX3, mvBlueCOUGAR-X(D): Added possibility to calculate SHA1 hash of firmware file currently saved in camera. Changed behaviour: - mvBlueCOUGAR-X105G/C: Minimum width changed from 16 to 80. - mvBlueCOUGAR-X, mvBlueCOUGAR-XD, mvBlueFOX3: cameras start with mvAcquisitionFrameRateLimitMode set to 'mvDeviceLinkThroughput', AcquisitionFrameRateEnable set to 'true' and AcquisitionFrameRate set to the maximum frame rate available with the sensor Bugs Fixed: - mvBlueCOUGAR-X104G/C, mvBlueCOUGAR-X104bG/C/UV, mvBlueCOUGAR-XD104G/C, mvBlueCOUGAR-XD104bG/C, mvBlueCOUGAR-XD204G/C, mvBlueCOUGAR-XD204bG/C: Camera could crash during streaming. (Bug introduced in version 2.15.578.0) - ChunkGain was not correct when using automatic gain control. - mvBlueFOX3: Show correct DeviceUserID and DeviceUserData after returning from standby mode. NEW FEATURES: - All libraries now use thread local storage to store the last error information. (all shipped packages) As a result much better exception messages can be generated now. UPDATES: - Improved support for 3rd party GenICam devices when using the sequencer wizard. (wxPropView) - Improved support for 3rd party devices that did not change the 'chunk_layout_id' when (mvGenTLConsumer-lib) the PayloadSize did change. - Improved support for 3rd party devices that did support the chunk mode without (mvGenTLConsumer-lib) specifying at least one chunk feature and a chunk port in their XML file. - Internal migration to libusb 1.0.21. (mvGenTL_Acquire-*.tgz ) BUGS FIXED: - Potential crash when calling 'GCUnregisterEvent' for a error event registered for a (mvGenTLProducer.cti) device that has already been closed. (Linux only). - For GEV streams where the trailer did arrive before the first payload packet these (mvGenTLProducer.cti) buffers have sometimes been tagged as incomplete even though all data has been captured when the socket driver was used. (Bug introduced in version 2.20.0) - Loading BMP files without the FreeImage library did fail when the bitmap file did (mvVirtualDevice-lib) specify a negative height(which actually means the image is NOT stored upside down). - Fixed a couple of bugs that did surface when using a 3rd party GenTL producer (mvGenTLConsumer-lib) - Potential crash when closing a DirectShow application in which the properties dialog (DirectShow_acquire.ax) has been opened at least once. - Lists below a selector can not be displayed correctly. This is a wxWidgets (wxPropView) limitation. Such lists are now treated like if 'Settings -> Property Grid -> Use Selector Grouping' is switched off. 01.05.2017 2.20.0 NEW FIRMWARE: - Firmware version 2.20.774.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3 (except for -2024(a)G/C) and mvBlueCOUGAR-X(D) (except for cameras with IMX sensors): Added new binning and decimation capabilities. - mvBlueCOUGAR-X(D)104/204(a(12)/b)G/C: Added support for sensor's vertical decimation feature with steps 2, 4, 8, 16. Sensor discards data. - mvBlueGEMINI: Lines will only appear as valid sources when configured as inputs now. - mvBlueFOX3: Defective pixel data can be stored permanently on cameras now. Changed behaviour: - TriggerSoftwareCommand returns GENCP_BUSY if camera isn't ready for trigger. Bugs Fixed: - Reading CounterValueAtReset did not work without reading CounterValue first. - mvBlueFOX3 and mvBlueCOUGAR-XD: CounterValueAtReset wasn't updated on a "software reset" - mvBlueCOUGAR-X(D)104/204(a(12)/b)G/C: mvResultingFramerate was not reached for mvAcquisitionFrameRateLimitMode = mvDeviceMaxSensorThroughput. - mvBlueCOUGAR-X102eG/C/GE, mvBlueFOX3-1013G/C, mvBlueFOX3-1020aG/C: Due to compatibility reasons former device clock frequencies are available again. (Bug introduced in version 2.15.578.0) - mvBlueFOX3-1012b/dG/C, mvBlueCOUGAR-X102b/dG/C: MaxValue for AcquisitionFrameRate corrected. - mvBlueCOUGAR-X/XD: Camera could crash after writing userfile. - Corrupt images could occur when changing width or height while sequencer mode is on. UPDATES: - All the GenICam nodemaps of the GenTL Producer comply with the GenICam GenTL SFNC (mvGenTLProducer.cti) 1.1.1 now. See 'Porting existing code' section in the manual for additional information. CHANGED BEHAVIOUR: - Examples for Visual Studio 2005 are no longer shipped as part of the installation. (all shipped MSI-based packages) Visual Studio 2005 is no longer supported by mvIMPACT Acquire. - All modules belonging to mvIMPACT Acquire are now build with the /DYNAMICBASE and (all shipped MSI-based packages) /NXCOMPAT linker switches for Windows. - The default value of 'ImageProcessing/DefectivePixelsFilter/Mode' is now (all shipped packages) 'dpfm3x3Median' after calibrating or when defective pixel data is detected inside the devices non-volatile memory while it used to be 'dpfmOff'. - Timestamp_us in the request info is based on QueryPerformanceCounter now. (low level mvHYPERION driver, Windows, version 2.1.45.53) - Only supported request info features will be visible now. Features which are not (all shipped packages) supported will also have the 'cfInvisible' flag set for the corresponding property within the 'RequestInfoConfiguration' class. NEW FEATURES: - New menu entry 'Settings -> Image Display -> Configure Images Per Display Count' (wxPropView) added. It allows to display multiple images displayed in a single large buffer. This might e.g. be useful for line scan applications to reconstruct a large image showing the complete object of interest. - Added class mv.impact.acquire.GenICam.DevFileStream for convenient file access for (mv.impact.acquire.dll) GenICam devices. - Support for the multi-part payload format as specified by the GenTL/GigE Vision (all shipped packages) standard added. See 'Image acquisition/Multi-part format' for details and links to (mvGigECapture.sys, version 2.3.1.57) the corresponding API classes and functions. (mvGigECapture2.sys, version 3.1.1.58) - Support for GenICam devices that stream JPEG data added. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - 'BufferPartCount' property added to 'CameraSettingsVirtualDevice' to simulate multi- (mvVirtualDevice-lib) part and JPEG data. - The scaler in 'ImageDestination' list now supports scaling from an AOI instead from (all shipped packages) the whole image. BUGS FIXED: - The minimum value of 'ValueCount' in 'LUTOperations/LUTs/LUT-' in interpolated (all shipped packages) was 1 instead of 2 and setting it to 1 could result in a crash. - On some Linux system the ARP request mechanism did not function properly. This could (mvGenTLProducer.cti) lead e.g. to the auto-configure IP in mvIPConfigure to fail. - Made NDIS 6.x based GEV filter driver 'header-data split' aware. This fixes problems (mvGigECapture2.sys, version 3.0.3.57) with jumbo frames on certain network interfaces where images could not be captured when using large packet sizes. - After canceling the 'Quick Setup' wizard, erroneous values were written into the (wxPropView) ColorTwist matrices, resulting in greyscale-like images when a ColorTwist matrix was enabled again. - Unhandled exception when using the 'Quick Setup' wizard, with mvBlueFOX devices. (wxPropView) (Bug introduced in version 2.19.0) - Constantly calling DMR_Init and DMR_Close or creating and deleting instances of (mvDeviceManager-lib) mvIMPACT::acquire::DeviceManager did cause the 'Path' variable of the calling process to get longer and longer(Windows only). - When loading a stored setting the calibration data for the flat field and dark (all shipped packages) current filter have not been restored. (Bug introduced in version 2.17.1) - On Windows 8 or higher the 'DeviceLinkSpeed' property of the 'InterfaceModule' class (mvGenTLProducer.cti) did report USB2 speed for U3V devices connected with super speed. - Bitshifting in 10-bit YUV pixel formats now only affects the luminance (Y) component. (mvDisplay-lib) This eliminates wrong colors due to the shifting affecting the chroma components too. 21.03.2017 2.19.0 NEW FIRMWARE: - Firmware version 2.19.711.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - When not using ANY of the AOI affecting features 'OffsetX' and 'OffsetY' can be modified at runtime when streaming with an activated sequencer now. - mvBlueCOUGAR-XD204(a/a12/b)G/C, mvBlueFOX3-2024(a)G/C: DecimationVertical can be used separate from BinningHorizontal or DecimationHorizontal. Bugs Fixed: - mvBlueFOX3: Camera could crash if USB connection was disconnected and reconnected while the camera was in standby mode. - Changing area dimensions in mvMultiAreaMode or switching off mvMultiAreaMode led to corrupt images. - 'mvAreaEnable' as it affects the 'PayloadSize' must become read-only when 'TLParamsLocked' is set. - 'mvMultiAreaMode' did not specify the 'streamable' attribute. - Selecting zero areas in multi-area mode crashed the camera under some conditions. - mvBlueCOUGAR-X(D): SequencerMode: Wrong exposure times could occur when using very small exposure times. - GEV test packets are send now even if the host application did not specify the "don't fragment" bit in the SCPS register. - mvBlueCOUGAR-X1010C, mvBlueFOX-1100C: ReverseX led to wrong colors. - mvBlueCOUGAR-XD204(a/a12/b)G/C, mvBlueFOX3-2024(a)G/C: DecimationVertical could not be configured correctly in combination with BinningHorizontal. CHANGED BEHAVIOUR: - Some function have been declared deprecated: (mvDeviceManager.h) - OBJ_IsSettingAvailable, use DMR_IsSettingAvailable instead. - OBJ_DeleteSetting, use DMR_DeleteSetting instead. UPDATES: - When running in chunk mode with the 'Image' chunk disabled the driver will use less (mvGenTLConsumer-lib) memory now. - Using mvMultiAreaMode of the camera can lead to corrupt images unless updating firmware to 2.19.xxx.x or greater. NEW FEATURES: - Initial version of the 'Multi AOI' wizard added. (wxPropView) - Added new command line parameters to enable/disable the filter driver on one or (mvGigEConfigure) multiple network interfaces. See tool output window for details. - Added new command line parameter to configure whether the NDIS filter driver shall (mvGenTL_Acquire*.msi) be installed automatically or not. See 'Installation from private setup routines' and search for 'GEV_NDIS_DRIVER_INSTALL' for details. - Whenever a new log-file is created (or and old one is overwritten) the previous file (all shipped packages) will be moved to . So now the log-output of the last 2 sessions of mvIMPACT Acquire will be available. - Added 'mvLensCalibrationEnable' property to mvIMPACT::acquire::GenICam::AcquisitionControl (C++) and (mvIMPACT_acquire.h) mv.impact.acquire.GenICam.AcquisitionControl (.NET) (mv.impact.acquire.dll) - 'SequencerSetStart' can now be explicitly set in the sequencer wizard. (wxPropView) - Capture settings can be stored in RAM now. See description of the function (all shipped packages) 'saveCurrentSettingOnStack' of the FunctionInterface class for one way of using this. - New functions added to API: - C API: DMR_IsSettingAvailable, DMR_DeleteSetting (mvDeviceManager-lib) - C++ API: mvIMPACT::acquire::FunctionInterface got the following new member (mvIMPACT_acquire.h) functions: deleteSettingFromStack, deleteSetting, isSettingAvailable, loadSettingFromStack, loadAndDeleteSettingFromStack, saveCurrentSettingOnStack. - .NET API: mv.impact.acquire.FunctionInterface got the following new member (mv.impact.acquire.dll) functions: deleteSettingFromStack, deleteSetting, isSettingAvailable, loadSettingFromStack, loadAndDeleteSettingFromStack, saveCurrentSettingOnStack. - New command line parameter added: 'fullscreen' or 'fs'. (wxPropView) BUGS FIXED: - Running the ColorTwist filter on Linux with RGB planar formats could result in (all shipped packages for Unix/Linux systems) crashes. (Bug introduced in version 2.13.6) - On some occasions when a mvBlueFOX camera would come out of the powered down state (mvBlueFOX-lib) the driver would fail to acquire images. - Linux installer scripts now take unused memory into account before spawning multiple (all shipped packages for Unix/Linux systems) threads for parallel compilation of mv sources during installation. This eliminates potential hangs during installation of MATRIX VISION Linux drivers due to lack of free memory on the target platform. - Starting the acquisition did reset the current scroll position of the display window (wxPropView) to the left upper corner of the image. - When pressing 'Cancel' in the 'Quick Setup' wizard, the exposure time would be set (wxPropView) equal to the AutoExposureUpperLimit, instead of it's default value on some occasions. - Potential crash when closing the device properties dialog from a DirectShow (DirectShow_acquire.ax) application. 09.02.2017 2.18.3 NEW FIRMWARE: - Firmware version 2.18.651.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-2024(a)G/C, mvBlueFOX3-2032(a)G/C, mvBlueFOX3-2051(a)G/C, mvBlueFOX3-2089G/C, mvBlueFOX3-2124G/C, mvBlueCOUGAR-X(D)104d/f/h/iG/C, mvBlueCOUGAR-X(D)105a/bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-X1012bG/C: Multi area mode implemented as described in the respective sensor specification. Changed behaviour: - mvBlueFOX3-2032(a)G/C, mvBlueFOX3-2051(a)G/C, mvBlueFOX3-2089(a)G/C, mvBlueFOX3-2124(a)G/C, mvBlueCOUGAR-X(D)104h/iG/C, mvBlueCOUGAR-X(D)105a/bG/C, mvBlueCOUGAR-X(D)109bG/C, mvBlueCOUGAR-X(D)1012bG/C: Increments for Height and OffsetY increased to 4. Bugs Fixed: - mvBlueFOX3 (all models): cameras did not start correctly if the USB connection was disconnected and reconnected while the camera was in standby; this could also happen if the host was switched off and on again while an externally powered camera was in standby mode. UPDATES: - Adapted firmware update procedure to new product naming scheme. (mvDeviceConfigure) NEW FEATURES: - New properties published in API: C++: mvIMPACT::acquire::Device::manufacturerSpecificInformation, (mvIMPACT_acquire.h) mvIMPACT::acquire::SystemSettings::featurePollingEnable, mvIMPACT::acquire::SystemSettings::featurePollingInterval_ms, mvIMPACT::acquire::SystemSettings::methodPollingInterval_ms, mvIMPACT::acquire::SystemSettings::methodPollingMaxRetryCount. .NET: mv.impact.acquire.Device.manufacturerSpecificInformation, (mv.impact.acquire.dll) mv.impact.acquire.SystemSettings.featurePollingEnable, mv.impact.acquire.SystemSettings.featurePollingInterval_ms, mv.impact.acquire.SystemSettings.methodPollingInterval_ms, mv.impact.acquire.SystemSettings.methodPollingMaxRetryCount. BUGS FIXED: - Data-streams coming from a GEV 2.x device with 64-bit block ID switched off have not (mvGenTLProducer.cti) not been decoded correctly when the socket driver was active. - Legacy 16-bit block ID mode is only used when a GEV 2.x device actually claims to (mvGenTLProducer.cti) support it. - It is no longer possible to assign an invalid persistent IPv4 address to a GEV (mvIPConfigure) device. 02.02.2017 2.18.2 NEW FIRMWARE: - Firmware version 2.17.641.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-X104iG/C, mvBlueCOUGAR-X105bG/C: support for extended horizontal and vertical Binning/Decimation up to 16x16 - mvBlueCOUGAR-X104dG/C, mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-X105bG/C, mvBlueCOUGAR-X104iG/C, mvBlueCOUGAR-X1012bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD1012bG/C, mvBlueCOUGAR-XD109bG/C, mvBlueFOX3-2024G/C, mvBlueFOX3-2024aG/C, mvBlueFOX3-2051G/C, mvBlueFOX3-2051aG/C, mvBlueFOX3-2032G/C, mvBlueFOX3-2032aG/C, mvBlueFOX3-2124G/C, mvBlueFOX3-2124aG/C, mvBlueFOX3-2089G/C, mvBlueFOX3-2089aG/C: support for OffsetX and OffsetY in sequencer - mvBlueCOUGAR-X(D), mvBlueFOX3: Added support for the 'chunk layout id' feature. This update requires mvIMPACT Acquire 2.18.1 or greater! - mvBlueCOUGAR-X(D): Added support for 'ExtendedChunk' mode. This update requires mvIMPACT Acquire 2.18.1 or greater! Changed behaviour: - mvBlueFOX3: When the image itself is not transferred in chunk mode the payload type will be 'Chunk' not 'Image Extended Chunk' now. - All features that affect the payload size can no longer be disabled via 'SequencerFeatureEnable'. So if the sequencer is used, all these properties are always part of the sequencer sets. Bugs Fixed: - When the sequencer was running the exposure time value was sometimes taken from the stored sequencer set even if 'SequencerFeatureEnable[SequencerFeatureSelector]' for 'ExposureTime' was set to false. - mvBlueFOX3-1020aG/C: Frame rate was halved for special AOI and exposure time settings. CHANGED BEHAVIOUR: - The 'mvIMPACT_AcquireExecutablesPrerequisites' merge module became a central (all shipped MSI based packages) requirement for all installations. As a consequence it will always be installed now. This will make redistributing custom installations in need of the mvDisplay-lib much easier but will not affect others. UPDATES: - Improved execution speed for GenICam property function calls. Previous versions did (mvGenTLConsumer-lib) sometimes read features selected by a selector when changing the selector value even if the application never accessed the selected features. NEW FEATURES: - The settings of all devices currently opened in wxPropView will be added to the (wxPropView) ZIP-archive containing the log-files now. BUGS FIXED: - Sometimes 'mvBlueFOX-MLC202bx' and 'mvBlueFOX-MLC202dx' devices did not start (mvBlueFOX-lib) properly on Windows 10. As a result no images could be acquired even though communication with the sensor does work properly. - In Linux systems, under some circumstances a libusb segmentation fault could occur. (mvGenTLProducer.cti) (Bug introduced in version 2.17.3) - When a 'SequencerFeatureEnable' property was read-only the sequencer wizard could (wxPropView) crash. - Fixed an issue where the property grid did not receive the focus when expanding or (wxPropView) collapsing items in the tree. As a result using the scrollwheel of the mouse did not scroll within the tree but e.g. did select another device - The sequencer wizard did not dynamically respond to changes in the properties thus (wxPropView) e.g. changing 'BinningHorizontal' did not automatically update the limits for 'Width'. 20.01.2017 2.18.1 NEW FIRMWARE: - Firmware version 2.16.624.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD109bG/C, mvBlueCOUGAR-XD1012bG/C: Added Support for Vertical Binning(SUM)/Decimation(AVERAGE) - Added BinningHorizontalMode, BinningVerticalMode, DecimationHorizontalMode and DecimationVerticalMode properties. Changed behaviour: - mvBlueFOX3-1031C, mvBlueFOX3-1100G/C: For compatibility reasons: AcquisitionFrameRate is not used in trigger mode. Bugs Fixed: - 'SequencerMode' becomes read-only now when streaming is active. - mvBlueFOX3: AcquisitionFrameRate was not handled correctly when using UserSets. UPDATES: - The GenTL producer is now fully compliant with the current GenTL validation (mvGenTLProducer.cti) framework. - The DirectShow interface related header files will be installed by default now. (all shipped MSI based packages) - When using the merge modules supporting Windows 10 no longer needs special treatment. (all shipped MSI based packages) - Improved performance when dealing with chunk data delivered by devices supporting the (mvGenTLConsumer-lib) chunk layout ID feature. NEW FEATURES: - Multiple display windows can be created and deleted dynamically now(see (wxPropView) 'Settings->Image Display->Configure Image Display Count'). The sequencer wizard has an 'Auto-Assign Displays To Sets' button now. - Added new C# example: SmartFrameRecall. (all shipped MSI based packages) - Added new functions to 'mv.impact.acquire.GenICam.CustomCommandGenerator' and 'mvIMPACT::acquire::GenICam::CustomCommandGenerator' that allow to send multiple smart frame recall transmission requests in a single command. - 'Feature vs. Time' plot added to the analysis section in the lower right side of the (wxPropView) screen. BUGS FIXED: - The installation of the serial port driver on Windows Vista - Windows 10 was broken (mvHYPERION-x86_64-*.msi) on 64 platforms. (Bug introduced in version 2.18.0) - The 32-bit installation for mvBlueFOX, mvSIGMA and mvTITAN drivers on Windows 10 (mvBlueFOX-x86-*.msi) did not install the Microsoft signed driver. (mvTITAN_mvGAMMA-x86-*.msi) (mvDELTA_mvSIGMA-x86-*.msi) - Potential crash when using the temporal noise histogram in full AOI mode when image (wxPropView) sizes did change. - Sometimes 'bind' requests to the socket dealing with the GEV streaming data could (mvGenTLProducer.cti) fail. - The recording will only stop early in low memory conditions when the sequence to (wxPropView) record is larger than the number of available request objects, thus when the requests need to be copied by the application. - The X and Y offset was not taken into account when working with DirectShow. (DirectShow_acquire.ax) (mvGenTLConsumer-lib) - mvBlueCOUGAR-X devices with firmware revisions smaller than 1.5.75.0 could not be (mvGenTLConsumer-lib) initialized in 'DeviceSpecific' interface layout any more. (Bug introduced in version 2.15.1) - When disconnecting a U3V device supporting events on Windows sometimes the (mvGenTLProducer.cti) internal event thread did not properly terminate but did generate lots of 'An unexpected system error did occur: 0x0000001f(31)' errors. - Potential crash when modifying properties while 'SystemSettings/FeaturePollingEnable' (mvGenTLConsumer-lib) was active and a device had a lot of polling times defined in its XML file. - For properties specifying the 'cfAllowValueCombinations' flag it was no longer (wxPropView) possible to select no option after selecting at least one for the first time. (Bug introduced in version 2.17.0) 13.12.2016 2.18.0 NEW FIRMWARE: - Firmware version 2.15.578.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-XD104G/C, mvBlueCOUGAR-XD104aG/C, mvBlueCOUGAR-XD104a12G, mvBlueCOUGAR-XD104bG/C, mvBlueCOUGAR-XD104baG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD109bG/C, mvBlueCOUGAR-XD1012bG/C: SmartFrameRecall feature implemented. - mvBlueFOX3, mvBlueCOUGAR-X(D): support for custom command that allows to modify gain, exposure and counter duration in a sequencer set while the sequencer is running Changed behaviour: - mvBlueCOUGAR-XD126G/C, mvBlueCOUGAR-XD129G/C: DecimationVertical is only available for SensorTaps = Two. Bugs Fixed: - BF3-2xx: Using special sequencer settings (small AOIs and Binning/Decimation) could lead to limited bandwidth. - DeviceLinkHeartbeatMode was inverted. Switching it off turned it on and vice versa. - mvBlueFOX-1013G/C, mvBlueFOX-1020G/C, mvBlueFOX-1020aG/C, mvBlueCOUGAR-X102eG/C, mvBlueCOUGAR-X104eG/C: Some cameras have wrong pixels in one column. UPDATES: - Internal migration to Doxygen 1.8.12. NEW FEATURES: - Kernel drivers are signed by the Windows Hardware Developer Center Dashboard portal (all shipped MSI based packages) for Windows 10 installations now. Since Windows 10 version 1607 a fresh Windows installation will no longer accept other signatures. - On Linux systems, GEV cameras with bad network configurations now appear on the (mvIPConfigure) device list. - New header file added to C/C++ interface: mvCustomCommandDataTypes.h (all shipped packages) - New header file added to C++ interface: mvIMPACT_acquire_GenICam_CustomCommands.h. (all shipped packages) This file adds the class 'mvIMPACT::acquire::GenICam::CustomCommandGenerator' to the public interface. - Class 'mv.impact.acquire.GenICam.CustomCommandGenerator' published. (mv.impact.acquire.dll) - New samples added to all packages: 'GenICamSmartFrameRecallUsage' and (all shipped packages) 'GenICamSequencerParameterChangeAtRuntime'. - Major Sequencer Wizard overhaul, with new capabilities and new user interface. (wxPropView) BUGS FIXED: - On some systems resetting the camera during Auto-assigning the DHCP option caused (mvIPConfigure) the application to misbehave. (Bug introduced in version 2.17.3) - Devices sending an invalid value for 'valid_chunk_data' in their trailer packet could (mvGenTLProducer.cti) cause crashes. - When a sequence has been recorded displaying the very last image could cause a crash (wxPropView) (Bug introduced in version 2.17.3) - Some of the values stored for the settings of the analysis controls where properly (wxPropView) read back when restarting the application but haven't been applied. - Shortcuts to various examples applications created in the programs menu under (all shipped MSI based packages) 'Programs -> MATRIX VISION -> mvIMPACT Acquire -> Examples' did point to incorrect targets. (Bug introduced in version 2.12.3) - Drivers can be installed on Windows Vista and older again. (all shipped MSI based packages) (Bug introduced in version 2.16.0) - Commands 'DefectivePixelReadFromDevice' and 'DefectivePixelWriteToDevice' will only (all shipped packages) visible now when the device supports loading and storing of defective pixel data in non-volatile memory. - Defective pixel data is correctly read back from a setting into the properties (all shipped packages) 'DefectivePixelOffsetX' and 'DefectivePixelOffsetY' now. - For certain sensors it was possible to set 'Aoi/X' or 'Aoi/Y' to a value that in (mvBlueFOX-lib) combination with 'Aoi/W' or 'Aoi/H' did result in an AOI too small finally resulting in a crash. - Calling 'OBJ_DeleteSetting' for a setting that does not exist OR for a setting for (mvPropHandling-lib) which the current user has no sufficient access rights returns an error now. - When running on Windows 10 the log messages did report Windows 8.1. (all shipped MSI based packages) 01.11.2016 2.17.3 NEW FIRMWARE: - Firmware version 2.14.507.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Sequencer settings are saved in UserSets. - mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-X104iG/C, mvBlueCOUGAR-X105bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-X1012bG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD109bG/C, mvBlueCOUGAR-XD1012bG/C: Extended sequencer mode: Gain and Binning/Decimation - mvBlueFOX3-2xx: Extended sequencer mode: Gain and Binning/Decimation - mvBlueCOUGAR-X(D)x2xxG/C (cameras with CCD sensors): Extended sequencer mode: Gain Changed behaviour: - Binning and Decimation Properties now use the 'ValidValueSet' attribute. - If a sensor specific color correction matrix is available it will be used to initialize the color transformation control features Bugs Fixed: - mvGainAutoLowerLimit could not set different from 0. UPDATES: - Improved firmware update for GEV devices. Added nicer progress dialogues providing (mvDeviceConfigure) more feedback about the current status of the update process. - Internal migration to IPP 2017. (all shipped packages) CHANGED BEHAVIOUR: - Removed toolbar for page selection from property grid. The 'Driver' properties are (wxPropView) accessible under the 'Device Driver' category from the main property grid now. - Changing the 'CPU Idle States' is no longer available starting from Windows 8 as the (mvDeviceConfigure) underlying API is no longer supported by the operating system. NEW FEATURES: - 'ValidValueSet' nodes in a GenICam XML file will result in a translation dictionary (mvGenTLConsumer-lib) containing all these values being attached to that property now. As a result these properties will automatically be displayed with a drop down box in wxPropView and similar tools. - mvIPConfigure now offers various ways of automatically assigning valid network (mvIPConfigure) configurations to detected devices that are configured incorrectly. - Support for Hotplugging of U3V devices on Linux systems. (mvGenTLProducer.cti) - mvIMPACT::acquire::Request::getChunkGainCount, (mvIMPACT_acquire.h) mvIMPACT::acquire::Request::getChunkGain and mvIMPACT::acquire::Request::chunkmvCustomIdentifier added. - mv.impact.acquire.Request.chunkGainCount, (mv.impact.acquire.dll) mv.impact.acquire.Request.getChunkGain and mv.impact.acquire.Request.chunkmvCustomIdentifier added. - The wxPropView recording sequence size is no longer limited to the number of request (wxPropView) objects allocated for the selected device driver instance. If the number of frames to record is higher than the number of requests the images will be copied and stored in RAM. BUGS FIXED: - When closing one of the GUI applications in 'maximized' mode the next time the (all wxWidgets based applications) application did start parts of the application have been hidden by the Windows taskbar. - When one of the GUI applications was moved out of the left side of the screen its (all wxWidgets based applications) x-position was not correctly restored upon the next start - The splash screen is displayed at least for one second now. (all wxWidgets based applications) - Spin-editors will accept a ',' as a floating point value separator again. (wxPropView) (Bug introduced in version 2.17.0) - Calling 'mvDispSetImage' with mono/grey-scale data and a pitch not divisible by 4 (mvDisplay-lib) results in a correct display now. Missing mv.impact.acquire.SystemSettings.imageProcessingMode property added(.NET) (mv.impact.acquire.dll) - When the currently selected property in the property tree became read-only it still (wxPropView) seemed to be writeable and vice versa. - The *.mvlog files contained in the automatically generated ZIP-file had their (wxPropView) original content overwritten by one line only, containing the path of the logfile itself. - On Linux systems with more than one network adapter the link speed of the last one (mvIPConfigure) inquired was shown as the link speed for all of them. - On Linux systems updating the Firmware of GEV devices could sometimes lead to (mvDeviceConfigure) a segmentation fault. 21.09.2016 2.17.2 NEW FIRMWARE: - Firmware version 2.13.460.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-1031C : FrameStart and FrameBurstActive trigger are available. - mvBlueFOX3-1100G/C, mvBlueCOUGAR-X1010G/C : FrameStart trigger can also be used with rolling shutter. - mvBlueFOX3-2124C, mvBlueFOX3-2089C support BinningHorizontal. Changed behaviour: - mvBlueFOX3-1100G/C : Enabling FrameStart trigger no longer switch to global reset mode automatically. - mvBlueFOX3-2024aG/C, mvBlueCOUGAR-X104fG/C: Minimal exposure time is now only 10 usec. Bugs Fixed: - mvBlueFOX3 devices at certain temperatures sometimes did not boot correctly. - mvBlueFOX3-2024G/C: BalanceWhiteAuto, GainAuto and ExposureAuto features no longer reduce the maximum frame rate if activated. CHANGED BEHAVIOUR: - Restored old (pre 2.17.0) bit shift behaviour. (mvDisplay-lib) - Added a check for the presence of KB3033929 which is needed on Windows 7 and (all shipped MSI based packages) earlier for the processing of SHA256 signatures introduced in version 2.16.0. NEW FEATURES: - ARMv8-a (Aarch64) support added for mvGenTL_Acquire and mvBlueFOX. This will add (mvBlueFOX-ARM64_gnu-*.tgz) support for various Aarch64 platforms running at least ubuntu 14.04 or a compatible (mvGenTL_Acquire-ARM64_gnu-*.tgz ) system. - For Windows 8 and greater the 'FullScreen' option in wxPropView became available. (wxPropView) The image will be rendered using Direct3D 9 now. BUGS FIXED: - Splashscreen of GUI tools is now displayed correctly on Linux systems. Furthermore on (wxPropView) both linux and windows systems it is no longer 'always-on-top', thus no longer hides (mvDeviceConfigure) clickable dialog boxes. (mvIPConfigure) - Fixed potential crash when opening the Sequencer Wizard for GenICam devices. (wxPropView) - Fixed potential crash when using the 'Send Logfiles to MV-Support' functionality. (wxPropView) - Fixed an issue where the property grid did not always receive the focus when clicking (wxPropView) on it. As a result e.g. clicking on the property grid after selecting a device using the scrollwheel of the mouse did not scroll within the tree but did select another device. - Switching to 'FullScreen' mode on Windows 7 or smaller or changing the setting (wxPropView) 'Settings -> Property Grid -> Create Editors With Sliders' no longer raises an assertion. (Bug introduced in version 2.17.0) 30.08.2016 2.17.1 NEW FIRMWARE: - Firmware version 2.12.426.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-X(D) (res. > 1600x1200): Storing of defective pixel positions possible. - New cameras: mvBlueFOX3-2124aG/C, mvBlueFOX3-2089aG/C, mvBlueCOUGAR-X1012bG/C, mvBlueCOUGAR-X109bG/C, mvBlueCOUGAR-XD1012bG/C, mvBlueCOUGAR-XD109bG/C - mvBlueFOX3: LED can be switched off - mvBlueFOX3: camera can automatically switch to standby if inactive Restrictions: - mvBlueFOX3-2024aG/C, mvBlueCOUGAR-X104fG/C: Minimal exposure time increased to 30 usec. Changed behaviour: - BF3-2xx: Enhanced sequencer mode: Sequencered images with BinningHorizontal and/or BinningVertical may now be captured at higher frame rates if sensor supports this increase. - mvBlueFOX3: settings (except LUT values) are restored after standby Bugs Fixed: - mvBlueFOX3-2xxx devices at certain temperatures sometimes did not boot correctly. UPDATES: - Incorrectly configured GigE Vision devices (no matching IPv4 address or netmask) do (mvGenTLProducer.cti) no longer delay 'updateDeviceList' calls. As a result starting the applications like wxPropView, mvIPConfigure and mvDeviceConfigure will start much faster now. CHANGED BEHAVIOUR: - Changed name of NDIS 6.x based filter driver files from 'mvGigECapture.*' to (mvGigECapture2.sys, version 3.0.2.56) 'mvGigECapture2.*' in order to allow easier switching between the NDIS 5.x and the NDIS 6.x drivers. NEW FEATURES: - Added 'mvDefectivePixelCorrectionControl' class to GenICam namespace (mvIMPACT_acquire.h) (mv.impact.acquire.display.dll) - Added properties 'DefectivePixelOffsetX' and 'DefectivePixelOffsetY' and commands (mvIMPACT_acquire.h) 'DefectivePixelReadFromDevice' and 'DefectivePixelWriteToDevice' to class (mv.impact.acquire.display.dll) 'ImageProcessing. - Added 'mvDeviceStatusLEDEnable', 'mvDeviceStandbyTimeoutEnable' and (mvIMPACT_acquire.h) 'mvDeviceStandbyTimeout' to class 'GenICam::DeviceControl' (mv.impact.acquire.display.dll) - New color correction matrices added: 'cticmmBlueCOUGAR_Xx09bC_WPPLS', (all shipped packages) 'cticmmBlueCOUGAR_Xx012bC_WPPLS', 'cticmmBlueCOUGAR_XDx09bC_WPPLS', 'cticmmBlueCOUGAR_XDx012bC_WPPLS', 'cticmmBlueFOX3_x124aC_WPPLS'. They will be used by mvBlueCOUGAR-X_x09bC, mvBlueCOUGAR-X_x012bC, mvBlueCOUGAR-XDx09bC, mvBlueCOUGAR-XDx012bC and mvBlueFOX3_x124aC devices respectively. - MATRIX VISION GenICam devices supporting the 'mvDeviceStandbyTimeout' feature will (mvGenTLConsumer-lib) exchange heartbeat messages with the device when this feature is active to prevent the device from moving into power down mode while the application is running. BUGS FIXED: - Changing features that have impact on the value of 'PayloadSize' AFTER queuing at (mvGenTLConsumer-lib) least one buffer and BEFORE calling 'acquisitionStart' in chunk mode could result in buffers being returned to the application with an incorrect 'Request::imageSize' value (just the size of the image data without the additional chunk data space was reported then). - Unplugging or rebooting a U3V device with event support with an open driver instance (mvGenTLProducer.cti) could cause a handle leak on Windows. - Potential blue screen (BSOD) when binding the filter driver didn't succeed. (mvGigECapture2.sys, version 3.0.2.56) - Removing the GigE Vision filter driver when uninstalling the mvIMPACT Acquire package (mvGenTL_Acquire*.msi) did not work. (Bug introduced in version 2.6.3) - Downgrading the GigE Vision filter driver from the NDIS 6.x back to the NDIS 5.x (mvGigECapture2.sys, version 3.0.2.56) version did not work properly. (mvGenTLProducer.cti) (mvGigEConfigure) 04.08.2016 2.17.0 NEW FIRMWARE: - Firmware version 2.11.383.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-1031C: HDR mode can be enabled - New features published: 'mvU3VLNKErrorCount' and 'mvU3VPHYErrorCount'. Both features can be found in the 'TransportLayer' category. They provide information about the quality of the USB connection. Changed behaviour: - Deprecated some features with respect to the latest SFNC 2.3: 'GevGGVCPPendingTimeout' (use 'DeviceLinkCommandTimeout' instead), 'GevGVCPHeartbeatDisable'(use 'DeviceLinkHeartbeatMode' instead) 'mvAcquisitionFrameRateEnable' (use 'AcquisitionFrameRateEnable' instead) Bugs Fixed: - BF3-2xx: BF3-2xxx: The first image after an acquisition start was sometimes still using the old exposure time. - BCX: Sometimes the camera could crash while streaming to a multicast address. UPDATES: - Migration to wxWidgets 3.x. All wxWidgets based applications are built using (all shipped packages) wxWidgets 3.x now. Apart from wxPropView all applications can still be built using at least wxWidgets 2.6. However wxPropView uses the wxPropertyGrid classes which have been added to wxWidgets 3.0 thus here at least this version is a hard requirement. The old wxPropGrid is no longer shipped with mvIMPACT Acquire. - Migration to an NDIS 6.x based GEV filter driver on Windows Vista or newer. This (mvGigECapture.sys, version 3.0.1.55) new filter driver can be used on Windows 10 as well now. The NDIS 5.x based driver (mvGigECapture.sys, version 2.2.0.54) will still be installed on older Windows systems not supporting the NDIS 6.x framework. - Color correction matrices 'cticmmBlueCOUGAR_XDx04dC_WPPLS', (all shipped packages) 'cticmmBlueCOUGAR_Xx04fC_WPPLS', 'cticmmBlueFOX3_x024C_WPPLS', 'cticmmBlueFOX3_x024aC_WPPLS', 'cticmmBlueCOUGAR_Xx04iC_WPPLS', 'cticmmBlueCOUGAR_Xx05bC_WPPLS', 'cticmmBlueCOUGAR_XDx04hC_WPPLS', 'cticmmBlueCOUGAR_XDx05aC_WPPLS', 'cticmmBlueFOX3_x032C_WPPLS', 'cticmmBlueFOX3_x032aC_WPPLS', 'cticmmBlueFOX3_x051C_WPPLS', 'cticmmBlueFOX3_x051aC_WPPLS', 'cticmmBlueFOX3_x124C_WPPLS', 'cticmmBlueFOX3_x089C_WPPLS' and 'cticmmBlueFOX3_x089aC_WPPLS' updated. CHANGED BEHAVIOUR: - Bit shifting images in wxPropView with multi-byte pixel formats now displays the (mvDisplay-lib) actual bit of the pixels. This might result in solarize effects. NEW FEATURES: - Added support for pixel format RGB888Planar. (all shipped packages) - A new CameraLink configuration with 16bits per pixel and 2 pixels per clock that is (mvHYPERION-lib) not included in the CameraLink Standard is now supported. - 'Copy To Clipboard' and 'Set From Clipboard' option added to the property grids (wxPropView) context menu. - ContinuousCaptureToUserMemory can be built with OpenCV support now and has been added (all shipped packages) to the Linux installation packages as well. - New constructors added to mvIMPACT::acquire::GenICam::SystemModule (mvDeviceManager-lib) and mvIMPACT::acquire::GenICam::InterfaceModule. They can be used without any valid (mvIMPACT_acquire.h) pointer to a device. - wxPropView and mvDeviceConfigure will warn on incorrectly set up GenICam devices when (wxPropView) trying to open one of these devices. In previous versions these devices could only be (mvDeviceConfigure) seen using mvIPConfigure which is not the first application you would normally launch. - New property 'StatusLEDEnable' published under 'SystemSettings' for mvBlueFOX (mvBlueFOX-lib) devices. - New test image format added: 'vdtmMovingRGB888PlanarImage'. (mvVirtualDevice-lib) BUGS FIXED: - Once the property 'RequestCount' has been modified by an application it did no longer (mvPropHandling-lib) turn read-only during acquisition for GenICam devices. - 'FunctionInterface::imageRequestReset' did not always return when using infinite (mvGenTLProducer.cti) buffer timeouts in triggered mode with no trigger when calling functions in the following sequence: imageRequestSingle, acquisitionStart, imageRequestSingle, imageRequestWaitFor, imageRequestReset. - 'FunctionInterface::imageRequestReset' did not always return when using (mvGenTLConsumer-lib) acquisitionStartStopBehaviour == assbUser and at least 2 threads in which one thread constantly calls 'imageRequestSingle' while the other calls 'acquisitionStop' and 'imageRequestReset'. - Potential crash when calling 'updateDeviceList' after a failed attempt to open a (mvGenTLConsumer-lib) GenICam compliant device. (Bug introduced in version 2.16.0) 17.06.2016 2.16.1 NEW FIRMWARE: - Firmware version 2.10.326.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - BF3-2xx: Extended sequencer mode: Binning can be used. - Support BCX-104iG/C-POE cameras. - mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD104hG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-X104iG/C, mvBlueCOUGAR-X105bG/C, mvBlueFOX3-2024G/C, mvBlueFOX3-2024aG/C, mvBlueFOX3-2032G/C, mvBlueFOX3-2032aG/C, mvBlueFOX3-2051G/C, mvBlueFOX3-2089G/C, mvBlueFOX3-2124G/C: BlackLevelAuto can be set to 'Off'. Bugs Fixed: - BF3-2xx: fixed bug that could lead to white blinking LED on USB errors - BF3-1xx: fixed bug in FrameAverageControl that produced corrupted images when width or height was changed. UPDATES: - Migration to version 3.0.1 of the GenApi runtime. (all shipped packages for GenICam compliant devices) NEW FEATURES: - The 'GenICam' namespace now contains the full SFNC 2.3 feature set. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) 19.05.2016 2.16.0 NEW FIRMWARE: - Firmware version 2.9.284.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Added SHA1 hash to the GenICam file name for GEV devices in order to speed up device initialisation time by avoiding redundant file downloads. - New cameras: mvBlueFOX3-2089G/C Changed behaviour: - Removed all impl-bits from the chunk data to allow offline processing of chunk buffers. - mvBlueFOX3 devices will automatically change their 'mvDevicePowerMode' property back to 'mvActive' when opening the a device currently in standby mode. Bugs Fixed: - mvBlueFOX3-2xxx: Some exposure times led to lower frame rates than expected. - Sometimes, after booting host and a mvBlueCOUGAR-XD simultaneously (2 links), opening the device will fail. - 'SequencerSetNext' no longer requires an explicit call to 'SequencerSetSave' in order to become effective. UPDATES: - *.msi and *.cat files are now signed with a SHA-256 certificate and is timestamped by (all shipped MSI based packages) a SHA-1 timestamp server. All other files will be dual signed with SHA-1 and SHA-256 signatures as since 01.01.2016 tools like e.g. Internet explorer will issue a warning otherwise. This may result in the 'Always trust software from MATRIX VISION' question to be displayed again. This may require KB3033929 and KB2921916 to be installed on Windows 7 and Windows server 2008. Please have a look in the 'Known issues' section of the mvIMPACT Acquire manual. - Initialisation speed for GenICam compliant devices improved. Opening a MATRIX VISION (mvGenTLProducer) GEV device is up to 350ms faster now when the GenICam file has been downloaded for (mvGenTLConsumer) the first time(requires a firmware update). For U3V devices supporting the SHA1 hash the initialisation is up to 450ms faster now. - Import speed for large LUTs from *.csv-files improved. (wxPropView) - The display update frame rate can be configured via 'Settings -> Set Update (wxPropView) Frequency' now. This fixes the problem of a freezing GUI or missing status bar updates at high frame rates. - The 'Detailed Feature Information' dialogue contains information about the binary (wxPropView) data size and the max. binary data size for properties specifying the 'cfContainsBinaryData' flag now. - 'Show Feature Change Time Consumption' option added to 'Settings -> Property Grid'. (wxPropView) - Execution speed from and to 'ibpfYUV411_UYYVYY_Packed' format improved. (all shipped packages) - The capture pin property dialogue will automatically expand the device feature tree (DirectShow_acquire.ax) now as wxPropView does it when opening a device. - mvHYPERION Linux kernel driver and the respective installers now support kernel 4.0. (low level mvHYPERION driver, Linux) CHANGED BEHAVIOUR: - Interface layout 'dilGeneric' has been removed from the public interface. It has been (all shipped packages) declared deprecated for almost 4 years now. This might break existing binaries and will require changes in the source during rebuilds. Systems depending on the generic interface layout will NO LONGER WORK starting from this version of mvIMPACT Acquire. Please update your code as described in the documentation. - When opening a GenICam device, an AcquisitionStop command will now be sent, just in (mvGenTLConsumer-lib) case the previous process using the device crashed unexpectedly. NEW FEATURES: - Automatically joining multicast groups of GEV devices can be disabled now via the (mvGenTLProducer.cti) property mvAutoJoinMulticastGroups. - New color correction matrices added: 'cticmmBlueFOX3_x124C_WPPLS', (all shipped packages) 'cticmmBlueFOX3_x089C_WPPLS' and 'cticmmBlueFOX3_x089aC_WPPLS'. These will be used by 'mvBlueFOX3_x124C', 'mvBlueFOX3_x089C' and 'mvBlueFOX3_x089aC' devices respectively. - Initial version of the 'Sequencer Control' wizard added. For devices running with the (wxPropView) GenICam interface layout this wizard will allow convenient access to sequencer control related features. BUGS FIXED: - The 'TapSort' filter for 1Y2 and 2YE data did not re-order the data correctly when (mvTITANfg-lib) operated in image processing mode 'ipoMinimizeMemoryUsage'. (mvHYPERIONfg-lib) (mvVirtualDevice-lib) - 'TLGetInfo' did return 'INFO_DATATYPE_INT32' instead of 'INFO_DATATYPE_UINT32' for (mvGenTLProducer.cti) the data type query of 'TL_INFO_GENTL_VER_MAJOR' and 'TL_INFO_GENTL_VER_MINOR'. - Potential crash when running the de-Bayer filter on Linux. (all shipped packages) - 'imageRequestReset' calls did not return until the current image has been generated (mvVirtualDevice-lib) completely and the user defined frame delay (FrameDelay_us) did elapse, thus large frame delays could block an application for a long time. - Images that had a different resulting AOI than set for the device(e.g. because of an (DirectShow_acquire.ax) enabled rotation or scaling filter) have been delivered with incorrect width and height. - Calling 'FunctionInterface::getCurrentCaptureBufferLayout' when the rotation filter (all shipped packages) was active did return a width and height than was 1 pixel and line smaller than the actual resulting image. - Caching of the GenICam XML files did not work correctly on Linux systems. (mvGenTLProducer.cti) 08.04.2016 2.15.2 NEW FIRMWARE: - Firmware version 2.8.241.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New camera: mvBlueFOX3-2124G/C (IMX253) Bugs Fixed: - Frame rate inconsistencies corrected for mvBlueCOUGAR-X105bG/C, mvBlueCOUGAR-X104iG/C and mvBlueFOX3-2032aG/C. UPDATES: - Slightly improved execution speed in general. (mvPropHandling-lib) - Reduced memory footprint in interface layout 'dilGenICam' and 'dilGeneric' by roughly (mvGenTLConsumer-lib) 64KB/request object. NEW FEATURES: - The display supports zoom factors smaller than 1 up to 0.125 now. (wxPropView) BUGS FIXED: - The function TransportLayerControl.gevGetResultingPacketDelay could return negative (mvIMPACT_acquire_GenICam.h) values. (mv.impact.acquire.dll) - Sometimes when an editor in the property grid was selected and then the focus was (wxPropView) transferred to another control within the application later when clicking on another property in the property grid the GUI jump back to the feature previously selected. - Multi-threaded access to library improved. Waiting for error event data while talking (mvGenTLProducer.cti) to the device in parallel is faster now. 28.03.2016 2.15.1 NEW FIRMWARE: - Firmware version 2.7.221.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Bugs Fixed: - mvBlueCOUGAR-X1010G/C: Acquisition could stop when changing exposure time. Bug introduced in version 2.6.148.0. - mvBlueFOX3-2032G, mvBlueFOX3-2051G: Although mvAcquisitionFrameRateLimitMode = mvDeviceLinkThroughput more than 380MByte/s were possible, which results in delayed images. UPDATES: - Improved execution speed of 'PropertyS::readBinary', 'PropertyS::writeBinary' (mvPropHandling-lib) 'PropertyS::binaryDataBufferSize', 'OBJ_GetBinaryBufferSize', 'OBJ_GetBinary' and 'OBJ_SetBinary'. - Slightly improved the initialisation speed for GEV devices by removing some redundant (mvGenTLProducer.cti) register accesses. - GEV devices with an incorrect IP setup correctly update some internal registers like (mvGenTLProducer.cti) current link speed and interface count once the IP configuration has been fixed and the device has been re-discovered in the current process. - minizip is no longer used internally. (mvGenTLConsumer-lib) - Slightly improved heartbeat behaviour for GEV devices. This will result in less (mvGenTLProducer.cti) network traffic on the control channel. - Improved performance when dealing with chunk data delivered by devices supporting the (mvGenTLConsumer-lib) chunk layout ID feature. CHANGED BEHAVIOUR: - The following enumeration values and classes have been removed from the interface (all shipped packages) 'acquire::cfUserAllocatedMemory', 'acquire::PROPHANDLING_NO_USER_ALLOCATED_MEMORY and 'acquire::ENoUserAllocatedMemory'. There is NO direct replacement for all these things, as they haven't been used internally or externally anyway. Simply remove all references from your code. - In case a U3V device did not recover from a reset on the control endpoint(e.g. when (mvGenTLProducer.cti) the device firmware did crash/hang) the driver did hang when the device did continue to send incorrect ACK-ids. NEW FEATURES: - The user can now select whether shortcuts to certain applications shall be created (all MSI-based shipped packages) on the desktop or not. BUGS FIXED: - wxPropView on ARM systems correctly displays captured images again. (wxPropView) (Bug introduced in version 2.14.0) - Changing the exposure time from a very small value to one slightly larger (e.g. from (mvBlueFOX-lib) 12 to 21 us for mvBlueFOX-x00w devices could result in a couple of incorrectly exposed frames. - Installing any installer that is NOT the mvGenTL_Acquire one without also updating (mvDeviceManager-lib) updating the mvGenTL_Acquire package did result in GenICam compliant devices being no longer accessible(Windows only). (Bug introduced in version 2.15.0) - Socket driver did not correctly handle GEV 2.x devices streaming in extended block ID (mvGenTLProducer.cti) mode. - Multi-threaded access to library improved. E.g. calling 'DSClose' in parallel with (mvGenTLProducer.cti) 'EventGetData' sometimes did cause crashes. - Certain large values when written to the AOI width and/or height of the scaler in the (all shipped packages) 'ImageDestination' list could result in a crash. - mvDeviceConfigure refused to update the firmware of mvBlueCOUGAR devices when their (mvDeviceConfigure) 'AcquisitionFrameRate' Property was not visible. 24.02.2016 2.15.0 NEW FIRMWARE: - Firmware version 2.6.180.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Support for new cameras: - mvBlueCOUGAR-X105bG/C (IMX264) - mvBlueCOUGAR-X104iG/C (IMX265) - mvBlueFOX3-2032aG/C (IMX265) Changed behaviour: - mvBlueFOX3-*: Increased event timestamp accuracy. Bugs Fixed: - mvBlueFOX3: FWUpdate from 2.3 ( to 2.4 or 2.5 ) could result in unbootable camera, when starting with saved UserSet. - mvBlueFOX3, mvBlueCOUGAR-X(D): OffsetX and OffsetY appear correctly in the image leader / image info chunk. UPDATES: - Migration to version 3.0.0 of the GenApi runtime. (all shipped packages for GenICam compliant devices) - Migration to version 1.5 of the GenICam GenTL spec. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) CHANGED BEHAVIOUR: - mvDeviceConfigure will reset the 'UserSetDefault' (aka 'UserSetDefaultSelector') to (mvDeviceConfigure) 'Default' during updates and will only restore the user selected values if the user selects to persist the user sets during a firmware update. BUGS FIXED: - The x64 version of wxPropView no longer crashes on Windows 8.1 when opening the (wxPropView) editor for a property containing binary data. This was a bug in wxWidgets that surfaced when migrating to Visual Studio 2013. (Bug introduced in version 2.8.0) - GenICam URL cache is now properly invalidated during firmware updates and/or device (mvDeviceConfigure) resets. (mvGenTLConsumer-lib) - Some issues regarding auto and manual IP assignment on Windows XP systems. (mvIPConfigure) - Configuring IP settings with mvIPConfigure did fail when the GEV camera had been (mvGenTLProducer.cti) first recognized with an invalid IP address. This happened because some optional GEV capabilities were not being recognised correctly due to the IP address mismatch. - The 'Quick Setup' wizard did not always set minimum and maximum Pixelclock correctly. (wxPropView) 09.02.2016 2.14.3 NEW FEATURES: - New color correction matrices added: 'cticmmBlueFOX3_x032aC_WPPLS', 'cticmmBlueFOX3_x051aC_WPPLS', 'cticmmBlueCOUGAR_Xx04iC_WPPLS'. They will be used by mvBlueFOX3_x032aC, mvBlueFOX3_x051aC and 'mvBlueCOUGAR-Xx04iC' devices respectively. (all shipped packages) BUGS FIXED: - If working with medium or full CameraLink cameras trigger mode was not working. (low level mvHYPERION driver, Linux) - Correct error handling when requesting images larger than 512 MB. (low level mvHYPERION driver, Windows, version 2.1.44.52) 27.01.2016 2.14.2 NEW FIRMWARE: - Firmware version 2.5.146.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-2024G/C: Added frame averager. Changed behaviour: - Deprecated SFNC feature made invisible. Introduced their replacements: - 'DeviceSerialNumber' (Replaces 'DeviceID') - 'TestPattern' (Replaces 'TestImageSelector') - 'UserSetDefault' (Replaces 'UserSetDefaultSelector') - All the 'GevSupported...' features (Replaced already by 'GevSupportedOptionSelector' and 'GevSupportedOption'. - mvBlueFOX3-2024G/C, mvBlueFOX3-2051G/C, mvBlueFOX3-2032(a)G/C, mvBlueCOUGAR-X104dG/C, mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-X105bG/C, mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-XD105aG/C, mvBlueCOUGAR-XD104hG/C: changed mapping of luminance LUT on grey cameras from 'map_10To12' to 'map_12To9' and changed mapping of red,green and blue LUTs on color cameras from from 'map_8To12' to 'map_10To9' Bugs Fixed: - mvBlueCOUGAR-X104eG/C, mvBlueFOX3-1020G/C, mvBlueFOX3-1020aG/C: Constant time between trigger and exposure for all exposure times. - Several mvBlueCOUGAR-X / mvBlueCOUGAR-XD / mvBlueFOX3: CounterValueAtReset didn't yield the right value BUGS FIXED: - In Linux systems, mknewappl.sh script no longer generates deprecated code. (all shipped packages for Unix/Linux systems) - 'mvIMPACT::acquire::GenICam::ImageFormatControl::mvDigitizationMode' became (mvIMPACT_acquire_GenICam.h) 'mvIMPACT::acquire::GenICam::ImageFormatControl::mvSensorDigitizationBitDepth' in (mv.impact.acquire.dll) the public API. The Firmware did use that name anyway, thus the features in the API did use an incorrect name before thus always have been invalid. - DMR_ImageRequestReset did not return when a mvHYPERION board was operated in external (mvHYPERION-lib) triggered mode and there was NO trigger signal on Linux. (low level mvHYPERION driver, Linux) - Potential blue screen (BSOD) when requesting images larger than 512 MB on Windows. (low level mvHYPERION driver, Windows) 21.12.2015 2.14.1 NEW FIRMWARE: - Firmware version 2.4.100.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed behaviour: - 'LUTValueAll' is no longer invalidated by 'LUTValue' but now set the 'noCache' attribute. So now each read to 'LUTValueAll' actually reads data from the device, but each write to 'LUTValue' no longer automatically reads 'LUTValueAll' speeding up LUT write operations significantly. Bugs Fixed: - mvBlueFOX3: UserSets saved when connected to USB3 weren't available with USB2 and vice versa. - mvBlueFOX3: Events do not have to be collected any more, even if they were requested before. - mvBlueCOUGAR-X1010G/mvBlueFOX3-1100G: AutoWhiteBalance to reduce chess board pattern did not work for DefaultUserSet != Default. AcquisitionStop at extremely small frame rates caused timeouts. UPDATES: - Slightly improved internal handling for the thread that updates features defining a (mvGenTLConsumer-lib) polling time in their XML file. - Slightly improved color correction wizard. (wxPropView) NEW FEATURES: - New color correction matrix added: 'cticmmBlueCOUGAR_Xx05bC_WPPLS'. This will be (all shipped packages) used by 'mvBlueCOUGAR-Xx05bC' devices. BUGS FIXED: - Boolean properties that specify the 'cfShouldBeDisplayedAsList' flag did not (wxPropView) correctly deal with the index parameter in wxPropView thus only element 0 could be accessed correctly using the check box editors introduced in version 2.14.0. (Bug introduced in version 2.14.0) - When enabling/disabling network or USB interfaces while pressing the 'Update Device (wxPropView) List' button in wxPropView sometimes error messages like 'An exception occurred: NOT_A_PROPERTY while updating feature XYZ' was generated in the 'Output' Window. - Fixed a small resource leak when interfaces did appear and vanish frequently between (mvGenTLConsumer-lib) calls to 'DMR_UpdateDeviceList'. - Potential deadlock when running a triggered acquisition with no trigger signal and (mvBlueFOX-lib) infinite timeouts for the buffers. - IFOpenDevice did return a valid handle even if a particular device could not be (mvGenTLProducer.cti) opened and the GenTL error code was not GC_ERR_RESOURCE_IN_USE. (Bug introduced in version 2.12.2) - Reconnect behaviour improved: Disconnecting a device and calling (mvGenTLProducer.cti) 'DMR_UpdateDeviceList' afterwards did result in devices not being properly (mvGenTLConsumer-lib) reopened until 'DMR_UpdateDeviceList' was called again after plugging the device back in. - Minor memory leak when enumerating USB3 devices (e.g. when updating the device (mvGenTLProducer.cti) list). - 'State' property now correctly describes a mvBlueFOX device as 'Absent' or 'Present' (mvBlueFOX-lib) after updating the device list on Linux systems. - Framestart trigger in CameraLink devices will now always work, even if the camera has (mvHYPERION-lib) a slow pixel clock (~20MHz). 01.12.2015 2.14.0 NEW FIRMWARE: - Firmware version 2.3.73.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New Property 'mvAcquisitionMemoryFrameCount' added. This property contains the number of images currently stored in the frame buffer of the device. If this value increases during normal streaming mode this could indicate a bandwidth shortage. - mvBlueFOX3: ColorCorrectionMatrix added. - New Property 'ColorTransformationSelector' added. Changed behaviour: - mvBlueFOX3: Temperature resolution is .25 now. - 'mvAcquisitionMemoryMaxFrameCount' declared deprecated. Use the maximum value of 'mvAcquisitionMemoryFrameCount' instead. - 'LUTValueAll' is no longer invalidated by 'LUTValue' but now set the 'noCache' attribute. So now each read to 'LUTValueAll' actually reads data from the device, but each write to 'LUTValue' no longer automatically reads 'LUTValueAll' speeding up LUT write operations significantly. Bugs Fixed: - mvBlueFOX3: Negative temperature values were not shown correctly. - mvBlueFOX3: DeviceLinkSpeed and mvResultingFramerate were not updated correctly when switching from a USB2 connection to a USB3 connection. - mvBlueCOUGAR-X1010G/C: Camera could crash, when switching to trigger mode while acquisition is on. - mvBlueFOX3-1100G/C, mvBlueFOX3-1031G/C: Timeouts when switching to continuous mode while acquisition is on. - mvBlueCOUGAR-X105G/C: Reducing the frame rate does no longer result in a 45 second interruption on the streaming channel. - mvBlueFOX3: Sometimes camera did not start after standby mode. - mvBlueFOX3: Events do not have to be collected anymore, even if they were requested before. UPDATES: - Slightly improved update speed for cameras operated in device specific interface (mvGenTLConsumer-lib) layout. - Improved reconnection behaviour for GEV cameras that reconnect with a different (mvGenTLProducer.cti) IP address (e.g. LLA-configured devices ). CHANGED BEHAVIOUR: - The 'Quick Setup' wizard preset "Best Quality" no longer initialises cameras at the (wxPropView) maximum possible frame rate, so that slower Interfaces (e.g. low performance USB controllers) can still show a delay-free live image. NEW FEATURES: - New attribute for features introduced: TComponentRepresentation. It can be used (all shipped packages) to create graphical user interfaces that use custom controls for features with a certain behaviour(e.g. check boxes for features that only have 2 possible states or sliders with logarithmic behaviour for features like exposure time). The following new interface functions have been added: C: OBJ_GetRepresentation, OBJ_GetRepresentationS, OBJ_RepresentationToString C++: mvIMPACT::acquire::Component::representation, mvIMPACT::acquire::Component::representationAsString .NET: mv.impact.acquire.Component.representation, mv.impact.acquire.Component.representationAsString. - New features published: mvIMPACT::acquire::Device::userControlledImageProcessingEnable, (mvIMPACT_acquire.h) mvIMPACT::acquire::SystemSettings::imageProcessingMode, mvIMPACT::acquire::Request::getImageProcessingResultsIterator (C++), mv.impact.acquire.Device.userControlledImageProcessingEnable, (mv.impact.acquire.dll) mv.impact.acquire.Request.imageProcessingResultsIterator (NET). This will allow to control the behaviour of the image processing pipeline. See 'Image Processing' section in the API manuals for more information. - New color correction matrices added: 'cticmmBlueCOUGAR_XDx04hC_WPPLS' and (all shipped packages) 'cticmmBlueFOX3_x032C_WPPLS'. These will be used by 'mvBlueCOUGAR-XDx04hC' and 'mvBlueFOX3_x032C' devices respectively. - New command line parameter added: 'fw_file'. (mvDeviceConfigure) BUGS FIXED: - Using a driver older than version 2.13.3 with wxPropView version 2.13.3 or newer did (wxPropView) not correctly update the status bar. (Bug introduced in version 2.13.3) - 'Quick Setup' wizard now correctly removes any residual digital gain or blacklevel (wxPropView) values, when the respective total value is within the analog range. (Bug introduced in version 2.13.8) - IP autocomplete is no longer triggered when simply reading out the IP of a device. (mvIPConfigure) - mvBlueFOX-x00w: Sometimes the first frame after gain/exposure change had the old (mvBlueFOX-lib) settings. - Switching off the tooltips in wxPropView did still display values that didn't fit (wxPropView) into the editor associated with the value as a tool tip like overlay. - The 'TapSort' filter for 2XE-1Y data did not re-order the data correctly. (mvTITANfg-lib) (Bug introduced in version 2.13.4) (mvHYPERIONfg-lib) (mvVirtualDevice-lib) - The synchronization of the CameraLink medium channels is now implemented in (low level mvHYPERION driver, Linux) the hardware. This results in a more reliable operation and removes effects of (low level mvHYPERION driver, Windows) delayed image processing using ImageRequestSingle. Previous versions sometimes (mvHYPERIONfg-lib) could not perform the synchronization task and under some conditions an ImageRequestSingle was delayed. - Sometimes only parts of an image were captured when buffers where queued and then the (mvGenTLConsumer-lib) acquisition engine was stopped(e.g. due to a power cycle on the device). Then after the connection to the device was re-established a new acquisition was set up with smaller buffer sizes. Then when stopping and restarting the acquisition with a buffer size requirement larger than the current one but smaller or equal to the initial one only data up to the previous buffer size was captured. - The status bar now correctly remembers its own visibility (wxPropView) - Reset behaviour of U3V devices improved on Linux systems. (mvGenTLProducer.cti) - When working with multiple instances of the mvIMPACT::acquire::DeviceManager object (mvIMPACT_acquire.h) the mvIMPACT::acquire::Device::isOpen function did not always return the correct state of the device. 10.11.2015 2.13.8 NEW FIRMWARE: - Firmware version 2.2.36.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New cameras: mvBlueFOX3-2051G/C, mvBlueFOX3-2032G/C, mvBlueCOUGAR-XD104hG/C - mvBlueFOX3-* LUT support. - Added support for the 'DeviceRegistersStreamingStart' and 'DeviceRegistersStreamingEnd' features. Bugs Fixed: - mvBlueCOUGAR-XD104G/C, mvBlueCOUGAR-XD104a12G, mvBlueCOUGAR-XD104bG/C: Additional FrameEndEvents could occur at AcquisitionStart. - mvBlueCOUGAR-XD104d, X104f, mvBlueFOX3-2024, 2024a: In very rare cases booting could lead to corrupt images. - mvBlueCOUGAR-X1010, mvBlueFOX3-1100: Wrong exposure event, when switching to trigger mode. - mvBlueCOUGAR-X1010, mvBlueFOX3-1100: First trigger failed when using exposure times > 210 ms. - mvBlueFOX3: Writing invalid(unaligned) values to the streaming size registers will properly return U3V_STATUS_SI_PAYLOAD_SIZE_NOT_ALIGNED now. UPDATES: - Internal migration to libusb 1.0.20. (mvGenTL_Acquire-*.tgz ) NEW FEATURES: - 'Quick Setup' wizard can now be configured to not pop up automatically when opening (wxPropView) a device, over the relevant item in the menu. - 'Quick Setup' wizard now keeps a history of each property it modifies. (wxPropView) - Support for non-camera devices not supporting the usual set of mandatory features (mvGenTLConsumer-lib) added. - Legacy GenICam XML files specifying invalid register addresses (above the 32-bit (mvGenTLProducer.cti) range) are supported now if the upper bits of the address definitions can be ignored for GigE Vision. - New color correction matrices added: 'cticmmBlueCOUGAR_XDx05aC_WPPLS' and (all shipped packages) 'cticmmBlueFOX3_x051C_WPPLS'. These will be used by 'mvBlueCOUGAR-XDx05aC' and 'mvBlueFOX3_x051C' devices respectively. BUGS FIXED: - Rounding of properties defining a minimum value that did not align with the step (mvPropHandling-lib) width was not done correctly. So a feature with a valid value range from 3 to 18 with a step width of 5 did not allow to set values of 3, 8, 13 and 18 but only 5, 10 and 15. - Fixed an internal issue resulting in tons of 'EProperty: Property 'PixelsPerCycle' (mvHYPERIONfg-lib) does not support this value type(-2016(PROPHANDLING_INVALID_PROP_VALUE_TYPE))' log (mvTITANfg-lib) messages when dealing with CameraLink camera descriptions. (Bug introduced in version 1.11.1) - If working with medium or full CameraLink cameras then the mvHYPERION needs to (low level mvHYPERION driver, Linux) synchronize the input channels. This will be done before enabling a request. Under certain conditions Linux signalled a blocking function call inside the kernel module during this synchronization step. - mvLogFileViewer works with up-to-date browsers again. (all shipped packages) - Fixed clipping bug in ColorTwist filter for pixel formats RGB101010Packed, (all shipped packages) RGB121212Packed and RGB141414Packed. - Storing a setting in XML format without specifying a file extension did not add (mvPropHandling) '.xml' to the file name if a '.' was part of the path. - GenICam devices defining the 'DeviceRegistersStreamingStart' and/or (mvGenTLConsumer-lib) 'DeviceRegistersStreamingEnd' features as 'not writeable' did cause a crash when trying to load or store a setting. - On Windows multiple entries in the list of network adapters with the same MAC but (mvGenTLProducer.cti) different IPv4 addresses did result in incorrect interface information after the 2nd call to 'TLUpdateInterfaceList'. This could e.g. happen if a 'Microsoft Virtual WiFi Miniport Adapter' was present in the system. 13.10.2015 2.13.7 NEW FIRMWARE: - Firmware version 2.1.2.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Version Number increased. BUGS FIXED: - 'Quick Setup' wizard now remains visible when a greyscale camera is opened. (wxPropView) (Bug introduced in version 2.13.5) - 'BandwidthConsumed' did not state the actual bandwidth consumed on the wire, but the (mvBlueFOX-lib) amount of data after the image processing on the host. - Properties specifying the 'cfContainsBinaryData' flag did not always return the (mvGenTLConsumer-lib) correct value when calling the 'binaryDataBufferMaxSize' function when the property was not accessible when the device was initialised. - If the image chunk was switched off after images have been captured sometimes the old (mvGenTLConsumer-lib) image data was displayed instead of an empty buffer with just chunk data. 09.10.2015 2.13.6 NEW FIRMWARE: - Firmware version 2.0.9.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - Version numbering scheme changed due to purely administrative reasons. No major changes have been made. - Mono12p/BayerXX12p added for all cameras except mvBlueCOUGAR-X2xx. - mvBlueFOX3-2024aC/G, mvBlueFOX3-2024C/G: LED indicates different camera states now. See manual for details. Bugs Fixed: - Additional FrameEndEvents could occur at AcquisitionStart. - LUTs where not stored/restored properly by the UserSetLoad/Save commands if a device did support both luminance AND RGB LUTs. - CCDs: SW-Trigger could fail if send immediately after enabling trigger mode. NEW FEATURES: - Gamma filter in Windows and Linux systems has been optimized to run on multiple (all shipped packages) threads - In Linux systems, the ColorTwist Filter now uses the internal thread pool (all shipped packages for Unix/Linux systems) optimization, introduced in version 2.12.3 UPDATES: - Support for internal analysis tool improved. (mvGigECapture.sys, version 2.1.2.53) - Increased packet size auto negotiation algorithm speed thus reduced the (mvGenTLProducer.cti) initialisation time for GEV devices. - Firmware related files are no longer presented to the user using the file access (wxPropView) control wizard. BUGS FIXED: - Debayering to Mono formats in Linux systems, now correctly use the internal (all shipped packages for Unix/Linux systems) thread pool optimization, introduced in version 2.12.3 - Firmware update for mvBlueCOUGAR-S devices is working again. (mvGenTLConsumer-lib) (Bug introduced in version 2.12.3) - mvBlueFOX-x202bx: Column calibration was not always working properly resulting in (mvBlueFOX-lib) visible columns even when looking at homogeneous scenes. - mvHYPERION-CLb: The driver did crash if working with signal 'Trigger-In(J3.4/J3.5)'. (mvHYPERIONfg-lib) - mvHYPERION: Sometimes the DMR_ImageRequestReset function did not work properly. (mvHYPERIONfg-lib) Requests did return unexpected result values then. - When one or multiple requests where aborted for a U3V device the first requests (mvGenTLProducer.cti) result was returned as 'rrTimeout' instead of 'rrRequestAborted' on Windows. - When releasing the 'IAMVideoProcAmp' once for a device not closed afterwards did (DirectShow_acquire.ax) result in a crash when accessing stuff belonging to that interface afterwards. - Calling 'DSA_UnregisterAllDevices' or 'DllUnregisterServer' did no always delete all (DirectShow_acquire.ax) devices previously registered for DirectShow usage resulting in some applications displaying devices no longer present in the current system even if one of the unregister-functions have been called. - RAW file import in wxPropView now correctly fails if either the width or the height (wxPropView) is specified smaller than 1. 18.09.2015 2.13.5 NEW FEATURES: - Firmware version 1.6.483.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueCOUGAR-X(D) devices with IMX sensors support decimation in X and Y direction now. - mvBlueFOX3-2024C: Added support for YUV411_8_UYYVYY format. Bugs Fixed: - mvBlueFOX3: UserFile can be up- and downloaded correctly now. - AWB sometimes did not work correctly if binning or decimation was enabled. - The Properties 'Aoi/X' and 'Aoi/Y' also affect the file import mode now. Therefore (mvVirtualDevice-lib) now AOIs can be extracted from images loaded from disk. - The 'Quick Setup' wizard now provides color and greyscale pre-sets, tuned for quality (wxPropView) or speed. UPDATES: - The 'LostImagesCount' property counts gaps in the block ID continuity for U3V devices (mvGenTLProducer.cti) now. BUGS FIXED: - Fixed bug introduced in version 2.13.0 with mvBlueFOX(-M)12x CCD gain settings update. (mvBlueFOX-lib) - Windows/64bit: On a few System/OS combinations, application crash when opening (mvTITAN/mvGAMMA) the device. Fixed in matrixfg.sys, version 1.114. - When working with the socket implementation in setups where the first payload packet (mvGenTLProducer.cti) processed was the potential smaller one from the end of a block(e.g. in LAG mode where data tends to arrive out of order) blocks sometimes did contain corrupt data with no error being reported to the upper layers. - When opening a U3V device with event support an error message was written to the (mvGenTLProducer.cti) log output because of an incorrect initialisation order. 03.09.2015 2.13.4 UPDATES: - Detection of lost frames due to buffer under-runs improved. (mvGigECapture.sys, version 2.1.1.52) NEW FEATURES: - Firmware version 1.6.475.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Bugs Fixed: - mvBlueFOX3: AGC value can now reach up to 48dB for IMX sensors. - mvBlueCOUGAR-XD124a, XD126, XD129: maximum image height was incorrect after closing and opening the camera. - mvBlueCOUGAR-XD104d, X104f, mvBlueFOX3-2024, 2024a: - in very rare cases switching the image format led to corrupt images. - when using LUT the output image no longer has a "solarize" effect. - pending ACKs are now being sent when writing to 'mvUserData', 'DeviceUserName', 'UserSetDefaultSelector' IP-configuration registers etc. - The 'Quick Setup' wizard can now be forcefully shown/hidden by using the 'qsw' (wxPropView) cmd-line parameter in wxPropView. This feature overrides the default settings for the current session but it does not overwrite them. BUGS FIXED: - The 'TapSort' filter for 2X-2YE data did not re-order the data correctly when (mvTITANfg-lib) 'ImageProcessingOptimization' was set to 'ipoMinimizeMemoryUsage'. (mvHYPERIONfg-lib) (mvVirtualDevice-lib) - Calling 'imageRequestReset' from a thread running in parallel to a thread calling (mvGenTLProducer.cti) 'imageRequestSingle' could result in a deadlock on Windows for U3V devices. - mvDeviceConfigure did not backup and restore settings correctly if a device e.g. had (mvDeviceConfigure) a valid UserSet2 and UserSet4, but no UsetSet1 and/or UserSet3. - The 'Quick Setup' wizard now correctly disables features if they are not available on (wxPropView) the running platform. 13.08.2015 2.13.3 NEW FEATURES: - Firmware version 1.6.461.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueCOUGAR-XD124aG/C: Internal pre-gain reduced by 5dB. This will result in slightly darker but less noisier images after a firmware update. - New default: BalanceWhiteAuto = Off. - All sensors now have default white balance values corresponding to a light temperature of 5000K. - mvBlueCOUGAR-X/XD: The 'UserFile', selectable in File Access Control, is be preserved during firmware updates. - AcquisitionFrameRate property does not change its value any more, only by user input. New maximum values provided for this property. The maximum frame rate that can be reached with the current settings may be read from the mvResultingFrameRate property. - mvBlueCOUGAR-X(D): Device boot time reduced by 500 ms. New Features: - Full mvBlueSIRIUS support added. - mvBlueFOX3: RGB/YUV modes enabled for devices with IMX249 sensors. - Improved SequencerControl: 'CounterDuration' became a valid value for 'SequencerFeatureSelector', 'SequencerTriggerSource' and 'SequencerTriggerActivation' added. Bugs Fixed: - mvBlueCOUGAR-X104fG/C: Some devices did not start correctly. - mvBlueCOUGAR-X(D): With certain SCPS payload size and AOI combinations in chunk mode the device did crash. - mvBlueFOX3: The data written to 'mvUserData' was not stored in non-volatile memory. - mvBlueFOX3: Calling 'FileOperationExecute' with 'FileOperationSelector' set to 'Close' twice did result in a crash. - mvBlueFOX3: Corrected device link speed to 5Gbps for USB super speed. - IMX: Sometimes starting/stopping the acquisition took too long. - IMX: Corrupt images when over-triggering and ExposureMode = TriggerWidth is used. - mvBlueCOUGAR-XD124a, XD126, XD129: OffsetY was not set when the image height was set to the sensor maximum, leading to black stripes in the image - mvBlueCOUGAR-X/XD: An upload of a 'UserFile' that exceeds the flash section size could crash the camera. - mvBlueCOUGAR-X/XD: When a 'DeviceReset' was executed after a firmware update the device could fail to reboot properly in very rare cases. The status LED would show blueish white color then. Power-cycling the device did fix this. UPDATES: - U3V devices that specify the non-HEX version of the serial number in the U3V device (mvGenTLProducer.cti) info serial string descriptor could not be initialised. BUGS FIXED: - When a faulty U3V device did not answer when reading the max. device response time (mvGenTLProducer.cti) the whole driver did lock up. - When a request timeout for a U3V device did elapse the request result was returned (mvGenTLProducer.cti) as 'rrRequestAborted' instead of 'rrTimeout' on Linux. - On Windows the link speed value of LAG groups has not always been reported (mvGenTLProducer.cti) correctly as added in version 2.5.17. This could result in incorrect resend behaviour and/or frames being reported as incomplete even though no data was lost on the link. (Bug introduced in version 2.6.0) 29.07.2015 2.13.2 UPDATES: - mvIMPACT Acquire applications can be compiled with C++ 11 support now. (all shipped packages for Unix/Linux systems) CHANGED BEHAVIOUR: - The 'Quick Setup' wizard display window no longer hides the status bar of wxPropView. (wxPropView) NEW FEATURES: - New sample added to all packages: 'GenICamSequencerUsage'. (all shipped packages) - ImageProcessing now has a rotation filter. Relevant properties 'RotationEnable' (mvIMPACT_acquire.h) and 'RotationAngle' published. - New C# example application added to all packages: 'SingleCaptureStorage'. (all MSI-based shipped packages) - New VB.NET example application added to all packages: 'SingleCapture', (all MSI-based shipped packages) 'SingleCaptureStorage'. - New color correction matrix added: 'cticmmBlueFOX3_x140C_WPPLS'. It will be used by (all shipped packages) mvBlueFOX3-1140C devices. BUGS FIXED: - Calling 'EventKill' for events of type 'EVENT_REMOTE_DEVICE' or 'EVENT_NEW_BUFFER' (mvGenTLProducer.cti) did not result in 'EventGetData' to return 'GC_ERR_ABORT' but 'GC_ERR_NO_DATA'. - Payload type 'ExtendedChunk' for GEV devices was not handled correctly. The (mvGenTLProducer.cti) 'image present' bit was ignored, thus the 'BUFFER_INFO_IMAGEPRESENT' query did return 0 even if an image was present in the payload. - Unplugging a U3V device with event support on Linux no longer floods the log (mvGenTLProducer.cti) output. - The 'TapSort' filter for RGB 24-bit with 2 pixels per cycle did not re-order the (mvHYPERIONfg-lib) data correctly when 'ImageProcessingOptimization' was set to (mvTITANfg-lib) 'ipoMinimizeMemoryUsage'. (mvVirtualDevice-lib) - mvBlueCOUGAR-XD1212aC devices now correctly use the 'cticmmBlueCOUGAR_XDx212C_WPPLS' (all shipped packages) color correction matrix by default. - U3V events have been reported in a different order than delivered by the device under (mvGenTLProducer.cti) Windows. 22.06.2015 2.13.1 NEW FEATURES: - Firmware version 1.6.414.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueCOUGAR-XD126AG/C,mvBlueCOUGAR-XD129G/C: Improved image quality for higher device clock frequencies. New Features: - mvBlueFOX3: Event support added. - mvBlueFOX3-1012bC/1012dC/1013C/1020C/1020aC/1031C support YUV-Formats now. - 'Streamable' attributes added to features suitable for streaming in the GenICam XML files. Bugs Fixed: - mvBlueCOUGAR-X225G/C: Corrupt images. (Bug introduced in 1.6.403.0) - mvBlueFOX3: Switching 'mvDevicePowerMode' from 'mvActive' to 'mvStandby' and then back to 'mvActive' did result in the chunk mode no longer working. (Bug introduced in 1.6.403.0) - mvBlueFOX3-2024aC/G: Only 32 instead of 41 Hz could be reached with 'mvDigitizationBitDepth' set to 'Auto'. - New sample added to all packages: 'ContinuousCaptureGenICam_C'. (all shipped packages) BUGS FIXED: - Calling 'attachUserBuffer' for a request that had a user buffer with a different (all shipped packages) size attached to it before could fail. - The VB.NET example 'ContinuousCapture.VB.exe' also uses the 'getDeviceFromUserInput' (all shipped MSI-based packages) function from 'mv.impact.acquire.example.helper.dll' now thus also automatically selects the 'dilGenICam' interface layout if available. - mvBlueFOX3 cameras with event support on Linux systems may cause a segmentation fault (mvGenTLConsumer-lib) when closing the device. (Bug introduced in version 2.12.4) 11.06.2015 2.13.0 UPDATES: - All example applications will now use the interface layout 'dilGenICam' and the (all shipped packages) acquisition start/stop mode 'assbUser' if supported by the selected device. NEW FEATURES: - Added support for pixel format YUV411_UYYVYY_Packed. (all shipped packages) BUGS FIXED: - mvBlueFOX-M certain CCD sensor types did not power up correctly in rare cases. (mvBlueFOX-lib) - Potential deadlock when reading or writing properties from or to a GenICam compliant (mvGenTLConsumer-lib) device defining at least on feature with a polling time. 26.05.2015 2.12.5 UPDATES: - Firmware version 1.6.403.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3: SequencerControl added. Bugs Fixed: - mvBlueCOUGAR-X104fG/C: Sometimes no images could be captured after PowerOn. - mvBlueCOUGAR-XD: Gain for DigitalTaps was ten times higher than the value in the corresponding register. BUGS FIXED: - mvBlueFOX-MLC202b devices operated in triggered mode did result in incorrectly (mvBlueFOX-lib) exposed images for certain exposure times. - If 2 processes during start-up where configured for log-output into a file both (all shipped packages) processes could lock up. This problem affects ALL mvIMPACT Acquire packages, thus when running more than one driver package on a system ALL package should be updated! (Bug introduced in version 1.12.70) - Capturing images with more than 64 MByte memory consumption could lead to problems. (low level mvHYPERION driver, Windows) (Bug introduced in version 2.11.4) 13.05.2015 2.12.4 UPDATES: - Firmware version 1.6.393.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueFOX3: Changed the status in case of a buffer too small from 'U3V_STATUS_DATA_DISCARDED' to 'U3V_STATUS_DATA_OVERRUN' as required by the U3V specification version 1.0.1. New Features: - 'ChunkSequencerSetActive' for all devices supporting the sequencer control category. - Support for new product added: mvBlueFOX3-2024aG/C. Bugs Fixed: - mvBlueCOUGAR-X125: FFC Calibration bug fixed. - Missing invalidation of 'LineStatus' and 'LineStatusAll' when writing to 'LineInverter' or 'LineMode'. NEW FEATURES: - 'IAMCameraControl' feature 'CameraControl_Exposure' as well as the 'AMVideoProcAmp' (DirectShow_acquire.ax) features 'VideoProcAmp_Brightness' and 'VideoProcAmp_Gain' correctly handle the 'Auto' option as well as the runtime availability of these features. BUGS FIXED: - Calling 'IAMCameraControl::Get' with 'CameraControl_Exposure' did return a value (DirectShow_acquire.ax) that was differed from the actual value by 1. - Calling 'IAMCameraControl::GetRange' with 'CameraControl_Exposure' did return an (DirectShow_acquire.ax) invalid value for 'pSteppingDelta'. - Devices specifying a category with a deprecated name as well as a category with the (mvGenTLConsumer-lib) name the deprecated one has been replaced within their GenICam file could not be initialised. 08.05.2015 2.12.3 UPDATES: - Detection of lost frames due to buffer under-runs improved. (mvGigECapture.sys, version 2.1.0.51) (mvGenTLProducer.cti) - Status bar displays more statistics now. (wxPropView) - The GenICam nodemaps of the 'System Module' and the 'Interface Module' more closely (mvGenTLProducer.cti) comply with the GenICam GenTL SFNC 1.0 now. CHANGED BEHAVIOUR: - The mvGenTLProducer is now fully compliant with the GenICam GenTL validation (mvGenTLProducer.cti) framework. This however required some changes that might affect applications relying on some MATRIX VISION specific GenTL producer behaviour: - After calling 'GCUnregisterEvent' for a given event or after closing the module associated with an event the event handle will become invalid now. - DevicePort related function calls will now fail after closing the associated device. - Calling 'DSGetBufferID' with an invalid index will now fail. - Calling 'DSStartAcquisition' with 'iNumToAcquire' set to 0 will now fail. - Read from or writing to the device port of a device that has been closed will now fail. - Calling 'DSAnnounceBuffer' while an acquisition is running will now fail. - On Windows 8 and greater less shortcuts will be created in the start menu now as (all shipped MSI-based packages) since Windows 8 nested folders in the start menus are no longer allowed. NEW FEATURES: - On Linux an internal thread pool is now used to speed up de-bayer processing time. (all shipped packages for Unix/Linux systems) This will increase the number of threads created by the number of processors per initialised device in a process. - New properties published: mvIMPACT::acquire::Request::chunkSequencerSetActive, (mvIMPACT_acquire.h) mvIMPACT::acquire::GenICam::DataStreamModule::mvResendMode, mvIMPACT::acquire::Statistics::bandwidthConsumed (C++), mv.impact.acquire.Request.chunkSequencerSetActive, (mv.impact.acquire.dll) mv.impact.acquire.GenICam.DataStreamModule.mvResendMode, mv.impact.acquire.Statistics.bandwidthConsumed (NET) - GenCP 1.1 multi-event support added. If supported by the device this will be enabled (mvGenTLProducer.cti) by the GenTL producer now. - U3V event support for Linux added. (mvGenTLProducer.cti) BUGS FIXED: - 'Quick Setup' wizard: Pressing 'Cancel'/'Factory Reset' will now correctly revert/set (wxPropView) all relevant ColorTwist properties respectively. - The original payload type from the underlying transport layer was reported instead of (mvGenTLProducer.cti) the GenTL payload type for the 'BUFFER_INFO_PAYLOADTYPE' query. This could result in problem when processing chunk data with 3rd party software. - Accessing a data stream buffer through the GenICam node map now works properly. (mvGenTLProducer.cti) - Constantly opening and closing U3V devices with event support did result in failures (mvGenTLProducer.cti) during open calls after some time. - Calling mv.impact.acquire.FunctionInterface.imageRequestUnlock directly after (mv.impact.acquire.dll) increasing the request count for a newly created request index did crash. - When a device did stream image data in chunk mode the paddingX field from the leader (mvGenTLConsumer-lib) of the transport layer specific data was not used to correctly set the line pitch of the request buffer. - When a device did stream image data in chunk mode the pixel format property from the (mvGenTLConsumer-lib) leader of the transport layer specific data was not used to correctly set the pixel format of the request buffer. This could cause problems when the pixel format did change from buffer to buffer (e.g. when using the SequencerControl). - When a device implemented the 'TLParamsLocked' feature as an actual device register (mvGenTLConsumer-lib) and this register stayed set for whatever reasons when an application did terminate opening the device again did not reset this parameter causing problems when trying to configure the device. - Updating chunk data in a request buffer could fail, if the chunk features did include (mvGenTLConsumer-lib) selectors, that are there but are not available at the given moment. - When switching chunk mode off requests no longer display 'old' chunk data when (mvGenTLConsumer-lib) streaming in image mode. - mvHYPERION-SDI: Sometimes the first images captured were distorted. This could mainly (mvHYPERIONfg-lib) be seen with 3G camera signals. (low level mvHYPERION driver, Linux and Windows) 26.03.2015 2.12.2 UPDATES: - Firmware version 1.6.360.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueCOUGAR-X(D)104(b)G/C, mvBlueCOUGAR-XD204(b)G/C: Exact frame rate. - mvBlueCOUGAR-X, mvBlueFOX3 with EV76Cxxx sensors: Correct YOffset in line-scan mode. There was an offset of 5 lines compared to areas scan. New Features: - mvBlueFOX3: Chunk support added. - mvBlueCOUGAR-X(D): Action command support added. - mvBlueCOUGAR-X(D)104d/fG/C: Sequencer mode available. - mvBlueCOUGAR-X(D)104d/fG/C: LUT-bit-depth increased: 12bit to 9bit. - mvBlueFOX3: Device link throughput limitation mode added. - mvBlueCOUGAR-XD126G/C: New clock frequency: 60 MHz Bugs Fixed: - mvBlueCOUGAR-X(D): Link speed change detection can fail sporadically when booting some systems. - mvBlueCOUGAR-X12x,mvBlueCOUGAR-XD12x: FrameBurstStart did not work correctly in conjunction with SequencerMode. SequencerMode did not work correctly with very short exposure time in first SequencerSet. - Support for newer kernel versions added to mvHYPERION modules. (low level mvHYPERION driver, Linux) CHANGED BEHAVIOUR: - mvGenTLProducer now dynamically adjusts the receive buffer memory, starting with (mvGenTLProducer.cti) 12MiB and increasing it, if possible, up to 32MiB in 4MiB increments. - Improved GenTL validation framework compliance. This did change the behaviour of some of the functions exported by the mvGenTLProducer-lib: - All 'GetInfo' function can no longer be called with an invalid 'INFO_DATATYPE' pointer. - Calling 'IFClose' causes all devices associated with this interface to be closed as well. - The deprecated 'StreamAcquisitionModeSelector' feature of the data stream module has been replaced by the official 'StreamBufferHandlingMode'. - The data type reported for 'BUFFER_INFO_PIXEL_ENDIANNESS' has been changed from 'INFO_DATATYPE_UINT32' to 'INFO_DATATYPE_INT32'. NEW FEATURES: - The property mvIMPACT::acquire::SystemSettings::imageProcessingOptimization (C/C++) (mvIMPACT_acquire.h) or mv.impact.acquire.SystemSettings.imageProcessingOptimization (.NET) can now be (mv.impact.acquire.dll) used to influence the behaviour of the internal image processing algorithms. BUGS FIXED: - On Linux when the same interface(same MAC address) was present more than once in (mvGenTLProducer.cti) the ifconfig table some internal list have not been updated correctly and therefore devices connected to this interface could not be accessed. This could e.g. happen when an avahi daemon was running on an interface already configured with e.g. dhcp or static ip. - The 'auto assign temp IP' option did only work if both the IP as well as the (mvIPConfigure) netmask where invalid. - Crashes in the destructor of the classes (mvIMPACT_acquire_GenICam.h) mvIMPACT::acquire::GenICam::ODevFileStream or mvIMPACT::acquire::GenICam::IDevFileStream when an attempt to open a file did fail. - 'CaptureToUserMemory_C' did fail when requesting a single frame for devices with (CaptureToUserMemory.c) AcquisitionStartStopBehaviour' set to 'assbUser'. - Potential crashes in the channel split filter when working with 'ibpfMono12Packed_V1' (all shipped packages) or 'ibpfMono12Packed_V2' formats. 13.02.2015 2.12.1 NEW FEATURES: - mvIPConfigure can now auto-assign a valid and unused temporary IP Address to a device (mvIPConfigure) which is not configured properly. The user no longer has to enter it manually. - The 'GenICam' namespace now contains the full SFNC 2.2 feature set. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) - MATRIX VISION Linux installation scripts now support an unattended installation mode. (all shipped packages for Unix/Linux systems) - Linux installation script for mvVirtualDevices is available now. (all shipped packages for Unix/Linux systems) BUGS FIXED: - Unplugging and the re-inserting mvBlueFOX USB2 devices to a USB3 host controller (mvBlueFOX-lib) on Windows 7 did not work properly. Afterwards no image capture was possible. - Certain exposure times on mvBlueFOX-x00w did result in incorrectly exposed images. (mvBlueFOX-lib) - Division by 0 exceptions when trying to initialise various flavors of the mvBlueFOX2 (DirectShow_acquire.ax) under DirectShow. (Bug introduced in version 2.11.9) - When unicasting GEV Action commands only the first action command could be sent while (mvGenTLProducer.cti) every additional command did report an error. - The function mv.impact.acquire.helper.RequestProvider.acquisitionStart did fail when (mv.impact.acquire.dll) called a second time even if mv.impact.acquire.helper.RequestProvider.acquisitionStop has been called before. 30.01.2015 2.12.0 UPDATES: - Firmware version 1.6.306.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueFOX3-1031G/C: Minimum exposure has been set to 30 usec. Bugs Fixed: - mvBlueFOX3-2024xx: Single request acquisition mode failed when using pixel formats other than Mono8 or BayerRG8. - mvBlueCOUGAR-X100wG/C: Frame rate for trigger burst modes corrected. - mvBlueCOUGAR-XD104dG/C, mvBlueCOUGAR-X104fG/C: Changing the pixel format could result in corrupt images. CHANGED BEHAVIOUR: - For Windows 8 and greater the 'FullScreen' option in wxPropView is no longer (wxPropView) available as this feature is no longer supported by the operating system. - All devices offering the 'dilGenICam' interface layout will now be initialised in (DirectShow_acquire.ax) 'dilGenICam' interface layout instead of 'dilDeviceSpecific'. - ImageRequestWaitFor() should no longer cause considerable CPU load on weaker Linux (mvBlueFOX-lib) systems such as ARM boards. - The increment of the 'ImageWidth' and 'ImageHeight' properties of the scaler (all shipped packages) belonging to the 'ImageDestination' class have been reduced from 4 to 1 allowing finer scaling. - All GenICam SFNC features with the 'Abs' postfix in the feature name have been (mvIMPACT_acquire_GenICam.h) removed from the public interface. If a device supports the 'Abs' feature only, the (mv.impact.acquire.dll) interface will automatically bind to this feature when using the object without the 'Abs'. NEW FEATURES: - New color correction matrices added: 'cticmmBlueCOUGAR_Xx04fC_WPPLS' and (all shipped packages) 'cticmmBlueFOX3_x024aC_WPPLS'. These will be used by 'mvBlueCOUGAR-x04fC' and 'mvBlueFOX3_x024aC' devices respectively. - mvDeviceConfigure now performs checks and displays the current and future firmware (mvDeviceConfigure) versions before updating a device. - Support for GEV Action commands added to the (mvGenTLProducer.cti) mvIMPACT::acquire::GenICam::InterfaceModule (C++) and (mvIMPACT_acquire_GenICam.h) mv.impact.acquire.GenICam.InterfaceModule (.NET) classes added. (mv.impact.acquire.dll) - A lot of new events integrated into the GenICam.EventControl wrapper class. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) BUGS FIXED: - IP performance issue check on Linux U3V interfaces no longer takes place. As a (mvIPConfigure) result, erroneous messages on the log window of mvIPConfigure no longer appear. - Potential crash when processing hot-plug messages under 64-bit Windows systems. (mvBlueFOX-lib) - Crashes when an application tried to open a device that was registered for DirectShow (DirectShow_acquire.ax) access but was not present in the current system. (Bug introduced in version 2.11.9) - JPEG, TIFF and PNG import added based on the 'FreeImage' library works for the (mvVirtualDevice-lib) mvBlueLYNX-X as well now. - Random crash in wxPropView when switching back and forth between 2 or more devices (wxPropView) running in live mode. - Access to WO-GenApi features was not possible. (mvGenTLConsumer-lib) 15.01.2015 2.11.9 UPDATES: - Firmware version 1.6.295.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueFOX3: AGC/AWB/AEC calculation is faster now. New Features: - Support for new products added: mvBlueCOUGAR-X104fG/C, mvBlueFOX3-2024G/C - mvBlueCOUGAR-X1010G/C, mvBlueCOUGAR-X104G/C, mvBlueCOUGAR-X104bG/C, mvBlueCOUGAR-XD104G/C, mvBlueCOUGAR-XD104bG/C, mvBlueCOUGAR-X1010G/C, mvBlueCOUGAR-X104fG/C, mvBlueCOUGAR-X104dG/C, mvBlueCOUGAR-X100wG/C, mvBlueFOX3-1100G/C, mvBlueFOX3-1140C: FrameBurstStart trigger without jitter. - mvBlueCOUGAR-XD104dG/C, mvBlueFOX3-2024G/C: ExposureMode = TriggerWidth Bugs Fixed: - mvBlueCOUGAR: Setting DiscoveryACKDelay to zero is possible now. - mvBlueFOX3: The device temperature was not shown correctly. NEW FEATURES: - Initial version of the 'Quick Setup' wizard for mvBlueFOX devices added. (wxPropView) - On Windows wxPropView has now three new help menu options which (wxPropView) - directly open the logs folder - create a zip file with all the logs - open the systems default email client to send an email to support.de@balluff.de. - New color correction matrix added: 'cticmmBlueCOUGAR_Xx010C_WPPLS' This will be used (all shipped packages) by 'mvBlueCOUGAR-x010C' devices. - The DirectShow interface supports the 'IAMVideoProcAmp' and the 'IAMCameraControl' (DirectShow_acquire.ax) interface now. This will e.g. allow to adjust the exposure time and the gain under MATLAB. - JPEG, TIFF and PNG import added based on the 'FreeImage' library. (mvVirtualDevice-lib) - New property published in C++ and .NET interface: (mvVirtualDevice-lib) CameraSettingsVirtualDevice::aoiMode. (mvIMPACT_acquire.h) (mv.impact.acquire.dll) BUGS FIXED: - Logging also works with the new log section format introduced in version 2.5.0. (DirectShow_acquire.ax) 18.12.2014 2.11.8 UPDATES: - Just minor internal changes. Nothing new, nothing fixed. 17.12.2014 2.11.7 NEW FEATURES: - The 'ipv4_mask' parameter now accepts a ';' separated list of masks (mvDeviceConfigure) (e.g. ipv4_mask=169.254.*;192.168.100*). BUGS FIXED: - Restoring values created and set in the 'Custom Properties' dialog of Vision Pro from (mvIMPACTAcquire_Cognex_Adapter-lib) a *.vpp file is working now. - Potential crash when working with mvBlueFOX devices on Linux. (mvBlueFOX-lib) (Bug introduced in version 2.11.6) - Under some conditions it could comes to random crashes of the system. (Linux only) (Linux, low level mvHYPERION driver) 02.12.2014 2.11.6 UPDATES: - Firmware version 1.6.259.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - mvBlueFOX3-1020(a)G/C/GE, mvBlueCOUGAR-X102eG/C/GE, mvBlueCOUGAR-X104eG/C/GE has reduced analog gain step size. New Features: - AGC/AWB/AEC for mvBlueFOX3. - MT9P031/MT9M021/MT9M024/E2V-sensors: FrameBurstStart with no jitter. Bugs Fixed: - mvBlueFOX3: - Under some conditions there was a delay in the communication to the mvBlueFOX3 devices. This occurred only on Linux systems with particular host controllers. - Changes in the BOS descriptor from USB2.1 Specification introduced. - mvBlueFOX3-1013G/C, mvBlueFOX3-1020G/C: Wrong exposure times could occur while changing properties. - mvBlueCOUGAR-X105G/C: Wrong exposure times when using ShutterMode = GlobalReset. - If TriggerMode=On was the very first write command it did not work. BUGS FIXED: - mv.impact.acquire.display.ImageDisplay.SetImage( Request pRequest) did mix up 'R' and (mv.impact.acquire.display.extensions.dll) 'B' in 'ibpfRGBx888Planar' mode. - Potential deadlock when closing a device while an unplug message is processed (mvBlueFOX-lib) internally. (Linux only) - Random crash when a device was unplugged while streaming data. (Linux only) (mvBlueFOX-lib) - Under some conditions the imageRequests were returned with an false error code. (Linux, low level mvHYPERION driver) 24.11.2014 2.11.5 UPDATES: - Internal migration to libusb 1.0.19. (mvGenTL_Acquire-*.tgz ) NEW FEATURES: - ARM softfloat and ARM hardfloat support added for mvGenTL_Acquire and mvBlueFOX. (mvBlueFOX-ARMsf_gnueabi-*.tgz) This will add support for various ARM platforms running at least ubuntu 12.04 or (mvBlueFOX-ARMhf_gnueabi-*.tgz) a compatible system. (mvGenTL_Acquire-ARMsf_gnueabi-*.tgz ) (mvGenTL_Acquire-ARMhf_gnueabi-*.tgz ) - New color correction matrix added: 'cticmmBlueFOX3_x024C_WPPLS' This will be used by (all shipped packages) 'mvBlueFOX3-x024C' devices. BUGS FIXED: - Linux installer scripts no longer complain about missing Platform.h file. (mvGenTL_Acquire-x86_*.tgz) (Bug introduced in version 2.11.3) (mvBlueFOX-x86_*.tgz) 19.11.2014 2.11.4 CHANGED BEHAVIOUR: - NeuroCheck 6.x interfaces do no longer support devices NOT manufactured by MATRIX (mv.impact.acquire.NeuroCheck6.dll) VISION. (mv.impact.acquire.NeuroCheck6_1.dll) - Footer and actual image buffer use 2 separate blocks of memory now. Because of this (mvHYPERIONfg-lib) (low level mvHYPERION driver, Linux) it is now possible to allocate or provide a contiguous block of memory that provides (low level mvHYPERION driver) space for multiple images to implement a ring buffer pool without any gaps between the individual images. This needs a kernel driver update as well. NEW FEATURES: - NeuroCheck 6.1 interface for mvBlueCOUGAR and mvBlueFOX devices added to all MSI (all shipped MSI-based packages) based packages. BUGS FIXED: - When the current device got disconnected the 'Quick Setup' wizard is no longer (wxPropView) periodically generating error messages. - When for whatever reasons the on-board processor of a mvHYPERION device could not (mvHYPERIONfg-lib) be booted the driver instance did crash. 11.11.2014 2.11.3 NEW FEATURES: - Initial version of the 'Quick Setup' wizard added. (wxPropView) - New command line parameter added: 'custom_genicam_file'. (mvDeviceConfigure) - 'FirmwareUpgrade' on Linux can now be used to update the firmware of mvHYPERION (all shipped packages for Unix/Linux systems) devices from a console window as well. This might be useful on systems without a graphical user interface. - New property published in C++ and .NET interface: Device::manufacturer. (mvIMPACT_acquire.h) (mv.impact.acquire.dll) BUGS FIXED: - A couple of small memory leaks whenever a connection to a GenICam device was (mvGenTLConsumer-lib) lost an then re-established automatically by the driver when the device was (mvGenTLProducer.cti) discovered again or when a GEV or U3V interface did disappear at runtime. - When deleting a 'ComponentCallback' object without previously unregistering all (all shipped packages) objects bound to this callback an application could crash when the callback condition became fulfilled afterwards. - The GenICam XML files returned by the various modules of the producer contained an (mvGenTLProducer.cti) additional '\0' character at the end and the consumer did rely on this when storing (mvGenTLConsumer-lib) the file. - Potential crash when a GenICam device was disconnected shortly before reading the (mvGenTLConsumer-lib) 'PayloadSize' property. - Potential deadlock when writing to a GenICam property of the device shortly after a (GenApi runtime) device was disconnected or the connection to the device was lost for some other reason. This did only happen for GenICam devices that support an event channel. - When for some reason a device driver did forward a frame that did carry a width or (all shipped packages) height of 0 into one of the image processing functions (e.g. the LUT filter) the driver instance could crash. - Crash when calling 'DMR_ReleaseImageBuffer' for a buffer that was obtained from a (mvDeviceManager-lib) call to 'DMR_CopyImageBuffer' with a source buffer where 'vpData' was != 0 but 'iSize' was 0. - Payload type 'Image_ExtendedChunk' for GEV devices was not handled correctly. (mvGenTLProducer.cti) - Payload type 'Chunk' was not handled correctly when the buffer did not carry the (mvGenTLConsumer-lib) 'ChunkWidth' and 'ChunkHeight' feature. 23.10.2014 2.11.2 UPDATES: - Firmware version 1.6.230.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3-2024G/C: New mvBlueFOX3 hardware added with support for IMX174 sensor. Bugs Fixed: - mvBlueCOUGAR-X100wG/C: Corrupt image in HDR-mode. - mvBlueFOX3-1020G/C: Some sensors were showing stripes in saturated areas. CHANGED BEHAVIOUR: - When 'AcquisitionStartStopBehaviour' is set to 'assbUser' and 'AcquisitionMode' is (mvGenTLConsumer-lib) set to 'SingleFrame' calling 'acquisitionStop' will also send a stop command to the device now in order to properly terminate outstanding frame requests there. - Loading a setting in 'GenICam' or 'Generic' interface layout will only work if the (mvGenTLConsumer-lib) setting has been created with the same interface layout AND at least the same product. Thus e.g. loading a setting created with a mvBlueCOUGAR-X122G will only work for other mvBlueCOUGAR-X122G devices. - For U3V devices the driver will access the 'MaxDeviceResponseTime' register first (mvGenTLProducer.cti) now. NEW FEATURES: - Lens control wizard added to allow convenient configuration of a lens controllable by (wxPropView) a GenICam device. This wizard will be available if the device supports the 'mvLensControl' category. BUGS FIXED: - Update issue with some HDR parameter combinations for mvBlueFOX-x00w devices. (mvBlueFOX-lib) - 'imageRequestReset' calls are handled correctly now. (mvVirtualDevice-lib) - Color correction matrices for 'cticmmBlueCOUGAR_Xx20aC_WPPLS', (all shipped packages) 'cticmmBlueFOX_x20aC_WPPLS', 'cticmmBlueCOUGAR_Xx05C_WPPLS' and 'cticmmBlueFOX_x05C_WPPLS' did use incorrect values. 09.10.2014 2.11.1 UPDATES: - Firmware version 1.6.223.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - New camera mvBlueCOUGAR-XD104dG/C supported. Changed Behaviour: - mvBlueCOUGAR-XD: Link process with only one link now completes faster. Bugs Fixed: - mvBlueCOUGAR-X105G/C: mvShutterMode was not available. (Bug introduced in Firmware version 1.6.129.0) - Cameras with CMOSIS sensors: Changing ExposureTime did not work correctly. - mvBlueCOUGAR-XD12xG/C: Wrong exposure time when using slow framerates (<2 fps). - mvBlueCOUGAR-XD126C: Max Height could be set to wrong values if switching the SensorTap property. - Changing ExposureMode to TriggerWidth did not work correctly. - mvBlueFOX3: In some cases e.g. after changing the exposure time BF3 sent corrupted frames. - FrameStart signal wasn't correct. - Support for third party GenICam devices that change the 'IsImplemented' feature of (mvGenTLConsumer-lib) their features at runtime improved. These features will now be available, but when (mvPropHandling-lib) marked as 'not implemented' will have neither read nor write access. CHANGED BEHAVIOUR: - When the 'TestMode' property is set to 'ImageDirectory the following changes have (mvVirtualDevice-lib) been applied: - The 'FrameId' property of a returned request object will contain the index of the image file within the directory - The 'UserData' property of a returned request object will contain the name of the file that was loaded (or an error message) at index 0 and the 'True' if this file is the last image file in this directory or 'False' otherwise at index 1. BUGS FIXED: - Certain internal error codes could end up in the application layer (e.g. GenTL (mvGenTLConsumer-lib) specific ones) but as these are not part of the SDK the application could not properly handle them. - For GEV 2.x devices the driver now correctly switches on the '64bitBlockIdEnable' bit (mvGenTLProducer.cti) - For GEV the 'Image_ExtendedChunk' format is decoded correctly now. (mvGenTLProducer.cti) - For GEV 2.x devices the test packet validation was not always working correctly. (mvGenTLProducer.cti) - Devices specifying a category with a deprecated name as well as a category with the (mvGenTLConsumer-lib) name the deprecated one has been replaced with in their GenICam file could not be initialised. - Devices specifying sub-lists within their chunk info features caused the driver to (mvGenTLConsumer-lib) crash at runtime when streaming in chunk mode. 15.09.2014 2.11.0 CHANGED BEHAVIOUR: - Tooltips in the wxPropView Property tree now have a delay of 2 seconds. (wxPropView) - Format for storing settings to XML files changed. This change comes with some (all shipped packages) compatibility issues. XML files created from now on might not be usable with mvIMPACT Acquire versions smaller than 2.11.0! XML files created with older versions will still be readable. See documentation for details. BUGS FIXED: - mvDeviceConfigure compile errors in Linux systems. (mvDeviceConfigure) (bug introduced in version 2.10.1) - When working with more than one U3V device on Windows processing the very first (mvGenTLProducer.cti) device removal event within the current process did not work correctly. This could e.g. result in a devices 'State' property not going to 'Absent' when calling 'DeviceReset' for the very first time. 26.08.2014 2.10.1 UPDATES - Firmware version 1.6.192.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) New Features: - mvBlueFOX3: mvDevicePowermode function added. Changed Behaviour: - mvBlueCOUGAR-XD: Link process with one link now faster Bugs Fixed: - LineScan-trigger mode. First image with wrong blockID did lead to a stop of streaming after first the image. - mvBlueCOUGAR-X104G/X104aG/X104bG/X125aG: Wrong init values for LUT did result in 'mv::EValTooLarge' error upon reading. - Gain(DigitalAll) value was set with factor 10 too high. (Bug introduced in 1.6.173.0) CHANGED BEHAVIOUR: - Firmware files for discontinued products (mvBlueCOUGAR-P, mvBlueCOUGAR-S and (all shipped packages for GenICam compliant devices) mvBlueLYNX-M7) will no longer be shipped as part of the installation package. The latest firmware versions are still available on the MATRIX VISION website. - Merge modules (*.msm-files) to build custom MSI based installation packages are (all shipped MSI based packages) no longer part of the actual MSI package for a particular driver but can be downloaded as a separate archive from the MATRIX VISION website. This was done to reduce the size of a standard installation. As a result 64-bit packages now roughly use 55% of their original size, 32-bit packages about 50%. NEW FEATURES: - mvDeviceConfigure can write a log file from the content of the log window now. (mvDeviceConfigure) - Filter 'FormatReinterpreter' added. (all shipped packages) - New properties published in C++ and .NET interface: (mvIMPACT_acquire.h) formatReinterpreterEnable, formatReinterpreterMode (mv.impact.acquire.dll) BUGS FIXED: - Firmware update for mvBlueFOX and mvHYPERION devices is working again. (mvDeviceConfigure) (Bug introduced in version 2.9.1) - The default parameter for 'scope' when calling 'DMR_SaveSettingToDefault' or (mvDeviceManager-lib) 'DMR_SaveSystemToDefault' was 'sGlobal' but must be 'sUser'. This did also result in an error being reported in wxPropView when selecting 'Action -> Capture Settings -> Save Active Device Settings -> ... (Per User Only)'. (Bug introduced in version 2.5.9) - XML Files stored in the folder 'CameraFiles' but not containing camera description (all shipped frame grabber packages) data but e.g. a device setting the name of the file did end up as a selectable camera description but obviously did not behave correctly. 21.07.2014 2.10.0 UPDATES - Firmware version 1.6.165.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Bugs Fixed: - CCDs: Changing the exposure time did not always work correctly. - Updated mvSDK driver packages. matrixfg.sys version 1.113, bugfix DMA unmap. (mvTITAN, mvSIGMA) CHANGED BEHAVIOUR: - Unused data type 'TImageResultConfiguration' removed from the interface. If your (all shipped packages) code was using it, replace every occurrence by 'TBoolean'. This will not affect shipped applications. NEW FEATURES: - New class 'RequestInfoConfiguration' added to the interface. (mvIMPACT_acquire.h) (mv.impact.acquire.dll) BUGS FIXED: - The request properties 'Image/OffsetX' and 'Image/OffsetY' where always reported as (mvGenTLConsumer-lib) 0 when the chunk mode was used. - When using more than one mvTITAN/mvGAMMA grabber, Calling the 'CloseDevice' could (all shipped packages for mvTITAN/mvGAMMA devices) cause problems. - Storing calibration data to an XML setting is working again. (mvPropHandling-lib) (Bug introduced in version 2.9.0) 10.07.2014 2.9.2 CHANGED BEHAVIOUR: - When updating the firmware of a device, and the UserSet persistence is enabled, the (mvDeviceConfigure) UserSet used after the update will be the one defined in UserSetDefaultSelector, instead of the "Default" UserSet. BUGS FIXED: - Updating the firmware of more than one devices with UserSet persistence enabled, (mvDeviceConfigure) will not restore the UserSets correctly for all devices except the first. (Bug introduced in version 2.9.1) - Trying to load an incompatible setting from the Registry on Windows did cause a (mvPropHandling-lib) leak of 2 handles. - Restoring settings from the Registry on Windows did not work correctly for GenICam (mvGenTLConsumer-lib) devices. (mvPropHandling-lib) (Bug introduced in version 2.9.0) 07.07.2014 2.9.1 CHANGED BEHAVIOUR: - When using mvDeviceConfigure to update the firmware of a GenICam device, UserSets (mvDeviceConfigure) stored on the device can be preserved now. NEW FEATURES: - The 'DataStreamModule' object will allow access to the 'mvResendRequestCredits' (mvGenTLProducer.cti) property now when the NDIS based filter driver for GEV is used. BUGS FIXED: - Restoring settings did not work correctly for GenICam devices. (mvGenTLConsumer-lib) (Bug introduced in version 2.9.0) - The x64 version of wxPropView no longer crashes on Windows 8.1 when opening the color (wxPropView) correction wizard. This was a bug in wxWidgets that surfaced when migrating to Visual Studio 2013. (Bug introduced in version 2.8.0) 24.06.2014 2.9.0 UPDATES: - Firmware version 1.6.157.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Bugs Fixed: - Long Link-Up times caused by noise on the twisted pair interface. - mvBlueCOUGARX-102eG/C, mvBlueCOUGARX-104eG/C: Linescan trigger mode: Camera absent after stopping and starting trigger signal. - mvBlueCOUGARX-102eG/C,mvBlueCOUGARX-104eG/C: In trigger mode first image needs too much trigger pulses. - mvBlueFOX3-1020G/C: Reduced framerate for special AOI and exposure settings. - LUT Wizard improved: X-axis uses a nicer scaling now, if there is only a single LUT (wxPropView) this no longer has to be explicitly selected during synchronization, when loading a setting the dialog is refreshed automatically, 'Cache -> Device' is now the default, some hints added. - Improved Axis scaling of the various analysis plots and wizards. (wxPropView) CHANGED BEHAVIOUR: - Writing an invalid (e.g. too long) value to a GenICam string property will result in (mvGenTLConsumer-lib) an exception reported back to the application now. NEW FEATURES: - The number of request objects in the result queue can now be queried at runtime, by (all shipped packages) calling the imageRequestResultQueueElementCount() method of the FunctionInterface class. BUGS FIXED: - '\n' and '\t' characters in string property values will be stored into and restored (mvPropHandling-lib) from XML settings correctly now. - Installing MATRIX VISION Linux drivers on trusty tahr (Ubuntu 14.04 LTS) systems no (all shipped packages for Unix/Linux systems) longer generates warnings/errors when building SingleSnap and mvDeviceConfigure. - Load settings from XML file now works properly. This change brings some compatibility (all shipped packages) issues. XML files created from now on will not be usable with mvIMPACT Acquire versions smaller than 2.9.0! XML files created with older versions, will still be usable, but with the same limitations they had up until now. - The x64 version of wxPropView no longer crashes on Windows 8.1. This was a bug in (wxPropView) wxWidgets that surfaced when migrating to Visual Studio 2013. (Bug introduced in version 2.8.0) - Windows XP is supported again! (all MSI-based shipped packages) (Bug introduced in version 2.8.0) 26.05.2014 2.8.0 UPDATES: - Firmware version 1.6.139.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GenICam compliant devices) Changed Behaviour: - all mvBlueFOX3 devices: Minimum width is now 32 Pixel. - mvBlueFOX3-1013C/1020C/1031C/1100C: Transfer rate limitation changed for RGB pixelformats. - mvBlueFOX3-1020G/C: Maximum fps limit is now 51.8 Hz - mvBlueFOX3-1100C: Bayer pattern changed to RG. - mvBlueFOX3-1031C: Bayer pattern changed to GR. - mvBlueFOX3-1012d(b)G/C: Sensor's width and offsetX must be a multiple of 2. New Features: - TriggerSelector 'FrameBurstActive' is available for CCD sensors. - all mvBlueFOX3 devices: Frame Average Control added to mvBlueFOX3 Firmware. - mvBlueFOX3-1100C: RGB pixelformat support added. Bugs Fixed: - Enabling and disabling both FrameBurstStart and FrameBurstActive Triggers could result in continuous acquisition. - all mvBlueFOX3 devices: Timestamp does not increment with several pixel clocks - mvBlueCOUGAR-X1010G/C: Possible camera crash when changing sensor settings. - mvBlueFOX3-1020C/1013C: Incorrect colors in linescan mode. - Migration from Visual Studio 2005 to Visual Studio 2013. All Windows packages of (all shipped MSI-based packages) mvIMPACT Acquire are compiled using Visual Studio 2013 now. This might require changes in custom installation scripts. See 'Installation from private setup routines' in the documentation. - On systems with 4 or more CPUs the Bayer filter will no longer use SSE2 but openMP (all shipped packages) in order to better distribute the overall load. NEW FEATURES: - 'update_fw_file' parameter added to the command line interface. (mvDeviceConfigure) BUGS FIXED: - FlatField correction wrap-around issue when using the Mono16 pixel format. (mvGenTLConsumer-lib) - Crash when calling 'DevClose' for a U3V device without previously calling 'DSClose' (mvGenTLProducer.cti) for each open stream for this device. 15.05.2014 2.7.2 UPDATES: - When only a feature using a deprecated GenICam SFNC name is available this will be (mvIMPACT_acquire_GenICam.h) automatically be bound to the object expecting the new name as well. This allows (mv.impact.acquire.dll) to write less code when multiple devices shall be supported. - Migration to version 3.0.7.0 of libusbK for U3V devices. (mvGenTL_Acquire*.msi) CHANGED BEHAVIOUR: - The deprecated libraries 'mvBlueCOUGAR-lib' and 'mvTLIClientGigE.cti' are no longer (all shipped packages for GEV/U3V devices) shipped as the migration to version 2.4.0 of the GenApi runtime requires changing custom installers anyway. - Examples for Visual Studio 6 and 2003 are no longer shipped as part of the (all shipped MSI-based packages) installation. Visual Studio 6 and 2003 are no longer supported by mvIMPACT Acquire! - The GEV filter driver will also capture buffers that not start with a leader but with (mvGigECapture.sys, version 2.0.16.50) payload when running with the 'ResendImmediate' strategy being switched off (as it should be done for LAG connections). NEW FEATURES: - Visual Studio 2013 workspace and project files added to sample programs. (all shipped MSI based packages) - When a firmware update that was triggered by using the command line interface did (mvDeviceConfigure) fail, the exit code of the application will no longer be 0. BUGS FIXED: - Potential crash when calling 'DMR_UpdateDeviceList' or (mvGenTLProducer.cti) 'mvIMPACT::acquire::DeviceManager::updateDeviceList' for a device that disappeared or was disconnected just at roughly the same time. - Buffers with a 'PayloadSize' smaller than 'wMaxPacketSize' of the streaming endpoint (mvGenTLProducer.cti) can be captured from U3V devices now. - Some empty folders no longer needed are no longer created by the installers. (all shipped MSI-based packages) - The 'FileVersion' and 'SchemaVersion' properties did not always contain the correct (mvGenTLConsumer-lib) values(decimal values have been interpreted as hexadecimal ones). - Potential deadlock when a device did re-appear during a call to (mvGenTLConsumer-lib) 'mvIMPACT::acquire::FunctionInterface::updateDeviceList' or 'DMR_UpdateDeviceList'. 14.04.2014 2.7.1 UPDATES: - Firmware version 1.6.123.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GEV/U3V devices) New Features: - writable discovery ACK delay for GEV devices implemented. Bugs Fixed: - CCDs: Changing exposure time in trigger mode: New exposure time was not active during first trigger. (Bug introduced in 1.6.42.0) BUGS FIXED: - Potential deadlock when a new 'DMR_ImageRequestReset' was executed simultaneously (all shipped packages) from 2 or more threads. 10.04.2014 2.7.0 DEPRECATED API CODE: - 'mvIMPACT::acquire::InfoBase': Use 'mvIMPACT::acquire::Info' instead. (mvIMPACT_acquire.h) - 'mvIMPACT::acquire::StatisticsBase': Use 'mvIMPACT::acquire::Statistics' instead. (mvIMPACT_acquire.h) - 'mvIMPACT::acquire::SystemBase': Use 'mvIMPACT::acquire::SystemSettings' instead. (mvIMPACT_acquire.h) UPDATES: - Firmware version 1.6.120.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GEV/U3V devices) Changed Behaviour: - Applying changes to the binning or decimation registers will not affect the visible section of the AOI anymore. - mvBlueFOX3-1020G/C: Maximum fps=51.8 Hz - mvBlueFOX3-1100G/C, mvBlueCOUGAR-X1010G/C: 'BinningVertical' restricts the vertical AOI increment('Height', 'OffsetY') to 4 pixels. New Features: - 'FrameBurstStartTrigger' with sensor trigger for CCDs. Bugs Fixed: - mvBlueCOUGAR-XD104G/C: Streaming could fail after startup. - Invalid frame rate limits when using long exposure times. (mvBlueCOUGAR, mvBlueFOX3) - mvBlueFOX3-1100G/C, mvBlueFOX3-1140GW, mvBlueCOUGAR-X1010G/C: Cameras do now saturate also for 'Width' < 500 pixels. - mvBlueFOX3: On Windows 8.1 with default drivers installed the device could go into a sleep state. - mvBlueFOX3: All image related parameters will be reported correctly after a successful image acquisition. - Migration to version 2.4.0 of the GenApi runtime. (mvBlueCOUGAR installer) - Migration to version 1.4 of the GenICam GenTL spec. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - Improved hotplug support on Windows while streaming. (mvGenTLProducer.cti) NEW FEATURES: - Property 'AcquisitionBurstFrameCount' added to class 'CameraSettingsBlueCOUGAR' for (mvGenTLConsumer-lib) usage with interface layout 'dilDeviceSpecific'. (mv.impact.acquire.dll) - U3V event and chunk support added. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - The color of the 'Request Info' overlay is now selectable. (wxPropView) - The 'Requests' list is no longer displayed in the property tree of wxPropView. As an (wxPropView) alternative a 'Detailed Request Information' has been added. BUGS FIXED: - The 'State' property of a device did change before it was fully initialised when it (mvGenTLConsumer-lib) was re-discovered after being absent for some time. 21.03.2014 2.6.3 UPDATES: - Firmware version 1.6.105.0 for mvBlueFOX3 and mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Changed behaviour: - 'BalanceWhiteAuto' and 'BlackLevelAuto' temperature stability increased. (mvBlueCOUGAR-X/XD104) New features: - Binning/Decimation for many sensors added Bugs fixed: - On USB2 acquisition provides no longer out-dated images. (mvBlueFOX3) - 'mvLineDebounceTime' value in default UserSet was not working after startup. - A firmware update can also be performed on a USB2 interface. (mvBlueFOX3) - After a device reset, it could happen that the mvBlueFOX3 did not restart (mvBlueFOX3) properly. - Swapped rows and columns corrected. (mvBlueFOX3-1140C) - Device was sporadically not recognized by the host. (mvBlueFOX3) - Load speed for large settings (e.g. containing calibration data) from an XML file (all shipped packages) has been improved. BUGS FIXED: - Autoscrolling in the log-textcontrol did not work correctly. (mvDeviceConfigure) - Partial (no GEV Support) install/uninstall of the mvGenTL_Acquire driver over the (mvGenTL_Acquire*.msi) command line caused 'Error 2753'. - Working with a U3V device from one process while enumerating it from another could (mvGenTLProducer.cti) cause communication problems. - Defining digital signals for various I/O related operations using the class (mv.impact.acquire.dll) 'mv.impact.acquire.OutputSignalGeneratorFrameGrabber' did not work correctly. For example the function 'mv.impact.acquire.OutputSignalGeneratorFrameGrabber.getValidPassThroughSignalCount' did always return 0. - Calling 'mv.impact.acquire.OutputSignalGeneratorFrameGrabber.undefineSignal' for (mv.impact.acquire.dll) mvTITAN, mvGAMMA, mvDELTA or mvSIGMA did always return 'DMR_FEATURE_NOT_AVAILABLE', even if the feature was avaiable. - Writing register data with more than 492 bytes to a U3V device did fail when operated (mvGenTLProducer.cti) on a USB2 interface. 06.03.2014 2.6.2 UPDATES: - Firmware version 1.6.89.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Bugs fixed: - mvBlueCOUGAR-X(D) with CCDs: No frames with minimum exposure times. (Bug introduced in 1.6.39.0) - mvBlueCOUGAR-XD: DHCP in LAG mode works independently of the link where the DHCP offer arrives now(CISCO Switch) Changed behaviour: - mvBlueCOUGAR-X102eG/C/GE: Phase shift adapted for extended temperature range. CHANGED BEHAVIOUR: - Auto-fill of Netmask and Gateway fields in 'Assign Temporary IP' dialogue now matches (mvIPConfigure) that of persistent IP settings. MAC address and 'Build MAC from serial' button are now greyed out when a device is already selected in the device list. NEW FEATURES: - Updating a mvBlueFOX3 device with a damaged firmware does also work on Linux now. (mvGenTLProducer.cti) - 'CPU Idle States' can be configured using the command line interface now. This can (mvDeviceConfigure) be combined with the 'quit' parameter to be used from a script. (Windows only). BUGS FIXED: - blue screen (BSOD) on Windows 8.x systems when removing or disabling the filter (mvGigECapture.sys, version 2.0.15.49) driver one or multiple adapters. - Open streams are closed before opening them again, U3V interfaces are ignored in the (mvIPConfigure) log window and auto scrolling now always works correctly. - U3V(mvBlueFOX3) devices can now be installed on a Linux system, without affecting (mvGenTL_Acquire-x86_*.tgz) USB2(mvBlueFOX) devices on the same system. 20.02.2014 2.6.1 UPDATES: - Firmware version 1.6.74.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Bugs fixed: - mvBlueCOUGAR-3X120aG: Timers were not working. Changed behaviour: - SequencerControl: Visibility = Expert. Not saved in UserSet. - Firmware version 1.6.75.0 for mvBlueFOX3 devices added. (all shipped packages for USB3 Vision devices) Bugs fixed: - USB2 compatibility improved. NEW FEATURES - Buffers larger than 4 MB can be captured from U3V devices on Windows via USB2 now. (mvGenTLProducer.cti) BUGS FIXED: - When a GEV device did send a PENDING_ACK command back to the host and the timeout (mvGenTLProducer.cti) reported in this command did elapse, the host did send an invalid GEV packet back to the device. 10.02.2014 2.6.0 DEPRECATED API CODE: - Interface layout 'dilDeviceSpecific' has been declared deprecated for usage with (all shipped packages) the mvGenTL_Acquire driver packages, thus for mvBlueCOUGAR-P, mvBlueCOUGAR-S, mvBlueCOUGAR-X, mvBlueCOUGAR-XD and mvBlueLYNX-M7 devices. UPDATES: - Firmware version 1.6.63.0 for mvBlueFOX3 devices added. (all shipped packages for USB3 Vision devices) New features: - Secure firmware update added, starting with this firmware all file updates will be verified before being activated. - mvBlueFOX3-1031G/C: Internal pixel clock increased to 75 MHz (was 68,75 MHz). Now 30Hz@1920x1080 is possible. Bugs fixed: - GenCP pending acknowledge detection changed to a timer based version. CHANGED BEHAVIOUR: - Interface layout 'dilGeneric' has been removed from the public interface. It had been (all shipped packages) declared deprecated for more than a year now. This will not break existing binaries but will require changes in the source during rebuilds. - Improved IP address handling in mvIPConfigure: Setting of persistent IPs can now be (mvIPConfigure) done directly without setting a temporary IP in advance. NEW FEATURES - Initial support for U3V(USB3 Vision) on Linux added. (mvGenTL_Acquire-x86_*.tgz) - mvBlueFOX devices support up to 256(instead of 64) HRTC steps now. (mvBlueFOX-lib) - Added support for new tap geometries to the tap sort filter: 'cltxg1X2/cltyg1Y2', (all shipped packages) 'cltxg2X/cltyg1Y2', 'cltxg2XE/cltyg1Y2' and 'cltxg2XM/cltyg1Y2'. Please note that all these formats are currently not covered by the GenICam SFNC. BUGS FIXED: - Potential crashes when a network interface was assigned a new IP-address, subnet mask (mvGenTLConsumer-lib) or gateway and then afterwards 'DMR_UpdateDeviceList' or (mvGenTLProducer.cti) 'mvIMPACT::acquire::DeviceManager::updateDeviceList' was called from a running application. - On Windows there was a small memory leak (approx. 60 KB) with each call to (mvGenTLProducer.cti) 'DMR_UpdateDeviceList' or 'mvIMPACT::acquire::DeviceManager::updateDeviceList'. (Bug introduced in version 2.5.17) - On Windows there was a leak of 1 OS-handle with each call to (mvGenTLProducer.cti) 'DMR_UpdateDeviceList' or 'mvIMPACT::acquire::DeviceManager::updateDeviceList'. See 'known issues' in the documentation. (Bug introduced in version 2.5.17) - Potential crash when selecting an unsupported bits per pixel, pixels per cycle (mvHYPERIONfg-lib) combination for a given pixel format. - Potential deadlock when a new 'DMR_ImageRequestSingle' was executed while a pending (mvGenTLConsumer-lib) 'DMR_ImageRequestReset' was being processed. 20.01.2014 2.5.20 UPDATES: - Firmware version 1.6.42.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Bugs fixed: - LinescanMode (E2V-sensors): Correct overtrigger behaviour. - mvBlueCOUGAR-X120bG: Device stopped responding when constantly changing exposure values from the application. New features: - SequencerControl according to GenICam-SFNC. So far CCDs only. - mvBlueCOUGAR-XD126G, mvBlueCOUGAR-XD126aG: 36MHz pixel clock enabled. Changed behaviour: - mvBlueCOUGAR-X105G: Sensor only supports a width increment of 2. - mvBlueCOUGAR-3X120aG: Added support for two additional digital inputs, removed Bayer formats. - Firmware version 1.6.42.0 for mvBlueFOX3 devices added. (all shipped packages for USB3 Vision devices) Bugs fixed: - LinescanMode (E2V-sensors): Correct overtrigger behaviour. - Wrong pixel format info in leader when changing the 'PixelFormat' (e.g. Mono10 -> Mono12). - mvBlueFOX3-1013x, mvBlueFOX3-1020x: Use correct AOI now. Changed behaviour: - mvBlueFOX3-1031x: FrameStartTrigger disabled. CHANGED BEHAVIOUR: - The GEV filter driver does no longer try to re-construct buffers that have already (mvGigECapture.sys, version 2.0.14.48) been partially streamed from the device to the host when a capture buffer is arriving late in the filter driver. This is now in sync. with the socket layer based implementation. NEW FEATURES: - New color correction matrix added: 'cticmmBlueFOX3_x031C_WPPLS' This will be used by (all shipped packages) 'mvBlueFOX3-1031C' devices. - New color correction matrices added: 'cticmmBlueCOUGAR_x21C_WPPLS' and (all shipped packages) 'cticmmBlueFOX_x21C_WPPLS'. These will be used by 'mvBlueCOUGAR-Xx21C' and 'mvBlueFOX-x21C' devices. - mvBlueFOX3 devices with a damaged firmware image can be accessed again. When (mvGenTLProducer.cti) detecting such a device the mvGenTLProducer.cti library will automatically upload a working firmware image into the RAM of the device. However to permanently store a firmware on the device another update using mvDeviceConfigure is needed afterwards. BUGS FIXED: - Potential crashes when a GEV device lost network connectivity during a certain (mvGenTLConsumer-lib) stage of the initialisation. - Potential crash when a device did report a 'min' value larger than the 'max' value (wxPropView) for a feature an this feature then got modified in the property tree by the user. 14.01.2014 2.5.19 UPDATES: - Slightly improved error reporting for the GEV filter driver. (mvGigECapture.sys, version 2.0.13.47) (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - When using the command line parameters to update the device firmware the application (mvDeviceConfigure) will also allow to downgrade the firmware now. Only firmware versions which are exactly the same will be ignored. BUGS FIXED: - Firmware update via command line did not work for mvBlueFOX3 devices if the (mvDeviceConfigure) 'ipv4_mask' parameter was specified. - Potential deadlock when a device did re-appear during a call to (mvGenTLConsumer-lib) 'mvIMPACT::acquire::FunctionInterface::updateDeviceList' or 'DMR_UpdateDeviceList'. 12.12.2013 2.5.18 UPDATES: - Firmware version 0x33 (51) for mvBlueFOX devices added. (mvBlueFOX-lib) Changes: - Fix for illegal endpoint size. Now only if CH9Fix-Bit in device EEPROM is set. Needs mvIMPACT Acquire 1.11.10 or later on the host to to run. - Firmware version 1.6.31.0 for mvBlueFOX3 devices added. (all shipped packages for USB3 Vision devices) Bugs fixed: - Booting host system with a camera already connected could lead to this device becoming inaccessible. - Triggermode also works after timeout. (needs mvIMPACT Acquire 2.5.18 or greater) - mvBlueFOX3-1100x, -1140x: Switching to trigger mode could fail. - mvBlueFOX3-1013x: Improved pixel sampling at low temperatures. - mvBlueFOX3-1013x: Bad line in rolling shutter mode with some exposure times. (E.g.: EV76C560 with exposure time = 2050 us) CHANGED BEHAVIOUR: - In rare cases where a GigE Vision did not reboot after a firmware update the device (mvGenTLConsumer-lib) driver will now report a timeout error after a certain amount of time instead of never returning from the firmware update function. NEW FEATURES: - The current progress of the firmware update is displayed when updating mvBlueCOUGAR (mvDeviceConfigure) or mvBlueFOX3 devices now. (mvGenTLConsumer-lib) - 'Chapter9TestCompatibilityEnable' property added for mvBlueFOX devices. (mvBlueFOX-lib) (Requires Firmware version 0x33 (51) or greater) - CHM version of mvBlueFOX3 manual added. (mvGenTL_Acquire*.msi) BUGS FIXED: - 'mvIMPACT::acquire::GenICam::AcquisitionControl::mvResultingFrameRate' and (mvIMPACT_acquire_GenICam.h) 'mv.impact.acquire.GenICam.AcquisitionControl.mvResultingFrameRate' did use an (mv.impact.acquire.dll) incorrect data type. Was 'PropertyI64' and is now 'PropertyF'. - In case 'ImageRequestTimeout_ms' did elapse for a single buffer queued for a U3V (mvGenTLProducer.cti) device, sometimes multiple buffers currently queued have been signalled under Windows Vista and greater (one with 'rrTimeout', all others with 'rrRequestAborted'). 12.11.2013 2.5.17 UPDATES: - LAG link speed detection improved. (mvGenTLProducer.cti) NEW FEATURES: - Firmware version 1.6.15.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Bugs fixed: - mvBlueCOUGAR-XD: LAG sometimes was not correctly configured when using a persistent IP address. - mvBlueCOUGAR-X102eG/C, mvBlueCOUGAR-X102eGE, mvBlueCOUGAR-X104eG/C: Bad line in rolling shutter mode with some exposure times. (E.g.: mvBlueCOUGAR-X102eG with exposure time = 2050us) - mvBlueCOUGAR-X102bG/C did stop streaming when using exposure times > 12220us in triggered mode. BUGS FIXED: - U3V devices supporting events can be initialised now. (mvGenTLProducer.cti) - 'ibpfMono12Packed_V1' (which corresponds 'Mono12p' from the PFNC specification) is (all shipped packages) supported properly now. - 'ImageRequestTimeout_ms' handling improved. Whenever one buffer timeout did expire (mvHYPERIONfg-lib) all buffers currently queued have been returned to the application. - The 'Connected To IPv4 Address' combo box as well as the (mvIPConfigure) 'Local IP To Use For Sending' became read-only. - Modifying the state of the hardware LUT in parallel with changing any other parameter (mvBlueFOX-lib) except the 'Gain_dB' property did not update the LUT related parameters. - Socket driver handles ChunkData correctly again. (mvGenTLProducer.cti) (Bug introduced in version 2.5.15) 17.10.2013 2.5.16 DEPRECATED API CODE: - The function 'DMR_UpgradeDeviceFeatures' has been declared deprecated. Since this (all shipped packages) function never did perform any useful task there is no direct replacement. CHANGED BEHAVIOUR: - All mvBlueLYNX (NOT mvBlueLYNX-X!) related stuff removed from mvIMPACT Acquire. This (all shipped packages) is an internal change as the ppc603e based mvIMPACT Acquire package was never officially released but also did result in some stuff being removed from the public interface. The following stuff has been removed: mvIMPACT::acquire::CameraSettingsBlueLYNX, mv.impact.acquire.CameraSettingsBlueLYNX, TBlueLYNXCameraDataClipMode and TBlueLYNXCameraFlashMode. Please remove every occurrence of any of those data types from your code. - Improved image quality for mvBlueFOX-223 devices. (mvBlueFOX-lib) NEW FEATURES: - Firmware version 1.6.4.0 for mvBlueFOX3 devices added. (all shipped packages for USB3 Vision devices) - Property 'mvIMPACT::acquire::Request::chunkExposureTime' added. (mvIMPACT_acquire.h) - .NET Property 'mv.impact.acquire.Request.chunkExposureTime' added. (mv.impact.acquire.dll) - Firmware version 1.6.5.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - Trigger 'FrameStart'/'mvTimestampReset' with 'AnyEdge'. - PFNC compliant formats added. - mvBlueCOUGAR-XD: PowerSaving properties for CCDs added. - Support for 4 digital inputs for POEI added. Bugs fixed: - mvBlueCOUGAR-XD: Resend packets did contain invalid image data. - Setting 'CounterValue' the first time after booting the device did not work. - EV76C560: AOI changes sometimes where not visible in the first image. - MT9M024/MT9M034: First trigger failed when switching to trigger mode. - ICX415: Shadow in first lines when not using the full height of the sensor. BUGS FIXED: - The display module as well as the analysis plots in wxPropView did mix up the lower (mvDisplay-lib) 4 bits of 2 consecutive pixels. (wxPropView) - In case 'ImageRequestTimeout_ms' did elapse for a single buffer queued for a U3V (mvGenTLProducer.cti) device, sometimes all buffers currently queued have been signalled (one with 'rrTimeout', all others with 'rrRequestAborted'). - When an 'ImageRequestTimeout_ms' did elapse more or less at the same time an U3V (mvGenTLProducer.cti) device did start streaming sometimes the stream did get out of sync resulting in a lot of buffers being reported as corrupted. - On systems running low on resources or with an extremely fragmented kernel space U3V (mvGenTLProducer.cti) buffers sometimes did not completely cleaned up. - Firmware version 0x32 (50) for mvBlueFOX devices added. (mvBlueFOX-lib) Bugs fixed: - Fix for illegal endpoint size on all mvBlueFOX-MLC. Needs mvIMPACT Acquire 1.11.10 or later on the host to run. 29.08.2013 2.5.15 UPDATES: - Improved the performance of the socket based GEV driver when working in LAG mode with (mvGenTLProducer.cti) 2 links or more. 23.08.2013 2.5.14 CHANGED BEHAVIOUR: - The old MFC based version of 'PropView' is no longer shipped as part of the examples. (all shipped MSI-based packages) It has long been replaced by 'wxPropView'. Its source files are also part of the installer packages but must be enabled explicitly during the installation. BUGS FIXED: - 'GenICam::InterfaceModule::deviceLinkSpeed' and (mvGenTLProducer.cti) 'GenICam::DeviceModule::deviceLinkSpeed' did report too large values for U3V devices. - Trying to display an invalid buffer in 'ffBGR2BytePacked_V2' format could cause in a (mvDisplay-lib) crash. - With 'InterfaceLayout' set to 'dilDeviceSpecific' and 'ImageDestination/PixelFormat' (mvGenTLConsumer-lib) set to a 'Mono' format, Bayer versions of the mvBlueCOUGAR-X did deliver unprocessed Bayer images even when 'ImageProcessing/ColorProcessing' was set to 'Auto'. (Bug introduced in version 2.4.0) 12.08.2013 2.5.13 CHANGED BEHAVIOUR: - Class 'mvIMPACT::acquire::display::ImageDisplayWindow' does no longer allow a copy (mvIMPACT_acquire_display.h) constructor or an assignment operator. UPDATES: - Improved support for third party U3V and GEV devices that did not use the numerical (mvGenTLConsumer-lib) pixel format values from their corresponding standard as numerical values in the 'PixelFormat' enumeration in their GenICam XML file. - Full 64-bit support added for mvTITAN and mvGAMMA boards. This will now allow to run (mvTITAN_mvGAMMA-x64.msi) 64-bit applications with these boards on Windows. - Migration to version 3.0.6.0 of libusbK for U3V devices. (mvGenTL_Acquire*.msi) NEW FEATURES: - Property 'TimestampLatch' added to class 'mv.impact.acquire.GenICam.DeviceControl'. (mv.impact.acquire.dll) - Property 'TimestampLatch' added to class (mvIMPACT_acquire_GenICam.h) 'mvIMPACT::acquire::GenICam::DeviceControl'. - New C# example application added to all packages: 'ContinuousCaptureAllDevices'. (all MSI-based shipped packages) BUGS FIXED: - An attempt to open a U3V device that has either crashed or did report an invalid (mvGenTLProducer.cti) value (0) for the 'Maximum Device Response Time' register could cause the driver to lock up. - Raw I/O mode enabled for the U3V streaming enabled. This fixes potential deadlocks (mvGenTLProducer.cti) when asynchronously aborting the acquisition. - When working with the Socket API based transport layer for GEV sometimes re-starting (mvGenTLProducer.cti) the stream did not result in data being captured. (Bug introduced in version 2.5.7) - When calling 'DSStartAcquisition' with 'iNumToAcquire' greater than 0 the automatic (mvGenTLProducer.cti) stop of the acquisition engine did sometimes continue to deliver buffers even after the desired number of buffers had already been captured. - Calling 'DSRevokeBuffer' after 'DSQueueBuffer' and 'DSFlushQueue' did always return (mvGenTLProducer.cti) 'GC_ERR_INVALID_BUFFER' for U3V devices if no 'DSStartAcquisition' and 'DSStopAcquisition' sequence was executed in between. - Mirror filter did not correctly handle images where one dimension was smaller than 2 (all shipped packages) or in YUV422Planar mode when one dimension was smaller than 4. - Sometimes a 'pure virtual function call' exception was raised during the refresh of (mvGenTLConsumer-lib) features defining a polling time in their GenICam XML file. - With 'InterfaceLayout' set to 'dilDeviceSpecific' the features under 'Info/Camera' (mvGenTLConsumer-lib) that provide write access could not be modified. - Error message in log-file each time when modifying a digital output related property (mvGenTLConsumer-lib) in 'DeviceSpecific' interface for mvBlueCOUGAR-P or mvBlueLYNX-M7 devices. (Bug introduced in version 2.2.1) - Example 'ContinuousCaptureAllDevices' could crash. (ContinuousCaptureAllDevices) (Bug introduced in version 1.12.69) - Pixel format 'ibpfBGR101010Packed_V2' can be displayed correctly again. (mvDisplay-lib) (Bug introduced in version 2.4.0) 29.07.2013 2.5.12 UPDATES: - GEV DISCOVERY commands will be sent without the 'allow broadcast' bit in the command (mvGenTLProducer.cti) by default now as some devices then do not answer at all. The bit however will still be used when running e.g. mvIPConfigure with the 'Advanced Device Discovery' option enabled. - A warning will be issued now when a device has been detected but cannot be used for (wxPropView) whatever reasons at the moment. NEW FEATURES: - New color correction matrices added: 'cticmmBlueCOUGAR_Xx04eC_WPPLS' and (all shipped packages) 'cticmmBlueFOX3_x020C_WPPLS'. These will be used by 'mvBlueCOUGAR-X104eC' and 'mvBlueFOX3-1020C' devices. - Full 64-bit support added for mvDELTA and mvSIGMA boards. This will now allow to run (mvDELTA_mvSIGMA-x64.msi) 64-bit applications with these boards on Windows. BUGS FIXED: - Calling 'DSQueueBuffer' for a U3V data stream did result in a buffer being returned (mvGenTLProducer.cti) immediately (mostly without consistent content). - Each open/close iteration did increase the handle count of the current process by 7. (low level driver (oswin32-lib), Windows) 23.07.2013 2.5.11 UPDATES: - Improved the detection of link speed changes on a network interface. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - New FPGA file for mvBlueFOX-22x devices added. This improves EMC compatibility for (mvBlueFOX-lib) this devices. (FPGA version: 37). NEW FEATURES: - New C# example application added to all packages: 'Callback'. (all MSI-based shipped packages) - Initial version of hot-plug support for U3V devices added. (mvGenTLProducer.cti) (mvGenTLConsumer-lib) - Firmware version 1.5.102.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - GVCP-Capability bit 'test_data' is now supported, Test packets can now be filled with verifiable test data according to the GEV specification. Bugs fixed: - Increasing 'DeviceClockfrequency' did not result in higher frame rates when setting 'mvAcquisitionFrameRateLimitMode' to 'mvLegacy'. (Bug introduced in firmware version 1.5.95.0) - static versions of the functions 'gevGetEffectivePayloadPacketsPerImage', (mvIMPACT_acquire_GenICam.h) 'gevGetEffectiveBytesPerImage', 'gevGetResultingBandwidth' and 'gevGetResultingPacketDelayadded' added to class 'mvIMPACT::acquire::GenICam::TransportLayerControl'. - static versions of the functions 'gevGetEffectivePayloadPacketsPerImage', (mv.impact.acquire.dll) 'gevGetEffectiveBytesPerImage', 'gevGetResultingBandwidth' and 'gevGetResultingPacketDelayadded' added to class 'mv.impact.acquire.GenICam.TransportLayerControl'. BUGS FIXED: - mvBlueFOX-x00w: With the advanced option 'daoOnDemandTriggerPreShot' enabled (mvBlueFOX-lib) and with 'OnDemand'-TriggerMode active could randomly cause corrupted images. - mvBlueFOX-x05: Changing the exposure time sometimes did become effective with a (mvBlueFOX-lib) delay of one frame. - Increasing the 'RequestCount' above a certain value (16 or 21 depending on buffer (mvGenTLProducer.cti) layout) did cause the acquisition to lock up with U3V devices. - Converting Bayer data to RGB for buffers with a width smaller than 6 could cause (all shipped packages) crashes on some Windows systems. - Applying the 'GainOffsetKnee' filter to Bayer data for images with a width smaller (all shipped packages) than 4 did result in crashes. - Applying the 'AdaptiveEdgeSensing' filter to Bayer data for images with a width (all shipped packages) than 4 did result in crashes when at least one gain did differ from 1.0. - The 'SIPayloadFinalTransfer1Size' register of U3V devices was not set correctly (mvGenTLProducer.cti) on a 64-bit system. This could e.g. result in images not being delivered. - Calling 'FunctionInterface::imageRequestReset' several times with (mvGenTLProducer.cti) 'AcquisitionStartStopBehaviour' to 'assbUser' could result in a deadlock. - When opening a GenICam compliant device did fail wxPropView did crash when (wxPropView) 'Settings -> Warn On Reduced Driver Performance' was active. (Bug introduced in version 2.5.5) 07.06.2013 2.5.10 UPDATES: - Just minor internal changes. Nothing new, nothing fixed. 06.06.2013 2.5.9 UPDATES: - Improved write speed to GenICam features with the 'Cachable' attribute set to (mvGenTLConsumer-lib) 'NoCache'. NEW FEATURES: - Property 'defectivePixelsFound' added to class (mvIMPACT_acquire.h) 'mvIMPACT::acquire::ImageProcessing'. - Property 'defectivePixelsFound' added to class (mv.impact.acquire.dll) 'mv.impact.acquire.ImageProcessing'. - Added 'fffmTransmitCorrectionImage' to 'TFlatFieldFilterMode' enumeration. (all shipped packages) - Added 'dcfmTransmitCorrectionImage' to 'TDarkCurrentFilterMode' enumeration. (all shipped packages) - Added 'bcmPacked' and 'bcmLinearPacked' to 'TBayerConversionMode' enumeration. (all shipped packages) BUGS FIXED: - Certain image dimensions (e.g. 2100x28 when converted from 'ibpfRGB888Packed' to (all shipped packages) 'ibpfBGR888Packed' and vice versa) could cause crashes. - Creating an mvIMPACT buffer from a request using pixel format 'ibpfYUV422Planar' (all shipped packages) could cause crashes. - Wizard button for file upload/download will become enabled when the 'FileSelector' (wxPropView) feature is selected in the property grid now. - When the 'ChannelSplit' filter was active and the destination format was set to (all shipped packages) 'ibpfRGB888Packed' the format conversion was not executed. - mvBlueFOX-x00w: First image after gain/expose change did still use the previous (mvBlueFOX-lib) values. (Bug introduced in version 2.5.0) - In case of a failed white balance calibration the correct error codes will be written (all shipped packages) to the 'WBResult' property now. - Performing a white balance calibration with 'WBAoiMode' set to 'amCentered' on an (all shipped packages) image with either the width or the height or both smaller or equal than 75 pixel did crash at runtime. - Calling 'DMR_OpenDevice' with a valid device handle and a NULL-pointer for 'hDrv' did (all shipped packages) crash at runtime. 23.05.2013 2.5.8 CHANGED BEHAVIOUR: - Reducing the request count will now release large chunks of memory which previously (all shipped packages) had been locked for future usage. - Getting a bitmap from 'mv.impact.acquire.Request.bitmapData' will also work for (mv.impact.acquire.dll) images with a pitch, that is not a multiple of 4 now. - 'mv.impact.acquire.LibraryPath.init' is called inside the constructor of (mv.impact.acquire.dll) 'mv.impact.acquire.DeviceManager' now, thus an application does no longer has to do this explicitly unless changes shall be applied to the search paths. - Default values changed: (mvGenTLProducer.cti) 'GenICam::InterfaceModule::mvDeviceCommandChannelTransmissionTimeout': Was 0 is 200. 'GenICam::InterfaceModule::mvDeviceCommandChannelRetryCount': Was 0 is 3. - When working with a setting with the deprecated property (all shipped packages) 'mvIMPACT::acquire::ImageProcessing::mirrorMode' being activated it was not possible to completely switch off mirroring with the newly introduced global mirror mode. - Now mvHYPERION-SDI boards starts scanning the ancillary data with a higher user data (mvHYPERIONfg-lib) id number. UPDATES: - The GEV filter driver will try to map user-mode buffers in kernel space with page (mvGigECapture.sys, version 2.0.12.46) priority 'high' now. This used to be 'normal' before. - Improved zooming in and out of the image display using the scroll wheel. (wxPropView) - Improved Bayer and mono data handling inside the 'DefectivePixel' filter. (all shipped packages) NEW FEATURES: - Property 'mvLinearLogarithmicMode' added to class (mvIMPACT_acquire_GenICam.h) 'mvIMPACT::acquire::GenICam::AnalogControl'. - Property 'mvLinearLogarithmicMode' added to class (mv.impact.acquire.dll) 'mv.impact.acquire.GenICam.AnalogControl'. - All code that is signed using a code signing certificate will also be timestamped (all shipped MSI based packages) now. - Internal conversion filter added. When a device transfers in either of these formats: (all shipped packages) 'ibpfMono12Packed_V1', 'ibpfMono12Packed_V2' or 'ibpfBGR101010Packed_V2', and at least one post-processing filter can't deal with this format, the driver will now silently convert this data into a suitable format if possible. - Firmware version 1.5.95.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - mvBlueCOUGAR-X1010: DeviceClockFrequency 96 Mhz added. - mvBlueCOUGAR-X102e: High dynamic range added (mvLinearLogarithmicMode). Bugs fixed: - CCD-sensors: Changing the exposure time was delayed by one frame when using long exposure times. - mvBlueCOUGAR-XD-124/126/129: Visible SUB-pulse in overlapped trigger mode. - mvBlueCOUGAR-X102bG: Too bright images when using trigger mode. - mvBlueCOUGAR-XD: Correct link speed after booting the host while the camera was already up. Changed behaviour: - mvBlueCOUGAR-XD: PixelFormat '12BitPacked' became faster. - TriggerSoftwareCommand became WriteOnly. BUGS FIXED: - Setting 'GenICam::InterfaceModule::mvDeviceCommandChannelRetryCount' to 0 did result (mvGenTLProducer.cti) in no commands being sent at all. - Some newly introduced header files were missing in the Linux packages. (all shipped packages for Unix/Linux systems) (Bug introduced in version 2.5.7) - Creating instances of the classes 'mv.impact.acquire.GenICam.SystemModule' (mv.impact.acquire.dll) or 'mv.impact.acquire.GenICam.InterfaceModule' do no longer open the device passed to the constructors. - With 'LUTMode' set to direct and 'LUTImplementation' set to 'Software' the highest (all shipped packages) possible pixel value was not affected by the LUT transformation. - Fixed various minor issues not affecting user applications directly. (mvPropHandling-lib) 07.05.2013 2.5.7 CHANGED BEHAVIOUR: - When the GEV filter driver detects packets belonging to a new frame that can't (mvGigECapture.sys, version 2.0.11.45) be reconstructed safely as too much data is missing already (e.g. because at the time the transmission of the frame did start there was no buffer to capture the data into and the capture buffer did arrive inside the driver after large parts of the buffer have already been lost) the remains of these frames are dropped now. Previous versions did report these frames as incomplete with the remains of the data. UPDATES: - Improved GEV acquisition streaming start speed. (mvGenTLProducer.cti) - Added 'daoUseRawSensorGain' to the 'Camera/AdvancedOptions' property for (mv.impact.acquire.dll) mvBlueFOX-x05 devices. - Some common functions, templates and classes used in various example applications (all shipped packages) moved into separate header files under $(MVIMPACT_ACQUIRE_DIR)/common. NEW FEATURES: - Functions 'gevGetEffectivePayloadPacketsPerImage', 'gevGetEffectiveBytesPerImage', (mvIMPACT_acquire_GenICam.h) 'gevGetResultingBandwidth' and 'gevGetResultingPacketDelayadded' added to class 'mvIMPACT::acquire::GenICam::TransportLayerControl'. - Functions 'gevGetEffectivePayloadPacketsPerImage', 'gevGetEffectiveBytesPerImage', (mv.impact.acquire.dll) 'gevGetResultingBandwidth' and 'gevGetResultingPacketDelayadded' added to 'mv.impact.acquire.GenICam.TransportLayerControl'. BUGS FIXED: - Some code did rely on the SFNC feature 'PixelFormat' using the 'real' numerical (mvGenTLConsumer-lib) values as the integer representation of the enumeration entries, thus the entry for 'Mono8' for a GEV device was expected to have a numerical representation of '0x01080001'. However the numerical values for SFNC enumerated features are not covered by the standard thus in theory can be anything. - Downloading the GenICam file from a device did align the amount of memory read to a (mvGenTLConsumer-lib) 4-byte boundary. For transport layer technologies that are not restricted to a certain alignment such as GenCP or U3V this could result in the device to complain about too much memory being read. - With 'Settings -> Property Grid -> Use Selector Grouping' active a read-only selector (wxPropGrid-lib) automatically resulted in all selected features becoming read-only as well. - Network adapters with an IPv4 address of 255.255.255.255 can discover GEV devices (mvGenTLProducer.cti) now. - Alignment restrictions reported by the 'SIInfo' register of a U3V device are handled (mvGenTLProducer.cti) now. 29.04.2013 2.5.6 CHANGED BEHAVIOUR: - The 'index' parameter of the constructors of the classes 'InterfaceModule' and (mvIMPACT_acquire_GenICam.h) 'DataStreamModule' classes belonging to the 'GenICam' namespace have been changed (mv.impact.acquire.dll) from int to int64 as the properties these values are obtained from also use 64-bit integers. NEW FEATURES: - Added 'daoUseRawSensorGain' to the 'Camera/AdvancedOptions' property for (mvBlueFOX-lib) mvBlueFOX-x05 devices. - Checks for potential performance issues added. (mvIPConfigure) - LUT wizard will be available even if the 'LUTSelector' feature is not supported. (wxPropView) BUGS FIXED: - Potential crashes in when working with the spatial noise histogram in one of the (wxPropView) following pixel formats: 'ibpfRGB101010Packed', 'ibpfRGB121212Packed', 'ibpfRGB141414Packed', 'ibpfRGB161616Packed', 'ibpfYUV444_UYV_10Packed' or 'ibpfYUV444_10Packed'. - Potential crashes when working with the 'DefectivePixelsFilter/Mode' property set to (all shipped packages) 'dpfm3x3Median'. - 'DefectivePixelsFilter/Mode' set to 'dpfm3x3Median' or 'dpfm3x1Average' is working (all shipped packages) with 2-byte mono input pixel formats now. 23.04.2013 2.5.5 UPDATES: - Various hyperlinks added (links to online documentation etc.) to 'Help' menus. (wxPropView) (mvDeviceConfigure) (mvGigEConfigure) (mvIPConfigure) - A warning will be issued now when driver performance issues are detected (e.g. a (wxPropView) missing GEV filter driver). - A warning will be issued now when multiple network adapters of the host system seem (mvIPConfigure) to reside in the same subnet. - A more sophisticated check for outdated firmware has been added for mvBlueCOUGAR-X, (mvDeviceConfigure) mvBlueCOUGAR-XD and mvBlueFOX3 devices. BUGS FIXED: - The state of the pixel histogram related features was not properly restored when (wxPropView) closing and restarting the application. - Multiple GEV events send in one network packet will be correctly forwarded as (mvGenTLProducer.cti) multiple individual events by the producer now. - Calling 'DMR_AllocImageBuffer' with pixel formats 'ibpfRGB101010Packed', (mvDeviceManager-lib) 'ibpfRGB121212Packed', 'ibpfRGB141414Packed' or 'ibpfRGB161616Packed' did result in a buffer set up for 'ibpfRGBx888Planar' with only the pixel format, width and height set correctly. - Working with a single buffer in the NDIS filter driver that is incomplete, can't be (mvGigECapture.sys, version 2.0.10.44) reconstructed and has an infinite timeout resulted in the buffer never being returned until 'imageRequestReset' was called. - When working with 'AcquisitionStartStopBehaviour' to 'assbDefault' and just single (mvGenTLConsumer-lib) buffers in the queue, due to long or delayed processing times internal calls to 'AcquisitionStop' have been issued. This could rarely result in the next buffer being returned with the result status 'rrRequestAborted'. - The order of interfaces as reported by iterating over (mvGenTLConsumer-lib) 'SystemModule::interfaceSelector' did not match the order of 'InterfaceModule' instances, thus when using the selector value as the 'index' parameter for the 'InterfaceModule' this did not always result in the correct interface instance being created. 10.04.2013 2.5.4 NEW FEATURES: - Property 'OffsetCorrection_pc' for mvBlueFOX-x02aG devices added. (mvBlueFOX-lib) (mvIMPACT_acquire.h) (mv.impact.acquire.dll) 08.04.2013 2.5.3 UPDATES: - Added 'Why the MSI packages are that large' to the 'Installation from private setup (mvIMPACT_Acquire_API_C_manual) routines' chapter of the documentation. (mvIMPACT_Acquire_API_CPP_manual) (mvIMPACT_Acquire_API_NET_manual) - Internal migration to IPP 7.1.1. (all shipped packages) NEW FEATURES: - Property 'AcquisitionControl::mvResultingFrameRate' published. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) CHANGED BEHAVIOUR: - In 'SingleFrame' mode calling 'DMR_AcquisitionStart' or (mvGenTLConsumer-lib) 'FunctionInterface::acquisitionStart' will return 'DMR_ACQUISITION_ENGINE_BUSY' now if the current single frame acquisition has not finished before the next one shall be started. - The application now waits for previous single frame acquisitions to become ready (wxPropView) before accepting a new acquisition request. The old behaviour can be enabled by using the menu item 'Settings -> Allow Fast Single Frame Acquisition'. BUGS FIXED: - mvIPConfigure could crash when updating the device list when U3V devices where (mvIPConfigure) connected to the system and a U3V driver was installed. 02.04.2013 2.5.2 NEW FEATURES: - The 'InfoPlot' can plot every PropertyI, PropertyI64 and PropertyF feature attached (wxPropView) to a request of the current device now. - New test image formats added: 'vdtmHorizontalBayer12Packed_V1Ramp' and (mvVirtualDevice-lib) 'vdtmHorizontalBayer12Packed_V2Ramp'. - Firmware version 1.5.80.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - New sensor supported: EV76C570 Bugs fixed: - Switching 'TriggerSource' from 'Software' to 'Line4' did trigger one image when 'Line4' was high. - In triggered mode applied new exposure times did become effective AFTER the next trigger signal and not with the NEXT trigger signal. (Bug introduced in firmware version 1.5.71.0) - Class 'mvXLampControl' added to namespace 'mvIMPACT::acquire::GenICam' (C++) and (mvIMPACT_acquire.h) 'mv.impact.acquire.GenICam' (.NET). (mv.impact.acquire.dll) - Properties 'CameraSettingsVirtualDevice::tapsXGeometry' and (mvIMPACT_acquire.h) 'CameraSettingsVirtualDevice::tapsYGeometry' published. (mv.impact.acquire.dll) - Properties 'GenICam::InterfaceModule::mvDeviceCommandChannelTransmissionTimeout' and (mvIMPACT_acquire.h) 'GenICam::InterfaceModule::mvDeviceCommandChannelRetryCount' added. (mv.impact.acquire.dll) (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - The method 'mvIMPACT::acquire::Request::getComponentLocator' became public. (mvIMPACT_acquire.h) - The method 'mv.impact.acquire.Request.getComponentLocator' became public. (mv.impact.acquire.dll) - Internally a monotonic clock is used wherever possible (Linux only). (all shipped packages for Unix/Linux systems) BUGS FIXED: - The palette of the 'System.Drawing.Bitmap' instance returned by (mv.impact.acquire.dll) 'mv.impact.acquire.Request.bitmapData' will actually use a grey-scale palette for pixel format 'System.Drawing.Imaging.PixelFormat.Format8bppIndexed' now as stated in the documentation. - Fixed various minor issues regarding memory allocation. (mvBlueFOX-lib) - mvBlueFOX3 devices did stay open after a firmware update when the application was not (mvDeviceConfigure) terminated. - When a sequence with acquisition mode 'MultiFrame' did terminate on Linux the (wxPropView) application did lock up. - mvTITAN-G1/mvGAMMA-G: When changing the gain and/or offset as well as the video (mvTITANfg-lib) channel between 2 requests the gain/offset changes where lost. - When a request timeout did elapse with 'AcquisitionMode' set to 'SingleFrame', the (mvGenTLProducer.cti) 'RequestResult' did contain 'rrRequestAborted' instead of 'rrTimeout' for U3V devices. - When quickly requesting images with 'AcquisitionMode' set to 'SingleFrame' from U3V (mvGenTLProducer.cti) devices, 'RequestResult' did contain 'rrFrameCorrupt' from time to time. - The link speed for GEV devices supporting the link speed register is correctly (mvGenTLProducer.cti) reported by the properties 'GenICam::InterfaceModule::DeviceLinkSpeed' and 'GenICam::DeviceModule::DeviceLinkSpeed' now. 19.03.2013 2.5.1 NEW FEATURES: - Property 'mv.impact.acquire.Request.bitmapData' and function (mv.impact.acquire.dll) 'mv.impact.acquire.TImageBufferPixelFormat.asSystemDrawingImagingPixelFormat' added. - mvBlueFOX3_technical_manuals.pdf added. (mvGenTL_Acquire*.msi) BUGS FIXED: - mvBlueFOX-200wG/C devices will no longer offer the 'SlowClock' FPGA, which is (mvBlueFOX-lib) supported by the MLC version only. 14.03.2013 2.5.0 CHANGED BEHAVIOUR: - mvBlueFOX-x00w: First image after gain/expose change did still (mvBlueFOX-lib) use the previous values. - Flash was activated 2 times. - Artifacts in the upper image area of the image. - mvBlueFOX-x00w: Increased gain range (lower limit is -1dB now). (mvBlueFOX-lib) - mvBlueFOX-x00w: Increased minimum exposure time to the minimum the sensor can (mvBlueFOX-lib) actually work with properly. - mvBlueFOX-x00w: Adjusted gain in HDR mode. (mvBlueFOX-lib) - Version 1.1.10.8 of the kernel mode driver added. This driver is no longer WHQL (mvDELTA_mvSIGMA-x86_64-.msi) certified. - Version 1.1.4.13 of the kernel mode driver added. This driver is no longer WHQL (mvTITAN_mvGAMMA-x86_64-.msi) certified. - The name format for log-sections in mvDebugFlags.mvd has changed. (all shipped packages) Was: , became: -', 'EnumPropertyI' and 'EnumPropertyI64'. - Devices not supporting streaming channels are supported now. (mvGenTLConsumer-lib) - Firmware update for mvBlueFOX3 devices is possible now. (mvDeviceConfigure) (mvGenTLProducer-lib) (mvGenTLConsumer-lib) - New constant added to 'TRequestResult': 'rrDataAcquisitionNotSupported'. This will (all shipped packages) e.g. be reported when attempting to capture data from a U3V or GEV device that does not support stream channels. - Documentation related merge modules added to installer packages. (all MSI-based shipped packages) BUGS FIXED: - A mvBlueLYNX-X device can no longer be opened with 'DEVICE_ACCESS_CONTROL' more than (mvGenTLProducer-lib) once. 04.03.2013 2.4.2 UPDATES: - Added 'Relationship between driver, firmware, FPGA file and user settings' section (mvBlueFOX3 technical manual) to the 'Quickstart' chapter of the documentation. (mvBlueCOUGAR-X technical manual) (mvBlueLYNX-M7 technical manual) - Added 'Running customized mvIMPACT Acquire MSI installers from other installation (mvIMPACT_Acquire_API_C_manual) frameworks' to the 'Installation from private setup routines' chapter of the (mvIMPACT_Acquire_API_CPP_manual) documentation. (mvIMPACT_Acquire_API_NET_manual) CHANGED BEHAVIOUR: - The method 'mv.impact.acquire.helper.RequestReadyEventArgs.unlockData' became (mv.impact.acquire.dll) 'internal', the method 'mv.impact.acquire.helper.RequestReadyEventArgs.lockData' became a property 'mv.impact.acquire.helper.RequestReadyEventArgs.data'. Instead of 'mv.impact.acquire.helper.RequestReadyEventArgs.unlockData', 'mv.impact.acquire.helper.RequestReadyEventData.Dispose' must be called now. NEW FEATURES: - 'mv.impact.acquire.Request.getIMPACTImage' function added. This can be used to get (mv.impact.acquire.dll) a handle that can be used to create a 'mvIMPACT_NET.Image' object. - New C# example application added to all packages: 'CameraDescriptions'. (all MSI-based shipped packages) BUGS FIXED: - When images where displayed in one format and then in a different format which did (mvDisplay-lib) use the same amount of bytes per buffer but a different width and/or height the displayed images where not correct. - When the required payload size for a U3V device did change and data has been acquired (mvGenTLProducer.cti) into a buffer before then capturing data in this buffer with reduced payload size did fail. - PFNC compliant pixel formats 'BGRa8' ('ibpfRGBx888Packed' in mvIMPACT Acquire) and (mvGenTLConsumer-lib) 'YUV8_UYV' ('ibpfYUV444_UYVPacked' in mvIMPACT Acquire) are supported correctly now. - Driver crash during Windows8_64 power off. (low level mvHYPERION driver, Windows) - In Windows standby mode, after re-enabling the mvHYPERION grabber no data acquisition (low level mvHYPERION driver, Windows) was possible from mvHYPERION-CLm/CLf/SDI devices. - Writing non-binary data to a string property and then reading back that data in (mvPropHandling-lib) binary format could cause crashes if the non-binary data was shorter than 4 bytes. - Fixed various minor issues regarding memory allocation. (all shipped packages) 22.02.2013 2.4.1 UPDATES: - Added 'Acquisition Start/Stop Behaviour' section to 'How the capture process works' (all shipped packages) chapter to the API documentation. - Added 'Relationship between driver, firmware and FPGA file' section to the (mvBlueFOX technical manual) 'Quickstart' chapter of the documentation. CHANGED BEHAVIOUR: - The following properties have been removed from the public interface as they are not (all shipped packages) exposed by the framework anyway thus have never been available: 'GenICam::acquisitionStart', 'GenICam::acquisitionStop', 'GenICam::acquisitionAbort'. - The shift feature introduced in version 2.4.0 will clip pixels that have a too large (all shipped packages) value to be displayed to the maximum value instead of just masking the higher bits now. NEW FEATURES: - New property published in 'SystemSettings': 'AcquisitionIdleTimeMax_ms' (all shipped packages) BUGS FIXED: - Color correction matrices for mvBlueCOUGAR-XD104C, mvBlueCOUGAR-XD104aC, (all shipped packages) mvBlueCOUGAR-XD104bC, mvBlueCOUGAR-XD124bC, mvBlueCOUGAR-XD126aC and mvBlueCOUGAR-XD129aC devices will be correctly selected when setting 'ColorTwistInputCorrectionMatrix' to 'DeviceSpecific' now. - 'Statistics/FramesPerSecond' property converges towards the actual value with (all shipped packages) 'normal' speed again. (Bug introduced in version 2.4.0) - 'GenICamInterfaceLayout' example does no longer crash on Linux. (all shipped packages for Unix/Linux systems) - The 'mvUserData' property of an mvBlueCOUGAR-X or mvBlueCOUGAR-XD device is no longer (mvGenTLConsumer-lib) stored in a setting/restored from a setting. As this feature is stored in non-volatile device memory restoring this value would modify the data in the device which is not wanted. - imageRequestSingle on Linux did always return an error. (mvHYPERIONfg-lib) - Building low level drivers for Linux failed. (low level mvHYPERION driver, Linux) - For images in pixel format 'ibpfBGR101010Packed_V2' the red and the blue channel have (mvVirtualDevice-lib) been flipped. - For images in pixel format 'ibpfBGR101010Packed_V2' the 'ChannelSplit' filter did (all shipped packages) split in BGR order instead of RGB as for all other RGB and BGR formats. 15.02.2013 2.4.0 UPDATES: - Further improved resend behaviour for GEV devices. Fine-tuned some default (mvGigECapture.sys, version 2.0.9.43) parameters. (mvGenTLProducer.cti) - The device selection ComboBox as well as the title bar will contain the value of the (wxPropView) 'DeviceID' property of the selected device now. - Slightly improved usability of the 'Assign Temporary IPv4 Address' dialog. (mvIPConfigure) - Improved error handling in case of low system resources (GEV only). (mvGenTLProducer.cti) CHANGED BEHAVIOUR: - The U3V kernel driver will be installed by default now. (mvGenTL_Acquire*.msi) - The properties 'Request::infoFrameID' and 'Request::infoFrameNr' are reported as 64 (all shipped packages) bit integers now. Applications compiled with this version of the interface MUST update mvPropHandling-lib on the target system when accessing these properties! NEW FEATURES: - Overloaded method for 'mv.impact.acquire.Property.readS' added that takes an input of (mv.impact.acquire.dll) 'TPropertyLimits'. - For images with more than 8 bits per pixel per channel the left and right arrow keys (wxPropView) can be used to select which bits shall be displayed now. - New function added: 'mvDispSetShift', 'mvDispGetShift', 'mvDisplayGetAppliedShift', (mvDisplay-lib) - New function added: 'mvIMPACT::acquire::display::ImageDisplay::GetShift', (mvIMPACT_acquire_display.h) 'mvIMPACT::acquire::display::ImageDisplay::SetShift', 'mvIMPACT::acquire::display::ImageDisplay::GetAppliedShift'. - New properties added: 'mv.acquire.display.ImageDisplay.shift', (mv.impact.acquire.display.dll) 'mv.acquire.display.ImageDisplay.appliedShift' - Added support for 'DeviceTemperature' and 'DeviceTemperatureSelector' for (mvGenTLProducer.cti) mvBlueLYNX-X devices. - New classes added: 'mv.impact.acquire.helper.RequestProvider', (mv.impact.acquire.dll) 'mv.impact.acquire.helper.RequestReadyEventArgs' and 'mv.impact.acquire.helper.IRequestBuffer. - 'cltxg4X2E' added to 'TCameraTapsXGeometry'. (mvTITANfg-lib) (mvHYPERIONfg-lib) (mvVirtualDevice-lib) (mv.impact.acquire.dll) - New C# example applications added to all packages: 'DigitalIOs', (all shipped MSI-based packages) 'GenICamInterfaceLayout', 'Properties', 'ContinuousCaptureSimple'. - New property published in 'ChannelSplit' filter: 'channelSplitDeinterlaceEnable' (all shipped packages) - Color correction matrices added: 'cticmmBlueCOUGAR_Xx04C_WPPLS' and (all shipped packages) 'cticmmBlueCOUGAR_Xx04aC_WPPLS'. These will be used by mvBlueCOUGAR-X104C and mvBlueCOUGAR-X104aC devices. BUGS FIXED: - Capturing to user supplied memory with 'InterfaceLayout' set to 'dilDeviceSpecific' (mvGenTLConsumer-lib) did not work with mvBlueCOUGAR-X devices that came up with a GEV pixel format that was using more than one channel. - In rare cases (when the current working directory on Linux became invalid) (all shipped packages for Unix/Linux systems) starting a mvIMPACT Acquire based application could crash. - When Bayer images where generated by setting the properties 'Camera/PixelFormat' and (mvVirtualDevice-lib) 'Camera/BayerMosaicParity' the driver internal de-Bayer filter did not process the images in 'Auto' mode. 31.01.2013 2.3.4 BUGS FIXED: - Fixed some compiler warnings. (mvHYPERIONfg-lib) 30.01.2013 2.3.3 UPDATES: - Default values when using the filter driver changed: 'ResendResponseTimeout_ms' (mvGigECapture.sys, version 2.0.8.42) changed from 2 to 3. BUGS FIXED: - The buffers internally allocated used 1 byte too much memory. This could cause a (mvGenTLProducer.cti) decrease in the overall performance because of redundant reallocations. (Bug introduced in version 2.0.9) - Improved resend behaviour when working in LAG mode with 2 links or more. Sometimes (mvGigECapture.sys, version 2.0.8.42) parts of frames that already have been captured completely where requested for resend. - Timestamps for U3V devices will correctly be reported in us by the framework now. (mvGenTLProducer.cti) - Temporary aborting a running acquisition by calling (mvGenTLProducer.cti) 'FunctionInterface::imageRequestReset' could cause incorrect behaviour. (Bug introduced in version 2.3.2) - Improved FrameStart Activation LevelHigh/LevelLow. Previous versions did not (mvHYPERIONfg-lib) correctly work with this trigger event. 23.01.2013 2.3.2 CHANGED BEHAVIOUR: - Migration to the official version 1.0 of the USB3 Vision standard. This required some (mvGenTLProducer.cti) changes in internal data structures. Only devices compliant with version 1.0 of the standard will be supported now. NEW FEATURES: - First version that adds .NET/Mono support for mvBlueLYNX-X devices. (mvBlueLYNX-X firmware) BUGS FIXED: - When calling 'FunctionInterface::imageRequestSingle' after calling (mvGenTLProducer.cti) 'FunctionInterface::acquisitionStart' on a mvBlueLYNX-X device an error was logged, but the request was not properly processed. This did result in the function 'FunctionInterface::imageRequestReset' not returning when called. - Continuous acquisition from a USB3 Vision device did sometimes stop when e.g. post (mvGenTLProducer.cti) processing of images took longer then the time between 2 consecutive images delivered by the device. - RealTimeController Opcode Jump, writing jump address corrected. (mvHYPERIONfg-lib) 18.01.2013 2.3.1 NEW FEATURES: - New sample added to all packages: 'ContinuousCaptureOnlyProcessLatest'. (all shipped MSI-based packages) - Added 'CPU Idle States Enabled' option (Windows only). (mvDeviceConfigure) - Firmware version 1.5.61.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - EV76C560/EV76C661: AEC and AGC implemented. - Random delay added to discovery acknowledge as required by the GEV specification, improves the detection of all cameras when there are many cameras connected to one subnet. Changed behaviour: - Streaming indication (LED color GREEN) is triggerd by FrameStart not by AcquisitionStart. Bugs fixed: - CCD sensors sometimes did deliver corrupt image data. (Bug introduced in firmware version 1.5.18.0) BUGS FIXED: - Trying to close an unplugged mvBlueFOX fitted with a motor focus module did crash (mvBlueFOX-lib) at runtime. 11.01.2013 2.3.0 CHANGED BEHAVIOUR: - mvBlueCOUGAR-msi packages have been renamed to mvGenTL_Acquire-msi. Some libraries (mvBlueCOUGAR.msi -> mvGenTL_Acquire.msi) belonging to these packages also changed their name: mvBlueCOUGAR-lib became (mvBlueCOUGAR-lib -> mvGenTLConsumer-lib) mvGenTLConsumer-lib, mvTLIClientGigE.cti became mvGenTLProducer.cti. This change (mvTLIClientGigE.cti -> mvGenTLProducer.cti) became necessary as by now a much wider range of products(e.g. mvBlueFOX3, mvBlueLYNX-X) is supported by this package and therefore the names became misleading. The old files are still part of the package but are not installed by default any more. See 'Installation from private setup routines' for details. UPDATES: - On 64-bit Windows now both 32-bit and 64-bit processes can access the GenICam runtime (mvGenTL_Acquire.msi) at the same time. This required a change in the way the GenICam runtime is installed (mvGenTL_Acquire-x64.msi) on the target system. See 'Installation from private setup routines' for details. - Added some missing stuff to the documentation. (all shipped packages) - 'Done' button added to close the application. (mvGigEConfigure) - The 64-bit MSI installers do no longer create a desktop shortcut to mvDeviceConfigure.(all shipped MSI-based packages) BUGS FIXED: - 'CaptureToUserMemory' works with 'AcquisitionStartStopBehaviour' set to 'assbUser' (all shipped packages) - When sending multi-byte Bayer data to the internal de-Bayer algorithm with (all shipped packages) 'ColorProcessing' set to 'cpmBayerToMono' did result in incorrect results on multi-core systems. - unmap user memory works now. Previous version did not unmap user memory if working in (mvHYPERION2.sys, version 2.1.36.44) a 32-bit process on a 64-bit version of Windows. (mvHYPERION.sys, version 1.0.51.53) - Properties in mv.impact.acquire.Connector did always refer to the first device in (mv.impact.acquire.dll) the list of open devices supporting this feature even if the object was created with a reference to a different device. - Instances of mvIMPACT::acquire::CameraSettingsBase did always refer to the setting (mvIMPACT_acquire.h) 'Base' as the parameter 'settingName' was not forwarded to the base class constructor. 20.12.2012 2.2.2 UPDATES: - Reading the current state of a digital input in 'DeviceSpecific' interface layout (mvBlueCOUGAR-lib) is faster now. - The saturation wizards have been re-factored an became a single 'Color Correction' (wxPropView) wizard. NEW FEATURES: - Firmware version 1.5.58.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - mvBlueCOUGAR-XD supports 8 counters now. Changed behaviour: - 'mvAcquisitionFrameRateAuto' is only available for mvBlueCOUGAR-XD devices now. Bugs fixed: - Auto Gain Control did not work correctly with multi-tap sensors. - Writing a char string without a terminating \0 to 'DeviceUserID' (called 'UserDefinedName' in mvIPConfigure.exe or called 'DeviceID' in the Device list) caused malfunction concerning EEPROM entries. - Corrupt images with -X105G/105C. (Bug introduced in firmware version 1.5.51.10) - If a 'DeviceUserID' longer than 15 Chars was written, than the camera it listed with serial number '00:00:00:00:00:00 ()' and opening is NOT possible any more. - New properties published in C++ and .NET interface: (mvIMPACT_acquire.h) colorTwistInputCorrectionMatrixEnable, colorTwistInputCorrectionMatrixMode, (mv.impact.acquire.dll) colorTwistInputCorrectionMatrixRow0, colorTwistInputCorrectionMatrixRow1, colorTwistInputCorrectionMatrixRow2, colorTwistOutputCorrectionMatrixEnable, colorTwistOutputCorrectionMatrixMode, colorTwistOutputCorrectionMatrixRow0, colorTwistOutputCorrectionMatrixRow1, colorTwistOutputCorrectionMatrixRow2, colorTwistResultingMatrixRow0, colorTwistResultingMatrixRow1 and colorTwistResultingMatrixRow2. BUGS FIXED: - With 'LUTInterpolationMode' set to 'Cubic' and 'LUTImplementation' set to 'Hardware' (mvBlueFOX-lib) the resulting LUT was incorrect. (mvBlueCOUGAR-lib) - Simultaneous acquisition from both input channels improved. Previous driver versions (mvHYPERIONfg-lib) had some errors if both input channels did run with different frame rates. - 'SingleCapture' for C# works with 'AcquisitionStartStopBehaviour' set to 'assbUser' (all shipped MSI-based packages) now. 17.12.2012 2.2.1 UPDATES: - Modifying the digital outputs in 'DeviceSpecific' interface layout is faster now. (mvBlueCOUGAR-lib) NEW FEATURES: - Firmware version 1.5.51.10 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - Support for mvBlueCOUGAR-X1010G devices - FrameEndEvent implemented. Bugs fixed: - Modifying the gain while AEC and AGC is active resulted in incorrect automode. - CMV2000/CMV4000 FrameStartTrigger: First trigger failed. - The user will be notified now if 2 products with different firmware versions are (wxPropView) detected in mvDeviceConfigure or a device with an outdated firmware is opened in (mvDeviceConfigure) wxPropView. - Further improved API documentation: Added [in], [out] and [in, out] statements to (all shipped packages) all function parameters. - 'SingleCapture' for C# added. (all shipped MSI-based packages) 13.12.2012 2.2.0 UPDATES: - Added some new message boxes in order to tell the user exactly what is the problem (mvGigEConfigure) when installing/removing the GEV filter driver fails. CHANGED BEHAVIOUR: - Some 'Access violation' exceptions internally raised during run-time type checks (mvTLIClientGigE-lib) replaced by a different internal exception with error code 'GC_ERR_INVALID_HANDLE' as the 'Access violation' exception did trigger certain debuggers(e.g. Delphi XE2 and XE3) even if handled internally. NEW FEATURES: - Redesign of documentation: (all shipped packages) - Splitted documentation into product specific technical manual and a separate document for each supported programming language. - Added .NET specific documentation. - Updated from Doxygen 1.5.8 to 1.8.2 resulting in a much nicer output. - Added a nice search Window in the online versions of the documentation. - Added 'Deprecated' section to the SDK manuals. - Added automatic links to examples in the sections describing a certain function. BUGS FIXED: - Start acquisition -> stop acquisition -> reduce request count -> start acquisition -> (mvBlueCOUGAR-lib) stop acquisition -> increase request count above the initial value -> start acquisition sequences did sometimes return requests with the 'Result' property set to 'rrUnprocessibleRequest'. - Calling 'DSGetBufferInfo' with 'BUFFER_INFO_SIZE_FILLED' always returns the correct (mvTLIClientGigE-lib) value now. (mvGigECapture.sys, version 2.0.7.41) - Calling 'OBJ_GetHandleEx' with a path(e.g. Camera/Gain_dB) from a list, that contains (mvDeviceManager-lib) a sub-list 'Camera' and a 'property 'Gain_dB' in that list will return a valid handle now. - When trying to assign a user defined name longer than supported by the device via (mvTLIClientGigE-lib) mvIPConfigure the string sent to the device was not terminated by '\0'. - Potential crashes when shutting down the device manager after a failed attempt to (mvTLIClientGigE-lib) open a U3V device. - Sometimes the streaming of a U3V device did not start. (mvTLIClientGigE-lib) 03.12.2012 2.1.4 CHANGED BEHAVIOUR: - mv.impact.acquire.RTCtrProgram.setProgramSize removed. Added a setter to the property (mv.impact.acquire.dll) mv.impact.acquire.RTCtrProgram.programSize instead. - mv.impact.acquire.IOSubSystem.pulseStartConfiguration became (mv.impact.acquire.dll) mv.impact.acquire.IOSubSystem.getPulseStartConfiguration, mv.impact.acquire.DeviceManager.deviceBaseList became mv.impact.acquire.DeviceManager.internalHandle, mv.impact.acquire.IOSubSystem.RTCtrProgram became mv.impact.acquire.IOSubSystem.getRTCtrProgram to match the C++ implementation. - mv.impact.acquire.Component.flagsAsString became a method. (mv.impact.acquire.dll) - Return value type of mv.impact.acquire.OutputSignalGeneratorFrameGrabber.defineDigitalSignal, (mv.impact.acquire.dll) mv.impact.acquire.OutputSignalGeneratorFrameGrabber.definePulse, mv.impact.acquire.OutputSignalGeneratorFrameGrabber.definePulseSequence, mv.impact.acquire.OutputSignalGeneratorFrameGrabber.definePassThroughSignal, mv.impact.acquire.OutputSignalGeneratorFrameGrabber.defineLineScanPulse, mv.impact.acquire.OutputSignalGeneratorFrameGrabber.undefineSignal and mv.impact.acquire.OutputSignalGeneratorFrameGrabber.getValidSignalsForPassThroughModes changed from bool to int to match the C++ implementation. NEW FEATURES: - mvIMPACT::acquire::CameraDescriptionManager::getTotalCameraDescriptionCount added to (mvIMPACT_acquire.h) C++ interface to match with the .NET implementation. BUGS FIXED: - Missing class mv.impact.acquire.DigitalIOMeasurementControl added. (mv.impact.acquire.dll) - Missing property mv.impact.acquire.PropertyS.binaryDataBufferMaxSize added. (mv.impact.acquire.dll) - mvBlueFOX-x02bG/C: On some systems after the initialisation the image was either too (mvBlueFOX-lib) dark or no images have been delivered at all. 26.11.2012 2.1.3 CHANGED BEHAVIOUR: - 'DeviceSpecific' and various mvBlueFOX and mvBlueCOUGAR-XD specific color correction (all shipped packages) matrices added to 'ColorTwistInputCorrectionMatrixEnable'. If the used sensor is known a matching color correction matrix will be used if 'ColorTwistInputCorrectionMatrixEnable' is set to 'DeviceSpecific', which is the default. NEW FEATURES: - Firmware version 1.5.32.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - The 'FrameBurstStart' trigger in conjunction with the 'AcqusitionFrameBurstCount' allows to trigger multiple bursts of images. - mvBlueCOUGAR-X102b: The auto modes can be done inside the device's FPGA as well now, not only within the image sensor. - mvBlueCOUGAR-X102d: Sensor specific auto exposure is working now. - New pixel formats: Mono12, Mono14. - Support for mvBlueCOUGAR-XD124a, mvBlueCOUGAR-XD126, mvBlueCOUGAR-XD129 added. - mvBlueCOUGAR-X102e: global shutter without reset is possible now. - mvBlueCOUGAR-XD: auto white balance, auto exposure, auto gain and binning is working now. - mvBlueCOUGAR-X125aG/C: Extended temperature range. - Minimum gain can be used for 'mvGainAutoLowerLimit'. - CMV2000/CMV4000: New ExposureMode 'TriggerWidth' implemented. Changed behaviour: - 'WhiteBalanceRatio' working range increased: Maximum is 8 now. - mvBlueCOUGAR-XD: Resend functionality disabled. Bugs fixed: - mvBlueCOUGAR-XD: 'mvGevSCBW' bandwidth setting, calculation also takes the number of links into account now. - mvBlueCOUGAR-X125aC works under LabVIEW again. - The real inter-packet delay, controlled by 'GevSCPD' and 'mvGevSCBW' was slightly to short. - Correction of the Format 'BGR10V2Packed': Red and blue flipped. - When the ratio between red and blue was adverse the resulting colors of the 'WhiteBalanceRatio' settings have not been correct. - mvBlueCOUGAR-X105: Noise after startup eliminated. - Depending on the selected format and AOI and with activated chunk data the delivered frames could have been incomplete. - Writing AnalogGain no longer stops the AGC. BUGS FIXED: - mvBlueFOX-x00w: First image after gain/expose change did still use the previous (mvBlueFOX-lib) values. Old behaviour can be activated by enabling the AdvancedOptions bit 'daoPipelinedGainExposeControl'. - SD-NTSC (125M487i60) format corrected to 720x486. (mvHYPERIONfg-lib) - When registering a callback to a GenICam event feature such as (mvBlueCOUGAR-lib) mv.impact.acquire.GenICam.eventExposureEndTimestamp under 64-bit Windows the application did crash upon the first event delivery. - For some properties with a registered user callback the callback was executed a (mvBlueCOUGAR-lib) second time when reading the new value of the property as a result of the callback. - The default minimum value for floating point properties was DBL_MIN instead of (all shipped packages) -1. * DBL_MAX. - The methods 'I2CRead' and 'I2CWrite' of mv.impact.acquire.I"CControl became public as (mv.impact.acquire.dll) in C/C++. 16.11.2012 2.1.2 CHANGED BEHAVIOUR: - mv.impact.acquire.EnumPropertyF is a Generic class now. (mv.impact.acquire.dll) BUGS FIXED: - mv.impact.acquire.OutputSignalGeneratorBlueDevice allows access to digital outputs (mv.impact.acquire.dll) now. - Internal checks for certain versions of a specification did not always work (mvTLIClientGigE-lib) correctly. E.g. when a device claimed to be compliant with version 2.0 of the GEV spec. features requiring GEV 1.1 where not accessed. - Sometimes the GEV capture driver did report 'rrNotEnoughMemory' even if this error (mvGigECapture.sys, version 2.0.5.39) has not been raised internally. (mvTLIClientGigE-lib) (Bug introduced in version 2.1.0) - Missing public properties added: mv.impact.acquire.EnumPropertyI.listOfValidValues, (mv.impact.acquire.dll) mv.impact.acquire.EnumPropertyF.listOfValidValues. - mvBlueFOX-x02dG/C: Low light mode was internally reset when changing certain camera (mvBlueFOX-lib) parameters. - Changing parameters in the currently selected camera description list did (mvTITANfg-lib) automatically set the value of 'Connector/CameraOutputUsed' to 'coAuto' for mvTITAN-RGB/G3, mvTITAN-RGB/G4, mvTITAN-CL and mvGAMMA-CL boards. - Changing the property 'DigitalOutputs/ControlMode' did automatically set the (mvTITANfg-lib) value of all 'Mode' properties of the digital outputs to 'Manual' for mvTITAN-CL and mvGAMMA-CL boards. - The first delivery of a GenTL event to a registered user callback could result in the (mvBlueCOUGAR-lib) callback being executed twice. (mvPropHandling-lib) NEW FEATURES: - 'PseudoFloatEnumProp' property added. (mvVirtualDevice-lib) - 'I2CDeviceSubAddressWidth' can be set to 0 for devices not supporting a sub-address (mvBlueFOX-lib) now. - 'DMR_GetVersion', 'mvIMPACT::acquire::DeviceManager::getVersionAsString' and (mvDeviceManager-lib) 'mv.impact.acquire.DeviceManager.getVersionAsString' added. (mv.impact.acquire.dll) 12.11.2012 2.1.1 BUGS FIXED: - GEV 2.0 events(using the 64-bit block ID) will be correctly forwarded by the producer (mvTLIClientGigE-lib) now. 06.11.2012 2.1.0 CHANGED BEHAVIOUR: - Constructors of classes mv.impact.acquire.Component and mv.impact.acquire.Property (mv.impact.acquire.dll) became public as in C/C++. NEW FEATURES: - Initial support for U3V(USB3 Vision) added. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) - NEON optimized version of Bayer decoder added for mvBlueLYNX-X devices. (mvBlueCOUGAR-lib) BUGS FIXED: - mv.impact.acquire.Property.readSArray without the delimiter parameter inserts a (mv.impact.acquire.dll) single whitespace between the values now as in C/C++. - Storing and restoring calibration data for the 'DefectivePixelsFilter' does work (all shipped packages) again. (Bug introduced in version 1.6.8) - Calling 'DSGetBufferInfo' with 'BUFFER_INFO_PIXELFORMAT', 'BUFFER_INFO_WIDTH', (mvTLIClientGigE-lib) 'BUFFER_INFO_HEIGHT', 'BUFFER_INFO_XOFFSET', 'BUFFER_INFO_YOFFSET', 'BUFFER_INFO_XPADDING' or 'BUFFER_INFO_YPADDING' will return 'GC_ERR_NOT_AVAILABLE' if the payload type of the buffer is reported as 'PAYLOAD_TYPE_CHUNK_DATA' and either an image is not present or it is not known if an image is present in the buffer. - Calling 'DSRevokeBuffer' for a buffer that was allocated inside the producer will (mvTLIClientGigE-lib) reset 'pBuffer' to 0 now. - Potential blue screen (BSOD) on Windows systems running low on resources. (mvGigECapture.sys, version 2.0.5.39) - GigE Vision streaming protocol blocks with more than 16383 payload packets can be (mvTLIClientGigE-lib) captured now. - Removing the last value from a property did always work even if it was the last value (mvPropHandling-lib) and also if the property did specify the 'cfFixedSize' flag. 30.10.2012 2.0.17 UPDATES: - Internal conversion from 'YUV444_UYVPacked' and 'YUV444Packed' to packed RGB and BGR (all shipped packages) formats improved. The new version is up to 10 times faster depending on the processor. CHANGED BEHAVIOUR: - The default user set can be restored via 'UserSetSelector' = 'Default' and then (mvTLIClientGigE-lib) calling 'UserSetLoad' now. It is no longer possible to overwrite this default setting using 'UserSetSave'. BUGS FIXED: - 'DEVICE_INFO_ACCESS_STATUS' will be reported as an INT32 now. This used to be UINT32. (mvTLIClientGigE-lib) - Calling 'TLOpenInterface' with a known ID but without calling 'TLUpdateInterfaceList' (mvTLIClientGigE-lib) before is working now. - Calling 'IFOpenDevice' with a known ID but without calling 'IFUpdateDeviceList' (mvTLIClientGigE-lib) before is working now. - Calling 'DSAllocAndAnnounceBuffer' could fail with 'GC_ERR_INVALID_PARAMETER' and (mvTLIClientGigE-lib) the last error message being set to 'invalid alignment' even if all parameters passed to the function where correct. 25.10.2012 2.0.16 CHANGED BEHAVIOUR: - Devices operated in interface layout 'dilGenICam' will return (mvBlueCOUGAR-lib) 'DMR_EXECUTION_PROHIBITED' when trying to load a setting while streaming is active now, as while streaming is active not all features can be updated anyway. NEW FEATURES: - Property 'mvLampDetect' added to 'mvDACParams'. (mv.impact.acquire.dll) (mvIMPACT_acquire.h) 24.10.2012 2.0.15 CHANGED BEHAVIOUR: - mv.impact.acquire.Request.requestNr became mv.impact.acquire.Request.number. (mv.impact.acquire.dll) NEW FEATURES: - mv.impact.acquire.Request.chunkCounterCount, (mv.impact.acquire.dll) mv.impact.acquire.Request.chunkTimerCount, mv.impact.acquire.Request.getChunkCounterValue and mv.impact.acquire.Request.getChunkTimerValue added. - Support for 10, 12, 14 and 16-bit PGM import added when reading image data from a (mvVirtualDevice-lib) directory. BUGS FIXED: - In 'DeviceSpecific' interface layout when for certain trigger configurations the (mvBlueCOUGAR-lib) trigger edge(TriggerActivation) was not always configured correctly for mvBlueCOUGAR-X devices. - When setting 'AcquisitionStartStopBehaviour' to 'assbUser' and calling (mvBlueCOUGAR-lib) 'DMR_AcquisitionStop' or 'mvIMPACT::acquire::FunctionInterface::acquisitionStop' while buffers were queued all these buffers did increment the 'ErrorCount' property in the 'Statistics' list by 1. 23.10.2012 2.0.14 UPDATES: - Improved performance of 'ImageDirectory' TestMode. (mvVirtualDevice-lib) NEW FEATURES: - Support for 'DeviceVersion' and 'FirmwareVersion' properties added for mvBlueLYNX-X (mvTLIClientGigE-lib) devices. (mvBlueCOUGAR-lib) BUGS FIXED: - System wide internal mutexes could cause deadlocks (Linux only). (all shipped Linux driver packages) 17.10.2012 2.0.13 BUGS FIXED: - Drivers internally deleting a feature from a feature tree could cause crashes. (mvPropHandling-lib) (Bug introduced in version 2.0.12) 16.10.2012 2.0.12 NEW FEATURES: - 'genCPVersionMajor', 'gencpVersionMinor', 'u3vVersionMajor' and 'u3vVersionMinor' (mvTLIClientGigE-lib) added to nodemaps of 'System-module', 'Interface-module' and 'Device-module'. 'gevVersionMajor', 'gevVersionMinor' and 'deviceLinkSpeed' added to nodemaps of (mvTLIClientGigE-lib) 'Interface-module' and 'Device-module'. - Preliminary support for U3V became public. To install the supporting files this must (mvBlueCOUGAR.msi) explicitly be selected in the 'Select the features to install' dialog. (mvBlueCOUGAR-x64.msi) BUGS FIXED: - Exporting the 'ConstantsDictEntry' tokens to and XML file could cause a crash when (mvPropHandling-lib) encountering a 'PROP_MAX_BINARY_BUFFER_SIZE' attached to a string property. - Importing settings from a XML file did fail for mvBlueLYNX-X devices without a valid (mvTLIClientGigE-lib) IPv4 address. 08.10.2012 2.0.11 UPDATES: - The color twist filter is no longer 'UNDER CONSTRUCTION'. (all shipped packages) NEW FEATURES: - Added support for 'inUse' Feature (see e.g. mvIMPACT::acquire::Device::isInUse). (mvTLIClientGigE-lib) When a mvBlueLYNX-X is opened with 'Exclusive' access no other application can (mvBlueCOUGAR-lib) connect now, when any application is already connected a connection with 'Exclusive' access will fail. - In the 'Detailed Feature Information' dialog the actual raw binary data will be (wxPropView) displayed now for properties specifying the 'cfContainsBinaryData' flag. Previous versions did display Base64 encoded strings. - Properties mvIMPACT::acquire::GenICam::DigitalIOControl::mvRTMInputSelector and (mvIMPACT_acquire_GenICam.h) mvIMPACT::acquire::GenICam::DigitalIOControl::mvRTMSource added. (mv.impact.acquire.dll) BUGS FIXED: - The Registry based updating of settings did not evaluate the type descriptor of the (mvPropHandling-lib) setting to update, which could result in inconsistent data sets being used for the update operation. - When a network interface had a valid IP address but no GEV device connected to the (mvTLIClientGigE-lib) interface the 'mvIMPACT::acquire::FunctionInterface::updateDeviceList' or 'DMR_UpdateDeviceList' calls took several seconds longer than necessary. - GenICam properties that specify 'NoCache' will be created with the newly introduced (mvPropHandling-lib) 'cfAlwaysForceUpdate' flag now to make sure that features will always be set to the (mvBlueCOUGAR-lib) desired value. - Internal 'Invalid proplist ID' exceptions when opening mvHYPERION devices. (mvHYPERIONfg-lib) 26.09.2012 2.0.10 BUGS FIXED: - 'imageRequestReset' behaviour improved for mvBlueLYNX-X devices. (mvTLIClientGigE-lib) 24.09.2012 2.0.9 DEPRECATED API CODE: - The function 'OBJ_GetHandle' has been declared deprecated. Use 'ObjGetHandleEx' (mvDeviceManager.h) instead. CHANGED BEHAVIOUR: - Each property list can contain up to 65535 instead of 32767 components now, and up (mvPropHandling-lib) to 65535 instead of 32767 property list in total are supported now. NEW FEATURES: - Support for 8-bit PGM import added when reading image data from a directory. (mvVirtualDevice-lib) - 'cfAllowValueCombinations' added to '/Camera/ImageType' property. (mvVirtualDevice-lib) WARNING: Because of that 'vditAll' became 'vditNone'. - Preliminary support for U3V(USB3 Vision) added(so far not accessible by everyone). (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) BUGS FIXED: - Calling 'DSGetInfo' with 'STREAM_INFO_BUF_ALIGNMENT' will return 1 instead of '0' now (mvTLIClientGigE-lib) if there are no custom alignment restrictions for that stream. - When setting a device was configured to transmit Bayer data under certain conditions (all shipped packages) the host-based Bayer decoder returned an image that only contained 'transmitted height divided by 2' lines. (Bug introduced in version 1.11.46) 30.08.2012 2.0.8 NEW FEATURES: - Function HDRControl::isAvailable added. (mvIMPACT_acquire.h) (mv.impact.acquire.dll) - New properties added to nodemap of the 'System', 'Interface' and 'Device' modules: (mvTLIClientGigE-lib) 'GenCPVersionMajor', 'GenCPVersionMinor', 'U3vVersionMajor' and 'U3vVersionMinor'. - New properties added to nodemap of the 'Interface' and 'Device' modules: (mvTLIClientGigE-lib) 'GevVersionMajor' and 'GevVersionMinor'. BUGS FIXED: - Devices reporting an invalid(too large) number of streaming channels did cause (mvBlueCOUGAR-lib) crashes. - Color twist matrices 'XYZToAdobeRGB_D50', 'XYZToAdobeRGB_D65' and 'm_XYZTosRGB_D65' (all shipped packages) internally used interchanged values. (Bug introduced in version 2.0.0) - Class AutoControlParameters did use different names under .NET for some properties (mv.impact.acquire.dll) Therefore Under .NET 'intergralTime_ms' became 'controllerIntegralTime_ms' and 'derivativeTime_ms' became 'controllerDerivativeTime_ms'. - Some newly introduced enum values were missing in the public interface. (mv.impact.acquire.dll) TLUTMapping.LUTm14To14, TLUTMapping.LUTm16To16, TBlueFOXInfoSensorCapabilities.bfiscNone, TBlueFOXInfoSensorCapabilities.bfiscTemperatureSensor. - Changing the digital input threshold did not correctly update the state of the (mvBlueFOX-lib) digital inputs. - Access to the properties aoiWidth, aoiHeight, aoiStartX and aoiStartY of class (mv.impact.acquire.dll) mv.impact.acquire.AutoControlParameters was not possible. 15.08.2012 2.0.6 NEW FEATURES: - Class mvIMPACT::acquire::GenICam::mvOMAPPreviewConfig added. (mvIMPACT_acquire_GenICam.h) (mv.impact.acquire.dll) 13.08.2012 2.0.5 UPDATES: - When using the external I2C bus lots of log messages have been generated since (mvBlueFOX-lib) version 1.12.58. - Default values when using the filter driver changed: 'mvResendRequestMax' from 0 to (mvGigECapture.sys, version 2.0.4.38) 5, 'ResendResponseTimeout_ms' from 5 to 2. - Minimum value of 'mvResendRequestMax' set to 1. (mvTLIClientGigE.cti) - When a call to 'OBJ_GetHandleEx' does fail a more meaningful exception message will (all shipped packages) be generated now. - classes mvIMPACT::acquire::RTCProgram and mvIMPACT::acquire::RTCProgramStep are (mvIMPACT_acquire.h) derived from mvIMPACT::acquire::ComponentCollection now. NEW FEATURES: - Property 'DACValueAll' added to class mvIMPACT::acquire::GenICam::mvDACParams and (mvIMPACT_acquire.h) mv.impact.acquire.GenICam.mvDACParams. (mv.impact.acquire.dll) BUGS FIXED: - mv.impact.acquire.PulseStartConfiguration.number_ and (mv.impact.acquire.dll) mv.impact.acquire.DigitalIO.description_ became private(have been public). - If supported by the device access to property (mv.impact.acquire.dll) mv.impact.acquire.PulseStartConfiguration.digitalSignal is possible now. - The property 'get' of mv.impact.acquire.DigitalOutput and (mv.impact.acquire.dll) mv.impact.acquire.DigitalInput became a public function. - The property 'isWriteable' of mv.impact.acquire.DigitalInput has been removed as (mv.impact.acquire.dll) inputs are not writeable by design and to stay in sync. with the C/C++ interface. - mv.impact.acquire.OutputSignalGeneratorFrameGrabber does allow to access all digital (mv.impact.acquire.dll) outputs of a device now. - When a call to 'createSetting' does fail a proper return value is returned now. (all shipped packages) Older versions could raise an exception. 08.08.2012 2.0.4 BUGS FIXED: - Camera descriptions have not been available via instances of class (mv.impact.acquire.dll) mv.impact.acquire.CameraDescriptionManager. All camera description count properties except 'totalCameraDescriptionCount' did return 0. 07.08.2012 2.0.3 BUGS FIXED: - When working with the interface layout 'dilGenICam' or 'dilGeneric' when requesting (mvBlueCOUGAR-lib) at least one image with image request control mode 'ircmUpdateBufferLayout' the next call to 'FunctionInterface::acquisitionStop' or 'DMR_AcquisitionStop' did not return. - For mvBlueLYNX-X devices the request buffer layout queried by the image request (mvBlueCOUGAR-lib) control mode 'ircmUpdateBufferLayout' did not correctly handle line pitch restrictions. - The initial value of 'Enable' in the saturation wizards could be incorrect. (wxPropView) 06.08.2012 2.0.2 UPDATES: - Improved zooming in and out of the image display using the scroll wheel. (wxPropView) - 'Details' button added to saturation wizard. (wxPropView) - Frame rate no longer drops when the AGC is switched on and 'AutoControlMode' is set (mvBlueFOX-lib) to 'Standard'. NEW FEATURES: - When scrollbars are visible in a display area, you can drag around the center of the (wxPropView) visible display area when NOT inside the AOI of a analysis plot. - 14 -> 14 bit and 16 -> 16 bit SW LUT are now supported by the 'LUTOperations' filter. (all shipped packages) BUGS FIXED: - When using the 'IID_IAMCameraControl' interface of the DirectShow support library (DirectShow_acquire.ax) setting the exposure time to the maximum allowed value could result in a crash. - The firmware package can be used to update mvBlueCOUGAR-X104bG/C types now (mvBlueCOUGAR-X_Update.mvu) - EEPROM readout frequency reduced. (mvHYPERION2.sys, version 2.1.36.44) 31.07.2012 2.0.1 NEW FEATURES: - All example applications can be compiled using Visual Studio 2010 now. (all shipped MSI-based packages) BUGS FIXED: - When using the 'IID_IAMCameraControl' interface of the DirectShow support library (DirectShow_acquire.ax) certain devices could cause an invalid loop if they reported a minimum, maximum or actual exposure time of '0 us'. 26.07.2012 2.0.0 UPDATES: - using MATRIX VISION devices via the DirectShow_acquire.ax library under LabVIEW no (DirectShow_acquire.ax) longer displays a 'Error: Cannot initialise OLE' messages when opening the device. (Windows only) CHANGED BEHAVIOUR: - mvIMPACT Acquire will use version numbers according to the 'Semantic Versioning (all shipped packages) Specification' starting from this version. See http://semver.org/ for details. NEW FEATURES: - Basic support for the 'IID_IAMCameraControl' interface added. So far only the (DirectShow_acquire.ax) exposure time can be controlled. - New header file added: $(MVIMPACT_ACQUIRE_DIR)/DriverBase/Include/mvVersionInfo.h (all shipped packages) BUGS FIXED: - Color twist matrices 'XYZToAdobeRGB_D50' and 'XYZToAdobeRGB_D65' internally used (all shipped packages) interchanged values, thus the D50 matrix did use the D65 values and vice versa. - The last byte of the user EEPROM could not be accessed. (mvBlueFOX-lib) - Missing file added to installer packages: UserSuppliedMemory.cs (all shipped MSI-based packages) - Timeouts during single frame acquisition could cause a leaking handle per request. (mvBlueFOX-lib) (Windows only) - Opening and closing an mvBlueFOX or mvHYPERION device caused a handle leak of 2-4 per (mvBlueFOX-lib) iteration. (mvHYPERIONfg-lib) (Windows only) - Chunk buffers that changed their size on a per buffer basis while streaming was (mvBlueCOUGAR-lib) active could not always be decoded correctly. (mvTLIClientGigE-lib) 12.07.2012 1.12.73 BUGS FIXED: - 'DeviceIPAddress' property could become 'Unavailable' after rebooting two cameras (mvBlueCOUGAR-lib) several times. - EEPROM read out improved. Current version reads byte by byte and no longer with (mvHYPERION2.sys, version 2.1.35.43) multi-byte accesses. - Driver cleanup function improved when loading the driver with default flash (mvHYPERION2.sys, version 2.1.35.43) configuration within DeviceConfigure. 11.07.2012 1.12.72 CHANGED BEHAVIOUR: - 'VBSample' removed(deprecated). (all shipped MSI-based packages) - Some objects in the namespace 'mvIMPACT::acquire::GenICam' are no longer derived from (mvIMPACT_acquire_GenICam.h) mvIMPACT::acquire::ComponentCollection as calling the 'restoreDefault' method of this base class could affect the state of properties outside the scope of the object calling the function. - All the component iteration functions (parent, firstChild, firstSibling, nextSibling (mvIMPACT_acquire.h) and lastSibling) will no longer raise an exception when there queried object is not available. However the newly returned object must be checked using the 'isValid' function before accessing it. NEW FEATURES: - Firmware version 1.4.63.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - POE support, devices with POE have only 2 digital outputs. Changed behaviour: - EV76C560: No dependency Height-OffsetY in linescan mode. - flow control and 10Base_T support disabled - 'ContinuousCapture' for VB.NET added. (all shipped MSI-based packages) - Installers will also register an environment variable 'MVIMPACT_ACQUIRE_DATA_DIR' now (all shipped MSI-based packages) that will point to the folder containing all application data specific files and folders like log-files, camera descriptions etc.. - All valid pixel formats can be selected by the 'pixelFormat' property in (mvVirtualDevice-lib) mvIMPACT::acquire::CameraSettingsBase' now. When not set to 'Auto', the properties 'TestMode' and 'ChannelBitDepth' will become invisible. BUGS FIXED: - mvBlueFOX-x05G/C: Pixel artifacts with certain exposure settings when sensor is (mvBlueFOX-lib) operated in triggered mode much improved. 27.06.2012 1.12.71 UPDATES: - Improved acquisition performance of mvBlueLYNX-X devices. (mvTLIClientGigE-lib) (mvBlueCOUGAR-lib) BUGS FIXED: - Some problems occurred while trying to open mvHYPERION devices with default firmware. (mvHYPERIONfg-lib) Also system powerdown with default firmware did end with a system crash. (mvHYPERION2.sys, version 2.1.34.42) - Setting 'ImageProcessing/ColorProcessing' to 'RawToPlanes' did not work with (all shipped packages) an input pixel format of 'ibpfMono12Packed_V2'. 15.06.2012 1.12.70 UPDATES: - Devices that only report a single streaming channel will consume one thread less now. (mvBlueCOUGAR-lib) CHANGED BEHAVIOUR: - 'F5' is used instead of 'ALT+CTRL+U' to update device lists now. (wxPropView) (mvDeviceConfigure) (mvIPConfigure) (mvGigEConfigure) NEW FEATURES: - IP address added to list control. (mvIPConfigure) BUGS FIXED: - Loading a setting did not correctly restore calibration data for the dark current and (all shipped packages) the flat field filter. (Bug introduced in version 1.11.11) - When a connection to a GEV device was lost and is re-established later sometimes log- (mvTLIClientGigE-lib) messages reported invalid values for the GevSCPSPacketSize feature. 11.06.2012 1.12.69 DEPRECATED API CODE: - The function 'mvDispSetWindow' is no longer declared in 'mvDisplay.h'. This function (mvDisplay.h) internally did only call 'mvDispSetImage'. For backward compatibility this function however will still be exported by the library thus this will not break existing applications at runtime. - In order to have consistent function names several functions from the 'C' interface (mvDisplay-lib) have been renamed. The functions will still be exported with the old names as well thus this will not break existing binaries but will require changes in the source during rebuilds. The following functions have been renamed: - mvDestroyImageWindow: Use mvDispWindowDestroy instead. - mvGetDisplayWindowHWnd: Use mvDispWindowGetWindowHandle instead. - mvGetDisplayStructure: Use mvDispWindowGetDisplayHandle instead. - mvInitDisplayWindow: Use mvDispWindowCreate instead. - mvSetDisplayWindowRefreshTime: Use mvDispWindowSetRefreshTime instead. - mvShowDisplayWindow: Use mvDispWindowShow instead. - mvInstallPreProcHandler: Use mvDispWindowSetMessageHandler instead. If re-building your application please note that when linking against the new export names, the display library on the target system must be updated as well. NEW FEATURES: - 'mvIMPACT::acquire::ComponentIterator' is now just a typedef. All functions/features (mvIMPACT_acquire.h) of this class has been moved to the base class 'mvIMPACT::acquire::Component'. This does not cause any compatibility issues, but will slightly improve the way feature iteration can be used. - Class mvIMPACT::acquire::GenICam::mvACCControl added. (mvIMPACT_acquire_GenICam.h) - All camera description recognised by a certain frame grabber will be created during (mvHYPERIONfg-lib) the initialisation now. Because of this change the class (mvSIGMAfg-lib) mvIMPACT::acquire::CameraDescriptionManager can finally access all camera (mvTITANfg-lib) descriptions that can be selected via the 'Camera/Type' property directly after initialisation of a device. BUGS FIXED: - mvBlueFOX-x05G/C: Pixel artifacts when sensor is saturated. (mvBlueFOX-lib) - mvBlueFOX-x05G/C: Pixel artifacts with certain exposure settings when sensor is (mvBlueFOX-lib) operated in triggered mode. - Calling 'mvDispUpdate' could crash in 'DM_FullScreen' mode if creating the (mvDisplay-lib) DirectDraw surface did fail before(e.g. because of missing user rights). - Missing calling convention added to typedef of 'CBOBJChanged'. (mvDeviceManager-lib) - X-Offset and Y-Offset for analysis controls where interchanged. (wxPropView) (Bug introduced in version 1.12.28) - Direct conversion of Bayer data to Mono8 improved. Border pixels are handled (all shipped packages) correctly now, RGB weighting uses the following formula now: 0.299 * R' + 0.587 * G' + 0.114 * B'. 24.05.2012 1.12.68 UPDATES: - Color correction data for mvBlueCOUGAR specific sensors updated(EXPERIMENTAL! (all shipped packages) SUBJECT TO CHANGE!) NEW FEATURES: - Initial version with full .NET support that is independent from the mvIMPACT-SDK. (mv.impact.acquire.dll) (mv.impact.acquire.display.dll) - New protected method 'mvIMPACT::acquire::Request::getComponentLocator' added. This (mvIMPACT_acquire.h) will make it a little easier to derive from 'mvIMPACT::acquire::Request'. - Functions 'mvIMPACT::acquire::Request::unlock' and (mvIMPACT_acquire.h) 'mvIMPACT::acquire::Request::configure' added. These functions result in the same behaviour as calling 'mvIMPACT::acquire::FunctionInterface::imageRequestUnlock' and 'mvIMPACT::acquire::FunctionInterface::imageRequestConfigure' but allow to write nicer code. - Functions 'mvIMPACT::acquire::Request::attachUserBuffer' and (mvIMPACT_acquire.h) 'mvIMPACT::acquire::Request::detachUserBuffer' added. This will reduce the amount of code needed to capture into user supplied memory. - Function 'mvIMPACT::acquire::FunctionInterface::getCurrentCaptureBufferLayout' added. (mvIMPACT_acquire.h) This will offer a new more convenient way find out what kind of buffers are needed to capture into user supplied memory. - Functions mvIMPACT::acquire::EnumPropertyF::getTranslationDictValues, (mvIMPACT_acquire.h) mvIMPACT::acquire::EnumPropertyI::getTranslationDictValues and mvIMPACT::acquire::EnumPropertyI64::getTranslationDictValues added. - Function 'mvDispGetWindowHandle' added. (mvDisplay-lib) - Functions 'mvDispSetImageFromImageBuffer' and 'mvDispSetImageFromRequest' added (mvDisplayExtensions.h) BUGS FIXED: - mvDispGetError did return a random error code until the first error did occur or the (mvDisplay-lib) function was called a second time(uninitialised internal variable). - mvBlueLYNX-X: Read of fallback EEPROM if default EEPROM contains an invalid MAC. (mvTLIClientGigE-lib) 11.05.2012 1.12.67 DEPRECATED API CODE: - mvIMPACT::acquire::Property::isConstDefined has been declared deprecated. Use (mvIMPACT_acquire.h) mvIMPACT::acquire::Property::hasMaxValue, mvIMPACT::acquire::Property::hasMinValue and mvIMPACT::acquire::Property::hasStepWidth instead. UPDATES: - Kernel modules rebuilt. No change in behaviour. (mvBlueFOX2.sys, version 1.0.4.5) NEW FEATURES: - Support for mvBlueFOX-202d with MT9M024 revision 0x41 added. (mvBlueFOX-lib) - 'basedOn' property added to mvIMPACT::acquire::BasicDeviceSettings. (mvIMPACT_acquire.h) BUGS FIXED: - Selecting 'Calibrate' for the 'Mode' of the 'Dark current filter' or the 'Flat Field (all shipped packages) filter' could cause crashes. (Bug introduced in version 1.12.57) - Selecting 'ImageDestination/PixelFormat' different from 'Auto' for mvBlueCOUGAR-X (mvBlueCOUGAR-lib) devices in device specific interface layout did not always result in the correct pixel format being returned by the driver. - Some properties of the mvIMPACT::acquire::GenICam::InterfaceModule class where (mvPropHandling-lib) missing the 'cfReadAccess' flag. (mvBlueCOUGAR-lib) 26.04.2012 1.12.66 NEW FEATURES: - New features added to 'ColorTwist' filter(EXPERIMENTAL! SUBJECT TO CHANGE!) (all shipped packages) BUGS FIXED: - The 'Offset_pc' property in device specific interface layout for mvBlueCOUGAR-S (mvBlueCOUGAR-lib) devices can be modified again. (Bug introduced in version 1.12.33) - Random crashes when a GEV device was unplugged or rebooted while streaming was (wxPropView) active. (Bug introduced in version 1.12.62) 24.04.2012 1.12.65 NEW FEATURES: - mvIMPACT::acquire::InfoBlueFOX::deviceSensorRevision property added. (mvIMPACT_acquire.h) - 'DeviceSensorRevision' property added. (mvBlueFOX-lib) BUGS FIXED: - When constantly calling 'mvIMPACT::acquire::FunctionInterface::updateDeviceList' or (mvBlueCOUGAR-lib) 'DMR_UpdateDeviceList' in parallel to running image acquisitions then closing a (mvTLIClientGigE-lib) device, that became disconnected could end up in a deadlock. - The maximum number of defective pixels internally that can be detected is 1000 while (all shipped packages) the 'DefectivePixelsFilter' worked with 1001. - Depending on the image content at the time of calibration setting (all shipped packages) 'DefectivePixelsFilter/Mode' either to 'dpfm3x3Median' or 'dpfm3x1Average' could result in crashes. - Multi-byte Bayer formats are correctly supported by the 'DefectivePixelsFilter' now. (all shipped packages) - NeuroCheck 6 interface only gets installed if NeuroCheck 6 has been detected on the (all shipped MSI-based packages) target system. 23.04.2012 1.12.64 CHANGED BEHAVIOUR: - Return value of the functions mvIMPACT::acquire::TriggerControl::triggerSoftware and (mvIMPACT_acquire.h) mvIMPACT::acquire::Statistics::reset changed from TDMR_ERROR to int. NEW FEATURES: - mvIMPACT::acquire::UserData::getFreeMemory function added. (mvIMPACT_acquire.h) BUGS FIXED: - A stream channel index different from 0 can be configured now. (mvGigECapture.sys, version 2.0.3.37) - High frame rates with large amounts of data lost could still lead to a hanging (mvGigECapture.sys, version 2.0.3.37) process on Windows. - Unresolved symbols 'DrvGetHardwareFeatureDecodeBufferSize' and (mvBlueFOX-lib) 'DrvEncodeHardwareFeature' at runtime on some Linux platforms. 18.04.2012 1.12.63 DEPRECATED API CODE: - The functions mvIMPACT::acquire::FunctionInterface::isRequestOK has been declared (all shipped packages) deprecated. Use mvIMPACT::acquire::Request::isOK instead. Refer to 'Porting existing code' section in the documentation for more information. NEW FEATURES: - mvIMPACT::acquire::Property::hasMaxValue, mvIMPACT::acquire::Property::hasMinValue, (mvIMPACT_acquire.h) mvIMPACT::acquire::Property::hasStepWidth added. - 'getMaxValue', 'getMinValue' and 'getStepWidth' functions added to classes (mvIMPACT_acquire.h) mvIMPACT::acquire::EnumPropertyF, mvIMPACT::acquire::EnumPropertyI and mvIMPACT::acquire::EnumPropertyI64. - mvIMPACT::acquire::Request::isOK added. (mvIMPACT_acquire.h) BUGS FIXED: - When a device suddenly stopped responding while working in 'SoftwareTrigger' mode (mvBlueCOUGAR-lib) closing the driver or calling 'imageRequestReset' could result in a deadlock when buffers where queued after the device stopped responding. - The property 'RequestResult' is updated correctly again. (all shipped packages) (Bug introduced in version 1.12.58) 16.04.2012 1.12.62 NEW FEATURES: - 'DeviceTemperature' property added for mvBlueFOX-202dx devices. (mvBlueFOX-lib) BUGS FIXED: - mvHYPERION devices can capture data again. (mvHYPERIONfg-lib) (Bug introduced in version 1.12.60) - Sporadic crashes caused by invalid image data being used to update the pixel data of (wxPropView) the status bar. - In full screen mode the info plot no longer draws on top of the image. (wxPropView) 11.04.2012 1.12.61 BUGS FIXED: - Resend requests when NOT using the 'immediate resend' strategy could be sent to an (mvGigECapture.sys, version 2.0.2.36) invalid destination MAC address(0). 11.04.2012 1.12.60 CHANGED BEHAVIOUR: - Data type of mvIMPACT::acquire::InfoBlueFOX::sensorCaps changed from (mvIMPACT_acquire.h) mvIMPACT::acquire::PropertyI to mvIMPACT::acquire::PropertyIBlueFOXInfoSensorCapabilities. This might force you to change your code during rebuilds but will not break existing binaries. - Removed unused data type 'TBlueLYNXVideoOutMode'. (mvDriverBaseEnums.h) - Property 'Camera/Flash' renamed to 'Camera/FlashMode' (mvBlueLYNX-lib) - The classes mvIMPACT::acquire::TriggerControl and mvIMPACT::acquire::SyncOutput are (mvIMPACT_acquire.h) derived from mvIMPACT::acquire::ComponentCollection now. BUGS FIXED: - High frame rates with large amounts of data lost could lead to a hanging process (mvTLIClientGigE-lib) on Windows. (mvGigECapture.sys, version 2.0.1.35) 03.04.2012 1.12.59 UPDATES: - Internally modified thread shutdown order when closing the driver instance. (mvVirtualDevice-lib) NEW FEATURES: - Firmware version 1.4.57.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - New sensors: CMV2000, CMV4000, EV76C560 (color) - New devices: mvBlueCOUGAR-XD. - CCDs: Smear reduction property. - FFC Feature extended: FFC works for sensor sizes > 1.8 Mega-Pixel, however the FFC data can not be stored in flash. Instead the data is accessible using the File Control feature (up- and download). - MT9P031: New pixel clock frequency: 98 MHz. - EV76C560: LinescanMode (AcquisitionMode 'Continuous' only) - MT9V034 can also use the FPGA's auto control features now. - Support for events added ('EventExposureEnd' 'EventLineRisingEdge'). - Application Switchover - HeartbeatDisable Changed behaviour: - Many optimizations concerning the network behaviour (traversing firewalls, DHCP/AutoIP, Discovery Process, GigE Vision Protocol, etc...) - 'ExposureActive' signal is now internally ANDed with the 'AcquisitionActive' signal, useful for controlling lighting systems. It is now equivalent to the DEPRECATED 'mvExposureAndAcquisitionActive' signal. The previous behaviour can be obtained by using the new signal 'mvExposureActive'. - GevSCBW unit changed (KByte/s -> KBps) - Only one green LUT instead of LUT_GreenRed and LUT_GreenBlue is used now. - Luminance LUT for RGB. Bugs fixed: - Color Transformation Matrix works with negative values, too - MT9V034: AGC upper limit did not work correctly. - using more than one OR gate caused unexpected results. - 'UserDefinedName' was lost after FW update. - FrameAverager (only -2xx) - First line for all CCD sensors did contain incorrect data. BUGS FIXED: - 'can not access 'CameraLink\serial\' in the network' during the installation. (all shipped 64-bit MSI-based packages with CameraLink support) 29.03.2012 1.12.58 DEPRECATED API CODE: - The functions mvIMPACT::acquire::FunctionInterface::saveSystemToDefault and (all shipped packages) DMR_SaveSystemToDefault have been declared deprecated. See 'Porting existing code section in the documentation for more information. CHANGED BEHAVIOUR: - mvIMPACT::acquire::WhiteBalanceSettings::WBresult renamed to (mvIMPACT_acquire.h) mvIMPACT::acquire::WhiteBalanceSettings::WBResult. This might force you to change your code during rebuilds but will not break existing binaries. UPDATES: - More internal optimizations. (all shipped packages) NEW FEATURES: - mvIMPACT::acquire::FunctionInterface::getSetting() added. (mvIMPACT_acquire.h) - mvIMPACT::acquire::Statistics::formatConvertTime_s added. (mvIMPACT_acquire.h) - Class mvIMPACT::acquire::BasicDeviceSettings added. This acts as a base class (mvIMPACT_acquire.h) for mvIMPACT::acquire::CameraSettingsBase and contains the features, that are available for all interface layouts. BUGS FIXED: - 'mvIMPACT::acquire::ComponentList::size' and 'OBJ_GetElementCount' did return the (mvDeviceManager-lib) number of reserved elements instead of the number of elements actually valid and allocated. - Sporadic crashes when leaving full screen mode. (wxPropView) - Serial write function is working again. (clsermv-lib) (Bug introduced in version 1.12.49) - Makefiles now also work on Linux distributions with complex Linux version string. (low level mvHYPERION driver, Linux) 14.03.2012 1.12.57 CHANGED BEHAVIOUR: - As the mvIMPACTAcquire_Cognex_Adapter-lib is shipped and build as part of mvIMPACT (all shipped MSI-based packages) Acquire it will now use the global mvIMPACT Acquire version number. UPDATES: - Internal optimizations. (all shipped packages) NEW FEATURES: - Support for increment from GenICam XML float nodes added. (mvBlueCOUGAR-lib) - cfShouldBeDisplayedAsEnumeration added to interface. (mvPropHandling-lib) BUGS FIXED: - A feature selecting others that itself was an enumeration and did not contain any (wxPropView) translation dictionary entries could cause crashes. - Some missing files added to mvHYPERION Linux drivers again. (all shipped Linux driver packages for mvHYPERION devices) (Bug introduced in version 1.12.51) 08.03.2012 1.12.56 NEW FEATURES: - Initial version of mvIMPACT::acquire::RequestFactory added. (mvIMPACT_acquire.h) BUGS FIXED: - Correctly links against GenApi runtime version 2.3.0 now. (mvBlueCOUGAR-lib) - RGB GEV pixel formats are handled correctly again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.12.54) - The last value of a selected pixel histogram range was not drawn. (wxPropView) - Wrong clipping in line profile plots. Connecting lines from points outside of the (wxPropView) plot window were drawn not from the virtual intersection point of the line, but from the lower/upper range of the plot window. 06.03.2012 1.12.55 CHANGED BEHAVIOUR: - 'DelphiSample' removed(deprecated). (all shipped MSI-based packages) NEW FEATURES: - New sample added to all packages: 'GenICamInterfaceLayout'. (all shipped packages) - 32-bit CameraLink communication libraries will be installed on 64-bit versions of (all shipped 64-bit MSI-based packages with CameraLink support) Windows according to the CameraLink Specification 2.0 now. BUGS FIXED: - The samples 'Callback' and 'Callback_C' have incorrectly been installed into the (all shipped 32-bit MSI-based packages) 'SingleCaptureMasterSlave' sub-folder. - The line pitch reported by returned by requests requested in 'Trial' mode was not (mvBlueCOUGAR-lib) always correct for mvBlueLYNX-X devices. - DirectShow device registration via command line is working again. (DirectShow_acquire.ax) 01.03.2012 1.12.54 CHANGED BEHAVIOUR: - Devices operated in interface layout 'dilGenICam' will return (mvBlueCOUGAR-lib) 'DMR_EXECUTION_PROHIBITED' when trying to store a setting while streaming is active now, as the settings stored that way do not contain all the required data. - In rare cases where the device string identifier reported by the GenTL producer does (mvBlueCOUGAR-lib) change at runtime, this is now correctly recognised by the consumer. NEW FEATURES: - Initial version with GEV 2.0 support. Kernel- and User Mode drivers might NOT be (mvTLIClientGigE-lib) mixed, thus either both modules must belong to a package with a version 1.12.53 or (mvGigECapture.sys, version 2.0.0.34) older or to a package with a version 1.12.54 or newer. - Added support for mvBlueCOUGAR-XD devices. (mvTLIClientGigE-lib) (mvDeviceConfigure) - If there is more data to display than the system can handle, paint events will be (wxPropView) skipped on Windows now(see 1.12.26 for a similar change for Linux). - NIC Setup hints added. (mvGigEConfigure) BUGS FIXED: - mvHYPERION-SDI: Mono formats work again. (mvHYPERIONfg-lib) - In rare cases when sending more than 256 requests to the driver at the same time not (mvBlueFOX-lib) all these requests have been processed and returned. This then could result in unexpected capture errors. - New FPGA file for mvBlueFOX-MLC added. This introduces a change on the external I2C (mvBlueFOX-lib) bus. SCL stretching during and after the I2C_ACK is now possible. (FPGA version: 46). 23.02.2012 1.12.53 CHANGED BEHAVIOUR: - Some min/max/resize items added to various dialogs. (wxPropView) - The property grid will consume all screen space available when the analysis tab and (wxPropView) the image display are switched off. - New FPGA file for mvBlueFOX-MLC added. This introduces a different SCL bus stretching (mvBlueFOX-lib) (FPGA version: 45). UPDATES: - Migration to version 2.3.0 of the GenApi runtime. (mvBlueCOUGAR installer) BUGS FIXED: - Setting the dark current filter mode to 'Calibrate' with a Mono8 input format could (all shipped packages) result in crashes after all images used for calibration have been captured. (Bug introduced in version 1.12.8) 15.02.2012 1.12.52 CHANGED BEHAVIOUR: - New FPGA file for mvBlueFOX-MLC added. This introduces a different external I2C bus (mvBlueFOX-lib) timing(FPGA version: 44). NEW FEATURES: - Initial version with basic GEV 2.0 support. Work in progress. (mvTLIClientGigE-lib) BUGS FIXED: - mvBlueFOX devices do no longer report an error after updating the firmware. (mvBlueFOX-lib) (Bug introduced in version 1.12.32) - Flash update mvHYPERION grabber. (mvDeviceConfigure) 02.02.2012 1.12.51 BUGS FIXED: - RotaryDecoder digital input signal list corrected. (mvHYPERIONfg-lib) - Binning mode for mvBlueFOX-202b is working properly now. (mvBlueFOX-lib) - mvBlueFOX devices with a firmware version smaller than 36 can be initialised again. (mvBlueFOX-lib) (Bug introduced in version 1.11.52) 27.01.2012 1.12.50 CHANGED BEHAVIOUR: - The auto negotiation algorithm for the optimal GEV packet size will only select (mvTLIClientGigE-lib) values which are a multiple of 4 now as some cameras did send test packets even if they were not capable of streaming data with other packet sizes. BUGS FIXED: - SD signal resolution corrected. (mvHYPERIONfg-lib) - Data transfer related issues with mvBlueFOX-1xx devices (CCD) on some operating (mvBlueFOX-lib) systems. FPGA version 89(0x59). (Bug introduced in version 1.12.32(FPGA version 87(0x57)) - New FPGA file for mvBlueFOX-2xx (CCD) devices added. This fixes a footer error at (mvBlueFOX-lib) small exposure times(FPGA version: 36). 16.01.2012 1.12.49 CHANGED BEHAVIOUR: - The interface header file 'DirectShowAcquire.h' is no longer installed to (all shipped MSI-based packages) '%TARGET_DIR%\DSImpactAcquire\Include' but to '%TARGET_DIR%\ThirdPartySWBindings\DirectShow\Include'. This might force you to modify your makefiles during rebuilds. BUGS FIXED: - CapturePin and associated property dialog is working again. (DirectShow_acquire.ax) - Bitmap files stored with 'SingleCaptureStorage' on 64-bit versions of Linux could not (SingleCaptureStorage.cpp) be loaded with any other application. - Camera format Bayer packed: CL-Camera description copy and export corrected. (mvHYPERIONfg-lib) 03.01.2012 1.12.48 BUGS FIXED: - Internal GP-OUT handler did only update the first GP-OUT. (mvTITANfg-lib) - Wake up from powerstate 3 improved, query for max. request objects corrected (mvHYPERION2.sys, version 2.1.33.41) - Devices operated in interface layout 'dilGenICam' or 'dilGeneric' not supporting a (DirectShow_acquire.ax) writeable 'OffsetX', 'OffsetY' 'Width' or 'Height' property can be used now when the AOI is not touched by an application. 21.12.2011 1.12.47 CHANGED BEHAVIOUR: - Driver is build with DDK 7600 now and requires a newer version of the WDF coinstaller (mvBlueFOX2.sys, version 1.0.3.4) (1.9). Installations that did NOT use Merge Modules and did integrate the kernel driver into a private setup routine must change the name of the WdfCoInstaller-DLL (was: WdfCoInstaller01001.dll for 32-bit and WdfCoInstaller01005.dll for 64-bit, became WdfCoInstaller01009.dll for both platforms) and the name of the *.cat-file (was: 'mvBlueFOX2_.cat', became: 'mvBlueFOX2.cat'). - Matrix multiplication order in 'ColorTwist' filter reversed. Only the 'ColorTwist' (all shipped packages) matrix provides a 4th column now. When enabled, this will be used as an overall offset for the resulting matrix. BUGS FIXED: - The internal format converter did not remove the 'BayerParity' attribute from buffers (all shipped packages) that (after the conversion) did no longer contain Bayer data. - mvBlueFOX-x05 devices sometimes used a wrong frame rate after switching on/off (mvBlueFOX-lib) binning related features. Also flash signals could be triggered randomly when changing the binning parameters. 07.12.2011 1.12.46 CHANGED BEHAVIOUR: - Classes renamed: mvIMPACT::acquire::GenICam::Device became (mvIMPACT_acquire_GenICam.h) mvIMPACT::acquire::GenICam::DeviceModule, mvIMPACT::acquire::GenICam::Interface became mvIMPACT::acquire::GenICam::InterfaceModule. - Property 'ColorTemperature' removed from list 'WhiteBalanceSettings-. This (all shipped packages) feature never served any purpose. NEW FEATURES: - Wrapper code to access features from the 'SystemModule' and the 'InterfaceModule' (mvIMPACT_acquire_GenICam.h) module of the GenICam GenTL Producer added. - The interface list is also updated when calling 'InterfaceUpdateList' from the (mvBlueCOUGAR-lib) 'System' module now. - A capture setting can be dropped onto the property grid now. This will load an apply (wxPropView) this setting automatically. - The description strings of all enum entries will be appended to the features doc (mvBlueCOUGAR-lib) string now. BUGS FIXED: - 'full tree' mode is working again. (wxPropView) (Bug introduced in version 1.12.33) - Incorrect log message('BUG detected in interface handling...') removed. (mvBlueCOUGAR-lib) - Updating the device list via DMR_UpdateDeviceList or (mvBlueCOUGAR-lib) mvIMPACT::acquire::DeviceManager::updatedeviceList will also invalidate the limits of 'mvBlueCOUGAR/GenTL/System/InterfaceSelector'. - mvBlueFOX-x00w devices did use an incorrect minimal width and height. (mvBlueFOX-lib) 29.11.2011 1.12.45 NEW FEATURES: - Spin control editors in the property grid will contain an additional slider now. This (wxPropView) behaviour can be switched off under 'Settings -> Property Grid'. - Command line interface added. (mvIPConfigure) - New features added to 'ColorTwist' filter(EXPERIMENTAL! SUBJECT TO CHANGE!) (all shipped packages) BUGS FIXED: - DirectShow access is also possible for devices using interface layout 'dilGenICam' (DirectShow_acquire.ax) and these devices define a category 'TriggerControls'. - Packages carry a digital signature again. (all shipped MSI-based packages) (Bug introduced in version 1.12.41) - 'ColorTwist' filter works correctly with pixel format 'ibpfRGBx888Planar' now. (all shipped packages) 22.11.2011 1.12.44 CHANGED BEHAVIOUR: - When leaving a spin editor using the TAB key the new property value will be applied (wxPropView) instead of the previous one now. - Default value of the the property (all shipped packages) '/ImageProcessing/WhiteBalance' changed from 'Daylight' to 'User1'. NEW FEATURES: - 'Driver Properties' page added to property grid control. (wxPropView) - mvIMPACT::acquire::Device::deviceDriverFeatureList function added as well as (mvDeviceManager-lib) TDMR_DeviceInfoType::dmdithDeviceDriver. (mvIMPACT_acquire.h) BUGS FIXED: - mvBlueFOX-x00w: Fixed Exposure difference overlapped/non overlapped mode when AOI (mvBlueFOX-lib) width was smaller than 700 pixels. - mvBlueFOX-x02d: Fixed update issues with AEC/AGC. Increased minimal exposure time (mvBlueFOX-lib) because of a sensor specific bug. - mvBlueFOX-x02b: Fixed update issues with AEC/AGC. (mvBlueFOX-lib) - Device discovery information was not fully refreshed for GEV devices after a call to (mvTLIClientGigE-lib) 'IFUpdateDeviceList' if a device has been detected previously and data in the discovery acknowledge differed from a previous call. 17.11.2011 1.12.43 NEW FEATURES: - DirectShow access is also possible to devices using interface layouts different from (DirectShow_acquire.ax) 'dilDeviceSpecific'. - 64-bit integer property support added to property interface. (DirectShow_acquire.ax) 16.11.2011 1.12.42 DEPRECATED API CODE: - The function DMR_GetDeviceInfo has been declared deprecated. Use DMR_GetDeviceInfoEx (mvDeviceManager-lib) instead. CHANGED BEHAVIOUR: - mv-icon is used by windows created by library now. (mvDisplay-lib) - in full screen mode there is no more flickering when moving the mouse pointer (wxPropView) - Red and blue component flipped for 'idpfBGR101010Packed_V2' and (mvBlueCOUGAR-lib) 'ibpfBGR101010Packed_V2' in order to be compliant with the upcoming PFNC. (mvDisplay-lib) (wxPropView) NEW FEATURES: - Function 'DMR_GetDeviceInfoEx' added as well as 'mvIMPACT::acquire::Device::isInUse'. (all shipped packages) wxPropView will show device usage information in the device driver information dialog(F8) now. BUGS FIXED: - Some UNICODE related issues(wrong string conversions). (wxPropView) - Some invalid 64 integer to string conversions. (wxPropView) (mvPropHandling-lib) (mvVirtualDevice-lib) - The legacy GCGetPortURL function did always return 0 for the size of the URL. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.36) - Data sync. @ 40MHz improved for mvBlueFOX-MLC205x devices. (mvBlueFOX-lib) 15.11.2011 1.12.41 UPDATES: - 'LinearInterpolation' Bayer conversion filter execution speed improved on all (all shipped packages) platforms except 32-bit Windows. - Improved property grid in NeuroCheck 6 interface. (all shipped MSI-based packages) CHANGED BEHAVIOUR: - Default request count reduced to 6 for mvBlueLYNX-X devices. (mvBlueCOUGAR-lib) BUGS FIXED: - Reset behaviour of trigger_controller() improved. (mvHYPERIONfg-lib) - LUT wizard did crash in case the 'LUTSelector' feature was read-only. (wxPropView) - Internal IP address to string handling did not correctly handle endianess. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.38) (Linux only) 03.11.2011 1.12.40 BUGS FIXED: - 'IOStatesAtExposureStart' is working now. (mvBlueFOX-lib) 02.11.2011 1.12.39 DEPRECATED API CODE: - The features '/ImageProcessing/Saturation' and all the features (all shipped packages) within that list have be declared deprecated. Applications should use the color twist matrix under '/ImageProcessing/ColorTwist' or(for GenICam SFNC compliant devices) the '/Camera/GenICam/ColorTransformationControl' features instead. NEW FEATURES: - 64-bit integer parameters can be handled by method objects now. (mvPropHandling-lib) (wxPropView) - Splitter added between the property grid and the tool tip window. (wxPropView) - Progress dialog added for file upload and download wizard. (wxPropView) - NeuroCheck 6 interface for mvBlueCOUGAR and mvBlueFOX devices added to all MSI based (all shipped MSI-based packages) packages. - Saturation wizards added. (wxPropView) - 'mvIMPACT::acquire::ImageProcessing::setSaturation' function added. (mvIMPACT_acquire.h) - 'ColorTwist' filter supports pixel format 'ibpfRGBx888Planar' now (all shipped packages) BUGS FIXED: - 'DSGetBufferInfo' when asked for the size of the 'BUFFER_INFO_PIXELFORMAT_NAMESPACE' (mvTLIClientGigE-lib) info did return 4 instead of 8 as required by the spec. - Sometimes ending a continuous acquisition resulted in a 'AcquisitionStop', (wxPropView) 'AcquisitionStart' and 'AcquisitionStop' command being send to a GenICam device instead of a single 'AcquisitionStop' command. (Bug introduced in version 1.12.11) - Storing image sequences on Linux on slower machines did result in the first image (wxPropView) of the sequence being stored times. (Bug introduced in version 1.12.26) - Property grid popup menus are working again. (wxPropView) (Bug introduced in version 1.12.38) - AbortRequest(), Capture-IRP handling improved to avoid any side effects with (mvHYPERION2.sys, version 2.1.31.39) function DpsForIsr() 27.10.2011 1.12.38 NEW FEATURES: - Support for large(64KB) EEPROM access via I2C added for mvBlueFOX-MLC devices added. (mvBlueFOX-lib) - Support for 'IOStatesAtExposureStart' property added. (mvBlueFOX-lib) BUGS FIXED: - Value strings starting with one or more whitespace characters have not been processed (wxPropView) correctly for properties specifying the 'cfShouldBeDisplayedAsList' flag. 26.10.2011 1.12.37 UPDATES: - Migration to version 1.3 of the GenICam GenTL spec. (mvTLIClientGigE-lib) BUGS FIXED: - Crash whenever a wxPropView >= 1.12.33 detected a mvBlueFOX or mvBlueCOUGAR-X with (wxPropView) a driver < 1.12.33. (Bug introduced in version 1.12.33) 25.10.2011 1.12.36 CHANGED BEHAVIOUR: - Spin-editors will accept a ',' as a floating point value separator as well now. (wxPropView) BUGS FIXED: - Some request info properties had the 'cfWriteAccess' flag set. (mvBlueCOUGARLocal-lib) - Tapsort filter RGB24-2Tap corrected. (mvHYPERIONfg-lib) - Digital input mapping to internal signals corrected. (mvHYPERIONfg-lib) 19.10.2011 1.12.35 NEW FEATURES: - Buffers returned from a mvBlueLYNX-X will have a timestamp now. (mvTLIClientGigE-lib) - 'PaddingX' property added. (mvVirtualDevice-lib) - Nonstandard RGB24-2Tap CL-Mode added. (mvHYPERIONfg-lib) - Enhanced transfer error handling added. (mvSIGMAfg-lib) BUGS FIXED: - When the network interface with a MATRIX VISION MAC address was shut down opening (mvTLIClientGigE-lib) a mvBlueLYNX-X resulted in a crash. - 8 mono buffers with a pitch divisible by 4 and a width different from the pitch can (mvDisplay-lib) be displayed correctly now as well as 422 packed YUV and packed RGB formats that use X-padding. 17.10.2011 1.12.34 CHANGED BEVAVIOUR: - Some additional I2C device addresses block for access from external applications (mvBlueFOX-lib) NEW FEATURES: - 'mvGevInterfaceLinkSpeed' added to nodemaps of 'System-module' and (mvTLIClientGigE-lib) 'Interface-module'. - Link speed and MTU of the adapter a device has been located on is displayed now. (mvIPConfigure) - Further improved filter driver when packet data does arrive out of order. Immediate (mvGigECapture.sys, version 1.1.10.33) resend will be disabled in LAG configuration now. BUGS FIXED: - mvBlueFOX devices of type 202b and 202d can be operated again. (mvBlueFOX-lib) (Bug introduced in version 1.12.33) 12.10.2011 1.12.33 DEPRECATED API CODE: - Windows 2000 version of the GigE Vision filter driver has been declared deprecated. No new versions will be created but version 1.1.7.30 will remain stay as part of the driver installation for Windows 2000. CHANGED BEVAVIOUR: - mvBlueCOUGAR-X devices in device specific interface mode do no longer automatically (mvBlueCOUGAR-lib) set the black level to the lowest possible value by default. NEW FEATURES: - Properties containing binary data can be edited with a simple hex editor now. (wxPropView) - "Automatically Reconnect To Unused Devices" option added(see 'Usage hints' under (wxPropView) 'About'). - "Show Method Execution Errors" option added. (wxPropView) - I2CControl features added for mvBlueFOX-MLC202 devices. (mvBlueFOX-lib) - 'UserEEPROMSize' property added. (mvBlueFOX-lib) - Filter driver behaviour improved when payload packets arrive out of order. (mvGigECapture.sys, version 1.1.9.32) - Resend statistics will also be updated if resend is switched off now. (mvGigECapture.sys, version 1.1.9.32) BUGS FIXED: - Sometimes the first image of a sequence was returned with a footer error for some (mvBlueFOX-lib) CMOS versions of the mvBlueFOX-MLC. - Negative values for 64-bit integer properties can be read and written using the (wxPropView) property grid now. - Crashes when closing a device in 'full tree' mode. (wxPropView) (Bug introduced in version 1.12.29) - New FPGA file for mvBlueFOX-MLC200 devices added. This fixes a pixel clock related (mvBlueFOX-lib) issue at 40 MHz pixel clock. - When storing string property values that did contain either '<' or '>' the resulting (mvPropHandling-lib) XML file was not well-formed. 30.09.2011 1.12.32 NEW FEATURES: - 'Find Feature' dialog allows logical OR of multiple search strings now. (wxPropView) - Usage hints, keyboard shortcuts and command line options can be found by pressing (wxPropView) 'F1' now. BUGS FIXED: - GevSCPx and GevSCDAx where accessed in reverse order. Because of that some devices (mvTLIClientGigE-lib) refused to open a streaming channel. - Devices that require 'TLParamsLocked' to be set for 'SingleFrame' acquisition mode (mvBlueCOUGAR-lib) can be operated in 'SingleFrame' mode now. - Potential crash when 'Continuous Recording' was active. (wxPropView) (Bug introduced in version 1.12.22) - 'The firmware of this device could not be verified' after updating an mvBlueCOUGAR-X (mvDeviceConfigure) to a FW-version larger or equal than 1.2.0. 28.09.2011 1.12.31 NEW FEATURES: - Properties 'SystemSettings/FeaturePollingEnable' and (mvBlueCOUGAR-lib) 'SystemSettings/FeaturePollingInterval_ms' added. BUGS FIXED: - Missing newly introduced '$MVIMPACT_ACQUIRE_DIR/common/System/Linux/version.inc' (all shipped packages for Unix/Linux systems) added to TGZ archives. - Error messages about invalid access to certain HDR related feature upon init for (mvBlueFOX-lib) mvBlueFOX-202dG, mvBlueFOX-M202dG and mvBlueFOX-ML/IGC202dG devices. - Serial port communication open/close improved. (mvHYPERION2.sys, version 2.1.31.39) (mvHYPERION.sys, version 1.0.50.52) 21.09.2011 1.12.30 NEW FEATURES: - mvHYPERION-HD-SDI: Software supported version of interlaced handling added. (mvHYPERIONfg-lib) - Support for mvBlueFOX-ML/IGC202aG devices added. (mvBlueFOX-lib) 02.09.2011 1.12.29 CHANGED BEVAVIOUR: - If a device supports the 'BalanceWhiteAuto' feature, this feature is switched off in (mvBlueCOUGAR-lib) 'DeviceSpecific' interface layout for backward compatibility reasons. NEW FEATURES: - Second tool bar added as when working with small horizontal display resolutions not (wxPropView) not all the tools where visible. - 'Find Feature' dialog added(e.g. reachable via CTRL+F). (wxPropView) 31.08.2011 1.12.28 CHANGED BEHAVIOUR: - 'Line Profile' plot split into 'Horizontal Line Profile' and 'Vertical Line Profile'. (wxPropView) - Gain limits adjusted for CCD versions. mvBlueFOX-12x types: was -6.5 - 30.0, became (mvBlueFOX-lib) -6.48 - 29.7, mvBlueFOX-22x types: was -9.0 - 30.0, became -9.0 - 29.7. NEW FEATURES: - Initial version of GenICam related additional wizards for easier configuration of (wxPropView) LUTControl and FileAccessControl related features. BUGS FIXED: - Sometimes when writing to a property while internally the polling thread was updating (mvBlueCOUGAR-lib) features as well some changes where not forwarded to the device. 25.08.2011 1.12.27 NEW FEATURES: - More merge modules added to MSI based packages. (all shipped MSI based packages) BUGS FIXED: - 'FILTER_INSTALL_PARAMS' in the installers property table can be overwritten from the (mvBlueCOUGAR.msi) outside world now. Please note that overwriting this property will NOT work when (mvBlueCOUGAR-x64.msi) doing a managed installation with elevated privileges as this is not supported by Windows Installer. - SEHException(COM-Context) on some newer i3, i5 and i7 processors when using some of (all shipped packages) the internal processing functions. 24.08.2011 1.12.26 CHANGED BEHAVIOUR: - The maximum number of request objects is 32767 now. Implicitly this was the case (all shipped packages) before, but now this is also reflected by all the properties that allow to influence this value. - 'VB6Sample' removed(deprecated). (all shipped MSI-based packages) - Class 'Root' removed. (mvIMPACT_acquire_GenICam.h) NEW FEATURES: - Support for mvBlueLYNX-X devices added. (mvTLIClientGigE-lib) (mvBlueCOUGAR-lib) - 'FooterCheckEnable' property added. (mvBlueFOX-lib) BUGS FIXED: - Directly starting live acquisition from the command line is working again. (wxPropView) (Bug introduced in version 1.12.11) - On Linux when too much data was send to the display module the application could (wxPropView) lock up. - When closing a mvBlueCOUGAR-X in 'DeviceSpecific' interface layout with (mvBlueCOUGAR-lib) 'TriggerSource' set to 'Software' the next time the device was opened in 'DeviceSpecific' interface layout not all trigger modes seemed to be available (only 'Continuous and 'OnHighExpose'). 16.08.2011 1.12.25 UPDATES: - New FPGA file for mvBlueFOX-MLCxxx devices added. (mvBlueFOX-lib) NEW FEATURES: - 'device' command line parameter does accept '*' as a serial number wildcard now. (wxPropView) BUGS FIXED: - Acquisition mode selection did not work properly with every version of wxWidgets. (wxPropView) - Serial -> MAC Feature is working again. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.17) 11.08.2011 1.12.24 CHANGED BEHAVIOUR: - Device events reported before an event was registered at the device message port will (mvTLIClientGigE-lib) by silently discarded now. - Drivers not supporting the internal 'Update@v' callback for digital input will no (mvDeviceManager-lib) longer report error messages in the log file. (Related to change in 1.11.48) UPDATES: - GEV devices will register their user defined name(if supported and set) as the string (mvBlueCOUGAR-lib) representation of the property mvIMPACT::acquire::Device::deviceID now. NEW FEATURES: - I/O measurement features for mvBlueFOX-2xx and mvBlueFOX-MLCxxx devices added. See (mvBlueFOX-lib) e.g. the class mvIMPACT::acquire::DigitalIOMeasurementControl. BUGS FIXED: - 'OnChanged' callbacks fired as a result of a device event reported by the GenICam (mvTLIClientGigE-lib) GenTL producer could not read the 'new' value of a property but received the previous one. - 'MirrorMode' property is no longer used internally. (DirectShow_acquire.ax) 09.08.2011 1.12.23 NEW FEATURES: - 'ChannelSplit' can handle Bayer data now. (all shipped packages) - Files can be written into properties storing binary data and binary data from a property can be stored into a file when right-clicking on a property in the property (wxPropView) grid. - Started to add 'real' pitch(thus a pitch that is NOT width times bytes per pixel) (all shipped packages) support. - Support for 'Padding X' and 'Padding Y' as specified in the GEV spec. added. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) BUGS FIXED: - Potential deadlock when a GenICam command with read access got executed in parallel (mvBlueCOUGAR-lib) with other threads accessing the GenApi runtime. - Features invalidated by changing others did not accept new values when these were (mvPropHandling-lib) equal to the value the last time this feature was actively read. (Bug introduced in version 1.12.17) - GEV Message channel is set up correctly again. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.3) 02.08.2011 1.12.22 NEW FEATURES: - Primary application switchover support added. (mvTLIClientGigE-lib) BUGS FIXED: - GenICam features which are write-only can be written to now. (mvBlueCOUGAR-lib) - When used with multiple displays to display multiple input channels in parallel (wxPropView) the update for displays receiving data absolutely in parallel could stop resulting in only a single display refreshing data. - Some ports of wxWidgets do not allow to have a window without a close button. When (wxPropView) using this button on the 'monitor image' wxPropView did crash. - When a callback is fired this is handled in a thread save way now. Certain features (wxPropView) could cause a deadlock when a callback was registered before as GUI elements were accessed outside the main thread. - Updating the firmware of a GEV device sometimes did return DMR_INTERNAL_ERROR even (mvDeviceConfigure) if the update was successful. 25.07.2011 1.12.21 DEPRECATED API CODE: - 'C': The functions 'DMR_EventWaitFor' and 'DMR_EventGetData' as well as the struct (all shipped packages) 'EventData'. 'C++': The classes 'EventSubSystem', 'EventWaitResults' and 'EventData'. Please refer to the documentation for replacements. CHANGED BEHAVIOUR: - 'showEvents' and 'se' command line options are no longer supported. (wxPropView) - Sample 'EventHandling' removed(deprecated). (all shipped packages) UPDATES: - 'GVCP_FORCEIP_ALLOW_BROADCAST' added to force IP command for GEV devices. This (mvTLIClientGigE-lib) will allow devices which move into a different subnet during execution of the command to send an acknowledge. - Improved way of reporting errors. Aborted buffers will no longer appear as capture (mvBlueFOX-lib) errors in the log file. 21.07.2011 1.12.20 CHANGED BEHAVIOUR: - 'OnChanged' callback functions signature introduced in version 1.12.18 has been (all shipped packages) changed. NEW FEATURES: - New mode added to 'ChannelSplit' filter: csmExtractSingle. Also the 'ChannelSplit' (all shipped packages) filter interface has been added to the C++ interface now. 14.07.2011 1.12.19 NEW FEATURES: - 'Temporal Noise Histogram' added. (wxPropView) UPDATES: - 'GVCP_DISCOVERY_ALLOW_BROADCAST' added to discovery command for GEV devices. This (mvTLIClientGigE-lib) will allow devices which reside in different subnets to answer discovery requests. - 'Noise Histogram' renamed to 'Spatial Noise Histogram'. (wxPropView) BUGS FIXED: - Crash when working with the 'ChannelSplit' filter in 'Vertical' direction and the (all shipped packages) input format for the filter was either 'ibpfYUV422_UYVY_10Packed' or 'ibpfYUV422_10Packed'. 13.07.2011 1.12.18 NEW FEATURES: - An application can register an 'OnChanged' callback on an arbitrary feature now. See (mvPropHandling-lib) new 'Callback' and 'Callback_C' samples for details or right click on a feature in (mvDeviceManager-lib) wxPropViews property grid and then monitor feature changes in the 'Output' window. (mvIMPACT_acquire.h) (wxPropView) - 'mvGevInterfaceMTU' added to nodemaps of 'System-module' and 'Interface-module'. (mvTLIClientGigE-lib) The interface MTU also internally serves as a boundary for packet size negotiation now which can help in case of a misbehaving NIC driver. BUGS FIXED: - mvBlueFOX-202b and mvBlueFOX-202d devices did use an incorrect minimal width and (mvBlueFOX-lib) height as well as an incorrect increment for the AOI/W and AOI/H parameters. - mvBlueFOX-MLC devices switched on the digital outputs for about 500us during init. (mvBlueFOX-lib) 07.07.2011 1.12.17 UPDATES: - Reduced network traffic. When one feature invalidates one or more other features (mvBlueCOUGAR-lib) these invalidated features will not be queried from the device unless an application re-reads them. - MAC addresses can be build from serial numbers for mvBlueLYNX-M7 and some OEM devices (mvTLIClientGigE-lib) now. BUGS FIXED: - The current state of the digital inputs can be read back again. (mvTITANfg-lib) (Bug introduced in version 1.11.48) (mvSIGMAfg-lib) (mvHYPERIONfg-lib) (mvBlueCOUGARLocal-lib) - Firmware updates for mvBlueCOUGAR-S devices are possible again. (mvDeviceConfigure) (Bug introduced in version 1.11.51) - Retrieving URL strings from a remote device did fail if the URL address was higher or (mvTLIClientGigE-lib) equal 0x80000000, which could be the case if the remote device does support a manifest table. - camera-info-thread startup behaviour improved. (mvHYPERIONfg-lib) 05.07.2011 1.12.16 NEW FEATURES: - 'FlashType' 'VSync' added for mvBlueFOX-MLC202d devices. (mvBlueFOX-lib) - Modifying the 'GevGVCPHeartbeatDisable' feature of a GEV device will also cause the (mvTLIClientGigE-lib) internal heartbeat handling to be updated now. 04.07.2011 1.12.15 BUGS FIXED: - mvHYPERION-HD-SDI, stopping internal camera-info-thread corrected. (mvHYPERIONfg-lib) - mvHYPERION-HD-SDI, connector capabilities corrected. (mvHYPERIONfg-lib) - Potential crash when starting the acquisition did fail and logging was enabled on (mvBlueCOUGAR-lib) 32-bit platforms. 30.06.2011 1.12.14 CHANGED BEHAVIOUR: - Internal sensor update timeout increased in order to address situations where a (mvBlueCOUGARLocal-lib) sensor update was delayed by other tasks. NEW FEATURES: - Custom FPGA files can be selected using the 'CustomFPGAFileSelector' property. (mvBlueFOX-lib) BUGS FIXED: - Starting the acquisition is working again in 'Generic' and 'GenICam' interface (mvBlueCOUGAR-lib) layout. (Bug introduced in version 1.12.11) - Closing multiple mvBlueFOX devices could take a very long time on Linux. (mvBlueFOX-lib) - Camera/TriggerControls/FrameStart/TriggerSource did contain string values 'GP-IN0' (mvBlueCOUGARLocal-lib) and 'GP-IN1' instead of 'Line2' and 'Line3'. 15.06.2011 1.12.13 NEW FEATURES: - x64 version of the kernel mode driver added. This will allow existing 32-bit (mvTITAN_mvGAMMA-x64.msi) applications to run on x64 bit versions of Windows. However this will still NOT allow true x64 applications to run with mvTITAN/mvGAMMA boards. - Generic interface header files added for 'GenICam' interface layout: (all shipped packages) mvIMPACT_acquire_GenICam.h and mvIMPACT_acquire_GenICam_FileStream.h. UPDATES: - New version of the CRT and OpenMP runtimes added. (all shipped MSI based packages) BUGS FIXED: - If the max. value was also the most frequent value, incorrect data was displayed in (wxPropView) the histogram plot. (Bug introduced in version 1.12.9) 08.06.2011 1.12.12 CHANGED BEHAVIOUR: - Acquisition mode 'SingleFrame' is no longer available for GEV devices that don't (wxPropView) support this mode. NEW FEATURES: - Firmware version 1.3.36.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) New features: - Device specific AutoExposure, AutoGain and AutoWhiteBalance with AutoHighlightAOI. - mvAcquisitionMemoryMode: For recording and playback of images. - DigitalGain and DigitalBlackLevel implemented. - UserOutputValueAll implemented. - TimerReset and CounterReset via Command and ResetSource. - Mono12/Mono14 format implemented. Changed behaviour: - GevSCBW unit changed (KByte/s -> KBps). - ChunkSelector Pixelformat -> PixelFormat. - ChunkTimer -> ChunkTimerValue. - ChunkCounter -> ChunkCounterValue. - Default TimerTriggerSource = TimerEnd -> free-running timer. - BlackLevel: Unit is now percent of saturation. Bugs fixed: - Router capability disabled(could lead to network overloads). - Colors of YUV formats are correct now. BUGS FIXED: - Continuous acquisition for mvHYPERION devices is working under wxPropView again. (mvHYPERIONfg-lib) (Bug introduced int version 1.12.11) - 'Capture -> Capture Settings -> Usage Mode' selection is stored and restored when (wxPropView) opening/closing the application. - Update of the internal setting table when working with multiple settings and displays (wxPropView) when loading a setting at runtime was missing. 06.06.2011 1.12.11 DEPRECATED API CODE: - The class mvIMPACT::acquire::SystemBlueCOUGAR has been declared deprecated (mvIMPACT_acquire.h) and will be removed in future versions. Use mvIMPACT::acquire::SystemSettings instead. NEW FEATURES: - 'mvIMPACT::acquire::FunctionInterface::acquisitionStart', (all shipped packages) 'mvIMPACT::acquire::FunctionInterface::acquisitionStop', 'mvIMPACT::acquire::Device::acquisitionStartStopBehaviour', 'DMR_AcquisitionStart' and 'DMR_AcquisitionStop'. - Refactored acquisition mode selection and added support for 'MultiFrame' (wxPropView) acquisition for devices supporting this mode. 01.06.2011 1.12.10 CHANGED BEHAVIOUR: - Increased maximum exposure to 8s for mvBlueFOX-x02b/d(with minimum pixel clock). (mvBlueFOX-lib) - Fixed read back of exposure time to real value. (mvBlueFOX-lib) - Correctly limit exposure time if internal limit reached. (mvBlueFOX-lib) UPDATES: - Merged with current code base(includes some minor fixes). (mvBlueCOUGARLocal-lib) 30.05.2011 1.12.9 CHANGED BEHAVIOUR: - Displayed minimum, maximum, deviation etc. of a histogram plot will only take into (wxPropView) account the current draw window now. The plot will be scaled to the maximum value of that selected draw window. UPDATES: - URL handling improved. (mvTLIClientGigE-lib) BUGS FIXED: - The current state of the digital inputs in 'DeviceSpecific' interface layout can be (mvBlueCOUGAR-lib) read back again. (Bug introduced in version 1.11.48) - mvHYPERION-SDI: Only supported capture pixel formats can be selected now. (mvHYPERIONfg-lib) - Mysterious 'dummy' device does no longer show up on Linux. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.5) - Does no longer crash at startup. (mvIPConfigure) (Bug introduced in version 1.12.5) 20.05.2011 1.12.8 CHANGED BEHAVIOUR: - Linescan mode optimization added to correction filter (dark current and flat field) (mvHYPERIONfg-lib) BUGS FIXED: - Makefile corrected for Linux build (mvHYPERIONfg-lib) 12.05.2011 1.12.7 BUGS FIXED: - Device specific AGC/AEC is available in 'DeviceSpecific' interface layout for (mvBlueCOUGAR-lib) mvBlueCOUGAR-X devices with firmware versions 1.2.9 and greater now. - Potential crashes when calling 'DSClose'. This e.g. happened when closing a device. (mvTLIClientGigE-lib) (Bug introduced in version 1.12.5) - Deadlock in case an invalid device handle was passed to 'DevGetPort', (mvTLIClientGigE-lib) 'DevGetNumDataStreams', 'DevGetDataStreamID'. 'DevOpenDataStream', 'DevGetInfo', 'TLIMV_DevSetParam', 'TLIMV_DevGetInterfaceParam' or 'TLIMV_DevSetInterfaceParam'. (Bug introduced in version 1.12.4) - Remote device events can be received after a device was disconnected and then (mvTLIClientGigE-lib) reconnected again. (Bug introduced in version 1.12.5) 10.05.2011 1.12.6 NEW FEATURES: - Support for mvBlueFOX-ML/IGC202dG, Rev >= 0.92 (mvBlueFOX-lib) - In-place version of Tap sort filter added. (all shipped packages) - New property added to system setting list to influence memory usage behaviour of (all shipped packages) image-processing filters. CHANGED BEHAVIOUR: - Serial port, polling period changed in serialwrite() (mvHYPERION2.sys, version 2.1.30.38) (mvHYPERION.sys, version 1.0.49.51) - Firmware error handling added, mvHYPERION devices should have at least firmware (mvHYPERIONfg-lib) version 57. Older firmware are not recommended. 03.05.2011 1.12.5 CHANGED BEHAVIOUR: - Sensor FIFO is reseted when 'imageRequestReset' is called now. (mvBlueFOX-lib) - GEV test packet validation enabled. (mvTLIClientGigE-lib) UPDATES: - Number of default debug writer tags increased from 8 to 16 for all USB and GEV (all shipped packages) devices. - Some gcc 4.5 related crashes fixed by moving around some code and changing the name (all shipped packages for Unix/Linux systems) of some internal classes. BUGS FIXED: - Missed frames calculation correctly handles wrap-around conditions of the frame (mvBlueFOX-lib) counter now. - Settings without a hierarchy table can be restored correctly from the Windows (all shipped MSI based packages) Registry again. (Bug introduced in version 1.12.4) 28.04.2011 1.12.4 NEW FEATURES: - For GigE Vision compliant devices mvIPConfigure can be launched from the 'Set ID' (mvDeviceConfigure) dialog now. - Setting hierarchies can be stored and restored as part of a load/save setting (all shipped packages) operation now. XML based settings stored with the setting hierarchy included can only be restored using mvIMPACT Acquire packages with version 1.12.4 or greater. BUGS FIXED: - When an initialised GEV device was unplugged or stopped communicating with an (mvTLIClientGigE-lib) application all other devices could no longer stream data to this application properly. 19.04.2011 1.12.3 CHANGED BEHAVIOUR: - When attaching a user supplied buffer to a request the internal buffer previously (all shipped packages) attached to this request will be unlocked, which will result in memory being freed in most cases. When removing the user supplied buffer later the internal request memory will be re-allocated automatically. - Prepared the GenICam GenTL producer to support other transport layer technologies. (mvTLIClientGigE-lib) The reported transport layer type of the system module now e.g. will be 'Mixed'. This later might affect applications that assume only GEV devices devices to be reported by the library. Therefore an application should then check the TLTYPE value carefully. BUGS FIXED: - Writing binary data to a string property and then reading it back could result in (mvPropHandling) in incorrect data if the size of the original binary buffer was not a multiple of 4 and one of the last 3 bytes did contain a value larger than 127. - mvIMPACT::acquire::Request did always report either a single ChunkCounterValue or a (mvIMPACT_acquire.h) single ChunkTimerValue property no matter how many timers or counters have actually been part of the chunk data. 12.04.2011 1.12.2 UPDATES: - Internal migration to IPP 7.0.3. (all shipped packages) CHANGED BEHAVIOUR: - AbortAllRequests, exception handling improved. (mvHYPERION2.sys, version 2.1.29.37) NEW FEATURES: - Function 'OBJ_GetBinaryBufferMaxSize added to 'C'-interface and (all shipped packages) 'mvIMPACT::acquire::PropertyS::binaryDataBufferMaxSize' added to 'C++'-interface. BUGS FIXED: - Incorrect black level calibration offset for certain exposure times for mvBlueFOX-x05 (mvBlueFOX-lib) devices. - Potential blue screen (BSOD) when re-requesting lost data packages. (mvGigECapture.sys, version 1.1.7.30) 05.04.2011 1.12.1 NEW FEATURES: - Support for mvBlueFOX-ML/IGC202d and mvBlueFOX-ML/IGC205 devices added. (mvBlueFOX-lib) - HDR control features added for mvBlueCOUGAR-Xx00w devices in device specific (mvIMPACT_acquire.h) interface layout. 25.03.2011 1.12.0 CHANGED BEHAVIOUR - Functions and classes that have been declared deprecated for some time now have (mvIMPACT_acquire.h) been removed from the C/C++ interface. This will not break existing binaries, but (mvDeviceManager.h) will force you to change your code during rebuilds when deprecated code was used by your application. A list of functions that have been removed and their replacement can be found in the device drivers manual under 'C/C++ developer -> Porting existing code'. - mvHYPERION-SDI: Auto-detect camera mode improved. (mvHYPERIONfg-lib) - Analysis plot colors better represent the actual color channels of the image buffer (wxPropView) now. NEW FEATURES: - x64 version of the kernel mode driver added. This will allow existing 32-bit (mvDELTA_mvSIGMA-x64.msi) applications to run on x64 bit versions of Windows. However this will still NOT allow true x64 applications to run with mvDELTA/mvSIGMA boards. - Initial version of the color twist filter published under image processing. (all shipped packages) - Configuration dialog now uses the same property grid control as wxPropView. (DirectShow_acquire.ax) - mvHYPERION-SDI: Additional mvHDCam info stuff added. (mvHYPERIONfg-lib) - Support for mvHDCam output modes Raw2K, YUV, RawTwoInOne, Raw12bit added. (mvHYPERIONfg-lib) - Error handling improved for 3G-SDI video input. (mvHYPERIONfg-lib) BUGS FIXED: - When a driver internally did modify a property that did specify the (wxPropView) 'cfShouldBeDisplayedAsList' flag the current editor in the property grid was deselected. - Displaying and storing frames belonging to a recorded sequence does work again. (wxPropView) (Bug introduced in version 1.11.49) - When working with hardware LUTs in interpolated mode with interpolation mode set to (all shipped packages) 'Linear' the final value of the calculated LUT was not always correct. - When the read-only property selected in the grid became writable (e.g. because the (wxPropView) live mode was stopped and this property can only be modified when the device doesn't stream data) the editor could only be reactivated if selecting a different property and then the current one again. - Previous driver versions did ignore value changes smaller than 0.01 for GenICam float (mvBlueCOUGAR-lib) properties. - Driver based controller for AEC and AGC did not work after a long period with (all shipped packages) almost no light. 16.03.2011 1.11.53 BUGS FIXED: - HRT-controller reset added when programming a new controller sequence. Only HRTC's (mvHYPERION2.sys, version 2.1.28.36) modifying digital output signals have been affected. (low level mvHYPERION2 driver, Linux) 15.03.2011 1.11.52 NEW FEATURES: - 'TestMode' 'vdtmEmptyMonoBuffer' added. (mvVirtualDevice-lib) - Initial version of 'SystemSettings/MemoryInit' features added. No interface (all shipped packages) published so far. Meant for debugging purposes only. - Final version of 'MotorFocus' features added and published via class (mvBlueFOX-lib) 'mvIMPACT::acquire::MotorFocusControl'. - Class mvIMPACT::acquire::CameraDescriptionSDI added (mvIMPACT_acquire.h) - The double linescan mode(BayerPacked) demosaic algorithms can deliver (mvHYPERIONfg-lib) ibpfRGBx888Planar directly now. This removes one internal conversion for certain setups. BUGS FIXED: - In 'Generic' and 'GenICam' interface layout when queuing the first buffer and calling (mvBlueCOUGAR-lib) 'TriggerSoftware' directly afterwards in rare cases the command was send to the device before the streaming has been started resulting in the trigger command being ignored. CHANGED BEHAVIOUR: - 'OBJ_Execute' or 'mvIMPACT::acquire::Method::call' do no longer accept callers who (mvPropHandling-lib) pass too many parameters. Now the amount of parameters must exactly match what is expected or an 'PROPHANDLING_WRONG_PARAM_COUNT' error will be returned and an appropriate exception might be generated. - Content descriptor of SDI camera descriptions changed from 'SDICamera' to 'SDI'. (mvHYPERIONfg-lib) Because of this change existing camera descriptions will no longer be detected until these files are adapted by changing the file name and the 'contentDescriptor' and 'name' attribute in the root 'Proplist' node of the file. - Visibility of propertylists in the videocapture dialogbox is now based on wxWidgets. (DirectShow_acquire) 09.03.2011 1.11.51 BUGS FIXED: - Vertical Scrollbar of wxPropView is working again. (mvDisplay-lib) (Bug introduced in version 1.11.50) NEW FEATURES: - Properties 'mvIMPACT::acquire::Info::recommendedListsForUIs' added. (all shipped packages) - Bayer images can be treated as mono(single channel) images now by histogram, line (wxPropView) and intensity plots. - Initial version of 'MotorFocus' features added to driver. However these are still (mvBlueFOX-lib) subject to change thus so far are meant for evaluation purposes only. - Support for mvBlueFOX-MLC205 devices added. (mvBlueFOX-lib) CHANGED BEHAVIOUR: - Property grid view mode 'Multiple Settings View' became 'Standard View'. Old (wxPropView) 'Standard View' removed. - Some properties renamed: - 'CustomDescriptionFilename' became 'CustomDescriptionFileName' (mvBlueCOUGAR-lib) - 'PseudoFilenameProperty' became 'PseudoFileNameProperty' (mvVirtualDevice-lib) - 'Filename' became 'FileName' in all lists within 'LUTs'. (all shipped packages) 03.03.2011 1.11.50 NEW FEATURES: - Properties 'mvIMPACT::acquire::Request::imageWidthTotal' and (all shipped packages) 'mvIMPACT::acquire::Request::imageHeightTotal' added. BUGS FIXED: - If one or more features selected by another one did contain values which where out (mvBlueCOUGAR-lib) of bounds for the feature of the device to update, an update from a setting could be incomplete. - 'TLParamsLocked' feature is set correctly according to the current streaming state (mvBlueCOUGAR-lib) in 'Generic' and 'GenICam' interface layout again. (Bug introduced in version 1.11.48) - Chunk buffers that did not contain any data(just leader and trailer) will no longer (mvBlueCOUGAR-lib) be returned with result 'rrFrameIncomplete'. (mvTLIClientGigE-lib) - HW-SPI-Access improved to support the automatic camera parameter detection under (mvHYPERIONfg-lib) Linux as well. (low level mvHYPERION2 driver, Linux) - Installation of version 2.1.1 of the GenApi runtime is working correctly now. (mvBlueCOUGAR driver, Linux) (Bug introduced in version 1.11.42) - Internal data transfer improved. Now the corresponding routine called from the (mvHYPERIONfg-lib) FPGA-processor waits until all data has been transferred completely. 23.02.2011 1.11.49 NEW FEATURES: - Automatic camera parameter detection added for mvHYPERION-SDI devices. The driver (mvHYPERIONfg-lib) now tries to scan and detect the parameters of the connected SDI devices. If the camera description 'SDICameraAutoDetect' is used then these detected parameters will be used for image requests. - Support for mvHYPERION-CLb hardware revision 3.xx added. (mvHYPERIONfg-lib) (mvHYPERION2.sys, version 2.1.27.35) (low level mvHYPERION2 driver, Linux) CHANGED BEHAVIOUR: - Pending calls to 'imageRequestWaitFor' will return with 'DMR_WAIT_ABANDONED' (all shipped packages) now whenever 'imageRequestReset' is called from a different thread. - Optimized driver for very high frame rates. This will improve the overall max. frame (mvBlueFOX-lib) rate that can be achieved without losing frames but will consume more physical memory when increasing the request count for the driver instance of a specific device. 10.02.2011 1.11.48 CHANGED BEHAVIOUR: - All 'Update@v' functions to update the state of the digital inputs of a device have (all shipped packages) been removed. When reading the value of a digital input it will be updated automatically to reflect its current state. In wxPropView to re-read the state of a digital input right-click on the property and select 'Force Refresh' from the menu. NEW FEATURES: - The 32-bit version of the VisionPro adapter is correctly recognized on 64-bit (all shipped MSI-based packages) versions of Windows running a 64-bit mvIMPACT Acquire driver. - Ancillary data support added for Hyperion-SDI grabber. Now if connecting a (mvHYPERIONfg-lib) mvHDCam-SDI with anc_data support the grabber could read data like serial number or device ID independent from serial connection. - Error handling improved if onboard-processor could not start. (mvHYPERIONfg-lib) BUGS FIXED: - mvBlueCOUGAR-P/mvBlueLYNX-M7 devices can be used in 'DeviceSpecific' interface layout (mvBlueCOUGAR-lib) again. (Bug introduced in version 1.11.28) - When an 'onRead' callback was attached to a property storing more than a single value (mvPropHandling-lib) reading any other value than the one at index 0 did cause a crash. - Multiple file access to driver instance improved. Sometimes if working with serial (mvHYPERION2.sys, version 2.1.26.34) connection in one process and the capture stuff in a different process the system could stop if closing the driver access (closefile). - Start/stop trigger sometimes resulted in halve the frame rate if enabling UserAoi in (mvHYPERIONfg-lib) the camera settings. 25.01.2011 1.11.47 CHANGED BEHAVIOUR: - Start/stop trigger mode: Previous versions did delay incoming stop trigger signals (mvHYPERIONfg-lib) which resulted in a reduced overall trigger frequency. Now this delay has been removed. BUGS FIXED: - FPGA <-> processor communication improved. More than one task/process/thread can (mvHYPERION2.sys, version 2.1.25.33) access digital I/O related functions simultaneously now. - Previous version did allow to set negative camera AOI parameters. (mvHYPERIONfg-lib) 19.01.2011 1.11.46 NEW FEATURES: - Support for multiple displays and multiple capture settings added. (wxPropView) - BayerPacked format added to camera description. (mvHYPERIONfg-lib) - linescan start condition can be combined with FVAL. This mode is needed to avoid any (mvHYPERIONfg-lib) color mismatch for cameras which support Bayer packed mode. (mvHYPERION2.sys, version 2.1.24.32) UPDATES: - Devices that report register addresses that don't fit into the 32-bit specified (mvBlueCOUGAR-lib) by the GEV standard can be used now(without the features using invalid addresses). - Improved behaviour for devices not using the standard category names for chunk features if the device does at least support 'ChunkWidth'. - Integer and float properties which where not readable at the time of opening the (mvBlueCOUGAR-lib) device can be created now. - Categories that do not contain any accessible feature will no longer created. (mvBlueCOUGAR-lib) BUGS FIXED: - In 'DeviceSpecific' interface layout the first image was taken with the default (mvBlueCOUGAR-lib) exposure time instead of the selected one if the exposure mode was set to 'cemStandard' (Bug introduced in version 1.11.24) - In rare case assigning a value too large or too small to a floating point property (wxPropView) could cause the application to crash if the properties min/max value did have a lot of digits after the comma. - Crashes when working with GEV devices supporting chunk mode under .NET. Memory (mvIMPACT_acquire.h) corruptions where reported by the garbage collector in Request::Dispose. (Bug introduced in version 1.11.29) - Display can deal with images in 'ibpfMono12Packed_V2' that have an odd width now. (mvDisplay-lib) - Binning is working correctly now for mvBlueFOX-x02xx devices. (mvBlueFOX-lib) 07.01.2011 1.11.45 CHANGED BEHAVIOUR: - Renamed mvIMPACT::acquire::Request::getChunkCounter to (mvIMPACT_acquire.h) mvIMPACT::acquire::Request::getChunkCounterValue and mvIMPACT::acquire::Request::getChunkTimer to mvIMPACT::acquire::Request::getChunkTimerValue. BUGS FIXED: - Installation of version 2.1.1 of the GenApi runtime is working correctly now. (mvBlueCOUGAR.msi) (Bug introduced in version 1.11.42) (mvBlueCOUGAR-x64.msi) - Under certain conditions image requests could be lost. Then not every image request (mvBlueFOX-lib) actually did result in an image being captured and transmitted by the camera. - Automatic installation of the filter driver is working again. (mvBlueCOUGAR-x64.msi) (Bug introduced in version 1.10.86) 21.12.2010 1.11.44 CHANGED BEHAVIOUR: - EXPERIMENTAL: Some internal threads reserve smaller stack sizes now. (mvBlueCOUGAR-lib) (Windows only) (mvTLIClientGigE-lib) - In 'Generic' interface layout trying to load or save a setting will report (mvBlueCOUGAR-lib) DMR_FEATURE_NO_AVAILABLE now as load/save operations for settings are not supported anyway. NEW FEATURES: - 2 new samples added to Linux packages: 'CaptureToUserMemory_C' and (all shipped packages for Unix/Linux systems) 'ContinuousCapture_C'. - Log files can be moved around in the file system and still be viewed with (all shipped packages) mvLogFileViewer.html without changing files.mvloglist afterwards. - Import of *.raw images with pixel formats 'ibpfBGR888Packed', (wxPropView) 'ibpfBGR101010Packed_V2', 'ibpfYUV444_UYVPacked', 'ibpfYUV444_UYV_10Packed', 'ibpfYUV444Packed' and 'ibpfYUV444_10Packed' improved. BUGS FIXED: - Import of *.raw images with Bayer data is working now. Storing RAW Bayer images did (wxPropView) create files with a ':' in the file name, which is an illegal character for file names. - Internal controller handling improved. This will improve the support for area scan (mvHYPERIONfg-lib) cameras in trigged applications. 16.12.2010 1.11.43 NEW FEATURES: - Extended line valid(LVAL) signal feature added. The user can extend the camera AOIs (mvHYPERION.sys, version 1.0.48.50) width only if the cameras horizontal pixels per line are not compatible with the (mvHYPERION2.sys, version 2.1.23.31) mvHYPERIONs alignment restrictions. (low level mvHYPERION and mvHYPERION2 driver, Linux) - VectorScope plot can deal with YUV422Packed formats now. (wxPropView) 10.12.2010 1.11.42 CHANGED BEHAVIOUR: - Property 'SystemSettings/Camera/AdvancedImageInfo' removed. Use (mvBlueFOX-lib) 'Camera/AdvancedOptions' with 'daoImageAverage' in the setting instead. NEW FEATURES: - New pixel formats introduced: 'ibpfBGR101010Packed_V2', 'ibpfYUV444_UYVPacked', (all shipped packages) 'ibpfYUV444_UYV_10Packed', 'ibpfYUV444Packed', 'ibpfYUV444_10Packed'. - Linux version can deal with ibpfBGR888Packed now. (wxPropView) - Rotation filter supports 'ibpfRGBx888Planar' now. (all shipped packages) - New property 'AdvancedOptions' added to 'Camera' list of each setting. (mvBlueFOX-lib) - 3G-SDI YUV422_10bit support added. (mvHYPERIONfg-lib) - 3G-SDI Rawmode support added, 10 or 12 bit. (mvHYPERIONfg-lib) - TriLevelSync added for synchronizing external devices. (mvHYPERIONfg-lib) - On-board flash memory can now be selected by the driver (user or default). (mvHYPERIONfg-lib) UPDATES: - Migration to version 2.1.1 of the GenApi runtime. (mvBlueCOUGAR installer) BUGS FIXED: - For formats 'ibpfRGB101010Packed' - 'ibpfRGB161616Packed' the channel split filter (all shipped packages) did crash in 'vertical' mode. - When a setting was stored while 'AcquisitionMode' was set to 'Continuous' and (mvBlueCOUGAR-lib) streaming was active the current state of 'TLParamsLocked' was stored as well, which in 'Generic' interface layout could result in certain streaming related properties being read-only after opening the device even if streaming was not active. - Internal conversions from ibpfMono8 to ibpfRGBx888Planar could cause crashes if the (all shipped packages) physical buffer size of the source buffer was larger than the width times the line pitch of this buffer. - For formats 'ibpfRGB101010Packed' - 'ibpfRGB161616Packed' a correct RGB value is (wxPropView) displayed in the right corner of the status bar now. - Images with a width that is not divisible by 4 are stored correctly to a file now. (wxPropView) (Windows only) - Properties that specify the 'cfAllowValueCombinations' that only had a 'None'(0) (wxPropView) entry in their translation dictionary did cause wxPropView to crash. These properties will be read-only in wxPropView now. - Sometimes the trigger controller didn't switch synchronously with the corresponding (mvHYPERIONfg-lib) request. 01.12.2010 1.11.41 NEW FEATURES: - Support for Bayer versions of 'ibpfMono12Packed_V2' added. (all shipped packages) BUGS FIXED: - Continuous calls to 'DMR_Init' and 'DMR_Close' did cause an error code -2100 (mvBlueFOX-lib) after roughly 500 iterations. (Linux only) - Restart trigger improved if waiting on all possible trigger events (acquisitionStart, (mvHYPERIONfg-lib) frameStart, frameStop). - In case of frameStart trigger event when aborting a capture sequence with (mvHYPERIONfg-lib) 'imageRequestReset' all following requests will return with timeout error. - DeviceVersion is now reported correctly. (mvHYPERIONfg-lib) 30.11.2010 1.11.40 CHANGED BEHAVIOUR: - All the 'Pseudo'-features have been moved into a sub-category 'PseudoFeatures' (mvVirtualDevice-lib) NEW FEATURES: - After resetting or re-connecting a device all GenICam related features will be (mvBlueCOUGAR-lib) invalidated now. BUGS FIXED: - Disconnecting or resetting the device while no requests where being processed (mvBlueCOUGAR-lib) resulted in the data streams not being closed properly. - mvBlueCOUGAR-S devices can be used for streaming in 'DeviceSpecific' interface again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.37) - On Linux mvIPConfigure is working again. The application does no longer directly (mvIPConfigure) link to the mvTLIClientGigE-lib. 26.11.2010 1.11.39 NEW FEATURES: - HDR support added for mvBlueFOX-x02d devices added. (mvBlueFOX-lib) UPDATES: - Slightly improved read/write access to GigE Vision devices(no longer queries the CCP (mvTLIClientGigE-lib) register before the actual read/write access). BUGS FIXED: - When 'ImageDestination/PixelFormat' was different from 'idpfAuto' or 'idpfRaw' and (all shipped packages) the device itself did change the pixel format randomly(thus did not transfer what was requested) the format converter did perform a conversion based on incorrect assumptions. - In rare cases disconnecting a device while a continuous stream was running could (mvBlueCOUGAR-lib) result in crashes. - Working with external trigger: triggerstart/stop corrected. Some combinations of (mvHYPERIONfg-lib) previous driver versions and firmware > f57 this triggermode resulted in incorrect pixel data. This behaviour is now corrected and all combinations of trigger are supported again. 25.11.2010 1.11.38 CHANGED BEHAVIOUR: - Increased 'PoolSize' registry parameter from 256 MB to 640 MB for Cognex adapter. (all shipped MSI-based packages) This will fix certain timeout issues when running devices with high resolutions via the mvIMPACTAcquire_Cognex_Adapter-lib. Please note that this memory is NOT automatically consumed unless truly needed. - The data type of the property mvIMPACT::acquire::TriggerControl::triggerDelayAbs_us (mvHYPERIONfg-lib) has been changed from int to float in order to be compatible with other device (mvIMPACT_acquire.h) drivers. BUGS FIXED: - When an GenTL function was called without calling 'GCInitLib' and 'TLOpen' before (mvTLIClientGigE-lib) this did initialise the 'System' module by accident. - Calling 'DSFlushQueue' with 'ACQ_QUEUE_UNQUEUED_TO_INPUT' or 'ACQ_QUEUE_ALL_TO_INPUT' (mvTLIClientGigE-lib) or 'DSStopAcquisition' with 'ACQ_QUEUE_ALL_TO_INPUT' could result in buffers being returned without fresh data. - mvIMPACT Acquire drivers < 1.10.55 can be initialised again. (wxPropView) (Bug introduced in version 1.11.37) - Line profile in YUV422 modes did contain incorrect 'V' values for all even pixels (wxPropView) of a line. - Image request control mode 'trial' is working again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.35) - In device specific legacy trigger mode the selection of the corresponding digital (mvBlueCOUGAR-lib) input is working with mvBlueCOUGAR-S. (Bug introduced in version 1.11.37) - Request Info properties 'FrameNr' and 'CameraOutputUsed' now report valid data. The (mvHYPERION2.sys, version 2.1.22.30) 'FrameNr' property reports now a channel specific counter. This counter will be (mvHYPERIONfg-lib) incremented for every request handled by the FPGA-processor. - Working with external trigger events: Combinations of StartTrigger and DelayLines now (mvHYPERIONfg-lib) works correctly. Previous version did restart the trigger controller during each request and under certain conditions trigger events will had been missed. - Medium CameraLink modes RGB30 and RGB36 corrected. Not all ways of switching between (mvHYPERIONfg-lib) CameraLink modes Base and Medium where working correctly. 23.11.2010 1.11.37 DEPRECATED API CODE: - The interface layout 'Generic' has been declared deprecated. Please use 'GenICam' (all shipped packages for GigE Vision devices) instead, which offer a more flexible access to GenICam devices. CHANGED BEHAVIOUR: - The default interface layout became 'GenICam' if supported by the connected device. (wxPropView) NEW FEATURES: - Firmware version 1.2.9.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This fixes the following issues: - line debouncer is working now - mvBlueCOUGAR-X100wG/C devices did start up with the horizontal mirror enabled. - Fixed caching issues in some command registers(e.g. UserSetLoad and UserSetSave) - New GenICam description file for mvBlueCOUGAR-S devices added(version 3.0.0) (mvBlueCOUGAR installer) This might not be completely backward compatible but will introduce SFNC compliant names for categories and fixes some minor issues. UPDATES: - Now 15 instead of 5 different trigger modes can be handled by the device specific (mvBlueCOUGAR-lib) interface layout. BUGS FIXED: - Potential crash during firmware update via mvDeviceConfigure. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.35) - Devices that did offer more than 1 root category with names similar to a standard (mvBlueCOUGAR-lib) category(e.g. DeviceControl and MyDeviceControl) in the GenICam XML file could not be initialised. - In device specific legacy trigger mode the selection of the corresponding digital (mvBlueCOUGAR-lib) input is working with mvBlueCOUGAR-X firmware versions 1.2.x or greater now. - Property 'TriggerSource' did not become invisible when switching to (mvBlueCOUGAR-lib) 'TriggerInterface' 'Advanced'. - Deadlock when an mvBlueFOX is disconnected during a running acquisition when the (mvBlueFOX-lib) 'ImageRequestTimeout_ms' property is set to 0. 08.11.2010 1.11.36 NEW FEATURES: - Experimental version of a low-light exposure mode for mvBlueFOX-x02d devices added. (mvBlueFOX-lib) (subject to change, use with care) BUGS FIXED: - In AGC mode the default upper gain limit is the maximum gain allow again and not 0. (mvBlueFOX-lib) (Bug introduced in version 1.11.13) (mvBlueCOUGAR-lib) - Connected devices are displayed again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.20) (mvTLIClientGigE-lib) (mvGigEConfigure) - The update of visibilities of properties in the 'TransportLayerControl' list or the (mvBlueCOUGAR-lib) 'FileAccessControl' list did not work correctly in 'DeviceSpecific' interface layout and 'Generic' interface layout. - In 'DeviceSpecific' interface layout the access mode of 'mvGevSCBWControl' and (mvBlueCOUGAR-lib) 'mvGevSCBW' was not updated correctly with respect to the current state of 'TLParamsLocked'. - If a device is accessible via more than one interface, it is displayed on every (mvBlueCOUGAR-lib) matching adapter now(before it was only listed at the first one the device has been (mvGigEConfigure) detected on. 05.11.2010 1.11.35 NEW FEATURES: - Added support for 'BUFFER_INFO_IMAGEPRESENT', 'BUFFER_INFO_IMAGEOFFSET', (mvTLIClientGigE-lib) 'BUFFER_INFO_DELIVERED_IMAGEHEIGHT', 'BUFFER_INFO_DELIVERED_CHUNKPAYLOADSIZE' and 'BUFFER_INFO_CHUNKLAYOUTID' to the 'DSGetBufferInfo' function. - Added support for mvBlueFOX-MLC202bG and mvBlueFOX-MLC202bC devices. (mvBlueFOX-lib) UPDATES: - Further improved detection of lost device access. When the connection to a device is (mvBlueCOUGAR-lib) lost while streaming or after streaming has been on and is then reconnected the device can either continue streaming or will report an error status during connection problems. BUGS FIXED: - Calling DSFlushQueue with 'ACQ_QUEUE_ALL_TO_INPUT' could result in buffers being (mvTLIClientGigE-lib) placed in the input buffer pool more than once, which could result in deadlocks during cleanup. - Calling 'DSStopAcquisition' with 'ACQ_STOP_FLAGS_KILL' and an active filter driver (mvTLIClientGigE-lib) could result in a deadlock. 04.11.2010 1.11.34 NEW FEATURES: - Image request control mode 'trial' implemented. (mvV4L-lib) BUGS FIXED: - Calling 'DSGetBufferInfo' with 'BUFFER_INFO_SIZE_FILLED' returns the correct value (mvTLIClientGigE-lib) in chunk mode now. - Capture errors from CMOS versions of the mvBlueFOX-1xx and mvBlueFOX-M1xx when (mvBlueFOX-lib) switching digital I/Os during image transfer. 03.11.2010 1.11.33 NEW FEATURES: - Capture into a user supplied buffer is working now. (mvV4L-lib) BUGS FIXED: - 'TLIMV_IFSetInterfaceParam' will be exported as all the other function under 32 (mvTLIClientGigE-lib) Windows now. This will fix an error message being reported under 32-bit versions of Windows when starting mvIPConfigure. 02.11.2010 1.11.32 NEW FEATURES: - mvBlueFOX-MLC FPGA Version 0x1e: Supports I2C on IO connector (mvBlueFOX-lib) - Firmware version 1.2.1.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This firmware introduces massive changes in feature names and a lot of new features like - ChunkMode - Extended Counter/Timer functionality - New acquisition and trigger modes However this firmware version is NOT fully backward compatible. If in doubt please contact MATRIX VISION. Because of these changes it can also not be guaranteed that older device driver will run in 'DeviceSpecific' interface layout when operated with devices using a firmware version greater than 1.2.x thus updating the driver on these systems is also highly recommended. - Source code for mvIPConfigure added to MSI based installer (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) 28.10.2010 1.11.31 CHANGED BEHAVIOUR: - After a PnP arrival event the digital outputs are restored to their previous state. (mvBlueFOX-lib) NEW FEATURES: - Calculation of missed frames based on frame counter in Statistics/LostImagesCount. (mvBlueFOX-lib) Please note that e.g. when doing single snaps and the sensor runs in autotrigger mode this will currently result in the lost image counter to increase so don't use this parameter as a proof that frames have actually been missed. This depends on the point of view and the application. - Support for ibpfMono10 and ibpfMono16 added. (mvV4L-lib) BUGS FIXED: - In 'DeviceSpecific' interface layout certain advanced trigger configurations could (mvBlueCOUGAR-lib) result in inconsistent device updates. - In 'DeviceSpecific' interface layout modifying the HW-LUT did not always update the (mvBlueCOUGAR-lib) camera HW. - In 'GenICam' interface layout Loading settings did not always update all features. (mvBlueCOUGAR-lib) 25.10.2010 1.11.30 UPDATES: - Internal migration to IPP 6.1.6. (all shipped packages) NEW FEATURES: - Support for extended chunk format added. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) BUGS FIXED: - Devices that do not support chunk mode can be opened again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.28) - Certain Linux distribution could cause crashes during clean up work. (mvPropHandling-lib) (Bug introduced in version 1.11.16) 19.10.2010 1.11.29 CHANGED BEHAVIOUR: - Packed Bayer conversion mode changed, now this mode packs the pixels and (all shipped packages) interpolates every second one. BUGS FIXED: - User AOI works with TabXGeometry 1X8 now. (mvHYPERIONfg-lib) (mvTITANfg-lib) - Firmware update via mvDeviceConfigure does terminate correctly again for mvBlueCOUGAR (mvBlueCOUGAR-lib) and mvBlueLYNX-M7 devices again. (Bug introduced in version 1.11.20) 14.10.2010 1.11.28 NEW FEATURES: - 12 bit acquisition mode added to mvHYPERION-HD-SDI. (mvHYPERIONfg-lib) - Firmware version 49 for mvBlueFOX devices added. This will add motor focus control (mvBlueFOX-lib) related features. UPDATES: - Enhanced chunk processing added. All chunk features will be part of the request info (mvBlueCOUGAR-lib) now and will reside in a sublist 'Info/ChunkData' of each request object. BUGS FIXED: - The 64-bit Linux build of the GenICam GenTL producer did use an incorrect structure (mvTLIClientGigE-lib) alignment resulting in some registers returning an incorrect value when accessing them via a GenApi nodemap. - Fixed initialising of PulseStartConfiguration. Previous versions did program the (mvHYPERIONfg-lib) rotary decoder interface but not the default behaviour(trigger input signal). 08.10.2010 1.11.27 NEW FEATURES: - Additional trigger delay added. Now it is possible to set also a trigger delay in (mvHYPERIONfg-lib) lines. The property delayAbs_usec is not affected from this new property. For working with this new delay feature a mvHYPERION-CLm/CLf firmware upgrade to version 61 is required. UPDATES: - Improved detection of lost device access. If a device is no longer responding the (mvTLIClientGigE-lib) 'State' property will be set to 'Absent'. When a device is responding again all (mvBlueCOUGAR-lib) communication channels will be re-created thus the device can be used again without the need to close and re-open it. - Request error handling improved, now error strings will be logged instead of error (mvHYPERIONfg-lib) codes. - Further improved enhanced device discovery for misconfigured devices. A new detection (mvTLIClientGigE-lib) mode has been added to mvIPConfigure. Switching it on and off enables and disables (mvIPConfigure) the usage of limited broadcasts for the device discovery. If a device is not visible during 'normal' device discovery switching on limited broadcasts might help. 07.10.2010 1.11.26 UPDATES: - Uncompressed versions of all the GenICam XML files processed will be written to (mvBlueCOUGAR-lib) a default directory automatically. - Channel link reset improved if working with full CameraLink cameras. (mvHYPERION2.sys, version 2.1.21.29) BUGS FIXED: - Potential memory corruption when changing from 'normal' operation to 'chunk' mode (mvBlueCOUGAR-lib) without changing the image resolution and then capturing data into a driver allocated buffer that previously contained 'normal' image data. - In interface layout 'dilGeneric' and 'dilGenICam' the 'ChunkModeActive' feature is (mvBlueCOUGAR-lib) no longer switched off automatically, when opening a device that supports the chunk mode. 06.10.2010 1.11.25 NEW FEATURES: - 'AcquisitionStart' trigger added. Now it is possible to control acquisition start (mvHYPERIONfg-lib) independent from the 'FrameStart' trigger. - Trigger counter read out added for 'FrameStart' and 'AcquisitionStart' trigger. (mvHYPERIONfg-lib) (mvHYPERION2.sys, version 2.1.20.28) CHANGED BEHAVIOUR: - Previous trigger overlap mode(restart trigger mode) must be defined until now with (mvHYPERIONfg-lib) 'FrameStart' and 'FrameStop' trigger. This change is not compatible with older versions. Now both trigger lists must hold the same trigger signal definitions to enable this restart mode. UPDATES: - Improved device discovery introduced in version 1.11.23 does no longer take more (mvTLIClientGigE-lib) time. It's even faster than all previous versions now. (mvBlueCOUGAR-lib) 30.09.2010 1.11.24 NEW FEATURES: - Rotary encoder interface added to the pulsestartconfiguration list. (mvHYPERIONfg-lib) - Additional Bayer conversion algorithms added to support enhanced raw modes. This (all shipped packages) special line scan acquisition modes are only available for certain line scan cameras. BUGS FIXED: - The x64 version of the DirectShow interface could connect to devices when running (DirectShow_acquire.ax) the capture application with elevated access rights only on some 64-bit versions of Windows. - wxPropView can be compiled with wxWidgets version smaller than 2.7.1 again. (wxPropView) - Potential crashes at start-up when wxPropView has been compiled with wxWidgets 2.6.x (wxPropView) on Debian. - Small memory leak when constantly opening an closing a device. (mvBlueCOUGAR-lib) 24.09.2010 1.11.23 CHANGED BEHAVIOUR: - Discovery of misconfigured GEV devices improved. Now devices e.g. using a persistent (mvTLIClientGigE-lib) IP address connected to an adapter that resides in a different net can be discovered (mvBlueCOUGAR-lib) as well. However this increases the device enumeration time per adapter. - Increased 'PoolSize' registry parameter from 64 MB to 256 MB for Cognex adapter. (all shipped MSI-based packages) This will fix certain timeout issues when running devices with high resolutions via the mvIMPACTAcquire_Cognex_Adapter-lib. Please note that this memory is NOT automatically consumed unless truly needed. 17.09.2010 1.11.22 BUGS_FIXED: - Changes from version 1.11.6 improved. Now internal multiplexer data is only (low level mvHYPERION driver, Linux) updated if it has changed. This load behaviour was changed in version 1.11.6. (mvHYPERION.sys, version 1.0.47.49) 10.09.2010 1.11.21 NEW FEATURES: - Property mvIMPACT::acquire::Device::bayerConversionMode published. (mvIMPACT_acquire.h) This will allow full access to the new Bayer conversion mode added in version 1.11.9. UPDATES: - Amount of internal threads needed to operate a mvBlueCOUGAR-S device reduced. (mvTLIClientGigE-lib) (mvBlueCOUGAR-lib) BUGS FIXED: - Device interface IP address is displayed correctly again. (mvIPConfigure) (Bug introduced in version 1.11.20) 03.09.2010 1.11.20 CHANGED BEHAVIOUR: - All GenTL MATRIX VISION specific features have been renamed to start with a (mvTLIClientGigE-lib) leading 'mv' now. - 'TNetworkProtocol' is no longer part of the interface as it has not been used anyway. (mvDriverBaseEnums.h) - Power over CameraLink is now be enabled during driver start. (mvHYPERION.sys, version 1.0.46.48) NEW FEATURES: - New pixel format introduced: ibpfBGR888Packed. (all shipped packages) - New binning modes for mvBlueFOX-x05 devices added. (mvBlueFOX-lib) - New interface layout added: 'dilGenICam'. (mvBlueCOUGAR-lib) - Saving an interface layout using selectors is possible in 'dilGenICam' now. (mvBlueCOUGAR-lib) - Functions 'OBJ_GetDisplayName', 'OBJ_GetSelectedFeatures' and (all shipped packages) 'OBJ_GetSelectingFeatures'added to 'C'-interface and 'mvIMPACT::acquire::Component::displayName', 'mvIMPACT::acquire::Component::selectedFeatureCount', 'mvIMPACT::acquire::Component::selectingFeatureCount', 'mvIMPACT::acquire::Component::selectedFeatures', 'mvIMPACT::acquire::Component::selectingFeatures', 'mvIMPACT::acquire::Component::selectedFeature' and 'mvIMPACT::acquire::Component::selectingFeature' added to 'C++'-interface. wxPropView will now allow to use either the 'real' name of the component or the display name (if defined) to display a feature in the property grid. Also 'selector <-> selectee' relationships can be displayed now. - Some internal changes. This version is now a fully compliant GenICam GenTL consumer (mvBlueCOUGAR-lib) according the GenICam GenTL spec. version 1.2. - Firmware version 1.1.43.1 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) BUGS FIXED: - Selecting 'Assign temp. IP' from the context menu of the device list is working (mvIPConfigure) again. (Bug introduced in version 1.11.17) - In rare cases certain nodes in a devices XML file could result in (mvBlueCOUGAR-lib) features not being updated correctly or even in enum features being assigned a different value for no reason when the TLParamsLocked node was accessed during start and stop of streaming. - If set request timeout to 0 ms and working with a frametrigger then sometimes the (mvHYPERIONfg-lib) driver could not be closed. (mvHYPERION2.sys, version 2.1.19.27) 29.07.2010 1.11.19 NEW FEATURES: - Buffer nodemap and port access related functions for buffer module implemented. (mvTLIClientGigE-lib) - Firmware version 1.1.40.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This adds support for mvBlueCOUGAR-X124 devices, fixes various minor bugs regarding network related topics and allows the use of mvBlueCOUGAR-X devices under National Instruments LabVIEW with the Vision Acquisition Software (VAS). BUGS FIXED: - Calling DSFlushQueue did not always clear all internal buffer flags e.g. leaving some (mvTLIClientGigE-lib) buffers marked as 'queued' afterwards. - x64 and ppc_6xx Linux builds are working again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.17) - mvBlueCOUGAR-X devices with an old firmware not supporting HW-LUT features are (mvBlueCOUGAR-lib) running at full speed in 'DeviceSpecific' interface mode again. (Bug introduced in version 1.11.13) - 'Flat field filter' is working correctly again on multi-core systems. (all shipped packages) (Bug introduced in version 1.11.6 with the introduction of OpenMP) 27.07.2010 1.11.18 DEPRECATED API CODE: - mvIMPACT::acquire::ImageProcessing::mirrorMode has been declared deprecated and will (mvIMPACT_acquire.h) be removed in future versions. See 'C++ developers -> Porting existing code' in the device manual for replacements. UPDATES: - Timing improved for mvBlueFOX-2x devices. (FPGA version) NEW FEATURES: - Driver information can be listed via F12 now. (wxPropView) - RAW image files containing one of the supported mvIMPACT Acquire pixel formats can (wxPropView) be imported now. - The mirror filter can be applied to individual channels of the image now. Each (all shipped packages) channel can have a different mirror setting. See class mvIMPACT::acquire::ImageProcessing for details. - Improved new logging mechanism. (all shipped packages) - 'ChannelSplit' filter added to image processing chain. This filter can be used to (all shipped packages) convert multi-channel images into a mono format of the corresponding bit depth with all channels of the image re-arranged as planes. The interface of this filter is under development still and might change in future releases. - mvBlueCOUGAR-X firmware is part of the Linux driver package as well now. (all shipped Linux builds of the mvBlueCOUGAR driver package) - Decoder reset added for mvHYPERION-SDI during device open. (mvHYPERION2.sys, version 2.1.18.26) - Remaining SFNC features added to Device, Interface and System nodemaps. - Support for 'ACQ_STOP_FLAGS_KILL' in DSStopAcquisition added. BUGS FIXED: - In planar or packed YUV test mode images with a height that was not a multiple of 4 (mvVirtualDevice-lib) could result in the creation of incorrect test data. - Synchronisation of medium channels improved. (low level mvHYPERION driver, Linux) - MDL_PAGES_LOCKED check added before calling MdlUnlockPages. (mvHYPERION2.sys, version 2.1.18.26) - OnCancelReadWrite improved. (mvHYPERION2.sys, version 2.1.18.26) - Power over CameraLink will be switched on/off correctly for different system power (mvHYPERION2.sys, version 2.1.18.26) states. 14.07.2010 1.11.17 CHANGED BEHAVIOUR: - The stream channel selector is only available when the device offers at least one (mvTLIClientGigE-lib) stream now. - Some return values changed from 'GC_ERR_ERROR' to 'GC_ERR_IO' where appropriate. (mvTLIClientGigE-lib) - 'PORT_INFO_MODEL' returns a unique name per module now. (mvTLIClientGigE-lib) - Checking for sufficient disk space will be done AFTER selecting the components to be (all shipped MSI based packages) installed. - 'LastResult' property of the code generation section became read-only. (mvBlueCOUGAR-lib) NEW FEATURES: - mvDELTA, mvSIGMA, mvTITAN and mvGAMMA devices will return an increasing frame number (mvSIGMAfg-lib) now. (mvTITANfg-lib) - Support for error events added. (mvTLIClientGigE-lib) - mvBlueFOX devices will work on a NEC-USB 3.0 xHCI controller now. (mvBlueFOX-lib) - Firmware version 1.1.30.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This version includes various minor bug fixes, adds new trigger sources and an initial version of a programmable AND/OR matrix as well as a possibility to reset the internal timestamp via a digital input which will allow to sync. several cameras with an external signal. - New file format for log output added. Files with the *.mvlog extension can be viewed (all shipped packages) using mvLogFileViewer.html(There is a shortcut in the programs menu on Windows) now. UPDATES: - Chapters about installation and logging in manuals. (all shipped packages) BUGS FIXED: - Under XP and Windows 2000 drivers could only be installed while the system time (mvBlueFOX.msi) during installation was within the time span KMCS certificate used to sign the kernel (mvBlueFOX-x64.msi) drivers was valid. (mvHYPERION.msi) (mvHYPERION-x64.msi) (mvTITAN_mvGAMMA.msi) (mvDELTA_mvSIGMA.msi) - The grid property currently selected did not become invisible in the tree control (wxPropView) even if it visibility did change (e.g. because of a change in the user experience control box). - Multiple load/unload operations on the module with some interface function calls in (mvTLIClientGigE-lib) between could result in crashes. - When a device with no streaming channels was detected during a call to (mvTLIClientGigE-lib) 'IFUpdateDeviceList' an internal exception was raised and the enumeration of the devices did stop thus not every device was detected. - The module names of the 'Device' Module and the remote device have been interchanged. (mvTLIClientGigE-lib) - The schema version tag of the remote device URL contains a sub minor number now as required by the GenTL spec 1.2. - 'DEVICE_INFO_ACCESS_STATUS' always returns the correct value now. (mvTLIClientGigE-lib) - 'DSFlushQueue' with 'ACQ_QUEUE_ALL_DISCARD' behaves as defined in the GenTL spec. (mvTLIClientGigE-lib) now. - 'DSGetInfo' with STREAM_INFO_NUM_DELIVERED, STREAM_INFO_NUM_UNDERRUN, (mvTLIClientGigE-lib) STREAM_INFO_NUM_STARTED, STREAM_INFO_NUM_ANNOUNCED, STREAM_INFO_NUM_QUEUED, STREAM_INFO_NUM_AWAIT_DELIVERY or STREAM_INFO_PAYLOAD_SIZE did return incorrect data type information. - The visibility of Bayer conversion related properties will be updated depending on (all shipped packages) current image format again. (Bug introduced in version 1.11.6) - various samples as well as wxPropView can be compiled using gcc 4.0 or greater again (all shipped packages) (Bug introduced in version 1.11.6) - Potential crash when closing the log-configuration dialog for a certain logger. (mvDeviceConfigure) - The result of the firmware update is displayed correctly again when updating the (mvDeviceConfigure) firmware of an mvBlueCOUGAR device. (Bug introduced in version 1.11.12) 05.07.2010 1.11.16 DEPRECATED API CODE: - mvIMPACT::acquire::OutputSignalGeneratorBlueDevice::canInvertExposeActiveSignal, (mvIMPACT_acquire.h) mvIMPACT::acquire::OutputSignalGeneratorBlueDevice::isExposeActive, mvIMPACT::acquire::OutputSignalGeneratorBlueDevice::isExposeActiveSignalInverted and mvIMPACT::acquire::OutputSignalGeneratorBlueDevice::makeExposeActive have been declared deprecated and will be removed in future versions. See 'C++ developers -> Porting existing code' in the device manual for replacements. CHANGED BEHAVIOUR: - Some status information properties moved from statistics list to info list. (mvHYPERIONfg-lib) NEW FEATURES: - Firmware version 47 for mvBlueFOX devices added. This will add improved detection (mvBlueFOX-lib) for mvBlueFOX-MLC devices with an empty EEPROM. - mvHYPERION2 kernel module control parameter added to handle special load behaviour. (low level mvHYPERION2 driver, Linux) Current module version supports handling of PoCL with this control parameter. - mvIMPACT::acquire::TriggerControl::triggerDelayAbs_us support for mvBlueCOUGAR (mvIMPACT_acquire.h) devices added. - SDI camera description added for mvHYPERION-SDI boards. This camera description also (mvHYPERIONfg-lib) supports enhanced YUV422_10Packed destination formats. - Additional status info properties added for mvHYPERION-SDI boards. (mvHYPERIONfg-lib) - 'Force Refresh' option added to the context menu of the property grid. If a property (wxPropView) internally defines some method to update its value(e.g. a counter value) calling this function will assign the current value to the property. - Intensity plot added. (wxPropView) UPDATES: - Linux version of mvBlueFOX driver makes use of libusb 1.0.8 now. (mvBlueFOX-lib) - USB transfer compliant with Linux kernel versions 2.6.33 and higher now. (mvBlueFOX-lib) - Updated mvSDK driver package. Changes in mvsigma.sys. IRP_MJ_CLEANUP dispatch (mvSIGMA, version 4.1.13.50) function added. - Migration to version 1.2 of the GenICam GenTL spec. (mvTLIClientGigE-lib) BUGS FIXED: - AEC/AGC with active AutoControlMode 'Standard' is working again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.13) - Translation lookaside buffer(P55 compatible) bugfix added, mvHYPERION-CLm did (low level mvHYPERION2 driver, Linux) generate 32-bit address headers if detecting a 32-bit physical DMA address (highpart = 0). - When the property selected in the grid became read-only (e.g. because the live mode (wxPropView) was started and this property can only be modified when the device doesn't stream data) the editor did disappear and could only be reactivated if selecting a different property and then the current one again. - Timeout handling corrected. Next request after a timeout condition was also reported (mvHYPERIONfg-lib) with timeout error(mvHYPERION-CLm/CLf only). - Average pixel value in Histogram plots in raw Bayer modes was 4 times too small. (wxPropView) 15.06.2010 1.11.15 NEW FEATURES: - Firmware version 46 for mvBlueFOX devices added. This will add enhanced support (mvBlueFOX-lib) for mvBlueFOX-MLC devices. BUGS FIXED: - Translation lookaside buffer(P55 compatible) bugfix added, mvHYPERION-CLm did (mvHYPERION2.sys, version 2.1.17.25) generate 32-bit address headers if detecting a 32-bit physical DMA address (highpart = 0). 11.06.2010 1.11.14 NEW FEATURES: - Firmware version 1.1.19.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) Bugs fixed: - Sometimes the mvBlueCOUGAR-X failed to boot. (Bug introduced in firmware version 1.1.18.0) 10.06.2010 1.11.13 CHANGED BEHAVIOUR: - Property mvIMPACT::acquire::Device::autoLoadSettingsOrder renamed to (mvIMPACT_acquire.h) mvIMPACT::acquire::Device::autoLoadSettingOrder. This might force you to change your code upon rebuilds but will not affect existing binaries. NEW FEATURES: - Property 'ControllerDelay_Images' is available for the device specific AGC/AEC (mvBlueCOUGAR-lib) interface for mvBlueCOUGAR-Xx00w devices now. This requires at least firmware version 1.1.15.0. - 'Inverter' property is available for digital outputs in the device specific interface (mvBlueCOUGAR-lib) for mvBlueCOUGAR-X devices now. - 10 -> 10 bit HW LUT for colour and 12 -> 10 bit HW LUT for mono versions of the (mvBlueCOUGAR-lib) mvBlueCOUGAR-X added. This will require firmware version than 1.1.18.0. or higher. - mvBlueCOUGAR-Xx00w devices will allow a negative value for the lower gain limit in (mvBlueCOUGAR-lib) active AGC mode. - Firmware version 1.1.18.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This version includes various minor bug fixes and adds support for HW-LUTs. Bugs fixed: - Trigger overlapped with small exposure time. - mvBlueCOUGAR-X122: Darker images with lower trigger frequency. - FFC did not work before first AcquisitionStart. Features added: - HW-LUT: 10To10 for colour models, 12To10 for mono models. - mvBlueCOUGAR-Xx00w Test image. - Temperature limit hysteresis added. BUGS FIXED: - Potential crash when calling the 'UpdateDeviceList' function when the driver could (mvBlueCOUGAR-lib) not find a valid producer. - When working with hardware LUTs in interpolated mode the final value of the (all shipped packages) calculated LUT was not always correct. - When calling the 'restoreDefault' method for the 'DirectValues' property of a LUT (all shipped packages) the default value count was defaulted to 256 even when working with larger LUTs. - When calling 'OBJ_GetFDictEntries', 'OBJ_GetIDictEntries' or 'OBJ_GetI64DictEntries' (mvDeviceManager-lib) with 'pTranslationString' set to 0 'PROPHANDLING_INPUT_BUFFER_TOO_SMALL' was returned if 'translationStringBufSize' was smaller than the internal buffers length. 31.05.2010 1.11.12 NEW FEATURES: - Firmware version 1.1.15.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) This version includes various minor bug fixes and adds support for HDR and device specific AGC/AEC for mvBlueCOUGAR-Xx00w devices. Furthermore it introduces support for counters and timer, single and multi frame acquisition, overlapped trigger for CCD types, LineInverter and an initial version of FFC(Flat field correction). - Improved error reporting when a load/save setting operation did fail on Windows (wxPropView) NT 6.0 and higher(Vista, 7, ...) because of missing user rights. - 'ExposureAndAcquisitionActive' mode added to DigitalOutput modes for mvBlueCOUGAR-X (mvBlueCOUGAR-lib) devices (This requires a firmware update.). BUGS FIXED: - Some small full screen mode related issues fixed: Blinking cursors from the active (wxPropView) editor in the property grid is no longer visible in full screen mode, once returned (mvDisplay-lib) from full screen mode the application does no longer stay on top of all other windows and potential crashes when closing wxPropView while a resource consuming acquisition was running. - Potential thread leak when constantly opening and closing a device. (all shipped packages) (Bug introduced in version 1.11.6 with the introduction of OpenMP) - Lots of missing calls to 'CloseHandle' added to sample applications. (all shipped MSI based packages) (Windows only) - ImageDestination -> PixelFormat = ibpfRGB888Packed did result in the 'R' and 'B' (mvHYPERIONfg-lib) being flipped when capturing from an RGB video source. - Memory read access handling improved. Sometimes if working with large image buffers (mvHyperion.sys, version 1.0.45.47) read access to transfer properties was not possible. (mvHyperion2.sys, version 2.1.16.24) 26.05.2010 1.11.11 CHANGED BEHAVIOUR: - mvBlueFOX-x00w devices will now off a min. exposure time of 6 us with a step width of (mvBlueFOX-lib) 1 us. NEW FEATURES: - The image correction filters (dark current and flat field) can now handle camera AOI (all shipped packages) settings. The camera AOI must fit into the correction data AOI or can have the same size. - New sample added: 'SingleCaptureMasterSlave'. (all shipped MSI based packages) - Property 'BayerMosaicParity' added and published in user interface. (mvVirtualDevice-lib) - Device specific AGC/AEC modes and HDR control features for mvBlueCOUGAR-Xx00w devices (mvBlueCOUGAR-lib) added. (Firmware 1.1.9.1 or higher required) BUGS FIXED: - Internal exception when setting up internal callbacks for SDI versions of the (mvHYPERIONfg-lib) mvHYPERION. (Bug introduced in version 1.11.6) - Sometimes mvBlueFOX-x00w devices had a logarithmical response to light after (mvBlueFOX-lib) initialisation. 11.05.2010 1.11.10 NEW FEATURES: - New functions added to get/set int and float properties in an atomic way. (mvDeviceManager-lib) C-interface: OBJ_Get/SetIArray, OBJ_Get/SetI64Array, OBJ_Get/SetFArray. (mvDeviceManager.h) C++-interface: EnumPropertyI::read/write overload, EnumPropertyI64::read/write (mvIMPACT_acquire.h) overload, EnumPropertyF::read/write overload, IOSubSystemBlueFOX::readOutputRegisterAtomic, IOSubSystemBlueFOX::readInputRegisterAtomic, IOSubSystemBlueFOX::writeOutputRegisterAtomic. BUGS FIXED: - An issue with a code signing certificate resulted in drivers not being installable (all shipped MSI-based packages containing kernel modules) on Windows XP and Windows XP64 any more. 07.05.2010 1.11.9 CHANGED BEHAVIOUR: - Function mvIMPACT::acquire::HDRControl::getKneePointCount removed from interface. (mvIMPACT_acquire.h) Use mvIMPACT::acquire::HDRControl::kneePointCount instead. NEW FEATURES: - Handling for buffers with an odd width for 'ibpfMono12Packed_V2' improved. (all shipped packages) - Adaptive edge sensing de-Bayer algorithm is fully integrated but not yet published (all shipped packages) in the user interface. BUGS FIXED: - When a version of wxPropView that makes use of the user defined access level was (wxPropView) deployed on a system that did not offer support for this feature, wxPropView did crash. (Bug introduced in version 1.11.7) - AOIs in 'Fit to screen' mode and various other special scenarios(zoomed when the (wxPropView) width and height did differ significantly, ...) on Windows finally behave as desired. - Some small full screen mode related issues fixed: With an active analysis plot and/or (wxPropView) monitor display the full screen image was overwritten by these controls. - Missing documentation about the new way of installing and running applications build (all shipped packages) with mvIMPACT Acquire added. (Bug introduced in version 1.11.7) - On some Linux distributions certain(long) log messages could result in crashes. (all shipped packages) - Certain exposure times in connection with certain line delay settings could still (mvBlueFOX-lib) result in black frames for mvBlueFOX-x05 devices. 29.04.2010 1.11.8 CHANGED BEHAVIOUR: - Pending ACK as well as the transmission of extended status by a device will be (mvTLIClientGigE-lib) enabled automatically when a device supporting these features is opened. NEW FEATURES: - The 32-bit mvBlueCOUGAR, mvBlueFOX, mvHYPERION and mvVirtualDevice user mode drivers (mvGigECapture.sys, version 1.1.6.29) can access and run with a 64-bit kernel mode driver. Thus 32-bit (mvTLIClientGigE-lib) applications can be installed on a 64-bit Windows system. See remarks in the chapter (mvHYPERIONfg-lib) 'Building and Linking'. (mvHYPERION.sys, version 1.0.44.46) (Windows only) (mvHYPERION2.sys, version 2.1.15.23) - GainOffsetKnee filter also supports pixel formats ibpfRGBx888Planar, (all shipped packages) ibpfYUV422Packed, ibpfYUV422_10Packed, ibpfYUV422_UYVYPacked, ibpfYUV422_UYVY_10Packed and ibpfYUV422Planar now. - Debug messages can be controlled via a registry entry 'debuglevel' now. (mvHYPERION.sys, version 1.0.44.46) - New pixel formats introduced: ibpfYUV422_10Packed, ibpfYUV422_UYVY_10Packed. (all shipped packages) - Experimental version of adaptive edge sensing de-Bayer algorithm added. Selectable (all shipped packages) via the property 'ImageProcessing -> BayerConversionMode'. BUGS FIXED: - Device power handling improved. (mvHYPERION.sys, version 1.0.44.46) - YUV Histogram was only correct for AOI x-offsets divisible by 2. (wxPropView) 14.04.2010 1.11.7 CHANGED BEHAVIOUR: - TScalerInterpolationMode::simLanczos removed from interface (added in 1.11.6) as this (all shipped packages) interpolation mode was not available for all pixel formats. - Final version of HDR control features added for mvBlueFOX-x00w devices. (mvBlueFOX-lib) - Trigger overlap feature stop moment changed if working with trigger_linedelays. (mvHYPERIONfg-lib) NEW FEATURES: - Functions 'OBJ_GetVisibility', 'OBJ_GetVisibilityS' and 'OBJ_VisibilityToString' (all shipped packages) added to 'C'-interface and 'mvIMPACT::acquire::Component::visibility' and 'mvIMPACT::acquire::Component::visibilityAsString' added to 'C++'-interface. wxPropView will now use this information to allow a user defined access level to properties. - 10to8 HW-LUT is switched on automatically if 'BitsPerPixel=10' and (mvTITANfg-lib) 'Camera->PixelFormat=Mono8'. - The property 'HardwareInit' and the feature list 'OnBoardMemory' have been moved (mvTITANfg-lib) from 'DeviceSpecificData' to the device list that is available also before opening a device. The old location of the feature will continue to work, but should not be used any more. If the newer version of the features have been modified, these will be used, if not the old version will be used. - New sample added: 'ContinuousCaptureDirectX'. (all shipped MSI based packages) - Firmware version 1.00.33 for mvBlueCOUGAR-S Rev. 0 and version 1.02.04 for (all shipped packages for GigE Vision devices) mvBlueCOUGAR-S Rev. 1 devices added. This fixes the following issues: - First image after changing the exposure time or the gain was taken with the old sensor timing - When connected to certain 3COM PoE Hubs/Switches the cameras didn't work correctly - AOI/Frame rate related behaviour has been improved. - Some minor GEV protocol specific issues. - 2 full screen modes added(one is accessible via the context menu of a certain image (wxPropView) display, the other one via F11) BUGS FIXED: - In very rare cases calls to 'mvIMPACT::acquire::Property::readS' and (mvIMPACT_acquire.h) 'mvIMPACT::acquire::Property::readSArray' could raise 'mvIMPACT::acquire::EInputBufferTooSmall' exceptions when being called at an 'unfavourable' moment. A second call could end up just fine. (Bug introduced in version 1.10.65) - Serial port enable corrected for mvHYPERION-HD-SDI (low level mvHYPERION driver, Linux) (low level mvHYPERION2 driver, Linux) - Changing the video mode did not always correctly setup the MSBDataPos parameter. (mvTITAN-lib, version 1.5.28.4) - Reading property values that specify the 'cfAllowValueCombinations' as strings (mvPropHandling-lib) did return an empty string if the integer representation of the properties current value was 0 and an additional trailing whitespace in the resulting value if the integer representation was different from 0. - The C++ interface is compatible with Visual Studio 6.0 again (mvIMPACT_acquire.h) (Bug introduced in version 1.11.6) - 'ibpfMono12Packed_V2' buffers can be converted into a mvIMPACT image buffer correctly (mvDeviceManager-lib) now. - 'Dark current filter' is working again. (all shipped packages) (Bug introduced in version 1.11.6) - mvBlueCOUGAR-X devices can be initialised in 'DeviceSpecific' interface mode again (mvBlueCOUGAR-lib) (Bug introduced in version 1.11.6) - Input data multiplexer onboard-RAM access improved. (mvHYPERION.sys, version 1.0.43.45) - mvHYPERION-CLb/CLe boards work under 64bit versions of Windows again. (mvHYPERION.sys, version 1.0.43.45) - Triggered acquisition corrected if working with more than one input channel parallel. (mvHYPERIONfg-lib) - In Bayer test mode images with a height that was not a multiple of 8 could result in (mvVirtualDevice-lib) the creation of incorrect test data. 30.03.2010 1.11.6 CHANGED BEHAVIOUR: - When a camera description did specify a Y-Tap geometry of 'cltyg1Y2' or 'cltyg2YE' (mvTITANfg-lib) and the tap sort filter was switched off the resulting image was twice as wide and (mvHYPERIONfg-lib) did contain half the amount of lines as specified in the camera description. Now an image with the AOI as defined in the camera description will be returned then. - Gain step width of Gain-Offset-Knee filter changed from 0.005 to 0.0625. (all shipped packages) NEW FEATURES: - Properties 'TapsXGeometry' and 'TapsYGeometry' added in order to allow testing of (mvVirtualDevice-lib) the tap sort filter. - 'cltxg4X2' added to 'TCameraTapsXGeometry'. (mvTITANfg-lib) (mvHYPERIONfg-lib) (mvVirtualDevice-lib) - Property 'ScalerInterpolationMode' published. (mvIMPACT_acquire.h) - Function CameraSettingsFrameGrabber::triggerControl( const std::string& name ) and (mvIMPACT_acquire.h) CameraSettingsBlueCOUGAR::triggerControl( const std::string& name ) added. - Permanent DMA Buffer handling added. Now it is possible to define a device specific (mvHYPERIONfg-lib) permanent DMA buffer. This buffer is allocated during the driver start. (mvHYPERION.sys, version 1.0.42.44) (mvHYPERION2.sys, version 2.1.14.22) UPDATES: - Lots of internal processing filters make use of Open MP now. This will improve the (all shipped packages) the execution speed of various conversions or processing steps when the systems the driver is running on has more than 1 core. However when embedding the driver into a custom installation package this now requires to ship the correct version of the Open MP runtime as well. To find out about the correct version please refer to the chapter 'Installing from private setup routines' of the devices manual. - Firmware version 1.0.96.0 for mvBlueCOUGAR-X devices added. (all shipped packages for GigE Vision devices) - Internal image processing code updated. (all shipped packages) - Internal migration to IPP 6.1.4. (all shipped packages) BUGS FIXED: - Changing the current device selection from a used to an unused one did not change (wxPropView) the state of the 'Use' button state. (Bug introduced in version 1.11.5) - mvBlueFOX-MLC200w will display the correct number of digital I/Os now. (mvBlueFOX-lib) - Digital input read out improved for mvHYPERION-CLb boards. (mvHYPERIONfg-lib) - Start behaviour improved. Under certain conditions (first request with trial mode) (mvHYPERIONfg-lib) some boards did not start the acquisition correctly afterwards. - Transfer pixel format property was invisible for mvHYPERION, mvTITAN-CL, mvGAMMA-CL (mvHYPERIONfg-lib) and mvTITAN-DIG boards. (mvTITANfg-lib) 16.03.2010 1.11.5 NEW FEATURES: - Support for mvBlueFOX-MLC200w devices added. (mvBlueFOX-lib) UPDATES: - Firmware version 1.02.03 for mvBlueCOUGAR-S Rev. 1 devices added. This fixes the (all shipped packages for GigE Vision devices) following issues: - First image after changing the exposure time or the gain was taken with the old sensor timing - When connected to certain 3COM PoE Hubs/Switches the cameras didn't work correctly - AOI/Frame rate related behaviour has been improved. - Firmware version 1.0.93.0 for mvBlueCOUGAR-X devices added. This will fix an issue (all shipped packages for GigE Vision devices) where the device could not be accessed if the devices boot sequence was complete before the surrounding network was up. BUGS FIXED: - Device specific AEC and AGC is working correctly again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.10.93) - Image AOI offsetX and offsetY will now be set correctly (DirectShow_acquire.ax) 09.03.2010 1.11.4 CHANGED BEHAVIOUR: - The step width for AOI/W, AOI/H, AOI/X and AOI/Y for mvBlueFOX-x00w devices is 2 (mvBlueFOX-lib) now(used to be 16 in X and 8 in Y direction). BUGS FIXED: - Trigger acquisition mode 'TriggerOverlap' improved. (mvHYPERIONfg-lib) - Abort function improved (only CLf/CLm). In rare cases a running acquisition did not (mvHYPERIONfg-lib) start again after calling 'imageRequestReset'. Sometimes 'imageRequestReset' calls could result in a system deadlock. - The first image taken after changing the exposure time or gain was acquired using the (mvBlueFOX-lib) previous values. 08.03.2010 1.11.3 BUGS FIXED: - Potential blue screen (BSOD) when the internal timeout check function was called in (mvGigECapture.sys, version 1.1.5.28) parallel with StartIo. - Potential deadlock when the system was running extremely low on resources. (mvTLIClientGigE-lib) (Windows only) 01.03.2010 1.11.2 BUGS FIXED: - Calling 'imageRequestReset' and 'imageRequestSingle' in parallel could result in (mvBlueCOUGAR-lib) deadlocks in rare cases. (Bug introduced in version 1.10.90) - Selecting an explicit mono destination format did result in an incomplete sensor (mvBlueCOUGAR-lib) update for mvBlueCOUGAR-X devices. - When a device driver did not support the 'SettingUsed' property an active info plot (wxPropView) could result in crashes. (Bug introduced in version 1.11.1) 26.02.2010 1.11.1 CHANGED BEHAVIOUR: - Default value type when creating features from XML(thus NOT updating an existing (mvPropHandling-lib) list) for a property is string now while it used to be int. - When opened in 'DeviceSpecific' interface layout with 'Read' access, the acquisition (mvBlueCOUGAR-lib) related features will be read-only now. NEW FEATURES: - New property 'SettingUsed' added to info list of a request. This will contain the (all shipped packages) handle and name(via readS) of the setting that was used for processing this request. - mvTITAN-CL boards will support 1x24 RGB and 1x30 RGB configurations now, mvGAMMA-CL (mvTITANfg-lib) will support 1x24 RGB configurations now. BUGS FIXED: - mvTITAN-CL and mvGAMMA-CL boards will support the 3x8 mono mode as defined in the (mvTITANfg-lib) CameraLink spec. now. - Incorrect timestamps have been returned from time to time. (mvHYPERIONfg-lib) - Inconsistent(in terms of PixelsPerCycle and the tap configuration) but working (mvHYPERIONfg-lib) CameraLink camera descriptions will result in a correct hardware setup again. (mvTITANfg-lib) (Bug introduced in version 1.11.0) - Parallel initialisation of multiple devices should always work now(XALAN doesn't (mvBlueCOUGAR-lib) seem to be thread safe) - CancelIO and abort function improved. Under some circumstances the requests sent (mvHYPERION2.sys, version 2.1.13.21) to mvHYPERION kernel mode driver could not be cancelled. 11.02.2010 1.11.0 CHANGED BEHAVIOUR - Functions and classes that have been declared deprecated for some time now have (mvIMPACT_acquire.h) been removed from the C/C++ interface. This will not break existing binaries, but (mvDeviceManager.h) will force you to change your code during rebuilds when deprecated code was used by (mvDriverBaseEnums.h) your application. A list of functions that have been removed and their replacement can be found in the device drivers manual under 'C/C++ developer -> Porting existing code'. - Max. AOI increased to 8192 x 8192. (mvVirtualDevice-lib) - CameraLink camera descriptions will only allow consistent property sets now(e.g. when (mvHYPERIONfg-lib) setting 'PixelsPerCycle' to 1, only tap geometries that are valid in that context (mvTITANfg-lib) can be selected). In rare cases this might break existing code! UPDATES: - Migration to version 2.0.1 of the GenApi runtime. (mvBlueCOUGAR installer) NEW FEATURES: - New pixel format introduced: 'ibpfMono12Packed_V2'. (all shipped packages) - New property 'PixelFormat' added to 'Camera' parameter list of the device. This (all shipped packages) property can be used to explicitly define the pixel format used for the transfer between the capture device and the host systems memory. This can differ from the pixel format delivered to the user application if needed. - Overlapped expose mode is available in device specific interface for mvBlueCOUGAR-X (mvBlueCOUGAR-lib) devices now. - The data from the analysis grids can be copied into the clipboard by clicking on one (wxPropView) of the data cells(right mouse button). - The grid value format string of the analysis grids can be configured in a printf (wxPropView) like way(right mouse button). - GenICam GenTL producer does support multicast now. (mvTLIClientGigE-lib) - New test image formats added: 'vdtmHorizontalMonoRamp', 'vdtmVerticalMonoRamp', (mvVirtualDevice-lib) 'vdtmMovingVerticalMonoRamp', 'vdtmHorizontalMono12Packed_V2Ramp'. - New GenICam description file for mvBlueCOUGAR-S devices added(version 2.3.1). This (mvBlueCOUGAR installer) will fix an issue when switching on/off vertical binning and reading back the current height and/or y-offset afterwards. - mvV4L2 package (V4L2 to mvIMPACT Acquire interface) integrated. - If supported by the device it is possible to establish a single 'control' and one or (mvBlueCOUGAR-lib) more 'read-only' connections to a GigE Vision device from one or multiple systems. (mvDeviceManager-lib) - Property 'TapSortEnable' published. (mvIMPACT_acquire.h) - A default interface layout that will be used for all devices supporting it can be (wxPropView) selected and is stored when closing the application now. - Very simple hard disk recording mechanism added. (wxPropView) - A driver will offer more than one result queue now. The number of result queues can (all shipped packages) be defined by writing to the 'ResultQueueCount' property before opening a device. - HDR control features added for mvBlueFOX-x00w devices. (mvBlueFOX-lib) - trigger acquisition modes added to mvHYPERION-CLf/CLm. Now the trigger modes are (mvHYPERIONfg-lib) fully compatible with mvHYPERION-CLe. - trigger delay property lines added. This property is only available for line scan (mvHYPERIONfg-lib) applications. BUGS FIXED: - 'Offset_pc' feature was always set to the maximum value internally no matter what was (mvBlueCOUGAR-lib) selected in the properties value. - Potential crash when feeding an image with an unsupported pixel format into the (all shipped packages) calibration routine of the 'Flat field filter' or 'Dark current filter'. - Storing raw Bayer images in *.raw format is working again. (wxPropView) (Bug introduced in version 1.10.85) - Exception handling added to buffer allocation. Now the exception will be caught (all shipped packages) correctly if buffer allocation failed. - AGC/AEC when working with ibpfMono16 did not work correctly. (mvBlueFOX-lib) (mvBlueCOUGAR-lib) 11.01.2010 1.10.99 CHANGED BEHAVIOUR: - Lower limit for property 'Offset_pc' for mvBlueCOUGAR-P, mvBlueCOUGAR-X devices and (mvBlueCOUGAR-lib) mvBlueLYNX-M7 devices set to 0%(was -100%). UPDATES: - Some properties like AOI related things that will be overwritten by the Cognex (mvIMPACTAcquire_Cognex_Adapter-lib, version 1.1.1.3) runtime anyway are no longer displayed in the property list of e.g. QuickBuild. - Devices that don't support rising edge or falling edge trigger modes will use (mvIMPACTAcquire_Cognex_Adapter-lib, version 1.1.1.3) high level or low level trigger modes if possible now. - nios application updated because of newer firmware for mvHYPERION-CLm/CLf boards (mvHYPERIONfg-lib) (firmwareversion > 52). NEW FEATURES: - It's possible to establish 'read-only' access to a GigE Vision device now. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) - 'Offset_pc' property in device specific interface published for mvBlueCOUGAR-X (mvBlueCOUGAR-lib) devices - 40 MHz pixel clock can be selected for mvBlueFOX-x00w devices now. (mvBlueFOX-lib) - New camera-format YUV for SDI-cameras added. This format in the camera descriptions has been added temporarily and will be replaced with an newer camera handler later. (mvHYPERIONfg-lib) - New GenICam description file for mvBlueCOUGAR-S devices added(version 2.3.1) (mvBlueCOUGAR installer) BUGS FIXED: - Single shot mode for mvBlueFOX-202 devices. (mvBlueFOX-lib) - Several small bugs fixed in the 64-bit version of the Windows kernel drivers. (mvHYPERION2.sys, version 2.1.11.19) (mvHYPERION-clm/clf). (mvSerialPort.sys, version 1.0.5.5) 15.12.2009 1.10.98 UPDATES: - Improved image quality for mvBlueFOX-x00w at 32 MHz pixel clock. (mvBlueFOX-lib) BUGS FIXED: - Watermark generator: Vertical line in cross-hairs mode for RGBx888Packed format is (all shipped packages) created correctly now. 11.12.2009 1.10.97 UPDATES: - Some enhanced error checking (short packets, etc.) and statistical information added. (mvGigECapture.sys, version 1.1.4.27) NEW FEATURES: - Enhanced gamma correction related features added to LUTOperations. (all shipped packages) - 'GainOffsetKnee' filter added to image processing chain. (all shipped packages) - GenICam features that define a polling time will be updated automatically in the (mvBlueCOUGAR-lib) generic interface layout now. - Early version of 'WatermarkGenerator' added. So far the features have not been added (all shipped packages) to the C++ wrapper. - Property 'mvIMPACT::acquire::Device::deviceVersion' added. (all shipped packages) - Firmware update for mvBlueCOUGAR-X devices is possible now. (mvDeviceConfigure) (mvBlueCOUGAR-lib) BUGS FIXED: - The GenApi 2.0 runtime installer will write to the 'Path' variable on Windows Vista (mvBlueCOUGAR.msi) and Windows 7 again. (mvBlueCOUGAR-x64.msi) (Bug introduced in version 1.10.95) - Test images in ibpfRGB101010Packed - ibpfRGB141414Packed did use an incorrect white (mvVirtualDevice-lib) value(0xFFFF instead of 0x3FF, 0xFFF and 0x3FFF). 01.12.2009 1.10.96 CHANGED BEHAVIOUR: - Keyboard shortcuts reorganized. (wxPropView) - mvTLIClientGigE.dll became mvTLIClientGigE.cti on Windows as required by the GenTL (mvTLIClientGigE-lib) standard. Also the installer will set the GENICAM_GENTL32/64_PATH variable now. On Linux a softlink has been introduced (mvTLIClientGigE.cti -> mvTLIClientGigE.so). This version is now a fully compliant GenICam GenTL producer according the GenICam GenTL spec. version 1.0. - If no valid boardinfo can be read from the eeprom then the driver will generate some (mvHYPERIONfg-lib) default strings for serial number and board type. - Eeprom write access now checks a magic number before flashes data to eeprom. (low level mvHYPERION driver, Linux) (low level mvHYPERION2 driver, Linux) UPDATES: - updated mvSDK driver package. Changes in matrixfg.sys DMA_Common_Buffer (mvTITAN, version 1.5.28.2) (mvSIGMA, version 4.1.12.49) - 'CaptureToUserMemory_C' is available on Linux as well now. (all shipped packages) BUGS FIXED: - Frame number is no longer shared across driver instances. (mvVirtualDevice) - 'mvIMPACTAcquire_Cognex_Adapter.dll' did not end up in the 'x64' subfolder of 'bin' (all shipped x64 MSI based packages) - Some missing standard enumeration values implemented, GCPortRead and GCPortWrite no (mvTLIClientGigE-lib) longer have alignment restrictions. - Potential crashes in rare case when enumerating devices inside a driver did fail. (mvBlueCOUGAR-lib) (mvBlueFOX-lib) (mvBlueLYNX-lib) - The GenApi 2.0 runtime installer will be executed on x64 versions of Windows as well. (mvBlueCOUGAR-x64.msi) (Bug introduced in version 1.10.95) - driver module close function improved. (low level mvHYPERION2 driver, Linux) 17.11.2009 1.10.95 DEPRECATED API CODE: - The class class mvIMPACT::acquire::InfoFrameGrabber has been declared deprecated (mvIMPACT_acquire.h) and will be removed in future versions. Use mvIMPACT::acquire::Info instead. NEW FEATURES: - The property mvIMPACT::acquire::Info::deviceDriverVersion is available for every (all shipped packages) driver now. - Added support for features that became available with AIK version 1.1 supported by (mvIMPACTAcquire_Cognex_Adapter-lib, version 1.1.0.2) VisionPro 6.0 or greater. This includes a timestamp and multi-byte mono pixel formats. CHANGED BEHAVIOUR: - Delay of about 50 msec added after EEPROM access. (mvHYPERION2.sys, version 2.1.10.18) - UART read buffer increased to 64 kByte. (mvHYPERION.sys) UPDATES: - Slightly improved automatic doc string creation from GenICam features. (mvBlueCOUGAR-lib) - Migration to version 2.0.0 of the GenApi runtime. This will change the installation (mvBlueCOUGAR installer) sequence on Windows as the GenICam runtime installer will be launched independently from within the mvBlueCOUGAR installer. - Driver start behaviour from default flash configuration improved. (mvHYPERION2.sys, version 2.1.10.18) BUGS FIXED: - 3rd party streaming devices that don't support 'AcquisitionMode' 'SingleFrame' will (mvBlueCOUGAR-lib) work again. (Bug introduced in version 1.10.77) - Underlying GenICam features whose node changed from true to false did (mvBlueCOUGAR-lib) not become invisible in mvIMPACT Acquire(interface layout 'Generic' only). - Enumerated properties whose underlying GenICam nodes node (mvBlueCOUGAR-lib) changed at runtime did not result in a correct dictionary update(interface layout 'Generic' only). 05.11.2009 1.10.94 NEW FEATURES: - New sample added: 'CaptureToUserMemory_C'. (all shipped MSI based packages) - Standard derivation added to noise histogram plot. (wxPropView) - mvHYPERION-HD-SDI support added. (low level mvHYPERION2 driver, Linux) CHANGED BEHAVIOUR: - default capture buffer alignment for devices that don't require a certain memory (all shipped packages) alignment will return '1' now. This used to be '0'. BUGS FIXED: - More minor issues introduced with the changed interface ID in mvTLIClientGigE-lib. (mvIPConfigure) (Bug introduced in version 1.10.87) 26.10.2009 1.10.93 NEW FEATURES: - Tool bar and status bar can be switched on and off now. (wxPropView) - 'RawToPlanes' mode added to Bayer conversion filter. (all shipped packages) - Support for mvBlueCOUGAR-X devices added. (mvBlueCOUGAR-lib) UPDATES: - Firmware versions 1.01.20 for mvBlueCOUGAR-S Rev. 1 and 1.00.29 for mvBlueCOUGAR-S (all shipped packages for GigE Vision devices) devices added. This fixes some problems with setting the upper and lower limits for the AGC and AEC algorithms. BUGS FIXED: - On some Linux distributions enabling logging to stdout could result in crashes. (all shipped packages) - Loading of stored filter parameters for 'Dark current filter' did cause incorrect (all shipped packages) images for negative correction values. - Clipping effects in dark current filter. (all shipped packages) - Potential blue screen (BSOD) when re-requesting lost data packets from cameras that (mvGigECapture.sys, version 1.1.3.26) don't support resend and some other small issues. (mvTLIClientGigE-lib) 19.10.2009 1.10.92 DEPRECATED API CODE: - mvIMPACT::acquire::FunctionInterface::ensureRequests. (mvIMPACT_acquire.h) Use mvIMPACT::acquire::SystemSettings::requestCount instead. NEW FEATURES: - Properties 'GainLowerLimit_dB', 'GainUpperLimit_dB', 'ExposeLowerLimit_us' and (mvBlueCOUGAR-lib) 'ExposeUpperLimit_us' will be available in device specific auto control mode for mvBlueCOUGAR-S devices after updating the firmware to version 1.01.19 for Rev. 1 devices or 1.00.28 for Rev. 0 devices. - Properties 'mvIMPACT::acquire::Request::imageOffsetX' and (all shipped packages) 'mvIMPACT::acquire::Request::imageOffsetY' added. - Property 'mvIMPACT::acquire::Device::defaultRequestCount' added. (all shipped packages) - It is possible to reduce the number of request buffers at runtime by writing to the (all shipped packages) property mvIMPACT::acquire::SystemSettings::requestCount now. However this is only possible if NO request is currently queued for acquisition OR is locked by the application. - New GenICam description file for mvBlueCOUGAR-S devices added(version 2.3.0). This (mvBlueCOUGAR installer) will allow to access the gain and exposure limits when ALCMode is active and the Firmware supports it. - New pixel format introduced: ibpfYUV422_UYVYPacked. (all shipped packages) - Mirror function and soft scaler support the formats ibpfRGB101010Packed, (all shipped packages) ibpfRGB121212Packed, ibpfRGB141414Packed and ibpfRGB161616Packed now. - 12 -> 12 bit SW LUT added. (all shipped packages) UPDATES: - Firmware versions 1.01.19 for mvBlueCOUGAR-S Rev. 1 and 1.00.28 for mvBlueCOUGAR-S (all shipped packages for GigE Vision devices) devices added. BUGS FIXED: - TLGetInterfaceInfo is working again. (mvTLIClientGigE-lib) (Bug introduced in version 1.10.87) - wxPropView did report errors in its resource (*.rc) file when build it from scratch. (all shipped packages) - Serial numbers like 'VD1' and 'VD10' could not be distinguished from one another. (mvDeviceManager-lib) - Several minor issues introduced with the changed interface ID in mvTLIClientGigE-lib. (mvIPConfigure) (Bug introduced in version 1.10.87) - In 'mmTopDown' when processing YUV422Packed, every 2 consecutive pixels did contain (all shipped packages) swapped 'Y' components. 02.10.2009 1.10.91 NEW FEATURES: - Property 'FrameDelay_us' published for mvBlueCOUGAR and mvBlueLYNX-M7 devices. (mvBlueCOUGAR-lib) CHANGED BEHAVIOUR: - Property 'FrameDelay_ms' became 'FrameDelay_us' (mvVirtualDevice-lib) This is a code AND application breaking change! - The 32-bit MSI based setup for mvHYPERION devices will no longer allow an (mvHYPERION.msi) installation on Windows 2000 or smaller. BUGS FIXED: - VectorScope plot for RGB888Packed and RGBx888Packed modes is working again. (wxPropView) (Bug introduced in version 1.10.85) - Loading of stored filter parameters for 'Defective pixel filter', 'Flat field filter' (all shipped packages) and 'Dark current filter' fixed. - Under certain conditions (using a generic camera) the kernel driver did report (mvHYPERION.sys) acquisition errors. This was generated by the buildscattergather function and has now been fixed. - Serial ports now use the file object pointer from IRPStackLocation as owner (mvHYPERION.sys) secure multi thread access. (mvHYPERION2.sys, version 2.1.9.17) - Address encoding bit for FPGA DMA-transfer removed from 32-bit driver versions. The (mvHYPERION2.sys, version 2.1.9.17) address encoding bit will currently be set on 64-bit operating systems only now. - Potential blue screen (BSOD) when re-requesting lost data packets on Windows 2000. (mvGigECapture.sys, version 1.1.2.25) 28.09.2009 1.10.90 UPDATES: - MSI packages will be built using WiX 3.0.5419.0 now. (all shipped MSI based packages) BUGS FIXED: - 'Offset_pc' in device specific interface for mvBlueCOUGAR-S devices is working now. (mvBlueCOUGAR-lib) 17.09.2009 1.10.89 NEW FEATURES: - The state of the digital inputs and outputs at the beginning and the end of the (mvBlueCOUGARLocal-lib) exposure period will be returned as part of the request info now. This requires an FPGA update. - Automatic tap calibration enabled for mvBlueCOUGAR-S125 devices. This requires (mvBlueCOUGAR-lib) Firmware versions 1.01.18 or greater. - New GenICam description file for mvBlueCOUGAR-S devices added(version 2.2.0). This (mvBlueCOUGAR installer) will allow to access the pixel compensation and the tap calibration features. UPDATES: - GCGetLastError support improved. (mvTLIClientGigE-lib) - Missing user rights when trying to change the filter driver configuration will be (mvTLIClientGigE-lib) reported to the user now. (mvGigEConfigure) BUGS FIXED: - Cameras that according to the camera description needed pixel rearrangement AND (mvHYPERIONfg-lib) de-mosaicing on the host system where always returned as Bayer RAW images. (mvTITANfg-lib) - 'StreamType' feature returns the correct value now. (mvTLIClientGigE-lib) - Standard users can successfully call the function 'TLIMV_IsDriverInstalled' under (mvTLIClientGigE-lib) Windows now. - Property 'AdapterIPAddress' did contain a list of MAC addresses instead of IP (mvTLIClientGigE-lib) addresses. (mvBlueCOUGAR-lib) (Bug introduced in version 1.10.87) - The property 'PixelClock_KHz' can contain sensor specific values when the (mvBlueCOUGARLocal-lib) mvBlueLYNX-M7 is operated with 2 different sensor heads now. - Switching binning modes or pixel clocks while capturing frames could result in long (mvBlueFOX-lib) delays or incorrect image data(FPGA version 79). - Installation order of device drivers was incorrect(Serial port driver will be (mvHYPERION.msi) installed BEFORE the board drivers will be installed, as the latter once need the (mvHYPERION-x64.msi) serial port driver to be present). 10.09.2009 1.10.88 UPDATES: - Improved update speed of mvBFx05 in OnDemand trigger mode (mvBlueFOX-lib) BUGS FIXED: - Switching between base and medium cameras improved. (mvHYPERIONfg-lib) 08.09.2009 1.10.87 NEW FEATURES: - Certain things can be done by passing command line parameters to the application as (mvDeviceConfigure) well no, allowing things like e.g. firmware updates to be performed for each device with less or no user interaction. - Settings can be imported to and exported from a system wide location now. (wxPropView) - Global settings will be handled during device initialisation if available. User (all shipped packages) specific settings will be favoured for backward compatibility. - All modules of the TLI support read/write access to their ports now. (mvTLIClientGigE-lib) - mvHYPERION-HDSDI support added, SPI access is located temporarily in the kernelmodule (mvHYPERION2.sys, version 2.1.7.15) - UART ctrl RS485 support added (mvHYPERION2.sys, version 2.1.7.15) UPDATES: (all shipped packages) - 'DMR_ImportCameraDescription' or 'mvIMPACT::acquire::CameraDescriptionBase::importDescription' will return an error, if the referenced file can't be opened for reading. - When updating an mvBlueCOUGAR-P or mvBlueLYNX-M7 device, mvDeviceConfigure will (mvDeviceConfigure) automatically open a file dialogue in the folder containing the FW-files shipped as part of the driver package. - Initial version that can handle GigE Vision 1.1 compliant devices. This also (mvTLIClientGigE-lib) includes a method to overcome some firewall related issues when streaming image data. This however requires a GigE Vision 1.1 compliant device as well. - Higher frame rates can be reached in single shot mode for mvBlueFOX-10x devices now. (mvBlueFOX-lib) - Minor change to get rid of the first property being displayed in red in the (mvIMPACTAcquire_Cognex_Adapter-lib, version 1.0.1.1) QuickBuild(R) feature dialogue. - Firmware versions 1.01.18 for mvBlueCOUGAR-S Rev. 1 and 1.00.27 for mvBlueCOUGAR-S (all shipped packages for GigE Vision devices) devices added. BUGS FIXED: - mvHYPERION-CLe and mvHYPERION-CLb serial port installation. (low level mvHYPERION driver, windows) - Binning in high speed modes (pixel clock >= 32 MHz) could result in incorrect image (mvBlueFOX-lib) data for mvBlueFOX-12x devices(FPGA version 78). - Infinite timeout (ImageRequestTimeout_ms set to 0) is working again. (mvTLIClientGigE-lib) (Bug introduced in version 1.10.85) (mvGigECapture.sys, version 1.1.1.24) - imageRequestReset is working with the filter driver again. (mvTLIClientGigE-lib) (Bug introduced in version 1.10.70) (mvGigECapture.sys, version 1.1.1.24) 20.08.2009 1.10.86 NEW FEATURES: - Method 'mvIMPACT::acquire::Statistics::reset' published. (all shipped packages) - Installer packages can be installed with no user interaction now. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) - Filter driver can be installed without user interaction now (call mvGigEConfigure (mvGigEConfigure) with parameters 'install quit'(in this order!)). UPDATES: - Firmware version 1.01.17 for mvBlueCOUGAR-S125C Rev. 1 devices added. This fixes a (all shipped packages for GigE Vision devices) right shift in the image in Mono8 mode. BUGS FIXED: - 'rtctrlModeRunRestart' mode for devices that support HRTC is working again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.10.26) (mvBlueFOX-lib) (mvHYPERIONfg-lib) - PoCL switched on during loading the driver module (low level mvHYPERION2 driver, Linux) - Closing the driver now releases the mvHYPERION board correctly. (low level mvHYPERION2 driver, Linux) 07.08.2009 1.10.85 DEPRECATED API CODE: - 'urNothing': Use 'urNoUpdatePerformed' instead. (mvDriverBaseEnums.h) NEW FEATURES: - Initial version of mvIMPACT Acquire -> VisionPro(R) adapter added to Windows based (all shipped MSI based packages) installer packages. The adapter will be installed by default but can be switched off by deselecting the corresponding merge module in the installation procedure. - Support for some more pixel formats in VectorScope and noise plot added. (wxPropView) - When a Bayer raw image is displayed, the pixel histogram and the line profile will (wxPropView) display a plot for each color component now. - Property 'mvIMPACT::acquire::CameraSettingsBlueDevice::autoControlMode' published. (mvIMPACT_acquire.h) UPDATES: - Missing xpm files added to Linux versions of the GigE Vision driver packages. (mvBlueCOUGAR driver package, Linux) - Firmware versions 1.01.16 for mvBlueCOUGAR-S Rev. 1 devices and 1.00.26 (all shipped packages for GigE Vision devices) for mvBlueCOUGAR-S devices added. This fixes the following issues: 1) The first image taken after re-configuring the camera sometimes did not use the new parameters. 2) It is possible to use software trigger for both digital inputs in delayed readout mode 3) DISCOVERY_ACK will be broadcasted if requested by the application. BUGS FIXED: - When selecting 'idpfRaw' as target pixel format, frame grabber device did return (mvHYPERIONfg-lib) 8 bit mono formats, even if e.g. a connected digital camera did transfer more bits (mvTITANfg-lib) per component. - 'LocalDirectory' for description files is working again. (mvBlueCOUGAR-lib) - When reading the description file fails the driver no longer keeps the heartbeat (mvBlueCOUGAR-lib) thread running. - Devices that reported a local acquisition problem by sending a single trailer with (mvGigECapture.sys, version 1.1.0.23) an appropriate status message did result in resend requests being triggered. - The timeout values passed by the user for buffers and resend did not result in the (mvGigECapture.sys, version 1.1.0.23) correct timeout values on all CPUs. - Potential deadlock when resend was enabled on multi-core CPUs. (mvGigECapture.sys, version 1.1.0.23) - Double-clicking on the live display in full view mode did not switch on the selected (wxPropView) analysis plot again. (Bug introduced in version 1.10.84) - In scaled mode, the last line of the image was not drawn under certain conditions. (mvDisplay-lib) - When using a camera description, that would deliver a 32 or 24 bit RGB signal (mvTITANfg-lib) directly at the grabbers input, the resulting frame did not contain correct data when switching the destination pixel format explicitly to RGBx888Packed or RGB888Packed for mvTITAN-DIG, mvTITAN-CL and mvGAMMA-CL devices. - When working with the software implementation of the LUT, the data for the red (all shipped packages) channel has been applied to the blue channel and vice versa. 24.07.2009 1.10.84 DEPRECATED API CODE: - The class class mvIMPACT::acquire::StatisticsFrameGrabber and (mvIMPACT_acquire.h) mvIMPACT::acquire::StatisticsBlueFOX have been declared deprecated and will be removed in future versions. Use mvIMPACT::acquire::Statistics instead. NEW FEATURES: - Properties 'mvIMPACT::acquire::Statistics::lostImagesCount' and (all shipped packages) 'mvIMPACT::acquire::Statistics::retransmitCount' published. (mvIMPACT_acquire.h) - New HDSDI-Hyperion grabber support added in user mode library. (mvHYPERIONfg-lib) UPDATES: - The property grid will no longer display the last available tool tip if moving the (wxPropView) mouse to another feature with no tool tip. (Linux only) - Some more resend related features added. (mvGigECapture.sys, version 1.0.20.21) CHANGED BEHAVIOUR: - Test image modes offer enhanced functionality(more test images can be created now). (mvVirtualDevice-lib) This might break existing code as some enum values of TVirtualDeviceTestMode have been removed. BUGS FIXED: - If omitting the file extension while attempting to store an image on Linux the (wxPropView) save operation did fail. - Some messages send to the 'Output' window have not been constructed correctly for (wxPropView) UNICODE builds. - An image loaded from a file is not longer erased when maximizing the display area or (wxPropView) selecting a different device. - Potential crash when enumerating the devices registered for DirectShow access. (DirectShow_acquire.ax) (Bug partly introduced in version 1.10.83) - When the size of a device local description file was 4 byte aligned already, 4 bytes (mvBlueCOUGAR-lib) too much have been read from the device the description file download to fail for certain third party cameras. - Sometimes the first call to the 'triggerSoftware' method directly after sending (mvBlueCOUGAR-lib) buffers to the request queue that was empty before did not result in an image being triggered. - On multi-core CPUs sometimes the calibration of the flat field and the dark current (all shipped packages) filter could fail/produce incorrect results. 15.07.2009 1.10.83 NEW FEATURES: - The main image display will be hidden when disabled now, allowing (wxPropView) a full view analysis plot. - The Bayer parity of the test modes 'vdtmBayerWhiteBalanceTestImage' and (mvVirtualDevice-lib) 'vdtmBayerWhiteBalanceTestImageMono12' is selectable now. BUGS FIXED: - Bayer conversion: bmpGB did produce an incorrect left upper pixel and (all shipped packages) bmpBG and bmpGR did produce an incorrect pixel at the beginning of every other line on some platforms for 8 bit images and on all platforms for multi-byte images. - Some labels of the x and y axis displayed an incorrect (too large) value. (wxPropView) - Potential deadlock on multi-core Windows systems with resend enabled. (mvGigECapture.sys, version 1.0.19.20) - Certain exposure times could still result in black frames for mvBlueFOX-x05 (mvBlueFOX-lib) devices. 13.07.2009 1.10.82 NEW FEATURES: - Property 'mvIMPACT::acquire::Request::imageChannelBitDepth' (all shipped packages) published. This feature will only be available for driver versions (mvIMPACT_acquire.h) higher than 1.10.81. - Monitor display added. (wxPropView) - Initial version of the mvIMPACT Acquire -> VisionPro interface (all shipped MSI based packages) added to installer packages. UPDATES: - Version 2 of the mvBlueFOX kernel mode driver for x86 is working under (mvBlueFOX.msi) Windows 2000 as well now. - A more mature version of the NDIS based filter driver with resend (mvGigECapture.sys, version 1.0.18.19) introduced in version 1.10.77. - New firmware 2.2.7 for mvBlueCOUGAR-P devices added. (all shipped packages for GigE Vision devices) - The property interface will expose 64-bit integer properties as well now. (DirectShow_acquire.ax) BUGS FIXED: - Request size is no longer limited to 64 MB. (mvHYPERION2.sys, version 2.1.5.13) - Potential crash when ending the application in live mode while (wxPropView) displaying multi-byte data. - Last 2 rows in the numerical display of the histogram and noise plot (wxPropView) did contain incorrect data. - It was possible that properties define a default value, that was (mvPropHandling-lib) invalid with respect to the translation dictionary of that property. - Some devices claimed(e.g. mvHYPERION boards) to support the 'triggerMode' (mvIMPACT_acquire.h) property from the 'CameraSettingsXXX' class even if they didn't. - Clipping effects in flat field correction filter. (all shipped packages) 02.07.2009 1.10.81 NEW FEATURES: - Log file output is possible in plain text mode now. See documentation for (all shipped packages) details. UPDATES: - Missing new source files for wxPropView added to MSI based installer packages (all shipped MSI based packages) (AnalysisDataGridTable.h/.cpp and VectorScopeCanvas.h/.cpp). BUGS FIXED: - Potential crashes when settings 'ImageRequestTimeout_ms' to 0 and sending 4 (mvBlueFOX-lib) or more requests to the driver at once while working in a triggered mode with no trigger signal and then close the driver. - Potential crash when ending the application in live mode while the mouse (wxPropView) cursor is on top of the image or when moving the mouse over the lower right line of the current image. (Bug introduced in version 1.10.78) - Request size is no longer limited to 64 MB. (mvHYPERION.sys, version 1.0.37.39) - Reset medium channel version 2 added. This bugfix needs an up to date (mvHYPERION.sys, version 1.0.37.39) CLe-firmware(version 44 or higher). - Image buffer check improved. This fixes an issue when increasing the request (mvHYPERIONfg-lib) buffer size of a request that had been used before. 25.06.2009 1.10.80 DEPRECATED API CODE: - Function 'mvIMPACT::acquire::FunctionInterface::availableImageRequestControls' (mvIMPACT_acquire.h) has been declared deprecated. Use 'mvIMPACT::acquire::FunctionInterface:: getAvailableImageRequestControls' instead. NEW FEATURES: - There can be more than one image request control now. Functions (all shipped packages) DMR_CreateRequestControl (C-API) and mvIMPACT::acquire:: FunctionInterface::createRequestControl (C++-API) implemented. - Grid step controls added to vectorScope in order to allow to (wxPropView) analyse not every pixel in the selected AOI. - 'Load image...' added to 'Action' menu (wxPropView) - The name of an image file can be passed as a command line parameter now. (wxPropView) UPDATES: - Memory usage of numerical analysis display reduced. (wxPropView) CHANGED BEHAVIOUR: - The AOI of the currently selected analysis plot can be dragged to a new (wxPropView) location by LEFT-clicking into the AOI and drag it to its new location. RIGHT-clicking and dragging on the image will define a NEW AOI for the selected analysis control. BUGS FIXED: - Synchronized AOI height was incorrect. (wxPropView) - Some minor display related issues for multi-byte RGB data display in (wxPropView) VectorScope control. - Invalid command line parameters could lead to an endless loop when (wxPropView) starting the application. - Restoring the default of AOI, binning, gain and exposure time was not (mvBlueCOUGAR-lib) always working correctly when closing and then re-opening a device. (mvBlueCOUGARLocal-lib) - GFP_DMA flag removed from driver init in mvHYPERION2 module. (low level mvHYPERION2 driver, Linux) 19.06.2009 1.10.79 NEW FEATURE: Power over CameraLink can now be switched on/off from wxPropView. (mvHYPERIONfg-lib) This feature has been added to the Device Specific Data list. (mvHYPERION.sys, version 1.0.36.38) (mvHYPERION2.sys, version 2.1.4.12) NEW FEATURE: Standard Windows serial port access added to mvHYPERION (mvHYPERION.sys, version 1.0.36.38) wdm-kernel module. NEW FEATURE: Horizontal binning implemented for mvBlueFOX-x00wG/C devices. (mvBlueFOX-lib) (This enables 'BinningH' and 'BinningHV'. NEW FEATURE: Initial version of enhanced capture thread and recording controls (wxPropView) added. Continuous and/or silent recording is now possible, the depth of the capture queue can be configured now (especially useful for continuous recording). NEW FEATURE: The AOI of the currently selected analysis plot can be dragged to (wxPropView) a new location by right-clicking and dragging into the AOI. NEW FEATURE: The analysis plots now have a numerical display based on a wxGrid (wxPropView) control. Updating this grid requires a lot of additional CPU load if active in live mode thus this feature should be used for analysis purposes only. NEW FEATURE: Supported image file types can be dropped into the display area (wxPropView) for analysis now. NEW FEATURE: AOI sync. feature added to 'Settings -> Analysis' menu. (wxPropView) NEW FEATURE: VectorScope plot control added. (wxPropView) CHANGED BEHAVIOUR: AOIs can only be changed by the mouse if the selected plot (wxPropView) is enabled as well BUGFIX: The request info 'exposeStart_us' did return the timestamp of the end (mvBlueFOX-lib) of the exposure. BUGFIX: On Windows changing the value of a spin control in the lower right (wxPropView) section of the application did not update the internal data structures. (Windows only) (Bug introduced in version 1.10.78) BUGFIX: LUT related properties in class mvIMPACT::acquire::ImageProcessing (mvIMPACT_acquire.h) have not been bound correctly if available. (Bug introduced in version 1.10.73) BUGFIX: Calling ImageBufferDesc::ImageBufferDesc( TImageBufferPixelFormat (mvIMPACT_acquire.h) pixelFormat, int width, int height ) did allocate but never free memory for the image. 09.06.2009 1.10.78 NEW FEATURE: The AOI of the selected image analysis plot can now also be (wxPropView) positioned by right-clicking and dragging the mouse on the image. NEW FEATURE: The current pixels value is displayed in the lower right end of (wxPropView) the status bar now. NEW FEATURE: custom format NonStandardMono12packed added. (mvHYPERIONfg-lib) CHANGED BEHAVIOUR: Multi-byte data acquisition set byte ordering correct. (mvHYPERIONfg-lib) (big endianess) CHANGED BEHAVIOUR: Max. request objects limit removed for mvHYPERION-CLm/CLf. (mvHYPERIONfg-lib) This limit must be temporarily handled on application site. Its value is 32. BUGFIX: When selecting an AOI width smaller than 316 the exposure time selected (mvBlueFOX-lib) differed from the one actually used for mvBlueFOX-x02 devices. BUGFIX: On ppc cell systems weak_ordering attribute will be set for DMA (low level mvHYPERION2 driver, Linux) mapping. BUGFIX: Spin controls directly respond to text input as well now (after (wxPropView) pressing ENTER). (Linux only) BUGFIX: Scrollbars in scaled display mode behave correctly now. (wxPropView) (Linux only) 04.06.2009 1.10.77 NEW FEATURE: 50 MHz pixel clock for certain sensors is available now. (mvBlueCOUGARLocal-lib) NEW FEATURE: Early version of a NDIS based transport layer that supports (mvGigECapture.sys, version 1.0.17.18) packet resend requests added. The transport layer parameters can be accessed via the 'System/TLI/DataStream' list for testing. UPDATE: Gain response is much more linear for mvBlueFOX-x0x devices now. (mvBlueFOX-lib) UPDATE: Improved SingleFrame acquisition mode for mvBluexxx devices. (mvBlueCOUGAR-lib) BUGFIX: Certain exposure times could result in black frames for (mvBlueFOX-lib) mvBlueFOX-x05 devices. BUGFIX: Calling imageRequestReset during a live acquisition could lead to (mvBlueCOUGAR-lib) deadlocks in rare cases. 26.05.2009 1.10.76 NEW FEATURE: Slider to quickly navigate into a recorded sequence added. (wxPropView) BUGFIX: Starting a record sequence directly after increasing the request (wxPropView) count for a device did not behave correctly. BUGFIX: On Linux platforms not supporting recursive mutexes the end of a (wxPropView) sequence recording could result in a deadlock. (Linux only) BUGFIX: ibpfYUV422Packed did not return correct images for raw Bayer video (all shipped packages) sources and the colorProcessing property set to 'Auto'. (Linux only) BUGFIX: Crashes when stopping the filter driver from within the VisualStudio (mvGigECapture.sys, version 1.0.16.17) debugger or another debugging environment for at least 2 times (Bug introduced in version 1.10.66 in 1.0.13.14 of the kernel module) 14.05.2009 1.10.75 UPDATE: Firmware version 1.00.25 for mvBlueCOUGAR-S devices and version (all shipped packages for GigE Vision devices) 1.01.13 for mvBlueCOUGAR-S Rev. 1 devices. This fixes an issue where in software triggered mode some frames did not get transferred completely. Also this update will allow AGC/AEC in triggered mode. BUGFIX: mvIMPACT::acquire::FunctionInterface::requestCount did not always (mvIMPACT_acquire.h) return the correct current value. The return value was incorrect, if an application did write to the property mvIMPACT::acquire::SystemSettings::requestCount before. BUGIFX: Now CLm/CLf boards can capture the full frame rate if working with (mvHYPERIONfg-lib) area scan cameras. LineScan acquisition is not affected from this change. This bugfix needs an up to date firmware with version 47. BUGFIX: copying image result data corrected. (low level mvHYPERION2 driver, Linux) BUGFIX: 64bit dma_address handling. Now CLf/CLm low level driver set the (mvHYPERION2.sys, version 2.1.3.11) AddressSpaceEncoding flag correctly. (low level mvHYPERION2 driver, Linux) 11.05.2009 1.10.74 NEW FEATURE: Visual Studio 2008 workspace and project files added to sample (all shipped MSI based packages) programs. UPDATE: More detailed information output added. (mvIPConfigure) UPDATE: Migration to version 1.1.2 of the GenApi runtime. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) UPDATE: Firmware version 2.2.0 added for mvBlueCOUGAR-P devices added. (all shipped packages for GigE Vision devices) This fixes various issues with memory allocation in the local interface and enables the new firmware update procedure. UPDATE: Sampling parameters for mvBlueFOX-2xx (CCD version only) improved. (mvBlueFOX-lib) This will improve the overall image quality and will fix a smearing issue for the mvBlueFOX-221. CHANGED BEHAVIOUR: Gamma response behaviour for LUT operations inverted. (all shipped packages) BUGFIX: Removing a user supplied capture buffer from a request object could (mvHYPERIONfg-lib) lead to crashes. 04.05.2009 1.10.73 NEW FEATURE: PoCL enabled for Hyperion CLm/CLf. (mvHYPERION2.sys, version 2.1.2.10) NEW FEATURE: Property 'UserDataMaxSize_bytes' published. This feature can be (mvBlueCOUGARLocal-lib) written to BEFORE opening the device. The value stored by the property defines the max. amount of bytes, that can be transmitted together with the image or without the image via the transmission library of mvIMPACT. NEW FEATURE: Flexible user data chunk size transmission. (FW/RFS 2.1.35) This requires a firmware update. NEW FEATURE: Vertical binning implemented for mvBlueFOX-x00wG/C devices. (mvBlueFOX-lib) Max. frame rate increased to 60 Hz. NEW FEATURE: 10 -> 8 bit HW LUT for mvBlueFOX-2xx for color versions now fully (mvBlueFOX-lib) functional. UPDATE: New firmware update procedure for mvBlueCOUGAR-P and mvBlueLYNX-M7 (mvBlueCOUGAR-lib) devices. These method can only be used when the device itself provides (mvDeviceConfigure) a recent firmware, thus until the device itself can deal with this method, the 'old' update procedure will be used automatically. UPDATE: New version of the filter driver added. This version has been built (mvGigECapture.sys, version 1.0.15.16) with a newer version of the DDK. UPDATE: Missing new source files for wxPropView added to MSI based installer (all shipped MSI based packages) packages (ValuesFromUserDlg.h/.cpp). UPDATE: Internal image processing code updated. (all shipped packages) CHANGED BEHAVIOUR: The number of requests is no longer limited by the sensor (mvBlueCOUGARLocal-lib) resolution. The ImageMemoryManager class and the property 'ImageBufferSize_bytes' are no longer needed and internally don't do anything any more. All references in existing applications should be removed. BUGFIX: On-board processor supports DMA transfer on 64-bit operating systems (mvHYPERIONfg-lib) properly now. BUGFIX: On-board processor will clear the input data fifo for line/frame (mvHYPERIONfg-lib) cameras within the first image request only. BUGFIX: Disconnect/Connect a camera to Hyperion-CLm/CLf could result in a (mvHYPERION2.sys, version 2.1.2.10) disturbed image. Now the PoCL logic reset after 3 sec the CameraLink receiver channel. BUGFIX: Switching from RGB to multi-channel grey acquisition for mvTITAN-RGB/x (mvTITANfg-lib) boards. BUGFIX: When constructing an instance of the class (mvIMPACT_acquire.h) mvIMPACT::acquire::ImageProcessing in an application build with header files from versions 1.10.71 - 1.10.72 running this application on a system with a driver version smaller than 1.10.71 did raise an exception. (Bug introduced in version 1.10.71) BUGFIX: When editing a spin control via the arrow keys up/down the focus is (wxPropView) no longer lost at random. (Bug introduced in version 1.10.69) BUGFIX: Crashes when activating the noise profile for multi-byte mono formats. (wxPropView) BUGFIX: Multi-byte Bayer raw data conversion to multi-byte mono images. (all shipped packages) BUGFIX: When explicitly requesting a multi-byte RGB packed format all (mvBlueFOX-lib) mvBlueFOX devices internally used a single byte format. As the mvBlueFOX2 series is capable of capturing with more than 8 bit resolution, these devices now select a multi-byte format. BUGFIX: When explicitly requesting a multi-byte RGB packed format from a Bayer (mvBlueFOX-lib) sensor, the image color conversion resulted in incorrect images after (mvBlueCOUGAR-lib) 'requestCount' buffers have been captured. (mvBlueLYNX-lib) BUGFIX: Problems when requesting more (>16) frames then some of the internal (mvBlueCOUGARLocal-lib) components could handle. 15.04.2009 1.10.72 NEW FEATURE: mvBlueCOUGAR-S devices support 'AutoControlMode' acmStandard now. (mvBlueCOUGAR-lib) NEW FEATURE: Draw window is selectable for line profile as well now. (wxPropView) BUGFIX: Switching the draw window start from 0 to 1 and back did not work (wxPropView) for the pixel and the noise histogram. BUGFIX: Switching off the image header did not work. (mvBlueFOX-lib) (Bug introduced in version 1.10.71) 14.04.2009 1.10.71 NEW FEATURE: LUTOperations filter added to image processing features. (all shipped packages) NEW FEATURE: 10 -> 8 bit hardware LUT added. This can be configured via the (mvBlueFOX-lib) LUTOperations filter. This feature is available for mvBlueFOX-2xx devices only. So far the feature has just been implemented for mono versions of this device. CHANGED BEHAVIOUR: Multi-byte Bayer raw signals are no longer automatically (mvHYPERIONfg-lib) converted to single byte Bayer raw data by default but will be transferred as multi-byte data now. BUGFIX: On Linux string properties storing string longer than 256 chars (mvPropHandling-lib) did return their data truncated when calling mvIMPACT::acquire::Property::readS, OBJ_GetSFormatted, OBJ_GetSFormattedEx, OBJ_GetSArrayFormatted or OBJ_GetSArrayFormattedEx. BUGFIX: A call to the constructor of (mvIMPACT_acquire.h) mvIMPACT::acquire::CameraSettingsBlueDevice could raise an exception for certain device types. (Bug introduced in version 1.10.65) 06.04.2009 1.10.70 UPDATE: Serial port driver compatibility added for Basler cameras. (mvSerialPort.sys, version 1.0.3.3) UPDATE: PortClose() now calls an IoCtl in the mvHYPERION low level drivers. (clsermv.dll, version 1.0.5.6) BUGFIX: Some debug outputs removed. (mvHYPERION2.sys, version 2.1.1.9) BUGFIX: Small bug in read function fixed. (mvSerialPort.sys, version 1.0.3.3) 03.04.2009 1.10.69 NEW FEATURE: Serial port driver added for mvHYPERION-CLf and mvHYPERION-CLm (mvSerialPort.sys, version 1.0.0.0) devices. This will allow communication with CameraLink compliant (mvSAlloc.sys, version 1.0.0.0) cameras via COM port access function or standard terminal applications. UPDATE: Firmware version 1.00.24 for mvBlueCOUGAR-S devices added. (all shipped packages for GigE Vision devices) This fixes an issue where 1-3 black lines could be seen in the first lines of the image when working in partial scan mode. For color versions of the mvBlueCOUGAR-S this could also result in incorrect Bayer conversion results(mixed up color channels). UPDATE: The interface headers and samples can be used with Borland C++ Builder (all shipped packages) 2007 now. UPDATE: New version of the filter driver added. This version contains further (mvGigECapture.sys, version 1.0.14.15) enhancements regarding debugging. UPDATE: mvBlueFOX-x00wG/C devices will return the used Gain and exposure values (mvBlueFOX-lib) when operated in device specific AGC/AEC mode. CHANGED BEHAVIOUR: mvBlueFOX-x00wG/C devices will use 'Standard' as the default (mvBlueFOX-lib) 'AutoControlMode' now. CHANGED BEHAVIOUR: DirectShow_acquire.msi will no longer be shipped as a (all shipped MSI based packages) separate package. Each device driver now contains the files needed for DirectShow support. Old DirectShow_acquire installations will be removed automatically during an upgrade. mvDeviceConfigure can now be used to set up devices for DirectShow. BUGFIX: Installer can be installed on Windows 7 without SP1. (mvBlueCOUGAR.msi) (Bug introduced in version 1.10.64) (mvBlueCOUGAR-x64.msi) BUGFIX: x64 version of the GigE Vision capture driver is working again. (mvGigECapture.sys, version 1.0.14.15) (Bug introduced in version 1.10.66) BUGFIX: Potential crashes, when working with the driver internal Bayer (all shipped packages) de-mosaicing and mvIMPACT on Linux. BUGFIX: Property grid is displayed correctly again. In 'full tree' mode (wxPropView) certain driver sub-trees are not created any more. (Bug introduced in version 1.10.66) BUGFIX: In single frame acquisition mode sometimes error (either timeouts or (mvBlueCOUGAR-lib) 'DEV_NO_FREE_REQUEST_AVAILABLE' where returned. (Bug introduced in version 1.10.65) 20.03.2009 1.10.68 UPDATE: mvHYPERION-clf/clm Linux compatibility for ppc64 system added. (low level mvHYPERION2 driver, Linux) UPDATE: Timestamps became 64-bit values (have been 32-bit). This needs a FW (mvBlueCOUGARLocal-lib) update as well. BUGFIX: Installation did fail on x86 systems because of a wrong kernel module (mvHYPERIONfg.msi) (x64). (Bug introduced in version 1.10.63) BUGFIX: 'State' property is correctly updated again when removing/re-connecting (mvBlueFOX-lib) a device. (Bug introduced in version 1.10.64) 19.03.2009 1.10.67 UPDATE: Firmware version 1.01.11 for mvBlueCOUGAR-S Rev. 1 mono devices and (all shipped packages for GigE Vision devices) version 1.0112 for mvBlueCOUGAR-S Rev. 1 color devices added. UPDATE: Some new code added to 'ContinuousCapture_C' sample. (all shipped packages) BUGFIX: Sometimes calling 'DMR_CopyCameraDescription' could fail even when a (mvDeviceManager-lib) valid camera description handle was passed to the function. BUGFIX: Sudden increase in intensity when slightly increasing the Gain_dB (mvBlueFOX-lib) property for mvBlueFOX-x05 devices. BUGFIX: Some AOI, AGC and AEC issues for mvBlueFOX-x00wG/C devices. (mvBlueFOX-lib) 13.03.2009 1.10.66 UPDATE: New version of the filter driver added. This version will work with (mvGigECapture.sys, version 1.0.13.14) limited user rights (e.g. with UAC under Vista switch on and NOT (mvTLIClientGigE-lib) running the application as an administrator) as well. CHANGED BEHAVIOUR: mvGigEConfigure is digitally signed and requires (asks for) (mvGigEConfigure) administrator rights on Windows Vista now. CHANGED BEHAVIOUR: wxPropView, mvDeviceConfigure and mvIPConfigure are (all shipped MSI based packages) digitally signed now. CHANGED BEHAVIOUR: All mvIMPACT Acquire MSI packages are digitally signed now. (all shipped MSI based packages) CHANGED BEHAVIOUR: Version 1 of the mvBlueFOX kernel mode driver for x86 (mvBlueFOX.msi) targets is no longer shipped. CHANGED BEHAVIOUR: The 32-bit version of the mvBlueFOX driver is digitally (mvBlueFOX.msi) signed now. Because of this *.cat files have been added to the installer packages and this might force you to modify custom installations. BUGFIX: Missing files 'DevData.h' and 'common.rc2' needed to compile (all shipped MSI based packages) wxPropView added. BUGFIX: Writing to the property 'SensorHeads' with an index different from 0 (mvBlueCOUGARLocal-lib) in a HRTC program step caused an exception for M7 devices even if multiple sensor heads were available. (Bug introduced in version 1.10.65) 10.03.2009 1.10.65 DEPRECATED API CODE: Functions 'OBJ_GetSFormatted' and 'OBJ_GetSArrayFormatted' (mvDeviceManager-lib) have been declared deprecated. Use new 'Ex' versions of these functions. UPDATE: channel synchronization improved (for medium and full cameras) (low level mvHYPERION2 driver, windows 2.0.7.7) (low level mvHYPERION2 driver, Linux) UPDATE: Search for mvBlueFOX in /dev/bus/usb by default. (mvBlueFOX-lib) UPDATE: CLm support added to kernel modules. AbortRequest function now (low level mvHYPERION2 driver added, windows 2.0.6.6) releases both request queues. (low level mvHYPERION2 driver, Linux) UPDATE: When a mvIMPACT buffer is returned to the user this buffer will now (mvDeviceManager-lib) correctly specify the 'IPL_BITSPERSAMPLE' feature for multi-byte pixel formats. NEW FEATURE: Long time integration. Exposure on high by writing to a digital (mvBlueFOX-lib) output. NEW FEATURE: mvHYPERION CLm support added to Hyperion driver (mvHYPERIONfg-lib) NEW FEATURE: 'DesiredAverageGreyValue' property implemented for mvBlueCOUGAR-S (mvBlueCOUGAR-lib) devices. NEW FEATURE: Missing properties published in class (mvIMPACT_acquire.h) mvIMPACT::acquire::AutoControlParameters. NEW FEATURE: Functions 'OBJ_GetSFormattedEx' and 'OBJ_GetSArrayFormattedEx' (mvDeviceManager-lib) added. BUGFIX: Potential crash when closing a device, that was running in live mode. (wxPropView) BUGFIX: Medium modes 10x4 and 12x4 corrected. (mvHYPERIONfg-lib) BUGFIX: Sometimes the first call to (mvBlueCOUGAR-lib) mvIMPACT::acquire::TriggerControl::triggerSoftware did not result in a frame being triggered. BUGFIX: Minor problem when updating properties that do specify the cfFixedSize (mvPropHandling-lib) flag with data that contained more values than the property did allow. BUGFIX: Potential crashes when an application was terminated forcefully without (mvDeviceManager-lib) calling the correct clean up code (DMR_Close, etc.). 02.03.2009 1.10.64 UPDATE: Support for newer kernel version added to mvHYPERION modules. (low level mvHYPERION driver, Linux) UPDATE: Property 'AcquisitionIdleTimeMax_ms' introduced. (mvBlueCOUGAR-lib) UPDATE: Re-organized structure of the example applications. (all shipped MSI based packages) 'SynchronousCaptureMultipleInputs' is now part of every installation package. NEW FEATURE: New Samples added: 'GenericInterfaceLayout', 'DigitalIOs' (all shipped MSI based packages) 'ContinuousCaptureMultipleInputs', 'ContinuousCaptureMultipleVideoSignals'. NEW FEATURE: mvIMPACT::acquire::ComponentIterator::lastSibling and (mvIMPACT_acquire.h) OBJ_GetLastSibling function added. (mvDeviceManager-lib, 1.10.64.142) NEW FEATURE: Support for mvBlueFOX-x00wG/C devices added. (mvBlueFOX-lib) NEW FEATURE: Initial version of multi-byte de-mosaicing algorithm added. (all shipped packages) NEW FEATURE: Property 'mvIMPACT::acquire::Device::capabilities' and some (mvIMPACT_acquire.h) convenience functions to query the availability of certain capabilities published. NEW FEATURE: Draw step width is selectable for pixel and noise histogram now. (wxPropView) NEW FEATURE: wxPropView can finally cope with lists and features being deleted (wxPropView) at runtime. NEW FEATURE: Inversion parameter added to 'OutputSignalGeneratorBlueDevice' (mvIMPACT_acquire.h) Some convenience functions added to class 'OutputSignalGeneratorBlueDevice'. NEW FEATURE: HRTC programs can decrease in size at runtime now. (mvBlueCOUGAR-lib) (mvBlueFOX-lib) (mvHYPERIONfg-lib) NEW FEATURE: 'MissingData_pc' property will be available for every device (all shipped packages) driver now. Devices, that can't detect missing data will not modify this parameter, thus it will always stay 0. NEW FEATURE: EEPROM access and user data related interface implemented for (mvTITANfg-lib) mvTITAN and mvGAMMA boards. NEW FEATURE: AGC/AEC support for 2 byte mono pixel formats. (mvBlueFOX-lib) NEW FEATURE: TAutoControlMode published and implemented for mvBlueFOX and (mvBlueFOX-lib) mvBlueCOUGAR driver. (mvBlueCOUGAR-lib) CHANGED BEHAVIOUR: 'Device::allowUnrecommendedFeatures' became a boolean (mvIMPACT_acquire.h) property. BUGFIX: Sometimes wxPropView did crash when the current device was changed (wxPropView) and the mouse was moved in the property grid. BUGFIX: I/O access is possible again. (mvSIGMAfg-lib) (Bug introduced in version 1.10.52) BUGFIX: mvBlueFOX-10x devices no longer claim to have SDRAM. (mvBlueFOX-lib) (Bug introduced in version 1.10.55) BUGFIX: Property 'syncOutputMode' of class 'IOSubSystemFrameGrabber' was bound (mvIMPACT_acquire.h) to and incorrect property. 18.02.2009 1.10.63 CHANGED BEHAVIOUR: Installation sequence changed as with previous versions (mvBlueCOUGAR.msi) upgrading from an old to a newer version of the capture filter driver (mvBlueCOUGAR-x64.msi) could fail until rebooting the system and manually installing the filter driver using mvGigEConfigure. CHANGED BEHAVIOUR: Linux package, mvHYPERION board variants CLf and CLm will (low level mvHYPERION driver, Linux) now be handled by a separate kernel module 'mvHYPERION2'. This new kernel module offers a better support for 'full' CameraLink cameras. UPDATE: Stop/Restart of streaming behaviour in case of request queue underruns (mvBlueCOUGAR-lib) improved. UPDATE: Slightly improved 'triggerSoftware' command execution time. (mvBlueCOUGAR-lib) UPDATE: Invalid FW files can no longer be selected for mvBlueCOUGAR-S devices. (mvDeviceConfigure) NEW FEATURE: Partial scan mode implemented for mvBlueCOUGAR-S devices. (mvBlueCOUGAR-lib) BUGFIX: mvHYPERION-CLf, sometimes the acquisition does not start and returns (mvHYPERIONfg-lib) a timeout error. With this bugfix the acquisition should start secure. BUGFIX: mvHYPERION-CLe and CLb, sometimes the acquisition does not start (low level mvHYPERION driver, windows 1.0.34.36) and returns a timeout error. With this bugfix the acquisition should start secure. BUGFIX: Depending on certain internal processing functions being active or not (mvBlueCOUGAR-lib) sometimes data was captured into the user supplied capture buffer by (mvBlueCOUGARLocal-lib) the hardware but the final result, which ended up in a different buffer (mvBlueFOX-lib) was returned to the user. (mvHYPERIONfg-lib) BUGFIX: When a device was closed with binning active, re-opening it could (mvBlueCOUGAR-lib) result in an incorrect max. AOI. BUGFIX: Record mode is working correctly again. (wxPropView) (Bug introduced in version 1.10.57) BUGFIX: When binning is active, the FrameRate_Hz property becomes invisible now (mvBlueCOUGAR-lib) BUGFIX: Closing the device did not made it available for re-opening until the (mvTLIClientGigE-lib) the heartbeat timeout did elapse. (Bug introduced in version 1.10.52) 12.02.2009 1.10.62 NEW FEATURE: PropView an drivers can handle buffer that contain NO image data (wxPropView) but additional data like processing results only now. (mvVirtualDevice-lib) (mvBlueCOUGAR-lib) UPDATE: Firmware version 2.1.22 added for mvBlueCOUGAR-P devices added. (all shipped packages for GigE Vision devices) This fixes an issue with writing non-volatile parameters(e.g. GevInterfaceMTU) to the device. UPDATE: Optimized the selection of the optimal transfer pixel format for (mvBlueCOUGAR-lib) mvBlueCOUGAR-S devices. BUGFIX: When an incomplete chunk image was forwarded and the height and width (mvBlueCOUGAR-lib) information of the chunk was invalid this could lead to crashes in rare cases. (Bug introduced in version 1.10.61) BUGFIX: Internal conversions from multi-byte mono to multi-byte RGB pixel (all shipped packages) did not always return correct results. BUGFIX: Defective pixel filter is working again. (all shipped packages) (Bug introduced in version 1.8.5) 11.02.2009 1.10.61 UPDATE: Firmware version 2.1.21 added for mvBlueCOUGAR-P devices added. (all shipped packages for GigE Vision devices) NEW FEATURE: PropView can configured to display incomplete image buffer as (wxPropView) well. BUGFIX: Property 'DigitalInputThreshold_mV' no longer appears to be available (mvBlueCOUGAR-lib) for mvBlueCOUGAR-P devices. 09.02.2009 1.10.60 NEW FEATURE: Image request control mode 'trial' implemented. (mvBlueCOUGARLocal-lib) 05.02.2009 1.10.59 DEPRECATED API CODE: The class class mvIMPACT::acquire::StatisticsBlueCOUGAR (mvIMPACT_acquire.h) has been declared deprecated and will be removed in future version. All features of this class are now available in the base class mvIMPACT::acquire::Statistics for every device. NEW SAMPLE: SynchronousCaptureMultipleInputs sample added. (mvBlueCOUGAR.msi) This sample can be used as a starting point synchronized image (mvBlueCOUGAR-x64.msi) acquisition from multiple sensor heads from mvBlueLYNX-M7 devices. NEW FEATURE: Firmware and support for mvBlueCOUGAR-S124(1.01.10) and (all shipped packages for GigE Vision devices) mvBlueCOUGAR-S125(1.01.07) added. NEW FEATURE: Function mvIMPACT::acquire::DigitalOutput::iswriteable added. (mvIMPACT_acquire.h) NEW FEATURE: Properties (all shipped packages) 'mvIMPACT::acquire::Statistics::framesIncompleteCount' and 'mvIMPACT::acquire::Statistics::missingDataAverage_pc' published. CHANGED BEHAVIOUR: Slightly improved the network adapter recognition function (mvTLIClientGigE-lib) on Linux. CHANGED BEHAVIOUR: Whenever a request is returned to the user that does not (all shipped packages) contain a valid buffer, the request buffer properties are set to invalid values. BUGFIX: 8 byte memleak whenever the min, max or increment parameter of a (mvPropHandling-lib) property was changed by a device driver. BUGFIX: Leading 'kHz_' in the string representation of the allowed values for (mvBlueCOUGAR-lib) the property 'PixelClock_kHz' removed again. (Bug introduced in version 1.10.57) BUGFIX: Parallel acquisition improved. If using asynchronous cameras (mvHYPERIONfg-lib) then sometimes the request was return with an error. BUGFIX: When the mvBlueLYNX-M7 was operated with a single sensor head only (mvBlueCOUGARLocal-lib) the initialisation of the device could fail. 29.01.2009 1.10.58 NEW FEATURE: Property 'userData' published in class (mvVirtualDevice-lib) 'mvIMPACT::acquire::CameraSettingsVirtualDevice'. (mvIMPACT_acquire.h) NEW FEATURE: Property 'imageRequestTimeout_ms' published. (mvVirtualDevice-lib) BUGFIX: 'empty' strings for overlay display could result in incorrect overlay (wxPropView) data. BUGFIX: New FPGA file (version 76) added to driver. This fixes problems when (mvBlueFOX-lib) working with single image requests(always just a single request in the input queue) that could cause in capture errors. 28.01.2009 1.10.57 DEPRECATED API CODE: 'rrCameraUserAOINotSupported', (mvDriverBaseEnums.h) 'rrScanStandardNotSupported' and 'rrScanRateInvalid'. Check for DMR_CAMERA_DESCRIPTION_INVALID_PARAMETER as a result of calling the 'imageRequestSingle' function instead. 'bwbrErrorToDark': Use 'bwbrErrorTooDark' instead. 'bwbrErrorToBright': Use 'bwbrErrorTooBright' instead. These are spelling mistakes. Deprecated constants will be removed in future versions of the interface. This will not break existing binaries but will force you to change your code we re-build applications. CHANGED BEHAVIOUR: Color format conversion from Camera format RGB888packed (mvHYPERIONfg-lib) to destination color format RGBx888packed now calculated in FPGA. UPDATE: Firmware version 1.01.10 for mvBlueCOUGAR-S devices 120, 121 and 123 (all shipped packages for GigE Vision devices) Rev. 1(mono versions) added to setup. This improves the frame rate in single shot mode, fixes problems with cameras that have been assigned a persistent IP, that are connected to power before the host systems network interface card is up and fixes an issue when accessing the min. value of ExposureTimeAbs. UPDATE: Error detection when calling DMR_ImageRequestSingle or (all shipped packages) FunctionInterface::imageRequestSingle improved. UPDATE: New version of the filter driver added. This version contains enhanced (mvGigECapture.sys, version 1.0.12.13) debugging options. BUGFIX: TDeviceEventType::detAll correctly specifies ALL event event types (mvDriverBaseEnums.h) again. (Bug introduced in version 1.10.55) BUGFIX: Several minor issues that caused the initialisation of a device to (mvBlueCOUGAR-lib) fail. This could occur whenever a device has been detected by the (mvTLIClientGigE-lib) device manager, was then power cycled and afterwards the user tried to initialise it. BUGFIX: In case no capture buffer could be allocated because of the system (mvBlueCOUGARLocal-lib) being short on memory requesting an image could lead to crashes. BUGFIX: Sometimes the max. value of 'RequestCount' was by 1 larger than there (mvBlueCOUGARLocal-lib) is frame buffer. BUGFIX: Certain sets of parameters could result in an unprocessible request (mvBlueCOUGAR-lib) that because of an internal problem could result in a deadlock. BUGFIX: The calculation of the dark current correction image (through the (all shipped packages) 'Calibrate' mode operated on partly uninitialsed memory. This could lead to incorrect correction images. When updating the driver also the calibration must be performed again to get rid of the problem. BUGFIX: When changing the video channel for an M7 it was possible that the (mvBlueCOUGAR-lib) sensor switched to was not completely updated. (Bug introduced in version 1.10.56) 19.01.2009 1.10.56 CHANGED BEHAVIOUR: Properties 'BinningMode' and 'TestMode' will always be (mvBlueCOUGAR-lib) available for mvBlueLYNX-M7 and mvBlueCOUGAR devices. However as not (mvBlueCOUGARLocal-lib) every device supports these features, some devices will only allow to set these properties to 'Off'. This has been done for compatibility reasons only. NEW FEATURE: Binning added to mvBlueLYNX-M7 devices. So far no all sensors (mvBlueCOUGAR-lib) support this feature. This requires a firmware update. (mvBlueCOUGARLocal-lib) UPDATE: Settings that have been exported with a locale that stores floating (mvPropHandling-lib) point values with a separating ',' instead of a '.' can be imported again. UPDATE: Firmware version 1.00.23 for all mvBlueCOUGAR-S devices 120, 121 and (all shipped packages for GigE Vision devices) 123 added to setup. This improves the frame rate in single shot mode and fixes an issue when accessing the min. value of ExposureTimeAbs. BUGFIX: devices, that support more than 1 trigger mode in advanced trigger (mvBlueCOUGAR-lib) interface did not correctly update all device registers, when switching back to the standard trigger interface. 15.01.2009 1.10.55 NEW FEATURE: Support for sensor specific footer sizes added. (mvBlueCOUGARLocal-lib) NEW FEATURE: Property 'mvIMPACT::acquire::Device::interfaceLayout' published. (mvIMPACT_acquire.h) UPDATE: New version of the filter driver added. This version can return (mvGigECapture.sys, version 1.0.11.12) statistical information. UPDATE: Firmware version 1.00.23 for mvBlueCOUGAR-S mono devices added to (all shipped packages for GigE Vision devices) setup. This improves the frame rate in single shot mode and fixes an issue when accessing the min. value of ExposureTimeAbs. UPDATE: The image DMA buffer will only be mapped and locked once. This (low level mvHYPERION driver, windows 1.0.33.35) information are renewed only if the affected buffers are changed. BUGFIX: Bottom-half interrupt routine should be thread safe now. (low level mvHYPERION driver, windows 1.0.33.35) (low level mvHYPERION2 driver, windows 2.0.3.3) BUGFIX: Trigge rmode availability corrected for mvHYPERION-CLe boards. (mvHYPERIONfg-lib) BUGFIX: mvBlueFOX-10x devices make use of the SDRAM as well. (mvBlueFOX-lib) BUGFIX: Socket API based transport layer did not correctly handle an image (mvTLIClientGigE-lib) request timeout of 0. BUGFIX: Multi-byte mono pixel formats with zoom factors greater than 1 could (mvDisplay-lib) cause crashes. (Bug introduced in version 1.10.50) 07.01.2009 1.10.54 NEW FEATURE: Class mvIMPACT::acquire::EnumPropertyI64 can be compiled using (mvIMPACT_acquire.h) Visual Studio 6 now. NEW FEATURE: Zooming can also be done by using the mouse wheel now. (wxPropView) NEW FEATURE: Property 'mvIMPACT::acquire::Request::imageFooter' published. (mvIMPACT_acquire.h) NEW FEATURE: 'Offset_pc' feature became available for mvBlueCOUGAR-P and (mvBlueCOUGAR-lib) mvBlueLYNX-M7 devices. (mvBlueCOUGARLocal-lib) NEW FEATURE: Early version of a socket based transport layer that supports (mvTLIClientGigE-lib) packet resend requests added. The transport layer parameters can be accessed via the 'System/TLI/DataStream' list for testing. DEPRECATED API CODE: The functions ImageProcessing::defineFilterImageBuffer, (mvIMPACT_acquire.h) ImageProcessing::queryFilterImageBuffer, DMR_GetFilterImageBuffer (mvDeviceManager-lib) and DMR_SetFilterImageBuffer have been declared deprecated. Since none of these functions ever did perform any useful task there is no direct replacement. CHANGED BEHAVIOUR: Maximum number of request objects limited for the grabber (mvHYPERIONfg-lib) boards CLf and CLm. BUGFIX: Function mvIMPACT::acquire::EnumPropertyI64::write did truncate the (mvIMPACT_acquire.h) value to a 32-bit parameter. BUGFIX: Improved error handling for imageRequestSingle(). It is possible (mvHYPERIONfg-lib) that the operating system cannot generate the DMA-address list for the requested image buffer. This will no result in an appropriate error message. 17.12.2008 1.10.53 CHANGED BEHAVIOUR: Now trigger controlled acquisition is available (mvHYPERIONfg-lib) for Hyperion-CLf and CLm products (with some limitations). (low level mvHYPERION2 driver added, windows 2.0.0.0) CHANGED BEHAVIOUR: Only the trigger modes supported by the selected video (mvBlueCOUGARLocal-lib) channel will be available now. NEW FEATURE: Noise histogram plot added. So far not all pixel formats are (wxPropView) supported. NEW FEATURE: Full AOI mode added for image analysis plots. (wxPropView) NEW FEATURE: Draw window is selectable for pixel and noise histogram now. (wxPropView) UPDATE: New GenICam description file for mvBlueCOUGAR-S devices added(version 2.1.2). (mvBlueCOUGAR installer) This will fix some small bugs. 11.12.2008 1.10.52 DEPRECATED API CODE: The class class mvIMPACT::acquire::ConnectorFrameGrabber (mvIMPACT_acquire.h) and the function IOSubSystem::RTCCtrProgramCount have been declared deprecated and will be removed in future version. Use mvIMPACT::acquire::Connector and IOSubSystem::RTCtrProgramCount instead. BUGFIX: Calling a read function of one of the classes derived from (mvIMPACT_acquire.h) mvIMPACT::acquire::Property that accepts a reference to a vector did raise an exception when the parameter 'start' differed from 0. BUGFIX: In case of a failed initialisation the driver could crash while (mvTITANfg-lib) shutting down. (mvSIGMAfg-lib) BUGFIX: Tap sort filter did not re-arrange the pixel data for mvGAMMA-CL and (mvTITANfg-lib) mvTITAN-CL boards. (Bug introduced in version 1.10.20) BUGFIX: Requesting a buffer that doesn't fit into the memory accessible by the (mvTITANfg-lib) could lead to states where further image acquisition was no longer (mvSIGMAfg-lib) possible. 08.12.2008 1.10.51 BUGFIX: Programming the flash memory with mvHYPERION2 kernel driver was not (low level mvHYPERION2 driver, windows 2.0.1.1) possible. CHANGED BEHAVIOUR: 'OBJ_GetSFormatted' and 'OBJ_GetSArrayFormatted' will (mvPropHandling-lib) accept empty format strings now. This will result in the same behaviour (mvDeviceManager-lib) as a NULL pointer. 05.12.2008 1.10.50 NEW FEATURE: 'DeviceReset' feature implemented for mvBlueCOUGAR-P and (FW/RFS 2.1.10) mvBlueLYNX-M7 devices. This requires a firmware update. IMPORTANT: Once devices have been updated, at least this version (1.10.50) of the remote driver must be used! UPDATE: Some files needed to build wxPropView added to installer. (all shipped MSI based packages) UPDATE: When updating the firmware for mvBlueCOUGAR-S devices only firmware (mvDeviceConfigure) files matching the HW revision can be selected now. UPDATE: Migration to version 1.1.1 of the GenApi runtime. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) UPDATE: Misleading log message when executing a RW command in generic interface (mvBlueCOUGAR-lib) mode. UPDATE: Register access no longer uses concatenation if not supported by the (mvTLIClientGigE-lib) device. CHANGED BEHAVIOUR: mvHYPERION board variants CLf and CLm will now be (low level mvHYPERION driver, windows 1.0.32.34) handled by a separate kernel mode driver 'mvHYPERION2'. This new kernel (low level mvHYPERION2 driver added, windows 2.0.0.0) driver included as part of the driver package. This new kernel driver offers a better support for 'full' CameraLink cameras. BUGFIX: Setting 'ImageRequestTimeout_ms' to 0 did not result in a never (mvTITANfg-lib) elapsing time out but a buffer that immediately timed out if no (mvSIGMAfg-lib) captured frame was available in the devices result queue. BUGFIX: Sometimes the heartbeat thread was running even if opening the device (mvBlueCOUGAR-lib) failed. BUGFIX: Small memory leak, when opening the device failed. (mvBlueCOUGAR-lib) BUGFIX: In scaled mode only the rectangle currently visible was converted. (mvDisplay-lib) (This only affected pixel formats not directly displayable like e.g. RGB101010Packed) BUGFIX: Switching from zoomed to 'fit to screen' mode could result in only (wxPropView) parts of the image being displayed. === CD2008/B === 19.11.2008 1.10.49 NEW FEATURE: Firmware files for mvBlueCOUGAR-S Rev. 1 devices added to setups. (all shipped packages for GigE Vision devices) UPDATE: Slightly improved the algorithm that selects to optimal payload packet (mvTLIClientGigE-lib) size for the streaming channel as this didn't work with all cameras before. UPDATE: Panel for controls on the right have a scroll bar now when needed (mvIPConfigure) as the controls in the lower right section otherwise couldn't be accessed with very low screen resolutions. BUGFIX: write image results to footer memory improved. (low level mvHYPERION driver, windows) BUGFIX: Memory manager mode 'Automatic' could lock up under certain conditions. (mvSIGMAfg-lib) (Bug introduced in version 1.10.31) (mvTITANfg-lib) 18.11.2008 1.10.48 NEW FEATURE: class mvIMPACT::acquire::SystemBlueCOUGAR published. (mvIMPACT_acquire.h) This class contains the acquisition mode property. UPDATE: using medium or full cameras, now phase error detect will be (low level mvHYPERION driver, windows) checked. UPDATE: New GenICam description file for mvBlueCOUGAR-S devices added(version 2.1.1) (mvBlueCOUGAR installer) This will fix some small bugs. UPDATE: Firmware version 1.00.22 for mvBlueCOUGAR-S devices added to setup. (all shipped packages for GigE Vision devices) This update will reduce the time needed to start the streaming of on the device by 50%. BUGFIX: Float properties are only created as spin controls if they define (wxPropView) a step width now. 14.11.2008 1.10.47 NEW FEATURE: Interrupt enable added for mvHYPERION-CLf and mvHYPERION-CLm (low level mvHYPERION driver, windows) on Windows XP. NEW FEATURE: class mvIMPACT::acquire::CameraSettingsVirtualDevice added. (mvIMPACT_acquire.h) UPDATE: Source code for wxWidgets version of PropView added to MSI based (all shipped MSI based packages) installer. CHANGED BEHAVIOUR: serial communication temporarily controlled with a timer. (low level mvHYPERION driver, windows) CHANGED BEHAVIOUR: Property 'FrameDelay_ms' became a pure integer property. (mvVirtualDevice-lib) BUGFIX: Serial port 1 will be configured correctly now. (low level mvHYPERION driver, windows) 13.11.2008 1.10.46 NEW FEATURE: Initial version that supports multiple parallel data streams. (mvBlueCOUGAR-lib) The mvBlueLYNX-M7 can now transfer to streams in parallel, however this will need a FW update. UPDATE: Splitter added to allow usage with screen resolutions of 1024 by (mvIPConfigure) 768 and smaller. CHANGED BEHAVIOUR: Most methods in generic mode and some belonging to the (mvBlueCOUGAR-lib) transport layer no longer require parameters. The parameters needed in previous releases are now available as global properties in the System list. These new properties are 'MethodPollingInterval_ms' and 'MethodPollingMaxRetryCount'. CHANGED BEHAVIOUR: Certain features reserved for internal use will no longer (mvBlueCOUGAR-lib) be created as mvIMPACT Acquire properties or methods. Currently this will affect 'AcquisitionStart', 'AcquisitionStop' and 'GevCCP'. UPDATE: Manual and firmware files for mvBlueLYNX-M7 devices added to setup. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) UPDATE: The property 'VideoChannel' as part of the request infos will be (all shipped packages) supported by every device driver now. Devices that don't support multiple video channels will always return 0. BUGFIX: mvBlueFOX-2xx devices make use of the SDRAM as well. (mvBlueFOX-lib) BUGFIX: All mvBlueFOX-2xx devices use the same Bayer pattern as the existing (mvBlueFOX-lib) mvBlueFOX-1xx devices. BUGFIX: Gain_dB is returned correctly as part of the request info now. (mvBlueCOUGARLocal-lib) BUGFIX: When the current image width was larger than the size of the display (wxPropView) area and the height of the image was smaller, no image was displayed. BUGFIX: In generic mode the feature 'AcquisitionMode' is no longer registered (mvBlueCOUGAR-lib) in the systems list. BUGFIX: Message channel was not closed when closing the device. (mvTLIClientGigE-lib) 27.10.2008 1.10.45 UPDATE: The signed versions of the mvDELTA/mvSIGMA and the mvGAMMA/mvTITAN (mvTITAN_mvGAMMA.msi) drivers that have been introduced with version 1.10.25 of this SDK (mvDELTA_mvSIGMA.msi) have been removed again as systems running an old unsigned version of any of these packages can't be cleaned up completely. This in a worst case could lead to a state where the device driver was not working at all. Signed versions of these packages will be available on request, but can't be installed on a system that had an unsigned version installed in the past. BUGFIX: Unscaled display with scrollbars: Scrolling down did move the image (wxPropView) in upper direction and vice versa. 24.10.2008 1.10.44 UPDATE: Some internal and some documentation related issues. First auto build local packages for mvBlueLYNX-M7 devices. 22.10.2008 1.10.43 BUGFIX: Parallel acquisition improved. (low level mvHYPERION driver, windows) NEW FEATURE: Property 'DigitalInputThreshold_mV' added for mvBlueLYNX-M7 (mvBlueCOUGAR-lib) devices. NEW FEATURE: Property 'DigitalInputThreshold_mV' published in C++ interface. (mvIMPACT_acquire.h) BUGFIX: mvBlueFOX-205 types used a wrong device type and thus appeared as (mvBlueFOX-lib) mvBlueFOX-M205 types and claimed to have 4 instead of 2 digital outputs. BUGFIX: Digital input properties no longer specify the 'cfWriteAccess' flag (mvBlueCOUGAR-lib) if no local application is connected. (mvBlueCOUGARLocal-lib) (Bug introduced in version 1.10.36) 20.10.2008 1.10.42 BUGFIX: With a missing sensor head 0 the device can still be initialised. (mvBlueCOUGARLocal-lib) Check the property 'DeviceStatus' or 'DeviceStatusString' for information about the device state. BUGFIX: Local mvIMPACT lic related problem fixed. (mvBlueCOUGARLocal-lib) (Bug introduced in version 1.10.36) NEW FEATURE: mvBlueLYNX-M7 devices can be accessed and configured via the (mvBlueCOUGAR-lib) on board WLAN interface now. 24.09.2008 1.10.41 BUGFIX: Switching input channel. Not all needed properties have been set (mvHYPERIONfg-lib) correctly if switching the input channel. BUGFIX: InitExternalListAccess exception during init(only visible in log files) (mvSIGMAfg-lib) (Bug introduced in version 1.10.33) BUGFIX: Closing a GigE Vision device did no longer destroy the data streams (mvBlueCOUGAR-lib) of other GigE Vision devices running in the same process. (mvTLIClientGigE-lib) BUGFIX: When using the generic interface layout when working with non-MATRIX (mvBlueCOUGAR-lib) VISION devices certain interconnections within the XML file belonging to the device in connection with float features could lead to crashes. 22.09.2008 1.10.40 BUGFIX: Configuring a device to use a persistent IP address is working again. (mvIPConfigure) BUGFIX: Flash signal output in 'GlobalResetRelease' shutter mode for (mvBlueFOX-lib) mvBlueFOX-105 devices. 17.09.2008 1.10.39 NEW FEATURE: Image buffers no longer need 4 byte alignment in order to be (mvDisplay-lib) displayed correctly. NEW FEATURE: Property 'divider' added to class 'PulseStartConfiguration'. (mvIMPACT_acquire.h) CHANGED BEHAVIOUR: AOI step width reduced from 4 to 1. (mvVirtualDevice-lib) BUGFIX: If the filter driver was not installed the application did not (mvGigEConfigure) terminate automatically during silent uninstall. BUGFIX: Potential crash in the rare case of cancelling a request that also (mvGigECapture.sys, version 1.0.9.10) just timed out. 15.09.2008 1.10.38 NEW FEATURE: 'customDataDirectory' property published in class 'Device' (all shipped packages) NEW FEATURE: Class mvIMPACT::acquire::InfoBlueCOUGAR added to interface. (mvIMPACT_acquire.h) CHANGED BEHAVIOUR: Timestamps will now be created in kernel mode to improve (mvBlueCOUGARLocal-lib) precision. (Requires RFS update) NEW FEATURE: property 'ClientConnectionState' added to 'Info -> Camera' and (mvBlueCOUGARLocal-lib) class mvIMPACT::acquire::InfoBlueCOUGAR. (mvBlueCOUGAR-lib) (mvIMPACT_acquire.h) BUGFIX: Properties under 'Info' will be updated correctly again. (mvBlueCOUGARLocal-lib) 11.09.2008 1.10.37 NEW FEATURE: If supported by the device, the optimal packet size for the (mvBlueCOUGAR-lib) current transmission channel is determined automatically during (mvTLIClientGigE-lib) device init. To disabled this feature set the property 'AutoNegotiatePacketSize' in the device list to 'No'. This feature requires at least firmware version 2.0.0 for mvBlueCOUGAR-P and mvBlueLYNX-M7 devices and version 1.00.20 for mvBlueCOUGAR-S devices. NEW FEATURE: All mvBlueFOX-M1xx devices and mvBlueFOX-2xx devices have 8 MB (mvBlueFOX-lib) of usable local memory now. This might require a firmware update. UPDATE: Firmware version 1.00.20 for mvBlueCOUGAR-S devices added to setup. (all shipped packages for GigE Vision devices) This fixes an issue during the auto negotiation of the package size and an issue where several devices in a zero config network couldn't obtain correct IP addresses. DEPRECATED API CODE: DEV_REQUEST_CANT_UNLOCKED (use (mvDriverBaseEnums.h) DEV_REQUEST_CANT_BE_UNLOCKED instead), rrSnapAborted (use rrRequestAborted instead). Deprecated constants will be removed in future versions of the interface. This will not break existing binaries but will force you to change your code we re-build applications. BUGFIX: Detection of changed pixelPerCycle settings improved (mvHYPERIONfg-lib) BUGFIX: Timestamps will now be reported correctly. (mvSIGMAfg-lib) (mvTITANfg-lib) BUGFIX: If imageRequestReset was called during a running image acquisition the (mvSIGMAfg-lib) the current frame was returned with rrTimeout instead of (mvTITANfg-lib) rrRequestAborted. BUGFIX: Calling 'imageRequestReset' while active image requests are processed (mvBlueCOUGAR-lib) by the driver could cause long delays of up to 10 seconds. 08.09.2008 1.10.36 UPDATE: Slightly improved digital I/O access. (mvBlueFOX-lib) UPDATE: New GenICam File (2.1.0) for mvBlueCOUGAR-S devices added to setup. (all shipped packages for GigE Vision devices) CHANGED BEHAVIOUR: Features used by a local application running on the (mvBlueCOUGAR-lib) mvBlueCOUGAR-P or mvBlueLYNX-M7 will be locked for the client now. BUGFIX: Sometimes images were triggered when enabling an external trigger (mvBlueFOX-lib) mode or a HRTC program even if there was no external or HRTC generated signal for mvBlueFOX-102aG devices. BUGFIX: Some small license related problems. (mvBlueFOX-lib) BUGFIX: Potential deadlock when closing a connection to an mvBlueCOUGAR-P or (mvBlueCOUGAR-lib) mvBlueLYNX-M7 device that has been disconnected while just updating some of the device info properties. 01.09.2008 1.10.35 UPDATE: Memory management of capture buffers improved for mvBlueCOUGAR-P (mvBlueCOUGAR-lib) and mvBlueLYNX-M7 devices. UPDATE: Slight performance increase in buffer info handling. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) UPDATE: Firmware version 1.00.17 for mvBlueCOUGAR-S devices added to setup. (all shipped packages for GigE Vision devices) ForceIP command is correctly acknowledged now and the DeviceUserID is correctly written to non-volatile memory now. CHANGED BEHAVIOUR: Only update files with a name that exactly matches the (mvDeviceConfigure) requirements can be selected for mvBlueCOUGAR and mvBlueLYNX-M7 devices now. BUGFIX: Passing a timeout value of 0 to the property 'ImageRequestTimeout_ms' (mvTLIClientGigE-lib) now results in a timeout, that never elapses. (mvGigECapture.sys, version 1.0.8.9) BUGFIX: Potential deadlock when calling imageRequestReset in a triggered (mvBlueCOUGAR-lib) application with no trigger signal present. BUGFIX: Interface count is displayed correctly now. (mvIPConfigure) BUGFIX: Error handling during file upload for mvBlueCOUGAR-P and mvBlueLYNX-M7 (mvBlueCOUGAR-lib) devices. BUGFIX: Devices with an old FW (<1.0009) and a new description file can be (mvBlueCOUGAR-lib) initialised for update now. BUGFIX: AOIs in zoom mode where not displayed at the correct('real') position. (wxPropView) BUGFIX: TLIMV_ForceIP could crash when the adapter receiving the ack from the (mvTLIClientGigE-lib) device had an index higher than the number of adapters used to send the command. 28.08.2008 1.10.34 NEW FEATURE: New plots for 'frame ID', 'frame ID difference', (wxPropView) 'gain in milli dB' and line counter added. BUGFIX: OS handle leak in filter based driver(Windows only, one handle per (mvTLIClientGigE-lib) frame). BUGFIX: Some request info properties haven't been updated correctly. (mvBlueCOUGAR-lib) (Bug introduced in version 1.10.31) UPDATE: Firmware and description files for mvBlueCOUGAR and mvBlueLYNX-M7 (mvBlueCOUGAR-1.10.34.112.tar.gz) devices added to Linux version of the remote driver. 26.08.2008 1.10.33 NEW BEHAVIOUR: When explicitly asking for the destination format (mvBlueCOUGAR-lib) ibdfRGB888Packed mvBlueCOUGAR-S devices will directly transmit RGB image data. This requires more network bandwidth, but saves CPU time. NEW BEHAVIOUR: XML log files can no longer be viewed if the viewer expects (all shipped packages) valid XML as an input but results in valid XML files when the drivers are closed correctly even if several devices write to the same log file. NEW FEATURE: Support for devices with multiple network interfaces added. (mvIPConfigure) NEW FEATURE: Pixel clock speeds 6000, 8000, 10000 and 12000 MHz added for (mvBlueFOX-lib) mvBlueFOX-105 and mvBlueFOX-102aG devices. NEW FEATURE: Configuration support for devices with multiple interfaces added. (mvIPConfigure) (mvTLIClientGigE-lib) UPDATE: Firmware version 1.00.15 for mvBlueCOUGAR-S devices added to setup. (mvBlueCOUGAR.msi) Fixes problems during FW update. (mvBlueCOUGAR-x64.msi) BUGFIX: Automatic and Pool based memory modes work correctly again. (mvTITANfg-lib) (Bug introduced in version 1.10.31) (mvSIGMAfg-lib) (mvBlueCOUGARLocal-lib) 22.08.2008 1.10.32 NEW FEATURE: Initial version of mvIPConfigure added. (all shipped mvBlueCOUGAR related driver packages) NEW FEATURE: Info plot added to wxPropView. (wxPropView) NEW FEATURE: Average pixel values added to histogram output. (wxPropView) NEW FEATURE: Zoom added to image display window. (wxPropView) Usage: Click in the image display area and press '+' or '-'. Active when 'Scale' feature is not 'checked' only! NEW FEATURE: Properties (all shipped packages) 'mvIMPACT::acquire::Statistics::abortedRequestsCount' and 'mvIMPACT::acquire::Statistics::timedOutRequestsCount' published. NEW FEATURE: Properties (all shipped mvBlueCOUGAR related driver packages) 'mvIMPACT::acquire::StatisticsBlueCOUGAR::framesIncompleteCount' and 'mvIMPACT::acquire::StatisticsBlueCOUGAR::missingDataAverage_pc' published. NEW FEATURE: Initial version of Linux (socket based) version of the GigE Vision (mvTLIClientGigE-lib) device client driver. NEW BEHAVIOUR: The host driver uses dynamic ports for the control channel (mvTLIClientGigE-lib) now. Thus each device will communicate with a different host port from now on. BUGFIX: Some small GUI layout related bugs fixed (List control column width) (mvDeviceConfigure) BUGFIX: Default stream ports are created dynamically by the system now to (mvTLIClientGigE-lib) avoid potential port collisions when working with multiple devices in multiple processes. BUGFIX: Crashes when writing an invalid or unsupported GevCCP value to the (mvTLIClientGigE-lib) device. BUGFIX: Default message ports are created dynamically by the system now to (mvTLIClientGigE-lib) avoid potential port collisions when working with multiple devices in multiple processes. The TLI now gets notified when the message channel related parameters are changed by the user. BUGFIX: Generic GigE Vision devices can be initialised again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.10.30) BUGFIX: Timestamp_us in the request info is correct now. (mvVirtualDevice-lib) 14.08.2008 1.10.31 NEW FEATURE: error handling improved. Now driver can also detect DMA-FIFO (low level mvHYPERION driver, windows) overrun errors. NEW FEATURE: digital inputs/outputs and connector capability depends on (mvHYPERIONfg-lib) board variants. Not all mvHYPERION boards support same connectors. NEW FEATURE: Property 'mvIMPACT::acquire::Request::imageMemoryMode' published. (mvIMPACT_acquire.h) NEW FEATURE: Property 'mvIMPACT::acquire::Request::imageFooterSize' published. (mvIMPACT_acquire.h) NEW FEATURE: Function 'mvIMPACT::acquire::FunctionInterface::imageRequestConfigure' published. (mvIMPACT_acquire.h) NEW FEATURE: It's possible to capture directly into user supplied memory now. (all shipped packages) NEW FEATURE: Property 'mvIMPACT::acquire::ImageRequestControl::requestToUse' (mvIMPACT_acquire.h) published. This will allow to define the request object that shall be be used for the next acquisition. This feature might be interesting when directly capturing into user supplied memory. NEW FEATURE: min, max, step width and default value can be assigned as a string (mvPropHandling-lib) now if a translation dictionary has been defined before. NEW SAMPLE: CaptureToUserMemory (all shipped MSI based packages) UPDATE: Optimized firmware programming for mvHYPERION boards. (mvDeviceConfigure) UPDATE: Support for mvHYPERION board variants CLm and CLb added. (mvHYPERIONfg-lib) CHANGED BEHAVIOUR: EnumHyperion(), If board type is programmed without (mvHYPERIONfg-lib) the family name ("mvHYPERION") then this family name will be added to board type string to report consistent board types. CHANGED BEHAVIOUR: Property 'AcquisitionMode' moved from ImagingSubSystem (mvBlueCOUGAR-lib) into 'SystemSettings'. BUGFIX: Trigger related settings have not always been stored correctly (mvBlueCOUGAR-lib) resulting in an incorrect trigger mode after restoring a setting. Settings stored with older version of the driver should be deleted. BUGFIX: Only with application mvDeviceConfigure, if two mvHYPERIONS are (mvHYPERIONfg-lib) present always mvHYPERION0 will be opened. BUGFIX: Functions OBJ_SetP and mvIMPACT::acquire::PropertyPtr::write are (mvDeviceManager-lib) working now. BUGFIX: Crashes with AOI width of 16 for mvBlueFOX-105 types. (mvBlueFOX-lib) 04.08.2008 1.10.30 NEW FEATURE: Property 'CaptureBufferAlignment' added to C++ interface. (mvIMPACT_acquire.h) DEPRECATED API CODE: mvIMPACT::acquire::Request::getParamS and (mvIMPACT_acquire.h) mvIMPACT::acquire::Request::getImageBuffer have been declared deprecated. The information of the structures is available via direct property access now, which is more flexible and more efficient. BUGFIX: description files, that haven't been 4 byte aligned can be downloaded (mvBlueCOUGAR-lib) from the device again. (Bug introduced in version 1.10.29) 01.08.2008 1.10.29 NEW FEATURE: Direct access to HRTC's added for advanced control of (mvHYPERIONfg-lib) digital inputs and outputs(e.g. incremental encoder). NEW FEATURE: Property 'shutterMode' for mvBlueFOX devices added to C++ (mvIMPACT_acquire.h) interface. NEW FEATURE: HRTC support added for mvBlueCOUGAR-P and mvBlueLYNX-M7 devices (mvBlueCOUGAR-lib) This also requires a firmware update. (mvBlueCOUGARLocal-lib) NEW FEATURE: Property 'DigitalInputThreshold_mV' added for mvBlueLYNX-M7 (mvBlueCOUGARLocal-lib) devices. UPDATE: Reliability and update speed improved when filter driver is active. (mvTLIClientGigE-lib) (mvGigECapture.sys, version 1.0.6.7) UPDATE: Firmware version 1.00.14 for mvBlueCOUGAR-S devices added to setup (mvBlueCOUGAR.msi) The behaviour regarding IP configuration is the same for (mvBlueCOUGAR-x64.msi) mvBlueCOUGAR-S and mvBlueCOUGAR-P now. Update to FW 1.00.14 is required for mvBlueCOUGAR-S devices. After a power cycle the mvBlueCOUGAR-S devices will boot faster. UPDATE: mvBlueFOX-M105G/C is also working with mvBlueFOX.sys (old version of (mvBlueFOX-lib) the kernel driver). UPDATE: Complete revision of internal buffer handling. (all shipped packages) BUGFIX: Potential crashes when initialising two or more devices belonging (all shipped packages) to at least two different device families in parallel(e.g. each device in its own thread). BUGFIX: Pool mode of the memory manager is working again. (mvTITANfg-lib) (mvSIGMAfg-lib) BUGFIX: Update of muxdata corrected, only mvHYPERION-clf affected. (low level mvHYPERION wdm driver) BUGFIX: mvBlueFOX-M105G/C triggerOnLow and (color-)binning mode. (mvBlueFOX-lib) BUGFIX: Manual download of description file was only working after the device (mvBlueCOUGAR-lib) has been initialised. (Bug introduced in version 1.10.20) BUGFIX: Loading of stored filter parameters for 'defective pixel (mvTITANfg-lib) filter', 'Flat field filter' and 'Dark current filter' fixed. (mvSIGMAfg-lib) (mvHYPERIONfg-lib) (mvVirtualDevice-lib) === CD2008/A === 23.07.2008 1.10.28 BUGFIX: Potential deadlock when calling 'imageRequestReset' during a pending (mvBlueFOX-lib) sensor update. NEW FEATURE: message signalled interrupt added. This newer interrupt handling (low level mvHYPERION wdm driver) must be enabled for using mvHYPERION boards clf under Vista and newer windows version. Linux drivers are not affected. BUGFIX: Sometimes acquisition produces a dead_lock. This problem is related (low level mvHYPERION Linux driver) to the request_queues in the kernel_module while accessing spin_locks from user mode via read function and from interrupt context. Now spin_lock functions replaced with spin_lock_irqsave variants. BUGFIX: The digital outputs can be controlled using the local interface again. (mvBlueCOUGARLocal-lib) BUGFIX: Component::isDefault and OBJ_IsDefault did not always return correct (mvPropHandling-lib) results. UPDATE: Firmware version 1.00.13 for mvBlueCOUGAR-S devices added to setup. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) 18.07.2008 1.10.27 BUGFIX: Reliability improved, when using multiple devices in one process. (mvBlueFOX-lib) CHANGED BEHAVIOUR: A wider range of request results is returned now. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) BUGFIX: Automatic pixel format estimation was not always correct. (mvBlueCOUGAR-lib) BUGFIX: 'SensorColorPattern' was not always set correctly. (mvBlueCOUGAR-lib) BUGFIX: mvIMPACT Acquire compliant user mode library was missing in installer (mvTITAN_mvGAMMA.msi) database. (mvDELTA_mvSIGMA.msi) (Bug introduced in version 1.10.25) 16.07.2008 1.10.26 BUGFIX: Creating an instance of a class derived from (mvIMPACT_acquire.h) 'mvIMPACT::acquire::Statistics' could raise an exception. BUGFIX: Calling 'restoreDefault' for and instance of (mvIMPACT_acquire.h) 'mvIMPACT::acquire::SystemSettings' did raise an exception CHANGED BEHAVIOUR: mvBlueCOGAR-SxxxG devices will transfer ibpfMono8 unless (mvBlueCOUGAR-lib) another pixel format is explicitly selected by the user. BUGFIX: Changing the trigger or the exposure mode did not always result in a (mvBlueCOUGAR-lib) consistent deivce update. 15.07.2008 1.10.25 UPDATE: Adapter and device info will be logged now. (mvTLIClientGigE-lib) UPDATE: Abort speed improved. (mvBlueFOX-lib) UPDATE: Firmware version 1.00.12 for mvBlueCOUGAR-S devices added to setup. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) NEW FEATURE: The MSI based installers for mvDELTA/mvSIGMA and mvTITAN/mvGAMMA (mvTITAN_mvGAMMA.msi) devices will use the signed version of the kernel mode driver under (mvDELTA_mvSIGMA.msi) Windows now. Please note that these drivers can't be installed on a system that has unsigned driver versions installed. Unsigned driver packages must be removed from the system manually and no unsigned version should be installed after a signed version has been installed on the system. NEW FEATURE: 'Offset_pc' feature became available for mvBlueCOUGAR-S devices. (mvBlueCOUGAR-lib) NEW FEATURE: 'Sharpness' feature became available for mvBlueCOUGAR-S devices. (mvBlueCOUGAR-lib) BUGFIX: Certain trigger mode changes in the device specific interface did not (mvBlueCOUGAR-lib) correctly update the device (old mode was used e.g. when changing from ctmOnHighExpose to ctmOnRisingEdge. BUGFIX: Some missing visibility callbacks for AGC/AEC added. (mvBlueCOUGAR-lib) BUGFIX: supported 'non-CameraLink' devices can be initialised again. (mvTITANfg-lib) (Bug introduced in version 1.10.20) 11.07.2008 1.10.24 NEW FEATURE: DMA-Buffer handling improved. Previous versions call alloc/free (mvHYPERIONfg-lib) for each request. Now only dma_buffer will be reallocated if a size is increased through other aoi data. BUGFIX: Certain parameters in the device specific interface haven't always (mvBlueCOUGAR-lib) been set correctly directly after opening the device. BUGFIX: wxPropView could crash if the image display was switched on before (wxPropView) at least one image had been captured. (Windows only) 08.07.2008 1.10.23 BUGFIX: The zipped version of the mvBlueCOUGAR-S XML file is installed now (mvBlueCOUGAR.msi) instead of the unzipped one. (mvBlueCOUGAR-x64.msi) (Bug introduced in version 1.10.22) UPDATE: The socket based transport layer achieves a slightly better (mvTLIClientGigE-lib) performance now and device updates work much faster now. BUGFIX: The socket based transport layer did not correctly handle changed (mvTLIClientGigE-lib) destination port and changed packet size. 07.07.2008 1.10.22 BUGFIX: Small memory leak when opening a device with a zipped XML file. (mvBlueCOUGAR-lib) BUGFIX: When a network interface disappeared at runtime (when a device has (mvBlueCOUGAR-lib) been disconnected from a peer-to-peer conection a consecutive call to DMR_UpdateDeviceList caused a deadlock. NEW FEATURE: Trigger modes ctmOnRisingEdge, ctmOnFallingEdge, ctmOnHighExpose (mvBlueCOUGAR-lib) and ctmOnLowExpose implemented for mvBlueCOUGAR-S devices. (Requires at least FW version 1.00.11, driver will no longer support devices with a smaller firmware version) NEW FEATURE: Flash signal output and VD signal output implemented for (mvBlueCOUGAR-lib) mvBlueCOUGAR-S devices. (Requires at least FW version 1.00.11, driver will no longer fully support devices with a smaller firmware version) UPDATE: Firmware version 1.00.11 for mvBlueCOUGAR-S devices added to setup. (mvBlueCOUGAR.msi) (mvBlueCOUGAR-x64.msi) 03.07.2008 1.10.21 BUGFIX: Timestamps will be correct even without 'GevTimestampTickFrequency' (mvBlueCOUGAR-lib) being defined in the description file. UPDATE: Improved thread savetiness. (mvBlueFOX-lib) BUGFIX: ContinuousCaptureToAVI sample will work with mvBlueCOUGAR device as (mvBlueCOUGAR-lib) well now. (ContinuousCaptureToAVI.cpp) 26.06.2008 1.10.20 NEW FEATURE: mvIMPACT::acquire::FunctionInterface::createSetting can return (mvIMPACT_acquire.h) the ComponentList to the newly created setting now. BUGFIX: The constructor of the class CameraSettingsFrameGrabber no longer (mvIMPACT_acquire.h) raises an exception when the device using it does not support the 'TriggerControls' list. (Bug introduced in version 1.10.17) BUGFIX: mvIMPACT Lic check could fail because of some misaligned internal (mvDeviceManager-lib) structures. BUGFIX: Generic interface will work with devices that only define the (mvBlueCOUGAR-lib) the mandatory GenICam features in their description file. (mvTLIClientGigE-lib) BUGFIX: Default de-mosaicing for rolor sensors attached to mvBlueLYNX-M7 (mvBlueCOUGAR-lib) devices. UPDATE: Init speed improved. (mvBlueFOX-lib) UPDATE: Firmware update files for mvBlueCOUGAR-S devices added to installer. (mvBlueCOUGAR.msi) (version 1.0010) (mvBlueCOUGAR-x64.msi) 17.06.2008 1.10.19 UPDATE: The filter driver works with devices that send larger packets than (mvGigECapture.sys, version 1.0.4.5) promised by the SCPS register and with devices that send the last packet of a block larger than necessary now. BUGFIX: The property 'FWVersion' contains the correct version info for (mvTLIClientGigE-lib) mvBlueCOUGAR-S devices now. (mvBlueCOUGAR-lib) (Requires at least FW version 1.0007) BUGFIX: During property update the current value was written before setting (mvBlueCOUGAR-lib) the new limits. This could cause an internal exception as the current value e.g. could be larger than the old max. value. (This applies to the generic interface layout only) 10.06.2008 1.10.18 UPDATE: Additional trigger input signals added, software trigger enabled (mvHYPERIONfg-lib) CHANGED BEHAVIOUR: Trigger signal PulseStartConfiguration currently (mvHYPERIONfg-lib) removed from signal list. NEW FEATURE: Trigger signal controlled acquisition added for Linux driver (low level mvHYPERION Linux driver) BUGFIX: Sometimes the first image capture by the GigE Kernel mode capture (mvTLIClientGigE-lib) filter was incomplete. BUGFIX: Digital outputs 2 and 3 couldn't be modified in manual mode. (mvBlueCOUGARLocal-lib) NEW FEATURE: Support for 105 versions of the mvBlueFOX added. (mvBlueFOX-lib) 29.05.2009 1.10.17 NEW FEATURE: Trigger signal controlled acquisition added. (mvHYPERIONfg-lib) BUGFIX: Visibility of the features 'Expose_us' amd 'Gain_dB' depending on the (mvBlueCOUGAR-lib) settings applied to 'AutoExposeControl', 'AutoGainControl' and (mvBlueFOX-lib) 'ExposeMode'. BUGFIX: Re-programming the sensor caused aborted images after the first cycle. (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) NEW FEATURE: Firmware update for mvBlueCOUGAR-S devices added. (mvBlueCOUGAR-lib) (mvDeviceConfigure) NEW FEATURE: FrameRate_Hz feature added for mvBlueCOUGAR-S devices. (mvBlueCOUGAR-lib) NEW FEATURE: 'onHighExpose' and 'OnRisingEdge' trigger modes added for (mvBlueCOUGAR-lib) mvBlueCOUGAR-S devices. NEW FEATURE: XML file upload published for mvBlueCOUGAR-S devices. (mvBlueCOUGAR-lib) (mvDeviceConfigure) BUGFIX: Minor number confusion during initialising of more than one device. (low level mvHYPERION driver Linux) 13.05.2008 1.10.16 BUGFIX: Improved stability on Linux. (mvBlueFOX-lib) NEW FEATURE: 10 bit support added for all 'M' and 'X' types and for all (mvBlueFOX-lib) CMOS based standard types. 24.04.2008 1.10.15 BUGFIX: ReadSerialData() Timeouthandling corrected (low level mvHYPERION Windows driver) NEW FEATURE: CameraLink line receiver reset added at device init. (low level mvHYPERION Windows driver) PoCL feature enabled only with timer callbacks. BUGFIX: When multiple threads called functions accessing request object (mvDeviceManager-lib) related data internal data structures could get damaged. BUGFIX: DMR_UpdateDeviceList reports newly detected GigE Vision devices (mvBlueCOUGAR-lib) connected to a network interface that previously didn't have a valid IP address. BUGFIX: Misleading log message, Support for RGB888Planar histogram and line (wxPropView) profile. BUGFIX: Improved stability on Linux. (mvBlueFOX-lib) BUGFIX: 100% CPU load after opening a device under Kubuntu (Kernel 2.6.x). (mvBlueFOX-lib) CHANGED BEHAVIOUR: As on Linux we currently only support 16KB per USB (mvBlueFOX-lib) transfer this is also the only valid value for the property 'TransferSize' now. This might force you to modify existing code for Linux projects. UPDATE: Re-programming mvBlueCOUGAR devices in 'device specific interface' (mvBlueCOUGAR-lib) mode is much faster now. NEW FEATURE: BinningMode added to device specific interface. (mvBlueCOUGAR-lib) UPDATE: Check against matching RFS added. (mvBlueCOUGARLocal-lib) UPDATE: DMR_OpenDevice returns a larger variety of error codes now. (mvDeviceManager-lib) 11.04.2008 1.10.14 UPDATE: New version of firmware added to installer. (mvBlueCOUGAR.msi) 08.04.2008 1.10.13 BUGFIX: Unsafe close of mvHYPERION device because of wrong usage of an internal (mvHYPERIONfg-lib) index. NEW FEATURE: Certain capture related parameters no longer turn read-only during (mvBlueCOUGAR-lib) a running acquisition. NEW FEATURE: A local application running on the mvBlueCOUGAR-P can inform a (mvBlueCOUGAR-lib) host application about parameter changes now. (Requires a firmware update) 04.04.2008 1.10.12 NEW FEATURE: mvHYPERION board CL4e added. (low level mvHYPERION drivers windows and Linux) CHANGED: serial communication now completely controlled with interrupts. (low level mvHYPERION Windows driver) NEW FEATURE: wxPropView can now store image data in raw format. (wxPropView) CHANGED BEHAVIOUR: All MSI based packages will now block attempts to downgrade (all shipped MSI based packages) an installation. If this is desired please uninstall the newer version before installing the old one. BUGFIX: Icons in maintenance mode will be displayed correctly(transparent) now. (all shipped MSI based packages) BUGFIX: Min., max. and step width of properties that change dynamically at (mvBlueCOUGAR-lib) runtime are now correctly propagated up to the user interface. BUGFIX: AOI handling in device specific interface is working just like for (mvBlueCOUGAR-lib) every other mvIMPACT Acquire compliant device now. BUGFIX: Crash when closing a device operated with the mvBlueCOUGAR-P specific (mvBlueCOUGAR-lib) host interface during a running acquisition in 'Continuous' mode. 28.03.2008 1.10.11 BUGFIX: Missing 32 MHz enum added to 'TCameraPixelClock' enum (mvDriverBaseEnums.h) BUGFIX: Installation of mvTITAN/mvGAMMA devices via MSI is working correctly (mvTITAN_mvGAMMA.msi) again. (Bug introduced in version 1.10.10) UPDATE: Revision of the local interface. Higher frame rates can be achieved (mvBlueCOUGARLocal-lib) now and support for the class mvIMPACT::acquire::ImageMemoryManager has been added. 14.03.2008 1.10.10 BUGFIX: The device specific interface for mvBlueCOUGAR-P devices didn't (mvBlueCOUGAR-lib) convert Bayer image data correctly. (mvTLIClientGigE-lib) CHANGED BEHAVIOUR: Some logging mechanisms changed. Now a common *.log file (mvBlueCOUGAR-lib) is used. (mvTLIClientGigE-lib) BUGFIX: Power over CameraLink temporarily removed. (mvHYPERION low level Linux HW driver) (mvHYPERION low level windows HW driver) 06.03.2008 1.10.9 BUGFIX: Medium camera support, synchronization of the medium channels (mvHYPERION low level Linux HW driver) improved. BUGFIX: Power over CameraLink is working on Linux now. (mvHYPERION low level Linux HW driver) BUGFIX: Runtime crashes during process termination on Linux when more (all shipped packages) than one driver lib was present. BUGFIX: The property 'pixelClock_KHz' is bound correctly in the C++ layer now. (mvBlueCOUGAR-lib) 03.03.2008 1.10.8 BUGFIX: CL comlibs (mvHYPERION and mvTITAN/mvGAMMA packages) BUGFIX: Resetting the trigger mode when closing and re-opening the device (mvSIGMA/mvDELTA low level HW driver) 19.02.2008 1.10.7 CHANGED BEHAVIOUR: The class mvIMPACT::acquire::AutoControlParametersBlueFOX (mvIMPACT_acquire.h) has been renamed to mvIMPACT::acquire::AutoControlParameters and is no available in the class mvIMPACT::acquire::CameraSettingsBlueDevice thus is no longer restricted to the mvBlueFOX. This will not break existing binaries, but might force you to change your code during rebuilds when directed references to this class have been used. CHANGED BEHAVIOUR: The properties autoExposeControl and autoGainControl have (mvIMPACT_acquire.h) been moved to the base class from mvIMPACT::acquire::CameraSettingsBlueFOX to mvIMPACT::acquire::CameraSettingsBlueDevice. This will not affect existing binaries or code. CHANGED BEHAVIOUR: Property 'exposeMode' moved to base class (mvIMPACT_acquire.h) mvIMPACT::acquire::CameraSettingsBlueDevice. BUGFIX: The request count can be modified again. (all shipped packages) (Bug introduced in version 1.10.6) BUGFIX: Calling the import, export and copy function of a camera description (mvDeviceManager-lib) results in the desired behaviour now. NEW FEATURE: mvBlueFOX compatible overlapped expose mode implemented. (mvBlueCOUGAR-lib) (Requires FW update to version 1.0.11) NEW FEATURE: CameraLink grabbers now can sort the pixel data if needed from (mvHYPERIONfg-lib) multi-tap cameras if needed. (mvTITANfg-lib) BUGFIX: Closing the device is working correctly again. (mvHYPERIONfg-lib) (Bug introduced in version 1.10.6) 12.02.2008 1.10.6 BUGFIX: mvDeviceConfigure no longer displays an error on startup when no (mvDeviceConfigure) mvBlueCOUGAR driver is installed. (Bug introduced in version 1.10.4) NEW BEHAVIOUR: mvHYPERION buffer alignment increased to 64k (mvHYPERIONfg-lib) NEW BEHAVIOUR: now mvHYPERION Linux kernel also support ppc64 systems (mvHYPERION low level HW driver) BUGFIX: The correct version of the GigE Kernel mode capture filter is (mvBlueCOUGAR.msi) installed again on Windows XP an newer. (Bug introduced in version 1.10.5) BUGFIX: mvGigEConfigure is installing the capture filter driver correctly (mvGigEConfigure) even it hasn't been installed previously using the the method offered by the Windows OS. UPDATE: mvGigEConfigure is started from the MSI based installer and directly (mvBlueCOUGAR.msi) installs the driver now. Installation process creates shortcuts to mvGigEConfigure now. BUGFIX: Parallel installation of the MSM files of the mvIMPACT Acquire base (all shipped MSI based packages) libs (mvIMPACT_AcquireBaseLibs.msm) could mess up the OS internal component data base. This could happen, if installations for two different product groups both installed the merge modules during the installation process, which isn't done by default. NEW BEHAVIOUR: The environment variables MVIMPACT_ACQUIRE_DIR and GENICAM_ROOT (all shipped MSI based packages) will now overwrite existing values while in previous installations the new values where appended ';' separated to the existing values. BUGFIX: 'Flat Field Filter' and 'Dark Current Filter' could cause crashes, if (all shipped packages) no settings have been loaded for the device and the calibration mode was switched on in live mode. BUGFIX: Files that are not DWORD aligned can be downloaded now. (mvBlueCOUGAR-lib) NEW FEATURE: Soft AGC and AEC feature added to mvBlueCOUGAR-P specific (mvBlueCOUGAR-lib) interface. BUGFIX: Correct numbering of mvSIGMA-SQ boards. (mvSIGMAfg-lib) BUGFIX: Correct handling of digital IOs of mvSIGMA boards. (mvSIGMAfg-lib) BUGFIX: Calling 'imageRequestReset' didn't unlock the current request, which (mvSIGMA/mvDELTA low level HW driver) could result in a delay during the close that was equal to the value of the property 'ImageRequestTimeout_ms' for that request. BUGFIX: Closing a board did not unlock the current request, which could result (mvSIGMAfg-lib) in a delay during the close that was equal to the value of the (mvTITANfg-lib) property 'ImageRequestTimeout_ms' for that request. BUGFIX: XML log files can be viewed at runtime an will always be valid XML. (all shipped packages) NEW FEATURE: Version info of the mvPropHandling lib is stored in a XML setting (mvPropHandling-lib) in the top-level list now. NEW FEATURE: Update device list menu entry. (mvDeviceConfigure) 24.01.2008 1.10.5 NEW FEATURE: First version using the new version of the propgrid(1.2.11). (wxPropView) NEW FEATURE: CameraSettingsBlueCOUGAR::triggerSource and (mvIMPACT_acquire.h) CameraSettingsBlueCOUGAR::triggerInterface feature added. NEW FEATURE: Initial version of mvGigEConfigure added. (mvBlueCOUGAR.msi) NEW FEATURE: Detection of GigE Vision devices on host systems with more (mvTLIClientGigE-lib) than one network adapter that has been assigned a zero-conf IP address. NEW FEATURE: Multiple streams per device are now supported. (mvTLIClientGigE-lib) NEW FEATURE: Windows 2000 support added to GigE Vision capture kernel driver. (mvBlueCOUGAR.msi) On Windows 2000 platforms a different version of the kernel mode filter. NEW FEATURE: New configuration tool added to installer: mvGigEConfigure (mvBlueCOUGAR.msi) This is meant to allow an easy installation and configuration of the GigE Vision capture kernel driver. BUGFIX: Creating a stream was resetting the upper 16 bit of the port register. (mvTLIClientGigE-lib) BUGFIX: Firmware version is displayed correctly in the log file now for (mvBlueCOUGAR-lib) mvBlueCOUGAR-P devices. BUGFIX: Changing the 'AdapterIPAddress' property will update the 'AdapterName' (mvBlueCOUGAR-lib) and 'AdapterDescription' property now. BUGFIX: Internal timeout for device discovery increased in order to be (mvBlueCOUGAR-lib) compliant with the recommendation of the GigE specification. BUGFIX: The imageDir mode sometimes internally created an invalid path (mvVirtualDevice-lib) which resulted in no images being read from the specified directory. (Linux only) NEW FEATURE: TestImageBarWidth property. (mvVirtualDevice-lib) 14.01.2008 1.10.4 BUGFIX: When multiple threads where calling DMR_GetImpactRequestBufferEx (mvDeviceManager-lib) with the 'ibfUseRequestMemory' set and at least two threads where asking for a packed RGB or an YUV format it could happen that the content of the returned image buffers contained a mixture of the individual images. BUGFIX: 'MissingData_pc' property wasn't calculated correctly in chunk mode. (mvBlueCOUGAR-lib) NEW FEATURE: mvDeviceConfigure can now be used to assign a new IP address (mvDeviceConfigure) to a GigE Vision compliant device. (mvTLIClientGigE-lib) CHANGED BEHAVIOUR: Internal native socket default buffer size increased. (mvTLIClientGigE-lib) CHANGED BEHAVIOUR: If no EEPROM info could be found the device is listed with (mvSIGMAfg-lib) a default serial number (MV000000000). (mvTITANfg-lib) UPDATE: new HWUpdateFunction added, only for HW Testing (mvSIGMAfg-lib) 08.01.2008 1.10.3 BUGFIX: internal use of AOI-Parameter was wrong for cameras with more than (mvHYPERIONfg-lib) one tap. NEW FEATURE: mvIMPACT Acquire compatible trigger handling for mvBlueCOUGAR-P (mvBlueCOUGAR-lib) devices. CHANGED BEHAVIOUR: The increment for the AOI width property has been changed (mvHYPERIONfg-lib) from 4 to 8. 17.12.2007 1.10.2 BUGFIX: Open -> Close -> Open resulted in no more images being captured. (mvTLIClientGigE-lib) NEW FEATURE: Support for digital output 3 and 4 added. (mvBlueCOUGAR firmware and GenICam XML-file) 12.12.2007 1.10.1 NEW FEATURE: Power over CameraLink added to the low level kernel (mvHYPERION low level HW driver) drivers. This feature needs hardware revision >= 2.xx of HYPERION-CLe. CameraLink clock detection available for hardware revision < 2.xx. NEW FEATURE: Digital inputs and additional digital outputs connector J6 (mvHYPERIONfg-lib) added to IOSubSystem. This feature depends on firmware version and will be available from firmware version 35 onwards. BUGFIX: Potential memory leak when closing the device while image requests (mvBlueFOX-lib) are still in the input queue. NEW FEATURE: Support for the 10 bit version of the mvBlueFOX added. (mvBlueFOX-lib) BUGFIX: Certain low level USB HW initialisation errors are passed up to the (mvBlueFOX-lib) user now. BUGFIX: Flash update added for mvHYPERION boards. (mvDeviceConfigure) (bug related to Linux compilation of mvDeviceConfigure) NEW FEATURE: Handling of default_flash configuration added. (mvHYPERION low level HW driver) 21.11.2007 1.10.0 CHANGED BEHAVIOUR: Functions and classes that have been declared deprecated (mvIMPACT_acquire.h) for some time now have been removed from the C++ interface. This will not break existing binaries, but will force you to change your code during rebuilds when deprecated code was used by your application. A list of functions that have been removed and their replacement can be found in the device drivers manual under 'C/C++ developer -> Porting existing code' BUGFIX: Camera description files that contain a '.' in their name couldn't be (mvHYPERIONfg-lib) reloaded after exporting them, when trying to create a camera (mvTITANfg-lib) description, that was already existing no error message was returned, (mvSIGMAfg-lib) Camera descriptions that contained 'Generic' as part of their name couldn't be exported and imported. BUGFIX: Local XML files no longer have to be DWORD aligned to be downloadable. (mvBlueCOUGAR-lib) NEW FEATURE: Initial version of the GigE Vision capture kernel driver added (mvBlueCOUGAR.msi) to setup. BUGFIX: line scan mode: only first request will synchronize to next line, (mvHYPERION low level HW driver) following request transfer directly next lines without breaks BUGFIX: digital io passthrough mode, inverted / notinverted can't be switched (mvHYPERION low level HW driver) BUGFIX: snap request with timeout = 0 never elapses. (mvHYPERION low level HW driver) 07.11.2007 1.9.17 BUGFIX: When programming periodically Pulse sequence on a digital output (mvHYPERIONfg-lib) then it is now possible to define a longer pulse than the period of the signal. BUGFIX: Non-standard lists under ImagingSubSystem/Camera will be stored as (mvBlueCOUGAR-lib) well now. BUGFIX: Log output can be configured through mvDebugFlags.mvd now. (mvTLIClientGigE-lib) NEW FEATURE: wxPropView can draw overlays from special strings attached to the (wxPropView) request. 01.11.2007 1.9.16 BUGFIX: Device specific interface for the mvBlueCOUGAR is working again. (mvBlueCOUGAR-lib) (Bug introduced in version 1.9.15) NEW FEATURE: GenICam files will be searched under a specific directory (mvBlueCOUGAR-lib) now if the device specifies the URL as a file. (mvBlueCOUGAR.msi) On Windows this directory will be %ALL USERS\Documents\MATRIX VISION\mvIMPACT Acquire\GenICam, on Linux it will be $HOME/etc//matrix-vision/mvimpact-acquire/genicam NEW FEATURE: IO subsystem improved, now it is possible to program single pulse (mvHYPERIONfg-lib) and pulse sequences to digital output. New IO-System is not compatible to previous version. NEW FEATURE: Flash update added for mvHYPERION boards. (mvDeviceConfigure) BUGFIX: Grey 8x4 medium mode, every 8 pixel was dark. (mvHYPERIONfg-lib) BUGFIX: Abort function, if switch off camera during acquisition sometimes no reaction of the application any more. (mvHYPERIONfg-lib) NEW FEATURE: Firmware version will now be reported. (mvHYPERIONfg-lib) 31.10.2007 1.9.15 BUGFIX: When a digital output was switched to 'Manual' the device was set up (mvBlueCOUGAR-lib) for flash output and vice versa. (Device specific interface only) BUGFIX: AcquisitionMode changes haven't been taken into account. (mvBlueCOUGAR-lib) (Device specific interface only) 29.10.2007 1.9.14 BUGFIX: Time stamp works correctly with every GEV compliant device now that correctly (mvBlueCOUGAR-lib) implements the time stamp tick frequency registers and the timestamp itself. BUGFIX: 64-bit int properties that define a hex format string haven't been (mvPropHandling-lib) assigned correctly when writing the string value without leading '0x' (e.g. "c0a8001212"). BUGFIX: MFC version of PropView can be compiled again. (Bug introduced in version 1.9.8) BUGFIX: TImpactBufferFlag::ibfRecyleBufHandle became (mvDeviceManager.h) TImpactBufferFlag::ibfRecycleBufHandle (spelling mistake). This will not break existing binaries, but will force you to change your code during rebuilds when this flag was used by your application. CHANGED BEHAVIOUR: The translation dictionary entries for the property (mvBlueFOX-lib) SensorColorPattern have been adapted to all other occurrences of these strings in other drivers(camera descriptions etc.). UPDATE: Improved stability. (mvBlueCOUGAR-lib) NEW FEATURE: When the resulting IMPACT image buffer returned by a device (all shipped packages) is a raw Bayer image, the IMPACT buffer will be allocated with the Bayer image buffer type IPL_BAYERMOSAICBUF now. NEW FEATURE: Property 'TriggerMoment' added to class (mvIMPACT_acquire.h) mvIMPACT::acquire::PulseStartCOnfiguration 23.10.2007 1.9.13 CHANGED BEHAVIOUR: TBlueLYNXCameraExposeMode has been replaced by (mvIMPACT_acquire.h) TCameraExposeMode. NEW FEATURE: mvBlueCOUGAR specific interface layout enhanced and some (mvBlueCOUGAR-lib) minor bugs fixed. CHANGED BEHAVIOUR: Execution of mvIMPACT::acquire::Method::call and (mvPropHandling-lib) OBJ_Execute speeded up a little. NEW FEATURE: New error code added to TRequestResult enum: rrDeviceAccessLost (mvDriverBaseEnums.h) === CD2007/A === 15.10.2007 1.9.12 BUGFIX: YUV422Packed mode is returned correctly now for mvTITAN-RGB boards. (mvTITANfg-lib) NEW FEATURE: FVAL-PassThrough mode is possible for mvTITAN/mvGAMMA-CL. (mvTITANfg-lib) (mvTITAN/mvGAMMA low level HW driver) BUGFIX: Trigger-Out can be used via pulse sequences also for mvGAMMA-CL. CHANGED BEHAVIOUR: initialiseHW ( Loading FPGA ) is always done by default (mvTITANfg-lib) for TITAN boards. BUGFIX: 64-bit integer properties can be read as 32-bit values now. (mvPropHandling-lib) This however is NOT recommended as it might result in loss of data and is just meant for compatibility reasons. BUGFIX: Left-right mirror in YUV422-packed mode flipped the Y components (mvSIGMAfg-lib) incorrectly. NEW FEATURE: Initial version of the mvBlueCOUGAR specific C++ interface. (mvIMPACT_acquire.h) NEW FEATURE: Function mvIMPACT::acquire::Property::allowsValueCombinations, (mvIMPACT_acquire.h) class mvIMPACT::acquire::PulseStartConfiguration, mvIMPACT::acquire::IOSubSystem::getPulseStartConfiguration, mvIMPACT::acquire::IOSubSystem::getPulseStartConfigurationCount, mvIMPACT::acquire::OutputSignalGeneratorFrameGrabber:: getValidSignalsForPassThroughModes, mvIMPACT::acquire::OutputSignalGeneratorFrameGrabber:: getValidPassThroughSignalCount, mvIMPACT::acquire::OutputSignalGeneratorFrameGrabber:: getValidPassThroughSignalValue, mvIMPACT::acquire::OutputSignalGeneratorFrameGrabber:: getValidPassThroughSignalString mvIMPACT::acquire::OutputSignalGeneratorFrameGrabber:: definePassThroughSignal. CHANGED BEHAVIOUR: The class mvIMPACT::acquire::ImageProcessingBlueFOX (mvIMPACT_acquire.h) is no longer available. As all its features are available for every device there is only one class mvIMPACT::acquire::ImageProcessing now. Please replace every occurrence of mvIMPACT::acquire::ImageProcessingBlueFOX or mvIMPACT::acquire::ImageProcessingBase in your code by mvIMPACT::acquire::ImageProcessing. This change will NOT break existing binaries thus compiled software already shipped will continue to work! CHANGED BEHAVIOUR: Creating an instance of (mvIMPACT_acquire.h) mvIMPACT::acquire::IOSubSystemBlueFOX no longer raises an internal exception. This is NOT a bugfix but purely cosmetics. 24.09.2007 1.9.11 BUGFIX: mvBlueFOX-102aG could cause footer errors. (mvBlueFOX-lib) New FPGA version 68. 19.09.2007 1.9.10 BUGFIX: The properties 'HDOutput', 'VDOutput' and 'pixelClockOutput' (mvIMPACT_acquire.h) were mapped to an incorrect data type. NEW FEATURE: mvIMPACT::acquire::Request::getInfoIterator function added. (mvIMPACT_acquire.h) NEW FEATURE: The visible data from the info list of a request can be (wxPropView) displayed as an overlay now. BUGFIX: Closing a device in debug builds could result in a heap corruption. (mvTITAN/mvGAMMA low level HW driver) NEW FEATURE: Timeout handling and property 'ImageRequestTimeout_ms' (mvBlueCOUGAR-lib) implemented. BUGFIX: First image is received correctly now. (mvBlueCOUGAR-lib) NEW FEATURE: FrameID as part of the Request infos implemented. (mvBlueCOUGAR-lib) NEW FEATURE: Support for chunk mode added. (mvBlueCOUGAR-lib) 04.09.2007 1.9.9 NEW BEHAVIOUR: 'Abort' button enabled during running live acquisition. (wxPropView) BUGFIX: Missing merge module mvBlueFOXKernelDriver.msm added to 32-bit (mvBlueFOX.msi) installer package (Windows only). NEW FEATURE: The saturation filter can be used with RGB destination formats (mvBlueFOX-lib) as well now. NEW FEATURE: Support for mvBlueCOUGAR devices added (so far Windows only). (mvBlueCOUGAR-lib) (mvTLIClientGigE-lib) 15.08.2007 1.9.8 DEPRECATED API CODE: mvIMPACT::acquire::Request::getInfo and (mvIMPACT_acquire.h) mvIMPACT::acquire::Request::getResult have been declared deprecated. The information of the structures is available via direct property access now, which is more flexible and more efficient. BUGFIX: DMR_GetImageRequestInfo and DMR_GetImageRequestInfoEx and (mvDeviceManager-lib) mvIMPACT::acquire::Request::getInfo returned DMR_INTERNAL_ERROR as internally this parameter became 64-bit integer but was handled as a 32-bit integer. For backward compatibility this parameter will be truncated to 32-bit now but the use of this functions is not recommended any more. Also see comments above made above. (Bug introduced in version 1.9.7) NEW FUNCTION: DMR_UpdateDeviceList, (mvDeviceManager-lib) mvIMPACT::acquire::DeviceManager::updateDeviceList (mvIMPACT_acquire.h) BUGFIX: File mode didn't work correctly when damaged image files where present (mvVirtualDevice-lib) in the selected directory. NEW FEATURE: Timestamp property implemented for request results. (mvVirtualDevice-lib) NEW BEHAVIOUR: As only the mvBlueFOX-124C and mvBlueFOX-102C support vertical (mvBlueFOX-lib) color binning at the moment, vertical and full binning is no longer available for other color versions of the mvBlueFOX. NEW BEHAVIOUR: The two buttons 'Live' and 'Stop' have been replaced by one (wxPropView) 'Live' Push-Button BUGFIX: Bayer pattern for the color version of the mvBlueFOX-102C is decoded (mvBlueFOX-lib) correctly again. BUGFIX: Crashes when switching between developers view and standard view (wxPropView) while the selected device wasn't initialised. BUGFIX: dma_error handling improved, multitasking problem fixed (mvHYPERION low level HW_WDM_driver) BUGFIX: abort_request function improved, waits now until last request will be signalled. (mvHYPERION low level HW_WDM_driver) 27.07.2007 1.9.7 BUGFIX: Potential memory leak fixed. (mvBlueFOX-lib) BUGFIX: Changes stored in the system settings list will be updated (mvHYPERIONfg-lib) automatically at start-up. (mvTITANfg-lib) (mvSIGMAfg-lib) (mvVirtualDevice-lib) BUGFIX: Gain wasn't set correctly, when video channel was changed. (mvTITANfg-lib) NEW FEATURE: RequestInfo: Property 'TimeStamp_us' is now a 64-bit integer. (mvHYPERIONfg-lib) (mvSIGMAfg-lib) (mvVirtualDevice-lib) (mvBlueFOX-lib) (mvTITANfg-lib) BUGFIX: calculation lost images corrected (mvHYPERIONfg-lib) BUGFIX: time stamp calculation corrected (mvHYPERION low level HW_WDM_driver) 24.07.2007 1.9.6 BUGFIX: Combo box controls display the correct initial value again. (wxPropView) (Bug introduced in version 1.9.5) NEW FEATURE: Doc string feature added to camera descriptions. (mvHYPERIONfg-lib) (mvSIGMAfg-lib) (mvTITANfg-lib) NEW BEHAVIOUR: general fpga_reset removed from abort_function uart_init changed, now only minimal register access added. (mvHYPERION low level HW driver) 19.07.2007 1.9.5 BUGFIX: Writing image results improved. (mvHYPERIONfg-lib) (Linux only) BUGFIX: Cancelling of a process now works correct. (mvHYPERIONfg-lib) BUGFIX: Serial port now works with interrupt. (mvHYPERIONfg-lib) BUGFIX: Undefined symbols error when opening an mvHYPERION on Linux from (mvHYPERIONfg-lib) an application that dynamically loads the mvDeviceManager-lib BUGFIX: In case of USB Bus related transmission errors the data transfer (mvBlueFOX-lib) will be restarted faster and more reliable now. BUGFIX: Linux only: Closing and reopening a mvBlueFOX device no longer (mvBlueFOX-lib) causes a segmentation fault. BUGFIX: Linux only: Closing and reopening a mvBlueFOX device no longer (mvBlueFOX-lib) creates an unused thread. BUGFIX: Linux only: 2 extra, unused threads no longer created for (mvBlueFOX-lib) mvBlueFOX. BUGFIX: Switching the property 'FooterMode' from 'Off' to any other value (mvBlueFOX-lib) while the driver was busy processing image requests could lead to heap corruptions. BUGFIX: clserialWrite() result corrected (mvHYPERION-kernel-Linux) BUGFIX: Undefined symbols error when opening an mvBlueFOX on Linux from (mvBlueFOX-lib) an application that dynamically loads the mvDeviceManager-lib BUGFIX: High CPU load under wxPropView after opening the camera. (mvBlueFOX-lib) (Bug introduced in version 1.7.2, Linux only) NEW FEATURE: VB 6 sample uses enumerated properties now as well. (all shipped MSI-packages) NEW FEATURE: First version using the new version of the propgrid(1.2.7). (wxPropView) 14.06.2007 1.9.4 BUGFIX: 8 bit bitmap export changed the image data in a way that the exported (wxPropView) image had a different histogram. BUGFIX: mvShowDisplayWindow sometimes returned too early (before all internal (mvDisplay-lib) data structures have been set up correctly). BUGFIX: Property 'Info/DeviceDriverVersion' returns a correct release number (all shipped packages) again. (Bug introduced in version 1.9.2) BUGFIX: When an mvTITAN-RGB/G4 was operated in PAL mode certain error (mvTITANfg-lib) conditions e.g. a wrong pixel clock couldn't be detected correctly. BUGFIX: Loading of settings during device init didn't update all the (mvTITANfg-lib) properties (e.g. Connector/cameraOutputUsed) correctly. (mvSIGMAfg-lib) BUGFIX: The request info 'frameID' is now visible for the mvBlueFOX. (mvBlueFOX-lib) Fixed issue with frame on demand mode/single frame capture mode. Minor timing fixes. Repaired CCD 'expose on high' trigger mode. Improved camera softstart by new firmware version 41. NEW FEATURE: New compatible way to handle the user data in case of a reconnect (mvBlueFOX-lib) event for a device added. Now the user can select whether he wants the cached data or if he wants the data to be refreshed from the devices non-volatile memory. See property 'ReconnectBehaviour' for details. BUGFIX: Critical Section added to the handling of common resoures for (mvHYPERIONfg-lib) request-function and waitforrequest-function. NEW FEATURE: Medium camera support added. (mvHYPERIONfg-lib) NEW BEHAVIOUR: PWM Super-Softstart for mvBlueFOX devices added to firmware. (mvBlueFOX-lib) (-> Firmware version 41) CHANGED: The translation string of the enum value 'rrOK' changed from (all shipped packages) 'Ready' to 'OK'. 23.05.2007 1.9.3 BUGFIX: The displayed AOIs in scaled display mode used unscaled offsets. (wxPropView) BUGFIX: Under certain 32-bit Linux distributions wxPropView could crash (wxPropView) while playing around with the spin controls for the histogram and line profile. NEW FEATURE: Colour to channel description mapping added to histogram and (wxPropView) line profile. BUGFIX: 'ctmOnDemand' trigger mode for mvBlueFOX 102ag (mvBlueFOX-lib) CHANGED: Min. width of the image for mvBlueFOX-102ag versions reduced from (mvBlueFOX-lib) 200 to 20. BUGFIX: Capturing 2-4 sync. grey sources (co2xComposite, co3xComposite, (mvTITANfg-lib) co4xComposite mode) resulted in incorrect images for the mvTITAN-RGB/G3 and mvTITAN-RGB/G4. (Bug introduced in version 1.7.5 with the introduction of the scaler feature) NEW FEATURE: Signed 64-bit Windows driver available for mvHYPERION and (mvBlueFOX-x64.msi) mvBlueFOX. These packages will run under every amd64/x64 based (mvHYPERION-x64.msi) Windows version including Windows Vista. NEW FEATURE: New pixel formats introduced: ibpfRGB101010Packed, (all shipped packages) ibpfRGB121212Packed, ibpfRGB141414Packed, ibpfRGB161616Packed. UPDATE: Newer MSI compiler used to create Windows installer packages. (all shipped MSI based packages) 23.04.2007 1.9.2 BUGFIX: Calling DMR_GetImageRequestBufferImageData after a failed call to (mvDeviceManager-lib) DMR_ImageRequestWaitFor could lead to crashes. BUGFIX: Reading from the digital inputs of an mvGAMMA-CL or an mvTITAN-CL (mvTITANfg-lib) returned incorrect results (triggerIN and syncIN have been flipped). BUGFIX: max. offsets for X/Y offsets for histogram and line profile. (wxPropView) BUGFIX: Spin controls will be used for properties defining a min. and max. (wxPropView) value again. (Bug introduced in version 1.9.0) UPDATE: Calibration parameters are available again for fine tuning (mvBlueFOX-lib) the mvBlueFOX (CCD versions only). NEW FEATURE: class CameraDescriptionManager provides enhanced 'locate (mvIMPACT_acquire.h) description via string' functionality now. Either the list name or value of the property 'name' of the description can be passed to the corresponding location function now. NEW FEATURE: 64-bit Windows driver available. Currently this driver can't be (mvBlueFOX-x64.msi) installed on Windows Vista, as it's still not certified and Windows Vista doesn't allow uncertified drivers to be installed. NEW FEATURE: mvVirtualDevice driver available for testing and/or developing (mvVirtualDevice.msi) on Windows (32 and 64-bit) without MATRIX VISION hardware. (mvVirtualDevice-x64.msi) NEW FEATURE: Trigger modes 'ctmOnDemand', 'ctmOnRisingEdge', 'ctmOnLowLevel' (mvBlueFOX-lib) and 'ctmOnHighLevel' for mvBlueFOX-102aG devices. NEW FEATURE: Trigger mode 'ctmContinuous' works with mbBlueFOX-102 devices (mvBlueFOX-lib) under USB 1.1 now. NEW FEATURE: The histogram now also displays the pixel value where most values (wxPropView) have been detected. NEW FEATURE: Some additional request info properties became accessible for (mvTITANfg-lib) certain devices. (line counter for mvGAMMA-CL, mvTITAN-CL and mvTITAN-DIG) 17.04.2007 1.9.1 BUGFIX: Some missing references to namespace 'std' added in function (mvIMPACT_acquire.h) CameraDescriptionManager::update. NEW FEATURE: 64-bit integer properties now also available under .NET (mvIMPACT_acquire.h) NEW FEATURE: VB 6 sample provides more usable functions and types now (all shipped MSI-packages) UPDATE: Low level Linux kernel drivers direct transfer version simplified. (low level mvHYPERION Linux kernel) With the versions before it was not possible to close the capture stream from the camera. Every second image was lost. Also digital I/O subsystem expanded. BUGFIX: memory leak removed Hyperion_lib deletes now all initialised (mvHYPERIONfg-lib) modules. 12.04.2007 1.9.0 BUGFIX: DMR_CloseDevice doesn't return DMR_NOT_INITIALIZED on a successful (mvDeviceManager-lib) device close any more. BUGFIX: HRTC programs stored with versions older than 1.8.2 could not be read (mvPropHandling-lib) with current versions of the driver any more. BUGFIX: Increasing the number of request objects by writing to the (mvSampleDevice-lib) 'RequestCount' property is working now. (mvBlueCOUGAR-lib) (mvBlueLYNX-lib) NEW FEATURE: Support for 64-bit integer properties. (all shipped packages) NEW FEATURE: Some new component flags added. (mvPropHandling-lib) NEW FEATURE: Property 'flashType'. (mvBlueFOX-lib) NEW FEATURE: wxPropView can be used to store a recorded sequence to disk (wxPropView) NEW BEHAVIOUR: The default doc-string is an empty string now. (mvPropHandling-lib) NEW BEHAVIOUR: The default format string for pointer properties (vtPtr) (mvPropHandling-lib) is "0x%x" now, while it used to be "%x". NEW BEHAVIOUR: The translation dictionary of the property 'triggerMode' (mvBlueFOX-lib) only contains modes, which are available for the sensor installed in the camera now. 20.03.2007 1.8.7 BUGFIX: mvTITAN/mvGAMMA devices can be initialised again. (mvTITANfg-lib) (Bug introduced in version 1.8.6) UPDATE: mvTITAN/mvGAMMA devices can be used with Windows Vistas Aero layout. (low level HW driver) UPDATE: mvDELTA/mvSIGMA devices can be used with Windows Vistas Aero layout. (low level HW driver) 14.03.2007 1.8.6 BUGFIX: Calling DMR_GetDevice (or mvIMPACT::acquire::DeviceManager::getDevice) (mvDeviceManager-lib) with an empty search string could result in a crash. BUGFIX: Calculation of vertical start position for non-interlaced cameras (mvSIGMAfg-lib) corrected. NEW FEATURE: All MSI-based installer packages work on Windows Vista now. (all shipped MSI based packages) NEW FEATURE: 8 bpp BMP support added. (wxPropView) NEW FEATURE: Tool tip support added to property grid. (wxPropView) NEW FEATURE: Devices can store/load filter parameters for 'defective pixel (mvTITANfg-lib) filter', 'Flat field filter' and 'Dark current filter' now. (mvSIGMAfg-lib) (mvHYPERIONfg-lib) (mvBlueCOUGAR-lib) (mvBlueLYNX-lib) CHANGED BEHAVIOUR: mvDeviceManager no longer writes a log-file if none has (mvDeviceManager-lib) has been specified via mvDebugFlags.mvd or if mvDebugFlags.mvd couldn't be located. 12.03.2007 1.8.5 BUGFIX: DeviceManager classes close devices only when the last instance to (mvIMPACT_acquire.h) the device manager is destroyed. (mvDeviceManager-lib) BUGFIX: When AGC and AEC where switched on and the initial exposure time was (mvBlueFOX-lib) higher than the max. exposure time defined by the AEC controller the controller circuit used incorrect exposure times. BUGFIX: class mvIMPACT::acquire::WhiteBalanceSettings did incorrectly bind (mvIMPACT_acquire.h) the interface property greenGain to the drivers blueGain and vice versa. BUGFIX: Certain format conversion after a Bayer conversion didn't work. (all shipped packages) NEW FEATURE: PNG support added. (wxPropView) NEW FEATURE: YUV histogram and profile support added. (wxPropView) 22.02.2007 1.8.4 BUGFIX: YUV422Planar is displayed correctly now on platforms that don't (wxPropView) support RAW BITMAP access. BUGFIX: Some internal pixel format conversions on arm platforms. (all shipped packages) BUGFIX: Loading previously stored correction data for the defective pixels (mvBlueFOX-lib) filter is working now. BUGFIX: Loading a setting at runtime after opening a device did not update (all shipped packages) all data stored by some image processing filters. NEW FEATURE: Initial version of the I/O Subsystem. (mvHYPERIONfg-lib) NEW FEATURE: Mirror function supports the formats ibpfRGBx888Planar, ibpfYUV422Packed (all shipped packages) and ibpfYUV422Planar now. NEW FEATURE: Deprecated interface functions, types, structs and classes will (mvIMPACT_acquire.h) result in a compile time warning if supported by the compiler. CHANGED BEHAVIOUR: mvIMPACT::acquire::ComponentIterator prefix ++ operator (mvIMPACT_acquire.h) return a self reference now. CHANGED BEHAVIOUR: C++ sample 'Properties' redesigned. 15.02.2007 1.8.3 NEW FEATURE: The device list now contains a new property 'DeviceClass' (all shipped packages) NEW FEATURE: Major revision of pixel format conversion section. (all shipped packages) BUGFIX: Some internal pixel format conversions (all arm builds) CHANGED BEHAVIOUR: mvBlueFOX-102aG cameras have a higher default gain now. (mvBlueFOX-lib) The default gain has been increased by a factor of 1.375. This will result in brighter images when changing the driver version. 12.02.2007 1.8.2 BUGFIX: Corrupt or inconsistent settings could lead to incomplete updates (mvPropHandling-lib) BUGFIX: Reading a property's attributes (such as min. or max.) performs a (mvPropHandling-lib) data type check now. BUGFIX: in class mvIMPACT::acquire::WhiteBalanceSettings the properties (mvIMPACT_acquire.h) 'redGain', 'blueGain', 'greenGain' and 'totalGain' have been declared as integer properties while they are float properties. BUGFIX: missing assignment operator added to class mvIMPACT::acquire::Device. (mvIMPACT_acquire.h) BUGFIX: Cameras reach full frame rates again. (mvBlueFOX-lib) (Bug introduced in version 1.8.0) CHANGED BEHAVIOUR: Type checks added to constructors of Property, Method and (mvIMPACT_acquire.h) ComponentList classes. CHANGED BEHAVIOUR: The property 'Name' of each user data entry in the device (mvBlueFOX-lib) list is no longer allowed to start with a '!' character. 06.02.2007 1.8.1 NEW FEATURE: Class 'mvIMPACT::acquire::ImageMemoryManager' added. (mvIMPACT_acquire.h) CHANGED BEHAVIOUR: mvIMPACT::acquire::TMemManMode has been renamed to (mvIMPACT_acquire.h) mvIMPACT::acquire::TMemorymanagerMode, enums value names now start with 'mmm' instead of 'mm'. CHANGED BEHAVIOUR: mvIMPACT::acquire::TPoolMode has been renamed to (mvIMPACT_acquire.h) mvIMPACT::acquire::TMemoryManagerPoolMode, enums value names now start with 'mmpm' instead of 'pm'. 01.02.2007 1.8.0 BUGFIX: On Windows destroying of windows works correctly now when calling (mvDisplay-lib) 'mvDestroyImageWindow'. BUGFIX: Reprogramming the sensor (changing the expose time etc.) could (mvBlueFOX-lib) be incomplete. BUGFIX: Setting 'ImageRequestTimeout_ms' to '0' results in a time-out, that (mvBlueFOX-lib) never elapses. BUGFIX: some missing UNICODE conversions added. (wxPropView and mvDeviceConfigure) BUGFIX: Not all members of class mvIMPACT::acquire::CameraDescriptionManager (mvIMPACT_acquire.h) have been initialised correctly. UPDATE: Internal migration to libexpat 2.0.0. (all shipped MSI-based packages) CHANGED BEHAVIOUR: libexpat-lib is no longer shipped with the MSI packages, as (all shipped MSI based packages) none of the modules depends on it any more. This might force you to to modify existing installer projects. CHANGED BEHAVIOUR: Property 'Statistics/LostImagesCount' no longer available (mvBlueFOX-lib) as on the mvBlueFOX we can't lose images in a way as counted by this property. CHANGED BEHAVIOUR: Trigger mode 'ctmOnHighExpose' no longer available for CMOS (mvBlueFOX-lib) versions as these sensors don't support this mode anyway. CHANGED BEHAVIOUR: TCameraTestMode::ctmImageDirectory removed from the (mvDriverBaseEnums.h) interface as this value was reserved for internal tests anyway. NEW FEATURE: Some compile time warnings for Visual Studio 6.0 C/C++ added (mvIMPACT_acquire.h) NEW FEATURE: Calibration parameters added to user data list for fine tuning (mvBlueFOX-lib) the mvBlueFOX(CCD versions only). NEW FEATURE: x64 sections added to Visual Studio 2005 makefiles for the sample (all *.vs2005.vcproj files) programs. Compatible libraries will follow. NEW FEATURE: A new pixel format is available: YUV422Planar. (all shipped MSI based packages) 10.01.2007 1.7.6 BUGFIX: Active scaler could cause crashes. (mvBlueFOX-lib) (Bug introduced in version 1.7.5) CHANGED BEHAVIOUR: By default warnings will no longer be written into the (all shipped packages) log-files. CHANGED BEHAVIOUR: The sample 'ContinuousCaptureToAVIFile' allows the precise (all shipped packages) setting of the capture frame rate for the mvBlueFOX now. 03.01.2007 1.7.5 NEW FEATURE: Property ImageDestination::scalerMode is now implemented for (all shipped packages) every device. However so far scaling is done in software. Only reducing the image size with mvDELTA/mvSIGMA devices will be done with no additional CPU load. BUGFIX: Property 'ImageProcTime' in the 'Statistics' list is displaying (all shipped packages) correct data again. (Bug introduced in version 1.7.0) 02.01.2007 1.7.4 BUGFIX: 'ChannelData' typedef appeared twice which caused newer GCC versions (mvDeviceManager.h) to fail compiling. BUGFIX: Defective pixels filter is working again. (all shipped packages) (Bug introduced in version 1.7.0) BUGFIX: High CPU load under wxPropView for devices that do not support event (all shipped packages) handling. (Bug introduced in version 1.7.2) CHANGED BEHAVIOUR: Event handling stuff for C++ modified. See Porting (all shipped packages) existing code section in manual. NEW FEATURE: Record feature added to mvPropView. (mvPropView) NEW FEATURE: Auto offset calibration speed now can be configured. (mvBlueFOX-lib) NEW FEATURE: Support for mvBlueFOX-102aG and mvBlueFOX-M102aG added. (mvBlueFOX-lib) NEW FEATURE: Property ImageDestination::scalerMode is now implemented for (mvSIGMAfg-lib) mvDELTA/mvSIGMA devices. 10.11.2006 1.7.3 BUGFIX: Maximum number of supported boards no longer limited to 16. (mvSIGMAfg-lib) BUGFIX: On certain motherboards devices couldn't always be detected correctly. (low level driver for mvDELTA, mvSIGMA, mvTITAN and mvGAMMA boards) BUGFIX: Memory leak when opening and closing a device that supports (mvBlueFOX-lib) events. (mvTITANfg-lib) (Bug introduced in version 1.7.2) BUGFIX: Memory leak when opening a device, acquire at least one image (all shipped packages) and closing the device again. BUGFIX: Memory leak when opening and closing a device that supports camera (mvTITANfg-lib) descriptions. (mvSIGMAfg-lib) (mvHYPERIONfg-lib) BUGFIX: Certain log messages didn't terminate correctly. (all shipped packages) BUGFIX: Several minor installer issues (Windows only) mostly introduced with (all shipped packages) version 1.7.2. BUGFIX: Info property SensorFPGAVersion is set correctly again. (mvBlueFOX-lib) (Bug introduced in version 1.6.6) BUGFIX: Test mode 'moving color' returns a Bayer image, that is converted (mvBlueFOX-lib) in 'Auto' Bayer conversion mode automatically. From version 1.7.0 to 1.7.2 no color image could be returned. (Bug introduced in version 1.7.0) NEW FUNCTION: DMR_GetDriverHandle. (mvDeviceManager-lib) NEW FEATURE: Start/stop trigger modes added (mvTITAN/mvGAMMA-CL only) (mvTITANfg-lib) 26.10.2006 1.7.2 NEW FEATURE: Certain drivers/devices can now report certain events. For (all shipped packages) details see documentation of the functions DMR_EventWaitFor and DMR_EventGetData (C-developers) or the class EventSubSystem(C++, .NET and Python developers). NEW SAMPLES: CameraDescriptions, EventHandling (all shipped packages) BUGFIX: Renaming existing camera description files now doesn't confuse the (mvTITANfg-lib) driver any more. (mvSIGMAfg-lib) BUGFIX: Deadlocks when switching the powerMode property during a running image (mvBlueFOX-lib) acquisition. === CD2006/B === 20.10.2006 1.7.1 BUGFIX: mvDisplay-lib Crashes in all the 'ContinuousCapture' samples (sample source code) on Hyper-threading machines. NEW SAMPLE: ContinuousCaptureAllFormats added to setup(Windows). (all shipped packages) NEW SAMPLE: SequenceCapture added to setup(Windows). (all shipped packages) BUGFIX: Missing files needed to compile ContinuousCaptureToAVIFile added. (all shipped packages) NEW FEATURE: Different view modes can be selected now for the property grid (wxPropView) to allow C-developers to display the grid like it would be accessed by the interface functions. NEW FEATURE: Support for resizeable vector properties added. (wxPropView) BUGFIX: Crashes when defining a new destination image with a greater line (mvDisplay-lib) count, but a smaller overall pixel count. NEW FEATURE: 'ibfRecycleBufHandle' added to mvDeviceManager. (mvDeviceManager-lib) BUGFIX: Disconnecting an mvBlueFOX shortly before closing the device (mvblueFOX-lib) could lead to a deadlock. BUGFIX: Corrected the visibility of some callbacks in the camera descriptions. (mvTITANfg-lib) BUGFIX: Acquisition from a 10 bit monochrome digital camera into an (mvTITANfg-lib) RGB or YUV destination format now works correctly. CHANGED BEHAVIOUR: Some values and corresponding strings of the enum (mvDriverBaseEnums.h) 'TCameraOutput' have been renamed. BUGFIX: Mono10 acquisition with mvGAMMA-G and mvTITAN-G1 works correctly (mvTITANfg-lib) again. (Bug introduced in version 1.7.0) BUGFIX: Incorrect gain and offset for images acquired with a destination (mvTITANfg-lib) format different from 'Auto' with a mvTITAN-RGB/G3 or mvTITAN-RGB/G4. BUGFIX: Increasing the value count for properties that define a translation (mvPropHandling-lib) dictionary could lead to crashes. BUGFIX: Installer no longer leaves the file 'Properties.vs2005.vcproj'. (all shipped packages) (Bug introduced in version 1.6.5) BUGFIX: Internal conversion from Mono10-16 to another Mono10-16 format (all shipped packages) corrected. BUGFIX: 'ContinuousCapture_C' sample revised. This sample now works with every device. BUGFIX: Closing either wxPropView or mvDeviceConfigure while in minimized (mvDeviceConfigure) could lead to situations, where applications could not restore (wxPropView) their original size. 29.09.2006 1.7.0 NEW FEATURE: Property 'BayerParity' added to digital camera descriptions. (mvDeviceManager.h) (mvTITANfg-lib) (mvHYPERIONfg-lib) NEW FEATURE: 'Flat Field', 'Defective Pixel' and 'Dark Current' filter support (mvBlueFOX-lib) ibpfMono10, ibpfMono12, ibpfMono14 and ibpfMono16 now. (mvTITANfg-lib) This also includes a complete redesign of the internal processing (mvSIGMAfg-lib) functions. (mvHYPERIONfg-lib) BUGFIX: copy constructor and assignment operator corrected for classes (mvIMPACT_acquire.h) 'RTCtrProgram', 'OutputSignalGeneratorFrameGrabber' and 'ImageProcessingBase'. CHANGED BEHAVIOUR: ImpactAcquireException behaves as described in changeset (mvIMPACT_acquire.h) 1.6.5 again. Please note that this requires the CD2006/B version of the mvIMPACT-SDK installation when using both the mvIMPACT-SDK and the mvIMPACT.acquire interface. NEW FEATURE: Property Device::LoadSettings offers 'no auto load' option (all shipped packages) now. BUGFIX: Pixel format ibpfRGBx888Planar is returned correctly again. (all shipped packages) (Bug introduced in version 1.6.7) NEW FEATURE: mvBlueFOX devices now can use an updated kernel driver. Updates (mvDeviceConfigure) for cameras already installed on a system can be performed via (mvBlueFOX-lib) mvDeviceConfigure, new cameras connected to the system for the first (mvBlueFOX2.sys, version 1.0.0.0) time will automatically use the new driver. The new driver will cause less CPU load than the previous one. This applies to Windows systems only. See documentation under GUI -> mvDeviceConfigure -> how to update the kernel driver as well. BUGFIX: Property 'LineDelay_clk' is set correctly when reconnecting or opening (mvBlueFOX-lib) an mvBlueFOX-102 device. NEW FEATURE: Property 'SensorTimingMode' added to CameraSettingsBlueFOX class. (mvBlueFOX-lib) (mvIMPACT_acquire.h) NEW FEATURE: Class SystemBlueFOX offers a new property 'powerMode' now. (mvBlueFOX-lib) NEW FEATURE: Support for YUV formats added to mvDeviceManager (mvDeviceManager-lib) 04.09.2006 1.6.9 BUGFIX: Expose times larger than 250000 us result in correct images now for (mvBlueFOX-lib) mvBlueFOX-121 models. NEW BEHAVIOUR: PWM Softstart for mvBlueFOX devices added to firmware. (mvBlueFOX-lib) (-> Firmware version 37) 29.08.2006 1.6.8 NEW FEATURE: 'Browse' and 'Default' button added to log output configurator. (mvDeviceConfigure) 22.08.2006 1.6.7 BUGFIX: Project file for sample 'ContinuousCaptureToAVIFile' was missing (all shipped MSI based packages) some source files and the linking of the vfw32.lib in the VS 6 project file. BUGFIX: mvDeviceConfigure could crash when no recognized device could be (mvDeviceConfigure) detected. NEW FEATURE: mvDeviceConfigure can start wxPropView for a device by double (mvDeviceConfigure) clicking on a device in the list control of devices. This will (wxPropView) open a new instance of wxPropView an start live acquisition from that device. 09.08.2006 1.6.6 BUGFIX: DMR_DeleteUserDataEntry returns a correct error code now when an (all shipped packages) invalid index has been passed to the function. BUGFIX: The real exposure time written to the camera has been incorrect in (mvBlueFOX-lib) previous versions of the driver for mvBlueFOX-102G and mvBlueFOX-102C devices. The lower the pixel clock the higher the difference between desired and real exposure time. This will result in brighter images when using older drivers and also when using older drivers an image at a higher pixel clock will be brighter than an image with the same exposure time at a lower pixel clock. BUGFIX: Properties, that store more than one value and that are assigned via (mvPropHandling-lib) 'writeS' now safely convert the data. CHANGED BEHAVIOUR: The property 'Product' now contains a longer string (mvSIGMAfg-lib) that is compliant with the other device drivers. BUGFIX: Properties displayed as a vector are handled correctly now (each (PropView) element can only assign one parameter to the property). NEW FEATURE: Functions OBJ_GetFlagsS and OBJ_GetTypeS added to 'C' (mvDeviceManager.h) compliant interface. NEW FEATURE: Functions DMR_ErrorCodeToString added to 'C' compliant (mvDeviceManager.h) interface. NEW FEATURE: Functions Component::flagsS and Component::typeS added to (mvIMPACT_acquire.h) C++ compliant interface. NEW FEATURE: ImpactAcqiureException::getErrorCodeAsString() (mvIMPACT_acquire.h) static ImpactAcqiureException::getErrorCodeAsString( int errorCode ) CHANGED BEHAVIOUR: ImpactAcquireException does always derive from (mvIMPACT_acquire.h) std::runtime_error now (see new features in version 1.6.5). The behaviour described in version 1.6.5 will be implemented when there is a new mvIMPACT-SDK release as otherwise old mvIMPACT-SDK C++ applications will NOT compile with mvIMPACT Acquire version higher than 1.6.5. BUGFIX: Missing reference to Instinf.msm added to merge file install for frame (all shipped MSI based frame grabber packages) grabber devices 10.07.2006 1.6.5 BUGFIX: Timestamp in *.log-output is always positive now. (all shipped packages) BUGFIX: Appending to existing log files always produces consistent XML (all shipped packages) output now. However appending to files is slow and should only be used is necessary. See section 'logging' in the corresponding manual. BUGFIX: XML file output on Linux now working correctly. (all shipped packages) NEW SAMPLE: ContinuousCaptureToAVIFile sample added to the C++ samples. (all shipped MSI based packages) This sample can be used as a starting point for AVI capture related applications. NEW FEATURE: Visual Studio 2005 workspace and project files added to sample (all shipped MSI based packages) programs. NEW FEATURE: A new pixel format is available: RGB888Packed. (all shipped MSI based packages) CHANGED BEHAVIOUR: String representation of the pixel formats corrected in (all shipped MSI based packages) the result structures. NEW FEATURE: 'OffsetAutoBlackLevel' property published for mvBlueFOX for C++ (mvIMPACT_acquire.h) and all other high level languages. The property is located in class CamerSettingsBlueFOX. NEW FEATURE: 'controllerDelay_Images' property published for mvBlueFOX for C++ (mvIMPACT_acquire.h) and all other high level languages. The property is located in class AutoControlParametersBlueFOX. NEW FEATURE: mvImpactAcquireException will now either be derived from (mvIMPACT_acquire.h) std::runtime_error or (if mvIMPACT.h has been included before) ImpactException. CHANGED BEHAVIOUR: Some typedefs that only have been used internally removed (mvIMPACT_acquire.h) from the interface and made private class members. BUGFIX: Some C++ interface objects are now reference counted in order to (mvIMPACT_acquire.h) avoid crashes under .NET NEW FEATURE: Enhanced error information output for mvTITAN and mvGAMMA (mvTITANfg-lib)) boards. NEW BEHAVIOUR: When a CameraLink camera description contains valid data, (mvTITANfg-lib) but data the used frame grabber can't cope with (e.g. a description for a MEDIUM camera connected to a mvGAMMA-CL) the Result structures 'result' entry will now return 'rrCameraNotSupported'. NEW BEHAVIOUR: property 'VideoOutput' in the camera description list (mvTITANfg-lib) and the property 'CameraOutputUsed' in the list 'Connector' (mvSIGMAfg-lib) became read-only. BUGFIX: Disconnecting an mvBlueFOX USB camera could lead to crashes (mvBlueFOX-lib) in very rare cases. BUGFIX: Reconnect restarts HRTC programs that where running before (mvBlueFOX-lib) the device was removed. CHANGED BEHAVIOUR: mvBlueFOX devices return a more precise error (mvBlueFOX-lib) information on failures during firmware update and modification of the device ID. BUGFIX: Property values with a format specifier for hex (%x) haven't (mvPropHandling-lib) always been converted from/to string correctly. NEW FEATURE: mvDeviceConfigure stores its current layout and restores (mvDeviceConfigure) it on the next start-up. NEW FEATURE: mvDeviceConfigure can now be used to configure the way (mvDeviceConfigure) *.log-output is generated(Action -> Configure Log output). NEW FEATURE: mvDeviceConfigure now detects device ID conflicts and informs (mvDeviceConfigure) the user about it. BUGFIX: Minor display issues in the Windows version of wxPropView (wxPropView version) NEW FEATURE: Toolbar added to wxPropView. (wxPropView version) 07.06.2006 1.6.4 NEW FEATURE: The MFC based version of mvPropView is no longer the (all shipped MSI based packages) default application to configure a device. Use the wxWidgets based version instead, which is available for Linux as well and offers more features like histogram, line profile, enhanced GUI features. CHANGED BEHAVIOUR: The camera handling for frame grabber devices has been (mvTITANfg-lib) simplified. Please see the section 'C++ developers -> Image (mvSIGMAfg-lib) acquisition -> Working with camera descriptions' for details (mvHYPERIONfg-lib) 29.05.2006 1.6.3 NEW FEATURE: All MSI-based installers now offer a modify option in (all shipped MSI based packages) maintenance mode. NEW FEATURE: Support for digital camera descriptions added to C++ interface. BUGFIX: Auto offset programming could cause distortions in the image. (mvBlueFOX-lib) Visible with large gain and short expose times(approx. 500 us) and certain scenes. 23.05.2006 1.6.2 BUGFIX: Trying to log into a file, that couldn't be created could cause (all shipped packages) crashes. NEW FEATURE: 'ScanClock' for mvTITAN-RGB, mvTITAN-G1 and mvGAMMA-G. (mvTITANfg-lib) BUGFIX: Property 'offset_pc' in class mvIMPACT::CameraSettingsFrameGrabber has been renamed to 'offset_mV' and is bound correctly now. NEW FEATURE: 'FlashToExposeDelay_us' for mvBlueFOX devices. (mvBlueFOX-lib) BUGFIX: Statistical properties 'QueueTime_s' and 'CaptureTime_s' contain (mvBlueFOX-lib) correct values again. BUGFIX: Overlay works when moving the display window out of the right (mvPropView) or bottom of the visible desktop area. This only affects images display in YUV422Packed mode. 09.05.2006 1.6.1 NEW FEATURE: The mvTITAN-RGB now support the setting of gain and offset (mvTITANfg-lib) per channel(R, G and B) in RGB mode. NEW FEATURE: The mvTITAN-RGB/G4s PAL decoder is now supported. (mvTITANfg-lib) NEW FEATURE: Support for mvHYPERION-CLe boards added. (mvHYPERIONfg-lib) BUGFIX: Internal support for Mono10 - Mono16 pixel formats added for (mvTITANfg-lib) mvTITAN-CL and mvTITAN-DIG boards. NEW FEATURE: mvBlueFOX 120C, 121C and 124C support horizontal color (mvBlueFOX-lib) binning now, mvBlueFOX 124C also supports vertical color binning 02.05.2006 1.6.0 NEW FEATURE: Repair also reinstalls the low level frame grabber driver (all shipped MSI based packages) now. NEW FEATURE: Image request control handling improved. See documentation of class mvIMPACT::acquire::FunctionInterface(OOP developers only) See also the 'porting existing code' section. NEW FEATURE: ComponentCollection::hObj() returns the underlying handle for this collection. BUGFIX: logging into files is now multi-process safe. BUGFIX: sample 'continuousCaptureAllDevices' is now completely multi thread safe. See the corresponding 'Porting existing code' section for details about enhancements and deprecated stuff. === CD2006/A === 24.04.2006 1.5.0 CHANGED BEHAVIOUR: The mvBlueFOX specific property 'USBRetransmit' has (mvBlueFOX-lib) been renamed to 'USBRetransmitCount'. See the corresponding 'Porting existing code' section for details. CHANGED BEHAVIOUR: The class mvIMPACT::acquire::Info has been renamed to mvIMPACT::acquire::InfoBlueFOX. See the corresponding 'Porting existing code' section for details. NEW FEATURE: Support for frame grabbers added (mvTITAN (RGB-G4, RGB-G3, CL, G1, DIG)) (mvTITANfg-lib) mvGAMMA (G, CL), mvSIGMA(SLC, SQ), mvDELTA). (mvSIGMAfg-lib) (mvDeviceManager-lib) NEW FEATURE/CHANGED BEHAVIOUR: mvPropView only checks for overlay (DD) (mvPropView) when it needs it and displays a message on failure. DirectDraw overlay is only needed/used for YUV422Packed images currently. export/save operations can now be cancelled. NEW FEATURE: Logging is now fully supported. See corresponding section in the manual. NEW FEATURE: A wxWidgets based version of mvPropView has been added to the setup. It has some nice features(live histogram, line profile) and a Linux version is available as well. However its display performance is weaker than the MFC based mvPropView, which is the reason, why no short cut will be created on the desktop. However the higher CPU load is ONLY caused by the applications way of displaying the images and has nothing to do with the performance of the interface itself. It can be found in the 'bin' folder of the installation. 27.02.2006 1.4.6 BUGFIX: UserData::getUserDataEntry( int nr ) const now behaves as stated in the documentation. NEW FEATURE: UserData::validUserDataEntryIndexes(). UPDATE: mvBlueCOUGAR support added (mvDeviceManager-lib) BUGFIX: Calling 'imageRequestSingle' from one and 'imageRequestReset' from (mvBlueFOX-lib) another thread could produce deadlocks. 16.02.2006 1.4.5 UPDATE: Internally the C++ interface now uses the class 'ExceptionFactory' to create exceptions. BUGFIX: long time integration sometimes produced incorrect images. (mvBlueFOX-lib) BUGFIX: Return values of DMR_WriteUserDataToHardware corrected (mvBlueFOX-lib) BUGFIX: Writing empty user data entries to the device could leed to a state (mvBlueFOX-lib) where the camera couldn't be accessed any more. (Bug introduced in version 1.4.0) BUGFIX: Crashes when selecting planar destination formats under mvPropView (mvPropView) (Bug introduced in version 1.4.0) 23.01.2006 1.4.4 BUGFIX: Function PropertyS::readBinary. BUGFIX: Properties UserData::memoryAvailable_bytes and UserData::memoryConsumed_bytes bound correctly now. UPDATE: Improved sensor timing and therefore image quality for certain sensor (mvBlueFOX-lib) operation modes. NEW FEATURE: sfFile flag added to TStorageFlag enum to allow explicit (mvPropHandling-lib) declaration of file I/O. Previous versions interpreted the sfNative flag NOT set as file output. This method is now deprecated but still supported. New applications should us the sfFile flag. This also allows to do file output AND native output with a single function call (by combining(sfNative | sfFile)). 20.01.2006 1.4.3 NEW FEATURE: Interface to unlock certain features via a license file added (mvBlueFOX-lib) (mvDeviceManager-lib version 1.4.3.23) NEW FEATURE: SDRAM memory support added for mvBlueFOX-M CCD versions. (mvBlueFOX-lib) 17.01.2006 1.4.2 NEW FEATURE: SDRAM memory support added for mvBlueFOX-M CMOS(102) versions. (mvBlueFOX-lib) 03.01.2006 1.4.1 BUGFIX: Spelling mistake introduced in version 1.4.0 corrected. This will not (mvPropHandling-lib) allow to restore the calibration data for DarkFiled, FlatField and DefectivePixels Filter without changing the corresponding section in the Registry and/or the XML file. To restore these data rename the list "DeficeSpeficData' to 'DeviceSpecificData'. NEW FEATURE: PropertyS::writeBinary and PropertyS::readBinary overloads. BUGFIX: Connecting a hot-plug device while mvPropView is already running (mvPropView) is working correctly again. (mvDeviceManager-lib) (Bug introduced in version 1.4.0) 22.12.2005 1.4.0 BUGFIX: DDraw overlay update didn't worked with some graphic adapters (mvPropView) (Matrox P650, ATI X1300 etc..). BUGFIX: Status line image format. (mvPropView) BUGFIX: Now every transfer size with every sensor resolution is working (mvBlueFOX-lib) CHANGED BEHAVIOUR: The property 'UserData' has been replaced by a list (mvBlueFOX-lib) of entries, that allow a more flexible management of user data. This is an incompatible change and might force you to modify existing code. Data stored in the device EEPROM with the old format will still be readable. See the corresponding 'Porting existing code' section for details. INCOMPATIBLE CHANGE: The class ImageBufferDescriptor does no longer support the constructors explicit ImageBufferDesc( ImageBuffer* p, bool boTakeOwnership = false ) and explicit ImageBufferDesc( const ImageBuffer& source ); See the corresponding 'Porting existing code' section for details. NEW FEATURE: ImageProcessing::defineFilterImageBuffer and ImageProcessing::queryFilterImageBuffer. NEW FEATURE: class ExceptionFactory. NEW FEATURE: Binary data can be written to and read from string properties now. BUGFIX: export/import of large string data (mvPropHandling-lib) NEW FEATURE: class ImageProcessingBlueFOX. It provides access to a new (mvBlueFOX-lib) range of filter functions that address certain characteristics of image sensors(Flat field filter, defective pixels filter, dark current filter). 04.11.2005 1.3.9 NEW FEATURE: Default clock for CCD mvBlueFOX cameras set to 24MHz. (mvBlueFOX-lib) 24MHz available for all mvBlueFOX CCD cameras now. UPDATE: Sensor timing for various mvBlueFOX cameras optimized. (mvBlueFOX-lib) NEW FEATURE: ComponentAccess::changedCounterAttr function. BUGFIX: Closing one device might stop all other devices from displaying (mvPropView) live images. BUGFIX: Rapid switching between devices in live mode could leave requests (mvPropView) locked until no more free requests where available thus resulting in no more images being captured. BUGFIX: HRTC-program mode is restored correctly again. (mvBlueFOX-lib) (Bug introduced in version 1.3.4) BUGFIX: Flash and HRTC program are stopped when closing the mvBlueFOX. (mvBlueFOX-lib) NEW FEATURE: Implemented basic log mechanism for mvBlueFOX devices. (mvBlueFOX-lib) BUGFIX: Bayer conversion on SSE2 compatible processors with more than one (mvBlueFOX-lib) device in YUV mode in the same process. === CD2005/C === 04.10.2005 1.3.8 BUGFIX: Hanging communication thread under NeuroCheck fixed (mvBlueFOX-lib) (Bug introduced in version 1.3.6) NEW FEATURE: OBJ_GetIDictEntry and OBJ_GetFDictEntry function added. (mvDeviceManager-lib) These functions can be used to query a single translation dictionary entry instead of the complete dictionary and are meant for use under VB or VB.NET and C# (from the mvIMPACT_NET-lib). NEW FEATURE: The device list now has a userData property ("UserData"), which (mvBlueFOX-lib) can be used to store user specific data permanently into the device. BUGFIX: IOSubSystem::readInputRegister returns correct results now all the time. 09.09.2005 1.3.7 BUGFIX: Overlapped expose mode is working again. (mvBlueFOX-lib) (Bug introduced in version 1.3.6) NEW BEHAVIOUR: HRTC programs and settings only store the essential data (mvBlueFOX-lib) now. (mvPropView) 06.09.2005 1.3.6 BUGFIX: RGBx888Packed mode when calling DMR_GetImpactRequestBufferEx (mvDeviceManager-lib) with 'ibfUseRequestMemory' is working now. BUGFIX: DMR_GetImageRequestBufferImageData correctly supports the RGBx888Planar mode now. BUGFIX: mvPropView is compilable again. (mvPropView) NEW FEATURE: mvPropView can display planar RGB images properly now. (mvPropView) BUGFIX: Structure alignment in mvDeviceManager.h set to 8 byte boundaries. NEW BEHAVIOUR: Compiler warning in mvIMPACT::acquire::ImageProcessing::ImageProcessing removed. BUGFIX: Unplugging the mvBlueFOX during the init procedure is now handled (mvBlueFOX-lib) correctly. BUGFIX: Unplugging the mvBlueFOX while capturing images and setting (mvBlueFOX-lib) properties in now handled correctly. BUGFIX: With activated Bayer conversion the first image might have been (mvBlueFOX-lib) in an incorrect format. NEW BEHAVIOUR: mvBlueFOX update speed enhanced. (mvBlueFOX-lib) BUGFIX: HRTC program files can be imported an stored correctly again (mvBlueFOX-lib) (mvPropHandling-lib version 1.3.6.15) 08.08.2005 1.3.5 BUGFIX: Calling imageRequestReset with the device removed doesn't cause (mvBlueFOX-lib) an access violation anymore. BUGFIX: Import of lists from the registry. (mvPropHandling-lib) BUGFIX: Check for available device features. (mvDeviceManager-lib) === CD2005/B === 02.08.2005 1.3.4 NEW FEATURE: ibpfRGBx888Planar is now fully supported. (mvBlueFOX-lib) NEW FEATURE: Request::getIMPACTImage( TImpactBufferFlag flags ) const; (mvDeviceManager-lib) which can be used to control the way the returned IMPACT buffers are created and handled. 28.07.2005 1.3.3 NEW FUNCTIONS: IOSubSystem::getInputCount, IOSubSystem::getOutputCount to query the number of available digital inputs and outputs for a device. INCOMPATIBLE CHANGES: - typedef for IntDict and FloatDict removed from interface. Replace each occurrence of FloatDict by std::vector >, each occurrence of IntDict by std::vector >. - class local enum for Property limits made global. Property::minValue became plMinValue Property::maxValue became plMaxValue Property::stepWidth became plStepWidth - RTCtrProgram::programSize became RTCtrProgram::getProgramSize. - These changes became necessary for creating the .NET interface and might force you to change existing code. NEW FEATURE: TWhiteBalanceParameter enum published an applied to the property 'WhiteBalance' in the interface class 'ImageProcessing'. NEW FEATURE: A new application has been added to the setup('mvDeviceConfigure'). It can be used to perform firmware updates and to assign unique device IDs. BUGFIX: Crashes when calling the update method for a (mvBlueFOX-lib) HardwareRealtimeController without parameters. BUGFIX: A hardware real-time controller program is stopped automatically (mvBlueFOX-lib) when it's modified. BUGFIX: trigger mode 'OnHighExpose' fixed. This trigger mode also sets (mvBlueFOX-lib) the flag cfInvisible for the properties 'expose_us' and 'FrameDelay_us' now as modifying these properties in this trigger mode has no effect. BUGFIX: USB devices don't leave zombie windows in process memory. (mvBlueFOX-lib) UPDATE: Some missing return types added, slight modifications in the template classes to allow compilation with Microsoft Visual Studio 2005. BUGFIX: mvDeviceManager returns correct error codes when calling the (mvDeviceManager-lib) functions DMR_SetDeviceID or DMR_UpdateFirmware now. NEW FEATURE: IOSubsystem/HRTC programs can be stored as XML file as well now. (mvPropHandling-lib) New error code: PROPHANDLING_CANT_SERIALIZE_DATA and new flag cfDisallowSerialize. BUGFIX: FunctionInterface::saveSystem is working again. 08.07.2005 1.3.2 NEW FEATURE: Support for mvBlueFOX-102G/O4 and mvBlueFOX-102C/O4 (mvBlueFOX-lib) added. NEW FEATRUE: HRTC programs are now stored in the registry as well. 27.06.2005 1.3.1 BUGFIX: DEV_REQUEST_CANT_UNLOCKED error code value corrected to -2115. (mvBlueFOX-lib) BUGFIX: mvPropView: Storing Bitmaps is working again. (mvPropView) NEW FEATURE: Base class ComponentCollection for CameraSettings, ImageProcessing and ImageDestination. This allows to restore the default values for every property managed by these objects. NEW FUNCTIONS: DMR_GetImageRequestBufferData(), (mvDeviceManager-lib) DMR_GetImageRequestBufferChannelData(), DMR_GetImageRequestBufferImageData() and DMR_SetImageRequestBufferImageData(). BUGFIX: Expose readout for mvBlueFOX 102 series. (mvBlueFOX-lib) BUGFIX: AGC/AEC for mvBlueFOX 102 series. (mvBlueFOX-lib) BUGFIX: External trigger for mvBlueFOX CMOS series now working. (mvBlueFOX-lib) NEW SAMPLE: 'VBSample' to demonstrate how to access the devices under Visual Basic .NET. NEW SAMPLE: 'DelphiSample' to demonstrate how to access the devices under Borland Delphi 5.x and onwards. BUGFIX: Missing lib exports for functions DMR_SaveRTCtrProgram and (mvDeviceManager-lib) DMR_LoadRTCtrProgram added. NEW BEHAVIOUR: The C++ interface header file and folder have been renamed to achieve the same look and feel as the IMPACT CPP wrapper files. mvi_acquire/mvi_acquire.h became mvIMPACT_CPP/mvIMPACT_acquire.h. NEW BEHAVIOUR: The class mvIMPACT_CPP::acquire::System has been renamed to mvIMPACT_CPP::acquire::SystemSettings to avoid conflicting names under .NET. NEW BEHAVIOUR: The function mvIMPACT::acquire::stringAllocator became a static protected member of the class mvIMPACT::acquire::ComponentAccess. NEW BEHAVIOUR: ::size_type return types changed to unsigned int (reason: .NET support). NEW BEHAVIOUR: std::map and std::set dependencies removed from C++ wrapper FunctionInterface::getAvaiableSettings now returns a string vector instead of a string set(reason: .NET support). 31.05.2005 1.3.0 NEW BEHAVIOUR: The underlying C-API has been moved completely to the (mvDeviceManager-lib) mvDeviceManager-lib. Applications compiled with and older version of this interface MUST be recompiled, re-linked and maybe modified. See the corresponding 'Porting existing code' section for details. This allows to use the supported devices from other programming languages (such as Visual Basic or Delphi) as well. BUGFIX: mvi_acquire.h has been adapted to work with the compiler bugs of the Visual Studio 6.x compiler. NEW FEATURE: The setup has been reorganized. There are now workspaces for Visual Studio 6.x, 7.x and Borland C++ Builder 6.x for all Sample programs. NEW SAMPLE: ContinuousCapture_C shows how to work with the 'C' compliant interface. NEW BEHAVIOUR: It's no longer necessary to link mvPropHandling.lib. (mvDeviceManager-lib) Only mvDeviceManager.lib is needed now. UPDATE: Bayer conversion speed optimised for mvBlueFOX devices. (mvBlueFOX-lib) BUGFIX: mvBlueFOX 121 with 40MHz pixel clock is now working properly. (mvBlueFOX-lib) 1.2.2 NEW FEATURE: Hibernating support added for mvBlueFOX devices. (mvBlueFOX-lib) NEW BEHAVIOUR: Searching devices is now down in the mvDeviceManager-lib. (mvDeviceManager-lib) This will require an up to date mvDeviceManager-lib on each target system compiled with the actual version of the mvi_acquire.h! NEW BEHAVIOUR: Device::setID and Device::updateFirmware now call direct (mvDeviceManager-lib version 1.2.2.6) exports of the mvDeviceManager-lib. This will require an up to date mvDeviceManager-lib on each target system compiled with the actual version of the mvi_acquire.h! NEW BEHAVIOUR: matchString function removed! 28.04.2005 1.2.1 BUGFIX: Missing implementations of the class ImageProcessing added. BUGFIX: Spelling mistakes in enum TBlueFOXTransferSize. NEW BEHAVIOUR: TBlueFOXFooterMode values renamed. NEW BEHAVIOUR: Image buffer state property removed from ImageBuffer class as it became redundant. NEW PROPERTY: Info::SensorType. BUGFIX: Visibility flag for components in invisible sublists is (mvPropHandling-lib) correct now. BUGFIX: import of XML ComponentLists. (mvPropHandling-lib) NEW FEATURE: AGC and AEC are available under mvPropView now. (mvBlueFOX-lib) NEW FEATURE: MirrorMode property (allows horizontal or vertical flipping (mvBlueFOX-lib) of the image. See ImageProcessing::MirrorMode. NEW FEATURE: User controlled firmware update, EEPROM stored device ID. (mvBlueFOX-lib) See Device::setID(), Device::updateFirmware(), Device::HWUpdateResult. NEW FEATURE: USB 1.1 support added for mvBlueFOX cameras. (mvBlueFOX-lib) 20.04.2005 1.2.0 NEW FUNCTION Property::readSArray. (mvPropHandling-lib) NEW BEHAVIOUR: FunctionInterface::createSetting and FunctionInterface::createImageRequestControl don't throw exceptions anymore, but return an error code if the call failed. BUGFIX: An error is reported, if XML-settings can't be located. (mvPropHandling-lib) BUGFIX: Error codes are reported by functions from class FunctionInterface (mvBlueFOX-lib) Error codes can be from the error code range of TDEV_MGR_ERROR, TDEVICE_DRIVER_ERROR or TPROPHANDLING_ERROR. NEW FEATURE: Real time control machines added to interface and driver. (mvBlueFOX-lib) NEW FEATURE: AGC and AEC controls added to interface and driver. (mvBlueFOX-lib) NEW BEHAVIOUR: Init speed, PnP speed optimised. (mvBlueFOX-lib) BUGFIX: mvPropView: OptionTree reacts faster and uses less CPU time. NEW FEATURE: TComponentFlag::cfShouldBeDisplayedAsList. (mvPropHandling-lib) UPDATE: C++ wrapper header structure reorganized. Now there is only one header ( mvi_acquire.h ). NEW BEHAVIOUR: Certain things in the interface have been changed. Some will force you to recompile your application, some will even force you to modify existing code. We are still in the beta stadium, but we are getting closer to a stable interface. Some exported function modified or removed from mvPropHandling.h BUGFIX: Destroying a DeviceManager object doesn't leave invalid windows (mvDeviceManager-lib) and threads any more. BUGFIX: mvDevMgrGetDevInfo, mvDevMgrSetParam made thread save. NEW BEHAVIOUR: Component::canWrite renamed to Component::isWriteable() NEW FEATURE: Component::isVisible, CameraSettingsBlueFOX, AutoControlParameters. (subject to change! See documentation!) NEW BEHAVIOUR: Missing units added to some properties. BUGFIX: Various minor fixes. 11.03.2005 1.1.1 NEW BEHAVIOUR: In mvPropHandlingDataTypes.h the unsigned int constants (mvPropHandling-lib) for defining the operation mode of search functions have been renamed to avoid confusion with the TStorageFlag type. The leading 'sf' has been renamed to 'sm'. The constant 'sfSearchSublists' has been removed, as the underlying behaviour can be expressed by the maximum search depth as well. This is an incompatible change which might force you to modify existing source. NEW FEATURE: New TStorageFlag added: sfProcessInheritance. (mvPropHandling-lib) BUGFIX: Deadlock removed when multiple threads accessed the property (mvPropHandling-lib) module. DOCUMENTATION UPDATED NEW FEATURE: New sample program added (ContinuousCaptureAllDevices), to demonstrate how to access all supported devices found in the current system in a single application. BUGFIX: PropertyS::read function caused an access violation when building the result string when a NULL-pointer was returned by the function. BUGFIX: Noisy images for certain sensor types of the mvBlueFOX. (mvBlueFOX-lib) BUGFIX: Wrong colours in Bayer converted images for 1024*768 sensor. (mvBlueFOX-lib) < 11.03.2005 previous versions