|
|
|
| R2012a Documentation → Image Acquisition Toolbox | |
Learn more about Image Acquisition Toolbox |
|
| Contents | Index |
This table summarizes what's new in Version 4.1 (R2011a):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems |
|---|---|---|
| Yes Details below | Yes Summary | Bug
Reports Includes fixes |
New features and changes introduced in this version are:
Support for vendor-specific properties is now available in the GigE Vision adaptor. In addition to the general source properties, you can now use most vendor-specific properties that your hardware supports.
You can use these vendor-specific properties both in the command-line toolbox, and the Image Acquisition Tool. In the Image Acquisition Tool, they are available on the Device Properties tab. You can also access them when using the From Video Device block, using the Edit Properties button on the Source Block Parameters dialog box.
You can get property help for device-specific properties using the imaqhelp function. See imaqhelp for more information.
Support for VideoWriter has been added to the disc logging for the toolbox. This provides additional codecs, including MJPEG2000, and large file support.
Note that this support is only available in the command-line toolbox. It is not supported in the Image Acquisition Tool.
For more information on using VideoWriter, see Acquiring Image Data > Logging Image Data to Disk > Logging Data to Disk Using VideoWriter in the Image Acquisition User's Guide.
Support has been added for additional Matrox® hardware.
Support has also been added for Matrox hardware on 64-bit Windows.
In addition to the Solios and Helios families of frame grabbers, the Radient family is now supported. This includes support for these new boards:
Radient eCL
Solios eV-CL
Support has also been added for DALSA® hardware on 64-bit Windows.
Support has been added for additional DALSA hardware:
Xcelera-CL LX1 Base
Xcelera-CL PX4 Dual
Xcelera-CL PX4 Full
Xcelera-CL PX4 SE
Xcelera-CL + PX8 Full (Preliminary)
Xcelera-HS PX8 (Preliminary)
Xcelera-LVDS PX4
XRI-1600
Xcelera-AN LX1 Quad
The following changes have been made in order to update DALSA support for 64-bit operating systems and for Windows 7:
Rename the coreco adaptor to dalsa.
Drop support for custom errors when using Sapera 5.
Transition support for the IFC adaptor to a new adaptor called dalsaifc.
The coreco adaptor has been renamed dalsa.
The imaqhwinfo and videoinput commands will detect if a user uses the adaptor name coreco, and will replace it with dalsa. This will be accompanied by a warning.
Loading of saved resources in .mat, .iat, and .mdl files will be transitioned to the new name in the same manner, and also be accompanied by a warning.
Support for custom errors when using Sapera 5 is discontinued, in order to better support Sapera 6 and 7.
In R2008b the toolbox discontinued support of version 5 of Sapera and began to generate an error if it was used. This error no longer appears, and the old adaptor will not load.
Support for the IFC adaptor is transitioned to a new adaptor called dalsaifc.
The original coreco adaptor could be used for both IFC and Sapera. In order to support upgrades to the current dalsa adaptor, we have broken out the IFC support into a separate adaptor called dalsaifc.
The imaqhwinfo and videoinput commands will detect if a user specifies the adaptor name coreco and dalsaifc is loadable on the system, then it will replace it with dalsaifc. This will be accompanied by a warning.
Loading of saved resources in .mat, .iat, and .mdl files is transitioned to the new name in the same manner, and is accompanied by a warning.
In order to allow for vendor-specific properties to be supported in the GigE Vision adaptor, triggering properties will be set as device-specific properties. This affects only customers who adopted the use of the GigE adaptor that was released in R2010b and who are using hard-coded calls to triggerconfig for hardware triggering. You will now be able to set up more advanced triggering properties using the vendor-specific properties that your hardware supports.
If you used a general TriggerCondition property value such as FallingEdge or RisingEdge, or a TriggerSource property value such as Line1-FrameStart, you need to use a device-specific property going forward.
For example, you might now use a TriggerCondition property value such as DeviceSpecific and a TriggerSource property value such as DeviceSpecific, and then set the FrameStartTriggerSource device-specific property to Line1, FrameStartTriggerMode to On, and FrameStartTriggerActivation to RisingEdge.
If you continue to use the general triggerconfig values, you will get a warning, though the toolbox attempts to set device-specific values for you.
An example warning:
Warning: With the current version of the GigE Vision adaptor, hardware triggering has changed. However, we will attempt to configure the hardware trigger as specified.
In R2011a, the old trigger configurations are removed and a warning is issued, as described above, and the toolbox sets device-specific properties if it can detect them. In a future release, the toolbox will error if an old trigger configuration is used.
 | Version 4.2 (R2011b) Image Acquisition Toolbox Software | Version 4.0 (R2010b) Image Acquisition Toolbox Software |  |
Includes the most popular MATLAB recorded presentations with Q&A sessions led by MATLAB experts.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
