A bus-based engine speed and torque temporary control method and system

Abstract

This invention discloses a bus-based method and system for temporary engine speed and torque control. When multiple external devices simultaneously send temporary speed and torque control requests to the same engine ECU via the CAN bus, the system compares the multiple messages pairwise based on the priority information and control mode information carried in the TSC message and a preset competition mechanism. This determines a unique winning message from the multiple concurrent TSC requests, avoiding command overwriting and frequent state transitions, thus ensuring the stability and reliability of power output. Simultaneously, the temporary control target obtained based on the winning message competes with other control requests from the engine itself for priority, and the final control target is determined based on the competition result. This ensures that external temporary requests no longer override the engine's own safety protection logic and speed regulation characteristics, eliminating potential safety hazards.

Description

Technical Field

[0001] This invention belongs to the field of engine power control and relates to a bus-based temporary control method and system for engine speed and torque. Background Technology

[0002] As automobiles become increasingly electrified, the number of electronic control units is growing, and their interconnections are becoming more frequent, necessitating real-time data communication. The CAN bus, with its distributed and real-time control capabilities, is widely used in automotive local area networks. The J1939 protocol, based on the CAN bus, has established a complete communication protocol standard. Achieving high-precision, fast-response coordinated speed or torque control via the bus is increasingly becoming a key technology in new energy powertrain systems.

[0003] In practical applications, an engine often needs to respond to multiple temporary speed and torque control requests simultaneously sent by external devices via the CAN bus. However, existing technologies lack a complete, reasonable, and orderly conflict resolution mechanism to effectively filter and sort multiple concurrent TSC requests. This makes it difficult for the ECU to determine the only reasonable and highest-priority control command when faced with multiple requests, which can easily lead to problems such as control logic confusion, command overwriting, or frequent changes in execution state. Furthermore, even if a unique external request is selected, existing technologies lack a method to effectively coordinate and prioritize this temporary external request with the engine's inherent control logic and physical safety limitations. This can lead to external requests potentially overriding the engine's own safety protection, posing a safety hazard. Summary of the Invention

[0004] The purpose of this invention is to solve the problem of the lack of a conflict resolution mechanism for temporary speed or torque control requests from multiple external devices based on a bus in the prior art, and to provide a bus-based method and system for temporary control of engine speed and torque.

[0005] To achieve the above objectives, the present invention employs the following technical solution: A bus-based temporary control method for engine speed and torque includes the following steps: S1: Obtain the temporary speed and torque control (TSC) message, verify the TSC message, if the verification passes, parse the TSC message and obtain the parsed message data, if the verification fails, discard the current TSC message; S2: Based on the parsed message data, according to the priority information and control mode information carried by the TSC message, and combined with the preset competition mechanism, multiple TSC messages are compared in pairs, and a unique winning TSC message is determined from the multiple TSC messages. S3: Obtain the temporary control target based on the winning TSC message, compete for priority with other control requests of the engine itself, and determine the engine's final control target based on the competition result.

[0006] A further improvement of the present invention is that: S2 includes the following steps: TSC messages indicating TSC override control failure and non-temporary control are filtered out in order of priority. Based on the filtered messages, a pairwise comparison is performed according to a preset competition mechanism to determine the unique winning TSC message from multiple TSC messages. The preset competition mechanism includes: Higher communication priority is higher than lower communication priority; Speed ​​control mode and torque control mode have higher priority than speed limit control mode and torque limit control mode. When one TSC message is in speed control mode and the other is in torque control mode, the message with the older timestamp has higher priority. When both TSC messages are in speed control mode or torque control mode, the message with the older timestamp has higher priority. When both TSC messages are in either speed limit control mode or torque limit control mode, the message with the smaller torque limit value or speed limit value has higher priority. When the torque limit value and speed limit value are the same, the message with the older timestamp has higher priority.

[0007] S2 includes the following steps: S2.1: Determine whether the TSC control mode of the current TSC message is TSC overrun control failure. If yes, the current TSC message exits TSC contention. If not, execute S2.2. S2.2: Determine whether the control purpose of the current TSC message is temporary control. If yes, execute S2.3; otherwise, the current TSC message exits the TSC contention. S2.3: Determine if it is a single TSC message. If yes, complete the message verification and execute the current message. If no, execute S2.4. S2.4: Determine whether the two TSC packets come from different source addresses. If yes, proceed to S2.5; otherwise, select the latest packet. S2.5: Determine if the two TSC messages have the same priority. If yes, proceed to S2.6; otherwise, select the message with the higher priority. S2.6: Determine if two TSC messages have the same TSC control mode. If yes, execute S2.7. If no, the speed control mode and torque control mode have higher priority than the speed limit control mode and torque limit control mode. If one TSC message is in speed control mode and the other TSC message is in torque control mode, select the message with the older timestamp. S2.7: Determine whether the control modes of the two TSC messages are the same. If the control modes of the two TSC messages are both speed control mode or torque control mode, select the message with the older timestamp. If the control modes of the two TSC messages are both speed limit control mode or torque limit control mode, execute S2.8. S2.8: Determine whether the torque limit values ​​of the two TSC messages are the same. If yes, proceed to S2.9; otherwise, the message with the smaller torque limit value has higher priority. S2.9: Determine whether the speed limit values ​​of the two TSC messages are the same. If yes, execute S2.10; otherwise, the message with the smaller speed limit value has higher priority. S2.10: If the torque limit and speed limit values ​​of two TSC messages are the same, the message with the older timestamp has higher priority.

[0008] In step S1, when obtaining the Temporary Speed ​​and Torque Control (TSC) message, the information carried by the TSC message includes the target device ID, the message source device ID, the control request mode, the message priority, the engine request speed control conditions, the engine speed request value, the engine speed limit value, the integer part of the torque request value, the integer part of the torque limit value, the fractional part of the torque request value, the fractional part of the torque limit value, and the control purpose.

[0009] When verifying TSC messages, the verification is performed based on the J1939 standard communication protocol.

[0010] S3 includes the following steps: The winning TSC message participates in the competition for engine control requests, and the final engine control information is determined by the engine limitation information. Based on the final control information, the fuel injection quantity and injection phase of the engine are controlled to enable the engine to reach the corresponding target speed and target torque control values.

[0011] A bus-based temporary engine speed and torque control system includes: The TSC message verification module is used to acquire and verify the temporary speed and torque control TSC messages. If the verification passes, the TSC message is parsed and the parsed message data is obtained. If the verification fails, the current TSC message is discarded. The multi-message contention adjudication module is used to compare multiple TSC messages pairwise based on the parsed message data, priority information and control mode information carried by the TSC message, and a preset contention mechanism, and adjudicate the unique winning TSC message from the multiple TSC messages. The control target output module is used to obtain the temporary control target based on the winning TSC message, compete for priority with other control requests of the engine itself, and determine the engine's final control target based on the competition result.

[0012] A computer program product includes a computer program that, when executed by a processor, implements any one of the methods described.

[0013] A terminal device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the steps of any of the methods described above.

[0014] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described herein.

[0015] Compared with the prior art, the present invention has the following beneficial effects: This invention discloses a bus-based temporary engine speed and torque control method. When multiple external devices simultaneously send temporary speed and torque control requests to the same engine ECU via the CAN bus, the method compares the multiple messages pairwise based on the priority information and control mode information carried in the TSC message and a preset competition mechanism. This determines a unique winning message from the multiple concurrent TSC requests, avoiding instruction overwriting and frequent state transitions, thus ensuring the stability and reliability of power output. At the same time, the temporary control target obtained based on the winning message competes with other control requests from the engine itself for priority, and the final control target is determined based on the competition result. This ensures that external temporary requests no longer override the engine's own safety protection logic and speed regulation characteristics, eliminating potential safety hazards. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 This is the TSC multi-message contention strategy control flowchart; Figure 2 This is the actual control output flowchart of the engine; Figure 3 This is a graph showing the engine response results of the message competition between the speed control mode and the speed limit mode, specifically a graph showing the actual engine control state and the change of engine speed over time. Figure 4 This is a graph showing the engine response results of the message competition between torque control mode and torque limiting mode, specifically the changes in the engine's actual control state and net torque over time. Detailed Implementation

