Commercial vehicle flashing fault positioning method and device and fault diagnosis system

Abstract

The invention provides a commercial vehicle flashing fault positioning method and device and a fault diagnosis system, and the method comprises the steps: controlling OBD equipment to be connected to a diagnosis interface when a commercial vehicle flashing fault occurs, and determining a line puncturing point based on an ODX file of a vehicle; the line pricking point is located between the diagnosis interface and a target ECU to be flashed; in the flashing process of the target ECU, synchronously collecting a first message at the diagnosis interface and a second message at the barbed line point; and comparing the arrival states of the first message and the second message, and positioning the physical link with the flashing fault. According to the method and the device, the first message at the diagnosis interface and the second message at the barbed line point are subjected to differential comparison, so that fault positioning can be improved from a node level to a line segment level, and the fault positioning precision is improved.

Description

Technical Field

[0001] This invention relates to the field of fault location technology for flashing and writing, and specifically to a method, device and fault diagnosis system for locating faults in flashing and writing of commercial vehicles. Background Technology

[0002] With the development of automotive electronics technology, automotive control systems have become increasingly complex. Modern automotive control systems often contain multiple Electronic Control Units (ECUs), each responsible for managing specific vehicle functions such as engine control, transmission control, body control, and airbag systems. To ensure these control systems function properly, automakers and developers must perform thorough diagnostics and testing on the ECUs. This diagnostic and testing process requires reprogramming the ECUs, and fault localization during this process is crucial to the efficiency and reliability of the diagnostic and testing process.

[0003] There are two existing fault location / diagnosis methods. One is ODX-based general diagnostics, which uses ODX files to parse vehicle diagnostic parameters and read general fault codes. Its core lies in improving the compatibility of diagnostic tools by using standardized description files, focusing on software and logic-level diagnostics, such as detecting ECU response and software version compatibility. However, it cannot detect physical connection problems, such as damaged wiring harnesses, loose connectors, signal interference, and other hardware faults. The other is location / diagnosis based on mirrored packets. Mirrored monitoring replicates network traffic through a "mirror port" of a network device (such as a gateway or switch) and then analyzes these replicated packets. The mirror port can only capture data "passing through that port." If the fault occurs before the mirror point (e.g., the wiring harness from the diagnostic interface to the gateway), the mirror port will not see this data and therefore cannot detect the fault. Furthermore, mirrored monitoring is often used to statistically analyze macro-level indicators such as network load and error frame rate, rather than for real-time tracking of specific packets. In flashing scenarios, it is necessary to know precisely at which point the flashing packets are lost, and mirroring cannot provide this granular analysis.

[0004] Therefore, there is an urgent need to provide a method, device, and fault diagnosis system for locating faults in commercial vehicles, which can solve the problem that existing diagnostic methods focus on macroscopic faults, that is, they can only obtain node-level faults such as puncture points or diagnostic interfaces, but cannot obtain specific physical link faults between nodes and ECUs. This would enable fault location from the node logic level to the physical line segment level, thereby improving fault location accuracy, providing support for subsequent fault maintenance / repair, and improving the efficiency of subsequent maintenance / repair. Summary of the Invention

[0005] In view of this, it is necessary to provide a method, device and fault diagnosis system for locating faults in commercial vehicle flashing, in order to solve the technical problem that the existing technology focuses on macro-level faults, that is, it can only obtain node-level faults such as spiking points or diagnostic interfaces, but cannot obtain specific physical link faults between nodes and ECUs, resulting in low fault location accuracy.

[0006] To address the aforementioned technical problems, in a first aspect, the present invention provides a method for locating faults in the flashing process of commercial vehicles, comprising: When a commercial vehicle ECU flashing malfunctions, the OBD device is connected to the diagnostic interface and the puncture point is determined based on the vehicle's ODX file; the puncture point is located between the diagnostic interface and the target ECU to be flashed. During the flashing process of the target ECU, the first message at the diagnostic interface and the second message at the puncture point are collected simultaneously. By comparing the arrival status of the first and second messages, the physical link where the write failure occurred can be located.

[0007] In one possible implementation, the spiking points are determined based on the vehicle's ODX file, including: The diagnostic communication route is determined based on the ODX file and the address of the target ECU; When a gateway exists in the diagnostic communication route, the gateway is used as the spike point.

[0008] In one possible implementation, determining the barbed wire points based on the vehicle's ODX file also includes: If no gateway is found in the diagnostic communication route, determine whether a router is found in the diagnostic communication route. When a router exists in the diagnostic communication route, the router is used as the spike point.

[0009] In one possible implementation, determining the barbed wire points based on the vehicle's ODX file also includes: When there is no router in the diagnostic communication route, the candidate ECU with the shortest physical location from the target ECU is determined, and the candidate ECU is used as the spiking point.

[0010] In one possible implementation, before comparing the arrival status of the first message and the second message, the method further includes: Extract the first flash service message from the first message and the second flash service message from the second message, wherein the first flash service message and the second flash service message include a data transmission service message; The step of comparing the arrival status of the first and second packets to locate the physical link where the write failure occurred includes: By comparing the arrival status of the first and second flash service messages, the physical link where the flash failure occurred can be located.

[0011] In one possible implementation, the first and second write service messages further include a request download service message and an exit transmission service message.

[0012] In one possible implementation, comparing the arrival status of the first message and the second message to locate the physical link where the write failure occurred includes: When both the first and second packets have an arrival status of "not arrived," it is determined that the write failure occurred on a physical link prior to the diagnostic interface. When the arrival status of the first message is "arrived" and the arrival status of the second message is "not arrived", it is determined that the write failure occurred in the physical link between the diagnostic interface and the spike point. When both the first and second messages have arrived, the cause of the flashing failure is determined to be a problem with the target ECU or software version compatibility.

[0013] In one possible implementation, the method further includes: The network topology diagram between the diagnostic interface and the target ECU is displayed on the display interface, and the physical links where the flashing failure occurred are displayed separately on the network topology diagram.

[0014] Secondly, the present invention also provides a commercial vehicle flashing fault location device, comprising: The puncture point determination unit is used to control the OBD device to connect to the diagnostic interface and determine the puncture point based on the vehicle's ODX file when a fault occurs during the flashing of a commercial vehicle; the puncture point is located between the diagnostic interface and the target ECU to be flashed. The message synchronization receiving unit is used to synchronously collect the first message at the diagnostic interface and the second message at the spiking point during the flashing process of the target ECU. The write failure location unit is used to compare the arrival status of the first message and the second message to locate the physical link where the write failure occurred.

[0015] Thirdly, the present invention also provides a fault diagnosis system, including an OBD device, a wire-tapping device, and a mobile terminal, wherein the mobile terminal includes a memory and a processor, wherein... The OBD device is used to connect to the diagnostic interface and serve as the first message monitoring point; The barbed wire device is used to perform barbed wire operations at the barbed wire point, serving as a second message monitoring point; The memory is used to store programs; The processor, coupled to the memory, is used to execute the program stored in the memory to implement the steps in the commercial vehicle fault location method described in any of the above possible implementations.

[0016] The beneficial effects of this invention are as follows: The commercial vehicle flashing fault location method provided by this invention, when a commercial vehicle flashing fault occurs, simultaneously collects the first message at the diagnostic interface and the second message at the spike point. It can determine the status through the messages and determine whether the fault occurs in the physical link between the spike point and the diagnostic interface, that is, isolate the flashing fault on the physical link between the spike point and the diagnostic interface. Its location accuracy is much higher than that of node-level faults such as ECU signal timeout or network anomaly located by ODX or mirror messages, which greatly improves the fault location accuracy and provides clear and specific repair guidance for maintenance personnel.

