新能源系统诊断规范

PAGEPAGE10/47XXXX —“填写项目代号”“向项目申请”制 ：校对 ：审核 “业务高级经理”会签 “控制集成主管”批准 “部长”XXX 年XXX 月信息V1.01；2310232801、02V1.1

务；4、删除2703、04子服务；527seed机数；6seedkey4字节；72F02子服务；81906子服务；9statusbit0、3支持10、删除NRC11；11、F184修改为9个字节；12、添加故障码中英文照表；2556777778cvs1 8SupportedDiagnosticServices 9l10 11ECUReset(11H) 1328 14SecurityAcces27 15t3E 21ControlDTCSetting(85H) 21yrH 23WriteDataByIdentifier(2EH) 24InputOutputControlByIdentifier(2FH) 26ClearDiagnosticInformation(14H) 27ReadDTCInformation(19H) 28RoutineControl(31H) 35RequestDownLoad(34H) 37373738中英对照表 38附A:冻结帧39附B: 41列表： 414143B.445DTC BS BlockSTmin MinimumSeparationTimeC M U TBD SID DID NRC UDS 一器Client 端ECU 电控单元参考文献NO.参考文档题目[1]ISO11898-1:2003Roadvehicles-Controllerareanetwork(CAN)Part1:Datalinkandsignaling[2]ISO11898-2:2003Roadvehicles-Controllerareanetwork(CAN)Part2:High-speedmediumaccessunit[3]ISO11898-5:2007Roadvehicles-Controllerareanetwork(CAN)Part5:High-speedmediumaccessunitwithlow-powermode[4]ISO15765-2:2004RoadVehicle-DiagnosticonCANPart2:NetworkingServices[5]ISO15765-3:2004RoadVehicle-DiagnosticonCANPart3:ApplicationServices[6]ISO14229-1:2006RoadVehicle-DiagnosticDiagnosticServicesSpecification[7]ISO15031-6:2005Roadvehicles-Communicationbetweenvehicleandequipmentforemission-relateddiagnosticPart6:Diagnostictroublecodedefinitions网络拓扑“由网络工程师一发布网络拓扑”.

Fg1. C70GB-2014g. D管脚管脚12描述EVBUSCAN_H/3345678910111213141516////EVBUS//////Tab1.OBD“由线束工程师OBD”需求4.1. 协议411. 要求及北京汽车股份有限公司企业标准《CAN网络节点级子控制单元（ECU）技术要求》要求。412. 数据链路层数据链路层应满足ISO11898-1要求。所有8控单元将忽略该请求帧。当8填充。413. 网络层应满足ISO15765-2要求和下述要求：D控制器名称控制器名称简称ID(Hex)响应ID(Hex)ID(Hex)实施网段驱动电机控制器 MCU0x7E00x7E80x7DFEVBUSTab2.“由网络工程师一发布所有ID分配，各填写各自的”ParameterueUnitBS8-STmin20msParameteruteuUnitN_As/N_Ar70n/amsN_Brn/a<70msN_Bs150n/amsN_Csn/a<70msN_Cr150n/amsTab3. 网络层时间参数需求4.1.4. 应用层时间参数P2serverP2clientMin0n/aMax50n/aTimeoutn/a150msmsP2*server02000n/amsP2*clientn/an/a5000msP3client_phys2P2servern/an/amsuP2servn/an/amsParameterMinNominalutUnitS3servern/an/a5000msS3client020004000msTab4. 应用层时间参数需求DiagnosticServices（ISO14229-1）ServicesshallbeimplementedaccordingtoISO14229-1.Additionaldetailsarespecifiedinthissection.SupportedDiagnosticTheoverviewofECUsupporteddiagnosticservicesisdescribedinthefollowingtable.Table5SupporteddiagnosticservicesofECUultdedssAddress A√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√√1√3√√√1√√√√√√√√√√1√3√√√3√√√3√√√3√DiagnosticServicesListSessionSID10ServiceNameDefa DiagnosticServicesListSessionSID10ServiceNameDefa ProgrammingSecurityAcceAddressingFunctionddress1127283E85222E2F1419DiagnosticSessionControlEcuResetSecurityAccessCommunicationControlTesterPresentControlDTCSettingReadDataByIdentifierrInputOutputControlByIdentifierClearDiagnosticInformationReadDTCInformation31RoutineControl343637RequestDownLoadTransferData。TheservicesneedtosupportsuppressPositveResponseBit(SPRS)areshowedinfollowingtable.Tab5.ServicessupportedSPRSbitDiagnosticServicesListSIDServiceName(Hex)10 DiagnosticSessionControl

SupportSPRS11EcuReset√27SecurityAccess28CommunicationControl√3ETesterPresent√85ControlDTCSetting√222EReadDataByIdentifierWriteDataByIdentifier14ClearDiagnosticInformation192FReadDTCInformationInputOutputContorlByIdentifier31RoutineControl34RequestDownload36TransferData37RequestTransferExitSIDSIDServiceNameSupportSPRSbitTab6.NegativeResponseCodes12H13H22H24H36H31H33H37H35H72H78H7FH92H/93H7EHDescriptionserviceNotSupportedsubFunctionNotSupportedincorrectMessageLengthOrInvalidFormatconditionsNotCorrectrequestSequenceErrorexceededNumberOfAttemptsrequestOutOfRangesecurityAccessDeniedrequiredTimeDelayNotExpiredInvalidKeygeneralProgrammingFailureresponsePendingserviceNotSupportedInActiveSessionVoltageTooHigh/voltageTooLowsubFunctionNotSupportedInActiveSessionIftwoormoreNRCsarereasonable,theECUcouldsendthenegativeresponsemessageaccordingtothefollowingpriorityrules：The7FhNRCtheForothers,theNRCwithsmallernumberhashigherThisserviceisusedbytheclienttoenabledifferentdiagnosticsessionsintheserver(s).Aenablesaspecificsetofdiagnosticservicesintheserver(s).MessageFormat#2DefaultSessionProgrammingSession#2DefaultSessionProgrammingSessionM010203ByteNameCvt#1RequestServiceIdentifierSub-function=[M10Sub-Function=[#2DefaultSessionProgrammingSessionSub-Function=[#2DefaultSessionProgrammingSessionM010203P2server[]=[#3#4MM00-FF00-FFP2*server[]=[ByteNameCvtValue#1PositiveResponseServiceIdentifierM50#5byte#1M00-FF#6byte#2]M00-FFTimingP2servervalueisprovidedin1msresolution.TimingP2*servervalueisprovidedin10msNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM10#3NegativeResponseCodeMNRCSub-functionParameterDefinitionHEXDescriptionCvt01DefaultSessionThisdiagnosticsessionenablesthedefaultdiagnosticsessionintheserver(s)anddoesnotsupportanydiagnosticapplicationtimeouthandlingprovisions.(e.g.noTesterPresentserviceisMnecessarytokeepthesessionnecessarytokeepthesessionactive).0203ProgrammingSessionThisdiagnosticsessionenablesalldiagnosticservicesrequiredtosupportedthememoryprogrammingofaserver.ExtendedDiagnosticSessionThisdiagnosticsessioncane.g.beusedtoenablealldiagnosticservicesrequiredtosupporttheadjustmentoffunctionslike“Idle,O,”ne’so.tnoetoenablediagnosticservices,whicharenotspecificallytiedtotheadjustmentoffunctions.MM22The22TheECUcurrentconditionsdonotallowthechangeofdiagnosticSession.MNRC(Hex)DescriptionCvt12Thesub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.MImplementationRulesThisserviceisusedbythediagnostictooltoenabledifferentofdiagnosticsessionsinaserver.Inordertoadiagnosticservicetheappropriatesessionhastobestartedfirst.Thereshallbeonlyonediagnosticsessionactiveatatime.Normal/DefaultSession(01h)shallbeenabledautomaticallybytheECUifnodiagnosticsessionhasbeenrequestedatpowerup.TheECUshallreturntoNormal/DefaultSession(01h)aftertimeoutofSession.TheECUshallbecapableofprovidingalldiagnosticfunctionalitydefinedforthedefaultdiagnosticsessionundernormaloperatingconditions.TheECUshallfirstsendaDiagnosticSessionControlPositiveResponse(50hmessagebeforethenewsessionbecomesactiveintheECU.APositiveResponse(50hmessageshallbereturnedbyanECUifthediagnostictoolrequestsasessionthatisalreadyrunning.IftheECUhasalreadyreceivedthesamerequestmessagepreviouslyandperformedtherequestedoperation,theECUshallcontinuetoperformthecurrentoperation(i.e.itisnotachangeofthesession).TheECUshallremaininitscurrentdiagnosticsessionifitisnotabletoswitchintotherequesteddiagnosticsession.TheTesterPresent(3Eh)serviceshallbeusedtokeepthenon-defaultdiagnosticsessionsactivebyretriggeringS3server.AlsoanyotherservicerequestshallretriggerAfunctionalTesterPresent(3Eh)requestwithoutresponsemaybesentatanytime,evenregardlessofanyotherserviceinprogress.Whenreceivingortransmittinganydiagnosticmessages,including3Ehservice,theECUReset

Fig3. SessiontransitiondiagramThisservicerequeststheservertoeffectivelyperformanECUresetbasedonthecontentoftheparametervalue(suppressPosRspMsgIndicationBit(bit7)notshown).MessageFormatRequest：#1#2NameRequestServiceIdentifierSub-Function=[HardResetCvtM11MSoftReset]0103PositiveResponse：Byte#1NamePositiveResponseServiceIdentifierSub-Function=[CvtMValue51#2ResetType:HardResetM01SoftReset]03NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM11#3NegativeResponseCodeMNRCOption01Option01DescriptionHardResetThisvalueidentifiesa“hardreset”conditionwhichsimulatestheCvtM0303power-on/start-upsequencetypicallyperformedafteraserverhasbeenpreviouslydisconnectedfromitspowersupply(i.e.battery).SoftReset Msesat”,hserimmediatelyrestarttheapplicationprogramifapplicable.Theperformedactionisimplementationspecificandnotdefinedbythestandard.Atypicalactionistorestarttheapplicationwithoutofpreviouslylearnedconfigurationdata,adaptivefactorsandotherlong-termadjustments.NegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13ThelengthofthemessageiswrongM22ThecriteriafortheECUResetrequestarenotmet.MImplementationRulesThepositiveresponseshallbesentbeforeperformingtheECUreset.Theexecutionofresetwilltake<TBD>ms,whichmeanstheECUcan’trespondtoanynewrequestsentwithinthistime.CommunicationControl（28H）Theserviceisusedto“switchon/off”thetransmissionand/orthereceptionofcertainmessagesof(a)server(s).MessageFormatByteNameCvt ByteNameCvt Value#1RequestServiceIdentifierM(hex)28#2Sub-Function=[EnableRxAndTxM00DisableRxAndTx]03CommunicationType=[NormalCommunicationMessagesNetworkManagementCommunication01#3MessagesM02NetworkManagementCommunicationMessagesAndNormalCommunicationMessages]03PositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM68Sub-Function=[EnableRxAndTx00#2EnableRxAndDisableTxM01DisableRxAndEnableTx02DisableRxAndTx]03NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM28#3NegativeResponseCodeMNRCNRC1213NRC121322ConditionsSub-functionparameterintherequestmessageisnotsupported.ThelengthofthemessageiswrongTheoperatingconditionsoftheserverarenotmettoperformtherequiredaction.Noneoftherequestedvaluesaresupportedbythedevice.CvtMMM31MSub-functionParameterDefinition：DescriptionEnableRxAndTxThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbeenabledforthespecifiedThisvalueindicatesthatthereceptionandtransmissionofmessagesshallbedisabledforthespecifiedCvt00M03MDataParameterDefinition：DescriptionNormalCommunicationMessagesThisvaluereferencesallapplication-relatedcommunication(inter-applicationsignalexchangebetweenmultiplein-vehicleservers).NetworkManagementCommunicationMessagesThisvaluereferencesallnetworkmanagementrelatedcommunication.NetworkManagementCommunicationMessagesAndNormalCommunicationMessagesThisvaluereferencesallnetworkmanagementandapplication-relatedcommunicationCvt01M02M03MImplementationRulesTherearenospecialgeneralimplementationrulesforthisservice.Thepurposeofthisserviceistoprovideameanstoaccessdataand/ordiagnosticservices,whichhaverestrictedaccessforsecurityorsafetyreasons.Diagnosticservicesfordownloading/uploadingroutinesordataintoaserverandreadingspecificmemorylocationsfromaserveraresituationswheresecurityaccessmayberequired.Improperroutinesordatadownloadedintoaservercouldpotentiallydamagetheelectronicsorothervehiclecomponentsorriskthecompliancetosafety,orsecuritystandards.Thesecurityconceptusesaseedandkeyrelationship.TheclientshallrequesttheservertounlockbysendingtheserviceSecurityAccess-RequestSeedmessage.Theservershallrespondbysendingaseed.Theseedistheinputparameterforthekeycalculationalgorithm.usedbytheclienttocalculatethecorrespondingkeyvalue.Inasecondstep,theclientshallrequestthekeybysendingthecalculatedkeytotheserverusingtheappropriateserviceSecurityAccess-SendKey.Theservershallcomparethiskeytooneinternallystored/calculated.Ifthetwonumbersmatch,thentheservershallenable(unlock)theaccesstospecificservices/dataandindicatethatwiththeserviceSecurityAccess-SendKey.Ifthetwonumbersdonotmatch,thisshallbeconsideredasafalseaccessattempt.Ifaccessisrejectedforanyotherreason,itshallnotbeconsideredasafalseaccessattempt.AninvalidkeyrequirestheclienttostartoverfromthebeginningwithaSecurityAccess-RequestSeedmessage.Ifaserversupportssecurity,butisalreadyunlockedwhenaSecurityAccess-RequestSeedmessageisreceived,thatservershallrespondwithaSecurityAccess-RequestSeedpositiveresponsemessageservicewithaseedvalueequalto(0).Theclientshallusethismethodtodetermineifaserverislockedbycheckingforaseed.TheSeed-KeyalgorithmforSecurityAccesMandatorKey((((seed>>4XORseed)<<3XOR)TheSecuritySeedis4Bytesrandomnumbers.ComputeKeyComputeKeyGenerateSeedCompareKeyComputeKeyComputeKeyGenerateSeedCompareKeySeedPoponseSendSeedKessey27$yyyRe$g. uysuMessageutThisservicerequestsaseedfromtheserver.Basedonthisseed,theclientisableoueegyoetrugevut：By#1#2Nameuvuyye=uPositiveResponse：CvMMux2701，11ByteNameCvtue#1PositiveResponseServiceIdentifierM67#2uyye=uM01，11uyd[]=[M#3seed#1(highbyte)…M…00-FF…#6#6seed#m(low]M00-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex)ConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22ThecriteriafortheSecurityAccessrequestarenotmet.M37requiredTimeDelayNotExpiredM.2.SendKeyThisservicesendsakeycalculatedbytheclienttotheserver.Theservershallcomparethiskeytooneinternallystored/calculated.Ifthetwonumbersmatch,thentheservershallenable(“unlock”)theclient’saccesstospecificservices/data.Request：#1NameRequestServiceIdentifierCvtM27#2=SendKeyM02，12SecurityKey[]=[M#3(highM00-FF………#6(low]M00-FFPositiveResponse：NameCvtValue#1PositiveResponseServiceIdentifierM67#2=SendKeyM02，12NegativeResponse：NameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNRC121322NRC12132224ConditionsSub-functionparameterintherequestmessageisnotsupported.Thelengthofthemessageiswrong.Thecriteriafortherequestarenotmet.requestSequenceErrorThe“sendKey”sub-functionisreceivedwithoutfirstreceivinga“requestSeed”requestmessage.invalidKeyexceededNumberOfAttemptsSendifthedelaytimerisactiveduetothenumberofCvtMMMM3536MMallowedfalseaccessattempts.allowedfalseaccessattempts.Sub-functionParameterDefinitionHEXDescriptionCvt01requestSeed（level1）M02sendKey（level1）M11requestSeed（level3flash）M12sendKey（level3flash）MImplementationRulesAfterPowerOn/ResettheECUisinlockedstate.Thesecurityaccessfailurecounterissetto0.TheECUshallwait10sbeforeacceptingthefirstRequestSeedmessageafterEcuReset/PowerOn.AfterthethirdfailureattempttheECUshallwait10sbeforeacceptingthe“RequestSeed”message.AstoredintheEEPROMoftheECU.OneveryPowerOn/Reset,theECUchecksforthisflag,thenwaitsagain10sbeforeacceptingthenext“RequestSeed”message(ItisallowedtoimplementtheSecurityAccessrequirementwithoutbasedontheFlag)AnySecurityAccessrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Ifthetesterrequestsaseed,ithastosendthecorrespondingkeytotheECU.ThissequenceisIfthetestersendsaconsecutive“RequestSeed”,therequestisacceptedandthesameseedisreturned,butthesecurityaccessfailurecounterisincremented.Ifthetestersendsaninvalidtherequestisrejectedwithnegativeresponsecode“InvalidKey”,thesequencesallbereset(anycurrentseedbecomesinvalid)andthesecurityaccessfailurecounterisincremented.Whenthesecuritycounterreachesthevalueof3(i.e.3failedtries),theECUshallwait10sbeforeacceptinganother“RequestSeed”message.Anysuchrequestduringthistimewillberejectedwiththenegativeresponsecode“Requiredtimedelaynotexpired”(37h).Whenthe10swaittimeiselapsedthesecurityaccessfailurecounterisdecrementedbyoneandanothertryisallowed.Whenduringthistrythesecurityaccessfailurecounterisincrementedagain(duetoaninvalidtheECUshallwaitagain10sbeforeacceptinganother“RequestSeed”message.Whenthistryisvalid,thesecurityaccessfailurecounterisnotchanged.BJEVusesfourstates(threedifferentlevels):Locked,Unlocked(Level1),Unlock(Level2)andUnlocked(Flash).TheECUcouldsupportsomeofthemaccordingtotherequirement.g. uyg. uysCuThisserviceshallbeusedtoindicatetoaserverthattheclientispresent.ThisserviceisrequiredintheabsenceofotherUDSservicestopreventserversfromautomaticallyreturningtonormaloperationandstopcommunication.MessageFormatRequest:#1#2NameRequestServiceIdentifierzeroSubFunctionCvtMM3E00PositiveResponse:ByteNameCvtValue#1PositiveResponseServiceIdentifierM7E#2zeroSubFunctionM00NegativeResponse:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM3E#3NegativeResponseCodeMNRCee):NRC(Hex)12ConditionsSub-functionparameterintherequestmessageisnotsupported.CvtM13Thelengthofthemessageiswrong.MSub-functionParameterDefinitionHEXDescriptionCvt00ZeroSubFunctionThisparametervalueisusedtoindicatethatnosub-functionvaluebesideMthesuppressPosRspMsgIndicationBitissupportedbythisservice.ImplementationRulesTherearenospecialgeneralimplementationrulesforthisservice.ThisserviceisusedtoenableanddisablethesettingofDiagnosticTroubleCodes,DTCs,intheECU(s).TheControlDTCSettingrequestmessagecanbeusedtostopthesettingofdiagnostictroublecodesinanindividualserveroragroupofservers.Iftheserverbeingaddressedisnotabletostopthesettingofdiagnostictroublecodes,itshallrespondwithaControlDTCSettingnegativeresponsemessageindicatingthereasonforthereject.MessageFormatRequest:Byte#1NameRequestServiceIdentifierCvtMValue(hex)85#2=OnM01Off]02PositiveResponse:ByteNameCvtValue#1PositiveResponseServiceIdentifierMC5#2OnM01Off]02NegativeResponse:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM85#3NegativeResponseCodeMNRCSub-functionParameterDefinitionHEXDescriptionCvt01OnTheserver(s)shallresumethesettingofdiagnostictroublecodesMaccordingtonormaloperatingconditionsNRC121322ConditionsNRC121322ConditionsSub-functionparameterintherequestmessageisnotsupported.ThelengthofthemessageiswrongTheoperatingconditionsoftheserverarenotmettoperformtherequiredaction.CvtMMU02OffTheserver(s)shallstopthesettingofdiagnostictroublecodes.MImplementationRulesThesettingofDTCsintheECUshallbeswitchedoffdirectlyaftertherequestControlDTCSettingwithsettingmode2(switchisreceived(Option:Suppresspositiveresponsemessageindicationbitisset)oraftersuccessfultransmissionofthepositiveresponse(Option:Suppresspositiveresponsemessageindicationbitisset).ThesettingofDTCsintheECUshallbeswitchedonagain,whenoneofthefollowingeventsoccurs:TherequestControlDTCSettingwithsettingmode1(switchon)isreceived(Option:Suppresspositiveresponsemessageindicationbitisset)oraftersuccessfultransmissionofthepositiveresponse(Option:Suppresspositiveresponsemessageindicationbitisnotset).TheECUpowersupplyvoltageisdown(resetorECUpowerdownevent).ThediagnosticsessionchangesfromDiagnosticSessiontoDefaultSession.TheservicesReadDTCInformation-ReportDTCByStatusMask,ReadDTCInformation-ReportSupportedDTCandClearDiagnosticInformationshallnotbeaffectedbythisservice.ReadDataByIdentifier（22H）TherequestmessagerequestsdatarecordvaluesfromtheserverbyoneormoredataIdentifier(s).WhenreceivingaReadDataByIdentifierrequest,theserverwillaccessthedataelementsoftherecordsspecifiedbythedataIdentifierparameter(s)andtransmittheirvalueinpositiveresponsecontainingtheassociateddataRecordparameter(s).MessageFormatRequest：NameCvt#1RequestServiceIdentifierM22DataIdentifier[]#1=[#2byte#1(MSB)M00-FF#3byte#2]M00-FF……..…DataIdentifier[]#m=[#n-1byte#1(MSB)U00-FF#nbyte#2]U00-FFPositiveResponse：NameCvtValue#1PositiveResponseServiceIdentifierM62DataIdentifier[]#1=[#2byte#1(MSB)M00-FF#3byte#2]M00-FFDataRecord[]#1=[#4data#1M00-FF…………#(k-1)+4…data#k]…U..00-FF…DataIdentifier[]#m=[#n-(o-1)-2byte#1(MSB)U00-FF#n-(o-1)-1byte#2]U00-FFDataRecord[]#m=[#n-(o-1)data#1U00-FF………#ndata#o]U00-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM22#3NegativeResponseCodeMNRCNRC1322ConditionsNRC1322ConditionsThelengthofthemessageiswrong.Theoperatingconditionsoftheserverarenotmettoperformtherequiredaction.NoneoftherequesteddataIdentifiervaluesaresupportedbythedevice.CvtMU31MDataParameterDefinition:FordataIdentifiersupportedbytheECU,pleaserefertoappendixB.ImplementationRulesThenumberofdataIdentifierstobereadwithinasinglerequestislimitedto1.WriteDataByIdentifier(2EH)TheWriteDataByIdentifierserviceisusedbytheclienttowriteadataRecordtoaserver.ThedataisidentifiedbyadataIdentifier.DataRecord[]DataRecord[]=[ByteNameCvt#1RequestServiceIdentifierM2EDataIdentifier[]#1=[#2byte#1(MSB)M00-FF#3byte#2]M00-FF#4…data#1…U…00-FF…#m+3data#m]U00-FFPositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM6EDataIdentifier[]#1=[#2byte#1(MSB)M00-FF#3byte#2]M00-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM2E#3NegativeResponseCodeMNRCNRC1322ConditionsNRC1322ConditionsCvtThelengthofthemessageiswrong.TegsfeUehtttrequiredaction(e.g.,thedataforaDataIdentifierisstoredinEEPROMandanEEPROMfailurehasoccurred).TheECUinternalconditionsdonotallowthewritingofanyDataIdentifier/IdentificationOption.ThesystemiscurrentlyinThesystemiscurrentlyinInputOutputControlByIdentifierserviceactivestage.Thesystemiscurrentlybusyatmodifyingmemory.Thevehicleismoving.ThedataIdentifierintherequestmessageisnotsupportedintheserverorthedataIdentifierissupportedforreadonlypurpose(viaReadDataByIdentifierservice).AnydatatransmittedintherequestmessageafterthedataIdentifierisinvalid(ifapplicabletothenode).ThedataIdentifier,whichreferenceaspecificaddress,issecuredandtheserverisnotinanunlockedstate.Theserverdetectsanerrorwhenwritingtoamemorylocation.MU31M33M72MDataParameterDefinition:FordataIdentifiersupportedbytheECU,pleaserefertoappendixB.ImplementationRulesItisthesystemsupplier’sresponsibilitythattheserverconditionsaremetwhenperforminganyactionrequestbythisservice,includingbutnotlimitedtothefollowing:1)Thehighandlowvoltagecurrentfaultdoesnotexistinthesystem.Pleasespecifyotherrulesinyourmodule.InputOutputControlByIdentifier(2FH)Thisserviceisusedbythetestertosubstituteavalueforaninputsignal,internalECUfunctionand/orcontrolanoutputofanelectronicreferencedbyaninputOutputDataIdentifier.MessageFormatRequest：ByteNameCvtValue(hex)#1RequestServiceIdentifierM2FDataIdentifier[]#1=[#2byte#1(MSB)M00-FF#3byte#2]M00-FFControlOptionRecord#1[]=[#4ControlState#1/InputOutputControlParameterM/U00-FF…………#4+(m-1)ControlState#m]C00-FFControlEnableMaskRecord#1[]=[#4+m ControlMask#1C00-FF… ………#4+m+(r-1) ControlMask#r]C00-FFPositiveResponse：NameCvtValue#1 PositiveResponseServiceIdentifierM6FDataIdentifier[]#1=[#2 (MSB)M00-FF#3 ]M00-FFControlStatusRecord#1[]=[#4ControlState#1/InputOutputControlParameterC00-FF…………#4+(m-1)ControlState#m]C00-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM2F#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRCConditionsCvt(Hex)13Thelengthofthemessageiswrong.M22ConditionsNotCorrectM24TebnsdtgaM3131TheserverdoesnotsupporttherequesteddataIdentifier.TheuseroptionalinputOutputControlParametercontainsinvaliddata.OneormultipleofthecontrolStateareinvalid.Thecorrespondingsecurityisnotgrantedtoperformtherequiredservice.M33MOption(Hex)Option(Hex)00DescriptionCvtreturnControlToECUThisparameterspecifiesthattheECUshalltakecontrolofthevalueofdataIdentifier.ResetToDefaultThevalueshallindicatetotheserverthatitisrequestedtoresettheinputsignal,in-ternalparameteroroutputsignalreferencedbytheinputOutputLocalIdentifiertoitsdefaultstate.NumberofcontrolStatebytesinrequest:0NumberofcontrolStateinpos.response:dependsondataIdentifierShortTermAdjustmentThis parameter specifies that the ECU shall set the value M01M03MdataIdentifiertorequestvalueofthecontrolStateParamter.Ifdiagnosticcommunicationwiththetesterisbroken,thecontrolshallbegivenbacktotheECU.ImplementationRuleItisthesystemresponsibilitythattheserverconditionsaremetwhenperforminganyactionrequestbythisservice,includingbutnotlimitedtofollowing:1)Thehighandlowvoltagecurrentfaultdoesnotthe2)Thecontrolledincludingtheactuator,hasnofault.Pleasespecifyotherrulesinmodule.(14H)Thisserviceisusedbytheclienttocleardiagnosticinformationintheserver’smemory.Request：NameCvt#1RequestServiceIdentifierGroupOfDTC[]=[M14#2groupOfDTCHighByteM00-FF#3groupOfDTCMiddleByteM00-FF#4#4groupOfDTCLowByte]M00-FF1322CvtMM311322CvtMM31ThelengthofthemessageiswrongTheECUinternalconditionsdonotallowdeletionofthediagnosticinformationstoredinthenode.Theseare:Thevehicleismoving.Thesystemiscurrentlyinorshutdownprocess.ThesystemiscurrentlyinI/OControl.ThesystemisintheprocessofchangingsomeMemorycontent.WronggroupOfDTCvaluesinrequest.MByte#1NamePositiveResponseServiceIdentifierCvtMValue54NegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM14#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC)NRC(Hex) ConditionsDataParameterDefinition：Option(Hex)Option(Hex)FFFFFFxxxxxxDescriptionAllGroups(allAparticularDTCImplementationRuleTheimplementationofclearingdiagnosticinformationwilltakethetimeof<TBD>seconds.TheDTCsstoredinRAMandnon-volatilememoryshallbeclearedbeforethepositiveresponseissent.WiththeparametergroupOfDTCitisalsopossibletoclearonlyaspecificgroupofDTCsoraspecificDTC.AsubsequentcalltoreadoutthefaultmemoryshallnotretrieveanyDTCwhichhasbeensetbeforethelastexecutionofClearDiagnosticInformation.EvenifnoDTCwasstored,theECUshallreturnwithapositiveresponse.Thereshallbenosequencedependencytoanyotherservice.Evenifthefaultmemorywasnotread,itmaybecleared.ADTCcanjustbeclearedbytesterwithservice14h.(19H)Thisserviceallowsaclienttoreadthestatusofserver-residentDiagnostic(DTC)informationfromanyserver,orgroupofserverswithinavehicle.Request：#1#2NameRequestServiceIdentifierSub-Function=ReportNumberOfDTCByStatusMaskCvtMM1901#3DTCStatusMaskM00-FFPositiveResponse：ByteNameCvtValue#1PositiveResponseServiceIdentifierM59Sub-Function=M#2ReportNumberOfDTCByStatusMask01#3DTCStatusAvailabilityMaskM01-FFDTCFormatIdentifier=#4ISO15031-6DTCFormatM00DTCCount[]=[#5DTCCountHighByteM00-FF#6DTCCountLowByte]M00-FFNegativeResponse：ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM19#3NegativeResponseCodeMNRCNegativeResponseCodes(NRC):NRCConditionsCvt12Sub-functionparameterintherequestmessageisnotsupported.M13ThelengthofthemessageiswrongM31requestOutOfRangeMByte#1NameRequestServiceIdentifierSub-Function=CvtMMByte#1NameRequestServiceIdentifierSub-Function=CvtMM19#2ReportDTCByStatusMask02#3DTCStatusMaskM00-FFPositiveResponse：ByteNameCvtValue#1PositiveResponseService