Firmware versions contained in this MVU file: * 2.44.2843.0 : mvBlueCOUGAR-X firmware * 2.30.1482.0 : mvBlueCOUGAR-X firmware (maintenance firmware for cameras with Sony-CCD, Aptina, E2V and CMOSIS sensors) =============================================================================================================================================================== version info firmware =============================================================================================================================================================== Date: Release: Changes: Affected devices: --------------------------------------------------------------------------------------------------------------------------------------------------------------- 28.09.2021 2.44.2843.0 NEW FEATURES: - New cameras: mvBlueCOUGAR-X108aG/C and mvBlueCOUGAR-X1012dG/C. - TriggerMode mvLowLatency also known as Fast Trigger Mode is available for Sony GS all Sensors Gen 2,3,4 - As 'InputSource' for counter and timer 'SofwareSignals' are introduced. This all simplyfies software generated pulses. - The automatic white balance (AWB) has been improved concerning the behavior when pixels all are saturated. In this case nearly no color casts arise. - On the fly changes during the running sequencer are now also possible with binning all and decimation properties. CHANGED BEHAVIOUR: - The change in 2.43.2720.1 is reverted. DPC is per default active again. BUGS FIXED: - Overtriggering of the sensor due to inaccurracy in framerate calculation all - UserSets could be lost when switching between USB2 and USB3. Bug introduced in 2.39.2472.0. BF3 - corrected sensor settings to prevent unstable framerates when using all with IMX53x sensor sensor binning/decimation - DualADC mode was not working correctly. Bug introduced in 2.41.2640.0 . mvBlueCOUGAR-XD107G/C - Defective Pixel Correction (DPC) with color sensors could generate image all artifacts depending on the image - When EncoderModeOutput is set to Motion or DirectionUp sometimes pulses has been BF3, BCX(D) not counted as expected. 05.08.2021 2.43.2720.1 NEW FEATURES: - CHANGED BEHAVIOUR: - For color cameras: mvDefectivePixelEnable is Off by default. BUGS FIXED: - 16.06.2021 2.43.2720.0 NEW FEATURES: - New cameras: mvBlueFOX3-2124dG/C, mvBlueFOX3-2081aG/C, mvBlueFOX3-2051dG/C - FrameActive is available as output signal. all - Offset and Length of FileAccessControl have now appropriate values all CHANGED BEHAVIOUR: - BUGS FIXED: - Changing exposure time could stop auto exposure control. all - Maximum Framerate has not been adjusted when AEC was activated all - Activated frame average in pixleformats > 8Bit can lead to delayed or lost BF3-2 frames. - Saving defect pixel coordinates no longer worked. Bug introduced in 2.41.2640.0 BCXD, BF3-2 26.04.2021 2.41.2640.1 NEW FEATURES: - CHANGED BEHAVIOUR: - BUGS FIXED: - Potentially no images. Bug introduced in 2.41.2640.0 mvBlueFOX3-2162G/C mvBlueFOX3-2204G/C mvBlueFOX3-2246G/C mvBlueCOUGAR-XD1016G/C mvBlueCOUGAR-XD1020aG/C mvBlueCOUGAR-XD1025G/C 26.03.2021 2.41.2640.0 NEW FEATURES: - New cameras: mvBlueFOX3-2204bC, mvBlueCOUGAR-XD1020aG/C - BCX(D): Streaming in an other subnet is now supported - Binning/Decimation beyond the sensor minimum possible - AGC/AEC is now faster and there is also an additional mode,'mvPeak' for calculating the actual value. It is less sensitive to small changes. - BCXT: DualADC compression can now be configured with a bunch of optimized settings. - Support for future cameras >= Rev 6 is added. - BF3/BCXD: Defective Pixel Correction can be now used even if the static defective pixel coordinate list is empty. This eliminates the need for offline calibration. Pixels are dynamically detected and replaced on the fly. - Cameras with Pregius S are using the more accurate sensor signal internally for a also more accurate exposure value in the chunk data. CHANGED BEHAVIOUR: - Resend requests of multiple consecutive packets are acknowledged with one command. BUGS FIXED: - BCX(D): Resend mechanism for variable image length added; Needed for JPEG and Sequencer applications - mvBlueFOX3-2124rG/C: Changing gain could lead to corrupt images. - mvBlueFOX3-2205G/C, mvBlueCOUGAR-X1020G/C: Corrupt images could occur when changing exposure time in global reset shutter mode. - mvBlueFOX3-2205G/C, mvBlueCOUGAR-X1020G/C:AcquisitionStart/Stop at high framerates could lead to timeouts. - mvBlueCOUGAR-X1020G/C, mvBlueFOX3-2205G/C: First image after acquisition start was corrupt when using ReverseY. - mvBlueCOUGAR-XD1031C: Color correction matrix was not initialized. - BCX(D): FFC is now working with IMX249 sensor in AOI Mode if OffsetX is not a multiple of 4 - TriggerSoftwareCommand could fail for FrameBurstStart-trigger when sending command immediately after AcquisitionStart. - mvBlueCOUGAR-XD1016C, Changing the the pixeldepth during Binning/Decimation could lead to corrupt images - mvLiquidLensStatus had mistakenly displayed errors. 18.03.2021 2.30.1482.0 !! Maintenance firmware for all cameras with Sony-CCDs, Aptina, E2V and CMOSIS sensors !! NEW FEATURES: - CHANGED BEHAVIOUR: - BUGS FIXED: - mvBlueCOUGAR-X(D): Support for Streaming in another Subnet added. 16.12.2020 2.40.2546.0 NEW FEATURES: - There is the new 'mvAutoFeatureControl' which groups all common properties that belongs to the automatic exposure, gain and white balance controller. - AEC/AGC can be controlled with the new additional properties mvAutoFeatureSensitivity, mvAutoFeatureCharacteristic and mvAutoFeatureBrightnessTolerance - New cameras: mvBlueFOX3-2162C - mvBlueCOUGAR-XD1016G/C, mvBlueCOUGAR-XD1025C, mvBlueCOUGAR-XD1031C: YUV and RGB pixel formats are available. - Uart/RS232 maximum tranfer rate increased up to 115kBaud on all cameras - The timestamp for Line4 and Line5 events is now more accurate on all mvBlueCOUGAR-X(D) and mvBlueFOX3 - Cameras with Pregius Generation 4 are using the more accurate sensor signal for flash or exposure period output. This feature is not available in other sensor chip families. CHANGED BEHAVIOUR: - mvBlueCOUGAR-X(D): The FFC calibration with color sensors lightens the image about 30% when FFC is enabled to avoid color artifacts. This 30% factor is now removed and should be compensated using the AOI mode feature. In that case only the AOI area is used to calculate the correction values. BUGS FIXED: - High exposure values,more than 34s using BF3 or more than 2s using BCX(D) had caused an overflow of ChunkExposureTime. - mvResultingFramerate is now updated even if AEC is active - AutoWhiteBalancing did not work correctly when ReverseX is used. - ChunkGain was updated one frame too late. - The internal FFC calibration didn't work with small AOIs 08.12.2020 2.30.1480.0 !! Maintenance firmware for all cameras with Sony-CCDs, Aptina, E2V and CMOSIS sensors !! NEW FEATURES: - CHANGED BEHAVIOUR: - BUGS FIXED: - mvBlueCOUGAR-X102eG/C, mvBlueCOUGAR-X104eG/C: Switching DeviceScanType could lead to no images. Bug introduced in 2.15.556.0. 29.09.2020 2.39.2472.0 NEW FEATURES: - New cameras: mvBlueCOUGAR-XD102mG, mvBlueCOUGAR-XD1016G/C, mvBlueCOUGAR-XD1025G/C, mvBlueFOX3-2162G - Framerate increased for mvBlueFOX3-2016G, mvBlueFOX3-2246G, mvBlueCOUGAR-X102fG in 2 times binning mode - The setting of digital IOs is now faster CHANGED BEHAVIOUR: - BUGS FIXED: - BCX(D): On Uart receive side data could be lost when using baud rates above 38kbaud - mvBlueFOX3-2064G/C: Using mvShutterMode = mvGlobalReset could result in timeouts in very rare cases. - All cameras with IMX sensors: Long exposure times in auto exposure control (AEC) mode leads to halfed frame rate when controled exposure time was above the user selected frame rate. - mvBlueFOX3-xxxx: Device link throughput maximum limit was higher than the maximum available streaming bandwidth. 23.06.2020 2.38.2371.0 NEW FEATURES: - ExposureMode 'TriggerWidth'now supported by IMX Rolling Shutter cameras - New cameras: mvBlueFOX3-2204G/C, mvBlueFOX-2246G/C - The Blockscan mode can be used with more lines now. - Initializing of the camera timestamp is now possible CHANGED BEHAVIOUR: - BUGS FIXED: - mvBlueCOUGAR-X1020G/C, mvBlueFOX3-(M)2205G/C, mvBlueFOX3-(M)2124rG/C: ReverseY did not work correctly. Bug introduced in 2.37.2285.0. - mvBlueFOX3-2064G/C: Using mvShutterMode = mvGlobalReset could result in timeouts in rare cases. - mvBlueFOX3-2, In rare case, host controller dependant, the USB2 mode didn't work 14.05.2020 2.37.2285.1 NEW FEATURES: - CHANGED BEHAVIOUR: - BUGS FIXED: - mvBlueFOX3-2xx only: Depending on the USB3 Controller of the host system, cameras are not present after system boot. Bug introduced in 2.37.2285.0. 26.03.2020 2.37.2285.0 NEW FEATURES: - New cameras: BF3-4-0169ZC and BF3-4-0196ZC. - mvBlueCOUGAR-X(D): The IEEE1588 Precision Time Protocol (PTP) that synchronize mutiple GigE cameras in the same network is supported. The implementation is based on the two step mode. - mvBlueCOUGAR-X(D): The Blockscan mode, a method to deal with small AOIs with high framerates is implemented for all cameras with global shutter IMX sensors. CHANGED BEHAVIOUR: - mvDefectivePixelOffsetX/Y are now visible selected by mvDefectivePixelSelector. - Image start in vertical binning/decimation modes is now unified between different models. BUGS FIXED: - Bandwidth sharing of multiple GigE cameras streaming over one GigE switch has not worked correctly when the switch has poor memory equipment. - mvBlueCOUGAR-X104fC, mvBlueFOX3(M)-2024aC, BF3-M50024AC: Sometimes no images could be captured when using ReverseY. - Switching Triggermodi when Acquisition is on led to one unintentionally trigger. 04.02.2020 2.30.1476.0 !! Maintenance firmware for all cameras with Sony-CCDs, Aptina, E2V and CMOSIS sensors !! NEW FEATURES: - CHANGED BEHAVIOUR: - mvBlueFOX3-1031C: Defect pixel correction is used when mvDefectivePixelEnable is On. ( On is default ). BUGS FIXED: - Switching Triggermodi when Acquisition is on led to one unintentionally trigger. 14.01.2020 2.36.2211.0 NEW FEATURES: - New cameras: BF3-5-0205ZG and BF3-5-0205ZC. - New cameras: BF3-4-0169ZG and BF3-4-0196ZG. - New Property 'mvGigabitMasterSlaveMode' for cameras with revision >= 5 added. This property allows to set the Phy clock mode for Gigabit link connections to Master/Slave/Auto. Default is Auto. In case of long boot times setting clock mode to Master or Slave could help to reduce the boot time. A reboot is necessary to get new clock mode active. - mvBlueFOX3-xxxx ( except Rolling shutter cameras ): Defective pixel correction is done in camera. mvDefectivePixelEnable is On by default. Defective pixel correction is not working with MultiAreaMode and BlockScanMode. CHANGED BEHAVIOUR: - BUGS FIXED: - AutoExposure/AutoGain: If exposure time has reached its upper limit and there are only small changes in brightness gain could stay at 0. - mvBlueCOUGAR-X1020G: ReverseY did not work correctly. - mvBlueFOX3-xxxx: Switching too often to mvDevicePowerMode = mvStandby could crash the camera. - ReverseX and ReverseY did not work correctly with scaling factors > 2. - Link establishment between BCX(D) Rev. 5 and a Lancom Switch has sometimes failed 29.08.2019 2.35.2054.0 NEW FEATURES: - mvBlueCOUGAR-X(D): SmartFrameRecall can be used with larger preview images. - DecimationHorizontalMode and DecimationVerticalMode are now writable. They can be set to 'Discard' or 'Average'. BinningHorizontalMode and BinningVerticalMode are now writable. They can be set to 'Sum' or 'Average'. This helps to better choose what to achieve. - New cameras: BF3-5M-0032AG/C with IMX265 sensor, BF3-5M-0051ZG/C with IMX250 sensor, BF3-5M-0051AG/C with IMX264 sensor, BF3-5M-0124AG/C with IMX304 sensor, BF3-5M-0124RG/C with IMX226 sensor and mvBlueFOX3-2071G/C with IMX420 sensor. - mvBlueFOX3, mvBlueCOUGAR-X(D): Support for custom command that allows to modify OffsetX and OffsetY in a sequencer set while the sequencer is running. - mvBlueFOX3, mvBlueCOUGAR-X(D): Line events RisingEdge, FallingEdge and AnyEdge are now available for all input lines a camera supports. - mvBlueFOX3 with IMX sensors: BlockScanMode implemented. - New 12 to 9 RawLUT for color cameras added. It is only available instead of the 10 to 9 component LUT's (Red, Green, Blue) and vice versa. CHANGED BEHAVIOUR: - Discard is the new default value for DecimationHorizontalMode as well as for DecimationVerticalMode. - Cameras with polarized color sensors do no longer support Gamma nor LUT. BUGS FIXED: - mvAcquisitionMemoryMaxFrameCount was not set correctly when SmartFrameRecall is used. - Cameras that support mvDualAdcMode did not have their user AOIs (that are used for BalanceWhiteAuto, ExposureAuto, GainAuto) initialised. Bug introduced in 2.30.1451.0 - mvBlueFOX-2205G/C, mvBlueCOUGAR-X1020G/C: Using ReverseY could lead to lost images. - The divider value in the rotary encoder unit was wrong by 2 and a transparent setting of 1 (to get an event for every "tick") wasn't feasible - mvBlueCOUGAR-XPOEI: Debouncer was not working on Line7. 13.06.2019 2.34.1937.0 NEW FEATURES: - mvBlueCOUGAR-X(D) and mvBlueFOX3: Gamma support in AnalogControl added - mvBlueFOX2205G/C, mvBlueCOUGAR-X1020G/C: Increased frame rate when using binning or decimation. - New cameras: BF3-4-0315ZG/C, mvBlueCOUGAR-X105pC. - mvBlueCOUGAR-X(D) and mvBlueFOX3 with IMX sensors: Sequencer supports user outputs. They can be used on a per frame basis. In combination with output lines and AND/OR gates this can be a powerful tool to extract e.g. exposure signals from one set only. - New read only property shows the validity of the current setting. Invalid combinations of Binning/Decimation settings can be detected before starting the acquisition. - All cameras with IMX sensors: ReverseX and ReverseY implemented. Exceptions: * POLARSENS sensors: none * IMX183 and IMX226 sensors: ReverseY only. CHANGED BEHAVIOUR: - Rolling Shutter IMX: Exposure time increased from 1s to 20s. - Invalid Binning/Decimation settings prevent streaming images. BUGS FIXED: - mvBlueCOUGAR-XD couldn't do any resends anymore (bug introduced in 2.33) - AOI was wrong after startup when UserSetDefault is using binning or decimation. - Running timer does not stop when changing timer delay. - mvBlueFOX3 (all models): fixed overflow in ChunkExposureTime when being used with long integration times - When TimerReset and FrameTrigger was fed by the same signal, you got "old" timestamps. - autoGain/autoExposure sometimes did not work correct when changing Binning/Decimation - Rolling Shutter IMX: Changing exposure time just before AcquisitionStart could led to one image with former exposure time. 06.03.2019 2.33.1779.0 NEW FEATURES: - New cameras: mvBlueCOUGAR-X102nG/C, mvBlueCOUGAR-X105pG, mvBlueCOUGAR-X107bG/C, mvBlueCOUGAR-X1020G/C, mvBlueCOUGAR-XD1031G/C, mvBlueCOUGAR-XD107bG/C, mvBlueFOX3-2051pG/C, mvBlueFOX-2124rG/C, mvBlueFOX-2205G/C. - mvBlueCOUGAR-X102nG/C, mvBlueCOUGAR-X107bG/C, mvBlueCOUGAR-XD107G/C, mvBlueCOUGAR-XD107bG/C, mvBlueFOX3-2071aG/C : Frame rate increased when using DecimationHorizontal. Grey versions only: Frame rate increased when using BinningHorizontal. - mvBlueCOUGAR-XD1031G/C: Sequencer with changing image size and position. CHANGED BEHAVIOUR: - Multi-AOIs close together are no longer combined. BUGS FIXED: - mvBlueCOUGAR-X: GEV register SCSP was changed whenever register SCP was changed - mvBlueCOUAGR-X109bG/C, mvBlueCOUAGR-XD109bG/C, mvBlueFOX3-2089aG/C: There were no images when using reverse mode combined with binning or decimation. - mvBlueFOX3-2064G/C: Invalid EventFrameEndFrameID could occur in trigger mode. - When using the Color Pseudo Luminance LUT, the resulting waveform is no longer compromised by a sawtooth signal pattern. 26.02.2019 2.30.1470.0 !! Maintenance firmware for all cameras with Sony-CCDs, Aptina, E2V and CMOSIS sensors !! NEW FEATURES: - CHANGED BEHAVIOUR: - 'TimerValue', 'CounterValue', 'mvSerialInterfaceASCIIBuffer', 'mvSerialInterfaceBinaryBuffer', 'mvSerialInterfaceBytesToWrite', 'mvSerialInterfaceBytesToRead', 'mvSerialInterfaceReceiveStatus', 'mvSerialInterfaceBytesAvailableForRead', 'mvLiquidLensReceiveStatus', 'mvLiquidLensErrorCount', 'mvLiquidLensFirmwareVersion', 'mvStepperFirmwareVersion', 'mvStepperReceiveStatus', 'mvStepperErrorCount', 'mvI2cInterfaceASCIIBuffer', 'mvI2cInterfaceBinaryBuffer', 'mvI2cInterfaceBytesToWrite', 'mvI2cInterfaceBytesToRead' cannot be stored to and loaded from a file anymore. - USB 3.1 Gen 1 devices (USB 3.0 devices) will now identify themselves as USB 3.2 Gen 1 devices. BUGS FIXED: - mvBlueCOUGAR-X105G/C: Real exposure time did not always match requested exposure time. - mvBlueCOUGAR-X102eG/C: Flat field correction data were not saved correctly. 15.12.2018 2.32.1676.0 NEW FEATURES: - New camera: BF3-3M-0064Z CHANGED BEHAVIOUR: - 'TimerValue', 'CounterValue', 'mvSerialInterfaceASCIIBuffer', 'mvSerialInterfaceBinaryBuffer', 'mvSerialInterfaceBytesToWrite', 'mvSerialInterfaceBytesToRead', 'mvSerialInterfaceReceiveStatus', 'mvSerialInterfaceBytesAvailableForRead', 'mvLiquidLensReceiveStatus', 'mvLiquidLensErrorCount', 'mvLiquidLensFirmwareVersion', 'mvStepperFirmwareVersion', 'mvStepperReceiveStatus', 'mvStepperErrorCount', 'mvI2cInterfaceASCIIBuffer', 'mvI2cInterfaceBinaryBuffer', 'mvI2cInterfaceBytesToWrite', 'mvI2cInterfaceBytesToRead' cannot be stored to and loaded from a file anymore. - 'mvLiquidLensPowerMode' can now be stored and loaded from a file. - USB 3.1 Gen 1 devices (USB 3.0 devices) will now identify themselves as USB 3.2 Gen 1 devices. - mvBlueFOX3-2xxxG/C: slightly better sequencer performance for small frames. - UserSetLoad and UserSetStore cannot be executed any more while streaming is active. - Multi-AOIs close together are no longer combined if no overlapping AOIs are configured. BUGS FIXED: - Setting gain directly after AGC = Off did not work correctly. - mvBlueFOX3-2064G/C: ExposureTime could be wrong for some usecs. - When writing an unsupported packet size value to into the packet size register of a GEV device the value is corrected according to R-562st of version 2.1 of the GEV specification. - mvBlueFOX3-2xxxG/C: Camera did blink blue-yellow while booting (on status LED) - mvBlueFOX3-xxxx: When coming from standby with active binning or decimation the AOI was automatically reduced by the binning/decimation factor. 05.10.2018 2.31.1574.0 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: - mvBlueFOX-2064G/C: Frame rate increased up to 60fps at full AOI. - mvBlueFOX3-2XXX: SmartFrameRecall can only be enabled if the image width is a multiple of 8 - USB 3.0 devices will now identify themselves 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. 05.07.2018 2.30.1463.0 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. 17.05.2018 2.29.1385.0 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. 12.04.2018 2.28.1323.0 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 acquisitionStart 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. 09.02.2018 2.27.1231.0 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%. 06.12.2017 2.26.1138.0 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. 18.10.2017 2.25.1029.0 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. 20.09.2017 2.24.975.0 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) 10.08.2017 2.23.928.0 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. 10.07.2017 2.22.883.0 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(). 01.06.2017 2.21.833.0 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. 01.05.2017 2.20.774.0 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. 21.03.2017 2.19.711.0 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. 09.02.2017 2.18.651.0 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. 02.02.2017 2.17.641.0 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. 20.01.2017 2.16.624.0 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. 13.12.2016 2.15.578.0 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. 01.11.2016 2.14.507.0 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. 21.09.2016 2.13.460.0 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. 30.08.2016 2.12.426.0 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 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. - mvBlueFOX3-2024aG/C, mvBlueCOUGAR-X104fG/C: Minimal exposure time increased to 30 usec. BUGS FIXED: - mvBlueFOX3-2xxx devices at certain temperatures sometimes did not boot correctly. 04.08.2016 2.11.383.0 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. 17.06.2016 2.10.326.0 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. 19.05.2016 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. 08.04.2016 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. 28.03.2016 BUGS FIXED: - mvBlueCOUGAR-X1010G/C: Acquisition could stop when changing exposure time. Bug introduced in version - mvBlueFOX3-2032G, mvBlueFOX3-2051G: Although mvAcquisitionFrameRateLimitMode = mvDeviceLinkThroughput more than 380MByte/s were possible, which results in delayed images. 24.02.2016 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. 27.01.2016 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 21.12.2015 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. 01.12.2015 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. 10.11.2015 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. 13.10.2015 NEW FEATURES: - Version Number increased. 09.10.2015 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. 18.09.2015 1.6.483.0 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. 03.09.2015 1.6.475.0 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. 13.08.2015 1.6.461.0 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. 22.06.2015 1.6.414.0 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'. 26.05.2015 1.6.403.0 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. 13.05.2015 1.6.393.0 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'. 26.03.2015 1.6.360.0 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. 30.01.2015 1.6.306.0 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. 15.01.2015 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. 02.12.2014 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. 23.10.2014 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. 09.10.2014 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 - 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. 26.08.2014 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 21.07.2014 BUGS FIXED: - CCDs: Changing the exposure time did not always work correctly. 24.06.2014 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. 26.05.2014 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. 14.04.2014 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 10.04.2014 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: Under 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. 21.03.2014 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) 06.03.2014 BUGS FIXED: - mvBlueCOUGAR-X(D) with CCDs: No frames with minimum exposure times. (Bug introduced in - 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. 20.02.2014 BUGS FIXED: - mvBlueCOUGAR-3X120aG: Timers were not working. - USB2 compatibility improved. (mvBlueFOX3) CHANGED BEHAVIOUR: - SequencerControl: Visibility = Expert. Not saved in UserSet. 10.02.2014 NEW FEATURES: - Secure firmware update added, starting with this firmware all file updates will (mvBlueFOX3) be verified before being activated. - mvBlueFOX3-1031G/C: Internal pixel clock increased to 75 MHz (was 68,75 MHz). (mvBlueFOX3) Now 30Hz@1920x1080 is possible. BUGS FIXED: - GenCP pending acknowledge detection changed to a timer based version. (mvBlueFOX3) 20.01.2014 BUGS FIXED: - LinescanMode (E2V-sensors): Correct overtrigger behaviour. - mvBlueCOUGAR-X120bG: Device stopped responding when constantly changing exposure values from the application. - Wrong pixel format info in leader when changing the 'PixelFormat' (e.g. Mono10 -> Mono12). - mvBlueFOX3-1013x, mvBlueFOX3-1020x: Use correct AOI now. 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. - mvBlueFOX3-1031x: FrameStartTrigger disabled. 12.12.2013 BUGS FIXED: - Booting host system with a camera already connected could lead to this device (mvBlueFOX3) becoming inaccessible. - Triggermode also works after timeout. (needs mvIMPACT Acquire 2.5.18 or greater) (mvBlueFOX3) - 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) 12.11.2013 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. 17.10.2013 NEW FEATURES: - Initial version with mvBlueFOX3 support. - 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. 23.07.2013 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 23.05.2013 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. 02.04.2013 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 14.03.2013 NEW FEATURES: - Record mode is available for mvBlueCOUGAR-XD now. - Support for 'ChunkExposureTime' and 'GevLinkSpeed' added. CHANGED BEHAVIOUR: - AcquisitionFrameRateLimitMode introduced for all devices. This replaces the mvBlueCOUGAR-XD specific 'AcquisitionFrameRateAuto' feature which was introduced in firmware version - Maximum of TriggerDelay increased from 10000 us to UINT_MAX us. - ICX674/694/814: Support for pixel clock 66 Mhz added. - MT9M02x: Width and OffsetX must be a multiple of 2 now. - Fast changing of exposure time. Not (yet) for MT9P031, MT9J003. BUGS FIXED: - ICX625: Missing columns in the middle of the image. - ICX655/625: TriggerSoftware commands immediately after modifying the trigger mode did not trigger an images. - mvBlueCOUGAR-XD12x: YUV format was transferred incorrectly resulting in wrong colours. - 'mvGevSCBW' maximum value is now set correctly for 100Mbit/s links. 18.01.2013 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 20.12.2012 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 - 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. 17.12.2012 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. 26.11.2012 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. 11.07.2012 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 03.04.2012 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. 08.06.2011 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. 23.11.2010 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) 02.11.2010 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. 03.09.2010 29.07.2010 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). 14.07.2010 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. 11.06.2010 BUGS FIXED: - Sometimes the mvBlueCOUGAR-X failed to boot. (Bug introduced in firmware version 10.06.2010 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. NEW FEATURES: - HW-LUT: 10To10 for colour models, 12To10 for mono models. - mvBlueCOUGAR-Xx00w Test image. - Temperature limit hysteresis added. 31.05.2010 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). 30.03.2010 16.03.2010 This will fix an issue where the device could not be accessed if the devices boot sequence was complete before the surrounding network was up.