1 - EA4 NTC 0x0A1 Kinematic Integrity Fault

Slide 1

NTC Overview
NTC 0x0A1  Kinematic Integrity Fault

Description:


This diagnostic is responsible for detecting  a condition of failed mechanical integrity between the input shaft and output shaft, where the motor coupling may have broken free from the assist mechanism and the motor starts spinning freely.  

Diagnostic Overview:

  • This diagnostic monitors cumulative motor position (scaled to hw deg) and if this hw position exceeds a calibratable threshold ~ (maximum rack travel + tolerance), the NTC is set. 

  • This is not a recoverable fault.
     

Typical Fault Response:  F3 fault type.

  • Since motor is free spinning, the hand wheel position is not known for those systems that use motor position to help with Handwheel angle calculations.  In such cases Handwheel angle dependent functions need to be disabled.  
     

Probable Sources
(Most to Least Probable):

    • Motor Rotations not constrained mechanically 

      • Not connected to a R & P gear 

      • Mechanical failure 

Initialization

 

Periodic

X

Event

 

Date

Revision

Initials

06-13-16

Initial Release

SS

   
   
   
   
   
   
   
   
   

Description of Unusual Event setting NTC

Root Cause / Explanation

  
  
  

Date

FDD & Rev

Modifications to Diagnostic Function

06-13-16

SF045A, V2.0.0

Initial release

   
   
   

Algorithm Changes / Lessons Learned / Revision Log

2 - EA4 NTC 0x0A6 Handwheel Angle to Motor Angle Correlation

Slide 1

NTC Overview
NTC 0x0A6 Hw Angle to Motor Angle Correlation

Description:

  • This diagnostic is in place primarily to detect a correlation error between motor position and Handwheel position derived from a Handwheel angle sensor. 

Diagnostic Overview:

  • The diagnostic compares the Handwheel angle with the cumulative motor position scaled to Handwheel degrees. 

  • If the difference exceeds a calibratable threshold for a duration of time, then the NTC is set.  An error accumulator strategy is used to set the NTC.  

  • The diagnostic as designed will apply only for those systems that have an absolute position sensor. 

  • This diagnostic is executed only if the motor position and Handwheel angle sensor signals are valid, and the Handwheel position sensor has been trimmed. 

Typical Fault Response:  F3 Notification Only

  • The fault response will stop providing Handwheel position to dependent functions for the duration of the fault.   

Probable Sources
(Most to Least Probable):

  • System without travel stops and non-contacting sensor roll-over 

  • Sensor – Electrical connection – open/short 

  • Control module – Signal Open / Short - Failed external component or solder connection (resistor or capacitor) 

  • Broken motor coupling/belt 

Initialization

 

Periodic

X

Event

 

Date

Revision

Initials

06-13-16

Initial Release

SS

   
   
   
   
   
   
   
   
   

Description of Unusual Event setting NTC

Root Cause / Explanation

  
  
  

Date

FDD & Rev

Modifications to Diagnostic Function

06-13-16

SF045A, V2.0.0

Initial release

   
   
   

Algorithm Changes / Lessons Learned / Revision Log

3 - SF045A_HwAgSysArbn_Peer Review Checklist Design

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 3 prior to the review

Function OwnerComplete the attendance invitation list in section 5

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 4. 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.00.00







Product NameElectric Power SteeringElectrical Arch.4Review ScopeDefect TypeNumbers




YesClosedFR
Function IDSF045A_HwAgSysArbn

Generic design is now simplfied considering only Pinion coordinates to arbitrate the HwAg signals instead of flexibility to choose between Handwheel, Pinion and MotorAg coordinates. This resulted in removing the cals used to apply compilance error compensation and priority selection.
- Kinematic Integrity diagonstic added
- HwAg to MotAg Correlation diagonstic added
- Logic added to arbitrate HwAg signal going to EOT when HwAg sensor signals not available.
Requirement0




NoRejectedFDD
Long NameLoa Manager

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.1.0EffortDesign8






FMEA
AuthorSudeep ShankarReview Effort(Hrs.)
Standards2






*.m File


Corr+Verf effort(Hrs.)
Documentation4






Cal Process


Total Effort (Hrs.)0.00Others1













