Model Advisor Report for 'state_machine/StateMachine'

Pass	Fail	Warning	Not Run	Total
115	0	67	101	283

Check optimization settings

You should turn on the following optimization(s):

	Inline parameters
	Remove code from floating-point to integer conversions that wraps out-of-range values
	Inline invariant signals
	Remove root level I/O zero initialization
	Remove internal data zero initialization
	Ignore test point signals
	Pass reusable subsystem outputs as individual arguments

Identify blocks using one-based indexing

Check the model for blocks configured for one-based indexing

Passed
All blocks in the model use zero-based indexing.
_________________________________________________________________________________________

Check for blocks requiring one-based indexing

Warning
The following blocks require one-based indexing.

state_machine/StateMachine/Chart

Recommended Action
Evaluate the blocks to determine if one-based indexing is used. Consider replacing the blocks with Simulink basic blocks

Identify questionable software environment specifications

You selected support for non-finite numbers. You should deselect this option for production code generation.

Identify lookup table blocks that generate expensive out-of-range checking code

These settings can lead to inefficient code generation when inputs always fall within the range of valid breakpoint values for lookup table blocks, including Lookup Table blocks, Prelookup blocks and Interpolation blocks.

Passed
The lookup table blocks have been configured to generate range-checking free code.

Identify questionable code instrumentation (data I/O)

Passed

Check output types of logic blocks

Identify logic blocks that are outputting non-Boolean data types.

Passed
There are no logic blocks in the model or subsystem.

Identify blocks that generate expensive rounding code

Not Run

Identify questionable fixed-point operations

Not Run

Identify blocks that generate expensive fixed-point and saturation code

Not Run

Identify time-varying source blocks interfering with frequency response estimation

Not Run

Check Data Store Memory blocks for multitasking, strong typing, and shadowing issues

Duplicate data store names checking is not set to 'error'. Duplicate usage of data store names can lead to unintended shadowing of data stores of higher model scope. Consider changing this setting to 'error' on the Data Validity page of the Configuration Parameters dialog box.

Check data store block sample times for modeling errors

Not Run

Check for potential ordering issues involving data store access

Not Run

Identify disabled library links

Passed

Identify parameterized library links

Passed

Identify unresolved library links

Passed

Identify model reference variants and variant subsystems that override variant choice

Identify model or subsystem for model reference variants and variant subsystems that specify variant choice using the override option instead of using the active variant control.

Passed
No model reference variants or variant subsystems found which override their choice.

Check for model reference configuration mismatch

Not Run

Check for parameter tunability information ignored for referenced models

Passed

Check for implicit signal resolution

Passed

Check bus usage

Not Run

Check root model Inport block specifications

This check is only supported at the model level. To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis.

Check for blocks not recommended for MISRA-C:2004 compliance

Identify blocks that are not supported or recommended for MISRA-C:2004 compliant code generation.

See Also

High-Integrity Guidelines, hisl_0020 'Blocks not recommended for MISRA-C:2004 compliance'

Passed
Blocks that are not supported or recommended for MISRA-C:2004 compliant code generation were not found in the model or subsystem.

Check configuration parameters for MISRA-C:2004 compliance

Identify configuration parameters that might impact MISRA-C:2004 compliant code generation.

See Also

High-Integrity Guidelines, hisl_0060 'Configuration parameters to improve MISRA-C:2004 compliance'

_________________________________________________________________________________________

Check Model Verification block enabling
Identify whether Diagnostics > Data Validity > Model Verification block enabling is set to Disable All.

Warning
Diagnostics > Data Validity > Model Verification block enabling is not set to Disable All.

Configuration Parameter	Actual Value	Recommended Value
Model Verification block enabling	UseLocalSettings	DisableAll

Recommended Action
Set Diagnostics > Data Validity > Model Verification block enabling to Disable All.
_________________________________________________________________________________________

Check System target file
Identify whether Code Generation > System target file is an ERT-based target.

Passed
Code Generation > System target file is set to an ERT-based target.
_________________________________________________________________________________________

Check Code Generation > Interface parameters
Identify whether Code Generation > Interface parameters are set to recommended values.

Warning
The following Code Generation > Interface parameters are not set to the recommended values.

Configuration Parameter	Actual Value	Recommended Value
Non-finite numbers	Selected	Cleared
Code replacement library	GCC ARM Cortex-M3	None

Recommended Action
Set the above Code Generation > Interface parameters to the recommended values.
_________________________________________________________________________________________

Check Parentheses level
Identify whether Code Generation > Code Style > Parentheses level is Maximum (Specify precedence with parentheses).

Warning
Code Generation > Code Style > Parentheses level is not set to Maximum (Specify precedence with parentheses).

Configuration Parameter	Actual Value	Recommended Value
Parentheses level	Nominal	Maximum

Recommended Action
Set Code Generation > Code Style > Parentheses level to Maximum (Specify precedence with parentheses).
_________________________________________________________________________________________

Check Maximum identifier length
Identify whether Code Generation > Symbols > Maximum identifier length parameter is set to 31.

Passed
Code Generation > Symbols > Maximum identifier length parameter is set to 31.

Check consistency of block parameter units

Identify Simscape blocks with ambiguous setting of parameter units. For example, a block parameter expected in 'Hz' may be specified in the dialog with unit of 'rad/s'. Such settings could lead to unexpected conversion factors applied to the numerical value.

Passed
No Simscape blocks with ambiguous unit setting found in the model.

Check for optimal bus virtuality

Passed

Check for partial structure parameter usage with bus signals

Not Run

Check bus usage

Not Run

Identify questionable operations for strict single-precision design

Not Run

Display model version information

Not Run

Check safety-related optimization settings

Check optimization settings in the model configuration that might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Block reduction (BlockReduction)	on	off
Warning	Application lifespan (days) (LifeSpan)	1	inf
Warning	Remove code from floating-point to integer conversions that wraps out-of-range values (EfficientFloat2IntCast)	off	on

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related code generation settings

Check optimization settings in the model configuration that might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values	Not Recommended Values	Prerequisites
Warning	Show eliminated blocks (ShowEliminatedStatement)	off	on		SystemTargetFile
Warning	Verbose comments for SimulinkGlobal storage class (ForceParamTrailComments)	off	on		SystemTargetFile
Warning	Requirements in block comments (ReqsInCode)	off	on		SystemTargetFile
Warning	non-finite numbers (SupportNonFinite)	on	off		SystemTargetFile
Warning	absolute time (SupportAbsoluteTime)	on	off		SystemTargetFile
Warning	Terminate function required (IncludeMdlTerminateFcn)	on	off		SystemTargetFile
Warning	Suppress error status in real-time model data structure (SuppressErrorStatus)	off	on		SystemTargetFile
Warning	Parentheses level (ParenthesesLevel)	Nominal	Maximum		SystemTargetFile
Warning	Preserve operand order in expression (PreserveExpressionOrder)	off	on		SystemTargetFile
Warning	Preserve condition expression in if statement (PreserveIfCondition)	off	on		SystemTargetFile
Warning	Generate preprocessor conditionals (GeneratePreprocessorConditionals)	Use local settings	Disable all		SystemTargetFile
Warning	Minimum mangle length (MangleLength)	1		1, 2, 3	SystemTargetFile

∧ Less

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check sample times and tasking mode

Not Run

Check solver for code generation

Passed

Check the hardware implementation

Check 'Byte ordering' and 'Signed integer division rounds to' parameters
Identify inconsistencies or underspecification of hardware attributes that can lead to incorrect and inefficient generated code.

Warning
You have not specified Byte ordering and Signed integer division rounding.

Recommended Action
Specify Byte ordering to ensure efficient code generation for the target hardware. Specify Signed integer division rounding to ensure correct code generation for the target hardware.
_________________________________________________________________________________________

Check whether 'Production hardware' and 'Test hardware' match
Identify whether 'Test hardware is the same as production hardware' is selected in the Configuration Parameters > Hardware Implementation pane. If it is cleared, identify whether target specifications match.

Passed
'Test hardware is the same as production hardware' is selected or is cleared and the target specifications match.

10.1 Requirements Traceability

4

0

1

0

Check for blocks that do not link to requirements

Check for blocks that do not link to a requirements document

Warning
The following blocks do not link to a requirements document:

∧ Less
Recommended Action
For each block in the list, in the Model Editor, right-click the block, select Requirements Traceability, and specify a requirement.

Identify requirement links that specify invalid locations within documents

Passed

Identify requirement links with missing documents

Passed

Identify requirement links with path type inconsistent with preferences

Passed

Identify selection-based links having description fields that do not match their requirements document text

Passed

10.2 Model Diagnostic Settings

2

0

12

0

Check safety-related diagnostic settings for solvers

Check diagnostic settings in the model configuration that apply to solvers and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Algebraic loop (AlgebraicLoopMsg)	warning	error
Warning	Minimize algebraic loop (ArtificialAlgebraicLoopMsg)	warning	error
Warning	Block priority violation (BlockPriorityViolationMsg)	warning	error
Warning	Unspecified inheritability of sample time (UnknownTsInhSupMsg)	warning	error
Warning	Automatic solver parameter selection (SolverPrmCheckMsg)	warning	error
Warning	State name clash (StateNameClashWarn)	none	warning

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for sample time

Check diagnostic settings in the model configuration that apply to sample time and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Source block specifies -1 sample time (InheritedTsInSrcMsg)	warning	error
Warning	Discrete used as continuous (DiscreteInheritContinuousMsg)	warning	error
Warning	Enforce sample times specified by Signal Specification blocks (SigSpecEnsureSampleTimeMsg)	warning	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for signal data

Check diagnostic settings in the model configuration that apply to signal data and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Division by singular matrix (CheckMatrixSingularityMsg)	none	error
Warning	Underspecified data types (UnderSpecifiedDataTypeMsg)	none	error
Warning	Detect overflow (IntegerOverflowMsg)	warning	error
Warning	Inf or NaN block output (SignalInfNanChecking)	none	error
Warning	Simulation range checking (SignalRangeChecking)	none	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for parameters

Check diagnostic settings in the model configuration that apply to parameters and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Detect underflow (ParameterUnderflowMsg)	none	error
Warning	Detect precision loss (ParameterPrecisionLossMsg)	warning	error
Warning	Detect loss of tunability (ParameterTunabilityLossMsg)	warning	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for data used for debugging

Check diagnostic settings in the model configuration that apply to data used for debugging and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Model Verification block enabling (AssertControl)	UseLocalSettings	DisableAll

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for data store memory

Check diagnostic settings in the model configuration that apply to data store memory and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Detect read before write (ReadBeforeWriteMsg)	UseLocalSettings	EnableAllAsError
Warning	Detect write after read (WriteAfterReadMsg)	UseLocalSettings	EnableAllAsError
Warning	Detect write after write (WriteAfterWriteMsg)	UseLocalSettings	EnableAllAsError

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for type conversions

Check diagnostic settings in the model configuration that apply to type conversions and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Unnecessary type conversions (UnnecessaryDatatypeConvMsg)	none	warning, error
Warning	Vector/matrix block input conversion (VectorMatrixConversionMsg)	none	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for signal connectivity

Check diagnostic settings in the model configuration that apply to signal connectivity and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Signal label mismatch (SignalLabelMismatchMsg)	none	error
Warning	Unconnected block input ports (UnconnectedInputMsg)	warning	error
Warning	Unconnected block output ports (UnconnectedOutputMsg)	warning	error
Warning	Unconnected line (UnconnectedLineMsg)	warning	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for bus connectivity

Check diagnostic settings in the model configuration that apply to bus connectivity and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Unspecified bus object at root Outport block (RootOutportRequireBusObject)	warning	error
Warning	Element name mismatch (BusObjectLabelMismatch)	warning	error
Warning	Bus signal treated as vector (StrictBusMsg)	ErrorLevel1	ErrorOnBusTreatedAsVector

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings that apply to function-call connectivity

Check diagnostic settings in the model configuration that apply to function-call connectivity and might impact safety.

Passed
All constraints on model configuration parameters have been met.

Status	Parameter	Current Value	Recommended Values
Pass	Invalid function-call connection (InvalidFcnCallConnMsg)	error	error
Pass	Context-dependent inputs (FcnCallInpInsideContextMsg)	EnableAllAsError	EnableAllAsError

Check safety-related diagnostic settings for compatibility

Check diagnostic settings in the model configuration that affect compatibility and might impact safety

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	S-function upgrades needed (SFcnCompatibilityMsg)	none	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for model initialization

Check whether Diagnostics > Data Validity >Underspecified initialization detection is set to Simplified. If it is set to Classic check that the sub-parameters are selected.

Passed
All constraints on model configuration parameters have been met.

