WO2019061481A1 - 一种数控机床的故障诊断方法和装置 - Google Patents

一种数控机床的故障诊断方法和装置 Download PDF

Info

Publication number
WO2019061481A1
WO2019061481A1 PCT/CN2017/104947 CN2017104947W WO2019061481A1 WO 2019061481 A1 WO2019061481 A1 WO 2019061481A1 CN 2017104947 W CN2017104947 W CN 2017104947W WO 2019061481 A1 WO2019061481 A1 WO 2019061481A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
fault diagnosis
phenomenon
user
diagnosed
Prior art date
Application number
PCT/CN2017/104947
Other languages
English (en)
French (fr)
Inventor
孙琦
鲁克斯阿明
符昀华
范顺杰
Original Assignee
西门子公司
孙琦
鲁克斯阿明
符昀华
范顺杰
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 西门子公司, 孙琦, 鲁克斯阿明, 符昀华, 范顺杰 filed Critical 西门子公司
Priority to US16/651,642 priority Critical patent/US11474495B2/en
Priority to EP17927179.6A priority patent/EP3683640B1/en
Priority to PCT/CN2017/104947 priority patent/WO2019061481A1/zh
Priority to CN201780094673.XA priority patent/CN111356964A/zh
Publication of WO2019061481A1 publication Critical patent/WO2019061481A1/zh

Links

Images

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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
    • G05B19/406—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by monitoring or safety
    • 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/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0267—Fault communication, e.g. human machine interface [HMI]
    • G05B23/0272—Presentation of monitored results, e.g. selection of status reports to be displayed; Filtering information to the user
    • 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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
    • G05B19/408—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by data handling or data format, e.g. reading, buffering or conversion of data
    • 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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/18—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form
    • G05B19/4155—Numerical control [NC], i.e. automatically operating machines, in particular machine tools, e.g. in a manufacturing environment, so as to execute positioning, movement or co-ordinated operations by means of programme data in numerical form characterised by programme execution, i.e. part programme or machine function execution, e.g. selection of a programme
    • 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/30—Nc systems
    • G05B2219/32—Operator till task planning
    • G05B2219/32356—For diagnostics

