CN116521143B - DID read-write service processing method and device for fault diagnosis - Google Patents
DID read-write service processing method and device for fault diagnosis Download PDFInfo
- Publication number
- CN116521143B CN116521143B CN202310807808.XA CN202310807808A CN116521143B CN 116521143 B CN116521143 B CN 116521143B CN 202310807808 A CN202310807808 A CN 202310807808A CN 116521143 B CN116521143 B CN 116521143B
- Authority
- CN
- China
- Prior art keywords
- read
- information
- file
- fault diagnosis
- write service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000003745 diagnosis Methods 0.000 title claims abstract description 236
- 238000003672 processing method Methods 0.000 title claims abstract description 12
- 238000000034 method Methods 0.000 claims abstract description 41
- 230000006870 function Effects 0.000 claims description 106
- 238000012545 processing Methods 0.000 claims description 20
- 238000004891 communication Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 13
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 32
- 238000013507 mapping Methods 0.000 abstract description 21
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 8
- 230000008859 change Effects 0.000 description 6
- 230000008676 import Effects 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 6
- 238000012423 maintenance Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0808—Diagnosing performance data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The embodiment of the invention provides a fault diagnosis DID read-write service processing method and device. The method comprises the following steps: reading the diagnosis database file after judging that the diagnosis database file is changed; analyzing the diagnosis database file and extracting DID read-write service information of fault diagnosis; determining DID interface information according to the DID read-write service information of fault diagnosis; writing DID interface information into the attribute file; the attribute file is imported into an AUTOSAR configuration tool chain to generate configuration information so as to correlate fault diagnosis DID read-write service information and DID interface information, so that an automatic generation flow of the diagnostic DID read-write service interface mapping relation is realized, a large amount of code development or configuration work is not needed, the error rate in manual development engineering is reduced, the stability of fault diagnosis DID read-write service software is ensured, the workload is greatly reduced, and the development efficiency of fault diagnosis DID read-write service is improved.
Description
Technical Field
The invention relates to the technical field of automobiles, in particular to a DID read-write service processing method and device for fault diagnosis.
Background
The automobile open system architecture (AUTomotive Open System Architecture, AUTOSAR) is a consortium that is dedicated to the development of automobile electronic software standards. AUTOSAR is built jointly by global automobile manufacturers, component suppliers and other electronic, semiconductor and software system companies, each member maintains a development partnership, each partnership is brought into hand-in-hand cooperation, and aims to develop an open and standardized software architecture for the automobile industry. The AUTOSAR architecture is beneficial to the exchange and update of vehicle electronic system software, and provides a foundation for efficiently managing more and more complex vehicle electronic and software systems.
Most of the development of fault diagnosis Data Identifier (DID) read-write service in a current micro control unit (Microcontroller Unit, MCU) based on the auto sar architecture is realized through the configuration of a tool chain and a protocol stack, and a unique service interface exists for each fault diagnosis DID read-write service in the tool chain.
Fig. 1 is a schematic diagram of a call relationship of a MCU fault diagnosis DID read/write service based on a standardized AUTOSAR interface in the prior art, as shown in fig. 1, a service interface may be a standardized AUTOSAR interface, that is, a standardized AUTOSAR interface generated by an upper Software component (SWC) through a tool chain, each interface is used for a diagnostic communication service management module (Diagnostic Communication Manager, DCM) to call, and an interface mapping (mapping) connection relationship is to be established in a tool.
Fig. 2 is a schematic diagram of a call relation of a fault diagnosis DID read-write service of an MCU based on a Callout function in the prior art, as shown in fig. 2, a service interface may also be a Callout callback function, that is, each fault diagnosis DID read-write service corresponds to 1 Callout callback function, that is, each fault diagnosis DID read-write service and a Callout callback function establish an interface mapping relation, and these Callout callback functions are directly called by a diagnostic communication service management module DCM.
However, in the process of implementing the present invention, the inventors found that at least the following problems exist in the prior art: when the function is transplanted or the requirement of fault diagnosis service is changed on different platforms, the interface mapping related to the fault diagnosis DID read-write service can be greatly changed, and the change work is basically realized by manual configuration or development of developers, so that the problems of large workload, long development period, high error rate and the like are caused.
Disclosure of Invention
Aiming at the defects in the prior art, the embodiment of the invention provides a fault diagnosis DID read-write service processing method and device.
In a first aspect, a method for processing a fault diagnosis DID read-write service is provided, including:
if the diagnosis database file is judged to be changed, the diagnosis database file is read;
Analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier;
determining DID interface information according to the DID read-write service information of fault diagnosis;
writing the DID interface information into a property file;
and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
As described above, optionally, the determining the DID interface information according to the fault diagnosis DID read-write service information includes:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
The above method, optionally, the determining the DID interface information according to the fault diagnosis DID read-write service information further includes:
and determining DID callback function information according to the fault diagnosis DID read-write service information.
As above, optionally, the writing the DID interface information into the attribute file includes:
and writing the DID parameter information and the DID callback function information into a property file.
The method, optionally, after writing the DID interface information into the attribute file, further includes:
And generating a corresponding callback function based on the DID parameter information and the callback function information.
In a second aspect, there is provided a fault diagnosis DID read-write service processing apparatus, including:
the reading module is used for reading the diagnosis database file if the diagnosis database file is judged to be changed;
the analysis module is used for analyzing the diagnosis database file and extracting the read-write service information of the fault diagnosis data identifier DID;
the determining module is used for determining DID interface information according to the DID read-write service information of fault diagnosis;
the writing module is used for writing the DID interface information into the attribute file;
and the association module is used for importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to associate the DID read-write service information of fault diagnosis and the DID interface information.
The above apparatus, optionally, the determining module is specifically configured to:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
The above apparatus, optionally, the determining module is further configured to:
and determining DID callback function information according to the fault diagnosis DID read-write service information.
The above apparatus, optionally, the writing module is specifically configured to:
And writing the DID parameter information and the DID callback function information into a property file.
The apparatus as above, optionally, the writing module is further configured to:
and generating a corresponding callback function based on the DID parameter information and the callback function information.
In a third aspect, an embodiment of the present invention provides an electronic device, including:
the device comprises a memory and a processor, wherein the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method of: if the diagnosis database file is judged to be changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the fault diagnosis DID read-write service information; writing the DID interface information into a property file; and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
In a fourth aspect, embodiments of the present invention provide a storage medium having stored thereon a computer program which, when executed by a processor, performs a method of: if the diagnosis database file is judged to be changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the fault diagnosis DID read-write service information; writing the DID interface information into a property file; and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
According to the fault diagnosis DID read-write service processing method provided by the embodiment of the invention, after judging that the diagnosis database file is changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the fault diagnosis DID read-write service information; writing the DID interface information into a property file; the attribute file is imported into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information, so that an automatic generation flow of the mapping relation of the diagnosis DID read-write service interface is realized, a great deal of code development or configuration work is not needed, on one hand, the error rate in manual development engineering is reduced, the stability of fault diagnosis DID read-write service software is ensured, on the other hand, the workload is greatly reduced, and the development efficiency of fault diagnosis DID read-write service is improved.
Drawings
FIG. 1 is a schematic diagram of a call relationship of a DID read-write service for MCU fault diagnosis based on a standardized AUTOSAR interface in the prior art;
FIG. 2 is a schematic diagram of a call relationship of a DID read-write service for MCU fault diagnosis based on a Callout callback function in the prior art;
FIG. 3 is a flowchart illustrating steps of an embodiment of a method for processing DID read/write service for fault diagnosis according to the present invention;
FIG. 4 is a schematic diagram of CDD file content in an embodiment of a DID read-write service processing method for fault diagnosis according to the present invention;
FIG. 5 is a flowchart illustrating steps of another embodiment of a method for processing a DID read/write service for fault diagnosis according to the present invention;
fig. 6 is a block diagram showing the structure of an embodiment of a fault diagnosis DID read-write service processing apparatus of the present invention;
fig. 7 is a block diagram of an embodiment of an electronic device of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended detailed description.
In the prior art, when function migration is performed on different platforms or a fault diagnosis service requirement is changed, interface mapping related to a fault diagnosis DID read-write service may be changed greatly, and the changing work is basically realized by manual configuration or development of a developer, so that the problems of large workload, long development period, high error rate and the like are caused. In order to solve the problem, the embodiment of the invention reads the diagnosis database file after judging that the diagnosis database file is changed; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the fault diagnosis DID read-write service information; writing the DID interface information into a property file; the attribute file is imported into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information, so that an automatic generation flow of the mapping relation of the diagnosis DID read-write service interface is realized, a great deal of code development or configuration work is not needed, on one hand, the error rate in manual development engineering is reduced, the stability of fault diagnosis DID read-write service software is ensured, on the other hand, the workload is greatly reduced, and the development efficiency of fault diagnosis DID read-write service is improved.
Referring to fig. 3, a step flowchart of an embodiment of a fault diagnosis DID read-write service processing method according to the present invention may specifically include the following steps:
step S310, if the diagnosis database file is judged to be changed, the diagnosis database file is read;
specifically, in the intelligent driving field, the controller has high requirements on computing power, and the controller comprises a System On Chip (SOC) and a micro control unit (Micro Control Unit, MCU), and the MCU is mainly responsible for the whole vehicle network, functional safety and fault diagnosis, and in terms of fault diagnosis, mainly refers to fault diagnosis based on a unified diagnostic service (Unified Diagnostic Services, UDS) protocol. Before the automobile diagnosis protocol is produced, the automobile maintenance can only rely on the experience of a maintenance master, after the diagnosis protocol, such as the UDS protocol, fault information can be stored in a memory once parts are in problem or have been in problem, the maintenance master can read the fault information through a communication bus, for example, after an electronic control unit (Electronic Control Unit, ECU) experiences an under-voltage fault, diagnosis fault codes (Diagnostic Trouble Code, DTC) represented by the under-voltage fault can be stored, and snapshot information (such as the speed of the automobile, the read voltage value and the like) when the fault occurs can be selectively stored. The snapshot information helps test engineers and after-market engineers find the cause of the failure. After the fault diagnosis information is read based on the UDS protocol, the fault diagnosis and maintenance of the vehicle can be performed.
When developing an MCU chip, MCU suppliers can perform a platform processing so as to be applied to a plurality of projects. When new projects are processed, the diagnosis requirements of each original equipment manufacturer (Original Equipment Manufacturer, OEM) and the corresponding vehicle model are different, and the diagnosis requirements are proposed; in addition, in different stages of the project, such as a sample a, a sample B, a sample C or a mass production stage, the diagnostic requirement may have operations of adding a new requirement, deleting a requirement, updating a requirement, and the like, and the diagnostic requirement is changed.
In the MCU system, when a diagnosis requirement or a diagnosis requirement change is proposed, the diagnosis database file is changed, for example, the generation or update of the diagnosis database file, that is, a new diagnosis database file is generated or the contents in the diagnosis database file are changed, for example, added, deleted, updated, etc. The diagnostic database file may be monitored in real time to determine if it has changed. The diagnostic database file is an ODX (Open diagnostic data exchange, open diagnostic data interaction) file or a CDD (CANdela Diagnostic Descriptions, candelia diagnostic description) file in the MCU system.
ODX files and CDD files exist physically in the form of extensible markup language (Extensible Markup Language, XML) files that can be opened directly with a text editor or XML tool, but this approach is very poorly readable and difficult for a layman to see. ODX is a standardized diagnostic file, the ODX unifies the format of the diagnostic file, and format conversion is not needed when the diagnostic file is transferred and exchanged in research, test, production, after-sales and other departments. After the ODX file is available, when different vehicles or different ECUs are diagnosed, only the ODX file adapting to the vehicle model or the ECUs is needed to be loaded, and no change is needed to be made to a diagnostic instrument.
If it is judged that the ODX/CDD file is changed, the ODX/CDD file content is read, and specifically, the ODX/CDD file content can be automatically read through a script, for example, the file content of the ODX/CDD file is read through a Python script according to the rule of reading an XML file format, and diagnostic information recorded in the ODX/CDD file is obtained.
Step S320, analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier;
specifically, the diagnostic database ODX/CDD file is parsed, the fault diagnosis DID read-write service information is extracted, in the ODX/CDD file, the fault diagnosis DID read-write service information has a corresponding identifier, for example, an identifier with "DID" in the field of the ODX/CDD file, and the script is used to parse the diagnostic database ODX/CDD file, so as to extract all the fault diagnosis DID read-write service information.
Referring to fig. 4, a schematic diagram of CDD file content in an embodiment of a method for processing a fault diagnosis DID read/write service according to the present invention is shown, and the part outlined in fig. 4 is fault diagnosis DID read/write service information, and it can be seen that the field has a "DID" identifier, and the field with the "DID" identifier is extracted, so that fault diagnosis DID read/write service information can be extracted.
Step S330, determining DID interface information according to the DID read-write service information of fault diagnosis;
specifically, DID interface information is determined according to the extracted fault diagnosis DID read-write service information,
for example, the Callout callback function information, the port information and the like corresponding to each DID are determined according to the read DIDI read-write service information.
Step S340, writing the DID interface information into a property file;
specifically, when the diagnostic communication service management module DCM module is developed, configuration development is performed in an auto sar tool chain, and the corresponding configuration attribute file is an Arxml file. In the prior art, the DID interface information is configured in the configuration item of the DCM module in the tool chain, and the tool chain is synchronized to the configuration Arxml file. When the number of DID is relatively large, the corresponding DID interface information is also large, and the workload is very large if the DID interface information is configured one by one in the tool chain. In order to solve the problem, in the embodiment of the present invention, the determined fault diagnosis DID interface information is written into an attribute file of the diagnosis communication service management module DCM, where the attribute file is an Arxml file, the physical existence form of the Arxml file is the same as that of the ODX/CDD file, and is an XML file, the location of the DID interface information in the Arxml file is found, and the determined DID interface information is written into the location of the DID interface information in the Arxml file. Therefore, the Arxml file is directly updated and configured through the script without filling in the content of the configuration item through the tool chain.
And step S350, importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the DID read-write service information of fault diagnosis and the DID interface information.
Specifically, after the determined DID interface information is written in the location of the DID interface information in the Arxml file, the attribute file is also required to be imported into an AUTOSAR configuration tool chain, and configuration information is generated through the AUTOSAR configuration tool chain, so that fault diagnosis DID read-write service information and DID interface information can be associated, and DID interface mapping is achieved.
According to the fault diagnosis DID read-write service processing method provided by the embodiment of the invention, after judging that the diagnosis database file is changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the fault diagnosis DID read-write service information; writing the DID interface information into a property file; the attribute file is imported into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information, so that an automatic generation flow of the mapping relation of the diagnosis DID read-write service interface is realized, a great deal of code development or configuration work is not needed, on one hand, the error rate in manual development engineering is reduced, the stability of fault diagnosis DID read-write service software is ensured, on the other hand, the workload is greatly reduced, and the development efficiency of fault diagnosis DID read-write service is improved.
On the basis of the foregoing embodiment, further, the determining the DID interface information according to the fault diagnosis DID read-write service information includes:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
Specifically, the DID parameter information, such as the DID identification, DID description information, etc., is determined from the extracted failure diagnosis DID read-write service information.
After the DID parameter information is determined, the DID callback function information, such as Callout callback function names corresponding to the respective DID, such as read function names, write function names, etc., may be further determined.
And then, the determined DID parameter information and callback function information are written into an Arxml file of the attribute file, so that the attribute file contains the DID information and the corresponding interface information.
After the DID callback function information is written in the attribute file Arxml file, the DID callback function information needs to be generated. The corresponding interface functions in the DCM module or the configuration attribute Arxml file are only 1 interface function name, but the entity of the function is realized by handwriting codes, and the main body of the Callout function can be automatically generated through script because the Callout function names are related to DID and are regular. Specifically, the Callout callback function corresponding to each DID is generated according to the filled DID callback function information, and the input parameter and the return parameter of the Callout callback function may be determined by the fault diagnosis requirement, where the difference is that the function name corresponding to each Callout callback function of each DID is different.
For example, the DCM attribute files Arxml and Callout callback functions can be automatically generated through script, the interface and interface relation is automatically realized, the complicated procedure of mapping manually one by one is avoided, and the mapping efficiency is improved. Finally, the filled attribute files are imported into an AUTOSAR configuration tool chain, configuration information is generated by using the AUTOSAR configuration tool chain, fault diagnosis DID read-write service information is extracted by analyzing an automatic script of the diagnosis database ODX/CDD file, repeated importing and repeated configuration of the diagnosis database file by the AUTOSAR tool chain are avoided, the written attribute files are associated with the generated Callout callback function, and a fault diagnosis DID read-write service information interface mapping function is realized.
For example, for did_0xf414 in fig. 4, after this failure diagnosis DID information is read, it is determined that callback functions corresponding to the interface information of the DID are respectively: DID_0xF414_ReadData or DID_0xF414_WriteData. The did_0xf414_readdata or did_0xf414_writedata interface function is then written to the configuration attribute Arxml file. And finally, importing the configuration attribute Arxml file into an AUTOSAR configuration tool chain, and generating configuration information through the AUTOSAR configuration tool chain, so that fault diagnosis DID read-write service information (DID_0xF414) and DID interface information (DID_0xF414_ReadData or DID_0xF414_WriteData interface function) can be associated, and DID interface mapping can be realized.
On the one hand, in the DCM module development stage, configuration development is performed in an auto sar tool chain, and corresponding configuration attribute Arxml files are provided, in the prior art, configuration item contents are filled in through the tool chain, when DID is relatively large, corresponding read-write interface functions are also relatively large, and if configuration is performed in the tool chain one by one, the workload is particularly large. In the embodiment of the invention, the configuration item content is not filled in through a tool chain, and the interface function content in the configuration attribute Arxml file is directly updated or rewritten (over write) through a script, so that the automatic production of the configuration attribute Arxml file is realized; on the other hand, the corresponding interface function in the DCM module or the configuration attribute Arxml file is just an interface function name, but the entity of the function is realized by handwriting codes, and because the Callout function names are related to DID and are regular, the main body of the Callout function is automatically generated through script in the embodiment of the invention; when the DID is more, the corresponding Callout functions are more, and at this time, the flow of automatically generating the Callout functions is more efficient and is less prone to error compared with the prior art.
Referring to fig. 5, a flowchart illustrating steps of another embodiment of a method for processing a fault diagnosis DID read/write service according to the present invention may specifically include the following steps:
Step S510, judging that the ODX/CDD file of the diagnosis database is proposed or updated;
specifically, when the diagnosis requirement is set up or changed, the diagnosis database ODX/CDD file is updated;
step S520, reading and analyzing DID information in the diagnosis database ODX/CDD through an automatic script;
specifically, reading the ODX/CDD file content of a diagnosis database through an automatic script, and extracting DID read-write service information in the ODX/CDD file content;
step S530, adding the extracted DID information into an Arxml file of the attribute file of the DCM module;
specifically, the extracted DID read-write service information for fault diagnosis is written into an Arxml file of an attribute file of the DCM module through a script;
step S540, automatically generating a Callout calling function matched with the DID read-write service;
specifically, automatically generating a Callout calling function corresponding to the DID read-write service through a script;
step S550, importing tools automatically generate DCM module configuration and configuration codes;
specifically, importing an Arxml file of a DCM module attribute file into an AUTOSAR configuration tool chain, automatically generating configuration content, and further generating configuration codes;
step S560, automatic generation or connection of fault diagnosis DID read-write service interface based on AUTOSAR architecture
Through the steps, the automatic generation or connection of the DID read-write service interface for fault diagnosis can be completed.
For example, in the development stage of the intelligent driving field, 1 fault diagnosis DID of "camera calibration result" is newly added in the diagnosis requirement, if the fault diagnosis DID interface information of "camera calibration result" is all imported into the ODX/CDD file to the auto sar tool chain, the configuration is updated, and then manually adapted and developed, the whole process is time-consuming, and may bring new configuration modification due to the format or attribute information problem of the ODX/CDD file itself, manual adjustment and correction are required, the whole process is time-consuming and labor-consuming, and error-prone. If the fault diagnosis DID read-write service processing method provided by the embodiment of the invention can automatically analyze the content of the ODX/CDD file, read the fault diagnosis DID information of the 'camera calibration result' through a script, determine the fault diagnosis DID read-write interface function of the 'camera calibration result' according to the fault diagnosis DID information of the 'camera calibration result', write the fault diagnosis DID read-write interface function of the 'camera calibration result' into the configuration attribute Arxml file of the DCM module, import the configuration attribute Arxml file into an AUTOSAR configuration tool chain to generate configuration information so as to correlate the fault diagnosis DID of the 'camera calibration result' with the corresponding read-write interface function, realize the automatic update of the configuration Arxml file of the DCM module, avoid the manual one-by-one import process and improve the fault diagnosis DID read-write service processing efficiency.
According to the fault diagnosis DID read-write service processing method provided by the embodiment of the invention, on the basis of processing the DID read-write service by adopting the Callout calling function, the interface mapping relation between the Callout calling function and the DID read-write service is changed from manual matching relation change to automatic matching relation generation. Firstly, when the diagnosis requirement is set up or the diagnosis requirement is changed, the generation or updating of the ODX/CDD file of the diagnosis database is accompanied; then, taking a diagnosis database ODX/CDD file as input, automatically analyzing the file through a script and extracting DID read-write service content, on one hand, generating DID attribute information in a diagnosis communication module DCM, and importing the DID attribute information into a configuration AUTOSAR tool chain, and on the other hand, generating a Callout calling function of the fault diagnosis DID read-write service; the automatic mapping of the DID read-write service and the Callout calling function in the diagnosis communication module DCM is completed through the automatic import of the DID configuration attribute in the AUTOSAR tool chain and the automatic generation of the Callout calling function; the automatic generation flow of the DID read-write service mapping connection relation is not required to carry out a large amount of code development or configuration work, so that on one hand, the error rate in manual development engineering is reduced, the software stability is ensured, on the other hand, the workload is greatly reduced, and the development efficiency is improved.
Referring to fig. 6, a block diagram of an embodiment of a fault diagnosis DID read-write service processing apparatus according to the present invention may specifically include the following modules: a reading module 610, a parsing module 620, a determining module 630, a writing module 640, and an associating module 650, wherein:
the reading module 610 is configured to read the diagnostic database file if it is determined that the diagnostic database file is changed; the parsing module 620 is configured to parse the diagnostic database file and extract the fault diagnosis data identifier DID read-write service information; the determining module 630 is configured to determine DID interface information according to the fault diagnosis DID read-write service information; the writing module 640 is configured to write the DID interface information into a property file; the association module 650 is configured to import the attribute file into an automotive open system architecture auto sar configuration tool chain, and generate configuration information to associate the fault diagnosis DID read-write service information with the DID interface information.
Optionally, the determining module 630 is specifically configured to:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
Optionally, the determining module 630 is further configured to:
and determining DID callback function information according to the fault diagnosis DID read-write service information.
Optionally, the writing module 640 is specifically configured to:
and writing the DID parameter information and the DID callback function information into a property file.
Optionally, the writing module 640 is further configured to:
and generating a corresponding callback function based on the DID parameter information and the callback function information.
Specifically, in the intelligent driving field, the controller has higher requirement on computing capability, the controller comprises an SOC chip and an MCU, the MCU is mainly responsible for whole vehicle network, functional safety and fault diagnosis, and the fault diagnosis mainly refers to fault diagnosis based on UDS protocol. When developing an MCU chip, MCU suppliers can perform a platform processing so as to be applied to a plurality of projects. When a new project is processed, the diagnosis requirements of each OEM and the corresponding vehicle model are different, and the diagnosis requirements are proposed; in addition, in different stages of the project, such as a sample a, a sample B, a sample C or a mass production stage, the diagnostic requirement may have operations of adding a new requirement, deleting a requirement, updating a requirement, and the like, and the diagnostic requirement is changed.
In the MCU system, when a diagnosis requirement or a diagnosis requirement change is proposed, the diagnosis database file is changed, for example, the generation or update of the diagnosis database file, that is, a new diagnosis database file is generated or the contents in the diagnosis database file are changed, for example, added, deleted, updated, etc. The reading module 610 may monitor the diagnostic database file in real time to determine if it has changed. The diagnosis database file is an ODX file or a CDD file in the MCU system, and the physical existence form of the ODX file and the CDD file is an XML file.
If the reading module 610 determines that the ODX/CDD file is changed, the ODX/CDD file content is read, specifically, the reading module 610 may automatically read the ODX/CDD file content through a script, for example, the reading module 610 reads the file content of the ODX/CDD file according to the rule of reading the XML file format through a Python script, and obtains diagnostic information recorded in the ODX/CDD file.
The parsing module 620 parses the diagnostic database ODX/CDD file, extracts the fault diagnosis DID read/write service information, where the fault diagnosis DID read/write service information has a corresponding identifier in the field of the ODX/CDD file, for example, an identifier with "DID", etc., and the parsing module 620 parses the diagnostic database ODX/CDD file using the script, and extracts all the fault diagnosis DID read/write service information. The determining module 630 determines the DID interface information according to the extracted fault diagnosis DID read-write service information, for example, the determining module 630 determines Callout callback function information, port information, and the like corresponding to each DID according to the read DID read-write service information.
The writing module 640 writes the DID interface information into a property file;
specifically, when the diagnostic communication service management module DCM module is developed, configuration development is performed in an auto sar tool chain, and the corresponding configuration attribute file is an Arxml file. In the prior art, the DID interface information is configured in the configuration item of the DCM module in the tool chain, and the tool chain is synchronized to the configuration Arxml file. When the number of DID is relatively large, the corresponding DID interface information is also large, and the workload is very large if the DID interface information is configured one by one in the tool chain. To solve this problem, in the embodiment of the present invention, the writing module 640 writes the determined fault diagnosis DID interface information into an attribute file of the diagnostic communication service management module DCM, where the attribute file is an Arxml file, the physical existence form of the Arxml file is the same as that of the ODX/CDD file, and is an XML file, so as to find the location of the DID interface information in the Arxml file, and writes the determined DID interface information in the location of the DID interface information in the Arxml file. Therefore, the Arxml file is directly updated and configured through the script without filling in the content of the configuration item through the tool chain.
The association module 650 imports the attribute file into an AUTOSAR configuration tool chain to generate configuration information to associate the fault diagnosis DID read-write service information with the DID interface information.
Specifically, after the determined DID interface information is written in the location of the DID interface information in the Arxml file, the attribute file is also required to be imported into an AUTOSAR configuration tool chain, and configuration information is generated through the AUTOSAR configuration tool chain, so that fault diagnosis DID read-write service information and DID interface information can be associated, and DID interface mapping is achieved.
Further, the determining module 630 determines DID parameter information, such as DID identification, DID description information, etc., from the extracted fault diagnosis DID read-write service information. After determining the DID parameter information, the determining module 630 may further determine DID callback function information, for example, callout callback function names corresponding to each DID, for example, read function names, write function names corresponding to each DID, and so on.
Then, the writing module 640 writes the determined DID parameter information and callback function information into the attribute file Arxml file, so that the attribute file contains the DID information and the corresponding interface information thereof.
After the DID callback function information is written in the attribute file Arxml file, the DID callback function information needs to be generated. The corresponding interface functions in the DCM module or the configuration attribute Arxml file are only 1 interface function name, but the entity of the function is realized by handwriting codes, and the main body of the Callout function can be automatically generated through script because the Callout function names are related to DID and are regular. Specifically, the Callout callback function corresponding to each DID is generated according to the filled DID callback function information, and the input parameter and the return parameter of the Callout callback function may be determined by the fault diagnosis requirement, where the difference is that the function name corresponding to each Callout callback function of each DID is different.
On the one hand, in the DCM module development stage, configuration development is performed in an auto sar tool chain, and corresponding configuration attribute Arxml files are provided, in the prior art, configuration item contents are filled in through the tool chain, when DID is relatively large, corresponding read-write interface functions are also relatively large, and if configuration is performed in the tool chain one by one, the workload is particularly large. In the embodiment of the invention, the configuration item content is not filled in through a tool chain, and the interface function content in the configuration attribute Arxml file is directly updated or rewritten (over write) through a script, so that the automatic production of the configuration attribute Arxml file is realized; on the other hand, the corresponding interface function in the DCM module or the configuration attribute Arxml file is just an interface function name, but the entity of the function is realized by handwriting codes, and because the Callout function names are related to DID and are regular, the main body of the Callout function is automatically generated through script in the embodiment of the invention; when the DID is more, the corresponding Callout functions are more, and at this time, the flow of automatically generating the Callout functions is more efficient and is less prone to error compared with the prior art.
According to the fault diagnosis DID read-write service processing device provided by the embodiment of the invention, on the basis of processing the DID read-write service by adopting the Callout calling function, the interface mapping relation between the Callout calling function and the DID read-write service is changed from manual matching relation change to automatic matching relation generation. Firstly, when the diagnosis requirement is set up or the diagnosis requirement is changed, the generation or updating of the ODX/CDD file of the diagnosis database is accompanied; then, taking a diagnosis database ODX/CDD file as input, automatically analyzing the file through a script and extracting DID read-write service content, on one hand, generating DID attribute information in a diagnosis communication module DCM, and importing the DID attribute information into a configuration AUTOSAR tool chain, and on the other hand, generating a Callout calling function of the fault diagnosis DID read-write service; the automatic mapping of the DID read-write service and the Callout calling function in the diagnosis communication module DCM is completed through the automatic import of the DID configuration attribute in the AUTOSAR tool chain and the automatic generation of the Callout calling function; the automatic generation flow of the DID read-write service mapping connection relation is not required to carry out a large amount of code development or configuration work, so that on one hand, the error rate in manual development engineering is reduced, the software stability is ensured, on the other hand, the workload is greatly reduced, and the development efficiency is improved. For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.
Fig. 7 is a block diagram of an embodiment of an electronic device of the present invention, as shown in fig. 7, the device includes: a processor 610, a memory 720, and a bus 730;
wherein processor 710 and memory 720 communicate with each other via bus 730;
processor 710 is configured to invoke program instructions in memory 720 to perform the methods provided by the method embodiments described above, including, for example: if the diagnosis database file is judged to be changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the DID read-write service information of fault diagnosis; writing the DID interface information into a property file; and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
Embodiments of the present invention disclose a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, enable the computer to perform the methods provided by the method embodiments described above, for example comprising: if the diagnosis database file is judged to be changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the DID read-write service information of fault diagnosis; writing the DID interface information into a property file; and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
Embodiments of the present invention provide a non-transitory computer readable storage medium storing computer instructions that cause a computer to perform the methods provided by the above-described method embodiments, for example, including: if the diagnosis database file is judged to be changed, the diagnosis database file is read; analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier; determining DID interface information according to the DID read-write service information of fault diagnosis; writing the DID interface information into a property file; and importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to correlate the fault diagnosis DID read-write service information and the DID interface information.
It should be noted that, for simplicity of description, the method embodiments are shown as a series of acts, but it should be understood by those skilled in the art that the embodiments are not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts are not necessarily required by the embodiments of the invention.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
It will be apparent to those skilled in the art that embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the invention may take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the invention.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
The above describes in detail a method and a device for processing a DID read-write service for fault diagnosis provided by the present invention, and specific examples are applied to illustrate the principles and embodiments of the present invention, and the above description of the examples is only used to help understand the method and core idea of the present invention; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present invention, the present description should not be construed as limiting the present invention in view of the above.
Claims (10)
1. The DID read-write service processing method for fault diagnosis is characterized by comprising the following steps:
if the diagnosis database file is judged to be changed, the diagnosis database file is read;
analyzing the diagnosis database file, and extracting the DID read-write service information of the fault diagnosis data identifier;
determining DID interface information according to the DID read-write service information of fault diagnosis;
writing the DID interface information into a property file;
importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture, and generating configuration information so as to correlate the DID read-write service information of fault diagnosis and the DID interface information;
the attribute file is an attribute file of a diagnosis communication service management module DCM, and the DID interface information is DID parameter information and DID callback function information.
2. The method of claim 1, wherein the determining DID interface information according to the fault diagnosis DID read-write service information comprises:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
3. The method of claim 2, wherein determining DID interface information from the fault diagnosis DID read-write service information further comprises:
And determining DID callback function information according to the fault diagnosis DID read-write service information.
4. The method of claim 3, wherein the writing the DID interface information into the properties file comprises:
and writing the DID parameter information and the DID callback function information into a property file.
5. The method of claim 4, wherein the writing the DID interface information to the properties file further comprises:
and generating a corresponding callback function based on the DID parameter information and the callback function information.
6. A fault diagnosis DID read-write service processing apparatus, characterized by comprising:
the reading module is used for reading the diagnosis database file if the diagnosis database file is judged to be changed;
the analysis module is used for analyzing the diagnosis database file and extracting the read-write service information of the fault diagnosis data identifier DID;
the determining module is used for determining DID interface information according to the DID read-write service information of fault diagnosis;
the writing module is used for writing the DID interface information into the attribute file;
the association module is used for importing the attribute file into an AUTOSAR configuration tool chain of an automobile open system architecture to generate configuration information so as to associate the DID read-write service information of fault diagnosis with the DID interface information;
The attribute file is an attribute file of a diagnosis communication service management module DCM, and the DID interface information is DID parameter information and DID callback function information.
7. The apparatus of claim 6, wherein the determining module is specifically configured to:
and determining DID parameter information according to the fault diagnosis DID read-write service information.
8. The apparatus of claim 7, wherein the means for determining is further for:
and determining DID callback function information according to the fault diagnosis DID read-write service information.
9. An electronic device, comprising:
the device comprises a memory and a processor, wherein the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1-5.
10. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310807808.XA CN116521143B (en) | 2023-07-04 | 2023-07-04 | DID read-write service processing method and device for fault diagnosis |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310807808.XA CN116521143B (en) | 2023-07-04 | 2023-07-04 | DID read-write service processing method and device for fault diagnosis |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116521143A CN116521143A (en) | 2023-08-01 |
| CN116521143B true CN116521143B (en) | 2023-09-29 |
Family
ID=87392566
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310807808.XA Active CN116521143B (en) | 2023-07-04 | 2023-07-04 | DID read-write service processing method and device for fault diagnosis |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116521143B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103529821A (en) * | 2013-09-29 | 2014-01-22 | 重庆邮电大学 | Configurable method and device for diagnostic protocol stack system based on CAN (controller area network) bus |
| GB201409237D0 (en) * | 2014-05-23 | 2014-07-09 | Daimler Ag | Method and system for diagnosing faults of a component of a vehicle |
| KR101629184B1 (en) * | 2014-12-10 | 2016-06-13 | 현대오트론 주식회사 | Method for calling periodic function to enhance process speed of EEPROM in AUTOSAR |
| WO2019228556A2 (en) * | 2019-07-02 | 2019-12-05 | Alibaba Group Holding Limited | System and method for decentralized-identifier creation |
| WO2022041720A1 (en) * | 2020-08-24 | 2022-03-03 | 华为技术有限公司 | Uds-based communication method, ecu and upper computer |
| CN114942745A (en) * | 2021-02-08 | 2022-08-26 | 广汽埃安新能源汽车有限公司 | Automatic configuration method for UDS protocol stack of motor controller |
| CN115328853A (en) * | 2022-08-15 | 2022-11-11 | 合众新能源汽车有限公司 | AUTOSAR-based file configuration method and device |
| CN115546927A (en) * | 2022-11-01 | 2022-12-30 | 于墨 | UDS diagnosis automatic test system based on AUTOSAR standard |
| CN115599382A (en) * | 2022-10-25 | 2023-01-13 | 上海智驾汽车科技有限公司（Cn） | Automatic Sar architecture based code automatic generation tool and method |
| CN116244348A (en) * | 2023-03-30 | 2023-06-09 | 岚图汽车科技有限公司 | Method, device, equipment and storage medium for processing vehicle diagnosis demand data |
| CN116300809A (en) * | 2023-03-14 | 2023-06-23 | 惠州市德赛西威智能交通技术研究院有限公司 | Method, system and storage medium for realizing diagnosis and upgrading of vehicle-mounted equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9424608B2 (en) * | 2014-10-09 | 2016-08-23 | Wrap Media, LLC | Generating and delivering a wrap package of cards including custom content and/or services in response to a vehicle diagnostic system triggered event |
| US11012305B2 (en) * | 2017-08-09 | 2021-05-18 | Servicenow, Inc. | Systems and methods for service mapping |
-
2023
- 2023-07-04 CN CN202310807808.XA patent/CN116521143B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102981501A (en) * | 2012-11-30 | 2013-03-20 | 重庆邮电大学 | Automobile ECU (Electronic Control Unit) fault diagnosis information matching method based on XML (Extensive Makeup Language) |
| CN103529821A (en) * | 2013-09-29 | 2014-01-22 | 重庆邮电大学 | Configurable method and device for diagnostic protocol stack system based on CAN (controller area network) bus |
| GB201409237D0 (en) * | 2014-05-23 | 2014-07-09 | Daimler Ag | Method and system for diagnosing faults of a component of a vehicle |
| KR101629184B1 (en) * | 2014-12-10 | 2016-06-13 | 현대오트론 주식회사 | Method for calling periodic function to enhance process speed of EEPROM in AUTOSAR |
| WO2019228556A2 (en) * | 2019-07-02 | 2019-12-05 | Alibaba Group Holding Limited | System and method for decentralized-identifier creation |
| WO2022041720A1 (en) * | 2020-08-24 | 2022-03-03 | 华为技术有限公司 | Uds-based communication method, ecu and upper computer |
| CN114942745A (en) * | 2021-02-08 | 2022-08-26 | 广汽埃安新能源汽车有限公司 | Automatic configuration method for UDS protocol stack of motor controller |
| CN115328853A (en) * | 2022-08-15 | 2022-11-11 | 合众新能源汽车有限公司 | AUTOSAR-based file configuration method and device |
| CN115599382A (en) * | 2022-10-25 | 2023-01-13 | 上海智驾汽车科技有限公司（Cn） | Automatic Sar architecture based code automatic generation tool and method |
| CN115546927A (en) * | 2022-11-01 | 2022-12-30 | 于墨 | UDS diagnosis automatic test system based on AUTOSAR standard |
| CN116300809A (en) * | 2023-03-14 | 2023-06-23 | 惠州市德赛西威智能交通技术研究院有限公司 | Method, system and storage medium for realizing diagnosis and upgrading of vehicle-mounted equipment |
| CN116244348A (en) * | 2023-03-30 | 2023-06-09 | 岚图汽车科技有限公司 | Method, device, equipment and storage medium for processing vehicle diagnosis demand data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116521143A (en) | 2023-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109343857B (en) | Method, apparatus and storage medium for deploying machine learning model on line | |
| CN106980560B (en) | ICD database based multi-bus protocol testing and simulating method and platform | |
| CN107179971B (en) | Automatic coding method and system for CAN bus fault processing | |
| CN107370637B (en) | Vehicle-mounted ECU communication function automatic test system and method | |
| CN112035363A (en) | Automatic interface testing method and device | |
| CN115167831A (en) | Software integration method and device based on AUTOSAR and use method | |
| CN110543427B (en) | Test case storage method and device, electronic equipment and storage medium | |
| CN110989549B (en) | Software test general automation control method and device for train control system | |
| Sandmann et al. | Autosar-compliant development workflows: From architecture to implementation-tool interoperability for round-trip engineering and verification and validation | |
| CN117234926A (en) | AUTOSAR architecture-based software component interface checking method and device | |
| CN114460925B (en) | Automatic test method for CAN interface HIL of electric automobile controller | |
| CN101673200B (en) | The detection method of user input model and device | |
| CN116521143B (en) | DID read-write service processing method and device for fault diagnosis | |
| CN112947896A (en) | Directed graph-based component dependence analysis method | |
| CN116521217A (en) | Method, system and storage medium for rapidly configuring BSW based on AUTOSAR tool | |
| CN113032256B (en) | Automated testing method, apparatus, computer system, and readable storage medium | |
| CN115348200A (en) | CAN communication function test method and test system | |
| CN114488997A (en) | ECU (electronic control Unit) flashing method and device, electronic equipment and storage medium | |
| CN113985849A (en) | Method for writing DTC (digital control channel) read ECU (electronic control unit) version of automatic clear-reading whole vehicle based on CANoe software | |
| CN107844639B (en) | Project standard structure automatic generation method and system | |
| Bergelt et al. | Towards Cloud-supported Automotive Software Development and Test | |
| CN112784434A (en) | Model-based avionics design method | |
| CN114064449A (en) | Simulation test report generation method and device, electronic equipment and storage medium | |
| CN116755684B (en) | OAS Schema generation method, device, equipment and medium | |
| CN117952069A (en) | ARXML file processing method, ARXML file processing device, ARXML file processing equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |