新能源汽車整車控制器系統(tǒng)診斷規(guī)范

新能源汽車整車控制器系統(tǒng)診斷規(guī)范—“EV160”文件編號：“EV14”編制校對::審核：“業(yè)務(wù)高級經(jīng)理”會簽：“控制系統(tǒng)集成主管”批準(zhǔn)：“部長”XXX年XXX月版本信息2003Part2:High-speedmediumaccessunit2007Part5:High-speedmediumaccessunitwithlow-powermode2004Part2:NetworkingLayerServices2004Part3:ApplicationLayerServices[6]ISO14229-1:RoadVehicle-DiagnosticSystemsDiagnostic2006ServicesSpecification[7]ISO15031-6:Roadvehicles-Communicationbetweenvehicleand2005externalequipmentforemission-relatedPart6:Diagnostictroublecodedefinitions“由網(wǎng)絡(luò)工程師統(tǒng)一發(fā)布網(wǎng)絡(luò)拓?fù)洹盕ig1.C70GB-2014整車網(wǎng)絡(luò)拓?fù)浣Y(jié)構(gòu)“由線束工程師統(tǒng)一發(fā)布OBD接口定義”物理層應(yīng)滿足ISO11898-2要求及北京新能源汽車股份有限公EVBUSMCU“由網(wǎng)絡(luò)工程師統(tǒng)一發(fā)布所有診斷ID分配，各系統(tǒng)填寫各自的診斷ID至上表”ParameterBSSTminValue8Unit-msParameterN_As/N_ArN_BrN_BsN_CsN_CrTimeoutPerformanceRequirement網(wǎng)絡(luò)層時間參數(shù)需求UnitmsmsmsmsmsParameterP2serverP2clientP2*serverP2*clientP3client_phys2P3client_funcParameterS3serverS3clientMin00P2serverP2server_maxMin0NominalMaxTimeoutTimeout4000UnitmsmsmsmsmsmsUnitmsmsTab4.應(yīng)用層時間參數(shù)需求4.2.DiagnosticServices（ISO14229-1）ServicesshallbeimplementedaccordingtoISO14229-1.Additional4.2.1.SupportedDiagnosticServicesTable5SupporteddiagnosticservicesofECUDiagnosticDiagnosticServicesListServiceNameDiagnosticSessionControlEcuResetSecurityAccessCommunicationContTesterPresentControlDTCSettingReadDataByIdentifWriteDataByIdentiInputOutputControlByIdentifierClearDiagnosticInformationReadDTCInformationRoutineControlRequestDownLoadTransferDataRequestTransferExAddressingPhysicalAddress√√√√√√√√√√√√√√√SessionDefaExten√√√√√√Programming√√√√√√√√√√rityAccessFunctionAddress√√√√√DiagnosticSessionControlEcuResetSecurityAccessCommunicationControlTesterPresentControlDTCSettingReadDataByIdentifierWriteDataByIdentifierClearDiagnosticInformationReadDTCInformationInputOutputContorlByIdentifierRoutineControlRequestDownloadTransferDataRequestTransferExit√√√√√Tab6.NegativeRespDescriptionDescriptionserviceNotSupportedsubFunctionNotSupportedincorrectMessageLengthOrInvalidFormatconditionsNotCorrectrequestSequenceErrorexceededNumberOfAttemptsrequestOutOfRangesecurityAccessDeniedrequiredTimeDelayNotExpiredInvalidKeygeneralProgrammingFailureresponsePendingserviceNotSupportedInActiveSessionVoltageTooHigh/voltageTooLowsubFunctionNotSupportedInActiveSessionNRC(Hex)92H/93Hnegativeresponsemessageaccordingtothefoll4.2.2.DiagnosticSessionControl（10H）.MessageFormatByteNameRequestServiceIdentifierSub-function=[DefaultSessionProgrammingSessionCvtMMExtendedDiagnosticSession]Value(hex)ByteByteNameCvtValue#1PositiveResponseServiceIdentifierM50Sub-Function=[DefaultSessionProgrammingSessionExtendedDiagnosticSession]byte#1byte#2]byte#1byte#2]P2server[]=[P2*server[]=[00-FFMMMMMTimingP2servervalueisprovidedin1msresolution.TimingP2*servervalueisprovidedin10msresolution.ByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCMMMHEXDescriptionCvt01DefaultSessionMThisdiagnosticsessionenablesthedefaultdiagnosticsessionintheserver(s)anddoesnotsupportanydiagnosticapplicationtimeouthandlingprovisions..noTesterPresentserviceisnecessarytokeepthesessionactive).02ProgrammingSessionMThisdiagnosticsessionenablesalldiagnosticservicesrequiredtosupportedthememoryprogrammingExtendedDiagnosticSessionThisdiagnosticsessioncan.beusedtoenablealldiagnosticservicesrequiredtosupporttheetc.”intheserver’smemory.toenablediagnosticservices,whicharenotspecificallytiedtotheadjustmentoffunctions.MDescriptionDescriptionThesub-functionparameterintherequestmessageisnotsupported.Thelengthofthemessageiswrong.TheECUcurrentconditionsdonotallowthechangeofdiagnosticSession.NRC(Hex)MMMFig3.Sessiontransitiondiagramresetbasedonthecontentof.MessageFormatByteNameCvtValue(hex)#1RequestServiceIdentifierM11Sub-Function=[#2ResetType:HardResetM01SoftReset]03ByteNameCvtValue#1PositiveResponseServiceIdentifierM51Sub-Function=[#2ResetType:HardResetM01SoftReset]03ByteNameValueNegativeResponseServiceIdentifierMRequestServiceIdentifierMNegativeResponseCodeMNRCOptionDescriptionOptionHardResetHardResetsimulatesthepower-on/start-upsequencetypicallyperformedafteraserverhasbeenpreviouslydisconnectedfromitspowersupply.battery).SoftResetcausestheservertoimmediatelyrestarttheapplicationprogramifapplicable.Theperformedactionisimplementationspecificandnotdefinedbythestandard.Atypicalactionistorestarttheapplicationwithoutreinitializingofpreviouslylearnedconfigurationdata,adaptivefactorsandotherlong-termadjustments.MMConditionsSub-functionparameterintherequestsupported.ThelengthofthemessageiswrongMThecriteriafortheECUResetrequestarenotmet.Mreset.4.2.4.CommunicationControl（28H）.MessageFormatByteByteNameCvtValueRequestServiceIdentifierSub-Function=[MEnableRxAndTxDisableRxAndTx]MCommunicationType=[NormalCommunicationMessagesNetworkManagementCommunicationMessagesNetworkManagementCommunicationMessagesMAndNormalCommunicationMessages]AndNormalCommunicationMessages]tByteNameValuet#1PositiveResponseServiceIdentifierM68SubSub-Function=[EnableRxAndTx00#2EnableRxAndDisableTxM01DisableRxAndEnableTxDisableRxAndEnableTx02DisableRxAndTx]03ByteByteNametValueNegativeResponseServiceIdentifierMRequestServiceIdentifierMNegativeResponseCodeMNRCNRCNRC(Hex)Conditions12Sub-functionparameterintherequestmessageisnotMsupported.22TheoperatingconditionsoftheserverarenotmettoMperformtherequiredaction.31NoneoftherequestedCommunicationTypevaluesareMsupportedbythedevice.DescriptionDescriptionEnableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbeenabledforthespecifiedCommunicationType.DisableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbedisabledforthespecifiedCommunicationType.Option(hex)MMDescriptionDescriptionNormalCommunicationMessagesThisvaluereferencesallapplication-relatedcommunication(inter-applicationsignalexchangebetweenmultiplein-vehicleservers).NetworkManagementCommunicationMessagesThisvaluereferencesallnetworkmanagementrelatedcommunication.NetworkManagementCommunicationMessagesAndNormalCommunicationMessagesThisvaluereferencesallnetworkmanagementandapplication-relatedcommunicationOption(hex)MMM4.2.5.SecurityAccess（27H）correspondingkeyvaSecurityAccess-RequestSeedmessage.respondwithaSecurityAccess-RequestSeedTheSeed-KeyalgorithmforSecurityAccesTheSecuritySeedis4Bytesrandomnumbers.TesterComputeKeyGenerateSeedComputeKeyCompareKey.Fig4.SecurityAccessprocedureByteName#1RequestServiceIdentifier#2SecurityAccessType=RequestSeedByteName#1PositiveResponseServiceIdentifier#2SecurityAccessType=RequestSeedtMMtMMMValue(hex)01，11Value01，11…00-FF…00-FFMMNegativeResponse：ByteByteNametValue#1NegativeResponseServiceIdentifierM#2RequestServiceIdentifierM#3NegativeResponseCodeMNRCt12Sub-functionparameterintheresupported.13Thelengthofthe22ThecriteriafortheSecurityAccessrequestarenotmet.M37requiredTimeDelayNotExpiredMNameNameRequestServiceIdentifierSecurityAccessType=SendKey…Value(hex)02，1200-FF…00-FFBytetMMMMMByteName#1PositiveResponseServiceIdentifier#2SecurityAccessType=SendKeytMMValue02，12ByteNametValue#1NegativeResponseServiceIdentifierM#2RequestServiceIdentifierM#3NegativeResponseCodeMNRCConditionsConditionst12Sub-functionparameterintheresupported.13Thelengthofthe22ThecriteriafortheSecurityAccessrequestarenotmet.M24requestSequenceErrorM36exceededNumberOfAttemptsMSendifthedelaytimernumberofallowedfalseaccessattempts.HEXHEXDescriptionCvt01requestSeed（level1）M11requestSeed（level3flash）MFigFig5.SecurityAccessFig6.SecurityAccessNRCrequirements4.2.6.TesterPresent（3EH）ByteNametValue(hex)#1RequestServiceIdentifierM#2zeroSubFunctionMByteNametValue#1PositiveResponseServiceIdentifierM#2zeroSubFunctionMByteByteNametValueNegativeResponseServiceIdentifierMRequestServiceIdentifierMNegativeResponseCodeMNRCConditionsSub-functionparameterinsupported.therequestmessageisnotMThelengthofthemessageMDescriptionDescriptionZeroSubFunctionThisparametervalueisusedtoindicatethatnosub-functionvaluebesidethesuppressPosRspMsgIndicationBitissupportedbythisservice.MHEX4.2.7.ControlDTCSetting(85H)DiagnosticTroubleCodes,DTCs,intheECUControlDTCSettingnegatthereject.ByteNameRequestServiceIdentifierDTCSettingType=[ByteNamePositiveResponseServiceIdentifierDTCSettingType[ByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodetMMtMMtMMMValue(hex)ValueValueNRCDescriptionDescriptionTheserver(s)shallresumethesettingofdiagnostictroublecodesaccordingtonormaloperatingconditionsTheserver(s)shallstopthesettingofdiagnostictroubleMMHEXNRCNRC(Hex)Conditions12Sub-functionparameterintherequestmessageisnotMsupported.22TheoperatingconditionsoftheserverarenotmettoUperformtherequiredaction.event).TheservicesReadDTCInformation-ReportDTCByReadDTCInformation-ReportSupportedDTCandClearDiagnost4.2.8.ReadDataByIdentifier（22H）TherequestmessagerequestsdatarecordvaluesfromtheserverbyoneormoredataIdentifier(s).WhenreceivingaReadDataByIdentifierrequest,theserverwillthedataIdentifierparameter(s)andtransmittheirvalueinReadDataByIdentifierpositiveresponsecontainingtheassociateddataRecordparameter(s)..MessageFormatByte…NameRequestServiceIdentifierDataIdentifier[]#1=[byte#2]…tMMMValue(hex)00-FF00-FF…DataIdentifier[]#m=[#nbyte#2]U00-FFNameNamePositiveResponseServiceIdentifierDataIdentifier[]#1=[byte#2]DataRecord[]#1=[…data#k]…DataIdentifier[]#m=[byte#2]DataRecord[]#m=[…data#o]Byte…#(k-1)+4…#n-(o-1)-2#n-(o-1)-1#n-(o-1)Value00-FF00-FF00-FF…00-FF…00-FF00-FF00-FF…00-FFCvtMMMM…UUUUNegativeResponse：ByteByteNametValue#1NegativeResponseServiceIdentifierM#2RequestServiceIdentifierM#3NegativeResponseCodeMNRCNRCNRC(Hex)Conditions22TheoperatingconditionsoftheserverarenotmettoUperformtherequiredaction.31NoneoftherequesteddataIdentifiervaluesareMsupportedbythedevice.4.2.9.WriteDataByIdentifierTheWriteDataByIdentifierservice.MessageFormatNameNameRequestServiceIdentifierDataIdentifier[]#1=[byte#2]…data#m]Value(hex)00-FF00-FF00-FF…00-FFByte…#m+3tMMMUUByteName#1PositiveResponseServiceIdentifierDataIdentifier[]#1=[#3byte#2]NegativeResponse：ByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodetMMMtMMMValue00-FF00-FFValueNRCNRCNRCConditionsCvt221.Theoperatingperformtherequiredaction.,thedataforaDataIdentifierisstoredinEEPROMandanEEPROMfailurehasoccurred).2.TheECUinternalconditionsdonotallowthewritingofanyDataIdentifier/IdentificationOption.2)ThesystemiscurrentlyinInputOutputControlByIdentifierserviceactivestage.3)Thesystemiscurrentlybusyatmodifyingmemory.4)Thevehicleismoving.31311.ThedataIdentifierintherequestmessageisnotsupportedMintheserverorthedataIdentpurpose(viaReadDataByIdentifierservice).2.AnydatatransmittedintherequestmessageafterthedataIdentifierisinvalid(ifapplicablet33ThedataIdentifier,whichreferenceaspecificaddress,isM72Theserverdetectsanerrorwhenwritingtoamemorylocation.Mconditionsaremetwhenperform1)Thehighandlowvoltagecurrentfaultdoesnotexistinthesystem.Pleasespecifyotherrulesinyourmodule.electronicsystemreferencedbyaninputOutputDataIdentif.MessageFormatNameNameRequestServiceIdentifierDataIdentifier[]#1=[byte#2]ControlOptionRecord#1[]=[ControlState#1/InputOutputControlParameter…ControlState#m]ControlEnableMaskRecord#1[]=[ControlMask#1…ControlMask#r]Value(hex)00-FF00-FF00-FF…00-FF00-FF…00-FFByte…#4+(m-1)#4+m…#4+m+(r-CvtMMMM/UCC…CNameNamePositiveResponseServiceIdentifierDataIdentifier[]#1=[byte#2]ControlStatusRecord#1[]=[ControlState#1/InputOutputControlParameter…ControlState#m]Byte…#4+(m-1)Value00-FF00-FF00-FF…00-FFtMMMCCNegativeResponse：ByteByteNametValueNegativeResponseServiceIdentifierMRequestServiceIdentifierMNegativeResponseCodeMNRCNRCNRCConditionsCvt22ConditionsNotCorrectM24The“returnControlToECU”sub-functionisrecfirstreceivinga“ShortTer311.TheserverdoesnotsupporttherequesteddataIdentifier.MuseroptionalinputOutputControlParametercontainsinvalid3.OneormultipleofthecontrolStateareinvalid.33ThecorrespondingsecurityisnotyetgrantedtoperformtheMrequiredservice.OptionOptionDescriptionCvt00returnControlToECUMThisparameterspecifiesthattheECUshalltakecontrolofthevalueofdataIdentifier.01ResetToDefaultMrequestedtoresettheinputsignal,in-ternalparameteroroutputsignalreferencedbytheinputOutputLocalIdentifierNumberofcontrolStatebytesinrequest:0NumberofcontrolStatebytesinpos.response:dependsonthedataIdentifier03ShortTermAdjustmentMThisparameterspecifiesthattheECUshallsetthevalueofdataIdentifiertorequestvalueofthethediagnosticcommunicationwiththetesterisbroken,thecontrolshallbegivenbacktotheECU.1)Thehighandlowvoltagecurrentfaultdoesnotexistinthesystem.2)Thecontrolledsystem,includingtheactuator,hasnofault.Pleasespecifyotherrulesinyourmodule.4.2.11.ClearDiagnosticInformation(14H).MessageFormatByteNameCvtValue(hex)RequestServiceIdentifierMgroupOfDTCHighByteMgroupOfDTCMiddleByteMgroupOfDTCLowByte]MByteNameCvtValue#1PositiveResponseServiceIdentifierM54ByteNameValueNegativeResponseServiceIdentifierMRequestServiceIdentifierMNegativeResponseCodeMNRCConditionsThelengthofthemessageiswrongTheECUinternalconditionsdonotallowdeletionofthediagnosticinformationstoredinthenode.Theseshutdownprocess.Memorycontent.WronggroupOfDTCvaluesinrequest.MMMFFFFFFxxxxxxDescriptionAparticularDTCresponse..MessageFormat.1.ReadDTCInformation-ReportNumberOfDTCByStatusMask(0x19ByteByteName#1RequestServiceIdentifierSub-Function=#2ReportNumberOfDTCByStatusMask#3DTCStatusMaskValue(hex)CvtMMMByteByteName#1PositiveResponseServiceIdentifierSub-Function=#2ReportNumberOfDTCByStatusMask#3DTCStatusAvailabilityMaskValueMMMDTCFormatIdentifierDTCFormatIdentifier=ISO15031-6DTCFormatDTCCount[]=[DTCCountHighByteDTCCountLowByte]MMMByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCMMMConditionsConditionsSub-functionparameterinsupported.ThelengthofthemessagerequestOutOfRangetherequestmessageisnotMMMByteByteName#1RequestServiceIdentifierSub-Function=#2ReportDTCByStatusMask#3DTCStatusMaskValue(hex)MMMByteByteName#1PositiveResponseServiceIdentifierSub-Function=#2ReportDTCByStatusMask#3DTCStatusAvailabilityMaskDTCAndStatusRecord[]＝[#4DTCHighByte#1DTCMiddleByte#1DTCLowByte#1statusOfDTC#1DTCHighByte#2DTCMiddleByte#2C…DTCLowByte#2statusOfDTC#2DTCHighByte#mDTCMiddleByte#mDTCLowByte#m#NstatusOfDTC#m]ValueMMMByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCCvtMMMConditionsConditionsSub-functionparameterinsupported.ThelengthofthemessagerequestOutOfRangetherequestmessageisnotMMMByteName#1RequestServiceIdentifierSub-Function=#2reportDTCSnapshotIdentificationtMMValue(hex)ByteByteName#1PositiveResponseServiceIdentifierSub-Function=#2reportDTCSnapshotIdentificationDTCRecord[]＝[#3DTCHighByte#1#4DTCMiddleByte#1#5DTCLowByte#1]#6DTCSnapshotRecordNumber#1…DTCRecord[]#m＝[DTCHighByte#mDTCMiddleByte#mDTCLowByte#m]DTCSnapshotRecordNumber#mValue00-FF00-FF00-FF00-FF00-FF00-FF00-FF00-FF#n-3#n-2#n-1tMMCCNegativeResponse：ByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCCvtMMMConditionsSub-functionparameterintherequestmessageisnotsupported.M31requestOutOfRangeM.4.ReadDTCInformation-reportDTCSnapshotRecordByDTCNumberNameNameRequestServiceIdentifierSub-Function=ReportDTCSnapshotRecordByDTCNumberDTCHighByteDTCMiddleByteDTCLowByte]DTCSnapshotRecordNumberValue(hex)00-FF00-FF00-FF00-FFBytetMMMMMMByteName#1PositiveResponseServiceIdentifierSub-Function=#2ReportDTCSnapshotRecordByDTCNumberDTCAndStatusRecord[]＝[#3DTCHighByte#4DTCMiddleByte#5DTCLowByte#6statusOfDTC]#7DTCSnapshotRecordNumber#1#8DTCSnapshotRecordNumberOfIdentifiers#1DTCSnapshotRecord[]#1=[#11snapshotData#1byte#1#11+(p-1)snapshotData#1byte#p#11+(p-1)+(p+2)*(w-dataIdentifier#wbyte(MSB)#11+(p-1)+(p+2)*(w-dataIdentifier#wbyte(LSB)#11+(p-1)+(p+2)*(w-snapshotData#wbyte#1tMMCValue00-FF00-FF00-FF00-FF00-FE00-FF00-FF00-FF00-FF…00-FF…00-FF00-FF00-FF#11+(p-1)+(p+2)*(w-2)+3+(p-1)……+(p+2)*(w-+(p+2)*(w-+(p+2)*(w-+(p+2)*(w-+(p-1)snapshotData#wbyte#p]………DTCSnapshotRecordNumberOfIdentifiers#xDTCSnapshotRecord[]#x=[dataIdentifier#1byte(MdataIdentifier#1byte(LsnapshotData#1byte#1…snapshotData#1byte#p…snapshotData#wbyte#100-FFsnapshotData#wbyte#p]…ByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCMMMConditionsConditionsSub-functionparameterinsupported.ThelengthofthemessagerequestOutOfRangetherequestmessageisnotMMMByteName#1RequestServiceIdentifierSub-Function=#2ReportSupportedDTCValue(hex)MMByte…#7+4*(m-#7+4*(m-#7+4*(m-#7+4*(m-NamePositiveResponseServiceIdentifierSub-Function=ReportSupportedDTCDTCStatusAvailabilityMaskDTCAndStatusRecord[]DTCHighByte#1DTCMiddleByte#1DTCLowByte#1statusOfDTC#1…DTCHighByte#mDTCMiddleByte#mDTCLowByte#mstatusOfDTC#m]tMMMMMMMMMMValue01-FF00-FF00-FF00-FF00-FF00-FF00-FFByteByteName#1NegativeResponseServiceIdentifier#2RequestServiceIdentifier#3NegativeResponseCodeValueNRCCvtMMMConditionsConditionsSub-functionparameterinsupported.ThelengthofthemessagerequestOutOfRangetherequestmessageisnotMMMParameterDescriptionDTCStatusMaskTheDTCStatusMaskcontains8DTCstatusbyteisusedintherequestmessagetoallowanexternaltesttooltorequestDTCinformationfortheDTCswhosestatusmatchestheDTCStatusMask.ADTC’sstatusmatchestheDTCStatusMaskifanyoneofcorrespondingstatusbitintheDTCStatusMaskisalsosetto“1”..,iftheDTCStatusMaskisbit-wiselogicallyANDedwiththeDTC’sactualstatusandtheresultisnon-zero,thenamatchhasoccurred).IftheexternaltesttoolspecifiesastatusmaskthatcontainsbitsthattheECUdoesnotsupport,thentheECUshallprocesstheDTCinformationusingonlytheBitField0123BitFieldDescriptionThisbitshallindicatetheresultofthemostrecentlyperformedtest.Alogical‘lasttestfailedmeaningthatthefailureiscompletelyresultofthemostrecentlyperformedtestreturnsa“pass”result.Resetto0afteracallofClearDiagnosticInformation.TestfailedthisoperationcycleThisbitshallindicatethatadiagnostictesthasreportedaTestFailedresultatanytimeduringthecurrentoperationto0whenanewoperationcycleisinitiatedorafteracalltoClearDiagnosticthisbitpendingDTCThisbitshallindicatewhetherornotadiagnostictesthasreportedaTestFailedresultatanytimeduringthecurrentorlastcompletedoperationcycle.Thestatusshallonlybeupdatedifthetestrunsandcompletes.ThecriteriatosetthePendingDTCbitandtheTestFailedThisOperationCyclebitarethesame.ThedifferenceisthattheTestFailedThisOperationCycleisclearedattheendofthecurrentoperationcycleandthePendingDTCbitisnotcleareduntilanoperationcyclehascompletedwherethetesthaspassedatleastonceandneverfailed.Resetto0afteClearDiagnosticInformation.confirmedDTCThisbitshallindicatewhetheramalfunctionwasdetectedenoughtimestowarrantthattheDTCisstormoretimesforemissionrelevantelectroniccontrolunits).ThisinformationcanbeusedbytheexternaltesttooltorequestadditionaldiagnosticinformationsuchasExtendedDataRecordsorSnapshotRecords.AConfirmedDTCdoesnotindicatethatthemalfunctionispresentatthetimeofthereMM4567Failedcanbeusedtodetermineifamalfunctionispresentatthetimeoftherequest.).Resettological‘0’afteracalltoClearDiagnosticInformationorafterself-healingcriteriahasbeensatisfiedorafterdiscardingthisDTCduetoFaultMemoryoverflow.TestnotcompletesincelastcleThisbitshallindicatewhetheraDTCtesthasruntocompletionsincethelasttimeacallwasmadetoClearDTCtesthasnotruntocompletion.Ifthetespassesorfails(TestFailedThisOperationCycle=1)Information.ThisbitshallindicatewhetheraDTCtesthaseverreturnedaTestFailedcallwasmadetoClearDiagnosticInformation(latchedTestFailedThisOperationCycle=1).Zero(0)shallindicatethatthetesZero(0)afteracalltoClearDiagnosticInformation.IncontradictiontotheConfirmedDTCthisbitisnotresetbyself-healingcriteriaorwhenitwasoverwrittenduetoanoverflowofthefaultmemory.Testnotcompletethisoperationcycle