CN114489766A - Method, device, medium and equipment for checking version information of vehicle-mounted controller - Google Patents
Method, device, medium and equipment for checking version information of vehicle-mounted controller Download PDFInfo
- Publication number
- CN114489766A CN114489766A CN202210007077.6A CN202210007077A CN114489766A CN 114489766 A CN114489766 A CN 114489766A CN 202210007077 A CN202210007077 A CN 202210007077A CN 114489766 A CN114489766 A CN 114489766A
- Authority
- CN
- China
- Prior art keywords
- controller
- standard
- current
- version
- version number
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/194—Calculation of difference between files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a method, a device, a medium and equipment for checking version information of a vehicle-mounted controller, wherein the method comprises the following steps: creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type in different production stages; sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction; if the current part number, the current software version number and the current hardware version number sent by each controller are determined to be received, the current part number, the current software version number and the current hardware version number are verified one by one based on the standard version file of the controller; therefore, corresponding standard controller version information is created to provide standard basis for verification; the current version information of each controller is automatically read through the diagnosis request message, the whole reading process does not need manual participation, and the reading efficiency is improved; the current version information is automatically verified based on the standard controller version information, so that the verification accuracy can be improved.
Description
Technical Field
The invention belongs to the technical field of vehicle testing, and particularly relates to a method, a device, a medium and equipment for checking version information of an on-board controller.
Background
When a vehicle in a research and development stage needs to be tested or has a problem, firstly, whether the information (part number, hardware version number and software version number) of the whole vehicle controller is correct or not needs to be rapidly confirmed, and basic premise is provided for problem analysis and confirmation; it is necessary to read the vehicle control unit information quickly and accurately.
However, with the development of vehicle motorization, intellectualization and networking, the number of controllers of a single vehicle is increasing, and therefore version control of the vehicle controller becomes more cumbersome. If in the test process of the research and development stage, errors of the version information of the controller can bring hidden quality troubles to the vehicle.
The prior art generally reads the controller information by manually operating a specific tool and performs manual comparison. However, this method is relatively long in reading version information, inefficient, and prone to errors in human comparison.
Disclosure of Invention
Aiming at the problems in the prior art, the embodiment of the invention provides a method, a device, a medium and equipment for checking version information of an on-board controller, which are used for solving the technical problems that in the prior art, when a vehicle is tested or the vehicle has problems and the version information of the on-board controller needs to be identified and checked, the reading efficiency of the version information of the controller is low, and errors are easily caused by manual comparison.
In a first aspect of the present invention, a method for checking version information of an onboard controller is provided, the method comprising:
creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
and if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file.
In the foregoing solution, the creating a standard version file of a controller includes:
acquiring the name, the diagnosis request ID and the diagnosis response ID of each controller in all vehicle types;
aiming at any vehicle type, acquiring a standard part number, a standard software version number and a standard hardware version number corresponding to each controller of the vehicle type in different production stages;
summarizing the name, the diagnosis request ID, the diagnosis response ID, the standard part number, the standard software version number and the standard hardware version number corresponding to each controller into a first table file;
and generating the controller standard version file based on the first table file.
In the above scheme, the sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction includes:
analyzing the first table file according to the one-key reading instruction, and obtaining the name, the diagnosis request ID and the diagnosis response ID of each controller;
and sending a diagnosis request message to each controller based on the communication network segment and the diagnosis request ID.
In the foregoing solution, the sending a diagnosis request packet to each controller based on a communication network segment and the diagnosis request ID includes:
if the communication network segment comprises multiple network segments, sending corresponding diagnosis request messages to the controllers in parallel based on the multiple network segments and the diagnosis request IDs;
and if the communication network segment comprises a single network segment, sending corresponding diagnosis request messages to the controllers one by one based on the single network segment and the diagnosis request ID.
In the above solution, the checking the current part number, the current software version number, and the current hardware version number one by one based on the controller standard version file includes:
analyzing the controller standard version file, and obtaining the standard part number, the standard software version number and the standard hardware version number of each controller;
comparing the standard part number with the current part number, comparing the standard software version number with the current software version number and comparing the standard hardware version number with the current hardware version number aiming at any one controller;
and outputting a comparison result.
In the foregoing scheme, the outputting the comparison result includes:
if the current part number is determined to be consistent with the standard part number, the current software version number is determined to be consistent with the standard software version number, and the current hardware version number is determined to be consistent with the standard hardware version number, outputting first prompt information with correct controller version information;
and if any item of the current part number, the current software version number and the current hardware version number is determined to be inconsistent with the corresponding information in the standard version file of the controller, outputting second prompt information of wrong version information of the controller.
In the above scheme, after the diagnostic request message is sent to each controller of the vehicle to be tested according to the one-key reading instruction, the method further includes:
if the diagnosis request message is determined not to obtain the response of the current controller, outputting third prompt information which does not realize the diagnosis function; the third prompt message includes the name of the current controller.
In a second aspect of the present invention, there is provided an apparatus for verifying version information of an on-board controller, the apparatus comprising:
the creating unit is used for creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
the sending unit is used for sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
and the checking unit is used for checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received.
In a third aspect of the invention, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the method of any one of the first aspect.
In a fourth aspect of the present invention, a computer device comprises a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of the first aspect when executing the program.
The invention provides a method, a device, a medium and equipment for checking version information of a vehicle-mounted controller, wherein the method comprises the following steps: creating a standard version file of a controller; the controller standard version file comprises controller version information of each vehicle type at different production stages; sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction; if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, the current part number, the current software version number and the current hardware version number are verified one by one based on the controller standard version file; therefore, corresponding standard controller version information is established for each vehicle type in different production stages, and a standard basis is provided for verification; then, the current version information of each controller is automatically read through the diagnosis request message, the whole reading process does not need manual participation, and the reading efficiency of the version information is improved; after the current version information is read, the current version information is automatically verified based on the standard controller version information, and compared with a manual comparison mode, the verification accuracy can be improved.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 is a schematic flow chart illustrating a method for checking version information of an onboard controller according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of an apparatus for checking version information of an onboard controller according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to better understand the technical solutions, the technical solutions of the embodiments of the present specification are described in detail below with reference to the drawings and specific embodiments, and it should be understood that the specific features of the embodiments and embodiments of the present specification are detailed descriptions of the technical solutions of the embodiments of the present specification, and are not limitations of the technical solutions of the present specification, and the technical features of the embodiments and embodiments of the present specification may be combined with each other without conflict.
The embodiment provides a method for checking version information of an on-board controller, as shown in fig. 1, the method includes the following steps:
s110, creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
in general, there are numerous types of vehicles, such as off-road, commercial, passenger car, etc.; and the number and type of controllers used for different vehicle models may also be different. The number and type of controllers for each model of vehicle are determined during the design phase, but from the beginning of the design to the mass production, many production phases are passed in the middle, such as the model design phase, the development phase, the whole vehicle testing phase, the mass production phase, and so on. And the version information of the controller may be different at different stages of production. Wherein, the controller may include: the system comprises a vehicle control unit, a motor controller, a battery management system BMS, a vehicle-mounted charger and the like.
Therefore, the step needs to create a controller standard version file first; the controller standard version file comprises controller version information of each vehicle type in different production stages.
In one embodiment, creating a controller standard version file includes:
acquiring the name, the diagnosis request ID and the diagnosis response ID of each controller in all vehicle types;
aiming at any vehicle type, acquiring a standard part number, a standard software version number and a standard hardware version number corresponding to each controller of the vehicle type in different production stages;
summarizing names, diagnosis request IDs, diagnosis response IDs, standard part numbers, standard software version numbers and standard hardware version numbers corresponding to all controllers into a first table file;
a controller standard version file is generated based on the first table file.
Alternatively, the present embodiment may group the names, the diagnostic request IDs, and the diagnostic response IDs of the controllers in one table file (for example, a second table file); summarizing the standard part number, the standard software version number and the standard hardware version number in another table file (such as a third table file); then in one embodiment, creating a controller standard version file comprises:
acquiring the name, the diagnosis request ID and the diagnosis response ID of each controller in all vehicle types;
summarizing the name, the diagnosis request ID and the diagnosis response ID of each controller into a second table file;
aiming at any vehicle type, acquiring a standard part number, a standard software version number and a standard hardware version number corresponding to each controller of the vehicle type in different production stages;
summarizing the standard part number, the standard software version number and the standard hardware version number corresponding to each controller into a third table file;
and generating a controller standard version file based on the second table file and the third table file.
In this embodiment, the first table file, the second table file and the third table file may be table files in any format, such as Excel tables. Each controller corresponds to a unique diagnosis request ID and a diagnosis response ID so as to send a diagnosis request message to the controller according to the diagnosis request ID and acquire version information of the controller according to the diagnosis response ID. The controller name is generally an english name, such as the english name VCU of the vehicle controller.
For example, the first table file may be as shown in table 1:
TABLE 1
The second table file may be as shown in table 2:
TABLE 2
In the development stage, a third table file corresponding to a certain vehicle type can be shown in table 3:
TABLE 3
| Controller name | Standard part number | Standard software version number | Standard hardware version number |
| Controller A | 1 | 1.1 | 1.2 |
| Controller B | 2 | 2.1 | 1.2 |
| …… | …… | …… | |
| Controller N | N | 3.2 | 3.3 |
Therefore, the controller standard version file is created for each vehicle model in different production stages, and after the controller standard version file is created, the controller standard version file can be generated into an initialization (ini) file with a specific format by using Python software. The staff member may import the initialization file into the diagnostic platform (which may be understood as a diagnostic server). The diagnosis platform of the present embodiment may be a canoe (can open environment) tool.
The controller standard version file can provide standard information for a subsequent verification process, and can effectively meet the monitoring requirements on the part number, the hardware version number and the software version number of the vehicle controller in the research and development stage; when a vehicle in a development stage needs to be tested or has a problem, whether the information of the vehicle controller is correct or not can be rapidly confirmed through the standard version file of the controller, and a basic premise can be provided for problem analysis.
S111, sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
when a vehicle to be tested in a research and development stage needs to be tested, a worker can click a one-key reading instruction in the diagnosis platform, and then the diagnosis platform can send a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction.
Here, the diagnostic request ID and the diagnostic response ID for each controller are stored in the controller standard version file described above. Therefore, in one embodiment, sending a diagnosis request message to each controller of the vehicle under test one by one according to the one-key reading instruction includes:
analyzing the first table file according to the one-key reading instruction, and obtaining the name, the diagnosis request ID and the diagnosis response ID of each controller;
and sending a diagnosis request message to each controller based on the communication network segment and the diagnosis request ID.
Here, if the diagnostic request ID and the diagnostic response ID corresponding to the controller are stored in the second table file, it is also necessary to read a command to analyze the second table file to obtain the name, the diagnostic request ID, and the diagnostic response ID of each controller.
In one embodiment, sending a diagnosis request message to each controller based on a communication network segment and the diagnosis request ID includes:
if the communication network segment comprises multiple network segments, sending corresponding diagnosis request messages to each controller in parallel based on the multiple network segments and the diagnosis request ID;
and if the communication network segment comprises the single network segment, sending a corresponding diagnosis request message to each controller one by one based on the single network segment and the diagnosis request ID.
In this embodiment, in order to adapt to the maturity of the diagnostic function in the development stage, the reading of the full network segment or the sub-network segment of the interface of the On Board Diagnostics (OBD) in the development stage can be supported.
Specifically, when the vehicles are in different production stages, the corresponding communication network segments may be different, in some production stages, the vehicles may perform multi-network segment communication, and in some production stages, the vehicles may perform only single-network segment communication. Therefore, when the communication network segment comprises multiple network segments, in order to improve the reading efficiency, the diagnosis request message is sent to the corresponding control in parallel based on the multiple network segments.
If the communication network segment comprises the single network segment, the diagnosis request message is sent to each controller one by one based on the single network segment and the diagnosis request ID.
It is worth noting that even if the version information is sent through a single network segment, the reading time of each controller version information can be kept about 1-2 s, and compared with the mode that in the prior art, when the version information of the controller is read, the version information can be read only by manually operating a specific tool after being sequentially connected with the controller and then manually operating on an operation interface, the reading efficiency of the version information can be obviously improved.
And S111, if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file.
After the controller receives the diagnosis request message, if the controller is in a normal state, the current part number, the current software version number and the current hardware version number of the controller can be fed back to the diagnosis.
And if the diagnosis server determines that the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are received, the diagnosis server checks the current part number, the current software version number and the current hardware version number one by one based on the standard version file of the controller.
In one embodiment, the checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file includes:
analyzing a controller standard version file by using an analysis strategy written by a CAN bus Access Programming Language (CAPL) Language, and acquiring a standard part number, a standard software version number and a standard hardware version number of each controller;
aiming at any controller, comparing the standard part number with the current part number, comparing the standard software version number with the current software version number, and comparing the standard hardware version number with the current hardware version number;
and outputting a comparison result.
In this embodiment, the comparison result may be directly printed in a write display (write) window of the diagnosis platform, or the comparison result may be printed as a file in html or ini format, which is not limited herein.
In this embodiment, when the version information is printed, the part number and the hardware version number support the formats of "0 to 9", "a to Z" and "a to Z" for the character string corresponding to the software version number, and the unknown character string is printed in a unified manner for the other character strings? ".
In one embodiment, outputting the comparison result comprises:
if the current part number is determined to be consistent with the standard part number, the current software version number is determined to be consistent with the standard software version number, and the current hardware version number is determined to be consistent with the standard hardware version number, outputting first prompt information with correct controller version information; and simultaneously printing the current version information of the controller;
and if any item of the current part number, the current software version number and the current hardware version number is determined to be inconsistent with the corresponding information in the standard version file of the controller, outputting second prompt information of wrong version information of the controller.
Specifically, if the current part number is not consistent with the standard part number, or the current software version number is not consistent with the standard software version number, or the current hardware version number is not consistent with the standard hardware version number, the second prompt message that the version information of the controller is wrong is output. And, the current version information of the controller is printed out at the same time.
In addition, if the controller fails and may not respond to the diagnosis request message, in an embodiment, after the diagnosis request message is sent to each controller of the vehicle to be tested according to the one-key reading instruction, the method further includes:
if the diagnosis request message is determined not to obtain the response of the current controller, outputting third prompt information which does not realize the diagnosis function; the third prompt message includes the name of the current controller.
Therefore, the embodiment can flexibly and quickly compare the controller information (part number, hardware version number and software version number) of different vehicle types in different stages, prompt and provide efficient support for problem diagnosis.
In the method for checking version information of a vehicle-mounted controller provided by this embodiment, first, for each vehicle type in different production stages, corresponding standard controller version information is created to provide a standard basis for checking; then, the current version information of each controller is automatically read through the diagnosis request message, the whole reading process does not need manual participation, the operation is simple, and the reading efficiency of the version information is improved; after the current version information is read, the current version information is automatically and quickly verified based on the standard controller version information, and compared with a manual comparison mode, the verification accuracy can be improved.
Based on the same inventive concept, this embodiment further provides a device for checking version information of an on-board controller, as shown in fig. 2, the device includes:
a creating unit 21 for creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
the sending unit 22 is used for sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
a checking unit 23, configured to, if it is determined that the current part number, the current software version number, and the current hardware version number that are sent by each of the controllers based on the diagnosis request packet are received, check the current part number, the current software version number, and the current hardware version number one by one based on the controller standard version file.
The specific functions of the above units can be referred to the corresponding descriptions in the above method embodiments, and are not described herein again. Since the apparatus described in the embodiment of the present invention is an apparatus used for implementing the method in the embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the apparatus based on the method described in the embodiment of the present invention, and thus the detailed description is omitted here. All devices adopted by the method of the embodiment of the invention belong to the protection scope of the invention.
Based on the same inventive concept, the present embodiment provides a computer apparatus 300, as shown in fig. 3, including a memory 310, a processor 320, and a computer program 311 stored on the memory 310 and operable on the processor 320, wherein the processor 320 executes the computer program 311 to implement the following steps:
creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
and if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file.
In particular embodiments, any of the foregoing embodiments may be implemented when processor 320 executes computer program 311.
Since the computer device described in this embodiment is a device used for implementing the method for verifying the version information of the vehicle-mounted controller in this embodiment, a person skilled in the art can understand a specific implementation manner of the computer device in this embodiment and various variations thereof based on the methods described in the foregoing embodiments of this application, and therefore, a detailed description of how the server implements the method in this embodiment is not provided here. The equipment used by those skilled in the art to implement the methods in the embodiments of the present application is within the scope of the present application.
Based on the same inventive concept, the present embodiment provides a computer-readable storage medium 400, as shown in fig. 4, on which a computer program 411 is stored, the computer program 411 implementing the following steps when being executed by a processor:
creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
when a vehicle to be tested is tested, a diagnosis request message is sent to each controller according to a one-key reading instruction;
and if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file.
In a specific implementation, the computer program 411 may implement any of the foregoing embodiments when executed by a processor.
The method, the device, the medium and the equipment for checking the version information of the vehicle-mounted controller provided by the embodiment of the invention have the beneficial effects that at least:
the invention provides a method, a device, a medium and equipment for checking version information of a vehicle-mounted controller, wherein the method comprises the following steps: creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages; sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction; if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, the current part number, the current software version number and the current hardware version number are verified one by one based on the controller standard version file; therefore, corresponding standard controller version information is established for each vehicle type in different production stages, and a standard basis is provided for verification; then, the current version information of each controller is automatically read through the diagnosis request message, the whole reading process does not need manual participation, and the reading efficiency of the version information is improved; after the current version information is read, the current version information is automatically verified based on the standard controller version information, and compared with a manual comparison mode, the verification accuracy can be improved.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (10)
1. A method of verifying version information for an on-board controller, the method comprising:
creating a standard version file of a controller; the controller standard version file comprises controller version information of each vehicle type at different production stages;
sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
and if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received, checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file.
2. The method of claim 1, wherein the creating a controller standard version file comprises:
acquiring the name, diagnosis request ID and diagnosis response ID of each controller in all vehicle types;
aiming at any vehicle type, acquiring a standard part number, a standard software version number and a standard hardware version number corresponding to each controller of the vehicle type in different production stages;
summarizing the name, the diagnosis request ID, the diagnosis response ID, the standard part number, the standard software version number and the standard hardware version number corresponding to each controller into a first table file;
and generating the controller standard version file based on the first table file.
3. The method of claim 2, wherein sending a diagnostic request message to each controller of the vehicle under test according to the one-touch read command comprises:
analyzing the first table file according to the one-key reading instruction, and obtaining the name, the diagnosis request ID and the diagnosis response ID of each controller;
and sending a diagnosis request message to each controller based on the communication network segment and the diagnosis request ID.
4. The method of claim 3, wherein said sending a diagnostic request message to each of said controllers based on a communication network segment and said diagnostic request ID comprises:
if the communication network segment comprises multiple network segments, sending corresponding diagnosis request messages to the controllers in parallel based on the multiple network segments and the diagnosis request IDs;
and if the communication network segment comprises a single network segment, sending corresponding diagnosis request messages to the controllers one by one based on the single network segment and the diagnosis request ID.
5. The method of claim 1, wherein said checking the current part number, the current software version number, and the current hardware version number one by one based on the controller standard version file comprises:
analyzing the controller standard version file, and obtaining the standard part number, the standard software version number and the standard hardware version number of each controller;
comparing the standard part number with the current part number, comparing the standard software version number with the current software version number and comparing the standard hardware version number with the current hardware version number aiming at any one controller;
and outputting a comparison result.
6. The method of claim 5, wherein outputting the comparison result comprises:
if the current part number is determined to be consistent with the standard part number, the current software version number is determined to be consistent with the standard software version number, and the current hardware version number is determined to be consistent with the standard hardware version number, outputting first prompt information with correct controller version information;
and if any item of the current part number, the current software version number and the current hardware version number is determined to be inconsistent with the corresponding information in the standard version file of the controller, outputting second prompt information of wrong version information of the controller.
7. The method of claim 1, wherein after sending the diagnosis request message to each controller of the vehicle under test according to the one-touch reading instruction, the method further comprises:
if the diagnosis request message is determined not to obtain the response of the current controller, outputting third prompt information which does not realize the diagnosis function; the third prompt message includes the name of the current controller.
8. An apparatus for verifying version information of an on-board controller, the apparatus comprising:
the creating unit is used for creating a controller standard version file; the controller standard version file comprises controller version information of each vehicle type at different production stages;
the sending unit is used for sending a diagnosis request message to each controller of the vehicle to be tested according to the one-key reading instruction;
and the checking unit is used for checking the current part number, the current software version number and the current hardware version number one by one based on the controller standard version file if the current part number, the current software version number and the current hardware version number which are sent by each controller based on the diagnosis request message are determined to be received.
9. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 7.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 7 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210007077.6A CN114489766A (en) | 2022-01-05 | 2022-01-05 | Method, device, medium and equipment for checking version information of vehicle-mounted controller |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210007077.6A CN114489766A (en) | 2022-01-05 | 2022-01-05 | Method, device, medium and equipment for checking version information of vehicle-mounted controller |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114489766A true CN114489766A (en) | 2022-05-13 |
Family
ID=81509846
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210007077.6A Pending CN114489766A (en) | 2022-01-05 | 2022-01-05 | Method, device, medium and equipment for checking version information of vehicle-mounted controller |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114489766A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114661330A (en) * | 2022-05-25 | 2022-06-24 | 武汉海微科技有限公司 | Vehicle hardware program updating method, device, equipment and storage medium |
| CN116389467A (en) * | 2023-06-07 | 2023-07-04 | 北京集度科技有限公司 | Data transmission device, method for checking a vehicle, vehicle and computer program product |
| CN116737220A (en) * | 2023-05-23 | 2023-09-12 | 广州汽车集团股份有限公司 | Method and device for acquiring domain controller software version information and vehicle diagnosis equipment |
-
2022
- 2022-01-05 CN CN202210007077.6A patent/CN114489766A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114661330A (en) * | 2022-05-25 | 2022-06-24 | 武汉海微科技有限公司 | Vehicle hardware program updating method, device, equipment and storage medium |
| CN116737220A (en) * | 2023-05-23 | 2023-09-12 | 广州汽车集团股份有限公司 | Method and device for acquiring domain controller software version information and vehicle diagnosis equipment |
| CN116389467A (en) * | 2023-06-07 | 2023-07-04 | 北京集度科技有限公司 | Data transmission device, method for checking a vehicle, vehicle and computer program product |
| CN116389467B (en) * | 2023-06-07 | 2023-08-11 | 北京集度科技有限公司 | Data transmission device, method for checking a vehicle, vehicle and computer program product |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114489766A (en) | Method, device, medium and equipment for checking version information of vehicle-mounted controller | |
| CN108563214B (en) | Vehicle diagnosis method, device and equipment | |
| CN107370637B (en) | Vehicle-mounted ECU communication function automatic test system and method | |
| CN113608518B (en) | Data generation method, device, terminal equipment and medium | |
| CN103713527B (en) | Refreshing method, writing apparatus and writing system for automobile electronic controller | |
| CN103439961B (en) | Automobile electronic control unit diagnostic function test method and system | |
| CN111045416B (en) | Method and device for analyzing CAN (controller area network) signal of whole vehicle by using diagnosis message | |
| CN108334058A (en) | A kind of diagnostic system and method based on car body controller | |
| CN113189970A (en) | Hardware-in-loop automatic test method and system of CAN bus controller and storage medium | |
| CN112015489A (en) | Management method, device, storage medium and system for vehicle-mounted software | |
| CN114407812B (en) | Diagnostic database determination method, device, electronic equipment and storage medium | |
| CN113791605A (en) | Test method, device, equipment and storage medium | |
| CN114924544A (en) | Method and system for matching and detecting automobile ECU software | |
| CN113406944B (en) | Vehicle diagnosis method, device, equipment and computer readable storage medium | |
| CN111857103B (en) | Vehicle diagnosis method, device, equipment and storage medium | |
| CN107229567A (en) | A kind of IPMI firmwares automatization test system | |
| CN115118577B (en) | Remote upgrade abnormality cause determination method, device, electronic equipment and storage medium | |
| CN111240302B (en) | Signal verification method and device, electronic equipment and storage medium | |
| CN113434411A (en) | TIAS function test method and system | |
| CN111143225B (en) | Vulnerability processing method of automobile diagnosis software and related products | |
| CN113590399A (en) | Automatic testing system and method for vehicle-mounted voice | |
| Lutchen et al. | AI-based classification of CAN measurements for network and ECU identification | |
| CN110471399A (en) | Vehicular diagnostic method, device, system and vehicle based on ECU | |
| JP2005014743A (en) | Failure part detection device for vehicle | |
| CN117294552B (en) | Method and device for testing data integrity based on HJ1239 standard |
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 |