[0017] Furthermore, this invention determines the puncture points based on ODX files, abandoning the traditional method of blindly measuring and troubleshooting based on the experience of maintenance personnel, and realizing the automated determination of puncture points, thereby further improving the positioning efficiency and accuracy of fault location during brushing. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A schematic flowchart of an embodiment of the commercial vehicle flashing fault location method provided by the present invention; Figure 2 A schematic diagram illustrating an embodiment of the present invention for determining spiking points based on vehicle ODX files; Figure 3 A schematic diagram of an embodiment of the commercial vehicle flashing fault location device provided by the present invention; Figure 4 This is a schematic diagram of an embodiment of the fault diagnosis system provided by the present invention. Detailed Implementation

[0020] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0021] It should be understood that the schematic drawings are not drawn to scale. The flowcharts used in this invention illustrate operations implemented according to some embodiments of the invention. It should be understood that the operations in the flowcharts may be implemented out of order, and steps without logical contextual relationships may be reversed or performed simultaneously. Furthermore, those skilled in the art, guided by the content of this invention, may add one or more other operations to the flowcharts, or remove one or more operations from the flowcharts. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0022] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0023] This invention provides a method, device, and fault diagnosis system for locating faults in commercial vehicle flashing, which will be described below.

[0024] To clearly illustrate the shortcomings of existing technologies such as ODX-based general diagnostics and mirrored message diagnostics, the following explanation is provided: ODX diagnostics is a logic-level diagnostic method. It monitors ECU response and software version compatibility, assuming the physical link is normal and focusing only on communication content rather than signal transmission on the physical line. Therefore, it cannot detect physical link faults. Furthermore, when an ODX file fails to flash, it only indicates communication failure, not which cable bundle / link is faulty. In other words, ODX diagnostics diagnoses the interface node, indicating whether the interface successfully received the message. Mirrored monitoring is used to statistically analyze macroscopic indicators such as network load and error frame rate, rather than for real-time tracking of specific messages. In other words, mirrored monitoring can only determine if there is a fault in the route before the mirrored port, not the specific location of the fault. Therefore, existing diagnostic methods are all macroscopic node-level diagnostics, unable to achieve higher-precision physical line segment-level diagnostics, resulting in low location accuracy.

[0025] To solve the above technical problems, Figure 1 This is a schematic flowchart of an embodiment of the commercial vehicle flashing fault location method provided by the present invention, as shown below. Figure 1 As shown, the method for locating faults in commercial vehicle flashing includes: S101. When a commercial vehicle ECU flashing malfunctions, the OBD device is connected to the diagnostic interface and the puncture point is determined based on the vehicle's ODX file. The puncture point is located between the diagnostic interface and the target ECU to be flashed.

[0026] In this context, "OBD device" generally refers to an external device that can be plugged into a diagnostic interface and communicates with the vehicle network via the diagnostic interface. In a specific embodiment of the present invention, the OBD device can be a diagnostic tool. After the diagnostic tool is connected to the diagnostic interface, it can send commands and data to the target ECU.

[0027] The diagnostic interface (OBD interface) can be seen as the only standard access point for the vehicle's internal network to be open to the outside world. All external devices can only communicate with the ECU of a commercial vehicle through the diagnostic interface.

[0028] ODX (Open Diagnostic Data Exchange) files are used to describe the diagnostic data and logic of an ECU. They are a standardized diagnostic data format, based on XML, and can describe in detail vehicle diagnostic information such as fault codes (DTCs), communication parameters, and diagnostic services. ODX files are typically generated automatically by specialized tools such as VisualODX.

[0029] A piercing point is a physical measurement point that establishes an electrical connection with a metal wire inside a vehicle by piercing it in order to measure signals or messages.

[0030] In summary, the diagnostic interface can be seen as the main exit point of the entire vehicle network, enabling monitoring of the entire vehicle network. The spike point is equivalent to building an observation point inside the vehicle network, through which monitoring of a certain part of the vehicle network can be achieved.

[0031] S102. During the flashing process of the target ECU, the first message at the diagnostic interface and the second message at the puncture point are collected simultaneously.

[0032] To confirm the time synchronization of the first and second messages, the timestamps of the first and second messages are collected simultaneously when collecting the first and second messages, and the timing of the collection is used to determine whether the first and second messages are collected synchronously.

[0033] Specifically, if the time synchronization of the first message and the second message is poor, the next step will not be executed. The next step will only be executed when the time synchronization of the first message and the second message meets the requirements, so as to ensure the accuracy of the fault location.

[0034] S103. Compare the arrival status of the first and second messages to locate the physical link where the write failure occurred.

[0035] The arrival status refers to whether a message has been received or not. If a message has been received, the arrival status is not reached; if a message has not been received, the arrival status is not reached.

[0036] It should be understood that the commercial vehicle fault location method in this embodiment of the invention can be implemented in any device based on the commercial vehicle fault location method, such as a fault location device. Specifically, the commercial vehicle fault location method is stored in the aforementioned device as a pre-programmed program. When the device is started, the program is invoked, and the commercial vehicle fault location method is implemented.

[0037] Compared with existing technologies, the commercial vehicle flashing fault location method provided in this invention can simultaneously collect the first message at the diagnostic interface and the second message at the spike point when a flashing fault occurs in a commercial vehicle. It can determine whether the fault occurs in the physical link between the spike point and the diagnostic interface by obtaining the status through the messages. In other words, it isolates the flashing fault on the physical link between the spike point and the diagnostic interface. Its location accuracy is much higher than that of node-level faults such as ECU signal timeout or network anomalies located by ODX or mirror messages. It greatly improves the fault location accuracy and provides clear and specific repair guidance for maintenance personnel.

[0038] Furthermore, this embodiment of the invention determines the puncture points based on ODX files, abandoning the traditional method of blindly measuring and troubleshooting based on the experience of maintenance personnel, and realizing the automated determination of puncture points, thereby further improving the positioning efficiency and accuracy of fault location.

[0039] To further improve diagnostic efficiency, in some embodiments of the present invention, such as Figure 2 As shown, step S101, which determines the piercing points based on the vehicle's ODX file, includes: S201. Determine the diagnostic communication route based on the ODX file and the address of the target ECU.

[0040] In this context, diagnostic communication routing refers to the route in the ODX file that a diagnostic request starts from the diagnostic interface, ends at the target ECU, and passes through one or more network hub devices in between, consisting of all the network hub devices.

[0041] Diagnostic communication routes include, but are not limited to, gateways, routers, and various ECUs.

[0042] S202. When a gateway exists in the diagnostic communication route, the gateway is used as the spike point.

[0043] This invention, by setting a gateway as a spike point when a gateway exists in the diagnostic communication route, leverages the gateway's characteristic as a key hub connecting different networks to achieve rapid and accurate diagnosis of the longest link in the entire diagnostic communication route from the diagnostic interface to the gateway, which has the most connected devices and is most likely to have problems.

[0044] In practical applications, there are situations where there is no gateway in the diagnostic communication route. To achieve rapid fault location in this scenario, in some embodiments of the present invention, such as... Figure 2 As shown, the step S101, which determines the barbed wire points based on the vehicle's ODX file, further includes: S203. When there is no gateway in the diagnostic communication route, determine whether there is a router in the diagnostic communication route; S204. When a router is present in the diagnostic communication route, the router is used as a spike point.

[0045] To illustrate why setting a gateway as a spike point has a higher priority than setting a router as a spike point, let's take the diagnostic communication route as diagnostic interface-gateway-router-target ECU as an example: If the gateway is used as the fault point, the faulty physical link can be divided into two segments: diagnostic interface-gateway and gateway-router-target ECU. It can identify faults in the diagnostic interface-gateway segment with 100% accuracy.

[0046] If the router is used as the fault point, the faulty physical link can be divided into two segments: diagnostic interface-gateway-router and router-target ECU. It can identify faults in the router-target ECU segment with 100% accuracy.

[0047] Both involve a fuzzy range where the fault cannot be directly determined. For the gateway as the fault point, the fuzzy range is gateway-router-target ECU; for the router as the fault point, it's diagnostic interface-gateway-router. The gateway-router-target ECU segment represents the internal network after the gateway, typically smaller and more compact, possibly located within the same control cabinet, or the fault point may be the gateway itself. The physical scope and complexity of troubleshooting are relatively lower. However, the diagnostic interface-gateway-router segment encompasses the networks both inside and outside the gateway, with a longer path / range, making troubleshooting more difficult.

