This disclosure relates generally to automotive maintenance systems and, more particularly, to automotive diagnostic systems that provide multi-point inspection (MPI) services using multiple automotive data measurement tools.
In recent years, vehicles and the field of automotive maintenance have experienced rapid growth in computerized systems both within automotive vehicles and in computerized diagnostic tools that identify maintenance issues with the vehicles. Modern vehicles include one or more computer systems that are often referred to as an electronic control unit (ECU). In some vehicles, the ECU controls and monitors the operations of numerous systems including, but not limited to, the engine, steering, tires, transmission, brakes, fuel delivery or battery level monitoring, and climate control systems. Some vehicles also include numerous sensors that monitor various aspects of the operation of the vehicle. The ECU receives the sensor data and is configured to generate diagnostic trouble codes (DTCs) if the sensors indicate that one or more systems in the vehicle may be failing or operating outside of predetermined parameters.
Many vehicles use the controller area network (CAN) vehicle bus to transmit data between the ECU and the onboard sensors and components in the vehicle. The CAN bus, or other equivalent data networks in a vehicle, provides a common communication framework between the ECU and the various sensors and systems in the vehicle. Additionally, the CAN bus or equivalent network enables communication between the ECU and external diagnostic tools. Diagnostic tools are also digital computers with communication ports and input/output devices, including display screens and input control buttons, which relay information to a mechanic and enable the mechanic to perform tests and send commands to the ECU. The ECU and diagnostic tools often use an industry standard protocol, such as a version of the on-board diagnostics (OBD) protocol, including the OBD-II protocol. Automotive mechanics and service professionals use a wide range of digital diagnostic tools to interface with the ECUs in vehicles both to diagnose issues with the vehicles, which are often indicated by DTC data from the ECU.
In addition to retrieving DTCs from in-vehicle ECUs, automotive technicians use a wide range of diagnostic equipment to perform inspections and maintenance for vehicles. Many service centers often use different pieces of diagnostic equipment from different manufacturers. The technicians often use the diagnostic and record the results manually during a multi-point inspection For example, a technician uses a battery testing device and a wheel-alignment tester manually during an inspection, and the two devices may be produced by different manufacturers. Some inspection processes seek to collect automotive information for digital storage in a computer system. The process of performing inspection tests and inputting the data into the computer system remains largely manual, however. Some diagnostic tools are configured to transmit results to another computing system for storage, but the data formats and communication protocols for the diagnostic tools of different manufacturers are often incompatible. Additionally, the technician often has to use different and incompatible user interfaces with different diagnostic tools during the MPI, which can increase the inspection time and require additional training for the technicians. Consequently, improvements to the operation of automotive diagnostic systems that enable technicians to perform inspections and other maintenance tasks using multiple diagnostic tools more efficiently would be beneficial.
A connected service for automotive diagnostics offers an integration layer that forms a back bone to enable communication and dataflow that will allow technician to perform inspection and store the data in central data storage system. The system optionally includes integration with Electronic multi-point inspection (eMPI) software is. The system includes network services that enable establishment of a connection service framework that is compatible with diagnostic equipment from multiple manufacturers, a secure web administration console that allows both OEM & dealers to configure new equipment, select equipment, scan VIN & view completed results, and integration with equipment vendors based upon a standard web service contract.
In one embodiment, an automotive inspection system includes a plurality of diagnostic tools, each diagnostic tool in the plurality of diagnostic tools being configured to perform a diagnostic procedure on a vehicle, a client computing device, and a server connected to the plurality of diagnostic tools and the client computing device. The server is configured to receive a first command to operate a first diagnostic tool in the plurality of diagnostic tools from the client computing device, transmit the first command to the first diagnostic tool to perform a first diagnostic procedure on the vehicle, receive first diagnostic data from the first diagnostic tool for the first diagnostic procedure, generate a report including the first diagnostic data for the vehicle, and transmit the report to the client computing device to enable an operator of the client computing device to review the first diagnostic data.
In another embodiment, a method of performing an automotive inspection has been developed. The method includes receiving with a server a first command to operate a first diagnostic tool in a plurality of diagnostic tools from a client computing device, transmitting with the server the first command to the first diagnostic tool to perform a first diagnostic procedure on a vehicle, receiving with the server first diagnostic data from the first diagnostic tool for the first diagnostic procedure, generating with the server a report including the first diagnostic data for the vehicle, and transmitting the report from the server to the client computing device to enable an operator of the client computing device to review the first diagnostic data.
For the purposes of promoting an understanding of the principles of the embodiments described herein, reference is now be made to the drawings and descriptions in the following written specification. No limitation to the scope of the subject matter is intended by the references. This patent also includes any alterations and modifications to the illustrated embodiments and includes further applications of the principles of the described embodiments as would normally occur to one skilled in the art to which this document pertains.
In
After identifying the make and model of the vehicle, the tech console 254 generates a web-based interface for the technician to perform the MPI of the vehicle using the diagnostic equipment 232. The interface is optionally customized for the make and model of the vehicle that is undergoing inspection to accommodate different features of different vehicle models. In one embodiment, the technician uses a PC, smartphone, tablet based computer or other suitable computing device to view a graphical user interface (GUI) that guides the technician through the MPI process.
In one embodiment, the technician is only required to connect a diagnostic tool to the vehicle but is not required to perform complex operations with the diagnostic tool because the tech console 254 is configured to operate the diagnostic tool remotely. For example, in one embodiment the technician 202 connects a battery testing device to the electrical terminals of a vehicle battery, but the technician does not have to read or interpret test results from the battery tester. Instead, the tech console 254 retrieves the information directly from the battery tester via a wired data network, such as Ethernet, or a wireless data network, such as a Bluetooth or IEEE 802.11 wireless network. The server 250 implements network services that are compatible with a wide range of automotive testing equipment from multiple vendors to enable different service centers to use the server 250 with a wide range of testing equipment. For example, in the illustrative embodiment of
In another operating mode, the server 250 receives data from a commercially available multi-point inspection application 224. The MPI application 224 is a software program that typically collects diagnostic inspection data manually from the technician as the technician 202 performs a manual MPI inspection of the vehicle. The server 250 executes stored program instructions to implement the eMPI Web-service 264 and iEquipment control web service 265 that are compatible with the report formats from existing MPI application programs 224. The server 250 also provides diagnostic tool command and data retrieval through the iEquipment web service 265 to enable the client computing device 332 to send commands to the plurality of diagnostic tools 232 and receive results from the diagnostic procedures that the diagnostic tools 232 perform on the vehicle 290. The web console 252 receives compatible MPI data from the MPI web service 264 to accommodate service centers that use the existing commercial MPI software instead of the automated MPI and maintenance processes that are implemented by the server 250.
In the server 250, an administrator 270 reviews MPI report data and other diagnostic information that the web console 252 stores using an administrative console 256. The administrator 270 also controls the authorization and registration of specific pieces of diagnostic equipment 232 for use with the server 250 using the equipment serial and model numbers that are typically stored in a non-volatile memory in each piece of equipment, and a vendor token that is used for authentication and authorization of different accounts with the server 250. An individual account corresponds to, for example, a service center, a chain of multiple service centers, or to an individual technician in different configurations of the server 250. The administrative console 256 provides registration information about the connected diagnostic equipment 232 and software services that are registered with the server 250. For example,
In addition to the administrator 270, the server 250 provides aggregate MPI information to original equipment manufacturers (OEMs) 272. The OEMs 272 retrieve the MPI data from the server 250 through an OEM web console 275, and a network-based service aggregates MPI information from multiple service centers to enable the OEM 272 to review MPI and other diagnostic information from multiple service centers. The OEMs 272 include, for example, the vehicle manufacturers and part suppliers that provide replacement parts to service centers.
The technician uses a client computing device 332, such as a PC, smartphone, or tablet, to interact with the user interface that is provided by the web console 252. The technician typically performs an authentication “login” process to access the system 252 prior to performing the MPI. In the configuration of
The server 250 stores the result data from the MPI in the database 330. In some instances, when a single vehicle visits one or more service centers that share access to the database 330, the stored information provide vehicle maintenance history information to the technician. The server 250 transmits portions of the information in the database 330 to external databases, such as the external database 358, to provide access to aggregate information to third-parties via a business intelligence console 360. Examples of third-parties include automotive manufacturers and part supplier OEMs. The business intelligence console 360 provides aggregate information about the overall activity of one or more service centers to the third-parties. The database 358 optionally receives only portions of the VIN data that correspond to general makes and models of vehicles while portions of the VIN data that identify individual vehicles are not available to the business logic console 360.
Process 1100 begins as the system 200 receives an optional pre-inspection vehicle from a motor vehicle prior to commencement of a full multipoint inspection process (block 1104). Other embodiments of the process 1100 omit the pre-inspection vehicle data collection and report process, and the process 1100 continues as described in more detail with reference to the processing of block 1124 below.
During process 1100, the As illustrated in
Process 1100 continues as the server 250 identifies potential maintenance issues with the vehicle 904 based on DTCs and other vehicle information received from the vehicle data and transmission device 908 (block 1112). In the system 200, the server 250 accesses the database 330 that stores diagnostic trouble code data to enable the server 250 to identify potential maintenance issues that correspond to different DTCs. In some embodiments, the server 250 specifies the make, model, and year of the vehicle 904 using the VIN data to identify specific maintenance issues that have occurred in vehicles with a similar make, model, and year. The server 250 generates a report corresponding to the DTCs and other vehicle information corresponding to the vehicle 904. The report includes, for example, an explanation of the DTC codes for the user 270 and a recommendation to bring the vehicle 904 to a service center for a more detailed inspection if necessary. In the illustrative embodiment of
Process 1100 continues as the server 250 identifies an address that is associated with the electronic communication device 274 (block 1116). The server 250 identifies the address in a user registration information in the database 330 that associates the VIN from the vehicle 904 with the user 270. The address is, for example, an email address, telephone number, or social media account name that the user 270 uses for communication with the electronic communication device 274. The user 270 optionally performs a registration process if the server 250 fails to identify a suitable address that is associated with the VIN from the vehicle 904. The server 250 transmits the report to the electronic communication device, such as the mobile telephone 274, that is associated with the user 270 (block 1120). In the system 200, the server 250 transmits the report to the address that is associated with the mobile telephone 274, or another electronic communication device associated with the user 270 such as a tablet or personal computer.
Process 1100 continues with the multipoint inspection process that occurs when the vehicle 904 travels to a service center with the diagnostic system 200. In the system 200, the server 250 generates a GUI for the client computing device 332 (block 1124). The server 250 generates the GUI including control elements for each of the plurality of diagnostic tools 232. For example, if the diagnostic tools 232 include a battery monitor and a tire pressure monitor, the server 250 generates a GUI including controls to perform a battery and tire pressure monitoring procedures. In one embodiment, the server 250 is configured with a plurality of registered diagnostic tools and the server 250 generates the GUI including controls for each of the registered devices. In the system 200, the server 250 implements a web service that produces one or more HTML pages to implement the GUI through the tech console 254. The client computing device 332 receives the tech console GUI 254 from the server 250 and executes a web browser or other software application view the GUI.
During process 1100, the technician 202 uses the client computing device 332 to view the GUI and enter commands to operate the diagnostic tools. In the system 200, the client computing device 332 receives user input to execute a command and the server 250 receives the commands to perform diagnostic procedures that are transmitted from the client computing device 332 as web service requests (block 1128). The server 250 then transmits the command to one of the plurality of diagnostic tools 232 (block 1132). In some embodiments, the server 250 translates the command from a web service request that is received from the client computing device 332 into a different command protocol that is compatible with the selected diagnostic tool to perform the command.
Process 1100 continues as the server 250 receives transmissions from the diagnostic tools 232 in response to performing the diagnostic procedures on the vehicle 290 (block 1136). As described above, the diagnostic tools 232 transmit the diagnostic data to the server 250 through a wired or wireless data network. In many embodiments, at least one of the diagnostic tools 232 retrieves the VIN from the ECU in the vehicle 290, and the server 250 receives the VIN for the vehicle 290 in addition to other diagnostic data from the diagnostic tools 232. The analysis system 250 stores the diagnostic data in the database 330 as part of a vehicle history data in association with the VIN from the vehicle 290. In some embodiments, the technician also enters a request to order a new part for the vehicle 290 though the iShop web service 240.
After performing one or more diagnostic procedures, the system 200 generates a report that includes diagnostic data from at least one of the diagnostic procedures (block 1140). As describe above,
During process 1100, the server 250 transmits the report to the client computing device 332 and optionally to the electronic communication device 274 that is associated with the vehicle owner 270 (block 1144). In the server 250, the web console 252 transmits the report to the client computing device 332 to enable the technician 202 to use a web browser or other user software to review the full MPI report to diagnose issues with the vehicle 290 and to report on maintenance work that has been completed for the vehicle 290. The server 250 optionally identifies the address of the user account that is associated with the electronic communication device 274 and transmits the report to the electronic communication device 274 to enable the user 270 to review the report directly.
It will be appreciated that variants of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems, applications or methods. Various presently unforeseen or unanticipated alternatives, modifications, variations or improvements may be subsequently made by those skilled in the art that are also intended to be encompassed by the following claims.
This application claims priority to U.S. Provisional Application No. 61/931,370, which is entitled “Automotive Inspection System Using Network-Based Computing Infrastructure,” and was filed on Jan. 24, 2014, the entire contents of which are hereby incorporated by reference herein.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2015/012606 | 1/23/2015 | WO | 00 |
Number | Date | Country | |
---|---|---|---|
61931370 | Jan 2014 | US |