Total15







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
Special cases are shown as errorOthersTools issueClosed








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
No Server runnables











Are all clients defined?Yes













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)?NA
No cal tables











Do all calibrations have correct values for all metadata?Yes













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











Is NVM defined in the appropriate number of blocks?NA
No NVM defined











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













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




























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













Does the Component shortname match data dictionary FDD metadata?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













Do all Memory Store blocks for PIM and Display Variables have the "Data store name must resolve to Simulink signal object" setting checked to true?Yes













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













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













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











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


No baseline requirements









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













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













Is the list of unlinked blocks acceptable?NA




























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













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


No requirement traceability report
























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







6.1Change the order of inputs fed to PeriodicModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1Changed the input orderDocumentationImplementedClosed







6.2HwAgSnsrls can be removed from If and Else block as in both blocks it is just a pass throughModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsDataUpdated as per commentDesignImplementedClosed







6.3Change the name of the HwAgSysArbnHwAgSnsrlsThd to a meaningful name representing Kinematic in the name.ModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsDataName changedDocumentationImplementedClosed







6.4Latch the confidence to 0 when Kinematic integrity fault is set to TRUE.ModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/VldtSnsrlsDataFault latchedDesignImplementedClosed







6.5Change the design to compare sensor and sensorless confidence signals against correlation confidence thershold cals to determine whether to perform correlation check. And also simplify the design to select between sensor and sensorless signalModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSelnDesign in simplifiedDesignImplementedClosed







6.6Simplify the correlation logic. Substract one signal from another and take the absolute value of it.ModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrlnUpdated as per commentDesignImplementedClosed







6.7Store the flag to a PIM to indicate whether correlation is true or notModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrln/SetNtcPassPIM updatedDesignImplementedClosed







6.8Set the NTC to "Prepass" instead of "Pass" when Correlation is true with debounce stepModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/VrfyHwAgCorrln/SetNtcPassNTC state updatedDesignImplementedClosed







6.9NtcNr1.NTCNR_0X0A6 NTC definition in data dictionary must indicate that the NTC uses debounce step*.m File
Changed in DDStandardsImplementedClosed







6.10Change the block name "DftCal" to a meaningful nameModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChgchange the name to be more meaningfulDocumentationImplementedClosed







6.11Move Reference timer and calibrations inside block. ( If, else and other) blockModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChgMoved the calibrations inside the blocksStandardsImplementedClosed







6.12Port name "Tmr" to the "ApplyRateLim" block to be updated to more meaningful name so that design is readable.ModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/TestHwAgSrcChgchange the name to be more meaningfulDocumentationImplementedClosed







6.13Add Correlation Status flag to else and elseif logicModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSelnAdded correlation flag after simplifying the designDesignImplementedClosed







6.14Add a cal to to restrict the duration of sensorless HwAg signal to be transmitted on Serial Com sincel last correlated also set the calibration to duration equivalent to one dayModelSF045A_HwAgSysArbn/HwAgSysArbn/HwAgSysArbnPer1/HwAgArbn/HwAgSrcSeln/SnsrlsDataToSerlComupdated design to add timer logicDesignImplementedClosed







6.15














6.16














6.17














6.18














6.19














6.20














6.21














6.22














6.23














6.24














6.25














7Section 7: APPROVALS













RoleFirst ReviewDateAttendanceApproval?










Function Owner*Sudeep Shankar6/13/2016Yes











Peer Reviewer*Kevin DerryYesNo










SafetyCarl TarumNo











SoftwareSpandana BalaniYes











ESG / Systems<Name - if invited>












EPDT / CSEMatthew TompkinsYesNo










Hardware<Name - if invited>












Test<Name - if invited>












RoleSecond Review (if required)DateAttendanceApproval?










Function Owner*<Name - if invited>6/15/2016












Peer Reviewer*Kevin DerryYesYes










Safety<Name - if invited>












Software<Name - if invited>












ESG / Systems<Name - if invited>












EPDT / CSEMatthew TompkinsYes











Hardware<Name - if invited>












Test<Name - if invited>












RoleThird Review (if required)DateAttendanceApproval?










Function Owner*<Name - if invited>













Peer Reviewer*<Name - if invited>












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