Title of Invention

TORQUE SPEED CONTROL AUTHORITY FOR AN ENGINE HAVING AN ALL-SPEED GOVERNOR

Abstract

A motor vehicle (20) has a diesel engine (22) and one or more sources (30, 36) providing data (CAN_TSC_OCM, CAN_TSC_OCM_SA11) relevant to operations of the vehicle that are external to the engine (22) but potentially influential on fueling of the engine (22). An engine control system (24) processes data according to an all-speed governing strategy (52) for controlling engine fueling (66) to develop all-speed governed fueling data (MFGOV) that sets engine fueling (66) when a data input to the engine control system (24) from the one or more sources discloses no need to influence engine fueling (66). When the data input from such one or more sources discloses a need to influence engine fueling (66), that data input causes engine fueling (66) to be set by a strategy (54) other than the all-speed governing strategy (52), a torque speed control strategy (54) in particular.

Full Text

TORQUE SPEED CONTROL AUTHORITY FOR AN ENGINE HAVING AN ALL-SPEED GOVERNOR Field of the Invention This invention relates generally to motor vehicle internal combustion engines that have all-speed governors. More specifically, the invention relates to engines, systems, and methods for control of fueling in such engines to avoid potential stalling when the action of a device, component, or system in a vehicle external to the engine, such as traction control, ABS, or the transmission, results in a torque request to an electronic engine control system that is different from the torque being requested by an all-speed governor strategy in the engine control system. Background of the Invention A known electronic engine control system comprises a processor-based engine controller that processes data from various sources to develop control data for controlling certain functions of the engine. One function that is can be effectively controlled by a processor-based system is engine torque. Control of torque is accomplished by control of engine fueling. A processor-based control system processes certain data useful in setting a data value for engine fueling that will cause the engine to develop requested torque, and then uses the result of that processing to control fuel injectors that inject fiiel into engine cylinders where the fiiel is combusted to develop the requested torque. A processor-based engine control system can endow a diesel engine with an electronic governor, one type of which is commonly known as an all-speed governor. In general, an all-speed governor functions in a manner such that for any given speed within a range of engine speeds, fuel will be injected into the cylinders in a proper amount to handle whatever torque is being requested at that speed within a range of allowable torque. As torque requests change while engine speed is held constant at a given speed, the engine control system adjusts fueling in a manner that strives to maintain that given speed. A motor vehicle that is powered by such an engine may have certain devices, components, and/or systems whose influence on engine torque via influencing engine fueling may be desirable under certain conditions of vehicle operation, but unnecessary and/or undesirable in the absence of those conditions. Examples are the transmission during certain gearshifts, the ABS system during certain braking events, and the traction control system during certain traction control events. When such events are allowed to influence engine torque, it is important that they do so in appropriate ways. Of particular importance is the avoidance of changing fueling to an extent that is detrimental to engine and vehicle operation. For example, fueling should not be restricted to such an extent that the engine may stall. Summary of the Invention Briefly, a general aspect of the present invention relates to an improvement for an all-speed-governed engine where authority is accorded to a torque speed control strategy to control engine fueling, and hence engine torque, on occasions when a device, component, or system that is external to the engine, indicates a need for torque speed control instead of all-speed governing. Accordingly a generic aspect of the invention relates to an internal combustion engine having a fueling system for fueling the engine; one or more sources providing data relevant to operations of the apparatus that are external to the engine but potentially influential on fueling of the engine; and an engine control system comprising a processor for processing data according to an all-speed governing strategy for controlling the fueling system to develop all-speed governed fueling data that sets engine fueling when a data input to the engine control system from the one or more sources discloses no need to influence engine fueling, but when the data input from such one or more sources discloses a need to influence engine fueling, that data input causes engine fueling to be set by a strategy other than the all-speed governing strategy. A specific example of the other strategy is a torque speed control Still other generic aspects relate to the control system just described and the method that is performed by the control in controlling the engine. Still other generic aspects relate to motor vehicles having such engines and control systems. The foregoing, along with further features and advantages of the invention, will be seen in the following disclosure of a presently preferred embodiment of the invention depicting the best mode contemplated at this time for carrying out the invention. This specification includes drawings, now briefly described as follows. Brief Description of the Drawings Figure 1 is a general schematic block diagram of a portion of an exemplary processor-based engine control system in accordance with principles of the present invention. Figure 1A illustrates a representative motor vehicle having the engine control system presented in Figure 1. Figure 2 is a flow diagram for selecting a particular message from one of multiple external sources in a motor vehicle in accordance with a current SAE (Society of Automotive Engineers) standard. Figures 3A and 3B comprise a detailed software strategy diagram that discloses the inventive principles. Description of the Preferred Embodiment Figure 1 comprises a strategy interface 50 to illustrate how the inventive strategy interfaces with other portions of the engine control strategy in a processor-based engine control system and with certain devices, components, and/or systems that are external to the engine and engine control system in a motor vehicle propelled by the vehicle. An example of a vehicle that can benefit from the invention is a truck powered by a diesel engine, such as a turbocharged diesel engine. Examples of such devices, components, and/or systems are those mentioned earlier. Figure 1A illustrates such a truck 20 comprising a diesel engine 22 having an engine control system 24. An accelerator pedal 26 operated by the driver acts on an accelerator position sensor (APS) 28 to provide a control input to control system 24. Truck 20 also comprises a transmission 30 having an input directly coupled to the engine output for propelling the vehicle through a drive train 32 ending at driven ones of the truck's wheels 34. Truck 20 further comprises an ABS system 36 that acts on wheels 34 under certain conditions. ABS system 36 and transmission 30 provide certain inputs to engine control system 24 in accordance with principles of the invention. A traction control system can also provide an input when present. The engine control system comprises an all-speed GOVERNOR strategy 52 that provides all-speed governing of the engine at times when those certain external devices, components and/or systems disclose no need to influence engine torque. However, when any one of such devices, components, and/or systems discloses such a need, the inventive strategy is enabled to act in ways that can override the all-speed governing strategy when conditions for overriding that strategy are present. The inventive strategy disclosed in Figure 2 is embodied principally in a TORQUE SPEED CONTROL portion 54 that forms an interface between certain portions on the left and certain portions on the right. The portions on the left are, in addition to all-speed GOVERNOR strategy 52: a CAN PARAMETER MESSAGES portion 56; a PROGRAMMABLE PARAMETERS portion 58; a TORQUE CALCULATOR portion 60; a CAMP SIGNAL PROCESSING portion 62. The portions on the right are: TORQUE CALCULATOR portion 60; a FUEL LEVHTER portion 64; a FUEL PULSEWBDTH COMMAND portion 66; and an ENGINE SPEED SETPOINT portion 68. CAN PARAMETER MESSAGES portion 56 represents certain data and/or data messages that are present on a data link or data bus through which various devices, components, and systems in the vehicle electronically communicate. Data or messages for only certain parameters are utilized by TORQUE SPEED CONTROL portion 54. The four parameters shown in Figure 1 are: CAN_TSC_OCM; CAN_TSC_OCM_SA11; CAN_MAXMOT_P7; CAN MAXMOT LMT. CANTSCOCM represents data from any external source other than a source SA11. CAN_TSC_OCM_SA11 represents data from source SA11. CANMAXM0TP7 represents data corresponding to a maximum allowable overspeed; C ANMAXMOTLMT represents data corresponding to a maximum allowable time limit for overspeed. PROGRAMMABLE PARAMETERS portion 58 represents parameters that are programmed into the engine control system for the particular engine model in the vehicle. The three parameters shown are: TRXC_EN[PP]; N_HIIDLE[PP]; and N_LIDLE[PP]. TRXC_EN[PP] represents data for enabling or unenabling traction control; N_HHDLE[PP] represents data for enabling or unenabling high idle; and N_LD3LE[PP] represents data defining low idle speed. TORQUE CALCULATOR portion 60 processes certain data to develop a data value for desired fuel for delivering requested torque MFRQST TRQ. CAMP SIGNAL PROCESSING 62 provides a data value for engine speed N. GOVERNOR portion 52 provides a data value for MFGOV representing governor-commanded mass fuel that is determined by FUEL LIMITER portion 64 processing certain data. FUEL LIMITER portion 64, FUEL PULSEWIDTH COMMAND portion 66? and a ENGINE SPEED SETPOINT portion 68 are present in the control system to set a limit on engine fueling, to set the amount of fuel injected (subject to limiting by portion 64), and to set engine speed, respectively. TORQUE CALCULATOR portion 60, FUEL LIMITER portion 64, FUEL PULSEWIDTH COMMAND portion 66, and ENGINE SPEED SETPOINT portion 68 are essentially conventional in certain engine control systems of international Truck & Engine Corporation. They are however adapted for proper interaction with TORQUE SPEED CONTROL portion 54, as will be apparent from the present disclosure. Source SA11, mentioned above, represents an ABS system in the vehicle. Other sources may also be present in the vehicle. The presence of such sources and data messages from them are made known to TORQUE SPEED CONTROL portion 54 via CAN PARAMETER MESSAGES portion 56. Because messages can originate at one or more of multiple sources, it becomes appropriate to assign priority to the messages. Priority assignment is performed by processing that is conducted in accordance with a flow diagram 70 shown in Figure 2. Flow diagram 70 embodies SAE Standard J1939/71 adapted for particular application to the present invention where a motor vehicle may have either a single or multiple external sources that can influence engine torque in certain situations where engine fueling should be different from that which would otherwise be commanded by the all-speed governing strategy. A detailed discussion of Figure 2 is believed unnecessary because flow diagram 70 is basically self-explanatory. As each message is given, it is queued and processed in sequence. Step 72 determines if there is more than one message in the queue. If not, the single message is validated and processed (step 74). If there is more than one message in the queue, step 76 determines if one has a higher priority than any other. If so, that one is validated and processed (step 78). If not, a step 80 determines if they seek the same control mode, either a speed-torque control mode or speed-torque limit mode. If they do not seek the same control mode, a speed-torque control message is favored over a speed-torque limit message, and so a step 82 selects the former type of message for processing by TORQUE SPEED CONTROL portion 54. If they do seek the same control mode, a step 84 distinguishes one type from the other. If the messages are speed-torque messages, a step 86 determines if they are from the same source. If they are, a step 88 selects the newest message for processing by TORQUE SPEED CONTROL portion 54. If they are not, a step 90 selects the oldest message for processing by TORQUE SPEED CONTROL portion 54. If step 84 determines that the messages are speed-torque limit messages, then a step 92 determines if they have the same torque limit. If not, a step 94 selects the one with the lower limit for processing. If they are, a step 96 determines if the messages have the same speed limit. If they do not, then a step 98 selects the one with the lower speed limit for processing by TORQUE SPEED CONTROL portion 54. If they do, then a step 100 selects the oldest one for processing by TORQUE SPEED CONTROL portion 54. A message typically comprises a packet of data. One data element in a packet signifies that the particular source is sending a message. Another data element distinguishes the particular type of message, and still another element designates a data value for Requested Torque. Torque Calculator portion 60 translates the externally requested torque into the desired fuel for delivering requested torque MF_RQST_TRQ. When TORQUE SPEED CONTROL portion 54 has control authority, the engine control system is operating in one of two modes, referred to in the present example as Mode 2 and Mode 3. Mode 2 is a mode of operation where TORQUE SPEED CONTROL portion 54 is calling for fueling that will provide a specific engine torque. Mode 3 is a mode of operation where TORQUE SPEED CONTROL portion 54 is calling for fueling that will limit engine torque to some maximum value. Hence, when the type of message issued by an external source is a torque control message, the control system is operating in Mode 2, and when the type of message issued by an external source is a torque limiting message, the control system is operating in Mode 3. Two other modes are Mode 0 and Mode 1. Mode 0 is an operating mode where the standard engine control, i.e. the accelerator pedal that is operated by the driver to provide an input to the engine control system through APS 24, has control authority. MFGOV represents the desired fueling when the accelerator pedal has control authority. Any other mode is an override mode where authority is given to a portion or portions of the strategy that can override the APS input. Mode 1 is a speed control mode that is independent of the strategy represented by Modes 2 and 3. Figures 3A and 3B show that TORQUE SPEED CONTROL portion 54 is organized into a Torque Speed Control Enable portion 102, a Torque Speed Control Enable Delay portion 104, a Momentary Overspeed Control portion 106, a Torque Request Handling portion 108, and a Torque Limit For Launch Control portion 110. Torque Speed Control Enable portion 102 comprises switch functions 112, 114, 116, 118, 122, 120; comparison functions 124, 126, 128, 130, 132, 134; OR logic functions 136, 138; AND logic functions 140, 142, 144; and a latch function 146. Torque Speed Control Enable Delay portion 104 comprises a comparison function 148 and a latch function 150. Momentary Overspeed Control Portion 106 comprises comparison functions 152, 154, 156, 158, and 160; AND logic functions 162, 164; an OR logic gate 166, and a timer function 167. Torque Request Handling portion 108 comprises a switch function 168, a limiting function 170, and a switch function 172. Torque Limit For Launch Control portion 110 comprises comparison functions 174, 176, and 178, a store function 179, an AND logic function 180, a timer function 182 and a latching function 184. AND logic function 144 in Torque Speed Control Enable portion 102 provides a data output TSCEN for enabling and unenabling torque speed control. When the data value for TSCEN is a logic "1", torque speed control is enabled, and when the data value is a logic "0", torque speed control is unenabled. The data value for TSCEN is determined by two data values: the data value TSCENLATCH provided by latch function 146; and the data value provided by OR logic function 136. OR logic function 136 provides a logic "1" output based on data messages from external sources that include source SA11 and any other external sources. When the vehicle is equipped with traction control, switch function 116 is set to ON, allowing one element of a data message from source SA11 (ABS system) to act as an input to OR logic function 136. That element of the data message can be either a logic "0" signifying that the source is not issuing a torque request or a logic "1" signifying that the source is issuing a torque request. Switch function 114 determines whether a torque request message is being issued by source SAIL The other input to OR logic function 136 comes from the other external sources. That input, which can be either a logic "0" signifying that the source is not issuing a torque request or a logic "1 "signifying that the source is issuing a torque request, is provided by switch function 112. Any logic "1" input to OR logic function 136 is effective to allow torque speed control to be enabled. But torque speed control will be enabled only if certain other conditions have caused latch function 146 to be set. Those conditions involve parameters N, TSCN STALL, MFRQSTTRQ, MFGOV, and TSC_MFGOV_HYS. Switch function 120 is enabled to set latch function 146 when switched ON. It will do so however only if data values for N, TSC_N_STALL, MF_RQST_TRQ, MFGOV, and TSC_MFGOV_HYS are such that OR logic function 138 provides a logic "1" to switch function 120. OR logic function 138 can provide a "1" logic output either while engine speed N is greater than a speed below which the engine will stall, or while MFRQST TRQ is greater than or equal to MFGOV, assuming that switch function 118 is ON. (How switch function 118 works will be explained later.) Switch function 120 is switched ON and OFF by AND logic function 140. For torque speed control to be enabled, switch function 120 must be OFF, a condition that occurs only when the output of AND logic function 140 is logic "0". AND logic function provides a logic "1" output only both when MFGOV is less than some defined value as determined by comparison function 134 and when engine speed N is less than low idle speed N_LIDLE[PP]. What this means in essence is that once the engine has started running with all-speed governing in control of engine fueling, latch function 146 becomes set, thereby making it possible to enable torque speed control But torque speed control will be enabled only if one of the external sources calls for it to be enabled. If multiple sources call for it to be enabled, the particular source that is allowed to set the data value for (MFRQST TRQ is determined by the priority determination processing of Figure 2. Once latch function 146 has been set, it can be reset only by another set of conditions. AND logic function 142 is used to reset latch function 146. Switch function 122 and comparison functions 128, 130 control AND logic function 142. Switch function 122 is under the control of comparison function 134. Once torque speed control has been enabled, comparison function 130 provides a logic "1" input to AND logic function 142. Should engine speed drop below low idle speed, comparison function 128 will also provide a logic "1" input. And if switch function 122 is ON, by virtue of comparison function 134 indicating that MFGOV is above some predetermined value, it too will provide a logic "P' input. This means that torque speed control will be unenabled should engine speed fall below low idle speed. Control of fueling will then be restored to Governor portion 52 for restoring fiieling to avoid engine stalling. Even if MFGOV is below the predetermined value for turning switch function 122 ON, the switch function will be turned ON if MFGOV exceeds MF_QST_TRQ. With stalling having been avoided by discontinuance of torque speed control, a restoration of conditions favorable for torque speed control will cause latch function 146 to be set, thereby making it possible for torque speed control to be once again enabled when an external source calls for such enablement With torque speed control enabled, Torque Speed Control portion 54 acquires control of engine fueling from Governor portion 52. In now controlling engine fueling, Torque Speed Control portion acts via Torque Request Handling portion 108. The enablement of torque speed control turns switch function 172 in Torque Request Handling portion 108 from OFF to ON. With switch function 168 in Torque Request Handling portion 108 OFF, the data value for TSCMFOCM becomes the minimum value TSCMFMIN set by limiting function 170 with the intent of reducing fueling to a level that is slightly that at which the engine would stall due to insufficient fueling. If MFRQSTTRQ does not exceed that minimum TSC_MF_MIN, then the data value for TSC_MF_OCM is that of TSC MF MIN. TSCMFOCM provides an input to FUEL LIMITER portion 64, which has been adapted to accord priority to TSCMFOCM in limiting fueling. TSC_MF_OCM also provides an input to FUEL PULSEWIDTH COMMAND portion 66, which has been adapted to utilize it in determining proper pulse widths for fuel injection pulses in the fuel limiting process. By making TSC_EN an input to both FUEL PULSEWIDTH COMMAND portion 66 and ENGINE SPEED SETPOINT portion 68, both portions are apprized of torque speed control enablement for now processing data according to any portions of their respective strategies that are peculiar to torque speed control. During torque speed control enablement, Momentary Overspeed Control portion 106 serves to honor torque requests from an external source that could increase engine speed above high idle speed. Overspeed is allowed only for short times and the overspeed is limited to a maximum speed. One example of how this feature may be used involves assisting transmission downshifts during motoring conditions. Momentary Overspeed Control portion 106 accomplishes this by control of switch function 168. Instead of TSC_MF_OCM being forced to TSC_MF_MIN, the operation of switch function 166 from OFF to ON allows MF_RQST_TRQ to set the value for TSC MF OCM. If engine speed is less than high idle speed as determined by comparison function 160, OR logic function 166 allows Momentary Overspeed Control portion 106 to turn switch function 168 ON. Once engine speed exceeds high idle speed, OR logic function will turn switch function 168 OFF unless AND logic function 164 acts to keep the switch function ON. AND logic function 164 will keep switch function 168 ON for a limited time, as set by the collective effect of functions 167, 158, provided that engine speed continues to exceed high idle speed, as determined by comparison function 154, and that one of the external sources is continuing to call for torque speed control authority, as determined by comparison function 156. Engine speed must also not exceed a maximum limit, as determined by comparison function 152. Torque Speed Control Enable Delay portion 104 serves to delay enablement of torque speed control until the first call for enablement of torque speed control after the all-speed governor has acquired control authority. Operation of the ignition switch to start the engine causes latch function 150 to be set. The setting of latch function 150 turns on switch function 118 in Torque Speed Control Enable portion 102 so that comparison function 126 compares whatever the data value is for MF_RQST_TRQ with the data value for MFGOV. Once the data value for TSCEN changes from "0" to "1", comparison function 148 resets latch function 150 to cause the data value for TSC_EN_DELAY to switch back to "0" thereby turning switch function 118 off. With switch function 118 now off, the data value for a parameter TSC_MFGOV_HYS is added to the data value for MFGOV so that comparison function 126 now compares the data value for MF_RQST_TRQ with the data value for the sum of the data values for MFGOV and TSC__MFGOV__HYS. Comparison function 126 will continue to compare in this way until the ignition switch is turned off to shut down the engine and once again turned on when the engine is once again started. The inclusion of TSC_MFGOV_HYS imparts a certain hysteresis that assures that desired fuel calculated from the external torque request is great enough to prevent the logic from cycling between accelerator and the external controls, which could cause fluctuations in engine torque. Torque Limit For Launch Control portion 110 acts only when the mode changes from Mode 2 to Mode 0, representing a change from torque control to driver control. Store 179, comparators 174, 176 and AND logic function 180 are arranged to detect that change, which is represented by the data value for CAN_TSC_OCM changing from "2" to "0", and when they do, AND logic function 180 sets latch function 184. As a consequence, the output TSC_LC_EN of latch function 184 changes from a "0" to a "1". A transition from Mode 2 to Mode 0 occurs at vehicle launch, and may be triggered by the action of certain automatic transmissions that invoked Mode 2 operation at incipient launch. At some point in the launch, the transmission accedes control back to the driver, and that is when the mode reverts to Mode 0. The setting of latch function 184 starts timer function 182 and also signals FUEL PULSEWIDTH COMMAND portion 66. The latter now acts to apply a rate-of-change limiting function to fueling that is being requested by the driver by virtue of Mode 0 operation. The purpose in doing this is to assure that at the point in vehicle launch where the transmission returns control to the driver, the driver is not requesting fueling that would impair the quality of the launch. Once timer function 182 has timed out, comparison function 178 resets latch function 184, and it in turn resets timer function 182 and also returns TSC_LC_EN to "0". FUEL PULSEWIDTH COMMAND portion 66 is then allowed to discontinue applying rate-of-change limiting to engine fueling. Principles of the invention can apply to vehicle platforms that have transmissions directly driven by diesel engines and to hybrid platforms where a DC motor may propel the vehicle and the engine will act as a battery charger to charge batteries that operate the DC motor. In such a hybrid vehicle, torque speed control can still be used to prevent the hybrid controller from stalling the engine. While a presently preferred embodiment of the invention has been illustrated and described, it should be appreciated that principles of the invention apply to all embodiments falling within the scope of the following claims. WHAT IS CLAIMED IS: 1. Apparatus comprising: an internal combustion engine (22) having a fueling engine (22); one or more sources (30,36,TRXC_EN[P (CAN_TSC_OCM;CAN_TSC_OCM-SA11) relevant to operations of the apparatus that are external to the engine (22) but potentially influential on fueling of the engine (22); and an engine control system (24) comprising a processor for processing data according to an all-speed governing strategy (52) for controlling the fueling system to develop all-speed governed fueling data that sets engine fueling (66) when a data input to the engine control system (24) from the one or more sources (30,36,TRXC_EN[PP]) discloses no need to influence engine fueling (66), but when the data input from such one or more sources (30,36,TRXC_EN[PP]) discloses a need to influence engine fueling (66), that data input causes engine fueling (66) to be set by a strategy (54) other than the all-speed governing strategy (52). 2. Apparatus as set forth in Claim 1 wherein the apparatus comprises a wheeled land vehicle 20 that is propelled by the engine (22), and the one or more sources (30,36,TRXC_EN[PP]) comprise one or more systems that act on wheels (34) of the land vehicle 20. 3. Apparatus as set forth in Claim 1 wherein the apparatus comprises a motor vehicle 20, the vehicle 20 comprising a transmission (30) that is directly coupled to the engine (22) for propelling the vehicle 20 through a drivetrain (32) ending at driven ones of wheels (34) of the vehicle 20, and the one or more sources (30,36,TRXC_EN[PP]) comprise one or more systems that act on at least some of wheels (34). 4. Apparatus as set forth in Claim 1, Claim 2 or Claim 3 wherein the one or more sources (30,36,TRXC_EN[PP]) comprise one or more of: an ABS system (36); a traction control system TRXC_EN[PP]; and the transmission (30). 5. Apparatus as set forth in Claim 4 wherein the control system (24) comprises functions for placing the other strategy (54) in an enabled state when the data values for one set of inputs indicate the existence of conditions appropriate for the other strategy (54) to influence engine fueling (66) and for placing the other strategy (54) in an unenabled state when the data values for another set of inputs indicate the existence of conditions inappropriate for the other strategy (54) to influence engine fueling (66). 6. Apparatus as set forth in Claim 5 wherein the one set of inputs includes engine speed (N). 7. Apparatus as set forth in Claim 6 wherein the one set of inputs includes engine torque requested (MF_RQST_TRQ) from one of the one or more sources (30?36,TRXC_EN[PP]) and torque requested (MF_RQST_TRQ) by the all-speed governing strategy (52). 8. Apparatus as set forth in Claim 7 wherein the one set of inputs includes engine speed (N). 9. Apparatus as set forth in Claim 5 wherein the other set of inputs includes engine speed (N) and engine low idle speed (N_LIDLE[PP]), engine torque requested (MFRQST TRQ) from one of the one or more sources (30,36,TRXC_EN[PP]), and torque requested (MF_RQST_TRQ) by the all-speed-governing strategy (52). 10. Apparatus as set forth in Claim 5 wherein the other strategy (54) includes a momentary overspeed control portion (106) that, when the other strategy (54) is enabled, is effective to allow engine speed (N) to exceed high idle speed (N_HIIDLE[PP]) for a limited time. 11. Apparatus as set forth in Claim 10 wherein inputs to the momentary overspeed control portion (106) include engine speed (N) , engine high idle speed (N_HIIDLE[PP] ) , a maximum speed limit (CAN_MAXMOT_P7) , and a maximum time limit (CAN MAXMOT LMT). 12. Apparatus as set forth in wherein with the strategy (54) other than the all-speed governing strategy (52) influencing engine fueling (66), that other strategy (54) functions to detect incipient engine stalling (TSCNSTALL) and change engine fueling (66) to avoid actual stalling. 13. Apparatus as set forth in Claim 1, Claim 2 or Claim 3 wherein the strategy 54 other than the all-speed governing strategy (52) influencing engine fueling (66) comprises a torque speed control strategy (54) influencing engine fueling (66) to influence engine torque. 14. Apparatus as set forth in Claim 13 wherein the torque speed control strategy (54) influencing engine fueling (66) to influence engine torque comprises influencing engine fueling (66) to create desired engine torque. 15. Apparatus as set forth in Claim 13 wherein the torque speed control strategy (54) influencing engine fueling (66) to influence engine torque comprises influencing engine fueling (66) to impose a limit (110) on engine torque. 16. A method for control of an internal combustion engine (22) having a fueling system that in one mode of operation is under control of an accelerator position sensor (28) free of influence from certain other external sources (30,36,TRXC_EN[PP]) and in another mode of operation is influenced by one or more of those external sources (30,36,TRXC_EN[PP]), the method comprising: when the engine (22) is operating in the one mode, processing data according to an all-speed governing strategy (52) to set desired engine fueling (66); and when the engine (22) is operating in another mode, processing data according a strategy (54) other than the all-speed governing strategy (52) to set desired engine fueling (66). 17. A method as set forth in Claim 16 wherein the strategy (54) other than the all-speed governing strategy (52) comprises a torque speed control strategy (54) to set engine fueling (66) for setting engine torque. 18. A method as set forth in Claim 17 wherein the torque speed control strategy (54) comprises setting engine fueling (66) to create desired engine torque. 19. A method as set forth in Claim 17 wherein the torque speed control strategy (54) comprises setting engine fueling (66) to impose a limit (110) on engine torque. Dated this 17 day of May 2006

Documents:

1689-CHENP-2006 CORRESPONDENCE OTHERS 14-06-2011.pdf

1689-CHENP-2006 AMENDED CLAIMS 21-09-2011.pdf

1689-CHENP-2006 EXAMINATION REPORT REPLY RECEIVED 21-09-2011.pdf

1689-CHENP-2006 FORM-3 21-09-2011.pdf

1689-CHENP-2006 OTHER PATENT DOCUMENT 21-09-2011.pdf

1689-CHENP-2006 POWER OF ATTORNEY 21-09-2011.pdf

1689-CHENP-2006 CORRESPONDENCE PO.pdf

1689-CHENP-2006 FORM-18.pdf

1689-chenp-2006-abstract.pdf

1689-chenp-2006-assignement.pdf

1689-chenp-2006-claims.pdf

1689-chenp-2006-correspondnece-others.pdf

1689-chenp-2006-description(complete).pdf

1689-chenp-2006-drawings.pdf

1689-chenp-2006-form 1.pdf

1689-chenp-2006-form 3.pdf

1689-chenp-2006-form 5.pdf

1689-chenp-2006-pct.pdf