Automobile controller software version automatic inspection and calibration method and system and storage medium

Abstract

The invention discloses an automatic verification and calibration method and system for an automobile controller software version and a storage medium, and relates to the technical field of automobile software verification. The method comprises the following specific steps: confirming controller label information, software version information and calibration information; storing the controller label information, the software version information and the calibration information in a configuration file of an upper computer; configuring software connection parameters of the upper computer, and connecting the upper computer with the controller; inputting controller bar code information into the upper computer and carrying out automatic verification, and if verification is correct, carrying out controller software version automatic verification and controller automatic calibration; and recording a verification result and a calibration result of the controller software version. The method is not only suitable for verification of the single-node controller software version on the whole vehicle, but also suitable for verification of the unloaded electronic control software version, has general practicability, and improves the software version verification efficiency and accuracy.

Description

Technical Field

[0001] This invention relates to the field of automotive software verification technology, and in particular to an automatic verification and calibration method, system, and storage medium for automotive controller software versions. Background Technology

[0002] With the rapid development of new energy vehicles and the accelerated pace of software iteration, controller software updates and upgrades are becoming increasingly frequent, placing higher demands on controller software version control. To reduce development costs and improve efficiency, controller development is gradually becoming platform-based. The same controller software can be matched to different platform models by switching different calibration parameters. Currently, controller software versions and calibration parameters are typically controlled at the source of controller production, by suppliers at the EOL (End-of-Life) testing station in the factory. However, this method cannot meet the software version verification and calibration requirements after successful production and delivery to customers, including software upgrades and reuse of old components (updating software, switching different calibration parameters). Furthermore, current controller software version number control relies solely on the software number. When software changes or upgrades occur, if engineers fail to update the corresponding software number in the software program in a timely manner, the compared software version numbers may match, but the actual internal software program of the controller may be inconsistent, leading to uncontrolled software versions and affecting the assembly of customer assemblies / vehicles.

[0003] For controllers that have been successfully manufactured and shipped to customers, and have undergone software upgrades and reuse of old components (updating software and switching different calibration parameters), the supplier's after-sales personnel typically use specialized tools to upgrade the software and modify the calibration parameters. However, they do not verify or record the controller software version, which can lead to issues such as missing or incorrect software updates, or even the risk of accidentally updating to the wrong software version or modifying calibration parameters. This could result in controller malfunction, performance degradation of the assembly / vehicle, and regulatory violations. Therefore, for those skilled in the art, how to achieve automatic verification and calibration of automotive controller software versions is a pressing issue that needs to be addressed. Summary of the Invention

[0004] The purpose of this invention is to provide an automatic verification and calibration method, system, and storage medium for automotive controller software versions, in order to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following solution: On one hand, it provides an automatic verification and calibration method for automotive controller software versions, the specific steps of which include the following: Confirm the controller label information, software version information, and calibration information; The controller tag information, the software version information, and the calibration information are uploaded to the host computer and automatically saved to the host computer's configuration file. Configure the host computer software connection parameters and establish communication with the controller; Input the controller barcode information into the host computer and perform automatic verification. If the verification is correct, perform automatic verification of the controller software version and automatic calibration of the controller. The results of controller software version verification and calibration are automatically recorded.

[0006] Preferably, the controller label information includes the manufacturer, project description, customer part number, product name, product model, hardware version, and software version; the software version information includes a CRC32 checksum, ECU software number, and software version number.

[0007] Preferably, the host computer software connection parameters include device model, channel, baud rate, client, and controller type.

[0008] Preferably, the controller label barcode is scanned by a barcode scanner or the controller barcode information is manually entered into the host computer, and the host computer verifies the customer part number and barcode length of the controller barcode information.

[0009] Preferably, the specific steps for automatic verification of the controller software version are as follows: The host computer sends the DID data command to the controller to read the CRC32 check code, the DID data command to read the ECU software number, and the DID data command to read the software version number; The controller receives instructions and sends back to the host computer the original data stream of CRC32 check code DID, the original data stream of ECU software number DID, and the original data stream of software version number DID. The host computer processes the raw data stream to obtain the CRC32 checksum, ECU software number, and software version number. The CRC32 checksum reading value, the ECU software number reading value, and the software version number reading value are compared with the CRC32 checksum setting value, the ECU software number setting value, and the software version number setting value, respectively. Based on the comparison results, different colored text box backgrounds are displayed on the host computer.

[0010] Preferably, the specific steps for the automatic calibration of the controller are as follows: Determine whether calibration is required. If so, the host computer reads the actual SOC value and determines whether the actual SOC value before calibration meets the preset threshold. If it does not meet the threshold, SOC calibration is performed. If it meets the threshold, recalibration is not required. The SOC calibration steps are as follows: the host computer automatically sends a real SOC value calibration command to calibrate the real SOC value to a preset threshold; the controller receives the calibration command and performs real SOC calibration according to the command, and feeds back the calibration result to the host computer.

[0011] On the other hand, an automatic verification and calibration system for automotive controller software version is provided. This system utilizes the aforementioned automatic verification and calibration method for automotive controller software version, and is applied to situations where the automotive controller is already installed in the vehicle. The system includes diagnostic equipment, a host computer, and an OBD port conversion harness. When the vehicle is powered on, the diagnostic device is connected to the vehicle's CAN bus through the OBD port conversion harness. The diagnostic device is also connected to the host computer for information exchange, enabling the verification of the controller software version and the switching of calibration parameters.

[0012] It also includes components for use when the vehicle controller is not installed in the vehicle, including diagnostic equipment, a host computer, a controller low-voltage wiring harness, and a 5V to 12V boost module; wherein, the 5V to 12V boost module is connected to the vehicle controller through the controller low-voltage wiring harness to provide power voltage to the vehicle controller; the vehicle controller is connected to the diagnostic equipment through a CAN bus, and the diagnostic equipment is connected to the host computer.

[0013] Finally, a computer storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the automatic verification and calibration method for the software version of an automotive controller.

[0014] According to specific embodiments provided by the present invention, the present invention discloses the following technical effects: It is applicable not only to the software version verification of single-node controllers on the whole vehicle, but also to the software version verification of electronic control software not installed on the vehicle. It has universal applicability and does not need to be verified in conjunction with other controllers, thus reducing the software development cost of the controller. Software version verification and calibration can be performed without an internet connection, reducing the cost of backend maintenance and management, covering more controller software version verification and calibration scenarios, and solving the problem of offline verification of controller software versions. The method does not rely on the joint software version verification of the vehicle's multi-node controller, that is, it does not rely on the vehicle control unit, battery management unit, integrated power unit or electric drive control unit. If any node is missing, the method of the present invention can still be used, which greatly improves the efficiency of software version verification. Automatic software version verification and calibration parameter switching reduce the risk of manual software version verification and improve the accuracy of automotive controller software version verification. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is a flowchart illustrating the overall method of the present invention; Figure 2 This is a flowchart of the automatic verification process for the controller software version of the present invention; Figure 3 This is a flowchart illustrating the interaction between the host computer and the controller in this invention. Figure 4 This is the automatic calibration process for the controller of the present invention; Figure 5 This is a structural diagram of the vehicle controller verification system of the present invention during vehicle installation; Figure 6 This is a structural diagram of the verification system for the vehicle controller of the present invention when it is not installed in the vehicle. Detailed Implementation

[0017] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0018] The purpose of this invention is to provide an automatic verification and calibration method for automotive controller software versions, such as... Figure 1 As shown, the specific steps include the following: S1. Confirm the controller label information, software version information, and calibration information; S2. Upload the controller tag information, software version information, and calibration information to the host computer. The information is automatically saved to the host computer's configuration file. S3. Configure the connection parameters of the host computer software and establish communication with the controller; S4. Input the controller barcode information into the host computer and perform automatic verification. If the verification is correct, perform automatic verification of the controller software version and automatic calibration of the controller. S5. Automatically record the controller software version verification results and calibration results.

[0019] Furthermore, in S1, the controller label information includes the manufacturer, project description, customer part number, product name, product model, hardware version, and software version; the software version information includes the CRC32 checksum, ECU software number, and software version number. The CRC32 checksum corresponding to the controller software version is confirmed using a CRC32 cyclic redundancy check algorithm. Whenever the controller software data or code changes, the controller recalculates the CRC32 code according to the CRC32 cyclic redundancy check algorithm and latches it into the relevant DID. This invention simultaneously verifies the CRC32 checksum and the software version number, improving the accuracy of software version verification.

[0020] Furthermore, the connection parameters in the S3 host computer software include device model, channel, baud rate, client, and controller type. Configuration is performed based on the actual connected hardware device, channel, baud rate, and controller. When the connection is successful after configuration, the device status displays: Connected; otherwise, the device status displays: Not Connected.

[0021] Furthermore, in S4, the controller label barcode is scanned by a barcode scanner or the controller barcode information is manually entered into the host computer. The host computer verifies the customer part number and barcode length of the controller barcode information. If the barcode information is verified to be correct, the software version is automatically verified and the calibration parameters are switched.

[0022] Furthermore, the automatic verification of the controller software version in S4 is implemented as follows: the host computer controls the CAN box to send a DID instruction to the controller to read the DID data stream. The CRC32 checksum, ECU software number, and software version number correspond to different DID data streams. When the controller software data or code is updated, the controller calculates and latches the data burned into the controller using the CRC32 checksum algorithm, thereby obtaining the CRC32 checksum and storing it in the corresponding DID (different controllers use different checksum algorithms, including but not limited to the CRC32 checksum algorithm). Whenever the controller software is upgraded, the value corresponding to the CRC32 checksum changes. Since the ECU software number and software version number need to be manually updated in the software program by developers, there is a risk that the ECU software number and software version number may not be updated. Therefore, this invention simultaneously verifies the CRC32 checksum, ECU software number, and software version number to ensure the accuracy of the controller software version. The flowchart of the automatic verification of the controller software version in this invention is as follows: Figure 2 As shown in the diagram, the interaction flow between the host computer and the controller is as follows: Figure 3 As shown.

[0023] The specific steps are as follows: S41. The host computer sends a command to the controller to read the DID data of the CRC32 checksum. S42. The controller receives the instruction and feeds back the original data stream of CRC32 check code DID to the host computer. S43. The host computer processes the received CRC32 checksum DID raw data stream to obtain the CRC32 checksum read value. S44. The host computer compares the CRC32 checksum reading value with the CRC32 checksum setting value, and displays different colored text box backgrounds in the host computer according to the comparison result. S45. The host computer sends a command to the controller to read the DID data of the ECU software number; S46. The controller receives the instruction and feeds back the ECU software number DID raw data stream to the host computer. S47. The host computer processes the received ECU software number DID raw data stream to obtain the ECU software number read value. S48. The host computer compares the ECU software number read value with the ECU software number set value, and displays text box backgrounds of different colors in the host computer according to the comparison result. S49. The host computer sends a DID data command to the controller to read the software version number; S410: The controller receives instructions and feeds back the software version number DID and raw data stream to the host computer. S411. The host computer processes the received raw data stream of the software version number DID to obtain the software version number read value. S412. The host computer compares the software version number reading value with the ECU software number setting value, and displays text box backgrounds of different colors in the host computer according to the comparison result. S413. If the CRC32 check flag, ECU software number, and software version number check flag are all correct, then the check is successful.

[0024] Furthermore, such as Figure 4 As shown, the specific steps for automatic controller calibration in S4 are as follows: Step 1: The host computer determines whether real SOC calibration is required based on the checkboxes. Step 2: If real SOC calibration is to be performed, the host computer will automatically send a command to read real SOC data, the controller will feed back the real SOC DID raw data stream, and the host computer will process the received real SOC raw data to obtain the real SOC value before calibration. Step 3: The host computer determines whether the actual SOC value before calibration is equal to the preset threshold. In this embodiment, the preset threshold is set to 17%. If the actual SOC value before calibration is equal to 17%, recalibration is not required; if the actual SOC value before calibration is not equal to 17%, actual SOC calibration is performed. Step 4: The host computer automatically sends a real SOC calibration command to calibrate the real SOC to 17%. If the controller responds according to the calibration command, the real SOC calibration is considered successful; otherwise, the real SOC calibration is considered to have failed.

[0025] Furthermore, the host computer automatically records the controller information (such as manufacturer, project description, customer part number, product name, product model, hardware version, software version, label barcode), software version verification results (expected CRC32 checksum value, expected ECU software number value, expected software version number value, actual CRC32 checksum value, actual ECU software number value, actual software version number value, software verification result) and calibration results (true SOC before calibration, true SOC after calibration, calibration result) in a file.

[0026] On the other hand, an automatic verification and calibration system for automotive controller software version is provided, which uses an automatic verification and calibration method for automotive controller software version, and is applied to situations where the automotive controller has already been installed in the vehicle, such as... Figure 5 As shown, it includes diagnostic equipment, a host computer, and an OBD port conversion harness; among which, Once the vehicle is powered on, the diagnostic equipment connects to the vehicle's CAN bus via the OBD port conversion harness. The diagnostic equipment also connects to the host computer for information exchange, enabling verification of the controller software version and switching of calibration parameters. The diagnostic equipment is a CAN test device capable of sending diagnostic commands, such as the ZLG USBCANFD-200U, Canoe, or PCAN.

[0027] like Figure 6 As shown, it also includes components for use when the vehicle controller is not installed in the vehicle, including diagnostic equipment, a host computer, a controller low-voltage wiring harness, and a 5V to 12V boost module; wherein, the 5V to 12V boost module is connected to the vehicle controller through the controller low-voltage wiring harness to provide power voltage to the vehicle controller; the vehicle controller is connected to the diagnostic equipment through the CAN bus, and the diagnostic equipment is connected to the host computer.

[0028] Depending on whether the controller is installed in the vehicle, there are different systems. The difference in system composition is the power supply method. When the controller is installed in the vehicle, it is powered by the vehicle's battery. When the controller is not installed in the vehicle, it requires a separate power supply.

[0029] Finally, a computer storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of an automatic verification and calibration method for the software version of an automotive controller.

[0030] In summary, the automatic verification method and system for automotive controller software versions of the present invention achieves the following beneficial effects: It supports independent verification in non-vehicle environments (such as inventory controllers) and non-factory environments (such as after-sales service points), eliminating dependence on the vehicle assembly line (EOL station). This method can also be applied to controller / vehicle assembly EOL stations. It achieves a closed-loop version management system for the entire lifecycle of the controller, from production and warehousing to vehicle installation.

[0031] The single-node independent verification architecture eliminates the need to rely on a multi-controller network (such as VCU / BMS / IPU) within the vehicle. A single controller independently completes the verification, avoiding verification failures caused by missing nodes. This reduces development complexity and improves the verification success rate (it can still be used in fault scenarios).

[0032] 3. Offline operation without network connectivity. By eliminating network connection limitations and utilizing localized verification logic, it covers offline scenarios such as underground parking garages and remote areas, reducing backend maintenance costs.

[0033] 4. Automated Traceability System. Automatically generates the binding relationship between controllers and verification / calibration records, supporting local storage and optional synchronization to the MES system. Enables full lifecycle data traceability, improving regional collaboration efficiency.

[0034] 5. While automatically verifying the controller software version, the controller can also be automatically calibrated without requiring additional tools and software from the controller manufacturer, thus improving the utilization rate of old controller components.

[0035] This document uses specific examples to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. Furthermore, those skilled in the art will recognize that, based on the ideas of the present invention, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for automatically verifying and calibrating the software version of an automotive controller, characterized in that, The specific steps include the following: Confirm the controller label information, software version information, and calibration information; The controller tag information, the software version information, and the calibration information are uploaded to the host computer and automatically saved to the host computer's configuration file. Configure the host computer software connection parameters and establish communication with the controller; Input the controller barcode information into the host computer and perform automatic verification. If the verification is correct, perform automatic verification of the controller software version and automatic calibration of the controller. The results of controller software version verification and calibration are automatically recorded.

2. The method for automatic verification and calibration of automotive controller software version according to claim 1, characterized in that, The controller label information includes the manufacturer, project description, customer part number, product name, product model, hardware version, and software version; the software version information includes the CRC32 checksum, ECU software number, and software version number.

3. The method for automatic verification and calibration of automotive controller software version according to claim 1, characterized in that, The connection parameters of the host computer software include device model, channel, baud rate, client, and controller type.

4. The automatic verification and calibration method for automotive controller software version according to claim 1, characterized in that, The controller label barcode is scanned by a barcode scanner or the controller barcode information is manually entered into the host computer. The host computer then verifies the customer part number and barcode length of the controller barcode information.

5. The method for automatic verification and calibration of automotive controller software version according to claim 2, characterized in that, The specific steps for automatic verification of the controller software version are as follows: The host computer sends the DID data command to the controller to read the CRC32 check code, the DID data command to read the ECU software number, and the DID data command to read the software version number; The controller receives instructions and sends back to the host computer the original data stream of CRC32 check code DID, the original data stream of ECU software number DID, and the original data stream of software version number DID. The host computer processes the raw data stream to obtain the CRC32 checksum, ECU software number, and software version number. The CRC32 checksum reading value, the ECU software number reading value, and the software version number reading value are compared with the CRC32 checksum setting value, the ECU software number setting value, and the software version number setting value, respectively. Based on the comparison results, different colored text box backgrounds are displayed on the host computer.

6. The automatic verification and calibration method for automotive controller software version according to claim 1, characterized in that, The specific steps for the automatic calibration of the controller are as follows: Determine whether calibration is required. If so, the host computer reads the actual SOC value and determines whether the actual SOC value before calibration meets the preset threshold. If it does not meet the threshold, SOC calibration is performed. If it meets the threshold, recalibration is not required. The SOC calibration steps are as follows: the host computer automatically sends a real SOC value calibration command to calibrate the real SOC value to a preset threshold; the controller receives the calibration command and performs real SOC calibration according to the command, and feeds back the calibration result to the host computer.

7. An automatic verification and calibration system for automotive controller software versions, characterized in that, The calibration is performed using the automatic verification and calibration method for automotive controller software version as described in any one of claims 1-6, applicable to situations where the automotive controller is already installed in the vehicle, including diagnostic equipment, a host computer, and an OBD port conversion harness; wherein... When the vehicle is powered on, the diagnostic device is connected to the vehicle's CAN bus through the OBD port conversion harness. The diagnostic device is also connected to the host computer for information exchange, enabling the verification of the controller software version and the switching of calibration parameters.

8. An automatic verification and calibration system for automotive controller software versions, characterized in that, The calibration is performed using an automatic verification and calibration method for automotive controller software version as described in any one of claims 1-6, applicable to situations where the automotive controller is not installed in a vehicle. The method includes a diagnostic device, a host computer, a controller low-voltage wiring harness, and a 5V to 12V boost module. The 5V to 12V boost module is connected to the automotive controller via the controller low-voltage wiring harness to provide power to the automotive controller. The automotive controller is connected to the diagnostic device via a CAN bus, and the diagnostic device is connected to the host computer.

9. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the steps of an automatic verification and calibration method for an automotive controller software version as described in any one of claims 1-6.

Images