The software described in this document is furnished under a license agreement. The software may be used
or copied only under the terms of the license agreement. No part of this manual may be photocopied or
reproduced in any form without prior written consent from The MathW orks, Inc.
FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation
by, for, or through the federal government of the United States. By accepting delivery of the Program
or Documentation, the government hereby agrees that this software or documentation qualifies as
commercial computer software or commercial computer software documentation as such terms are used
or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and
conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern
theuse,modification,reproduction,release,performance,display,anddisclosureoftheProgramand
Documentation by the federal government (or other entity acquiring for or through the federal government)
and shall supersede any conflicting contractual terms or conditions. If this License fails to meet the
government’s needs or is inconsistent in any respect with federal procurement law, the government agrees
to return the Program and Docu mentation, unused, to The MathWorks, Inc.
Trademarks
MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See
www.mathworks.com/trademarks for a list of additional trademarks. Other product or brand
names may be trademarks or registered trademarks of their respective holders.
Patents
The MathWorks products are protected by one or more U.S. patents. Please see
www.mathworks.com/patents for more information.
Summary by Version ...............................1
Version 3.5 (R2010a) Image Acquisition Toolbox
Software
Version 3.4 (R2009b) Image Acquisition Toolbox
Software
Version 3.3 (R2009a) Image Acquisition Toolbox
Software
Version 3.2 (R2008b) Image Acquisition Toolbox
Software
Version 3.1 (R2008a) Image Acquisition Toolbox
Software
........................................4
........................................7
........................................8
........................................13
........................................17
Contents
Version 3.0 (R2007b) Image Acquisition Toolbox
Software
Version 2.1 (R2007a) Image Acquisition Toolbox
Software
Version 2.0 (R2006b) Image Acquisition Toolbox
Software
Version 1.10 (R2006a) Image Acquisition Toolbox
Software
Version 1.9.x (R14SP3) Image Acquisition Toolbox
Software
Version 1.8 (R14SP2) Image Acquisition Toolbox
Software
........................................19
........................................21
........................................24
........................................25
........................................26
........................................27
iii
Version 1.7 (R14SP1) Image Acquisition Toolbox
Software
Version 1.6 (R14+) Image Acquisition Toolbox
Software
Version 1.5 (R14) Image Acquisition Toolbox
Software
Version 1.1 (R13SP1) Image Acquisition Toolbox
Software
Version 1.0 (R13.0.1+) Image Acquisition Toolbox
Software
Compatibility Summary for Image Acquisition Toolbox
Software
........................................36
........................................38
........................................42
........................................45
........................................47
........................................48
ivContents
SummarybyVersion
This table provides quick access to what’s new in each version. For
clarification, see “Using Release Notes” on page 2 .
Image Acquisition Toolbox™ Release No tes
Version
(Release)
Latest Versi
V3.5 (R2010a
V3.4 (R2009b)
V3.3 (R2009a)
V3.2 (R2
V3.1 (R2008a)
V3.0 (R2007b)
V2.1 (
V2.0 (R2006b)
008b)
R2007a)
New Features
and Changes
on
Yes
)
Details
Yes
Details
Yes
Details
Yes
Details
Yes
Details
Yes
Detai
Yes
Details
Yes
Details
Version
Compatibilit
Consideratio
Yes
Summary
NoBug Reports
Yes
Summary
Yes
Summary
Yes
Summary
Yes
ls
Summa
Yes
Summary
NoBug Reports
ry
y
ns
Fixed Bugs
and Known
Problems
Bug Reports
Includes fix
Includes fixes
Bug Repor
Includes
Bug Reports
Includes fixes
Bug Reports
Includes fixes
Bug Rep
Inclu
Bug Reports
Includes fixes
Includes fixes
es
ts
fixes
orts
des fixes
Related
Documentation
at Web Site
Printable R elease
Notes: PDF
Current product
documentation
No
No
No
No
No
No
No
V1.10 (R2006a)
.9.x (R14SP3)
V1
V1.8 (R14SP2)
Yes
ails
Det
Yes
Details
Yes
Details
NoBug
NoBug Reports
No
Reports
ludes fixes
Inc
Includes fixes
ixed bugs
F
No
No
No
1
Image Acquisition Toolbox™ Release Notes
Version
(Release)
V1.7 (R14SP1)
V1.6 (R14+)
V1.5 (R14)
V1.1 (R13SP1)
V1.0 (R13.0.1+)
New Features
and Changes
Yes
Details
Yes
Details
Yes
Details
Yes
Details
Yes
Details
Version
Compatibility
Considerations
No
No
No
No
NoNoNo
Fixed Bugs
and Known
Problems
Fixed bugs
Fixed bugs
Fixed bugs
Fixed bugs
Related
Documentation
at Web Site
No
No
No
No
Using Release Notes
Use release notes when upgrading to a newer version to learn about:
• New features
• Changes
• Potential impact on your existing files and practices
Review the release notes for other MathWorks™ products required for this
product (for example, MATLAB
bugs, or compatibility considerations in other products impact you.
If you are upgrading from a software version other than the m ost recent one,
review the current release notes and all interim versions. For example, when
you upg rade from V1.0 to V1.2, review the release notes for V1.1 and V1.2.
®
or Simulink®). Determine if enhancements,
What Is in the Release Notes
New Features and Changes
• New functionality
2
SummarybyVersion
• Changes to existing functionality
Version Compatibility Con si derations
When a new feature or change introduces a reported incompatibility between
versions, the Compatibility Considerations subsection explains the
impact.
Compatibility issues reported after the product release appear under Bug
Reports at The MathWorks™ Web site. Bug fixes can sometimes result
in incompatibilities, so review the fixed bugs in Bug Reports for any
compatibility impact.
Fixed Bugs and Known Problems
The MathWorks offers a user-searchable Bug Reports database so you can
view Bug Reports. The development team updates this database at release
time and as more information becomes available. Bug Reports include
provisions for any known workarounds or file replacem ents. Information is
available for bugs existing in or fixed in Release 14SP2 or later. Information
is not avail able for all bugs in earlier releases.
Access Bug Reports using y our MathWorks Account.
3
Image Acquisition Toolbox™ Release Notes
Version 3.5 (R2010a) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.5 (R2010a):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “Session Log in the Image Acquisition Tool” on page 4
• “Additional Export Location in the Image Acquisition Tool” on page 4
• “Support for Additional DCAM Trigger Modes” on page 5
• “Disk Logging on Windows Vista 64-bit Platforms” on page 5
WhiteReference Property Ignored for Matrox Devices” on page 5
• “
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
Printable Release
Notes: PDF
Current product
documentation
Session Log in the Image Acquisition Tool
The new session log dynam ically records every action you perform in the
Image Acquisition Tool. The corresponding command-line functionality for
actions on a videoinput object or videosource object is reflected in the log. The
title displays the name of the device, as shown in the Hardware Browser.
You can save the contents of the session log to a MATLAB code file or copy
it to another source. For more inform ation, see “Saving and Copying the
Session Log”.
Additional Expor t Location in the Image Acquisition
Tool
Youcannowexportdatatoan.avi file after it has been acquired. Previously
you could export data to a MAT-file, the MATLAB Workspace, or a tool in
4
Version 3.5 (R2010a) Image Acquisition Toolbox™ Software
the Image Processing Toolbox™ (Image Tool, Image File, or Movie Player).
Nowyoucanalsoexporttoan.
compression, on the export.
For more information, see “Exporting Data”.
avi file a nd set .avi file options, such as
Support for Additional DCAM Trigger Modes
You can now use all trigger modes and all trigger inputs supported by DCAM
cameras, as of R2010a. Previous toolbox releases supported only trigger mode
0. Support for the additional trigger modes and inputs will not affect any
existing code you may be using.
For information on the additional trigger modes, including use of parameters,
see “Setting DCAM-Specific Trigger Modes”.
Disk Logging on Windows Vista 64-bit Platforms
When using Windows V ista ™ 64-bit platforms, if you used disk logging to
an .
avi file, you could see a crash if there was no colormap set. With other
versions of Windows
®
, you could see corrupted data.
Compatibility Considerations
Now if you use disk logging to an .avi file without setting a colormap, you will
get a warning and a default grayscale colormap will be set in order to avoid
this problem.
WhiteReference Property Ignored for Matrox Devices
In pr ev ious ve rsions of the M a t rox®adaptor, the properties WhiteReference,
BlackReference,andInputGain could all be used. Starting in R2010a, the
WhiteReference property will be ignored.
This applies to the following devices:
• Matrox Helios XA
• Matrox Odyssey XA
• Matrox Solios XA
5
Image Acquisition Toolbox™ Release Notes
Compatibility Considerations
The first phase of deprecating this property is that the WhiteReference
property will be ignored. You should use the BlackReference property
and the
WhiteReference property and it will be ignored. The warning specifies that
you can use
The second phase of the deprecation, in a future release, is that you will
receive a error. The third stage, in a future release, will be removal of the
property.
InputGain property. You will receive a warning if you use the
BlackReference property and the InputGai n property together.
6
Version 3.4 (R2009b) Image Acquisition Toolbox™ Software
Version 3.4 (R2009b) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.4 (R2009b):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoBug Reports
New features and changes introduced in this version are:
Fixed Bugs an d
Known Problems
Includes fixes
Related
Documentation at
Web Site
No
Custom getter in the Adaptor Kit
You can now query properties from a camera in the adaptor kit using the
custom getter. This allows you to return the current value of a dynamically
changing property, and execute a function when you get the property value.
Suppose you have a camera that has a cooler to control the temperature of
the cam era. You may need to make an acquisition when it reaches a certain
temperature. You could use the custom getter to query the temperature
property of the camera.
This custom getter functionality works for properties that have an underlying
storagetypeof
See Querying Device Properties in the Image Acquisition Toolbox Adaptor Kit
User’s Guide for informatio n on this feature.
double, int, double array,andint array.
7
Image Acquisition Toolbox™ Release Notes
Version 3.3 (R2009a) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.3 (R2009a):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “Windows 64 Support” on page 8
• “Image Acquisition Tool Enhancements” on page 9
• “New Hamamatsu Hardware Support” on page 9
• “Bug Fix: Changing ROI Now Affects t h e Frame Rates for QImaging
Devices” on page 9
• “Property Removed from Matrox Helios XA and Solios XA Boards” on
page 10
• “Bug Fix: Trigger Names for Matrox Helios XA and Solios XA Boards
Fixed” on page 10
• “Bug Fix: Image Acquisition Tool Disk Logging Now Works on Systems
with Non-US Locales” on page 11
• “New Trigger Configuration Names for Some DALSA Sapera Boards” on
page 11
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
No
Windows 64 Support
Support for 64-bit versions of Windows for the following adaptors has been
added:
• National Instruments
• Hamamatsu
• QImaging
®
8
®
Version 3.3 (R2009a) Image Acquisition Toolbox™ Software
• Winvideo
Note The Image Acquisition Toolbox™ software does no t impose any
restrictions on the Windows 64 support for the above listed vendors. However,
the v endors may impose restrictions. If you encounter any problems, please
see your vendor or driver documentation.
Image Acquisition Tool Enhancements
Minor enhancements have been added to the Image Acquisition Tool,
including the ability to register third-party adaptors.
To register a third-party adaptor, click Tools > Register a Third-PartyAdaptor on the Image Acquisitio n Tool menu.
New Hamamatsu Hardware Support
Support has been added for the following Hamamatsu hardware:
• 1394b S800 ORCA-R2
• C9300-221
For the latest information about supported hardw are , visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
Bug Fix: Changing ROI Now Affects the Frame Rates
for QImaging Devices
A previous bug w here you could not increasetheframeratebyspecifyingthe
region of interest for QImaging devices is fixed. It is now possible to increase
the frame rate by specifying the region of interest.
For example, the following code where
affect the frame rate:
Property Removed from Matrox Helios XA and Solios
XA Boards
Support for the TriggerFormat property is being removed for the following
Matrox boards:
• Helios XA
• Soios XA
10
Compatibility Considerations
Customers who use the Tri gger Format property for these boards are affected.
This property is no longer supported. The trigger format can be specified in
the DCF camera configuration file created by Matrox Intellicam.
Bug Fix: Trigger Names for Matrox Helios XA and
Solios XA Boards Fixed
The trigger names for the Helios XA boards were not correct. The timer
trigger sources for the Solios XA and the Helios XA boards were also not
correct. In both cases, they were using the XCL trigger names.
These have been corrected and now the XA boards are using the XA triggers
and the XCL boards are using the XCL triggers.
Compatibility Considerations
Customers who were using the old triggernameswillneedtoupdatetheir
code to use the correct trigger names.
Version 3.3 (R2009a) Image Acquisition Toolbox™ Software
Bug Fix: Image Ac
Works on Systems
There was a bug th
properly when u
logging featu
system, it wil
at prevented the Image Acquisition Tool from working
sed on systems with non-US locales and when using the disk
re. Now when you use the disk logging feature on a non-US
l work properly.
New Trigger C
Sapera Board
In previous
trigger3, t
driver, the
trigger1 an
trigger so
releases of the Sapera adaptor, some boards had trigger sources
rigger4
se trigger sources have actual names. Note that the sources
d
urces3,4,and5donot.
s
,andtrigger5. In the current release of the Sapera
trigger2 correspond with actual inputs on the board, while
quisition Tool Disk Logging Now
with Non-US Locales
onfiguration Names for Some DALSA
Compatibility Considerations
The only c
supporte
• x64-CL i
• x64-LVD
ustomers that will be impacted are those that were using previously
d boards and the improper trigger source names. These boards are:
Pro
S
• x64 Ful
• x64 Dua
For th
• trigg
• trig
• trig
In R
eive a warning and the new trigger source name will be used. In R2009a,
rec
you
ndard invalid trigger source error message.
sta
l
l
eseboards,inR2008bthetriggersources u se their actual names:
er3 –
boardSync
ger4 –
ger5 –
2008b if you attempt to set the trigger source to trigger3-5, you will
will receive an error message, and in R2009b, you will receive the
toBoardSync
cameraControlToBoardSync
11
Image Acquisition Toolbox™ Release Notes
Note that the old names will only show up in the warning, and will not show
up in the output from
Loading saved objects is not an issue. Potentially an object saved in R2008a
would not load in R2009a o r beyond once the warning message is turned into
an error. However, trigger configurations of videoinput objects are not saved.
Therefore trigger configurations which will be invalid in R2009a will not be
saved for objects in R2008a or earlier.
triggerinfo or triggerconfig .
12
Version 3.2 (R2008b) Image Acquisition Toolbox™ Software
Version 3.2 (R2008b) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.2 (R2008b):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “Interactive ROI Tool” on page 13
• “Additional Export Locations” on page 14
• “New .avi File Save Option” on page 14
• “Improved Device Properties Tab” on page 14
• “Preview Window Has 16-Bit Data Support” on page 15
• “Additional DALSA Hardware Support” on page 15
• “The Image Processing Toolbox Software Required to Use the Image
Acquisition Toolbox Software” on page 15
• “New Trigger Configuration Names for Some DALSA Sapera Boards” on
page 16
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
No
Interactive ROI Tool
You can now select a region of interest (ROI) interactively while previewing
your image data in the Image Acquisition Tool. The interactive tool lets
you select and adjust a region of interest in the Preview Window while
previewing. The drag-and-draw mechanism makes setting a region of interest
much easier and faster.
For more information on this feature see Setting a Regio n of Interest
Interactively in the Image Acquisition Toolbox documentation.
13
Image Acquisition Toolbox™ Release Notes
Additional Expo
You can export da
Acquisition Too
can export to ad
single-frame a
These three op
For more infor
Acquisition
New .avi Fil
In the Image
as an .avi fi
increment
videos of o
acquire 10
them for l
as
sample
automati
For more
Image Ac
le. In version R2008b an option was added to automatically
the .avi file nam es. This is useful if you want to acquire multiple
ne or more subjects. For example, a lab technician may want to
seconds of video on a group of five different cultures and save
ater analysis. The technician may want resulting file names such
_0001.avi
cfilenameincrementinglikethisexample.
information on logging data to .avi files, see Disk Logging in the
quisition Toolbox documentation.
ta that has been acquired in memory in the Image
ltoaMAT-fileortheMATLABWorkspace. InR2008byou
ditional locations, including Image Tool and Im a ge File for
cquisitions, and Movie Player for multiple-frame acquisitions.
tions are provided by the Image Processing Toolbox software.
mation on exporting data, see Exporting Data in the Image
Toolbox documentation.
eSaveOption
Acquisition T ool, when you log an acquisition to disk, it is saved
, sample_0002.avi, etc. This new option allows for
rt Locations
14
Improv
The Dev
devic
impro
addit
while
Prop
ct What’s This? to see the help on that property.
sele
For
ameters in the Image Acquisition Toolbox documentation.
Par
ed Device Properties Tab
ice Properties tab in the Image Acquisition Tool is used to set
e-specific properties. In R2008b, the Device Properties pane has been
ved. Most properties now feature a slider for setting the value, in
ion to the capability of setting it manually. You can adjust the slider
previewing and see the res ults dynamically.
erty help was also added in the pane. Right-click a property name and
more information on setting device properties, see Setting Device-Specific
Version 3.2 (R2008b) Image Acquisition Toolbox™ Software
Preview Window H
The Image Acquis
that is built int
16-bit image da
but m any camera
display now su
Additional D
Support has b
• X64 Xcelera
• X64 Xcelera
• X64-CL-Ex
• PC2-Comp™
For the la
Image Acq
www.math
test information about supported hardware , visit the
uisition Toolbox product page at the MathWorks Web site
works.com/products/imaq
The Imag
Use the
The Ima
Tool, n
produc
ge Acquisition Toolbox product, including the Image Acquisition
ow requires you to have a license for the Image Processing To olbox
t starting in R2008b.
ition Toolbox Preview window and the Preview window
o the Image Acquisition Tool now support the display of up to
ta. The Preview window was designed to only show 8-bit data,
s return 10-, 12-, 14-, or 16-bit data. The Preview window
pports these higher bit-depth cameras.
ALSA Hardware Support
een a dde d for the following new DALSA
-CL PX4 Dual™
-CL PX4 Full™
press™
Express
e Processing Toolbox Software Required to
Image Acquisition Toolbox Software
as 16-Bit Data Support
®
hardware:
.
already have the Image Processing Toolbox product, you do not need to
If you
do any
If yo
Acqu
want
for
Pro
bot
If
thing.
u do not have the Image Processing Toolbox product, the Image
isition Toolbox software R2008a and earlier will continue to work. If you
to us e R2008b or future releases, and you have a current active license
the Image Acquisition Toolbox software, you can download the Image
cessing Toolbox product for free. New customers will need to purchase
h products to use the Image Acquisition Toolbox product.
you hav e any ques tions, please contact MathWorks customer service.
15
Image Acquisition Toolbox™ Release Notes
New Trigger Configuration Names for Some DALSA
Sapera Boards
In previous releases of the Sapera adaptor, some boards had trigger sources
trigger3, trigger4,andtrigger5. In the current release of the Sapera
driver, these trigger sources have actual names. Note that the sources
trigger1 and trigger2 correspond with actual inputs on the board, while
triggersources3,4,and5donot.
Compatibility Considerations
The only customers that will be impacted are those that were using previously
supported boards and the improper trigger source names. These boards are:
• x64-CL iPro
• x64-LVDS
• x64 Full
• x64 Dual
16
For these boards, in R2008b the trigger sources will use their actual names:
• trigger3 –
• trigger4 – toBoardSync
• trigger5 – cameraControlToBoardSync
InR2008bifyouattempttosetthetrigger source to trigger3-5, you will
receive a warning and the new trigger source name will be used. In R2009a,
you will receive an error message, and in R2009b, you will receive the
standard invalid trigger source error message.
Note that the old names will only show up in the warning, and will not show
up in the output from
Loading saved objects is not an issue. Potentially an object saved in R2008a
would not load in R2009a o r beyond once the warning message is turned into
an error. However, trigger configurations of videoinput objects are not saved.
Therefore trigger configurations which will be invalid in R2009a will not be
saved for objects in R2008a or earlier.
boardSync
triggerinfo or triggerconfig .
Version 3.1 (R2008a) Image Acquisition Toolbox™ Software
Version 3.1 (R2008a) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.1 (R2008a):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “New Hamamatsu Hardware Support” on page 17
• “National Instruments RTSI Support” on page 17
• “Corrected Spelling of Two QImaging Device-Specific Property Values –
Phase 3” on page 18
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
No
New Hamamatsu Hardware Support
Support has been added for the follow ing new hardware:
• Hamamatsu C9100–13
For the latest information about supported hardw are , visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
National Instruments RTSI Suppor t
Some National Instruments boards support RTSI, which is a real-time system
interface that allows you to use multiple boards together. This feature
involves hardware synchronization. The Image Acquisition Toolbox software
now s upports use of the RTSI functionality in National Instruments boards
that are supported by the toolbox.
17
Image Acquisition Toolbox™ Release Notes
Corrected Spelling of Two QImaging Device-Specific
Property Values – Phase 3
In release R2007a, the following QImaging device-specific property values
were changed to correct the spelling:
• The fan speed property value
ThreeQuarter.
• The readout speed property value
ThreeQuater is now correctly spelled
2M5 is now correctly spelled 2.5M.
Compatibility Considerations
In R2007a, use of the incorrect spelling produced a warning. In R2007b, use
of the incorrect spelling produced an error. In this release, the incorrectly
spelled property name will no longer work.
For detailed information on the property spelling changes and the new error,
see Compatibility Considerations for R2007a.
18
Version 3.0 (R2007b) Image Acquisition Toolbox™ Software
Version 3.0 (R2007b) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 3.0 (R2007b):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “Introduction of the Image Acquisition Tool” on page 19
• “Support for National Instruments Hardware” on page 19
• “Corrected Spelling of Two QImaging Device-Specific Property Values –
Phase 2” on page 20
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
No
Introduction of the Image Acquisition Tool
The functionality of the Image Acquisition Toolbox software is now available
in a desktop application. You connect directly to your hardware in the tool
and can preview and acquire image data. You can log the data to M ATLAB in
several formats, and also generate an AVI file, right from the tool.
The Image Acquisition Tool provides a desktop environment that integrates a
preview/acquisition area wi th acquisition parameters so that you can change
settings and see the changes dynamically applied to your image data.
You can open the Image Acquisition Tool by doing one of the following:
• PXI™-1407, PXI™-1409, PXI™-1411, PXI™-1422, and PXI™-1428
For the latest information about supported hardw are , visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
Corrected Spelling of Two QImaging Device-Specific
Property Values – Phase 2
In the previous release, R2007a, the following QImaging device-specific
property values were changed to correct the spelling:
• The fan speed property value
ThreeQuarter.
• The readout speed property value
ThreeQuater is now correctly spelled
2M5 is now correctly spelled 2.5M.
Compatibility Considerations
In R2007a, use of the incorrect spelling produced a warning. In this release,
R2007b, use of the incorrect spelling will produce an error.
For detailed information on the property spelling changes and the new error,
see Compatibility Considerations for R2007a.
20
Version 2.1 (R2007a) Image Acquisition Toolbox™ Software
Version 2.1 (R2007a) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 2.1 (R2007a):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
Yes
Summary
New features and changes introduced in this version are:
• “New Image Acquisition Toolbox Simulink Block” on page 21
• “New Hardware Support” on page 21
• “Improved DCAM Driver” on page 22
• “Corrected Spelling of Two QImaging D ev ice -Specific Property Values”
on page 22
Fixed Bugs an d
Known Problems
Bug Reports
Includes fixes
Related
Documentation at
Web Site
No
New Image Acquisition Toolbox Simulink Block
A new Simulink block, the From Video Device block, allows Simulink users to
acquire image a n d video data streams from image acquisition devices such
as cameras and frame grabbers in order to incorporate the image data into a
Simulink model. The new block also offers the ability to configure and preview
the acquisition directly from Simulink.
Compatibility Considerations
The former Image Acquisition Toolbox block, the Video Input b lo ck, is
obsolete. If you have models that use the Video Input block, you should
change them to use the new From Video Device block, which offers additional
functionality and features.
New Hardware Support
• Support for additional QImaging devices – R etiga 2000RV, Retiga
4000RV, and Rolera MGi.
21
Image Acquisition Toolbox™ Release Notes
• Support for additional Matrox devices – Helios XA and Solios XA.
For the latest information about supported hardw are , visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
Improved DCAM Driver
The Image Acquisition Toolbox software now uses an improved DCAM
adaptor, w hich uses version 6.4.2 of the CMU DCAM driver. The new driver
supports 1394B firewire and DCAM 1.3.1. It also supports new frame rates
of 120 and 240 frames per second.
Corrected Spelling of Two QImaging Device-Specific
Property Values
The following QImaging device-specific property values have changed to
correct the spelling:
22
• The fan speed property value
ThreeQuarter.
• The readout speed property value
ThreeQuater is now correctly spelled
2M5 is now correctly spelled 2.5M.
Compatibility Considerations
Fan Speed Property
Some QImaging video input source objects have a fan speed property if the
camera supports it. If they do, one of the possible values is ¾ speed. This
property value was misspelled as
(when the QImaging adaptor was introduced in the Image Acquisition Toolbox
software Version 1.9, Release 2006a). The change allows the correct spelling
to work instead of causing an error.
VIDEOINPUT objects: When loaded from MAT files, any misspelling will
be silently corrected. You could notice the value is different if you inspect
the
FanSpeed property. M isspellings saved in R2006a/R2006b would load
seamlessly in R2007a (backward compatible). Corrected spellings saved
ThreeQuater instead of ThreeQuarter
Version 2.1 (R2007a) Image Acquisition Toolbox™ Software
in R2007a, however, would error (not load) in R2006a/R2006b (forward
incompatible).
SET: The misspelling will be obsoleted over several releases. In R2007a both
spellings will be supported (backward compatible) but the misspelling will
generate a warning. In the next significant release (IAT v2.1+1), the warning
will be changed to an error that suggests correct spelling. In the following
significant release (IAT v2.1+2), the error will become the standard incorrect
property value response. C orrections written in R2007a would error in
R2006a/R2006b (forward incompatible).
GET: Will return the correctly spelled value, even if set is called with the
misspelling.
Readout Speed Property
Most/all QImaging video input source objects have a readout speed property.
If they do, one of the possible values is 2.5 MHz. This property value
was misspelled as
2M5 instead of 2.5M (when the QImaging adaptor was
introduced in the Image Acquisition Toolbox software Version 1.9, Release
2006a). The change will allow the correct spelling to work instead of erroring.
VIDEOINPUT objects: When loaded from MAT files, any misspelling will
be silently corrected. You could notice the value is different if you inspect
the
Readout property. Misspellings saved in R2006a/R2006b would load
seamlessly in R2007a (backward compatible). Corrected spellings saved
in R2007a, however, would error (not load) in R2006a/R2006b (forward
incompatible).
SET: The misspelling will be obsoleted over several releases. In R2007a both
spellings will be supported (backward compatible) but the misspelling will
generate a warning. In the next significant release (IAT v2.1+1), the warning
will be changed to an error that suggests correct spelling. In the following
significant release (IAT v2.1+2), the error will become the standard incorrect
property value response. C orrections written in R2007a would error in
R2006a/R2006b (forward incompatible).
GET: Will return the correctly spelled value, even if set is called with the
misspelling.
23
Image Acquisition Toolbox™ Release Notes
Version 2.0 (R2006b) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 2.0 (R2006b):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoBug Reports
New features and changes introduced in this version are
• Hamamatsu hardware support.
(For the latest information about supported hardware, visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.)
Fixed Bugs an d
Known Problems
Includes fixes
Related
Documentation at
Web Site
No
24
Version 1.10 (R2006a) Ima ge Acquisition Toolbox™ Software
Version 1.10 (R2006a) Image Acquisition Toolbox
Software
New Features and
Changes
Yes
Details below
This table summ
Version
Compatibility
Considerations
NoBug Reports
New features and changes introduced in this version are:
• Support for additional Coreco boards.
• Support for the Coreco Sapera driver. The Image Acquisition Toolbox
software now supports both the Coreco IFC driver and the Coreco Sapera
driver.
• Support for additional Matrox boards.
• Support for QImaging devices.
For the latest information about supported hardware, visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
• Native Bayer Demosaicing. This new color space setting will interpolate
Bayer pattern encoded images into standard RGB images. If your camera
uses B ayer filtering, the Image Acquisition Toolbox software now supports
the Bayer pattern and can return color if desired.
arizes what’s new in Version 1.10 (R2006a):
Fixed Bugs an d
Known Problems
Includes fixes
Related
Documentation at
Web Site
No
25
Image Acquisition Toolbox™ Release Notes
Version 1.9.x (R14SP3) Image Acquisition Toolbox
Software
New Features and
Changes
Yes
Details below
This table summ
Version
Compatibility
Considerations
NoBug Reports
New Features in Version 1.9. New features introduced in this version are:
• Support for the Matrox Meteor-II/Camera Link fram e grabber
For the latest information about supported hardware, visit the
Image Acquisition Toolbox product page at the MathWorks Web site
www.mathworks.com/products/imaq.
• Significant improvements to the Video Input block for use with Simulink
• Improved performance of t he Video Preview window (the version built
with Handle Graphics
In addition, this version includes the inaugural release of the Image
Acquisition Toolbox Adaptor Kit, Version 1.0. The adaptor kit is a C++
framework for developing hardware adaptors. You can use this kit to add
support for additional hardware to the toolbox.
arizes what’s new in Version 1.9.x (R14SP3):
Fixed Bugs an d
Known Problems
Includes fixes
®
components)
Related
Documentation at
Web Site
No
26
New Features in Version 1.9.1. This version introduces support for the
Matrox He lios XCL cam era link frame grabber. Note that this device requires
Matrox Imaging Library (MIL), Version 8.0.
Upgrading from an Earlier Release. The following issue is related to
upgrading from a previous release:
• The Helios XCL requires Matrox Imaging Library (MIL), Version 8.0.
Version 1.8 (R14SP2) Image Acquisition Toolbox™ Software
Version 1.8 (R14SP2) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 1.8 (R14SP2):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoYes
New features and changes introduced in this version are:
• “User-Customiza b le Video Preview Window”
• “Support for Format 7 Added to the DCAM Adaptor”
• “Getting Information About the N ative Data Type”
• “Acquiring Data in Single-Precision Format”
Fixed Bugs an d
Known Problems
Details below
Related
Documentation at
Web Site
No
User-Customizable Video Preview Window
The Image Acquisition Toolbox software includes a new open-architecture
reimplementation of the Video Preview window. The new Video Preview
window provides the same capabilities as its predecessor: it displays a
live preview of the video stream from a particular video input object, with
information about the video resolution, video frame timestamp, and the
status of the video input object.
In addition, because this previewing capability is built using standard
MATLAB Handle Graphics features, you can access the video data using
standard Handle Graphics techniques. For example, you can now use the
preview function to direct the live preview video stream to any Handle
Graphics image object. This lets you include the previewing capability in
GUIs of your own creation.
To start the Video Preview window, use the
vid = videoinput('winvideo');
preview(vid)
preview function, as follow s:
27
Image Acquisition Toolbox™ Release Notes
The Video Preview window displays a preview of the live video stream being
provided by the d ev ice.
28
Stopping the Live Preview Video Stream
The toolbox includes a new function, stoppreview, that you can use to stop the
live preview video stream for a specific video input object. For example, the
followingcodestopsthepreviewvideostream started in the previous example:
stoppreview(vid)
Support for Format 7 Added to the DCAM Adaptor
The Imag e Acquisition Toolb ox DCAM adaptor now supports DCAM Format 7
(also called partial scan format). When creating a video input object with the
DCAM adaptor, the prefix
of formats returned by
F7_ identifies Format 7 video formats in the list
imaqhwinfo.
Getting Information About the Native Data Type
With this release, imaqhwinfo now includes information about the native
data type of a device, based on the video format used to create the video
input object.
To get this information, call the
video input object as an arg ument.
imaqhwinfo function specifying a
imaqhwinfo returns a structure
Version 1.8 (R14SP2) Image Acquisition Toolbox™ Software
containing information about the object and this structure now contains a
NativeDataType field that contains this information.
Acquiring Data in Single-Precision Format
The getdata function can now return image data in single-precision format.
Major Bug Fixes
Version 1.8 of the Image Acquisition Toolbox software includes the following
bug fixes.
DCAM Monochrome 16-Bit Formats Returned as Big-Endian
The DCAM adaptor now correctly returns data in Mono 16-bit format as
big-endian, as specified in the DCAM specification (1.30). Previously, the
DCAM adaptor returned Mono 16-bit data in little-endian.
PreviewNoLongerProducesErrorswhenROIPositionIsSet
for Matrox Meteor-II/1394
You can now preview data from the Matrox Meteor-II/1394 board after
configuring the
following error:
ROIPosition property. Previously, previewing produced the
??? matrox: DigControl Error
Value is out of range
(Error detected on 1394 system)
Miscellaneous Fixes to Video Input Blo ck
This release includes several fixes to the Video Input block in the Image
Acquisition Block Library. The fixes include the following:
• The Source Block Parameters dialog box now updates the Input video
format list when you change the selected device.
• The Source Block Parameters dialog box no longer contains duplicate
entries in the Input video format list.
29
Image Acquisition Toolbox™ Release Notes
Upgrading from a Previous Release
The following issue is related to upgrading from a previous release.
Update of the IFC Libraries Used with Coreco Devices
The Image Acquisition Toolb ox software now requires Version 5.8.0 of the IFC
libraries when you are working with Coreco devices.
Known Software and Documentation Issues
This section describes some known software issues with Version 1.8:
• “General Issues” on page 30
• “Matrox Matrox Devices” on page 32
• “Data Translation Devices” on page 33
• “Image Acquisition Block Library” on page 34
30
General Issues
• Warning messages indicating that the toolbox was unable to allocate
memory can be displayed multiple times under the following scenario:
1 The Video Preview window is open.
2 The
3 Hardware trigger executes, initiating an acquisition.
To prevent this problem, close the Video Preview window.
• You might encounter a problem logging data to an AVI file. For example,
the value of the
To remedy this problem, try changing the value of the AVI file object’s
Compression property to 'none'.
Video Preview Window Performance Issues. The Video Preview window
may experience performance issues when previewing large images or when
previewing image data from multiple devices. If performance problems occur,
or MATLAB appears to stop responding, the following actions may help
alleviate some of these issues:
imaqmem function is used to limit memory to a very small amount.
DiskLoggerFrameCount property might remain at 0 (zero).
Version 1.8 (R14SP2) Image Acquisition Toolbox™ Software
- Using the ROIPosition property to configure a smaller resolution
- Resizing the preview window such that the entire image is not visible
- Creating a custom preview window GUI by following the example in
“Previewing Data in Custom GUIs” in th e Image Acquisition Toolbox
User’s Guide documentation. Doing so will allow you to scale the image
size down when the preview window is resized.
• Avoid previewing multiple video input objects simultaneously. In general,
for best performance, prev iew only one video input object at a time.
If performance issues p ersist, you can disable the new Video Preview window
and use the preview window included in previous releases . Use the following
commands to disable the new Video Preview window. Note, however, that
when you disable the new Video Preview window, the Handle Graphics
customization features of the
Restarting MATLAB will reenable the MATLAB Handle Graphics based
Video Preview window. To manually reenable the new Video Preview window,
execute the following commands:
• There are known issues with the U SB Creative WebCam drivers that can
lead to crashes and computer reboots. It is recommended that you only
install one of these devices per system.
• Some device drivers, most commonly Video for Windows (VFW) drivers,
mightrequestadevicetobeselectedviaadialogbox. Bychoosingadevice
from the dialog box, you can associate an image acqu isition object w ith
an installed device.
TV Tuner Devices. The following list covers known issues w ith TV Tuner
Devices (devices with an
• Video input objects as sociated with a TV tuner card like the ATI Rage
Theater Video Capture card might be created with an invalid analog format
selected. To correct this, modify the value of the
property on the currently selected video source object. (Use the
getselectedsource function to retrieve the currently selected video source
object.)
AnalogVideoFormat video source property):
AnalogVideoFormat
32
• While accessing a TV tuner card, a blue screen crash can occur if you
repeatedly open and close the Video Preview windo w.
Matrox Matrox Devices
• The Matrox MIL or MIL-Lite Library is required and must be installed
before you can use the toolbox.
• The Gencout program, which is related to the Genesis board, will start
whenyoufirsttrytousethetoolbox.ThiscausesMATLABtolosefocus. To
work around this behavior, uninstall the Genesis Native Library. Gencout
is not used by the Image Acquisition Toolbox software, but it is installed by
default by the installation program for the Genesis drivers.
• It is recommended that MIL’s nonpaged reserved memory be greater than
the size of four incoming images. You can change this value using the
Matrox MIL Configuration utility, provided with MIL.
Version 1.8 (R14SP2) Image Acquisition Toolbox™ Software
- For standard RS170 and CCIR monochrom e formats, at least 2 MB of
nonpaged memory is recommended.
- For standard NTSC and PAL color formats, at least 8 MB is
recommended.
• Two- and four-band images are not supported. D ual-channel video,
however, is supported via a DCF file if the r esulting image is a single band.
• UARTs are not supported.
• If the device supports exposure t imer s, they are exposed as video source
object properties using the prefix
using the manual bypass exposure model as described in the Matrox MILUser’s Guide. Do not set these parameters while the object is previewing or
running, to avoid invalid combinations of parameters while the object is
accessing the device.
• User digital inputs are not currently supported. User digital output
values are exposed as video source object properties using the prefix
UserOutputBit.
Timer. These properties are implemented
Data Translation Devices
• You should update device drivers to Imaging Omni CD 2.2 drivers. These
drivers are available from the support page at
®
• Data Translation
nonvolatile memory. Set this value as follows:
DevicesReserved Memory Recommendations
3120
313x
3152
drivers allow for the reservation of nonpaged,
Nonpaged reserved memory must be greater than the
size of four incoming images. Recommended values are:
For standard RS170 and CCIR monochrome formats, at
least 2 MB of nonpaged memory
For standard NTSC and PAL color formats, at least 8 MB
You can change this value in the DT driver properties;
see the Data Translation User’s Guide for your hardware
for more information.
datatranslation.com.
33
Image Acquisition Toolbox™ Release Notes
DevicesReserved Memory Recommendations
3152-LS
3153
3154
3155
3157
Nonpaged reserved memory must be greater than the size
of the total number of frames provided by the hardware
for a whole trigger. Use this equation to determine the
size of the total number of frames:
total = FramesPerTrigger * FrameGrabInterval
where
FramesPerTrigger and FrameGrabInterval are
properties of the video input object. Refer to the Image
Acquisition Toolbox documentation for more information
on these properties.
• Line scan mode for the 3152-LS is not supported.
• For the 3152-LS, 3153, 3154, 3155, and 3157 devices in immediate trigger
mode, the last image frame of a trigger and the first image frame of the
next trigger might not be adjacent frames in the incoming video; that is,
one or more frames might be dropped between triggers.
• The 3152 might require certain color depths from your video card in
order to fully function. To determine whether the proper color depth is
selected, start
both
'Passthru' and 'Single Frame Acquire' function properly. If
'Passthru' fails, try using a different color depth, e.g., 24-bit truecolor
DTAcquire (provided with your hardware) and verify that
instead of 32-bit truecolor.
34
Image Acquisition Block Library
The following are known issues with the Image Acqu isition Block Li brary:
• Support limited to Windows video devices compatible w ith DirectX
Video Input block only supports Windows video devices that are compatible
with DirectX. To determine whether a device is DirectX compatible, use the
AMCAP.EXE utility included with the Image Acquisition Toolbox software in
the
toolbox\imaq\imaq directory. You can also down load this utility from
• Invalid devices in the Device name list — When you first open the Video
Input block mask, MATLAB searches your computer and populates the
®
—The
Version 1.8 (R14SP2) Image Acquisition Toolbox™ Software
Device name list in the Block Parameters dialog box with al l the image
acquisition devices available on your system. If you disconne c t or change
the device connected to the computer while MATLAB is running, the mask
will not reflect these hardware changes. The Device name list continues to
list the devices initially found when the mask was first opened. The only
way to update this list is to restart MATLAB; using the Image Acquisition
Toolbox function
imaqreset has no effect.
• No support for DV camcorders — The Image Acquisition block library does
not currently support DV camcorders. Attempting to access the Image
Acquisition block library while a DV camcorder is connected to your system
will cause MATLAB to hang. This will be addressed in a future release.
• Support only for RGB24 formats — The Video Input block only supports
RGB24 formats. Other video formats, such as RGB8 and Y422, cause an
error when the model is run. This will be corrected in a future release.
• No preview or co nfigu ration capabilities — The Video Input block does
not support a preview window, nor does it provide access to device
configuration parameters. To configure a device or see a preview of the
acquired data, you must use utility programs supplied with the device or
third-party applications, such as the Microsoft
AMCAP.EXE utility is included with the Image Acquisition Toolbox software
in the
toolbox\imaq\imaq directory. Any device configuration performed
®
AMCAP.EXE utility. The
using a third-party application will affect the device in the Simulink model.
Note Make sure to close whatever third-party application you use f or
previewing or configuration before running your Simulink model.
35
Image Acquisition Toolbox™ Release Notes
Version 1.7 (R14SP1) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 1.7 (R14SP1):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoYes
New features and changes introduced in this version are:
• Matrox Meteor-II/1394 — The Matrox adaptor now supports the
Matrox Meteor-II/1394 adaptor board for digital video acquisition. The
Meteor-II/1394 board supports IEEE
IIDC Digital Camera Specification using Matrox Imaging Library (MIL).
Fixed Bugs an d
Known Problems
Details below
®
1394 video cameras based on the
Related
Documentation at
Web Site
No
Known Software and Documentation Issues
This section describes some known software problems with Version 1.7.
Limitations of Matrox Meteor-II/1394 Support
The support for the Matrox Meteor-II/1394 board includes the following
limitations:
• Automatic mode for properties is not supported.
• DCAM absolute properties are not supported.
36
These settings are not exposed by the Matrox Imaging Library and are
therefore unavailable.
Known Issue with the Matrox Meteor-II/1394 Support
The Matrox Meteor-II/1394 board provides only limited support for the
ROIPosition property. You can define a region of interest using the
ROIPosition property, specifying the value as a four-element vector of the
form
Version 1.7 (R14SP1) Image Acquisition Toolbox™ Software
[XOffset YOffset Width He ight]
However, for the Meteor-II/1394 board, the value of the XOffset and YOffset
elements of the position vector must be 0 (zero).
Other Issues
See the issues described in Known Software and Documentation Issues for
Version 1.8.
37
Image Acquisition Toolbox™ Release Notes
Version 1.6 (R14+) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 1.6 (R14+):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoYes
New features and changes introduced in this version are:
• New Image Acquisition Block Library
• DCAM Adaptor Now Supports Absolute Values
• Performance Enhancements
Fixed Bugs an d
Known Problems
Details below
Related
Documentation at
Web Site
No
New Image Acquisition Block Library
The Image Acquisition Toolbox software now in cl ud es a Simulink block
library, called the Image Acquisition Block Library. The block library contains
one block: the Video Input block. You can use this block to bring live video
data into a simulation.
To open the Image Acquisition Block Library, enter
imaqlib
38
at the MATLAB prompt. MATLAB displays the contents of the block library
in a separate window:
Version 1.6 (R14+) Image Acquisition Toolbox™ Software
DCAM Adaptor Now Supports Absolute Values
The DCAM adaptor now supports properties that let you specify the value of
a property as an absolute value, if the device supports that capability for
a particular feature.
As defined by the IIDC DCAM specification, the values specified for properties
can be interpreted as either relative or absolute. Relative values only have
meaning in relation to a device-specific reference point. For example, if you
set the shutter speed property to 4000, this value might be interpreted as 4000
seconds for one device, but 4000 milliseconds for another device. Previously,
the DCAM adaptor device-specific properties only supported relative values.
To provide more precise control, the IIDC DCAM specification also defines
absolute values, where the units are specified as part of the definition. For
example, the DCAM specification defines the units for shutter speed property
as seconds. So, if you specify a value of 0.10032 for this property, any D CA M
device that supports absolute values would interpret the value as 100.32
milliseconds. To find out the units used with a feature that supports absolute
values, see Appendix B of the IIDC 1394-based DCAM specification or check
the documentation that came with your device.
39
Image Acquisition Toolbox™ Release Notes
New Properties
To support both absolute and relative v alues, the DCAM adaptor now provides
additional device-specific properties. If a device supports absolute values for
a particular feature, the DCAM adaptor creates a property, using the same
featurenameastherelativepropertybut with the word “Absolute” appended
to it. For example, if a device supports both relative and absolute values for
shutter speed, the DCAM adaptor creates properties named
ShutterAbsolute.
When it creates an absolute value property, the DCAM adaptor also creates
apropertytocontrolthetypeofvaluethedeviceuses. Thispropertyhas
thesamenameasthefeaturewiththeword“Control”appendedtoit. For
example, if the DCAM adaptor created the
creates a
If you set either the relative or absolute properties, the corresponding mode
property is set to
property, the value of the ShutterMode property changes to 'manual'. Setting
the control property has no effect on the mode property.
ShutterControl property.
Shutter and
ShutterAbsolute property, it a lso
'manual'. For example, if you set the Shut terAbsolute
40
Performance Enhancements
Because of a number of enhancements to the way that the toolbox handles
video frames, you might no tice increased performance in the following areas:
• Faster acquisition with the
• Previewing should consume less CPU overhead.
• Frame handling during acquisition should be faster.
Note The actual performance improvement achieved depends on factors such
as video format, resolution, and CPU speed.
getdata, peekdata,andgetsnapshot functions.
Version 1.6 (R14+) Image Acquisition Toolbox™ Software
Major Bug Fixes
This release includes the following major bug fix:
• For long acquisitions, the metadata information reported from
was sometimes incorrect. This included reporting the wrong values for
the
AbsTime and FrameNumber fields of the getdata metadata structure.
This has been fixed.
getdata
Upgrading from a Previous Release
The following are some change s from previous releases:
• The
• The way the toolbox determines the default value of device-specific
FieldStart property for the Coreco PC-Vision device has be en
removed. To specify which field the device uses as the first fie ld for an
interlaced video signal, use the
properties for Matrox devices has changed. In some cases, the initial value
of the property at object creation time (and the default value returned
by the
previous releases. To ensure that properties that are important to your
application have t he value you expect, you should explicitly set them . Do
not depend on the default value.
propinfo function) might be different than what was returned in
StartingField property.
Other Issues
See the issues described in Known Software and Documentation Issues for
Version 1.8.
41
Image Acquisition Toolbox™ Release Notes
Version 1.5 (R14) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 1.5 (R14):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoYes
New features and changes introduced in this version are:
• Additional Hardware Support
• New Utility Functions
• Changes to Existing Functions
Fixed Bugs an d
Known Problems
Details below
Related
Documentation at
Web Site
No
Additional Hardware Support
The Image Acquisitio n Toolbox software provides support for specific image
acquisition devices by providing adaptors that enab le a connection between
MATLAB and devices. The toolbox supports devices from specific hardware
vendors, such as Matrox or Data Translation, or for g eneral categories of
devices, such as consumer-level video devices that support a connection via
DirectX or Video for Windows drivers.
This releas e provides support for the following additional vendors and device
categories:
42
• Coreco Imaging, Inc. image acquisition devices, including the PC 2-Vision™ ,
the PCVision, the PCVisionplus, the PC-RGB, and the PC-DIG
• Matrox CronosPlus
• Digital cameras that comply with the IIDC 1394-based Digital Camera
(DCAM) Specification
New Utility Functions
The toolbox includes the following new utility functions:
Version 1.5 (R14) Image Acquisition Toolbox™ Software
• isrunning — Determines if a video input object is running
islogging — Determines if a video input object is logging
•
obj2mfile — Saves a video input object by creating an M-file containing
•
the commands necessary to recreate the object
Changes to Existing Functions
The toolbox includes the following enhancements to existing functions and
properties:
• You can now specify the color space of the returned image data by setting
the value of the
ReturnedColorSpace property.
• The
•
• The
imaqmem function can now retrieve specific fields by field name.
flushdata now accepts an array of video input objects
wait function can now wait until an object stops running or logging.
Previously, this function only waited until an object stopped running.
Major Bug Fixes
The Image Acquisitio n Toolbox software 1.5 includes several important bug
fixes made since Version 1.1.
Limitations from the Previous Version Lifted
The following are limitations that existed in previous versions of the toolbox
that are no longer issues:
• Matrox acquisition devices that support image scaling now scale images
correctly for any selected video source object. Previously, the toolbox only
honored the
source object.
• DV devices, such as camcorders,werelimitedtothedefault
provided by the device. Addi tional formats are now available for these
devices.
• DV devices, such as camcorders, no longer experience a short lag between
the preview window display, and what is actually captured by the device.
XScaleFactor and YScaleFactor properties of the first video
'dvsd' format
43
Image Acquisition Toolbox™ Release Notes
Incorrect MIL-Lite Version No Longer Crashes MATLAB
The Image Acquisition Toolbox software requires MIL-Lite Version 7.0 or
later. Now, if you attempt to create a video input object for a Matrox device
and the installed version of the Matrox MIL-Lite library is earlier than
Version 7.0, the toolbox issues an error.
The trigger Function Now Accepts Vector of Video Input Objects
You can now pass a vector of video input objects to the trigger function.
Previously, this function only accepted a single video input object.
The winvideo Adaptor Works with Devices That Provide
Input/Output Capabilities
The toolbox winvideo adaptor now lets you acquire video from devices that
supportvideooutputandvideoinputonthesamecard,suchasthenVidiaTV
tuner card.
Known Software and Documentation Problems
See the issues described in Known Software and Documentation Issues for
Version 1.8.
44
Version 1.1 (R13SP1) Image Acquisition Toolbox™ Software
Version 1.1 (R13SP1) Image Acquisition Toolbox Software
This table summarizes what’s new in Version 1.1 (R13SP1):
New Features and
Changes
Yes
Details below
Version
Compatibility
Considerations
NoYes
New features and changes introduced in this version are:
• Region of interest (ROI) configurations using the
now supported for all hardware devices.
• A troubleshooting utility is now included in the
matlabroot/toolbox/imaq/imaq directory called AMCap.exe. This utility
canbeusedtoverifythatWindowsvideo devices are working properly.
• Enhanced memory management is now provided to optimize image frame
storage efficiency.
• A warning is issued when accessing Windows video hardware using an
incorrect DirectX version.
Fixed Bugs an d
Known Problems
Details below
Related
Documentation at
Web Site
No
ROIPosition property are
Major Bug Fixes
The Image Acquisition Toolbox software 1.1 includes several bug fixes made
since Version 1.0. This section describes the particularly important Version
1.1 bug fixes.
• A memory leak associated with running
• The toolbox now stops acquisition hardware when you press Ctrl+C to
interrupt the
• When using Matrox DCF cam era files, the toolbox now configures all video
source objects according to the camera file settings.
• A MATLAB segmentation fault that occurred when using old versions of
the Matrox MIL library has been fixed. The toolbox now displays a message
instead.
getsnapshot function.
peekdata has been fixed.
45
Image Acquisition Toolbox™ Release Notes
• A segmentation fault associated with accessing the Data Translation 3157
frame grabber has been fixed.
46
Version 1.0 (R13.0.1+) Ima ge Acquisition Toolbox™ Software
Version 1.0 (R13.0.1+) Image Acquisition Toolbox
Software
Introduction t
o the Image Acquisition Toolbox
Software
The Image Acqu
MathWorks tha
aMATLABsess
Acquisition
represent t
For example
Matrox fram
construct
vid = videoinput('matrox');
Using the
the conne
or syntax for the device installed on your system.)
ction to the device.
Softwar
The too
hardwa
Acquis
lbox requires the device drivers for the installed image acquisition
re. For the most up-to-date list of supported hardware, go to the Image
ition T oolbox product page (
isition Toolbox software 1.0 is a new product from The
t lets you connect to an image acquisition device from within
ion. Based on MATLAB object technology, the Image
Toolbox software provides functions for creating objects that
he connection to the device.
, the following command creates an object
egrabber. (Usethe
properties of the
e and Hardware Requirements
vid associated with a
imaqhwinfo function to retrieve the object
vid object, you can control various as pects of
www.mathworks.com/products/imaq).
47
Image Acquisition Toolbox™ Release Notes
Compatibility Summary for Image Acquisition Toolbox
Software
This table summarizes new features and changes that might cause
incompatibilities when you upgrade from an earlier version, or wh en you
use files on multiple versions. Details are provided in the description of the
new feature or change.
Version (Release)New Features and Changes with
Version Compatib ility Impact
Latest Version
V3.5 (R2010a)
V3.4 (R2009b)
V3.3 (R2009a)See the Compatibility
See the Compatibil ityConsiderations subheading
for this change:
• Disk Logging on Windows Vista
64–bit
• WhiteReference Property Ignored
for Matrox D evices
None
Considerations subheading
for each of these new features or
changes:
• New Trigger Configuration
Names for Some Dalsa-Coreco
Boards
• Property Removed from Matrox
Helios X A and S olio s XA B oards
• Trigger Names for Matrox Helios
XA and Solios XA Boards Fixed
48
Compatibility Summary for Image Acquisition Toolbox™ Software
Version (Release)New Features and Changes with
Version Compatib ility Impact
V3.2 (R2008b)See the Compatibility
Considerations subheading
for each of these new features or
changes:
• New Trigger Configuration
Names for Some Dalsa-Coreco
Boards
V3.1 (R2008a)See the Compatibility
Considerations subheading
for this change:
• Corrected Spelling of Tw o
QImaging D evice-Specific
Property Values
V3.0 (R2007b)See the Compatibility
Considerations subheading
for this change:
• Corrected Spelling of Tw o
QImaging D evice-Specific
Property Values
V2.1 (R2007a)See the Compatibility
Considerations subheading
for each of these new features or
changes:
• Corrected Spelling of Tw o
QImaging D evice-Specific
Property Values
• New Image Acquisition Toolbox
Simulink Block
V2.0 (R2006b)
V1.10 (R2006a)
None
None
49
Image Acquisition Toolbox™ Release Notes
Version (Release)New Features and Changes with
Version Compatib ility Impact
V1.9.x (R14SP3)
V1.8 (R14SP2)
V1.7 (R14SP1)
V1.6 (R14+)
V1.5 (R14)
V1.1 (R13SP1)
V1.0 (R13.0.1+)
None
None
None
None
None
None
None
50
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.