Patent Grant
11887413
Most vehicles are serviced at least once during their useful life. In many instances, a vehicle is serviced at a facility with professional mechanics (e.g., technicians). The technicians can use any of a variety of non-computerized hand tools to service (e.g., repair) any of the wide variety of mechanical components on a vehicle. While servicing a vehicle, a technician sometimes needs information for diagnosing and/or repairing the vehicle, and for post-repair activities performed to the repaired vehicle. Such technician may use a vehicle information system that provides parameter identifier (PID) values. With hundreds of PIDs being available for each of hundreds of different types of vehicles, the technician may not know which PIDs are applicable or helpful for diagnosing a particular symptom for a particular vehicle. This may lead to a technician guessing which PIDs should be requested to diagnose the symptom. If the technician guesses incorrectly, the technician may not see PID values that would lead to a quicker and more accurate diagnosis of the symptom. In that situation or in another situation, the technician does not have the ability to obtain a filtered list of PID values based on repair order data, past user selection of PID values and/or anomalous PID values.
Several example embodiments that relate to diagnostic lists, such as a PID filter list, a component test filter list, a functional test filter list, and/or a reset procedure filter list are described herein. Some example embodiments relate to displaying PIDs based on a PID filter list.
Viewed from one aspect, an example embodiment takes the form of a method comprising determining, by a display device, identifying information for a vehicle to be serviced. The method further includes receiving, at the display device, at least one symptom identifier for the vehicle. The method additionally includes sending, by the display device, a request over a communication network to a remote server for a PID filter list for the vehicle, the request comprising the identifying information for the vehicle and the at least one symptom identifier for the vehicle. The method also includes receiving, at the display device, a response to the request over the communication network from the remote server, the response comprising the PID filter list for the vehicle. The method further includes determining, by the display device based on the PID filter list for the vehicle, a symptom-based subset of PIDs for the vehicle from a set of available PIDs. The method additionally includes displaying, by the display device on a display interface, the symptom-based subset of PIDs for the vehicle.
Viewed from another aspect, an example embodiment takes the form of a display device comprising a display interface, one or more processors, a non-transitory computer readable medium, and program instructions stored on the non-transitory computer readable medium. The program instructions may be executable by the one or more processors to determine identifying information for a vehicle to be serviced. The program instructions may be further executable by the one or more processors to receive at least one symptom identifier for the vehicle. The program instructions may additionally be executable by the one or more processors to send a request over a communication network to a remote server for a PID filter list for the vehicle, the request comprising the identifying information for the vehicle and the at least one symptom identifier for the vehicle. The program instructions may also be executable by the one or more processors to receive a response to the request over the communication network from the remote server, the response comprising the PID filter list. The program instructions may be further executable by the one or more processors to determine, based on the PID filter list for the vehicle, a symptom-based subset of PIDs for the vehicle from a set of available PIDs. The program instructions may additionally be executable by the one or more processors display, on the display interface, the symptom-based subset of PIDs for the vehicle.
Viewed from yet another aspect, an example embodiment takes the form of a non-transitory computer readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions. The functions include determining identifying information for a vehicle to be serviced. The functions further include receiving at least one symptom identifier for the vehicle. The functions additionally include sending a request over a communication network to a remote server for a PID filter list for the vehicle, the request comprising the identifying information for the vehicle and the at least one symptom identifier for the vehicle. The functions also include receiving a response to the request over the communication network from the remote server, the response comprising the PID filter list for the vehicle. The functions further include determining, based on the PID filter list for the vehicle, a symptom-based subset of PIDs for the vehicle from a set of available PIDs. The functions additionally include displaying, on the display interface, the symptom-based subset of PIDs for the vehicle.
These as well as other aspects and advantages will become apparent to those of ordinary skill in the art by reading the following detailed description, with reference where appropriate to the accompanying drawings. Further, it should be understood that the embodiments described in this overview and elsewhere are intended to be examples only and do not necessarily limit the scope of the invention.
Example embodiments are described herein with reference to the drawings.
This description describes several example embodiments, at least some which pertain to determining a diagnostic list and/or providing the diagnostic list to a display device configured to display the diagnostic list. The diagnostic list can comprise a diagnostic filter list. The diagnostic filter list can comprise a PID filter list, a component test filter list, a functional test filter list, and/or a reset procedure filter list. The display device is operable to display the diagnostic list. A diagnostic filter list can be applicable to a set of vehicles and a symptom exhibited by a vehicle within the set of vehicles. A diagnostic filter list can be based on other criteria as well. In the foregoing examples, the diagnostic filter list is contextually relevant to the set of vehicles, symptom, and/or other criteria. The display device can be connected to the vehicle exhibiting the symptom in order to display PID data values from the vehicle for PIDs that the server has determined to be most applicable to the set of vehicles and the symptom. The display device may also display component tests, functional tests, and/or reset procedures that the server has determined to be most applicable to the set of vehicles and the symptom. The display device may then cause selected component tests, functional tests, and/or reset procedures to be performed on the vehicle.
The communication network 3 can comprise the communication links 5, 6, and 7 as well as other communication links (not shown). The communication network 3 and the communication links 5, 6, and 7 can include various network components such as switches, modems, gateways, antennas, cables, transmitters, and/or receivers. The communication network 3 can comprise a wide area network (WAN). The WAN can carry data using packet-switched and/or circuit-switched technologies. The WAN can include an air interface or wire to carry the data. The communication network 3 can comprise a network or at least a portion of a network that carries out communications using a Transmission Control Protocol (TCP) and the Internet Protocol (IP), such as the communication network commonly referred to as the Internet.
The repair shop 8 can comprise a variety of shop tools, such as brake lathes, wheel alignment machines, wheel balancers, and/or diagnostic devices for diagnosing vehicles. A shop tool can comprise the display device 4. As shown in
A vehicle, such as vehicle 9, is a mobile machine that can be used to transport a person, people, or cargo. As an example, any vehicle discussed herein can be driven and/or otherwise guided along a path (e.g., a paved road or otherwise) on land, in water, or in the air or outer space. As another example, any vehicle discussed herein can be wheeled, tracked, railed, or skied. As yet another example, any vehicle discussed herein can include an automobile, a motorcycle, an all-terrain vehicle (ATV) defined by ANSI/SVIA-1-2007, a snowmobile, a personal watercraft (e.g., a JET SKI® personal watercraft), a light-duty truck, a medium-duty truck, a heavy-duty truck, a semi-tractor, or a farm machine. As an example, a vehicle guided along a path can include a van (such as a dry or refrigerated van), a tank trailer, a platform trailer, or an automobile carrier. As still yet another example, any vehicle discussed herein can include or use any appropriate voltage or current source, such as a battery, an alternator, a fuel cell, and the like, providing any appropriate current or voltage, such as about 12 volts, about 42 volts, and the like. As still yet another example, any vehicle discussed herein can include or use any desired system or engine. Those systems or engines can include items that use fossil fuels, such as gasoline, natural gas, propane, and the like, electricity, such as that generated by a battery, magneto, fuel cell, solar cell and the like, wind and hybrids or combinations thereof. As still yet another example, any vehicle discussed herein can include an ECU, a data link connector (DLC), and a vehicle communication link that connects the DLC to the ECU.
A vehicle manufacturer can build various quantities of vehicles each calendar year (i.e., January 1st to December 31st). In some instances, a vehicle manufacturer defines a model year for a particular vehicle model to be built. The model year can start on a date other than January 1st and/or can end on a date other than December 31st. The model year can span portions of two calendar years. A vehicle manufacturer can build one vehicle model or multiple different vehicle models. Two or more different vehicle models built by a vehicle manufacturer during a particular calendar year can have the same of different defined model years. The vehicle manufacturer can build vehicles of a particular vehicle model with different vehicle options. For example, the particular vehicle model can include vehicles with six-cylinder engines and vehicles with eight-cylinder engines. The vehicle manufacturer or another entity can define vehicle identifying information for each vehicle built by the vehicle manufacturer. Particular vehicle identifying information identifies particular sets of vehicles (e.g., all vehicles of a particular vehicle model for a particular vehicle model year or all vehicles of a particular vehicle model for a particular vehicle model year with a particular set of one or more vehicle options).
As an example, the particular vehicle identifying information can comprise indicators of characteristics of the vehicle such as when the vehicle was built (e.g., a vehicle model year), who built the vehicle (e.g., a vehicle make (i.e., vehicle manufacturer)), marketing names associated with vehicle (e.g., a vehicle model name, or more simply “model”), and features of the vehicle (e.g., an engine type). In accordance with that example, the particular vehicle identifying information can be referred to by an abbreviation YMME or Y/M/M/E, where each letter in the order shown represents a model year identifier, vehicle make identifier, vehicle model name identifier, and engine type identifier, respectively, or an abbreviation YMM or Y/M/M, where each letter in the order shown represents a model year identifier, vehicle make identifier, and vehicle model name identifier, respectively. An example Y/M/M/E is 2004/Toyota/Camry/4 Cyl, in which “2004” represents the model year the vehicle was built, “Toyota” represents the name of the vehicle manufacturer Toyota Motor Corporation, Aichi Japan, “Camry” represents a vehicle model built by that manufacturer, and “4 Cyl” represents a an engine type (i.e., a four cylinder internal combustion engine) within the vehicle. A person skilled in the art will understand that other features in addition to or as an alternative to “engine type” can be used to identify a vehicle using particular vehicle identifying information. These other features can be identified in various manners, such as a regular production option (RPO) code, such as the RPO codes defined by the General Motors Company LLC, Detroit Michigan.
A vehicle communication link within a vehicle can include one or more conductors (e.g., copper wire conductors) or can be wireless. As an example, a vehicle communication link can include one or two conductors for carrying vehicle data messages in accordance with a vehicle data message (VDM) protocol. A VDM protocol can include a Society of Automotive Engineers (SAE) J1850 (PWM or VPW) VDM protocol, an International Organization of Standardization (ISO) 15764-4 controller area network (CAN) VDM protocol, an ISO 9141-2 K-Line VDM protocol, an ISO 14230-4 KWP2000 K-Line VDM protocol, or some other protocol presently defined for performing communications within a vehicle.
An ECU can control various aspects of vehicle operation or components within a vehicle. For example, the ECU can include a powertrain (PT) system ECU, an engine control module (ECM) ECU, a supplemental inflatable restraint (SIR) system (i.e., an air bag system) ECU, an entertainment system ECU, or some other ECU. The ECU can receive inputs (e.g., a sensor input), control output devices (e.g., a solenoid), generate a vehicle data message (VDM) (such as a VDM based on a received input or a controlled output), and set a diagnostic trouble code (DTC) as being active or history for a detected fault or failure condition within a vehicle. Performance of a functional test can or a reset procedure with respect to an ECU can comprise the display device 4 transmitting a VDM to a vehicle. A VDM received at an ECU can comprise a PID request. A VDM transmitted by an ECU can comprise a response comprising the PID and a PID data value for the PID.
Next,
Next,
Next,
Display device 4 may transmit the vehicle identifying information 26 and the one or more symptom identifiers 27 to server 2. Server 2 may process the vehicle identifying information 26 and the one or more symptom identifiers 27 in order to determine one or more contextually relevant diagnostic filter lists to provide back to display device 4. In particular, server 2 may provide any combination of PID filter list 182, functional test filter list 184, reset procedure filter list 186, and component test filter list 188.
PID filter list 182 may indicate contextually relevant PIDs for the vehicle 9 with vehicle identifying information 26 and symptoms corresponding to the one or more symptom identifiers 27. Functional test filter list 184 may indicate contextually relevant functional tests for the vehicle 9 with vehicle identifying information 26 and symptoms corresponding to the one or more symptom identifiers 27. Reset procedure filter list 186 may indicate contextually relevant reset procedures for the vehicle 9 with vehicle identifying information 26 and symptoms corresponding to the one or more symptom identifiers 27. Component test filter list 188 may indicate contextually relevant component tests for the vehicle 9 with vehicle identifying information 26 and symptoms corresponding to the one or more symptom identifiers 27.
After receiving one or more diagnostic filter lists from server 2, display device 4 may use the one or more diagnostic filter lists to determine and display contextually relevant subsets of data or information to a technician. In particular, display device 4 may display a symptom-based subset of PIDs, a symptom-based subset of functional tests, a symptom-based subset of reset procedures, and/or a symptom-based subset of component tests.
Next,
The DLC 34 can comprise a connector such as an OBD I connector, an OBD II connector, or some other connector. An OBD II connector can include slots for retaining up to sixteen connector terminals, but can include a different number of slots or no slots at all. As an example, a DLC connector can include an OBD II connector that meets the SAE J1962 specification such as a connector 16M, part number 12110252, available from Delphi Automotive LLP of Troy, Michigan. The DLC 34 can include conductor terminals that connect to a conductor in a vehicle. For instance, the DLC 34 can include connector terminals that connect to conductors that respectively connect to positive and negative terminals of a vehicle battery. The DLC 34 can include one or more conductor terminals that connect to a conductor of the vehicle communication link such that the DLC 34 is communicatively connected to the ECU within the vehicle 9.
Next,
A processor such as the processor 50 or any other processor discussed in this description can comprise one or more processors. A processor can include a general purpose processor (e.g., an INTEL® single core microprocessor or an INTEL® multicore microprocessor), or a special purpose processor (e.g., a digital signal processor, a graphics processor, or an application specific integrated circuit (ASIC) processor). A processor can be configured to execute computer-readable program instructions (CRPI). For example, the processor 50 can execute CRPI 60 stored in the memory 52. A processor can be configured to execute hard-coded functionality in addition to or as an alternative to software-coded functionality (e.g., via CRPI). The at least one processor of the processor 50 can be programmed to perform any function or combination of functions described herein as being performed by the server 2.
A memory such as the memory 52 or any other memory discussed in this description can include one or more memories. A memory can comprise a non-transitory memory, a transitory memory, or both a non-transitory memory and a transitory memory. A non-transitory memory, or a portion thereof, can be located within or as part of a processor (e.g., within a single integrated circuit chip). A non-transitory memory, or a portion thereof, can be separate and distinct from a processor.
A non-transitory memory can include a volatile or non-volatile storage component, such as an optical, magnetic, organic or other memory or disc storage component. Additionally or alternatively, a non-transitory memory can include or be configured as a random-access memory (RAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a compact disk read-only memory (CD-ROM). The RAM can include static RAM or dynamic RAM.
A transitory memory can include, for example, CRPI provided over a communication link, such as a communication link which is connected to or is part of the communication network 3. The communication link can include a digital or analog communication link. The communication link can include a wired communication link including one or more wires or conductors, or a wireless communication link including an air interface.
A “memory” can be referred to by other terms such as a “computer-readable memory,” a “computer-readable medium,” a “computer-readable storage medium,” a “data storage device,” a “memory device,” “computer-readable media,” a “computer-readable database,” “at least one computer-readable medium,” or “one or more computer-readable medium.” Any of those alternative terms can be preceded by the prefix “transitory” if the memory is transitory or “non-transitory” if the memory is non-transitory.
The memory 52 stores computer-readable data, such as the CRPI 60, an index 61, mapping data 62, RO data 63, diagnostic session data (DSD) 64, a diagnostic list 65, a threshold 66, component hierarchy 67, and baseline ranges 68. The RO data 63 can comprise data from one or more RO. The data from each RO can be stored within the RO data 63 as a separate record pertaining to a vehicle of the set of vehicles being worked on at a repair shop. The RO data 63 can comprise RO data aggregated from multiple ROs. The threshold 66 can comprise any threshold value and/or threshold percentage discussed in this description.
The DSD 64 can comprise data the server 2 can use to determine an operating state of the display device 4. The data the server 2 uses to determine an operating state of the display device 4 can include vehicle identifying information 26, data indicating an elapsed time since the server 2 last received a communication from the display device 4, data indicating the most recent type of diagnostic list requested by and/or transmitted to the display device 4, and/or data indicating a repair has been made to the particular vehicle.
The DSD 64 can comprise data indicative of the determined operating state of the display device 4. Examples of the operating state include (i) the display device 4 is connected to the server 2, (ii) the display device is not connected to the server 2 (i.e., disconnected from the server 2), (iii) the display device 4 is connected to a particular vehicle (e.g., the vehicle 9), (iv) the display device 4 is no longer connected to the particular vehicle (i.e., disconnected from the particular vehicle), (v) the display device 4 is in a request and/or display diagnostic list mode for the particular vehicle, (vi) the display device 4 has exited the request and/or display diagnostic list mode for the particular vehicle, and (vii) the display device has returned to the request and/or display diagnostic list mode for the particular vehicle.
The DSD 64 can also comprise data indicating a diagnostic session at the display device 4 is active or inactive. The server 2 can determine a new diagnostic session is active upon receiving vehicle identifying information for a particular vehicle while the DSD 64 does not include data indicating a diagnostic session is active for the particular vehicle. The server 2 can determine an active diagnostic session for a particular vehicle has transitioned to inactive upon receiving vehicle identifying information for a different particular vehicle. The server 2 can determine an active diagnostic session for a particular vehicle has transitioned to an inactive session upon determining a threshold amount of time has elapsed since a particular activity of the active diagnostic session. As an example, the particular activity can comprise receiving a request from the display device 4, receiving a communication indicating the display device 4 is connected to the communication network 3 and/or transmitting a response with a diagnostic list to the display device 4. Other examples of the particular activity are also possible.
The baseline ranges 68 can comprise baseline ranges for PIDs. The baseline range for each PID can comprise a baseline maximum data value and a baseline minimum data value. The baseline ranges 68 can comprise baseline ranges for PIDs from each set of vehicles identifiable by some particular vehicle identifying information. In this way, the server 2 can provide the display device 4 with applicable baseline ranges with respect to a particular vehicle connected to the display device 4.
In one respect, the baseline ranges 68 can comprise baseline ranges defined by a vehicle manufacturer. For a particular PID associated with a DTC, the vehicle manufacturer may define the baseline maximum data value as the greatest data value for the particular PID an ECU would output while the associated DTC is set to inactive, and the vehicle manufacturer may define the baseline minimum data value as the lowest data value for the particular PID the ECU would output while the associated DTC is set to inactive.
In another respect, the baseline ranges 68 can comprise baseline ranges determined by the server 2 from PID data values received within communications that include PID data values, such as the communication 21. The server 2 can store the received PID data values within the baseline ranges 68 and determine the maximum and minimum data values for each PID for each set of vehicles identifiable by particular vehicle identifying information. The server 2 can maintain a PID count that indicates how many PID data values have been received and/or stored for a particular PID. The server 2 can compare the PID count to a first threshold PID count value stored in the threshold 66. If the server 2 determines that the PID count is less than the first threshold PID count value, the server 2 can produce a first baseline range for the particular PID. As an example, the server 2 can determine the first baseline range for the PID to be a mean maximum PID data value plus X standard deviations of the mean maximum PID data value and a mean minimum PID data value minus X standard deviations of the mean minimum PID data value. The mean maximum PID data value is the mean of maximum PID data values for the particular PID across vehicles identifiable by the particular vehicle identifying information with all DTC from the ECU that provides the particular PID set to inactive. The mean minimum PID data value is the mean of minimum PID data values for the particular PID across vehicles identifiable by the particular vehicle identifying information with all DTC from the ECU that provides the particular PID set to inactive.
As the server 2 continues to receive PID data values for the particular PID, the server 2 can determine the quantity of received PID data values for the particular PID exceeds the first threshold PID count value, but is less than a second threshold PID count value. In this situation, the server 2 can produce a second baseline range for the particular PID. As an example, the server 2 can determine the second baseline range for the PID to be a mean maximum PID data value plus X−1 standard deviations of the mean maximum PID data value and a mean minimum PID data value minus X−1 standard deviations of the mean minimum PID data value. The first baseline range can be referred to a loose baseline range with respect to the second baseline range. The second baseline range can be referred to as a tighter baseline range with respect to the first baseline range.
The server 2 can determine loose and tight baseline ranges in other manners. For example, before the server 2 has received a number of PID data values for the particular PID that exceeds the first threshold PID count value, the server 2 can add a first percentage of the mean maximum PID data value for the particular PID to that mean maximum PID data value or a first percentage of the maximum PID data value for the particular PID to that maximum PID data value. Furthermore, before the server 2 has received a number of PID data values for the particular PID that exceeds the first threshold PID count value, the server 2 can subtract a first percentage of the mean minimum PID data value for the particular PID from that mean minimum PID data value or a first percentage of the minimum PID data value for the particular PID from that minimum PID data value.
As the server 2 continues to receive PID data values for the particular PID, the server 2 can determine the quantity of received PID data values for the particular PID exceeds the first threshold PID count value, but is less than a second threshold PID count value. In this situation, the server 2 can add a second percentage of a mean maximum PID data value for the particular PID to that mean maximum PID data value or a second percentage of a maximum PID data value for the particular PID to that maximum PID data value, and the server 2 can subtract a second percentage of a mean minimum PID data value for the particular PID from that mean minimum PID data value or a second percentage of a minimum PID data value for the particular PID from that minimum PID data value. The second percentage can be smaller than the first percentage so that the baseline range determined using the second percentage is typically a tighter baseline range as compared to the baseline range determined using the first percentage.
The server 2 can provide the display device 4 with a baseline range for the particular PID without any tolerance values so that the display device 4 does not need to calculate a baseline range to be displayed on a display interface of the display device 4. Alternatively, the server 2 can provide the display device 4 with a baseline range for the particular PID with at least one tolerance value. The at least one tolerance value could, for example, be the first percentage or second percentage discussed above, or a value of the X standard deviations or the X−1 standard deviations. Other examples of the at least one tolerance value are also possible.
The CRPI 60 can comprise a plurality of program instructions. The CRPI 60 and any other CRPI described in this description can include data structures, objects, programs, routines, or other program modules that can be accessed by a processor and executed by the processor to perform a particular function or group of functions and are examples of program codes for implementing steps for methods described in this description.
In general, the CRPI 60 can include program instructions to cause the server 2 to perform any function described herein as being performed by the server 2 or to cause any component of the server 2 to perform any function herein as being performed by that component of the server 2. As an example, the CRPI 60 can include program instructions to perform the set of functions 200 shown in
As another example, the CRPI 60 can include program instructions to perform session management with respect to the display device 4. The processor 50 can use the DSD 64 to determine the operating state of the display device 4. Upon and/or in response to determining the display device 4 is in the request and/or display diagnostic list mode for the particular vehicle, the processor 50 can determine the requested diagnostic list and provide the display device 4 with a response including the requested diagnostic list.
Upon and/or in response to determining the display device 4 has exited the request and/or display diagnostic list mode for the particular vehicle and that a repair has been made to the particular vehicle, the processor 50 can provide a session-change response to the display device 4 to direct the display device 4 to display a previously-displayed diagnostic list or a different diagnostic list. The session-change response can include the previously-displayed diagnostic list or the different diagnostic list. As an example, the previously-displayed diagnostic list can comprise a PID filter list, and the different diagnostic list can comprise a component test filter list such that display device 4 displays a list of component tests that can be performed to verify the repair corrected the symptom exhibited by the particular vehicle. As another example, the previously-displayed diagnostic list can comprise a PID filter list, and the different diagnostic list can comprise a functional test filter list such that display device 4 displays a list of functional tests that can be performed to verify the repair corrected the symptom exhibited by the particular vehicle. As yet another example, the previously-displayed diagnostic list can comprise a PID filter list, and the different diagnostic list can comprise a reset procedure filter list such that display device 4 displays a list of reset procedures that can be performed with respect to a vehicle component repaired on the particular vehicle. The previously-displayed diagnostic list can comprise any of the diagnostic lists discussed in this description.
Upon and/or in response to determining the display device 4 has returned to the request and/or display diagnostic list mode for the particular vehicle, the processor 50 can provide a session-change response to the display device 4 to direct the display device 4 to display a previously-displayed diagnostic list or a different diagnostic list.
A communication interface such as the communication interface 51 or any other communication interface discussed in this description can include one or more communication interfaces. Each communication interface can include one or more transmitters configured to transmit data onto a network, such as the communication network 3. The data transmitted by the communication interface 51 can comprise any data described herein as being transmitted, output, and/or provided by the server 2. Moreover, each communication interface can include one or more receivers configured to receive data carried over a network, such as the communication network 3. The data received by the communication interface 51 can comprise any data described herein as being received by the server, such as repair order data and any request described herein.
A transmitter can transmit radio signals carrying data and a receiver can receive radio signals carrying data. A communication interface with that transmitter and receiver can include one or more antennas and can be referred to as a “radio communication interface,” an “RF communication interface,” or a “wireless communication interface.” The radio signals transmitted or received by a radio communication interface can be arranged in accordance with one or more wireless communication standards or protocols such as an IEEE 802.15.1 standard for WPANs, a Bluetooth version 4.1 standard developed by the Bluetooth Special Interest Group (SIG) of Kirkland, Washington, or an IEEE 802.11 standard for wireless LANs (which is sometimes referred to as a WI-FI® standard), or a cellular wireless communication standard such as a long term evolution (LTE) standard, a code division multiple access (CDMA) standard, an integrated digital enhanced network (IDEN) standard, a global system for mobile communications (GSM) standard, a general packet radio service (GPRS) standard, a universal mobile telecommunications system (UMTS) standard, an enhanced data rates for GSM evolution (EDGE) standard, or a multichannel multipoint distribution service (MMDS) standard.
Additionally or alternatively, a transmitter can transmit a signal (i.e., one or more signals or one or more electrical waves) carrying or representing data onto a wire (e.g., one or more wires) and a receiver can receive via a wire a signal carrying or representing data over the wire. The wire can be part of a network, such as the communication network 3. The signal carried over a wire can be arranged in accordance with a wired communication standard such as a Transmission Control Protocol/Internet Protocol (TCP/IP), an IEEE 802.3 Ethernet communication standard for a LAN, a data over cable service interface specification (DOCSIS standard), such as DOCSIS 3.1, a USB specification (as previously described), or some other wired communication standard.
The data transmitted by a communication interface can include a destination identifier or address of a network device to which the data is to be transmitted. The data transmitted by a communication interface can include a source identifier or address of the system component including the communication interface. The source identifier or address can be used to send a response to the network device that includes the communication interface that sent the data.
A communication interface that is configured to carry out communications over the communication network 3, such as the communication interface 51, can include a modem, a network interface card, and/or a chip mountable on a circuit board. As an example the chip can comprise a CC3100 Wi-Fi® network processor available from Texas Instruments, Dallas, Texas, a CC256MODx Bluetooth® Host Controller Interface (HCI) module available from Texas instruments, and/or a different chip for communicating via Wi-Fi®, Bluetooth® or another communication protocol.
Next,
Next,
Next,
Next,
The DTCs shown in
Next,
Next,
Next,
Next,
Next,
Next,
The RO 100 includes a service provider identifier 102, a date of service identifier 104, a customer indicator 106 that indicates a customer seeking service of a given vehicle, vehicle information 108 that indicates the given vehicle, vehicle service requests 110, 112, and 114 indicating the complaint(s) or service(s) requested by the customer, parts information 116 indicating parts obtained for servicing the given vehicle, service procedure information 118, 120, and 122 carried out on the given vehicle, and a vehicle-usage indicator 130 (e.g., vehicle mileage data that indicates a number of miles the given vehicle has been driven). The vehicle-usage indicator 130 on the RO 100 can indicate a driven distance using kilometers or some other units as an alternative or in addition to vehicle mileage data. In addition to or as an alternative to indicating a distance, the vehicle-usage indicator 130 can include a time-used indicator such as an hours indicator indicating, for example, how long a vehicle or an engine has been used.
Service provider identifier 102 can include information that indicates a name and geographic location of the service provider (e.g., the repair shop 8). Vehicle information 108 can include a vehicle identification number (VIN) 132 associated with the given vehicle and a description of the given vehicle. The vehicle information 108 is an example of particular vehicle identifying information for a set of vehicles that includes the given vehicle. Service procedure information 118, 120, and 122 can include information within distinct RO sections 124, 126, and 128, respectively, of the RO 100. The service procedure information within any one distinct RO section 124, 126, and 128 can be unrelated to the service procedure information with any other distinct section. Alternatively, two or more distinct sections including service procedure information can pertain to related service operations performed on the given vehicle.
The RO 100 includes labor operation codes (LOCs). The LOCs can conform to those defined by a vehicle manufacturer, a service provider that generates an RO, a service information provider, such as Mitchell Repair Information, LLC, Poway, California, or some other entity. For simplicity of
Next,
Block 201 includes determining, at the server 2, a diagnostic filter list for providing to the display device 4 in response to a request. The diagnostic filter list can comprise a PID filter list, a component test filter list, a functional test filter list, and/or a reset procedure filter list. Table 1 represents those diagnostic filter lists as diagnostic filter lists 1, 2, 3, and 4. The diagnostic filter list can comprise two or more diagnostic filter lists as represented by diagnostic filter lists 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, and 15 in Table 1.
Next, block 202 includes receiving, at the server 2, the request sent over the communication network 3 from the display device 4, wherein the request comprises particular vehicle identifying information and at least one symptom identifier. The request can be configured and/or communicated like the request for filter list 24 shown in
Next, block 203 includes transmitting, by the server 2 over the communication network 3 to the display device 4, a response to the request, the request comprising the diagnostic filter list. The response to the request can be configured and/or communicated like the response to the request 25 shown in
Next,
Block 211 includes receiving, at the server 2, RO data, wherein the RO data comprises data from one or more ROs that indicate particular vehicle identifying information, at least one symptom identifier, and a particular vehicle component. The received RO data can be stored as the RO data 63.
The particular vehicle identifying information referred to throughout this description can comprise a vehicle manufacturer identifier, and (i) at least one vehicle model year identifier and at least one vehicle model identifier, or (ii) at least one vehicle model year identifier, at least one vehicle model identifier, and at least one engine identifier. The server 2 can determine the vehicle identifying information contained in the vehicle information 108 of an RO. For the RO 100, the vehicle identifying information can comprise the Y/M/M (1997/Ford/Crown Victoria) identified on the RO 100, the Y/M/M/E (1997/Ford/Crown Victoria/4.6 L) identified on the RO 100, and/or at least a portion of the VIN 132. The server 2 can use taxonomies to determine which portions of the RO data contain the vehicle identifying information.
The server 2 can determine the at least one symptom identifier from various portions of an RO. For instance, the server 2 can determine the at least one symptom identifier from a vehicle service request (e.g., vehicle service requests 110, 112, or 114 shown on the RO 100 in
The particular vehicle component can comprise a vehicle component identified in the parts information 116 of an RO. For the RO 100, the particular vehicle component can comprise a mass air flow (MAF) sensor, an oil filter, and an engine coolant temperature (ECT) sensor. The server 2 can use taxonomies to determine which vehicle component listed in the parts information 116 pertains to which symptom identifier and/or service procedure on the RO 100.
Next, block 212 includes determining, at the server 2, symptom-to-PID mapping data 71 based on the received RO data and component-to-PID mapping data 72, wherein the component-to-PID mapping data 72 maps one or more PIDs from a set of available PIDs for a set of vehicles identifiable by the particular vehicle identifying information to the particular vehicle component, and wherein the symptom-to-PID mapping data 71 maps the one or more PIDs from the set of available PIDs for the set of vehicles identifiable by the particular vehicle identifying information to the at least one symptom identifier.
Next, block 213 includes determining at the server 2 based on the set of available PIDs for the set of vehicles and the symptom-to-PID mapping data 71, a PID filter list (e.g., a PID filter list from the diagnostic list 65), wherein the PID filter list is associated with the particular vehicle identifying information and the at least one symptom identifier, and wherein the PID filter list indicates a symptom-based subset of PIDs from the set of available PIDs for the set of vehicles. Determining the PID list can include the server 2 retrieving a PID list stored in a memory before the server 2 received the request. Alternatively, determining the PID list can include generating the PID list after the server 2 receives the request (e.g., without retrieving a PID list stored in a memory before the server 2 received the request).
The PID filter list can comprise a list of one or more PIDs. The one or more PIDs can be represented in any of a variety of formats, such as a PID name consisting of one or more words, an index value into an ordered list of PIDs 350 (shown in
Next, block 214 (shown in
Next, block 215 includes transmitting, by the server 2 over the communication network 3 to the display device 4, a response to the request (e.g., the response to the request 25), the response comprising the PID filter list. The display device 4 can subsequently display the PID filter list. The response to the request can comprise a computer-readable file including the PID filter list. The computer-readable file can comprise an extensible markup language (XML) file or another type of computer-readable file.
Additional methods including the functions of the set 210 can be performed to determine diagnostic lists shown in in Table 1.
A first additional method including the functions of the set 210 includes: (i) determining, at the server 2, symptom-to-component-test mapping data based on the received RO data and component-to-component-test mapping data, wherein the symptom-to-component-test mapping data maps one or more component tests from a set of available component tests for the set of vehicles identifiable by the particular vehicle identifying information to the at least one symptom identifier, (ii) determining, at the server 2 based on the set of available component tests for the set of vehicles and the symptom-to-component-test mapping data, a component test filter list, wherein the component test filter list is associated with the particular vehicle identifying information and the at least one symptom identifier, and wherein the component test filter list indicates a symptom-based subset of component tests from the set of available component tests for the set of vehicles, and (iii) retrieving, by the server 2 based on the particular vehicle identifying information and the at least one symptom identifier received in the request, the component test filter list. For the first additional method including the set 210, the response to the request comprises the component test filter list. For the first additional method including the set 210, the PID filter list can comprise index values 92 into an ordered list of PIDs 90 for vehicles identifiable by the particular vehicle identifying information, and/or the component test filter list comprises index values 97 into an ordered list of component tests 95 for vehicles identifiable by the particular vehicle identifying information
For the first additional method including the set 210, the at least one symptom identifier can comprise at least one DTC that each vehicle of the set of vehicles can set active. The symptom-based subset of PIDs from the set of available PIDs for the set of vehicles comprises a DTC-based subset of PIDs from the set of available PIDs for the set of vehicles. The symptom-based subset of component tests from the set of available component tests for the set of vehicles comprises a DTC-based subset of component tests from the set of available component tests for the set of vehicles. For the first additional function including the set 210, the component test filter list can comprise a component test performable by an oscilloscope of the display device 4 or a multimeter of the display device 4.
The first additional method including the functions of the set 210 can further include: (i) determining, at the server 2, symptom-to-functional-test mapping data based on the received RO data and component-to-functional-test mapping data, wherein the symptom-to-functional-test mapping data maps one or more functional tests from a set of available functional tests for the set of vehicles identifiable by the particular vehicle identifying information to the at least one symptom identifier, (ii) determining, at the server 2 based on the set of available functional tests for the set of vehicles and the symptom-to-functional-test mapping data, a functional test filter list, wherein the functional test filter list is associated with the particular vehicle identifying information and the at least one symptom identifier, and wherein the functional test filter list indicates a symptom-based subset of functional tests from the set of available functional tests for the set of vehicles, and (iii) retrieving, by the server 2 based on the particular vehicle identifying information and the symptom received in the request, the functional test filter list. For the first additional method including the set 210, the response to the request can further comprises the functional test filter list. The functional test filter list can indicate a functional test that comprises transmission of a vehicle data message from the display device 4 to the vehicle 9. The PID filter list can comprise index values into an ordered list of PIDs, component tests, and functional tests for vehicles identifiable by the particular vehicle identifying information.
For the first additional method including the set 210, the at least one symptom identifier can comprise at least one DTC that each vehicle of the set of vehicles can set active, the symptom-based subset of PIDs from the set of available PIDs for the set of vehicles can comprise a DTC-based subset of PIDs from the set of available PIDs for the set of vehicles, the symptom-based subset of component tests from the set of available component tests for the set of vehicles can comprise a DTC-based subset of component tests from the set of available component tests for the set of vehicles, and the symptom-based subset of functional tests from the set of available functional tests for the set of vehicles can comprise a DTC-based subset of functional tests from the set of available functional tests for the set of vehicles.
A second additional method including the functions of the set 210 includes: (i) determining, at the server 2, symptom-to-functional-test mapping data based on the received RO data and component-to-functional-test mapping data, wherein the symptom-to-functional-test mapping data maps one or more functional tests from a set of available functional tests for the set of vehicles identifiable by the particular vehicle identifying information to the at least one symptom identifier, (ii) determining, at the server 2 based on the set of available functional tests for the set of vehicles and the symptom-to-functional-test mapping data, a functional test filter list, wherein the functional test filter list is associated with the particular vehicle identifying information and the at least one symptom identifier, and wherein the functional test filter list indicates a symptom-based subset of functional tests from the set of available functional tests for the set of vehicles, and (iii) retrieving, by the server 2 based on the particular vehicle identifying information and the symptom received in the request, the functional test filter list. For the second additional function including the set 210, the response to the request comprises the functional test filter list.
For the second additional method including the set 210, the at least one symptom identifier can comprise at least one diagnostic trouble code (DTC) that each vehicle of the set of vehicles can set active, the symptom-based subset of PIDs from the set of available PIDs for the set of vehicles can comprise a DTC-based subset of PIDs from the set of available PIDs for the set of vehicles, and the symptom-based subset of functional tests from the set of available functional tests for the set of vehicles can comprise a DTC-based subset of functional tests from the set of available functional tests for the set of vehicles. For the second additional method including the set 210, the functional test filter list can indicate a functional test that comprises transmission of a vehicle data message from the display device to the vehicle. For the second additional method including the set 210, the PID filter list can comprise index values into an ordered list of PIDs and functional tests for vehicles identifiable by the particular vehicle identifying information.
A third additional method including the functions of the set 210 includes: (i) determining, at the server 2, symptom-to-reset-procedure mapping data based on the received RO data and component-to-reset-procedure mapping data, wherein the symptom-to-reset-procedure mapping data maps one or more reset procedures from a set of available reset procedures for the set of vehicles identifiable by the particular vehicle identifying information to the at least one symptom identifier, (ii) determining, at the server 2 based on the set of available reset procedures for the set of vehicles and the symptom-to-reset-procedure mapping data, a reset procedure filter list, wherein the reset procedure filter list is associated with the particular vehicle identifying information and the at least one symptom identifier, and wherein the reset procedure filter list indicates a symptom-based subset of reset procedures from the set of available reset procedures for the set of vehicles, and (iii) retrieving, by the server 2 based on the particular vehicle identifying information and the symptom received in the request, the reset procedure filter list. For the third additional method including the set 210, the response to the request comprises the reset procedure filter list. For the third additional method including the set 210, the reset procedure filter list can comprise index values into an ordered list of reset procedures for vehicles identifiable by the particular vehicle identifying information.
For the third additional method including the set 210, the at least one symptom identifier can comprise at least one diagnostic trouble code (DTC) that each vehicle of the set of vehicles can set active, the symptom-based subset of reset procedures from the set of available reset procedures for the set of vehicles can comprise a DTC-based subset of reset procedures from the set of available reset procedures for the set of vehicles, and the symptom-based subset of reset procedures from the set of available reset procedures for the set of vehicles can comprise a DTC-based subset of reset procedures from the set of available reset procedures for the set of vehicles.
The third additional method including the set 210 can include: (i) establishing, at the server 2, a diagnostic session for the display device 4 with respect to the first response and the second response, (ii) determining, at the server 4, a vehicle repair has occurred with respect to the diagnostic session, and (iii) transmitting, by the server 2 over the communication network 3 to the display device 4, the second response in response to determining the vehicle repair has occurred with respect to the diagnostic session. In this regard, the response comprises a first response and a second response, the first response comprises the PID filter list and the second response comprises the reset procedure filter list, and transmitting the response comprising the PID filter list comprises transmitting the first response. Determining the vehicle repair has occurred can comprise determining a threshold amount of time has elapsed since the first response was transmitted to the display device 4.
A fourth additional method including the functions of the set 210 includes: determining the PID filter list can comprise modifying an existing PID filter list. The existing PID filter list can comprise a different subset of PIDs from the set of available PIDs for the set of vehicles. The existing PID filter list is associated with the particular vehicle identifying information and the at least one symptom identifier. Modifying the existing PID filter list can include adding at least one PID from the set of available PIDs for the set of vehicles to the existing PID filter list and/or removing at least one PID from the existing PID filter list.
A fifth additional method including the functions of the set 210 includes: determining, at the processor 50 based on the set of RO data, the subset of RO data by determining the set of RO data indicates the particular vehicle component is a most-replaced component and the at least one symptom identifier is a most-reported symptom for vehicles of the set of vehicles identifiable by the particular vehicle identifying information. For such a method, the RO data comprises a subset of a set of RO data, and receiving the RO data comprises receiving the set of RO data. Also, the set of RO data comprises data from multiple ROs that indicate (i) the particular vehicle identifying information or different vehicle identifying information, (ii) the at least one symptom identifier or a different symptom, and (iii) the particular vehicle component or a different vehicle component.
A sixth additional method including the functions of the set 210 includes: (i) determining, at the server 2, a vehicle component related to the particular vehicle component, (ii) determining, at the server 2, at least one PID to add to the PID filter list based on component-to-PID mapping data that maps one or more PIDs from the set of available PIDs for the set of vehicles identifiable by the particular vehicle identifying information to the vehicle component related to the particular vehicle component, and (iii) adding, by the server, the at least one PID to the PID filter list. The server 2 can determine the vehicle component related to the particular vehicle component by searching data within the memory 52 that identifies vehicle components of the vehicles of the set of vehicles in a hierarchical format based on systems and/or subsystems of the vehicles of the set of vehicles. The searched data can comprise the component hierarchy 67.
Next,
Each indented line including a rectangular bullet point “□” lists a vehicle component that is part of an identified system or subsystem within a vehicle. Each vehicle component in the component hierarchy 67 can be associated with a PID, a component test, a functional test, and/or a reset procedure. Examples of the PID, component test, functional test, and/or reset procedure associated with the vehicle component are shown in
As an example, if the particular vehicle component for the set 210 comprises an oxygen sensor, the processor 50 can determine another PID, component test, functional test, and/or reset procedure to include in a diagnostic list by reference to the component hierarchy 67. The other PID, component test, functional test, and/or reset procedure can be related to a vehicle component within the same system or subsystem as the particular vehicle component or a vehicle component within a different system or subsystem. The vehicle components within each system and subsystem within the component hierarchy can be ordered so that the processor 50 can determine which vehicle component within the other system or subsystem are to be considered to determine whether the vehicle component is associated with a PID, component test, functional test, and/or reset procedure.
Next,
Block 221 includes receiving, at the server 2, a first set of PID values and a second set of PID values, wherein the first set of PID values are for a particular PID from a first set of vehicles with all DTCs for a particular ECU within each vehicle of first the set of vehicles set to inactive, wherein the second set of PID values are for the particular PID from a second set of vehicles with one or more particular DTCs for the particular ECU within each vehicle of the second set of vehicles set to active, and wherein the first set of vehicles and the second set of vehicles are identifiable by particular vehicle identifying information.
The first set of PID values can include and/or be associated with data that that indicates the first set of vehicles, the status of DTC within the first set of vehicles for the particular ECU, and the PID.
Returning to
Next, block 223 includes determining, by the server from among the second set of PID values, one or more PID values for the particular PID is outside of the range of PID values for the particular PID by a threshold value. As an example, the threshold value with respect to the example PID 6 for fuel pressure can be seven, such as plus seven from the greatest value in the determined range and/or minus seven from the smallest value in the determined range. In accordance with that example, the PID values 27, 26, 25, and 23 for vehicle 1 are PID values outside of the range of PID values for PID 6 by the threshold value, PID values 26, 26, 24, 22, and 24 for vehicle 2 are PID values outside of the range of PID values for PID 6 by the threshold value, PID values 25, 24, 26, and 26 for vehicle 3 are PID values outside of the range of PID values for PID 6 by the threshold value, and PID values 27, 24, 24, 25, and 26 for vehicle X are PID values outside of the range of PID values for PID 6 by the threshold value.
Determining the one or more PID values for the particular PID is outside of the range of PID values can comprise (i) determining the second set of PID values comprises a first quantity of PIDs, (ii) determining the one or more PID values for the particular PID comprises a second quantify of PIDs, and (iii) determining the second quantity of PIDs exceeds a threshold percentage of the first quantity of PIDs.
Determining the range of PID values for the particular PID can comprise determining a range of values for the particular PID at some number of standard deviations (e.g., one, two, three, or four standard deviations) of a mean value of PID values for the particular PID within the first set of PID values. The server 2 can determine the mean value of the PID values.
The range of PID values for the particular PID can comprise a first range of PID values. The server 2 can determine that each PID value of the first range of PID values was generated in a vehicle of the first set of vehicles while the vehicle is operating in a first operating state. The response can further comprise data indicating the first range of PID values is associated with the first operating state. That data can be used for placing a vehicle connected to the display device 4 in the first operating state and/or for guiding a user in placing the vehicle connected to the display device 4 in the first operating state. The range of PID values can be stored within the baseline ranges 68.
Next, block 224 includes adding, by the server, the particular PID to a PID filter list in response to determining the one or more PID values for the particular PID is outside of the range of PID values for the particular PID by the threshold value. The PID filter list can be stored as and/or within the diagnostic list 65. The PID filter list can be associated with and/or include the particular vehicle identifying information and the particular DTC to enable the server 2 to retrieve the PID filter list in response to a request.
The PID filter list can include one or more default PIDs before the particular PID is added to the PID filter list and after the particular PID is added to the PID filter list. As an example, PIDs 1, 3, 5, 8-12, 14, 15, 18, 20, 22, 24, 25 and 30 from the PID list 350 can be default PIDs and PID 6 can be the particular PID added to the PID filter list. The PID filter list can comprise index values 351 into an ordered list of PIDs (e.g., the PID list 350) for vehicles identifiable by the particular vehicle identifying information. Adding the particular PID to the PID filter list can be conditioned on the server 2 determining the one or more PID values for the particular PID comprise at least a threshold number of PID values.
Next, block 225 includes receiving, at the server 2, a request sent over the communication network 3 from the display device 4, wherein the request comprises the particular vehicle identifying information and the particular DTC.
Next, block 226 includes retrieving, by the server 2 based on the particular vehicle identifying information and the particular DTC received in the request, the PID filter list. The server 2 can retrieve the PID filter list from the diagnostic list 65.
Next, block 227 includes transmitting, by the server 2 over the communication network 3 to the display device 4, a response to the request, the response comprising the PID filter list.
In addition to determining the first range of PID values, the method 220 can include determining, by the server 2 from among the first set of PID values, a second range of PID values for the particular PID. The server can determine each PID value of the second range of PID values was generated in a vehicle of the first set of vehicles while the vehicle is operating in a second operating state different than the first operating state. The response can further comprise the second range of PID values and data indicating the second range of PID values is associated with the second operating state. That data can be used for placing a vehicle connected to the display device 4 in the second operating state and/or for guiding a user in placing the vehicle connected to the display device 4 in the second operating state.
The operating states associated with a range of PID values can be defined by one or more vehicle operating parameters. Each vehicle operating parameter can comprise a single parameter value or a range of parameter values. The single parameter value can comprise a mean value of multiple parameter values. As an example, the first operating state can comprise a first engine revolutions per minute (RPM) value, a first engine load value, and/or a first engine temperature value. In accordance with that example, the second operating state can comprise a second engine RPM value if the first operating state comprises the first RPM value, a second engine load value if the first operating state comprises the first engine load value, and a second engine temperature value if the first operating state comprises the first engine temperature value. The vehicle operating parameters can be determined from PID values. For example, the first and second engine load values can be determined from PID values that indicate a calculated engine load.
Next,
Block 231 includes receiving, at the server 2, a first request sent over a communication network from a first display device connected to a first vehicle, wherein the first request comprises particular vehicle identifying information and at least one symptom identifier, wherein the particular vehicle identifying information identifies a particular set of vehicles, wherein the particular set of vehicles comprises the first vehicle, and wherein the at least one symptom identifier comprises a symptom that each vehicle of the particular set of vehicles can exhibit. The first request can be configured and/or communicated like the request for filter list 24 shown in
The at least one symptom identifier can comprise at least one diagnostic trouble code that each vehicle of the particular set of vehicles can set to active. The particular vehicle identifying information can comprise a vehicle manufacturer identifier, and (i) at least one vehicle model year identifier and at least one vehicle model identifier, or (ii) at least one vehicle model year identifier, at least one vehicle model identifier, and at least one engine identifier.
Next, block 232 transmitting, by the server over the communication network to the first display device, a response to the first request, the response to the first request comprising a PID filter list. The response to the first request can be configured and/or communicated like the response to the request 25 shown in
Next, block 233 determining, by the server, the first display device requested from the first vehicle for display by the first display device an additional PID not included within the PID filter list. Determining the first display device requested from the first vehicle for display by the first display device an additional PID not included within the PID filter list can comprise determining the additional PID was requested within a threshold amount of time after the server receives the first request or after the server transmits the response.
Next, block 234 generating, by the server, a modified PID filter list by adding the additional PID to the PID filter list. The modified PID filter list can comprise index values into an ordered list of PIDs 350 for vehicles identifiable by the particular vehicle identifying information. The modified PID filter list can be stored in the diagnostic list 65. In accordance with the example in which the additional PID is PID6 for fuel pressure, the modified PID filter list can comprise the index values 351.
Next, block 235 receiving, at the server after generating the modified PID filter list, a next request sent over the communication network from a second display device, wherein the next request comprises the particular vehicle identifying information and the at least one symptom identifier. The next request can be configured and/or communicated like the request for filter list 24 shown in
Next, block 236 transmitting, by the server over the communication network to the second display device, a response to the next request, the response to the next request comprising the modified PID filter list. In one respect, the second display device is the first display device. In a second respect, the second display device is not the first display device. In other words, the first display device and the second display device are individual display devices. The response to the next request can be configured and/or communicated like the response to the request 25 shown in
As an example, a first additional function that can be performed with the set 230 includes: (i) receiving, at the server 2, PID data provided to the first display device from the first vehicle, and (ii) determining, by the server 2, the PID data provided to the first display device from the first vehicle and subsequently received by the server includes PID data for the additional PID to be displayed by the first display device.
As another example, a second additional function that can be performed with the set 230 includes receiving, at the server 2, data indicating the first display device received an input requesting display of the additional PID, wherein the server 2 determines the first display device requested from the first vehicle for display by the first display device the additional PID not included within the PID filter list based at least in part on the data indicating the first display device received an input requesting display of the additional PID.
As yet another example, a third additional function that can be performed with the set 230 includes: (i) retrieving, by the server 2 based on the particular vehicle identifying information and the at least one symptom identifier received in the first request, the PID filter list from a computer-readable memory 52, and/or (ii) retrieving, by the server 2 based on the particular vehicle identifying information and the at least one symptom identifier received in the next request, the modified PID filter list from a computer-readable memory 52.
In accordance with the example embodiment including the set 230, the first display device can be one of multiple display devices registered with the server 2. Accordingly, generating the modified PID filter list can be conditioned on the server 2 determining the first display device requesting from the first vehicle for display by the first display device the additional PID not included within the PID filter list is an nth time any of the multiple display devices has requested for display on the any of the multiple display devices the additional PID not included within the PID filter list after the server 2 has transmitted the PID filter list to the any of the multiple display devices. For this example embodiment, “n” of the nth time comprises a predetermined threshold number greater than one.
In further examples, a functional test filter list, a component test filter list, or a reset procedure filter list may be modified according to information received by the server 2 that indicates which specific tests or reset procedures were performed on vehicles having the particular vehicle identifying information and the at least one symptom identifier. The server 2 may receive messages from display devices indicating when tests or reset procedures are performed. The server 2 may then determine to adjust one of the diagnostic filter lists based on the received messages. For instance, if the server 2 determines that a particular functional test not in the functional test filter list has been performed above a threshold frequency on vehicles having the particular vehicle identifying information and the at least one symptom identifier, the server 2 may add the particular functional test to the functional test filter list. Additionally, if the server 2 determines that an existing functional test in the functional test filter list has been performed less than a threshold frequency on vehicles having the particular vehicle identifying information and the at least one symptom identifier, the server 2 may remove the existing functional test from the functional test filter list.
In additional examples, the server 2 may monitor the frequency of performance of functional tests, component tests, and/or reset procedures in order to determine a ranking. The server 2 may then provide an indication of the ranking as part of the functional test filter list, component test filter list, and/or reset procedure list. For example, the component test filter list for vehicles having the particular vehicle identifying information and the at least one symptom identifier may include five component tests. The server 2 may receive messages from multiple display devices indicating when one of the five component tests has been performed on a vehicle having the particular vehicle identifying information and the at least one symptom identifier. The server 2 may determine a ranking of the five component tests based on the frequency of performance of each of the five component tests indicated by the received messages. The server 2 may then indicate the ranking when providing the component test filter list so that display devices may display the five component tests in order based on frequency of performance.
In further examples, the server 2 may provide a ranking of functional tests, component tests, and/or reset procedures based on the probability of component failure of different associated components. For example, a functional test filter list may include two functional tests related to a first vehicle component and two functional tests related to a second vehicle component. The server 2 may determine a respective probability that each of the first vehicle component and the second vehicle component has failed for vehicles having the particular vehicle identifying information and the at least one symptom identifier. If the server 2 determines that the first vehicle component has a higher probability of failure, then the two functional tests related to the first vehicle component may be ranked higher than the two functional tests related to the second vehicle component. The server 2 may provide the ranking and an indication of an associated vehicle component for each functional test when providing the functional test filter list to a display device.
In further examples, the server 2 may provide a ranking of functional tests and/or component tests based on an amount of time determined to be required to perform the tests. The time required to perform a particular test can be determined from data indicating when the particular test was previously selected and when performance of the particular test was completed. As an example, a functional test filter list may include a first functional test and a second functional test related to a first vehicle component. The server 2 can determine that the time required to perform the first functional test is greater than the time required to perform the second test. The server 2 can then rank the second test first and the first test second within the functional test filter list.
Next,
The processor 250 can comprise one or more processors. The processor 250 can include a general purpose processor (e.g., an INTEL® single core microprocessor or an INTEL® multicore microprocessor), or a special purpose processor (e.g., a digital signal processor, a graphics processor, or an application specific integrated circuit (ASIC) processor). The processor 250 can be configured to execute computer-readable program instructions (CRPI). For example, the processor 250 can execute CRPI 260 stored in the memory 252. The processor 250 can be configured to execute hard-coded functionality in addition to or as an alternative to software-coded functionality (e.g., via CRPI). The processor 250 can be programmed to perform any function or combination of functions described herein as being performed by the display device 4.
The memory 252 can include one or more memories. The memory 252 can comprise a non-transitory memory, a transitory memory, or both a non-transitory memory and a transitory memory. A non-transitory memory, or a portion thereof, can be located within or as part of a processor (e.g., within a single integrated circuit chip). A non-transitory memory, or a portion thereof, can be separate and distinct from a processor.
The memory 252 stores computer-readable data, such as the CRPI 260, an index 261, and a default diagnostic list 262.
The CRPI 260 can comprise a plurality of program instructions. The CRPI 260 can include data structures, objects, programs, routines, or other program modules that can be accessed by a processor and executed by the processor to perform a particular function or group of functions and are examples of program codes for implementing steps for methods described in this description.
In general, the CRPI 260 can include program instructions to cause the display device 4 to perform any function described herein as being performed by the display device 4 or to cause any item of the display device 4 to perform any function herein as being performed by that item of the display device 4. As an example, the CRPI 260 can include program instructions to perform the set of functions 360 shown in
The index 261 may be the same as the index 61 described in reference to
The default diagnostic list 262 may be the same as the diagnostic list 65 described in reference to
The communication interface 251 can include one or more communication interfaces. Each communication interface can include one or more transmitters configured to transmit data onto a network, such as the communication network 3. The data transmitted by the communication interface 251 can comprise any data described herein as being transmitted, output, and/or provided by the display device 4. Moreover, each communication interface can include one or more receivers configured to receive data carried over a network, such as the communication network 3. The data received by the communication interface 251 can comprise any data described herein as being received by the display device 4, such as vehicle identifying information or a DTC.
Next,
Display interface 300 may display identifying information 304 about a vehicle to be serviced. The identifying information 304 may include a year, make, model, and engine as displayed in
Display interface 300 may additionally include an indication of at least one symptom identifier 302. The at least one symptom identifier 302 may include a single DTC, such as engine code P0171. In other examples, the at least one symptom identifier 302 may include two or more DTCs. In further examples, the at least one symptom identifier 302 may include a different type of symptom identifier as well or instead. For instance, the at least one symptom identifier 302 may be entered via display interface 300 or a different user interface. In another example, the at least one symptom identifier 302 may be captured from a repair order.
Display interface 300 may further include an indicator of network connectivity 306 of display device 4. For instance, the indicator of network connectivity 306 may indicate that the display device 4 has an active wireless or wired network connection. In some examples, whether or not the display device 4 has network connectivity may be used to determine a state of the display interface 300. Different information may be displayed on display interface 300 depending on the current state of display interface 300.
Display interface 300 may additionally include one or more information cards 310, 330, and 340. Each of the information cards 310, 330, and 340 may be selectable via display interface 300. In some examples, selection of an information card may cause the card to switch to a dynamic mode in which live data is displayed. In further examples, a display interface may include different or additional information cards than those displayed in
Display interface 300 includes PID card 310, which may be used to show a code-specific customized PID list. In particular, card 310 may display a subset of PIDs that are selected from a set of available PID's based on the at least one symptom identifier 302. As shown in
Display interface 300 additionally includes functional test card 330, which may be used to show a code-specific list of functional tests. In particular, functional test card 330 may display a subset of functional tests that are selected from a set of available functional tests based on the at least one symptom identifier 302. As shown in
Display interface 300 additionally includes component test card 340, which may be used to show a code-specific list of component tests. In particular, component test card 340 may display a subset of component tests that are selected from a set of available component tests based on the at least one symptom identifier 302. As shown in
Next,
PID card 310 displays a code-specific customized PID list which includes six different PIDs. The six PIDs have six corresponding descriptors: Engine Speed, Short Term FT Bank 2, MAP Sensor (kPa), HO2S Bank 1 Sensor 1, Short Term FT Bank 1, and ECT Sensor. This symptom-based subset of PIDs may be determined by display device 4 based on a PID filter list provided from server 2 for the at least one symptom identifier 302. In one example, PID descriptors may be displayed when PID card 310 is in a static mode, but live PID data may not be displayed. When PID card 310 is selected via display interface 300, PID card 310 may be switched to a dynamic mode in which live PID data is displayed. In some examples, live PID data may be requested by display device 4 and received from vehicle 9 in response to selection of PID card 310 via display interface 300.
Functional test card 330 displays a code-specific functional test list which includes three different functional tests and reset procedures. The three functional tests and reset procedures have three corresponding descriptors: Engine Speed Control, Fuel Trim Enable, and Fuel Trim Reset. This symptom-based subset of functional tests and reset procedures may be determined by display device 4 based on a functional test filter list from server 2 for the at least one symptom identifier 302. In one example, when a particular functional test is selected from functional test card 330, a functional test may be initiated by a communication from display device 4 to vehicle 9.
Component test card 340 displays a code-specific component test list which includes three different component tests. The three component tests relate to three different vehicle components: Fuel Pump, Oxygen Sensor, and Mass Airflow Sensor. This symptom-based subset of component tests may be determined by display device 4 based on a component test filter list from server 2 for the at least one symptom identifier 302. In one example, when a particular component test is selected from component test card 340, a component test may be initiated by a communication from display device 4 to a multimeter or an oscilloscope that is connected to vehicle 9.
Next,
A baseline range may additionally be displayed within display interface 300 for each PID in the symptom-based subset of PIDs. For instance, baseline range 313 may be displayed the Engine Speed PID 311. The baseline range 313 may indicate a typical operating range between 500 and 720 for the Engine Speed PID 311. Baseline ranges are similarly displayed for each additional PID with the symptom-based subset of PIDs. In particular, the MAP Sensor PID has a baseline range between 20 and 64, the Short Term FT Bank 1 PID has a baseline range between −1 and 1, the Short Term FT Bank 2 PID has a baseline range between −1 and 1, the HO2S Bank 1 Sensor 1 PID has a baseline range between 0.1 and 1, and the ECT Sensor PID has a baseline range between 190 and 221.
In some examples, the displayed baseline ranges may be received by display device 4 from server 2. In other examples, baseline ranges for one or more displayed PIDs in the symptom-based subset of PIDs may be unavailable from server 2. For such PIDs, prompts may be provided via display interface 300 to allow a technician to input a minimum and maximum value for the PID. In further examples, default baseline ranges may be stored on display device 4 for certain PIDs. In such examples, when a baseline range for a given PID is unavailable from server 2, a default baseline range stored on display device 4 for the given PID may instead be displayed. A technician may only be queried for minimum and maximum values if a baseline range is unavailable from server 2 and display device 4 also lacks a default baseline range for the given PID.
Display interface 300 may additionally provide a listing of other available PIDs not in the symptom-based subset of PIDs for selection by a technician. For instance, the other available PIDs may be viewable within a drop-down menu. Upon selection of a particular PID from the other available PIDs, the particular PID may be added to PID card 310 so that a technician may view live values for the particular PID. Additionally, display device 4 may send a message to server 2 indicating that the particular PID was selected for a vehicle having identifying information 304 and the at least one symptom identifier 302. The server 2 may process such messages in order to determine associations between particular PIDs and vehicle symptoms.
In further examples, display interface 300 may additionally provide an option to remove one or more PIDs from PID card 310. For instance, when a particular PID from the other available PIDs is added to PID card 310 by a technician, the technician may be required to select an existing PID from PID card 310 for removal. Display device 4 may send a message to server 2 indicating that the existing PID was selected for removal for a vehicle having identifying information 304 and the at least one symptom identifier 302. The server 2 may process such messages in order to disassociate particular PIDs and vehicle symptoms.
Next
The display interface 300 may therefore first provide a DTC-based or symptom-based subset of PIDs to provide a technician with PIDs of interest to focus on for a particular DTC or symptom. If machine learned baseline ranges are available for those PIDs of interest, the display interface 300 may also display the baseline ranges and highlight out-of-range PIDs to further facilitate a technician's ability to diagnose a vehicle being serviced.
In some examples, baseline ranges received by display device 4 from server 2 may not be displayed on display interface 300, but may still be used to highlight out-of-range PIDs. The derived baseline ranges provided by server 2 may therefore be concealed by display device 4. By contrast, user-entered baseline ranges may always be displayed within display interface 300.
Next,
In an additional example embodiment, a history of PID data may be recorded as soon as a PID value crosses outside of its baseline range (e.g., the previous 10 seconds). The history of PID data may be recorded only for the particular PID that is out-of-range, or it may be recorded for all displayed PIDs. The recording may be used to allow a technician to replay PID values to help diagnose why a particular PID went out of its baseline range at a particular point in time.
Next,
Multiple baseline ranges for a particular PID may be provided by server 2 to display device 4. Each baseline range may correspond to a different operating state of vehicle 9. In this manner, more precise baseline ranges may be displayed to a technician in situations where the typical value range for a PID is different depending on vehicle operating state. When the vehicle operating state changes, the baseline ranges displayed on display interface 300 may responsively be changed to correspond to the new vehicle operating state.
In some examples, display device 4 may detect the current vehicle operating state. For instance, display device 4 may determine the current vehicle operating state based on data received from vehicle 9 or from another device in communication with vehicle 9. Display device 4 may then automatically determine the vehicle operating state and provide an indication of the current vehicle operating state to a technician.
In other examples, an input mechanism may be provided for a technician to select the current vehicle operating state. For instance, a dropdown menu may be provided with several different possible vehicle operating states for which server-provided baseline ranges are available. When a technician selects the current vehicle operating state via the input mechanism, the corresponding baseline ranges for displayed PID's may automatically displayed. In other examples, the corresponding baseline ranges may not be displayed, but may still be used to identify when a PID value goes out of range as previously described.
In further examples, baseline ranges may only be available for a particular vehicle operating state. For instance, a particular vehicle operating state may have been used to generate the baseline ranges (e.g., only PID data collected when the vehicle was in the particular vehicle operating state may have been used by server 2 to generate the baseline ranges). In such a scenario, an indication of the particular vehicle operating state may be displayed on display interface 300 to help a technician put the vehicle into an operating state for which the displayed baseline ranges are accurate.
In additional examples, one or more cues may be provided to assist a technician in putting a vehicle into an operating state for which baseline ranges are available. The cues may be visual cues, audio cues, tactile cues, or a different type of feedback. For instance, audio cues may instruct a technician to raise the RPM of a vehicle until an RPM is reached for which baseline ranges for the displayed PIDs are available.
In another example, the vehicle operating state may correspond to a geographical location of the vehicle. For instance, different baseline ranges may be generated by server 2 for vehicles located in a first area than for vehicles located in a second area. External factors such as weather conditions may cause the typical operating baseline ranges to be different for the same type of vehicle when the vehicle is located in a different geographical location.
In a further example, the vehicle operating state may correspond to different ranges of engine temperature for the engine of the vehicle. In some examples, a vehicle operating state may include a combination of two or more different states, such as a combination of RPM and engine temperature. Other vehicle operating states may also be used as well or instead.
In an additional example, server 2 may provide multiple different PID filter lists that correspond to different vehicle operating states for a given at least one symptom identifier. In that case, display device 4 may determine which PID filter list to apply and which symptom-based subset of PIDs to display based on a current operating state of the vehicle 9. Similarly, server 2 may also provide multiple different functional test filter lists or component test filter lists that correspond to different vehicle operating state for a given at least one symptom identifier. In that case, display device 4 may determine which tests to display as part of a symptom-based subset based on the current vehicle operating state.
In a further example, display device 4 may deactivate the flagging of PIDs with out-of-range values based on the current vehicle operating state. In particular, server 2 may provide an indication of a vehicle operating state for which PID baseline ranges are to be applied. If display device 4 determines that the current vehicle operating state does not correspond to the vehicle operating state indicated by server 2, display device 4 may stop flagging PIDs with out-of-range values so as not to distract a technician with inapplicable warnings. As an example, a baseline range for a particular PID may have been generated by server 2 based on PID data from vehicles at idle (e.g., between 600 RPM and 900 RPM). If display device 4 determines that a current vehicle being serviced is operating at 2200 RPM, display device 4 may refrain from flagging the particular PID even if the particular PID has a value outside of the baseline range indicated by server 2. As previously discussed, display device 4 may additionally provide one or more cues in order to indicate to a technician how to switch the vehicle to an operating state at which the baseline range may be applied.
Next,
Additionally, the display interface 300 may also show all available functional tests and reset procedures 331, which may include any available functional tests and reset procedures that were not identified for the symptom-based subset. The other available functional tests and reset procedures 331 may be displayed within functional test card 330, or as part of a separate window. In this case, the other available functional tests and reset procedures 331 include CKP variation learn, calibration P/N, EVAP service bay test, injector balance, output controls, and VIN.
In some cases, when a particular functional test or reset procedure from the other available functional tests and reset procedures 331 is selected to be performed on the vehicle 9, display device 4 may send a message to server 2 indicating the selected test or reset procedure as well as the at least one symptom identifier 302. Such a message may help server 2 learn to associate the selected functional test or reset procedure with the at least one symptom identifier 302 for future requests.
As previously noted, reset procedures may be included within functional tests or provided in a separate section. In some cases, reset procedures may only be displayed as part of the symptom-based subset of reset procedures or the other available reset procedures after a particular service operation has been completed on vehicle 9. In some cases, server 2 may identify the particular service operation (e.g., installation of a vehicle component) for which a particular reset procedure should be displayed. Display device 4 may then monitor the vehicle 9 for completion of the particular service operation in order to determine when to display the particular reset procedure within the display interface.
Next,
Additionally, the display interface 300 may also show all available component tests 341, which may include any available component that were not identified for the symptom-based subset. The other available component tests 341 may be displayed within component test card 340, or as part of a separate window. In this case, the other available component tests 341 include component tests for the anti-lock brakes (ABS), body electrical, charging system, fuel injection, transfer case, and transmission.
When a particular component test is selected from either the symptom-based subset or the other available component tests, display device 4 may send a message to another device such as a multimeter or oscilloscope to perform the selected component test. In some cases, when a particular component test from the other available component tests 331 is selected to be performed on the vehicle 9, display device 4 may send a message to server 2 indicating the selected component test as well as the at least one symptom identifier 302. Such a message may help server 2 learn to associate the selected component tests with the at least one symptom identifier 302 for future requests.
In additional examples, functional tests, reset procedures, and/or component tests displayed within a symptom-based subset may be arranged within display interface 300 based on information received by display device 4 from server 2. In one example, tests may be arranged based on associated vehicle component. For instance, two symptom-based functional tests may relate to a first vehicle component while a different two symptom-based functional tests may relate to a second vehicle component. In that case, the display interface 300 may indicate to which component each functional test relates. Additionally, the functional tests may be ordered on the display interface 300 according to which component they relate. For instance, server 2 may indicate that the first vehicle component has a higher probability of failure based on the at least one symptom identifier 304 than the second vehicle component. In that case, the two symptom-based functional tests related to the first vehicle component may be displayed before the two symptom-based functional tests related to the second vehicle component.
In a further example, functional tests, reset procedures, and/or component tests may be ordered according to a ranking based on performance frequency. For instance, a symptom-based subset of component tests may include three component tests. Server 2 may provide a ranking of the three component tests based on how often each of the component tests has been applied in the past for vehicles having identifying information 304 and the at least one symptom identifier 302. The component tests may then be ordered on display interface 300 according to the provided ranking. The display interface 300 may additionally display a numerical ranking of each of the three component tests.
Next,
In some examples, when PIDs and/or tests are unavailable for display device 4 from server 2, display device 4 may have access to one or more default filter lists stored within memory on display device 4. The default filter lists may include default PID filter lists, default functional test filter lists, and/or default component test filter lists. In some examples, the default filter lists may indicate PIDs and/or tests to display regardless of the at least one symptom identifier 302. In other examples, different default filter lists may be associated with different symptom identifiers. For instance, the default filter lists may be cached versions of symptom-based filter lists previously provided to the display device 4 by server 2. When one or more default filter lists are available within local memory of display device 4, the display interface 300 may be considered to be in a partially degraded state.
In further examples, display device 4 may not be able to receive filter lists from server 2 and may also lack default filter lists within local memory. In this case, the display interface 300 may be considered to be in a fully degraded state. In this state, any available PIDs, functional tests, and/or component tests may be displayed within display interface 300. A technician may then be provided with a prompt to select PIDs to display and/or tests to perform. An additional prompt may be provided to allow for the entry of baseline ranges corresponding to different PIDs.
In additional examples, display interface 300 may be in a hybrid state in which certain types of symptom-based information are available, but not other types. For instance, a symptom-based subset of PIDs for a particular symptom identifier may be displayed. However, symptom-based functional tests and component tests may be unavailable. In that case, all available functional tests and component tests may be displayed via display interface 300.
In further examples, the state of display interface 300 may be based on other factors besides network connectivity. For instance, different levels of subscriptions to different types of filter lists may be available. In that case, a current subscription of a user may be used to determine what information is displayed via display interface 300.
Next,
Display device 4 may receive index values 351 from server 2 that make up a PID filter list. The index values 351 may represent entries from the ordered list 350 of PIDs stored within memory of display device 4. Display device 4 may select PIDs from the ordered list 350 that correspond to index values 351 in order to determine a symptom-based subset 352 of PIDs to display within display interface 300. In this manner, a minimal amount of information may be transmitted over a network connection between server 2 and display device 4. Display device 4 may locally store information about individual PIDs as part of ordered list 350. For example, this stored information may include full PID descriptors to display within display interface 300. The stored information may also include instructions for requesting corresponding PID values from vehicle 9.
In further examples, an ordered list of functional tests stored on display device 4 may be the same as a corresponding ordered list of functional tests stored at server 2. A functional test filter list received by display device 4 from server 2 may include index values that represent entries from the ordered list of functional tests. The functional test filter list may be applied by display device 4 to determine a symptom-based subset of functional tests for display to a technician.
In additional examples, an ordered list of reset procedures stored on display device 4 may be the same as a corresponding ordered list of reset procedures stored at server 2. A reset procedure filter list received by display device 4 from server 2 may include index values that represent entries from the ordered list of reset procedures. The reset procedure filter list may be applied by display device 4 to determine a symptom-based subset of reset procedures for display to a technician.
In further examples, an ordered list of component tests stored on display device 4 may be the same as a corresponding ordered list of component tests stored at server 2. A component test filter list received by display device 4 from server 2 may include index values that represent entries from the ordered list of component tests. The component test filter list may be applied by display device 4 to determine a symptom-based subset of component tests for display to a technician.
In yet further examples, a single ordered list may include multiple types of entries, including any combination of PIDs, functional tests, reset procedures, and component tests. A diagnostic filter list sent by server 2 to display device 4 may then include index values for multiple types of entries. For instance, the diagnostic filter list may include index values corresponding to both PIDs and component tests. In that case, the diagnostic filter list may be applied by display device 4 to determine both a symptom-based subset of PIDs and a symptom-based subset of component tests for display.
Next,
Block 361 includes determining identifying information for a vehicle to be serviced. The identifying information may define a particular set of vehicles in any of the manners described herein, including but not limited to a year, make, model, and/or engine. In some examples, the identifying information may be received from vehicle 9. In other examples, the identifying information may be received in a different manner. For instance, the identifying information may be entered via display interface 300 or captured from a repair order. The vehicle may be serviced as part of a repair procedure, a maintenance procedure, or a different type of service procedure.
Next, block 362 includes receiving at least one symptom identifier for the vehicle. In some examples, the at least one symptom identifier may be a single DTC. In further examples, the at least one symptom identifier may include two or more DTCs. One or more DTCs may be received by display device 4 from vehicle 9. In other examples, the at least one symptom identifier may be a different type of identifier. For example, the at least one symptom identifier may be entered via display interface 300 (e.g., by selecting one or more vehicle symptoms from a predetermined drop-down list). In another example, the at least one symptom identifier may be captured from a repair order.
Next, block 363 includes sending a request over a communication network to a remote server for a PID filter list for the vehicle. The request may include the identifying information for the vehicle and the at least one symptom identifier for the vehicle. The request may be transmitted over a wireless or wired connection. In some examples, the request may be for a functional test filter list, a reset procedure filter list, and/or a component test filter list in addition to or instead of a request for a PID filter list.
Next, block 364 includes receiving a response to the request over the communication network from the remote server. The response may include the PID filter list for the vehicle. In some examples, the PID filter list may include index values into an ordered list of PIDs stored in a memory of display device 4. In other examples, the PID filter list may include another type of PID identifier and/or descriptor.
In further examples, the response may include a functional test filter list, a reset procedure filter list, and/or a component test filter list in addition to or instead of a PID filter list. In some examples, a single filter list may identify multiple types of diagnostic information. For instance, a single filter list may identify both PIDs and tests. In one example, an ordered list of diagnostic information may be stored in memory of display device 4 that includes both PIDs and tests. The filter list may then include index values into the ordered list that identify at least one PID and at least one test.
Next, block 365 includes determining, based on the PID filter list for the vehicle, a symptom-based subset of PIDs for the vehicle from a set of available PIDs. The set of available PIDs may be all PIDs available for a vehicle having particular identifying information. In other examples, the set of available PIDs may include PIDs for multiple sets of vehicles each having different identifying information. In one example, the symptom-based subset of PIDs may be determined by selecting PIDs from an ordered list of PIDs stored on display device 4.
In further examples, a symptom-based subset of functional tests may be determined from a set of available functional tests as well or instead. In additional examples, a symptom-based subset of reset procedures may be determined from a set of available reset procedures as well or instead. In further examples, a symptom-based subset of component tests may be determined from a set of available component tests as well or instead.
Next, block 366 includes displaying, on a display interface, the symptom-based subset of PIDs for the vehicle. In particular, corresponding descriptors for PIDs within the subset may be displayed within a PID card. When the PID card is selected, the PID card may switch to a dynamic mode in which live PID values are displayed for the PIDs within the subset. In further examples, an indication of a component to which PIDs within the subset pertain may also be displayed within the display interface. In additional examples, certain PIDs within the subset may pertain to a particular vehicle component and other PIDs within the subset may pertain to one or more related components. In that case, PIDs may be categorized within the display interface based on which component or system they relate to.
In further examples, a symptom-based subset of functional tests, a symptom-based subset of reset procedures, and/or a symptom-based subset of component tests may be displayed as well or instead. When a functional test or reset procedure is selected, instructions may be provided by display device 4 to vehicle 9 to perform the selected functional test or reset procedure. When a component test is selected, instructions may be sent to a multimeter or oscilloscope to perform the selected component test on vehicle 9.
The server 2, the display device 4, and the RO device 10 comprise a computing system. The server 2, the display device 4, and/or the RO device 10 can comprise any of the components of an example computing system 450 shown in
In a basic configuration 451, the computing system 450 can include one or more processors 452 and a system memory 454. A memory bus 459 can be used for communicating between the processor 452 and the system memory 454. Depending on the desired configuration, the processor 452 can be of any type including but not limited to a microprocessor (μP), a microcontroller (μC), a digital signal processor (DSP), or any combination thereof. A memory controller 453 can also be used with the processor 452, or in some implementations, the memory controller 453 can be an internal part of the processor 452.
Depending on the desired configuration, the system memory 454 can be of any type including but not limited to volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.) or any combination thereof. The system memory 454 can include one or more applications 455, and program data 457. The application 455 can include an algorithm 456 that is arranged to perform the functions described as being performed by the server 2, the display device 4, or the RO device 10. The program data 457 can include system data 458 that could be directed to any number of types of data, such as one more of the following types of data: the index 61, the mapping data 62, the RO data 63, the diagnostic session data 64, the diagnostic list 65, the threshold 66, and/or the component hierarchy 67. In some example embodiments, the applications 455 can be arranged to operate with the program data 457 on an operating system executable by the processor 452.
The computing system 450 can have additional features or functionality, and additional interfaces to facilitate communications between the basic configuration 451 and any devices and interfaces. For example, data storage devices 460 can be provided including removable storage devices 461, non-removable storage devices 462, or a combination thereof. Examples of removable storage and non-removable storage devices include magnetic disk devices such as flexible disk drives and hard-disk drives (HDD), optical disk drives such as compact disc (CD) drives or digital versatile disk (DVD) drives, solid state drives (SSD), and tape drives to name a few. Computer storage media can include volatile and nonvolatile, non-transitory, removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable program instructions, data structures, program modules, or other data such as the data stored in a computer-readable memory, such at the memory 52.
The system memory 454 and the storage devices 460 are examples of computer-readable medium, such as the memory 52. The system memory 454 and the storage devices 460 can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computing system 450.
For the display device 4 and the RO device 10, the computing system 450 can include or be implemented as a portion of a small-form factor portable (i.e., mobile) electronic device such as a smartphone (e.g., an IPHONE® smartphone from Apple Inc. of Cupertino, California, or a GALAXY S® smartphone from Samsung Electronics Co., Ltd. Of Maetan-Dong, Yeongtong-Gu Suwon-Si, Gyeonggi-Do, Republic of Korea), a tablet device (e.g., an IPAD® tablet device from Apple Inc., or a SAMSUNG GALAXY TAB tablet device from Samsung Electronics Co., Ltd.), or a wearable computing device (e.g., a wireless web-watch device or a personal headset device). The application 455, or the program data 457 can include an application downloaded to the communication interfaces 467 from the APP STORE® online retail store, from the GOOGLE PLAY® online retail store, or another source of the applications or the CRPI described herein for use on the display device and the RO device 10.
Additionally or alternatively, the computing system 450 can include or be implemented as part of a personal computing system (including both laptop computer and non-laptop computer configurations), or a server. In some embodiments, the disclosed methods can be implemented as CRPI encoded on a non-transitory computer-readable storage media in a machine-readable format, or on other non-transitory media or articles of manufacture.
The computing system 450 can also include output interfaces 463 that can include a graphics processing unit 464, which can be configured to communicate to various external devices such as display devices 466 or speakers via one or more A/V ports 465 or a communication interface 467. The communication interface 467 can include a network controller 468, which can be arranged to facilitate communications with one or more other computing systems 470 over a network communication via one or more communication ports 469. The communication connection is one example of a communication media. Communication media can be embodied by computer-readable program instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. A modulated data signal can be a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media can include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared (IR) and other wireless media.
In one embodiment, the example computer program product 480 is provided using a signal bearing medium 481. The signal bearing medium 481 can include one or more programming instructions 482 that, when executed by one or more processors can provide functionality or portions of the functionality described above with respect to
The one or more programming instructions 482 can be, for example, computer executable and/or logic implemented instructions. In some examples, a computing system such as the computing system 450 of
The processor 50 can be configured like the processor 452. The memory 52 can be configured as part of or all of the system memory 454 or the storage devices 460. The communication interface 51 can be configured as part of or all of the communication interfaces 467.
Each of the server 2, the display device 4, and the computing system 450 can comprise a power source. In accordance with the example embodiments, a power source can include a connection to an external power source and circuitry to allow current to flow to other elements connected to the power source. As an example, the external power source can include a wall outlet at which a connection to an alternating current can be made. As another example, the external power source can include an energy storage device (e.g., a battery) or an electric generator.
Additionally or alternatively, a power source can include a connection to an internal power source and power transfer circuitry to allow current to flow to other elements connected to the power source. As an example, the internal power source can include an energy storage device, such as a battery. Furthermore, any power source described herein can include various circuit protectors and signal conditioners. The power sources described herein can provide a way to transfer electrical currents to other elements that operate electrically.
It should be understood that the arrangements described herein and/or shown in the drawings are for purposes of example only. As such, those skilled in the art will appreciate that other arrangements and elements (e.g., machines, interfaces, functions, orders, and/or groupings of functions) can be used instead, and some elements can be omitted altogether according to the desired results. Furthermore, various functions described and/or shown in the drawings as being performed by one or more elements can be carried out by a processor executing computer-readable program instructions or by a combination of hardware, firmware, and/or software. For purposes of this description, execution of CRPI contained in some computer-readable medium to perform some function can include executing all of the program instructions of those CRPI or only a portion of those CRPI.
The term “data” within this description can be used interchangeably with the term “information” or similar terms, such as “content.” The data described herein can be transmitted and received. As an example, any transmission of the data described herein can occur directly from a transmitting device (e.g., a transmitter) to a receiving device (e.g., a receiver). As another example, any transmission of the data described herein can occur indirectly from the transmitter to a receiver via one of one or more intermediary network devices, such as an access point, an antenna, a base station, a hub, a modem, a relay, a router, a switch, or some other network device. The transmission of any of the data described herein can include transmitting the data over an air interface (e.g., using radio signals (i.e., wirelessly)). The transmission of any of the data described herein can include transmitting the data over a wire (e.g., a single wire, a twisted pair of wires, a fiber optic cable, a coaxial cable, a wiring harness, a power line, a printed circuit, a CAT5 cable, or CAT6 cable). The wire can be referred to as a “conductor” or by another term. As an example, transmission of the data over the conductor can occur electrically or optically.
The data can represent various things such as objects and conditions. The objects and conditions can be mapped to a data structure (e.g., a table). A processor can refer to the data structure to determine what object or condition is represented by the data. As an example, the data received by a processor can represent a calendar date. The processor can determine the calendar date by comparing the data to a data structure that defines calendar dates. As another example, data received by a processor can represent a vehicle component. The processor can determine what type of vehicle component is represented by the data by comparing the data to a structure that defines a variety of vehicle components.
While various aspects and embodiments are described herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and are not intended to be limiting, with the true scope being indicated by the claims, along with the full scope of equivalents to which such claims are entitled. It is also to be understood that the terminology used herein for the purpose of describing particular embodiments only, and is not intended to be limiting.
In this description, the articles “a,” “an,” and “the” are used to introduce elements and/or functions of the example embodiments. The intent of using those articles is that there is one or more of the introduced elements and/or functions.
In this description, the intent of using the term “and/or” within a list of at least two elements or functions and the intent of using the terms “at least one of” and “one or more of” immediately preceding a list of at least two components or functions is to cover each embodiment including a listed component or function independently and each embodiment comprising a combination of the listed components or functions. For example, an embodiment described as comprising “A, B, and/or C,” or “at least one of A, B, and C,” or “one or more of A, B, and C” is intended to cover each of the following possible embodiments: (i) an embodiment comprising A, but not B and not C, (ii) an embodiment comprising B, but not A and not C, (iii) an embodiment comprising C, but not A and not B, (iv) an embodiment comprising A and B, but not C, (v) an embodiment comprising A and C, but not B, (v) an embodiment comprising B and C, but not A, and (vi) an embodiment comprising A, B, and C. For the embodiments comprising component or function A, the embodiments can comprise one A or multiple A. For the embodiments comprising component or function B, the embodiments can comprise one B or multiple B. For the embodiments comprising component or function C, the embodiments can comprise one C or multiple C. The use of ordinal numbers such as “first,” “second,” “third” and so on is to distinguish respective elements rather than to denote a particular order of those elements unless the context of using those terms explicitly indicates otherwise.
Embodiments of the present disclosure may thus relate to one of the enumerated example embodiment (EEEs) listed below.
This application is a continuation application of U.S. patent application Ser. No. 16/290,422 filed on Mar. 1, 2019 and published on Jun. 27, 2019 as United States Patent Application Publication No 2019/0197800 A1. U.S. patent application Ser. No. 16/290,422 is a continuation application of U.S. patent application Ser. No. 15/236,060 filed on Aug. 12, 2016 and issued on Apr. 23, 2019 as U.S. Pat. No. 10,269,191. United States Patent Application Publication No 2019/0197800 A1 and U.S. Pat. No. 10,269,191 are incorporated herein by reference, as if fully set forth in this description.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5058044 | Stewart et al. | Oct 1991 | A |
| 5553235 | Chen et al. | Sep 1996 | A |
| 5916286 | Seashore et al. | Jun 1999 | A |
| 6055468 | Kaman et al. | Apr 2000 | A |
| 6084870 | Wooten et al. | Jul 2000 | A |
| 6236917 | Liebl et al. | May 2001 | B1 |
| 6301531 | Pierro et al. | Oct 2001 | B1 |
| 6330499 | Chou et al. | Dec 2001 | B1 |
| 6336065 | Gibson et al. | Jan 2002 | B1 |
| 6484080 | Breed | Nov 2002 | B2 |
| 6604033 | Banet et al. | Aug 2003 | B1 |
| 6609050 | Li | Aug 2003 | B2 |
| 6609051 | Fiechter et al. | Aug 2003 | B2 |
| 6708092 | Starks et al. | Mar 2004 | B1 |
| 6768935 | Morgan et al. | Jul 2004 | B1 |
| 6845307 | Rother | Jan 2005 | B2 |
| 6877017 | Beom | Apr 2005 | B1 |
| 6879894 | Lightner et al. | Apr 2005 | B1 |
| 6956501 | Kitson | Oct 2005 | B2 |
| 6959235 | Abdel-Malek et al. | Oct 2005 | B1 |
| 7020546 | Nagai et al. | Mar 2006 | B2 |
| 7082359 | Breed | Jul 2006 | B2 |
| 7379801 | Heffington | May 2008 | B2 |
| 7634351 | Diem | Dec 2009 | B2 |
| 7734287 | Ying | Jun 2010 | B2 |
| 7751955 | Chinnadurai et al. | Jul 2010 | B2 |
| 7945358 | Avery et al. | May 2011 | B2 |
| 7953530 | Pederson et al. | May 2011 | B1 |
| 8024084 | Breed | Sep 2011 | B2 |
| 8036788 | Breed | Oct 2011 | B2 |
| 8055403 | Lowrey et al. | Nov 2011 | B2 |
| 8135509 | Thompson et al. | Mar 2012 | B1 |
| 8160767 | Thompson et al. | Apr 2012 | B1 |
| 8370018 | Andreasen et al. | Feb 2013 | B2 |
| 8423226 | Underdal et al. | Apr 2013 | B2 |
| 8433472 | Singh et al. | Apr 2013 | B2 |
| 8560164 | Nielsen et al. | Oct 2013 | B2 |
| 8666588 | Geilen et al. | Mar 2014 | B2 |
| 8694328 | Gormley | Apr 2014 | B1 |
| 8930067 | Green et al. | Jan 2015 | B1 |
| 9117319 | Chen et al. | Aug 2015 | B2 |
| 9342934 | Chen | May 2016 | B2 |
| 9773358 | Berglund et al. | Sep 2017 | B2 |
| 10269191 | Lewis et al. | Apr 2019 | B2 |
| 10769870 | Lewis et al. | Sep 2020 | B2 |
| 20020007237 | Phung et al. | Jan 2002 | A1 |
| 20020007289 | Malin et al. | Jan 2002 | A1 |
| 20020059020 | Abe et al. | May 2002 | A1 |
| 20020073000 | Sage | Jun 2002 | A1 |
| 20040172177 | Nagai et al. | Sep 2004 | A1 |
| 20050027403 | Nagai | Feb 2005 | A1 |
| 20050096806 | Diem | May 2005 | A1 |
| 20060020477 | Retzbach et al. | Jan 2006 | A1 |
| 20060030981 | Robb et al. | Feb 2006 | A1 |
| 20060136104 | Brozovich et al. | Jun 2006 | A1 |
| 20060142907 | Cancilla et al. | Jun 2006 | A1 |
| 20060184383 | Davis et al. | Aug 2006 | A1 |
| 20070100520 | Shah et al. | May 2007 | A1 |
| 20070294003 | Underdal et al. | Dec 2007 | A1 |
| 20080161989 | Breed | Jul 2008 | A1 |
| 20080243488 | Balmelli et al. | Oct 2008 | A1 |
| 20080294303 | King et al. | Nov 2008 | A1 |
| 20090204287 | Blanz et al. | Aug 2009 | A1 |
| 20090216401 | Underdal et al. | Aug 2009 | A1 |
| 20090259358 | Andreasen | Oct 2009 | A1 |
| 20090271239 | Underdal et al. | Oct 2009 | A1 |
| 20100010702 | Gilbert | Jan 2010 | A1 |
| 20100138701 | Constantino | Jun 2010 | A1 |
| 20100262332 | Gilbert | Oct 2010 | A1 |
| 20100324777 | Tominaga et al. | Dec 2010 | A1 |
| 20110035094 | Van Den Berg et al. | Feb 2011 | A1 |
| 20120035803 | Singh et al. | Feb 2012 | A1 |
| 20120041635 | Johnson et al. | Feb 2012 | A1 |
| 20120116630 | Howell et al. | May 2012 | A1 |
| 20120232743 | Singh | Sep 2012 | A1 |
| 20130054082 | Costantino | Feb 2013 | A1 |
| 20130204485 | Chen | Aug 2013 | A1 |
| 20130204640 | Underdal et al. | Aug 2013 | A1 |
| 20130304278 | Chen | Nov 2013 | A1 |
| 20130304306 | Selkirk et al. | Nov 2013 | A1 |
| 20130317694 | Merg | Nov 2013 | A1 |
| 20140025253 | Rybak et al. | Jan 2014 | A1 |
| 20140074344 | Amirpour et al. | Mar 2014 | A1 |
| 20140075356 | Gray et al. | Mar 2014 | A1 |
| 20140207515 | Merg et al. | Jul 2014 | A1 |
| 20140207771 | Merg | Jul 2014 | A1 |
| 20140277902 | Koch | Sep 2014 | A1 |
| 20140277908 | Fish et al. | Sep 2014 | A1 |
| 20140279707 | Joshua et al. | Sep 2014 | A1 |
| 20150105972 | Madison et al. | Apr 2015 | A1 |
| 20150121275 | Marshall et al. | Apr 2015 | A1 |
| 20150218872 | Breed | Aug 2015 | A1 |
| 20150331686 | Petersen et al. | Nov 2015 | A1 |
| 20150371457 | Bakfan et al. | Dec 2015 | A1 |
| 20160005242 | Hua et al. | Jan 2016 | A1 |
| 20160071334 | Johnson et al. | Mar 2016 | A1 |
| 20160086397 | Phillips | Mar 2016 | A1 |
| 20160093122 | Chen | Mar 2016 | A1 |
| 20160189440 | Cattone | Jun 2016 | A1 |
| 20170039059 | Gintz et al. | Feb 2017 | A1 |
| 20170098200 | Merg et al. | Apr 2017 | A1 |
| 20170103101 | Mason | Apr 2017 | A1 |
| 20170116793 | Lin et al. | Apr 2017 | A1 |
| 20170132576 | Merg et al. | May 2017 | A1 |
| 20170337584 | Najdecki et al. | Nov 2017 | A1 |
| 20170345227 | Allen, Jr. et al. | Nov 2017 | A1 |
| 20180047222 | Lewis et al. | Feb 2018 | A1 |
| 20180047223 | Lewis et al. | Feb 2018 | A1 |
| 20180075671 | Lewis et al. | Mar 2018 | A1 |
| 20180075672 | Lewis et al. | Mar 2018 | A1 |
| 20190197800 | Lewis et al. | Jun 2019 | A1 |
| 20200273266 | Lewis et al. | Aug 2020 | A1 |
| 20200302711 | Lewis et al. | Sep 2020 | A1 |
| 20200364958 | Lewis et al. | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 101477336 | Jul 2009 | CN |
| 101566837 | Oct 2009 | CN |
| 101981593 | Feb 2011 | CN |
| 101986124 | Mar 2011 | CN |
| 102708134 | Oct 2012 | CN |
| 104488004 | Apr 2015 | CN |
| 105453141 | Mar 2016 | CN |
| 106200618 | Dec 2016 | CN |
| 10235416 | Feb 2004 | DE |
| 102014008490 | Nov 2014 | DE |
| 1079053 | Feb 2001 | EP |
| 1868146 | Dec 2007 | EP |
| 2112492 | Oct 2009 | EP |
| 2112495 | Oct 2009 | EP |
| 2239699 | Oct 2010 | EP |
| 2608055 | Jun 2013 | EP |
| 2787711 | Oct 2014 | EP |
| 2887621 | Jun 2015 | EP |
| 2249398 | May 1992 | GB |
| 2489820 | Oct 2012 | GB |
| 2001202125 | Jul 2001 | JP |
| 2011059023 | Mar 2011 | JP |
| 2012212199 | Nov 2012 | JP |
| 0217118 | Feb 2002 | WO |
| 2004092918 | Oct 2004 | WO |
| 2004101322 | Nov 2004 | WO |
| 2006105930 | Oct 2006 | WO |
| 2009133667 | Nov 2009 | WO |
| 2014001799 | Jan 2014 | WO |
| 2014005771 | Jan 2014 | WO |
| 2017131568 | Aug 2017 | WO |
| Entry |
|---|
| European Patent Office; Communication pursuant to Article 94(3) EPC for European Patent Application No. 17 768 267.1-1009; dated Jan. 3, 2023; 5 pages. |
| PRC National Intellectual Property Administration; Notice of Completing Formalities for Patent Registration, Notice of Granting Patent Right for Invention, and Search Report for Chinese patent application No. 202110676593.3 dated Jan. 11, 2023. |
| Chinese National Intellectual Property Administration; Office Action for Chinese patent application No. 202110676593.3 dated Aug. 10, 2022. |
| Hu Jie et al. , “Developing PC-Based Automobile Diagnostic System Based on OBD System,” 2010, Publisher: IEEE. |
| C. Sasikumar et al., “Built in Self-Test for Fault Tolerant Real Time In-vehicle Networks through Automotive Diagnostics,” 2011, Publisher: IEEE. |
| Mathias Johanson et al., “Improving Vehicle Diagnostics through Wireless Data Collection and Statistical Analysis,” 2007, Publisher: IEEE. |
| F. Corno et al., Evaluating the effects of transient faults on vehicle dynamic performance in automotive systems, 2004, Publisher: IEEE. |
| Zhao et al., “Design of Fault Diagnosis Testing Centre for Electronic Control Engine,” 2007, Publisher: IEEE. |
| Wang et al. , “Design of Vehicle Bus Data Acquisition and Fault Diagnosis System,” 2011 , Publisher: IEEE. |
| China National Intellectual Property Administration; Office action for Chinese Patent Application No. 201780047365.1 dated Oct. 21, 2020. |
| Auterra, LLC, DashDyno SPD Automotive Computer, Feb. 21, 2011, http://www.auterraweb.com/ (1 page). |
| Jain, A.K., et al., Data Clustering: A Review, ACM Computing Surveys, vol. 31, No. 3, Sep. 1999, pp. 264-323 (60 pages). |
| Seyfert, Karl, OBD II Generic PID Diagnosis, Motor Magazine, Sep. 2007, Troy Michigan (7 pages). |
| Seyfert, Karl, “OBD II includes many helpful diagnostic trouble codes, designed to identify the possible causes of hundreds of potential system faults. But can it correctly identify a loose nut behind the wheel?”, Motor Magazine, Oct. 2015, Troy, Michigan, pp. 4 and 6 (2 pages). |
| Seyfert, Karl, “OBD II's self-diagnostic capabilities have been a real boon to repair on many vehicles. But the systems on some early vehicles can really throw you a curve.”, Motor Magazine, Jun. 2005, Troy, Michigan, pp. 6 and 8 (2 pages). |
| Muller, Tobias Carsten, et al., A Heuristic Approach for Offboard-Diagnostics in Advanced Automotive Systems, SAE World Congress 2009, Apr. 20, 2009, Detroit, MI, SAE Doc. No. 2009-01-1027 (9 pages). |
| Sankavaram, Chaitanya, et al., Event-driven Data Mining Techniques for Automotive Fault Diagnosis, 21st International Workshop on Principles of Diagnosis, Oct. 13-16, 2010, pp. 1-8 (8 pages). |
| Singh, Satnam, et al., Data-Driven Framework for Detecting Anomalies in Field Failure Data, Aerospace Conference, 2011 IEEE, updated Jan. 3, 2011, pp. 1-14 (14 pages). |
| Weyer, Jake, Identifix Leader Charts New Course, Jan. 1, 2016, downloaded from World Wide Web at http://ratchetandwrench.com/core/pagetools.php?pageid=22705&uri=%2FRatchetWrench%2FJanuary-2016%2Fidentifix-Leader-Charts-New-Course%2F . . . , Apr. 21, 2016 (2 pages). |
| Zhang, Yilu, et al., Remote Vehicle State of Health Monitoring and its Application to Vehicle No-Start Prediction, AUTEST 2009, Anaheim, CA, Sep. 2009, IEEE, pp. 88-93 (6 pages). |
| U.S. Appl. No. 15/236,123, inventors: Bradley R. Lewis, Patrick S. Merg, Roy S. Brozovich, Jacob G. Foreman, Joshua C. Covington, Brett A. Kelley, and Steven E. Miskovic; filed Aug. 12, 2016. |
| International Search Report, International Application No. PCT/US2017/046215, dated Nov. 22, 2017 (5 pages). |
| Written Opinion of the International Searching Authority, International Application No. PCT/US2017/046215, dated Nov. 22, 2017 (9 pages). |
| Hu et al., The Development of Vehicle Diagnostic System Based on Android Platform, International Conference on Connected Vehicles and Expo (ICCVE), 2015, pp. 42-47 (6 pages). |
| U.S. Appl. No. 15/815,574, inventors Bradley R. Lewis, Patrick S. Merg, Roy S. Brozovich, Jacob G. Foreman, Joshua C. Covington, Brett A. Kelley, and Steven E. Miskovic, filed Nov. 16, 2017. |
| U.S. Appl. No. 15/815,466, inventors Bradley R. Lewis, Patrick S. Merg, Roy S. Brozovich, Jacob G. Foreman, Joshua C. Covington, Brett A. Kelley, and Steven E. Miskovic, filed Nov. 16, 2017. |
| European Patent Office; Communication pursuant to Article 94(3) EPC for European Application No. 17 768 267.1-1009 dated Feb. 11, 2021. |
| Number | Date | Country | |
|---|---|---|---|
| 20200364958 A1 | Nov 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16290422 | Mar 2019 | US |
| Child | 16944093 | US | |
| Parent | 15236060 | Aug 2016 | US |
| Child | 16290422 | US |
