Communication topology of diesel engine controller with built-in tbox

Abstract

This invention discloses a communication topology for a diesel engine controller with a built-in TBOX, relating to an ECU. The TBOX is integrated into the diesel engine controller, and communication between the TBOX and the ECU is achieved via a UART link carrying the UDS and XCP protocols, enabling data interaction between the TBOX and the ECU. This invention achieves an integrated design of the TBOX and ECU, making the engine more intelligent and the vehicle more information-driven; furthermore, the UART communication protocol in the diesel engine controller communication topology with a built-in TBOX enables command communication using the UDS and XCP protocols, effectively supporting the implementation of various TBOX functions.

Description

Technical Field

[0001] This invention relates to an ECU, and more specifically, to a communication topology for a diesel engine controller with a built-in TBOX. Background Technology

[0002] The Vehicle-to-Everything (TBOX) remote communication terminal is a product integrating vehicle network and wireless communication functions, providing network services. It is typically installed below the dashboard. The TBOX communicates with the engine via the CAN bus, acquiring real-time vehicle information including fuel consumption, engine coolant temperature, engine speed, vehicle mileage, current speed, battery voltage, intake air pressure, coolant temperature, oxygen sensor voltage, engine load, throttle opening, airflow, GPS vehicle location, etc., and reporting this information in real time, thus achieving real-time monitoring of vehicle driving data. In addition to real-time information reporting, the TBOX can also remotely diagnose vehicle faults and remotely upgrade vehicle software. The TBOX is crucial for vehicle information systems. Currently, most TBOX terminals on the market are independent of the engine and require manual installation. Because the TBOX is installed separately from the engine in a location on the vehicle, it communicates with the engine via the vehicle's CAN bus. Figure 1 As shown. This not only leads to high installation costs, but also makes the communication between the later-installed TBOX and the ECU susceptible to interference from other devices in the vehicle. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide a communication topology structure for a diesel engine controller with built-in TBOX, which addresses the shortcomings of the existing technology and realizes the integrated design of TBOX and ECU, and can well support the implementation of various functions of TBOX.

[0004] The present invention discloses a communication topology for a diesel engine controller with a built-in TBOX, wherein the TBOX is built into the diesel engine controller, and the TBOX communicates with the ECU through a UART link for carrying the UDS protocol and the XCP protocol, so as to realize data interaction between the TBOX and the ECU.

[0005] As a further improvement, the TBOX is equipped with a TBOX processing unit and a TBOX protocol processing unit, and the ECU is equipped with an MCU processing unit and an MCU protocol processing unit;

[0006] After receiving the instruction, the TBOX processing unit performs scheduling processing according to the instruction to package the instruction into data in UART protocol format, and then delivers it to the TBOX protocol processing unit; the TBOX protocol processing unit transmits the data to the MCU protocol processing unit and the MCU processing unit for processing via the UART link.

[0007] Furthermore, the TBOX is equipped with a cloud command processing unit for communication between the TBOX and the cloud.

[0008] Furthermore, when the cloud sends a fault diagnosis command, the cloud command processing unit generates a diagnosis task based on the fault diagnosis command and sends the diagnosis task to the TBOX processing unit. The TBOX processing unit sends a start diagnosis command to the TBOX protocol processing unit based on the diagnosis task. The TBOX protocol processing unit packages the fault diagnosis command into a UDS protocol command and then transmits the UDS protocol command to the MCU protocol processing unit in the form of a protocol frame via a UART link. The MCU protocol processing unit parses the protocol frame to obtain the fault diagnosis command and sends a start diagnosis command to the MCU processing unit so that the MCU processing unit can perform fault diagnosis on the engine and collect diagnostic data. Then, the diagnostic data is reported to the MCU protocol processing unit, which packages the diagnostic data and transmits the packaged diagnostic data to the TBOX protocol processing unit via a UART link. After parsing the received diagnostic data, the TBOX protocol processing unit reports it to the cloud sequentially through the TBOX processing unit and the cloud command processing unit.

