WO2007038983A1

WO2007038983A1 - Analysis of vehicle diagnostic data stream using a recorded movie of the data stream

Info

Publication number: WO2007038983A1
Application number: PCT/EP2005/054918
Authority: WO
Inventors: Daniel M. Buckley
Original assignee: Snap-On Incorporated
Priority date: 2005-09-29
Filing date: 2005-09-29
Publication date: 2007-04-12

Abstract

A vehicle diagnostic system provides for a recordal of a movie of an incoming data stream. The system comprises a rules storage system configured to store one or more rules, each of which determines whether the vehicle may have an anomaly when applied to the recorded movie. An operator interface may be configured to alert an operator of the diagnostic system to a suspected anomaly in the vehicle based on an analysis of the movie.

Description

ANALYSIS OF VEHICLE DIAGNOSTIC DATA STREAM USING A RECORDED MOVIE OF THE DATA STREAM

BACKGROUND

Field

[0001] This invention relates to vehicle diagnostic equipment, including scantools that analyze data streams, such as data streams that comply with the OBD Il or EOBD data stream specifications. The invention more particularly relates to an analysis of movies of data streams, the movies being defined by sequential data within a data stream, so as to provide trend information on vehicle performance. The analysis of the movie within the context of the present invention is intended to cover both real time analysis (as the movie file is being generated) and offline analysis where a movie is recorded and analysed at a later period in time.

Description of Related Art

[0002] Vehicles, such as automobiles, often include numerous on-board computer systems. Each computer system often operates and tests various aspects of the vehicle, including aspects relating to the engine, anti-lock braking system (ABS), transmission and air bag. The number of on-board computer systems will vary from vehicle to vehicle but it is not intended within the context of the present invention to limit to any one number or numbers of such computers.

[0003] Scantools are diagnostic devices that provide information about vehicles through interrogation of these on-board computer systems. An interrogation may seek one or more individual sensor data readings, such as a throttle, RPM or coolant temperature. Another interrogation may test for the setting of codes by the vehicle, such as a code indicating that there was an emission fault. A still further interrogation may cause the vehicle to perform a particular test and to return the results of that test.

[0004] Scantools often communicate with the vehicle in accordance with an established communication specification, such as the OBD Il or EOBD data stream specification, as will be appreciated by the person skilled in the art. The diagnostic information that is returned from the vehicle may be displayed either in text or graphic format on a display associated with the scantool.

[0005] In order to diagnose a particular problem with the vehicle, the mechanic must often determine which tests to administer and must analyze the diagnostic information that is returned as a result. Some scantools assist the mechanic by allowing the mechanic to program the scantool to begin recording diagnostic information when a particular condition is met, such as when the output of a sensor exceeds a pre-determined value.

[0006] Unfortunately, determining which tests to run and interpreting the diagnostic information that is returned as a result can require a great deal of skill and experience. This can limit the type of personnel that can effectively use these scantools or lead to errors in the assessment of anomalies in the vehicle.

[0007] Furthermore, some conditions are not observable or detectable based on the output of a sensor exceeding one pre-determined value. Such conditions are therefore heretofore undetectable.

SUMMARY

[0008] These and other problems are addressed by a vehicle diagnostic system in accordance with the teachings of the present invention. Such a vehicle diagnostic system may include a rules storage system configured to store one or more rules. Each rule may determine whether a vehicle may have an anomaly when applied to vehicle diagnostic information. An operator interface may be configured to alert an operator of the diagnostic system to a suspected anomaly in the vehicle. A processing system may be configured to receive diagnostic information from the vehicle, generate a movie of that diagnostic information, apply one or more rules in the rules storage system to the movie of the diagnostic information, and cause the operator interface to alert the operator to a suspected anomaly in the vehicle if application of the one or more rules results in a determination that the vehicle may have that anomaly. [0009] The processing system may be configured to deliver a plurality of different types of test requests to the vehicle. Each test request may cause a different type of diagnostic information to be sent by the vehicle to the diagnostic system.

[0010] The rules storage system may be configured to store a relationship between each rule and the type of diagnostic information to which the rule applies. The processing system may be configured to consult the relationships in the rules storage system for the purpose of identifying the rule or rules that should be applied to a particular type of diagnostic information and to only apply the identified rule or rules to that information.

[0011] The vehicle diagnostic system may include a test sets storage system configured to store a plurality of test sets. Each test set may designate a plurality of test requests that are to be sent to the vehicle in response to a single request for the test set.

[0012] The test sets storage system may be configured to store a relationship between each test set and a description of the test set that the operator may select for the purpose of initiating the test set. The processing system may be configured to present a plurality of the descriptions of the test sets to the operator and to implement the test set selected by the operator.

[0013] The processing system may be configured to receive diagnostic information from the vehicle in response to each test request in the selected test set; apply one or more rules in the rules storage system to the diagnostic information provided in response to each test request in the selected test set; and cause the operator interface to alert the operator to each suspected anomaly in the vehicle that application of the one or more rules determines that the vehicle may have.

[0014] The vehicle diagnostic system may include a vehicle interface configured to receive the diagnostic information from the vehicle in the form of a data stream and to deliver the diagnostic information to the processing system. The vehicle interface may be configured to receive a data stream in compliance with the OBD Il or EOBD data stream specifications. [0015] The operator interface may include a display.

[0016] The operator interface may be configured to display at least portions of the diagnostic information and to alert the operator to a suspected anomaly in the vehicle by giving emphasis to a displayed portion of the diagnostic information that is indicative of the suspected anomaly.

[0017] The operator interface may be configured to alert an operator by providing a description of the suspected anomaly.

[0018] The operator interface may be configured to alert an operator by suggesting one or more additional tests to run.

[0019] The rules storage system may contain rules that are not created by the operator of the vehicle diagnostic system. The rules storage system may contain rules that are created by the manufacturer of the vehicle diagnostic system.

[0020] The rules storage system may be configured to store rules that test for an out-of-bound condition, a glitch, a step function, a matching pattern, and/or a logical combination of other rules.

[0021] A vehicle diagnostic system may include a test sets storage system configured to store a plurality of test sets. Each test set may designate a plurality of test requests that are to be sent to a vehicle in response to a single request for the test requests designated by that test set. Each test request may cause a different type of diagnostic information to be sent by the vehicle to the diagnostic system. A processing system may be configured to receive an identification of a selected test set in the test sets storage system, obtain from the test sets storage system the plurality of test requests designated by the selected test set, send the plurality of test requests designated by the selected test set to the vehicle, and receive diagnostic information from the vehicle in response to each communicated test request.

[0022] A vehicle diagnostic process may include sending a test request to a vehicle; receiving diagnostic information from the vehicle in response to the test request; applying one or more rules to the diagnostic information, each rule configured to determine whether the vehicle may have an anomaly; and alerting a technician to a suspected anomaly in the vehicle if the application of one or more rules to the diagnostic information determines that the vehicle may have that anomaly.

[0023] The vehicle diagnostic process may include consulting relationships between rules and types of diagnostic information and applying only the rule or rules to the diagnostic information that have matching relationships to the type of the diagnostic information.

[0024] The vehicle diagnostic process may include sending a plurality of test requests to the vehicle in response to a technician's selection of a set of tests to run from a plurality of test sets; receiving diagnostic information from the vehicle in response to each test request; applying one or more rules to each received diagnostic information, each rule configured to determine whether the vehicle may have an anomaly; and alerting a technician to a suspected anomaly in the vehicle if the application of the one or more rules to any of the diagnostic information determines that the vehicle may have that anomaly.

[0025] The alerting may include giving emphasis to a portion of the diagnostic information that is indicative of the anomaly, providing a description of the anomaly, and/or suggesting one or more additional test to run.

[0026] One or more of the applied rules may test for an out-of bound condition, a glitch, a step function, a matching pattern and/or a logical combination of other rules.

[0027] A vehicle diagnostic process may include selecting a set of tests to run from a list of test sets; obtaining the selected set of tests to run from a test sets storage system; sending a test request for each test in the selected set of tests to a vehicle; and receiving diagnostic information in response to each test request from the vehicle.

[0028] The movie that is generated of the output from the vehicle typically is defined by a sequence of snap-shots before and after some applied trigger point. The triggering may be automatically implemented by a rule or may be externally activated by a user of the system. A movie comprises a plurality of frames, each frame being defined by collection data readings or trouble codes. It will be understood therefore that a movie of a first set of readings may have different frame characteristics to that of a movie of another set of readings- where the first and second set of readings are used in the diagnosis of different problems associated with the vehicle.

[0029] These as well as other objects, features, benefits, components and steps will now become clear from the following detailed description of illustrative embodiments and the accompanying drawings.

BRIEF DESCRIPTION OF DRAWINGS

[0030] FIG. 1 is a block diagram of one embodiment of a vehicle diagnostic system in communication with a vehicle.

[0031] FIG. 2 is a block diagram illustrating examples of the types of rules that may be stored in the rules storage system shown in FIG. 1.

[0032] FIG. 3 is a table illustrating one embodiment of relationships between rules and diagnostic information types that may be stored in the rules storage system shown in FIG. 1.

[0033] FIG. 4 is a table illustrating one embodiment of relationships that may be stored in the test series storage system shown in FIG. 1.

[0034] FIG. 5 is a flow diagram of one embodiment of a process that may be implemented by the vehicle diagnostic system shown in FIG. 1.

[0035] Fig. 6 is a schematic illustrating the formation of a movie in accordance with the teachings of the invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0036] FIG. 1 is a block diagram of one embodiment of a vehicle diagnostic system in communication with a vehicle.

[0037] As shown in FIG. 1 , a vehicle diagnostic system 101 is in communication with a vehicle 103 over a communication link 105. [0038] The vehicle 103 may be any type of vehicle, including a land vehicle, such as an automobile, truck or motorcycle; a flying vehicle, such as an airplane; or a watercraft, such as a ship.

[0039] The vehicle 103 may be equipped with a diagnostic system that provides diagnostic information about the vehicle. This information may be provided in response to requests for the information. Different types of information may be returned in response to different types of requests.

[0040] Requests may be sent relating to different areas or aspects of the vehicle. When the vehicle 103 is an automobile, for example, requests may be sent relating to the engine, the anti-lock braking system (ABS), the transmission, the air bag controller and/or other systems or modules. A request may seek information about an individual sensor, such as a throttle, RPM or coolant temperature. A request may seek information about one or more codes that the vehicle has set, such as an indication that there has been an emission fault. A request may cause a test to be initiated and diagnostic information about the test to be returned.

[0041] The communication with the vehicle may take place using a data stream, such as a data stream that is in compliance with the OBD Il data stream specification.

[0042] The communication link 105 may be a wired link, a wireless link, or a combination of the two. The communication link 105 may comply with the OBD Il data stream specification. The communication link 105 may include one or more connectors for temporarily connecting to the diagnostic system in the vehicle 103, such as a connector in compliance with the OBD Il data stream specification. The communication link 105 may include a connector to connector to a data port in the vehicle.

[0043] The vehicle diagnostic system 101 may include a rules storage system 107. The rules storage system 107 may be configured to store one or more rules. Each rule or combination of rules may determine whether a vehicle may have an anomaly when the rule is applied to diagnostic information from the vehicle. [0044] The vehicle diagnostic system 101 may also include a data store 122 configured to store a movie of the incoming data stream. The term "movie" within the present invention is intended to define a set of data parameters separated only in the time domain. For example at the present moment in time it is known for the data stream to provide a snap shot of the vehicle at a certain instant in time, with that snap shot including information on the status of for example trouble codes and other data parameters. The data store of the present invention stores a time sequence of a plurality of these snap shots so as to define a movie having historical data relating to the status of individual codes over an extended time period. The movie can then be interrogated to ascertain trends or values relative to previous values. The movie that is generated of the output from the vehicle typically is typically defined by a sequence of snap-shots before and after some applied trigger point. The triggering may be automatically implemented by a rule or may be externally activated by a user of the system. A movie therefore may be considered as a set comprising a plurality of frames, each frame being defined by collection data readings and/or trouble codes. It will be understood therefore that a movie of a first set of readings may have different frame characteristics to that of a movie of another set of readings- where the first and second set of readings are used in the diagnosis of different problems associated with the vehicle.

[0045] FIG. 2 is a block diagram illustrating examples of the types of rules that may be stored in the rules storage system 107 shown in FIG. 1. AS shown in FIG. 2, the rules storage system 107 may include out-of-bound rules 201, glitch rules 203, step function rules 205, pattern matching rules 207 and/or logical combination rules 209. Although rules may be defined for specific snap shot effects, and may also be present in the rules storage system, for the purposes of the present invention we are concerned with rules defined for movie interrogation, as the present invention involves the use of such movies to provide historical or extended time frame data that can indicate trends or once off anomalies in vehicle performance. Of course, in the overall diagnostic performed on the vehicle, a full test routine will probably require a combination of snap shot applied rules and movie applied rules. [0046] An out-of-bound rule 201 may test certain types of diagnostic information from the vehicle to determine whether that information exceeds one or more boundaries over a specified time period. For example, a rule may test whether a temperature sensor is generating a signal indicating a temperature in excess of a pre-determined threshold over an extended time period. An out-of-bound rule may test whether diagnostic information falls within a range of values. Equivalently, a test may be performed to ascertain whether diagnostic information falls within several ranges of values. While it may be permissible for a reading to momentarily drift towards un-permitted levels using the movie analysis of the present invention it is possible to provide a level of analysis based on a time domain performance, and although the parameter may not actually hit the un-permitted level, if it spends a continual time near that level and away from its normal base value, i.e. an analysis of the trends visible through an inspection of the movie presents an indication that there is a fault.

[0047] A glitch rule 203 may similarly test a particular type of diagnostic information to determine whether it evidences a problematic glitch. For example, a glitch rule may test whether a parameter has a large excursion and then returns to a base reading within a small number of sample periods of the datastream, possibly indicating an intermittent electrical contact in the sensor or controller. By analyzing a movie sequence such glitches may become more apparent.

[0048] A pattern matching rule 207 may specify one or more patterns against which a particular type of diagnostic information is compared. A pattern matching rule 207 may include criteria that specifies the degree of similarity that is required before a match is declared.

[0049] A logical combination rule 209 may test diagnostic information against a logical combination of two or more rules. The particular rules which are the subject of a logical combination rule 209 may be one of the out-of-bound rules 201, glitch rules 203, step function rules 205 or pattern matching rules 207. It may also be another rule that is not individually accessible. [0050] A logical combination rule 209 may be configured to operate upon a single type of diagnostic information or upon multiple types of diagnostic information, obtained either at the same or at different times.

[0051] FIG. 3 is a table illustrating one embodiment of relationships between rules and diagnostic information types that may be stored in the rules storage system 107 shown in FIG. 1. As shown in FIG. 3, a rules/diagnostic information type table 301 may be included within the rules storage system 107. The table 301 may include a rule column 305 identifying each rule and a diagnostic information type column 307 identifying a type of diagnostic information to which the corresponding rule may be applied.

[0052] As illustrated in FIG. 3, rules 1 and 3, for example, may be applied to diagnostic information type 7, while rule 2 may be applied to diagnostic information type 3 and rule 4 may be applied to diagnostic information type 9. As illustrated in FIG. 3, each rule may only be applied to certain types of diagnostic information. More than one rule may be applied to a single type of diagnostic information.

[0053] Satisfaction of a rule that is stored in the rules storage system 107 may signify either an anomaly with the vehicle or that the aspect of the vehicle to which the rule has been applied is functioning properly. For example, application of an out- of-bound rule to diagnostic information may result in a determination that the diagnostic information falls within the bounds of the rule. Such an in-bounds determination may be specified to be indicative of an anomaly. It may instead be specified to be indicative of proper operation, in which event the failure of the diagnostic information to fall within the bounds might be specified as indicative of the anomaly.

[0054] One or more of the rules that are stored in the rules storage system 107 may be created by a person or group with a high degree of expertise in vehicle diagnostics. This may be a person other than the operator of the vehicle diagnostic system 101. For example, one or more of the rules may be created and/or loaded into the rules storage system 107 by the manufacturer of the vehicle diagnostic system, the distributor of the diagnostic system, the manufacturer of the vehicle, or another expert in the field.

[0055] Referring back to FIG. 1 , the vehicle diagnostic system 101 may include an operator interface 109. The operator interface 109 may facilitate communications between the vehicle diagnostic system 101 and the operator of the system (not shown in FIG. 1).

[0056] The operator interface 109 may be configured to alert an operator of the diagnostic system to a suspected anomaly in the vehicle under test.

[0057] The operator interface 109 may include an output system 111 configured to communicate information from the vehicle diagnostic system 101 to the operator of it. The output system may include a display, a loudspeaker, and/or a communication link with another system.

[0058] When a display is included in the output system 111 , all or a portion of the diagnostic information that is received by the vehicle diagnostic system 101 may be delivered to the display. The operator interface 109 may communicate an alert to a suspected anomaly in the vehicle to the operator by giving emphasis to a portion of the displayed diagnostic information that is indicative of the suspected anomaly. The emphasis may consist of or include flagging or tagging the portion, highlighting the portion, flashing the portion, underlining the portion, and/or application of a different color to the portion.

[0059] The operator interface 109 may also or instead alert an operator of the vehicle diagnostic system 101 to a suspected anomaly by providing a description of the suspected anomaly and/or by suggesting one or more additional tests that may be run.

[0060] The operator interface 109 may include an input system 113 through which the operator may provide information to the vehicle diagnostic system 101, such as requests that certain tests be performed. The input system 103 may include any type of input device, such as a touch screen, keyboard, mouse or communication link with another system. [0061] The vehicle diagnostic system 101 may include a vehicle interface 115. The vehicle interface 115 may be configured to interface the information coming from the vehicle 103 over the communication link 105 to other components in the vehicle diagnostic system 101. The vehicle interface 115 may be configured to facilitate communication both from the vehicle diagnostic system 101 to the vehicle 103 and from the vehicle 103 to the vehicle diagnostic system 101. The vehicle interface 115 may be configured to manage data stream communications, including communications that are in compliance with the OBD Il data stream specification or other data stream standards that are used in vehicle analysis such as the EOBD data stream standard that is in common usage in Europe and which extends to diesel vehicles.

[0062] The vehicle diagnostic system 101 may include a test sets storage system 117.

[0063] FIG. 4 is a table illustrating one embodiment of relationships that may be stored in the test sets storage system 117. As shown in FIG. 4, the test sets storage system 117 may include a test set names table 401. The test set names table 401 may include a test description 403 of sets of tests that may be performed by the vehicle diagnostic system 101 and a corresponding test number 405 for each corresponding set of tests. The test description 403 may describe the set of tests in language that is readily understood by non-expert operators. The corresponding test number 405 for each set of tests may be used as a convenience to avoid redundancy in the descriptions in a test set signals table 407.

[0064] The test set signals table 407 may include the test number 405 of each test set and a test request 407 to which each test number is associated. As can be seen from the examples in the test set signals table 407, test set number 1 has associated with it test requests 4, 2 and 3. Thus, the information stored in the test sets storage system 117 indicates that the test set described as "Check Engine" should result in the test requests 4, 2 and 3 being sent to the vehicle. Similarly, the example data in FIG. 4 indicates that the "Check ABS" test set should result in the test requests 7, 10, 2 and 4 being delivered to the vehicle. [0065] The information shown in FIG. 4 thus illustrates that a related series of tests may be associated with a single user-friendly description. It also illustrates that the same test request, e.g., test request 2, may be a part of more than one test set group.

[0066] All or portions of the data that is stored in the test sets storage system 117 may be created by a person or group with a high degree of expertise in vehicle diagnostics. This may be a person other than the operator of the vehicle diagnostic system 101. For example, all or portions of this data may be created and/or loaded in the tests sets storage system 117 by the manufacturer of the vehicle diagnostic system 101 , the distributor of the diagnostic system, the manufacturer of the vehicle, or another expert in the field.

[0067] Referring back to FIG. 1 , the vehicle diagnostic system 101 may include a trouble shooting storage system 119. The trouble shooting storage system 119 may store information, such as textual material, drawings, diagrams and charts, that may be consulted by the operator of the vehicle diagnostic system 101 to assist the operator in determining what tests to run and/or in analyzing diagnostic information that is received by the vehicle diagnostic system 101.

[0068] The information in the trouble shooting storage system 119 may be created by a person or group with a high degree of expertise in vehicle diagnostics. This may be a person other than the operator of the vehicle diagnostic system 101. For example, all or portions of this information may be created and/or loaded in the trouble shooting storage system 119 by the manufacturer of the vehicle diagnostic system, the distributor of the diagnostic system, the manufacturer of the vehicle, or another expert in the field.

[0069] One or more rules in the rules storage system 107 may direct the operator to one or more sections in the trouble shooting storage system 119. One or more sections in the trouble shooting storage system 119 may, in turn, direct the operator to one or more tests or one or more test sets in the test sets storage system 117.

[0070] The vehicle diagnostic system 101 may also include a processing system 121. The processing system 121 may be any type of processing system and may include hardware and/or software. It may include one or more microprocessors, storage devices and/or memories. It may include a general purpose computer programmed to operate in connection with the vehicle diagnostic system 101 or a computing system dedicated to the vehicle diagnostic system 101. It may be a standalone system or part of a network. It may be in a single location or distributed across several locations.

[0071] The processing system 121 may coordinate and manage the operations of the vehicle diagnostic system 101 and the communication between its various components.

[0072] FIG. 5 is a flow diagram of one embodiment of a process that may be implemented by the vehicle diagnostic system 101 shown in FIG. 1. As shown in FIG. 5, a test to be performed by the vehicle diagnostic system 101 may be selected, as reflected by a Select Test block 501.

[0073] Any approach may be used for the Select Test block 501. For example, the operator may select the test from a list of tests that are displayed on the output system 111 under the control of the processing system 121. Alternatively, the test may be one of the tests that are provided in a test set that is stored in the test sets storage system 117. The operator may select this test set from a list of test sets that are displayed on the output system 111 under the control of the processing system 121. The selected test may be a test that is recommended by a rule that is stored in the rules storage system 107 based on an analysis of earlier diagnostic information. The selected test may be a test that is recommended by the trouble shooting storage system 119. It may be initiated automatically or through a selection made by an operator of the system. The selected test may be initiated automatically by the vehicle diagnostic system 101 as part of a comprehensive test process that the vehicle diagnostic system 101 performs on the vehicle without the operator identifying the test or tests sets to be run.

