DCS two-layer system fault simulation system and method
Through the DCS layer 2 system fault simulation system and methods, software is used to simulate hardware failures, and the problems of damage risk and limited simulation range in the prior art hardware simulation are solved, and more flexible and extensive fault simulation is achieved, which improves the operator's ability to deal with layer 2 failures in DCS system.
Patent Information
- Application Number
- CN202411736823.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-29
- Publication Date
- 2025-03-07
AI Technical Summary
The existing technology simulates DCS layer 2 system failures mainly rely on hardware simulation, and there is a risk of hardware damage and the simulation range is limited, so it is impossible to effectively and quickly respond to DCS system layer 2 failures.
Provide a DCS layer 2 system fault simulation system and method, through components such as failure point determination module, fault value judgment module, fault type determination module, fault processing module, etc., it realizes software simulation of hardware failures, refines fault types and builds a fault database.
Through software simulation of hardware failures, reduce the risk of hardware damage, expand the simulation range, improve the flexibility and adaptability of simulation, and can simulate a variety of faults that cannot be simulated directly using hardware.
Smart Images
Figure CN119583362A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of DCS layer 2 system fault simulation, and in particular, relates to a DCS layer 2 system fault simulation system and method. Background Art
[0002] The DCS layer 2 system (power station computer information and control system) of a nuclear power plant is the central system used by nuclear power plant units to monitor and control the units. It is required to have high reliability, high efficiency and high availability. If a failure occurs, it will not only fail to ensure the safe and stable operation of the unit, but may also cause serious damage to the unit. How to properly handle a failure is a skill that nuclear power plant operators and maintenance personnel must have.
[0003] Nuclear power plant simulator products are important tools for training nuclear power plant operators and managers. However, the existing nuclear power plant simulator products simulate DCS layer 2 system failures through hardware simulation. Hardware simulation has the technical problem of hardware damage, and the scope of hardware simulation is limited. Summary of the invention
[0004] The purpose of the present application is to provide a DCS layer 2 system fault simulation system and method to solve the technical problem that the existing technology simulates the DCS layer 2 system fault hardware, resulting in incomplete simulation of the nuclear power plant simulator and the operator being unable to effectively and quickly respond to the DCS system layer 2 fault.
[0005] In order to achieve the above objectives, this application provides the following technical solutions:
[0006] In a first aspect, the present application provides a DCS layer 2 system fault simulation system, comprising:
[0007] A fault point determination module, used to obtain a fault instruction and determine multiple fault points of the second-layer workstation corresponding to the fault instruction;
[0008] A fault value judgment module is used to determine the fault value of each fault point and judge whether the fault point has changed based on the fault value;
[0009] A fault type determination module is used to determine the fault type of the fault point when the fault point changes;
[0010] A first fault processing module, used for stopping data transmission and reception at the fault point when the fault type of the fault point is a network fault;
[0011] The second fault processing module is used to respond to the human-machine interface fault based on a preset human-machine interface event when the fault type of the fault point is a human-machine interface fault.
[0012] In some embodiments, the fault value determination module includes:
[0013] An original point value acquisition unit, used to acquire the original point value of the fault point;
[0014] The fault judgment unit is used to determine that the fault point has changed when the difference between the original point value and the fault value is greater than a preset difference.
[0015] In some embodiments, the original point value obtaining unit is used to add the original point value to the fault database.
[0016] In some embodiments, the fault types include network faults and human-machine interface faults.
[0017] In some embodiments, the DCS layer 2 system fault simulation system further includes:
[0018] The fault database building module is used to obtain the point number of the fault point and build a fault database based on the point number and the fault value.
[0019] In a second aspect, the present application provides a DCS layer 2 system fault simulation method, comprising:
[0020] S401, determining multiple fault points of the second-layer workstation corresponding to the fault instruction;
[0021] S402, determine the fault value of each fault point, and judge whether the fault point has changed based on the fault value. If it has changed, proceed to step S403; if it has not changed, end the fault simulation process;
[0022] S403, when the fault point changes, determine the fault type of the fault point, when it is determined that the fault type of the fault point is a network fault, proceed to step S404, when it is determined that the fault type of the fault point is a human-machine interface fault, proceed to step S405;
[0023] S404, when the fault type of the fault point is a network fault, stopping data transmission and reception at the fault point;
[0024] S405: When the fault type of the fault point is a human-machine interface fault, respond to the human-machine interface fault based on a preset human-machine interface event.
[0025] In S402, it is determined whether the fault point has changed based on the preset polling process.
[0026] In S404, the local network status is set to unavailable.
[0027] In some embodiments, human-machine interface failures include mouse, keyboard failures, display failures, and touch screen, hard button failures.
[0028] In some embodiments, when the human-machine interface failure is a touch screen or hard button failure, the preset human-machine interface event is:
[0029] Determine whether there is preset event processing logic;
[0030] When there is no preset event processing logic, it does not respond to touch screen and hard button operations;
[0031] When there is a preset event processing logic, the operation of the touch screen and hard buttons is responded to based on the preset event processing logic.
[0032] Compared with the prior art, the DCS layer 2 system fault simulation system and method provided by the present application has the following beneficial effects:
[0033] The present application realizes the simulation of hardware failures through software by setting up multiple failure points of the second-layer workstation corresponding to the failure instructions. This can not only reduce the loss of directly using hardware to simulate failures and reduce the risk of hardware damage, but also can simulate many failures that cannot be simulated directly using hardware, thereby improving the scope of simulation.
[0034] Furthermore, the present application is arranged to determine the fault type of the fault point when the fault point changes, and set the fault type to a network fault and a human-machine interface fault. The fault type can be refined to simulate a single fault. Each fault can be used alone, or more complex faults can be generated through different combinations, thereby improving the flexibility and adaptability of the simulation. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for the technical description.
[0036] Figure 1 A schematic diagram of the structure of the DCS layer 2 system fault simulation system provided for this application;
[0037] Figure 2 A schematic diagram of the structure of the fault value judgment module provided in this application;
[0038] Figure 3 A schematic diagram of the workflow of the DCS layer 2 system fault simulation system provided for this application;
[0039] Figure 4 This is a flow chart of the DCS layer 2 system fault simulation method provided in this application. DETAILED DESCRIPTION
[0040] The following is further explained in detail through specific implementation methods.
[0041] To facilitate understanding, we first briefly describe the DCS Layer 2 system. As a human-computer interaction system that interfaces with operators / maintenance personnel, the DCS Layer 2 system has the functions of manipulation and information management. It includes some interfaces with other networks as well as interfaces with personnel.
[0042] First, as Figures 1 to 3 As shown, the present application provides a DCS layer 2 system fault simulation system 10, comprising:
[0043] A fault point determination module 100 is used to obtain a fault instruction and determine multiple fault points of the second-layer workstation corresponding to the fault instruction;
[0044] A fault value judgment module 200 is used to determine the fault value of each fault point and judge whether the fault point has changed based on the fault value;
[0045] The fault type determination module 300 is used to determine the fault type of the fault point when the fault point changes; the fault type includes network fault and human-machine interface fault;
[0046] The first fault processing module 400 is used to stop data transmission and reception at the fault point when the fault type of the fault point is a network fault;
[0047] The second fault processing module 500 is used to respond to the human-machine interface fault based on a preset human-machine interface event when the fault type of the fault point is a human-machine interface fault.
[0048] It should be understood that a fault instruction can be added to the fault instruction list, or deleted from the fault instruction list, wherein both the addition and deletion are completed through the teaching console.
[0049] Specifically, determining the multiple failure points includes: determining the multiple failure points of the second-layer workstation based on rules and design requirements.
[0050] The stopping of data transmission and reception at the fault point in the first fault processing module 400 specifically includes: setting the local network status to unavailable.
[0051] It should be noted that if there is no fault point corresponding to the fault instruction in the second-layer workstation, it means that the fault instruction is irrelevant to the second-layer workstation. At this time, the fault value judgment module 200, the fault type determination module 300, the first fault processing module 400 and the second fault processing module 500 do not need to work.
[0052] It should be understood that the first fault processing module 400 and the second fault processing module 500 can be functional modules integrated in the training platform in actual application, and the fault of the fault point is processed in the training platform. The training platform also includes a display interface to display the fault of the fault point.
[0053] Compared with the prior art, the present application realizes the simulation of hardware failures through software by setting up multiple fault points of the second-layer workstation corresponding to the fault instructions. This can not only reduce the loss of directly using hardware to simulate failures and reduce the risk of hardware damage, but also can simulate many failures that cannot be simulated directly using hardware, thereby improving the scope of simulation.
[0054] Furthermore, the present application is arranged to determine the fault type of the fault point when the fault point changes, and set the fault type to a network fault and a human-machine interface fault. The fault type can be refined to simulate a single fault. Each fault can be used alone, or more complex faults can be generated through different combinations, thereby improving the flexibility and adaptability of the simulation.
[0055] In some embodiments, Figure 2 As shown, the fault value judgment module 200 includes:
[0056] The original point value acquisition unit 210 is used to acquire the original point value of the fault point;
[0057] The fault judgment unit 220 is used to determine that the fault point has changed when the difference between the original point value and the fault value is greater than a preset difference.
[0058] It should be noted that the preset difference value can be determined according to the type of fault value. For example, if the fault value is based on 0 or 1 to indicate fault or no fault, the preset difference value is 0, that is, when the original point value and the fault value are different, it is determined that the fault point has changed. When the fault value represents the communication rate, although there is a difference between the original point value and the fault value, when the difference value is within the preset range of the communication rate, it is determined that the fault point has not changed. When the difference value is outside the preset range of the communication rate, it is determined that the fault point has changed.
[0059] In order to facilitate subsequent maintenance personnel to trace the fault, in some embodiments of the present application, such as Figure 1 As shown, the DCS layer 2 system fault simulation system 10 also includes a fault database construction module 600, which is used to obtain the point number of the fault point and construct a fault database based on the point number and the fault value. The original point value acquisition unit 210 is also used to: add the original point value to the fault database.
[0060] This application records the fault value, original point value and point number in a fault database, and the data of each fault point can be traced back through the fault database to facilitate subsequent analysis.
[0061] Specifically, the fault database includes at least three columns, which are respectively used to store the point number, the fault value and the original point value.
[0062] Furthermore, the fault database may also include a time column for recording the time when the fault point changes.
[0063] In some actual scenarios, the fault instruction corresponds to multiple fault points. In order to save the network resource overhead of judging whether the multiple fault points have changed, in some embodiments, the specific method of judging whether the fault point has changed in the fault value judgment module 200 is: judging whether the fault point has changed based on the preset polling process polling.
[0064] The present application polls multiple fault points based on a polling process to see whether they have changed, thereby saving network resource overhead and improving the orderliness of determining whether a fault point has changed.
[0065] To further refine the fault types, in some embodiments, human-machine interface faults include mouse, keyboard faults, display faults, touch screen, and hard button faults. This application further refines the fault types by classifying human-machine interface faults into the above three specific faults, further improving the flexibility and adaptability of simulation.
[0066] In some embodiments, when the human-machine interface failure is a mouse or keyboard failure, the preset human-machine interface event is:
[0067] Call back the mouse and keyboard fault simulation functions corresponding to the Human Machine Interface (HMI) program;
[0068] Create a subwindow of preset size in the display window based on the mouse and keyboard failure simulation function;
[0069] Capture mouse and keyboard events based on child windows.
[0070] This application captures mouse and keyboard events through a newly created sub-window, so that all keyboard and mouse operations of the HMI main interface program are captured by the sub-window, and the HMI main interface operations are unresponsive.
[0071] It should be understood that when the human-machine interface fault disappears, the HMI main interface is reset to capture mouse and keyboard events so that the main interface operations respond normally.
[0072] In one embodiment, the sub-window is a window with a length and a width of one pixel.
[0073] In one embodiment, when the human-machine interface failure is a display failure, the preset human-machine interface event is:
[0074] Call back the display panel fault simulation function corresponding to the human-machine interface program;
[0075] Based on the display failure simulation function, a new top window covering the display window is created in the display window, and the mouse shape is set to none.
[0076] In one embodiment, the size of the top window is consistent with the size of the display window. After the human-machine interface failure disappears, the mouse shape is set to the original state and the top window is hidden.
[0077] In one embodiment, when the human-machine interface failure is a touch screen or hard button failure, the preset human-machine interface event is:
[0078] Determine whether there is preset event processing logic;
[0079] When there is no preset event processing logic, it does not respond to touch screen and hard button operations;
[0080] When there is a preset event processing logic, the operation of the touch screen and hard buttons is responded to based on the preset event processing logic.
[0081] In some embodiments, Figure 3 As shown, the working process of the DCS layer 2 system fault simulation system 10 is as follows:
[0082] The fault point determination module 100 obtains the fault instruction and determines whether there is a fault point corresponding to the fault instruction in the secondary workstation. If not, the process ends. If so, the fault value of each fault point is determined based on the fault value determination module 200.
[0083] Determine whether the fault point has changed based on the fault value. If it has changed, determine whether it is a network fault based on the fault type determination module 300. If it is a network fault, stop sending and receiving data. If it is not a network fault, determine whether it is a human-machine interface fault.
[0084] If not, return to the step of waiting for the fault point to change;
[0085] If so, the fault handling program is called, and the fault handling program calls back the fault callback function corresponding to the human-machine interface to generate a related fault event.
[0086] In the second aspect, based on the above-mentioned DCS layer 2 system fault simulation system, the present application also provides a DCS layer 2 system fault simulation method, such as Figure 4 As shown, the method includes:
[0087] S401, determining multiple fault points of the second-layer workstation corresponding to the fault instruction;
[0088] S402, determine the fault value of each fault point, and judge whether the fault point has changed based on the fault value. If it has changed, proceed to step S403; if it has not changed, end the fault simulation process;
[0089] S403, when the fault point changes, determine the fault type of the fault point, the fault type includes network fault and human-machine interface fault, when the fault type of the fault point is determined to be a network fault, proceed to step S404, when the fault type of the fault point is determined to be a human-machine interface fault, proceed to step S405;
[0090] S404, when the fault type of the fault point is a network fault, stopping data transmission and reception at the fault point;
[0091] S405: When the fault type of the fault point is a human-machine interface fault, respond to the human-machine interface fault based on a preset human-machine interface event.
[0092] It should be noted that the specific implementation principle or specific implementation details of each step of the above DCS layer 2 system fault simulation method can be found in the corresponding content of the above DCS layer 2 system fault simulation system embodiment, which will not be repeated here.
[0093] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by any technician familiar with the technical field within the technical scope disclosed in the present application should be covered within the protection scope of the present application.
Claims
1. A DCS layer 2 system fault simulation system, characterized in that: include: A fault point determination module, used to obtain a fault instruction and determine multiple fault points of the second-layer workstation corresponding to the fault instruction; A fault value judgment module is used to determine the fault value of each fault point and judge whether the fault point has changed based on the fault value; A fault type determination module is used to determine the fault type of the fault point when the fault point changes; A first fault processing module, used for stopping data transmission and reception at the fault point when the fault type of the fault point is a network fault; The second fault processing module is used to respond to the human-machine interface fault based on a preset human-machine interface event when the fault type of the fault point is a human-machine interface fault.
2. The DCS layer 2 system fault simulation system according to claim 1 is characterized in that: The fault value judgment module includes: An original point value acquisition unit, used to acquire the original point value of the fault point; The fault judgment unit is used to determine that the fault point has changed when the difference between the original point value and the fault value is greater than a preset difference.
3. The DCS two-layer system fault simulation system according to claim 2 is characterized in that: The original point value acquisition unit is used to add the original point value to the fault database.
4. The DCS layer 2 system fault simulation system according to claim 1, characterized in that: Fault types include network faults and human-machine interface faults.
5. The DCS two-layer system fault simulation system according to claim 1 is characterized in that: The DCS layer 2 system fault simulation system also includes: The fault database building module is used to obtain the point number of the fault point and build a fault database based on the point number and the fault value.
6. A DCS layer 2 system fault simulation method, characterized in that: include: S401, determining multiple fault points of the second-layer workstation corresponding to the fault instruction; S402, determine the fault value of each fault point, and judge whether the fault point has changed based on the fault value. If it has changed, proceed to step S403; if it has not changed, end the fault simulation process; S403, when the fault point changes, determine the fault type of the fault point, when it is determined that the fault type of the fault point is a network fault, proceed to step S404, when it is determined that the fault type of the fault point is a human-machine interface fault, proceed to step S405; S404, when the fault type of the fault point is a network fault, stopping data transmission and reception at the fault point; S405: When the fault type of the fault point is a human-machine interface fault, respond to the human-machine interface fault based on a preset human-machine interface event.
7. The DCS layer 2 system fault simulation method according to claim 6 is characterized in that: In S402, it is determined whether the fault point has changed based on the preset polling process.
8. The DCS layer 2 system fault simulation method according to claim 6 is characterized in that: In S404, the local network status is set to unavailable.
9. The DCS layer 2 system fault simulation method according to claim 6, characterized in that: Human-machine interface failures include mouse, keyboard, monitor, touch screen, and hard button failures.
10. The DCS layer 2 system fault simulation method according to claim 9, characterized in that: When the human-machine interface fault is a touch screen or hard button fault, the preset human-machine interface events are: Determine whether there is preset event processing logic; When there is no preset event processing logic, it does not respond to touch screen and hard button operations; When there is a preset event processing logic, the operation of the touch screen and hard buttons is responded to based on the preset event processing logic.