CN112733132A - Method and system for upgrading ECU (electronic control Unit) data - Google Patents
Method and system for upgrading ECU (electronic control Unit) data Download PDFInfo
- Publication number
- CN112733132A CN112733132A CN202110007765.8A CN202110007765A CN112733132A CN 112733132 A CN112733132 A CN 112733132A CN 202110007765 A CN202110007765 A CN 202110007765A CN 112733132 A CN112733132 A CN 112733132A
- Authority
- CN
- China
- Prior art keywords
- data
- data packet
- controller
- upgrading
- packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 238000004891 communication Methods 0.000 claims description 5
- 238000013475 authorization Methods 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 25
- 238000002347 injection Methods 0.000 description 5
- 239000007924 injection Substances 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000000889 atomisation Methods 0.000 description 1
- 238000002485 combustion reaction Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 239000002283 diesel fuel Substances 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000000243 solution Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/51—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a method and a system for upgrading ECU data. The ECU data upgrading method comprises the following steps: judging whether a data upgrading requirement exists, traversing the old controller data packet if the data upgrading requirement exists, acquiring an identification code contained in the old controller data packet with the same content as the set data packet, and rewriting the data updating and flashing times corresponding to the identification code, wherein the data updating and flashing times are used as a data upgrading determination identifier of the controller corresponding to the identification code. According to the ECU data upgrading method provided by the invention, the set data packet is configured, the vehicle ECUs to be upgraded are determined based on the set data packet and the pre-stored old controller data packet, and the data upgrading authorization is automatically carried out on the vehicle ECUs to be upgraded in batches, so that the data upgrading efficiency is greatly improved, and the labor cost required in the data upgrading process is reduced.
Description
Technical Field
The embodiment of the invention relates to a vehicle engineering technology, in particular to a method and a system for ECU data upgrading.
Background
In a common rail type accumulator injection system, the ECU mainly receives signals of various sensors, and by means of electromagnetic valves on an injector, diesel oil is enabled to inject correct injection quantity at correct injection points with correct injection pressure, so that the optimal combustion ratio, the atomization and the optimal ignition time of a diesel engine are ensured, and the diesel engine has good economy and the least pollution emission.
The ECU configured in the common rail type accumulator injection system needs to be upgraded frequently, at present, if the ECU needs to be upgraded, the number of an engine of a vehicle needing to be upgraded is inquired manually, the upgrading authority is configured for each ECU needing to write firmware manually according to the number of the engine, and the labor cost is high. In addition, if the ECU fails to be upgraded, the upgrading authority needs to be reconfigured manually, and the upgrading efficiency is low.
Disclosure of Invention
The invention provides a method and a system for upgrading ECU data, which aim to realize the purpose of automatically carrying out upgrading authorization on ECU controllers needing upgrading in batches.
In a first aspect, an embodiment of the present invention provides a method for upgrading ECU data, including:
judging whether a data upgrading requirement exists, traversing the old controller data packet if the data upgrading requirement exists, acquiring an identification code contained in the old controller data packet with the same content as the set data packet,
and rewriting the data updating and flashing times corresponding to the identification code, wherein the data updating and flashing times are used as a data upgrading determination identifier of the controller corresponding to the identification code.
Optionally, the identification code is an engine number.
Optionally, the old controller data packet is a controller outgoing data packet.
Optionally, after obtaining the identification code included in the old controller data packet with the same content as the set data packet, the method further includes:
and replacing the old controller data packet with the new controller data packet, wherein the old controller data packet has the same content as the setting data packet.
Optionally, traversing the old controller packet includes:
and inquiring whether an old controller data packet belongs to a same family data packet with the setting data packet or not, and acquiring an identification code contained in the old controller data packet which has the same content with the setting data packet or belongs to the same family data packet with the setting data packet.
Optionally, the old controller packet includes version family information,
and rewriting the data updating and flashing times corresponding to the identification code according to the version family information.
In a second aspect, an embodiment of the present invention further provides a system for ECU data upgrade, including a management unit, a server, and a terminal,
the management unit is in communication connection with the server, a setting data packet is configured in the management unit, an old controller data packet is stored in the server,
the management unit is used for judging whether a data upgrading requirement exists or not, traversing the old controller data packet if the data upgrading requirement exists, acquiring an identification code contained in the old controller data packet with the same content as the set data packet, and rewriting the data updating and flashing times corresponding to the identification code in the server;
the terminal is in communication connection with the server and used for finishing data upgrading of the controller corresponding to the identification code based on the data updating and flashing times.
Optionally, the terminal is further configured to determine whether the data upgrade of the controller is successful,
if the data of the controller is upgraded successfully, the terminal returns an upgrade success flag bit to the server, and the server rewrites the data updating and flashing times corresponding to the controller to be zero;
and if the data upgrading of the controller fails, the terminal returns an upgrading failure zone bit to the server, and the server maintains the data updating and flashing times corresponding to the controller.
Optionally, the management unit is further configured to:
inquiring whether an old controller data packet belongs to a same family data packet with the setting data packet, acquiring an identification code contained in the old controller data packet which has the same content with the setting data packet or belongs to the same family data packet with the setting data packet,
the old controller data packet comprises version family information, and the management unit rewrites the data updating and flashing times corresponding to the identification code in the server according to the version family information.
Optionally, configuring a family of new controller data packets in the terminal,
and the terminal completes the data upgrading of the controller corresponding to the identification code by utilizing the new controller data packet of the same family based on the data updating and flashing times.
Compared with the prior art, the invention has the beneficial effects that: according to the ECU data upgrading method provided by the invention, the set data packet is configured, the vehicle ECUs to be upgraded are determined based on the set data packet and the pre-stored old controller data packet, and the data upgrading authorization is automatically carried out on the vehicle ECUs to be upgraded in batches, so that the data upgrading efficiency is greatly improved, and the labor cost required in the data upgrading process is reduced.
Drawings
FIG. 1 is a flowchart of an ECU data upgrade method in an embodiment;
FIG. 2 is a flow chart of another ECU data upgrade method in an embodiment;
fig. 3 is a block diagram of an ECU data upgrade system in the embodiment.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
The present embodiment is applicable to the case of ECU controller upgrade, and the method may be executed by a Management unit, where the Management unit is implemented by using a Product Data Management system (PDM), fig. 1 is a flowchart of an ECU Data upgrade method in the embodiment, and referring to fig. 1, the method for ECU Data upgrade includes:
s101, judging whether a data upgrading requirement exists or not, traversing an old controller data packet if the data upgrading requirement exists, and acquiring an identification code contained in the old controller data packet with the same content as the set data packet.
Illustratively, the management unit is configured with a setting data packet, and the content of the setting data packet is the same as the content in the data packet which needs to be upgraded or replaced.
Illustratively, the old controller packet contains the same content as the packet configured by default in each ECU before the upgrade has not been performed.
In one possible implementation scheme, the old controller data packet is stored in the data server, the old controller data packet binds the identification code, the management unit acquires the old controller data packet in the server, judges whether the content in the setting data packet is the same as the content in the current old controller data packet, and records the identification code corresponding to the old controller data packet if the content in the setting data packet is the same as the content in the current old controller data packet.
In one possible implementation, the old controller data packet includes the same content as the controller factory data packet. According to the scheme, when data upgrading is needed each time, the set data packet is the factory data packet, namely after ECU upgrading is completed each time, the old controller data packet stored in the server does not need to be updated.
For example, the identification code may be a Vehicle Identification Number (VIN) or an engine number, and the identification code may be configured in the old controller data packet or may be in one-to-one correspondence with the old controller data packet in the form of key value pairs and stored in the server.
In one possible embodiment, the identification code is an engine number.
For example, if the contents in the setup data packet and the old controller data packet are the same, the check codes of the setup data packet and the old controller data packet may be calculated respectively, and if the check codes of the setup data packet and the old controller data packet are the same, the contents in the setup data packet and the old controller data packet are determined to be the same.
And S102, rewriting the data updating and flashing times corresponding to the identification code.
Illustratively, one identification code corresponds to one data update flash time, and the data update flash time is configured in the server.
Specifically, the number of data update flashes is used as a data upgrade determination flag of the controller corresponding to the identification code. For example, the default value of the number of data update times may be configured as 0, if the number of data update times is 0, it indicates that the ECU corresponding to the current identification code cannot be upgraded, if the condition for rewriting the number of data update times is satisfied, the number of data update times may be rewritten as 1, and if the number of data update times is 1, it indicates that the ECU corresponding to the current identification code can be upgraded.
In an implementation, a new controller data packet required in the data packet upgrading process may be configured in the management unit, the ECU may obtain the new controller data packet through the management unit, and when the ECU communicates with the server and obtains that the number of data update times is not 0, the ECU may complete the upgrading of the data packet according to a predetermined data packet upgrading process.
In the embodiment, the set data packet is configured, the vehicle ECUs to be upgraded are determined based on the set data packet and the pre-stored old controller data packet, and data upgrading authorization is automatically performed on the vehicle ECUs to be upgraded in batches, so that the data upgrading efficiency is greatly improved, and the labor cost required in the data upgrading process is reduced.
Fig. 2 is a flowchart of another ECU data upgrading method in the embodiment, and referring to fig. 2, the method for ECU data upgrading may further be:
s201, judging whether a data upgrading requirement exists or not, and traversing the old controller data packet if the data upgrading requirement exists.
S202, acquiring the identification code contained in the old controller data packet with the same content as the set data packet.
Illustratively, in the scheme shown in fig. 2, version family information is also included in the old controller packet, and the version family information includes the version number of the current old controller packet and the packet type.
Besides the identification code contained in the old controller data packet with the same content as the set data packet, the method also comprises the step of obtaining the version family information contained in the current old controller data packet.
For example, in this step, the method of determining whether the content in the setting packet is the same as the content in the old controller packet is the same as the content described in step S101.
For example, the version family information is configured at a fixed position of the old controller packet and occupies a byte number with a fixed length, and the version family information may be obtained by intercepting a byte at a specified position in the old controller packet.
S203, acquiring the identification code contained in the old controller data packet belonging to the same family as the set data packet.
In step S202, if the setting packet and the old version packet contain different contents, the version family information in the setting packet and the version family information in the old controller packet are compared to determine whether they belong to the same family information.
For example, if the packet type included in the version group information in the setting packet is the same as the packet type included in the version group information in the old controller packet, it is determined that the setting packet and the current old controller packet belong to the same group.
And S204, rewriting the data updating and flashing times corresponding to the identification code according to the version family information.
For example, in this step, if the contents of the setting packet and the old controller packet are the same, the version group information included in the setting packet and the old controller packet is also the same, and in this case, the number of data update flushes may be rewritten to 1.
If the content of the setting data packet is different from that of the old controller data packet, and the setting data packet and the old controller data packet belong to the same family of data packets, the number of data update times can be rewritten according to the version number included in the version family information in the setting data packet and the old controller data packet. For example, if the version number of the packet is set to 002 and the version number of the old controller packet is set to 001, the number of data update flushes is rewritten to 2. If the version number of the packet is set to 003 and the version number of the old controller packet is set to 001, the number of data update flushes is rewritten to 3.
For example, the number of old controller packets stored in the server may change, for example, after the new vehicle is delivered, the controller factory packets configured by the ECU in the vehicle may be newly added in the server.
For example, the ECUs of the same category may be upgraded multiple times, before each data upgrade, the configured setting data packet is a new controller data packet used in the last data upgrade, if an old controller data packet stored in the server is not updated, the content of the setting data packet is the same as that of the old controller data packet in the first data upgrade of the ECU of the category, and the content of the setting data packet is different from that of the old controller data packet in the subsequent data upgrade. Because the upgrading times of the vehicle ECU corresponding to the newly-added old controller data packet in the server are possibly different from the upgrading times of the vehicle ECU corresponding to the old controller data packet stored in the server in advance, the data updating and flashing times corresponding to the identification code are rewritten through the version family information, the data flashing times required by the vehicle ECU corresponding to the newly-added old controller data packet in the server to be upgraded to the latest version can be met, and the problem that the data upgrading fails due to the fact that the authorized flashing times are insufficient is solved.
For example, the vehicle ECU a has not been subjected to data upgrade, the version number of the controller shipment data packet configured in the vehicle ECU a is 001, meanwhile, the remaining vehicle ECUs of the same type have been subjected to one upgrade, and the version number of the old controller data packet configured in the remaining vehicle ECUs of the same type is 002, the version number of the data packet is set to be 002 when the third upgrade is performed, and the number of data update times is 2. For the vehicle ECU A, the data packet needs to be upgraded to the latest version by two data flashing, namely the data packet is upgraded from the 001 version to the 002 version and then from the 002 version to the 003 version.
In one possible embodiment, obtaining the identification code contained in the old controller data packet having the same content as the setting data packet further comprises: the old controller packet having the same contents as the set packet is replaced by the new controller packet.
In one possible embodiment, obtaining the identification code included in the old controller packet belonging to the same family as the configuration packet further comprises: the old controller packet having the same contents as the set packet is replaced by the new controller packet.
When data is upgraded every time, an old controller data packet with the same content as a set data packet is replaced by a new controller data packet with the latest version, so that the ECU of a vehicle in a factory state can be conveniently determined, whether the ECU is upgraded according to a set data packet upgrading process or not can be conveniently monitored, and the upgrading of the data packet can be completed in a version-by-version upgrading mode.
Example two
Fig. 3 is a block diagram of an ECU data upgrade system in the embodiment, and referring to fig. 3, the embodiment proposes a system for ECU data upgrade, which includes a management unit 100, a server 200, and a terminal 300.
The management unit 100 is connected to the server 200 in communication, and the management unit 100 arranges a setting packet, and the server 200 stores an old controller packet.
The working process of the ECU data upgrading system comprises the following steps:
step 1, the management unit is used for judging whether a data upgrading requirement exists, traversing an old controller data packet stored in the server if the data upgrading requirement exists, and acquiring an identification code contained in the old controller data packet with the same content as the set data packet.
And 2, the management unit rewrites the data updating and flashing times corresponding to the identification code in the server.
For example, the default value of the data update count may be configured to be 0, if the data update count is 0, the ECU corresponding to the current identification code cannot be upgraded, if the condition for rewriting the data update count is satisfied, the data update count may be rewritten to 1, and if the data update count is 1, the ECU corresponding to the current identification code may be upgraded.
And 3, the terminal is used for finishing the data upgrading of the controller corresponding to the identification code based on the data updating and flashing times.
For example, the terminal may be an ECU diagnostic tool.
For example, a new controller data packet required in the upgrading process may be configured in the management unit, the terminal may obtain the new controller data packet through the management unit, and when the terminal communicates with the server and the obtained data update write-through number is not 0, the terminal may complete upgrading of the data packet according to a predetermined data packet upgrading flow.
In one possible embodiment, the operation of the ECU data upgrade system further comprises:
step 4, the terminal judges whether the data upgrading of the controller is successful, if the data upgrading of the controller is successful, the terminal returns an upgrading success flag bit to the server; and if the data upgrading of the controller fails, the terminal returns an upgrading failure zone bit to the server.
For example, in this step, if the controller packet in the ECU is upgraded to the latest new controller packet, the terminal determines that the data upgrade of the ECU is successful.
In this step, if the server receives the upgrade success flag bit, the server rewrites the data update and write frequency corresponding to the controller to zero; and if the server receives the upgrading failure zone bit, the server maintains the data updating and flashing times corresponding to the controller.
When the data is upgraded successfully, the server rewrites the number of data updating and refreshing to zero, and the ECU can not change the data again, so that the problem that personnel without upgrading authority can freely refresh the ECU after the ECU is upgraded successfully can be solved.
In the upgrading process, after the management unit completely rewrites the data updating and updating times in the server, the change state of the data updating and updating times can be acquired, and whether the ECU is successfully upgraded can be directly determined according to the change state of the data updating and updating times.
In one possible embodiment, the operation process of the ECU data upgrading system may further include:
step 1, judging whether a data upgrading requirement exists or not, and traversing an old controller data packet if the data upgrading requirement exists.
And 2, judging whether the content in the set data packet is the same as that in the old controller data packet or not, and acquiring the identification code contained in the old controller data packet with the same content as that of the set data packet.
And 3, inquiring whether the old controller data packet and the set data packet belong to the same family data packet or not, and acquiring the identification code contained in the old controller data packet belonging to the same family data packet as the set data packet.
And 4, the management unit rewrites the data updating and flashing times corresponding to the identification code in the server according to the version family information.
Illustratively, in this step, the manner in which the management unit rewrites the number of data update flushes corresponding to the identification code in the server according to the version family information is the same as that described in step S204 in the first embodiment.
And 5, the terminal completes data upgrading of the controller corresponding to the identification code by utilizing the same family new controller data packet based on the data updating and flashing times.
For example, in this step, if the number of data update times is 1, the new controller packet of the same family is the latest new controller packet, and the terminal directly uses the latest new controller packet to complete the data upgrade of the ECU.
And if the data updating times are more than 1, the new controller data packets of the same family comprise all default controller data packets between the old controller data packet and the latest new controller data packet configured in the ECU to be upgraded. And the terminal completes the data upgrading of the ECU by utilizing the data packet of the new controller of the same family in a version-by-version upgrading mode.
Step 6, the terminal judges whether the data upgrading of the controller is successful, if the data upgrading of the controller is successful, the terminal returns an upgrading success flag bit to the server; if the data of the controller fails to be upgraded, the terminal returns an upgrading failure zone bit to the server
Step 7, if the server receives the upgrade success flag bit, the server rewrites the data update and flash times corresponding to the controller to zero; and if the server receives the upgrading failure zone bit, the server maintains the data updating and flashing times corresponding to the controller.
In one possible embodiment, the acquiring, by the management unit, the identification code included in the old controller packet having the same content as the setting packet further includes: the old controller packet having the same contents as the set packet is replaced by the new controller packet.
In one possible embodiment, the obtaining, by the management unit, the identification code included in the old controller packet belonging to the same family as the configuration packet further includes: the old controller packet having the same contents as the set packet is replaced by the new controller packet.
In one possible embodiment, the server may be configured to acquire the setting data packet stored in the management unit, and the server traverses the old controller data packet, queries an identification code included in the old controller data packet having the same content as the setting data packet, and rewrites the number of data update flushes corresponding to the identification code.
In this embodiment, in order to record the technical solutions and the beneficial effects in detail, the same contents as those in the first embodiment are omitted for brevity.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A method for ECU data upgrade, comprising:
judging whether a data upgrading requirement exists, traversing the old controller data packet if the data upgrading requirement exists, acquiring an identification code contained in the old controller data packet with the same content as the set data packet,
and rewriting the data updating and flashing times corresponding to the identification code, wherein the data updating and flashing times are used as a data upgrading determination identifier of the controller corresponding to the identification code.
2. The method of ECU data upgrade of claim 1, wherein the identification code is an engine number.
3. The method of ECU data upgrade of claim 1, wherein the old controller data package is a controller factory data package.
4. The method for upgrading ECU data according to claim 1, wherein after acquiring the identification code contained in the old controller data packet with the same content as the setting data packet, the method further comprises:
and replacing the old controller data packet with the new controller data packet, wherein the old controller data packet has the same content as the setting data packet.
5. The method of ECU data upgrade of claim 1, wherein traversing the old controller data packet comprises:
and inquiring whether an old controller data packet belongs to a same family data packet with the setting data packet or not, and acquiring an identification code contained in the old controller data packet which has the same content with the setting data packet or belongs to the same family data packet with the setting data packet.
6. The method of ECU data upgrade according to claim 5, wherein the old controller packet includes version family information,
and rewriting the data updating and flashing times corresponding to the identification code according to the version family information.
7. The system for ECU data upgrading is characterized by comprising a management unit, a server and a terminal,
the management unit is in communication connection with the server, a setting data packet is configured in the management unit, an old controller data packet is stored in the server,
the management unit is used for judging whether a data upgrading requirement exists or not, traversing the old controller data packet if the data upgrading requirement exists, acquiring an identification code contained in the old controller data packet with the same content as the set data packet, and rewriting the data updating and flashing times corresponding to the identification code in the server;
the terminal is in communication connection with the server and used for finishing data upgrading of the controller corresponding to the identification code based on the data updating and flashing times.
8. The system for ECU data upgrade according to claim 7, wherein the terminal is further configured to determine whether the data upgrade of the controller is successful,
if the data of the controller is upgraded successfully, the terminal returns an upgrade success flag bit to the server, and the server rewrites the data updating and flashing times corresponding to the controller to be zero;
and if the data upgrading of the controller fails, the terminal returns an upgrading failure zone bit to the server, and the server maintains the data updating and flashing times corresponding to the controller.
9. The system for ECU data upgrade of claim 8, wherein the management unit is further configured to:
inquiring whether an old controller data packet belongs to a same family data packet with the setting data packet, acquiring an identification code contained in the old controller data packet which has the same content with the setting data packet or belongs to the same family data packet with the setting data packet,
the old controller data packet comprises version family information, and the management unit rewrites the data updating and flashing times corresponding to the identification code in the server according to the version family information.
10. The system for ECU data upgrade according to claim 9, wherein a family-wide new controller package is configured in the terminal,
and the terminal completes the data upgrading of the controller corresponding to the identification code by utilizing the new controller data packet of the same family based on the data updating and flashing times.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110007765.8A CN112733132A (en) | 2021-01-05 | 2021-01-05 | Method and system for upgrading ECU (electronic control Unit) data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110007765.8A CN112733132A (en) | 2021-01-05 | 2021-01-05 | Method and system for upgrading ECU (electronic control Unit) data |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112733132A true CN112733132A (en) | 2021-04-30 |
Family
ID=75591157
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110007765.8A Pending CN112733132A (en) | 2021-01-05 | 2021-01-05 | Method and system for upgrading ECU (electronic control Unit) data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112733132A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114880002A (en) * | 2022-07-12 | 2022-08-09 | 江铃汽车股份有限公司 | OTA data flashing method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104539668A (en) * | 2014-12-16 | 2015-04-22 | 北京新能源汽车股份有限公司 | Method and system for remotely updating software program in automobile |
| CN107132788A (en) * | 2017-03-30 | 2017-09-05 | 深圳市元征科技股份有限公司 | A kind of vehicle electronic control unit writes with a brush dipped in Chinese ink method and apparatus automatically |
| CN108182072A (en) * | 2017-12-28 | 2018-06-19 | 上汽通用五菱汽车股份有限公司 | Remote upgrade method, server and the storage medium of vehicle electronics |
| WO2018154949A1 (en) * | 2017-02-23 | 2018-08-30 | 住友電気工業株式会社 | Program updating system, control device, program updating method and computer program |
| CN109343881A (en) * | 2018-10-11 | 2019-02-15 | 珠海格力电器股份有限公司 | Firmware upgrade update method, device and air-conditioning |
| CN110351314A (en) * | 2018-04-03 | 2019-10-18 | 厦门雅迅网络股份有限公司 | The remote upgrade method and computer readable storage medium of automobile controller |
-
2021
- 2021-01-05 CN CN202110007765.8A patent/CN112733132A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104539668A (en) * | 2014-12-16 | 2015-04-22 | 北京新能源汽车股份有限公司 | Method and system for remotely updating software program in automobile |
| WO2018154949A1 (en) * | 2017-02-23 | 2018-08-30 | 住友電気工業株式会社 | Program updating system, control device, program updating method and computer program |
| CN107132788A (en) * | 2017-03-30 | 2017-09-05 | 深圳市元征科技股份有限公司 | A kind of vehicle electronic control unit writes with a brush dipped in Chinese ink method and apparatus automatically |
| CN108182072A (en) * | 2017-12-28 | 2018-06-19 | 上汽通用五菱汽车股份有限公司 | Remote upgrade method, server and the storage medium of vehicle electronics |
| CN110351314A (en) * | 2018-04-03 | 2019-10-18 | 厦门雅迅网络股份有限公司 | The remote upgrade method and computer readable storage medium of automobile controller |
| CN109343881A (en) * | 2018-10-11 | 2019-02-15 | 珠海格力电器股份有限公司 | Firmware upgrade update method, device and air-conditioning |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114880002A (en) * | 2022-07-12 | 2022-08-09 | 江铃汽车股份有限公司 | OTA data flashing method and system |
| CN114880002B (en) * | 2022-07-12 | 2022-09-06 | 江铃汽车股份有限公司 | OTA data flashing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11507365B2 (en) | On-board update device, update processing program, program update method, and on-board update system | |
| CN112328294B (en) | OTA upgrading method and system for vehicle ECU | |
| CN101604371B (en) | Method and system for controlling authority of plug-in unit | |
| US20170344355A1 (en) | Updating vehicle system modules | |
| US20220156057A1 (en) | In-vehicle update device, update processing program, and program update method | |
| CN106874026A (en) | For the method and apparatus via the air interface steadily firmware of more new vehicle | |
| DE102016106802A1 (en) | Vehicle control storage methods and systems | |
| CN108153562B (en) | System and method for remote program update management of ECU of new energy automobile | |
| US20190278588A1 (en) | Vehicle control system and software compatibility checking method | |
| US20070036021A1 (en) | Data reprogramming method and system | |
| US20220004374A1 (en) | Program update system and update processing program | |
| CN102103511A (en) | Method and system for refreshing application program | |
| CN112733132A (en) | Method and system for upgrading ECU (electronic control Unit) data | |
| WO2019123747A1 (en) | Electronic control device for automobile and control method thereof | |
| CN111290351A (en) | Driver management method, system, computer equipment and storage medium | |
| CN113570758A (en) | Remote monitoring terminal and vehicle Bluetooth key management method | |
| CN114793250B (en) | Configurable CAN data analysis method | |
| KR20220154195A (en) | Certificate list renewal method and device | |
| CN115344281A (en) | Finished automobile OTA (over the air) upgrading method, system, storage medium and equipment | |
| KR20120042303A (en) | Variant control cluster using vehicle diagnosis protocol and process for setting the same | |
| JP3982226B2 (en) | Data writing system for electronic control unit | |
| US20230153097A1 (en) | Devices and method for managing electronic control units of a motor vehicle | |
| CN115225481B (en) | Gateway diagnosis route configuration method and device, vehicle-mounted gateway, vehicle and medium | |
| EP4250686A1 (en) | Automatic configuration of replaced field devices in an industrial plant | |
| KR20130022688A (en) | Device for updating software of electronic control units in vehicle |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210430 |
|
| RJ01 | Rejection of invention patent application after publication |