CN115186627B - Method for developing fault diagnosis manual of commercial vehicle - Google Patents
Method for developing fault diagnosis manual of commercial vehicle Download PDFInfo
- Publication number
- CN115186627B CN115186627B CN202210884879.5A CN202210884879A CN115186627B CN 115186627 B CN115186627 B CN 115186627B CN 202210884879 A CN202210884879 A CN 202210884879A CN 115186627 B CN115186627 B CN 115186627B
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- fault
- code
- phenomenon
- elements
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000003745 diagnosis Methods 0.000 title claims abstract description 151
- 238000000034 method Methods 0.000 title claims abstract description 26
- 238000012423 maintenance Methods 0.000 claims abstract description 30
- 238000011161 development Methods 0.000 claims abstract description 20
- 238000007689 inspection Methods 0.000 claims description 11
- 238000011835 investigation Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 claims description 5
- 238000005259 measurement Methods 0.000 claims description 5
- 230000001502 supplementing effect Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 claims description 3
- 239000013589 supplement Substances 0.000 claims description 3
- 230000002159 abnormal effect Effects 0.000 claims 1
- 230000010354 integration Effects 0.000 abstract 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/103—Formatting, i.e. changing of presentation of documents
- G06F40/109—Font handling; Temporal or kinetic typography
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/12—Use of codes for handling textual entities
- G06F40/151—Transformation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
- G06F40/18—Editing, e.g. inserting or deleting of tables; using ruled lines of spreadsheets
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
Abstract
The invention belongs to the field of automobile fault diagnosis manual development, and particularly relates to a commercial automobile fault diagnosis manual development method. It comprises the following steps: identifying and describing a fault diagnosis table form, and establishing a corresponding logic relationship among a fault phenomenon, a fault reason and a maintenance scheme; converting a fault diagnosis table into a diagnosis flow specification; the fault diagnosis table is established by taking the fault phenomenon as an access point, and the corresponding logic relationship among the common automobile fault phenomenon, the fault cause and the maintenance scheme is explained from two functional loops of an automobile mechanical system and an electric system. And carrying out content identification, information integration and flow typesetting on the fault diagnosis table through typesetting software according to set logic, and finally generating a PDF format text for release. The typesetting is performed systematically, the fault tolerance rate during typesetting is improved, and meanwhile, the manual development period is greatly shortened.
Description
Technical Field
The invention belongs to the field of automobile fault diagnosis manual development, and particularly relates to a commercial automobile fault diagnosis manual development method。
Background
In the market, a common commercial vehicle fault diagnosis manual is generally a fault diagnosis technical text in a PDF format issued to the outside by combining a system function diagram of a vehicle type to be developed and system data (such as a function specification, an engineering drawing and the like) of a controller according to a fault phenomenon and an investigation method which occur in a past vehicle type and performing content compiling according to a set XML template. The development method needs to manually conduct integral typesetting, has large manual intervention quantity and long development period, and provides a commercial vehicle fault diagnosis manual development method for solving the problems.
Disclosure of Invention
To solve the defects and the shortages of the prior art; the invention aims at a method for developing a fault diagnosis manual of a commercial vehicle; through establishing fault diagnosis technical texts, typesetting software integrates content information and performs flow typesetting on the technical texts according to set logic to generate PDF format texts for release, and typesetting is performed systematically, so that the fault tolerance rate in typesetting is improved, and meanwhile, the manual development period is greatly shortened.
In order to achieve the above purpose, the invention adopts the following technical scheme: it comprises the following steps:
(S01) identifying and describing a fault diagnosis table format;
the fault diagnosis table is compiled by excel. The punctuation marks in the text are uniformly Chinese marks, and the punctuation marks are not arranged at the end of the last character after each item of information is edited. The text format is set to facilitate the stable processing of data during importing, identifying and integrating to typesetting software.
(S02) establishing a corresponding logic relation among the fault phenomenon, the fault reason and the maintenance scheme;
the corresponding logic relationship comprises a fault phenomenon element, a fault code element, a code description element, a professional phenomenon supplementing element, a diagnosis step element, a diagnosis unit coding element, a diagnosis unit element, a technical parameter element, a fault cause element, a diagnosis result element, a diagnosis next step element and a maintenance method element.
The professional phenomenon supplementing element supplements some simple phenomena which can exclude part of reasons from the perspective of a maintenance technician, and reduces the fault range.
Analyzing the fault occurrence principle, developing diagnosis step elements, and encoding the diagnosis step. The inspection items contained in each diagnosis step element are used as a diagnosis unit, and a diagnosis unit coding element is established.
The investigation of the elements of the diagnostic unit is based on the description of the diagnostic steps, in combination with the information of the execution circuits and the signal circuits in the machine/circuit system, and the parts involved in the circuits;
technical parameters such as a voltage standard value, a resistance standard value, a clearance standard value, a measurement standard value and the like are included in the technical parameter elements; the related technical parameters are used as inspection items and are added in each inspection link of the fault phenomenon diagnosis flow and the fault reason piece inspection flow.
For the more complex mechanical structure and circuit diagram, schematic development is performed according to the information of connectors, pins, operation methods and the like related to the diagnosis unit, and the schematic development is used for the illustration of the drawing. The schematic code is consistent with its corresponding diagnostic unit code.
Setting diagnosis results of each checking step according to the checking flow of the fault diagnosis unit, and maintaining the diagnosed fault reason piece and the failure mode information corresponding to the reason piece into the fault reason element.
The diagnostic next element is used to direct the current diagnostic step to jump to the next diagnostic step.
And developing a corresponding maintenance scheme according to the fault reasons in the maintenance method elements. The maintenance scheme consists of elements such as parts to be maintained, maintenance modes, maintenance man-hour codes and the like.
(S03) converting a fault diagnosis table into a diagnosis flow specification;
and importing all developed fault diagnosis tables under the target vehicle type into typesetting software for recognition, extracting fault diagnosis table elements, converting according to an XML customized format, and finally generating a PDF format text for release.
Generating a complete diagnosis flow of the fault phenomenon by typesetting software according to the jump rule of the diagnosis step; and generating an investigation flow according to each possible fault reason piece, and adding relevant technical parameters to each link of the flow.
Preferably, the fault information in the technical text in step S02 is established based on all perceived anomalies of the vehicle during actual operation.
Preferably, in the step S02, for the fault phenomenon having the specific DTC code, the specific meaning indicated by the DTC code and the specific meaning indicated by the DTC code may be maintained in the fault code element and the code description element, respectively.
Preferably, the technical parameter elements in the step S02 include technical parameters such as a voltage standard value, a resistance standard value, a gap standard value, a measurement standard value, and the like; when a plurality of technical parameters exist in one diagnosis unit, the technical parameter elements are respectively filled with information such as names, upper limit values, lower limit values, parameter units and the like of the technical parameters.
Preferably, the diagnostic steps of different fault principles in the step S02 cannot be arranged in sequence, and the jump logic of the diagnostic step is set to guide and jump, so that each diagnostic step forms a complete fault diagnosis flow.
Preferably, in the step S02, a diagnosis result determination is set as to whether or not the inspection member in the diagnosis unit is damaged; the judgment result is used to guide the next diagnostic step.
Preferably, in the step S02, the developed diagnostic unit graphics are imported into typesetting software, and the typesetting software links the diagnostic unit content with the corresponding diagnostic unit graphics through the diagnostic unit code, and typesets the diagnostic unit content to the same position in the XML text; the diagnostic unit content is linked under the corresponding diagnostic step name directory.
Preferably, in the step S02, the maintenance schedule may be related to the maintenance man-hour of the corresponding faulty component in the man-hour manual by means of a man-hour code.
Preferably, the typesetting software in the step S03 sets a skip rule of the diagnostic step, and identifies the diagnostic step code in the diagnostic next element corresponding to the diagnostic result of each diagnostic unit, so as to implement the relevant skip of the diagnostic step corresponding to each different fault principle.
Preferably, in the step S03, the troubleshooting may be performed step by step according to the cause analysis through the fault phenomenon, so as to generate a diagnosis flow; and a confirmation flow of the appointed reason can be generated according to the possible reason guide. And realizing multi-scene application.
Preferably, the typesetting function of the typesetting software in the step S03 is developed based on PDF version fault diagnosis manual development standards.
According to the invention, through establishing the fault diagnosis technical text, the typesetting software integrates content information and performs flow typesetting on the technical text according to the set logic to generate the PDF format text for release, and the manual development period is greatly shortened while systematically typesetting and improving the fault tolerance rate during typesetting.
Detailed Description
The present invention will be described below with reference to specific examples in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the description is only illustrative and is not intended to limit the scope of the invention. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present invention.
The specific implementation mode adopts the following technical scheme: the development method of the fault diagnosis manual of the commercial vehicle comprises the following specific steps of;
1. fault diagnosis table development
1.1, establishing an excel format fault diagnosis table text compiling specification. The punctuation marks in the text are uniformly Chinese marks, and the punctuation marks are not arranged at the end of the last character after each item of information is edited. The text format is set to facilitate the stable processing of data during importing, identifying and integrating to typesetting software.
And 1.2, synchronously developing the fault diagnosis table elements. The fault diagnosis table element includes: the system comprises a fault phenomenon element, a fault code element, a code description element, a professional phenomenon supplementing element, a diagnosis step element, a diagnosis unit coding element, a diagnosis unit element, a technical parameter element, a fault reason element, a diagnosis result element, a diagnosis next step element and a maintenance method element.
1.3, developing fault phenomenon elements; the fault phenomenon elements are established based on all perceived anomalies of the vehicle during actual operation.
Developing fault codes and code description elements; for the fault phenomenon of the DTC code with specific meaning, the code and the specific meaning indicated by the code are directly maintained in a fault code element and a code description element respectively.
Developing professional phenomenon supplementary elements; the device is in the angle of a maintenance technician, supplements simple phenomena which can eliminate partial reasons, and reduces the fault range.
And 1.4, analyzing the fault occurrence principle of the fault phenomenon, and developing a diagnosis scheme according to the fault occurrence principle.
And establishing diagnosis step codes according to the fault occurrence principle. The examination item contained in each diagnosis step element is used as a diagnosis unit, and a diagnosis unit code is established.
The investigation of the elements of the diagnostic unit is based on the description of the diagnostic steps, in combination with the information of the execution circuits and the signal circuits in the machine/circuit system, and the parts involved in the circuits;
technical parameter elements of the components involved in the diagnostic unit elements are developed. The technical parameter elements comprise technical parameters such as a voltage standard value, a resistance standard value, a clearance standard value, a measurement standard value and the like. When a plurality of technical parameters exist in one diagnosis unit, the technical parameter elements are respectively filled with information such as names, upper limit values, lower limit values, parameter units and the like of the technical parameters.
For the more complex mechanical and circuit structures, schematic development is performed according to the information related to the diagnosis unit, such as connectors, pins, inspection methods and the like, and the schematic development is used for the illustration of the drawings. The schematic code is consistent with its corresponding diagnostic unit code.
Setting diagnosis results of each checking step according to the checking flow of the fault diagnosis unit, and maintaining the diagnosed fault reason piece and the failure mode information corresponding to the reason piece into the fault reason element.
The diagnostic next element is used to direct the current diagnostic step to jump to the next diagnostic step.
And 1.5, developing a corresponding maintenance method according to the possible fault reasons detected in the diagnosis step. The maintenance method elements comprise elements such as a fault reason piece to be maintained, a maintenance mode, a maintenance man-hour code and the like.
2. Establishing a corresponding logic relationship among fault phenomena, fault reasons and maintenance schemes;
3. performing diagnosis flow conversion on fault diagnosis table
And 3.1, importing all developed fault diagnosis tables under the target vehicle type into typesetting software, and converting the text format into an XML text format. The typesetting software reads the fault diagnosis list information, carries out XML format text catalog structured typesetting on fault phenomenon codes, fault phenomenon names, diagnosis step codes and diagnosis step contents in the list, and arranges the text catalog sequences under the same structure according to the corresponding coding sequences.
And 3.2, importing the developed diagnostic unit graphs into typesetting software, and linking the diagnostic unit contents and the corresponding diagnostic unit graphs through diagnostic unit codes by the typesetting software, and typesetting the diagnostic unit contents and the corresponding diagnostic unit graphs to the same position in an XML text. The diagnostic unit content is linked under the corresponding diagnostic step name directory.
And 3.3, the typesetting software realizes the relevant jump of the diagnosis steps corresponding to different fault principles by identifying the diagnosis step codes in the diagnosis next step corresponding to the diagnosis results of the diagnosis units, so as to form a complete fault diagnosis flow.
And 3.4, typesetting requirements of typesetting software are developed based on fault diagnosis manual development standards of PDF format. The function examples of the composition software are as follows:
1) And the typesetting software converts the technical text format into an XML format, identifies the standard name of the fault phenomenon, and adjusts the name of the main catalog in the XML format document into the text content in the 'fault phenomenon name'.
2) Identifying diagnosis step codes and diagnosis step information, typesetting the XML format text according to the diagnosis step coding sequence, and replacing the subdirectory names under the main directory in the XML format document with the contents in the diagnosis step information.
3) Identifying the content of the diagnosis unit, configuring the graph and inserting the diagnosis unit into the XML format text below the corresponding diagnosis step. And filling the corresponding technical parameters in the diagnosis step into XML according to the examination order of the diagnosis units.
4) The jump rule of the diagnosis result is set for meeting the logic series connection and typesetting requirements of the fault diagnosis flow:
4.1, if the diagnosis result is the corresponding diagnosis next step element, only one diagnosis result has the corresponding diagnosis step code, and the other diagnosis step code is not used;
and if the code is available, skipping according to the code of the diagnosis step, and if the code is not available, indicating that diagnosis is finished, and outputting a maintenance method corresponding to the diagnosis flow.
4.2, if the diagnosis result is the next element of diagnosis, the two diagnosis results are coded in steps;
when code in the next diagnostic step = current diagnostic step code +1; the next step of diagnosis is placed at the lower side of the diagnosis flow in the XML document typesetting;
when the code in the next diagnostic step > the current diagnostic step code +1; the jump step of the diagnostic next step is placed to the right of the diagnostic flow in the XML document layout.
4.3, if the diagnosis result is the next element of the diagnosis, the two diagnosis results are not corresponding to the step codes;
the diagnosis result is no on the right side of the XML document typesetting; the diagnosis result is yes at the lower side of the XML document typesetting.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein.
Furthermore, it should be understood that although the present disclosure describes embodiments, not every embodiment is provided with a separate embodiment, and that this description is provided for clarity only, and that the disclosure is not limited to the embodiments described in detail below, and that the embodiments described in the examples may be combined as appropriate to form other embodiments that will be apparent to those skilled in the art.
Claims (4)
1. A method for developing a fault diagnosis manual of a commercial vehicle is characterized by comprising the following steps of: it comprises the following steps:
s01, identifying and describing a fault diagnosis table type;
the fault diagnosis table is compiled by excel; the punctuation marks in the text are uniformly Chinese marks, and the punctuation marks are not arranged at the end of the last character after each item of information is edited; the text format is set so as to facilitate the stable data processing during importing, identifying and integrating to typesetting software;
in the step S01 fault diagnosis table, fault phenomenon elements are established based on all perceived abnormal conditions of the vehicle in the actual running process;
s02, establishing a corresponding logic relation among fault phenomena, fault reasons and maintenance schemes;
the corresponding logic relationship comprises a fault phenomenon element, a fault code element, a code description element, a professional phenomenon supplementing element, a diagnosis step element, a diagnosis unit coding element, a diagnosis unit element, a technical parameter element, a fault cause element, a diagnosis result element, a diagnosis next step element and a maintenance method element;
the professional phenomenon supplementing element supplements some simple phenomena which can exclude part of reasons from the angle of a maintenance technician, so that the fault range is reduced;
analyzing the fault occurrence principle, developing diagnosis step elements, and encoding the diagnosis step; the inspection item contained in each diagnosis step element is used as a diagnosis unit, and a diagnosis unit coding element is established;
the investigation of the elements of the diagnostic unit is based on the parts involved in the execution and signal circuits in the machine/circuitry;
the technical parameter elements comprise a voltage standard value, a resistance standard value, a clearance standard value and a measurement standard value technical parameter; the related technical parameters are used as inspection items and are added into each inspection link of the fault phenomenon diagnosis flow and the fault reason piece inspection flow;
for the more complicated mechanical structure and circuit diagram, schematic development is carried out according to the information of connectors, pins and operation methods related to the diagnosis unit, and the schematic development is used for illustration of the diagram; the schematic diagram codes are consistent with the corresponding diagnostic unit codes;
setting diagnosis results of each checking step according to the checking flow of the fault diagnosis unit, and maintaining the diagnosed fault reason piece and failure mode information corresponding to the reason piece into a fault reason element;
the diagnosis next step element is used for guiding the current diagnosis step to jump to the next diagnosis step;
in the maintenance method elements, developing a corresponding maintenance scheme according to the fault cause; the maintenance scheme consists of parts to be maintained, maintenance modes and maintenance man-hour code elements;
in the step S02, for the fault phenomenon having the specific DTC code, the specific meaning represented by the DTC code and the specific meaning represented by the DTC code are maintained in the fault code element and the code description element, respectively;
setting a diagnosis result determination in the step S02 as to whether or not the inspection part in the diagnosis unit is damaged; the judging result is used for guiding out the next diagnosis step;
in the step S02, the maintenance scheme performs a correlation query with the maintenance man-hour of the corresponding fault part in the man-hour manual through the man-hour code;
s03, converting a fault diagnosis table into a diagnosis flow instruction;
importing all developed fault diagnosis tables under a target vehicle type into typesetting software for recognition, extracting fault diagnosis table elements, converting according to an XML customized format, and finally generating a PDF format text for release;
generating a complete diagnosis flow of the fault phenomenon by typesetting software according to the jump rule of the diagnosis step; and generating an investigation flow according to each possible fault reason piece, and adding relevant technical parameters to each link of the flow.
2. The method for developing a fault diagnosis manual for a commercial vehicle according to claim 1, wherein: the diagnosis steps of different fault principles in the step S02 cannot be sequentially arranged, and the jump rule of the diagnosis steps is established to guide and jump, so that each diagnosis step forms a complete fault diagnosis flow.
3. The method for developing a fault diagnosis manual for a commercial vehicle according to claim 1, wherein: the technical parameter elements in the step S02 comprise voltage standard values, resistance standard values, clearance standard values and measurement standard value technical parameters; when a plurality of technical parameters exist in one diagnosis unit, technical parameter names, upper limit values, lower limit values and parameter unit information are respectively filled in technical parameter elements.
4. The method for developing a fault diagnosis manual for a commercial vehicle according to claim 1, wherein: setting a skip rule of the diagnosis step by the typesetting software in the step S03, and identifying the diagnosis step codes in the elements of the next diagnosis step corresponding to the diagnosis results of the diagnosis units to realize the relevant skip of the diagnosis steps corresponding to different fault principles.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210884879.5A CN115186627B (en) | 2022-07-26 | 2022-07-26 | Method for developing fault diagnosis manual of commercial vehicle |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210884879.5A CN115186627B (en) | 2022-07-26 | 2022-07-26 | Method for developing fault diagnosis manual of commercial vehicle |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115186627A CN115186627A (en) | 2022-10-14 |
| CN115186627B true CN115186627B (en) | 2024-02-27 |
Family
ID=83520595
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210884879.5A Active CN115186627B (en) | 2022-07-26 | 2022-07-26 | Method for developing fault diagnosis manual of commercial vehicle |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115186627B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303421B (en) * | 2022-12-30 | 2024-04-09 | 武汉品致汽车技术有限公司 | Fault diagnosis manual auxiliary development system |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102183945A (en) * | 2011-01-17 | 2011-09-14 | 武汉理工大学 | Multifunctional remote fault diagnosis system for electric control automobile |
| CN104503442A (en) * | 2014-12-25 | 2015-04-08 | 中国人民解放军军械工程学院 | Fault diagnosis training method for ordnance equipment |
| CN105302098A (en) * | 2015-11-11 | 2016-02-03 | 同济大学 | Subway vehicle interoperation maintenance and support platform based on IETM and building method thereof |
| CN109062191A (en) * | 2018-09-06 | 2018-12-21 | 武汉锐科控制系统有限公司 | Auto analyzer failure is associated with maintenance advisory information and display methods |
| KR20190067339A (en) * | 2017-12-07 | 2019-06-17 | 현대자동차주식회사 | Vehicle diagnostic apparatus and method for controlling the same |
| CN113655770A (en) * | 2021-07-02 | 2021-11-16 | 上海乐意修科技有限公司 | Automobile fault diagnosis teaching system and method |
| CN114265384A (en) * | 2021-11-22 | 2022-04-01 | 阿尔特汽车技术股份有限公司 | Vehicle fault information processing method and system |
| WO2022095790A1 (en) * | 2020-11-09 | 2022-05-12 | 深圳市道通科技股份有限公司 | Automobile failure diagnosis method and system, and automobile failure diagnostic unit |
-
2022
- 2022-07-26 CN CN202210884879.5A patent/CN115186627B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102183945A (en) * | 2011-01-17 | 2011-09-14 | 武汉理工大学 | Multifunctional remote fault diagnosis system for electric control automobile |
| CN104503442A (en) * | 2014-12-25 | 2015-04-08 | 中国人民解放军军械工程学院 | Fault diagnosis training method for ordnance equipment |
| CN105302098A (en) * | 2015-11-11 | 2016-02-03 | 同济大学 | Subway vehicle interoperation maintenance and support platform based on IETM and building method thereof |
| KR20190067339A (en) * | 2017-12-07 | 2019-06-17 | 현대자동차주식회사 | Vehicle diagnostic apparatus and method for controlling the same |
| CN109062191A (en) * | 2018-09-06 | 2018-12-21 | 武汉锐科控制系统有限公司 | Auto analyzer failure is associated with maintenance advisory information and display methods |
| WO2022095790A1 (en) * | 2020-11-09 | 2022-05-12 | 深圳市道通科技股份有限公司 | Automobile failure diagnosis method and system, and automobile failure diagnostic unit |
| CN113655770A (en) * | 2021-07-02 | 2021-11-16 | 上海乐意修科技有限公司 | Automobile fault diagnosis teaching system and method |
| CN114265384A (en) * | 2021-11-22 | 2022-04-01 | 阿尔特汽车技术股份有限公司 | Vehicle fault information processing method and system |
Non-Patent Citations (1)
| Title |
|---|
| 基于知识库的汽车故障及其原因和特征研究;李德贵;杨良勇;;产业与科技论坛;20130415(第07期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115186627A (en) | 2022-10-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104516818B (en) | The automatization test system and its method of compiler a kind of software suitable for Logical Configuration | |
| CN115186627B (en) | Method for developing fault diagnosis manual of commercial vehicle | |
| US8683451B1 (en) | System and method for translating software code | |
| CN110244936B (en) | Method and device for supporting VISIO flow chart to automatically import DCS algorithm configuration software | |
| RU2601141C2 (en) | System and method for providing diagnostic information on faults | |
| CN111522741A (en) | Interface test code generation method and device, electronic equipment and readable storage medium | |
| CN112630622A (en) | Method and system for pattern compiling and downloading test of ATE (automatic test equipment) | |
| CN101442758B (en) | Failure diagnosis method and apparatus | |
| CN109815124B (en) | MBSE-based interlocking function defect analysis method and device and interlocking system | |
| CN109508204B (en) | Front-end code quality detection method and device | |
| CN113239016B (en) | Database design assistance apparatus and method | |
| JPH0572278A (en) | Automatic programing apparatus for test timing | |
| JPH09244921A (en) | Automation system for software test | |
| CN111679983B (en) | JAVA interface static test method and device | |
| CN111858298A (en) | Software testing method based on 3V model | |
| JP2013171350A (en) | Device for measuring test coverage of diagram type program, and method therefor, and program | |
| CN107885493B (en) | Program creation support method and program creation support device | |
| CN112487547B (en) | Electrical process design and processing method for railway vehicle | |
| JP2006059276A (en) | Source code evaluating system | |
| US7120616B2 (en) | Method for specifying, executing and analyzing method sequences for recognition | |
| US20210294293A1 (en) | Information processing apparatus, information processing method, production system, article manufacturing method and storage medium | |
| JP2781300B2 (en) | Automatic test timing program generator | |
| Taylor | Test diagram generation: A practical application of the ATML standards | |
| CN117520167A (en) | Automatic testing device for calculation analysis program and operation method | |
| JP4564689B2 (en) | Hardware function verification method and hardware function verification apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |