Reliability test method and device for nuclear power digital instrumentation and control system

By acquiring design requirements in the nuclear power digital instrumentation control system, writing and executing test cases, the time-consuming and labor-consuming problem of hardware failure injection testing is solved, and the rapid identification of fault tolerance and safety performance is achieved, reducing costs and improving testing efficiency.

CN115774432BActive Publication Date: 2024-11-26CHINA TECHENERGY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202111038015.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-06
Publication Date
2024-11-26
Estimated Expiration
2041-09-06

AI Technical Summary

Technical Problem

The prior art consumes a lot of human resources and time in the hardware failure injection test of nuclear power digital instrumentation control systems, and it is difficult to quickly and effectively verify the reliability of pure hardware products. The physically implemented fault injection accuracy is low, and the hardware implementation fault injection cost is High and may cause hardware damage.

Method used

A reliability testing method for nuclear power digital instrumentation control systems is proposed. By acquiring design requirements, testing objects are determined, testing cases are written, and testing cases for hardware single products and system products are executed in the product design stage to quickly identify fault-tolerant performance and safety performance. Reduce costs.

Benefits of technology

It realizes the fault-tolerant and security performance of hardware single products and system products quickly and effectively identify the fault-tolerant performance and security performance, reduces testing costs, improves testing efficiency, and avoids excessive consumption of human resources and time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115774432B_ABST
    Figure CN115774432B_ABST
Patent Text Reader

Abstract

The present application discloses a reliability testing method and device for a nuclear power digital instrumentation and control system. The reliability testing method for a nuclear power digital instrumentation and control system includes: obtaining the design requirements of the nuclear power digital instrumentation and control system, and determining the test objects of the nuclear power digital instrumentation and control system according to the design requirements, and the test objects include single hardware products and system products; writing corresponding test cases for the test objects, and the test cases include single hardware product test cases and system product test cases; executing single hardware product test cases in the product design stage to test the reliability of single hardware products; executing system product test cases in the system design stage to test the reliability of system products. The reliability testing method and device for a nuclear power digital instrumentation and control system of the embodiment of the present application can effectively and quickly identify the fault tolerance performance and safety performance of single hardware products and system products, and the solution is easy to implement and reduces costs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of nuclear power plant equipment, and in particular to a reliability testing method and device for a nuclear power digital instrumentation and control system. Background Art

[0002] Nuclear power DCS (Distributed Control System) safety-grade pure hardware products usually do not include programmable devices such as MCU (Microcontroller Unit), CPLD (Complex Programmable Logic Device) / FPGA (Field Programmable Gate Array). There is currently no efficient and cost-saving method for reliability and safety testing based on pure hardware circuits.

[0003] In an article titled "Application of Hardware Fault Injection Testing in Security Product Development", a hardware fault injection testing method based on security products is introduced, including the testing method and testing process of hardware fault injection, and the design and execution of hardware fault injection test cases are described in detail with specific examples. This method is actually also a reliability test, but it consumes a lot of human resources and time. If it is a project with time or resource constraints, it is necessary to reduce the scope of testing security functions and hardware fault injection. This method cannot quickly, effectively, and comprehensively verify the reliability of pure hardware products.

[0004] In an article titled "A Review of Safety Testing Methods Based on Fault Injection", prototype-based fault injection technology is proposed, including physical fault injection and hardware fault injection. However, physical fault injection is not easy to control, has low accuracy, and is prone to accidents; in addition, hardware fault injection requires additional equipment, requires a large investment, and may cause hardware damage.

[0005] Among the existing safety-level hardware product reliability testing methods, hardware fault injection testing technology is based on the analysis results of FMEDA (Failure Modes Effects and Diagnostic Analysis), which is consistent with FMEDA analysis. FMEDA analysis determines the safety impact and diagnostic methods of random hardware failures, while fault injection testing verifies the actual impact of various failure modes on the system through actual on-board testing to determine whether the FMEDA analysis is correct.

[0006] Although most of the existing reliability testing methods for safety-level hardware products can be directly tested on the actual board, hardware fault injection testing can improve the reliability and safety of the system and can truly verify whether the system and board level can be guided to a safe state after various modes occur. However, such methods require a lot of human resources and time. In some projects with limited time or resources, such methods cannot be widely used. Summary of the invention

[0007] The purpose of this application is to solve one of the above-mentioned technical problems at least to a certain extent.

[0008] To this end, the first purpose of this application is to propose a reliability testing method for a nuclear power digital instrumentation and control system, which can effectively and quickly identify the fault tolerance and safety performance of hardware single products and system products. The solution is easy to implement and reduces costs.

[0009] The second objective of the present application is to provide a reliability testing device for a nuclear power digital instrumentation and control system.

[0010] The third object of the present application is to provide a computer device.

[0011] A fourth object of the present application is to provide a non-transitory computer-readable storage medium.

[0012] In order to achieve the above-mentioned purpose, the first embodiment of the present application proposes a nuclear power digital instrumentation and control system reliability testing method, comprising:

[0013] Obtaining design requirements for a nuclear power digital instrumentation and control system, and determining test objects for the nuclear power digital instrumentation and control system according to the design requirements, wherein the test objects include hardware single products and system products;

[0014] Compile corresponding test cases for the test object, the test cases including hardware single product test cases and system product test cases;

[0015] Executing the hardware single product test case during the product design phase to test the reliability of the hardware single product;

[0016] The system product test cases are executed during the system design phase to test the reliability of the system product.

[0017] Optionally, obtaining design requirements of a nuclear power digital instrumentation and control system, and determining a test object of the nuclear power digital instrumentation and control system according to the design requirements, includes:

[0018] Select products required for the design according to the design requirements, the products including safety-grade products and non-safety-grade products;

[0019] Acquire the characteristics of the security-level product, and select the security-level product to be tested as the test object according to the characteristics of the security-level product, wherein the characteristics of the security-level product include first functional characteristics, performance characteristics, fault tolerance and stability;

[0020] The characteristics of the non-security-level products are obtained, and non-security-level products to be tested are selected as test objects according to the characteristics of the non-security-level products, wherein the characteristics of the non-security-level products include second functional characteristics.

[0021] Optionally, the first functional characteristics include diagnostic functions, power supply DC-DC / AC-DC conversion and filtering functions, and key functions of communication, analog front-end conditioning, and clock crystal oscillator circuits;

[0022] The performance characteristics include analog acquisition / output accuracy, network communication rate, and response time;

[0023] The fault tolerance includes determining the failure mode through analysis to guide safety / danger;

[0024] The stability includes circuit parameter drift.

[0025] Optionally, the second functional characteristics include failure rate and key functions of the board.

[0026] Optionally, when the test object is a single hardware product, a corresponding test case is written for the test object, including:

[0027] Select the fault model corresponding to the single hardware product based on the device failure model in the failure mode and effect analysis FMEA report;

[0028] Write the fault model corresponding to the hardware single product into the hardware single product test case.

[0029] Optionally, when the test object is a system product, a corresponding test case is written for the test object, including:

[0030] Selecting a fault model corresponding to the system product based on system design requirements;

[0031] Write the fault model corresponding to the system product into the system product test case.

[0032] Optionally, the fault model corresponding to the system product includes a product-level failure model and a system-level failure model.

[0033] The product-level failure model includes power failure, communication failure, digital quantity acquisition / output and analog quantity acquisition / output function abnormality, and main control unit configuration / control failure;

[0034] The system-level failure model includes the failure of the system hardware diagnosis function and the abnormality of the system alarm function.

[0035] Optionally, executing the hardware single product test case in the product design stage to test the reliability of the hardware single product includes:

[0036] Set the hardware failure duration of the hardware single product;

[0037] Setting a hardware fault injection time for the hardware single product;

[0038] Generate a hardware fault of the hardware single product;

[0039] The test result of the hardware single product is recorded. If the test result of the hardware single product is inconsistent with the qualified criterion in the test case of the hardware single product, the tested hardware single product is determined to be a defective product.

[0040] Optionally, executing the system product test case in the system design phase to test the reliability of the system product includes:

[0041] Setting the duration of hardware failure of the system product;

[0042] Setting a hardware fault injection time for the system product;

[0043] Generate hardware failure of the system product;

[0044] The test result of the system product is recorded. If the test result of the system product is inconsistent with the qualified criterion in the test case of the system product, it is determined that the tested system product is a defective product.

[0045] The reliability testing method of the nuclear power digital instrumentation and control system of the embodiment of the present application obtains the design requirements of the nuclear power digital instrumentation and control system, determines the test object of the nuclear power digital instrumentation and control system according to the design requirements, and then writes corresponding test cases for the test object. Then, the hardware single product test cases are executed in the product design stage to test the reliability of the hardware single product, and the system product test cases are executed in the system design stage to test the reliability of the system product. The method can effectively and quickly identify the fault tolerance performance and safety performance of the hardware single product and the system product, and the solution is easy to implement and reduces costs.

[0046] In order to achieve the above-mentioned purpose, the second embodiment of the present application proposes a nuclear power digital instrumentation and control system reliability testing device, comprising:

[0047] A determination module, used to obtain the design requirements of the nuclear power digital instrumentation and control system, and determine the test object of the nuclear power digital instrumentation and control system according to the design requirements, wherein the test object includes a single hardware product and a system product;

[0048] A programming module, used to write corresponding test cases for the test object, wherein the test cases include hardware single product test cases and system product test cases;

[0049] A first test module, used to execute the hardware single product test case in the product design stage to test the reliability of the hardware single product;

[0050] The second test module is used to execute the system product test cases during the system design phase to test the reliability of the system product.

[0051] Optionally, the determining module is used to:

[0052] Select products required for the design according to the design requirements, the products including safety-grade products and non-safety-grade products;

[0053] Acquire the characteristics of the security-level product, and select the security-level product to be tested as the test object according to the characteristics of the security-level product, wherein the characteristics of the security-level product include first functional characteristics, performance characteristics, fault tolerance and stability;

[0054] The characteristics of the non-security-level products are obtained, and non-security-level products to be tested are selected as test objects according to the characteristics of the non-security-level products, wherein the characteristics of the non-security-level products include second functional characteristics.

[0055] Optionally, the first functional characteristics include diagnostic functions, power supply DC-DC / AC-DC conversion and filtering functions, and key functions of communication, analog front-end conditioning, and clock crystal oscillator circuits;

[0056] The performance characteristics include analog acquisition / output accuracy, network communication rate, and response time;

[0057] The fault tolerance includes determining the failure mode through analysis to be safety / danger oriented;

[0058] The stability includes circuit parameter drift.

[0059] Optionally, the second functional characteristics include failure rate and key functions of the board.

[0060] Optionally, the programming module is used to:

[0061] When the test object is a single hardware product, the fault model corresponding to the single hardware product is selected based on the device failure model in the failure mode and effects analysis FMEA report;

[0062] Write the fault model corresponding to the hardware single product into the hardware single product test case.

[0063] Optionally, the programming module is used to:

[0064] When the test object is a system product, a fault model corresponding to the system product is selected based on the system design requirements;

[0065] Write the fault model corresponding to the system product into the system product test case.

[0066] Optionally, the fault model corresponding to the system product includes a product-level failure model and a system-level failure model.

[0067] The product-level failure model includes power failure, communication failure, digital quantity acquisition / output and analog quantity acquisition / output function abnormality, and main control unit configuration / control failure;

[0068] The system-level failure model includes the failure of the system hardware diagnosis function and the abnormality of the system alarm function.

[0069] Optionally, the first test module is used to:

[0070] Set the hardware failure duration of the hardware single product;

[0071] Setting a hardware fault injection time for the hardware single product;

[0072] Generate a hardware fault of the hardware single product;

[0073] The test result of the hardware single product is recorded. If the test result of the hardware single product is inconsistent with the qualified criterion in the test case of the hardware single product, the tested hardware single product is determined to be a defective product.

[0074] Optionally, the second test module is used to:

[0075] Setting the duration of hardware failure of the system product;

[0076] Setting a hardware fault injection time for the system product;

[0077] Generate hardware failure of the system product;

[0078] The test result of the system product is recorded. If the test result of the system product is inconsistent with the qualified criterion in the test case of the system product, it is determined that the tested system product is a defective product.

[0079] The nuclear power digital instrumentation and control system reliability testing device of the embodiment of the present application obtains the design requirements of the nuclear power digital instrumentation and control system, determines the test object of the nuclear power digital instrumentation and control system according to the design requirements, and then writes corresponding test cases for the test object. Then, the hardware single product test cases are executed in the product design stage to test the reliability of the hardware single product, and the system product test cases are executed in the system design stage to test the reliability of the system product. The fault tolerance performance and safety performance of the hardware single product and the system product can be effectively and quickly identified, and the solution is easy to implement and reduces costs.

[0080] In order to achieve the above-mentioned objectives, the third aspect embodiment of the present application proposes a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the reliability testing method of the nuclear power digital instrumentation and control system as described in the first aspect embodiment is implemented.

[0081] In order to achieve the above-mentioned objectives, the fourth aspect embodiment of the present application also proposes a non-temporary computer-readable storage medium, on which a computer program is stored, characterized in that when the computer program is executed by a processor, it implements the nuclear power digital instrumentation and control system reliability testing method as described in the first aspect embodiment.

