Engine program tamper-proof method and engineering machinery device

Abstract

The present invention relates to the field of vehicle technology, and specifically discloses an engine program anti-tampering method and an engineering machinery device. In the method, S10: Detect whether TBOX is online, and it can be determined whether TBOX is removed. If TBOX is not online, it can be proved that TBOX is removed, and it is further determined that there is a suspicion of tampering with the engine program. Therefore, step S50 is executed: the engine ECU locks the engine. This is to prompt the person who tampers with the engine program to restore the engine program. When TBOX is online, S20 is used to detect whether TBOX is in communication connection with the engine ECU. If so, it means that TBOX and the engine ECU are working normally, and then S60 is executed. If not, it means that the engine ECU program may be tampered with, and S30 is required to determine whether the engine ECU program is tampered with. If it is tampered with, step S50 is executed. If it is not tampered with, it means that there is a fault in TBOX, and then the TBOX needs to be repaired. The engine program anti-tampering method solves the problem that consumers forcibly remove TBOX and then tamper with the engine ECU program.

Description

Technical Field

[0001] The present invention relates to the field of vehicle technology, and in particular to an engine program tamper-proof method and an engineering machinery device. Background Art

[0002] Before entering the market, construction machinery and equipment must meet regulatory requirements (such as environmental protection requirements and safety requirements, etc.), otherwise they cannot be sold legally.

[0003] After construction machinery devices are sold to the market, there are cases where consumers privately tamper with vehicle data. For example, the regulations require that the engine emission standards of National IV vehicles meet certain environmental protection requirements, but some customers tamper with the engine programs of some vehicles in order to reduce maintenance costs and reduce fuel consumption, which puts the OEM in a passive situation.

[0004] To avoid this phenomenon, the existing technology generally connects the engine ECU to the TBOX for communication. The TBOX can transmit the status of the engine ECU to the Internet of Vehicles platform, and then determine whether the engine program has been tampered with privately, so as to prevent consumers from tampering with the engine ECU program privately. However, there are still consumers who forcibly remove the TBOX and then tamper with the engine ECU program.

[0005] In order to eliminate the above problems, there is an urgent need for an engine program anti-tampering method and an engineering machinery device to solve the above problems. Summary of the invention

[0006] The purpose of the present invention is to provide an engine program anti-tampering method and an engineering machinery device to solve the problem in the related art that consumers forcibly dismantle the TBOX and then tamper with the engine ECU program.

[0007] In one aspect, the present invention provides an engine program tamper-proof method, which is implemented by a TBOX online detection device. The engine program tamper-proof method comprises:

[0008] S10: Detect whether the TBOX is online, if yes, execute S20, if no, execute S50;

[0009] S20: Detect whether the TBOX is in communication connection with the engine ECU. If yes, execute S30; if no, execute S40;

[0010] S30: Detect whether the engine ECU program has been tampered with, if yes, execute S50, if not, execute S60;

[0011] S40: determining the TBOX failure;

[0012] S41: the engine ECU enables the engine to execute a countdown lock mode;

[0013] S42: The Internet of Vehicles platform determines whether the TBOX failure affects normal driving. If yes, S43 is executed; if no, S44 is executed.

[0014] S43: Replace the TBOX and execute S44;

[0015] S44: terminating the countdown vehicle locking mode and executing S60;

[0016] S50: The engine ECU locks the engine;

[0017] S60: The engine ECU operates normally.

[0018] As a preferred technical solution of the engine program anti-tampering method, the TBOX online detection device includes a power supply, a first resistor, a second resistor and a detection module. When the TBOX connection port of the TBOX is connected to the ECU connection port of the engine ECU, the power supply, the first resistor and the second resistor form a series circuit. When the TBOX connection port is connected to the ECU connection port, the detection module detects the voltage of the second resistor. When the TBOX connection port is disconnected from the ECU connection port, the detection module detects the voltage of the power supply.

[0019] S10 specifically includes:

[0020] S101: Determine whether the voltage displayed by the detection module is the voltage of the power supply, if yes, execute S102, if no, execute S103;

[0021] S102: Determine that the TBOX is not online, and execute S50;

[0022] S103: Determine that the TBOX is online, and execute S20.

[0023] As a preferred technical solution of the engine program anti-tampering method, S30 includes A1: periodically checking the engine ECU program version information;

[0024] A1 specifically includes:

[0025] A11: Upload the engine ECU program version information to the Internet of Vehicles platform at every preset time a;

[0026] A12: The Internet of Vehicles platform compares the engine ECU program version information to be reviewed with the reviewed engine ECU program version information in the program version library. If they are consistent, A13 is executed; if they are inconsistent, A14 is executed.

[0027] A13: Determine that the engine ECU program has not been tampered with;

[0028] A14: It is determined that the engine ECU program has been tampered with.

[0029] As a preferred technical solution of the engine program anti-tampering method, S30 further includes B1: verifying the upgraded engine ECU program version information;

[0030] B1 specifically includes:

[0031] B11: Upload the engine ECU program version information to be upgraded to the Internet of Vehicles platform;

[0032] B12: The Internet of Vehicles platform records the compliant engine ECU program version information to be upgraded into the program version library;

[0033] B13: writing the engine ECU program to be upgraded into the engine ECU;

[0034] B14: The Internet of Vehicles platform compares the engine ECU program version information to be upgraded written into the engine ECU with the engine ECU program version information recorded in the program version library. If they are consistent, B15 is executed; if they are inconsistent, B16 is executed;

[0035] B15: Determine that the engine ECU program has not been tampered with;

[0036] B16: It is determined that the engine ECU program has been tampered with.

[0037] As a preferred technical solution of the engine program anti-tampering method, S30 further includes C1: verifying the engine ECU program through monitoring data;

[0038] C1 specifically includes:

[0039] C11: extract the data of the engine data monitoring module;

[0040] C12: If the data monitoring module does not generate data or the data of the data monitoring module exceeds the normal value, if yes, execute C13, if no, execute C14;

[0041] C13: Determine that the engine ECU program has been tampered with;

[0042] C14: Determine that the engine ECU program has not been tampered with.

[0043] As a preferred technical solution for the engine program anti-tampering method, in C12, the detection period is a preset value of b days.

[0044] As a preferred technical solution of the engine program anti-tampering method, S43 specifically includes:

[0045] S431: unbinding keys from the TBOX and the engine ECU;

[0046] S432: Replace the TBOX;

[0047] S433: Perform key binding between the newly replaced TBOX and the engine ECU.

[0048] As a preferred technical solution for the engine program anti-tampering method, S44 specifically includes:

[0049] S441: The Internet of Vehicles platform generates a termination password for the countdown vehicle locking mode;

[0050] S442: The engine ECU terminates the countdown vehicle locking mode according to the termination password.

[0051] As a preferred technical solution for the engine program tamper-proof method, S40 also includes: the instrument displays a TBOX fault and reminds maintenance.

[0052] On the other hand, the present invention provides an engineering machinery device, including the engine program anti-tampering method in any of the above schemes to prevent the engine program from being tampered with.

[0053] The beneficial effects of the present invention are:

[0054] The present invention provides an engine program tamper-proof method and an engineering machinery device, which are implemented by a TBOX online detection device. The engine program tamper-proof method comprises S10: detecting whether TBOX is online, if yes, executing S20, otherwise executing S50; S20: detecting whether TBOX is in communication connection with an engine ECU, if yes, executing S30, otherwise executing S40; S30: detecting whether the engine ECU program is tampered with, if yes, executing S50, otherwise executing S60; S40: judging TBOX failure; S41: the engine ECU enables the engine to execute a countdown vehicle locking mode; S42: the vehicle networking platform determines whether the TBOX failure affects normal driving, if yes, executing S43, otherwise executing S44; S43: replacing TBOX and executing S44; S44: terminating the countdown vehicle locking mode and executing S60; S50: the engine ECU locks the engine; S60: the engine ECU works normally. In this method, S10: detect whether TBOX is online, and then determine whether TBOX has been removed. If TBOX is not online, it can be proved that TBOX has been removed, and further determine that there is suspicion of tampering with the engine program. Therefore, step S50 is executed: the engine ECU locks the engine. This is to encourage the person who tampers with the engine program to restore the engine program. When TBOX is online, S20 is used to detect whether TBOX is connected to the engine ECU for communication. If so, it means that TBOX and the engine ECU are working normally, and then S60 is executed. If not, it means that the engine ECU program may be tampered with, and then S30 is required to determine whether the engine ECU program has been tampered with. If it has been tampered with, step S50 is executed. If it has not been tampered with, it means that there is a fault in TBOX, and then TBOX needs to be repaired in time. This engine program anti-tampering method solves the problem that consumers forcibly remove TBOX and then tamper with the engine ECU program. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 Flow chart of the engine program anti-tampering method in an embodiment of the present invention;

[0056] Figure 2 A flowchart of periodically checking engine ECU program version information in an embodiment of the present invention;

[0057] Figure 3 A flowchart of checking the upgraded engine ECU program version information in an embodiment of the present invention;

[0058] Figure 4 Flow chart of verifying the engine ECU program by monitoring data in an embodiment of the present invention;

[0059] Figure 5 1 is a circuit diagram of a TBOX online detection device in an embodiment of the present invention.

[0060] In the figure:

[0061] 1. TBOX; 11. TBOX connection port; 2. Engine ECU; 12. ECU connection port;

[0062] 31. Power supply; 32. First resistor; 33. Second resistor; 34. Detection module. DETAILED DESCRIPTION

[0063] The technical solution of the present invention will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0064] In the description of the present invention, it should be noted that the orientations or positional relationships indicated by the terms "center", "up", "down", "left", "right", "vertical", "horizontal", "inside", "outside", etc. are based on the orientations or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as limiting the present invention. In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. Among them, the terms "first position" and "second position" are two different positions, and the first feature "above", "above" and "above" the second feature include the first feature being directly above and obliquely above the second feature, or simply indicates that the first feature is higher in level than the second feature. The first feature "below", "below" and "below" the second feature include the first feature being directly below and obliquely below the second feature, or simply indicates that the first feature is lower in level than the second feature.

[0065] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0066] Embodiments of the present invention are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and cannot be understood as limiting the present invention.

[0067] like Figure 1~Figure 5 As shown, this embodiment provides an engine program tamper-proof method, which is implemented by a TBOX online detection device. The engine program tamper-proof method includes:

[0068] S10: Check whether TBOX1 is online. If yes, execute S20; if not, execute S50.

[0069] Since TBOX1 can report the status of engine ECU2 to the Internet of Vehicles platform, when the program of engine ECU2 is tampered, the Internet of Vehicles platform will discover it through TBOX1 and then lock the engine. To avoid this phenomenon, TBOX1 is usually removed to achieve tampering of the engine ECU program. To avoid this situation, in this step, by detecting whether TBOX1 is online, it can be determined whether TBOX1 is unplugged. If TBOX1 is not online, it means that TBOX1 is removed. At this time, step S50 is executed: engine ECU2 locks the engine. This is to encourage the person who tampers with the engine program to restore the engine program. When TBOX1 is online, execute S20.

[0070] Alternatively, if Figure 5As shown, the TBOX online detection device 4 includes a power supply 31, a first resistor 32, a second resistor 33 and a detection module 34. When the TBOX connection port 11 of the TBOX1 is connected to the ECU connection port 12 of the engine ECU2, the power supply 31, the first resistor 32 and the second resistor 33 form a series circuit. When the TBOX connection port 11 is connected to the ECU connection port 12, the detection module 34 detects the voltage of the second resistor 33. When the TBOX connection port 11 is disconnected from the ECU connection port 12, the detection module 34 detects the voltage of the power supply 31. In this embodiment, the power supply 31 and the first resistor 32 are integrated on the engine ECU2, and the second resistor 33 is integrated on the TBOX1. The power supply 31, the first resistor 32 and the second resistor 33 are connected in series in sequence. When the TBOX connection port 11 is connected to the ECU connection port 12, the power supply 31, the first resistor 32 and the second resistor 33 form a series current. The detection module 34 is a voltmeter. The first terminal of the detection module 34 is electrically connected to the line between the first resistor 32 and the second resistor 33, and the second terminal of the detection module 34 is electrically connected to the line between the ECU connection port 12 and the power supply 31. When the TBOX connection port 11 is connected to the ECU connection port 12, the detection module 34 measures the voltage of the second resistor 33. When the TBOX connection port 11 is disconnected from the ECU connection port 12, the detection module 34 measures the voltage of the power supply 31.

[0071] Therefore, S10 specifically includes:

[0072] S101: Determine whether the voltage displayed by the detection module 34 is the voltage of the power supply 31, if yes, execute S102, if not, execute S103.

[0073] In this step, when the detection module 34 measures the voltage of the power supply 31, the TBOX connection port 11 is disconnected from the ECU connection port 12, indicating that TBOX1 has been removed. When the detection module 34 measures a voltage other than the power supply 31, the detection module 34 measures the voltage of the second resistor 33, indicating that the TBOX connection port 11 is connected to the ECU connection port 12, indicating that TBOX1 has not been removed.

[0074] S102: Determine that TBOX1 is not online, and execute S50.

[0075] S103: Determine that the TBOX1 is online, and execute S20.

[0076] S20: Detect whether TBOX1 is in communication connection with the engine ECU2. If yes, execute S30; if not, execute S40.

[0077] In this step, S20 is used to detect whether TBOX1 is in communication with the engine ECU2. If yes, it means that TBOX1 and the engine ECU2 are working normally, and then S60 is executed. If no, it means that the engine ECU program may be tampered with, and then S30 is required to determine whether the engine ECU program is tampered with.

[0078] S30: Detect whether the engine ECU program has been tampered with, if yes, execute S50, if not, execute S60;

[0079] This step specifically includes three parallel methods A1, B1 and C1 for determining whether the engine ECU program has been tampered with in different situations, but is not limited to these three.

[0080] A1: Periodically check the engine ECU program version information. In the daily operation of engineering machinery, A1 is a periodic detection method. After reaching the preset period, A1 is automatically triggered.

[0081] A1 specifically includes:

[0082] A11: Upload the engine ECU program version information to the Internet of Vehicles platform at preset intervals a.

[0083] In this step, the engine ECU program version information is uploaded to the Internet of Vehicles platform via TBOX1.

[0084] A12: The Internet of Vehicles platform compares the engine ECU program version information to be reviewed with the reviewed engine ECU program version information in the program version library. If they are consistent, A13 is executed; if they are inconsistent, A14 is executed.

[0085] In this step, the version information of the running program of each engine ECU2 is unique and is pre-stored in the program version library of the Internet of Vehicles platform. When the running program of the engine ECU2 has not been tampered with, the engine ECU program version information is consistent with the reviewed engine ECU program version information in the program version library. When the engine ECU program version information is inconsistent with the reviewed engine ECU program version information in the program version library, it means that the engine ECU program has been tampered with.

[0086] A13: Determine that the engine ECU program has not been tampered with;

[0087] A14: It is determined that the engine ECU program has been tampered with.

[0088] Optionally, S30 also includes B1: checking the version information of the upgraded engine ECU program; B1 is aimed at the problem of unauthorized tampering during the later engine ECU program upgrade process.

[0089] B1 specifically includes:

[0090] B11: Upload the engine ECU program version information to be upgraded to the Internet of Vehicles platform.

[0091] In this step, the engine ECU programs to be upgraded are different for different models. In some special working scenarios, the engine ECU programs to be upgraded even need to be customized. Therefore, when upgrading the engine ECU program, it is necessary to upload the engine ECU program to be upgraded to the Internet of Vehicles platform for review.

[0092] B12: The Internet of Vehicles platform will include the compliant engine ECU program version information to be upgraded into the program version library.

[0093] In this step, if the reviewed engine ECU program to be upgraded complies with relevant regulations, such as environmental protection regulations, traffic safety regulations, etc., the version information of the engine ECU program to be upgraded is then recorded in the program version library to facilitate the program upgrade of the engine ECU.

[0094] B13: Write the engine ECU program to be upgraded into the engine ECU2.

[0095] B14: The Internet of Vehicles platform compares the engine ECU program version information written into the engine ECU2 with the engine ECU program version information included in the program version library. If they are consistent, B15 is executed; if they are inconsistent, B16 is executed.

[0096] In this step, when the upgraded engine ECU program is inconsistent with the engine ECU program version information recorded in the program version library, it indicates that the engine ECU program is different from the engine ECU program recorded in the program version library.

[0097] B15: Determine that the engine ECU program has not been tampered with.

[0098] B16: The engine ECU program is determined to be tampered with.

[0099] Optionally, S30 further includes C1: verifying the engine ECU program through monitoring data.

[0100] In this step, when the engine is running, the SCR downstream NOx sensor, SCR inlet temperature sensor and other sensors on the engine monitor data in real time to determine the working state of the engine, and then determine whether the engine is working under the control of the compliant engine ECU program.

[0101] C1 specifically includes:

[0102] C11: Extract data from the engine data monitoring module.

[0103] In this step, real-time monitoring data of the SCR downstream NOx sensor, SCR inlet temperature sensor, etc. can be extracted.

[0104] C12: If the data monitoring module does not generate data or the data of the data monitoring module exceeds the normal value, if yes, execute C13, if no, execute C14;

[0105] In this step, if the data monitoring module does not generate data, it means that the data monitoring module is not working, and thus cannot monitor the working condition of the engine. The Internet of Vehicles platform cannot determine the working condition of the engine, and it can be determined that the engine ECU program has been tampered with. At the same time, if the data of the data monitoring module exceeds the normal value, it can be determined that the engine ECU program has been tampered with.

[0106] Optionally, in C12, the detection period is a preset value of b days. Specifically, b can be one week or two weeks.

[0107] C13: The engine ECU program is determined to be tampered with.

[0108] C14: Determine that the engine ECU program has not been tampered with.

[0109] S40: Determine whether TBOX1 is faulty.

[0110] In this step, when there is no communication connection between TBOX1 and the engine ECU2, it indicates that a fault has occurred in TBOX1.

[0111] At this time, the instrument on the engineering machinery device shows TBOX1 failure, prompting maintenance.

[0112] S41: The engine ECU 2 enables the engine to execute the countdown lock mode.

[0113] In this step, the engine ECU2 starts the countdown car lock mode, and when the countdown car lock mode ends, the engine will lock the car.

[0114] S42: The Internet of Vehicles platform determines whether the TBOX1 fault affects normal driving. If yes, execute S43; if no, execute S44.

[0115] In this step, the Internet of Vehicles platform evaluates the fault of TBOX1. If it affects normal driving, S43 is executed; otherwise, S44 is executed.

[0116] S43: Replace TBOX1 and execute S44;

[0117] S43 specifically includes:

[0118] S431: Unbind the keys of TBOX1 and engine ECU2.

[0119] S432: Replace TBOX1.

[0120] S433: Bind the keys of the newly replaced TBOX1 and the engine ECU2.

[0121] Since TBOX1 and engine ECU2 are bound together, replacing any one of them will cause the vehicle to be locked. At the same time, when one of them is damaged, the communication key can be replaced by setting the replaced part to the previous key. Otherwise, it cannot be used normally.

[0122] S44: terminating the countdown vehicle locking mode and executing S60;

[0123] S44 specifically includes:

[0124] S441: The Internet of Vehicles platform generates a termination password for the countdown vehicle lock mode.

[0125] S442: The engine ECU 2 terminates the countdown vehicle locking mode according to the termination password.

[0126] In this step, the termination password can be input through the virtual keyboard on the instrument, or a KEY can be generated from the termination password and the countdown locking mode can be terminated by inserting the KEY into the input jack of TBOX1.

[0127] S50: The engine ECU 2 locks the engine.

[0128] S60: The engine ECU 2 operates normally.

[0129] In this method, S10: detect whether TBOX1 is online, and then determine whether TBOX1 has been removed. If TBOX1 is not online, it can be proved that TBOX1 has been removed, and further determine that there is a suspicion of tampering with the engine program. Therefore, step S50 is executed: the engine ECU2 locks the engine. This is to encourage the person who tampers with the engine program to restore the engine program. When TBOX1 is online, S20 is used to detect whether TBOX1 is in communication connection with the engine ECU2. If so, it means that TBOX1 and the engine ECU2 are working normally, and then S60 is executed. If not, it means that the engine ECU program may be tampered with, and then S30 is needed to determine whether the engine ECU program has been tampered with. If it has been tampered with, step S50 is executed. If it has not been tampered with, it means that TBOX1 has a fault, and then TBOX1 needs to be repaired in time. This engine program anti-tampering method solves the problem that consumers forcibly remove TBOX1 and then tamper with the engine ECU program.

[0130] This embodiment provides an engineering machinery device, including the engine program anti-tampering method in the above scheme to prevent the engine program from being tampered with.

[0131] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the embodiments of the present invention. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all the embodiments here. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the protection scope of the claims of the present invention.

Claims

