EP2267292A1 - Engine Control System - Google Patents
Engine Control System Download PDFInfo
- Publication number
- EP2267292A1 EP2267292A1 EP09163596A EP09163596A EP2267292A1 EP 2267292 A1 EP2267292 A1 EP 2267292A1 EP 09163596 A EP09163596 A EP 09163596A EP 09163596 A EP09163596 A EP 09163596A EP 2267292 A1 EP2267292 A1 EP 2267292A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- microprocessor
- monitoring
- engine
- vehicle
- main
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 claims abstract description 76
- 239000000446 fuel Substances 0.000 claims description 14
- 238000001514 detection method Methods 0.000 claims description 5
- 230000001133 acceleration Effects 0.000 claims description 3
- 238000000034 method Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000002347 injection Methods 0.000 description 2
- 239000007924 injection Substances 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000010561 standard procedure Methods 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Images
Classifications
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/22—Safety or indicating devices for abnormal conditions
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/24—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means
- F02D41/26—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means using computer, e.g. microprocessor
- F02D41/266—Electrical control of supply of combustible mixture or its constituents characterised by the use of digital means using computer, e.g. microprocessor the computer being backed-up or assisted by another circuit, e.g. analogue
Definitions
- the present invention relates to a vehicle engine control and monitoring system, and in particular to an improved system that increases vehicle availability in the event of a fault condition.
- the engine control unit (ECU) of a vehicle engine includes a main microprocessor for controlling various engine functions, including vehicle drive. If the main microprocessor (hereinafter the “main micro") develops an error, for example an algorithmic error, then potentially dangerous consequences can arise. For example, the engine may be caused to deliver torque in excess of the driver demanded torque. For this reason, modern ECUs often include an electronic safety monitor (ESM).
- ESM electronic safety monitor
- the ESM may comprise a dedicated microprocessor (hereinafter referred to as a "monitoring micro"), which is configured to monitor the correct operation of the main micro.
- shut down the main micro if a fault develops in the main micro, the default action is to shut down the main micro or execute a so-called "safe state". In either case, injection events are disabled in the engine, which results in an immediate loss of power. This causes the engine to stall and consequently reduces vehicle availability in the event of a main micro fault. In some circumstances, shutting down the system in this way can be dangerous, for example if a fault develops when the vehicle is travelling at speed in the outside lane of a motorway.
- prior art systems may not be capable of detecting certain faults.
- prior art monitoring systems are configured to monitor output signals from the ECU before those signals reach the engine. The problem with this is that these systems are not able to detect faults that occur downstream of where the feedback signal is taken. This is illustrated schematically in Figure 1 .
- an ECU (1) having a main micro (10), an output module (2), and an ESM (3).
- an engine subsystem (4) External to the ECU (1) is an engine subsystem (4), which comprises a plurality of fuel injectors (5).
- the output module (2) of the ECU (1) is connected to the injectors (5) via a drive line (6).
- the ECU (1) operates the injectors (5) according to a drive signal (7), which is calculated by the main micro (10).
- the drive signal (7) which comprises a series of injector drive pulses, is communicated to the injectors (5) via the output module (2) and the drive line (6).
- the ESM (3) receives a feedback signal (8) from the output module (2) corresponding to the drive signal (7) output by the output module (2).
- the ESM (3) performs a 'torque transform' on the drive signal (7) in order to estimate the torque delivered by the engine when operating in accordance with the drive signal (7).
- the ESM (3) then performs a check to verify if the estimated delivered torque corresponds to the driver-requested torque.
- the driver-requested torque can be determined from monitoring the pedal position (9) of the driver's accelerator pedal. If the estimated delivered torque corresponds to the driver-requested torque, then no fault is reported. Conversely, if the estimated delivered torque does not correspond to the driver-requested torque, a fault is reported and the system is shut down.
- the present invention aims to provide an improved control and monitoring system that increases vehicle availability in the event of a fault developing in the main micro, and which is capable of detecting a wider range of faults than the prior art system described above.
- a vehicle engine control system comprising: a main microprocessor for controlling the vehicle engine; and a monitoring microprocessor for monitoring the correct operation of the main microprocessor; the monitoring microprocessor being configured to receive a first signal indicative of a driver command, and a second signal indicative of an actual engine output parameter, wherein, in the event that a fault is detected in the main microprocessor:
- the monitoring microprocessor may be configured to intervene in order to bring the actual engine output parameter to within the acceptable operating envelope in the event that the acceptable operating envelope is exceeded. To this end, the monitoring micro may disable one or more fuel injectors from an injector drive circuit of the vehicle engine. Alternatively or additionally, the monitoring microprocessor may be configured to intervene by reducing fuel pressure in a common rail supplying one or more fuel injectors of the vehicle engine.
- the monitoring microprocessor may be configured to receive a brake switch signal indicative of the driver applying the vehicle brakes.
- the monitoring microprocessor may be configured to intervene to reduce the engine speed on receiving the brake switch signal.
- the monitoring microprocessor is configured to reduce the engine speed to an engine idle speed immediately on receiving the brake switch signal.
- the first signal may be indicative of the position of a driver accelerator pedal.
- the second signal may be indicative of the rotational speed of the vehicle engine, cylinder pressure or vehicle acceleration.
- the second signal may be sampled on an output side of the vehicle engine.
- the system may be configured to enter a limp-home mode on detection of a fault associated with the main microprocessor.
- the vehicle engine In the limp-home mode, the vehicle engine may be operated according to an engine speed control model.
- the set point for the engine speed control model may be replicated in both the main microprocessor and the monitoring microprocessor.
- the monitoring microprocessor may be operable to control the vehicle engine in accordance with the limp-home mode by utilising the first and second signals in the event of a failure of the main microprocessor.
- Figure 1 which is a schematic representation indicating where feedback signals are taken in a typical prior art control and monitoring system, has already been described above by way of background to the present invention.
- a control and monitoring system is shown schematically in Figure 2 .
- the system comprises a main micro 10 and a monitoring micro 12.
- the main micro 10 is configured to control an injector drive circuit, in which a plurality of fuel injectors 14 are connected. Whilst not shown in Figure 1 , the injectors 14 are connected in respective parallel branches of the injector drive circuit, between high and low voltage rails.
- Each parallel branch includes a switch (not shown) for enabling and disabling the respective injector 14 in that branch from the injector drive circuit; these switches are provided on the low-voltage side of the injectors 14, and are referred to collectively herein as the "low side arbitration logic" 16.
- the monitoring micro 12 is configured to monitor the correct operation of the main micro 10, and is connected on the low voltage side of the injectors 14.
- the monitoring micro 12 has the capability to control the injectors 14 via the low side arbitration logic 16 should this be required in the event of a fault developing in the main micro 10 or otherwise in the event of a main micro failure.
- the monitoring micro 12 is configured to receive three feedback signals: (i) engine speed 18; (ii) pedal position 20; and (iii) brake switch 22.
- the engine speed 18 refers to the actual, real-time, rotational speed of the vehicle engine, and is obtained via a suitable engine speed sensor known in the art.
- the pedal position 20 refers to the position of the driver's accelerator pedal, and is indicative of the real-time driver-demanded torque; the pedal position may be monitored by any suitable pedal-position sensing means known in the art.
- the brake switch 22 relates to the vehicle brakes, and this signal informs the monitoring micro 12 when the driver is applying the brakes; any suitable monitoring means known in the art may be employed for this purpose, for example a suitable sensor configured to detect when the brake pedal is pressed.
- the main micro 10 also receives the three signals 18, 20 and 22. However, providing these signals to the monitoring micro 12 independently from the main micro 10 gives the monitoring micro 12 the capability to control the engine in the event of a fault, as described in further detail later.
- the monitoring micro 12 detects the presence of a fault or error in the main micro 10.
- the monitoring micro 12 may perform algorithmic checks on the main micro 10 to confirm that the main micro 10 is programming correctly, and/or the monitoring micro 12 may perform time-based checks. Any number of standard techniques may be employed for detecting the presence of faults in the main micro 10, and these techniques would be readily apparent to person skilled in the art. In the interests of conciseness, examples of suitable monitoring techniques are not discussed in detail herein because the present invention is concerned with the action that is taken once a fault has been detected, and not with the detection of faults per se. However, it should be noted that a main micro fault may be detected initially by the main micro's onboard diagnostics rather than by the monitoring micro 12, as indicated at Step B1 in Figure 3 .
- Step A2 the monitoring micro 12 reports to the main micro 10 that a fault has been detected (Step A2), and the process flow of Figure 3 continues to Step A3 as described below. If the main micro fault is detected by the main micro's onboard diagnostics (Step B1), then the monitoring micro 12 is not required to report the fault, and the process flow of Figure 3 continues directly to Step A3.
- the main micro 10 enters a "limp home" mode in response to receiving the fault report from the monitoring micro 12 or in response to a fault being detected by the onboard diagnostics.
- the limp-home mode is known, and consists essentially of the main micro 10 controlling the engine according to a reduced-power regime. This allows the driver to continue to drive the vehicle in the event of a fault, so that the vehicle can be driven safely off the road, or to a service centre where the fault can be repaired. It is important to note that, whilst it may be known to enter a limp-home mode when a vehicle develops certain faults, it is not known in the prior art to enter a limp-home mode when faults are detected in the main micro 10. As mentioned in the introduction, the default action in the prior art on detection of faults in the main micro 10 is to shut down the system, which results in an immediate loss of power and hence an immediate loss of vehicle availability.
- the main micro 10 operates the engine according to an engine speed control model, the set point of which is defined by a pedal map duplicated in both the main micro 10 and the monitoring micro 12.
- An example of a pedal map is shown in Figure 4 .
- the x-axis represents driver pedal position, whilst the y-axis represents engine speed.
- the target engine speed is set at 700 rpm (the idle speed).
- the target engine speed is limited to 2000 rpm.
- a linear increase in engine speed is defined between these two extreme pedal positions.
- a non-linear characteristic could be defined in other examples.
- the monitoring micro 12 monitors whether the engine is running within a so-called "SAFE" operating envelope (Step A4), which in this example is an envelope of allowable engine speeds.
- SAFE envelope of allowable engine speeds.
- This envelope is represented by the hatched region below the line in Figure 4 , and is denoted as "SAFE”.
- SAFE the region above the line in Figure 4
- UNSAFE the region above the line in Figure 4
- the monitoring micro utilises the pedal and engine speed feedback signals ( Figure 2 ) to determine if the engine is operating within the allowable operating envelope or outside of the allowable envelope.
- the monitoring micro 12 determines that the engine is operating within the allowable operating envelope (SAFE - Figure 4 )
- the monitoring micro 12 allows the main micro 10 to continue to operate the engine in the limp home mode, i.e. the process flow in Figure 3 returns to Step A3 and the monitoring micro 12 continues to check that the allowed operating envelope (SAFE - Figure 4 ) is respected. Therefore, even though a fault has been detected in the main micro 10, vehicle availability is maintained because the monitoring micro 12 has confirmed that the actual torque experienced by the driver does not exceed the allowable driver-demanded torque as defined in the engine speed control model. Consequently, the driver is able to continue to drive the vehicle to safety in the event of a main micro fault.
- Step A6 the monitoring micro 12 detects that the engine is operating outside of the allowable operating envelope (UNSAFE - Figure 4 )
- the monitoring micro 12 intervenes (Step A6) to reduce the engine speed as described in further detail below. Intervention is required because the UNSAFE region of Figure 4 indicates that the actual torque is greater than the driver-demanded torque.
- the monitoring micro intervenes to reduce the engine speed to within the allowed operating envelope (SAFE region in Figure 4 ).
- the monitoring micro utilises the arbitration logic ( Figure 2 ) on the low side of the injectors to disable one or more of the injectors.
- the monitoring micro may also be configured to control fuel pressure, for example in a common rail supplying the injectors. In such a configuration, the monitoring micro could intervene by reducing the fuel pressure in the event that the allowable engine speed envelope is exceeded to bring the engine speed back into the SAFE region of Figure 4 .
- the monitoring micro 12 In addition to ensuring that the allowable operating envelope is respected whilst the main micro 10 operates the limp home mode, the monitoring micro 12 simultaneously monitors the brake switch (Step A5 in Figure 3 ). If the monitoring micro 12 detects that the driver is applying the brake, then it will intervene at Step A6 (either via the arbitration logic or by reducing rail pressure) to bring the engine speed immediately down to the idle speed of 700 rpm; this is irrespective of the current (accelerator) pedal position. This intervention provides an additional level of safety to the system, and ensures safe operation even in the event of an accelerator pedal failure, or if the monitoring micro 12 receives an erroneous pedal position signal for another reason.
- FIG. 5 there is shown an ECU 30 comprising the main micro 10 and the monitoring micro 12. External to the ECU 30 is the engine subsystem 32, which includes the fuel injectors 34.
- An output module 36 of the ECU 30 communicates with the fuel injectors 34 via a control line 38.
- the output module 36 sends injector drive pulses 40 to the injectors 34 to control the injection of fuel.
- the monitoring micro 12 receives three feedback signals, i.e. the engine speed signal 18, the pedal position signal 20, and the brake switch signal 22.
- the monitoring micro 12 receives feedback from the output side of the engine subsystem 32.
- that feedback is the sampled engine speed 18, which is indicative of the actual behaviour of the engine experienced by the driver.
- the prior art which takes its feedback from the input side of the engine subsystem (see Figure 1 ), and hence is only indicative of target or predicted parameters and thus provides no indication of the actual conditions experienced by the driver.
- the prior art system of Figure 1 would not detect faults occurring downstream of the output module of the ECU, the system shown in Figure 5 is able to detect a wider range of faults, including faults occurring downstream of the output module (36) that may affect actual torque delivery.
- the present system increases vehicle availability in the event of a fault developing in the main micro 10.
- this is achieved by allowing the main micro 10 to continue to operate within a predefined operating envelope that has been deemed to be safe, with the monitoring micro 12 subsequently managing the failed state by intervening when required. Consequently, in the event of main micro failure, the driver is able to continue to drive the vehicle to safety or to a service centre where the fault can be repaired.
- the monitoring micro 12 may monitor other parameters such as cylinder pressure or vehicle acceleration in order to determine the actual engine output.
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Chemical & Material Sciences (AREA)
- Combustion & Propulsion (AREA)
- Mechanical Engineering (AREA)
- Computer Hardware Design (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Combined Controls Of Internal Combustion Engines (AREA)
- Electrical Control Of Air Or Fuel Supplied To Internal-Combustion Engine (AREA)
Abstract
Description
- The present invention relates to a vehicle engine control and monitoring system, and in particular to an improved system that increases vehicle availability in the event of a fault condition.
- The engine control unit (ECU) of a vehicle engine includes a main microprocessor for controlling various engine functions, including vehicle drive. If the main microprocessor (hereinafter the "main micro") develops an error, for example an algorithmic error, then potentially dangerous consequences can arise. For example, the engine may be caused to deliver torque in excess of the driver demanded torque. For this reason, modern ECUs often include an electronic safety monitor (ESM). The ESM may comprise a dedicated microprocessor (hereinafter referred to as a "monitoring micro"), which is configured to monitor the correct operation of the main micro.
- At present, if a fault develops in the main micro, the default action is to shut down the main micro or execute a so-called "safe state". In either case, injection events are disabled in the engine, which results in an immediate loss of power. This causes the engine to stall and consequently reduces vehicle availability in the event of a main micro fault. In some circumstances, shutting down the system in this way can be dangerous, for example if a fault develops when the vehicle is travelling at speed in the outside lane of a motorway.
- In addition to the aforesaid problems, prior art systems may not be capable of detecting certain faults. In general, prior art monitoring systems are configured to monitor output signals from the ECU before those signals reach the engine. The problem with this is that these systems are not able to detect faults that occur downstream of where the feedback signal is taken. This is illustrated schematically in
Figure 1 . - Referring to
Figure 1 , there is shown an ECU (1) having a main micro (10), an output module (2), and an ESM (3). External to the ECU (1) is an engine subsystem (4), which comprises a plurality of fuel injectors (5). The output module (2) of the ECU (1) is connected to the injectors (5) via a drive line (6). The ECU (1) operates the injectors (5) according to a drive signal (7), which is calculated by the main micro (10). The drive signal (7), which comprises a series of injector drive pulses, is communicated to the injectors (5) via the output module (2) and the drive line (6). As shown inFigure 1 , the ESM (3) receives a feedback signal (8) from the output module (2) corresponding to the drive signal (7) output by the output module (2). - The ESM (3) performs a 'torque transform' on the drive signal (7) in order to estimate the torque delivered by the engine when operating in accordance with the drive signal (7). The ESM (3) then performs a check to verify if the estimated delivered torque corresponds to the driver-requested torque. The driver-requested torque can be determined from monitoring the pedal position (9) of the driver's accelerator pedal. If the estimated delivered torque corresponds to the driver-requested torque, then no fault is reported. Conversely, if the estimated delivered torque does not correspond to the driver-requested torque, a fault is reported and the system is shut down.
- Referring still to
Figure 1 , if a fault developed within the ECU (1), but downstream of the output module (2), for example at position "X", this could affect the actual drive signal communicated to the fuel injectors (5), and would consequently affect the actual torque delivery. However, the ESM (3) would not detect this fault. This is because the ESM (3) receives its feedback from the output module (2), which is upstream of the fault at position "X", and hence the fault would not be reflected in the feedback signal (8) provided to the ESM (3). Similarly, this system would not detect mechanical faults occurring downstream of the ECU (3), for example faults occurring in the engine subsystem (4), which could also affect the actual torque delivered by the engine. - Against this background, the present invention aims to provide an improved control and monitoring system that increases vehicle availability in the event of a fault developing in the main micro, and which is capable of detecting a wider range of faults than the prior art system described above.
- According to the present invention there is provided a vehicle engine control system comprising: a main microprocessor for controlling the vehicle engine; and a monitoring microprocessor for monitoring the correct operation of the main microprocessor; the monitoring microprocessor being configured to receive a first signal indicative of a driver command, and a second signal indicative of an actual engine output parameter, wherein, in the event that a fault is detected in the main microprocessor:
- (i) the monitoring microprocessor is configured to determine from the first and second signals if the actual engine output parameter is within a predefined acceptable operating envelope, and
- (ii) the main microprocessor is allowed to continue to operate the vehicle engine provided that the actual engine output parameter is within the acceptable operating envelope.
- The monitoring microprocessor may be configured to intervene in order to bring the actual engine output parameter to within the acceptable operating envelope in the event that the acceptable operating envelope is exceeded. To this end, the monitoring micro may disable one or more fuel injectors from an injector drive circuit of the vehicle engine. Alternatively or additionally, the monitoring microprocessor may be configured to intervene by reducing fuel pressure in a common rail supplying one or more fuel injectors of the vehicle engine.
- Advantageously, the monitoring microprocessor may be configured to receive a brake switch signal indicative of the driver applying the vehicle brakes. The monitoring microprocessor may be configured to intervene to reduce the engine speed on receiving the brake switch signal. Preferably, the monitoring microprocessor is configured to reduce the engine speed to an engine idle speed immediately on receiving the brake switch signal.
- The first signal may be indicative of the position of a driver accelerator pedal. The second signal may be indicative of the rotational speed of the vehicle engine, cylinder pressure or vehicle acceleration. The second signal may be sampled on an output side of the vehicle engine.
- The system may be configured to enter a limp-home mode on detection of a fault associated with the main microprocessor. In the limp-home mode, the vehicle engine may be operated according to an engine speed control model. The set point for the engine speed control model may be replicated in both the main microprocessor and the monitoring microprocessor. The monitoring microprocessor may be operable to control the vehicle engine in accordance with the limp-home mode by utilising the first and second signals in the event of a failure of the main microprocessor.
-
Figure 1 , which is a schematic representation indicating where feedback signals are taken in a typical prior art control and monitoring system, has already been described above by way of background to the present invention. - The invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
-
Figure 2 is a block diagram of a control and monitoring system according to an embodiment of the present invention; -
Figure 3 is a flow chart showing the process flow of the system ofFigure 2 ; -
Figure 4 is a graph showing an engine-speed pedal map utilised in the system ofFigures 2 and3 ; and -
Figure 5 is a schematic representation of the system ofFigures 2 to 4 , illustrating where feedback signals are taken. - A control and monitoring system is shown schematically in
Figure 2 . The system comprises amain micro 10 and amonitoring micro 12. Themain micro 10 is configured to control an injector drive circuit, in which a plurality offuel injectors 14 are connected. Whilst not shown inFigure 1 , theinjectors 14 are connected in respective parallel branches of the injector drive circuit, between high and low voltage rails. Each parallel branch includes a switch (not shown) for enabling and disabling therespective injector 14 in that branch from the injector drive circuit; these switches are provided on the low-voltage side of theinjectors 14, and are referred to collectively herein as the "low side arbitration logic" 16. - The
monitoring micro 12 is configured to monitor the correct operation of themain micro 10, and is connected on the low voltage side of theinjectors 14. Themonitoring micro 12 has the capability to control theinjectors 14 via the lowside arbitration logic 16 should this be required in the event of a fault developing in themain micro 10 or otherwise in the event of a main micro failure. - The
monitoring micro 12 is configured to receive three feedback signals: (i)engine speed 18; (ii)pedal position 20; and (iii)brake switch 22. Theengine speed 18 refers to the actual, real-time, rotational speed of the vehicle engine, and is obtained via a suitable engine speed sensor known in the art. Thepedal position 20 refers to the position of the driver's accelerator pedal, and is indicative of the real-time driver-demanded torque; the pedal position may be monitored by any suitable pedal-position sensing means known in the art. Thebrake switch 22 relates to the vehicle brakes, and this signal informs the monitoring micro 12 when the driver is applying the brakes; any suitable monitoring means known in the art may be employed for this purpose, for example a suitable sensor configured to detect when the brake pedal is pressed. - Whilst not shown in
Figure 2 , the main micro 10 also receives the threesignals monitoring micro 12 the capability to control the engine in the event of a fault, as described in further detail later. - Operation of the system in the event of a fault occurring in the main micro 10 will now be described with reference to
Figure 3 . Referring toFigure 3 , at Step A1 themonitoring micro 12 detects the presence of a fault or error in the main micro 10. In order to detect the fault/error, the monitoring micro 12 may perform algorithmic checks on the main micro 10 to confirm that the main micro 10 is programming correctly, and/or themonitoring micro 12 may perform time-based checks. Any number of standard techniques may be employed for detecting the presence of faults in the main micro 10, and these techniques would be readily apparent to person skilled in the art. In the interests of conciseness, examples of suitable monitoring techniques are not discussed in detail herein because the present invention is concerned with the action that is taken once a fault has been detected, and not with the detection of faults per se. However, it should be noted that a main micro fault may be detected initially by the main micro's onboard diagnostics rather than by the monitoring micro 12, as indicated at Step B1 inFigure 3 . - Still referring to
Figure 3 , following the detection of a fault in the main micro 10 at Step A1, the monitoring micro 12 reports to the main micro 10 that a fault has been detected (Step A2), and the process flow ofFigure 3 continues to Step A3 as described below. If the main micro fault is detected by the main micro's onboard diagnostics (Step B1), then themonitoring micro 12 is not required to report the fault, and the process flow ofFigure 3 continues directly to Step A3. - At Step A3, the main micro 10 enters a "limp home" mode in response to receiving the fault report from the monitoring micro 12 or in response to a fault being detected by the onboard diagnostics. The limp-home mode is known, and consists essentially of the main micro 10 controlling the engine according to a reduced-power regime. This allows the driver to continue to drive the vehicle in the event of a fault, so that the vehicle can be driven safely off the road, or to a service centre where the fault can be repaired. It is important to note that, whilst it may be known to enter a limp-home mode when a vehicle develops certain faults, it is not known in the prior art to enter a limp-home mode when faults are detected in the main micro 10. As mentioned in the introduction, the default action in the prior art on detection of faults in the main micro 10 is to shut down the system, which results in an immediate loss of power and hence an immediate loss of vehicle availability.
- In the limp home mode (Step A3), the main micro 10 operates the engine according to an engine speed control model, the set point of which is defined by a pedal map duplicated in both the main micro 10 and the
monitoring micro 12. An example of a pedal map is shown inFigure 4 . Referring toFigure 4 , the x-axis represents driver pedal position, whilst the y-axis represents engine speed. At 0 % pedal, i.e. when the driver is not pressing the accelerator pedal, the target engine speed is set at 700 rpm (the idle speed). At 100 % pedal, i.e. when the driver presses the accelerator pedal to its maximum extent, the target engine speed is limited to 2000 rpm. In this example, a linear increase in engine speed is defined between these two extreme pedal positions. However, it will be appreciated that a non-linear characteristic could be defined in other examples. - Returning to
Figure 3 , whilst the main micro 10 controls the engine in the limp-home mode (Step A3), the monitoring micro 12 monitors whether the engine is running within a so-called "SAFE" operating envelope (Step A4), which in this example is an envelope of allowable engine speeds. This envelope is represented by the hatched region below the line inFigure 4 , and is denoted as "SAFE". Conversely, the region above the line inFigure 4 is denoted as "UNSAFE" and corresponds to engine speeds outside of the allowable envelope. The monitoring micro utilises the pedal and engine speed feedback signals (Figure 2 ) to determine if the engine is operating within the allowable operating envelope or outside of the allowable envelope. - If the monitoring micro at Step A4 (
Figure 3 ) determines that the engine is operating within the allowable operating envelope (SAFE -Figure 4 ), then themonitoring micro 12 allows the main micro 10 to continue to operate the engine in the limp home mode, i.e. the process flow inFigure 3 returns to Step A3 and themonitoring micro 12 continues to check that the allowed operating envelope (SAFE -Figure 4 ) is respected. Therefore, even though a fault has been detected in the main micro 10, vehicle availability is maintained because themonitoring micro 12 has confirmed that the actual torque experienced by the driver does not exceed the allowable driver-demanded torque as defined in the engine speed control model. Consequently, the driver is able to continue to drive the vehicle to safety in the event of a main micro fault. - However, if at Step A4 (
Figure 3 ) themonitoring micro 12 detects that the engine is operating outside of the allowable operating envelope (UNSAFE -Figure 4 ), then themonitoring micro 12 intervenes (Step A6) to reduce the engine speed as described in further detail below. Intervention is required because the UNSAFE region ofFigure 4 indicates that the actual torque is greater than the driver-demanded torque. - At Step A6, if the engine speed exceeds the allowable operating envelope, then the monitoring micro intervenes to reduce the engine speed to within the allowed operating envelope (SAFE region in
Figure 4 ). To achieve this, the monitoring micro utilises the arbitration logic (Figure 2 ) on the low side of the injectors to disable one or more of the injectors. Whilst not shown in the drawings, the monitoring micro may also be configured to control fuel pressure, for example in a common rail supplying the injectors. In such a configuration, the monitoring micro could intervene by reducing the fuel pressure in the event that the allowable engine speed envelope is exceeded to bring the engine speed back into the SAFE region ofFigure 4 . - In addition to ensuring that the allowable operating envelope is respected whilst the main micro 10 operates the limp home mode, the monitoring micro 12 simultaneously monitors the brake switch (Step A5 in
Figure 3 ). If themonitoring micro 12 detects that the driver is applying the brake, then it will intervene at Step A6 (either via the arbitration logic or by reducing rail pressure) to bring the engine speed immediately down to the idle speed of 700 rpm; this is irrespective of the current (accelerator) pedal position. This intervention provides an additional level of safety to the system, and ensures safe operation even in the event of an accelerator pedal failure, or if themonitoring micro 12 receives an erroneous pedal position signal for another reason. - For comparison purposes with the prior art system shown in
Figure 1 , the feedback signals that are provided to the monitoring micro 12 in the present system are illustrated schematically inFigure 5 . Referring toFigure 5 , there is shown anECU 30 comprising the main micro 10 and themonitoring micro 12. External to theECU 30 is theengine subsystem 32, which includes thefuel injectors 34. An output module 36 of theECU 30 communicates with thefuel injectors 34 via a control line 38. The output module 36 sendsinjector drive pulses 40 to theinjectors 34 to control the injection of fuel. Themonitoring micro 12 receives three feedback signals, i.e. theengine speed signal 18, thepedal position signal 20, and thebrake switch signal 22. - Notably, in the present system the
monitoring micro 12 receives feedback from the output side of theengine subsystem 32. In this example, that feedback is the sampledengine speed 18, which is indicative of the actual behaviour of the engine experienced by the driver. This is in contrast to the prior art, which takes its feedback from the input side of the engine subsystem (seeFigure 1 ), and hence is only indicative of target or predicted parameters and thus provides no indication of the actual conditions experienced by the driver. Whereas the prior art system ofFigure 1 would not detect faults occurring downstream of the output module of the ECU, the system shown inFigure 5 is able to detect a wider range of faults, including faults occurring downstream of the output module (36) that may affect actual torque delivery. - It is clear from the above description that the present system increases vehicle availability in the event of a fault developing in the main micro 10. In summary, this is achieved by allowing the main micro 10 to continue to operate within a predefined operating envelope that has been deemed to be safe, with the monitoring micro 12 subsequently managing the failed state by intervening when required. Consequently, in the event of main micro failure, the driver is able to continue to drive the vehicle to safety or to a service centre where the fault can be repaired.
- It will be appreciated that many modifications may be made to the examples described above without departing from the scope of the present invention as defined in the following claims. For example, in addition to or instead of monitoring engine speed, the monitoring micro 12 may monitor other parameters such as cylinder pressure or vehicle acceleration in order to determine the actual engine output.
Claims (14)
- A vehicle engine control system comprising:a main microprocessor (10) for controlling the vehicle engine; anda monitoring microprocessor (12) for monitoring the correct operation of the main microprocessor (10);the monitoring microprocessor (12) being configured to receive a first signal (20) indicative of a driver command, and a second signal (18) indicative of an actual engine output parameter,wherein, in the event that a fault is detected in the main microprocessor (10):(i) the monitoring microprocessor (12) is configured to determine from the first and second signals (20, 18) if the actual engine output parameter is within a predefined acceptable operating envelope, and(ii) the main microprocessor (10) is allowed to continue to operate the vehicle engine provided that the actual engine output parameter is within the acceptable operating envelope.
- The system of Claim 1, wherein in the event that the acceptable operating envelope is exceeded, the monitoring microprocessor (12) is configured to intervene in order to bring the actual engine output parameter to within the acceptable operating envelope.
- The system of Claim 2, wherein the monitoring microprocessor (12) is configured to intervene by disabling one or more fuel injectors from an injector drive circuit of the vehicle engine.
- The system of Claim 2 or Claim 3, wherein the monitoring microprocessor (12) is configured to intervene by reducing fuel pressure in a common rail supplying one or more fuel injectors of the vehicle engine.
- The system of any preceding claim, wherein the monitoring microprocessor (12) is configured to receive a brake switch signal (22) indicative of the driver applying the vehicle brakes.
- The system of Claim 6, wherein the monitoring microprocessor (12) is configured to intervene to reduce the engine speed on receiving the brake switch signal (22).
- The system of Claim 6, wherein the monitoring microprocessor (12) is configured to reduce the engine speed to an engine idle speed immediately on receiving the brake switch signal (22).
- The system of any preceding claim, wherein the first signal (20) is indicative of the position of a driver accelerator pedal.
- The system of any preceding claim, wherein the second signal (18) is indicative of the rotational speed of the vehicle engine, cylinder pressure or vehicle acceleration.
- The system of any preceding claim, wherein the second signal (18) is sampled on an output side of the vehicle engine.
- The system of any preceding claim, wherein the system is configured to enter a limp-home mode on detection of a fault associated with the main microprocessor (10).
- The system of Claim 11, wherein the vehicle engine is operated according to an engine speed control model in the limp-home mode.
- The system of Claim 12, wherein the set point for the engine speed control model is replicated in both the main microprocessor (10) and the monitoring microprocessor (12).
- The system of Claim 13, wherein the monitoring microprocessor (12) is operable to control the vehicle engine in accordance with the limp-home mode by utilising the first and second signals in the event of a failure of the main microprocessor (10).
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09163596.1A EP2267292B1 (en) | 2009-06-24 | 2009-06-24 | Engine Control System |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP09163596.1A EP2267292B1 (en) | 2009-06-24 | 2009-06-24 | Engine Control System |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2267292A1 true EP2267292A1 (en) | 2010-12-29 |
EP2267292B1 EP2267292B1 (en) | 2017-02-01 |
Family
ID=41268068
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09163596.1A Active EP2267292B1 (en) | 2009-06-24 | 2009-06-24 | Engine Control System |
Country Status (1)
Country | Link |
---|---|
EP (1) | EP2267292B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012016155A1 (en) * | 2010-07-30 | 2012-02-02 | General Electric Company | Safety module for an engine control system |
US9278746B1 (en) * | 2013-03-15 | 2016-03-08 | Brunswick Corporation | Systems and methods for redundant drive-by-wire control of marine engines |
US9726108B2 (en) | 2010-07-30 | 2017-08-08 | General Electric Company | Integrated safety and input/output module for an engine control system |
US9940762B2 (en) * | 2013-09-25 | 2018-04-10 | Ford Global Technologies, Llc | Systems and methods for identification of a compromised module |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3804012A1 (en) * | 1988-02-10 | 1989-08-24 | Daimler Benz Ag | Method for preventing the over-revving of an internal combustion engine |
DE3844286A1 (en) * | 1988-12-30 | 1990-07-05 | Bosch Gmbh Robert | SAFETY EMERGENCY PROCEDURE FOR MOTOR VEHICLES AND DEVICE FOR ITS IMPLEMENTATION |
US20030088358A1 (en) | 2001-11-02 | 2003-05-08 | Yoshiharu Takeuchi | Vehicular controller |
JP2003155954A (en) | 2001-11-19 | 2003-05-30 | Denso Corp | Electronic control device for vehicle |
US20030144778A1 (en) | 2002-01-28 | 2003-07-31 | Hidemasa Miyano | Vehicle electronic control system having fail-safe function |
-
2009
- 2009-06-24 EP EP09163596.1A patent/EP2267292B1/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3804012A1 (en) * | 1988-02-10 | 1989-08-24 | Daimler Benz Ag | Method for preventing the over-revving of an internal combustion engine |
DE3844286A1 (en) * | 1988-12-30 | 1990-07-05 | Bosch Gmbh Robert | SAFETY EMERGENCY PROCEDURE FOR MOTOR VEHICLES AND DEVICE FOR ITS IMPLEMENTATION |
US20030088358A1 (en) | 2001-11-02 | 2003-05-08 | Yoshiharu Takeuchi | Vehicular controller |
JP2003155954A (en) | 2001-11-19 | 2003-05-30 | Denso Corp | Electronic control device for vehicle |
US20030144778A1 (en) | 2002-01-28 | 2003-07-31 | Hidemasa Miyano | Vehicle electronic control system having fail-safe function |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012016155A1 (en) * | 2010-07-30 | 2012-02-02 | General Electric Company | Safety module for an engine control system |
US9726108B2 (en) | 2010-07-30 | 2017-08-08 | General Electric Company | Integrated safety and input/output module for an engine control system |
US9278746B1 (en) * | 2013-03-15 | 2016-03-08 | Brunswick Corporation | Systems and methods for redundant drive-by-wire control of marine engines |
US9940762B2 (en) * | 2013-09-25 | 2018-04-10 | Ford Global Technologies, Llc | Systems and methods for identification of a compromised module |
Also Published As
Publication number | Publication date |
---|---|
EP2267292B1 (en) | 2017-02-01 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6751544B2 (en) | Vehicle engine control device | |
EP0555892B1 (en) | Engine throttle control system | |
JP4409800B2 (en) | Engine control device | |
US8169173B2 (en) | Method for controlling a vehicle drive unit | |
US8956266B2 (en) | Vehicle driving force control device | |
KR20170037528A (en) | Method and device for operating a driving system for a motor vehicle using an acceleration monitoring | |
KR101000433B1 (en) | Fail safe controlling method of oil pump control unit for hybrid vehicle | |
JPS6251737A (en) | Safety emergency travelling method and device for self-ignition type internal combustion engine | |
US9460628B2 (en) | Method and device for preventing unintentional acceleration of a motor vehicle | |
US11040673B2 (en) | Control apparatus and control method for electric motor in vehicle | |
US20160010582A1 (en) | Method and arrangement for controlling an internal combustion engine, comprising at least two control units | |
US9567937B2 (en) | Method and device for operating a fuel injection device, especially of a motor vehicle | |
JP4753085B2 (en) | Control device for internal combustion engine | |
EP2267292B1 (en) | Engine Control System | |
KR20130029879A (en) | Control method for fail safety of hybrid vehicle | |
CN106476812B (en) | Method and device for operating a drive system of a motor vehicle | |
JP2011032903A (en) | Control device of vehicle | |
JP2749345B2 (en) | Method and apparatus for monitoring a safety stop for an internal combustion engine | |
JP4012654B2 (en) | Engine equipment control device and electronically controlled throttle system | |
US8074527B2 (en) | Monitoring system for a hybrid drive | |
US8433464B2 (en) | Method for simplifying torque distribution in multiple drive systems | |
JP4623991B2 (en) | Vehicle control system | |
JPH06320981A (en) | Method and device for controlling output of vehicle driving unit | |
KR101870486B1 (en) | Method and device for monitoring a control unit for operating an engine system | |
JP2010101249A (en) | Idle stop control device for internal combustion engine |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA RS |
|
17P | Request for examination filed |
Effective date: 20110629 |
|
17Q | First examination report despatched |
Effective date: 20110801 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: DELPHI INTERNATIONAL OPERATIONS LUXEMBOURG S.A.R.L |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20160901 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA RS |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP Ref country code: AT Ref legal event code: REF Ref document number: 865818 Country of ref document: AT Kind code of ref document: T Effective date: 20170215 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 602009044048 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MP Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: LT Ref legal event code: MG4D |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MK05 Ref document number: 865818 Country of ref document: AT Kind code of ref document: T Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 9 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170502 Ref country code: NO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170501 Ref country code: IS Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170601 Ref country code: LT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: LV Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: ES Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170601 Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170501 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 602009044048 Country of ref document: DE |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20171103 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MC Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: MM4A |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170624 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170624 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170630 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170630 |
|
REG | Reference to a national code |
Ref country code: BE Ref legal event code: MM Effective date: 20170630 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 10 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170630 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170624 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602009044048 Country of ref document: DE Owner name: DELPHI TECHNOLOGIES IP LIMITED, BB Free format text: FORMER OWNER: DELPHI INTERNATIONAL OPERATIONS LUXEMBOURG S.A R.L., BASCHARAGE, LU |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: 732E Free format text: REGISTERED BETWEEN 20190222 AND 20190227 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO Effective date: 20090624 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CY Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: MK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20170201 |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230327 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20230612 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R081 Ref document number: 602009044048 Country of ref document: DE Owner name: PHINIA DELPHI LUXEMBOURG SARL, LU Free format text: FORMER OWNER: DELPHI TECHNOLOGIES IP LIMITED, ST. MICHAEL, BB |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20240509 Year of fee payment: 16 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20240509 Year of fee payment: 16 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20240509 Year of fee payment: 16 |