|
|
|
| R2011b Documentation → Simscape | |
Learn more about Simscape |
|
| Contents | Index |
This table summarizes what's new in Version 3.4 (R2010b):
| 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
The following data logging enhancements have been implemented in this version:
plot and plotxy commands have been added. The plot command lets you plot logged data against time, while the plotxy command plots two sets of data against each other. Also, plot and plotxy methods are now available for simscape.logging.Node and simscape.logging.Series objects. For more information, see the respective reference pages.
New configuration parameter, Decimation, lets you downsample logged data by skipping time steps. For more information, see Data Logging Options.
Simulation data is now logged according to the value specified for the Output options parameter in the Data Import/Export pane of the Configuration Parameters dialog box.
For models that do not use the default value of the Output options parameter in the Data Import/Export pane of the Configuration Parameters dialog box, logged simulation data may change compared to the previous release.
The creation and detection of zero-crossing conditions in Simscape models have been improved.
The Simscape language now implements relational functions in a different way from how relational operators are implemented. Unlike relational operators, these relational functions now do not create Simulink zero-crossing conditions.
For more information about zero crossings in Simscape models, see Creating and Detecting Zero Crossings in Simscape Models in the Simscape User's Guide.
For more information about creating models in the Simscape language, see the Simscape Language Guide and the equations syntax.
If your model generates a Simulink warning or error about zero crossings involving Simscape blocks, the warning or error message now specifies which blocks are generating this zero-crossing diagnostic message.
If you globally disable zero-crossing detection in a Simulink model containing Simscape blocks, and if you are using a variable-step solver without a local solver, you now receive a diagnostic warning or error. You can control which message that you receive in the Simscape pane of the model Configuration Parameters dialog box, through the Zero-crossing control is globally disabled in Simulink drop-down list. This option supports context-sensitive or "What's This?" help, by default accessed through right-clicking the item.
See Harmonizing Simulink and Simscape Solvers in the Simscape User's Guide.
You can now generate C++ code from Simscape models. Encapsulated C++ code generation is not supported.
For more information, see Code Generation and Limitations in the Simscape User's Guide.
The implementation and control of matrix linear algebra in the Solver Configuration block have been improved and simplified. Whether you choose the sparse solver or the full solver, your linear algebra choice is now implemented in both model simulation and code generated from the model.
For more information, see the Solver Configuration block reference page.
In Simscape Language, the name of the block built from a component file generally corresponds to the component file name. You can provide a more descriptive name for the block by adding a comment line immediately following the component declaration. This comment line is called the descriptor. For more information, see How to Customize the Block Name.
If you use subclassing, the subclass inherits all of the members (parameters, variables, nodes, inputs and outputs) from the base class (for more information, see Subclassing and Inheritance). In previous releases, descriptor was one of the inherited properties. That is, if you had a subclass component without a descriptor, the resulting block name was derived from the descriptor of the base class, instead of the component file name. This could create issues with library building if both the subclass component and the base class component were in the same sublibrary.
Starting with this release, descriptor is no longer inherited from the base class. In other words, if a component file does not contain a comment line immediately following the component declaration, the component name is always used for the block name.
For existing subclass components, if the component does not have a descriptor line, upon rebuilding the library the block name will change compared to the previous release. To preserve the old name, add a descriptor line to the subclass component file.
The Model Simulation chapter has been expanded and improved with revised and new sections, including:
More information about real-time simulation is available in Simulating with Hardware in the Loop, in the Motion, Control, and Real-Time Simulation chapter of the SimMechanics™ User's Guide.
The following demo has been added in Version 3.4:
Demo Name | Description |
Electrical Transformer | Presents a view inside a transformer core using the electromagnetic blocks from the Magnetic block library. |
 | Version 3.5 (R2011a) Simscape Software | Version 3.3 (R2010a) Simscape Software |  |
Learn more about Simulink through this collection of videos, articles, technical literature and the Getting Started with Simulink Guide.
| © 1984-2012- The MathWorks, Inc. - Site Help - Patents - Trademarks - Privacy Policy - Preventing Piracy - RSS |