[0018] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0019] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0020] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0021] In the description of the embodiments of the present invention, it should be noted that if terms such as "upper," "lower," "horizontal," or "inner" indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings, or the orientation or positional relationship commonly used when the product of the invention is in use, they are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present invention. Furthermore, terms such as "first" and "second" are only used to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0022] Furthermore, the use of the term "horizontal" does not imply that the component must be absolutely horizontal, but rather that it can be slightly tilted. For example, "horizontal" simply means that its direction is more horizontal than "vertical," and does not mean that the structure must be completely horizontal, but can be slightly tilted.

[0023] In the description of the embodiments of the present invention, it should also be noted that, unless otherwise explicitly specified and limited, the terms "set," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention according to the specific circumstances.

[0024] The present invention will now be described in further detail with reference to the accompanying drawings: See Figures 1 to 4 This invention discloses a bus-based temporary control method for engine speed and torque. By requesting continuous speed and torque limits, an external device can temporarily control the engine's speed and torque via CAN bus messages. This embodiment designs the logic for single-message transmission and reception of speed and torque, as well as message delay interruption, according to the J1939 standard communication protocol. It also designs a multi-message contention logic algorithm for speed and torque and develops a competition mechanism between the engine's temporary control request and other engine requests, thus realizing the function of bus-based temporary control of engine speed and torque.

[0025] Example 1 This embodiment discloses a bus-based temporary control method for engine speed and torque, including the following steps: Step 1: The external device sends a TSC message to the CAN bus. The message carries information including: target device ID, message source device ID, control request mode, message priority, engine speed control conditions, engine speed request value, engine speed limit value, integer part of torque request value, integer part of torque limit value, fractional part of torque request value, fractional part of torque limit value, and control purpose.

[0026] Step 2: The ECU receives these TSC messages via the CAN bus and verifies them based on the J1939 standard communication protocol. If the verification fails, the message is discarded; if the verification succeeds, the message is parsed and the parsed message data is stored in the structure array Control_Request[ i ]middle, i It corresponds to a specific source device ID.

[0027] Step 3: Message verification.

[0028] The J1939 standard communication protocol specifies that a checksum is used to verify the correctness of signal data from the transmitting device to the receiving device. The checksum is the sum of the first 7 data bytes, 4 identifier bytes, and a message count value (0-7), transmitted cyclically. The calculation method is as follows:

[0029]

[0030] in, S k The sum of PDU bytes and message count; Byte i For data bytes; M j For identifier bytes; k For message counting, k ∈[0, 7]; Sum k This is the checksum. If the checksum equals 0x0F, checksum error diagnosis is disabled.

[0031] The external device controller sends a message count cyclically at a certain period (e.g., 10 ms), with the message count ranging from 0 to 7, and then restarting. If the final checksum calculated by the ECU from the received message matches the sent message, it indicates that the data was complete, accurate, and reliable during transmission.

[0032] Step 4: When multiple external controllers simultaneously send TSC messages to the CAN bus, the ECU uses a sequential comparison method to competitively sort these messages, that is, it compares each message pairwise to select the winning TSC message. The multi-message competition logic is as follows: Step 4.1: Verify if the message is correct. If correct: The ECU parses the message and proceeds to step 4.2; if incorrect: The ECU does not parse the message.

[0033] Step 4.2: Determine if SPN695=0 is true. If true: the message exits TSC contention; if false: proceed to step 4.3.

[0034] SPN695 indicates the TSC control mode. When the value of SPN695 is 0, the TSC overrun control fails; when the value of SPN695 is 1, the speed control mode is activated; when the value of SPN695 is 2, the torque control mode is activated; and when the value of SPN695 is 3, the speed limiting mode or torque limiting mode is activated.

[0035] Step 4.3: Determine if SPN3350=0b11111 is true. If true, the control objective is temporary control, proceed to step 4.4; otherwise: exit TSC contention.

[0036] Step 4.4: Is it a single message? If yes: Complete message verification and execute the message; if not: Proceed to step 4.5.

[0037] Step 4.5: Do the two messages originate from different source addresses? If yes: Proceed to Step 4.6; if not: Select the latest message.

[0038] Step 4.6: Are the messages the same priority? If yes: Proceed to Step 4.7; if not: Select the message with the higher priority.

