CN110515369B - Safety association data processing method and device of automatic control system - Google Patents
Safety association data processing method and device of automatic control system Download PDFInfo
- Publication number
- CN110515369B CN110515369B CN201910810241.5A CN201910810241A CN110515369B CN 110515369 B CN110515369 B CN 110515369B CN 201910810241 A CN201910810241 A CN 201910810241A CN 110515369 B CN110515369 B CN 110515369B
- Authority
- CN
- China
- Prior art keywords
- data
- safety
- detection sensor
- interface
- fault
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G05—CONTROLLING; REGULATING
- G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
- G05B23/00—Testing or monitoring of control systems or parts thereof
- G05B23/02—Electric testing or monitoring
- G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
- G05B23/0208—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the configuration of the monitoring system
Abstract
The embodiment of the invention provides a safety associated data processing method and a device, a processor, electronic equipment and a storage medium of an automatic control system, wherein the safety associated data processing method of the automatic control system comprises the following steps: receiving a user call instruction, and acquiring call object information corresponding to the call instruction by analyzing the call instruction; and calling at least one standardized function block according to the calling object information to acquire safety associated data corresponding to the calling object information, thereby fully utilizing the safety associated data, effectively ensuring the safe operation of the automatic control system and reducing the development cost of the automatic control system.
Description
Technical Field
The embodiment of the invention relates to the technical field of industrial control, in particular to a security association data processing method and device of an automatic control system, a processor, electronic equipment and a storage medium.
Background
The fault safety system is a part of an automatic control system, is used for providing a safety function for a production line or equipment when the production line or the equipment has a functional fault, and is a very important protection measure for operators and controlled equipment so as to avoid the injury and the accident of the operators and the equipment and ensure the normal production activity. Generally, fail-safe systems are not easily actuatable, and only function when an automated control system fails.
However, in the prior art, the related safety-related data of the automation control system is not effectively managed, which results in higher development cost of the automation control system.
Disclosure of Invention
In order to solve the above problems, embodiments of the present invention provide a method and an apparatus for processing security association data of an automation control system, a processor, an electronic device, and a storage medium, so as to at least partially solve the above problems.
According to a first aspect of the embodiments of the present invention, there is provided a method for processing safety association data of an automation control system, including:
receiving a user call instruction, and acquiring call object information corresponding to the call instruction by analyzing the call instruction;
and calling at least one standardized function block according to the calling object information to acquire safety associated data corresponding to the calling object information.
Optionally, after the obtaining of the security association data corresponding to the invocation object information, the method further includes: and calling at least one interface library file to display the safety association data corresponding to the calling object information.
Optionally, the call object information includes at least one of failure detection sensor information, failure safety system information, or controlled device information.
Optionally, before the invoking at least one standardized function block to obtain the security association data corresponding to the invocation target information, the method further includes:
collecting security association data, the security association data comprising: at least one of fault detection sensor association data, controlled device association data, or failsafe system association data;
and compiling the at least one standardized function block and the interface library file which can be repeatedly called according to the collected safety associated data.
Optionally, the collecting security association data specifically includes: and calling a data acquisition program function block to acquire the safety associated data according to the output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment.
Optionally, before invoking the data acquisition program function block to acquire the safety-related data according to the output data of at least one of the fault detection sensor, the fault safety system, or the controlled device, the method further includes:
determining the configuration address of an I/O interface of output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment;
determining at least one transmission channel address used by the I/O interface according to the address offset of the I/O interface and the configuration address;
and compiling the data acquisition program functional block which can be called repeatedly according to the at least one transmission channel address.
Optionally, the address offset of the I/O interface is determined according to an identifier of a template type of the I/O interface.
Optionally, the data collection program functional block is compiled based on an Openness high-level language.
Optionally, the fault detection sensor correlation data comprises: at least one of status data of the failure detection sensor, position data of the failure detection sensor, or operation time of the failure detection sensor; and/or the presence of a gas in the atmosphere,
the failsafe system associated data includes: at least one of status data of the failsafe system, safety diagnostic data of the failsafe system, or lifecycle data of the failsafe system; and/or the presence of a gas in the atmosphere,
the controlled device association data comprises: at least one of the name of the controlled equipment, the work position of the controlled equipment or the state data of the controlled equipment.
According to a second aspect of an embodiment of the present invention, there is provided a security association data processing apparatus of an automation control system, including:
the analysis module is used for receiving a user call instruction and acquiring corresponding call object information by analyzing the call instruction;
and the calling module is used for calling at least one standardized function block according to the calling object information so as to acquire the safety association data corresponding to the calling object information.
According to a third aspect of the embodiments of the present invention, there is provided a processor, configured to execute a program, where the program executes the method according to any one of the embodiments of the present invention.
According to a fourth aspect of embodiments of the present invention, there is provided an electronic apparatus, including: one or more processors, memory, a display unit, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing any of the methods of embodiments of the present invention.
According to a fourth aspect of the embodiments of the present invention, there is provided a storage medium including a stored program, wherein when the program runs, a device including the storage medium is controlled to execute the method according to any one of the embodiments of the present invention.
In the embodiment of the invention, after a user calling instruction is received and the calling object information corresponding to the calling instruction is obtained by analyzing the calling instruction, at least one standardized function block is called according to the calling object information to obtain the safety associated data corresponding to the calling object information, so that the safety associated data is fully utilized, the safe operation of an automatic control system is effectively ensured, and the development cost of the automatic control system is reduced.
Drawings
The drawings are only for purposes of illustrating and explaining the present invention and are not to be construed as limiting the scope of the present invention. Wherein the content of the first and second substances,
FIG. 1 is a schematic diagram of an automated control system according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating a method for processing safety-related data of an automation control system according to an embodiment of the invention;
FIG. 3 is a diagram illustrating the compilation of the at least one standardized function block and the interface library file according to an embodiment of the invention;
FIG. 4 is a diagram illustrating the function blocks of the data collection program that are programmed to be recalled in accordance with one embodiment of the present invention;
FIG. 5 is a schematic diagram illustrating compiling the at least one standardized function block and the interface library file according to the collected security association data according to an embodiment of the invention;
FIG. 6 is a schematic diagram of an interface for displaying the failure detection sensor associated data by invoking a failure detection sensor associated data interface library file in an embodiment in accordance with the present invention;
FIG. 7 is a schematic diagram illustrating compiling a failsafe system associated data collection standardized function block and a failsafe system associated data interface library file in accordance with an embodiment of the present invention;
FIG. 8 is an interface diagram illustrating a call to a failsafe system associated data interface library file to display failsafe system associated data in accordance with an embodiment of the present invention;
FIG. 9 is a block diagram of a safety-related data processing apparatus of an automated control system according to an embodiment of the present invention; and
fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
List of reference numerals:
101: a programmable logic controller;
102: an I/O interface;
103: a fault detection sensor;
104: a controlled device;
201: receiving a user call instruction, and acquiring call object information corresponding to the call instruction by analyzing the call instruction;
202: and calling at least one standardized function block according to the calling object information to acquire safety associated data corresponding to the calling object information.
301: collecting security association data, the security association data comprising: at least one of fault detection sensor association data, failsafe system association data, or controlled device association data;
302: and compiling the at least one standardized function block and the interface library file which can be repeatedly called according to the collected safety associated data.
401: determining a configuration address of an I/O interface of output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment;
402: determining at least one transmission channel address used by the I/O interface according to the address offset of the I/O interface and the configuration address;
403: and compiling the data acquisition program functional block which can be called repeatedly according to the at least one transmission channel address.
501: compiling a fault detection sensor associated data acquisition standardized function block and a fault detection sensor associated data interface library file which can be repeatedly called according to the acquired fault detection sensor associated data so as to acquire the fault detection sensor associated data corresponding to the fault detection sensor information and display the fault detection sensor associated data;
502: compiling a repeatedly-called correlated data acquisition standardized function block of the fault safety system and a correlated data interface library file of the fault safety system according to the collected correlated data of the fault safety system so as to acquire the correlated data of the fault safety system corresponding to the information of the fault safety system and display the correlated data of the fault safety system;
503: compiling a repeatedly-called controlled equipment associated data acquisition standardized function block and a controlled equipment associated data interface library file according to the acquired controlled equipment associated data so as to acquire the controlled equipment associated data corresponding to the controlled equipment information and display the controlled equipment associated data;
701: compiling a state data acquisition standardized function block of the fail-safe system and a state data interface library file of the fail-safe system which can be repeatedly called according to the acquired state data of the fail-safe system so as to acquire the state data of the fail-safe system corresponding to the fail-safe system information and display the state data of the fail-safe system;
702: compiling a safety diagnosis data acquisition standardized function block of the fault safety system and a safety diagnosis data interface library file of the fault safety system which can be repeatedly called according to the acquired safety diagnosis data of the fault safety system so as to acquire the safety diagnosis data of the fault safety system corresponding to the fault safety system information and display the safety diagnosis data of the fault safety system;
703: compiling a life cycle data acquisition standardized function block of the fault safety system and a life cycle data interface library file of the fault safety system which can be repeatedly called according to the acquired life cycle data of the fault safety system so as to acquire the life cycle data of the fault safety system corresponding to the fault safety system information and display the life cycle data of the fault safety system
901: analysis module
902: calling module
1001: a processor;
1002: a memory; and
1003: a display unit.
Detailed Description
In order to more clearly understand technical features, objects, and effects of embodiments of the present invention, specific embodiments of the present invention will now be described with reference to the accompanying drawings.
Failsafe systems are generally not easily actuatable, and generally function when an automated control system fails. For example: the operation of stopping the vehicle is generally not performed by pressing the emergency stop button (as a failure detection sensor), but the emergency stop button is pressed only when an emergency actually occurs. The frequency of the fault detection sensor action is therefore typically relatively low. But if these failure detection sensors are not active for a long time, they may have been damaged but not discovered, which also results in an increased potential risk. In addition, when a fault detection sensor (such as an emergency stop button) operates, the field has no indication data, and if the field is installed in a large number and the position is hidden, an operator can hardly find out which emergency stop button is pressed, so that a large amount of cost is needed to determine the specific pressed emergency stop button in the later period if a reset operation is carried out. Furthermore, the controlled device integrated with the fail-safe system cannot intuitively and conveniently master relevant data of the fail-safe system, such as the safety level that the fail-safe system can reach, the life cycle of the fail-safe system, and the like, for a user. For various reasons, which are listed or not listed, the safety-related data is not fully utilized, and the development cost of the automation control system is high.
In the embodiment of the invention, after a user calling instruction is received and the calling object information corresponding to the user calling instruction is obtained by analyzing the calling instruction, at least one standardized function block is called according to the calling object information to obtain the safety associated data corresponding to the calling object information, so that the safety associated data is fully utilized, the safe operation of the automatic control system is effectively ensured, and the development cost of the automatic control system is reduced.
Fig. 1 is a schematic diagram of an automated control system according to an embodiment of the invention. As shown in fig. 1, the automation control system includes a programmable logic controller 101, an I/O interface 102, a failure detection sensor 103, and a controlled device 104, where the programmable logic controller 101 is configured to control the failure detection sensor 103 and the controlled device 104, the failure detection sensor 103 is configured to detect whether the controlled device 104 fails, and the I/O interface 102 is configured to output data from the failure detection sensor 103 and the controlled device 104.
Fig. 2 is a flow chart illustrating a method for processing safety-related data of an automation control system according to an embodiment of the present invention. As shown in fig. 2, the method for processing safety-related data of the automation control system in the present embodiment includes the following steps 201 to 202:
In the embodiment of the invention, after a user calling instruction is received and the calling object information corresponding to the user calling instruction is obtained by analyzing the calling instruction, at least one standardized function block is called according to the calling object information to obtain the safety associated data corresponding to the calling object information, and because the standardized function block can be directly called, the workload of a user in the aspects of programming development and project integration is simplified, and the project implementation time is saved; the interface library file is helpful for a user to comprehensively know the equipment in the automatic control system, provides timely information and help for the safety maintenance of the equipment, can effectively shorten the downtime of the equipment or the system, and ensures the timely treatment of equipment faults, thereby effectively ensuring the safe operation of the automatic control system. In addition, the safety associated data are obtained by calling at least one standardized function block, so that the safety associated data can be summarized and effectively utilized, and effective data storage is provided for digitization of a future automatic control system. Therefore, management of safety associated data is effectively achieved through the standardized function blocks, and development cost of the automatic control system is reduced integrally.
Optionally, in an embodiment of the present invention, the security association data processing method shown in fig. 2 is executed by a programmable logic controller.
Further, in this embodiment of the present invention, after obtaining the security association data corresponding to the invocation target information, the method further includes: and calling at least one interface library file to display the safety associated data corresponding to the calling object information.
The standardized function block and the interface library file are configured through the programmable logic controller so as to call the standardized function block and the interface library file, and then the safety associated data corresponding to the called object information can be acquired and displayed, and the safety associated data can be rapidly and comprehensively and accurately known, so that the safe operation of the automatic control system is effectively guaranteed.
Optionally, in this embodiment of the present invention, the call object information includes at least one of failure detection sensor information, failure safety system information, or controlled device information.
Optionally, in an embodiment of the present invention, before the step 202, a processing step of compiling the at least one standardized function block and the interface library file may be performed, which is described in detail in fig. 3.
Optionally, in an embodiment of the present invention, fig. 3 is a schematic diagram of compiling the at least one standardized function block and the interface library file in an embodiment of the present invention. As shown in fig. 3, the process of compiling the at least one standardized function block and the interface library file includes the following steps 301 to 302:
Optionally, in this embodiment of the present invention, when the safety-related data is collected in step 301, a data collection program function block is called to collect the safety-related data specifically according to output data of at least one of the fault detection sensor, the fault safety system, and the controlled device.
Optionally, in the embodiment of the present invention, the data collection program function block called in step S302 is programmed through steps 401 to 403 in fig. 4 as follows, which may be executed before step S302.
FIG. 4 is a diagram illustrating the function blocks of the data collection program that are programmed to be called repeatedly, according to an embodiment of the present invention. As shown in fig. 4, the process of programming the repeatedly called function block of the data collection program includes the following steps 401 to 403:
and 403, compiling the function block of the data acquisition program which can be repeatedly called according to the at least one transmission channel address.
Optionally, in an embodiment of the present invention, the configuration address of the I/O interface in step 401 may be obtained from system configuration information formed by the automation control system shown in fig. 1, where the system configuration information is stored on the programmable logic controller, and the system configuration information includes the I/O interface configuration information. The I/O interface configuration information further comprises an identifier of a template type of the I/O interface and a configuration address of the I/O interface; the configuration address of the I/O interface is an address allocated to the I/O interface, so that output data of at least one of the fault detection sensor, the controlled device and the fault safety system can be transmitted conveniently.
Optionally, in step 401, in the embodiment of the present invention, the address offset of the I/O interface is specifically obtained according to the I/O interface configuration information in the system configuration information, and the address offset of the I/O interface is specifically determined according to an identifier (module type ID) of a template type of the I/O interface;
optionally, in this embodiment of the present invention, the identifier of the template type of the I/O interface is order number information of the I/O interface.
Optionally, in combination with the embodiments shown in fig. 3 and 4, a transmission channel is configured on the I/O interface, and output data of at least one of the fault detection sensor, the fault safety system, or the controlled device is output in the form of a safety state value in the transmission channel to form safety associated data.
Therefore, when the safety-related data is collected by the scheme of the embodiment of fig. 3 and 4, if the transmission channel address of the safety-related data changes due to the change of the configuration address of the I/O interface, the data collection program function block may be repeatedly called to directly determine the configuration address and the address offset of the I/O interface, and further determine the transmission channel address, and finally, the collection of the safety-related data is realized, thereby further reducing the development cost of the automatic control system.
The application scenarios of the above examples shown in fig. 3 and 4 include, but are not limited to: in different automation control systems, the slots of the communication bus plugged into the same I/O interface in the automation control system are different, which results in different configuration addresses for the same I/O interface. Therefore, codes developed corresponding to the steps 401 to 403 are reintroduced into the programmable logic controller through some high-level languages, such as Open Network Edge Services Software (Openness) high-level languages, so as to be programmed into a data acquisition program function block, a configuration address of an I/O interface in the current automation control system is determined through the data acquisition program function block, an address offset of the I/O interface is determined through an identifier of a template type of the I/O interface, and a transmission channel address used by the I/O interface in the current automation control system is finally determined, so as to complete acquisition of safety related data.
Optionally, in an embodiment of the present invention, the template types of the I/O interface include: at least one of a digital quantity input type, a digital quantity output type, or an analog quantity input type. The digital quantity input type means that the I/O interface supports input of a switching quantity (for example, an emergency stop button is pressed) to the programmable logic controller, the digital quantity output type means that the I/O interface supports output of the switching quantity (for example, control of starting and stopping of a motor) from the programmable logic controller, and the analog quantity input type means that the I/O interface supports input of an analog quantity (for example, motor temperature) to the programmable logic controller.
Taking the example of an I/O interface having two transmission channels, the configuration address of the I/O interface occupies two bytes, and each transmission channel address occupies 1 byte. For example, in an automation control system X, two I/O interfaces S1 and S2 are configured, the template types of the two I/O interfaces are digital input types, if the I/O interface S1 is inserted into a first slot (referred to as slot a) of a backplane bus of the automation control system, the configuration address is, for example, 10, and since the template type is the digital input type, it is determined that the corresponding address offset is 2, the transmission channel address is 10+2=12, where the configuration address (taking two bytes as an example) of the I/O interface S1 is 10 and 11, and the transmission channel addresses are 12 and 13, respectively. The I/O interface S2 is inserted into the next slot next to the first slot A, namely the second slot (called slot B), and the last transmission channel address 13 of the I/O interface S1 inserted into the slot A is connected; thus, the configuration address of the I/O interface S2 inserted in the slot B can only start from 14, and since the address offset is also 2, the configuration addresses (for example, two bytes) of the I/O interface S2 are 14 and 15, and the transmission channel addresses are 16 and 17, respectively.
For another example, in another automation control system Y, two I/O interfaces S1 and S2 are configured, the template types of the two I/O interfaces are both digital input types, if the I/O interface S1 is plugged in a second slot (referred to as slot B) of a backplane bus of the automation control system, the configuration address is, for example, 14, and since the template type of the I/O interface S1 is the digital input type, it is determined that the corresponding address offset is 2, the transmission channel address is 14+2=16, wherein the configuration address (taking two bytes as an example) of the I/O interface S1 is 14 and 15, and the transmission channel addresses are 16 and 17, respectively. The I/O interface S2 is inserted into the next slot next to the second slot B, namely the third slot (called as slot C), because the last transmission channel address 17 of the I/O interface S1 inserted into the slot A; this results in that the configuration address of the I/O interface S2 plugged into the slot B can only start from 18, and since the address offset is also 2, the configuration addresses (for example, two bytes) of the I/O interface S2 are 17 and 18, and the transmission channel addresses are 19 and 20, respectively.
By repeatedly calling the programmed data acquisition program function blocks in the automatic control systems X and Y, the configuration addresses and the transmission channel addresses can be automatically determined by combining specific items, so that the acquisition of safety associated data is realized.
Optionally, in an embodiment of the present invention, the fault detection sensor related data includes: at least one of status data of the failure detection sensor, position data of the failure detection sensor, or operation time of the failure detection sensor. The controlled equipment collects the associated data and comprises the following steps: at least one of the name of the controlled equipment, the work position of the controlled equipment or the state data of the controlled equipment. The failsafe system associated data includes: at least one of status data of the failsafe system, safety diagnostic data of the failsafe system, or lifecycle data of the failsafe system.
Optionally, in the embodiment of the present invention, the safety-related data includes fault detection sensor-related data, fault safety system-related data, and controlled device-related data. Therefore, in step 302, the at least one standardized function block and the interface library file which can be repeatedly invoked are compiled for the failure detection sensor associated data, the fail-safe system associated data and the controlled device associated data respectively.
Specifically, fig. 5 is a schematic diagram illustrating compiling the at least one standardized function block and the interface library file according to the collected security association data in an embodiment of the present invention. As shown in fig. 5, the method may specifically include the following steps 501 to 503:
Optionally, in this embodiment of the present invention, the fault detection sensor related data in step 501 is specifically fault detection sensor related data collected from an I/O port, where the fault detection sensor related data includes: at least one of status data of the failure detection sensor, position data of the failure detection sensor, or operation time of the failure detection sensor. Of course, the failure detection sensor-related data need not be limited to include at least one of status data of the failure detection sensor, position data of the failure detection sensor, and operation time of the failure detection sensor. The status data of the failure detection sensor includes, but is not limited to, normal status data and abnormal status data, and the abnormal status data may be generated by a detection signal generated when the failure detection sensor detects a failure of the controlled device, for example, when the sensor fails (short circuit, disconnection, or the like).
Alternatively, in the embodiment of the present invention, the malfunction detection sensor includes, for example, a sudden stop button, a safety door position switch, and the like.
Specifically, fig. 6 is an interface schematic diagram for calling a fault detection sensor association data interface library file to display the fault detection sensor association data in the embodiment of the present invention. As shown in fig. 6, in response to the collection of the emergency stop function information of the emergency stop button, the safety level of the emergency stop function, the state of the emergency stop button (pressed), the action time of the emergency stop button, the recovery time of the emergency stop button, and the remaining time of the safety device (i.e., the controlled device) are displayed in the interface.
Optionally, the acquiring, by the controlled device, the associated data includes: at least one of the name of the controlled equipment, the work position of the controlled equipment or the state data of the controlled equipment. The name of the controlled equipment and the station of the controlled equipment can be collected from a data buffer area of the programmable logic controller or specified to be input by a user. In the case of a failsafe system, as described above, when a dangerous situation occurs in the automation control system, the fault sensor is triggered to generate a detection signal, which needs to be input into the diagnostic buffer of the programmable logic controller via the I/O interface, and therefore the status data of the controlled device is preferably the status data of the controlled device collected from the I/O interface.
The sequence of steps 501 to 503 is not particularly limited, and may be executed sequentially in any form or in parallel.
Therefore, in the embodiment of the present invention, through the above steps 501-503, no matter which fault monitoring sensor (for example, an emergency stop button) needs to be invoked, or any complete safety function (for example, a safety gate function), even any controlled device (for example, a motor), and the whole fault safety system (for example, a safety system of a certain production line), can be implemented by invoking the relevant safety-related data collection standardized function block and the safety-related data collection interface library file database.
Optionally, in an embodiment of the present invention, the associating data includes: for example, the status data of the failsafe system, the safety diagnostic data of the failsafe system, and the life cycle data of the failsafe system are described, and when the reusable failsafe system related data acquisition standardized function block and the failsafe system related data interface library file are compiled in step 502, the failsafe system related data acquisition standardized function block and the failsafe system related data interface library file may be compiled according to different types of failsafe system related data.
Fig. 7 is a schematic diagram of compiling a failsafe system associated data collection standardized function block and a failsafe system associated data interface library file in an embodiment of the invention. As shown in fig. 7, in an embodiment of the present invention, the step 602 may include the following steps: step 701-step 703:
Optionally, in an embodiment of the present invention, the state data of the failsafe system in step 701 may specifically include: at least one of the name of the fail-safe system, the safety level of the fail-safe system or the state information (abnormal or normal) of the fail-safe system can be established, so that a detection and reminding mechanism of the operation expiration of the fail-safe system can be established, the safety level of the fail-safe system can be ensured to meet the requirements of relevant standards, accidents and risks can be effectively prevented, and the safety of long-term operation of equipment of the automatic control system can be guaranteed.
Optionally, in an embodiment of the present invention, the safety diagnosis data of the failsafe system in the step 702 includes: the diagnostic information related to the fail-safe system includes, for example, a specific failure of the fail-safe system, a time at which the failure occurred, and the like, or at least one of system diagnostic interfaces of the fail-safe system. The system diagnostic interface of the fail-safe system includes, for example, intermediate data that presents a failure diagnostic process.
Optionally, in an embodiment of the present invention, the life cycle data of the failsafe system in step 703 includes: at least one of a commissioning time of the fail-safe system (including a start-up time and a run-time), a triggering time of the fail-safe system, a detection period of the fail-safe system, or a down time of the fail-safe system (a reset time).
Here, in the embodiment of the present invention shown in fig. 7, the state data acquisition standardized function block of the fail-safe system and the state data interface library file of the fail-safe system, the safety diagnosis data acquisition standardized function block of the fail-safe system and the safety diagnosis data interface library file of the fail-safe system, and the life cycle data acquisition standardized function block of the fail-safe system and the life cycle data interface library file of the fail-safe system are respectively created. In the practical application process, the state data acquisition standardization function block of the fault safety system, the safety diagnosis data acquisition standardization function block of the fault safety system and the life cycle data acquisition standardization function block of the fault safety system can be compiled, but only one fault safety system associated data interface database file can be compiled, so that important fault safety system associated data can be selected in one interface to be displayed.
Optionally, fig. 8 is an interface schematic diagram illustrating that a failsafe system associated data interface library file is called to display failsafe system associated data in an embodiment of the present invention. As shown in fig. 8, in the interface, the specific content displayed includes: the start-up time and run time of the failsafe system, the safety level of the failsafe system, and the status of the failsafe system, etc.
Fig. 9 is a schematic structural diagram of a safety-related data processing apparatus of an automation control system according to an embodiment of the present invention. As shown in fig. 9, the security association data processing apparatus may include:
the analysis module 901 is used for receiving a user call instruction and obtaining the corresponding call object information by analyzing the call instruction;
a calling module 902, configured to call at least one standardized function block according to the call object information, so as to obtain security association data corresponding to the call object information.
The embodiment of the invention also provides a processor, which is used for running the program, wherein the method in any embodiment of the invention is executed when the program runs.
Fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 10, the electronic apparatus includes: one or more processors 1001, memory 1002, a display unit 1003, and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the methods described in any of the embodiments of the present invention.
The embodiment of the invention also provides a storage medium, which comprises a stored program, wherein when the program runs, a device comprising the storage medium is controlled to execute the method in any embodiment of the invention.
Note that the computer storage media of the present invention can be either computer readable signal media or computer readable storage media or any combination of the two. The computer readable medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access storage media (RAM), a read-only storage media (ROM), an erasable programmable read-only storage media (EPROM or flash memory), an optical fiber, a portable compact disc read-only storage media (CD-ROM), an optical storage media piece, a magnetic storage media piece, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
It should be understood that although the specification has been described in terms of various embodiments, not every embodiment includes every single embodiment, and such description is for clarity purposes only, and it will be appreciated by those skilled in the art that the specification as a whole can be combined as appropriate to form additional embodiments as will be apparent to those skilled in the art.
The above description is only an exemplary embodiment of the present invention, and is not intended to limit the scope of the present invention. Any person skilled in the art should be able to make equivalent changes, modifications and combinations without departing from the concept and principle of the embodiments of the present invention.
Claims (8)
1. A safety association data processing method of an automation control system is characterized by comprising the following steps:
receiving a user call instruction, and acquiring call object information corresponding to the call instruction by analyzing the call instruction; the calling object information comprises at least one of fault detection sensor information, fault safety system information or controlled equipment information;
collecting security association data, the security association data comprising: at least one of fault detection sensor association data, controlled device association data, or failsafe system association data;
compiling at least one standardized function block and an interface library file which can be repeatedly called according to the collected safety associated data;
calling at least one standardized function block according to the calling object information to acquire safety associated data corresponding to the calling object information;
wherein the fault detection sensor correlation data comprises: at least one of status data of the failure detection sensor, position data of the failure detection sensor, or operation time of the failure detection sensor; the controlled device association data comprises: at least one of the name of the controlled equipment, the station of the controlled equipment or the state data of the controlled equipment; the failsafe system associated data includes: at least one of status data of the failsafe system, safety diagnostic data of the failsafe system, or lifecycle data of the failsafe system; the collecting of the security association data specifically comprises: calling a data acquisition program function block to acquire the safety associated data according to output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment; before the step of calling a data acquisition program function block to acquire the safety associated data according to the output data of at least one of the fault detection sensor, the fault safety system or the controlled device, the method further comprises the following steps:
determining a configuration address of an I/O interface of output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment;
determining at least one transmission channel address used by the I/O interface according to the address offset of the I/O interface and the configuration address;
and compiling the data acquisition program functional block which can be called repeatedly according to the at least one transmission channel address.
2. The method according to claim 1, wherein after obtaining the security association data corresponding to the call object information, further comprising: and calling at least one interface library file to display the safety association data corresponding to the calling object information.
3. The method of claim 1, wherein the address offset of the I/O interface is determined based on an identification of a template type of the I/O interface.
4. The method of claim 1, wherein the data collection program function block is based on Openness high level language programming.
5. A safety-associated data processing device of an automation control system, comprising:
the analysis module (901) is used for receiving a user call instruction and obtaining the corresponding call object information by analyzing the call instruction; the calling object information comprises at least one of fault detection sensor information, fault safety system information or controlled equipment information;
a security association data collection module for collecting security association data, said security association data comprising: at least one of fault detection sensor associated data, controlled device associated data, or failsafe system associated data;
the compiling module is used for compiling at least one standardized function block and an interface library file which can be repeatedly called according to the collected safety associated data;
a calling module (902) for calling at least one standardized function block according to the calling object information to obtain security association data corresponding to the calling object information;
wherein the fault detection sensor association data comprises: at least one of status data of the failure detection sensor, position data of the failure detection sensor, or operation time of the failure detection sensor; the controlled device association data comprises: at least one of the name of the controlled equipment, the station of the controlled equipment or the state data of the controlled equipment; the failsafe system association data includes: at least one of status data of the failsafe system, safety diagnostic data of the failsafe system, or lifecycle data of the failsafe system; the collecting of the security association data specifically comprises: according to output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment; before the security association data acquisition module acquires the security association data, the security association data processing device of the automatic control system further executes the following steps:
determining the configuration address of an I/O interface of output data of at least one of the fault detection sensor, the fault safety system or the controlled equipment;
determining at least one transmission channel address used by the I/O interface according to the address offset of the I/O interface and the configuration address;
and compiling the data acquisition program functional block which can be repeatedly called according to the at least one transmission channel address.
6. A processor, characterized in that the processor is configured to run a program, wherein the program when running performs the method of any of claims 1 to 4.
7. An electronic device, comprising: one or more processors (1001), memory (1002), a display unit (1003), and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the method of any of claims 1-4.
8. A storage medium comprising a stored program, wherein a device comprising the storage medium is controlled to perform the method of any one of claims 1 to 4 when the program is run.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910810241.5A CN110515369B (en) | 2019-08-29 | 2019-08-29 | Safety association data processing method and device of automatic control system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910810241.5A CN110515369B (en) | 2019-08-29 | 2019-08-29 | Safety association data processing method and device of automatic control system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110515369A CN110515369A (en) | 2019-11-29 |
| CN110515369B true CN110515369B (en) | 2022-11-15 |
Family
ID=68628082
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910810241.5A Active CN110515369B (en) | 2019-08-29 | 2019-08-29 | Safety association data processing method and device of automatic control system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110515369B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2153288A1 (en) * | 2007-06-04 | 2010-02-17 | Endress+Hauser GmbH+Co. KG | Field device |
| CN102591331A (en) * | 2012-03-14 | 2012-07-18 | 桂林中昊力创机电设备有限公司 | Fault visual diagnostic system of automatic equipment |
| CN103529747A (en) * | 2013-10-24 | 2014-01-22 | 中铁隧道集团有限公司 | Fault handling system of drill jumbo |
| CN109445412A (en) * | 2018-10-26 | 2019-03-08 | 天津英创汇智汽车技术有限公司 | A kind of condition detection method and device |
| CN109582528A (en) * | 2018-09-11 | 2019-04-05 | 阿里巴巴集团控股有限公司 | State monitoring method, device, electronic equipment and computer readable storage medium |
| CN109597397A (en) * | 2018-11-28 | 2019-04-09 | 北京星航机电装备有限公司 | A kind of fault diagnosis system and method based on ForceControl configuration software |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0328706A1 (en) * | 1988-02-18 | 1989-08-23 | Hans Dr. Viessmann | Safety device for control and regulation systems |
| DE19801137A1 (en) * | 1998-01-14 | 1999-07-22 | Siemens Ag | Automation system operating method e.g. for rapid shut-down of automated processes in emergency |
| US7539597B2 (en) * | 2001-04-10 | 2009-05-26 | Smartsignal Corporation | Diagnostic systems and methods for predictive condition monitoring |
| CN104090186B (en) * | 2014-07-03 | 2016-08-31 | 上海辰竹仪表有限公司 | A kind of analog quantity automatic checking system based on safety instrument |
| DE102014113135A1 (en) * | 2014-09-11 | 2016-03-17 | Pilz Gmbh & Co. Kg | Monitored adaptable emergency stop switch |
| US20160217674A1 (en) * | 2015-01-26 | 2016-07-28 | Trane International Inc. | Remote monitoring of an hvac system for fault detection and diagnostics |
-
2019
- 2019-08-29 CN CN201910810241.5A patent/CN110515369B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2153288A1 (en) * | 2007-06-04 | 2010-02-17 | Endress+Hauser GmbH+Co. KG | Field device |
| CN102591331A (en) * | 2012-03-14 | 2012-07-18 | 桂林中昊力创机电设备有限公司 | Fault visual diagnostic system of automatic equipment |
| CN103529747A (en) * | 2013-10-24 | 2014-01-22 | 中铁隧道集团有限公司 | Fault handling system of drill jumbo |
| CN109582528A (en) * | 2018-09-11 | 2019-04-05 | 阿里巴巴集团控股有限公司 | State monitoring method, device, electronic equipment and computer readable storage medium |
| CN109445412A (en) * | 2018-10-26 | 2019-03-08 | 天津英创汇智汽车技术有限公司 | A kind of condition detection method and device |
| CN109597397A (en) * | 2018-11-28 | 2019-04-09 | 北京星航机电装备有限公司 | A kind of fault diagnosis system and method based on ForceControl configuration software |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110515369A (en) | 2019-11-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107918382B (en) | Automobile fault diagnosis method, automobile fault diagnosis device and electronic equipment | |
| EP2990896A1 (en) | Information processing device, and information processing device control method and control program | |
| WO1999017199A1 (en) | Automated validation and verification of computer software | |
| CN101876935B (en) | Debugging program monitoring method and device | |
| CN114076873A (en) | Cable fault analysis and prediction method and device | |
| CN112025766B (en) | Robot system health self-checking method and device and electronic equipment | |
| CN103713215A (en) | System and method for detecting X-ray tube running state | |
| CN103814501A (en) | Diagnosis for GOOSE communication | |
| CN113832663B (en) | Control chip fault recording method and device and control chip fault reading method | |
| CN110515369B (en) | Safety association data processing method and device of automatic control system | |
| CN106529304A (en) | Android application concurrent vulnerability detection system | |
| CN109871307A (en) | A kind of automated testing method being accurately positioned starting matter of time | |
| CN111124828B (en) | Data processing method, device, equipment and storage medium | |
| EP3825855A1 (en) | Variable memory diagnostics | |
| CN115755147A (en) | Method, device, medium and computing equipment for evaluating radioactive aerosol | |
| KR20180014978A (en) | Method and apparatus for analyzing safety of automotive software | |
| CN106776236B (en) | Method and apparatus for monitoring execution of a program | |
| WO2022160141A1 (en) | Industrial network-based codeless tracking analytics method and apparatus for industrial software | |
| CN103853643A (en) | An apparatus and a method for memory testing by a programmable circuit in a safety critical system | |
| US10222791B2 (en) | Operation assistance apparatus at time of accident in plant | |
| CN106021649A (en) | A model configuration detector used for a virtual circuit verifying platform and a control method | |
| CN112817827A (en) | Operation and maintenance method, device, server, equipment, system and medium | |
| CN111930081A (en) | Method and device for monitoring AGV state, edge device and storage medium | |
| CN112905199A (en) | Code update detection method and device | |
| CN112735103A (en) | Alarm correlation identification method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |