Release Notes
(
MIL’s USB3
Vision system)
August, 2015
This document
outlines what is new with MIL’s USB3 Vision system and explains the
current limitations and particularities.
It also presents
last-minute information that did not make it into the manual or
on-line help. Note that this help file serves to complement your
manual. The information found in this file overrides your formally
documented material.
Contents
1.
Matrox Imaging
Library’s USB3 Vision system.
1.1
Differences
between MIL 10 Update 30 and MIL 10 Update 19.
1.2
What's new in MIL
10 Update 30.
1.3
Differences
between MIL 10 Update 19 and MIL 10 Update 1.
1.4
What's new in MIL
10 Update 19.
4.
Supported
operating systems.
5.
Location of
examples (in the help file)
Bug
Fixes to MIL's USB3 Vision system. Note that installing MIL Update
30 will include all the contents of MIL Update 1 and Update 19.
·
No new
Features.
·
Fixed
an error in
MdigAlloc
(M_GC_DEVICE_USER_NAME) caused when the
name was programmed without power cycling.
·
Fixed a
Synchronization Lost event at the end of
MdigProcess
().
·
Improved packed and YUV444
PixelFormatsupport.
·
Fixed
camera access errors in
MdigHookFunction
(M_CAMERA_PRESENT).
·
Fixed
MdigInquire(M_SOURCE_SIZEX/Y) to return
the camera Width/Height feature without scaling factor.
·
Added
compliance with newly released
GenCP1.1 and USB3Vision 1.0.1
specifications.
·
Fixed
race condition when grabbing with multiple host controllers that
caused a driver exception.
·
Fixed
acquisition with multiple cameras (n>4) with event enabled that
caused a Windows stop error.
·
Default
color buffer type changed from RGB24 to BGR32 for optimal display
performance.
·
In case
a Synchronization Lost event occurs, the driver will automatically
attempt to resynchronize the image stream with the camera.
This will reset the
BlockIDto 0.
·
Camera
Assistant can now be used to manipulate USB3 Vision devices and to
diagnose some setup problems.
·
The MIL
Help now has information about MIL's USB3 Vision system.
·
New
features and bug fixes to MIL's USB3 Vision system.
·
Added
support for MIL's USB3 Vision system in Capture Assistant.
·
Added
support for streaming Monochrome and Bayer data of 10 and 12 bit
packed pixel format.
·
Added
support for
MdigAlloc
(M_GC_DEVICE_USER_NAME).
·
Added
support for
MdigAlloc
(M_GC_MANIFEST_ENTRY()).
·
Added
support for
MdigAlloc
(M_GC_XML_DOWNLOAD_SKIP and
M_GC_XML_FORCE_DOWNLOAD).
·
Added
support for
MdigInquire
(M_CAMERA_PRESENT).
·
Added
support for
MsysHookFunction
(M_CAMERA_PRESENT).
·
Added
support for
MdigHookFunction
(M_CAMERA_PRESENT).
·
Added
support for
MdigInquire/
MsysGetHookInfo
(M_GC_UNIQUE_ID_STRING).
·
Added
MultiCamerahardware-specific example.
·
Added
acquisition statistics to be displayed in Camera Assistant.
·
If 2
cameras are used and camera M_DEV0 is removed from the PC, M_DEV1
will be remapped as M_DEV0, if M_DEV1 and M_DEV0 were not
allocated.
·
MdigGetHookInfo
(
M_GC_FRAME_BLOCK_ID) Called from within
MdigProcesscallback is now reporting
the data trailer packet’s
BlockIdinstead of the data Leader
packet’s
BlockId.
·
Fixed
MdigInquire
(M_PROCESS_FRAME_MISSED) which always
returned 0.
·
Fixed
MdigAlloc
() failure with certain cameras.
·
Fixed
issue regarding cameras sometimes not being detected after
hibernate/sleep.
·
Fixed
USB3 Vision Diagnostic Tool that would enter an endless loop with
certain cameras.
·
Fixed
MdigAlloc
() operation that failed if one or more
features listed in the specified DCF (Digitizer Configuration File)
is not writeable in the camera.
·
Fixed
YUV 411 and 444 Pixel formats causing corrupted images.
·
Fixed
MdigGrab
() with triggers enabled needing 2
triggers to grab one frame.
·
Fixed
driver exception caused when starting a grab with certain cameras
under Windows 7.
·
Fixed
MdigGrab
() failure with error message caused by
an unaligned image size.
·
Fixed
MdigGetHookInfo
(M_CORRUPTED_FRAME,
M_GC_FRAME_BYTES_RECEIVED, M_GC_FRAME_LINE_COUNT,
M_GC_FRAME_STATUS_CODE) which did not return the appropriate value.
Added
USB3 Vision-specific information to the MIL Help Reference and MIL
Help Hardware-specific Notes.
·
Added
USB3 Vision support.
·
Added
support for DCF selection.
·
Added a
detailed Tree View; displays entire Ethernet and USB ecosystems.
·
Added
Statistics Report module. Generated Statistics reports are
automatically included in a
SysInfo.
·
Added
command-line dump mode. Used when generating a
SysInfo.
·
Added
various diagnostics.
·
Device
triggers can now be controlled by the Feature Browser or by the
triggers section of the Acquisition Properties tab.
·
Added
GigE Vision multicast monitor support.
·
Added
network adapter configuration parameters (Jumbo Packets, Receive
Buffers, Interrupt Moderation) when selecting a network adapter
from the Acquisition Device's tab.
·
Network
Adapter statistics are now generated using Windows performance
counters.
·
Matrox
Inspector needs an image width that is a multiple of 4 pixels. Not
following this rule will make Inspector crash or report errors.
·
BGR or
RGB, packed (10 or 12 bits) pixel format are not supported.
·
If you
are experiencing
Synchronisationlost errors or image
corruption under Windows 7 with
RenesasUSB 3.0 Host Controller, make
sure you are using the Host controller driver version 2.1.39.0 or
later for the 2.x series and 3.0.23.0 or later for 3.x series.
·
When
using events, if a camera disconnect (M_CAMERA_PRESENT hook gets
called), in
sequense
MdigHook
(M_UNHOOK),
MdigFree()/
MdigAlloc()
MdigHook() must be called instead of
only
MdigProcess(M_START/M_STOP) as shown in
the Hardware specific example
MultiCamers.
·
In
Intellicam, you can now modify a DCF
while the feature browser is open, when working with a Camera Link
camera accessed using the
GenICam
CLProtocol. However, the feature
browser will no longer
workwithTeledyne DALSA Camera Link
cameras using the
GenICam
CLProtocolwith
Saperasoftware version 7.3 or lower. In
this case, update the
Saperasoftware to version 7.4 or
higher.
·
Fixed
possible
Intellicamcrash when clicking on "Dump
state to DCF" in the camera configuration tab when the camera
contains a LUT.
·
Fixed
issue where error messages would not be displayed when starting the
feature browser.
·
Fixed
possible
Intellicamcrash when aborting a grab
from a triggered camera that is not receiving any triggers.
·
Fixed
non-
GenICamsystems that could not grab
after U1 was installed.
·
Fixed
Intellicamfailure to load a DCF that
was saved with "Dump state to DCF" button.
This section lists the
supported operating systems.
·
32-bit
Windows® 7
·
64-bit
Windows® 7
·
32-bit
Windows® 8.1
·
64-bit
Windows® 8.1
v
If
using Windows 7, you must install the USB 3.0 host controller
driver prior to using MIL's USB3 Vision system.
In the
help file, the location information written at the top of examples
might not be up-to-date. Use MIL Example Launcher to find an
example on disk.
·
Your
camera must be USB3 Vision compliant in order to work with the
Matrox USB3 Vision driver. For more information, you can refer to
http://www.visiononline.org/vision-standards.cfm.
·
Note
that a diagnostic tool is available from
MilConfigto troubleshoot the connection
to USB3 Vision cameras. Capture assistant can also be used to
diagnose USB issues and generate a usage statistic report.
Matrox Imaging Library (MIL) 10.0 Update 30
(c) Copyright Matrox Electronic Systems Ltd., 1992-
2015
.
1.1
Differences
between MIL 10 Update 30 and MIL 10 Update 19.
1.2
What's new in
MIL 10 Update
30.
1.2.1
New features
summary.
1.2.2
Bug
Fixes.
1.2.3
Behavior
change.
1.3
Differences
between MIL 10 Update 19 and MIL 10 Update 1.
1.4
What's new in
MIL 10 Update
19.
1.4.1
New features
summary.
1.4.2
Behavior
change.
1.4.3
Bug
Fixes.
1.4.4
Documentation.
1.4.5
Capture
Assistant.
3.
Intellicam
bug
fixes.