[go: up one dir, main page]

WO2018103252A1 - Procédé et appareil de développement secondaire destinés à un dispositif de diagnostic - Google Patents

Procédé et appareil de développement secondaire destinés à un dispositif de diagnostic Download PDF

Info

Publication number
WO2018103252A1
WO2018103252A1 PCT/CN2017/081806 CN2017081806W WO2018103252A1 WO 2018103252 A1 WO2018103252 A1 WO 2018103252A1 CN 2017081806 W CN2017081806 W CN 2017081806W WO 2018103252 A1 WO2018103252 A1 WO 2018103252A1
Authority
WO
WIPO (PCT)
Prior art keywords
function
diagnostic device
configuration information
diagnostic
secondary development
Prior art date
Application number
PCT/CN2017/081806
Other languages
English (en)
Chinese (zh)
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 WO2018103252A1 publication Critical patent/WO2018103252A1/fr

Links

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0218—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults
    • G05B23/0256—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterised by the fault detection method dealing with either existing or incipient faults injecting test signals and analyzing monitored process response, e.g. injecting the test signal while interrupting the normal operation of the monitored system; superimposing the test signal onto a control signal during normal operation of the monitored system
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/24—Pc safety
    • G05B2219/24065—Real time diagnostics

Definitions

  • the present invention relates to the field of automobile technology, and in particular, to a secondary development method and device for a diagnostic device.
  • OBD On-Board Diagnostic
  • the user can only view the current data during the use, but cannot manage the data processing. For example, the user may wish to summarize the mileage, time and fuel consumption of each trip. Waveforms or tables are presented, but current OBD systems cannot implement such functions.
  • the main object of the present invention is to provide a secondary development method and device for a diagnostic device, which aims to solve the problem that the OBD system function on the market is fixed and the user cannot modify the diagnostic function according to his own needs.
  • a secondary development method for a diagnostic device includes the following steps:
  • the calling instruction refers to calling the function of the h header file corresponding to the function and/or the dll file of the dynamic link library as a function pointer.
  • the step of writing configuration information to the diagnostic device through the SDK packet to add a preset function to the diagnostic device includes:
  • the configuration information of the preset function is encapsulated as a function into the dll file in the dynamic link library, and the call interface is generated and saved as a h header file.
  • the step of writing configuration information to the diagnostic device through the SDK packet to add a preset function to the diagnostic device includes:
  • the interface configured through the SDK package adds configuration information of the new function to the storage location of the configuration information of the original function.
  • the step of writing configuration information to the diagnostic device through the SDK packet to add a preset function to the diagnostic device includes:
  • the interface configured through the SDK package deletes the configuration information in the storage location of the configuration information of the original function.
  • the step of writing configuration information to the diagnostic device through the SDK packet to add a preset function to the diagnostic device includes:
  • the interface configured through the SDK package modifies the configuration information in the storage location of the configuration information of the original function.
  • the method further includes:
  • the received ECU data is flashed to the ECU data to be erased by the interface configured by the SDK package.
  • the ECU data flashing manner comprises: local refresh, network refresh or CD refresh.
  • the functions of the SDK package include:
  • the steps include:
  • the acquired data is sent to the account associated with the device to be diagnosed.
  • the present invention further provides a secondary development device for a diagnostic device, including:
  • connection module for connecting the SDK package with the diagnostic device
  • a processing module configured to: when a call instruction is detected, invoke a preset function added by the diagnostic device to acquire data corresponding to the call instruction, and output and save the data in an output form corresponding to the preset function;
  • the calling instruction refers to calling the function of the h header file corresponding to the function and/or the dll file of the dynamic link library as a function pointer.
  • the writing module is further configured to encapsulate the configuration information of the preset function as a function into a dll file in the dynamic link library, and generate a call interface to save as a h header file.
  • the writing module comprises:
  • a writing unit configured to write configuration information of the newly added function to the diagnostic device through the SDK package
  • the adding unit is used to add configuration information of the new function to the storage location of the configuration information of the original function by the interface configured by the SDK package.
  • the writing module comprises:
  • a writing unit configured to write configuration information of the deleting function to the diagnostic device through the SDK package
  • the deletion unit is configured to delete the configuration information in the storage location of the configuration information of the original function by using the interface configured by the SDK package.
  • the writing module comprises:
  • a writing unit configured to write configuration information of the modified function to the diagnostic device through the SDK package
  • the modification unit is configured to modify the configuration information in the storage location of the configuration information of the original function by using the interface configured by the SDK package.
  • the ECU data flashing manner comprises: local refresh, network refresh or CD refresh.
  • the secondary development device of the diagnostic device further includes:
  • the brush writing module is configured to perform ECU data writing to the device to be flashed through the interface configured by the SDK package.
  • the functions of the SDK package include:
  • the secondary development device of the diagnostic device further includes:
  • a sending module configured to send the acquired data to an account associated with the device to be diagnosed.
  • the invention connects the SDK package with the diagnostic device; writes the configuration information to the diagnostic device through the SDK package to add a preset function to the diagnostic device; when the call instruction is detected, the preset function added in the diagnostic device is acquired and acquired. And the data corresponding to the calling instruction outputs and saves the data in an output form corresponding to the preset function; wherein the calling instruction refers to a dll file of a h header file and/or a dynamic link library corresponding to the function Called as a function pointer.
  • the diagnostic function of the diagnostic device is modified by the SDK package to realize the functions that the user wishes to diagnose the device.
  • FIG. 1 is a schematic flow chart of a first embodiment of a secondary development method of a diagnostic device according to the present invention
  • FIG. 2 is a schematic flow chart of a refinement of an embodiment of step S20 of FIG. 1;
  • FIG. 3 is a schematic flow chart of a second embodiment of a secondary development method of a diagnostic device according to the present invention.
  • FIG. 4 is a schematic flow chart of a third embodiment of a secondary development method of a diagnostic device according to the present invention.
  • FIG. 5 is a schematic diagram of functional modules of a first embodiment of a secondary development device of a diagnostic device according to the present invention.
  • FIG. 6 is a schematic diagram of a refinement function module of an embodiment of the write module of FIG. 5;
  • FIG. 7 is a schematic diagram of functional modules of a second embodiment of a secondary development device of the diagnostic device of the present invention.
  • FIG. 8 is a schematic diagram of functional modules of a third embodiment of a secondary development device for a diagnostic device according to the present invention.
  • the invention provides a secondary development method of a diagnostic device.
  • FIG. 1 is a schematic flow chart of a first embodiment of a secondary development method of a diagnostic device according to the present invention.
  • the secondary development method of the diagnostic device includes:
  • Step S10 connecting the SDK package with the diagnostic device
  • the Diagnostic, OBD uses on-board diagnostics (On-Board)
  • the Diagnostic, OBD system is connected with an onboard diagnostic interface on the vehicle to collect data of various sensors to diagnose the vehicle fault; the OBD system monitors the operating condition of the engine and the working state of the exhaust aftertreatment system at any time, and if it is found, it may cause excessive emissions. In the case of the situation, a warning will be issued immediately. When the system fails, the fault light or check engine warning light is on, and the OBD system will store the fault information in the memory.
  • the standard diagnostic instrument and diagnostic interface can read the relevant information in the form of fault code.
  • the maintenance personnel can quickly and accurately determine the nature and location of the fault.
  • the fault is displayed in the form of a fault code, which has certain requirements on the user's professional knowledge.
  • the user needs to know the fault type corresponding to the fault code, and the data acquired each time can only be viewed, and the user cannot process the data.
  • the user may wish to summarize the data such as the mileage, time and fuel consumption of each trip, and present it in the form of a waveform diagram or a table; in order to facilitate the ordinary user to read the information sent by the OBD system, it can also adapt
  • the need for different users to adjust the diagnostic device diagnostic function requires adjustment of the information output by the OBD system.
  • SDK Software Development Kit, SDK
  • SDK software development kit
  • Step S20 writing configuration information to the diagnostic device through the SDK package, to add a preset function to the diagnostic device;
  • the user may wish to summarize the data such as the mileage, time and fuel consumption of each trip, and present it in the form of a waveform diagram or a table.
  • the configuration information of the function can be written to the diagnostic device through the SDK package, and the user wants the diagnostic device to have the configuration information.
  • the function can be realized by writing the configuration information of the preset function to the diagnostic device through the SDK package.
  • step S20 includes:
  • the configuration information of the preset function is encapsulated as a function into the dll file in the dynamic link library, and the call interface is generated and saved as a h header file.
  • API Application Programming Interface Interface
  • the application calls the API of the operating system.
  • the command (action) that causes the operating system to execute the application.
  • the dll (Dynamic Link Library) file contains the API The execution code of the function, and the API function in the dll file must be used by the declaration of the API function (h header file) and its import library (lib file).
  • the SDK package encapsulates the configuration information of the preset function as an API function into the dll file in the dynamic link library, and generates a call interface to save as a h header file.
  • the API function needs to be called (ie, the preset function is executed)
  • the head is passed.
  • the file finds the corresponding dll file, and the linker calls the API function from the dll file to perform the preset function.
  • FIG. 2 is a schematic diagram of a refinement process of an embodiment of step S20 of FIG. 1.
  • the step S20 includes:
  • Step S21 writing configuration information of the newly added function to the diagnostic device through the SDK package;
  • step S22 the interface configured by the SDK package adds configuration information of the new function to the storage location of the configuration information of the original function.
  • the preset function may be a new function written in the diagnostic device.
  • the configuration information of the newly added function is written to the diagnostic device through the SDK package; the preset function may also change the original function of the diagnostic device ( Modifying the original function), the interface configured by the SDK package adds configuration information of the new function in the storage location of the configuration information of the original function, and of course, the configuration information can be deleted and modified in the storage location of the configuration information of the original function, thereby Make the diagnostic device have the features that the user wants to have.
  • Data stream display function Including: normal mode, recording mode; display mode: send data stream to the caller's window, after the window is received, it can be displayed, saved, parsed, etc. in the interface; in the data recording mode, the saved data stream can be saved, transmitted and re-selected.
  • 7 Read frozen data frame Reads the frozen data stream recorded by the electronic control unit when the fault occurs.
  • 8 Fault code storage function The read electronic control unit fault code is stored in EXCEL form; it can be edited and sorted; the saved file is stored in a special format.
  • Read electronic control unit information function Displays information such as vehicle VIN, electronic control unit version information, and electronic control unit part number.
  • ECU/TCU, etc. Electronic control unit (ECU/TCU, etc.) reprogramming function
  • ECU/TCU Electronic control unit
  • Network refresh transfer the data required by the service station through the network, and then write the data to the electronic control unit
  • CD refresh store the released refresh data in CD form, using the SDK package
  • the refresh program writes the data from the CD to the electronic control unit.
  • Actuator action test function The system actuators are tested for motion and have a warning reminder function to test each electronic actuator of the car.
  • Anti-theft system settings and key programming Realize the anti-theft key, replace the anti-theft computer, etc.: It has the function of intelligent key and engine electronic anti-theft system matching.
  • 13 Maintenance light to zero Use the diagnostic device to zero the maintenance lamp.
  • Fault background information Describe the state of the vehicle's electronic control system when the fault occurs, including the following information: diagnostic fault code, current data parameters (freeze frame), fault type, and give possible fault causes; Perform a list of causes of failure, a description of the principle, a partial circuit diagram, a diagnostic step, and the location of the component, etc., according to PC
  • the fault information read by the diagnostic device, clear which system of the vehicle has a problem, possible fault phenomena and problem points, and give the corresponding fault resolution steps and test methods; 3.
  • circuit connection diagram can view the fault related The circuit connection diagram of the electrical components such as sensors and relays, including: schematic diagram, overview diagram, position diagram of the connector, terminal definition diagram, location map of the ground point, circuit diagram of the whole vehicle, and list of symbols of all models.
  • 15 Maintenance instruction information upgrade When the new version of the maintenance guide is released, update it.
  • 16 Diagnostic software upgrade Dedicated client upgrade software for fast upgrades.
  • 17 Automatically create diagnostic reports Distributor information, owner information, etc.
  • Diagnostic report editing management The fault code and other information are automatically generated. Other information such as license plate number and work number must be manually input. 1. Editing the fault diagnosis report: The fault can be solved according to the specified format, including: service station information and technician information.
  • Fault diagnosis report management can store existing diagnostic reports , delete, browse, print, etc., and send diagnostic trouble reports to the server or email via the network. 19 Diagnostic report upload Each 4S The store diagnostic report is uploaded to the designated server (private network and database support), which can store, delete, browse, and print the existing common fault reports, and upload the diagnostic fault report to the server through the network; including: 1. Fuzzy query: For a certain vehicle, query the fault description keyword to get all fault information corresponding to the keyword, including fault code, fault description, frequency of fault occurrence, possible fault location, proportion of possible fault locations, Fault diagnosis method; 2.
  • Fault code query For a certain vehicle, input its fault code, index it, find its fault information, including fault code, fault description, frequency of fault occurrence, possible fault location, and possible fault location. Proportion, fault resolution method; 3.
  • Fault location query For a certain vehicle, input the fault location for query, you can index all the fault codes, fault descriptions, and frequency of occurrence of each fault generated in the location. 20 Common faults query and statistics Requires dedicated network support, which can be manually counted without network support. twenty one Authorized use function It can realize the function of authorizing the open use of each function module of the service station side diagnosis system.
  • Step S30 when the calling instruction is detected, calling a preset function added by the diagnostic device to acquire data corresponding to the calling instruction, and outputting and saving the data in an output form corresponding to the preset function;
  • the calling instruction refers to calling the function of the h header file corresponding to the function and/or the dll file of the dynamic link library as a function pointer.
  • the data corresponding to the calling instruction is acquired by the diagnostic device; and the preset function is written to the diagnostic device through the SDK package, so that the user can conveniently obtain the required and interesting data through the diagnostic device, and can quickly Know the situation of the car, and analyze and make a customized display, for example, display data in the form of drawing waveforms, and save the obtained data to form a test database, and also make the data into a report for easy management.
  • the diagnostic function of the diagnostic device is modified by the SDK package to realize the function that the user desires to diagnose the device.
  • FIG. 3 is a schematic flowchart diagram of a second embodiment of a secondary development method for a diagnostic device according to the present invention. Based on the first embodiment of the foregoing method, the method further includes:
  • step S40 the received ECU data is flashed to the ECU data to be erased by the interface configured by the SDK package.
  • ECU Electronic Control Unit, electronic control unit, commonly known as driving computer, car computer
  • ECU Electronic Control Unit, electronic control unit, commonly known as driving computer, car computer
  • the current ECU data writing requires special interfaces and equipment to carry out.
  • one computer can only write ECU data to one car at a time, which is slow. ,low efficiency.
  • the diagnostic device is also a device that is communicatively connected with the ECU.
  • the function of the diagnostic device can be modified to implement the ECU data writing function, and one computer can simultaneously transfer with multiple diagnostic devices, and the received ECU data.
  • the ECU data is written to the device to be flashed through the interface configured by the SDK package.
  • the brushing and writing modes include: 1. local refresh; 2. network refresh: transmitting the data required by the service station through the network, and then writing the data to the electronic control Unit; 3. CD refresh: The released refresh data is stored in CD form, and the data in the CD is written to the electronic control unit by using the refresh program in the SDK package. Therefore, it is possible to perform ECU data writing on multiple vehicles at the same time, which is fast and efficient.
  • an interface for writing ECU data is set in the diagnostic device through the SDK package, so that ECU data can be written to multiple vehicles at the same time, and the speed is fast and the efficiency is high.
  • FIG. 4 is a schematic flowchart diagram of a third embodiment of a secondary development method of a diagnostic device according to the present invention. Based on the second embodiment of the foregoing method, the method further includes:
  • step S50 the acquired data is sent to an account associated with the device to be diagnosed.
  • the data corresponding to the calling instruction is acquired by the diagnostic device; and the preset function is written to the diagnostic device through the SDK package, so that the user can conveniently obtain the required and interesting data through the diagnostic device, and can quickly Know the situation of the car, and analyze and make a customized display, for example, display data in the form of drawing waveforms, and save the obtained data to form a test database, and also make the data into a report for easy management.
  • the test results and operation reports obtained by the 4S shop for repairing and maintaining the car can also be sent to the owner.
  • the communication information can be set in the diagnostic device through the SDK package, and the obtained data is sent to the specified account.
  • the acquired data is sent to the account associated with the device to be diagnosed, for example, the acquired data. Send it to the car owner's email account, or send it to the owner's mobile phone in the form of information, so that the user can know the current running status of the car.
  • the acquired data is sent to the account associated with the device to be diagnosed, so that the user can know the current running state of the car in time.
  • the invention further provides a secondary development device for a diagnostic device.
  • FIG. 5 is a schematic diagram of functional modules of a first embodiment of a secondary development device for a diagnostic device according to the present invention.
  • the secondary development device of the diagnostic device includes a connection module 10, a write module 20, and a processing module 30.
  • connection module 10 is configured to connect the SDK package with the diagnostic device
  • the Diagnostic, OBD uses on-board diagnostics (On-Board)
  • the Diagnostic, OBD system is connected with an onboard diagnostic interface on the vehicle to collect data of various sensors to diagnose the vehicle fault; the OBD system monitors the operating condition of the engine and the working state of the exhaust aftertreatment system at any time, and if it is found, it may cause excessive emissions. In the case of the situation, a warning will be issued immediately. When the system fails, the fault light or check engine warning light is on, and the OBD system will store the fault information in the memory.
  • the standard diagnostic instrument and diagnostic interface can read the relevant information in the form of fault code.
  • the maintenance personnel can quickly and accurately determine the nature and location of the fault.
  • the fault is displayed in the form of a fault code, which has certain requirements on the user's professional knowledge.
  • the user needs to know the fault type corresponding to the fault code, and the data acquired each time can only be viewed, and the user cannot process the data.
  • the user may wish to summarize the data such as the mileage, time and fuel consumption of each trip, and present it in the form of a waveform diagram or a table; in order to facilitate the ordinary user to read the information sent by the OBD system, it can also adapt
  • the need for different users to adjust the diagnostic device diagnostic function requires adjustment of the information output by the OBD system.
  • SDK Software Development Kit, SDK
  • SDK software development kit
  • the writing module 20 is configured to write configuration information to the diagnostic device through the SDK package to add a preset function to the diagnostic device.
  • the user may wish to summarize the data such as the mileage, time and fuel consumption of each trip, and present it in the form of a waveform diagram or a table.
  • the configuration information of the function can be written to the diagnostic device through the SDK package, and the user wants the diagnostic device to have the configuration information.
  • the function can be realized by writing the configuration information of the preset function to the diagnostic device through the SDK package.
  • the writing module 20 is further configured to encapsulate the configuration information of the preset function as a function into the dll file in the dynamic link library, and generate the calling interface and save the file as a h header file.
  • API Application Programming Interface Interface
  • the application calls the API of the operating system.
  • the command (action) that causes the operating system to execute the application.
  • the dll (Dynamic Link Library) file contains the API The execution code of the function, and the API function in the dll file must be used by the declaration of the API function (h header file) and its import library (lib file).
  • the SDK package encapsulates the configuration information of the preset function as an API function into the dll file in the dynamic link library, and generates a call interface to save as a h header file.
  • the API function needs to be called (ie, the preset function is executed)
  • the head is passed.
  • the file finds the corresponding dll file, and the linker calls the API function from the dll file to perform the preset function.
  • FIG. 6 is a schematic diagram of a refinement function module of an embodiment of the write module 20 of FIG. 5; the write module 20 includes:
  • a new unit 21 is configured to write configuration information of the newly added function to the diagnostic device through the SDK package;
  • the modifying unit 22 is configured to add configuration information of the new function to the storage location of the configuration information of the original function by using the interface configured by the SDK package.
  • the preset function may be a new function written in the diagnostic device.
  • the configuration information of the newly added function is written to the diagnostic device through the SDK package; the preset function may also change the original function of the diagnostic device ( Modifying the original function), the interface configured by the SDK package adds configuration information of the new function in the storage location of the configuration information of the original function, and of course, the configuration information can be deleted and modified in the storage location of the configuration information of the original function, thereby Make the diagnostic device have the features that the user wants to have.
  • the processing module 30 is configured to: when a call instruction is detected, invoke a preset function added by the diagnostic device to acquire data corresponding to the call instruction, and output and save the output form corresponding to the preset function. data;
  • the calling instruction refers to calling the function of the h header file corresponding to the function and/or the dll file of the dynamic link library as a function pointer.
  • the data corresponding to the calling instruction is acquired by the diagnostic device; and the preset function is written to the diagnostic device through the SDK package, so that the user can conveniently obtain the required and interesting data through the diagnostic device, and can quickly Know the situation of the car, and analyze and make a customized display, for example, display data in the form of drawing waveforms, and save the obtained data to form a test database, and also make the data into a report for easy management.
  • the diagnostic function of the diagnostic device is modified by the SDK package to realize the function that the user desires to diagnose the device.
  • FIG. 7 is a schematic diagram of functional modules of a second embodiment of a secondary development device for a diagnostic device according to the present invention.
  • the secondary development device of the diagnostic device further includes a flashing module 40.
  • the flash writing module 40 is configured to perform ECU data writing to the device to be flashed through the interface configured by the SDK package.
  • ECU Electronic Control Unit, electronic control unit, commonly known as driving computer, car computer
  • ECU Electronic Control Unit, electronic control unit, commonly known as driving computer, car computer
  • the current ECU data writing requires special interfaces and equipment to carry out.
  • one computer can only write ECU data to one car at a time, which is slow. ,low efficiency.
  • the diagnostic device is also a device that is communicatively connected with the ECU.
  • the function of the diagnostic device can be modified to implement the ECU data writing function, and one computer can simultaneously transfer with multiple diagnostic devices, and the received ECU data.
  • the ECU data is written to the device to be flashed through the interface configured by the SDK package.
  • the brushing and writing modes include: 1. local refresh; 2. network refresh: transmitting the data required by the service station through the network, and then writing the data to the electronic control Unit; 3. CD refresh: The released refresh data is stored in CD form, and the data in the CD is written to the electronic control unit by using the refresh program in the SDK package. Therefore, it is possible to perform ECU data writing on multiple vehicles at the same time, which is fast and efficient.
  • an interface for writing ECU data is set in the diagnostic device through the SDK package, so that ECU data can be written to multiple vehicles at the same time, and the speed is fast and the efficiency is high.
  • FIG. 8 is a schematic diagram of functional modules of a third embodiment of a secondary development device for a diagnostic device according to the present invention.
  • the secondary development device of the diagnostic device further includes a transmitting module 50.
  • the sending module 50 is configured to send the acquired data to an account associated with the device to be diagnosed.
  • the data corresponding to the calling instruction is acquired by the diagnostic device; and the preset function is written to the diagnostic device through the SDK package, so that the user can conveniently obtain the required and interesting data through the diagnostic device, and can quickly Know the situation of the car, and analyze and make a customized display, for example, display data in the form of drawing waveforms, and save the obtained data to form a test database, and also make the data into a report for easy management.
  • the test results and operation reports obtained by the 4S shop for repairing and maintaining the car can also be sent to the owner.
  • the communication information can be set in the diagnostic device through the SDK package, and the obtained data is sent to the specified account.
  • the acquired data is sent to the account associated with the device to be diagnosed, for example, the acquired data. Send it to the car owner's email account, or send it to the owner's mobile phone in the form of information, so that the user can know the current running status of the car.
  • the acquired data is sent to the account associated with the device to be diagnosed, so that the user can know the current running state of the car in time.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Vehicle Cleaning, Maintenance, Repair, Refitting, And Outriggers (AREA)

Abstract

La présente invention concerne un procédé de développement secondaire destiné à un dispositif de diagnostic, consistant : à connecter une trousse de développement logiciel (SDK) à un dispositif de diagnostic (S10) ; à écrire des informations de configuration dans le dispositif de diagnostic au moyen de la trousse SDK afin d'ajouter une fonction prédéfinie dans le dispositif de diagnostic (S20) ; à appeler, lors de la détection d'une instruction d'appel, la fonction prédéfinie ajoutée dans le dispositif de diagnostic afin d'obtenir des données correspondant à l'instruction d'appel de façon à délivrer et sauvegarder les données dans un format de sortie correspondant à la fonction prédéfinie (S30), un fichier d'en-tête h correspondant à la fonction et/ou un fichier dll d'une bibliothèque de liens dynamiques étant utilisé comme pointeur de fonction d'appel selon l'instruction d'appel. L'invention concerne également un appareil de développement secondaire destiné à un dispositif de diagnostic. Selon l'invention, la fonction de diagnostic du dispositif de diagnostic est modifiée au moyen de la trousse SDK, et des fonctions souhaitées par l'utilisateur du dispositif de diagnostic sont assurées.
PCT/CN2017/081806 2016-12-05 2017-04-25 Procédé et appareil de développement secondaire destinés à un dispositif de diagnostic WO2018103252A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611106536.7A CN106708012A (zh) 2016-12-05 2016-12-05 诊断设备的二次开发方法及装置
CN201611106536.7 2016-12-05

Publications (1)

Publication Number Publication Date
WO2018103252A1 true WO2018103252A1 (fr) 2018-06-14

Family

ID=58935875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/081806 WO2018103252A1 (fr) 2016-12-05 2017-04-25 Procédé et appareil de développement secondaire destinés à un dispositif de diagnostic

Country Status (2)

Country Link
CN (1) CN106708012A (fr)
WO (1) WO2018103252A1 (fr)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111752830A (zh) * 2020-06-22 2020-10-09 中国第一汽车股份有限公司 汽车诊断系统、汽车诊断系统的更新方法、装置和设备
CN112464825A (zh) * 2020-11-30 2021-03-09 深圳市道通科技股份有限公司 一种汽车信号波形的绘制方法、装置、系统及移动终端
CN112887945A (zh) * 2021-01-11 2021-06-01 公安部第三研究所 一种车联网网络的渗透测试方法
CN113055250A (zh) * 2021-03-29 2021-06-29 深圳市元征科技股份有限公司 一种联网通信方法、装置、终端设备及存储介质
CN113110994A (zh) * 2021-04-19 2021-07-13 深圳市元征科技股份有限公司 一种车辆诊断方法、装置、电子设备及存储介质
CN113359678A (zh) * 2021-06-25 2021-09-07 潍柴动力股份有限公司 一种发动机数据的刷写装置
CN113721594A (zh) * 2021-09-06 2021-11-30 深圳市星卡软件技术开发有限公司 远程保养灯归零方法、装置和计算机设备
CN114281065A (zh) * 2021-12-28 2022-04-05 深圳市元征科技股份有限公司 车辆的电子控制单元刷写方法、装置及诊断设备
CN114326683A (zh) * 2021-12-31 2022-04-12 深圳市星卡科技有限公司 远程维修安全气囊模块方法、装置和计算机设备
CN114488997A (zh) * 2021-12-28 2022-05-13 深圳市元征科技股份有限公司 Ecu刷写的方法、装置、电子设备及存储介质
CN114647422A (zh) * 2022-04-01 2022-06-21 深圳市元征科技股份有限公司 一种车辆电子控制单元刷写方法、装置、设备和介质
CN114973447A (zh) * 2022-07-21 2022-08-30 深圳市星卡软件技术开发有限公司 一种采集汽车数据方法、装置和计算机设备
CN115600222A (zh) * 2022-08-31 2023-01-13 武汉光庭信息技术股份有限公司（Cn） 汽车安全等级解锁方法、待刷写ecu单元及系统
CN115718474A (zh) * 2022-11-18 2023-02-28 深圳市博诺技术有限公司 一种汽车诊断设备开发者模式系统
CN115729221A (zh) * 2022-11-29 2023-03-03 重庆长安汽车股份有限公司 一种车辆诊断显示方法、装置、电子设备及存储介质
CN117193267A (zh) * 2023-10-24 2023-12-08 宁波极望信息科技有限公司 一种数据采集、监视系统及其管理方法

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107835980A (zh) * 2017-08-25 2018-03-23 深圳市元征科技股份有限公司 一种开发平台的构建方法、装置和计算机可读存储介质
CN109446087A (zh) * 2018-10-29 2019-03-08 深圳市元征科技股份有限公司 一种信息诊断的方法、系统及相关组件
CN110865629B (zh) * 2019-10-30 2024-06-18 一汽奔腾轿车有限公司 一种用于整车电器系统检测的数据服务平台及服务方法
CN111930418B (zh) * 2020-07-27 2024-01-05 深圳市元征科技股份有限公司 诊断设备功能配置方法、诊断设备及存储介质
CN113377589A (zh) * 2021-06-08 2021-09-10 东软睿驰汽车技术（沈阳）有限公司 一种故障诊断方法、装置、车载终端及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060080680A1 (en) * 2004-10-12 2006-04-13 Majid Anwar Platform independent dynamic linking
CN103631609A (zh) * 2012-08-21 2014-03-12 广州汽车集团股份有限公司 一种车载ecu应用程序的刷新方法及系统
CN104932480A (zh) * 2015-04-29 2015-09-23 深圳市元征软件开发有限公司 汽车诊断系统设计方法和装置
CN105302113A (zh) * 2015-10-28 2016-02-03 武汉锐科控制系统有限公司 一种可配置化及可扩展的汽车诊断系统及诊断方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090119657A1 (en) * 2007-10-24 2009-05-07 Link Ii Charles M Methods and systems for software upgrades
CN101286066A (zh) * 2007-12-28 2008-10-15 奇瑞汽车股份有限公司 一种汽车控制器软件刷新的方法
CN101699224A (zh) * 2009-10-19 2010-04-28 中国汽车技术研究中心 基于LabVIEW和PXI的汽车数字仪表测试系统
CN202003221U (zh) * 2011-04-19 2011-10-05 吴天文 车载中央控制器
CN102211555A (zh) * 2011-04-19 2011-10-12 吴天文 车载中央控制器
CN102393731A (zh) * 2011-10-17 2012-03-28 苏州凌创电子科技有限公司 基于obd-ⅱ的车载监控诊断装置
CN202975800U (zh) * 2012-12-14 2013-06-05 中国船舶重工集团公司第七一六研究所 基于wifi与移动智能终端的can总线诊断系统
CN103685240A (zh) * 2013-11-25 2014-03-26 深圳市元征科技股份有限公司 基于dpu431的车辆诊断模块及车辆诊断方法
CN104601692B (zh) * 2015-01-13 2019-06-04 北京京东尚科信息技术有限公司 基于云存储的行车数据处理方法、设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060080680A1 (en) * 2004-10-12 2006-04-13 Majid Anwar Platform independent dynamic linking
CN103631609A (zh) * 2012-08-21 2014-03-12 广州汽车集团股份有限公司 一种车载ecu应用程序的刷新方法及系统
CN104932480A (zh) * 2015-04-29 2015-09-23 深圳市元征软件开发有限公司 汽车诊断系统设计方法和装置
CN105302113A (zh) * 2015-10-28 2016-02-03 武汉锐科控制系统有限公司 一种可配置化及可扩展的汽车诊断系统及诊断方法

