CN113424234A

CN113424234A - Vehicle scanning tool auto-initialization

Info

Publication number: CN113424234A
Application number: CN201980091672.9A
Authority: CN
Inventors: P·S·默根; R·S·布罗佐维奇; J·G·福尔曼; B·A·凯利
Original assignee: Sinabo
Current assignee: Sinabo; Snap On Inc
Priority date: 2018-12-11
Filing date: 2019-12-11
Publication date: 2021-09-21
Also published as: WO2020123608A1; EP3895087A1

Abstract

In one embodiment, a method includes receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. Based on the background information, the method includes determining a vehicle scanning tool function to be performed on the vehicle. The method also includes identifying a vehicle scanning tool associated with the user identifier. The method also includes causing a selectable vehicle scanning tool initialization option to be displayed on the computing device. The method also includes receiving, from the computing device, a selection of a selectable vehicle scanning tool initialization option. In response to receiving the selection, the method additionally provides an indication to initialize the vehicle scanning tool to perform a vehicle scanning tool function on the vehicle.

Description

Vehicle scanning tool auto-initialization

Cross Reference to Related Applications

The present application claims rights to U.S. patent application No. 16/216354 filed on 12/11/2018, U.S. patent application No. 16/216366 filed on 12/11/2018, and U.S. patent application No. 16/216388 filed on 12/11/2018. U.S. patent application No. 16/216354, U.S. patent application No. 16/216366, and U.S. patent application No. 16/216388 are all incorporated herein by reference in their entirety.

Background

Most vehicles are serviced at least once during their service life. In many cases, the vehicle is serviced in a facility having a specialized mechanic (e.g., technician). Technicians may use various non-computerized hand tools to service (e.g., repair) various mechanical components on a vehicle. The technician may also use a computerized vehicle scanning tool to electronically communicate with the vehicle, test the vehicle or collect diagnostic information of the vehicle. When servicing a vehicle, technicians sometimes obtain information to diagnose and/or service the vehicle. Such diagnostic information may be viewed by a technician on a computer workstation located at a different location in the facility than the vehicle. The technician may print the relevant diagnostic information from the workstation and then return the printed material to the vehicle. The technician may then use the printed material to manually configure the vehicle scanning tool to perform the function of the vehicle. Islanding of information between different computing devices in a plant (e.g., workstations and vehicle scanning tools) can lead to inefficiencies in the time it takes for a technician to maintain a vehicle in the facility.

Disclosure of Invention

Several examples are depicted herein relating to vehicle scanning tool auto-initialization. Some examples involve supplementing vehicle maintenance content with an alternative link that initializes the vehicle scan tool. Other examples involve locating available vehicle scanning tools and transmitting information to the vehicle scanning tools to initialize the vehicle scanning tools to perform context dependent (contextual reusable) vehicle maintenance functions. However, further examples relate to a vehicle scanning tool configured to receive a vehicle scanning tool auto-initialization request and take action on the request based on a current operating state of the vehicle scanning tool.

Viewed from one aspect, the example embodiments take the form of a method. The method includes receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. The method also includes determining a vehicle scanning tool function to be performed on the vehicle based on the context information. The method also includes determining a vehicle scanning tool associated with the user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier. The method additionally includes causing a selectable vehicle scanning tool initialization option to be displayed on the computing device. The method also includes receiving, from the computing device, a selection of a selectable vehicle scanning tool initialization option. The method additionally includes, in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, the example embodiments take the form of a system. The system includes a computing device, at least one vehicle scanning tool, and a server. The server is configured to receive from the computing device (i) a user identifier, (ii) a vehicle identifier for the vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. The server is further configured to determine a vehicle scanning tool function to be performed on the vehicle based on the context information. The server is further configured to identify a vehicle scanning tool associated with the user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier. The server is additionally configured to cause a selectable vehicle scanning tool initialization option to be displayed on the computing device. The server is further configured to receive a selection of a selectable vehicle scan tool initialization option from the computing device. The server is further configured to, in response to receiving the selection, provide an indication of selection of a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, example embodiments take the form of a non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors to cause a computing system to perform functions. The functions include receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. The functions also include determining a vehicle scanning tool function to be performed on the vehicle based on the context information. The functions also include determining a vehicle scanning tool associated with the user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier. The functionality additionally includes causing selectable vehicle scan tool initialization options to be displayed on the computing device. The functions also include receiving, from the computing device, a selection of a selectable vehicle scanning tool initialization option. The functions also include, in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, the example embodiments take the form of a system. The system includes means for receiving from the computing device (i) a user identifier, (ii) a vehicle identifier for the vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. The system also includes means for determining a vehicle scanning tool function to be performed on the vehicle based on the context information. The system additionally includes means for identifying a vehicle scanning tool associated with the user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier. The system also includes means for causing a selectable vehicle scanning tool initialization option to be displayed on the computing device. The system also includes means for receiving a selection of a selectable vehicle scanning tool initialization option from the computing device. The system additionally includes means, responsive to receiving the selection, for providing an indication of selection of a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, the example embodiments take the form of a method. The method includes receiving, by a computing device, textual vehicle maintenance content. The method also includes identifying, by the computing device, a vehicle scanning tool function related to relevant text at a location within the textual vehicle maintenance content. The method additionally includes modifying, by the computing device, the textual vehicle maintenance content to include a selectable link at the location of the relevant text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle. The method also includes providing, by the computing device, modified textual vehicle maintenance content including the selectable link.

Viewed from another aspect, the example embodiments take the form of a system. The system includes a vehicle scanning tool and a computing device. The computing device is configured to receive textual vehicle maintenance content. The computing device is also configured to identify vehicle scanning tool functions related to relevant text at a location within the textual vehicle maintenance content. The computing device is further configured to modify the textual vehicle maintenance content to include a selectable link at the location of the relevant text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle. The computing device is additionally configured to provide modified textual vehicle maintenance content including the selectable link.

Viewed from another aspect, example embodiments take the form of a non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors to cause a computing system to perform functions. The function includes receiving textual vehicle maintenance content. The functions also include identifying a vehicle scanning tool function associated with associated text at a location within the textual vehicle care content. The functions also include modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text, wherein the selectable link is selectable to initiate the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle. The functionality additionally includes providing modified textual vehicle maintenance content including the selectable link.

Viewed from another aspect, the example embodiments take the form of a system. The system includes means for receiving textual vehicle maintenance content. The system also includes means for identifying a vehicle scanning tool function associated with associated text at a location within the textual vehicle care content. The system additionally includes means for modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text, wherein the selectable link is selectable to initiate the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle. The system also includes means for providing modified textual vehicle maintenance content including the selectable link.

Viewed from another aspect, the example embodiments take the form of a method. The method includes receiving, at a vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool, the request including a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier. The method also includes determining a current operating state of the vehicle scanning tool. Based on the current operating state of the vehicle scanning tool, the method further includes making a decision to initialize the vehicle scanning tool according to a request for automatic initialization of the vehicle scanning tool. In response to making the determination, the method additionally includes using the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, an example embodiment takes the form of a vehicle scanning tool. The vehicle scanning tool includes a control system configured to receive a request for automatic initialization of the vehicle scanning tool, the request including a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier. The control system is further configured to determine a current operating state of the vehicle scanning tool. Based on the current operating state of the vehicle scanning tool, the control system is further configured to make a decision to initialize the vehicle scanning tool according to a request for automatic initialization of the vehicle scanning tool. In response to making the determination, the control system is additionally configured to use the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, example embodiments take the form of a non-transitory computer-readable medium having instructions stored therein, the instructions being executable by one or more processors to cause a computing system to perform functions. The functions include receiving, at a vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool, the request including a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier. The functions also include determining a current operating state of the vehicle scanning tool. Based on the current operating state of the vehicle scanning tool, the function additionally includes making a decision to initialize the vehicle scanning tool in accordance with a request for automatic initialization of the vehicle scanning tool. In response to making the determination, the functions further include using the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

Viewed from another aspect, an example embodiment takes the form of a vehicle scanning tool. The vehicle scanning tool comprises means for receiving, at the vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool, the request comprising a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions comprising the vehicle scanning tool function and selected from a plurality of vehicle identifiers comprising the vehicle identifier. The vehicle scanning tool further comprises means for determining a current operating state of the vehicle scanning tool. Based on the current operating state of the vehicle scanning tool, the vehicle scanning tool additionally comprises means for making a decision to initialize the vehicle scanning tool according to a request for automatic initialization of the vehicle scanning tool. In response to making the determination, the vehicle scanning tool further includes means for using the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

These and other aspects and advantages will be apparent to those of ordinary skill in the art upon reading the following detailed description, with reference where appropriate to the accompanying drawings. Furthermore, it should be understood that the embodiments described in this summary and elsewhere are examples only and do not necessarily limit the scope of the invention.

Drawings

Example embodiments are described herein with reference to the accompanying drawings.

FIG. 1 is a schematic diagram illustrating an example operating environment in which example embodiments may operate.

FIG. 2 is a schematic view of a vehicle showing an example placement of a vehicle scanning tool.

FIG. 3 illustrates example vehicle maintenance information displayed on a computing device.

FIG. 4 illustrates example vehicle maintenance information and selectable links displayed on a computing device.

FIG. 5 illustrates an example vehicle maintenance information and deactivated selectable link displayed on a computing device.

FIG. 6 illustrates a listing of example vehicle maintenance information, selectable links, and vehicle scanning tool identifiers displayed on a computing device.

FIG. 7 is a flow diagram depicting a set of functions that may be performed in accordance with an example embodiment.

FIG. 8 is a block diagram of an example server.

Fig. 9 is a diagram illustrating example mapping data, according to an example embodiment.

FIG. 10 is a diagram illustrating an example index, according to an example embodiment.

FIG. 11 is a schematic diagram illustrating symptom-to-part mapping data in accordance with an example embodiment.

FIG. 12 is a diagram illustrating example mapping data, according to an example embodiment.

Fig. 13 is a diagram illustrating additional example mapping data according to an example embodiment.

FIG. 14 illustrates an example PID index.

FIG. 15 illustrates an example component test index.

FIG. 16 illustrates an example functional test index.

FIG. 17 illustrates an example reset procedure index.

Fig. 18 shows an example of component hierarchy data.

Fig. 19 is a communication flow diagram in accordance with an example embodiment.

Fig. 20 is another communication flow diagram in accordance with an example embodiment.

Fig. 21 is an additional communication flow diagram in accordance with an example embodiment.

FIG. 22 is another flow diagram depicting a set of functions that may be performed in accordance with an example embodiment.

FIG. 23 illustrates an example user profile.

FIG. 24 is an example menu configuration for a vehicle scanning tool.

FIG. 25 is another flow diagram depicting a set of functions that may be performed in accordance with an example embodiment.

FIG. 26 is an illustration of an initialized vehicle scanning tool, according to an example embodiment.

FIG. 27 is a block diagram of an example vehicle scanning tool.

FIG. 28 is a functional block diagram illustrating a computing system arranged in accordance with at least some example embodiments.

FIG. 29 is a schematic diagram illustrating a conceptual partial view of a computer program product for executing a computer process on a computing system, according to an example embodiment.

Detailed Description

Vehicle maintenance information is often referenced by technicians when servicing a vehicle. Such information may be Original Equipment Manufacturer (OEM) content provided by the manufacturer of the vehicle or vehicle component. Examples of OEM content include vehicle maintenance procedures, vehicle specifications, shop manuals, repair manuals, technical service bulletins, and wiring diagrams. The skilled artisan may also refer to non-OEM content from other vendors. Prior to or during servicing of the vehicle, a technician may view vehicle servicing content on a computer workstation. In some examples, the vehicle maintenance content may be retrieved by searching on a search device, which may be a computer workstation, a tablet computer, or a different computing device at a repair shop. An example search query may include identification information for a vehicle type, and one or more symptom descriptors corresponding to symptoms exhibited by a vehicle to be serviced. The symptom descriptors may be Diagnostic Trouble Codes (DTCs) that are used by the manufacturer to identify different types of vehicle issues. Upon entering the search query, the technician may be presented with one or more relevant segments of vehicle maintenance information to assist in maintaining the vehicle.

To service a vehicle, a technician may use a vehicle scanning tool, which is a computing device configured to communicate with the vehicle to perform one or more vehicle service functions on the vehicle. These communications may involve sending and/or receiving vehicle data messages to the vehicle via a wired and/or wireless connection with the vehicle. Example vehicle service functions that may be performed on a vehicle using a vehicle scanning tool include functional testing, component testing, and reset procedures. These vehicle maintenance functions may involve transmitting or multiple messages to the vehicle to test components or systems on the vehicle. In some cases, one or more messages representing the test results may be subsequently received by the scanning tool from the vehicle. In a further example, a vehicle maintenance function performed using the vehicle scanning tool may include retrieving data from a vehicle. Such data may include Parameter Identifier (PID) values.

To use a vehicle scanning tool on a vehicle, a technician typically must determine the scanning tool function to perform and also navigate to that function within one or more user-navigable menus on the vehicle scanning tool. However, the technician may not be aware of the relevant scan tool functions to be performed on a vehicle exhibiting a particular set of symptoms. Additionally, a technician may not be able to easily determine the relevant scan tool functionality by viewing the printed output of the OEM vehicle maintenance content. Furthermore, once the relevant scan tool function is identified by the technician, the technician may need to navigate through a complex series of navigable menus (e.g., involving 20 or 30 navigation steps) to configure the vehicle scan tool to perform that function on a given vehicle. These challenges may lead to sub-optimal selection of scan tool functions and/or inefficient utilization of technician time at the repair shop.

Example embodiments described herein relate to initialization of automated vehicle scanning tools. More particularly, embodiments relate to providing user-selectable options for automatically configuring a vehicle scanning tool to perform related scanning tool functions. The user-selectable options may be presented to the technician on a display of a computing device separate from the vehicle scanning tool. For example, the computing device may be a computer workstation or tablet computer configured to display OEM content. In other examples, the computing device may be another piece of shop equipment, such as a wheel aligner (e.g., alignment rack and display interface). After the technician selects the user-selectable option, the vehicle scanning tool may be automatically configured to perform the associated vehicle maintenance function. In some cases, the technician can then initiate performance of the vehicle service function using a single entry (e.g., a single click) at the vehicle scanning tool.

To supplement textual vehicle maintenance content (such as OEM content), the content may first be processed to identify scan tool functionality associated with text in the OEM content. When the relevant scan tool functionality is identified, the OEM content may be modified to include a selectable link that initializes the vehicle scan tool. For example, modifying OEM content may involve converting a portion of text to a selectable link, or adding a selectable link in the vicinity of the text. In this case, the vicinity may be defined as being within a given distance, e.g. 1 centimeter from the text, or within a given distance based on the height of the text, e.g. a distance equal to twice the average height of the text. Other examples are possible. In some examples, the relevant scan tool functions may be identified by identifying the particular scan tool function referenced by a name in the OEM content. In a further example, a previously determined relationship or mapping may be used to determine which scan tool functions to introduce at corresponding points in the OEM content. Example mappings include component-to-function mappings and symptom-to-component mappings. The hierarchy of vehicle components may also be used to locate the relevant scan tool functions. The temporal phase of the procedure described by a given section of OEM content may also be considered to determine what scan tool functionality to introduce. More generally, OEM content may be modified using context awareness to introduce vehicle scanning tool initialization links at determined points within the OEM content.

At run-time, the selectable links within the OEM content may be modified based on vehicle scanning tools available to the technician or shop floor. More specifically, a technician profile describing scan tools available to a technician and corresponding scan tool capabilities may be referenced in order to determine whether the technician may access a scan tool that may perform the relevant scan tool function. If a scan tool is available that can perform a particular maintenance function, a selectable link within the OEM content that is replenished may be activated. Otherwise, the selectable link may be deactivated and a message may be provided to the technician, such as a suggestion to obtain the associated scanning tool or a sales quote for a scanning tool capable of performing a given maintenance function. If multiple scan tools are available, a drop down list of scan tools may be presented to allow a technician to select a scan tool to initialize. In some examples, a hierarchy of configuration files may be traversed to locate an associated scan tool. For example, if the technician's profile does not contain a scanning tool that can perform a particular vehicle maintenance function, a shop profile describing the scanning tools available at the repair shop may be searched to locate the appropriate scanning tool. The presentation of selectable links may be dynamically adjusted based on the current availability of the scanning tool and/or the current connection status of the scanning tool with the corresponding vehicle.

When a vehicle scan tool initialization link is selected by a technician, an indication including a request for automatic initialization of the vehicle scan tool may be sent to the selected scan tool in order to initialize the scan tool to perform the associated scan tool function. The indication may include a vehicle identifier for the vehicle and a function identifier for the scan tool function. In some examples, an identifier for the vehicle component and/or system involved in the scan tool function may also be included in the indication. In some cases, the text of the selectable link may be parsed at runtime and converted into a format that is understandable by the particular vehicle scanning tool to be initialized. Once sent to the scan tool, the indication may automatically initialize the vehicle scan tool based on the function identifier and the vehicle identifier so that a technician does not have to manually navigate through multiple menus to set up the scan tool.

The vehicle scanning tool may be configured with a set of rules to process incoming vehicle initialization requests. More specifically, the current operating state of the vehicle scanning tool may be determined and then used to determine how to take action for a given initialization request. Example operating states of the scan tool include: off, on but not connected to any vehicle, connected to a vehicle but not performing any function, and in use. In some examples, the scan tool may monitor for a scan tool initialization request message when the scan tool is turned on. If the scan tool receives such a message when the scan tool has not been connected to a different vehicle and has not performed a vehicle maintenance function, the scan tool may automatically configure itself to perform the requested scan tool function (e.g., so that a technician may initiate the scan tool function with a single click). Conversely, if the scanning tool is connected to a different vehicle or has performed a vehicle maintenance function, the scanning tool may be configured to present a customized message to the user indicating that the function has been requested without initializing the scanning tool. The user may then leave the current activity and/or vehicle to initialize the scanning tool for the requested function. In a further example, one or more scan tool initialization requests for one or more vehicles sent to the scan tool may be queued on the scan tool for later invocation.

Prior to initializing the scanning tool in response to the scanning tool initialization request, the scanning tool may verify that the vehicle identifier in the scanning tool initialization request matches the vehicle identifier of the vehicle to which the scanning tool is currently connected. If the identifiers do not match, the scanning tool may be configured to present a message identifying the vehicle to which the scanning tool should be connected to allow the scanning tool to perform the requested function. In some examples, the vehicle identifier may be the year, make, model, and engine (YMME) of the vehicle. In other examples, the vehicle identifier may also or alternatively include a Vehicle Identification Number (VIN), an associated repair order identifier, and/or a license plate number.

After the scan tool determines to take action on the vehicle scan tool initialization request, the scan tool may automatically configure itself to perform the requested scan tool function on the identified vehicle. Such automatic configuration may involve the scanning tool parsing an extensible markup language (XML) stream or other type of data stream from a scanning tool initialization request to obtain the required vehicle information and scanning tool functionality information. The user may then be presented with the option to initiate the requested scan tool function on the identified vehicle. In a further example, a cookie crumb trail may also be displayed on the vehicle scanning tool, displaying different levels containing vehicle information and/or components of scanning tool functionality information that are automatically selected during the scanning tool auto-initialization process. Cookie trails may provide the technician with an intuitive understanding of the effect of the scan tool auto-initialization process. The cookie trail may also allow a technician to navigate, for example, to perform related vehicle maintenance functions on the vehicle.

Once the vehicle scan tool has been initialized, the technician may provide an entry to cause the scan tool to initiate the requested scan tool function on the vehicle. In some cases, only a single entry (e.g., a click or voice confirmation) may be required to initiate one or more functions. The scan tool may then communicate with the vehicle to perform this function. In some cases, data representing the results of the function may be received by the scanning tool from the vehicle. This data may be displayed within the OEM content being replenished (e.g., near the selected link that caused the scan tool to be initialized). In a further example, certain types of functions (such as collecting PID data) may not require user confirmation at all if the scanning tool is already connected to the vehicle. Alternatively, such functionality may be performed automatically by the scan tool after the technician selects a link from the OEM content.

According to examples described herein, some different types of computing devices may be used as a master device that provides context to identify relevant vehicle scanning tool functions and displays selectable options that allow the vehicle scanning tool to be automatically initialized. As described above, the host device may be a computer workstation or tablet configured to display OEM content that has been supplemented with selectable links. In other examples, the option to initialize the vehicle scanning tool may be presented at another piece of shop equipment. In particular, the wheel aligner may display an option to initialize the vehicle scanning tool after certain steps of a vehicle maintenance program have been performed on the vehicle using the wheel aligner. Other types of computing devices in the plant may also act as the master device. In such a case, the option to initialize the vehicle scanning tool may be presented in some other format than a selectable link, such as a yes/no question or a drop down menu with a number of context-dependent vehicle scanning tool functions to select from. In further examples, the master device may be the vehicle scanning tool itself or a different vehicle scanning tool.

Example embodiments described herein include functions performed at a server, which may be located at a repair shop or may be remote from the repair shop. The server may communicate with the host device to identify relevant context information in order to present an option to initialize the scanning tool to perform relevant vehicle maintenance functions on the vehicle. The server may also communicate with the scanning tool to provide an indication that the scanning tool is properly initialized to perform the associated vehicle maintenance function. In some examples, a server may first prepare a selectable link for OEM content during a first period of time, and then the same server or a different server may manage the presentation of the link and initialization of the vehicle scanning tool during a second period of time. In other examples, these functions may all be performed during the same time period.

In additional examples, some or all of the functions described herein as being performed by a server may be performed by different computing devices. In particular, it is expressly contemplated that some or all of the functions associated with identifying the associated scan tool functions and providing an indication to initialize the scan tool may be performed by a master device that displays scan tool initialization options to a technician. For example, the master device may be a search device that displays OEM content to a technician in response to a search query. The search device itself may supplement the OEM content with selectable links, manage presentation of information based on available scanning tools, and/or communicate directly with the scanning tools to initialize the scanning tools to perform related vehicle maintenance functions.

In still further examples, the vehicle maintenance content may include non-OEM content generated by an entity other than the vehicle manufacturer. For example, a manufacturer of a vehicle scanning tool that does not produce a vehicle may generate non-OEM content (such as real repair tips) to guide a technician based on previous vehicle maintenance instances. The real repair tip may, but need not, include data based on complaints, causes, and corrections listed on a repair order generated by a repair shop. The real repair tip may be modified to include a selectable link corresponding to the scan tool function that may be used to confirm that the causes listed on the real fault tip apply to different vehicles, but of the same year, make and model. The real repair tip may be modified to include a selectable link corresponding to a scan tool function that may be used to perform the corrections listed on the real repair tip for a different vehicle or to confirm that the corrections listed on the repair tip that were performed on a different vehicle actually repaired a different vehicle.

FIG. 1 is a schematic diagram illustrating an example operating environment 1 in which example embodiments may operate. The operating environment 1 comprises a server 2, a communication network 3, a vehicle scanning tool 4,

communication links

5, 6 and 7, a repair shop 8, a vehicle 9 and a master device 10.

Communication network 3 may include

communication links

5, 6, and 7 as well as other communication links (not shown). The communication network 3 and the

communication links

5, 6 and 7 may include various network components such as switches, modems, gateways, antennas, cables, transmitters and/or receivers. The communication network 3 may include a Wide Area Network (WAN). The WAN may piggyback data using packet-switched and/or circuit-switched technologies. The WAN may include an air interface or line to carry data. The communication network 3 may include a network or at least a part of a network that performs communication using a Transmission Control Protocol (TCP) and an Internet Protocol (IP), such as a communication network generally called the internet.

The repair shop 8 may include various shop tools such as a brake lathe, a wheel aligner, a wheel balancer, and/or diagnostic equipment for diagnosing the vehicle. The shop tool may include a vehicle scanning tool 4. As shown in fig. 1, the vehicle scanning tool 4 is positioned within a repair shop 8. However, the vehicle scanning tool 4 may be operated inside and/or outside the repair shop 8. For example, the vehicle scanning tool 4 may be used within the vehicle 9 while the vehicle 9 is traveling on a road outside the repair shop 8 for any of a variety of purposes. The server 2 may be scaled to be able to service any number of vehicle scanning tools, such as one vehicle scanning tool (as shown in fig. 1), one hundred vehicle scanning tools, one thousand vehicle scanning tools, or some other number of vehicle scanning tools.

A vehicle, such as vehicle 9, is a mobile machine that may be used to transport people, or cargo. As an example, the vehicles discussed herein may be driven along a road (e.g., a paved road or otherwise) and/or otherwise guided in land, water, air, or outer space. As another example, the vehicles discussed herein may be wheeled, tracked, or skiing. As yet another example, the vehicles discussed herein may include automobiles, motorcycles, All Terrain Vehicles (ATVs) as defined by ANSI/SVIA-1-2007, snowmobiles, personal water motorcycles (e.g., JET)

Personal water motorcycle), a light truck, a medium truck, a heavy truck, a semi-tractor, or an agricultural machine. As an example, the vehicle guided along the path may comprise a truck (such as a dry goods or refrigerated truck), a tank trailer, a flatbed trailer, or a motor vehicle. As yet another example, the vehicles discussed herein may include or use any suitable voltage or current source, such as a battery, alternator, fuel cell, etc., that provides any suitable current or voltage (such as about 12 volts, about 42 volts, etc.). As yet another example, the vehicles discussed herein may include or utilize any desired system or engine. These systems or engines may include items that use fossil fuels (such as gasoline, natural gas, propane, etc.), electricity (such as that generated by batteries, magneto, fuel cells, solar cells, etc.), wind, and hybrid power, or combinations thereof. As yet another example, any of the vehicles discussed herein may include an ECU, a Data Link Connector (DLC), and a vehicle communication link connecting the DLC to the ECU.

Vehicle manufacturers may manufacture different numbers of vehicles per calendar year (e.g., 1 month, 1 day to 12 months, 31 days). In some cases, the vehicle manufacturer defines the model year for the particular vehicle model to be manufactured. The model year may start on a date other than 1 month and 1 day, or may end on a date other than 12 months and 31 days. Model years may span portions of two calendar years. A vehicle manufacturer may make one vehicle model or a plurality of different vehicle models. Two or more different vehicle models made by a vehicle manufacturer within a particular calendar year may have the same or different defined model years. A vehicle manufacturer may manufacture a vehicle of a particular vehicle model with different vehicle options. For example, a particular vehicle model may include a vehicle with a six cylinder engine and a vehicle with an eight cylinder engine. A vehicle manufacturer or other entity may define a vehicle identifier for each vehicle manufactured by the vehicle manufacturer. The particular vehicle identifier may identify a particular set of vehicles (e.g., all vehicles of a particular vehicle model for a particular vehicle model year or all vehicles of a particular vehicle model year with a particular set of one or more vehicle options).

As an example, the particular vehicle identifier may include an indication of a characteristic of the vehicle, such as when the vehicle was built (e.g., vehicle model year), who built the vehicle (e.g., vehicle manufacturer (i.e., vehicle manufacturer)), a marketing name associated with the vehicle (e.g., vehicle model name, or more simply "model"), and a characteristic of the vehicle (e.g., engine type). According to this example, a particular vehicle identifier may be referred to by the acronym YMME or Y/M/E, where each letter in the order shown represents a model year identifier, a vehicle manufacturer identifier, a vehicle model name identifier, and an engine type identifier, respectively, or by the acronym or Y/M, where each letter in the order shown represents a model year identifier, a vehicle manufacturer identifier, and a vehicle model name identifier, respectively. Example Y/M/M/E is 2004/Toyota/Camry/4Cyl, where "2004" represents the model year of the vehicle, "Toyota" represents the name of Toyota Motor company, Toyota, Japan, "Camry" represents the model of the vehicle made by the manufacturer, and "4 Cyl" represents the engine type within the vehicle (i.e., a four-cylinder internal combustion engine). Those skilled in the art will appreciate that other characteristics in addition to or as an alternative to "engine type" may be used to identify a vehicle using a particular vehicle identifier. These other characteristics may be identified in various ways, such as a conventional production option (RPO) code, such as the RPO code defined by general automobile company, detroit, michigan.

The vehicle communication link within the vehicle may include one or more conductors (e.g., copper wire conductors) or may be wireless. As an example, the vehicle communication link may include one or two conductors for carrying vehicle data messages in accordance with a Vehicle Data Message (VDM) protocol. The VDM protocol may include an Society of Automotive Engineers (SAE) J1850(PWM or VPW) VDM protocol, an International organization for standardization (ISO)15764-4 Controller Area Network (CAN) VDM protocol, an ISO 9141-2K-Line VDM protocol, an ISO 14230-4KWP2000K-Line VDM protocol, or some other protocol currently defined for performing communications within a vehicle.

The ECU may control various aspects of vehicle operation or components within the vehicle. For example, the ECUs may include a Powertrain (PT) system ECU, an Engine Control Module (ECM) ECU, a supplemental air charge restraint (SIR) system (i.e., airbag system) ECU, an entertainment system ECU, or some other ECU. The ECU may receive inputs (e.g., sensor inputs), control output devices (e.g., solenoids), generate Vehicle Data Messages (VDMs), such as VDMs based on the received inputs or the controlled outputs, and set Diagnostic Trouble Codes (DTCs) as a valid or historical of detected faults or failure conditions within the vehicle. The functional test on the ECU or the execution of the reset procedure may include the vehicle scanning tool 4 transmitting a VDM to the vehicle. The VDM received at the ECU may include a PID request. The VDM transmitted by the ECU may include a response that includes PID and PID data values.

The host device 10 is a computing device with a display interface. The master device 10 may be configured to display vehicle maintenance information to a technician. The master device 10 may be located at the repair shop 8 near the vehicle 9, at the repair shop 8 but remote from the vehicle 9, or remote from the repair shop 8. In an example embodiment, the master device 10 is a computer workstation, a tablet computer, a smartphone, a search device, a wheel aligner, a different shop device, or a vehicle scanning tool.

Next, fig. 2 shows example details of the vehicle 9 and an example placement of the vehicle scanning tool 4 within the vehicle 9. In particular, FIG. 2 shows that the vehicle 9 includes an airbag system ECU 20, a traction control system ECU 21, a powertrain system ECU 22, an anti-lock braking system (ABS) ECU 23, and a DLC 24, each connected to a vehicle communication link 26. Other examples of ECUs within the vehicle 9 are possible. For example, the DLC 24 may be positioned within a passenger compartment of the vehicle 9, within an engine compartment of the vehicle 9, or within a storage compartment of the vehicle 9. The vehicle scanning tool 4 may include and/or be connected to the DLC 24 via a DLC-to-scanning tool communication link 25. The vehicle scanning tool 4 is typically removed after the vehicle 9 has been serviced at the repair shop 8. In this way, the vehicle scanning tool 4 can be used to service other vehicles after they arrive at the repair shop 8.

DLC 24 may include connectors, such as an OBD I connector, an OBD II connector, or some other connector. OBD II connectors may include slots for retaining up to 16 connector terminals, but may include a different number of slots or no slots at all. By way of example, the DLC connector may comprise an OBD II connector compliant with SAE J1962 specifications, such as connector 16M part number 12110252 available from Aptiv LLC of dublin, ireland. DLC 24 may include conductor terminations that connect with conductors in the vehicle. For example, DLC 24 may include connector terminals that connect to conductors that connect to the positive and negative poles of a vehicle battery, respectively. DLC 24 may include one or more conductor terminations that connect to conductors of a vehicle communication link, such that DLC 24 is operatively connected to an ECU within vehicle 9.

Next, fig. 3 illustrates an example of vehicle maintenance information displayed on the computing device. More specifically, display interface 30 is a display of a computing device configured to display vehicle maintenance information. The vehicle maintenance information may be OEM content from one or more vehicle or vehicle component manufacturers. The vehicle maintenance information may be textual information and/or may include other forms of media including image, video, and/or audio content. In some examples, the computing device is a stationary computer workstation at a repair shop, a mobile computing device (such as a touch pad device or a smartphone), a laptop, or a different type of computing device at a vehicle repair shop.

In some examples, the computing device may be a search device that provides vehicle maintenance information in response to a search query. Referring to FIG. 3, the display interface 30 includes prompts for a vehicle identifier 31 and a search query 33. In this example, the vehicle identifier 31 includes the year, make, model, and engine of the vehicle, and the vehicle identifier identifies the 2010 savory Colorado with a 5.3L engine. In other examples, the vehicle identifiers 31 may represent different sets of vehicles. In a further example, certain types of textual vehicle maintenance information may be universally applicable to multiple sets of vehicles. Additionally, in this example, the search query 33 is a vehicle symptom described by the DTC of P0446. In other examples, different types of search queries may be used, such as keyword searches. The display interface 30 additionally indicates a repair Shop 32, in this example a computing device located in Tuscany Shop 021.

In response to the search query 33, textual vehicle maintenance information 34 related to the DTC P0446 for the vehicle described by the vehicle identifier 31 may be presented to the technician on the display interface 30. In some examples, textual vehicle maintenance information 34 may be OEM content. Textual vehicle maintenance information 34 may be retrieved by the server and provided from the server to the computing device for display on display interface 30. In this example, the DTC descriptor and the circuit/system descriptor are included within the textual vehicle maintenance information 34. In further examples, various other types of maintenance information may also or alternatively be displayed. In some examples, textual vehicle maintenance information 34 may take the form of a scrollable website with multiple pages of vehicle maintenance information.

Next, FIG. 4 illustrates example vehicle maintenance information and selectable links displayed on a computing device. More specifically, in FIG. 4, the display interface 30 includes an associated scan tool function 35 that includes a selectable link that initiates the vehicle scan tool to perform a functional test named "Vent solenoid actuation". The functional test may be identified by the server as a context-dependent scan tool function to be included in the presented portion of the textual vehicle service information 34. If the technician clicks on the selectable link, the vehicle scanning tool may be automatically configured to perform a functional test on the vehicle.

In some examples, the presented selectable link to initialize the vehicle scanning tool to perform the functional test may be included within the textual vehicle maintenance information 34 at a point in time before the search query 33 is entered at the display interface 30. More specifically, the server may parse textual information in the OEM content and identify the context-dependent scan tool functionality for which the selectable link was introduced. OEM content that has been modified to include selectable links may be stored in a database. Subsequently, when OEM content is provided for display (e.g., on display interface 30), the presentation of selectable links may be adjusted based on currently available scanning tools for technicians and/or workshops.

At runtime, the server may evaluate the scan tools available to the technician by referencing a user profile associated with a user identifier (e.g., a technician identifier and/or a plant identifier). In particular, the technician may be identified as logged into the computing device displaying the OEM content. A technician identifier for a technician may be used to locate a technician profile describing registered vehicle scanning tools and corresponding scanning tool capabilities. Referring to FIG. 4, a vehicle scanning tool VST1 may be identified as an available vehicle scanning tool for a technician logging in and providing a search query at display interface 30. Additionally, a technician profile containing VST1 may indicate that VST1 is capable of performing a "vent solenoid actuated" functional test on a vehicle described by vehicle identifier 31. Accordingly, the selectable link for the functional test may be activated within the displayed OEM content and may present the option of sending the functional test to VST 1. In a further example, if the technician profile for the technician does not include a vehicle scanning tool capable of performing functional testing, the shop profile may be referenced instead. For example, the VST1 may be a tool available at the repair shop 32 that is capable of performing functional tests.

Upon selection of the selectable link by the technician, the server may transmit an indication to initialize the VST1 for performing a "vent solenoid actuated" functional test on the vehicle described by the vehicle identifier 31. The indication may include the vehicle identifier 31 and an identifier for the functional test. The indication may additionally include an identifier for the vehicle system or component to be tested (e.g., the EVAP system). In some examples, these indications may be specifically generated in a format that may be interpreted by VST 1. In particular, the server may parse the text of the previously inserted selectable link and convert the information (e.g., vehicle identifier, test identifier, and/or system/component identifier) into a customized message for transmission to the VST 1.

Next, FIG. 5 illustrates example vehicle maintenance information and a selectable link to deactivation displayed on a computing device. More specifically, the server may determine that no vehicle scan tool associated with the technician may perform the "vent solenoid actuated" functional test. Thus, the presentation of a selectable link within the associated scan tool function 35 may be adjusted so that the link cannot be selected by the technician. The appearance of the link may be dynamic such that if a vehicle scan tool that can perform a functional test is available to the technician, the link will again become active within the display interface 30.

In some examples, the selectable links that have been added to the OEM content may be visible even when no available scanning tools may be initialized to perform vehicle maintenance functions. Thus, a technician may be notified of the presence of the associated vehicle scan tool functionality when reviewing OEM content. In a further example, the messages presented to the technician may be adjusted to include sales offers for vehicle scanning tools that may perform the relevant scanning tool functions.

Next, FIG. 6 illustrates a list of example vehicle maintenance information, selectable links, and vehicle scanning tool identifiers displayed on a computing device. More specifically, where multiple vehicle scanning tools associated with a technician are identified as being available and capable of performing the associated vehicle scanning tool function, a selectable list of vehicle scanning tool identifiers corresponding to the vehicle scanning tools may be presented to allow the technician to select the vehicle scanning tool to be initialized. Referring to fig. 6, three vehicle scanning tool identifiers are presented as options: VST1, VST2 and VST 3. Each of these three vehicle scanning tools is capable of performing a "vent solenoid actuation" test on a vehicle identified by the vehicle identifier 31. To send a functional test to the scan tool, the technician may need to select a vehicle scan tool identifier from a list of available options to initialize the vehicle scan tool.

In a further example, when multiple vehicle scanning tools are available and are capable of performing an associated vehicle maintenance function, a vehicle scanning tool may be automatically selected from the available scanning tools. In some examples, a vehicle scanning tool with the highest level of capability to perform vehicle maintenance functions may be selected and presented to the user within the OEM content. For example, the capability level may be based on which scan tool from the set of available scan tools has the latest software version installed.

In additional examples, a vehicle scanning tool may be automatically selected based on a vehicle connection status. For example, if there is a vehicle scanning tool already connected to the vehicle to be serviced, the vehicle scanning tool may be automatically selected for initialization. If no vehicle scanning tool has been connected to a vehicle, a vehicle scanning tool that is not currently connected to any vehicle may be selected instead. In a further example, it may also or alternatively be considered whether each scan tool is currently performing a scan tool function when selecting between vehicle scan tools. In yet another example, when selecting vehicle scanning tools, future scheduling information for each vehicle scanning tool may be considered.

In a further example, rather than automatically selecting a single vehicle scanning tool for presentation to a technician, a list of multiple vehicle scanning tools may be prioritized based on various factors, including capability level, connection status, and activity status. In additional examples, some or all of these factors may be displayed within a list of vehicle scanning tools from which the technician may select a vehicle scanning tool to initialize.

In a further example, various different types of OEM content and other vehicle maintenance content may be supplemented with selectable links. In some examples, the OEM content may be or include wiring principles (e.g., ground locations, wiring locations, and/or components connected by wiring) that exhibit a portion of the vehicle. The wiring diagram may be modified to include selectable links in the wiring diagram corresponding to different vehicle components. Each selectable link may be selected to initialize a vehicle scanning tool to perform a respective vehicle scanning tool function associated with the corresponding vehicle component in the wiring diagram. For example, a selectable link in the wiring diagram may result in initialization of a scan tool to display PID data or perform tests related to components in the wiring diagram.

Next, fig. 7 shows a flow diagram depicting a set of functions 40 (or more simply "set 40") that may be performed in accordance with the example embodiments described in this specification. The set 40 includes functions shown in blocks labeled with integers 41 through 44 (inclusive). The following description of the set 40 includes references to elements shown in other figures described in this specification, but the function of the set 40 is not limited to being performed by only the referenced elements. The various methods may be performed using all of the functions shown in set 40 or any suitable subset of the functions shown in set 40. Any of these methods may be performed in conjunction with other functions, such as one or more of the other functions described in this specification. In some examples, the set 40 may be performed by a server (such as server 2 of fig. 1). In further examples, some or all of the set 40 may be performed by a different device (such as the master device 10 of fig. 1).

Block 41 includes receiving textual vehicle maintenance content. The textual vehicle maintenance content may be OEM content provided by a vehicle or component manufacturer. Vehicle maintenance content may include other forms of media besides textual information, including charts, pictures, videos, and the like. In some examples, the textual vehicle maintenance information may be received at some time prior to requesting viewing of the information. For example, OEM content from different sources may be received, processed, and customized to include selectable links. The customized OEM content may be stored in a database. The customized OEM content may later be retrieved from a database and provided in response to a search query or other viewing request. In other examples, textual vehicle maintenance content may be received in response to a request to view the content. In such an example, the content may be supplemented with selectable links and immediately provided for viewing on the display device.

Next, block 42 includes identifying vehicle scanning tool functionality associated with relevant text at a location within the textual vehicle maintenance content. In particular, the content may be processed to find context-dependent scan tool functionality for which selectable scan tool initialization links are provided at different points within the content. In some examples, particular vehicle scanning tool functions may be identified by name within the OEM content, and links may be inserted for these vehicle scanning tool functions. In other examples, the appropriate vehicle scanning tool functionality to be incorporated into the OEM content may be determined in some different manner.

In some examples, relevant vehicle scanning tool functions may be identified by reference to one or more predetermined and saved mappings. The mappings may be learned relationships and may include component-to-function mappings, symptom-to-component mappings, and/or other mappings described herein. In a further example, a hierarchy of vehicle components may also be referenced to determine context-dependent scan tool functionality. Temporal vehicle maintenance phases of vehicle maintenance programs associated with OEM content may also be considered to find an appropriate location to insert a link for the context-dependent scan tool functionality.

As an example, the OEM content may be an article regarding fuel injector testing. If the article refers by name to specific injector tests that may be performed by the vehicle scan tool, selectable links may be inserted for these tests. If no test is referenced, but the injector component is referenced by name, a component-to-function mapping may be used to locate the relevant scan tool function or test. In some examples, all relevant scan tool functions or tests for a component may be introduced as selectable links. In other examples, a maintenance program schedule may be considered to determine which scan tool functions or tests to introduce. The service schedule divides the vehicle service routine into a series of discrete time phases (e.g., pre-repair, and post-repair phases). The vehicle scan tool function can then be classified based on one or more process phases associated therewith in order to determine when to introduce the scan tool function. For example, if a portion of the article describes post-repair information for the injector and thus determines that the temporal vehicle maintenance phase is a post-repair maintenance phase, one or more selectable links to the reset procedure may be introduced at that point of the article.

In a further example, the vehicle component may not be referred to by name in the OEM content, but may refer to a symptom (e.g., a DTC or textual descriptor for the symptom). The symptom-to-component mapping can then be referenced to identify relevant vehicle components for the symptom. The component-to-function mapping can then be used to locate the appropriate scan tool function to introduce the selectable link. In these and other examples, the skilled artisan may not be aware of the relevant scan tool functions that may be available for execution on a vehicle associated with OEM content without the inserted link.

In an additional example, if a vehicle component is referenced by name but no suitable scan tool functionality exists for the component, the hierarchy of the component may be considered to locate the system to which the component belongs. System diagnostics (e.g., fuel system or ignition system) may then result in relevant vehicle scanning tool functionality to be introduced within the OEM content. More generally, multiple levels of the component hierarchy tree may be traversed up or down to locate the relevant scan tool function.

In a further example, the associated scan tool functionality introduced into the OEM content in the form of a selectable link may be a filtered PID list. In particular, if the article is about a fuel injector, a selectable link may be inserted that automatically sets a PID list of context-dependent PIDs for viewing on a vehicle scanning tool. The filtered PID list customized to the OEM content may allow a technician to quickly view the associated PID values without having to manually select the associated PID from a long list of available PIDs on the vehicle scanning tool.

Next, block 43 includes modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text. The selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle. In some examples, text within the OEM content may be converted directly into a selectable link (e.g., a hyperlink). In a further example, a selectable link may be inserted near or on the relevant text within the OEM content. The exact location and appearance of the selectable links may also vary.

Next, block 44 includes providing modified textual vehicle maintenance content including the selectable link. In some examples, the modified content may be provided to a display device to display the content and allow the link to be selected. In other examples, the modified content may instead be stored in a database and subsequently retrieved for display, e.g., in response to a search query that results in OEM content. In some examples, a first server may receive and supplement OEM content with selectable links, and a second server may then provide the supplemented OEM content for display and act upon selection of the selectable links to cause vehicle scanning tools to be automatically initialized to perform context-dependent vehicle maintenance functions.

Next, fig. 8 is a block diagram of the server 2. As shown in fig. 8, the server 2 includes a processor 50, a communication interface 51, and a memory 52. Two or more of these components may be communicatively coupled or linked together via a system bus, network, or other connection mechanism 53.

A processor, such as processor 50 or any other processor discussed in this specification, may include one or more processors. The processor may include a general-purpose processor (e.g.,

single-core microprocessor or

A multi-core microprocessor), or a special purpose processor such as a digital signal processor, a graphics processor, an embedded processor, or an Application Specific Integrated Circuit (ASIC) processor. The graphics processor may be configured to access and use the memory to create or retrieve data to be displayed on the displayA displayed GUI. The embedded processor may include a central processor chip for use in a system other than a general purpose workstation, a notebook computer, or a desktop computer. The processor may be configured to execute a Computer Readable Program Indication (CRPI). For example, the processor 50 may execute a CRPI 60 stored in the memory 52. The processor may be configured to perform hard-coded functions in addition to or as an alternative to software-coded functions (e.g., via CRPI). The at least one processor of the processor 50 may be programmed to perform any function or combination of functions described herein as being performed by the server 2.

Memory, such as memory 52 or any other memory discussed in this specification, may include one or more memories. The memory may include non-transitory memory, or both non-transitory memory and transitory memory. The non-transitory memory or a portion thereof may be located within the processor or as part of the processor (e.g., within a single integrated circuit chip). The non-transitory memory, or a portion thereof, may be separate and distinct from the processor.

The non-transitory memory may include volatile or non-volatile storage components, such as optical, magnetic, organic, or other memory or optical disk storage components. Additionally or alternatively, the non-transitory memory may include or be configured as Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), or compact disc read only memory (CD-ROM). The RAM may include static RAM or dynamic RAM.

The temporary memory may comprise, for example, a CRPI provided over a communication link, such as a communication link connected to or part of the communication network 3. The communication link may comprise a digital or analog communication link. The communication link may comprise a wired communication link or comprise one or more wires or conductors, or a wireless communication link comprising an air interface.

"memory" may be referred to by other terms, such as "computer-readable memory," computer-readable medium, "" computer-readable storage medium, "" storage device, "" memory device, "" computer-readable medium, "" computer-readable database, "" at least one computer-readable medium, "or" one or more computer-readable media. If the memory is transient, any of these alternative terms may be preceded by the prefix "transient"; if the memory is non-transitory, "non-transitory" may be added.

The memory 52 stores computer-readable data, such as a CRPI 60, an index 61, mapping data 62, Repair Order (RO) data 63, Diagnostic Session Data (DSD)64, a component hierarchy 65, original OEM content 66, supplemental OEM content 67, technician profiles 68, and/or shop floor profiles 69.

RO data 63 may include data from one or more ROs. The data for each RO may be stored in RO data 63 as a separate record relating to the set of vehicles being repaired at the repair shop. The RO data 63 may include RO data aggregated from a plurality of ROs. The RO data 63 may be used by the server 2 to generate any or all of the mapping data 62. The RO data 63 may include data from one or more ROs that indicate specific vehicle identification information, at least one symptom, and specific vehicle components. The server 2 may receive RO data indicating components actually replaced on the vehicle to repair the symptom recognized on the RO. The RO data 63 may comprise and/or be comprised in a computer readable file, such as an extensible markup language (XML) file.

DSD 64 may include data that server 2 may use to determine the operating state of vehicle scanning tool 4. The data used by the server 2 to determine the operational status of the vehicle scanning tool 4 may include a vehicle identifier, data indicating the elapsed time since the server 2 last received a communication from the vehicle scanning tool 4, data indicating the most recent type of scanning tool function transmitted to the vehicle scanning tool 4, and/or data indicating scanning tool functions that have been completed on a particular vehicle.

DSD 64 may include data indicative of the determined operating state of one or more vehicle scanning tools (such as vehicle scanning tool 4) identified in technician profile 68 and/or shop profile 69. Examples of operating states include (i) the vehicle scanning tool 4 being connected to the server 2 or (ii) the vehicle scanning tool 4 not being connected to the server 2 (i.e., disconnected from the server 2). More specifically, if the vehicle scanning tool 4 can receive a message from the server 2 via a wireless or other connection, the vehicle scanning tool 4 can be considered to be connected to the server 2. In some examples, a separate login at the vehicle scanning tool 4 may be required to initially connect to the server 2. In a further example, a periodic beacon signal may be sent from the server 2 to the vehicle scanning tool 4 to determine whether the vehicle scanning tool 4 is still connected to the server 2. Additional examples of operating states include (iii) the vehicle scanning tool 4 being connected to a particular vehicle (e.g., vehicle 9), (iv) the vehicle scanning tool 4 no longer being connected to (i.e., disconnected from) the particular vehicle, (v) the vehicle scanning tool 4 being in an auto-initialization mode for the particular vehicle, and (vi) the vehicle scanning tool 4 not being in an auto-initialization mode (e.g., being in a manual mode) for the particular vehicle. In some examples, the vehicle scanning tool 4 may be connected to a particular vehicle by a wiring harness or other physical connection. In other examples, the vehicle scanning tool 4 may be wirelessly connected to a particular vehicle.

DSD 64 may also include data indicating that the diagnostic session of vehicle scanning tool 4 is active or inactive. Server 2 may determine that a new diagnostic session is active upon receiving the vehicle identifier for the particular vehicle, while DSD 64 does not include data indicating that the diagnostic session for the particular vehicle is active. The server 2 may determine that an active diagnostic session for a particular vehicle has transitioned to inactive upon receiving a vehicle identifier for a different particular vehicle. The server 2 may determine that the active diagnostic session for the particular vehicle has transitioned to an inactive session when it is determined that a threshold time has elapsed since a particular activity of the active diagnostic session. As an example, the specific activity may include receiving a request from the vehicle scanning tool 4, receiving a communication indicating that the vehicle scanning tool 4 is connected to the communication network 3, and/or transmitting a response with scanning tool functionality to the vehicle scanning tool 4. Other examples of specific activities are possible.

CRPI 60 may include a number of program instructions. CRPI 60, and any other CRPI described in this specification, can include data structures, objects, programs, routines or other program modules that can be accessed and executed by a processor to perform a particular function or group of functions and are examples of program code for implementing steps for the methods described in this specification.

In general, CRPI 60 may include program instructions that cause server 2 to perform any of the functions described herein as being performed by server 2 or that cause any component of server 2 to perform any of the functions described herein as being performed by that component of server 2. As an example, CRPI 60 may include program instructions to perform the set of functions 40 shown in fig. 7 and/or the set of functions 150 shown in fig. 22.

As another example, CRPI 60 may include program instructions to perform session management with respect to vehicle scanning tool 4. Processor 50 may use DSD 64 to determine the operational status of vehicle scanning tool 4. Based on the operational state of vehicle scanning tool 4, processor 50 may provide vehicle scanning tool 4 with an indication to initialize the vehicle scanning tool to perform context-dependent scanning tool functions.

Upon and/or in response to determining that the vehicle scanning tool 4 has completed a vehicle scanning tool function on a particular vehicle, the processor 50 may provide a session change response to the vehicle scanning tool 4 to configure the vehicle scanning tool 4 to perform a previously provided scanning tool function or a different scanning tool function. The session change response may include a previously provided scan tool function or a different scan tool function. In some examples, a previously provided or different scan tool function may involve a different vehicle than the particular vehicle. In a further example, the session change response may cause vehicle scanning tool 4 to switch to a manual (e.g., user configurable) mode.

A communication interface (such as communication interface 51 or any other communication interface discussed in this specification) may include one or more communication interfaces. Each communication interface may include one or more transmitters configured to transmit data onto a network, such as communication network 3. The data transmitted by the communication interface 51 may include any data transmitted, output, and/or provided by the server 2 as described herein. Further, each communication interface may include one or more receivers configured to receive data piggybacked over a network, such as communication network 3. The data received by communication interface 51 may include any data or requests received by a server as described herein.

The transmitter may transmit a data-bearing radio signal and the receiver may receive a data-bearing radio signal. The communication interface with the transmitter and receiver may include one or more antennas and may be referred to as a "radio communication interface," an "RF communication interface," or a "wireless communication interface. The radio signals transmitted or received by the radio communication interface may be arranged in accordance with one or more wireless communication standards or protocols, such as WPAN, a standard of the Institute of Electrical and Electronics Engineers (IEEE)802.15.1, a standard specified by the bluetooth Special Interest Group (SIG) of corkland, washington

Release 4.1 standard, or the IEEE 802.11 standard for wireless LANs (sometimes referred to as

A standard), or a cellular wireless communication standard, such as a Long Term Evolution (LTE) standard, a Code Division Multiple Access (CDMA) standard, an Integrated Digital Enhanced Network (IDEN) standard, a global system for mobile communications (GSM) standard, a General Packet Radio Service (GPRS) standard, a Universal Mobile Telecommunications System (UMTS) standard, an enhanced data rates for GSM evolution (EDGE) standard, or a multi-channel multi-point distribution service (MMDS) standard.

Additionally or alternatively, the transmitter may transmit signals (i.e., one or more signals or one or more electrical waves) carrying or representing the data onto the line (e.g., one or more lines) and the receiver may receive the signals carrying or representing the data via the line. The line may be part of a network, such as a communication network 3. The signals piggybacked over the line may be arranged in accordance with a wired communication standard such as the transmission control protocol/internet protocol (TCP/IP), the IEEE 802.3 ethernet communication standard for LANs, the data over cable service interface specification (DOCSIS standard) such as DOCSIS 3.1, the USB specification (as previously described), or some other wired communication standard.

The data transmitted by the communication interface may include a destination identifier or address of the network device to which the data is to be transmitted. The data transmitted by the communication interface may include a source identifier or address of the system component that includes the communication interface. The source identifier or address may be used to send a response to a network device that includes a communication interface to send data.

A communication interface, such as communication interface 51, configured to perform communication over communication network 3 may include a modem, a network interface card, and/or a chip mountable on a circuit board. As an example, the chip may include CC3100 available from Texas instruments, Inc

Network processor, CC256MODx Bluetooth available from Texas instruments

Host Controller Interface (HCI) module and/or module for passing

Bluetooth

Or a different chip that communicates using other communication protocols.

The original OEM content 66 represents any type of vehicle maintenance information described herein, including textual vehicle maintenance information. The supplemental OEM content 67 represents OEM content that has been supplemented with one or more selectable vehicle scanning tools to initialize links. In some examples, the original OEM content 66 may be processed to generate the supplemental OEM content 67 at a point in time before the display of the supplemental OEM content 67 is required. In other examples, either the original OEM content 66 or the supplemental OEM content 67, or both, may not be stored in the memory 52. For example, OEM content may be retrieved from an external database in response to a request from a display device and may be replenished on-the-fly with an optional link prior to providing the replenished OEM content to the display device.

The memory 52 may also include one or more user profiles associated with the user identifiers. The one or more user profiles may include a technician profile 68 and/or a plant profile 69. The technician profile 68 includes data describing the vehicle scanning tools associated with the technician identifier for a particular plant technician or other user. The shop configuration file 69 includes data describing vehicle scanning tools associated with a particular vehicle repair shop or other facility. The technician profile 68 and/or the shop profile 69 may store information regarding the service capabilities of the different vehicle scanning tools to allow selection of an appropriate vehicle scanning tool to perform a vehicle maintenance function. The technician profiles 68 and the shop profile 69 may be arranged in a hierarchy such that the shop profile 69 includes data describing vehicle scanning tools for a plurality of different technicians. The hierarchy may also include other levels of configuration files.

Next, fig. 9 shows an example of the mapping data 62. As shown, mapping data 62 may include symptom-to-PID Mapping Data (MD)71, component-to-PID MD 72, symptom-to-component test MD 73, component-to-component test MD 74, symptom-to-function test MD 75, component-to-function test MD 76, symptom-to-reset procedure MD 77, and component-to-reset procedure MD 78. More specific examples of the aforementioned mapping data will be discussed below.

To determine some or all of mapping data 62, server 2 may monitor the frequency of performing functional tests, component tests, and/or reset procedures by one or more vehicle scanning tools on vehicles having a particular vehicle identifier and at least one symptom identifier. In a further example, server 2 may determine partial or full mapping data 62 based on component failure probabilities for different associated components of a vehicle having a particular vehicle identifier and at least one symptom identifier.

Next, FIG. 10 illustrates an example of different indices that may be stored within index 61. As shown, the index 61 may include a PID index 81, a Component Test Index (CTI)82, a Function Test Index (FTI)83, and a Reset Procedure Index (RPI) 84. Two or more of these indices may be combined and stored as a single index. More specific examples of the foregoing indices will be discussed below. The server 2 may use any of the presented indices in order to communicate the relevant scan tool functionality to the vehicle scan tool 4. In particular, in some examples, server 2 may transmit an index value to vehicle scanning tool 4 that identifies the relevant scanning tool function to configure vehicle scanning tool 4.

Next, fig. 11 is a schematic diagram showing an example of symptom-to-part mapping data 89 that may be stored in mapping data 62. Symptom 85 in fig. 11 is shown as a DTC, but the mapped symptoms may include symptoms other than DTCs. Fig. 11 shows a symptom count 86 in parentheses for each symptom. The server 2 may determine a symptom count 86 based on the RO data 63.

The DTC shown in fig. 11 may be referred to as a "P code" from the powertrain controller ECU. As shown in fig. 11, one symptom (e.g., symptoms P0171 and P0172) may be mapped to multiple parts. The mapping between symptoms and components is represented in fig. 11 by mapping line 87.

In a further example, a vehicle symptom may be identified by one or more non-DTC symptom identifiers (such as "engine misfire", "misfire", or "engine no start" or "no start"). The non-DTC symptom identifier identifies symptoms other than DTCs. In other examples, a symptom may be identified by one or more DTCs and one or more non-DTC symptom identifiers. Furthermore, any symptom discussed herein (including any symptom or symptoms and/or at least one symptom) can be identified by (i) one or more DTCs, (ii) one or more non-DTC symptom identifiers, and/or (iii) one or more DTCs and one or more non-DTC symptom identifiers.

