Documenting an incident on board a motor vehicle

Abstract

A procedure (200, 250) for documenting an event on board a motor vehicle (105) comprises steps of recording an event; determining that a context of the event is not determinable; storing the event and an indication of a missing context; and associating an actual context with the stored event when a context has become determinable.

Description

[0001] The present invention relates to the documentation of an event on board a motor vehicle. In particular, the invention relates to the documentation of events in such a way that different events can be correlated with one another.

[0002] A motor vehicle comprises several control units, each of which performs predetermined functions on board the vehicle. If a control unit detects a predetermined event, such as a fault, this can be entered into an error log.

[0003] A fault can be stored together with a context, allowing multiple faults that share the same context to be considered together. For example, faults that precede or accompany an observable malfunction can be analyzed to determine the cause of the malfunction.

[0004] The context can be determined for all control units by a central component on board the vehicle. If the central component is unavailable when a fault is detected, the fault can only be stored without context. This can make it difficult to find a correlation between stored faults.

[0005] One object underlying the invention is to provide a technique for documenting an event in such a way that it can be correlated with another event in an improved manner. The invention solves this problem by means of the subject matter of the independent claims. Subclaims specify preferred embodiments.

[0006] According to a first aspect of the invention, a method for documenting an event on board a motor vehicle comprises steps of detecting an event; determining that a context of the event is undeterminable; storing the event and an indication of a missing context; and associating a current context with the stored event if a context has become determinable.

[0007] By assigning a current context to a past event, the event can be better contextualized with another event. Events for which no context is initially available can be contextualized later to determine correlation between contexts. For example, a phase in which no context is available can last approximately 2.0 seconds.

[0008] The current context can be assigned to all stored events for which there is an indication of a missing context. This allows events to which no current context could be assigned to be collectively assigned the same most recent context. No event is backdated, since the subsequently determined context can only indicate a later, not an earlier, point in time or state than the context that could not be determined when the event occurred or that was valid when the event occurred. This can be important for event analysis.

[0009] Preferably, the current context is saved along with the event. This allows a fully-fledged entry to be created, which can be treated in subsequent analysis, for example, using an analysis program, in the same way as an entry whose context could be determined at the time of occurrence and was saved with the event.

[0010] An event without context can be stored in a first memory. An event for which a valid context can be immediately determined can be stored in a second memory. The first memory can primarily serve development purposes and is also called an information memory. The second memory can primarily serve maintenance or analysis of the vehicle and is also called an error memory. The capacities of the memories can vary.

[0011] In one embodiment, events from only a predetermined past time range are stored in the first memory, while longer-term events are stored in the second memory.

[0012] An event can be stored in the second memory if a context is assigned to it. This allows the information in the second memory to always be kept in a consistent format. By subsequently saving it to the second memory, the information collected there can be completed.

[0013] In one embodiment, the event is moved from the first to the second memory when subsequently provided with a context. The event can subsequently be converted into a format in which it is indistinguishable from a fully context-stored event, allowing it to be removed from the first memory.

[0014] The context preferably includes a system time and / or a mileage of the vehicle. The system time can originate from a local time base, which can optionally be regularly compared with a generally valid time. The system time resolution is typically less than one second and can include a date in addition to a time. The mileage can be determined in meters or kilometers.

[0015] The event can be determined by a first device on board the motor vehicle, while the context can be determined by a second device on board the motor vehicle. The two devices can be different from one another. The second device can provide the determined context to the first device. Furthermore, the devices can be available at different speeds after activation of the motor vehicle. For example, the first device can comprise a display device in the cockpit, which can take over a second to become available after activation. Furthermore, for example, the second device can comprise a control unit for a brake or steering control, which can be available after only approximately 100 ms after activation.If the second device is available while the first is not yet available, no associated context can initially be determined for an event determined by the second device.

[0016] The event may relate to a detected error of a component of the motor vehicle. The error may indicate incorrect or defective function of the component. The component may, for example, comprise a sensor, an actuator, a control device, a bus, or a connection. The component may also comprise a communication device for communicating with an external device, and a failed communication attempt may be interpreted as an error. The external device may, for example, comprise a central location, a cellular network, a satellite navigation system, or a mobile device. In further embodiments, the device may also comprise a system that can be connected to the vehicle via an interface, for example a diagnostic unit, a USB device, a map module, or another device.

[0017] The central location is located outside the vehicle and can be used by multiple vehicles. The central location is typically implemented as a server or service, for example, in a cloud.

[0018] According to a further aspect of the present invention, a control system on board a motor vehicle comprises a first and a second component. The first component can be configured to provide a current context; and the second component can be configured to detect an event. The control system is configured to store an event for which no context can be determined without context. A current context can be assigned to the stored event if a context can be determined.