[0082] Additional aspects and advantages of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0084] Figure 1 This is a flow chart of a method for reliability testing of a nuclear power digital instrumentation and control system according to an embodiment of the present application;

[0085] Figure 2 It is a flow chart for determining the test object of the nuclear power digital instrumentation and control system;

[0086] Figure 3 This is a flow chart for testing the reliability of a single hardware product;

[0087] Figure 4 It is a flow chart for testing the reliability of system products;

[0088] Figure 5 It is a schematic diagram of the effect of the relationship between failure mode and hardware fault injection verification;

[0089] Figure 6 It is a schematic diagram of the effect of the location of hardware fault injection testing in each test stage;

[0090] Figure 7 It is a structural schematic diagram of a nuclear power digital instrumentation and control system reliability testing device according to an embodiment of the present application. DETAILED DESCRIPTION

[0091] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0092] The present application is further described in detail below in conjunction with specific embodiments. These embodiments should not be construed as limiting the scope of protection claimed in the present application.

[0093] The following describes the reliability testing method and device of the nuclear power digital instrumentation and control system in the embodiment of the present application with reference to the accompanying drawings.

[0094] Figure 1 FIG. 1 is a flow chart of a method for testing the reliability of a nuclear power digital instrumentation and control system according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0095] S1, obtain the design requirements of the nuclear power digital instrumentation and control system, and determine the test object of the nuclear power digital instrumentation and control system according to the design requirements.

[0096] Among them, the test objects include single hardware products and system products.

[0097] Before the nuclear power digital instrumentation and control system officially starts operation, it is necessary to conduct reliability and safety tests on the nuclear power digital instrumentation and control system. In other words, it is necessary to test the hardware products and system products involved in the system. Therefore, it is necessary to first determine which hardware products and system products in the system need to be tested as test objects.

[0098] Specifically, Figure 2 As shown, the step further includes:

[0099] S11, select the products required for the design according to the design requirements.

[0100] Among them, products include safety-level products and non-safety-level products. There are different extraction principles for safety-level products and non-safety-level products.

[0101] S12, obtaining characteristics of security-level products, and selecting security-level products to be tested as test objects according to the characteristics of the security-level products.

[0102] Among them, the characteristics of safety-level products include first functional characteristics, performance characteristics, fault tolerance and stability.

[0103] Specifically, the first functional characteristics include diagnostic functions, power supply DC-DC / AC-DC conversion and filtering functions, as well as key functions of communication, analog front-end conditioning, and clock crystal circuits. In other words, the devices involved in the above functions need to be tested.

[0104] Performance characteristics include analog acquisition / output accuracy, network communication rate, and response time. In other words, devices related to the above performance need to be tested.

[0105] Fault tolerance includes determining through analysis whether the failure mode leads to safety / hazard. If a device cannot be determined through analysis whether the failure mode leads to safety / hazard, then the device needs to be tested.

[0106] Stability includes circuit parameter drift. Devices that are prone to circuit parameter drift as the ambient temperature, humidity, and time change need to be tested.

[0107] In summary, the security-level products that need to be tested can be selected through the above dimensions.

[0108] S13, obtaining characteristics of non-safety-grade products, and selecting non-safety-grade products to be tested as test objects according to the characteristics of the non-safety-grade products.

[0109] Among them, the characteristics of non-safety-grade products include the second functional characteristics, which further include failure rate and key functions of the board. For non-safety-grade products, it is necessary to select devices with high failure rates and devices involving key functions of the board for testing.

[0110] S2, write corresponding test cases for the test object.

[0111] Among them, test cases are classified by type and may include hardware single product test cases and system product test cases. Hardware single product test cases are test cases for hardware single products, and system product test cases are test cases for system products. In actual application, the above test cases can be written as one test case.

[0112] When the test object is a single hardware product, the fault model corresponding to the single hardware product can be selected based on the device failure model in the FMEA (Failure Mode and Effects Analysis) report, and then the fault model corresponding to the single hardware product can be written into the single hardware product test case.

[0113] When the test object is a system product, the fault model corresponding to the system product can be selected based on the system design requirements, and then the fault model corresponding to the system product can be written into the system product test case.

[0114] Among them, the fault models corresponding to system products include product-level failure models and system-level failure models. Specifically, product-level failure models include power failure, communication failure, digital acquisition / output and analog acquisition / output function abnormalities, and main control unit configuration / control failure; system-level failure models include system hardware diagnosis function failure and system alarm function abnormalities. By hierarchical processing of failure models, the scope of fault identification and fault injection can be fully covered.

[0115] S3, executes hardware single product test cases during the product design phase to test the reliability of the hardware single product.

[0116] The specific testing process is as follows: Figure 3 As shown, the steps include:

[0117] S31, setting the hardware failure duration of a single hardware product.

[0118] The injection time can be selected as single, periodic or continuous.

[0119] S32, setting the hardware fault injection time of a single hardware product.

[0120] You can choose to inject it before powering on a single hardware product or system product or during operation.

[0121] S33, generating a hardware failure of a single hardware product.

[0122] Create corresponding hardware failures in the hardware product based on the test cases.

[0123] S34, recording the test results of a single hardware product.

[0124] If the test result of the hardware single product is inconsistent with the qualified criteria in the hardware single product test case, the tested hardware single product is determined to be a defective product.

[0125] S4, executes system product test cases during the system design phase to test the reliability of the system product.

[0126] The specific testing process is as follows: Figure 4 As shown, the steps include:

[0127] S41, setting the hardware failure duration of the system product.

[0128] S42, setting a hardware fault injection time of the system product.

[0129] S43, generates a hardware failure of the system product.

[0130] S44, record the test results of the system products.

[0131] If the test result of the system product is inconsistent with the qualified criteria in the system product test case, the tested system product is determined to be a defective product.

[0132] The reliability testing method for a nuclear power digital instrumentation and control system in an embodiment of the present application obtains the design requirements of the nuclear power digital instrumentation and control system, determines the test object of the nuclear power digital instrumentation and control system according to the design requirements, and then compiles corresponding test cases for the test object. Then, the hardware single product test cases are executed in the product design stage to test the reliability of the hardware single product, and the system product test cases are executed in the system design stage to test the reliability of the system product. This method can effectively and quickly identify the fault tolerance and safety performance of the hardware single product and the system product, and the solution is easy to implement and reduces costs.

[0133] The following is a detailed description of a method for testing the reliability of a nuclear power digital instrumentation and control system using a specific embodiment.

[0134] The IEC61508-2010 standard explicitly requires that safety-level hardware single products and system products need to perform hardware fault injection testing to verify the rationality and effectiveness of hardware design and safety analysis, prompting R&D personnel to adjust and improve the design scheme, thereby improving the quality and safety of single boards and systems. In response to the requirements of the standard, this embodiment proposes a reliability testing method for a nuclear power digital instrumentation and control system. The method includes hardware fault injection testing methods, sampling selection of fault modes, hardware fault injection testing procedures, test plans and use case design, test execution, and other contents.

[0135] 1. Hardware fault injection test method

[0136] The objects of hardware fault injection are divided into single hardware products and system products, so the fault injection test method is actually divided into two dimensions, single hardware product fault injection and system product fault injection. Generally speaking, the hardware fault injection test method is based on FMEA analysis technology, establishes hardware failure modes, and verifies the preventive measures of failure modes through fault insertion technology. The relationship between failure modes and hardware fault injection verification can be shown as follows: Figure 5 As shown, single hardware product fault injection can cover device-level failure models and circuit-level failure models, and system product fault injection covers product-level and system-level failure models, so that the scope of fault identification and fault injection is complete.

[0137] Hardware single product fault injection test method: It is essentially different from the conventional hardware circuit function test method. It is based on the component failure model and conducts comprehensive fault injection testing from a physical perspective to identify potential hardware defects and post-failure impacts. The hardware single product failure is based on an effective device failure library model. This embodiment adopts the failure model specified in IEC62061, specifically, sampling based on the device failure model in the FMEA report as the test failure model for the hardware single product.

[0138] System product fault injection test method: System product faults generally come from single product level failures and system level failures. Single product level failures include power board power failure / undervoltage / overvoltage failures, gateway communication failures, etc. System level failures include system level diagnostic function, system monitoring function, etc. System product fault failure types are limited, all of which can be identified and tested in full range.

[0139] 2. Principles for selecting fault models (single hardware product) / selection (system product)

[0140] 2.1 Principles for selecting fault models for single hardware products

[0141] According to the FMEA analysis report, in actual applications, there are hundreds or even thousands of devices on a single board that need to consider failure modes. However, in projects with limited time or cost, it is impossible to traverse all device failure modes.

[0142] Through the equivalence classification method, combined with the product's quality characteristic parameters, a certain fault sampling selection principle is established to screen representative hardware fault models. For products with different security levels, the sampling selection principle will be different. Among them, the sampling principle for a single hardware product is shown in Table 1:

