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

1、精選文庫整車控制器系統(tǒng)診斷規(guī)范“EV160”文件編號：“EV160-20150002014”編制校對審核會簽“業(yè)務(wù)高級經(jīng)理”“控制系統(tǒng)集成主管”批準“部長”XXX年XXX月版本信息版本日期編制校對審核更新描述V1.0初始版本V1.120151127崔曉靜崔曉靜1、修改數(shù)據(jù)鏈路層描述；2、刪除31服務(wù)的02子服務(wù)；3、刪除28服務(wù)的01、02子服務(wù)；4、刪除2703、04子服務(wù)；5、27添加seed為四個字節(jié)的隨機數(shù)；6、seed和key在列表中定4個字節(jié)；7、刪除2F02子服務(wù)；8、刪除1906子服務(wù)；9、status改為僅bit0、3支持10、刪除NRC11；11、F184修改為9個字節(jié)；1

2、2、添加故障碼中英文對照表；目錄TOC o 1-5 h z版本信息2 HYPERLINK l bookmark6 o Current Document 參考文獻5 HYPERLINK l bookmark8 o Current Document 網(wǎng)絡(luò)拓撲5 HYPERLINK l bookmark10 o Current Document 診斷接口6 HYPERLINK l bookmark12 o Current Document 診斷需求7 HYPERLINK l bookmark14 o Current Document 4.1.診斷協(xié)議7 HYPERLINK l bookmark16

3、o Current Document 4.1.1.物理層7 HYPERLINK l bookmark18 o Current Document 4.1.2.數(shù)據(jù)鏈路層7 HYPERLINK l bookmark20 o Current Document 4.1.3.網(wǎng)絡(luò)層7應(yīng)用層時間參數(shù)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:凍結(jié)幀信息40附錄B:42B.1版本信息參數(shù)列表：42B.2數(shù)據(jù)流參數(shù)列表：42B.3版本信息參數(shù)定義44B.4數(shù)據(jù)流參數(shù)定義46術(shù)語DTC故障診斷碼BSB

8、locksizeSTminMinimumSeparationTimeC有條件的M強制性執(zhí)行U用戶選用TBD待定義SID服務(wù)標識符DID數(shù)據(jù)標識符NRC負響應(yīng)碼UDS統(tǒng)的診斷服務(wù)Server服務(wù)器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網(wǎng)絡(luò)拓撲由網(wǎng)絡(luò)工程師統(tǒng)一發(fā)布網(wǎng)絡(luò)拓撲”-一左:前豐童右At車宙右甘豐宙控制甦;邃慚樓口；車身押制樓塊；前S1；W平熱纜；方向盤轉(zhuǎn)拘怙越瓠電子槻宜垂氛；戟擷溝傳感算；嬴一CJNFCBUS：宜浪花電越雯;BMS=電池皆理垂統(tǒng)；DC-CHM：亶汛充電樁；RMS=

11、遠程監(jiān)持乘鑽；整車控tlflh潼斷接口；電范皆理丟統(tǒng)；P捋坤創(chuàng)殍；遠理金揑乘統(tǒng)；充電機瑋制兼軼；電對助力轉(zhuǎn)向垂統(tǒng);3EEB皿薪聽舞高通總經(jīng);I*VCU：CHG：EPS：+MCU：電幼電機揑創(chuàng)甦；+ICM=儀盤捽啊垂蛻；+ECC：電子觀捽垂境；EAS=電功空謂.垂蜒；+CHG-S：充電機捽刨垂撫（MJ；卜卜I：CANVBUS：匝車髙速總線;VOJrDLC：BCM：AHL=SAS=ESP：YBS=C1VEBL3：臣車低速總拔；BCM：車身拎制農(nóng)塊；DLU慈斷n?PEPS一梃如垂統(tǒng)；ICM=主儀我單元iSDM=安全氣養(yǎng)樓訣；ESCL：電子轉(zhuǎn)向柱鈦=RVG個車慮議乘茨；IPMS=SVA+PAS：愎燥犒