[0048] Therefore, by setting the priority of the gateway as a spike point to be greater than that of the router as a spike point, the embodiments of the present invention can reduce the fuzzy range after spike point diagnosis, reduce the difficulty and workload of fault location, and improve the efficiency of fault location.

[0049] In real-world scenarios, some diagnostic communication routes include neither gateways nor routers. To achieve rapid fault location in this situation, in some embodiments of the present invention, such as... Figure 2 As shown, the step S101, which determines the barbed wire points based on the vehicle's ODX file, further includes: S205. When there is no router in the diagnostic communication route, determine the candidate ECU with the shortest physical location from the target ECU in the diagnostic communication route, and use the candidate ECU as the spiking point.

[0050] This invention achieves refined segmentation by using the candidate ECU with the shortest physical distance from the target ECU as the puncture point, minimizing the fuzzy range and improving fault location efficiency.

[0051] To illustrate why the candidate ECU with the shortest physical distance to the target ECU is chosen as the spiking point, rather than any other ECU, let's take the diagnostic communication route—diagnostic interface—ECU A—ECU B—target ECU as an example: If ECU A is taken as the fault point, the physical fault link can be divided into two segments based on this fault point: diagnostic interface-ECU A and ECU A-ECU B-target ECU. It can identify faults in the diagnostic interface-ECU A segment with 100% accuracy.

[0052] If ECU B is taken as the fault point, the physical fault link can be divided into two segments based on this fault point: diagnostic interface-ECU A-ECU B and ECU B-target ECU. It can identify faults in the segment from ECU B to target ECU with 100% accuracy.

[0053] Using ECU B as the fault point can provide clear guidance for repair when a flashing fault is found in the section from ECU B to the target ECU. However, using ECU A as the fault point requires further investigation to pinpoint the location of the fault when a flashing fault is found in the section from ECU A to ECU B to the target ECU.

[0054] Therefore, by setting the priority of the gateway as a spike point to be higher than that of the router as a spike point, this embodiment of the invention can reduce the ambiguity range after spike point diagnosis, reduce the difficulty and workload of fault location, and improve fault location efficiency. In other words, by setting the above, this embodiment of the invention, under the premise that global optimal location cannot be achieved, adopts end segmentation to achieve local optimality, and always ensures high diagnostic efficiency.

[0055] In summary, the embodiments of the present invention determine the puncture point by setting the priority order of gateway, router, and nearest ECU, which can improve the rationality of puncture point selection and thus improve fault location efficiency.

[0056] Since there are various types of messages in the diagnostic communication route, and the embodiments of this invention focus on write failures, in order to further optimize the fault location efficiency, in some embodiments of this invention, before step S103, the following step is further included: Extract the first write service message from the first message and the second message from the second message. The first write service message and the second write service message include the transfer data service message (TransferData). Then step S103 is specifically as follows: By comparing the arrival status of the first and second write service messages, the physical link where the write failure occurred can be located.

[0057] This invention, by setting up the extraction of first and second brush service messages related to brushing from the first and second messages respectively, can reduce the number of messages that need to be acquired and processed, and improve the efficiency of brushing fault location.

[0058] Among them, the data transmission service message represents the actual data transmitted during the flashing process, which is crucial to the flashing process. Therefore, the first and second flashing service messages are set to include the data transmission service message.

[0059] In addition to transmitting data service messages, requests and exit requests need to be initiated before and after flashing. Therefore, in a specific embodiment of the present invention, the first flashing service message and the second flashing service message also include a request download service message and a request transferexit message.

[0060] In some embodiments of the present invention, step S103 specifically includes: When the arrival status of both the first and second messages is "not arrived", it is determined that the write failure occurred on the physical link before the diagnostic interface. It should be noted that when both the arrival status of the first and second messages is "not received," another possible problem is that while the vehicle's internal network is working properly, there is a connection issue at the spiking point and the diagnostic interface, which prevents the first and second messages from being received.

