Vehicle-mounted whole vehicle fault UDS diagnosis system and method

Abstract

The invention provides a vehicle-mounted whole vehicle fault UDS diagnosis system and method, and belongs to the technical field of vehicle diagnos.The system is characterized in that a whole vehicle fault UDS diagnosis module and a fault prompt module are both integrated in a seat area cabin controller and connected with the seat area cabin controller; the central gateway is connected with the seat area cabin controller and each function controller and is used for forwarding a whole vehicle communication message and a diagnosis message; the seat area cabin controller receives the communication signal of the central gateway and displays the whole vehicle operation information and the whole vehicle fault code information; the fault prompting module is used for collecting and processing the fault signals, received by the seat area cabin controller, of all the function controllers and carrying out fault prompting; and the whole vehicle fault UDS diagnosis module is used for diagnosing the whole vehicle fault in response to the operation of the driver, generating whole vehicle fault code information and sending the whole vehicle fault code information to the seat area cabin controller. According to the invention, a driver carries out fault diagnosis by himself / herself, timely and accurately confirms fault reasons, and fault processing efficiency is improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of vehicle diagnosis, and in particular relates to a vehicle-mounted UDS diagnosis system and method for whole vehicle faults. Background Art

[0002] UDS, short for Unified Diagnostic Services, is a standardized service protocol used for vehicle fault diagnosis in the automotive industry.

[0003] OBD is the abbreviation of On-Board Diagnostics, vehicle diagnosis.

[0004] With the development of automobile technology and the increase in the number of vehicles, the probability of vehicle failure problems has also increased. The traditional vehicle fault diagnosis method mainly relies on the driver's experience or after-sales service personnel to go to the site and connect the vehicle's OBD interface through the diagnostic tool for UDS diagnosis. However, this method has many shortcomings, especially when the driver lacks experience or is far away from the service station, the problem troubleshooting cycle will be very long, and the cause of the fault cannot be accurately confirmed, which brings inconvenience and loss to the driver.

[0005] A new generation of improved vehicle fault diagnosis methods has emerged, such as vehicle fault diagnosis through external local reading devices or 4G / 5G remote reading devices, but these methods still have certain limitations. First, external local reading devices require after-sales service personnel to operate, and the processing efficiency is low. Secondly, although the processing efficiency of 4G / 5G remote reading devices has been improved, they may face signal dropouts in remote areas. In addition, these methods cannot help drivers understand the problems of their vehicles in real time, and cannot alleviate the anxiety caused by vehicle failures while driving.

[0006] This is a shortcoming of the prior art. Therefore, in view of the above-mentioned defects in the prior art, it is very necessary to provide a vehicle-mounted UDS diagnosis system and method for vehicle faults. Summary of the invention

[0007] In view of the increasingly prominent problem of vehicle diagnosis, traditional diagnosis methods rely on driver experience or require service personnel to be on-site, with a long troubleshooting cycle and inability to accurately confirm faults. The new generation of external reading devices or remote diagnosis methods have low efficiency or unstable signals, and cannot show the defects of vehicle problems to the driver. The present invention provides an on-board vehicle fault UDS diagnosis system and method to solve the above technical problems.

[0008] In a first aspect, the present invention provides a vehicle-mounted UDS diagnostic system for vehicle faults, including a cockpit controller, a central gateway, a vehicle fault UDS diagnostic module, a fault prompt module, and several function controllers; The vehicle fault UDS diagnosis module and fault prompt module are integrated into the cockpit controller and connected to the cockpit controller; The central gateway is connected to the cockpit controller and each functional controller to forward vehicle communication messages and diagnostic messages; The cockpit controller receives the communication signal from the central gateway and displays the vehicle operation information and vehicle fault code information; The fault prompt module collects and processes the fault signals of each functional controller received by the cockpit controller and issues fault prompts; The vehicle fault UDS diagnostic module diagnoses the vehicle fault in response to the driver's operation, generates vehicle fault code information, and sends it to the cockpit controller. Furthermore, the fault prompt module also includes an indicator light; The fault prompting mode of the fault prompting module includes prompting the fault by lighting up the control indicator light, prompting the fault by prompting text, and prompting the fault by prompting sound; wherein the prompting text and prompting sound prompt the fault through the cockpit controller; The fault prompt module uses one or a combination of control indicator lights, prompt texts, and prompt sounds to distinguish different types of faults; The fault prompt module also records the fault log and operation log after the fault prompt occurs.

[0009] Furthermore, the cockpit controller is also provided with an external interface; External interface, used for external drivers or after-sales service personnel to read data.

[0010] Furthermore, the vehicle fault UDS diagnosis module includes: A diagnostic activation unit that responds to the driver's fault diagnostic registration using the cockpit controller's interface; A diagnostic switch unit, which uses the interface of the cockpit controller to respond to the driver's selection to turn the diagnostic function on or off; Diagnostic authentication unit, which controls the two-way security authentication between the cockpit controller and the central gateway during the vehicle fault code diagnosis process; A fault code diagnosis unit responds to a single function controller diagnosis request from an authorized driver or a diagnosis request from all function controllers of the vehicle, and performs fault code diagnosis according to pre-stored diagnosis instructions for all function controllers of the vehicle; The diagnostic display unit uses the cockpit controller's interface to display all fault codes and maintenance recommendations after diagnosis, and responds to driver-selected faults for freeze frame reading; The remote monitoring interface unit responds to the remote diagnostic device or platform to read fault codes and freeze frames.

[0011] In a second aspect, the present invention provides a diagnostic method of the vehicle-mounted vehicle fault UDS diagnostic system based on the first aspect, comprising the following steps: S1. After the vehicle enters the running state, the fault prompt module receives the fault signal forwarded by the cockpit controller and gives a fault prompt when a fault occurs; S2. After receiving the driver's login request, the vehicle fault UDS diagnosis module judges the diagnostic conditions, and when the diagnostic conditions are met, it starts the vehicle fault UDS diagnosis, generates diagnostic instructions, and then forwards the diagnostic instructions to the corresponding target function controllers through the cockpit controller and the central gateway, and receives the diagnostic results returned by the central gateway and the cockpit controller to each target function controller.

[0012] Furthermore, the specific steps of step S1 are as follows: S11. After the vehicle is powered on, it is determined that the vehicle has entered the running state; the vehicle running state includes the powered-on engine not started state and the powered-on engine started state; S12. The vehicle fault UDS diagnostic module receives the driver's activation request through the interface of the cockpit controller, obtains the registration request generated by the driver using unique personal information and the set personal password, and completes the activation of the diagnostic function after successful registration; S13. The vehicle fault UDS diagnostic module receives the driver's diagnostic function on and off through the cockpit controller interface; S14. The cockpit controller receives the operation information of each functional controller through the central gateway, generates a fault signal, and forwards it to the fault prompt module; S15. The fault prompt module receives and analyzes the fault signal to determine whether there is a fault prompt; If yes, go to step S16; If not, return to step S14; S16. The fault prompt module will analyze the fault prompt corresponding to the fault type and prompt the driver through indicator lights, prompt text or prompt sound according to the pre-set prompt method.

