1 - SF040A_MotVel_Design_PeerReviewChkList

Nexteer_Template_V1.0

Overview

Peer Review Instructions
Technical Review Checklist
Template Change Log


Sheet 1: Peer Review Instructions

Instructions for Functional Design Package Peer Review




PRE-MEETING


Function OwnerConfirm that requirements are reviewed and approved PRIOR to the FDP peer review

Function OwnerStart with latest version of the template for any "first reviews" - Continue to use existing temmplate for re-reviews

Function OwnerProvide the functional design package (changed documents) to the invited attendees 1-2 working days in advance of review

Function OwnerNotify the assigned peer reviewer and make sure they are prepared to do their function in the meeting

Function OwnerIdentify necessary attendance and invite to meeting

Function OwnerComplete the "Author" column information for sections 1 through 5 prior to the review

Function OwnerComplete the attendance invitation list in section 7

Function OwnerFor Re-reviews only: Complete the column "remarks by author" to identify actions taken to address items found in earlier reviews.



DURING MEETING


Function OwnerPresent document changes to the review team

Peer ReviewerCapture attendance of the review

Peer ReviewerCapture actions and issues in section 6. Identify issue summary, Document type, Reference (Requirement ID, section number, etc), Defect Type and indicate status as "OPEN"



POST MEETING


Function OwnerFollow up on all "open" items. Update "Summary of Resolution" to indicate what was done or decided.

Function OwnerSchedule follow up review OR review open items with peer reviewer and obtain agreement to close

Peer ReviewerClose change request in system and confirm all associated tasks are complete. Upload peer review checklist (this document) with any FDP updates

Sheet 2: Technical Review Checklist

Technical Review Checklist - Template Version 02.02.00







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function IDSF040A MotVel

Added "uint16" data type conversion block and moved the position of the "single" data type conversion block to match the code in SumAg SqurdSum subsystem.Requirement0




NoRejectedFDD
Long NameMotor Velocity

Interface0




NAOpenModel
Version that you started from. NOT the version you hope to release. If this will be v1.0.0, enter NA. Starting Baseline1.4.0EffortDesign0






FMEA
AuthorFei YuanReview Effort(Hrs.)
Standards0






*.m File


Corr+Verf effort(Hrs.)
Documentation0






Cal Process


Total Effort (Hrs.)0.00Others0













Total0







Checklist No.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 reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status







1Section 1: Data Dictionary














Is Filename of Data Dictionary in correct format?Yes













Is the FDD.Version property correctly updated?Yes













Is the Data Dictionary Verification report error free?No


6 I/O signal names and 1 PIM name causes the errors. They are acceptable.Closed








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













Are all runnables defined?Yes













Do runnables have the correct time step?Yes













Do server runnables correctly define arguments?NA













Are all clients defined?NA













Do client definitions match the corresponding server runnable?Yes













Does name and metadata of every signal match its corresponding interface signal?Yes













Do output signal ranges match requirements (check DOOR min/max attributes too)?Yes













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













Are all data types represented by released Data_Management classes?Yes













Do all calibrations have correct values for all metadata?NA













Is NVM defined in the appropriate number of blocks?Yes













Are constants defined with proper scope (local vs global)?Yes













Are all dependent constants and calibrations included in one file?Yes













Does FDD.DesignASIL match requirements?





























2Section 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 reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








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>"?Yes













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













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













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













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




























3Section 3: Requirements LinkingAuthor: 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 reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








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













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













Is the list of unlinked blocks acceptable?Yes




























4Section 4: Model AdvisorAuthor: 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 reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








Was Model Advisor run with the correct configuration settings?Yes













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













Are Model Advisor report "Warnings" acceptable?Yes




























5Section 5: 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 reviewerAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: Data in this column shall be filled by reviewer after checking whether the rework is completed. Status








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 Reports folder contain only the data dictionary verification report, Model Advisor report, and zipped requirements traceability report?Yes




























4Section 6: Other Issus/Actions IdentifiedDocumentReferenceSummary of resolutionAuthor: Defect type to be selected. Defect TypeAuthor: What action is taken to fix the comment & other remarks need to be filled by author. Remarks By AuthorAuthor: 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














5Section 7: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*Prerit Pramod9/15/2016












Peer Reviewer*<Name>












Safety<Name - if invited>












SoftwareChaitanya Gare












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleThird Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleFourth Review (if required)DateAttendanceApproval?










Function Owner*<Owner Name>













Peer Reviewer*<Name>












Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSE<Name - if invited>












Hardware<Name - if invited>












Test<Name - if invited>












RoleAdd more if necessaryDateAttendanceApproval?










































P.S.:Yes indicates adherence














No indicates non-adherence, reviewer shall provide suitable comments at the end of this document for each point.














NA indicates not applicable














Sheet 3: 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











































































2 - SF040A_MotVel_ModelAdvisor_Report

Model Advisor Report for 'SF040A_MotVel'
Model Advisor Report - SF040A_MotVel.slx
Simulink version: 8.2Model version: 1.145
System: SF040A_MotVelCurrent run: 19-Sep-2016 16:00:49
 Model Advisor configuration: ...NxtrModelAdvisorConfig.mat

Run Summary
PassFailWarningNot RunTotal
   50   0   17   292359


Model Advisor

    By Product

        Simulink

        Simulink Coder


        Embedded Coder


        Simscape


        Simulink Verification and Validation

            Modeling Standards

                DO-178C/DO-331 Checks


                IEC 61508, ISO 26262, and EN 50128 Checks


                MathWorks Automotive Advisory Board Checks


            Requirements Consistency


        Simulink Control Design


    By Task

        Code Generation Efficiency


 Check optimization settings

You should turn on the following optimization(s):

  • Block reduction
  • Remove code from floating-point to integer conversions that wraps out-of-range values
  • Inline invariant signals
  • The Simulation range checking diagnostic is enabled. Because this diagnostic can increase the time it takes to simulate your model, you should consider turning it off, by setting its value to none.
  • Ignore testpoints when generating code
  • Pass reusable subsystem outputs as individual arguments



  •         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
    Inport55
    Outport38
    SubSystem41


    Simulink

    Block TypeCount
    Inport55
    SubSystem41
    Outport38
    Constant35
    DataStoreWrite14
    DataTypeConversion13
    Sum12
    DataStoreMemory11
    S-Function11
    Product10
    DataStoreRead9
    ActionPort8
    From8
    Goto6
    Selector5
    If4
    Merge4
    Math4
    TriggerPort3
    RelationalOperator3
    Assignment2
    ForIterator2
    Concatenate2
    UnaryMinus1
    ∧ Less

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


    Maximum Subsystem Depth: 8

    Subsystem Depth

    Subsystem NameLevelDepth
    CopyRight211
    MotVel17
    MotVel/CopyRight221
    MotVel/MotVelInit122
    MotVel/MotVelInit1/CopyRight231
    MotVel/MotVelPer124
    MotVel/MotVelPer1/CopyRight231
    MotVel/MotVelPer1/Indexing Counter33
    MotVel/MotVelPer1/Indexing Counter/CopyRight241
    MotVel/MotVelPer1/Indexing Counter/MotCtrlMotAgBufIdxReset42
    MotVel/MotVelPer1/Indexing Counter/MotCtrlMotAgBufIdxReset/Copyright151
    MotVel/MotVelPer1/Indexing Counter/MotCtrlMotAgBufIdxSet42
    MotVel/MotVelPer1/Indexing Counter/MotCtrlMotAgBufIdxSet/Copyright151
    MotVel/MotVelPer226
    MotVel/MotVelPer2/CopyRight231
    MotVel/MotVelPer2/MtrVelHwVelCRFCalc32
    MotVel/MotVelPer2/MtrVelHwVelCRFCalc/CopyRight241
    MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Limit_HwVel41
    MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Limit_MotVelColRefFrm41
    MotVel/MotVelPer2/MtrVelMRFCalc35
    MotVel/MotVelPer2/MtrVelMRFCalc/CopyRight241
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc44
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/CopyRight251
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/LimStat_f3251
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision152
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision1/CopyRight261
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision252
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision2/CopyRight261
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision152
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision1/CopyRight261
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision252
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision2/CopyRight261
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum53
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/CopyRight261
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/FixdToFloat_f32_u1661
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision162
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision1/CopyRight271
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision262
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision2/CopyRight271
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt52
    MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/CopyRight261
    ∧ 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
    1SF040A_MotVel/MotCtrlMotAgMeclMissing port dimension
    Missing signal data type
    Missing port sample time
    2SF040A_MotVel/MotCtrlMotAgMeasTiMissing port dimension
    Missing signal data type
    Missing port sample time
    3SF040A_MotVel/AssiMechPolarityMissing port dimension
    Missing signal data type
    Missing port sample time
    4SF040A_MotVel/MotAgBufMissing port dimension
    Missing signal data type
    Missing port sample time
    5SF040A_MotVel/MotAgTiBufMissing port dimension
    Missing signal data type
    Missing port sample time
    6SF040A_MotVel/MotAgBufIdxMissing port dimension
    Missing signal data type
    Missing port sample time
    7SF040A_MotVel/MotCtrlMotAgBuf_SigInMissing signal data type
    Missing port sample time
    8SF040A_MotVel/MotCtrlMotAgTiBuf_SigInMissing 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 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 folder names

    Identify folders using incorrect characters and formatting.

    See Also

    Warning
    The following folders have incorrect names:

    FolderIncorrect Character or Format
    C:/Users/bzhf94/Google Drive/Active/Test/EA4/SF040A_MotVel_Design/DesignFolder name includes incorrect characters or formatting.


    Recommended Action
    Rename the above folders to remove incorrect characters and formatting.


     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...../MtrVelMRFCalc/SumAg SqurdSum


    Recommended Action
    Rename the subsystem blocks using 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

    Warning
    The following Inport and Outport block names contain incorrect characters:

    ErrorIncorrect port block
    Name contains incorrect characters...../MotVelPer2/MtrVelMRFCalc/MotAgBuf
    Name contains incorrect characters...../MtrVelMRFCalc/MtrVelMRFCalc/MotAgBuf


    Recommended Action
    Rename the Inport or Outport blocks to use 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
    SF040A_MotVelSF040A_MotVel/CopyRight2
    SF040A_MotVel/MotVelSF040A_MotVel/MotVel/CopyRight2
    SF040A_MotVel/MotVel/MotVelPer1..../MotVel/MotVelPer1/Assignment
    SF040A_MotVel/MotVel/MotVelPer1..../MotVel/MotVelPer1/Assignment1
    SF040A_MotVel/MotVel/MotVelPer1..../MotVel/MotVelPer1/CopyRight2
    ..../MotVel/MotVelPer1/Indexing Counter..../Indexing Counter/BUFSIZE_CNT_U08
    ..../MotVel/MotVelPer1/Indexing Counter..../Indexing Counter/CntrPrev_Read
    ..../MotVel/MotVelPer1/Indexing Counter..../Indexing Counter/CntrPrev_Write
    ..../MotVel/MotVelPer1/Indexing Counter..../MotVelPer1/Indexing Counter/CopyRight2
    ..../MotVel/MotVelPer1/Indexing Counter..../MotVel/MotVelPer1/Indexing Counter/One
    ..../MotVel/MotVelPer1/Indexing Counter..../MotVel/MotVelPer1/Indexing Counter/Sum
    SF040A_MotVel/MotVel/MotVelPer2..../MotVel/MotVelPer2/CopyRight2
    ..../MotVel/MotVelPer2/MtrVelMRFCalc..../MotVelPer2/MtrVelMRFCalc/CopyRight2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/Add
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/Add1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Bitwise Operator1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Bitwise Operator2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/Constant1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/CopyRight2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Read
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Read1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Read2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Write
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Write1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Data Store Write2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/LimStat_f32
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MotVelIninCntr
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays10
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays11
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays4
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays5
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays6
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays7
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays8
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Number of Delays9
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/MtrVelMRFCalc/Product2
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Relational Operator
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Relational Operator1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/SqdSumTiStampPrev_Write
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/SumAgTiMotRevSecPrev_Write
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/SumTiStampBufStPrev_Write1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Vector Concatenate
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/Vector Concatenate1
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/dMotVelAvrgTi
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/dMotVelMotAgRef
    ..../MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc..../MtrVelMRFCalc/dMotVelMotAgRef1
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/ARCHGLBPRM_2PI_ULS_F1
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/ARCHGLBPRM_2PI_ULS_F32
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Add1
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Add2
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Add3
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Add4
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Add5
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/Bitwise Operator1
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/CopyRight2
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Divide
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/FixdToFloat_f32_u16
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/For Iterator
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/Math Function
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/Number of Delays3
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/Number of Delays7
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Product
    ..../MtrVelMRFCalc/SumAg SqurdSum..../MtrVelMRFCalc/SumAg SqurdSum/Product1
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/Relational Operator
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/SqdSumTiStampPrev_Read
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/SqdSumTiStampPrev_Write
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAg SqurdSum/SumAgTiMotRevSecPrev_Read
    ..../MtrVelMRFCalc/SumAg SqurdSum..../SumAgTiMotRevSecPrev_Write
    ∧ 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

                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 > Signals & Ports > Signal Dimensionsoffon
    View > Model Browser Options > Model Browseroffon
    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:

    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
    12

    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.

    Passed
    All displayed names provide descriptive information.
    _________________________________________________________________________________________

    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 signals
    Identify inputs to subsystem blocks to ensure that propagated signals are displayed.

    Warning
    The following subsystem-level Inport block signals have no propagated signal labels. Signals coming from parent system should have a label.

    Recommended Action
    Display signal labels for propagated signals on the inputs signals.
    _________________________________________________________________________________________

    Check subsystem output label propagation
    Identify outputs from subsystem blocks where propagated signals are not displayed.

    Warning
    The following subsystem-level Outport block signals have no propagated signal label. Signals coming from the subsystem should have a label.

    Recommended Action
    Display signal labels for propagated signals on the output 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.

    Passed
    All conditions expressions were drawn horizontally.
    _________________________________________________________________________________________

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

    Passed
    All transitions actions where 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 where found in the chart.



                MATLAB Functions


            Requirements Consistency Checking


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

    Inconsistencies:

    The following selection-based links have descriptions that differ from their corresponding selections in the requirements documents. If this reflects a change in the requirements document, click Update to replace the current description in the selection-based link with the text from the requirements document (the external description).
     
    Block 

    Current description External description  

    SF040A_MotVel/MotVel/call_MotVelPer1

    REQ: SF040A_100REQ:SF040A_100

    Update

    SF040A_MotVel/MotVel/call_MotVelPer2

    REQ: SF040A_101REQ:SF040A_101

    Update

    SF040A_MotVel/MotVel/MotCtrlMotAgMecl

    REQ: SF040A_9REQ:SF040A_9

    Update

    SF040A_MotVel/MotVel/MotCtrlMotAgMeasTi

    REQ: SF040A_32REQ:SF040A_32

    Update

    SF040A_MotVel/MotVel/AssiMechPolarity

    REQ: SF040A_67REQ:SF040A_67

    Update

    SF040A_MotVel/MotVel/MotAgBuf

    REQ: SF040A_37REQ:SF040A_37

    Update

    SF040A_MotVel/MotVel/MotAgTiBuf

    REQ: SF040A_38REQ:SF040A_38

    Update

    SF040A_MotVel/MotVel/MotAgBufIdx

    REQ: SF040A_68REQ:SF040A_68

    Update

    SF040A_MotVel/MotVel/MotVelMrf

    REQ: SF040A_43REQ:SF040A_43

    Update

    SF040A_MotVel/MotVel/HwVel

    REQ: SF040A_45REQ:SF040A_45

    Update

    SF040A_MotVel/MotVel/MotVelCrf

    REQ: SF040A_44REQ:SF040A_44

    Update

    SF040A_MotVel/MotVel/MotCtrlMotAgBuf_SigOut

    REQ: SF040A_11REQ:SF040A_11

    Update

    SF040A_MotVel/MotVel/MotCtrlMotAgTiBuf_SigOut

    REQ: SF040A_39REQ:SF040A_39

    Update

    SF040A_MotVel/MotVel/MotCtrlMotAgBufIdx

    REQ: SF040A_40REQ:SF040A_40

    Update

    SF040A_MotVel/MotVel/MotVelPer1/Assignment

    REQ: SF040A_75REQ:SF040A_75

    Update

    SF040A_MotVel/MotVel/MotVelPer1/Assignment1

    REQ: SF040A_77REQ:SF040A_77

    Update

    SF040A_MotVel/MotVel/MotVelPer1/Indexing Counter

    REQ: SF040A_76REQ:SF040A_76

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Divide

    REQ: SF040A_88REQ:SF040A_88

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Divide1

    REQ: SF040A_90REQ:SF040A_90

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Limit_HwVel

    REQ: SF040A_92REQ:SF040A_92

    Update
    REQ: SF040A_94REQ:SF040A_94

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelHwVelCRFCalc/Limit_MotVelColRefFrm

    REQ: SF040A_89REQ:SF040A_89

    Update
    REQ: SF040A_93REQ:SF040A_93

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Add

    REQ: SF040A_102REQ:SF040A_102

    Update
    REQ: SF040A_104REQ:SF040A_104

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Add1

    REQ: SF040A_102REQ:SF040A_102

    Update
    REQ: SF040A_104REQ:SF040A_104

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Bitwise Operator1

    REQ: SF040A_104REQ:SF040A_104

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Bitwise Operator2

    REQ: SF040A_102REQ:SF040A_102

    Update
    REQ: SF040A_104REQ:SF040A_104

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/If

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/If1

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/LimStat_f32

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Merge

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Merge1

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision1

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMotRefFrmDecision2

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision1

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/MotVelMrfDecision2

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Relational Operator

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Relational Operator1

    REQ: SF040A_111REQ:SF040A_111

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Selector

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/Selector1

    REQ: SF040A_104REQ:SF040A_104

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt

    REQ: SF040A_103REQ:SF040A_103

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/ARCHGLBPRM_2PI_ULS_F1

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Add1

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Add2

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Add3

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Add4

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Add5

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Bitwise Operator1

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Divide

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/For Iterator

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/If

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Math Function

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Merge

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision1

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/MotAg1Decision2

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Product

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Product1

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Relational Operator

    REQ: SF040A_102REQ:SF040A_102

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Selector1

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumAg SqurdSum/Selector2

    REQ: SF040A_105REQ:SF040A_105

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/Add

    REQ: SF040A_103REQ:SF040A_103

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/Add1

    REQ: SF040A_103REQ:SF040A_103

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/Bitwise Operator2

    REQ: SF040A_103REQ:SF040A_103

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/For Iterator

    REQ: SF040A_103REQ:SF040A_103

    Update

    SF040A_MotVel/MotVel/MotVelPer2/MtrVelMRFCalc/MtrVelMRFCalc/SumTiStampBufSt/Selector1

    REQ: SF040A_103REQ:SF040A_103

    Update


            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