北京新能源机动车整车控制器系统诊断标准规范

\\\\整车控制器系统诊断规范—“EV160”文件编号：“EV160-20150002014编制：校对：审核：“业务高级经理”会签：“控制系统集成主管”扌比准:“部长”XXX年XXX月

版本信息版本日期编制校对审核更新描述V1.0初始版本Vl.l20151127崔晓静崔晓静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个字节；12、添加故障码中英文对照表；目录TOC\o"1-5"\h\z版本信息2参考文献5网络拓扑5诊断接口6诊断需求74.1.诊断协议74.1.1.物理层74.1.2.数据链路层74.1.3.网络层7应用层时间参数8DiagnosticServices(ISO14229-1)8SupportedDiagnosticServices9DiagnosticSessionControl(10H)11ECUReset(11H)13CommunicationControl(28H)14SecurityAccess(27H)15TesterPresent(3EH)21ControlDTCSetting(85H)21ReadDataByIdentifier(22H)23WriteDataByIdentifier(2EH)24InputOutputControlByIdentifier(2FH)26ClearDiagnosticInformation(14H)27ReadDTCInformation(19H)28RoutineControl(31H)35RequestDownLoad(34H)37TransferData(36H)37RequestTransferExit(37H)3.7故障定义38故障码DTC中英文对照表38附录A:冻结帧信息40附录B:42B.1版本信息参数列表：42B.2数据流参数列表：42B.3版本信息参数定义44B.4数据流参数定义46术语DTC故障诊断码BSBlocksizeSTminMinimumSeparationTimeC有条件的M强制性执行U用户选用TBD待定义SID服务标识符DID数据标识符NRC负响应码UDS统的诊断服务Server服务器Client客户端ECU电控单元参考文献NO.参考文档题目[1]ISO11898-1:2003Roadvehicles-Controllerareanetwork(CAN)Part1:Datalinklayerandphysicalsignaling[2]ISO11898-2:2003Roadvehicles-Controllerareanetwork(CAN)Part2:High-speedmediumaccessunit⑶ISO11898-5:2007Roadvehicles-Controllerareanetwork(CAN)Part5:High-speedmediumaccessunitwithlow-powermode[4]ISO15765-2:2004RoadVehicle-DiagnosticonCANPart2:NetworkingLayerServices⑸ISO15765-3:2004RoadVehicle-DiagnosticonCANPart3:ApplicationLayerServices⑹ISO14229-1:2006RoadVehicle-DiagnosticSystemsDiagnosticServicesSpecification[7]ISO15031-6:2005Roadvehicles-Communicationbetweenvehicleandexternalequipmentforemission-relateddiagnosticPart6:Diagnostictroublecodedefinitions网络拓扑由网络工程师统一发布网络拓扑”一「一左:前丰童右At车宙右甘丰宙»控制甦;邃慚楼口；车身押制樓块；前S1；W平热纜；方向盘转拘怙越瓠电子槻宜垂氛；戟撷沟传感算；嬴一一「一左:前丰童右At车宙右甘丰宙»控制甦;邃慚楼口；车身押制樓块；前S1；W平热纜；方向盘转拘怙越瓠电子槻宜垂氛；戟撷沟传感算；嬴一CJNFCBUS：宜浪花电越雯;«BMS=电池皆理垂统；«DC-CHM：亶汛充电桩；«RMS=远程监持乘鑽；整车控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：愎燥犒敬系竦+泊车轲助垂境；AQC：自功汽翼梓制系蜕;EHLL.陨乐主養单元iEU：DVDS示果挠；DS昭骂址员麼椅奥块；LINBUS：1ZW沁BCM=车身护割換关；Anri-PiDcbl=Anri-PiKb2=Anri-PiKh3=Anri-Puxtri：Anri-PiKh.车宙薛夹氣苑;RaduSensor.酉■怙題鴉，FigFig1.C70GB-2014整车网络拓扑结构诊断接口丄口口口口口口口口8'口口口口□口口口応丄口口口口口口口口8'口口口口□口口口応Fig2.OBD诊断接口管脚描述1EVBUSCANH2/3/4接地5接地6/7/8/9EVBUSCANL10/11/12/13/14/15/16电源Tab1.OBD诊断接口针脚定义由线束工程师统一发布OBD接口定义”诊断需求诊断协议4.1.1.物理层物理层应满足ISO11898-2要求及北京新能源汽车股份有限公司企业标准《新能源汽车高速CAN网络节点级电子控制单元（ECU）技术要求》要求。4.1.2.数据链路层数据链路层应满足ISO11898-1要求。所有诊断请求和应答帧的数据长度应为8字节，否则电控单元将忽略该诊断请求帧。当诊断响应长度不足8字节时，空余的字节应用0xAA填充。4.1.3.网络层网络层应满足ISO15765-2要求和下述要求：

.寻址方式可以支持物理寻址和功能寻址。诊断消息ID描述见下表：控制器名称简称物理寻址诊断请求ID(Hex)诊断响应ID(Hex)功能寻址诊断请求ID(Hex)实施网段驱动电机控制器MCU0x7E00x7E80x7DFEVBUSTab2.诊断ID列表“由网络工程师统一发布所有诊断ID分配，各系统填写各自的诊断ID至上表”.网络层时间参数ParameterValueUnitBS8-STmin20msParameterTimeoutPerformanceRequirementUnitNAs/NAr70n/amsNBrn/a<70msNBs150n/amsNCsn/a<70msNCr150n/amsTab3.网络层时间参数需求4.1.4.应用层时间参数ParameterMinMaxTimeoutUnitP2server050n/amsP2clientn/an/a150msP2*server02000n/amsP2*clientn/an/a5000msP3clientphys2P2servern/an/amsP3clientfuncP2servermaxn/an/amsParameterMinNominalTimeoutUnitS3servern/an/a5000msS3client020004000msTab4.应用层时间参数需求DiagnosticServices(ISO14229-1)ServicesshallbeimplementedaccordingtoISO14229-1.Additionaldetailsare

specifiedinthissection.4.2.1.SupportedDiagnosticServicesTheoverviewofECUsupporteddiagnosticservicesisdescribedinthefollowingtable.Table5SupporteddiagnosticservicesofECUDiagnosticServicesListSessionSecurityAccessAddressingSID(Hex)ServiceNameDefaultExtendedProgrammingPhysicalAddressFunctionAddress10DiagnosticSessionControl7711EcuReset7727SecurityAccess728CommunicationControl773ETesterPresent7785ControlDTCSetting7722ReadDataByIdentifier72EWriteDataByIdentifier71屯72FInputOutputControlBvidentifier71714ClearDiagnosticInformation719ReadDTCInformation731RoutineControl7173734RequestDownLoad73736TransferData73737RequestTransferExit737说明：访问权限丁1表示需要扩展安全级权限，V3表示需要编程安全级权限。TheservicesneedtosupportsuppressPositveResponseBit(SPRS)areshowedinfollowingtable.Tab5.ServicessupportedSPRSbitDiagnosticServicesListSupportSPRSbitSID(Hex)ServiceName10DiagnosticSessionControl7

DiagnosticServicesListSupportSPRSbitSID(Hex)ServiceName11EcuReset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier14ClearDiagnosticInformation19ReadDTCInformation2FInputOutputContorlByIdentifier31RoutineControl34RequestDownload36TransferData37RequestTransferExitThenegativeResponseCodes(NRC)usedbyECUaredefinedasfollows:Tab6.NegativeResponseCodesNRC(Hex)Description11HserviceNotSupported12HsubFunctionNotSupported13HincorrectMessageLengthOrInvalidFormat22HconditionsNotCorrect24HrequestSequenceError36HexceededNumberOfAttempts31HrequestOutOfRange33HsecurityAccessDenied37HrequiredTimeDelayNotExpired35HInvalidKey72HgeneralProgrammingFailure78HresponsePending7FHserviceNotSupportedInActiveSession92H/93HVoltageTooHigh/voltageTooLow7EHsubFunctionNotSupportedInActiveSessionIftwoormoreNRCsarereasonable,theECUcouldsendthenegativeresponsemessageaccordingtothefollowingpriorityrules：•The7FhNRChavethehighestpriority;•Forothers,theNRCwithsmallernumberhashigherpriority.DiagnosticSessionControl(10H)Thisserviceisusedbytheclienttoenabledifferentdiagnosticsessionsintheserver(s).Adiagnosticsessionenablesaspecificsetofdiagnosticservicesintheserver(s).MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceldentifierM10#2Sub-function=[DefaultSessionProgrammingSessionExtendedDiagnosticSession]M010203PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM50#2Sub-Function=[DefaultSessionProgrammingSessionExtendedDiagnosticSession]M010203P2server[]=[#3byte#1M00-FF#4byte#2]M00-FFP2*server[]=[#5byte#1M00-FF#6byte#2]M00-FFTimingP2servervalueisprovidedin1msresolution.TimingP2*servervalueisprovidedin10msresolution.NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM10#3NegativeResponseCodeMNRCSub-functionParameterDefinitionHEXDescriptionCvt01DefaultSessionThisdiagnosticsessionenablesthedefaultdiagnosticsessionintheserver(s)anddoesnotsupportanydiagnosticapplicationtimeouthandlingprovisions.(e.g.noTesterPresentserviceisMnecessarytokeepthesessionactive).02ProgrammingSessionThisdiagnosticsessionenablesalldiagnosticservicesrequiredtosupportedthememoryprogrammingofaserver.M03ExtendedDiagnosticSessionThisdiagnosticsessioncane.g.beusedtoenablealldiagnosticservicesrequiredtosupporttheadjustmentoffunctionslike“IdleSpeed,COValue,etc."intheserver'smemory.Itcanalsobeusedtoenablediagnosticservices,whicharenotspecificallytiedtotheadjustmentoffunctions.MNegativeResponseCodes(NRC)NRC(Hex)DescriptionCvt12Thesub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22TheECUcurrentconditionsdonotallowthechangeofdiagnosticSession.M.ImplementationRulesThisserviceisusedbythediagnostictooltoenabledifferenttypesofdiagnosticsessionsinaserver.Inordertoexecuteadiagnosticservicetheappropriatesessionhastobestartedfirst.Thereshallbeonlyonediagnosticsessionactiveatatime.Normal/DefaultSession(01h)shallbeenabledautomaticallybytheECUifnodiagnosticsessionhasbeenrequestedatpowerup.TheECUshallreturntoNormal/DefaultSession(01h)aftertimeoutofExtendedDiagnosticSession.TheECUshallbecapableofprovidingalldiagnosticfunctionalitydefinedforthedefaultdiagnosticsessionundernormaloperatingconditions.TheECUshallfirstsendaDiagnosticSessionControlPositiveResponse(50hxx)messagebeforethenewsessionbecomesactiveintheECU.ADiagnosticSessionControlPositiveResponse(50hxx)messageshallbereturnedbyanECUifthediagnostictoolrequestsasessionthatisalreadyrunning.IftheECUhasalreadyreceivedthesamerequestmessagepreviouslyandperformedtherequestedoperation,theECUshallcontinuetoperformthecurrentoperation(i.e.itisnotachangeofthesession).TheECUshallremaininitscurrentdiagnosticsessionifitisnotabletoswitchintotherequesteddiagnosticsession.TheTesterPresent(3Eh)serviceshallbeusedtokeepthenon-defaultdiagnosticsessionsactivebyretriggeringS3server.AlsoanyotherservicerequestshallretriggerS3server.AfunctionalTesterPresent(3Eh)requestwithoutresponsemaybesentatanytime,evenregardlessofanyotherserviceinprogress.Whenreceivingortransmittinganydiagnosticmessages,including3Ehservice,

