Equipment fault diagnosis method and system, storage medium and electronic device

Abstract

The invention discloses an equipment fault diagnosis method and system, a storage medium and an electronic device, and relates to the technical field of industrial automation, and the equipment fault diagnosis method comprises the steps: determining a target service instance which is distributed when equipment registration service is completed for current equipment in a basic service module; a target service module to which the service instance belongs is utilized to analyze device data of the current device, whether the current device has a fault is determined according to an analysis result, the target service module belongs to the upper layer service module, and the target service module belongs to the lower layer service module. The upper-layer service module at least comprises one of an equipment state acquisition service module, an asynchronous message service module, an equipment trend service module, a historical data persistence service module and an equipment state analysis service module, and by adopting the technical scheme, the technical problem of low equipment fault diagnosis efficiency is solved.

Description

Technical Field

[0001] The present application relates to the field of industrial automation technology, and in particular to a method, system, storage medium and electronic device for diagnosing equipment failure. Background Art

[0002] At present, with the continuous improvement of the automation level of industrial equipment, the equipment complexity and equipment integration of industrial equipment are also increasing, resulting in equipment fault diagnosis and equipment maintenance work becoming more and more difficult.

[0003] Traditional fault diagnosis methods include visual inspection of the equipment's exterior to look for obvious damage, wear, leakage, etc., auditory inspection by listening to the sound of the equipment during operation to determine whether there is abnormal noise and to look for problems with bearings, gears and other components, and tactile inspection by touching the surface of the equipment to feel abnormal temperature or vibration and to look for overheating or imbalance of certain parts of the equipment. However, these methods all rely on manual experience and regular maintenance, which are not only inefficient, but also difficult to accurately predict and prevent equipment failures. Although the industry already has integrated tools for fault diagnosis, these integrated tools have low concurrent processing efficiency due to functional coupling, and untimely monitoring will slow down the speed of diagnosing equipment failures.

[0004] Therefore, in the related art, there is a technical problem of low efficiency in equipment fault diagnosis.

[0005] With regard to the technical problem of low efficiency in equipment fault diagnosis in related technologies, no effective solution has been proposed yet. Summary of the invention

[0006] The embodiments of the present application provide a method, system, storage medium and electronic device for diagnosing equipment faults, so as to at least solve the technical problem of low efficiency in equipment fault diagnosis in the related art.

[0007] According to an embodiment of the present application, a method for diagnosing a device fault is provided, which is applied to a device fault diagnosis system, wherein the device fault diagnosis system includes multiple service modules, and the multiple service modules include at least a grassroots service module and an upper-layer service module. The grassroots service module provides grassroots services for the upper-layer service module, including: determining a target service instance distributed when completing a device registration service for a current device in the grassroots service module; analyzing device data of the current device using the target service module to which the service instance belongs, and determining whether the current device has a fault based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: a device status acquisition service module, an asynchronous message service module, a device trend service module, a historical data persistence service module, and a device status analysis service module.

[0008] In an exemplary embodiment, determining the target service instance to be distributed when completing the device registration service for the current device in the grassroots service module includes: distributing a newly registered service instance to the current device when the current device performs the device registration service; if it is determined that the current device has an instance tag, and the instance tag is used to indicate that the service instance to which the current device belongs is a first service instance, then based on a release instruction of the grassroots service module, releasing the current device from the occupation process of the first service instance; obtaining a second service instance from the newly registered service instance, determining the second service instance as the target service instance, and distributing the successfully released current device to the second service instance according to a release signal indicating that the current device is successfully released.

[0009] In an exemplary embodiment, the target service module is the device status acquisition service module, and the device data of the current device is analyzed using the target service module to which the service instance belongs, and whether the current device has a fault is determined based on the analysis result, including: obtaining the device control tag of the current device from the grassroots service module through the device status acquisition module; storing the operating status data of the current device acquired by the device status acquisition module in the first message queue corresponding to the device control tag, wherein the device data includes the operating status data of the current device, and the first message queue is created in the grassroots service module; using the device status acquisition module to subscribe to the first notification message of the first message queue; determining that the current device has a fault when it is determined that the first notification message has an abnormal notification message; determining the fault handling measures based on the device protocol used when the device status acquisition module acquires the operating status data of the current device, wherein the abnormal notification message is used to indicate that the operating status data of the current device has an abnormality.

[0010] In an exemplary embodiment, the method also includes: determining a data transmission channel provided by the asynchronous message service module for other service modules to perform data transmission, wherein the other service modules represent modules in the upper-layer service modules other than the asynchronous message service module, one end of the data transmission channel is connected to the device status acquisition service module, and the other end of the transmission channel is connected to the remaining service modules, and the remaining service modules include at least one of the following: a device trend service module, a historical data persistence service module, and a device status analysis service module; and sending the device data from the device status acquisition service module to the remaining service modules through the data transmission channel.

[0011] In an exemplary embodiment, the target service module is the device trend service module, and the device data of the current device is analyzed using the target service module to which the service instance belongs, and whether the current device has a fault is determined based on the analysis result of the analysis, including: obtaining the device control tag of the current device from the grassroots service module through the device trend service module, and subscribing to the second notification message of the second message queue corresponding to the device control tag; when it is determined that the second notification message is used to indicate an update of the second message queue, the trend queue maintained by the device trend service module is updated according to the update message in the second message queue to obtain an updated trend queue, and the updated trend queue is synchronized to a relational database to perform data persistence operations on the updated trend queue; when it is determined that the change trend of the current trend queue maintained by the device trend service module is used to indicate that the current device has a fault, a persistent trend queue corresponding to the current trend queue is obtained from the relational database, and the current trend queue is restored using the persistent trend queue.

[0012] In an exemplary embodiment, the method also includes: obtaining the device control tag of the current device from the grassroots service module through the historical data persistence service module, and subscribing to the third message queue corresponding to the device control tag; and persistently storing the device data stored in the third message queue in a file appending manner.

[0013] In an exemplary embodiment, the target service module is the device status analysis service module, which uses the target service module to which the service instance belongs to analyze the device data of the current device, and determines whether the current device has a fault based on the analysis result, including: obtaining the real-time device status value of the current device through the device status analysis service module; determining the characteristic status value range set for the current device; and determining that the current device has a fault when it is determined that the real-time device status value does not fall within the characteristic status value range of the current device.

[0014] In an exemplary embodiment, determining the characteristic state value range set for the current device includes: collecting device state values ​​within the normal operation cycle of the current device according to a collection cycle to obtain a set of initial state values ​​corresponding to the collection cycle; setting the average value of the set of initial state values ​​as the baseline value of the current device, setting the maximum value of the set of initial state values ​​as the maximum characteristic state value of the characteristic state value range, and setting the minimum value of the set of initial state values ​​as the minimum characteristic state value of the characteristic state value range, thereby determining the characteristic value range.

[0015] According to another aspect of an embodiment of the present application, a device failure diagnosis system is also provided, and the device failure diagnosis system is used to execute the above-mentioned device failure diagnosis method.

[0016] According to another aspect of the embodiments of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the above-mentioned device fault diagnosis method when running.

[0017] According to another aspect of the embodiments of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the device failure diagnosis method through the computer program.

[0018] According to another embodiment of the present application, a computer program product is provided, including a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0019] In an embodiment of the present application, a device fault diagnosis system including multiple service modules is designed, wherein the multiple service modules include at least a base service module and an upper service module, wherein the base service module provides base services for the upper service module, and then uses the device fault diagnosis system to determine the target service instance distributed when the device registration service is completed for the current device in the base service module; the device data of the current device is analyzed using the target service module to which the service instance belongs, and whether the current device has a fault is determined based on the analysis result of the analysis, wherein the target service module belongs to the upper service module, and the upper service module includes at least one of the following: a device status acquisition service module, an asynchronous message service module, a device trend service module, Service module, historical data persistence service module, equipment status analysis service module; adopting the above technical scheme, an efficient and real-time equipment fault diagnosis strategy is proposed, which can completely decouple the various equipment functions required for equipment fault diagnosis into multiple independent services. Each service has independent and complete operation capabilities. This completely independent service model improves the modularity of the system. While improving the diagnostic efficiency of equipment faults, it also provides great convenience for subsequent service expansion and maintenance. Even if a service fails, it will not affect the normal operation of other services. It also improves the high reliability and stability of the system, has important practical significance and application value, solves the technical problem of low efficiency in equipment fault diagnosis, and improves the diagnostic efficiency of equipment faults. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0021] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0022] Figure 1 It is a hardware environment diagram of a method for diagnosing a device failure in an embodiment of the present application;

[0023] Figure 2 is a flow chart of a method for diagnosing a device failure according to an embodiment of the present application;

[0024] Figure 3 is a schematic diagram of data flow based on a message service according to an embodiment of the present application;

[0025] Figure 4 It is a structural block diagram of a device fault diagnosis system according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] According to one aspect of an embodiment of the present application, a method for diagnosing a device failure is provided. The method for diagnosing a device failure is widely used in industrial equipment control application scenarios such as fault diagnosis of industrial equipment, automated control equipment, semi-automated control equipment, etc. Optionally, in this embodiment, the method for diagnosing a device failure can be applied to Figure 1 In the hardware environment composed of industrial equipment 102 and server 104 shown in FIG. Figure 1 As shown, the server 104 is connected to the industrial device 102 via a network, and can be used to provide services (such as application services, etc.) for the terminal or a client installed on the terminal. A database can be set on the server or independently of the server to provide data storage services for the server 104. Cloud computing and / or edge computing services can be configured on the server or independently of the server to provide data computing services for the server 104.

[0029] The above network may include but is not limited to at least one of the following: wired network, wireless network. The above wired network may include but is not limited to at least one of the following: wide area network, metropolitan area network, local area network, and the above wireless network may include but is not limited to at least one of the following: WIFI (Wireless Fidelity), Bluetooth. The industrial equipment 102 may not be limited to mechanical processing equipment such as lathes, milling machines, grinders, drilling machines, CNC machine tools, automation equipment such as robot arms, automated assembly lines, automatic welding machines, conveyor belts, conveyors, elevators, automatic guided vehicles, etc., packaging equipment such as balers, sealing machines, labeling machines, injection molding machines and blow molding machines for the production of plastic products, bending machines, shearing machines, stamping machines, metal processing equipment, etc., generators, transformers, motors, etc., chemical equipment such as reactors, distillation towers, centrifuges, etc., textile equipment such as looms, spinning machines, dyeing machines, etc., food processing equipment such as mixers, cutting machines, and baking machines, construction machinery such as excavators, cranes, concrete mixers, pressure gauges, thermometers, viscometers, etc., measurement and testing equipment Handheld equipment: handheld diagnostic tools such as multimeters, clamp ammeters, infrared thermal imagers, handheld measuring tools such as handheld laser rangefinders, digital levels, angle meters, handheld communication devices such as walkie-talkies and handheld terminals (for data collection and transmission), handheld monitoring equipment such as portable monitors and data loggers, handheld operating tools such as handheld electric drills, screwdrivers, wrenches, etc., handheld detection equipment such as vibration meters, sound level meters, ultrasonic leak detectors, handheld computers and data terminals for on-site data input, analysis and reporting, handheld navigation equipment such as GPS locators and map navigation equipment, handheld lighting equipment such as flashlights and headlamps for on-site lighting, handheld safety equipment such as gas detectors and radiation detectors, handheld maintenance tools such as cleaning tools and lubrication tools.

[0030] In this embodiment, a method for diagnosing equipment failure is provided, which is applied to the above industrial equipment. Figure 2 : is a flow chart of a method for diagnosing a device failure according to an embodiment of the present application, the flow chart includes the following steps:

[0031] Step S202, determining a target service instance distributed when completing a device registration service for the current device in the base service module;

[0032] Furthermore, in the device fault diagnosis system, the grassroots service provided by the grassroots service module is, for example, a device registration service, and the grassroots service module can be understood as a device registration service module. Figure 3 As shown, the device registration service module provides registration services to the upper layer service module.

[0033] Step S204, using the target service module to which the service instance belongs to analyze the device data of the current device, and determining whether the current device has a fault based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: device status acquisition service module, asynchronous message service module, device trend service module, historical data persistence service module, device status analysis service module.

[0034] Through the above steps, the target service instance distributed when the device registration service is completed for the current device in the basic service module is determined by using the device fault diagnosis system; the device data of the current device is analyzed by using the target service module to which the service instance belongs, and whether the current device has a fault is determined according to the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: a device status acquisition service module, an asynchronous message service module, a device trend service module, a historical data persistence service module, and a device status analysis service module; adopting the above technical solution, an efficient and real-time device fault diagnosis strategy is proposed, which can completely decouple the various device functions required for device fault diagnosis into multiple independent services, each service has independent and complete operation capabilities, and this completely independent service mode improves the modularity of the system, while improving the diagnostic efficiency of device faults, it also provides great convenience for subsequent service expansion and maintenance, even if a service fails, it will not affect the normal operation of other services, and also improves the high reliability and stability of the system, which has important practical significance and application value, solves the technical problem of low efficiency of device fault diagnosis, and improves the diagnostic efficiency of device faults.

[0035] Based on the decoupling characteristics of the service functions of the above-mentioned system, this application further realizes the high flexibility and composability of services. In practical applications, each device service can be freely expanded horizontally or vertically according to the specific needs of the site. Whether it is to increase the number of services or improve the performance of services, it can be easily achieved to meet the monitoring needs in different scenarios. At the same time, multiple services can also be arbitrarily combined into a new service. This combination method not only simplifies the configuration and management of the system, but also enables the system to respond quickly and accurately under high concurrency and high real-time requirements, thereby monitoring and controlling the equipment in real time and efficiently, greatly improving the adaptability and scalability of the system, enabling it to cope with various complex monitoring scenarios.

[0036] In an exemplary embodiment, the implementation process of determining the target service instance to be distributed when the device registration service is completed for the current device in the grassroots service module in the above-mentioned step S202 specifically includes: distributing a newly registered service instance to the current device when the current device performs the device registration service; if it is determined that the current device has an instance tag, and the instance tag is used to indicate that the service instance to which the current device belongs is a first service instance, then based on the release instruction of the grassroots service module, the current device is released from the occupation process of the first service instance; a second service instance is obtained from the newly registered service instance, the second service instance is determined as the target service instance, and the successfully released current device is distributed to the second service instance according to the release signal of the successful release of the current device.

[0037] Optionally, when it is determined that the current device does not have an instance tag, the newly registered service instance is directly distributed to the current device.

[0038] Specifically, the device registration service module can also implement the following functions: basic information management function of the device. The basic information of the device includes but is not limited to the name, code (globally unique), location, and type. When a device is added or deleted, a Topic (topic) in the message queue is created for the device synchronously. Among them, two Topics can be created for each device in the message queue, which are the Topic for message push and subscription and the Topic for device control.

[0039] It is understandable that a message queue is a middleware for asynchronous communication between applications, mainly used to transmit messages in a distributed system. In a message queue, messages are classified according to certain rules, which are called "Topics". Topics can also be regarded as a mechanism for organizing and classifying messages in a message queue, which helps to achieve asynchronous communication, decoupling and scalability between applications. By using Topics reasonably, the flexibility and maintainability of distributed systems can be improved.

[0040] In the message queue of this application, Topic can be understood as a label used to identify a class of messages with the same characteristics or types. By using Topic, producers (the party sending messages) can send messages according to a specific topic, and consumers (the party receiving messages) can subscribe to topics of interest to receive corresponding messages.

[0041] Furthermore, using Topics, you can classify messages, making them easier to manage and search. For example, in an e-commerce system, order messages, inventory messages, and user messages can be set as different Topics.

[0042] And in the message queue, the mode in which the producer publishes messages to a specific Topic and the consumer subscribes to the Topic of interest to receive messages helps to achieve decoupling, that is, the producer and consumer do not need to interact directly, but communicate indirectly through the Topic.

[0043] Topic settings are very flexible. You can set different topics according to business needs, or combine multiple topics into more complex rules to meet different communication needs.

