Products & Services Solutions Academia Support User Community Company

Learn more about Signal Processing Blockset   

Version 6.10 (R2009b) Signal Processing Blockset Software

This table summarizes what's new in Version 6.10 (R2009b):

New Features and ChangesVersion Compatibility ConsiderationsFixed Bugs and Known ProblemsRelated Documentation at Web Site
Yes
Details below
Yes
Summary
Bug Reports
Includes fixes
Printable Release Notes: PDF

Current product documentation

New features and changes introduced in this version are:

"What's This?" Context-Sensitive Help Added for Signal Processing Blockset Blocks

R2009b introduces context-sensitive help for most Signal Processing Blockset blocks. To find out if a block supports context-sensitive help, look for the question mark icon ( ) in the lower-left corner of the block dialog box. When you see this icon, you can get help on any parameter on the block mask by right-clicking on the parameter name.

Periodogram and Spectrum Scope Blocks Support Mean-Square Spectrum

Previously, the Periodogram and Spectrum Scope blocks supported only Power Spectral Density (PSD) visualizations. Now, these blocks also support Mean-Square Spectrum (MSS) computations. The Spectrum Scope block also supports MSS visualizations. As opposed to the PSD, which measures power per unit of frequency, the MSS measures power at a specific frequency.

Compatibility Considerations

The changes in the Spectrum Scope block result in the following two compatibility considerations.

Inherit sample increment from input parameter renamed Inherit sample time from input.   The Inherit sample increment from input parameter of the Spectrum Scope block has been renamed Inherit sample time from input. The behavior of the parameter remains the same.

Tunability Status Changed for Two Parameters.   The Inherit sample time from input (previously Inherit sample increment from input) and Sample time of original time series parameters of the Spectrum Scope block are no longer tunable during simulation. To change these parameters while you are working with a model, you must stop a running simulation, change the parameter, and then start the simulation again.

Power Spectrum Estimation Blocks Compute PSD Like the Signal Processing Toolbox Spectrum Objects

The behavior of the following blocks has changed so that they produce identical results to the Signal Processing Toolbox™ spectrum objects:

To produce correct results and align with the Signal Processing Toolbox spectrum objects, these blocks now scale their output by the sampling frequency, Fs. In addition to producing different results in R2009b, these five blocks have two new parameters:

Compatibility Considerations

In releases before R2009b, the block did not scale the output by Fs. To produce correct results and give the same output as the Signal Processing Toolbox spectrum objects, these five blocks now divide the spectrum by Fs.

To produce the old behavior, place a Gain block in front of these blocks in your model to multiply the signal by sqrt(Fs).

Spectrum Scope Computes Both One-Sided and Two-Sided Spectra

The Spectrum Scope block now computes one-sided ([0... Fs]) and two-sided ((-Fs/2...Fs/2]) spectra in the same way that the Signal Processing Toolbox spectrum objects do. A new Spectrum type parameter on the Scope Properties tab replaces the Frequency range parameter that was on the Axis Properties tab in previous releases. You can set the Spectrum type to compute and display either a One-sided ([0...Fs/2]) or Two-sided ((-Fs/2...Fs/2]) spectrum.

Compatibility Considerations

The changes in the Spectrum Scope block result in the following compatibility considerations.

Spectrum Scope Output Now Scaled by Fs.   To produce correct results and align with the Signal Processing Toolbox spectrum objects, the Spectrum Scope block now scales its output by Fs. Because of this change in scaling, the output of the Spectrum Scope block is different than in previous releases. To help you transition to this behavior, the block updates the Y-axis limits to provide the same view as previous releases. This update occurs the first time you run an R2009a or earlier model in R2009b. This update marks your model changed. Therefore, to preserve the updated Y-axis limits, save your model after running it in R2009b for the first time.

Spectrum type parameter replaces Frequency range parameter.   In previous releases, the Spectrum Scope block computed two-sided spectra over the interval (0…Fs]. It displayed these spectrums over the interval specified by the Frequency range parameter. This release removes the Frequency range parameter from the Axis Properties tab and replaces it with a Spectrum type parameter on the Scope Properties tab. The Spectrum Scope block now computes and displays the spectrum over the interval specified by the Spectrum type parameter, either One-sided ([0...Fs/2]) or Two-sided ((-Fs/2...Fs/2]). The blockset no longer supports the [0...Fs] option for the Frequency range parameter. The following table shows how values of the Frequency range parameter map to the new Spectrum type parameter.

Frequency RangeSpectrum Type
[0...Fs/2]One-sided ([0...Fs/2])
[-Fs/2...Fs/2]Two-sided ((-Fs/2...Fs/2])
[0...Fs]Two-sided ((-Fs/2...Fs/2])

These changes mean that the one-sided spectrum for real signals in R2009b differs from the one-sided spectrum computed by the R2009a Spectrum Scope block. Also, the Spectrum Scope block no longer supports one-sided spectrums for complex inputs. To view the spectrum of a complex input in R2009b, set the Spectrum type parameter to Two-sided ((-Fs/2...Fs/2]).

Y-axis scaling Parameter Removed.   This release removes the Y-axis scaling parameter from the Axis Properties tab. You now set the Y-axis units using the Spectrum units parameter on the Scope Properties tab of the block mask.

Frequency units Parameter Removed.   This release also removes the Frequency units parameter from the Axis Properties tab. The units of the frequency axis are now always expressed in Hertz.

New Data Type Assistant and Ability to Specify Design Minimums and Maximums

Effective in R2009b, a new Data type attributes pane replaces the Fixed-point pane of the following blocks:

The Data type attributes pane provides you with the following new features:

Variable Size Data Support

Limited support for variable size data is now available. The following blocks support variable size data as of this release:

See Working with Variable-Size Signals for more information about variable size data.

Enumerated Data Type Support

Limited support for enumerated data types is now available. The following blocks support enumerated data types as of this release:

See Using Enumerated Data in the Simulink documentation for more information about enumerated data types.

New Pulse Shaping Filter Block

The Filter Design Toolbox™ library now includes the Pulse Shaping Filter block. See the block reference page for more information.

To Audio Device Block Handles Sample-Based Signals Differently

In previous releases, the To Audio Device block treated each sample of sample-based signals as a separate signal. In R2009b, the behavior of the block has changed such that it treats each column of both frame and sample-based inputs as separate channels.

Compatibility Considerations

This change in behavior results in a backward incompatibility for sample-based signals with a length greater than 1. For such input signals in R2009b, the To Audio Device Block produces different results than it did in past releases.

Zero-Latency Filter Structure Removed from CIC Blocks

The Zero-latency decimator and Zero-latency interpolator selections are no longer available. These options were previously available from the Filter structure parameter on the CIC Decimation and CIC Interpolation block masks. Because each block now only implements one filter structure, the Filter structure parameter has also been removed.

Compatibility Considerations

Before running a previously existing model that uses these modes, run the slupdate function. After you do, the block now produces N extra latencies, where N is the number of filter sections.

Empty Initial Conditions Support Removed from Some Blocks

The following blocks no longer support empty ( [ ] ) initial conditions:

Compatibility Considerations

Provide the initial conditions parameter on these blocks with a nonempty value.

  


Related Products & Applications

Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.

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