[0143]

[0144]

[0145] Table 1

[0146] 2.2 Principles for selecting fault models for system products

[0147] Specifically, the fault model selection principle of the system product can be shown in Table 2:

[0148]

[0149] Table 2

[0150] 3. Hardware fault injection test process

[0151] The execution phase and testing process of hardware fault injection testing in nuclear power safety-level product testing are generally distributed in two stages: product confirmation testing and system testing. Taking safety-level products as an example, in the entire life cycle of safety-level products, before fault injection testing, it is necessary to complete hardware FMEA analysis, embedded software code writing, hardware design, and sample debugging, and then perform hardware single product and system product fault injection testing. The position of hardware fault injection testing in each testing phase can be as follows: Figure 6 As shown in the figure. In the product requirements / design stage, the corresponding tests are software unit testing, hardware single board testing and confirmation testing. In this stage, hardware fault injection testing of single hardware products can be performed; in the system requirements / design stage, the corresponding tests are system testing and system integration testing. In this stage, hardware fault injection testing of system products can be performed.

[0152] 4. Test plan and use case design

[0153] Before the hardware fault test is executed, it is necessary to write a test plan and test cases. The test plan mainly coordinates test resources, arranges test time, builds the test environment, and conducts preliminary debugging of automated test equipment. The test cases of single hardware products are selected according to the hardware failure mode selection principle of safety-level products. Then, according to the failure mode in the FMEA analysis report, the corresponding test cases are designed and the impact analysis after the device failure in FMEA is used as the qualification criterion for the single hardware product test. The test cases of system products are selected according to the hardware failure mode selection principle of system products. The corresponding test cases are written in the system testing phase, and the corresponding test qualification criteria are determined according to the analysis of the fault-tolerant design requirements of the system products.

[0154] 5. Test execution

[0155] Taking safety-level products as an example, the following is the execution process of hardware fault injection testing.

[0156] Step 1: Select the duration of the hardware fault. You can choose the injection time as single, periodic, or continuous.

[0157] Step 2: Select the time to inject hardware faults. You can choose to inject before powering on a single hardware product or system product or during operation.

[0158] Step 3: Create hardware faults. Create corresponding hardware faults in single hardware products or system products according to the test cases, such as hardware open circuit and short circuit faults.

[0159] Step 4: Record the test data, including data before and after the hardware fault is inserted. Any test result that is inconsistent with the qualified criteria in the test case is considered a defect.

[0160] After the test process is completed, the test data needs to be organized and merged into the product confirmation test report. If the fault injection test is performed in the system test environment, the hardware fault injection test results can be recorded in the system test report. The test report needs to record the test environment, hardware test sample information (including hardware PCB (Printed Circuit Board), Logic, PCBA_BOM (Printed Circuit Board Assembly, PCBA bill of materials) and product BOM (Bill of Material)), software test version and other information.

[0161] The nuclear power safety-level hardware product reliability testing method based on hardware insertion testing in the embodiment of the present application can effectively and quickly identify the fault tolerance and safety performance of single hardware products and system products through hardware fault insertion technology, with less manpower investment and low time cost, and can effectively improve the reliability and safety of pure hardware products and system products.

[0162] In order to implement the above-mentioned embodiment, the present application also proposes a reliability testing device for a nuclear power digital instrumentation and control system.

[0163] Figure 7 It is a structural schematic diagram of a nuclear power digital instrumentation and control system reliability testing device according to an embodiment of the present application.

[0164] like Figure 7 As shown, the device includes a determination module 71 , a programming module 72 , a first test module 73 and a second test module 74 .

[0165] The determination module 71 is used to obtain the design requirements of the nuclear power digital instrumentation and control system and determine the test objects of the nuclear power digital instrumentation and control system according to the design requirements. The test objects include hardware single products and system products.

[0166] The determination module 71 is specifically used to: select the products required for the design according to the design requirements, and the products include safety-level products and non-safety-level products; obtain the characteristics of the safety-level products, and select the safety-level products that need to be tested as the test objects according to the characteristics of the safety-level products, and the characteristics of the safety-level products include the first functional characteristics, performance characteristics, fault tolerance and stability; obtain the characteristics of the non-safety-level products, and select the non-safety-level products that need to be tested as the test objects according to the characteristics of the non-safety-level products, and the characteristics of the non-safety-level products include the second functional characteristics. The first functional characteristics include diagnostic functions, power supply DC-DC / AC-DC conversion and filtering functions, and key functions of communication, analog front-end conditioning, and clock crystal oscillator circuits; performance characteristics include analog quantity acquisition / output accuracy, network communication rate, and response time; fault tolerance includes determining the fault mode through analysis to guide safety / danger; stability includes circuit parameter drift. The second functional characteristics include failure rate and key functions of the board.

