A vehicle diagnostic system

Abstract

The application discloses a vehicle diagnosis system for diagnosing a vehicle, which is characterized by comprising a data server and a plurality of diagnosis devices connected in communication with the data server, wherein when the diagnosis device is connected with the vehicle through an external interface, the data server verifies and matches basic information of the vehicle, device identification information of the diagnosis device and site information of a diagnosis site where the vehicle is located to form a matching relationship, the data server determines a diagnosis program corresponding to diagnosis operation to be performed by the vehicle at the diagnosis site according to the matching relationship, the diagnosis device is connected in communication with the vehicle and is used for completing a predetermined degree of diagnosis operation, and the data server and the diagnosis device jointly complete the whole diagnosis operation based on the diagnosis program.

Description

Technical Field

[0001] This invention relates to the field of vehicle diagnostic technology, and more particularly to a vehicle diagnostic system. Background Technology

[0002] Currently, vehicle production lines require multiple off-line diagnostics at different stages to ensure stable and reliable vehicle production. This means that after completing specific assembly processes, such as assembly, various indicators related to these processes are tested. If problems are found, the vehicle must be repaired or modified to resolve the fault until the test is passed before the vehicle can proceed to the next process or be rolled off the production line.

[0003] However, due to the different manufacturing processes of different vehicles, vehicle manufacturers need to develop separate diagnostic functions for each step of the diagnostic process, distributing diagnostic functions to different testing equipment and having diagnostic personnel at the corresponding workstations perform the corresponding operations, thereby ensuring the orderly diagnosis of vehicles throughout the production process.

[0004] However, this approach still presents several challenges. First, distributing diagnostic functions across different modules presents a challenge to system integration and coordination. Communication and collaboration between modules require complex design and debugging, increasing system complexity and development costs. Second, existing diagnostic functions are typically designed for specific vehicle models or specific diagnostic needs. Adjustments require redesigning new diagnostic equipment or re-flashing old equipment, leading to high maintenance and upgrade costs and poor compatibility. Furthermore, existing diagnostic systems often require high-performance hardware, further increasing system costs. Summary of the Invention

[0005] The purpose of this invention is to provide a vehicle diagnostic system that solves the problem of redundancy in diagnostic equipment and procedures during vehicle off-line diagnostics, improves the applicability and scalability of the diagnostic system, and makes system maintenance more convenient.

[0006] This invention provides a vehicle diagnostic system for diagnosing vehicles, comprising: a data server with a plurality of operating services; and multiple diagnostic devices communicatively connected to the data server. When a diagnostic device connects to the vehicle via an external interface, the data server verifies and matches the vehicle's basic information, the diagnostic device's device identification information, and the site information of the diagnostic station where the vehicle is located to form a matching relationship. Based on the matching relationship, the data server determines the diagnostic program corresponding to the diagnostic operation that the vehicle needs to perform at the diagnostic station. The diagnostic devices communicate with the vehicle and are used to complete a predetermined degree of diagnostic operation. The data server and the diagnostic devices jointly complete all diagnostic operations based on the diagnostic program.

[0007] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features: whenever a vehicle needs to perform a new diagnostic operation, any diagnostic terminal can be identified by the diagnostic personnel at the corresponding diagnostic station through a handheld terminal, and sent to the data server along with the station information stored in the handheld terminal for verification and matching. After the diagnostic personnel connect the diagnostic device to the vehicle, the diagnostic device communicates with the vehicle through the communication protocol set in the diagnostic device, obtains the vehicle's basic information, and sends it to the data server for verification and matching to obtain a matching relationship.

[0008] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features: a diagnostic device corresponds one-to-one with a vehicle; the diagnostic device connects to the vehicle through an external interface before the vehicle performs its first diagnostic operation; after the diagnostic device connects to the vehicle, it communicates with the vehicle through a communication protocol set in the diagnostic device and obtains the vehicle's basic information, which is then sent to a data server for verification and matching; each diagnostic station is equipped with a corresponding identification device; whenever a vehicle enters a diagnostic station, the identification device identifies the vehicle's vehicle identification information and sends the vehicle identification information and the station information of the diagnostic station to the data server for verification and matching to obtain a matching relationship.

[0009] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features: the diagnostic device pre-stores a protocol stack and preset services for calling the protocol stack, and the diagnostic operation is completed jointly by the diagnostic program and the diagnostic device, including: the data server sends and stores the diagnostic program to the diagnostic device through the running service, and controls the diagnostic device to execute the diagnostic program; during the execution process, the diagnostic device calls the protocol stack through the preset service to complete the data interaction with the vehicle and obtain the diagnostic result fed back by the vehicle; the diagnostic result is temporarily stored in the diagnostic device and sent to the data server when the diagnostic device and the data server are connected for communication.

[0010] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features: the diagnostic device pre-stores a protocol stack and preset services for calling the protocol stack, and the diagnostic operation is completed jointly by the diagnostic program and the diagnostic device, including: the data server executes the diagnostic program through the running service, and the diagnostic device calls the protocol stack through the preset service during the execution process to complete the data interaction between the data server, the diagnostic device and the vehicle, so that the data server obtains the diagnostic results fed back by the vehicle and stores them.

[0011] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features, wherein the diagnostic operation is a program flashing operation. When the data server determines the diagnostic program corresponding to the diagnostic operation that the vehicle needs to perform at the diagnostic station based on the matching relationship, it also confirms the flashing file that needs to be loaded into the vehicle based on the station information, and verifies the accuracy of the flashing file based on the basic information. Before the data server completes the diagnostic operation based on the diagnostic program and the diagnostic device, it flashes the flashing file into the vehicle through the diagnostic device.

[0012] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features, including: at least one handheld terminal held by a diagnostician and connected to a data server. The handheld terminal has a barcode scanner and stores site information of the diagnostic station where the diagnostician is located. The diagnostic device is provided with a device identifier containing device identification information. When the diagnostician scans the device identifier with the barcode scanner, the handheld terminal obtains the corresponding device identification information and sends the device identification information and the stored site information to the data server for verification and matching. After the data server and the diagnostic device jointly complete the diagnostic operation, the data server sends the corresponding diagnostic results to the handheld terminal for the diagnostician to confirm according to the matching relationship.

[0013] Furthermore, the vehicle diagnostic system provided by this invention may also have the following technical features: the handheld terminal has an interactive interface for allowing diagnostic personnel to select, adjust, and / or execute one or more diagnostic procedures. When the diagnostic result of the diagnostic operation indicates a diagnostic failure, the data server sends the diagnostic failure message and diagnostic result to the corresponding handheld terminal based on the site information, enabling the diagnostic personnel to perform troubleshooting operations and select the diagnostic procedure to be executed through the handheld terminal after troubleshooting. When the diagnostic personnel confirm the execution of the troubleshooting operation, the data server determines the corresponding diagnostic device based on the association between the terminal identification information and the device identification information, and runs the troubleshooting program through the running service, thereby completing the vehicle troubleshooting operation through the diagnostic device.

[0014] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical feature: whenever the data server completes a diagnostic operation based on the diagnostic program and the diagnostic device and the diagnosis is successful, the data server predicts the next diagnostic operation that the vehicle needs to perform based on the matching relationship and the preset vehicle diagnostic process and determines the corresponding diagnostic program, and further sends the diagnostic program to the diagnostic device to replace the diagnostic program that has already completed the diagnosis.

[0015] Furthermore, the vehicle diagnostic system provided by the present invention may also have the following technical features, wherein the diagnostic device includes: a core board, on which a diagnostic module, a cache module, and a wireless module are provided; an interface component adapted to the vehicle's external interface; an interaction component for enabling the diagnostic module to interact with the user; a power supply component electrically connected to the interface component, the wireless module, and the diagnostic module for providing power and power adaptation; and an expansion interface component electrically connected to the diagnostic module, wherein the diagnostic module is electrically connected to the vehicle through the interface component and is used to perform diagnostics on the vehicle; the cache module is electrically connected to the diagnostic module for caching the data generated by the diagnostic module during the diagnostic process; the wireless module is electrically connected to the diagnostic module for connecting the diagnostic module to the main controller; and the main controller is used to jointly perform diagnostics with the diagnostic module. The expansion interface component is any one or more of a USB interface, a Type-C interface, a flash memory interface, and a Pogo Pin interface.

[0016] The role and effect of invention

[0017] According to the vehicle diagnostic system provided by this invention, since multiple diagnostic devices are connected to the vehicle through communication with a data server, and a matching relationship is established between the diagnostic devices, the vehicle, and the diagnostic station, the data server can automatically determine the diagnostic program that the vehicle currently needs to execute. The data server and the diagnostic devices jointly complete the diagnostic operation of the vehicle. Therefore, the diagnostic system of this solution can not only realize the automated loading, running, and diagnosis of diagnostic programs during the vehicle's off-line process, but also flexibly adopt different operating modes for different diagnostic applications based on the cooperation between the data server and the diagnostic devices. For example, when the performance of the diagnostic device supports it, it runs the diagnostic program itself; when the performance is insufficient, it runs the diagnostic program through the server. The diagnostic device only guarantees the operation of basic services and protocols. This approach greatly reduces the performance requirements of the diagnostic device, lowers hardware costs, and the communication and collaborative work between different modules are relatively simple, with high flexibility and scalability, reducing system complexity and development costs.

[0018] Other features and advantages of the invention will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the invention. The objects and other advantages of the invention are realized and obtained in accordance with the structures particularly pointed out in the description, claims and drawings.

[0019] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0020] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the accompanying drawings used in the description of the specific embodiments or the prior art will be briefly introduced below.

[0021] Figure 1 This is a structural block diagram of a vehicle diagnostic system provided in an embodiment of the present invention.

[0022] Figure 2 This is a schematic diagram of the structure of the diagnostic device provided in an embodiment of the present invention.

[0023] Figure 3 This is a structural block diagram of the diagnostic device provided in an embodiment of the present invention.

[0024] Figure 4 The structural frame of the handheld terminal provided in the embodiment of the present invention.

[0025] Figure 5 This is a flowchart of the diagnostic process of the vehicle diagnostic system in an embodiment of the present invention. Detailed Implementation

[0026] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0027] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such orders can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein.

[0028] Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such process, method, product, or apparatus.

[0029] <Example 1>

[0030] During the vehicle rollout process, there are multiple diagnostic stations, each with corresponding diagnostic personnel responsible for performing different diagnostic operations on the vehicle.

[0031] Figure 1This is a structural block diagram of a vehicle diagnostic system provided in an embodiment of the present invention.

[0032] refer to Figure 1 The vehicle diagnostic system 1000 includes multiple diagnostic devices 100, a handheld terminal 200, and a data server 300. Both the diagnostic devices 100 and the handheld terminal 200 are communicatively connected to the data server 300.

[0033] In this embodiment, each diagnostic station is equipped with several diagnostic devices 100. Whenever a vehicle enters the diagnostic station, the diagnostic personnel connect one diagnostic device 100 (which can be any one) to the vehicle for subsequent diagnostic operations. After all diagnostics at this diagnostic station are completed, the diagnostic personnel disconnect the diagnostic device 100 from the vehicle for testing subsequent vehicles.

[0034] Figure 2 This is a schematic diagram of the structure of the diagnostic device provided in an embodiment of the present invention. Figure 3 This is a structural block diagram of the diagnostic device provided in an embodiment of the present invention.

[0035] The diagnostic device 100 is used to connect to the vehicle and is responsible for data exchange with the vehicle during the diagnostic process.

[0036] refer to Figure 2 and Figure 3 The diagnostic device 100 specifically includes a housing 01, a core board 10, an interface component 20, an interaction component 30, a power supply component 40, and an expansion interface component 50. The core board 10 includes a first substrate, a second substrate, a support component, and a diagnostic module 130, a cache module 131, a wireless module 150, and a Bluetooth module 170 disposed on the substrate.

[0037] In this embodiment, the diagnostic device 100 is a handheld diagnostic terminal; the data server 300 is a server that stores all the diagnostic programs required by the manufacturer during the vehicle production process. Diagnostic personnel carry the diagnostic device 100 during the diagnostic process and perform diagnostics on the vehicle using the pre-loaded diagnostic programs in the device. When a diagnostic program not loaded in the device 100 needs to be executed, the device 100 can be connected to the data server 300 for joint diagnostic work.

[0038] The core board 10 is used to implement the main diagnostic functions of the diagnostic device 100, such as sending diagnostic signals to the vehicle, organizing and uploading diagnostic data, and executing diagnostic programs. Next, the core board 10 and its related modules will be described in detail:

[0039] The two substrates are used to fix and electrically connect hardware components such as the diagnostic module 130, cache module 131, wireless module 150, interface component 20, interaction component 30, power supply component 40, and expansion interface component 50. In this embodiment, the first substrate and the second substrate are each a circuit board, and the support component is used to offset the second substrate from the first substrate to form a double-layer structure. The diagnostic module 130, cache module 131, wireless module 150, interface component 20, and power supply component 40 are all disposed on the side of the first substrate closer to the second substrate, that is, spatially located between the first substrate and the second substrate; the interaction component 30 is disposed on the side of the second substrate away from the first substrate, that is, spatially located between the second substrate and the housing 01.

[0040] As an alternative, the core board 10 can also use a single substrate instead of the first substrate, the second substrate, and the support components, with all related modules and components set on a single substrate.