Next, fig. 12 shows other examples of the mapping data 62. In particular, fig. 12 shows an example of symptoms of four symptoms to PID MD 71: symptom 1 is mapped to one PID, symptom 2 is mapped to one PID, symptom 3 is mapped to one PID, and symptom 4 is mapped to two PIDs. Fig. 12 also shows an example of a symptom-to-component test MD 73 for four symptoms: symptom 1 is mapped to two component tests, symptom 2 is mapped to two component tests, symptom 3 is mapped to zero component tests, and symptom 4 is mapped to two component tests. Fig. 12 also shows an example of a symptom-to-function test MD 75 for four symptoms: symptom 1 is mapped to four functional tests, symptom 2 is mapped to four functional tests, symptom 3 is mapped to four functional tests, and symptom 4 is mapped to four functional tests. Fig. 12 also shows an example of a symptom-to-reduction procedure MD 77 for five symptoms: symptom 1 is mapped to one reset procedure, symptom 2 is mapped to one reset procedure, symptom 3 is mapped to zero reset procedures, symptom 4 is mapped to one reset procedure, and symptom 5 is mapped to two reset procedures. In fig. 12, example symptoms are shown in parentheses, with the PID, component test, functional test, and reset procedures listed after the colon.

Next, fig. 13 shows another example of the mapping data 62. In particular, fig. 13 shows an example of four component parts to PID MD 72: part 1 is mapped to three PIDs, part 2 is mapped to three PIDs, part 3 is mapped to two PIDs, and part 4 is mapped to one PID. Fig. 13 also shows an example of a five-part-to-part test MD 74: component 1 is mapped to two component tests, component 2 is mapped to three component tests, component 3 is mapped to three component tests, component 4 is mapped to two component tests, and component 5 is mapped to one component test. Fig. 13 also shows an example of a six-component part-to-function test MD 76: component 1 is mapped to two functional tests, component 2 is mapped to zero functional tests, component 3 is mapped to two functional tests, component 4 is mapped to zero functional tests, component 5 is mapped to zero tests, and component 6 is mapped to one functional test. Fig. 13 also shows an example of a component-to-reset procedure MD 78 of eight components:

parts

1, 2, 3, 4, 5, and 6 are mapped to zero reset procedures, part 7 is mapped to two reset procedures, and part 8 is mapped to two reset procedures, respectively. In FIG. 13, example components are shown in parenthesis, and PIDs, component tests, functional tests, and reset procedures are listed after the colon.

Next, fig. 14 shows an example of the PID index 90. The PID index 90 includes an ordered list of PIDs. FIG. 14 shows three example representations of PIDs within the PID index 90. As shown in fig. 14, the PID index 90 may represent the PID using a PID number 91, an index value 92, and a PID name 93 (i.e., at least one word describing the PID). Different PID indices (for example embodiments) may represent PIDs using only one of the three example representations, using a combination of any two of the three example representations, or using different example PID representations. For example, the index values 92 may include decimal, hexadecimal, or some other base number of digits to represent a PID within the PID index 90. The PID index 81 (shown in fig. 10) may include a plurality of PID indices, such as a separate PID index for each of a plurality of different sets of specific identification information (e.g., a separate PID index for each Y/M or Y/M/E). Those individual PID indices may be arranged like PID index 90 or may be arranged in another manner. The PID index 90 may include or be associated with a particular vehicle identifier.

Next, fig. 15 shows an example of a Component Test Index (CTI) 95. The component testing may be performed by an oscilloscope of the vehicle scanning tool 4 or a multimeter of the vehicle scanning tool 4. CTI 95 includes an ordered list of component tests. FIG. 15 shows three example representations of component testing within CTI 95. As shown in fig. 15, CTI 95 may represent a component test using a component test number 96, an index value 97, and a component test name 98 (i.e., at least one word describing the component test). Different CTIs (for example embodiments) may represent component testing using only one of the three example representations, using a combination of any two of the three example representations, or using different example component testing representations. For example, index value 97 may include a decimal, hexadecimal, or some other base number to represent component testing within CTI 95. CTI 82 (as shown in FIG. 10) may include multiple component test indexes, such as a separate CTI for each of multiple different sets of specific identification information (e.g., a separate CTI for each Y/M/M or Y/M/M/E). Those individual CTIs may be arranged like CTI 95 or in another way. CTI 95 may include or be associated with a particular vehicle identifier.

Next, fig. 16 shows an example of a Functional Test Index (FTI) 101. The FTI 101 includes an ordered list of functional tests. Fig. 16 shows three example representations of functional tests in the FTI 101. As shown in fig. 16, the FTI 101 may represent a functional test using a functional test number 103, an index value 105, and a functional test name 107 (i.e., at least one word describing the functional test). Different FTIs (for example embodiments) may represent functional tests using only one of the three example representations, using a combination of any two of the three example representations, or using different example functional test representations. For example, the index value 105 may comprise a decimal, hexadecimal, or some other base number to represent the functional test within the FTI 101. The FTI 83 (shown in FIG. 10) may include a plurality of functional test indices, such as a separate FTI for each of a plurality of different sets of specific identifying information (e.g., a separate FTI for each Y/M/M or Y/M/M/E). Those individual FTIs may be arranged like FTI 101, or in another manner. The FTI 101 may include or be associated with a particular vehicle identifier.

Next, fig. 17 shows an example of the Reset Program Index (RPI) 111. RPI 111 includes an ordered list of reset procedures. FIG. 17 shows three example representations of a reset procedure in RPI 111. As shown in fig. 17, RPI 111 may represent a reset procedure using a reset procedure number 113, an index value 115, and a reset procedure name 117 (i.e., at least one word describing the reset procedure). Different RPIs (for example embodiments) may represent a reset procedure using only one of the three example representations, using a combination of any two of the three example representations, or using different example reset procedure representations. For example, index value 115 may include a decimal, hexadecimal, or other base number to represent a reset procedure within RPI 111. RPI 84 (shown in FIG. 10) may include multiple reset program indices, such as a separate RPI for each of multiple different sets of specific identifying information (e.g., a separate RPI for each Y/M/M or Y/M/M/E). Those individual RPIs may be arranged like RPI 111 or may be arranged in another manner. RPI 111 may include or be associated with a particular vehicle identifier. Index value 115 may be different from the index values of other indices (e.g., PID index 90, CTI 95, and FTI 101) so that indices using multiple indices may form a single index without any overlap of indices.

Next, FIG. 18 shows a specific example of a component hierarchy 65. The component hierarchy 65 may include a separate component hierarchy for each set of vehicles identifiable by a particular vehicle identifier. In an alternative arrangement, a single component hierarchy may involve multiple sets of vehicles that may be identified by different specific vehicle identifiers. In fig. 18, the component hierarchy 65 relates to a vehicle with a gasoline powered engine having an electrical system, an exhaust system, a fuel system, and an air intake system. Fig. 18 shows that the vehicle system may be subdivided into subsystems, as the electrical system is shown as including an ignition subsystem and a charging system.

Including rectangular dots "" each indented row lists a vehicle component that is part of an identified system or subsystem within the vehicle. Each vehicle component in component hierarchy 65 may be associated with a PID, a component test, a functional test, and/or a reset procedure. An example of a PID, component test, functional test, and/or reset procedure associated with a vehicle component is shown in fig. 13. For example, FIG. 18 shows the EGR valve being part of the exhaust system, and FIG. 13 shows the EGR valve associated with PID 13, PID 14, PID 24, CT 1, CT 4, FT 13, and FT 14. The component hierarchy 65 may include data (e.g., metadata) indicating which PID, component test, functional test, and/or reset procedure is associated with the vehicle component. System and subsystem identifiers in the component hierarchy may also be associated with PIDs, component tests, functional tests, and/or reset procedures. This association with the system and subsystem may apply to all vehicle components within the system and subsystem, respectively. In some examples, symptom-to-function mapping may be used to identify context-dependent scan tool functions.

As an example, if the particular vehicle component referenced in the OEM content is an oxygen sensor, the processor 50 may determine the context-dependent PID, component test, functional test, and/or reset procedure to include in the indication sent to the vehicle scanning tool 4 by referencing the component hierarchy 65. The associated PID, component test, functional test, and/or reset procedures may be associated with a vehicle component within the same system or subsystem as a particular vehicle component or with a vehicle component within a different system or subsystem. The vehicle components within each system and subsystem within the component hierarchy may be ordered such that the processor 50 may determine which vehicle component within the other systems or subsystems to consider to determine whether the vehicle component is associated with a PID, component test, functional test, and/or reset procedure.

Next, fig. 19 is a communication flow diagram in accordance with an example embodiment. FIG. 19 illustrates an example workflow that results in automatically initializing a vehicle scanning tool. Fig. 19 shows an example communication that occurs between the master device 120 and the server 121. Fig. 19 further illustrates example communications that occur between server 121 and vehicle scanning tool 122. The master device 120 may be a computing device configured to display information to a technician, such as a computer workstation, a tablet computer, a smartphone, a search device, a wheel aligner, a vehicle scanning tool, or another piece of shop equipment. The vehicle scanning tool 122 may be a computing device configured to communicate with a vehicle to transmit data to the vehicle and/or receive data from the vehicle to cause one or more vehicle maintenance functions to be performed.

The communication may include the master device 120 sending a user identifier 123 (e.g., a technician identifier and/or a shop identifier), a vehicle identifier 124, and contextual information 125 to the server 121. The user identifier 123 may be a numeric identifier, a text identifier, or some other form of identifier. The user identifier 123 may be determined based on a technician logging into a software application running on the host device 120. The vehicle identifier 124 may identify a vehicle to be maintained at the repair shop. The vehicle identifier 124 may include the year, make, model, and engine of the vehicle, or a different set of identifying information. The vehicle identifier 124 may be in a Department of Motor Vehicle (DMV) format or a different format. In a further example, the vehicle identifier 124 may also or alternatively include a Vehicle Identification Number (VIN), an associated repair order identifier, and/or a license plate number. Background information 125 may be OEM content or different types of textual and/or non-textual vehicle maintenance information displayed on host device 120.

The communication may also include the server 121 sending an indication that causes a prompt 126 to be displayed on the master device 120 to automatically configure the vehicle scanning tool to perform context-dependent scanning tool functions. The server 121 may determine context-dependent scanning tool functions based on context information 125 for the vehicle described by the vehicle identifier 124 and for the scanning tool associated with the user identifier 123. In some examples, prompt 126 may be a selectable link that is activated and displayed within OEM content displayed on a display interface of master device 120. In other examples, the prompt 126 may be presented as a yes/no question or in a different format.

The communication may additionally include the master device 120 sending a user confirmation signal 127 to the server 121. The user confirmation signal 127 may be transmitted in response to a user input provided at the master device 120. The user input item may indicate that the technician agrees to automatically initialize the vehicle scanning tool to perform context-dependent vehicle scanning tool functions. The user input item may take the form of a click, a button press, an audio input item, or a different type of confirmation input item. In some examples, the user input item may further relate to selecting a scan tool from a list of scan tools and/or selecting a scan tool function from a list of scan tool functions.

The communication may also include the server 121 sending data describing the vehicle identifier 124, the vehicle scanning tool function identifier 128, and the vehicle system and/or component identifier 129 to the vehicle scanning tool 122. In particular, in response to receiving the user confirmation signal 127 from the master device 120, the server 121 may provide a set of instructions to configure the vehicle scanning tool 122 to perform context-dependent scanning tool functions. The indication may include a vehicle identifier 124 that may be converted to a different format by the server 121 before transmission to the vehicle scanning tool 122. The indication may also include a vehicle scanning tool function identifier 128 that may identify the vehicle scanning tool function by name, identification number, index value into a list of functions, and/or in a different manner. The indication may also include a system and/or component identifier 129, which is a name or other descriptor for the vehicle system and/or component in which the scan tool function is located. The indication may cause the vehicle scanning tool 122 to be initialized such that scanning tool functions will be performed on the vehicle in response to a single input from the technician provided at the vehicle scanning tool. In some examples, the entry may be provided by a technician at the master device 120 or at a different computing device.

The background information 125 may also include timing information indicating that a particular step of the plurality of steps of the vehicle maintenance program has been completed. The server 121 may then determine the vehicle scan tool function as the function to be performed on the vehicle after the particular step. Server 121 may also receive an indication from vehicle scanning tool 122 that the vehicle scanning tool function performed on the vehicle is complete. In response, server 121 may provide host device 120 with an indication to display a subsequent step in the plurality of steps, where the subsequent step is subsequent to performing a particular step of the vehicle maintenance program.

In a further example, the master device 120 may include a video camera. For example, the master device 120 may be configured to display an augmented reality presentation. In such an example, the contextual information 125 provided by the master device 120 to the server 121 may include a portion of the vehicle currently being viewed by the video camera. Depending on which part of the vehicle is currently being viewed by the technician, the relevant scan tool functionality may be superimposed at a corresponding location in the augmented reality presentation.

Next, fig. 20 is another communication flow diagram in accordance with an example embodiment. FIG. 20 illustrates an example workflow that results in automatically initializing a vehicle scanning tool upon user input at a search device. FIG. 20 illustrates example communications that occur between the search apparatus 130 and the server 121. The search device 130 may be an example of the master device 120 shown in fig. 19. Fig. 20 further illustrates example communications that occur between server 121 and vehicle scanning tool 122.

The communication may include the search device 130 transmitting the user identifier 123, the vehicle identifier 124, and the search query 135. The search query 135 may indicate a vehicle symptom, such as a DTC or textual explanation of the vehicle symptom. In other examples, the search query 135 may be a keyword search that does not specifically identify a vehicle symptom. Based on search query 135, server 121 may provide OEM content 136 with selectable links for display on search device 130. The selectable link may allow for automatic initialization of the vehicle scanning tool to perform vehicle scanning tool functions that are contextually related to corresponding portions of the OEM content 136. In some examples, the selectable link may be added to the OEM content at a previous point in time. In other examples, the selectable link may be added to the OEM content in response to receiving search query 135. In either case, the appearance of the selectable link may be modified based on the availability of the scanning tool for the technician and/or the plant identified by the user identifier 123. The communication may also include a user selection 137 of a selectable link in the OEM content. Selection of this link triggers the automatic initialization of the vehicle scanning tool to perform context-dependent scanning tool functions.

The communication may additionally include the server 121 sending data describing the vehicle identifier 124, the vehicle scanning tool function identifier 128, and the vehicle system and/or component identifier 129 to the vehicle scanning tool 122. In fig. 20, the scan tool function identified by the vehicle scan tool function identifier 128 may be associated with OEM content 136 that is displayed on the search device 130 in response to a search query 135 entered by a technician at the search device 130.

Next, fig. 21 is an additional communication flow diagram in accordance with an example embodiment. Fig. 21 illustrates an example workflow that results in the automatic initialization of a vehicle scanning tool upon user input at a wheel aligner. Fig. 21 shows example communications that occur between the wheel aligner 140 and the server 121. The wheel aligner 140 may be an example of the master device 120 shown in fig. 19. Fig. 21 further illustrates an example of communications that occur between server 121 and vehicle scanning tool 122.

The communication may include the wheel aligner 140 transmitting the user identifier 123, the vehicle identifier 124, and an indication of the alignment function 145 performed on the vehicle by the wheel aligner 140. In some examples, the corrective function 145 may be a step of a vehicle maintenance program. Based on the correction function 145, the server 121 may cause a prompt 146 to be displayed on the wheel aligner 140 that provides the functionality to initialize the vehicle scan tool to perform the post-correction scan tool. The scan tool function may be a reset procedure. As an example, a four-wheel correction may be performed on a 2018 ford horse using a wheel aligner. For the vehicle, the scan tool function may be a pre-crash radar calibration or a steering angle sensor reset, each of which may be determined to be an appropriate scan tool function to be performed after the correction function 145. The communication may also include a user confirmation 147 to initialize the vehicle scanning tool to perform the corrected vehicle scanning tool function. User confirmation 147 will trigger the automatic initialization of the vehicle scanning tool to perform the calibrated vehicle scanning tool function.

The communication may additionally include the server 121 sending data describing the vehicle identifier 124, the vehicle scanning tool function identifier 128, and the vehicle system and/or component identifier 129 to the vehicle scanning tool 122. In fig. 21, the scan tool function identified by the vehicle scan tool function identifier 128 may be a scan tool function determined to be an appropriate scan tool function after the wheel correction function is performed on the vehicle by the wheel aligner 140.

In a further example, a sequence of vehicle scan tool functions may be presented on the wheel aligner 140 during execution of the alignment procedure. For example, before the technician begins performing the wheel corrections, the option of configuring the vehicle scanning tool 122 to check the tire pressure on the vehicle may be presented at the wheel aligner 140. Another option to set up the vehicle scanning tool 122 to put the vehicle into neutral adjustment or correction mode may then be presented at the wheel aligner 140. After the technician initiates the correction, additional options may be presented at the wheel aligner 140 to set the vehicle scan tool 122 to lock the steering wheel and set the wheel angle to neutral. More generally, a sequence of vehicle scanning tool initialization options may be presented at appropriate times during the performance of a vehicle maintenance procedure at a wheel aligner or some other piece of shop equipment. The server 121 may also monitor the completion of the scan tool functions and send a message to the wheel aligner or other plant equipment to continue to perform subsequent steps of the vehicle maintenance procedure at the appropriate time.

Next, FIG. 22 shows a flowchart depicting a set of functions 150 (or more simply a "set 150") that can be performed in accordance with the example embodiments described in this specification. The set 150 includes the functions shown in the blocks labeled with integers 151 through 156 (inclusive). The following description of the collection 150 includes references to elements shown in other figures described in this specification, but the functionality of the collection 150 is not limited to being performed by only the referenced elements. The various methods may be performed using all of the functions shown in the set 150 or any suitable subset of the functions shown in the set 150. Any of these methods may be performed in conjunction with other functions, such as one or more of the other functions described in this specification, including any of the functions of the collection 40 illustrated in fig. 7. In some examples, the set 150 may be performed by a server (such as server 2 of fig. 1). In further examples, some or all of the set 150 may be performed by a different device (such as the master device 10 of fig. 1).

Block 151 includes receiving from the computing device (i) a user identifier, (ii) a vehicle identifier for the vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device. The computing device may be any of the host devices described herein, including a computer workstation, a tablet, a smartphone, a search device, a wheel aligner, a vehicle scanning tool, or another piece of workshop equipment. The user identifier may be a technician identifier and/or a plant identifier received based on session information at the computing device identifying a currently logged-on technician, or the user identifier may be received in some other manner. The vehicle identifier may be received based on user input at the computing device, located from a maintenance order, or the vehicle identifier may be received in some other manner. The background information may be any type of OEM content and other types of vehicle maintenance content described herein, including textual and/or non-textual content, one or more steps of a vehicle maintenance program, and/or a search query entered at a computing device.

Next, block 152 includes determining a vehicle scanning tool function to be performed on the vehicle based on the context information. More specifically, the vehicle scanning tool function may be a vehicle maintenance function that is associated with a vehicle maintenance context displayed on the computing device. Vehicle scan tool functionality may be determined using any method described herein that identifies relevant scan tool functionality, including using one or more maps, vehicle component hierarchies, and/or service procedure timeline information. In some cases, determining a vehicle scanning tool function may involve retrieving a scanning tool function previously determined to be relevant to the vehicle maintenance content context displayed on the computing device.

Next, block 153 includes identifying a vehicle scanning tool associated with the user identifier. The vehicle scanning tool may be configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions and selected from a plurality of vehicle identifiers. At least the determined vehicle scanning tool function may be included in the plurality of vehicle scanning tool functions. At least the received vehicle identifier may be included in the plurality of vehicle identifiers. Identifying a vehicle scanning tool that is capable of performing the associated scanning tool function on a particular vehicle may involve referencing a user profile (e.g., a technician profile and/or a shop profile) that describes available vehicle scanning tools and corresponding scanning tool capabilities.

Next, block 154 includes causing a selectable vehicle scan tool initialization option to be displayed on the computing device. In some examples, the selectable vehicle scan tool initialization option may be a selectable link inserted into OEM content displayed on the computing device. In other examples, the selectable vehicle scanning tool initialization option may take the form of a yes/no question, a list of available vehicle scanning tool functions, or a different type of prompt.

