A non-j2534 device compatibility method, tool, and computer- storeable medium

Abstract

The application relates to a non-J2534 device compatible method, a tool and a computer storage medium, the method comprising the following steps: predefining a high-layer interface format, the high-layer interface format defining a high-layer interface in a J2534 protocol standard form and containing a communication function conforming to the J2534 protocol; when a vehicle diagnosis device conforming to the J2534 protocol or a vehicle diagnosis device not conforming to the J2534 protocol is used, the high-layer interface is respectively realized according to the pre-defined high-layer interface format; a connection class respectively acquires the high-layer interface of the vehicle diagnosis device; and a client of vehicle diagnosis software respectively accesses the high-layer interface by accessing the connection class and accesses the vehicle diagnosis device conforming to the J2534 protocol or the vehicle diagnosis device not conforming to the J2534 protocol. Through the application, various diagnosis devices of different protocols can be integrated, the expansibility is improved, and the function of the diagnosis software is improved.

Description

Technical Field

[0001] This invention relates to the field of automotive electronic information, and in particular to a method, tool, and computer-compatible storage medium for non-J2534 devices. Background Technology

[0002] With the development of the automotive industry, various diagnostic tools for vehicles have emerged. J2534, released by SAE (Society of Automotive Engineers) in 2002 and authorized by the U.S. Environmental Protection Agency for use in reprogramming Electronic Control Units (ECUs), is an interface standard protocol that can be used as an automotive diagnostic protocol. Many automotive OEMs' diagnostic software and interface device manufacturers support this protocol, but diagnostic devices that do not support the J2534 protocol still exist.

[0003] If diagnostic software only supports J2534 protocol devices, its disadvantages are poor scalability and applicability; it will be incompatible with non-J2534 devices. Developing separate diagnostic software for non-J2534 devices, which may be based on many different protocol standards, would significantly increase the cost of the diagnostic software and hinder diagnostic work and unified data maintenance. Summary of the Invention

[0004] To address the aforementioned problems in the prior art, this invention provides a method, tool, and computer-storable medium for compatibility with non-J2534 devices. These methods aim to solve the compatibility issues of non-J2534 devices, support different protocols of non-J2534 devices, improve scalability, and reduce coupling.

[0005] This invention provides a method for compatibility with non-J2534 devices, comprising: predefining a high-level interface format, wherein the high-level interface format specifies that the high-level interface adopts the J2534 protocol standard form and includes communication functions conforming to the J2534 protocol; when using a vehicle diagnostic device conforming to the J2534 protocol or a vehicle diagnostic device not conforming to the J2534 protocol, the high-level interface is implemented according to the predefined high-level interface format respectively; a connection class obtains the high-level interface of the vehicle diagnostic device respectively; and a client of the vehicle diagnostic software accesses the high-level interface by accessing the connection class, and accesses the vehicle diagnostic device conforming to the J2534 protocol or the vehicle diagnostic device not conforming to the J2534 protocol respectively.

[0006] Another aspect of the present invention provides a non-J2534 device compatible tool, comprising: a high-level interface, wherein the high-level interface is implemented using a vehicle diagnostic device conforming to the J2534 protocol or a vehicle diagnostic device not conforming to the J2534 protocol according to a predefined format, wherein the predefined format refers to the high-level interface adopting the J2534 protocol standard form and containing communication functions conforming to the J2534 protocol; and a connection class, which respectively obtains the high-level interface of the vehicle diagnostic device, for the vehicle diagnostic software client to access the high-level interface by accessing the connection class, and to access the vehicle diagnostic device conforming to the J2534 protocol or the vehicle diagnostic device not conforming to the J2534 protocol through the high-level interface.

[0007] In another aspect, the present invention provides a computer-storable medium storing program code, the program code including instructions for performing the steps in the above-described method.

[0008] The non-J2534 device compatibility method, tool, and computer-storable medium provided by this invention adopt an appearance pattern, enabling the integration of diagnostic devices with various different protocols, improving scalability, and enhancing the functionality of diagnostic software. By adding a higher-level interface between the existing system's client and complex protocols, the complexity brought about by different protocols is hidden, connecting non-J2534S devices with existing diagnostic software. This higher-level interface allows for better handling of call order and dependencies, reducing mutual dependence and improving flexibility and security. Attached Figure Description

[0009] Figure 1 This is a flowchart of the non-J2534 device compatibility method provided in Embodiment 1 of the present invention;

[0010] Figure 2 This is a schematic diagram of the high-level interface provided in Embodiment 1 of the present invention;

[0011] Figure 3 This is a schematic diagram of the connection of the vehicle diagnostic equipment provided in Embodiment 1 of the present invention;

[0012] Figure 4 This is a schematic diagram of the non-J2534 compatible tool provided in Embodiment 1 of the present invention. Detailed Implementation

[0013] 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 some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0014] This invention is primarily based on the J2534 protocol. The J2534 standard protocol is for flash programming of radio frequency-related ECUs, regardless of the communication protocol used by the ECU. Using the J2534 protocol allows all types of ECUs to use only a single tool (hardware device), and such devices using the J2534 protocol are often referred to as pass-through devices.

[0015] The J2534 standard protocol defines two types of interfaces for walk-through devices that support SAE J2534: one is the application programming interface (API) between a programming application running on a computer and the software device driver of the walk-through device; the other is the hardware interface between the walk-through device and the vehicle.

[0016] The J2534 provides a programming interface for both application software clients and host computer drivers. If compatibility of the J2534 programming interface can be achieved, the diagnostic software provided by Company A, along with diagnostic equipment from Company B, the J2534 driver, and the device driver, can be used to diagnose the vehicle.

[0017] Example 1

[0018] This embodiment provides a method for compatibility with non-J2534 devices, such as... Figure 1 As shown, it includes:

[0019] Step S101: Predefine the high-level interface format. The high-level interface format requires that the high-level interface adopt the J2534 protocol standard form and include communication functions conforming to the J2534 protocol. Specifically, a J2534 high-level interface can be predefined, which contains the standard API communication functions of the J2534 protocol. The high-level interface format can be as follows: Figure 2 As shown. This high-level interface format can be implemented using Java classes or other languages ​​supported by the J2534 protocol.

