Control method and storage medium of peripheral devices when ECU application layer software is updated in batches

Abstract

The present invention provides a method and storage medium for controlling peripheral devices when ECU application layer software is updated in batches. The method comprises: when the application layer software is updated in batches, the control parameters of the peripheral devices corresponding thereto are identified by VIN codes; an OTA task list and a corresponding software upgrade package are configured; software version information of a target controller of each vehicle is obtained according to the VIN code; it is determined whether the software version information is the same as the version information of the software upgrade package, and when the information is different, the software upgrade package is sent to an OTA client; when the vehicle to be updated meets the OTA upgrade requirements, the control parameters of the vehicle to be updated are calibrated by the application layer software, and after the calibration is completed, the application layer software is updated by OTA, and at the same time, a Boot loader is used to replace the application layer software to control all hardware interfaces, the Boot loader reads and executes the control parameters corresponding to more than one peripheral device, and controls each peripheral device to run with the corresponding control parameters through the hardware interface.

Description

Technical Field

[0001] The present invention relates to the technical field of new energy vehicle control, and in particular to a control method and storage medium for peripheral devices when ECU application layer software is updated in batches. Background Art

[0002] With the promotion of OTA technology, the application layer software of multiple ECUs of the whole vehicle will be packaged together for OTA upgrade, which is a time-consuming method. During the OTA process, the vehicle is powered by a low-voltage lead-acid battery with a small capacity. The power consumption during the upgrade must be controllable and as low as possible, otherwise the lead-acid battery power supply is prone to upgrade failure, resulting in vehicle failure. For large OEMs, there are many models in mass production, each with different configurations, different models, and different configurations of the same model. Their peripheral devices are different, and the amount of control and management operations is large. Therefore, it is very necessary to perform batch operations on vehicles.

[0003] The peripheral devices controlled by each controller of new energy vehicles are divided into high and low level control, PWM duty cycle control and other methods. When updating the application layer software, the software will be erased first and then the new software will be written. During the process, the controller pin level will be high or low without application layer software. For some devices such as cooling fans and water pumps, level-type devices may have level enable, resulting in high-speed constant rotation, and PWM-type devices will have high-speed constant rotation with a duty cycle of 0 or 100%. At this time, the low-voltage energy consumption is very high. Summary of the invention

[0004] A major problem solved by the present invention is that when new energy vehicles update the application layer software in batches, the peripheral devices have problems of high energy consumption, high noise and large operation volume due to the lack of effective control. In addition, large OEMs have many models and configurations, resulting in obvious differences in peripheral devices, which further aggravates the aforementioned problems.

[0005] According to one aspect of the present invention, the present invention provides a method for controlling peripheral devices when ECU application layer software is updated in batches, comprising:

[0006] S1. When the application layer software is updated in batches, the control parameters of the peripheral devices corresponding to the VIN codes are identified through the VIN codes;

[0007] S2. Configure the OTA task list and the corresponding software upgrade package;

[0008] S3, obtaining version information of the target controller of each vehicle to be updated;

[0009] S4, determining whether the software version information of the target controller is the same as the version information of the software upgrade package, and when the two are different, sending the software upgrade package to the OTA client;

[0010] S5. When the vehicle to be updated meets the OTA upgrade requirements, calibrate the control parameters of the vehicle to be updated through the application layer software;

[0011] S6. After the calibration is completed, the application layer software is upgraded and updated by OTA. At the same time, the Boot loader is used to replace the application layer software to control all hardware interfaces. The Boot loader reads and executes the control parameters corresponding to more than one peripheral device, and controls each peripheral device to run with the corresponding control parameters through the hardware interface.

[0012] Furthermore, the control method further includes:

[0013] In step S5, when the vehicle to be updated does not meet the OTA upgrade requirements, steps S2-S4 are re-implemented until the vehicle to be updated meets the OTA upgrade requirements.

[0014] Furthermore, the control method further includes:

[0015] In step S4, when the version information of the target controller of any of the vehicles to be updated is the same as the version information of the software upgrade package, the vehicle to be updated is marked as successfully updated, and step S2 is re-implemented.

[0016] Furthermore, before the application layer software is updated in batches, control parameters of peripheral devices corresponding to the vehicle to be updated are defined according to the actual configuration of the vehicle and the device model.

[0017] Furthermore, before identifying the control parameters corresponding to the vehicle to be updated through the VIN code of the vehicle to be updated, the control parameters of the peripheral devices corresponding to the vehicle to be updated are customized.

[0018] Furthermore, the OTA upgrade requirement is to reach a preset upgrade time.

[0019] Furthermore, the control parameters defined according to the actual configuration and device model of the vehicle are linked to the vehicle VIN code.

[0020] Furthermore, before identifying the control parameters corresponding to the VIN code of the vehicle to be updated, the customized control parameters of the peripheral device are linked to the VIN code of the vehicle.

[0021] According to another aspect of the present invention, a storage medium is also disclosed, which is a computer-readable storage medium. An executable computer program is stored on the computer-readable storage medium. The executable computer program is used to execute the peripheral device control method when the ECU application layer software is batch updated as described in any of the above.

[0022] The present invention provides a method for controlling peripheral devices when the application layer software is updated, while ensuring the universality of the underlying software. The method can enable the device to work in a suitable low-power working condition. At the same time, the method is designed to automatically identify the vehicle model and the control parameters of the peripheral devices corresponding to the vehicle configuration according to the vehicle VIN number before OTA. At the same time, the host factory authority can manually select the peripheral device control parameters, and the parameters are written into the public data storage area through interaction with the application layer, so as to realize the management of differentiated peripheral devices when the vehicle application layer software is updated in batches. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

[0024] Figure 1 Schematic diagram of the control flow of peripheral devices during ECU OTA software calibration and upgrade in an embodiment of the present invention. DETAILED DESCRIPTION

[0025] Various exemplary embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present invention.

[0026] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0027] The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

[0028] In order to make the objectives, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with specific embodiments and with reference to the accompanying drawings.

[0029] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.

[0030] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0031] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0032] Embodiment 1, as Figure 1As shown, it is a schematic diagram of the control flow of peripheral devices during ECU OTA software calibration and upgrade in this embodiment. Before the vehicle leaves the factory, the control parameters of the peripheral devices are configured according to the device type, and the control parameters of the peripheral devices are linked to the VIN code of the vehicle to be updated, and then the application layer software starts batch updating;

[0033] S1. When the application layer software is updated in batches, the control parameters of the peripheral devices linked to the corresponding VIN codes are identified by the VIN codes of the vehicles to be updated; or before the application layer software is updated in batches, the control parameters of the peripheral devices of the vehicles to be updated can also be customized according to the vehicle device models and / or actual configurations.

[0034] S2. Configure the OTA task list and the corresponding software upgrade package (i.e., upgrade package);

[0035] S3, obtaining software version information of the target controller of each vehicle to be updated according to the VIN code;

[0036] S4. Determine whether the feedback version information of the target controller is the same as the version information of the upgrade package. If they are different, send the software upgrade package to OTA according to the VIN code. When the version information of the target controller of any vehicle to be updated is the same as the version information of the software upgrade package, mark the upgrade of the vehicle to be updated as successful, and re-implement step S2 to configure a new OTA task list and the corresponding software upgrade package.

[0037] S5. When the vehicle to be updated meets the OTA upgrade requirements, the control parameters of the peripheral devices of the vehicle to be updated are calibrated through the application layer software; when the vehicle to be updated does not meet the OTA upgrade requirements, steps S2-S4 are re-implemented until the vehicle to be updated meets the OTA upgrade requirements. The OTA upgrade requirement can be to reach a preset upgrade time.

[0038] S6. After the calibration is completed, the application layer software is upgraded and updated by OTA. At the same time, the Boot loader is used to replace the application layer software to control all hardware interfaces. The Boot loader reads and executes the control parameters corresponding to more than one peripheral device, and controls each peripheral device to run with the corresponding control parameters through the hardware interface, thereby achieving the purpose of batch controlling peripheral devices when the application layer software is updated in batches.

[0039] Preferably, the control parameters of the peripheral devices corresponding to the vehicle to be updated may also be customized before the VIN code of the vehicle to be updated is identified and the control parameters linked thereto are correspondingly identified.

[0040] In the second embodiment, the vehicle management system backend of the OEM for ECU OTA software calibration and upgrade can identify the vehicle model and actual configuration through the VIN code. Therefore, the vehicle management system of the OEM needs to first link vehicles of different models and configurations and the peripheral device control parameters of each controller corresponding to these vehicles.

[0041] After the parameter link configuration is completed, before the vehicle software is updated in batches through OTA, a round of calibration operation is performed first, that is, when configuring the upgrade package, the vehicle model and configuration are identified by the vehicle VIN code in the vehicle management system to link the corresponding peripheral device control parameters. The OEM authority can also manually select the control parameters of the peripheral devices. If no modification is required, the parameter setting step can be skipped and the software version instructions of each target controller can be directly obtained. After receiving the software version information feedback from each target controller, if the software version information of the software upgrade package is inconsistent with the software version information fed back by the target controller, the software upgrade package can be sent normally afterwards.

[0042] When the preset upgrade time arrives, the OTA system first sends an upgrade status detection command to detect the vehicle status. When the vehicle feedback meets the upgrade status requirements, the controller peripheral device control parameters are calibrated first. After receiving the feedback information of the calibration completion, the OTA upgrade command is issued to update the controller application layer software. If the vehicle feedback does not meet the upgrade requirements, no calibration is performed and no OTA software update is performed.

[0043] In the previous step, when the calibration status is fed back, the value in the storage address is not checked, and the calibration is completed after the process is completed. Since OTA will judge the power gear, vehicle gear and torque and other conditions, the conditions are generally strict, so the calibration will not fail when the OTA judgment conditions are met. If the calibration fails, the OTA judgment conditions will basically not be met, and the OTA process will be exited immediately.

[0044] The calibrated control parameters of the peripheral devices are stored in the public data storage area by the application layer software, and all control parameters are backed up. The storage address area of ​​the calibrated control parameters and the storage address area of ​​the backup control parameters should be selected as far apart as possible, because the damage of the storage address is mostly continuous, so this can avoid the damage of two sets of storage addresses at the same time.

[0045] The control parameters of the peripheral devices can be determined by different ECUs, and need to be agreed upon in advance by both the application layer software and the bootloader software developers. For example, the control parameters of the vehicle controller ECU include device control type, effective level, PWM frequency, PWM duty cycle, checksum, etc.

[0046] When the application layer software is updated, the software will run and jump to the Bootloader software. The Bootloader reads the device control type, effective level, PWM frequency, PWM duty cycle, check code and other control parameters from the public data area. The parameter verification module performs parameter verification of the calibrated control parameters. The verification algorithm is defined by the OEM according to the enterprise standard. After the verification is passed, the device control with demand control is carried out.

[0047] During the aforementioned parameter verification process, when the parameter fails to pass the verification, the backup control parameter is verified. When the verification passes, the Bootloader uses the backup control parameter to control the peripheral device and outputs the corresponding electrical level and duty cycle. The Bootloader reads and executes the control parameters corresponding to more than one peripheral device that has passed the verification, and controls each peripheral device to run with the corresponding control parameters through the hardware interface, thereby batch controlling the peripheral devices when the application layer software is batch updated.

[0048] If both sets of parameters fail the verification, the control is performed according to the backup control parameters. The specific control steps are as follows: when the application layer software is updated, the Boot loader reads and executes the control parameters corresponding to more than one peripheral device that has passed the verification, and controls each peripheral device to run with the corresponding control parameters through the hardware interface. Because when the verification fails, it does not mean that all control parameters are wrong, and some control parameters can still be used to control the corresponding peripheral devices to work normally. At this time, it is also necessary to store fault information in the storage address pre-agreed with the application layer software, which is used to display the fault code after the program update is completed (the fault code can only be sent through the diagnostic protocol when the application layer software is running, but the fault Bootloader in the storage space can be stored first).

[0049] When the application layer software is updated, the software jumps to run the new application layer software, and the peripheral devices resume control of the application layer software. During operation, the application layer software will periodically detect whether at least one of the acquired control parameters of the peripheral controller and the backed-up control parameters can be successfully verified. Otherwise, the fault information will be stored in the storage address agreed with the application layer software to display the fault code and remind customers and staff.

[0050] The steps for displaying the fault code are as follows: when the application layer software is running, the fault code and VIN code will be bound together through the communication protocol and sent together to the vehicle management system. The vehicle management system will mark the vehicle as faulty based on the received fault code and VIN code.

[0051] In this embodiment, the vehicle management system updates the database through networking to update its own control parameters.

[0052] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

[0053] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, 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 process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

Claims

1. A method for controlling peripheral devices when ECU application layer software is updated in batches, characterized in that: The control method comprises: S1. Identifying the control parameters of the peripheral device corresponding to the VIN code of the vehicle to be updated through the VIN code; S2. Configure the OTA task list and the corresponding software upgrade package; S3, obtaining software version information of the target controller of each vehicle to be updated; S4, determining whether the software version information of the target controller is the same as the version information of the software upgrade package, and when the two are different, sending the software upgrade package to the OTA client according to the VIN code; when the software version information of the target controller of any of the vehicles to be updated is the same as the version information of the software upgrade package, marking the vehicle to be updated as successfully updated, and re-implementing step S2 to configure a new OTA task list and the corresponding software upgrade package; S5. When the vehicle to be updated does not meet the OTA upgrade requirements, re-implement steps S2-S4 until the vehicle to be updated meets the OTA upgrade requirements; when the vehicle to be updated meets the OTA upgrade requirements, calibrate the control parameters of the peripheral devices of the vehicle to be updated through the application layer software; S6. After the calibration is completed, the application layer software is updated by OTA. Instead of the application layer software controlling all hardware interfaces, the Read and execute control parameters corresponding to more than one peripheral device, and control each peripheral device to operate with the corresponding control parameters through the hardware interface.

2. The control method according to claim 1, characterized in that: Before the application layer software is updated in batches, control parameters of peripheral devices corresponding to the vehicle to be updated are defined according to the actual configuration of the vehicle and the device model.

3. The control method according to claim 1, characterized in that: Before step S1, the method further includes customizing control parameters of peripheral devices corresponding to the vehicle to be updated.

4. The control method according to claim 2, characterized in that: The control parameters defined according to the actual vehicle configuration and device model are linked to the vehicle VIN code.

5. The control method according to claim 3, characterized in that: Before identifying the control parameters of the peripheral device corresponding to the VIN code through the VIN code of the vehicle to be updated, the customized control parameters of the peripheral device are linked to the vehicle VIN code.

6. The control method according to claim 1, characterized in that: The OTA upgrade requirement is to reach a preset upgrade time.

7. A storage medium, wherein the storage medium is a computer-readable storage medium, wherein an executable computer program is stored on the computer-readable storage medium, wherein: The executable computer program is used to execute a method for controlling peripheral devices during batch updating of ECU application layer software as described in any one of claims 1-6.

Images