北京新能源汽车整车控制器系统诊断规范

1、精选文库整车控制器系统诊断规范“EV160”文件编号：“EV160-20150002014”编制校对审核会签“业务高级经理”“控制系统集成主管”批准“部长”XXX年XXX月版本信息版本日期编制校对审核更新描述V1.0初始版本V1.120151127崔晓静崔晓静1、修改数据链路层描述；2、删除31服务的02子服务；3、删除28服务的01、02子服务；4、删除2703、04子服务；5、27添加seed为四个字节的随机数；6、seed和key在列表中定4个字节；7、删除2F02子服务；8、删除1906子服务；9、status改为仅bit0、3支持10、删除NRC11；11、F184修改为9个字节；1

2、2、添加故障码中英文对照表；目录TOC o 1-5 h z版本信息2 HYPERLINK l bookmark6 o Current Document 参考文献5 HYPERLINK l bookmark8 o Current Document 网络拓扑5 HYPERLINK l bookmark10 o Current Document 诊断接口6 HYPERLINK l bookmark12 o Current Document 诊断需求7 HYPERLINK l bookmark14 o Current Document 4.1.诊断协议7 HYPERLINK l bookmark16

3、o Current Document 4.1.1.物理层7 HYPERLINK l bookmark18 o Current Document 4.1.2.数据链路层7 HYPERLINK l bookmark20 o Current Document 4.1.3.网络层7应用层时间参数8 HYPERLINK l bookmark22 o Current Document DiagnosticServices(ISO14229-1)8 HYPERLINK l bookmark24 o Current Document SupportedDiagnosticServices9 HYPERLINK

4、 l bookmark26 o Current Document DiagnosticSessionControl(10H)11 HYPERLINK l bookmark28 o Current Document ECUReset(11H)13 HYPERLINK l bookmark30 o Current Document CommunicationControl(28H)14 HYPERLINK l bookmark32 o Current Document SecurityAccess(27H)15 HYPERLINK l bookmark34 o Current Document T

5、esterPresent(3EH)21 HYPERLINK l bookmark36 o Current Document ControlDTCSetting(85H)21 HYPERLINK l bookmark38 o Current Document ReadDataByIdentifier(22H)23 HYPERLINK l bookmark40 o Current Document WriteDataByIdentifier(2EH)24 HYPERLINK l bookmark42 o Current Document InputOutputControlByIdentifier

6、(2FH)26 HYPERLINK l bookmark44 o Current Document ClearDiagnosticInformation(14H)27 HYPERLINK l bookmark46 o Current Document ReadDTCInformation(19H)28 HYPERLINK l bookmark48 o Current Document RoutineControl(31H)35 HYPERLINK l bookmark50 o Current Document RequestDownLoad(34H)37 HYPERLINK l bookmar

7、k52 o Current Document TransferData(36H)37 HYPERLINK l bookmark54 o Current Document RequestTransferExit(37H)3.7 HYPERLINK l bookmark56 o Current Document 故障定义38 HYPERLINK l bookmark58 o Current Document 故障码DTC中英文对照表38附录A:冻结帧信息40附录B:42B.1版本信息参数列表：42B.2数据流参数列表：42B.3版本信息参数定义44B.4数据流参数定义46术语DTC故障诊断码BSB

8、locksizeSTminMinimumSeparationTimeC有条件的M强制性执行U用户选用TBD待定义SID服务标识符DID数据标识符NRC负响应码UDS统的诊断服务Server服务器Client客户端ECU电控单元参考文献NO.参考文档题目1ISO11898-1:2003Roadvehicles-Controllerareanetwork(CAN)Part1:Datalinklayerandphysicalsignaling2ISO11898-2:2003Roadvehicles-Controllerareanetwork(CAN)Part2:High-speedmediumacc

9、essunitISO11898-5:2007Roadvehicles-Controllerareanetwork(CAN)Part5:High-speedmediumaccessunitwithlow-powermode4ISO15765-2:2004RoadVehicle-DiagnosticonCANPart2:NetworkingLayerServicesISO15765-3:2004RoadVehicle-DiagnosticonCANPart3:ApplicationLayerServicesISO14229-1:2006RoadVehicle-DiagnosticSystemsDi

10、agnosticServicesSpecification7ISO15031-6:2005Roadvehicles-Communicationbetweenvehicleandexternalequipmentforemission-relateddiagnosticPart6:Diagnostictroublecodedefinitions网络拓扑由网络工程师统一发布网络拓扑”-一左:前丰童右At车宙右甘丰宙控制甦;邃慚楼口；车身押制樓块；前S1；W平热纜；方向盘转拘怙越瓠电子槻宜垂氛；戟撷沟传感算；嬴一CJNFCBUS：宜浪花电越雯;BMS=电池皆理垂统；DC-CHM：亶汛充电桩；RMS=

11、远程监持乘鑽；整车控tlflh潼斷接口；电范皆理丟统；P捋坤创殍；远理金揑乘统；充电机玮制兼轶；电对助力转向垂统;3EEB皿薪聽舞高通总经;I*VCU：CHG：EPS：+MCU：电幼电机揑创甦；+ICM=仪盘捽啊垂蛻；+ECC：电子观捽垂境；EAS=电功空謂.垂蜒；+CHG-S：充电机捽刨垂抚（MJ；卜卜I：CANVBUS：匝车髙速总线;VOJrDLC：BCM：AHL=SAS=ESP：YBS=C1VEBL3：臣车低速总拔；BCM：车身拎制農块；DLU慈斷n?PEPS一梃如垂统；ICM=主仪我单元iSDM=安全气養樓訣；ESCL：电子转向柱钛=RVG個车虑議乘茨；IPMS=SVA+PAS：愎燥犒

12、敬系竦+泊车轲助垂境；AQC：自功汽翼梓制系蜕;EHLL.陨乐主養单元iEU：DVDS示果挠；DS昭骂址员麼椅奥块；LINBUS：1ZW沁BCM=车身护割換关；Anri-PiDcbl=Anri-PiKb2=Anri-PiKh3=Anri-Puxtri：Anri-PiKh.车宙薛夹氣苑;RaduSensor.酉怙題鴉，Fig1.C70GB-2014整车网络拓扑结构诊断接口丄口口口口口口口口8口口口口口口口応Fig2.OBD诊断接口管脚描述1EVBUSCANH2/精选文库3/4接地5接地6/7/8/9EVBUSCANL10/11/12/13/14/15/16电源Tab1.OBD诊断接口针脚定义由线

13、束工程师统一发布OBD接口定义”诊断需求诊断协议4.1.1.物理层物理层应满足ISO11898-2要求及北京新能源汽车股份有限公司企业标准新能源汽车高速CAN网络节点级电子控制单元（ECU）技术要求要求。4.1.2.数据链路层数据链路层应满足ISO11898-1要求。所有诊断请求和应答帧的数据长度应为8字节，否则电控单元将忽略该诊断请求帧。当诊断响应长度不足8字节时，空余的字节应用0 xAA填充。4.1.3.网络层网络层应满足ISO15765-2要求和下述要求：精选文库精选文库.寻址方式可以支持物理寻址和功能寻址。诊断消息ID描述见下表：控制器名称简称物理寻址诊断请求ID(Hex)诊断响应ID

14、(Hex)功能寻址诊断请求ID(Hex)实施网段驱动电机控制器MCU0 x7E00 x7E80 x7DFEVBUSTab2.诊断ID列表“由网络工程师统一发布所有诊断ID分配，各系统填写各自的诊断ID至上表”.网络层时间参数ParameterValueUnitBS8-STmin20msParameterTimeoutPerformanceRequirementUnitNAs/NAr70n/amsNBrn/a70msNBs150n/amsNCsn/a70msNCr150n/amsTab3.网络层时间参数需求4.1.4.应用层时间参数ParameterMinMaxTimeoutUnitP2serv

15、er050n/amsP2clientn/an/a150msP2*server02000n/amsP2*clientn/an/a5000msP3clientphys2P2servern/an/amsP3clientfuncP2servermaxn/an/amsParameterMinNominalTimeoutUnitS3servern/an/a5000msS3client020004000msTab4.应用层时间参数需求DiagnosticServices(ISO14229-1)ServicesshallbeimplementedaccordingtoISO14229-1.Additional

16、detailsarespecifiedinthissection.4.2.1.SupportedDiagnosticServicesTheoverviewofECUsupporteddiagnosticservicesisdescribedinthefollowingtable.Table5SupporteddiagnosticservicesofECUDiagnosticServicesListSessionSecurityAccessAddressingSID(Hex)ServiceNameDefaultExtendedProgrammingPhysicalAddressFunctionA

17、ddress10DiagnosticSessionControl7711EcuReset7727SecurityAccess728CommunicationControl773ETesterPresent7785ControlDTCSetting7722ReadDataByIdentifier72EWriteDataByIdentifier71屯72FInputOutputControlBvidentifier71714ClearDiagnosticInformation719ReadDTCInformation731RoutineControl7173734RequestDownLoad73

18、736TransferData73737RequestTransferExit737说明：访问权限丁1表示需要扩展安全级权限，V3表示需要编程安全级权限。TheservicesneedtosupportsuppressPositveResponseBit(SPRS)areshowedinfollowingtable.Tab5.ServicessupportedSPRSbitDiagnosticServicesListSupportSPRSbitSID(Hex)ServiceName10DiagnosticSessionControl7DiagnosticServicesListSupportS

19、PRSbitSID(Hex)ServiceName11EcuReset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier14ClearDiagnosticInformation19ReadDTCInformation2FInputOutputContorlByIdentifier31RoutineControl34RequestDownload36TransferData37RequestTransferExit

20、ThenegativeResponseCodes(NRC)usedbyECUaredefinedasfollows:Tab6.NegativeResponseCodesNRC(Hex)Description11HserviceNotSupported12HsubFunctionNotSupported13HincorrectMessageLengthOrInvalidFormat22HconditionsNotCorrect24HrequestSequenceError36HexceededNumberOfAttempts31HrequestOutOfRange33HsecurityAcces

21、sDenied37HrequiredTimeDelayNotExpired35HInvalidKey72HgeneralProgrammingFailure78HresponsePending7FHserviceNotSupportedInActiveSession92H/93HVoltageTooHigh/voltageTooLow7EHsubFunctionNotSupportedInActiveSessionIftwoormoreNRCsarereasonable,theECUcouldsendthenegativeresponsemessageaccordingtothefollowi

22、ngpriorityrules：The7FhNRChavethehighestpriority;Forothers,theNRCwithsmallernumberhashigherpriority.DiagnosticSessionControl(10H)Thisserviceisusedbytheclienttoenabledifferentdiagnosticsessionsintheserver(s).Adiagnosticsessionenablesaspecificsetofdiagnosticservicesintheserver(s).MessageFormatRequest：B

23、yteNameCvtValue(hex)#1RequestServiceldentifierM10#2Sub-function=DefaultSessionProgrammingSessionExtendedDiagnosticSessionM010203PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM50#2Sub-Function=DefaultSessionProgrammingSessionExtendedDiagnosticSessionM010203P2server=#3byte#1M00-F

24、F#4byte#2M00-FFP2*server=#5byte#1M00-FF#6byte#2M00-FFTimingP2servervalueisprovidedin1msresolution.TimingP2*servervalueisprovidedin10msresolution.NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM10#3NegativeResponseCodeMNRCSub-functionParameterDefiniti

25、onHEXDescriptionCvt01DefaultSessionThisdiagnosticsessionenablesthedefaultdiagnosticsessionintheserver(s)anddoesnotsupportanydiagnosticapplicationtimeouthandlingprovisions.(e.g.noTesterPresentserviceisMnecessarytokeepthesessionactive).02ProgrammingSessionThisdiagnosticsessionenablesalldiagnosticservi

