WO2009047110A1

WO2009047110A1 - Modular functional units for starting and stopping an internal combustion engine

Info

Publication number: WO2009047110A1
Application number: PCT/EP2008/062624
Authority: WO
Inventors: Frank Steuernagel; Christian Muehlbauer
Original assignee: Robert Bosch Gmbh
Priority date: 2007-10-01
Filing date: 2008-09-22
Publication date: 2009-04-16
Also published as: DE102007047091A1

Abstract

The invention relates to a device for controlling the operating conditions of a vehicle assembly, comprising a central controller with a central interface and a coordinator, a plurality of function modules that are connected to the central interface and an assembly control interface. The coordinator is connected to the plurality of function modules via the central interface and is configured to select one of the function modules. The controller is configured to control the assembly via the assembly control interface according to the selected function module. The invention also relates to a method for controlling the operating conditions of a vehicle assembly, comprising the steps: linking a plurality of function modules, each of which is configured to execute a function to a coordinator and transmission of a desired function to the coordinator. The function module, the function of which corresponds to the desired function is selected according to the invention by the coordinator and the operating conditions are controlled by the coordinator according to said desired function.

Description

description

Title Modular functional units for starting and stopping an internal combustion engine

State of the art

The invention is based on conventional control mechanisms and control devices for internal combustion engines for the start and stop operation.

In conventional internal combustion engines of vehicles, start signals or stop signals originating from ignition locks or from "start / stop" buttons are implemented directly or by means of relay circuits, for example by means of a hardware circuit or via an intelligent control unit In addition, controls are known in which the start / stop process of the internal combustion engine is automatically triggered, for example, when the vehicle is at a standstill intelligent software function, which is implemented, for example, in a control unit.

The document DE 103 17 090 A1 discloses a device for improving the start / stop operation of a vehicle, in which a start control unit processes signals of a speed sensor and a start time transmitter and emits a corresponding start signal. All controls are implemented in the controller.

Especially in hybrid vehicles results in a very wide range of start / stop situations for the internal combustion engine, since the internal combustion engine with a starter and / or an electric motor that serves as a drive, as well as with other hybrid-specific components such as clutches and transmissions can be combined , So far, the functions have been assigned to control elements or associated components, so that a controller with a variety of functions with complex and ineffective realizations was linked. It is an object of the invention to provide control mechanisms which do not have these disadvantages.

Disclosure of the invention

By means of the method according to the invention and the device according to the invention, the individual functions which determine the control are provided modularly and can therefore be freely selected. This enables simultaneous engineering with regard to the various functions, for example the maintenance and care of different functions or function modules separately from each other. The modularization of the functions easily allows for a customized selection of control functions without additional effort and without the need to change control programming. The individual functions can be modularly added as desired or removed, so that any, freely selectable portfolio can be put together. The modules can be easily added, replaced or removed, whereby the maintenance is significantly simplified, for example by a workshop operation. At the same time, this significantly reduces the likelihood of a fault due to faulty maintenance due to the low complexity of the maintenance process. Furthermore, the various functional modules can be reused. In addition, the modules can be provided as software modules that can be easily imported into the module (s) by selecting a programmer. The software modules thus form a library from which various software modules can be retrieved, the software modules can be very easily selected and assembled by programming on the basis of the same interface before they are stored in a memory of a module or multiple modules or a controller. The structure of the control mechanism according to the invention therefore also has inherent safety features, so that, for example, conflicts between two functions are prevented can be provided with only a single, centralized processing unit, which efficiently utilizes processing hardware, and can easily combine individual functions into groups that can be grouped together in terms of vehicle equipment, customer requirements, and marketplace placement, particularly by the manufacturer.