[0167] The programming module 72 is used to write corresponding test cases for the test object, and the test cases include hardware single product test cases and system product test cases.

[0168] The programming module 72 is specifically used for: when the test object is a single hardware product, selecting the fault model corresponding to the single hardware product based on the device failure model in the failure mode and effects analysis FMEA report; and writing the fault model corresponding to the single hardware product into the single hardware product test case.

[0169] The programming module 72 is specifically used for: when the test object is a system product, selecting a fault model corresponding to the system product based on the system design requirements; and writing the fault model corresponding to the system product into a system product test case.

[0170] The fault models corresponding to system products include product-level failure models and system-level failure models. Product-level failure models include power failure, communication failure, digital quantity acquisition / output and analog quantity acquisition / output function abnormalities, and main control unit configuration / control failure; system-level failure models include system hardware diagnostic function failure and system alarm function abnormalities.

[0171] The first test module 73 is used to execute hardware single product test cases during the product design phase to test the reliability of the hardware single product.

[0172] The first test module 73 is specifically used to: set the duration of the hardware fault of the single hardware product; set the hardware fault injection time of the single hardware product; generate the hardware fault of the single hardware product; record the test result of the single hardware product, if the test result of the single hardware product is inconsistent with the qualified criteria in the test case of the single hardware product, then determine that the tested single hardware product is a defective product.

[0173] The second testing module 74 is used to execute system product test cases during the system design phase to test the reliability of the system product.

[0174] The second test module 74 is specifically used to: set the duration of the hardware fault of the system product; set the hardware fault injection time of the system product; generate the hardware fault of the system product; record the test result of the system product. If the test result of the system product is inconsistent with the qualified criteria in the system product test case, it is determined that the tested system product is a defective product.

[0175] It should be understood that the nuclear power digital instrumentation and control system reliability testing device of this embodiment is consistent with the description of the nuclear power digital instrumentation and control system reliability testing method of the first aspect embodiment, and will not be repeated here.

[0176] The nuclear power digital instrumentation and control system reliability test device of the embodiment of the present application obtains the design requirements of the nuclear power digital instrumentation and control system, determines the test object of the nuclear power digital instrumentation and control system according to the design requirements, and then writes corresponding test cases for the test object. Then, the hardware single product test cases are executed in the product design stage to test the reliability of the hardware single product, and the system product test cases are executed in the system design stage to test the reliability of the system product. This device can effectively and quickly identify the fault tolerance performance and safety performance of the hardware single product and the system product, and the solution is easy to implement and reduces costs.

[0177] In order to implement the above embodiments, the present application also proposes a computer device.

[0178] The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the reliability testing method for a nuclear power digital instrumentation and control system according to the first embodiment is implemented.

[0179] In order to implement the above embodiments, the present application also proposes a non-transitory computer-readable storage medium.

[0180] The non-temporary computer-readable storage medium stores a computer program, which, when executed by a processor, implements the nuclear power digital instrumentation and control system reliability testing method as described in the first aspect of the embodiment.

[0181] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0182] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing in a suitable manner if necessary, and then stored in a computer memory.

[0183] It should be understood that the various parts of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0184] It should be noted that, in the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0185] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

Claims