[0013] Furthermore, the specific steps of step S2 are as follows: S21. The vehicle fault UDS diagnostic module receives the driver's login request through the cockpit controller interface and performs identity authentication; If the identity authentication is passed, proceed to step S22; If the identity authentication fails, the system will prompt that the user or password is incorrect and the process ends; S22. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request, it makes a judgment on whether the diagnostic function is turned on and the diagnostic conditions are turned on, and reminds when the diagnostic function is not turned on or the diagnostic conditions are not met. When the diagnostic function is turned on and the diagnostic conditions are met, it proceeds to step S23; S23. The vehicle fault UDS diagnosis module parses the diagnosis request and identifies the diagnosis mode; When the diagnosis mode is single function controller diagnosis, go to step S24; When the diagnosis mode is the diagnosis of all functional controllers of the vehicle, the process proceeds to step S25; S24. The vehicle fault UDS diagnostic module uses the function controller as the target function controller and obtains the diagnostic instruction of the target controller, and then determines the routing address of the target controller by the functional addressing mode or the physical address addressing mode, forwards it to the central gateway through the cockpit controller for routing forwarding of the diagnostic instruction, and receives the diagnostic result returned by the target controller through the central gateway and the cockpit controller, and proceeds to step S28; S25. The vehicle fault UDS diagnostic module obtains the diagnostic instructions of each functional controller and locates each functional controller in the set order; S26. The vehicle fault UDS diagnostic module determines the routing address of the located functional controller by functional addressing or physical address addressing, forwards it to the central gateway via the cockpit controller, and then forwards the diagnostic instructions, and receives the diagnostic results returned by the located functional controller via the central gateway and cockpit controller; S27. The vehicle fault UDS diagnosis module determines whether the diagnosis is completed; If yes, go to step S28; If not, locate the next function controller and return to step S26; S28. The vehicle fault UDS diagnosis module displays the diagnostic code information in the diagnosis results through the interface of the cockpit controller.

[0014] Furthermore, the specific steps of step S22 are as follows: S221. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request through the cockpit controller interface, it determines whether the diagnostic function is turned on; If it is on, go to step S223; If not, go to step S222; S222. The vehicle fault UDS diagnostic module reminds the driver to turn on the diagnostic function through the cockpit controller interface, and returns to step S221; S223. The vehicle fault UDS diagnosis module determines whether the diagnosis conditions are met according to the vehicle operation information; If all diagnostic conditions are met, proceed to step S23; If there are unsatisfied diagnostic conditions, proceed to step S224; S224. The vehicle fault UDS diagnostic module prompts the unmet diagnostic conditions through the interface of the cockpit controller and ends.

[0015] Furthermore, the diagnostic conditions in step S223 include: The vehicle is powered on or started, the speed is 0 km / h, the battery is not in the charging state, the handbrake is pulled, and the vehicle gear is in P / N gear.

[0016] Furthermore, in the process of forwarding the diagnostic instruction and the diagnostic result between the cockpit controller and the central gateway in step S24 and step S26, a two-way security authentication between the cockpit controller and the central gateway is required, and the specific steps are as follows: SS1. After the cockpit controller sends a verification request to the central gateway, it receives the first random challenge string data generated by the central gateway, and generates a second random challenge string data based on the first random challenge string data; SS2. The cockpit controller uses the predefined key and the second random challenge string data to calculate the cockpit controller ownership certificate and send it to the central gateway; SS3. The central gateway verifies the ownership certificate of the cockpit controller; If the verification is successful, proceed to step SS4; If the verification fails, the authentication is considered to have failed and the process ends; SS4. The central controller uses the predefined key and the first random challenge string data to calculate the central gateway ownership certificate and sends it to the cockpit controller; SS5. The cockpit controller verifies the central gateway ownership certificate; If the verification is successful, proceed to step SS6; If the verification fails, the authentication is considered to have failed and the process ends; SS6. The cockpit controller sends diagnostic instructions of each functional controller to the central gateway in the diagnostic order; SS7. The central gateway verifies the diagnostic instructions of each functional controller; If the verification is successful, proceed to step SS8; If the diagnosis fails, the authentication is judged to have failed and the process ends; SS8. The central gateway routes and forwards the diagnostic instructions sent by the cockpit controller to the corresponding functional controller, receives the diagnostic results returned by the functional controller, and then routes and forwards the diagnostic results to the cockpit controller.

[0017] The beneficial effects of the present invention are: The vehicle-mounted UDS diagnosis system and method for whole vehicle faults provided by the present invention can use the cockpit controller to perform fault diagnosis when the vehicle prompts a fault, enabling the driver to perform fault diagnosis by himself, promptly and accurately confirm the cause of the fault, and improve the efficiency of fault handling.