In hybrid engines, a variety of start / stop situations are possible, for example, towing start, slip start, swing start, torn start / scribe start, pulse start, thrust takeover, dynamic stop or soft stop. Depending on the desired situation, agreed regulations required, which are implemented according to the invention by means of functions that are modularly selectable and each requiring a specific control of several operating parameters. Therefore, according to the invention, a specific, modular function in the form of a functional module is provided for each start / stop situation, with the device according to the invention and the method according to the invention respectively allowing any functional modules to be combined with one another via a coordinator. The coordinator is connected according to the invention via a central interface with a plurality of functional modules, which can be connected or disconnected independently of each other. Preferably, the central interface comprises a plurality of sub-interfaces, each of which can accommodate a module or functional module. The number of sub-interfaces, which form the central interface of the central controller, preferably corresponds to the number of available different modules, but also fewer sub-interfaces may be provided as available function modules. In the latter case, not all available different functional modules can be connected simultaneously to a controller. Furthermore, the central interface can provide more subinterfaces than function modules are available to accommodate, for example, future functional models additionally. Preferably, all subinterfaces are of the same design, ie have identical or compatible plug and socket geometries, are based on the same standards for physical interfaces and / or are based on the same telecommunications standards for the transfer layer, network layer, transport layer and / or session control layer according to OSI reference model ISO 7498. The central interface may be provided in the form of an interface bank in which the geometry of the sub-interface repeats periodically in a bar-shaped or bidirectional manner in the form of a jack or plug matrix. In addition to electrical connections and mechanical fasteners can be provided, which, as well as the electrical connection elements, repeat in the same way. Therefore, each functional module also preferably includes the same functional module interface, wherein each functional module may also have a functional module interface which, although not identical to other functional module interfaces, is compatible with the subinterfaces. Each functional module preferably comprises exactly one functional module interface to which a subinterface is assigned. An electrical connection pair or group is preferably referred to as the interface, which connects the respective functional module detachably from the respective subinterfaces, wherein the interface is essentially defined by the geometric, electrical and logical properties. According to a particular embodiment of the invention, at least some of these properties are identical for all subinterfaces and for all functional module interfaces. -A-

The controller preferably further comprises a coordinator connected to the central interface for data transmission. On the one hand, the connection between the coordinator and the central interface serves to transfer data from the coordinator to the respective functional module, to transmit data from the respective function module to the coordinator and to transmit control data between the coordinator and the respective radio modules. Such control data are used to enable or disable function modules by a signal output by the coordinator, and / or for the transmission of status data from the function module to the coordinator, which reproduces the status of the function modules respectively. The status data thus include, for example: function module ready, function module switched on, function module standby, function module not ready to receive data or not ready to process data and present error within the function module. The control data for the function modules are preferably transmitted via a control line whose signal is used to block and / or to release individual function modules, wherein preferably always a maximum of one function module is enabled and further function modules are disabled. The blocking or release relates to the data processing, data reception, data output and / or other functional areas of the function modules.

Preferably, the central controller and / or the coordinator comprises a lock which enables access to a selected function module and / or blocks access to non-selected function modules. The specification of the individual functional module to be blocked or released can be provided via the type of signal, for example an identifier, or an enable signal can be output via individual enable signals for each functional module or for all subinterfaces, but preferably only a maximum one of the enable signals releases exactly one function module or one subinterface. In the same way, such enable signals may alternatively or in combination block the non-selected function modules. The blocking or release may relate to the data traffic and / or the data processing of the function modules.

Via the central controller or via the coordinator, a bidirectional or semibidirectional data connection is established between an aggregate or combustion engine interface and the selected functional module. This data connection serves for the transmission of operating parameters and sensor data from the engine or internal combustion engine to the selected functional module and the transmission of engine control data from the selected functional module to the engine or internal combustion engine, wherein the engine or the internal combustion engine according to the engine control data. setting the drive parameters. In this case, the data can be transmitted via the coordinator or via another unit, which is controlled by the coordinator, between the function module and the internal combustion engine. Preferably, such engine control data or sensor data run via the functional module interface and via the central interface. For connection of the internal combustion engine, the central controller therefore preferably comprises an engine control interface, which comprises a control output for outputting data to the internal combustion engine and a control input for inputting sensor or operating parameter data to the controller. The internal combustion engine interface is preferably connected directly to the coordinator and / or to the central controller.

The central controller preferably further comprises a default memory or an interface for a default memory, wherein in the default memory default values, safety values and / or stationary values are stored, which relate to an operating parameter of the internal combustion engine or other components of the vehicle. The default memory is preferably connected to the coordinator via a lock, wherein the lock blocks a data connection between the default memory and the selected function module and / or blocks a data connection between the default memory and the respective non-selected function modules. The blocking can be carried out in the same way in which the data connection between the coordinator and the selected function module is also released or the connection to the non-released function modules is blocked, ie. via a trigger signal, a blocking signal or another signal with which the coordinator activates the lock. This ensures that only the selected function module receives at least read permissions for the default memory, or possibly also write permissions for the default memory.

The central controller preferably further comprises a basic function module connected to the coordinator and associated with basic functions. These basic functions may be functions necessary for a standard operation of the internal combustion engine and / or may be functions common to at least some of the functional modules.

The functions within the functional modules or within the basic functional module are preferably stored as software code within the functional module, wherein the functional module further preferably comprises a data processing device and a main memory with which the software code can be converted into corresponding functions. External data are also read in via a function module interface, for example from the default memory and / or from the combustion engine interface. gate control interface to process the corresponding data. The functional module interface therefore preferably only transmits operating parameter data and control data which control the release or blocking of functional modules. The functional module may further comprise hardware components that implement at least part of the function. In a particular embodiment, a hardwired controller is provided instead of the software code within a read-only memory of the functional module, for example via an FPGA, an IC circuit and / or discrete components that realize at least some functional parts. According to a further embodiment, the functional modules each comprise read-only memories in which the respective function is implemented as software code, the calculation taking place on the basis of this software code within the central control. Therefore, data is transmitted via the function module interface which reproduce the function in the form of software code, the software code being loaded therefrom into the central controller in the case of a selected function module, from there by a data processing device, for example a microprocessor or a CPU to be processed. In this case, the central controller receives sensor or operating parameter data from the engine control interface and outputs corresponding engine control data to the engine control interface. In a further embodiment, the data processing for executing the function of the function module can be divided between the function module and the central controller, so that a part of the function is calculated within the function module and a further part of the function is provided by the central controller. The function or the functional part is preferably provided by performing corresponding calculations. Furthermore, part of the function can be taken over by the basic function module, so that the function as a whole results from the function module, the central controller, the basic function module and the respective running software code. The selection of the function can thus lead to software code being transmitted, a single functional module being exclusively enabled for the calculation and / or only the selected functional module being allowed to receive sensor data or operating parameter data and / or to output engine control data to the engine control interface. The respective assignment is carried out by the coordinator via corresponding activation signals of the selected function module or via other mechanisms.

Between the function module interface and the central interface each additional supply lines can be provided. The data transmission between internal combustion engine, engine control interface, coordinator, central interface, function module interface and function module can be via digital data transmission in parallel and / or serial form or by analog signal transmission and / or a combination thereof. The data transfer mechanisms between the various components of the device according to the invention may be different or partially similar. Preferably, the data transmission between the central interface and the functional module interfaces is the same for all functional modules or for all subinterfaces.

According to the invention, operating states of a vehicle internal combustion engine in the form of different start or stop sections are implemented in independent functions as individual function modules. Below are some examples of the corresponding operating states that are implemented by the respective function module for controlling hybrid drives.

- towing start: separating clutch closed, electric machine pulls combustion engine up to idling speed (generally used for first start via ignition lock or in mild hybrids)

- Slip start (power, torque, comfort start): The electric machine pulls up the combustion engine with a sliding disconnect clutch. Combustion engine start-up includes variants Power, Torque and possibly Comfort, which can be characterized by different coupling ramp gradients. - Swing start (also emergency start): With open disconnect clutch (proportional clutch) in the stand, the speed of the electric motor can be increased. As a result, the fastest possible clutch closing is realized with internal combustion engine start.

- Torn start / scribing start: When the disconnect clutch is open, the speed of the electrical machine is increased, the disconnect clutch is closed in a pulsed manner until

Internal combustion engine is entrained. The opening of the separating clutch to a clutch value serves the internal combustion engine for independent startup. Subsequently, a synchronization of the internal combustion engine and the e- lectric machine. Suitable as a comfort start variant, as it increases starting time.

