Configuration equipment abnormity monitoring method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of equipment anomaly monitoring, in particular to a configuration equipment anomaly monitoring method and device, electronic equipment and a storage medium. The method comprises the following steps: analyzing an obtained project file of at least one controller to obtain an I / O period of at least one configuration device connected with the controller; based on the I / O period of the at least one configuration device, calculating to obtain a cycle counting period of the configuration device; acquiring a cyclic count value of a current data packet and a previous data packet of at least one configuration device, and calculating a difference value between the cyclic count value of the current data packet and the cyclic count value of the previous data packet; whether the difference value of the cycle counting values and the cycle counting period meet the preset conditions or not is monitored, if not, it is judged that the configuration equipment is abnormal, and therefore abnormal conditions such as packet loss or station loss of the configuration equipment are accurately and efficiently monitored, and normal operation of a production line is ensured.

Description

Technical Field

[0001] The present disclosure relates to the technical field of device anomaly monitoring, and particularly to a method, device, electronic device and storage medium for monitoring anomalies of configuration devices. Background Art

[0002] With the continuous advancement and development of Industry 4.0, as the core control devices of industrial automation, PLCs, DCSs, etc. can realize remote monitoring of numerous configuration devices in the industrial field by collecting and analyzing controller data, thus ensuring the smooth operation of the production line. However, affected by many factors such as the complex industrial field environment interference, cyber attacks, multi-level switch networking connection failures or hardware failures, etc., configuration devices often have abnormal situations such as station loss or packet loss, resulting in some configuration devices losing connection or being unable to receive data normally even though the connection is normal. Among them, station loss of a configuration device means that the configuration device loses contact or cannot work properly; packet loss means that during the data transmission process of the configuration device, some or all data packets fail to reach the destination on time. Whether it is station loss or packet loss, they both belong to anomalies of configuration devices. If these anomalies cannot be detected in time, and the long-term station loss or packet loss cannot be resolved in time, it is very likely to cause the production line to stop production, thus bringing huge economic losses to the enterprise. Therefore, how to accurately and efficiently monitor the anomalies of configuration devices and avoid the production line from stopping production due to anomalies such as station loss or packet loss is a technical problem that urgently needs to be solved. Summary of the Invention

[0003] To solve the above technical problems, the present disclosure provides a method, device, electronic device and storage medium for monitoring anomalies of configuration devices.

[0004] The first aspect of the embodiments of the present disclosure provides a method for monitoring anomalies of configuration devices, including: Parsing the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller; Calculating the cycle counting period of the configuration device based on the I / O cycles of at least one configuration device; Obtaining the cycle count values of the current data packet and the previous data packet of at least one configuration device, and calculating the difference between the cycle count values of the current data packet and the previous data packet; Monitoring whether the difference between the cycle count values and the cycle counting period meets a preset condition. If not, it is determined that the configuration device has an anomaly.

[0005] The second aspect of the embodiments of the present disclosure provides a device for monitoring anomalies of configuration devices, including: A parsing module, configured to parse the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller; A calculation module, configured to calculate a cycle count period of a configuration device based on an I / O cycle of at least one configuration device; An acquisition module, configured to obtain cycle count values of a current data packet and a previous data packet of at least one configuration device, and calculate a difference between the cycle count values of the current data packet and the previous data packet; A monitoring module, configured to monitor whether a difference between cycle count values and a cycle count period meet a preset condition, and if not, determine that there is an abnormality in the configuration device.

[0006] A third aspect of the embodiments of the present disclosure provides an electronic device, including: A processor; A memory, configured to store a computer program; Wherein, the processor is configured to read the computer program from the memory and execute the computer program to implement the configuration device abnormality monitoring method provided in the first aspect above.

[0007] A fourth aspect of the embodiments of the present disclosure provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, enables the processor to implement the configuration device abnormality monitoring method provided in the first aspect above.

[0008] The technical solutions provided in the embodiments of the present disclosure have the following advantages compared with the prior art: The configuration device abnormality monitoring method, device, electronic device and storage medium provided in the embodiments of the present disclosure can parse engineering files of at least one obtained controller, and obtain I / O cycles of at least one configuration device connected to the controller; calculate a cycle count period of the configuration device based on the I / O cycles of at least one configuration device; obtain cycle count values of a current data packet and a previous data packet of at least one configuration device, and calculate a difference between the cycle count values of the current data packet and the previous data packet; monitor whether a difference between cycle count values and a cycle count period meet a preset condition, and if not, determine that there is an abnormality in the configuration device. Thus, based on the cycle count value of the data packet message of the configuration device and the data packet reception time, it is possible to accurately and efficiently monitor abnormalities such as packet loss or station loss of the configuration device. In addition, combined with the network topology diagram of the configuration device, the abnormality monitoring results of the configuration device are displayed on the network topology diagram, which can more intuitively and efficiently display the abnormality location, is beneficial to timely solve the monitored abnormalities, and thus ensure the normal operation of the production line. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings here are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure.

