A nuclear power plant equipment drive control priority management system and method

Abstract

The application provides a nuclear power plant equipment driving control priority management system and method, and relates to the technical field of nuclear engineering technology.The nuclear power plant equipment driving control priority management system comprises an equipment driving module, a table configuration module and the like.The equipment driving module is used for obtaining equipment driving instructions generated after logical operation of each instrument control subsystem, and performing attribute configuration on the equipment driving instructions to obtain driving instruction blocks.The table configuration module is used for generating equipment driving signal connection tables corresponding to the equipment driving instructions according to attribute information of each actuator corresponding to the driving instruction blocks.The equipment driving signal connection tables comprise the codes of the actuators and the names of process systems corresponding to the actuators.The priority management system and method provided by the application can clearly display the priority relationship of driving instructions of different instrument control subsystems / platforms on a logic diagram, and realize the automatic matching function and management of actuators and driving signals.

Description

A priority management system and method for drive control of nuclear power plant equipment Technical Field

[0001] This invention relates to the field of nuclear engineering technology, and in particular to a priority management system and method for drive control of nuclear power plant equipment. Background Technology

[0002] In the current nuclear power plant control logic design process, the priority expression of equipment drive commands mainly relies on separate specification documents and agreements with DCS suppliers regarding the priority command relationships for different platforms, and is achieved by identifying the relevant instrumentation and control subsystems in the IO list. When the control logic of the actuator in each instrumentation and control subsystem expresses the corresponding control function in the IO list: PS (RPS system code): Signals related to the RPS system are filled with "YES" (i.e., signals need to be sent to the PS during acquisition; when signals need to be sent to multiple subsystems simultaneously, the supplier must implement signal isolation and allocation according to relevant principles), otherwise filled with "NO". KDS (DAS system code): Signals related to the DAS system are filled with "YES" (i.e., signals need to be sent to the KDS during acquisition; when signals need to be sent to multiple subsystems simultaneously, the supplier must implement signal isolation and allocation according to relevant principles), otherwise filled with "NO". DEC: DEC 2-hour control cabinet and DEC... For signals related to the 12-hour control cabinet, fill in A-2h, B-2h, 12h, or NO according to the actual situation. PSAS / SAS: If the signal is collected by PSAS / SAS, fill in "YES" in this column; otherwise, fill in "NO". If the signal is distributed to PSAS / SAS through the Functional Safety Level 1 platform, fill in "YES" in this column. If the signal is only used by the Functional Safety Level 1 platform, fill in "NO" in this column.

[0003] For an actuator, priority management of different control commands from various instrumentation and control subsystems is completed in the Equipment Interface Module (CIM). Located at the end of the safety-grade DCS platform, the CIM primarily receives control commands at different functional levels from the Safety Dedicated Facility Actuation System (ESFAS), Safety Automation System (SAS), Diversified Actuation System (DAS), Severe Accident Instrumentation and Control System (SA I&C), and Power Plant Standard Automation System (PSAS). It implements priority management of these control commands and drives pumps, valves, and other equipment in dedicated safety facilities and related support systems through priority logic processing within the CIM. The ESFAS is part of the Reactor Protection System (RPS), which includes the Reactor Emergency Shutdown System (RTS) and the Dedicated Safety Facility Actuation System (ESFAS).

[0004] When it's necessary to understand which instrumentation and control subsystems the actuator receives, it's not clearly visible from the actuator's control logic diagrams; the information can only be gleaned from the I / O list, and even then, only the relevant instrumentation and control subsystems are apparent. Regarding the specific control functions of each instrumentation and control subsystem, since neither the actuator's control logic diagrams nor the I / O list express this, it's necessary to individually query the detailed control logic files of each subsystem to determine the control functions of each subsystem for the same actuator. Furthermore, the control logic diagrams for the same actuator don't clearly show the commands driven by multiple platforms or the priority relationships between these commands. When configuration and commissioning personnel, as well as subsequent nuclear power plant owners and maintenance personnel, need to understand the complete control functions of the actuator, they must manually sift through the design documents of each instrumentation and control subsystem, manually establishing relationships between multiple documents. This manual process is not only inefficient and lacks accuracy, but errors can directly impact the safe operation of the nuclear power plant. Summary of the Invention

[0005] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a nuclear power plant equipment drive control priority management system and method to solve the problem that in the design of nuclear power plant control logic, the priority expression of equipment drive instructions currently mainly relies on separate specification documents and DCS suppliers to agree on the priority instruction relationship of different platforms; and the control logic diagram fails to clearly express the equipment drive instructions of different safety level platforms and the relationship between the equipment.