[0039] Step 4.7: Are the two messages in the same TSC control mode? If yes: Proceed to Step 4.8; If not: Speed ​​control mode and torque control mode have higher priority than speed limit control mode or torque limit control mode; If one message is in speed control mode and the other is in torque control mode, select the older message, i.e., the message sent earlier.

[0040] Step 4.8: If the control modes of the two messages are the same, and both messages are in speed control mode or torque control mode, then the older message (sent earlier) has higher priority. If both messages are in speed limit control mode or torque limit control mode, then proceed to step 4.9.

[0041] Step 4.9: Determine if the torque limit values ​​of the two messages are the same. If they are the same, proceed to step 4.10; if they are different, the message with the smaller torque limit value has higher priority.

[0042] Step 4.10: Determine if the speed limit values ​​of the two messages are the same. If they are the same, proceed to step 4.11; if they are different, the message with the smaller speed limit value has higher priority.

[0043] Step 4.11: If the torque limit and speed limit values ​​of the two messages are the same, the older message (the message sent earlier) has a higher priority.

[0044] Step 5: The winning TSC message participates in the competition for engine control requests. Through engine limitation information, it determines the final engine control information and, by controlling the engine injection quantity and injection phase, enables the engine to reach the corresponding target speed and torque control values. See [link to relevant documentation]. Figure 2 .

[0045] Engine control requests include low idle speed, two-stage speed regulation, and full-range speed regulation; engine limitation information includes high idle speed, external characteristics, and engine protection.

[0046] The above describes the design and analysis process of the bus-based temporary control method for engine speed and torque disclosed in this embodiment.

[0047] Example 2 This embodiment discloses a bus-based temporary control method for engine speed and torque, specifically its practical application in a high-pressure common rail diesel engine electronic controller project, including the following steps: This is for an electronically controlled high-pressure common rail diesel engine with 8 cylinders, a displacement of 7.3 L, a maximum engine torque of 850 Nm, and a rated speed of 2500 r / min. The ECU uses a little-endian message design and the CAN message uses the extended frame format. The operating steps are as follows: Bus-based temporary engine speed control: Step 1: On the engine test bench, the accelerator pedal opening signal is 30%. At this time, the engine speed is maintained at about 1610 rpm, and the engine operation mode parameter value (Combustion_Control_Path_Owner) is 8, indicating that the engine is in a two-level speed regulation state.

[0048] Step 2: Using the CAN-Test software, send the following message to the CAN bus in a 10 ms cycle to simulate an external device with source address 07 sending a TSC message to the CAN bus: ID:0C000007, Data: 03 E0 2E FF FF FF FF 40; ID:0C000007, Data: 03 E0 2E FF FF FF FF 51; ID:0C000007, Data: 03 E0 2E FF FF FF FF 62; ID:0C000007, Data: 03 E0 2E FF FF FF FF 73; ID:0C000007, Data: 03 E0 2E FF FF FF FF 04; ID:0C000007, Data: 03 E0 2E FF FF FF FF 15; ID:0C000007, Data: 03 E0 2E FF FF FF FF 26; ID:0C000007, Data: 03 E0 2E FF FF FF FF 37.

[0049] Step 3: The ECU receives these TSC messages via the CAN bus and verifies the messages based on the J1939 standard communication protocol.

[0050] Taking the first message as an example, the message checksum calculation process is as follows: when k When =0, Sk =(03+E0+2E+FF+FF+FF+FF)+(0C+00+00+07)+0&0x0F=0x520; Sum k =((( S k >>6)&0x03)+( S k >>3)+ S k )&0x07=0x4.

[0051] The other six messages were also verified using the same algorithm. If the message verification was successful, it proves that the data transmission was error-free.

[0052] Step 4: After the message verification is successful, the message information is parsed.

[0053] The ECU parses the message, which carries the following information: target device ID=00 (engine), message source device ID=07, control request mode=03 (speed limit mode or torque limit mode), message priority=00 (highest priority), engine request speed control condition=00 (default value), engine speed request value or engine speed limit value=E0 2E (1500rpm), torque request value or torque limit value=FF (default value), and control purpose=0b11111 (temporary control mode), etc.