[0018] It can be seen that compared with the prior art, the present invention has outstanding substantive features and significant progress, and the beneficial effects of its implementation are also obvious. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0020] Figure 1 It is a schematic diagram of the vehicle-mounted UDS diagnosis system for vehicle faults of the present invention.

[0021] Figure 2 It is a flow chart of an embodiment of the vehicle-mounted UDS diagnosis method for vehicle faults of the present invention.

[0022] Figure 3 It is a flow chart of another embodiment of the vehicle-mounted UDS diagnosis method for vehicle faults of the present invention. DETAILED DESCRIPTION

[0023] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0024] See also Figure 1 The figure shows a specific implementation of a vehicle-mounted vehicle fault UDS diagnostic system, including a cockpit controller, a central gateway, a vehicle fault UDS diagnostic module, a fault prompt module and several functional controllers; The vehicle fault UDS diagnosis module and fault prompt module are integrated into the cockpit controller and connected to the cockpit controller; The central gateway is connected to the cockpit controller and each functional controller to forward vehicle communication messages and diagnostic messages; The cockpit controller receives the communication signal from the central gateway and displays the vehicle operation information and vehicle fault code information; The fault prompt module collects and processes the fault signals of each functional controller received by the cockpit controller and issues fault prompts; The vehicle fault UDS diagnostic module diagnoses the vehicle fault in response to the driver's operation, generates vehicle fault code information, and sends it to the cockpit controller.

[0025] It should be noted that the cockpit controller is the original controller with audio and video entertainment controller and vehicle information display. The vehicle diagnostic function is integrated here, and the vehicle diagnostic function can be realized without adding an additional controller; The vehicle fault UDS diagnosis module uses the interface of the cockpit controller to assist the driver in operating fault diagnosis, making it possible for the driver to diagnose and handle vehicle faults according to their own needs, thereby improving the transparency of vehicle status.

[0026] In this embodiment, the fault prompt module also includes an indicator light; The fault prompting mode of the fault prompting module includes prompting the fault by lighting up the control indicator light, prompting the fault by prompting text, and prompting the fault by prompting sound; wherein the prompting text and prompting sound prompt the fault through the cockpit controller; The fault prompt module uses one or a combination of control indicator lights, prompt texts, and prompt sounds to distinguish different types of faults; The fault prompt module also records the fault log and operation log after the fault prompt occurs; It should be noted that the fault prompt module will uniformly process and display the faults of the entire vehicle, and save the logs after the fault occurs, which is convenient for local or remote retrieval; The cockpit controller is also provided with an external interface; the external interface includes but is not limited to USB, Type C, Bluetooth, 4G and other methods. The driver or after-sales service personnel can copy or read data for analysis through the external interface. In addition, the driver can also delete the log data; External interface, used for external drivers or after-sales service personnel to read data; The vehicle fault UDS diagnosis module includes: A diagnostic activation unit that responds to the driver's fault diagnostic registration using the cockpit controller's interface; A diagnostic switch unit, which uses the interface of the cockpit controller to respond to the driver's selection to turn the diagnostic function on or off; It should be noted that only when the diagnostic function of the vehicle fault UDS diagnostic module is activated and turned on, the module is allowed to be used for fault diagnosis, and based on network security needs, the driver can decide to turn this function on / off; Diagnostic authentication unit, which controls the two-way security authentication between the cockpit controller and the central gateway during the vehicle fault code diagnosis process; A fault code diagnosis unit responds to a single function controller diagnosis request from an authorized driver or a diagnosis request from all function controllers of the vehicle, and performs fault code diagnosis according to pre-stored diagnosis instructions for all function controllers of the vehicle; The diagnostic display unit uses the cockpit controller's interface to display all fault codes and maintenance recommendations after diagnosis, and responds to driver-selected faults for freeze frame reading; It should be noted that the diagnostic display unit will display the fault codes read and parsed on the cockpit display interface, which includes the fault codes and fault repair suggestions, so that the driver can clearly understand the vehicle problem; A remote monitoring interface unit, which responds to the remote diagnostic device or platform to read fault codes and freeze frames; What needs life is that the freeze frame corresponding to the fault code can be read through the remote monitoring interface unit and stored in a specific area to facilitate problem analysis and resolution.

[0027] The following is an embodiment of the diagnostic method of the on-board whole vehicle fault UDS diagnostic system provided by the embodiment of the present disclosure. The method and the on-board whole vehicle fault UDS diagnostic system of the above-mentioned embodiments belong to the same inventive concept. For details not fully described in the embodiment of the diagnostic method of the on-board whole vehicle fault UDS diagnostic system, please refer to the embodiment of the above-mentioned on-board whole vehicle fault UDS diagnostic system.

[0028] like Figure 2 As shown, the method comprises the following steps: S1. After the vehicle enters the running state, the fault prompt module receives the fault signal forwarded by the cockpit controller and gives a fault prompt when a fault occurs; S2. After receiving the driver's login request, the vehicle fault UDS diagnosis module judges the diagnostic conditions, and when the diagnostic conditions are met, it starts the vehicle fault UDS diagnosis, generates diagnostic instructions, and then forwards the diagnostic instructions to the corresponding target function controllers through the cockpit controller and the central gateway, and receives the diagnostic results returned by the central gateway and the cockpit controller to each target function controller.

[0029] In this embodiment, Figure 3 As shown, the specific steps of step S1 are as follows: S11. After the vehicle is powered on, it is determined that the vehicle has entered the running state; the vehicle running state includes the powered-on engine not started state and the powered-on engine started state; S12. The vehicle fault UDS diagnostic module receives the driver's activation request through the interface of the cockpit controller, obtains the registration request generated by the driver using unique personal information and the set personal password, and completes the activation of the diagnostic function after successful registration; It should be noted that the driver registration authorizes the driver or after-sales service personnel to use the vehicle fault UDS diagnosis module to diagnose vehicle faults, thereby preventing unauthorized access; S13. The vehicle fault UDS diagnostic module receives the driver's diagnostic function on and off through the cockpit controller interface; S14. The cockpit controller receives the operation information of each functional controller through the central gateway, generates a fault signal, and forwards it to the fault prompt module; S15. The fault prompt module receives and analyzes the fault signal to determine whether there is a fault prompt; If yes, go to step S16; If not, return to step S14; S16. The fault prompt module will analyze the fault prompt corresponding to the fault type and prompt the driver through an indicator light, prompt text or prompt sound according to the pre-set prompt method; The specific steps of step S2 are as follows: S21. The vehicle fault UDS diagnostic module receives the driver's login request through the cockpit controller interface and performs identity authentication; If the identity authentication is passed, proceed to step S22; If the identity authentication fails, the system will prompt that the user or password is incorrect and the process ends; S22. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request, it makes a judgment on whether the diagnostic function is turned on and the diagnostic conditions are turned on, and reminds when the diagnostic function is not turned on or the diagnostic conditions are not met. When the diagnostic function is turned on and the diagnostic conditions are met, it proceeds to step S23; The specific steps of step S22 are as follows: S221. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request through the cockpit controller interface, it determines whether the diagnostic function is turned on; If it is on, go to step S223; If not, go to step S222; S222. The vehicle fault UDS diagnostic module reminds the driver to turn on the diagnostic function through the cockpit controller interface, and returns to step S221; S223. The vehicle fault UDS diagnosis module determines whether the diagnosis conditions are met according to the vehicle operation information; If all diagnostic conditions are met, proceed to step S23; If there are unsatisfied diagnostic conditions, proceed to step S224; Diagnostic conditions include: the vehicle is powered on or started, the vehicle speed is 0 km / h, the battery is not powered, the handbrake is pulled, and the vehicle gear is P / N gear; S224. The vehicle fault UDS diagnostic module prompts the unsatisfied diagnostic conditions through the cockpit controller interface, and ends; S23. The vehicle fault UDS diagnosis module parses the diagnosis request and identifies the diagnosis mode; When the diagnosis mode is single function controller diagnosis, go to step S24; When the diagnosis mode is the diagnosis of all functional controllers of the vehicle, the process proceeds to step S25; S24. The vehicle fault UDS diagnostic module uses the function controller as the target function controller and obtains the diagnostic instruction of the target controller, and then determines the routing address of the target controller by the functional addressing mode or the physical address addressing mode, forwards it to the central gateway through the cockpit controller for routing forwarding of the diagnostic instruction, and receives the diagnostic result returned by the target controller through the central gateway and the cockpit controller, and proceeds to step S28; S25. The vehicle fault UDS diagnostic module obtains the diagnostic instructions of each functional controller and locates each functional controller in the set order; S26. The vehicle fault UDS diagnostic module determines the routing address of the located functional controller by functional addressing or physical address addressing, forwards it to the central gateway via the cockpit controller, and then forwards the diagnostic instructions, and receives the diagnostic results returned by the located functional controller via the central gateway and cockpit controller; S27. The vehicle fault UDS diagnosis module determines whether the diagnosis is completed; If yes, go to step S28; If not, locate the next function controller and return to step S26; S28. The vehicle fault UDS diagnosis module displays the diagnostic code information in the diagnosis results through the interface of the cockpit controller.