[0044] In a distributed system, Topics can be used to help achieve message scalability. For example, by adding more consumers to subscribe to the same Topic, the concurrency and throughput of message processing can be improved.

[0045] Furthermore, in this application, a Topic can be set to implement message filtering. Consumers can only receive messages that meet specific conditions based on specific Topic rules.

[0046] It should be noted that different message queue systems may support different Topic modes, such as Point-to-Point mode and Publish / Subscribe mode. In the Publish / Subscribe mode, the use of Topic is particularly common.

[0047] Optionally, the device registration service module can also implement a distribution policy management function for the device.

[0048] All device services provided by the upper-level service module (such as status collection service, device operation trend service, device status analysis service, etc.) must be registered with the registration service when they are started, and each device service maintains a heartbeat with the registration service in a long connection. Each device service sends a heartbeat to the registration service regularly to indicate its survival status.

[0049] At the same time, when the registration service does not receive a heartbeat after the timeout, it will actively inquire about the survival status of the corresponding service. If no effective response is received after a certain period of time, the service instance of the corresponding service is considered abnormal, and it will be removed from the registration service list, and other device services will be notified at the same time.

[0050] The registration service provided by the device registration service module can distribute multiple devices to the same service (for example, if there are 100 devices and 5 device status collection services, each service can be distributed to 20 devices). Each device is responsible for data processing by a service instance.

[0051] When a new service instance is added, the device registration service module will redistribute the devices, and try to ensure that the existing devices remain unchanged, and evenly extract a portion of the devices from the device list of other services to the new instance. When the service instance is reduced, the device registration service module will distribute the devices that are reduced in instance management to the existing service instance.

[0052] In this application, a device cannot be managed by two service instances at the same time, so the following strategy is formulated: when a new service instance is registered, it means that the newly registered service instance applies to control the device, and the device registration service module will distribute the device. When the device is distributed, the service instance to which the device belongs will be marked. At the same time, if the device is already occupied by other service instances, the device registration service module will notify the corresponding service instance to release the device. If the service instance occupying the device receives the notification while processing the business, the service instance occupying the device will release the device after processing the current business of the device, and notify the device registration service module that the device has been released.

[0053] To prevent the service instance occupying the device from continuing to process the next business process, the instance tag of the current device must be determined before the service instance occupying the device processes the business process. When it is found that the service instance occupying the device is inconsistent with the service instance of the current device, the service instance occupying the device actively abandons the process. When the device registration service module has not received a release signal after a certain period of time, it is assumed that the device has been released. When the device registration service module successfully obtains the released device, it can formally transfer the device to the newly registered service instance, thereby ensuring that a device is only processed by one instance.

[0054] In the above embodiments, an innovative device management strategy in a distributed environment is proposed, aiming to provide an efficient distribution mechanism for core device class control services. This strategy not only has significant use value, but also can effectively optimize the device management process in a distributed environment and improve overall management efficiency.

[0055] Optionally, the device registration service module also has an extension function, that is, considering that the amount of data processed by different devices may be different, different numbers of devices can be distributed to different instances based on computer performance and the data processing capacity of the device, thereby realizing the expansion of the above distributed algorithm.

[0056] In an exemplary embodiment, the target service module is the device status acquisition service module, and the technical solution of analyzing the device data of the current device using the target service module to which the service instance belongs in the above step S204 and determining whether the current device has a fault based on the analysis result is further described, specifically including: obtaining the device control tag of the current device from the grassroots service module through the device status acquisition module; storing the operating status data of the current device acquired by the device status acquisition module in the first message queue corresponding to the device control tag, wherein the device data includes the operating status data of the current device, and the first message queue is created in the grassroots service module; using the device status acquisition module to subscribe to the first notification message of the first message queue; determining that the current device has a fault when it is determined that the first notification message has an abnormal notification message; determining the fault handling measures according to the device protocol used when the device status acquisition module acquires the operating status data of the current device, wherein the abnormal notification message is used to indicate that the operating status data of the current device has an abnormality.

[0057] Among them, the above-mentioned fault handling measures can be, for example, setting the water valve on / off, adjusting the feeding port to increase or decrease the feeding amount, adjusting the motor to increase or decrease the speed, etc., and this application does not impose any restrictions on this.

