Abstract: A diagnostic system for a vehicle, includes a computer storing software on a computer readable media, configurable for setting up recording of vehicle operations, selecting from a plurality of customizable triggering operations according to Boolean logic, and a vehicle communication interface detachably connected to the computer, being setup by the computer for recording of vehicle operation while the vehicle is operating and recorded information stored in a computer readable media of the vehicle communication interface being reviewed by the computer, and detachably connected to the vehicle for recording of the vehicle operations.

Abstract: A method for optimizing a test sequence to diagnose a failure mode of a device, such as a vehicle, is provided. At least one symptom of a fault of the device is received, and a plurality of taxonomies is generated. The taxonomies include a device component taxonomy, a fault taxonomy, and a diagnostic taxonomy, and each taxonomy has a plurality of nodes. At least one diagnostic test sequence, based on the symptom and the taxonomies, is generated, costs associated with the diagnostic test sequence are determined, and a cost optimal test sequence, based on the costs and the diagnostic test sequence, is generated.

Abstract: A dynamic diagnostic plan generator arranges diagnostic test procedures related to a vehicle/power tool/patient symptom or operational problem in a sequence based on a probabilistic Failure Mode and Effects Analysis (FMEA). The diagnostic plan generator also tracks a vehicle/power tool/patient state, and provides instructions for test preparation steps and instructions for performing the diagnostic test procedures. The plan generator further generates schematic illustrations of the diagnostic test procedures, and creates a diagnostic data structure containing information related to the diagnostic test procedures. In addition, the diagnostic plan generator sends and receives information regarding actual failure mode occurrences, for example, to and from a central database. Furthermore, the diagnostic plan generator facilitates the creation of failure mode tests by an expert diagnostics author.

Abstract: A diagnostic system for a patient includes a memory receiving and storing patient specific information, and storing diagnostic test requirements of a plurality of diagnostic sequences, and a processor identifying the test requirements for a selected diagnostic sequence according to the patient specific information in advance of executing the diagnostic sequence.

Abstract: A dynamic diagnostic plan generator arranges diagnostic test procedures related to a vehicle symptom or operational problem in a sequence based on a probabilistic Failure Mode and Effects Analysis (FMEA). The diagnostic plan generator also tracks a vehicle state, and provides instructions for test preparation steps and instructions for performing the diagnostic test procedures. The plan generator further generates schematic illustrations of the diagnostic test procedures, and creates a diagnostic data structure containing information related to the diagnostic test procedures. In addition, the diagnostic plan generator sends and receives information regarding actual failure mode occurrences, for example, to and from a central database. Furthermore, the diagnostic plan generator facilitates the creation of failure mode tests by an expert diagnostics author.

Abstract: A vehicle state tracker tracks the state of a vehicle during a diagnostic test sequence to eliminate redundant steps between diagnostic procedures. The vehicle state tracker maintains a list of preconditions required for each diagnostic procedure, reads a current vehicle state from a memory register and verifies the current setting of the vehicle state corresponding to a specific precondition. If the precondition is required and the current setting is not valid, the state tracker further formats a test preparation step corresponding to the precondition for display to instruct a vehicle technician to satisfy the precondition. Otherwise, if the precondition is not required and the corresponding setting is valid, the state tracker formats an instruction to reverse the corresponding vehicle condition. The state tracker additionally receives feedback indicating when a precondition has been satisfied or the corresponding vehicle condition has been reversed, and updates the vehicle state in memory.

Abstract: A diagnostic system for a vehicle, includes a computer storing software on a computer readable media, configurable for setting up recording of vehicle operations, selecting from a plurality of customizable triggering operations according to Boolean logic, and a vehicle communication interface detachably connected to the computer, being setup by the computer for recording of vehicle operation while the vehicle is operating and recorded information stored in a computer readable media of the vehicle communication interface being reviewed by the computer, and detachably connected to the vehicle for recording of the vehicle operations.

Abstract: A diagnostic system for a vehicle, including a memory receiving and storing vehicle specific information, and storing diagnostic test requirements of a plurality of diagnostic sequences, and a processor identifying the test requirements for a selected diagnostic sequence according to the vehicle specific information in advance of executing the diagnostic sequence.

