CN115904411A - Software error-proofing method and system applied to after-sale market - Google Patents
Software error-proofing method and system applied to after-sale market Download PDFInfo
- Publication number
- CN115904411A CN115904411A CN202211466877.0A CN202211466877A CN115904411A CN 115904411 A CN115904411 A CN 115904411A CN 202211466877 A CN202211466877 A CN 202211466877A CN 115904411 A CN115904411 A CN 115904411A
- Authority
- CN
- China
- Prior art keywords
- ecu
- software
- vehicle
- flashed
- flashing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Stored Programmes (AREA)
Abstract
The invention belongs to the technical field of vehicle software flashing, and relates to a software error-proofing flashing method and system applied to after-sales markets, wherein when flashing equipment is in communication connection with a production management system and is connected with a vehicle, the following steps are executed: acquiring a finished vehicle VIN code, and determining identification information of a current vehicle according to the VIN code; acquiring an ECU (electronic control unit) supporting flash in the vehicle from a production management system according to the identification information; and receiving the confirmation information of the ECU to be flashed, judging whether the ECU to be flashed accords with the flashing condition, and if so, transmitting the corresponding software update package to the ECU to be flashed. According to the method and the system, the correlation is established between the VIN code and the production management system, so that the erasable ECU can be quickly determined, and the accuracy of subsequent ECU flashing is ensured.
Description
Technical Field
The invention belongs to the technical field of vehicle software flashing, and particularly relates to a software error-proofing flashing method and system applied to an after-sale market.
Background
The statements in this section merely provide background information related to the present disclosure and may not necessarily constitute prior art.
With the increasing input and support of China on electric automobiles, people have higher acceptance on the electric automobiles, more and more people start purchasing the electric automobiles, and the support of the electric automobiles per year is promoted to be increased; the electromotion and intelligence degrees in the electric automobile four-generation are higher and higher, the concept of a software defined automobile is more and more mature, more and more ECUs (electronic control units) with software functions are arranged in the electric automobile, the upgrading quantity and times of the ECU software are increased in an explosive mode, and the requirements that a large number of different ECUs are required to write the software on a production line of a host factory and an after-sale market appear.
After-sale market service personnel have different abilities and have little knowledge about software, and besides, the current market sells a plurality of configured vehicle types, and ECUs with the same vehicle type in different configured vehicles also have different software versions; the situation that the version information of the developed software is different also occurs due to the current shortage of various resources when the ECUs of the same configuration vehicle type are the same, and great inconvenience is brought to after-market software flashing under the situation.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a software error-proofing method and a software error-proofing system applied to the after-sales market. The association is established between the VI N code and the production management system, so that the ECU which can be refreshed can be quickly determined, and the accuracy of subsequent ECU refreshing is ensured.
In order to achieve the above object, one or more embodiments of the present invention provide the following technical solutions:
a software error-proofing brushing method applied to after-sales markets is applied to brushing equipment, the brushing equipment is in communication connection with a production management system, and after the brushing equipment is connected with a vehicle, the following steps are executed:
acquiring a finished automobile VI N code, and determining identification information of a current vehicle according to the VI N code;
acquiring an ECU (electronic control unit) supporting flash in the vehicle from a production management system according to the identification information;
and receiving the confirmation information of the ECU to be flashed, judging whether the ECU to be flashed accords with the flashing condition, and if so, transmitting the corresponding software update package to the ECU to be flashed.
Further, judging whether the ECU to be subjected to the flash meets the flash condition comprises the following steps:
acquiring local identification information and a current software version number of the ECU to be flashed of the vehicle;
acquiring ECU (electronic control unit) applicable information and a software version number of a corresponding software update package, wherein the ECU applicable information comprises ECU identification information applicable to the software update package;
and if the identification information of the ECU to be flashed is consistent with the ECU application information of the software updating package, and the current software version number of the ECU to be flashed is lower than the software version number of the software updating package, the ECU to be flashed conforms to the flashing condition.
Further, the identification information of the ECU includes one or more of a part number and a hardware version number.
Further, after the configuration information of the ECU to be flashed local to the vehicle is acquired, the following operations are also executed: and comparing the configuration information of the ECU local to the vehicle with the configuration information of the ECU acquired from the production management system, and if the configuration information of the ECU local to the vehicle is inconsistent, uploading the configuration information of the ECU acquired from the vehicle to the production management system.
Further, transmitting the corresponding software update package to the to-be-flashed ECU comprises:
sending a memory erasing request to the ECU to be refreshed, wherein the memory erasing request comprises an erasing starting address and an erasing length;
and transmitting the corresponding software update package to the ECU to be flashed.
One or more embodiments provide a flash device configured to execute the software error-proofing method applied to the after-market.
One or more embodiments provide a vehicle ECU, connected to the flash device, configured to:
receiving a software update package transmitted by the flash device;
respectively carrying out integrity check and validity check on the software update package;
and if the verification is passed, executing software flashing.
Further, after the software is flashed, the current software version number of the ECU is read and compared with the software version number of the software update package, and if the current software version number of the ECU is consistent with the software version number of the software update package, the flashed data is correct.
Further, the integrity check employs a CRC check.
One or more embodiments provide a software error-proofing system for after-market applications, including the brushing apparatus and the vehicle ECU.
The above one or more technical solutions have the following beneficial effects:
by means of a production management system (MES), association is established between the VI N code and the production management system, and the ECU which can be rewritten can be quickly determined on the basis of one-to-one correspondence between the VI N code of the whole vehicle and the configuration information of the ECU, so that the accuracy of subsequent ECU rewriting is ensured.
By matching the identification information of the ECU to be refreshed and the current software version number based on the vehicle local with the ECU application information and the software version number of the software update package, software error refreshing is prevented.
In addition, as the flash equipment is connected with the production management system, the production management system can accurately store the current configuration information of the vehicle through data consistency verification when the ECU is replaced but the ECU is not updated to the production management system in time.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and together with the description serve to explain the invention and not to limit the invention.
FIG. 1 is a diagram illustrating an architecture of a software error proofing system for after-market applications according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating an overall software error proofing method applied to an after-sales market according to an embodiment of the present invention;
fig. 3 is a specific flowchart of the software error-proofing method applied to the after-market in the embodiment of the present invention.
Detailed Description
It is to be understood that the following detailed description is exemplary and is intended to provide further explanation of the invention as claimed. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs.
It is noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments according to the invention. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, and it should be understood that when the terms "comprises" and/or "comprising" are used in this specification, they specify the presence of stated features, steps, operations, devices, components, and/or combinations thereof, unless the context clearly indicates otherwise.
The embodiments and features of the embodiments of the present invention may be combined with each other without conflict.
Example one
A software error-proofing system applied to after-sales markets comprises a writing device and a production management system (MES for short). The flash equipment is in communication connection with the production management system, is simultaneously used for being connected with a vehicle-mounted CAN controller, and is communicated with an ECU (electronic control unit) configured in a vehicle through a CAN network.
The production management system comprises a material management function, can realize the whole process material management from material purchase to finished product warehousing, and has complete records on the vehicle type, the manufacturer and the ECU information configured by the vehicle. Specifically, the production management system records the tracing code of the ECU, the tracing code is bound with the ECU and cannot be replaced, and if the ECU is replaced in the after-sales market, a new tracing code is uploaded to the production management system to replace the existing tracing code.
The flash equipment comprises a VI N code automatic acquisition module and an intelligent identification module.
The VI N code automatic acquisition module is used for automatically acquiring the VI N code of the whole vehicle after the vehicle is connected with the flash device, acquiring the identification information of the current vehicle according to the VI N code coding rule of the whole vehicle, and acquiring an ECU module which is developed in the current vehicle and has been flashed, namely the ECU which supports flash at present, from a production management system according to the identification information, and providing for selection of customers through a popup window.
The VI N code of the vehicle consists of 17 numbers and letters, each code represents a certain aspect of the vehicle and respectively has information of the country of production, manufacturer, type, brand, model, engine model, production date and the like of the vehicle. According to the encoding rule of the finished vehicle VI N code, identification information of a current vehicle can be acquired, wherein the identification information comprises a vehicle type, configuration information and the like, the configuration information of each ECU in the vehicle can be acquired from a production management system based on the identification information, and the configuration information of the ECU comprises a part number, a hardware version number, a software version number and the like.
The current vehicle identification information is obtained through analyzing the VI N code, and a bridge between the current vehicle and a production management system is established, so that the configuration information of each ECU of the vehicle can be prepared, the ECU which cannot be flashed can be rapidly eliminated, and the subsequent accurate flashing is guaranteed. Even if the ECU is replaced in the after-market, a new tracing code is generally uploaded to a production management system to replace an existing tracing code, that is, accurate current ECU configuration information can be acquired through the production management system, so that which ECUs can be flashed is confirmed.
The intelligent identification module is used for establishing communication connection with the ECU after confirming the ECU to be written with a brush, and executing the following steps:
(1) Acquiring configuration information of the ECU local to the vehicle and acquiring a corresponding software update package;
(2) Analyzing the software updating package to obtain ECU applicable information and a software version number of the software updating package, wherein the ECU applicable information comprises ECU identification information applicable to the software updating package; the identification information of the ECU includes one or more of a part number, a unique identifier, and a hardware version number.
(3) And judging whether the ECU accords with the software flashing condition, specifically, if the identification information of the ECU to be flashed is consistent with the ECU application information of the software updating package, and the current software version number of the ECU to be flashed is lower than the software version number of the software updating package, the ECU to be flashed accords with the flashing condition.
In the embodiment, partial information is acquired through the UDS diagnostic service to judge whether the software to be flashed is matched with the flash ECU, the acquired specific information includes but is not limited to information such as an ECU part number, an ECU special identifier, a hardware version number and a software version number, and if the acquired specific information is matched with the ECU, software is developed to be flashed. And switching between the application software and the flash mode is realized through the UDS service, so that the flash of the software is realized.
In order to compensate for the fact that after the ECU is replaced in the after-market, information may not be updated to the production management system in time, after the configuration information of the ECU local to the vehicle is acquired in step (1), the following operations are further performed: and comparing the configuration information of the ECU local to the vehicle with the configuration information of the ECU acquired from the production management system, and if the configuration information of the ECU local to the vehicle is inconsistent, uploading the configuration information of the ECU acquired from the vehicle to the production management system.
As a specific implementation manner, the step (3) of determining whether the ECU meets the software flashing condition specifically includes the following steps:
(3.1) the intelligent identification module reads information such as an ECU part number and an ECU special identifier through the UDS service to judge whether the software to be flashed is matched with the ECU; if the data is matched with the data, the flash is continuously performed, and if the data is not matched with the data, flash failure and a failure reason are prompted;
(3.2) the intelligent identification module reads the ECU hardware version number through the UDS service to judge whether the ECU hardware supports software upgrading; if the flash is supported, the flash is continuously performed, and if the flash is not supported, the flash failure and the failure reason are prompted;
(3.3) reading the ECU software version number through the UDS service to judge whether the current ECU needs software upgrading; if the software is needed, continuing to perform software flashing, and if the software is not needed, prompting the flashing failure and the failure reason;
and (3.4) if the verification of the steps (1) to (3) is passed, controlling the UDS service ECU to switch into a flash mode, sending a flash starting message to the ECU, and transmitting a software updating package corresponding to the ECU.
The ECU is internally provided with an erasing memory module, a downloading transmission module, an integrity checking module and an effectiveness checking module.
The erasing memory module is used for erasing the specific data in the current ECU FLASH address after receiving the FLASH starting message; the specific implementation manner of erasing the data in the FLASH address by the memory erasing module is determined by a host factory, and the data format requested by the terminal of the FLASH device is generally as follows: 31 service + erase dd + erase start address + erase length.
And the download transmission module is used for downloading and transmitting the software update package to the corresponding memory address of the FLASH.
The integrity checking module is used for checking the integrity of data transmission after the downloading and transmission of the software data are finished, so that the integrity of the data transmission is ensured, and a common checking method is crc checking;
the validity checking module is used for checking the validity of the data in the FLASH address, checking whether the data stored in the FLASH memory is valid or not, feeding back a checking result after the checking is finished, if the checking validity passes, indicating that the software data flashing is correct, exiting the flashing mode, and if the validity does not pass, indicating that the software data flashing is incorrect, and prompting the reason of the flashing failure and the failure.
Reading current software version information through a UDS service, comparing whether the current software version information is an updated software version, if the current software version information is consistent with the updated software version information, indicating that the software is successfully refreshed, and if the current software version information is inconsistent with the updated software version information, prompting the refreshing failure and failure reasons;
and finishing the flash after the data information in the flash process is stored.
Example two
The present embodiment aims to provide a software error-proofing method applied to an after-market based on the system of the first embodiment, which is applied to a brushing device, where the brushing device is in communication connection with a production management system, and after establishing connection with a vehicle, executes the following steps:
step 1: acquiring a finished automobile VI N code, and determining identification information of a current vehicle according to the VI N code;
step 2: acquiring an ECU (electronic control unit) supporting flash in the vehicle from a production management system according to the identification information;
and step 3: and receiving the confirmation information of the ECU to be flashed, judging whether the ECU to be flashed accords with the flashing condition, and if so, transmitting the corresponding software update package to the ECU to be flashed.
The step 3 of judging whether the ECU to be subjected to flash writing meets the flash writing condition specifically comprises the following steps:
s1: automatically reading the VI N code and ECU identification information;
s2: judging whether the flash software is matched with the current vehicle type or not by reading the special identifier of the controller;
s3: judging whether the current hardware version supports software flashing or not by reading the hardware version number of the controller;
s4: judging whether the current software needs software flashing or not by reading the software version number of the controller;
s5: through the UDS diagnostic service, the controller enters a flash mode;
s6: erasing original data in the FLASH address through a UDS diagnosis service;
s7: downloading and transmitting the software data to be written to FLASH through a UDS diagnosis service;
s8, after the downloading and transmission are finished, detecting the integrity of the data through UDS diagnostic service;
s9: checking data validity by the UDS diagnostic service;
s10: through the UDS diagnostic service, the controller exits the flash mode;
s11: reading and comparing the current software version number through a UDS diagnosis service;
s12: storing the whole data of the flash process;
s13: finishing the flash writing;
before the software flash, the following is included for steps S1-S4:
automatically reading finished automobile VI N codes (the mode of reading the VI N codes by a host factory is consistent), automatically judging the current automobile type according to the VI N codes, and popping up a developed and written ECU module of the current automobile type for a client to select a window; the intelligent identification module reads the identification information of the ECU part through the UDS diagnostic service, and the obtained specific information includes but is not limited to information such as an ECU part number, an ECU special identifier and the like;
judging whether the current software to be written and the ECU configuration vehicle model are matched or not through the ECU (electronic control unit) identification information read by the UDS service, if so, continuing to write the software, and if not, prompting the software writing failure and the failure reason;
reading the hardware version number of the ECU through the UDS diagnostic service, judging whether the current hardware version supports software flashing, if so, continuing to perform software flashing, and if not, prompting the flashing failure and the failure reason;
reading the software version number of the ECU through the UDS diagnostic service, judging whether the current ECU needs to perform software flashing, if the software version to be flashed is higher than the ECU software version, continuing to perform software flashing, and if the software version to be flashed is lower than or equal to the ECU software version, prompting the flashing failure and the failure reason;
further, at the start of the software flush, the following is included for steps S5-S10:
1. through the UDS diagnostic service, the ECU enters a software flashing mode;
2. the erasing memory module is used for clearing data stored in FLASH in the ECU;
3. downloading the software data to be written to a FLASH memory;
4. the integrity of the downloaded data is verified, if the verification is passed, the flash is continuously performed, and if the verification is not passed, the software flash failure and the failure reason are prompted;
5. the validity check module is used for checking the validity of the data in the FLASH memory address, if the data passes the check, the ECU exits the FLASH mode, and if the data does not pass the check, the FLASH failure and the failure reason are prompted;
6. through the UDS diagnostic service, the ECU exits the flash mode;
further, after the controller completes the flash, the following contents are included for steps S11 to S13;
1. reading the current ECU software version number through the UDS diagnostic service, continuing to perform software flashing if the read software version number is consistent with the version number of the software to be flashed, and prompting software flashing failure and failure reasons if the read software version number is inconsistent with the version number of the software to be flashed;
2. data in the whole upgrading process is stored, so that later-stage problem troubleshooting and data statistics are facilitated;
3. and ending the software flashing flow.
In one or more embodiments, association is established between the VI N code and the production management system by means of a production management system (MES), and the ECU capable of being flashed can be quickly determined based on one-to-one correspondence between the VI N code of the whole vehicle and the configuration information of the ECU, so that the accuracy of subsequent ECU flashing is ensured.
Although the embodiments of the present invention have been described with reference to the accompanying drawings, it is not intended to limit the scope of the invention, and it should be understood by those skilled in the art that various modifications and variations can be made without inventive changes in the technical solutions of the present invention.
Claims (10)
1. A software error-proofing brushing method applied to after-sales markets is applied to brushing equipment and is characterized in that the brushing equipment is in communication connection with a production management system, and after the brushing equipment is connected with a vehicle, the following steps are executed:
acquiring a finished vehicle VIN code, and determining identification information of a current vehicle according to the VIN code;
acquiring an ECU (electronic control unit) supporting flash in the vehicle from a production management system according to the identification information;
and receiving the confirmation information of the ECU to be flashed, judging whether the ECU to be flashed accords with the flashing condition, and if so, transmitting the corresponding software update package to the ECU to be flashed.
2. The software error-proofing method applied to the after-market according to claim 1, wherein judging whether the ECU to be flashed conforms to the flashing condition comprises:
acquiring local identification information and a current software version number of the ECU to be flashed of the vehicle;
acquiring ECU (electronic control unit) applicable information and a software version number of a corresponding software update package, wherein the ECU applicable information comprises ECU identification information applicable to the software update package;
and if the identification information of the ECU to be refreshed is consistent with the ECU application information of the software updating package, and the current software version number of the ECU to be refreshed is lower than the software version number of the software updating package, the ECU to be refreshed accords with the refreshing condition.
3. The software error-proofing method applied to the after-market according to claim 2, wherein the identification information of the ECU includes one or more of a part number and a hardware version number.
4. The software error-proofing method applied to the after-market according to claim 1, after obtaining the configuration information of the ECU to be flashed local to the vehicle, further performing the following operations: and comparing the configuration information of the ECU local to the vehicle with the configuration information of the ECU acquired from the production management system, and if the configuration information of the ECU local to the vehicle is inconsistent, uploading the configuration information of the ECU acquired from the vehicle to the production management system.
5. The software error-proofing method applied to the after-market as recited in claim 1, wherein transmitting the corresponding software update package to the to-be-flashed ECU comprises:
sending a memory erasing request to the ECU to be refreshed, wherein the memory erasing request comprises an erasing initial address and an erasing length;
and transmitting the corresponding software update package to the ECU to be flashed.
6. A brushing device, characterized by being configured to execute the software error-proofing brushing method applied to the after-market according to any one of claims 1-5.
7. A vehicle ECU, connected to the flash device of claim 6, configured to:
receiving a software update package transmitted by the flash device;
respectively carrying out integrity check and validity check on the software update package;
and if the verification is passed, executing software flashing.
8. The vehicle ECU of claim 7, wherein after software flashing, the current software version number of the ECU is read and compared with the software version number of the software update package, and if the current software version number of the ECU is consistent with the software version number of the software update package, the flashing data is correct.
9. The vehicle ECU of claim 7, wherein the integrity check employs a CRC check.
10. A software error-proofing system for after-market applications, comprising a flash device according to claim 6 and a vehicle ECU according to any one of claims 7-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211466877.0A CN115904411A (en) | 2022-11-22 | 2022-11-22 | Software error-proofing method and system applied to after-sale market |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211466877.0A CN115904411A (en) | 2022-11-22 | 2022-11-22 | Software error-proofing method and system applied to after-sale market |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115904411A true CN115904411A (en) | 2023-04-04 |
Family
ID=86484408
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211466877.0A Pending CN115904411A (en) | 2022-11-22 | 2022-11-22 | Software error-proofing method and system applied to after-sale market |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115904411A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643777A (en) * | 2023-07-27 | 2023-08-25 | 江铃汽车股份有限公司 | Automatic after-sale upgrading method and system for automobile software |
-
2022
- 2022-11-22 CN CN202211466877.0A patent/CN115904411A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116643777A (en) * | 2023-07-27 | 2023-08-25 | 江铃汽车股份有限公司 | Automatic after-sale upgrading method and system for automobile software |
| CN116643777B (en) * | 2023-07-27 | 2023-10-03 | 江铃汽车股份有限公司 | Automatic after-sale upgrading method and system for automobile software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108803580B (en) | Method for matching vehicle CAN protocol and related equipment | |
| CN111488165B (en) | Method and system for upgrading vehicle ECU through script | |
| WO2021203604A1 (en) | Update test method and apparatus for vehicle component, and computer device and storage medium | |
| CN114327543A (en) | Online upgrading method and device for vehicle-mounted controller, vehicle and storage medium | |
| CN113703814B (en) | Configuration method, system, storage medium and configuration equipment of Internet of vehicles APP | |
| CN115904411A (en) | Software error-proofing method and system applied to after-sale market | |
| CN111475174A (en) | Device and method for online writing and configuration of vehicle-mounted gateway | |
| CN112000358B (en) | Upgrading method of charging pile and intelligent charging pile | |
| CN113031974A (en) | Software flashing method for transmission control unit | |
| CN116775079A (en) | Vehicle part refreshing method and device, electronic equipment and storage medium | |
| CN111708555A (en) | Data processing device, method and system | |
| CN114675855A (en) | Vehicle software remote upgrading method and device and platform equipment | |
| CN114398066A (en) | Software upgrading method, system and application of domain controller | |
| CN113625690A (en) | Intelligent diagnosis method and system for automobile and mobile terminal | |
| CN115934130A (en) | ECU (electronic control Unit) upgrading method, device, equipment and medium | |
| CN112269374B (en) | Method and device for repairing error data written in electronic control unit | |
| CN115550176A (en) | Internet of vehicles vehicle hardware upgrading method and device and electronic equipment | |
| CN115469899A (en) | Firmware upgrading method, device, equipment, medium and vehicle-mounted system | |
| CN112559000B (en) | Whole vehicle software updating method and device for vehicle | |
| CN114356769A (en) | Software learning method, device, equipment and storage medium | |
| CN116560698B (en) | Online automatic brushing method for flexible intelligent production line of motorcycle | |
| CN112052032A (en) | Flash method and device of electronic control unit | |
| CN114063605B (en) | Remote programming method and device based on step space module and computer equipment | |
| CN114859860A (en) | Method for restoring factory settings of vehicle controller | |
| CN114756258B (en) | ECU software refreshing method and system based on ODX |
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 |