[0058] It can be understood that the above-mentioned device status collection service module is used to provide device status collection services for the current device (ie Figure 3 The device status collection service module can interact directly with the devices of various manufacturers, for example, by installing sensors or based on the existing protocols of the devices of various manufacturers, to collect the operating status data of the devices in real time, including parameters such as temperature, humidity, resistance, pressure, amplitude, current, voltage, power, noise, etc., and can also control related devices according to the protocol.

[0059] The specific device status collection service module can realize the following functions: device status collection function.

[0060] Based on the device status collection service provided by the device status collection service module, the control right of the device can be dynamically obtained from the device registration service module, and then the Topic of the corresponding device can be created in the message queue. Different devices have globally unique Topics. After the device status collection service module obtains the corresponding device control right (that is, obtains the device control Topic), it starts to collect the status data of the device and sends the collected data to the message queue. In this embodiment, the process from collecting data to sending it to the message queue only takes a few microseconds to complete, with very high real-time performance, and due to the single function, the number of devices that can be carried is very large. At the same time, considering that in a distributed situation, the service may be deployed in multiple instances, and the devices controlled by different service instances are uniformly managed by the device registration service module.

[0061] Based on the above content, this application proposes a global decoupled equipment monitoring strategy based on message queues. This strategy decouples the monitoring and control functions of the equipment into multiple completely independent service modules. Each module can run independently and interact in real time through message queues. It can monitor the equipment comprehensively and efficiently and improve the real-time performance of industrial equipment monitoring.

[0062] Furthermore, the device status collection service module can also realize the device control function. By dynamically subscribing to the device's message queue through the device status collection service module, different processing methods can be provided according to the relevant protocols of the device when collecting data when the abnormal topic of the device is obtained. These processing methods are related to actual business scenarios such as water valve opening / closing, increasing or decreasing the feeding amount of the feeding port, and increasing or decreasing the speed of the motor, and no specific design is made here.

[0063] In an exemplary embodiment, the following technical solution is further proposed: determining a data transmission channel provided by the asynchronous message service module for other service modules to perform data transmission, wherein the other service modules represent modules in the upper-layer service modules other than the asynchronous message service module, one end of the data transmission channel is connected to the device status acquisition service module, and the other end of the transmission channel is connected to the remaining service modules, and the remaining service modules include at least one of the following: device trend service module, historical data persistence service module, device status analysis service module; the device data is sent from the device status acquisition service module to the remaining service modules through the data transmission channel.

[0064] In this embodiment, the asynchronous message service module serves as a transfer station for the device status collection service module to exchange data with other service modules, and is only responsible for receiving and temporarily storing data. Figure 3 As shown, the asynchronous message service module can provide message services. When a device sends data, the device code can be used as the Topic of the message queue to filter the data sent by different devices. This embodiment proposes a device fault diagnosis strategy based on real-time and historical data of industrial equipment. The strategy collects device status in real time and processes data storage, asynchronous analysis, asynchronous reverse notification, etc. through asynchronous subscription to achieve device health status identification and control.

[0065] In an exemplary embodiment, the target service module is the device trend service module, and the following steps are used to analyze the device data of the current device in the above step S204 using the target service module to which the service instance belongs, and to describe the implementation process of determining whether the current device has a fault based on the analysis result: obtaining the device control tag of the current device from the grassroots service module through the device trend service module, and subscribing to the second notification message of the second message queue corresponding to the device control tag; when it is determined that the second notification message is used to indicate that the second message queue is updated, the trend queue maintained by the device trend service module is updated according to the update message in the second message queue to obtain an updated trend queue, and the updated trend queue is synchronized to the relational database to perform data persistence operation on the updated trend queue; when it is determined that the change trend of the current trend queue maintained by the device trend service module is used to indicate that the current device has a fault, a persistent trend queue corresponding to the current trend queue is obtained from the relational database, and the current trend queue is restored using the persistent trend queue.

[0066] In the above embodiment, the device trend service module is used to provide device trend services for the current device (ie Figure 3 The core of the equipment trend service is to change the traditional database-based real-time calculation to prefabricated data, which greatly reduces the instantaneous high occupation of computer resources and solves the problem of idle resources during service idle time. By prefabricating data, computer resources are balanced throughout the process, making full use of computer resources.

[0067] Specifically, the device trend service module can implement the trend queue management function. In the Redis (RemoteDictionary Server, remote dictionary service) database, three fixed-length trend queues are maintained for each device by default, namely the real-time trend queue (within 1 hour by default), the daily trend queue, and the monthly trend queue. Among them, the data volume and performance factors need to be considered for the daily trend queue and the monthly trend queue. The actual trend queue needs to take fixed-step data according to the frequency of data collection. For all three, the data needs to be compressed to a certain extent. At the same time, considering the inevitable visibility of abnormal data, the abnormal data should be retained when compressing the data.

[0068] Furthermore, the device trend service module can also implement data subscription function. The device trend service module dynamically obtains the control right of the corresponding device from the device registration service, and then subscribes to the topic of the corresponding device from the message queue, and updates the device status data to the relevant queue in real time. At the same time, based on the distributed cache, the consistency of the trend data is guaranteed even if the service instance changes.

[0069] Optionally, the device trend service module can also implement data persistence. To avoid data loss, the device trend service module provides an independent thread to synchronize real-time trend queues, daily trend queues, monthly trend queues and other queues to the relational database regularly, and to recover data in case of system abnormalities. Considering the concurrency problem in the distributed situation, the thread logic is based on distributed locks, and multiple service instances freely compete for distributed locks to achieve data synchronization. At the same time, considering the decoupling of the service, this scheduling is not recommended to achieve other distributed task scheduling services.

[0070] Optionally, the device trend service module can also realize the trend viewing function. Considering the performance issue, for trend-based queue management, when viewing the trend on the visual terminal, the full value of the corresponding queue can be selected according to the options provided by the visual terminal, and real-time statistics are no longer performed through the database.

[0071] Based on the above embodiments, the present application proposes a unique trend data prefabrication strategy based on the equipment trend service module, which cleverly solves the problem of instantaneous high demand for computer resources during traditional trend viewing, can meet the needs of industrial equipment trend viewing, and balance the instantaneous resource occupancy to the real-time operation process of the server, significantly improving the stability of the system and resource utilization efficiency.

[0072] In an exemplary embodiment, further, the historical data persistence service module can obtain the device control tag of the current device from the grassroots service module, and subscribe to the third message queue corresponding to the device control tag; the device data stored in the third message queue can be persistently stored in a file appending manner.

[0073] In this embodiment, the historical data persistence service module provides Figure 3 The historical data service shown can use the historical data persistence service module to dynamically obtain the control of the corresponding device from the device registration service, and then subscribe to the topic of the corresponding device from the message queue to obtain the device status data in real time. It can be understood that in order to ensure the traceability of the data, the historical data persistence service module will store all the collected device status data persistently.

[0074] Since the persistently stored data is mainly used for data tracing and is not frequently used, and considering the huge amount of data, it can be stored in the form of file appending. And select independent files for different devices.

[0075] Furthermore, considering the scalability, the historical data persistence service module can also set up some data support database storage according to actual needs.

[0076] In an exemplary embodiment, the target service module is the device status analysis service module, and a technical solution is further proposed for implementing step S204 in which the device data of the current device is analyzed by the target service module to which the service instance belongs, and determining whether the current device has a fault based on the analysis result of the analysis, including: obtaining the real-time device status value of the current device through the device status analysis service module; determining the range of characteristic status values ​​set for the current device; and determining that the current device has a fault when it is determined that the real-time device status value does not belong to the range of characteristic status values ​​of the current device.

[0077] Optionally, in one embodiment, the device status analysis service module may provide: Figure 3 The status analysis service shown in the figure dynamically obtains the control of the corresponding device from the device registration service module through the device status analysis service module, and then subscribes to the topic of the corresponding device from the message queue to obtain the device status data in real time. By analyzing the device status data to determine whether the current device is faulty, the working status of the device can be monitored in real time.

[0078] Furthermore, for the implementation process of determining the characteristic state value range set for the current device, the following process can be referred to: the device state values ​​within the normal operation cycle of the current device are collected according to the collection cycle to obtain a set of initial state values ​​corresponding to the collection cycle; the average value of the set of initial state values ​​is set as the baseline value of the current device, the maximum value of the set of initial state values ​​is set as the maximum characteristic state value of the characteristic state value range, and the minimum value of the set of initial state values ​​is set as the minimum characteristic state value of the characteristic state value range, thereby determining the characteristic value range.

[0079] Optionally, the device status analysis service module can also realize the device status feature extraction function. Different devices have their own parameter specifications, so the operating status of different devices needs to be identified in combination with their respective parameter features.

[0080] For the determination process of the above characteristic state value range, the following content can also be referred to: In view of the situation that a large number of devices increase the difficulty of manual maintenance, the device state values ​​within a certain period of time can be extracted during the normal operation of the equipment, and the average value of the device state values ​​within a certain period of time can be used as the benchmark safety value of the equipment, and the maximum device state value and the minimum device state value can be set as the upper and lower limit safety values ​​of the equipment respectively, and then the characteristic state value range is determined according to the upper and lower limit safety values. Among them, the upper and lower limit safety values ​​can be manually fine-tuned.

[0081] When the device status characteristic value is empty, the device status value within 30 minutes is temporarily stored by default, and then the device status characteristic value is automatically calculated according to the above rules. When the device status characteristic value is not empty, it is manually recalculated with reference to the device status value determined above. When the user clicks on the feature recalculation, the device status characteristic value is regenerated by the device status analysis service module according to the rules.

[0082] In this embodiment, an automated device characteristic state extraction strategy is proposed, which achieves accurate extraction of device characteristic states in an automated manner, thereby avoiding errors and omissions that may occur in traditional manual recording of device parameters and improving data accuracy and reliability.

[0083] Optionally, the device trend service module can also realize the device status identification function. Specifically, the device trend service module subscribes to the real-time status value of the device and compares the real-time status value with the characteristic status value. When the lower limit range of the upper characteristic status value is exceeded, an abnormal alarm is immediately triggered.

[0084] Optionally, the device trend service module can also implement the device exception handling function. When an abnormal alarm is triggered, the device trend service module immediately records all status values ​​of the device after the alarm, stores them in the form of file append, and records the device alarm record in the relationship library. At the same time, the device trend service module can provide human intervention functions such as alarm release, termination of status recording, and device record status query. When the device returns to normal, the recording will be automatically terminated if there is no human intervention for a certain period of time to prevent data explosion.

[0085] Optionally, the equipment trend service module can also implement notification extension functions. The equipment trend service module can provide automatic notification mechanisms such as factory area voice alarm, SMS, agent, and phone calls after the equipment alarm.

[0086] Optionally, the device trend service module can also provide a device status notification function. When an abnormality occurs in a device, the device trend service module sends an abnormal message to the abnormal Topic corresponding to the device. Since the device trend service module only analyzes the device status based on existing data and does not interact directly with the device, it only informs the device status externally without performing specific control. In this design, the device abnormality Topic notification is received and processed by the device status collection service module.

[0087] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for an industrial device (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods of each embodiment of the present application.

[0088] Figure 4 is a structural block diagram of a device fault diagnosis system according to an embodiment of the present application; Figure 4 As shown, it specifically includes: a basic service module 42 and an upper service module 44.

[0089] The base layer service module 42 provides base layer services for the upper layer service module 44 .

[0090] The upper layer service module 44 includes at least one of the following: an equipment status collection service module, an asynchronous message service module, an equipment trend service module, a historical data persistence service module, and an equipment status analysis service module.

[0091] Through the above modules, a device fault diagnosis system including multiple service modules is designed, wherein the multiple service modules include at least a grassroots service module and an upper-layer service module, wherein the grassroots service module provides grassroots services for the upper-layer service module, and then uses the device fault diagnosis system to determine the target service instance distributed when the device registration service is completed for the current device in the grassroots service module; uses the target service module to which the service instance belongs to analyze the device data of the current device, and determines whether the current device has a fault based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: a device status acquisition service module, an asynchronous message service module, and a device trend service module. Service module, historical data persistence service module, equipment status analysis service module; adopting the above technical scheme, an efficient and real-time equipment fault diagnosis strategy is proposed, which can completely decouple the various equipment functions required for equipment fault diagnosis into multiple independent services. Each service has independent and complete operation capabilities. This completely independent service model improves the modularity of the system. While improving the diagnostic efficiency of equipment faults, it also provides great convenience for subsequent service expansion and maintenance. Even if a service fails, it will not affect the normal operation of other services. It also improves the high reliability and stability of the system, has important practical significance and application value, solves the technical problem of low efficiency in equipment fault diagnosis, and improves the diagnostic efficiency of equipment faults.

[0092] In an exemplary embodiment, the above-mentioned device fault diagnosis system is also used to: distribute a newly registered service example to the current device when the current device performs device registration service; if it is determined that the current device has an instance tag, and the instance tag is used to indicate that the service instance to which the current device belongs is a first service instance, then based on the release instruction of the grassroots service module, release the current device from the occupation process of the first service instance; obtain a second service instance from the newly registered service instance, determine the second service instance as the target service instance, and distribute the successfully released current device to the second service instance according to the release signal of the successful release of the current device.

[0093] In an exemplary embodiment, the target service module is the device status acquisition service module, and the above-mentioned device fault diagnosis system is also used to: obtain the device control tag of the current device from the grassroots service module through the device status acquisition module; store the operating status data of the current device acquired by the device status acquisition module in the first message queue corresponding to the device control tag, wherein the device data includes the operating status data of the current device, and the first message queue is created in the grassroots service module; use the device status acquisition module to subscribe to the first notification message of the first message queue; determine that the current device has a fault when it is determined that the first notification message has an abnormal notification message; determine the fault handling measures according to the device protocol used by the device status acquisition module when acquiring the operating status data of the current device, wherein the abnormal notification message is used to indicate that the operating status data of the current device has an abnormality.

[0094] In an exemplary embodiment, the above-mentioned equipment fault diagnosis system is also used to: determine the data transmission channel provided by the asynchronous message service module for other service modules to perform data transmission, wherein the other service modules represent modules in the upper-layer service modules other than the asynchronous message service module, one end of the data transmission channel is connected to the equipment status acquisition service module, and the other end of the transmission channel is connected to the remaining service modules, and the remaining service modules include at least one of the following: equipment trend service module, historical data persistence service module, equipment status analysis service module; and send the equipment data from the equipment status acquisition service module to the remaining service modules through the data transmission channel.

[0095] In an exemplary embodiment, the target service module is the device trend service module, and the above-mentioned device fault diagnosis system is also used to: obtain the device control tag of the current device from the grassroots service module through the device trend service module, and subscribe to the second notification message of the second message queue corresponding to the device control tag; when it is determined that the second notification message is used to indicate that the second message queue is updated, the trend queue maintained by the device trend service module is updated according to the update message in the second message queue to obtain an updated trend queue, and the updated trend queue is synchronized to the relational database to perform data persistence operation on the updated trend queue; when it is determined that the change trend of the current trend queue maintained by the device trend service module is used to indicate that the current device has a fault, obtain the persistent trend queue corresponding to the current trend queue from the relational database, and use the persistent trend queue to perform data recovery on the current trend queue.

[0096] In an exemplary embodiment, further, the above-mentioned device fault diagnosis system is also used to: obtain the device control tag of the current device from the grassroots service module through the historical data persistence service module, and subscribe to the third message queue corresponding to the device control tag; and persistently store the device data stored in the third message queue in a file appending manner.

[0097] In an exemplary embodiment, the target service module is the device status analysis service module, and the above-mentioned device fault diagnosis system is also used to: further obtain the real-time device status value of the current device through the device status analysis service module; determine the characteristic status value range set for the current device; and determine that the current device has a fault when it is determined that the real-time device status value does not belong to the characteristic status value range of the current device.

[0098] In an exemplary embodiment, the above-mentioned equipment fault diagnosis system is also used to: collect equipment status values ​​within the normal operation cycle of the current equipment according to a collection cycle to obtain a set of initial status values ​​corresponding to the collection cycle; set the average value of the set of initial status values ​​as the baseline value of the current equipment, set the maximum value of the set of initial status values ​​as the maximum characteristic status value of the characteristic status value range, and set the minimum value of the set of initial status values ​​as the minimum characteristic status value of the characteristic status value range, thereby determining the characteristic value range.

[0099] An embodiment of the present application further provides a storage medium, which includes a stored program, wherein the program executes any of the above methods when it is run.

[0100] Optionally, in this embodiment, the storage medium may be configured to store program codes for executing the following steps:

[0101] S1, determining a target service instance to be distributed when completing a device registration service for a current device in the base service module;

[0102] S2, using the target service module to which the service instance belongs to analyze the device data of the current device, and determining whether the current device has a fault based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: device status acquisition service module, asynchronous message service module, device trend service module, historical data persistence service module, device status analysis service module.

[0103] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0104] Optionally, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0105] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0106] An embodiment of the present application further provides another computer program product, including a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.

