IO (input / output) board card virtualization method of non-security-level DCS (distributed control system) and related device

Abstract

The invention discloses an IO board card virtualization method of a non-security-level DCS and a related device, and relates to the technical field of industrial automation control, and the method comprises the steps: analyzing a configuration file of a project, and carrying out the extraction of an input point table, an output point table and a fault point table of a basic control layer according to the input and output functions of a real IO board card; during virtualization, an input point table, an output point table and a fault point table are loaded into a virtual basic control layer relation dynamic library, a virtual DCS system is initialized, and a section of continuous space is distributed in a shared memory according to the type of each point table; and storing the fault association relationship between different hierarchy nodes under the control station in the fault point table in the form of a fault tree. And then generating a virtual control station and a virtual IO board card according to the fault point table, and realizing virtualization of the IO board card. According to the method and the device, batch data communication and high-precision fault simulation of the virtual IO board cards are realized, and DCS hardware dependence is reduced.

Description

Technical Field

[0001] The present application relates to the field of industrial automation control technology, and in particular to an IO board virtualization method and related devices for a non-safety-level DCS. Background Art

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

[0003] Existing common IO board virtualization technology also has obvious defects: it only focuses on input and output signal simulation, fails to fully realize core functions such as parameter configuration and fault-safe output; fails to effectively solve the compatibility issues between virtual IO boards and physical IO boards at the configuration file level; and lacks the ability to dynamically adapt to the DCS field control layer engineering structure. Summary of the Invention

[0004] The purpose of this application is to provide an IO board virtualization method and related devices for non-safety-level DCS, which can realize batch data communication and high-precision fault simulation of virtual IO boards and reduce the DCS hardware dependence.

[0005] To achieve the above objectives, this application provides the following solutions: In a first aspect, the present application provides a method for virtualizing an IO board of a non-safety-level DCS, comprising the following steps: By parsing the project configuration file 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 nodes at different levels under the control station in the form of a fault tree.

[0006] 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. A continuous space is allocated to each point table in the shared memory according to its type. The virtual basic control layer relational dynamic library is used to store the mapping relationship between each point table and each continuous space in the shared memory.

[0007] A virtual control station and virtual IO board are generated according to the fault point table, and the different functions of the real IO board are simulated according to the input point table, output point table and fault point table to realize the virtualization of the IO board; the virtual control station includes several virtual IO boards; the simulation functions include input and output functions and fault simulation functions; the input and output functions are to control the data interaction of each virtual IO board under the virtual control station according to the input point table and output point table; the fault simulation function is to perform fault correlation response according to the fault point table; data interaction refers to the data transmission between each virtual IO board and the virtual field device layer and the virtual monitoring operation layer respectively through the virtual gateway; the data transmitted between the virtual IO board and the virtual field device layer and the virtual monitoring operation layer is in the form of engineering values; the fault correlation response is that when a fault occurs at any node, the virtual gateway changes the variable value of the faulty node in the shared memory, and sets the fault position of the corresponding node in the downstream layer of the faulty node according to the fault correlation relationship in the fault point table.

[0008] Optionally, the virtual IO board is divided into a virtual input board and a virtual output board. The virtual input board is used to obtain data of 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.

[0009] Optionally, before generating a virtual control station and a virtual IO board according to the fault point table, the method further includes: analyzing the functions of the real IO board of the non-safety-level DCS, retaining the normal working mode function, device configuration function, channel acquisition function and channel output function; integrating the channel acquisition function and the channel output function into input and output functions; transforming the initialization mode function into the initialization state function, and transforming the power-off storage function and the self-diagnosis function into the fault simulation function; and removing the watchdog function, bus function, hardware slot acquisition function, chassis address acquisition function and firmware code download function.

[0010] Optionally, the project configuration file is the core technical carrier for the design, implementation, and operation of non-safety-level DCS. The configuration file defines the full life cycle functional configuration 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.

[0011] Optionally, the configuration file of a single control station is parsed first to generate a single control station communication point table, and then all the single control station communication point tables are merged according to the corresponding arrangement order 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 type; specifically, by parsing the configuration of the drive information of the input board or output board of each control station, the number of input boards and output boards in the control station, the arrangement order, the arrangement order of each channel variable 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.

[0012] Optionally, a continuous space is allocated in the shared memory according to the type of each point table, specifically: the corresponding input, output and fault three whole memory areas are divided according to the start and end offset addresses, and the offset addresses of all board channels should be strictly arranged according to the configuration of the drive information of the IO board. The offset addresses of all board channels cannot overlap, and the offset addresses corresponding to empty channels also need to 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 drive information.

[0013] Optionally, the generation rule of the fault tree in the fault point table includes: generating according to the topology structure of control station->cage->IO board->channel, and an upstream node failure triggering a cascading failure response of a downstream node.

[0014] In a second aspect, the present application provides a computer device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the IO board virtualization method for the non-safety-level DCS described above.

[0015] In a third aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the IO board virtualization method for a non-safety-level DCS as described above.

[0016] In a fourth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the IO board virtualization method for a non-safety-level DCS as described above.

[0017] According to the specific embodiments provided in this application, this application discloses the following technical effects: The present application provides a method and related device for virtualizing IO boards for non-safety-level DCS. The method includes: extracting the input point table, output point table, and fault point table of the basic control layer based on the input and output functions implemented by the real IO board by parsing the configuration file of the project; loading the input point table, output point table, and fault point table into the virtual basic control layer relationship dynamic library during virtualization, initializing the virtual DCS system, and allocating a continuous space in the shared memory according to the type of each point table; storing the fault association relationship between nodes at different levels under the control station in the form of a fault tree in the fault point table. Subsequently, a virtual control station and virtual IO board are generated based on the fault point table, and the different functions of the real IO board are simulated to realize the virtualization of the IO board; specifically, the functions of the virtualization simulation include controlling the interaction of engineering value data of each virtual IO board under the virtual control station based on the input point table and output point table, and responding to fault associations based on the fault point table. By analyzing the virtualization working scenario of the IO board, this application enables only engineering value data to be exchanged between the IO board and nodes of other layers during virtualization, thereby reducing the process of converting electrical values ​​into engineering values ​​and then converting them back into 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 IO board and the shared memory through the input point table and the output point table, the communication efficiency between the virtual IO board and the virtual field device layer (L0) and the monitoring and operation layer (L2) is improved. In addition, by constructing a fault tree consistent with the real DCS topology structure, during fault simulation, upstream faults can cause downstream related chain fault responses, thereby realizing chain triggering of faults in the virtual basic control layer (L1). BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 This is a flowchart of a method for virtualizing an IO board of a non-safety-level DCS provided in one embodiment of the present application.

[0020] Figure 2 A schematic diagram of the structure of a computer device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0022] A nuclear power simulator is a device that simulates the operation, systems, and equipment of a nuclear power plant. Like a real nuclear power system, the simulator is divided into the field equipment layer (L0), the basic control layer (L1), and the monitoring and operation layer (L2) from an instrumentation and control perspective. The field equipment layer simulation of the nuclear power simulator is achieved through the field equipment layer process model. This means that the simulator does not have actual field equipment, but rather simulates the field equipment process using engineering values ​​for input and output. Simulation of the basic control layer (L1) and the monitoring and operation layer (L2) is achieved using safety-level or non-safety-level virtual DCS software. The basic control layer (L1) of a non-safety-level DCS system, also known as the control station, consists of a control cabinet, a network cabinet, and a power cabinet. The control cabinet contains controllers and I / O boards. The controllers are primarily responsible for logical operations and algorithm execution, while the I / O boards connect the physical field equipment in the field equipment layer (L0) to the controllers, implementing input and output functions and other functions.

[0023] However, many functions of the IO boards in non-safety-level DCS are related to hardware. During the virtualization process, these functions must be analyzed, and inapplicable functions must be trimmed or simplified. Functions that affect the system process logic or user experience must be retained as much as possible.

[0024] The functions of real IO boards are divided into the following categories: initialization mode function, normal working mode function, watchdog function, power-off storage function, bus communication, redundancy, self-diagnosis, message consistency, polling and other functions, device configuration function, hardware slot collection function, chassis address collection function, firmware code download function, self-diagnosis function, channel collection function, channel output function, etc.

[0025] The virtual IO card of the non-safety-level DCS is mainly used for data communication of the non-safety DCS and fault simulation of the card itself during simulator training. Combining the above scenarios, we can see that: The normal working mode function, device configuration function, channel acquisition function and channel output function are retained; the channel acquisition function and channel output function are integrated into the input and output function; the initialization mode function is transformed into the initialization state function, and the power-off storage function and self-diagnosis function are transformed into the fault simulation function; the watchdog function, bus function, hardware slot acquisition function, chassis address acquisition function and firmware code download function are removed.

[0026] Among the functions of retention and transformation, the normal working mode and initial state can be simulated through the two teaching and control commands of the simulator, namely "run" and "reset initial conditions". That is, when the simulator is in the running state, the virtual IO board simulates the normal working mode of the real board and can realize all the retention and transformation functions of the IO board; when the "reset initial conditions" command of the simulator is received, the virtual IO 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 rather than the old data in the cache.

[0027] The input and output functions and fault simulation functions of virtual IO boards are closely related and are implemented as a whole during the IO board virtualization process. This is also the core function of board virtualization. The purpose of this application is to implement a solution to achieve batch data communication and high-precision fault simulation for virtual IO boards, thereby reducing DCS hardware dependence.

[0028] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0029] The embodiment of the present application provides a method for virtualizing an IO board of a non-safety-level DCS. In an exemplary embodiment, Figure 1 As shown, the following steps are included: A1. By parsing the project configuration file and extracting the input point table, output point table, and fault point table of the basic control layer based on the input and output functions implemented by the actual IO board, the virtual DCS system will then virtualize the IO board's input and output functions and fault simulation functions based on the information in these three point tables.

[0030] The basic control layer is used to interact with the field device layer and the monitoring operation layer. The IO board in the real DCS collects data from the field device layer (L0). It needs to convert electrical values ​​in the range of 4~20mA or 0~5V, 0~10V, etc. into engineering values ​​such as temperature, height, flow, etc. detected by the sensors of the field equipment. Then, it participates in the control logic operation. A part of it is converted into electrical values ​​again and returned to the field device layer (L0), and the other part is transmitted to the monitoring operation layer (L2).

[0031] By virtualizing the IO boards, the virtual input boards connect directly to the simulator's process model, no longer collecting electrical signals from the actual field device layer. Instead, the values ​​collected by the virtual input boards are the simulator's engineering value data. The data output by the virtual output boards is no longer sent to the actual field device layer (L0), but instead to the virtual field device layer on the simulator, namely the field device layer process model. Therefore, the virtual IO boards optimize the process of collecting, converting, and transmitting field device data, reducing the conversion process from electrical value input to engineering value input to logical operations to engineering value output to electrical value output. Engineering values ​​are used throughout the data transmission and logical operations, reducing data conversion time and resource consumption. Furthermore, the direct transmission of engineering values ​​avoids precision loss, significantly improving the accuracy of simulator debugging.

[0032] Data exchange between the virtual IO board and the field device-level process model is achieved through network communication. For a large-scale virtual DCS system, communication efficiency between the virtual IO board and the field device-level process model must be very high, requiring hundreds of thousands of points per 50ms. To this end, the virtual IO board optimizes the communication method of the real IO board. Instead of point-to-point communication, all points of the same type are merged using input and output point tables, and then copied to the entire memory area.

[0033] Specifically, the project's configuration file is the core technical vehicle for the design, implementation, and operation of a non-safety-level DCS. The configuration file defines the full lifecycle functional configuration, including control logic, human-machine interface, and communication rules. Each control station corresponds to a configuration file, and the order of the I / O boards within each control station is independent of each other. Each virtual control station in the virtual DCS uses the same basic control layer configuration file as a real DCS, implementing the same logical control as a real DCS and communicating data with the field device-level process model.

[0034] Data communication between the virtual IO board and the field device layer process model is achieved through the communication point table. In order to obtain the communication point table information of the entire virtual DCS system, it is necessary to first parse the configuration file of the single control station to generate a single control station communication point table, and then merge all the single control station communication point tables according to the 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 drive information of the input board or output board of each control station, the number of input boards and output boards in the control station, the arrangement order, the arrangement order of each channel variable 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, in order to facilitate project implementation and reduce the difficulty of point matching of the field device layer process model, it is necessary to add some project information to the communication point table, such as obtaining the board type, variable description and upper and lower limits of each channel by parsing the project configuration file.

[0035] The fault point table is used to store fault associations between nodes at different levels of the control station in the form of a fault tree. After the virtual IO board communicates with the field device layer process model, the IO board's fault simulation function must be implemented. This virtual IO board fault simulation function is achieved by parsing the fault point table of the basic control layer. The basic control layer's fault point table records the correspondence between virtual control stations and virtual IO board channels. The generation rules for the basic control layer's fault point table are similar to those of the basic control layer's input and output point tables, differing in that the subordinate relationship of controller -> cage -> board -> channel is added. This table represents all faults in the virtual DCS basic control layer (L1) and is derived by merging the fault point tables of all single stations.

[0036] Extracting information about key I / O board functions occurs offline in the configuration software of the engineering station. The input, output, and fault functions of DCS boards all require the system to be online. Therefore, the technical solution includes a virtual DCS system that loads the three extracted point tables at startup, loading all relevant information into a dynamic library within the virtual basic control layer. This dynamic library stores the mapping between all board-related input, output, and fault variables and the subsequently generated shared memory.

[0037] A2. Load the input point table, output point table, and fault point table into the virtual basic control layer relational dynamic library, initialize the virtual DCS system, and allocate a continuous space in the shared memory for each point table based on its type. The virtual basic control layer relational dynamic library is used to store the mapping relationship between each point table and each continuous space in the shared memory.

[0038] In step A2, a continuous space is allocated in the shared memory based on the type of each point table. Specifically, the three corresponding input, output, and fault memory areas are divided according to the starting and ending offset addresses. The offset addresses of all board channels should be strictly arranged according to the configuration of the driver information of the IO board. The offset addresses of all board channels cannot overlap, and the offset addresses corresponding to empty channels also need to be reserved to ensure that the memory space divided according to the input point table or output point table strictly corresponds to the order of the input board or output board driver information. Moreover, 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 IO board in the engineering configuration. This has the advantage that the virtual IO board variables and shared memory distribution created from the project file are completely consistent. Data communication can adopt the method of direct whole-chip copy, without the need for point-to-point matching and copying between data, greatly improving communication efficiency.

[0039] A3. Generate a virtual control station and virtual I / O boards based on the fault point table. Simulate the various functions of real I / O boards based on the input point table, output point table, and fault point table to virtualize the I / O boards. The virtual control station includes several virtual I / O boards. These virtual I / O boards are divided into virtual input boards and virtual output boards. Virtual input boards are used to obtain data from corresponding nodes through the virtual gateway based on the input point table. Virtual output boards are used to transmit data to corresponding nodes through the virtual gateway based on the output point table.

[0040] The simulation functions include input / output and fault simulation. The input / output function controls the data exchange between the virtual I / O boards in the virtual control station according to the input and output point tables. Data exchange involves each virtual I / O board transmitting data to the virtual field device layer and the virtual monitoring and operation layer through a virtual gateway. The virtual gateway responds to operational commands from the field device layer's process model and periodically performs data input and output. Data input from the field device layer's process model updates the virtual gateway's shared memory by calling its input interface. The simulation controller's data acquisition area acquires the latest input data according to the logic operation cycle. After logical operation, a portion of the input data is sent to the monitoring and operation layer (L2) for display or further calculation, while the remaining portion is written to the virtual gateway's shared memory through the output board's driver. The field device layer's process model then acquires the latest output data from the shared memory according to its own data acquisition cycle. Compared to real I / O boards, the data transmitted between the virtual field device layer and the virtual monitoring and operation layer is in the form of engineering values.

[0041] In another exemplary embodiment of the present application, when the virtual DCS system is running, the virtual IO board starts to interact with the field device layer process model according to the operation cycle of the simulation controller. Each virtual IO board transmits data according to the mapping relationship saved when the system starts. The virtual input board collects data in the entire shared memory to the input end of the simulation controller in the virtual control station, and the virtual output board writes the data calculated and output in the simulation controller to the specified location of the shared memory.

[0042] The fault simulation function performs fault correlation responses based on the fault point table. When a fault occurs at any node, the virtual gateway changes the variable values ​​of the failed node in shared memory and, based on the fault correlation relationships in the fault point table, sets faults for the corresponding nodes downstream of the failed node. The fault tree generation rules in the fault point table follow the topology of control station -> cage -> I / O card -> channel, with upstream node failures triggering cascading fault responses at downstream nodes.

[0043] Specifically, the virtual IO board's fault simulation function is also controlled by the field device layer process model. 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. Simultaneously, according to the fault tree formed by the virtual DCS topology, the relevant nodes are set to fault. With this virtual IO board fault simulation solution, a single fault initiated in the field device layer process model will cause a fault response that cascades through related faults in the system, resulting in a high degree of simulation and closer to the fault response of a real DCS.

[0044] In summary, this embodiment provides a method for virtualizing IO boards for non-safety-level DCSs. By analyzing the virtualization scenarios of IO boards, this method allows only engineering value data to be exchanged between the IO board and nodes in other layers during virtualization. This reduces the need to convert electrical values ​​to engineering values ​​and then back to electrical values, simplifies data conversion steps, optimizes the data transmission process, and improves data transmission accuracy. By storing the mapping relationship between the virtual IO board's channels and shared memory in input and output point tables, the communication efficiency between the virtual IO board and the virtual field device layer (L0) and the monitoring and operation layer (L2) is improved. Furthermore, by constructing a fault tree consistent with the real DCS topology, upstream faults can trigger related cascading fault responses downstream during fault simulation, achieving cascading fault triggering in the virtual basic control layer (L1). By parsing engineering configuration files, reconstructing the input and output logic and fault simulation mechanism of the virtual IO board, this method achieves a lightweight virtual replacement for physical IO board functions, suitable for testing, debugging, and low-cost deployment scenarios of industrial control systems.

[0045] In an exemplary embodiment, a computer device is provided. The computer device may be a server or a terminal. The internal structure diagram thereof may be as follows: Figure 2 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it can implement an IO board virtualization method for a non-safety-level DCS provided in the previous embodiment.

[0046] Those skilled in the art will understand that Figure 2 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0047] In an exemplary embodiment, a computer device is further provided, including a memory and a processor. The memory stores a computer program, and the processor implements the steps in the above method embodiments when executing the computer program.

[0048] In an exemplary embodiment, a computer-readable storage medium is provided, storing a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0049] In an exemplary embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0050] 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, stored data, displayed data, 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 relevant data must comply with relevant regulations.

[0051] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the above-mentioned embodiments. In particular, any reference to memory, database, 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 may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0052] The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may include, but are not limited to, general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic units, data processing logic units based on quantum computing, and the like.

[0053] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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.

[0054] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above examples is only intended to help understand the method and core concept of this application. At the same time, for those skilled in the art, based on the concept of this application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A method for virtualizing an IO board of a non-safety-level DCS, characterized in that: include: By parsing the project configuration file 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 nodes at different levels under the control station in the form of a fault tree; 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. A continuous space is allocated to each point table in the shared memory according to the type of the point table; the virtual basic control layer relationship dynamic library is used to store the mapping relationship between each point table and each continuous space in the shared memory; A virtual control station and a virtual IO board are generated according to the fault point table, and different functions of the real IO board are simulated according to the input point table, the output point table and the fault point table to realize the virtualization of the IO board; the virtual control station includes several virtual IO boards; the simulation functions include input and output functions and fault simulation functions; the input and output functions are to control the various virtual IO boards under the virtual control station to perform data interaction according to the input point table and the output point table; the fault simulation function is to perform fault association response according to the fault point table; the data interaction refers to the data transmission between each virtual IO board and the virtual field device layer and the virtual monitoring operation layer respectively through the virtual gateway; the data transmitted between the virtual IO board and the virtual field device layer and the virtual monitoring operation layer is in the form of engineering values; the fault association response is that when a fault occurs at any node, the virtual gateway changes the variable value of the faulty node in the shared memory, and sets the fault position of the corresponding node in the downstream layer of the faulty node according to the fault association relationship in the fault point table.

2. The IO board virtualization method for non-safety-level DCS according to claim 1, characterized in that: The virtual IO board is divided into a virtual input board and a virtual output board. The virtual input board is used to obtain data of 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.

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

4. The IO board virtualization method for non-safety-level DCS according to claim 1, characterized in that: The configuration file of the project is the core technical carrier for the design, implementation and operation of non-safety-level DCS. The configuration file defines the functional configuration of 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.

5. The IO board virtualization method for non-safety-level DCS according to claim 4, characterized in that: First, the configuration file of a single control station is parsed to generate a single control station communication point table. Then, all the single control station communication point tables are merged according to the corresponding arrangement order 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 type. Specifically, by parsing the configuration of the driver information of the input board or output board of each control station, the number and arrangement order of the input boards and output boards in the control station, the arrangement order of each channel variable, 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 project configuration file.

6. The IO board virtualization method for non-safety-level DCS according to claim 5, characterized in that: According to the type of each point table, a continuous space is allocated to each in the shared memory. Specifically, the corresponding input, output and fault memory areas are divided according to the start and end offset addresses, and the offset addresses of all board channels should be strictly arranged according to the configuration of the IO board drive information. The offset addresses of all board channels cannot overlap, and the offset addresses corresponding to empty channels also need to 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 drive information.

7. The IO board virtualization method for non-safety-level DCS according to claim 1, characterized in that: The generation rules of the fault tree in the fault point table include: generating according to the topology structure of control station->cage->IO board->channel, and the upstream node failure triggering the chain failure response of the downstream node.

8. A computer device comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the IO board virtualization method for a non-safety-level DCS according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for virtualizing an IO board of a non-safety-level DCS according to any one of claims 1 to 7 is implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method for virtualizing an IO board of a non-safety-level DCS according to any one of claims 1 to 7 is implemented.

Images