[0061] When the arrival status of the first message is "arrived" and the arrival status of the second message is "not arrived", it is determined that the write failure occurred in the physical link between the diagnostic interface and the spike point.

[0062] When the arrival status of the first message is "arrived" and the arrival status of the second message is "not arrived", it means that the diagnostic instrument has successfully issued a command. However, the command disappears when it reaches the spiking point. The fault must be on the physical link between the diagnostic interface and the spiking point, thus achieving physical segment-level positioning.

[0063] When both the first and second messages have arrived, the cause of the flashing failure is determined to be a problem with the target ECU or software version compatibility.

[0064] Specifically, both the first and second messages showed arrival status as "arrived," indicating that the physical communication link was functioning correctly, the command was successfully transmitted from the diagnostic interface to the internal node, and ultimately reached the target ECU. The fault may lie in the ECU itself or in a software / logic-level issue, such as a mismatch between the target ECU or its software version.

[0065] This invention, by comparing the arrival status of the first and second messages, transforms a complex network communication problem into a simple comparison of whether a message is present or absent, thus simplifying the amount of data to be analyzed. Simultaneously, it can clearly identify the physical line segment where the fault occurred, rather than a vague network area or node, improving the accuracy of fault location.

[0066] To achieve a clear display of faults, in some embodiments of the present invention, the commercial vehicle fault location method further includes: The network topology diagram between the diagnostic interface and the target ECU is displayed on the display interface, and the physical links where the flashing failure occurred are distinguished and displayed on the network topology diagram.

[0067] Specifically, physical links experiencing write failures can be differentiated in the network topology map through color or style changes. Specifically, physical links experiencing write failures are highlighted in red on the network topology map, and diagnostic logs are displayed on the interface.

[0068] This invention, by distinguishing and displaying physical links, achieves visual labeling of faults, providing more intuitive data support for subsequent maintenance personnel.

[0069] In a specific example of the present invention, a heavy vehicle experienced the following fault during the flashing process: the VCU (vehicle control unit) flashing process always failed at 10% progress.

[0070] First, import the ODX file. Based on the routing analysis, the gateway is automatically identified as the critical point, and it is indicated that a spike should be made at the CAN bus pin of the gateway. Then, connect the OBD device to the spike device at the gateway.

[0071] Then, the flashing process was initiated, and the critical TransferData messages were monitored in real time at the spike point and the diagnostic interface. It was found that the messages were fully captured at the diagnostic interface, but were intermittently lost at the gateway spike point.

[0072] Next, differential analysis was performed to determine that the fault occurred on the communication link between the diagnostic interface and the gateway.

[0073] Finally, on the network topology diagram in the real interface, the connection between the diagnostic interface and the gateway is highlighted in red, and a message "Physical link failure" is displayed.

[0074] Further investigation prompted maintenance personnel to intervene. After investigation, the personnel discovered a loose connection in the CAN_H line between the diagnostic interface and the gateway. They then tightened the wiring and re-flashed the firmware, which was successful. The entire fault location process took only 8 minutes, significantly improving both fault location and flashing efficiency.

[0075] In summary, the commercial vehicle flashing fault location method proposed in this invention has the following advantages: 1. It achieves precise physical-level fault location: elevating fault location from the "node level" to the "segment level," directly guiding maintenance personnel to inspect specific segments of the wiring harness or connectors—something other solutions cannot achieve. 2. It intelligently guides the piercing operation through a unique piercing point selection logic, avoiding the blind reliance on experience and improving diagnostic efficiency and accuracy. 3. It solves the problem of capturing and locating instantaneous flashing interruptions: through synchronous acquisition and differential analysis of key flashing messages, it can capture and locate the instantaneous communication interruption that causes flashing failure. 4. The diagnostic conclusions are clear and intuitive: the output results are no longer abstract fault codes or "communication timeouts," but specific and actionable maintenance guidance, such as "check the wiring harness from the diagnostic interface to the gateway."