Status	Parameter	Current Value	Recommended Values
Pass	Underspecified initialization detection (UnderspecifiedInitializationDetection)	Simplified	Simplified

Check safety-related diagnostic settings for model referencing

Check diagnostic settings in the model configuration that apply to model referencing and might impact safety.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Port and parameter mismatch (ModelReferenceIOMismatchMessage)	none	error
Warning	Model configuration mismatch (ModelReferenceCSMismatchMessage)	none	warning, error
Warning	Invalid root Inport/Outport block connection (ModelReferenceIOMsg)	none	error
Warning	Unsupported data logging (ModelReferenceDataLoggingMessage)	warning	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

Check safety-related diagnostic settings for saving

Check diagnostic settings in the model configuration that apply to saving model files.

Warning
The model configuration parameters are not set to the recommended values specified in the data file.

Status	Parameter	Current Value	Recommended Values
Warning	Block diagram contains disabled library links (SaveWithDisabledLinksMsg)	warning	error
Warning	Block diagram contains parameterized library links (SaveWithParameterizedLinksMsg)	warning	error

Recommended Action
Follow the links in the result table to modify the model configuration parameters.

10.3 Simulink

9

0

2

11

Check usage of lookup table blocks

Check for Lookup Table blocks, Prelookup blocks and Interpolation blocks that do not generate out-of-range checking code.

Passed
There are no Lookup Table blocks, Prelookup blocks and Interpolation blocks in the model.

Check for blocks that have constraints on tunable parameters

Not Run

Check for Discrete-Time Integrator blocks with initial condition uncertainty

Passed

Check for potentially delayed function-call block return values

Not Run

Check model for known block upgrade issues

Update analysis is only supported at the model level. To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis over.

Check root model Inport block specifications

This check is only supported at the model level. To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis.

Check usage of Merge blocks

Not Run

Check for blocks not recommended for C/C++ production code deployment

Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.

Passed
Blocks not recommended for C/C++ production code deployment were not found in the model or subsystem.

Identify questionable subsystem settings

Not Run

Check usage of tunable parameters in blocks

Identify tunable parameters used to specify expressions, data type conversions, or indexing operations.

See Also

MathWorks Automotive Advisory Board Guideline: db_0110

Passed
Tunable parameters are not used in the model.

Check usage of Math Operations blocks

Not Run

Check usage of Signal Routing blocks

Not Run

Check usage of Logic and Bit Operations blocks

Not Run

Check usage of Ports and Subsystems blocks

Not Run

Check bus usage

Not Run

Identify unconnected lines, input ports, and output ports

Identify unconnected lines, input ports, and output ports in the subsystem

Passed
There are no unconnected lines, input ports, and output ports in this subsystem.

Check for Strong Data Typing with Simulink I/O

Identify whether Stateflow charts have Use Strong Data Typing with Simulink I/O cleared.

See Also

MathWorks Automotive Advisory Board Guideline: db_0122

Passed
Use Strong Data Typing with Simulink I/O is selected.

Check for inconsistent vector indexing methods

Check consistent usage of vector indexing methods across the model or subsystem

Passed
All the blocks in the model use 'one-based' vector indexing.

Check for MATLAB Function block interfaces with inherited properties

Not Run

Check MATLAB Function block metrics

Not Run

Check MATLAB Code Analyzer messages

Check MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Check MATLAB code for global variables

Check for global variables in MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check for global variables in MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check for global variables in called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

10.4 Stateflow

6

0

Check Stateflow data objects with local scope

Identify Stateflow data objects with local scope that are not scoped at the chart level or below.

See Also

MathWorks Automotive Advisory Board Guideline: db_0125

Passed
All Stateflow data objects are properly scoped.

Check usage of exclusive and default states in state machines

Identify Stateflow charts and substates that incorrectly use or define exclusive and default states.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0137

_________________________________________________________________________________________

Check Stateflow charts for exclusive states
Identify Stateflow charts that have singular exclusive (OR) states.

Passed
The Stateflow charts do not have singular exclusive (OR) states.
_________________________________________________________________________________________

Check Stateflow charts for undefined default states
Identify Stateflow charts that do not define default states.

Passed
Each Stateflow chart defines a default state.
_________________________________________________________________________________________

Check for multiple states assigned as the default state
At the root level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
The root level of the chart has only one default state assigned.
_________________________________________________________________________________________

Check for substates with singular OR states
States configured as OR should always be part of a group of states.

Passed
No singular OR states were detected.
_________________________________________________________________________________________

Check for substates without default states defined
At every level in the Stateflow hierarchy a default state should be assigned.

Passed
All substates have default states assigned.
_________________________________________________________________________________________

Check for substates with multiple default states defined
At every level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
All levels of the chart have only one default state assigned.

Check state machine type of Stateflow charts

Compares the state machine type of all Stateflow charts to the desired type.

Passed
The model contains only one Stateflow chart.

Input Parameters Selection

Name	Value
State Machine Type	Mealy or Moore

Check Stateflow charts for ordering of states and transitions

Identify Stateflow charts that have User specified state/transition execution order cleared.

Passed
All Stateflow charts in the model have User specified state/transition execution order selected.

Check Stateflow debugging options

Identify whether the following Stateflow debugging options are cleared: Enable debugging/animation, Enable overflow detection (with debugging), Transition Conflict, Detect Cycles, and Data Range

Passed
The Stateflow debugging options are selected.

Option	Recommended Value	Actual Value
Simulation Target > General > Enable debugging/animation	Selected	Selected
Simulation Target > General > Enable overflow detection (with debugging)	Selected	Selected
Transition Conflict	Selected	Selected
Detect Cycles	Selected	Selected
Data Range	Selected	Selected

Check Stateflow charts for uniquely defined data objects

Identifies local data identifiers that are defined in multiple scopes within a chart.

Passed
All Stateflow local data is uniquely defined.

10.5 Library Links

3

0

Identify disabled library links

Passed

Identify parameterized library links

Passed

Identify unresolved library links

Passed

10.6 Model Referencing

2

0

1

Check safety-related model referencing settings

Check model referencing settings in the model configuration that might impact safety.

Passed
All constraints on model configuration parameters have been met.

Status	Parameter	Current Value	Recommended Values
Pass	Rebuild (UpdateModelReferenceTargets)	IfOutOfDateOrStructuralChange	IfOutOfDateOrStructuralChange
Pass	Pass fixed-size scalar root inputs by value for code generation (ModelReferencePassRootInputsByReference) *	on	on
Pass	Minimize algebraic loop occurrences (ModelReferenceMinAlgLoopOccurrences)	off	off

Recommended Action

* The Command-Line values provided in the table are reverse of the settings in the Configuration Parameters Dialog. Therefore, 'on' in the Command-Line corresponds to an "Off" setting in the dialog, and 'off' in the Command-Line corresponds to an "On" setting in the dialog.

Check for model reference configuration mismatch

Not Run

Check for parameter tunability information ignored for referenced models

Passed

10.7 Bug Reports

1

0

7

0

Display bug reports for DO Qualification Kit

