Store 
| Products & Services | Solutions | Academia | Support | User Community | Company |
 |
Download Product Updates | | |  |
Get Pricing | | | |
Trial Software |
| Documentation → Simulink |
| Products & Services | Solutions | Academia | Support | User Community | Company |
|
Download Product Updates | | | |
Get Pricing | | | |
Trial Software |
| Documentation → Simulink |
| Contents | Index |
| Learn more about Simulink |
This table summarizes what's new in V6.3 (R14SP3):
| New Features and Changes | Version Compatibility Considerations | Fixed Bugs and Known Problems | Related Documentation at Web Site |
|---|---|---|---|
| Yes Details below | Yes—Details labeled as Compatibility Considerations, below. See also Summary. | Bug
Reports at Web site | No |
New features and changes introduced in this version are organized by these topics:
Fixed-Point Functions No Longer Supported for Use in Signal Objects
Parameter Object Expressions No Longer Supported in Dialog Boxes
This topic contains new features and changes for model reference:
Function-Call Models. This release allows you to use a block capable of emitting a function-call signal, such as a Function-Call Generator or a custom S-function, in one model to control execution of another model during the current time step. See Defining Function-Call Models for more information.
Using Noninlined S-Functions in Referenced Models. This release adds limited support for use of noninlined S-functions in models referenced by other models. For example, you can simulate a model that references models containing noninlined S-functions. However, you cannot use Real-Time Workshop software to generate a standalone executable (Real-Time Workshop target) for the model. See Simulink Model Referencing Limitations in the Simulink documentation for information on other limitations.
Referenced Models Without Root I/O Can Inherit Sample Times. Previous releases of Simulink software do not allow referenced models without root-level input or output ports to inherit their sample time. This release removes this restriction.
Referenced Models Can Use Variable Step Solvers. Previous releases of Simulink software do not allow models to reference models that require variable-step solvers. This release removes this restriction.
Model Dependency Graphs Accessible from the Tools Menu. This release adds a Model Reference Dependency Graph item to the Model Editor's Tools menu. The item displays a graph of the models referenced by the model displayed in the Model Editor. You can open any model in the dependency graph by clicking its node. See Viewing a Model Reference Hierarchy for more information.
Command That Converts Atomic Subsystems to Model References. This release introduces a MATLAB command that converts an atomic subsystem to a model reference. See Simulink.SubSystem.convertToModelReference for more information.
Model Reference Demos. This release has the following model reference demo changes:
Model reference demo names are now prepended with sldemo_. For example, the demo mdlref_basic.mdl is now sldemo_mdlref_basic.mdl.
You can no longer use the mdlrefdemos command from the MATLAB command prompt to access model reference demos. Instead, you can navigate to the Simulink demos tab either though the Help browser, or by typing demos at the command prompt, then navigating to the Simulink demos category and browsing the demos.
This release replaces the Variable Transport Delay block of previous releases with two new blocks. The Variable Transport Delay block of previous releases implemented a variable time delay behavior, which is now implemented by the Variable Time Delay block introduced in this release. This release changes the behavior of the Variable Transport Delay block to model variable transport delay behavior, e.g., the behavior of a fluid flowing through a pipe.
This release adds a sampled level trigger option for causing the Discrete-Time Integrator to reset. The new reset trigger is more efficient than the level reset option, but may introduce a discontinuity when integration resumes.
Note In Simulink 6.2 and 6.2.1, the level reset option behaves like the sampled level option in this release. This release restores the level reset option to its original behavior. |
This release includes the following enhancements to the signal latching capabilities of the Inport block.
Label Clarified for Triggered Subsystem Latch Option. The dialog box for an Inport block contains a check box to latch the signal connected to the system via the port. This check box applies only to triggered subsystems and hence is enabled only when the Inport block resides in a triggered subsystem. In this release, the label for the check box that selects this option has changed from Latch (buffer) input to Latch input by delaying outside signal. This change is intended to make it clear what the option does, i.e., cause the subsystem to see the input signal's value at the previous time step when the subsystem executes at the current time step (equivalent to inserting a Memory block at the input outside the subsystem). The Inport block's icon displays <Lo> to indicate that this option is selected.
Latch Option Added for Function-Call Subsystems. This release adds a check box labeled Latch input by copying inside signal to the Inport block's dialog box. This option applies only to function-call subsystems and hence is enabled only if the Inport block resides in a function-call subsystem. Selecting this option causes Simulink software to copy the signal output by the block into a buffer before executing the contents of the subsystem and to use this copy as the block's output during execution of the subsystem. This ensures that the subsystem's inputs, including those generated by the subsystem's context, will not change during execution of the subsystem. The Inport block's icon displays <Li> to indicate that this option is selected.
In previous releases, the dialog box for a function-call subsystem contains a check box labeled Warn if function-call inputs arise inside called context. This release changes the label to Warn if function-call inputs are context-specific. This change is intended to indicate more clearly the warning's purpose, i.e., to alert you that some or all of the function-call inputs come from the function-call subsystem's context and hence could change while the function-call subsystem is executing.
Note In this release, you can avoid this function-call inputs problem by selecting the Latch input by copying inside signal option on the subsystem's Inport blocks (see Latch Option Added for Function-Call Subsystems). |
This release introduces the following enhancements to model annotations:
Annotation properties dialog box (see Annotations Properties Dialog Box)
Annotation callback functions (see Annotation Callback Functions)
Annotation application programming interface (see Annotations API)
This release allows you to add custom signal viewers and generators so that you can manage them in the Signal & Scope Manager. See Adding Custom Viewers and Generators for further details.
This release adds an Evaluate Property Values During Search option to the Model Explorer. This option applies only for searches by property value. If enabled, the option causes the Model Explorer to evaluate the value of each property as a MATLAB expression and compare the result to the search value. If disabled (the default), the Model Explorer compares the unevaluated property value to the search value.
Previous releases allow you to use signal objects to check signal property values assigned by signal sources. This release allows you, in addition, to use signal objects to assign values to properties not set by signal sources. See Simulink.Signal for more information.
This release introduces the following bus utility functions:
In this release, the Embedded MATLAB Function block supports many Fixed-Point Toolbox functions. This allows you to generate code from models that contain fixed-point M functions. See Working with the Fixed-Point Embedded MATLAB Subset in the Fixed-Point Toolbox documentation for more information.
The Embedded MATLAB Editor has a new tool, the Ports and Data Manager. This tool helps you manage your block inputs, outputs, and parameters. The Ports and Data Manager uses the same Model Explorer dialogs for manipulating data, but restricts the view to the block you are working on. You can still access the Model Explorer via a menu item to get the same functionality as in previous releases.
Embedded MATLAB Function blocks now supports input triggers and function-call outputs. See Ports and Data Manager for more information.
This release adds find options to the Data Object Wizard. The options enable you to restrict the search for model data to specific kinds of objects. See Data Object Wizard for more information.
This release can display logged signal data in the MATLAB Times Series Tools viewer on demand or whenever a simulation ends or you pause a simulation. See "Viewing Logged Signal Data" in the Simulink documentation for more information.
In this release, root-level Inport blocks can import data from time-series (see Simulink.Timeseries) and time-series array (see Simulink.TSArray) objects residing in the MATLAB workspace. See Importing Data from a Workspace for more information. From Workspace blocks can also import time-series objects. The ability to import time-series objects allows you to use data logged from one simulation as input to another simulation.
Previous releases of Simulink software generate an error if you try to use a variable-step solver to solve a model that contains Rate Transition blocks. This release allows you to use variable-step as well as fixed-step solvers to simulate a model. Note that you cannot generate code from a model that uses a variable-step solver. However, you may find it advantageous, in some cases, to use a variable-step solver to test aspects of the model not directly related to code generation. This enhancement allows you to switch back and forth between the two types of solver without having to remove and reinsert Rate Transition blocks.
This release adds the following simulation diagnostics:
This release changes the name of the Data Integrity diagnostics pane of the Configuration Parameters dialog box to the Data Validity pane. It also reorganizes the pane into groups of related diagnostics. See Diagnostics Pane: Data Validity for more information.
When you enable the Ensure sample time independent solver constraint (see Periodic sample time constraint for more information), Simulink software generates several error messages if the model is not sample-time independent. In previous releases, these messages were not specific enough for you to determine why a model failed to be sample-time independent. In this release, the messages point to the specific block, signal object, or model parameter that causes the model not to be sample-time independent.
This release adds the following model viewing enhancements:
A command history for pan and zoom commands (see Viewing Command History)
Keyboard shortcuts for panning model views (see Model Viewing Shortcuts)
This release allows you to use M-code to perform the following customizations of the standard Simulink user interface:
Add custom commands to the Model Editor's Tools menu (see Disabling and Hiding Dialog Box Controls)
Disable, or hide widgets on Simulink dialog boxes (see Disabling and Hiding Dialog Box Controls)
In this release, the extension for files created by the MATLAB mex command on Windows systems has changed from dll to mexw32 or mexw64.
If you have implemented any S-functions in C, Ada, or Fortran or have models that reference other models, you should
Recreate any mexopts.bat files (other than the one in your MATLAB preferences directory) that you use to build S-functions and model reference simulation targets
Rebuild your S-functions
Previous releases allowed you to use fixed-point data type functions, such as sfix, to specify the value of the DataType property of a Simulink.Signal object. This release allows you to use only builtin data types and Simulink.NumericType objects to specify the data types of Simulink.Signal objects. See the Simulink.Signal documentation for more information.
Previous releases allow you to specify a Simulink.Parameter object as the value of a block parameter by entering an expression that returns a parameter object in the parameter's value field in the block's parameter dialog box. In this release, you must enter the name of a variable that references the object in the MATLAB or model workspace.
In this release, the extension for files created by the MATLAB mex command has changed from dll to mexw32 (and mexw64).
If you use a mexopts.bat file other than the one created by the mex command in your MATLAB preferences directory to build Accelerator targets, you should recreate the file from the mexopts.bat template that comes with this release.
 | Version 6.4 (R2006a) Simulink Software | Version 6.2 (R14SP2) Simulink Software |  |
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 |
