Filter checks

Passed  
Failed  
Warning  
Not Run  
   

Navigation

Upgrade Advisor

View

Scroll to top
Show check details
Model Advisor Report - realtime_pacer_example.mdl
Simulink version: 8.4 Model version: 1.29
System: realtime_pacer_example Current run: 16-Nov-2016 13:01:54

Run Summary
Pass Fail Warning Not Run Total
   14    0    4    6 24


Upgrade Advisor


  Check model for block upgrade issues

Passed


  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.


  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 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

  • slRemoveDataTypeAndScale() automatic replacement cases
Passed
No calls to slDataTypeAndScale() require replacement.
_________________________________________________________________________________________

Recommended Replacement Cases
Identify unnecessary calls to slDataTypeAndScale() that the model advisor can automatically replace.

See Also

  • slRemoveDataTypeAndScale() automatic replacement cases
Passed
No calls to slDataTypeAndScale() can be automatically replaced.
_________________________________________________________________________________________

Manual Inspection Cases
Identify calls to slDataTypeAndScale() that might be unnecessary.

See Also

  • slRemoveDataTypeAndScale() manual inspection cases
Passed
No calls to slDataTypeAndScale() require manual inspection.


  Check that the model is saved in SLX format

Check that the model is saved in SLX format.

Warning
Model realtime_pacer_example is saved in an MDL file: /Users/Berge/Documents/MATLAB/RealTime_Pacer/RealTime_Pacer/realtime_pacer_example.mdl

Recommended Action
Save model realtime_pacer_example in a file with extension ".slx". The button below will save it in file:
  /Users/Berge/Documents/MATLAB/RealTime_Pacer/RealTime_Pacer/realtime_pacer_example.slx.
To choose a different name or location, use the "Save As..." menu item in the Simulink Editor.


  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.


  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 rapid accelerator signal logging

You are not simulating in Rapid Accelerator mode.


  Check get_param calls for block CompiledSampleTime

Found no MATLAB files that call get_param('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

Passed
Model is configured to use the 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 and local libraries for legacy SimEvents blocks

Check model and its associated libraries for blocks from a version of SimEvents prior to 4.0 (R2011b).

Passed
All SimEvents blocks in this model are up-to-date.


  Check model for block upgrade issues requiring compile time information

Not Run


  Check consistency of initialization parameters for Outport and Merge blocks

Not Run


  Check Unit Delay and Zero-Order Hold blocks for rate transition

Not Run


  Check for implicit event duplication caused by SimEvents blocks

Not Run


  Check for Mux blocks used to create bus signals

Not Run


  Check for root outports with constant sample time

Not Run


  Analyze model hierarchy and continue upgrade sequence

The Upgrade Advisor guides you through the following sequence for upgrading your models:

  1. The Upgrade Advisor opens each model and library in turn, from leaf to root, and selects the non-compile checks. Run the checks, take any advised actions, then click Continue Upgrade Sequence to open the next model and continue.
  2. When you reach the root end of the hierarchy, the Upgrade Advisor then opens each model again in the same order (but not libraries) and selects only the checks that require a model compile (marked with ^). Run the checks, take any advised actions, then click Continue Upgrade Sequence to open the next model. Continue until you reach the end of the hierarchy and this check passes.
If there are no child models, you still need to continue the check sequence until you have run both non-compile and compile checks (marked with ^).

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
Child models found. Click "Continue Upgrade Sequence" to run the next checks.


Recommended Action
Click "Continue Upgrade Sequence" to refresh the Upgrade Advisor with compile checks selected (marked with ^).

  • realtime_pacer_example (current)
  • realtime_pacer_lib (next)
  • ^realtime_pacer_example