26、cesrequiredtosupportedthememoryprogrammingofaserver.M03ExtendedDiagnosticSessionThisdiagnosticsessioncane.g.beusedtoenablealldiagnosticservicesrequiredtosupporttheadjustmentoffunctionslike“IdleSpeed,COValue,heserversmemory.Itcanalsobeusedtoenablediagnosticservices,whicharenotspecificallytiedt

27、otheadjustmentoffunctions.MNegativeResponseCodes(NRC)NRC(Hex)DescriptionCvt12Thesub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22TheECUcurrentconditionsdonotallowthechangeofdiagnosticSession.M.ImplementationRulesThisserviceisusedbythediagnostictooltoenabledif

28、ferenttypesofdiagnosticsessionsinaserver.Inordertoexecuteadiagnosticservicetheappropriatesessionhastobestartedfirst.Thereshallbeonlyonediagnosticsessionactiveatatime.Normal/DefaultSession(01h)shallbeenabledautomaticallybytheECUifnodiagnosticsessionhasbeenrequestedatpowerup.TheECUshallreturntoNormal/

29、DefaultSession(01h)aftertimeoutofExtendedDiagnosticSession.TheECUshallbecapableofprovidingalldiagnosticfunctionalitydefinedforthedefaultdiagnosticsessionundernormaloperatingconditions.TheECUshallfirstsendaDiagnosticSessionControlPositiveResponse(50hxx)messagebeforethenewsessionbecomesactiveintheECU.

30、ADiagnosticSessionControlPositiveResponse(50hxx)messageshallbereturnedbyanECUifthediagnostictoolrequestsasessionthatisalreadyrunning.IftheECUhasalreadyreceivedthesamerequestmessagepreviouslyandperformedtherequestedoperation,theECUshallcontinuetoperformthecurrentoperation(i.e.itisnotachangeofthesessi

31、on).TheECUshallremaininitscurrentdiagnosticsessionifitisnotabletoswitchintotherequesteddiagnosticsession.TheTesterPresent(3Eh)serviceshallbeusedtokeepthenon-defaultdiagnosticsessionsactivebyretriggeringS3server.AlsoanyotherservicerequestshallretriggerS3server.AfunctionalTesterPresent(3Eh)requestwith

32、outresponsemaybesentatanytime,evenregardlessofanyotherserviceinprogress.Whenreceivingortransmittinganydiagnosticmessages,including3Ehservice,theS3servertimerwillreset.DefaultExtendwci1001,10031002Programming002110310031103WO01M1O1101Fig3.SessiontransitiondiagramECUReset(11H)Thisservicerequeststheser

33、vertoeffectivelyperformanECUresetbasedonthecontentoftheResetTypeparametervalue(suppressPosRspMsgIndicationBit(bit7)notshown).MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceldentifierM11#2Sub-Function=ResetType:HardResetSoftResetM0103PositiveResponse：ByteNameCvtValue#1PositiveResponseServi

34、ceIdentifierM51#2Sub-Function=ResetType:HardResetSoftResetM0103NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM11#3NegativeResponseCodeMNRCSub-functionParameterDefinitionOption(Hex)DescriptionCvt01HardResetThisvalueidentifiesa“hardreset”conditionwhic

35、hSimulaMtesthpower-on/start-upsequencetypicallyperformedafteraserverhasbeenpreviouslydisconnectedfromitspowersupply(i.e.battery).03SoftResetThisvalueidentifiesa“softresetcondition,whichcausestheservertoimmediatelyrestarttheapplicationprogramifapplicable.Theperformedactionisimplementationspecificandn

36、otdefinedbythestandard.Atypicalactionistorestarttheapplicationwithoutreinitializingofpreviouslylearnedconfigurationdata,adaptivefactorsandotherlong-termadjustments.MNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong

37、M22ThecriteriafortheECUResetrequestarenotmet.MImplementationRulesThepositiveresponseshallbesentbeforeperformingtheECUreset.Theexecutionofresetwilltakems,whichmeanstheECUcantrespondtoanynewrequestsentwithinthistime.CommunicationControl(28H)Theserviceisusedto“switchon/off”thetransmissionand/ortherecep

38、tionofcertainmessagesof(a)server(s).MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceIdentifierM28#2Sub-Function=EnableRxAndTxDisableRxAndTxM0003#3CommunicationType=NormalCommunicationMessagesNetworkManagementCommunicationMessagesNetworkManagementCommunicationMessagesAndNormalCommunicationM

39、essagesM010203PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM68Sub-Function=EnableRxAndTx00#2EnableRxAndDisableTxM01DisableRxAndEnableTx02DisableRxAndTx03NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM28#3NegativeResponseCodeMN

40、RCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13ThelengthofthemessageiswrongM22Theoperatingconditionsoftheserverarenotmettoperformtherequiredaction.M31NoneoftherequestedCommunicationTypevaluesaresupportedbythedevice.MSub-functionParameterD

41、efinition：Option(hex)DescriptionCvt00EnableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbeenabledforthespecifiedCommunicationType.M03DisableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbedisabledforthespecifiedCommunicationType.MDataParameterDefini

42、tion：Option(hex)DescriptionCvt01NormalCommunicationMessagesThisvaluereferencesallapplication-relatedcommunication(inter-applicationsignalexchangebetweenmultiplein-vehicleservers).M02NetworkManagementCommunicationMessagesThisvaluereferencesallnetworkmanagementrelatedcommunication.M03NetworkManagement

43、CommunicationMessagesAndNormalCommunicationMessagesThisvaluereferencesallnetworkmanagementandapplication-relatedcommunicationMImplementationRulesTherearenospecialgeneralimplementationrulesforthisservice.SecurityAccess(27H)Thepurposeofthisserviceistoprovideameanstoaccessdataand/ordiagnosticservices,w

44、hichhaverestrictedaccessforsecurityorsafetyreasons.Diagnosticservicesfordownloading/uploadingroutinesordataintoaserverandreadingspecificmemorylocationsfromaserveraresituationswheresecurityaccessmayberequired.Improperroutinesordatadownloadedintoaservercouldpotentiallydamagetheelectronicsorothervehicl

45、ecomponentsorriskthevehiclescompliancetosafety,securitystandards.Thesecurityconceptusesaseedandkeyrelationship.TheclientshallrequesttheservertounlockbysendingtheserviceSecurityAccess-RequestSeedmessage.Theservershallrespondbysendingaseed.Theseedistheinputparameterforthekeycalculationalgorithm.Itisus

46、edbytheclienttocalculatethecorrespondingkeyvalue.Inasecondstep,theclientshallrequestthekeycomparisonbysendingthecalculatedkeytotheserverusingtheappropriateserviceSecurityAccess-SendKey.Theservershallcomparethiskeytooneinternallystored/calculated.Ifthetwonumbersmatch,thentheservershallenable(unlock)t

47、heclientsaccesstospecificservices/dataandindicatethatwiththeserviceSecurityAccess-SendKey.Ifthetwonumbersdonotmatch,thisshallbeconsideredasafalseaccessattempt.Ifaccessisrejectedforanyotherreason,itshallnotbeconsideredasafalseaccessattempt.Aninvalidkeyrequirestheclienttostartoverfromthebeginningwitha

48、SecurityAccess-RequestSeedmessage.Ifaserversupportssecurity,butisalreadyunlockedwhenaSecurityAccess-RequestSeedmessageisreceived,thatservershallrespondwithaSecurityAccess-RequestSeedpositiveresponsemessageservicewithaseedvalueequaltozero(0).Theclientshallusethismethodtodetermineifaserverislockedbych