[0019] One of the components can be configured to fully or partially execute a method described herein. For this purpose, the component can comprise an electronic processing device, embodied, for example, as a programmable microcomputer or microcontroller. The method can be in the form of a computer program product with program code means. The computer program product can also be stored on a computer-readable data carrier. Features or advantages of the method can be transferred to the control system or a device comprised by it, or vice versa.

[0020] The control system preferably comprises one or more memories for storing events. The process of storing, modifying a stored event, or copying or moving an entry between the memories can be performed by any component. The component can in particular comprise the first and / or second component; in a further embodiment, a dedicated memory component can also be provided.

[0021] According to yet another aspect of the present invention, a motor vehicle comprises a control system as described herein. The motor vehicle may, for example, comprise a motorcycle, a passenger car, a truck, or a bus.

[0022] The invention will now be described in more detail with reference to the accompanying drawings, in which: Fig. 1 a system on board a motor vehicle; and Fig. 2 Flow diagrams of two processes illustrated.

[0023] Fig. 1 shows a system 100 on board a motor vehicle 105. For purely exemplary purposes, the motor vehicle 105 is depicted as a passenger car. The system 100 comprises a first component 110 and a second component 115. Furthermore, a first memory 120 and / or a second memory 125 may be provided. The components 110, 115 and, if appropriate, the memories 120 and / or 125 may be communicatively connected to one another via a bus 130. The memories 120, 125 are depicted separately from the component 110; however, one or both memories 120, 125 may also be included in the component 110.

[0024] The first component 110 is configured to determine a context. The context may include a point in time and / or an operating state of the motor vehicle 105. The operating state may, in particular, include a mileage, i.e., a total distance traveled, of the motor vehicle 105. Further information may also be included in the context, for example, an operating parameter of a drive motor or an energy storage device for the drive motor. The operating parameter may, for example, include a rotational speed, a provided torque, and / or an operating temperature. The operating parameter of an electrical energy storage device may include a state of charge, an operating temperature, or a value indicating aging of the energy storage device. Further, by way of example, a hydraulic pressure of a cooling or lubricating fluid or of a working or transmission medium may be stored as an operating parameter.

[0025] In further embodiments, other or further parameters may be included in the context, for example a geographical position of the motor vehicle 105, an ambient temperature or a prevailing weather.

[0026] The first component 110 may comprise a control unit configured, for example, to display operating parameters for a driver of the motor vehicle 105. The operating parameters may, in particular, include a driving speed or a fault condition of a component 110, 115, one of the memories 120, 125, or the bus 130. A corresponding output device for the driver may be located in a clearly visible location in front of a driver's seat, for example, in the area of ​​a steering wheel or in a center console.

[0027] The second component 115 can comprise any other device on board the motor vehicle 105 that can determine and communicate an event. For example, the second component 115 can comprise another control unit; alternatively, however, it can also comprise a sensor, an actuator, or another active component. In an exemplary embodiment, the second component comprises a drive control, a chassis control, or a brake control. Several second components 115 can be provided, which can be installed at different locations on the motor vehicle 105 and each can be assigned a predetermined task.

[0028] The first memory 120 may comprise a short-term information store, the contents of which may be primarily intended for the development or analysis of an immediate fault on board the motor vehicle 105. The second memory 125 may comprise a long-term fault store, in which events and, in particular, faults can be collected for later analysis.

[0029] It should be noted that in another embodiment, an external storage device located outside the motor vehicle 105 may be used. The external storage device may, for example, be provided at a central server or service and configured to store information from a plurality of motor vehicles 105. In this case, the system 100 may include a wireless communication device for communicating with the external location or external storage device.

[0030] If a component 115 on board the motor vehicle 105 detects an event, the event can be assigned a context that applies at the time of the event or its determination. For this purpose, the context can be provided by the first component 110. Different or differently detailed contexts can be determined for different events. The event and the associated context can then be stored in one of the memories 120, 125.

[0031] For example, when the motor vehicle 105 is started up, the components 110, 115 can be transitioned from a switched-off or inactive state to a switched-on or active state. This process can also be called booting. The components 110, 115 can require different amounts of time for this, so that a situation can arise in which the second component 115 is already operating, but the first component 110 has not yet provided any context. Such a situation typically lasts only a few tens of milliseconds to approximately two seconds. However, there is generally no time limit, and the situation can, in principle, last any length of time.

[0032] Should the second component 115 detect an event within this time, for example, a fault in a connected sensor or actuator, the context of the event cannot initially be determined. It is proposed to initially store the event without context in one of the memories 120, 125. As soon as the second component 110 is active and can provide a context, a stored event without context can be modified by assigning it a current context. Preferably, the determined current context is written to the relevant memory 120, 125 together with the event.

[0033] In one embodiment, events with a valid context are always stored in the second memory 125, while an event without a valid context is stored in the first memory 120. If a context is subsequently assigned to the event, the event can be copied or moved to the second memory 125. The context is preferably stored together with the event.

[0034] Fig. Figure 2 shows a flowchart of methods 200, 250 for documenting an event. Methods 200, 250 preferably run concurrently and can also be considered a single, unified method 200.

