CN115186627A - Method for developing fault diagnosis manual of commercial vehicle - Google Patents
Method for developing fault diagnosis manual of commercial vehicle Download PDFInfo
- Publication number
- CN115186627A CN115186627A CN202210884879.5A CN202210884879A CN115186627A CN 115186627 A CN115186627 A CN 115186627A CN 202210884879 A CN202210884879 A CN 202210884879A CN 115186627 A CN115186627 A CN 115186627A
- Authority
- CN
- China
- Prior art keywords
- diagnosis
- fault
- manual
- developing
- code
- 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.)
- Granted
Links
- 238000003745 diagnosis Methods 0.000 title claims abstract description 180
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000012423 maintenance Methods 0.000 claims abstract description 26
- 238000011161 development Methods 0.000 claims abstract description 18
- 238000006243 chemical reaction Methods 0.000 claims abstract description 5
- 238000013024 troubleshooting Methods 0.000 claims description 7
- 239000013589 supplement Substances 0.000 claims description 6
- 238000005259 measurement Methods 0.000 claims description 5
- 238000007689 inspection Methods 0.000 claims description 4
- 230000002159 abnormal effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 3
- 238000012790 confirmation Methods 0.000 claims description 2
- 230000010354 integration Effects 0.000 abstract description 3
- 230000009897 systematic effect Effects 0.000 description 2
- 108091026890 Coding region Proteins 0.000 description 1
- 230000007547 defect Effects 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Health & Medical Sciences (AREA)
- Computational Linguistics (AREA)
- General Engineering & Computer Science (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Artificial Intelligence (AREA)
- Health & Medical Sciences (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Strategic Management (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Test And Diagnosis Of Digital Computers (AREA)
Abstract
The invention belongs to the field of automobile fault diagnosis manual development, and particularly relates to a method for developing a fault diagnosis manual of a commercial vehicle. It comprises the following steps: identifying and explaining the fault diagnosis table format, and establishing corresponding logic relations among fault phenomena, fault reasons and maintenance schemes; a fault diagnosis table conversion diagnosis process description; the fault diagnosis table is established by taking a fault phenomenon as an entry point, starting from two major functional loops of an automobile mechanical system and an electric system, and explaining the corresponding logical relationship among common automobile fault phenomena, fault reasons and maintenance schemes. And performing 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 carried out systematically, the fault-tolerant rate during the typesetting is improved, and the development cycle of the manual is greatly shortened.
Description
Technical Field
The invention belongs to the field of automobile fault diagnosis manual development, and particularly relates to a method for developing a fault diagnosis manual of a commercial vehicle.
Background
In the market, a common fault diagnosis manual for commercial vehicles is generally made according to a fault phenomenon and a troubleshooting method occurring in a past vehicle model, a system function diagram of a vehicle model to be developed and system data (such as a function specification, an engineering drawing and the like) of a controller according to a set XML template, and a fault diagnosis technical text in a PDF format issued externally is generated. The development method needs manual overall typesetting, has large manual intervention amount and long development period, and provides a development method of a fault diagnosis manual of a commercial vehicle for solving the problems.
Disclosure of Invention
Aiming at solving the problems of the defects and the shortcomings of the prior art; the invention aims to provide a method for developing a fault diagnosis manual of a commercial vehicle; by establishing the fault diagnosis technical text, the typesetting software carries out content information integration and flow typesetting on the technical text according to the set logic to generate the PDF format text for release, systematic typesetting is carried out, the fault tolerance rate during typesetting is improved, and meanwhile, the manual development period is greatly shortened.
In order to achieve the purpose, the invention adopts the technical scheme that: it comprises the following steps:
(S01) identifying and explaining the fault diagnosis table format;
and compiling the fault diagnosis table by using excel. The punctuation marks in the text are uniformly Chinese symbols, and the punctuation marks are not arranged at the end of the last character after various information is edited. The text format is set to facilitate smooth data processing during importing, identifying and integrating to typesetting software.
(S02) establishing a corresponding logic relation among a fault phenomenon, a fault reason and a maintenance scheme;
the corresponding logical relationship comprises a fault phenomenon element, a fault code element, a code description element, a professional phenomenon supplement 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.
The professional phenomenon supplement element is a simple phenomenon which stands at the angle of a maintenance technician and can eliminate partial reasons, so that the fault range is reduced.
Analyzing the fault occurrence principle, developing elements of the diagnosis steps and coding the diagnosis steps. The checking item contained in each diagnosis step element is used as a diagnosis unit to establish a diagnosis unit coding element.
The examination of the elements of the diagnostic unit is performed on the basis of the components involved in the signal circuit, which are implemented in the mechanical/electrical system.
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; the related technical parameters are used as examination items and are added to each examination link of a fault phenomenon diagnosis process and a fault cause component examination process.
For the more complicated mechanical structure and circuit diagram, the schematic development is carried out 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.
And setting diagnosis results of all the troubleshooting steps according to the troubleshooting process of the fault diagnosis unit, and maintaining the diagnosed fault cause and the failure mode information corresponding to the cause into the fault cause element.
The diagnostic next element is used to direct the current diagnostic step to jump to the next diagnostic step.
In the elements of the maintenance method, a corresponding maintenance scheme is developed according to the failure reason. The maintenance scheme comprises elements such as parts to be maintained, maintenance modes and maintenance man-hour codes.
(S03) a fault diagnosis table conversion diagnosis flow description;
the typesetting software is characterized in that all developed fault diagnosis tables under the target vehicle type are imported into the typesetting software for recognition, the fault diagnosis table elements are extracted, the conversion is carried out according to an XML customized format, and finally a PDF format text for release is generated.
Generating a complete diagnosis flow of the fault phenomenon by the typesetting software according to the jump rule of the modal diagnosis step; and respectively generating a checking flow according to each possible fault reason, and adding related technical parameters in each link of the flow.
Preferably, the fault information in the technical text of step S02 is established based on all perceptible abnormal conditions of the vehicle during actual operation.
Preferably, in step S02, for a fault phenomenon having a specific DTC code, the DTC code and the specific meaning indicated by the code may be maintained in the fault code element and the code description element, respectively.
Preferably, the technical parameter information in step S02 includes technical parameters such as a voltage standard value, a resistance standard value, a gap standard value, and a measurement standard value; when a plurality of technical parameters exist in one diagnosis unit, the technical parameter elements are respectively filled with information such as the name, the upper limit value, the lower limit value, the parameter unit and the like of each technical parameter.
Preferably, the diagnosis steps of different fault principles in step S02 cannot be arranged in sequence, and a diagnosis step jump logic is set to perform guidance and jump, so that each diagnosis step forms a complete fault diagnosis process flow.
Preferably, the step S02 sets a diagnosis result determination as to whether or not the inspection part in the diagnosis unit is damaged; the decision is used to guide the next diagnostic step.
Preferably, in the step S02, the developed diagnostic unit graph is imported into typesetting software, and the typesetting software links the diagnostic unit content and the corresponding diagnostic unit graph through the diagnostic unit codes and typesets the diagnostic unit graph to the same position in the XML text; the diagnostic unit content is linked below the corresponding diagnostic step name directory.
Preferably, the repair plan in step S02 may be queried in association with repair man-hours corresponding to the faulty component in a man-hour manual by a man-hour code.
Preferably, the typesetting software in the step S03 sets the diagnosis step jump logic, and realizes the related jump of the diagnosis steps corresponding to different fault principles by identifying the diagnosis step codes in the diagnosis next step elements corresponding to the diagnosis results of the diagnosis units.
Preferably, in the step S03, the diagnosis process may be generated by performing troubleshooting step by step according to cause analysis through a fault phenomenon; and a confirmation flow for specifying the 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 the PDF fault diagnosis manual development standard.
According to the invention, by establishing the fault diagnosis technical text, the typesetting software carries out content information integration and flow typesetting on the technical text according to the set logic to generate the PDF format text for release, and systematic typesetting is carried out, so that the fault tolerance rate during typesetting is improved, and meanwhile, the development period of the manual is greatly shortened.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described below by way of specific embodiments. It is to be understood that such description is merely illustrative and not intended to limit the scope of the present invention. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present invention.
The specific implementation mode adopts the following technical scheme: a method for developing a fault diagnosis manual of a commercial vehicle comprises the following specific steps;
1. fault diagnosis table development
1.1, establishing text compilation specifications of the excel-format fault diagnosis table. The punctuation marks in the text are uniformly Chinese symbols, and the punctuation marks are not arranged at the end of the last character after various information is edited. The text format is set to facilitate smooth processing of data during importing, identifying and integrating to typesetting software.
And 1.2, synchronously developing elements of the fault diagnosis table. The failure diagnosis table element includes: fault phenomenon element, fault code element, code description element, professional phenomenon supplement element, diagnosis step element, diagnosis unit coding element, diagnosis unit element, technical parameter element, fault reason element, diagnosis result element, diagnosis next step element and maintenance method element.
1.3, developing fault phenomenon elements; the elements of the fault phenomena are established on the basis of all the perceived abnormal conditions of the vehicle during the actual operation thereof.
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 supplementary elements of professional phenomena; stand at the angle of a maintenance technician, and supplement simple phenomena capable of eliminating partial reasons, thereby reducing the fault range.
And 1.4, analyzing a fault occurrence principle of the fault phenomenon, and developing a diagnosis scheme according to the fault occurrence principle.
And establishing a diagnosis step code according to a fault occurrence principle. The checking item contained in each diagnosis step element is used as a diagnosis unit, and a diagnosis unit code is established.
The examination of the elements of the diagnostic unit is performed on the basis of the components involved in the signal circuit, which are implemented in the mechanical/electrical system.
The technical parameter elements of the components involved in the diagnosis unit element are developed. The technical parameter elements comprise 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 the name, the upper limit value, the lower limit value, the parameter unit and the like of each technical parameter.
For the more complicated mechanical structure and circuit structure, schematic development is performed based on information such as connectors, pins, inspection methods, etc. related to the diagnostic unit, and the schematic development is used for illustration of the drawings. The schematic code is consistent with its corresponding diagnostic unit code.
And setting the diagnosis result of each diagnosis step according to the diagnosis process 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 checked out in the diagnosis step. The elements of the maintenance method comprise elements such as fault cause parts to be maintained, maintenance modes, maintenance labor hour codes and the like.
2. Establishing corresponding logic relations among fault phenomena, fault reasons and maintenance schemes;
3. diagnosis process conversion for fault diagnosis table
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 table information, carries out XML format text catalogue structured typesetting on the fault phenomenon codes, the fault phenomenon names, the diagnosis step codes and the diagnosis step contents in the table, and arranges the text catalogue sequence under the same structure according to the corresponding coding sequence.
And 3.2, importing the developed diagnosis unit graph into typesetting software, linking the diagnosis unit content and the corresponding diagnosis unit graph through diagnosis unit coding by the typesetting software, and typesetting to the same position in the XML text. The diagnostic unit content is linked below the corresponding diagnostic step name directory.
And 3.3, the typesetting software realizes the related skip of the diagnosis steps corresponding to different fault principles by identifying the diagnosis step codes in the next diagnosis step corresponding to the diagnosis result of each diagnosis unit so as to form a complete fault diagnosis process flow.
3.4, the typesetting requirement of the typesetting software is based on the development standard of a fault diagnosis manual in a PDF format. An example of the function of the typesetting software is 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 main directory name in the XML format document into the text content in the fault phenomenon name.
2) Identifying the diagnosis step codes and the diagnosis step information, typesetting the XML format text according to the diagnosis step code 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, matching the picture and inserting the picture into the corresponding diagnosis step in the XML format text. And filling the corresponding technical parameters in the diagnosis step into XML according to the inspection sequence of the diagnosis units.
4) The jump rule of the diagnosis result is set for meeting the logic series and typesetting requirements of the fault diagnosis process:
4.1, if the diagnosis result corresponds to the next element of diagnosis, only one diagnosis result has a corresponding diagnosis step code, and the other diagnosis step code does not exist;
skipping according to the diagnosis step codes if the codes exist, and outputting the maintenance method corresponding to the diagnosis process if no codes exist, namely, the diagnosis is finished.
4.2, if the diagnosis result corresponds to the next element of diagnosis, the two diagnosis results have step codes;
when the code in the next diagnostic step = the current diagnostic step code +1; the next jump step of the diagnosis is arranged 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 next jump step of the diagnosis is placed to the right of the diagnosis flow in the XML document layout.
4.3, if the diagnosis result corresponds to the next step element of diagnosis, the two diagnosis results do not have corresponding step codes;
if the diagnosis result is 'no', the right side of the XML document typesetting is judged; the diagnosis result is 'yes' at the lower side of the layout of the XML document.
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 attributes 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 specification describes embodiments, not every embodiment includes only a single embodiment, and such description is for clarity purposes only, and it is to be understood that all embodiments may be combined as appropriate by one of ordinary skill in the art to form other embodiments as will be apparent to those of skill in the art from the description herein.
Claims (10)
1. A method for developing a fault diagnosis manual of a commercial vehicle is characterized by comprising the following steps: it comprises the following steps:
(S01) identifying and explaining a fault diagnosis table format;
compiling a fault diagnosis table by using 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 all information is edited; the text format is set to facilitate the smooth processing of data during the importing, identifying and integrating to the typesetting software;
(S02) establishing a corresponding logic relation among a fault phenomenon, a fault reason and a maintenance scheme;
the corresponding logical relationship comprises a fault phenomenon element, a fault code element, a code description element, a professional phenomenon supplement 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;
the professional phenomenon supplement element is a simple phenomenon which stands at the angle of a maintenance technician and can eliminate partial reasons, so that the fault range is reduced;
analyzing a fault occurrence principle, developing elements of a diagnosis step, and coding the diagnosis step; the checking item contained in each diagnosis step element is used as a diagnosis unit to establish a diagnosis unit coding element;
the element of the diagnosis unit is checked based on the parts related to the execution in the mechanical/circuit system and the signal loop;
the technical parameter elements comprise voltage standard values, resistance standard values, clearance standard values and measurement standard value technical parameters; the related technical parameters are used as examination items and are added to each examination link of a fault phenomenon diagnosis process and a fault cause component examination process.
For more complex mechanical structure and circuit diagram, the schematic development is carried out according to the connector, pin and operation method information related to the diagnosis unit, and the schematic development is used for illustration of the attached drawings; the schematic code is consistent with its corresponding diagnostic unit code.
Setting diagnosis results of all the troubleshooting steps according to a troubleshooting process of a fault diagnosis unit, and maintaining diagnosed fault cause pieces and failure mode information corresponding to the cause pieces into fault cause elements;
the diagnosis next element is used for guiding the current diagnosis step to skip to the next diagnosis step;
in the elements of the maintenance method, developing a corresponding maintenance scheme according to the failure reason; the maintenance scheme comprises components to be maintained, maintenance modes and maintenance man-hour code elements.
(S03) a fault diagnosis table conversion diagnosis flow description;
the typesetting software is characterized in that all developed fault diagnosis tables under a target vehicle type are imported into the typesetting software for recognition, the elements of the fault diagnosis tables are extracted and converted according to an XML customized format, and finally, a PDF format text for release is generated;
generating a complete diagnosis flow of the fault phenomenon by the typesetting software according to the jump rule of the modal diagnosis step; and respectively generating a checking flow according to each possible fault reason, and adding related technical parameters in each link of the flow.
2. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: in the fault diagnosis table (step S01), fault phenomenon elements are established based on all the sensed abnormal conditions of the vehicle during the actual operation.
3. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: in the above (step S02), regarding the trouble phenomenon having the specific DTC code, the DTC code and the specific meaning indicated by the code may be maintained in the trouble code element and the code description element, respectively.
4. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: the diagnosis steps of different fault principles in the step S02 can not be arranged in sequence, and jump logic of the diagnosis steps is established to guide and jump, so that the diagnosis steps form a complete fault diagnosis process flow.
5. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: the technical parameter information in the step (S02) comprises a voltage standard value, a resistance standard value, a gap standard value and a measurement standard value technical parameter; when a plurality of technical parameters exist in one diagnosis unit, the technical parameter names, the upper limit value, the lower limit value and the parameter unit information are respectively filled in the technical parameter elements.
6. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: a diagnosis result determination is set in said (step S02) as to whether or not the inspection part in the diagnosis unit is broken; the decision is used to guide the next diagnostic step.
7. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: in the step S02, the developed diagnosis unit graph is imported into typesetting software, and the typesetting software links the diagnosis unit content and the corresponding diagnosis unit graph through diagnosis unit coding and typesets the diagnosis unit graph to the same position in the XML text; linking the diagnostic unit content to below the corresponding diagnostic step name directory; the typesetting function of the typesetting software is developed based on the development standard of a PDF fault diagnosis manual.
8. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: the repair plan in step S02 is associated with the repair man-hour of the corresponding faulty component in the man-hour manual by the man-hour code.
9. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: and (S03) setting the diagnosis step jump logic by the typesetting software, and realizing the related jump of the diagnosis steps corresponding to different fault principles by identifying the diagnosis step codes in the diagnosis next step elements corresponding to the diagnosis results of the diagnosis units.
10. The method for developing the fault diagnosis manual of the commercial vehicle according to claim 1, characterized in that: in the step (S03), troubleshooting is performed step by step according to cause analysis through a fault phenomenon, and a diagnosis flow is generated; generating a confirmation flow of a designated reason according to the possible reason guide; and realizing multi-scene application.
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 true CN115186627A (en) | 2022-10-14 |
| CN115186627B 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) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303421A (en) * | 2022-12-30 | 2023-06-23 | 武汉品致汽车技术有限公司 | 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 |
|---|
| 李德贵;杨良勇;: "基于知识库的汽车故障及其原因和特征研究", 产业与科技论坛, no. 07, 15 April 2013 (2013-04-15) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116303421A (en) * | 2022-12-30 | 2023-06-23 | 武汉品致汽车技术有限公司 | Fault diagnosis manual auxiliary development system |
| CN116303421B (en) * | 2022-12-30 | 2024-04-09 | 武汉品致汽车技术有限公司 | Fault diagnosis manual auxiliary development system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115186627B (en) | 2024-02-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113780598B (en) | Intelligent substation virtual terminal checking method | |
| 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 | |
| CN115186627A (en) | Method for developing fault diagnosis manual of commercial vehicle | |
| CN103605556A (en) | Virtual test subject integrally-constructing system and method | |
| CN104572153A (en) | Update data conversion method for vehicle updating | |
| CN104850715B (en) | City rail vehicle wiring method based on EPLAN platforms | |
| US8301422B2 (en) | Process for creating a library of algorithmic representations of electronic equipment | |
| CN103810090A (en) | Nuclear power station digital regulation installing, debugging and verifying method and nuclear power station digital regulation version upgrading method and platform | |
| CN107193251B (en) | Evaluation system and evaluation method | |
| CN101442758B (en) | Failure diagnosis method and apparatus | |
| US20150169295A1 (en) | Design Assistance Device for Control Software | |
| CN116541308B (en) | Regression testing method and system | |
| CN112631918A (en) | Software automation test verification method | |
| CN108267968B (en) | Collaborative semi-physical simulation optical fiber data interaction security verification method | |
| CN113239016B (en) | Database design assistance apparatus and method | |
| CN111414440B (en) | Method and system for verifying control system algorithm configuration diagram by utilizing data flow isomorphism | |
| CN113504774B (en) | Train control interlocking integration and dispatching centralized system interface data checking method and device | |
| US20100287415A1 (en) | Method of making an enduring universal tool for developing equipment tests and tool for the implementation thereof | |
| CN111858298A (en) | Software testing method based on 3V model | |
| CN114756217B (en) | Plug-in based script generation system | |
| CN103853660A (en) | Component-oriented model-based software construction and verification method | |
| CN113609577B (en) | Automobile electric appliance principle inspection method | |
| CN110941941B (en) | Inspection system and inspection method for circuit design |
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 |