[0010] To more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0011] Figure 1 It is a flowchart of a method for monitoring abnormal conditions of a configuration device provided by an embodiment of the present disclosure; Figure 2 It is a flowchart of another method for monitoring abnormal conditions of a configuration device provided by an embodiment of the present disclosure; Figure 3 It is a flowchart of another method for monitoring abnormal conditions of a configuration device provided by an embodiment of the present disclosure; Figure 4 It is a schematic structural diagram of a device for monitoring abnormal conditions of a configuration device provided by an embodiment of the present disclosure; Figure 5 It is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Detailed implementation manners

[0012] In order to more clearly understand the above objects, features, and advantages of the present disclosure, the following will further describe the solutions of the present disclosure. It should be noted that, without conflict, the embodiments of the present disclosure and the features in the embodiments can be combined with each other.

[0013] In the following description, many specific details are set forth to fully understand the present disclosure, but the present disclosure can also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of the present disclosure, rather than all the embodiments.

[0014] It should be understood that the steps recorded in the method implementation manners of the present disclosure can be executed in different orders and / or executed in parallel. In addition, the method implementation manners can include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.

[0015] It should be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or configuration device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or elements inherent to such process, method, article or configuration device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the presence of additional identical elements in the process, method, article or configuration device comprising the element.

[0016] It should be noted that the modifications of "one" and "multiple" mentioned in this disclosure are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly specified in the context, it should be understood as "one or more".

[0017] Due to various factors such as high temperature, high pressure, high electromagnetic interference, network attacks, multi-level switch networking connection failures or hardware failures at the industrial site, abnormal situations such as station loss or packet loss often occur in the configuration device, resulting in some configuration devices losing connection or being unable to receive data normally even though the connection is normal. Whether it is station loss or packet loss, it belongs to the abnormality of the configuration device. If these abnormalities cannot be detected in time, the long-term station loss or packet loss cannot be resolved in time, which is very likely to lead to the shutdown and production suspension of the production line. To address this problem, the embodiments of this disclosure provide a method for monitoring abnormalities of a configuration device, which will be introduced below in combination with specific embodiments.

[0018] Figure 1 It is a flowchart of a method for monitoring abnormalities of a configuration device provided by the embodiments of this disclosure. This method can be executed by a configuration device abnormality monitoring device, which can be implemented in software and / or hardware. This abnormality monitoring device can be configured in an industrial site configuration device, such as a server or a terminal, and is not further limited here.

[0019] As Figure 1 shown, the method for monitoring abnormalities of a configuration device provided in this embodiment includes the following steps: S110. Parse the engineering file of at least one controller obtained to acquire the I / O cycle of at least one configuration device connected to the controller.

[0020] In the embodiments of the present disclosure, the controller refers to a controller used to control numerous configuration devices in an industrial field, including but not limited to: Programmable Logic Controller (PLC), Distributed Control System (DCS), and robot-specific controllers, etc. Different types of controllers have different control methods and application scenarios.

[0021] The configuration devices connected to the controller here include but are not limited to automation devices such as sensors, cameras, motors, frequency converters, robots, etc. in the industrial field. These devices are controlled by the controller and execute in an orderly manner according to a predetermined program. In addition, the configuration devices are generally also referred to as stations or substations, and no specific limitation is made here.

[0022] In an actual industrial field, there are various connection methods between the configuration devices and the controller, including but not limited to: the configuration devices are directly connected to the controller, the configuration devices are connected to the controller through an upper-level switch, and the configuration devices are connected to the controller through multiple levels of upper-level switches. That is to say, there can be 0 - N levels of upper-level switches directly connected between the configuration devices and the controller, where N is a positive integer. The upper-level switch here is hereinafter simply referred to as the switch.

[0023] The engineering file of the controller refers to the file created and used during the development of the controller, which contains all the information required to implement a specific automation control task, such as configuration files for describing the hardware configuration, communication configuration, parameter configuration, etc. of the controller, as well as program files for describing the control logic of the controller, etc.

