An IO board card virtualization method of a non-safety level DCS and a related device

Abstract

The application discloses an IO board card virtualization method of a non-safety level DCS and a related device, relates to the technical field of industrial automation control, and comprises the following steps: by analyzing the configuration file of an engineering, input point tables, output point tables and fault point tables of a basic control layer are extracted according to the input and output functions realized by real IO board cards; when virtualization is performed, the input point tables, the output point tables and the fault point tables are loaded into a virtual basic control layer relationship dynamic library, a virtual DCS system is initialized, and each point table is allocated a continuous space in a shared memory according to the type of the point table; the fault correlation relationship between nodes at different levels under a control station is stored in the form of a fault tree in the fault point table. Then, a virtual control station and a virtual IO board card are generated according to the fault point table, and the virtualization of the IO board card is realized. The application realizes batch data communication and high-precision fault simulation of the virtual IO board card, and reduces the dependence on DCS hardware.

Description

Technical Field

[0001] This application relates to the field of industrial automation control technology, and in particular to a method and related apparatus for virtualizing the I / O boards of a non-safety-grade DCS. Background Technology

[0002] In the field of traditional industrial automation control, the physical input and output (IO) boards used to build conventional non-safety-grade distributed control systems (DCS) are expensive and dependent on specific hardware architectures, limiting system scalability. Traditional IO boards also lack sufficient fault simulation capabilities, making it difficult to effectively simulate complex scenarios (such as channel-level faults and board-level communication interruptions).

[0003] Existing common IO board virtualization technologies also have obvious shortcomings: they only focus on input and output signal simulation and fail to fully realize core functions such as parameter configuration and fault-safe output; they fail to effectively solve the compatibility problem between virtual IO boards and physical IO boards at the configuration file level; and they lack the ability to dynamically adapt to the engineering structure of DCS field control layer. Summary of the Invention

[0004] The purpose of this application is to provide a method and related apparatus for virtualizing IO boards in a non-security-grade DCS, which can realize batch data communication and high-precision fault simulation of virtual IO boards, and reduce the dependence on DCS hardware.

[0005] To achieve the above objectives, this application provides the following solution:

[0006] Firstly, this application provides a method for virtualizing IO boards in a non-security-grade DCS, comprising the following steps:

[0007] By parsing the configuration file of the project and based on the input and output functions implemented by the actual IO board, the input point table, output point table, and fault point table of the basic control layer are extracted. The basic control layer is used to interact with the field equipment layer and the monitoring operation layer. The fault point table is used to store the fault association relationship between different levels of nodes under the control station in the form of a fault tree.

[0008] The input point table, output point table, and fault point table are loaded into the virtual basic control layer relational dynamic library, and the virtual DCS system is initialized. According to the type of each point table, a contiguous space is allocated in the shared memory. The virtual basic control layer relational dynamic library is used to store the mapping relationship between each point table and each contiguous space in the shared memory.

[0009] A virtual control station and virtual I / O boards are generated based on the fault point table. The different functions of the real I / O boards are simulated according to the input point table, output point table, and fault point table, thus virtualizing the I / O boards. The virtual control station includes several virtual I / O boards. The simulation functions include input / output functions and fault simulation functions. The input / output function controls the various virtual I / O boards under the virtual control station to interact with each other according to the input and output point tables. The fault simulation function performs fault correlation responses based on the fault point table. Data interaction refers to the data transmission between each virtual I / O board and the virtual field device layer and virtual monitoring operation layer through a virtual gateway. The data transmitted between the virtual I / O boards and the virtual field device layer and virtual monitoring operation layer is in the form of engineering values. The fault correlation response is that when any node fails, the virtual gateway changes the variable value of the node with the failed node in shared memory and sets the fault flag for the corresponding node at the downstream level of the failed node according to the fault correlation relationship in the fault point table.

[0010] Optionally, the virtual I / O board is divided into a virtual input board and a virtual output board. The virtual input board is used to obtain data from the corresponding node through the virtual gateway according to the input point table; the virtual output board is used to transmit data to the corresponding node through the virtual gateway according to the output point table.

[0011] Optionally, before generating the virtual control station and virtual I / O board based on the fault point table, the following steps are also included: analyzing the functions of the real I / O board of the non-safety-grade DCS, retaining the normal working mode function, equipment configuration function, channel acquisition function, and channel output function; integrating the channel acquisition function and channel output function into input / output function; modifying the initialization mode function into an initialization state function, and modifying the power-off storage function and self-diagnosis function into a fault simulation function; and removing the watchdog function, bus function, hardware slot acquisition function, chassis address acquisition function, and firmware code download function.