12、敬系竦+泊車軻助垂境；AQC：自功汽翼梓制系蛻;EHLL.隕樂主養(yǎng)單元iEU：DVDS示果撓；DS昭罵址員麼椅奧塊；LINBUS：1ZW沁BCM=車身護割換關(guān)；Anri-PiDcbl=Anri-PiKb2=Anri-PiKh3=Anri-Puxtri：Anri-PiKh.車宙薛夾氣苑;RaduSensor.酉怙題鴉，F(xiàn)ig1.C70GB-2014整車網(wǎng)絡(luò)拓撲結(jié)構(gòu)診斷接口丄口口口口口口口口8口口口口口口口応Fig2.OBD診斷接口管腳描述1EVBUSCANH2/精選文庫3/4接地5接地6/7/8/9EVBUSCANL10/11/12/13/14/15/16電源Tab1.OBD診斷接口針腳定義由線

13、束工程師統(tǒng)一發(fā)布OBD接口定義”診斷需求診斷協(xié)議4.1.1.物理層物理層應(yīng)滿足ISO11898-2要求及北京新能源汽車股份有限公司企業(yè)標準新能源汽車高速CAN網(wǎng)絡(luò)節(jié)點級電子控制單元（ECU）技術(shù)要求要求。4.1.2.數(shù)據(jù)鏈路層數(shù)據(jù)鏈路層應(yīng)滿足ISO11898-1要求。所有診斷請求和應(yīng)答幀的數(shù)據(jù)長度應(yīng)為8字節(jié)，否則電控單元將忽略該診斷請求幀。當診斷響應(yīng)長度不足8字節(jié)時，空余的字節(jié)應(yīng)用0 xAA填充。4.1.3.網(wǎng)絡(luò)層網(wǎng)絡(luò)層應(yīng)滿足ISO15765-2要求和下述要求：精選文庫精選文庫.尋址方式可以支持物理尋址和功能尋址。診斷消息ID描述見下表：控制器名稱簡稱物理尋址診斷請求ID(Hex)診斷響應(yīng)ID

14、(Hex)功能尋址診斷請求ID(Hex)實施網(wǎng)段驅(qū)動電機控制器MCU0 x7E00 x7E80 x7DFEVBUSTab2.診斷ID列表“由網(wǎng)絡(luò)工程師統(tǒng)一發(fā)布所有診斷ID分配，各系統(tǒng)填寫各自的診斷ID至上表”.網(wǎng)絡(luò)層時間參數(shù)ParameterValueUnitBS8-STmin20msParameterTimeoutPerformanceRequirementUnitNAs/NAr70n/amsNBrn/a70msNBs150n/amsNCsn/a70msNCr150n/amsTab3.網(wǎng)絡(luò)層時間參數(shù)需求4.1.4.應(yīng)用層時間參數(shù)ParameterMinMaxTimeoutUnitP2serv

15、er050n/amsP2clientn/an/a150msP2*server02000n/amsP2*clientn/an/a5000msP3clientphys2P2servern/an/amsP3clientfuncP2servermaxn/an/amsParameterMinNominalTimeoutUnitS3servern/an/a5000msS3client020004000msTab4.應(yīng)用層時間參數(shù)需求DiagnosticServices(ISO14229-1)ServicesshallbeimplementedaccordingtoISO14229-1.Additional

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

17、ddress10DiagnosticSessionControl7711EcuReset7727SecurityAccess728CommunicationControl773ETesterPresent7785ControlDTCSetting7722ReadDataByIdentifier72EWriteDataByIdentifier71屯72FInputOutputControlBvidentifier71714ClearDiagnosticInformation719ReadDTCInformation731RoutineControl7173734RequestDownLoad73

18、736TransferData73737RequestTransferExit737說明：訪問權(quán)限丁1表示需要擴展安全級權(quán)限，V3表示需要編程安全級權(quán)限。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