[0041] The diagnostic module 130 is electrically connected to various modules, including the cache module 131, wireless module 150, interface component 20, interaction component 30, power supply component 40, and expansion interface component 50, and controls each module. Additionally, the diagnostic module 130 can be electrically connected to the vehicle via the interface component 20 to perform diagnostics on the vehicle.

[0042] The cache module 131 includes a high-speed memory set up in the diagnostic module 130 and a flash memory card connected via a flash memory interface.

[0043] In one specific implementation, the diagnostic module 130 is an ARM main processor of model Cortex-A7 (dual core), which supports parallel processing and is compatible with multiple diagnostic protocols. The high-speed memory consists of 256M DDR memory and 256M Nand-flash memory located in the ARM main processor, and the flash memory card is an SD card, which is connected to the ARM main processor through the SD card slot (i.e., expansion interface component 50).

[0044] like Figure 1 As shown, in this embodiment, the diagnostic device 100 is connected to the data server 300 via a wireless module 150. To perform vehicle diagnostics, the data server 300 works in conjunction with the diagnostic module 130. Specifically, the diagnostic module 130 stores different diagnostic programs and performs vehicle diagnostics via the interface component 20. During the diagnostic process, diagnostic data, processing results, logs, and other data are stored in the cache module 131. Furthermore, when the diagnostic device 100 establishes a connection with the data server 300 via the wireless module 150, it also uploads the cached data from the cache module 131 to the data server 300, where the data server 300 performs analysis, statistics, and archiving of the data.

[0045] However, since there are many diagnostic programs for actual vehicles, the low-cost diagnostic module 130 may not be able to store all of them. In this case, if the diagnostic device 100 needs to execute a diagnostic program that has not been loaded, the diagnostic module 130 can connect to the data server 300, retrieve the diagnostic program from the data server 300, and load or replace it. Alternatively, the diagnostic module 130 may not load the diagnostic program, but instead run the diagnostic program through the data server 300 and complete the diagnosis by forwarding diagnostic signals through the diagnostic device 100.

[0046] During the diagnostic process, specifically due to the compatibility of the ARM main processor, it stores various communication and hardware protocols required for the diagnostic process through a protocol stack. Therefore, the diagnostic module 130 can communicate with the vehicle and call hardware such as the wireless module 150 and the touch screen 193 based on these protocols. When diagnostic data, processing results, logs, and other data are obtained, the ARM main processor will organize and archive this data. If the wireless module 150 is connected to the main controller 20 at this time, it will also upload the organized data to the main controller 20 in parallel.

[0047] The wireless module 150 is a WIFI module, used to enable the diagnostic module 130 to communicate with the main controller 20 via WIFI and to complete data transmission and reception. The WIFI module 150 includes a WIFI chip 151 and an antenna 152.

[0048] The WIFI chip 151 is electrically connected to the diagnostic module 130 on the substrate and to the second DC-DC converter 144. The operating voltage is obtained from the second conversion terminal of the second DC-DC converter 144 to ensure operation. The antenna 152 is connected to the WIFI chip 151 and is used to provide signal transmission and reception.

[0049] In one practical application, the diagnostic module 130 has a diagnostic program pre-downloaded in it. When the WIFI module 150 establishes a communication connection with the main controller 20, it can upload the diagnostic data and corresponding results obtained by the diagnostic module 130 after completing the vehicle diagnosis to the server for archiving and storage.

[0050] In another practical application, the diagnostic module 130 does not have the required diagnostic program. In this case, the main controller 20 runs the diagnostic program and sends diagnostic signals to the diagnostic module 130 via the wireless module 150. The diagnostic module 130 then calls various protocols to communicate with the vehicle to complete the diagnosis. The diagnostic data and corresponding results are temporarily stored and organized in the cache module 131 and then uploaded to the main controller 20 in parallel for storage. In this case, the main controller 20 and the diagnostic module 130 jointly perform vehicle diagnosis, so the diagnostic module 130 can flexibly adapt to different diagnostic scenarios in practical applications.

[0051] To achieve high-bandwidth transmission in the diagnostic device 100, the bandwidth rate of the entire wireless module 150 needs to reach 600-900 Mbits (preferably 750 Mbits). Correspondingly, the connection bandwidth rate between the diagnostic module 130 and the WIFI chip 151 needs to reach 400-1000 Mbits (preferably 700 Mbits). In this embodiment, the WIFI chip 151 supports two frequencies: 2.4G and 5G. The antenna 152 is a dual-antenna system supporting MIMO, with a signal frequency of 80MHz, enabling the 5G WIFI to support a maximum transmission rate of 867Mbps. Simultaneously, the high-speed memory in the cache module 131 also supports high-speed read and write operations, effectively supporting the connection bandwidth rate of the diagnostic module 130. This design gives the diagnostic device 100 high-bandwidth characteristics, and combined with the aforementioned parallel processing capabilities, it enables timely downloading and uploading of diagnostic data.

[0052] The interface assembly 20 is partially mounted on the housing 01 and partially mounted on the base plate, and is used to connect to the vehicle's external interfaces. The interface assembly 20 includes a connector interface 121, two adapter interfaces 122(1) and 122(2) and an automatic switching switch 123.

[0053] The connector interface 121 is matched with the model of the vehicle's external interface, such as an OBD interface or other industrial-grade connector interface. The connector interface 121 is installed on the housing 01, so as to facilitate the diagnostic personnel to connect the diagnostic device 100 to the vehicle. The adapter interface 122 corresponds to the interface protocol supported by the vehicle's external interface. The adapter interface 122 and the automatic switching switch 123 are installed on the base plate. The two adapter interfaces 122(1) and 122(2) are electrically connected to the diagnostic module 130 respectively.

[0054] As one specific implementation, the adapter interface 122 is a CAN interface and an ETH interface. It can be understood that the adapter interface can be set according to the interface protocol supported by various vehicle models in the actual market. For example, in other implementations, the adapter interface 122 can also be a CANFD interface or other interfaces that can support vehicle diagnostics, and three or more adapter interfaces 122 can be set as needed.

[0055] The automatic switching switch 123 is used to automatically switch the appropriate adapter interface 122 according to the interface protocol corresponding to the external interface when the connector interface 121 is connected to the vehicle's external interface. Specifically, the automatic switching switch 123 is an automatic switching switch matrix, which is set between the connector interface 121 and the adapter interface 122, and can automatically adapt to different OBD interface pin definitions. When a signal type output from the vehicle's external interface is received, the automatic switching switch 123 switches to match the corresponding adapter interface 122 according to the signal type.

[0056] In this embodiment, since different interface types have different pin definitions in the OBD interface, when the vehicle is connected, different interface protocols will send electrical signals to the connector interface 121 through different pins. Therefore, the automatic switching switch 123 can determine the type of the current interface protocol based on the number of pins corresponding to the electrical signal, and thus switch to match the corresponding adapter interface 122.