Definitions

  • the invention relates to the technical field of industrial automation, in particular to a fault diagnosis method and device for a numerical control machine tool.
  • CNC machine tool is a key equipment in the manufacturing industrial system. It is an automatic machine tool controlled by a computer program. It has the advantages of high precision machining and high automation. Its availability is critical to the stable operation of the associated manufacturing industrial system.
  • FIG. 1 shows a block diagram of a feed system of a numerically controlled machine tool, which can be used as an example of a numerically controlled machine tool.
  • the feed system of the numerical control machine tool 10 includes a programmable logic controller (PLC) 101, a servo drive 102, a servo motor 103, and a coupling. Coupling 104, two bearings 105, a ball screw pair 106 and an encoder 107.
  • PLC programmable logic controller
  • the PLC 101 drives the servo motor 103 to rotate by the servo drive 102, and the servo motor 103 drives the nut in the ball screw pair 103 to rotate by the coupler 104 and the bearing 105.
  • the structure of a CNC machine tool is complex, including multiple complex and cooperative subsystems, such as mechanical, electrical, hydraulic and startup subsystems.
  • the irregularity and uncertainty of the fault phenomenon improve the difficulty of fault diagnosis, which may lead to long-term abnormal operation of the equipment and even business interruption.
  • fault diagnosis methods for CNC machine tools include fault tree analysis, fault propagation model analysis, and case-based reasoning analysis.
  • Fault monitoring and diagnosis are typically performed using mathematical modeling methods based on digital signals, and such methods are more suitable for utilizing certain, regular digital signals.
  • the signals and/or information generated by CNC machine tools are uncertain, and it is difficult to perform efficient fault diagnosis using the above method.
  • the present invention provides a fault diagnosis method and apparatus for a numerically controlled machine tool, which utilizes feedback information provided by the user, and can improve the efficiency of fault diagnosis of the numerically controlled machine tool.
  • a fault diagnosis method for a numerically controlled machine tool comprising: receiving a fault phenomenon to be diagnosed by a user input from a user terminal; performing the fault phenomenon to be diagnosed Fault diagnosis; returning a fault diagnosis result to the user terminal; receiving the result from the user terminal The user's feedback on the fault diagnosis result; if the user's feedback on the fault diagnosis result indicates that the fault has been resolved, the diagnosis strategy for the fault phenomenon to be diagnosed is adjusted according to the fault diagnosis result.
  • the fault diagnosis strategy is adjusted according to the feedback, thereby improving the accuracy of the fault diagnosis.
  • performing fault diagnosis on the fault phenomenon to be diagnosed including: performing fault diagnosis on the fault phenomenon to be diagnosed based on a fault diagnosis information database, where the fault diagnosis information database includes at least one fault phenomenon and For each fault phenomenon, an association relationship between the at least one possible faults of the fault phenomenon is generated; after receiving the feedback from the user terminal of the user terminal on the fault diagnosis result, the method further includes: If the feedback of the fault diagnosis result by the user indicates that the fault is not resolved, then
  • the fault diagnosis result of the fault diagnosis expert includes generating at least one possible fault of the fault phenomenon to be diagnosed, and the feedback of the fault diagnosis result of the fault diagnosis expert indicates that the fault has been solved.
  • the feedback of the fault diagnosis result of the fault diagnosis expert includes: a fault that actually generates the fault phenomenon to be diagnosed; and updating the fault diagnosis information database according to the second fault diagnosis result, including:
  • the fault diagnosis result includes at least one possible fault that generates the fault phenomenon to be diagnosed, and indication information of a probability of occurrence of each possible fault; and a feedback indication of the fault diagnosis result by the user
  • the fault has been solved, and the feedback of the fault diagnosis result by the user further includes: a fault that actually generates the fault phenomenon to be diagnosed; and a diagnosis strategy for the fault phenomenon to be diagnosed according to the fault diagnosis result
  • the method includes: increasing a probability of a fault that actually generates the fault phenomenon to be diagnosed.
  • the user can feedback whether the fault diagnosis result solves the fault.
  • the user can also feedback the fault that actually generates the fault phenomenon to be diagnosed, so that the fault diagnosis device can actually generate the fault phenomenon of the fault phenomenon to be diagnosed when adjusting the fault diagnosis strategy. The probability increases. If the fault diagnosis result indicates that the fault is not resolved, the fault diagnosis device may send the fault phenomenon to be diagnosed to a fault diagnosis expert, and the fault diagnosis device may send the fault diagnosis expert's fault diagnosis result to the user, and receive the user feedback.
  • the fault diagnosis information database is updated according to the fault diagnosis result of the fault diagnosis expert, for example, the fault symptom to be diagnosed is added in the fault diagnosis information database, and the actual feedback of the user feedback is generated.
  • the fault diagnosis strategy is adjusted according to the user feedback, and the fault diagnosis information base is updated, which not only satisfies the accuracy of the fault diagnosis, but also updates the fault diagnosis information base, and can be directly based on the fault diagnosis after the diagnosis of the same fault phenomenon.
  • the information base greatly reduces the reliance on fault diagnosis experts and improves the efficiency of fault diagnosis.
  • the method before receiving a fault phenomenon to be diagnosed by a user input from a user terminal, the method further includes: sending a fault symptom list to the user terminal, where the fault symptom list includes at least one fault phenomenon;
  • the fault phenomenon to be diagnosed which is input by the user from the user terminal, includes: receiving the fault phenomenon to be diagnosed selected by the user from the fault symptom list; and detecting the fault phenomenon to be diagnosed Performing fault diagnosis, including: performing fault diagnosis on the fault phenomenon to be diagnosed based on a fault diagnosis information base, wherein the fault diagnosis information database includes at least one fault phenomenon and at least one fault phenomenon is generated for each fault phenomenon An association between possible failures; or receiving the fault phenomenon to be diagnosed by a user input from a user terminal, comprising: receiving the fault to be diagnosed by the user input from the user terminal Semantic description of the phenomenon; fault diagnosis of the fault phenomenon to be diagnosed Comprising: receiving a fault diagnosis expert diagnosis result of the failure of the phenomenon to be diagnosed.
  • the fault diagnosis device can perform fault diagnosis.
  • a fault diagnosis method for a numerically controlled machine tool comprising: receiving a fault phenomenon to be diagnosed by a user input; and transmitting the fault phenomenon to be diagnosed to a fault diagnosis device. Fault diagnosis; receiving a fault diagnosis result from the fault diagnosis device for the fault phenomenon to be diagnosed; providing the fault diagnosis result to the user; receiving feedback from the user on the fault diagnosis result; Sending feedback of the user to the fault diagnosis result to the fault diagnosis device.
  • the fault diagnosis strategy is adjusted according to the feedback, thereby improving the accuracy of the fault diagnosis.
  • receiving the feedback of the fault diagnosis result by the user further comprising: receiving a fault of the user feedback that actually generates the fault phenomenon to be diagnosed.
  • a fault diagnosis apparatus for a numerically controlled machine tool including:
  • a user interface module for receiving a fault phenomenon to be diagnosed by a user input from a user terminal
  • a fault diagnosis module configured to perform fault diagnosis on the fault phenomenon to be diagnosed
  • the user interface module is further configured to return a fault diagnosis result to the user terminal, and receive feedback from the user terminal of the user terminal on the fault diagnosis result;
  • the fault diagnosis module is further configured to adjust a diagnosis strategy for the fault phenomenon to be diagnosed according to the fault diagnosis result if the feedback of the fault diagnosis result indicates that the fault has been resolved.
  • the fault diagnosis device After the fault diagnosis device returns the fault diagnosis result to the user, the user receives feedback on the fault diagnosis result, adjusts the fault diagnosis strategy according to the feedback, and improves the accuracy of the fault diagnosis.
  • the fault diagnosis module is configured to: perform fault diagnosis on the fault phenomenon to be diagnosed based on a fault diagnosis information database, where the fault diagnosis module performs fault diagnosis on the fault phenomenon to be diagnosed, where the fault diagnosis
  • the information base includes at least one fault phenomenon and an association relationship between at least one possible fault that generates the fault phenomenon for each fault phenomenon,
  • the fault diagnosis module is further configured to send the fault phenomenon to be diagnosed to a fault diagnosis expert for fault diagnosis and receive the fault when the user feedback to the fault diagnosis result indicates that the fault is not resolved.
  • the user interface module is further configured to return a fault diagnosis result of the fault diagnosis expert to the user terminal, and receive feedback from the user of the user terminal on a fault diagnosis result of the fault diagnosis expert;
  • the fault diagnosis module is further configured to: when the feedback of the fault diagnosis result of the fault diagnosis expert indicates that the fault has been resolved, adjust a diagnosis strategy for the fault phenomenon to be diagnosed, and When the feedback of the fault diagnosis result of the fault diagnosis expert indicates that the fault has been solved, the fault diagnosis information database is updated according to the fault diagnosis result of the fault diagnosis expert.
  • the fault diagnosis result of the fault diagnosis expert includes generating at least one possible fault of the fault phenomenon to be diagnosed, and the feedback of the fault diagnosis result of the fault diagnosis expert indicates that the fault has been solved.
  • the feedback of the fault diagnosis result of the fault diagnosis expert by the user further includes: a fault that actually generates the fault phenomenon to be diagnosed; and the fault diagnosis module updates the fault according to the fault diagnosis result of the fault diagnosis expert
  • the fault diagnosis information base is specifically configured to: add, in the fault diagnosis information base, an association relationship between the fault phenomenon to be diagnosed and the fault that the user feedback actually generates the fault phenomenon to be diagnosed.
  • the fault diagnosis result includes at least one possible fault that generates the fault phenomenon to be diagnosed, and indication information of a probability of occurrence of each possible fault; and a feedback indication of the fault diagnosis result by the user malfunction
  • the feedback of the fault diagnosis result is further included: the fault that actually generates the fault phenomenon to be diagnosed; the fault diagnosis module adjusts the to-be diagnosed according to the fault diagnosis result
  • the diagnosis strategy of the fault phenomenon is specifically used to increase the probability of the fault that actually generates the fault phenomenon to be diagnosed.
  • the user can feedback whether the fault diagnosis result solves the fault.
  • the user can also feedback the fault that actually generates the fault phenomenon to be diagnosed, so that the fault diagnosis device can actually generate the fault phenomenon of the fault phenomenon to be diagnosed when adjusting the fault diagnosis strategy. The probability increases. If the fault diagnosis result indicates that the fault is not resolved, the fault diagnosis device may send the fault phenomenon to be diagnosed to a fault diagnosis expert, and the fault diagnosis device may send the fault diagnosis expert's fault diagnosis result to the user, and receive the user feedback.
  • the fault diagnosis information database is updated according to the fault diagnosis result of the fault diagnosis expert, for example, the fault symptom to be diagnosed is added in the fault diagnosis information database, and the actual feedback of the user feedback is generated.
  • the fault diagnosis strategy is adjusted according to the user feedback, and the fault diagnosis information base is updated, which not only satisfies the accuracy of the fault diagnosis, but also updates the fault diagnosis information base, and can be directly based on the fault diagnosis after the diagnosis of the same fault phenomenon.
  • the information base greatly reduces the reliance on fault diagnosis experts and improves the efficiency of fault diagnosis.
  • the user interface module is further configured to send a fault symptom list to the user terminal before receiving a fault phenomenon to be diagnosed by a user input from a user terminal, where the fault phenomenon list includes At least one fault phenomenon, when the user interface module receives the fault phenomenon to be diagnosed by the user input from the user terminal, specifically for receiving the fault phenomenon from the user of the user terminal
  • the fault diagnosis module to be diagnosed is selected in the list, and the fault diagnosis module is configured to perform fault diagnosis on the fault phenomenon to be diagnosed based on a fault diagnosis information database when performing fault diagnosis on the fault phenomenon to be diagnosed.
  • the fault diagnosis information base includes at least one fault phenomenon and an association relationship between at least one possible fault that generates the fault phenomenon for each fault phenomenon; or the user interface module is receiving from a user
  • the fault diagnosis module is specifically configured to receive a fault diagnosis expert when performing fault diagnosis on the fault phenomenon to be diagnosed The diagnosis result of the fault phenomenon to be diagnosed.
  • the fault diagnosis device can perform fault diagnosis.
  • a user terminal including:
  • a user interface module for receiving a fault phenomenon to be diagnosed by a user input
  • a communication module configured to send the fault phenomenon to be diagnosed to a fault diagnosis device for fault diagnosis, and receive a fault diagnosis result from the fault diagnosis device for the fault phenomenon to be diagnosed;
  • the user interface module is further configured to provide the fault diagnosis result to the user, and receive feedback from the user on the fault diagnosis result;
  • the communication module is further configured to send feedback of the fault diagnosis result by the user to the fault diagnosis apparatus.
  • the fault diagnosis result is returned to the user, the feedback of the user for the fault diagnosis result is received, and the fault diagnosis strategy is adjusted according to the feedback, thereby improving the accuracy of the fault diagnosis.
  • the user interface module when receiving the feedback of the fault diagnosis result by the user, is further configured to receive a fault that is generated by the user and actually generates the fault phenomenon to be diagnosed.
  • a fault diagnosis system for a numerically controlled machine tool comprising:
  • a fault diagnosis information base including at least one fault phenomenon and an association relationship between at least one possible fault that generates the fault phenomenon for each fault phenomenon;
  • a fault diagnosis device configured to receive a fault phenomenon to be diagnosed by a user, perform fault diagnosis on the fault phenomenon to be diagnosed based on the fault diagnosis information database, and return a fault diagnosis result to the user, and receive the fault
  • the user feedback on the fault diagnosis result if the feedback of the fault diagnosis result indicates that the fault has been resolved, the diagnosis strategy for the fault phenomenon to be diagnosed is adjusted according to the fault diagnosis result.
  • the fault diagnosis device After the fault diagnosis device returns the fault diagnosis result to the user, the user receives feedback on the fault diagnosis result, adjusts the fault diagnosis strategy according to the feedback, and improves the accuracy of the fault diagnosis.
  • the fault diagnosis apparatus is further configured to: after receiving the feedback of the fault diagnosis result by the user, if the feedback of the fault diagnosis result indicates that the fault is not resolved,
  • the user can feedback whether the fault diagnosis result solves the fault.
  • the user can also feedback the fault that actually generates the fault phenomenon to be diagnosed, so that the fault diagnosis device can actually generate the fault phenomenon of the fault phenomenon to be diagnosed when adjusting the fault diagnosis strategy. The probability increases. If the fault diagnosis result indicates that the fault is not resolved, the fault diagnosis device may send the fault phenomenon to be diagnosed to a fault diagnosis expert, and the fault diagnosis device may send the fault diagnosis expert's fault diagnosis result to the user, and receive the user feedback.
  • the fault diagnosis information database is updated according to the fault diagnosis result of the fault diagnosis expert, for example, the fault symptom to be diagnosed is added in the fault diagnosis information database, and the actual feedback of the user feedback is generated.
  • the fault diagnosis strategy is adjusted according to the user feedback, and the fault diagnosis information base is updated, which not only satisfies the accuracy of the fault diagnosis, but also updates the fault diagnosis information base, and can be directly based on the fault diagnosis after the diagnosis of the same fault phenomenon.
  • the information base greatly reduces the reliance on fault diagnosis experts and improves the efficiency of fault diagnosis.
  • the system further includes a generating device of the fault diagnosis information library, configured to set at least one fault condition of the numerical control machine tool; and respectively operate the numerical control machine tool under each fault condition set a simulation model to generate a fault and record at least one fault phenomenon of the fault; for each fault phenomenon recorded, backtracking at least one possible fault of the fault phenomenon to establish the fault phenomenon and generate The relationship between the possible failures of the failure phenomenon.
  • a generating device of the fault diagnosis information library configured to set at least one fault condition of the numerical control machine tool; and respectively operate the numerical control machine tool under each fault condition set a simulation model to generate a fault and record at least one fault phenomenon of the fault; for each fault phenomenon recorded, backtracking at least one possible fault of the fault phenomenon to establish the fault phenomenon and generate The relationship between the possible failures of the failure phenomenon.
  • the fault diagnosis information base established by the method has the advantages that the fault condition is comprehensive and the fault diagnosis information is rich. The result of fault diagnosis based on such a fault diagnosis information base is more accurate.
  • the system is deployed in the cloud. Users can access the fault diagnosis system for troubleshooting anytime, anywhere.
  • a sixth aspect provides a fault diagnosis apparatus for a numerically controlled machine tool, comprising: at least one memory for storing a machine readable program; at least one processor for calling the machine readable program to execute the first aspect, the first aspect Any of the possible implementations, the second aspect, or the method provided by any of the possible implementations of the second aspect.
  • a seventh aspect providing the machine readable medium storing machine readable instructions, the machine readable instructions, when executed by at least one processor, causing the at least one processor to perform the first aspect, the first aspect Any of the possible implementations, the second aspect, or the method provided by any of the possible implementations of the second aspect.
  • Figure 1 is a schematic diagram of a feed system for a numerically controlled machine tool.
  • FIG. 2 is a schematic diagram of a fault diagnosis system according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a fault diagnosis method according to an embodiment of the present invention.
  • FIG. 4 is still another flowchart of a fault diagnosis method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a fault diagnosis apparatus according to an embodiment of the present invention when performing fault diagnosis.
  • FIG. 6 is a schematic diagram of a fault diagnosis apparatus according to an embodiment of the present invention.
  • FIG. 7 is still another schematic diagram of a fault diagnosis apparatus according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 9 is still another schematic diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of generating a fault diagnosis information base by a fault diagnosis information base generating apparatus according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of a fault diagnosis information database generated in an embodiment of the present invention.
  • the fault diagnosis method of CNC machine tools is usually based on digital signal using mathematical modeling method for fault monitoring and diagnosis, and is more suitable for using certain, regular digital signals.
  • the signals and/or information generated by CNC machine tools are uncertain, and it is difficult to perform efficient fault diagnosis using traditional methods.
  • the fault diagnosis device after the fault diagnosis device returns the fault diagnosis result to the user, the user receives feedback on the fault diagnosis result, adjusts the fault diagnosis strategy according to the feedback, and improves the accuracy of the fault diagnosis.
  • the user can feedback whether the fault diagnosis result solves the fault.
  • the user can also feedback the fault that actually generates the fault phenomenon to be diagnosed, so that the fault diagnosis device can actually generate the fault phenomenon of the fault phenomenon to be diagnosed when adjusting the fault diagnosis strategy. The probability increases. If the fault diagnosis result indicates that the fault is not resolved, the fault diagnosis device may send the fault phenomenon to be diagnosed to a fault diagnosis expert, and the fault diagnosis device may send the fault diagnosis expert's fault diagnosis result to the user, and receive the user feedback.
  • the fault diagnosis information database is updated according to the fault diagnosis result of the fault diagnosis expert, for example, the fault symptom to be diagnosed is added in the fault diagnosis information database, and the actual feedback of the user feedback is generated.
  • the fault diagnosis strategy is adjusted according to the user feedback, and the fault diagnosis information base is updated, which not only satisfies the accuracy of the fault diagnosis, but also updates the fault diagnosis information base, and can be directly based on the fault diagnosis after the diagnosis of the same fault phenomenon.
  • Information library greatly reducing the dependence on fault diagnosis experts, improve The efficiency of fault diagnosis.
  • the user can input the fault phenomenon to be diagnosed or select the fault phenomenon to be diagnosed from the fault symptom list provided by the fault diagnosis device. If the user inputs the fault phenomenon to be diagnosed, the fault diagnosis device can send the fault phenomenon to be diagnosed. Go to a fault diagnosis expert and return the fault diagnosis result of the fault diagnosis expert to the user; if the user selects the fault phenomenon to be diagnosed from the list of known fault phenomena provided by the fault diagnosis device, the fault diagnosis device can be based on a fault diagnosis The information base is diagnosed and the diagnosis results are returned to the user. In this way, no matter whether a fault phenomenon to be diagnosed is a phenomenon that has occurred in the past or a new phenomenon, the fault diagnosis device can perform fault diagnosis.
  • FIG. 2 is a schematic diagram of a fault diagnosis system according to an embodiment of the present invention.
  • the fault diagnosis system 100 includes a fault diagnosis device 40 for performing fault diagnosis on a numerically controlled machine tool 10.
  • the fault diagnosis device 40 can perform fault diagnosis based on a fault diagnosis information base 204. Therefore, the fault diagnosis information base 204 can be regarded as a part of the fault diagnosis system 100, and can also be regarded as being independent of the fault diagnosis system 100.
  • the fault diagnosis information base 204 includes at least one fault phenomenon and an association relationship between at least one possible fault that generates the fault phenomenon for each fault phenomenon. In a possible fault that produces a fault phenomenon, if a fault is the starting node in the entire fault propagation path, that is, the fault is not caused by other faults, the fault can be regarded as a possibility of a fault phenomenon. The root cause of the failure.
  • the fault diagnosis information base 204 can be organized and presented in a manner of big data. And it can be deployed in the cloud to provide rich and accurate fault information to the fault diagnosis device 40.
  • the fault diagnosis information base 204 can be generated by a fault diagnosis information library generating device 30.
  • the fault diagnostic information base generating device 30 can be considered as part of the fault diagnostic system 100 or can be considered to be independent of the fault diagnostic system 100.
  • the principle of the fault diagnosis information base generating device 30 for generating the fault diagnosis information base 204 can be referred to the following FIGS. 10 and 11 and the corresponding description.
  • the fault diagnostic device 40 can include a user interface module 401 and a fault diagnostic module 402.
  • the user interface module 401 can be configured to interact with a user terminal 50 to receive a fault phenomenon 201 to be diagnosed that is input by the user 60 or selected from the fault symptom list 205.
  • the user interface module 401 can also be used to interact with the user terminal 50 to return a fault diagnosis result 202 to the user 60.
  • the user interface module 401 can also be used to interact with the user terminal 50 to receive feedback 203 from the user on the fault diagnosis result 202.
  • the user interface module 401 can also be used to interact with a user terminal 50 for transmitting a fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70, and receiving a fault phenomenon to be diagnosed from the fault diagnosis expert 70.
  • the fault diagnosis result 202 of 201 can also be used to interact with a user terminal 50 for transmitting a fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70, and receiving a fault phenomenon to be diagnosed from the fault diagnosis expert 70.
  • the fault diagnosis result 202 of 201 can also be used to interact with a user terminal 50 for transmitting a fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70, and receiving a fault phenomenon to be diagnosed from the fault diagnosis expert 70.
  • the fault diagnostic module 402 in the fault diagnostic device 40 can be based on a fault to be diagnosed by a fault diagnostic information base 204
  • the phenomenon 201 is used for fault diagnosis, and the fault phenomenon 201 to be diagnosed may also be sent to a fault diagnosis expert 70 through the user interface module 401, and the fault diagnosis result 202 of the fault diagnosis expert 70 may be received.
  • the fault diagnosis module 402 can also adjust the diagnosis strategy of the fault phenomenon 201 to be diagnosed according to the feedback 203 of the user 60.
  • the fault diagnosis information base 204 can also be updated.
  • the fault diagnosis device 40 can also be deployed in the cloud, so that the user 60 can conveniently access the fault diagnosis device 40 anytime and anywhere through the user terminal 50 for fault diagnosis.
  • the user terminal 50 can be a personal computer (PC), a mobile terminal, a tablet, or the like.
  • FIG. 3 is a flowchart of a fault diagnosis method according to an embodiment of the present invention. As shown in FIG. 3, the method may include the following steps:
  • the fault diagnosis device 40 transmits a fault phenomenon list 205 to the user terminal 50.
  • S302 The user terminal 50 presents the fault phenomenon list 205 to the user 60.
  • the user terminal 50 receives the fault phenomenon 201 to be diagnosed selected by the user 60 from the fault phenomenon list 205.
  • the fault diagnosis device 40 receives the fault phenomenon 201 to be diagnosed selected from the list by the user 60 from the user terminal 50.
  • the fault diagnosis device 40 performs fault diagnosis based on the fault phenomenon 201 to be diagnosed based on the fault diagnosis information base 204.
  • the fault diagnosis device 40 returns the fault diagnosis result 202 to the user terminal 50.
  • the user terminal 50 sends the feedback 203 of the user 60 to the fault diagnosis result 202 to the fault diagnosis device 40.
  • step S311 The fault diagnosis device 40 determines whether the fault has been resolved based on the feedback 203. If the feedback 203 indicates that the fault has been resolved (Y), then step S312 is performed. If the feedback 203 indicates that the failure is not resolved (N), then step S313 is performed.
  • the fault diagnosis device 40 adjusts the diagnosis strategy of the fault phenomenon 201 to be diagnosed.
  • the fault diagnosis result 202 includes at least one possible fault that generates the fault phenomenon 201 to be diagnosed, and indication information of the probability of occurrence of each possible fault (eg, indicating that the fault occurrence probability is high, medium, low, or indicating specific).
  • the feedback 203 of the fault diagnosis result 202 by the user 60 further includes: a fault that actually generates the fault phenomenon 201 to be diagnosed; and the fault diagnosis apparatus 40 may adjust the diagnosis strategy of the fault phenomenon 201 to be diagnosed.
  • the probability of actually generating a fault of the fault phenomenon 201 to be diagnosed increases. Accordingly, the probability of generating other faults of the fault phenomenon 201 to be diagnosed can be reduced.
  • the fault diagnosis device 40 transmits the fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70.
  • the fault diagnosis expert 70 performs fault diagnosis on the fault phenomenon 201 to be diagnosed.
  • the fault diagnostic device 40 receives the fault diagnosis result 202 from the fault diagnostic expert 70.
  • the fault diagnosis device 40 transmits the fault diagnosis result 202 of the fault diagnosis expert 70 to the user terminal 50.
  • S317 The user terminal 50 presents the fault diagnosis result 202 of the fault diagnosis expert 70 to the user 60.
  • S318 The user 60 performs fault repair according to the fault diagnosis result 202 of the fault diagnosis expert 70.
  • the user terminal 50 transmits the feedback 203 to the fault diagnosis result 202 input by the user 60 in step S319 to the fault diagnosis device 40.
  • step S321 The fault diagnosis device 40 determines whether the fault has been solved according to the feedback 203 received in step S320. If the feedback 203 indicates that the fault has been resolved, step S322 is performed, otherwise the fault phenomenon 201 to be diagnosed may be re-issued to the fault diagnosis.
  • the expert 70 performs fault diagnosis and repeats the aforementioned steps S313 and subsequent steps.
  • the fault diagnosis device 40 adjusts a diagnosis strategy of the fault phenomenon 201 to be diagnosed, for example, a probability value assigned to the fault that actually generates the fault phenomenon 201 to be diagnosed, and is used to identify that the actually occurring fault is likely to be generated at all. The probability of occurrence of a failure phenomenon 201.
  • the fault diagnosis device 40 updates the fault diagnosis information base 204 according to the fault diagnosis result 202 of the fault diagnosis expert 70, for example, adding the fault phenomenon 201 to be diagnosed in the fault diagnosis information base 204 and the fault actually generated by the user 60 to be diagnosed.
  • the relationship between the failures of phenomenon 201 is a simple matter.
  • FIG. 4 is still another flowchart of a fault diagnosis method according to an embodiment of the present invention. Different from the flow shown in FIG. 3, in the flow shown in FIG. 4, the fault phenomenon 201 to be diagnosed is not in the fault phenomenon list 205 provided by the fault diagnostic device 40, and the user 60 manually inputs the fault phenomenon 201 to be diagnosed. As shown in FIG. 4, the process includes the following steps:
  • the fault diagnosis device 40 transmits a fault symptom list 205 to the user terminal 50.
  • the user terminal 50 presents the fault phenomenon list 205 to the user 60.
  • the user terminal 50 receives the fault phenomenon 201 to be diagnosed input by the user 60.
  • the fault diagnosis device 40 receives the fault phenomenon 201 to be diagnosed input from the user 60 of the user terminal 50.
  • the fault diagnosis device 40 transmits the fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70.
  • the fault diagnosis expert 70 performs fault diagnosis on the fault phenomenon 201 to be diagnosed.
  • the fault diagnostic device 40 receives the fault diagnosis result 202 from the fault diagnostic expert 70.
  • the fault diagnosis device 40 transmits the fault diagnosis result 202 to the user terminal 50.
  • S409 The user terminal 50 presents the fault diagnosis result 202 to the user 60.
  • the user terminal 50 transmits the feedback 203 of the user 60 to the fault diagnosis result 202 to the fault diagnosis device 40.
  • step S413 The fault diagnosis device 40 determines whether the fault has been solved according to the feedback 203. If the feedback 203 indicates that the fault has been resolved, step S413 is performed. Otherwise, the fault phenomenon 201 to be diagnosed may be sent back to the fault diagnosis expert 70 for fault diagnosis. The aforementioned steps S405 and subsequent steps are repeated.
  • S414 Adjust the diagnosis strategy of the fault phenomenon 201 to be diagnosed. For example, a probability value assigned to the fault that actually generates the fault phenomenon 201 to be diagnosed is used to identify the probability that the actually occurring fault occurs in all faults that may generate the fault phenomenon 201 to be diagnosed.
  • the fault diagnosis information base 204 is updated according to the fault diagnosis result 202 of the fault diagnosis expert 70. For example, the relationship between the fault phenomenon 201 to be diagnosed and the fault that is actually fed back by the user 60 to generate the fault phenomenon 201 to be diagnosed is added to the fault diagnosis information base 204.
  • FIG. 5 is a flowchart of the fault diagnosis apparatus 40 according to an embodiment of the present invention when performing fault diagnosis. As shown in FIG. 5, the process may include the following steps:
  • S501 Send a fault symptom list 205 to the user terminal 50.
  • S502 Receive a fault phenomenon 201 to be diagnosed returned by the user terminal 50.
  • step S503 Determine whether the fault phenomenon 201 to be diagnosed is selected from the fault phenomenon list 205 or is input by the user 60. If it is selected from the failure phenomenon list 205, step S504 is performed, and if the user 60 inputs, steps S505 and S506 are performed.
  • S504 Perform fault diagnosis based on the fault symptom 201 to be diagnosed based on the fault diagnosis information base 204.
  • S505 Send the fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70.
  • S508 Receive feedback 203 from the user terminal 50 of the user terminal 50 to the fault diagnosis result 202.
  • step S509 The fault diagnosis device 40 determines, according to the feedback 203, whether the fault has been resolved. If the fault has been resolved, step S510 is performed, and if the fault is not resolved, step S511 is performed.
  • FIG. 6 is a schematic diagram of a fault diagnosis apparatus 40 according to an embodiment of the present invention.
  • the fault diagnosis device Setting 40 can include:
  • a user interface module 401 configured to receive a fault phenomenon 201 to be diagnosed by a user 60 input from a user terminal 50;
  • a fault diagnosis module 402 is configured to perform fault diagnosis on the fault phenomenon 201 to be diagnosed
  • the user interface module 401 is further configured to return a fault diagnosis result 202 to the user terminal 50, and receive feedback 203 from the user terminal 50 to the fault diagnosis result 202 by the user terminal 50;
  • the fault diagnosis module 402 is further configured to adjust the diagnosis strategy of the fault phenomenon 201 to be diagnosed according to the fault diagnosis result 202 in the case that the feedback 203 of the fault diagnosis result 202 by the user 60 indicates that the fault has been resolved.
  • the fault diagnosis module 402 is configured to perform fault diagnosis on the fault phenomenon 201 to be diagnosed based on a fault diagnosis information base 204, where the fault diagnosis information base 204 includes at least one a fault phenomenon and an association relationship between at least one possible fault that produces the fault phenomenon for each fault phenomenon,
  • the fault diagnosis module 402 is further configured to send the fault phenomenon 201 to be diagnosed to a fault diagnosis expert 70 for fault diagnosis and receive fault diagnosis in the case that the feedback 203 of the fault diagnosis result 202 by the user 60 indicates that the fault is not resolved.
  • the user interface module 401 is further configured to return the fault diagnosis result 202 of the fault diagnosis expert 70 to the user terminal 50, and receive feedback 203 from the user terminal 50 of the user terminal 50 to the fault diagnosis result 202 of the fault diagnosis expert 70;
  • the fault diagnosis module 402 is further configured to adjust the diagnosis strategy of the fault phenomenon 201 to be diagnosed, and the fault to the user 60 in the case that the feedback 203 of the fault diagnosis result 202 of the fault diagnosis expert 70 indicates that the fault has been resolved by the user 60.
  • the fault diagnostic information base 204 is updated in accordance with the fault diagnostic result 202 of the fault diagnostic expert 70.
  • the fault diagnosis result 202 of the fault diagnostic expert 70 includes at least one possible fault that generates the fault phenomenon 201 to be diagnosed, and the feedback 203 of the fault diagnosis result 202 of the fault diagnostic expert 70 by the user 60 indicates that the fault has been resolved, and
  • the feedback 203 of the user 60 to the fault diagnosis result 202 of the fault diagnosis expert 70 further includes: a fault that actually generates the fault phenomenon 201 to be diagnosed; the fault diagnostic module 402 updates the fault diagnostic information base 204 according to the fault diagnosis result 202 of the fault diagnostic expert 70.
  • the relationship between the fault phenomenon 201 to be diagnosed and the fault that the user 60 feedback actually generates the fault phenomenon 201 to be diagnosed is added to the fault diagnosis information base 204.
  • the fault diagnosis result 202 includes at least one possible fault that generates the fault phenomenon 201 to be diagnosed, and indication information of the probability of occurrence of each possible fault; the feedback of the user 60 to the fault diagnosis result 202 indicates that the fault has been resolved. And the feedback of the fault diagnosis result 202 by the user 60 further includes: actually generating the fault phenomenon 201 to be diagnosed.
  • the fault diagnosis module 402 is specifically configured to increase the probability of actually generating the fault of the fault phenomenon 201 to be diagnosed.
  • the user interface module 401 is further configured to send a fault symptom list 205 to the user terminal 50 before receiving a fault phenomenon 201 to be diagnosed, which is input by a user 60 of the user terminal 50, in the fault phenomenon list 205.
  • the user interface module 401 when receiving the fault phenomenon 201 to be diagnosed input by the user 60 from the user terminal 50, specifically for receiving the user 60 from the user terminal 50 to be diagnosed from the fault phenomenon list 205
  • the fault diagnosis module 402 is configured to perform fault diagnosis on the fault phenomenon 201 to be diagnosed based on a fault diagnosis information base 204 when the fault diagnosis module 201 is fault diagnosis, wherein the fault diagnosis information base 204 includes at least a fault phenomenon and, for each fault phenomenon, an association between at least one possible fault that produces the fault phenomenon; or
  • the user interface module 401 is configured to receive a semantic description of the fault phenomenon 201 to be diagnosed input by the user 60 from the user terminal 50 when receiving the fault phenomenon 201 to be diagnosed input from a user 60 of the user terminal 50.
  • the module 402 is specifically configured to receive a diagnosis result of the fault phenomenon 201 to be diagnosed by the fault diagnosis expert 70.
  • the fault diagnosis apparatus 40 shown in FIG. 6 reference may be made to the implementation of the fault diagnosis apparatus 40 in FIG. 2 to FIG. 5, wherein the user interface module 401 is used to interact with the user terminal 50, and the fault diagnosis module 402 is used. For fault diagnosis, access the fault diagnosis information base 204, adjust the fault diagnosis strategy, and the like.
  • FIG. 7 is still another schematic diagram of the fault diagnosis apparatus 40 according to an embodiment of the present invention.
  • the fault diagnostic device 40 shown in FIG. 7 can be considered as a hardware implementation of the fault diagnostic device 40 shown in FIG. 6.
  • the at least one memory 404 is configured to store a machine readable program
  • the at least one processor 403 is configured to invoke the machine readable program to execute the method performed by the fault diagnosis apparatus 40 in each of the foregoing processes.
  • the module of the user interface module 401 and the fault diagnosis module 402 can be regarded as a program module or a software module stored in the memory 404. After being called by the processor 403, the fault diagnosis device 40 in the foregoing processes is executed. The method of execution.
  • the fault diagnostic apparatus 40 shown in FIG. 7 may further include at least one communication interface 405, access to the fault diagnosis information base 204, interaction with the user terminal 50, and the like.
  • the fault diagnosis apparatus 40 shown in FIG. 6 and FIG. 7 can be deployed on the cloud, and at least one memory 404 can be a memory on the cloud, and at least one processor 403 can also be a virtualized processing device on the cloud, such as virtual. Machine and so on.
  • FIG. 8 is a schematic diagram of a user terminal 50 according to an embodiment of the present invention. As shown in FIG. 8, the user terminal 50 can include:
  • a user interface module 501 configured to receive a fault phenomenon 201 to be diagnosed by a user 60;
  • a communication module 502 configured to send the fault phenomenon 201 to be diagnosed to a fault diagnosis device 40 for fault diagnosis, and receive a fault diagnosis result 202 from the fault diagnosis device 40 for the fault phenomenon 201 to be diagnosed;
  • the user interface module 501 is further configured to provide the fault diagnosis result 202 to the user 60, and receive feedback 203 from the user 60 to the fault diagnosis result 202;
  • the communication module 502 is further configured to send the feedback 204 of the user 60 to the fault diagnosis result 202 to the fault diagnostic device 40.
  • the user interface module 501 when receiving the feedback 203 of the fault diagnosis result 202 by the user 60, is further configured to receive a fault that is actually fed back by the user 60 to generate the fault phenomenon 201 to be diagnosed.
  • the user terminal 50 shown in FIG. 8 reference may be made to the implementation of the user terminal 50 in FIG. 2 to FIG. 5, wherein the user interface module 501 is used to interact with the user 60, and the communication module 502 is used for the fault diagnosis apparatus. 40 interactions.
  • FIG. 9 is still another schematic diagram of the user terminal 50 according to an embodiment of the present invention.
  • the user terminal 50 shown in FIG. 9 can be regarded as a hardware implementation of the user terminal 50 shown in FIG.
  • at least one memory 504 is configured to store a machine readable program
  • at least one processor 503 is configured to invoke the machine readable program to execute the method performed by the user terminal 50 in each of the foregoing processes.
  • the user module 501 and the communication module 502 in FIG. 8 can be regarded as a program module or a software module stored in the memory 504. After being called by the processor 503, the user terminal 50 executed in the foregoing processes is executed. method.
  • the user terminal 50 shown in FIG. 9 may also include at least one display 505 for displaying information to the user 60 or the diagnostic troubleshooter 70. Additionally, a communication interface 506 can be included for communicating with the fault diagnostic device 40.
  • FIG. 10 is a flowchart of generating a fault diagnosis information base by a fault diagnosis information base generating apparatus according to an embodiment of the present invention.
  • the method may include the following steps:
  • At least one fault condition 1102 of the numerical control machine tool 10 is set.
  • the current of the servo motor 103 of the numerical control machine tool 10 is set to 0 as a fault condition 1102.
  • the at least one fault condition 1102 may relate to all components of the numerically controlled machine tool 10, such as the PLC 101, the servo drive 102, the servo motor 103, the coupler 104, the bearing 105, the ball screw pair 106, and the encoder in FIG. 107. This traverses all the components of the CNC machine 10 and produces more comprehensive faults.
  • each of the fault conditions 1102 provided relates to only one component of the numerically controlled machine tool 10.
  • each of some or all of the set of at least one fault condition 1102 relates to at least two components of the numerically controlled machine tool 10.
  • a total of 100 fault conditions 1102 are set, of which each of the 50 fault conditions 1102 relates to at least two components of the numerically controlled machine tool 10.
  • various actual fault scenarios can be simulated, and the fault diagnosis information base generated by the traditional history-dependent fault record and the expert experience is more flexible and the fault coverage is more comprehensive.
  • fault condition 1102 when fault condition 1102 is set, all possible fault conditions can be traversed to simulate all possible faults.
  • step S1002 under each of the set fault conditions 1102, a simulation model of the numerically controlled machine tool 10 is separately operated to generate a fault 1103, and at least one fault phenomenon 1104 of the fault 1103 is recorded. Among them, a fault may have multiple fault phenomena. In step S1002, all fault phenomena 1104 of fault 1103 may be recorded, or a partial fault phenomenon 1104 of fault 1103 may be recorded.
  • the fault condition 1102 is set as follows: the current of the servo motor 103 is zero.
  • the simulation model of the numerically controlled machine tool 10 is operated under the fault condition 1102, and the generated fault 1103 is that the servo motor 103 has no current output.
  • the fault phenomenon 1104 of the fault is that the rotational speed of the nut in the ball screw set 106 is reduced to zero.
  • a failure phenomenon in which the servo motor 103 is faulty is recorded in step S1002: the rotation speed of the nut in the ball screw pair 106 is reduced to zero.
  • step S1003 for each fault phenomenon 1104 recorded, at least one possible fault 1103 of the fault phenomenon 1104 is traced back to establish the fault phenomenon 1104 and at least one possible fault 1103 that generates the fault phenomenon 1104. The relationship between them.
  • fault phenomenon 1104 can be generated by the fault 1103 (1h), and the fault 1103 (1h) can be Directly or indirectly caused by fault 1103 (12), fault 1103 (12) is caused by fault 1103 (11), and fault 1103 (11) is caused by fault 1103 (1).
  • fault phenomenon 1104(2) may also be generated by fault 1103(21), while fault 1103(21) may be caused by fault 1103(1), fault 1103(2), or fault 1103(4).
  • step S1004 a fault diagnosis information base 204 of the numerical control machine tool 10 is generated based on at least one association relationship established in step S1003.
  • the fault diagnosis information base 204 of the numerical control machine tool 10 may be generated according to all the established association relationships or partial association relationships.
  • the generated fault diagnostic information base 204 can be implemented in a variety of ways.
  • 1102 is the fault condition of the injection.
  • 1103(1) to 1103(m) are m types of faults, where m is a positive integer.
  • a fault may cause another fault, 1103(11) ⁇ 1103(q1) in Figure 10, 1103 (12) to 1103 (1h), 1103 (3k), 1103 (qs), and 1103 (11) to 1103 (q1) are one or more of m types of failures from 1103 (1) to 1103 (m).
  • the fault that is caused, where q, h, k, s are positive integers.
  • 1104(1) ⁇ 1104(n) are n kinds of fault phenomena, where n is a positive integer.
  • the process from one fault phenomenon 1104 to one fault 1103 is referred to as a reverse fault propagation path of the fault phenomenon 1104.
  • the foregoing reverse fault propagation path from fault phenomenon 1104(2) to fault 1103(1) may be: 1104(2)->1103(21)->1103(2), indicating fault phenomenon 1104(2) ) is generated by fault fault 1103 (21), and fault 1103 (21) can be caused by fault 1103 (2). Therefore, in the case of establishing a fault propagation model, in step S1003, the established association relationship is a reverse fault propagation path of the fault phenomenon 1104, and in step S1004, the fault propagation model is generated according to the established reverse fault propagation path.
  • the fault diagnosis information base 204 As the fault diagnosis information base 204.
  • the generated fault diagnosis information base 204 may also include a strip of fault use cases, such as:
  • Fault use case 2 1104(2)->1103(21)->1103(2), indicating that fault phenomenon 1104(2) is generated by fault fault 1103(21), and fault 1103(21) can be caused by fault 1103(2) .
  • Fault use case three 1104(2)->1103(21)->1103(4), indicating that fault phenomenon 1104(2) is generated by fault fault 1103(21), and fault 1103(21) can be caused by fault 1103(4) .
  • Fault use case four 1104(2)->1103(1h)->1103(12)->1103(11)->1103(1), indicating that fault phenomenon 1104(2) is generated by fault fault 1103(1h), Fault 1103 (1h) is caused by fault 1103 (12), while fault 1103 (12) is caused by fault 1103 (11), and fault 1103 (11) is caused by fault 1103 (1).
  • the generated fault diagnosis information base 204 can also be represented by a fault tree, and details are not described herein again.
  • a semantic description 1105 of each of the fault phenomena 1104 can also be set and recorded in the first fault diagnostic information base 204, and a semantic description 1106 of each fault 1103 can be set and recorded in the first fault diagnostic information base 204.
  • the corresponding fault phenomenon is determined according to the semantic description of the fault phenomenon input by the user, and then the fault phenomenon is determined by the fault phenomenon, and the semantic description of the determined fault is returned to the user.
  • the semantics corresponding to the aforementioned fault 1103 "No current output of the servo motor 103" is described as "servo motor fault”;
  • the semantic phenomenon corresponding to the number of failure phenomena 1104 "the rotational speed of the nut in the ball screw pair 106 is 0" is described as "The nut in the ball screw set 106 does not move.”
  • other simulation models of the numerical control machine tool 10 may be separately run to generate the fault diagnosis information base 204 under each of the fault conditions 1102 of the at least one fault condition 1102 set in step S1001. Since different simulation models have different simulation effects on one numerical control machine tool 10, the fault diagnosis information base 204 generated by using different simulation models is included. The information is not consistent and can be mutually modified to generate a comprehensive and accurate fault diagnosis information base 204.
  • the generated fault diagnosis information base 204 can be organized and presented in a big data manner. And it can be deployed in the cloud to provide rich and accurate fault information to the fault diagnosis device 40.
  • a fault in the embodiment of the present invention may be considered as a failure of one or several components themselves, rather than a fault caused by failure of other components.
  • the PLC drives the servo motor to rotate by the servo drive under the control of the computer program in the encoder, and the servo motor drives the ball screw pair through the coupler and the bearing.
  • the nut turns.
  • the current failure phenomenon is that the speed of the nut in the ball screw pair drops to zero.
  • the root cause of this malfunction is the servo motor failure. Since the servo motor failure will cause the bearing to stop rotating, and the bearing stops rotating, the nut in the ball screw pair cannot be rotated.
  • this failure phenomenon is not caused by bearing failure, and its root cause, in other words, the actual failure is the servo motor failure. If the servo motor does not malfunction and the bearing fails to rotate due to mechanical failure, the fault phenomenon is that the speed of the nut in the ball screw pair drops to 0, but the root cause of the fault is the bearing failure, not the servo motor failure.
  • the failure in the embodiment of the present invention can also be referred to as the root cause of a specific failure occurring in a numerically controlled machine tool.
  • embodiments of the present invention also provide a machine readable medium storing machine readable instructions for causing a machine to perform a method as hereinbefore described.
  • a system or apparatus equipped with the machine readable medium on which software program code implementing the functions of any of the above-described embodiments is stored, and a computer of the system or apparatus is stored or a Central Processing Unit (CPU) or a Micro Processor Unit (MPU)) reads and executes program code stored in a storage medium.
  • CPU Central Processing Unit
  • MPU Micro Processor Unit
  • the program code itself read from the storage medium can implement the functions of any of the above embodiments, and thus the program code and the storage medium storing the program code constitute a part of the embodiment of the present invention.
  • Storage medium embodiments for providing program code include floppy disk, hard disk, magneto-optical disk, optical disk (such as Compact Disc Read-Only Memory (CD-ROM), recordable optical disk (Compact Disk-Recordable, CD-R) ), rewritable disc (Compact Disk-ReWritable, CD-RW), digital video disc-read only memory (DVD-ROM), digital versatile disc-random memory (Digital Versatile Disc-Random Access Memory, DVD- RAM), rewritable digital versatile disc (Digital Versatile Disc ⁇ ReWritable, DVD ⁇ RW), magnetic tape, non-volatile memory card and read-only memory (ROM), and on the cloud Storage resources.
  • the program code can be downloaded from the server computer or via the communication network.
  • the program code read out from the storage medium is written into a memory provided in an expansion board inserted into the computer or written in a memory set in an extension unit connected to the computer, and then based on the program code.
  • the instructions cause a CPU or the like mounted on the expansion board or the expansion unit to perform part and all of the actual operations, thereby realizing the functions of any of the above embodiments.
  • the device structure described in the foregoing embodiments may be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or may be multiple Some components in a standalone device are implemented together.
  • the hardware unit can be implemented mechanically or electrically.
  • a hardware unit can include permanently dedicated circuitry or logic (such as a dedicated processor, FPGA or ASIC) to perform the corresponding operations.
  • the hardware unit may also include programmable logic or circuitry (such as a general purpose processor or other programmable processor) that can be temporarily set by software to perform the corresponding operations.
  • programmable logic or circuitry such as a general purpose processor or other programmable processor
  • a specific implementation mechanical mode, or dedicated permanent circuit, or temporarily set circuit

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Manufacturing & Machinery (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

涉及工业自动化技术领域，尤其涉及数控机床的故障诊断方法和装置，利用了用户提供的反馈信息，能够提高数控机床故障诊断的效率。在一种数控机床（10）的故障诊断方法，故障诊断装置（40）接收来自一个用户终端（50）的一个用户（60）输入的一个待诊断的故障现象（201），对待诊断的故障现象（201）进行故障诊断，向用户终端（50）返回一个故障诊断结果（202），接收来自用户终端（50）的用户（60）对故障诊断结果（202）的反馈（203），若用户对故障诊断结果（202）的反馈（203）指示故障已被解决，则根据故障诊断结果（202）调整对待诊断的故障现象（201）的诊断策略。

Description

一种数控机床的故障诊断方法和装置 技术领域
本发明涉及工业自动化技术领域，尤其涉及一种数控机床的故障诊断方法和装置。
背景技术
数控机床(Computer Numerical Control machine tool，CNC machine tool)，是制造工业系统中的关键设备，是一种由计算机程序控制的自动化机床，具有零件加工精度高，自动化程度高等优点。其可用性对于所属的制造工业系统的稳定运行至关重要。
通常，一个数控机床的结构较为复杂。为了示意简单图1示出了一个数控机床的的一个进给系统的结构框图，该进给系统可作为数控机床的一个例子。如图1所示，该数控机床10的进给系统包括一个可编程逻辑控制器(Programmable Logical Controller，PLC)101、一个伺服驱动(servo drive)102、一个伺服电机(servo motor)103、一个耦合器(coupling)104，两个轴承(bearing)105、一个滚珠螺杆副(ball screw pair)106和一个编码器(encoder)107。PLC101在编码器107中的计算机程序的控制下，通过伺服驱动102带动伺服电机103转动，进而伺服电机103通过耦合器104、轴承105带动滚珠螺杆副103中的螺母转动。
可见，一个数控机床的结构复杂，包括多个复杂的相互协作的子系统，比如：机械、电器、液压和启动子系统等。故障现象的不规则和不确定性提高了故障诊断的难度，可能会导致长时间的设备异常运行，甚至业务中断。
目前常用的数控机床的故障诊断方法有故障树分析、故障传播模型分析、基于案例的推理分析等。通常基于数字信号采用数学建模的方法进行故障监控和诊断，而这样的方法比较适合利用确定的、规则的数字信号。而数控机床的产生的信号和/或信息具有不确定性，采用上述方法难以进行高效的故障诊断。
发明内容
有鉴于此，本发明提供一种数控机床的故障诊断方法和装置，利用了用户提供的反馈信息，能够提高数控机床故障诊断的效率。
第一方面，提供一个数控机床的故障诊断方法，该方法可由一个故障诊断装置执行，包括：接收来自一个用户终端的一个用户输入的一个待诊断的故障现象；对所述待诊断的故障现象进行故障诊断；向所述用户终端返回一个故障诊断结果；接收来自所述用户终端的所述 用户对所述故障诊断结果的反馈；若所述用户对所述故障诊断结果的反馈指示故障已被解决，则根据所述故障诊断结果调整对所述待诊断的故障现象的诊断策略。
该方法中，将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
可选地，对所述待诊断的故障现象进行故障诊断，包括：基于一个故障诊断信息库对所述待诊断的故障现象进行故障诊断，其中，所述故障诊断信息库包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；在接收来自所述用户终端的所述用户对所述故障诊断结果的反馈之后，所述方法还包括：若所述用户对所述故障诊断结果的反馈指示故障未被解决，则
将所述待诊断的故障现象发送至一个故障诊断专家进行故障诊断；
接收所述故障诊断专家返回的故障诊断结果；
向所述用户终端返回所述故障诊断专家的故障诊断结果；
接收来自所述用户终端的所述用户对所述故障诊断专家的故障诊断结果的反馈；
若所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决，则根据所述故障诊断专家的故障诊断结果更新所述故障诊断信息库并调整对所述待诊断的故障现象的诊断策略。
可选地，所述故障诊断专家的故障诊断结果包括产生所述待诊断的故障现象的至少一个可能的故障，所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决，且所述用户对所述故障诊断专家的故障诊断结果的反馈还包括：实际产生所述待诊断的故障现象的故障；根据所述第二故障诊断结果更新所述故障诊断信息库，包括：
在所述故障诊断信息库中增加所述待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。
可选地，所述故障诊断结果包括产生所述待诊断的故障现象的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息；所述用户对所述故障诊断结果的反馈指示故障已被解决，且所述用户对所述故障诊断结果的反馈还包括：实际产生所述待诊断的故障现象的故障；根据所述故障诊断结果调整对所述待诊断的故障现象的诊断策略，包括：将实际产生所述待诊断的故障现象的故障的概率增大。
其中，用户在对故障诊断结果进行反馈时，可反馈故障诊断结果是否解决了故障。此外，若故障诊断结果指示故障已被解决，则用户还可反馈实际产生待诊断的故障现象的故障，这样故障诊断装置在调整故障诊断策略时，可将实际产生待诊断的故障现象的故障的概率增大。 若故障诊断结果指示故障未被解决，则故障诊断装置可将待诊断的故障现象发送至一个故障诊断专家，故障诊断装置可将故障诊断专家的故障诊断结果发送至用户，并接收用户的反馈，若用户的反馈指示故障已被解决，则根据故障诊断专家的故障诊断结果更新故障诊断信息库，比如：在故障诊断信息库专用增加待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。这样，根据用户反馈调整了故障诊断策略，更新了故障诊断信息库，不仅满足了本次故障诊断的准确性，由于更新了故障诊断信息库，后续在诊断同样的故障现象时可直接基于故障诊断信息库，极大地减少了对故障诊断专家的依赖，提高了故障诊断的效率。
可选地，在接收来自一个用户终端的一个用户输入的一个待诊断的故障现象之前，还包括：向所述用户终端发送一个故障现象列表，所述故障现象列表中包括至少一个故障现象；接收来自所述用户终端的所述用户输入的所述待诊断的故障现象，包括：接收所述用户从所述故障现象列表中选择的所述待诊断的故障现象；对所述待诊断的故障现象进行故障诊断，包括：基于一个故障诊断信息库对所述待诊断的故障现象进行故障诊断，其中，所述故障诊断信息库包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；或接收来自一个用户终端的一个用户输入的所述待诊断的故障现象，包括：接收来自所述用户终端的所述用户输入的所述待诊断的故障现象的语义描述；对所述待诊断的故障现象进行故障诊断，包括：接收一个故障诊断专家对所述待诊断的故障现象的诊断结果。
这样，无论一个待诊断的故障现象是以往已出现过的现象，还是新出现的现象，故障诊断装置均能够进行故障诊断。
第二方面，提供一个数控机床的故障诊断方法，该方法可由一个用户终端执行，包括：接收一个用户输入的一个待诊断的故障现象；将所述待诊断的故障现象发送至一个故障诊断装置进行故障诊断；接收来自所述故障诊断装置的针对所述待诊断的故障现象的一个故障诊断结果；将所述故障诊断结果提供给所述用户；接收所述用户对所述故障诊断结果的反馈；将所述用户对所述故障诊断结果的反馈发送至所述故障诊断装置。
该方法中，将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
可选地，接收所述用户对所述故障诊断结果的反馈，还包括：接收所述用户反馈的实际产生所述待诊断的故障现象的故障。
第三方面，提供一个数控机床的故障诊断装置，包括：
一个用户接口模块，用于接收来自一个用户终端的一个用户输入的一个待诊断的故障现象；
一个故障诊断模块，用于对所述待诊断的故障现象进行故障诊断；
所述用户接口模块，还用于向所述用户终端返回一个故障诊断结果，接收来自所述用户终端的所述用户对所述故障诊断结果的反馈；
所述故障诊断模块，还用于在所述用户对所述故障诊断结果的反馈指示故障已被解决的情况下，根据所述故障诊断结果调整对所述待诊断的故障现象的诊断策略。
故障诊断装置将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
可选地，所述故障诊断模块在对所述待诊断的故障现象进行故障诊断时具体用于：基于一个故障诊断信息库对所述待诊断的故障现象进行故障诊断，其中，所述故障诊断信息库包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系，
所述故障诊断模块，还用于在所述用户对所述故障诊断结果的反馈指示故障未被解决的情况下，将所述待诊断的故障现象发送至一个故障诊断专家进行故障诊断，并接收所述故障诊断专家返回的故障诊断结果；
所述用户接口模块还用于向所述用户终端返回所述故障诊断专家的故障诊断结果，接收来自所述用户终端的所述用户对所述故障诊断专家的故障诊断结果的反馈；
所述故障诊断模块，还用于在所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决的情况下，调整对所述待诊断的故障现象的诊断策略，以及在所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决的情况下，根据所述故障诊断专家的故障诊断结果更新所述故障诊断信息库。
可选地，所述故障诊断专家的故障诊断结果包括产生所述待诊断的故障现象的至少一个可能的故障，所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决，且所述用户对所述故障诊断专家的故障诊断结果的反馈还包括：实际产生所述待诊断的故障现象的故障；所述故障诊断模块在根据所述故障诊断专家的故障诊断结果更新所述故障诊断信息库时，具体用于：在所述故障诊断信息库中增加所述待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。
可选地，所述故障诊断结果包括产生所述待诊断的故障现象的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息；所述用户对所述故障诊断结果的反馈指示故障 已被解决，且所述用户对所述故障诊断结果的反馈还包括：实际产生所述待诊断的故障现象的故障；所述故障诊断模块在根据所述故障诊断结果调整对所述待诊断的故障现象的诊断策略时，具体用于：将实际产生所述待诊断的故障现象的故障的概率增大。
其中，用户在对故障诊断结果进行反馈时，可反馈故障诊断结果是否解决了故障。此外，若故障诊断结果指示故障已被解决，则用户还可反馈实际产生待诊断的故障现象的故障，这样故障诊断装置在调整故障诊断策略时，可将实际产生待诊断的故障现象的故障的概率增大。若故障诊断结果指示故障未被解决，则故障诊断装置可将待诊断的故障现象发送至一个故障诊断专家，故障诊断装置可将故障诊断专家的故障诊断结果发送至用户，并接收用户的反馈，若用户的反馈指示故障已被解决，则根据故障诊断专家的故障诊断结果更新故障诊断信息库，比如：在故障诊断信息库专用增加待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。这样，根据用户反馈调整了故障诊断策略，更新了故障诊断信息库，不仅满足了本次故障诊断的准确性，由于更新了故障诊断信息库，后续在诊断同样的故障现象时可直接基于故障诊断信息库，极大地减少了对故障诊断专家的依赖，提高了故障诊断的效率。
可选地，所述用户接口模块，还用于在接收来自一个用户终端的一个用户输入的一个待诊断的故障现象之前，向所述用户终端发送一个故障现象列表，所述故障现象列表中包括至少一个故障现象，所述用户接口模块在接收来自所述用户终端的所述用户输入的所述待诊断的故障现象时，具体用于接收来自所述用户终端的所述用户从所述故障现象列表中选择的所述待诊断的故障现象，所述故障诊断模块在对所述待诊断的故障现象进行故障诊断时，具体用于基于一个故障诊断信息库对所述待诊断的故障现象进行故障诊断，其中，所述故障诊断信息库包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；或所述用户接口模块在接收来自一个用户终端的一个用户输入的所述待诊断的故障现象时，具体用于接收来自所述用户终端的所述用户输入的所述待诊断的故障现象的语义描述，所述故障诊断模块在对所述待诊断的故障现象进行故障诊断时，具体用于接收一个故障诊断专家对所述待诊断的故障现象的诊断结果。
这样，无论一个待诊断的故障现象是以往已出现过的现象，还是新出现的现象，故障诊断装置均能够进行故障诊断。
第四方面，提供一种用户终端，包括：
一个用户接口模块，用于接收一个用户输入的一个待诊断的故障现象；
一个通信模块，用于将所述待诊断的故障现象发送至一个故障诊断装置进行故障诊断，以及接收来自所述故障诊断装置的针对所述待诊断的故障现象的一个故障诊断结果；
所述用户接口模块，还用于将所述故障诊断结果提供给所述用户，以及接收所述用户对所述故障诊断结果的反馈；
所述通信模块，还用于将所述用户对所述故障诊断结果的反馈发送至所述故障诊断装置。
将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
可选地，所述用户接口模块在接收所述用户对所述故障诊断结果的反馈时，还用于接收所述用户反馈的实际产生所述待诊断的故障现象的故障。
第五方面，提供一个数控机床的一个故障诊断系统，包括：
一个故障诊断信息库，包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；
一个故障诊断装置，用于接收一个用户输入的一个待诊断的故障现象，基于所述故障诊断信息库对所述待诊断的故障现象进行故障诊断，向所述用户返回一个故障诊断结果，接收所述用户对所述故障诊断结果的反馈，若所述用户对所述故障诊断结果的反馈指示故障已被解决，则根据所述故障诊断结果调整对所述待诊断的故障现象的诊断策略。
故障诊断装置将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
可选地，所述故障诊断装置，还用于在接收所述用户对所述故障诊断结果的反馈之后，若所述用户对所述故障诊断结果的反馈指示故障未被解决，则
将所述待诊断的故障现象发送至一个故障诊断专家进行故障诊断；
接收所述故障诊断专家返回的故障诊断结果；
向所述用户返回所述故障诊断专家的故障诊断结果；
接收所述用户对所述故障诊断专家的故障诊断结果的反馈；
若所述用户对所述故障诊断专家的故障诊断结果的反馈指示故障已被解决，则根据所述故障诊断专家的故障诊断结果更新所述故障诊断信息库并调整对所述待诊断的故障现象的诊断策略。
其中，用户在对故障诊断结果进行反馈时，可反馈故障诊断结果是否解决了故障。此外，若故障诊断结果指示故障已被解决，则用户还可反馈实际产生待诊断的故障现象的故障，这样故障诊断装置在调整故障诊断策略时，可将实际产生待诊断的故障现象的故障的概率增大。若故障诊断结果指示故障未被解决，则故障诊断装置可将待诊断的故障现象发送至一个故障诊断专家，故障诊断装置可将故障诊断专家的故障诊断结果发送至用户，并接收用户的反馈， 若用户的反馈指示故障已被解决，则根据故障诊断专家的故障诊断结果更新故障诊断信息库，比如：在故障诊断信息库专用增加待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。这样，根据用户反馈调整了故障诊断策略，更新了故障诊断信息库，不仅满足了本次故障诊断的准确性，由于更新了故障诊断信息库，后续在诊断同样的故障现象时可直接基于故障诊断信息库，极大地减少了对故障诊断专家的依赖，提高了故障诊断的效率。
可选地，所述系统还包括所述故障诊断信息库的一个生成装置，用于设置所述数控机床的至少一种故障条件；在设置的每一种故障条件下，分别运行所述数控机床的一个仿真模型以产生一条故障，并记录所述故障的至少一种故障现象；对于记录的每一种故障现象，回溯产生该故障现象的至少一种可能的故障，以建立该故障现象与产生该故障现象的可能的故障之间的关联关系。
由于运行的是数控机床的仿真模型，这样就可以方便地设置各种故障条件，以向该仿真模型注入故障。通过该方法建立的故障诊断信息库具有故障情况覆盖全面，故障诊断信息丰富的优点。基于这样的故障诊断信息库进行故障诊断的结果更准确。
可选地，所述系统部署在云端。用户可随时随地访问该故障诊断系统进行故障诊断。
第六方面，提供一个数控机床的故障诊断装置，包括：至少一个存储器，用于存储机器可读程序；至少一个处理器，用于调用所述机器可读程序，执行第一方面、第一方面的任一种可能的实现方式、第二方面或第二方面的任一种可能的实现方式提供的方法。
第七方面，提供所述机器可读介质上存储有机器可读指令，所述机器可读指令在被至少一个处理器执行时，使所述至少一个处理器执行第一方面、第一方面的任一种可能的实现方式、第二方面或第二方面的任一种可能的实现方式提供的方法。
附图说明
图1为一个数控机床的进给系统的示意图。
图2为本发明实施例提供的故障诊断系统的示意图。
图3为本发明实施例提供的一种故障诊断方法的一个流程图。
图4为本发明实施例提供的一种故障诊断方法的又一流程图。
图5为本发明实施例提供的故障诊断装置在进行故障诊断时的流程图。
图6为本发明实施例提供的故障诊断装置的一个示意图。
图7为本发明实施例提供的故障诊断装置的又一示意图。
图8为本发明实施例提供的用户终端的一个示意图。
图9为本发明实施例提供的用户终端的又一示意图。
图10为本发明实施例中故障诊断信息库生成装置生成故障诊断信息库的流程图。
图11为本发明实施例中生成的故障诊断信息库的示意图。
附图标记列表：
Figure PCTCN2017104947-appb-000001
Figure PCTCN2017104947-appb-000002
Figure PCTCN2017104947-appb-000003
具体实施方式
如前所述，目前，数控机床的故障诊断方法通常基于数字信号采用数学建模的方法进行故障监控和诊断，比较适合利用确定的、规则的数字信号。而数控机床的产生的信号和/或信息具有不确定性，采用传统方法难以进行高效的故障诊断。
本发明实施例中，故障诊断装置将故障诊断结果返回给用户后，接收用户针对故障诊断结果的反馈，根据反馈调整故障诊断策略，提高了故障诊断的准确性。
其中，用户在对故障诊断结果进行反馈时，可反馈故障诊断结果是否解决了故障。此外，若故障诊断结果指示故障已被解决，则用户还可反馈实际产生待诊断的故障现象的故障，这样故障诊断装置在调整故障诊断策略时，可将实际产生待诊断的故障现象的故障的概率增大。若故障诊断结果指示故障未被解决，则故障诊断装置可将待诊断的故障现象发送至一个故障诊断专家，故障诊断装置可将故障诊断专家的故障诊断结果发送至用户，并接收用户的反馈，若用户的反馈指示故障已被解决，则根据故障诊断专家的故障诊断结果更新故障诊断信息库，比如：在故障诊断信息库专用增加待诊断的故障现象与所述用户反馈的实际产生所述待诊断的故障现象的故障之间的关联关系。这样，根据用户反馈调整了故障诊断策略，更新了故障诊断信息库，不仅满足了本次故障诊断的准确性，由于更新了故障诊断信息库，后续在诊断同样的故障现象时可直接基于故障诊断信息库，极大地减少了对故障诊断专家的依赖，提高 了故障诊断的效率。
其中，用户可输入待诊断的故障现象或者从故障诊断装置提供的故障现象列表中选择待诊断的故障现象，若用户自身输入待诊断的故障现象，则故障诊断装置可将待诊断的故障现象发送至一个故障诊断专家，并将故障诊断专家的故障诊断结果返回给用户；若用户从故障诊断装置提供的已知的故障现象列表中选择待诊断的故障现象，则故障诊断装置可基于一个故障诊断信息库进行故障诊断，也会将故障诊断结果返回给用户。这样，无论一个待诊断的故障现象是以往已出现过的现象，还是新出现的现象，故障诊断装置均能够进行故障诊断。
下面，结合附图对本发明实施例进行详细说明。
图2为本发明实施例提供的故障诊断系统的示意图。如图2所示，该故障诊断系统100包括：一个故障诊断装置40，用于对一个数控机床10进行故障诊断。
其中，故障诊断装置40可基于一个故障诊断信息库204进行故障诊断，因此，故障诊断信息库204可视为故障诊断系统100的一部分，也可视为独立于故障诊断系统100。故障诊断信息库204中包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系。对于产生一种故障现象的可能的故障中，如果一个故障是整个故障传播路径中的起始节点，即该故障不是由其他故障引起的，则该故障可视为一种故障现象的一种可能的故障根本原因。其中，可选地，故障诊断信息库204可以大数据的方式组织、呈现。且可部署在云端，便于向故障诊断装置40提供丰富准确的故障信息。
该故障诊断信息库204可由一个故障诊断信息库生成装置30生成。该故障诊断信息库生成装置30可视为故障诊断系统100的一部分，或者也可视为独立于故障诊断系统100。该故障诊断信息库生成装置30生成故障诊断信息库204的原理可参考后面的图10和图11及对应的说明。
故障诊断装置40可包括一个用户接口模块401和一个故障诊断模块402。其中，该用户接口模块401可用于与一个用户终端50进行交互，接收一个用户60输入的或从故障现象列表205中选择的待诊断的故障现象201。该用户接口模块401还可用于与该用户终端50进行交互，向用户60返回故障诊断结果202。此外，该用户接口模块401还可用于与该用户终端50交互，接收用户对故障诊断结果202的反馈203。
此外，该用户接口模块401还可以用于与一个用户终端50交互，用于向一个故障诊断专家70发送待诊断的故障现象201，并从该故障诊断专家70处接收对该待诊断的故障现象201的故障诊断结果202。
故障诊断装置40中的故障诊断模块402可基于一个故障诊断信息库204对待诊断的故障 现象201进行故障诊断，也可将待诊断的故障现象201通过用户接口模块401发送至一个故障诊断专家70，并接收该故障诊断专家70的故障诊断结果202。
此外，故障诊断模块402还可根据用户60的反馈203调整对待诊断的故障现象201的诊断策略，可选地，还可更新故障诊断信息库204。
可选地，故障诊断装置40也可部署在云端，这样，用户60可通过用户终端50可随时随地方便地访问故障诊断装置40以进行故障诊断。其中用户终端50可以为个人电脑(Personal Computer，PC)、移动终端、平板电脑等。
图3为本发明实施例提供的一种故障诊断方法的一个流程图。如图3所示，该方法可包括如下步骤：
S301：故障诊断装置40向用户终端50发送一个故障现象列表205。
S302：用户终端50向用户60呈现故障现象列表205。
S303：用户终端50接收用户60从故障现象列表205中选择的待诊断的故障现象201。
S304：故障诊断装置40接收来自用户终端50的用户60从列表中选择的待诊断的故障现象201。
S305：故障诊断装置40基于故障诊断信息库204对待诊断的故障现象201进行故障诊断。
S306：故障诊断装置40向用户终端50返回故障诊断结果202。
S307：用户终端50向用户60呈现故障诊断结果202。
S308：用户60根据故障诊断结果202进行故障修复。
S309：用户60在用户终端50上输入对故障诊断结果202的反馈203。
S310：用户终端50向故障诊断装置40发送用户60对故障诊断结果202的反馈203。
S311：故障诊断装置40根据反馈203判断故障是否已被解决。若反馈203指示故障已被解决(Y)，则执行步骤S312。若反馈203指示故障未被解决(N)，则执行步骤S313。
S312：故障诊断装置40调整对待诊断的故障现象201的诊断策略。其中，故障诊断结果202包括产生待诊断的故障现象201的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息(比如：指示故障发生概率高、中、低，或者指示具体的故障发生概率等)，用户60对故障诊断结果202的反馈203还包括：实际产生待诊断的故障现象201的故障；则故障诊断装置40在调整对待诊断的故障现象201的诊断策略时，可将实际产生待诊断的故障现象201的故障的概率增大。相应地，可将产生该待诊断的故障现象201的其他故障的概率减小。
S313：故障诊断装置40将待诊断的故障现象201发送至一个故障诊断专家70。
S314：故障诊断专家70对待诊断的故障现象201进行故障诊断。
S315：故障诊断装置40接收来自故障诊断专家70的故障诊断结果202。
S316：故障诊断装置40向用户终端50发送故障诊断专家70的故障诊断结果202。
S317：用户终端50向用户60呈现故障诊断专家70的故障诊断结果202。
S318：用户60根据故障诊断专家70的故障诊断结果202进行故障修复。
S319：用户60在用户终端50上输入对故障诊断专家70的故障诊断结果202的反馈203。
S320：用户终端50向故障诊断装置40发送步骤S319中用户60输入的对故障诊断结果202的反馈203。
S321：故障诊断装置40根据步骤S320中收到的反馈203判断故障是否已被解决，若反馈203指示故障已被解决，则执行步骤S322，否则可将待诊断的故障现象201重新发给故障诊断专家70进行故障诊断，重复前述的步骤S313及之后的步骤。
S322：故障诊断装置40调整对待诊断的故障现象201的诊断策略，比如赋予该实际产生该待诊断的故障现象201的故障一个概率值，用于标识该实际发生的故障在所有可能产生该待诊断的故障现象201的故障中发生的概率。
S323：故障诊断装置40根据故障诊断专家70的故障诊断结果202更新故障诊断信息库204，比如：在故障诊断信息库204中增加待诊断的故障现象201与用户60反馈的实际产生待诊断的故障现象201的故障之间的关联关系。
图4为本发明实施例提供的一种故障诊断方法的又一流程图。与图3所示流程不同的是，图4所示的流程中，待诊断的故障现象201不在故障诊断装置40提供的故障现象列表205中，用户60手动输入该待诊断的故障现象201。如图4所示，该流程包括如下步骤：
S401：故障诊断装置40向用户终端50发送一个故障现象列表205。
S402：用户终端50向用户60呈现故障现象列表205。
S403：用户终端50接收用户60输入的待诊断的故障现象201。
S404：故障诊断装置40接收来自用户终端50的用户60输入的待诊断的故障现象201。
S405：故障诊断装置40将待诊断的故障现象201发送至一个故障诊断专家70。
S406：故障诊断专家70对待诊断的故障现象201进行故障诊断。
S407：故障诊断装置40接收来自故障诊断专家70的故障诊断结果202。
S408：故障诊断装置40向用户终端50发送故障诊断结果202。
S409：用户终端50向用户60呈现故障诊断结果202。
S410：用户60根据故障诊断结果202进行故障修复。
S411：用户60在用户终端50上输入对故障诊断结果202的反馈203。
S412：用户终端50向故障诊断装置40发送用户60对故障诊断结果202的反馈203。
S413：故障诊断装置40根据反馈203判断故障是否已被解决，若反馈203指示故障已被解决，则执行步骤S413，否则可将待诊断的故障现象201重新发给故障诊断专家70进行故障诊断，重复前述的步骤S405及之后的步骤。
S414：调整对待诊断的故障现象201的诊断策略。比如赋予该实际产生该待诊断的故障现象201的故障一个概率值，用于标识该实际发生的故障在所有可能产生该待诊断的故障现象201的故障中发生的概率。
S415：根据故障诊断专家70的故障诊断结果202更新故障诊断信息库204。比如：在故障诊断信息库204中增加待诊断的故障现象201与用户60反馈的实际产生待诊断的故障现象201的故障之间的关联关系。
图5为本发明实施例提供的故障诊断装置40在进行故障诊断时的流程图。如图5所示，该流程可包括如下步骤：
S501：向用户终端50发送一个故障现象列表205。
S502：接收用户终端50返回的待诊断的故障现象201。
S503：判断待诊断的故障现象201是从故障现象列表205中选择的，还是用户60输入的。若是从故障现象列表205中选择的，则执行步骤S504，若是用户60输入的，则执行步骤S505和S506。
S504：基于故障诊断信息库204对待诊断的故障现象201进行故障诊断。
S505：将待诊断的故障现象201发送至一个故障诊断专家70。
S506：接收来自故障诊断专家70的故障诊断结果202。
S507：向用户终端50发送故障诊断结果202。
S508：接收来自用户终端50的用户60对故障诊断结果202的反馈203。
S509：故障诊断装置40根据反馈203判断故障是否已被解决。若故障已被解决，则执行步骤S510，若故障未被解决，则执行步骤S511。
S510：调整对待诊断的故障现象201的诊断策略(更新故障诊断信息库204)。
S511：将用户60对故障诊断结果202的反馈203发给故障诊断专家70。
S512：接收来自故障诊断专家70的故障诊断结果202。
图6为本发明实施例提供的故障诊断装置40的一个示意图。如图6所示，该故障诊断装 置40可包括：
一个用户接口模块401，用于接收来自一个用户终端50的一个用户60输入的一个待诊断的故障现象201；
一个故障诊断模块402，用于对待诊断的故障现象201进行故障诊断；
用户接口模块401，还用于向用户终端50返回一个故障诊断结果202，接收来自用户终端50的用户60对故障诊断结果202的反馈203；
故障诊断模块402，还用于在用户60对故障诊断结果202的反馈203指示故障已被解决的情况下，根据故障诊断结果202调整对待诊断的故障现象201的诊断策略。
可选地，故障诊断模块402在对待诊断的故障现象201进行故障诊断时具体用于：基于一个故障诊断信息库204对待诊断的故障现象201进行故障诊断，其中，故障诊断信息库204包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系，
故障诊断模块402，还用于在用户60对故障诊断结果202的反馈203指示故障未被解决的情况下，将待诊断的故障现象201发送至一个故障诊断专家70进行故障诊断，并接收故障诊断专家70返回的故障诊断结果202；
用户接口模块401还用于向用户终端50返回故障诊断专家70的故障诊断结果202，接收来自用户终端50的用户60对故障诊断专家70的故障诊断结果202的反馈203；
故障诊断模块402，还用于在用户60对故障诊断专家70的故障诊断结果202的反馈203指示故障已被解决的情况下，调整对待诊断的故障现象201的诊断策略，以及在用户60对故障诊断专家70的故障诊断结果202的反馈203指示故障已被解决的情况下，根据故障诊断专家70的故障诊断结果202更新故障诊断信息库204。
可选地，故障诊断专家70的故障诊断结果202包括产生待诊断的故障现象201的至少一个可能的故障，用户60对故障诊断专家70的故障诊断结果202的反馈203指示故障已被解决，且用户60对故障诊断专家70的故障诊断结果202的反馈203还包括：实际产生待诊断的故障现象201的故障；故障诊断模块402在根据故障诊断专家70的故障诊断结果202更新故障诊断信息库204时，具体用于：
在故障诊断信息库204中增加待诊断的故障现象201与用户60反馈的实际产生待诊断的故障现象201的故障之间的关联关系。
可选地，故障诊断结果202包括产生待诊断的故障现象201的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息；用户60对故障诊断结果202的反馈指示故障已被解决，且用户60对故障诊断结果202的反馈还包括：实际产生待诊断的故障现象201的故 障；故障诊断模块402在根据故障诊断结果202调整对待诊断的故障现象201的诊断策略时，具体用于：将实际产生待诊断的故障现象201的故障的概率增大。
可选地，用户接口模块401，还用于在接收来自一个用户终端50的一个用户60输入的一个待诊断的故障现象201之前，向用户终端50发送一个故障现象列表205，故障现象列表205中包括至少一个故障现象，用户接口模块401在接收来自用户终端50的用户60输入的待诊断的故障现象201时，具体用于接收来自用户终端50的用户60从故障现象列表205中选择的待诊断的故障现象201，故障诊断模块402在对待诊断的故障现象201进行故障诊断时，具体用于基于一个故障诊断信息库204对待诊断的故障现象201进行故障诊断，其中，故障诊断信息库204包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；或
用户接口模块401在接收来自一个用户终端50的一个用户60输入的待诊断的故障现象201时，具体用于接收来自用户终端50的用户60输入的待诊断的故障现象201的语义描述，故障诊断模块402在对待诊断的故障现象201进行故障诊断时，具体用于接收一个故障诊断专家70对待诊断的故障现象201的诊断结果。
图6所示的故障诊断装置40的其他可选实现方式可参考图2～图5中故障诊断装置40的实现，其中用户接口模块401用于与用户终端50进行交互，而故障诊断模块402用于进行故障诊断，访问故障诊断信息库204，调整故障诊断策略等。
图7为本发明实施例提供的故障诊断装置40的又一示意图。图7所示的故障诊断装置40可视为图6所示的故障诊断装置40的一种硬件实现方式。其中，至少一个存储器404，用于存储机器可读程序，至少一个处理器403，用于调用所述机器可读程序，执行前述各流程中故障诊断装置40所执行的方法。其中，图6中的各个模块：用户接口模块401、故障诊断模块402可视为存储器404中存储的程序模块或软件模块，在被处理器403调用后，执行前述各流程中故障诊断装置40所执行的方法。
图7所示的故障诊断装置40还可包括至少一个通信接口405，访问故障诊断信息库204、与用户终端50交互等。图6和图7所示的故障诊断装置40可部署在云上，则至少一个存储器404即可为云上的存储器，至少一个处理器403也可为云上的虚拟化的处理装置，比如虚拟机等。
图8为本发明实施例提供的用户终端50的一个示意图。如图8所示，该用户终端50可包括：
一个用户接口模块501，用于接收一个用户60输入的一个待诊断的故障现象201；
一个通信模块502，用于将待诊断的故障现象201发送至一个故障诊断装置40进行故障诊断，以及接收来自故障诊断装置40的针对待诊断的故障现象201的一个故障诊断结果202；
用户接口模块501，还用于将故障诊断结果202提供给用户60，以及接收用户60对故障诊断结果202的反馈203；
通信模块502，还用于将用户60对故障诊断结果202的反馈204发送至故障诊断装置40。
可选地，用户接口模块501在接收用户60对故障诊断结果202的反馈203时，还用于接收用户60反馈的实际产生待诊断的故障现象201的故障。
图8所示的用户终端50的其他可选实现方式可参考图2～图5中用户终端50的实现，其中用户接口模块501用于与用户60进行交互，通信模块502用于与故障诊断装置40交互。
图9为本发明实施例提供的用户终端50的又一示意图。图9所示的用户终端50可视为图8所示的用户终端50的一种硬件实现方式。其中，至少一个存储器504，用于存储机器可读程序，至少一个处理器503，用于调用所述机器可读程序，执行前述各流程中用户终端50所执行的方法。其中，图8中的各个模块：用户接口模块501、通信模块502可视为存储器504中存储的程序模块或软件模块，在被处理器503调用后，执行前述各流程中用户终端50所执行的方法。
图9所示的用户终端50还可包括至少一个显示器505，用于向用户60或故障诊断专家70显示信息。此外，还可包括一个通信接口506，用于与故障诊断装置40通信。
图10为本发明实施例中故障诊断信息库生成装置生成故障诊断信息库的流程图。
如图2所示，该方法可包括如下步骤：
S1001：设置故障条件。
S1002：运行数控机床的仿真模型。
S1003：回溯故障。
S1004：生成故障诊断信息库。
其中，步骤S1001中，设置数控机床10的至少一种故障条件1102。比如：设置数控机床10的伺服电机103的电流为0作为一种故障条件1102。
可选地，该至少一种故障条件1102可涉及数控机床10的所有部件，比如：图1中的PLC101、伺服驱动102、伺服电机103、耦合器104、轴承105、滚珠螺杆副106和编码器107。这样可遍历数控机床10的所有部件，产生的故障更全面。
可选地，设置的每一种故障条件1102仅涉及数控机床10的一个部件。
可选地，设置的至少一种故障条件1102中的部分或全部故障条件1102中的每一种均涉及数控机床10的至少两个部件。比如：共设置100种故障条件1102，其中有50种故障条件1102中的每一种均涉及到数控机床10的至少两个部件。这样可模拟各种实际的故障场景，实现上比传统的依赖于历史故障的记录以及专家经验生成的故障诊断信息库更灵活，故障覆盖更全面。
可选地，在设置故障条件1102时，可遍历所有可能的故障条件，以模拟所有可能出现的故障。
在步骤S1002中，在设置的每一种故障条件1102下，分别运行数控机床10的一个仿真模型以产生一条故障1103，并记录故障1103的至少一种故障现象1104。其中，一个故障可能会具有多个故障现象。在步骤S1002中，可记录故障1103的所有故障现象1104，或者记录故障1103的部分故障现象1104。
比如：设置故障条件1102为：伺服电机103的电流为0。在该故障条件1102下运行数控机床10的仿真模型，产生的故障1103为：伺服电机103无电流输出。该故障的故障现象1104为：滚珠螺杆副106中的螺母的转速降为0。在步骤S1002中记录伺服电机103故障的故障现象：滚珠螺杆副106中的螺母的转速降为0。
在步骤S1003中，对于记录的每一种故障现象1104，回溯产生该故障现象1104的至少一种可能的故障1103，以建立该故障现象1104与产生该故障现象1104的至少一种可能的故障1103之间的关联关系。
其中，可回溯产生该故障现象1104的所有可能的故障1103，也可以回溯产生该故障现象1104的部分可能的故障1103。其中，建立的故障现象1104与故障1103之间的关联关系可如图3中所示，对于故障现象1104(2)，可由故障1103(1h)产生该故障现象1104，而故障1103(1h)可直接或间接由故障1103(12)引起，而故障1103(12)由故障1103(11)引起，而故障1103(11)由故障1103(1)引起。此外，故障现象1104(2)还可能由故障1103(21)产生，而故障1103(21)可由故障1103(1)、故障1103(2)或故障1103(4)引起。
在步骤S1004中，根据步骤S1003中建立的至少一个关联关系生成数控机床10的一个故障诊断信息库204。
可选地，可根据建立的全部的关联关系或部分的关联关系生成数控机床10的故障诊断信息库204。生成的故障诊断信息库204的实现方式可有多种。
比如：如图3所示的故障传播模型。其中，1102为注入的故障条件。1103(1)～1103(m)为m种故障，其中m为正整数。一种故障可能会引发另一种故障，图10中1103(11)～1103(q1)、 1103(12)～1103(1h)、1103(3k)、1103(qs)、1103(11)～1103(q1)为由1103(1)～1103(m)为m种故障中的一个或多个引发的故障，其中，q、h、k、s为正整数。1104(1)～1104(n)为n种故障现象，其中n为正整数。其中，由一个故障现象1104到一个故障1103的过程，称为该故障现象1104的一条反向故障传播路径。比如：前述的由故障现象1104(2)到故障1103(1)的一条反向故障传播路径可为：1104(2)-＞1103(21)-＞1103(2)，表示故障现象1104(2)由故障故障1103(21)产生，而故障1103(21)可由故障1103(2)引起。因此，对于建立故障传播模型的情形，在步骤S1003中，建立的关联关系是一种故障现象1104的反向故障传播路径，而步骤S1004中是根据建立的反向故障传播路径生成故障传播模型，作为故障诊断信息库204。
生成的故障诊断信息库204也可包括一条条的故障用例，比如：
对于故障现象1104(2)而言，包括四条故障用例，分别为：
故障用例一、1104(2)-＞1103(21)-＞1103(1)，表示故障现象1104(2)由故障故障1103(21)产生，而故障1103(21)可由故障1103(1)引起。
故障用例二、1104(2)-＞1103(21)-＞1103(2)，表示故障现象1104(2)由故障故障1103(21)产生，而故障1103(21)可由故障1103(2)引起。
故障用例三、1104(2)-＞1103(21)-＞1103(4)，表示故障现象1104(2)由故障故障1103(21)产生，而故障1103(21)可由故障1103(4)引起。
故障用例四、1104(2)-＞1103(1h)-＞1103(12)-＞1103(11)-＞1103(1)，表示故障现象1104(2)由故障故障1103(1h)产生，而故障1103(1h)由故障1103(12)引起，而故障1103(12)由故障1103(11)引起，而故障1103(11)由故障1103(1)引起。
此外，生成的故障诊断信息库204也可以故障树的方式表示，这里不再赘述。
此外，还可设置每一种故障现象1104的语义描述1105并记录在第一故障诊断信息库204中，以及设置每一个故障1103的语义描述1106并记录在第一故障诊断信息库204中。这样便于在故障诊断时，根据用户输入的故障现象的语义描述确定对应的故障现象，进而由故障现象确定可能的故障，再将确定的故障的语义描述返回至用户。提高了故障诊断信息库的可用性，便于用户理解，对于用户更友好。
比如：前述的故障1103“伺服电机103无电流输出”对应的语义描述为“伺服电机故障”；期数的故障现象1104“滚珠螺杆副106中的螺母的转速降为0”对应的语义描述为“滚珠螺杆副106中的螺母不动”。
可选地，还可以在步骤S1001设置的至少一种故障条件1102每一种故障条件1102下，分别运行数控机床10的其他仿真模型以生成故障诊断信息库204。由于不同的仿真模型对一个数控机床10的仿真效果不同，因此利用不同的仿真模型生成的故障诊断信息库204中包含 的信息不尽一致，可以相互修正，以生成信息全面且准确的故障诊断信息库204。
生成的故障诊断信息库204可以大数据的方式组织、呈现。且可部署在云端，便于向故障诊断装置40提供丰富准确的故障信息。
本发明实施例中的故障可认为是某一个或几个部件自身发生了故障，而不是由其他部件故障而引发的故障。以前述的数控机床10的进给系统为例，正常情况下，PLC在编码器中的计算机程序的控制下，通过伺服驱动带动伺服电机转动，进而伺服电机通过耦合器、轴承带动滚珠螺杆副中的螺母转动。当前发生故障的故障现象是滚珠螺杆副中的螺母的转速降为0。产生该故障现象的根本原因是伺服电机故障。由于伺服电机故障会导致轴承停止转动，而轴承停止转动则无法带动滚珠螺杆副中的螺母转动。但此故障现象并不是由于轴承故障造成的，其根本原因，换言之实际发生的故障是伺服电机故障。若伺服电机未发生故障，而轴承发生了机械故障导致无法转动，那么故障现象也是滚珠螺杆副中的螺母的转速降为0，但故障的根本原因是轴承故障，而不是伺服电机故障。
因此，从这个意义上将，本发明实施例中的故障也可称为一个数控机床发生的一个特定故障的根本原因。
基于相同的技术构思，本发明实施例还提供了一种机器可读介质，该机器可读介质上存储用于使一机器执行如本文前述方法的机器可读指令。具体地，可以提供配有该机器可读介质的系统或者装置，在该机器可读介质上存储着实现上述实施例中任一实施例的功能的软件程序代码，且使该系统或者装置的计算机(或中央处理器(Central Processing Unit，CPU)或微处理器(Micro Processor Unit，MPU))读出并执行存储在存储介质中的程序代码。
在这种情况下，从存储介质读取的程序代码本身可实现上述实施例中任何一项实施例的功能，因此程序代码和存储程序代码的存储介质构成了本发明实施例的一部分。
用于提供程序代码的存储介质实施例包括软盘、硬盘、磁光盘、光盘(如只读光盘驱动器(Compact Disc Read-Only Memory，CD-ROM)、可录光盘(Compact Disk-Recordable，CD-R)、可擦写光盘(Compact Disk-ReWritable，CD-RW)、数字视盘(Digital Video Disc-Read Only Memory，DVD-ROM)、数字多功能光盘随机存储器(Digital Versatile Disc-Random Access Memory，DVD-RAM)、可重写型数字多功能光盘(Digital Versatile Disc±ReWritable，DVD±RW)等)、磁带、非易失性存储卡和只读存储器(Read-Only Memory，ROM)，以及云上的存储资源。可选择地，可以由通信网络从服务器计算机上或云上下载程序代码。
此外，应该清楚的是，不仅可以通过执行计算机所读出的程序代码，而且可以通过基于程序代码的指令使计算机上操作的操作系统等来完成部分或者全部的实际操作，从而实现上 述实施例中任意一项实施例的功能。
此外，可以理解的是，将由存储介质读出的程序代码写到插入计算机内的扩展板中所设置的存储器中或者写到与计算机相连接的扩展单元中设置的存储器中，随后基于程序代码的指令使安装在扩展板或者扩展单元上的CPU等来执行部分和全部实际操作，从而实现上述实施例中任一实施例的功能。
需要说明的是，上述各流程和各设备结构图中不是所有的步骤和模块都是必须的，可以根据实际的需要忽略某些步骤或模块。各步骤的执行顺序不是固定的，可以根据需要进行调整。上述各实施例中描述的设备结构可以是物理结构，也可以是逻辑结构，即，有些模块可能由同一物理实体实现，或者，有些模块可能分由多个物理实体实现，或者，可以由多个独立设备中的某些部件共同实现。
以上各实施例中，硬件单元可以通过机械方式或电气方式实现。例如，一个硬件单元可以包括永久性专用的电路或逻辑(如专门的处理器，FPGA或ASIC)来完成相应操作。硬件单元还可以包括可编程逻辑或电路(如通用处理器或其它可编程处理器)，可以由软件进行临时的设置以完成相应操作。具体的实现方式(机械方式、或专用的永久性电路、或者临时设置的电路)可以基于成本和时间上的考虑来确定。
上文通过附图和优选实施例对本发明进行了详细展示和说明，然而本发明不限于这些已揭示的实施例，基与上述多个实施例本领域技术人员可以知晓，可以组合上述不同实施例中的代码审核手段得到本发明更多的实施例，这些实施例也在本发明的保护范围之内。

Claims (20)

  1. 一个数控机床(10)的故障诊断方法，其特征在于，包括：
    接收来自一个用户终端(50)的一个用户(60)输入的一个待诊断的故障现象(201)；
    对所述待诊断的故障现象(201)进行故障诊断；
    向所述用户终端(50)返回一个故障诊断结果(202)；
    接收来自所述用户终端(50)的所述用户(60)对所述故障诊断结果(202)的反馈(203)；
    若所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障已被解决，则根据所述故障诊断结果(202)调整对所述待诊断的故障现象(201)的诊断策略。
  2. 如权利要求1所述的方法，其特征在于，对所述待诊断的故障现象(201)进行故障诊断，包括：基于一个故障诊断信息库(204)对所述待诊断的故障现象(201)进行故障诊断，其中，所述故障诊断信息库(204)包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；在接收来自所述用户终端(50)的所述用户(60)对所述故障诊断结果(202)的反馈(203)之后，所述方法还包括：若所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障未被解决，则
    将所述待诊断的故障现象(201)发送至一个故障诊断专家(70)进行故障诊断；
    接收所述故障诊断专家(70)返回的故障诊断结果(202)；
    向所述用户终端(50)返回所述故障诊断专家(70)的故障诊断结果(202)；
    接收来自所述用户终端(50)的所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)；
    若所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决，则根据所述故障诊断专家(70)的故障诊断结果(202)更新所述故障诊断信息库(204)并调整对所述待诊断的故障现象(201)的诊断策略。
  3. 如权利要求2所述的方法，其特征在于，所述故障诊断专家(70)的故障诊断结果(202)包括产生所述待诊断的故障现象(201)的至少一个可能的故障，所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决，且所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)还包括：实际产生所述待诊断的故障现象(201)的故障；根据所述第二故障诊断结果(202)更新所述故障诊断信息库(204)，包括：
    在所述故障诊断信息库(204)中增加所述待诊断的故障现象(201)与所述用户(60)反馈的实际产生所述待诊断的故障现象(201)的故障之间的关联关系。
  4. 如权利要求1或2所述的方法，其特征在于，所述故障诊断结果(202)包括产生所述待诊断的故障现象(201)的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息；所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障已被解决，且所述用户(60)对所述故障诊断结果(202)的反馈(203)还包括：实际产生所述待诊断的故障现象(201)的故障；根据所述故障诊断结果(202)调整对所述待诊断的故障现象(201)的诊断策略，包括：
    将实际产生所述待诊断的故障现象(201)的故障的概率增大。
  5. 如权利要求1所述的方法，其特征在于，
    在接收来自一个用户终端(50)的一个用户(60)输入的一个待诊断的故障现象(201)之前，还包括：向所述用户终端(50)发送一个故障现象列表(205)，所述故障现象列表(205)中包括至少一个故障现象；接收来自所述用户终端(50)的所述用户(60)输入的所述待诊断的故障现象(201)，包括：接收所述用户(60)从所述故障现象列表(205)中选择的所述待诊断的故障现象(201)；对所述待诊断的故障现象(201)进行故障诊断，包括：基于一个故障诊断信息库(204)对所述待诊断的故障现象(201)进行故障诊断，其中，所述故障诊断信息库(204)包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；或
    接收来自一个用户终端(50)的一个用户(60)输入的所述待诊断的故障现象(201)，包括：接收来自所述用户终端(50)的所述用户(60)输入的所述待诊断的故障现象(201)的语义描述；对所述待诊断的故障现象(201)进行故障诊断，包括：接收一个故障诊断专家(70)对所述待诊断的故障现象(201)的诊断结果。
  6. 一个数控机床(10)的故障诊断方法，其特征在于，包括：
    接收一个用户(60)输入的一个待诊断的故障现象(201)；
    将所述待诊断的故障现象(201)发送至一个故障诊断装置(40)进行故障诊断；
    接收来自所述故障诊断装置(40)的针对所述待诊断的故障现象(201)的一个故障诊断结果(202)；
    将所述故障诊断结果(202)提供给所述用户(60)；
    接收所述用户(60)对所述故障诊断结果(202)的反馈(203)；
    将所述用户(60)对所述故障诊断结果(202)的反馈(204)发送至所述故障诊断装置 (40)。
  7. 如权利要求6所述的方法，其特征在于，接收所述用户(60)对所述故障诊断结果(202)的反馈(203)，还包括：接收所述用户(60)反馈的实际产生所述待诊断的故障现象(201)的故障。
  8. 一个数控机床(10)的故障诊断装置(40)，其特征在于，包括：
    一个用户接口模块(401)，用于接收来自一个用户终端(50)的一个用户(60)输入的一个待诊断的故障现象(201)；
    一个故障诊断模块(402)，用于对所述待诊断的故障现象(201)进行故障诊断；
    所述用户接口模块(401)，还用于向所述用户终端(50)返回一个故障诊断结果(202)，接收来自所述用户终端(50)的所述用户(60)对所述故障诊断结果(202)的反馈(203)；
    所述故障诊断模块(402)，还用于在所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障已被解决的情况下，根据所述故障诊断结果(202)调整对所述待诊断的故障现象(201)的诊断策略。
  9. 如权利要求8所述的装置(40)，其特征在于，所述故障诊断模块(402)在对所述待诊断的故障现象(201)进行故障诊断时具体用于：基于一个故障诊断信息库(204)对所述待诊断的故障现象(201)进行故障诊断，其中，所述故障诊断信息库(204)包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系，
    所述故障诊断模块(402)，还用于在所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障未被解决的情况下，将所述待诊断的故障现象(201)发送至一个故障诊断专家(70)进行故障诊断，并接收所述故障诊断专家(70)返回的故障诊断结果(202)；
    所述用户接口模块(401)还用于向所述用户终端(50)返回所述故障诊断专家(70)的故障诊断结果(202)，接收来自所述用户终端(50)的所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)；
    所述故障诊断模块(402)，还用于在所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决的情况下，调整对所述待诊断的故障现象(201)的诊断策略，以及在所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决的情况下，根据所述故障诊断专家(70)的故障诊断结果(202)更新所述故障诊断信息库(204)。
  10. 如权利要求9所述的装置(40)，其特征在于，所述故障诊断专家(70)的故障诊断结果(202)包括产生所述待诊断的故障现象(201)的至少一个可能的故障，所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决，且所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)还包括：实际产生所述待诊断的故障现象(201)的故障；所述故障诊断模块(402)在根据所述故障诊断专家(70)的故障诊断结果(202)更新所述故障诊断信息库(204)时，具体用于：
    在所述故障诊断信息库(204)中增加所述待诊断的故障现象(201)与所述用户(60)反馈的实际产生所述待诊断的故障现象(201)的故障之间的关联关系。
  11. 如权利要求8或9所述的装置(40)，其特征在于，所述故障诊断结果(202)包括产生所述待诊断的故障现象(201)的至少一个可能的故障，以及每一个可能的故障发生的概率的指示信息；所述用户(60)对所述故障诊断结果(202)的反馈指示故障已被解决，且所述用户(60)对所述故障诊断结果(202)的反馈还包括：实际产生所述待诊断的故障现象(201)的故障；所述故障诊断模块(402)在根据所述故障诊断结果(202)调整对所述待诊断的故障现象(201)的诊断策略时，具体用于：
    将实际产生所述待诊断的故障现象(201)的故障的概率增大。
  12. 如权利要求8所述的装置(40)，其特征在于，
    所述用户接口模块(401)，还用于在接收来自一个用户终端(50)的一个用户(60)输入的一个待诊断的故障现象(201)之前，向所述用户终端(50)发送一个故障现象列表(205)，所述故障现象列表(205)中包括至少一个故障现象，所述用户接口模块(401)在接收来自所述用户终端(50)的所述用户(60)输入的所述待诊断的故障现象(201)时，具体用于接收来自所述用户终端(50)的所述用户(60)从所述故障现象列表(205)中选择的所述待诊断的故障现象(201)，所述故障诊断模块(402)在对所述待诊断的故障现象(201)进行故障诊断时，具体用于基于一个故障诊断信息库(204)对所述待诊断的故障现象(201)进行故障诊断，其中，所述故障诊断信息库(204)包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；或
    所述用户接口模块(401)在接收来自一个用户终端(50)的一个用户(60)输入的所述待诊断的故障现象(201)时，具体用于接收来自所述用户终端(50)的所述用户(60)输入的所述待诊断的故障现象(201)的语义描述，所述故障诊断模块(402)在对所述待诊断的 故障现象(201)进行故障诊断时，具体用于接收一个故障诊断专家(70)对所述待诊断的故障现象(201)的诊断结果。
  13. 一个用户终端(50)，其特征在于，包括：
    一个用户接口模块(501)，用于接收一个用户(60)输入的一个待诊断的故障现象(201)；
    一个通信模块(502)，用于将所述待诊断的故障现象(201)发送至一个故障诊断装置(40)进行故障诊断，以及接收来自所述故障诊断装置(40)的针对所述待诊断的故障现象(201)的一个故障诊断结果(202)；
    所述用户接口模块(501)，还用于将所述故障诊断结果(202)提供给所述用户(60)，以及接收所述用户(60)对所述故障诊断结果(202)的反馈(203)；
    所述通信模块(502)，还用于将所述用户(60)对所述故障诊断结果(202)的反馈(204)发送至所述故障诊断装置(40)。
  14. 如权利要求13所述的用户终端(50)，其特征在于，所述用户接口模块(501)在接收所述用户(60)对所述故障诊断结果(202)的反馈(203)时，还用于接收所述用户(60)反馈的实际产生所述待诊断的故障现象(201)的故障。
  15. 一个数控机床(10)的一个故障诊断系统(100)，其特征在于，包括：
    一个故障诊断信息库(204)，包括至少一个故障现象以及对于每一个故障现象，产生该故障现象的至少一种可能的故障之间的关联关系；
    一个故障诊断装置(40)，用于接收一个用户(60)输入的一个待诊断的故障现象(201)，基于所述故障诊断信息库(204)对所述待诊断的故障现象(201)进行故障诊断，向所述用户(60)返回一个故障诊断结果(202)，接收所述用户(60)对所述故障诊断结果(202)的反馈(203)，若所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障已被解决，则根据所述故障诊断结果(202)调整对所述待诊断的故障现象(201)的诊断策略。
  16. 如权利要求15所述的系统(100)，其特征在于，所述故障诊断装置(40)，还用于在接收所述用户(60)对所述故障诊断结果(202)的反馈(203)之后，若所述用户(60)对所述故障诊断结果(202)的反馈(203)指示故障未被解决，则
    将所述待诊断的故障现象(201)发送至一个故障诊断专家(70)进行故障诊断；
    接收所述故障诊断专家(70)返回的故障诊断结果(202)；
    向所述用户(60)返回所述故障诊断专家(70)的故障诊断结果(202)；
    接收所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)；
    若所述用户(60)对所述故障诊断专家(70)的故障诊断结果(202)的反馈(203)指示故障已被解决，则根据所述故障诊断专家(70)的故障诊断结果(202)更新所述故障诊断信息库(204)并调整对所述待诊断的故障现象(201)的诊断策略。
  17. 如权利要求15或16所述的系统(100)，其特征在于，所述系统(100)还包括所述故障诊断信息库(204)的一个生成装置(30)，用于
    设置所述数控机床(10)的至少一种故障条件；
    在设置的每一种故障条件下，分别运行所述数控机床(10)的一个仿真模型以产生一条故障，并记录所述故障的至少一种故障现象；
    对于记录的每一种故障现象，回溯产生该故障现象的至少一种可能的故障，以建立该故障现象与产生该故障现象的可能的故障之间的关联关系。
  18. 如权利要求15～17所述的系统(100)，所述系统(100)部署在云端。
  19. 一个数控机床(10)的故障诊断装置，其特征在于，包括：
    至少一个存储器，用于存储机器可读程序；
    至少一个处理器，用于调用所述机器可读程序，执行如权利要求1～7任一项所述的方法。
  20. 机器可读介质，其特征在于，所述机器可读介质上存储有机器可读指令，所述机器可读指令在被至少一个处理器执行时，使所述至少一个处理器执行权利要求1～7任一项所述的方法。
