Method for Compensating for Cable Length in a Vehicle Electronic Speed Control System

The present invention relates to speed or "cruise" control systems for automobiles. More specifically, it relates to a method of compensating for cable length between the speed control vacuum servo and the throttle linkage in a vehicle electronic speed control system.

In cruise control systems like that disclosed in U.S. patent application Ser. No. 023,165, filed Mar. 6, 1987, entitled "Method of Determining and Using a Filtered Speed Error in an Integrated Acceleration Based Electronic Speed Control System for Vehicles", now U.S. Pat. No. 4,860,210, issued on Aug. 22, 1989, assigned to the assignee of the present application, the specification of which is herein incorporated by reference, cables with different lengths between the speed control vacuum actuator and the throttle linkage are utilized in different model vehicles. Thus, there is a need to compensate for the varying cable lengths in electronic speed control systems.

Speed control systems are illustrated in the following U.S. patents. They are: U.S. Pat. No. 3,722,614, issued on Mar. 27, 1973 to Sakakibara et al., entitled "Method And Apparatus For Causing Constant Traveling Speed Of Automotive Vehicles"; U.S. Pat. No. 4,066,874, issued on Jan. 3, 1978 to Mark L. Shaw, entitled "Digital Speed Control System"; U.S. Pat. No. 4,066,876, issued on Jan. 3, 1978 to Mark L. Shaw et al., entitled "Digital Speed Control System"; U.S. Pat. No. 4,250,854, issued on Feb. 17, 1981 to Matsui et al., entitled "Speed Control System For Automotive Vehicles"; U.S. Pat. No. 4,335,799, issued on June 22, 1982 to Neal G. Shields, entitled "Speed Governor With Below Dashboard Servomotor"; U.S. Pat. No. 4,340,824, issued on July 20, 1982 to Mark L. Shaw, entitled "Auxiliary Steering Wheel Command System"; U.S. Pat. No. 4,345,663, issued on Aug. 24, 1982 to Neal G. Shields, entitled "Speed Governor With Dual Safety System"; U.S. Pat. No. 4,352,403, issued on Oct. 5, 1982 to Charles F. Burney, entitled "Vehicle Speed Control System"; U.S. Pat. No. 4,394,739, issued on July 19, 1983 to Suzuki et al, entitled "Automatic Speed Control System For An Automotive Vehicle"; U.S. Pat. No. 4,431,077, issued on Feb. 14, 1984 to Charles F. Burney, entitled "Vehicle Speed Control System"; U.S. Pat. No. 4,451,888, issued on May 29, 1984 to Kuno et al, entitled "Speed Control Method And Apparatus For Automotive Vehicles"; U.S. Pat. No. 4,451,890, issued on May 29, 1984 to Suzuki et al, entitled "Automatic Speed Control System For An Automotive Vehicle"; U.S. Pat. No. 4,463,822, issued on Aug. 7, 1984 to Tanigawa et al., entitled "Cruise Control System For Automotive Vehicle"; U.S. Pat. No. 4,467,428, issued on Aug. 21, 1984 to Caldwell, entitled "Automatic Speed Control Systems"; U.S. Pat. No. 4,470,478, issued on Sept. 11, 1984 to Hayashi et al., entitled "Vehicle Speed Control Apparatus With Set Increase"; U.S. Pat. No. 4,472,777, issued on Sept. 18, 1984 to Youngblood, entitled "Engine Control Apparatus For Vehicle Speed"; U.S. Pat. No. 4,479,184, issued on Oct. 23, 1984 to Nakano, entitled "Device For Maintaining a Constant Vehicle Speed"; U.S. Pat. No. 4,478,184, issued on Oct. 23, 1984 to Shinoda et al., entitled "Speed Control System And Method For Automotive Vehicles"; U.S. Pat. No. 4,484,279, issued on Nov. 20, 1984 to Muto, entitled "Vehicle Speed Control Method"; U.S. Pat. No. 4,488,527, issued on Dec. 18, 1984 to Pfalzgraf et al., entitled "Device For Controlling The Speed Of Travel Of An Automotive Vehicle"; U.S. Pat. No. 4,501,284, issued on Feb. 26, 1985 to Kuno et al., entitled "Speed Control Method And System For Automotive Vehicles"; U.S. Pat. No. 4,516,652, issued on May 14, 1985 to Tanigawa et al., entitled "Apparatus For Controlling The Speed Of An Automobile"; U.S. Pat. No. 4,522,280, issued on June 11, 1985 to Blaney, entitled "Automatic Disengagement Device For Automotive Cruise Control System"; U.S. Pat. No. 4,549,266, issued on Oct. 22, 1985 to Schneider et al., entitled "Vehicle Speed Control": U.S. Pat. No. 4,597,465, issued on July 1, 1986 to Burney, entitled "Cruise Control System And Method With Overspeed Sensor"; U.S. Pat. No. 4,606,425, issued on Aug. 19, 1986 to Hayashi et al., entitled "Vehicle Speed Control Apparatus"; and U.S. Pat. No. 4,608,954, issued on Sept. 2, 1986 to Gray, entitled "Input Circuit For An Electronic Vehicle Speed Control Unit". Of interest is SAE Paper No. 830662 by Peter G. Blaney, entitled "Improvement To Cruise Controls Utilizing Microprocessor Technology"; and a paper entitled "New LSI Circuits That Optimize Cruise Control Systems" by Mark L. Shaw.

In cruise control systems, after a set is decoded from the switch read section of the software, the speed control cable timer (hereinafter SCUCAB) and the error maximum (hereinafter ERRMAX) registers are cleared and the set test (hereinafter SETTST) flag is set. After the SETTST flag is set, a new set-up pulse is calculated and an adaptable pulse width adjust (hereinafter PWADJ) term is added to the set-up pulse. The PWADJ term may also be added to the resume set-up pulse during a resume mode.

If a 121 millisecond time interval has not passed the adapted cable speed control algorithm will move to the cruise actuation section of the algorithm. The brake flag is checked to determine if the speed control has been activated. If so, the vac vent time (hereinafter VVTIMR) is checked to see if the VVTIMR has decremented to zero. If this is the case, the SETTST flag is checked. If the SETTST flag is set, indicating that a pulse has been fired, the EVENT flag is set.

After the EVENT flag is set, the algorithm will continue on to update the PWADJ term which, in turn, is utilized to adjust the actual car speed to be equivalent with the selected desired set speed. The algorithm is bypassed if it is sensed that a brake flag has been set, which implies that either the speed control is cut out or the deceleration mode is ongoing. If the program determines that the brake set flag is cleared, the EVENT flag is checked. If the EVENT flag is clear, the algorithm will be bypassed since this implies that either a set was not executed or the "set" set-up pulse has not yet timed out. If the EVENT flag is set, either the "error sample delay time" mode or the "error sampling time" mode is occurring. The correct mode is determined by the SETTST flag. If the SETTST flag is set, the SCUCAB is used as a delay timer. When the SCUCAB increments to speed control counter delay, the SETTST flag is cleared and the SCUCAB is reset in order to be used as a sampling timer.

During the error sampling mode, the speed error is calculated as the error (ERRTEMP) is equal to the desired set speed (SETSPD) plus the speed control adapted control point (SCSCAB), the quantity, minus the actual car speed (CARSPD). The absolute value of the error (ERRTEMP) is compared to the absolute value of ERRMAX (the largest error for the current set set-up pulse). If the present error, ERRTEMP, is larger than ERRMAX, it is saved as a new ERRMAX.

Error sampling is completed when the error sampling timer increments to the speed control counter error. At this time, the absolute value of ERRMAX is compared to the ERRMAX dead band (hereinafter SCSEDB). If the ERRMAX is less than the SCSEDB, then ERRTOT and PWADJ will not be updated since the maximum error is within a desired tolerance for the current set. In this case, the EVENT flag is cleared and the adaptive cable algorithm ends with a jump to the acceleration calculation section of the routine.

However, if ERRMAX is greater than or equal to SCSEDB, adaptive updating is necessary. At this time, ERRMAX is added to ERRTOT (the accumulation register for all of the error maximums) and ERRTOT is compared to its positive and negative limits. If ERRTOT is within the predetermined limits, PWADJ will not be updated and the EVENT flag will be cleared and the algorithm will again jump to the acceleration calculation section.