[0057] In practice, due to vehicle security access mechanisms, diagnostic operations often require the transmission and reception of diagnostic data through specific physical access interfaces on the vehicle. Furthermore, different vehicles may support different interface types, causing difficulties in customizing diagnostic equipment. Therefore, this solution improves the versatility of the diagnostic device 100 during vehicle off-line diagnostics by pre-setting commonly used vehicle interface types on the market and automatically adapting to different vehicles via automatic switching switches 123.

[0058] The interactive component 30 is mounted on the housing and is used to enable the diagnostic module 130 to interact with the user.

[0059] As one specific implementation method, such as Figure 2 As shown, the interactive component 30 includes four indicator lights 191 and one button 192. Correspondingly, the front of the housing has five mounting holes that match the number and shape of the indicator lights 191 and the button 192.

[0060] The indicator light 191 is used to indicate the execution result of the diagnostic program of the diagnostic module 130 or other results. In one specific embodiment, each indicator light 191 may be a charging indicator light indicating the charging status of the diagnostic device 100, a running indicator light indicating whether the diagnostic program is running, a vehicle connection indicator light indicating whether the interface component 20 has been successfully connected to the vehicle, a WIFI indicator light indicating the WIFI connection status, etc.

[0061] Button 192 is used to allow diagnostic personnel to perform simple control of the diagnostic device 100. In one specific implementation, each button 192 can be a power button for turning the diagnostic device 100 on and off, as well as other function keys adapted to the diagnostic program, such as starting the diagnostic process or pausing the diagnostic process.

[0062] The aforementioned indicator light 191 and button 192 are fixed on the second base plate and electrically connected to the diagnostic module 130, respectively. They are exposed to the outside of the housing through the mounting holes on the housing so that the user can check the status of the indicator light or operate the button.

[0063] In this embodiment, the interactive component 20 abandons the complex human-computer interaction part. It only uses simple button operation and indicator lights to indicate the current operating status to the diagnostic personnel. In actual operation, the diagnostic personnel only need to start the vehicle diagnostic device 100 by pressing a button and connecting it to the vehicle's external interface to start the diagnosis. This greatly simplifies the diagnostic operation of the diagnostic personnel and is both portable and easy to use.

[0064] It is understood that the number, location, and corresponding functions of the indicator lights 191 and buttons 192 can be adjusted according to actual development needs, and this embodiment does not impose any restrictions on this.

[0065] In other implementations, the interaction component 30 may also include a speaker and a touchscreen. The speaker can provide prompts to the diagnostic personnel by playing audio; the touchscreen may be a touch LCD screen that displays the corresponding interface based on the diagnostic program stored in the diagnostic module 130, allowing the diagnostic personnel to perform relevant operations.

[0066] The power supply assembly 40 is electrically connected to the interface assembly 20, the wireless module 150, and the diagnostic module 130, respectively, for providing power and performing power adaptation.

[0067] Specifically, the power supply assembly 40 includes a protection assembly 141, a first DC-DC converter 142, a power switch 143, and a second DC-DC converter 144 connected in series, and also includes a battery module electrically connected to the first DC-DC converter 142, the battery module including a battery manager 145 and a battery 146.

[0068] The protection component 141 is used to protect the power output by the vehicle through the interface component 20. It has a fuse and a transient diode (TVS). When the vehicle erroneously outputs a large voltage, the protection component 141 can protect the diagnostic device 100 from damage in time.

[0069] The first conversion terminal of the first DC-DC converter 142 is electrically connected to the protection component 141, and the second conversion terminal is electrically connected to the first conversion terminal of the second DC-DC converter 144 via a power switch 143. In this embodiment, the first DC-DC converter 142 is used to convert between 12V and 5V voltages, with the voltage at its first conversion terminal being 12V and the voltage at its second conversion terminal being 5V.

[0070] The power switch 143 is used to control the switching on and off of the vehicle and the power supply of the battery 146 to the diagnostic module 130, thereby enabling the operation of the entire diagnostic device 100.

[0071] The second conversion terminal of the second DC-DC converter 144 is electrically connected to the diagnostic module 130 and the Wi-Fi module 150. In this embodiment, the second DC-DC converter 144 is used to convert between 5V and 3.3V voltages, with the voltage at its first conversion terminal being 5V and the voltage at its second conversion terminal being 3.3V.

[0072] In this embodiment, since a battery 146 is provided and a battery manager 145 is used to manage and control the power output of the battery 146, the diagnostic device 100 can also operate normally when not connected to a vehicle, making it convenient for diagnostic personnel to carry and use.

[0073] The expansion interface component 50 is fixed to the housing and electrically connected to the diagnostic module 130 to achieve the corresponding function.

[0074] In one specific implementation, the expansion interface component 50 is a Pogo Pin interface 161 and a flash memory interface 162.

[0075] The Pogo Pin 161 is located on the side of the casing and can support data transfer and charging simultaneously.

[0076] The flash memory interface 162 is an SD card slot for inserting an SD card and enabling the diagnostic module 130 to read the SD card, thereby making the SD card a cache module 131.

[0077] In other embodiments, the expansion interface component can also be any one of a USB interface, a Type-C interface, or any combination of multiple USB interfaces, Type-C interfaces, Pogo Pin interfaces, and SD interfaces. Specifically:

[0078] The USB interface is used to connect a USB flash drive, enabling the reading of its contents. When used in vehicle diagnostic devices, the USB flash drive can be used to install system image files, allowing the installation, updating, or flashing of the diagnostic module 130's system to be completed via the USB flash drive. Additionally, the USB interface can also be used to export diagnostic data and results from the diagnostic module 130.

[0079] The Type-C interface serves a similar purpose to the Pogo Pin interface, supporting both data transfer and charging simultaneously.

[0080] The Bluetooth module 170 enables the diagnostic module 130 to communicate with a Bluetooth-enabled configuration device held by the diagnostic personnel. In practical applications, the Bluetooth module 170 also allows the diagnostic personnel to modify the configuration information of the diagnostic module 130 via the Bluetooth connection, such as configuring or changing the WIFI SSID and IP address.

[0081] In this embodiment, the overall voltage of the core board 10 is below 5V, and the power consumption is controlled between 1.5W and 2.0W. The power consumption of the entire diagnostic device 100 is controlled between 3W and 5W. Therefore, the core board 10 also has low power consumption characteristics, which can effectively meet the long-term vehicle diagnostic needs.

[0082] It should also be noted that, in specific implementations, the diagnostic device 100 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the diagnostic device 100 may only include the components necessary for implementing the embodiments of this application, and not necessarily all the components shown in the figures.

[0083] The above is a detailed introduction to the diagnostic device 100. The handheld terminal 200 will now be described in detail:

[0084] Figure 4 This is a structural block diagram of a handheld terminal provided in an embodiment of the present invention. (Reference) Figure 4 The handheld terminal 200 includes a core device 60, an operating device 70, a barcode scanner 80, and an interactive component 90.

[0085] The core device 60 specifically includes a first housing, a core board 10', an interface module 62, a heat dissipation module 63, a power supply module 64, and an expansion interface module 65.

[0086] The operating device 70 has at least a second housing, an operating control module 72, and a display 73.

[0087] The display 73 is located on the side of the second housing facing the user. The first housing has an open side, which mates with the side of the second housing opposite to the display 73, thereby achieving a structurally fixed connection between the core device 60 and the operating device 70.

[0088] In this embodiment, the handheld terminal 200 is a handheld diagnostic terminal; the core device 60 stores the drivers, protocols and services necessary for communication with the vehicle, and the operating device 70 stores the diagnostic programs required by the manufacturer during the vehicle off-line process, as well as the operating system necessary for human-machine interaction with diagnostic personnel.

[0089] In the first usage scenario, diagnostic personnel can carry a handheld terminal 200 during the diagnostic process. After connecting the vehicle diagnostic equipment to the vehicle, they can run the diagnostic program through the operating device 70. The core device 60 communicates and interacts with the vehicle by transmitting the signals generated during the diagnostic program. Finally, the operating device 70 displays the diagnostic data and results to the diagnostic personnel, enabling the operating device 70 and the core device 60 to jointly diagnose the vehicle.

[0090] In the second usage scenario, when problems occur during the vehicle diagnostic process (such as the vehicle diagnostic fails), the diagnostic personnel can also debug the diagnostic program or the vehicle through the operating device 70. During this process, the core device 60 also completes the communication and interaction with the vehicle.

[0091] The core board 10' is used to implement the main diagnostic functions of the core device 60, such as sending diagnostic signals to the vehicle and organizing and uploading diagnostic data. The core board 10' includes a base plate, and a diagnostic module 66, a cache module 67, and a wireless module 68 disposed on the base plate.

[0092] In this embodiment, the substrate is a circuit board used to fix and electrically connect hardware such as the diagnostic module 66, cache module 67, wireless module 68, interface module 62, heat dissipation module 63, power supply module 64, and expansion interface module 65.

[0093] The diagnostic module 66, cache module 67, wireless module 68, interface module 62, heat dissipation module 63, power module 64, and expansion interface module 65 in the aforementioned handheld terminal 200 are functionally similar to the diagnostic module 130, cache module 131, wireless module 150, interface component 20, power component 40, and expansion interface component 50 in the diagnostic device 100, so they will not be described in detail.

[0094] The heat dissipation module 63 is disposed inside the first housing and located on one side of the core board 10', and is used to dissipate heat from the operating device 70, the core board 10', and the power module 64. An air outlet is provided on the other side of the first housing, so that air circulates inside the first housing to ensure heat dissipation performance.

[0095] The above is a detailed introduction to the core device 60. The following describes the operating device 70:

[0096] The operation control module 72 is used to control the operation of various hardware components in the handheld terminal 200, and to perform diagnostics together with the diagnostic module 66.

[0097] In one implementation, the operation control module 72 is an Intel mobile platform processor, supporting a Windows 10 operating system, and the handheld terminal 200 is equipped with 8GB of RAM and 256GB of storage. The display 73 is a screen supported by this Intel processor. In actual use, the handheld terminal 200 can be a tablet computer with an operating system (i.e., the second operating system layer 2006) installed, enabling human-computer interaction with diagnostic personnel, facilitating the debugging and execution of diagnostic programs.

[0098] In this embodiment, the diagnostic module 66 is only responsible for communicating with the vehicle, while the Intel mobile platform processor is responsible for connecting with upstream and downstream systems, data storage, and timely debugging. Therefore, the diagnostic module 66 can use a lower-cost chip, such as a dual-core ARM main processor with a processing performance of 600MHz-900MHz (preferably 700MHz) in this embodiment. While the handheld terminal 200 needs to use a high-performance processor, such as the multi-core Intel mobile platform processor with a processing performance of 2.0GHz-2.5GHz (preferably 2.2GHz) in this embodiment, the handheld terminal 200 can use existing computer equipment and support the running of diagnostic programs and human-machine interaction through existing operating systems. The additional development work for vehicle adaptation can be concentrated on the low-cost diagnostic module 66. Ultimately, the low-cost core device and the high-performance operating device work together to complete the diagnostic operation for the vehicle. Therefore, the handheld terminal 200 in this solution still has high-performance vehicle diagnostic capabilities while reducing costs.

[0099] As one implementation, the handheld terminal 200 in this embodiment is also equipped with a barcode scanner 80.

[0100] The barcode scanner 80 includes a scanning button and a scanning indicator light located on the second housing, both of which are electrically connected to the handheld terminal 200. In practical applications, vehicle and other vehicle diagnostic equipment may have QR codes or barcodes. Diagnostic personnel can align the scanning indicator light with the location to be scanned and press the scanning button to activate the scanning indicator light to perform a scan, thereby enabling the operation control module 72 to acquire the data stored in the QR code or barcode for subsequent processing.

[0101] The interactive component 90 includes indicator lights, buttons, speakers, and other components required by the handheld terminal 200 during use.

[0102] In one specific implementation, the interactive component 90 in this embodiment comprises three indicator lights mounted on the core device 60, three buttons mounted on the core device 60, and four buttons mounted on the handheld terminal 200. Specifically,

[0103] Three indicator lights are located on the side of the first housing 110, which are respectively a charging indicator light to indicate the charging status of the handheld terminal 200, a running indicator light to indicate whether the diagnostic program is running, and a vehicle connection indicator light to indicate whether the interface module 20 has been successfully connected to the vehicle.

[0104] Three buttons are located on the side of the first housing: a diagnostic button for start-stop diagnostics, a vehicle information acquisition button for obtaining diagnostic data from the vehicle, and a hard-start button for performing a hard-start on the core device 60.

[0105] Four buttons are located on the side of the second housing of the handheld terminal 200: two volume control buttons for increasing and decreasing volume, a power button for turning the handheld terminal 200 on and off, and a Win key for the handheld terminal 200.

[0106] The diagnostic button for start-stop diagnostics, the vehicle information acquisition button for obtaining diagnostic data from the vehicle, and the hard start button for hard-starting the core device 60.

[0107] In this embodiment, the first housing and the second housing are provided with mounting holes for mounting the adaptive interactive component 90.

[0108] It should be noted that although the indicator lights and buttons of the aforementioned interactive component 90 are all located on the side of the first or second housing, in practical applications, the indicator lights and buttons can also be located on the front or back of the housing, or other locations that are convenient for users to observe and use. This embodiment does not impose any restrictions on this. Furthermore, it is understood that the number of indicator lights and buttons and their corresponding functions can also be adjusted according to actual development needs, and this embodiment does not impose any restrictions on this either.