Display bug reports for DO Qualification Kit (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 4 DO Qualification Kit bug reports for release R2014a

ID	Bug Report Summary	Modified
1052010	DO Qualification Kit - Errors in Simulink Verification and Validation model coverage TOR and TCPR documents	03 Oct 2014
1055372	DO Qualification Kit - Insufficient test cases for the Logical Operator block in Simulink Verification and Validation model coverage	03 Oct 2014
1102239	DO Qualification Kit - Errors in Simulink® Code Inspector™ test cases and test case traceability matrix	03 Oct 2014
1036499	DO Qualification Kit - Polyspace® Bug Finder™ and Polyspace® Code Prover™ qualification summary report does not provide results for r2014a	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Embedded Coder

Display bug reports for Embedded Coder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 30 Embedded Coder bug reports for release R2014a

ID	Bug Report Summary	Modified
1165591	Embedded Coder - Simulation And Code Generation Mismatch: Possible mismatch in simulation and code generation results for conditional subsystems driven by a referenced model	30 Dec 2014
1166721	Embedded Coder - Use of nested bus objects can cause uncompilable code	17 Nov 2014
1163516	Embedded Coder - Incorrect Code Generation: Incorrect scaling applied to output of trigonometric block when inputs to block are of fixed-point data type and trigonometric function is replaced by code replacement library	14 Nov 2014
1033073	Embedded Coder - Import of AUTOSAR platform types may result in a Maximum recursion limit error when building the corresponding Simulink model	13 Nov 2014
1135794	Embedded Coder - Unnecessary reference and dereference generated when child model has C++ class interface with an input or output passed by reference	10 Nov 2014
1123960	Embedded Coder - Enumerated constants or signals might cause efficiency regression in generated code	04 Nov 2014
1146225	Embedded Coder - Generating code for a model that contains reusable subsystems can cause crash	10 Oct 2014
1040380	Embedded Coder - Behavior of SIL simulation may differ from behavior of normal mode simulation	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1047316	Embedded Coder - Code generation may generate an unused shared constant parameter	03 Oct 2014
1048850	Embedded Coder - Using GetSet custom storage classes may degrade performance	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1046484	Embedded Coder - Enumerated data for 16-bit targets results in inefficient generated code	03 Oct 2014
1072759	Embedded Coder - Incorrect Code Generation: Global data store memory referenced across model reference boundary	03 Oct 2014
1063135	Embedded Coder - Incorrect code replacement can occur for addition operations on complex types	03 Oct 2014
1052971	Embedded Coder - Generating code for a model which references a protected model can result in an error in the before_tlc hook function	03 Oct 2014
1058395	Embedded Coder - Selecting the Target hardware parameter in a model that uses Model blocks may cause errors during build.	03 Oct 2014
1045146	Embedded Coder - Building a model produces repeated linker and compiler flags in the generated makefile.	03 Oct 2014
1074528	Embedded Coder - Incorrect Code Generation: Code replacement library generates incorrect code for blocks involving inputs with heterogenous fixed-point types	03 Oct 2014
1070325	Embedded Coder - Build error Undefined identifier TLC_FASE for AUTOSAR model that references a custom storage class with non-direct data access	03 Oct 2014
1079297	Embedded Coder - Unable to save AUTOSAR model without Embedded Coder	03 Oct 2014
1038545	Embedded Coder - Enumerated data types on 16-bit targets cause unexpected behavior	03 Oct 2014
1071507	Embedded Coder - Unexpected mask parameter type causes build failure.	03 Oct 2014
1090328	Embedded Coder - Incorrect Code Generation: Incorrect code generation: Code replacement of fixed-point addition or subtraction operation can produce unexpected results	03 Oct 2014
1121795	Embedded Coder - ARXML importer error when importing components with MODE-ACCESS-POINTS	03 Oct 2014
1055681	Embedded Coder - Simulation And Code Generation Mismatch: Simulation and code generation mismatch when a Constant block drives a Rate Transition block through nested reusable subsystem and model boundaries.	03 Oct 2014
1087719	Embedded Coder - Incorrect Code Generation: Incorrect code is generated when the table size of an n-D Lookup Table block is tunable and code replacement library (CRL) is used to replace lookup table functions.	03 Oct 2014
1140393	Embedded Coder - Model reference software-in-the-loop (SIL) simulation fails when scalar output is passed as reference by C++ class method	29 Sep 2014
1129292	Embedded Coder - Incorrect Code Generation: Incorrect numerical result from generated code for model step function output that is updated in conditional execution context	24 Sep 2014
750309	Embedded Coder - Simulation And Code Generation Mismatch: Simulation behavior and generated code behavior might differ when subsystem variants use preprocessor conditions	06 Sep 2011

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Code Prover

Display bug reports for Polyspace Code Prover (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 4 Polyspace Code Prover bug reports for release R2014a

ID	Bug Report Summary	Modified
1032718	Polyspace Code Prover - Error message 'Unable to start the test campaign. An error has occurred during compilation' when using Automatic Orange Tester	03 Oct 2014
1007966	Polyspace Code Prover - Error ps_porky.exe has stopped working during compilation phase	03 Oct 2014
1053459	Polyspace Code Prover - False grey check on right operand of logical operation in while loop condition	03 Oct 2014
1115645	Polyspace Code Prover - Incorrect red check using left comma separator expression	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Bug Finder

Display bug reports for Polyspace Bug Finder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 13 Polyspace Bug Finder bug reports for release R2014a

ID	Bug Report Summary	Modified
1159277	Polyspace Bug Finder - Error Could not access folder /tmp/Polyspace	18 Dec 2014
1144593	Polyspace Bug Finder - Error submitting job with LSF Scheduler	24 Nov 2014
1106721	Polyspace Bug Finder - Error Unable to create zip archive	21 Oct 2014
1011906	Polyspace Bug Finder - Unnecessary use of Fixed-Point Toolbox	03 Oct 2014
1016765	Polyspace Bug Finder - Polyspace Queue Manager displays an empty queue when non ASCII characters are used in Author property	03 Oct 2014
1049312	Polyspace Bug Finder - Error Cannot instantiate Polyspace cluster during compilation phase	03 Oct 2014
1007401	Polyspace Bug Finder - Removing a running job from Polyspace Queue Manager freezes Job Scheduler	03 Oct 2014
1055753	Polyspace Bug Finder - Wrong setting for signed right shift when using Polyspace for MBD	03 Oct 2014
1043686	Polyspace Bug Finder - Analysis stops after 'Function Analysis' phase	03 Oct 2014
1067834	Polyspace Bug Finder - 'Search For All References' changes location in source code	03 Oct 2014
1020039	Polyspace Bug Finder - FlexLM license is not released when a job is canceled/deleted	03 Oct 2014
1124120	Polyspace Bug Finder - Justifications and comments are not saved automatically when an analysis is relaunched	03 Oct 2014
1090353	Polyspace Bug Finder - Back to model does not work for TargetLink	03 Oct 2014

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Code Inspector

Display bug reports for Simulink Code Inspector (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 21 Simulink Code Inspector bug reports for release R2014a

ID	Bug Report Summary	Modified
1061512	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for a Shift Arithmetic block with constant input.	20 Oct 2014
1048022	Simulink Code Inspector - Code inspection fails when the generated code uses a direct pointer	03 Oct 2014
1043629	Simulink Code Inspector - Simulink Code Inspector compatibility checks fails to detect when configuration parameter GenerateAllocFcn is set to on	03 Oct 2014
1058787	Simulink Code Inspector - Simulink Code Inspector fails to verify S-function blocks created with Legacy Code Tool	03 Oct 2014
1076734	Simulink Code Inspector - Code inspection might fail to verify generated code for If block containing unary minus operator	03 Oct 2014
1076813	Simulink Code Inspector - Code inspection returns Failed to Verify when it should return Verified for components containing shadowed blocks related to Data Store Memory	03 Oct 2014
1076803	Simulink Code Inspector - SLCI may fail to verify a model if model contains mux block	03 Oct 2014
1056460	Simulink Code Inspector - Code inspection gives incorrect results for referenced models using function prototype control.	03 Oct 2014
1005887	Simulink Code Inspector - Code inspection gives incorrect output under certain conditions if the model contains a MinMax block	03 Oct 2014
1067577	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for model containing Multiport Switch block with constant vector input	03 Oct 2014
1067577	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for model containing Multiport Switch block with constant vector input	03 Oct 2014
1080972	Simulink Code Inspector - Code inspection might fail to verify initialization code for model with multiple instances of referenced model	03 Oct 2014
1055585	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for model with cascaded Polynomial blocks	03 Oct 2014
1089166	Simulink Code Inspector - Code inspection fails for data type replacement names using upper case primitive C data type names	03 Oct 2014
1044579	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for a model containing a Width block	03 Oct 2014
1067681	Simulink Code Inspector - Code inspection might return Failed to verify for a component that should return Verified for model containing a Polynomial block with identical coefficients	03 Oct 2014
1104432	Simulink Code Inspector - Simulation And Code Generation Mismatch: Code inspection returns Failed to verify for a component that should return Verified when a vector in a Stateflow chart is assigned a value in some, but not all, branches of a condition	03 Oct 2014
1102254	Simulink Code Inspector - Simulation And Code Generation Mismatch: A Simulink Code Inspector compatibility check of the dimensions of Stateflow graphical function arguments returns Passed when it should return Warning for inconsistent argument dimensions of structure elements.	03 Oct 2014
1067649	Simulink Code Inspector - Simulation And Code Generation Mismatch: Code inspection returns Failed to verify for a component that should return Verified for selection on an input signal containing expressions independent of the selection index	15 Sep 2014
1090613	Simulink Code Inspector - Code inpection might fail to verify code for model with constant input to a product block.	21 Jul 2014
815642	Simulink Code Inspector - Simulink Code Inspector might fail to verify code generated from a model with redundant modeling constructs	27 Sep 2012

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Report Generator

Display bug reports for Simulink Report Generator (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 8 Simulink Report Generator bug reports for release R2014a

ID	Bug Report Summary	Modified
1177091	Simulink Report Generator - Internet Explorer 11 not supported for Simulink Web View	16 Dec 2014
1154431	Simulink Report Generator - Text component's Retain spaces and carriage returns option does not wrap when generating PDF reports	28 Oct 2014
1159257	Simulink Report Generator - Simulink System Snapshot component errors when taking a snapshot using a printframe with one cell	24 Oct 2014
924935	Simulink Report Generator - On non-English platforms, MATLAB Report Generator may garble certain character sequences such as ~(( when generating Word/Rich Text Format (RTF) documents via DSSSL stylesheets	24 Oct 2014
1031964	Simulink Report Generator - Simulink Web view shows transparent property tables when viewed from Internet Explorer 10.	03 Oct 2014
1075177	Simulink Report Generator - Simulink Web view throws an error when exporting a library MATLAB function block	03 Oct 2014
1061708	Simulink Report Generator - Simulink Web view system navigation issues with Internet Explorer 8	03 Oct 2014
1096793	Simulink Report Generator - Simulink Report Generator does not generate links for named propagated signal lines in HTML reports.	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Verification and Validation

Display bug reports for Simulink Verification and Validation (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 3 Simulink Verification and Validation bug reports for release R2014a

ID	Bug Report Summary	Modified
1084325	Simulink Verification and Validation - Error when using the XML data file to author Model Advisor checks for model configuration parameters	03 Oct 2014
1091947	Simulink Verification and Validation - Model Advisor Check usage of Math Operations blocks incorrectly warns if any element of a matrix defined in a Gain block contains 1	03 Oct 2014
685630	Simulink Verification and Validation - sldvmakeharness and slvnvmakeharness do not update correctly for models that are configured to load input data from a workspace before the simulation begins.	17 Mar 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for SystemTest

Display bug reports for SystemTest (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Passed
There are no SystemTest bug reports for release R2014a.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display configuration management data

Not Run

Display model metrics and complexity report

Display number of elements and name, level, and depth of subsystems for the model or subsystem

Model metrics information
Display number of elements for Simulink blocks and Stateflow constructs

Summary

Element Type	Count
Inport	10
Outport	14
Stateflow	1

Simulink

Block Type	Count
Outport	14
Inport	10
TriggerPort	1
Mux	1

Stateflow

Stateflow construct	Count
Stateflow Transitions	15
Stateflow States	11
Stateflow Events	10
Stateflow Data	10
Stateflow Junctions	2
Stateflow Charts	1

_________________________________________________________________________________________

Model complexity information
Display name, level, and depth of subsystems

Maximum Subsystem Depth: 2

Subsystem Depth

Subsystem Name	Level	Depth
Chart	1	1

Check for unconnected objects

Identify unconnected lines, input ports, and output ports in the subsystem

Passed
There are no unconnected lines, input ports, and output ports in this subsystem.

Check for root Inports with missing properties

Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions

Warning
This check is only supported at the model level.

Recommended Action
To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis.

Check for root Inports with missing range definitions

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.

Passed
Blocks not recommended for C/C++ production code deployment were not found in the model or subsystem.

Check usage of Stateflow constructs

Not Run

Check state machine type of Stateflow charts

Compares the state machine type of all Stateflow charts to the desired type.

Passed
The model contains only one Stateflow chart.

Input Parameters Selection

Name	Value
State Machine Type	Mealy or Moore

Check usage of Math Operations blocks

Not Run

Check usage of Signal Routing blocks

Not Run

Check usage of Logic and Bit Operations blocks

Not Run

Check usage of Ports and Subsystems blocks

Not Run

Check for inconsistent vector indexing methods

Check consistent usage of vector indexing methods across the model or subsystem

Passed
All the blocks in the model use 'one-based' vector indexing.

Check for model objects that do not link to requirements

Check Simulink blocks and Stateflow objects that do not link to a requirements document

Warning
The following blocks do not link to a requirement document:

∧ Less
Recommended Action
For each object in the list, in the Model Editor, right-click the block, select Requirements, and specify a requirement.

Check for MATLAB Function block interfaces with inherited properties

Not Run

Check MATLAB Function block metrics

Not Run

Check MATLAB Code Analyzer messages

Check MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Check MATLAB code for global variables

Check for global variables in MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check for global variables in MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check for global variables in called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Display bug reports for Embedded Coder

Display bug reports for Embedded Coder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 30 Embedded Coder bug reports for release R2014a

ID	Bug Report Summary	Modified
1165591	Embedded Coder - Simulation And Code Generation Mismatch: Possible mismatch in simulation and code generation results for conditional subsystems driven by a referenced model	30 Dec 2014
1166721	Embedded Coder - Use of nested bus objects can cause uncompilable code	17 Nov 2014
1163516	Embedded Coder - Incorrect Code Generation: Incorrect scaling applied to output of trigonometric block when inputs to block are of fixed-point data type and trigonometric function is replaced by code replacement library	14 Nov 2014
1033073	Embedded Coder - Import of AUTOSAR platform types may result in a Maximum recursion limit error when building the corresponding Simulink model	13 Nov 2014
1135794	Embedded Coder - Unnecessary reference and dereference generated when child model has C++ class interface with an input or output passed by reference	10 Nov 2014
1123960	Embedded Coder - Enumerated constants or signals might cause efficiency regression in generated code	04 Nov 2014
1146225	Embedded Coder - Generating code for a model that contains reusable subsystems can cause crash	10 Oct 2014
1040380	Embedded Coder - Behavior of SIL simulation may differ from behavior of normal mode simulation	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1047316	Embedded Coder - Code generation may generate an unused shared constant parameter	03 Oct 2014
1048850	Embedded Coder - Using GetSet custom storage classes may degrade performance	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1046484	Embedded Coder - Enumerated data for 16-bit targets results in inefficient generated code	03 Oct 2014
1072759	Embedded Coder - Incorrect Code Generation: Global data store memory referenced across model reference boundary	03 Oct 2014
1063135	Embedded Coder - Incorrect code replacement can occur for addition operations on complex types	03 Oct 2014
1052971	Embedded Coder - Generating code for a model which references a protected model can result in an error in the before_tlc hook function	03 Oct 2014
1058395	Embedded Coder - Selecting the Target hardware parameter in a model that uses Model blocks may cause errors during build.	03 Oct 2014
1045146	Embedded Coder - Building a model produces repeated linker and compiler flags in the generated makefile.	03 Oct 2014
1074528	Embedded Coder - Incorrect Code Generation: Code replacement library generates incorrect code for blocks involving inputs with heterogenous fixed-point types	03 Oct 2014
1070325	Embedded Coder - Build error Undefined identifier TLC_FASE for AUTOSAR model that references a custom storage class with non-direct data access	03 Oct 2014
1079297	Embedded Coder - Unable to save AUTOSAR model without Embedded Coder	03 Oct 2014
1038545	Embedded Coder - Enumerated data types on 16-bit targets cause unexpected behavior	03 Oct 2014
1071507	Embedded Coder - Unexpected mask parameter type causes build failure.	03 Oct 2014
1090328	Embedded Coder - Incorrect Code Generation: Incorrect code generation: Code replacement of fixed-point addition or subtraction operation can produce unexpected results	03 Oct 2014
1121795	Embedded Coder - ARXML importer error when importing components with MODE-ACCESS-POINTS	03 Oct 2014
1055681	Embedded Coder - Simulation And Code Generation Mismatch: Simulation and code generation mismatch when a Constant block drives a Rate Transition block through nested reusable subsystem and model boundaries.	03 Oct 2014
1087719	Embedded Coder - Incorrect Code Generation: Incorrect code is generated when the table size of an n-D Lookup Table block is tunable and code replacement library (CRL) is used to replace lookup table functions.	03 Oct 2014
1140393	Embedded Coder - Model reference software-in-the-loop (SIL) simulation fails when scalar output is passed as reference by C++ class method	29 Sep 2014
1129292	Embedded Coder - Incorrect Code Generation: Incorrect numerical result from generated code for model step function output that is updated in conditional execution context	24 Sep 2014
750309	Embedded Coder - Simulation And Code Generation Mismatch: Simulation behavior and generated code behavior might differ when subsystem variants use preprocessor conditions	06 Sep 2011

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for IEC Certification Kit

Display bug reports for IEC Certification Kit (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 1 IEC Certification Kit bug reports for release R2014a

ID	Bug Report Summary	Modified
1039832	IEC Certification Kit - Polyspace® Bug Finder™ Reference, Polyspace Bug Finder Release Notes, and Polyspace® Code Prover™ Release Notes shipping with the IEC Certification Kit are not the versions released with Polyspace for R2014a	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Code Prover

Display bug reports for Polyspace Code Prover (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 4 Polyspace Code Prover bug reports for release R2014a

ID	Bug Report Summary	Modified
1032718	Polyspace Code Prover - Error message 'Unable to start the test campaign. An error has occurred during compilation' when using Automatic Orange Tester	03 Oct 2014
1007966	Polyspace Code Prover - Error ps_porky.exe has stopped working during compilation phase	03 Oct 2014
1053459	Polyspace Code Prover - False grey check on right operand of logical operation in while loop condition	03 Oct 2014
1115645	Polyspace Code Prover - Incorrect red check using left comma separator expression	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Bug Finder

Display bug reports for Polyspace Bug Finder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 13 Polyspace Bug Finder bug reports for release R2014a

ID	Bug Report Summary	Modified
1159277	Polyspace Bug Finder - Error Could not access folder /tmp/Polyspace	18 Dec 2014
1144593	Polyspace Bug Finder - Error submitting job with LSF Scheduler	24 Nov 2014
1106721	Polyspace Bug Finder - Error Unable to create zip archive	21 Oct 2014
1011906	Polyspace Bug Finder - Unnecessary use of Fixed-Point Toolbox	03 Oct 2014
1016765	Polyspace Bug Finder - Polyspace Queue Manager displays an empty queue when non ASCII characters are used in Author property	03 Oct 2014
1049312	Polyspace Bug Finder - Error Cannot instantiate Polyspace cluster during compilation phase	03 Oct 2014
1007401	Polyspace Bug Finder - Removing a running job from Polyspace Queue Manager freezes Job Scheduler	03 Oct 2014
1055753	Polyspace Bug Finder - Wrong setting for signed right shift when using Polyspace for MBD	03 Oct 2014
1043686	Polyspace Bug Finder - Analysis stops after 'Function Analysis' phase	03 Oct 2014
1067834	Polyspace Bug Finder - 'Search For All References' changes location in source code	03 Oct 2014
1020039	Polyspace Bug Finder - FlexLM license is not released when a job is canceled/deleted	03 Oct 2014
1124120	Polyspace Bug Finder - Justifications and comments are not saved automatically when an analysis is relaunched	03 Oct 2014
1090353	Polyspace Bug Finder - Back to model does not work for TargetLink	03 Oct 2014

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Design Verifier

Display bug reports for Simulink Design Verifier (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 2 Simulink Design Verifier bug reports for release R2014a

ID	Bug Report Summary	Modified
754968	Simulink Design Verifier - Simulink Design Verifier incorrectly reports unreachable test objectives in Stateflow charts as Undecided.	13 Dec 2011
756367	Simulink Design Verifier - Number of successfully analyzed Simulink Design Verifier Test Generation objectives might decrease compared to number from previous release	13 Dec 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Verification and Validation

Display bug reports for Simulink Verification and Validation (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 3 Simulink Verification and Validation bug reports for release R2014a

ID	Bug Report Summary	Modified
1084325	Simulink Verification and Validation - Error when using the XML data file to author Model Advisor checks for model configuration parameters	03 Oct 2014
1091947	Simulink Verification and Validation - Model Advisor Check usage of Math Operations blocks incorrectly warns if any element of a matrix defined in a Gain block contains 1	03 Oct 2014
685630	Simulink Verification and Validation - sldvmakeharness and slvnvmakeharness do not update correctly for models that are configured to load input data from a workspace before the simulation begins.	17 Mar 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display configuration management data

Not Run

Display model metrics and complexity report

Display number of elements and name, level, and depth of subsystems for the model or subsystem

Model metrics information
Display number of elements for Simulink blocks and Stateflow constructs

Summary

Element Type	Count
Inport	10
Outport	14
Stateflow	1

Simulink

Block Type	Count
Outport	14
Inport	10
TriggerPort	1
Mux	1

Stateflow

Stateflow construct	Count
Stateflow Transitions	15
Stateflow States	11
Stateflow Events	10
Stateflow Data	10
Stateflow Junctions	2
Stateflow Charts	1

_________________________________________________________________________________________

Model complexity information
Display name, level, and depth of subsystems

Maximum Subsystem Depth: 2

Subsystem Depth

Subsystem Name	Level	Depth
Chart	1	1

Check for unconnected objects

Identify unconnected lines, input ports, and output ports in the subsystem

Passed
There are no unconnected lines, input ports, and output ports in this subsystem.

Check for root Inports with missing properties

Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions

Warning
This check is only supported at the model level.

Recommended Action
To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis.

Check for root Inports with missing range definitions

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.

Passed
Blocks not recommended for C/C++ production code deployment were not found in the model or subsystem.

Check usage of Stateflow constructs

Not Run

Check state machine type of Stateflow charts

Compares the state machine type of all Stateflow charts to the desired type.

Passed
The model contains only one Stateflow chart.

Input Parameters Selection

Name	Value
State Machine Type	Mealy or Moore

Check usage of Math Operations blocks

Not Run

Check usage of Signal Routing blocks

Not Run

Check usage of Logic and Bit Operations blocks

Not Run

Check usage of Ports and Subsystems blocks

Not Run

Check for inconsistent vector indexing methods

Check consistent usage of vector indexing methods across the model or subsystem

Passed
All the blocks in the model use 'one-based' vector indexing.

Check for model objects that do not link to requirements

Check Simulink blocks and Stateflow objects that do not link to a requirements document

Warning
The following blocks do not link to a requirement document:

∧ Less
Recommended Action
For each object in the list, in the Model Editor, right-click the block, select Requirements, and specify a requirement.

Check for MATLAB Function block interfaces with inherited properties

Not Run

Check MATLAB Function block metrics

Not Run

Check MATLAB Code Analyzer messages

Check MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Check MATLAB code for global variables

Check for global variables in MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check for global variables in MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check for global variables in called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Display bug reports for Embedded Coder

Display bug reports for Embedded Coder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 30 Embedded Coder bug reports for release R2014a

ID	Bug Report Summary	Modified
1165591	Embedded Coder - Simulation And Code Generation Mismatch: Possible mismatch in simulation and code generation results for conditional subsystems driven by a referenced model	30 Dec 2014
1166721	Embedded Coder - Use of nested bus objects can cause uncompilable code	17 Nov 2014
1163516	Embedded Coder - Incorrect Code Generation: Incorrect scaling applied to output of trigonometric block when inputs to block are of fixed-point data type and trigonometric function is replaced by code replacement library	14 Nov 2014
1033073	Embedded Coder - Import of AUTOSAR platform types may result in a Maximum recursion limit error when building the corresponding Simulink model	13 Nov 2014
1135794	Embedded Coder - Unnecessary reference and dereference generated when child model has C++ class interface with an input or output passed by reference	10 Nov 2014
1123960	Embedded Coder - Enumerated constants or signals might cause efficiency regression in generated code	04 Nov 2014
1146225	Embedded Coder - Generating code for a model that contains reusable subsystems can cause crash	10 Oct 2014
1040380	Embedded Coder - Behavior of SIL simulation may differ from behavior of normal mode simulation	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1047316	Embedded Coder - Code generation may generate an unused shared constant parameter	03 Oct 2014
1048850	Embedded Coder - Using GetSet custom storage classes may degrade performance	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1046484	Embedded Coder - Enumerated data for 16-bit targets results in inefficient generated code	03 Oct 2014
1072759	Embedded Coder - Incorrect Code Generation: Global data store memory referenced across model reference boundary	03 Oct 2014
1063135	Embedded Coder - Incorrect code replacement can occur for addition operations on complex types	03 Oct 2014
1052971	Embedded Coder - Generating code for a model which references a protected model can result in an error in the before_tlc hook function	03 Oct 2014
1058395	Embedded Coder - Selecting the Target hardware parameter in a model that uses Model blocks may cause errors during build.	03 Oct 2014
1045146	Embedded Coder - Building a model produces repeated linker and compiler flags in the generated makefile.	03 Oct 2014
1074528	Embedded Coder - Incorrect Code Generation: Code replacement library generates incorrect code for blocks involving inputs with heterogenous fixed-point types	03 Oct 2014
1070325	Embedded Coder - Build error Undefined identifier TLC_FASE for AUTOSAR model that references a custom storage class with non-direct data access	03 Oct 2014
1079297	Embedded Coder - Unable to save AUTOSAR model without Embedded Coder	03 Oct 2014
1038545	Embedded Coder - Enumerated data types on 16-bit targets cause unexpected behavior	03 Oct 2014
1071507	Embedded Coder - Unexpected mask parameter type causes build failure.	03 Oct 2014
1090328	Embedded Coder - Incorrect Code Generation: Incorrect code generation: Code replacement of fixed-point addition or subtraction operation can produce unexpected results	03 Oct 2014
1121795	Embedded Coder - ARXML importer error when importing components with MODE-ACCESS-POINTS	03 Oct 2014
1055681	Embedded Coder - Simulation And Code Generation Mismatch: Simulation and code generation mismatch when a Constant block drives a Rate Transition block through nested reusable subsystem and model boundaries.	03 Oct 2014
1087719	Embedded Coder - Incorrect Code Generation: Incorrect code is generated when the table size of an n-D Lookup Table block is tunable and code replacement library (CRL) is used to replace lookup table functions.	03 Oct 2014
1140393	Embedded Coder - Model reference software-in-the-loop (SIL) simulation fails when scalar output is passed as reference by C++ class method	29 Sep 2014
1129292	Embedded Coder - Incorrect Code Generation: Incorrect numerical result from generated code for model step function output that is updated in conditional execution context	24 Sep 2014
750309	Embedded Coder - Simulation And Code Generation Mismatch: Simulation behavior and generated code behavior might differ when subsystem variants use preprocessor conditions	06 Sep 2011

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for IEC Certification Kit

Display bug reports for IEC Certification Kit (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 1 IEC Certification Kit bug reports for release R2014a

ID	Bug Report Summary	Modified
1039832	IEC Certification Kit - Polyspace® Bug Finder™ Reference, Polyspace Bug Finder Release Notes, and Polyspace® Code Prover™ Release Notes shipping with the IEC Certification Kit are not the versions released with Polyspace for R2014a	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Code Prover

Display bug reports for Polyspace Code Prover (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 4 Polyspace Code Prover bug reports for release R2014a

ID	Bug Report Summary	Modified
1032718	Polyspace Code Prover - Error message 'Unable to start the test campaign. An error has occurred during compilation' when using Automatic Orange Tester	03 Oct 2014
1007966	Polyspace Code Prover - Error ps_porky.exe has stopped working during compilation phase	03 Oct 2014
1053459	Polyspace Code Prover - False grey check on right operand of logical operation in while loop condition	03 Oct 2014
1115645	Polyspace Code Prover - Incorrect red check using left comma separator expression	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Bug Finder

Display bug reports for Polyspace Bug Finder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 13 Polyspace Bug Finder bug reports for release R2014a

ID	Bug Report Summary	Modified
1159277	Polyspace Bug Finder - Error Could not access folder /tmp/Polyspace	18 Dec 2014
1144593	Polyspace Bug Finder - Error submitting job with LSF Scheduler	24 Nov 2014
1106721	Polyspace Bug Finder - Error Unable to create zip archive	21 Oct 2014
1011906	Polyspace Bug Finder - Unnecessary use of Fixed-Point Toolbox	03 Oct 2014
1016765	Polyspace Bug Finder - Polyspace Queue Manager displays an empty queue when non ASCII characters are used in Author property	03 Oct 2014
1049312	Polyspace Bug Finder - Error Cannot instantiate Polyspace cluster during compilation phase	03 Oct 2014
1007401	Polyspace Bug Finder - Removing a running job from Polyspace Queue Manager freezes Job Scheduler	03 Oct 2014
1055753	Polyspace Bug Finder - Wrong setting for signed right shift when using Polyspace for MBD	03 Oct 2014
1043686	Polyspace Bug Finder - Analysis stops after 'Function Analysis' phase	03 Oct 2014
1067834	Polyspace Bug Finder - 'Search For All References' changes location in source code	03 Oct 2014
1020039	Polyspace Bug Finder - FlexLM license is not released when a job is canceled/deleted	03 Oct 2014
1124120	Polyspace Bug Finder - Justifications and comments are not saved automatically when an analysis is relaunched	03 Oct 2014
1090353	Polyspace Bug Finder - Back to model does not work for TargetLink	03 Oct 2014

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Design Verifier

Display bug reports for Simulink Design Verifier (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 2 Simulink Design Verifier bug reports for release R2014a

ID	Bug Report Summary	Modified
754968	Simulink Design Verifier - Simulink Design Verifier incorrectly reports unreachable test objectives in Stateflow charts as Undecided.	13 Dec 2011
756367	Simulink Design Verifier - Number of successfully analyzed Simulink Design Verifier Test Generation objectives might decrease compared to number from previous release	13 Dec 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink PLC Coder

Display bug reports for Simulink PLC Coder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Passed
There are no Simulink PLC Coder bug reports for release R2014a.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Verification and Validation

Display bug reports for Simulink Verification and Validation (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 3 Simulink Verification and Validation bug reports for release R2014a

ID	Bug Report Summary	Modified
1084325	Simulink Verification and Validation - Error when using the XML data file to author Model Advisor checks for model configuration parameters	03 Oct 2014
1091947	Simulink Verification and Validation - Model Advisor Check usage of Math Operations blocks incorrectly warns if any element of a matrix defined in a Gain block contains 1	03 Oct 2014
685630	Simulink Verification and Validation - sldvmakeharness and slvnvmakeharness do not update correctly for models that are configured to load input data from a workspace before the simulation begins.	17 Mar 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display configuration management data

Not Run

Display model metrics and complexity report

Display number of elements and name, level, and depth of subsystems for the model or subsystem

Model metrics information
Display number of elements for Simulink blocks and Stateflow constructs

Summary

Element Type	Count
Inport	10
Outport	14
Stateflow	1

Simulink

Block Type	Count
Outport	14
Inport	10
TriggerPort	1
Mux	1

Stateflow

Stateflow construct	Count
Stateflow Transitions	15
Stateflow States	11
Stateflow Events	10
Stateflow Data	10
Stateflow Junctions	2
Stateflow Charts	1

_________________________________________________________________________________________

Model complexity information
Display name, level, and depth of subsystems

Maximum Subsystem Depth: 2

Subsystem Depth

Subsystem Name	Level	Depth
Chart	1	1

Check for unconnected objects

Identify unconnected lines, input ports, and output ports in the subsystem

Passed
There are no unconnected lines, input ports, and output ports in this subsystem.

Check for root Inports with missing properties

Identify Inport blocks in the top-level of the model with missing or inherited sample times, data types, or port dimensions

Warning
This check is only supported at the model level.

Recommended Action
To run this analysis, please open the model advisor from the top level of the model instead of the subsystem level and start the analysis.

Check for root Inports with missing range definitions

Not Run

Check for root Outports with missing range definitions

Not Run

Check for blocks not recommended for C/C++ production code deployment

Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.

Passed
Blocks not recommended for C/C++ production code deployment were not found in the model or subsystem.

Check usage of Stateflow constructs

Not Run

Check state machine type of Stateflow charts

Compares the state machine type of all Stateflow charts to the desired type.

Passed
The model contains only one Stateflow chart.

Input Parameters Selection

Name	Value
State Machine Type	Mealy or Moore

Check usage of Math Operations blocks

Not Run

Check usage of Signal Routing blocks

Not Run

Check usage of Logic and Bit Operations blocks

Not Run

Check usage of Ports and Subsystems blocks

Not Run

Check for inconsistent vector indexing methods

Check consistent usage of vector indexing methods across the model or subsystem

Passed
All the blocks in the model use 'one-based' vector indexing.

Check for model objects that do not link to requirements

Check Simulink blocks and Stateflow objects that do not link to a requirements document

Warning
The following blocks do not link to a requirement document:

∧ Less
Recommended Action
For each object in the list, in the Model Editor, right-click the block, select Requirements, and specify a requirement.

Check for MATLAB Function block interfaces with inherited properties

Not Run

Check MATLAB Function block metrics

Not Run

Check MATLAB Code Analyzer messages

Check MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Check MATLAB code for global variables

Check for global variables in MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check for global variables in MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check for global variables in called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Display bug reports for Embedded Coder

Display bug reports for Embedded Coder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 30 Embedded Coder bug reports for release R2014a

ID	Bug Report Summary	Modified
1165591	Embedded Coder - Simulation And Code Generation Mismatch: Possible mismatch in simulation and code generation results for conditional subsystems driven by a referenced model	30 Dec 2014
1166721	Embedded Coder - Use of nested bus objects can cause uncompilable code	17 Nov 2014
1163516	Embedded Coder - Incorrect Code Generation: Incorrect scaling applied to output of trigonometric block when inputs to block are of fixed-point data type and trigonometric function is replaced by code replacement library	14 Nov 2014
1033073	Embedded Coder - Import of AUTOSAR platform types may result in a Maximum recursion limit error when building the corresponding Simulink model	13 Nov 2014
1135794	Embedded Coder - Unnecessary reference and dereference generated when child model has C++ class interface with an input or output passed by reference	10 Nov 2014
1123960	Embedded Coder - Enumerated constants or signals might cause efficiency regression in generated code	04 Nov 2014
1146225	Embedded Coder - Generating code for a model that contains reusable subsystems can cause crash	10 Oct 2014
1040380	Embedded Coder - Behavior of SIL simulation may differ from behavior of normal mode simulation	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1047316	Embedded Coder - Code generation may generate an unused shared constant parameter	03 Oct 2014
1048850	Embedded Coder - Using GetSet custom storage classes may degrade performance	03 Oct 2014
1049916	Embedded Coder - Generating a code generation report with a Web view of the model causes MATLAB to stop	03 Oct 2014
1046484	Embedded Coder - Enumerated data for 16-bit targets results in inefficient generated code	03 Oct 2014
1072759	Embedded Coder - Incorrect Code Generation: Global data store memory referenced across model reference boundary	03 Oct 2014
1063135	Embedded Coder - Incorrect code replacement can occur for addition operations on complex types	03 Oct 2014
1052971	Embedded Coder - Generating code for a model which references a protected model can result in an error in the before_tlc hook function	03 Oct 2014
1058395	Embedded Coder - Selecting the Target hardware parameter in a model that uses Model blocks may cause errors during build.	03 Oct 2014
1045146	Embedded Coder - Building a model produces repeated linker and compiler flags in the generated makefile.	03 Oct 2014
1074528	Embedded Coder - Incorrect Code Generation: Code replacement library generates incorrect code for blocks involving inputs with heterogenous fixed-point types	03 Oct 2014
1070325	Embedded Coder - Build error Undefined identifier TLC_FASE for AUTOSAR model that references a custom storage class with non-direct data access	03 Oct 2014
1079297	Embedded Coder - Unable to save AUTOSAR model without Embedded Coder	03 Oct 2014
1038545	Embedded Coder - Enumerated data types on 16-bit targets cause unexpected behavior	03 Oct 2014
1071507	Embedded Coder - Unexpected mask parameter type causes build failure.	03 Oct 2014
1090328	Embedded Coder - Incorrect Code Generation: Incorrect code generation: Code replacement of fixed-point addition or subtraction operation can produce unexpected results	03 Oct 2014
1121795	Embedded Coder - ARXML importer error when importing components with MODE-ACCESS-POINTS	03 Oct 2014
1055681	Embedded Coder - Simulation And Code Generation Mismatch: Simulation and code generation mismatch when a Constant block drives a Rate Transition block through nested reusable subsystem and model boundaries.	03 Oct 2014
1087719	Embedded Coder - Incorrect Code Generation: Incorrect code is generated when the table size of an n-D Lookup Table block is tunable and code replacement library (CRL) is used to replace lookup table functions.	03 Oct 2014
1140393	Embedded Coder - Model reference software-in-the-loop (SIL) simulation fails when scalar output is passed as reference by C++ class method	29 Sep 2014
1129292	Embedded Coder - Incorrect Code Generation: Incorrect numerical result from generated code for model step function output that is updated in conditional execution context	24 Sep 2014
750309	Embedded Coder - Simulation And Code Generation Mismatch: Simulation behavior and generated code behavior might differ when subsystem variants use preprocessor conditions	06 Sep 2011

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for IEC Certification Kit

Display bug reports for IEC Certification Kit (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 1 IEC Certification Kit bug reports for release R2014a

ID	Bug Report Summary	Modified
1039832	IEC Certification Kit - Polyspace® Bug Finder™ Reference, Polyspace Bug Finder Release Notes, and Polyspace® Code Prover™ Release Notes shipping with the IEC Certification Kit are not the versions released with Polyspace for R2014a	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Code Prover

Display bug reports for Polyspace Code Prover (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 4 Polyspace Code Prover bug reports for release R2014a

ID	Bug Report Summary	Modified
1032718	Polyspace Code Prover - Error message 'Unable to start the test campaign. An error has occurred during compilation' when using Automatic Orange Tester	03 Oct 2014
1007966	Polyspace Code Prover - Error ps_porky.exe has stopped working during compilation phase	03 Oct 2014
1053459	Polyspace Code Prover - False grey check on right operand of logical operation in while loop condition	03 Oct 2014
1115645	Polyspace Code Prover - Incorrect red check using left comma separator expression	03 Oct 2014

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Polyspace Bug Finder

Display bug reports for Polyspace Bug Finder (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 13 Polyspace Bug Finder bug reports for release R2014a

ID	Bug Report Summary	Modified
1159277	Polyspace Bug Finder - Error Could not access folder /tmp/Polyspace	18 Dec 2014
1144593	Polyspace Bug Finder - Error submitting job with LSF Scheduler	24 Nov 2014
1106721	Polyspace Bug Finder - Error Unable to create zip archive	21 Oct 2014
1011906	Polyspace Bug Finder - Unnecessary use of Fixed-Point Toolbox	03 Oct 2014
1016765	Polyspace Bug Finder - Polyspace Queue Manager displays an empty queue when non ASCII characters are used in Author property	03 Oct 2014
1049312	Polyspace Bug Finder - Error Cannot instantiate Polyspace cluster during compilation phase	03 Oct 2014
1007401	Polyspace Bug Finder - Removing a running job from Polyspace Queue Manager freezes Job Scheduler	03 Oct 2014
1055753	Polyspace Bug Finder - Wrong setting for signed right shift when using Polyspace for MBD	03 Oct 2014
1043686	Polyspace Bug Finder - Analysis stops after 'Function Analysis' phase	03 Oct 2014
1067834	Polyspace Bug Finder - 'Search For All References' changes location in source code	03 Oct 2014
1020039	Polyspace Bug Finder - FlexLM license is not released when a job is canceled/deleted	03 Oct 2014
1124120	Polyspace Bug Finder - Justifications and comments are not saved automatically when an analysis is relaunched	03 Oct 2014
1090353	Polyspace Bug Finder - Back to model does not work for TargetLink	03 Oct 2014

∧ Less

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Design Verifier

Display bug reports for Simulink Design Verifier (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 2 Simulink Design Verifier bug reports for release R2014a

ID	Bug Report Summary	Modified
754968	Simulink Design Verifier - Simulink Design Verifier incorrectly reports unreachable test objectives in Stateflow charts as Undecided.	13 Dec 2011
756367	Simulink Design Verifier - Number of successfully analyzed Simulink Design Verifier Test Generation objectives might decrease compared to number from previous release	13 Dec 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

Display bug reports for Simulink Verification and Validation

Display bug reports for Simulink Verification and Validation (R2014a) available at http://www.mathworks.com/support/bugreports .
NOTE: This check does not determine whether your model might be affected by these bugs.

Warning
There are 3 Simulink Verification and Validation bug reports for release R2014a

ID	Bug Report Summary	Modified
1084325	Simulink Verification and Validation - Error when using the XML data file to author Model Advisor checks for model configuration parameters	03 Oct 2014
1091947	Simulink Verification and Validation - Model Advisor Check usage of Math Operations blocks incorrectly warns if any element of a matrix defined in a Gain block contains 1	03 Oct 2014
685630	Simulink Verification and Validation - sldvmakeharness and slvnvmakeharness do not update correctly for models that are configured to load input data from a workspace before the simulation begins.	17 Mar 2011

Recommended Action
To determine if your model is affected by the bugs, review the bug report descriptions and workarounds in the links provided in the ID column.

Input Parameters Selection

Name	Value
Only show bug reports modified after date(mm/dd/yyyy)

14.1 Naming Conventions

6

0

Check file names

Identify file names with incorrect characters or formatting.

See Also

MathWorks Automotive Advisory Board Guideline: ar_0001

Passed
All files have correct names.

Check folder names

Identify folders using incorrect characters and formatting.

See Also

MathWorks Automotive Advisory Board Guideline: ar_0002

Passed
All folder names have correct formatting.

Check subsystem names

Identify subsystem names that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0201

Passed
All subsystem names use correct characters.

Check port block names

Identify names of Inport or Outport blocks that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0211

Passed
All the Inport or Outport block names use correct characters.

Check character usage in signal labels

Identify signal labels that are not correct for C variable names.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0221

Passed
All signal labels use correct characters.

Check character usage in block names

Identify block names that use characters that are not correct in C code.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0231

Passed
All blocks use correct characters.

14.2 Model Architecture

1

0

Check for mixing basic blocks and subsystems

Identify levels in the model that include basic blocks and subsystems. Each level of a model must be designed with blocks of the same level (for example, only subsystems or only basic blocks).

See Also

MathWorks Automotive Advisory Board Guideline: db_0143

Passed
The model does not mix basic blocks and subsystems at the same level.

14.3 Model Configuration Options

1

0

1

0

Check Implement logic signals as Boolean data (vs. double)

Identify whether Implement logic signals as Boolean data (vs. double) is selected.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0011

Passed
Implement logic signals as Boolean data (vs. double) is selected.

Check model diagnostic parameters

Identify diagnostic parameters that are set to none.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0021

Warning
The following diagnostics parameters are set to none:

Recommended Action
In the Configuration Parameters dialog box, set the above diagnostic parameters to warning or error.

14.4 Simulink

17

0

4

3

Check for Simulink diagrams using nonstandard display attributes

Identify nonstandard display attributes in Simulink diagrams.

See Also

MathWorks Automotive Advisory Board Guideline: na_0004

_________________________________________________________________________________________

Check format settings
Identify incorrect model-level format options.

Warning
NOTE: The following subchecks were performed on a subsystem, but are based on root-level settings.The following format display options are incorrect.

Display Attribute	Recommended Value	Actual Value
Display > Signals & Ports > Wide Nonscalar Lines	on	off
Display > Library Links	none	disabled

Recommended Action
Set the format options to the recommended value.
_________________________________________________________________________________________

Check block colors
Identify blocks using nonstandard colors.

Passed
All blocks use standard colors.
_________________________________________________________________________________________

Check canvas colors
Identify canvases that are not white.

Passed
All diagrams use a white canvas.
_________________________________________________________________________________________

Check diagram zoom
Identify diagrams that do not have zoom factor set to 100 %.
Note: Zoom factors can differ for each instance of a model diagram opened in Simulink Editor

Warning
The following diagrams do not have zoom factor set to 100 percent:

state_machine/StateMachine

Recommended Action
For each listed diagram, select View > Zoom > Normal View (100%).

Check font formatting

Identify inconsistent formatting of text.

See Also

MathWorks Automotive Advisory Board Guideline: db_0043

Passed
All block and line fonts have consistent formatting.

The following font characteristics are used in the model/subsystem. Font characteristics are sorted by number of occurrences. The most common characteristics are bold.

Font Name	Font Size	Font Style
Helvetica	10	normal

Input Parameters Selection

Name	Value
Font Name	Common
Font Size	Common
Font Style	Common

Check positioning and configuration of ports

Identify input and output ports with incorrect positioning and configurations.

See Also

MathWorks Automotive Advisory Board Guideline: db_0042

_________________________________________________________________________________________

Check Inport blocks position
Identify Inport blocks that result in left-flowing signals.

Passed
There are no Inport blocks in the model that result in left-flowing signals.
_________________________________________________________________________________________

Check Outport block position
Identify Outport blocks that result in left-flowing signals.

Passed
There are no Outport blocks in the model that result in left-flowing signals.
_________________________________________________________________________________________

Check port orientation
Identify port blocks with nondefault orientation.

Passed
All ports use the default orientation.
_________________________________________________________________________________________

Check for duplicate Inports blocks
Identify duplicate Inport blocks.

Passed
All Inport blocks in the model are used once.

Check visibility of block port names

Identify port block names that are not uniformly displayed. The block names must all be displayed or none displayed. Library blocks are an exception to this rule. This check ignores masked and subsystem blocks.

See Also

MathWorks Automotive Advisory Board Guideline: na_0005

_________________________________________________________________________________________

Check for incorrect port name display
Identify ports that are incorrectly displaying names.

Passed
Subsystem blocks are correctly displayed.
_________________________________________________________________________________________

Check for incorrect subsystem port name display
Identify subsystems that are incorrectly displaying names.

Passed
Subsystem blocks are correctly displayed.

Input Parameters Selection

Name	Value
Display all port names (Diagram > Format > Show Block Name).	true

Check display for port blocks

Identify Inport and Outport blocks that do not specify Port number for the Icon display block parameter.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0081

Passed
All port blocks display the port number.

Check whether block names appear below blocks

Identify blocks where the name is not displayed below the block.

See Also

MathWorks Automotive Advisory Board Guideline: db_0142

Passed
All blocks have names displayed below the block.

Check the display attributes of block names

Identify whether to display block names.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0061

_________________________________________________________________________________________

Check for blocks with hidden names and obvious function
Identify block names that are displayed but can be hidden due to obvious behavior.

Passed
All blocks with obvious behavior have hidden names.
_________________________________________________________________________________________

Check for non-descriptive displayed block names
Identify block names that are displayed but should be hidden due to a lack of a descriptive name.

Warning
The following blocks have a name displayed, however, the name is not descriptive:

state_machine/StateMachine/Chart

Recommended Action
Modify the block name to provide descriptive information, or hide the block name by deselecting (Diagram > Format > Show Block Name).
_________________________________________________________________________________________

Check for missing block names
Identify block names that are hidden but should be displayed to show a descriptive name.

Passed
All displayed names provide descriptive information.

Check position of Trigger and Enable blocks

Identify Trigger and Enable blocks that are not centered in the upper third of the model diagram.

See Also

MathWorks Automotive Advisory Board Guideline: db_0146

Passed
The model does not contain Trigger and Enable blocks, or the blocks are in the upper third of the model diagram.

Check for nondefault block attributes

Identify blocks that use and fail to display nondefault values.

See Also

MathWorks Automotive Advisory Board Guideline: db_0140

Passed
Model displays all block parameter values that are not default values.

Check for matching port and signal names

Identify mismatches between names of ports and corresponding signals.

See Also

MathWorks Automotive Advisory Board Guideline: jm_0010

Warning
The following ports have names that differ from corresponding signals:

Recommended Action
Update the port or the signal so that the names match.

Check Trigger and Enable block names

Match the name of the Trigger and Enable blocks to the name of the signal that triggers the subsystem. If the signal is not named, use any name for the block.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0281

_________________________________________________________________________________________

Check Trigger block names
Identify Trigger blocks that do not match the names of the signals to which they are connected.

Passed
All Trigger blocks in the system are correctly named.
_________________________________________________________________________________________

Check for root level Trigger block
Identify Trigger blocks placed at the root level of the model.

Passed
No Trigger blocks where found at the root level.
_________________________________________________________________________________________

Check Enable block names
Identify Enable blocks that do not match the names of the signals to which they are connected.

Passed
All Enable blocks in the system are correctly named.
_________________________________________________________________________________________

Check for root level Enable block
Identify Enable blocks placed at the root level of the model.

Passed
No Enable blocks where found at the root level.

Check signal line labels

Identify blocks that require labeled signals. A subset of source and destination blocks require labeled signals.

See Also

MathWorks Automotive Advisory Board Guideline: na_0008

_________________________________________________________________________________________

Check source block labels
The following source blocks require labeled signals; Inport, From, Data Store Read, Constant, Bus Selector, Demux, Selector. If the signal name is visible on the block, this rule is considered met.

Warning
The following signals have no label:

∧ Less
Recommended Action
Add a new or propagated label to the signal line.
_________________________________________________________________________________________

Check destination block labels
The following destination blocks require labeled signals; Outport, Goto, Data Store Write, Bus Creator, Mux, Subsystem, Chart. If the signal name is visible on the source block, this rule is considered met.

Warning
The following signals have no label:

∧ Less
Recommended Action
Add a new or propagated label to the signal line.

Check for propagated signal labels

Identify propagated labels on signal lines.

See Also

MathWorks Automotive Advisory Board Guideline: na_0009

_________________________________________________________________________________________

Check subsystem input labels
Identify subsystem inputs that are labeled and display propagated signals.

Passed
All inputs to the subsystem have labels and display propagated signals.
_________________________________________________________________________________________

Check subsystem output labels
Identify outputs from subsystems that are labeled and display signal propagation.

Passed
All outputs from the subsystem have labels and display propagated signals.
_________________________________________________________________________________________

Signal propagation for nonsubsystem blocks
Identify the signal propagation status for both transformative and nontransformative blocks.

Passed
All outputs from non subsystem blocks correctly use labels and display propagated signals.

Check for unconnected ports and signal lines

Identify unconnected block input ports, output ports, and signal lines.

See Also

MathWorks Automotive Advisory Board Guideline: db_0081

Passed
All lines and ports in the model are connected.

Check for prohibited blocks in discrete controllers

Identify blocks that are not allowed in discrete controllers. Prohibited blocks include all continuous blocks and some source and sink blocks.

See Also

Passed
All blocks in the model are allowed in discrete controllers.

Check for blocks not recommended for C/C++ production code deployment

Identify blocks not supported by code generation or not recommended for C/C++ production code deployment.

Passed
Blocks not recommended for C/C++ production code deployment were not found in the model or subsystem.

Check for prohibited sink blocks

Identify sink blocks that must be removed prior to code generation.

See Also

MathWorks Automotive Advisory Board Guideline: hd_0001

Passed
There are no prohibited blocks in the subsystem.

Check scope of From and Goto blocks

Not Run

Check usage of Switch blocks

Not Run

Check usage of Relational Operator blocks

Identify Relational Operator blocks that connect to constants with the first (upper) input value.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0131

Passed
This model does not contain Relational Operator blocks.

Check for indexing in blocks

Identify blocks that use zero-based indexing.

See Also

MathWorks Automotive Advisory Board Guideline: db_0112

Passed
All blocks in the system are configured to use one-based indexing.

Check usage of buses and Mux blocks

Not Run

Check usage of tunable parameters in blocks

Identify tunable parameters used to specify expressions, data type conversions, or indexing operations.

See Also

MathWorks Automotive Advisory Board Guideline: db_0110

Passed
Tunable parameters are not used in the model.

Check orientation of Subsystem blocks

Check for subsystems that do not have the correct orientation. Blocks with the correct orientation have inputs on the left and outputs on the right.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0111

Passed
All subsystem blocks use the correct orientation.

14.5 Stateflow

10

0

2

5

Check usage of exclusive and default states in state machines

Identify Stateflow charts and substates that incorrectly use or define exclusive and default states.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0137

_________________________________________________________________________________________

Check Stateflow charts for exclusive states
Identify Stateflow charts that have singular exclusive (OR) states.

Passed
The Stateflow charts do not have singular exclusive (OR) states.
_________________________________________________________________________________________

Check Stateflow charts for undefined default states
Identify Stateflow charts that do not define default states.

Passed
Each Stateflow chart defines a default state.
_________________________________________________________________________________________

Check for multiple states assigned as the default state
At the root level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
The root level of the chart has only one default state assigned.
_________________________________________________________________________________________

Check for substates with singular OR states
States configured as OR should always be part of a group of states.

Passed
No singular OR states were detected.
_________________________________________________________________________________________

Check for substates without default states defined
At every level in the Stateflow hierarchy a default state should be assigned.

Passed
All substates have default states assigned.
_________________________________________________________________________________________

Check for substates with multiple default states defined
At every level in the Stateflow hierarchy only one state should be assigned as the default.

Passed
All levels of the chart have only one default state assigned.

Check transition orientations in flowcharts

Identify transitions in Stateflow flowcharts that are drawn incorrectly.

See Also

MathWorks Automotive Advisory Board Guideline: db_0132

_________________________________________________________________________________________

Check for conditions drawn vertically
Condition expressions should be drawn on the horizontal segments of flowcharts.

Passed
All condition expressions were drawn horizontally.
_________________________________________________________________________________________

Check for action transitions drawn vertically
Transition actions should be drawn on the vertical segments of flowcharts.

Passed
All transition actions were drawn vertically.
_________________________________________________________________________________________

Check for junctions for default transitions
All Junctions in a flow chart should have a default exit transition.

Passed
All Junctions have a default exit transition.
_________________________________________________________________________________________

Check for transitions that combine condition and action
Flowcharts should not combine condition evaluations and action expressions in a single transition.

Passed
No combined expressions were found in the chart.

Check entry formatting in State blocks in Stateflow charts

Identify missing line breaks between entry action (en), during action (du), and exit action (ex) entries in states. Identify missing line breaks after semicolons (;) in statements.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0501

Warning
The following entries use incorrect formatting.

Action Entry or Statement	State
entry: SubState = uint8(2);	state_machine/StateMachine/Chart/AgilityMap/Zebra/Delay

Recommended Action
Ensure that the entries (en:,du:,ex:) and each statement begin on a new line.

Check return value assignments of graphical functions in Stateflow charts

Identify graphical functions with multiple assignments of return values in Stateflow charts.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0511

Passed
No multiple assignments of return values were found.

Check default transition placement in Stateflow charts

Identify all groupings of states that do not have a default transition or do not have the default state as the top-most state.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0531

_________________________________________________________________________________________

Identify states that do not have default transitions.

Passed
All groupings of states have default transitions.
_________________________________________________________________________________________

Identify states where the default transition is not the top-most state.

Warning
The following states do not have the default state as the top-most state:

Recommended Action
Rearrange the states so the default state is the top-most state. Place the destination state of the default transition above all other states in the state hierarchy.
_________________________________________________________________________________________

Identify default transitions not connected to the top of the state.

Warning
The following default transitions are not connected to the top of the state:

Recommended Action
Move the transition so it connects to the top of the state.
_________________________________________________________________________________________

Identify states with multiple default transitions.

Passed
All states have only one default transition.

Check for Strong Data Typing with Simulink I/O

Identify whether Stateflow charts have Use Strong Data Typing with Simulink I/O cleared.

See Also

MathWorks Automotive Advisory Board Guideline: db_0122

Passed
Use Strong Data Typing with Simulink I/O is selected.

Check Stateflow data objects with local scope

Identify Stateflow data objects with local scope that are not scoped at the chart level or below.

See Also

MathWorks Automotive Advisory Board Guideline: db_0125

Passed
All Stateflow data objects are properly scoped.

Check usage of return values from a graphical function in Stateflow charts

Identify calls to graphical functions that are used in conditional expressions.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jc_0521

Passed
No conditional expressions containing calls to graphical functions were found.

Check for MATLAB expressions in Stateflow charts

Identify Stateflow objects that use MATLAB expressions that are not suitable for code generation.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0127

Passed
No Stateflow objects that use MATLAB expressions were found.

Check for pointers in Stateflow charts

Identify pointer operations on custom code variables.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jm_0011

Passed
No pointer operations were found.

Check for event broadcasts in Stateflow charts

Identify undirected event broadcasts that might cause recursion during simulation and generate inefficient code.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: jm_0012

Passed
No instances of undirected event broadcast were found.

Check transition actions in Stateflow charts

Identify missing line breaks between transition actions.
Note: This check does not support charts that use MATLAB as the action language.

See Also

MathWorks Automotive Advisory Board Guideline: db_0151

Passed
All transition actions are formatted correctly.

Check for bitwise operations in Stateflow charts

Not Run

Check for unary minus operations on unsigned integers in Stateflow charts

Not Run

Check for comparison operations in Stateflow charts

Not Run

Check for equality operations between floating-point expressions in Stateflow charts

Not Run

Check for mismatches between names of Stateflow ports and associated signals

Not Run

14.6 MATLAB Functions

1

0

2

Check input and output settings of MATLAB Function blocks

Not Run

Check MATLAB Function block metrics

Not Run

Check MATLAB code for global variables

Check for global variables in MATLAB code

See Also

MathWorks Automotive Advisory Board Guideline: na_0024

_________________________________________________________________________________________

Check for global variables in MATLAB code used in MATLAB Function blocks

Passed
No MATLAB Function blocks found
_________________________________________________________________________________________

Check for global variables in MATLAB functions defined in Stateflow charts

Passed
No MATLAB functions defined in Stateflow charts found
_________________________________________________________________________________________

Check for global variables in called MATLAB functions

Passed
No external MATLAB functions found
_________________________________________________________________________________________

Identify requirement links with missing documents

Passed

Identify requirement links that specify invalid locations within documents

Passed

Identify selection-based links having description fields that do not match their requirements document text

Passed

Identify requirement links with path type inconsistent with preferences

Passed

Check for non-continuous signals driving derivative ports

Not Run

Runtime diagnostics for S-functions

Passed

Check if Read/Write diagnostics are enabled for Data Store blocks

Passed

Check code generation settings

Verify 'Language' setting
Check whether Code Generation > Language is set to C or C++.

Passed
Code Generation > Language is set to C or C++.
_________________________________________________________________________________________

Verify 'Code interface packaging' setting
Check whether Code Generation > Interface > Code interface packaging is set to Nonreusable function or Reusable function.

Passed
Code Generation > Interface > Code interface packaging is set to Nonreusable function or Reusable function.
_________________________________________________________________________________________

Verify 'Shared code placement' setting
Check whether Code Generation > Interface > Shared code placement is set to Shared location.

Warning
Code Generation > Interface > Shared code placement is not set to Shared location .

Recommended Action
Set Code Generation > Interface > Shared code placement to Shared location .
_________________________________________________________________________________________

Verify 'Source file' setting
Check whether Code Generation > Custom Code > Source file is set to "" (i.e. unspecified).

Passed
Code Generation > Custom Code > Source file is set to "".
_________________________________________________________________________________________

Verify 'Header file' setting
Check whether Code Generation > Custom Code > Header file is set to "" (i.e. unspecified).

Passed
Code Generation > Custom Code > Header file is set to "".
_________________________________________________________________________________________

Verify 'Initialize function' setting
Check whether Code Generation > Custom Code > Initialize function is set to "" (i.e. unspecified).

Passed
Code Generation > Custom Code > Initialize function is set to "".
_________________________________________________________________________________________

Verify 'Terminate function' setting
Check whether Code Generation > Custom Code > Terminate function is set to "" (i.e. unspecified).

Passed
Code Generation > Custom Code > Terminate function is set to "".
_________________________________________________________________________________________

Verify 'Combine signal/state structures' setting
Check whether Code Generation > Interface > Combine signal/state structures is cleared.

Passed
Code Generation > Interface > Combine signal/state structures is cleared.
_________________________________________________________________________________________

Verify 'Include comments' setting
Check whether Code Generation > Comments > Include comments is selected.

Passed
Code Generation > Comments > Include comments is selected.
_________________________________________________________________________________________

Verify 'Generate scalar inlined parameters as' setting
Check whether Code Generation > Symbols > Generate scalar inlined parameters as is set to Literals.

Passed
Code Generation > Symbols > Generate scalar inlined parameters as is set to Literals.
_________________________________________________________________________________________

Verify 'Preserve condition expression in if statement' setting
Check whether Code Generation > Code Style > Preserve condition expression in if statement is selected.

Warning
Code Generation > Code Style > Preserve condition expression in if statement is cleared.

Recommended Action
Select the Code Generation > Code Style > Preserve condition expression in if statement checkbox.
_________________________________________________________________________________________

Verify 'Code replacement library' setting
Check whether Code Generation > Interface > Code replacement library is set to None.

Warning
Code Generation > Interface > Code replacement library is not set to None .

Recommended Action
Set Code Generation > Interface > Code replacement library to None .
_________________________________________________________________________________________

Verify 'Standard math library' setting
Check whether Code Generation > Interface > Standard math library is set to C89/C90 (ANSI) or C99 (ISO).

Passed
Code Generation > Interface > Standard math library is set to C89/C90 (ANSI) or C99 (ISO).
_________________________________________________________________________________________

Verify 'Classic call interface' setting
Check whether Code Generation > Interface > Classic call interface is cleared.

Passed
Code Generation > Interface > Classic call interface is cleared.
_________________________________________________________________________________________

Verify 'Terminate function required' setting
Check whether Code Generation > Interface > Terminate function required is cleared.

Warning
Code Generation > Interface > Terminate function required is selected.

Recommended Action
Clear the Code Generation > Interface > Terminate function required checkbox.
_________________________________________________________________________________________

Verify 'MAT-file logging' setting
Check whether Code Generation > Interface > MAT-file logging is cleared.

Passed
Code Generation > Interface > MAT-file logging is cleared.
_________________________________________________________________________________________

Verify 'Support non-finite numbers' setting
Check whether Code Generation > Interface > Support non-finite numbers is cleared.

Warning
Code Generation > Interface > Support non-finite numbers is selected.

Recommended Action
Clear the Code Generation > Interface > Support non-finite numbers checkbox.
_________________________________________________________________________________________

Verify 'absolute time' setting
Check whether Code Generation > Interface > absolute time is cleared.

Warning
Code Generation > Interface > absolute time is selected.

Recommended Action
Clear the Code Generation > Interface > absolute time checkbox.
_________________________________________________________________________________________

Verify 'Suppress error status in real-time model data structure' setting
Check whether Code Generation > Interface > Suppress error status in real-time model data structure is selected.

Warning
Code Generation > Interface > Suppress error status in real-time model data structure is cleared.

Recommended Action
Select the Code Generation > Interface > Suppress error status in real-time model data structure checkbox.
_________________________________________________________________________________________

Verify 'Create block' setting
Check whether Code Generation > Verification > Create block is set to none.

Passed
Code Generation > Verification > Create block is set to none.
_________________________________________________________________________________________

Verify 'Measure function execution times' setting
Check whether Code Generation > Verification > Measure function execution times is cleared.

Passed
Code Generation > Verification > Measure function execution times is cleared.
_________________________________________________________________________________________

Verify 'Signal naming' setting
Check whether Code Generation > Symbols > Signal naming is set to None.

Passed
Code Generation > Symbols > Signal naming is set to None.
_________________________________________________________________________________________

Verify 'Parameter naming' setting
Check whether Code Generation > Symbols > Parameter naming is set to None.

Passed
Code Generation > Symbols > Parameter naming is set to None.
_________________________________________________________________________________________

Verify 'TLCOptions' setting
Check whether TLCOptions is set to "" (i.e. unspecified).

Passed
TLCOptions is set to "".
_________________________________________________________________________________________

Verify 'variable-size signals' setting
Check whether Code Generation > Interface > variable-size signals is cleared.

Passed
Code Generation > Interface > variable-size signals is cleared.
_________________________________________________________________________________________

Verify 'Single output/update function' setting
Check whether Code Generation > Interface > Single output/update function is selected.

Passed
Code Generation > Interface > Single output/update function is selected.
_________________________________________________________________________________________

Verify 'Suppress generation of default cases for Stateflow switch statements if unreachable' setting
Check whether Code Generation > Code Style > Suppress generation of default cases for Stateflow switch statements if unreachable is cleared.

Passed
Code Generation > Code Style > Suppress generation of default cases for Stateflow switch statements if unreachable is cleared.
_________________________________________________________________________________________

Verify Code Generation > Interface > Interface setting
Check whether Code Generation > Interface > Interface is set to None

Passed
Code Generation > Interface > Interface is set to None.

Check data import and export settings

Verify 'Initial state' setting
Check whether Data Import/Export > Initial state is cleared.

Passed
Data Import/Export > Initial state is cleared.

Check diagnostic settings

Verify 'Detect write after write' setting
Check whether Diagnostics > Data Validity > Detect write after write is set to EnableAllAsError.

Warning
Diagnostics > Data Validity > Detect write after write is not set to EnableAllAsError .

Recommended Action
Set Diagnostics > Data Validity > Detect write after write to EnableAllAsError .
_________________________________________________________________________________________

Verify 'Underspecified initialization detection' setting
Check whether Diagnostics > Data Validity > Underspecified initialization detection is set to Simplified.

Passed
Diagnostics > Data Validity > Underspecified initialization detection is set to Simplified.
_________________________________________________________________________________________

Verify 'Non-bus signals treated as bus signals' setting
Check whether Diagnostics > Connectivity > Non-bus signals treated as bus signals is set to error.

Warning
Diagnostics > Connectivity > Non-bus signals treated as bus signals is not set to error .This incompatibility is fatal and will prevent execution of the Code Inspector

Recommended Action
Set Diagnostics > Connectivity > Non-bus signals treated as bus signals to error .
_________________________________________________________________________________________

Verify 'Detect downcast' setting
Check whether Diagnostics > Data Validity > Detect downcast is set to error.

Passed
Diagnostics > Data Validity > Detect downcast is set to error.
_________________________________________________________________________________________

Verify 'Detect overflow' setting
Check whether Diagnostics > Data Validity > Parameters > Detect overflow is set to error.

Passed
Diagnostics > Data Validity > Parameters > Detect overflow is set to error.
_________________________________________________________________________________________

Verify 'Detect overflow' setting
Check whether Diagnostics > Data Validity > Signals > Detect overflow is set to error.

Warning
Diagnostics > Data Validity > Signals > Detect overflow is not set to error .

Recommended Action
Set Diagnostics > Data Validity > Signals > Detect overflow to error .
_________________________________________________________________________________________

Verify 'Detect underflow' setting
Check whether Diagnostics > Data Validity > Detect underflow is set to error.

Warning
Diagnostics > Data Validity > Detect underflow is not set to error .

Recommended Action
Set Diagnostics > Data Validity > Detect underflow to error .
_________________________________________________________________________________________

Verify 'Detect loss of tunability' setting
Check whether Diagnostics > Data Validity > Detect loss of tunability is set to error.

Warning
Diagnostics > Data Validity > Detect loss of tunability is not set to error .

Recommended Action
Set Diagnostics > Data Validity > Detect loss of tunability to error .
_________________________________________________________________________________________

Verify 'Unexpected backtracking' setting
Check whether Diagnostics > Stateflow > Unexpected backtracking is set to error.

Warning
Diagnostics > Stateflow > Unexpected backtracking is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Unexpected backtracking to error .
_________________________________________________________________________________________

Verify 'Invalid input data access in chart initialization' setting
Check whether Diagnostics > Stateflow > Invalid input data access in chart initialization is set to error.

Warning
Diagnostics > Stateflow > Invalid input data access in chart initialization is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Invalid input data access in chart initialization to error .
_________________________________________________________________________________________

Verify 'No unconditional default transitions' setting
Check whether Diagnostics > Stateflow > No unconditional default transitions is set to error.

Warning
Diagnostics > Stateflow > No unconditional default transitions is not set to error .

Recommended Action
Set Diagnostics > Stateflow > No unconditional default transitions to error .
_________________________________________________________________________________________

Verify 'Transition outside natural parent' setting
Check whether Diagnostics > Stateflow > Transition outside natural parent is set to error.

Warning
Diagnostics > Stateflow > Transition outside natural parent is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Transition outside natural parent to error .
_________________________________________________________________________________________

Verify 'Transition shadowing' setting
Check whether Diagnostics > Stateflow > Transition shadowing is set to error.

Warning
Diagnostics > Stateflow > Transition shadowing is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Transition shadowing to error .
_________________________________________________________________________________________

Verify 'Undirected event broadcasts' setting
Check whether Diagnostics > Stateflow > Undirected event broadcasts is set to error.

Warning
Diagnostics > Stateflow > Undirected event broadcasts is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Undirected event broadcasts to error .
_________________________________________________________________________________________

Verify 'Transition action specified before condition action' setting
Check whether Diagnostics > Stateflow > Transition action specified before condition action is set to error.

Warning
Diagnostics > Stateflow > Transition action specified before condition action is not set to error .

Recommended Action
Set Diagnostics > Stateflow > Transition action specified before condition action to error .
_________________________________________________________________________________________

Verify Bus signal treated as vector setting
Check whether Diagnostics > Connectivity > Bus signal treated as vector is set to 'error'

Warning
Diagnostics > Connectivity > Bus signal treated as vector is not set to error.This incompatibility is fatal and will prevent execution of the Code Inspector

Recommended Action
Set Diagnostics > Connectivity > Mux blocks used to create bus signals> to error and Diagnostics > Connectivity > Bus signal treated as vector to error.

Check hardware implementation settings

Verify 'char' setting
Check whether Hardware Implementation > char is set to 8.

Passed
Hardware Implementation > char is set to 8.
_________________________________________________________________________________________

Verify 'short' setting
Check whether Hardware Implementation > short is set to 16.

Passed
Hardware Implementation > short is set to 16.
_________________________________________________________________________________________

Verify 'int' setting
Check whether Hardware Implementation > int is set to 32.

Passed
Hardware Implementation > int is set to 32.
_________________________________________________________________________________________

Verify 'long' setting
Check whether Hardware Implementation > long is set to 32.

Passed
Hardware Implementation > long is set to 32.
_________________________________________________________________________________________

Verify 'float' setting
Check whether Hardware Implementation > float is set to 32.

Passed
Hardware Implementation > float is set to 32.
_________________________________________________________________________________________

Verify 'double' setting
Check whether Hardware Implementation > double is set to 64.

Passed
Hardware Implementation > double is set to 64.
_________________________________________________________________________________________

Verify 'pointer' setting
Check whether Hardware Implementation > pointer is set to 32.

Passed
Hardware Implementation > pointer is set to 32.
_________________________________________________________________________________________

Verify 'native' setting
Check whether Hardware Implementation > native is set to 32.

Passed
Hardware Implementation > native is set to 32.
_________________________________________________________________________________________

Verify 'Signed integer division rounds to' setting
Check whether Hardware Implementation > Signed integer division rounds to is set to Zero.

Warning
Hardware Implementation > Signed integer division rounds to is not set to Zero .

Recommended Action
Set Hardware Implementation > Signed integer division rounds to to Zero . Select a compatible device with attributes matching those listed in the SLCI Hardware Implementation checks and the SLCI documentation.
_________________________________________________________________________________________

Verify 'Shift right on a signed integer as arithmetic shift' setting
Check whether Hardware Implementation > Shift right on a signed integer as arithmetic shift is selected.

Passed
Hardware Implementation > Shift right on a signed integer as arithmetic shift is selected.
_________________________________________________________________________________________

Verify 'Test hardware is the same as production hardware' setting
Check whether Hardware Implementation > Test hardware is the same as production hardware is selected.

Passed
Hardware Implementation > Test hardware is the same as production hardware is selected.
_________________________________________________________________________________________

Verify 'Device type' setting
Identify whether Hardware Implementation > Device type is not set to ASIC/FPGA->ASIC/FPGA .

Passed
Hardware Implementation > Device type is not set to ASIC/FPGA->ASIC/FPGA .

Check optimization settings

Verify 'AdvancedOptControl' setting
Check whether AdvancedOptControl is set to -SLCI.

Warning
AdvancedOptControl is not set to -SLCI .This incompatibility is fatal and will prevent execution of the Code Inspector

Recommended Action
Set AdvancedOptControl to -SLCI .
_________________________________________________________________________________________

Verify 'Implement logic signals as Boolean data (vs. double)' setting
Check whether Optimization > Implement logic signals as Boolean data (vs. double) is selected.

Passed
Optimization > Implement logic signals as Boolean data (vs. double) is selected.
_________________________________________________________________________________________

Verify 'Optimize initialization code for model reference' setting
Check whether Optimization > Optimize initialization code for model reference is selected.

Passed
Optimization > Optimize initialization code for model reference is selected.
_________________________________________________________________________________________

Verify 'Remove code from floating-point to integer conversions that wraps out-of-range values' setting
Check whether Optimization > Remove code from floating-point to integer conversions that wraps out-of-range values is selected.

Warning
Optimization > Remove code from floating-point to integer conversions that wraps out-of-range values is cleared.

Recommended Action
Select the Optimization > Remove code from floating-point to integer conversions that wraps out-of-range values checkbox.
_________________________________________________________________________________________

Verify 'Remove code from floating-point to integer conversions with saturation that maps NaN to zero' setting
Check whether Optimization > Remove code from floating-point to integer conversions with saturation that maps NaN to zero is cleared.

Warning
Optimization > Remove code from floating-point to integer conversions with saturation that maps NaN to zero is selected.

Recommended Action
Clear the Optimization > Remove code from floating-point to integer conversions with saturation that maps NaN to zero checkbox.
_________________________________________________________________________________________

Verify 'Remove code that protects against division arithmetic exceptions' setting
Check whether Optimization > Remove code that protects against division arithmetic exceptions is cleared.

Passed
Optimization > Remove code that protects against division arithmetic exceptions is cleared.
_________________________________________________________________________________________

Verify 'Maximum stack size (bytes)' setting
Check whether Optimization > Signals and Parameters > Maximum stack size (bytes) is set to inf.

Warning
Optimization > Signals and Parameters > Maximum stack size (bytes) is not set to inf .

Recommended Action
Set Optimization > Signals and Parameters > Maximum stack size (bytes) to inf .
_________________________________________________________________________________________

Verify 'Pack Boolean data into bitfields' setting
Check whether Optimization > Signals and Parameters > Pack Boolean data into bitfields is cleared.

Passed
Optimization > Signals and Parameters > Pack Boolean data into bitfields is cleared.
_________________________________________________________________________________________

Verify 'Use bitsets for storing state configuration' setting
Check whether Optimization > Stateflow > Use bitsets for storing state configuration is cleared.

Passed
Optimization > Stateflow > Use bitsets for storing state configuration is cleared.
_________________________________________________________________________________________

Verify 'Simplify array indexing' setting
Check whether Optimization > Signals and Parameters > Simplify array indexing is cleared.

Passed
Optimization > Signals and Parameters > Simplify array indexing is cleared.
_________________________________________________________________________________________

Verify 'Inline parameters' setting
Check whether Optimization > Signals and Parameters > Inline parameters is selected.

Passed
Optimization > Signals and Parameters > Inline parameters is selected.
_________________________________________________________________________________________

Verify 'Use bitsets for storing Boolean data' setting
Check whether Optimization > Stateflow > Use bitsets for storing Boolean data is cleared.

Passed
Optimization > Stateflow > Use bitsets for storing Boolean data is cleared.

Check solver settings

Verify 'Type' setting
Check whether Solver > Type is set to Fixed-step.

Passed
Solver > Type is set to Fixed-step.
_________________________________________________________________________________________

Verify 'Solver' setting
Check whether Solver > Solver is set to FixedStepDiscrete.

Passed
Solver > Solver is set to FixedStepDiscrete.

Check for unconnected objects in the model

Check for unconnected objects
Identify unconnected lines, input ports, and output ports in the model or subsystem

Passed
There are no unconnected lines, input ports, or output ports in the model or subsystem.

Check system target file setting

Verify System target file setting
Check whether Code Generation > System target file is ert.tlc or a System target file derived from ERT

Passed
The target is ERT or derived from ERT.

Check function specification setting

Check model interface settings
Check whether Function specification in the Model Interface dialog box is set to Default model initialize and step functions

Passed
Model Interface >Function specification is set to Default model initialize and step functions .

Check for usage of fixed-point instrumentation

Not Run

Check for unsupported blocks

Check for blocks not supported by Simulink Code Inspector
Identify blocks that are not supported by Simulink Code Inspector

Passed
There are no unsupported blocks in this model or subsystem.

Check storage class for workspace variables

Not Run

Check for sample times in the model

Not Run

Check usage of Sources blocks

Not Run

Check usage of Signal Routing blocks

Not Run

Check usage of Math Operations blocks

Not Run

Check usage of Signal Attributes blocks

Not Run

Check usage of Logical and Bit Operations blocks

Not Run

Check usage of Lookup Tables blocks

Not Run

Check usage of User-Defined Function blocks

Not Run

Check usage of Ports and Subsystems blocks

Not Run

Check usage of Discontinuities blocks

Not Run

Check usage of Sinks blocks

Not Run

Check usage of Discrete blocks

Not Run

Check usage of root Outport blocks

Not Run

Check for unsupported Signal Conversion blocks automatically inserted at signals entering block input ports

Not Run

Check usage of buses

Not Run

Check for usage of synthesized local data stores

Not Run

Check usage of global data stores

Not Run

Check for root Outport blocks being conditionally assigned

Not Run

Check conditional input branch execution setting

Verify conditional input branch execution setting
Check whether 'Signal storage reuse' and 'Enable local block outputs' are set when conditional input branch execution is set

Passed
Conditional input branch execution setting is compatible.

Check usage of Stateflow blocks

Not Run

Check for Stateflow machine data

All Stateflow data must be parented by a Stateflow chart
Simulink Code Inspector does not support Stateflow data of machine scope

Passed
No Stateflow data is of machine scope.

Check for Stateflow machine events

All Stateflow events must be parented by a Stateflow chart
Simulink Code Inspector does not support Stateflow events of machine scope

Passed
No Stateflow events are of machine scope.

Check usage of Stateflow charts

Not Run

Check usage of Stateflow data

Not Run

Check usage of Stateflow events

Not Run

Check usage of Stateflow states

Not Run

Check usage of Stateflow junctions

Not Run

Check usage of Stateflow transitions

Not Run

Check usage of Stateflow graphical functions

Not Run

Check Loop unrolling threshold setting

Not Run

Check destinations of If and Switchcase blocks

Not Run

Check for root Outport blocks that have non-auto storage class

Not Run

Check for Terminator blocks connected to Model Reference block outports

Not Run

Check for unsupported propagation of initial condition values

Not Run

Check for usage of data dictionary

Not Run

Check compatibility with Simulink Design Verifier

Not Run

Check model for foreign characters

Check that the characters in the model can be represented in the current encoding.

Passed
All the characters in the model can be represented in the current encoding.

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.

Open the Upgrade Advisor

Warning
To check for upgrade issues, open the Upgrade Advisor.

Recommended Action
Click the link below to close the Model Advisor and open the Upgrade Advisor for state_machine/StateMachine.
Open the Upgrade Advisor

Model Advisor Report - state_machine.slx
Simulink version: 8.3	Model version: 1.33
System: state_machine/StateMachine	Current run: 30-Dec.-2014 23:53:38

Filter checks

Navigation

View

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection

Input Parameters Selection