However, if ERRTOT exceeds the positive limit, speed control ERRTOT high trigger point (hereinafter SCSTGH), PWADJ is incremented by the speed control time increment (hereinafter SCUINC). If ERRTOT exceeds the negative limit, speed control low trigger point (hereinafter SCSTGL), PWADJ is decremented by the speed control time decrement (hereinafter SCUDEC). At this point, both the EVENT flag and ERRTOT are cleared and the algorithm ends by jumping to the acceleration calculation section of the routine.

Other objects, features and advantages of the present invention will become more fully apparent from the following Detailed Description of the Preferred Embodiment, the appended claims and in the accompanying drawings in which:

FIG. 1 is a block diagram of the electronic speed control system;

FIG. 2 is a chart depicting the operation of the vacuum solenoid and the vent solenoid and the corresponding throttle action which is a function of the current flow through the solenoids;

FIG. 3 is a schematic diagram of the speed sensor signal conditioning circuit;

FIG. 4 is a schematic diagram of the throttle position indicator signal conditioning circuit;

FIG. 5 is a schematic diagram of the network switch filter;

FIG. 6 is a schematic diagram for the peripheral interface/signal conditioner and solenoid drivers;

FIG. 7 is a flowchart of an overview of the method for electronic speed control;

FIG. 8 is a continuation of the overview flowchart in FIG. 7 of the method for electronic speed control;

FIG. 9 is a detailed flow chart of the method for electronic speed control;

FIG. 10 is a continuation of the detailed flowchart of the method for electronic speed control begun in FIG. 9;

FIG. 10(a) is a detailed flowchart of the method in block G;

FIG. 11 is another continuation of the detailed flowchart of the method for electronic speed control begun in FIG. 9;

FIG. 11(a) is another continuation of the detailed flowchart of the adaptive cable routine for electronic speed control begun in FIG. 9;

FIG. 11(b) is a diagram of the adaptive cable timing;

FIG. 12 is still another continuation of the detailed flowchart of the method for electronic speed control begun in FIG. 9;

FIG. 13 is yet another continuation of the detailed flowchart of the method for electronic speed control begun in FIG. 9;

FIG. 14 is an interpolation point-slope curve for the set pulse width variable SETPW;

FIG. 15 is an interpolation point-slope curve for the resume pulse width variable RESTBL;

FIG. 16 is an interpolation point-slope curve for the vacuum solenoid acceleration rate variable VACACC;

FIG. 17 is an interpolation point-slope curve for the vacuum solenoid regular desired acceleration rate variable VACREG;

FIG. 18 is an interpolation point-slope curve for the vent solenoid regular desired acceleration rate variable VENTRG;

FIG. 19 is an interpolation point-slope curve for the throttle gain factor THGAIN;

FIG. 20 is an interpolation point-slope curve for the speed gain factor SPGAIN;

FIG. 21 is a flowchart illustrating the method for checking the condition of the clutch for an electronic speed control; and

FIG. 22 is a flowchart illustrating the method for checking the resume switch and disabling it, if necessary.

The basics of automotive electronic cruise or speed control is explained in Chapter 8 of Understanding Automotive Electronics by Ribbens and Mansour, published by Texas Instruments and distributed by the Society of Automotive Engineers (SAE). Chapter 8 is entitled "Vehicle Motion Control", pages 209-230, and is hereby expressly incorporated by reference.

Referring to FIG. 1, a block diagram of the electronic speed control system is shown. Central to the system is the engine control logic module 50 which controls many things in addition to the speed control, such as engine timing and some of the fuel tasks. The heart of the engine control logic module 50 is the microcontroller Z20 which works in tandem with memory means such as a programmable read-only memory and/or random access memory (MEMORY) Z51. The microcontroller Z20 accepts signals from signal conditions 58, 60, 62, 64, 66 and 68. In addition, the microcontroller Z20 sends signals and receives signals from the vacuum solenoid driver/interface 54 and the vent solenoid driver/interface 56.

The function of the vacuum solenoid driver/interface 54 and vent solenoid driver/interface 56 is to control the operation of the vacuum solenoid 34 and the vent solenoid 36. The operation of these solenoids, as well as purge vent solenoid 38, will control the vacuum actuator 44 which in turn controls the throttle position. Purge vent solenoid 38 is connected between ground and V.sub.CC via series switches for power on/off 74A and brakes 80A (also shown in block 74 and block 80 for ease of description). The solenoid 38 purges the vacuum actuator 44 if brake switch 80A or power on/off switch 74A is opened after the electronic speed control system shown in FIG. 1 has been "on". Connected to the throttle (not shown) is a throttle position indicator 46 which also sends information back to microcontroller Z20 via A/D converter Z85. This is shown in block diagram form in FIG. 1, and is completely described in commonly assigned U.S. Pat. No. 4,637,361, entitled "Non-Adjustable Throttle Position Indicator" to Killen et al., of Jan. 20, 1987, and is hereby expressly incorporated by reference; this non-adjustable throttle position indicator is one of the methods which can be employed to record the throttle position and indicate the throttle position in an electronically controlled engine system.

Also hereby expressly incorporated by reference are the following documents: U.S. Pat. No. 4,335,689 to Abe et al., dated June 22, 1982, entitled "Electronic Type Air/Fuel Ratio Control System"; U.S. Pat. No. 4,508,078 to Takeuchi et al., dated Apr. 2, 1985, entitled "Electrically Operated Engine Throttle Valve Actuating Device"; and U.S. Pat. No. 4,492,211 to Shimomura et al., dated Jan. 8, 1985, entitled "Air-To-Fuel Ratio Control System For Internal Combustion Engine".

Referring now to FIG. 2, a chart depicting the operation of the vacuum solenoid 34 and the vent solenoid 36 and the corresponding throttle action which is a function of the current flow through the solenoids. More specifically, in the chart the current flow through the solenoid will be indicated by a logical "one". Likewise, the lack of a current flow through the solenoids will be indicated by a logical "zero".

The throttle action is indicated in FIG. 2 by the following labels on the rows: open, close and hold. It can be seen that the throttle action is open if both vacuum and vent solenoids 34 and 36, respectively, have current flow through them. Similarly, the throttle action is closed if the current flow through the vacuum and vent solenoids 34 and 36, respectively, is "zero". Likewise, the throttle action is in a hold position if the vacuum solenoid 34 has no current flow through it and the vent solenoid 36 has current flow.

Returning now to FIG. 1, the signal conditioning blocks 58, 60, 62, 64, 66 and 68, all take their input signals from various sensors/actuators, etc., throughout the vehicle and, more specifically, get their inputs from some specific control mechanisms, some of which are dedicated to the electronic speed control operation.

For example, referring to the signal conditioning block 58, the function of this block is to accept a signal from the set switch 70 which is located on a stalk switch assembly which has other functions to control the wiper mechanisms Hi/Lo beam headlamps and the turn signals of the vehicle. A more descriptive treatment of such a stalk switch assembly can be found in a commonly assigned U.S. Pat. No. 4,219,706, dated Aug. 26, 1980, to David A. Koch, Michael G. Moore and Arthur L. Pawlus, entitled "Steering Column Mounted Control Stalk With Multiple Actuators For Rotatable and Slide Type Switches" which is hereby expressly incorporated by reference.

Referring now to the signal conditioning block 60, the function of this block is to receive a signal from the resume switch 72 which is described in the '706 patent.

Referring now to the signal conditioning block 62, its function is to receive a signal from the power on/off switch 74 which is also described in the '706 patent.

Referring now to the signal conditioning block 64, its function is to receive a signal from the park/neutral or clutch switch 76. This function is also described in the '706 patent.

The function of the signal conditioning block 66 is to receive a signal from the speed sensor 78 as shown in FIG. 1.

The function of the signal conditioning block 68 is to receive a signal from the brake switch 80, the function of which is also explained in the '706 patent which has been expressly incorporated by reference.

Referring again to FIG. 1, the circuit is powered by a 12-volt supply from the battery of the vehicle. The power on/off switch 74 which is shown as a block, is also schematically shown as switch 74A. Likewise, the brake switch block 80 is also shown schematically as 80A. The two switches are in series with the 12-volt supply and the solenoid bank composed of vacuum solenoid 34, vent solenoid 36 and purge vent solenoid 38.

The vacuum reservoir 42 receives vacuum via vacuum source 40 from the engine vacuum lines (not shown) which are generally available in the engine compartment of an automotive vehicle. The vacuum reservoir 42 feeds its vacuum to the vacuum valve body 32 which is metered by the vacuum solenoid 34, vent solenoid 36 and purge vent solenoid 38. In turn, the vacuum valve body 32 controls the vacuum actuator 44 which in turn controls the throttle, which is not shown.

Referring now to FIG. 3, a schematic diagram is shown of the speed sensor signal conditioning circuit which is typical of the blocks shown in blocks 58, 60, 62, 64, 66 and 68. For example, shown is the vehicle speed sensor signal from speed sensor 78 being presented to an RC network powered by V.sub.CC. The V.sub.CC voltage is divided down through resistor R76 which, in the preferred embodiment, has a value of 5.1 Kohms. The vehicle speed sensor signal is presented to the juncture of resistor R76 and resistor R125. Resistor R125 has a value of 20 Kohms and is in series with resistor 76 and is connected on its other end to capacitor C126 which has a value of 0.1 Microfarads. The capacitor C126 is connected between resistor R125 and ground potential.

The vehicle speed sensor signal from vehicle speed sensor 78 is presented through the RC network formed with the above recited components to an inverter which is represented as Z8. The signal is then presented to the microcontroller Z20.

FIG. 4 is a schematic diagram of the throttle position indicator signal conditioning circuit. The throttle position indicator signals from the throttle position indicator 46 are presented to the juncture of an RC network. The entire circuit is powered by a power signal V.sub.CC and is divided through a resistor R155 which has a value of 100 Kohms. The throttle position indicator signal is presented to the juncture of resistor R155 and a series connected resistor R156 which has a value of 10 Kohms. The other end of resistor R156 is connected to a capacitor C157 which has a value of 0.1 Microfarads. The capacitor C157 in turn is connected to ground.

The throttle position indicator signal is presented to an A/D converter shown as Z85 in FIG. 1 and FIG. 4 through the RC network. The resultant converted signal from A/D converter Z85 is then presented to the microcontroller Z20.

Referring now to FIG. 5, a schematic diagram is shown of the network-switch filter for signals from the set switch 70 or resume switch 72, park/neutral or clutch switch 76 and brake switch 80. An 8-volt supply is shown as powering the network-switch filter circuit. The various components are used to modify the signal as received from the various switch inputs and as sent out to the various signal conditioning (peripheral interface) blocks 58, 60, 62, 64, 66 and 68 which are shown in FIG. 1. The circuitry is repetitive and two of the repeating portions of the circuit are illustrated. The power signal of 8 volts is buffered through resistor R1 and R6, etc., and a signal input is received from various switches and presented to the juncture of resistor R1 and another resistor R2. The resistor R2 is connected to ground through a capacitor C5. The ground potential is then pulled up through resistors R3 and R4 which also receive a portion of the signal which has been presented through the juncture of R2 and C5. The signal output to the signal conditioning (peripheral interface) blocks 58, 60, 62, 64, 66 and 68 is then sent from resistor R3 or its equivalent in the other circuits.

Referring to FIG. 6, illustrated is a schematic diagram for the peripheral interface/signal conditioner and solenoid drivers. As shown, the peripheral interface/signal conditioner chip designated as Z83 has many switch input ports which are shown in FIG. 5. The peripheral interface Z83 also sends and receives signals to and from the microcontroller Z20. In addition, the peripheral interface Z83 sends signals to the vacuum solenoid 34 and the vent solenoid 36; Z83 includes the function of the signal conditioning blocks 58, 60, 62, 64, 66 and 68 from FIG. 1, as well as the interface function of blocks 54 and 56 from FIG. 1. The solenoid driver function of blocks 54 and 56 is separately shown in FIG. 6. These solenoid driver signals are then fed to a typical solenoid driver circuit which is schematically represented in FIG. 6. The solenoid driver circuits are essentially the same in each case. Shown is a signal presented in parallel to a resistor RC40C which has a value of 12 Kohms. In parallel with resistor RC40C, is capacitor RC40B which has a value of 0.0022 Microfarads. This conditions the signal from the peripheral interface Z83 and presents it to an amplifier Z43 for presentation to the vacuum solenoid 34 or vent solenoid 36 as filtered by a capacitor RC40D which has a value of 0.0022 Microfarads. The capacitor RC40D is connected across the output of the amplifier Z43 to ground. For feedback purposes, the feedback resistor RC40A is provided which has a value of 27 Kohms. The diagnostic function of this circuit is completely described in the commonly assigned U.S. Pat. No. 4,612,638 to Kissel, issued on Sept. 16, 1986, entitled "Diagnostic Protection Circuit and Method Using Tri-State Control And Positive Feedback" which is hereby expressly incorporated by reference.

Referring now to FIG. 7 and FIG. 8, an overview of the method for electronic speed control is shown in flowchart form.

The method begins in block 100. It is to be recognized that the engine control logic module 50 controls a large number of sensors, actuators, etc., throughout the engine and receives data from various points. Therefore, the microcontroller Z20 is doing many things and will have a main control program which is either interrupted for use by the electronic speed control system shown in FIG. 1, or is branched from in order to respond to the needs of the electronic speed control system. Therefore, block 100 is represented as jump from the main program. An equivalent would include the use of a microcontroller or microprocessor dedicated to the electronic speed control function.

The method next calls, in block 110, for a check of the speed control power on/off switch 74A. The method checks the speed control power on/off switch 74A to see whether it is on or off. If it is off, the method then proceeds to block 112 to clear the set speed stored in memory Z51 to eliminate a resume condition from occurring after engine restart and then to disengage the speed control in block 120 and to eventually return to the main program in block 210.

Returning to block 110, if the power on/off switch 74 is on, the method falls through to block 130 to see if the resume switch 72 is locked on. If not, the method clears the RESSW flag in block 131. If the resume switch 72 is locked on, the method branches to block 132.

Next, the method goes to block 132 to check to see whether the vehicle is ready for speed control. This condition is usually indicated by a call for some type of speed adjustment, i.e., whether car speed is above or below a window of acceptable speed around a set speed or whether the operator has called for the first instance of speed control by engaging the power on/off switch 74 and the set switch 70.

Next, the method checks in block 133 to see whether the engine speed is too high. This is done by taking an input, the engine speed, which is available information from the other portions of the engine control logic module 50 and is generated initially by speed sensor 78. The engine speed is then compared to a value stored in the MEMORY Z51 and if it is too high, the method branches to block 120 to disengage the speed control. If, however, the engine speed is not too high, the method branches to block 134 to check to see whether the last vehicle speed as sensed in speed sensor 78 is too low to allow the use of the electronic speed control. If the last vehicle speed sensed is too low, the disengaged speed control operation occurs in block 120. That is, the sensed vehicle speed and engine speed are compared to predetermined limits stored in memory Z51. If outside the limits, the electronic speed control is disengaged.

If the last vehicle speed is not too low, the method falls out of block 13 and then either checks in block 135 to see whether the vehicle is in park or neutral or checks to see whether the clutch is depressed in block 135. The choice will be determined by the type of transmission employed in the vehicle, the block 135 being used if the vehicle employs an automatic transmission and block 136 being employed if the vehicle utilizes a manual transmission. If the clutch is depressed or if the vehicle is in park or neutral, as checked in blocks 135 and 136, the method branches to block 120 to disengage the speed control.

If the vehicle is not in park, neutral as checked in block 135, or the clutch is not depressed as checked in block 136, the method falls through to check whether the brake is applied in block 138, disengaging the speed control in 140 if it is applied and, if not, going to block 139 to check to see whether the vacuum solenoid and vent solenoid ports are working. If not, the method branches to a fault routine in block 141, returns and disengages the speed control in block 140. If the ports are working, as checked in block 139 (utilizing the method and circuitry described in commonly assigned U.S. Pat. No. 4,612,638, entitled "Diagnostic Protection Circuit And Method Using Tri-State Control And Positive Feedback", which has been incorporated by reference), the method falls through to block 150 to check to see whether a set condition is called for by the operation of the set switch 70 in the stalk column. If the set is called for as checked in block 150, the method branches to block -60 to save the vehicle speed as it currently exists and defines this as the set speed.

Returning to block 150, if the operator has not called for a new set speed, then the method checks to see whether this is a tap in block 170. This refers to the tapping of the set switch 70 on the stalk switch assembly located on the steering column. If a tap condition has occurred, then the method branches to 180 to add 2 miles per hour to the set speed and then opens the throttle slightly in block 182 before engaging the speed control in block 202.

Returning now to block 170, if the condition is not a tap, then the method falls through to block 190 to check to see whether the condition as sensed is a resume condition as called for by the operation of the resume switch 72 on the stalk column. If the resume condition is called for in block 190 or the set condition is called for in block 150, the method then flows to block 200 to open the throttle and then engage the speed control in block 202.

Returning to block 190, if the resume condition is not sensed, then the method checks to see whether the operator has called for a deceleration/reset condition by appropriate operation of the set switch 70 on the stalk switch assembly on the steering column. This occurs when the operator of the vehicle continuously depresses the set switch 70 and holds it until the desired lower speed is achieved. If the method detects a deceleration/reset condition in block 192, it branches to block 194 to disengage the speed control, close the throttle in block 196 and upon release of the set switch (button) 70 on the stalk by the operator in block 198, the method will save the vehicle speed as the set speed and return to block 200 to open the throttle and engage the speed control in block 202.

Returning to block 192, if the condition detected is not a deceleration/reset condition, the method skips to block 203 to see if it is time to calculate the vehicle speed. Block 204 is entered after 121 msec. have passed and vehicle speed is calculated according to the formula (utilizing a speed sensor 78 interrupt service) (where "=" means "is redefined as"): ##EQU1##

In essence, if the program skips block 202 and enters block 203 directly, this means that either it is not desired to engage the electronic speed control (although the vehicle conditions may allow for it to be engaged) or it is already engaged and the operator of the vehicle desires for the speed control to continue unchanged. Similarly, if the method arrives at block 202 (from block 200), this means that the operator desires the speed control to begin or to become engaged, or that the operator of the vehicle wants to make a change in the speed control set speed.

All conditions prior to the calculation of the vehicle set speed in block 204 are checked every time the main program completes a loop which is every 11 msec. Vehicle speed is updated on a speed sensor 78 interrupt basis: i.e., when 8 pulses have been detected (signifying one complete revolution of the speed sensor cable) as new vehicle speed is calculated. Waiting 121 msec. (11 main program loops) assures us that a new vehicle speed has been calculated (is ready). If a new vehicle speed is not ready (i.e., the 121 msec. have not passed), we return to the main program in block 210 and wait for another interrupt to occur.

Next, the method falls through to block 205 to compensate for the cable length from the speed control vacuum actuator 44 to the throttle linkage.

Next, the method falls through to block 206 to calculate the vehicle acceleration according to the formula (Note: division by 8=1/8=0.125, a close approximation to 0.121):

Next, the method falls through to block 208 to check to see whether the speed control is engaged.

The actual physical disengagement of the speed control involves the reading of a flag BRKSET by the program. This is done at block 208. The speed control is engaged if the BRKSET flag is set to a logical zero condition and is disengaged if the BRKSET flag is set at a logical one condition.

If the flag BRKSET is a logical one, the program calls for a 165 msec. vent pulse output, which is the maximum possible. A vent timer will then be reloaded with 165 msec. until the BRKSET flag is cleared which happens in blocks 150, 170, 190, 192 and 202 after the operations in each of those respective blocks.

If the vehicle's brakes are applied while the vehicle is cruising or operating under electronic speed control, or if the power on/off switch 74 is turned "off", the BRKSET flag goes to a logical "1" level. The BRKSET flag goes to a logical zero (clear) when the vehicle is cruising under electronic speed control (including TAP, SET and RESUME functions and excluding DECELERATION (note that BRKSET is cleared when the set button is released after DECEL)). Therefore, the BRKSET flag is the electronic speed control engage/disengage indicator.

If the speed control is not engaged, the method branches to block 209 to begin or to continue venting the vent solenoid 36 and then moves to block 210 and returns to the main program. If the speed control is engaged as checked in block 208, the method falls through to block 220 to calculate the speed error which is a plus or minus signal. Next, the method falls through to block 222 to look up in a table in memory Z51 or to calculate the desired acceleration which can be a plus or a minus signal.

The method calculates the acceleration error (the difference between the desired acceleration and the actual acceleration) which is also a plus or a minus signal which is also in block 224 and adds it to the previous acceleration errors in block 226.

Next, the summed acceleration limit is calculated or looked up in a table in memory Z51 as shown in block 228 and then checked in block 230 to see whether the summed acceleration error is greater than a designated limit. If the summed acceleration error is less than a designated limit, the method branches to block 240 to save the summed acceleration error and to maintain the throttle position in block 242 and to return to the main program in block 244.

Returning to block 230, if the summed acceleration error is greater than a predetermined limit, the method falls through to block 250 to clear the summed acceleration error and then proceeds to block 252 to check to see whether acceleration is needed to return to the set speed. If not, the method falls through to block 270 to decelerate or close the throttle slightly and to return to the main program in block 272.

Returning to block 252, if acceleration is needed to return to the set speed, then the method branches to block 260 to accelerate or open the throttle slightly and then return to the main program in block 272.

Referring now to FIG. 9, FIG. 10, FIG. 11, FIG. 12 and FIG. 13, detailed flowcharts are presented describing the method for electronic speed control claimed herein.

As previously described, the integrated electronic speed control method described herein is designed to be integrated into the control strategy of the engine control computer and used on an as-needed basis. Therefore, block 500 shows a jump step to the electronic speed control software methods from a main engine control strategy being utilized by the engine control logic module 50. It is to be appreciated that all the functions described herein could be incorporated into a microcontroller dedicated to electronic speed control thereby eliminating the need to jump from a main program.

The method first checks to see whether the power on/off switch 74 is on in block 502. If not, the method clears the variable reserved for the vehicle set speed (SETSPD) in block 50- to eliminate a resume condition after engine restart (reference: block 112), and then branches to block 540 to disengage or "break" the electronic speed control and to set the BRKSET flag indicating that the speed control is stopped or disengaged, clear the ACLFLG (the RESUME/TAP MODE indicator), and to clear the SETFLG (the indicator for set switch 70) and clear the set switch timer.

If the electronic speed control power on/off switch 74A is on, the method falls through to block 503 to see if the resume switch 72 is locked on. If not, the method clears the RESSW flag in block 503A. If the resume switch 72 is locked on, the method branches to block 504. (This explanation can be cross referenced to block 130 and following in the overview flowcharts shown in FIG. 7 and FIG. 8).

Next, the method falls through to block 504 to check the engine speed to see whether it is above 5,000 rpm (reference: block 133). If it is, the method again branches to block 540 to disengage the electronic speed control set the BRKSET flag, clear the ACLFLG, clear the SETFLG, and clear the SET SWITCH timer. If the engine speed is less than 5,000 rpm, the method falls through to block 506 to monitor the vehicle speed and check to see whether it is less than a variable called low speed cut-out, hereinafter abbreviated LOSPCO (reference: block 134). The LOSPCO is a variable which can be stored in a look-up table in memory Z51 in the engine control logic module 50. LOSPCO is the minimum speed at which the electronic speed control system shown in FIG. 1 will operate or stay engaged; otherwise, block 540 is entered.

If the vehicle speed is greater than LOSPCO, the method falls through to block 508 to check to see whether the transmission is in park or neutral (as indicated by the park/neutral switch on an automatic transmission equipped vehicle) or to block 510 to check whether the clutch is depressed (a indicated by the clutch switch for a manual transmission equipped vehicle). These switches are represented in the diagram in FIG. 1 as block 76 and can be either a hardware switch or a software switch or flag. This corresponds to block 135 and block 136 in FIG. 7.

If the transmission is in park/neutral or the clutch is depressed as indicated by switch 26, the method branches to block 540 to disengage the electronic speed control, to set the BRKSET flag, clear the ACLFLG, clear the SETFLG and clear the set switch timer. If the park/neutral/clutch switch 76 is off, the method falls through to block 512 to check to see whether the brake is applied. This is determined by looking at the condition of the brake switch 80. If the brake has been applied, the method branches to block 540 to disengage the electronic speed control as previously described. This corresponds to block 138 in FIG. 7. If the brake is not applied, the method falls through to block 514 to another decision block to check the vacuum and vent ports to see whether they are working. These ports are on microcontroller Z20. This is done via the circuitry and method described and claimed in commonly assigned U.S. Pat. No. 4,612,638, entitled "Diagnostic Protection Circuit and Method Using Tri-State Control and Positive Feedback" to Kissel which has been expressly incorporated by reference. If not, the method branches to block 520 and jumps to a fault routine hereinafter called FAULTL, generates and stores a diagnostic fault code and then returns proceeding to block 540 to disengage the electronic speed control as previously described. This corresponds to block 139 on FIG. 7.

If the vac/vent ports on microcontroller Z20 are working, the method falls through to block 530 to check to see whether the set switch 70 is on (reference: blocks 150 and following).

If the set switch 70 is on, the method falls through to block 531 to set the set switch indicator flag (SETFLG) and then to block 532 to increment the set switch timer internal to the microcontroller Z20. The set switch timer is set for 11 msec. of counts. Next, the method falls through to block 534 to check t see whether the set switch 70 has been engaged for a time period greater than a variable called SETIME. The variable SETIME is a stored value in memory of Z51 which is a time period of about 400 msec. beyond which, if the set switch 70 is still engaged, that the electronic speed control system shown in FIG. 1 will interpret that the operator of the vehicle desires to decelerate the vehicle down from the current set speed. The speed of the vehicle coasts down, therefore, decreased by a continuous depression of the set switch 70. If the set switch 70 has been depressed for a time greater than SETIME, the method branches to block 540 to disengage the speed control which acts to decelerate or to coast the vehicle and to reset the speed control. If the set switch 70 has not been depressed for the SETIME, the method falls through to block 600 (to be explained below).

Returning now to block 530, if the set switch 70 is not depressed, the method branches to block 548 to see if the set switch 70 was depressed previously, during the current drive time. This is done by looking at a flag SETFLG stored in memory Z51 to see if SETFLG equals 1. If the set switch 70 was not depressed as checked in block 548, the method branches to block 582 to see whether a RESUME condition exits.

If the resume switch 72 is not depressed, the method branches to block 600, the operation of which will be explained below.

If the resume switch 72 is depressed as checked in block 582, the method falls through to block 586 to see whether ACLFLG flag is set or clear. If the flag is set, the method branches to block 600.

If the ACLFLG flag is clear, the electronic speed control via microcontroller Z20 interprets the action of the operator as a RESUME condition and proceeds accordingly. The method then sets ACLFLG and clears BRKSET n block 587 and then falls through to block 588 to interpolate the SETPW variable (see description with respect to block 564) and get the appropriate number of set pulses in multiples of 11 msec. counts. Next, in block 590, the method checks to see whether the vehicle speed is greater than the set speed. If so, the method branches to block 570. If the vehicle speed, as checked in block 590, is less than the current set speed, the method falls through to block 592 to interpolate the variable RESTBL which is an additional source of vacuum pulses for RESUME conditions. This means that the resume pulses are retrieved in multiples of 11 msec. counts. The interpolation proceeds as described with respect to blocks 564 and 588. There is a separate look-up table in memory Z51 for RESTBL. The data comes from a point slope curve similar to that shown in FIG. 15. The data in the table is a function of the difference or delta between the speed the vehicle is traveling as compared to the set speed from memory Z51.

Next, the method falls through to block 594 to add the resume pulse to the set pulse and then branches to block 570 to load the vacuum timer internal to microcontroller Z20 with the set pulse before falling through to block 600.

If the set switch 70 was depressed as checked in block 548, the method clears the flag SETFLG in block 549 and then falls through to block 550 and checks to see if the set switch 70 was depressed for greater than 22 msec. This 22 msec. time period is called the debounce time. A timer within the microcontroller Z20 monitors this time period. The debounce time is experimentally determined to be the time the set switch 70 must be engaged before the microcontroller Z20 interprets the signal so created as a legitimate SET or TAP signal. This allows for the occurrence of a stray signal created by an accidental bump or mechanical jarring of the set switch 70. A legitimate SET or TAP signal will be longer than the debounce time of 22 msec., but less than the SETIME minimum of about 400 msec. as previously described with respect to block 534.

If the set switch 70 was depressed for greater than 22 msec., the method falls through to block 552 to check the condition of the BRKSET flag indicating whether the system is engaged or not. If BRKSET is clear, the method falls through to block 554 to check the vehicle speed to see whether it is greater than the set speed stored plus 2 miles per hour; if not, the system interprets this action of the operator as a TAP and proceeds to block 555 to set the ACLFLG flag and branches to block 556 to add 2 miles per hour to the stored set speed and to save this new value as a new set speed in memory Z51. Next, the method falls through to block 558 to load the vacuum timer, internal to microcontroller Z20, with 2 loop times or two 11 msec. pulses which is equal to 22 msec. Thereafter, the method branches to block 568.

Returning to block 552, if the BRKSET flag is set, the method will branch to block 559 to clear the BRKSET flag and then to block 560 to see whether the vehicle speed is greater than or equal to a variable called MINSET which is the minimum set speed allowed in order to use the electronic speed control system shown in FIG. 1. Block 559 is also entered via block 554 if the vehicle speed is found to be greater than the stored set speed plus 2 miles per hour.

In block 560, if the vehicle speed is less than the MINSET value, the method branches to block 561 to clear SETSPD and then to block 600. If the vehicle speed is greater than or equal to the MINSET value, the microcontroller Z20 interprets the action of the operator as a SET command and falls through to block 902 where the clutch mask (CLCHMK) is cleared. Next, the command falls through into block 562 where the current vehicle speed is saved and defined as the new set speed. Next, in block 904, the deceleration mode is checked to determine if the vehicle is in a deceleration mode. If the vehicle is in a deceleration mode, the method branches to block 568. If the vehicles is not in a deceleration mode, the method falls through to block 906 where the speed control cable timer (SCUCAB) and error maximum (ERRMAX) are cleared. SCUCAB is a dual purpose timer used to measure an "error sample delay time" and also "error sample time" as will be explained herein. ERRMAX is the maximum "set" error for the particular "set" pulse that has just been fired. Both SCUCAB and ERRMAX are RAM functions.

Next, in block 908, the method falls through to set the set test (SETTST). Next, the method falls through into block 564 where a set-up pulse is determined. Next, in block 910, a pulse width adjust (PWADJ) term is added to the set-up pulse. The PWADJ is a number of 11 msec. pulses added to or subtracted from the set-up pulse. PWADJ is also a RAM function.

Next, the method falls through to block 568 to check the vehicle speed to see whether it is greater than a stored value MAXSET which is the maximum allowable set speed allowed for use by the electronic speed control system shown in FIG. 1. If the current set speed is greater than the MAXSET value, the method branches to block 566 to save the MAXSET as the new set speed. The output of blocks 566 and blocks 568 both ar fed to block 570 to load the vac timer with the appropriate pulse as interpolated in block 564 and 910 or as specified in block 558. Thereafter, the method falls through to block 600.

Returning to block 550, if the set switch 70 was depressed for less than 22 msec., the method branches to block 600.

Referring now to block 600, the method checks to see whether a new vehicle speed exists. If not, as shown in block 602, the method branches to block 672 (to be explained below). A new vehicle speed is found in block 600 by waiting for 11 loop times or 121 msec.; for a new vehicle speed signal from speed sensor 78, then the information from the speed sensor 78 is processed. This is averaged with the old vehicle speed and then redefined as a new vehicle speed (block 204).

The vehicle speed then drops into the adaptive cable routine (block 205) prior to the calculation of acceleration. As illustrated in FIG. 11(a), the calculated new car speed from block 600 falls through to block 912 where the brake set flag (BRKSET) is checked. If the BRKSET flag check is a positive one, the method leaves block 912 and falls into block 206. If the BRKSET is not set, the method falls through to block 914 where the EVENT flag is checked. If the EVENT flag is not set, the method branches to calculate the current acceleration. If the EVENT flag is set, the method falls through to block 916 where the SETTST flag is checked to see if it has been cleared. The SETTST and EVENT are bits used for adapted cable updating and are described by the timing diagram illustrated in FIG. 11(b).

The SETTST flag is set which initiates a set-up pulse from the speed control vacuum actuator to the throttle. At the end of the set-up pulse, which generally takes between approximately 400 to 600 msec., the EVENT flag is at the end of the pulse. At this time when the EVENT flag is set, the vac/vent timer (VVTIMR) is equal to zero. After the EVENT flag has been set there is a delay time for which the vehicle adapts to the new cruise control setting. This delay time is generally equal to about 1-4 seconds and is not desired to be included in the error sampling time. After the delay time has passed, the SETTST flag is cleared and the timer moves into the error sampling time, as seen in FIG. 11(b). The error sample time is generally 1-4 seconds and at the end of the error sampling time, the EVENT flag is cleared. Both SETTST and EVENT functions are RAM functions.

After the EVENT flag is checked the method falls through to block 916 where the SETTST flag clear is checked. If the SETTST flag is clear, the method falls through to block 924. If not, the method falls through to block 918. At that time the SCUCAB is checked to see if the timer is less than the speed control counter delay (SCKDLY). The SCKDLY is the error sampling delay time after the set-up pulse. The SCKDLY is a calibration constant and has a predetermined value. If SCUCAB is less than SCKDLY the method moves to block 920 where SCUCAB is incremented. The method then falls through to the calculation of acceleration. However, if SCUCAB is greater than or equal to SCKDLY the method falls through to block 922 where SETTST and SCUCAB are cleared.

After block 922, the method falls through to block 924 where SCUCAB is checked with the speed control counter error (SCKERR). SCKERR is the error sampling time after the delay time. This is a calibrated constant and is generally about two to four seconds. If SCUCAB is less than SCKERR the method branches to block 926 where SCUCAB is incremented. The method then falls through to block 928 where a temporary error (ERRTEMP) is determined. The ERRTEMP is determined by the desired set speed (SETSPD) added with the speed control adapted cable control point (SCSCAB), the quantity, minus the actual car speed (CARSPD). SCSCAB is a control point for the speed control adaptive cable. This is a calibrated constant and generally varies a fraction between zero to one (e.g. 1/8, 1/4, 1/2, 1/16, etc.).

Next, the method falls through to block 930 to check the absolute value of ERRTEMP with respect to the absolute value of ERRMAX. If the absolute value of ERRTEMP is greater than the absolute value of ERRMAX, the method falls through to block 932 where the value of ERRTEMP becomes the new ERRMAX value. If the absolute value of ERRTEMP is less than the absolute value of ERRMAX, then the method falls through to calculate acceleration (ACCO). Also, if ERRMAX is replaced with ERRTEMP, the method falls back to calculate acceleration (ACCO).

If SCUCAB is greater than SCKERR in block 924 the method falls through to block 934. At this point, the method checks to see if ERRMAX is greater than the speed control ERRMAX dead band (SCSEDB). The SCSEDB is a calibrated constant which is a range of acceptable error for the cruise control to function properly without updating the PWADJ. If ERRMAX is less than SCSEDB, the method falls through to block 956 where the EVENT flag is cleared. The method then falls through to calculate acceleration (ACCO).

In the event ERRMAX is greater than SCSEDB, the method falls through into block 936 where ERRMAX is added to error total (ERRTOT) and a new ERRTOT is calculated. ERRTOT is the accumulation register for the ERRMAXs during the set. ERRTOT is also a RAM function.

After a new ERRTOT has been determined in block 936, the method falls through to block 938 where ERRTOT is checked against the speed control high trigger point (SCSTGH). The SCSTGH is the trigger point at which point ERRTOT exceeds a set maximum limit. SCSTGH is a calibration constant and limits the amount of error. If, in the case a malfunction occurs, and the error continues to climb, the SCSTGH will limit the continuing of the method.

If ERRTOT is greater than SCSTGH in block 938, the method branches to block 940 where PWADJ is readjusted. In block 940 the PWADJ is added with a speed control time increment (SCUINC) to determine a ne pulse width adjust (PWADJ) term. SCUINC is an increment term, generally one or two, 11 msec. intervals, for adjusting the PWADJ term. The method then falls through to block 94 where the PWADJ is checked with the speed control pulse width adjust high limit (SCULMH). The SCULMH is the PWADJ high limit, and is a calibration constant and serves to limit the continued climb of the PWADJ term in the event of a malfunction. SCULMH is approximately 20 times the 11 msec. interval. If the PWADJ is greater than SCULMH, the method falls through to block 944 where SCULMH becomes the new PWADJ term. The method then falls through to block 954 where ERRTOT is cleared. However, if the PWADJ in block 942 is less than SCULMH, the method branches off and falls through to block 954.

In block 938, when ERRTOT is greater than SCSTGH, the method branches to block 946 where ERRTOT is checked with the speed control error total low trigger point (SCSTGL). The SCSTGL, like the high trigger point, limits the low point of the ERRTOT and is a calibrated constant. In the event that ERRTOT is greater than SCSTGL, the method branches to block 956 to clear the EVENT flag.

In block 946, if ERRTOT is less than SCSTGL, the method falls through to block 948 where PWADJ is again determined. In block 948, speed control time decrement (SCUDEC) is subtracted from the PWADJ to come up with a new PWADJ. The SCUDEC is an increment by which the PWADJ term is decremented to become a new PWADJ term. SCUDEC is a calibration constant and is generally 1 or 2 times the 11 msec. interval. After block 948, the method falls through to block 950 where PWADJ is checked with the speed control pulse width adjust low limit (SCULML). SCULML is a calibration constant and is the low limit for the pulse width adjust. The SCULML is approximately 20 times 11 msec.

If PWADJ is greater than SCULML in block 950, the method branches to block 954 where ERRTOT is cleared. In the event PWADJ is less than SCULML in block 950, the method falls through to block 952 where SCULML becomes the new PWADJ. The method falls through to block 954 where ERRTOT is cleared. From block 954, the method falls through to block 956 where the EVENT flag is cleared. After the EVENT flag is cleared in block 956, the method falls through to calculate the acceleration.

This new vehicle speed is then used in block 604 to calculate the current acceleration. That is, if a new vehicle speed exists as checked in block 600, the method falls through to block 604 to calculate the current acceleration to be equal to 1/8 of the difference between the variable's OLDSPD and NEWSPD. The calculated current acceleration employs as 1/8 factor in the calculation. The 1/8 factor represents 1/8 sec. or 0.125 sec. which closely approximates 121 msec. or 11 loop times. The (NEWSPD-OLDSPD) is a difference in speed over 121 msec. Dividing by 1/8 sec. closely approximates the correct acceleration in this period with the appropriate distance/time.sup.2 units. The new acceleration is then averaged with the old in block 605 (reference: block 206).

Next the method falls through to block 606 to check to see whether the speed control is engaged as indicated by the condition of the BRKSET flag. The significance of the BRKSET flag has been described above with respect to block 540.

Blocks 610 through 640 comprise the feature known as CALERR. CALERR is a method of determining and using a filtered speed error in an integrated acceleration based electronic speed control system for vehicles.

Speed error is calculated by finding the difference between set speed and vehicle speed and then filtering the result. The error is tested for polarity and magnitude before selecting a desired acceleration rate.

If the electronic speed control is not engaged, the method branches to block 608 to load the vent timer with 15 counts. This corresponds to a vent pulse of 15 times 11 msec. in duration. Returning to block 606, if the speed control is found to be engaged, the method falls through to block 610 to calculate a variable called DELTASPEED. DELTASPEED is equal to the difference between the set speed value and the vehicle speed value. After this calculation, the method falls through to block 612 to check to see whether the DELTASPEED value calculated in block 610 is positive.

If the DELTASPEED is positive as checked in block 612, i.e., the set speed is greater than the vehicle speed, the method branches to block 614 to determine whether the system is in a resume or a tap mode. This is done by checking the condition of the flag ACLFLG. If ACLFLG equals zero, the system is not in a resume or tap mode and the method branches to block 616 to interpolate the variable VACREG from a table of values taken from a point-slope curve as shown in FIG. 17 to retrieve (as done in previous interpolations) the desired acceleration value from memory Z51 which is positive. The variable VACREG is the REGULAR DESIRED ACCELERATION CURVE. This is to be distinguished from the variable VACACC which is the DESIRED ACCELERATION CURVE or table of values taken from the curve in FIG. 16 for the RESUME/TAP mode. Basically, these curves are a table of values stored in memory Z51 which the system uses to look up the values needed for a smooth return to the set speed or, more specifically, how much acceleration is needed to return to the set speed by controlling the vacuum solenoid 34. The data in the VACACC table provides faster acceleration than the VACREG table.

Following block 616, the method branches down to other parts of the routine using VACREG, the desired acceleration (positive) from block 616 to compute the acceleration error.

