![北京新能源汽車整車控制器系統(tǒng)診斷規(guī)范[分享借鑒]_第1頁(yè)](http://file1.renrendoc.com/fileroot_temp2/2020-10/5/a5e95d1d-a0ff-47bd-81f5-8881b2d79016/a5e95d1d-a0ff-47bd-81f5-8881b2d790161.gif)
![北京新能源汽車整車控制器系統(tǒng)診斷規(guī)范[分享借鑒]_第2頁(yè)](http://file1.renrendoc.com/fileroot_temp2/2020-10/5/a5e95d1d-a0ff-47bd-81f5-8881b2d79016/a5e95d1d-a0ff-47bd-81f5-8881b2d790162.gif)
![北京新能源汽車整車控制器系統(tǒng)診斷規(guī)范[分享借鑒]_第3頁(yè)](http://file1.renrendoc.com/fileroot_temp2/2020-10/5/a5e95d1d-a0ff-47bd-81f5-8881b2d79016/a5e95d1d-a0ff-47bd-81f5-8881b2d790163.gif)
版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)
文檔簡(jiǎn)介
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ù);8、 刪除19 06子服務(wù);9、 status改為僅bit0、3支持10、刪除NRC11;11、
2、F184修改為9個(gè)字節(jié);12、添加故障碼中英文對(duì)照表;目錄版本信息21.參考文獻(xiàn)52.網(wǎng)絡(luò)拓?fù)?3.診斷接口64.診斷需求74.1.診斷協(xié)議74.1.1.物理層74.1.2.數(shù)據(jù)鏈路層74.1.3.網(wǎng)絡(luò)層74.1.4.應(yīng)用層時(shí)間參數(shù)84.2.Diagnostic Services(ISO14229-1)84.2.1.Supported Diagnostic Services94.2.2.DiagnosticSessionControl(10H)114.2.3.ECUReset (11H)134.2.4.CommunicationControl(28H)144.2.5.SecurityAcces
3、s(27H)154.2.6.TesterPresent(3EH)214.2.7.ControlDTCSetting(85H)214.2.8.ReadDataByIdentifier(22H)234.2.9.WriteDataByIdentifier (2EH)244.2.10.InputOutputControlByIdentifier (2FH)264.2.11.ClearDiagnosticInformation (14H)274.2.12.ReadDTCInformation (19H)284.2.13.RoutineControl (31H)354.2.14.RequestDownLo
4、ad(34H)374.2.15.TransferData (36H)374.2.16.RequestTransferExit (37H)375.故障定義386.故障碼DTC中英文對(duì)照表38附錄 A: 凍結(jié)幀信息39附錄 B:41B.1 版本信息參數(shù)列表:41B.2 數(shù)據(jù)流參數(shù)列表:41B.3 版本信息參數(shù)定義43B.4 數(shù)據(jù)流參數(shù)定義45術(shù)語(yǔ)DTC故障診斷碼BS Block sizeSTminMinimum Separation Time C有條件的M強(qiáng)制性執(zhí)行U用戶選用TBD待定義SID服務(wù)標(biāo)識(shí)符DID數(shù)據(jù)標(biāo)識(shí)符NRC負(fù)響應(yīng)碼UDS統(tǒng)一的診斷服務(wù)Server服務(wù)器Client客戶端ECU電控
5、單元1. 參考文獻(xiàn)NO.參考文檔題目1 ISO11898-1: 2003 Road vehicles - Controller area network (CAN) Part 1:Data link layer and physical signaling 2 ISO11898-2: 2003 Road vehicles - Controller area network (CAN) Part 2: High-speed medium access unit 3 ISO11898-5: 2007 Road vehicles - Controller area network (CAN) Par
6、t 5: High-speed medium access unit with low-power mode 4 ISO15765-2: 2004 Road Vehicle - Diagnostic on CAN Part 2: Networking Layer Services 5 ISO15765-3: 2004 Road Vehicle - Diagnostic on CAN Part 3: Application Layer Services 6 ISO14229-1: 2006 Road Vehicle - Diagnostic Systems Diagnostic Services
7、 Specification 7 ISO15031-6: 2005 Road vehicles - Communication between vehicle and external equipment for emission-related diagnostic Part 6: Diagnostic trouble code definitions 2. 網(wǎng)絡(luò)拓?fù)洹坝删W(wǎng)絡(luò)工程師統(tǒng)一發(fā)布網(wǎng)絡(luò)拓?fù)洹盕ig 1. C70GB-2014整車網(wǎng)絡(luò)拓?fù)浣Y(jié)構(gòu)3. 診斷接口Fig 2. OBD診斷接口管腳描述1EVBUS CAN_H2/3/4接地5接地6/7/8/9EVBUS CAN_L10/11/12
8、/13/14/15/16電源Tab 1. OBD 診斷接口針腳定義“由線束工程師統(tǒng)一發(fā)布OBD接口定義”4. 診斷需求4.1. 診斷協(xié)議4.1.1. 物理層物理層應(yīng)滿足ISO11898-2要求及北京新能源汽車股份有限公司企業(yè)標(biāo)準(zhǔn)新能源汽車高速 CAN 網(wǎng)絡(luò)節(jié)點(diǎn)級(jí)電子控制單元( ECU)技術(shù)要求要求。4.1.2. 數(shù)據(jù)鏈路層數(shù)據(jù)鏈路層應(yīng)滿足ISO11898-1要求。所有診斷請(qǐng)求和應(yīng)答幀的數(shù)據(jù)長(zhǎng)度應(yīng)為8字節(jié),否則電控單元將忽略該診斷請(qǐng)求幀。當(dāng)診斷響應(yīng)長(zhǎng)度不足8字節(jié)時(shí),空余的字節(jié)應(yīng)用0xAA填充。4.1.3. 網(wǎng)絡(luò)層網(wǎng)絡(luò)層應(yīng)滿足ISO15765-2要求和下述要求:. 尋址方式可以支持物
9、理尋址和功能尋址。診斷消息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至上表”. 網(wǎng)絡(luò)層時(shí)間參數(shù)ParameterValueUnit BS 8- STmin 20msParameterTimeout Performance Requirement Unit N_As/N_Ar 70 n/a ms N_Br n/a 70 ms N_Bs 150 n/a ms
10、 N_Cs n/a 70 ms N_Cr 150 n/a ms Tab 3. 網(wǎng)絡(luò)層時(shí)間參數(shù)需求4.1.4. 應(yīng)用層時(shí)間參數(shù)ParameterMin Max Timeout Unit P2server 0 50 n/a msP2client n/a n/a 150 msP2*server 0 2000 n/a msP2* clientn/an/a5000msP3client_phys2 P2server n/a n/a ms P3client_func P2server_max n/a n/a ms ParameterMin Nominal Timeout Unit S3server n/a
11、n/a 5000 ms S3client 0 2000 4000 ms Tab 4. 應(yīng)用層時(shí)間參數(shù)需求4.2. Diagnostic Services(ISO14229-1)Services shall be implemented according to ISO14229-1. Additional details are specified in this section.4.2.1. Supported Diagnostic ServicesThe overview of ECU supported diagnostic services is described in the fo
12、llowing table.Table 5 Supported diagnostic services of ECUDiagnostic Services ListSessionSecurityAccessAddressingSID (Hex)Service NameDefaultExtendedProgrammingPhysical AddressFunction Address10DiagnosticSessionControl 11EcuReset 27SecurityAccess 28CommunicationControl 3ETesterPresent 85ControlDTCSe
13、tting 22ReadDataByIdentifier 2EWriteDataByIdentifier 13 2FInputOutputControlByIdentifier 114ClearDiagnosticInformation 19ReadDTCInformation 31RoutineControl 13 34RequestDownLoad336TransferData337RequestTransferExit3說明:訪問權(quán)限1表示需要擴(kuò)展安全級(jí)權(quán)限,3表示需要編程安全級(jí)權(quán)限。The services need to support suppressPositveResponse
14、Bit (SPRS) are showed in following table.Tab 5. Services supported SPRS bitDiagnostic Services ListSupportSPRS bitSID(Hex)Service Name10DiagnosticSessionControl11EcuReset27SecurityAccess28CommunicationControl3ETesterPresent85ControlDTCSetting22ReadDataByIdentifier2EWriteDataByIdentifier14ClearDiagno
15、sticInformation19ReadDTCInformation2FInputOutputContorlByIdentifier31RoutineControl34RequestDownload36TransferData37RequestTransferExitThe negativeResponseCodes (NRC) used by ECU are defined as follows:Tab 6. Negative Response CodesNRC(Hex)Description11HserviceNotSupported12HsubFunctionNotSupported1
16、3HincorrectMessageLengthOrInvalidFormat22HconditionsNotCorrect24HrequestSequenceError36HexceededNumberOfAttempts31HrequestOutOfRange33HsecurityAccessDenied37HrequiredTimeDelayNotExpired35HInvalidKey72HgeneralProgrammingFailure78HresponsePending7FHserviceNotSupportedInActiveSession92H/93HVoltageTooHi
17、gh / voltageTooLow7EHsubFunctionNotSupportedInActiveSessionIf two or more NRCs are reasonable, the ECU could send the negative response message according to the following priority rules: The 7Fh NRC have the highest priority; For others, the NRC with smaller number has higher priority.4.2.2. Diagnos
18、ticSessionControl(10H)This service is used by the client to enable different diagnostic sessions in the server(s). A diagnostic session enables a specific set of diagnostic services in the server(s).. Message FormatRequest:ByteNameCvtValue(hex)#1RequestServiceIdentifierM10#2Sub-function = Def
19、aultSession ProgrammingSessionExtendedDiagnosticSession M010203Positive Response:ByteNameCvtValue#1PositiveResponseServiceIdentifierM50#2Sub-Function=DefaultSessionProgrammingSessionExtendedDiagnosticSession M010203P2server =#3byte#1M00-FF#4byte#2M00-FFP2*server =#5byte#1M00-FF#6byte#2M00-FFTiming P
20、2server value is provided in 1ms resolution.Timing P2*server value is provided in 10ms resolution.Negative Response:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM10#3NegativeResponseCodeMNRCSub-function Parameter DefinitionHEXDescription Cvt01 DefaultSessionThis di
21、agnostic session enables the default diagnostic session in the server(s)and does not support any diagnostic application timeout handling provisions. (e.g. no TesterPresent service is necessary to keep the session active).M02ProgrammingSessionThis diagnostic session enables all diagnostic services re
22、quired to supported the memory programming of a server.M03 ExtendedDiagnosticSessionThis diagnostic session can e.g. be used to enable all diagnostic services required to support the adjustment of functions like “Idle Speed, CO Value, etc.” in the servers memory. It can also be used to enable diagno
23、stic services, which are not specifically tied to the adjustment of functions.MNegative Response Codes (NRC)NRC(Hex)DescriptionCvt12 The sub-function parameter in the request message is not supported.M13 The length of the message is wrong.M22 The ECUcurrent conditions do not allow the change ofdiagn
24、ostic Session.M. Implementation RulesThis service is used by the diagnostic tool to enable different types of diagnostic sessions in a server. In order to execute a diagnostic service the appropriate session has to be started first.There shall be only one diagnostic session active at a time.N
25、ormal/Default Session (01h) shall be enabled automatically by the ECU if no diagnostic session has been requested at power up.The ECU shall return to Normal/Default Session (01h) after timeout of ExtendedDiagnostic Session.The ECU shall be capable of providing all diagnostic functionality defined fo
26、r the default diagnostic session under normal operating conditions.The ECU shall first send a DiagnosticSessionControl Positive Response (50h xx) message before the new session becomes active in the ECU.A DiagnosticSessionControl Positive Response (50h xx) message shall be returned by an ECU if the
27、diagnostic tool requests a session that is already running. If the ECU has already received the same request message previously and performed the requested operation, the ECU shall continue to perform the current operation (i.e. it is not a change of the session).The ECU shall remain in its current
28、diagnostic session if it is not able to switch into the requested diagnostic session.The TesterPresent (3Eh) service shall be used to keep the non-default diagnostic sessions active by retriggering S3server. Also any other service request shall retrigger S3server.A functional TesterPresent (3Eh) req
29、uest without response may be sent at any time, even regardless of any other service in progress.When receiving or transmitting any diagnostic messages, including 3Eh service, the S3servertimer will reset.Fig 3. Session transition diagram4.2.3. ECUReset (11H)This service requests the server to effect
30、ively perform an ECU reset based on the content of the ResetType parameter value (suppressPosRspMsgIndicationBit (bit 7) not shown).. Message FormatRequest:ByteNameCvtValue(hex)#1RequestServiceIdentifierM11#2Sub-Function= ResetType: HardResetSoftResetM0103Positive Response:ByteNameCvtValue#1P
31、ositiveResponseServiceIdentifierM51#2Sub-Function= ResetType: HardResetSoftResetM0103Negative Response:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM11#3NegativeResponseCodeMNRCSub-function Parameter DefinitionOption (Hex) Description Cvt01 HardResetThis value iden
32、tifies a “hard reset” condition which simulates the power-on / start-up sequence typically performed after a server has been previously disconnected from its power supply (i.e. battery).M03SoftResetThis value identifies a “soft reset” condition, which causes the server to immediately restart the app
33、lication program if applicable. The performed action is implementation specific and not defined by the standard. A typical action is to restart the application without reinitializing of previously learned configuration data, adaptive factors and other long-term adjustments.MNegative Response Codes (
34、NRC)NRC (Hex) Conditions Cvt12 Sub-function parameter in the request message is not supported. M13 The length of the message is wrong M22The criteria for the ECUReset request are not met.M. Implementation RulesThe positive response shall be sent before performing the ECU reset.The execution o
35、f reset will take ms, which means the ECU cant respond to any new request sent within this time.4.2.4. CommunicationControl(28H)The service is used to “switch on/off” the transmission and/or the reception of certain messages of (a) server(s).. Message FormatRequest:ByteNameCvtValue(hex)#1Requ
36、estServiceIdentifierM28#2Sub-Function = EnableRxAndTxDisableRxAndTx M0003#3CommunicationType= NormalCommunicationMessagesNetworkManagementCommunicationMessages NetworkManagementCommunicationMessagesAndNormalCommunicationMessages M010203Positive Response:ByteNameCvtValue#1PositiveResponseServiceIdent
37、ifierM68#2Sub-Function = EnableRxAndTxEnableRxAndDisableTx DisableRxAndEnableTxDisableRxAndTx M00010203Negative Response:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM28#3NegativeResponseCodeMNRCNegative Response Codes(NRC)NRC (Hex) Conditions Cvt12 Sub-function pa
38、rameter in the request message is not supported. M13 The length of the message is wrongM22The operating conditions of the server are not met to perform the required action.M31None of the requested CommunicationType values are supported by the device.MSub-function Parameter Definition:Option(hex)Desc
39、ription Cvt00EnableRxAndTxThis value indicates that the reception and transmission of messages shall be enabled for the specified CommunicationType.M03DisableRxAndTxThis value indicates that the reception and transmission of messages shall be disabled for the specified CommunicationType.MData Parame
40、ter Definition:Option(hex)Description Cvt01NormalCommunicationMessagesThis value references all application-related communication (inter-application signal exchange between multiple in-vehicle servers).M02NetworkManagementCommunicationMessagesThis value references all network management related comm
41、unication.M03NetworkManagementCommunicationMessagesAndNormalCommunicationMessagesThis value references all network management and application-related communicationM. Implementation RulesThere are no special general implementation rules for this service.4.2.5. SecurityAccess(27H)The purpose of
42、 this service is to provide a means to access data and/or diagnostic services, which have restricted access for security or safety reasons. Diagnostic services for downloading/uploading routines or data into a server and reading specific memory locations from a server are situations where security a
43、ccess may be required. Improper routines or data downloaded into a server could potentially damage the electronics or other vehicle components or risk the vehicles compliance to safety, or security standards. The security concept uses a seed and key relationship.The client shall request the server t
44、o unlock by sending the service SecurityAccess-RequestSeed message. The server shall respond by sending a seed. The seed is the input parameter for the key calculation algorithm. It is used by the client to calculate the corresponding key value.In a second step, the client shall request the key comp
45、arison by sending the calculated key to the server using the appropriate service SecurityAccess-SendKey. The server shall compare this key to one internally stored/calculated. If the two numbers match, then the server shall enable (unlock) the clients access to specific services/data and indicate th
46、at with the service SecurityAccess-SendKey. If the two numbers do not match, this shall be considered as a false access attempt. If access is rejected for any other reason, it shall not be considered as a false access attempt. An invalid key requires the client to start over from the beginning with
47、a SecurityAccess-RequestSeed message.If a server supports security, but is already unlocked when a SecurityAccess-RequestSeed message is received, that server shall respond with a SecurityAccess-RequestSeed positive response message service with a seed value equal to zero (0). The client shall use t
48、his method to determine if a server is locked by checking for a non-zero seed.The Seed-Key algorithmfor SecurityAccess(Mandatory):Key = (seed4) XOR seed)3) XOR seed)。The Security Seed is 4Bytes random numbers.Fig 4. Security Access procedure. Message Format.1. Request SeedThis service
49、requests a seed from the server. Based on this seed, the client is able to calculate the corresponding key to be sent for unlocking the server.Request:ByteNameCvtValue(hex)#1RequestServiceIdentifierM27#2SecurityAccessType = RequestSeedM01,11Positive Response:ByteNameCvtValue#1PositiveResponseService
50、IdentifierM67#2SecurityAccessType = RequestSeedM01,11SecuritySeed = M#3seed#1 (high byte)M00-FF#6seed#m (low byte) M00-FFNegative Response:ByteNameCvtValue#1NegativeResponseServiceIdentifierM7F#2RequestServiceIdentifierM27#3NegativeResponseCodeMNRCNegative Response Codes(NRC)NRC (Hex) Conditions Cvt
51、12 Sub-function parameter in the request message is not supported. M13 The length of the message is wrong.M22 The criteria for the SecurityAccess request are not met.M37requiredTimeDelayNotExpiredM.2. Send KeyThis service sends a key calculated by the client to the server. The server shall co
52、mpare this key to one internally stored/calculated. If the two numbers match, then the server shall enable (“unlock”) the clients access to specific services/data.Request:ByteNameCvtValue(hex)#1RequestServiceIdentifierM27#2SecurityAccessType = SendKeyM02,12SecurityKey = M#3key#1 (high byte)M00-FF#6key#m (low byte) M00-FFPositive Response:ByteNameCvtValue#1PositiveResponseServiceIdentifierM67#2SecurityA
溫馨提示
- 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。
最新文檔
- 如何健全辦學(xué)管理辦法
- 員額退出機(jī)制管理辦法
- 藥品責(zé)任追究管理辦法
- 拉薩補(bǔ)貼資金管理辦法
- 肯德基安全培訓(xùn)課件
- 倒閘操作培訓(xùn)課件
- 肝膿腫病人護(hù)理課件
- 眾安實(shí)業(yè)培訓(xùn)課件
- 二附中期末數(shù)學(xué)試卷
- kbz饋電開關(guān)培訓(xùn)課件
- 【MOOC】人像攝影-中國(guó)傳媒大學(xué) 中國(guó)大學(xué)慕課MOOC答案
- 中小學(xué)家長(zhǎng)會(huì)期中期末家長(zhǎng)會(huì)253
- 派出所應(yīng)對(duì)校園突發(fā)事件應(yīng)急預(yù)案
- 網(wǎng)絡(luò)安全漏洞挖掘與報(bào)告
- 埋地消防管滲漏整改工程施工方案
- 裝飾裝修施工人員安全知識(shí)培訓(xùn)考試試卷及答案
- 2023年上海市普通高中學(xué)業(yè)水平合格性考試地理試題及答案
- 醫(yī)聯(lián)體協(xié)議書(2024版)
- 宿舍消防安全培訓(xùn)課件
- 11 《愛蓮說》對(duì)比閱讀-2024-2025中考語(yǔ)文文言文閱讀專項(xiàng)訓(xùn)練(含答案)
評(píng)論
0/150
提交評(píng)論