theS3servertimerwillreset.DefaultExtendwci1001,10031002Programming^00211031003DefaultExtendwci1001,10031002Programming^002110310031103WO01M1O1101Fig3.SessiontransitiondiagramECUReset(11H)ThisservicerequeststheservertoeffectivelyperformanECUresetbasedonthecontentoftheResetTypeparametervalue(suppressPosRspMsgIndicationBit(bit7)notshown).MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceldentifierM11#2Sub-Function=[ResetType:HardResetSoftReset]M0103PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM51#2Sub-Function=[ResetType:HardResetSoftReset]M0103NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM11#3NegativeResponseCodeMNRCSub-functionParameterDefinitionOption(Hex)DescriptionCvt01HardResetThisvalueidentifiesa“hardreset”conditionwhichSimulaMtesthpower-on/start-upsequencetypicallyperformedafteraserverhasbeenpreviouslydisconnectedfromitspowersupply(i.e.battery).03SoftResetThisvalueidentifiesa“softreset"condition,whichcausestheservertoimmediatelyrestarttheapplicationprogramifapplicable.Theperformedactionisimplementationspecificandnotdefinedbythestandard.Atypicalactionistorestarttheapplicationwithoutreinitializingofpreviouslylearnedconfigurationdata,adaptivefactorsandotherlong-termadjustments.MNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13ThelengthofthemessageiswrongM22ThecriteriafortheECUResetrequestarenotmet.MImplementationRulesThepositiveresponseshallbesentbeforeperformingtheECUreset.Theexecutionofresetwilltake<TBD>ms,whichmeanstheECUcan'trespondtoanynewrequestsentwithinthistime.CommunicationControl(28H)Theserviceisusedto“switchon/off”thetransmissionand/orthereceptionofcertainmessagesof(a)server(s).MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceIdentifierM28#2Sub-Function=[EnableRxAndTxDisableRxAndTx]M0003#3CommunicationType=[NormalCommunicationMessagesNetworkManagementCommunicationMessagesNetworkManagementCommunicationMessagesAndNormalCommunicationMessages]M010203PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM68Sub-Function=[EnableRxAndTx00#2EnableRxAndDisableTxM01DisableRxAndEnableTx02DisableRxAndTx]03

NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM28#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13ThelengthofthemessageiswrongM22Theoperatingconditionsoftheserverarenotmettoperformtherequiredaction.M31NoneoftherequestedCommunicationTypevaluesaresupportedbythedevice.MSub-functionParameterDefinition：Option(hex)DescriptionCvt00EnableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbeenabledforthespecifiedCommunicationType.M03DisableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbedisabledforthespecifiedCommunicationType.MDataParameterDefinition：Option(hex)DescriptionCvt01NormalCommunicationMessagesThisvaluereferencesallapplication-relatedcommunication(inter-applicationsignalexchangebetweenmultiplein-vehicleservers).M02NetworkManagementCommunicationMessagesThisvaluereferencesallnetworkmanagementrelatedcommunication.M03NetworkManagementCommunicationMessagesAndNormalCommunicationMessagesThisvaluereferencesallnetworkmanagementandapplication-relatedcommunicationMImplementationRulesTherearenospecialgeneralimplementationrulesforthisservice.SecurityAccess(27H)Thepurposeofthisserviceistoprovideameanstoaccessdataand/ordiagnosticservices,whichhaverestrictedaccessforsecurityorsafetyreasons.Diagnosticservicesfordownloading/uploadingroutinesordataintoaserverandreadingspecificmemorylocationsfromaserveraresituationswheresecurityaccessmayberequired.Improperroutinesordatadownloadedintoaservercouldpotentiallydamagetheelectronicsorothervehiclecomponentsorriskthevehicle'scompliancetosafetysecuritystandards.Thesecurityconceptusesaseedandkeyrelationship.TheclientshallrequesttheservertounlockbysendingtheserviceSecurityAccess-RequestSeedmessage.Theservershallrespondbysendingaseed.Theseedistheinputparameterforthekeycalculationalgorithm.Itisusedbytheclienttocalculatethecorrespondingkeyvalue.Inasecondstep,theclientshallrequestthekeycomparisonbysendingthecalculatedkeytotheserverusingtheappropriateserviceSecurityAccess-SendKey.Theservershallcomparethiskeytooneinternallystored/calculated.Ifthetwonumbersmatch,thentheservershallenable(unlock)theclient'saccesstospecificservices/dataandindicatethatwiththeserviceSecurityAccess-SendKey.Ifthetwonumbersdonotmatch,thisshallbeconsideredasafalseaccessattempt.Ifaccessisrejectedforanyotherreason,itshallnotbeconsideredasafalseaccessattempt.AninvalidkeyrequirestheclienttostartoverfromthebeginningwithaSecurityAccess-RequestSeedmessage.Ifaserversupportssecurity,butisalreadyunlockedwhenaSecurityAccess-RequestSeedmessageisreceived,thatservershallrespondwithaSecurityAccess-RequestSeedpositiveresponsemessageservicewithaseedvalueequaltozero(0).Theclientshallusethismethodtodetermineifaserverislockedbycheckingforanon-zeroseed.TheSeed-KeyalgorithmforSecurityAccess(Mandatory)：Key=((((seed>>4)XORseed)<<3)XORseed)。TheSecuritySeedis4Bytesrandomnumbers.TesterECURequestSeCUrityAccess〜Seed$27$xxCompute

Keypos_m_SendSeed$6Generate

SeedCompute

KeyWecurityAcCompareKeyResP°nse_一—$67$yy/厂AccepKey$7F$27RejectKeyFig4.SecurityAccessprocedureMessageFormatRequestSeedThisservicerequestsaseedfromtheserver.Basedonthisseed,theclientisabletocalculatethecorrespondingkeytobesentforunlockingtheserver.Request：ByteNameCvtValue(hex)#1RequestServiceldentifierM27#2SecurityAccessType=RequestSeedM01,11PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM67#2SecurityAccessType=RequestSeedM01，11SecuritySeed[]=[M#3seed#1(highbyte)M00-FF

