CN115079673B - Fault uploading method, device, equipment and storage medium - Google Patents
Fault uploading method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115079673B CN115079673B CN202210791278.XA CN202210791278A CN115079673B CN 115079673 B CN115079673 B CN 115079673B CN 202210791278 A CN202210791278 A CN 202210791278A CN 115079673 B CN115079673 B CN 115079673B
- Authority
- CN
- China
- Prior art keywords
- fault
- data
- data frames
- information
- frame
- 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
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000012545 processing Methods 0.000 claims description 22
- 230000005540 biological transmission Effects 0.000 claims description 15
- 238000013507 mapping Methods 0.000 claims description 9
- 230000006870 function Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 8
- 125000004122 cyclic group Chemical group 0.000 description 7
- 230000008569 process Effects 0.000 description 6
- 239000000284 extract Substances 0.000 description 4
- 230000008859 change Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000008034 disappearance Effects 0.000 description 1
- 230000008030 elimination Effects 0.000 description 1
- 238000003379 elimination reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000446 fuel Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000004092 self-diagnosis Methods 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 230000001502 supplementing effect Effects 0.000 description 1
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)
- Maintenance And Management Of Digital Transmission (AREA)
Abstract
The application relates to a fault uploading method, device, equipment and storage medium. The fault uploading method comprises the following steps: reading fault information of each component in the electronic control unit; generating a group of data frames conforming to a preset frame format according to the fault information; and uploading a group of data frames in sequence, and reading fault information of each component in the electronic control unit again after the uploading is completed so as to generate and upload a next group of data frames. The fault uploading method provided by the application can solve the problems that the fault code is not uploaded timely and is easy to miss, and the like.
Description
Technical Field
The present application relates to the field of fault detection technologies, and in particular, to a fault uploading method, device, equipment, and storage medium.
Background
In order to improve the level of electronics and automation of automobiles, electronic control units (Electronic Control Unit, ECU) are often used to implement various functions of various automobiles. The electronic control units CAN be connected through a bus controller local area network (Controller Area Network, CAN) bus, so that the electronic control units of the whole vehicle form a network system, and information transmission among the electronic control units is realized.
When the electronic control unit fails, the fault analysis equipment CAN acquire the fault code of the electronic control unit through the CAN bus and locate the fault on the electronic control unit according to the fault code. However, as more and more electronic control units are provided on the automobile, the functions realized by the electronic control units are more and more complex, and fault codes generated by the electronic control units are more and more various, so that the faults are supported and positioned rapidly. Once the fault codes are increased, the problems of untimely uploading, omission and the like of the fault codes are easy to occur.
Disclosure of Invention
Based on the problems, the application provides a fault uploading method, a device, equipment and a storage medium, which can improve the problems of untimely uploading of fault codes, easy omission and the like.
In a first aspect, the present application provides a fault uploading method, where the fault uploading method includes: reading fault information of each component in the electronic control unit; generating a group of data frames conforming to a preset frame format according to the fault information; and uploading a group of data frames in sequence, and reading fault information of each component in the electronic control unit again after the uploading is completed so as to generate and upload a next group of data frames.
With reference to the first aspect, in a first implementation manner of the first aspect, the step of generating a set of data frames according to the preset frame format according to the fault information includes: extracting fault codes and provider identifiers in fault information, wherein the fault information comprises the fault codes and source information, and the source information comprises equipment identifiers and provider identifiers; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the step of determining, according to the fault table, a fault number corresponding to the fault code includes: determining the order of the fault codes in a fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
With reference to the first aspect, in a third implementation manner of the first aspect, after the step of generating a set of data frames according to the preset frame format according to the fault information, the method further includes: generating frame information according to a group of data frames, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to a group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the step of generating frame information according to a set of data frames includes: determining a frame sequence number of each data frame according to the number of a group of data frames; determining a total number of failures based on a number of data encodings in a set of data frames; the frame number and the total number of failures are used as frame information.
With reference to the first aspect, in a fifth implementation manner of the first aspect, the preset frame format includes a first data bit for describing fault information; the first data bits include a first one-data bit for representing a device identification, a first two-data bit for representing a vendor identification, and a first three-data bit for representing a failure number.
With reference to the third implementation manner of the first aspect, in a sixth implementation manner of the first aspect, the preset frame format includes a second data bit for describing frame information; the second data bits include a second data bit for indicating a total number of failures and a second data bit for indicating a frame number.
In a second aspect, the present application provides a fault uploading device, the device comprising: the reading unit is used for reading fault information of each component in the electronic control unit; the processing unit is used for generating a group of data frames conforming to a preset frame format according to the fault information; and the uploading unit is used for sequentially uploading a group of data frames and reading the fault information of each component in the electronic control unit again after the uploading is finished so as to generate and upload the next group of data frames.
With reference to the second aspect, in a first possible implementation manner of the second aspect, the processing unit is specifically configured to: extracting fault codes and provider identifiers in fault information, wherein the fault information comprises the fault codes and source information, and the source information comprises equipment identifiers and provider identifiers; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the processing unit is specifically configured to: determining the order of the fault codes in a fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
With reference to the second aspect, in a third possible implementation manner of the second aspect, the processing unit is further configured to: generating frame information according to a group of data frames, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to a group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
With reference to the third possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the processing unit is specifically configured to: determining a frame sequence number of each data frame according to the number of a group of data frames; determining a total number of failures based on a number of data encodings in a set of data frames; the frame number and the total number of failures are used as frame information.
With reference to the second aspect, in a fifth possible implementation manner of the second aspect, the preset frame format includes a first data bit for describing fault information; the first data bits include a first one-data bit for representing a device identification, a first two-data bit for representing a vendor identification, and a first three-data bit for representing a failure number.
With reference to the third implementation manner of the second aspect, in a sixth implementation manner of the second aspect, the preset frame format includes a second data bit for describing frame information; the second data bits include a second data bit for indicating a total number of failures and a second data bit for indicating a frame number.
In a third aspect, the present application also provides a fault uploading device, where the fault uploading device includes a processor and a memory, and the processor and the memory are connected through a bus; a processor for executing a plurality of instructions; a memory for storing a plurality of instructions adapted to be loaded by a processor and to perform the fault upload method of the first aspect or any implementation of the first aspect.
In a fourth aspect, the present application also provides a computer readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor and to perform the fault upload method as in the first aspect or any of the embodiments of the first aspect.
In summary, the fault uploading device generates and uploads a group of data frames conforming to a preset frame format according to the read fault information of the electronic control unit, and then reads the fault information of each component in the electronic control unit again to generate and upload a next group of data frames. The fault uploading device may be an electronic control unit, or may be another device connected to the electronic control unit. Therefore, the fault uploading method belongs to an active uploading mode, so that faults can be uploaded timely even if the electronic control unit is newly added equipment or the electronic control unit is newly added with functions. In addition, because the application packages the fault information in a group of data frames, more faults can be uploaded, and the fault uploading process is repeatedly and circularly carried out, even after the uploading of a group of data frames is completed, the fault information is acquired again and uploaded, so that the application realizes the endless uploading of the faults. In general, the fault uploading device improves the problems that the uploading of the fault codes is not timely and is easy to miss and the like in a fault uploading mode through active circulation.
Drawings
FIG. 1 is an application scenario diagram of a failure upload method in one embodiment;
FIG. 2 is a schematic diagram of a default frame format in one embodiment;
FIG. 3 is a schematic diagram of a set of data frames in one embodiment;
FIG. 4 is a flow diagram of a fault upload method in one embodiment;
FIG. 5 is a flow chart of a fault uploading method in another embodiment;
FIG. 6 is a schematic block diagram of a fault uploading device provided by the present application;
Fig. 7 is a structural block diagram of a fault uploading device provided by the present application.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
Since the embodiments of the present application relate to a large number of terms, for convenience of understanding, related terms and concepts to which the embodiments of the present application may relate will be described below.
1. Electronic control unit (Electronic Control Unit, ECU)
The electronic control unit is also called as "driving computer", "vehicle-mounted computer" and is a microcomputer controller specially used for automobile. In terms of use, the system is a microcomputer controller special for automobiles. The electronic control unit is used for monitoring various input data (such as braking, gear shifting and the like) and various running states (acceleration, slipping, oil consumption and the like) of the automobile at any time, calculating information sent by various sensors according to a pre-designed program, sending various parameters to various related executing mechanisms after processing, and executing various preset control functions. The method collects signals of the sensors, performs operation, converts the operation result into control signals, and controls the work of a controlled object.
2. Fault code
The fault code is fully called an On-board automatic diagnostic system (On-Board Diagnostics, OBD) fault code, which is a character string used to indicate a fault condition. Taking the fault code used on the automobile as an example, the fault code adopted on the current automobile is often referred to as the fault code in the second generation (namely OBD-II) of the OBD system. The fault code in OBD-II may consist of 5 digits and/or letters, such as P0123 indicating that the A-circuit input voltage to the throttle position sensor is too high.
Specifically, the first digit of the fault code in OBD-II is a letter to indicate the system that has failed, e.g., P indicates a powertrain system, B indicates a body system, C indicates a chassis system, U indicates an undefined or network failure of the vehicle; the second bit is a number indicating who the body making the code is, 0 indicating society of automotive Engineers (Society of Automotive Engineers, SAE), 1 indicating that the fault code is a vendor-customized fault code; the third bit is a number to indicate a malfunctioning subsystem, e.g., 0 indicates a full system, 1 and 2 indicates a fuel supply system, 3 indicates an ignition system, etc.; the fourth and fifth digits may be numbers and/or letters to represent the vendor original code, i.e., the vendor custom code.
The electronic control unit has a fault self-diagnosis function, and communicates with each component in the electronic control unit when the power is on, so as to read the fault code in each component. The maintenance personnel CAN acquire the fault code through the CAN bus, and carry out corresponding maintenance on the fault according to the fault corresponding to the fault code.
It should be further noted that the drawings provided in the present embodiment are only for illustrating the basic concept of the present invention by way of illustration, and only the components related to the present invention are shown in the drawings, not according to the number, shape and size of the components in actual implementation, and the form, number and proportion of each component in actual implementation may be arbitrarily changed, and the layout of the components may be more complex. The structures, proportions, sizes, etc. shown in the drawings attached hereto are for illustration purposes only and are not intended to limit the scope of the invention, which is defined by the claims, but rather by the claims. Meanwhile, references in the specification to directions or positional relationships such as "upper", "lower", "left", "right", "middle", "longitudinal", "transverse", "horizontal", "inner", "outer", "radial", "circumferential", etc., are based on the directions or positional relationships shown in the drawings, are also for convenience of description only, and do not indicate or imply that the apparatus or elements to be referred to must have a specific orientation, be constructed and operated in a specific orientation, and change or adjustment of the relative relationship thereof without substantial change of technical content, but are also regarded as the scope of the invention that can be implemented. And therefore should not be construed as limiting the invention. Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
It should be further noted that the fault uploading device and the fault uploading apparatus to which the present application relates next may include, but are not limited to, an electronic control unit (Electronic Control Unit, ECU), a central processing unit (central processing unit, CPU), a general purpose processor, a coprocessor, a Digital Signal Processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The fault uploading device and the fault uploading equipment can realize the described method of the application, for example, a group of data frames which conform to a preset frame format can be generated according to the fault information, and the application is not repeated.
At present, when an electronic control unit fails, the failure analysis equipment CAN acquire a failure code of the electronic control unit through a CAN bus and position the failure occurring on the electronic control unit according to the failure code. However, as more and more electronic control units are provided on the automobile, the functions realized by the electronic control units are more and more complex, and fault codes generated by the electronic control units are more and more various, so that the faults are supported and positioned rapidly. Once the fault codes are increased, the problems of untimely uploading, omission and the like of the fault codes are easy to occur.
In this regard, the application provides a fault uploading method, which solves the problems of untimely uploading of fault codes, easy omission and the like by actively circulating the uploading of faults. Specifically, the fault uploading device or the fault uploading equipment firstly obtains fault information of each component in the electronic control unit, and generates a group of data frames which accord with a preset frame format according to the fault information; and uploading a group of data frames in sequence, and reading fault information of each component in the electronic control unit again after the uploading is completed so as to generate and upload a next group of data frames.
In order to better understand the fault uploading method provided by the present application, the following detailed description will be given with reference to an application scenario diagram of the fault uploading method in fig. 1, and the fault uploading device is taken as an execution body.
As shown in fig. 1, in an automobile, there are generally a plurality of electronic control units, and each of the electronic control units may be connected to and in data communication with other devices, such as a fault analysis device, of a non-electronic control unit through a data transmission bus (CAN bus), or may be connected to and in data communication with other devices of the non-electronic control unit through the data transmission bus. The fault uploading method provided by the application can realize the uploading of the fault of any one of a plurality of electronic control units in the automobile, and the fault uploading device for executing the fault uploading method can be the electronic control unit or other devices connected with the electronic control unit. Preferably, the fault uploading device is the electronic control unit itself which needs to upload faults, namely the electronic control unit uploads the faults by adopting the fault uploading method of the application. It should be noted that, the execution body of the fault uploading method of the present application may be a fault uploading device or a fault uploading apparatus, which is not limited in this aspect of the present application.
In general, an automobile has a plurality of electronic control units, each of which has a plurality of components, each of which implements a different function, and at least one fault code is associated with each function. It can be seen that with the improvement of the intelligence of the automobile, the functions in the automobile are more and more abundant, and correspondingly, the types of fault codes are more and more abundant. In this regard, the fault uploading device first obtains fault information in the electronic control unit, where the fault information is used to indicate a fault occurring in each component in the electronic control unit, and then generates a set of data frames according to the fault information, where the set of data frames includes at least one data frame, where each data frame indicates at least one fault of the electronic control unit, where the at least one fault may be from the same component or from a different component, and the application is not limited to this.
And uploading the generated group of data frames through the CAN bus in sequence, so that the receiving end CAN acquire faults of all components in the electronic control unit by analyzing the group of data frames. After the uploading of the group of data frames is finished, the electronic control unit reads the fault information of each component again to generate and upload the next group of data frames again according to the fault information. It should be noted that, a set of data frames generated in the previous time may or may not coincide with data frames generated in the next time. The reason for the inconsistency is that: the old fault resulting from the previous reading has been eliminated at the time of the next reading, or the next reading results in a new fault that did not occur at the time of the previous reading. More specifically, the elimination of the old fault and the new fault may be due to the fact that the fault of the car is eliminated or newly increased on the one hand, and on the other hand, may be caused by an occasional fault, such as loosening of the connector lug of the sensor, etc., which may disappear when it occurs.
By way of example, the preset frame format may be a frame format as shown in fig. 2, the preset frame format including 11-bit data bits for representing a device identification, 8-bit data bits for representing a total number of failures, 6-bit data bits for representing a frame number, 3-bit data bits for representing a vendor identification, and 40-bit data bits for representing a failure number. Wherein every 10 bits of the 40 bits of data representing the fault number are used to indicate a fault code. Next, the present application will be described in detail with respect to a process of generating a set of data frames conforming to the preset frame format:
Firstly, fault uploading equipment extracts fault codes and source information in fault information, wherein corresponding relations exist between the fault codes and the source information, each fault code corresponds to one source information, and the source information comprises equipment identification and provider identification. And then the fault uploading equipment converts the fault code into a fault number, fills the source information and the converted fault number into corresponding data bits under a preset frame format to obtain a group of data frames, wherein each data frame is filled with at least 1 and at least 4 fault numbers, and each fault number in the same data frame belongs to the same provider. When the fault code is converted into the fault number, the fault uploading device firstly obtains a fault table corresponding to the provider identification according to the provider identification corresponding to the fault code. The fault table is used for indicating the mapping relation between the fault code and the fault number, so that the fault uploading device can determine the fault number corresponding to the fault code according to the fault table, and combine the fault number and the source information to obtain a group of data frames conforming to a preset frame format. It should be noted that, the fault number corresponding to the fault code may be determined according to the order of the fault code in the fault table, that is, the ranking of the fault code in the fault table is converted from decimal into two-level system, so as to obtain the fault number. For example, assuming that the fault information includes the fault code P0123, the vendor identifier 001 and the device identifier 0x999 of the component a, the fault uploading device first obtains the fault table corresponding to the vendor identifier 001, finds the order of the fault code P0123 in the fault table to be 20, and converts the order 20 into the fault number 0000010100, so that the fault number 0000010100, the vendor identifier 001 and the device identifier 0x999 are filled in the corresponding data bits under the data frame.
The failure uploading device then generates frame information from the aforementioned set of data frames and supplements the frame information to the set of data frames. Because the frame information is used for identifying a group of data frames, when the receiving end receives the group of data frames, the data transmission progress of the electronic control unit can be determined according to the frame information in the data frames. Specifically, the fault uploading device determines the frame number of each data frame according to the number of the group of data frames, determines the total number of faults according to the number of data codes in the group of data frames, uses the frame number and the total number of faults as frame information, and adds the frame information to the corresponding data bits under the group of data frames. For example, it is assumed that the aforementioned set of data frames has N data frames, and a total of the N data frames includes 4 (N-1) +m failure numbers, where the failure number in each data frame is greater than or equal to 1, N may be any positive integer greater than 1, and M may be any one of 1 to 4. Correspondingly, decimal 0-N is converted into N pieces of two-level system data, decimal 4 (N-1) +M is converted into binary data, and the binary data are respectively filled into corresponding data bits under the frame sequence number and the total number of faults in a data frame.
In summary, the fault uploading device in the embodiment of the application realizes the active cyclic uploading of faults by continuously and repeatedly executing the processes of acquiring the fault information, generating the data frame and uploading the data frame, thereby improving the problems of untimely uploading of fault codes, easy omission and the like.
Based on the above embodiments, the present application proposes a fault uploading method, and the present application will take an execution body as a fault uploading device as an example, and the fault uploading method will be described in more detail with reference to the flowchart of fig. 4. Specific:
401: and reading fault information of each component in the electronic control unit.
The fault uploading device reads fault information of each component in the electronic control unit, and the fault uploading device can be the electronic control unit or other devices connected with the electronic control unit. The fault information is used for indicating faults of all components in the electronic control unit, the fault information comprises fault codes and source information, a corresponding relation exists between the fault codes and the source information, each fault code corresponds to one source information, and the source of the fault code can be uniquely determined based on the source information. The source information includes a device identification for indicating the electronic control unit from which the fault code originated and a vendor identification for indicating the component from which the fault code originated. The fault code comprises a fault code in OBD-ii, the device identification comprises a string for uniquely indicating the electronic control unit, and the vendor identification comprises a string for uniquely representing a component in the electronic control unit.
It should be noted that the electronic control unit includes at least one component, each component may be from a different vendor, and the different vendors may have different rules for defining the fault code, for example, the fourth and fifth bits in the fault code in OBD-ii are customized by the vendor. Thus different fault codes may represent the same fault and the same fault may represent different faults. In order to upload faults without omission and enable a receiving end to rapidly analyze and locate the faults, the application reads the source information while reading the fault codes, and correlates the fault codes with the source information.
402: And generating a group of data frames conforming to a preset frame format according to the fault information.
The preset frame format is a standard format for uploading a data frame of a fault, and can comprise a first data bit for describing fault information; the first data bits include a first one-data bit for representing a device identification, a first two-data bit for representing a vendor identification, and a first three-data bit for representing a failure number. Preferably, the first one data bit is an 11 bit data bit, the first two data bits are 3 bit data bits, and the first three data bits are 40 bit data bits. Namely, the method comprises the following steps: the preset frame format comprises a first data bit for describing fault information; the first data bits include 11 bits for representing the device identification, 3 bits for representing the vendor identification, and 40 bits for representing the failure number, wherein every 10 bits of the 40 bits for representing the failure number are used to indicate one failure code.
In order to generate a group of data frames conforming to a preset frame format, the fault uploading device firstly extracts a fault code and source information in the fault information, converts the fault code into a fault number according to the corresponding relation between the fault code and the fault number, and fills a supplier identifier and a device identifier in the fault number and the source information into corresponding data bits in the preset frame format to obtain a group of data frames. At least one data code may be included in the data frame, each fault number indicating a fault occurring in the electronic control unit. After receiving the data frame uploaded by the fault uploading device, the receiving terminal can determine the electronic control unit with the fault according to the device identification in the data frame, and correspondingly analyze the fault number according to the supplier identification so as to realize accurate positioning of the fault.
It should be noted that the fault code is different from the fault number in that the fault code is a series of ASCII codes, for example, the fault code in OBD-ii, and the fault number is a series of two-level digits. The application converts the fault code into the fault number, on one hand, the application aims to increase the variety of the representable faults and on the other hand, the application aims to reduce the analysis difficulty.
It should be noted that, the present application fills the supplier identifier in the data frame, so that on one hand, the accuracy of fault analysis performed by the receiving end can be improved, on the other hand, the distinction degree of the fault code is increased, so as to further reduce the omission of the fault code, and on the other hand, the types of faults which can be accommodated by fault uploading are greatly increased under the condition of not excessively increasing the bus load.
To understand the third point described above, the present application will be described next. It is assumed that the data frame that is allowed to be uploaded on the CAN bus comprises L-bit data bits. The first scheme is adopted: each data bit represents one fault, and a total of at most L faults can be represented, so that the types of faults which can be uploaded by the method are too few. To increase the kinds of uploadable failures, a second scheme may also be employed: the method can transmit more fault types, but greatly increases bus load and increases difficulty of fault analysis of a receiving end. In contrast, the application not only increases the type of the fault which can be uploaded, but also does not excessively increase the bus load by filling the supplier identifier and the fault coding mode in the data frame.
For example, when the preset frame format of the present application is adopted, it is assumed that the vendor identification in the data frame includes L 1 bits, the failure number includes L 2 bits, and the number of failures that the data frame can represent isThe application can represent the number of faults far larger than L 1+L2 in the first scheme, and the second scheme can represent/>The resolution difficulty of the data frame is far smaller than that of the second scheme, because the receiving end respectively resolves the supplier identifier and the fault number when receiving the preset frame format, namely resolving L 1 bits of data and L 2 bits of data respectively, and the second scheme needs to resolve L 1+L2 bits of data together.
For more detailed example, assuming that the vendor identifier in the preset frame format of the present application is 3-bit data bits and the failure number is 10-bit data bits, a total of 2 10 -1 failures, that is, 1023 failures, can be represented.
403: And uploading the group of data frames in sequence, and reading the fault information of each component in the electronic control unit again after the uploading is completed to generate and upload the next group of data frames.
The fault uploading device uploads the generated group of data frames through the CAN bus in sequence, so that the device directly or indirectly connected to the CAN bus CAN receive the group of data frames and analyze the group of data. After the uploading is completed, the fault uploading device reads the fault information of each component in the electronic control unit again, and performs the next round of processing, namely, generates and sends a next group of data frames according to the fault information read again. After the next set of data frames is uploaded, the next set of data frames is generated and transmitted. Therefore, the fault uploading provided by the application is an active circulation mode, fault missing transmission is reduced by continuously uploading faults, and timeliness and efficiency of fault uploading are greatly improved. Because the receiving end can re-receive to acquire all data frames when uploading in the next round even if the receiving end fails to successfully receive all data frames in the previous round of fault uploading, the fault automatic retransmission is realized.
It should be noted that, the data frames obtained by the foregoing steps are different from the data frames of the next group generated in the present step. The two differ at least in: firstly, generating two groups of data frames with different time, wherein the former group is earlier than the latter group; second, the contents of the two sets of data frames may be different due to the addition or disappearance of the fault. It should be noted that, whether the previous and subsequent data frames are the same or different, the content of the data frames is updated in real time, so that timeliness and efficiency of fault uploading are further improved.
In one implementation, the preset frame format includes a second data bit for describing frame information; the second data bits include a second data bit for indicating a total number of failures and a second data bit for indicating a frame number.
Preferably, the second data bit is an 8-bit data bit, the first two data bits are 6-bit data bits, and the first three data bits are 40-bit data bits. Namely, the method comprises the following steps: the preset frame format includes a second data bit for describing frame information; the second data bits include 8-bit data bits for representing the total number of failures and 6-bit data bits for representing the frame number.
In one implementation manner, the step of generating a group of data frames according to the preset frame format according to the fault information includes: extracting fault codes and provider identifiers in fault information, wherein the fault information comprises the fault codes and source information, and the source information comprises equipment identifiers and provider identifiers; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
In one implementation manner, the step of determining the fault number corresponding to the fault code according to the fault table includes: determining the order of the fault codes in a fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
In one implementation manner, after the step of generating the set of data frames according to the preset frame format according to the fault information, the method further includes: generating frame information according to a group of data frames, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to a group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
In one implementation manner, the step of generating frame information according to a set of data frames includes: determining a frame sequence number of each data frame according to the number of a group of data frames; determining a total number of failures based on a number of data encodings in a set of data frames; the frame number and the total number of failures are used as frame information.
In summary, the fault uploading method of the application belongs to an active uploading mode, so that the fault can be uploaded in time even if the electronic control unit is newly added equipment or the electronic control unit is newly added with functions. In addition, because the application packages the fault information in a group of data frames, more faults can be uploaded, and the fault uploading process is repeatedly and circularly carried out, even after the uploading of a group of data frames is completed, the fault information is acquired again and uploaded, so that the application realizes the endless uploading of the faults. In general, the fault uploading device improves the problems that the uploading of the fault codes is not timely and is easy to miss and the like in a fault uploading mode through active circulation.
Based on the above embodiments, the present application will take the execution subject as the fault uploading device as an example, and the steps of forming the envelope chart will be described in more detail with reference to the flowchart of fig. 5. Specific:
501: and reading fault information of each component in the electronic control unit.
The fault information comprises a fault code and source information, wherein a corresponding relation exists between the fault code and the source information, and the source information comprises a device identifier and a provider identifier.
502: And generating a group of data frames conforming to a preset frame format according to the fault information.
Wherein the preset frame format comprises a first data bit for describing fault information and a second data bit for describing frame information; the first data bits include a first one-to-one data bit for representing a device identification, a first two-to-one data bit for representing a vendor identification, and a first three data bit for representing a failure number; the second data bits include a second data bit for indicating a total number of failures and a second data bit for indicating a frame number.
When a group of data frames conforming to a preset frame format are generated according to the fault information, the fault uploading equipment firstly extracts the fault code and the source information in the fault information, converts the fault code into the fault number according to the corresponding relation between the fault code and the fault number, and fills the fault number, the supplier identifier and the equipment identifier in the source information into the corresponding data bits under the preset frame format to obtain a group of data frames.
Preferably, the first data bit in the preset frame format is 11 bits, the first second data bit is 3 bits, the first third data bit is 40 bits, the second first data bit is 8 bits, the first second data bit is 6 bits, and the first third data bit is 40 bits. That is (as shown in fig. 2): the preset frame format comprises a first data bit for describing fault information and a second data bit for describing frame information; the first data bits include 11 bits for representing the device identification, 3 bits for representing the vendor identification, and 40 bits for representing the failure number, wherein every 10 bits of the 40 bits for representing the failure number are used to indicate one failure code; the second data bits include 8-bit data bits for representing the total number of failures and 6-bit data bits for representing the frame number.
503: Frame information is generated from the set of data frames.
The frame information is used for identifying a group of data frames, the frame information comprises a fault total number and a frame serial number, the fault total number refers to the total number of fault numbers in the generated group of data frames, namely the total number of faults generated by each component in the electronic control unit, and the frame serial number refers to the serial number of each data frame in the generated group of data frames. Specifically, the fault uploading device determines the frame number of each data frame according to the number of the group of data frames, determines the total number of faults according to the number of data codes in the group of data frames, and then uses the frame number and the total number of faults as frame information. For example, assuming that the number of the set of data frames is N, the total number of failures in the set of data frames is 4 (N-1) +m, the frame numbers of the set of data frames are 0 to N, respectively, and the total number of failures in the set of data frames is 4 (N-1) +m. N may be any positive integer greater than 1 and M may be any one of 1 to 4.
504: And supplementing the frame information into the group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
The fault uploading device fills the total number of faults and the frame number in the frame information into corresponding data bits under the group of data frames respectively. It should be noted that, before filling, the system of the frame information obtained in step 503 may also be converted, that is, the total number of faults in decimal and the frame number may be converted into binary values, respectively.
It should be noted that, since the frame numbers in the above-mentioned group of data frames are continuous, when the receiving end receives the group of data frames, it can determine whether the data frames are missed according to the frame numbers in the received data frames, and also can determine whether the fault codes are completely transmitted according to the total number of faults in the data frames, so as to determine whether the data frames are transmitted. Therefore, the application can assist the receiving end to determine the data transmission progress of the electronic control unit according to the frame information when receiving a group of data frames by filling the total number of faults and the fault codes in the data frames, namely, whether the data frames are missed or transmitted completely.
505: And uploading the group of data frames in sequence, and reading the fault information of each component in the electronic control unit again after the uploading is completed to generate and upload the next group of data frames.
The fault uploading device sequentially uploads the group of data frames according to the sequence from small to large of the frame sequence number of each data frame, reads fault information of each component in the electronic control unit again after uploading is completed to generate and upload the next group of data frames, and repeatedly executes the steps 501 to 505, so that the cyclic active uploading of faults is realized.
As can be seen from the foregoing description, the receiving end can determine whether there is a missed data frame condition according to the data frame sent by the failed uploading device, and can also know whether the uploading is finished, so that even in the case of missed data, the receiving end can select a strategy of discarding or receiving data, and receive complete data in the next failed uploading. It can be appreciated that the fault uploading method of the application improves the problem that the fault code uploading is easy to miss from another angle.
For a better explanation of the cyclic active upload process of the failure in the present application, the present application will be illustrated with reference to fig. 3. Specific: as shown in the first case, in the case that no fault occurs, the fault uploads the data frame that is empty in the fault cycle; as shown in the second case, under the condition that the total number of faults is not more than 4 and the fault number 3 is recovered to be normal in the cyclic uploading process, the fault uploading device fills the fault number 3 in the data frame uploaded in the previous time, and after the fault 3 is eliminated, the fault uploading device eliminates the fault number 3 in the data frame uploaded in the next time; as shown in a third case, when the total number of faults is not more than 4, and in the cyclic transmission process, the faults 3 are recovered to be normal, and the faults 5 are newly added; as shown in case four, in case the total number of failures exceeds 4, the failure uploading device generates a plurality of data frames according to the failure information.
In one implementation manner, to generate a set of data frames according to the fault information in step 502, the fault uploading device may extract a fault code and a provider identifier in the fault information, where the fault information includes a fault code and source information, and the source information includes a device identifier and a provider identifier; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
Wherein, each supplier identifier corresponds to a fault table, and the fault table contains the mapping relation between the fault code and the fault number. The fault uploading equipment firstly acquires a fault table corresponding to the provider identifier for acquiring a fault number corresponding to the fault code, and searches the corresponding fault number according to the fault table. After obtaining the fault number, the fault uploading device fills the fault number, the provider identifier and the device identifier in the fault information into corresponding data bits in a preset frame format, and it can also be understood that the fault number and the source information are combined, so that a group of data frames conforming to the preset frame format is obtained. It should be noted that the fault table may include at least one pair of fault numbers and fault numbers, where the fault numbers correspond to the fault numbers one by one.
In one implementation manner, in order to implement the step of determining the fault number corresponding to the fault code according to the fault table, the fault uploading device may determine an order of the fault code in the fault table, where the fault table includes at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
The fault codes in the fault table are arranged according to a linear sequence, so that the fault number corresponding to the fault code is determined according to the fault table, and the fault uploading device can determine according to the sequence of the fault code in the fault table, namely, the sequence of the fault code in the fault table is converted into two-level system data, namely, the fault number corresponding to the fault code.
In summary, the embodiment of the application realizes the cyclic active uploading of faults by filling the information such as the fault number, the supplier identifier, the equipment identifier, the frame number, the total number of faults and the like in the data frame, and further improves the problems of untimely uploading of the fault codes, easy omission and the like.
Referring to fig. 6, the implementation of the present invention further provides a fault uploading device. The embodiment of the invention can divide the functional units of the device according to the method example, for example, each functional unit can be divided corresponding to each function, and two or more functions can be integrated in one unit. The integrated units may be implemented in hardware or in software functional units. It should be noted that, in the embodiment of the present invention, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. As shown in fig. 6, the fault uploading device includes a reading unit 610, a processing unit 620, and an uploading unit 630, specifically:
A reading unit 610 for reading failure information of each component in the electronic control unit; a processing unit 620, configured to generate a group of data frames according to a preset frame format according to the fault information; and an uploading unit 630, configured to upload a group of data frames sequentially, and read the fault information of each component in the electronic control unit again after the uploading is completed, so as to generate and upload a next group of data frames.
In one implementation, the processing unit 620 is specifically configured to: extracting fault codes and provider identifiers in fault information, wherein the fault information comprises the fault codes and source information, and the source information comprises equipment identifiers and provider identifiers; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
In one implementation, the processing unit 620 is specifically configured to: determining the order of the fault codes in a fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
In one embodiment, the processing unit 620 is further configured to: generating frame information according to a group of data frames, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to a group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
In one implementation, the processing unit 620 is specifically configured to: determining a frame sequence number of each data frame according to the number of a group of data frames; determining a total number of failures based on a number of data encodings in a set of data frames; the frame number and the total number of failures are used as frame information.
In one embodiment, the preset frame format includes a first data bit for describing fault information; the first data bits include 11 bits for representing the device identification, 3 bits for representing the vendor identification, and 40 bits for representing the failure number, wherein every 10 bits of the 40 bits for representing the failure number are used to indicate one failure code.
In one embodiment, the preset frame format includes a second data bit for describing frame information; the second data bits include 8-bit data bits for representing the total number of failures and 6-bit data bits for representing the frame number.
In summary, the fault uploading device reads the fault information of each component in the electronic control unit through the reading unit 610, generates a group of data frames conforming to the preset frame format according to the fault information through the processing unit 620, sequentially uploads a group of data frames through the uploading unit 630, and reads the fault information of each component in the electronic control unit again after the uploading is completed to generate and upload the next group of data frames, so that the cyclic active uploading of faults is realized, and the problems that the uploading of fault codes is not timely and is easy to miss and the like are solved.
Referring to fig. 7, a schematic block diagram of a fault uploading device according to another embodiment of the present application is provided. The fault uploading device in this embodiment as shown in the figure may include: a processor 710 and a memory 720. The processor 710 and the memory 720 are connected by a bus 730. A processor 710 for executing a plurality of instructions; memory 720 for storing a plurality of instructions adapted to be loaded by processor 710 and to perform the method of fault upload as in the above-described embodiments.
The processor 710 may be an electronic control unit (Electronic Control Unit, ECU), a central processing unit (central processing unit, CPU), a general purpose processor, a co-processor, a digital signal processor (DIGITAL SIGNAL processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. The processor 710 may also be a combination that performs computing functions, such as including one or more microprocessors, a combination of a DSP and a microprocessor, and the like. In this embodiment, the processor 710 may use a single-chip microcomputer, and various control functions can be realized by programming the single-chip microcomputer, for example, in this embodiment, the functions of collecting, processing and demodulating fault information are realized, and the processor has the advantages of strong computing power and rapid processing. Specific:
The processor 710 is configured to perform a function of the reading unit 610 for reading fault information of each component in the electronic control unit; and is further configured to perform a function of the processing unit 620, and generate a set of data frames according to the preset frame format according to the fault information; and also performs the function of the uploading unit 630 to upload a set of data frames in sequence, and to read the failure information of each component in the electronic control unit again after the uploading is completed, so as to generate and upload the next set of data frames.
In one embodiment, the processor 710 is specifically configured to: extracting fault codes and provider identifiers in fault information, wherein the fault information comprises the fault codes and source information, and the source information comprises equipment identifiers and provider identifiers; obtaining a fault table corresponding to the supplier identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number; and determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
In one embodiment, the processor 710 is specifically configured to: determining the order of the fault codes in a fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear order; and determining the fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
In one embodiment, the processor 710 is further configured to: generating frame information according to a group of data frames, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to a group of data frames, so that the receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames.
In one embodiment, the processor 710 is specifically configured to: determining a frame sequence number of each data frame according to the number of a group of data frames; determining a total number of failures based on a number of data encodings in a set of data frames; the frame number and the total number of failures are used as frame information.
In one embodiment, the preset frame format includes a first data bit for describing fault information; the first data bits include 7 bits for representing the device identification, 3 bits for representing the vendor identification, and 40 bits for representing the failure number, wherein every 10 bits of the 40 bits for representing the failure number are used to indicate one failure code.
In one embodiment, the preset frame format includes a second data bit for describing frame information; the second data bits include 8-bit data bits for representing the total number of failures and 6-bit data bits for representing the frame number.
The application also provides a computer readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor and to perform the method of any of the preceding embodiments.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application, which are described in detail and are not to be construed as limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of protection of the present application is to be determined by the appended claims.
Claims (7)
1. A method of fault upload, comprising:
Reading fault information of each component in the electronic control unit;
generating a group of data frames conforming to a preset frame format according to the fault information, wherein the preset frame format comprises second data bits used for describing the frame information, and the second data bits comprise second data bits used for representing the total number of faults and second data bits used for representing frame sequence numbers;
Determining a frame number of each data frame according to the number of the group of data frames, determining a total number of faults according to the number of the fault numbers in the group of data frames, and taking the frame number and the total number of faults as frame information, wherein the frame information is used for identifying the group of data frames;
the frame information is supplemented to the group of data frames, so that a receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames;
Sequentially uploading the group of data frames according to the sequence of the frame sequence numbers of the data frames from small to large, and reading the fault information of each component in the electronic control unit again after the uploading is completed so as to generate and upload the next group of data frames; after the uploading of the next group of data frames is completed, the next group of data frames are generated and sent until the electronic control unit is powered down and cannot output fault information.
2. The method of claim 1, wherein the step of generating a set of data frames conforming to a preset frame format based on the failure information comprises:
extracting a fault code and a provider identifier in the fault information, wherein the fault information comprises the fault code and source information, and the source information comprises a device identifier and the provider identifier;
Obtaining a fault table corresponding to the provider identifier, wherein the fault table is used for indicating the mapping relation between the fault code and the fault number;
And determining a fault number corresponding to the fault code according to the fault table, and combining the fault number and the source information to obtain a group of data frames conforming to a preset frame format.
3. The method according to claim 2, wherein the step of determining the fault number corresponding to the fault code from the fault table comprises:
Determining the order of the fault codes in the fault table, wherein the fault table comprises at least one fault code, and the at least one fault code is arranged in a linear sequence;
And determining a fault number corresponding to the fault code according to the sequence of the fault code in the fault table.
4. The method of claim 1, wherein the preset frame format includes a first data bit for describing the fault information; the first data bits include a first one-to-one data bit for representing a device identification, a first two-to-one data bit for representing a vendor identification, and a first three data bit for representing a failure number.
5. A fault uploading device, comprising:
The reading unit is used for reading fault information of each component in the electronic control unit;
A processing unit, configured to generate a set of data frames according to a preset frame format according to the fault information, where the preset frame format includes second data bits for describing the frame information, and the second data bits include second first data bits for representing a total number of faults and second data bits for representing a frame sequence number; determining a frame number of each data frame according to the number of the group of data frames, determining a total number of faults according to the number of the fault numbers in the group of data frames, and taking the frame number and the total number of faults as frame information, wherein the frame information is used for identifying the group of data frames; the frame information is supplemented to the group of data frames, so that a receiving end determines the data transmission progress of the electronic control unit according to the frame information when receiving the group of data frames;
the uploading unit is used for sequentially uploading the group of data frames according to the sequence of the frame sequence numbers of the data frames from small to large, and reading the fault information of each component in the electronic control unit again after the uploading is finished so as to generate and upload the next group of data frames; after the uploading of the next group of data frames is completed, the next group of data frames are generated and sent until the electronic control unit is powered down and cannot output fault information.
6. The fault uploading device is characterized by comprising a processor and a memory, wherein the processor and the memory are connected through a bus; the processor is used for executing a plurality of instructions; the memory for storing the plurality of instructions adapted to be loaded by the processor and to perform the fault upload method of any one of claims 1-4.
7. A computer readable storage medium having stored therein a plurality of instructions adapted to be loaded by a processor and to perform the fault upload method of any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210791278.XA CN115079673B (en) | 2022-07-05 | 2022-07-05 | Fault uploading method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210791278.XA CN115079673B (en) | 2022-07-05 | 2022-07-05 | Fault uploading method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115079673A CN115079673A (en) | 2022-09-20 |
| CN115079673B true CN115079673B (en) | 2024-06-11 |
Family
ID=83258633
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210791278.XA Active CN115079673B (en) | 2022-07-05 | 2022-07-05 | Fault uploading method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115079673B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1340275A (en) * | 1999-02-18 | 2002-03-13 | 诺基亚移动电话有限公司 | Video coding |
| CN1458764A (en) * | 2003-05-30 | 2003-11-26 | 西安通视数据有限责任公司 | Forward error correcting method in one-way broadcast file transmission |
| CN101111845A (en) * | 2005-02-02 | 2008-01-23 | 皇家飞利浦电子股份有限公司 | Method, apparatus, device, system, program, for calibrating |
| CN101271421A (en) * | 2007-03-22 | 2008-09-24 | 北京邮电大学 | Software fault test system and method |
| CN103443725A (en) * | 2011-03-29 | 2013-12-11 | 三菱电机株式会社 | Abnormality diagnosis device and abnormality diagnosis system for servo control device |
| CN108111341A (en) * | 2017-12-15 | 2018-06-01 | 惠州市敦雅科技有限公司 | A kind of fault message feedback method and device |
| CN111993891A (en) * | 2019-05-27 | 2020-11-27 | 广州汽车集团股份有限公司 | Electric vehicle data storage device and control method and monitoring system thereof |
| CN112525553A (en) * | 2020-12-16 | 2021-03-19 | 重庆金康赛力斯新能源汽车设计院有限公司 | Vehicle fault remote diagnosis method and related equipment |
| CN112732982A (en) * | 2021-01-18 | 2021-04-30 | 深圳市元征科技股份有限公司 | Fault code storage method and device, terminal equipment and readable storage medium |
-
2022
- 2022-07-05 CN CN202210791278.XA patent/CN115079673B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1340275A (en) * | 1999-02-18 | 2002-03-13 | 诺基亚移动电话有限公司 | Video coding |
| CN1458764A (en) * | 2003-05-30 | 2003-11-26 | 西安通视数据有限责任公司 | Forward error correcting method in one-way broadcast file transmission |
| CN101111845A (en) * | 2005-02-02 | 2008-01-23 | 皇家飞利浦电子股份有限公司 | Method, apparatus, device, system, program, for calibrating |
| CN101271421A (en) * | 2007-03-22 | 2008-09-24 | 北京邮电大学 | Software fault test system and method |
| CN103443725A (en) * | 2011-03-29 | 2013-12-11 | 三菱电机株式会社 | Abnormality diagnosis device and abnormality diagnosis system for servo control device |
| CN108111341A (en) * | 2017-12-15 | 2018-06-01 | 惠州市敦雅科技有限公司 | A kind of fault message feedback method and device |
| CN111993891A (en) * | 2019-05-27 | 2020-11-27 | 广州汽车集团股份有限公司 | Electric vehicle data storage device and control method and monitoring system thereof |
| CN112525553A (en) * | 2020-12-16 | 2021-03-19 | 重庆金康赛力斯新能源汽车设计院有限公司 | Vehicle fault remote diagnosis method and related equipment |
| CN112732982A (en) * | 2021-01-18 | 2021-04-30 | 深圳市元征科技股份有限公司 | Fault code storage method and device, terminal equipment and readable storage medium |
Non-Patent Citations (5)
| Title |
|---|
| .轨道车辆转向架关键部件故障分析研究;徐晓灵;《科技风》;20201231;全文 * |
| Detecting Cycles in Graphs Using Parallel Capabilities of GPU;Mahdi F;《International Conference on Digital Information & Communication Technology & Its Applications》;20111231;全文 * |
| DF_(7G)型机车触摸显示器的设计开发;苗永春;苏德坤;;机车电传动;20060915(05);全文 * |
| 一种使用CAN总线汽车组合仪表的设计方案;郝魁;吕达;于洪兵;;内燃机与配件;20180130(02);全文 * |
| 基于UDS的汽车通信故障诊断机制与处理策略;刘彤;赵益宏;蔡伟杰;陈文强;韦兴民;赵福全;;汽车电器;20130220(02);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115079673A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101744226B1 (en) | System and method for providing diagnostic fault information | |
| US20050027480A1 (en) | Model-based intelligent diagnostic agent | |
| CN112485019B (en) | Vehicle fault diagnosis method and device, vehicle and storage medium | |
| JP2009265104A (en) | Diagnostic data mining | |
| US8103946B2 (en) | Secure data strategy for vehicle control systems | |
| CN112558584B (en) | Diagnostic data acquisition method and device and diagnostic equipment | |
| CN115079673B (en) | Fault uploading method, device, equipment and storage medium | |
| CN114662954A (en) | Vehicle performance evaluation system | |
| CN111721972B (en) | Method and device for verifying rotation speed measured value of electrically-driven gearbox | |
| CN113515307A (en) | Calibratable can information processing system and method based on hybrid electric vehicle | |
| JP2021138210A (en) | Vehicle data management device, vehicle data management system and vehicle data management method | |
| CN112415983B (en) | Working method for analyzing whole vehicle signals | |
| CN115076364A (en) | Hybrid power gear shifting system and fault diagnosis processing method thereof | |
| CN114756585A (en) | Vehicle data acquisition method and device, electronic equipment and storage medium | |
| CN114384887B (en) | Emission diagnosis method and device and electronic equipment | |
| WO2018218534A1 (en) | Vehicle information identification method, identifying apparatus, and computer readable storage medium | |
| JP2020083139A (en) | Vehicle electronic control device and diagnostic system | |
| US11822421B2 (en) | Apparatus and method for diagnosing faults | |
| JPH0746676A (en) | Communication system for vehicle diagnosis | |
| JP2022015991A (en) | Communication system | |
| CN117971874A (en) | Configuration word generation method and device, electronic equipment and storage medium | |
| GB2612362A (en) | Fault prediction for machines | |
| CN113988034A (en) | Vehicle physical examination method, electronic device and storage medium | |
| CN116580475A (en) | Data recording device and method | |
| CN115757044A (en) | Method, device, equipment and medium for processing abnormal state of vehicle controller |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240116 Address after: No. 13 Xingxiang Road, Zengjia Town, High tech Zone, Jiulongpo District, Chongqing, 400039 Applicant after: Chongqing Selis Phoenix Intelligent Innovation Technology Co.,Ltd. Address before: 610095 No. 2901, floor 29, unit 1, building 1, No. 151, Tianfu Second Street, high tech Zone, China (Sichuan) pilot Free Trade Zone, Chengdu, Sichuan Province Applicant before: Chengdu Thalys Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |