CN111949005B - Method, device and equipment for acquiring frozen frame data and storage medium - Google Patents
Method, device and equipment for acquiring frozen frame data and storage medium Download PDFInfo
- Publication number
- CN111949005B CN111949005B CN202010751067.4A CN202010751067A CN111949005B CN 111949005 B CN111949005 B CN 111949005B CN 202010751067 A CN202010751067 A CN 202010751067A CN 111949005 B CN111949005 B CN 111949005B
- Authority
- CN
- China
- Prior art keywords
- data
- frame data
- ecu
- ecu system
- fault codes
- 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
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
- G05B23/0213—Modular or universal configuration of the monitoring system, e.g. monitoring system having modules that may be combined to build monitoring program; monitoring system that can be applied to legacy systems; adaptable monitoring system; using different communication protocols
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B2219/00—Program-control systems
- G05B2219/20—Pc systems
- G05B2219/24—Pc safety
- G05B2219/24065—Real time diagnostics
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a method, a device, equipment and a storage medium for acquiring frozen frame data, relates to the technical field of vehicle diagnosis, and can improve the acquisition efficiency and accuracy of the frozen frame data. The method comprises the following steps: analyzing vehicle diagnosis data to obtain communication data related to freezing frame data of each Electronic Control Unit (ECU) system of a vehicle to be diagnosed, and fault codes and data streams respectively corresponding to the freezing frame data of each ECU system; for each ECU system in each ECU system, respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects; calling a data export interface to respectively export the fault codes and the data streams corresponding to the respective frozen frame data of each ECU system from the different container objects; and respectively storing the communication data associated with the freezing frame data of each ECU system and the exported fault mother and data stream corresponding to each freezing frame data in different preset files in an associated manner.
Description
Technical Field
The present application relates to the field of vehicle diagnosis technologies, and in particular, to a method, an apparatus, a device, and a storage medium for acquiring freeze frame data.
Background
When a vehicle has a fault, an ECU (Electronic Control Unit) corresponding to the fault location generates a corresponding fault code, and also generates freeze frame data corresponding to the fault code, where the freeze frame data indicates the operating state data of the vehicle when the fault code is generated. Therefore, the frozen frame data is greatly helpful for analyzing the vehicle fault, and the abnormal position and the abnormal reason can be better located and found by analyzing the frozen frame data. Currently, in order to acquire required freeze frame data in customized diagnostic items, a worker needs to search and confirm each item of diagnostic data in each vehicle ECU, for example, diagnostic data such as ECU-related information, fault code data and data streams, which not only wastes a lot of human resources, but also causes low efficiency in acquiring freeze frame data and is prone to errors.
Disclosure of Invention
The embodiment of the application provides a method, a device, equipment and a storage medium for acquiring frozen frame data, which can greatly improve the acquisition efficiency of the frozen frame data and are not easy to make mistakes.
In a first aspect, the present application provides a method for obtaining freeze frame data, including:
analyzing vehicle diagnosis data to obtain communication data related to freezing frame data of each Electronic Control Unit (ECU) system of a vehicle to be diagnosed, and fault codes and data streams respectively corresponding to the freezing frame data of each ECU system;
for each ECU system in each ECU system, respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects;
calling a data export interface to respectively export the fault codes and the data streams corresponding to the respective frozen frame data of each ECU system from the different container objects;
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different preset files in an associated manner.
In an optional implementation, the container object is a vector container;
for each of the ECU systems, respectively storing the fault code and the data stream corresponding to the respective freeze frame data into different container objects, including:
and for each ECU system in the ECU systems, storing the fault code corresponding to the respective freeze frame data into a first vector container, and storing the data stream corresponding to the respective freeze frame data of each ECU system into a second vector container.
In an alternative implementation, the data export interface comprises a first data export interface and a second data export interface;
the calling data export interface respectively exports fault codes and data streams corresponding to respective frozen frame data from the different container objects, and the method comprises the following steps:
and calling the first data export interface, calling the second data export interface in sequence, and exporting the fault codes and the data streams corresponding to the frozen data of the ECU according to a preset path.
In an alternative implementation, the data export interface comprises a first data export interface;
calling a data export interface to respectively export fault codes and data streams corresponding to respective frozen frame data from the different container objects, wherein the data export interface comprises the following steps:
and calling the first data export interface, and exporting the fault codes and the data streams corresponding to the respective frozen frame data according to a preset path.
In an optional implementation manner, the preset file is an EXCEL file;
respectively and correlatively storing communication data correlated with the respective frozen frame data of each ECU system and fault codes and data streams corresponding to the respective frozen frame data which are derived into different preset files, wherein the method comprises the following steps:
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different EXCEL files in an associated manner.
In an optional implementation manner, the associating, in different EXCEL files, communication data associated with respective frozen frame data of each ECU system and the derived fault code and data stream corresponding to each respective frozen frame data are respectively stored in association, including:
respectively writing communication data related to the respective freezing frame data of each ECU system into a preset first Sheet label page of the EXCEL file corresponding to each ECU system;
respectively writing fault codes corresponding to the respective freezing frame data of each ECU system into a third Sheet label page of the EX CEL file corresponding to each ECU system;
and respectively writing the data stream corresponding to the respective freezing frame data of each ECU system into a second sheet label page of the EXCEL file corresponding to each ECU system.
In an alternative implementation, the freeze frame data includes an ECU name, ECU filter identification information, and ECU response identification information.
In a second aspect, the present application provides a frozen frame data obtaining apparatus, including:
the analysis module is used for analyzing the vehicle diagnosis data to obtain communication data related to the freezing frame data of each electronic control unit ECU system of the vehicle to be diagnosed, and fault codes and data streams corresponding to the freezing frame data of each ECU system;
the storage module is used for respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects for each ECU system in each ECU system;
the export module is used for calling a data export interface to respectively export the fault code and the data stream corresponding to the respective frozen frame data of each ECU system from the different container objects;
and the writing module is used for respectively and correlatively storing the communication data related to the respective frozen frame data of each ECU system and the derived fault codes and data streams corresponding to the respective frozen frame data in different preset files.
In an optional implementation, the container object is a vector container;
the storage module is specifically configured to:
and for each ECU system in the ECU systems, storing the fault code corresponding to the respective freeze frame data into a first vector container, and storing the data stream corresponding to the respective freeze frame data of each ECU system into a second vector container.
In an alternative implementation, the data export interface comprises a first data export interface and a second data export interface;
the export module is specifically configured to:
and calling the first data export interface, calling the second data export interface in sequence, and exporting the fault codes and the data streams corresponding to the frozen data of the ECU according to a preset path.
In an alternative implementation, the data export interface comprises a first data export interface;
the export module is specifically configured to:
and calling the first data export interface, and exporting the fault codes and the data streams corresponding to the respective frozen frame data according to a preset path.
In an optional implementation manner, the preset file is an EXCEL file;
the write module is specifically configured to:
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different EXCEL files in an associated manner.
In an optional implementation manner, the writing module includes:
the first writing unit is used for respectively writing the communication data related to the respective frozen frame data of each ECU system into a preset first Sheet label page of the EXCEL file corresponding to each ECU system;
a second writing unit, configured to write the fault code corresponding to the respective frozen frame data of each ECU system into a third Sheet tab of the EX CEL file corresponding to each ECU system;
and a third writing unit, configured to write the data stream corresponding to the respective freeze frame data of each ECU system into a second sheet tab of the EXCEL file corresponding to each ECU system.
In an alternative implementation, the freeze frame data includes an ECU name, ECU filter identification information, and ECU response identification information.
In a third aspect, the present application provides an electronic device, comprising:
a memory for storing a freeze frame data acquisition program;
a processor, configured to implement the frozen frame data acquisition method according to the first aspect or any optional manner of the first aspect when executing the frozen frame data acquisition program.
In a fourth aspect, the present application provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the frozen frame data acquisition method according to the first aspect or any alternative of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer program product, which, when run on an electronic device, causes the electronic device to execute the steps of the method for acquiring freeze frame data according to the first aspect or any optional manner of the first aspect.
By adopting the method for acquiring the frozen frame data, communication data associated with the frozen frame data of each ECU system of the vehicle to be diagnosed and fault codes and data streams corresponding to the respective frozen frame data of each ECU system are respectively stored in different preset files in an associated manner. Therefore, the method and the device ensure that the staff can acquire the required frozen frame data in the preset file, can effectively improve the acquisition efficiency of the frozen frame data, and are not easy to make mistakes.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a schematic illustration of the principle of analyzing vehicle diagnostic data;
fig. 2 is a schematic flow chart of a freeze frame data obtaining method according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating an implementation of S204 in FIG. 2;
fig. 4 is a schematic diagram of a freeze frame data acquiring apparatus according to an embodiment of the present application;
fig. 5 is a schematic diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "first," "second," "third," and the like in the description of the present application and in the appended claims, are used for distinguishing between descriptions that are not intended to indicate or imply relative importance.
It should also be appreciated that reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. The terms "include" and its derivatives mean "including, but not limited to," unless otherwise specifically noted.
Before explaining the method provided by the present application, an exemplary explanation is first given to related concepts in the frozen frame data acquisition process and the frozen frame data acquisition principle employed by the present application.
At present, vehicle diagnostic data based on the ODX standard is provided by an automobile manufacturer, and generally includes a series of XML files, and different types of diagnostic data are encapsulated by XML tags, and each type of diagnostic data generally has a unique identification information ID and name, and the name of the diagnostic data is generally denoted as shortname or longname. When a worker analyzes the vehicle diagnostic data by means of software, for example, using a C + + programming language, a corresponding C + + type is usually designed for each type of diagnostic data, and is used to store specific data in an XML tag corresponding to the type of diagnostic data. Referring to fig. 1, fig. 1 is a schematic diagram of a principle of analyzing vehicle diagnostic data. As can be seen from fig. 1, in the present embodiment, the C + + language is used to define the DATA types of the first-level C + + definitions, such as ECU-VARIANT, DIAG-DATA-DICTIONARY-SPEC, DTC-DOPS, DTC-DOP, DTCs, and DTC, and respectively store the DATA in the XML tags corresponding to the different types of diagnostic DATA. That is, in the prior art, the data in the XML tag is associated with the C + + type, and the data in the XML tag is stored in the corresponding C + + type, so that subsequent calling is facilitated.
However, for some customized vehicle diagnostic items, because the diagnostic requirements need to be adjusted according to the production requirements of the cooperation manufacturers, the vehicle diagnostic process has a condition that does not strictly comply with the ODX standard, and for such a condition, if the required frozen frame data is screened from each diagnostic data acquired from each ECU of the vehicle to be diagnosed according to the frozen frame data acquisition process based on the ODX standard, the whole process is very troublesome, and the frozen frame data acquisition efficiency is low.
Therefore, the embodiment of the application provides a method for acquiring freeze frame data, which respectively stores communication data associated with the freeze frame data of each ECU system of a vehicle to be diagnosed and fault codes and data streams corresponding to the respective freeze frame data of each ECU system in association with different preset files. Therefore, the method and the device ensure that the staff can acquire the required frozen frame data in the preset file, can effectively improve the acquisition efficiency of the frozen frame data, and are not easy to make mistakes.
The following describes an exemplary freeze frame data acquisition method provided by the present application, with reference to a specific embodiment.
Referring to fig. 2, fig. 2 is a schematic flowchart of a method for obtaining freeze frame data according to an embodiment of the present application. The execution subject of the freeze frame data acquisition method in this embodiment is an electronic device, and may be a hardware device in various vehicle diagnosis scenarios, for example, a vehicle diagnosis device. The freeze frame data acquisition method as shown in fig. 2 may include:
s201, analyzing the vehicle diagnosis data to obtain communication data related to the freezing frame data of each Electronic Control Unit (ECU) system of the vehicle to be diagnosed, and fault codes and data streams corresponding to the freezing frame data of each ECU system.
In the embodiment of the present application, the freeze frame data includes ECU-related data, for example, an ECU name, ECU filter identification information, ECU response identification information, and the like. It should be noted that each ECU system of the vehicle to be diagnosed corresponds to one ODX-D file, wherein the ODX-D file is the vehicle diagnosis data based on the XML language. And the ODX-D file corresponding to each ECU system comprises freezing frame data of the ECU, and fault codes and data streams corresponding to the freezing frame data. The vehicle diagnosis data is analyzed, namely an ODX-D file is analyzed, data under each directory in the ODX-D file are read, communication data related to freezing frame data of each ECU system of the vehicle to be diagnosed are screened out, and fault codes and data streams corresponding to the freezing frame data of each ECU are analyzed. The screened communication data related to the frozen frame data of each ECU system of the vehicle to be diagnosed comprises parameters related to a communication protocol between the vehicle to be diagnosed and the diagnostic equipment.
And S202, respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects for each ECU system in the ECU systems.
In this embodiment, since the number of the fault codes and the data streams included in each ECU system is not fixed, the fault codes and the data streams corresponding to the respective freeze frame data of each ECU system in each ECU system need to be stored in different container objects, specifically, a container (container) is a class template for storing data. Data structures such as variable-length arrays, linked lists, balanced binary trees, etc. are all implemented as containers in the STL. When a developer uses a container, i.e., instantiates a container class template as a container class, it will indicate what type of element is stored in the container. The container can store variables of basic types and objects. Since the vector container (vector container) is a sequential container encapsulating a dynamic size (variable length) array, and is ordered according to a strict linear order, any element in the sequence can be quickly and directly accessed through the position of the element in the sequence. It can store various types of objects, as any other type of container. Therefore, optionally, in this embodiment, the container object is a vector container; for each of the ECU systems, respectively storing the fault code and the data stream corresponding to the respective freeze frame data into different container objects, including: and respectively storing fault codes and data streams corresponding to respective freezing frame data into different vector containers for each ECU system in each ECU system.
Further, in an alternative implementation manner, the fault code corresponding to the respective freeze frame data of each ECU system in the respective ECU systems may be stored in the first vector container, and the data stream corresponding to the respective freeze frame data of each ECU system may be stored in the second vector container.
S203, calling a data export interface to export the fault code and the data stream corresponding to the respective frozen frame data of each ECU system from the different container objects respectively.
In an optional implementation manner, in order to ensure that a tester is convenient to debug and fault location is convenient, it is determined that the data export interface includes a first data export interface and a second data export interface, where the first data export interface is used to process operations other than data of a single ECU, for example, uniformly operate all ECU data according to an export path, which may also be referred to as a total data export interface; the second data export interface is used for exporting the data of the single ECU and can also be called as a single data export interface;
illustratively, the invoking data exporting interfaces respectively export fault codes and data streams corresponding to respective frozen frame data from the different container objects, including:
and calling the first data export interface, calling the second data export interface in sequence, and exporting the fault codes and the data streams corresponding to the frozen data of the ECU according to a preset path.
In this way, if a problem occurs during the export process, it is convenient to locate whether the first data export interface is faulty or the second data export interface is faulty, for example, if a fault occurs on the export path, the first data export interface is directly located, and if a fault occurs during the export of each ECU data, the second data export interface is located.
It can be understood that the fault codes and data stream derivation corresponding to the respective frozen frame data of each ECU can also be derived through the total data interface, that is, the above first data derivation interface, and only when the fault codes and data stream derivation is uniformly derived through the total data interface, the fault debugging and positioning are inconvenient.
And S204, respectively and correlatively storing the communication data correlated with the respective frozen frame data of each ECU system and the derived fault codes and data streams corresponding to the respective frozen frame data in different preset files.
Illustratively, the preset file is an EXCEL file; in this embodiment, the communication data associated with the freeze frame data of each ECU system and the fault code and data stream associated with the freeze frame data of each ECU system are stored in different EXCEL files in association with each other, so that the worker can quickly and accurately find the required freeze frame data. The acquisition efficiency of the frozen frame data can be effectively improved.
Illustratively, the associating the communication data associated with the respective frozen frame data of each ECU system and the derived fault codes and data streams corresponding to the respective frozen frame data are respectively stored in different preset files in an associated manner, including:
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different EXCEL files in an associated manner.
As shown in fig. 3, it is a flowchart of a specific implementation of S204 in fig. 2. As shown in fig. 3, S204 includes S2041 to S2043. The details are as follows:
s2041, respectively writing the communication data related to the respective frozen frame data of each ECU system into a preset first Sheet label page of the EXCEL file corresponding to each ECU system.
S2042, writing fault codes corresponding to the respective frozen frame data of each ECU system into a third Sheet label page of the EX CEL file corresponding to each ECU system.
S2043, writing the data stream corresponding to the respective frozen frame data of each ECU system into the second sheet label page of the EXCEL file corresponding to each ECU system.
In this embodiment, the method includes determining the EXCEL files corresponding to the ECU systems, and establishing different sheet label pages in the EXCEL files corresponding to the ECU systems to store the freeze frame data, the fault code and the data stream corresponding to the ECU systems, so that a worker can directly find the required freeze frame data of any one ECU through the EXCEL files corresponding to the ECU systems.
Based on the above embodiments, after the vehicle diagnostic data is analyzed by using the method for acquiring the frozen frame data provided by the present application, communication data associated with the frozen frame data of each ECU system of the vehicle to be diagnosed, and fault codes and data streams corresponding to the frozen frame data of each ECU system can be respectively stored in different preset files in an associated manner, so that the efficiency of acquiring the frozen frame data is effectively improved, and errors are not easily caused.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Based on the method for acquiring the freeze frame data provided by the embodiment, the embodiment of the invention further provides an embodiment of a device for implementing the embodiment of the method.
Referring to fig. 4, fig. 4 is a schematic diagram of a device for acquiring freeze frame data according to an embodiment of the present application. Modules or units are included for performing the steps in the corresponding embodiment of fig. 2. Please refer to the related description of the embodiment corresponding to fig. 2. For convenience of explanation, only the portions related to the present embodiment are shown. Referring to fig. 4, the freeze frame data acquisition apparatus 400 includes:
the analysis module is used for analyzing the vehicle diagnosis data to obtain communication data related to the freezing frame data of each electronic control unit ECU system of the vehicle to be diagnosed, and fault codes and data streams corresponding to the freezing frame data of each ECU system;
the storage module is used for respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects for each ECU system in each ECU system;
the export module is used for calling a data export interface to respectively export the fault code and the data stream corresponding to the respective frozen frame data of each ECU system from the different container objects;
and the writing module is used for respectively and correlatively storing the communication data related to the respective frozen frame data of each ECU system and the derived fault codes and data streams corresponding to the respective frozen frame data in different preset files.
In an optional implementation, the container object is a vector container;
the storage module is specifically configured to:
and for each ECU system in the ECU systems, storing the fault code corresponding to the respective freeze frame data into a first vector container, and storing the data stream corresponding to the respective freeze frame data of each ECU system into a second vector container.
In an alternative implementation, the data export interface comprises a first data export interface and a second data export interface;
the export module is specifically configured to:
and calling the first data export interface, calling the second data export interface in sequence, and exporting the fault codes and the data streams corresponding to the frozen data of the ECU according to a preset path.
In an alternative implementation, the data export interface comprises a first data export interface;
the export module is specifically configured to:
and calling the first data export interface, and exporting the fault codes and the data streams corresponding to the respective frozen frame data according to a preset path.
In an optional implementation manner, the preset file is an EXCEL file;
the write module is specifically configured to:
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different EXCEL files in an associated manner.
In an optional implementation manner, the writing module includes:
the first writing unit is used for respectively writing the communication data related to the respective frozen frame data of each ECU system into a preset first Sheet label page of the EXCEL file corresponding to each ECU system;
a second writing unit, configured to write the fault code corresponding to the respective frozen frame data of each ECU system into a third Sheet tab of the EXCEL file corresponding to each ECU system;
and a third writing unit, configured to write the data stream corresponding to the respective freeze frame data of each ECU system into a second sheet tab of the EXCEL file corresponding to each ECU system.
In an alternative implementation, the freeze frame data includes an ECU name, ECU filter identification information, and ECU response identification information.
It should be noted that, because the contents of information interaction, execution process, and the like between the modules or units are based on the same concept as that of the method embodiment of the present application, specific functions and technical effects thereof may be specifically referred to a part of the method embodiment, and are not described herein again.
Fig. 5 is a schematic diagram of an electronic device provided in an embodiment of the present application. As shown in fig. 5, the electronic apparatus 5 of this embodiment includes: a processor 500, a memory 501 and a computer program 502, such as a freeze frame acquisition program, stored in the memory 501 and executable on the processor 500. The processor 500 executes the computer program 502 to implement the steps in the above-mentioned embodiments of the freeze frame acquisition method, such as the steps 201 and 204 shown in fig. 2. Alternatively, the processor 500 implements the functions of the modules/units in the above device embodiments, for example, the functions of the units 401 to 404 shown in fig. 4, when executing the computer program 502.
Illustratively, the computer program 502 may be partitioned into one or more modules/units that are stored in the memory 501 and executed by the processor 500 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 502 in the electronic device 5. For example, the computer program 502 may be divided into an analysis module, a storage module, an export module, and a write module, and specific functions of each module are described in the embodiment corresponding to fig. 4, which is not described herein again.
The electronic device may include, but is not limited to, a processor 500, a memory 501. It will be appreciated by those skilled in the art that fig. 5 is merely an example of the electronic device 5 and does not constitute a limitation of the electronic device 5 and may include more or less components than those shown, or some components may be combined, or different components, for example the video processing device may also include an input output device, a network access device, a bus, etc.
The Processor 500 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 501 may be an internal storage unit of the electronic device 5, such as a hard disk or a memory of the electronic device 5. The memory 501 may also be an external storage device of the electronic device 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 5. Further, the memory 501 may also include both an internal storage unit and an external storage device of the electronic device 5. The memory 501 is used for storing the computer program and other programs and data required by the electronic device. The memory 501 may also be used to temporarily store data that has been output or is to be output.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the freeze frame acquisition method can be implemented.
The embodiment of the present application provides a computer program product, which when running on an electronic device, enables the electronic device to implement the above freeze frame acquisition method when executed.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A method for acquiring freeze frame data, comprising:
analyzing vehicle diagnosis data to obtain communication data associated with freezing frame data of each ECU system of the vehicle to be diagnosed, and fault codes and data streams corresponding to the freezing frame data of each ECU system;
for each ECU system in each ECU system, respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects;
calling a data export interface to respectively export the fault codes and the data streams corresponding to the respective frozen frame data of each ECU system from the different container objects;
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different preset files in an associated manner.
2. The method of claim 1, wherein the container object is a vector container;
for each of the ECU systems, respectively storing the fault code and the data stream corresponding to the respective freeze frame data into different container objects, including:
and for each ECU system in the ECU systems, storing the fault code corresponding to the respective frozen frame data into a first vector container, and storing the data stream corresponding to the respective frozen frame data into a second vector container.
3. The method of claim 1, wherein the data export interfaces include a second data export interface for each respective ECU system;
the calling data export interface respectively exports fault codes and data streams corresponding to respective frozen frame data of each ECU system from the different container objects, and the method comprises the following steps:
and respectively calling the corresponding second data export interfaces for each ECU system, and exporting the fault codes and the data streams corresponding to the respective frozen frame data according to a preset path.
4. The method of claim 1, wherein the data export interface comprises a first data export interface;
the calling data export interface respectively exports fault codes and data streams corresponding to respective frozen frame data of each ECU system from the different container objects, and the method comprises the following steps:
and calling the first data export interface, and exporting fault codes and data streams corresponding to the respective freezing frame data of all the ECU systems according to a preset path.
5. The method according to any one of claims 1 to 4, wherein the preset file is an EXCEL file;
respectively and correlatively storing communication data correlated with the respective frozen frame data of each ECU system and fault codes and data streams corresponding to the respective frozen frame data which are derived into different preset files, wherein the method comprises the following steps:
and respectively storing the communication data associated with the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different EXCEL files in an associated manner.
6. The method of claim 5, wherein the associating the communication data associated with the respective freeze frame data of each of the ECU systems and the derived fault codes and data streams corresponding to the respective freeze frame data in different EXCEL files comprises:
respectively writing communication data related to the respective freezing frame data of each ECU system into a preset first Sheet label page of the EXCEL file corresponding to each ECU system;
respectively writing fault codes corresponding to the respective freezing frame data of each ECU system into a third Sheet label page of the EXCEL file corresponding to each ECU system;
and respectively writing the data stream corresponding to the respective freezing frame data of each ECU system into a second sheet label page of the EXCEL file corresponding to each ECU system.
7. The method of claim 5, wherein the freeze frame data includes an ECU name, ECU filter identification information, and ECU response identification information.
8. A frozen frame data acquisition apparatus, comprising:
the analysis module is used for analyzing the vehicle diagnosis data to obtain the freezing frame data of each ECU system of the vehicle to be diagnosed, and the fault codes and the data streams corresponding to the freezing frame data of each ECU system;
the storage module is used for respectively storing fault codes and data streams corresponding to respective freezing frame data into different container objects for each ECU system in each ECU system;
the export module is used for calling a data export interface to respectively export the fault code and the data stream corresponding to the respective frozen frame data of each ECU system from the different container objects;
and the writing module is used for respectively and correlatively storing the communication data related to the respective freezing frame data of each ECU system and the derived fault codes and data streams corresponding to the respective freezing frame data in different preset files.
9. An electronic device, comprising:
a memory for storing a freeze frame data acquisition program;
a processor for implementing the freeze frame data acquisition method according to any one of claims 1 to 7 when executing the freeze frame data acquisition program.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the freeze frame data acquisition method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010751067.4A CN111949005B (en) | 2020-07-30 | 2020-07-30 | Method, device and equipment for acquiring frozen frame data and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010751067.4A CN111949005B (en) | 2020-07-30 | 2020-07-30 | Method, device and equipment for acquiring frozen frame data and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111949005A CN111949005A (en) | 2020-11-17 |
| CN111949005B true CN111949005B (en) | 2021-10-22 |
Family
ID=73338627
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010751067.4A Active CN111949005B (en) | 2020-07-30 | 2020-07-30 | Method, device and equipment for acquiring frozen frame data and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111949005B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09126954A (en) * | 1995-10-27 | 1997-05-16 | Nissan Motor Co Ltd | Electronic control device for automobile |
| JP2004232498A (en) * | 2003-01-28 | 2004-08-19 | Denso Corp | Creation method for time series freeze frame data and vehicle controlling device |
| CN102323814A (en) * | 2011-06-07 | 2012-01-18 | 广州汽车集团股份有限公司 | Freeze frame defining and reading method and device |
| CN103294796A (en) * | 2013-05-24 | 2013-09-11 | 上海申腾信息技术有限公司 | XML (extensive markup language) parsing method and implementation method of custom XML structural forms in medical records |
| CN103902746A (en) * | 2014-03-11 | 2014-07-02 | 深圳市元征科技股份有限公司 | Fault code, data stream and freeze frame data storage and playback method |
| CN109213132A (en) * | 2018-11-26 | 2019-01-15 | 重庆长安汽车股份有限公司 | A kind of method, device and equipment that UDS diagnostic interface software generates |
| CN110647137A (en) * | 2019-09-30 | 2020-01-03 | 深圳市元征科技股份有限公司 | Method, device, equipment and medium for acquiring frozen frame data |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8909416B2 (en) * | 2008-04-14 | 2014-12-09 | Innova Electronics, Inc. | Handheld scan tool with fixed solution capability |
-
2020
- 2020-07-30 CN CN202010751067.4A patent/CN111949005B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09126954A (en) * | 1995-10-27 | 1997-05-16 | Nissan Motor Co Ltd | Electronic control device for automobile |
| JP2004232498A (en) * | 2003-01-28 | 2004-08-19 | Denso Corp | Creation method for time series freeze frame data and vehicle controlling device |
| CN102323814A (en) * | 2011-06-07 | 2012-01-18 | 广州汽车集团股份有限公司 | Freeze frame defining and reading method and device |
| CN103294796A (en) * | 2013-05-24 | 2013-09-11 | 上海申腾信息技术有限公司 | XML (extensive markup language) parsing method and implementation method of custom XML structural forms in medical records |
| CN103902746A (en) * | 2014-03-11 | 2014-07-02 | 深圳市元征科技股份有限公司 | Fault code, data stream and freeze frame data storage and playback method |
| CN109213132A (en) * | 2018-11-26 | 2019-01-15 | 重庆长安汽车股份有限公司 | A kind of method, device and equipment that UDS diagnostic interface software generates |
| CN110647137A (en) * | 2019-09-30 | 2020-01-03 | 深圳市元征科技股份有限公司 | Method, device, equipment and medium for acquiring frozen frame data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111949005A (en) | 2020-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11158143B2 (en) | Vehicle diagnostic method and device, and computer readable storage medium | |
| US9256517B1 (en) | Display of aggregated stack traces in a source code viewer | |
| CN110955714A (en) | Method and device for converting unstructured text into structured text | |
| US11520620B2 (en) | Electronic device and non-transitory storage medium implementing test path coordination method | |
| CN111026080A (en) | Hardware-in-loop test method and device for controller | |
| CN112256253A (en) | Code generation method and device, electronic equipment and computer readable storage medium | |
| CN112948233A (en) | Interface testing method, device, terminal equipment and medium | |
| CN114895935A (en) | Method and device for flashing vehicle ECU, electronic equipment and storage medium | |
| CN111949005B (en) | Method, device and equipment for acquiring frozen frame data and storage medium | |
| CN114691403A (en) | Server fault diagnosis method and device, electronic equipment and storage medium | |
| CN110750440A (en) | Data testing method and terminal equipment | |
| US8966323B2 (en) | Monitoring multiple data transfers | |
| CN113835729A (en) | Upgrading method and device, terminal equipment and computer readable storage medium | |
| CN111930097B (en) | Vehicle diagnostic data analysis method, device, equipment and storage medium | |
| CN109189671B (en) | Layer-by-layer approximation type variable positioning method and system and terminal equipment | |
| CN109324838B (en) | Execution method and execution device of single chip microcomputer program and terminal | |
| CN112181538B (en) | Diagnostic flow execution method, device, equipment and storage medium | |
| CN114329090A (en) | Path reference searching method and device, electronic equipment and storage medium | |
| CN114416057A (en) | Project code packaging method and device, terminal equipment and storage medium | |
| CN113467815A (en) | Application repair method and device for hot update, terminal equipment and storage medium | |
| CN112445797B (en) | Vehicle diagnosis data reference method, device, terminal equipment and storage medium | |
| KR20200058718A (en) | System and method for automotive data conversion for data testing based on ttcn-3, recording medium for performing the method | |
| CN114185803A (en) | Page script debugging method and device, computer readable storage medium and server | |
| CN116594960B (en) | Descriptive file format conversion method, descriptive file format conversion device, computer equipment and storage medium | |
| CN112445491A (en) | File sequence processing method and device, terminal equipment and storage 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 |