#6seed#m(lowbyte)]MOO-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22ThecriteriafortheSecurityAccessrequestarenotmet.M37requiredTimeDelayNotExpiredMSendKeyThisservicesendsakeycalculatedbytheclienttotheserver.Theservershallcomparethiskeytooneinternallystored/calculated.Ifthetwonumbersmatch,thentheservershallenable(“unlock”)theclient'saccesstospecificservices/data.Request：ByteNameCvtValue(hex)#1RequestServiceIdentifierM27#2SecurityAccessType=SendKeyM02,12SecurityKey[]=[M#3key#1(highbyte)M00-FF#6key#m(lowbyte)]M00-FFPositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM67#2SecurityAccessType=SendKeyM02,12NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22ThecriteriafortheSecurityAccessrequestarenotmet.M24requestSequenceErrorThe“sendKey"sub-functionisreceivedwithoutfirstreceivinga“requestSeed"requestmessage.M35invalidKeyM36exceededNumberOfAttemptsSendifthedelaytimerisactiveduetoexceedingthemaximumnumberofMallowedfalseaccessattempts.Sub-functionParameterDefinitionHEXDescriptionCvt01requestSeed(level1)M02sendKey(level1)M11requestSeed(level3flash)M12sendKey(level3flash)MImplementationRulesAfterPowerOn/ResettheECUisinlockedstate.Thesecurityaccessfailurecounterissetto0.TheECUshallwait10sbeforeacceptingthefirstRequestSeedmessageafterEcuReset/PowerOn.AfterthethirdfailureattempttheECUshallwait10sbeforeacceptingthenext“RequestSeed”message.AflagisstoredintheEEPROMoftheECU.OneveryPowerOn/Reset,theECUchecksforthisflag,thenwaitsagain10sbeforeacceptingthenext“RequestSeed”message(ItisallowedtoimplementtheSecurityAccessrequirementwithoutbasedontheFlag)AnySecurityAccessrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Ifthetesterrequestsaseed,ithastosendthecorrespondingkeytotheECU.Thissequenceismandatory.Ifthetestersendsaconsecutive“RequestSeed”,therequestisacceptedandthesameseedisreturned,butthesecurityaccessfailurecounterisincremented.Ifthetestersendsaninvalidkey,therequestisrejectedwithnegativeresponsecode“InvalidKey”,thesequenceshallbereset(anycurrentseedbecomesinvalid)andthesecurityaccessfailurecounterisincremented.Whenthesecuritycounterreachesthevalueof3(i.e.3failedtries),theECUshallwait10sbeforeacceptinganother“RequestSeed”message.Anysuchrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Whenthe10swaittimeiselapsedthesecurityaccessfailurecounterisdecrementedbyoneandanothertryisallowed.Whenduringthistrythesecurityaccessfailurecounterisincrementedagain(duetoaninvalidkey),theECUshallwaitagain10sbeforeacceptinganother“RequestSeed”message.Whenthistryisvalid,thesecurityaccessfailurecounterisnotchanged.BJEVusesfourstates(threedifferentlevels):Locked,Unlocked(Level1),Unlock(Level2)andUnlocked(Flash).TheECUcouldsupportsomeofthemaccordingtotherequirement.

Lockedi'JMUnlocked(Flash)Urfccked(Level2j'!；IFig5.SecurityAccessTesterECUm匕l匚-丄=二Lockedi'JMUnlocked(Flash)Urfccked(Level2j'!；IFig5.SecurityAccessTesterECUm匕l匚-丄=二--u」^l=i-/rr-r1-'-I___,:■■-—jFf52.厂'—*LL二泄匚sKtiV127—■二4niIS-L1l"■*—币I5：仁「r：f-ir•；t；-i|t■■-vii-卜心；-i■:'t三-:xd:mc：_'~ri-_ySi—：-.==；S2-丘?_：?nd$：?：?」SendInval1key=i「mt-e:ter_|：'t—^■f-LirTJ-.•八-LJLL：沁nrl-计£....''■Wl"_―116questf'；,——_.22^——f..J'TOC\o"1-5"\h\zS^rid-?-'■■:.nl」2r____*—■"i.^F~52.—iPjlLII'~V/-LLLL；^qucLitS，-^—b.——-；nnd3」___—*_■"i■歹吊”£：-f沁nd-Syy-'■Exceed皿口加匚讨aytemuti_27玷E-沁CQI二"f-匚些XquWB*存厂“一一TjmE步1刊口於expifE芒*■—.—-■■■SendirivaldkeySendirivaldkey0t：6T0txii：i-r.'.dlJI-.thirdattemptTesterPresent(3EH)Thisserviceshallbeusedtoindicatetoaserverthattheclientispresent.ThisserviceisrequiredintheabsenceofotherUDSservicestopreventserversfromautomaticallyreturningtonormaloperationandstopcommunication.MessageFormatRequest:ByteNameCvtValue(hex)#1RequestServiceIdentifierM3E#2zeroSubFunctionM00PositiveResponse:ByteNameCvtValue#1PositiveResponseServiceIdentifierM7E#2zeroSubFunctionM00NegativeResponse:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM3E#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC):NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.MSub-functionParameterDefinitionHEXDescriptionCvt00ZeroSubFunctionThisparametervalueisusedtoindicatethatnosub-functionvaluebesidethesuppressPosRspMsgIndicationBitissupportedbythisservice.MImplementationRulesTherearenospecialgeneralimplementationrulesforthisservice.ControlDTCSetting(85H)Thisserviceis