- Pulse start: With an open disconnect clutch (pulse clutch), the speed of the electrical machine can be increased. Later impulsive closing of the clutch with internal combustion engine start.

- Thrust: During electric driving, the speed of the electric machine can be increased. Later closing of the clutch, internal combustion engine is in push circuit.

- Dynamic stop (also called "sailing"): Open load-free disconnect clutch, switch off combustion engine. - Soft stop: Disconnect clutch closed, electric machine actively draws combustion engine to a standstill; Disconnect opens depending on the situation.

The respective function modules preferably report the following signals as control data to the central controller: ready, active, successfully completed, function aborted, error detected and user-related abort.

Brief description of the drawings

Embodiments of the invention are illustrated in the drawings and explained in more detail in the following description.

Show it

Figure 1 shows an embodiment of the invention

Figure 2 shows an embodiment of the invention according to a second aspect and

FIG. 3 is a flow chart which illustrates the method according to the invention by way of example.

Embodiments of the invention

1 shows an embodiment of the device according to the invention is shown. A central controller 10 is connected via a central interface 18.3 with individual functional module interfaces 22 az belonging to the respective functional modules 20 az. The central interface 18.3 comprises individual subinterfaces, which form the individual connection points to data lines 24.1 az and control lines 24.2 az. In the figure 1, the data lines are shown in solid lines, whereas the control lines are shown in dashed lines. The connections of the connection points, ie the sub-interfaces of the central interface is shown in phantom and can be implemented, for example, by a parallel or serial bus. The data line and the control line are not necessarily separate physical lines, but may also be distinguishable by their signal characteristics. The connection of the sub-interfaces of the central interface 18.3 (shown in phantom) is connected to a coordinator 14 which is provided within the central controller 10. The central controller further includes an engine control interface including a control input 18.1 and a control input 18.2. The coordinator 14 is connected to the internal combustion engine Control interface connected. In principle, instead of or in combination with the internal combustion engine interface, the controller may comprise further bidirectional interfaces for further drive components such as e-machine, clutch, transmission, etc. The control input 18.1 and the control output 18.2 can, as shown in dashed lines in Figure 1, are connected to an internal combustion engine 30, wherein the internal combustion engine receives from the control output 18.2 signals according to which operating conditions of the internal combustion engine are set, ie, for example, injection quantity, target speed, ignition angle, Filling level, etc. The internal combustion engine in turn supplies the control input 18.2 with sensor data or operating parameters that characterize operating conditions of the internal combustion engine, such as current speed, torque, temperature, etc. Preferably, the central controller 10 is connected to other components of the drive and / or the vehicle, for example with clutches, speed converters, electric drive machine, and the like, to control and receive from these data in the same manner as the engine 30. The central controller 10 further includes a Vorga- benspeicher 12, which is connected via a barrier 14.1 with the coordinator 14. The coordinator controls the lock 14.1, which may be provided, for example, as a function in the form of software in the coordinator to control the access of individual function modules to the default memory 12. Likewise, the coordinator may further control access to the engine control interface or to other control interfaces of other components of the vehicle. The central controller 10 further comprises a basic function module 16 which is connected to the coordinator and which, in combination with the coordinator, performs basic functions. The central controller 10 preferably has an input via which the desired function can be input, this input preferably being connected to the coordinator 14, so that the latter can send out a corresponding blocking or enabling signal in order to activate the desired function module and to lock the non-selected function modules.

The coordinator releases access by means of enable and / or inhibit signals to setpoint and / or manipulated variables. The desired or manipulated variables are preferably present only once in the system, for example within a main memory of the central control, wherein the access to the main memory, which contains such desired and manipulated variables, is released by means of enable or disable signals. Default values, safety values and stationary values are stored in the setpoint or manipulated variables in the central control, preferably in the default memory. The desired or manipulated variables may relate to one or more components of the vehicle drive. Instead of a release or disable signal, a positive or negative trigger signal can also be used. The respective locking mechanism (which locks or releases the functional module and / or the data connection) is preferably the same for all functional modules. Control lines and the data tions are preferably connected in parallel. Furthermore, a bus protocol is preferably used which avoids a collision, in particular of the signals of the control lines. As a release or blocking signal, a signal can also be used which characterizes the system state, for example the system state of a function module or of the central control. Furthermore, the enable or disable signal, which is supplied to the individual function modules, comprise a unique identifier which corresponds to the identifier of exactly one functional module or no functional module. In such an embodiment, the function modules are only active if their identifier is sent via the respective control line. In this way, all function modules can be locked individually with the same control signal or released individually.