Next, block 155 includes receiving a selection of a selectable vehicle scan tool initialization option from the computing device. The selection may involve a touch screen press, a button press, a mouse click, a voice entry, or a different type of user confirmation. In some examples, the selection may additionally require that the vehicle scanning tool be selected from a list of available scanning tools capable of performing the associated scanning tool function on the particular vehicle.

Next, block 156 includes providing an indication to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle in response to receiving the selection. The indication may include at least a vehicle identifier and an identifier for a vehicle scanning tool function. The indication may additionally include an identifier for the component and/or system involved in the vehicle scanning tool function. In further examples, the indication may also include other types of data. In particular, if configuration parameters (such as values) are present in the OEM content, these parameters may be identified by the server and passed to the scanning tool so that the technician does not need to manually enter the parameters. By providing an indication to automatically initialize the vehicle scanning tool to perform context-dependent functions, manually browsing the at least one navigable menu on the vehicle scanning tool may be avoided. In some examples, the indication may configure the vehicle scanning tool such that only a single user input (e.g., one click on the vehicle scanning tool) is required to initiate execution of the vehicle scanning tool function on a particular vehicle.

In a further example, the scan tool may provide a response indicating the status of the scan tool function being performed. The response or feedback data may be received by the server and sent back to the master device. The master device may display the feedback data (e.g., within the OEM content). The feedback data may also be associated with a repair order, which may be helpful if the vehicle is brought back to a repair shop so that the technician can see how the vehicle parts are reset and/or activated.

Next, fig. 23 illustrates an example user profile. The server may store or otherwise access one or more user profiles (e.g., technician profiles and/or shop profiles) describing previously registered vehicle scanning tools in order to identify scanning tools capable of performing context-dependent scanning tool functions. Fig. 23 shows a first technician profile 160 for a first technician, a second technician profile 161 for a second technician, and a plant profile 162. Each user profile may be associated with a user identifier (e.g., a technician identifier and/or a plant identifier).