[0024] Optionally, the format of the controller can be XML format, or JSON format or other formats.

[0025] Optionally, depending on different configurations and settings of the controller, the number of engineering files can be one or more.

[0026] In some embodiments of the present disclosure, the corresponding engineering file is exported from the controller by calling a dedicated export tool, thereby obtaining the engineering file corresponding to the controller. The engineering file can also be obtained through other means, which is not further limited here. For example, taking Siemens PLC1500 as an example, the engineering file of the PLC controller can be directly exported through the openness tool.

[0027] By parsing the obtained engineering file of the controller, configuration information such as the I / O cycle of the configuration device, which has been set in advance in the PLC engineering file, can be obtained. The I / O cycle T of the configuration device 1It refers to the time interval for the configuration device to send data packets to controllers such as PLCs under normal conditions, and this cycle can be configured in advance. Herein, the writing of the I / O cycle of the configuration device can also be written as the IO cycle, and no further limitation is made here.

[0028] S120. Calculate the cyclic counting period of the configuration device based on the I / O cycle of at least one configuration device.

[0029] In the embodiments of the present disclosure, the I / O cycle of the configuration device can be obtained by parsing the engineering file of the controller. The I / O cycles of different configuration devices are different and can be set to fixed values in advance through configuration.

[0030] The configuration device, switch, and PLC communicate and transfer data through industrial field buses such as profinet and Ethernet. The data packets are periodically communicated and transferred between the controller and the configuration device through the bus. The message structure of the data packets sent by the configuration device includes the destination address, source address, and data status (APDU), where the data status includes the cycle counter and other status bytes. Each cycle counter byte of each data packet includes a specific cycle count value.

[0031] The cyclic counting periods of the cycle count values of different configuration devices are different, and the cyclic counting period can be calculated through the following formula. Specifically: C = T 1 / 31.25 where C is the cyclic counting period of a certain configuration device, and T 1 is the I / O cycle of this configuration device. It can also be understood that the cyclic calculation period of the configuration device is equal to the I / O cycle of the configuration device divided by 31.25. Or it can be understood that the I / O cycle of the configuration device is equal to 31.25 times the cyclic counting period of this configuration device.

[0032] For example, if the I / O cycle T 1 = 1 ms (millisecond) = 1000 (microseconds) of a certain configuration device, then the corresponding cyclic counting period C = 1000 / 31.25 = 32. Another example, if the I / O cycle T 1 = 2 ms (millisecond) = 2000 (microseconds) of another configuration device, then the corresponding cyclic counting period C = 2000 / 31.25 = 64.

[0033] S130. Obtain the cycle count values of the current data packet and the previous data packet of at least one configuration device, and calculate the difference between the cycle count values of the current data packet and the previous data packet.

[0034] Specifically, the acquisition device obtains the data packets of different configuration devices transmitted in the industrial fieldbus by means of listening or querying, reads the message information of each data packet, and obtains the target address, source address, and data status (APDU) in the message information, where the data status includes a cycle counter, and records the cycle count value c of each data packet. n , (n is a positive integer).

[0035] In some embodiments of the present disclosure, obtaining the cycle count values of the current data packet and the previous data packet of at least one configuration device includes: obtaining the current data packet and the previous data packet of at least one configuration device, reading the message information of the data packet, and obtaining the cycle count value of the current data packet and the cycle count value of the previous data packet from the message information.

[0036] Among them, calculating the difference between the cycle count values of adjacent data packets of the same configuration device, that is, calculating the difference between the cycle count values of the current data packet and the previous data packet sent by the same configuration device. For example, for a certain configuration device, the cycle count value c of the data packet received at time t 1 = 32, and the cycle count value c of the data packet received at time t 1 = 96. Then the difference in the cycle count values △c 2 = c 2 - c 1 = c 2 - c 1 = 96 - 32 = 64; the cycle count value c of the data packet received at time t 2 = 96, and the cycle count value c of the data packet received at time t 2 = 128. Then the difference in the cycle count values △c 3 = c 3 - c 2 = c 3 - c 2 = 128 - 96 = 32.

[0037] S140. Monitor whether the difference between the cycle count values and the cycle count period meets a preset condition. If not, it is determined that the configuration device is abnormal.

[0038] In some embodiments of the present disclosure, the preset condition means that the difference between the cycle count values of the current data packet and the previous data packet of the same configuration device is equal to the cycle count period.