[0009] Furthermore, when the cloud sends a template instruction, the cloud command processing unit generates a data acquisition task based on the template instruction and sends the data acquisition task to the TBOX processing unit. The TBOX processing unit sends a start acquisition instruction to the TBOX protocol processing unit based on the data acquisition task. The TBOX protocol processing unit packages the template instruction into an XCP protocol command and then transmits the XCP protocol command as a protocol frame to the MCU protocol processing unit via a UART link. The MCU protocol processing unit parses the protocol frame to obtain the template instruction and sends a start acquisition instruction to the MCU processing unit so that the MCU processing unit can collect the engine's operating data. Then, the collected operating data is reported to the MCU protocol processing unit, which packages the operating data and transmits the packaged operating data to the TBOX protocol processing unit via a UART link. After parsing the received packaged operating data, the TBOX protocol processing unit reports it to the cloud sequentially through the TBOX processing unit and the TBOX cloud command processing unit.

[0010] Furthermore, the protocol frame consists of a start symbol, a command unit, a data unit length, a data unit, and a checksum; wherein, the command unit is used to write an identification code for recognizing UDS protocol commands and XCP protocol commands.

[0011] Furthermore, the command unit can also be written with the identification code of the heartbeat command, which is used to synchronize the transmission status of the TBOX protocol processing unit and the MCU protocol processing unit.

[0012] Beneficial effects

[0013] The advantages of this invention are as follows: By embedding the TBOX into the diesel engine controller, and with the TBOX and ECU communicating via a UART link, an integrated design of the TBOX and ECU is achieved, making the engine more intelligent and the vehicle more information-based. Furthermore, the UART communication protocol in the diesel engine controller communication topology with the TBOX integrated enables command communication using the UDS and XCP protocols, effectively supporting the implementation of various TBOX functions. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of the traditional communication method between the TBOX and the ECU;

[0015] Figure 2 This is a schematic diagram of the communication topology of the diesel engine controller with built-in TBOX according to the present invention;

[0016] Figure 3 This is a schematic diagram illustrating the functional interaction of the diesel engine controller with built-in TBOX according to the present invention;

[0017] Figure 4 This is a schematic diagram of the operation flow of the communication topology protocol for the diesel engine controller with built-in TBOX according to the present invention;

[0018] Figure 5 This is a schematic diagram of the UDS protocol function interaction of the diesel engine controller with built-in TBOX of the present invention;

[0019] Figure 6 This is a schematic diagram of the fault diagnosis process of the diesel engine controller UDS with built-in TBOX of the present invention;

[0020] Figure 7 This is a schematic diagram of the XCP protocol functional interaction of the diesel engine controller with built-in TBOX of the present invention;

[0021] Figure 8 This is a schematic diagram of the XCP data acquisition process of the diesel engine controller with built-in TBOX according to the present invention. Detailed Implementation

[0022] The present invention will be further described below with reference to embodiments, but this does not constitute any limitation on the present invention. Any limited modifications made by any person within the scope of the claims of the present invention are still within the scope of the claims of the present invention.

[0023] See Figures 2-3 This invention discloses a communication topology for a diesel engine controller with a built-in TBOX. The TBOX is embedded within the diesel engine controller, and communication between the TBOX and the ECU occurs via a UART link carrying the UDS and XCP protocols, thereby enabling data exchange between the TBOX and the ECU. Figure 2 As shown in the overall framework diagram, the relevant functions of TBOX are integrated into the diesel engine controller as a module. Specifically, TBOX and the engine ECU communicate with the MCU through UART (Universal Asynchronous Receiver / Transmitter). TBOX becomes part of the ECU, thereby realizing point-to-point communication between TBOX and ECU, which is not affected by the external environment and improves anti-interference capability.

[0024] Because the communication link between the ECU and TBOX has been changed from the original CAN bus to UART communication, some functions that were originally carried by the CAN bus must now be carried by the UART link. The interaction between the TBOX and ECU is mainly implemented using the UDS (Unified Diagnostic Services) protocol and the XCP (Universal Measurement and Calibration Protocol), such as... Figure 3 As shown.

[0025] When carrying UDS and XCP protocol functions via a UART link, a corresponding protocol frame must be designed on the UART link to drive them. In this embodiment, the protocol frame consists of a start symbol, command unit, data unit length, data unit, and checksum. The structure of the protocol frame is shown in the table below:

[0026] start symbol Command Unit Data unit length Data Unit Verification code 2 1 2 N 1 .

[0027] The data unit contains the corresponding data; the checksum uses an XOR algorithm to verify the integrity of the data frame; the command unit is used to write identification codes for recognizing UDS protocol commands and XCP protocol commands. Additionally, the command unit can also write the identification code for the heartbeat command, used to synchronize the transmission status of the TBOX protocol processing unit and the MCU protocol processing unit.

[0028] like Figure 4 As shown, to implement the carrying of these protocols, the TBOX in this embodiment includes a TBOX processing unit and a TBOX protocol processing unit, while the ECU includes an MCU processing unit and an MCU protocol processing unit. After receiving an instruction, the TBOX processing unit performs scheduling processing according to the instruction, packaging the instruction into UART protocol format data, and then delivering it to the TBOX protocol processing unit. The TBOX protocol processing unit transmits the data to the MCU protocol processing unit and the MCU processing unit for processing via the UART link. Furthermore, the TBOX includes a cloud command processing unit for communication between the TBOX and the cloud.

[0029] When the TBOX needs to implement UDS-related functions, it sends a UDS command data frame to the ECU, which then responds and performs the necessary processing. UDS-related functions mainly include parameter data reading, fault diagnosis, and program flashing. The interaction of the built-in TBOX with the engine UDS protocol is as follows: Figure 5 The specific process is as follows: Figure 6 As shown.

[0030] from Figure 6As can be seen, when a fault diagnosis command is issued from the cloud, the cloud command processing unit generates a diagnosis task based on the command and sends it to the TBOX processing unit. The TBOX processing unit then sends a start diagnosis command to the TBOX protocol processing unit based on the diagnosis task. The TBOX protocol processing unit packages the fault diagnosis command into a UDS protocol command and transmits it as a protocol frame to the MCU protocol processing unit via the UART link. The MCU protocol processing unit parses the protocol frame to obtain the fault diagnosis command and sends a start diagnosis command to the MCU processing unit, enabling it to perform engine fault diagnosis and collect diagnostic data. The diagnostic data is then reported to the MCU protocol processing unit, which packages the data and transmits it to the TBOX protocol processing unit via the UART link. Finally, the TBOX protocol processing unit parses the received diagnostic data and reports it to the cloud sequentially through the TBOX processing unit and the cloud command processing unit.

[0031] When the TBOX needs to perform XCP-related functions, it sends XCP command data frames to the ECU, which then responds and processes them. The XCP-related functions primarily implement data acquisition. The interaction of the engine XCP protocol functions with the built-in TBOX is as follows: Figure 7 The specific process is as follows: Figure 8 As shown.

[0032] from Figure 8 As can be seen, when the cloud issues a template instruction, the cloud command processing unit generates a data acquisition task based on the template instruction and sends the data acquisition task to the TBOX processing unit. The TBOX processing unit sends a start acquisition command to the TBOX protocol processing unit based on the data acquisition task. The TBOX protocol processing unit packages the template instruction into an XCP protocol command and then transmits the XCP protocol command as a protocol frame to the MCU protocol processing unit via the UART link. The MCU protocol processing unit parses the protocol frame to obtain the template instruction and sends a start acquisition command to the MCU processing unit, enabling the MCU processing unit to acquire engine operating data. The acquired operating data is then reported to the MCU protocol processing unit, which packages the operating data and transmits the packaged operating data to the TBOX protocol processing unit via the UART link. The TBOX protocol processing unit parses the received packaged operating data and then reports it to the cloud sequentially through the TBOX processing unit and the TBOX cloud command processing unit.

[0033] Because this embodiment integrates the TBOX into the diesel engine controller, the TBOX and ECU communicate via a UART link, achieving an integrated design of the TBOX and ECU, making the engine more intelligent and the vehicle more information-driven. Furthermore, the UART communication protocol in the diesel engine controller communication topology with the TBOX integrated enables command communication using the UDS and XCP protocols, effectively supporting the implementation of various TBOX functions.

