US20160350985A1 - Vehicle diagnostic monitor tool - Google Patents
Vehicle diagnostic monitor tool Download PDFInfo
- Publication number
- US20160350985A1 US20160350985A1 US15/231,177 US201615231177A US2016350985A1 US 20160350985 A1 US20160350985 A1 US 20160350985A1 US 201615231177 A US201615231177 A US 201615231177A US 2016350985 A1 US2016350985 A1 US 2016350985A1
- Authority
- US
- United States
- Prior art keywords
- data
- vehicle
- operational data
- trigger event
- trigger
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/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
-
- F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
- F02—COMBUSTION ENGINES; HOT-GAS OR COMBUSTION-PRODUCT ENGINE PLANTS
- F02D—CONTROLLING COMBUSTION ENGINES
- F02D41/00—Electrical control of supply of combustible mixture or its constituents
- F02D41/22—Safety or indicating devices for abnormal conditions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
- G06F11/0739—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function in a data processing system embedded in automotive or aircraft systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/065—Replication mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0656—Data buffering arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
-
- 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/006—Indicating maintenance
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
- G07C5/00—Registering or indicating the working of vehicles
- G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
-
- 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/0808—Diagnosing performance data
-
- 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/0816—Indicating performance data, e.g. occurrence of a malfunction
-
- G—PHYSICS
- G08—SIGNALLING
- G08C—TRANSMISSION SYSTEMS FOR MEASURED VALUES, CONTROL OR SIMILAR SIGNALS
- G08C19/00—Electric signal transmission systems
Definitions
- Today's vehicles are equipped with many different types of data collection and processing components. Much of the data collected by the data collection components is used to control the operation of the vehicle. For example, data collected by oxygen sensors is used to control the amount of fuel introduced into the engine, to avoid providing an overly rich fuel mixture that would result in decreased fuel efficiency and increased emissions.
- operational data encompasses data that is used to control the operation of the vehicle, such as the data from oxygen sensors as noted above (data which is used by one or more vehicle controllers as feedback for controlling some aspect of the vehicles operation), or data that is simply generated during the operation of the vehicle (some vehicles generate operational data that is not used by any vehicle component during routine vehicle operation, but is rather used by diagnostic or service equipment during vehicle servicing or maintenance).
- operational data is not stored, but rather is generated, contemporaneously used (either to control various vehicular systems or to provide data to diagnostic or service equipment during vehicle servicing), and then discarded.
- Exemplary operational data include, but is not limited to, engine coolant temperature, engine speed, oxygen levels, throttle position, brake temperature, vehicle speed, brake position, and gearbox parameters. Much of this data is collected very frequently, some types of operational data being collected multiple times per second. The sheer quantity of operational data being generated by the various vehicle components and subsystems makes storing or archiving all of such operational data problematical. Some vendors do provide data logging systems for temporary use in vehicles, where all the operational data generated by the vehicle is stored for later analysis, but such data logging systems are not designed for long term use.
- Fault code data somewhat addresses the problem of storing the enormous quantity of operational data generated by vehicles.
- Fault codes corresponding to specific undesirable operating parameters are predefined.
- a processor in the vehicle monitors the operational data as it is generated, and whenever an operating parameter corresponding to a specific predefined fault code is detected, the fault code is stored in a memory in the vehicle.
- the fault code is generally a numeric or alphanumeric value that can be stored using very little memory resources.
- the number 11 can be defined as a fault code for the following condition: battery sensing voltage drops below 4 or between 7 and 8 volts for more than 20 seconds.
- Fault codes can be retrieved and used to diagnose vehicle problems. Even with the data provided by fault codes, accurate diagnosis of complex or unusual vehicular system failures can be problematical.
- the concepts disclosed herein encompass temporarily storing operational data in a buffer in the vehicle, rather than simply discarding the operational data, and then archiving such buffered operational data whenever a fault code is generated.
- Such archived operational data combined with the fault code will provide a contextually rich data set that will greatly facilitate diagnosis of vehicle problems.
- the term combining does not require the archived or saved operational data and the fault code data to be stored in the same file location or data packet, rather, the term combining is used to indicate that a contextual link between the archived operational data and the fault code is generated, so that even if the archived operational data and the fault code are not stored together in a single file or data packet, the archived operational data corresponding to a particular fault code can be differentiated from archived operational data corresponding to a different fault code.
- Time indexing can be used to correlate specific archived operational data to specific fault codes, if the different types of data are to be stored separately.
- the archived operational data corresponding to a particular fault code is ring buffered operational data, which includes operational data collected both before and after the fault code is detected.
- the amount of operational data before and after the fault code can be defined as desired, and need not be identical (that is, some users may prefer relatively more operational data after a fault code is detected, and relatively less operational data before a fault code is detected, or vice versa).
- systems implementing the concepts disclosed herein are configured to enable the temporal extent of such a ring buffer to be a user adjustable parameter.
- the contextually (and temporally) linked buffered operational data and fault code data are conveyed in real-time to a remote computing device, so that a diagnosis of a vehicle problem causing the generation of the fault code can occur while the vehicle is operational. Rapid diagnosis of problems can lead to the prevention of damage to the vehicle caused by continuing to operate the vehicle after a malfunction is detected, where the diagnosis indicates that continued operation of the vehicle would result in such damage. In such circumstances, the driver of the vehicle can be contacted to ensure that continued operation of the vehicle does not occur. If the diagnosed problem is relatively minor, the operator of the vehicle can be contacted with less urgency to arrange for a repair. In an exemplary, but not limiting embodiment, where continued operation of the vehicle is not likely to result in damage, the results of the vehicle diagnosis are forwarded to the vehicle operator, service for the vehicle is scheduled, and parts required for the service are ordered, all while the vehicle continues to operate.
- the fault codes discussed above represent the detection of an anomalous vehicle condition identified by analyzing the operational data.
- the concepts disclosed herein encompass embodiments where real time analysis of the vehicle operational data at the vehicle indicates an anomalous condition exists, even when the anomalous condition does not correspond to a fault code predefined by the vehicle manufacturer.
- the controller in the vehicle tasked with the analysis of operational data to detect an anomalous condition can be configured as desired to detect specific conditions that a user has determined represents an anomaly.
- buffered operational data is conveyed to a remote computing device whenever a user defined operating parameter is detected.
- a custom fault code library (note that prior art fault codes are tied to specific operating parameters, however, prior art fault codes are predefined at the vehicle manufacturer level, and are not user modifiable or user defined).
- This concept is referred to herein and in the claims that follow as a user defined fault code.
- Such user defined fault codes can include any user defined single operational parameter, or a combination of user defined operational parameters, that are unique from the fault codes defined at the vehicle manufacturer level.
- systems implementing the concepts disclosed herein are configured so that user defined fault codes can be defined and implemented while the vehicle is operational.
- user defined fault codes are generated at a remote computing device attempting to acquire additional information to be used to diagnose a vehicle, where the user defined fault code is uniquely defined based on buffered operational data conveyed to the remote computing device while the vehicle is operating.
- the concepts disclosed herein encompass embodiments in which the detection of an anomalous conditions triggers the transmission of the buffered operational data collected proximate the detection of the anomalous condition (and data defining the detected anomaly) to the remote computing device for analysis immediately (i.e., in real-time), or after only a relatively brief delay.
- a wireless data link such as a cellular data link, is used to transmit such data from the vehicle to the remote computing device.
- the buffered operational data collected proximate the detection of the anomalous condition can be stored at the vehicle and sent to the remote computing device when a data link can be established.
- buffered operational data collected proximate the detection of the anomalous condition is intended to encompass: (1) buffered operational data collected for a predefined period after the anomaly has been detected; (2) buffered operational data collected for a predefined period before the anomaly was detected; and (3) buffered operational data collected for a predefined period after the anomaly has been detected combined with buffered operational data collected for a predefined period before the anomaly was detected. Because the buffer temporarily stores operational data, some amount of operational data acquired before the anomalous event is detected is available (the amount of operational data available being a function of a size of the buffer).
- the buffered operational data includes operational data that is automatically broadcast by the vehicle while the vehicle is operating. In at least one exemplary embodiment, the buffered operational data includes operational data that must be specifically requested. In yet another exemplary embodiment, the buffered operational data includes both operational data that is automatically broadcast by the vehicle while the vehicle is operating and operational data that must be specifically requested. In general, operational data that must be requested is operational data that can be generated upon request (such as throttle position data), but is not data that normally generated during routine vehicle operations.
- the concepts disclosed herein can also be implemented as a non-transitory memory medium, storing machine instructions that when executed by a processor implement the method, and by a system for implementing the method.
- the basic elements include a vehicle, operational data collection components in the vehicle, a memory (i.e., a buffer) at the vehicle in which some amount of operational data is temporarily stored, and a vehicle processor for monitoring the operational data to detect an anomalous condition (i.e., to detect a fault code, manufacturer defined or user defined).
- a communication link (preferably bidirectional, so that in the event that the diagnosis indicates that continued operation is ill advised, the driver of the vehicle can be contacted) for communicating with a remote computing device is included.
- a processor such as a computing device implementing machine instructions to implement the specific functions noted above
- a custom circuit such as an application specific integrated circuit
- real-time as used herein and the claims that follow is not intended to imply the data is transmitted instantaneously, rather the data is collected over a relatively short period of time (over a period of seconds or minutes), and transmitted to the remote computing device on an ongoing basis (transmission of the buffered operational data being triggered by the detection of a fault or anomaly), as opposed to storing the data at the vehicle for an extended period of time (hour or days), and transmitting an extended data set to the remote computing device after the data set has been collected.
- the concepts disclosed herein encompass a system where the above identified data operational data collection components, the data buffer (where some amount of operational data is temporarily stored, rather than being discarded), the processor (for analyzing the operational data to detect an anomalous condition), and the data link (for conveying the buffered operational data and the detected anomalous condition to a remote computing device for analysis) are included in a plurality of enrolled vehicles.
- a system includes a remote computing device (either an individual computing device, or a network of such devices), where the buffered operational data and the data defining the anomalous condition (such as a fault code) can be stored or analyzed (i.e., diagnosed).
- vehicle position data and/or inspection data is collected from enrolled vehicles and stored at a first server, operated by a first entity, for use by the operator of the vehicle. Such data is collected during normal operation of the vehicle, and sent to the first server during normal operation of a vehicle.
- the buffered operational data and the data defining the anomalous condition are sent from the vehicle to the first server.
- the first entity operating the first server then conveys the buffered operational data and the data defining the anomalous condition to a second server operated by a second entity.
- the second entity analyzes the buffered operational data and the data defining the anomalous condition and determines the cause of the anomalous condition.
- the vehicle operator can then be contacted to arrange servicing of the vehicle.
- the second entity is the manufacturer of the vehicle or the vehicle power plant.
- each enrolled vehicle includes a position tracking component (such as a global position satellite (GPS) tracking device), along with the data buffer, the data link to the remote computing device, and the processor for detecting the anomalous condition (or responding to the detection of the anomalous condition by using the data link to convey the buffered operational data to a remote computing device for analysis).
- a position tracking component such as a global position satellite (GPS) tracking device
- GPS global position satellite
- such components are incorporated into a diagnostic or telematics device also including the position tracking component.
- the concepts disclosed herein also encompass embodiments in which techniques are implemented to reduce an amount of buffered operational data conveyed to a remote computing device for analysis. Particularly where the data link from the vehicle to the remote computing device is wireless (such as cellular or satellite based communications), data transmission rates represent a cost that can be controlled.
- the concepts disclosed herein encompass a variety of filtering techniques that can be used to determine if a particular condition exists, such that when such a predefined condition exists, the buffered operational data will not be sent to the remote computing device, even if an anomalous condition is detected.
- One such filtering technique is based on detecting (using a position sensing component) a location of the vehicle at startup.
- the automated buffered operational data transmission functionality can be turned off (as the vehicle will likely be coupled to a diagnostic device at the service center, such that the remote diagnostic function is not needed).
- Such locations can be stored in a memory at the vehicle, or more preferably, the vehicle can communicate its location at start up to the remote computing device, which has access to the locations of such service centers.
- the remote computing device determines if the processor in the vehicle responsible for controlling transmission of the buffered operational data to the remote computing device should be instructed not to transmit such data.
- Another such filter technique is based on analyzing whether the same anomalous conditions are detected in about the same geographic position and/or within a predefined time period (which can indicate that the vehicle is being driven around a service facility trying to replicate an intermittent fault).
- Another technique that can be used to reduce the amount of buffered operational data that is wirelessly conveyed to a remote computing device is to ensure that duplicate information, related to the same anomalous condition, is not sent time and time again.
- an occurrence counter in a diagnostic trouble code (DTC) is analyzed to determine if a particular fault code is a reoccurring event that can be ignored to minimize an amount of data that is transmitted wirelessly.
- DTC diagnostic trouble code
- the concepts disclosed herein also encompass embodiments in which the processor controlling the collection and transmission of buffered operational data is configured to either ignore operational data generated during an initial start-up of the vehicle (referred to as settling time. This technique will result in no buffered operational data and anomalous condition data being wirelessly conveyed to a remote computing device until after a predetermined settling time has elapsed.
- the buffered operational data sent to the remote computing device can be: (1) operational data collected before the anomaly; (2) operational data collected after the anomaly; and (3) a combination of operational data collected before the anomaly and after the anomaly.
- a processor in the vehicle is configured to monitor dashboard lamps, to determine if any warning indicator lamps on the vehicle dashboard change in response to the recently detected anomalous condition.
- a lamp status change i.e., from off to on, or from amber/yellow to red, indicating an escalation
- a controller in the vehicle is configured to enable an operator of the vehicle to manually trigger the transmission of buffered operational data to the remote computing device.
- This can be used to enable an operator who is concerned that something unusual might be occurring in regard to vehicle operation, so that buffered operational data can be analyzed at a remote computing device to determine if there really is an operational issue with the vehicle.
- the processor in the vehicle tasked with monitoring the operational data to detect an anomalous condition may not have detected such an anomalous condition, in which case only the buffered operational data will be conveyed to the remote computing device (i.e., data defining the anomalous condition will not be present, thus will not be sent to the remote computing device).
- an indication that the operator of the vehicle triggered the data transmission can be included, so the analysis of the buffered operational data at the remote computing device can proceed with the understanding that the operator of the vehicle suspects a problem exists, even if an anomalous condition has not be detected at the vehicle by the vehicle hardware monitoring the operational data for such an anomalous condition.
- the vehicle can be equipped with a user input specifically configured to enable the vehicle operator to trigger the transmission of the current buffered operational data to the remote computing device (i.e., a button, rocker panel, switch or other user input that is added to the vehicle).
- an existing operator input element is modified to support such a triggering function.
- a control device used to control vehicle equipment such a headlight or radio can be used as a trigger, if the processor controlling the transmission of the buffered operational data is coupled to the control device, and configured to respond to a certain input pattern from the control device (i.e., the control device is manipulated by the operator in a predefined and unusual pattern, such as repeatedly manipulating the control device in a specific and unusual sequence not normally employed in routine vehicle operations).
- the controller responsible for sending the buffered operational data to the remote computing device is configured to recognize repeatedly turning the radio on and off in a specific predefined pattern as an operator trigger signal, requiring the processor to use the data link to upload the contents of the data buffer to the remote computing device.
- FIG. 1 is a high level logic diagram showing exemplary overall method steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time;
- FIG. 2 is a functional block diagram of an exemplary computing device that can be employed to implement some of the method steps disclosed herein;
- FIG. 3 is a functional block diagram of an exemplary vehicle employed to implement some of the concepts disclosed herein;
- FIG. 4 is an exemplary functional block diagram showing the basic functional components used to implement the method steps of FIG. 1 ;
- FIG. 5 is another exemplary functional block diagram showing the basic functional components used to implement the method steps of FIG. 1 ;
- FIG. 6 is a functional block diagram of an exemplary diagnostic unit including a position sensing component that can be added to a vehicle to implement some of the concepts disclosed herein;
- FIG. 7 is a functional block diagram of exemplary processor functions that can be implemented in the diagnostic unit of FIG. 6 ;
- FIG. 8 is a flow chart showing exemplary steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time, the method of FIG. 8 including some additional functions as compared to the method of FIG. 1 .
- a reference to an activity that occurs in real-time is intended to refer not only to an activity that occurs with no delay, but also to an activity that occurs with a relatively short delay (i.e., a delay or lag period of seconds or minutes, but with less than an hour of lag time).
- FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one aspect of the concepts disclosed herein, to convey data defining an anomalous vehicle condition along with operational data (collected from the vehicle proximate to the detection of the anomaly) to a remote computing device, so that the cause of the anomaly can be diagnosed in real-time.
- Vehicle fault codes represent an exemplary type of anomaly.
- fault codes are used to facilitate diagnosis of vehicle problems, however, the operational data discussed herein is not used in addition to the fault codes to diagnose vehicle problems. Providing such operational data in addition to the data defining the anomaly (such as a fault code) will facilitate more accurate diagnoses.
- each vehicle enrolled in the diagnostic system is equipped with components to collect operational data, a data buffer in which operational data is temporarily stored, a processor to detect anomalous conditions (such as anomalous conditions corresponding to predefined fault codes), and a data link to convey the data defining the anomalous condition and contents of the data buffer to a remote computing device for diagnosis.
- anomalous conditions such as anomalous conditions corresponding to predefined fault codes
- a data link to convey the data defining the anomalous condition and contents of the data buffer to a remote computing device for diagnosis.
- a majority of vehicles manufactured today already include components to collect operational data during operation of the vehicle. Such data is used during operation of the vehicle, to provide feedback to control many vehicle systems, including but not limited to engine fuel supply components, vehicle braking components, vehicle cooling components, and vehicle transmission components.
- such vehicles are modified to include a data buffer in which this operational data is temporarily stored.
- Such operational data is generated, used to control operation of the vehicle (or used for diagnostic purposes when the vehicle is coupled to a diagnostic unit in a service bay), and then discarded. Further modifications include configuring a processor in the vehicle to convey detected vehicle anomalies and the contents of the data buffer when the anomaly is detected to the remote computing device for diagnosis.
- the data buffer can be configured as desired to include operational data collected before the anomaly occurs, after the anomaly occurs, or both.
- a temporal extent of the operational data conveyed to the remote computing device along with the data defining the anomaly, both before and after the anomaly occurs is a user definable parameter.
- the buffer collects several minutes of data, in a first in, first out type data buffer.
- the data link is used to convey the anomaly (i.e., vehicle data that is identified as non-standard, or anomalous, which in an exemplary, but not limiting embodiment, is represented by a fault code, which is a numeric or alphanumeric value corresponding to a predefined fault condition) and the contents of the data buffer (in some embodiments the entire contents of the data buffer is sent, whereas in other embodiments less than the entire contents of the data buffer is sent along with the anomaly) to a remote computing device for analysis.
- the fault code and contents of the data buffer may be sent to more than one remote computing device before analysis of the data is implemented.
- the fault code and contents of the data buffer are wirelessly conveyed from the vehicle (in real-time) to a computing device (which may be a network of linked devices as opposed to a single computing device) operated by the vehicle owner or a vendor providing a service to the vehicle owner.
- the data is stored therein, and then conveyed to a different remote computing device (which itself maybe a network of linked devices as opposed to a single computing device) operated by a vendor providing diagnostic services to the vehicle owner.
- a processor at a remote location is used to analyze the fault code (or other data defining the detected anomalous or non-standard data) and the contents of the data buffer conveyed from the vehicle to identify a cause of the anomaly.
- the processor at the remote location may request additional data from the vehicle to facilitate the analysis or to confirm a diagnosis.
- the additional data is the contents of the data buffer at a subsequent time interval, while in other embodiments the additional data is specifically defined data that the vehicle collects and conveys.
- the remote computing device in at least one embodiment comprises a computing system controlled by the operator of the vehicle, while in other exemplary embodiments the computing system is controlled by a third party or vendor who manages the diagnostic service for the operators of the enrolled vehicles (in some embodiments, the third party bills the vehicle operators a subscription fee).
- the remote computing device can be operating in a networked environment.
- FIG. 2 schematically illustrates an exemplary computing system 250 suitable for use in implementing the method of FIG. 1 (i.e., for executing at least block 14 of FIG. 1 , and in some embodiments block 16 as well).
- Exemplary computing system 250 includes a processing unit 254 that is functionally coupled to an input device 252 and to an output device 262 , e.g., a display (which can be used to output a result to a user, although such a result can also be stored).
- Processing unit 254 comprises, for example, a central processing unit (CPU) 258 that executes machine instructions for carrying out an analysis data collected from enrolled vehicles, to diagnose a mechanical fault (or other vehicle anomaly).
- the machine instructions implement functions generally consistent with those described above with respect to block 14 of FIG. 1 .
- CPUs suitable for this purpose are available, for example, from Intel Corporation, AMD Corporation, Motorola Corporation, and other sources, as will be well known to those of ordinary skill in this art.
- RAM random access memory
- non-volatile memory 260 which can include read only memory (ROM) and may include some form of memory storage, such as a hard drive, optical disk (and drive), etc. These memory devices are bi-directionally coupled to CPU 258 . Such storage devices are well known in the art. Machine instructions and data are temporarily loaded into RAM 256 from non-volatile memory 260 . Also stored in the non-volatile memory are an operating system software and ancillary software. While not separately shown, it will be understood that a generally conventional power supply will be included to provide electrical power at voltage and current levels appropriate to energize computing system 250 .
- Input device 252 can be any device or mechanism that facilitates user input into the operating environment, including, but not limited to, one or more of a mouse or other pointing device, a keyboard, a microphone, a modem, or other input device.
- the input device will be used to initially configure computing system 250 , to achieve the desired processing (i.e., to analyze performance data from a vehicle to detect a mechanical or other fault).
- Configuration of computing system 250 to achieve the desired processing includes the steps of loading appropriate processing software into non-volatile memory 260 , and launching the processing application (e.g., loading the processing software into RAM 256 for execution by the CPU) so that the processing application is ready for use.
- Output device 262 generally includes any device that produces output information, but will most typically comprise a monitor or computer display designed for human visual perception of output. Use of a conventional computer keyboard for input device 252 and a computer display for output device 262 should be considered as exemplary, rather than as limiting on the scope of this system.
- Data link 264 is configured to enable vehicle anomaly data and buffered operational data collected in connection with operation of enrolled vehicles to be input into computing system 250 for analysis to determine a cause of the anomalous data.
- USB universal serial bus
- Fire Wire ports Fire Wire ports
- infrared data ports wireless data communication
- Wi-Fi and BluetoothTM network connections via Ethernet ports
- vehicle data from the enrolled vehicles will be communicated wirelessly, either directly to the remote computing system that analyzes the data to diagnose the anomaly, or to some storage location or other computing system that is linked to computing system 250 .
- the vehicle anomaly data and buffered operational data collected in connection with operation of enrolled vehicles is wirelessly transmitted in a compact binary format to a first server, where the data is converted to a different format for transmission to a second server over a computer network, such as the Internet.
- the second format is XML.
- remote computer and the term remote computing device are intended to encompass networked computers, including servers and clients, in private networks or as part of the Internet.
- the buffered operational data and anomaly defining data can be stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network.
- a vendor is responsible for diagnosing the operational data and anomaly defining data, and clients of the vendor are able to access and review such data, as well as any resulting diagnoses. While implementation of the method noted above has been discussed in terms of execution of machine instructions by a processor (i.e., the computing device implementing machine instructions to implement the specific functions noted above), the method could also be implemented using a custom circuit (such as an application specific integrated circuit).
- FIG. 3 is a functional block diagram of exemplary components used in vehicles enrolled in the vehicle diagnostic service, which are used in each enrolled vehicle 41 to implement some of the method steps shown in FIG. 1 .
- An exemplary vehicle diagnostic service is based on adding a data buffer 46 and a bi-directional data link 43 to each enrolled vehicle.
- this data link is a combination RF transmitter and receiver, although separate transmitters and receivers could be used. If the vehicle does not already include operational data collecting components 40 , such components are added.
- the vehicle includes at least one processor 42 that performs the functions of temporarily storing operational data from components 40 in data buffer 46 , detecting an anomalous condition in the vehicle, and in response to detecting such an anomaly, using bi-directional data link 43 to convey real-time anomaly data and the buffered operational data from the enrolled vehicle to a remote computing device 44 (which is used to determine or diagnose a cause for the detected anomaly).
- processor functions can be implemented by a single processor, or distributed across multiple processors.
- data from the vehicle is read by the microcontroller implementing processor 42 before moving into buffer 46 , as is as would be typical of using a microcontroller to read data from most any data connection.
- the data buffer, data link, and processor responsible for triggering the transmission of buffered data to the remote computing device are combined into a single component.
- an output 45 is also included, to provide diagnostic related information to the driver in a form that can be easily understood by the driver.
- Output 45 can be implemented using one or more lights (for example, a red light can be used to indicate that a problem has been detected which requires the operator to stop the vehicle, or to modify vehicle operations (for example, to slow down or otherwise reduce a load being placed on the vehicle until a repair can be made), using a speaker providing an audible output, and using a display providing a visual output.
- output 45 can be combined into a single component with the data buffer and the data link, so only a single additional component is added to the vehicle (recognizing that most vehicles already include the additional required components, such as the operational data collecting components and the processor, although in at least some embodiments an additional processor is added to the vehicle to control the triggering of the transmission of buffered operational data to the remote computing device).
- the concepts disclosed herein are in at least some embodiments intended to be used by fleet owners operating multiple vehicles, and the anomaly defining data and buffered operational data conveyed to the remote location for diagnosis will include an ID component that enables each enrolled vehicle to be uniquely identified.
- FIG. 4 is a functional block diagram of an exemplary system 50 that can be employed to implement the method steps of FIG. 1 .
- the components include at least one enrolled vehicle 52 (including the components discussed above in connection with FIG. 3 ), an optional repair facility 54 , a processor component 56 (in the vehicle) to implement the function of detecting an anomalous condition (such as detecting a fault code), a processor component 58 (also in the vehicle) to implement the function of conveying the fault code (or other data defining the detected anomaly) and contents of the operational data buffer to a remote location, and a remote processor component 60 to implement the function of analyzing the fault code (or other data defining the detected anomaly) and contents of the data buffer conveyed from the vehicle to determine a cause for the anomaly.
- processor component 56 and 58 can be the same, or different processors in the vehicle.
- FIG. 5 is another functional block diagram showing the components of a vehicle diagnostic system in accord with the concepts disclosed herein, where the data link and data buffer are combined into a single component to be added to a vehicle to enable the vehicle to participate in the diagnostic program.
- a system 62 includes a vehicle 64 and a remote computing device 72 for performing diagnostic analysis on data supplied by the vehicle over a wireless network 70 .
- Vehicle 64 includes a plurality of components for collecting operational data, including a brake control unit 66 a , an engine control unit 66 b , and a transmission control unit 66 c , each of which transmit operational data along a data bus 67 . While only a single data bus is shown, it should be understood that multiple data buses could be employed. Further, a vehicle controller/processor, such as is shown in FIG. 3 , is not illustrated in FIG. 5 , but one or more such elements will be coupled to the data bus to receive and use operational data generated by the vehicle.
- Vehicle 64 also includes an add-on diagnostic unit 68 , which combines a data buffer, a data link, and a processor implementing one or more of the functions associated with processor components 56 and 58 of FIG. 4 into a single device (noting that the vehicle's own processors could also be configured to implement such functions, particularly the function of detecting an anomalous condition, if desired).
- an add-on diagnostic unit 68 which combines a data buffer, a data link, and a processor implementing one or more of the functions associated with processor components 56 and 58 of FIG. 4 into a single device (noting that the vehicle's own processors could also be configured to implement such functions, particularly the function of detecting an anomalous condition, if desired).
- Diagnostic unit 68 conveys diagnostic logs 76 from vehicle 64 to remote computer 72 via wireless network 70 , generally as discussed above. Diagnostic logs 76 include an identified anomaly (such as a fault code) and data stored in the data buffer portion of diagnostic unit 68 . Remote computer 72 analyzes the diagnostic logs to determine a cause of the anomaly. Remote computer 72 conveys data 74 (which includes one or more of configuration data and diagnostic data) to diagnostic device 68 via the wireless network. The configuration data is used to modify the functions implemented by the processor in diagnostic unit 68 .
- Modifications includes, but are not limited to, changing the amount of operational data to be stored in the data buffer, changing an amount of operational data collected before an anomaly that is conveyed to the remote computing device, changing an amount of operational data collected after an anomaly that is conveyed to the remote computing device, changing a type of operational data that is conveyed to the remote computing device (this enables the remote computing device to request specific types of operational data after a diagnostic log has been received, to facilitate diagnosing the anomaly), and changing a definition of what constitutes an anomaly.
- the diagnostic data includes data conveyed to the operator of the vehicle, informing the operator of what actions the operator needs to take in response to the diagnosis. Such diagnostic data can include instructions to cease vehicle operations as soon as possible to avoid unsafe or damaging conditions, instructions to proceed to a designated repair facility, and/or instructions to proceed with a scheduled route, and to wait to repair the vehicle when the route is complete.
- diagnostic device 68 is implemented by using a hardware device installed onboard medium and heavy duty (Class 5 - 8 ) vehicles that is permanently or temporarily installed, powered from onboard vehicle power systems, connected to the in-vehicle diagnostic data communications network, capable of collecting diagnostic data from the vehicle data communications network and sending it to an off board server.
- the specific information to be acquired from the vehicle communications data link is remotely configurable.
- the specific data messages that trigger a data collection event are also remotely configurable.
- Data transmission from the vehicle includes a wireless interface between the vehicle and the off board server, such as a cellular modem or other similar wireless data transmission method. Data received at the off board server may then be forwarded to any defined set of consumers for the diagnostic information to be remotely analyzed and acted upon.
- the components of system 62 include the hardware device used to implement diagnostic device 68 , hardware programming (firmware), the wireless network, and the remote computing device (such as a computer server/data center).
- System 62 operates by using the remote computing device to transmit programming/configuration data to the in-vehicle device (i.e., diagnostic device 68 ) via the wireless network.
- the diagnostic data device stores operational data to include with all diagnostic log events (i.e., with each fault code or detected anomaly).
- the diagnostic log conveyed to the remote computing device from the vehicle includes data such as a diagnostic log file revision, a diagnostic log file type, a device ID, a configured time interval defining the extent of buffered operational data, and the number of parameters to be stored in the diagnostic log files.
- the diagnostic data device in the vehicle performs the functions of: storing a list of diagnostic parameters to be monitored and recorded from the vehicle data link at regular periodic intervals; storing a list of event parameters to trigger diagnostic data capture; and storing a time interval for diagnostic parameter recording.
- the diagnostic data device is connected to an in-vehicle data link (e.g., a 11939 bus) and vehicle power connections.
- diagnostic data device is continuously monitoring for specific data messages configured to trigger the collection of diagnostic log files. Once diagnostic log files are recorded, they are transmitted via the wireless network to the remote computing device. Diagnostic log files are moved from the data center server within minutes to a destination server where the data may be analyzed and/or distributed for further action.
- the diagnostic log sent to the remote computing device includes one minute worth of operational data collected both before and after the anomalous event.
- the diagnostic log sent to the remote computing device includes the following types of operational data: any user defined fault code that has been detected, any vehicle manufacturer defined fault code that has been detected, a position of the vehicle at the time the fault code is detected (if the vehicle includes a position sensor), trip start and end times, odometer value and source address, engine hours and source address, power take off (PTO) hours and source address, total fuel and source address, idle fuel and source address, PTO Fuel and source address, VIN and source address, and trip fuel economy calculated from odometer and total fuel values listed above.
- the processor in the vehicle configured to assemble the vehicle data (including buffered operational data and data defining the anomaly that was detected) to be uploaded to the remote computing can be configured to always send the same types of data to the remote computing device for each anomaly detected, or the processor can be configured to send specific types of data to the remote computing device based on the anomaly detected.
- the processor can be configured to send specific types of data to the remote computing device based on the anomaly detected.
- the processor can be configured to always send the same types of data to the remote computing device for each anomaly detected, or the processor can be configured to send specific types of data to the remote computing device based on the anomaly detected.
- the processor can be configured to always send the same types of data to the remote computing device for each anomaly detected, or the processor can be configured to send specific types of data to the remote computing device based on the anomaly detected.
- brake temperature data oil temperature data
- fuel level data fuel level data
- engine hour data coolant temperature data
- tire pressure data such types of data being exemplary, and not limiting
- only a subset of the most likely relevant data is sent to the remote computing device (for example, if the anomaly deals with brakes, then brake temperature data and tire pressure data is sent, but other types of data having less to do with the vehicle braking system are not sent to the remote computing device).
- the diagnostic device in the vehicle can be remotely configured to redefine the parameters used to generate a diagnostic log.
- the diagnostic log generated by the diagnostic device includes two primary components; at least some of the operational data temporarily stored in the data buffer, and data defining the anomaly (in some embodiments, fault codes are used to define the anomaly).
- the diagnostic device can be remotely reconfigured to change an amount of buffered operational data acquired before the anomaly that is included in the diagnostic log.
- the diagnostic device can be remotely reconfigured to change an amount of buffered operational data acquired after the anomaly that is included in the diagnostic log.
- the diagnostic device can be remotely reconfigured to change the type of operational data that is included in the diagnostic log (in the terms of FIG.
- the diagnostic device can be remotely reconfigured to selectively determine whether data from brake control unit 66 a , data from engine control unit 66 b , and/or data from transmission control unit 66 c should be included in the diagnostic log, noting that such operational data generating components are exemplary, and not limiting).
- the diagnostic device can also be remotely reconfigured to define what constitutes an anomaly that triggers sending a diagnostic log to the remote computing device for diagnosis. As discussed above, fault codes defined by the vehicle manufacturer can be considered to be anomalies that will trigger conveying a diagnostic log to the remote location.
- the concepts disclosed herein encompass enabling the diagnostic device to be remotely reconfigured to define a single parameter or a set of parameters (beyond the parameters used by manufacturers to define fault codes) that will trigger the conveyance of diagnostic log to the remote location.
- the diagnostic device can be remotely reconfigured to generate and convey a diagnostic log to the remote location in response to detecting any specified parameter or set parameters.
- FIG. 6 is a functional block diagram of an exemplary diagnostic unit including a position sensing component that can be added to a vehicle to implement some of the concepts disclosed herein.
- a diagnostic (or telematics) unit 100 includes at least one data port 102 enabling vehicle operational data to be input into unit 100 (in an exemplary, but not limiting unit, a port for 11939 data and a port for 11708 data are provided, recognizing that such types of data are exemplary, and not limiting), a buffer 108 where operational data is temporarily stored, a GPS component 110 for determining vehicle location (which, as discussed below, can in certain embodiments be used to influence when the contents of the data buffer is transmitted to the remote computing device for analysis), a wireless data link 104 for sending operational data in the buffer to the remote computing device for analysis of an anomalous condition, and a processor 106 (for implementing at least the function of causing the buffered operational data to be conveyed via the data link to a remote computing device when an anomalous condition is detected).
- a data port 102 enabling vehicle operational data to be input into unit 100 (in an exemplary, but not limiting unit, a port for 11939 data and a port for 11708 data
- FIG. 6 also shows an optional operator trigger 111 , that an operator of the vehicle can actuate to cause processor 106 to use the data link to send the contents of the buffer to the remote computing device.
- the operator is determining that some anomalous condition has occurred which should be investigated. Perhaps the driver feels an odd vibration, hears an odd engine noise, or otherwise perceives some abnormal condition.
- the trigger 111 is coupled to controller 106 , which is configured to respond by sending the buffered operational data to the remote computing device.
- the processor in the vehicle tasked with monitoring the operational data to detect an anomalous condition may not have detected such an anomalous condition, in which case only the buffered operational data will be conveyed to the remote computing device (i.e., data defining the anomalous condition will not be present, thus will not be sent to the remote computing device).
- the buffered operational data will be conveyed to the remote computing device (i.e., data defining the anomalous condition will not be present, thus will not be sent to the remote computing device).
- an indication that the operator of the vehicle triggered the data transmission can be included, so the analysis of the buffered operational data at the remote computing device can proceed with the understanding that the operator of the vehicle suspects a problem exists, even if an anomalous condition has not be detected at the vehicle by the vehicle hardware monitoring the operational data for such an anomalous condition.
- Trigger 111 can be implemented with a dedicated user input device (only used to trigger sending the contents of the data buffer to the remote computing device), or an existing operator input element is modified to support such a triggering function.
- a control device used to control vehicle equipment such a headlight or radio can be used as a trigger, if the processor controlling the transmission of the buffered operational data is coupled to the control device, and configured to respond to a certain input pattern from the control device (i.e., the control device is manipulated by the operator in a predefined and unusual pattern, such as repeatedly manipulating the control device in a specific and unusual sequence not normally employed in routine vehicle operations).
- Buffer 108 can be implemented as a first in, first out buffer that temporarily stores the operational data generated by the vehicle in normal operation, which conventionally is generated and discarded rather than being saved. Buffer 108 is intended to be relatively small, and not intended to attempt to archive all of the operational data generated by the vehicle for an extended period of operation. Rather, buffer 108 is intended to store relatively small, but still useful amounts of operational data. In an exemplary, but not limiting embodiment, the amount of operational data stored in buffer 108 represents seconds or minutes of data, rather than hours or days of data. In an exemplary, but not limiting embodiment, buffer 108 is implemented using flash memory, of less than a gigabyte. With memory prices dropping regularly, more operational data could be stored.
- wireless transmission of data represents a cost
- a balance between the amount of data collected (more data leading to better diagnoses) and the amount of data wirelessly transmitted (less data being transmitted meaning less cost) is sought.
- Empirical studies have indicated that useful amounts of data can be obtained using a buffer of 256 MB or less and data transmissions of less than about 30 kilobytes per anomaly.
- Processor 106 implements at least the function of using the data link to send the contents of the buffer (or at least a portion of the contents) to the remote computing device when an anomalous event occurs. In some embodiments, processor 106 implements additional functions. In at least one embodiment, processor 106 analyzes the operational data to detect specific conditions that have been predetermined to represent an anomaly that should trigger the transmission of the buffer to the remote computing device. In at least some embodiments, the data link can be used to enable changes to be made to the logic used by the processor to determine what represents an anomaly.
- a different processor in the vehicle is determining when an anomalous condition occurs.
- any processor in a vehicle that generates a fault code based on specific operational data can be configured to send that fault code to processor 106 , so that processor 106 responds by using the data link to send the fault code and the contents of the data buffer to the remote computing device.
- FIG. 7 IS a functional block diagram of exemplary processor functions that can be implemented in the diagnostic unit of FIG. 6 .
- a block 112 corresponds to the function of analyzing the operational data generated by the vehicle to detect an anomalous condition. This function is generally implemented when parameters other than manufacturer designated fault codes (which are generally detected by other processors in the vehicle) are used to define an anomaly.
- a block 114 refers to the function of applying specific logic (i.e., a filter) to reduce an amount of data that might otherwise be sent to the remote computing device, as will be discussed below).
- a block 116 refers to the function of using the data link to send the buffered operational data to the remote computing device based on a trigger event (such as an operator trigger, a fault code detected by some other processor, or an anomalous condition detected by processor 106 ).
- a block 118 refers to the function of using the data link to send lamp escalation data to the remote computing device after buffered operational data corresponding to a previously detected anomalous condition has been sent, in the event that an indicator lamp has changed status since the anomalous event (this function is discussed in detail below).
- blocks 112 , 116 , and 118 are shown in dashed lines, as such functions can be considered optional, and such functions are not implemented in all embodiments.
- block 114 refers to the function of applying specific logic (i.e., one or more filters) to reduce an amount of data that might otherwise be sent to the remote computing device.
- logic i.e., one or more filters
- such logic is implemented to reduce an amount of buffered operational data conveyed to a remote computing device for analysis, as a cost control function.
- the concepts disclosed herein encompass a variety of filtering techniques that can be used to determine if a particular condition exists, such that when such a predefined condition exists, the buffered operational data will not be sent to the remote computing device, even if an anomalous condition is detected.
- One such filtering technique is based on detecting (using GPS component 110 ) a location of the vehicle at startup.
- the automated buffered operational data transmission functionality can be turned off (as the vehicle will likely be coupled to a diagnostic device at the service center, such that the remote diagnostic function is not needed).
- Such locations can be stored in a memory at the vehicle, or more preferably, the vehicle can communicate its location at start up to the remote computing device, which has access to the locations of such service centers.
- the remote computing device determines if processor 106 should be instructed (via data link 104 ) not to transmit the buffered operational data to the remote computing device even if an anomaly is detected.
- controller 106 is configured to not to transmit the buffered operational data to the remote computing device even if an anomaly is detected, if the vehicle remains within a relatively small geographical area (i.e., within five miles or so, such an area being exemplary and not limiting) in a predefined period of time (such as 24 hours, again recognizing that the specified interval is exemplary, and not limiting).
- Another technique that can be used to reduce the amount of buffered operational data that is wirelessly conveyed to a remote computing device is to ensure that duplicate information, related to the same anomalous condition, is not sent time and time again.
- an occurrence counter in a diagnostic trouble code (DTC) generated in the vehicle is analyzed to determine if a particular fault code is a reoccurring event that can be ignored to minimize an amount of data that is transmitted wirelessly to the remote computing device for analysis.
- Processor 106 can be configured to send repeating fault codes/anomalies, when the re-occurring anomaly is accompanied by a new anomaly.
- processor 106 is configured to either ignore operational data generated during an initial startup of the vehicle (referred to as settling time).
- settling time operational data generated during an initial startup of the vehicle.
- controller 106 is configured to ignore, or not to store, about the first ten seconds of operational data that is generated upon vehicle startup.
- Vehicle startup can also present the unusual condition where the data buffer may not have filled to capacity. Assume the data buffer is configured to store 90 seconds of operational data, and an anomalous condition is detected 45 seconds after operational data began to fill up the buffer.
- Controller 106 can be configured to send only the 45 seconds present in the buffer, or can be configured to not transmit any portion of the buffer, if the buffer is not full, depending on the logic one wishes to employ. Partial data is likely to be more useful than no data, so the former technique is more likely to be implemented.
- block 118 refers to the function of using the data link to send lamp escalation data to the remote computing device after buffered operational data corresponding to a previously detected anomalous condition has been sent, in the event that an indicator lamp has changed status since the anomalous event.
- processor 106 is configured to monitor dashboard lamps, to determine if any warning indicator lamps on the vehicle dashboard change in response to the recently detected anomalous condition. When such a lamp status change (i.e., from off to on, or from amber/yellow to red, indicating an escalation) is detected, processor 106 is configured to use data link 104 to send information defining the change in the lamp status to the remote computing device.
- the fault code data may include lamp status, but that information is not necessarily accurate, and even when accurate the buffered operational data may not capture a change in lamp status that occurs at a time point after the anomaly has occurred.
- processor 106 can be implemented via hardware (such as an application specific integrated circuit implementing fixed logical steps), or a controller implementing software (i.e., a series of logical steps). Processor 106 can be a single component, or different functions described above that are implemented by processor 106 can be distributed across multiple processors.
- processor 106 is configured to include data from GPS component 110 with the buffered operational data, when such data is conveyed to the remote computing device via data link 104 .
- FIG. 8 is a flow chart showing exemplary steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time, where the method of FIG. 8 includes some additional functions as compared to the method of FIG. 1 .
- FIG. 8 is discussed in terms of diagnostic unit 100 of FIG. 6 , but it should be recognized that the steps of FIG. 8 could be implemented in embodiments having different configurations than the diagnostic unit of FIG. 6 .
- diagnostic unit 100 of FIG. 6 powers on.
- operational data generated during an initial settling period (generally measured in seconds, an exemplary settling period being 10 seconds, with the understanding that such a time period is exemplary, and not limiting) is ignored.
- any fault codes or anomalous events occurring in the settling period are also ignored.
- operational data in the settling period can be stored in the data buffer, but fault codes or anomalous events in the settling period are ignored, such that no operational data is sent to the remote computing device until after the settling period has elapsed.
- operational data is stored in a first in, first out buffer.
- at least one processor in the vehicle (which in some embodiments is processor 106 of FIG.
- a different processor in the vehicle determines if an anomalous event has occurred (either by monitoring the operational data itself, or by waiting for a fault code or anomalous condition to be detected by some other vehicle processor). If not, operational data in the data buffer is continuously updated (for example, for each new second of new data added to the buffer, the oldest second of data is discarded, recognizing that the stated one second intervals being added/discarded is exemplary, and not limiting).
- processor 106 takes the contents of the buffer, collects an additional amount of operational data after anomaly is detected (in an exemplary embodiment, an additional 10-20 seconds of operational data is acquired, noting that such a time period is exemplary, and not limiting), and uses the data link to send the buffered operational data collected before and after the anomaly is detected, and data defining the anomaly, to the remote computing device.
- This data is sent as a compact binary file to minimize data transmission costs.
- the binary data file is translated into another format (such as XML), and then sent via a computer network to a secondary server for analysis, as indicated in a block 134 .
- Blocks 132 and 134 are useful in embodiments where a first server where the data is originally received from the vehicle is operated by a first entity (such as an entity that collects and stores GPS data transmitted from the vehicle during routine vehicle operation (such data being collected even when no anomalous event is detected), and the buffered operational data and data defining the anomalous event are conveyed from the server/remote computing device operated by the first entity to a server/remote computing device operated by a second entity (the second entity being responsible for performing the service of diagnosing the buffered operational data to determine the cause of the anomaly).
- a first entity such as an entity that collects and stores GPS data transmitted from the vehicle during routine vehicle operation (such data being collected even when no anomalous event is detected)
- the buffered operational data and data defining the anomalous event are conveyed from the server/remote computing device operated by the first entity to a server/remote computing device operated by a second entity (the second entity being responsible for performing the service of diagnosing the buffered operational data to determine
- the concepts disclosed herein encompass at least one embodiment implemented as a system in which diagnostic units such as those shown in FIG. 6 are included in a plurality of enrolled vehicles.
- a system includes a remote computing device (either an individual computing device, or a network of such devices), where the buffered operational data and the data defining the anomalous condition (such as a fault code) can be stored or analyzed (i.e., diagnosed).
- vehicle position data and/or inspection data is collected from enrolled vehicles and stored at a first server, operated by a first entity, for use by the operator of the vehicles. Such data is collected during normal operation of the vehicle, and sent to the first server during normal operation of a vehicle.
- the buffered operational data and the data defining the anomalous condition are sent from the vehicle to the first server.
- the first entity operating the first server then conveys the buffered operational data and the data defining the anomalous condition to a second server operated by a second entity.
- the second entity analyzes the buffered operational data and the data defining the anomalous condition and determines the cause of the anomalous condition.
- the vehicle operator can then be contacted to arrange servicing of the vehicle.
- the second entity is the manufacturer of the vehicle or the vehicle power plant.
- a first telematics unit for use in a vehicle comprising:
- a first data port for receiving operational data from the vehicle during operation of the vehicle;
- a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle;
- a data link for wirelessly conveying data from the vehicle to a remote computing device; and
- a processor configured to use the data link to send operational data from the buffer to the remote computing device when an anomalous condition is detected at the vehicle.
- the first telematics unit described above where the processor is configured to send a predefined additional quantity of operational data collected after the anomaly is detected to the remote computing device, along with buffered operational data collected before the anomaly is detected.
- the first telematics unit described above where the processor is configured to receive a notification from a different vehicle processor that is configured to detect the anomalous condition.
- the first telematics unit described above where the processor is configured to send buffered operational data to the remote computing device based on a trigger signal received from a vehicle operator, even if an anomalous condition has not been detected.
- the first telematics unit described above where after buffered operational data has been sent to the remote computing device in response to the detection of an anomalous condition, the processor is configured to monitor a warning lamp status associated with the anomaly, and to use the data link to send lamp escalation data to the remote computing device when that warning lamp changes condition.
- a second telematics unit for use in a vehicle comprising: (a) a positioning sensing component for collecting geographical position data from the vehicle during vehicle operation, the geographical position data being time indexed; (b) a data port for receiving operational data from the vehicle during operation of the vehicle; (c) a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle; (d) a data link for wirelessly conveying data from the vehicle to a remote computing device; and (e) a processor configured to use the data link to send operational data from the buffer to the remote computing device when an anomalous condition is detected at the vehicle.
- the second telematics unit described above where the processor is configured to send a predefined additional quantity of operational data collected after the anomaly is detected to the remote computing device, along with buffered operational data collected before the anomaly is detected.
- the second telematics unit described above where the processor is configured to determine a position of the vehicle at startup, and ignore anomalous conditions occurring while the vehicle's position is proximate to a known location where anomalous conditions should be ignored.
- the second telematics unit described above where the processor IS configured to determine a position of the vehicle at startup, then send a request to the remote computing device to determine if the position of the vehicle is proximate to a known location where anomalous conditions should be ignored, and if so, the processor is configured to ignore anomalous conditions occurring proximate that location.
- the second telematics unit described above where the processor is configured to send buffered operational data to the remote computing device based on a trigger signal received from a vehicle operator, even if an anomalous condition has not been detected.
- the processor is configured to monitor a warning lamp status associated with the anomaly, and to use the data link to send lamp escalation data to the remote computing device when that warning lamp changes condition.
- a system for detecting an anomalous condition with a vehicle and diagnosing that anomalous condition (a) a vehicle comprising: (i) at least one sensor for generating vehicle operational data; (ii) a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle; (iii) a data link for wirelessly conveying data from the vehicle to a remote location; and (iv) a processor configured to use the data link to send operational data from the buffer to the remote location when an anomalous condition is detected at the vehicle; and (b) a computing device at the remote location, the computing device being configured to implement the function of analyzing the buffered operational data received from the vehicle to diagnose the anomalous condition.
- Such an alert can be conveyed using at least one of a text message, an email message, and an automated telephone message.
- the processor in the vehicle is configured to include position data defining a location of the vehicle when the anomaly is detected with the data being conveyed to the remote computing device.
- each such predefined location is stored in the vehicle, while in other embodiments, upon startup the processor communicates with the remote computing device to determine if the vehicle's present location indicates that anomalies should be ignored.
- the processor in the vehicle is configured to monitor lamp status associated with a previously detected anomaly, and if the lamp status of a warning lamp associated with that anomaly changes, the processor is configured to convey lamp escalation data to the remote computing device.
- the processor in the vehicle is configured to convey buffered operational data to the remote computing device based on an operator trigger, even if no anomaly has been detected.
- the computing device at the remote location is configured to automatically schedule a repair of the vehicle based on a current location of the vehicle using location data received from the vehicle with the buffered operational data.
- the computing device at the remote location is configured to receive and store position data from the vehicle during normal operation of the vehicle, and when buffered operational data is received from the vehicle, the computing device automatically forwards the buffered operational data to a computing device operated by a different entity, the different entity performing the diagnosis.
- the buffered operational data received by the first entity may require reformatting to a different data format, such as XML, before sending the data to the second entity for analysis.
- a method for detecting an anomalous condition with a vehicle and diagnosing that anomalous condition including the steps of: (a) storing operational data generated while operating a vehicle in a first in, first out buffer during operation of the vehicle; (b) detecting an anomalous condition; (c) using a data link to wirelessly convey buffered operational data from the vehicle to a remote location; and (d) analyzing the buffered operational data at the remote location to diagnose the anomalous condition.
- a computing device at the remote location IS configured to automatically alert the operator of the vehicle about the diagnosis.
- Such an alert can be conveyed using at least one of a text message, an email message, and an automated telephone message.
- a processor in the vehicle is configured to include position data defining a location of the vehicle when the anomaly is detected with the data being conveyed to the remote location.
- a processor in the vehicle is configured to ignore anomalies, and thus not send data to the remote location, for a predetermined period of time following vehicle startup.
- a processor in the vehicle is configured to ignore anomalies when a location of the vehicle at startup corresponds to a predefined location.
- each such predefined location is stored in the vehicle, while in other embodiments, upon startup the processor communicates with a remote computing device to determine if the vehicle's present location indicates that anomalies should be ignored.
- a processor in the vehicle is configured to monitor lamp status associated with a previously detected anomaly, and if the lamp status of a warning lamp associated with that anomaly changes, the processor is configured to convey lamp escalation data to the remote computing device.
- a processor in the vehicle is configured to convey buffered operational data to the remote computing device based on an operator trigger, even if no anomaly has been detected.
- a computing device at the remote location is configured to automatically schedule a repair of the vehicle.
- a computing device at the remote location is configured to automatically schedule a repair of the vehicle based on a current location of the vehicle using location data received from the vehicle with the buffered operational data.
- a computing device at the remote location is configured to automatically order parts required to repair the vehicle.
- a computing device at the remote location is configured to receive and store position data from the vehicle during normal operation of the vehicle, and when buffered operational data is received from the vehicle, the computing device automatically forwards the buffered operational data to a computing device operated by a different entity, the different entity performing the diagnosis.
- the buffered operational data received by the first entity may require reformatting to a different data format, such as XML, before sending the data to the second entity for analysis.
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Accounting & Taxation (AREA)
- Tourism & Hospitality (AREA)
- Finance (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Biomedical Technology (AREA)
- Health & Medical Sciences (AREA)
- Chemical & Material Sciences (AREA)
- Combustion & Propulsion (AREA)
- Mechanical Engineering (AREA)
- Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)
- Selective Calling Equipment (AREA)
- Testing And Monitoring For Control Systems (AREA)
Abstract
Operational data generated and used in a vehicle to control various vehicular systems is temporarily stored in a data buffer in the vehicle. A processor in the vehicle is configured to detect anomalous conditions, which can be based on predefined fault codes or user defined conditions (based on a single parameter or a combination of parameters). Whenever such an anomaly is detected, a diagnostic log is conveyed from the vehicle to a remote location. Such a log will include the detected anomaly, and buffered operational data. In at least one embodiment, the diagnostic log includes buffered operational data collected both before and after the anomaly. The diagnostic log is analyzed at the remote location to diagnose the cause of the anomalous condition, so a decision can be made as to whether the vehicle requires immediate repair, or whether the repair can be scheduled at a later time.
Description
- This application is a continuation of copending patent application Ser. No. 13/219,467, filed on Aug. 26, 2011. Ser. No. 13/219,467 is based on a prior copending provisional application, Ser. No. 61/377,865, filed on Aug. 27, 2010, the benefit of the filing date of which is claimed under 35 U.S.C. §119(e). Ser. No. 13/219,467 is further a continuation-in-part of copending patent application, Ser. No. 12/956,961, filed on Nov. 30, 2010 (now abandoned), copending patent application, Ser. No. 13/157,184, filed on Jun. 9, 2011, and copending patent application, Ser. No. 13/157,203, also filed on Jun. 9, 2011, the benefits of the filing dates of which are claimed under 35 U.S.C. §120.
- Today's vehicles are equipped with many different types of data collection and processing components. Much of the data collected by the data collection components is used to control the operation of the vehicle. For example, data collected by oxygen sensors is used to control the amount of fuel introduced into the engine, to avoid providing an overly rich fuel mixture that would result in decreased fuel efficiency and increased emissions.
- Two broad classes of data include operational data and fault code data. As used herein and the claims that follow, the term operational data encompasses data that is used to control the operation of the vehicle, such as the data from oxygen sensors as noted above (data which is used by one or more vehicle controllers as feedback for controlling some aspect of the vehicles operation), or data that is simply generated during the operation of the vehicle (some vehicles generate operational data that is not used by any vehicle component during routine vehicle operation, but is rather used by diagnostic or service equipment during vehicle servicing or maintenance). In general, operational data is not stored, but rather is generated, contemporaneously used (either to control various vehicular systems or to provide data to diagnostic or service equipment during vehicle servicing), and then discarded. Exemplary operational data include, but is not limited to, engine coolant temperature, engine speed, oxygen levels, throttle position, brake temperature, vehicle speed, brake position, and gearbox parameters. Much of this data is collected very frequently, some types of operational data being collected multiple times per second. The sheer quantity of operational data being generated by the various vehicle components and subsystems makes storing or archiving all of such operational data problematical. Some vendors do provide data logging systems for temporary use in vehicles, where all the operational data generated by the vehicle is stored for later analysis, but such data logging systems are not designed for long term use.
- Fault code data somewhat addresses the problem of storing the enormous quantity of operational data generated by vehicles. Fault codes corresponding to specific undesirable operating parameters are predefined. A processor in the vehicle monitors the operational data as it is generated, and whenever an operating parameter corresponding to a specific predefined fault code is detected, the fault code is stored in a memory in the vehicle. The fault code is generally a numeric or alphanumeric value that can be stored using very little memory resources. For example, the number 11 can be defined as a fault code for the following condition: battery sensing voltage drops below 4 or between 7 and 8 volts for more than 20 seconds. Fault codes can be retrieved and used to diagnose vehicle problems. Even with the data provided by fault codes, accurate diagnosis of complex or unusual vehicular system failures can be problematical.
- It would be desirable to provide a vehicular diagnostic method and apparatus that provided more contextual data than available based on fault codes alone, which do not rely on storing all of the operational data produced by a vehicle.
- This application specifically incorporates by reference the disclosures and drawings of each patent application identified above as a related application.
- The concepts disclosed herein encompass temporarily storing operational data in a buffer in the vehicle, rather than simply discarding the operational data, and then archiving such buffered operational data whenever a fault code is generated. Such archived operational data combined with the fault code will provide a contextually rich data set that will greatly facilitate diagnosis of vehicle problems. The term combining does not require the archived or saved operational data and the fault code data to be stored in the same file location or data packet, rather, the term combining is used to indicate that a contextual link between the archived operational data and the fault code is generated, so that even if the archived operational data and the fault code are not stored together in a single file or data packet, the archived operational data corresponding to a particular fault code can be differentiated from archived operational data corresponding to a different fault code. Time indexing can be used to correlate specific archived operational data to specific fault codes, if the different types of data are to be stored separately.
- In at least one exemplary embodiment, the archived operational data corresponding to a particular fault code is ring buffered operational data, which includes operational data collected both before and after the fault code is detected. The amount of operational data before and after the fault code can be defined as desired, and need not be identical (that is, some users may prefer relatively more operational data after a fault code is detected, and relatively less operational data before a fault code is detected, or vice versa). In at least one exemplary embodiment, systems implementing the concepts disclosed herein are configured to enable the temporal extent of such a ring buffer to be a user adjustable parameter.
- In at least one exemplary embodiment, the contextually (and temporally) linked buffered operational data and fault code data are conveyed in real-time to a remote computing device, so that a diagnosis of a vehicle problem causing the generation of the fault code can occur while the vehicle is operational. Rapid diagnosis of problems can lead to the prevention of damage to the vehicle caused by continuing to operate the vehicle after a malfunction is detected, where the diagnosis indicates that continued operation of the vehicle would result in such damage. In such circumstances, the driver of the vehicle can be contacted to ensure that continued operation of the vehicle does not occur. If the diagnosed problem is relatively minor, the operator of the vehicle can be contacted with less urgency to arrange for a repair. In an exemplary, but not limiting embodiment, where continued operation of the vehicle is not likely to result in damage, the results of the vehicle diagnosis are forwarded to the vehicle operator, service for the vehicle is scheduled, and parts required for the service are ordered, all while the vehicle continues to operate.
- It should be recognized that the fault codes discussed above represent the detection of an anomalous vehicle condition identified by analyzing the operational data. The concepts disclosed herein encompass embodiments where real time analysis of the vehicle operational data at the vehicle indicates an anomalous condition exists, even when the anomalous condition does not correspond to a fault code predefined by the vehicle manufacturer. The controller in the vehicle tasked with the analysis of operational data to detect an anomalous condition can be configured as desired to detect specific conditions that a user has determined represents an anomaly. Thus, in at least one exemplary embodiment, buffered operational data is conveyed to a remote computing device whenever a user defined operating parameter is detected. In essence, this enables a user to define a custom fault code library (note that prior art fault codes are tied to specific operating parameters, however, prior art fault codes are predefined at the vehicle manufacturer level, and are not user modifiable or user defined). This concept is referred to herein and in the claims that follow as a user defined fault code. Such user defined fault codes can include any user defined single operational parameter, or a combination of user defined operational parameters, that are unique from the fault codes defined at the vehicle manufacturer level. In at least one exemplary embodiment, systems implementing the concepts disclosed herein are configured so that user defined fault codes can be defined and implemented while the vehicle is operational. In at least one exemplary embodiment, user defined fault codes are generated at a remote computing device attempting to acquire additional information to be used to diagnose a vehicle, where the user defined fault code is uniquely defined based on buffered operational data conveyed to the remote computing device while the vehicle is operating.
- It should be recognized that the concepts disclosed herein encompass embodiments in which the detection of an anomalous conditions triggers the transmission of the buffered operational data collected proximate the detection of the anomalous condition (and data defining the detected anomaly) to the remote computing device for analysis immediately (i.e., in real-time), or after only a relatively brief delay. In at least one exemplary embodiment, a wireless data link, such as a cellular data link, is used to transmit such data from the vehicle to the remote computing device. In at least one embodiment, if a data link cannot be established between the vehicle and the remote computing device to transmit the buffered operational data and data defining the detected anomaly immediately, then the buffered operational data collected proximate the detection of the anomalous condition (and the data defining the anomalous condition detected) can be stored at the vehicle and sent to the remote computing device when a data link can be established. The phrase buffered operational data collected proximate the detection of the anomalous condition is intended to encompass: (1) buffered operational data collected for a predefined period after the anomaly has been detected; (2) buffered operational data collected for a predefined period before the anomaly was detected; and (3) buffered operational data collected for a predefined period after the anomaly has been detected combined with buffered operational data collected for a predefined period before the anomaly was detected. Because the buffer temporarily stores operational data, some amount of operational data acquired before the anomalous event is detected is available (the amount of operational data available being a function of a size of the buffer).
- In at least one exemplary embodiment, the buffered operational data includes operational data that is automatically broadcast by the vehicle while the vehicle is operating. In at least one exemplary embodiment, the buffered operational data includes operational data that must be specifically requested. In yet another exemplary embodiment, the buffered operational data includes both operational data that is automatically broadcast by the vehicle while the vehicle is operating and operational data that must be specifically requested. In general, operational data that must be requested is operational data that can be generated upon request (such as throttle position data), but is not data that normally generated during routine vehicle operations.
- In addition to being implemented as a method, the concepts disclosed herein can also be implemented as a non-transitory memory medium, storing machine instructions that when executed by a processor implement the method, and by a system for implementing the method. In such a system, the basic elements include a vehicle, operational data collection components in the vehicle, a memory (i.e., a buffer) at the vehicle in which some amount of operational data is temporarily stored, and a vehicle processor for monitoring the operational data to detect an anomalous condition (i.e., to detect a fault code, manufacturer defined or user defined). Where vehicle diagnosis is to be performed in real-time at remote locations, a communication link (preferably bidirectional, so that in the event that the diagnosis indicates that continued operation is ill advised, the driver of the vehicle can be contacted) for communicating with a remote computing device is included. It should be recognized that these basic elements can be combined in many different configurations to achieve the exemplary concepts discussed above. Thus, the details provided herein are intended to be exemplary, and not limiting on the scope of the concepts disclosed herein.
- The above noted methods are preferably implemented by a processor (such as a computing device implementing machine instructions to implement the specific functions noted above) or a custom circuit (such as an application specific integrated circuit).
- The term real-time as used herein and the claims that follow is not intended to imply the data is transmitted instantaneously, rather the data is collected over a relatively short period of time (over a period of seconds or minutes), and transmitted to the remote computing device on an ongoing basis (transmission of the buffered operational data being triggered by the detection of a fault or anomaly), as opposed to storing the data at the vehicle for an extended period of time (hour or days), and transmitting an extended data set to the remote computing device after the data set has been collected.
- The concepts disclosed herein encompass a system where the above identified data operational data collection components, the data buffer (where some amount of operational data is temporarily stored, rather than being discarded), the processor (for analyzing the operational data to detect an anomalous condition), and the data link (for conveying the buffered operational data and the detected anomalous condition to a remote computing device for analysis) are included in a plurality of enrolled vehicles. Such a system includes a remote computing device (either an individual computing device, or a network of such devices), where the buffered operational data and the data defining the anomalous condition (such as a fault code) can be stored or analyzed (i.e., diagnosed). In one exemplary, but not limiting embodiment, vehicle position data and/or inspection data is collected from enrolled vehicles and stored at a first server, operated by a first entity, for use by the operator of the vehicle. Such data is collected during normal operation of the vehicle, and sent to the first server during normal operation of a vehicle. In the event that an anomalous condition is detected, the buffered operational data and the data defining the anomalous condition are sent from the vehicle to the first server. The first entity operating the first server then conveys the buffered operational data and the data defining the anomalous condition to a second server operated by a second entity. The second entity then analyzes the buffered operational data and the data defining the anomalous condition and determines the cause of the anomalous condition. The vehicle operator can then be contacted to arrange servicing of the vehicle. In an exemplary embodiment, the second entity is the manufacturer of the vehicle or the vehicle power plant.
- The concepts disclosed herein also encompass embodiments in which each enrolled vehicle includes a position tracking component (such as a global position satellite (GPS) tracking device), along with the data buffer, the data link to the remote computing device, and the processor for detecting the anomalous condition (or responding to the detection of the anomalous condition by using the data link to convey the buffered operational data to a remote computing device for analysis). In at least one exemplary embodiment, such components are incorporated into a diagnostic or telematics device also including the position tracking component.
- The concepts disclosed herein also encompass embodiments in which techniques are implemented to reduce an amount of buffered operational data conveyed to a remote computing device for analysis. Particularly where the data link from the vehicle to the remote computing device is wireless (such as cellular or satellite based communications), data transmission rates represent a cost that can be controlled. The concepts disclosed herein encompass a variety of filtering techniques that can be used to determine if a particular condition exists, such that when such a predefined condition exists, the buffered operational data will not be sent to the remote computing device, even if an anomalous condition is detected. One such filtering technique is based on detecting (using a position sensing component) a location of the vehicle at startup. If that location corresponds to a repair facility or service center, then the automated buffered operational data transmission functionality can be turned off (as the vehicle will likely be coupled to a diagnostic device at the service center, such that the remote diagnostic function is not needed). Such locations can be stored in a memory at the vehicle, or more preferably, the vehicle can communicate its location at start up to the remote computing device, which has access to the locations of such service centers. The remote computing device then determines if the processor in the vehicle responsible for controlling transmission of the buffered operational data to the remote computing device should be instructed not to transmit such data. Another such filter technique is based on analyzing whether the same anomalous conditions are detected in about the same geographic position and/or within a predefined time period (which can indicate that the vehicle is being driven around a service facility trying to replicate an intermittent fault). Another technique that can be used to reduce the amount of buffered operational data that is wirelessly conveyed to a remote computing device is to ensure that duplicate information, related to the same anomalous condition, is not sent time and time again. In at least one embodiment, an occurrence counter in a diagnostic trouble code (DTC) is analyzed to determine if a particular fault code is a reoccurring event that can be ignored to minimize an amount of data that is transmitted wirelessly.
- The concepts disclosed herein also encompass embodiments in which the processor controlling the collection and transmission of buffered operational data is configured to either ignore operational data generated during an initial start-up of the vehicle (referred to as settling time. This technique will result in no buffered operational data and anomalous condition data being wirelessly conveyed to a remote computing device until after a predetermined settling time has elapsed.
- It should be recognized that there is a temporal connection between the buffered operational data to be sent to the remote computing device and the detection of the anomalous event. Depending upon user preference, the buffered operational data sent to the remote computing device can be: (1) operational data collected before the anomaly; (2) operational data collected after the anomaly; and (3) a combination of operational data collected before the anomaly and after the anomaly.
- The concepts disclosed herein also encompass embodiments in which once buffered operational data and data defining an anomalous event are wirelessly conveyed to a remote computing device, a processor in the vehicle is configured to monitor dashboard lamps, to determine if any warning indicator lamps on the vehicle dashboard change in response to the recently detected anomalous condition. When such a lamp status change (i.e., from off to on, or from amber/yellow to red, indicating an escalation) is detected, that information is wirelessly transmitted to the remote computing device to which the buffered operational data and anomalous condition data were previously sent.
- The concepts disclosed herein also encompass embodiments in which a controller in the vehicle is configured to enable an operator of the vehicle to manually trigger the transmission of buffered operational data to the remote computing device. This can be used to enable an operator who is concerned that something unusual might be occurring in regard to vehicle operation, so that buffered operational data can be analyzed at a remote computing device to determine if there really is an operational issue with the vehicle. In such circumstances, the processor in the vehicle tasked with monitoring the operational data to detect an anomalous condition may not have detected such an anomalous condition, in which case only the buffered operational data will be conveyed to the remote computing device (i.e., data defining the anomalous condition will not be present, thus will not be sent to the remote computing device). In such a data transmission of buffered operational data, an indication that the operator of the vehicle triggered the data transmission can be included, so the analysis of the buffered operational data at the remote computing device can proceed with the understanding that the operator of the vehicle suspects a problem exists, even if an anomalous condition has not be detected at the vehicle by the vehicle hardware monitoring the operational data for such an anomalous condition. The vehicle can be equipped with a user input specifically configured to enable the vehicle operator to trigger the transmission of the current buffered operational data to the remote computing device (i.e., a button, rocker panel, switch or other user input that is added to the vehicle). In at least one embodiment, an existing operator input element is modified to support such a triggering function. For example, a control device used to control vehicle equipment such a headlight or radio can be used as a trigger, if the processor controlling the transmission of the buffered operational data is coupled to the control device, and configured to respond to a certain input pattern from the control device (i.e., the control device is manipulated by the operator in a predefined and unusual pattern, such as repeatedly manipulating the control device in a specific and unusual sequence not normally employed in routine vehicle operations). In at least one embodiment, the controller responsible for sending the buffered operational data to the remote computing device is configured to recognize repeatedly turning the radio on and off in a specific predefined pattern as an operator trigger signal, requiring the processor to use the data link to upload the contents of the data buffer to the remote computing device.
- This Summary has been provided to introduce a few concepts in a simplified form that are further described in detail below in the Description. However, this Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
- Various aspects and attendant advantages of one or more exemplary embodiments and modifications thereto will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
-
FIG. 1 is a high level logic diagram showing exemplary overall method steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time; -
FIG. 2 is a functional block diagram of an exemplary computing device that can be employed to implement some of the method steps disclosed herein; -
FIG. 3 is a functional block diagram of an exemplary vehicle employed to implement some of the concepts disclosed herein; -
FIG. 4 is an exemplary functional block diagram showing the basic functional components used to implement the method steps ofFIG. 1 ; -
FIG. 5 is another exemplary functional block diagram showing the basic functional components used to implement the method steps ofFIG. 1 ; -
FIG. 6 is a functional block diagram of an exemplary diagnostic unit including a position sensing component that can be added to a vehicle to implement some of the concepts disclosed herein; -
FIG. 7 is a functional block diagram of exemplary processor functions that can be implemented in the diagnostic unit ofFIG. 6 ; and -
FIG. 8 is a flow chart showing exemplary steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time, the method ofFIG. 8 including some additional functions as compared to the method ofFIG. 1 . - Exemplary embodiments are illustrated in referenced Figures of the drawings. It is intended that the embodiments and Figures disclosed herein are to be considered illustrative rather than restrictive. No limitation on the scope of the technology and of the claims that follow is to be imputed to the examples shown in the drawings and discussed herein. Further, it should be understood that any feature of one embodiment disclosed herein can be combined with one or more features of any other embodiment that is disclosed, unless otherwise indicated.
- As used herein and in the claims that follow, a reference to an activity that occurs in real-time is intended to refer not only to an activity that occurs with no delay, but also to an activity that occurs with a relatively short delay (i.e., a delay or lag period of seconds or minutes, but with less than an hour of lag time).
-
FIG. 1 is a high level flow chart showing the overall method steps implemented in accord with one aspect of the concepts disclosed herein, to convey data defining an anomalous vehicle condition along with operational data (collected from the vehicle proximate to the detection of the anomaly) to a remote computing device, so that the cause of the anomaly can be diagnosed in real-time. Vehicle fault codes represent an exemplary type of anomaly. In the prior art, fault codes are used to facilitate diagnosis of vehicle problems, however, the operational data discussed herein is not used in addition to the fault codes to diagnose vehicle problems. Providing such operational data in addition to the data defining the anomaly (such as a fault code) will facilitate more accurate diagnoses. - Referring to
FIG. 1 , in ablock 10, each vehicle enrolled in the diagnostic system is equipped with components to collect operational data, a data buffer in which operational data is temporarily stored, a processor to detect anomalous conditions (such as anomalous conditions corresponding to predefined fault codes), and a data link to convey the data defining the anomalous condition and contents of the data buffer to a remote computing device for diagnosis. As noted above, a majority of vehicles manufactured today already include components to collect operational data during operation of the vehicle. Such data is used during operation of the vehicle, to provide feedback to control many vehicle systems, including but not limited to engine fuel supply components, vehicle braking components, vehicle cooling components, and vehicle transmission components. According to the concepts disclosed herein, such vehicles are modified to include a data buffer in which this operational data is temporarily stored. Conventionally, such operational data is generated, used to control operation of the vehicle (or used for diagnostic purposes when the vehicle is coupled to a diagnostic unit in a service bay), and then discarded. Further modifications include configuring a processor in the vehicle to convey detected vehicle anomalies and the contents of the data buffer when the anomaly is detected to the remote computing device for diagnosis. The data buffer can be configured as desired to include operational data collected before the anomaly occurs, after the anomaly occurs, or both. In an exemplary embodiment, a temporal extent of the operational data conveyed to the remote computing device along with the data defining the anomaly, both before and after the anomaly occurs, is a user definable parameter. In at least one embodiment, the buffer collects several minutes of data, in a first in, first out type data buffer. It should be recognized that such an amount of data is exemplary, and not limiting. From a diagnostic perspective, the more data the better. From an implementation standpoint, larger data buffers will cost somewhat more than smaller data buffers, although memory costs are relatively small. Wireless data transmission rates can be relatively costly, so a desire for larger data sets for diagnostic purposes is at odds with a desire for smaller data sets to control wireless data transmission expenses. Exemplary studies have indicated that useful amounts of data can be acquired using a data buffer of 128 MB to 256 MB, with transmitted data packets being less than about 50 kilobytes per anomaly, though such values are exemplary, rather than limiting. - In a
block 12, the data link is used to convey the anomaly (i.e., vehicle data that is identified as non-standard, or anomalous, which in an exemplary, but not limiting embodiment, is represented by a fault code, which is a numeric or alphanumeric value corresponding to a predefined fault condition) and the contents of the data buffer (in some embodiments the entire contents of the data buffer is sent, whereas in other embodiments less than the entire contents of the data buffer is sent along with the anomaly) to a remote computing device for analysis. It should be understood that the fault code and contents of the data buffer (in which operational data are stored) may be sent to more than one remote computing device before analysis of the data is implemented. For example, in an exemplary but not limiting embodiment, the fault code and contents of the data buffer are wirelessly conveyed from the vehicle (in real-time) to a computing device (which may be a network of linked devices as opposed to a single computing device) operated by the vehicle owner or a vendor providing a service to the vehicle owner. The data is stored therein, and then conveyed to a different remote computing device (which itself maybe a network of linked devices as opposed to a single computing device) operated by a vendor providing diagnostic services to the vehicle owner. - In a
block 14, a processor at a remote location is used to analyze the fault code (or other data defining the detected anomalous or non-standard data) and the contents of the data buffer conveyed from the vehicle to identify a cause of the anomaly. In anoptional block 16, the processor at the remote location may request additional data from the vehicle to facilitate the analysis or to confirm a diagnosis. In some embodiments, the additional data is the contents of the data buffer at a subsequent time interval, while in other embodiments the additional data is specifically defined data that the vehicle collects and conveys. - In general, the analysis of the fault code/anomaly and the contents of the data buffer will be carried out by a remote computing device. The remote computing device in at least one embodiment comprises a computing system controlled by the operator of the vehicle, while in other exemplary embodiments the computing system is controlled by a third party or vendor who manages the diagnostic service for the operators of the enrolled vehicles (in some embodiments, the third party bills the vehicle operators a subscription fee). The remote computing device can be operating in a networked environment.
FIG. 2 schematically illustrates anexemplary computing system 250 suitable for use in implementing the method ofFIG. 1 (i.e., for executing at least block 14 ofFIG. 1 , and in some embodiments block 16 as well).Exemplary computing system 250 includes aprocessing unit 254 that is functionally coupled to aninput device 252 and to anoutput device 262, e.g., a display (which can be used to output a result to a user, although such a result can also be stored).Processing unit 254 comprises, for example, a central processing unit (CPU) 258 that executes machine instructions for carrying out an analysis data collected from enrolled vehicles, to diagnose a mechanical fault (or other vehicle anomaly). The machine instructions implement functions generally consistent with those described above with respect to block 14 ofFIG. 1 . CPUs suitable for this purpose are available, for example, from Intel Corporation, AMD Corporation, Motorola Corporation, and other sources, as will be well known to those of ordinary skill in this art. - Also included in
processing unit 254 are a random access memory (RAM) 256 andnon-volatile memory 260, which can include read only memory (ROM) and may include some form of memory storage, such as a hard drive, optical disk (and drive), etc. These memory devices are bi-directionally coupled toCPU 258. Such storage devices are well known in the art. Machine instructions and data are temporarily loaded intoRAM 256 fromnon-volatile memory 260. Also stored in the non-volatile memory are an operating system software and ancillary software. While not separately shown, it will be understood that a generally conventional power supply will be included to provide electrical power at voltage and current levels appropriate to energizecomputing system 250. -
Input device 252 can be any device or mechanism that facilitates user input into the operating environment, including, but not limited to, one or more of a mouse or other pointing device, a keyboard, a microphone, a modem, or other input device. In general, the input device will be used to initially configurecomputing system 250, to achieve the desired processing (i.e., to analyze performance data from a vehicle to detect a mechanical or other fault). Configuration ofcomputing system 250 to achieve the desired processing includes the steps of loading appropriate processing software intonon-volatile memory 260, and launching the processing application (e.g., loading the processing software intoRAM 256 for execution by the CPU) so that the processing application is ready for use.Output device 262 generally includes any device that produces output information, but will most typically comprise a monitor or computer display designed for human visual perception of output. Use of a conventional computer keyboard forinput device 252 and a computer display foroutput device 262 should be considered as exemplary, rather than as limiting on the scope of this system.Data link 264 is configured to enable vehicle anomaly data and buffered operational data collected in connection with operation of enrolled vehicles to be input intocomputing system 250 for analysis to determine a cause of the anomalous data. Those of ordinary skill in the art will readily recognize that many types of data links can be implemented, including, but not limited to, universal serial bus (USB) ports, parallel ports, serial ports, inputs configured to couple with portable memory storage devices, Fire Wire ports, infrared data ports, wireless data communication such as Wi-Fi and Bluetooth™, network connections via Ethernet ports, and other connections that employ the Internet. Note that vehicle data from the enrolled vehicles will be communicated wirelessly, either directly to the remote computing system that analyzes the data to diagnose the anomaly, or to some storage location or other computing system that is linked tocomputing system 250. In at least one embodiment, the vehicle anomaly data and buffered operational data collected in connection with operation of enrolled vehicles is wirelessly transmitted in a compact binary format to a first server, where the data is converted to a different format for transmission to a second server over a computer network, such as the Internet. In at least one embodiment, the second format is XML. - It should be understood that the term remote computer and the term remote computing device are intended to encompass networked computers, including servers and clients, in private networks or as part of the Internet. The buffered operational data and anomaly defining data can be stored by one element in such a network, retrieved for review by another element in the network, and analyzed by yet another element in the network. In at least one embodiment, a vendor is responsible for diagnosing the operational data and anomaly defining data, and clients of the vendor are able to access and review such data, as well as any resulting diagnoses. While implementation of the method noted above has been discussed in terms of execution of machine instructions by a processor (i.e., the computing device implementing machine instructions to implement the specific functions noted above), the method could also be implemented using a custom circuit (such as an application specific integrated circuit).
-
FIG. 3 is a functional block diagram of exemplary components used in vehicles enrolled in the vehicle diagnostic service, which are used in each enrolledvehicle 41 to implement some of the method steps shown inFIG. 1 . An exemplary vehicle diagnostic service is based on adding adata buffer 46 and abi-directional data link 43 to each enrolled vehicle. In an exemplary embodiment, this data link is a combination RF transmitter and receiver, although separate transmitters and receivers could be used. If the vehicle does not already include operationaldata collecting components 40, such components are added. As discussed above, most vehicles manufactured today include such operational data collecting components already, as many of today's vehicles are designed to use such continuously generated operational data to control operation of the vehicle in real-time, and such vehicle generally include data collecting components, data buses, and controllers that use the operational data to control the operation of the vehicle. The vehicle includes at least oneprocessor 42 that performs the functions of temporarily storing operational data fromcomponents 40 indata buffer 46, detecting an anomalous condition in the vehicle, and in response to detecting such an anomaly, using bi-directional data link 43 to convey real-time anomaly data and the buffered operational data from the enrolled vehicle to a remote computing device 44 (which is used to determine or diagnose a cause for the detected anomaly). It should be understood that those processor functions can be implemented by a single processor, or distributed across multiple processors. As shown inFIG. 3 , data from the vehicle is read by themicrocontroller implementing processor 42 before moving intobuffer 46, as is as would be typical of using a microcontroller to read data from most any data connection. In an exemplary, but not limiting embodiment, the data buffer, data link, and processor responsible for triggering the transmission of buffered data to the remote computing device are combined into a single component. - In some embodiments, an
output 45 is also included, to provide diagnostic related information to the driver in a form that can be easily understood by the driver.Output 45 can be implemented using one or more lights (for example, a red light can be used to indicate that a problem has been detected which requires the operator to stop the vehicle, or to modify vehicle operations (for example, to slow down or otherwise reduce a load being placed on the vehicle until a repair can be made), using a speaker providing an audible output, and using a display providing a visual output. Note thatoutput 45 can be combined into a single component with the data buffer and the data link, so only a single additional component is added to the vehicle (recognizing that most vehicles already include the additional required components, such as the operational data collecting components and the processor, although in at least some embodiments an additional processor is added to the vehicle to control the triggering of the transmission of buffered operational data to the remote computing device). - The concepts disclosed herein are in at least some embodiments intended to be used by fleet owners operating multiple vehicles, and the anomaly defining data and buffered operational data conveyed to the remote location for diagnosis will include an ID component that enables each enrolled vehicle to be uniquely identified.
-
FIG. 4 is a functional block diagram of anexemplary system 50 that can be employed to implement the method steps ofFIG. 1 . The components include at least one enrolled vehicle 52 (including the components discussed above in connection withFIG. 3 ), anoptional repair facility 54, a processor component 56 (in the vehicle) to implement the function of detecting an anomalous condition (such as detecting a fault code), a processor component 58 (also in the vehicle) to implement the function of conveying the fault code (or other data defining the detected anomaly) and contents of the operational data buffer to a remote location, and aremote processor component 60 to implement the function of analyzing the fault code (or other data defining the detected anomaly) and contents of the data buffer conveyed from the vehicle to determine a cause for the anomaly. Note thatprocessor component -
FIG. 5 is another functional block diagram showing the components of a vehicle diagnostic system in accord with the concepts disclosed herein, where the data link and data buffer are combined into a single component to be added to a vehicle to enable the vehicle to participate in the diagnostic program. - In the diagnostic system embodiment of
FIG. 5 , asystem 62 includes avehicle 64 and aremote computing device 72 for performing diagnostic analysis on data supplied by the vehicle over awireless network 70.Vehicle 64 includes a plurality of components for collecting operational data, including abrake control unit 66 a, anengine control unit 66 b, and atransmission control unit 66 c, each of which transmit operational data along adata bus 67. While only a single data bus is shown, it should be understood that multiple data buses could be employed. Further, a vehicle controller/processor, such as is shown inFIG. 3 , is not illustrated inFIG. 5 , but one or more such elements will be coupled to the data bus to receive and use operational data generated by the vehicle.Vehicle 64 also includes an add-ondiagnostic unit 68, which combines a data buffer, a data link, and a processor implementing one or more of the functions associated withprocessor components FIG. 4 into a single device (noting that the vehicle's own processors could also be configured to implement such functions, particularly the function of detecting an anomalous condition, if desired). -
Diagnostic unit 68 conveysdiagnostic logs 76 fromvehicle 64 toremote computer 72 viawireless network 70, generally as discussed above.Diagnostic logs 76 include an identified anomaly (such as a fault code) and data stored in the data buffer portion ofdiagnostic unit 68.Remote computer 72 analyzes the diagnostic logs to determine a cause of the anomaly.Remote computer 72 conveys data 74 (which includes one or more of configuration data and diagnostic data) todiagnostic device 68 via the wireless network. The configuration data is used to modify the functions implemented by the processor indiagnostic unit 68. Modifications includes, but are not limited to, changing the amount of operational data to be stored in the data buffer, changing an amount of operational data collected before an anomaly that is conveyed to the remote computing device, changing an amount of operational data collected after an anomaly that is conveyed to the remote computing device, changing a type of operational data that is conveyed to the remote computing device (this enables the remote computing device to request specific types of operational data after a diagnostic log has been received, to facilitate diagnosing the anomaly), and changing a definition of what constitutes an anomaly. The diagnostic data includes data conveyed to the operator of the vehicle, informing the operator of what actions the operator needs to take in response to the diagnosis. Such diagnostic data can include instructions to cease vehicle operations as soon as possible to avoid unsafe or damaging conditions, instructions to proceed to a designated repair facility, and/or instructions to proceed with a scheduled route, and to wait to repair the vehicle when the route is complete. - In an exemplary embodiment,
diagnostic device 68 is implemented by using a hardware device installed onboard medium and heavy duty (Class 5-8) vehicles that is permanently or temporarily installed, powered from onboard vehicle power systems, connected to the in-vehicle diagnostic data communications network, capable of collecting diagnostic data from the vehicle data communications network and sending it to an off board server. The specific information to be acquired from the vehicle communications data link is remotely configurable. The specific data messages that trigger a data collection event are also remotely configurable. Data transmission from the vehicle includes a wireless interface between the vehicle and the off board server, such as a cellular modem or other similar wireless data transmission method. Data received at the off board server may then be forwarded to any defined set of consumers for the diagnostic information to be remotely analyzed and acted upon. - The components of
system 62 include the hardware device used to implementdiagnostic device 68, hardware programming (firmware), the wireless network, and the remote computing device (such as a computer server/data center).System 62 operates by using the remote computing device to transmit programming/configuration data to the in-vehicle device (i.e., diagnostic device 68) via the wireless network. During vehicle operation, the diagnostic data device stores operational data to include with all diagnostic log events (i.e., with each fault code or detected anomaly). In an exemplary but not limiting embodiment, the diagnostic log conveyed to the remote computing device from the vehicle includes data such as a diagnostic log file revision, a diagnostic log file type, a device ID, a configured time interval defining the extent of buffered operational data, and the number of parameters to be stored in the diagnostic log files. The diagnostic data device in the vehicle performs the functions of: storing a list of diagnostic parameters to be monitored and recorded from the vehicle data link at regular periodic intervals; storing a list of event parameters to trigger diagnostic data capture; and storing a time interval for diagnostic parameter recording. In an exemplary but not limiting embodiment, the diagnostic data device is connected to an in-vehicle data link (e.g., a 11939 bus) and vehicle power connections. - During vehicle operation, while the vehicle data link communication is active, the diagnostic data device is continuously monitoring for specific data messages configured to trigger the collection of diagnostic log files. Once diagnostic log files are recorded, they are transmitted via the wireless network to the remote computing device. Diagnostic log files are moved from the data center server within minutes to a destination server where the data may be analyzed and/or distributed for further action.
- In an exemplary, but not limiting embodiment, the diagnostic log sent to the remote computing device includes one minute worth of operational data collected both before and after the anomalous event.
- In an exemplary, but not limiting embodiment, the diagnostic log sent to the remote computing device includes the following types of operational data: any user defined fault code that has been detected, any vehicle manufacturer defined fault code that has been detected, a position of the vehicle at the time the fault code is detected (if the vehicle includes a position sensor), trip start and end times, odometer value and source address, engine hours and source address, power take off (PTO) hours and source address, total fuel and source address, idle fuel and source address, PTO Fuel and source address, VIN and source address, and trip fuel economy calculated from odometer and total fuel values listed above. It should be understood the processor in the vehicle configured to assemble the vehicle data (including buffered operational data and data defining the anomaly that was detected) to be uploaded to the remote computing can be configured to always send the same types of data to the remote computing device for each anomaly detected, or the processor can be configured to send specific types of data to the remote computing device based on the anomaly detected. For example, assume that the following types of data are available (either in the buffered operational data, or accessible to the processor): brake temperature data, oil temperature data, fuel level data, engine hour data, coolant temperature data, and tire pressure data (such types of data being exemplary, and not limiting). In some embodiments, regardless of the type of anomaly detected, all available data types are sent to the remote computing device. In other embodiments, only a subset of the most likely relevant data is sent to the remote computing device (for example, if the anomaly deals with brakes, then brake temperature data and tire pressure data is sent, but other types of data having less to do with the vehicle braking system are not sent to the remote computing device).
- In an exemplary, but not limiting embodiment, the diagnostic device in the vehicle can be remotely configured to redefine the parameters used to generate a diagnostic log. The diagnostic log generated by the diagnostic device includes two primary components; at least some of the operational data temporarily stored in the data buffer, and data defining the anomaly (in some embodiments, fault codes are used to define the anomaly). The diagnostic device can be remotely reconfigured to change an amount of buffered operational data acquired before the anomaly that is included in the diagnostic log. The diagnostic device can be remotely reconfigured to change an amount of buffered operational data acquired after the anomaly that is included in the diagnostic log. The diagnostic device can be remotely reconfigured to change the type of operational data that is included in the diagnostic log (in the terms of
FIG. 5 , the diagnostic device can be remotely reconfigured to selectively determine whether data frombrake control unit 66 a, data fromengine control unit 66 b, and/or data fromtransmission control unit 66 c should be included in the diagnostic log, noting that such operational data generating components are exemplary, and not limiting). The diagnostic device can also be remotely reconfigured to define what constitutes an anomaly that triggers sending a diagnostic log to the remote computing device for diagnosis. As discussed above, fault codes defined by the vehicle manufacturer can be considered to be anomalies that will trigger conveying a diagnostic log to the remote location. It should also be recognized that the concepts disclosed herein encompass enabling the diagnostic device to be remotely reconfigured to define a single parameter or a set of parameters (beyond the parameters used by manufacturers to define fault codes) that will trigger the conveyance of diagnostic log to the remote location. For example, regardless of the parameters used to define preset fault codes, the diagnostic device can be remotely reconfigured to generate and convey a diagnostic log to the remote location in response to detecting any specified parameter or set parameters. - The concepts disclosed herein also encompass embodiments in which a the data buffer, the data link to the remote computing device, and the processor for detecting the anomalous condition are incorporated into a diagnostic or telematics device also including a position tracking component (such as a GPS component, recognizing that other position sensing technologies can be similarly employed).
FIG. 6 is a functional block diagram of an exemplary diagnostic unit including a position sensing component that can be added to a vehicle to implement some of the concepts disclosed herein. A diagnostic (or telematics)unit 100 includes at least onedata port 102 enabling vehicle operational data to be input into unit 100 (in an exemplary, but not limiting unit, a port for 11939 data and a port for 11708 data are provided, recognizing that such types of data are exemplary, and not limiting), abuffer 108 where operational data is temporarily stored, aGPS component 110 for determining vehicle location (which, as discussed below, can in certain embodiments be used to influence when the contents of the data buffer is transmitted to the remote computing device for analysis), awireless data link 104 for sending operational data in the buffer to the remote computing device for analysis of an anomalous condition, and a processor 106 (for implementing at least the function of causing the buffered operational data to be conveyed via the data link to a remote computing device when an anomalous condition is detected). -
FIG. 6 also shows anoptional operator trigger 111, that an operator of the vehicle can actuate to causeprocessor 106 to use the data link to send the contents of the buffer to the remote computing device. In this case, the operator is determining that some anomalous condition has occurred which should be investigated. Perhaps the driver feels an odd vibration, hears an odd engine noise, or otherwise perceives some abnormal condition. Thetrigger 111 is coupled tocontroller 106, which is configured to respond by sending the buffered operational data to the remote computing device. In such circumstances, the processor in the vehicle tasked with monitoring the operational data to detect an anomalous condition may not have detected such an anomalous condition, in which case only the buffered operational data will be conveyed to the remote computing device (i.e., data defining the anomalous condition will not be present, thus will not be sent to the remote computing device). In such a data transmission of buffered operational data, an indication that the operator of the vehicle triggered the data transmission can be included, so the analysis of the buffered operational data at the remote computing device can proceed with the understanding that the operator of the vehicle suspects a problem exists, even if an anomalous condition has not be detected at the vehicle by the vehicle hardware monitoring the operational data for such an anomalous condition.Trigger 111 can be implemented with a dedicated user input device (only used to trigger sending the contents of the data buffer to the remote computing device), or an existing operator input element is modified to support such a triggering function. For example, a control device used to control vehicle equipment such a headlight or radio can be used as a trigger, if the processor controlling the transmission of the buffered operational data is coupled to the control device, and configured to respond to a certain input pattern from the control device (i.e., the control device is manipulated by the operator in a predefined and unusual pattern, such as repeatedly manipulating the control device in a specific and unusual sequence not normally employed in routine vehicle operations). - Buffer 108 can be implemented as a first in, first out buffer that temporarily stores the operational data generated by the vehicle in normal operation, which conventionally is generated and discarded rather than being saved.
Buffer 108 is intended to be relatively small, and not intended to attempt to archive all of the operational data generated by the vehicle for an extended period of operation. Rather, buffer 108 is intended to store relatively small, but still useful amounts of operational data. In an exemplary, but not limiting embodiment, the amount of operational data stored inbuffer 108 represents seconds or minutes of data, rather than hours or days of data. In an exemplary, but not limiting embodiment,buffer 108 is implemented using flash memory, of less than a gigabyte. With memory prices dropping regularly, more operational data could be stored. However, wireless transmission of data represents a cost, and in at least one embodiment a balance between the amount of data collected (more data leading to better diagnoses) and the amount of data wirelessly transmitted (less data being transmitted meaning less cost) is sought. Empirical studies have indicated that useful amounts of data can be obtained using a buffer of 256 MB or less and data transmissions of less than about 30 kilobytes per anomaly. -
Processor 106 implements at least the function of using the data link to send the contents of the buffer (or at least a portion of the contents) to the remote computing device when an anomalous event occurs. In some embodiments,processor 106 implements additional functions. In at least one embodiment,processor 106 analyzes the operational data to detect specific conditions that have been predetermined to represent an anomaly that should trigger the transmission of the buffer to the remote computing device. In at least some embodiments, the data link can be used to enable changes to be made to the logic used by the processor to determine what represents an anomaly. - In some embodiments, a different processor (i.e., not processor 106) in the vehicle is determining when an anomalous condition occurs. For example, any processor in a vehicle that generates a fault code based on specific operational data can be configured to send that fault code to
processor 106, so thatprocessor 106 responds by using the data link to send the fault code and the contents of the data buffer to the remote computing device. -
FIG. 7 IS a functional block diagram of exemplary processor functions that can be implemented in the diagnostic unit ofFIG. 6 . Ablock 112 corresponds to the function of analyzing the operational data generated by the vehicle to detect an anomalous condition. This function is generally implemented when parameters other than manufacturer designated fault codes (which are generally detected by other processors in the vehicle) are used to define an anomaly. Ablock 114 refers to the function of applying specific logic (i.e., a filter) to reduce an amount of data that might otherwise be sent to the remote computing device, as will be discussed below). Ablock 116 refers to the function of using the data link to send the buffered operational data to the remote computing device based on a trigger event (such as an operator trigger, a fault code detected by some other processor, or an anomalous condition detected by processor 106). Ablock 118 refers to the function of using the data link to send lamp escalation data to the remote computing device after buffered operational data corresponding to a previously detected anomalous condition has been sent, in the event that an indicator lamp has changed status since the anomalous event (this function is discussed in detail below). InFIG. 7 , blocks 112, 116, and 118 are shown in dashed lines, as such functions can be considered optional, and such functions are not implemented in all embodiments. - As noted above, block 114 refers to the function of applying specific logic (i.e., one or more filters) to reduce an amount of data that might otherwise be sent to the remote computing device. In some embodiments, such logic is implemented to reduce an amount of buffered operational data conveyed to a remote computing device for analysis, as a cost control function. The concepts disclosed herein encompass a variety of filtering techniques that can be used to determine if a particular condition exists, such that when such a predefined condition exists, the buffered operational data will not be sent to the remote computing device, even if an anomalous condition is detected. One such filtering technique is based on detecting (using GPS component 110) a location of the vehicle at startup. If that location corresponds to a repair facility or service center, then the automated buffered operational data transmission functionality can be turned off (as the vehicle will likely be coupled to a diagnostic device at the service center, such that the remote diagnostic function is not needed). Such locations can be stored in a memory at the vehicle, or more preferably, the vehicle can communicate its location at start up to the remote computing device, which has access to the locations of such service centers. The remote computing device then determines if
processor 106 should be instructed (via data link 104) not to transmit the buffered operational data to the remote computing device even if an anomaly is detected. Another such filter technique is based on analyzing whether the same anomalous conditions are being detected in about the same geographic position and/or within a predefined time period (which can indicate that the vehicle is being driven around a service facility trying to replicate an intermittent fault). In one embodiment,controller 106 is configured to not to transmit the buffered operational data to the remote computing device even if an anomaly is detected, if the vehicle remains within a relatively small geographical area (i.e., within five miles or so, such an area being exemplary and not limiting) in a predefined period of time (such as 24 hours, again recognizing that the specified interval is exemplary, and not limiting). Another technique that can be used to reduce the amount of buffered operational data that is wirelessly conveyed to a remote computing device is to ensure that duplicate information, related to the same anomalous condition, is not sent time and time again. In at least one embodiment, an occurrence counter in a diagnostic trouble code (DTC) generated in the vehicle is analyzed to determine if a particular fault code is a reoccurring event that can be ignored to minimize an amount of data that is transmitted wirelessly to the remote computing device for analysis.Processor 106 can be configured to send repeating fault codes/anomalies, when the re-occurring anomaly is accompanied by a new anomaly. - The concepts disclosed herein also encompass embodiments in which
processor 106 is configured to either ignore operational data generated during an initial startup of the vehicle (referred to as settling time). During initial vehicle startup, as various components in the vehicle initialize, what otherwise might appear to be anomalous operating conditions may briefly exist. In general, such conditions rapidly disappear as vehicle components operate for more than several seconds. In an exemplary, but not limiting embodiment,controller 106 is configured to ignore, or not to store, about the first ten seconds of operational data that is generated upon vehicle startup. Vehicle startup can also present the unusual condition where the data buffer may not have filled to capacity. Assume the data buffer is configured to store 90 seconds of operational data, and an anomalous condition is detected 45 seconds after operational data began to fill up the buffer.Controller 106 can be configured to send only the 45 seconds present in the buffer, or can be configured to not transmit any portion of the buffer, if the buffer is not full, depending on the logic one wishes to employ. Partial data is likely to be more useful than no data, so the former technique is more likely to be implemented. - As noted above, block 118 refers to the function of using the data link to send lamp escalation data to the remote computing device after buffered operational data corresponding to a previously detected anomalous condition has been sent, in the event that an indicator lamp has changed status since the anomalous event. In at least one embodiment,
processor 106 is configured to monitor dashboard lamps, to determine if any warning indicator lamps on the vehicle dashboard change in response to the recently detected anomalous condition. When such a lamp status change (i.e., from off to on, or from amber/yellow to red, indicating an escalation) is detected,processor 106 is configured to use data link 104 to send information defining the change in the lamp status to the remote computing device. Depending on the vehicle, the fault code data may include lamp status, but that information is not necessarily accurate, and even when accurate the buffered operational data may not capture a change in lamp status that occurs at a time point after the anomaly has occurred. In general, this lamp escalation logic pertains only to the same fault or anomaly. If there were a fault code such as (SrcAddr=3, SPN=111, FMI=1 and lamp state=all off) followed by the same SrcAddr, SPN, FMI and a different lamp state, then the lamp escalation logic component inprocessor 106 would send the new lamp state to the remote server/computing device via the data link. If the SrcAddr, SPN, FMI are different, then a new fault entry is created and buffered operational data pertaining to the new fault/anomaly and data defining the new anomaly are sent to the remote computing device. - It should be recognized that
processor 106 can be implemented via hardware (such as an application specific integrated circuit implementing fixed logical steps), or a controller implementing software (i.e., a series of logical steps).Processor 106 can be a single component, or different functions described above that are implemented byprocessor 106 can be distributed across multiple processors. - In at least one embodiment,
processor 106 is configured to include data fromGPS component 110 with the buffered operational data, when such data is conveyed to the remote computing device viadata link 104. -
FIG. 8 is a flow chart showing exemplary steps implemented in accord with the concepts disclosed herein to remotely diagnose an abnormal vehicle parameter in real-time, where the method ofFIG. 8 includes some additional functions as compared to the method ofFIG. 1 . Note thatFIG. 8 is discussed in terms ofdiagnostic unit 100 ofFIG. 6 , but it should be recognized that the steps ofFIG. 8 could be implemented in embodiments having different configurations than the diagnostic unit ofFIG. 6 . In ablock 120,diagnostic unit 100 ofFIG. 6 powers on. In ablock 122, operational data generated during an initial settling period (generally measured in seconds, an exemplary settling period being 10 seconds, with the understanding that such a time period is exemplary, and not limiting) is ignored. In some embodiments, any fault codes or anomalous events occurring in the settling period are also ignored. In some embodiments, operational data in the settling period can be stored in the data buffer, but fault codes or anomalous events in the settling period are ignored, such that no operational data is sent to the remote computing device until after the settling period has elapsed. In ablock 124, operational data is stored in a first in, first out buffer. In adecision block 126, at least one processor in the vehicle (which in some embodiments isprocessor 106 ofFIG. 6 , while in other embodiments is a different processor in the vehicle, such as a vehicle processor normally tasked with identifying fault codes) determines if an anomalous event has occurred (either by monitoring the operational data itself, or by waiting for a fault code or anomalous condition to be detected by some other vehicle processor). If not, operational data in the data buffer is continuously updated (for example, for each new second of new data added to the buffer, the oldest second of data is discarded, recognizing that the stated one second intervals being added/discarded is exemplary, and not limiting). If in decision block 126 an anomaly has been detected, thenprocessor 106 takes the contents of the buffer, collects an additional amount of operational data after anomaly is detected (in an exemplary embodiment, an additional 10-20 seconds of operational data is acquired, noting that such a time period is exemplary, and not limiting), and uses the data link to send the buffered operational data collected before and after the anomaly is detected, and data defining the anomaly, to the remote computing device. This data is sent as a compact binary file to minimize data transmission costs. In anoptional block 132, the binary data file is translated into another format (such as XML), and then sent via a computer network to a secondary server for analysis, as indicated in ablock 134.Blocks - Thus, the concepts disclosed herein encompass at least one embodiment implemented as a system in which diagnostic units such as those shown in
FIG. 6 are included in a plurality of enrolled vehicles. Such a system includes a remote computing device (either an individual computing device, or a network of such devices), where the buffered operational data and the data defining the anomalous condition (such as a fault code) can be stored or analyzed (i.e., diagnosed). In one exemplary, but not limiting embodiment, vehicle position data and/or inspection data is collected from enrolled vehicles and stored at a first server, operated by a first entity, for use by the operator of the vehicles. Such data is collected during normal operation of the vehicle, and sent to the first server during normal operation of a vehicle. In the event that an anomalous condition is detected, the buffered operational data and the data defining the anomalous condition are sent from the vehicle to the first server. The first entity operating the first server then conveys the buffered operational data and the data defining the anomalous condition to a second server operated by a second entity. The second entity then analyzes the buffered operational data and the data defining the anomalous condition and determines the cause of the anomalous condition. The vehicle operator can then be contacted to arrange servicing of the vehicle. In an exemplary embodiment, the second entity is the manufacturer of the vehicle or the vehicle power plant. - The concepts disclosed herein further specifically encompass the following.
- A first telematics unit for use in a vehicle, the telematics unit comprising:
- (a) a first data port for receiving operational data from the vehicle during operation of the vehicle; (b) a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle; (c) a data link for wirelessly conveying data from the vehicle to a remote computing device; and (d) a processor configured to use the data link to send operational data from the buffer to the remote computing device when an anomalous condition is detected at the vehicle.
- The first telematics unit described above, where the processor IS configured to include data defining the anomalous condition with the buffered operational data that is sent to the remote computing device.
- The first telematics unit described above, where the processor is configured to send a predefined additional quantity of operational data collected after the anomaly is detected to the remote computing device, along with buffered operational data collected before the anomaly is detected.
- The first telematics unit described above, where the processor is configured to analyze the operational data entering the buffer to detect the anomalous condition.
- The first telematics unit described above, where the processor is configured to receive a notification from a different vehicle processor that is configured to detect the anomalous condition.
- The first telematics unit described above, where the processor is configured to ignore anomalous conditions occurring during a predefined settling period after vehicle startup.
- The first telematics unit described above, where the processor is configured to ignore anomalous conditions that have already been reported to the remote computing device.
- The first telematics unit described above, where the processor is configured to send buffered operational data to the remote computing device based on a trigger signal received from a vehicle operator, even if an anomalous condition has not been detected.
- The first telematics unit described above, where after buffered operational data has been sent to the remote computing device in response to the detection of an anomalous condition, the processor is configured to monitor a warning lamp status associated with the anomaly, and to use the data link to send lamp escalation data to the remote computing device when that warning lamp changes condition.
- A second telematics unit for use in a vehicle, the telematics unit comprising: (a) a positioning sensing component for collecting geographical position data from the vehicle during vehicle operation, the geographical position data being time indexed; (b) a data port for receiving operational data from the vehicle during operation of the vehicle; (c) a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle; (d) a data link for wirelessly conveying data from the vehicle to a remote computing device; and (e) a processor configured to use the data link to send operational data from the buffer to the remote computing device when an anomalous condition is detected at the vehicle.
- The second telematics unit described above, where the processor is configured to include data defining the anomalous condition with the buffered operational data that is sent to the remote computing device.
- The second telematics unit described above, where the processor is configured to send a predefined additional quantity of operational data collected after the anomaly is detected to the remote computing device, along with buffered operational data collected before the anomaly is detected.
- The second telematics unit described above, where the processor IS configured to include geographical position data defining a location of the vehicle when the anomalous condition is detected with the buffered operational data that is sent to the remote computing device.
- The second telematics unit described above, where the processor is configured to analyze the operational data entering the buffer to detect the anomalous condition.
- The second telematics unit described above, where the processor is configured to receive a notification from a different vehicle processor configured to detect the anomalous condition.
- The second telematics unit described above, where the processor is configured to ignore anomalous conditions occurring during a predefined settling period after vehicle startup.
- The second telematics unit described above, where the processor is configured to determine a position of the vehicle at startup, and ignore anomalous conditions occurring while the vehicle's position is proximate to a known location where anomalous conditions should be ignored.
- The second telematics unit described above, where the processor IS configured to determine a position of the vehicle at startup, then send a request to the remote computing device to determine if the position of the vehicle is proximate to a known location where anomalous conditions should be ignored, and if so, the processor is configured to ignore anomalous conditions occurring proximate that location.
- The second telematics unit described above, where the processor IS configured to ignore anomalous conditions that have already been reported to the remote computing device.
- The second telematics unit described above, where the processor is configured to send buffered operational data to the remote computing device based on a trigger signal received from a vehicle operator, even if an anomalous condition has not been detected.
- The second telematics unit described above, where after buffered operational data has been sent to the remote computing device in response to the detection of an anomalous condition, the processor is configured to monitor a warning lamp status associated with the anomaly, and to use the data link to send lamp escalation data to the remote computing device when that warning lamp changes condition.
- A system for detecting an anomalous condition with a vehicle and diagnosing that anomalous condition: (a) a vehicle comprising: (i) at least one sensor for generating vehicle operational data; (ii) a first in, first out buffer in which operational data is temporarily stored during operation of the vehicle; (iii) a data link for wirelessly conveying data from the vehicle to a remote location; and (iv) a processor configured to use the data link to send operational data from the buffer to the remote location when an anomalous condition is detected at the vehicle; and (b) a computing device at the remote location, the computing device being configured to implement the function of analyzing the buffered operational data received from the vehicle to diagnose the anomalous condition.
- The system described above, where the computing device at the remote location IS configured to automatically alert the operator of the vehicle about the diagnosis. Such an alert can be conveyed using at least one of a text message, an email message, and an automated telephone message.
- The system described above, where the processor in the vehicle is configured to include position data defining a location of the vehicle when the anomaly is detected with the data being conveyed to the remote computing device.
- The system described above, where the processor in the vehicle is configured to ignore anomalies, and thus not send data to the remote computing device, for a predetermined period of time following vehicle startup.
- The system described above, where the processor in the vehicle is configured to ignore anomalies when a location of the vehicle at startup corresponds to a predefined location. In some embodiments, each such predefined location is stored in the vehicle, while in other embodiments, upon startup the processor communicates with the remote computing device to determine if the vehicle's present location indicates that anomalies should be ignored.
- The system described above, where the processor in the vehicle is configured to ignore anomalies that are repetitive.
- The system described above, where the processor in the vehicle is configured to monitor lamp status associated with a previously detected anomaly, and if the lamp status of a warning lamp associated with that anomaly changes, the processor is configured to convey lamp escalation data to the remote computing device.
- The system described above, where the processor in the vehicle is configured to convey buffered operational data to the remote computing device based on an operator trigger, even if no anomaly has been detected.
- The system described above, where the computing device at the remote location is configured to automatically schedule a repair of the vehicle.
- The system described above, where the computing device at the remote location is configured to automatically schedule a repair of the vehicle based on a current location of the vehicle using location data received from the vehicle with the buffered operational data.
- The system described above, where the computing device at the remote location is configured to automatically order parts required to repair the vehicle.
- The system described above, where the computing device at the remote location is configured to receive and store position data from the vehicle during normal operation of the vehicle, and when buffered operational data is received from the vehicle, the computing device automatically forwards the buffered operational data to a computing device operated by a different entity, the different entity performing the diagnosis. In such a system, the buffered operational data received by the first entity may require reformatting to a different data format, such as XML, before sending the data to the second entity for analysis.
- A method for detecting an anomalous condition with a vehicle and diagnosing that anomalous condition, including the steps of: (a) storing operational data generated while operating a vehicle in a first in, first out buffer during operation of the vehicle; (b) detecting an anomalous condition; (c) using a data link to wirelessly convey buffered operational data from the vehicle to a remote location; and (d) analyzing the buffered operational data at the remote location to diagnose the anomalous condition.
- The method described above, where a computing device at the remote location IS configured to automatically alert the operator of the vehicle about the diagnosis. Such an alert can be conveyed using at least one of a text message, an email message, and an automated telephone message.
- The method described above, where a processor in the vehicle is configured to include position data defining a location of the vehicle when the anomaly is detected with the data being conveyed to the remote location.
- The method described above, where a processor in the vehicle is configured to ignore anomalies, and thus not send data to the remote location, for a predetermined period of time following vehicle startup.
- The method described above, where a processor in the vehicle is configured to ignore anomalies when a location of the vehicle at startup corresponds to a predefined location. In some embodiments, each such predefined location is stored in the vehicle, while in other embodiments, upon startup the processor communicates with a remote computing device to determine if the vehicle's present location indicates that anomalies should be ignored.
- The method described above, where a processor in the vehicle IS configured to ignore anomalies that are repetitive.
- The method described above, where a processor in the vehicle is configured to monitor lamp status associated with a previously detected anomaly, and if the lamp status of a warning lamp associated with that anomaly changes, the processor is configured to convey lamp escalation data to the remote computing device.
- The method described above, where a processor in the vehicle is configured to convey buffered operational data to the remote computing device based on an operator trigger, even if no anomaly has been detected.
- The method described above, where a computing device at the remote location is configured to automatically schedule a repair of the vehicle.
- The method described above, where a computing device at the remote location is configured to automatically schedule a repair of the vehicle based on a current location of the vehicle using location data received from the vehicle with the buffered operational data.
- The method described above, where a computing device at the remote location is configured to automatically order parts required to repair the vehicle.
- The method described above, where a computing device at the remote location is configured to receive and store position data from the vehicle during normal operation of the vehicle, and when buffered operational data is received from the vehicle, the computing device automatically forwards the buffered operational data to a computing device operated by a different entity, the different entity performing the diagnosis. In such a method, the buffered operational data received by the first entity may require reformatting to a different data format, such as XML, before sending the data to the second entity for analysis.
- Although the concepts disclosed herein have been described in connection with the preferred form of practicing them and modifications thereto, those of ordinary skill in the art will understand that many other modifications can be made thereto within the scope of the claims that follow. Accordingly, it is not intended that the scope of these concepts in any way be limited by the above description, but instead be determined entirely by reference to the claims that follow.
Claims (20)
1. A system, comprising:
a remote computing device; and
an onboard vehicle data collection device logically coupled to a vehicle data bus over which passes a stream of vehicle operational data, the onboard vehicle data collection device including:
a memory;
a ring buffer arranged in the memory;
a data monitoring element to capture a predefined subset of vehicle operational data from the vehicle data bus during vehicle operation, such that the predefined subset of vehicle operational data is continuously copied into the ring buffer during vehicle operation;
a trigger detection element to:
monitor the stream of vehicle operational data;
detect a plurality of predefined trigger events; and
upon detection of a first trigger event of the plurality of predefined trigger events, copy a portion of vehicle operational data stored in the ring buffer to an area of the memory allocated for trigger event data that will be wirelessly transmitted to a remote data storage element, wherein the trigger event data includes data representing the first trigger event and the portion of vehicle operational data stored in the ring buffer; and
a wireless data link device to communicate the trigger event data to the remote data storage element.
2. A system according to claim 1 , wherein the onboard vehicle data collection device comprises:
a vehicle location sensing element to supply vehicle location data, wherein the trigger event data includes vehicle location data supplied by the vehicle location sensing element at a time proximate the detection of the first trigger event.
3. A system according to claim 1 , wherein the trigger event data also includes at least some vehicle operational data stored in the ring buffer for a predefined period of time before the detection of the first trigger event.
4. A system according to claim 1 , wherein the trigger event data also includes at least some vehicle operational data stored in the ring buffer for a predefined period of time after the detection of the first trigger event.
5. A system according to claim 1 , wherein the trigger event data also includes at least some vehicle operational data stored in the ring buffer for a first predefined period of time before the detection of the first trigger event, and at least some vehicle operational data stored in the ring buffer for a second predefined period of time after the detection of the first trigger event.
6. A system according to claim 5 , wherein the first predefined period of time is about thirty seconds and the second predefined period of time is about fifteen seconds.
7. A system according to claim 1 , wherein the first trigger event is directed towards an engine fuel supply event, a vehicle braking event, a vehicle cooling event, or a vehicle transmission event.
8. A system according to claim 1 , wherein the onboard vehicle data collection device comprises:
a user input arranged to manually cause the first trigger event.
9. A system according to claim 1 , wherein the onboard vehicle data collection device forces detection of a second trigger event, the second trigger event.
10. A system according to claim 1 , wherein the portion of vehicle operational data stored in the ring buffer has a reconfigurable size.
11. A method, comprising:
operating a vehicle;
passing a stream of vehicle operational data over a vehicle data bus;
continuously capturing, via an onboard vehicle data collection device logically coupled to the vehicle data bus, a predefined subset of vehicle operational data from the vehicle data bus while operating the vehicle;
continuously storing the captured predefined subset of vehicle operational data in a ring buffer arranged in a memory;
detecting, via a trigger detection element, a first trigger event of a detectable plurality of predefined trigger events;
upon detecting the first trigger event, copying a portion of vehicle operational data from the ring buffer to an area of the memory allocated for trigger event data, wherein the trigger event data includes data representing the first trigger event and the portion of vehicle operational data copied into the ring buffer upon detecting the first trigger event; and
communicating, via a wireless data link device, the trigger event data to a remote data storage element.
12. A method according to claim 11 , wherein detecting the first trigger event includes:
monitoring, via the trigger detection element, the stream of vehicle operational data.
13. A method according to claim 11 , wherein detecting the first trigger event includes:
monitoring, via the trigger detection element, the captured predefined subset of vehicle operational data.
14. A method according to claim 11 , wherein detecting the first trigger event includes:
providing vehicle location data via a vehicle location sensing element, wherein the trigger event data includes vehicle location data provided by the vehicle location sensing element at a time proximate the detection of the first trigger event.
15. A method according to claim 11 , wherein the trigger event data also includes at least some vehicle operational data stored in the ring buffer for a first predefined period of time before detecting the first trigger event, and at least some vehicle operational data stored in the ring buffer for a second predefined period of time after detecting the first trigger event.
16. An onboard vehicle data collection device, comprising:
a memory;
a ring buffer arranged in the memory;
a data monitoring element coupled to a vehicle data bus over which passes a stream of vehicle operational data, the data monitoring element arranged to capture a predefined subset of vehicle operational data from the vehicle data bus during vehicle operation such that the predefined subset of vehicle operational data is continuously copied into the ring buffer during vehicle operation;
a trigger detection element to:
monitor vehicle operational data;
detect, based on the monitored vehicle operational data, a plurality of predefined trigger events; and
upon detection of a first trigger event of the plurality of detectable predefined trigger events, copy a portion of vehicle operational data stored in the ring buffer to an area of the memory allocated for trigger event data, wherein the trigger event data includes data representing the first trigger event and the portion of vehicle operational data stored in the ring buffer; and
a wireless data link interface to communicate the trigger event data toward a remote data storage element.
17. An onboard vehicle data collection device according to claim 16 , wherein the trigger detection element to monitor the vehicle operational data is arranged to monitor the stream of vehicle operational data.
18. An onboard vehicle data collection device according to claim 16 , wherein the trigger detection element to monitor the vehicle operational data is arranged to monitor the predefined subset of vehicle operational data that is continuously copied into the ring buffer.
19. An onboard vehicle data collection device according to claim 16 , wherein the trigger event data also includes at least some vehicle operational data stored in the ring buffer for a first predefined period of time before detecting the first trigger event, and at least some vehicle operational data stored in the ring buffer for a second predefined period of time after detecting the first trigger event.
20. An onboard vehicle data collection device according to claim 16 , wherein the trigger event data is only communicated toward the remote data storage element upon detection of the first trigger event.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/231,177 US20160350985A1 (en) | 2010-08-27 | 2016-08-08 | Vehicle diagnostic monitor tool |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US37786510P | 2010-08-27 | 2010-08-27 | |
US12/956,961 US20120136802A1 (en) | 2010-11-30 | 2010-11-30 | System and method for vehicle maintenance including remote diagnosis and reverse auction for identified repairs |
US13/157,184 US10600096B2 (en) | 2010-11-30 | 2011-06-09 | System and method for obtaining competitive pricing for vehicle services |
US13/157,203 US20120136743A1 (en) | 2010-11-30 | 2011-06-09 | System and method for obtaining competitive pricing for vehicle services |
US13/219,467 US10665040B2 (en) | 2010-08-27 | 2011-08-26 | Method and apparatus for remote vehicle diagnosis |
US15/231,177 US20160350985A1 (en) | 2010-08-27 | 2016-08-08 | Vehicle diagnostic monitor tool |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/219,467 Continuation US10665040B2 (en) | 2010-08-27 | 2011-08-26 | Method and apparatus for remote vehicle diagnosis |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160350985A1 true US20160350985A1 (en) | 2016-12-01 |
Family
ID=45698270
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/219,467 Active US10665040B2 (en) | 2010-08-27 | 2011-08-26 | Method and apparatus for remote vehicle diagnosis |
US15/231,160 Abandoned US20160343177A1 (en) | 2010-08-27 | 2016-08-08 | Real time vehicle diagnosis system |
US15/231,177 Abandoned US20160350985A1 (en) | 2010-08-27 | 2016-08-08 | Vehicle diagnostic monitor tool |
US15/231,142 Active US11080950B2 (en) | 2010-08-27 | 2016-08-08 | Cooperative vehicle diagnosis system |
US16/863,735 Active 2033-01-09 US11978291B2 (en) | 2010-08-27 | 2020-04-30 | Method and apparatus for remote vehicle diagnosis |
US17/080,502 Pending US20210074088A1 (en) | 2010-08-27 | 2020-10-26 | Cooperative vehicle disgnosis system |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/219,467 Active US10665040B2 (en) | 2010-08-27 | 2011-08-26 | Method and apparatus for remote vehicle diagnosis |
US15/231,160 Abandoned US20160343177A1 (en) | 2010-08-27 | 2016-08-08 | Real time vehicle diagnosis system |
Family Applications After (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/231,142 Active US11080950B2 (en) | 2010-08-27 | 2016-08-08 | Cooperative vehicle diagnosis system |
US16/863,735 Active 2033-01-09 US11978291B2 (en) | 2010-08-27 | 2020-04-30 | Method and apparatus for remote vehicle diagnosis |
US17/080,502 Pending US20210074088A1 (en) | 2010-08-27 | 2020-10-26 | Cooperative vehicle disgnosis system |
Country Status (1)
Country | Link |
---|---|
US (6) | US10665040B2 (en) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170339056A1 (en) * | 2014-12-10 | 2017-11-23 | Toyota Jidosha Kabushiki Kaisha | Remote vehicle data collection system |
US20190141072A1 (en) * | 2016-12-06 | 2019-05-09 | Panasonic Intellectual Property Corporation Of America | Information processing device and information processing method |
US10600096B2 (en) | 2010-11-30 | 2020-03-24 | Zonar Systems, Inc. | System and method for obtaining competitive pricing for vehicle services |
CN110933021A (en) * | 2018-09-19 | 2020-03-27 | 罗伯特·博世有限公司 | Method and device for abnormality detection in a vehicle |
US10665040B2 (en) | 2010-08-27 | 2020-05-26 | Zonar Systems, Inc. | Method and apparatus for remote vehicle diagnosis |
US10872479B1 (en) | 2019-11-04 | 2020-12-22 | Ford Global Technologies, Llc | Secure log capture |
EP3771981A4 (en) * | 2018-04-06 | 2021-04-14 | Panasonic Intellectual Property Corporation of America | Log output method, log output device, and program |
US11915203B2 (en) | 2019-11-20 | 2024-02-27 | Polaris Industries Inc. | Vehicle service scheduling |
Families Citing this family (95)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8631411B1 (en) | 2009-07-21 | 2014-01-14 | The Research Foundation For The State University Of New York | Energy aware processing load distribution system and method |
US20120215491A1 (en) * | 2011-02-21 | 2012-08-23 | Snap-On Incorporated | Diagnostic Baselining |
FR2980887B1 (en) * | 2011-09-30 | 2021-11-12 | Ier Systems | METHOD AND SYSTEM FOR SECURING A VEHICLE OFFERED FOR RENTAL, AND INSTALLATION FOR RENTAL OF VEHICLES IMPLEMENTING SUCH SYSTEM OR PROCESS. |
US8868064B1 (en) * | 2011-11-09 | 2014-10-21 | Sprint Communications Company L.P. | Mobile device metrics management |
US9372831B2 (en) * | 2011-12-09 | 2016-06-21 | Fujitsu Ten Limited | Remote starter |
JP2013123096A (en) * | 2011-12-09 | 2013-06-20 | Fujitsu Ten Ltd | Remote starter, information processor and remote start system |
US9501375B2 (en) | 2012-02-07 | 2016-11-22 | Mts Systems Corporation | Mobile application tool and graphical user interface |
GB2501291A (en) * | 2012-04-19 | 2013-10-23 | Project Vanguard Ltd | Diagnostic system with predicted problem cause feedback |
DE102012010887A1 (en) * | 2012-06-01 | 2013-12-05 | Audi Ag | Motor vehicle with a control device for a non-vehicle computer system |
EP2680534B1 (en) | 2012-06-28 | 2017-12-27 | Harman Becker Automotive Systems GmbH | Logging for telematic systems |
US20160217628A1 (en) * | 2012-08-29 | 2016-07-28 | GM Global Technology Operations LLC | Method and apparatus for on-board/off-board fault detection |
US10083548B2 (en) * | 2012-09-07 | 2018-09-25 | Cellco Partnership | Appliance diagnostic information via a wireless communication link |
JP6067315B2 (en) | 2012-10-12 | 2017-01-25 | 富士通テン株式会社 | Vehicle control apparatus and vehicle control method |
WO2014062666A1 (en) | 2012-10-16 | 2014-04-24 | Fleetcor Technologies Operating Company, Llc | Communication of promotions based on data associated with a vehicle |
US9940615B2 (en) | 2012-10-16 | 2018-04-10 | Fleetcor Technologies Operating Company, Llc | Automated pairing of payment products and mobile to mobile devices |
US10162693B1 (en) | 2012-10-18 | 2018-12-25 | Sprint Communications Company L.P. | Evaluation of mobile device state and performance metrics for diagnosis and troubleshooting of performance issues |
US8924071B2 (en) * | 2013-04-26 | 2014-12-30 | Ford Global Technologies, Llc | Online vehicle maintenance |
CN103336522A (en) * | 2013-05-30 | 2013-10-02 | 长城汽车股份有限公司 | Vehicle fault inquiry system, controller and vehicle |
US9524592B2 (en) | 2013-06-03 | 2016-12-20 | Honda Motor Co., Ltd. | Driving analytics |
US9165413B2 (en) | 2013-06-03 | 2015-10-20 | Honda Motor Co., Ltd. | Diagnostic assistance |
US9037572B2 (en) | 2013-06-03 | 2015-05-19 | Honda Motor Co., Ltd. | Event driven snapshots |
US9324194B2 (en) * | 2013-06-11 | 2016-04-26 | Innova Electronics, Inc. | Method and system for database compilation on a remote electronic device |
US9885237B2 (en) * | 2013-09-23 | 2018-02-06 | Emerson Electric (Us) Holding Corporation (Chile) Limitada | Apparatus and method for monitoring health of articulating machinery |
CN110837448B (en) * | 2013-09-30 | 2023-10-10 | Mts系统公司 | Method and computing device for remotely monitoring a test performed in a test device |
US20150199693A1 (en) * | 2014-01-13 | 2015-07-16 | David Owen Wehmeyer | System and Method of Monitoring Vehicle Disposal of Regulated Substances |
EP3650262A1 (en) | 2014-04-04 | 2020-05-13 | Superpedestrian, Inc. | Systems, methods, and devices for the operation of electrically motorized vehicles |
US10308065B2 (en) | 2014-04-04 | 2019-06-04 | Superpedestrian, Inc. | Devices and methods for connecting a spoke to a hub |
EP3224056A4 (en) | 2014-11-24 | 2018-08-22 | Superpedestrian, Inc. | Devices and methods of a motorized wheel |
US9767626B2 (en) * | 2015-07-09 | 2017-09-19 | Ford Global Technologies, Llc | Connected services for vehicle diagnostics and repairs |
US10347055B2 (en) * | 2015-09-28 | 2019-07-09 | Noregon Systems, Inc. | Method and apparatus for connecting to a heavy duty vehicle and performing a vehicle roadworthiness check |
KR20170056331A (en) * | 2015-11-13 | 2017-05-23 | 한국전자통신연구원 | Information processing system and method for information processing thereof |
US20170168920A1 (en) * | 2015-12-09 | 2017-06-15 | Dspace Digital Signal Processing And Control Engineering Gmbh | Transfer of payload data |
US9460616B1 (en) | 2015-12-16 | 2016-10-04 | International Business Machines Corporation | Management of mobile objects and service platform for mobile objects |
JP2017117193A (en) * | 2015-12-24 | 2017-06-29 | 三菱自動車工業株式会社 | Vehicle information management system |
GB2546253B (en) | 2016-01-06 | 2020-04-22 | Ge Aviat Systems Ltd | Fusion of aviation-related data for comprehensive aircraft system health monitoring |
US10701859B2 (en) | 2016-01-07 | 2020-07-07 | Exmark Manufacturing Company, Incorporated | Electronic controller and turf maintenance vehicle incorporating same |
JP6671248B2 (en) | 2016-06-08 | 2020-03-25 | 株式会社日立製作所 | Abnormality candidate information analyzer |
JP6846991B2 (en) * | 2016-07-05 | 2021-03-24 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Anomaly detection electronic control unit, in-vehicle network system and anomaly detection method |
FR3055986B1 (en) * | 2016-09-13 | 2018-10-12 | Peugeot Citroen Automobiles Sa | DEVICE FOR CONTROLLING THE RESETTING OF A MOTORCYCLE ELECTRONIC CALCULATOR |
US10943283B2 (en) * | 2016-11-18 | 2021-03-09 | Cummins Inc. | Service location recommendation tailoring |
EP4304194A3 (en) * | 2016-11-23 | 2024-03-20 | Senzit, Inc. | A filter element analysis system and associated methods |
US20180144559A1 (en) * | 2016-11-23 | 2018-05-24 | Mann+Hummel Gmbh | Filter element analysis system and associated methods |
CN108886489B (en) * | 2016-12-06 | 2021-08-03 | 松下电器(美国)知识产权公司 | Information processing apparatus and information processing method |
JP6490879B2 (en) | 2016-12-06 | 2019-03-27 | パナソニック インテレクチュアル プロパティ コーポレーション オブ アメリカPanasonic Intellectual Property Corporation of America | Information processing apparatus and information processing method |
US11036883B2 (en) * | 2017-01-23 | 2021-06-15 | Raytheon Technologies Corporation | Data filtering for data request workflow system |
US11514056B2 (en) * | 2017-01-23 | 2022-11-29 | Raytheon Technologies Corporation | Data request workflow system |
WO2018156709A1 (en) * | 2017-02-24 | 2018-08-30 | Cummins Filtration Ip, Inc. | Filtration monitoring system data transmission |
JP6694113B2 (en) * | 2017-03-31 | 2020-05-13 | 日立建機株式会社 | Road surface management system and road surface management method |
EP3616366B1 (en) * | 2017-04-25 | 2021-05-19 | Munic | Method to write requests on a vehicle diagnostic bus |
US10510194B2 (en) * | 2017-06-12 | 2019-12-17 | Ford Global Technologies, Llc | Cloud-based connectivity energy budget manager |
JP6718415B2 (en) * | 2017-06-26 | 2020-07-08 | 株式会社日立ビルシステム | Parts replacement prediction device, parts replacement prediction system, parts replacement prediction method |
WO2019021064A1 (en) | 2017-07-25 | 2019-01-31 | Aurora Labs Ltd | Constructing software delta updates for vehicle ecu software and abnormality detection based on toolchain |
US10547502B2 (en) | 2017-08-10 | 2020-01-28 | Ford Global Technologies, Llc | Vehicle communications |
KR102411961B1 (en) * | 2017-09-07 | 2022-06-22 | 현대자동차주식회사 | Vehicle And Control Method Thereof |
US10686815B2 (en) | 2017-09-11 | 2020-06-16 | GM Global Technology Operations LLC | Systems and methods for in-vehicle network intrusion detection |
US10498749B2 (en) * | 2017-09-11 | 2019-12-03 | GM Global Technology Operations LLC | Systems and methods for in-vehicle network intrusion detection |
EP4216050A1 (en) * | 2017-10-03 | 2023-07-26 | Google LLC | Actionable event determination based on vehicle diagnostic data |
DE102018218185A1 (en) * | 2017-10-31 | 2019-07-11 | Robert Bosch Gmbh | Brake Pad Monitor with wireless connectivity |
EP3721344A1 (en) | 2017-12-07 | 2020-10-14 | Mts Systems Corporation | Integrated machine information management with application interactive user interface |
US10977881B1 (en) * | 2018-01-09 | 2021-04-13 | United Services Automobile Association (Usaa) | Rules based analysis of vehicle sensor data for actions |
FR3086407B1 (en) * | 2018-09-21 | 2021-08-13 | Continental Automotive France | ANOMALY IDENTIFICATION PROCESS FOR VEHICLE |
CN109240273A (en) * | 2018-11-02 | 2019-01-18 | 上海博泰悦臻网络技术服务有限公司 | Vehicle remote diagnosis method, server-side, engine end and client based on cloud |
US11417153B2 (en) * | 2018-12-21 | 2022-08-16 | Continental Autonomous Mobility US, LLC | Self-service repair for autonomous vehicles |
JP2020184651A (en) * | 2019-04-26 | 2020-11-12 | 日本電産モビリティ株式会社 | On-vehicle control device and information processing device |
US11195343B2 (en) * | 2019-05-30 | 2021-12-07 | The Boeing Company | Maintenance systems enhancement |
US11014534B2 (en) | 2019-07-13 | 2021-05-25 | Toyota Motor North America, Inc. | Remote access of transports |
US11386722B2 (en) | 2019-07-13 | 2022-07-12 | Toyota Motor North America, Inc. | Remote access of transports |
US11699308B2 (en) | 2019-07-29 | 2023-07-11 | Toyota Motor North America, Inc. | Tracking of transport data |
US11217041B2 (en) * | 2019-07-29 | 2022-01-04 | Toyota Motor North America, Inc. | Tracking of transport data |
US11500571B2 (en) | 2019-07-29 | 2022-11-15 | Toyota Motor North America, Inc. | Tracking of transport data |
CN110703736A (en) * | 2019-10-24 | 2020-01-17 | 深圳市道通科技股份有限公司 | Automobile diagnosis device, system and method |
JP7312965B2 (en) * | 2019-11-01 | 2023-07-24 | パナソニックIpマネジメント株式会社 | Information processing device, information processing method, and program |
JP7428555B2 (en) * | 2020-03-16 | 2024-02-06 | 本田技研工業株式会社 | Control device, system, program, and control method |
DE102020108581A1 (en) | 2020-03-27 | 2021-09-30 | Zf Cv Systems Global Gmbh | Data acquisition device for mobile devices, method for carrying out a preliminary analysis in a data acquisition device, vehicle and a correspondingly designed computer program |
JP7417860B2 (en) * | 2020-03-31 | 2024-01-19 | マツダ株式会社 | Vehicle information communication device and vehicle information communication method |
US11967189B2 (en) | 2020-04-20 | 2024-04-23 | Innova Electronics Corporation | Router for communicating vehicle data to a vehicle resource |
US11651628B2 (en) | 2020-04-20 | 2023-05-16 | Innova Electronics Corporation | Router for vehicle diagnostic system |
DE102020130609A1 (en) | 2020-11-19 | 2022-05-19 | Bayerische Motoren Werke Aktiengesellschaft | Method and device for analyzing and/or eliminating a vehicle problem |
US11837032B2 (en) * | 2020-12-31 | 2023-12-05 | Micron Technology, Inc. | Vehicle diagnosis and repair |
FR3119030A1 (en) * | 2021-01-18 | 2022-07-22 | Psa Automobiles Sa | Method for managing the operation of an electronic control unit of a motor vehicle, associated system, electronic control unit and motor vehicle |
CN113176987B (en) * | 2021-04-29 | 2023-09-15 | 华人运通(上海)云计算科技有限公司 | Log processing method, device and equipment of vehicle control instruction block and storage medium |
CN115263587B (en) * | 2021-04-29 | 2023-10-20 | 三一汽车制造有限公司 | Engine maintenance prompting method and device of working machine and electronic equipment |
US12024100B2 (en) * | 2021-05-19 | 2024-07-02 | Pony Ai Inc. | Device-level fault detection |
CN113485176B (en) * | 2021-06-22 | 2022-11-18 | 东风汽车集团股份有限公司 | Vehicle data acquisition, caching and retransmission method and remote monitoring terminal |
WO2023102765A1 (en) * | 2021-12-08 | 2023-06-15 | 陈献忠 | Fault alarm system for intelligent electric locomotive |
CN114490257B (en) * | 2022-01-13 | 2022-10-21 | 星河智联汽车科技有限公司 | Method, device and equipment for collecting logs of vehicle |
CN114419756B (en) * | 2022-01-30 | 2023-05-16 | 重庆长安汽车股份有限公司 | Method and system for dynamically capturing abnormal scene of whole vehicle |
GB2615763A (en) * | 2022-02-16 | 2023-08-23 | Belron Int Ltd | Vehicle diagnostic methods and systems |
CN114550340B (en) * | 2022-02-24 | 2023-07-18 | 深蓝汽车科技有限公司 | Method and system for remote diagnosis of controller |
CN115102706B (en) * | 2022-04-27 | 2023-10-20 | 麦格纳斯太尔汽车技术(上海)有限公司 | HOST-IDS safety detection system and method of vehicle ECU |
CN114821858B (en) * | 2022-04-29 | 2023-07-07 | 东风商用车有限公司 | Method, device, equipment and storage medium for illustrating abnormal vehicle index |
DE102022127303B4 (en) | 2022-10-18 | 2024-06-20 | Cariad Se | Computer-implemented method for identifying a defect in a motor vehicle |
CN115761933B (en) * | 2022-11-03 | 2024-05-24 | 成都赛力斯科技有限公司 | Automobile fault recovery method, device, computer equipment and storage medium |
US20240203168A1 (en) * | 2022-12-15 | 2024-06-20 | Cox Automotive, Inc. | Systems and methods for automatically predicting and scheduling vehicle repairs |
EP4421760A1 (en) * | 2023-02-27 | 2024-08-28 | Volvo Truck Corporation | A bodybuilder module for data logging and a data logging method |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974483A (en) * | 1997-05-21 | 1999-10-26 | Microsoft Corporation | Multiple transparent access to in put peripherals |
US6438472B1 (en) * | 1998-09-12 | 2002-08-20 | Data Tec. Co., Ltd. | Operation control system capable of analyzing driving tendency and its constituent apparatus |
US20020133273A1 (en) * | 2001-03-14 | 2002-09-19 | Lowrey Larkin Hill | Internet-based vehicle-diagnostic system |
US20020177926A1 (en) * | 2000-10-06 | 2002-11-28 | Lockwood Robert Farrell | Customer service automation systems and methods |
US20060089767A1 (en) * | 2004-10-25 | 2006-04-27 | Sowa Michael A | Vehicles fault diagnostic systems and methods |
US20070241874A1 (en) * | 2006-04-17 | 2007-10-18 | Okpysh Stephen L | Braking intensity light |
US20080049123A1 (en) * | 2006-08-25 | 2008-02-28 | Sportvision, Inc. | Video effect using movement within an image |
US20080167758A1 (en) * | 2007-01-08 | 2008-07-10 | Ford Global Technologies, Llc | Wireless Gateway Apparatus and Method of Bridging Data Between Vehicle Based and External Data Networks |
US7953530B1 (en) * | 2006-06-08 | 2011-05-31 | Pederson Neal R | Vehicle diagnostic tool |
Family Cites Families (344)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB1165051A (en) | 1967-05-31 | 1969-09-24 | Horstman Gear Company Ltd | Watchman Location System. |
US4092718A (en) | 1974-03-21 | 1978-05-30 | Wendt Hans J | Computerized dispatching system |
US3990067A (en) | 1974-09-30 | 1976-11-02 | Sentry Technology Incorporated | Electronic security tour system |
US4025791A (en) | 1975-08-12 | 1977-05-24 | Kilo Corporation | Object identification system |
US4258421A (en) | 1978-02-27 | 1981-03-24 | Rockwell International Corporation | Vehicle monitoring and recording system |
US4263945A (en) | 1979-06-20 | 1981-04-28 | Ness Bradford O Van | Automatic fuel dispensing control system |
US4325057A (en) | 1980-06-30 | 1982-04-13 | Bishop-Hall, Inc. | School bus approach notification method and apparatus |
GB2100705B (en) | 1981-06-23 | 1985-01-30 | Monitronix Syst | Monitored delivery systems |
US4658371A (en) | 1981-12-16 | 1987-04-14 | Art Systems, Inc. | Fuel dispensing and vehicle maintenance system with on-board computer |
US4602127A (en) | 1984-03-09 | 1986-07-22 | Micro Processor Systems, Inc. | Diagnostic data recorder |
NL8501581A (en) | 1985-06-03 | 1987-01-02 | Nedap Nv | METHOD FOR SELECTIVE FILLING OR EMPTYING STORAGE OR STOCK TANKS. |
EP0219859B1 (en) | 1985-10-25 | 1993-10-06 | Mitsubishi Denki Kabushiki Kaisha | Route bus service controlling system |
US4763356A (en) | 1986-12-11 | 1988-08-09 | AT&T Information Systems, Inc. American Telephone and Telegraph Company | Touch screen form entry system |
US4804937A (en) | 1987-05-26 | 1989-02-14 | Motorola, Inc. | Vehicle monitoring arrangement and system |
DE3828725A1 (en) | 1987-09-29 | 1989-04-13 | Pioneer Electronic Corp | METHOD FOR RECORDING THE DRIVING ROUTE DATA FOR A NAVIGATION DEVICE OF A MOTOR VEHICLE |
GB8815584D0 (en) | 1988-06-30 | 1988-08-03 | Analytical Instr Ltd | Fleet data monitoring system |
US4935195A (en) | 1988-08-29 | 1990-06-19 | Westinghouse Electric Corp. | Corrosion-erosion trend monitoring and diagnostic system |
US5120942A (en) | 1989-02-02 | 1992-06-09 | Computer Systems Design Inc. | Portable tour monitor device, report generating system and programming device therefor |
US5058044A (en) | 1989-03-30 | 1991-10-15 | Auto I.D. Inc. | Automated maintenance checking system |
DE3942070A1 (en) | 1989-12-20 | 1991-06-27 | Deutsche Lufthansa | DEVICE FOR MANAGING A VARIETY OF MOTOR VEHICLES |
AU634341B2 (en) | 1990-01-11 | 1993-02-18 | Kabushiki Kaisha Toshiba | Apparatus for supporting inspection of plant |
US5359522A (en) | 1990-05-09 | 1994-10-25 | Ryan Michael C | Fluid delivery control apparatus |
US5072380A (en) | 1990-06-12 | 1991-12-10 | Exxon Research And Engineering Company | Automatic vehicle recognition and customer billing system |
US5204819A (en) | 1990-08-27 | 1993-04-20 | Ryan Michael C | Fluid delivery control apparatus |
US5068656A (en) | 1990-12-21 | 1991-11-26 | Rockwell International Corporation | System and method for monitoring and reporting out-of-route mileage for long haul trucks |
US5128651A (en) | 1991-01-02 | 1992-07-07 | Heckart Daniel | School bus alarm system |
US5809437A (en) | 1995-06-07 | 1998-09-15 | Automotive Technologies International, Inc. | On board vehicle diagnostic module using pattern recognition |
US5479479A (en) | 1991-10-19 | 1995-12-26 | Cell Port Labs, Inc. | Method and apparatus for transmission of and receiving signals having digital information using an air link |
JP3273800B2 (en) | 1991-11-11 | 2002-04-15 | 茂 近藤 | Car driving analysis diagnosis method and device |
US5243323A (en) | 1991-12-20 | 1993-09-07 | Rogers Telecom Products, Inc. | School bus alarm system |
US5223844B1 (en) | 1992-04-17 | 2000-01-25 | Auto Trac Inc | Vehicle tracking and security system |
AU4639393A (en) | 1992-06-16 | 1994-01-04 | Dill Systems Corp. | Magnetic circuits for communicating data |
US5428546A (en) | 1992-10-16 | 1995-06-27 | Mobile Information Systems | Method and apparatus for tracking vehicle location |
US5585552A (en) | 1992-11-09 | 1996-12-17 | The Technician's Company | Method and apparatus for diagnosing automotive engine problems using oxygen |
US5442553A (en) | 1992-11-16 | 1995-08-15 | Motorola | Wireless motor vehicle diagnostic and software upgrade system |
CA2110025A1 (en) | 1992-12-16 | 1994-06-17 | Gerard Joseph Hughes | Automatic vehicle recognition and customer automobile diagnostic system |
US5400018A (en) * | 1992-12-22 | 1995-03-21 | Caterpillar Inc. | Method of relaying information relating to the status of a vehicle |
US5337003A (en) | 1992-12-28 | 1994-08-09 | Carmichael Edward W | Self-contained, clip-on engine operating time log |
US5623258A (en) | 1993-01-05 | 1997-04-22 | Dorfman; Bertrand | Multi-station data capture system |
US5399844A (en) | 1993-01-12 | 1995-03-21 | Facility Management Systems, Inc. | Inspection prompting and reading recording system |
US5719771A (en) * | 1993-02-24 | 1998-02-17 | Amsc Subsidiary Corporation | System for mapping occurrences of conditions in a transport route |
US5671141A (en) * | 1993-04-05 | 1997-09-23 | Ford Global Technologies, Inc. | Computer program architecture for onboard vehicle diagnostic system |
GB9308426D0 (en) | 1993-04-23 | 1993-06-09 | Roster Control Syst Ltd | Watchmans clock system |
US6748318B1 (en) | 1993-05-18 | 2004-06-08 | Arrivalstar, Inc. | Advanced notification systems and methods utilizing a computer network |
US6278936B1 (en) | 1993-05-18 | 2001-08-21 | Global Research Systems, Inc. | System and method for an advance notification system for monitoring and reporting proximity of a vehicle |
US6952645B1 (en) | 1997-03-10 | 2005-10-04 | Arrivalstar, Inc. | System and method for activation of an advance notification system for monitoring and reporting status of vehicle travel |
FR2706934B1 (en) | 1993-06-21 | 1995-10-13 | Valeo Electronique | |
US5394136A (en) | 1993-08-30 | 1995-02-28 | Rockwell International Corporation | Satellite communication and truck driver bonus notification and awards system |
FR2711821B1 (en) | 1993-10-22 | 1995-12-29 | Cogema | Industrial installation monitoring system. |
US5557254A (en) | 1993-11-16 | 1996-09-17 | Mobile Security Communications, Inc. | Programmable vehicle monitoring and security system having multiple access verification devices |
US5459660A (en) | 1993-12-22 | 1995-10-17 | Chrysler Corporation | Circuit and method for interfacing with vehicle computer |
US5572192A (en) | 1994-03-17 | 1996-11-05 | Detection Systems, Inc. | Personal security system with guard tour features |
US7421321B2 (en) * | 1995-06-07 | 2008-09-02 | Automotive Technologies International, Inc. | System for obtaining vehicular information |
US7103460B1 (en) | 1994-05-09 | 2006-09-05 | Automotive Technologies International, Inc. | System and method for vehicle diagnostics |
US7082359B2 (en) * | 1995-06-07 | 2006-07-25 | Automotive Technologies International, Inc. | Vehicular information and monitoring system and methods |
GB2290631B (en) | 1994-06-24 | 1998-11-11 | Fuji Heavy Ind Ltd | Diagnosis system for motor vehicle and the method thereof |
US5541845A (en) | 1994-08-02 | 1996-07-30 | Trimble Navigation Limited | Monitoring of route and schedule adherence |
US5459304A (en) | 1994-09-13 | 1995-10-17 | At&T Ipm Corp. | Smart card techniques for motor vehicle record administration |
US5598534A (en) | 1994-09-21 | 1997-01-28 | Lucent Technologies Inc. | Simultaneous verify local database and using wireless communication to verify remote database |
US6128959A (en) | 1994-11-07 | 2000-10-10 | Eaton Corporation | Driveline vibration analyzer |
DE4441101B4 (en) | 1994-11-18 | 2005-01-27 | Robert Bosch Gmbh | Method and device for determining diagnostic threshold values for a specific type of motor vehicle in the field |
US8280682B2 (en) | 2000-12-15 | 2012-10-02 | Tvipr, Llc | Device for monitoring movement of shipped goods |
US5499182A (en) | 1994-12-07 | 1996-03-12 | Ousborne; Jeffrey | Vehicle driver performance monitoring system |
US5839112A (en) | 1994-12-28 | 1998-11-17 | Automatic Data Processing | Method and apparatus for displaying and selecting vehicle parts |
US5629678A (en) | 1995-01-10 | 1997-05-13 | Paul A. Gargano | Personal tracking and recovery system |
FI99071C (en) | 1995-02-15 | 1997-09-25 | Nokia Mobile Phones Ltd | Procedure for use of applications in a mobile telephone as well as a mobile telephone |
WO1996027513A1 (en) | 1995-03-03 | 1996-09-12 | Qualcomm Incorporated | Method and apparatus for monitoring parameters of vehicle electronic control units |
EP1398293A3 (en) | 1995-03-10 | 2005-02-09 | Michael C. Ryan | Fluid delivery control nozzle |
US5729452A (en) | 1995-03-31 | 1998-03-17 | Envirotest Acquisition Co. | Method and system for diagnosing and reporting failure of a vehicle emission test |
US5680328A (en) | 1995-05-22 | 1997-10-21 | Eaton Corporation | Computer assisted driver vehicle inspection reporting system |
US7650210B2 (en) | 1995-06-07 | 2010-01-19 | Automotive Technologies International, Inc. | Remote vehicle diagnostic management |
US7672756B2 (en) | 1995-06-07 | 2010-03-02 | Automotive Technologies International, Inc. | Vehicle communications using the internet |
DE19526148C2 (en) | 1995-07-07 | 1997-06-05 | Mannesmann Ag | Method and system for forecasting traffic flows |
US5596501A (en) | 1995-07-19 | 1997-01-21 | Powerplant Fuel Modules, Llc | System for dispensing fuel at remote locations, and method of operating same |
US5745049A (en) | 1995-07-20 | 1998-04-28 | Yokogawa Electric Corporation | Wireless equipment diagnosis system |
US5884202A (en) | 1995-07-20 | 1999-03-16 | Hewlett-Packard Company | Modular wireless diagnostic test and information system |
US5700999A (en) | 1995-07-28 | 1997-12-23 | Streicher; Stanley H. | Bar code based refueling system |
DE19532067C1 (en) | 1995-08-31 | 1996-10-24 | Daimler Benz Ag | Programming system for vehicle electronic key |
US6043661A (en) | 1995-09-07 | 2000-03-28 | Gutierrez; Alejandro | School bus and trailer systems tester |
US5671158A (en) | 1995-09-18 | 1997-09-23 | Envirotest Systems Corp. | Apparatus and method for effecting wireless discourse between computer and technician in testing motor vehicle emission control systems |
US5758299A (en) | 1995-11-03 | 1998-05-26 | Caterpillar Inc. | Method for generating performance ratings for a vehicle operator |
US6744352B2 (en) | 1995-11-09 | 2004-06-01 | Vehicle Enhancement Systems, Inc. | System, apparatus and methods for data communication between vehicle and remote data communication terminal, between portions of vehicle and other portions of vehicle, between two or more vehicles, and between vehicle and communications network |
US6064299A (en) | 1995-11-09 | 2000-05-16 | Vehicle Enhancement Systems, Inc. | Apparatus and method for data communication between heavy duty vehicle and remote data communication terminal |
US5794164A (en) | 1995-11-29 | 1998-08-11 | Microsoft Corporation | Vehicle computer system |
US5956259A (en) | 1995-12-08 | 1999-09-21 | Gilbarco Inc. | Intelligent fueling |
US6169938B1 (en) | 1995-12-08 | 2001-01-02 | Marconi Commerce Systems Inc. | Transponder communication of ORVR presence |
US5742915A (en) | 1995-12-13 | 1998-04-21 | Caterpillar Inc. | Position referenced data for monitoring and controlling |
US7640185B1 (en) | 1995-12-29 | 2009-12-29 | Dresser, Inc. | Dispensing system and method with radio frequency customer identification |
US5732074A (en) | 1996-01-16 | 1998-03-24 | Cellport Labs, Inc. | Mobile portable wireless communication system |
US5890061A (en) | 1996-02-09 | 1999-03-30 | Ford Motor Company | Vehicular emergency message system with call restriction defeating |
US5808565A (en) | 1996-02-20 | 1998-09-15 | E-Systems, Inc. | GPS triggered automatic annunciator for vehicles |
US5731893A (en) | 1996-02-21 | 1998-03-24 | Dominique; Jeffrey M. | Portable microscope for inspecting fiber optic cable |
US5920846A (en) | 1996-02-27 | 1999-07-06 | Southwestern Bell Telephone Co. | Method and system for processing a service request relating to installation, maintenance or repair of telecommunications services provided to a customer premises |
US5867404A (en) | 1996-04-01 | 1999-02-02 | Cairo Systems, Inc. | Method and apparatus for monitoring railway defects |
US5923572A (en) | 1996-04-02 | 1999-07-13 | Pollock; Stephen F. | Fuel dispensing control, authorization and accounting system |
DE19625002B4 (en) | 1996-06-22 | 2005-03-10 | Daimler Chrysler Ag | Vehicle communication system |
US6084870A (en) | 1996-07-22 | 2000-07-04 | Qualcomm Incorporated | Method and apparatus for the remote monitoring and configuration of electronic control systems |
US5862223A (en) | 1996-07-24 | 1999-01-19 | Walker Asset Management Limited Partnership | Method and apparatus for a cryptographically-assisted commercial network system designed to facilitate and support expert-based commerce |
IL128479A (en) | 1996-08-13 | 2002-03-10 | Schmier Kenneth J | Public transit vehicle arrival information system |
CA2265951A1 (en) | 1996-09-16 | 1998-03-19 | Minorplanet Limited | Transferring accumulated data from vehicles |
US5922037A (en) | 1996-09-30 | 1999-07-13 | Vlsi Technology, Inc. | Wireless system for diagnosing examination and programming of vehicular control systems and method therefor |
EP1767406A1 (en) | 1996-11-13 | 2007-03-28 | Toyota Jidosha Kabushiki Kaisha | Vehicle information communication device and vehicle communication system |
JP2001504257A (en) | 1996-11-22 | 2001-03-27 | ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー | Resource allocation |
US5995898A (en) | 1996-12-06 | 1999-11-30 | Micron Communication, Inc. | RFID system in communication with vehicle on-board computer |
US6279390B1 (en) * | 1996-12-17 | 2001-08-28 | Denso Corporation | Thermostat malfunction detecting system for engine cooling system |
AU5823898A (en) | 1997-01-09 | 1998-08-03 | Roadtrac Llc. | Personal vehicle tracking system having cd-rom storing street map data |
US6240365B1 (en) | 1997-01-21 | 2001-05-29 | Frank E. Bunn | Automated vehicle tracking and service provision system |
US6009355A (en) | 1997-01-28 | 1999-12-28 | American Calcar Inc. | Multimedia information and control system for automobiles |
BR9808005A (en) | 1997-03-10 | 2000-03-08 | Global Research Systems Inc | Process, and, system for notifying a user in advance of an imminent arrival of a vehicle. |
US5942753A (en) | 1997-03-12 | 1999-08-24 | Remote Sensing Technologies | Infrared remote sensing device and system for checking vehicle brake condition |
US6253129B1 (en) | 1997-03-27 | 2001-06-26 | Tripmaster Corporation | System for monitoring vehicle efficiency and vehicle and driver performance |
US6405111B2 (en) | 1997-05-16 | 2002-06-11 | Snap-On Technologies, Inc. | System and method for distributed computer automotive service equipment |
US5874891A (en) | 1997-05-22 | 1999-02-23 | Child Check-Mate Systems, Inc. | Alarm system for use on a bus |
DE19725916A1 (en) | 1997-06-19 | 1999-01-28 | Daimler Benz Ag | Computer=aided diagnosis device for electronically-controlled systems in motor vehicle |
JPH1136911A (en) | 1997-07-14 | 1999-02-09 | Unisia Jecs Corp | Fuel injection volume control device |
EP1005627B1 (en) | 1997-08-19 | 2003-10-29 | Siemens VDO Automotive Corporation | Vehicle information system |
US6680694B1 (en) | 1997-08-19 | 2004-01-20 | Siemens Vdo Automotive Corporation | Vehicle information system |
US6263268B1 (en) | 1997-08-26 | 2001-07-17 | Transcontech Corporation | System and method for providing mobile automotive telemetry |
US20020150050A1 (en) | 1999-06-17 | 2002-10-17 | Nathanson Martin D. | Automotive telemetry protocol |
US5890520A (en) | 1997-09-26 | 1999-04-06 | Gilbarco Inc. | Transponder distinction in a fueling environment |
US6070156A (en) | 1997-09-26 | 2000-05-30 | Gilbarco Inc. | Providing transaction estimates in a fueling and retail system |
US6061614A (en) | 1997-10-17 | 2000-05-09 | Amtech Systems Corporation | Electronic tag including RF modem for monitoring motor vehicle performance |
JP3792913B2 (en) | 1997-11-17 | 2006-07-05 | 株式会社東芝 | Maintenance check support device |
US6092021A (en) | 1997-12-01 | 2000-07-18 | Freightliner Corporation | Fuel use efficiency system for a vehicle for assisting the driver to improve fuel economy |
EP0926020A3 (en) | 1997-12-22 | 2002-09-18 | Delphi Technologies, Inc. | Vehicle control using fm subcarrier messaging |
US6054950A (en) | 1998-01-26 | 2000-04-25 | Multispectral Solutions, Inc. | Ultra wideband precision geolocation system |
US6182275B1 (en) | 1998-01-26 | 2001-01-30 | Dell Usa, L.P. | Generation of a compatible order for a computer system |
JP3800794B2 (en) | 1998-03-09 | 2006-07-26 | 株式会社デンソー | Vehicle diagnostic system |
US6664897B2 (en) | 1998-03-09 | 2003-12-16 | William R. Pape | Method and system for livestock data collection and management |
US6202024B1 (en) | 1998-03-23 | 2001-03-13 | Kabushikikaisha Equos Research | Communicatory navigation system |
IL123949A (en) | 1998-04-03 | 2001-07-24 | On Track Innovations Ltd | Data transaction card having extended range |
CA2237415C (en) | 1998-05-13 | 2007-08-14 | B.M.R. Mfg. Inc. | System and method for prompting inspection of a multi-passenger vehicle |
US7209949B2 (en) | 1998-05-29 | 2007-04-24 | Research In Motion Limited | System and method for synchronizing information between a host system and a mobile data communication device |
DE19826059B4 (en) | 1998-06-12 | 2006-04-06 | Zf Friedrichshafen Ag | Method for controlling an automatic transmission |
US6078255A (en) | 1998-06-23 | 2000-06-20 | The Gleason Agency, Inc. | System for logging premises hazard inspections |
US6024142A (en) | 1998-06-25 | 2000-02-15 | Micron Communications, Inc. | Communications system and method, fleet management system and method, and method of impeding theft of fuel |
US6128551A (en) | 1998-07-02 | 2000-10-03 | Megatronics International Corp. | Method and apparatus for management of automated fuel delivery system |
US6311162B1 (en) | 1998-07-25 | 2001-10-30 | Ernst F. Reichwein | Interactive symptomatic recording system and methods |
AU6410999A (en) | 1998-10-13 | 2000-05-01 | Integrated Systems Research Corporation | System and method for fleet tracking |
US6107917A (en) | 1998-10-16 | 2000-08-22 | Carrender; Curtis L. | Electronic tag including RF modem for monitoring motor vehicle performance with filtering |
EP2065869A2 (en) | 1998-11-05 | 2009-06-03 | International Truck and Engine Corporation | Land vehicle communications systems and process for providing information and coordinating vehicle activities |
US6295492B1 (en) | 1999-01-27 | 2001-09-25 | Infomove.Com, Inc. | System for transmitting and displaying multiple, motor vehicle information |
US6246688B1 (en) | 1999-01-29 | 2001-06-12 | International Business Machines Corp. | Method and system for using a cellular phone as a network gateway in an automotive network |
US6199099B1 (en) | 1999-03-05 | 2001-03-06 | Ac Properties B.V. | System, method and article of manufacture for a mobile communication network utilizing a distributed communication network |
US6396413B2 (en) | 1999-03-11 | 2002-05-28 | Telephonics Corporation | Personal alarm monitor system |
US6181994B1 (en) | 1999-04-07 | 2001-01-30 | International Business Machines Corporation | Method and system for vehicle initiated delivery of advanced diagnostics based on the determined need by vehicle |
US6236911B1 (en) | 1999-04-20 | 2001-05-22 | Supersensor (Proprietary) Limited | Load monitoring system and method utilizing transponder tags |
US6505106B1 (en) | 1999-05-06 | 2003-01-07 | International Business Machines Corporation | Analysis and profiling of vehicle fleet data |
US7096193B1 (en) | 1999-05-21 | 2006-08-22 | Servicemagic, Inc. | Facilitating commerce among consumers and service providers by matching ready-to-act consumers and pre-qualified service providers |
US6317668B1 (en) | 1999-06-10 | 2001-11-13 | Qualcomm Incorporated | Paperless log system and method |
US6362730B2 (en) | 1999-06-14 | 2002-03-26 | Sun Microsystems, Inc. | System and method for collecting vehicle information |
US6754183B1 (en) | 1999-06-14 | 2004-06-22 | Sun Microsystems, Inc. | System and method for integrating a vehicle subnetwork into a primary network |
US6507810B2 (en) | 1999-06-14 | 2003-01-14 | Sun Microsystems, Inc. | Integrated sub-network for a vehicle |
AU4128899A (en) | 1999-06-18 | 2001-01-09 | Swisscom Mobile Ag | Interchangeable battery pack for a mobile telephone |
US6529723B1 (en) | 1999-07-06 | 2003-03-04 | Televoke, Inc. | Automated user notification system |
US7181409B1 (en) | 1999-07-07 | 2007-02-20 | The Regents Of The University Of California | Shared vehicle system and method involving reserving vehicles with highest states of charge |
US6256579B1 (en) | 1999-07-13 | 2001-07-03 | Alpine Electronics, Inc. | Vehicle navigation system with road link re-costing |
US6169943B1 (en) | 1999-07-14 | 2001-01-02 | Eaton Corporation | Motor vehicle diagnostic system using hand-held remote control |
DE19933638A1 (en) | 1999-07-17 | 2001-01-18 | Bosch Gmbh Robert | Navigational method for a means of transportation |
US6330499B1 (en) | 1999-07-21 | 2001-12-11 | International Business Machines Corporation | System and method for vehicle diagnostics and health monitoring |
US6662194B1 (en) | 1999-07-31 | 2003-12-09 | Raymond Anthony Joao | Apparatus and method for providing recruitment information |
US8015049B1 (en) | 1999-08-18 | 2011-09-06 | S.F. Ip Properties 61 Llc | On-line appointment system |
US7783507B2 (en) | 1999-08-23 | 2010-08-24 | General Electric Company | System and method for managing a fleet of remote assets |
US20110208567A9 (en) | 1999-08-23 | 2011-08-25 | Roddy Nicholas E | System and method for managing a fleet of remote assets |
MXPA02003346A (en) | 1999-10-01 | 2004-09-10 | Gen Electric Railcar Services | Method and arrangement for inspection and requalification of lined vehicles used for transporting commodities and/or hazardous materials. |
US6380951B1 (en) | 1999-10-01 | 2002-04-30 | Global Graphics Software Limited | Prepress workflow method and program |
US6834259B1 (en) | 1999-10-15 | 2004-12-21 | Timekeeping Systems, Inc. | Guard tour system |
US7027955B2 (en) | 1999-10-15 | 2006-04-11 | Timekeeping Systems, Inc. | Guard tour system incorporating a positioning system |
US8251702B2 (en) | 1999-10-27 | 2012-08-28 | Marks Jeffrey S | Methods and apparatus for online auctions and market-places utilizing program terms |
US6338152B1 (en) * | 1999-10-28 | 2002-01-08 | General Electric Company | Method and system for remotely managing communication of data used for predicting malfunctions in a plurality of machines |
CA2388572A1 (en) | 1999-10-28 | 2001-05-03 | General Electric Company | Diagnosis and repair system and method |
AU2619801A (en) | 1999-10-29 | 2001-06-06 | Gelco Corporation | Method and system for tracking equipment usage information |
US6727818B1 (en) | 1999-10-29 | 2004-04-27 | Hill-Rom Services, Inc. | Hygiene monitoring system |
US6259358B1 (en) | 1999-11-16 | 2001-07-10 | Paul Fjordbotten | School bus safety device |
US20010039508A1 (en) | 1999-12-16 | 2001-11-08 | Nagler Matthew Gordon | Method and apparatus for scoring and matching attributes of a seller to project or job profiles of a buyer |
US7139728B2 (en) | 1999-12-30 | 2006-11-21 | Rod Rigole | Systems and methods for online selection of service providers and management of service accounts |
US6615184B1 (en) | 2000-01-04 | 2003-09-02 | Mitzi Hicks | System and method for providing customers seeking a product or service at a specified discount in a specified geographic area with information as to suppliers offering the same |
US6526335B1 (en) | 2000-01-24 | 2003-02-25 | G. Victor Treyz | Automobile personal computer systems |
US20010047283A1 (en) | 2000-02-01 | 2001-11-29 | Melick Bruce D. | Electronic system for identification, recording, storing, and retrieving material handling equipment records and certifications |
US7401025B1 (en) | 2000-02-15 | 2008-07-15 | Elliott Lokitz | Accessible service provider clearinghouse |
US6370454B1 (en) | 2000-02-25 | 2002-04-09 | Edwin S. Moore Iii | Apparatus and method for monitoring and maintaining mechanized equipment |
US6594621B1 (en) | 2000-03-06 | 2003-07-15 | James H. Meeker | System and method for determining condition of plant |
US6876642B1 (en) | 2000-03-27 | 2005-04-05 | Delphi Technologies, Inc. | In-vehicle wireless local area network |
US20020032597A1 (en) | 2000-04-04 | 2002-03-14 | Chanos George J. | System and method for providing request based consumer information |
US20010037281A1 (en) | 2000-04-13 | 2001-11-01 | Jason French | Request for quote (RFQ) system and method |
US6408232B1 (en) | 2000-04-18 | 2002-06-18 | Agere Systems Guardian Corp. | Wireless piconet access to vehicle operational statistics |
US6856820B1 (en) | 2000-04-24 | 2005-02-15 | Usa Technologies, Inc. | In-vehicle device for wirelessly connecting a vehicle to the internet and for transacting e-commerce and e-business |
US6924750B2 (en) | 2000-05-17 | 2005-08-02 | Omega Patents, L.L.C. | Vehicle tracking unit for controlling operable vehicle devices using a vehicle data bus and related methods |
US6340179B2 (en) | 2000-05-30 | 2002-01-22 | Robert E. Mitchell | Advertising materials and method for cooperative promotions |
US20020038233A1 (en) | 2000-06-09 | 2002-03-28 | Dmitry Shubov | System and method for matching professional service providers with consumers |
WO2002001508A1 (en) | 2000-06-23 | 2002-01-03 | Automated Car Rental, L.L.C. | System and method for the automated release of vehicles from a moter pool |
US20020111725A1 (en) | 2000-07-17 | 2002-08-15 | Burge John R. | Method and apparatus for risk-related use of vehicle communication system data |
US7904219B1 (en) | 2000-07-25 | 2011-03-08 | Htiip, Llc | Peripheral access devices and sensors for use with vehicle telematics devices and systems |
US7228211B1 (en) | 2000-07-25 | 2007-06-05 | Hti Ip, Llc | Telematics device for vehicles with an interface for multiple peripheral devices |
US6604033B1 (en) | 2000-07-25 | 2003-08-05 | Networkcar.Com | Wireless diagnostic system for characterizing a vehicle's exhaust emissions |
US6636790B1 (en) | 2000-07-25 | 2003-10-21 | Reynolds And Reynolds Holdings, Inc. | Wireless diagnostic system and method for monitoring vehicles |
US6957133B1 (en) | 2003-05-08 | 2005-10-18 | Reynolds & Reynolds Holdings, Inc. | Small-scale, integrated vehicle telematics device |
EP1182599A1 (en) | 2000-07-26 | 2002-02-27 | Transmedia Network, Inc. | System and method for providing consumer rewards |
US20020016655A1 (en) | 2000-08-01 | 2002-02-07 | Joao Raymond Anthony | Apparatus and method for processing and/or for providing vehicle information and/or vehicle maintenance information |
US20050240459A1 (en) | 2000-08-04 | 2005-10-27 | Cox Steve J | Virtual referral service |
MXPA02003523A (en) | 2000-08-07 | 2002-08-20 | Gen Electric | Computerized method and system for guiding service personnel to select a preferred work site for servicing transportation equipment. |
US6959327B1 (en) | 2000-08-29 | 2005-10-25 | International Business Machines Corporation | System and method for dispatching and scheduling network transmissions with feedback |
AU2001289056A1 (en) | 2000-09-11 | 2002-03-26 | Pinotage, Llc | System and method for obtaining and utilizing maintenance information |
US6909947B2 (en) | 2000-10-14 | 2005-06-21 | Motorola, Inc. | System and method for driver performance improvement |
JP2002149864A (en) * | 2000-11-14 | 2002-05-24 | Matsushita Electric Ind Co Ltd | Remote diagnostic system |
US20030233278A1 (en) | 2000-11-27 | 2003-12-18 | Marshall T. Thaddeus | Method and system for tracking and providing incentives for tasks and activities and other behavioral influences related to money, individuals, technology and other assets |
US20020082912A1 (en) | 2000-12-22 | 2002-06-27 | Leon Batachia | Transactions between vendors and customers using push/pull model |
US20020087522A1 (en) | 2000-12-29 | 2002-07-04 | Macgregor Robert | Method and apparatus for facilitating internet based sales transactions by local vendors |
US7219066B2 (en) | 2001-01-12 | 2007-05-15 | International Business Machines Corporation | Skills matching application |
US20020111897A1 (en) | 2001-01-12 | 2002-08-15 | Davis Richard L. | Web-based method and implementation for procurement of goods and services |
US6502030B2 (en) | 2001-01-25 | 2002-12-31 | Labarge, Inc. | Web based vehicle tracking and user on-board status system |
US6450411B1 (en) | 2001-02-02 | 2002-09-17 | Logis-Tech Corporation | Environmental stabilization system and method for maintenance and inventory |
US20020107873A1 (en) | 2001-02-07 | 2002-08-08 | Bandag Licensing Corporation | System and method for data collection, reporting, and analysis of fleet vehicle information |
US7627546B2 (en) | 2001-02-14 | 2009-12-01 | General Electric Railcar Services Corporation | Railcar condition inspection database |
US6801841B2 (en) | 2001-02-15 | 2004-10-05 | Joseph A. Tabe | Standard transportation excellent maintenance solutions |
US6768994B1 (en) | 2001-02-23 | 2004-07-27 | Trimble Navigation Limited | Web based data mining and location data reporting and system |
US7516103B1 (en) | 2001-03-09 | 2009-04-07 | Whitefence, Inc. | Method and apparatus for facilitating electronic acquisition and maintenance of goods and services via the internet |
US20020133374A1 (en) | 2001-03-13 | 2002-09-19 | Agoni Anthony Angelo | System and method for facilitating services |
US7523159B1 (en) | 2001-03-14 | 2009-04-21 | Hti, Ip, Llc | Systems, methods and devices for a telematics web services interface feature |
US6954689B2 (en) | 2001-03-16 | 2005-10-11 | Cnh America Llc | Method and apparatus for monitoring work vehicles |
US6609082B2 (en) | 2001-03-22 | 2003-08-19 | David S. Wagner | Machine control device |
US7715533B2 (en) | 2001-04-27 | 2010-05-11 | Hewlett-Packard Development Company, L.P. | Brokering of information acquisition by devices in a wireless network |
US6879894B1 (en) | 2001-04-30 | 2005-04-12 | Reynolds & Reynolds Holdings, Inc. | Internet-based emissions test for vehicles |
US6502303B2 (en) | 2001-05-07 | 2003-01-07 | Chromalloy Gas Turbine Corporation | Method of repairing a turbine blade tip |
WO2002093438A1 (en) | 2001-05-15 | 2002-11-21 | Akzo Nobel N.V. | Fleet servicing method |
US7343252B2 (en) | 2001-06-01 | 2008-03-11 | Scientronix Inc. | Method, system and apparatus for passively monitoring the maintenance and distribution of fluid products to heavy work vehicles |
US6609083B2 (en) | 2001-06-01 | 2003-08-19 | Hewlett-Packard Development Company, L.P. | Adaptive performance data measurement and collections |
US20030030550A1 (en) | 2001-06-08 | 2003-02-13 | Talbot Douglas C. | Child safety device for buses |
DE10130279B4 (en) | 2001-06-26 | 2005-04-21 | Btt Bahn Tank Transport Gmbh Deutsche Bahn Gruppe | Method for a computer-controlled transport management system with precalculation of the time behavior of product values |
IES20010666A2 (en) | 2001-07-17 | 2002-11-13 | Aircraft Man Technologies Ltd | An electronic operations and maintenance log and system for an aircraft |
JP2003044704A (en) | 2001-07-31 | 2003-02-14 | Honda Motor Co Ltd | Method for providing service |
US6594579B1 (en) | 2001-08-06 | 2003-07-15 | Networkcar | Internet-based method for determining a vehicle's fuel efficiency |
US6587768B2 (en) | 2001-08-08 | 2003-07-01 | Meritor Heavy Vehicle Technology, Llc | Vehicle inspection and maintenance system |
US6609051B2 (en) * | 2001-09-10 | 2003-08-19 | Daimlerchrysler Ag | Method and system for condition monitoring of vehicles |
US7117121B2 (en) | 2001-09-11 | 2006-10-03 | Zonar Compliance Systems, Llc | System and process to ensure performance of mandated inspections |
US7362229B2 (en) | 2001-09-11 | 2008-04-22 | Zonar Compliance Systems, Llc | Ensuring the performance of mandated inspections combined with the collection of ancillary data |
US6671646B2 (en) | 2001-09-11 | 2003-12-30 | Zonar Compliance Systems, Llc | System and process to ensure performance of mandated safety and maintenance inspections |
US6880390B2 (en) | 2001-11-07 | 2005-04-19 | Bell Sea Marine Systems | Fuel meter for outboard engines |
US6873909B2 (en) * | 2001-11-19 | 2005-03-29 | Volvo Trucks North America, Inc. | System for preventing unauthorized trailer uncoupling |
US7174243B1 (en) | 2001-12-06 | 2007-02-06 | Hti Ip, Llc | Wireless, internet-based system for transmitting and analyzing GPS data |
US6614392B2 (en) | 2001-12-07 | 2003-09-02 | Delaware Capital Formation, Inc. | Combination RFID and GPS functionality on intelligent label |
JP3719659B2 (en) | 2001-12-26 | 2005-11-24 | 株式会社日立製作所 | Information receiving system and information receiving terminal |
WO2003077073A2 (en) | 2002-03-08 | 2003-09-18 | Fleettrakker, L.L.C. | Equipment tracking system and method |
US6529808B1 (en) | 2002-04-22 | 2003-03-04 | Delphi Technologies, Inc. | Method and system for analyzing an on-board vehicle computer system |
US7447968B2 (en) | 2002-04-24 | 2008-11-04 | Samsung Electronics, Co., Ltd. | Apparatus and method for supporting automatic repeat request in a high-speed wireless packet data communication system |
US6894617B2 (en) | 2002-05-04 | 2005-05-17 | Richman Technology Corporation | Human guard enhancing multiple site integrated security system |
JP2004044779A (en) | 2002-05-21 | 2004-02-12 | Aisin Seiki Co Ltd | Drive device |
AU2003241595A1 (en) | 2002-05-24 | 2003-12-12 | Paul A. Levine | Employee recruiting systems and methods |
US6946953B2 (en) | 2002-05-30 | 2005-09-20 | Vehicle Enhancement Systems, Inc. | Apparatus and method for enhanced data communications and control between a vehicle and a remote data communications terminal |
US8035508B2 (en) | 2002-06-11 | 2011-10-11 | Intelligent Technologies International, Inc. | Monitoring using cellular phones |
US6968259B2 (en) | 2002-06-28 | 2005-11-22 | Oem Controls | Monitoring and annunciation device for equipment maintenance |
US20040049450A1 (en) | 2002-09-04 | 2004-03-11 | Lussler Sherin B. | Method and apparatus for coordinating real estate closing services |
JP2004118370A (en) | 2002-09-25 | 2004-04-15 | Hitachi Ltd | Vehicle information collection system and method |
CA2408979A1 (en) | 2002-10-18 | 2004-04-18 | Richard Egon Schauble | Tamper-evident use-indicating odometer and engine-timer |
US8027843B2 (en) | 2002-11-07 | 2011-09-27 | International Business Machines Corporation | On-demand supplemental diagnostic and service resource planning for mobile systems |
US6631322B1 (en) | 2002-12-06 | 2003-10-07 | General Electric Co. | Method and apparatus for vehicle management |
US8538611B2 (en) * | 2003-01-06 | 2013-09-17 | General Electric Company | Multi-level railway operations optimization system and method |
US8225194B2 (en) * | 2003-01-09 | 2012-07-17 | Kaleidescape, Inc. | Bookmarks and watchpoints for selection and presentation of media streams |
US7604169B2 (en) | 2003-01-21 | 2009-10-20 | Pump-On Llc | Methods and systems for customer validation using any of a plurality of identification documents and identification document readers |
US20040236596A1 (en) | 2003-02-27 | 2004-11-25 | Mahesh Chowdhary | Business method for a vehicle safety management system |
US20040199412A1 (en) | 2003-03-14 | 2004-10-07 | Mccauley Stephen F. | Internet-based scheduling method and system for service providers and users |
US7421334B2 (en) * | 2003-04-07 | 2008-09-02 | Zoom Information Systems | Centralized facility and intelligent on-board vehicle platform for collecting, analyzing and distributing information relating to transportation infrastructure and conditions |
DE10323384A1 (en) * | 2003-05-23 | 2004-12-16 | Daimlerchrysler Ag | diagnostic system |
US20040243464A1 (en) | 2003-05-29 | 2004-12-02 | Bridgetree, Inc. | Sponsored promotions method |
US7113127B1 (en) | 2003-07-24 | 2006-09-26 | Reynolds And Reynolds Holdings, Inc. | Wireless vehicle-monitoring system operating on both terrestrial and satellite networks |
US20050038688A1 (en) | 2003-08-15 | 2005-02-17 | Collins Albert E. | System and method for matching local buyers and sellers for the provision of community based services |
US7142099B2 (en) | 2003-09-03 | 2006-11-28 | General Motors Corporation | Method and system for providing flexible vehicle communication within a vehicle communications system |
US20050065853A1 (en) | 2003-09-18 | 2005-03-24 | Philip Ferreira | Reverse auction system and method |
US6955302B2 (en) | 2003-11-13 | 2005-10-18 | York International Corporation | Remote monitoring diagnostics |
JP3963181B2 (en) | 2003-12-03 | 2007-08-22 | トヨタ自動車株式会社 | Vehicle fault diagnosis system |
DE10360125A1 (en) | 2003-12-20 | 2005-07-21 | Daimlerchrysler Ag | Data loggin in a motor vehicle |
US20050228707A1 (en) | 2003-12-23 | 2005-10-13 | Robert Hendrickson | Method for real-time allocation of customer service resources and opportunities for optimizing business and financial benefit |
DE10361628A1 (en) | 2003-12-27 | 2005-07-21 | Robert Bosch Gmbh | Commissioning an application in a mobile client |
US7412313B2 (en) | 2004-01-07 | 2008-08-12 | Temic Automotive Of North America, Inc. | Maintenance assistance for a vehicle |
US20050222756A1 (en) | 2004-04-05 | 2005-10-06 | Davis Scott B | Methods for displaying a route traveled by mobile users in a communication network |
US7680594B2 (en) | 2004-04-06 | 2010-03-16 | Honda Motor Co., Ltd. | Display method and system for a vehicle navigation system |
EP1733513A4 (en) | 2004-04-06 | 2009-05-06 | Honda Motor Co Ltd | Method and system for controlling the exchange of vehicle related messages |
US7225065B1 (en) | 2004-04-26 | 2007-05-29 | Hti Ip, Llc | In-vehicle wiring harness with multiple adaptors for an on-board diagnostic connector |
US20050273250A1 (en) | 2004-05-18 | 2005-12-08 | Bruce Hamilton | System and method for dynamic navigational route selection |
CA2508586A1 (en) | 2004-05-28 | 2005-11-28 | Infinian Corporation | Service provider system and method for marketing programs |
US6899151B1 (en) | 2004-06-07 | 2005-05-31 | Delaware Capital Formation, Inc. | Lighted supervisory system for a fuel dispensing nozzle |
US7877176B2 (en) * | 2004-06-24 | 2011-01-25 | General Motors Llc | Method and system for remote telltale reset |
US20070203769A1 (en) | 2005-10-14 | 2007-08-30 | Thomas Tracey R | Method of selecting and matching professionals |
US7912630B2 (en) * | 2004-12-14 | 2011-03-22 | International Business Machines Corporation | Method and system for performing programmatic actions based upon vehicle approximate locations |
US7254516B2 (en) | 2004-12-17 | 2007-08-07 | Nike, Inc. | Multi-sensor monitoring of athletic performance |
EP1852680A4 (en) | 2005-01-19 | 2012-09-19 | Jvc Kenwood Corp | Guiding route generation device and guiding route generation method |
US20060184381A1 (en) | 2005-01-27 | 2006-08-17 | Servicemagic, Inc. | Computer-implemented method and system for matching a consumer to a home service provider |
US7774223B2 (en) | 2005-02-28 | 2010-08-10 | Nick Karabetsos | System and method for scheduling location-specific services |
US20060232406A1 (en) | 2005-04-13 | 2006-10-19 | American Research And Technology | Use of rf-id tags for tracking a person carrying a portable rf-id tag reader |
US20060255967A1 (en) | 2005-04-22 | 2006-11-16 | Woo Henry S Y | Open road vehicle emissions inspection |
US20060282364A1 (en) | 2005-06-13 | 2006-12-14 | Berg David A | Communication system for electrical maintenance management of different facilities and method therefor |
US9117319B2 (en) | 2005-06-30 | 2015-08-25 | Innova Electronics, Inc. | Handheld automotive diagnostic tool with VIN decoder and communication system |
KR20070006134A (en) | 2005-07-07 | 2007-01-11 | 현대자동차주식회사 | Telematics terminal for high availability |
US7729977B2 (en) | 2005-08-17 | 2010-06-01 | Quan Xiao | Method and system for grouping merchandise, services and users and for trading merchandise and services |
US20070050193A1 (en) | 2005-08-24 | 2007-03-01 | Larson Gerald L | Fuel use categorization for fuel tax reporting on commercial vehicles |
DE112006002329B4 (en) | 2005-08-29 | 2022-06-09 | Midtronics, Inc. | Diagnostic device for automotive electrical systems |
WO2007033311A2 (en) | 2005-09-14 | 2007-03-22 | Wobb R W | Reverse auctioning system for automobile repair services |
JP2007102336A (en) | 2005-09-30 | 2007-04-19 | Car Bid Japan:Kk | System and method for automobile repair auction |
US20100010705A1 (en) | 2005-10-20 | 2010-01-14 | Airmax Group Plc | Methods and apparatus for monitoring vehicle data |
US7844500B2 (en) | 2005-11-18 | 2010-11-30 | Manhattan Bridge Capital, Inc. | Method for matching vendors with consumers |
US20070124283A1 (en) | 2005-11-28 | 2007-05-31 | Gotts John W | Search engine with community feedback system |
US8024114B2 (en) | 2006-02-01 | 2011-09-20 | Qualcomm Incorporated | Navigation data quality feedback |
US8006677B2 (en) | 2006-02-02 | 2011-08-30 | Immixt, LLC | Fuel control system and associated method |
US7778882B2 (en) | 2006-03-03 | 2010-08-17 | Mukesh Chatter | Method, system and apparatus for automatic real-time iterative commercial transactions over the internet in a multiple-buyer, multiple-seller marketplace, optimizing both buyer and seller needs based upon the dynamics of market conditions |
US20070244797A1 (en) | 2006-03-22 | 2007-10-18 | Hinson W Bryant | Computer network-implemented system and method for vehicle transactions |
US20070244800A1 (en) | 2006-03-30 | 2007-10-18 | Habin Lee | Work allocation system |
US7388518B2 (en) | 2006-05-09 | 2008-06-17 | Fleetmatics Patents Limited | Vehicle tracking system |
US20080040129A1 (en) | 2006-08-08 | 2008-02-14 | Capital One Financial Corporation | Systems and methods for providing a vehicle service management service |
US8630765B2 (en) | 2006-11-17 | 2014-01-14 | Innova Electronics, Inc. | OBD II-compliant diagnostic PC tablet and method of use |
US8050811B2 (en) | 2006-12-12 | 2011-11-01 | General Motors Llc | Method for controlling the distribution of vehicle-related data |
CA3004236C (en) | 2006-12-13 | 2019-11-05 | Crown Equipment Corporation | Fleet management system |
US8694328B1 (en) | 2006-12-14 | 2014-04-08 | Joseph Gormley | Vehicle customization and personalization activities |
US20080177653A1 (en) | 2007-01-22 | 2008-07-24 | David Famolari | System and method for enabling service providers to create real-time reverse auctions for location based services |
US20080189199A1 (en) | 2007-02-02 | 2008-08-07 | Ashantiplc, Ltd. | On-line trading of prospective customer leads |
US9792632B2 (en) | 2007-02-23 | 2017-10-17 | Epona Llc | System and method for processing vehicle transactions |
JP2008217341A (en) | 2007-03-02 | 2008-09-18 | Car Life Net Co Ltd | Estimate presentation method |
US20080228619A1 (en) | 2007-03-15 | 2008-09-18 | Locker Howard J | Apparatus, system, and method for allocating service requests |
US8355870B2 (en) | 2007-05-03 | 2013-01-15 | Hti Ip, Llc | Methods, systems, and apparatuses for telematics navigation |
US7900094B2 (en) | 2007-05-14 | 2011-03-01 | International Business Machines Corporation | Method, system and computer program for facilitating the analysis of error messages |
US20080294556A1 (en) | 2007-05-24 | 2008-11-27 | Jim Anderson | Mobile commerce service |
US9747729B2 (en) | 2007-05-31 | 2017-08-29 | Verizon Telematics Inc. | Methods, systems, and apparatuses for consumer telematics |
WO2009029891A1 (en) | 2007-08-29 | 2009-03-05 | Driverside Inc. | Automotive diagnostic and estimate system and method |
US7580808B2 (en) | 2007-09-11 | 2009-08-25 | Gm Global Technology Operations, Inc. | Onboard trip computer for emissions subject to reduction credits |
KR100987319B1 (en) | 2007-09-20 | 2010-10-13 | 성균관대학교산학협력단 | Active Database based Total Management System and Method for Diagnostic Information and Positioning Information of Vehicle |
US8892455B2 (en) | 2007-09-28 | 2014-11-18 | Walk Score Management, LLC | Systems, techniques, and methods for providing location assessments |
US8099308B2 (en) | 2007-10-02 | 2012-01-17 | Honda Motor Co., Ltd. | Method and system for vehicle service appointments based on diagnostic trouble codes |
US9014910B2 (en) | 2007-12-07 | 2015-04-21 | General Motors Llc | Method and system for providing vehicle data to third party authorized recipients |
KR20090063024A (en) | 2007-12-13 | 2009-06-17 | 현대자동차주식회사 | System and method for booking garage according to error code |
US9026304B2 (en) | 2008-04-07 | 2015-05-05 | United Parcel Service Of America, Inc. | Vehicle maintenance systems and methods |
EP2116968A1 (en) | 2008-05-06 | 2009-11-11 | Airmax Remote Limited | Method and apparatus for rating how a vehicle is driven |
US8050855B2 (en) * | 2008-08-07 | 2011-11-01 | General Motors Llc | Method and system for transmitting data to a traffic information server |
US20100257104A1 (en) | 2008-08-14 | 2010-10-07 | Reza Bundy | Method and apparatus for repair procedure |
KR20100023434A (en) | 2008-08-22 | 2010-03-04 | 엘지전자 주식회사 | Telematics device and method for providing car error service thereof |
US20100106534A1 (en) | 2008-10-24 | 2010-04-29 | Solid People Llc | Certification and risk-management system and method for a rental agreement |
US8060274B2 (en) | 2008-10-30 | 2011-11-15 | International Business Machines Corporation | Location-based vehicle maintenance scheduling |
US8438072B2 (en) | 2009-02-20 | 2013-05-07 | Consumercartel, Llc | Online exchange system and method with reverse auction |
US20110012720A1 (en) | 2009-07-15 | 2011-01-20 | Hirschfeld Robert A | Integration of Vehicle On-Board Diagnostics and Smart Phone Sensors |
US20110225096A1 (en) | 2010-03-15 | 2011-09-15 | Hanbum Cho | Method And System For Providing Diagnostic Feedback Based On Diagnostic Data |
US20110302046A1 (en) | 2010-06-04 | 2011-12-08 | Afshin Arian | Professional services website |
US10600096B2 (en) | 2010-11-30 | 2020-03-24 | Zonar Systems, Inc. | System and method for obtaining competitive pricing for vehicle services |
US10665040B2 (en) | 2010-08-27 | 2020-05-26 | Zonar Systems, Inc. | Method and apparatus for remote vehicle diagnosis |
US20120136802A1 (en) | 2010-11-30 | 2012-05-31 | Zonar Systems, Inc. | System and method for vehicle maintenance including remote diagnosis and reverse auction for identified repairs |
US20120136743A1 (en) | 2010-11-30 | 2012-05-31 | Zonar Systems, Inc. | System and method for obtaining competitive pricing for vehicle services |
US20200043068A1 (en) | 2010-11-30 | 2020-02-06 | Zonar Systems, Inc. | System and method for obtaining competitive pricing for vehicle services |
-
2011
- 2011-08-26 US US13/219,467 patent/US10665040B2/en active Active
-
2016
- 2016-08-08 US US15/231,160 patent/US20160343177A1/en not_active Abandoned
- 2016-08-08 US US15/231,177 patent/US20160350985A1/en not_active Abandoned
- 2016-08-08 US US15/231,142 patent/US11080950B2/en active Active
-
2020
- 2020-04-30 US US16/863,735 patent/US11978291B2/en active Active
- 2020-10-26 US US17/080,502 patent/US20210074088A1/en active Pending
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5974483A (en) * | 1997-05-21 | 1999-10-26 | Microsoft Corporation | Multiple transparent access to in put peripherals |
US6438472B1 (en) * | 1998-09-12 | 2002-08-20 | Data Tec. Co., Ltd. | Operation control system capable of analyzing driving tendency and its constituent apparatus |
US20020177926A1 (en) * | 2000-10-06 | 2002-11-28 | Lockwood Robert Farrell | Customer service automation systems and methods |
US20020133273A1 (en) * | 2001-03-14 | 2002-09-19 | Lowrey Larkin Hill | Internet-based vehicle-diagnostic system |
US20060089767A1 (en) * | 2004-10-25 | 2006-04-27 | Sowa Michael A | Vehicles fault diagnostic systems and methods |
US20070241874A1 (en) * | 2006-04-17 | 2007-10-18 | Okpysh Stephen L | Braking intensity light |
US7953530B1 (en) * | 2006-06-08 | 2011-05-31 | Pederson Neal R | Vehicle diagnostic tool |
US20080049123A1 (en) * | 2006-08-25 | 2008-02-28 | Sportvision, Inc. | Video effect using movement within an image |
US20080167758A1 (en) * | 2007-01-08 | 2008-07-10 | Ford Global Technologies, Llc | Wireless Gateway Apparatus and Method of Bridging Data Between Vehicle Based and External Data Networks |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10665040B2 (en) | 2010-08-27 | 2020-05-26 | Zonar Systems, Inc. | Method and apparatus for remote vehicle diagnosis |
US11978291B2 (en) | 2010-08-27 | 2024-05-07 | Zonar Systems, Inc. | Method and apparatus for remote vehicle diagnosis |
US11080950B2 (en) | 2010-08-27 | 2021-08-03 | Zonar Systems, Inc. | Cooperative vehicle diagnosis system |
US10600096B2 (en) | 2010-11-30 | 2020-03-24 | Zonar Systems, Inc. | System and method for obtaining competitive pricing for vehicle services |
US20170339056A1 (en) * | 2014-12-10 | 2017-11-23 | Toyota Jidosha Kabushiki Kaisha | Remote vehicle data collection system |
US11632384B2 (en) | 2016-12-06 | 2023-04-18 | Panasonic Intellectual Property Corporation Of America | Information processing device and information processing method |
US20190141072A1 (en) * | 2016-12-06 | 2019-05-09 | Panasonic Intellectual Property Corporation Of America | Information processing device and information processing method |
US10893063B2 (en) * | 2016-12-06 | 2021-01-12 | Panasonic Intellectual Property Corporation Of America | Information processing device and information processing method |
EP3771981A4 (en) * | 2018-04-06 | 2021-04-14 | Panasonic Intellectual Property Corporation of America | Log output method, log output device, and program |
US11838303B2 (en) | 2018-04-06 | 2023-12-05 | Panasonic Intellectual Property Corporation Of America | Log generation method, log generation device, and recording medium |
CN110933021A (en) * | 2018-09-19 | 2020-03-27 | 罗伯特·博世有限公司 | Method and device for abnormality detection in a vehicle |
US11277299B2 (en) * | 2018-09-19 | 2022-03-15 | Robert Bosch Gmbh | Method and device for anomaly detection in a vehicle |
US10872479B1 (en) | 2019-11-04 | 2020-12-22 | Ford Global Technologies, Llc | Secure log capture |
US11915203B2 (en) | 2019-11-20 | 2024-02-27 | Polaris Industries Inc. | Vehicle service scheduling |
Also Published As
Publication number | Publication date |
---|---|
US10665040B2 (en) | 2020-05-26 |
US20160343177A1 (en) | 2016-11-24 |
US20200258323A1 (en) | 2020-08-13 |
US11978291B2 (en) | 2024-05-07 |
US20160342456A1 (en) | 2016-11-24 |
US20120053778A1 (en) | 2012-03-01 |
US11080950B2 (en) | 2021-08-03 |
US20210074088A1 (en) | 2021-03-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210074088A1 (en) | Cooperative vehicle disgnosis system | |
US6745151B2 (en) | Remote diagnostics and prognostics methods for complex systems | |
US8543280B2 (en) | Collaborative multi-agent vehicle fault diagnostic system and associated methodology | |
JP6310332B2 (en) | Vehicle diagnostic machine and vehicle diagnostic method | |
CA2838632C (en) | Method and apparatus for translating vehicle diagnostic trouble codes | |
US9858733B2 (en) | Vehicle diagnostic data collecting apparatus, vehicle diagnostic data collecting method, vehicle diagnostic machine, and vehicle diagnosing method | |
US20160071338A1 (en) | Diagnostic unit and method | |
US20170161965A1 (en) | Distributed vehicle health management systems | |
WO2012027733A1 (en) | Method and apparatus for remote vehicle diagnosis | |
US20080236141A1 (en) | Method and system for automatically inspecting and registering automotive exhaust emission data | |
US20080291014A1 (en) | System and method for remote diagnosis and repair of a plant malfunction with software agents | |
KR101586051B1 (en) | Apparatus and method for providing vehicle data for testing product | |
CN105278521A (en) | Method and device for diagnosing fault cause of unit and air conditioning unit | |
KR102255599B1 (en) | System and method for providing vehicle diagnosis service | |
JP6310331B2 (en) | Data collection apparatus and data collection method for vehicle diagnosis | |
JP2007248070A (en) | Vehicle running test device | |
US20080161994A1 (en) | Method and system for autogenerating static fault code data based on a unified summary table for heavy duty diesel engines | |
CN106882162B (en) | Vehicle maintenance device and system | |
JP4315073B2 (en) | Failure analysis system | |
US7873450B2 (en) | System and method for an integrated interface for systems associated with locomotive operation | |
KR102242227B1 (en) | System and method for providing vehicle diagnosis information using vehicle gateway device | |
EP4379681A1 (en) | Method for detecting, predicting and preventing occurrence of failures and continuity control of vehicles, system performing said method and the device used in said system | |
CN115497289A (en) | Vehicle monitoring processing method and device | |
KR20210106852A (en) | Real-time integrated vehicles management system using wireless Internet network(LET) and method thereof | |
CN111899375A (en) | Portable data recording device, method for recording vehicle data and corresponding vehicle |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |