YOKOGAWA STARDOM FCN-500, Engineering Manual

Page: 88 / 226

<5. Function Test>
80
TI 34P02K35-02E Jun. 6, 2018-00
5.3 Unit Test Precautions
Unit test focuses on confirming the operation of control applications running on the
FCN-500 or FCN-RTU. This section describes know-how and precautions related to
unit test.
5.3.1 Pre-unit Test Checklist
Check the following items before starting unit test.
• Verify the source code.
Print out the source code, and check. Besides checking control logic, check that
application meets requirement specification.
• Verify that no Logic Designer compile errors and warnings are reported.
Check no errors or warnings are displayed in Logic Designer's compile result.
SEE ALSO
For details on compile errors and warnings, see Section 4.8, “Handling Compile Errors and Warnings.”
TIP
If multiple compile warnings on unused local variables and unused FB instances are reported, they can
be removed from all POU variable worksheets by selecting [Build]-[Remove unused variables and FB
instances] from the menu bar. This function, however, is only supported by Logic Designer R2.01.01
and later versions.
• Check for unused global variables.
Check for the presence of unused global variables following the procedure
described in Section 9.1.8, “Cross References” of Chapter 9, “Advanced
Engineering.” Specifically, if unused device label variables are found, determine
whether it is intentional or whether application programming is incomplete.
• Verify that no PLC error is reported at download.
Verify that no PLC error is reported when the project is downloaded to the FCN-
500 or FCN-RTU through Logic Designer.