Abstract: A dynamic diagnostic plan generator arranges diagnostic test procedures related to a vehicle symptom or operational problem in a sequence based on a probabilistic Failure Mode and Effects Analysis (FMEA). The diagnostic plan generator also tracks a vehicle state, and provides instructions for test preparation steps and instructions for performing the diagnostic test procedures. The plan generator further generates schematic illustrations of the diagnostic test procedures, and creates a diagnostic data structure containing information related to the diagnostic test procedures. In addition, the diagnostic plan generator sends and receives information regarding actual failure mode occurrences, for example, to and from a central database. Furthermore, the diagnostic plan generator facilitates the creation of failure mode tests by an expert diagnostics author.

Abstract: A reverse failure analyzer determines a group of diagnostic test procedures related to a particular vehicle component from a pool of diagnostic procedures, and then identifies the specific failure modes of each of the diagnostic test procedures. The reverse failure analyzer further associates the specific failure modes with the respective vehicle component associated with each of the diagnostic test procedures, and the symptoms associated with each of the diagnostic test procedures to the correlated vehicle components and failure modes. In addition, the reverse failure analyzer can cross-reference various vehicle components that can be the root cause of a particular symptom or a vehicle operational problem. Furthermore, the reverse failure analyzer can receive observed symptoms regarding a particular test subject vehicle and correlate the observed symptoms to the vehicle components that can cause the symptoms based on the results of reverse failure analyses.

Abstract: A vehicle state tracker tracks the state of a vehicle during a diagnostic test sequence to eliminate redundant steps between diagnostic procedures. The vehicle state tracker maintains a list of preconditions required for each diagnostic procedure, reads a current vehicle state from a memory register and verifies the current setting of the vehicle state corresponding to a specific precondition. If the precondition is required and the current setting is not valid, the state tracker further formats a test preparation step corresponding to the precondition for display to instruct a vehicle technician to satisfy the precondition. Otherwise, if the precondition is not required and the corresponding setting is valid, the state tracker formats an instruction to reverse the corresponding vehicle condition. The state tracker additionally receives feedback indicating when a precondition has been satisfied or the corresponding vehicle condition has been reversed, and updates the vehicle state in memory.

Abstract: A diagnostic information converter reads an existing static diagnostic procedure in the form of a tree graph and generates a diagnostic Failure Modes and Effects Analysis that can be used in the generation of a dynamic diagnostic test plan. The converter identifies the end nodes of the graph and associates a specific failure mode with each of the end nodes. In addition, the converter traces a unique path from each end node along successive branches through one or more intermediate nodes to the root node, and from each of the paths derives an initial failure mode test including the test steps corresponding to the root node, the intermediate nodes and the end node. The converter further identifies and annotates precondition nodes that correspond to a vehicle state or condition, rather than to an actual diagnostic test step and allows a user to edit the initial failure mode tests.

Abstract: A vehicle state tracker tracks the state of a vehicle during a diagnostic test sequence to eliminate redundant steps between diagnostic procedures. The vehicle state tracker maintains a list of preconditions required for each diagnostic procedure, reads a current vehicle state from a memory register and verifies the current setting of the vehicle state corresponding to a specific precondition. If the precondition is required and the current setting is not valid, the state tracker further formats a test preparation step corresponding to the precondition for display to instruct a vehicle technician to satisfy the precondition. Otherwise, if the precondition is not required and the corresponding setting is valid, the state tracker formats an instruction to reverse the corresponding vehicle condition. The state tracker additionally receives feedback indicating when a precondition has been satisfied or the corresponding vehicle condition has been reversed, and updates the vehicle state in memory.

Abstract: A diagnostic test sequence optimizer includes a diagnostic test selector that determines a group of diagnostic test procedures related to a specific symptom and vehicle type from a pool of diagnostic procedures. A failure mode analyzer then selects one or more factors that can affect resolution of a vehicle operational problem and performs a failure mode analysis to quantify a comparative utility of the individual tests, and a factor weighter assigns a weight to each of the factors. A vehicle receiver receives information regarding the history of the test subject vehicle, and a sequence optimizer places the diagnostic test procedures in an optimized sequence in accordance with the comparative utilities of the individual diagnostic procedures, user preferences and a Failure Mode and Effects Analysis compiled by the manufacturer of the vehicle.