Cited By (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111752830A (zh) * 2020-06-22 2020-10-09 中国第一汽车股份有限公司 汽车诊断系统、汽车诊断系统的更新方法、装置和设备
CN111752830B (zh) * 2020-06-22 2022-08-16 中国第一汽车股份有限公司 汽车诊断系统、汽车诊断系统的更新方法、装置和设备
CN112464825A (zh) * 2020-11-30 2021-03-09 深圳市道通科技股份有限公司 一种汽车信号波形的绘制方法、装置、系统及移动终端
CN112464825B (zh) * 2020-11-30 2024-06-07 深圳市道通科技股份有限公司 一种汽车信号波形的绘制方法、装置、系统及移动终端
CN112887945A (zh) * 2021-01-11 2021-06-01 公安部第三研究所 一种车联网网络的渗透测试方法
CN113055250B (zh) * 2021-03-29 2022-06-17 深圳市元征科技股份有限公司 一种联网通信方法、装置、终端设备及存储介质
CN113055250A (zh) * 2021-03-29 2021-06-29 深圳市元征科技股份有限公司 一种联网通信方法、装置、终端设备及存储介质
CN113110994A (zh) * 2021-04-19 2021-07-13 深圳市元征科技股份有限公司 一种车辆诊断方法、装置、电子设备及存储介质
CN113359678A (zh) * 2021-06-25 2021-09-07 潍柴动力股份有限公司 一种发动机数据的刷写装置
CN113359678B (zh) * 2021-06-25 2022-10-28 潍柴动力股份有限公司 一种发动机数据的刷写装置
CN113721594A (zh) * 2021-09-06 2021-11-30 深圳市星卡软件技术开发有限公司 远程保养灯归零方法、装置和计算机设备
CN114488997B (zh) * 2021-12-28 2024-05-10 深圳市元征科技股份有限公司 Ecu刷写的方法、装置、电子设备及存储介质
CN114281065A (zh) * 2021-12-28 2022-04-05 深圳市元征科技股份有限公司 车辆的电子控制单元刷写方法、装置及诊断设备
CN114488997A (zh) * 2021-12-28 2022-05-13 深圳市元征科技股份有限公司 Ecu刷写的方法、装置、电子设备及存储介质
CN114326683A (zh) * 2021-12-31 2022-04-12 深圳市星卡科技有限公司 远程维修安全气囊模块方法、装置和计算机设备
CN114647422A (zh) * 2022-04-01 2022-06-21 深圳市元征科技股份有限公司 一种车辆电子控制单元刷写方法、装置、设备和介质
CN114973447B (zh) * 2022-07-21 2022-11-01 深圳市星卡软件技术开发有限公司 一种采集汽车数据方法、装置和计算机设备
CN114973447A (zh) * 2022-07-21 2022-08-30 深圳市星卡软件技术开发有限公司 一种采集汽车数据方法、装置和计算机设备
CN115600222A (zh) * 2022-08-31 2023-01-13 武汉光庭信息技术股份有限公司（Cn） 汽车安全等级解锁方法、待刷写ecu单元及系统
CN115718474A (zh) * 2022-11-18 2023-02-28 深圳市博诺技术有限公司 一种汽车诊断设备开发者模式系统
CN115729221A (zh) * 2022-11-29 2023-03-03 重庆长安汽车股份有限公司 一种车辆诊断显示方法、装置、电子设备及存储介质
CN117193267A (zh) * 2023-10-24 2023-12-08 宁波极望信息科技有限公司 一种数据采集、监视系统及其管理方法

Also Published As

Publication number Publication date
CN106708012A (zh) 2017-05-24

Similar Documents

Publication Publication Date Title
WO2018103252A1 (fr) Procédé et appareil de développement secondaire destinés à un dispositif de diagnostic
WO2018184221A1 (fr) Procédé et appareil destinés à être utilisés dans le diagnostic à distance de véhicule
WO2018218520A1 (fr) Procédé, dispositif, système et serveur de mise à jour de données
WO2019218444A1 (fr) Procédé, appareil et dispositif de génération de rapport d'essai, et support de stockage
CN107621935B (zh) 一种联动控制系统和联动控制方法
WO2023153821A1 (fr) Procédé de compression d'un modèle de réseau neuronal et appareil électronique pour sa mise en œuvre
US20080234892A1 (en) Memory readout system for vehicle control device
WO2018076561A1 (fr) Procédé et dispositif pour traitement de données
WO2018000741A1 (fr) Procédé et dispositif de commande de quantité d'injection d'huile d'un moteur
CN110632511B (zh) 发动机在线监控试验系统及方法
CN112660045B (zh) 一种远程调试方法
JP2014203314A (ja) Ｅｃｕシミュレーション装置
WO2016056856A1 (fr) Procédé et système pour générer des données de vérification d'intégrité
CN114064473A (zh) 车机系统测试方法、系统、车辆及计算机可读存储介质
CN112034816A (zh) Eol诊断方法、eol诊断控制器及eol诊断系统
CN110566322A (zh) 柴油微粒过滤器的复位方法和装置
WO2023109889A1 (fr) Procédé et dispositif de flashage d'ecu de moteur, et procédé et dispositif de diagnostic de flashage d'ecu de moteur
CN118500749A (zh) 车辆功能测试方法、装置、计算机设备和存储介质
KR101056263B1 (ko) 비행 시뮬레이션 및 테스트를 위한 항공기 임베디드 시스템
CN112526971A (zh) 车辆配置系统、车辆和生产装置
CN110581988A (zh) 一种信号质量检测方法、装置、电子设备及存储介质
CN117234174A (zh) 一种车辆远程标定方法、系统及存储介质
CN110941254A (zh) 一种航空发动机数据处理方法及设备
WO2018094813A1 (fr) Procédé et appareil de commande de balayage et de lecture multimédias, et dispositif intelligent
CN110264065B (zh) 页岩气压裂高压控制元件的全生命周期管理系统

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: 17878342

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17878342

Country of ref document: EP

Kind code of ref document: A1