EP1796051B1 - Diagnostics devices in a vehicle with diagnostics framework for diagnostics module - Google Patents
Diagnostics devices in a vehicle with diagnostics framework for diagnostics module Download PDFInfo
- Publication number
- EP1796051B1 EP1796051B1 EP06090235A EP06090235A EP1796051B1 EP 1796051 B1 EP1796051 B1 EP 1796051B1 EP 06090235 A EP06090235 A EP 06090235A EP 06090235 A EP06090235 A EP 06090235A EP 1796051 B1 EP1796051 B1 EP 1796051B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- diagnostic
- vehicle
- framework
- modules
- vehicle systems
- 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.)
- Not-in-force
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
Definitions
- the invention relates to a device in a vehicle for diagnosis by a vehicle data bus of networked vehicle systems, comprising a diagnostic unit comprising an interface for exchanging information about the vehicle data bus with the networked vehicle systems.
- individual vehicle systems which preferably include controllers, are networked together by a vehicle data bus.
- the individual vehicle systems each include a diagnostic unit which is integrated into the respective control unit of the vehicle system.
- the diagnosis of the individual vehicle systems is carried out by the individual diagnostic units in the vehicle systems. Errors determined are stored in a fault memory in the individual vehicle systems.
- a vehicle-external diagnostic and test device which is linked to the vehicle data bus, the individual diagnostic units or fault memory can be queried. A comprehensive analysis of the vehicle as a whole is made difficult by this approach.
- similar diagnostic capacities are often maintained in the individual diagnostic units of the vehicle systems.
- Such a diagnostic device is for example in the DE 102 54 393 A1 described.
- a diagnostic control unit is connected to data and signal lines of a wiring harness and carries out functional tests of the components already installed during the production process.
- the diagnostic results obtained are transmitted wirelessly and used to locate the motor vehicle during production.
- the diagnostic device used in this case can be integrated into a control unit, which later also performs checking functions during operation of the vehicle.
- individual test sections are carried out successively in order to check individual components of the produced vehicle.
- the test program which is designed as software, can be replaced, a simultaneous execution of several test procedures is not provided. Thus, a complex diagnosis is particularly difficult if several vehicle components are to be checked in parallel.
- the DE 10 2004 008 816 A discloses a framework structure for diagnosing engine data of a vehicle according to the preamble of claim 1.
- the invention has for its object to provide a device for diagnosis by a vehicle data bus networked vehicle systems in which a simultaneous accelerated diagnosis of multiple vehicle systems is possible and an expandability and adaptation of the diagnostic capabilities in a modification of the vehicle after the original production easy is possible.
- diagnostic framework keeps part of the data transmitted by the vehicle systems in a memory area in order to reduce the number of accesses of the diagnostic modules to the vehicle systems.
- the diagnostic framework comprises a central fault memory in which the fault events of the networked vehicle systems are stored together has proven to be particularly advantageous.
- an overview of fault events that have occurred can thus be obtained in a simple manner.
- the results obtained during in-vehicle diagnostics are also used for vehicle maintenance and repair. It is therefore customary to couple vehicle-external test devices with the vehicle in order to read out the internal diagnostic results or to have specific diagnostic steps carried out on the vehicle systems and / or executed.
- a preferred embodiment therefore provides in that the diagnostic unit can be linked via the vehicle data bus or via a further interface with a vehicle-external test device, data being exchanged between the vehicle-external test device and the diagnostic modules or the vehicle systems via the diagnostic framework.
- the diagnostic framework can provide a uniform interface for access by an external test device. Thus, different vehicles can interact with one and the same external test device. It is only necessary to adapt the individual diagnostic frameworks of the different vehicles to the vehicle systems installed therein.
- the diagnostic modules which are fitted in the application program interface of the diagnostic framework, can also be used universally.
- the proposed procedure ensures that the results already determined by the in-vehicle diagnosis can be detected particularly easily and quickly. If, for example, a memory area is provided for the common storage of the fault events of the vehicle systems, then these fault events can be transmitted quickly to the external test device via the diagnostic framework without the need for access to the individual vehicle systems via the vehicle data bus. This speeds up vehicle diagnostics with an external test device.
- the diagnostic framework is advantageously designed such that diagnostic functions and / or diagnostic routines and / or memory and / or computing capacity are provided centrally to the diagnostic modules.
- diagnostic routines or memory areas of several diagnostic modules can be shared. This reduces the required storage and computing capacity in the vehicle.
- the individual vehicle systems no longer have to be designed to carry out diagnostic functions on their own. This makes the individual vehicle systems easier and cheaper.
- the proposed procedure is further characterized in that after completion of the vehicle, the diagnostic functionality can be extended and / or changed. It is not necessary to modify the individual vehicle systems, which is very expensive. Rather, it is sufficient to modify or replace individual or all diagnostic modules, or to add a new or several new diagnostic modules to the diagnostic unit.
- a function-oriented diagnosis is usually unsatisfactory or even impossible with diagnostic modules that are integrated in the individual vehicle systems. Especially with a function-oriented diagnosis, many data and information of the individual vehicle systems of several functional diagnoses needed. By embedding the diagnostic modules in the diagnostic framework, it is achieved that the diagnostic framework can maintain this data centrally, so that the number of accesses to the vehicle systems and a load on the vehicle data bus is significantly reduced.
- the vehicle systems preferably each comprise at least one control unit.
- the diagnostic unit is integrated in a control unit of the vehicle, preferably in a central multi-function display operating system.
- the vehicle data bus is a CAN bus and at least one of the diagnostic modules designed as a CAN snap module to log preselected CAN bus information.
- a CAN snap module is a diagnostic module capable of logging preselected data transmitted via the vehicle data bus.
- specifications can be made as to which data should be logged.
- the logged data can be stored in a memory in the diagnostic framework to be available for later offline analysis. Therefore, in a preferred embodiment, a memory is provided in the diagnostic framework for storing therein the logged CAN bus information.
- a development of the invention provides that the at least one configured as a CAN-snap module diagnostic module and / or at least one other of the diagnostic modules are configured to analyze the logged CAN bus information in terms of poor behavior or deviation from a good behavior in real time , As a result, error events can be detected, which are previously determined. Functional sequences can be monitored automatically in a targeted manner, in particular for complex processes, in order to determine causes of errors.
- At least one of the diagnostic modules is configured to configure the CAN snap module corresponding to the error event when the error event is detected, the logged CAN bus information and / or an adjustable period of time for logging.
- a vehicle 1 is shown.
- the vehicle 1 includes a plurality of vehicle systems 2-14.
- These vehicle systems 2-14 are configured as engine control unit 2, brake control unit 3, transmission control unit 4, comfort control unit 5, on-board control unit 6, door control unit 7, radio 8, navigation control unit 9, telematics control unit 10, control panel 11, further control units 12, 13 and as gateway 14.
- To the gateway 14 are multiple vehicle data buses 15-19 linked.
- the vehicle data buses 15-19 are designed as CAN drive data bus 15, CAN convenience data bus 16, CAN infotainment data bus 17, CAN combination data bus 18 and as CAN diagnostic data bus 19.
- Connected to the CAN drive data bus 15 are the engine control unit 2, the brake control unit 3, the transmission control unit 4 and the further control unit 12.
- the comfort control unit 5, the on-board power supply control unit 6, the door control unit 7 and the further control unit 13 are connected to the CAN comfort data bus 16.
- the radio 8, the navigation control unit 9 and the telematics control unit 10 are connected to the CAN infotainment data bus 17.
- Connected to the CAN combi data bus 18 is the switchboard 11 comprising a plurality of combination controls and display devices.
- the CAN diagnostic data bus 19 is connected to a vehicle external test device 20.
- a diagnostic framework 21 is provided. Between the diagnostic framework 21 and the individual vehicle data buses 15-19, one or more interfaces are provided in the gateway 14 (not shown). Individual diagnosis modules 22-26 are embedded in the diagnostic framework 21 or set up on the diagnostic framework 21.
- the diagnostic modules 22-26 include a central diagnostic module 22, a system diagnostic module 23, a CAN snap diagnostic module 24, a telemetry data coordination diagnostic module 25, and a test module 26. These diagnostic modules 22-26 perform in-vehicle diagnostics of the vehicle systems 2-14. This means that the individual vehicle systems 2-14 do not include independent diagnostic modules.
- the diagnosis is performed centrally by the diagnostic modules 22-26 in the diagnostic framework 21. As a result, the number of accesses indicated by lines 27 to the vehicle systems 2-13 is significantly reduced in number.
- a diagnosis carried out by the vehicle-external test device 20 is carried out via the diagnostic framework, as indicated by the line 28.
- the dotted lines 29, which indicates classical diagnostic accesses in a prior art embodiment, are not provided in the vehicle 1.
- FIG. 2 is a further schematic representation of a vehicle 30 with a vehicle external test device 31 shown.
- the vehicle 30 includes a diagnostic unit 32 configured as a gateway.
- the diagnostic unit 32 includes a diagnostic framework 33, in which diagnostic modules 34 are integrated.
- vehicle systems 36 are networked as control units via a vehicle data bus.
- the diagnostic unit 32 and the vehicle-external test device 31 are networked with each other via a further vehicle data bus 37.
- the vehicle systems 36 do not include diagnostic modules.
- the diagnosis of the vehicle 30 is performed centrally by the diagnostic modules 34 in the diagnostic framework 33.
- Individual external diagnostic modules 38 of the vehicle-external test device 31 access the central diagnostic framework 33 or the diagnostic modules 34 contained therein via a diagnostic application 39. Direct access of diagnostic modules of the vehicle external test device 31 to the vehicle systems 36 is not provided.
- the diagnostic unit 40 comprises a memory 41 and an operating system software kernel 42.
- the operating system software kernel 42 is set up by an operating system application program interface 43 (API).
- the operating system application program interface 43 is again set up by a diagnostic framework 44, which represents an application program interface.
- the diagnostic framework 44 uses portions of the memory 41. These portions of the memory 41 assigned to the diagnostic framework 44 are considered to be the memory of the diagnostic framework 44.
- the diagnostic framework 44 further employs an interface 45.
- the interface 45 includes a CAN application program interface 46, a CAN software kernel 47 and individual physical CAN interfaces 48.
- the CAN software kernel 47 also employs Bandwidth allocation protocol 49 and an ISO transport protocol 50, which in turn a KWP-2000 protocol 51 touches.
- Diagnostic modules 52-58 are based on diagnostic framework 44.
- the diagnostic modules include a diagnostic module 52 that generates an error list, a CAN snap diagnostic module 53, a test module 54, a system diagnostic module 55, a telemetry data coordination diagnostic module 56, a function-oriented diagnostic module 57, and other diagnostic modules 58.
- Via CAN data bus networking 59 the vehicle systems linked to the diagnostic unit 40.
- a vehicle-external test device 61 is likewise connected to the diagnostic unit 40 via a diagnostic connector 60, data being exchanged by means of the KWP-2000 protocol.
- the off-vehicle testing device 61 includes a system configuration coordinator 62, which is based on a communication coordinator 63.
- the communication coordinator can access adapters 64 which access the diagnostic connector 60 or other transport protocols 67, including, for example, the TCP / IP protocol.
- Fig. 4 Based on Fig. 4 will be explained how the CAN snap diagnostic module 53 after Fig. 3 Data of a CAN data bus is logged.
- the binary signals "terminal 15", “terminal 50" and “KD-bit brake” are then plotted against time in each case. Underneath, the battery voltage and the speed are shown as graphs versus time.
- the CAN snap module in this embodiment is configured to extract information concerning these listed signals from the data packets transmitted over the CAN data bus.
- the individual signal values that are determined are each assigned a time stamp.
- These data are stored in a memory. This may be a volatile memory for a timely evaluation or other storage medium in which the data is stored for a time-delayed diagnosis.
- the graphs displayed can be produced from the data. Shown are the waveforms for a rolling a vehicle in front of a closed barrier.
- the motor is switched off, which is indicated by a drop in the terminal 15 signal.
- the terminal 15 is closed again and then the terminal 50 is closed (time C), causing a start of the engine.
- the battery voltage signal 70 the battery voltage at time B decreases with the turning on of the terminal 15 (switching on the ignition). An even greater voltage drop occurs with the closing of terminal 50 (motor start).
- the battery voltage signal 70 can be used to determine that the battery voltage is below a battery voltage threshold value 74 of 8 V for 250 ms.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Small-Scale Networks (AREA)
- Testing And Monitoring For Control Systems (AREA)
- Control Of Position, Course, Altitude, Or Attitude Of Moving Bodies (AREA)
- Air Bags (AREA)
Abstract
Description
Die Erfindung betrifft eine Vorrichtung in einem Fahrzeug für eine Diagnose durch einen Fahrzeug-Datenbus vernetzter Fahrzeugsysteme, umfassend eine Diagnoseeinheit, die eine Schnittstelle für ein Austauschen von Informationen über den Fahrzeug-Datenbus mit den vernetzten Fahrzeugsystemen umfasst.The invention relates to a device in a vehicle for diagnosis by a vehicle data bus of networked vehicle systems, comprising a diagnostic unit comprising an interface for exchanging information about the vehicle data bus with the networked vehicle systems.
In Fahrzeugen sind einzelne Fahrzeugsysteme, die vorzugsweise Steuergeräte umfassen, durch einen Fahrzeug-Datenbus miteinander vernetzt. Um in dem Fahrzeug eine Diagnose der Fahrzeugsysteme ausführen zu können, ist im Stand der Technik vorgesehen, dass die einzelnen Fahrzeugsysteme jeweils eine Diagnoseeinheit umfassen, die in das jeweilige Steuergerät des Fahrzeugsystems integriert ist. Die Diagnose der einzelnen Fahrzeugsysteme wird von den einzelnen Diagnoseeinheiten in den Fahrzeugsystemen durchgeführt. Dabei ermittelte Fehler werden in einem Fehlerspeicher in den einzelnen Fahrzeugsystemen abgelegt. Über ein fahrzeugexternes Diagnose- und Testgerät, welches mit dem Fahrzeug-Datenbus verknüpft wird, können die einzelnen Diagnoseeinheiten bzw. Fehlerspeicher abgefragt werden. Eine umfassende Analyse des Fahrzeugs als Ganzes ist durch diese Vorgehensweise erschwert. Ferner werden in den einzelnen Diagnoseeinheiten der Fahrzeugsysteme häufig ähnliche Diagnosekapazitäten vorgehalten. Eine solche Diagnosevorrichtung ist beispielsweise in der
Aus der
Die
Der Erfindung liegt die technische Aufgabe zugrunde, eine Vorrichtung für eine Diagnose durch einen Fahrzeug-Datenbus vernetzter Fahrzeugsysteme zu schaffen, bei dem eine zeitgleiche beschleunigte Diagnose mehrerer Fahrzeugsysteme möglich ist und eine Erweiterbarkeit und Anpassung der Diagnosefähigkeiten bei einer Modifikation des Fahrzeugs nach der ursprünglichen Produktion einfach möglich ist.The invention has for its object to provide a device for diagnosis by a vehicle data bus networked vehicle systems in which a simultaneous accelerated diagnosis of multiple vehicle systems is possible and an expandability and adaptation of the diagnostic capabilities in a modification of the vehicle after the original production easy is possible.
Dieses technische Problem wird erfindungsgemäß durch einen Gegenstand mit den Merkmalen des Patentanspruchs 1 gelöst, wobei vorgesehen ist, dass auf die Schnittstelle ein Diagnoseframework aufsetzt, das eine Anwendungsprogramm-Schnittstelle (API) für Diagnosemodule bereitstellt, die zum Ausführen der fahrzeuginternen Diagnose der einzelnen Fahrzeugsysteme ausgestaltet sind, wobei mehrere Diagnosemodule zeitgleich parallel auf dem Diagnoseframework ausgeführt werden und das Diagnoseframework einen Zugriff der Diagnosemodule auf die Fahrzeugsysteme koordiniert. Hierdurch wird es möglich, mehrere Fahrzeugsysteme parallel zu analysieren. Bei der zunehmenden Vernetzung von Fahrzeugsystemen und einer starken Zunahme der elektrischen und elektronischen Fahrzeugsysteme ist eine schnelle und zeitnahe Diagnose mehrerer Fahrzeugsysteme notwendig. Indem der Zugriff auf die Fahrzeugsysteme durch das Diagnoseframework koordiniert wird, kann die Anzahl der Zugriffe auf den Fahrzeug-Datenbus minimiert werden.This technical problem is solved according to the invention by an article having the features of
Dabei werden einzelne übermittelte Daten der Fahrzeugsysteme zentral im Diagnoseframework vorgehalten, da diese häufig von mehreren Diagnosemodulen benötigt werden. Das Diagnoseframework hält einen Teil der von den Fahrzeugsystemen übermittelten Daten in einem Speicherbereich vor, um die Anzahl der Zugriffe der Diagnosemodule auf die Fahrzeugsysteme zu verringern.In this case, individual transmitted data of the vehicle systems are held centrally in the diagnostic framework, since they are often required by several diagnostic modules. The diagnostic framework keeps part of the data transmitted by the vehicle systems in a memory area in order to reduce the number of accesses of the diagnostic modules to the vehicle systems.
Als besonders vorteilhaft hat sich eine Ausführungsform erwiesen, bei der das Diagnoseframework einen zentralen Fehlerspeicher umfasst, in dem die Fehlerereignisse der vernetzten Fahrzeugsysteme gemeinsam abgelegt sind. Bei einer Diagnose, bei der mehrere Einzelsysteme gemeinsam diagnostiziert werden, kann somit auf einfache Weise ein Überblick über aufgetretene Fehlerereignisse erhalten werden.An embodiment in which the diagnostic framework comprises a central fault memory in which the fault events of the networked vehicle systems are stored together has proven to be particularly advantageous. In the case of a diagnosis in which several individual systems are diagnosed together, an overview of fault events that have occurred can thus be obtained in a simple manner.
In modernen Fahrzeugen werden die bei der fahrzeuginternen Diagnose ermittelten Ergebnisse ebenfalls für die Wartung und Reparatur der Fahrzeuge verwendet. Es ist daher üblich, fahrzeugexterne Testgeräte mit dem Fahrzeug zu koppeln, um die internen Diagnoseergebnisse auszulesen bzw. gezielt Diagnoseschritte an den Fahrzeugsystemen vornehmen zu lassen und/oder auszuführen. Eine bevorzugte Ausführungsform sieht daher vor, dass die Diagnoseeinheit über den Fahrzeug-Datenbus oder über eine weitere Schnittstelle mit einem fahrzeugexternen Testgerät verknüpfbar ist, wobei ein Datenaustausch zwischen dem fahrzeugexternen Testgerät und den Diagnosemodulen oder den Fahrzeugsystemen über das Diagnoseframework erfolgt. Dies bietet den Vorteil, dass das Diagnoseframework eine einheitliche Schnittstelle für einen Zugriff eines externen Testgeräts bereitstellen kann. Somit können unterschiedliche Fahrzeuge mit ein und demselben externen Testgerät zusammenwirken. Es ist lediglich erforderlich, die einzelnen Diagnoseframeworks der unterschiedlichen Fahrzeuge an die darin verbauten Fahrzeugsysteme anzupassen. Die Diagnosemodule, die in die Anwendungsprogramm-Schnittstelle des Diagnoseframeworks eingepasst sind, können ebenfalls universell verwendet werden. Bei einer externen Diagnose wird durch das vorgeschlagene Vorgehen erreicht, dass die bereits durch die fahrzeuginterne Diagnose ermittelten Ergebnisse besonders einfach und schnell erfasst werden können. Ist beispielsweise ein Speicherbereich für die gemeinsame Ablage der Fehlerereignisse der Fahrzeugsysteme vorgesehen, so können diese Fehlerereignisse schnell zu dem externen Testgerät über das Diagnoseframework übertragen werden, ohne dass Zugriffe über den Fahrzeug-Datenbus auf die einzelnen Fahrzeugsysteme notwendig sind. Hierdurch wird die Fahrzeugdiagnose mit einem externen Testgerät beschleunigt.In modern vehicles, the results obtained during in-vehicle diagnostics are also used for vehicle maintenance and repair. It is therefore customary to couple vehicle-external test devices with the vehicle in order to read out the internal diagnostic results or to have specific diagnostic steps carried out on the vehicle systems and / or executed. A preferred embodiment therefore provides in that the diagnostic unit can be linked via the vehicle data bus or via a further interface with a vehicle-external test device, data being exchanged between the vehicle-external test device and the diagnostic modules or the vehicle systems via the diagnostic framework. This offers the advantage that the diagnostic framework can provide a uniform interface for access by an external test device. Thus, different vehicles can interact with one and the same external test device. It is only necessary to adapt the individual diagnostic frameworks of the different vehicles to the vehicle systems installed therein. The diagnostic modules, which are fitted in the application program interface of the diagnostic framework, can also be used universally. In the case of an external diagnosis, the proposed procedure ensures that the results already determined by the in-vehicle diagnosis can be detected particularly easily and quickly. If, for example, a memory area is provided for the common storage of the fault events of the vehicle systems, then these fault events can be transmitted quickly to the external test device via the diagnostic framework without the need for access to the individual vehicle systems via the vehicle data bus. This speeds up vehicle diagnostics with an external test device.
Das Diagnoseframework ist vorteilhafterweise so ausgestaltet, dass den Diagnosemodulen Diagnosefunktionen und/oder Diagnoseroutinen und/oder Speicher und/oder Rechenkapazität zentral bereitgestellt werden. Hierbei können Diagnoseroutinen oder auch Speicherbereiche von mehreren Diagnosemodulen gemeinsam genutzt werden. Hierdurch wird die benötigte Speicher- und Rechenkapazität im Fahrzeug verringert. Die einzelnen Fahrzeugsysteme müssen nicht mehr dafür ausgelegt sein, selbstständig Diagnosefunktionen ausführen zu können. Hierdurch werden die einzelnen Fahrzeugsysteme einfacher und billiger. Das vorgeschlagene Vorgehen zeichnet sich ferner dadurch aus, dass nach einer Fertigstellung des Fahrzeugs die Diagnosefunktionalität erweitert und/oder verändert werden kann. Hierbei ist es nicht erforderlich, die einzelnen Fahrzeugsysteme zu modifizieren, was sehr aufwendig ist. Es ist vielmehr ausreichend, einzelne oder alle Diagnosemodule zu modifizieren, auszutauschen oder ein neues oder mehrere neue Diagnosemodule der Diagnoseeinheit zuzufügen. Insbesondere bei einer hohen Vernetzung der Fahrzeugsysteme, die gemeinsam Fahrzeugfunktionen zur Verfügung stellen, ist dies vorteilhaft oder erforderlich. Eine funktionsorientierte Diagnose ist in der Regel mit Diagnosemodulen, die in die einzelnen Fahrzeugsysteme integriert sind, nur unbefriedigend oder gar nicht möglich. Insbesondere bei einer funktionsorientierten Diagnose werden viele Daten und Informationen der einzelnen Fahrzeugsysteme von mehreren Funktionsdiagnosen benötigt. Indem die Diagnosemodule in das Diagnoseframework eingebettet sind, wird erreicht, dass das Diagnoseframework diese Daten zentral vorhalten kann, so dass die Anzahl der Zugriffe auf die Fahrzeugsysteme und eine Belastung des Fahrzeug-Datenbusses deutlich verringert wird.The diagnostic framework is advantageously designed such that diagnostic functions and / or diagnostic routines and / or memory and / or computing capacity are provided centrally to the diagnostic modules. Here, diagnostic routines or memory areas of several diagnostic modules can be shared. This reduces the required storage and computing capacity in the vehicle. The individual vehicle systems no longer have to be designed to carry out diagnostic functions on their own. This makes the individual vehicle systems easier and cheaper. The proposed procedure is further characterized in that after completion of the vehicle, the diagnostic functionality can be extended and / or changed. It is not necessary to modify the individual vehicle systems, which is very expensive. Rather, it is sufficient to modify or replace individual or all diagnostic modules, or to add a new or several new diagnostic modules to the diagnostic unit. This is advantageous or necessary, in particular in the case of a high level of networking of the vehicle systems, which together provide vehicle functions. A function-oriented diagnosis is usually unsatisfactory or even impossible with diagnostic modules that are integrated in the individual vehicle systems. Especially with a function-oriented diagnosis, many data and information of the individual vehicle systems of several functional diagnoses needed. By embedding the diagnostic modules in the diagnostic framework, it is achieved that the diagnostic framework can maintain this data centrally, so that the number of accesses to the vehicle systems and a load on the vehicle data bus is significantly reduced.
Die Fahrzeugsysteme umfassen vorzugsweise jeweils mindestens ein Steuergerät. Bei einer besonders bevorzugten Ausführungsform ist die Diagnoseeinheit in ein Steuergerät des Fahrzeugs integriert, vorzugsweise in ein zentrales Multifunktionsanzeigebediensystem.The vehicle systems preferably each comprise at least one control unit. In a particularly preferred embodiment, the diagnostic unit is integrated in a control unit of the vehicle, preferably in a central multi-function display operating system.
Bei einer besonders bevorzugten Ausführungsform ist der Fahrzeug-Datenbus ein CAN-Bus und mindestens eines der Diagnosemodule als CAN-Snap-Modul ausgestaltet, um vorwählbare CAN-Bus-Informationen zu protokollieren. Ein CAN-Snap-Modul ist ein Diagnosemodul, das in der Lage ist, vorausgewählte Daten, die über den Fahrzeug-Datenbus übermittelt werden, zu protokollieren. Hierbei können Vorgaben gemacht werden, welche Daten protokolliert werden sollen. Die protokollierten Daten können in einem Speicher in dem Diagnoseframework abgelegt werden, um für eine spätere Offline-Analyse zur Verfügung zu stehen. Daher ist bei einer bevorzugten Ausführungsform ein Speicher in dem Diagnoseframework vorgesehen, um darin die protokollierten CAN-Bus-Informationen abzulegen.In a particularly preferred embodiment, the vehicle data bus is a CAN bus and at least one of the diagnostic modules designed as a CAN snap module to log preselected CAN bus information. A CAN snap module is a diagnostic module capable of logging preselected data transmitted via the vehicle data bus. Here, specifications can be made as to which data should be logged. The logged data can be stored in a memory in the diagnostic framework to be available for later offline analysis. Therefore, in a preferred embodiment, a memory is provided in the diagnostic framework for storing therein the logged CAN bus information.
Eine Weiterbildung der Erfindung sieht vor, dass das mindestens eine als CAN-Snap-Modul ausgestaltete Diagnosemodul und/oder mindestens ein weiteres der Diagnosemodule ausgestaltet sind, die protokollierten CAN-Bus-Informationen hinsichtlich eines Schlechtverhaltens oder einer Abweichung von einem Gutverhalten in Echtzeit zu analysieren. Hierdurch können Fehlerereignisse detektiert werden, die vorher festgelegt sind. Zur Ermittlung von Fehlerursachen können so gezielt, insbesondere bei komplexen Vorgängen, automatisiert Funktionsabläufe überwacht werden.A development of the invention provides that the at least one configured as a CAN-snap module diagnostic module and / or at least one other of the diagnostic modules are configured to analyze the logged CAN bus information in terms of poor behavior or deviation from a good behavior in real time , As a result, error events can be detected, which are previously determined. Functional sequences can be monitored automatically in a targeted manner, in particular for complex processes, in order to determine causes of errors.
Besonders vorteilhaft ist es daher, bei einer Ausführungsform vorzusehen, dass mindestens eines der Diagnosemodule ausgestaltet ist, bei einem Feststellen eines Fehlerereignisses das CAN-Snap-Modul entsprechend des Fehlerereignisses zu konfigurieren, um die protokollierten CAN-Bus-Informationen und/oder einen einstellbaren Zeitraum für das Protokollieren festzulegen. So werden für eine Offline-Diagnose mit einem fahrzeugexternen Testgerät ausreichend Informationen gesammelt. Hierdurch werden im Betrieb auftretende komplexe Fehlerzusammenhänge für Werkstattpersonal nachvollziehbar und diagnostizierbar.It is therefore particularly advantageous, in one embodiment, to provide that at least one of the diagnostic modules is configured to configure the CAN snap module corresponding to the error event when the error event is detected, the logged CAN bus information and / or an adjustable period of time for logging. Thus, sufficient information is collected for an offline diagnosis with a vehicle-external test device. As a result, complex error relationships that occur during operation can be traced and diagnosed by workshop personnel.
Die Erfindung wird nachfolgend anhand bevorzugter Ausführungsbeispiele unter Bezugnahme auf Figuren näher erläutert. Hierbei zeigen:
- Fig. 1
- eine schematische Ansicht eines Fahrzeugs mit einer Ausführungsform einer Diagnoseeinheit;
- Fig. 2
- eine schematische Darstellung zur Erläuterung der Fahrzeugdiagnose mit einer Diagnoseeinheit, die ein Diagnoseframework umfasst;
- Fig. 3
- eine weitere schematische Ansicht einer Vorrichtung zur Diagnose vernetzter Fahrzeugsysteme; und
- Fig. 4
- eine Darstellung unterschiedlicher Messinformationen, aufgetragen gegen die Zeit, zur Erläuterung des Protokollierens von Signalen mittels eines CAN-Snap-Moduls.
- Fig. 1
- a schematic view of a vehicle with an embodiment of a diagnostic unit;
- Fig. 2
- a schematic representation for explaining the vehicle diagnosis with a diagnostic unit, which includes a diagnostic framework;
- Fig. 3
- a further schematic view of a device for diagnosing networked vehicle systems; and
- Fig. 4
- a representation of different measurement information plotted against time to explain the logging of signals using a CAN snap module.
In
In
In
Anhand von
- 11
- Fahrzeugvehicle
- 22
- als Motorsteuergerät ausgestaltetes Fahrzeugsystemdesigned as an engine control unit vehicle system
- 33
- als Bremsensteuergerät ausgestaltetes Fahrzeugsystemdesigned as a brake control unit vehicle system
- 44
- als Getriebesteuergerät ausgestaltetes Fahrzeugsystemdesigned as a transmission control unit vehicle system
- 55
- als Komfortsteuergerät ausgestaltetes Fahrzeugsystemdesigned as a comfort control device vehicle system
- 66
- als Bremsensteuergerät ausgestaltetes Fahrzeugsystemdesigned as a brake control unit vehicle system
- 77
- als Türsteuergerät ausgestaltetes Fahrzeugsystemas a door control device designed vehicle system
- 88th
- Radioradio
- 99
- als Navigationssteuergerät ausgestaltetes Fahrzeugsystemdesigned as a navigation control unit vehicle system
- 1010
- als Telematiksteuergerät ausgestaltetes Fahrzeugsystemas a telematics control unit designed vehicle system
- 1111
- SchalttafelSwitchboard
- 12, 1312, 13
- als weitere Steuergeräte ausgestaltete Fahrzeugsystemevehicle systems configured as further control devices
- 1414
- als Gateway ausgestaltetes Fahrzeugsystemdesigned as a gateway vehicle system
- 1515
- CAN-Antriebs-DatenbusCAN drive data bus
- 1616
- CAN-Komfort-DatenbusConvenience CAN data bus
- 1717
- CAN-Infotainment-DatenbusInfotainment CAN data bus
- 1818
- CAN-Kombi-DatenbusCAN Combined bus
- 1919
- CAN-Diagnose-DatenbusCAN diagnostic data
- 2020
- fahrzeuginternes TestgerätIn-vehicle test device
- 2121
- Diagnoseframeworkdiagnostic Framework
- 2222
- ZentraldiagnosemodulCentral diagnostic module
- 2323
- SystemdiagnosemodulSystem diagnostic module
- 2424
- CAN-Snap-DiagnosemodulCAN snap-diagnostic module
- 2525
- TelemetriedatenkoordinierungsdiagnosemodulTelemetry data coordinating diagnostic module
- 2626
- Prüfmodultest module
- 2727
- Linie, die Zugriffe des Diagnoseframeworks auf Fahrzeugsysteme andeutetLine that implies requests of the diagnostic framework on vehicle systems
- 2828
- Linie, die Zugriffe des externen Testgeräts auf die fahrzeuginterne Diagnose andeutetLine indicating accesses of the external test device to the in-vehicle diagnostic
- 2929
- Linie, die Diagnosezugriffe nach dem Stand der Technik andeutetLine that indicates diagnostic accesses in the prior art
- 3030
- Fahrzeugvehicle
- 3131
- fahrzeugexternes Testgerätvehicle external test device
- 3232
- Diagnoseeinheitdiagnostic unit
- 3333
- Diagnoseframeworkdiagnostic Framework
- 3434
- Diagnosemodulediagnostic modules
- 3535
- Fahrzeug-DatenbusVehicle data bus
- 3636
- Fahrzeugsystemevehicle systems
- 3737
- weiterer Fahrzeug-Datenbusanother vehicle data bus
- 3838
- externe Diagnosemoduleexternal diagnostic modules
- 3939
- Diagnoseapplikationdiagnostic application
- 4040
- Diagnoseeinheitdiagnostic unit
- 4141
- SpeicherStorage
- 4242
- BetriebssystemsoftwarekernOperating system software core
- 4343
- Betriebssystem-Anwendungsprogramm-Schnittstelle (BS-API)Operating system application program interface (BS API)
- 4444
- Diagnoseframeworkdiagnostic Framework
- 4545
- Schnittstelleinterface
- 4646
- CAN-Anwendungsprogramm-Schnittstelle (CAN-API)CAN application program interface (CAN API)
- 4747
- CAN-SoftwarekernCAN software core
- 4848
- physikalische CAN-Schnittstellenphysical CAN interfaces
- 4949
- Bandwidth-Allocation-ProtocolBandwidth Allocation Protocol
- 5050
- ISO-TransportprotokollISO transport protocol
- 5151
- KWP2000-ProtokollKWP2000 protocol
- 5252
- Diagnosemoduldiagnostic module
- 5353
- CAN-Snap-DiagnosemodulCAN snap-diagnostic module
- 5454
- PrüfdiagnosemodulPrüfdiagnosemodul
- 5555
- SystemdiagnosemodulSystem diagnostic module
- 5656
- TelemetriedatenkoordinierungsdiagnosemodulTelemetry data coordinating diagnostic module
- 5757
- funktionsorientiertes Diagnosemodulfunction-oriented diagnostic module
- 5858
- weitere Diagnosemodulefurther diagnostic modules
- 5959
- CAN-Datenbusvernetzung im FahrzeugCAN data bus networking in the vehicle
- 6060
- Diagnosesteckerdiagnostic connector
- 6161
- fahrzeugexternes Testgerätvehicle external test device
- 6262
- Systemkonfigurationskoordinator (SKK)System Configuration Coordinator (SKK)
- 6363
- Kommunikationskoordinatorcommunications coordinator
- 6464
- Adapteradapter
- 6565
- Kommunikationsprotokollecommunication protocols
- 7272
- Betriebsspannungoperating voltage
- 7474
- BatteriespannungsschwellenwertBattery voltage threshold
- A-CA-C
- Zeitpunktetimings
Claims (13)
- Device with a diagnostic functionality in a vehicle (1) for diagnostics by means of a vehicle data bus (15-18; 35) of networked vehicle systems (2-13; 36), comprising a diagnostic unit (32; 40) which comprises an interface (45) for exchanging information via the vehicle data bus (15-18; 35),
characterized in that
the diagnostic unit comprises a plurality of diagnostic modules (22-26; 34; 52-58) which are designed to carry out vehicle-internal diagnosis of the individual vehicle systems (2-13; 36), and a diagnostic framework (21; 33; 44), which makes available an application program interface (API) for the plurality of diagnostic modules (22-26; 34; 52-58), is based on the interface (45), wherein the plurality of diagnostic modules (22-26; 34; 52-58) are implemented simultaneously in parallel on the diagnostic framework (21; 33; 44), and the diagnostic framework (21; 33; 44) coordinates access by the diagnostic modules (22-26; 34; 52-58) to the vehicle systems (2-13; 36), wherein the diagnostic framework (21; 33; 44) stores part of the data transmitted by the vehicle systems (2-13; 36) in a memory area in order to reduce the number of access operations by the diagnostic modules (22-26; 34; 52-58) to the vehicle systems (2-13; 36). - Device according to Claim 1, characterized in that at least one of the diagnostic modules (22-26; 34; 52-58) is designed to analyse the vehicle systems (2-13; 36) in a way which is oriented towards vehicle functions.
- Device according to one of the preceding claims, characterized in that the diagnostic framework (21; 33; 44) comprises a central fault event memory in which fault events of the networked vehicle systems (2-13; 36) are stored together.
- Device according to one of the preceding claims, characterized in that the diagnostic unit (32; 40) can be linked to the vehicle-external test device (20; 3; 61) via the vehicle data bus or via a further interface (19), wherein data is exchanged between the vehicle-external test device (20; 3; 61) and the diagnostic modules (22-26; 34; 52-58) or the vehicle systems (2-13; 36) via the diagnostic framework (21; 33; 44).
- Device according to one of the preceding claims, characterized in that the diagnostic framework (21; 33; 44) makes available diagnostic functions and/or diagnostic routines and/or memory (41) and/or computing capacity to the diagnostic modules (22-26; 34; 52-58) on a central basis.
- Device according to one of the preceding claims, characterized in that the same function, resource and/or diagnostic routine can be used by at least two of the diagnostic modules (22-26; 34; 52-58).
- Device according to one of the preceding claims, characterized in that the diagnostic modules (22-26; 34; 52-58) exchange data and/or information about the diagnostic framework (21; 33; 44) with one another.
- Device according to one of the preceding claims, characterized in that the vehicle systems (2-13; 36) comprise control units.
- Device according to one of the preceding claims, characterized in that the diagnostic framework (21; 33; 44) is integrated into a control unit of one of the vehicle systems which is advantageously a multifunction display operator control device.
- Device according to one of the preceding claims, characterized in that the vehicle data bus (15-18; 35) is a CAN bus, and at least one of the diagnostic modules (22-26; 34; 52-58) is designed as a CAN snap module (24; 53) in order to log preselectable CAN bus information.
- Device according to one of the preceding claims, characterized in that a memory is provided in the diagnostic framework (21; 33; 44) in order to store the logged CAN bus information in it.
- Device according to one of the preceding claims, characterized in that the at least one diagnostic module which is designed as a CAN snap module (24; 53) and/or at least one further diagnostic module (22-26; 34; 52-58) are designed to analyse the logged CAN bus information in real time, in particular with respect to poor behaviour and/or deviation from good behaviour.
- Device according to one of the preceding claims, characterized in that at least one of the diagnostic modules (22-26; 34; 52-58) is designed, when a fault event is detected, to configure the CAN snap module (24; 53) in accordance with the fault event in order to define the data and/or signals which are to be logged.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102005058380 | 2005-12-06 | ||
DE102006009583A DE102006009583A1 (en) | 2005-12-06 | 2006-02-28 | Diagnostic device in a vehicle with diagnosis framework for diagnostic modules |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1796051A1 EP1796051A1 (en) | 2007-06-13 |
EP1796051B1 true EP1796051B1 (en) | 2009-02-11 |
Family
ID=37891739
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06090235A Not-in-force EP1796051B1 (en) | 2005-12-06 | 2006-11-27 | Diagnostics devices in a vehicle with diagnostics framework for diagnostics module |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1796051B1 (en) |
AT (1) | ATE422694T1 (en) |
DE (2) | DE102006009583A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102010015132A1 (en) | 2010-04-16 | 2011-10-20 | Volkswagen Ag | Method for acquiring data of vehicle for e.g. police investigation, for customer service to plan workshop, involves collecting data from vehicle system of vehicle by module based on conditions that are based on event of vehicle |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102007048087A1 (en) * | 2007-10-05 | 2009-04-09 | Volkswagen Ag | Testing area determining method for motor vehicle, involves providing interactions of user for executing complete test program, where possible paths of test program and interaction requests for each path are determined by analysis tools |
DE102009053753B4 (en) | 2009-11-18 | 2017-03-30 | Audi Ag | Method for determining the cause of a fault on a motor vehicle |
EP2653350A1 (en) * | 2012-04-18 | 2013-10-23 | Siemens Aktiengesellschaft | Vehicle network |
DE102012011908B4 (en) | 2012-06-15 | 2018-02-22 | Audi Ag | Diagnostic system for a motor vehicle and method for operating such a diagnostic system |
CN102890502B (en) * | 2012-09-26 | 2016-07-06 | 芜湖伯特利汽车安全系统股份有限公司 | A kind of anti-lock braking system controller off-line test device and detection method |
DE102013004070B3 (en) * | 2013-03-11 | 2014-08-14 | Audi Ag | Method for checking network for transferring data between power supply takers in motor car, involves detecting signal by operational network nodes, and issuing init message and lock message on diagnostic lines by diagnosis control device |
DE102014207282A1 (en) | 2014-04-16 | 2015-10-22 | Volkswagen Aktiengesellschaft | Method for diagnosing a motor vehicle system, diagnostic device for a motor vehicle system, control device for a motor vehicle system and motor vehicle |
DE102015002574B4 (en) | 2015-02-27 | 2018-06-21 | Audi Ag | Motor vehicle communication network with switch device |
SE541395C2 (en) | 2017-12-27 | 2019-09-10 | Scania Cv Ab | Method and control unit for facilitating diagnosis for a vehicle |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5671141A (en) * | 1993-04-05 | 1997-09-23 | Ford Global Technologies, Inc. | Computer program architecture for onboard vehicle diagnostic system |
DE19731116A1 (en) * | 1997-07-19 | 1999-01-28 | Bosch Gmbh Robert | Control device for automobile engine or drive transmission |
DE19836126A1 (en) * | 1998-08-10 | 2000-02-24 | Siemens Ag | Controller especially for motor vehicle |
DE19841267C1 (en) * | 1998-09-09 | 2000-03-02 | Siemens Ag | Process to implement error diagnostics with diagnostics modules monitoring subsystems in vehicle |
DE10000922A1 (en) * | 2000-01-12 | 2001-07-19 | Volkswagen Ag | Electronic system |
US6954689B2 (en) * | 2001-03-16 | 2005-10-11 | Cnh America Llc | Method and apparatus for monitoring work vehicles |
DE10145906A1 (en) * | 2001-09-18 | 2003-04-10 | Bosch Gmbh Robert | Method for carrying out remote diagnosis in a motor vehicle, vehicle diagnosis module and service center |
EP1516292B1 (en) * | 2002-06-10 | 2005-12-07 | Robert Bosch Gmbh | Method and device for a vehicle-related telematics service |
DE10307344B4 (en) * | 2003-02-21 | 2005-09-29 | Volkswagen Ag | Device and method for decentralized on-board diagnostics for motor vehicles |
WO2004087468A1 (en) * | 2003-04-01 | 2004-10-14 | Robert Bosch Gmbh | Control unit for a restraint system |
US7584029B2 (en) * | 2003-12-31 | 2009-09-01 | Teradyne, Inc. | Telematics-based vehicle data acquisition architecture |
DE102004008816A1 (en) * | 2004-02-20 | 2005-09-08 | Volkswagen Ag | Information exchange method for vehicle original information in which a vehicle application program interface is used to make information such as a commands, routines or macros available to internal or external applications |
-
2006
- 2006-02-28 DE DE102006009583A patent/DE102006009583A1/en not_active Withdrawn
- 2006-11-27 EP EP06090235A patent/EP1796051B1/en not_active Not-in-force
- 2006-11-27 AT AT06090235T patent/ATE422694T1/en not_active IP Right Cessation
- 2006-11-27 DE DE502006002803T patent/DE502006002803D1/en active Active
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102010015132A1 (en) | 2010-04-16 | 2011-10-20 | Volkswagen Ag | Method for acquiring data of vehicle for e.g. police investigation, for customer service to plan workshop, involves collecting data from vehicle system of vehicle by module based on conditions that are based on event of vehicle |
DE102010015132B4 (en) | 2010-04-16 | 2024-04-18 | Volkswagen Ag | Data collection method and data collection device for a vehicle |
Also Published As
Publication number | Publication date |
---|---|
DE102006009583A1 (en) | 2007-06-14 |
ATE422694T1 (en) | 2009-02-15 |
EP1796051A1 (en) | 2007-06-13 |
DE502006002803D1 (en) | 2009-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1796051B1 (en) | Diagnostics devices in a vehicle with diagnostics framework for diagnostics module | |
DE102008015352B4 (en) | Method for recording data and data recording system | |
EP1597643B1 (en) | Device and method for on-board diagnosis based on a model | |
EP1442277A1 (en) | Method for carrying out a telediagnosis on a motor vehicle, vehicle diagnosis module and service center | |
DE102005044236B4 (en) | diagnostic device | |
DE4203704C2 (en) | Method for initializing an electronic control system, particularly in a motor vehicle | |
DE3810239A1 (en) | Multifunction tester for fault diagnosis | |
DE102015108064B4 (en) | Test system and method for automated testing of at least two simultaneously connected to the test system control units and ECU connection and control unit switching unit for use in such a test system | |
DE102010015132B4 (en) | Data collection method and data collection device for a vehicle | |
EP1315332A2 (en) | Programmable data logger for CAN - systems | |
DE102007040216B4 (en) | System for controlling a rotor drive of an open-end rotor spinning machine | |
EP3074782B1 (en) | Device and method for testing a vehicle battery | |
DE102013002648B3 (en) | Master bus device for a vehicle communication bus of a motor vehicle | |
WO1991002256A1 (en) | Process and device for polling control unit data | |
EP3132322B1 (en) | Method for diagnosing a motor vehicle system, diagnostic device for a motor vehicle system, control device for a motor vehicle system, and motor vehicle | |
DE102015003211A1 (en) | Arrangement for diagnosing a motor vehicle | |
DE102014002723A1 (en) | Diagnostic system for motor vehicles | |
EP2653350A1 (en) | Vehicle network | |
DE10121587A1 (en) | Automatic testing of the performance characteristics of a CAN control system comprises a relay matrix connected to a noise generator to provide test input signals | |
DE102012015783A1 (en) | Method for diagnosing several vehicle components of motor car, involves actuating determined diagnostic unit by control device so that supplementary diagnosis data is provided to assigned vehicle component from diagnostic unit | |
DE102009034379A1 (en) | Procedures for transfer of diagnostic data or customer-related information within data processing unit in motor vehicle, involves carrying out charging of traction battery through cable | |
DE102005031724B4 (en) | Method and device for diagnosing electronic systems of a motor vehicle | |
DE102006027550B3 (en) | Fault diagnosis method for data bus network system in vehicle, involves specifying length of time of secondary operating condition and number of cycles in which system changes between two operating conditions | |
DE102006002495A1 (en) | Data storage method in vehicle, involves transforming information, which represents load condition of vehicle or component of vehicle into two, three, or multi-dimensional load collectives | |
DE102014017339A1 (en) | Method for determining fault conditions in a plurality of control units of a motor vehicle |
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 HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: RUEB, GERNOT Inventor name: BRAITSCHINK, PETER Inventor name: BROSE, HEINO |
|
17P | Request for examination filed |
Effective date: 20071213 |
|
17Q | First examination report despatched |
Effective date: 20080109 |
|
AKX | Designation fees paid |
Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
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 HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D Free format text: LANGUAGE OF EP DOCUMENT: GERMAN |
|
REF | Corresponds to: |
Ref document number: 502006002803 Country of ref document: DE Date of ref document: 20090326 Kind code of ref document: P |
|
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: 20090211 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: 20090211 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: 20090522 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: 20090211 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: 20090211 |
|
NLV1 | Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act | ||
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20090611 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: 20090211 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: 20090511 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: 20090211 |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FD4D |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090211 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: 20090211 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: 20090211 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: 20090211 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: 20090713 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20090211 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: 20090211 |
|
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: 20091112 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20090511 |
|
BERE | Be: lapsed |
Owner name: AUDI A.G. Effective date: 20091130 Owner name: VOLKSWAGEN AG Effective date: 20091130 |
|
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 NON-PAYMENT OF DUE FEES Effective date: 20091130 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: ST Effective date: 20100730 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
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: 20090512 Ref country code: BE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091130 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091130 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT 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: 20090211 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20091127 |
|
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 Effective date: 20090812 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20101127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20101130 Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20101130 |
|
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: 20090211 |
|
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 FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20090211 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20101127 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20211130 Year of fee payment: 16 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 502006002803 Country of ref document: DE |
|
P01 | Opt-out of the competence of the unified patent court (upc) registered |
Effective date: 20230529 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230601 |