[0109] In other implementations, the interactive component 90 may also include a speaker to prompt the diagnostic personnel by playing audio.

[0110] It should also be noted that, in specific implementations, the handheld terminal 200 may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the handheld terminal 200 may only include the components necessary for implementing the embodiments of this application, and not necessarily all the components shown in the figures.

[0111] The above is a detailed introduction to the handheld terminal 200.

[0112] The data server 300 is used to manage all diagnostic devices 100 and handheld terminals 200, and is responsible for storing diagnostic data and results.

[0113] The data server 300 has multiple running services and stores all diagnostic programs. Each diagnostic program has a pre-existing matching relationship with the site information of the diagnostic site within the data server 300.

[0114] In this embodiment, the core device 60, handheld terminal 200, and data server 300 perform vehicle diagnostics through a specific software architecture. The software architecture will be described in detail below.

[0115] The vehicle diagnostic software architecture includes the operating system layer, protocol layer, middleware layer, and application layer.

[0116] The operating system layer includes the operating system and the drivers corresponding to the diagnostic system hardware (the diagnostic system hardware is the wireless module 150, interface module 20, heat dissipation module 30, power module 40, expansion interface module 50, etc. in the diagnostic device 100, or the barcode scanner 80, interaction component 90, interface module 62, heat dissipation module 63, power module 64, and expansion interface module 65, etc. in the core device 60).

[0117] In this embodiment, the operating system and hardware drivers are used to provide functions such as raw hardware drivers, process calls, and memory management. The protocol layer, middleware layer, and application layer are set on the operating system.

[0118] The protocol layer includes a hardware protocol stack for driving the hardware and a network protocol stack for communication.

[0119] In this embodiment, the hardware protocol stack includes multiple hardware driver protocols corresponding to the diagnostic system hardware, such as a light driver protocol corresponding to the indicator lights. The network protocol stack includes an Ethernet protocol stack and a CAN protocol stack. The network protocol stack includes standard TCP / IP protocols, data server communication heartbeat protocols, etc., while the CAN protocol stack includes various diagnostic communication protocols (such as CAN protocol, ETH protocol, etc.). Furthermore, in practical applications, the protocol layer may also include other auxiliary protocols.

[0120] The middle layer includes process call management services and process communication management services.

[0121] The process call management service is used to manage the calls to applications and preset services in the application layer, as well as to detect and correct failures of preset services and various protocols.

[0122] The process communication management service is used to manage all inter-process communication between the application layer, protocol layer, and operating system layer.

[0123] In this embodiment, the operating system layer, protocol layer, and middleware layer are configured on the core device 60 of the diagnostic device 100 and the handheld terminal 200, while the application layer is configured on the operating device 70 of the handheld terminal 200 and the data server 300. The middleware layer's process communication management service can manage inter-process communication across devices through remote call services (such as RPC services).

[0124] In the first implementation, the data server 300 executes the diagnostic program through a running service. Hardware call requests and other related requests generated during the program's execution are sent to the process communication management service of the diagnostic device 100 via a remote call service. The process call management service then determines the corresponding preset service based on the request and uses this preset service to invoke the appropriate protocol to complete the data interaction between the data server 300, the diagnostic device 100, and the vehicle. In subsequent communication, the diagnostic data and results fed back by the vehicle are sent to the data server 300 for storage. This enables the data server 300 and the diagnostic device 100 to jointly perform diagnostic operations on the vehicle.

[0125] Similarly, when the diagnostic program is run through the operating device 70 of the handheld terminal 200, the hardware call request is sent to the core device 60 through the remote call service for subsequent processing, thereby enabling the operating device 70 and the core device 60 to jointly complete the diagnostic operation of the vehicle.

[0126] In a second implementation, after determining the diagnostic program to be executed, the data server 300 can also transmit the diagnostic program to the diagnostic device 100 (equivalent to the application layer being partially located in the diagnostic device 100), and then the diagnostic device 100 executes the diagnostic program. In this implementation, the process communication management service of the diagnostic device 100 can directly send the hardware call request and other related requests of the diagnostic program to the process call management service. Subsequently, the process call management service determines the corresponding preset service based on the request, and completes the data interaction between the diagnostic device 100 and the vehicle by calling the corresponding protocol through the preset service. During subsequent communication, the diagnostic data and results fed back by the vehicle are temporarily stored until the diagnostic device 100 establishes a communication connection with the data server 300, at which point the diagnostic data and results are sent to the data server 300 for storage. This also enables the data server 300 and the diagnostic device 100 to jointly complete the diagnostic operation of the vehicle.

[0127] In the first embodiment described above, the diagnostic device 100 is only responsible for communication and interaction with the vehicle, while the data server 200 is responsible for running the diagnostic program and collecting and analyzing the subsequent diagnostic results. In the second embodiment, the diagnostic device 100 is responsible for running the diagnostic program and communicating with the vehicle, while the data server 200 is responsible for determining the diagnostic program and collecting and analyzing the subsequent diagnostic results. Therefore, it can be seen that the diagnostic device 100 in the vehicle diagnostic system 1000 is responsible for a predetermined degree of diagnostic operation, and the data server 200 and the diagnostic device 100 jointly complete all diagnostic operations. The extent to which the diagnostic device 100 performs diagnostic operations depends on the computing power of the diagnostic device 100 and the vehicle's off-line diagnostic process.

[0128] The application layer includes at least one diagnostic procedure and a variety of preset services.

[0129] Different diagnostic procedures are used to perform different diagnostic operations on a vehicle, such as radar calibration, window calibration, camera calibration, software remapping, ECU testing, etc.

[0130] The preset services include vehicle communication services for calling the network protocol stack and the CAN protocol stack, as well as various services corresponding to different hardware protocol types. These services are used to uniformly call the corresponding hardware protocols to further control the hardware, thereby realizing the functions required by the diagnostic program. In this embodiment, each preset service occupies its own process.

[0131] In practice, direct access to hardware services through the application layer can lead to conflicts. For example, when a diagnostic program occupies a piece of hardware, it can cause other diagnostic programs to fail to access that hardware. Therefore, it is necessary to use a pre-defined service for unified invocation to resolve the conflict between applications.

[0132] In this embodiment, all diagnostic procedures are set in the data server 300 and the operating device 70, and preset services are set in the diagnostic terminal 100 and the operating device 70 (equivalent to the entire application layer being set in the operating device 70). The data server 300 can automatically determine the diagnostic procedures to be executed based on the vehicle's status and the diagnostic station it is located at; while on the handheld terminal 200, diagnostic personnel can also select and execute the required diagnostic procedures through the display screen of the operating device 70.

[0133] It should be noted that although this embodiment illustrates that the application layer can be entirely or partially located in the diagnostic device 100, the operating device 70, and the data server 300, in practical applications, the application layer can also be entirely or partially located in the core device 60 or other computing devices. For example, the diagnostic program and some preset services can be located in the operating device 70, while other preset services can be located in the diagnostic device 60, or the diagnostic program and preset services can all be located in the data server 300, etc. The application layer designed in this vehicle diagnostic software architecture can be flexibly set on different platforms according to hardware conditions.

