Learn more about Image Acquisition Toolbox

Version 3.3 (R2009a) Image Acquisition Toolbox Software

This table summarizes what's new in Version 3.3 (R2009a):

New Features and Changes	Version Compatibility Considerations	Fixed Bugs and Known Problems	Related Documentation at Web Site
Yes Details below	Yes Summary	Bug Reports Includes fixes	No

New features and changes introduced in this version are:

• Windows 64 Support

• Image Acquisition Tool Enhancements

• New Hamamatsu Hardware Support

• Bug Fix: Changing ROI Now Affects the Frame Rates for QImaging Devices

• Property Removed from Matrox Helios XA and Solios XA Boards

• Bug Fix: Trigger Names for Matrox Helios XA and Solios XA Boards Fixed

• Bug Fix: Image Acquisition Tool Disk Logging Now Works on Systems with Non-US Locales

• New Trigger Configuration Names for Some DALSA Sapera Boards

Windows 64 Support

Support for 64-bit versions of Windows^® for the following adaptors has been added:

• National Instruments^®

• Hamamatsu

• QImaging^®

• Winvideo

Note   The Image Acquisition Toolbox™ software does not impose any restrictions on the Windows 64 support for the above listed vendors. However, the vendors 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-Party Adaptor on the Image Acquisition 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 hardware, 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 where you could not increase the frame rate by specifying the 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 ROIPosition is changed would now affect the frame rate:

video_object =videoinput('qimaging',1,'MONO16_512x512');
set(video_object,'ROIPosition',[XOffset, YOffset, Width, Height]);
start(video_object);
for i=1:number_of_frames
	   tic
   trigger(video_object); 
   wait(video_object,15,'logging'); 
   elapsedTime = elapsedTime + toc;
   frameNumber = frameNumber + 1;
end

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

Compatibility Considerations

Customers who use the TriggerFormat 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 trigger names will need to update their code to use the correct trigger names.

Bug Fix: Image Acquisition Tool Disk Logging Now Works on Systems with Non-US Locales

There was a bug that prevented the Image Acquisition Tool from working properly when used on systems with non-US locales and when using the disk logging feature. Now when you use the disk logging feature on a non-US system, it will work properly.

New Trigger Configuration Names for Some DALSA Sapera Boards

In previous releases of the Sapera adaptor, some boards had trigger sources trigger3, trigger4, and trigger5. 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 trigger sources 3, 4, and 5 do not.

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

For these boards, in R2008b the trigger sources use their actual names:

• trigger3 – boardSync

• trigger4 – toBoardSync

• trigger5 – cameraControlToBoardSync

In R2008b if you attempt to set the trigger 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 triggerinfo or triggerconfig.

Loading saved objects is not an issue. Potentially an object saved in R2008a would not load in R2009a or 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.

Version 3.4 (R2009b) Image Acquisition Toolbox Software

Version 3.2 (R2008b) Image Acquisition Toolbox Software

© 1984-2009- The MathWorks, Inc.    -   Site Help   -   Patents   -   Trademarks   -   Privacy Policy   -   Preventing Piracy   -   RSS