Diagnostic fault design and data coupling system based on integrated architecture of adas product

Abstract

This invention discloses a diagnostic fault design and data coupling system based on an integrated ADAS product architecture. It includes a UDS service module and a UDS TP data transmission management module, divided based on the UDS unified diagnostic service module, and an Event module and a Fault module, divided based on the DEM diagnostic event management module. The UDS service module manages various diagnostic services; the UDS TP data transmission management module processes data for physical addressing and functional addressing, single frames and multiple frames, ensuring the normal reception and transmission of diagnostic messages; the Event module, or diagnostic event module, associates diagnostic events with DTC fault codes and sets DTC diagnostic fault codes after a fault occurs; and the Fault module, or diagnostic fault module, debounces faults before confirmation. This invention significantly reduces the amount of manual coding required by developers by coupling UDS diagnostics and DEM diagnostic event management.

Description

Technical Field

[0001] This invention relates to the field of UDS unified diagnostic services and DEM diagnostic event management, specifically a diagnostic fault design and data coupling system based on the integrated architecture of ADAS products. Background Technology

[0002] UDS diagnostic protocol is a diagnostic communication protocol used in automotive electronic control units (ECUs). Defined in ISO 14229, it is an international standard used in almost all ECUs controlling various vehicle functions. DEM diagnostic event management is responsible for confirming vehicle fault events, storing and managing fault data. In today's era of booming autonomous driving, ADAS products are emerging in large numbers, and fault diagnosis, as part of the automotive electronic control unit (ECU), plays a crucial role. Traditional UDS diagnostic services mostly rely on developers manually writing code, and DEM diagnostic event management is also manually coded according to requirements, resulting in a severe disconnect between the upper and lower layers and the lack of a unified interface for communication, greatly increasing the workload for developers. Therefore, a diagnostic-driven solution is urgently needed to address these problems. Summary of the Invention

[0003] The purpose of this invention is to provide a diagnostic fault design and data coupling system based on the integrated architecture of ADAS products, so as to solve the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: a diagnostic fault design and data coupling system based on an integrated ADAS product architecture, comprising a UDS service module and a UDS TP data transmission management module based on the UDS unified diagnostic service module, and an Event module and a Fault module based on the DEM diagnostic event management module, wherein...

[0005] The UDS service module is used to manage various diagnostic services. Each diagnostic service has its own unique ID, namely SID. The UDS service module divides the SID into diagnostic and communication management functional units, data transmission functional units, data storage functional units, input / output control functional units, routine functional units, and upload / download functional units according to the diagnostic communication protocol.

[0006] The UDS TP data transmission management module is used for data processing of physical addressing and functional addressing, single frames and multiple frames, to ensure the normal reception and transmission process of diagnostic messages. Physical addressing is a one-to-one access to a single ECU, while functional addressing is a one-to-many access based on different functions. Multiple frames include the first frame, flow control frame and consecutive frames.

[0007] The Event module, or Diagnostic Event module, is used to associate diagnostic events with DTC fault codes and to set the DTC diagnostic fault code after a fault occurs.

[0008] The Fault module, or fault diagnosis module, is used for debounce before a fault is confirmed, as well as for the storage and management of fault data. Event diagnostic events and Fault diagnostic faults are associated one-to-one.

[0009] Preferably, DTC diagnostic fault codes and Event diagnostic events are associated one-to-one and / or one-to-many.

[0010] Preferably, the diagnostic and communication management function unit includes six diagnostic services: session control service, reset service, secure access service, communication control service, standby handshake service, and control DTC service; the data transmission function unit includes two services: read data and write data; the data storage function unit includes two services: clear diagnostic data service and read diagnostic data service; the input / output control function unit includes one service: control input / output service; the routine function unit includes one service: routine control service; and the upload / download function unit includes three services: request download service, data transmission service, and request exit from transmission service.

[0011] Preferably, in addition to classifying the SID diagnostic service class ID, the UDS service module also classifies the DID data class ID, RID routine control class ID, DTC diagnostic fault code, and DM1 diagnostic message 1, and associates them through address mapping. The DID data class ID contains product-related information and configuration data, the RID routine control class ID contains calibration, burning and other related operations, the DTC diagnostic fault code corresponds to product faults, and the DM1 diagnostic message 1 contains the current error code, which can be traced back to the relevant network node by means of the source address.

[0012] Preferably, the implementation method of the UDS unified diagnostic service module includes the following steps:

[0013] A1: Configure diagnostic services according to product requirements;

[0014] A2: Send diagnostic commands via third-party software;

[0015] A3: By calling the upper-layer unified interface function, the software automatically performs reception verification under the action of the UDS TP module;

[0016] A4: Based on the diagnostic instructions, respond positively or negatively and fill in the data;

[0017] A5: Under the UDS TP module, transmit single or multiple frames.

[0018] Preferably, the implementation method of the DEM event management module includes the following steps:

[0019] B1: Configure fault events according to product requirements;

[0020] B2: When a diagnostic event occurs, the Event module is set;

[0021] B3: The Event module determines whether a diagnostic fault occurs under the action of debounce;

[0022] B4: DTC fault code is set, and can be queried and reported by reading diagnostic data service.

[0023] Preferably, the present invention also provides a method for implementing the above-mentioned diagnostic fault design and data coupling system based on the integrated architecture of ADAS products, including the following steps:

[0024] S1: Configure the diagnostic services and fault events required by different products and generate corresponding Config files;

[0025] S2: Based on version iterations, modify or remove the required diagnostic services and fault events;

[0026] S3: The upper layer implements diagnostic services and fault determination by calling the unified interface provided by the UDS and DEM modules;

[0027] S4: After the DEM module processes the fault event, it will set the DTC code for the UDS diagnostic module to read and operate.

[0028] S5: Testers can send diagnostic commands through third-party software, verify the validity of the protocol stack through positive and negative responses, and verify its correctness by clearing and reading the diagnostic data service.

[0029] Compared with the prior art, the beneficial effects of the present invention are:

[0030] This invention couples UDS diagnostics and DEM diagnostic event management, allowing developers to implement diagnostic functions simply by configuring the diagnostic service and fault events. This significantly reduces the amount of manual coding required by developers while ensuring code effectiveness. Simultaneously, testers, without prior experience, can determine the cause of a fault simply by reading DTC and snapshot information via the bus. Attached Figure Description

[0031] Figure 1 This is a diagram showing the partitioning of SID diagnostic services in an embodiment of the present invention;

[0032] Figure 2 This is a structural diagram of the diagnostic service module according to an embodiment of the present invention;

[0033] Figure 3 This is a fault classification diagram for an embodiment of the present invention;

[0034] Figure 4 This is a data coupling diagram of the UDS module and DEM module in an embodiment of the present invention;

[0035] Figure 5 This is a flowchart illustrating the diagnostic service response process according to an embodiment of the present invention.

[0036] Figure 6 This is a flowchart illustrating the fault event management process according to an embodiment of the present invention.

[0037] Figure 7 This is a flowchart illustrating the UDS diagnosis and event management process in an embodiment of the present invention. Detailed Implementation

[0038] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0039] This invention provides a technical solution: a diagnostic fault design and data coupling system based on the integrated architecture of ADAS products. The system divides the UDS unified diagnostic service module into a UDS service module and a UDS TP data transmission management module, and divides the DEM diagnostic event management module into two modules: Event and Fault.

[0040] like Figure 1As shown, in this embodiment, the UDS service module of the present invention is used to manage various diagnostic services. Each diagnostic service has its own independent ID, namely SID. According to the diagnostic communication protocol, the SID is divided into six categories: diagnostic and communication management functional unit, data transmission functional unit, data storage functional unit, input / output control functional unit, routine functional unit, and upload / download functional unit. The diagnostic and communication management functional unit includes six diagnostic services: session control service, reset service, secure access service, communication control service, standby handshake service, and DTC control service. The data transmission functional unit includes two services: reading data and writing data. The data storage functional unit includes two services: clearing diagnostic data and reading diagnostic data. The input / output control functional unit includes one service: controlling input / output. The routine functional unit includes one service: routine control service. The upload / download functional unit includes three services: request download service, data transmission service, and request exit from transmission service. In addition to classifying the SID diagnostic service class ID, the UDS service module also classifies the DID data class ID, RID routine control class ID, DTC diagnostic fault code, and DM1 diagnostic message, and associates them through address mapping. The DID data class ID contains product-related information and configuration data, the RID routine control class ID contains calibration, programming and other related operations, the DTC diagnostic fault code corresponds to the product fault, and the DM1 diagnostic message 1 contains the current error code, which can be traced back to the relevant network node by using the source address.

[0041] like Figure 2 As shown, in this embodiment, the attributes configured for the SID diagnostic service ID include service enable bit, service ID, number and ID of sub-services, session mode configuration, security level configuration, and addressing mode; the attributes configured for the DID data class ID include DID number, read / write support session mode, read / write support security level, DID data pointer, DID data length, read / write support selection, and storage location; the attributes configured for the DTC fault code include DTC hexadecimal code, DTC status, DTC determination count, and current diagnostic fault error count; and the attributes configured for the DM1 diagnostic message include DM1 code, DM1 message type, and DM1 message ID.

[0042] In this embodiment, in addition to dividing functions and data, the UDS service module also performs data processing on its positive and negative responses. Using the ISO 14229 diagnostic protocol as a standard, it adds corresponding NRC negative response codes to various diagnostic services to ensure consistency with the standard protocol. Simultaneously, it adds data validation, time management, and external interface functions to ensure data validity and improve its scalability.

[0043] In this embodiment, the UDS TP data transmission management module of the present invention is used to process data for physical addressing and functional addressing, as well as for single frames and multiple frames, to ensure the normal reception and transmission process of diagnostic messages. Physical addressing is a one-to-one access to a single ECU, while functional addressing is a one-to-many access based on different functions. Multiple frames include the first frame, flow control frame, and consecutive frames.

[0044] In this embodiment, the Event module of the present invention, i.e., the diagnostic event module, is used to diagnose the association between events and DTC fault codes, and to set the DTC diagnostic fault code after a fault occurs. The DTC diagnostic fault code and the Event diagnostic event can be associated in a one-to-one or one-to-many manner.

[0045] In this embodiment, the Fault module of the present invention, i.e., the fault diagnosis module, is used for debounce before a fault is confirmed, as well as for the storage and management of fault data. Event diagnosis events and Fault diagnosis events are associated one-to-one. For example... Figure 3 As shown, in this embodiment, diagnostic faults are divided into three categories: communication faults, hardware faults, and internal faults. Communication faults include message loss, invalid signals, and abnormal verification or counting faults; hardware faults include high and low voltage faults, SOC faults, and SPI faults; and internal faults include obstruction faults, circuit faults, and high and low temperature faults. In addition to the faults mentioned above, developers can add their own faults according to product requirements by simply adding them to the provided external interface functions.

[0046] like Figure 4 As shown in this embodiment, the key to achieving data coupling between the UDS module and the DEM module is that the DEM module confirms the diagnosed fault through the DTC fault code, sets the DTC code based on the correlation between the diagnosed fault and the DTC code, and the UDS module can then access and clear the DTC code, thus achieving data coupling between the two modules.

[0047] like Figure 5 As shown, in this embodiment, the implementation method of the UDS unified diagnostic service module includes the following steps:

[0048] A1: Configure diagnostic services according to product requirements;

[0049] A2: Send diagnostic commands via third-party software;

[0050] A3: By calling the upper-layer unified interface function, the software automatically performs reception verification under the action of the UDS TP module;

[0051] A4: Based on the diagnostic instructions, respond positively or negatively and fill in the data;

[0052] A5: Under the UDS TP module, transmit single or multiple frames.

[0053] like Figure 6 As shown, in this embodiment, the implementation method of the DEM event management module includes the following steps:

[0054] B1: Configure fault events according to product requirements;

[0055] B2: When a diagnostic event occurs, the Event module is set;

[0056] B3: The Event module determines whether a diagnostic fault occurs under the action of debounce;

[0057] B4: DTC fault code is set, and can be queried and reported by reading diagnostic data service.

[0058] like Figure 5 As shown, in this embodiment, the present invention also provides a method for implementing the above-mentioned diagnostic fault design and data coupling system based on the integrated architecture of ADAS products, including the following steps:

[0059] S1: Configure the diagnostic services and fault events required by different products and generate corresponding Config files;

[0060] S2: Based on version iterations, modify or remove the required diagnostic services and fault events;

[0061] S3: The upper layer implements diagnostic services and fault determination by calling the unified interface provided by the UDS and DEM modules;

[0062] S4: After the DEM module processes the fault event, it will set the DTC code for the UDS diagnostic module to read and operate.

[0063] S5: Testers can send diagnostic commands through third-party software, verify the validity of the protocol stack through positive and negative responses, and verify its correctness by clearing and reading the diagnostic data service.

[0064] Based on the above embodiments, by coupling UDS diagnostics and DEM diagnostic event management, developers only need to configure the diagnostic service and fault events to realize the diagnostic function.

[0065] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A diagnostic fault design and data coupling system based on an integrated ADAS product architecture, characterized in that, This includes the UDS service module and UDS TP data transmission management module, which are based on the UDS unified diagnostic service module, and the Event module and Fault module, which are based on the DEM diagnostic event management module. The UDS service module is used to manage various diagnostic services. Each diagnostic service has its own unique ID, namely SID. The UDS service module divides the SID into diagnostic and communication management functional units, data transmission functional units, data storage functional units, input / output control functional units, routine functional units, and upload / download functional units according to the diagnostic communication protocol. In addition to classifying SID diagnostic service class IDs, the UDS service module also classifies DID data class IDs, RID routine control class IDs, DTC diagnostic fault codes, and DM1 diagnostic message 1, and associates them through address mapping. DID data class IDs contain product-related information and configuration data, RID routine control class IDs contain calibration and programming, DTC diagnostic fault codes correspond to product faults, and DM1 diagnostic message 1 contains the current error code, which can be traced back to the relevant network node by using the source address. The UDS TP data transmission management module is used for data processing of physical addressing and functional addressing, single frames and multiple frames, to ensure the normal reception and transmission process of diagnostic messages. Physical addressing is a one-to-one access to a single ECU, while functional addressing is a one-to-many access based on different functions. Multiple frames include the first frame, flow control frame and consecutive frames. The Event module, or Diagnostic Event module, is used to associate diagnostic events with DTC fault codes and to set the DTC diagnostic fault code after a fault occurs. The Fault module, or fault diagnosis module, is used for debounce before a fault is confirmed, as well as for the storage and management of fault data. Event diagnosis events and Fault diagnosis events are associated one-to-one. The DTC diagnostic fault codes and Event diagnostic events are associated one-to-one and / or one-to-many.

2. The diagnostic fault design and data coupling system based on the integrated architecture of ADAS products according to claim 1, characterized in that: The diagnostic and communication management function unit includes six diagnostic services: session control service, reset service, secure access service, communication control service, standby handshake service, and control DTC service; the data transmission function unit includes two services: read data and write data; the data storage function unit includes two services: clear diagnostic data service and read diagnostic data service; the input / output control function unit includes one service: control input / output service; the routine function unit includes one service: routine control service; and the upload / download function unit includes three services: request download service, data transmission service, and request exit from transmission service.

3. The diagnostic fault design and data coupling system based on the integrated architecture of ADAS products according to any one of claims 1-2, characterized in that: The implementation method of the UDS unified diagnostic service module includes the following steps: A1: Configure diagnostic services according to product requirements; A2: Send diagnostic commands via third-party software; A3: By calling the upper-layer unified interface function, the software automatically performs reception verification under the action of the UDS TP module; A4: Based on the diagnostic instructions, respond positively or negatively and fill in the data; A5: Under the UDS TP module, transmit single or multiple frames.

4. The diagnostic fault design and data coupling system based on the integrated architecture of ADAS products according to claim 1, characterized in that: The implementation method of the DEM diagnostic event management module includes the following steps: B1: Configure fault events according to product requirements; B2: When a diagnostic event occurs, the Event module is set; B3: The Event module determines whether a diagnostic fault occurs under the action of debounce; B4: DTC fault code is set and reported by reading diagnostic data service.

5. The implementation method of the diagnostic fault design and data coupling system based on the integrated architecture of ADAS products according to any one of claims 1-4, characterized in that: Including the following steps: S1: Configure the diagnostic services and fault events required by different products and generate corresponding Config files; S2: Based on version iterations, modify or remove the required diagnostic services and fault events; S3: The upper layer implements diagnostic services and fault determination by calling the unified interface provided by the UDS and DEM modules; S4: After the DEM module processes the fault event, it will set the DTC code for the UDS diagnostic module to read and operate. S5: Testers send diagnostic commands through third-party software, verify the validity of the protocol stack through positive and negative responses, and verify its correctness by clearing and reading the diagnostic data service.

Images