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

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

《北京新能源汽车整车控制器系统诊断规范.docx》由会员分享，可在线阅读，更多相关《北京新能源汽车整车控制器系统诊断规范.docx（63页珍藏版）》请在冰豆网上搜索。

北京新能源汽车整车控制器系统诊断规范北京新能源汽车整车控制器系统诊断规范整车控制器系统诊断规范“EV160”文件编号：

“EV160”编制：

校对：

审核：

“业务高级经理”会签：

“控制系统集成主管”批准：

“部长”XXX年XXX月版本信息版本信息版本日期编制校对审核更新描述V1.0初始版本V1.1崔晓静崔晓静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、添加故障码中英文对照表；版本信息21.参考文献52.网络拓扑53.诊断接口64.诊断需求74.1.诊断协议7物理层7数据链路层7网络层7应用层时间参数84.2.DiagnosticServices（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）375.故障定义386.故障码DTC中英文对照表38附录A:

冻结帧信息39附录B:

41B.1版本信息参数列表：

41B.2数据流参数列表：

41B.3版本信息参数定义43B.4数据流参数定义45术语DTC故障诊断码BSBlocksizeSTminMinimumSeparationTimeC有条件的M强制性执行U用户选用TBD待定义SID服务标识符DID数据标识符NRC负响应码UDS统一的诊断服务Server服务器Client客户端ECU电控单元1.参考文献参考文献NO.参考文档题目1ISO11898-1:

2003Roadvehicles-Controllerareanetwork（CAN）Part1:

Datalinklayerandphysicalsignaling2ISO11898-2:

2003Roadvehicles-Controllerareanetwork（CAN）Part2:

High-speedmediumaccessunit3ISO11898-5:

2007Roadvehicles-Controllerareanetwork（CAN）Part5:

High-speedmediumaccessunitwithlow-powermode4ISO15765-2:

2004RoadVehicle-DiagnosticonCANPart2:

NetworkingLayerServices5ISO15765-3:

2004RoadVehicle-DiagnosticonCANPart3:

ApplicationLayerServices6ISO14229-1:

2006RoadVehicle-DiagnosticSystemsDiagnosticServicesSpecification7ISO15031-6:

2005Roadvehicles-Communicationbetweenvehicleandexternalequipmentforemission-relateddiagnosticPart6:

Diagnostictroublecodedefinitions2.网络拓扑网络拓扑“由网络工程师统一发布网络拓扑”Fig1.C70GB-2014整车网络拓扑结构3.诊断接口诊断接口Fig2.OBD诊断接口管脚描述1EVBUSCAN_H2/3/4接地5接地6/7/8/9EVBUSCAN_L10/11/12/13/14/15/16电源Tab1.OBD诊断接口针脚定义“由线束工程师统一发布OBD接口定义”4.诊断需求诊断需求4.1.诊断协议诊断协议4.1.1.物理层物理层物理层应满足ISO11898-2要求及北京新能源汽车股份有限公司企业标准新能源汽车高速CAN网络节点级电子控制单元（ECU）技术要求要求。

4.1.2.数据链路层数据链路层数据链路层应满足ISO11898-1要求。

所有诊断请求和应答帧的数据长度应为8字节，否则电控单元将忽略该诊断请求帧。

当诊断响应长度不足8字节时，空余的字节应用0xAA填充。

4.1.3.网络层网络层网络层应满足ISO15765-2要求和下述要求：

4.1.3.1.寻址方式寻址方式可以支持物理寻址和功能寻址。

诊断消息ID描述见下表：

控制器名称简称物理寻址诊断请求ID（Hex）诊断响应ID（Hex）功能寻址诊断请求ID（Hex）实施网段驱动电机控制器MCU0x7E00x7E80x7DFEVBUSTab2.诊断ID列表“由网络工程师统一发布所有诊断ID分配，各系统填写各自的诊断ID至上表”4.1.3.2.网络层时间参数网络层时间参数ParameterValueUnitBS8-STmin20msParameterTimeoutPerformanceRequirementUnitN_As/N_Ar70n/amsN_Brn/a70msN_Bs150n/amsN_Csn/a70msN_Cr150n/amsTab3.网络层时间参数需求4.1.4.应用层时间参数应用层时间参数ParameterMinMaxTimeoutUnitP2server050n/amsP2clientn/an/a150msP2*server02000n/amsP2*clientn/an/a5000msP3client_phys2P2servern/an/amsP3client_funcP2server_maxn/an/amsParameterMinNominalTimeoutUnitS3servern/an/a5000msS3client020004000msTab4.应用层时间参数需求4.2.DiagnosticServices（ISO14229-1）ServicesshallbeimplementedaccordingtoISO14229-1.Additionaldetailsarespecifiedinthissection.4.2.1.SupportedDiagnosticServicesTheoverviewofECUsupporteddiagnosticservicesisdescribedinthefollowingtable.Table5SupporteddiagnosticservicesofECUDiagnosticServicesListSessionSecurityAccessAddressingSID（Hex）ServiceNameDefaultExtendedProgrammingPhysicalAddressFunctionAddress10DiagnosticSessionControl11EcuReset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier132FInputOutputControlByIdentifier114ClearDiagnosticInformation19ReadDTCInformation31RoutineControl1334RequestDownLoad336TransferData337RequestTransferExit3说明：