[0076] On the other hand, embodiments of the present invention also provide a commercial vehicle flashing fault location device, such as... Figure 3 As shown, the commercial vehicle flashing fault location device 300 includes: The puncture point determination unit 301 is used to control the OBD device to connect to the diagnostic interface and determine the puncture point based on the vehicle's ODX file when a fault occurs during the flashing of a commercial vehicle; the puncture point is located between the diagnostic interface and the target ECU to be flashed. The message synchronization receiving unit 302 is used to synchronously collect the first message at the diagnostic interface and the second message at the spiking point during the flashing process of the target ECU. The write failure location unit 303 is used to compare the arrival status of the first message and the second message to locate the physical link where the write failure occurred.

[0077] The commercial vehicle flashing fault location device 300 provided in the above embodiments can realize the technical solutions described in the above commercial vehicle flashing fault location method embodiments. The specific implementation principles of each module or unit can be found in the corresponding content in the above commercial vehicle flashing fault location method embodiments, which will not be repeated here.

[0078] like Figure 4As shown, the present invention also provides a fault diagnosis system 400. The fault diagnosis system 400 includes an OBD device 401, a barbed wire device 402, and a mobile terminal 403, wherein the mobile terminal 403 includes a processor 4031, a memory 4032, and a display 4033. Figure 4 Only some components of the fault diagnosis system 400 are shown; however, it should be understood that implementation of all shown components is not required, and more or fewer components may be implemented instead.

[0079] OBD device 401 is used to connect to the diagnostic interface and serve as the first message monitoring point; The barbed wire device 402 is used to perform barbed wire operations at the barbed wire point, serving as a second message monitoring point; In some embodiments, processor 4031 is an electronic control unit (ECU) in fault diagnosis system 400, used to run program code stored in memory 4032 or process data, such as the commercial vehicle fault location method of the present invention.

[0080] In some embodiments, memory 4032 may be an internal storage unit of fault diagnosis system 400, such as hard disk or memory of fault diagnosis system 400.

[0081] In some embodiments, display 4033 may be an LED display, a liquid crystal display, a touch-screen liquid crystal display, or an OLED (Organic Light-Emitting Diode) touchscreen. Display 4033 is used to display information from the fault diagnosis system 400 and to display a visual user interface. Components 401-403 of the fault diagnosis system 400 communicate with each other via a device bus.

[0082] In some embodiments of the present invention, when the processor 4031 executes the commercial vehicle fault location program stored in the memory 4032, the following steps can be implemented: When a commercial vehicle ECU flashing fails, the OBD device is connected to the diagnostic interface and the puncture point is determined based on the vehicle's ODX file; the puncture point is located between the diagnostic interface and the target ECU to be flashed. During the flashing process of the target ECU, the first message at the diagnostic interface and the second message at the spiking point are collected simultaneously. By comparing the arrival status of the first and second messages, the physical link where the write failure occurred can be located.

[0083] Specifically, after the piercing point is determined, the OBD device 401 is connected to the diagnostic interface, and the piercing device 402 is controlled to perform the piercing operation at the piercing point.

[0084] It should be understood that when the processor 4031 executes the commercial vehicle fault location program in the memory 4032, in addition to the functions mentioned above, it can also perform other functions, as can be found in the description of the corresponding method embodiments above.

[0085] Accordingly, embodiments of the present invention also provide a computer-readable storage medium for storing computer-readable programs or instructions. When the programs or instructions are executed by a processor, they can implement the steps or functions of the commercial vehicle fault location method provided in the above-described method embodiments.

[0086] Those skilled in the art will understand that all or part of the processes of the methods described in the above embodiments can be implemented by a computer program instructing related hardware (such as a processor, controller, etc.), and the computer program can be stored in a computer-readable storage medium. The computer-readable storage medium may be a disk, optical disk, read-only memory, or random access memory, etc.

[0087] The above provides a detailed description of a commercial vehicle flashing fault location method, device, and fault diagnosis system provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A commercial vehicle flash write fault localization method, characterized in that, The method comprises the following steps: When the commercial vehicle writing fails, the OBD device is connected to the diagnostic interface, and the writing point is determined based on the ODX file of the vehicle; The writing point is located between the diagnostic interface and the target ECU to be written; During the writing process of the target ECU, the first message at the diagnostic interface and the second message at the writing point are synchronously collected; By comparing the arrival states of the first message and the second message, the physical link where the writing failure occurs is located.

2. The commercial vehicle flash failure localization method of claim 1, wherein, Determining the writing point based on the ODX file of the vehicle comprises the following steps: Determining the diagnostic communication route based on the ODX file and the address of the target ECU; When there is a gateway in the diagnostic communication route, the gateway is taken as the writing point.

3. The commercial vehicle flash failure localization method of claim 2, wherein, Determining the writing point based on the ODX file of the vehicle further comprises the following steps: When there is no gateway in the diagnostic communication route, it is judged whether there is a router in the diagnostic communication route; When there is a router in the diagnostic communication route, the router is taken as the writing point.

4. The commercial vehicle flash failure localization method of claim 3, wherein, Determining the writing point based on the ODX file of the vehicle further comprises the following steps: When there is no router in the diagnostic communication route, a candidate ECU with the shortest distance to the target ECU in the diagnostic communication route is determined, and the candidate ECU is taken as the writing point.

5. The commercial vehicle flash failure localization method of claim 1, wherein, Before the step of comparing the arrival states of the first message and the second message, the method further comprises the following steps: Extracting a first writing service message of the first message and a second writing service message in the second message, wherein the first writing service message and the second writing service message comprise a transmission data service message; The step of comparing the arrival states of the first message and the second message, and locating the physical link where the writing failure occurs, comprises the following steps: Comparing the arrival states of the first writing service message and the second writing service message, and locating the physical link where the writing failure occurs.

6. The commercial vehicle flash failure localization method of claim 5, wherein, The first writing service message and the second writing service message further comprise a request download service message and an exit transmission service message.

7. The commercial vehicle flash failure localization method of claim 1, wherein, The step of comparing the arrival states of the first message and the second message, and locating the physical link where the writing failure occurs, comprises the following steps: When the arrival states of the first message and the second message are both not arrived, it is determined that the writing failure occurs in the physical link before the diagnostic interface; When the arrival state of the first message is arrived and the arrival state of the second message is not arrived, it is determined that the writing failure occurs in the physical link between the diagnostic interface and the writing point; When the arrival states of the first message and the second message are both arrived, it is determined that the writing failure is caused by the target ECU or software version matching problem.

8. The commercial vehicle flash failure localization method of claim 1, wherein, The method further comprises the following steps: Displaying the network topology diagram between the diagnostic interface and the target ECU on the display interface, and distinguishing and displaying the physical link where the writing failure occurs on the network topology diagram.

9. A commercial vehicle flash failure localization device, characterized by The device comprises a writing point determination unit, which is configured to control the OBD device to be connected to the diagnostic interface when the commercial vehicle writing fails, and to determine the writing point based on the ODX file of the vehicle; the writing point is located between the diagnostic interface and the target ECU to be written. ​ A message synchronous receiving unit is configured to synchronously collect a first message at the diagnostic interface and a second message at the wire piercing point during a flashing process of the target ECU; A flashing failure positioning unit is configured to compare arrival states of the first message and the second message to position a physical link where the flashing failure occurs.

10. A failure diagnosis system characterized by comprising: The system comprises an OBD device, a wire piercing device, and a mobile terminal, the mobile terminal comprising a memory and a processor, wherein, The OBD device is configured to be connected to a diagnostic interface as a first message monitoring point; The wire piercing device is configured to perform a wire piercing operation at a wire piercing point as a second message monitoring point; The memory is configured to store a program; The processor is coupled to the memory and configured to execute the program stored in the memory to implement steps in the commercial vehicle flashing failure positioning method according to any one of claims 1 to 8.

Images