Software version checking device and method for vehicle controller, electronic equipment and medium

Abstract

The embodiment of the invention discloses a software version checking device and method for a vehicle controller, electronic equipment and a medium, and belongs to the technical field of vehicle engineering. The software version checking device at least comprises a design end, a supply end, an MOM module, a PDM module and an EOL management module. The design end is respectively connected with the PDM module and the EOL management module; the MOM module is connected with the EOL management module; and the EOL management module is respectively connected with the PDM module and the EOL test equipment. According to the embodiment of the invention, the EOL management module is introduced to stretch across the design, supply, production and test links of the vehicle controller, and the EOL management module is in butt joint with the design end, the MOM module, the PDM module and the EOL test equipment, so that the software version verification of the vehicle controller can be realized, the accident frequency of vehicle faults caused by wrong installation of the software version of the controller is reduced, and the reliability of the vehicle controller is improved. And normal production of a workshop is ensured.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of vehicle engineering technology, and in particular to a software version verification device, method, electronic equipment and medium for a vehicle controller. Background Art

[0002] With the continuous upgrading of vehicle intelligent driving technology, the types and number of vehicle controllers are increasing, and the iteration of controller software versions is becoming more frequent. At present, it is difficult to distinguish between controllers with the same hardware and different software when assembling them at the production site. Once a controller is mistakenly installed with a software version that is not exclusive to the controller, it will cause vehicle failure. Such faults are difficult to troubleshoot, which greatly affects the normal production of the workshop. Summary of the invention

[0003] The embodiments of the present invention provide a software version verification device, method, electronic device and medium for a vehicle controller, so as to at least realize software version verification of the vehicle controller, reduce the frequency of vehicle failure accidents caused by incorrect installation of controller software version, and help ensure normal production in the workshop.

[0004] In a first aspect, an embodiment of the present invention provides a software version checking device for a vehicle controller, comprising at least a design end, a supply end, a manufacturing operation management MOM module, a product data management PDM module and an end-of-line EOL management module;

[0005] The design end is connected to the PDM module and the EOL management module respectively, and is used to at least upgrade the internal software and software version number of each type of design controller according to the vehicle control function requirements; and maintain the upgraded software version number corresponding to each type of design controller to the PDM module, and update the upgraded internal software data corresponding to each type of design controller to the EOL management module;

[0006] The supply end is at least used to upgrade the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements;

[0007] The MOM module is connected to the EOL management module and is at least used to pre-acquire a subsequent vehicle production plan and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module;

[0008] The EOL management module is connected to the PDM module and the EOL test equipment respectively, and is at least used to maintain the view table of the controller to be tested; and, based on the planned production BOM information and the maintained view table of the controller to be tested, generates a form of the controller to be tested, and retrieves the software version number of the controller to be tested in the PDM module according to the form of the controller to be tested, so as to match the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; and, in cooperation with the EOL test equipment, performs software version verification on the controller to be tested;

[0009] Wherein, the controller to be tested is the design controller, the inventory controller or the production line controller.

[0010] Optionally, the EOL management module cooperates with the EOL test device to perform software version verification on the controller to be tested in at least the following manner:

[0011] After the EOL test device is connected to the current vehicle to be tested through the OBD port of the on-board diagnostic system by the operator, the EOL test device scans the current vehicle to be tested to obtain the controller list to be tested corresponding to the current vehicle to be tested and the software version number corresponding to each type of the controller to be tested in the current vehicle to be tested from the EOL management module;

[0012] The EOL test device reads the preset address parameters of each of the controllers to be tested in the current vehicle to be tested through a diagnostic instruction, so as to generate a software version verification result based on the preset address parameters of each of the controllers to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module;

[0013] The EOL test equipment transmits the software version verification result back to the EOL management module for storage, so as to trace back the software version verification result of any vehicle to be tested later.

[0014] Optionally, if the preset address parameter of each of the controllers to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module are consistent, the EOL test device displays that the software version verification result is qualified;

[0015] If the preset address parameters of at least one of the controllers to be tested are not consistent with the software version number of the corresponding type of vehicle controller in the EOL management module, the EOL testing device will display the software version verification result as an error, and then perform a full data flash on the corresponding controller to be tested based on the software version number and internal software data that can be obtained by the EOL management module.

[0016] Optionally, the design end is specifically used to define the software version number of each type of the designed controller according to the vehicle control function requirements, and maintain the upgraded software version number corresponding to each type of the designed controller in the production attribute unit of the controller part drawing number under the PDM module; and, upgrade the internal software of each type of the designed controller according to the vehicle control function requirements, and update the upgraded internal software data corresponding to each type of the designed controller to the EOL management module.

[0017] Optionally, the supply end is specifically used to upgrade the internal software of the inventory controller and the production line controller according to the vehicle control function requirements, and write the upgraded software version number as a preset address parameter into the preset address of the inventory controller or the production line controller through a preset protocol.

[0018] Optionally, if the software version verification device needs to modify the software version number of at least one type of the controller to be tested, but the EOL management module has generated the controller to be tested form, then the EOL management module is at least further used to batch modify the software version number of at least one type of the controller to be tested through the controller to be tested form.

[0019] Optionally, if the design end subsequently updates the internal software and software version number of any type of the designed controller, the EOL management module is at least used to maintain the internal software data of the corresponding type of the controller under test, and the PDM module is at least used to modify the software version number of the corresponding type of the controller under test.

[0020] In a second aspect, an embodiment of the present invention further provides a software version verification method for a vehicle controller, wherein the software version verification device described in the first aspect is used to perform the method, and the method at least comprises:

[0021] Upgrading the internal software and software version number of each type of design controller according to the vehicle control function requirements through the design end;

[0022] Maintaining the upgraded software version numbers corresponding to various design controllers to the PDM module through the design end, and updating the upgraded internal software data corresponding to various design controllers to the EOL management module;

[0023] Upgrading the internal software and software version numbers of the inventory controller and the production line controller according to the vehicle control function requirements through the supply side;

[0024] Pre-acquire the subsequent vehicle production plan through the MOM module, and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module;

[0025] Maintaining the controller view table to be tested by the EOL management module;

[0026] Generate a controller to be tested form according to the planned production BOM information and the maintained controller to be tested view table through the EOL management module, and retrieve the software version number of the controller to be tested in the PDM module according to the controller to be tested form to achieve matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data;

[0027] Performing software version verification on the controller to be tested by cooperating with the EOL test equipment through the EOL management module;

[0028] Wherein, the controller to be tested is the design controller, the inventory controller or the production line controller.

[0029] In a third aspect, an embodiment of the present invention further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the program, the steps in the software version verification method for the vehicle controller described in the second aspect are implemented.

[0030] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps in the vehicle controller software version verification method described in the second aspect are implemented.

[0031] The technical solution provided by the embodiment of the present invention is as follows: first, the design end upgrades the internal software and software version number of each type of design controller according to the vehicle control function requirements; further, the design end maintains the upgraded software version number corresponding to each type of design controller to the PDM module, and updates the upgraded internal software data corresponding to each type of design controller to the EOL management module; further, the supply end upgrades the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements; further, the MOM module pre-acquires the subsequent vehicle production plan, and pushes the planned production bill of materials BOM information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module; further, the EOL management module maintains the view table of the controller to be tested; further, the EOL management module generates a form of the controller to be tested according to the planned production BOM information and the maintained view table of the controller to be tested, and retrieves the software version number of the controller to be tested in the PDM module according to the form of the controller to be tested, so as to achieve the matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; finally, the EOL management module cooperates with the EOL test equipment to perform software version verification on the controller to be tested. In view of this, the embodiment of the present invention introduces an EOL management module that spans the design, supply, production and testing links of the vehicle controller. By connecting the EOL management module to the design end, MOM module, PDM module and EOL testing equipment, the software version of the vehicle controller can be verified, thereby reducing the frequency of vehicle failures caused by incorrect installation of the controller software version, and ensuring normal production in the workshop. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 It is a structural schematic diagram of a software version checking device for a vehicle controller provided by an embodiment of the present invention;

[0034] Figure 2 is a flow chart of a software version verification method for a vehicle controller provided by an embodiment of the present invention;

[0035] Figure 3 It is a structural schematic diagram of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0036] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0037] The terms used in the embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit the present application. The singular forms "a", "said" and "the" used in the embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings, and "multiple" generally includes at least two.

[0038] It should be understood that the term "and / or" used in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0039] It should be understood that although the terms first, second, third, etc. may be used to describe in the embodiments of the present application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, without departing from the scope of the embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.

[0040] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0041] It should also be noted that the term "includes", "comprising" or any other variation thereof is intended to cover non-exclusive inclusion, so that a commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprising a ..." do not exclude the existence of other identical elements in the commodity or device including the elements.

[0042] It should be particularly noted that any symbols and / or numbers in the specification that are not marked in the accompanying drawings are not drawing marks.

[0043] Figure 1 This is a schematic diagram of the structure of a vehicle controller software version verification device provided by an embodiment of the present invention. This embodiment is at least applicable to vehicle controller software version verification scenarios of various types of vehicles during the offline test phase, such as fuel vehicles, pure electric vehicles, hybrid vehicles, plug-in hybrid vehicles, extended-range electric vehicles, driverless vehicles, etc. The software version verification device can be implemented in software and / or hardware. Figure 1 As shown, the software version checking device 100 at least includes a design end 110, a supply end 120, a manufacturing operation management (MOM) module 130, a product data management (PDM) module 140 and an end of line (EOL) management module 150.

[0044] The design end 110 is respectively connected to the PDM module 140 and the EOL management module 150, and is used at least to upgrade the internal software and software version number of each type of design controller according to the vehicle control function requirements; and to maintain the upgraded software version numbers corresponding to each type of design controller to the PDM module 140, and to update the upgraded internal software data corresponding to each type of design controller to the EOL management module 150.

[0045] The supply end 120 is at least used to upgrade the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements.

[0046] The MOM module 130 is connected to the EOL management module 150 and is at least used to pre-acquire the subsequent vehicle production plan and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module 150 .

[0047] The EOL management module 150 is connected to the PDM module 140 and the EOL test device 200, respectively, and is used at least to maintain the view table of the controller to be tested; and to generate a form of the controller to be tested according to the planned production BOM information and the maintained view table of the controller to be tested, and to retrieve the software version number of the controller to be tested in the PDM module 140 according to the form of the controller to be tested, so as to achieve the matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; and, to cooperate with the EOL test device 200 to perform software version verification on the controller to be tested.

[0048] The controller to be tested is a design controller, an inventory controller or a production line controller.

[0049] It can be seen that the design end 110 may refer to the software and / or hardware platform used and maintained by the designers of the vehicle controller; the supply end 120 may refer to the software and / or hardware platform used and maintained by the suppliers, manufacturers, etc. of the vehicle controller; the MOM module 130 may refer to an operation management system of the vehicle manufacturing industry, which aims to improve vehicle production efficiency, reduce operation and management costs, and optimize the entire vehicle production process; the PDM module 140 may refer to a product data management system of the vehicle manufacturing industry; the EOL management module 150 may refer to a vehicle production line off-line management system of the vehicle manufacturing industry.

[0050] It is understandable that the design controller may refer to the vehicle controller that the designer is responsible for maintaining and upgrading, the inventory controller may refer to the vehicle controller that has been produced and stored in the warehouse, etc., and the production line controller may refer to the vehicle controller that is located on the production line and is being produced. In addition, the internal software data may refer to the internal software program of the vehicle controller; the software version number may be adaptively selected by the designer, supplier, etc. according to the number of iterations of the software program inside the vehicle controller, for example, it may be "V1.0", "V2.0", etc.

[0051] In a specific implementation, the MOM module 130 can obtain the subsequent vehicle production plan three days in advance. The supply side can upgrade the internal software program and software version number of the corresponding type of inventory controller and the internal software program and software version number of the corresponding type of production line controller according to the upgraded internal software program and software version number corresponding to each type of design controller.

[0052] For example, when the EOL management module 150 maintains the view table of the controller to be tested, the maintenance information may specifically be the first 7 digits of the part number of the controller to be tested (here, the design end 110 may define that the first 7 digits of the part number of the same controller to be tested are the same, and the corresponding OBD pins are also the same; it can be understood that the full name of OBD is On-Board Diagnostic); subsequently, the EOL management module 150 automatically generates a list of controllers to be tested for subsequent planned production models based on the planned production BOM information pushed by the MOM module 130 and the view table of the controller to be tested; subsequently, the EOL management module 150 can retrieve the software version number under the production attribute database with the part number of the controller to be tested from the PDM module 140 based on the list of controllers to be tested and the planned production BOM information corresponding to the specific controller to be tested; if an adapted software version number is retrieved, the controller to be tested, the software version number and the internal software data are correspondingly locked; if an adapted software version number is not retrieved, the EOL management module 150 can synchronously send an early warning message to the design end 110 and / or the supply end 120 to request the designer and / or supplier to perform maintenance on the controller to be tested.

[0053] The technical solution provided in this embodiment is as follows: first, the design end upgrades the internal software and software version number of each type of design controller according to the vehicle control function requirements; further, the design end maintains the upgraded software version number corresponding to each type of design controller to the PDM module, and updates the upgraded internal software data corresponding to each type of design controller to the EOL management module; further, the supply end upgrades the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements; further, the MOM module pre-acquires the subsequent vehicle production plan, and pushes the planned production bill of materials BOM information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module; further, the EOL management module maintains the view table of the controller to be tested; further, the EOL management module generates a form of the controller to be tested according to the planned production BOM information and the maintained view table of the controller to be tested, and retrieves the software version number of the controller to be tested in the PDM module according to the form of the controller to be tested, so as to achieve the matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; finally, the EOL management module cooperates with the EOL test equipment to perform software version verification on the controller to be tested. In view of this, this embodiment introduces an EOL management module that spans the design, supply, production and testing links of the vehicle controller. By connecting the EOL management module to the design end, MOM module, PDM module and EOL testing equipment, the software version of the vehicle controller can be verified, reducing the frequency of vehicle failures caused by incorrect installation of the controller software version, which is conducive to ensuring normal production in the workshop.

[0054] It should be noted that the inventor has seen the prior art solution of saving the software and hardware versions of the controller to the Manufacturing Execution System (MES), but this solution process has certain problems. Specifically, since the MES system is production-oriented, and the software version upgrade of the controller is initiated by R&D design, the MES system is directly connected with the EBOM (Engineering BOM) system to identify the software version of the production line controller, which makes it difficult to ensure the flexibility and compatibility of design and production.

[0055] It should also be noted that the software version verification device proposed in the present invention can also be used to perform software version verification on corresponding controllers and other equipment with test equipment unique to other application scenarios, such as airplanes, ships, etc., which will not be repeated here.

[0056] Based on the above embodiments or implementations, the specific working principle of how the EOL management module cooperates with the EOL test equipment to perform software version verification on the controller under test, the design end and the supply end, etc. is described below, but it is not intended to limit the present invention. In a specific implementation, the EOL management module can optionally cooperate with the EOL test equipment to perform software version verification on the controller under test in at least the following ways:

[0057] After the EOL test equipment is connected to the current vehicle to be tested through the OBD port of the vehicle diagnostic system by the operator, the EOL test equipment scans the current vehicle to be tested to obtain the controller list corresponding to the current vehicle to be tested and the software version numbers corresponding to various controllers to be tested in the current vehicle to be tested from the EOL management module;

[0058] The EOL test equipment reads the preset address parameters of each controller to be tested in the current vehicle to be tested through the diagnostic instruction, so as to generate a software version verification result based on the preset address parameters of each controller to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module;

[0059] The EOL test equipment transmits the software version verification results back to the EOL management module for retention, so that the software version verification results of any vehicle under test can be traced back later.

[0060] The above-mentioned coordinated cooperation process between the EOL management module and the EOL test equipment may occur after the vehicle arrives at the comparison station.

[0061] Exemplarily, the coordination process between the EOL management module and the EOL test equipment may be specifically as follows:

[0062] (1) The EOL test equipment scans the chassis number of the current vehicle to be tested to obtain the controller list corresponding to the current vehicle to be tested and the software version number corresponding to each controller to be tested in the current vehicle to be tested from the EOL management module.

[0063] (2) The EOL test equipment reads the parameters in the F195 address of each controller under test in the current vehicle under test through the diagnostic 2E instruction; after reading the parameters, the EOL test equipment can compare the read controller software version number with the software version number retrieved from the PDM module by the EOL management module. If the comparison is consistent, the EOL test equipment will display a qualified result (that is, if the preset address parameters of each controller under test and the software version number of the corresponding type of vehicle controller in the EOL management module are consistent, the EOL test equipment will display the software version verification result as qualified).

[0064] Specifically, the diagnostic sequence between the EOL test equipment and the vehicle under test can be:

[0065] (2.1) Enter the default session mode:

[0066] The EOL test equipment sends: 10 01 00 00 00;

[0067] The controller under test replies: 50 01 00 00 00.

[0068] (2.2) Read configuration information:

[0069] The EOL test equipment sends: 22F1 90 00 00 00;

[0070] The controller under test replies: 62F1 90XX XX XX (here "XX XX XX" is the software version number of a controller under test in the current vehicle under test).

[0071] (2.3) Configuration information comparison successful.

[0072] (3) If the comparison is inconsistent, the EOL test device will display an error message and initiate a full data flash on the corresponding vehicle controller based on the software version number and internal software program that the EOL management module can obtain to ensure the consistency of the software version (that is, if the preset address parameters of at least one controller to be tested are inconsistent with the software version number of the corresponding type of vehicle controller in the EOL management module, the EOL test device will display the software version verification result as an error, and then execute a full data flash on the corresponding controller to be tested based on the software version number and internal software data that the EOL management module can obtain).

[0073] Specifically, the diagnostic sequence between the EOL test equipment and the controller under test on which the full data flash is performed can be:

[0074] (3.1) Enter the default session mode:

[0075] The EOL test equipment sends: 10 01 00 00 00;

[0076] The controller under test replies: 50 01 00 00 00.

[0077] (3.2) Read configuration information:

[0078] The EOL test equipment sends: 22F1 90 00 00 00;

[0079] The controller under test replies: 62F1 90XX XX XX (here "XX XX XX" is the software version number of a controller under test in the current vehicle under test).

[0080] (3.3) Configuration information comparison failed.

[0081] (3.4) Change the session mode:

[0082] The EOL test equipment sends: 10 02 00 00 00;

[0083] The controller under test replies: 50 02 00 00 00.

[0084] (3.5) Secure Access:

[0085] EOL test equipment sent to: 27 01.

[0086] (3.6) Software version number writing:

[0087] The EOL test equipment sends: 2E F1 90XX XX XX (where "XX XX XX" is the software version number of a controller under test in the current vehicle under test after the change);

[0088] The controller under test replies: 6E F1 90 00 00 00.

[0089] (3.7) Data writing.

[0090] In another specific implementation, optionally, the design end is specifically used to define the software version number of each type of design controller according to the vehicle control function requirements, and maintain the upgraded software version number corresponding to each type of design controller in the production attribute unit of the controller part drawing number under the PDM module (i.e., the aforementioned production attribute database with the part number of the controller to be tested); and, upgrade the internal software of each type of design controller according to the vehicle control function requirements, and update the upgraded internal software data corresponding to each type of design controller to the EOL management module.

[0091] Among them, the vehicle control function requirements can be adaptively configured according to the customer's actual vehicle usage, and the present invention is not limited to this.

[0092] In another specific embodiment, optionally, the supply side is specifically used to upgrade the internal software of the inventory controller and the production line controller according to the vehicle control function requirements, and write the upgraded software version number as a preset address parameter into the preset address of the inventory controller or the production line controller through a preset protocol.

[0093] Among them, the preset protocol method can be a diagnostic protocol data identifier (Data Identifier, DID) method; the preset address can be the aforementioned F195 address. Of course, this address can be standardized with all vehicle controller manufacturers in advance to standardize the development of diagnostic processes.

[0094] In another specific embodiment, optionally, if the software version verification device needs to modify the software version number of at least one type of controller to be tested, but the EOL management module has generated a controller to be tested form, then the EOL management module is at least further used to batch modify the software version number of at least one type of controller to be tested through the controller to be tested form.

[0095] Among them, this implementation involves error correction on the design side and software version number maintenance errors, and is applicable to the scenario where the EOL management module has generated a form for the controller to be tested. At this time, after the software version number is modified on the design side and uploaded to the PDM module for storage, if the EOL management module accesses the PDM module again to achieve software version number matching for each controller to be tested, it is easy to cause frequent data access, and the EOL management module also needs a certain amount of time to regenerate the form for the controller to be tested, which will affect the production line judgment. In view of this, this implementation can make batch changes to the form of the controller to be tested in the EOL management module, which can not only effectively avoid the limitation of frequent access between modules, but also prevent batch error problems during production.

[0096] In another specific embodiment, optionally, if the design end subsequently updates the internal software and software version number of any type of design controller, the EOL management module is at least used to maintain the internal software data of the corresponding type of controller under test, and the PDM module is at least used to modify the software version number of the corresponding type of controller under test.

[0097] Among them, after the design end updates the function of the vehicle controller and synchronously maintains the software version number of the design controller, the PDM module maintains the upgraded software version number, and the software data of the corresponding vehicle model in the EOL management module also needs to be maintained accordingly.

[0098] It is understandable that this implementation can solve the problem of incorrect version supply of small batch vehicle controllers. Of course, if a controller software version error occurs and causes full data flashing, the EOL management module can issue an early warning for process personnel to query; if such problems occur frequently, it is necessary to contact the supplier to check the inventory and make batch rectifications to avoid affecting the flashing rhythm of the production line.

[0099] An embodiment of the present invention also provides a software version verification method for a vehicle controller. Figure 2This is a flow chart of a vehicle controller software version verification method provided by an embodiment of the present invention. This embodiment is at least applicable to vehicle controller software version verification scenarios of various types of vehicles during the offline test phase, such as fuel vehicles, pure electric vehicles, hybrid vehicles, plug-in hybrid vehicles, extended-range electric vehicles, driverless vehicles, etc. The software version verification method can be, but is not limited to, executed by the software version verification device in the embodiment of the present invention as the execution subject, and the execution subject can be implemented in software and / or hardware. Figure 2 As shown, the software version verification method includes at least the following specific steps:

[0100] S1. Upgrade the internal software and software version number of each type of design controller according to the vehicle control function requirements through the design end;

[0101] S2. Maintain the upgraded software version numbers corresponding to various design controllers to the PDM module through the design end, and update the upgraded internal software data corresponding to various design controllers to the EOL management module;

[0102] S3. Upgrade the internal software and software version number of the inventory controller and production line controller according to the vehicle control function requirements through the supply side;

[0103] S4. Obtain the subsequent vehicle production plan in advance through the MOM module, and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module;

[0104] S5. Maintaining the view table of the controller to be tested through the EOL management module;

[0105] S6. Generate a controller form to be tested according to the planned production BOM information and the maintained controller view table through the EOL management module, and retrieve the software version number of the controller to be tested in the PDM module according to the controller form to achieve software version number matching of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data;

[0106] S7. Use the EOL management module to cooperate with the EOL test equipment to perform software version verification on the controller to be tested;

[0107] The controller to be tested is a design controller, an inventory controller or a production line controller.

[0108] Optionally, step S7 at least specifically includes the following steps:

[0109] (7-1) After the EOL test device is connected to the current vehicle to be tested through the OBD port of the vehicle diagnostic system by the operator, the current vehicle to be tested is scanned by the EOL test device to obtain the controller list corresponding to the current vehicle to be tested and the software version numbers corresponding to various controllers to be tested in the current vehicle to be tested from the EOL management module;

[0110] (7-2) using the EOL test equipment to read the preset address parameters of each controller under test in the current vehicle under test through diagnostic instructions, so as to generate a software version verification result based on the preset address parameters of each controller under test and the software version number of the corresponding type of vehicle controller in the EOL management module;

[0111] (7-3) The software version verification result is transmitted back to the EOL management module through the EOL test equipment for retention, so as to trace the software version verification result of any vehicle to be tested later.

[0112] Optionally, step S7 at least further includes:

[0113] (7-4) If the preset address parameters of each controller to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module are consistent, the software version verification result displayed by the EOL test equipment is qualified;

[0114] (7-5) If the preset address parameters of at least one controller to be tested are not consistent with the software version number of the corresponding type of vehicle controller in the EOL management module, the software version verification result is displayed as an error by the EOL test equipment, and then the corresponding controller to be tested is fully flashed according to the software version number and internal software data that can be obtained by the EOL management module.

[0115] Optionally, step S1 and step S2 are at least specifically:

[0116] (1-1) The design end defines the software version number of each type of design controller according to the vehicle control function requirements, and maintains the upgraded software version number corresponding to each type of design controller in the production attribute unit of the controller part drawing number under the PDM module;

[0117] (1-2) The design end upgrades the internal software of each type of design controller according to the vehicle control function requirements, and updates the upgraded internal software data corresponding to each type of design controller to the EOL management module.

[0118] Optionally, step S3 at least specifically includes:

[0119] The supply side is used to upgrade the internal software of the inventory controller and the production line controller according to the vehicle control function requirements, and the upgraded software version number is written into the preset address of the inventory controller or the production line controller as the preset address parameter through the preset protocol.

[0120] Optionally, the software version verification method further includes at least:

[0121] (8-1) If the software version verification device needs to modify the software version number of at least one type of controller under test, but the EOL management module has generated a controller under test form, the EOL management module is used to batch modify the software version number of at least one type of controller under test through the controller under test form.

[0122] Optionally, the software version verification method further includes at least:

[0123] (8-2) If the design end subsequently updates the internal software and software version number of any type of design controller, the internal software data of the corresponding type of controller under test is maintained through the EOL management module, and the software version number of the corresponding type of controller under test is modified using the PDM module.

[0124] The technical solution provided in this embodiment firstly upgrades the internal software and software version number of each type of design controller according to the vehicle control function requirements through the design end; further, the software version number corresponding to each type of design controller after the upgrade is maintained in the PDM module through the design end, and the internal software data corresponding to each type of design controller after the upgrade is updated to the EOL management module; further, the internal software and software version number of the inventory controller and the production line controller are upgraded according to the vehicle control function requirements through the supply end; further, the subsequent vehicle production plan is obtained in advance through the MOM module, and the subsequent vehicle production plan involves at least The planned production bill of materials (BOM) information of a vehicle model is pushed to an EOL management module; further, the view table of the controller to be tested is maintained through the EOL management module; further, a form of the controller to be tested is generated through the EOL management module according to the planned production BOM information and the maintained view table of the controller to be tested, and the software version number of the controller to be tested is retrieved in the PDM module according to the form of the controller to be tested, so as to match the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; finally, the EOL management module cooperates with the EOL test equipment to perform software version verification on the controller to be tested. In view of this, the present embodiment introduces an EOL management module that spans the design, supply, production and testing links of the vehicle controller. By connecting the EOL management module to the design end, the MOM module, the PDM module and the EOL test equipment, the software version verification of the vehicle controller can be realized, and the frequency of vehicle failures caused by the wrong installation of the controller software version can be reduced, which is conducive to ensuring the normal production of the workshop.

[0125] An embodiment of the present invention further provides an electronic device, Figure 3 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention, see Figure 3, the electronic device 1000 includes a processor 1001 and a memory 1002, the memory 1002 stores computer-readable instructions, and when the computer-readable instructions are executed by the processor 1001, the steps in any one of the above software version verification methods are executed. Through the above technical solution, the processor 1001 and the memory 1002 are interconnected and communicate with each other through a communication bus and / or other forms of connection mechanisms (not marked), and the memory 1002 stores a computer program executable by the processor. When the electronic device 1000 is running, the processor 1001 executes the computer program to execute the software version verification method in any optional implementation method of the above embodiment to achieve at least the following functions: the internal software and software version number of each type of design controller are upgraded according to the vehicle control function requirements by the design end; the upgraded software version numbers corresponding to various types of design controllers are maintained to the PDM module by the design end, and the upgraded internal software data corresponding to various types of design controllers are updated to the EOL management module; the supply end is based on the vehicle control function requirements Request to upgrade the internal software and software version number of the inventory controller and production line controller; obtain the subsequent vehicle production plan in advance through the MOM module, and push the planned production material list BOM information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module; maintain the view table of the controller to be tested through the EOL management module; generate the controller to be tested form according to the planned production BOM information and the maintained controller to be tested view table through the EOL management module, and retrieve the software version number of the controller to be tested in the PDM module based on the controller to be tested form to achieve software version number matching of each controller to be tested, thereby correspondingly locking the controller to be tested, software version number and internal software data; perform software version verification on the controller to be tested in cooperation with the EOL test equipment through the EOL management module.

[0126] The embodiment of the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the software version verification method provided by all the embodiments of the present invention: the design end upgrades the internal software and software version number of each type of design controller according to the vehicle control function requirements; the design end maintains the upgraded software version number corresponding to each type of design controller to the PDM module, and updates the upgraded internal software data corresponding to each type of design controller to the EOL management module; the supply end upgrades the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements; the MOM module pre-acquires the subsequent The vehicle production plan is implemented, and the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan is pushed to the EOL management module; the view table of the controller to be tested is maintained through the EOL management module; the controller to be tested form is generated through the EOL management module according to the planned production BOM information and the maintained view table of the controller to be tested, and the software version number of the controller to be tested is retrieved in the PDM module according to the controller to be tested form to achieve software version number matching of each controller to be tested, thereby correspondingly locking the controller to be tested, software version number and internal software data; the software version verification of the controller to be tested is performed on the controller to be tested in cooperation with the EOL test equipment through the EOL management module.

[0127] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (a non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this document, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or device.

[0128] Computer-readable signal media may include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0129] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0130] Computer program code for performing the operations of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A software version checking device for a vehicle controller, characterized in that: At least including the design side, supply side, manufacturing operation management MOM module, product data management PDM module and end-of-line EOL management module; The design end is connected to the PDM module and the EOL management module respectively, and is used to at least upgrade the internal software and software version number of each type of design controller according to the vehicle control function requirements; and maintain the upgraded software version number corresponding to each type of design controller to the PDM module, and update the upgraded internal software data corresponding to each type of design controller to the EOL management module; The supply end is at least used to upgrade the internal software and software version number of the inventory controller and the production line controller according to the vehicle control function requirements; The MOM module is connected to the EOL management module and is at least used to pre-acquire a subsequent vehicle production plan and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module; The EOL management module is connected to the PDM module and the EOL test equipment respectively, and is at least used to maintain the view table of the controller to be tested; And, generating a controller to be tested form according to the planned production BOM information and the maintained controller to be tested view table, and retrieving the software version number of the controller to be tested in the PDM module according to the controller to be tested form, so as to achieve the matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; and, cooperating with the EOL test equipment to perform software version verification on the controller to be tested; Wherein, the controller to be tested is the design controller, the inventory controller or the production line controller.

