The present disclosure relates generally to the field of internal combustion engine systems. More particularly, the present disclosure relates to engine accessory drive systems for internal combustion engines.
Automotive manufacturers have developed various technologies to improve fuel economy and reduce emissions in response to consumer demand and government regulations. For example, start-stop systems operate to automatically shut down and restart a vehicle's internal combustion engine to reduce the amount of time that the engine spends idling, thereby reducing fuel consumption and emissions. This is most advantageous for vehicles that spend significant amounts of time waiting at traffic lights or that frequently come to a stop while driving. Fuel economy gains from this technology are typically in the range of five to fifteen percent or more.
Vehicle start-stop systems provide various design challenges. For example, conventional starter motors are not designed for the number of operational cycles required for start-stop systems compared to conventional systems. For example, starter motors in conventional non-start-stop systems are designed to perform at least 50,000 starting cycles over a vehicle's lifetime. In contrast, starter motors in start-stop systems are designed to perform as many as 500,000-800,000 cycles over a vehicle's lifetime. Accordingly, many conventional starter motors are inadequate for the demands of start-stop systems.
In addition, vehicle accessories, such as an alternator, power steering pump, coolant pump, vacuum pump, air conditioning compressor, fan, etc., are typically driven by the crankshaft of the engine via an accessory drive (e.g., serpentine) belt. However, in start-stop systems, the accessories are not driven by the engine when the engine is shut down.
Various embodiments relate to engine accessory drive (EAD) systems for internal combustion engines. An example EAD system includes a motor-generator unit (MGU) operably coupled to an accessory. The EAD system also includes a gearbox assembly. The gearbox assembly includes a first gear train operably coupled to the MGU. The gearbox assembly also includes a second gear train operably coupled to an output of the engine, as well as a clutch selectively coupling the first gear train with a second gear train. A starter assembly includes a starter shaft operably coupled to the second gear train. The starter assembly also includes a starter pinion coupled to the starter shaft. The starter assembly further includes an actuator configured to selectively engage the starter pinion with a flywheel of the engine. An EAD controller is configured to selectively operate the EAD system in one of a generator mode, an accessory drive mode, and a starter mode.
Another example EAD system includes an MGU configured to selectively operate as an electric generator and an electric motor. The MGU is operably coupled to an energy storage system. A gearbox assembly is operably coupled to the MGU and to an output of the engine. An EAD controller is in operative communication with each of the MGU and the gearbox assembly. The EAD controller is structured to receive engine data indicative of an engine condition, and to receive state of charge data indicative of a state of charge of the energy storage system. The EAD system is also structured to interpret each of the engine data and the state of charge data, and to selectively operate the EAD system in one of a generator mode and an accessory drive mode.
Various other embodiments relate to a method, including providing an EAD controller that is operably coupled to each of an internal combustion engine and an EAD system. The EAD system includes an MGU configured to selectively operate as an electric generator and an electric motor. The EAD system also includes an energy storage system operably coupled to the MGU. The EAD system further includes a gearbox assembly operably coupled to the MGU and to an output of the engine. The method also includes receiving, by the EAD controller, engine data indicative of an engine condition, and state of charge data indicative of a state of charge of the energy storage system. The method further includes interpreting, by the EAD controller, each of the engine data and the state of charge data. The method further includes selectively operating, by the EAD controller, the EAD system in one of a generator mode and an accessory drive mode.
These and other features, together with the organization and manner of operation thereof, will become apparent from the following detailed description when taken in conjunction with the accompanying drawings, wherein like elements have like numerals throughout the several drawings described below.
A crankshaft pulley 116 is coupled to the crankshaft 106 on a front side 118 of the engine 102. A belt 120 is coupled to the crankshaft pulley 116 and to one or more accessories. For example, as illustrated in
The system 130 of
Starting the engine by the ISG 132 requires a significant amount of torque output from the ISG 132. Accordingly, the belt 120 of the system 130 of
The present disclosure is directed to an engine accessory drive (EAD) system for use with an internal combustion engine. The EAD system includes an electric motor-generator unit (MGU) configured to selectively operate as an electric motor and an electric generator. In an embodiment, the MGU includes a single input/output shaft operably coupled to each of an engine accessory and a gearbox assembly. The gearbox assembly may be operatively coupled to an engine output (e.g., crankshaft). The gearbox assembly includes multiple gear trains that may be selectively engaged depending on a selected operational mode. The gear trains may have different gear ratios. Unlike conventional gearboxes that typically have relatively close gear ratios (e.g., 1.5:1, 2:1, etc.), the gear trains of the gearbox assembly may have relatively wide gear ratios (e.g., 14.5:1 for a first gear trains and 3:1 for a second gear trains in one embodiment).
The EAD system is selectively operable in at least two operational modes, including a generator mode and an accessory drive mode. In some embodiments, the EAD system is also operable in a starter mode. In the generator mode, mechanical energy (e.g., torque) is transferred from the engine to the MGU through the gearbox assembly, and the MGU is configured to convert the mechanical energy to electrical energy, which may be stored in a battery system. In the accessory drive mode, the MGU is configured to convert electrical energy to mechanical energy to operate the engine accessories. In the starter mode, the MGU is configured to convert electrical energy to mechanical energy to operate a starter mechanism.
The EAD system of the present disclosure provides an integrated system that may replace several discrete components utilized in conventional engine systems. In particular, the MGU of the EAD system may function as each of an electrical generator, an electric accessory drive motor, and an electric starter motor. For example, the EAD system may be utilized in start-stop systems to automatically shut down and restart a vehicle's internal combustion engine to reduce the amount of time that the engine spends idling, thereby reducing fuel consumption and emissions. When the engine is shut down, the MGU may operate as an electric motor to operate engine accessories. In conventional start-stop systems, accessories are either non-operational when the engine is shut down, or the accessories are driven using one or more electric motors. The EAD system of the present disclosure provides an integrated system in which the MGU may operate accessories while the engine is shut down, may operate as a starter to start and restart the engine, and may also operate as a generator to charge the battery system. In addition, while the engine is in operation and the battery system has a sufficient state of charge, the MGU of the EAD system may power the accessories rather than the engine powering the accessories. Accordingly, the EAD system of the present disclosure results in reduced part count, weight, size, and cost, while also providing improved engine performance and reduced fuel consumption, compared to conventional systems.
The MGU 204 is also operatively coupled, via the input/output shaft 206 to a gearbox assembly 214. The gearbox assembly 214 may include one or more gear trains or gear sets. The gear trains may have one or more fixed or variable gear ratios. As illustrated in
The EAD system 200 also includes an EAD controller 228. The EAD controller 228 is structured to operatively communicate with the MGU 204 and as well as other various components. Communication between and among the components may be via any number of wired or wireless connections. For example, a wired connection may include a serial cable, a fiber optic cable, a CATS cable, or any other form of wired connection. In comparison, a wireless connection may include the Internet, Wi-Fi, cellular, radio, etc. In one embodiment, a controller area network (CAN) bus 229 provides the exchange of signals, information, and/or data. The CAN bus 229 includes any number of wired and wireless connections. For example, the EAD controller 228 may be structured to operatively communicate with at least one of an engine control unit (ECU) 230 and various sensors 232 (e.g., speed sensors, torque sensors, voltage and current sensors, etc.) via the CAN bus 229. The ECU 230 and the sensors 232 are configured to provide any of several different measurement values (e.g., speed, torque, state of charge, etc.). The EAD controller 228 is structured to interpret the measurement values and to control the EAD system 200 based on such interpretations.
The EAD controller 228 may be configured to operate the EAD system 200 in various operational modes, including a generator mode, an accessory drive mode, and a starter mode. In the generator mode, the clutch 224 is engaged such that mechanical energy (e.g., torque) is transferred from the engine output 222 to the MGU 204 through the gearbox assembly 214. In this operational mode, the MGU 204 is configured to convert the mechanical energy to electrical energy, which may be stored in an energy storage system 234 and used, for example, to operate an electrical system. In other words, the MGU 204 is configured to operate as an electrical generator (e.g., alternator) in the generator mode. The energy storage system 234 may include one or more batteries. In some embodiments, the energy storage system 234 may also include a battery control module. In the generator mode, the accessories 208 are driven using mechanical energy transferred from the engine output 222 to the accessories 208 through the gearbox assembly 214.
In the accessory drive mode, the clutch 224 is disengaged to decouple the engine output 222 from the MGU 204. The MGU 204 is configured to convert electrical energy (e.g., stored in the energy storage system 234) to mechanical energy to operate the engine accessories 208. In other words, the MGU 204 is configured to operate as an electric motor in the accessory drive mode. Mechanical energy (e.g., torque) is transferred from the MGU to the accessories 208 via the input/output shaft 206, as described above.
In the starter mode, the clutch 224 is disengaged to decouple the engine output 222 from the MGU 204. The MGU 204 is configured to convert electrical energy (e.g., stored in the energy storage system 234) to mechanical energy to operate the starter assembly 225. The starter assembly 225 includes a drive shaft operably coupled to the first gear train 216 at a first end and a sliding pinion gear at a second end. The sliding pinion gear may be engaged with the flywheel (not shown) of the engine 202 such that the mechanical energy from the MGU 204 is used to start the engine 202. Accordingly, the EAD system 200 eliminates the need for a conventional starter motor.
The memory 306 is shown to include various modules for completing the activities described herein. More particularly, the memory 306 includes modules structured to optimize control of the EAD system 200 of
Certain operations of the EAD controller 228 described herein include operations to interpret and/or to determine one or more parameters. Interpreting or determining, as utilized herein, includes receiving values by any method known in the art, including at least receiving values from a datalink or network communication, receiving an electronic signal (e.g. a voltage, frequency, current, or PWM signal) indicative of the value, receiving a computer generated parameter indicative of the value, reading the value from a memory location on a non-transient computer readable storage medium, receiving the value as a run-time parameter by any means known in the art, and/or by receiving a value by which the interpreted parameter can be calculated, and/or by referencing a default value that is interpreted to be the parameter value.
As illustrated in
The operational mode module 310 is configured to control operation of the EAD system 200 based on the interpreted measurement values 312. For example, the operational mode module 310 may change operation of the EAD system 200 from one of the generator mode, the accessory drive mode, and the starter mode to another of the generator mode, the accessory drive mode, and the starter mode based on the interpreted measurement values 312. In one embodiment, for example, the measurement values 312 may include a state of charge of the energy storage system 234. The operational mode module 310 may be configured to change operation of the EAD system 200 from the accessory drive mode to the starter mode when the state of charge value falls below a predetermined value. The operational mode module may also change operation of the EAD system 200 from the starter mode to the generator mode upon detecting that the engine has started.
In another example, according to an embodiment, the measurement values 312 may include an accessory load demand value and a state of charge value. The measurement module 308 may determine an MGU output capacity based on the state of charge value. The operational mode module 310 may change operation of the EAD system 200 from the accessory drive mode to the starter mode when the accessory load demand value exceeds the MGU output capacity. The operational mode module may also change operation of the EAD system from the starter mode to the generator mode upon detecting that the engine has started.
The EAD system 400 also includes a starter assembly 416 and a hydraulic pump 418, each of which being operably coupled to the first gear train 408. As discussed in further detail below, the starter assembly 416 is powered by the MGU 404 via the first gear train 408. In contrast, conventional engine systems typically include electric starter motors. Because the EAD system 400 utilizes the MGU 404 to power the starter assembly 416, the EAD system 400 eliminates the need for a separate starter motor.
As shown in
In some embodiments, engine accessories are powered by torque transferred thereto from the MGU 504 via the second gear train 512. In some embodiments, the second gear train 512 is not coupled to an output of the engine 502 and the accessories are operable only via the MGU 504. However, in other embodiments, the second gear train 512 is coupled to an output of the engine 502 and the accessories are selectively operable via the output of the engine 502. The first gear train 508 is configured to receive torque transferred thereto from at least one of the MGU 504 and an output of the engine 502 either directly (e.g., via the crankshaft) or indirectly (e.g., via the camshaft). Such torque may be used to power the hydraulic pump 514 and/or the air compressor 516.
Referring back to
In certain implementations, the systems or processes described herein can include a controller structured to perform certain operations described herein. In certain implementations, the controller forms a portion of a processing subsystem including one or more computing devices having memory, processing, and communication hardware. The controller may be a single device or a distributed device, and the functions of the controller may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium.
In certain implementations, the controller includes one or more modules structured to functionally execute the operations of the controller. The description herein including modules emphasizes the structural independence of the aspects of the controller, and illustrates one grouping of operations and responsibilities of the controller. Other groupings that execute similar overall operations are understood within the scope of the present application. Modules may be implemented in hardware and/or as computer instructions on a non-transient computer readable storage medium, and modules may be distributed across various hardware or computer based components. More specific descriptions of certain embodiments of controller operations are included in the section referencing
Example and non-limiting module implementation elements include sensors providing any value determined herein, sensors providing any value that is a precursor to a value determined herein, datalink and/or network hardware including communication chips, oscillating crystals, communication links, cables, twisted pair wiring, coaxial wiring, shielded wiring, transmitters, receivers, and/or transceivers, logic circuits, hard-wired logic circuits, reconfigurable logic circuits in a particular non-transient state configured according to the module specification, any actuator including at least an electrical, hydraulic, or pneumatic actuator, a solenoid, an op-amp, analog control elements (springs, filters, integrators, adders, dividers, gain elements), and/or digital control elements.
The term “controller” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, a portion of a programmed processor, or combinations of the foregoing. The apparatus can include special purpose logic circuitry, e.g., an FPGA or an ASIC. The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them. The apparatus and execution environment can realize various different computing model infrastructures, such as distributed computing and grid computing infrastructures.
While this specification contains many specific implementation details, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of features specific to particular implementations. Certain features described in this specification in the context of separate implementations can also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation can also be implemented in multiple implementations separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
As utilized herein, the term “substantially” and any similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided unless otherwise noted. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the invention as recited in the appended claims. Additionally, it is noted that limitations in the claims should not be interpreted as constituting “means plus function” limitations under the United States patent laws in the event that the term “means” is not used therein.
The terms “coupled,” “connected,” and the like as used herein mean the joining of two components directly or indirectly to one another. Such joining may be stationary (e.g., permanent) or moveable (e.g., removable or releasable). Such joining may be achieved with the two components or the two components and any additional intermediate components being integrally formed as a single unitary body with one another or with the two components or the two components and any additional intermediate components being attached to one another.
It is important to note that the construction and arrangement of the system shown in the various exemplary implementations is illustrative only and not restrictive in character. All changes and modifications that come within the spirit and/or scope of the described implementations are desired to be protected. It should be understood that some features may not be necessary and implementations lacking the various features may be contemplated as within the scope of the application, the scope being defined by the claims that follow. It should be understood that features described in one embodiment could also be incorporated and/or combined with features from another embodiment in manner understood by those of ordinary skill in the art. It should also be noted that the terms “example” and “exemplary” as used herein to describe various embodiments are intended to indicate that such embodiments are possible examples, representations, and/or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).