Returning now to block 614, by monitoring the flag ACCFLG, if the system determines that the operator of the vehicle has called for a resume or a tap, the system falls through to block 618 to compare the variable DELTASPEED with the variable ACLRST. The comparison is made by checking to see whether the variable DELTASPEED is greater than or equal to a variable ACLRST. The ACLRST is a variable which is the DELTASPEED required to reset an acceleration flag ACLFLG; this indicates the end of a resume or tap mode.

If the DELTASPEED is greater than or equal to ACLRST as checked in block 618, the method branches to block 620 to interpolate the variable VACACC as previously described with respect to block 616. Alternatively, if the DELTASPEED variable is less than the constant ACLRST, the method falls to block 619 to cancel RESUME/TAP mode by clearing the ACLFLG flag--and then falls through to block 620 to interpolate the variable VACACC, described above, to retrieve the desired acceleration value, which is positive, before proceeding to fall through to other blocks in the routine using VACACC to compute the acceleration error.

Returning again to block 612, if the DELTASPEED is not positive, the method, in block 628, takes the absolute value, makes the delta positive, then clears ACCFLG in block 629, cancelling the RESUME/TAP MODE, the method falls to block 630 to again interrogate the DELTASPEED variable to see whether it is greater than a constant VNTAB1. The constant VNTAB1 is a limit to the maximum overspeed error allowed before the vent time is 100 percent (continuous venting).

If the DELTASPEED is less than or equal to the constant VNTAB1, the method falls through to block 632 to again interrogate the variable DELTASPEED to see whether it is greater than the constant VNTAB2. The constant VNTAB2 is an overspeed limit corresponding to 1/2 the maximum vent time allowed by the system. VNTAB1 and VNTAB2 are limits that, when triggered, will close the throttle as rapidly as possible; both are stored in memory Z51.

If the now positive DELTASPEED variable is less than or equal to the constant VNTAB2, the method falls through to block 634 to interpolate the point slope curve in FIG. 18 for the variable VENTRG, the regular desired acceleration rate for the vent solenoid 3 to retrieve the desired acceleration value which is negative. (This can also be done in a look-up table.)

After the variable VENTRG is interpolated and the desired deceleration value is retrieved from memory Z51, the method falls through to other blocks in the program which will be described below, but essentially the outputs from the steps performed in blocks 616, 620 and 634 all fall through to block 640 having captured the desired acceleration to compute the acceleration error.

Returning to block 630 and 632, if the DELTASPEED variable is less than the constant VNTABI as checked in block 630, and if the DELTASPEED variable is greater than the constant VNTAB2 as checked in block 632, the method moves to close the throttle (at a 50 percent rate in block 636). If the method branches from block 630 showing that the DELTASPEED variable is greater than the constant VNTAB1, the method branches to block 608 to load the vent timer (internal to the microcontroller Z20) with a 15 times 11 msec. continuous vent period. Similarly, if the method moves to close the throttle from block 632, the branch is to block 636 and the vent timer is loaded with a 5 times 11 msec. continuous time period resulting in a 55 msec. vent time. From block 608 or 636, the method falls through to block 672 which will be described below.

Blocks 642 through 666, including the branch through to block 662, comprise the feature known as ERRCHK. ERRCHK is a method for determining and using an acceleration correction in an integrated acceleration based electronic speed control system for vehicles.

An error correction pulse is selected by integrating (or summing) the differences between desired acceleration and the actual vehicle acceleration. The integral is compared to a trigger window. The throttle position is controlled based on the value of the integral as compared to the window. This is key in providing smooth control. The integration action serves to filter transient acceleration errors and to dampen throttle response to prevent throttle correction at a faster rate than the vehicle can respond thereby reducing over and under shoot of the throttle.

Returning now to the point in the method which follows the interpolation of the variables VENTRG, VACREG or VACACC, the method finds itself in block 640 subtracting the actual acceleration from the desired acceleration to compute an acceleration error. The acceleration error term computed in block 640 is added to a sum register in block 642 and is now called the summed acceleration error (ACCEL ERROR). The method next, in block 644, saves the sign of the sum register in memory and next, in block 646, interpolates the variable THGAIN which is the variable for the throttle gain factor. The throttle gain factor THGAIN is basically a dampening curve and it is stored in memory from a table or from a curve as shown in FIG. 19. It is a linear interpolation table in memory Z51 of the desired gain for throttle response as mapped against DELTA THROTTLE throttle position minus the MINIMUM THROTTLE position; THR - MINTHR.

MINTHR represents the lowest and MAXTHR represents the highest observed throttle and is completely described in commonly owned U.S. Pat. No. 4,637,361, issued on Jan. 20, 1987 to Killen et al., which has been expressly incorporated by reference.

The method next falls through to block 648 to interpolate the variable SPGAIN (from a table or from a curve as shown in FIG. 20), the speed gain factor used in combination with the throttle gain factor THGAIN to form a sum which is called SCGAIN, which is the speed control gain factor for the entire system. The computation of the total gain for the speed control system is done in block 650 and is called SCGAIN.

Next, the system moves to block 652 to retrieve the absolute value of the sum register in microcontroller Z20 which is holding the summed acceleration error.

Next, the method moves to block 654 to look at the absolute value of the summed acceleration error and see whether it is greater than or equal to the total gain for the speed control system, SCGAIN. This is done in block 654. If the absolute value of the summed acceleration error is greater than or equal to SCGAIN, the method falls through to block 656 to clear the sum ACCEL ERROR register and then to look at the sign of the sum ACCEL ERROR register in block 658 which was saved in block 644. If the sign of the sum register is positive, the method continues to fall through to block 660 to check to see whether the actual throttle position is greater than or equal to the maximum allowable throttle position value MAXTHR. If so, the method branches to block 672 and no vacuum action will be called for. If not, a vacuum pulse is loaded into the vacuum timer which corresponds to an 11 msec. pulse; this is done in block 662. Returning to block 658, if the sign of the sum register is not positive, the method branches the block 664 to check the actual throttle position value and compare it to the constant CLOTHR which is a constant which prevents the vent action if the actual throttle position is less than the stored constant CLOTHR. If the throttle position is greater than or equal to the variable CLOTHR, the method falls through to block 666, loading the vent timer with two 11 msec. time periods resulting in a 22 msec. vent pulse. Next, the method falls through to block 672. Returning to block 664, if the throttle position is less than the variable CLOTHR, the method automatically falls through to block 672 and no vent action is called for.

Returning now to block 654, if the absolute value of the summed acceleration error in the sum register is less than the total gain of the speed control system SCGAIN, the method branches to block 668 to hold the pulse by saving the sum register in block 668 and then by clearing the vacuum and vent timers in block 670 and falling through to block 672.

In block 672, the vacuum timer is checked to see whether its value is equal to zero. If it is, the method in block 674 then checks the vent timer to see whether it is equal to zero. If so, the method falls through in block 673 where the SETTST flag set is checked. If the SETTST flag is not set, the method branches to block 686 and returns to main. If the SETTST flag in block 673 is set, the method falls through to block 675 where the EVENT flag is set. If the EVENT flag is set the adaptive cable routine (205) will continue at block 914 when the system is in the adaptive cable routine. After the EVENT flag is set in block 675, the method falls through in block 676 to set bit 0 (5) equal to a logical one setting and to set bit 7 to a logical zero in RPIDRA, a specific location in the memory Z51 shown in FIG. 1 causing the throttle to hold its current position. These bits are the control signals for the solenoid driver circuits; a logical "0" turns on the driver which allows current to flow and a logical "1" turns the driver off. This should not be confused with the truth table information in FIG. 2 which merely described the overall throttle action vis-a-vis the solenoid action.

Once the output is sent to the memory Z51 in block 676, the method returns to the main control strategy in the engine control logic module 50 in block 686.

Returning to block 672, if the vacuum timer is not equal to zero, the method branches to block 678 to decrement the vacuum timer and output in block 680, a signal to the same memory Z51 location RPIDRA only this time placing a logical zero in bit 0 and a logical zero in bit 7 causing the throttle to open for the vacuum timer period before falling through to return to the main control strategy in block 686.

Returning to block 674, if the vent timer is not equal to zero, the method branches to decrement the vent timer in block 682 and in block 684 outputs a logical one to bit location 0 and a logical one to bit location 7 in the memory Z51 location in RPIDRA causing the throttle to close for the vent time period before falling through to block 686 and returning to the main control strategy.

The bit pattern of RPIDRA the solenoid drive register, is communicated to the throttle actuator vacuum servo's vent and vacuum solenoids in the main engine control program every 11 msec. in the diagnostic routine as described in the commonly assigned Kissel patent '638. This technique allows for standard engine control diagnostics techniques to be performed on these solenoids and other solenoids.