FIG. 2 shows a further embodiment of the invention according to a second aspect. FIG. 2 shows, in addition to circuit implementation, features of the functional sequence. The embodiment of the invention illustrated in FIG. 2 comprises a higher-level structure 110, which provides an input for selecting the functional module. The parent structure may be a vehicle controller, which in turn may receive user input, or may be a user input device that selects the desired function module, ie, the desired function, over the entered desired mode of operation. The higher-level structure 110 controls a state machine 120, which in turn drives the actual central controller 100, which represents an embodiment of the device according to the invention. The central controller 100 comprises a coordinator 130 which controls the release of functional modules and respective write rights or read rights via suitable signals. With the reference numeral 140 ae different, to be selected side by side function modules are shown, for example, flow modules for: tow start, slip start, thrust takeover, soft stop and dynamic stop. As specified by the state machine, the appropriate module is selected. The central controller 110 outputs the corresponding control value S 190, depending on the selected function, to aggregates 150 ac, which are connected to the central control via a control line. As aggregates 150 ac Antriebsg- gregate and other components of a powertrain of a hybrid engine are provided. The operating conditions prevailing in the units or the values detected by sensors there are reported back to the selected module 140a in the form of actual variables S200. Thus, each functional module 140 ae, if it is selected to provide a closed loop, the coordinator 130 does not interfere with the scheme itself, but only selects the corresponding function module. The coordinator 130 thus determines the type of control over the selected function, whereas the individual functional modules 140 ae provide the actual / target control for operating parameters of aggregates 150 ac. Functional parts of the functional modules that are suitable for some functional modules are common, for example, a PI, PD or PID Regiermodul can be provided as a basic function in the central control 100, which only relies on the respective function module. In this way, the same functional parts do not have to be implemented multiple times.

State machine 120 passes a select signal or decision signal 160 to the coordinator, such as a "tow start" trigger signal, and signals are passed from the state machine to the module, for example, when the function is to be retained but a desired operating parameter changes State machine 120 signal S 160 sent to the coordinator 130, a change of the function module, the coordinator 130 queries the respective function module with respect to the operating state (ready?) Of the function module.If the corresponding function module signals S 180 that it is not (yet) ready , the coordinator can wait for a certain period of time for the ready signal and issue an error message if there is no corresponding ready signal S 180. If the selected function module reports with "ready" (S 180) to the coordinator, then the Coordinator 130 access rights to target and nd manipulated variables free or to default values. As already noted, the engine interface provides command and set variables, whereas a default memory provides default values, safety values, and steady state values, both in the case of release by the coordinator. After the appropriate selected function has been called and has recognized the call, it activates the state machine (eg, via coordinator 130) to execute the function flow. Furthermore, the activated and selected function module 140a reports an active signal S180, for example, to the coordinator 130 and / or to the state machine 120. The coordinator thus has the task of mapping the function selected by the state machine by activating the corresponding function module, in order for the state machine and the aggregates emulate a variety of controls that can be individually selected. The state machine can also abort the function via a signal output to the coordinator, for example by an abort signal from the aggregates or by a change signal originating from the superordinate structure. Furthermore, the aggregates preferably return a completed start or stop function to the respective activated or selected module 140a, which then causes the coordinator to return this state to the state machine 120 via signal S 170. The activated and now fully executed function of the function module 140a (see example, drag start) continuously returns a completion status, which informs the coordinator 130 and thus the state machine 120 that the desired function has been completed. If the desired function changes, another function module 140 is selected and the signal output from the predecessor Function module goes to a signal S 180, which indicates an inactive state.