49、eckingforanon-zeroseed.TheSeed-KeyalgorithmforSecurityAccess(Mandatory)：Key=(seed4)XORseed)3)XORseed)。TheSecuritySeedis4Bytesrandomnumbers.TesterECURequestSeCUrityAccessSeed$27$xxComputeKeypos_m_SendSeed$6GenerateSeedComputeKeyWecurityAcCompareKeyResPnse_一$67$yy/厂AccepKey$7F$27RejectKeyFig4.Security

50、AccessprocedureMessageFormatRequestSeedThisservicerequestsaseedfromtheserver.Basedonthisseed,theclientisabletocalculatethecorrespondingkeytobesentforunlockingtheserver.Request：ByteNameCvtValue(hex)#1RequestServiceldentifierM27#2SecurityAccessType=RequestSeedM01,11PositiveResponse：ByteNameCvtValue#1P

51、ositiveResponseServiceIdentifierM67#2SecurityAccessType=RequestSeedM01，11SecuritySeed=M#3seed#1(highbyte)M00-FF#6seed#m(lowbyte)MOO-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)Condit

52、ionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22ThecriteriafortheSecurityAccessrequestarenotmet.M37requiredTimeDelayNotExpiredMSendKeyThisservicesendsakeycalculatedbytheclienttotheserver.Theservershallcomparethiskeytooneinternallystored/calculated.I

53、fthetwonumbersmatch,thentheservershallenable(“unlock”)theclientsaccesstospecificservices/data.Request：ByteNameCvtValue(hex)#1RequestServiceIdentifierM27#2SecurityAccessType=SendKeyM02,12SecurityKey=M#3key#1(highbyte)M00-FF#6key#m(lowbyte)M00-FFPositiveResponse：ByteNameCvtValue#1PositiveResponseServi

54、ceIdentifierM67#2SecurityAccessType=SendKeyM02,12NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemess

55、ageiswrong.M22ThecriteriafortheSecurityAccessrequestarenotmet.M24requestSequenceErrorThe“sendKeysub-functionisreceivedwithoutfirstreceivinga“requestSeedrequestmessage.M35invalidKeyM36exceededNumberOfAttemptsSendifthedelaytimerisactiveduetoexceedingthemaximumnumberofMallowedfalseaccessattempts.Sub-fu

56、nctionParameterDefinitionHEXDescriptionCvt01requestSeed(level1)M02sendKey(level1)M11requestSeed(level3flash)M12sendKey(level3flash)MImplementationRulesAfterPowerOn/ResettheECUisinlockedstate.Thesecurityaccessfailurecounterissetto0.TheECUshallwait10sbeforeacceptingthefirstRequestSeedmessageafterEcuRe

57、set/PowerOn.AfterthethirdfailureattempttheECUshallwait10sbeforeacceptingthenext“RequestSeed”message.AflagisstoredintheEEPROMoftheECU.OneveryPowerOn/Reset,theECUchecksforthisflag,thenwaitsagain10sbeforeacceptingthenext“RequestSeed”message(ItisallowedtoimplementtheSecurityAccessrequirementwithoutbased

58、ontheFlag)AnySecurityAccessrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Ifthetesterrequestsaseed,ithastosendthecorrespondingkeytotheECU.Thissequenceismandatory.Ifthetestersendsaconsecutive“RequestSeed”,therequestisacceptedandthesameseedisreturned,b

59、utthesecurityaccessfailurecounterisincremented.Ifthetestersendsaninvalidkey,therequestisrejectedwithnegativeresponsecode“InvalidKey”,thesequenceshallbereset(anycurrentseedbecomesinvalid)andthesecurityaccessfailurecounterisincremented.Whenthesecuritycounterreachesthevalueof3(i.e.3failedtries),theECUs

60、hallwait10sbeforeacceptinganother“RequestSeed”message.Anysuchrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Whenthe10swaittimeiselapsedthesecurityaccessfailurecounterisdecrementedbyoneandanothertryisallowed.Whenduringthistrythesecurityaccessfailureco