Abstract: A reverse failure analyzer determines a group of diagnostic test procedures related to a particular vehicle component from a pool of diagnostic procedures, and then identifies the specific failure modes of each of the diagnostic test procedures. The reverse failure analyzer further associates the specific failure modes with the respective vehicle component associated with each of the diagnostic test procedures, and the symptoms associated with each of the diagnostic test procedures to the correlated vehicle components and failure modes. In addition, the reverse failure analyzer can cross-reference various vehicle components that can be the root cause of a particular symptom or a vehicle operational problem. Furthermore, the reverse failure analyzer can receive observed symptoms regarding a particular test subject vehicle and correlate the observed symptoms to the vehicle components that can cause the symptoms based on the results of reverse failure analyses.

Abstract: A reverse failure analyzer determines a group of diagnostic test procedures related to a particular vehicle component from a pool of diagnostic procedures, and then identifies the specific failure modes of each of the diagnostic test procedures. The reverse failure analyzer further associates the specific failure modes with the respective vehicle component associated with each of the diagnostic test procedures, and the symptoms associated with each of the diagnostic test procedures to the correlated vehicle components and failure modes. In addition, the reverse failure analyzer can cross-reference various vehicle components that can be the root cause of a particular symptom or a vehicle operational problem. Furthermore, the reverse failure analyzer can receive observed symptoms regarding a particular test subject vehicle and correlate the observed symptoms to the vehicle components that can cause the symptoms based on the results of reverse failure analyses.

Abstract: A vehicle diagnostic data collector/analyzer compiles historical vehicle diagnostic data, including measured operating parameters from a number of different vehicles operating under a variety of normal vehicle operating conditions and vehicle component failure conditions, and performs statistical analyses on various vehicle type/operating condition combinations to establish operating parameter ranges corresponding to normal operating conditions and various failure conditions. The diagnostic data collector/analyzer also measures real-time operating parameters on specific test-subject vehicles and evaluates similarities and differences between the measured operating parameters and the established ranges, and correlates the test data with known operating conditions in order to diagnose potential failure modes of vehicle components.

Abstract: A vehicle state tracker tracks the state of a vehicle during a diagnostic test sequence to eliminate redundant steps between diagnostic procedures. The vehicle state tracker maintains a list of preconditions required for each diagnostic procedure, reads a current vehicle state from a memory register and verifies the current setting of the vehicle state corresponding to a specific precondition. If the precondition is required and the current setting is not valid, the state tracker further formats a test preparation step corresponding to the precondition for display to instruct a vehicle technician to satisfy the precondition. Otherwise, if the precondition is not required and the corresponding setting is valid, the state tracker formats an instruction to reverse the corresponding vehicle condition. The state tracker additionally receives feedback indicating when a precondition has been satisfied or the corresponding vehicle condition has been reversed, and updates the vehicle state in memory.

Abstract: A vehicle state tracker tracks the state of a vehicle during a diagnostic test sequence to eliminate redundant steps between diagnostic procedures. The vehicle state tracker maintains a list of preconditions required for each diagnostic procedure, reads a current vehicle state from a memory register and verifies the current setting of the vehicle state corresponding to a specific precondition. If the precondition is required and the current setting is not valid, the state tracker further formats a test preparation step corresponding to the precondition for display to instruct a vehicle technician to satisfy the precondition. Otherwise, if the precondition is not required and the corresponding setting is valid, the state tracker formats an instruction to reverse the corresponding vehicle condition. The state tracker additionally receives feedback indicating when a precondition has been satisfied or the corresponding vehicle condition has been reversed, and updates the vehicle state in memory.

Abstract: An interactive diagnostic schematic generator illustrates diagnostic test procedures for diagnosing failure modes of a vehicle. The schematic generator reads a schematic data file such as a wiring diagram from a computer memory, indicates a test subject in the schematic or illustrates a location where test equipment is to be connected, and formats the schematic for display on a display device. The schematic generator also receives feedback from a vehicle onboard computer, test equipment or user input indicating that the action has been performed, and removes the indication of the test subject in the schematic. The schematic generator further marks the test subject to indicate that the action has been performed with a marking style that is visually distinct from the indicating style, optionally indicating that the result has validated or invalidated the test subject.