What's New in MapleSim 6.1
MapleSim 6.1 provides improved performance, important additions to the API, connectivity enhancements, and more.
Faster Simulations
API Enhancements
Exported Code Improvements
Transparency Option for Multibody Geometry Components
Modelica Support
Connectivity Improvements
The Power of Maple 17
MapleSim 6.1 produces simulations faster than ever before due to a variety of improvements to the simulation engine. In particular:
For all models, the model pre-processing phase is more efficient, so your simulation results appear sooner
Substantial improvements have been made in creating the 3-D visualizations of large models, so simulation animations appear much more quickly than before
The MapleSim Application Programming Interface (API) is a collection of procedures for manipulating, simulating, and analyzing a MapleSim model in a Maple standard worksheet. In MapleSim 6.1, this API has been extended to provide even more flexibility for model creation and analysis.
Programmatic Analysis Tools
New commands make it easier to analyze the parameters in your model programmatically. These commands can take advantage of the full processing power of your computer, automatically detecting and using all available processor cores to perform your computations in parallel whenever possible. You can even specify how many cores you wish to involve, keeping the remaining cores available for other tasks. As a result, you can perform large numbers of computations rapidly and get your results faster.
MonteCarlo: Perform a Monte Carlo analysis of your model by simulating it repeatedly. With each simulation, the parameters you specify are varied randomly.
ParameterSweep: Perform a parameter sweep of your model by simulating it repeatedly. You provide the parameter values to sweep through as either a range or a list of values.
For more information, see MapleSim[Analysis][MonteCarlo] and MapleSim[Analysis][ParameterSweep] .
Creating Custom Components
With the updated API, you can easily create custom components programmatically.
Extract your defining equations from any Maple document, not just the Custom Component Template, or define your model from Modelica source code
Take advantage of extra flexibility to define new port types for your component
Send the component directly to MapleSim for inclusion in your next model
New commands in the API include:
MapleToModelica: Create a Modelica model from either a set of Maple equations, a DynamicSystems model, or Modelica source. The Modelica model can then be coupled directly to a MapleSim model as an embedded component using the SetComponent command.
CreateModel: Create a MapleSim model from a Modelica file or Modelica code. The model can optionally be saved to a MapleSim model (.msim) file.
SetComponent: Attach a Modelica model (defined in Modelica source code) to a linked MapleSim model as an embedded component. The Modelica source code can be generated using the MapleToModelica command.
For more information, see MapleSim[Tools][MapleToModelica], MapleSim[LinkModel][SetComponent] , MapleSim[CreateModel], and DynamicSystems.
Preferred variables
MapleSim optimizes the equations of a MapleSim ModelObject by removing redundant equations and variables from the system of equations. Running the GetEquations command on the ModelObject returns this system of equations so they can be examined in Maple.
In previous versions of MapleSim, you had no control over what variables were eliminated during the optimization process. In MapleSim 6.1, you can use the new prefvars option in GetEquations to specify a list of preferred variables. The equation simplification process keeps these variables in the system of equations whenever possible.
For more information, see MapleSim[LinkModel][GetEquations].
Other API Improvements
Other improvements to the API include commands to query and manipulate models.
LibraryVersion: Get information about the version of Modelica used in MapleSim.
DeleteAttachment: Delete a file attached to a MapleSim ModelObject.
ListSubsystems: List the subsystems of a MapleSim ModelObject.
For more information, see MapleSim[Tools][LibraryVersion], MapleSim[LinkModel][DeleteAttachment], and MapleSim[LinkModel][ListSubsystems].
Initialization for exported code is now more robust and includes both discrete and continuous variable iteration loops to ensure that the initial conditions adjust for changes in both the specified parameters and initial conditions. Other changes include the ability to specify a boolean or integer parameter, in addition to continuous parameters.
The geometry components found in the Visualization section of the Multibody palette have a new Transparent option, which allows you to make certain components transparent so you can see the components underneath. For example, you can add transparent car body to your engine model to provide additional visual context.
To access the option, select a geometry component, and then click the Inspector tab. When Transparent is selected, the corresponding object is rendered transparent in the 3D Playback view.
MapleSim 6.1 continues to enhance its support for Modelica. In addition to the new API commands that support the creation of custom components using Modelica code, Maple 6.1 also offers improved support of Modelica functions and algorithms.
New and improved connectivity add-ons to MapleSim 6.1 provide even more ways to integrate MapleSim into your toolchain.
MapleSim Connector for FMI
The MapleSim Connector for FMI adds support for v2.0 Beta 4 of the FMI standard, the most current definition available at this time. When you select this option from the FMU Generation template, you can also now choose to export your model for co-simulation using fixed-step solvers as well as model exchange.
Maplesoft will extend its support to meet the final version 2.0 standard once the definition is released.
Connectivity to Simulink®, NI LabVIEW™, and NI VeriStand™ Software
New export options in the MapleSim Connector, which connects to Simulink®, and the MapleSim Connector for LabVIEW™ and NI VeriStand™ Software allow you to export your MapleSim model as a discrete model (that is, a model without any continuous states), even if the model itself is continuous or includes continuous elements. With this option, the solver is included in the export, so the exported model can be simulated without any calls to external solvers. In some situations, the result is a much faster simulation in the target system, especially in the cases where the original model included both discrete and continuous elements. This approach is also useful for embedded controller code.
When this option is selected you can choose from one of five embedded solvers (Euler, RK2, RK3, RK4, and Implicit Euler) and specify the timestep for the discretization.
New MapleSim Connector for JMAG-RT
The MapleSim Connector for JMAG-RT allows you to use motor files exported from JMAG®-RT directly in your MapleSim simulations. The motor files are attached to the MapleSim model and then used to configure the new JMAG_RT component.
MapleSim 6.1 lets you take advantage of all the enhancements of Maple 17, including a wide variety of improvements in both the computation engine and interface. Below are just a few of the additions you may find useful. See New in Maple 17 for a more complete description of what Maple 17 offers.
Advanced code editor
The new code editor in Maple 17 has many features that make it easier to write, read, and debug Maple code. The new code editor is available in the startup code editor, code edit regions, and embedded components. Features include:
Syntax Highlighting
Bracket Matching
Quote Matching
Automatic Indentation
Command Completion
Error Checking
Import/Export
For more information, see Advanced Code Editor, Code Editor, Embedded Components, and Startup Code Editor.
New package for signal processing
Maple 17 offers new signal processing tools for analyzing and manipulating data in the frequency and time domains. The new package can be used for diverse applications such as creating a speech spectrogram, removing noise from polluted signals, and identifying the periodicity of data.
For more information, see New in Maple 17: Signal Processing.
Updates to control design and statistics tools
Control Design
Control design tools in Maple have been enhanced to become even more flexible. Improvements to the DynamicSystems package for control design include:
The FrequencyResponse command handles differential equations with input derivatives.
All models now accept linear, non-differential systems.
A new frequencies option for all frequency-based plots enables you to specify the precise frequencies at which expressions are evaluated.
The Grammians command has been extended to work with discrete systems.
For more information, see New in Maple 17: DynamicSystems.
New Statistics commands
Two new commands have been added to the Statistics package: PredictiveLeastSquares and RousseeuwCrouxSn.
PredictiveLeastSquares: Fit a linear model to data, especially when the number of variables is of the same order of magnitude or less than the number of observations.
RousseeuwCrouxSn: A measure of dispersion of a data set is a statistic that describes the variability or spread of the data set. This command finds the Rousseeuw and Croux measure of dispersion, Sn.
For more information, see New in Maple 17: Statistics, Statistics, Statistics[PredictiveLeastSquares], and Statistics[RousseeuwCrouxSn].
Ease of use enhancements
The following list gives a brief description of some of the enhancements in Maple 17 that make it easier to use.
Autocomplete in 2-D Math: Automatic command completion is now available while entering commands in standard mathematical notation. Once you have typed enough of a command name, a yellow tooltip appears with a suggested match for your command. Press Tab or Return/Enter to insert the suggestion.
Enhanced search and replace: You can now search for names that appear inside mathematical expressions.
Improved subscript handling: Subscript handling is more intuitive. In Maple 17, it is easier to create a variable that has a subscript as part of the variable name (a literal subscript) as opposed to an index reference to an element in an array or vector (an indexed subscript). To create a literal subscript, type the base name followed by two underscores, and then enter the subscript.
Using reserved names: Previously protected variable names, such as I and D, can now be used in your own calculations, even at the top level.
For more information, see Ease of Use Enhancements, Improved Subscript Handling, and Local Names.
Simulink is a registered trademark of The MathWorks, Inc. NI LabVIEW, NI VeriStand, and National Instruments are trademarks of National Instruments. JMAG is a registered trademark by JSOL Corp. in the US and other countries. Modelica is a registered trademark of the Modelica Association.
Download Help Document
