| Products & Services | Solutions | Academia | Support | User Community | Company |
| Download Product Updates | | | Get Pricing | | | Trial Software |
| Documentation → Communications Toolbox |
| Contents | Index |
| Learn more about Communications Toolbox |
This table summarizes what's new in Version 4.4 (R2009b):
| 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. | Printable Release Notes: PDF Current product documentation |
New features and changes introduced in this version are:
Adjacent channel power ratio (ACPR) calculations characterize spectral regrowth, caused by amplifier nonlinearity, in a communications system component, such as a modulator or an analog front end. These calculations determine the likelihood that a given system causes interference with an adjacent channel.
Many present transmission standards, such as IS-95, CDMA, WCDMA, 802.11, and Bluetooth, contain a definition for ACPR measurements. Most standards define ACPR measurements as the ratio of the average power in the main channel and any adjacent channels. The specific offset frequencies and measurement bandwidths (BWs) you use depends on the specific industry standard you are using. For instance, measurements of CDMA amplifiers involve two offsets (from the carrier frequency) of 885 kHz and 1.98 MHz, and a measurement BW of 30 KHz.
For more information, see the commmeasure.ACPR help page or Overview of ACPR Measurement Tutorial in the Communications Toolbox User's Guide.
commmeasure.EVM now supports three normalization options. You can normalize measurements according to the average power of the reference signal, average constellation power, or peak constellation power. This enhancement provides you with the flexibility to use EVM normalization with the different definitions of EVM measurements that appear in various industry standards. Typically, the variations in these standards pertain to the normalization option.
For more information, see the commmeasure.EVM help page.
Communications Toolbox contains a command-line approach for simulating error rate in a communications system. The error rate test console runs simulation on a user-defined communications system to obtain error rate analysis.
If you also have a user license for the Parallel Computing Toolbox software, the error rate test console reduces simulation time by automatically distributing the work load among the number of available processors.
For more information, see the commtest.ErrorRate help page, Running Simulations Using the Error Rate Test Console in the Communications Toolbox Getting Started Guide, or Error Rate Test Console in the Communications Toolbox User's Guide.
rayleighchan, ricianchan, and mimochan now support the Parallel Computing Toolbox™ software. Using the default MATLAB random stream algorithm, channel objects can generate independent channels on different workers. Since rayleighchan, ricianchan, and mimochan can generate independent channels on each worker, you can use the Parallel Computing Toolbox software to run simulations on multiple workers, reducing simulation time.
rayleighchan, ricianchan, and mimochan now use the default MATLAB random stream. Software versions before the 2009b release use the V5 RANDN (Ziggurat) algorithm to generate channel path gains. The default random stream is more robust for use with Parallel Computing Toolbox software and can generate channel path gain values that are the statistical equivalent to the V5 RANDN (Ziggurat) algorithm.
rayleighchan, ricianchan, and mimochan do not support reset(h,s), where h represents a channel and s represents the new channel state. To obtain the random number generation functionality before the 2009b release, including reset(h,s) support, use legacychannelsim. You can not use channel objects with Parallel Computing Toolbox software to run simulations in legacy mode.
The following demos are new or updated for this release:
Two new demos show how to simulate 3GPP EGPRS2 and IEEE 802.11b communications systems using the Error Rate Test Console. These demos can be run on multiple workers if you have a user license for the Parallel Computing Toolbox software.
The Raised Cosine demo now uses the filter design object fdesign.pulseshaping.
| Function or Function Element Name | What Happens When you use the Function or Element? | Use This Instead | Compatibility Considerations |
|---|---|---|---|
| seqgen.pn | Warns | commsrc.pn | Use commscrc.pn to create a PN sequence generator object. |
| rcosfir | Still runs | fdesign.pulseshaping | Use fdesign.pulseshaping to design raised cosine finite (FIR) impulse response filter |
| rcosflt | Still runs | fdesign.pulseshaping | Use fdesign.pulseshaping to design a filter input signal using raised cosine filter. Does not support IIR. |
| rcosiir | Still runs | N\A | Do not use. |
| rcosine | Still runs | fdesign.pulseshaping | Use fdesign.pulseshaping to design a design a raised cosine filter. Does not support IIR. |
| randint | Still runs | randi | Use Randi to generate matrix of uniformly distributed random integers |
| reset(h,s) for rayleighchan | Errors | N\A | Do not use. See legacychannelsim |
| reset(h,s) for ricianchan | Errors | N\A | Do not use. See legacychannelsim |
| reset(h,s) for mimochan | Errors | N\A | Do not use. See legacychannelsim |
| state parameter for awgn | Still runs | s, which is a random stream handle | None. |
| state parameter for wgn | Still runs | s, which is a random stream handle | None. |
| state parameter for bsc | Still runs | s, which is a random stream handle | None. |
| state parameter for randerr | Still runs | s, which is a random stream handle | None. |
| state parameter for randsrc | Still runs | s, which is a random stream handle | None. |
![]() | Version 4.5 (R2010a) Communications Toolbox Software | Version 4.3 (R2009a) Communications Toolbox Software | ![]() |

Learn how to apply early verification to your development process through these technical resources.
How much time do you spend on testing to ensure implementation meets system-level requirements?
| © 1984-2010- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |