This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Component Design

Component Design

Component Documentation

Reports

1 - EA4-x NTC 0xA9 CurrReasbnDiagc

Slide 1

NTC Overview
NTC 0xA9 Current Offset Reasonableness

Description: The Current Offset Reasonableness Diagnostic detects errors in the current measurement circuit that may lead to current feedback offset values that may cause performance and safety requirement violations.

Diagnostic Overview:  If a large current offset error occurs in a phase current measurement, the closed loop current control system adjusts the motor voltage so that the measurement of motor current matches the motor current command. If a fault exists that causes the motor current measurement to be incorrect then the motor voltage will thus be incorrect. This failure mode results in motor position-dependent motor torque or current errors which may be perceived as a large torque ripple at the motor shaft, and potentially larger than rated motor currents.  When the torque ripple caused by the phase current measurement offset error becomes large, it can produce motor torque in the opposite direction from the motor torque command resulting in difficulty moving a motor from specific motor positions.

The Current Offset Reasonableness method generates an expected motor voltage command based on a reference current command and a set of estimated motor parameters of the motor. The actual motor voltage command is  based on the reference current command and a set of measured motor current signals.   An error signal is calculated based on the expected motor voltage command and the actual motor voltage command. The method transforms the error signal into a stator reference frame (necessary in order for the current measurement offset error to appear as an offset in the voltage error signal) and diagnoses whether the set of measured motor current signals is faulty based on the transformed error signal.

Typical Fault Response:  F3 (Operator Notification)

 
(Most to Least Probable):

  • •Current Offset calibration incorrect. 

  • •Incorrect motor parameters for actual motor or motor parameter SW estimates being clamped by min/max calibration variables, 

  • •External circuit  … 

    • –Current Measurement Subsystem  

  • •More 

Initialization

 

Periodic

X

Event

 

Date

Revision

Initials

11/18/2016

Initial Release

Prerit Pramod

   
   
   
   
   
   
   
   
   

Description of Unusual Event setting NTC

Root Cause / Explanation

  
  
  

Date

FDD & Rev

Modifications to Diagnostic Function

   
   
   
   

Algorithm Changes / Lessons Learned / Revision Log

2 - SF031A_CurrReasbnDiagc_PeerReviewChkList

Nexteer_Template_V1.0

Overview

Project Info
Process
Safety
Software
Apps
SME
Master
Template Change Log

Sheet 1: Project Info

Peer Review Checklist - Component DesignTemplate Version: 3.0.0
Product NameElectric Power SteeringReview Scope
Component IDSF031A_CurrReasbnDiagcChanged the PIM names in Tusin Filter block from MotVltgDiagFildInpPrev, MotVltgDiagFildOutpPrev
to MotVltgDiagFildInp1Prev, MotVltgDiagFildOutp1Prev respectively and added 2 new PIMs
MotVltgDiagFildInp2Prev, MotVltgDiagFildOutp2Prev
Component Long NameCurrent Reasonableness Diagnostic
Component OwnerPrerit Pramod
Version that you started from. NOT the version you hope to release. If this will be v1.0.0, enter NA. Starting BaselineNA
The number that will be used when package is baselined in Synergy. For example, the first one will be 1.0.0. Intended Baseline1.1.0
Electrical ArchitectureEA4
CR NumberEA4# 8968
Author: The person who edited the design. Usually the Resolver of a CR. AuthorKrishna Namburi
Review TypeInspection



Author's Quality Statement:Author must provide an explanation of any deviation from an ideal Instpection process. This field may be used for analysis of anomalies. Only PIM names are updated and added. Formal Review is not required.




Meeting DateAttendeesExamples: Initial Mtg, Follow-up. Reason for Meeting
12/16/2016Prerit Pramod, Krishna NamburiReview for the changes









Sheet 2: Process

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Process Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .ContextYes













Are the following values correct for Runnables: .TimeStepYes













Are the following values correct for SrvRunnables: .ReturnYes













Are the following values correct for SrvRunnables: .ArgumentsYes













Are the following values correct for all Ip/Op/IrvSignals: .EngDTYes













Are the following values correct for all Ip/Op/IrvSignals: .DocUnitYes













Are the following values correct for all Ip/Op/IrvSignals: .EngInitYes













Are the following values correct for all Ip/Op/IrvSignals: .EngMinYes













Are the following values correct for all Ip/Op/IrvSignals: .EngMaxYes













Are the following values correct for all Ip/Op/IrvSignals: .ReadIn/WrittenInYes













Are the following values correct for all Ip/Op/IrvSignals: .ReadType/WriteTypeYes













Are the following values correct for all Calibrations: .DocUnitYes













Are the following values correct for all Calibrations: .PortNameYes













Are the following values correct for all NVM: .DocUnitYes













Are the following values correct for all PIM: .DocUnitYes













Are the following values correct for all Constants: .DocUnitYes













Does FDD Long Name, Short Name, and Description match requirements?Yes













Do output signal ranges match requirements?Yes













Are all clients from model defined in dictionary?Yes













Do client definitions match their corresponding server runnable?Yes













Is NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?














Is NVM with multiple values defined as a structure?














Are NVM structure members arranged largest-to-smallest datatype?














Are local Constants unique from global constants available in xx999A dictionaries?Yes













Are calibration tables named correctly (e.g. AssiX and AssiY)?NA













Are Constant names abbreviated properly (ALLCAPS are not checkable by tools)?Yes













Is the Data Dictionary Verification report error free?No













Are all data types represented by released Data_Management classes?Yes



























































































































































































2
Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Are all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model?Yes













Is each diagnostic (NTC) capable of being set to "PASS"?NA













Does non-zero intialization of PIM occur in the function's Init runnable?No













Does design properly include Set Ram Block Status when NVM RAM values change?NA













Are NTCs set only outside an IRQ (not related to the typical periodic OS)?NA













Are NTCs set and read only at periodic steps no less than 2 ms?NA













Does model execute without errors/warnings after loading NxtrMBDConfig configuration set?Yes













Is filename of model in correct format?Yes













Is Top level of model annotated with Requirements Baseline?Yes













Is the Top level of the model annotated with Tool Dependencies?Yes













Is Top level of model annotated with Change Log or History?Yes













Is the 2nd level of model free from subsystems that are not Function-Call Subsystems?Yes













Is the 2nd level of model free from arithmetic and logic operations?Yes













Are the Runnable trigger signals named as "call_<Runnable>"?No













Does 2nd level of model have a properly updated annotation with name, description, and intended baseline number?Yes













Are all data flow layers free of Function-Call Subsystems and Memory Store blocks?Yes













Does the Model have the confidentiality and copyright information inside all its Subsystems?Yes













Are all requirements links of the format <FDDNumber>_<ObjectID>?Yes













Does requirements HTML report reference only the DOORS module of this component for all links in the design?Yes













Was Model Advisor run with the correct configuration settings?Yes













Is the Model Advisor rerport free from "Fails".Yes













Does the model execute?Yes













If model has ADC input, is failure boolean input and appropriate fault response been included?NA













Do cal ranges & logic ensure no incompatible values for their datatype?Yes













Are "magic numbers" acceptable?Yes













Do IF..ELSEIF blocks also contain an ELSE condition?Yes













Do SWITCH CASE blocks also contain a DEFAULT condtion?NA











3
Are ELSE and DEFAULT branching conditions reachable when dependent on internal variables?Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does review meet 'inspection' criteria?Yes













Does Design folder contain only the model, data dictionary, and (optionally) a simulation setup script?Yes













Does Doc folder contain a zipped HTML webview model?Yes













Was webview model created without requirements highlighted?Yes













Does Doc folder contain appropriate number of NTC Summary sheets?NA













Does Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report?Yes



























































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25






























Sheet 3: Safety

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Safety Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for all Calibrations: .ImpactYes













Are the following values correct for all Calibrations: .TuningOwnerYes













Are the following values correct for all Calibrations: .OnlineYes













Does the FDD .DesignASIL property match requirements?Yes













Are lookup tables using compatible table dimensions?NA











































































































































































































































































































































































































































































































































































2
Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Are Model Advisor report ISO26262 warnings acceptable?Yes













Is model free from dynamic array size allocation?NA













Is model free from data type conversion blocks that do not explicitly state desired data type?Yes













Does model refrain from using Display Variable values in downstream operations?Yes













Are all GOTO/FROM blocks restricted in scope to their own subystem level?Yes













If model has ADC input, is failure boolean input and appropriate fault response been included?NA













Does design include output limiting blocks?Yes













Do cal ranges & logic ensure freedom from divide-by-zero?Yes













Are the following values correct for all NTC: .NtcTypYes













Does model include appropriate logic for dealing with missing or corrupted NVM data?NA



























































































































































































































































































3
Section 3: Delivery PackageAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does review meet 'inspection' criteria?Yes











































































































































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25






























Sheet 4: Software

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Software Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .ContextYes













Are the following values correct for SrvRunnables: .ReturnYes













Are the following values correct for SrvRunnables: .ArgumentsYes













Are the following values correct for all Calibrations: .PortNameYes













Are the following values correct for all NVM: .EngInitYes













Are the following values correct for all NVM: .AliasYes













Are the following values correct for all NVM: .InitRowColYes













Are the following values correct for all Display Variables: .EngMinYes













Are the following values correct for all Display Variables: .EngMaxYes













Are the following values correct for all Display Variables: .InitRowColYes













Are the following values correct for all PIM: .EngMinYes













Are the following values correct for all PIM: .EngMaxYes













Are the following values correct for all PIM: .InitRowColYes













Are lookup tables using compatible table dimensions?Yes













Are all clients from model defined in dictionary?Yes













Do client definitions match their corresponding server runnable?Yes













Is NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?NA













Is NVM with multiple values defined as a structure?NA













Are NVM structure members arranged largest-to-smallest datatype?NA













Are local Constants unique from global constants available in xx999A dictionaries?Yes





























































































































































































































































































































Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist.
Author: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist.
Author: Detailed Description of the finding shall be provided by the reviewer.
Corrective Action: What action is taken to fix the issue?
Author: Data in this column shall be filled by reviewer after checking whether the rework is completed.










Are all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model?Yes













Is each diagnostic (NTC) capable of being set to "PASS"?NA













Does non-zero intialization of PIM occur in the function's Init runnable?No













Does design properly include Set Ram Block Status when NVM RAM values change?NA













Are NTCs set only outside an IRQ (not related to the typical periodic OS)?Yes













Are NTCs set and read only at periodic steps no less than 2 ms?Yes













Is model free from dynamic array size allocation?Yes













Is model free from data type conversion blocks that do not explicitly state desired data type?Yes













Does model refrain from using Display Variable values in downstream operations?Yes













Are all GOTO/FROM blocks restricted in scope to their own subystem level?Yes













Does design calculate PIM values only within their defined range?Yes













Does design include output limiting blocks?Yes













Do cal ranges & logic ensure freedom from divide-by-zero?Yes













Do cal ranges & logic ensure no incompatible values for their datatype?Yes













Are Model Advisor report MISRA warnings acceptable?Yes













Is design free of unreachable logic?Yes













Do state machines provide exits of all non-latch states?NA













Is design free from recursive logic that could cause indefinate waits?Yes













Does design maintain data size consistency?Yes













Are "magic numbers" acceptable?Yes













Is design of a managable size and easy to understand?Yes













Is Stateflow used only for state machines not easily represented in Simulink?Yes













Is model free from over-nested IF logic or redundant IF..ELSEIF..ELSEIF.. Conditions?Yes













Is model free from arithmetic operations on Boolean values?Yes



























































3
Section 3: Delivery PackageAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status























































































































































4

DocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25






























Sheet 5: Apps

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

Applications Reviewer:







NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for Runnables: .TimeStepYes













Are the following values correct for all Calibrations: .DocUnitYes













Are the following values correct for all Calibrations: .EngMaxYes













Are the following values correct for all Calibrations: .CardinalityYes













Are the following values correct for all Calibrations: .CustomerVisibleYes













Are the following values correct for all Calibrations: .ImpactYes













Are the following values correct for all Calibrations: .GraphLinkYes













Are the following values correct for all Calibrations: .MonotonyYes













Are the following values correct for all NVM: .DocUnitNA













Are the following values correct for all Display Variables: .DocUnitYes













Are the following values correct for all Calibrations: .EngValyes













Are the following values correct for all Calibrations: .EngMinYes













Are the following values correct for all Calibrations: .TuningOwnerYes













Are the following values correct for all Calibrations: .OnlineYes













Does FDD Long Name, Short Name, and Description match requirements?Yes













Do output signal ranges match requirements?Yes













Do signal and parameter names accurately describe their purpose?Yes













Do all .Description properties provide useful information?Yes













Are calibration tables named correctly (e.g. AssiX and AssiY)?NA











































































































































































































































































































































2
Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does model execute without errors/warnings after loading NxtrMBDConfig configuration set?Yes













Does model include adequate annotation throughout?Yes













Are the following values correct for all NTC: .NtcTypYes













Are display variables appropriately placed?Yes













Does design provide appropriate tuning flexibility?NA













Are blocks linked to the correct requirements? (watch for problems due to copy/pasted blocks)Yes













Is the list of unlinked blocks acceptable?Yes













Does design account for all requirements?Yes













Is design of a managable size and easy to understand?Yes













Is design easily disabled via calibration?No













Does design either work with global signal units or contain necessary unit-conversion logic?No











































































































































































































































































3
Section 3: Delivery PackageAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does NTC Summary sheet adequately describe NTC usage?












































































































































4
Section 4: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25






























Sheet 6: SME

Peer Review Checklist - Component Design
Template Version:3.0.0






















YesClosedFR











NoRejectedFDD

SME Reviewer:Prerit Pramod






NAOpenModel

(optional) Reviewer #2:









FMEA












*.m File















Cal Process
































Item No.Cross Ref.Description of CheckAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1
Section 1: Data Dictionary














Are the following values correct for all Calibrations: .EngDTYesYes












Are the following values correct for all NVM: .EngDTYesYes












Are the following values correct for all Display Variables: .EngDTYesYes












Are the following values correct for all PIM: .EngDTYesYes












Are the following values correct for all Constants: .EngDTYesYes












Has Static Register evaluation has been completed and updated for any register data that is written to?NANA


























































































































































































































































































































































































































































































































































2
Section 2: ModelAuthor: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Does model include appropriate logic for dealing with missing or corrupted NVM data?NANA












Does design either work with global signal units or contain necessary unit-conversion logic?NANA












Does the design prevent Integrator drifting?NANA












Does design make proper use of limiters to prevent integrator windup and runaway values?NANA












Are all IIR filters free of potential instability over their defined calibration ranges?NANA










































































































































































































































































































































































3

Author: This column is for Self review. Author shall fill Yes/No/NA against each point in checklist. AuthorAuthor: This column is for reviewer. Reviewer shall fill Yes/No/NA against each point in checklist. ReviewerAuthor: Detailed Description of the finding shall be provided by the reviewer. Description of finding by reviewerCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status









Has author performed basic simulations to screen for problems?YesYes










































































































































4

DocumentReferenceSummary of resolutionCorrective Action: What action is taken to fix the issue? Corrective ActionAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







4.1














4.2














4.3














4.4














4.5














4.6














4.7














4.8














4.9














4.10














4.11














4.12














4.13














4.14














4.15














4.16














4.17














4.18














4.19














4.20














4.21














4.22














4.23














4.24














4.25






























Sheet 7: Master

This is the master list of questions.


ADVANCED FILTER CRITERIA

A macro is used to filter and populate separate spreadsheets for each engineering discipline.

ArtifactDomain1Domain2















NumberArtifactChecklist ItemDomain1Domain2



1dictIs Filename of Data Dictionary in correct format?Processnone



2dictIs the FDD.Version property correctly updated?Processnone



3dictAre the following values correct for Runnables: .ContextProcessSoftwareShould be Architect


4dictAre the following values correct for Runnables: .TimeStepProcessAppsShould be Architect


5dictAre the following values correct for SrvRunnables: .ReturnProcessSoftwareShould be Architect


6dictAre the following values correct for SrvRunnables: .ArgumentsProcessSoftwareShould be Architect


7dictAre the following values correct for all Ip/Op/IrvSignals: .EngDTProcessnoneShould be Architect


8dictAre the following values correct for all Ip/Op/IrvSignals: .DocUnitProcessnoneShould be Architect


9dictAre the following values correct for all Ip/Op/IrvSignals: .EngInitProcessnoneShould be Architect


10dictAre the following values correct for all Ip/Op/IrvSignals: .EngMinProcessnoneShould be Architect


11dictAre the following values correct for all Ip/Op/IrvSignals: .EngMaxProcessnoneShould be Architect


12dictAre the following values correct for all Ip/Op/IrvSignals: .ReadIn/WrittenInProcessnone



13dictAre the following values correct for all Ip/Op/IrvSignals: .ReadType/WriteTypeProcessnone



14dictAre the following values correct for all Calibrations: .EngDTSMEnone



15dictAre the following values correct for all Calibrations: .DocUnitAppsProcess



16dictAre the following values correct for all Calibrations: .EngMaxAppsnone



17dictAre the following values correct for all Calibrations: .CardinalityAppsnone



18dictAre the following values correct for all Calibrations: .CustomerVisibleAppsnone



19dictAre the following values correct for all Calibrations: .ImpactAppsSafety



20dictAre the following values correct for all Calibrations: .GraphLinkAppsnone



21dictAre the following values correct for all Calibrations: .MonotonyAppsnone



22dictAre the following values correct for all Calibrations: .PortNameSoftwareProcess



23dictAre the following values correct for all NVM: .EngDTSMEnone



24dictAre the following values correct for all NVM: .DocUnitProcessApps



25dictAre the following values correct for all NVM: .EngInitSoftwarenone



26dictAre the following values correct for all NVM: .AliasSoftwarenone



27dictAre the following values correct for all NVM: .InitRowColSoftwarenone



28dictAre the following values correct for all Display Variables: .EngDTSMEnone



29dictAre the following values correct for all Display Variables: .DocUnitAppsnone



30dictAre the following values correct for all Display Variables: .EngMinSoftwarenone



31dictAre the following values correct for all Display Variables: .EngMaxSoftwarenone



32dictAre the following values correct for all Display Variables: .InitRowColSoftwarenone



33dictAre the following values correct for all PIM: .EngDTSMEnone



34dictAre the following values correct for all PIM: .DocUnitProcessnone



35dictAre the following values correct for all PIM: .EngMinSoftwarenone



36dictAre the following values correct for all PIM: .EngMaxSoftwarenone



37dictAre the following values correct for all PIM: .InitRowColSoftwarenone



38dictAre the following values correct for all Constants: .EngDTSMEnone



39dictAre the following values correct for all Constants: .DocUnitProcessnone



40dictAre the following values correct for all Calibrations: .EngValAppsnone



41dictAre the following values correct for all Calibrations: .EngMinAppsnone



43dictAre the following values correct for all Calibrations: .TuningOwnerSafetyApps



47dictAre the following values correct for all Calibrations: .OnlineSafetyApps



44dictDoes the FDD .DesignASIL property match requirements?Safetynone



45dictDoes FDD Long Name, Short Name, and Description match requirements?AppsProcess



46dictDo output signal ranges match requirements?AppsProcess



42dictAre lookup tables using compatible table dimensions?SafetySoftware



48dictDo signal and parameter names accurately describe their purpose?Appsnone



49dictDo all .Description properties provide useful information?Appsnone



50dictHas Static Register evaluation has been completed and updated for any register data that is written to?SMEnone



51dictAre all clients from model defined in dictionary?ProcessSoftware



52dictDo client definitions match their corresponding server runnable?ProcessSoftware



53dictIs NVM defined in the appropriate number of blocks (separate for EOL vs saved at power-off)?ProcessSoftware



54dictIs NVM with multiple values defined as a structure?ProcessSoftware



55dictAre NVM structure members arranged largest-to-smallest datatype?ProcessSoftware



56dictAre local Constants unique from global constants available in xx999A dictionaries?ProcessSoftware



57dictAre calibration tables named correctly (e.g. AssiX and AssiY)?ProcessApps



58dictAre Constant names abbreviated properly (ALLCAPS are not checkable by tools)?Processnone



59dictIs the Data Dictionary Verification report error free?Processnone



60dictAre all data types represented by released Data_Management classes?Processnone



61modelAre all the Memory Store blocks for PIM and Display Variables located on the 2nd level of model?ProcessSoftware



62modelIs each diagnostic (NTC) capable of being set to "PASS"?ProcessSoftware



63modelDoes non-zero intialization of PIM occur in the function's Init runnable?ProcessSoftware



64modelDoes design properly include Set Ram Block Status when NVM RAM values change?ProcessSoftware



65modelAre NTCs set only outside an IRQ (not related to the typical periodic OS)?ProcessSoftware



66modelAre NTCs set and read only at periodic steps no less than 2 ms?ProcessSoftware



67modelDoes model execute without errors/warnings after loading NxtrMBDConfig configuration set?ProcessApps



68modelIs filename of model in correct format?Processnone



69modelIs Top level of model annotated with Requirements Baseline?Processnone



70modelIs the Top level of the model annotated with Tool Dependencies?Processnone



71modelIs Top level of model annotated with Change Log or History?Processnone



72modelIs the 2nd level of model free from subsystems that are not Function-Call Subsystems?Processnone



73modelIs the 2nd level of model free from arithmetic and logic operations?Processnone



74modelAre the Runnable trigger signals named as "call_<Runnable>"?Processnone



75modelDoes 2nd level of model have a properly updated annotation with name, description, and intended baseline number?Processnone



76modelAre all data flow layers free of Function-Call Subsystems and Memory Store blocks?Processnone



77modelDoes the Model have the confidentiality and copyright information inside all its Subsystems?Processnone



78modelAre all requirements links of the format <FDDNumber>_<ObjectID>?Processnone



79modelDoes requirements HTML report reference only the DOORS module of this component for all links in the design?Processnone



80modelWas Model Advisor run with the correct configuration settings?Processnone



81modelIs the Model Advisor rerport free from "Fails".Processnone



82modelDoes the model execute?Processnone



83modelAre Model Advisor report ISO26262 warnings acceptable?Safetynone



84modelIs model free from dynamic array size allocation?SafetySoftware



85modelDoes model include adequate annotation throughout?Appsnone



86modelIs model free from data type conversion blocks that do not explicitly state desired data type?SafetySoftware



87modelDoes model refrain from using Display Variable values in downstream operations?SafetySoftware



88modelAre all GOTO/FROM blocks restricted in scope to their own subystem level?SafetySoftware



89modelIf model has ADC input, is failure boolean input and appropriate fault response been included?SafetyProcess



90modelDoes design calculate PIM values only within their defined range?Softwarenone



91modelDoes design include output limiting blocks?SoftwareSafety



92modelDo cal ranges & logic ensure freedom from divide-by-zero?SoftwareSafety



93modelDo cal ranges & logic ensure no incompatible values for their datatype?SoftwareProcess



94modelAre Model Advisor report MISRA warnings acceptable?Softwarenone



95modelIs design free of unreachable logic?Softwarenone



96modelDo state machines provide exits of all non-latch states?Softwarenone



97modelIs design free from recursive logic that could cause indefinate waits?Softwarenone



98modelDoes design maintain data size consistency?Softwarenone



99modelAre "magic numbers" acceptable?ProcessSoftware



100modelAre the following values correct for all NTC: .NtcTypAppsSafety



101modelAre display variables appropriately placed?Appsnone



102modelDoes design provide appropriate tuning flexibility?Appsnone



103modelAre blocks linked to the correct requirements? (watch for problems due to copy/pasted blocks)Appsnone



104modelIs the list of unlinked blocks acceptable?Appsnone



105modelDoes design account for all requirements?Appsnone



106modelIs design of a managable size and easy to understand?AppsSoftware



107modelIs design easily disabled via calibration?Appsnone



108modelDoes model include appropriate logic for dealing with missing or corrupted NVM data?SMESafety



109modelDoes design either work with global signal units or contain necessary unit-conversion logic?SMEApps



110modelDoes the design prevent Integrator drifting?SMEnone



111modelDoes design make proper use of limiters to prevent integrator windup and runaway values?SMEnone



112modelAre all IIR filters free of potential instability over their defined calibration ranges?SMEnone



113modelIs Stateflow used only for state machines not easily represented in Simulink?Softwarenone



114modelDo IF..ELSEIF blocks also contain an ELSE condition?Processnone



115modelDo SWITCH CASE blocks also contain a DEFAULT condtion?Processnone



116modelAre ELSE and DEFAULT branching conditions reachable when dependent on internal variables?Processnone



117modelIs model free from over-nested IF logic or redundant IF..ELSEIF..ELSEIF.. Conditions?Softwarenone



118modelIs model free from arithmetic operations on Boolean values?Softwarenone



119modelIs model optimized to minimize redundant calculations?Processnone



120packageDoes NTC Summary sheet adequately describe NTC usage?Appsnone



121packageDoes review meet 'inspection' criteria?SafetyProcess



122packageDoes Design folder contain only the model, data dictionary, and (optionally) a simulation setup script?Processnone



123packageDoes Doc folder contain a zipped HTML webview model?Processnone



124packageWas webview model created without requirements highlighted?Processnone



125packageDoes Doc folder contain appropriate number of NTC Summary sheets?Processnone



126packageDoes Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report?Processnone



127packageHas author performed basic simulations to screen for problems?SMEnone



Sheet 8: Template Change Log

RevChangeAuthor
01.00.05Added lesson learned #3.5MDK
01.00.06Added lesson learned #3.6, 3.7 - Structure and writing of NVM in mfiles and models.MDK
02.00.00Combined ESG and Systems into one, compatible with Data_Management 2.13.0 of CreateDD and VerifyDD.K. Derry
02.01.00Added: Does FDD.DesignASIL match requirements?
Added: Was webview model created without requirements highlighted?
Removed: Redundant row in Data Dictionary section.
Formatting: Column C now consistently center-justified.		K. Derry
02.02.00Added: Are all data types represented by released Data_Management classes?
Removed: Are all runnables defined? Rationale: Automated tools checking.
Removed: Does the Component shortname match data dictionary FDD metadata?
Removed: "Data store name must resolve to Simulink signal object"
Edited: Model Advisor report should now be left unzipped.		K. Derry
3.0.0New concept of discipline-specific checklists.
New sheets for Project Info, Safety, Software, Apps, SME, and Master.
New VBA code to distribute master list onto appropriate discipline sheets.
Major reformatting, many line item checks added/deleted/modified.		K. Derry








































































3 - SF031A_CurrReasbnDiagc_ModelAdvisor_Report

Model Advisor Report for 'SF031A_CurrReasbnDiagc'
Model Advisor Report - SF031A_CurrReasbnDiagc.slx
Simulink version: 8.2Model version: 1.270
System: SF031A_CurrReasbnDiagcCurrent run: 19-Dec-2016 11:15:54
 Model Advisor configuration: ...NxtrModelAdvisorConfig.mat

Run Summary
PassFailWarningNot RunTotal
   48   0   19   133200


By Task

    Code Generation Efficiency

 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
  • Use bitsets for storing state configuration (Stateflow)
  • Use bitsets for storing boolean data (Stateflow)



    •     Frequency Response Estimation

        Managing Data Store Memory Blocks

        Managing Library Links And Variants

        Model Referencing

        Modeling Guidelines for MISRA-C:2004

        Modeling Physical Systems

        Modeling Signals and Parameters using Buses

        Modeling Single-Precision Systems

        Modeling Standards for DO-178C/DO-331

        Modeling Standards for EN 50128

        Modeling Standards for IEC 61508

        Modeling Standards for ISO 26262

     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 TypeCount
    Inport90
    Outport34
    SubSystem66
    Stateflow2


    Simulink

    Block TypeCount
    Inport90
    SubSystem66
    Constant52
    Outport34
    DataStoreWrite26
    Sum25
    Product22
    From18
    DataStoreMemory18
    Goto12
    S-Function10
    ActionPort10
    DataStoreRead9
    Math8
    Terminator4
    If5
    TriggerPort4
    Merge4
    Step4
    EnablePort4
    Abs3
    DataTypeConversion3
    RelationalOperator3
    Logic2
    MinMax1
    UnaryMinus1
    Sqrt1
    ∧ Less


    Stateflow

    Stateflow constructCount
    Stateflow Transitions30
    Stateflow Junctions16
    Stateflow Data10
    Stateflow Charts2


    _________________________________________________________________________________________

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


    Maximum Subsystem Depth: 8

    Subsystem Depth

    Subsystem NameLevelDepth
    CopyRight211
    CurrReasbnDiagc17
    CurrReasbnDiagc/CopyRight221
    CurrReasbnDiagc/CurrReasbnDiagcInit122
    CurrReasbnDiagc/CurrReasbnDiagcInit1/CopyRight231
    CurrReasbnDiagc/CurrReasbnDiagcInit1/MotVltgDaxLpFil31
    CurrReasbnDiagc/CurrReasbnDiagcInit1/MotVltgQaxLpFil31
    CurrReasbnDiagc/CurrReasbnDiagcInit222
    CurrReasbnDiagc/CurrReasbnDiagcInit2/CopyRight231
    CurrReasbnDiagc/CurrReasbnDiagcInit2/DiagVltgLpFil31
    CurrReasbnDiagc/CurrReasbnDiagcInit2/MotVelLpFil31
    CurrReasbnDiagc/CurrReasbnDiagcPer123
    CurrReasbnDiagc/CurrReasbnDiagcPer1/CopyRight231
    CurrReasbnDiagc/CurrReasbnDiagcPer1/FilLpUpdOutp31
    CurrReasbnDiagc/CurrReasbnDiagcPer1/FilLpUpdOutp131
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem32
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem132
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem1/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem232
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem2/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem332
    CurrReasbnDiagc/CurrReasbnDiagcPer1/If Action Subsystem3/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer1/LimStat_f131
    CurrReasbnDiagc/CurrReasbnDiagcPer1/LimStat_f331
    CurrReasbnDiagc/CurrReasbnDiagcPer226
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CopyRight231
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic35
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/Dynamic_Limit41
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem44
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/CopyRight251
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/Enumerated Constant651
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/SetNtcSts_Wo_Trigger53
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/SetNtcSts_Wo_Trigger/SetNtcSts62
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/SetNtcSts_Wo_Trigger/SetNtcSts/CopyRight271
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem/SetNtcSts_Wo_Trigger/SetNtcSts/ISO Fault Debounce Design71
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem144
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/CopyRight251
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/Enumerated Constant651
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/SetNtcSts_Wo_Trigger53
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/SetNtcSts_Wo_Trigger/SetNtcSts62
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/SetNtcSts_Wo_Trigger/SetNtcSts/CopyRight271
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem1/SetNtcSts_Wo_Trigger/SetNtcSts/ISO Fault Debounce Design71
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem242
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem2/CopyRight251
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem2/FilLpUpdOutp51
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem342
    CurrReasbnDiagc/CurrReasbnDiagcPer2/CurrReasbn Diagnostic/If Action Subsystem3/CopyRight251
    CurrReasbnDiagc/CurrReasbnDiagcPer2/If Action Subsystem32
    CurrReasbnDiagc/CurrReasbnDiagcPer2/If Action Subsystem/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer2/If Action Subsystem/FilLpUpdOutp41
    CurrReasbnDiagc/CurrReasbnDiagcPer2/If Action Subsystem132
    CurrReasbnDiagc/CurrReasbnDiagcPer2/If Action Subsystem1/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer2/LimDyn_f3231
    CurrReasbnDiagc/CurrReasbnDiagcPer2/Tustin Filter132
    CurrReasbnDiagc/CurrReasbnDiagcPer2/Tustin Filter1/CopyRight241
    CurrReasbnDiagc/CurrReasbnDiagcPer2/Tustin Filter232
    CurrReasbnDiagc/CurrReasbnDiagcPer2/Tustin Filter2/CopyRight241
    call_CurrReasbnInit111
    call_CurrReasbnInit211
    call_CurrReasbnPer111
    call_CurrReasbnPer211
    ∧ Less


     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
    The following Inport blocks have undefined or inherited sample times, data types or port dimensions

    InportLinkConditions
    1SF031A_CurrReasbnDiagc/MotCtrlMotVltgDaxMissing port dimension
    Missing signal data type
    Missing port sample time
    2SF031A_CurrReasbnDiagc/MotCtrlMotVltgQaxMissing port dimension
    Missing signal data type
    Missing port sample time
    3SF031A_CurrReasbnDiagc/MotVltgQaxFildMissing port dimension
    Missing signal data type
    Missing port sample time
    4SF031A_CurrReasbnDiagc/MotVltgDaxFildMissing port dimension
    Missing signal data type
    Missing port sample time
    5SF031A_CurrReasbnDiagc/MotAgElecMissing port dimension
    Missing signal data type
    Missing port sample time
    6SF031A_CurrReasbnDiagc/MotVltgQaxFfStatMissing port dimension
    Missing signal data type
    Missing port sample time
    7SF031A_CurrReasbnDiagc/MotVltgDaxFfStatMissing port dimension
    Missing signal data type
    Missing port sample time
    8SF031A_CurrReasbnDiagc/MotVelMrfMissing port dimension
    Missing signal data type
    Missing port sample time
    9SF031A_CurrReasbnDiagc/MotTqCmdLimrMinMissing port dimension
    Missing signal data type
    Missing port sample time
    10SF031A_CurrReasbnDiagc/SysMotTqCmdScaMissing port dimension
    Missing signal data type
    Missing port sample time


    Recommended Action
    Explicitly define all missing Inport block properties identified in the results
    • Missing port dimension: Model contains Inport blocks with inherited port dimension (-1). Specify port dimension for the listed Inport blocks.
    • Missing signal data type: Model contains Inport blocks with inherited data type. Specify a data type for the listed Inport blocks.
    • Missing port sample time: Model contains Inport blocks with inherited sample time (-1). Specify sample time information for the listed Inport blocks. Note: The sample time of root Inports with bus type must match the sample times specified at the leaf elements of the bus object.

     Check state machine type of Stateflow charts

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

    Check for Classic state machines
    Identify Stateflow charts using the Classic state machine type.

    Warning
    The following charts using Classic state machines were found in the model:

    Recommended Action
    For each chart listed above, in the Chart Properties dialog box, specify State Machine Type to either Mealy or Moore. Use the same state machine type for all charts in the model.
    _________________________________________________________________________________________

    Check for Mealy state machines
    Identify Stateflow charts using the Mealy state machine type.

    Passed
    No charts using Mealy state machines were found in the model.
    _________________________________________________________________________________________

    Check for Moore state machines
    Identify Stateflow charts using the Moore state machine type.

    Passed
    No charts using Moore state machines were found in the model.

    Input Parameters Selection
    NameValue
    State Machine TypeCommon

     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.



        Modeling Standards for MAAB

            Naming Conventions

     Check subsystem names

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

    See Also

    Warning
    The following subsystem names contain incorrect characters:

    ErrorSubsystem block
    Name contains incorrect characters...../CurrReasbnDiagcPer1/If Action Subsystem
    Name contains incorrect characters...../CurrReasbnDiagcPer1/If Action Subsystem1
    Name contains incorrect characters...../CurrReasbnDiagcPer1/If Action Subsystem2
    Name contains incorrect characters...../CurrReasbnDiagcPer1/If Action Subsystem3
    Name contains incorrect characters...../If Action Subsystem
    Name contains incorrect characters...../If Action Subsystem1
    Name contains incorrect characters...../If Action Subsystem2
    Name contains incorrect characters...../If Action Subsystem3
    Name contains incorrect characters...../CurrReasbnDiagcPer2/If Action Subsystem
    Name contains incorrect characters...../CurrReasbnDiagcPer2/If Action Subsystem1


    Recommended Action
    Rename the subsystem blocks using correct characters.

     Check character usage in block names

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

    See Also

    Warning
    The following block names use characters that are not correct for C code:

    Error typeBlock
    Name contains incorrect characters...../Function-Call Generator
    Name contains incorrect characters...../Function-Call Generator
    Name contains incorrect characters...../Function-Call Generator
    Name contains incorrect characters...../Function-Call Generator


    Recommended Action
    Rename the block using correct characters.



            Model Architecture

     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

    Warning
    The following level(s) in the model include basic blocks and subsystems:

    SystemBlock path
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/CopyRight2
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/Data Store Read
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/Step
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/Step1
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/Step2
    SF031A_CurrReasbnDiagcSF031A_CurrReasbnDiagc/Step3
    SF031A_CurrReasbnDiagc/CurrReasbnDiagc..../CurrReasbnDiagc/CopyRight2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/CopyRight2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/FilLpUpdOutp
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/FilLpUpdOutp1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/LimStat_f1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/LimStat_f3
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer1..../CurrReasbnDiagcPer1/k_MtrVel_Offset1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Abs
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Add
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Add1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Add2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Add3
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagc/CurrReasbnDiagcPer2/Add4
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant10
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant3
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant4
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Constant9
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/CopyRight2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Cos_f32
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write3
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write4
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write5
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Data Store Write6
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/LimDyn_f32
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Math Function
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Math Function1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product1
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product14
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product2
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product5
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product6
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product7
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Product8
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Sin_f32
    ..../CurrReasbnDiagc/CurrReasbnDiagcPer2..../CurrReasbnDiagcPer2/Sqrt1
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Abs
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Abs2
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant1
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant10
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant2
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant4
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant8
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Constant9
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/CopyRight2
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Data Store Write1
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Data Store Write5
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Dynamic_Limit
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Logical Operator2
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Logical Operator4
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/MinMax
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Product
    ..../CurrReasbn Diagnostic..../Relational Operator
    ..../CurrReasbn Diagnostic..../Relational Operator2
    ..../CurrReasbn Diagnostic..../Relational Operator4
    ..../CurrReasbn Diagnostic..../CurrReasbn Diagnostic/Unary Minus1
    ∧ Less


    Recommended Action
    If possible, replace blocks at the identified level of the model hierarchy with basic blocks. Move nonvirtual blocks into the identified subsystem.



            Model Configuration Options

     Check model diagnostic parameters

    Identify diagnostic parameters that are set to none.

    See Also

    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.



            Simulink

     Check for Simulink diagrams using nonstandard display attributes

    Identify nonstandard display attributes in Simulink diagrams.

    See Also

    _________________________________________________________________________________________

    Check format settings
    Identify incorrect model-level format options.

    Warning
    The following format display options are incorrect.

    Display AttributeRecommended ValueActual Value
    Display > Signals & Ports > Wide Nonscalar Linesonoff
    Display > Library Links > Allnonedisabled


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

    Check block colors
    Identify blocks using nonstandard colors.

    Warning
    The following blocks use nonstandard colors:

    ∧ Less
    Recommended Action
    Set the block foreground color to black and the background color to white.
    _________________________________________________________________________________________

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

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

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

     Check font formatting

    Identify inconsistent formatting of text.

    See Also

    Warning
    Font formatting is not consistent.

    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 NameFont SizeFont Style

    Helvetica
    Arial

    10
    14

    normal



    Recommended Action
    To have consistent font formatting, click Modify All Fonts to apply the font formatting selected in the input parameters above to all objects.

    Input Parameters Selection
    NameValue
    Font NameCommon
    Font SizeCommon
    Font StyleCommon

     Check positioning and configuration of ports

    Identify input and output ports with incorrect positioning and configurations.

    See Also

    _________________________________________________________________________________________

    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

    _________________________________________________________________________________________

    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
    NameValue
    Display all port names (Diagram > Format > Show Block Name).true

     Check the display attributes of block names

    Identify whether to display block names.

    See Also

    _________________________________________________________________________________________

    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:

    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.

    Warning
    The following blocks have descriptive names, however, the names are hidden:

    ∧ Less
    Recommended Action
    Modify the blocks to show the block name (Diagram > Format > Show Block Name).

     Check signal line labels

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

    See Also

    _________________________________________________________________________________________

    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

    _________________________________________________________________________________________

    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.



            Stateflow

     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

    _________________________________________________________________________________________

    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

    _________________________________________________________________________________________

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

    Warning
    The following transitions have condition expressions that are not horizontal:

    Recommended Action
    Draw condition transitions horizontally.
    _________________________________________________________________________________________

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

    Warning
    The following transitions have action expressions that are not vertical:

    Recommended Action
    Draw action transitions vertically.
    _________________________________________________________________________________________

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

    Warning
    The following Junctions do not have a default exit transition:

    Recommended Action
    Consider reorganizing the flow chart to add a default transition.
    _________________________________________________________________________________________

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

    Warning
    The following transition have a mixture of condition and assignment actions:

    Recommended Action
    Separate the conditional action from the assignment action.

     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

    _________________________________________________________________________________________

    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.

    Passed
    The default states are in the correct position.
    _________________________________________________________________________________________

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

    Passed
    All default transitions connect to the top of the state.
    _________________________________________________________________________________________

    Identify states with multiple default transitions.

    Passed
    All states have only one default transition.



            MATLAB Functions

        Requirements Consistency Checking

        Simulation Accuracy

        Simulation Runtime Accuracy Diagnostics

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

    Note: These runtime diagnostics may slow down simulation considerably. You should set them back to Disable all once you have verified that they do not cause any warnings or errors during simulation.



        Simulink Model File Integrity

        Upgrading to the Current Simulink Version