PCT/CN2017/104947 2017-09-30 2017-09-30 一种数控机床的故障诊断方法和装置 WO2019061481A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
US16/651,642 US11474495B2 (en) 2017-09-30 2017-09-30 Fault diagnosis method and apparatus for numerical control machine tool
EP17927179.6A EP3683640B1 (en) 2017-09-30 2017-09-30 Fault diagnosis method and apparatus for numerical control machine tool
PCT/CN2017/104947 WO2019061481A1 (zh) 2017-09-30 2017-09-30 一种数控机床的故障诊断方法和装置
CN201780094673.XA CN111356964A (zh) 2017-09-30 2017-09-30 一种数控机床的故障诊断方法和装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/104947 WO2019061481A1 (zh) 2017-09-30 2017-09-30 一种数控机床的故障诊断方法和装置

Publications (1)

Publication Number Publication Date
WO2019061481A1 true WO2019061481A1 (zh) 2019-04-04

Family

ID=65902678

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104947 WO2019061481A1 (zh) 2017-09-30 2017-09-30 一种数控机床的故障诊断方法和装置

Country Status (4)

Country Link
US (1) US11474495B2 (zh)
EP (1) EP3683640B1 (zh)
CN (1) CN111356964A (zh)
WO (1) WO2019061481A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI704435B (zh) * 2019-08-23 2020-09-11 國立中正大學 在啟動工具機之後進行模擬確認的加工方法與加工系統
CN113031560A (zh) * 2021-03-04 2021-06-25 徐州徐工施维英机械有限公司 故障诊断方法、装置和泵车
WO2022032684A1 (en) * 2020-08-14 2022-02-17 Siemens Aktiengesellschaft A method, device, system and storage medium for fault diagnosis and solution recommendation

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3258661B1 (en) * 2016-06-16 2020-11-18 ABB Schweiz AG Detection of abnormal configuration changes
US11209795B2 (en) 2019-02-28 2021-12-28 Nanotronics Imaging, Inc. Assembly error correction for assembly lines
US10481579B1 (en) 2019-02-28 2019-11-19 Nanotronics Imaging, Inc. Dynamic training for assembly lines
CN113074770A (zh) * 2021-04-02 2021-07-06 广西玉柴机器股份有限公司 一种数字控制的手轮断线测试方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102183945A (zh) * 2011-01-17 2011-09-14 武汉理工大学 一种多功能电控汽车远程故障诊断系统
CN102571987A (zh) * 2012-02-28 2012-07-11 中国人民解放军军事交通学院 基于Web的汽车远程故障诊断专家系统
JP2014081880A (ja) * 2012-10-18 2014-05-08 Nec Computertechno Ltd 診断回路診断装置、診断回路診断システム、診断回路診断方法、及び、診断回路診断プログラム
CN105391579A (zh) * 2015-11-25 2016-03-09 国家电网公司 基于关键告警集和监督分类的电力通信网故障定位方法
CN106254139A (zh) * 2016-08-30 2016-12-21 四川长虹网络科技有限责任公司 一种故障收集处理交互方法
CN106598020A (zh) * 2016-11-02 2017-04-26 中国人民解放军济南军区72465部队 一种基于bit和案例融合的装备故障诊断方法及系统

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6691066B1 (en) * 2000-08-28 2004-02-10 Sirf Technology, Inc. Measurement fault detection
JP3780508B2 (ja) * 2002-03-22 2006-05-31 株式会社ジェイテクト 工作機械の異常診断装置、異常診断方法及び異常診断プログラム
US7209860B2 (en) 2003-07-07 2007-04-24 Snap-On Incorporated Distributed expert diagnostic service and system
US7373225B1 (en) * 2005-07-25 2008-05-13 Snap-On Incorporated Method and system for optimizing vehicle diagnostic trees using similar templates
GB2442022A (en) * 2006-07-11 2008-03-26 Selex Comm Ltd A system for examining effects and proposing consequential actions
CN101192997A (zh) * 2006-11-24 2008-06-04 中国科学院沈阳自动化研究所 分布式设备远程状态监测与故障诊断系统
CN102055604B (zh) * 2009-11-05 2012-12-05 中国移动通信集团山东有限公司 一种故障定位方法及其系统
CN101753382B (zh) * 2010-01-25 2013-07-24 浪潮通信信息系统有限公司 一种自适应网络故障监控定位安全模型的构建方法
CN102146845B (zh) * 2011-01-28 2013-07-03 中国人民解放军海军工程大学 Petri网图形化方法及在船用燃气轮机故障诊断上的应用
CN102819239B (zh) * 2011-06-08 2014-09-17 同济大学 一种数控机床智能故障诊断方法
CN103778044B (zh) * 2012-10-23 2017-05-17 伊姆西公司 用于系统故障诊断和修复的方法和装置
CN102937798B (zh) * 2012-11-30 2015-02-18 重庆大学 一种人机结合的数控机床故障信息采集方法
CN104035433B (zh) * 2014-05-30 2017-01-11 北京必可测科技股份有限公司 工业设备的远程精密诊断及维护系统和方法
CN104506338A (zh) * 2014-11-21 2015-04-08 河南中烟工业有限责任公司 一种基于决策树的工业以太网网络故障诊断专家系统
CN105204436B (zh) * 2015-08-26 2016-10-26 山东省计算中心（国家超级计算济南中心） 基于分级预警的数控机床故障诊断方法
CN106557773B (zh) * 2015-09-25 2020-04-24 北京宝沃汽车有限公司 一种车辆故障诊断的方法及系统
CN205721347U (zh) * 2016-04-15 2016-11-23 宝沃汽车（中国）有限公司 车辆故障诊断系统
CN105956330B (zh) * 2016-05-31 2019-03-22 山东中烟工业有限责任公司 基于现场数据的产品工艺质量预测模型的建立方法及系统
CN106528723A (zh) * 2016-10-27 2017-03-22 重庆大学 基于故障树的数控机床故障消除方案判别指示方法
CN107133402A (zh) * 2017-05-03 2017-09-05 山东中烟工业有限责任公司 一种基于熵权topsis法的卷烟设备差异化轮保方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102183945A (zh) * 2011-01-17 2011-09-14 武汉理工大学 一种多功能电控汽车远程故障诊断系统
CN102571987A (zh) * 2012-02-28 2012-07-11 中国人民解放军军事交通学院 基于Web的汽车远程故障诊断专家系统
JP2014081880A (ja) * 2012-10-18 2014-05-08 Nec Computertechno Ltd 診断回路診断装置、診断回路診断システム、診断回路診断方法、及び、診断回路診断プログラム
CN105391579A (zh) * 2015-11-25 2016-03-09 国家电网公司 基于关键告警集和监督分类的电力通信网故障定位方法
CN106254139A (zh) * 2016-08-30 2016-12-21 四川长虹网络科技有限责任公司 一种故障收集处理交互方法
CN106598020A (zh) * 2016-11-02 2017-04-26 中国人民解放军济南军区72465部队 一种基于bit和案例融合的装备故障诊断方法及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3683640A4 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI704435B (zh) * 2019-08-23 2020-09-11 國立中正大學 在啟動工具機之後進行模擬確認的加工方法與加工系統
WO2022032684A1 (en) * 2020-08-14 2022-02-17 Siemens Aktiengesellschaft A method, device, system and storage medium for fault diagnosis and solution recommendation
CN113031560A (zh) * 2021-03-04 2021-06-25 徐州徐工施维英机械有限公司 故障诊断方法、装置和泵车

Also Published As

Publication number Publication date
CN111356964A (zh) 2020-06-30
US20200310380A1 (en) 2020-10-01
EP3683640A4 (en) 2021-04-21
US11474495B2 (en) 2022-10-18
EP3683640B1 (en) 2023-03-15
EP3683640A1 (en) 2020-07-22

Similar Documents

Publication Publication Date Title
WO2019061481A1 (zh) 一种数控机床的故障诊断方法和装置
CN111164524B (zh) 一种数控机床的故障诊断信息库的生成方法和装置
CN108021505B (zh) 数据上线方法、装置和计算机设备
CN104460360A (zh) 控制系统模拟系统和方法
US10437851B2 (en) Synchronizing object in local object storage node
CN111159893A (zh) 一种基于数字孪生的故障复现及预测系统
EP2500791A1 (en) System and method of simulating input/output modules in a control system
CN111108481B (zh) 故障分析方法及相关设备
WO2015029654A1 (en) Computer-implemented operator training system and method of controlling the system
CN105630661A (zh) 用于自动化跨系统程序调试的方法和装置
CN114003428A (zh) 用于分布式系统的故障预警方法和装置
US20210117593A1 (en) Configurable digital twin
US10152039B2 (en) Method and apparatus for the display of multiple errors on a human-machine interface
CN108241404A (zh) 一种获取离线操作时间的方法、装置及电子设备
US20230134186A1 (en) Machine learning data generation device, machine learning model generation method, and storage medium
CN116704870A (zh) 工业产线的演示系统、方法、设备及其介质
JP6997996B2 (ja) 情報処理方法、情報処理装置、プログラム、及び情報処理システム
CN104765616B (zh) 一种自动生成io模型的方法及系统
CN110728041B (zh) 信息处理方法及电子设备
RU2447488C1 (ru) Способ и система построения модели нарушенного функционирования технического объекта и машиночитаемый носитель
CN113961571B (zh) 一种基于数据探针的多模态数据感知方法及装置
WEI et al. Optimization of industrial maintenance processes with Augmented Reality
Vizuete IIoT based Augmented Reality for Factory Data Collection and Visualization
JP2022079529A (ja) 画像データの修正方法、修正装置、電子機器、記憶媒体、コンピュータプログラムおよび自動運転車両
CN116467111A (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: 17927179

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017927179

Country of ref document: EP

Effective date: 20200417