[0134] In one implementation, when the vehicle diagnostic device 1000 connects to the vehicle, the process call management service calls the vehicle communication service to communicate with the vehicle and determines the communication protocol compatible with the current vehicle from the CAN protocol stack. In subsequent communication with the vehicle, the compatible communication protocol is used to complete data exchange.

[0135] Figure 5 This is a flowchart of the diagnostic process of the vehicle diagnostic system in an embodiment of the present invention.

[0136] refer to Figure 5 To facilitate explanation, the following section will take the software rewriting operation of the vehicle's ECU during the vehicle off-line inspection as an example to provide a detailed introduction to the diagnostic process of the vehicle diagnostic system.

[0137] Step S1: When the diagnostic device 100 connects to the vehicle through the interface component 20, the data server 300 verifies and matches the vehicle's basic information, the diagnostic device's device identification information, and the site information of the diagnostic site where the vehicle is located to form a matching relationship.

[0138] In one implementation, the diagnostic device 100 connects to the vehicle and establishes communication with it via a protocol layer. This allows it to obtain basic information about the vehicle, including its VIN (Vehicle Identification Number), vehicle parameters, and system software version. This data is then unpacked via the protocol layer and, along with the device identification information of the diagnostic device 100, is sent to the data server 300 via the Wi-Fi module 150.

[0139] When the diagnostic personnel connect the diagnostic device 100 to the vehicle, they need to scan the diagnostic device 100 with the barcode scanner 80 of the handheld terminal 200 (the diagnostic device 100 has a device identifier containing device identification information, such as a QR code). At this time, the handheld terminal 200 can obtain the device identification information of the diagnostic device 100 and send it to the data server 300 along with the site information of the current diagnostic site stored in the handheld terminal 200.

[0140] Through the above operations, the data server 300 can establish a matching relationship between the diagnostic device 100, the diagnostic station, and the vehicle.

[0141] In step S2, the data server 300 determines the flashing file to be loaded into the vehicle and the corresponding flashing verification program (i.e., diagnostic program) based on the matching relationship.

[0142] In this embodiment, since the data server 300 has pre-stored corresponding relationships between each diagnostic program and diagnostic site, the associated diagnostic program can be matched. In practical applications, the matching of diagnostic programs can be further completed based on the vehicle's basic information.

[0143] In addition, after the flashing file is determined, the data server also needs to verify the accuracy of the flashing file based on the vehicle's basic information, such as version number verification, in order to avoid errors in the flashing file.

[0144] In step S3, the data server 300 establishes a communication connection with the vehicle through the running service control diagnostic device 100, and further completes the diagnostic operation together with the diagnostic device 100 based on the flashing file and flashing verification program.

[0145] Specifically, the data server 300 encapsulates the flash file and sends it to the process communication management service of the diagnostic device 100 via remote call service. Then, the diagnostic device 100 processes the flash file layer by layer through the middle layer, protocol layer and operating system layer (such as unpacking, encapsulating according to the communication protocol supported by the vehicle, calling the interface component 20 for transmission, etc.) and flashes the flash file into the vehicle.

[0146] Next, after the flashing is completed, the data server 300 executes the flashing verification program. The flashing verification program diagnostic device 100 sends relevant requests, and the process communication management service enables the process call management service to receive the aforementioned relevant requests through the RPC service. The process call management service determines the preset service to be called from the application layer according to the relevant requests, and calls the relevant protocol in the protocol layer through the preset service.

[0147] If the relevant request is a hardware call request, the identified hardware-related preset service will call the relevant hardware protocol, which in turn calls the operating system layer driver to cause the relevant diagnostic system hardware to perform the corresponding operation.

[0148] If the relevant request is a communication request, the process call management service will control the vehicle communication service to obtain the communication request, parse it, and encapsulate the communication request according to the previously determined communication protocol called by the vehicle communication service. The communication request is then sent to the operating system layer, and the operating system layer calls interface module 20 to send the encapsulated communication request to the vehicle through interface module 20.

[0149] Finally, the flashing verification program completes the integrity verification of the files written to the vehicle (i.e., the flashed data is consistent with the data actually written to the vehicle module) and generates the verification result.

[0150] The above is the system process for performing software flashing on a vehicle. Similarly, the diagnostic process for other vehicles is similar.

[0151] If the diagnosis indicates a vehicle malfunction after completion, the data server 300 will send the diagnosis result and troubleshooting notification to the corresponding diagnostic personnel's handheld terminal 200 based on the matching relationship, reminding the diagnostic personnel to perform troubleshooting operations on the vehicle. After the diagnostic personnel complete the troubleshooting, they need to re-execute the corresponding troubleshooting procedure, as detailed below:

[0152] The handheld terminal 200 allows diagnostic personnel to select, adjust, and / or execute troubleshooting procedures via the display 73. When the diagnostic personnel confirm the execution of the troubleshooting operation, the data server 300 determines the corresponding diagnostic device 100 based on the association between the terminal identification information and the device identification information, and runs the troubleshooting procedure through the running service, thereby completing the vehicle troubleshooting operation through the diagnostic device 100. The process of the data server 300 running the troubleshooting procedure is similar to the process of running the diagnostic procedure, and will not be described in detail here.

[0153] <Example 2>

[0154] The difference from Embodiment 1 is that in Embodiment 2, whenever a new vehicle begins its offline diagnostic operation, the diagnostic personnel connect a diagnostic device 100 (which can be any device) to the vehicle. During all subsequent diagnostic tests, the diagnostic device 100 does not need to be disconnected and can continuously perform different diagnostic operations at different diagnostic stations until the vehicle completes all diagnostics. In other words, in Embodiment 2, during a complete vehicle diagnostic process, there is a one-to-one correspondence between the diagnostic device 100 and the vehicle. After the diagnostic device 100 is connected to the vehicle, it communicates with the vehicle via a communication protocol and obtains the vehicle's basic information. This information, along with the device identification information of the diagnostic device 100, is then sent to the data server 300 for verification and matching.

