BACKGROUND

In existing vehicles, various components generate torque requests, and these torque requests are passed along to an engine ECU to cause an engine of the vehicle to produce the requested amount of torque. One problem with existing systems is that by using torque as the control input, the speed at which the engine operates may vary erratically. Even if torque requests are controlled such that the rate of change of the torque demand is limited, the engine speed may nevertheless change rapidly and unexpectedly due to the non-linear relationship between torque and engine speed. For example, changing loads on the engine may cause the engine speed to change, even without changing the amount of torque being produced or requested. These erratic changes in engine speed can cause rough operation for an operator of the vehicle, and can cause unwanted wear on the engine and other components. What is needed are devices and techniques that allow for changing torque requests to be processed without causing rapid and unexpected changes in engine speed.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

In some embodiments, a vehicle is provided. The vehicle comprises an engine, an engine electronic control unit (ECU), and at least one electronic control unit (ECU). The engine ECU is configured to control torque output by the engine in response to received torque request values. The at least one ECU is configured to determine a desired torque value, use the desired torque value, a current engine speed target value, and a current torque value to determine a subsequent engine speed target value, wherein the current torque value represents an amount of torque being generated by the engine; convert the subsequent engine speed target value to a torque request value; and provide the torque request value to the engine ECU.

-1- In some embodiments, a method of processing torque requests in a vehicle is provided. A desired torque value is determined. The desired torque value, a current engine speed target value, and a current torque value are used to determine a subsequent engine speed target value. The current torque value represents an amount of torque being generated by an engine of the vehicle. The subsequent engine speed target value is converted to a torque request value. The torque request value is provided to an engine electronic control unit (ECU) to control the amount of torque being generated by the engine.

, In some embodiments, a non-transitory computer-readable medium is provided. The computer- readable medium has computer-executable instructions stored thereon that, in response to execution by at least one electronic control unit of a vehicle, cause the at least one electronic control unit to perform actions comprising determining a desired torque value; using the desired torque value, a current engine speed target value, and a current torque value to determine a subsequent engine speed target value, wherein the current torque value represents an amount of torque being generated by an engine of the vehicle; converting the subsequent engine speed target value to a torque request value; and providing the torque request value to an engine electronic control unit (ECU) to control the amount of torque being generated by the engine. DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:

FIGURE 1 is a block diagram that illustrates selected components of an example embodiment of a vehicle according to various aspects of the present disclosure; and

FIGURES 2A-2B are a flowchart that illustrates a method of processing torque requests according to various aspects of the present disclosure. DETAILED DESCRIPTION

As stated above, controlling the rate of change of torque demand alone is not effective in controlling a rate of change of engine speed, at least because the relationship between torque and engine speed is non-linear. Accordingly, in some embodiments of

-2- the present disclosure, a change in a desired amount of torque is converted into a change in an engine speed target value. For example, if the desired amount of torque is greater than a current amount of torque being generated, then the engine speed target value may be smoothly increased, and if the desired amount of torque is less than a current amount of torque being generated, then the engine speed target value may be smoothly decreased. The new engine speed target value may then be converted back into a torque request, and the new torque request is provided to the engine ECU to be implemented. In this way, the changes in the engine speed can be limited in a linear fashion, thus avoiding the rapid and unexpected changes in engine speed that are caused by limiting a rate of change of a torque demand without considering how the changing torque demand would affect engine speed.

FIGURE 1 is a block diagram that illustrates selected components of an example embodiment of a vehicle according to various aspects of the present disclosure. In some embodiments, the vehicle 100 may be a Class 8 truck, though in other embodiments, any other type of vehicle may be used to include the illustrated components.

As illustrated, the vehicle 100 includes a speed controller electronic control unit (ECU) 102, a torque governor ECU 104, one or more torque request generators 106, an engine ECU 108, and an engine 1 10. As known to one of ordinary skill in the art, each of the ECUs 102, 104, 108 within the vehicle 100 is a computing device that includes a microcontroller, one or more types of memory, one or more inputs, and one or more outputs. Each of the ECUs may store instructions (or otherwise be operable to execute instructions provided to it) that cause the ECU to perform the actions described below. Though separate ECUs 102, 104, 108 are illustrated and described below, in some embodiments two or more of these ECUs 102, 104, 108 may be combined with each other into a single ECU. In some embodiments, the functionality described in one or more of the ECUs 102, 104, 108 may be split into multiple ECUs.

A torque request generator 106 is any component of a vehicle 100 that can generate a signal indicative of a desired amount of torque. One non-limiting example of a torque request generator 106 is a sensor that determines a position of an accelerator pedal and converts the position to an amount of torque desired. Another non-limiting example of a torque request generator 106 is a power-take-off (PTO) device controller that determines an amount of torque needed by the power-take-off system. Other examples of

-3- torque request generators 106 include, but are not limited to, an advanced braking system, an accident avoidance system, and a cruise control system.

In some embodiments, the speed controller ECU 102 receives torque requests from the one or more torque request generators 106. The speed controller ECU 102 determines an engine speed based on the torque requests, and provides the engine speed to the torque governor ECU 104. The torque governor ECU 104 then converts the engine speed to a torque request, and provides the torque request to the engine ECU 108. Further details of how the speed controller ECU 102 determines the engine speed and how the torque governor ECU 104 determines the torque request are provided below.

In some embodiments, the engine ECU 108 is an electronic component that functions to manage various aspects of the operation of the engine 1 10. For example, the engine's ignition timing, fuel consumption, and the like, may be monitored and controlled by the engine controller 108. The engine ECU 108 may modify these parameters in order to cause the engine 1 10 to produce a requested amount of torque. The engine ECU 108 may also communicate with one or more sensors of the engine 1 10 and may be configured to provide data from those sensors to other components. For example, the engine ECU 108 may be configured to determine a current engine speed, a current amount of torque being produced by the engine, and/or any other type of engine performance data known to one of ordinary skill in the art. In some embodiments, the engine 110 is an internal combustion engine, though this should not be seen as limiting. In some embodiments, the engine 1 10 may be another type of torque generating device capable of being controlled as described herein.

The various electronic components described above may communicate with each other through a vehicle-wide communications network (not illustrated). Those skilled in the art and others will recognize that the vehicle-wide communications network may be implemented using any number of different communication protocols such as, but not limited to, Society of Automotive Engineers' ("SAE") J1587, SAE J1922, SAE J1939, SAE J1708, and combinations thereof. Alternatively, the components described above may be provided by a single electronic component such as a general purpose controller or ECU residing on the vehicle 100, and so would not need to communicate via a network. It will be appreciated, however, that the present disclosure is not limited to any particular type or configuration of controller, or to any specific technique of communicating between components of the vehicle 100. One of ordinary skill in the art will understand that embodiments of a vehicle 100 have more components than those illustrated, including but not limited to transmission components, wheels, fluid pumps, and so on. Such well-known components of a vehicle 100 have not been illustrated or described to improve the clarity of the description of the novel features presented herein.

FIGURES 2A-2B are a flowchart that illustrates a method of processing torque requests according to various aspects of the present disclosure. From a start block, the method 200 proceeds through a continuation terminal ("terminal A") to block 202, where a torque request generator 106 of a vehicle 100 determines a desired torque value. This may occur in any manner appropriate to the particular torque request generator 106. For example, a power-take-off controller may determine, based on a control input to the power-take-off system, that a given torque amount is desired by the power-take-off system. As another example, an accelerator pedal sensor may detect that an accelerator pedal is depressed halfway, and may determine that half of the maximum torque (or some other suitable amount) is desired. As yet another example, a cruise control system may determine an optimal amount of torque to be used to maintain a given speed of travel.

