Automobile diagnostic method, device, electronic device and storage medium
By sending a read request according to the controller's diagnostic request address in the car diagnostic instrument, parsing the controller's response data frame, and displaying the supplier and function item interface, the problem of complex interface of existing car diagnostic software is solved and the diagnostic efficiency is improved.
Patent Information
- Application Number
- CN202411803841.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-10
- Publication Date
- 2025-10-03
- Estimated Expiration
- 2044-12-10
AI Technical Summary
The display interface of existing automotive diagnostic software is too complicated, making it difficult for operators to quickly select the required function items, affecting diagnostic efficiency.
By sending a read request for data content to the controller according to its diagnostic request address, the controller generates a response data frame. The diagnostic instrument monitors the diagnostic response address on the CAN bus and parses the response data frame to display the supplier and function item interface, simplifying the operation process.
It simplifies the process of manually selecting the model year and supplier, directly enters the function item interface, improves the efficiency of vehicle diagnosis, and avoids erroneous operations caused by complex information.
Smart Images

Figure CN119758950B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of automobile diagnosis, and in particular to an automobile diagnosis method, device, electronic equipment and storage medium. Background Art
[0002] In the traditional automotive repair industry, technicians often rely on a variety of diagnostic tools to diagnose electronic, electrical, and mechanical faults in vehicles. For example, oscilloscopes are suitable for analyzing dynamic signals and detecting transient faults, while multimeters are suitable for static measurements and basic circuit testing. With the increasing electronicization and intelligence of vehicles, fault diagnosis technology is constantly evolving. A large number of control units and sensors working together have brought new tools and approaches to troubleshooting. Each vehicle is typically equipped with multiple electronic control units, which not only perform various functions but also have self-diagnostic capabilities. When the system detects an anomaly, it generates a corresponding fault code. By connecting to the on-board diagnostic interface, maintenance personnel can read these codes and quickly identify the problem.
[0003] However, with the increasing complexity of vehicle electronic systems and the increasing number of control units, maintenance work has become more reliant on advanced diagnostic equipment and software tools. This has led to continuous updates and iterations in diagnostic software development, allowing for optimization of features and interface displays during software development. As diagnostic software development plans continue to refine their catalogs at all levels, the display interface of current diagnostic software is becoming increasingly complex, leading operators to frequently make incorrect selections and be unable to select the desired function, hindering the vehicle diagnostic process. Summary of the Invention
[0004] The problem solved by the present invention is how to simplify the display interface of the diagnostic software to improve the efficiency of automobile diagnosis.
[0005] To solve the above problems, the present invention provides an automobile diagnosis method, device, electronic device and storage medium.
[0006] In a first aspect, the present invention provides a vehicle diagnostic method, comprising:
[0007] When a controller is selected for diagnosis, a read request for data content is sent to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller;
[0008] acquiring the data content from the controller according to the diagnostic response address of the controller and the read request;
[0009] The corresponding supplier and the function item interface corresponding to the supplier are displayed according to the data content to complete the diagnosis of the controller.
[0010] Optionally, the read request includes an identifier corresponding to the data content, and sending the read request for the data content to the corresponding controller according to the diagnosis request address of the controller includes:
[0011] Constructing a request data frame according to the diagnosis request address and the identifier;
[0012] The request data frame is sent to the corresponding controller according to the diagnosis request address.
[0013] Optionally, the read request includes a read service code and an identifier corresponding to the data content, and sending the read request for the data content to the corresponding controller according to the diagnostic request address of the controller includes:
[0014] constructing a request data frame according to the diagnosis request address, the read service code and the identifier;
[0015] The request data frame is sent to the corresponding controller according to the diagnosis request address.
[0016] Optionally, acquiring the data content from the controller according to the diagnostic response address of the controller and the read request includes:
[0017] Receive a response data frame fed back by the controller, and obtain the data content according to the response data frame, wherein the response data frame is constructed according to the diagnostic response address, the identifier and the data content after the controller extracts the corresponding data content from the memory according to the identifier.
[0018] Optionally, the response data frame further includes a success response code, and the success response code is used to respond to the request service corresponding to the read service code.
[0019] Optionally, the read request includes a plurality of identifiers corresponding to the data content, and the plurality of identifiers are configured to correspond to a plurality of data contents stored in the controller, respectively.
[0020] Optionally, the diagnosis response address is determined according to the diagnosis request address and a preset rule.
[0021] In a second aspect, the present invention provides an automobile diagnostic device, comprising:
[0022] A first module is configured to, when a controller is selected for diagnosis, send a read request for data content to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to a supplier of the controller;
[0023] A second module is configured to obtain the data content from the controller according to the diagnostic response address of the controller and the read request;
[0024] The third module is used to display the corresponding supplier and the function item interface corresponding to the supplier according to the data content to complete the diagnosis of the controller.
[0025] In a third aspect, the present invention provides an electronic device comprising a memory and a processor;
[0026] The memory is used to store computer programs;
[0027] The processor is configured to implement the automobile diagnostic method as described in the first aspect when executing the computer program.
[0028] In a fourth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the automobile diagnostic method as described in the first aspect is implemented.
[0029] The beneficial effect of the automobile diagnostic method of the present invention is that when the diagnostic instrument diagnoses the controller, it can send a read request for the data content to the corresponding controller according to the diagnostic request address of the controller, and the controller can generate a corresponding diagnostic response address according to the diagnostic request address, and generate a response data frame after extracting the data content from the memory according to the read request. The diagnostic instrument can monitor the diagnostic response address on the CAN bus, so that it can receive the response data frame sent by the controller, parse the response data frame, and extract the data content therefrom, so that the supplier corresponding to the data content and the function item interface corresponding to the supplier can be displayed on the display interface, so that when the operator operates the diagnostic instrument, there is no need to click in sequence according to the five steps in the existing mainstream solution, but only needs to click on the controller and the function item, cancel the year information, and simplify the process of manually selecting the model year, and can automatically obtain the supplier information and enter the corresponding function item interface, replacing the process of manually selecting the supplier, preventing the operator from being unable to select the desired function item when faced with increasingly complex information, thereby improving the efficiency of automobile diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Figure 1 1 is a flow chart of a vehicle diagnostic method according to an embodiment of the present invention;
[0031] Figure 2 This is a schematic diagram showing the interface directory of mainstream solutions;
[0032] Figure 3 This is a schematic diagram of an interface directory display according to an embodiment of the present invention;
[0033] Figure 4 Schematic diagram of the process of sending a read request for data content to the controller according to an embodiment of the present invention Figure 1 ;
[0034] Figure 5 Schematic diagram of the process of sending a read request for data content to the controller according to an embodiment of the present invention Figure 2 ;
[0035] Figure 6 A system architecture diagram of an automobile diagnostic device according to an embodiment of the present invention;
[0036] Figure 7 2 is a system architecture diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0037] To make the above-mentioned objects, features, and advantages of the present invention more clearly understood, specific embodiments of the present invention are described in detail below with reference to the accompanying drawings. Although certain embodiments of the present invention are shown in the accompanying drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as being limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the drawings and embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.
[0038] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.
[0039] The term "including" and its variations used in this document are open inclusions, that is, "including but not limited to"; the term "based on" means "based at least in part on"; the term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments"; the term "optionally" means "optional embodiments". The relevant definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc. mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0040] It should be noted that the modifications of "one" and "multiple" mentioned in the present invention are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0041] The names of the messages or information exchanged between multiple devices in the embodiments of the present invention are only used for illustrative purposes and are not used to limit the scope of these messages or information.
[0042] like Figure 1 As shown, an embodiment of the present invention provides an automobile diagnostic method, comprising:
[0043] S100: When a controller is selected for diagnosis, a read request for data content is sent to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller.
[0044] Specifically, after the operator selects a controller on the display interface of the diagnostic instrument, a read request for data content is sent to the corresponding controller according to the diagnostic request address of the controller, and the supplier of the corresponding controller can be determined according to the data content.
[0045] Among them, the diagnostic request address refers to the address information used by the diagnostic instrument to send information to the controller. Different controllers have different request addresses, which are generally three digits. For example, the request address of the controller corresponding to the engine is 7E0.
[0046] Among them, the mainstream diagnostic software development process includes: (1) formulating development requirements: determining the diagnostic functions that the software needs to support. Functional development requirements include reading fault codes, reading data streams, special routines, and flashing functions, etc., and interface display requirements correspond to the optimization content related to the display interface of the diagnostic software; (2) Software development: The development team develops according to the input of the system engineer and converts the requirements into actual functions. This stage involves coding, architecture design and module integration; (3) Software testing: Test engineers perform software function testing on actual vehicles. The testing stage ensures that the developed software can run stably and meet the functional and performance requirements defined in the requirements; (4) Software release: After completing development and testing, the software will enter the release stage. This stage involves bringing the software to market and ensuring its stability and maintainability. This embodiment mainly optimizes the interface display requirements.
[0047] Among them, the interface of the mainstream solution is shown as follows Figure 2 As shown, clicking the directory is divided into 5 steps: model → year → controller → supplier → function item. Generally speaking, this operation is more intuitive and easy for operators to use. However, with the increase in modified cars and the continuous reduction in vehicle costs, there will be more and more year and supplier interface buttons. Operators may easily make the wrong choice and fail to select the desired function item. Based on the problems existing in the mainstream solution, this embodiment is designed as follows Figure 3The interface directory shown is divided into two steps when you click on the directory: controller → function item. The year information is cancelled, which simplifies the process of manually selecting the model year. It can also automatically obtain supplier information and enter the corresponding function item interface, replacing the process of manually selecting suppliers. This prevents operators from being unable to select the desired function item when faced with increasingly complex information, thereby improving the efficiency of vehicle diagnosis.
[0048] S200: Acquire the data content from the controller according to the diagnosis response address of the controller and the read request.
[0049] Specifically, after receiving a read request, the controller feeds back the corresponding data content to the diagnostic instrument. For example, the controller generates a corresponding diagnostic response address based on the diagnostic request address, and generates a response data frame after extracting the data content from the memory based on the read request. After sending a read request, the diagnostic instrument monitors the response address on the CAN bus, so that it can receive the response data frame sent by the controller. After parsing the response data frame, it can extract the data content from it.
[0050] Among them, the diagnostic response address refers to the address information used by the controller to reply to the diagnostic instrument. Different controllers have different diagnostic response addresses, which are generally three digits. For example, the response address of the controller corresponding to the engine is 7E8, that is, the diagnostic response address = diagnostic request address + 8.
[0051] S300: Displaying the corresponding supplier and the function item interface corresponding to the supplier according to the data content to complete the diagnosis of the controller.
[0052] Specifically, after receiving the response data frame, the diagnostic instrument parses the data content from it, so that the supplier corresponding to the data content and the function item interface corresponding to the supplier can be displayed on the display interface. Figure 3 As shown, for example, when the data content is 01, the corresponding supplier is supplier 1, and the corresponding function items include reading fault codes, reading data streams, special routines, and flashing functions, so that various diagnostic contents of the controller can be completed quickly.
[0053] In this embodiment, when the diagnostic instrument diagnoses the controller, it can send a read request for the data content to the corresponding controller according to the diagnostic request address of the controller. The controller can generate a corresponding diagnostic response address according to the diagnostic request address, and generate a response data frame after extracting the data content from the memory according to the read request. The diagnostic instrument can monitor the diagnostic response address on the CAN bus (Controller Area Network), so as to receive the response data frame sent by the controller, parse the response data frame, and extract the data content therefrom, so as to display the supplier corresponding to the data content and the function item interface corresponding to the supplier on the display interface. When operating the diagnostic instrument, the operator does not need to click in sequence according to the five steps in the existing mainstream solution, but only needs to click on the controller and the function item, cancel the year information, and simplify the process of manually selecting the model year. The diagnostic instrument can also automatically obtain the supplier information and enter the corresponding function item interface, replacing the process of manually selecting the supplier, preventing the operator from being unable to select the desired function item when faced with increasingly complex information, thereby improving the efficiency of automobile diagnosis.
[0054] Optionally, the read request includes an identifier corresponding to the data content, and sending the read request for the data content to the corresponding controller according to the diagnosis request address of the controller includes:
[0055] S110: Construct a request data frame according to the diagnosis request address and the identifier.
[0056] Specifically, combined Figure 4 As shown, taking the diagnosis request address as 7E0 and the identifier as F1A9 as an example, the constructed request data frame is [7E0]F1A9.
[0057] The identifier (or data stream ID) is typically determined by negotiation between the OEM and each controller supplier. It serves as a data channel for identifying specific information. The identifier allows the reading of a numerical value representing the supplier's information, namely, the data content (hereinafter referred to as the M value). The controller supplier writes the previously assigned value into the controller's memory in the controller it manufactures, ensuring that each controller can store its corresponding identification information. The OEM integrates the supplier information of all controllers and their corresponding M values into a symmetry table and sends this symmetry table to the diagnostic instrument supplier to ensure that the diagnostic instrument can understand the supplier or controller type represented by the value returned by each controller. An example of a symmetry table is as follows:
[0058] Peer Table
[0059] Controller Type Supplier Information M value Engine controller Supplier 1 01 Transmission controller Supplier 2 02
[0060] For the same controller, the M value of different suppliers is different; for different controllers, the M value of the same supplier can be the same or different.
[0061] S120: Send the request data frame to the corresponding controller according to the diagnosis request address.
[0062] Specifically, combined Figure 4 As shown, after generating the request data frame, the diagnostic instrument sends the request data frame to the corresponding controller according to the diagnostic request address. For example, if the request address of the engine corresponding controller is 7E0, the corresponding request data frame [7E0]F1A9 is sent to 7E0.
[0063] In this optional embodiment, when constructing a request data frame, the diagnostic request address and identifier are combined, which can effectively communicate with the controller and ensure that the request is conveyed accurately and reliably. Each controller receives the message through an independent request address and will not be confused with the communication of other controllers, ensuring the accuracy and security of the data request to help maintenance personnel quickly obtain key information and shorten the diagnosis time; when using the identifier to read the specified data content, only a small number of bytes of request data frames and response messages need to be transmitted, which reduces the bandwidth consumption of the CAN bus and improves the communication efficiency of the bus.
[0064] Optionally, the read request further includes a read service code and an identifier corresponding to the data content, and the sending of the read request for the data content to the corresponding controller according to the diagnostic request address of the controller further includes:
[0065] S130: Construct a request data frame according to the diagnosis request address, the read service code and the identifier.
[0066] Specifically, combined Figure 5 As shown, the diagnostic instrument sends a diagnostic request to the controller and uses the diagnostic service 22 (i.e., the read service code) in the ISO-14229 standard to read the data in the controller. The diagnostic request address, read service code and identifier can construct a request data frame. For example, the request data frame constructed by the diagnostic request address 7E0, the read service code 22 and the identifier F1A9 is [7E0]22F1A9.
[0067] Among them, diagnostic service 22 means "read data by identifier", which allows the diagnostic instrument to read specific data items inside the ECU (Electronic Control Unit). Through diagnostic service 22, the diagnostic instrument can request the ECU to provide data corresponding to a specific identifier. The identifier is usually used to mark specific parameters or information in the controller, such as supplier information, hardware / software version number, vehicle mileage, serial number, and calibration parameters.
[0068] S140: Send the request data frame to the corresponding controller according to the diagnosis request address.
[0069] Specifically, combined Figure 5 As shown, after generating the request data frame, the diagnostic instrument sends the request data frame to the corresponding controller according to the diagnostic request address. For example, if the request address of the engine corresponding controller is 7E0, the corresponding request data frame [7E0]22F1A9 is sent to 7E0.
[0070] In this optional embodiment, the service code is read to ensure that the diagnostic instrument only reads the specific data required, rather than accessing the entire data set, thereby avoiding redundant transmission and improving system performance.
[0071] Optionally, acquiring the data content from the controller according to the diagnostic response address of the controller and the read request includes:
[0072] Receive a response data frame fed back by the controller, and obtain the data content according to the response data frame, wherein the response data frame is constructed according to the diagnostic response address, the identifier and the data content after the controller extracts the corresponding data content from the memory according to the identifier.
[0073] Specifically, after the controller extracts the corresponding data content from the memory according to the identifier, it constructs a response data frame according to the diagnostic response address, identifier and data content. For example, the response data frame constructed by the diagnostic response address 7E8, identifier F1A9 and data content 01 is [7E8]F1A9 01; wherein, the diagnostic response address 7E8 indicates a response to the diagnostic request address 7E0, the identifier F1A9 is consistent with the aforementioned request data frame, and the data content 01 is the actual data corresponding to the identifier F1A9; after receiving the response data frame replied by the controller, the diagnostic instrument will identify the specific controller type or supplier information corresponding to the data content in the response data frame according to the peer table received previously, for example, data content 01 corresponds to supplier 1.
[0074] In this optional embodiment, since the response data frame strictly matches the service code and identifier in the diagnostic instrument request, the response content is guaranteed to meet the requirements of the request. The accurate data response ensures the integrity of the data, reduces the transmission of redundant information, reduces the communication load of the CAN bus, and improves the performance and real-time performance of the bus.
[0075] Optionally, the response data frame further includes a success response code, and the success response code is used to respond to the request service corresponding to the read service code.
[0076] Specifically, after receiving the request, the controller needs to verify whether the requested identifier is valid and whether it can access the data corresponding to the identifier. If everything is normal, it uses service 62 (i.e., the success response code) to reply to the diagnostic instrument. The response data frame consists of the diagnostic response address (e.g., 7E8), the success response code (e.g., 62), the identifier (e.g., F1A9) and the data content (e.g., 01), that is, the response data frame can be [7E8]62F1A9 01.
[0077] Among them, 62 is the response code for responding to the service 22 request. 62 indicates that the controller has successfully processed the request and returned the required data to the diagnostic instrument, that is, the ECU has successfully received and understood the identifier in the request (for example, F1A9), and the returned content is the specific data corresponding to the identifier (that is, the data content); if the ECU cannot correctly process the request (such as the identifier is invalid or the data is unavailable), it will return an error response code (such as 7F, etc.) with the specific error reason (such as access denied, invalid identifier, etc.).
[0078] In this optional embodiment, the successful response code indicates that the ECU correctly executes the request of the diagnostic instrument and returns the expected data or results, and ensures consistency between the request and the response, ensuring that the returned data matches the request.
[0079] Optionally, the read request includes a plurality of identifiers corresponding to the data content, and the plurality of identifiers are configured to correspond to a plurality of data contents stored in the controller, respectively.
[0080] Specifically, the read request includes multiple identifiers corresponding to the data content, for example, identifier one corresponds to the data content related to the supplier, identifier two corresponds to the data content related to the vehicle model, and identifier three corresponds to the data content related to the vehicle model year, thereby realizing the identification of supplier and year information, etc.
[0081] In this optional embodiment, by setting multiple identifiers to correspond to multiple data contents stored in the controller, the supplier and year information can be further identified simultaneously.
[0082] Optionally, the diagnosis response address is determined according to the diagnosis request address and a preset rule.
[0083] Specifically, in automotive diagnostic protocols (such as the ISO 14229-UDS protocol), diagnostic communication is carried out through the CAN bus. To ensure that data requests and responses between the communicating parties are not confused, different CAN IDs are usually used to distinguish request and response messages. For example, the diagnostic response address is set to diagnostic request address + 8 (that is, the preset rule is that the diagnostic request address + 8 can obtain the diagnostic response address). The request and response addresses do not conflict and are easy for the system to identify. The response address can be determined by simply adding 8 to the request address.
[0084] In the CAN bus, the smaller the ID, the higher the priority. To ensure that the request message has a higher priority, the ID corresponding to the request message is usually lower than the ID corresponding to the response message (that is, the request address is smaller than the response address).
[0085] In this optional embodiment, the diagnostic response address is determined based on the diagnostic request address and preset rules, ensuring that the CAN IDs of the request and response do not conflict and making it easier for technicians to manage these addresses.
[0086] like Figure 6 As shown, an embodiment of the present invention provides an automobile diagnostic device 600, comprising:
[0087] A first module 610 is configured to, when a controller is selected for diagnosis, send a read request for data content to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller;
[0088] A second module 620 is configured to obtain the data content from the controller according to the diagnostic response address of the controller and the read request;
[0089] The third module 630 is configured to display the corresponding supplier and a function item interface corresponding to the supplier according to the data content, so as to complete the diagnosis of the controller.
[0090] like Figure 7 As shown, an electronic device 700 provided by an embodiment of the present invention includes a memory 720 and a processor 710; the memory 720 is used to store computer programs; the processor 710 is used to implement the above-mentioned automobile diagnostic method when executing the computer program.
[0091] In other words, an electronic device 700 includes a memory 720 and a processor 710 coupled to the memory 720; the memory 720 is configured to store a computer program; and the processor 710 is configured to perform the following operations when executing the computer program:
[0092] When a controller is selected for diagnosis, a read request for data content is sent to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller;
[0093] acquiring the data content from the controller according to the diagnostic response address of the controller and the read request;
[0094] The corresponding supplier and the function item interface corresponding to the supplier are displayed according to the data content to complete the diagnosis of the controller.
[0095] An embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above-mentioned automobile diagnostic method is implemented.
[0096] In other words, a non-volatile computer-readable storage medium stores a computer program, which, when executed by a processor, causes the processor to perform the following operations:
[0097] When a controller is selected for diagnosis, a read request for data content is sent to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller;
[0098] acquiring the data content from the controller according to the diagnostic response address of the controller and the read request;
[0099] The corresponding supplier and the function item interface corresponding to the supplier are displayed according to the data content to complete the diagnosis of the controller.
[0100] An electronic device 700 that can serve as a server or client of the present invention will now be described, which is an example of a hardware device that can be applied to various aspects of the present invention. The electronic device 700 is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device 700 can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0101] The electronic device 700 includes a computing unit that can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) or a computer program loaded from a storage unit into a random access memory (RAM). In the RAM, various programs and data required for device operation can also be stored. The computing unit, ROM, and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.
[0102] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). In this application, the units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments of the present invention. In addition, the functional units in the various embodiments of the present invention can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into a single unit. The above-mentioned integrated units can be implemented in the form of hardware or software functional units.
[0103] Although the present invention is disclosed as above, the protection scope of the present invention is not limited thereto. Those skilled in the art may make various changes and modifications without departing from the spirit and scope of the present invention, and these changes and modifications will fall within the protection scope of the present invention.
Claims
1. A vehicle diagnostic method, characterized in that: include: When a controller is selected for diagnosis, a read request for data content is sent to the corresponding controller according to the diagnosis request address of the controller, wherein the data content is configured to correspond to the supplier of the controller; wherein the read request includes an identifier corresponding to the data content, and the identifier is used to read a value representing supplier information. The sending of the read request for data content to the corresponding controller according to the diagnosis request address of the controller includes: constructing a request data frame according to the diagnosis request address and the identifier; and sending the request data frame to the corresponding controller according to the diagnosis request address; Obtaining the data content from the controller according to the diagnostic response address of the controller and the read request; wherein, obtaining the data content from the controller according to the diagnostic response address of the controller and the read request comprises: receiving a response data frame fed back by the controller, and obtaining the data content according to the response data frame, wherein the response data frame is constructed according to the diagnostic response address, the identifier, and the data content after the controller extracts the corresponding data content from the memory according to the identifier; The corresponding supplier and the function item interface corresponding to the supplier are displayed according to the data content to complete the diagnosis of the controller.
2. The vehicle diagnostic method according to claim 1, wherein: The read request further includes a read service code, and the sending of a read request for data content to the corresponding controller according to the diagnostic request address of the controller includes: constructing a request data frame according to the diagnosis request address, the read service code and the identifier; The request data frame is sent to the corresponding controller according to the diagnosis request address.
3. The vehicle diagnostic method according to claim 2, characterized in that: The response data frame further includes a success response code, and the success response code is used to respond to the request service corresponding to the read service code.
4. The vehicle diagnostic method according to claim 1, wherein: The read request includes a plurality of identifiers corresponding to the data content, and the plurality of identifiers are configured to correspond to a plurality of data contents stored in the controller, respectively.
5. The vehicle diagnostic method according to claim 1, wherein: The diagnosis response address is determined according to the diagnosis request address and a preset rule.
6. An automobile diagnostic device, characterized in that: include: A first module is configured to, when a controller is selected for diagnosis, send a read request for data content to a corresponding controller according to a diagnosis request address of the controller, wherein the data content is configured to correspond to a supplier of the controller; wherein the read request includes an identifier corresponding to the data content, the identifier being used to read a value representing supplier information, and sending the read request for data content to the corresponding controller according to the diagnosis request address of the controller includes: constructing a request data frame according to the diagnosis request address and the identifier; and sending the request data frame to the corresponding controller according to the diagnosis request address; A second module is configured to obtain the data content from the controller according to the diagnostic response address of the controller and the read request; wherein, obtaining the data content from the controller according to the diagnostic response address of the controller and the read request comprises: receiving a response data frame fed back by the controller, and obtaining the data content according to the response data frame, wherein the response data frame is constructed according to the diagnostic response address, the identifier, and the data content after the controller extracts the corresponding data content from the memory according to the identifier; The third module is used to display the corresponding supplier and the function item interface corresponding to the supplier according to the data content to complete the diagnosis of the controller.
7. An electronic device, characterized in that: including memory and processor; The memory is used to store computer programs; The processor is configured to implement the automobile diagnosis method according to any one of claims 1 to 5 when executing the computer program.
8. A computer-readable storage medium, characterized in that The storage medium stores a computer program, and when the computer program is executed by a processor, the automobile diagnostic method according to any one of claims 1 to 5 is implemented.
Citation Information
Patent Citations
Vehicle control system, vehicle and vehicle control method
CN118579090A
Remote automobile diagnostic method and apparatus, mobile terminal,electronic device and server
US20200226852A1