[0074] The test request that corresponds to the test may then be directed by the processing system 121 through the vehicle interface 115 into the communication link 105 and, in turn, into the vehicle 103. This is reflected in FIG. 5 by a Send Test request block 503. In an alternate embodiment, diagnostic information may be sent by the vehicle and analyzed by the vehicle diagnostic system 101 without a test request.

[0075] The diagnostic information that the vehicle 103 generates in response may be received by the processing system 121 through the vehicle interface 115 and the communication link 105, as reflected by a Receive Diagnostic Information block 505.

[0076] The processing system 121 may then apply one or more rules in the rules storage system 107 to the received diagnostic information, as reflected by an Apply Applicable Rule(s) block 507. To accomplish this, the processing system may consult the rules storage system 107 to identify the rule or rules that are specified in the rules storage system 107 to be applied to diagnostic information of the type that has been received. If the rules storage system 107 designates multiple rules to be applied, the processing system 121 may cause each of those multiple rules to be applied.

[0077] The processing system 121 may then cause the output system 111 to communicate the results of the application of the rules, as reflected in a Communicate Results block 509. The results may be any of the types of anomaly alerts that are discussed above or an affirmative communication that no anomaly has been detected at this point in the process.

[0078] The process illustrated in FIG. 5 may be repeated in connection with other desired tests. One or more of these subsequent tests may be selected and initiated by the operator. They may instead be the remaining tests in a test set that the operator previously selected from the test sets storage system 117 that have not yet been performed. In this later case, the remaining tests may be initiated automatically by the vehicle diagnostic system 101.

[0079] In the event that a test set from the test sets storage system 117 has not yet been completed, the processing system 121 may defer the reporting of any test results to the operator until all of the tests in the test set are performed and analyzed by the rules in the rules storage system 107. In this embodiment, rules may be included in the rules storage system 107 that analyze the results of multiple tests within one or more of the test sets in the test sets storage system 117. The processing may be configured to provide a consolidated report of all of the test results.

[0080] The rules storage system 107, the test sets storage system 117 and the trouble shooting storage system 119 may include any type of hardware or software arrangement. Each may include one or more disk drives, CD-ROMs, tapes, ROMs, programmable memories and/or RAMs. Components in these storage systems may be separate from or shared by the processing system 121.

[0081] Any type of logical configuration may be used for the rules storage system 107, the test sets storage system 117 and the trouble shooting storage system 119. This includes databases, such as flat databases, relational databases and/or hierarchical databases. It also includes databases that are centralized or distributed.

[0082] Referring back to Fig. 1 , as has been mentioned previously all or part of the individual components identified may be distributed across one or more electronic devices. For example, a hand held scan tool may be provided with the functionality of the vehicle interface 115 and data store 122. Once the necessary movie has been recorded, that data may be uploaded or transferred to a standalone or networked computer system to enable a processing of that data. The rules 107, test sets 117 and trouble shooting 119 storage systems could be provided on that computer system. In this way, data in the form of a movie can be collected and then processed offline. This is particularly advantageous when one considers the volume of data that may require analysis from one or more movie sequences.