Next, at block 204, the torque request generator 106 transmits the desired torque value to a speed controller electronic control unit (ECU) 102 of the vehicle 100. Though the below discussion assumes that a single desired torque value is transmitted to the speed controller ECU 102, in some embodiments, more than one torque request generator 106 may transmit desired torque values to the speed controller ECU 102. In such embodiments, the speed controller ECU 102 may use the highest desired torque value, may average the received desired torque values, may prioritize values from one torque request generator 106 over others, or may use any other suitable technique for determining a desired torque value to process based on the received desired torque values.

At block 206, the speed controller ECU 102 compares the desired torque value to a current torque value generated by an engine 1 10 of the vehicle 100. In some embodiments, the current torque value may be received from the engine ECU 108 by the speed controller ECU 102. In some embodiments, the speed controller ECU 102 may derive the current torque value based on values provided from other sensors. As one non- limiting example, the speed controller ECU 102 may use a current engine speed value to derive the current torque value using a torque map.

-5- The method 200 then proceeds to a decision block 208, where a determination is made regarding whether the desired torque value is greater than the current torque value. In some embodiments, the determination may include a hysteresis value, such that the desired torque value is compared to the current torque value plus an increase hysteresis threshold amount instead of to the current torque value alone. This allows small increases in the desired torque value to be ignored, thereby improving the stability of the control method and avoiding unnecessary cycling of the functionality. In some embodiments, the increase hysteresis threshold amount may be configurable by the operator of the vehicle, with larger values providing increased stability but poorer responsiveness, and with smaller values providing greater responsiveness but decreased stability. In some embodiments, the increase hysteresis threshold amount may be determined while configuring the vehicle for delivery, and may not otherwise be configurable by the operator.

If the desired torque value is greater than the current torque value (and, optionally, is greater than the current torque value by at least the increase hysteresis threshold amount), then the result of decision block 208 is YES, and the method 200 advances to block 210. At block 210, the speed controller ECU 102 adds an increase amount to a previous engine speed target value for use as a subsequent engine speed target value. In some embodiments, the increase amount may be a fixed amount of engine speed (for example, 50 RPM) to be added to the previous engine speed target value. In some embodiments, the increase amount may be specified as an increase rate or slope (for example, 1 RPM per second), which is then converted to a fixed amount of engine speed by determining how much time has passed since a previous time the engine speed target value was updated. As with the increase hysteresis threshold amount, the increase amount may be configurable by the operator of the vehicle 100 in order to allow the engine speed to rise faster or slower, or may be determined while configuring the vehicle for delivery. The method 200 then proceeds to a continuation terminal ("terminal B").

Returning to decision block 208, if the desired torque value is not greater than the current torque value (or, optionally, is not greater than the current torque value by at least the increase hysteresis threshold amount), then the result of decision block 208 is NO, and the method 200 proceeds to another decision block 212. At decision block 212, a determination is made regarding whether the desired torque value is less than the current torque value. As with the determination in decision block 208, in some embodiments, the determination in decision block 212 may include a hysteresis value, such that the desired torque value is compared to the current torque value minus a decrease hysteresis threshold amount instead of to the current torque value alone. This again will allow small changes in the desired torque value to be ignored, to improve stability of the control method. As with the increase hysteresis threshold amount, in some embodiments the decrease hysteresis threshold amount may be configurable by the operator of the vehicle, and in some embodiments the decrease hysteresis threshold amount may be determined while configuring the vehicle for delivery.

If the desired torque value is less than the current torque value (and, optionally, is less than the current torque value by at least the decrease hysteresis threshold amount), then the result of decision block 212 is YES, and the method 200 advances to block 214. At block 214, the speed controller ECU 102 subtracts a decrease amount from a previous engine speed target value for use as a subsequent engine speed target value. As with the increase amount, the decrease amount may be configurable by an operator of the vehicle, may be determined while configuring the vehicle for delivery, may be a fixed amount of engine speed, and/or may be specified as a decrease rate or slope. In some embodiments, the increase amount and the decrease amount may be the same, while in some embodiments, two separate amounts may be provided for the increase amount and the decrease amount. The method 200 then proceeds to a continuation terminal ("terminal B").

Returning to decision block 212, if the desired torque value is not less than the current torque value (or, optionally, is not less than the current torque value by at least the decrease hysteresis threshold amount), then the result of decision block 212 is NO, and the method 200 proceeds to a continuation terminal ("terminal C"). From terminal C (FIGURE 2B), the method 200 proceeds to block 216, where the speed controller ECU 102 uses a previous engine speed target value as a subsequent engine speed target value.

As will be understood by one of ordinary skill in the art and as described further below, the method 200 may be performed as a loop. In each of blocks 210, 214, 216, for the first time through the loop, the "previous engine speed target value" may be a default value, may be a current engine speed detected by an engine speed sensor, or may use any other appropriate initialization value. For subsequent executions of the loop, the determined subsequent engine speed target value may be stored for use as the previous engine speed target value in any computer-readable medium, such as a memory accessible by the speed controller ECU 102.

The method 200 then proceeds through terminal B to block 218, where the speed controller ECU 102 transmits the subsequent engine speed target value to a torque governor ECU 104 of the vehicle 100. At block 220, the torque governor ECU 104 converts the subsequent engine speed target value to a torque request value. The torque governor ECU 104 may use any suitable technique to convert the subsequent engine speed target value to a torque request value. In some embodiments, the torque governor ECU 104 may use a torque map to convert the subsequent engine speed target value to a torque request value. In some embodiments, the torque governor ECU 104 may implement a proportional-integral-derivative (PID) controller, wherein the PID controller uses the subsequent engine speed target value as the setpoint, uses the current engine speed as the process variable, and outputs the torque request as a control variable.

The method 200 then proceeds to block 222, where the torque governor ECU 104 transmits the torque request value to an engine ECU 108. Then, at block 224, the engine ECU 108 causes the engine 1 10 to produce torque in accordance with the torque request value. The engine ECU 108 may cause the engine to produce the requested amount of torque using any suitable technique known to one of ordinary skill in the art. For example, the engine ECU 108 may alter the fuel/air mixture, may alter variable valve timing, may alter ignition timing, or use other techniques to change the amount of torque generated by the engine 1 10. Causing the engine 1 10 to produce torque in accordance with the torque request value will cause the engine speed to approach the subsequent engine speed target value.

The method 200 then proceeds to a decision block 226, where a determination is made regarding whether the method 200 should loop and continue. Typically, the method 200 will continue as long as the vehicle 100 is operating and the speed controller functionality described herein is enabled. If the method 200 should continue, then the result of decision block 226 is YES, and the method 200 returns to terminal A. Otherwise, if the method 200 should stop, then the result of decision block 226 is NO, and the method 200 proceeds to an end block to terminate. In some embodiments, the loop within method 200 may execute rapidly in order to provide real-time control of the engine speed. For example, in some embodiments desired torque values may be received by the speed controller ECU 102 or generated by at least one torque request generator

-8- 106 each clock cycle, or once every 10ms. In some embodiments, the remainder of the processing may then take two clock cycles, after which time the method 200 may loop back to receive the next desired torque value. The particular techniques used in the method 200 allow the torque requests to be generated so quickly, and thereby allow very fine-grained control. In some embodiments, the method 200 may implement a delay in order to wait longer before looping back to terminal A.

In the discussion above, the method 200 is described as determining whether the desired torque value is "greater than" or "less than" other values. One of ordinary skill in the art will recognize that, in some embodiments, these comparisons could be "greater than or equal to" and/or "less than or equal to" instead of strictly "greater than" and/or "less than."

One of ordinary skill in the art will also recognize that though the discussion above is provided in the context of an engine of a vehicle, in some embodiments, the techniques described herein may be used to control an engine that is not mounted in a vehicle. As some non-limiting examples, an auxiliary power unit, a stationary mounted pump unit, or any other type of device that includes an engine may use techniques such as those described herein to control torque generated by its engine.

While illustrative embodiments have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the invention.

-9-