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

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

2、改為9個(gè)字節(jié)；12、添加故障碼中英文對(duì)照表；目錄版本信息2.1. 參考文獻(xiàn)5.2. 網(wǎng)絡(luò)拓?fù)?.3. 診斷接口 6.4. 診斷需求7.4.1. 診斷協(xié)議Z.4.1.1. 物理層7.4.1.2. 數(shù)據(jù)鏈路層 7.4.1.3. 網(wǎng)絡(luò)層7.4.1.4. 應(yīng)用層時(shí)間參數(shù)84.2. Diag no Stic Services (ISO14229-1) 84.2.1. Supported Diag no Stic Services9.4.2.2. DiagnosticSessionControl(10H) 1 14.2.3. ECUReset (11H)13.4.2.4. CommunicationCon

3、trol (28H) 1 44.2.5. SecurityAccess(27H) 1.54.2.6. TesterPresent(3EH) 214.2.7. ControlDTCSetting(85H)214.2.8. ReadDataByldentifier (22H)234.2.9. WriteDataByIdentifier (2EH)244.2.10. InputOutputControlByldentifier (2FH)264.2.11. ClearDiagnosticInformation (14H)274.2.12. ReadDTC In formation (19H)284.

4、2.13. Rout in eC on trol (31H)354.2.14. RequestDownLoad(34H)374.2.15. TransferData (36H)374.2.16. RequestTransferExit (37H).37.5. 故障定義386. 故障碼DTC中英文對(duì)照表 .38附錄A:凍結(jié)幀信息 .4.0附錄B:4.2B.1版本信息參數(shù)列表：42B.2數(shù)據(jù)流參數(shù)列表： 42B.3版本信息參數(shù)定義 44B.4數(shù)據(jù)流參數(shù)定義 46術(shù)語(yǔ)DTC故障診斷碼BSBlock sizeSTmi nMinimum Separation TimeC有條件的M強(qiáng)制性執(zhí)行U用戶選用TB

5、D待定義SID服務(wù)標(biāo)識(shí)符DID數(shù)據(jù)標(biāo)識(shí)符NRC負(fù)響應(yīng)碼UDS統(tǒng)一的診斷服務(wù)Server服務(wù)器Clie nt客戶端ECU電控單元1. 參考文獻(xiàn)NO.參考文檔題目1ISO11898-1: 2003Road vehicles - Con troller area n etwork (CAN) Part 1:Data link layer and physical sig nali ng2ISO11898-2: 2003Road vehicles - Con troller area n etwork (CAN)Part 2: High-speed medium access un it3ISO118

6、98-5: 2007Road vehicles - Con troller area n etwork (CAN)Part 5: High-speed medium access unit with low-power mode4ISO15765-2: 2004Road Vehicle - Diagnostic on CAN Part 2: Networki ng Layer Services5ISO15765-3: 2004Road Vehicle - Diagnostic on CAN Part 3: Applicati on Layer Services6ISO14229-1: 2006

7、Road Vehicle - Diag no stic Systems Diag no stic Services Specificati on7ISO15031-6: 2005Road vehicles - Communi cati on betwee n vehicle and external equipment for emission-related diagnostic Part 6: Diagno stic trouble code defi niti ons2. 網(wǎng)絡(luò)拓?fù)溆删W(wǎng)絡(luò)工程師統(tǒng)一發(fā)布網(wǎng)絡(luò)拓?fù)洹盋70GB項(xiàng)目2014年度型整車網(wǎng)絡(luò)拓?fù)浣Y(jié)構(gòu)JSOVBU5 SWhgCS011

8、898-2!3血低 unUMiBM5：5遠(yuǎn)話，豪屯鳥4： * VCD：_* - - - ei.VfflL3- g 林dVEK-JL*BOS.車常忡整廉；1*龜H， DLC. $#(*i Kt.&i* 品電MG自嗆Tift中制薑| CH&S.iM* i*IHC 乘生搶鼻Jhmv-眈D9I尿鼻flhi*5M.罵廉鼎屋1擱我i區(qū)骨Ji 嚴(yán)iFL31E ：D50CBKM專島押j Ahl-u SLRifVi At4W& tnr*t： AarftadU. tSMi AdirfijK 右首*：EUmSman 胃特眸：QWV9 皿 CAM ECUS LINEV5 CANFCBUSL.Fig 1. C70GB-

