EP2104075B1 - Procédé d'enregistrement de données et système d'enregistrement de données - Google Patents
Procédé d'enregistrement de données et système d'enregistrement de données Download PDFInfo
- Publication number
- EP2104075B1 EP2104075B1 EP09003242.6A EP09003242A EP2104075B1 EP 2104075 B1 EP2104075 B1 EP 2104075B1 EP 09003242 A EP09003242 A EP 09003242A EP 2104075 B1 EP2104075 B1 EP 2104075B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- data
- data recording
- trigger condition
- modules
- fulfilled
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims description 22
- 230000015654 memory Effects 0.000 claims description 35
- 238000003860 storage Methods 0.000 claims description 29
- 238000004458 analytical method Methods 0.000 claims description 17
- 238000011156 evaluation Methods 0.000 claims description 5
- 230000001419 dependent effect Effects 0.000 claims description 2
- 238000010276 construction Methods 0.000 claims 2
- 230000000694 effects Effects 0.000 claims 1
- 230000005540 biological transmission Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 6
- 238000012544 monitoring process Methods 0.000 description 5
- 238000013461 design Methods 0.000 description 3
- 238000003745 diagnosis Methods 0.000 description 3
- 230000015572 biosynthetic process Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 1
- 230000002457 bidirectional effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007257 malfunction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
- G07C5/0841—Registering performance data
- G07C5/085—Registering performance data using electronic data carriers
Definitions
- the invention relates to a method for recording data and a data recording system.
- Such a method or data recording system is generally used for recording data which are transmitted between electronic units as bus subscribers of a bus system, wherein such a bus system is formed by a data bus of a motor vehicle. There, the electronic units of control units, with which various vehicle functions are realized or monitored, formed.
- a transmission system is provided as an external unit, which is connected via a bus interface to the data bus of the motor vehicle, which is formed by a CAN bus system.
- the transmission system has a controller with an executable program.
- the transmission system further comprises on the one hand a volatile memory in the form of a RAM (READ and ACCESS MEMORY) and a non-volatile memory in the form of a flash.
- the messages that are exchanged via the data bus of the motor vehicle, read and stored in the volatile memory which is preferably designed as a ring buffer. If the executable program registers a specific trigger event, the overwrite of the volatile Memory stopped to then transfer the contents of the volatile memory in the non-volatile memory.
- the trigger event can be formed from a single feature or from a combination or sequence of features that are transmitted via the data buses.
- Traceability of the bus traffic is achieved on the basis of the nonvolatile data stored in the transmission system in this way, especially if errors occur. On the basis of the non-volatile data stored messages that are exchanged over the data bus can be traced back to determine from which connected to the data bus control unit a faulty message was sent.
- the disadvantage here is that the transmission system must be connected as a separate unit to the data bus of the motor vehicle, which is associated with an additional design effort.
- the DE 103 08 972 A1 relates to a broadband avionics data retrieval system.
- the system includes one or more flight recorders, such as a flight data recorder or a cockpit voice recorder, that stores aircraft operating data received from sensors in the aircraft.
- a flight data acquisition unit coupled to sensors in the aircraft, may provide the aircraft operational data.
- the flight recorders store data during a flight, which in the event of an accident can help investigators determine the cause of the accident.
- the DE 10 2006 056 492 A1 relates to a vehicle electrical system of a motor vehicle with a plurality of control units, which are networked together via at least one data bus.
- a program-controlled operating data processing device is used which receives and processes a multiplicity of the operating data of the motor vehicle detected by the plurality of control devices.
- the DE 195 46 815 A1 concerns a method for operating a control system, in particular a control system of a motor vehicle, with at least two control units connected via a data transmission line, wherein at least one control unit acquires operating parameters and / or parameters and processes them into control parameters and at least partially separates these parameters, operating parameters and / or control parameters Control units are transmitted via the data transmission line. At least part of the detected and / or transmitted via the data transmission line operating parameters or control parameters and the other parameters are stored for later evaluation.
- the DE 199 33 924 A1 relates to a condition monitoring system for propulsion systems, which is based on the microsystem technology and continuously detects essential operating parameters, and then performs a state diagnosis and classification of the drive system.
- a classification of the operating state can be done, for example, by classifying into the classes "normal”, “prewarning” and "alarm".
- the EP 1 040 974 A2 relates to a device for influencing at least a first vehicle size, which describes a first vehicle movement or a first vehicle behavior.
- This device includes error detection and functional monitoring means having storage means in which first data generated in the error detection or function monitoring means is stored.
- the vehicle contains other devices with which at least other vehicle sizes can be influenced.
- second data which respectively exist at earlier times, are continuously stored and, if a predetermined condition is met, successively overwritten by second data, which respectively are present at later times, and in the storage means upon occurrence of a predetermined event stored two data are stored permanently.
- the invention has for its object to provide a method and a data recording system, by means of which with the least possible effort the most secure and comprehensive control of a bus system and connected to this electronic units is possible.
- the method according to the invention serves to record data which is transmitted between electronic units as bus subscribers of a bus system of a motor vehicle, and / or which are internally generated or present in bus subscribers.
- a number of data recording modules are provided, one of which is implemented in an electronics unit. Each data recording module has a ring memory. The design of the data recording modules and their distribution to the electronic units are adapted to their free computing and storage capacities.
- Each data logging module continuously encrypts data of the electronics unit in which it is implemented into a ring buffer. If a trigger condition exists, data of the ring memories of the data recording modules are not stored volatile. This trigger condition occurs when multiple local trigger conditions specified for individual different data recording modules are met. To check whether the or a trigger condition is met, the data recording modules exchange a reserved message with each other via the bus system. In this, a data logger communicates to the other data logger modules if its local trigger condition is met.
- the data can be stored in the form of non-volatile storage of the data.
- the storage of the data may initially take the form of a volatile storage of the data, whereby it is ensured that this data is not overwritten. To be able to save the data these are then read at a later time, in particular before a power cut of the system to an external unit and stored there not volatile.
- a comprehensive diagnostic option is possible when errors occur in the data traffic of the bus system. Since internal data of the bus subscribers are also recorded, a comprehensive diagnosis can also be carried out for them.
- the cause of the occurrence of a fault can be analyzed in a targeted manner by analyzing this stored data.
- the trigger conditions can be selected, for example, such that they are met when specific malfunctions occur, so that then the stored data just include the period in which an error to be analyzed has occurred.
- the stored data then represent a relatively small amount of data to be evaluated with reasonable effort. Since the stored data are closely related to the occurrence of the error due to the specification of the trigger conditions, the cause of the error can be determined with high reliability by evaluating this data ,
- the data recording system for logging messages of the bus system does not form an isolated, external unit which is connected to the bus system in addition to the electronic units. Rather, the data recording system is a distributed system consisting of data recording modules that are implemented in the individual electronic units of the bus system. It exploits the fact that electronic units or control units are designed as special electronic units in a motor vehicle, generally for use in automation systems, so that they still have free computing power. and have storage capacities. According to the functionalities of the data recording modules and their allocation to the electronic unit are adapted to the available there free computing and storage capacities, whereby on the one hand, the computing and storage capacities of the electronic units are optimally used and on the other hand, the functionality of the data recording modules is optimized.
- the inventive design of the data recording system in the form of data recording modules an external unit for logging messages on the bus system is no longer needed, whereby the hardware cost of the data recording system is significantly reduced.
- the distributed data recording system is thus suitable for use in motor vehicles, since additional monitoring units are accepted there due to lack of available space and ultimately also due to additional costs generally only in prototype vehicles, but not in production vehicles.
- the trigger conditions are adapted to the formation of the data recording system as a distributed system such that multiple local trigger conditions, which are predetermined for individual data recording modules, form a trigger condition.
- a local trigger condition is satisfied, for example, when a message of a data recording module or for a particular parameter of the data recording module a certain condition is met.
- a local trigger condition can be defined for all data recording modules or only for a subset of data recording modules.
- the definition of such local trigger conditions preferably takes place in an initialization phase via an external unit, in particular in an analysis unit which is also used for the evaluation of the measured value, that is to say for error analysis. In this case, this external unit must be connected to the bus system only during the initialization phase, but not during its operation.
- the data recording modules exchange a reserved message with one another via the bus system.
- this one data recording module notifies the other data recording module if its local trigger condition is met.
- the trigger condition is fulfilled if the messages contained in the reserved message contain the messages of all the data recording modules that fulfill their local trigger conditions.
- the trigger conditions formed from the local trigger conditions can be optimally adapted to the formation of the data recording modules, whereby it is achieved that the trigger conditions are fulfilled in specific error functions so that data can then be stored selectively at the error times, in order then to use the data Being able to analyze the origins and causes of errors.
- the extent of the data that is stored can advantageously depend on the trigger conditions, whereby the data required for error analysis can be optimally selected for specific error situations.
- the storage of data in particular their non-volatile storage can be flexibly adapted to the conditions of the bus system.
- the storage of the data can be done locally in the memories of the electronic units in which the data recording modules are integrated.
- a powerful electronic unit can be used for central storage of all data.
- an external unit in the form of an analysis unit is advantageously required only for the initialization of the trigger condition and for the evaluation of the stored data. Both functions are time independent of the data logging with the data recording modules and can therefore be performed independently of these at freely selectable times.
- FIG. 1 schematically shows a bus system 1 within a motor vehicle, to which a plurality of control devices 2 are connected, which generally form electronic units and exchange data as bus subscribers via the bus system 1 by sending messages.
- Such a bus system 1 of a motor vehicle may generally also comprise a configuration of a plurality of data buses, typically in motor vehicles CAN buses and LIN buses are used.
- the control units 2 of the motor vehicle form, for example, units for providing or monitoring vehicle functions. Example of this are control devices 2 for the brake, clutch or steering of a motor vehicle.
- bus system 1 is shown greatly simplified and shows a predetermined number of control units 2, which are connected to each other via bus lines 3.
- Each control unit 2 has a bus interface 4 for connection to the bus system 1.
- Such controllers 2 generally form electronic units with at least one computer unit and with storage media for storing data.
- each control unit 2 in addition to at least one volatile memory such as a RAM and at least one non-volatile memory such as a flash or EEPROM. If security-relevant functions are carried out with the control devices 2, they can have a redundant structure in order to achieve the necessary fault-tolerance.
- the control devices 2 which are used in a motor vehicle are generally designed such that they have free computing and storage capacities. .
- control devices 2 These free capacities of the control devices 2 are exploited by implementing data recording modules 5 therein.
- data recording modules 5 integrated in the control unit 2 form components of a distributed data recording system.
- the analysis unit 6 is not permanent, but only at certain times to the Bus system 1 is connected, which is indicated by the dashed lines lead of the analysis unit 6 to the bus system 1.
- the data recording modules 5 implemented in the individual control devices 2 form software modules which use the computing and storage capacities of the respective control device 2.
- each data recording module 5 uses the free capacity of the non-volatile memory of the controller 2, on which it is integrated, to form a ring memory.
- this ring memory continuously data of the associated control unit 2, in particular from this sent or received messages, non-volatile stored.
- the size of the ring memory is adapted to the free storage capacity of the associated control unit 2.
- the individual data recording modules 5 for this purpose are divided in a suitable manner to the control units 2 and specified in terms of their functionality in a suitable manner.
- the logging of messages of the individual control units 2 by the data recording modules 5 implemented therein serves to detect and analyze errors in the individual control units 2 or in the transmission of messages via the bus system 1.
- a data recording module 5 can be implemented in each control device 2. In general, only in a predetermined part of the control units 2 data recording modules 5 can be integrated.
- the operation of the distributed data recording system is such that during operation of the bus system 1, the individual data recording modules 5, the data of the associated control units 2, in particular the transmitted and received messages, read continuously and are written into the ring buffer. If a predefined trigger condition is fulfilled, data of the ring buffer are not stored volatile.
- the non-volatile storage of data can be done locally by the data of the ring buffer of the data recording module 5 are stored in the non-volatile memory of the controller 2 in which this data recording module 5 is implemented.
- a central storage is possible by, for example, the data of the ring memory of all data recording modules 5 are stored in the non-volatile memory of a control unit 2.
- the non-volatile storage of data can be done in the simplest case such that at the time of fulfillment of the trigger condition, the entire contents of a ring memory is stored non-volatile.
- the non-volatile storage can be carried out such that the data of the ring memory from a defined time before the fulfillment of the trigger condition until a defined time after the fulfillment of the trigger condition are transferred to the non-volatile memory.
- the extent of the non-volatile stored data can be dependent on the respective trigger condition.
- the analysis unit 6 is on the bus system 1 connected.
- the trigger conditions are adapted to the distributed structure of the data recording system and are each formed by a number of local trigger conditions for individual data recording modules 5.
- Each local trigger condition for a data recording module 5 defines a setpoint for a particular variable or parameter in the controller 2 itself, in which the data recording module 5 is integrated, or in a message received or transmitted by that controller 2.
- a trigger condition can be defined by the fact that for all or only for a part of the data recording modules 5 local trigger conditions are given.
- this reserved message consists of individual trigger fields for the individual local trigger conditions.
- a trigger field is set if the corresponding local trigger condition is fulfilled.
- the entire trigger condition is fulfilled when all trigger fields are set, that is, when the messages of all the data recording modules 5 that their local trigger conditions are met are contained in the reserved message. If several trigger conditions are specified, a reserved message with a corresponding number of trigger fields can be exchanged for each of these trigger conditions.
- the trigger conditions are generally chosen so that they are adapted to certain types of errors, so that the trigger conditions are met in certain error situations. Further, since the nature and extent of the non-volatile stored data are adapted to the trigger conditions, they provide immediate information about any errors that have occurred in the control units 2 or in the messages sent via the bus system 1.
- the analysis unit 6 can be connected to the bus system 1 of the motor vehicle at a predetermined time. For example, it can be detected while driving a motor vehicle with a counter, how often a trigger condition has been met. If a certain number of trigger conditions has been met, that is, if a certain number of error situations have been detected, a message can be sent to the driver of the motor vehicle be issued that he should visit a workshop. There, the analysis unit 6 is then connected to the bus system 1 of the motor vehicle and it is the non-volatile stored data of the individual data recording modules 5 read and evaluated.
- a defined time reference of messages of different data recording modules 5 can be established by tracing back the time sequence of the sending of messages between the data recording modules 5. For example, a chronological sequence of messages is obtained by analyzing which messages form responses or responses to previous messages. In general, a chronological sequence of messages can be obtained by providing them with unique time stamps. From the non-volatile stored data to a trigger condition results in a complete image of the traffic between the control units 2 in exactly the time range in which the error has occurred. This is because the trigger time corresponds to the time the error occurred and the data is recorded in a time range around this trigger time. This allows a precise analysis of the error that has occurred.
Landscapes
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Testing And Monitoring For Control Systems (AREA)
Claims (13)
- Procédé d'enregistrement de données qui sont transmises entre des unités électroniques sous la forme de participants au bus d'un système de bus d'un véhicule automobile et/ou qui sont générées ou présentes de manière interne dans des participants au bus, un certain nombre de modules d'enregistrement de données (5) étant prévu, dont chaque fois un est implémenté dans une unité électronique, chaque module d'enregistrement de données (5) présentant une mémoire circulaire, la conception des modules d'enregistrement de données (5) ainsi que leurs répartitions sur les unités électroniques étant adaptées à leurs capacités libres de calcul et de mémorisation et chaque module d'enregistrement de données (5) écrivant en continu dans une mémoire circulaire des données de l'unité électronique dans laquelle il est implémenté, et des données des mémoires circulaires des modules d'enregistrement de données (5) étant mémorisées de manière non volatile en présence d'une condition de déclenchement, la condition de déclenchement étant présente lorsque plusieurs conditions de déclenchement locales, qui sont prescrites pour différents modules d'enregistrement de données (5) individuels, sont remplies, et, pour vérifier si la ou une condition de déclenchement est remplie, les modules d'enregistrement de données (5) échangeant entre eux via le système de bus (1) un message réservé dans lequel un module d'enregistrement de données (5) informe les autres modules d'enregistrement de données (5) que sa condition de déclenchement locale est remplie.
- Procédé selon la revendication 1, caractérisé en ce que les modules d'enregistrement de données (5) sont formés de modules logiciels.
- Procédé selon l'une des revendications 1 ou 2, caractérisé en ce qu'une ou plusieurs conditions de déclenchement sont prescrites par une unité externe.
- Procédé selon la revendication 3, caractérisé en ce que l'unité externe est formée par une unité d'analyse (6) pouvant être connectée au système de bus (1), dans laquelle est effectuée une évaluation des données stockées.
- Procédé selon la revendication 4, caractérisé en ce que, pour la prescription des conditions de déclenchement, des conditions de déclenchement locales sont entrées dans les modules d'enregistrement de données (5) par l'unité d'analyse (6).
- Procédé selon l'une des revendications 1 à 5, caractérisé en ce que la condition de déclenchement est remplie lorsque le message réservé contient les informations de tous les modules d'enregistrement de données (5) que leurs conditions de déclenchement locales sont remplies.
- Procédé selon l'une des revendications 1 à 6, caractérisé en ce que toutes les données des mémoires circulaires sont stockées ou que les données stockées en présence de la ou d'une condition de déclenchement dépendent de cette condition de déclenchement.
- Procédé selon l'une des revendications 1 à 7, caractérisé en ce que des données des mémoires circulaires qui se situent dans un intervalle de temps prescrit sont stockées, le début de l'intervalle de temps se situant un temps défini avant l'instant de la condition de déclenchement et la fin de l'intervalle de temps se situant un temps défini après l'instant de la condition de déclenchement.
- Procédé selon l'une des revendications 1 à 8, caractérisé en ce que la mémorisation non volatile de données de la mémoire circulaire d'un module d'enregistrement de données (5) est effectuée localement, une mémoire non volatile de l'unité électronique dans laquelle le module d'enregistrement de données (5) est implémenté étant utilisée pour la mémorisation non volatile des données du module d'enregistrement de données (5).
- Procédé selon la revendication 9, caractérisé en ce que la mémorisation non volatile de données de la mémoire circulaire d'un module d'enregistrement de données (5) est effectuée centralement, en particulier dans une unité électronique.
- Procédé selon l'une des revendications 1 à 10, caractérisé en ce que les données stockées en présence d'une condition de déclenchement sont d'abord mémorisées de manière non volatile et, à un instant ultérieur, mémorisées de manière non volatile, les données stockées étant en particulier transmises à une unité externe pour leur mémorisation non volatile.
- Système d'enregistrement de données pour enregistrer des données qui sont transmises entre des unités électroniques sous la forme de participants au bus d'un système de bus (1) d'un véhicule automobile, dans lequel un certain nombre de modules d'enregistrement de données (5) est prévu, un module d'enregistrement de données (5) étant chaque fois implémenté dans une unité électronique, la conception des modules d'enregistrement de données (5) ainsi que leurs répartitions sur les unités électroniques étant adaptées à leurs capacités libres de calcul et de mémorisation, chaque module d'enregistrement de données (5) présentant une mémoire circulaire dans laquelle il écrit en continu des données de l'unité électronique dans laquelle il est implémenté, et des données des mémoires circulaires des modules d'enregistrement de données (5) étant stockées dans au moins une mémoire non volatile en présence d'une condition de déclenchement, la condition de déclenchement étant présente lorsque plusieurs conditions de déclenchement locales, qui sont prescrites pour différents modules d'enregistrement de données (5) individuels, sont remplies, et, pour vérifier si la ou une condition de déclenchement est remplie, les modules d'enregistrement de données (5) échangeant entre eux via le système de bus (1) un message réservé dans lequel un module d'enregistrement de données (5) informe les autres modules d'enregistrement de données (5) que sa condition de déclenchement locale est remplie.
- Système d'enregistrement de données selon la revendication 12, caractérisé en ce que celui-ci sert à mémoriser des données qui sont transmises via un système de bus (1) d'un véhicule automobile et que les unités électroniques sont des appareils de commande d'un véhicule automobile.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102008015352A DE102008015352B4 (de) | 2008-03-22 | 2008-03-22 | Verfahren zum Aufzeichnen von Daten und Datenaufzeichnungssystem |
Publications (2)
Publication Number | Publication Date |
---|---|
EP2104075A1 EP2104075A1 (fr) | 2009-09-23 |
EP2104075B1 true EP2104075B1 (fr) | 2015-09-09 |
Family
ID=40679372
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP09003242.6A Active EP2104075B1 (fr) | 2008-03-22 | 2009-03-06 | Procédé d'enregistrement de données et système d'enregistrement de données |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2104075B1 (fr) |
DE (1) | DE102008015352B4 (fr) |
ES (1) | ES2548296T3 (fr) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9183679B2 (en) | 2007-05-08 | 2015-11-10 | Smartdrive Systems, Inc. | Distributed vehicle event recorder systems having a portable memory data transfer system |
US9208129B2 (en) | 2006-03-16 | 2015-12-08 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
US9226004B1 (en) | 2005-12-08 | 2015-12-29 | Smartdrive Systems, Inc. | Memory management in event recording systems |
US9402060B2 (en) | 2006-03-16 | 2016-07-26 | Smartdrive Systems, Inc. | Vehicle event recorders with integrated web server |
US9501878B2 (en) | 2013-10-16 | 2016-11-22 | Smartdrive Systems, Inc. | Vehicle event playback apparatus and methods |
US9554080B2 (en) | 2006-11-07 | 2017-01-24 | Smartdrive Systems, Inc. | Power management systems for automotive video event recorders |
US9594371B1 (en) | 2014-02-21 | 2017-03-14 | Smartdrive Systems, Inc. | System and method to detect execution of driving maneuvers |
US9633318B2 (en) | 2005-12-08 | 2017-04-25 | Smartdrive Systems, Inc. | Vehicle event recorder systems |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8989959B2 (en) | 2006-11-07 | 2015-03-24 | Smartdrive Systems, Inc. | Vehicle operator performance history recording, scoring and reporting systems |
US8868288B2 (en) | 2006-11-09 | 2014-10-21 | Smartdrive Systems, Inc. | Vehicle exception event management systems |
DE102012204073A1 (de) * | 2012-03-15 | 2013-09-19 | Siemens Aktiengesellschaft | Spannungsversorgung für einen Bus eines Bussystems sowie Bussystem |
US9728228B2 (en) | 2012-08-10 | 2017-08-08 | Smartdrive Systems, Inc. | Vehicle event playback apparatus and methods |
US9610955B2 (en) | 2013-11-11 | 2017-04-04 | Smartdrive Systems, Inc. | Vehicle fuel consumption monitor and feedback systems |
US9663127B2 (en) | 2014-10-28 | 2017-05-30 | Smartdrive Systems, Inc. | Rail vehicle event detection and recording system |
US9679420B2 (en) | 2015-04-01 | 2017-06-13 | Smartdrive Systems, Inc. | Vehicle event recording system and method |
DE102020108581A1 (de) | 2020-03-27 | 2021-09-30 | Zf Cv Systems Global Gmbh | Datenerfassungsvorrichtung für mobile Vorrichtungen, Verfahren zur Durchführung einer Vorabanalyse bei einer Datenerfassungsvorrichtung, Fahrzeug sowie entsprechend ausgelegtes Computerprogramm |
CN111915763A (zh) * | 2020-07-24 | 2020-11-10 | 东风汽车有限公司 | 一种汽车高级驾驶辅助功能异常信息采集方法及电子设备 |
Family Cites Families (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19546815A1 (de) | 1995-12-15 | 1997-06-19 | Vdo Schindling | Steuersystem mit Datenspeicherung |
DE10015318A1 (de) | 1999-03-31 | 2000-11-16 | Bosch Gmbh Robert | Vorrichtung zur Beeinflussung einer ersten Fahrzeuggröße |
DE19933924A1 (de) | 1999-04-29 | 2000-11-02 | Loher Ag | Mikrosystem zur lokalen Zustandsüberwachung und Zustandsdiagnose von Maschinen, Anlagen und/oder Baugruppen, insbesondere von Antriebssystemen |
US20040027255A1 (en) | 2002-03-01 | 2004-02-12 | Greenbaum Myron H. | Wideband avionics data retrieval system |
DE10360125A1 (de) | 2003-12-20 | 2005-07-21 | Daimlerchrysler Ag | Datenloggin in einem Kraftfahrzeug |
US7296123B2 (en) * | 2005-02-01 | 2007-11-13 | Delphi Technologies, Inc. | Electronic control unit analysis |
DE102006018831A1 (de) * | 2006-04-22 | 2007-10-25 | Daimlerchrysler Ag | Kraftfahrzeugdiagnose und Fahrzeugannahme |
DE102006056492A1 (de) | 2006-11-30 | 2008-06-05 | Bayerische Motoren Werke Ag | Bordnetz mit programmgesteuerter Betriebsdatenverarbeitungs-Vorrichtung |
-
2008
- 2008-03-22 DE DE102008015352A patent/DE102008015352B4/de active Active
-
2009
- 2009-03-06 EP EP09003242.6A patent/EP2104075B1/fr active Active
- 2009-03-06 ES ES09003242.6T patent/ES2548296T3/es active Active
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9226004B1 (en) | 2005-12-08 | 2015-12-29 | Smartdrive Systems, Inc. | Memory management in event recording systems |
US9633318B2 (en) | 2005-12-08 | 2017-04-25 | Smartdrive Systems, Inc. | Vehicle event recorder systems |
US9208129B2 (en) | 2006-03-16 | 2015-12-08 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
US9402060B2 (en) | 2006-03-16 | 2016-07-26 | Smartdrive Systems, Inc. | Vehicle event recorders with integrated web server |
US9472029B2 (en) | 2006-03-16 | 2016-10-18 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
US9545881B2 (en) | 2006-03-16 | 2017-01-17 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
US9566910B2 (en) | 2006-03-16 | 2017-02-14 | Smartdrive Systems, Inc. | Vehicle event recorder systems and networks having integrated cellular wireless communications systems |
US9554080B2 (en) | 2006-11-07 | 2017-01-24 | Smartdrive Systems, Inc. | Power management systems for automotive video event recorders |
US9183679B2 (en) | 2007-05-08 | 2015-11-10 | Smartdrive Systems, Inc. | Distributed vehicle event recorder systems having a portable memory data transfer system |
US9501878B2 (en) | 2013-10-16 | 2016-11-22 | Smartdrive Systems, Inc. | Vehicle event playback apparatus and methods |
US9594371B1 (en) | 2014-02-21 | 2017-03-14 | Smartdrive Systems, Inc. | System and method to detect execution of driving maneuvers |
Also Published As
Publication number | Publication date |
---|---|
DE102008015352B4 (de) | 2013-12-19 |
EP2104075A1 (fr) | 2009-09-23 |
ES2548296T3 (es) | 2015-10-15 |
DE102008015352A1 (de) | 2009-09-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2104075B1 (fr) | Procédé d'enregistrement de données et système d'enregistrement de données | |
DE102005018301B4 (de) | Datenübertragungsvorrichtung | |
DE69505218T2 (de) | Verfahren zur Fehleridentifizierung in einem komplexen System | |
DE4320173C2 (de) | Diagnoseverfahren für Kraftfahrzeuge zum Überprüfen elektronisch gesteuerter Systeme | |
EP1796051B1 (fr) | Dispositifs de diagnostic dans un véhicule doté d'une unité d'informations de diagnostic pour un module de diagnostic | |
DE3810239A1 (de) | Multifunktionstester fuer die fehlerdiagnose | |
DE10307342A1 (de) | Vorrichtung und Verfahren zur modellbasierten On-Board-Diagnose | |
DE102010015132B4 (de) | Datenerhebungsverfahren und Datenerhebungsvorrichtung für ein Fahrzeug | |
WO2009103387A1 (fr) | Procédé d’enregistrement de données de diagnostic dans un véhicule automobile au moyen d’une mémoire en anneau volatile, suivi d’une réduction des données dans une mémoire non volatile | |
DE10157188A1 (de) | Programmierbarer Datenlogger und Klassiergerät für CAN-Systeme | |
WO2008119444A1 (fr) | Système d'enregistrement de données et procédé de collecte de données au moyen d'un système d'enregistrement de données | |
EP0436818B1 (fr) | Système de diagnose pour un dispositif de commande digital | |
DE202006003273U1 (de) | Diagnosevorrichtung in einem Fahrzeug für eine funktionsorientierte Diagnose | |
EP2394400B1 (fr) | Unité de traitement d'état configurable pour systèmes de capteurs/actionneurs | |
DE10029642A1 (de) | Einrichtung zur Überwachung eines datenbusvernetzten Systems, insbesondere eines Fahrzeugdatenbussystems | |
EP2405317B1 (fr) | Procédé de paramétrage assuré sûr d'un appareil | |
DE10307343B4 (de) | On-Board-Diagnosevorrichtung und On-Board-Diagnoseverfahren für Kraftfahrzeuge | |
EP0693726A1 (fr) | Procédé de transmission de données dans un système de traitement de données en temps réel | |
WO2000010838A1 (fr) | Systeme de bus installe dans un vehicule et procede de transmission d'informations | |
DE102008047561A1 (de) | Steuergerätesystem mit dezentraler Datenaufzeichnung und Verfahren zum Protokollieren von Daten | |
EP1117023B1 (fr) | Dispositif de diagnostic de fautes pendant le fonctionnement d'un véhicule automobile | |
DE102016009199B4 (de) | Verfahren zum Betreiben einer Datenerfassungseinheit zum Erfassen von mindestens einem Steuerungsereignis einer Steuerungvorrichtung eines Kraftfahrzeugs sowie eine Datenerfassungseinheit und eine Datenverarbeitungseinheit | |
EP0694451B1 (fr) | Dispositif de sécurité pour véhicule | |
DE102012015783A1 (de) | Diagnoseverfahren und Diagnosesystem für ein Kraftfahrzeug | |
WO2004061405A2 (fr) | Procede et systeme pour analyser des erreurs de blocs electroniques de vehicules et bloc electronique correspondant |
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: 20090904 |
|
17Q | First examination report despatched |
Effective date: 20091002 |
|
AKX | Designation fees paid |
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 |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
INTG | Intention to grant announced |
Effective date: 20150302 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
RBV | Designated contracting states (corrected) |
Designated state(s): AT DE ES FR GB |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: BUEHLER, OLIVER Inventor name: ULMER, DANIEL Inventor name: THEISSLER, ANDREAS |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: STEINBEIS INTERAGIERENDE SYSTEME GMBH |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT DE ES FR GB |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D Free format text: NOT ENGLISH |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: ULMER, DANIEL Inventor name: BUEHLER, OLIVER Inventor name: THEISSLER, ANDREAS |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: REF Ref document number: 748678 Country of ref document: AT Kind code of ref document: T Effective date: 20150915 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R096 Ref document number: 502009011525 Country of ref document: DE Ref country code: ES Ref legal event code: FG2A Ref document number: 2548296 Country of ref document: ES Kind code of ref document: T3 Effective date: 20151015 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 8 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20160312 Year of fee payment: 8 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R097 Ref document number: 502009011525 Country of ref document: DE |
|
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: 20160610 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 9 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 502009011525 Country of ref document: DE |
|
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: 20171003 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 10 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: GB Payment date: 20220113 Year of fee payment: 14 Ref country code: AT Payment date: 20220225 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20220405 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20230123 Year of fee payment: 15 |
|
REG | Reference to a national code |
Ref country code: AT Ref legal event code: MM01 Ref document number: 748678 Country of ref document: AT Kind code of ref document: T Effective date: 20230306 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20230306 |
|
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: 20230306 |
|
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: 20230306 Ref country code: AT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230306 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20240429 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230307 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20230307 |