Patent Application
20240192833
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), though in other instances, technicians and/or other professionals (or non-professionals) who are servicing the vehicle can do so at other locations, such as on the road. The technicians can use any of a variety of computerized tools and/or non-computerized tools to service (e.g., repair) any of the wide variety of mechanical vehicle components on a vehicle. While servicing a vehicle, a technician may desire to see information related to various vehicle components, such as circuits in a wiring harness of the vehicle, so that the technician can more accurately and quickly diagnose the vehicle.
Several example embodiments that relate to interactive vehicle diagnostic displays are described herein.
Viewed from one aspect, an example embodiment takes the form of a method comprising: (a) receiving, by at least one processor connected to a display, a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information, (b) displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers, (c) receiving, by the at least one processor while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol, (d) displaying, on the display in response to receiving the first input, the set of selectable identifiers, (e) receiving, by the at least one processor while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers, and (f) displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
Viewed from another aspect, an example embodiment takes the form of a system comprising: a display, at least one processor, and data storage comprising instructions executable by the at least one processor to cause the system to perform operations comprising: (a) receiving a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information, (b) displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers, (c) receiving, while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol, (d) displaying, on the display in response to receiving the first input, the set of selectable identifiers, (e) receiving, while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers, and (f) displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
Viewed from yet another aspect, an example embodiment takes the form of a non-transitory computer readable medium having stored thereon instructions that, upon execution by a computing system, cause the computing system to perform operations comprising: (a) receiving, by at least one processor of the computing system connected to a display of the computing system, a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information, (b) displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers, (c) receiving, by the at least one processor while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol, (d) displaying, on the display in response to receiving the first input, the set of selectable identifiers, (e) receiving, by the at least one processor while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers, and (f) displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
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 interactive vehicle diagnostic displays. The example embodiments can include a first device, such as a client computing system (or more simply, “client” or “CCS”), receiving from a second device, such as a server computing system (or more simply, “server” or “SCS”), a download including data for enabling a user of the CCS (e.g., a technician) to view at least one vehicle component as well as supplemental information associated with each vehicle component. For instance, in accordance with the example embodiments, the download can include (i) an image representative of a vehicle component (e.g., an image of a wiring harness), (ii) symbol data associated with a first symbol, (iii) a set of one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, where each selectable identifier of the set can indicate (e.g., identify) a respective portion of the supplemental information associated with the vehicle component. Supplemental information can include diagnostic information and/or other types of information.
As such, one or more of the example embodiments can comprise, after receiving the download, the CCS displaying the image and the first symbol, without displaying any other information associated with the vehicle component that was included in the download. While displaying the image and the first symbol, the CCS can next receive user-input corresponding to user selection of the first symbol, and can responsively display the set of selectable identifiers. Then, while displaying the set of selectable identifiers, the CCS can receive another user-input corresponding to user selection of one of the selectable identifiers and can responsively display the portion of supplemental information indicated by the selected identifier.
A download received at a CCS can comprise a variety of download content (or more simply “content”). In general, the content of the download can comprise, for example, images, symbol data, supplemental information associated with a vehicle component, identifiers of respective portions of the supplemental information, and/or links to additional download content. For example, a download received at the CCS can include enough data for enabling the technician to seamlessly and efficiently view information associated with the vehicle component without necessitating download of additional information associated with the vehicle component. As another example, a download received at the CCS can include (i) a subset of the images, symbol data, identifiers, and/or supplemental information associated with a vehicle component, and (ii) a hyperlink or other mechanism for providing the SCS with a request for additional information associated with the vehicle component.
Other examples of interactive vehicle diagnostic displays are possible as well.
Although a CCS (including its user interface, such as a display) is described primarily herein as an entity separate from a vehicle, it should be noted that, in some embodiments, the CCS could be included as a component of a vehicle, such as the vehicle having the vehicle component or a different vehicle. In such embodiments, a driver of the vehicle, a technician, or the like can view diagnostics for the vehicle component on the vehicle itself or on a different vehicle.
A CCS, such as CCS 2, can take various forms. For example, a CCS can be a specialty computing system, or “specialty CCS”, specifically configured in whole or in part for the purpose of servicing vehicles. A specialty CCS can include unique elements for facilitating servicing of vehicles or can otherwise be uniquely configured in such a way that distinguishes the specialty CCS from another type of computing system. A specialty CCS can be configured to perform various functions associated with servicing vehicles, can include communication interfaces with other systems/servers/networks associated with servicing vehicles, and can be configured to send and receive data over those interfaces in accordance with one or more protocols associated with servicing vehicles. Alternatively, a CCS can be a general purpose, non-specialty computing system, such as a general purpose smart phone, desktop computer, laptop computer, or the like.
As a general matter, a CCS—specialty or general purpose—can take the form of a hand-held device, laptop computer, desktop computer, and/or another type of device.
In line with the discussion above, a SCS, such as SCS 4, can take various forms as well, such as a specialty SCS specifically/uniquely configured for the purpose of servicing vehicles, or a general-purpose SCS.
A vehicle, such as vehicle 8, is a mobile machine that can be used to transport a person, people, and/or cargo. Any vehicle described herein can be driven and/or otherwise guided along a path (e.g., a paved road or otherwise) on land, in water, in the air, and/or outer space. Any vehicle described herein can be wheeled, tracked, railed, and/or skied. Any vehicle described 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, and/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. Any vehicle described herein can include and/or use any appropriate voltage and/or current source, such as a battery, an alternator, a fuel cell, and the like, providing any appropriate current and/or voltage, such as about 12 volts, about 42 volts, and the like. Any vehicle described herein can include and/or use any desired system and/or engine to provide its mobility. Those systems and/or engines can include vehicle components 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 and/or combinations thereof.
Some vehicles can be identified by characteristics of the vehicle such as when the vehicle was built (e.g., a vehicle year), who built the vehicle (e.g., a vehicle make), 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). This description uses an abbreviation YMME and/or Y/M/M/E, where each letter in the order shown represents a model year, vehicle make, vehicle model name, and engine type, respectively. This description uses an abbreviation YMM and/or Y/M/M, where each letter in the order shown represents a model year, vehicle make, and vehicle model name, respectively. An example Y/M/M/E is 2004/Toyota/Camry/4Cyl, 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 “4Cyl” 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. 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) and/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. The CCS, such as a specialty CCS, can include a transceiver connectable to a vehicle communication link and a processor to transmit and receive vehicle communications via the vehicle communication link.
Any vehicle described herein can include an electronic control unit (ECU), a data link connector (DLC), and a vehicle communication link that connects the DLC to the ECU. An ECU can control various aspects of vehicle operation and/or vehicle 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 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.
The DLC can include an on-board diagnostic (OBD) II 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 can include conductor terminals that connect to a conductor in a vehicle. For instance, the DLC can include connector terminals that connect to conductors that respectively connect to positive and negative terminals of a vehicle battery. The DLC can include one or more conductor terminals that connect to a conductor of the vehicle communication link such that the DLC is communicatively connected to the ECU.
The server 4 can be scaled so as to be able to serve any number of CCSs and/or vehicles, such as one CCS and one vehicle (as shown in
The CCS 2 and/or the vehicle 8 can be located at the same location as one another or remotely from one another at separate, distinct locations. For example, both the CCS 2 and the vehicle 8 can be located at a repair shop. As another example, both the CCS 2 and the vehicle 8 can be located out on the road. As yet another example, the CCS 2 can be located at a repair shop and the vehicle 8 can be located out on the road. One or more of these locations can also include various computerized shop tools (CSTs) and/or non-computerized shop tools, such as a battery charger, torque wrench, brake lathe, fuel pressure gauge, wheel balancer, etc. Further, one or more of the shop tools and/or the CCS 2 can be operable outside of a repair shop. For example, CCS 2 can be operable within the vehicle 8 as the vehicle 8 is driven on roads outside of the repair shop for any of a variety of purposes.
The vehicle 8 can transmit to the CCS 2 various data, such as OBD data (e.g., diagnostic trouble codes (DTCs), measurements read by a shop tool from a VDM, real-time and/or non-real-time electrical measurements (e.g., sensor readings), and/or other types of data. For example, the vehicle 8 can transmit data directly to the CCS 2 over communication link 11. As another example, the vehicle 8 can transmit data indirectly to the CCS 2 by transmitting the data over communication link 12, communication network 6, and communication link 10 to the SCS 4, after which the SCS 4 can transmit the data over communication link 10, communication network 6, and communication link 9 to the CCS 2. The vehicle 8 can perform such an indirect transmission of data with or without specifying the CCS 2 as a destination for the data. For instance, the vehicle 8 (and perhaps other vehicles in communication with the SCS 4) can transmit data to the SCS 4, specifying only the SCS 4 as the destination for the data. Thereafter, CCS 2 can transmit to SCS 4 a request for the data, SCS 4 can assemble the data and transmit the data to the CCS 2 in response to the request.
The CCS 2, the SCS 4, and/or the vehicle 8 can transmit data to (and receive data from) other devices on the communication network 6 as well, such as one or more databases (not shown) to which the CCS 2, the SCS 4, and/or the vehicle 8 have access.
For any given computer device discussed herein, such as the CCS 2, the SCS 4, and/or the vehicle 8, data received by that device can be stored within a computer-readable medium for use by that device. Further, for any given computer device discussed herein, such as the CCS 2, the SCS 4, and/or the vehicle 8, data received by that device can be stored locally in memory at that device and/or can be stored remotely at a storage location accessible by that device (e.g., a remote server or remote database).
One or more CCSs and/or one or more vehicles can be connected by a network established by those devices, such as a vehicle-to-client network, or the like. Such a network can comprise a personal area network (PAN). The PAN can be configured according to any of a variety of standards, protocols, and/or specifications. For example, the PAN can be configured according to a universal serial bus (USB) specification 2.0, 3.0, or 3.1 developed by the USB Implementers Forum. As another example, the PAN can be configured according to an Institute of Electrical and Electronics Engineers (IEEE) standard, such as an IEEE 802.11 standard (e.g., 802.11a, 802.11b, 802.11g, or 802.11n) or an IEEE 802.15 standard (e.g., 802.15.1, 802.15.3, 802.15.4, or 802.15.5) for wireless PAN.
In example operating environment 1, there can be a scenario in which the CCS 2 transmits to the SCS 4 a request for a download of information (e.g., information associated with a vehicle component for a particular vehicle). Such a request can include, for example, a YMM of a particular vehicle and a name of a particular vehicle component. As another example, the request can include a YMME of a particular vehicle and an indication (e.g., a description or code) of a particular symptom associated with a particular vehicle component. As yet another example, the request can include data received from the vehicle for which the information is being requested, and such data can include a vehicle identification number (VIN) of the vehicle, a DTC indicative of a particular vehicle component of the vehicle, an image of a particular vehicle component, among other possibilities. In this scenario, upon receipt of the request, the SCS 4 can assemble the download. For instance, upon receipt of the request, the SCS 4 can retrieve some or all of the CCS-requested information from memory at the SCS 4. Additionally or alternatively, upon receipt of the request, the SCS 4 can in turn transmit to one or more databases located remotely from the SCS 4 a request for some or all of the CCS-requested information and then receive some or all of the CCS-requested information from the one or more databases. Upon assembling the download including the CCS-requested information, the SCS 4 can transmit the download to the CCS 2.
Next,
The user interface 103 can include general user interface elements for performing various manual functions such as sending, via the transceiver 104, requests for a download of information, viewing information corresponding to the requested download, entering data (e.g., tool measurements based on a measurement performed by a measurement tool) to be stored in the CRM 102, manipulating data stored in the CRM 102, and deleting data stored in the CRM 102, among other possibilities. Such general user interface elements can take the form of a keyboard, mouse, touchpad, microphone, etc.
The user interface 103 can also include a display for displaying visual content output by the processor 101 and sent by the processor 101 to the user interface 103. The user interface 103 can display content in the form of a display user interface (DUI). A DUI can, for example, include a graphical user interface and/or text-based user interface. Displaying a DUI can include displaying one or more selector fields (e.g., text boxes, drop-down menus, etc.) at which a user can enter a selection, such as a selection of a visual prompt for requesting a download of information from the SCS 4, upon which the CCS 100 can generate the request and transmit the request via the transceiver 104. The user interface 103 can also include an element for providing audio content output by the processor 101 and sent by the processor 101 to the user interface 103.
A DUI can provide a way to request a download of information from the SCS 4. As an example, displaying a DUI can include displaying an Internet browser or other means for requesting a download of information from the SCS 4. Further, once the CCS 100 receives, via the transceiver 104, the download requested from the SCS 4, a DUI can display some or all of the information included in the download and can enable a user of the CCS 100 to interact with the displayed information. As a more particular example, the DUI can display a wiring diagram associated with vehicle 8 so that a technician can (i) view elements of the wiring diagram (e.g., vehicle components such as sensors, circuits, etc. that are part of the wiring diagram), (ii) select an element of interest of the wiring diagram, (iii) view electrical measurements associated with the selected element, (iv) view identifiers of available related information types for the selected element (e.g., component test information, pricing, and test procedure information), (v) select one or more of the identifiers, and/or (vi) view the related information types for the selected identifier(s). As yet another example, if the technician selects content, such as an element of the wiring diagram, for which related information is not available (due to a lack of licensing for the related information or due to the technician's lack of authorization to view the related information), the DUI can display error handling information.
The display can take various forms, such as a touchscreen, computer monitor, television screen, etc., and can utilize a variety of underlying display technologies, such as CRT, LED, LCD, etc.
The transceiver 104 can communicatively couple to a network, such as the communication network 6, a client-to-vehicle network, or a CST-to-client network. That coupling can be carried out, for example, by connecting the transceiver 104 to a wired communication link of the communication network 6, the client-to-vehicle network, or the CST-to-client network, syncing the transceiver to a wireless network access point, placing a phone call, or in some other manner. The transmitter of the transceiver 104 can transmit various data over the communication network 6, the client-to-vehicle network, or the CST-to-client network such as a request to the SCS 4 for a download of information from the SCS 4 or a request to vehicle 8 for real-time electric measurements from vehicle 8.
The transceiver 104 can include one or more items that allow the CCS 100 to receive various information, such as a download of information assembled by the SCS 4, real-time electrical measurements carried out by or otherwise performed by vehicle 8, tool measurement data (i.e., tool measurements) carried out by a computerized measurement tool (CMT), and/or non-measurement data (e.g., captured vehicle identification information) from a CST. The items of the transceiver 104 can include wires, cables, connectors, electrical circuitry, receivers, transmitters, and/or some other item. As an example, the transceiver 104 can include Universal Serial Bus (USB) connectors and cables for connecting to a CMT having a USB connector. Such USB connectors and cables can be configured according the USB 3.0 standard or another USB standard. As another example, the transceiver 104 can include a radio receiver to receive downloads of information, real-time electrical measurements, tool measurements, and/or non-measurement data transmitted by radio signals from the SCS 4, vehicle 8, a CMT, or a CST. As yet another example, the transceiver 104 can include a modem, a network interface card, and/or a chip mountable on a circuit board. The chip, for example, 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. The transceiver 104 can provide the received measurements and/or non-measurement data to another element of the CCS 100 by way of the connection mechanism 108.
The DLC interface 105 can include one or more DLC interface elements that allow the CCS 100 to communicate with a vehicle over a client-to-vehicle network established between the CCS 100 and a DLC of a vehicle. The DLC interface elements include a transceiver (e.g., an integrated transmitter and receiver, or a distinct transmitter and a distinct receiver). The transmitter of the DLC interface 105 can be configured to transmit data to a vehicle. The data transmitted by the DLC interface 105 to the vehicle may include a request for a VDM. The receiver of the DLC interface 105 can be configured to receive data transmitted by the vehicle 8 over the communication link 11. As an example, the transceiver of the DLC interface 105 can comprise a transceiver such as a system basis chip with high speed CAN transceiver 33989 provided by NXP Semiconductors, Eindhoven, Netherlands. The DLC interface elements of the DLC interface 105 can include a DLC that is configured to connect to the DLC in a vehicle, a wire connector, one or more wires that connect the DLC of the DLC interface 105 to the connection mechanism 108 such that vehicle data messages from the vehicle can be received by the processor 101 and/or another element of the CCS 100. The vehicle data messages or some portion thereof can be stored within the VDMs 114.
The capture device 107 is operable to capture various types of data. As an example, the capture device 107 can comprise a camera to capture an image. As another example, the capture device 107 can comprise an optical scanner to capture data by scanning a multi-dimensional code, such as a two-dimensional bar code and/or a matrix code. The captured data can include any of a variety of data that can be interpreted by the processor 101. The interpretation can include performing optical character recognition and/or comparing a captured media file to a reference media file. As an example, the captured data can comprise data representing the VIN of a vehicle. As another example, the captured data can comprise an image of a VIN plate and/or label on a vehicle, an image of a license plate attached to the vehicle, an image of a vehicle or a portion of a vehicle, an image of a vehicle component, and/or a two-dimensional (2D) machine-readable code (e.g., a QR code). The data captured by the capture device 107 can be stored in the CRM as captured data 115. Further, any or all of the data captured by the capture device 107 can be included in a request for a download of information, as discussed above.
The CRM 102 can include CRPI 109, a client (CCS) identifier 110, vehicle data messages 114, captured data 115, and server data 118. The CRM 102 can receive data stored as the VDMs 114, captured data 115, server data 118, or stored as other data from at least one of the processor 101, the user interface 103, and/or the transceiver 104. The CRPI 109 are executable by the processor 101 to perform functions described herein as being performed by the CCS 100.
The client ID 110 can include an identifier that a processor (e.g., a processor of the SCS 4) can use to distinguish the CCS 100 from at least one other client (e.g., all other clients). As an example, the client ID 110 can include a hardware serial number associated with the CCS 100. As another example, the client ID 110 can include a license number, such as a license number associated with an information product, such as the SHOPKEY® information system available from Snap-on Incorporated, Kenosha, Wisconsin. Additionally or alternatively, the client ID 110 can include an identifier that a processor can use to determine a model type of the CCS 100. For example, the client ID 110 can include a model identifier such as “EEMS330 W” which represents a model type of a client referred to as the VERUS® Edge diagnostic and information system sold by Snap-on Incorporated. The client ID 110 can include a software level identifier associated with software (e.g., the CRPI 109) contained in the CRM 102 and a hardware level identifier associated with items contained within the CCS 100. In line with the discussion above, the request for the download described herein can include the client ID 110 such that the SCS 4 can determine which client to send the download.
Furthermore, the client ID 110 can be associated with or include a labor rate. The labor rate, or the client ID 110 for that matter, can be pre-stored in the CRM 102 or can be input manually by a user of the CCS 100 via the user interface 103. The labor rate can enable the CCS 100 to receive or determine a cost estimate for servicing a particular vehicle component. For example, the SCS 4 can receive the client ID 110 and labor rate from the CCS 100 with the request for the download, can determine a cost estimate for servicing a particular vehicle component based on the labor rate, and can include the determined cost estimate in the download sent to the CCS 100. Alternatively, the SCS 4 can determine an estimated amount of time for servicing the particular vehicle component, and then include the estimated amount of time in the download sent to the CCS 100. Thereafter, the CCS 100 can determine the cost estimate by multiplying the estimated amount of time by the labor rate. This can reduce the burden on the SCS 4 and can possibly eliminate the need to include the labor rate in the request.
The server data 118 can include data the CCS 100 requests from the SCS 4 and received at the transceiver 104 from the SCS 4. For example, the received data can be and/or include the download described herein—namely, the download requested by the CCS 100, prepared by the SCS 4, sent by the SCS 4 to the CCS 100, and received by the CCS 100. Additionally or alternatively, as another example, the received data can include a hyperlink to another download. Other examples are also possible.
In general, the CRPI 109 can include program instructions executable by the processor 101 to cause the CCS 100 to perform any function described herein as being performed by the CCS 100 (e.g., function sets 230 and 390) and/or to cause any item of the CCS 100 to perform any function herein as being performed by that item of the CCS 100. Some particular examples of the CRPI 109 are provided in the following three paragraphs.
The CRPI 109 can include program instructions to cause the processor 101 to receive and process user-input representing a request for a download of information associated with at least one vehicle component. Further, the CRPI 109 can include program instructions to cause the processor 101 to, in response to receiving and processing the user-input representing the request, generate the request for the download of information associated with at least one vehicle component, the request being in a form to be transmitted via transceiver 104. In addition, the CRPI 109 can include program instructions to cause the transceiver 104 to transmit the request via the communication network 6 to the SCS 4, and then cause the transceiver 104 (and thereafter perhaps the processor 101) to receive the download, the download including, for instance (i) an image representative of a vehicle component (e.g., an image of a wiring harness), (ii) symbol data associated with a first symbol, (iii) a set of one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, where each selectable identifier of the set can indicate a respective portion of the supplemental information associated with the vehicle component.
The CRPI 109 can include program instructions to cause the user interface 103 to display a DUI, such as any DUI described in this description. In particular, the CRPI 109 can include program instructions to cause the user interface 103 to, after the CCS 100 receives a download (such as any download described in this description), display the image and the first symbol, without displaying the set of selectable identifiers and the supplemental information. The CRPI 109 can include program instructions to cause the processor 101 to, while the user interface 103 is being caused to displaying the image and the first symbol, receive and process user-input corresponding to user selection of the first symbol. Further, the CRPI 109 can include program instructions to cause the user interface 103 to, in response to the processor 101 receiving and processing the user-input, display the set of selectable identifiers. Still further, the CRPI 109 can include program instructions to cause the processor 101 to, while displaying the set of selectable identifiers, receive and process another user-input corresponding to user selection of one of the selectable identifiers. Yet still further, the CRPI 109 can include program instructions to cause the user interface 103 to, in response to the processor 101 receiving and processing the other user-input, display the portion of supplemental information indicated by the selected identifier.
The CRPI 109 can include program instructions to cause the processor 101 to receive and process other user-inputs as well.
Next,
Block 231 includes receiving a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component. Each selectable identifier of the set can indicate a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information. Some supplemental information within a download can be associated with multiple selectable identifiers within the download.
One or more of the CCS's described herein (e.g., CCS 100 or CCS 2) can be configured to receive the download. In particular, one or more of the elements of the CCS can be configured to receive the download, such as one or more processors connected to a display (e.g., the processor 101 of CCS 100, connected to user interface 103).
In some scenarios, CCS 100 (or CCS 2) can generate and transmit to a server (e.g., the SCS 4) the request for the download in response to first receiving user-input representing the request. To facilitate this in practice, the CCS 100 can provide an application or other mechanism through which a user (e.g., technician) can enter a request for information regarding a particular vehicle component for a particular vehicle. Further, such a request can include a variety of information representing characteristics of the particular vehicle and/or the particular vehicle component. Accordingly, the server can then use such information to assemble the download for the CCS 100 and transmit the download to the CCS 100. Examples of such information includes: (i) an identifier of the CCS 100 (e.g., client ID 110) (so that the server can determine where to send the download), (ii) an identifier of a particular vehicle (e.g., a VIN, a YMM, a YMME, etc.) (iii) an identifier of a particular vehicle component for which the download is being requested, (iv) the captured data 115 captured by the capture device 107 as discussed above (e.g., an image of a particular vehicle component for which the download is being requested, a bar code or QR code indicating the vehicle's VIN), and/or (v) one or more symptoms that a particular vehicle and/or a particular vehicle component is experiencing, among other possible information.
The CCS 100 can receive the information discussed in the preceding paragraph in various ways. For example, the CCS 100 can cause the user interface 103 to display a drop down menu to select the YMM or YMME of the vehicle. In particular, the drop down menu can enable a user to first select a year from a list of years, then select a manufacturer from a list of manufacturers for the selected year, and then select a model from a list of models for the selected manufacturer and year. The menu can further enable the user to then select an engine type for the selected YMM. As another example, the CCS 100 can obtain at least a portion of the information, such as the YMME, from the vehicle itself via the client-to-vehicle network.
After CCS 100 receives the information discussed in the preceding paragraph, the processor 101 can interpret the information to determine which characteristic(s) of the particular vehicle and/or the particular vehicle component to include in the request for the download. The processor 101 can then generate the request for the download and transmit the request via transceiver 104 to the server. Upon receipt of the request, the server can read the request to determine the characteristic(s) and assemble the download to include the image, symbol data, set of selectable identifiers, and supplemental information for the vehicle component indicated by the characteristic(s). The server can assemble the download by retrieving some or all of the download from memory at the server and/or transmitting to one or more databases located remotely from the server a request for some or all of the download and then receiving some or all of the download from the one or more databases. Upon assembling the download, the server can transmit the download for receipt by the CCS 100.
It can be assumed in some scenarios that the CCS 100 receives the download after and/or responsive to a technician first selected a particular vehicle YMM or YMME, although it should be understood that in other scenarios a technician can select a particular vehicle YMME at some point after the CCS 100 receives the download.
The vehicle component can be any of a variety of vehicle components on/in a vehicle. As an example, the vehicle component can include a brake rotor, a brake drum, a crankshaft, a camshaft, an ECU, a fuel pump, a solenoid, or a sensor. As another example, the vehicle component can comprise any of a variety of vehicle subsystems, such as a vehicle steering system, a vehicle fuel system, a vehicle emissions system, or a vehicle braking system. As another example, the vehicle component can be a wiring harness or an aspect of a wiring harness, such as a connector terminal, a circuit, a wire, etc. A “circuit”, as described herein, can refer to any wire or wires that are connected between two or more nodes and that serve as a means for carrying an electrical or optical signal. Further, a “wire” can refer herein to any type of wire, such as copper, aluminum, fiber-optic, etc., that can carry an electrical or optical signal.
Other examples of the vehicle component are also possible. The vehicle component can be a single vehicle component that does not contain any further vehicle components, such as a manifold air pressure (MAP) sensor or an ambient air temperature sensor. However, in some scenarios, the vehicle component can be a vehicle component that includes multiple other vehicle components, such as a wiring harness consisting of multiple aspects of a wiring harness (e.g., individual circuits, connector terminals, and/or sensors). In such scenarios, the CCS 100 receiving the download can include receiving a download that includes images, symbol data, sets of selectable identifiers, and supplemental information corresponding to the vehicle component as well as other vehicle components that are part of the vehicle component.
The downloaded image can have various formats. For instance, the image can be a scalable vector graphics (SVG) image or a JPEG image. Other examples are possible as well.
Receipt of user-input can be one way of triggering the processor 101 to generate and transmit a request for the download, although other ways are possible as well. In one example, for instance, the processor 101 can generate and transmit the request automatically without direct user-input, such as in response to a particular triggering event. In another example, the processor 101 can receive a VDM that indicates a problem with a particular vehicle component (e.g., a DTC within a VDM, where the DTC indicated that the particular vehicle component is failing).
The image included in the download can include the image of the vehicle component or provide data representing the image of the vehicle component for causing the user interface 103 to display the image. The processor 101 can process such data and in turn responsively cause user interface 103 to provide the image as part of a DUI. The image can be a two-dimensional (2D) and/or three-dimensional (3D) image of the vehicle component, or another type of image.
The first symbol (and any other “symbols” described herein) can take the form of a “hotspot” of the displayed image of the vehicle component. Herein, a “hotspot” can generally refer to a portion of the displayed image (or a portion of the DUI in general) that a user of the CCS 100 can interact with via the user interface 103. For example, when the processor 101 detects that a user is hovering over a hotspot with a mouse cursor or other aspect of the user interface 103, or the cursor is proximate to the hotspot in a region within a predetermined threshold distance from the hotspot, the processor 101 can responsively cause an event to occur, such as enabling the hotspot to be selected by the user and/or displaying a pop-up menu or other type of window (e.g., a menu or window including the set of identifiers or other information associated with the vehicle component). As another example, the processor 101 can detect a click, double-click, touch tap, or double-touch tap of the hotspot itself (or somewhere in the region) and can responsively cause an event to occur. These interactions with a hotspot (e.g., hovering over, proximate to, clicking, tapping, etc.) can be referred to as a selection of the hotspot (or a type of “hotspot-selection”), so as to trigger the processor 101 to cause an event to occur. Other DUI elements discussed herein can take the form of a hotspot as well.
Example events that can occur as a result of selecting a hotspot can vary. Further, hotspot selection can take various forms. As an example, when the processor 101 detects that a user is hovering over a hotspot, but has not clicked the hotspot, the processor 101 can responsively cause a pop-up window of information related to the hotspot to appear as long as the user's cursor remains hovering over the hotpot. Once the processor 101 detects that the user's cursor is no longer hovering over the hotspot, the processor 101 can responsively cause the pop-up window of information related to the hotspot to disappear. By contrast, when the processor 101 detects that the user has clicked the hotspot, the processor 101 can responsively cause the pop-up window of information to appear to a more permanent degree such that even when the user moves their cursor away from the hotspot (or the window itself), the pop-up window of information will remain displayed.
The symbol data can include the first symbol or provide data representing the first symbol for causing the processor 101 to establish the first symbol (e.g., determine where the user interface 103 should display the first symbol and/or cause the user interface 103 to display the first symbol). For instance, the symbol data can include a default set of coordinate points with respect to a default size of the image, the set of coordinate points including at least one coordinate point that corresponds to a coordinate point of a grid defined for the display (e.g., a predetermined grid of pixels). The set of coordinate points can include, for example, a set of pixel column(s) and row(s) at which to display the symbol. In some embodiments, the set of coordinate points can additionally include a set of pixel coordinate points identifying the region within the predetermined threshold distance from the first symbol, so that the processor 101 can recognize when a mouse cursor or other selection means enters the region and responsively trigger an event to occur. In any case, the processor 101 can use the default set of coordinate points, the grid defined for the display, and perhaps additionally a zoom level of the image with respect to the default size of the image, to establish the first symbol. The processor 101 can establish other symbols as well using the same type of data associated with each other symbol.
In addition to appearing in a pre-specified area of the image as noted above, a hotspot can serve as a link (e.g., a URL) to a particular search query associated with the hotspot such that, when the hotspot is clicked or otherwise selected, the processor 101 can responsively take action to initiate the particular search query. For instance, if the hotspot is placed in the area of the image associated with a MAP sensor, a selection of the hotspot can trigger the processor 101 to initiate a query for information associated with the MAP sensor that may or may not be included in the download described above.
In practice, after the image and symbol(s) are initially displayed, a zoom level of the image can affect where within the display the symbol(s) appear. For instance, when a user zooms in or out with respect to a displayed image and symbol, the number of pixels surrounding the symbol can change. And in another instance, when multiple symbols are displayed, zooming in or out can cause one or more of such symbols to disappear from view in the DUI, and/or can cause one symbol to appear in the same area of the display where another symbol once appeared. As such, the processor 101 can keep track of the zoom level and dynamically adjust the location(s) within the display where the symbol(s) should appear and cause the user interface 103 to display the symbol(s) in those dynamically-adjusted locations.
As noted above, the vehicle component itself can be a wiring harness, and thus the image in the download can depict the wiring harness. In an example scenario, however, the vehicle component can be connectable to or include a wiring harness, such as a MAP sensor connectable to the wiring harness or a single circuit of the wiring harness, and thus the image in the download can depict the wiring harness as connected to or part of the vehicle component. In line with this example scenario, the first symbol can be a symbol for a first circuit within the wiring harness, for instance. When a wiring harness includes other circuits, sensors, etc., the download could include other symbols (and corresponding symbol data) for such other circuits, sensors, etc., within the wiring harness.
The supplemental information can include various types of information associated with the vehicle component, examples of which include (i) a component test information, (ii) a real-fix information, (iii) a removal and replacement information, (iv) a connector view information, (v) a component location information, (vi) a technical service bulletin (TSB) information, (vii) a top diagnostic trouble code information, (viii) a top symptom information, (ix) a parameter identifier (PID) value information, (x) a baseline data information, (xi) a vehicle component calibration information, and (xii) a vehicle component reset information.
The component test information can include, for instance, information indicating how to test the vehicle component to determine whether the vehicle component has failed, such as a diagnostic flowchart and troubleshooting hints to determine whether the vehicle component is operating properly or failed.
The real-fix information can include, for instance, information the SCS 4 determines or has access to based on prior successful fixes to similar vehicles having the same displayed vehicle component. This information can be determined from repair orders describing the prior successful fixes. Further, the real-fix information can be indicative of a count of how many prior fixes were successful using the applied fix.
The removal and replacement information can include, for instance, information explaining how to remove the vehicle component from the vehicle and how to replace and/or reinstall the vehicle component into the vehicle. This information can identify special hand tools required for the removal and replacement procedure, torque specifications, vehicle component location information, and the like.
The connector view information can include, for instance, information indicating where a connector is located in a vehicle, circuit identifier (e.g. circuit number and/or name), pinout (description showing each pin/terminal in the connector and what circuit is connected to each pin).
The component location information can include, for instance, a description textual and/or graphical showing location of the vehicle component, perhaps in relation to one or more other vehicle components.
The TSB information can include, for instance, information obtained from TSB (e.g., a vehicle manufacturer TSB), such as information that indicates known faults, recall information, test procedures, removal and replacement procedures, etc.
The top diagnostic trouble code information can include, for instance, information that lists the DTC associated with the vehicle components. When multiple DTC associated with the vehicle component, the DTC can be ranked from most-likely to least likely to be set. Other rankings are possible as well.
The top symptom information can include, for instance, information that list the most-likely symptoms related to the vehicle component. This information can be theoretical and/or based on prior repair order information listing symptoms or live data.
The PID value information can include, for instance, information indicating specified values of parameters associated with a vehicle component (e.g., sensor values).
The baseline data information can include, for instance, electrical measurements of the vehicle component including a baseline value, such as the baseline voltage waveform discussed below.
Other types of supplemental information are possible as well. For instance, the supplemental information can include specification information—namely, specifications for the vehicle or the vehicle component. As an example, given a vehicle component that includes bolt holes or bolts for a thermostat housing or a cylinder head (which would be shown in the displayed image), the specification information may indicate a torque specification for tightening a bolt at the bolt hole. As another example, the vehicle component can include (and the displayed image can show) a fluid fill location, and the specification information can list a fluid type and capacity information for the fluid associated with the vehicle component. As yet another example, the supplemental information can include functional test information. The functional test information can include information related to testing that controls the vehicle component by serial data sent to the ECU of the vehicle. As yet another example, the supplemental information can include a PID list related to the vehicle component.
As still yet another example, the supplemental information can include a vehicle component calibration information to be performed on a vehicle if a procedure is performed to a particular vehicle component. For instance, the vehicle component calibration information can include calibration information for calibrating a lane departure system component if a wheel alignment (e.g., front and/or rear wheel alignment) procedure is performed, or the vehicle component calibration information can include calibration information for calibrating a parking assist component in a vehicle if a procedure is performed to a bumper on the vehicle. As still yet another example, the supplemental information can include a vehicle component reset information to be performed on a vehicle if a procedure is performed to a particular vehicle component. For instance, the vehicle component reset information can include reset information regarding resetting an electronic parking brake on a vehicle if a battery in the vehicle is disconnected from a battery cable in the vehicle.
As noted in block 231, each selectable identifier can identify one of the types of supplemental information listed in the preceding paragraph. For example, the set of selectable identifiers can include icons and/or text that read “Component Test” and “R&R Procedure”, corresponding to the component test information and to the removal and replacement information, respectively. Further, the processor 101 can cause the user interface 103 to provide a DUI including the set of selectable identifiers. Upon receipt of a user-input representing a selection of one of the selectable identifiers, the processor 101 can responsively cause the user interface 103 to provide a DUI (e.g., as a new DUI or as part of the current DUI) including the supplemental information corresponding to the selected identifier. As an example, upon receipt of a user-input representing a selection of “Component Test”, the user interface 103 can responsively display the component test information from the download. As another example, upon receipt of a user-input representing a selection of “R&R Procedure”, the user interface 103 can responsively display the removal and replacement information from the download. In some embodiments, the user interface 103 can display each selectable identifier as a respective hotspot.
Next, block 232 includes displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers. Displaying the image and the first symbol can include the user interface 103 displaying an image that shows a portion of the vehicle component or all of the vehicle component. For example, the displayed image can depict (or show) an entire wiring harness, including all connected sensors and/or circuits, or can instead include a portion of the wiring harness, including only some connected sensors and/or circuits (e.g., as shown in
The user interface 103 can display the image and the first symbol (and perhaps other symbols) such that a user can view the image and symbol(s) in various ways. For example, the image can take the form of a 2D or 3D image and the user interface 103 can enable a user to pan, zoom (in or out), and/or rotate the image to observe different portions of the image.
Next, block 233 includes receiving, while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol. Receiving the first input can include the processor 101 receiving, via user interface 103, a first user-input representing a selection of the first symbol. Such a selection of the first symbol can take the form of one of the hotspot-selection types discussed above (e.g., hovering over the first symbol, bringing a mouse cursor within a predetermined threshold distance from the first symbol, or clicking/double-clicking the first symbol).
Next, block 234 includes displaying, on the display in response to receiving the first input, the set of selectable identifiers. Displaying the set of selectable identifiers can include displaying one selectable identifier, or can include displaying more than one selectable identifier, depending on how many selectable identifiers are included in the download.
In some embodiments, displaying the set of selectable identifiers can include the user interface 103 displaying the set of selectable identifiers such that they overlay the image, the first symbol, and/or another area of the DUI. For example, as shown in
Next, block 235 includes receiving, while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers. Receiving the second input can include the processor 101 receiving, via user interface 103, a second user-input representing a selection of the first selectable identifier (e.g., clicking, tapping, hovering over, etc. the first selectable identifier).
Next, block 236 includes displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier. For example, in line with the discussion above, if the first selectable identifier is the “Component Test” identifier, and processor 101 receives the second input corresponding to a selection of the “Component Test”, displaying the respective portion of the supplemental information indicated by the first selectable identifier can include the user interface 103, in response to the processor 101 receiving the second input, displaying the component test information that was included in the download. As another example, if the first selectable identifier is the “Related TSB's” identifier, and processor 101 receives the second input corresponding to a selection of the “Related TSB's”, displaying the respective portion of the supplemental information indicated by the first selectable identifier can include the user interface 103, in response to the processor 101 receiving the second input, displaying the technical service bulletin (TSB) information that was included in the download.
Additional functions are described below. Some or all of these functions can be carried out before, during, or after the set 230 described above.
After displaying the respective portion of the supplemental information indicated by the first selectable identifier, the processor 101 can receive, while the set of selectable identifiers is displayed, a third input corresponding to selection of a second selectable identifier from the displayed set of selectable identifiers, and can responsively cause the user interface 103 to display the respective portion of the supplemental information indicated by the second selectable identifier. The user interface 103 displaying the respective portion of the supplemental information indicated by the second selectable identifier can include displaying the respective portion of the supplemental information indicated by the second selectable identifier with or instead of the respective portion of the supplemental information indicated by the first selectable identifier. As an example, if “Component Test” was selected and the component test information is being displayed, and then the technician selects “Related TSB's”, the processor 101 can cause the user interface 103 to no longer display the component test information and then instead display the technical service bulletin (TSB) information in the same location in the DUI where the component test information was displayed or in a different location in the DUI. As another example, in a similar situation, processor 101 can alternatively cause the user interface 103 to display both the component test information and the technical service bulletin (TSB) information at the same time so that the technician can view both simultaneously. Similar functions can be performed in the event that fourth, fifth, etc. inputs are received corresponding to selection of third, fourth, etc. selectable identifiers.
In some scenarios, the download can also include service estimate information associated with the vehicle component. The service estimate information can include various information that can enable a technician or other user to determine how much time, money, and/or labor may be needed for servicing the vehicle component associated with the selected identifier. As such, the service estimate information can include cost information indicating a price of the vehicle component and/or labor information pertaining to servicing of the vehicle component.
The service estimate information can take the form of service estimate information for only one vehicle component or only one aspect of the vehicle component. For example, when the vehicle component is a fuel pump, the service estimate information can include a price and labor hours for the fuel pump. Additionally or alternatively, the service estimate information can take the form of a collection of service estimate information for each aspect of the vehicle component. For example, when the vehicle component is a wiring harness, the service estimate information can include a price and labor hours for each of one or more aspects of the wiring harness, such as a sensor, individual circuit, etc. As a more particular example, as shown in
Accordingly, the functions discussed above can further include the user interface 103 displaying, on the display, while displaying the set of selectable identifiers, the service estimate information for the vehicle component displayed on the DUI and at least one selection graphic associated with the service estimate information. Displaying the selection graphic(s) can include the user interface 103 displaying at least one check box, radio button, etc. within the DUI. At some point after the user interface 103 displays the service estimate information and the selection graphic(s), the processor 101 can receive an input corresponding to selection of the selection graphic(s). For example, such an input can take the form of a user checking a check box displayed proximate to the service estimate information.
In some scenarios, a technician can use the functions described herein as part of a “session” (i.e., a period of time) during which the technician views and interacts with the interactive vehicle diagnostic display. As part of this session, the CCS 100 (e.g., the processor 101), the SCS 4, or another device can maintain, in local or remote memory, various records of the technician's interactions with various vehicle components. For example, the records can include a history of the vehicle components for which the technician requested downloads, a history of the supplemental information the technician viewed, etc.
As another example, the records can include an ongoing service estimate for the technician, including running totals for service estimate information for one or more vehicle components. As such, when a technician wishes to add the price and/or labor time for a particular vehicle component to the service estimate, the technician can input via the user interface 103 a selection of the selection graphic(s) corresponding to price and/or labor, upon which the processor 101 can then responsively output a request to generate a new service estimate or update an existing service estimate based on the service estimate information. Outputting the request to generate or update the service estimate can include the processor 101 causing the transceiver 104 to transmit the request to the SCS 4 or other device that is maintaining the service estimate, after which the SCS 4 or other device can receive the request and responsively generate a new service estimate or update the existing service estimate. Alternatively, when the service estimate can be maintained locally at the CCS 100, outputting the request to generate or update the service estimate can include the processor 101 causing a new service estimate to be generated and stored in memory or causing the existing service estimate to be updated in memory.
An interactive vehicle diagnostic display can include at least one electrical measurement associated with the vehicle component displayed on the DUI. For example, when the vehicle component is or includes a wiring harness which in turn includes various circuits and/or sensors, the download can include respective electrical measurements corresponding to each circuit and/or sensor obtained over a period of time. The electrical measurement(s) can be real-time electrical measurement(s) or non-real-time electrical measurement(s) obtained by the CCS 100, by a CMT, and/or by other means, from the vehicle having the vehicle component (e.g., from the vehicle having the technician-selected YMME). For instance, the electrical measurement(s) can be electrical measurement(s) that the SCS 4 received from the vehicle having the technician-selected YMME, such as electrical measurements that the vehicle reported directly to the SCS 4 or to another device that in turn transmitted to the SCS 4.
The electrical measurement(s) can take various forms. For instance, for a given vehicle component or a given aspect of a given vehicle component, the electrical measurement(s) can take the form of at least one voltage waveform representing multiple electrical measurements obtained over a period of time for the given vehicle component or the given aspect, such as a 2D voltage waveform plot of an oscilloscope reading. A voltage waveform can include, for instance, a baseline voltage waveform representing multiple electrical measurements, or a voltage waveform representing multiple electrical measurements obtained from the vehicle. Further, the electrical measurement(s) can include a minimum expected value of the electrical measurement(s) and/or a maximum expected value of the electrical measurement(s). The CCS 100 can display the electrical measurement(s) in any one or more of the forms discussed herein, including those discussed in this paragraph.
In an example scenario where the vehicle component is a wiring harness, a technician can select, via the user interface 103, the first symbol, where the first symbol can correspond to a first circuit of a wiring harness depicted as the displayed image. In response to receiving the selection, the user interface 103 can display within a DUI—in the same pop-up menu as the list of selectable identifiers or in a separate window—multiple electrical measurements obtained from the vehicle for the first circuit over a period of time. For example, the user interface 103 can display the multiple electrical measurements as a voltage waveform, as discussed above. As another example, the user interface 103 can display in a single graph a minimum expected value and a maximum expected value for the multiple electrical measurements, such as a minimum expected voltage and a maximum expected voltage. As yet another example, the user interface 103 can display the multiple electrical measurements in multiple separate graphs.
The download can include the electrical measurement(s), as part of the supplemental information or as additional information. Alternatively, the CCS 100 can obtain the electrical measurement(s) by way of a separate process occurring simultaneous to receiving the download or after receiving the download (e.g., after the user selects the first symbol associated with the vehicle component). As an example of how the CCS 100 might obtain desired electrical measurement(s) for the vehicle component, the CCS 100 (e.g., a vehicle interface device of the CCS 100, such as the DLC interface 105) can transmit to the vehicle over the client-to-vehicle network a request for a live data value associated with a PID used by the vehicle component, such as a PID associated with an electrical signal carrier on a circuit of a wiring harness. The vehicle interface device of the CCS 100 can then at some point receive, from the vehicle (e.g., from an electronic control unit within the vehicle), via the transceiver 104, the requested data value associated with the PID. The processor 101 can then convert the data value to obtain the desired electrical measurement(s).
In practice, if a user is not licensed or otherwise authorized to view any of the information associated with the vehicle component, the DUI may not include the restricted information. The restricted information can be included as part of the download in some scenarios, but not displayed. In other scenarios, the SCS 4 can determine that the user of the CCS (or the CCS itself, based on an identifier of the CCS included in the request) is not authorized to view certain information that is being requested, and in response to determining this, may not include the restricted information when assembling the download. Other examples of managing restricted information are possible as well.
Also shown are portions of the three circuits that may not be initially displayed as part of the image 302. These portions are shown as dashed lines and represented by reference numbers 316, 317, and 318, corresponding to the first circuit 304, the second circuit 305, and the third circuit 306, respectively. In practice, the download that the CCS receives can include image data representative of a full image of the wiring harness, but the CCS may not display the entire image at once. Rather, the CCS can display only a portion of the image, but the DUI 300 can enable a user to navigate to other portions of the image. For example, in order to view portions 316, 317, and 318, the CCS can provide as part of the DUI 300 one or more user-selectable navigation tools, such as navigation arrows that, when selected, cause a different portion of the image to be displayed. Other examples are possible as well.
In line with the discussion above, the symbol 314 is shown as taking up more pixels in the DUI 300 than the image of the MAP sensor 310 itself. As such, the user can be able to select the symbol 314 in various ways, such as by clicking/touching within the circular dashed region shown, or even by merely moving a mouse cursor (not shown) within the region. Other ways of selecting the symbol 314 are also possible.
The window 320 includes a list of selectable identifiers that identify various types of supplemental information related to the MAP sensor 310, where the supplemental information was downloaded with the download but is not yet displayed within DUI 300. In particular, the window 320 includes the following selectable identifiers, each of which is illustrated as a selectable link and each of which identifies supplemental information related to the MAP sensor 310: Component Test 321, Real Fixes 322, R&R Procedure 324, Connector View 325, Component Location 326, Related TSBs 327, Top Codes 328, and Top Symptoms 329. These eight selectable identifiers correspond to the following supplemental information from the download, respectively: (i) component test information, (ii) real-fix information, (iii) removal and replacement information, (iv) connector view information, (v) component location information, (vi) TSB information, (vii) top diagnostic trouble code information, and (viii) top symptom information. After the window 320 is displayed, the CCS can receive a selection of one of the selectable identifiers, and the CCS can then responsively cause the DUI 300 to include the portion of supplemental information that corresponds to the selected identifier. Selection of a given selectable identifier can cause the corresponding portion of supplemental information to be displayed in the current webpage, or can cause the CCS to generate a new webpage that includes the corresponding portion of supplemental information (e.g., a new tab in the Internet browser or a new window in the Internet browser).
Between the Related TSBs identifier 327 and the Top Codes identifier 328, the window 320 is shown to include a section for service estimate information associated with the MAP sensor 310. In particular, the window 320 includes an identifier for the price 330 of service for the MAP sensor 310 (shown as $47.95), and also includes an identifier for the amount of labor 331 for servicing the MAP sensor 310 (shown as 3.2 hours). The price and labor for a given vehicle component can be represented in other ways as well. Further, the window 320 includes a displayed price check box 332 and a displayed labor check box 333 that enable a user to add one, both, or none of price 330 and labor 331 to a service estimate (not shown). Accordingly, a user can select one, both, or none of the check boxes 332, 333. A user can also “uncheck” a given check box to remove price and/or labor from the service estimate. The price check box 332 is shown as selected, and thus the CCS has added the price of service ($47.95) to the service estimate (not shown). Although the labor check box 333 is not shown as selected, a user can later select it as well. Other ways to add/remove service estimate information to/from a service estimate are also possible. Although not shown, after receiving selection (or de-selection) of a given check box, the CCS can provide within the DUI 300 an indication of the service estimate.
Lastly, the window 320 is shown to include a voltage waveform 334 for the MAP sensor 310. The CCS can obtain the electrical measurement data used to present the voltage waveform 334 at various points in time. For example, after selection of the symbol 314, the CCS can transmit a request for a data value associated with a PID used by the MAP sensor 310, receive the data value, convert the data value to obtain the voltage waveform 334, and then include the voltage waveform 334 in the displayed window 320. The voltage waveform 334 can appear in the window 320 before, at the same time as, or after all the other information is displayed. For instance, the selectable identifiers and the service estimate information can be displayed first while the voltage waveform 334 is retrieved/loading, and then the voltage waveform 334 can be displayed once it is retrieved/loaded. Further, in some scenarios, the DUI can also include a selectable identifier (not shown) that identifies PID value information for the PID of the MAP sensor 310.
In practice, if a user is not licensed or otherwise authorized to view any of the information associated with the MAP sensor 310, the DUI 300 may not include such information.
In other examples, the second window 350 can be larger in size and can thus take up more or less space of the DUI 300 than as shown in
Additional example operations relating to vehicle diagnostic displays will now be described. In particular, such additional operations can relate to viewing both real-time and non-real-time electrical measurements associated with various vehicle circuits.
Next,
In some implementations, one or more of the CCS's described herein (e.g., CCS 100 or CCS 2) can be configured to receive a download of information, which can include some, all, or none of the information discussed above. In particular, one or more of the elements of the CCS can be configured to receive the download, such as one or more processors connected to a display (e.g., the processor 101 of CCS 100, connected to user interface 103). The download can be received in a manner similar to or different from the manner discussed above. For instance, the CCS 100 can receive user-input representing a request for the download, the request including various information regarding a particular vehicle or vehicle component (e.g., client ID 110, a VIN, a YMM, a YMME, etc.), and the server can then accordingly use such information to assemble the download for the CCS 100 and transmit the download to the CCS 100. The server can assemble and transmit the download in any of the manners discussed above.
Block 391 includes receiving a download including (i) an image representative of at least one circuit in a vehicle, the at least one circuit including a first circuit configured for carrying a first signal within the vehicle, and (ii) symbol data associated with at least one symbol, the at least one symbol including a first symbol. The first signal can be electrical or optical. Any given circuit represented by the image, including the first circuit, can take various forms, such as a crankshaft position (CKP) sensor ignition feed circuit, a CKP sensor signal input circuit, a CKP sensor reference low circuit, a CKP sensor ground circuit, a MAP sensor air flow circuit, a MAP sensor voltage source circuit, an ambient air temperature sensor circuit, among other possibilities.
Further, the processor 101 can be configured to receive data representing values of various circuit signals, such as the first signal carried by the first circuit.
The download can be received in a manner similar to or different from the manner discussed above. For instance, the CCS 100 can receive, via the user interface 103, user-input representing a request for the download, the request including various information regarding a particular vehicle or vehicle component (e.g., client ID 110, a VIN, a YMM, a YMME, etc.), and the server can then accordingly use such information to assemble the download for the CCS 100 and transmit the download to the CCS 100. The server can assemble and transmit the download in any of the manners discussed above.
In some implementations, the download can also include data indicative of a message to request a VDM including data representing values of a signal carried by a circuit. The data indicative of the message to request a VDM can include, for instance, a PID and an ECU identifier, which can be used as part of a process for requesting and receiving, from the vehicle, data representing values of various signals carried by various circuits, as described below.
Next, block 392 includes displaying, on a display after receiving the download, the image and the at least one symbol. The user interface 103 can display the image and the at least one symbol in various ways, such as in any one of the manners discussed above. The displayed image can include, for instance, three circuits (e.g., the entirety of three circuits, or three portions of respective larger circuits), each circuit represented by a displayed symbol.
Next, block 393 includes receiving, while the image and the at least one symbol are displayed on the display, a first input corresponding to selection of the first symbol. In general, the processor 101 can receive an input corresponding to selection of any one of the displayed symbol(s), which can be considered a selection of the circuit to which the selected symbol corresponds. Receiving the first input can include the processor 101 receiving, via the user interface 103, a first user-input representing a selection of the first symbol. Such a selection of the first symbol can take the form of one of the hotspot-selection types discussed above (e.g., hovering over the first symbol, bringing a mouse cursor within a predetermined threshold distance from the first symbol, or clicking/double-clicking the first symbol).
The first input can represent a request for data from the vehicle, such as a first request for at least one value of the first signal. As such, block 394 includes receiving, from the vehicle in response to receiving the first input, data representing at least one value of the first signal.
The processor 101 can receive such data in various ways. In line with the discussion above, for instance, in response to receiving the first input, a vehicle interface device of the CCS 100 such as the DLC interface 105 can transmit, directly and/or via the transceiver 104, the first request to the vehicle (e.g., the ECU within the vehicle) over a network to which CCS 100 is connected, such as the client-to-vehicle network described above. Similar to the requests discussed above, the first request in this scenario can include various information that identifies the first circuit, the first signal, the ECU within the vehicle, and/or other aspects of the vehicle. To facilitate this in practice, as noted above, the download can include a first identifier, such as a PID, that identifies the first circuit and/or the first signal, and can also include an ECU identifier for identifying the ECU. Upon receipt of the first request, the ECU can responsively obtain, and then transmit to the CCS 100 over the client-to-vehicle network, a response including the value(s) of the first signal. The vehicle interface device of the CCS 100 can then at some point receive the response, from the ECU via the transceiver 104, transmit the response to the processor 101, and the processor 101 can process the response to determine the value(s). The response can take the form of a VDM or other type of message.
As an example, the request can include (i) the client ID, (ii) an ECU identifier, (iii) a value corresponding to a particular diagnostic mode of operation—namely a value corresponding to a request for parameter data, and (iv) a PID for a vehicle component (e.g., sensor) with which the first circuit is associated (e.g., a PID for a MAP sensor if the first circuit is a circuit connected to the MAP sensor). In this example, the ECU's response can then include the client ID, the ECU identifier, the diagnostic mode value, the PID, and the value(s) (e.g., the latest MAP sensor value). The type of request and content of the request can vary from vehicle to vehicle and can depend on how the vehicle is configured (e.g., how one or more components of the vehicle, such as the ECU, are configured).
In alternative implementations, the processor 101 can receive the value(s) from an electronic measuring instrument (e.g., a digital volt-ohmmeter, digital multimeter, or the like) at an electrical measurement input to which the electronic measuring instrument is connected. This can be advantageous in scenarios in which value(s) are requested for a sensor in which there is no PID data, such as a CKP sensor.
The value(s) received from the vehicle can take various forms. For instance, the value(s) can include (i) a baseline value of the first signal, (ii) at least one minimum code setting value of the first signal, (iii) at least one maximum code setting value of the first signal, (iv) a most-recent measured value of the first signal (e.g., as the first signal is measured in real-time), (v) a minimum measured value of the first signal, and/or (vi) a maximum measured value of the first signal. The “data representing the at least one value of the first signal” can include one or more of these values (e.g., the most-recent measured value, the minimum measured value, and the maximum measured value. In some scenarios, receiving the data can involve receiving all of these values at substantially the same time. In other scenarios, receiving the data can involve receiving one or more of these values at one point in time and then later receiving a different one or more of these values at another point in time.
A “baseline value” is a value captured at some point in time from a measurement carried out on the vehicle (or on other vehicles of the same YMM of the vehicle), such as a measurement carried out by a digital volt-ohmmeter or a diagnostic scan tool that interrogates the ECU for PID values. As a general matter, baseline values can be stored with operating characteristics, such as engine RPM or temperature. Further, baseline values can obtained when a vehicle is operating without fault. As such, data values captured when the vehicle is operating with a fault can be compared to the baseline values, thereby giving the vehicle or the technician an indication as to what the fault is (the baseline values could also be compared with data values when the vehicle is operating without fault to provide confirmation the vehicle is operating as expected). Still further, the baseline values can also be obtained for a single unique vehicle and compared to data values captured later from that same exact vehicle. Yet still further, any baseline value can take the form of a single value (e.g., 4.65 V) or a range of values (e.g., 4.5-4.8 V).
A “code setting value” is set by the vehicle manufacturer engineers when developing the vehicle, and refers to a signal value that the ECU of the vehicle uses to set a given DTC from not active to active.
Any one or more of these values discussed above can be included with the download rather than received by the CCS 100 from the vehicle in response to the first request. For instance, the download can include a baseline value of the first signal, whereas other values of the first signal are received from the vehicle in response to the first request. In particular, the baseline value and/or the code setting value(s) can be known by the vehicle (or possibly by the SCS 4 or other entity from which the CCS 100 could receive such values) prior to receiving the download or received as part of the download, whereas values such as the most-recent measured value and the minimum/maximum measured values can be values captured in the time since the download was assembled/received.
In some scenarios, the first request can indicate a request for only one most-recent measured value of the first signal, and accordingly, the ECU can provide such a value. In other scenarios, however, the first request can indicate a request for repeated (e.g., continuous or periodic) most-recent measured values of the first signal in real-time (e.g., a request to provide the CCS 100 with updated measured values every 100 milliseconds (ms)). To facilitate this in practice, the ECU can be configured to interpret the first request such that the ECU is then triggered to enter a mode in which the ECU will repeatedly transmit the updated values (e.g., every 100 ms). Alternatively, if the ECU is not configured to enter such a mode, the user-selection of the first circuit can trigger the CCS 100 to repeatedly transmit to the ECU a request for a single, updated most-recent measured value. For example, the CCS 100 can transmit a request for a single, updated most-recent measured value every 100 ms. Most-recent measured values can be requested/received in other manners as well.
In scenarios where the CCS 100 repeatedly receives most-recent measured values, the CCS 100 can use such values to update any previous minimum or maximum measured values. For example, if the CCS 100 at one point receives a maximum measured value of 5 volts (V), but later receives a most-recent measured value of 6 V, the CCS 100 can adjust the maximum measured value to be 6 V. Alternatively, the ECU itself can provide updated minimum or maximum measured values.
Referring back to the set 390, block 395 next includes determining a first display-location on the display at which to display the data representing the at least one value of the first signal. Block 396 then includes displaying, on the display at the first display-location while the image and the at least one symbol are displayed on the display, the data representing the at least one value of the first signal.
In some examples, the processor 101 can determine the first display-location to be proximate in space on the DUI to a location at which the first circuit is being displayed on the DUI. Similarly, in examples where data for other circuits is displayed, the processor 101 can determine respective display-locations for such data that are proximate to the corresponding circuits. Herein, the term “proximate” can refer to a location of one graphical element on a DUI (e.g., the image, the first symbol, the data representing the at least one value of the first signal, etc.) being within a threshold extent of pixels from another graphical element on the DUI—namely, such that a user viewing the DUI could appreciate that the two graphical elements are associated with one another.
Additionally or alternatively, in other examples, the user interface 103 can display connector lines that connect one graphical element to another graphical element with which the one graphical element is associated. Such connector lines can appear on the DUI as a way to indicate to a user viewing the DUI that the two graphical elements are associated with one another, regardless of whether the two graphical elements are proximate to one another. Examples of connector lines 401, 403, 405, and 407 are shown in
In some embodiments, displaying the data representing the value(s) of the first signal can include the user interface 103 displaying the data on the DUI such that the data overlays the image, one or more symbols, and/or another area of the DUI. For example, as shown in
Determining the first display-location can include the processor 101 determining that the user interface 103 should display simultaneously, at the first display-location, the most-recent value of the first signal, the minimum value of the first signal, and the maximum value of the first signal. Accordingly, displaying the data representing the value(s) of the first signal can include the user interface 103 displaying simultaneously, at the first display-location, the most-recent value of the first signal, the minimum value of the first signal, and the maximum value of the first signal.
In scenarios where the CCS 100 receives at least one minimum code setting value of the first signal and/or at least one maximum code setting value of the first signal, determining the first display-location can include the processor 101 determining that the user interface 103 should display simultaneously, at the first display-location, the data and the minimum and/or maximum code setting values (e.g., displaying simultaneously the most-recent value of the first signal, the minimum value of the first signal, the maximum value of the first signal, and the minimum and maximum code setting values). The user interface 103 can then display simultaneously, at the first display-location, the data and the minimum and/or maximum code setting values.
In some embodiments, the processor 101 can also determine a second display-location on the DUI at which to display the baseline value associated with the first circuit, and then the user interface 103 can display the baseline value at the second display-location while also displaying the image and the at least one symbol. The second display-location can be distinct from the first display-location or can be substantially the same location.
In some implementations, the image can include a first portion representative of a first circuit and additionally include at least one other portion representative of at least one other circuit that is related to the first circuit and configured for carrying respective signals within the vehicle. For instance, the image can include a first portion representative of a first circuit and additionally a second portion representative of a second circuit that is related to the first circuit and configured for carrying a second signal within the vehicle.
Circuits that are “related” are circuits on and/or within a vehicle that are commonly inspected to diagnose a common vehicle condition (e.g., a customer complaint or vehicle symptom). A person skilled in the art will understand that in some instances only one of multiple related circuits need to be inspected to diagnose a common vehicle condition if inspection of that one circuit occurs prior to inspection of the other circuit(s) and is found to be the cause of the vehicle condition. A person skilled in the art will understand that multiple related circuits may comprise circuits inspected to certify that a service action has successfully resolved the common vehicle condition. As an example, an electrical ground circuit and a battery voltage supply circuit to a common ECU can be related as such circuits are commonly inspected when diagnosing a vehicle condition pertaining to the common ECU. As yet another example, multiple circuits identified in a diagnostic flowchart produced for and/or by a vehicle manufacturer to diagnose a particular vehicle condition are related circuits as those multiple circuits are commonly inspected during performance of the diagnostic flowchart. For instance, a circuit connected to a MAP sensor and a circuit connected to an ambient air temperature sensor can be related as both of those circuits can be identified in a single diagnostic flowchart and inspected during performance of the flowchart.
Further, circuits can be deemed to be “related” when they are connected in parallel and share the same ground and/or power source.
In such implementations, the act of displaying the image can, in some scenarios, involve the user interface 103 displaying both the first and second portions of the image together (i.e., displays both the first and second circuits) such that both appear in view in the DUI. Alternatively, in other scenarios, the act of displaying the image can involve the user interface 103 displaying the first portion without displaying the second portion (i.e., displays only the first circuit at first). This can happen for various reasons. For instance, in order to have a sufficiently-sized view of the first circuit on the DUI, it can be desirable to display the first circuit (and perhaps other circuits that are close in proximity to the first circuit in the vehicle), but not display any of the related circuits such as the second circuit that are located remotely from the first circuit in the vehicle (e.g., one sensor can be located near one end of the vehicle and the other sensor can be located near the opposite end of the vehicle, and thus the circuits for these sensors may not be displayed together at the same time).
In either scenario, the user interface 103 can also display—either at the first display-location with the data representing the at least one value of the first signal (e.g., in the same pop-up window as the data) or at a different location—a selection graphic associated with the second circuit. Displaying the selection graphic can include the user interface 103 displaying a check box, radio button, etc. within the DUI. At some point after the user interface 103 displays the selection graphic, the processor 101 can receive an input corresponding to selection of the selection graphic. For example, such an input can take the form of a user checking a check box.
In response to receiving the input, the CCS 100 can perform various actions. For example, in the scenario in which both the first and second portions of the image are being displayed, the processor 101 can receive data representing at least one value of the second signal. The act of the processor 101 receiving such data can occur in any manner discussed above (e.g., CCS 100 transmits request to the ECU, the ECU responds, etc.). The processor 101 can then determine a second-display location on the DUI at which to display the data representing the value(s) of the second signal, and the user interface 103 can display the data representing the value(s) of the second signal while displaying the image, the at least one symbol, and the data representing the value(s) of the first signal.
On the other hand, in the scenario in which first portion of the image is displayed without the second portion of the image, in response to receiving the input, (i) the processor 101 can receive the data representing the value(s) of the second signal and (ii) the user interface 103 can display the second portion of the image on the DUI. The user interface 103 displaying the second portion of the image on the DUI can involve displaying the second portion of the image while displaying the first portion of the image. For example, displaying the second portion of the image while displaying the first portion of the image can involve displaying both the first and second portions of the image such that they take up substantially the same amount of space on the DUI. As another example, displaying the second portion of the image while displaying the first portion of the image can involve displaying both the first and second portions of the image such that they take up different amounts of space on the DUI. As a more particular example, the input can trigger the user interface 103 to animate the DUI such that a zoomed-out view of the first portion of the image is shown while a zoomed-in view of the second portion of the image is shown. Other examples are possible as well.
Alternatively, the user interface 103 displaying the second portion of the image on the DUI can involve displaying the second portion of the image without displaying the first portion of the image. For instance, displaying the second portion of the image without displaying the first portion of the image can involve the user interface 103 replacing the first portion of the image with the second portion of the image—either at the same display-location on the DUI, at a different display-location, or perhaps on a new webpage. As a more particular example, the input can trigger the user interface 103 to animate the DUI such that the first portion of the image disappears (e.g., zoom out of the image until the first portion is no longer visible) and the second portion of the image automatically appears (e.g., zoom into the image until the second portion is visible). Other examples are possible as well.
The processor 101 can then determine a second-display location on the DUI at which to display the data representing the value(s) of the second signal, and the user interface 103 can display the data representing the value(s) of the second signal while displaying the image, the at least one symbol, and the data representing the value(s) of the first signal. In either scenario, the second display-location can be the same as or distinct from the first display-location.
In these scenarios described above, all portions of the image can be received as part of the initial download, or can alternatively be received at different points in time. For example, upon selection of the selection graphic, the CCS 100 can (i) transmit to the SCS 4 a request for an additional portion of the image representing the related circuit(s) (or a new image entirely that represents the related circuit(s), for that matter), (ii) receive from the SCS 4 the requested portion of the image (or new image), and (iii) display the requested portion of the image (or new image). Other examples are possible as well.
In some scenarios, certain values that the CCS 100 receives and the user interface 103 displays can be different from what might be considered normal. For instance, a value being above or below an expected value (e.g., a code setting value or even a minimum/maximum measured value) can possibly indicate a fault. In such scenarios, the user interface 103 can display abnormal values in a manner that indicates to the technician that the values are abnormal. By way of example, the user interface 103 can display a box around an abnormal value, change the color of the text of the abnormal value, or highlight the abnormal value in some other manner. Other examples are possible as well.
As noted above, in practice, a download that the CCS receives can include image data representative of a full image of the wiring harness, but the CCS may not display the entire image at once. Rather, the CCS can display only a portion of the image, but the DUI 400 can enable a user to navigate to other portions of the image. For example, in order to view other portions of the image, such as portions representative of additional circuits and sensors, the CCS can provide as part of the DUI 400 one or more user-selectable navigation tools, such as navigation arrows that, when selected, cause a different portion of the image to be displayed. Other examples are possible as well.
In particular,
In response to the selection of the first circuit 404, the CCS 100 (via the DLC interface) can request a VDM and receive a VDM including data representing value(s) of a first signal carried by the first circuit 404, and the user interface 103 can then display that data. As such, the DUI 400 shown in
In the alternate embodiments discussed above in which the MAP sensor 410 is selected, the first pop-up window 412 and/or any other pop-up windows discussed herein can be displayed in response.
In practice, other pop-up windows associated with other circuits can take forms similar to that of the first pop-up window 412 or can take other forms.
As shown, the first pop-up window 412 also includes a “Related Circuits” selection graphic 423 depicted as an unchecked check box.
Further, selection of the first circuit 404 can also trigger the user interface 103 to display on the DUI 400 a baseline pop-up window 424 including a baseline voltage 425 (depicted as 4.65 V). The baseline pop-up window also includes an operating range for similar vehicles operating normally/properly. For instance, the maximum measured voltage 426 across multiple vehicles is depicted as 5.0 V and the minimum measured voltage 427 across multiple vehicles is depicted as 4.4 V. The baseline voltage 425, maximum measured voltage 426, and/or minimum measured voltage 427 can be received with the initial download and displayed on the DUI 400 only when the first circuit 404 is selected, or can be requested and received from the vehicle in response to the selection of the first circuit 404 and then also displayed on the DUI 400 in response to the selection of the first circuit 404. The baseline voltage 425 can indicate voltage(s) previously measured on a circuit connected to the MAP sensor in the vehicle and/or can indicate voltage(s) previously measured on a circuit connected to the same type of MAP sensor in one or more other vehicles. A person skilled in the art will understand that the baseline pop-up window 424 can display baseline measurements other than a voltage, such as a frequency, resistance, duty-cycle, amperage, etc.
In some scenarios, a measured value for a given circuit can be out of range of the maximum and minimum measured values, which can indicate a problem with the circuit. In such scenario it may be desirable for the CCS 100 to cause the user interface 103 to display on the DUI 400 a walkthrough/guide of how to potentially diagnose the problem, such as by prompting the technician to use a measuring tool and guiding the technician step-by-step to measure values of circuits that are associated with the problem circuit, but for which there is no PID data. Examples of such circuits are the ground and source voltage.
In particular,
To facilitate this, the walkthrough pop-up window 429 includes a cross-sectional view of the connector 409 of the wiring harness, including cross-sectional views of pin-outs for the first circuit 404, the second circuit 406, and the third circuit 408. As shown at this point in time of the step-by-step walkthrough, the pin-out for the second circuit 406 is highlighted, identifying for the technician which circuit should be measured. In some implementations, the walkthrough pop-up window 429 can generally include information describing in various levels of detail how to perform the measurement. (In alternate implementations, the walkthrough pop-up window 429 can include pin-outs for other circuits that are related to the MAP sensor, such as an ambient air temperature sensor voltage source circuit.)
To facilitate this, in line with the discussion above, the walkthrough pop-up window 429 again includes a cross-sectional view of the connector 409 of the wiring harness, including cross-sectional views of pin-outs for the first circuit 404, the second circuit 406, and the third circuit 408. However, as shown at this different point in time of the step-by-step walkthrough, the pin-out for the third circuit 408 is highlighted, again identifying for the technician which circuit should be measured.
It should be understood that the second pop-up window 428, the third pop-up window 432, and/or any other type of information with the second and third circuits can be displayed on the DUI 400 in response to trigger events other than an out-of-range value. For instance, the second pop-up window 428 and the third pop-up window 432 can be displayed on the DUI 400 in response to a selection of the selection graphic 423.
The DUI 400 also includes a fourth pop-up window 440 connected via a connector line to the fourth circuit 436 so as to indicate that the first pop-up window 440 is associated with the fourth circuit 436. Below the fourth pop-up window 440 is a text label, “Ambient Air Temperature Sensor Circuit”, identifying the fourth circuit 436. The fourth pop-up window 440 includes five value received by the CCS 100 from the ECU of the vehicle for the ambient air temperature sensor circuit, such as (i) a maximum measured voltage 442 (depicted as 4.9 V at the illustrated point in time), (ii) a maximum code setting voltage 443 (depicted as 5.0 V at the illustrated point in time), (iii) a most-recent measured voltage 444 (depicted as 4.9 V at the illustrated point in time), (iv) a minimum measured voltage 445 (depicted as 4.5 V at the illustrated point in time), and (v) a minimum code setting voltage 446 (depicted as 0.0 V at the illustrated point in time).
In practice, the fourth pop-up window 440 can be displayed automatically as a further action performed by the CCS 100 in response to the selection of the selection graphic 423 (e.g., perhaps if the fourth circuit 436 is deemed to be closely related to the first circuit 404), or alternatively can be displayed in response to a user selection of the fourth circuit 436.
As described above, the computing systems described herein can be any of a number of different types of computing systems.
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. 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 CRPI 109 or other functions described in this description. 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 CCS ID 110, the VDM 114, the captured data 115, and/or the server data 118. 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 and/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, and/or other data such as the data stored in computer-readable medium 102 and 134.
The system memory 454 and the storage devices 460 are examples of computer-readable medium, such as the computer-readable medium 102. The system memory 454 and the storage devices 460 can include, but is not limited to, RAM, ROM, EEPROM, flash memory and/or other memory technology, CD-ROM, digital versatile disks (DVD) and/or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage and/or other magnetic storage devices, and/or any other medium which can be used to store the desired information and which can be accessed by the computing system 450.
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 CRPI 109, the application 455, and/or the program data 457 can include an application downloaded to a transceiver 73, 104, and/or 133, or 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.
Additionally or alternatively, the computing system 450 can include and/or be implemented as a personal computing system (including both laptop computer and non-laptop computer configurations), and/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, and/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 and/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, and/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 101 of CCS 100 or another processor can be configured as the processor 452. The CRM 102 of CCS 100 or another CRM can be configured as part of or all of the system memory 454 or the storage devices 460. The user interface 103 of CCS 100 or another user interface can be configured as part of or all of the output interfaces 463 and the display device(s) 466. The transceiver 104 of CCS 100 or another transceiver can be configured as part of or all of the communication interfaces 467.
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 elements or functions is to cover each embodiment including a listed element or function independently and each embodiment comprising a combination of the listed elements 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 C, (ii) an embodiment comprising B, but not A and C, (iii) an embodiment comprising C, but not A and 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 element or function A, the embodiments can comprise one A or multiple A. For the embodiments comprising element or function B, the embodiments can comprise one B or multiple B. For the embodiments comprising element or function C, the embodiments can comprise one C or multiple C.
In this description, the terms “data,” “information,” and “content” are used interchangeably. The data can be transmitted and received. As an example, the transmission of the data can occur directly from a transmitting device (e.g., a transmitter) to a receiving device (e.g., a receiver). As another example, the transmission of the data 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, and/or some other network device. The transmission of the data can include transmitting the data over an air interface (e.g., using radio signals (i.e., wirelessly)). The transmission of the data 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, and/or CAT6 cable). The wire can be referred to as a “conductor” and/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 and/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.
The diagrams, flow charts, and other data shown in the figures are provided merely as examples and are not intended to be limiting. Many of the elements illustrated in the figures and/or described herein are functional elements that can be implemented as discrete or distributed elements and/or in conjunction with other elements, and in any suitable combination and location. 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. Furthermore, various functions described as being performed by one or more elements can be carried out by a processor executing computer-readable program instructions (CRPI) and/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.
Example embodiments have been described above. Those skilled in the art will understand that changes and modifications can be made to the described embodiments without departing from the true scope and spirit of the present invention, which is defined by the claims.
Embodiments of the present disclosure may thus relate to one of the enumerated example embodiments (EEEs) listed below.
EEE 1 is a method comprising: receiving, by at least one processor connected to a display, a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information; displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers; receiving, by the at least one processor while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol; displaying, on the display in response to receiving the first input, the set of selectable identifiers; receiving, by the at least one processor while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers; and displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
EEE 2 is the method of EEE 1, wherein the download further includes service estimate information, wherein the service estimate information includes at least one of cost information indicating a price of the vehicle component and labor information pertaining to servicing of the vehicle component, and wherein the method further comprises: displaying, on the display while displaying the set of selectable identifiers, the service estimate information and at least one selection graphic associated with the service estimate information; receiving, by the at least one processor, a third input corresponding to selection of the at least one selection graphic associated with the service estimate information; and outputting, by the at least one processor in response to receiving the third input corresponding to selection of the at least one selection graphic associated with the service estimate information, a request to generate or update a service estimate based on the service estimate information.
EEE 3 is the method of EEE 1 or 2, wherein the supplemental information includes one or more of (i) a component test information, (ii) a real-fix information, (iii) a removal and replacement information, (iv) a connector view information, (v) a component location information, (vi) a technical service bulletin information, (vii) a top diagnostic trouble code information, (viii) a top symptom information, (ix) a parameter identifier (PID) value information, (x) a baseline data information, (xi) a vehicle component calibration information, and (xii) a vehicle component reset information.
EEE 4 is the method of any one of EEEs 1-3, further comprising: receiving, by the at least one processor, an identifier of at least one characteristic of a vehicle having the vehicle component, and outputting, by the at least one processor, a request for the download, wherein the request for the download includes the identifier of the at least one characteristic of the vehicle, wherein receiving the download occurs after transmitting the request for the download.
EEE 5 is the method of any one of EEEs 1-4, wherein the image depicts a wiring harness connectable to or part of the vehicle component, wherein the first symbol is a first symbol for a first circuit within the wiring harness, and wherein the method further comprises: receiving, by the at least one processor while the image and the first symbol are displayed, an input corresponding to selection of the first symbol for the first circuit; in response to receiving the input corresponding to selection of the first symbol for the first circuit, displaying, on the display, at least one electrical measurement associated with the first circuit.
EEE 6 is the method of EEE 5, wherein the download includes the at least one electrical measurement associated with the first circuit.
EEE 7 is the method of EEE 5 or 6, further comprising: transmitting, by a vehicle interface device, a request for a data value associated with a parameter identifier (PID) used by the vehicle component, wherein the PID is associated with an electrical signal carried on the first circuit; receiving, by the vehicle interface device, the data value associated with the PID; converting, by the at least one processor, the data value associated with PID to obtain the at least one electrical measurement.
EEE 8 is the method of any one of EEEs 5-7, further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one voltage waveform representing multiple electrical measurements corresponding to the first circuit obtained over a period of time, wherein the at least one voltage waveform comprises a baseline voltage waveform representing multiple electrical measurements or a voltage waveform representing multiple electrical measurements obtained from a vehicle connected to the display.
EEE 9 is the method of any one of EEEs 1-8, further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one of a minimum expected value of the at least one electrical measurement associated with the first circuit and a maximum expected value of the at least one electrical measurement associated with the first circuit.
EEE 10 is the method of EEE 9, wherein the at least one of the minimum expected value of the at least one electrical measurement associated with the first circuit and the maximum expected value of the at least one electrical measurement associated with the first circuit and the at least one electrical measurement are displayed in a single graph on the display.
EEE 11 is the method of any one of EEEs 1-10, wherein the symbol data includes a default set of coordinate points with respect to a default size of the image, wherein the set of coordinate points include at least one coordinate point that corresponds to a coordinate point of a grid defined for the display, and wherein the at least one processor establishes the first symbol based on the default set of coordinate points, the grid defined for the display and a zoom level of the image with respect to the default size of the image.
EEE 12 is the method of any one of EEEs 1-11, wherein the displayed image shows at least a portion of the vehicle component.
EEE 13 is a system comprising: a display; at least one processor; and data storage comprising instructions executable by the at least one processor to cause the system to perform operations comprising: receiving a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information; displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers; receiving, while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol; displaying, on the display in response to receiving the first input, the set of selectable identifiers; receiving, while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers; and displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
EEE 14 is the system of EEE 13, wherein the download further includes service estimate information, wherein the service estimate information includes at least one of cost information indicating a price of the vehicle component and labor information pertaining to servicing of the vehicle component, and wherein the operations further comprise: displaying, on the display while displaying the set of selectable identifiers, the service estimate information and at least one selection graphic associated with the service estimate information; receiving, by the at least one processor, a third input corresponding to selection of the at least one selection graphic associated with the service estimate information; and outputting, by the at least one processor in response to receiving the third input corresponding to selection of the at least one selection graphic associated with the service estimate information, a request to generate or update a service estimate based on the service estimate information.
EEE 15 is the system of EEE 13 or 14, wherein the supplemental information includes one or more of (i) a component test information, (ii) a real-fix information, (iii) a removal and replacement information, (iv) a connector view information, (v) a component location information, (vi) a technical service bulletin information, (vii) a top diagnostic trouble code information, (viii) a top symptom information, (ix) a parameter identifier (PID) value information, (x) a baseline data information, (xi) a vehicle component calibration information, and (xii) a vehicle component reset information.
EEE 16 is the system of any one of EEEs 13-15, the operations further comprising: receiving, by the at least one processor, an identifier of at least one characteristic of a vehicle having the vehicle component, and outputting, by the at least one processor, a request for the download, wherein the request for the download includes the identifier of the at least one characteristic of the vehicle, wherein receiving the download occurs after transmitting the request for the download.
EEE 17 is the system of any one of EEEs 13-16, wherein the image depicts a wiring harness connectable to or part of the vehicle component, wherein the first symbol is a first symbol for a first circuit within the wiring harness, and wherein the operations further comprise: receiving, by the at least one processor while the image and the first symbol are displayed, an input corresponding to selection of the first symbol for the first circuit; in response to receiving the input corresponding to selection of the first symbol for the first circuit, displaying, on the display, at least one electrical measurement associated with the first circuit.
EEE 18 is the system of EEE 17, wherein the download includes the at least one electrical measurement associated with the first circuit.
EEE 19 is the system of EEE 17 or 18, further comprising a vehicle interface device, the operations further comprising: transmitting, by the vehicle interface device, a request for a data value associated with a parameter identifier (PID) used by the vehicle component, wherein the PID is associated with an electrical signal carried on the first circuit; receiving, by the vehicle interface device, the data value associated with the PID; converting, by the at least one processor, the data value associated with PID to obtain the at least one electrical measurement.
EEE 20 is the system of any one of EEEs 17-19, the operations further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one voltage waveform representing multiple electrical measurements corresponding to the first circuit obtained over a period of time, wherein the at least one voltage waveform comprises a baseline voltage waveform representing multiple electrical measurements or a voltage waveform representing multiple electrical measurements obtained from a vehicle connected to the display.
EEE 21 is the system of any one of EEEs 13-20, the operations further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one of a minimum expected value of the at least one electrical measurement associated with the first circuit and a maximum expected value of the at least one electrical measurement associated with the first circuit.
EEE 22 is the system of EEE 21, wherein the at least one of the minimum expected value of the at least one electrical measurement associated with the first circuit and the maximum expected value of the at least one electrical measurement associated with the first circuit and the at least one electrical measurement are displayed in a single graph on the display.
EEE 23 is the system of any one of EEEs 13-22, wherein the symbol data includes a default set of coordinate points with respect to a default size of the image, wherein the set of coordinate points include at least one coordinate point that corresponds to a coordinate point of a grid defined for the display, and wherein the at least one processor establishes the first symbol based on the default set of coordinate points, the grid defined for the display and a zoom level of the image with respect to the default size of the image.
EEE 24 is the system of any one of EEEs 13-23, wherein the displayed image shows at least a portion of the vehicle component.
EEE 25 is a non-transitory computer readable medium having stored thereon instructions that, upon execution by a computing system, cause the computing system to perform operations comprising: receiving, by at least one processor of the computing system connected to a display of the computing system, a download including (i) an image representative of a vehicle component, (ii) symbol data associated with a first symbol, (iii) a set of selectable identifiers, the set including one or more selectable identifiers, and (iv) supplemental information associated with the vehicle component, wherein each selectable identifier of the set indicates a respective portion of the supplemental information associated with the vehicle component and, when selected, causes the display to display the respective portion of the supplemental information; displaying, on the display after receiving the download, the image and the first symbol without displaying the set of selectable identifiers; receiving, by the at least one processor while the image and the first symbol are displayed on the display without the set of selectable identifiers, a first input corresponding to selection of the first symbol; displaying, on the display in response to receiving the first input, the set of selectable identifiers; receiving, by the at least one processor while the set of selectable identifiers is displayed, a second input corresponding to selection of a first selectable identifier from the displayed set of selectable identifiers; and displaying, on the display in response to receiving the second input, the respective portion of the supplemental information indicated by the first selectable identifier.
EEE 26 is the non-transitory computer readable medium of EEE 25, wherein the download further includes service estimate information, wherein the service estimate information includes at least one of cost information indicating a price of the vehicle component and labor information pertaining to servicing of the vehicle component, and wherein the operations further comprise: displaying, on the display while displaying the set of selectable identifiers, the service estimate information and at least one selection graphic associated with the service estimate information; receiving, by the at least one processor, a third input corresponding to selection of the at least one selection graphic associated with the service estimate information; and outputting, by the at least one processor in response to receiving the third input corresponding to selection of the at least one selection graphic associated with the service estimate information, a request to generate or update a service estimate based on the service estimate information.
EEE 27 is the non-transitory computer readable medium of EEE 25 or 26, wherein the supplemental information includes one or more of (i) a component test information, (ii) a real-fix information, (iii) a removal and replacement information, (iv) a connector view information, (v) a component location information, (vi) a technical service bulletin information, (vii) a top diagnostic trouble code information, (viii) a top symptom information, (ix) a parameter identifier (PID) value information, (x) a baseline data information, (xi) a vehicle component calibration information, and (xii) a vehicle component reset information.
EEE 28 is the non-transitory computer readable medium of any one of EEEs 25-27, the operations further comprising: receiving, by the at least one processor, an identifier of at least one characteristic of a vehicle having the vehicle component, and outputting, by the at least one processor, a request for the download, wherein the request for the download includes the identifier of the at least one characteristic of the vehicle, wherein receiving the download occurs after transmitting the request for the download.
EEE 29 is the non-transitory computer readable medium of any one of EEEs 25-28, wherein the image depicts a wiring harness connectable to or part of the vehicle component, wherein the first symbol is a first symbol for a first circuit within the wiring harness, and wherein the operations further comprise: receiving, by the at least one processor while the image and the first symbol are displayed, an input corresponding to selection of the first symbol for the first circuit; in response to receiving the input corresponding to selection of the first symbol for the first circuit, displaying, on the display, at least one electrical measurement associated with the first circuit.
EEE 30 is the non-transitory computer readable medium of EEE 29, wherein the download includes the at least one electrical measurement associated with the first circuit.
EEE 31 is the non-transitory computer readable medium of EEE 29 or 30, the operations further comprising: transmitting, by a vehicle interface device, a request for a data value associated with a parameter identifier (PID) used by the vehicle component, wherein the PID is associated with an electrical signal carried on the first circuit; receiving, by the vehicle interface device, the data value associated with the PID; converting, by the at least one processor, the data value associated with PID to obtain the at least one electrical measurement.
EEE 32 is the non-transitory computer readable medium of any one of EEEs 29-31, the operations further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one voltage waveform representing multiple electrical measurements corresponding to the first circuit obtained over a period of time, wherein the at least one voltage waveform comprises a baseline voltage waveform representing multiple electrical measurements or a voltage waveform representing multiple electrical measurements obtained from a vehicle connected to the display.
EEE 33 is the non-transitory computer readable medium of any one of EEEs 25-32, the operations further comprising: displaying, on the display in response to receiving the input corresponding to selection of the first symbol for the first circuit, at least one of a minimum expected value of the at least one electrical measurement associated with the first circuit and a maximum expected value of the at least one electrical measurement associated with the first circuit.
EEE 34 is the non-transitory computer readable medium of EEE 33, wherein the at least one of the minimum expected value of the at least one electrical measurement associated with the first circuit and the maximum expected value of the at least one electrical measurement associated with the first circuit and the at least one electrical measurement are displayed in a single graph on the display.
EEE 35 is the non-transitory computer readable medium of any one of EEEs 25-34, wherein the symbol data includes a default set of coordinate points with respect to a default size of the image, wherein the set of coordinate points include at least one coordinate point that corresponds to a coordinate point of a grid defined for the display, and wherein the at least one processor establishes the first symbol based on the default set of coordinate points, the grid defined for the display and a zoom level of the image with respect to the default size of the image.
EEE 36 is the non-transitory computer readable medium of any one of EEEs 25-35, wherein the displayed image shows at least a portion of the vehicle component.
This application is a continuation application of U.S. patent application Ser. No. 17/938,267, filed on Oct. 5, 2022. U.S. patent application Ser. No. 17/938,267 published on Feb. 2, 2023 as United States Patent Application Publication number 2023/0034993 A1. U.S. patent application Ser. No. 17/938,267 is a continuation application of U.S. patent application Ser. No. 17/497,055, filed on Oct. 8, 2021. U.S. patent application Ser. No. 17/497,055 published on Jan. 27, 2022 as United States Patent Application Publication number 2022/0027023 A1 and issued as U.S. Pat. No. 11,507,254. U.S. patent application Ser. No. 17/497,055 is a continuation application of U.S. patent application Ser. No. 16/993,223, filed on Aug. 13, 2020. U.S. patent application Ser. No. 16/993,223 published on Nov. 26, 2020 as United States Patent Application Publication number 2020/0371650 A1 and issued on Jan. 11, 2022 as U.S. Pat. No. 11,221,738. U.S. patent application Ser. No. 16/993,223 is a continuation application of U.S. patent application Ser. No. 16/542,262, filed on Aug. 15, 2019. U.S. patent application Ser. No. 16/542,262 published on Dec. 5, 2019 as United States Patent Application Publication number US 2019/0369821 A1 and issued on Nov. 24, 2020 as U.S. Pat. No. 10,845,961. U.S. patent application Ser. No. 16/542,262 is a continuation application of U.S. patent application Ser. No. 15/286,169 filed Oct. 5, 2016. U.S. patent application Ser. No. 15/286,169 published as United States Patent Application Publication number US 2018/0095609 A1 on Apr. 5, 2018 and issued on Oct. 1, 2019 as U.S. Pat. No. 10,430,026. U.S. patent application Ser. No. 15/286,169 and United States Patent Application Publication number US 2018/0095609 A1 are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17938267 | Oct 2022 | US |
| Child | 18584211 | US | |
| Parent | 17497055 | Oct 2021 | US |
| Child | 17938267 | US | |
| Parent | 16993223 | Aug 2020 | US |
| Child | 17497055 | US | |
| Parent | 16542262 | Aug 2019 | US |
| Child | 16993223 | US | |
| Parent | 15286169 | Oct 2016 | US |
| Child | 16542262 | US |