[0006] To achieve the above and other related objectives, this invention provides a nuclear power plant equipment drive control priority management system, comprising: an equipment drive module, used to acquire equipment drive instructions generated after logical operations of each instrumentation and control subsystem, and to configure the attributes of the equipment drive instructions to obtain drive instruction blocks; a table configuration module, used to generate an equipment drive signal connection table corresponding to each actuator according to the drive instruction block and the attribute information of each actuator corresponding to the equipment drive instruction; wherein, the equipment drive signal connection table includes the actuator code and the name of the process system corresponding to the actuator; an equipment instruction optimization module, deployed in the logical interface of each actuator, used to filter all data of the same actuator from all equipment drive signal connection tables according to the actuator code as preliminary screening data, and sort the preliminary screening data according to the platform priority of the instrumentation and control subsystem corresponding to the drive instruction to generate an equipment instruction optimization table; and a signal synchronization module, deployed in the logical interface of each actuator, used to control the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each equipment drive instruction in the equipment instruction optimization table.

[0007] In one embodiment of the present invention, the device driving module includes: an instruction acquisition module, used to acquire device driving instructions generated after logical operations of each instrumentation and control subsystem; a first creation module, used to create a driving instruction function block according to the device driving instructions; and a first generation module, used to write the signal encoding and functional description of the device driving instructions into the driving instruction function block to generate the driving instruction block.

[0008] In one embodiment of the present invention, the table configuration module includes: a second creation module for creating a device drive signal connection table function block; a second association module for establishing an association between the device drive signal connection table function block and the device drive instruction; and a second generation module for writing the action command and column corresponding to each actuator into the device drive signal connection table function block after establishing the association, thereby generating a device drive signal connection table corresponding to the device drive instruction.

[0009] In one embodiment of the present invention, during the process of creating a device drive signal connection table function block and establishing an association with a device drive instruction, the signal encoding and functional description of the device drive instruction are written into the device drive signal connection table function block. After the writing is completed, the output connection number corresponding to each actuator is generated in the device drive signal connection table to establish the association.

[0010] In one embodiment of the present invention, the equipment instruction selection module is further configured to write back the page number information of the actuator of each equipment drive instruction in the process system to the equipment drive signal connection table.

[0011] In one embodiment of the present invention, the device instruction selection module is further configured to fill the page number information of the device drive signal connection table in the instrumentation and control subsystem of each device drive instruction in the device instruction selection table into the device instruction selection table.

[0012] In one embodiment of the present invention, the device instruction selection module includes: a third creation module for creating a device instruction selection table function block; a filtering module for filtering all data of the same actuator from all device drive signal connection tables according to the actuator's code to obtain preliminary screening data; a priority configuration module for configuring the platform priority of the instrumentation and control subsystem corresponding to each device drive instruction in the preliminary screening data according to priority rules; and a third generation module for placing the preliminary screening data into the device instruction selection table function block according to the platform priority of the instrumentation and control subsystem corresponding to each device drive instruction to generate a device instruction selection table.

[0013] In one embodiment of the present invention, during the process of placing the initial screening data into the device instruction preference table function block to generate the device instruction preference table, the order in which the row numbers of the initial screening data are placed into the device instruction preference table function block is consistent with the order of the platform priority of the device driving instruction corresponding to the row number selection.

[0014] In one embodiment of the present invention, the device instruction selection module further includes: a modification module, used to modify the information content of the device instruction selection table according to the instrumentation and control subsystem information of each actuator; and an annotation module, used to add a remark module to the device instruction selection table, and configure supplementary annotation information for the device instruction selection table in the remark module.

[0015] In one embodiment of the present invention, the signal synchronization module includes: a fourth creation module for creating a signal synchronization function block; a writing module for writing the signal synchronization function block into the logic interface of the actuator; and a fourth association module for synchronizing the device drive instruction corresponding to the device instruction preference table into the signal synchronization function block to establish a signal association with the device instruction preference table.

[0016] To achieve the above and other related objectives, the present invention also provides a method for priority management of nuclear power plant equipment drive control, comprising the following steps: obtaining equipment drive instructions generated after logical operations of each instrumentation and control subsystem through an equipment drive module, and configuring the attributes of the equipment drive instructions to obtain drive instruction blocks; generating an equipment drive signal connection table corresponding to the equipment drive instructions through a table configuration module based on the attribute information of each actuator corresponding to the drive instruction blocks and equipment drive instructions; wherein, the equipment drive signal connection table includes the code of the actuator and the name of the process system corresponding to the actuator; using an equipment instruction optimization module deployed in the logical interface of each actuator to filter all data of the same actuator from all equipment drive signal connection tables according to the actuator code as preliminary screening data, and sorting the preliminary screening data according to the platform priority of the instrumentation and control subsystem corresponding to the drive instructions to generate an equipment instruction optimization table; and using a signal synchronization module deployed in the logical interface of each actuator to control the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each equipment drive instruction in the equipment instruction optimization table.

[0017] As described above, the nuclear power plant equipment drive control priority management system and method of the present invention have the following beneficial effects: By establishing an association between the equipment drive module and the table configuration module during the design of the control logic diagram, and establishing an association between the table configuration module and the equipment instruction selection module, and by implementing platform priority management and control through the signal synchronization module, the priority relationship of equipment drive instructions between different instrumentation and control subsystems / platforms and actuators can be clearly displayed. This avoids errors caused by manual multi-platform design document review, effectively improves design quality, and ensures the safe operation of the nuclear power plant. By activating the data of functional modules and establishing data associations between modules, the inheritance and dynamic updating of equipment drive instructions and actuator-related attributes can be realized. This not only avoids errors caused by untimely manual updates but also significantly improves design efficiency and ensures the safe operation of the nuclear power plant. Moreover, by activating the data of functional modules and setting filtering conditions based on the characteristics of actuators and equipment drive instructions, automatic matching of actuators and drive signals can be achieved. This not only avoids errors caused by manual matching but also significantly improves design efficiency and ensures the safe operation of the nuclear power plant. Attached Figure Description

[0018] Figure 1 shows a structural block diagram of a priority management system provided in an embodiment of the present invention.

[0019] Figures 2 and 3 show schematic diagrams of the display interface for the driver instruction block configuration process provided in an embodiment of the present invention.

[0020] Figure 4 shows a schematic diagram of a driver instruction block provided in an embodiment of the present invention.

[0021] Figures 5 to 8 show schematic diagrams of the display interface for creating a device drive signal connection table according to an embodiment of the present invention.

[0022] Figure 9 shows a schematic diagram of a device drive signal connection table provided in an embodiment of the present invention.

[0023] Figures 10 to 16 show schematic diagrams of the display interface of a preferred table for creating device instructions provided in an embodiment of the present invention.

[0024] Figures 17 and 18 show schematic diagrams of the display interface for modifying the device instruction preference table according to an embodiment of the present invention.

[0025] Figures 19 and 20 show schematic diagrams of the display interface for supplementing annotation information to the preferred device instruction table according to an embodiment of the present invention.

[0026] Figures 21 to 23 show schematic diagrams of the display interface for the creation process of a signal synchronization function block provided in an embodiment of the present invention.

[0027] Component designation explanation

[0028] Device driver module 10; table configuration module 20; device instruction optimization module 30; signal synchronization module 40. Detailed Implementation

[0029] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be noted that, unless otherwise specified, the following embodiments and features described therein can be combined with each other.

[0030] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0031] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0032] Table of Abbreviations and Key Terms Definitions:

[0033] Abbreviations English Name Chinese Name CIM Component Interface Module DAS Diverse Actuation System DBC Design Basis Condition DEC Design Extension Condition ESFASE Engineered Safety Feature Actuation System I&CI Instrument & Control PSASPlant Standard Automation System RPS Reactor Protection System SASevere Accident SASSafety Automation System surface

[0034] The structure of a nuclear power plant's instrumentation and control system includes four independent defense layers:

[0035] Layer 1 - Prevention Line: PSAS (Power Plant Standard Automation System) is used to detect and correct transient events or system failures that deviate from the normal operation of the power plant, preventing the events from developing into accidents.

[0036] Layer 2 - Main Defense Line: RPS (Reactor Protection System) + SAS (Safety Automation System). The main defense line is used to activate accident mitigation measures to mitigate the consequences of DBC (Design Basis Condition) type 2-4 accidents to avoid serious accidents and radioactive material leaks. RPS implements all safety functions (Functional Safety Category 1) from accident occurrence to a controllable state. SAS implements safety functions from a controllable state to a safe shutdown state, as well as other Functional Safety Category 2 functions. Regarding type 2-4 accidents: based on the assumed frequency of the initiating event, the plant state can be divided into four Design Basis Conditions (DBC) and two Design Extension Conditions (DEC). DBC conditions, based on their frequency (f) per reactor year (y), can be divided into: a) DBC-1: Normal operation and normal operation transients (f > 1 / ry); b) DBC-2: Expected operating events (medium frequency events, 10 -2 / ry≤f<1 / ry); c)DBC-3: Rare Incident 10 -4 / ry≤f<10 -2 / ry); d)DBC-4: Extreme Accident (10 -6 / ry≤f<10 -4 / ry).

[0037] Layer 3 - Diversity Defense Line: DAS (Diversity Driven System). The diversity defense line is mainly used to bring the reactor to a safe state under conditions where a common-cause failure of the protection system software is superimposed on a design basis accident. The protection system software mainly refers to the software in the DCS system. The RPS cabinet is a safety-grade DCS, and the safety-grade DCS system has dedicated software.

[0038] 4-Layer - Severe Accident Defense Line: SA (Severe Accident) I&C (Instrumentation and Control) (Operating Condition Instrumentation and Control System). SA I&C can mitigate the consequences of a meltdown accident caused by a severe accident under conditions of complete power loss, providing necessary monitoring and control functions to ensure that the established safety objectives are not breached.

[0039] Based on the required functions, performance, classification, and independence requirements of the instrumentation and control system, the design allocates the necessary logic processing functions to different instrumentation and control subsystems. During the subsystem design phase, this functional allocation needs further refinement, distributing different functions among multiple controllers and input / output modules, as follows:

[0040] a) Functional safety Category 1 functions are assigned to the reactor protection system (RPS);

[0041] b) Functional safety Category 2 functions are assigned to the Safety Automation System (SAS);

[0042] c) Assign relevant functional safety Category 3 and non-safety functions to the power plant standard automation system (PSAS);