[0039] The above preset condition generally means that when the configuration device is normal, the difference between the cycle count values of adjacent data packets is equal to a preset fixed value, that is, the cycle count period of the configuration device.

[0040] If the difference between the cyclic count value of the current data packet and the previous data packet of the same configured device does not meet the preset condition, that is, it is not equal to the corresponding cyclic calculation period, it is considered that the configured device is abnormal.

[0041] In some embodiments of the present disclosure, the abnormalities of the configured device include, but are not limited to: packet loss abnormality, station loss abnormality, and other abnormalities. Among them, packet loss abnormality refers to the situation where some or all data packets fail to reach the target device on time during the data transmission process of the configured device. Station loss abnormality refers to the situation where the configured device loses connection or cannot work properly. Whether it is a station loss abnormality or a packet loss abnormality, they both belong to the abnormal types of the configured device.

[0042] In some embodiments of the present disclosure, to monitor whether the difference between the cyclic count value and the cyclic count period meets the preset condition, if not, it is determined that the configured device is abnormal, including: when the difference between the cyclic count value and the cyclic count period is different, it is determined that the configured device has a packet loss abnormality.

[0043] Under normal circumstances, the difference between the cyclic count values of adjacent data packets of the same configured device is equal to the cyclic count period of the configured device. When the difference between the cyclic count values of adjacent data packets is not equal to the cyclic count period, it indicates that the configured device has a packet loss abnormality.

[0044] For example, the I / O period T 1 = 1ms = 1000 microseconds of a certain configured device, and the cyclic count period C of this configured device = 1000 / 31.25 = 32. The cyclic count value c 1 of the data packet received by this configured device at time t 1 = 32, and the cyclic count value c 2 of the data packet received by this configured device at time t 2 = 96. Then the difference △c 1 of its cyclic count value 2 = c 1 - c 2 = 96 - 32 = 64, which does not meet the preset condition, so it is considered that this configured device has a packet loss abnormality. However, the cyclic count value c 2 of the data packet received by this configured device at time t 3 = 96, and the cyclic count value c 3 of the data packet received by this configured device at time t 2 = 128. Then the difference △c 3 of its cyclic count value 2 = c

[0045] In the embodiments of the present disclosure, it is possible to parse the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller; based on the I / O cycles of at least one configuration device, calculate the cycle count period of the configuration device; obtain the cycle count values of the current data packet and the previous data packet of at least one configuration device, and calculate the difference between the cycle count values of the current data packet and the previous data packet; monitor whether the difference between the cycle count values and the cycle count period meets a preset condition, and if not, determine that there is an abnormality in the configuration device. Thus, based on the cycle count period of the configuration device and the cycle count values of the data packet messages, it is possible to accurately and efficiently monitor the packet loss abnormality of the configuration device, which is beneficial to timely solve the packet loss abnormality, thereby ensuring the normal operation of the production line.

[0046] Based on the above embodiments, Figure 2 is a flowchart of another method for monitoring the abnormality of a configuration device provided by the embodiments of the present disclosure, as Figure 2 shown, and specifically includes the following steps: S210. Parse the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller.

[0047] S220. Based on the I / O cycles of at least one configuration device, calculate the cycle count period of the configuration device.

[0048] S230. Obtain the cycle count values of the current data packet and the previous data packet of at least one configuration device, and calculate the difference between the cycle count values of the current data packet and the previous data packet.

[0049] S240. Monitor whether the difference between the cycle count values and the cycle count period meets a preset condition, and if not, determine that there is an abnormality in the configuration device.

[0050] It should be noted that the specific implementation manners of S210 - S240 are similar to the above implementation manners and will not be elaborated here.

[0051] S250. Parse the engineering files of at least one obtained controller to obtain the watchdog time of at least one configuration device connected to the controller.

[0052] The watchdog time of the configuration device is the configuration information that can be set in the engineering files of controllers such as PLC and DCS, and can be obtained by parsing the engineering files of controllers such as PLC and DCS. The I / O cycle T of the configuration device 1 refers to the time interval for the configuration device to send data packets to controllers such as PLC or switches under normal conditions. The watchdog time T of the configuration device 2It refers to the timeout for the PLC to wait for receiving data packets from the configuration device. Whether it is the I / O cycle of the configuration device or the watchdog time of the configuration device, it can be configured in advance.

[0053] Under normal circumstances, the watchdog time T of the same configuration device 2 is an integer multiple of the I / O cycle T 1 . For example, it is 2 times, 3 times, or 4 times, etc. The multiples of different brands and / or different model control configurations are different. For example, Siemens PLC sets the watchdog time of the same configuration device to 3 times the configuration I / O cycle.

