SiL-test: Testing the POUs on the PC

This article is about the workflow phase "SiL-test (on PC)". (info)  This phase applies to an application and a library.

In the phase "SiL-test (on PC)", the →SiL-test incl. coverage is executed in Neuron Power Engineer for each POU on the PC verifying that the POU fulfills its specification and requirements in the simulated environment.

The SiL-test incl. coverages generates a coverage report for the POU. This coverage report is proving all branches in the implementation are covered by the test. This is a condition for operating a safety application.

In parallel, a SiL-test report is generated for each POU. This SiL-test report is proving that all requirement are verified by the test. This is also a condition for operating a safety application.

In case of the LVL-workflow, this phase can be omitted, if you comply with all warnings and/or notes as listed under "Recommendations for LVL-workflow".

How to test a →POU on the PC or how to perform the SiL-test for a POU ((warning) see SiL-test: Testing the POUs on the PC):

  1. In the Neuron Power Engineer project have the implemented test cases executed as SiL-Test with Coverage. Details: See Neuron Power Engineer user documentation, "Executing the test"

  2. Check the test report that the required coverage for the POU has been achieved and that all requirements have been covered by the SiL-test according to the specifications. (warning) See SiL-test: Testing the POUs on the PC and SiL-test: Testing the POUs on the PC.
    (info) Navigate within the test report as follows to see the appropriate information:

  3. In the console (where the progress of the SiL-test is displayed), click the hyperlink for the report to open the test report.

  4. In the test report, click the hyperlink for the POU (below of Statistics by Suite) and search for the text Coverage Information. The table below this text is listing the information on the test coverage (incl. branches).
    Details: See Neuron Power Engineer user documentation, "Checking the test execution"

  5. Again, in the test report, search for the text Statistics by Tag. The table below this text is listing the requirements of all executed test cases. Alternative: Click the hyperlink for the POU (below of Statistics by Suite). At the end of the displayed information, a table contains the column Tags in which the requirements per test case are listed.
    (warning) Mind that the requirements are only listed in the test report, if you have entered them within the implemented test case. If the requirements are not listed in the test report, you must use another method that is suited to track the requirements appropriately.

  6. Keep the SiL-test report because the names and fingerprints of the elements in these SiL-test reports will need to be compared with the information contained in the build report (see "Building and loading the application onto the PLC" ) or the library generation report (see "Creating and deploying a library").

Warning 1

For POUs for which the LVL workflow is not applicable, the SiL test is mandatory for each POU.

Warning 2

Warning 3

You must check for each POU which tests have been executed during the SiL-test.

  • It is mandatory that the same tests will be executed during the PiL-test.

  • The number of the executed tests must correspond to the expectations that are based on the test specification for the POU.