2. The software version checking device according to claim 1, characterized in that: The EOL management module cooperates with the EOL test device to perform software version verification on the controller to be tested in at least the following manner: After the EOL test device is connected to the current vehicle to be tested through the OBD port of the on-board diagnostic system by the operator, the EOL test device scans the current vehicle to be tested to obtain the controller list to be tested corresponding to the current vehicle to be tested and the software version number corresponding to each type of the controller to be tested in the current vehicle to be tested from the EOL management module; The EOL test device reads the preset address parameters of each of the controllers to be tested in the current vehicle to be tested through a diagnostic instruction, so as to generate a software version verification result based on the preset address parameters of each of the controllers to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module; The EOL test equipment transmits the software version verification result back to the EOL management module for storage, so as to trace back the software version verification result of any vehicle to be tested later.

3. The software version checking device according to claim 2, characterized in that: If the preset address parameters of each of the controllers to be tested and the software version number of the corresponding type of vehicle controller in the EOL management module are consistent, the EOL test device displays that the software version verification result is qualified; If the preset address parameters of at least one of the controllers to be tested are not consistent with the software version number of the corresponding type of vehicle controller in the EOL management module, the EOL testing device will display the software version verification result as an error, and then perform a full data flash on the corresponding controller to be tested based on the software version number and internal software data that can be obtained by the EOL management module.

4. The software version checking device according to claim 1, characterized in that: The design end is specifically used to define the software version number of each type of the design controller according to the vehicle control function requirements, and maintain the upgraded software version number corresponding to each type of design controller in the production attribute unit of the controller part drawing number under the PDM module; And, the internal software of each type of the design controller is upgraded according to the vehicle control function requirements, and the upgraded internal software data corresponding to each type of design controller is updated to the EOL management module.

5. The software version checking device according to claim 1, characterized in that: The supply end is specifically used to upgrade the internal software of the inventory controller and the production line controller according to the vehicle control function requirements, and write the upgraded software version number as a preset address parameter into the preset address of the inventory controller or the production line controller through a preset protocol.

6. The software version checking device according to claim 1, characterized in that: If the software version verification device needs to modify the software version number of at least one type of the controller under test, but the EOL management module has generated the controller under test form, then the EOL management module is at least further used to batch modify the software version number of at least one type of the controller under test through the controller under test form.

7. The software version checking device according to claim 1, characterized in that: If the design end subsequently updates the internal software and software version number of any type of the designed controller, the EOL management module is at least used to maintain the internal software data of the corresponding type of the controller under test, and the PDM module is at least used to modify the software version number of the corresponding type of the controller under test.

8. A method for checking the software version of a vehicle controller, characterized in that: The method is performed by using the software version checking device according to claim 1, and the method at least comprises: Upgrading the internal software and software version number of each type of design controller according to the vehicle control function requirements through the design end; Maintaining the upgraded software version numbers corresponding to various design controllers to the PDM module through the design end, and updating the upgraded internal software data corresponding to various design controllers to the EOL management module; Upgrading the internal software and software version numbers of the inventory controller and the production line controller according to the vehicle control function requirements through the supply side; Pre-acquire the subsequent vehicle production plan through the MOM module, and push the planned production bill of materials (BOM) information of at least one vehicle model involved in the subsequent vehicle production plan to the EOL management module; Maintaining the controller view table to be tested by the EOL management module; Generate a controller to be tested form according to the planned production BOM information and the maintained controller to be tested view table through the EOL management module, and retrieve the software version number of the controller to be tested in the PDM module according to the controller to be tested form to achieve matching of the software version number of each controller to be tested, thereby correspondingly locking the controller to be tested, the software version number and the internal software data; Performing software version verification on the controller to be tested by cooperating with the EOL test equipment through the EOL management module; Wherein, the controller to be tested is the design controller, the inventory controller or the production line controller.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program that can be run on the processor, characterized in that: When the processor executes the program, the steps in the software version verification method of claim 8 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps in the software version verification method of claim 8 are implemented.

Images