[0054] S260. Obtain multiple data packets sent by the configuration device, record the receiving times of the multiple data packets, calculate the difference between the receiving times of adjacent data packets, and analyze whether the difference between the receiving times of adjacent data packets is greater than the watchdog time of the configuration device. If the difference in receiving times is greater than the watchdog time of the configuration device, it is considered that there is a station loss anomaly in the configuration device.

[0055] Under normal circumstances, the configuration device will send data packets to the PLC at fixed time intervals. Therefore, theoretically, the time interval is fixed. Affected by the device's own faults and network fluctuations, the actual time interval is not equal to the set I / O cycle T 1 , and it may be less than the I / O cycle T 1 , it may be greater than the I / O cycle T 1 and less than the watchdog time T 2 , or it may be greater than the watchdog time T 2 .

[0056] Generally, the watchdog time T of the configuration device 2 is multiple times of the I / O cycle T 1 . For example, it is 2 times, 3 times, or 4 times, etc. When the receiving time of adjacent data packets exceeds the watchdog time, it indicates that the maximum waiting time of the controller has been seriously exceeded. Then, it can be judged that there is a station loss anomaly in the configuration device, that is, the configuration device has lost contact or cannot work properly, which belongs to a relatively serious abnormal situation.

[0057] Specifically, by obtaining multiple data packets sent by the same configuration device, recording the receiving times of the multiple data packets, calculating the difference between the receiving times of adjacent data packets, comparing the difference in receiving times with the watchdog time of the configuration device, and analyzing whether the difference between the receiving times of adjacent data packets is greater than the watchdog time of the configuration device. If the difference in receiving times is greater than the watchdog time of the configuration device, it is considered that there is a station loss anomaly in the configuration device.

[0058] For example, obtain adjacent data packets of the configuration device with anomalies and record their receiving time t n(n is a positive integer), calculate the difference △t in the reception times of two data packets, where △t = t n -t n-1 . If the difference △t in the reception times > the watchdog time T 2 , it indicates that the configuration device or the switch has lost a station, and at the same time, it can be preliminarily judged that the reason for the lost station is network anomaly.

[0059] If the difference △t in the reception times < the watchdog time T 2 , it indicates that the configuration device or the switch has not had a lost station anomaly. At this time, it cannot be fully determined the reason for the lost station anomaly, and multiple cases need to be classified and discussed. Further discussion is not carried out here.

[0060] Based on the above embodiments, Figure 3 is a flowchart of another method for monitoring anomalies in a configuration device provided by an embodiment of the present disclosure. As Figure 3 shown, it specifically includes the following steps: S310. Parse the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller.

[0061] S320. Calculate the loop count period of the configuration device based on the I / O cycles of at least one configuration device.

[0062] S330. Obtain the loop count values of the current data packet and the previous data packet of at least one configuration device, and calculate the difference between the loop count values of the current data packet and the previous data packet.

[0063] S340. Monitor whether the difference in the loop count values and the loop count period meet a preset condition. If not, it is determined that the configuration device has an anomaly.

[0064] It should be noted that the specific implementation manners of S310 - S340 are similar to the above implementation manners and will not be elaborated here.

[0065] S350. Display the anomaly monitoring results of the configuration device to the user. The anomaly monitoring results include packet loss anomaly and / or lost station anomaly.

[0066] In the embodiments of the present disclosure, the anomaly monitoring results of the configuration device are displayed to the user. Among them, the anomaly monitoring results of the configuration device include one or more of packet loss anomaly, lost station anomaly, and the scope of the anomaly.

[0067] The display methods include but are not limited to text, charts, audio - video, voice, etc. The display content includes but is not limited to information such as displaying the anomaly mark position, anomaly type, and quantity in the network topology diagram.

[0068] In the embodiments of the present disclosure, the number of packet losses or station losses can be further analyzed, and the number of packet losses or station losses within a preset time period can be cumulatively calculated to obtain the total number of packet losses or the total number of station losses; based on the total number of packet losses or the total number of station losses, the corresponding packet loss rate or station loss rate can be determined, and the total number of packet losses or the packet loss rate, the total number of station losses or the station loss rate are displayed, so as to facilitate the user to more intuitively understand the abnormal situation of the configuration device.

[0069] In the embodiments of the present disclosure, the network topology diagram of the configuration device can also be combined, and the abnormal monitoring results of the configuration device are displayed on the network topology diagram, which is conducive to intuitively and efficiently displaying the abnormal location, so as to facilitate the user to quickly locate the abnormal location, solve the abnormality in time, and ensure the normal operation of the production line.

[0070] Among them, the network topology diagram refers to the network relationship diagram of the connection of PLC, switch and configuration device, which can display the network address locations and connection relationships of all configuration devices. The network topology diagram at least includes the name and network address location of each configuration device. Among them, the network address location is the IP address of each configuration device.

[0071] Preferably, by displaying the abnormal monitoring results of the configuration device in a prominent manner on the network topology diagram, the abnormal location, range and type of the abnormality can be displayed more intuitively and efficiently, which is conducive to engineers quickly solving the abnormality and avoiding major production accidents such as production line shutdown.

[0072] For example, on the network topology diagram, the abnormal monitoring results are highlighted by eye-catching colors. For example, the configuration device with packet loss abnormality is displayed in red, and the configuration device with station loss abnormality is displayed in yellow. At the same time, all configuration devices with abnormalities can be displayed on the network topology diagram, and the approximate range of device abnormalities can be initially judged in combination with the location information of these configuration devices.

[0073] Optionally, for the configuration device with abnormality, based on the network topology diagram of the configuration device, the upper-level switch connected to the configuration device with abnormality is determined, and it is compared whether the number of configuration devices with abnormality connected under the upper-level switch is greater than the preset threshold of the upper-level switch. If it is greater than the preset threshold, it is considered that the abnormal range of the configuration device is the whole upper-level switch; if it is less than the preset threshold, it is considered that the abnormal range of the configuration device is at least one configuration device under the upper-level switch.

[0074] In a network topology diagram, there will be different upper-level switches, including but not limited to primary upper-level switches, secondary upper-level switches, tertiary upper-level switches, etc. Among them, the same primary upper-level switch can be connected to multiple configuration devices and / or multiple secondary upper-level switches, and each secondary upper-level switch can continue to be connected to multiple configuration devices and / or multiple tertiary upper-level switches. Through the network topology diagram, it is possible to quickly locate the position of the configuration device with anomalies, which is conducive to the user quickly locating the fault position and resolving the fault in a timely manner.

[0075] In an embodiment of the present disclosure, for a configuration device with anomalies, based on the network topology diagram of the configuration device, determine the upper-level switch to which the configuration device with anomalies is connected, and compare whether the number of configuration devices with anomalies connected under the upper-level switch is greater than a preset threshold, so as to judge the scope of device anomalies, determine whether it is a configuration device anomaly or an overall switch anomaly, which is conducive to formulating corresponding solutions.

[0076] Due to various factors such as interference from complex industrial site environments such as high temperature, high pressure, and high electromagnetic fields, network attacks, multi-level switch networking connection failures, or hardware failures in the industrial site, many types of anomalies may occur, including but not limited to: station loss caused by hardware failure of a certain configuration device, station loss or packet loss caused by a network cable failure between a certain configuration device and its upper-level switch, station loss or packet loss of the entire switch and the configuration devices connected thereto caused by hardware device failure of a certain switch, etc.

[0077] In an embodiment of the present disclosure, by comparing whether the number of configuration devices with anomalies connected under the upper-level switch is greater than a preset threshold, the scope of device anomalies can be judged. If it is greater than the preset threshold, it is considered that the scope of packet loss anomalies of the configuration device is the entire upper-level switch; if it is less than the preset threshold, it is considered that the scope of packet loss anomalies of the configuration device is at least one configuration device connected under the upper-level switch.

[0078] The preset threshold here refers to the maximum value of the number of configuration devices with anomalies connected under the same upper-level switch. For example, it can be 5, 6, 7, etc. The preset thresholds of different upper-level switches are different and can be configured in advance.

[0079] For example, the preset threshold of a certain first-level upper-layer switch is 5. If the number of abnormal configuration devices among the multiple configuration devices connected to this first-level upper-layer switch is greater than 5, it is usually considered that the entire first-level upper-layer switch is abnormal, and it is necessary to prioritize troubleshooting the switch, including but not limited to the device failure of the switch itself, the network cable connection failure of the switch, etc. If the number of abnormal configuration devices among the multiple configuration devices connected to this first-level upper-layer switch is 2, it is usually considered that the 2 configuration devices under this first-level upper-layer switch are abnormal, and it is necessary to prioritize troubleshooting the 2 abnormal configuration devices, without the need to troubleshoot the switch.

[0080] In the embodiments of the present disclosure, when it is detected that at least one configuration device has anomalies such as packet loss, by combining the network topology diagram where the abnormal configuration device is located and the anomalies of other configuration devices connected to the same upper-layer switch where the configuration device is located, the abnormal range can be accurately determined, which is conducive to quickly performing troubleshooting and resolving the problem.

[0081] In the embodiments of the present disclosure, by combining the network topology diagram to display the abnormal monitoring results of the configuration devices, the abnormal monitoring results of the configuration devices can be presented more intuitively and simply, which is conducive to on-site engineers quickly grasping specific information such as the type, quantity, and location of the anomalies, and is conducive to promptly resolving the faults, thereby ensuring the normal operation of the production line.

[0082] Figure 4 It is a schematic structural diagram of a configuration device abnormal monitoring device provided by the embodiments of the present disclosure. The configuration device abnormal monitoring device provided by the embodiments of the present disclosure can execute the processing flow provided by the embodiments of the configuration device abnormal monitoring method, as Figure 4 shown, the configuration device abnormal monitoring device 40 includes: an analysis module 41, a calculation module 42, a collection module 43, and a monitoring module 44.

[0083] Among them, the analysis module 41 can be used to analyze the engineering files of at least one obtained controller to obtain the I / O cycle of at least one configuration device connected to the controller.

[0084] The calculation module 42 can be used to calculate the cycle count period of the configuration device based on the I / O cycle of at least one configuration device.

[0085] The collection module 43 can be used to obtain the cycle count values of the current data packet and the previous data packet of at least one configuration device, and calculate the difference between the cycle count values of the current data packet and the previous data packet.

[0086] The monitoring module 44 can be used to monitor whether the difference between the cycle count values and the cycle count period meets a preset condition. If not, it is determined that the configuration device is abnormal.

[0087] In the embodiments of the present disclosure, the engineering files of at least one obtained controller can be parsed to determine the I / O cycle of at least one configuration device connected to the controller; based on the I / O cycles of at least one configuration device, the cyclic count period of the configuration device is calculated; the cyclic count values of the current data packet and the previous data packet of at least one configuration device are obtained, and the difference between the cyclic count values of the current data packet and the previous data packet is calculated; it is monitored whether the difference between the cyclic count values meets a preset condition, and if not, it is determined that the configuration device is abnormal. Thus, based on the cyclic count period of the configuration device and the cyclic count values of the data packet messages, the packet loss anomaly of the configuration device can be accurately and efficiently monitored, thereby ensuring the normal operation of the production line.

[0088] In some embodiments of the present disclosure, the acquisition module 43 further includes an acquisition sub-module 431 and a reading sub-module 432; the acquisition sub-module 431 is used to acquire the current data packet and the previous data packet of at least one configuration device; the reading sub-module 432 is used to read the message information of the data packet and obtain the cyclic count value of the current data packet and the cyclic count value of the previous data packet from the message information.

[0089] In some embodiments of the present disclosure, the monitoring module 44 further includes a comparison sub-module 441, which is used to compare the difference between the cyclic count values and the cyclic count period. When the two values are different, it is determined that the configuration device has a packet loss anomaly.

[0090] In some embodiments of the present disclosure, the parsing module 41 can also be used to parse the obtained engineering file of the controller and obtain the watchdog time of at least one configuration device connected to the controller.

[0091] In some embodiments of the present disclosure, the configuration device anomaly monitoring device 40 further includes a station loss anomaly recognition module 45, which is used to acquire multiple data packets sent by the configuration device, record the reception times of the multiple data packets, calculate the difference between the reception times of adjacent data packets, and analyze whether the difference between the reception times of adjacent data packets is greater than the watchdog time of the configuration device. If the difference between the reception times is greater than the watchdog time of the configuration device, it is considered that the configuration device has a station loss anomaly.

[0092] In some embodiments of the present disclosure, the configuration device anomaly monitoring device 40 further includes a display module 46, which is used to display the anomaly monitoring results of the configuration device to the user, and the anomaly monitoring results include packet loss anomalies and / or station loss anomalies.

[0093] In some embodiments of the present disclosure, the display module 46 further includes combining the network topology diagram of the configuration device and displaying the anomaly monitoring results of the configuration device on the network topology diagram.

[0094] Figure 4The configuration device anomaly monitoring device of the embodiment can be used to execute the technical solution of the above method embodiment, and its implementation principle and technical effect are similar, which will not be elaborated here.

[0095] Figure 5 The following is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. The electronic device provided by the embodiment of the present disclosure can execute the processing flow provided by the method embodiment of the configuration device anomaly monitoring method, as Figure 5 shown. The electronic device 5 includes: a processor 51, a memory 52, and a computer program 53; wherein, the computer program is stored in the memory 52 and is configured to read the computer program 53 from the memory 52 and execute the computer program 53 to implement the embodiment of the present disclosure Figures 1 to 4 to provide the configuration device anomaly monitoring method.

[0096] In addition, an embodiment of the present disclosure also provides a computer-readable storage medium. The storage medium can store a computer program. When the computer program is executed by a processor, the processor is enabled to implement the embodiment of the present disclosure Figures 1 to 4 to provide the configuration device anomaly monitoring method.

[0097] The above storage medium can include, for example, a memory of a computer program. The above computer program can be executed by the processor of the configuration device anomaly monitoring device to complete the embodiment of the present disclosure Figures 1 to 4 to provide the configuration device anomaly monitoring method. Optionally, the storage medium can be a non-transitory computer-readable storage medium. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (Random Access Memory, RAM), a compact disc read-only memory (Compact Disc ROM, CD-ROM), a magnetic tape, a floppy disk, and an optical data storage configuration device, etc.

[0098] The above are only specific implementation manners of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art. The general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to these embodiments described herein, but will be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A configuration device abnormality monitoring method, characterized in that: include: Parsing the obtained engineering file of at least one controller to obtain an I / O cycle of at least one configuration device connected to the controller; Based on the I / O cycle of the at least one configuration device, calculating and obtaining the cycle count cycle of the configuration device; Obtaining a cycle count value of a current data packet and a previous data packet of the at least one configuration device, and calculating a difference between the cycle count values ​​of the current data packet and the previous data packet; Monitor whether the difference between the cycle count value and the cycle count period meets a preset condition. If not, determine that an abnormality exists in the configuration device.

2. The method according to claim 1, characterized in that The monitoring of whether the difference between the cycle count value and the cycle count period meets a preset condition, and if not, determining that there is an abnormality in the configuration device, also includes: when the difference between the cycle count value and the cycle count period is different, determining that there is a packet loss abnormality in the configuration device.

3. The method according to claim 1, characterized in that The method of obtaining the cycle count value of the current data packet and the previous data packet of the at least one configuration device also includes: obtaining the current data packet and the previous data packet of the at least one configuration device, reading the message information of the data packet, and obtaining the cycle count value of the current data packet and the cycle count value of the previous data packet from the message information.

4. The method according to claim 1, characterized in that: The engineering file of the at least one controller is parsed to obtain the watchdog time of at least one configuration device connected to the controller.

5. The method according to claim 4, characterized in that Acquire multiple data packets sent by the configuration device, record the receiving time of the multiple data packets, calculate the difference in receiving time of adjacent data packets, and analyze whether the difference in receiving time of adjacent data packets is greater than the watchdog time of the configuration device. If the difference in receiving time is greater than the watchdog time of the configuration device, it is considered that the configuration device has a station loss exception.

6. The method according to any one of claims 1 to 5, characterized in that: The abnormal monitoring result of the configuration device is displayed to the user, wherein the abnormal monitoring result includes packet loss abnormality and / or station loss abnormality.

7. The method according to any one of claim 6, characterized in that: Combined with the network topology diagram of the configuration device, the abnormal monitoring result of the configuration device is displayed on the network topology diagram.

8. A configuration equipment abnormality monitoring device, characterized in that: include: A parsing module, used to parse the obtained engineering file of at least one controller to obtain the I / O cycle of at least one configuration device connected to the controller; A calculation module, configured to calculate a cycle count period of the configuration device based on an I / O cycle of the at least one configuration device; An acquisition module, used for acquiring a cycle count value of a current data packet and a previous data packet of the at least one configuration device, and calculating a difference between the cycle count values ​​of the current data packet and the previous data packet; The monitoring module is used to monitor whether the difference between the cycle count value and the cycle count period meets a preset condition. If not, it is determined that an abnormality exists in the configuration device.

9. An electronic device, characterized in that: include: processor; Memory for storing computer programs; Wherein, the processor is used to read the computer program from the memory and execute the computer program to implement the configuration device abnormality monitoring method described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the processor implements the configuration device abnormality monitoring method described in any one of claims 1 to 7.

Images