[0155] In this second embodiment, each diagnostic station is equipped with a corresponding identification device. Whenever a vehicle enters a diagnostic station, the identification device will automatically identify the vehicle identification information (e.g., the vehicle's VIN code) and send the vehicle identification information and the station information of the diagnostic station to the data server 300 for verification and matching to obtain a matching relationship.

[0156] Through the above process, the vehicle diagnostic system can automatically establish a matching relationship between the diagnostic device 100, the vehicle, and the diagnostic station, and subsequently, the data server 300 will automatically match the diagnostic program to perform diagnostic operations on the vehicle.

[0157] Furthermore, in this second embodiment, whenever the data server 300 successfully completes a diagnostic operation based on the diagnostic program and the diagnostic device, the data server 300 also predicts the next diagnostic operation that the vehicle needs to perform based on the matching relationship and the preset vehicle diagnostic process, and determines the corresponding diagnostic program. This diagnostic program is then sent to the diagnostic device 100 to replace the already completed diagnostic program. In this way, the diagnostic program can be pre-loaded into the diagnostic device 100, improving the overall production cycle of the vehicle diagnostic process and, to some extent, avoiding the problem of poor signal causing the diagnostic program to not be loaded into the terminal in time, thus affecting vehicle diagnostic efficiency.

[0158] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A vehicle diagnostic system for diagnosing vehicles, characterized in that, include: Data server; as well as Multiple diagnostic devices are communicatively connected to the data server. When the diagnostic device connects to the vehicle via an external interface, the data server verifies and matches the vehicle's basic information, the diagnostic device's identification information, and the site information of the diagnostic station where the vehicle is located to form a matching relationship. The data server determines the diagnostic procedure corresponding to the diagnostic operation that the vehicle needs to perform at the diagnostic station based on the matching relationship. The diagnostic device is communicatively connected to the vehicle and is used to perform a predetermined level of diagnostic operations. The data server and the diagnostic device jointly complete all the diagnostic operations based on the diagnostic program. Each of the diagnostic devices can have its device identification information obtained by the corresponding diagnostic site, and this information, along with the site information, can be sent to the data server for verification and matching. Whenever the vehicle needs to perform a new diagnostic operation, when the diagnostic device connects to the vehicle, the diagnostic device communicates with the vehicle through the communication protocol set in the diagnostic device, obtains the vehicle's basic information, and sends it to the data server for verification and matching to obtain the matching relationship.

2. The vehicle diagnostic system according to claim 1, characterized in that: in, The diagnostic device corresponds one-to-one with the vehicle. The diagnostic device connects to the vehicle via an external interface before the vehicle performs the first diagnostic operation. After the diagnostic device connects to the vehicle, it communicates with the vehicle via a communication protocol configured within the device, and obtains the vehicle's basic information, which is then sent to the data server for verification and matching. Each diagnostic station is equipped with a corresponding identification device. Whenever a vehicle enters a diagnostic station, the identification device identifies the vehicle identification information of the vehicle and sends the vehicle identification information and the station information of the diagnostic station to the data server for verification and matching to obtain the matching relationship.

3. The vehicle diagnostic system according to claim 1, characterized in that, The diagnostic device pre-stores a protocol stack and preset services for invoking the protocol stack. The data server and the diagnostic device jointly complete all the diagnostic operations based on the diagnostic program, including: The data server sends and stores the diagnostic program to the diagnostic device, and controls the diagnostic device to execute the diagnostic program. During execution, the diagnostic device uses the preset service to call the protocol stack to complete data interaction with the vehicle and obtain the diagnostic results fed back by the vehicle. The diagnostic results are temporarily stored in the diagnostic device and sent to the data server when the diagnostic device is in communication connection with the data server.

4. The vehicle diagnostic system according to claim 1, characterized in that, The diagnostic device pre-stores a protocol stack and preset services for invoking the protocol stack. The diagnostic operation, performed jointly by the diagnostic program and the diagnostic device, includes: The data server executes the diagnostic program. During execution, the diagnostic device uses the preset service to call the protocol stack to complete the data interaction between the data server, the diagnostic device, and the vehicle, so that the data server can obtain and store the diagnostic results fed back by the vehicle.

5. The vehicle diagnostic system according to claim 1, characterized in that: in, The diagnostic operation is a program flashing operation. When the data server determines the diagnostic program corresponding to the diagnostic operation that the vehicle needs to perform at the diagnostic station based on the matching relationship, it also confirms the flashing file that needs to be loaded into the vehicle based on the station information, and verifies the accuracy of the flashing file based on the basic information. Before the data server completes the diagnostic operation based on the diagnostic program and the diagnostic device, the diagnostic device writes the flashing file to the vehicle.

6. The vehicle diagnostic system according to claim 1, characterized in that, Also includes: At least one handheld terminal, held by the diagnostic personnel, is communicatively connected to the data server. The handheld terminal is equipped with a barcode scanner and stores site information of the diagnostic site where the diagnostic personnel are located. The diagnostic device is provided with a device identifier containing the device identification information. When the diagnostic personnel scan the device identifier using the barcode scanner, the handheld terminal obtains the corresponding device identification information and sends this device identification information, along with the stored site information, to the data server for verification and matching. After the data server and the diagnostic device jointly complete the diagnostic operation, the data server sends the corresponding diagnostic results to the handheld terminal for confirmation by the diagnostic personnel according to the matching relationship.

7. The vehicle diagnostic system according to claim 6, characterized in that: in, The handheld terminal has an interactive interface, allowing the diagnostic personnel to select, adjust, and / or execute one or more diagnostic procedures. When the diagnostic operation results in a diagnostic failure, the data server sends the diagnostic failure message and the diagnostic result to the corresponding handheld terminal based on the site information, enabling the diagnostic personnel to perform troubleshooting operations and, after troubleshooting, select the diagnostic program to be executed through the handheld terminal. When the diagnostic personnel confirm the execution of the troubleshooting operation, the data server determines the corresponding diagnostic device based on the association between the terminal identification information and the device identification information, and runs the troubleshooting program, thereby completing the troubleshooting operation for the vehicle through the diagnostic device.

8. The vehicle diagnostic system according to claim 2, characterized in that: in, Whenever the data server successfully completes a diagnostic operation based on the diagnostic program and the diagnostic device, the data server predicts the next diagnostic operation that the vehicle needs to perform based on the matching relationship and the preset vehicle diagnostic process, determines the corresponding diagnostic program, and then sends the diagnostic program to the diagnostic device to replace the diagnostic program that has already completed the diagnosis.

9. The vehicle diagnostic system according to claim 1, characterized in that, The diagnostic device includes: The core board is equipped with a diagnostic module, a cache module, and a wireless module. An interface component adapted to the vehicle's external interface; An interactive component is provided to enable human-computer interaction between the diagnostic module and the diagnostic personnel. The power supply component, electrically connected to the interface component, the wireless module, and the diagnostic module, is used to provide power and perform power adaptation; and The expansion interface component is electrically connected to the diagnostic module. The diagnostic module is electrically connected to the vehicle via the interface component and is used to perform diagnostics on the vehicle. The caching module is electrically connected to the diagnostic module and is used to cache the data generated by the diagnostic module during the diagnostic process. The wireless module is electrically connected to the diagnostic module, and is used to connect the diagnostic module to the data server. The expansion interface component is any one or more of the following: USB interface, Type-C interface, flash memory interface, and Pogo Pin interface.

Images