[0012] Optionally, the configuration file of the project is the core technology carrier for the design, implementation and operation of non-safety-level DCS. The configuration file defines the functional configurations throughout the entire life cycle, such as control logic, human-machine interface and communication rules. Each control station corresponds to a configuration file, and the arrangement order of each IO board in each control station is independent of each other.

[0013] Optionally, the configuration file of a single control station is first parsed to generate a single control station communication point table. Then, all single control station communication point tables are merged according to their corresponding arrangement order to generate a total communication point table. The communication point table is divided into input point table and output point table according to type. Specifically, by parsing the configuration of the driver information of the input or output board of each control station, the number and arrangement order of the input and output boards in the control station, the arrangement order of the variables of each channel, and the data type of each channel are obtained. The board type, variable description, and upper and lower limits of each channel are also obtained by parsing the configuration file of the project.

[0014] Optionally, a contiguous space is allocated in the shared memory according to the type of each point table. Specifically, the corresponding input, output, and fault memory regions are divided according to the start and end offset addresses. The offset addresses of all board channels should be strictly arranged according to the configuration of the I / O board driver information. The offset addresses of all board channels should not overlap, and the offset addresses corresponding to empty channels should also be reserved to ensure that the memory space divided according to the input point table or output point table strictly corresponds to the sorting of the input board or output board driver information.

[0015] Optionally, the generation rules for the fault tree in the fault point table include: generating it according to the topology of control station -> chassis -> IO board -> channel, with upstream node failure triggering a chain of fault responses in downstream nodes.

[0016] Secondly, this application provides a computer device, including: a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the non-security-level DCS IO board virtualization method described above.

[0017] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the aforementioned non-security-level DCS IO board virtualization method.

[0018] Fourthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the aforementioned non-security-level DCS IO board virtualization method.

[0019] According to the specific embodiments provided in this application, the following technical effects are disclosed:

[0020] This application provides a method and related apparatus for virtualizing I / O boards in a non-security-grade DCS. The method includes: parsing the configuration file of the project and extracting the input point table, output point table, and fault point table of the basic control layer based on the input / output functions implemented by the real I / O boards; during virtualization, loading the input point table, output point table, and fault point table into a virtual basic control layer relational dynamic library, initializing the virtual DCS system, and allocating a contiguous space in shared memory according to the type of each point table; storing the fault association relationships between different levels of nodes under the control station in the fault point table in the form of a fault tree. Subsequently, a virtual control station and virtual I / O boards are generated based on the fault point table, and different functions of the real I / O boards are simulated to realize the virtualization of the I / O boards; specifically, the virtualization simulation functions include controlling the interaction of engineering value data between various virtual I / O boards under the virtual control station according to the input point table and output point table, and performing fault association responses according to the fault point table. This application analyzes the virtualized working scenario of I / O boards, enabling the I / O boards to interact with nodes in other layers only by exchanging engineering value data. This reduces the process of converting electrical values ​​to engineering values ​​and then back to electrical values, simplifying data conversion steps, optimizing data transmission, and improving data transmission accuracy. By storing the mapping relationship between the channels of the virtual I / O boards and shared memory through input point tables and output point tables, the communication efficiency between the virtual I / O boards and the virtual field device layer (L0) and monitoring and operation layer (L2) is improved. In addition, by constructing a fault tree consistent with the real DCS topology, during fault simulation, upstream faults can cause downstream related cascading fault responses, realizing the cascading triggering of faults in the virtual basic control layer (L1). Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating a non-security-grade DCS I / O board virtualization method provided in one embodiment of this application.

[0023] Figure 2 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0025] A nuclear power plant simulator is a device used to simulate the operation, systems, and equipment of a nuclear power plant. Like a real nuclear power system, from an instrumentation and control perspective, a simulator can be divided into three layers: the field equipment layer (L0), the basic control layer (L1), and the monitoring and operation layer (L2). The simulation of the field equipment layer in a nuclear power plant simulator is achieved through a process model of the field equipment layer. This model does not have actual field equipment; instead, it simulates the process inputs and outputs of the field equipment using engineering values. The simulation of the basic control layer (L1) and the monitoring and operation layer (L2) is achieved through safety-grade or non-safety-grade virtual DCS software. The basic control layer (L1) of a non-safety-grade DCS system, also known as the control station, consists of control cabinets, network cabinets, and power cabinets. The control cabinets contain controllers and I / O boards. The controllers are mainly responsible for logic operations and algorithm execution, while the I / O boards are mainly responsible for connecting the field physical devices of the field equipment layer (L0) to the controllers, realizing input and output functions and other functions.

[0026] However, many functions of the IO boards in non-security-grade DCS are hardware-related. During the virtualization process, these functions need to be analyzed, and unsuitable functions should be cut off or simplified, while functions that affect the system's process logic or user experience should be retained as much as possible.

[0027] The functions of a real I / O board can be categorized as follows: initialization mode function, normal operation mode function, watchdog function, power-down storage function, bus communication, redundancy, self-diagnosis, message consistency, polling, etc., device configuration function, hardware slot acquisition function, chassis address acquisition function, firmware code download function, self-diagnosis function, channel acquisition function, channel output function, etc.

[0028] The virtual I / O boards of non-security-grade DCS are mainly used for data communication with non-security DCS and for simulating faults in the boards themselves during simulator training. Based on the above scenarios, we can conclude that:

[0029] Retain normal operation mode function, device configuration function, channel acquisition function and channel output function; integrate channel acquisition function and channel output function into input and output function; modify initialization mode function into initialization state function, modify power-off storage function and self-diagnosis function into fault simulation function; remove watchdog function, bus function, hardware slot acquisition function, chassis address acquisition function and firmware code download function.

[0030] Among the functions to be retained and modified, the normal working mode and the initial state can be simulated using the "Run" and "Reset Initial Conditions" commands in the simulator's teaching and control commands. That is, when the simulator is in the running state, the virtual I / O board simulates the normal working mode of the real board and can realize all the functions to be retained and modified of the I / O board. When the simulator receives the "Reset Initial Conditions" command, the virtual I / O board reads the data retained in the initial conditions and clears the cached data to ensure that the data sent to the simulation controller from the first cycle after running is the data in the initial conditions and not the old data in the cache.

[0031] The input / output and fault simulation functions of a virtual I / O board are related and are implemented as a unified whole during the virtualization process of the I / O board, which is also the core function of board virtualization. The purpose of this application is to provide a solution to achieve batch data communication and high-precision fault simulation of a virtual I / O board, thereby reducing the dependence on DCS hardware.

[0032] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0033] This application provides a method for virtualizing I / O boards in a non-security-grade DCS. In one exemplary embodiment, such as... Figure 1 As shown, it includes the following steps:

[0034] A1. By analyzing the project's configuration files and based on the input / output functions implemented by the actual I / O boards, the input point table, output point table, and fault point table of the basic control layer are extracted. The subsequent virtual DCS system will then use the information from these three tables to virtualize the I / O board's input / output functions and fault simulation functions.

[0035] The basic control layer is used to interact with the field device layer and the monitoring and operation layer. The IO boards in the real DCS collect data from the field device layer (L0), which needs to convert electrical values ​​of 4~20mA or 0~5V, 0~10V range into engineering values ​​such as temperature, altitude, and flow rate detected by the sensors of the field devices, and then participate in the control logic operation. Part of the data is converted back into electrical values ​​and returned to the field device layer (L0), while the other part is transmitted to the monitoring and operation layer (L2).

[0036] By virtualizing the I / O boards, the virtual input boards directly interface with the simulator's process model, no longer acquiring electrical signals from the actual field equipment layer. The values ​​acquired by the virtual input boards are the simulator's engineering values. Similarly, the data output by the virtual output boards is no longer sent to the actual field equipment layer (L0), but rather to the virtual field equipment layer on the simulator, i.e., the field equipment layer's process model. Therefore, the virtual I / O boards can optimize the acquisition, conversion, and transmission of field equipment data, reducing the conversion process of electrical value input -> engineering value input -> logic operation -> engineering value output -> electrical value output. The entire process uses engineering values ​​for data transmission and logic operations, reducing data conversion time and resource consumption. Furthermore, because engineering values ​​are directly transmitted, accuracy loss is avoided, significantly improving the accuracy of simulator debugging.

[0037] Data interaction between the virtual I / O board and the process model at the field device level is achieved through network communication. For a large-scale virtual DCS system, the efficiency requirements for communication between the virtual I / O board and the process model at the field device level are very high, needing to reach hundreds of thousands of points per 50ms. To address this, the virtual I / O board optimizes the communication method of the real I / O board, abandoning point-to-point communication and instead merging all points of the same type through input and output point tables, achieving this through a whole-area copy of the memory region.

[0038] Specifically, the configuration file of the project is the core technical carrier for the design, implementation, and operation and maintenance of non-safety-level DCS. The configuration file defines the full lifecycle functional configurations, including control logic, human-machine interface, and communication rules. Each control station corresponds to one configuration file, and the arrangement order of the I / O boards within each control station is independent. Each virtual control station in the virtual DCS uses the same basic control layer configuration file as the real DCS, implements the same logical control as the real DCS, and communicates with the process model at the field equipment level.

[0039] Data communication between the virtual I / O boards and the field device layer process model is achieved through a communication point table. To obtain the overall communication point table information for the virtual DCS system, the configuration files of individual control stations need to be parsed first to generate individual control station communication point tables. Then, all individual control station communication point tables are merged according to their corresponding order to generate the overall communication point table. The communication point tables are divided into input point tables and output point tables according to type. Specifically, by parsing the configuration of the driver information of each control station's input or output boards, the number and arrangement order of input and output boards within the control station, the arrangement order of variables for each channel, and the data type of each channel are obtained. This information can meet the basic communication requirements with the field device layer process model. However, to facilitate project implementation and reduce the difficulty of point-to-point communication with the field device layer process model, some engineering information needs to be added to the communication point table. For example, the board type, variable description, and upper and lower limits for each channel can be obtained by parsing the engineering configuration files.

[0040] The fault point table is used to store the fault relationships between nodes at different levels under the control station in the form of a fault tree. After the virtual I / O board communicates with the process model of the field equipment layer, the fault simulation function of the I / O board also needs to be implemented. The fault simulation function of the virtual I / O board is implemented by parsing the fault point table of the basic control layer. The fault point table of the basic control layer records the correspondence between the virtual control station and the virtual I / O board channel. The generation rules of the fault point table of the basic control layer are similar to those of the input point table and output point table of the basic control layer, except that a subordinate relationship of controller -> cage -> board -> channel is added. It is a table that reflects all faults of the virtual DCS basic control layer (L1) and is obtained by merging the fault point tables of all individual stations.

[0041] The process of extracting key functional information from the I / O boards is performed offline in the configuration software on the engineering workstation. Since the input, output, and fault functions of the DCS boards require the system to be online, the technical solution incorporates an action where the virtual DCS system loads the extracted three types of point tables upon startup, loading all relevant information into the virtual basic control layer relational dynamic library. This dynamic library stores the mapping relationship between all board-related input, output, and fault variables and the subsequently generated shared memory.

[0042] A2. Load the input point table, output point table, and fault point table into the virtual basic control layer relational dynamic library, and initialize the virtual DCS system. Allocate a contiguous space in shared memory according to the type of each point table. The virtual basic control layer relational dynamic library is used to store the mapping relationship between each point table and each contiguous space in shared memory.

[0043] In step A2, a contiguous space is allocated in shared memory according to the type of each point table. Specifically, the memory is divided into three whole blocks: input, output, and fault, based on the start and end offset addresses. The offset addresses of all board channels must strictly follow the configuration of the I / O board's driver information. Offset addresses of all board channels must not overlap, and offset addresses for empty channels must be reserved to ensure that the memory space allocated according to the input or output point table strictly corresponds to the order of the input or output board's driver information. Furthermore, this distribution method corresponds one-to-one with the offset address allocation in the three point tables and is completely consistent with the driver distribution of the I / O boards in the project configuration. The advantage of this is that the distribution of shared memory from the project file to the created virtual I / O board variables is completely consistent. Data communication can be achieved through direct whole-block copying, eliminating the need for point-to-point matching and copying between data, greatly improving communication efficiency.

[0044] A3. Generate a virtual control station and virtual I / O boards based on the fault point table, and simulate the different functions of the real I / O boards according to the input point table, output point table, and fault point table to realize the virtualization of the I / O boards. The virtual control station includes several virtual I / O boards. The virtual I / O boards are divided into virtual input boards and virtual output boards. The virtual input boards are used to obtain data from the corresponding nodes through the virtual gateway according to the input point table; the virtual output boards are used to transmit data to the corresponding nodes through the virtual gateway according to the output point table.

[0045] The simulation functions include input / output and fault simulation. The input / output function involves data interaction between various virtual I / O boards under the virtual control station based on input and output point tables. Data interaction refers to data transmission between each virtual I / O board and the virtual field device layer and virtual monitoring / operation layer via a virtual gateway. The virtual gateway responds to the operation commands of the process model in the field device layer, periodically performing data input and output operations. Data input from the process model in the field device layer updates the shared memory of the virtual gateway according to the input interface call method of the process model in the field device layer. The data acquisition area of ​​the simulation controller acquires the latest input data according to the logical operation cycle. After logical operations, part of the input data is sent to the monitoring and operation layer (L2) for display or further calculation, while the other part is written to the shared memory of the virtual gateway through the driver of the output board. The process model in the field device layer then acquires the latest output data in the shared memory according to its own data acquisition cycle. Compared with real I / O boards, the data transmitted between the virtual I / O boards and the virtual field device layer and virtual monitoring / operation layer is in the form of engineering values.

[0046] In another exemplary embodiment of this application, when the virtual DCS system is running, the virtual I / O board starts to interact with the process model of the field equipment layer according to the running cycle of the simulation controller. Each virtual I / O board transmits data according to the mapping relationship saved when the system starts. The virtual input board collects the data in the entire shared memory to the input terminal of the simulation controller in the virtual control station, and the virtual output board writes the data calculated and output by the simulation controller to a specified location in the shared memory.

[0047] The fault simulation function performs fault correlation response based on the fault point table. The fault correlation response involves the virtual gateway changing the variable values ​​of the faulty node in shared memory when any node fails, and setting fault flags for the corresponding nodes downstream of the faulty node according to the fault correlation relationships in the fault point table. The fault tree generation rules in the fault point table include: generating it according to the topology of control station -> chassis -> I / O board -> channel, with a fault in an upstream node triggering a cascading fault response in downstream nodes.

[0048] Specifically, the fault simulation function of the virtual I / O board is also controlled by the process model at the field equipment layer. Upon receiving a fault command, the virtual gateway changes the variable values ​​of the relevant fault points in memory according to the mapping relationship between the fault point table of the basic control layer in the dynamic library and the shared memory. At the same time, it sets the relevant nodes as faults according to the fault tree formed by the virtual DCS topology. Under this virtual I / O board fault simulation scheme, a single fault initiated in the process model at the field equipment layer will cause a chain of related fault responses in the system, resulting in a high degree of simulation that is closer to the fault response of a real DCS.

[0049] In summary, this embodiment provides a method for virtualizing I / O boards in a non-safety-grade DCS. By analyzing the virtualization working scenario of the I / O boards, the virtualization process enables the I / O boards to interact with nodes in other layers only by exchanging engineering value data. This reduces the process of converting electrical values ​​to engineering values ​​and then back to electrical values, simplifying the data conversion steps, optimizing the data transmission process, and improving the accuracy of data transmission. By storing the mapping relationship between the channels of the virtual I / O boards and shared memory through input point tables and output point tables, the communication efficiency between the virtual I / O boards and the virtual field device layer (L0) and monitoring and operation layer (L2) is improved. In addition, by constructing a fault tree consistent with the real DCS topology, during fault simulation, upstream faults can trigger downstream related cascading fault responses, realizing the cascading triggering of faults in the virtual basic control layer (L1). By parsing the engineering configuration file, the input / output logic and fault simulation mechanism of the virtual I / O boards are reconstructed, achieving a lightweight virtual replacement of the physical I / O board functions. This method is suitable for testing, debugging, and low-cost deployment scenarios of industrial control systems.

[0050] In one exemplary embodiment, a computer device is provided, which may be a server or a terminal, and its internal structure diagram may be as follows. Figure 2 As shown, the computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it can implement the non-security-grade DCS I / O board virtualization method provided in the previous embodiment.

[0051] Those skilled in the art will understand that Figure 2 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0052] In one exemplary embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0053] In one exemplary embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0054] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0055] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0056] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

[0057] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0058] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0059] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for IO board card virtualization of a non-safety level DCS, characterized in that, The application relates to a DCS (Distributed Control System) virtualization method and device. The method comprises the following steps: The basic control layer is used for interaction with the field device layer and the monitoring operation layer; The fault point table is used for storing the fault correlation relationship between different hierarchical nodes under the control station in the form of a fault tree, and the generation rule of the fault tree in the fault point table comprises: generating according to the topology of the control station -> the cage -> the IO board card -> the channel, and the chain fault response of the downstream node is triggered by the upstream node fault; The input point table, the output point table and the fault point table are loaded into a virtual basic control layer relationship dynamic library, and the virtual DCS system is initialized; each point table is allocated a continuous space in the shared memory according to the type of the point table; the virtual basic control layer relationship dynamic library is used for storing the mapping relationship between each point table and each continuous space in the shared memory; each point table is allocated a continuous space in the shared memory according to the type of the point table, specifically: the corresponding input, output and fault three whole memory areas are divided according to the beginning and end offset addresses, and the offset addresses of all the board card channels should be strictly arranged according to the configuration of the driving information of the IO board card; the offset addresses of all the board card channels cannot be overlapped, and the offset addresses corresponding to the empty channels also need to be reserved, so as to ensure that the memory space divided according to the input point table or the output point table corresponds to the sorting of the input board card or the output board card driving information strictly; The virtual control station and the virtual IO board card are generated according to the fault point table, and different functions of the real IO board card are simulated according to the input point table, the output point table and the fault point table, so as to realize the virtualization of the IO board card; the virtual control station comprises a plurality of virtual IO board cards; the simulated functions comprise input and output functions and fault simulation functions; the input and output functions are used for data interaction of each virtual IO board card under the control of the virtual control station according to the input point table and the output point table; the fault simulation function is used for fault correlation response according to the fault point table; the data interaction refers to that each virtual IO board card transmits data with the virtual field device layer and the virtual monitoring operation layer through a virtual gateway; the data form transmitted by the virtual IO board card, the virtual field device layer and the virtual monitoring operation layer is an engineering value; when any node fails, the virtual gateway changes the variable value of the failed node in the shared memory, and sets the fault of the corresponding node in the downstream hierarchical node according to the fault correlation relationship in the fault point table.

2. The method of claim 1, wherein the IO card virtualization of the non-safety- related DCS is performed by a virtualization server. The virtual IO board card is divided into a virtual input board card and a virtual output board card; the virtual input board card is used for acquiring the data of the corresponding node through the virtual gateway according to the input point table; and the virtual output board card is used for transmitting the data to the corresponding node through the virtual gateway according to the output point table.

3. The method of claim 1, wherein the IO card virtualization of non-safety DCS is performed by a virtualization server. Before generating the virtual control station and the virtual IO board card according to the fault point table, the method further comprises: analyzing the functions of the real IO board card of the non-safety level DCS, retaining normal working mode functions, device configuration functions, channel acquisition functions and channel output functions; integrating the channel acquisition functions and the channel output functions into input and output functions; transforming initialization mode functions into initialization state functions, and transforming power-off storage functions and self-diagnosis functions into fault simulation functions; removing watchdog functions, bus functions, hardware slot acquisition functions, case address acquisition functions and firmware code download functions.

4. The method of claim 1, wherein the IO card virtualization of non-safety- critical DCS is performed by a virtualization server. The configuration file of the project is a core technical carrier for design, implementation and operation and maintenance of the non-safety level DCS, and the configuration file defines functional configurations such as control logic, human-computer interface and communication rules in the whole life cycle; each control station corresponds to a configuration file, and the arrangement orders of the IO board cards in each control station are independent of each other.

5. The method of claim 4, wherein the IO card virtualization of non-safety DCS is performed by a virtualization server. The configuration file of a single control station is parsed to generate a single control station communication point table, and all single control station communication point tables are combined according to corresponding arrangement orders to generate a total communication point table; the communication point table is divided into an input point table and an output point table according to types; specifically, the number, arrangement order, arrangement order of each channel variable and data type of each channel of the input board card and the output board card in the control station are obtained by parsing the configuration of the drive information of the input board card or the output board card of each control station. The board card type, variable description and upper and lower limits of each channel are also obtained by parsing the configuration file of the project.

6. A computer device comprising: A memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the IO board card virtualization method of the non-safety level DCS according to any one of claims 1-5.

7. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the IO board card virtualization method of the non-safety level DCS according to any one of claims 1-5.

8. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the IO board card virtualization method of the non-safety level DCS according to any one of claims 1-5.

Images