|
|
|
|
|
|
|
|
|
|
|
|
| Model Advisor Report - zero.mdl | |
| Simulink version: 8.5 | Model version: 1.2 |
| System: zero | Current run: 10-Aug-2016 20:48:45 |
| Treat as Referenced Model: off | |
| Pass | Fail | Warning | Not Run | Total |
|---|---|---|---|---|
11
|
0
|
6
|
|
25 |
Upgrade Advisor
Check model for block upgrade issues
The Upgrade Advisor has checked blocks for issues in using them with this version of Simulink. See doc('slupdate') for more information.
S-function update status for the Level 2 API (see Writing S-Functions):
Blocks recommended for update, grouped by update reason:
Update reason — Simulink has encountered a problem while updating 'zero/V0'. Verify the settings and functionality of this block.:
zero/V0Update reason — Simulink has encountered a problem while updating 'zero/Zero Sequence Source/va'. Verify the settings and functionality of this block.:
zero/Zero Sequence Source/vaUpdate reason — Simulink has encountered a problem while updating 'zero/Zero Sequence Source/vb'. Verify the settings and functionality of this block.:
zero/Zero Sequence Source/vbUpdate reason — Simulink has encountered a problem while updating 'zero/Zero Sequence Source/vc'. Verify the settings and functionality of this block.:
zero/Zero Sequence Source/vcUpdate reason — The following subsystem output ports specify an initial output value. Since the simulation is not using this InitialOutput parameter, the value is meaningless. To improve the clarity of your design, use set_param to set the initial output to empty []. For more information, type "help set_param" at the MATLAB command line.:
zero/Subsystem/0zero/Subsystem/1zero/Subsystem/2zero/Synchronous Machine Measurements1/is_abc
Check usage of function-call connections
Check 'Invalid function-call connection' setting
Verify that the Invalid function-call connection diagnostic is set to error.
Passed
Diagnostics > Connectivity > Invalid function-call connection is set to error.
Recommended Action
_________________________________________________________________________________________
Check 'Context-dependent inputs' setting
Verify that the Context-dependent inputs diagnostic is set to Enable all as errors.
Warning
Diagnostics > Connectivity > Context-dependent inputs is set to Use local settings. This might lead to non-deterministic model execution.
Recommended Action
Set Diagnostics > Connectivity > Context-dependent inputs to Enable all as errors.
Check for calls to slDataTypeAndScale()
Search for blocks that have data type parameters specified by using slDataTypeAndScale().
Required Replacement Cases
Identify calls to slDataTypeAndScale() that are no longer supported and thus should be replaced. Such calls always can be automatically replaced.
See Also
Recommended Replacement Cases
Identify unnecessary calls to slDataTypeAndScale() that the model advisor can automatically replace.
See Also
Manual Inspection Cases
Identify calls to slDataTypeAndScale() that might be unnecessary.
See Also
Identify masked blocks that specify tabs in mask dialog using MaskTabNames parameter
Identify masked blocks that use the MaskTabNames parameter to programmatically create tabs in the mask dialog. Since R2013b, dialog controls are used to group parameters in a tab on the mask dialog.
Passed
No masked block found that uses MaskTabNames to create tabs in the mask dialog.
Check that the model is saved in SLX format
Check that the model is saved in SLX format.
Warning
Model zero is saved in an MDL file: D:\Office\MERITSoft_2016_2015a\zero.mdl
Recommended Action
Save model zero in a file with extension ".slx". The button below will save it in file:
D:\Office\MERITSoft_2016_2015a\zero.slx.
To choose a different name or location, use the "Save As..." menu item in the Simulink Editor.
Check signal logging save format
Check signal logging save format. The signal logging save format 'ModelDataLogs' will be removed in a future release. To take advantage of new functionality, update any models using 'ModelDataLogs' format to use 'Dataset' format. For guidelines about changes that you might need to make to models, callbacks, scripts, or tests, see Migrate from ModelDataLogs to Dataset Format.
Warning
One or more configsets attached to this model use 'ModelDataLogs' format for signal logging and requires updating.
Recommended Action
To take advantage of new functionality, update any models using 'ModelDataLogs' format to use 'Dataset' format.
Identify configurable subsystem blocks for converting to variant subsystem blocks
Identify configurable subsystem blocks at the model or subsystem level. You can convert these blocks to variant subsystems.
Passed
No configurable subsystem blocks found.
Check and update masked blocks in library to use promoted parameters
Searches libraries created before R2011b for masked blocks that should be updated to use promoted parameters. Since R2011b, if a block parameter is not promoted, its value in the linked block is locked to its value in the library block. This check excludes blocks of type Subsystem, Model reference, S-Function and M-S-Function.
Passed
This check only applies to libraries created before R2011b.
Check and update mask image display commands with unnecessary imread() function calls
Identify masks using an image display commands with unnecessary calls to imread(). Since 2013a, a performance and memory optimization is available for mask images specified via image path instead of RGB triple matrix.
Passed
No masked block found with unnecessary imread() calls in image display commands.
Check get_param calls for block CompiledSampleTime
Check model for Aerospace Blockset legacy 3DoF or 6DoF blocks
Check model for Aerospace Blockset legacy 3DoF or 6DoF blocks
Your model does not contain legacy 3DoF or 6DoF blocks.
_________________________________________________________________________________________
Check model for Aerospace Blockset blocks with unsupported versions of FlightGear
Check model for Aerospace Blockset blocks with unsupported versions of FlightGear
Your model does not contain blocks that specify a FlightGear version.
_________________________________________________________________________________________
Check and update model to use toolchain approach to build generated code
Warning
Model is not configured to use the toolchain approach.
Recommended Action
Model cannot be automatically upgraded to use the toolchain approach.
For more information about updating the model so it can use the toolchain approach to build the generated code, see "Upgrading Model to Use Toolchain Approach".
Check and update embedded target model to use ert.tlc system target file
Check and update embedded target model to use ert.tlc system target file. Only the models whose system target file is set to idelink_ert.tlc or idelink_grt.tlc and whose board matches one of the supported target hardware options can be updated. If the model can be updated, the model parameters will be converted to support use of ert.tlc system target file.
Passed
This model cannot be updated to use ert.tlc system target file because its system target file is not set to idelink_ert.tlc nor to idelink_grt.tlc.
Check Model History properties
Check models for edited Model History property values
Check that parameters in the Model Properties dialog History pane use the default tags In the MDL file format you can configure some model properties to make use of source control tool keyword substitution. If you save your model in SLX format, source control tools cannot perform keyword substitution. Any information in the model file from such keyword substitution is cached when you first save the MDL file as SLX, and is never updated again. The Model Properties History pane and any Model Info blocks in your model show stale information from then on.
Passed
This model uses the default value for property ModifiedByFormat.
Passed
This model uses the default value for property ModifiedDateFormat.
Passed
This model uses the default value for property ModelVersionFormat.
Analyze model hierarchy and continue upgrade sequence
The Upgrade Advisor guides you through the following sequence for upgrading your models:
The current results guide you through upgrading your entire hierarchy from leaf to root model, running the Upgrade Advisor on each model in turn. Click here to clear any hierarchy results and run this check on the current model only.
Warning
More checks to run. Click "Continue Upgrade Sequence" to run the next checks.
Recommended Action
Click "Continue Upgrade Sequence" to open the next model in this upgrade session.