访问权限1表示需要扩展安全级权限，3表示需要编程安全级权限。

TheservicesneedtosupportsuppressPositveResponseBit（SPRS）areshowedinfollowingtable.Tab5.ServicessupportedSPRSbitDiagnosticServicesListSupportSPRSbitSID（Hex）ServiceName10DiagnosticSessionControl11EcuReset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier14ClearDiagnosticInformation19ReadDTCInformation2FInputOutputContorlByIdentifier31RoutineControl34RequestDownload36TransferData37RequestTransferExitThenegativeResponseCodes（NRC）usedbyECUaredefinedasfollows:

Tab6.NegativeResponseCodesNRC（Hex）Description11HserviceNotSupported12HsubFunctionNotSupported13HincorrectMessageLengthOrInvalidFormat22HconditionsNotCorrect24HrequestSequenceError36HexceededNumberOfAttempts31HrequestOutOfRange33HsecurityAccessDenied37HrequiredTimeDelayNotExpired35HInvalidKey72HgeneralProgrammingFailure78HresponsePending7FHserviceNotSupportedInActiveSession92H/93HVoltageTooHigh/voltageTooLow7EHsubFunctionNotSupportedInActiveSessionIftwoormoreNRCsarereasonable,theECUcouldsendthenegativeresponsemessageaccordingtothefollowingpriorityrules：

The7FhNRChavethehighestpriority;Forothers,theNRCwithsmallernumberhashigherpriority.4.2.2.DiagnosticSessionControl（10H）Thisserviceisusedbytheclienttoenabledifferentdiagnosticsessionsintheserver（s）.Adiagnosticsessionenablesaspecificsetofdiagnosticservicesintheserver（s）.4.2.2.1.MessageFormatRequest：

ByteNameCvtValue（hex）#1RequestServiceIdentifierM10#2Sub-function=DefaultSessionProgrammingSessionExtendedDiagnosticSessionM010203PositiveResponse：

ByteNameCvtValue#1PositiveResponseServiceIdentifierM50#2Sub-Function=DefaultSessionProgrammingSessionM010203ExtendedDiagnosticSessionP2server=#3byte#1M00-FF#4byte#2M00-FFP2*server=#5byte#1M00-FF#6byte#2M00-FFTimingP2servervalueisprovidedin1msresolution.TimingP2*servervalueisprovidedin10msresolution.NegativeResponse：

ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM10#3NegativeResponseCodeMNRCSub-functionParameterDefinitionHEXDescriptionCvt01DefaultSessionThisdiagnosticsessionenablesthedefaultdiagnosticsessionintheserver（s）anddoesnotsupportanydiagnosticapplicationtimeouthandlingprovisions.（e.g.noTesterPresentserviceisnecessarytokeepthesessionactive）.M02ProgrammingSessionThisdiagnosticsessionenablesalldiagnosticservicesrequiredtosupportedthememoryprogrammingofaserver.M03ExtendedDiagnosticSessionThisdiagnosticsessioncane.g.beusedtoenablealldiagnosticservicesrequiredtosupporttheadjustmentoffunctionslike“IdleSpeed,COValue,etc.”intheserversmemory.Itcanalsobeusedtoenablediagnosticservices,whicharenotspecificallytiedtotheadjustmentoffunctions.MNegativeResponseCodes（NRC）NRC（Hex）DescriptionCvt12Thesub-functionparameterintherequestmessageisnotsupported.M13Thelengthofthemessageiswrong.M22TheECUcurrentconditionsdonotallowthechangeofdiagnosticSession.M4.2.2.2.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.Fig3.Sessiontransitiondiagram4.2.3.ECUReset（11H）ThisservicerequeststheservertoeffectivelyperformanECUresetbasedonthecontentoftheResetTypeparametervalue（suppressPosRspMsgIndicationBit（bit7）notshown）.4.2.3.1.MessageFormatRequest：

ByteNameCvtValue（hex）#1RequestServiceIdentifierM11#2Sub-Function=ResetType:

HardResetSoftResetM0103PositiveResponse：

ByteNameCvtValue#1PositiveResponseServiceIdentifierM51#2Sub-Function=ResetType:

HardResetSoftResetM0103NegativeResponse：

ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM11#3NegativeResponseCodeMNRCSub-functionParameterDefinitionOption（Hex）DescriptionCvt01HardResetThisvalueidentifiesa“hardreset”conditionwhichsimulatesthepower-on/start-upsequencetypicallyperformedMafteraserverhasbeenpreviouslydisconnectedfromitspowersupply（i.e.battery）.03SoftResetThisvalueidentifiesa“softreset”condition,whichcausestheservertoimmediatelyrestarttheapplicationprogramifapplicable.Theperformedactionisimplementationspecificandnotdefinedbythestandard.Atypicalactionistorestarttheapplicationwithoutreinitializingofpreviouslylearn