FIG. 3 shows a flow chart which represents an exemplary sequence according to the method according to the invention. At point A, a trigger signal "Towing Start" is input, which is supplied to the central control until the coordinator or the function module no longer outputs a signal that outputs a state "not ready" B, but until a ready signal B ' is issued. Subsequently, the function module corresponding to the sequence "Towing Start" is called, point C. Furthermore, a signal is given at point D, which releases the blocking of the write rights by the selected module, as long as the write rights are not yet given for the selected module , a wait loop E 'is executed.

This is followed by the mapping process F, in which the function modules or the activated function module return the respective operating state, i. active, finished, change the target request. In this case, the modules or the selected module which outputs such a signal can not yet be used until the operating state of the module (s) corresponds to a "ready" state. Only then, when the selected function module reports a ready signal, the function is executed. Thereafter, for example, at point G, the active function module returns with a signal indicating complete execution, i. the termination, the corresponding function. The termination of the respective function thus simultaneously leads to the withdrawal of the write rights at the point H of the activated function module. For example, the change of a feedback signal of the activated function module from "active" to "ready" is evaluated by the coordinator module or by the state machine as a signal that the function of the respective selected function module has ended and has been completed. The corresponding function module is thus deactivated again by withdrawing the write rights or locking the access, in order to avoid that already completed functions of function modules intervene in the operation of the internal combustion engine.

Claims

claims

A device for controlling the operating states of a vehicle unit (30), comprising a central controller (10) comprising a central interface (18.3) and a coordinator (14), a plurality of functional modules (20 az), to the Central interface (18.3) are connected, and an aggregate control interface (18.1,

18.2), wherein the coordinator (14) is connected to the plurality of functional modules (20 az) via the central interface (18.3) and configured to select one of the functional modules (20 az) and the controller is set up, the aggregate (30 ) via the aggregate control interface (18.1, 18.2) according to the selected function module to control.

The apparatus of claim 1, wherein the operating conditions include starting and stopping the assembly (30).

3. Apparatus according to claim 1 or 2, wherein the central interface (18.3) for each functional module comprises a sub-interface and all sub-interfaces (22 az) of the central interface (18.3) are equal and / or each functional module the same functional module interface ( 22 az).

4. Device according to one of the preceding claims, wherein the central controller (10) and / or the coordinator (14) comprises a lock which is adapted to enable access to the respectively selected function module (20 az) and / or access to the each not selected function module or on the respectively non-selected function modules (20 az) to block.

5. Device according to one of the preceding claims, wherein the central controller (10) provides a bidirectional or semi-bidirectional data connection between the selected function module (20 a-z) and the aggregate control interface (18.1, 18.2).

6. Device according to one of the preceding claims, wherein the central controller (10) comprises a default memory (12) or is adapted to be connected to a central default memory (12) for data exchange, and the central controller (10) provides a data connection between the default memory (12) and the selected functional module (20 az) over which the selected functional module can retrieve default values stored in the functional module (20 az).

7. A method for controlling operating conditions of a vehicle unit (30), comprising the steps of:

Connecting a plurality of functional modules (20 a-z), each adapted to perform a respective function, to a coordinator (14); Transmitting a desired function to the coordinator (14);

Selecting by the coordinator (14) the function module whose respective function corresponds to the desired function; and

Controlling the operating conditions according to the desired function by the coordinator

(14).

8. The method of claim 7, wherein selecting the functional module comprises: enabling a data connection between the coordinator (14) and the selected functional module and / or disabling data connections between the coordinator (14) and non-selected functional modules (20 az) respectively the coordinator (14) is connected.

The method of claim 7 or 8, wherein selecting the functional module comprises: enabling a data connection between the selected functional module and the aggregate control interface (18.1, 18.2); and / or blocking data connections between respectively non-selected function modules of the plurality of

Function modules (20 a-z) and the aggregate control interface (18.1, 18.2).

10. The method of claim 7, 8 or 9, wherein selecting the functional module comprises: enabling a data connection between the selected function module (20 az) and a default memory (12) and / or disabling data connections between each non-selected functional module Plurality of functional modules (20 az) and a default memory (12).