This disclosure is related to control systems for hybrid powertrain systems.
The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.
Known hybrid powertrain architectures can include multiple torque-generative devices, including internal combustion engines and non-combustion machines, e.g., electric machines, which transmit torque through a transmission device to an output member. One exemplary hybrid powertrain includes a two-mode, compound-split, electro-mechanical transmission which utilizes an input member for receiving tractive torque from a prime mover power source, preferably an internal combustion engine, and an output member. The output member can be operatively connected to a driveline for a motor vehicle for transmitting tractive torque thereto. Machines, operative as motors or generators, can generate torque inputs to the transmission independently of a torque input from the internal combustion engine. The machines may transform vehicle kinetic energy transmitted through the vehicle driveline to energy that is storable in an energy storage device. A control system is operative to monitor various inputs from the vehicle and the operator and provides operational control of the hybrid powertrain, including controlling transmission operating state and gear shifting, controlling the torque-generative devices, and regulating the power interchange among the energy storage device and the machines to manage outputs of the transmission, including torque and rotational speed. A control system can monitor input and control signals and execute algorithms to verify and secure operation of the powertrain.
A method to monitor integrity of a signal output from an operator-manipulable transmission range selector for a powertrain system includes equipping the transmission range selector with a range encoder and a direction encoder, determining a range state and a direction state based upon signals from the range encoder and the direction encoder, determining a discrete position of the transmission range selector based upon the range state and the direction state, and performing back rationality to verify the discrete position of the transmission range selector.
One or more embodiments will now be described, by way of example, with reference to the accompanying drawings, in which:
Referring now to the drawings, wherein the showings are for the purpose of illustrating certain exemplary embodiments only and not for the purpose of limiting the same,
The exemplary engine 14 comprises a multi-cylinder internal combustion engine selectively operative in several states to transfer torque to the transmission 10 via an input member 12, and can be either a spark-ignition or a compression-ignition engine. The engine 14 includes a crankshaft (not shown) operatively coupled to the input member 12 of the transmission 10. A rotational speed sensor 11 monitors rotational speed of the input member 12. Power output from the engine 14, comprising rotational speed and engine torque, can differ from the input speed NI and the input torque TI to the transmission 10 due to placement of torque-consuming components on the input member 12 between the engine 14 and the transmission 10, e.g., a hydraulic pump (not shown) and/or a torque management device (not shown).
The exemplary transmission 10 comprises three planetary-gear sets 24, 26 and 28, and four selectively engageable torque-transferring devices, i.e., clutches C170, C262, C373, and C475. As used herein, clutches refer to any type of friction torque transfer device including single or compound plate clutches or packs, band clutches, and brakes, for example. A hydraulic control circuit (‘HYD’) 42, preferably controlled by a transmission control module (hereafter ‘TCM’) 17, is operative to control and monitor clutch states. Clutches C262 and C475 preferably comprise hydraulically-applied rotating friction clutches. Clutches C170 and C373 preferably comprise hydraulically-controlled stationary devices that can be selectively grounded to a transmission case 68. Each of the clutches C170, C262, C373, and C475 is preferably hydraulically applied, selectively receiving pressurized hydraulic fluid via the hydraulic control circuit 42.
The first and second electric machines 56 and 72 preferably comprise three-phase AC machines, each including a stator (not shown) and a rotor (not shown), and respective resolvers 80 and 82. The motor stator for each machine is grounded to an outer portion of the transmission case 68, and includes a stator core with coiled electrical windings extending therefrom. The rotor for the first electric machine 56 is supported on a hub plate gear that is operatively attached to shaft 60 via the second planetary gear set 26. The rotor for the second electric machine 72 is fixedly attached to a sleeve shaft hub 66.
Each of the resolvers 80 and 82 preferably comprises a variable reluctance device including a resolver stator (not shown) and a resolver rotor (not shown). The resolvers 80 and 82 are appropriately positioned and assembled on respective ones of the first and second electric machines 56 and 72. Stators of respective ones of the resolvers 80 and 82 are operatively connected to one of the stators for the first and second electric machines 56 and 72. The resolver rotors are operatively connected to the rotor for the corresponding first and second electric machines 56 and 72. Each of the resolvers 80 and 82 is signally and operatively connected to a transmission power inverter control module (hereafter ‘TPIM’) 19, and each senses and monitors rotational position of the resolver rotor relative to the resolver stator, thus monitoring rotational position of respective ones of first and second electric machines 56 and 72. Additionally, the signals output from the resolvers 80 and 82 are interpreted to provide the rotational speeds for first and second electric machines 56 and 72, i.e., NA and NB, respectively.
The transmission 10 includes an output member 64, e.g. a shaft, which is operably connected to a driveline 90 for a vehicle (not shown), to provide output power to the driveline 90 that is transferred to vehicle wheels 93, one of which is shown in
The input torque from the engine 14 and the motor torques from the first and second electric machines 56 and 72 (TI, TA, and TB respectively) are generated as a result of energy conversion from fuel or electrical potential stored in an electrical energy storage device (hereafter ‘ESD’) 74. The ESD 74 is high voltage DC-coupled to the TPIM 19 via DC transfer conductors 27. The transfer conductors 27 include a contactor switch 38. When the contactor switch 38 is closed, under normal operation, electric current can flow between the ESD 74 and the TPIM 19. When the contactor switch 38 is opened electric current flow between the ESD 74 and the TPIM 19 is interrupted. The TPIM 19 transmits electrical power to and from the first electric machine 56 through a first motor control module (‘MCP-A’) 33 using transfer conductors 29, and the TPIM 19 similarly transmits electrical power to and from the second electric machine 72 through a second motor control module (‘MCP-B’) 34 using transfer conductors 31 to meet the torque commands for the first and second electric machines 56 and 72 in response to the motor torques TA and TB. Electrical current is transmitted to and from the ESD 74 in accordance with whether the ESD 74 is being charged or discharged.
The TPIM 19 preferably includes a hybrid control module (hereafter ‘HCP’) 5 and the pair of power inverters and respective motor control modules 33 and 34 configured to receive the torque commands and control inverter states therefrom for providing motor drive or regeneration functionality to meet the commanded motor torques TA and TB. The power inverters comprise known complementary three-phase power electronics devices, and each includes a plurality of insulated gate bipolar transistors (not shown) for converting DC power from the ESD 74 to AC power for powering respective ones of the first and second electric machines 56 and 72, by switching at high frequencies. The insulated gate bipolar transistors form a switch mode power supply configured to receive control commands. There is typically one pair of insulated gate bipolar transistors for each phase of each of the three-phase electric machines. States of the insulated gate bipolar transistors are controlled to provide motor drive mechanical power generation or electric power regeneration functionality. The three-phase inverters receive or supply DC electric power via DC transfer conductors 27 and transform it to or from three-phase AC power, which is conducted to or from the first and second electric machines 56 and 72 for operation as motors or generators via transfer conductors 29 and 31 respectively.
The aforementioned control modules communicate with other control modules, sensors, and actuators via a communications link comprising a local area network (hereafter ‘LAN’) bus 6, in this embodiment. The LAN bus 6 allows for structured communication between the various control modules. The specific communication protocol utilized is application-specific. The LAN bus 6 and appropriate protocols provide for robust messaging and multi-control module interfacing between the aforementioned control modules, and other control modules providing functionality including e.g., antilock braking, traction control, and vehicle stability. Multiple communications buses may be used to improve communications speed and provide some level of signal redundancy and integrity. Communications between the MCP-A 33 and the HCP 5 and between the MCP-B 34 and the HCP 5 is preferably effected using direct links preferably comprising serial peripheral interface (hereafter ‘SPI’) buses 37. Communication between individual control modules can also be effected using a wireless link, e.g., a short range wireless radio communications bus (not shown).
The HCP 5 provides supervisory control of the hybrid powertrain, serving to coordinate operation of the ECM 23, TCM 17, MCP-A 33, MCP-B 34, and BPCM 21. Based upon various command signals from the user interface 13 and the hybrid powertrain, including the ESD 74, the HCP 5 determines an operator torque request, an output torque command, an engine input torque command, clutch torque(s) for the applied torque-transfer clutches C170, C262, C373, C475 of the transmission 10, and the motor torques TA and TB for the first and second electric machines 56 and 72. The HCP 5 sends commands to specific control modules to effect control of the engine 14, transmission 10 and the first and second electric machines 56 and 72.
The ECM 23 is operatively connected to the engine 14, and functions to acquire data from sensors and control actuators of the engine 14 over a plurality of discrete lines, shown for simplicity as an aggregate bi-directional interface cable 35. The ECM 23 receives the engine input torque command from the HCP 5. The ECM 23 determines the actual engine input torque, TI, provided to the transmission 10 at that point in time based upon monitored engine speed and load, which is communicated to the HCP 5. The ECM 23 monitors input from the rotational speed sensor 11 to determine the engine input speed to the input member 12, which translates to the transmission input speed, NI. The ECM 23 monitors inputs from sensors (not shown) to determine states of other engine operating parameters including, e.g., a manifold pressure, engine coolant temperature, ambient air temperature, and ambient pressure. The engine load can be determined, for example, from the manifold pressure, or alternatively, from monitoring operator input to the accelerator pedal 113. The ECM 23 generates and communicates control signals to control engine actuators, including, e.g., fuel injectors, ignition modules, and throttle control modules, none of which are shown.
The TCM 17 is operatively connected to the transmission 10 and monitors inputs from sensors (not shown) to determine states of transmission operating parameters. The TCM 17 generates and communicates actuator control signals to control the transmission 10, including controlling the hydraulic control circuit 42. Inputs from the TCM 17 to the HCP 5 include estimated clutch torques for each of the clutches, i.e., C170, C262, C373, and C475, and rotational output speed, NO, of the output member 64. Other actuators and sensors may be used to provide additional information from the TCM 17 to the HCP 5 for control purposes. The TCM 17 monitors inputs from pressure switches (not shown) and selectively actuates pressure control solenoids (not shown) and shift solenoids (not shown) of the hydraulic circuit 42 to selectively actuate the various clutches C170, C262, C373, and C475 to achieve various transmission operating range states, as described hereinbelow.
The BPCM 21 is signally connected to sensors (not shown) to monitor the ESD 74, including states of electrical current and voltage parameters, to provide information indicative of parametric states of the batteries of the ESD 74 to the HCP 5. The parametric states of the batteries preferably include battery state-of-charge, battery voltage, battery temperature, and available battery power, referred to as a range PBAT
A brake control module (hereafter ‘BrCM’) 22 is operatively connected to friction brakes (not shown) on each of the vehicle wheels 93. The BrCM 22 monitors the operator input to the brake pedal 112 and generates control signals to control the friction brakes and sends a control signal to the HCP 5 to operate the first and second electric machines 56 and 72 based thereon.
Each of the control modules ECM 23, TCM 17, HCP-5, MCP-A 33, MCP-B 34, BPCM 21, and BrCM 22 is preferably a general-purpose digital computer comprising a microprocessor or central processing unit, storage mediums comprising read only memory (‘ROM’), random access memory (‘RAM’), electrically programmable read only memory (‘EPROM’), a high speed clock, analog to digital (‘A/D’) and digital to analog (‘D/A’) circuitry, and input/output circuitry and devices (‘I/O’) and appropriate signal conditioning and buffer circuitry. Each of the control modules has a set of control algorithms, comprising resident program instructions and calibrations stored in one of the storage mediums and executed to provide the respective functions of each computer. Information transfer between the control modules is preferably accomplished using the LAN bus 6 and SPI buses 37. The control algorithms are executed during preset loop cycles such that each algorithm is executed at least once each loop cycle. Algorithms stored in the non-volatile memory devices are executed by one of the central processing units to monitor inputs from the sensing devices and execute control and diagnostic routines to control operation of the actuators, using preset calibrations. Loop cycles are executed at regular intervals, for example each 3.125, 6.25, 12.5, 25 and 100 milliseconds during ongoing operation of the hybrid powertrain. Alternatively, algorithms may be executed in response to the occurrence of an event.
The exemplary hybrid powertrain selectively operates in one of several states that can be described in terms of engine states comprising one of an engine-on state (‘ON’) and an engine-off state (‘OFF’), and transmission operating range states comprising a plurality of fixed gears and continuously variable operating modes, described with reference to Table 1, below.
Each of the transmission operating range states is described in the table and indicates which of the specific clutches C170, C262, C373, and C475 are applied for each of the operating range states. A first continuously variable mode, i.e., EVT Mode 1, or M1, is selected by applying clutch C170 only in order to “ground” the outer gear member of the third planetary gear set 28. The engine state can be one of ON (‘M1_Eng_On’) or OFF (‘M1_Eng_Off’). A second continuously variable mode, i.e., EVT Mode 2, or M2, is selected by applying clutch C262 only to connect the shaft 60 to the carrier of the third planetary gear set 28. The engine state can be one of ON (‘M2_Eng_On’) or OFF (‘M2_Eng_Off’). For purposes of this description, when the engine state is OFF, the engine input speed is equal to zero revolutions per minute (‘RPM’), i.e., the engine crankshaft is not rotating. A fixed gear operation provides a fixed ratio operation of input-to-output speed of the transmission 10, i.e., NI/NO. A first fixed gear operation (‘G1’) is selected by applying clutches C170 and C475. A second fixed gear operation (‘G2’) is selected by applying clutches C170 and C262. A third fixed gear operation (‘G3’) is selected by applying clutches C262 and C475. A fourth fixed gear operation (‘G4’) is selected by applying clutches C262 and C373. The fixed ratio operation of input-to-output speed increases with increased fixed gear operation due to decreased gear ratios in the planetary gears 24, 26, and 28. The rotational speeds of the first and second electric machines 56 and 72, NA and NB respectively, are dependent on internal rotation of the mechanism as defined by the clutching and are proportional to the input speed measured at the input member 12. When the transmission 10 is controlled in EVT Mode 1, the transmission 10 can be commanded to operate in the reverse direction, which is accomplished by operating the second electric machine 72 in the reverse rotational direction through its motor control module in TPIM 19.
In response to operator input via the accelerator pedal 113, the brake pedal 112, and the transmission range selector 114, as captured by the user interface 13, the HCP 5 and one or more of the other control modules determine torque commands to control torque actuators to meet the operator torque request at the output member 64 for transference to the driveline 90. The torque actuators preferably include a plurality of torque generative devices, e.g., the engine 14 and the first and second electric machines 56 and 72 and a torque transferring device comprising the transmission 10 in this embodiment. Based upon operator commands from the user interface 13, the HCP 5 determines the operator torque request and an output torque command from the transmission 10 to the driveline 90 and actuator controls including an input torque from the engine 14, clutch torques for the torque-transfer clutches C170, C262, C373, C475 of the transmission 10 and the motor torque commands for the first and second electric machines 56 and 72 based upon operator commands from the user interface 13.
Torque security of the hybrid powertrain system can be achieved by executing integrity tests of the control system which include monitoring hardware integrity, monitoring integrity of algorithms and memory devices, securing and monitoring integrity of critical signals during communications within a control module and communications between the control modules, monitoring processor integrity and executing remedial actions. Torque security in presence of an observed fault can include limiting a torque actuator command signal. This can include maximum and minimum limits on torque actuator command signals and maximum rates of change on torque actuator command signals. Specifically, motor torque commands TA and TB can be limited to maximum and minimum motor torques, and changes in the motor torque commands TA and TB can be limited to effect a maximum rate of change in output torque, e.g., 0.2 g.
Securing and monitoring signal integrity is preferably accomplished by individually securing the control modules and securing the serial communications links between the control modules. The distributed control module system of the embodiment preferably includes each of the torque actuators controlled by a separate control module. This embodiment includes the ECM 23 that monitors sensors and control actuators of the engine 14, the TCM 17 that monitors sensors and control actuators of the transmission 10, the MCP-A 33 that monitors sensors and control actuators of the first electric machine 56, and the MCP-B 34 that monitors sensors and control actuators of the second electric machine 72. The HCP 5 monitors inputs from and commands operation of the ECM 23, TCM 17, MCP-A 33 and MCP-B 34. The control modules communicate the signals using the LAN bus 6 and the SPI bus 37. Each of the ECM 23, MCP-A 33, MCP-B 34 and TCM 17, is responsible for closed loop monitoring and self-security based on secured commands received from the HCP 5.
Securing and monitoring integrity of the signal includes monitoring processor integrity for each of the control modules. The processor integrity can be determined using diagnostics software that monitors data internal to the control module, and rationalizing it in one of the loop cycles. When an inconsistency between monitored data and rationalized data is detected, the inconsistency is recorded as a mismatch or a fault in a fault maturation algorithm, e.g., an X of Y routine wherein a matured fault is detected when X faults are observed out of immediately preceding Y observations of the signal. An example is detecting a matured fault when more than half the immediately preceding observations are mismatches occurring between the monitored data and the rationalized data. When the fault maturation algorithm achieves a threshold number of mismatching observations in the immediately preceding observations, the fault has matured, indicating signal corruption and a requirement for remedial action. The remedial action can be actuator-specific or across the entire control system, and places the powertrain in a torque-safe state. The remedial action will also include storing an OBD compliant code for subsequent retrieval. A diagnostic may preliminarily identify a fault pending, meaning an inconsistency has been detected but the fault maturation algorithm has not reached its threshold. The hardware integrity can be further determined using diagnostics software that monitors the sensors and actuators of the control system.
Monitoring integrity of a signal that is generated and communicated in the control system comprises actions to determine whether a received signal matches the generated signal. A signal can include an operator command signal, a sensor input signal and an actuator command and control signal. With reference to the embodiment described hereinabove, a signal can comprise an actuator command or control signal, including, e.g., motor torque commands for the first and second electric machines 56 and 72, the input torque command to the engine 14, and clutch torque commands for the clutches C170, C262, C373, and C475 of the transmission 10. The signal can include the sensor input signal, e.g., a signal from the rotational speed sensor 11 and the transmission output speed sensor 84 and resolvers 80 and 82. The signal can include an operator command, e.g., an operator input to the accelerator pedal 113, the operator brake pedal 112 and the transmission range selector 114.
Preferably, the second sensor 116 comprises a digital encoder that provides a unique set of discrete outputs for each of a plurality of valid subsets of the discrete positions, with each subset comprising a rotational direction of the output member 64 of the transmission 10 corresponding to an operator-selected direction of intended vehicle propulsion. In this embodiment the second sensor 116 generates four subsets, comprising four unique outputs corresponding to one of the Park, Reverse, Neutral, and Drive positions. The second sensor 116 is referred to as a direction encoder 116. Thus, in the embodiment shown, the transmission range selector 114 has discrete positions comprising P, R, N, DM . . . D1, and the direction encoder 116 generates outputs of DE Output 1, DE Output 2, DE Output 3, DE Output 4, and DE Output 5, wherein discrete position P has corresponding output DE Output 1, discrete position R has corresponding output DE Output 2, discrete position N has corresponding output DE Output 3, discrete position DM . . . D1 have corresponding output DE Output 4, and unknown discrete positions have corresponding output DE Output 5. In this embodiment, the output of the direction encoder 116 is a five-bit digital word. The direction encoder 116 is signally connected to the HCP 5 through a hardware input/output device (not shown). The HCP 5 decodes the five-bit digital word and generates a transmission shift lever direction state (hereafter ‘TDS’). The TDS preferably comprises a digital word, e.g., a four-bit or an eight-bit representation of the direction state, i.e., one of Park, Reverse, Neutral, and Drive, and Unknown direction state when the TDS is unable to determine a direction state.
The TDS and the output of the direction encoder 116 are input to a transmission direction state rationality algorithm (‘TDS Rationality Check’) 410, which verifies that the TDS output from the HCP 5 corresponds to the transmission direction indicated by the direction encoder 116 prior to being processed through the HCP 5. The signal output from the direction encoder 116 is compared to the expected direction encoder states for each of the direction states, i.e., Park, Reverse, Neutral, Drive, and Unknown, to determine that there is a complete correspondence to one and only one of the direction states. A fault can be set when there is not a positive correspondence. The rationality algorithm 410 compares the TDS with the signal output from the direction encoder 116 to verify that the TDS corresponds to the signal output from the direction encoder 116. Preferably there is a positive match between the two signals, i.e., the TDS corresponds directly to the signal output from the direction encoder 116. In this instance, no fault is indicated by the output of the rationality algorithm 410. When there is not a positive match between the two signals, the TDS is compared to the expected direction encoder states for each of the direction states, i.e., Park, Reverse, Neutral, and Drive. When the signal output from the direction encoder 116 is within one bit of one and only one of the direction states, the rationality algorithm 410 verifies that TDS matches that direction state. A fault is indicated by the output of the rationality algorithm 410 when there is not a match. When the signal output from the direction encoder 116 is not within one bit of one of the direction states (e.g. two or more bits are incorrect), the rationality algorithm 410 verifies that the TDS indicates the direction as Unknown. Otherwise the rationality check 410 can indicate a fault.
The TDS and the TSLP are input to a range validation logic algorithm (‘TDS Validation Logic’) 425, which compares the TDS and TSLP states to validate that there is logical consistency therebetween. When the range is validated, i.e., there is a match between a positive TDS and a positive TSLP, an output is a validated transmission range state (hereafter ‘VTRS’), which is validated using a dual-store check (430) and subsequently checked for a fault prior to use by the HCP 5. When the range is not validated, vehicle propulsion can be disabled, preferably by placing the vehicle in Neutral state. When the TDS has been error-corrected, and there is a match between the error-corrected TDS and the positive TSLP, the TSLP is valid and used as the VTRS. When there is an active fault with the direction encoder 116, or the direction encoder 116 generates an illegal value, the VTRS is commanded to a restricted range, e.g., disabling one or more of the low range Drive gears. When the TDS is positive and the TSLP indicates the range encoder 118 is between ranges or has an active fault, or the TCM 17 is off-line, the VTRS is commanded based upon the direction encoder 116 and operated at a restricted range, e.g., disabling one or more of the low range Drive gears, and used as the VTRS. The VTRS comprises a signal output corresponding to one of the discrete positions of the transmission range selector 114, including Park, Reverse, Neutral, DriveM . . . Drive1 as shown. The VTRS comprises Park, Reverse, Neutral, Drive6, Drive5, Drive4, Drive3, Drive2, and Drive1 in one embodiment. Additional discrete positions of the transmission range selector 114 can be used in other embodiments, and can be achieved during ongoing operation of the vehicle using operator-selectable features referred to as tap up/tap down controls (not shown).
The VTRS output is input to a back rationality check algorithm (‘VTRS Back Rationality Check’) 420. The back rationality check algorithm 420 monitors the TDS and the TSLP, and compares the VTRS thereto, including executing multiple checks to compare the VTRS to non-selected TDS outputs from HCP 5. The back rationality checks can be specific to each of Park, Reverse, Neutral, Drive6, Drive5, Drive4, Drive3, Drive2, and Drive1.
When the VTRS output indicates the transmission range selector 114 indicates Park, the algorithm 420 executes a first logic check that verifies that Park is indicated based upon the TSLP. This includes verifying the TSLP indicates Park and verifying the TDS does not indicate any one of Reverse, Neutral or Drive. The algorithm 420 executes a second logic check that verifies that Park is indicated based upon the TDS. This includes verifying the TDS indicates Park and verifying absence of system faults. A fault is indicated when there is a fault in any of the verifications.
When the VTRS output indicates the transmission range selector 114 indicates Reverse, the algorithm 420 executes a first logic check that verifies that Reverse is indicated based upon the TSLP. This includes verifying the TSLP indicates Reverse and verifying the TDS does not indicate any one of Park, Neutral or Drive. The algorithm 420 executes a second logic check that verifies that Reverse is indicated based upon the TDS. This includes verifying the TDS indicates Reverse and verifying absence of system faults. A fault is indicated when there is a fault in any of the verifications.
When the VTRS output indicates the transmission range selector 114 indicates Neutral, the algorithm 420 executes a first logic check that verifies that Neutral is indicated based upon the TSLP and the TDS. This includes verifying the TSLP indicates Neutral and verifying the TDS indicates Neutral. The algorithm 420 executes a second logic check that compares the TSLP and the TDS for logical inconsistencies. The algorithm 420 executes a third logic check to determine whether the VTRS commands Neutral, including whether Neutral has been commanded due to an active fault in one of the range encoder 118 and the direction encoder 116. A fault is indicated when there is a fault in any of the verifications.
When the VTRS output indicates the transmission range selector 114 indicates one of the Drive ranges, indicated by DriveX wherein X indicates the specific Drive range, e.g., one of Drive6, Drive5, Drive4, Drive3, Drive2, and Drive1 in this embodiment. The algorithm 420 executes a first logic check that verifies that the DriveX range is indicated based upon the TSLP. This includes verifying the TSLP indicates the Drive range and verifying the TDS does not indicate any one of Park, Reverse, or Neutral. The algorithm 420 executes a second logic check that verifies that the specific drive range DriveX is indicated based upon the TDS. This includes verifying the TDS indicates DriveX and verifying absence of system faults. A fault is indicated when there is a fault in any of the verifications.
When a fault occurs in any one of the transmission direction state rationality algorithm 410, the back rationality check algorithm 420, the range validation logic algorithm 425, or the one of dual store functions 415, 430, the control system executes remedial action (440) to mitigate risks associated with the presence of the fault. The remedial action places the powertrain in a torque-safe state. The remedial action further includes storing an OBD compliant code for subsequent retrieval. A diagnostic may preliminarily identify a fault pending, meaning data corruption or an inconsistency has been detected but the fault maturation algorithm has not reached its threshold. One specific remedial action can include operating the system in one specific operating range.
The TDS and VTRS are subjected to dual store functions 415, 430.
When the rationality check 510 indicates corruption of one or both of the primary and the redundant signals, or the dual store function 511 indicates corruption of the present contents of one the first and second memory locations 512, 512′ the control system identifies occurrence of the fault (‘Fault’). The control system determines whether the corrupted signal has matured (‘Mature Fault’) (514), and executes remedial action (516) to mitigate risks associated with the presence of the fault. A fault maturation algorithm can be executed, including, e.g., an X of Y routine wherein a fault has matured when X mismatched signals are observed out of immediately preceding Y signal observations. An example includes determining a fault has matured when more than half the immediately preceding observations indicate a corrupted signal.
Monitoring integrity of a signal transmitted over a serial bus includes detecting missing data, e.g., detecting loss of a message frame and taking a short term mitigation action and informing the receiving control module that no new data is available. Detecting missing data also includes detecting long term loss of communications to one of the control modules and taking a remedial action.
It is understood that modifications are allowable within the scope of the disclosure. The disclosure has been described with specific reference to the preferred embodiments and modifications thereto. Further modifications and alterations may occur to others upon reading and understanding the specification. It is intended to include all such modifications and alterations insofar as they come within the scope of the disclosure.
This application claims the benefit of U.S. Provisional Application No. 60/983,241, filed on Oct. 29, 2007 which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
6105448 | Borschert et al. | Aug 2000 | A |
6832148 | Bennett | Dec 2004 | B1 |
6868318 | Cawthorne | Mar 2005 | B1 |
7154236 | Heap | Dec 2006 | B1 |
7176643 | Yamada et al. | Feb 2007 | B2 |
20040072646 | Hori et al. | Apr 2004 | A1 |
20050076958 | Foster | Apr 2005 | A1 |
20050077867 | Cawthorne | Apr 2005 | A1 |
20050077877 | Cawthorne | Apr 2005 | A1 |
20050080523 | Bennett | Apr 2005 | A1 |
20050080527 | Tao | Apr 2005 | A1 |
20050080535 | Steinmetz | Apr 2005 | A1 |
20050080537 | Cawthorne | Apr 2005 | A1 |
20050080538 | Hubbard | Apr 2005 | A1 |
20050080539 | Hubbard | Apr 2005 | A1 |
20050080540 | Steinmetz | Apr 2005 | A1 |
20050080541 | Sah | Apr 2005 | A1 |
20050182526 | Hubbard | Aug 2005 | A1 |
20050182543 | Sah | Aug 2005 | A1 |
20050182546 | Hsieh | Aug 2005 | A1 |
20050182547 | Sah | Aug 2005 | A1 |
20050189918 | Weisgerber | Sep 2005 | A1 |
20050252283 | Heap | Nov 2005 | A1 |
20050252305 | Hubbard | Nov 2005 | A1 |
20050252474 | Sah | Nov 2005 | A1 |
20050255963 | Hsieh | Nov 2005 | A1 |
20050255964 | Heap | Nov 2005 | A1 |
20050255965 | Tao | Nov 2005 | A1 |
20050255966 | Tao | Nov 2005 | A1 |
20050255967 | Foster | Nov 2005 | A1 |
20050255968 | Sah | Nov 2005 | A1 |
20050256617 | Cawthorne | Nov 2005 | A1 |
20050256618 | Hsieh | Nov 2005 | A1 |
20050256623 | Hubbard | Nov 2005 | A1 |
20050256625 | Sah | Nov 2005 | A1 |
20050256626 | Hsieh | Nov 2005 | A1 |
20050256627 | Sah | Nov 2005 | A1 |
20050256629 | Tao | Nov 2005 | A1 |
20050256631 | Cawthorne | Nov 2005 | A1 |
20050256633 | Heap | Nov 2005 | A1 |
20050256919 | Cawthorne | Nov 2005 | A1 |
20060103339 | Yamada et al. | May 2006 | A1 |
20060194670 | Heap | Aug 2006 | A1 |
20070078580 | Cawthorne | Apr 2007 | A1 |
20070087896 | Matsuzaki et al. | Apr 2007 | A1 |
20070093953 | Heap | Apr 2007 | A1 |
20070149348 | Holmes | Jun 2007 | A1 |
20070191181 | Burns | Aug 2007 | A1 |
20070225886 | Morris | Sep 2007 | A1 |
20070225887 | Morris | Sep 2007 | A1 |
20070225888 | Morris | Sep 2007 | A1 |
20070225889 | Morris | Sep 2007 | A1 |
20070260381 | Sah | Nov 2007 | A1 |
20070276569 | Sah | Nov 2007 | A1 |
20070284162 | Zettel | Dec 2007 | A1 |
20070284163 | Heap | Dec 2007 | A1 |
20070284176 | Sah | Dec 2007 | A1 |
20070285059 | Zettel | Dec 2007 | A1 |
20070285060 | Zettel | Dec 2007 | A1 |
20070285061 | Zettel | Dec 2007 | A1 |
20070285063 | Zettel | Dec 2007 | A1 |
20070285097 | Zettel | Dec 2007 | A1 |
20080004779 | Sah | Jan 2008 | A1 |
20080028879 | Robinette | Feb 2008 | A1 |
20080032855 | Sah | Feb 2008 | A1 |
20080064559 | Cawthorne | Mar 2008 | A1 |
20080064562 | Zettel | Mar 2008 | A1 |
20080103003 | Sah | May 2008 | A1 |
20080119320 | Wu | May 2008 | A1 |
20080119321 | Heap | May 2008 | A1 |
20080120000 | Heap | May 2008 | A1 |
20080120001 | Heap | May 2008 | A1 |
20080120002 | Heap | May 2008 | A1 |
20080176706 | Wu | Jul 2008 | A1 |
20080176709 | Wu | Jul 2008 | A1 |
20080181280 | Wang | Jul 2008 | A1 |
20080182696 | Sah | Jul 2008 | A1 |
20080183372 | Snyder | Jul 2008 | A1 |
20080234097 | Sah | Sep 2008 | A1 |
20080236921 | Huseman | Oct 2008 | A1 |
20080243346 | Huseman | Oct 2008 | A1 |
20080249745 | Heap | Oct 2008 | A1 |
20080262694 | Heap | Oct 2008 | A1 |
20080262698 | Lahti | Oct 2008 | A1 |
20080272717 | Gleason | Nov 2008 | A1 |
20080275611 | Snyder | Nov 2008 | A1 |
20080275624 | Snyder | Nov 2008 | A1 |
20080275625 | Snyder | Nov 2008 | A1 |
20080287255 | Snyder | Nov 2008 | A1 |
20090069148 | Heap | Mar 2009 | A1 |
20090069989 | Heap | Mar 2009 | A1 |
20090070019 | Heap | Mar 2009 | A1 |
20090082170 | Heap | Mar 2009 | A1 |
20090088294 | West | Apr 2009 | A1 |
20090105039 | Sah | Apr 2009 | A1 |
20090105896 | Tamai | Apr 2009 | A1 |
20090105898 | Wu | Apr 2009 | A1 |
20090105914 | Buur | Apr 2009 | A1 |
20090107745 | Buur | Apr 2009 | A1 |
20090107755 | Kothari | Apr 2009 | A1 |
20090108673 | Wang | Apr 2009 | A1 |
20090111637 | Day | Apr 2009 | A1 |
20090111640 | Buur | Apr 2009 | A1 |
20090111642 | Sah | Apr 2009 | A1 |
20090111643 | Sah | Apr 2009 | A1 |
20090111644 | Kaminsky | Apr 2009 | A1 |
20090111645 | Heap | Apr 2009 | A1 |
20090112385 | Heap | Apr 2009 | A1 |
20090112392 | Buur | Apr 2009 | A1 |
20090112399 | Buur | Apr 2009 | A1 |
20090112412 | Cawthorne | Apr 2009 | A1 |
20090112416 | Heap | Apr 2009 | A1 |
20090112417 | Kaminsky | Apr 2009 | A1 |
20090112418 | Buur | Apr 2009 | A1 |
20090112419 | Heap | Apr 2009 | A1 |
20090112421 | Sah | Apr 2009 | A1 |
20090112422 | Sah | Apr 2009 | A1 |
20090112423 | Foster | Apr 2009 | A1 |
20090112427 | Heap | Apr 2009 | A1 |
20090112428 | Sah | Apr 2009 | A1 |
20090112429 | Sah | Apr 2009 | A1 |
20090112495 | Center | Apr 2009 | A1 |
20090115349 | Heap | May 2009 | A1 |
20090115350 | Heap | May 2009 | A1 |
20090115351 | Heap | May 2009 | A1 |
20090115352 | Heap | May 2009 | A1 |
20090115353 | Heap | May 2009 | A1 |
20090115354 | Heap | May 2009 | A1 |
20090115365 | Heap | May 2009 | A1 |
20090115373 | Kokotovich | May 2009 | A1 |
20090115377 | Schwenke | May 2009 | A1 |
20090115408 | West | May 2009 | A1 |
20090115491 | Anwar | May 2009 | A1 |
20090118074 | Zettel | May 2009 | A1 |
20090118075 | Heap | May 2009 | A1 |
20090118076 | Heap | May 2009 | A1 |
20090118077 | Hsieh | May 2009 | A1 |
20090118078 | Wilmanowicz | May 2009 | A1 |
20090118079 | Heap | May 2009 | A1 |
20090118080 | Heap | May 2009 | A1 |
20090118081 | Heap | May 2009 | A1 |
20090118082 | Heap | May 2009 | A1 |
20090118083 | Kaminsky | May 2009 | A1 |
20090118084 | Heap | May 2009 | A1 |
20090118085 | Heap | May 2009 | A1 |
20090118086 | Heap | May 2009 | A1 |
20090118087 | Hsieh | May 2009 | A1 |
20090118089 | Heap | May 2009 | A1 |
20090118090 | Heap | May 2009 | A1 |
20090118091 | Lahti | May 2009 | A1 |
20090118093 | Heap | May 2009 | A1 |
20090118094 | Hsieh | May 2009 | A1 |
20090118877 | Center | May 2009 | A1 |
20090118879 | Heap | May 2009 | A1 |
20090118880 | Heap | May 2009 | A1 |
20090118882 | Heap | May 2009 | A1 |
20090118883 | Heap | May 2009 | A1 |
20090118884 | Heap | May 2009 | A1 |
20090118885 | Heap | May 2009 | A1 |
20090118886 | Tamai | May 2009 | A1 |
20090118887 | Minarcin | May 2009 | A1 |
20090118888 | Minarcin | May 2009 | A1 |
20090118901 | Cawthorne | May 2009 | A1 |
20090118914 | Schwenke | May 2009 | A1 |
20090118915 | Heap | May 2009 | A1 |
20090118916 | Kothari | May 2009 | A1 |
20090118917 | Sah | May 2009 | A1 |
20090118918 | Heap | May 2009 | A1 |
20090118919 | Heap | May 2009 | A1 |
20090118920 | Heap | May 2009 | A1 |
20090118921 | Heap | May 2009 | A1 |
20090118922 | Heap | May 2009 | A1 |
20090118923 | Heap | May 2009 | A1 |
20090118924 | Heap | May 2009 | A1 |
20090118925 | Hsieh | May 2009 | A1 |
20090118926 | Heap | May 2009 | A1 |
20090118927 | Heap | May 2009 | A1 |
20090118928 | Heap | May 2009 | A1 |
20090118929 | Heap | May 2009 | A1 |
20090118930 | Heap | May 2009 | A1 |
20090118931 | Kaminsky | May 2009 | A1 |
20090118932 | Heap | May 2009 | A1 |
20090118933 | Heap | May 2009 | A1 |
20090118934 | Heap | May 2009 | A1 |
20090118935 | Heap | May 2009 | A1 |
20090118936 | Heap | May 2009 | A1 |
20090118937 | Heap | May 2009 | A1 |
20090118938 | Heap | May 2009 | A1 |
20090118939 | Heap | May 2009 | A1 |
20090118940 | Heap | May 2009 | A1 |
20090118941 | Heap | May 2009 | A1 |
20090118942 | Hsieh | May 2009 | A1 |
20090118943 | Heap | May 2009 | A1 |
20090118944 | Heap | May 2009 | A1 |
20090118945 | Heap | May 2009 | A1 |
20090118946 | Heap | May 2009 | A1 |
20090118947 | Heap | May 2009 | A1 |
20090118948 | Heap | May 2009 | A1 |
20090118949 | Heap | May 2009 | A1 |
20090118950 | Heap | May 2009 | A1 |
20090118951 | Heap | May 2009 | A1 |
20090118952 | Heap | May 2009 | A1 |
20090118954 | Wu | May 2009 | A1 |
20090118957 | Heap | May 2009 | A1 |
20090118962 | Heap | May 2009 | A1 |
20090118963 | Heap | May 2009 | A1 |
20090118964 | Snyder | May 2009 | A1 |
20090118969 | Heap | May 2009 | A1 |
20090118971 | Heap | May 2009 | A1 |
20090118999 | Heap | May 2009 | A1 |
20090144002 | Zettel | Jun 2009 | A1 |
Number | Date | Country |
---|---|---|
103 32 105 | Jan 2004 | DE |
Number | Date | Country | |
---|---|---|---|
20090112420 A1 | Apr 2009 | US |
Number | Date | Country | |
---|---|---|---|
60983241 | Oct 2007 | US |