9、2014整車網(wǎng)絡(luò)拓?fù)浣Y(jié)構(gòu)3. 診斷接口(1(口口 UO口口口 8勺口口口 口口口 口口1：Fig 2. OBD診斷接口管腳描述1EVBUS CAN H2/3/4接地5接地6/7/8/9EVBUS CAN L10/11/12/13/14/15/16電源Tab 1. OBD診斷接口針腳定義由線束工程師統(tǒng)一發(fā)布 OBD接口定義”4. 診斷需求4.1.診斷協(xié)議411物理層物理層應(yīng)滿足ISO11898-2要求及北京新能源汽車股份有限公司企業(yè)標(biāo)準(zhǔn) 新能源汽車高速 CAN網(wǎng)絡(luò)節(jié)點(diǎn)級(jí)電子控制單元（ECU）技術(shù)要求要求。412數(shù)據(jù)鏈路層數(shù)據(jù)鏈路層應(yīng)滿足ISO11898-1要求。所有診斷請(qǐng)求和應(yīng)答幀的數(shù)據(jù)長(zhǎng)度應(yīng)為

10、 8字節(jié)，否則電控單元將忽略該診斷 請(qǐng)求幀。當(dāng)診斷響應(yīng)長(zhǎng)度不足 8字節(jié)時(shí)，空余的字節(jié)應(yīng)用OxAA填充。413網(wǎng)絡(luò)層網(wǎng)絡(luò)層應(yīng)滿足ISO15765-2要求和下述要求：4.131.尋址方式可以支持物理尋址和功能尋址 診斷消息ID描述見下表：控制器名稱簡(jiǎn)稱物理尋址診斷請(qǐng)求ID(Hex)診斷響應(yīng)ID(Hex)功能尋址診斷請(qǐng)求ID(Hex)實(shí)施網(wǎng)段驅(qū)動(dòng)電機(jī)控制器MCU0x7E00x7E80x7DFEVBUSTab 2.診斷ID列表由網(wǎng)絡(luò)工程師統(tǒng)一發(fā)布所有診斷ID分配，各系統(tǒng)填寫各自的診斷ID至上表”4.1.3.2.網(wǎng)絡(luò)層時(shí)間參數(shù)ParameterValueUn itBS8-STmi n20msParame

11、terTimeoutPerforma nee Requireme ntUn itN As/N Ar70n/amsN Brn/a70msN Bs150n/amsN Csn/aV36Tran sferDataVVV37RequestTra nsferExitVVV說(shuō)明：訪問(wèn)權(quán)限V 1表示需要擴(kuò)展安全級(jí)權(quán)限，V3表示需要編程安全級(jí)權(quán)限。The services n eed to support suppressPositveResp on seBit (SPRS) are showed in following table.Tab 5. Services supported SPRS bitDiag

12、 no stic Services ListSupport SPRS bitSID (Hex)Service Name10Diag no sticSessio nCon trolVDiag no stic Services ListSupport SPRS bitSID (Hex)Service Name11EcuResetV27SecurityAccess28Communi cati onCon trolV3ETesterPrese ntV85Con trolDTCSetti ngV22ReadDataByIde ntifier2EWriteDataByIde ntifier14ClearD

13、iag no sticI nformati on19ReadDTCI nformatio n2FIn putOutputCo ntorlBylde ntifier31Routi neCo ntrol34RequestDow nl oad36Tran sferData37RequestTra nsferExitThe n egativeResp on seCodes (NRC) used by ECU are defi ned as follows:Tab 6. Negative Response CodesNRC(Hex)Descripti on11HserviceNotSupported12

14、HsubF unctionN otSupported13Hin correctMessageLe ngthOrI nvalidFormat22Hcon diti on sNotCorrect24HrequestSeque nceError36HexceededNumberOfAttempts31HrequestOutOfRa nge33HsecurityAccessDe nied37HrequiredTimeDelayNotExpired35HIn validKey72Hgen eralProgram min gFailure78Hresp on sePe nding7FHserviceNot

15、SupportedI nActiveSessi on92H/93HVoltageTooHigh / voltageTooLow7EHsubF unctionN otSupportedl nActiveSessi onIf two or more NRCs are reas on able, the ECU could send the n egative resp onse message accord ing to the followi ng priority rules The 7Fh NRC have the highest priority; For others, the NRC

16、with smaller number has higher priority.422 DiagnosticSessionControl 10H)This service is used by the clie nt to en able differe nt diag no stic sessi onsin the server(s). A diagnostic session enables a specific set of diagnostic services in the server(s).422.1. Message FormatRequestByteNameCvtValue(

17、hex)#1RequestServiceIde ntifierM10#2Sub-fu nction =DefaultSessi onProgrammi ngSessi onExte ndedDiag no sticSessi on M010203Positive Resp onseByteNameCvtValue#1PositiveResp on seServiceIde ntifierM50#2Sub-F unction=DefaultSessi onProgrammi ngSessi onExte ndedDiag no sticSessi on M010203P2server=#3byt

18、e#1M00-FF#4byte#2M00-FFP2*server=#5byte#1M00-FF#6byte#2M00-FFTiming P2server value is provided in 1ms resolution.Timing P2*server value is provided in 10ms resolution.Negative Resp onseByteNameCvtValue#1NegativeResp on seServiceIde ntifier:M7F#2RequestServiceIde ntifierM10#3NegativeResp on seCodeMNR

19、CSub-function Parameter DefinitionHEXDescripti onCvt01DefaultSessi onThis diag no stic sessi on en ables the default diag no stic sessi on in the server(s)and does not support any diagnostic application timeout han dli ng provisi ons. (e.g. no TesterPrese nt service isMn ecessary to keep the sessi o

20、n active).02Programmi ngSessio nThis diag no stic sessi on en ables all diag no stic services required to supported the memory program ming of a server.M03Exte ndedDiag no sticSessi onThis diag no stic sessi on can e.g. be used to en able all diag no stic services required to support the adjustme nt

21、 of functions like Speed, CO Value, etc.” in the server s memory. It carto enable diagnostic services, which are not specifically tied to the adjustme nt of fun cti ons.Mi also be usedIdleNegative Respo nse Codes (NRC)NRC(Hex)Descripti onCvt12The sub-fu nction parameter in the request message is not

22、 supported.M13The len gth of the message is wrong.M22The ECUcurre nt con diti ons do not allow the cha nge ofdiag no stic Sessi on.M4222 Implementation RulesThis service is used by the diag no stic tool to en able differe nt types of diag no stic sessions in a server. In order to execute a diagnosti

23、c service the appropriate session has to be started first.There shall be only one diagnostic session active at a time.Normal/Default Session (01h) shall be en abled automatically by the ECU if no diag no stic sessi on has bee n requested at power up.The ECU shall return to Normal/Default Session (01

24、h) after timeout of Exte ndedDiag no stic Sessi on.The ECU shall be capable of providing all diagnostic functionality defined for the default diag no stic sessi on un der no rmal operati ng con diti ons.The ECU shall first send a Diag no sticSessio nCon trol Positive Resp onse (50h xx) message befor

25、e the new sessi on becomes active in the ECU.A DiagnosticSessionControl Positive Response (50h xx) message shall be returned by an ECU if the diagnostic tool requests a session that is already running. If the ECU has already received the same request message previously and performed the requested op

26、eratio n, the ECU shall con ti nue to perform the curre nt operatio n (i.e. it is not a cha nge of the sessi on).The ECU shall rema in in its curre nt diag no stic sessi on if it is not able to switch into the requested diag no stic sessi on.The TesterPrese nt (3Eh) service shall be used to keep the

27、 non-default diag no stic sessi ons active by retriggeri ng S3server. Also any other service request shall retrigger S3server.A functional TesterPresent(3Eh) request without responsemay be sent at any time, eve n regardless of any other service in progress.Whe n recei ving or tran smitt ing any diag

28、 no stic messages, in cludi ng 3Eh service,the S3servertimer will reset.Default0310 03Extended10 01Programmtng11 03111 03 11001Fig 3. Sessi on tran siti on diagram423 ECUReset (11H)This service requests the server to effectively perform an ECU reset based on the content of the ResetType parameter va

29、lue (suppressPosRspMsgIndicationBit(bit 7) not show n).423.1. Message FormatRequestByteNameCvtValue(hex)#1RequestServicelde ntifierM11#2Sub-F un cti on= ResetType: HardResetSoftResetM01 03Positive Resp onseByteNameCvtValue#1PositiveResp on seServicelde ntifierM51#2Sub-F un cti on=ResetType: HardRese

30、t SoftResetM01 03Negative Resp onseByteNameCvtValue#1NegativeResp on seServicelde ntifierM7F#2RequestServicelde ntifierM11#3NegativeResp on seCodeMNRCSub-function Parameter DefinitionOptio n (Hex)Descriptio nCvt01HardResetThis value identifies a“ hard reset ” condition which simulateM s tpower- on /

31、 start-up seque nee typically performed after a server has bee n previously disc onn ected from its power supply (i.e. battery).03SoftResetThis value identifies a“ soft reset” condition, which causesimmediately restart the application program if applicable. The performed action is implementation spe

32、cific and not defined by the standard. A typical action is to restart the applicati on without rein itializ ing of previously lear ned con figurati on data, adaptive factors and other Ion g-term adjustme nts.M he servNegative Respo nse Codes (NRC)NRC (Hex)Con diti onsCvt12Sub-fu ncti on parameter in

33、 the request message is not supported.M13The len gth of the message is wrongM22The criteria for the ECUReset request are not met.M4232 Implementation RulesThe positive resp onse shall be sent before perform ing the ECU reset.The executi on of reset will take ms, which means the ECU caresp ond to any

34、 new request sent with in this time.424 Communicationcontrol (28H)The service is used to “ switch on/off ” the transmission and/or the reception of certa in messages of (a) server(s).4.2.4.1. Message FormatRequestByteNameCvtValue (hex)#1RequestServicelde ntifierM28#2Sub-F unction = En ableRxA ndTx D

35、isableRxA ndTx M0003#3Commun icati on Type=NormalCom muni cati onM essagesNetworkMa nageme ntCom muni cati on MessagesNetworkMa nageme ntCom muni cati onM essages An dNormalCom muni catio nM essages M010203Positive Resp onseByteNameCvtValue#1PositiveResp on seServicelde ntifierM68Sub-F unction = En

36、ableRxA ndTx00#2En ableRxA ndDisableTxM01DisableRxA ndE nableTx02DisableRxA ndTx 03Negative Resp onseByteNameCvtValue#1NegativeResp on seServicelde ntifierM7F#2RequestServicelde ntifierM28#3NegativeResp on seCodeMNRCNegative Respo nse Codes(NRC)NRC (Hex)Con diti onsCvt12Sub-fu ncti on parameter in t

37、he request message is not supported.M13The len gth of the message is wrongM22The operati ng con diti ons of the server are not met to perform the required action.M31None of the requested Communi cati on Type values are supported by the device.MSub-function Parameter Definition：Optio n( hex)Descripti

38、 onCvt00En ableRxA ndTxThis value in dicates that the recepti on and tran smissi on of messages shall be en abled for the specified Communi catio nType.M03DisableRxA ndTxThis value in dicates that the recepti on and tran smissi on of messages shall be disabled for the specified Communi cati on Type.

39、MData Parameter Defi nition：Optio n( hex)Descriptio nCvt01NormalCom mun icati onM essagesThis value references all applicati on-related com muni cati on (inter-application signal exchange between multiple in-vehicle servers).M02NetworkMa nageme ntCom muni cati onM essages This value references all n

40、 etwork man ageme nt related com muni cati on.M03NetworkMa nageme ntCom muni cati onM essagesA ndNormalCommu ni cati onM essagesThis value references all n etwork man ageme nt and application-related com municationM4242 Implementation RulesThere are no special general implementation rules for this s

41、ervice.425 SecurityAccess( 27H)The purpose of this service is to provide a means to access data an d/or diag no stic services, which have restricted access for security or safety reasons. Diagnostic services for dow nl oad in g/upload ing routi nes or data into a server and readi ng specific memory

42、locati ons from a server are situati ons where security access may be required. Improper rout ines or data dow nl oaded in to a server could pote ntially damage the electr onics or other vehicle comp onents or risk the vehicleafetcoorplia nee to s security sta ndards. The security con cept uses a se

43、ed and key relati on ship.The client shall request the server to uniock by sending the service SecurityAccess-RequestSeedmessage.The server shall resp ond by sending a seed. The seed is the in put parameter for the key calculati on algorithm. It is used by the clie nt to calculate the corresp onding

44、 key value.In a second step, the client shall request the key comparison by sending the calculated key to the server using the appropriate service SecurityAccess-Se ndKey. The server shall compare this key to one internally stored/calculated. If the two nu mbers match, the n the server shall en able

45、 (uni ock) the clie nt acsessto specific services/dataand indicate that with the service SecurityAccess-SendKey.If the two nu mbers do not match, this shall be con sidered as a false access attempt. If access is rejected for any other reas on, it shall not be con sidered as a false access attempt. A

46、n in valid key requires the clie nt to start over from the beg inning with a SecurityAccess-RequestSeed message.If a server supports security, but is already uni ocked whe n a SecurityAccess-RequestSeedmessageis received, that server shall respond with a SecurityAccess-RequestSeecpositive response m

47、essageservice with a seed value equal to zero (0). The clie nt shall use this method to determ ine if a server is locked by check ing for a non-zero seed.The Seed-Key algorithmfor SecurityAccess (Man datory)：Key = (seed4) XOR seed)3) XOR seed)The Security Seed is4 Bytes ran dom nu mbers.TesterECUCom

48、puteKeyR -Secuity Acces， 間昨 Seed-$27；s$xxopspOnse cosi t i ve Res-p- 略一_d $67 $xx Y Send 沖 $6Gen erateSeedComputeKeyCompareKeyQPOnse/一一一一 $67 $yy/ Accept 矽$7尸 $27 $35 Rj ect Key $7Fig 4. Security Access procedure4.2.5.1. Message Format4.2.5.1.1. Request SeedThis service requests a seed from the server. Based on this