[0083] Referring again back to Figure 1 , the diagnostic system 101 could, it will be appreciated, be configured to operate in one of two modes; a first mode where it effects a diagnosis on the basis of recorded movie data and a second where it effects the diagnosis on the basis of stand alone integers. Indeed a combination of the two modes could be used for specific tests and/or rules. If for example a movie analysis points to a specific trend but within that data sequence defined by the movie there are a predetermined number of faults or identifiable activities, then the diagnostic system 101 could utilize both results to provide the operator with a diagnosis of the problem. [0084] In order to effect a recordal of a movie it is possible to provide the operator with a trigger function. In this way the operator could be effecting an analysis of the vehicle using the second mode and then ascertains that a movie may provide a better insight or that the problem may require offline analysis. By utilizing a trigger a movie recordal may be effected. This may be achieved in a number of different ways. For example, the triggering may effect a recordal of all incoming data on the data stream for a predetermined time period or for example on the basis of the available capacity for storage. Alternatively, the data store could be configured to constantly cache all incoming streaming data in a first in first out (FIFO) manner. In this way once a trigger is applied, the data store stores a set of data in a time domain before the trigger and a set of data in a time domain after the trigger, the two sets being combined to form a stored movie. Such an example is shown in Fig. 6 where an example of the internal make up of the datastore 122 is shown. From an examination of the datastore 122 of Fig. 6, it is evident that the datastream comprising individual frames of data retrieved from the vehicle are routed through a buffer 600 in the datastore module. The buffer receives and temporarily stores these individual frames 603a, 603B, 603C, etc in a FIFO manner, with the number of individual frames storeable being defined by the memory allocation given to the buffer. The buffer is interfaced with a trigger 605, which as mentioned above could be a rules activated trigger or alternatively a user activated trigger. Activation of the trigger causes a marking of the data sequence within the buffer with a trigger point 606. By defining a movie as a predetermined number of frames before and after the trigger point it is possible to subdivide the data that is in the buffer to a storeable movie sequence. Alternatively all data in the buffer may be copied as the movie sequence, and the nature of the data that is stored will of course be affected by the timing of the trigger. Once this is created, this data is then copied to a movie storage cache 610 for subsequent or indeed immediate analysis. A movie may be interrogated as a whole or indeed subsequent processing may require additional subdivision of the movie sequence. It will be appreciated that a plurality of movie storage caches may be provided, each having a defined movie sequence stored therein. It will be further appreciated that such a movie could be associated with identifiers relating to the rules and/or tests that were used to generate the data stream that is recorded. Each movie cache would therefore be identified by these specific identifiers. This is especially important if one considers that processing and analysis of the data could be effected remotely from the recordal and by different persons.

[0085] The foregoing description has been presented for the purpose of illustration only. It is not intended to be exhaustive or to limit the concepts that have been disclosed. Numerous modifications and variations are possible.

[0086] For example, the embodiments that have been described may include or be utilized with any appropriate voltage source, such as a battery, an alternator and the like, providing any appropriate voltage, such as about 12 volts, about 42 volts and the like.

[0087] The embodiments that have been described may be used with any desired system or engine. These systems or engines may use fossil fuels, such as gasoline, natural gas, propane and the like, electricity, such as that generated by a battery, magneto, solar cell and the like, wind and hybrids or combinations thereof. These systems or engines may be incorporated into other systems, such as an automobile, a truck, a boat or ship, a motorcycle, a generator, an airplane and the like.

[0088] In short, the scope of this application is limited solely to the claims that now follow.

Claims

We Claim:

1. A vehicle diagnostic system comprising: a vehicle interface configured to receive diagnostic information from the vehicle in the form of a data stream; a data store configured to store the data stream so as to define a sampled set of the data stream, the sampled set including a plurality of instantaneous measurements over a time period; a rules storage system configured to store one or more rules, each of which determines whether a vehicle may have an anomaly when applied to vehicle diagnostic information; an operator interface configured to alert an operator of the diagnostic system to a suspected anomaly in the vehicle; and a processing system configured to: apply one or more rules in the rules storage system to the sampled set of the diagnostic information; and cause the operator interface to alert the operator to a suspected anomaly in the vehicle if application of the one or more rules results in a determination that the vehicle may have that anomaly.

2. The vehicle diagnostic system of claim 1 wherein the processing system is configured to deliver a plurality of different types of test requests to the vehicle, each one of which causes a different type of diagnostic information to be sent by the vehicle to the diagnostic system.

3. The vehicle diagnostic system of claim 2 wherein: the rules storage system is configured to store a relationship between each rule and the type of diagnostic information to which the rule applies; and the processing system is configured to: consult the relationships in the rules storage system for the purpose of identifying the rule or rules that should be applied to a particular type of diagnostic information; and to only apply the identified rule or rules to that information.

4. The vehicle diagnostic system of claim 2 further including a test sets storage system configured to store a plurality of test sets, each test set designating a plurality of test requests that are to be sent to the vehicle in response to a single request for the test requests designated by that test set.

5. The vehicle diagnostic system of claim 4 wherein: the test sets storage system is configured to store a relationship between each test set and a description of the test set that the operator may select for the purpose of initiating the test set; and the processing system is configured to: present a plurality of the descriptions of the test sets to the operator; and to implement the test set selected by the operator.

6. The vehicle diagnostic system of claim 4 wherein the processing system is configured to: receive diagnostic information from the vehicle in response to each test request in the selected test set; apply one or more rules in the rules storage system to the diagnostic information provided in response to each test request in the selected test set; and cause the operator interface to alert the operator to each suspected anomaly in the vehicle that application of the one or more rules determine that the vehicle may have.

7. The vehicle diagnostic system of claim 1 wherein the vehicle interface is configured to receive a data stream in compliance with the OBD Il data stream specification.

8. The vehicle diagnostic system of claim 1 wherein the vehicle interface is configured to receive a data stream in compliance with the EOBD data stream specification.

9. The vehicle diagnostic system of claim 1 wherein the operator interface includes a display.

10. The vehicle diagnostic system of claim 9 wherein the operator interface is configured to: display at least portions of the diagnostic information; and alert the operator to a suspected anomaly in the vehicle by giving emphasis to a displayed portion of the diagnostic information that is indicative of the suspected anomaly.

11. The vehicle diagnostic system of claim 1 wherein the operator interface is configured to alert an operator by providing a description of the suspected anomaly.

12. The vehicle diagnostic system of claim 1 wherein the operator interface is configured to alert an operator by suggesting one or more additional tests to run.

13. The vehicle diagnostic system of claim 1 wherein the rules storage system contains rules that are not created by the operator of the vehicle diagnostic system.

14. The vehicle diagnostic system of claim 13 wherein the rules storage system contains rules that are created by the manufacturer of the vehicle diagnostic system.

15. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for an out-of-bound condition.

16. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for a glitch.

17. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for a step function.

18. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for a matching pattern.

19. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for a logical combination of other rules.

20. The vehicle diagnostic system of claim 1 wherein the rules storage system is configured to store rules that test for trends within the sampled set.

21. The vehicle diagnostic system of claim 1 wherein the data store includes a buffer configured to temporarily store the data stream received from the vehicle interface.

22. The vehicle diagnostic system of claim 21 wherein the buffer operates on a FIFO principle, such that frames of data making up the data stream are dropped from the buffer from the buffer in a predetermined manner.

23. The vehicle diagnostic system of claim 21 wherein portions of the data stream present in the buffer define a sampled set of the data stream, this sampled set being selectable for storage as a movie.

24. The vehicle diagnostic system of claim 23 wherein the portions are selected on an external triggering, the triggering defining a trigger point within the buffered data stream about which the movie is defined.

25. The vehicle diagnostic system of claim 21 wherein the sampled set selectable for storage as a movie is stored within a cache of the data store, the stored movie being associated with one or more identifiers specific to the movie.

26. The vehicle diagnostic system of claim 22 wherein the processing system is configured to apply one or more rules in the rules storage system to individual frames within the buffer in addition to the application of one or more rules to the sampled set of the diagnostic information

27. A vehicle diagnostic process comprising: sending a test request to a vehicle; receiving diagnostic information from the vehicle in response to the test request; recording a time sequence of the received diagnostic information so as to define a movie of the diagnostic information for that test request; applying one or more rules to the movie, each rule configured to examine trends within the movie so as to determine whether the vehicle may have an anomaly; and alerting a technician to a suspected anomaly in the vehicle if the application of one or more rules to the diagnostic information determines that the vehicle may have that anomaly.

28. The vehicle diagnostic process of claim 27 further including: consulting relationships between rules and types of diagnostic information; and applying only the rule or rules to the diagnostic information that have matching relationships to the type of the diagnostic information.

29. The vehicle diagnostic process of claim 27 further comprising: sending a plurality of test requests to the vehicle in response to a technician's selection of a set of tests to run from a plurality of test sets; receiving diagnostic information from the vehicle in response to each test request; applying one or more rules to each received diagnostic information, each rule configured to determine whether the vehicle may have an anomaly, at least one of the rules testing a movie of the diagnostic information; and alerting a technician to a suspected anomaly in the vehicle if the application of one or more rules to any of the diagnostic information determines that the vehicle may have that anomaly.

30. The vehicle diagnostic process of claim 29 wherein the alerting includes giving emphasis to a portion of the diagnostic information that is indicative of the anomaly.

31. The vehicle diagnostic process of claim 29 wherein the alerting includes providing a description of the anomaly.

32. The vehicle diagnostic process of claim 29 wherein the alerting includes suggesting one or more additional test to run.

33. The vehicle diagnostic process of claim 29 wherein one or more of the applied rules tests for an out-of bound condition.

34. The vehicle diagnostic process of claim 29 wherein one or more of the applied rules tests for a glitch.

35. The vehicle diagnostic process of claim 29 wherein one or more of the applied rules tests for a step function.

36. The vehicle diagnostic process of claim 29 wherein one or more of the applied rules tests for a matching pattern.

37. The vehicle diagnostic process of claim 29 wherein one or more of the applied rules tests for a logical combination of other rules.

38. A computer program adapted when run on a computer to carry out the process steps of any one of claims 27 to 37.