[0030] In some embodiments, during the process of forwarding diagnostic instructions and forwarding diagnostic results between the cockpit controller and the central gateway in step S24 and step S26, two-way security authentication between the cockpit controller and the central gateway is required, and the specific steps are as follows: SS1. After the cockpit controller sends a verification request to the central gateway, it receives the first random challenge string data generated by the central gateway, and generates a second random challenge string data based on the first random challenge string data; SS2. The cockpit controller uses the predefined key and the second random challenge string data to calculate the cockpit controller ownership certificate and send it to the central gateway; SS3. The central gateway verifies the ownership certificate of the cockpit controller; If the verification is successful, proceed to step SS4; If the verification fails, the authentication is considered to have failed and the process ends; SS4. The central controller uses the predefined key and the first random challenge string data to calculate the central gateway ownership certificate and sends it to the cockpit controller; SS5. The cockpit controller verifies the central gateway ownership certificate; If the verification is successful, proceed to step SS6; If the verification fails, the authentication is considered to have failed and the process ends; SS6. The cockpit controller sends diagnostic instructions of each functional controller to the central gateway in the diagnostic order; SS7. The central gateway verifies the diagnostic instructions of each functional controller; If the verification is successful, proceed to step SS8; If the diagnosis fails, the authentication is judged to have failed and the process ends; SS8. The central gateway routes and forwards the diagnostic instructions sent by the cockpit controller to the corresponding functional controller, receives the diagnostic results returned by the functional controller, and then routes and forwards the diagnostic results to the cockpit controller; It should be noted that a two-way authentication process is used to implement identity verification of the cockpit domain controller and the central gateway, thereby ensuring that the central gateway will execute diagnostic instructions only after obtaining access rights and verifying that the diagnostic instructions are normal.

[0031] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0032] Although the present invention has been described in detail with reference to the accompanying drawings and in combination with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, a person of ordinary skill in the art may make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions shall be within the scope of the present invention. Any person of ordinary skill in the art may easily think of changes or substitutions within the technical scope disclosed by the present invention, and these shall be within the scope of protection of the present invention.

Claims

1. A vehicle-mounted UDS diagnostic system for vehicle faults, characterized in that: Including cockpit controller, central gateway, vehicle fault UDS diagnosis module, fault prompt module and several functional controllers; The vehicle fault UDS diagnosis module and fault prompt module are integrated into the cockpit controller and connected to the cockpit controller; The central gateway is connected to the cockpit controller and each functional controller to forward vehicle communication messages and diagnostic messages; The cockpit controller receives the communication signal from the central gateway and displays the vehicle operation information and vehicle fault code information; The fault prompt module collects and processes the fault signals of each functional controller received by the cockpit controller and issues fault prompts; The vehicle fault UDS diagnostic module diagnoses the vehicle fault in response to the driver's operation, generates vehicle fault code information, and sends it to the cockpit controller.

2. The vehicle fault UDS diagnostic system as claimed in claim 1, characterized in that: The fault prompt module also includes an indicator light; The fault prompting mode of the fault prompting module includes prompting the fault by lighting up the control indicator light, prompting the fault by prompting text, and prompting the fault by prompting sound; wherein the prompting text and prompting sound prompt the fault through the cockpit controller; The fault prompt module uses one or a combination of control indicator lights, prompt texts, and prompt sounds to distinguish different types of faults; The fault prompt module also records the fault log and operation log after the fault prompt occurs.

3. The vehicle-mounted vehicle fault UDS diagnostic system as claimed in claim 2, characterized in that: The cockpit controller is also provided with an external interface; External interface, used for external drivers or after-sales service personnel to read data.

4. The vehicle-mounted vehicle fault UDS diagnostic system as claimed in claim 1, characterized in that: The vehicle fault UDS diagnosis module includes: A diagnostic activation unit that responds to the driver's fault diagnostic registration using the cockpit controller's interface; A diagnostic switch unit, which uses the interface of the cockpit controller to respond to the driver's selection to turn the diagnostic function on or off; Diagnostic authentication unit, which controls the two-way security authentication between the cockpit controller and the central gateway during the vehicle fault code diagnosis process; A fault code diagnosis unit responds to a single function controller diagnosis request from an authorized driver or a diagnosis request from all function controllers of the vehicle, and performs fault code diagnosis according to pre-stored diagnosis instructions for all function controllers of the vehicle; The diagnostic display unit uses the cockpit controller's interface to display all fault codes and maintenance recommendations after diagnosis, and responds to driver-selected faults for freeze frame reading; The remote monitoring interface unit responds to the remote diagnostic device or platform to read fault codes and freeze frames.

5. A diagnostic method for a vehicle fault UDS diagnostic system based on any one of claims 1 to 4, characterized in that: The steps include: S1. After the vehicle enters the running state, the fault prompt module receives the fault signal forwarded by the cockpit controller and gives a fault prompt when a fault occurs; S2. After receiving the driver's login request, the vehicle fault UDS diagnosis module judges the diagnostic conditions, and when the diagnostic conditions are met, it starts the vehicle fault UDS diagnosis, generates diagnostic instructions, and then forwards the diagnostic instructions to the corresponding target function controllers through the cockpit controller and the central gateway, and receives the diagnostic results returned by the central gateway and the cockpit controller to each target function controller.

6. The diagnostic method according to claim 5, characterized in that The specific steps of step S1 are as follows: S11. After the vehicle is powered on, it is determined that the vehicle has entered the running state; the vehicle running state includes the powered-on engine not started state and the powered-on engine started state; S12. The vehicle fault UDS diagnostic module receives the driver's activation request through the interface of the cockpit controller, obtains the registration request generated by the driver using unique personal information and the set personal password, and completes the activation of the diagnostic function after successful registration; S13. The vehicle fault UDS diagnostic module receives the driver's diagnostic function on and off through the cockpit controller interface; S14. The cockpit controller receives the operation information of each functional controller through the central gateway, generates a fault signal, and forwards it to the fault prompt module; S15. The fault prompt module receives and analyzes the fault signal to determine whether there is a fault prompt; If yes, go to step S16; If not, return to step S14; S16. The fault prompt module will analyze the fault prompt corresponding to the fault type and prompt the driver through indicator lights, prompt text or prompt sound according to the pre-set prompt method.

7. The diagnostic method according to claim 5, characterized in that The specific steps of step S2 are as follows: S21. The vehicle fault UDS diagnostic module receives the driver's login request through the cockpit controller interface and performs identity authentication; If the identity authentication is passed, proceed to step S22; If the identity authentication fails, the system will prompt that the user or password is incorrect and the process ends; S22. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request, it makes a judgment on whether the diagnostic function is turned on and the diagnostic conditions are turned on, and reminds when the diagnostic function is not turned on or the diagnostic conditions are not met. When the diagnostic function is turned on and the diagnostic conditions are met, it proceeds to step S23; S23. The vehicle fault UDS diagnosis module parses the diagnosis request and identifies the diagnosis mode; When the diagnosis mode is single function controller diagnosis, go to step S24; When the diagnosis mode is the diagnosis of all functional controllers of the vehicle, the process proceeds to step S25; S24. The vehicle fault UDS diagnostic module uses the function controller as the target function controller and obtains the diagnostic instruction of the target controller, and then determines the routing address of the target controller by the functional addressing mode or the physical address addressing mode, forwards it to the central gateway through the cockpit controller for routing forwarding of the diagnostic instruction, and receives the diagnostic result returned by the target controller through the central gateway and the cockpit controller, and proceeds to step S28; S25. The vehicle fault UDS diagnostic module obtains the diagnostic instructions of each functional controller and locates each functional controller in the set order; S26. The vehicle fault UDS diagnostic module determines the routing address of the located functional controller by functional addressing or physical address addressing, forwards it to the central gateway via the cockpit controller, and then forwards the diagnostic instructions, and receives the diagnostic results returned by the located functional controller via the central gateway and cockpit controller; S27. The vehicle fault UDS diagnosis module determines whether the diagnosis is completed; If yes, go to step S28; If not, locate the next function controller and return to step S26; S28. The vehicle fault UDS diagnosis module displays the diagnostic code information in the diagnosis results through the interface of the cockpit controller.

8. The diagnostic method according to claim 7, characterized in that The specific steps of step S22 are as follows: S221. After the vehicle fault UDS diagnostic module receives the driver's diagnostic request through the cockpit controller interface, it determines whether the diagnostic function is turned on; If it is on, go to step S223; If not, go to step S222; S222. The vehicle fault UDS diagnostic module reminds the driver to turn on the diagnostic function through the cockpit controller interface, and returns to step S221; S223. The vehicle fault UDS diagnosis module determines whether the diagnosis conditions are met according to the vehicle operation information; If all diagnostic conditions are met, proceed to step S23; If there are unsatisfied diagnostic conditions, proceed to step S224; S224. The vehicle fault UDS diagnostic module prompts the unmet diagnostic conditions through the interface of the cockpit controller and ends.

9. The diagnostic method according to claim 8, characterized in that The diagnostic conditions in step S223 include: The vehicle is powered on or started, the speed is 0 km / h, the battery is not in the charging state, the handbrake is pulled, and the vehicle gear is in P / N gear.

10. The diagnostic method according to claim 7, characterized in that: In the process of forwarding the diagnostic instruction and the diagnostic result between the cockpit controller and the central gateway in step S24 and step S26, a two-way security authentication between the cockpit controller and the central gateway is required. The specific steps are as follows: SS1. After the cockpit controller sends a verification request to the central gateway, it receives the first random challenge string data generated by the central gateway, and generates a second random challenge string data based on the first random challenge string data; SS2. The cockpit controller uses the predefined key and the second random challenge string data to calculate the cockpit controller ownership certificate and send it to the central gateway; SS3. The central gateway verifies the ownership certificate of the cockpit controller; If the verification is successful, proceed to step SS4; If the verification fails, the authentication is considered to have failed and the process ends; SS4. The central controller uses the predefined key and the first random challenge string data to calculate the central gateway ownership certificate and sends it to the cockpit controller; SS5. The cockpit controller verifies the central gateway ownership certificate; If the verification is successful, proceed to step SS6; If the verification fails, the authentication is considered to have failed and the process ends; SS6. The cockpit controller sends diagnostic instructions of each functional controller to the central gateway in the diagnostic order; SS7. The central gateway verifies the diagnostic instructions of each functional controller; If the verification is successful, proceed to step SS8; If the diagnosis fails, the authentication is judged to have failed and the process ends; SS8. The central gateway routes and forwards the diagnostic instructions sent by the cockpit controller to the corresponding functional controller, receives the diagnostic results returned by the functional controller, and then routes and forwards the diagnostic results to the cockpit controller.

Images