[0107] The embodiments of the present application also provide a computer program, which includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the steps in any one of the above method embodiments.

[0108] Optionally, in this embodiment, the processor may be configured to perform the following steps through a computer program:

[0109] S1, determining a target service instance to be distributed when completing a device registration service for a current device in the base service module;

[0110] S2, using the target service module to which the service instance belongs to analyze the device data of the current device, and determining whether the current device has a fault based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: device status acquisition service module, asynchronous message service module, device trend service module, historical data persistence service module, device status analysis service module.

[0111] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0112] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation modes, and this embodiment will not be described in detail here.

[0113] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0114] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for diagnosing equipment failure, characterized in that: Applied to a device fault diagnosis system, the device fault diagnosis system includes multiple service modules, the multiple service modules include at least a base service module and an upper service module, the base service module provides base services for the upper service module, including: Determine a target service instance to be distributed when a device registration service is completed for a current device in the base service module; The target service module to which the service instance belongs is used to analyze the device data of the current device, and whether the current device has a fault is determined based on the analysis result of the analysis, wherein the target service module belongs to the upper-layer service module, and the upper-layer service module includes at least one of the following: device status acquisition service module, asynchronous message service module, device trend service module, historical data persistence service module, and device status analysis service module.

2. The method for diagnosing equipment failure according to claim 1, characterized in that: Determining a target service instance to be distributed when completing a device registration service for a current device in the base service module includes: When the current device performs device registration service, distributing a newly registered service example to the current device; If it is determined that the current device has an instance tag, and the instance tag is used to indicate that the service instance to which the current device belongs is a first service instance, releasing the current device from the occupation process of the first service instance based on the release instruction of the base service module; A second service instance is acquired from the newly registered service instance, the second service instance is determined as the target service instance, and the successfully released current device is distributed to the second service instance according to a release signal indicating that the current device is successfully released.

3. The method for diagnosing equipment failure according to claim 1, characterized in that: The target service module is the device status acquisition service module, and the device data of the current device is analyzed by using the target service module to which the service instance belongs, and whether the current device has a fault is determined according to the analysis result of the analysis, including: Acquire the device control tag of the current device from the grassroots service module through the device status acquisition module; Storing the running status data of the current device collected by the device status collection module in the first message queue corresponding to the device control tag, wherein the device data includes the running status data of the current device, and the first message queue is created in the grassroots service module; Using the device status acquisition module to subscribe to the first notification message of the first message queue; In a case where it is determined that the first notification message contains an abnormal notification message, determining that the current device has a fault; The fault handling measures are determined according to the device protocol used by the device status acquisition module when acquiring the operating status data of the current device, wherein the abnormality notification message is used to indicate that the operating status data of the current device is abnormal.

4. The method for diagnosing equipment failure according to claim 1, characterized in that: The method further includes: determining a data transmission channel provided by the asynchronous message service module for other service modules to perform data transmission, wherein the other service modules represent modules in the upper-layer service modules other than the asynchronous message service module, one end of the data transmission channel is connected to the device status acquisition service module, and the other end of the transmission channel is connected to the remaining service modules, and the remaining service modules include at least one of the following: a device trend service module, a historical data persistence service module, and a device status analysis service module; The device data is sent from the device status acquisition service module to the remaining service modules through the data transmission channel.

5. The method for diagnosing equipment failure according to claim 1, characterized in that: The target service module is the device trend service module, and the device data of the current device is analyzed by using the target service module to which the service instance belongs, and whether the current device has a fault is determined according to the analysis result, including: Obtaining the device control tag of the current device from the grassroots service module through the device trend service module, and subscribing to the second notification message of the second message queue corresponding to the device control tag; in the case of determining that the second notification message is used to indicate the update of the second message queue, updating the trend queue maintained by the device trend service module according to the update message in the second message queue to obtain an updated trend queue, and synchronizing the updated trend queue to a relational database to perform data persistence operation on the updated trend queue; When it is determined that the change trend of the current trend queue maintained by the device trend service module is used to indicate that there is a fault in the current device, a persistent trend queue corresponding to the current trend queue is obtained from the relational database, and the persistent trend queue is used to restore data of the current trend queue.

6. The method for diagnosing equipment failure according to claim 1, characterized in that: The method further includes: obtaining a device control tag of the current device from the base service module through the historical data persistence service module, and subscribing to a third message queue corresponding to the device control tag; The device data stored in the third message queue is persistently stored in a file appending manner.

7. The method for diagnosing equipment failure according to claim 1, characterized in that: The target service module is the device status analysis service module, and the device data of the current device is analyzed by using the target service module to which the service instance belongs, and whether the current device has a fault is determined according to the analysis result of the analysis, including: Acquire the real-time device status value of the current device through the device status analysis service module; Determining a characteristic state value range set for the current device; When it is determined that the real-time device status value does not belong to the characteristic status value range of the current device, it is determined that a fault exists in the current device.

8. The method for diagnosing equipment failure according to claim 7, characterized in that: Determining a characteristic state value range set for the current device includes: Collecting device status values ​​within the normal operation cycle of the current device according to a collection cycle to obtain a set of initial status values ​​corresponding to the collection cycle; The average value of the set of initial state values ​​is set as the baseline value of the current device, the maximum value of the set of initial state values ​​is set as the maximum characteristic state value of the characteristic state value range, and the minimum value of the set of initial state values ​​is set as the minimum characteristic state value of the characteristic state value range, thereby determining the characteristic value range.

9. A diagnostic system for equipment failure, characterized in that: At least used to perform the method described in any one of claims 1 to 8 above.

10. An electronic device comprising a memory and a processor, characterized in that: A computer program is stored in the memory, and the processor is configured to execute the method according to any one of claims 1 to 8 through the computer program.

Images