[0035] In a step 205, an event on board the motor vehicle 105 can be detected. This step is typically performed by a second component 115, but can also be performed by the first component 110. The event can relate to an externally acting quantity, such as an impact or an incoming message. The event can also include the result of a processing operation. Preferably, the event includes the result of a test of a component 110, 115 itself or a connected element for functionality.

[0036] In a step 210, it can be checked whether a context can be determined for the event. It is expected that this is possible in the vast majority of cases. The context can be determined, and the event can be stored together with the context in a step 215. Preferably, both pieces of information are stored in the second memory 125.

[0037] If it is determined in step 210 that a context cannot be determined at the given time, the event can be stored together with a predetermined placeholder in a step 220. The placeholder can occupy as much memory as a context, but does not have to represent a valid value. For example, the context can include a mileage, a date, and / or a time, and the placeholder can include zero or a series of zeros. Alternatively, a negative value can be used, or a predetermined value indicating the missing context. An event to which no context could initially be assigned is preferably stored in the first memory 120.

[0038] In a further embodiment, an indication that the context is not present can also be noted at another location, for example in the event itself or in management information for the event in the memory 120, 125. Steps 205 to 220 can be run through cyclically as long as the motor vehicle 105 is in operation.

[0039] The second method 250 may begin in a step 255, in which it is determined whether a current context can be determined. This is typically the case when the first component 110 is fully operational, i.e., has completed a startup process. If the context cannot be determined, the process may branch back to step 255 immediately or after waiting a predetermined time.

[0040] If a context can be determined, a check can be performed in step 260 to determine whether an event is stored in one of the memories 120, 125 to which no context is assigned. If events for which no context was initially known were stored only in the first memory 120, it may be sufficient to search through this. Continuing the above example, all events stored in the first memory 120 whose context corresponds to the predetermined placeholder can be determined.

[0041] If no event can be determined without a valid context, the second method 250 may end. Preferably, the second method 250 is restarted the next time the motor vehicle 105 is put into operation.

[0042] If one or more entries without a valid context were identified in step 260, a current context can be determined in step 265 and assigned to each of the found entries. For example, the previously assigned placeholder can be overwritten or replaced by the current context.

[0043] Optionally, in a step 270, the specific event may be copied or, more preferably, moved from the first memory 120 to the second memory 125.

[0044] Collected events, each with its associated context, can be correlated with one another to determine a cause in the form of a cause error for a perceivable problem, which can also be referred to as an effect error. For example, an effect error can consist of an unpleasant noise in a specific driving situation. Various cause errors can be considered for this error, such as transmission damage, a chassis problem, or a defective tire. To analyze the effect error, events following an initial event can be evaluated. A possible initial event in this context could include the motor vehicle 105 turning into a curve. Subsequent events could be vibrations in various components. The events retroactively assigned a context can be recognized as subsequent events because their contexts occur after the context of the initial event. Reference symbol 100 systems 105 Motor vehicle 110 first component 115 second component 120 first storage 125 second storage 130 buses 200 first procedure 205 Record event 210 Context determinable? 215 Save event with context 220 Save event with placeholder 250 second procedure 255 Context determinable? 260 saved event with placeholder available? 265 Replace placeholder with current context 270 Copy entry to long-term storage

Claims

[1] Method (200, 250) for documenting an event on board a motor vehicle (105), the method (200, 250) comprising the following steps: - detecting (205) an event; - determining (210) that a context of the event is not determinable; - storing (220) the event and an indication of a missing context; and - Assigning (265) a current context to the stored event when a context has become determinable (255). [2] The method (200, 250) of claim 1, wherein the current context is assigned to all stored events for which there is an indication of a missing context. [3] The method (200, 250) of claim 2, wherein the current context is stored together with the event. [4] The method (200, 250) of any preceding claim, wherein an event is stored in a first memory (120) without context; and the event is stored in a second memory (125) when a context is assigned to it. [5] The method (200, 250) of claim 4, wherein the event is moved from the first (120) to the second memory (125). [6] Method (200, 250) according to one of the preceding claims, wherein the context comprises a system time and / or a mileage of the motor vehicle (105). [7] Method (200, 250) according to one of the preceding claims, wherein the event is determined by a first device (110) on board the motor vehicle (105) and the context is determined by a second device (115) on board the motor vehicle (105). [8] Method (200, 250) according to one of the preceding claims, wherein the event relates to a detected fault of a component (110, 115) of the motor vehicle (105). [9] A control system (100) on board a motor vehicle (105), comprising a first (110) and a second component (115); wherein the first component (110) is configured to provide a current context; and the second component (115) is configured to detect an event; wherein the control system (100) is configured to store an event for which no context can be determined without context; and to assign a current context to the stored event if a context can be determined. [10] Motor vehicle (105) comprising a control system (100) according to claim 9.

Images