[0043] d) The functional safety Category 3 functions required to address the design baseline incidents caused by the combined failure of RPS and SAS are allocated to the diversity drive system (DAS);

[0044] e) Functional safety Category 3 functions required to address DEC (Design Extended Condition)-A and DEC-B conditions caused by mechanical system failures are assigned to the Extended Condition Instrumentation and Control System (SA I&C).

[0045] A single actuator may receive multiple equipment drive commands with different functions depending on the requirements of different operating conditions. Since different instrumentation and control systems perform different functions, they may simultaneously issue opposite control commands to the same actuator. Therefore, priority rules need to be established for these commands to determine the control command that the actuator should execute. The actuator can refer to various types of pumps, valves, and fans; the control of these actuators can be either opening or closing.

[0046] Priority is determined based on: a) the functional safety classification of the instrumentation and control system; b) the type of command, such as equipment protection, automatic, manual, etc.

[0047] Priority table of control signals:

[0048] Instrumentation and Control Subsystem Priority Protection System (EDG Unloading) 0RPS1DAS2SAS3SA I&C4PSAS5 surface

[0049] As shown in the table, based on functional importance, when different instrumentation and control systems such as RPS and DAS control the same actuator, the priority levels of the control signals, from high to low, are 0, 1, 2, 3, 4, and 5, respectively.

[0050] Please refer to Figure 1. In one embodiment of the present invention, the present invention provides a nuclear power plant equipment drive control priority management system, including: an equipment drive module 10, used to acquire equipment drive instructions generated after logical operations of each instrumentation and control subsystem, and to configure the attributes of the equipment drive instructions to obtain drive instruction blocks; a table configuration module 20, used to generate an equipment drive signal connection table corresponding to the equipment drive instructions based on the attribute information of each actuator corresponding to the drive instruction blocks and the equipment drive instructions; wherein, the equipment drive signal connection table includes the code of the actuator and the name of the process system corresponding to the actuator; an equipment instruction optimization module 30, deployed in the logical interface of each actuator, used to filter all data of the same actuator from all equipment drive signal connection tables according to the code of the actuator as preliminary screening data, and sort the preliminary screening data according to the platform priority of the instrumentation and control subsystem corresponding to the drive instructions to generate an equipment instruction optimization table; and a signal synchronization module 40, deployed in the logical interface of each actuator, used to control the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each equipment drive instruction in the equipment instruction optimization table.

[0051] In this embodiment, the device drive instructions in the device drive module 10 are generated by logical operations performed by each instrumentation and control subsystem. These logical operations are primarily for fulfilling the control requirements of the process discipline, implementing logic according to the functional requirements. For example, when performing containment isolation operations, multiple isolation valves may be opened or closed simultaneously. Therefore, the corresponding process discipline control requirements can be formed based on the logic of opening or closing multiple isolation valves, and these control requirements correspond to the device drive instructions. After obtaining the generated device drive instructions, attribute configuration, such as instruction content description, is performed on the device drive instructions to obtain a drive instruction block corresponding to the device drive instruction. The table configuration module 20 is used to generate a device drive signal connection table based on the obtained drive instruction block, corresponding to the same device drive instruction. The device drive signal connection table also contains attribute information for each actuator corresponding to the device drive instruction, such as the actuator code and process system. Consequently, the generated device drive signal connection table will also contain the corresponding actuator code, process system, and other information. The equipment instruction selection module 30 is deployed in the logical interface of each actuator. It can filter all data of the same actuator from all equipment drive signal connection tables based on the code of each actuator and generate an equipment instruction selection table. This data includes the actuator's code, signal code, functional description, process system, and other information. After obtaining the equipment instruction selection table, it is necessary to further configure the platform priority of the instrumentation and control subsystem corresponding to each equipment drive instruction of the actuator according to the priority relationship. For example, the instrumentation and control subsystem includes RPS (Reactor Protection System), DAS (Diversity Drive System), SAS (Safety Automation System), SAI&C (Extended Operating Condition Instrumentation and Control System), and PSAS (Power Plant Standard Automation System), and set the priority levels from 1 to 5 in descending order. The signal synchronization module 40 is also deployed in the logical interface of each actuator. When the signal synchronization module 40 issues equipment drive instructions to control the corresponding actuator, it controls the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each equipment drive instruction in the equipment instruction selection table.

[0052] The priority management system of this invention enables data activation of functional modules, establishes data associations between modules, and realizes the inheritance and dynamic updating of equipment drive commands and actuator-related attributes. This not only avoids errors caused by untimely manual updates but also significantly improves design efficiency and ensures the safe operation of nuclear power plants. Furthermore, it clearly displays the platform priority relationship of equipment drive commands between different instrumentation and control subsystems / platforms and actuators on the control logic interface diagram of the actuators, avoiding errors caused by manual multi-platform design document analysis, effectively improving design quality, and ensuring the safe operation of nuclear power plants. At the same time, by setting filtering conditions based on the characteristics of actuators and equipment drive commands, it achieves automatic matching of actuators and drive signals, which not only avoids errors caused by untimely manual updates but also significantly improves design efficiency and ensures the safe operation of nuclear power plants.