1. An engine program anti-tampering method, characterized in that: The method is implemented by a TBOX online detection device, wherein the TBOX online detection device is capable of detecting whether the TBOX (1) is online. The method for preventing the engine program from being tampered with comprises: S10: Detect whether the TBOX (1) is online, if yes, execute S20, if no, execute S50; S20: Detect whether the TBOX (1) is in communication connection with the engine ECU (2); if yes, execute S30; if no, execute S40; S30: Detect whether the engine ECU program has been tampered with, if yes, execute S50, if not, execute S60; S40: determining whether the TBOX (1) is faulty; S41: the engine ECU (2) causes the engine to execute a countdown locking mode; S42: The Internet of Vehicles platform determines whether the TBOX (1) fault affects normal driving. If yes, S43 is executed; if no, S44 is executed. S43: Replace the TBOX (1) and execute S44; S44: terminating the countdown vehicle locking mode and executing S60; S50: the engine ECU (2) locks the engine; S60: The engine ECU (2) operates normally.

2. The engine program anti-tampering method according to claim 1, characterized in that: The TBOX online detection device comprises a power supply (31), a first resistor (32), a second resistor (33) and a detection module (34); when the TBOX connection port (11) of the TBOX (1) is connected to the ECU connection port (12) of the engine ECU (2), the power supply (31), the first resistor (32) and the second resistor (33) form a series circuit; when the TBOX connection port (11) is connected to the ECU connection port (12), the detection module (34) detects the voltage of the second resistor (33); when the TBOX connection port (11) is disconnected from the ECU connection port (12), the detection module (34) detects the voltage of the power supply (31); S10 specifically includes: S101: determining whether the voltage displayed by the detection module (34) is the voltage of the power supply (31); if yes, executing S102; if no, executing S103; S102: Determine that the TBOX (1) is not online, and execute S50; S103: Determine that the TBOX (1) is online, and execute S20.

3. The engine program anti-tampering method according to claim 1, characterized in that: S30 includes A1: periodically checking the engine ECU program version information; A1 specifically includes: A11: Upload the engine ECU program version information to the Internet of Vehicles platform at every preset time a; A12: The Internet of Vehicles platform compares the engine ECU program version information to be reviewed with the reviewed engine ECU program version information in the program version library. If they are consistent, A13 is executed; if they are inconsistent, A14 is executed. A13: Determine that the engine ECU program has not been tampered with; A14: It is determined that the engine ECU program has been tampered with.

4. The engine program anti-tampering method according to claim 1, characterized in that: S30 also includes B1: checking the updated engine ECU program version information; B1 specifically includes: B11: Uploading the engine ECU program version information to be upgraded to the Internet of Vehicles platform; B12: The Internet of Vehicles platform records the compliant engine ECU program version information to be upgraded into the program version library; B13: writing the engine ECU program to be upgraded into the engine ECU (2); B14: the vehicle networking platform compares the engine ECU program version information written into the engine ECU (2) with the engine ECU program version information recorded in the program version library. If they are consistent, B15 is executed; if they are inconsistent, B16 is executed. B15: Determine that the engine ECU program has not been tampered with; B16: It is determined that the engine ECU program has been tampered with.

5. The engine program anti-tampering method according to claim 1, characterized in that: S30 also includes C1: verifying the engine ECU program through monitoring data; C1 specifically includes: C11: extract the data of the engine data monitoring module; C12: If the data monitoring module does not generate data or the data of the data monitoring module exceeds the normal value, if yes, execute C13, if no, execute C14; C13: Determine that the engine ECU program has been tampered with; C14: Determine that the engine ECU program has not been tampered with.

6. The engine program anti-tampering method according to claim 5, characterized in that: In C12, the detection period is a preset value of b days.

7. The engine program anti-tampering method according to claim 1, characterized in that: S43 specifically includes: S431: unbinding keys of the TBOX (1) and the engine ECU (2); S432: replacing the TBOX (1); S433: Perform key binding on the newly replaced TBOX (1) and the engine ECU (2).

8. The engine program anti-tampering method according to claim 1, characterized in that: S44 specifically includes: S441: The Internet of Vehicles platform generates a termination password for the countdown vehicle locking mode; S442: The engine ECU (2) terminates the countdown vehicle locking mode according to the termination password.

9. The engine program anti-tampering method according to claim 1, characterized in that: S40 also includes: the instrument displays TBOX (1) fault and reminds you to repair it.

10. An engineering machinery device, characterized in that: The engine program tamper-proof method according to any one of claims 1 to 9 is used to prevent the engine program from being tampered with.

Images