1. A reliability testing method for a nuclear power digital instrumentation and control system, characterized in that: The following steps are involved: Obtaining design requirements for a nuclear power digital instrumentation and control system, and determining test objects for the nuclear power digital instrumentation and control system according to the design requirements, wherein the test objects include hardware single products and system products; Compile corresponding test cases for the test object, the test cases including hardware single product test cases and system product test cases; Executing the hardware single product test case during the hardware single product design phase to test the reliability of the hardware single product; Executing the system product test cases during the system product design phase to test the reliability of the system product; Obtaining the design requirements of the nuclear power digital instrumentation and control system, and determining the test object of the nuclear power digital instrumentation and control system according to the design requirements, including: Select products required for the design according to the design requirements, the products including safety-grade products and non-safety-grade products; Acquire the characteristics of the security-level product, and select the security-level product to be tested as the test object according to the characteristics of the security-level product, wherein the characteristics of the security-level product include first functional characteristics, performance characteristics, fault tolerance and stability; Acquiring the characteristics of the non-security-level products, and selecting non-security-level products to be tested as test objects according to the characteristics of the non-security-level products, wherein the characteristics of the non-security-level products include second functional characteristics; The first functional characteristics include diagnostic functions, power supply DC conversion, power supply AC-DC conversion and filtering functions, as well as key functions of communication, analog front-end conditioning, and clock crystal oscillator circuits; The performance characteristics include analog acquisition / output accuracy, network communication rate, and response time; The fault tolerance includes determining the failure mode through analysis to be safety / danger oriented; The stability includes circuit parameter drift; When the test object is a single hardware product, write corresponding test cases for the test object, including: Select the fault model corresponding to the single hardware product based on the device failure model in the failure mode and effect analysis FMEA report; Writing the fault model corresponding to the hardware single product into the hardware single product test case; When the test object is a system product, write corresponding test cases for the test object, including: Selecting a fault model corresponding to the system product based on system design requirements; Writing the fault model corresponding to the system product into the system product test case; The fault model corresponding to the system product includes a product-level failure model and a system-level failure model. The product-level failure model includes power failure, communication failure, digital quantity acquisition / output and analog quantity acquisition / output function abnormality, and main control unit configuration / control failure; The system-level failure model includes the failure of the system hardware diagnosis function and the abnormality of the system alarm function.

2. The method according to claim 1, characterized in that The second functional characteristics include failure rate and board key functions.

3. The method according to claim 1, characterized in that Executing the hardware single product test case during the product design phase to test the reliability of the hardware single product includes: Set the hardware failure duration of the hardware single product; Setting a hardware fault injection time for the hardware single product; Generate a hardware fault of the hardware single product; The test result of the hardware single product is recorded. If the test result of the hardware single product is inconsistent with the qualified criterion in the test case of the hardware single product, the tested hardware single product is determined to be a defective product.

4. The method according to claim 1, characterized in that Executing the system product test cases during the system design phase to test the reliability of the system product includes: Setting the duration of hardware failure of the system product; Setting a hardware fault injection time for the system product; Generate hardware failure of the system product; The test result of the system product is recorded. If the test result of the system product is inconsistent with the qualified criterion in the test case of the system product, it is determined that the tested system product is a defective product.

5. A nuclear power digital instrumentation and control system reliability test device, characterized in that: include: A determination module, used to obtain the design requirements of the nuclear power digital instrumentation and control system, and determine the test object of the nuclear power digital instrumentation and control system according to the design requirements, wherein the test object includes a single hardware product and a system product; A programming module, used to write corresponding test cases for the test object, wherein the test cases include hardware single product test cases and system product test cases; A first test module is used to execute the hardware single product test case during the hardware single product design phase to test the reliability of the hardware single product; A second test module is used to execute the system product test case during the system product design phase to test the reliability of the system product; The determining module is used to: Select products required for the design according to the design requirements, the products including safety-grade products and non-safety-grade products; Acquire the characteristics of the security-level product, and select the security-level product to be tested as the test object according to the characteristics of the security-level product, wherein the characteristics of the security-level product include first functional characteristics, performance characteristics, fault tolerance and stability; Acquiring the characteristics of the non-security-level products, and selecting non-security-level products to be tested as test objects according to the characteristics of the non-security-level products, wherein the characteristics of the non-security-level products include second functional characteristics; The first functional characteristics include diagnostic functions, power supply DC conversion, power supply AC-DC conversion and filtering functions, as well as key functions of communication, analog front-end conditioning, and clock crystal oscillator circuits; The performance characteristics include analog acquisition / output accuracy, network communication rate, and response time; The fault tolerance includes determining the failure mode through analysis to be safety / danger oriented; The stability includes circuit parameter drift; The programming module is used to: When the test object is a single hardware product, the fault model corresponding to the single hardware product is selected based on the device failure model in the failure mode and effects analysis FMEA report; Writing the fault model corresponding to the hardware single product into the hardware single product test case; When the test object is a system product, a fault model corresponding to the system product is selected based on the system design requirements; Writing the fault model corresponding to the system product into the system product test case; The fault model corresponding to the system product includes a product-level failure model and a system-level failure model. The product-level failure model includes power failure, communication failure, digital quantity acquisition / output and analog quantity acquisition / output function abnormality, and main control unit configuration / control failure; The system-level failure model includes the failure of the system hardware diagnosis function and the abnormality of the system alarm function.