[0054] Step 5: The TSC message request and the engine two-level speed control request compete for control. The TSC has higher priority and executes the TSC message command. The engine enters the speed limit mode (Combustion_Control_Path_Owner=59). The engine speed responds to the TSC message command and the speed drops from 1610 rpm to 1500 rpm.

[0055] Step 6: After the TSC message control period, a second group of TSC messages is simultaneously sent cyclically at a 10 ms cycle to simulate an external device with source address 03 sending TSC messages to the CAN bus. ID: 0C000003, Data: 01 80 3E FF FF FF FF 60 ID: 0C000003, Data: 01 80 3E FF FF FF FF 71 ID: 0C000003, Data: 01 80 3E FF FF FF FF 02 ID: 0C000003, Data: 01 80 3E FF FF FF FF 13 ID: 0C000003, Data: 01 80 3E FF FF FF FF 24 ID: 0C000003, Data: 01 80 3E FF FF FF FF 36 ID: 0C000003, Data: 01 80 3E FF FF FF FF 47 Step 7: The ECU receives these TSC messages via the CAN bus and verifies the messages based on the J1939 standard communication protocol. If the message verification is correct, it proves that the data transmission is error-free.

[0056] Step 8: After the message verification is successful, parse the message information.

[0057] The message carries the following information: target device ID=00 (engine), message source device ID=03, control request mode=01 (speed control mode), message priority=00 (highest priority), engine request speed control condition=00 (default value), engine speed request value or engine speed limit value=80 3E (2000 rpm), torque request value or torque limit value=FF (default value), and control purpose=0b11111 (temporary control mode), etc.

[0058] Step 9: Currently in multi-message competition mode, the ECU uses the sequential comparison method to compete and sort these messages, that is, the messages are compared pairwise to select the final winning TSC message.

[0059] The competition process is as follows: (1) Two messages come from different source addresses. One message has a source address of 07 and the other has a source address of 03. This triggers condition (3).

[0060] (2) The two messages have the same priority, and the priority of both messages is 0, so condition (3) is entered.

[0061] (3) The two messages are different TSC control modes. The speed control mode should have a higher priority than the speed limit control mode or the torque limit control mode. Therefore, after sending the second group of messages (speed control mode), the engine responds to the message command first. After competing with other engine requests, the TSC request still has the upper hand. Therefore, the engine enters the speed control mode (Combustion_Control_Path_Owner=2), and the engine speed responds to the TSC message command, increasing from 1500 rpm to 2000 rpm.

[0062] Bus-based temporary engine torque control: Step 1: On the engine test bench, the accelerator pedal opening signal is 30%, the engine net torque is maintained at 430Nm, and the engine operating mode parameter value is 8, indicating that the engine is in a two-stage speed regulation state.

[0063] Step 2: Using the CAN-Test software, send the following message to the CAN bus in a 10 ms cycle to simulate an external device with source address 07 sending a TSC message to the CAN bus: ID:0C000007, Data: 03 FF FF 91 FF F7 FF 70; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 01; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 12; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 23; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 34; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 45; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 56; ID:0C000007, Data: 03 FF FF 91 FF F7 FF 67.

[0064] Step 3: The ECU receives these TSC messages via the CAN bus and verifies the messages based on the J1939 standard communication protocol.

[0065] Taking the first message as an example, the message checksum calculation process is as follows: when k When =0, S k =(03+FF+FF+91+FF+F7+FF)+(0C+00+00+07)+0&0x0F=0x59A; Sum k =((( S k >>6)&0x03)+( S k >>3)+ S k )&0x07=0x7.

[0066] The other six messages were also verified using the same algorithm. If the message verification was successful, it proves that the data transmission was error-free.

[0067] Step 4: After the message verification is successful, the message information is parsed.

[0068] The message carries the following information: Target device ID = 00 (engine), Message source device ID = 07, Control request mode = 03 (speed limit mode or torque limit mode), Message priority = 00 (highest priority), Engine request speed control condition = 00 (default value), Engine speed request value or engine speed limit value = FF FF (default value), Torque request value or torque limit value = 91 (20%), Decimal part of torque request value or torque limit value = 7 (0.875%), and Control purpose = 0b11111 (temporary control mode). The torque request value or torque limit value is 1400 × 20.875% = 292.25 Nm.

[0069] Step 5: The TSC message request and the engine two-level speed control request compete for power. The TSC has higher priority and executes the TSC message command. The engine enters the torque limiting mode (Combustion_Control_Path_Owner=20). The engine net torque responds to the TSC message command and decreases from 452 Nm to 292 Nm.

[0070] Step 6: After the TSC message control period has elapsed, a second group of TSC messages is simultaneously sent cyclically at a 10 ms cycle to simulate an external device with source address 03 sending TSC messages to the CAN bus. ID:0C000003, Data: 02 FF FF F8 FF F7 FF 60; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 71; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 02; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 13; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 24; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 35; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 46; ID:0C000003, Data: 02 FF FF F8 FF F7 FF 57.

[0071] Step 7: The ECU receives these TSC messages via the CAN bus and verifies the messages based on the J1939 standard communication protocol. If the message verification is correct, it proves that the data transmission is error-free.

[0072] Step 8: After the message verification is successful, parse the message information.

[0073] The message carries the following information: Target device ID = 00 (engine), Source device ID = 03, Control request mode = 02 (torque control mode), Message priority = 00 (highest priority), Engine request speed control condition = 00 (default value), Engine speed request value or engine speed limit value = FF FF (default value), Torque request value or torque limit value = F8 (27%), Decimal part of torque request value or torque limit value = 7 (0.875%), and Control purpose = 0b11111 (temporary control mode). The torque request value or torque limit value is 1400 × 27.875% = 390.25 Nm.

[0074] Step 9: Currently in multi-message competition mode, the ECU uses the sequential comparison method to compete and sort these messages, that is, the messages are compared pairwise to select the final winning TSC message.

[0075] The competition process is as follows: (1) Two messages come from different source addresses. One message has a source address of 07 and the other has a source address of 03. This triggers condition (3).

[0076] (2) The two messages have the same priority, and the priority of both messages is 0, so condition (3) is entered.

[0077] (3) The two messages are different TSC control modes. The torque control mode should have a higher priority than the speed limit control mode or torque limit control mode. Therefore, after sending the second message (torque control mode), the engine responds to the message command first. After competing with other engine requests, the TSC request still has the upper hand. Therefore, the engine enters the torque control mode (Combustion_Control_Path_Owner=1). The engine outputs net torque in response to the TSC message command, increasing from 292 Nm to 390 Nm.

[0078] Based on actual verification in a certain engine, this control method can achieve temporary control of engine speed and torque based on messages, which can meet the actual use requirements.

[0079] A schematic diagram of a terminal device according to an embodiment of the present invention. The terminal device of this embodiment includes: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps in the various method embodiments described above. Alternatively, when the processor executes the computer program, it implements the functions of each module / unit in the various device embodiments described above.

[0080] The computer program can be divided into one or more modules / units, which are stored in the memory and executed by the processor to complete the present invention.

[0081] The terminal device can be a desktop computer, laptop computer, cloud server, or other device with strong computing power. The terminal device may include, but is not limited to, a processor and memory.

[0082] The optimal choice for the processor is a multi-core high-speed central processing unit (CPU).

[0083] The memory can be used to store the computer program and / or module. The processor implements various functions of the terminal device by running or executing the computer program and / or module stored in the memory and calling the data stored in the memory.

[0084] If the modules / units integrated into the terminal device are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0085] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A bus-based temporary control method for engine speed and torque, characterized in that, Includes the following steps: S1: Obtain the temporary speed and torque control (TSC) message, verify the TSC message, if the verification passes, parse the TSC message and obtain the parsed message data, if the verification fails, discard the current TSC message; S2: Based on the parsed message data, according to the priority information and control mode information carried by the TSC message, and combined with the preset competition mechanism, multiple TSC messages are compared in pairs, and a unique winning TSC message is determined from the multiple TSC messages. S3: Obtain the temporary control target based on the winning TSC message, compete for priority with other control requests of the engine itself, and determine the engine's final control target based on the competition result.

2. The bus-based temporary control method for engine speed and torque according to claim 1, characterized in that, S2 includes the following steps: TSC messages indicating TSC override control failure and non-temporary control are filtered out in order of priority. Based on the filtered messages, a pairwise comparison is performed according to a preset competition mechanism to determine the unique winning TSC message from multiple TSC messages. The preset competition mechanism includes: Higher communication priority is higher than lower communication priority; Speed ​​control mode and torque control mode have higher priority than speed limit control mode and torque limit control mode. When one TSC message is in speed control mode and the other is in torque control mode, the message with the older timestamp has higher priority. When both TSC messages are in speed control mode or torque control mode, the message with the older timestamp has higher priority. When both TSC messages are in either speed limit control mode or torque limit control mode, the message with the smaller torque limit value or speed limit value has higher priority. When the torque limit value and speed limit value are the same, the message with the older timestamp has higher priority.

3. The bus-based temporary control method for engine speed and torque according to claim 2, characterized in that, S2 includes the following steps: S2.1: Determine whether the TSC control mode of the current TSC message is TSC overrun control failure. If yes, the current TSC message exits TSC contention. If not, execute S2.

2. S2.2: Determine whether the control purpose of the current TSC message is temporary control. If yes, execute S2.3; otherwise, the current TSC message exits the TSC contention. S2.3: Determine if it is a single TSC message. If yes, complete the message verification and execute the current message. If no, execute S2.

4. S2.4: Determine whether the two TSC packets come from different source addresses. If yes, proceed to S2.5; otherwise, select the latest packet. S2.5: Determine if the two TSC messages have the same priority. If yes, proceed to S2.6; otherwise, select the message with the higher priority. S2.6: Determine if two TSC messages have the same TSC control mode. If yes, execute S2.

7. If no, the speed control mode and torque control mode have higher priority than the speed limit control mode and torque limit control mode. If one TSC message is in speed control mode and the other TSC message is in torque control mode, select the message with the older timestamp. S2.7: Determine whether the control modes of the two TSC messages are the same. If the control modes of the two TSC messages are both speed control mode or torque control mode, select the message with the older timestamp. If the control modes of the two TSC messages are both speed limit control mode or torque limit control mode, execute S2.

8. S2.8: Determine whether the torque limit values ​​of the two TSC messages are the same. If yes, proceed to S2.9; otherwise, the message with the smaller torque limit value has higher priority. S2.9: Determine whether the speed limit values ​​of the two TSC messages are the same. If yes, execute S2.10; otherwise, the message with the smaller speed limit value has higher priority. S2.10: If the torque limit and speed limit values ​​of two TSC messages are the same, the message with the older timestamp has higher priority.

4. The bus-based temporary control method for engine speed and torque according to claim 1, characterized in that, In step S1, when obtaining the Temporary Speed ​​and Torque Control (TSC) message, the information carried by the TSC message includes the target device ID, the message source device ID, the control request mode, the message priority, the engine request speed control conditions, the engine speed request value, the engine speed limit value, the integer part of the torque request value, the integer part of the torque limit value, the fractional part of the torque request value, the fractional part of the torque limit value, and the control purpose.

5. The bus-based temporary control method for engine speed and torque according to claim 1, characterized in that, When verifying TSC messages, the verification is performed based on the J1939 standard communication protocol.

6. The bus-based temporary control method for engine speed and torque according to claim 1, characterized in that, S3 includes the following steps: The winning TSC message participates in the competition for engine control requests, and the final engine control information is determined by the engine limitation information. Based on the final control information, the fuel injection quantity and injection phase of the engine are controlled to enable the engine to reach the corresponding target speed and target torque control values.

7. A bus-based temporary control system for engine speed and torque, characterized in that, include: The TSC message verification module is used to acquire and verify the temporary speed and torque control TSC messages. If the verification passes, the TSC message is parsed and the parsed message data is obtained. If the verification fails, the current TSC message is discarded. The multi-message contention adjudication module is used to compare multiple TSC messages pairwise based on the parsed message data, priority information and control mode information carried by the TSC message, and a preset contention mechanism, and adjudicate the unique winning TSC message from the multiple TSC messages. The control target output module is used to obtain the temporary control target based on the winning TSC message, compete for priority with other control requests of the engine itself, and determine the engine's final control target based on the competition result.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-6.

9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-6.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-6.

Images