[0034] The above description is only a preferred embodiment of the present invention. It should be noted that those skilled in the art can make several modifications and improvements without departing from the structure of the present invention, and these will not affect the effectiveness of the implementation of the present invention or the practicality of the patent.

Claims

1. A communication method for a diesel engine controller with a built-in TBOX, characterized in that, The TBOX is built into the diesel engine controller, and the TBOX communicates with the ECU through a UART link for carrying the UDS protocol and XCP protocol, so as to realize data interaction between the TBOX and the ECU. Among them, UDS protocol commands or XCP protocol commands are encapsulated according to a custom protocol frame and then transmitted through the UART link; The protocol frame consists of a start symbol, a command unit, a data unit length, a data unit, and a checksum; the checksum uses an XOR algorithm to verify the integrity of the data frame; the command unit is used to write an identification code for recognizing UDS protocol commands and XCP protocol commands.

2. The communication method for a diesel engine controller with a built-in TBOX according to claim 1, characterized in that, The TBOX includes a TBOX processing unit and a TBOX protocol processing unit, and the ECU includes an MCU processing unit and an MCU protocol processing unit. After receiving the instruction, the TBOX processing unit performs scheduling processing according to the instruction to package the instruction into data in UART protocol format, and then delivers it to the TBOX protocol processing unit; the TBOX protocol processing unit transmits the data to the MCU protocol processing unit and the MCU processing unit for processing via the UART link.

3. The communication method for a diesel engine controller with a built-in TBOX according to claim 2, characterized in that, The TBOX is equipped with a cloud command processing unit, which is used to realize communication between the TBOX and the cloud.

4. The communication method for a diesel engine controller with a built-in TBOX according to claim 3, characterized in that, When the cloud sends a fault diagnosis command, the cloud command processing unit generates a diagnosis task based on the fault diagnosis command and sends the diagnosis task to the TBOX processing unit. The TBOX processing unit sends a start diagnosis command to the TBOX protocol processing unit based on the diagnosis task. The TBOX protocol processing unit packages the fault diagnosis command into a UDS protocol command and then transmits the UDS protocol command to the MCU protocol processing unit in the form of a protocol frame via a UART link. The MCU protocol processing unit parses the protocol frame to obtain the fault diagnosis command and sends a start diagnosis command to the MCU processing unit so that the MCU processing unit can perform fault diagnosis on the engine and collect diagnostic data. Then, the diagnostic data is reported to the MCU protocol processing unit, which packages the diagnostic data and transmits the packaged diagnostic data to the TBOX protocol processing unit via a UART link. After parsing the received diagnostic data, the TBOX protocol processing unit reports it to the cloud sequentially through the TBOX processing unit and the cloud command processing unit.

5. A communication method for a diesel engine controller with a built-in TBOX according to claim 3, characterized in that, When the cloud sends a template instruction, the cloud command processing unit generates a data acquisition task based on the template instruction and sends the data acquisition task to the TBOX processing unit. The TBOX processing unit sends a start acquisition command to the TBOX protocol processing unit based on the data acquisition task. The TBOX protocol processing unit packages the template instruction into an XCP protocol command and then transmits the XCP protocol command as a protocol frame to the MCU protocol processing unit via a UART link. The MCU protocol processing unit parses the protocol frame to obtain the template instruction and sends a start acquisition command to the MCU processing unit, enabling the MCU processing unit to acquire engine operating data. The acquired operating data is then reported to the MCU protocol processing unit, which packages the operating data and transmits the packaged operating data to the TBOX protocol processing unit via a UART link. After parsing the received packaged runtime data, the TBOX protocol processing unit reports it to the cloud sequentially through the TBOX processing unit and the TBOX cloud command processing unit.

6. The communication method for a diesel engine controller with a built-in TBOX according to claim 1, characterized in that, The command unit can also write the identification code of the heartbeat command, which is used to synchronize the transmission status of the TBOX protocol processing unit and the MCU protocol processing unit.

Images