The first technician profile 160 includes two vehicle scan tools (VST #1 and VST #2) and a respective set of capabilities for each scan tool. The set of capabilities represents a set of scan tool functions that can be performed by a corresponding scan tool. The capabilities of the scanning tool may vary based on the type of vehicle and/or other factors. The first technician profile 160 additionally includes the status of each of the two vehicle scanning tools. The state of VST #1 indicates that the first scanning tool is currently connected to the vehicle, and may also store identification information for the vehicle. The state of VST #2 indicates that a second scan tool is available (e.g., not connected to a vehicle). In some embodiments, when searching for a scanning tool to be automatically initialized, the server may first search for a scanning tool that is already connected to a particular vehicle. If no adequate scanning tool is connected to the vehicle, an available scanning tool may be selected instead. Scanning tools currently connected to different vehicles may not be a preferred choice. However, the scanning tool may be configured with a queuing mechanism that allows the scanning tool to receive and save initialization instructions when connected to a different vehicle. Once a scan tool becomes available or becomes connected to a vehicle associated with an indication, the scan tool may invoke an indication that is automatically configured to perform the associated scan tool function.

In an example implementation, the server may send a beacon signal (e.g., wireless communication) to the vehicle scanning tool to attempt to establish communication with the scanning tool before causing the scanning tool initialization option to be displayed on the master device. In some examples, the beacon signal may cause the scanning tool to switch from a manual mode to an automatic mode. The automatic mode may be a mode of vehicle scanning tool functions performed by the vehicle scanning tool in response to a single user confirmation input signal entered at the vehicle scanning tool.

The second technician profile 161 includes a vehicle scanning tool (VST #3) and a corresponding set of capabilities for the scanning tool. Second technician profile 161 also indicates that VST #3 currently has an unavailable/offline status. The server may be configured not to present scan tool initialization options for scan tools that are not available. For example, if no scan tools capable of performing the associated scan tool functionality are available, the selectable links in the OEM content may be disabled. In some examples, when the technician profile does not contain available scanning tools capable of performing the associated scanning tool function, the workshop profile may be searched for scanning tools.

In this case, the shop configuration file 162 includes each of the three vehicle scan tools (VST #1, VST #2, and VST #3), as well as a corresponding capability set and status for each scan tool. Any technician at the plant may use the scan tool from the plant configuration file 162. For example, if technician #2 needs a vehicle scan tool to perform context-dependent scan tool functions, the server may send an initialization indication to either VST #1 or VST # 2. The server may also notify the technician of the scan tool that has been initialized (e.g., by identifying the scan tool in OEM content displayed to the technician). In general, the technician may be a member of multiple groups of the plant hierarchy. The plant hierarchy may be activated and/or initialized by a server searching to find the appropriate vehicle scanning tool.

Next, fig. 24 is an example menu configuration of the vehicle scanning tool. The vehicle scanning tool may include a display interface 170 that allows a user to configure vehicle maintenance functions. To configure the scan tool, the technician may need to navigate through one or more navigable menus. The navigable menu may allow a user to configure vehicle information 171, which may include the year, make, model, and engine of the vehicle. Each item of vehicle information 171 may require a technician to separately select an input value from a list or different types of input mechanisms. Further, the navigable menu may additionally allow the user to configure the scan tool function 172. In some examples, the configuration may first require selection of the relevant vehicle system and/or component. Additionally, separate selections may be required to identify the type of test (e.g., functional test, component test, reset procedure) before providing a list of tests from which individual tests may be selected. It should be appreciated that the vehicle scanning tool may take on a variety of different configurations and/or appearances that may require extensive user navigation to configure the scanning tool to perform the relevant scanning tool functions. Automatic initialization of the vehicle scanning tool may avoid these user navigation steps by configuring the scanning tool to automatically navigate through menus to context-dependent scanning tool functions.

Next, FIG. 25 shows a flowchart depicting a set of functions 180 (or more simply "set 180") that may be performed in accordance with the example embodiments described in this specification. The set 180 includes the functions shown in the blocks labeled with integers 181 through 184 (inclusive). The following description of the set 180 includes references to elements shown in other figures described in this specification, but the functions of the set 180 are not limited to being performed by only the referenced elements. The various methods may be performed using all of the functions shown in the set 180 or any suitable subset of the functions shown in the set 180. Any of these methods may be performed in conjunction with other functions, such as one or more of the other functions described in this specification. In some examples, the set 180 may be performed by a vehicle scanning tool (such as the vehicle scanning tool 4 of fig. 1). In further examples, some or all of the set 150 may be performed by a different device (such as the server 2 of fig. 1).

Block 181 includes receiving a request at a vehicle scanning tool for automatic initialization of the vehicle scanning tool. The request includes a function identifier for a vehicle scanning tool function and a vehicle identifier for the vehicle. The request may also include additional information, such as a vehicle system and/or component identifier. The vehicle scanning tool is configured to display at least one navigable menu allowing selection from a plurality of vehicle scanning tool functions including at least a vehicle scanning tool function. The at least one navigable menu also allows selection from a plurality of vehicle identifiers including at least a vehicle identifier.

In some examples, the request may be received by the vehicle scanning tool from a server (such as server 2 of fig. 1). In some of these examples, the vehicle scanning tool may continuously monitor for vehicle scanning tool auto-initialization requests pushed from the server. In other of these examples, the vehicle scanning tool may periodically attempt to pull the vehicle scanning tool auto-initialization request from the server. In a further example, the vehicle scanning tool may receive a beacon signal from the server prior to receiving the request for automatic initialization of the vehicle scanning tool. In response to the beacon signal, the vehicle scanning tool may send a status flag to the server indicating whether the vehicle scanning tool is currently performing any vehicle scanning tool functions. The response of the vehicle scanning tool to the beacon signal may allow the server to select a vehicle scanning tool (e.g., from a plurality of available vehicle scanning tools) to receive a request for automatic initialization of the vehicle scanning tool.

The vehicle identifier may be year, make, model, and engine (YMME), or any other type of vehicle identifier described herein. In some examples, the vehicle scanning tool function may be a functional test in which the vehicle scanning tool transmits a message to an electronic control unit in the vehicle to perform the functional test on the vehicle with the vehicle scanning tool. In other examples, the vehicle scanning tool function may involve retrieving a list of relevant parameter identifier values (PIDs) from the vehicle for display on the vehicle scanning tool. Other types of vehicle scanning tool functionality are also contemplated.

Next, block 182 includes determining a current operating state of the vehicle scanning tool. The current operating state is one of a plurality of possible operating states of the vehicle scanning tool and can be used by the vehicle scanning tool to determine how and when to take action on the vehicle scanning tool auto-initialization request. The operating state may also be used by the vehicle scanning tool to determine how to customize message delivery to the technician. Example vehicle scanning tool operating states include: (i) off, (ii) on but not connected to the vehicle, (iii) connected to the vehicle but not actively performing any vehicle scanning tool functions, and (iv) performing vehicle scanning tool functions on the vehicle. Other operating states are also possible. Each operating state may be associated with one or more rules for taking action on vehicle scanning tool initialization requests.

In some examples, determining the current operating state of the vehicle scanning tool may involve determining that the vehicle scanning tool is not connected to any vehicle. In some embodiments, when in this operational state, the vehicle scanning tool may automatically take action on the vehicle scanning tool initialization request. In some examples, the vehicle scanning tool may also display a message indicating that the technician should connect the vehicle scanning tool to the appropriate vehicle for the requested vehicle scanning tool function. In an alternative embodiment, when in this operational state, the vehicle scanning tool may not take action on the vehicle scanning tool initialization request until the vehicle scanning tool determines that it has connected to the appropriate vehicle.

In a further example, determining the current operating state of the vehicle scanning tool may involve determining that the vehicle scanning tool has connected to the vehicle to which the vehicle scanning tool initialization request relates, and that the vehicle scanning tool is not currently performing any vehicle scanning tool functions on the vehicle. In such an operating state, the vehicle scanning tool may automatically act on the initialization request to initialize the vehicle scanning tool to perform the requested function on the vehicle.

In an additional example, determining the current operating state of the vehicle scanning tool may involve determining that the vehicle scanning tool has connected to the vehicle to which the initialization request relates, but that the vehicle scanning tool is currently performing a different vehicle scanning tool function on the vehicle. In this operational state, the vehicle scanning tool may display an option to interrupt different vehicle scanning tool functions. The vehicle scanning tool may only initialize itself to perform the requested scanning tool function upon receiving a user input indicating an interruption of a different vehicle scanning tool function. In a further example, the vehicle scanning tool may initialize itself to perform the requested scanning tool function only after detecting that a different vehicle scanning tool function has completed.

Next, block 183 includes making a decision to initialize the vehicle scanning tool based on the request for automatic initialization of the vehicle scanning tool. The decision may be made based on the determined current operating state of the vehicle scanning tool. In some examples, such a decision to take action on a vehicle scanning tool initialization request may be made immediately upon receipt of the request. In other examples, the decision to take action on the vehicle scanning tool initialization request may not be made until a later point in time. In some examples, this decision may be made by the vehicle scanning tool without requiring additional communication with the server. In an alternative example, the decision may be made with the assistance of a server. For example, the vehicle scanning tool may provide information to the server about its current operating state, and the server may respond to indicate when the vehicle scanning tool may take action on the vehicle scanning tool initialization request.

Regardless of the level of server involvement in making this decision, the vehicle scanning tool may be configured to verify that it is not connected to the wrong vehicle before taking action on the vehicle scanning tool initialization request. For example, the vehicle scanning tool may determine that the vehicle scanning tool is initially connected to a vehicle that is different from the vehicle to which the vehicle scanning tool initialization request relates. In response to determining that the vehicle scanning tool is initially connected to a different vehicle, the vehicle scanning tool may store a request for automatic initialization of the vehicle scanning tool. The vehicle scanning tool may then be configured to make the decision to initialize itself according to the request for automatic initialization of the vehicle scanning tool after determining that the vehicle scanning tool has been disconnected from a different vehicle and that the vehicle scanning tool has been connected to the vehicle to which the request relates.

Next, block 184 includes, in response to making the determination to initialize the vehicle scanning tool, using the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle. In some examples, the vehicle scanning tool may switch from a manual mode in which the at least one navigable menu is manually navigable through user entries to an automatic mode in which vehicle scanning tool functions are performed on the vehicle by the vehicle scanning tool in response to a single user input signal (e.g., a single click). The option to initiate the function may be presented in the form of a yes/no question or in a different format. If a user confirmation to perform a vehicle scanning tool function on the vehicle is received, a message may be transmitted from the vehicle scanning tool transmission to an electronic control unit in the vehicle to perform the vehicle scanning tool function on the vehicle with the vehicle scanning tool.

In some examples, the option to initiate the vehicle scanning tool function may be displayed on the vehicle scanning tool itself. In further examples, the option may also or alternatively be displayed on a different computing device, such as a requesting device or a different computing device wirelessly connected with the vehicle scanning tool. For example, from the alignment machine, the technician may be provided with the option of having the vehicle scanning tool check the tire pressure on the vehicle. For functions where there are no safety issues, it may not be necessary for the technician to provide an acknowledgement signal on the vehicle scanning tool itself. Other functions that need to be actuated in the vehicle may require confirmation by a technician at the vehicle scanning tool itself. The security logic that determines where user confirmation must be provided or whether user confirmation is required in order to initialize the vehicle scanning tool may generally be maintained by a server that communicates with both the vehicle scanning tool and the requesting device.

In a further example, the display interface of the vehicle scanning tool may be configured to provide the technician with an intuitive understanding of which navigation steps have been traversed by the scanning tool auto-initialization process. In particular, the vehicle scanning tool may display a cookie trail indicating which navigation menus are bypassed by using the function identifier and vehicle identifier (and possibly other information) contained in the auto-initialization request in order to initialize the vehicle scanning tool.

Next, fig. 26 is an illustration of an initialized vehicle scanning tool, according to an example embodiment. More specifically, the vehicle scan tool (VST #1) may have been initialized after receiving a vehicle scan tool auto-initialization request from the server. The display interface 190 of the vehicle scanning tool may include a cookie trace 191 that shows which navigation steps are automatically navigated (and thus avoided in manual navigation required by the technician). In this example, year (2010), brand (chevrolet), model (colorado), engine (5.3L), system (evaporative emission control or EVAP), and functional testing (vent solenoid actuation) are automatically selected based on the vehicle scan tool auto-initialization request. Cookie trail 191 may allow manual user navigation so that a technician may jump to a particular level to make an adjustment. For example, the technician may navigate to a functional test page to change the requested functional test to a related functional test before initiating the functional test on the vehicle.

The display interface 190 additionally includes a menu 192 with prompts informing the user that automatic initialization of the vehicle scan tool has occurred and asking the user for a confirmation signal to initiate the requested functional test. In this case, the prompt is presented in the form of a yes/no question, but other types of user interfaces are possible. Additionally, for certain types of vehicle scanning tool functions, no prompt may be required at all, or it may be displayed on the requesting computing device in addition to or in place of the vehicle scanning tool.

As previously described, the vehicle scanning tool may be configured to not always act immediately upon the auto-scan tool initialization request. In such an example, the vehicle scanning tool may be configured to store and display a queue of one or more buffered vehicle scanning tool initialization requests. Each request may be user-selectable to initialize a vehicle scanning tool to perform a corresponding vehicle scanning tool function. Each request may correspond to a particular vehicle. The displayed message may be customized for each request to indicate whether the vehicle scanning tool is currently connected to the appropriate vehicle for a given vehicle scanning tool function.

In a further example, the server may provide an indication to modify the current queue of auto-initialization requests stored and/or displayed by the vehicle scanning tool. For example, when the server recognizes that a different vehicle scanning tool or other workshop device has performed a previously requested function on the vehicle, the server may send a message to the vehicle scanning tool to delete the items in the queue. In an additional example, once the vehicle scanning tool has connected to a particular vehicle, the technician may be prompted with an option to accept or reject one or more queued functions. In such an example, when the technician rejects a particular function, that function may be deleted from the queue stored and displayed by the vehicle scanning tool.

Next, fig. 27 is a block diagram of a vehicle scanning tool 200 according to an example embodiment. Each instance of vehicle scanning tool 4 shown in fig. 1 may include and/or be configured like vehicle scanning tool 200 or any portion of vehicle scanning tool 200. Further, vehicle scanning tool 200 may operate in place of vehicle scanning tool 4 in any of the systems shown in fig. 1, or in some other system. As shown in fig. 27, the vehicle scanning tool 200 includes a processor 201, a network transceiver 202, a Vehicle Communication Transceiver (VCT)203, a user interface 204, and a memory 205. Two or more of these components may be operatively coupled together via a system bus, network, or other connection mechanism 206. Vehicle scanning tool 200 also includes a power source 212 and a housing 207. The user interface 204 includes a display 208. A display 208 may be connected to the connection mechanism 206.

The processor (such as processor 201 and/or any other processor discussed in this specification) may include one or more processors. Thus, the processors discussed in this description may also be referred to as at least one processor or one or more processors. The processor may include a general-purpose processor (e.g.,

single-core microprocessor or

A multi-core microprocessor), or a special purpose processor such as a digital signal processor, a graphics processor, an embedded processor, or an Application Specific Integrated Circuit (ASIC) processor.

An embedded processor refers to a processor having one or more specialized functions within a larger electronic, mechanical, pneumatic, and/or hydraulic device, as opposed to a general purpose computer. The embedded processor may include a central processing unit chip for use in a system other than a general purpose workstation, a notebook computer, or a desktop computer. In some embodiments, the embedded processor may execute an operating system, such as a real-time operating system (RTOS). As an example, the RTOS may include those developed by Micro Digital corporation

The RTOS, such that the processor 201 may, but need not, include (a) an advanced RISC (reduced instruction set computer) machine (ARM) processor (e.g., the AT91SAM4E ARM processor provided by Atmel corporation of san jose, california), or (b) the enzima semiconductor n.v. of eindhoven, netherlands

A processor (e.g., 52259 processor). General purpose processors, special purpose processors, and/or embedded processors may perform analog signal processing and/or digital signal processing.

The processor may be configured to execute a Computer Readable Program Indication (CRPI). CRPIs (such as CRPI 209) discussed in this disclosure may include assembly instructions, machine dependency instructions, microcode, firmware instructions, state setting data, and/or source or object code written in one programming language or any combination of two or more programming languages. By way of example, the programming languages may include an object oriented programming language such as Java, Python, or C + +, or a traditional procedural programming language such as the "C" programming language. The processor may be configured to perform hardware encoded functions in addition to or instead of software encoded functions (e.g., via CRPI). Processor 201 may be programmed to perform any function or combination of functions described herein as being performed by vehicle scanning tool 200.

Memory, such as memory 205 and/or any other memory discussed in this specification, may include one or more memories. Thus, any memory discussed in this specification can also be referred to as at least one memory or one or more memories. The memory may include non-transitory memory, or both non-transitory memory and transitory memory. The non-transitory memory or a portion thereof may be located within the processor or as part of the processor (e.g., within a single integrated circuit chip). The non-transitory memory, or a portion thereof, may be separate and distinct from the processor. In addition, certain portions of memory 205 may be used as data buffers (which may be more simply referred to as "buffers"). As an example, data received by the network transceiver 202 from a server may be stored in a buffer. At least a portion of the buffer may operate as a cache from which the processor 201 reads the stored data multiple times.

The non-transitory memory may include volatile or non-volatile storage components, such as optical, magnetic, organic, or other memory or optical disk storage components. Additionally or alternatively, the non-transitory memory may include or be configured as Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read Only Memory (PROM), Erasable Programmable Read Only Memory (EPROM), Electrically Erasable Programmable Read Only Memory (EEPROM), a hard disk, or a compact disc read only memory (CD-ROM). The RAM may include static RAM or dynamic RAM.

The transceiver (such as network transceiver 202, VCT 203, and/or any other transceiver discussed in this specification) may include one or more transceivers. Each transceiver includes one or more transmitters configured to transmit data or communications onto a network, data bus, and/or communication link. Each transceiver includes one or more receivers configured to receive data or communications carried over a network, data bus, and/or communication link. The transceiver or a portion thereof may be located within the processor or as part of the processor (e.g., within an integrated circuit chip). The transceiver or a portion thereof may be separate and distinct from the processor.

The network transceiver 202 may transmit any data or communications discussed as being transmitted, output or provided by the vehicle scanning tool 200, such as data or communications transmitted, output or provided to a vehicle, a communications network and/or a server. The network transceiver 202 may receive any data or communications discussed as being received by the vehicle scanning tool 200 and/or the network transceiver 202, such as data or communications received by the vehicle scanning tool 200 and/or the network transceiver 202 from a vehicle, a communications network, and/or a server.

The VCT 203 includes a transceiver configured for transmitting VDM to and receiving VDM transmitted by the vehicle. The VCT 203 may include a transceiver (e.g., an integrated transmitter and receiver, or a distinct transmitter and distinct receiver). In some embodiments, the transmitter of the VCT 203 may transmit the VDM to the vehicle. The VDM transmitted to the vehicle may include a request for diagnostic information (such as DTCs) from an ECU in the vehicle. In those embodiments, the receiver of VCT 203 may receive the VDM transmitted by the vehicle. The VDM received by the receiver of the VCT 203 may include diagnostic information transmitted by the ECU in the vehicle. The VDM may include a component identifier, such as an identifier of the ECU transmitting the VDM. The VDM may include data indicating a DTC set by the ECU. The processor 201 can select data from within the VDM and cause the selected data to be displayed on the display 208.

The VCT 203 may include a transceiver (e.g., an integrated transmitter and receiver, or a distinct transmitter and distinct receiver). The transmitter of VCT 203 may be configured to transmit the VDM to the vehicle or, in particular, to an ECU within the vehicle. The VDM transmitted by the VCT 203 may include a VDM with a request for a DTC set by the ECU. The receiver of VCT 203 may be configured to receive the VDM transmitted by the ECU over the vehicle-to-tool link. In some embodiments, the VDM received by the VCT 203 may include a VDM indicating DTCs set within the vehicle. As an example, the wired transceiver of the VCT 203 may include a transceiver, such as a system base chip with a high-speed CAN transceiver 33989 provided by engipu semiconductor of eindhoven, the netherlands.

The VDMs transmitted and/or received by the VCT 203 may be arranged according to criteria for the identified geographic region of vehicular operation. For example, in the united states, VDMs may be deployed according to the OBD II standard. As another example, in european countries, VDMs may be arranged according to the EOBD standard, which complies with european directive 98/69/EC.

In some embodiments, the vehicle-to-tool link comprises a wire harness. The wiring harness may be configured to provide a wired connection between the vehicle scanning tool 200 and the vehicle. In some embodiments, the wire harness may be removably connected to the DLC within the vehicle. VCT 203 may include and/or be connected to one or more connectors, where one connector may be positioned at an end of a wiring harness. In other embodiments, the vehicle-to-tool link comprises a wireless link between a transceiver in the vehicle scanning tool 200 and the vehicle. As an example, the transceiver in the vehicle may be within a vehicle component. As another example, the transceiver in the vehicle may be within the vehicle-to-tool link device.

The VCT 203 may include a wireless transceiver to communicate with a separate wireless transceiver within the vehicle scanning tool 200. A transmitter (such as a transmitter in the network transceiver 202 or the VCT 203, or in any other transceiver discussed in this specification) may include a radio transmitter configured to transmit a radio signal carrying data or communications, and a receiver (such as a receiver in the network transceiver 202 or the VCT 203, or in any other transceiver discussed in this specification) may include a radio receiver configured to receive a radio signal carrying data or communications. A transceiver with a radio transmitter and a radio receiver may include one or more antennas and may be referred to as a "radio transceiver", "RF transceiver", or "wireless transceiver".

The radio signals transmitted or received by the radio transceivers may be arranged in accordance with one or more wireless communication standards or protocols, such as Institute of Electrical and Electronics Engineers (IEEE) standards, such as (i) the IEEE 802.11 standard for wireless local area networks (wireless LANs, sometimes referred to as the Wi-Fi standard (e.g., 802.11a, 802.11b, 802.11g, or 802.11n), (ii) the IEEE 802.15 standard for wireless Personal Area Networks (PANs) (e.g., 802.15.1, 802.15.3, 802.15.4(ZigBee), or 802.15.5), (iii) the bluetooth version 4.1 or 4.2 standard developed by the bluetooth Special Interest Group (SIG) of cockland, washington, (iv) cellular wireless communication standards, such as the Long Term Evolution (LTE) standard, (v) the Code Division Multiple Access (CDMA) standard, (idvi) the Integrated Digital Enhanced Network (IDEN) standard, (vii) the global system for mobile communications (GSM) standard, (viii) a General Packet Radio Service (GPRS) standard, (ix) a Universal Mobile Telecommunications System (UMTS) standard, (x) an enhanced data rates for GSM evolution (EDGE) standard, (xi) a multi-channel multipoint distribution service (MMDS) standard, (xii) an International Telecommunications Union (ITU) standard, such as the ITU-T g.9959 standard known as the Z-Wave standard, (xiii) a 6LoWPAN standard, (xiv) a Thread network protocol, (xv) an international organization for standardization (ISO)/International Electrotechnical Commission (IEC) standard, such as the ISO/IEC 18000-3 standard for Near Field Communication (NFC), (xvi) a Sigfox communication standard, (xvii) a Neul communication standard, or (xviii) a LoRaWAN communication standard. Other examples of wireless communication standards or protocols are also available.

Additionally or alternatively, a transmitter (such as a transmitter in the network transceiver 202 or in the VCT 203) may transmit signals (e.g., one or more signals or one or more electrical waves) piggybacking or representing data or communications onto a line (e.g., one or more lines), and a receiver (such as a receiver in the network transceiver 202 or in the VCT 203) may receive signals piggybacking or representing data or communications via the line. The line may be part of a network. The signals piggybacked over the line may be arranged in accordance with a wired communication standard such as the transmission control protocol/internet protocol (TCP/IP), an IEEE 802.3 ethernet communication standard for LANs, a data cable service interface specification (DOCSIS standard) such as DOCSIS 3.1, a USB specification (as previously described), or some other wired communication standard.

Data or communications transmitted by a network transceiver, such as network transceiver 202, may include a destination identifier or address of a network device to which the data or communications are to be transmitted. The data or communications transmitted by the network transceiver may include a source identifier or address of the system component that includes the network transceiver. The source identifier or address may be used to send a response to a network device that includes a network transceiver to send data or communications.

A network transceiver configured to perform communications over a communication network, such as network transceiver 202, may include at least one of: a modem, a network interface card, or a chip that may be mounted on a circuit board. As an example, the chip may include CC3100 available from Texas instruments, Inc. of Dallas, Tex

Network processor, CC256MODx Bluetooth (R) available from Texas instruments

Host Controller Interface (HCI) module, or for communication via

Bluetooth

Or a different chip that communicates using other communication protocols.

Devices within or coupled to a communication network or communicating via the communication network using packet-switching techniques may be locally configured for the next "hop" in the network (e.g., the device or address where to send data and from where to expect data). As an example, a device (e.g., a transceiver) configured for communication using the IEEE 802.11 standard may be configured with a network name, a network security type, and a password. Some devices auto-negotiate this information through discovery mechanisms (e.g., cellular telephone technology).

The user interface 204 includes at least one component operable to input data (e.g., user selections) to the processor 201, and at least one component operable to output data (e.g., data output by the processor 201). The components of the user interface 204 may be referred to as "user interface components". In some embodiments, the display 208 may comprise a touch screen display operable to input data to the processor 201 and to display data output by the processor 201. In some embodiments, the user interface component includes a keyboard and/or a capture device.

The user interface component may include a control. The controls may be used by a user of the vehicle scanning tool 200 to enter input items, such as those that may be detected by the processor 201, into the vehicle scanning tool 200. The controls may include user-selectable controls for the U/I screen shown by display 208. The controls may include hardware controls, such as keys of a keyboard. In one aspect, the user-selectable controls may be independent of the keys of the keyboard. In this case, the input items may be entered using the display 208, for example, using a user-selectable control by touching the display 208 near the user-selectable control. In another aspect, user-selectable controls displayed on the display 208 may be associated with keys of a keyboard. In this case, the entry may be entered using the keys of the keyboard, using user-selectable controls. The keyboard may include buttons that are not associated with user-selectable controls displayed on the display 208.

The display 208 may, but need not, include a capacitive touch screen display, a resistive touch screen display, a plasma display, a Light Emitting Diode (LED) display, a cathode ray tube display, an Organic Light Emitting Diode (OLED) display, or a Liquid Crystal Display (LCD). The OLED display may include an active matrix OLED or a passive matrix OLED. The LCD may be a backlight, color LCD. The display 208 may include a touch screen display with an LCD. For example, the display 208 may include a capacitive (such as projected capacitance) touch screen display or a resistive touch screen display. Other examples of the display 208 are also available.

The display 208 may include a horizontal scroll bar and a vertical scroll bar. The horizontal scroll bar and the vertical scroll bar may be used to cause the display 208 to display a non-viewable portion of an image or screen output by the processor 201. The display 208 may display still images and/or video.

The display 208 may display a GUI including graphical objects. For example, the GUI may show a user-selectable control via which a user may enter input items related to using the vehicle scanning tool 200. The entry may represent a selection and/or information. By way of example, the user-selectable control may include a graphical button, such as a rectangle surrounding text representing selections or information associated with the button. As another example, the user-selectable controls may include drop-down menus, check boxes, and/or text boxes for entering textual information. A user-selectable control configured for entering a selection may be referred to as a selector. The processor 201 may output a U/I screen to the display 208. The U/I screen output by the processor 201 may be referred to as a "graphical user interface" or "GUI".

The keyboard may include components configured for use by a user to enter selections or information into one or more of the vehicle scanning tools 200. A key configured for inputting a selection may be referred to as a control key. The keyboard may include one or more control keys, or more simply "keys". The keys may include a button, such as a held button hold button or a held released button. In some embodiments, the keyboard comprises a hardware keyboard with a set of numeric keys, alphanumeric keys, alphabetic keys, or some other hardware key. In other embodiments, the display 208 comprises at least a portion of a keypad that includes soft keys, such as capacitive or resistive keys of a touch screen display. In still other embodiments, the keyboard includes at least one hardware key, such as a power on/off key, a yes key, and a no key, or four cursor keys for selecting a direction (such as up, down, left, or right). In still other embodiments, the soft keys of the keyboard on the touch screen display may include an on/off power key, a yes key and a no key, or four cursor keys.

The capture device may include one or more components configured to generate data based on an object proximate to the vehicle scanning tool 200 and/or a signal from which data may be generated. As an example, the data generated by the capture device may include an image (e.g., an image file), the content of a scanned image, and/or measurement data. In at least some embodiments, the capture device comprises at least one of: an image scanner, a barcode scanner, a visible light camera, a light source, a lens, or an image sensor. A data file representing the contents of the captured image or scanned image may be stored in the memory 205. As an example, the captured image may include at least one of: an image of the vehicle, or an image of some portion of the vehicle, such as a license plate attached to the vehicle or a VIN label attached to the vehicle. As another example, the captured image may include image data of a scanned barcode, such as a barcode attached to a VIN label on the vehicle.

The connection mechanism 206 may include any of a variety of conductors to carry communications or data between the components connected to the connection mechanism 206. By way of example, the connection mechanism 206 may include copper foil traces, or some other conductor of a printed circuit board.

The power supply 212 may be configured in any of a variety of configurations, or a combination of configurations. As an example, the power supply 212 may include circuitry to receive AC current from an AC power source (e.g., circuitry connected to an electrical wall socket) and convert the AC current to DC current for supply to one or more components within the vehicle scanning tool 200. As another example, the power source 212 may include or be battery operated. As another example, the power source 212 may include a solar cell or be operated by solar energy. The power supply 212 may include circuitry to distribute current throughout the vehicle scanning tool 200. Other examples of power supply 212 are also available.

Housing 207 may enclose at least a portion of processor 201, at least a portion of network transceiver 202, at least a portion of VCT 203, at least a portion of user interface 204, at least a portion of memory 205, at least a portion of connection mechanism 206, at least a portion of display 208, and/or at least a portion of power supply 212. The housing 207 may be referred to as an envelope. The housing 207 may support a substrate. At least a portion of the processor 201, at least a portion of the network transceiver 202, at least a portion of the VCT 203, at least a portion of the user interface 204, at least a portion of the memory 205, at least a portion of the connection mechanism 206, and/or at least a portion of the display 208 may be mounted on and/or connected to a substrate. The housing 207 may be made of various materials. For example, the housing 207 may be made of a plastic material (e.g., Acrylonitrile Butadiene Styrene (ABS)) and a thermoplastic elastomer for forming a grip on the housing 207.

The memory 205 stores computer-readable data. In an example embodiment, the computer readable data stored in memory 205 may include data from: CRPI 209, scan tool function 210, and navigable menu 211.

The scan tool function 210 comprises computer readable data that the processor 201 uses to perform scan tool functions including transmitting at least one VDM. In an example embodiment, the data that performs the scan tool function includes VDM data (i.e., data to be transmitted as a VDM). For example, VDM data according to the ISO 11898 VDM protocol may include a frame start bit, a multi-bit control field, a zero to eight byte data field, a multi-bit cyclic redundancy check field, an acknowledgement slot bit, an acknowledgement separation bit, and a multi-bit frame end field. Examples of VDM data for other VDM protocols are possible. In another embodiment, the data that performs the scan tool function includes VDM data and data from: a scan tool function identifier, a VCT identifier indicating which of two or more VCTs is to be used to transmit the VDM, a vehicle identification indicating which vehicles are associated with the scan tool function, and a scan tool function category. Each VDM transmitted by the processor 201 to perform the scan tool function is directed to at least one component in the vehicle. In some embodiments, the component comprises an ECU or a sensor connected to the ECU. The VDM may include data that the component is responsive to for performing some function in the vehicle.

The scan tool function 210 may also include a CRPI to cause the display 208 to display data related to the scan tool function. As an example, the scan tool function can include data for determining that the VDM transmitted by the vehicle is a response to the VDM transmitted by the vehicle scan tool 200 to perform the scan tool function. In some embodiments, the scan tool function is associated with a memory address used as a pointer to the scan tool function.

The scan tool function identifier may include data indicative of a scan tool function within the scan tool function 210. As an example, the scan tool function identifier may include a descriptive textual name for display on the display (e.g., parking brake cable service release). For example, the processor 201 may populate user-selectable controls of the U/I screen with descriptive textual names of scan tool functions. As another example, the scan tool function identifier may include a non-descriptive identifier (e.g., a memory address) of the scan tool function for accessing the scan tool function from the memory 205. The descriptive textual name of the scan tool function may be associated with a non-descriptive identifier of the scan tool function. A search of the memory 205 based on the descriptive text name may be used to determine a memory address for accessing the scan tool function from the memory 205.

The system and/or component identifier may include data indicative of the vehicle system and/or vehicle component. As an example, the system and/or component identifier may include a descriptive textual name for display on a display (e.g., a parking brake control system or a parking brake control module). For example, the processor 201 may populate the U/I screen with descriptive textual names of vehicle systems and/or vehicle components.

The navigable menu 211 can allow a user to configure diagnostic information as it is displayed by the vehicle scanning tool 200. In this case, "at least one" navigable menu refers to one or more navigable menus. Each piece of information, when manually entered using the navigable menu 211, may require a technician to individually select an input value from a list or different types of input mechanisms. The navigable menu 211 can allow a user to configure the scan tool function 210. In some examples, the configuration may first require selection of the relevant vehicle system and/or component. Additionally, a separate selection may be required to identify the type of test (e.g., functional test, component test, reset procedure) before being provided with a list of tests from which individual tests may be selected.

The navigable menu 211 may also allow a user to enter at least a portion of a vehicle identifier. As an example, the navigable menu 211 for entering year, make, model, and engine may be displayed in (1) order of year, make, model, and engine, (2) order of make, year, model, and engine, or (3) via another order. After displaying the navigable menu of the input year, make, model, and engine, an additional navigable menu of another feature of the input vehicle may be displayed. As an example, the additional navigable menu may allow the user input to further distinguish a feature of the identified vehicle, such as a feature indicating whether an air pump is present on the identified vehicle. Other examples of additional navigable menus are possible.

Vehicle scanning tool 200 may be configured to communicate with a vehicle using a vehicle communication link. As an example, a vehicle communication link in a vehicle may include one or more conductors for piggybacking a vehicle data message in accordance with a VDM protocol. The VDM protocol may include the society of automotive Engineers

J1850(PWM or VPW) VDM protocol, SAE J1939_ 201808-based Serial control and communication of heavy-duty vehicle networks-Top-level files

J1939VDM protocol and/or any other core J1939 Standard, International organization for standardization

15764-4 Controller Area Network (CAN) VDM protocol,

9141-2K-Line VDM protocol,

14230-4KWP2000K-Line VDM protocol,

17458 (e.g., parts 1-5) FlexRay VDM protocol,

17987 Local Interconnect Network (LIN) VDM protocol,

11898-1: 2015 road vehicle-CAN-first part: data link layer and physical signal protocol,

Cooperative VDM protocols (such as MOST specification Rev.3.0E2, or

Dynamic specification, rev.3.0.2) or some other VDM protocol defined to communicate with or within a vehicle. Each VDM discussed in this specification is arranged according to a VDM protocol.

The server 2, vehicle scanning tool 4, and master device 10 (e.g., a search device) each comprise a computing system. The server 2, vehicle scanning tool 4, and/or host device 10 may include any of the components of the example computing system 250 shown in fig. 28, which is a functional block diagram illustrating an example computing system.

In the basic configuration 251, the computing system 250 may include one or more processors 252 and a system memory 254. A memory bus 259 may be used for communicating between the processor 252 and the system memory 254. Depending on the desired configuration, the processor 252 may be of any type including, but not limited to, a microprocessor (μ P), a microcontroller (μ C), a Digital Signal Processor (DSP), or any combination thereof. The memory controller 253 may also be used with the processor 252, or in some embodiments the memory controller 253 may be an internal part of the processor 252.

Depending on the desired configuration, the system memory 254 may 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 254 may include one or more application programs 255, as well as program data 257. The application programs 255 may include an algorithm 256 arranged to perform the functions described as being performed by the server 2, the vehicle scanning tool 4 or the master device 10. Program data 257 may include system data 258, which may point to any number of data types, such as one or more of the following types of data: an index 61, mapping data 62, RO data 63, diagnostic session data 64, a component hierarchy 65, original OEM content 66, supplemental OEM content 67, a technician profile 68, and/or a shop profile 69. In some example embodiments, application programs 255 may be arranged to operate with program data 257 on an operating system executable by processor 252.

Computing system 250 may have additional features or functionality, and additional interfaces to facilitate communications between basic configuration 251 and any devices and interfaces. For example, a storage device 260 may be provided that includes a removable storage device 261, a non-removable storage device 262, 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 (HDDs), optical disk drives, such as Compact Disk (CD) drives or Digital Versatile Disk (DVD) drives, to name a few, optical disk drives, Solid State Drives (SSDs), and tape drives. Computer storage media may include volatile and nonvolatile, non-transitory, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable program instructions, data structures, program modules, or other data, such as data stored in a computer readable memory, such as memory 52.

System memory 254 and storage device 260 are examples of computer-readable media, such as memory 52. System memory 254 and storage device 260 may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computing system 250.

For the vehicle scanning tool 4 and the master device 10 (e.g., a search device), the computing system 250 may include or be implemented as part of a small-sized portable (i.e., mobile) electronic device, such as a smartphone (e.g., from apple, inc. of cupertino, california)

Smart phones, or Sanxing electronics, Inc. from Younggtong-Gu Maetan-Dong, Kyoto provincial Hovenia, republic of Korean

Smart phones), tablet devices (e.g., from apple inc.)

A tablet device, or a SAMSUNG GALAXY TAB tablet device from SAMSUNG electronics, inc.), or a wearable computing device (e.g., a wireless network watch device or a personal headset device). Application programs 255, or program data 257, may include a slave APP

On-line retail store, slave GOOGLE

An online retail store or other source of applications or CRPI described herein downloads to communication interface 267 for use on vehicle scanning tool 4 and host device 10.

Additionally or alternatively, computing system 250 may include or be implemented as part of a personal computing system (including both laptop and non-laptop configurations) or server. In some implementations, the disclosed methods may be implemented as a CRPI encoded in a machine-readable format on a non-transitory computer-readable storage medium or on other non-transitory media or article of manufacture. Fig. 29 is a schematic diagram illustrating a conceptual partial view of an example computer program product 280 including a computer program for executing a computer process on a computing system arranged in accordance with at least some embodiments presented herein.

Computing system 250 may also include an output interface 263, which may include a graphics processing unit 264, which may be configured to communicate with various external devices, such as a display device 266 or speakers, via one or more a/V ports 265 or a communication interface 267. Communication interface 267 may include a network controller 268 that may be arranged to facilitate communications with one or more other computing systems 270 through network communications via one or more communication ports 269. A communication connection is one example of communication media. Communication media may be embodied by computer readable program instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. A modulated data signal may 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 may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, Radio (RF), Infrared (IR), and other wireless media.

In one embodiment, the example computer program product 280 is provided using a signal bearing medium 281. The signal bearing medium 281 may include one or more programming instructions 282 that, when executed by one or more processors, may provide the functionality or portions of the functionality described above with respect to fig. 1-28. In some examples, signal bearing medium 281 may include a computer readable medium 283 such as, but not limited to, a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), a digital tape, or any other memory described herein. In some embodiments, the signal bearing medium 281 may include a computer recordable medium 284 such as, but not limited to, memory, read/write (R/W) CD, R/W DVD, and the like. In some embodiments, the signal bearing medium 281 may include a communication medium 285 such as, but not limited to, a digital and/or analog communication medium (e.g., fiber optic cable, waveguide, wired communications link, wireless communication link, etc.). Thus, for example, the signal bearing medium 281 may be conveyed by a wireless form of communication medium 285 (e.g., a wireless communication medium conforming to the IEEE 802.11 standard or other transmission protocol).

The one or more programming directives 282 may be, for example, computer-executable and/or logic-implemented directives. In some examples, a computing system (such as computing system 250 of fig. 28) may be configured to provide various operations, functions or actions in response to the programming instructions 282 communicated to the computing system 250 by one or more of the computer-readable medium 283, the computer-recordable medium 284 and/or the communication medium 285.

The processor 50 may be configured as the processor 252. The memory 52 may be configured as part or all of the system memory 254 or the storage device 260. Communication interface 51 may be configured as part or all of communication interface 267.

Each of server 2, vehicle scanning tool 4, host device 10, and computing system 250 may include a power source. According to an example embodiment, the power supply may include a connection to an external power source and circuitry to allow current to flow to other components connected to the power source. As an example, the external power source may include a wall socket where a connection to alternating current may be made. As another example, the external power source may include an energy storage device (e.g., a battery) or a generator.

Additionally or alternatively, the power supply may include a connection to an internal power source and power transfer circuitry that allows current to flow to other components connected to the power source. As an example, the internal power source may include an energy storage device, such as a battery. Further, any of the power supplies described herein may include various circuit protectors and signal conditioners. The power supplies described herein may provide a way to deliver current to other elements that are electrically operated.

It should be understood that the arrangements described herein and/or shown in the drawings are for example only. Thus, those skilled in the art will appreciate that other arrangements and elements (e.g., machines, interfaces, functions, orders, and/or groupings of functions) can be used instead, and some elements can be omitted altogether depending upon the desired results. Further, various functions described and/or illustrated in the figures as being performed by one or more elements may be performed by a processor executing computer readable programs or by a combination of hardware, firmware, and/or software. For purposes of this description, executing CRPIs included in some computer readable media to perform some functions may include executing all program instructions for the CRPIs or only a portion of the CRPIs.

The term "data" in this description may be used interchangeably with the term "information" or similar terms (such as "content"). Data described herein may be transmitted and received. By way of example, any transmission of data described herein may occur directly from a transmitting device (e.g., a transmitter) to a receiving device (e.g., a receiver). As another example, any transmission of data described herein may occur indirectly from a transmitter to a receiver via one or more intermediate network devices (such as an access point, antenna, base station, hub, modem, repeater, router, switch, or some other network device). Any transmission of data described herein may include transmission of data over an air interface, e.g., using radio signals (i.e., wirelessly). Any transmission of data described herein may include transmission of data over wires (e.g., single wire, twisted pair, fiber optic cable, coaxial cable, wire harness, power cord, printed circuit, CAT5 cable, or CAT6 cable). The lines may be referred to as "conductors" or other terminology. As an example, the transmission of data over the conductors may occur electrically or optically.

The data may represent various things, such as objects and conditions. Objects and conditions may be mapped to a data structure (e.g., a table). The processor may reference a data structure to determine that various objects or conditions are represented by the data. As an example, the data received by the processor may represent calendar dates. The processor may determine the calendar date by comparing the data to a data structure defining the calendar date. As another example, the data received by the processor may be representative of a vehicle component. The processor may determine which vehicle component is represented by the data by comparing the data to structures defining various vehicle components.

While various aspects and embodiments are described herein, other aspects and embodiments will be apparent to those skilled in the art. The aspects and embodiments disclosed herein are for purposes of illustration and not limitation, with the true scope being indicated by the claims and the full range of equivalents to which such claims are entitled. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.

In this description, the terms "a," "an," and "the" are used to describe elements and/or functions of example embodiments. It is intended that one or more of the recited elements and/or functions be present.

In this specification, the use of the term "and/or" in a list of at least two elements or functions and the use of the term "at least one" and "one or more" immediately following the list of at least two elements or functions is intended to encompass each embodiment independently including the listed elements or functions and each embodiment including combinations of the listed elements or functions. For example, embodiments described as including A, B and/or C, or at least one of A, B and C, or one or more of A, B and C, are intended to encompass each of the following possible embodiments: (i) an embodiment that includes a but does not include B and does not include C, (ii) an embodiment that includes B but does not include a and does not include C, (iii) an embodiment that includes C but does not include a and does not include B, (iv) an embodiment that includes a and B but does not include C, (v) an embodiment that includes a and C but does not include B, (vi) an embodiment that includes a, B, and C. For embodiments comprising a component or function a, the embodiment may comprise one a or more a. For embodiments comprising a component or function B, the embodiment may comprise one B or a plurality of B. For embodiments that include a component or function C, the embodiment may include one C or more C. Ordinal numbers such as "first," "second," "third," etc., are used to distinguish between corresponding elements and do not denote a particular order, unless otherwise indicated by the context in which the terms are used.

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, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device; determining a vehicle scanning tool function to be performed on the vehicle based on the context information; identifying a vehicle scanning tool associated with a user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier; causing a selectable vehicle scanning tool initialization option to be displayed on a computing device; receiving, from a computing device, a selection of a selectable vehicle scanning tool initialization option; and in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

EEE 2 is a method of EEE 1, wherein identifying a vehicle scanning tool associated with a subscriber identifier includes referencing a subscriber profile that includes data describing registered vehicle scanning tools associated with the subscriber identifier.

EEE 3 is a method of EEE 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises: determining which of the plurality of vehicle scanning tools are connected to the vehicle; and selecting a vehicle scanning tool from the plurality of vehicle scanning tools based on which of the plurality of vehicle scanning tools are connected to the vehicle.

EEE 4 is a method of EEE 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises providing the plurality of vehicle scanning tools for display within a drop-down menu on the computing device for selecting a vehicle scanning tool.

EEE 5 is a method of EEE 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises selecting a vehicle scanning tool from the plurality of vehicle scanning tools based on a level of capability of each of the plurality of vehicle scanning tools to perform vehicle scanning tool functions on the vehicle.

EEE 6 is the method of any one of EEEs 1 to 5, further comprising: determining that a technician profile including data describing registered vehicle scanning tools associated with a user identifier is missing a vehicle scanning tool; and subsequently determining that the shop floor profile associated with the user identifier includes data describing a vehicle scanning tool, wherein the vehicle scanning tool is identified based on the shop floor profile.

EEE 7 is the method of any one of EEEs 1 to 6, further comprising: receiving, from a computing device, a request to view vehicle maintenance content; and providing vehicle maintenance content for display on the computing device, wherein the provided vehicle maintenance content includes selectable vehicle scanning tool initialization options.

EEE 8 is a method of EEE 7, further comprising: determining that the vehicle maintenance content includes a second selectable vehicle scanning tool initialization option for vehicle scanning tool initialization to perform a second vehicle scanning tool function; determining that no vehicle scanning tool associated with the user identifier is capable of performing the second vehicle scanning tool function; and deactivating a second selectable vehicle scanning tool initialization option within the provided vehicle maintenance content.

EEE 9 is a method of EEE 8, further comprising causing a computing device to display a sales quote for a second vehicle scanning tool capable of performing a second vehicle scanning tool function within the provided vehicle maintenance content.

EEE 10 is the method of any one of EEEs 7 to 9, further comprising: identifying, within the vehicle maintenance context, at least one configuration parameter for the vehicle scanning tool to perform a vehicle scanning tool function; and providing an indication to configure the vehicle scanning tool with the at least one configuration parameter.

EEE 11 is the method of any one of EEEs 1 to 10, wherein the computing device comprises a search device, and wherein the context information comprises a search query entered at the search device, wherein the search query comprises a vehicle symptom of the vehicle.

EEE 12 is the method of any one of EEEs 1 to 11, wherein the computing device includes a wheel alignment rack, and wherein the background information includes vehicle maintenance functions performed on the vehicle using the wheel alignment rack.

EEE 13 is a method of EEE 12, wherein the determined vehicle scanning tool function comprises a post-correction reset procedure executable on the vehicle by the vehicle scanning tool.

EEE 14 is the method of any one of EEEs 1 to 13, wherein the computing device includes a video camera, and wherein the context information includes a portion of the vehicle currently viewed by the video camera.

EEE 15 is a method of any one of EEEs 1 to 14, wherein the computing device is configured to display a plurality of steps of a vehicle maintenance program in sequence, wherein the background information includes timing information indicating that a particular step of the plurality of steps has been completed, and wherein determining the vehicle scanning tool function includes determining that the vehicle scanning tool function is to be performed on the vehicle after the particular step.

EEE 16 is a method of EEE 15, further comprising: receiving, from a vehicle scanning tool, an indication of completion of performing a vehicle scanning tool function on a vehicle; and responsively providing an indication to the computing device to display a subsequent step of the plurality of steps, wherein the subsequent step is subsequent to performing the particular step of the vehicle maintenance program.

EEE 17 is a method of any one of EEEs 1 to 16, further comprising transmitting a beacon signal to the vehicle scanning tool to establish a communication link with the vehicle scanning tool prior to causing the selectable vehicle scanning tool initialization option to be displayed on the computing device.

EEE 18 is the method of any one of EEEs 1-17, further comprising providing, in response to receiving the selection from the computing device, an indication to cause the vehicle scanning tool to communicate with the vehicle to perform a vehicle scanning tool function on the vehicle.

EEE 19 is the method of any one of EEEs 1-18, further comprising providing an indication to cause the vehicle scanning tool to switch from a manual mode to an automatic mode in which vehicle scanning tool functions are performed on the vehicle in response to a single user confirmation input signal at the vehicle scanning tool.

EEE 20 is the method of any one of EEEs 1 to 19, further comprising: receiving a status of a vehicle scanning tool function performed on the vehicle by the vehicle scanning tool; and causing a status of the vehicle scanning tool function to be displayed on the computing device.

EEE 21 is the method of any one of EEEs 1-20, wherein the vehicle identifier includes the year, make, model, and engine of the vehicle.

EEE 22 is the method of any one of EEEs 1 to 21, wherein the vehicle scanning tool function comprises a functional test in which the vehicle scanning tool transmits a message to an electronic control unit in the vehicle to perform the functional test on the vehicle with the vehicle scanning tool.

EEE 23 is a method of any one of EEEs 1-22, wherein the vehicle scanning tool function includes retrieving a list of relevant parameter identifier values (PIDs) from the vehicle for display on the vehicle scanning tool.

EEE 24 is a system comprising: a computing device; at least one vehicle scanning tool; and a server configured to: receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device; determining a vehicle scanning tool function to be performed on the vehicle based on the context information; identifying a vehicle scanning tool associated with a user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier; causing a selectable vehicle scanning tool initialization option to be displayed on a computing device; receiving, from a computing device, a selection of a selectable vehicle scanning tool initialization option; and in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

EEE 25 is a system of EEEs 24, wherein the vehicle scanning tool is configured to: receiving a user confirmation to perform a vehicle scan tool function on a vehicle; and in response to receiving the user confirmation, transmitting one or more messages onto a communication link in the vehicle to perform a vehicle scanning tool function on the vehicle.

EEE 26 is a system of

EEEs

24 or 25 in which the computing device is a wheel alignment rack physically separate from the vehicle scanning tool.

EEE 27 is the system of any one of EEEs 24 to 26, wherein the computing device is a display device comprising a touch screen, wherein the display device is configured to: displaying vehicle scanning tool initialization options within the textual vehicle maintenance content; and recognizing selection of a selectable vehicle scanning tool initialization option via touch input on the touch screen.

EEE 28 is a non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions comprising: receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device; determining a vehicle scanning tool function to be performed on the vehicle based on the context information; identifying a vehicle scanning tool associated with a user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier; causing a selectable vehicle scanning tool initialization option to be displayed on a computing device; receiving, from a computing device, a selection of a selectable vehicle scanning tool initialization option; and in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

EEE 29 is a computing device configured to perform the method of any one of EEEs 1 to 23.

EEE 30 is a non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform the method of any of EEEs 1-23.

EEE 31 is a method comprising: (i) receiving, by a computing device, textual vehicle maintenance content; (ii) identifying, by the computing device, a vehicle scanning tool function related to relevant text at a location within the textual vehicle maintenance content; (iii) modifying, by the computing device, the textual vehicle maintenance content to include a selectable link at the location of the relevant text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle; and (iv) providing, by the computing device, the modified textual vehicle maintenance content including the selectable link.

EEE 32 is a method of EEE 31, wherein identifying a vehicle scanning tool function includes determining that associated text describes the vehicle scanning tool function.

EEE 33 is a method of EEE 31 or EEE 32, wherein identifying vehicle scanning tool functions comprises: (i) determining that the relevant text describes a vehicle component; and (ii) identifying vehicle scan tool functions based on the vehicle components and the component-to-function mapping.

EEE 34 is a method of any one of EEEs 31-33, wherein identifying a vehicle scanning tool function comprises: (i) determining that the relevant text describes a vehicle symptom; and (ii) identifying vehicle scan tool functions based on the vehicle symptoms, the symptom-to-component mapping, and the component-to-function mapping.

EEE 35 is a method of EEE 34, wherein the vehicle symptom comprises a Diagnostic Trouble Code (DTC).

EEE 36 is a method of any one of EEEs 31 to 35, wherein identifying a vehicle scanning tool function comprises: (i) determining that the relevant text describes a vehicle system; (ii) identifying a vehicle component that is part of a vehicle system; and (iii) identifying vehicle scan tool functions based on the vehicle components and the component-to-function mapping.

EEE 37 is a method of any one of EEEs 31-36, wherein identifying a vehicle scanning tool function comprises: (i) determining that the relevant text describes a vehicle component; (ii) determining that the vehicle component is part of a vehicle system; and (iii) identifying vehicle scan tool functions based on the vehicle systems and system-to-function mappings.

EEE 38 is a method of any one of EEEs 31-37, wherein identifying a vehicle scanning tool function comprises: (i) determining a temporal vehicle maintenance phase described by the textual vehicle maintenance content; and (ii) identifying a vehicle scan tool function based on a temporal vehicle maintenance phase.

EEE 39 is a method of EEE 38, wherein the determined temporal vehicle maintenance phase comprises a post-repair phase, and wherein the vehicle scan tool function comprises a reset procedure.

EEE 40 is the method of any one of EEEs 31-39, wherein the identified vehicle scanning tool function includes performing a functional test on the vehicle using the vehicle scanning tool.

EEE 41 is the method of any one of EEEs 31 to 40, wherein the identified vehicle scanning tool function comprises a search list of relevant parameter identifier values (PIDs) for display on the vehicle scanning tool.

EEE 42 is a method of any one of EEEs 31-41, wherein modifying textual vehicle maintenance content includes converting the associated text to a selectable link within the textual vehicle maintenance content.

EEE 43 is a method of any one of EEEs 31-42, wherein modifying the textual vehicle maintenance content includes including a selectable link in a drop-down menu proximate associated text within the textual vehicle maintenance content.

EEE 44 is the method of any one of EEEs 31 to 43, further comprising: (i) identifying, within the textual vehicle maintenance content, at least one configuration parameter for performing a vehicle scanning tool function; and (ii) modify the textual vehicle maintenance content to include the at least one configuration parameter with the selectable link.

EEE 45 is the method of any one of EEEs 31-44, wherein the textual vehicle maintenance content includes a wiring diagram, and wherein modifying the textual maintenance content to include selectable links includes modifying the wiring diagram to include a plurality of selectable links in the wiring diagram corresponding to a plurality of vehicle components, wherein each selectable link is selectable to initialize a vehicle scanning tool to perform a respective vehicle scanning tool function associated with the corresponding vehicle component in the wiring diagram.

EEE 46 is a system that includes a vehicle scanning tool and a computing device configured to (i) receive textual vehicle maintenance content; (ii) identifying a vehicle scanning tool function associated with relevant text at a location within the textual vehicle maintenance content; (iii) modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle; and (iv) providing the modified textual vehicle maintenance content including the selectable link.

EEE 47 is a system of EEE 46, further comprising a display device, wherein the display device is configured to: (i) receiving, from a computing device, modified textual vehicle maintenance content including a selectable link; and (ii) displaying the modified textual vehicle maintenance content including the selectable link.

EEE 48 is a system of EEEs 47, wherein the display device is further configured to: (i) receiving a user selection of a selectable link; and (ii) in response to receiving a user selection of the selectable link, providing an indication to the vehicle scanning tool to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle.

EEE 49 is the system of any one of EEEs 46 to 48, wherein the vehicle scanning tool is configured to: (i) receiving a user confirmation of execution of the identified vehicle scanning tool function on the vehicle; and (ii) in response to receiving the user confirmation, transmitting one or more communication signals to the vehicle to perform the identified vehicle scanning tool function on the vehicle.

EEE 50 is a non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions comprising: (i) receiving textual vehicle maintenance content; (ii) identifying a vehicle scanning tool function associated with relevant text at a location within the textual vehicle maintenance content; (iii) modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle; and (iv) providing the modified textual vehicle maintenance content including the selectable link.

The EEE 51 is a computing device configured to perform the method of any one of the EEEs 31 to 45.

EEE 52 is a non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform the method of any of EEEs 31-45.

EEE 53 is a vehicle scanning tool comprising means for performing the method of any one of EEEs 31 to 45.

EEE 54 is a method comprising receiving, at a vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool, the request comprising a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier; determining a current operating state of the vehicle scanning tool; making a decision to initialize the vehicle scanning tool according to a request for automatic initialization of the vehicle scanning tool based on a current operating state of the vehicle scanning tool; and in response to making the determination, using the function identifier and the vehicle identifier to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

EEE 55 is a method of EEE 54, further comprising receiving a user confirmation to perform a vehicle scanning tool function on the vehicle; and in response to receiving the user confirmation, transmitting a message from the vehicle scanning tool to an electronic control unit in the vehicle to perform a vehicle scanning tool function on the vehicle with the vehicle scanning tool.

EEE 56 is a method of EEE 54 or 55, wherein determining a current operating state of the vehicle scanning tool includes determining that the vehicle scanning tool is not connected to any vehicle.

EEE 57 is a method of EEE 54 or 55, wherein determining a current operating state of the vehicle scanning tool includes determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is not currently performing any vehicle scanning tool function on the vehicle.

EEE 58 is a method of EEE 54 or 55, wherein determining a current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is performing a different vehicle scanning tool function on the vehicle, and wherein making a decision to initialize the vehicle scanning tool based on a request for automatic initialization of the vehicle scanning tool comprises: displaying on the vehicle scanning tool an option to interrupt a different vehicle scanning tool function; and receiving a user input indicating to interrupt a different vehicle scanning tool function.

EEE 59 is a method of EEE 54 or 55, wherein determining a current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is performing a different vehicle scanning tool function on the vehicle, and wherein making a decision to initialize the vehicle scanning tool based on the request for automatic initialization of the vehicle scanning tool comprises detecting that the different vehicle scanning tool function has been completed.

EEE 60 is the method of any one of EEEs 54 to 59, further comprising: determining that a vehicle scanning tool is initially connected to a different vehicle; and in response to determining that the vehicle scanning tool is initially connected to a different vehicle, storing, at the vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool.

EEE 61 is a method of EEE 60, wherein making a decision to initialize the vehicle scanning tool based on a request for automatic initialization of the vehicle scanning tool includes determining that the vehicle scanning tool has been disconnected from a different vehicle and that the vehicle scanning tool has been connected to the vehicle.

EEE 62 is a method of any one of EEEs 54-61, further comprising causing the vehicle scanning tool to display a cookie trace indicating which of the at least one navigable menu is bypassed by initializing the vehicle scanning tool using the function identifier and the vehicle identifier.

EEE 63 is the method of any one of EEEs 54-62, wherein receiving a request for automatic initialization of a vehicle scanning tool comprises the vehicle scanning tool monitoring a vehicle scanning tool automatic initialization request pushed from a server.

EEE 64 is the method of any one of EEEs 54-62, wherein receiving a request for vehicle scan tool auto-initialization includes the vehicle scan tool periodically attempting to pull a vehicle scan tool auto-initialization request from a server.

EEE 65 is a method of any one of EEEs 54 to 64, further comprising, prior to receiving a request for automatic initialization of a vehicle scanning tool: receiving a beacon signal from a server; and sending a status flag from the vehicle scanning tool to the server, the status flag indicating whether the vehicle scanning tool is currently performing any vehicle scanning tool functions.

EEE 66 is a method of any one of EEEs 54-65, further comprising displaying a queue of a plurality of buffered vehicle scan tool initialization requests on the vehicle scan tool.

EEE 67 is a method of EEE 66, wherein each of the plurality of cached vehicle scan tool initialization requests is user-selectable to initialize a vehicle scan tool to perform a corresponding vehicle scan tool function.

EEE 68 is a method of any one of EEEs 54-67, further comprising causing the vehicle scanning tool to switch from a manual mode, in which the at least one navigable menu is manually navigable via a user input, to an automatic mode, in which vehicle scanning tool functions are performed on the vehicle by the vehicle scanning tool in response to a single user input signal.

EEE 69 is the method of any one of EEEs 54-68, wherein the vehicle identifier includes the year, make, model, and engine of the vehicle.

EEE 70 is a method of any one of EEEs 54-69, wherein the vehicle scanning tool function comprises a functional test in which the vehicle scanning tool transmits a message to an electronic control unit in the vehicle to perform the functional test on the vehicle with the vehicle scanning tool.

EEE 71 is a method of any one of EEEs 54-69, wherein the vehicle scanning tool function includes retrieving a list of relevant parameter identifier values (PIDs) from the vehicle for display on the vehicle scanning tool.

EEE 72 is a vehicle scanning tool that includes a control system configured to perform the method of any of EEEs 54-71.

EEE 73 is a non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform the method of any of EEEs 54-71.

EEE 74 is a system that includes means for performing the method of any of EEEs 1-23.

Claims

1. A method, comprising:

receiving, from a computing device, (i) a user identifier, (ii) a vehicle identifier for a vehicle, and (iii) contextual information related to vehicle maintenance content currently displayed on the computing device;

determining a vehicle scanning tool function to be performed on the vehicle based on the context information;

identifying a vehicle scanning tool associated with a user identifier, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including a vehicle scanning tool function and selected from a plurality of vehicle identifiers including a vehicle identifier;

causing a selectable vehicle scanning tool initialization option to be displayed on a computing device;

receiving, from a computing device, a selection of a selectable vehicle scanning tool initialization option; and

in response to receiving the selection, providing an indication to select a vehicle scanning tool function and a vehicle identifier from the at least one navigable menu on the vehicle scanning tool to initialize the vehicle scanning tool to perform the vehicle scanning tool function on the vehicle.

2. The method of claim 1, wherein identifying the vehicle scanning tool associated with the user identifier comprises referencing a user profile that includes data describing registered vehicle scanning tools associated with the user identifier.

3. The method of claim 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises:

determining which of the plurality of vehicle scanning tools is connected to a vehicle; and

selecting a vehicle scanning tool from the plurality of vehicle scanning tools based on which of the plurality of vehicle scanning tools is connected to a vehicle.

4. The method of claim 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises providing a plurality of vehicle scanning tool identifiers for display within a drop-down menu on the computing device for selecting a vehicle scanning tool.

5. The method of claim 2, wherein the user profile includes data describing a plurality of vehicle scanning tools capable of performing vehicle scanning tool functions on the vehicle, and the method further comprises selecting a vehicle scanning tool from the plurality of vehicle scanning tools to perform vehicle scanning tool functions on the vehicle based on the capability level of each of the plurality of vehicle scanning tools.

6. The method of claim 1, further comprising:

determining that a technician profile including data describing registered vehicle scanning tools associated with a user identifier is missing a vehicle scanning tool; and

it is then determined that the shop floor profile associated with the user identifier includes data describing a vehicle scanning tool, wherein the vehicle scanning tool is identified based on the shop floor profile.

7. The method of claim 1, further comprising:

receiving, from a computing device, a request to view vehicle maintenance content; and

providing vehicle maintenance content for display on a computing device, wherein the provided vehicle maintenance content includes selectable vehicle scanning tool initialization options.

8. The method of claim 7, further comprising:

determining that the vehicle maintenance content includes a second selectable vehicle scanning tool initialization option for vehicle scanning tool initialization to perform a second vehicle scanning tool function;

determining that no vehicle scanning tool associated with the user identifier is capable of performing the second vehicle scanning tool function; and

deactivating a second selectable vehicle scanning tool initialization option within the provided vehicle maintenance content.

9. The method of claim 8, further comprising causing the computing device to display a sales quote for a second vehicle scanning tool capable of performing a second vehicle scanning tool function within the provided vehicle maintenance content.

10. The method of claim 7, further comprising:

identifying, within the vehicle maintenance context, at least one configuration parameter for the vehicle scanning tool to perform a vehicle scanning tool function; and

providing an indication to configure the vehicle scanning tool with the at least one configuration parameter.

11. The method of claim 1, wherein the computing device comprises a search device, and wherein the contextual information comprises a search query entered at the search device, wherein the search query comprises a vehicular symptom of the vehicle.

12. The method of claim 1, wherein the computing device comprises a wheel alignment rack, and wherein the background information comprises vehicle maintenance functions performed on the vehicle with the wheel alignment rack.

13. The method of claim 12, wherein the determined vehicle scanning tool function comprises a post-correction reset procedure executable on the vehicle by the vehicle scanning tool.

14. The method of claim 1, wherein the computing device comprises a video camera, and wherein the contextual information comprises a portion of the vehicle currently viewed by the video camera.

15. The method of claim 1, wherein the computing device is configured to sequentially display a plurality of steps of a vehicle maintenance program, wherein the background information includes timing information indicating that a particular step of the plurality of steps has been completed, and wherein determining the vehicle scanning tool function includes determining that the vehicle scanning tool function is to be performed on the vehicle after the particular step.

16. The method of claim 15, further comprising:

receiving, from a vehicle scanning tool, an indication of completion of performing a vehicle scanning tool function on a vehicle; and

responsively providing an indication to the computing device to display a subsequent step of the plurality of steps, wherein the subsequent step is subsequent to performing the particular step of the vehicle maintenance program.

17. The method of claim 1, further comprising:

transmitting a beacon signal to the vehicle scanning tool to establish a communication link with the vehicle scanning tool prior to causing the selectable vehicle scanning tool initialization option to be displayed on the computing device.

18. The method of claim 1, further comprising:

in response to receiving the selection from the computing device, an indication is provided to cause the vehicle scanning tool to communicate with the vehicle to perform a vehicle scanning tool function on the vehicle.

19. The method of claim 1, further comprising providing an indication to cause the vehicle scanning tool to switch from a manual mode to an automatic mode in which vehicle scanning tool functions are performed on the vehicle in response to a single user confirmation input signal at the vehicle scanning tool.

20. The method of claim 1, further comprising:

receiving a status of a vehicle scanning tool function performed on the vehicle by the vehicle scanning tool; and

causing a status of the vehicle scanning tool function to be displayed on the computing device.

21. The method of claim 1, wherein the vehicle identifier comprises a year, make, model, and engine of the vehicle.

22. The method of claim 1, wherein the vehicle scanning tool function comprises a functional test in which the vehicle scanning tool transmits a message to an electronic control unit in the vehicle to perform the functional test on the vehicle with the vehicle scanning tool.

23. The method of claim 1, wherein the vehicle scanning tool function includes retrieving a list of relevant parameter identifier values (PIDs) from the vehicle for display on the vehicle scanning tool.

24. A system, comprising:

a computing device;

at least one vehicle scanning tool; and

a server configured to:

25. The system of claim 24, wherein the vehicle scanning tool is configured to:

receiving a user confirmation to perform a vehicle scan tool function on a vehicle; and

in response to receiving the user confirmation, one or more messages are transmitted onto a communication link in the vehicle to perform a vehicle scanning tool function on the vehicle.

26. The system of claim 24, wherein the computing device is a wheel alignment stand physically separated from the vehicle scanning tool.

27. The system of claim 24, wherein the computing device is a display device comprising a touchscreen, wherein the display device is configured to:

displaying vehicle scanning tool initialization options within the textual vehicle maintenance content; and

selection of a selectable vehicle scanning tool initialization option is recognized via a touch input on the touch screen.

28. A non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions comprising:

29. A method, comprising:

receiving, by a computing device, textual vehicle maintenance content;

identifying, by the computing device, a vehicle scanning tool function related to relevant text at a location within the textual vehicle maintenance content;

modifying, by the computing device, the textual vehicle maintenance content to include a selectable link at the location of the relevant text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle; and

providing, by the computing device, modified textual vehicle maintenance content including the selectable link.

30. The method of claim 29, wherein identifying a vehicle scanning tool function comprises determining that the associated text depicts a vehicle scanning tool function.

31. The method of claim 29, wherein identifying a vehicle scanning tool function comprises:

determining that the relevant text describes a vehicle component; and

vehicle scan tool functions are identified based on vehicle components and component-to-function mappings.

32. The method of claim 29, wherein identifying a vehicle scanning tool function comprises:

determining that the relevant text describes a vehicle symptom; and

vehicle scan tool functions are identified based on vehicle symptoms, symptom-to-component mappings, and component-to-function mappings.

33. The method of claim 32, wherein the vehicle symptom comprises a Diagnostic Trouble Code (DTC).

34. The method of claim 29, wherein identifying a vehicle scanning tool function comprises:

determining that the relevant text describes a vehicle system;

identifying a vehicle component that is part of a vehicle system; and

35. The method of claim 29, wherein identifying a vehicle scanning tool function comprises:

determining that the relevant text describes a vehicle component;

determining that the vehicle component is part of a vehicle system; and

vehicle scan tool functions are identified based on vehicle systems and system-to-function mappings.

36. The method of claim 29, wherein identifying a vehicle scanning tool function comprises:

determining a temporal vehicle maintenance phase described by the textual vehicle maintenance content; and

vehicle scan tool functions are identified based on a temporal vehicle maintenance phase.

37. The method of claim 36, wherein the determined temporal vehicle maintenance phase comprises a post-repair phase, and wherein the vehicle scan tool function comprises a reset procedure.

38. The method of claim 29, wherein the identified vehicle scanning tool function comprises performing a functional test on the vehicle with the vehicle scanning tool.

39. The method of claim 29, wherein the identified vehicle scanning tool function comprises a search list of relevant parameter identifier values (PIDs) for display on the vehicle scanning tool.

40. The method of claim 29, wherein modifying textual vehicle maintenance content comprises converting relevant text to a selectable link within the textual vehicle maintenance content.

41. The method of claim 29, wherein modifying the textual vehicle maintenance content includes including a selectable link in a drop-down menu near relevant text within the textual vehicle maintenance content.

42. The method of claim 29, further comprising:

identifying, within the textual vehicle maintenance content, at least one configuration parameter for performing a vehicle scanning tool function; and

modifying the textual vehicle maintenance content to include the at least one configuration parameter with the selectable link.

43. The method of claim 29, wherein the textual vehicle maintenance content includes a wiring diagram, and wherein modifying the textual maintenance content to include the selectable link includes:

the wiring diagram is modified to include a plurality of selectable links in the wiring diagram corresponding to the plurality of vehicle components, wherein each selectable link is selectable to initialize a vehicle scanning tool to perform a respective vehicle scanning tool function associated with the corresponding vehicle component in the wiring diagram.

44. A system, comprising:

a vehicle scanning tool; and

a computing device configured to:

receiving textual vehicle maintenance content;

identifying a vehicle scanning tool function associated with relevant text at a location within the textual vehicle maintenance content;

modifying the textual vehicle maintenance content to include a selectable link at the location of the associated text, wherein the selectable link is selectable to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle; and

modified textual vehicle maintenance content is provided that includes a selectable link.

45. The system of claim 44, further comprising a display device, wherein the display device is configured to:

receiving, from a computing device, modified textual vehicle maintenance content including a selectable link; and

displaying the modified textual vehicle maintenance content including the selectable link.

46. The system of claim 45, wherein the computing device is further configured to:

receiving a user selection of a selectable link from a display device; and

in response to receiving a user selection of the selectable link, an indication is provided to the vehicle scanning tool to initialize the vehicle scanning tool to perform the identified vehicle scanning tool function on the vehicle.

47. The system of claim 44, wherein the vehicle scanning tool is configured to:

receiving a user confirmation of execution of the identified vehicle scanning tool function on the vehicle; and

in response to receiving the user confirmation, one or more communication signals are transmitted to the vehicle to perform the identified vehicle scanning tool function on the vehicle.

48. A non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions comprising:

receiving textual vehicle maintenance content;

49. A method, comprising:

receiving, at a vehicle scanning tool, a request for automatic initialization of the vehicle scanning tool, the request including a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier;

determining a current operating state of the vehicle scanning tool;

making a decision to initialize the vehicle scanning tool according to a request for automatic initialization of the vehicle scanning tool based on a current operating state of the vehicle scanning tool; and

in response to making the determination, a vehicle scanning tool function is performed on the vehicle using the function identifier and the vehicle identifier to initialize the vehicle scanning tool.

50. The method of claim 49, further comprising:

in response to receiving the user confirmation, transmitting a message from the vehicle scanning tool to an electronic control unit in the vehicle to perform a vehicle scanning tool function on the vehicle with the vehicle scanning tool.

51. The method of claim 49, wherein determining the current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is not connected to any vehicle.

52. The method of claim 49, wherein determining the current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is not currently performing any vehicle scanning tool function on the vehicle.

53. The method of claim 49, wherein determining the current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is performing a different vehicle scanning tool function on the vehicle, and wherein making the decision to initialize the vehicle scanning tool based on the request for automatic initialization of the vehicle scanning tool comprises:

displaying on the vehicle scanning tool an option to interrupt a different vehicle scanning tool function; and

a user input is received indicating an interruption of a different vehicle scanning tool function.

54. The method of claim 49, wherein determining the current operating state of the vehicle scanning tool comprises determining that the vehicle scanning tool is connected to the vehicle and that the vehicle scanning tool is performing a different vehicle scanning tool function on the vehicle, and wherein making the decision to initialize the vehicle scanning tool based on the request for automatic initialization of the vehicle scanning tool comprises detecting that the different vehicle scanning tool function has been completed.

55. The method of claim 49, further comprising:

determining that a vehicle scanning tool is initially connected to a different vehicle; and

in response to determining that the vehicle scanning tool is initially connected to a different vehicle, a request for automatic initialization of the vehicle scanning tool is stored at the vehicle scanning tool.

56. The method of claim 55, wherein making a decision to initialize the vehicle scanning tool based on the request for automatic initialization of the vehicle scanning tool comprises determining that the vehicle scanning tool has been disconnected from a different vehicle and that the vehicle scanning tool has been connected to a vehicle.

57. The method of claim 49, further comprising causing the vehicle scanning tool to display a cookie trail indicating which of the at least one navigable menu to bypass by initializing the vehicle scanning tool using the function identifier and the vehicle identifier.

58. The method of claim 49, wherein receiving the request for vehicle scanning tool auto-initialization comprises the vehicle scanning tool monitoring a vehicle scanning tool auto-initialization request pushed from a server.

59. The method of claim 49, wherein receiving the request for vehicle scanning tool auto-initialization comprises the vehicle scanning tool periodically attempting to pull a vehicle scanning tool auto-initialization request from a server.

60. The method of claim 49, further comprising, prior to receiving the request for automatic initialization of the vehicle scanning tool:

receiving a beacon signal from a server; and

a status flag is sent from the vehicle scanning tool to the server indicating whether the vehicle scanning tool is currently performing any vehicle scanning tool functions.

61. The method of claim 49, further comprising displaying a queue of a plurality of buffered vehicle scan tool initialization requests on the vehicle scan tool.

62. The method of claim 61, wherein each of the plurality of cached vehicle scan tool initialization requests is user-selectable to initialize a vehicle scan tool to perform a corresponding vehicle scan tool function.

63. The method of claim 49, further comprising causing the vehicle scanning tool to switch from a manual mode in which the at least one navigable menu is manually navigable by user input to an automatic mode in which vehicle scanning tool functions are performed on the vehicle by the vehicle scanning tool in response to a single user input signal.

64. The method of claim 49, wherein the vehicle identifier includes a year, make, model, and engine of the vehicle.

65. The method of claim 49, wherein the vehicle scanning tool function comprises a functional test in which the vehicle scanning tool transmits a message to an electronic control unit in the vehicle to perform the functional test on the vehicle with the vehicle scanning tool.

66. The method of claim 49, wherein the vehicle scanning tool function includes retrieving a list of relevant parameter identifier values (PIDs) from the vehicle for display on the vehicle scanning tool.

67. A vehicle scanning tool, comprising:

a processor configured to:

receiving a request for automatic initialization of a vehicle scanning tool, the request including a function identifier for a vehicle scanning tool function and a vehicle identifier for a vehicle, wherein the vehicle scanning tool is configured to display at least one navigable menu selected from a plurality of vehicle scanning tool functions including the vehicle scanning tool function and selected from a plurality of vehicle identifiers including the vehicle identifier;

determining a current operating state of the vehicle scanning tool;

68. A non-transitory computer-readable medium having stored therein instructions executable by one or more processors to cause a computing system to perform functions comprising:

determining a current operating state of the vehicle scanning tool;