WO2024027240A1 - 诊断模块的调用方法、装置和系统 - Google Patents

诊断模块的调用方法、装置和系统 Download PDF

Info

Publication number
WO2024027240A1
WO2024027240A1 PCT/CN2023/091352 CN2023091352W WO2024027240A1 WO 2024027240 A1 WO2024027240 A1 WO 2024027240A1 CN 2023091352 W CN2023091352 W CN 2023091352W WO 2024027240 A1 WO2024027240 A1 WO 2024027240A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
terminal device
diagnostic
unit
functional unit
Prior art date
Application number
PCT/CN2023/091352
Other languages
English (en)
French (fr)
Inventor
谢嘉丰
吴恩奇
肖灵聪
Original Assignee
深圳市星卡软件技术开发有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市星卡软件技术开发有限公司 filed Critical 深圳市星卡软件技术开发有限公司
Publication of WO2024027240A1 publication Critical patent/WO2024027240A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • the present application relates to the field of vehicle diagnosis technology, and in particular to a method, device and system for calling a diagnostic module.
  • the purpose of this application is to provide a calling method, device and system for a diagnostic module to improve software development efficiency and facilitate software version maintenance.
  • embodiments of the present application provide a method for calling a diagnostic module, which is applied to a terminal device.
  • the terminal device is communicatively connected to a lower computer of the vehicle; the terminal device is provided with a diagnostic module, and the diagnostic module is encapsulated with multiple functional units.
  • the module is provided with a calling function; the method includes: obtaining the diagnostic instruction input by the user and determining the target functional unit corresponding to the diagnostic instruction; calling the target functional unit based on the calling function corresponding to the target functional unit; executing the function corresponding to the target functional unit to obtain the vehicle's diagnostic information.
  • the above functional units include at least one of the following: vehicle identification unit, fault code reading unit, fault code clearing unit, data stream reading unit, oscilloscope unit, printer unit or endoscope unit .
  • the above-mentioned target functional unit is a vehicle identification unit;
  • the above-mentioned step of executing the function corresponding to the target functional unit and obtaining the diagnostic information of the vehicle includes: the terminal device sends a vehicle identification instruction to the lower computer;
  • the vehicle's vehicle identification code is obtained through the vehicle's electronic control unit;
  • the lower computer sends the vehicle identification code to the terminal device;
  • the terminal device determines the vehicle model information corresponding to the vehicle identification code, and uses the vehicle model information as the vehicle's diagnostic information.
  • the step for the terminal device to determine the vehicle type information corresponding to the vehicle identification code includes: if the vehicle type information corresponding to the vehicle identification code is stored in the database, the terminal equipment determines the vehicle type information corresponding to the vehicle identification code based on the database information; if the vehicle type information corresponding to the vehicle identification code is not stored in the database, the terminal device obtains the vehicle type information corresponding to the vehicle identification code input by the user, and saves the vehicle type information corresponding to the vehicle identification code input by the user in in the database.
  • the lower computer responds to the fault code reading instruction and obtains the vehicle fault code of the vehicle through the vehicle's electronic control unit; the lower computer sends the vehicle fault code to the terminal device as the vehicle's diagnostic information; the above target functional unit is the fault code clearing unit; the above The steps of executing the function corresponding to the target functional unit and obtaining the vehicle's diagnostic information include: the terminal device sends a fault code clearing instruction to the lower computer; the lower computer responds to the fault code clearing instruction and clears the vehicle's vehicle fault code through the vehicle's electronic control unit; The lower computer returns the vehicle fault code clearing result to the terminal device as vehicle diagnostic information.
  • the functional unit is an oscilloscope unit; the above-mentioned steps of executing the function corresponding to the target functional unit and obtaining the diagnostic information of the vehicle include: the terminal device draws a waveform diagram based on the data flow, and uses the waveform diagram as the diagnostic information of the vehicle.
  • the above-mentioned target functional unit is a printer unit; the above-mentioned step of executing the function corresponding to the target functional unit and obtaining the diagnostic information of the vehicle includes: generating print data based on the diagnostic information of the vehicle; sending the print data to a printer that is communicatively connected to the terminal device, so that the printer can perform a printing operation based on the printing data.
  • the above-mentioned target functional unit is an endoscope unit;
  • the above-mentioned step of executing the function corresponding to the target function unit and obtaining the diagnostic information of the vehicle includes: the terminal device sends an endoscope instruction to the lower computer;
  • the slave computer responds to the endoscope command and obtains the vehicle's video stream through the vehicle's electronic control unit; the slave computer sends the video stream to the terminal device as the vehicle's diagnostic information; the terminal device monitors the video stream returned by the slave computer.
  • embodiments of the present application also provide a calling device for a diagnostic module, which is applied to a terminal device.
  • the terminal device is communicatively connected to a lower computer of the vehicle; the terminal device is provided with a diagnostic module, and the diagnostic module is encapsulated with multiple functional units.
  • the module is provided with a calling function; the device includes: a diagnostic instruction acquisition module, used to obtain the diagnostic instruction input by the user, and determine the target functional unit corresponding to the diagnostic instruction; a functional unit calling module, used to call the target based on the calling function corresponding to the target functional unit Functional unit; diagnostic information acquisition module, used to execute the function corresponding to the target functional unit and obtain vehicle diagnostic information.
  • embodiments of the present application also provide a calling system for a diagnostic module, which includes: a terminal device, a lower computer of the vehicle, and an electronic control unit of the vehicle; the terminal device is used to execute the above calling method of the diagnostic module.
  • Embodiments of the present application provide a method, device and system for calling a diagnostic module.
  • the diagnostic module of a terminal device is encapsulated with multiple functional units.
  • the terminal device can determine the target functional unit corresponding to the diagnostic instruction input by the user; the calling target Mark the functional unit and execute the function corresponding to the target functional unit to obtain the vehicle's diagnostic information.
  • all functional units can be encapsulated in the diagnostic module, so that all scheduling is self-implemented and executed by the diagnostic module. Developers do not need to care about the specific implementation logic inside the diagnostic module, and only need to call the calling function exposed by the diagnostic module. , all diagnostic logic can be completed, thereby improving software development efficiency and facilitating software version maintenance.
  • Figure 1 is a flow chart of a calling method of a diagnostic module provided by an embodiment of the present application
  • Figure 2 is a schematic diagram of a calling method of a diagnostic module provided by an embodiment of the present application
  • Figure 3 is a flow chart of another calling method of a diagnostic module provided by an embodiment of the present application.
  • Figure 4 is a schematic structural diagram of a calling system for a diagnostic module provided by an embodiment of the present application
  • Figure 5 is a schematic structural diagram of a calling device for a diagnostic module provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • VIN numbers Vehicle Identification Number, vehicle identification number
  • ECU Electronic Control Unit, electronic control unit programming, data flow, etc.
  • embodiments of the present application provide a calling method, device and system for a diagnostic module, which can improve software development efficiency and facilitate software version maintenance.
  • the embodiment of the present application provides a calling method of a diagnostic module, which is applied to a terminal device.
  • the terminal device is communicated with a lower computer of the vehicle; the terminal device is provided with a diagnostic module, the diagnostic module is encapsulated with multiple functional units, and the diagnostic module is provided with a calling function. .
  • the terminal device in this embodiment can be a mobile phone, a computer, a tablet, or other device with human-computer interaction and communication functions, and the lower computer of the vehicle can communicate with the terminal device.
  • the terminal device can be equipped with a diagnostic module, such as SDK (Software Development Kit). Multiple functional units can be set up in the SDK, and each functional unit can perform different functions, such as: vehicle identification system based on machine learning, reading car fault codes, clearing fault codes, reading data streams, oscilloscopes, printers, and endoscopic Mirror etc.
  • the calling method of the diagnostic module includes the following steps:
  • Step S102 Obtain the diagnosis instruction input by the user and determine the target functional unit corresponding to the diagnosis instruction.
  • this embodiment discloses a vehicle identification library that integrates machine learning, reading automobile fault codes, clearing automobile fault codes, reading data streams, oscilloscopes, printers, internal Looking Glass as an integrated SDK. Developers only need to care about the development of the business logic layer. To implement specific functions, they only need to call the methods exposed by the SDK to complete the required functions. This not only makes it easy for developers to call, but also protects the integrity of the diagnostic module code, making it difficult to be modified by developers who collaborate on the development. It also ensures that the interfaces developed by different people and after entering the diagnostic function remain unified.
  • this embodiment can uniformly encapsulate the machine learning-based vehicle identification system, read automobile fault codes, "clear fault codes, read data streams,” wave detectors, printers, endoscopes and other functions, and set them after the encapsulation is completed.
  • a unified interface API is provided to facilitate calls by the APP business layer), and the required function packages can be formed in the SDK.
  • the user can input diagnostic instructions through the APP (Application, Application) of the terminal device.
  • APP Application, Application
  • the functional unit corresponding to the diagnostic instruction is called the target functional unit.
  • Step S104 Call the target functional unit based on the calling function corresponding to the target functional unit.
  • the terminal device can call the functional unit in the SDK by calling functions. Therefore, after the target functional unit is determined, the target functional unit can also be called based on the calling function corresponding to the target functional unit.
  • Step S106 Execute the function corresponding to the target functional unit to obtain vehicle diagnostic information.
  • the function corresponding to the target function unit can be executed.
  • the target function unit can obtain the diagnostic information of the vehicle and send the diagnostic information to the APP.
  • the target functional unit can obtain diagnostic information through the lower computer, and the lower computer reads the diagnostic information through the vehicle's ECU.
  • the entrances of the functional units can be unified.
  • all scheduling can be self-implemented and executed by the SDK. Developers do not need to care about the specific internal implementation logic. , you only need to call the functions exposed by the SDK to complete all the logic of diagnosis.
  • An embodiment of the present application provides a method for calling a diagnostic module.
  • the diagnostic module of a terminal device is encapsulated with multiple functional units.
  • the terminal device can determine the target functional unit corresponding to the diagnostic instruction input by the user; call the target functional unit and execute the target functional unit
  • the corresponding function obtains vehicle diagnostic information.
  • all functional units can be encapsulated in the diagnostic module, so that all scheduling is self-implemented and executed by the diagnostic module. Developers do not need to care about the specific implementation logic inside the diagnostic module, and only need to call the calling function exposed by the diagnostic module. , all diagnostic logic can be completed, thereby improving software development efficiency and facilitating software version maintenance.
  • This embodiment provides another method of calling a diagnostic module. This method is implemented on the basis of the above embodiment.
  • Figure 3 is a flow chart of another method of calling a diagnostic module.
  • the diagnostic module in this embodiment The calling method includes the following steps:
  • Step S302 Obtain the diagnosis instruction input by the user and determine the target functional unit corresponding to the diagnosis instruction.
  • Step S304 Call the target functional unit based on the calling function corresponding to the target functional unit.
  • Step S306 Execute the function corresponding to the target functional unit, send instructions to the lower computer and receive the vehicle diagnostic information returned by the lower computer.
  • the functional unit in this embodiment includes at least one of the following: a vehicle identification unit, a fault code reading unit, a fault code clearing unit, a data stream reading unit, an oscilloscope unit, a printer unit, or an endoscope unit.
  • the target functional unit is the vehicle identification unit:
  • the terminal device sends a vehicle identification instruction to the lower computer; the lower computer responds to the vehicle identification instruction and obtains the vehicle identification code of the vehicle through the electronic control unit of the vehicle; the lower computer sends the vehicle identification code to the terminal device; the terminal device determines the vehicle identification code correspondence
  • the vehicle model information is used as vehicle diagnostic information.
  • the vehicle identification unit in this embodiment may be a machine learning-based vehicle identification unit.
  • the business layer of the APP can call the SDK and send vehicle identification instructions to the host computer.
  • the slave computer responds to the vehicle identification command and reads the VIN code through the vehicle's ECU, and the slave computer sends the read VIN code to the terminal device.
  • the terminal device determines the vehicle type information corresponding to the vehicle identification code based on the database; if the vehicle type information corresponding to the vehicle identification code is not stored in the database, the terminal device obtains the vehicle identification code input by the user Corresponding vehicle model information, and save the vehicle model information corresponding to the vehicle identification code entered by the user in the database.
  • the retrieved vehicle model information can be information as the vehicle model information corresponding to the vehicle identification code. If it does not exist, the user needs to manually enter the vehicle model information corresponding to the vehicle identification code.
  • the vehicle model information manually entered by the user can be bound to the vehicle identification code and uploaded to the database to complete the learning function. After the vehicle identification code is read next time, the user does not need to manually select the vehicle type information.
  • the target functional unit is the fault code reading unit:
  • the terminal device sends a fault code reading instruction to the lower computer; the lower computer responds to the fault code reading instruction and obtains the vehicle fault code of the vehicle through the vehicle's electronic control unit; the lower computer sends the vehicle fault code to the terminal device as a diagnosis of the vehicle information.
  • the APP business layer calls the SDK.
  • the SDK can automatically generate the specified fault code reading instruction and send the fault code reading instruction to the lower computer.
  • the lower computer After receiving the fault code reading instruction, the lower computer reads the vehicle fault code through the vehicle's electronic control unit and returns the vehicle fault code as the vehicle's diagnostic information to the SDK.
  • the SDK returns the diagnostic information to the APP business through the fixed data template.
  • Layer the business layer can process and display data according to business needs.
  • the target functional unit is the fault code clearing unit:
  • the terminal device sends a fault code clearing instruction to the lower computer; the lower computer responds to the fault code clearing instruction and clears the vehicle's vehicle fault code through the vehicle's electronic control unit; the lower computer returns the vehicle fault code clearing result to the terminal device as the vehicle's fault code. diagnostic information.
  • the SDK After getting the fault code, if you need to clear the fault code, you only need to call the cleanDtc() function provided by the SDK.
  • the SDK will internally send a HEX command (ie, the fault code clearing command) to notify the lower computer to clear the vehicle's fault code. .
  • the target functional unit is the data stream reading unit:
  • the terminal device sends a data stream reading instruction to the lower computer; the lower computer responds to the data stream reading instruction and obtains the vehicle's data stream through the vehicle's electronic control unit; the lower computer sends the data stream to the terminal device as the vehicle's diagnostic information; The terminal device monitors the data stream returned by the lower computer;
  • the business logic layer of the APP only needs to call the getDataStream(listener) function provided by the SDK.
  • the SDK will internally send a HEX command (i.e., data stream reading command) to notify the lower computer to read the vehicle data stream information. .
  • the lower computer After obtaining the vehicle's data stream through the vehicle's electronic control unit, the lower computer sends the data stream to the terminal device as the vehicle's diagnostic information.
  • the terminal device can provide a callback listener to monitor the returned data, and the interface can be continuously refreshed according to business needs.
  • the target functional unit is the oscilloscope unit:
  • the terminal device draws a waveform diagram based on the data flow, and uses the waveform diagram as the vehicle's diagnostic information.
  • the business logic layer of the APP only needs to call the get Oscilloscope(tag, listener) function provided by the SDK.
  • the SDK will internally send a HEX command to notify the lower computer to read the data.
  • the callback listener monitors the returned data, and can draw waveforms on the interface according to business needs, and use the waveforms as vehicle diagnostic information.
  • the target functional unit is the printer unit:
  • print data is generated based on the vehicle's diagnostic information; the print data is sent to a printer that is communicatively connected to the terminal device, so that the printer performs a printing operation based on the print data.
  • the target functional unit is the endoscope unit
  • the terminal device sends endoscope instructions to the lower computer
  • the slave computer responds to the endoscope command and obtains the vehicle's video stream through the vehicle's electronic control unit; the slave computer sends the video stream to the terminal device as the vehicle's diagnostic information; the terminal device monitors the video stream returned by the slave computer.
  • the terminal device can call the external getSufView(listener) function of the SDK. Through callback listening, the endoscope unit will push the video stream to the business layer of the APP.
  • the business layer of the APP can process the video stream at the business level according to needs.
  • the above method provided by the embodiment of this application can call the SDK, so that the secondary development engineer does not need to care about the development and maintenance of diagnosis-related functions; in this method, every time a new project is developed, only the SDK needs to be imported to implement All functions of diagnosis; in this method, developers can only use open functions, and functional units will not be tampered with at will; in this method, when multiple functional units are updated, developers only need to upgrade the SDK after merging to upgrade. Updates to all relevant functional units.
  • the above methods provided by the embodiments of this application can allow developers to enter the development state faster and care about the content they care about. Finished projects can be quickly developed based on business needs faster. And multiple platforms can achieve uniformity of data content.
  • FIG. 4 is a schematic structural diagram of a calling system for a diagnostic module.
  • the calling system for the diagnostic module in this embodiment includes: a terminal device, a lower computer of the vehicle and The electronic control unit of the vehicle; the terminal device is used to execute the calling method of the above diagnostic module.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • embodiments of the present application provide a calling device for a diagnostic module, which is applied to a terminal device.
  • the terminal device is communicatively connected to a lower computer of the vehicle; the terminal device is provided with a diagnostic module, and the diagnostic module is encapsulated with multiple functions. Unit, the diagnostic module is set with a calling function.
  • the calling device of the diagnostic module includes:
  • the diagnostic instruction acquisition module 51 is used to obtain the diagnostic instruction input by the user and determine the target functional unit corresponding to the diagnostic instruction;
  • the functional unit calling module 52 is used to call the target functional unit based on the calling function corresponding to the target functional unit;
  • the diagnostic information acquisition module 53 is used to execute the function corresponding to the target functional unit and obtain the diagnostic information of the vehicle.
  • An embodiment of the present application provides a calling device for a diagnostic module.
  • the diagnostic module of a terminal device is encapsulated with multiple functional units.
  • the terminal device can determine the target functional unit corresponding to the diagnostic instruction input by the user; call the target functional unit and execute the target functional unit
  • the corresponding function obtains vehicle diagnostic information.
  • all functional units can be encapsulated in the diagnostic module, so that all scheduling is self-implemented and executed by the diagnostic module. Developers do not need to care about the specific implementation logic inside the diagnostic module, and only need to call the calling function exposed by the diagnostic module. , all diagnostic logic can be completed, thereby improving software development efficiency and facilitating software version maintenance.
  • the above functional units include at least one of the following: vehicle identification unit, fault code reading unit, fault code clearing unit, data stream reading unit, oscilloscope unit, printer unit or endoscope unit.
  • the above-mentioned target functional unit is the vehicle identification unit;
  • the above-mentioned diagnostic information acquisition module is used for the terminal device to send vehicle identification instructions to the lower computer;
  • the lower computer responds to the vehicle identification instruction and obtains the vehicle identification code of the vehicle through the electronic control unit of the vehicle;
  • the lower computer The terminal device sends the vehicle identification code;
  • the terminal device determines the vehicle type information corresponding to the vehicle identification code, and uses the vehicle type information as the vehicle's diagnostic information.
  • the above diagnostic information acquisition module is used to determine the vehicle type information corresponding to the vehicle identification code based on the database if the vehicle identification code is stored in the database; if the vehicle type information corresponding to the vehicle identification code is not stored in the database, the terminal equipment obtains The vehicle type information corresponding to the vehicle identification code input by the user is stored in the database.
  • the above-mentioned target functional unit is a fault code reading unit; the above-mentioned diagnostic information acquisition module is used for the terminal device to send a fault code reading instruction to the lower computer; the lower computer responds to the fault code reading instruction and obtains the vehicle's vehicle information through the vehicle's electronic control unit. Fault code; the lower computer sends the vehicle fault code to the terminal device as the vehicle's diagnostic information; the above target function unit is the fault code clearing unit; the above diagnostic information acquisition module is used for the terminal device to send the fault code clearing instruction to the lower computer; the lower computer responds The fault code clearing command clears the vehicle's vehicle fault code through the vehicle's electronic control unit; the lower computer returns the vehicle fault code clearing result to the terminal device as the vehicle's diagnostic information.
  • the above-mentioned target functional unit is a data stream reading unit; the above-mentioned diagnostic information acquisition module is used for the terminal device to send data stream reading instructions to the lower computer; the lower computer responds to the data stream reading instructions and obtains the vehicle through the vehicle's electronic control unit The data stream; the lower computer sends the data stream to the terminal device as the vehicle's diagnostic information; the terminal device monitors the data stream returned by the lower computer; the above target functional unit is the oscilloscope unit; the above diagnostic information acquisition module is used for the terminal device based on the data stream Draw a waveform graph and use the waveform graph as diagnostic information for the vehicle.
  • the above-mentioned target functional unit is a printer unit; the above-mentioned diagnostic information acquisition module is used to generate print data based on the vehicle's diagnostic information; send the print data to a printer that is communicatively connected to the terminal device, so that the printer performs a printing operation based on the print data.
  • the above-mentioned target functional unit is an endoscope unit; the above-mentioned diagnostic information acquisition module is used for the terminal device to send endoscope instructions to the lower computer; the lower computer responds to the endoscope instruction and obtains the video stream of the vehicle through the electronic control unit of the vehicle; the lower computer The computer sends a video stream to the terminal device as vehicle diagnostic information; the terminal device monitors the video stream returned by the lower computer.
  • An embodiment of the present application also provides an electronic device for running the calling method of the above diagnostic module; see Figure 6 for a schematic structural diagram of an electronic device.
  • the electronic device includes a memory 100 and a processor 101, where the memory 100 is used to store one or more computer instructions, and the one or more computer instructions are executed by the processor 101 to implement the calling method of the above-mentioned diagnostic module.
  • the electronic device shown in FIG. 6 also includes a bus 102 and a communication interface 103.
  • the processor 101, the communication interface 103 and the memory 100 are connected through the bus 102.
  • the memory 100 may include high-speed random access memory (RAM, Random Access Memory), and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
  • RAM random access memory
  • non-volatile memory non-volatile memory
  • the communication connection between the system network element and at least one other network element is realized through at least one communication interface 103 (which can be wired or wireless), and the Internet, wide area network, local network, metropolitan area network, etc. can be used.
  • the bus 102 may be an ISA bus, a PCI bus, an EISA bus, etc.
  • the bus can be divided into address bus, data bus, control bus, etc. For ease of presentation, only one bidirectional arrow is used in Figure 6, but it does not mean that there is only one bus or one type of bus.
  • the processor 101 may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor 101 .
  • the above-mentioned processor 101 can be a general-purpose processor, including a Central Processing Unit (CPU for short), a Network Processor (NP for short), etc.; it can also be a Digital Signal Processor (DSP for short). ), Application Specific Integrated Circuit (ASIC for short), Field-Programmable Gate Array (FPGA for short) or other programmable logic devices, discrete gate or transistor logic devices, and discrete hardware components.
  • CPU Central Processing Unit
  • NP Network Processor
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory 100.
  • the processor 101 reads the information in the memory 100 and completes the steps of the method in the foregoing embodiment in combination with its hardware.
  • Embodiments of the present application also provide a computer-readable storage medium that stores computer-executable instructions.
  • the computer-executable instructions When the computer-executable instructions are called and executed by the processor, the computer-executable instructions prompt the processor to implement
  • the specific implementation of the calling method of the diagnostic module can be found in the method embodiments and will not be described again here.
  • the computer program products of the diagnostic module calling method, device and system provided by the embodiments of the present application include a computer-readable storage medium storing program codes.
  • the instructions included in the program codes can be used to execute the methods in the previous method embodiments. Specifically, For implementation, please refer to the method embodiments and will not be described again here.
  • connection should be understood in a broad sense.
  • it can be a fixed connection or a detachable connection. , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be an internal connection between two components.
  • connection should be understood in a broad sense.
  • it can be a fixed connection or a detachable connection. , or integrally connected; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be an internal connection between two components.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Quality & Reliability (AREA)
  • Test And Diagnosis Of Digital Computers (AREA)

Abstract

本申请提供了一种诊断模块的调用方法、装置和系统。其中，该方法应用于终端设备，终端设备与车辆的下位机通信连接；终端设备设置有诊断模块，诊断模块封装有多个功能单元，诊断模块设置有调用函数；该方法包括：获取用户输入的诊断指令，确定诊断指令对应的目标功能单元；基于目标功能单元对应的调用函数，调用目标功能单元；执行目标功能单元对应的函数，获取车辆的诊断信息。该方式中，功能单元可以全部被封装在诊断模块中，使所有调度都由诊断模块内部自我实现和执行，开发人员不需要关心诊断模块内部具体的实现逻辑，仅需要调用诊断模块公开的调用函数，即可完成诊断的所有逻辑，从而提高软件的开发效率，方便软件版本维护。

Description

诊断模块的调用方法、装置和系统
相关申请的交叉引用
本申请要求于2022年08月03日提交中国国家知识产权局的申请号为202210924376.6、名称为“诊断模块的调用方法、装置和系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及车辆诊断技术领域，尤其是涉及一种诊断模块的调用方法、装置和系统。
背景技术
目前，开发人员在开发车辆的诊断软件时，不同的模块功能必须依附于不同的软件支持，需要导入不同的软件包，才能实现不同的模块功能。因此，单个项目可能要依赖数十个不同功能的软件包，由于单个软件包的功能单一，会导致件维护繁琐、开发效率低，不利于快速开发和软件版本维护。
发明内容
有鉴于此，本申请的目的在于提供一种诊断模块的调用方法、装置和系统，以提高软件的开发效率，方便软件版本维护。
第一方面，本申请实施例提供了一种诊断模块的调用方法，应用于终端设备，终端设备与车辆的下位机通信连接；终端设备设置有诊断模块，诊断模块封装有多个功能单元，诊断模块设置有调用函数；方法包括：获取用户输入的诊断指令，确定诊断指令对应的目标功能单元；基于目标功能单元对应的调用函数，调用目标功能单元；执行目标功能单元对应的函数，获取车辆的诊断信息。
在本申请较佳的实施例中，上述功能单元至少包括以下之一：车辆识别单元、故障码读取单元、故障码清除单元、数据流读取单元、示波器单元、打印机单元或内窥镜单元。
在本申请较佳的实施例中，上述目标功能单元为车辆识别单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备向下位机发送车辆识别指令；下位机响应车辆识别指令，通过车辆的电子控制单元获取车辆的车辆识别码；下位机向终端设备发送车辆识别码；终端设备确定车辆识别码对应的车型信息，将车型信息作为车辆的诊断信息。
在本申请较佳的实施例中，上述终端设备确定车辆识别码对应的车型信息的步骤，包括：如果数据库中存储有车辆识别码对应的车型信息，终端设备基于数据库确定车辆识别码对应的车型信息；如果数据库中没有存储车辆识别码对应的车型信息，终端设备获取用户输入的车辆识别码对应的车型信息，并将用户输入的车辆识别码对应的车型信息保存在 数据库中。
在本申请较佳的实施例中，上述目标功能单元为故障码读取单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备向下位机发送故障码读取指令；下位机响应故障码读取指令，通过车辆的电子控制单元获取车辆的车辆故障码；下位机向终端设备发送车辆故障码作为车辆的诊断信息；上述目标功能单元为故障码清除单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备向下位机发送故障码清除指令；下位机响应故障码清除指令，通过车辆的电子控制单元清除车辆的车辆故障码；下位机向终端设备返回车辆故障码的清除结果作为车辆的诊断信息。
在本申请较佳的实施例中，上述目标功能单元为数据流读取单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备向下位机发送数据流读取指令；下位机响应数据流读取指令，通过车辆的电子控制单元获取车辆的数据流；下位机向终端设备发送数据流作为车辆的诊断信息；终端设备监听下位机回传的数据流；上述目标功能单元为示波器单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备基于数据流绘制波形图，将波形图作为车辆的诊断信息。
在本申请较佳的实施例中，上述目标功能单元为打印机单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：基于车辆的诊断信息生成打印数据；将打印数据发送至与终端设备通信连接的打印机中，以使打印机基于打印数据执行打印操作。
在本申请较佳的实施例中，上述目标功能单元为内窥镜单元；上述执行目标功能单元对应的函数，获取车辆的诊断信息的步骤，包括：终端设备向下位机发送内窥镜指令；下位机响应内窥镜指令，通过车辆的电子控制单元获取车辆的视频流；下位机向终端设备发送视频流作为车辆的诊断信息；终端设备监听下位机回传的视频流。
第二方面，本申请实施例还提供一种诊断模块的调用装置，应用于终端设备，终端设备与车辆的下位机通信连接；终端设备设置有诊断模块，诊断模块封装有多个功能单元，诊断模块设置有调用函数；装置包括：诊断指令获取模块，用于获取用户输入的诊断指令，确定诊断指令对应的目标功能单元；功能单元调用模块，用于基于目标功能单元对应的调用函数，调用目标功能单元；诊断信息获取模块，用于执行目标功能单元对应的函数，获取车辆的诊断信息。
第三方面，本申请实施例还提供一种诊断模块的调用系统，包括：终端设备、车辆的下位机和车辆的电子控制单元；终端设备用于执上述的诊断模块的调用方法。
本申请实施例带来了以下有益效果：
本申请实施例提供的一种诊断模块的调用方法、装置和系统，终端设备的诊断模块封装有多个功能单元，终端设备可以确定用户输入的诊断指令对应的目标功能单元；调用目 标功能单元并执行目标功能单元对应的函数，获取车辆的诊断信息。该方式中，功能单元可以全部被封装在诊断模块中，使所有调度都由诊断模块内部自我实现和执行，开发人员不需要关心诊断模块内部具体的实现逻辑，仅需要调用诊断模块公开的调用函数，即可完成诊断的所有逻辑，从而提高软件的开发效率，方便软件版本维护。
本公开的其他特征和优点将在随后的说明书中阐述，或者，部分特征和优点可以从说明书推知或毫无疑义地确定，或者通过实施本公开的上述技术即可得知。
为使本公开的上述目的、特征和优点能更明显易懂，下文特举较佳实施例，并配合所附附图，作详细说明如下。
附图说明
为了更清楚地说明本申请具体实施方式或现有技术中的技术方案，下面将对具体实施方式或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图是本申请的一些实施方式，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种诊断模块的调用方法的流程图；
图2为本申请实施例提供的一种诊断模块的调用方式的示意图；
图3为本申请实施例提供的另一种诊断模块的调用方法的流程图；
图4为本申请实施例提供的一种诊断模块的调用系统的结构示意图；
图5为本申请实施例提供的一种诊断模块的调用装置的结构示意图；
图6为本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
目前，诊断软件功能大多局本地限于读汽车VIN码(Vehicle Identification Number，车辆识别码)、读汽车故障码、清故障码、ECU(Electronic Control Unit，电子控制单元)编程、数据流等，开发人员在开发车辆的诊断软件时，不同的模块功能必须依附于不同的软件支持，需要导入不同的软件包，才能实现不同的模块功能。因此，单个项目可能要依赖数十个不同功能的软件包，由于单个软件包的功能单一，会导致件维护繁琐、开发效率低，不利于快速开发和软件版本维护。
基于此，本申请实施例提供的一种诊断模块的调用方法、装置和系统，可以提高软件的开发效率，方便软件版本维护。
为便于对本实施例进行理解，首先对本申请实施例所公开的一种诊断模块的调用方法进行详细介绍。
实施例一：
本申请实施例提供一种诊断模块的调用方法，应用于终端设备，终端设备与车辆的下位机通信连接；终端设备设置有诊断模块，诊断模块封装有多个功能单元，诊断模块设置有调用函数。
其中，本实施例的终端设备可以为手机、电脑、平板电脑等具有人机交互与通信功能的设备，车辆的下位机可以与该终端设备进行通信。终端设备中可以设置有诊断模块，例如：SDK(Software Development Kit，软件开发工具包)。在SDK中可以设置有多个功能单元，每个功能单元可以执行不同的功能，例如：基于机器学习车辆识别系统、读汽车故障码、清除故障码、读取数据流、示波器、打印机、内窥镜等。
基于上述描述，参见图1所示的一种诊断模块的调用方法的流程图，该诊断模块的调用方法包括如下步骤：
步骤S102，获取用户输入的诊断指令，确定诊断指令对应的目标功能单元。
参见图2所示的一种诊断模块的调用方式的示意图，本实施例揭示了一种集机器学习的车辆识别库、读汽车故障码、清汽车故障码、读数据流、示波器、打印机、内窥镜为一体的SDK。开发人员只需要关心业务逻辑层的开发，具体的功能实现只需要调用SDK对外暴露的方法即可完成所需功能。这样不仅开发人员调用简单，并且可以保护诊断模块代码的完整性，不易被协同开发的开发人员修改的同时，也保证了不同人员开发，进入诊断功能后的界面保持统一性。
其中，本实施例可以将基于机器学习车辆识别系统、读汽车故障码、“清除故障码、读取数据流、“波器、打印机、内窥镜等功能进行统一封装，封装完毕之后对其设置了统一接口API，以便于APP业务层进行调用)，可以在SDK里形成所需要的功能包。
如图2所示，用户可以通过终端设备的APP(Application，应用程序)输入诊断指令，首先确定诊断指令对应哪一个或几个标功能单元，将诊断指令对应的功能单元称为目标功能单元。
步骤S104，基于目标功能单元对应的调用函数，调用目标功能单元。
如图2所示，终端设备可以通过调用函数调用SDK中的功能单元。因此，在确定目标功能单元之后，也可以基于目标功能单元对应的调用函数调用目标功能单元。
步骤S106，执行目标功能单元对应的函数，获取车辆的诊断信息。
如图2所示，在调用目标功能单元之后，就可以执行目标功能单元对应的功能，目标功能单元可以获取车辆的诊断信息并将该诊断信息发送至APP中。
例如，目标功能单元可以通过下位机获取诊断信息，下位机通过车辆的ECU读取诊断信息。本实施例中通过将多个功能单元封装进诊断模块中，可以统一功能单元的入口，通过封装蓝牙串口指令使所有调度都由SDK内部自我实现和执行，开发人员不需要关心内部具体的实现逻辑，仅需要调用SDK公开的函数，即可完成诊断的所有逻辑。
本申请实施例提供的一种诊断模块的调用方法，终端设备的诊断模块封装有多个功能单元，终端设备可以确定用户输入的诊断指令对应的目标功能单元；调用目标功能单元并执行目标功能单元对应的函数，获取车辆的诊断信息。该方式中，功能单元可以全部被封装在诊断模块中，使所有调度都由诊断模块内部自我实现和执行，开发人员不需要关心诊断模块内部具体的实现逻辑，仅需要调用诊断模块公开的调用函数，即可完成诊断的所有逻辑，从而提高软件的开发效率，方便软件版本维护。
实施例二：
本实施例提供了另一种诊断模块的调用方法，该方法在上述实施例的基础上实现，如图3所示的另一种诊断模块的调用方法的流程图，本实施例中的诊断模块的调用方法包括如下步骤：
步骤S302，获取用户输入的诊断指令，确定诊断指令对应的目标功能单元。
步骤S304，基于目标功能单元对应的调用函数，调用目标功能单元。
步骤S306，执行目标功能单元对应的函数，向下位机发送指令并接收下位机返回的车辆的诊断信息。
本实施例中的功能单元至少包括以下之一：车辆识别单元、故障码读取单元、故障码清除单元、数据流读取单元、示波器单元、打印机单元或内窥镜单元。
(1)目标功能单元为车辆识别单元：
具体地，终端设备向下位机发送车辆识别指令；下位机响应车辆识别指令，通过车辆的电子控制单元获取车辆的车辆识别码；下位机向终端设备发送车辆识别码；终端设备确定车辆识别码对应的车型信息，将车型信息作为车辆的诊断信息。
本实施例的车辆识别单元可以为基于机器学习的车辆识别单元。APP的业务层可以调用SDK，向下位机发送车辆识别指令。下位机响应车辆识别指令，通过车辆的ECU读取VIN码，下位机将读取的VIN码发送至终端设备。
其中，如果数据库中存储有车辆识别码对应的车型信息，终端设备基于数据库确定车辆识别码对应的车型信息；如果数据库中没有存储车辆识别码对应的车型信息，终端设备获取用户输入的车辆识别码对应的车型信息，并将用户输入的车辆识别码对应的车型信息保存在数据库中。
在数据库中检索VIN码是否存在对应的车型信息，若存在，则可以将检索到的车型信 息作为该车辆识别码对应的车型信息。若不存在，则需要用户手动输入该车辆识别码对应的车型信息。
之后可以将用户手动输入的车型信息与该车辆识别码绑定，并上传至数据库，完成学习功能，在下次读取该车辆识别码后，无需用户再进行手动选择车型信息。
(2)目标功能单元为故障码读取单元：
具体地，终端设备向下位机发送故障码读取指令；下位机响应故障码读取指令，通过车辆的电子控制单元获取车辆的车辆故障码；下位机向终端设备发送车辆故障码作为车辆的诊断信息。
APP业务层调用SDK，通过调用getDTC()函数，SDK内部可以将自动生成指定的故障码读取指令并且将故障码读取指令发送至下位机。
下位机接收到故障码读取指令后，通过车辆的电子控制单元读取车辆故障码后，将车辆故障码作为车辆的诊断信息返回给SDK，SDK通过固数据模板将诊断信息返会给APP业务层，业务层可以根据业务需求进行数据在处理和展示。
(3)目标功能单元为故障码清除单元：
具体地，终端设备向下位机发送故障码清除指令；下位机响应故障码清除指令，通过车辆的电子控制单元清除车辆的车辆故障码；下位机向终端设备返回车辆故障码的清除结果作为车辆的诊断信息。
在得到故障码后，如果需要进行清除故障码，仅需要调用SDK对外提供的cleanDtc()函数，SDK内部将会发送HEX指令(即故障码清除指令)通知下位机对车辆的故障码进行清码。
(4)目标功能单元为数据流读取单元：
具体地，终端设备向下位机发送数据流读取指令；下位机响应数据流读取指令，通过车辆的电子控制单元获取车辆的数据流；下位机向终端设备发送数据流作为车辆的诊断信息；终端设备监听下位机回传的数据流；
如果需要读取车辆数据流，APP的业务逻辑层仅需要调用SDK对外提供的getDataStream(listener)函数，SDK内部将会发送HEX指令(即数据流读取指令)通知下位机读取车辆数据流信息。
通过车辆的电子控制单元获取车辆的数据流之后，下位机向终端设备发送数据流作为车辆的诊断信息。终端设备可以提供回调listener对回传的数据进行监听，可根据业务需求，进行界面不断刷新。
(5)目标功能单元为示波器单元：
具体地，终端设备基于数据流绘制波形图，将波形图作为车辆的诊断信息。
如果需要读取车辆数据流，APP的业务逻辑层仅需要调用SDK对外提供的get Oscilloscope(tag,listener)函数，SDK内部将会发送HEX指令通知下位机读取数据，会根据标签类型，并且提供回调listener对回传的数据进行监听，并可以根据业务需求，进行界面绘制波形图，将波形图作为车辆的诊断信息。
(6)目标功能单元为打印机单元：
具体地，基于车辆的诊断信息生成打印数据；将打印数据发送至与终端设备通信连接的打印机中，以使打印机基于打印数据执行打印操作。
根据之前的步骤返回的车辆的诊断信息，如果需要生成报告并且通过外挂打印机打印，可调用SDK对外的startPrint(obj)函数，按约定数据格式提供的obj文件格式传输给打印机单元，打印机单元会自动打包数据，并通过二进制流传送至打印机，并按照指定格式打印。
(7)目标功能单元为内窥镜单元；
具体地，终端设备向下位机发送内窥镜指令；
下位机响应内窥镜指令，通过车辆的电子控制单元获取车辆的视频流；下位机向终端设备发送视频流作为车辆的诊断信息；终端设备监听下位机回传的视频流。
终端设备可调用SDK对外的getSufView(listener)函数，通过回调监听，内窥镜单元会向APP的业务层推送视频流，APP的业务层根据需求可对视频流进行业务层面处理。
本申请实施例提供的上述方法，可以通过调用SDK，使二次开发的工程师不需要关心诊断相关功能的开发和维护；该方式中，每一次开发新项目，仅需将SDK导入，即可实现诊断的所有功能；该方式中，开发人员只能使用开放函数，功能单元不会被随意篡改；该方式中，多个功能单元进行版本更新时，合并完开发人员仅需要升级SDK，即可升级所有相关功能单元的更新。
综上，本申请实施例提供的上述方法可以让开发人员更快的进入开发状态，关心自己所关心的内容。可以更快地根据业务需求快速开发成品项目。并且多平台可以做到数据内容的统一性。
实施例三：
本实施例提供了一种诊断模块的调用系统，如图4所示的一种诊断模块的调用系统的结构示意图，本实施例中的诊断模块的调用系统包括：终端设备、车辆的下位机和车辆的电子控制单元；终端设备用于执行上述诊断模块的调用方法。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的诊断模块的调用系统的具体工作过程，可以参考前述的诊断模块的调用方法的实施例中的对应过程，在此不再赘述。
实施例四：
对应于上述方法实施例，本申请实施例提供了一种诊断模块的调用装置，应用于终端设备，终端设备与车辆的下位机通信连接；终端设备设置有诊断模块，诊断模块封装有多个功能单元，诊断模块设置有调用函数。参见图5所示的一种诊断模块的调用装置的结构示意图，该诊断模块的调用装置包括：
诊断指令获取模块51，用于获取用户输入的诊断指令，确定诊断指令对应的目标功能单元；
功能单元调用模块52，用于基于目标功能单元对应的调用函数，调用目标功能单元；
诊断信息获取模块53，用于执行目标功能单元对应的函数，获取车辆的诊断信息。
本申请实施例提供的一种诊断模块的调用装置，终端设备的诊断模块封装有多个功能单元，终端设备可以确定用户输入的诊断指令对应的目标功能单元；调用目标功能单元并执行目标功能单元对应的函数，获取车辆的诊断信息。该方式中，功能单元可以全部被封装在诊断模块中，使所有调度都由诊断模块内部自我实现和执行，开发人员不需要关心诊断模块内部具体的实现逻辑，仅需要调用诊断模块公开的调用函数，即可完成诊断的所有逻辑，从而提高软件的开发效率，方便软件版本维护。
上述功能单元至少包括以下之一：车辆识别单元、故障码读取单元、故障码清除单元、数据流读取单元、示波器单元、打印机单元或内窥镜单元。
上述目标功能单元为车辆识别单元；上述诊断信息获取模块，用于终端设备向下位机发送车辆识别指令；下位机响应车辆识别指令，通过车辆的电子控制单元获取车辆的车辆识别码；下位机向终端设备发送车辆识别码；终端设备确定车辆识别码对应的车型信息，将车型信息作为车辆的诊断信息。
上述诊断信息获取模块，用于如果数据库中存储有车辆识别码对应的车型信息，终端设备基于数据库确定车辆识别码对应的车型信息；如果数据库中没有存储车辆识别码对应的车型信息，终端设备获取用户输入的车辆识别码对应的车型信息，并将用户输入的车辆识别码对应的车型信息保存在数据库中。
上述目标功能单元为故障码读取单元；上述诊断信息获取模块，用于终端设备向下位机发送故障码读取指令；下位机响应故障码读取指令，通过车辆的电子控制单元获取车辆的车辆故障码；下位机向终端设备发送车辆故障码作为车辆的诊断信息；上述目标功能单元为故障码清除单元；上述诊断信息获取模块，用于终端设备向下位机发送故障码清除指令；下位机响应故障码清除指令，通过车辆的电子控制单元清除车辆的车辆故障码；下位机向终端设备返回车辆故障码的清除结果作为车辆的诊断信息。
上述目标功能单元为数据流读取单元；上述诊断信息获取模块，用于终端设备向下位机发送数据流读取指令；下位机响应数据流读取指令，通过车辆的电子控制单元获取车辆 的数据流；下位机向终端设备发送数据流作为车辆的诊断信息；终端设备监听下位机回传的数据流；上述目标功能单元为示波器单元；上述诊断信息获取模块，用于终端设备基于数据流绘制波形图，将波形图作为车辆的诊断信息。
上述目标功能单元为打印机单元；上述诊断信息获取模块，用于基于车辆的诊断信息生成打印数据；将打印数据发送至与终端设备通信连接的打印机中，以使打印机基于打印数据执行打印操作。
上述目标功能单元为内窥镜单元；上述诊断信息获取模块，用于终端设备向下位机发送内窥镜指令；下位机响应内窥镜指令，通过车辆的电子控制单元获取车辆的视频流；下位机向终端设备发送视频流作为车辆的诊断信息；终端设备监听下位机回传的视频流。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的诊断模块的调用装置的具体工作过程，可以参考前述的诊断模块的调用方法的实施例中的对应过程，在此不再赘述。
实施例五：
本申请实施例还提供了一种电子设备，用于运行上述诊断模块的调用方法；参见图6所示的一种电子设备的结构示意图，该电子设备包括存储器100和处理器101，其中，存储器100用于存储一条或多条计算机指令，一条或多条计算机指令被处理器101执行，以实现上述诊断模块的调用方法。
进一步地，图6所示的电子设备还包括总线102和通信接口103，处理器101、通信接口103和存储器100通过总线102连接。
其中，存储器100可能包含高速随机存取存储器(RAM，Random Access Memory)，也可能还包括非不稳定的存储器(non-volatile memory)，例如至少一个磁盘存储器。通过至少一个通信接口103(可以是有线或者无线)实现该系统网元与至少一个其他网元之间的通信连接，可以使用互联网，广域网，本地网，城域网等。总线102可以是ISA总线、PCI总线或EISA总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图6中仅用一个双向箭头表示，但并不表示仅有一根总线或一种类型的总线。
处理器101可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法的各步骤可以通过处理器101中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器101可以是通用处理器，包括中央处理器(Central Processing Unit，简称CPU)、网络处理器(Network Processor，简称NP)等；还可以是数字信号处理器(Digital Signal Processor，简称DSP)、专用集成电路(Application Specific Integrated Circuit，简称ASIC)、现场可编程门阵列(Field-Programmable Gate Array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步 骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器100，处理器101读取存储器100中的信息，结合其硬件完成前述实施例的方法的步骤。
本申请实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令在被处理器调用和执行时，计算机可执行指令促使处理器实现上述诊断模块的调用方法，具体实现可参见方法实施例，在此不再赘述。
本申请实施例所提供的诊断模块的调用方法、装置和系统的计算机程序产品，包括存储了程序代码的计算机可读存储介质，程序代码包括的指令可用于执行前面方法实施例中的方法，具体实现可参见方法实施例，在此不再赘述。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统和/或装置的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
另外，在本申请实施例的描述中，除非另有明确的规定和限定，术语“安装”、“相连”、“连接”应做广义理解，例如，可以是固定连接，也可以是可拆卸连接，或一体地连接；可以是机械连接，也可以是电连接；可以是直接相连，也可以通过中间媒介间接相连，可以是两个元件内部的连通。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
在本申请的描述中，需要说明的是，术语“中心”、“上”、“下”、“左”、“右”、“竖直”、“水平”、“内”、“外”等指示的方位或位置关系为基于附图所示的方位或位置关系，仅是为了便于描述本申请和简化描述，而不是指示或暗示所指的装置或元件必须具有特定的方位、以特定的方位构造和操作，因此不能理解为对本申请的限制。此外，术语“第一”、“第二”、“第三”仅用于描述目的，而不能理解为指示或暗示相对重要性。
最后应说明的是：以上所述实施例，仅为本申请的具体实施方式，用以说明本申请的技术方案，而非对其限制，本申请的保护范围并不局限于此，尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，其依然可以对前述实施例所记载的技术方案进行修改或可轻易想到变化，或者对其中部分技术特征进行等同替换；而这些修改、变化或者替换，并不使相应技术方案的本质脱离本申请实施例技术方案的精神和范围，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (10)

  1. 一种诊断模块的调用方法，其特征在于，应用于终端设备，所述终端设备与车辆的下位机通信连接；所述终端设备设置有诊断模块，所述诊断模块封装有多个功能单元，所述诊断模块设置有调用函数；所述方法包括：
    获取用户输入的诊断指令，确定所述诊断指令对应的目标功能单元；
    基于所述目标功能单元对应的调用函数，调用所述目标功能单元；
    执行所述目标功能单元对应的函数，获取所述车辆的诊断信息。
  2. 根据权利要求1所述的方法，其特征在于，所述功能单元至少包括以下之一：车辆识别单元、故障码读取单元、故障码清除单元、数据流读取单元、示波器单元、打印机单元或内窥镜单元。
  3. 根据权利要求2所述的方法，其特征在于，所述目标功能单元为所述车辆识别单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备向所述下位机发送车辆识别指令；
    所述下位机响应所述车辆识别指令，通过所述车辆的电子控制单元获取所述车辆的车辆识别码；
    所述下位机向所述终端设备发送所述车辆识别码；
    所述终端设备确定所述车辆识别码对应的车型信息，将所述车型信息作为所述车辆的诊断信息。
  4. 根据权利要求3所述的方法，其特征在于，所述终端设备确定所述车辆识别码对应的车型信息的步骤，包括：
    如果数据库中存储有所述车辆识别码对应的车型信息，所述终端设备基于所述数据库确定所述车辆识别码对应的车型信息；
    如果所述数据库中没有存储所述车辆识别码对应的车型信息，所述终端设备获取用户输入的所述车辆识别码对应的车型信息，并将用户输入的所述车辆识别码对应的车型信息保存在所述数据库中。
  5. 根据权利要求2所述的方法，其特征在于，所述目标功能单元为所述故障码读取单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备向所述下位机发送故障码读取指令；
    所述下位机响应所述故障码读取指令，通过所述车辆的电子控制单元获取所述车辆的车辆故障码；
    所述下位机向所述终端设备发送所述车辆故障码作为所述车辆的诊断信息；
    所述目标功能单元为所述故障码清除单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备向所述下位机发送故障码清除指令；
    所述下位机响应所述故障码清除指令，通过所述车辆的电子控制单元清除所述车辆的车辆故障码；
    所述下位机向所述终端设备返回所述车辆故障码的清除结果作为所述车辆的诊断信息。
  6. 根据权利要求2所述的方法，其特征在于，所述目标功能单元为所述数据流读取单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备向所述下位机发送数据流读取指令；
    所述下位机响应所述数据流读取指令，通过所述车辆的电子控制单元获取所述车辆的数据流；
    所述下位机向所述终端设备发送所述数据流作为所述车辆的诊断信息；
    所述终端设备监听所述下位机回传的所述数据流；
    所述目标功能单元为所述示波器单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备基于所述数据流绘制波形图，将所述波形图作为所述车辆的诊断信息。
  7. 根据权利要求2所述的方法，其特征在于，所述目标功能单元为所述打印机单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    基于所述车辆的诊断信息生成打印数据；
    将所述打印数据发送至与所述终端设备通信连接的打印机中，以使所述打印机基于所述打印数据执行打印操作。
  8. 根据权利要求2所述的方法，其特征在于，所述目标功能单元为所述内窥镜单元；执行所述目标功能单元对应的函数，获取所述车辆的诊断信息的步骤，包括：
    所述终端设备向所述下位机发送内窥镜指令；
    所述下位机响应所述内窥镜指令，通过所述车辆的电子控制单元获取所述车辆的视频流；
    所述下位机向所述终端设备发送所述视频流作为所述车辆的诊断信息；
    所述终端设备监听所述下位机回传的所述视频流。
  9. 一种诊断模块的调用装置，其特征在于，应用于终端设备，所述终端设备与车辆的下位机通信连接；所述终端设备设置有诊断模块，所述诊断模块封装有多个功能单元，所述诊断模块设置有调用函数；所述装置包括：
    诊断指令获取模块，用于获取用户输入的诊断指令，确定所述诊断指令对应的目标功 能单元；
    功能单元调用模块，用于基于所述目标功能单元对应的调用函数，调用所述目标功能单元；
    诊断信息获取模块，用于执行所述目标功能单元对应的函数，获取所述车辆的诊断信息。
  10. 一种诊断模块的调用系统，其特征在于，包括：终端设备、车辆的下位机和所述车辆的电子控制单元；所述终端设备用于执行权利要求1-8任一项所述的诊断模块的调用方法。
PCT/CN2023/091352 2022-08-03 2023-04-27 诊断模块的调用方法、装置和系统 WO2024027240A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210924376.6 2022-08-03
CN202210924376.6A CN114995862B (zh) 2022-08-03 2022-08-03 诊断模块的调用方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2024027240A1 true WO2024027240A1 (zh) 2024-02-08

Family

ID=83022604

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/091352 WO2024027240A1 (zh) 2022-08-03 2023-04-27 诊断模块的调用方法、装置和系统

Country Status (2)

Country Link
CN (1) CN114995862B (zh)
WO (1) WO2024027240A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117880061A (zh) * 2024-03-11 2024-04-12 雅安数字经济运营有限公司 一种数据中心运维监控系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114995862B (zh) * 2022-08-03 2022-11-01 深圳市星卡软件技术开发有限公司 诊断模块的调用方法、装置和系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110333713A (zh) * 2019-08-06 2019-10-15 深圳市瀚智科技有限公司 车辆故障诊断方法及系统
CN113110994A (zh) * 2021-04-19 2021-07-13 深圳市元征科技股份有限公司 一种车辆诊断方法、装置、电子设备及存储介质
CN113885476A (zh) * 2021-10-22 2022-01-04 深圳市元征科技股份有限公司 一种车辆诊断方法及相关装置
US20220188434A1 (en) * 2020-05-29 2022-06-16 Launch Tech Co., Ltd Vehicle diagnosis method, server and diagnosis device
CN114995862A (zh) * 2022-08-03 2022-09-02 深圳市星卡软件技术开发有限公司 诊断模块的调用方法、装置和系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6907445B2 (en) * 2001-02-12 2005-06-14 International Truck Intellectual Property Company, Llc Consistent application programming interface for communicating with disparate vehicle network classes
US8934866B2 (en) * 2009-04-20 2015-01-13 Aetherpal Inc. System to assist a mobile device subscriber to perform self-diagnosis of the mobile device
JP6885226B2 (ja) * 2017-07-03 2021-06-09 株式会社デンソー 電子制御装置
CN111078326A (zh) * 2019-12-28 2020-04-28 深圳市元征科技股份有限公司 一种功能模块的调用方法、装置及设备
CN112181538B (zh) * 2020-09-27 2023-05-30 深圳市元征科技股份有限公司 诊断流程执行方法、装置、设备及存储介质
CN113778557B (zh) * 2021-09-15 2024-04-26 深圳市元征软件开发有限公司 车辆诊断软件配置方法、装置、服务器及存储介质
CN114779740A (zh) * 2022-04-22 2022-07-22 重庆长安汽车股份有限公司 一种车辆故障远程诊断系统及方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110333713A (zh) * 2019-08-06 2019-10-15 深圳市瀚智科技有限公司 车辆故障诊断方法及系统
US20220188434A1 (en) * 2020-05-29 2022-06-16 Launch Tech Co., Ltd Vehicle diagnosis method, server and diagnosis device
CN113110994A (zh) * 2021-04-19 2021-07-13 深圳市元征科技股份有限公司 一种车辆诊断方法、装置、电子设备及存储介质
CN113885476A (zh) * 2021-10-22 2022-01-04 深圳市元征科技股份有限公司 一种车辆诊断方法及相关装置
CN114995862A (zh) * 2022-08-03 2022-09-02 深圳市星卡软件技术开发有限公司 诊断模块的调用方法、装置和系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117880061A (zh) * 2024-03-11 2024-04-12 雅安数字经济运营有限公司 一种数据中心运维监控系统
CN117880061B (zh) * 2024-03-11 2024-05-17 雅安数字经济运营有限公司 一种数据中心运维监控系统

Also Published As

Publication number Publication date
CN114995862A (zh) 2022-09-02
CN114995862B (zh) 2022-11-01

Similar Documents

Publication Publication Date Title
WO2024027240A1 (zh) 诊断模块的调用方法、装置和系统
US11934352B2 (en) Card rendering method and electronic device
WO2019218458A1 (zh) 一种应用程序测试方法、装置、移动终端及介质
CN111428462A (zh) 通讯协议模板构建的方法及终端设备
WO2021082969A1 (zh) 核间数据处理方法、系统、片上系统以及电子设备
CN1926525A (zh) 多突发协议设备控制器
CN112579508A (zh) 一种数据处理方法、数据处理装置、设备及存储介质
WO2022041720A1 (zh) 一种基于uds的通信方法、ecu及上位机
WO2022161059A1 (zh) 一种模型运行方法及相关装置
CN110213092A (zh) 混合云的资源访问方法、平台管理设备、存储介质及装置
CN110147257A (zh) 终端设备侧的驱动程序的处理方法、装置和设备
CN111444609A (zh) 数据处理方法及仿真系统
WO2012048491A1 (zh) 面向ic装备控制软件的gui平台化实现方法
CN113065779B (zh) 数据处理方法、装置和电子设备
CN116737016B (zh) 触控数据扫描的控制方法、装置、计算机设备和存储介质
CN114040189A (zh) 多媒体测试方法、装置、存储介质及电子设备
CN113010122A (zh) 图像形成装置监控装置、方法、系统和存储介质
CN112486807A (zh) 一种压力测试方法、装置、电子设备和可读存储介质
CN109725621A (zh) 一种基于1553b总线和can总线的二级总线程序在线烧写方法
CN115729729A (zh) 一种功耗异常定位方法、系统、终端设备和存储介质
CN113766216A (zh) 一种视频模块的验证方法及验证系统
CN111949510B (zh) 测试处理方法、装置、电子设备及可读存储介质
CN110287754A (zh) 车辆信息管理方法、装置和计算机可读存储介质
CN111371799A (zh) Mctp控制器收发数据的控制方法、装置及设备
JP3647827B2 (ja) 無線印刷インターフェース・キットおよび方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23848951

Country of ref document: EP

Kind code of ref document: A1