[0020] Step S102: When using vehicle diagnostic equipment compliant with the J2534 protocol or not, the high-level interface is implemented according to the predefined high-level interface format. Specifically, both devices using the J2534 protocol and devices not using the J2534 protocol implement this interface (e.g., Figure 2 (J2534Device, NotJ2534Device1, NotJ2534Device2 in the example). In specific implementations, the interface can be implemented through classes.

[0021] In an optional implementation, the non-J2534 device compatibility method of this embodiment further includes: determining whether the vehicle diagnostic device conforms to the J2534 protocol, wherein conforming to the J2534 protocol means supporting at least one of the following communication protocols: ISO14229, ISO14230, CAN, ISO15765, and J1939. Specifically, since J2534 supports the following communication protocols: ISO14229, ISO14230, CAN (ISO11898), ISO15765, and J1939, devices that communicate using these protocols can be identified as devices using the J2534 protocol, while other devices that use other protocols such as RS-232 serial communication protocol, vehicle Ethernet, etc., are identified as devices using non-J2534 protocols.

[0022] Step S103: The connection class obtains the high-level interface of the vehicle diagnostic device; specifically, the connection class (Connector) obtains the actual vehicle diagnostic device (Device). The connection class interfaces with the high-level interface on one side and the client on the other, enabling data transmission between the high-level interface and the client.

[0023] In step S104, the vehicle diagnostic software client accesses higher-level interfaces through the connection class, and accesses either vehicle diagnostic devices compliant with the J2534 protocol or those not compliant with the J2534 protocol. Specifically, the client accesses the connection class (Connector) to access the vehicle diagnostic device. The client can be vehicle diagnostic software installed on the user's PC (such as original factory diagnostic software from Volkswagen, Honda, Toyota, Mercedes-Benz, etc.), and the vehicle diagnostic device can be a device of the same brand as the vehicle diagnostic software or a different brand. Figure 3 As shown, one end of the vehicle diagnostic device connects to the client of the vehicle diagnostic software installed on a PC via a high-level interface, while the other end connects to the vehicle's ECU via a programming driver interface. The programming driver interface is used to diagnose and reprogram the vehicle's ECU. Therefore, through the high-level interface implemented by the vehicle diagnostic device, the vehicle diagnostic software can diagnose the vehicle and perform programming operations to rewrite the vehicle's ECU, regardless of whether the vehicle diagnostic device supports the J2534 protocol.

[0024] The non-J2534 device compatibility method provided in this embodiment adopts the facade pattern, which can integrate diagnostic devices with various different protocols, improve scalability, and enhance the functionality of the diagnostic software. By adding a higher-level interface between the existing system's client and the complex protocols, the complexity brought about by different protocols is hidden, connecting non-J2534S devices with existing diagnostic software. This higher-level interface can handle call order and dependencies effectively, reducing mutual dependencies and improving flexibility and security.

[0025] In one optional implementation, the communication function includes at least the PassThruConnect function, which establishes a connection between the client and the vehicle diagnostic equipment. Specifically, this function contains information such as the protocol used, the standard or extended CAN identifier, or whether ISO 15765 is used. The function may also include a channel identifier, which will be used for all subsequent communication.

[0026] In specific implementations, the J2534 API also includes many functions for communication, which must be supported by both hardware tools and vehicle manufacturer applications, as shown in Table 1. For example, the function PassThruIoctl can be used for initialization to set various parameters, such as node address, baud rate, or protocol-specific parameters. Furthermore, some ECUs send a large number of messages at very short intervals; the filtering function PassThruStartMsgFilter can be set to block or forward messages, thereby reducing the number of messages that need to be sent between the hardware tools and the client.

[0027] Table 1 J2534 API Function Table

[0028]

[0029]

[0030] This embodiment also provides a non-J2534 device compatible tool. This tool can be built into the vehicle diagnostic device or stored as an external device and connected to the vehicle diagnostic device via a wireless or wired network interface for easy access. At the hardware level, if the compatible tool is built into the vehicle diagnostic device, the device's memory stores the software code of the non-J2534 device compatible tool, and the processor runs the software code. If the compatible device is a separate external device, the compatible tool may include memory, a processor, and an interface. The memory and processor store and run the code, and the interface connects to other devices for communication.

[0031] like Figure 4 As shown, the non-J2534 device compatibility tool in this embodiment includes:

[0032] The high-level interface 401 is implemented using either vehicle diagnostic equipment conforming to or not conforming to the J2534 protocol, according to a predefined format. The predefined format refers to the high-level interface adopting the J2534 protocol standard form and containing communication functions conforming to the J2534 protocol. Specifically, a J2534 high-level interface can be predefined, containing standard API communication functions of the J2534 protocol. The high-level interface format can be as follows: Figure 2 As shown. This high-level interface format can be implemented using Java classes or other languages ​​supported by the J2534 protocol. This predefined high-level interface format can be stored in the compatibility tool or obtained by downloading or other means when needed.

[0033] Devices using the J.2534 protocol and devices not using the J.2534 protocol both implement this interface (e.g. Figure 2 In specific implementations, the interface (J2534Device, NotJ2534Device1, NotJ2534Device2) can be implemented through classes.

[0034] In an optional vehicle diagnostic device that conforms to the J2534 protocol, the vehicle diagnostic device means that it supports at least one of the following communication protocols: ISO14229, ISO14230, CAN, ISO15765, and J1939. The communication protocols supported by J2534 include ISO14229, ISO14230, CAN (ISO11898), ISO15765, and J1939. Devices that communicate using these protocols can be considered to be devices using the J2534 protocol, while other devices that use other protocols such as RS-232 serial communication protocol or automotive Ethernet protocol are considered to be devices using non-J2534 protocols.

[0035] The connection class 402 retrieves the high-level interface of the vehicle diagnostic device. The vehicle diagnostic software client accesses this interface via the connection class to access either the J.2534 compliant or non-compliant vehicle diagnostic device. Specifically, the connection class (Connector) retrieves the actual vehicle diagnostic device (Device), and the client accesses the connection class (Connector) to access the device. The connection class interfaces with both the high-level interface and the client, enabling data transmission between them. The client can be vehicle diagnostic software installed on the user's PC (such as original equipment manufacturer (OEM) diagnostic software from Volkswagen, Honda, Toyota, Mercedes-Benz, etc.), and the vehicle diagnostic device can be from the same brand as the diagnostic software or a different brand. Figure 3As shown, one end of the vehicle diagnostic device connects to the client of the vehicle diagnostic software installed on a PC via a high-level interface, while the other end connects to the vehicle's ECU via a programming driver interface. The programming driver interface is used to diagnose and reprogram the vehicle's ECU. Therefore, through the high-level interface implemented by the vehicle diagnostic device, the vehicle diagnostic software can diagnose the vehicle and perform programming operations to rewrite the vehicle's ECU, regardless of whether the vehicle diagnostic device supports the J2534 protocol.

[0036] The non-J2534 device compatibility tool provided in this embodiment adopts the facade pattern, which can integrate diagnostic devices with various different protocols, improving scalability and enhancing the functionality of the diagnostic software. By adding a higher-level interface between the existing system's client and the complex protocols, the complexity brought about by different protocols is hidden, connecting non-J2534S devices with existing diagnostic software. This higher-level interface allows for better handling of call order and dependencies, reducing mutual dependencies and improving flexibility and security.

[0037] This embodiment also provides a computer-storable medium storing program code, which includes instructions for performing the steps in the aforementioned method.

[0038] In the description of the embodiments of the present invention, it should be understood that the terms "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "center," "top," "bottom," "top," "bottom," "inner," "outer," "inner side," and "outer side," etc., indicating the orientation or positional relationship, are based on the orientation or positional relationship shown in the accompanying drawings and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the present invention. "Inner side" refers to the interior or enclosed area or space. "Outer perimeter" refers to the area surrounding a specific component or specific area.

[0039] In the description of embodiments of the present invention, the terms "first," "second," "third," and "fourth" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first," "second," "third," or "fourth" may explicitly or implicitly include one or more of that feature. In the description of the present invention, unless otherwise stated, "a plurality of" means two or more.

[0040] In the description of the embodiments of the present invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," "joining," and "assembly" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0041] In the description of embodiments of the present invention, specific features, structures, materials or characteristics may be combined in any suitable manner in one or more embodiments or examples.

[0042] In the description of the embodiments of the present invention, it should be understood that "-" and "~" represent a range of two numerical values, and this range includes the endpoints. For example, "AB" represents a range greater than or equal to A and less than or equal to B. "A~B" represents a range greater than or equal to A and less than or equal to B.

[0043] In the description of embodiments of the present invention, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0044] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for compatibility with non-J2534 devices, characterized in that, The method includes: A predefined high-level interface format is defined, which specifies that the high-level interface adopts the J2534 protocol standard form and includes communication functions that conform to the J2534 protocol. The communication functions include at least the PassThruConnect function for establishing a connection between the client and the vehicle diagnostic equipment. The PassThruConnect function contains information on the protocol used, standard or extended CAN identifier, whether ISO15765 is used, and a channel identifier for all subsequent communications. The high-level interface format is implemented using JAVA classes or other programming languages ​​supported by the J2534 protocol. The system determines whether the vehicle diagnostic equipment conforms to the J2534 protocol. Conformity to the J2534 protocol means supporting at least one of the following communication protocols: ISO14229, ISO14230, CAN, ISO15765, and J1939. Devices using these protocols are considered J2534 protocol devices. RS... Devices using J2532 serial communication protocol, vehicle Ethernet, or other communication protocols are considered non-J2534 protocol devices. When using vehicle diagnostic equipment that conforms to the J2534 protocol or that does not conform to the J2534 protocol, the high-level interface is implemented according to the predefined high-level interface format. Both J2534 protocol devices and non-J2534 protocol devices implement the same high-level interface. The connection class obtains the high-level interface of the vehicle diagnostic equipment. One end of the connection class connects to the high-level interface, and the other end connects to the client to realize data transmission between the high-level interface and the client. The vehicle diagnostic software client accesses the higher-level interfaces by accessing the connection class, and accesses vehicle diagnostic devices that conform to or do not conform to the J2534 protocol.

2. A tool compatible with non-J2534 devices, characterized in that, The method applied to claim 1 includes: The high-level interface is implemented using a vehicle diagnostic device that conforms to the J2534 protocol or a vehicle diagnostic device that does not conform to the J2534 protocol, respectively, according to a predefined format. The predefined format means that the high-level interface adopts the J2534 protocol standard form and includes communication functions that conform to the J2534 protocol. The connection class obtains the high-level interface of the vehicle diagnostic device, which is used by the client of the vehicle diagnostic software to access the high-level interface and access the vehicle diagnostic device that conforms to the J2534 protocol or the vehicle diagnostic device that does not conform to the J2534 protocol through the high-level interface.

3. The non-J2534 device compatibility tool according to claim 2, characterized in that, The communication function includes at least: The PassThruConnect function is used to establish a connection between the client and the vehicle diagnostic device.

4. The non-J2534 device compatibility tool according to claim 2, characterized in that, Using the vehicle diagnostic equipment that conforms to the J2534 protocol means that the vehicle diagnostic equipment supports at least one of the following communication protocols: ISO14229, ISO14230, CAN, ISO15765, and J1939.

5. A computer storage medium storing program code, the program code including instructions for performing the steps of the method as claimed in claim 1.

Images