[0053] In one embodiment of the present invention, the device driver module 10 includes: an instruction acquisition module, used to acquire device driver instructions generated after logical operations of each instrumentation and control subsystem; a first creation module, used to create a driver instruction function block according to the device driver instructions; and a first generation module, used to write the signal encoding and functional description of the device driver instructions into the driver instruction function block to generate the driver instruction block. In this embodiment, during the generation of the driver instruction block, the device driver module 10 first needs to create a driver instruction function block according to the device driver instructions, and after the driver instruction function block is created, it adds the signal encoding and functional description of the device driver instructions to the driver instruction function block to generate the driver instruction block.

[0054] Please refer to Figures 2 and 3. During the generation of the drive instruction block, for example, first locate the drive instruction (ACTUATOR_LINK) function block in the library of the logic interface of the actuator in the RPS / DAS and other instrumentation control subsystems, and drag and drop it into the drawing area. Then, select the ACTUATOR_LINK function block and modify the signal encoding and function description in the properties dialog box.

[0055] Please refer to Figure 4. The arrows indicate the direction of the signals output by each instrumentation and control subsystem after logical operations. The "0128" in the box represents the signal code of the device drive command, and "RCPB isolated resettable" below the box represents the functional description of the device drive command.

[0056] In one embodiment of the present invention, the table configuration module 20 includes: a second creation module for creating a device drive signal connection table function block; a second association module for establishing an association between the device drive signal connection table function block and the device drive instruction; and a second generation module for, after establishing the association, writing the action command and column type corresponding to each actuator into the device drive signal connection table function block to generate a device drive signal connection table corresponding to the device drive instruction. In this embodiment, when the table configuration module 20 establishes an association with the device drive module 10, it first creates a device drive signal connection table function block, and then establishes an association between the device drive signal connection table function block and the device drive instruction, thereby enabling the writing of the signal code and function description corresponding to the device drive instruction into the device drive signal connection table function block. Then, by configuring the attribute information of the device drive signal connection table function block, such as writing the action command and column type into the device drive signal connection table function block, a device drive signal connection table corresponding to the device drive instruction is generated to display the signal code, function description, actuator code, process system, and other information corresponding to each device drive instruction.

[0057] In one embodiment of the present invention, during the process of creating a device drive signal connection table function block and establishing an association with the device drive instruction, the signal code and functional description of the device drive instruction are written into the device drive signal connection table function block. After writing is completed, an output connection number corresponding to each actuator is generated in the device drive signal connection table to establish an association. In this embodiment, the attribute information includes the signal code, functional description, actuator code, process system, output connection number, and other information corresponding to each device drive instruction. After the signal code and functional description of the device drive instruction are written into the device drive signal connection table function block, an output connection number is generated in the device drive signal connection table function block. Typically, this output connection number can use the same number as the signal code. Furthermore, after the output connection number is generated, it is determined that an association has been established.

[0058] The equipment instruction selection module 30 is also used to write back the page number information of the actuators of each equipment drive instruction in the process system to the equipment drive signal connection table. The equipment instruction selection module 30 is also used to fill in the page number information of the equipment drive signal connection table of each equipment drive instruction in the instrumentation and control subsystem into the equipment instruction selection table.

[0059] In this embodiment, after generating the preferred equipment instruction table based on the equipment drive signal connection table, the page number information of the actuator in the process system corresponding to each equipment drive instruction in the preferred equipment instruction table is written back to the preferred equipment drive signal connection table. Simultaneously, the page number information of each equipment drive instruction in the preferred equipment instruction table in the instrumentation and control subsystem's equipment drive signal connection table is also filled into the preferred equipment instruction table accordingly. This allows for querying the corresponding page number in the instrumentation and control subsystem's equipment drive signal connection table when viewing the corresponding actuator in the preferred equipment instruction table. Similarly, when viewing a specific actuator in the preferred equipment drive signal connection table, the page number information displayed in the preferred equipment drive signal connection table can be used to query the corresponding page number of the actuator in the process system.

[0060] Please refer to Figures 5 through 8. During the creation of the device drive signal connection table, in Figure 5, locate the Device Drive Signal Connection Table (ACTUATOR_TABLE) function block in the library and drag and drop it to the drawing area. In Figures 6 and 7, select the ACTUATOR_TABLE function block, right-click to display a signal list for device drive commands, and double-click the row containing the signal to associate it. A signal code corresponding to the "Connection Number" will be generated in the "Output Connection Number" field of the table. The signal list includes the connection number / signal code and a function description. In Figure 8, select the ACTUATOR_TABLE function block and modify the action command, system (process system of the actuator), device (code of the actuator), and column in the properties dialog box. If multiple signals need to be associated, you can add signal rows to the ACTUATOR_TABLE function block by modifying the row number in the properties.

[0061] Please refer to Figure 9. The device drive signal connection table of this invention mainly includes connection number (signal code), signal description (functional description), action command, system (process system of the actuator), device (code of the actuator), column, page number, and output connection number. The output connection number corresponds one-to-one with the connection number. The output connection number is generated synchronously after each actuator writes the connection number (signal code) and signal description (functional description) of the device drive instruction into the table. The page number is the page number corresponding to the logical interface of each actuator in the process system corresponding to the device instruction preference table after the device drive signal connection table is associated with the device instruction preference table.

[0062] In one embodiment of the present invention, the device instruction selection module 30 includes: a third creation module for creating a device instruction selection table function block; a filtering module for filtering all data of the same actuator from all the device drive signal connection tables according to the actuator's code to obtain preliminary screening data; a priority configuration module for configuring the platform priority of the instrumentation and control subsystem corresponding to each device drive instruction in the preliminary screening data according to priority rules; and a third generation module for placing the preliminary screening data into the device instruction selection table function block according to the platform priority of the instrumentation and control subsystem corresponding to each device drive instruction to generate the device instruction selection table. In this embodiment, during the generation of the device instruction selection table, the device instruction selection module 30 first creates a device instruction selection table function block, and obtains preliminary screening data by filtering all data of the same actuator from all the device drive signal connection tables according to the actuator's code. Further, the preliminary screening data is then placed into the device instruction selection table function block according to the corresponding row number of the signal list to generate the device instruction selection table.

[0063] In one embodiment of the present invention, during the process of placing the preliminary screening data into the device instruction preference table function block to generate the device instruction preference table, the order in which the row numbers of the preliminary screening data are placed into the device instruction preference table function block is consistent with the order of the platform priority of the device driving instruction corresponding to the row number selection. In this embodiment, when establishing an association between the preliminary screening data obtained from the device driving signal connection table and the device instruction preference table function block, the preliminary screening data needs to be written into the device instruction preference table function block, that is, by selecting the corresponding signal rows one by one and placing them into the device instruction preference table function block. Furthermore, when placing the preliminary screening data, according to the row number of the signal row corresponding to each device driving instruction, it is also necessary to ensure that the order in which the row numbers of each device driving instruction are selected is consistent with the order of the platform priority of the device driving instruction corresponding to the row number selection.

[0064] Please refer to Figures 10 to 16. During the creation of the device instruction preference table, as shown in Figure 10, locate the device instruction preference table (PRIO_TABLE) function block in the function block library, drag and drop it to the corresponding area of ​​the drawing, and then save the drawing. Click to select the dragged-and-drop PRIO_TABLE function block, as shown in Figure 11. As shown in Figure 12, right-click the PRIO_TABLE function block to bring up the following page link, where you can select the attributes of the associated signals; typically, select "Function Description". As shown in Figure 13, enter the device code (the code of the actuator) in the text box, and then click Filter to display the preferred signals that meet the conditions for that device. As shown in Figure 14, first select the row in the preference module where the signal will be placed using the row number in the upper right corner, and then double-click the row containing the signal to associate it. All signals in the list need to be added to the preference table. It is recommended to select the row numbers in ascending order of signal priority, from highest to lowest. If the signal is added successfully, "Link successful" will be displayed; if it has already been linked, "This data has been linked" will be displayed. After adding and closing the interface shown in Figure 14, the table shown in Figure 15 will be generated. As shown in Figure 16, clicking the PRIO_TABLE function block with the added signal again opens the module's property window, allowing modification and supplementation of the information in the device instruction preference table.

[0065] In one embodiment of the present invention, the device instruction selection module 30 further includes: a modification module, used to modify the information content of the device instruction selection table according to the instrumentation and control subsystem information of each actuator; and an annotation module, used to add a note module to the device instruction selection table, wherein the note module is configured with supplementary annotation information for the device instruction selection table. In this embodiment, after obtaining the device instruction selection table, the information content in the device instruction selection table can be modified, and supplementary annotation information can also be added to the information content in the device instruction selection table.

[0066] Please refer to Figure 17. Function block codes can be modified to device codes, and row numbers in the device instruction preference table can be modified. For example, according to the management requirements of the SAS or PSAS platform, if the device is implemented on the SAS or PSAS platform, the row number is the number of preferred signals plus one. Each priority level is modified and set by the instrumentation and control subsystem. Further, as shown in the figure, in the attribute information related to priority level 2, for devices implemented on the SAS or PSAS platform, the signal description value priority needs to be manually filled in; the signal description, connection number, and page number should be filled in as NA, the system should be filled in as a three-letter code plus "*", the action command should be filled in according to the control requirements, and the priority should be filled in according to the instrumentation and control subsystem. After filling in, the device instruction preference table corresponding to the actuator code as shown in Figure 18 is generated. The device instruction preference table includes signal description, connection number, system (instrumentation and control subsystem), page number, action command, and priority. The page number in the device instruction preference table is the corresponding page number from the logical interface of the device drive signal connection table in the instrumentation and control subsystem after the device instruction preference table and the device drive signal connection table are linked.

[0067] Please refer to Figure 19. When adding annotation information to the device instruction preference table, locate the Note module (NOTE) in the annotation class module list of the function block window and drag and drop it near the preference table. Double-click the NOTE module, for example, and enter "Comment * for SAS" to annotate the symbol "*" in the preference table, as shown in Figure 20.

[0068] In one embodiment of the present invention, the signal synchronization module 40 includes: a fourth creation module for creating a signal synchronization function block; a writing module for writing the signal synchronization function block into the logic interface of the actuator; and a fourth association module for synchronizing the device driver instruction corresponding to the device instruction preference table into the signal synchronization function block to establish a signal association with the device instruction preference table. In this embodiment, when synchronizing the device driver instruction corresponding to the device instruction preference table into the signal synchronization module 40, it is also necessary to first create a signal synchronization function block, place the signal synchronization function block into the logic interface of the actuator, and then synchronize the device driver instruction corresponding to the device instruction preference table into the signal synchronization function block to establish a signal association.

[0069] Referring to Figure 21, for the execution signals of the actuators in the equipment instruction preference table, such as electrical unloading signals and RPS control signals, the synchronization logic also needs to be represented in the drawing. Therefore, locate the Signal Synchronization (UD_DO_Link_INTERNAL) function block in the function block library and drag and drop it to the drawing area; select the UD_DO_Link_INTERNAL function block, then right-click on it to bring up the interface shown in Figure 22. Double-click the required signal to associate it with the equipment instruction preference table. Finally, the synchronization logic represented by the UD_DO_Link_INTERNAL function block in the drawing is shown in Figure 23.

[0070] In one embodiment of the present invention, the signal synchronization module 40 is further configured to select the corresponding device drive instructions to control the actuator in descending order of platform priority of the instrumentation and control subsystems corresponding to each device drive instruction in the device instruction preference table. In this embodiment, when controlling the actuator, the signal synchronization module 40 selects the corresponding device drive instructions to control the actuator in descending order of platform priority of the instrumentation and control subsystems corresponding to each device drive instruction in the device instruction preference table. Simultaneously, device drive instructions with lower platform priority are suppressed until the device drive instruction of the previous priority is executed, after which the device drive instruction with lower platform priority is executed.

[0071] In one embodiment of the present invention, the present invention also provides a method for priority management of nuclear power plant equipment drive control, comprising the following steps:

[0072] Step S10: Obtain the device driver instructions generated after logical operations of each instrumentation and control subsystem through the device driver module 10, and configure the attributes of the device driver instructions to obtain the driver instruction block;

[0073] Step S20: The table configuration module 20 generates a device drive signal connection table corresponding to the device drive instruction based on the attribute information of each actuator corresponding to the drive instruction block and the device drive instruction; wherein, the device drive signal connection table includes the code of the actuator and the name of the process system corresponding to the actuator;

[0074] Step S30: Using the device instruction selection module 30 deployed in the logical interface of each actuator, all data of the same actuator are selected from all the device drive signal connection tables according to the actuator's code, as preliminary screening data. The preliminary screening data is then sorted according to the platform priority of the instrumentation and control subsystem corresponding to the drive instruction to generate a device instruction selection table; and

[0075] Step S40: The signal synchronization module 40 deployed in the logical interface of each actuator is used to control the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each device drive instruction in the device instruction preference table.

[0076] In summary, the nuclear power plant equipment drive control priority management system and method disclosed in this invention, by establishing an association between the equipment drive module 10 and the table configuration module 20 during the control logic diagram design, and by establishing an association between the table configuration module 20 and the equipment instruction selection module 30, and by implementing platform priority management and control through the signal synchronization module 40, clearly displays the priority relationship of equipment drive instructions among different instrumentation and control subsystems / platforms and actuators. This avoids errors caused by manual multi-platform design document review, effectively improves design quality, and ensures the safe operation of the nuclear power plant. By activating the data of functional modules and establishing data associations between modules, the inheritance and dynamic updating of equipment drive instructions and actuator-related attributes can be achieved. This not only avoids errors caused by untimely manual updates but also significantly improves design efficiency and ensures the safe operation of the nuclear power plant. Furthermore, by activating the data of functional modules and setting filtering conditions based on the characteristics of actuators and equipment drive instructions, automatic matching of actuators and drive signals can be achieved. This not only avoids errors caused by manual matching but also significantly improves design efficiency and ensures the safe operation of the nuclear power plant. Therefore, this invention effectively overcomes the various shortcomings of the prior art and has high industrial application value.

[0077] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A priority management system for drive control of nuclear power plant equipment, characterized in that, include: The device driver module is used to obtain the device driver instructions generated after logical operations of each instrumentation and control subsystem, and to configure the attributes of the device driver instructions to obtain a driver instruction block. A table configuration module is used to generate a device drive signal connection table corresponding to the device drive instruction based on the attribute information of each actuator corresponding to the drive instruction block and the device drive instruction; wherein, the device drive signal connection table includes the actuator code and the name of the process system corresponding to the actuator; a device instruction selection module is deployed in the logical interface of each actuator, used to filter all data of the same actuator from all the device drive signal connection tables according to the actuator code as preliminary screening data, and sort the preliminary screening data according to the platform priority of the instrumentation and control subsystem corresponding to the drive instruction to generate a device instruction selection table; and a signal synchronization module is deployed in the logical interface of each actuator, used to synchronize the device drive signal connection table according to the device instruction. The platform priority relationship between the instrumentation and control subsystems corresponding to each device drive instruction in the preferred list controls the actuator; wherein, the device instruction selection module includes: a third creation module for creating a device instruction selection table function block; a filtering module for filtering all data of the same actuator from all device drive signal connection tables according to the actuator's code to obtain preliminary screening data; a priority configuration module for configuring the platform priority of the instrumentation and control subsystems corresponding to each device drive instruction in the preliminary screening data according to priority rules; and a third generation module for placing the preliminary screening data into the device instruction selection table function block according to the platform priority of the instrumentation and control subsystems corresponding to each device drive instruction to generate the device instruction selection table.

2. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The device driver module includes: an instruction acquisition module, used to acquire device driver instructions generated after logical operations of each instrumentation and control subsystem; a first creation module, used to create a driver instruction function block according to the device driver instructions; and a first generation module, used to write the signal encoding and functional description of the device driver instructions into the driver instruction function block to generate the driver instruction block.

3. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The table configuration module includes: a second creation module for creating a device drive signal connection table function block; a second association module for establishing an association between the device drive signal connection table function block and the device drive instruction; and a second generation module for, after establishing the association, writing the action command and column corresponding to each actuator into the device drive signal connection table function block to generate the device drive signal connection table corresponding to the device drive instruction.

4. The nuclear power plant equipment drive control priority management system according to claim 3, characterized in that: During the process of creating a device drive signal connection table function block and establishing an association with the device drive instruction, the signal encoding and functional description of the device drive instruction are written into the device drive signal connection table function block. After the writing is completed, the output connection number corresponding to each actuator is generated in the device drive signal connection table to establish the association.

5. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The equipment instruction selection module is also used to write the page number information of each equipment drive instruction in the equipment instruction selection table to the execution mechanism of the process system in reverse to the equipment drive signal connection table.

6. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The device instruction selection module is also used to fill the page number information of the device drive signal connection table in the instrumentation and control subsystem into the device instruction selection table for each device drive instruction in the device instruction selection table.

7. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: In the process of placing the initial screening data into the device instruction preference table function block to generate the device instruction preference table, the order in which the row numbers of the initial screening data are placed into the device instruction preference table function block is consistent with the order of the platform priority of the device driving instruction corresponding to the row number selection.

8. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The device instruction selection module further includes: a modification module, used to modify the information content of the device instruction selection table according to the instrumentation and control subsystem information of each actuator; and an annotation module, used to add a note module to the device instruction selection table, and configure supplementary annotation information for the device instruction selection table in the note module.

9. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The signal synchronization module includes: a fourth creation module for creating a signal synchronization function block; a writing module for writing the signal synchronization function block into the logic interface of the actuator; and a fourth association module for synchronizing the device drive instruction corresponding to the device instruction preference table into the signal synchronization function block to establish a signal association with the device instruction preference table.

10. The nuclear power plant equipment drive control priority management system according to claim 1, characterized in that: The signal synchronization module is also used to control the actuator by sequentially selecting the corresponding device drive instruction to execute according to the platform priority relationship between the instrumentation and control subsystems corresponding to each device drive instruction in the device instruction preference table, in descending order of platform priority of the instrumentation and control subsystems.

11. A method for priority management of equipment drive control in a nuclear power plant, characterized in that, The process includes the following steps: First, the device driver module obtains the device driver instructions generated after logical operations of each instrumentation and control subsystem, and configures the attributes of the device driver instructions to obtain a driver instruction block. Second, the table configuration module generates a device driver signal connection table corresponding to the device driver instruction based on the attribute information of each actuator corresponding to the driver instruction block and the device driver instruction. The device driver signal connection table includes the actuator's code and the name of the process system corresponding to the actuator. Third, the device instruction optimization module, deployed in the logical interface of each actuator, filters all data of the same actuator from all the device driver signal connection tables based on the actuator's code as initial screening data, and sorts the initial screening data according to the platform priority of the instrumentation and control subsystem corresponding to the driver instruction to generate a device instruction optimization table. Finally, the process is further described below. A signal synchronization module deployed in the logical interface of each actuator is used to control the actuator according to the platform priority relationship between the instrumentation and control subsystems corresponding to each device drive instruction in the device instruction preference table; wherein, the device instruction preference module includes: a third creation module for creating a device instruction preference table function block; a filtering module for filtering all data of the same actuator from all the device drive signal connection tables according to the actuator's code to obtain preliminary screening data; a priority configuration module for configuring the platform priority of the instrumentation and control subsystems corresponding to each device drive instruction in the preliminary screening data according to priority rules; and a third generation module for placing the preliminary screening data into the device instruction preference table function block according to the platform priority of the instrumentation and control subsystems corresponding to each device drive instruction to generate the device instruction preference table.

Images