Presented in FIG. 21 is a method of determining the condition of a manual transmission clutch and of a park/neutral gear in an automatic transmission in an electronic speed control system for a vehicle.

A method is shown to disengage an electronic speed control as a function of the condition of the park/neutral gear or manual clutch. If the automatic transmission lever is bumped from "drive" or the manual transmission clutch is disengaged (by depression of the clutch pedal or by putting the transmission in neutral) while the electronic speed control is operating, the method will sense this by detecting a difference in the ratio of engine speed to vehicle speed (N/V). If the ratio changes by +/-25 percent, the electronic speed control is disengaged.

Referring now to FIG. 21, the clutch check subroutine will be described. The clutch check routine is executed every eighth pulse from the speed sensor 78 on vehicles utilizing a manual transmission. In this regard, eight pulses from the speed sensor 78, in this particular embodiment, is equivalent to one revolution of the speed sensor. A signal generated by another sensor (an engine speed sensor) on the engine (not shown) creates a pulse called an engine pick-up pulse, where the frequency of the engine pick-up pulse signal is equal to the engine RPM divided by 30 for a four-cylinder engine. A counter is set up internal to microcontroller Z20 and is called CNTEPP, which is incremented for every engine pick-up pulse as it occurs.

Returning now to the description of the clutch check by the subroutine, the clutch bit in a designated data word is cleared after a set condition or a resume condition; therefore, there are three main memory locations in memory Z51 which are utilized in this subroutine. CNTEPP corresponds to the number of counts from the engine pick-up pulse per speed sensor revolution. This memory location stores the count from a counter internal to the microcontroller Z20 and this counter is incremented for each engine pick-up pulse as it occurs. Another memory location, OLDEPP, corresponds to the value of CNTEPP which existed at or upon the occurrence of a set or a resume condition. Another memory location called CLCHMK corresponds to the clutch bit. If CLCHMK is set, then the speed control should be in off condition.

Returning to block 700 in the clutch check subroutine as branched to on an interrupt basis as described above from the main electronic speed control method, if the clutch bit CLCHMK is not set, the method falls through to block 702 to check to see if the engine pick-up pulse count per speed sensor revolution is currently within 25 percent of the OLDEPP count. This is a window of acceptable counts which, if exceeded, will indicate in general that the N/V ratio has changed. If the count in CNTEPP is within 25 percent of the OLDEPP count, the method will branch to block 708 to clear the CNTEPP counter to start a new speed sensor revolution and return to the main control strategy in block 710 as no change has occurred from engagement of the clutch to upset the control of the engine from the electronic speed control.

Returning now to block 702, if the new count in memory location CNTEPP is not within the 25 percent window of the old count in OLDEPP, the method falls through to block 704 to set the clutch bit CLCHMK indicating that the clutch has been engaged as a significant (+/-25 percent) change in the N/V ratio usually indicating a changed gear condition. The method then falls through to block 706 to update the old count OLDEPP by reading the contents of the CNTEPP into the OLDEPP location. This block 706 is also entered if the clutch bit has been set as checked by block 700. The method next falls through to block 708 and 710 as previously described to return to the main program after clearing the counter CNTEPP to start another speed sensor revolution. The subroutine returns to the main program to block 510 carrying its decision to be used in the rest of the electronic speed control strategy.

Such a method can also be used by computing and monitoring the rate of change of engine speed or the ratio of vehicle speed to engine speed.

Presented in FIG. 22 is a method of disabling a resume switch in an electronic speed control system for vehicles.

A decision is made to disable the resume switch if it is found in an engage condition at the same time that normal electronic speed control cut-outs are in effect due to conditions such as: brake on, car speed too low, park/neutral gear engaged (automatic transmission), clutch engaged (manual transmission), RPM too high, or N/V (the ratio of engine speed N to vehicle speed V) is out of range

Referring now to FIG. 22, the resume switch check routine is described. Looking first at decision block 800 which is reached by a branch from the main electronic speed control routine described in this description as it relates to block 110 and block 502, the method calls for the polling of the speed control power on/off switch shown in FIG. 1 as item 74. If the on/off switch 74 is in the off condition, the method branches to block 802 to clear the set speed before branching back to the main electronic speed control routine from block 804 to disengage the speed control as shown in block 120 and block 540 and return to the main electronic speed control routine in block 806.

If the speed control on/off switch 74A is in the on condition as checked in block 800, the BRKSET flag is polled in block 810 to determine it condition. If the BRKSET flag is in the set condition, the method falls through to block 812 to make another decision based on the condition of the resume switch shown as item 72 in FIG. 1. If the resume switch 72 is off, the method falls through to block 814 to clear the resume switch flag (RESSW). Clearing the RESSW flag allows the Resume mode to be enabled. This now means the operator can do a resume if desired. Alternatively, if the BRKSET flag is clear as checked in block 810, a resume is not allowed due to the branch to block 815. This means that the resume mode cannot be re-armed until after the speed control is disengaged. This method will detect and react to stuck resume switch conditions, even those due to an oscillating resume switch signal. These steps are expanded explanations of what occurs in blocks 130, 131 and 503. Next, the speed control cut-out conditions are polled in block 815.

Returning now to decision block 810, if the BRKSET flag is in the clear condition, the method branches directly from block 810 to block 815 to check the speed control cut-out conditions. The speed control cut-out conditions include conditions such as the vehicle brake being applied, the vehicle speed being too low, the park or neutral gear being engaged in vehicles equipped with automatic transmissions, the clutch being engaged for vehicles equipped with manual transmissions, the engine RPM being too high, or the ratio of the engine speed to the vehicle speed being out of range. This is also addressed in blocks 133, 134, 135, 504, 506, 508, 510 and 512.

If any of the cut-out conditions are out of range indicating that the speed control system should be disengaged, the method branches to block 816 to disengage the speed control (reference: block 120 and 540), before returning to the main electronic speed control routine in block 817.

If none of the speed control cut-out conditions are met as checked in block 815, the method falls through to block 818 to check the vac/vent ports; if not working, the method disengages the speed control in block 819 and jumps to a fault routine in block 820. This is also shown in reference to blocks 139 and 514. If the vac/vent ports are working from block 818, the switches are read (the condition of the set switch 70 and the resume switch 72). Reference: blocks 150 and following and blocks 530 and following.

Next, the routine in block 824 polls the condition of the set switch 70. If the set switch is on, the method branches to block 826 to set the appropriate flags and to check the timers as described elsewhere in this description; see blocks 532 and following.

Returning now to block 824, if the set switch 70 is off, the method falls through to block 830 to check to see if the electronic speed control has just been set; reference: block 548. If the electronic speed control has not just been set, the method branches to block 832 to poll the condition of the resume switch 72; reference: block 582. If the resume switch 72 is off, the method branches to block 834 to return to the main electronic speed control routine; reference blocks 203 and 600.

Returning now to block 832, if the resume switch 72 is on, the method falls through to block 836 to poll the condition of the resume switch flag. If the resume switch flag is set, the method branches, as previously described, to block 834 to return to the main routine. If the resume switch flag is clear as checked in block 836 (reference: block 584), the method falls through to set the resume switch flag in block 837 and then to block 838 to enter the resume mode of the electronic speed control routine (reference: blocks 190 and 588).

Returning now to decision block 830, if the electronic speed control has just recently been set, but the set switch 70 is off, the method will fall through to block 840 to determine whether the condition should be interpreted as a set or a tap. (See blocks 550, 552, 554.) If the routine interprets the condition as a tap, this routine is followed via block 842 and the set speed is increased by two miles per hour (reference: blocks 170 and 554).

Returning now to block 840, if the set condition is found as checked in block 840, the method falls through to set the resume switch flag in block 843 and then to block 844 to perform a set function on the current speed the vehicle is travelling (reference: blocks 150 and 560).

Next, the method returns to the main electronic speed control routine in block 848 (reference: block 562).

The resume switch flag is set after a set or a resume condition in the normal speed control mode. The resume switch is not recognized when the resume switch flag is in the set condition.

While the present invention has been disclosed in connection with the preferred embodiment thereof, it should be understood that there may be other embodiments which fall within the spirit and scope of the subject invention and that the invention is susceptible to modification, variation and change without departing from the proper scope or the fair meaning of the following claims.