User's Manual ProSafe-RS System Test Reference 4th Edition
Introduction i When constructing and maintaining safety systems, debugging and testing are very important. ProSafe-RS provides functions for debugging and testing efficiently. In ProSafe-RS, tests are classified according to targets used during testing as follows. Target test This test type uses actual devices. SCS simulation test This test type uses an SCS simulator running on a PC. An SCS simulation test is executed in a CENTUM integration environment. Note that this test involves an SCS simulator along with an FCS simulator and an HIS simulator, while PC is logically disconnected from the control buses, is called a virtual test. Logic simulation test This test type uses a logic simulator running on a PC. Logic simulation tests are primarily used in POU module tests. This document is a reference manual that explains system test functions of ProSafe-RS. It contains information on types of test function that can be used with ProSafe-RS and operation procedures as a reference document. To carry out ProSafe-RS tests, please read the test function section of Engineering Guide (IM 32Q01C10-31E) first. Read the appropriate sections of this manual to examine related information, learn about operation details and obtain deeper understanding. This manual consists of the following chapters: Chapter 1 Overview of ProSafe-RS System Tests This chapter describes an overview of the tests that can be executed with ProSafe-RS and explains the functions, operation procedures and software/hardware environments. Read this chapter to learn about these details. Chapter 2 Operations of Logic Simulation Tests This chapter describes an overview of logic simulation tests and explains the operations. Read this chapter to learn about these details. Chapter 3 SCS Simulation Tests This chapter explains the following details of SCS simulation tests. Engineering procedures and operation procedures of SCS simulation tests Functions of the SCS Test Function window and how to operate them How to execute SCS simulation tests and to utilize test support functions Expanded test functions Tests using multiple SCS simulators Testing CENTUM integration in virtual tests Read this chapter to learn about these details. Chapter 4 Target Tests This chapter describes an overview of target tests and explains how to execute tests in cases where online changes are possible or impossible, respectively. Read this chapter to learn about these details. Chapter 5 Test Function Tools This chapter explains tools used in engineering tests. Read this chapter to learn about these details. Media No. (CD) 4th Edition : Jan. 2015 (YK) All Rights Reserved Copyright 2011, Yokogawa Electric Corporation
Safety Precautions for Use ii Safety, Protection, and Modification of the Product To protect the system controlled by the Product and the Product itself and to ensure safe operation, please observe the safety precautions described in this Manual. Yokogawa Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe the safety precautions and instructions when operating the Product. If the Product is used in a manner not specified in the User's Manuals, the protection provided by the Product may be impaired. If any protection or safety circuit is required for the system controlled by the Product or for the Product itself, please install it externally. Use only spare parts that are approved by YOKOGAWA when replacing parts or consumables of the Product. Do not use the Product and its accessories such as power cords on devices that are not approved by YOKOGAWA. Do not use the Product and its accessories for any purpose other than those intended by YOKOGAWA. Modification of the Product is strictly prohibited. The following symbols are used in the Product and User's Manuals to indicate the accompanying safety precautions: Indicates that caution is required for operation. This symbol is labeled on the Product to refer the user to the User's Manuals for necessary actions or behaviors in order to protect the operator and the equipment against dangers such as electric shock. In the User's Manuals, you will find the precautions necessary to prevent physical injury or death, which may be caused by accidents, such as electric shock resulting from operational mistakes. Identifies a protective conductor terminal. Before using the Product, you must ground the protective conductor terminal to avoid electric shock. Identifies a functional grounding terminal. A terminal marked "FG" also has the same function. This terminal is used for grounding other than protective grounding. Before using the Product, you must ground this terminal. Indicates an AC supply. Indicates a DC supply. Indicates the ON position of a power on/off switch. Indicates the OFF position of a power on/off switch. Notes on Handling User's Manuals Hand over the User's Manuals to your end users so that they can keep the User's Manuals on hand for convenient reference. Thoroughly read and understand the information in the User's Manuals before using the Product. For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that the Product is suitable for any particular purpose but to describe the functional details of the Product. Contents of the User's Manuals are subject to change without notice.
Every effort has been made to ensure the accuracy of contents in the User's Manuals. However, should you have any questions or find any errors, contact us or your local distributor. The User's Manuals with unordered or missing pages will be replaced. Warning and Disclaimer Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for the Product. YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either using or not being able to use the Product. Notes on Software YOKOGAWA makes no warranties, either expressed or implied, with respect to the Software Product's merchantability or suitability for any particular purpose, except as specified in the warranty terms. Purchase the appropriate number of licenses of the Software Product according to the number of computers to be used. No copy of the Software Product may be made for any purpose other than backup; otherwise, it is deemed as an infringement of YOKOGAWA's Intellectual Property rights. Keep the software medium of the Software Product in a safe place. No reverse engineering, reverse compiling, reverse assembling, or converting the Software Product to human-readable format may be performed for the Software Product. No part of the Software Product may be transferred, converted, or sublet for use by any third-party, without prior written consent from YOKOGAWA. iii
iv Documentation Conventions Symbols The following symbols are used in the User's Manuals. Identifies instructions that must be observed to avoid physical injury, electric shock, or death. Identifies instructions that must be observed to prevent damage to the software or hardware, or system failures of the Product. Identifies important information required to understand operations or functions. Identifies additional information. Identifies referenced content. In online manuals, you can view the referenced content by clicking the links that are in green text. However, this action does not apply to the links that are in black text. Typographical Conventions The following typographical conventions are used throughout the User's Manuals. Commonly Used Conventions throughout the User's Manuals Δ Mark Indicates that a space must be entered between character strings. Example:.ALΔPIC010Δ-SC Character string enclosed by braces { } Indicates character strings that may be omitted. Example:.PRΔTAG{Δ.sheet name} Conventions Used to Show Key or Button Operations Characters enclosed by brackets [ ] When characters are enclosed by brackets in the description of a key or button operation, it indicates a key on the keyboard, a button name in a window, or an item in a list box displayed in a window. Example: To alter the function, press the [ESC] key. Conventions of a User-defined Folder User-defined folder name enclosed by parenthesis ( ) User definable path is written in a pair of parentheses. Example: (RS Project Folder)\SCS0101
v Drawing Conventions If the RS Project Folder is C:\MYRSPJT, the above path becomes C: \MYRSPJTSCS0101. Drawings used in the User's Manuals may be partially emphasized, simplified, or omitted for the convenience of description. Drawings of windows may be slightly different from the actual screenshots with different settings or fonts. The difference does not hamper the understanding of basic functionalities and operation and monitoring tasks. Integration with CENTUM SEE The Product can be integrated with CENTUM VP or CENTUM CS 3000. In the User's Manuals, the integration with CENTUM VP or CENTUM CS 3000 is referred to as "Integration with CENTUM." In the User's Manuals, the explanations for integrating the Product with CENTUM VP or CENTUM CS 3000, the glossary for various features of CENTUM VP is used instead of the glossary for CENTUM CS 3000. For example, the term "CENTUM VP System Alarm View" is used instead of "CENTUM CS 3000 System Alarm window." Nevertheless, if the features for integrating the Product with CENTUM VP and CENTUM CS 3000 are different, both features will be explained separately. For more information about the functions and usage of CENTUM VP components for integrating the Product with CENTUM VP, refer to: User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM VP For more information about the features and usage of CENTUM CS 3000 components for integrating the Product with CENTUM CS 3000, refer to: User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM CS 3000 Explanation of Hardware and Software Behaviors in the User's Manuals In the User's Manuals, system behaviors are explained assuming that the latest versions of YOKOGAWA software and hardware at the time of publication of the User's Manuals are installed. If additional precise information about the safety of legacy versions of software or hardware is required, a link to the corresponding explanation is provided. Please refer to the information according to your system. Station Types A safety control station (hereafter referred to as SCS) is named according to the type of the safety control unit used in it. Table Info-1 Names of SCS and Safety Control Unit Used SCSV1-S SCSP1-S SCSP2-S SCSU1-S Name of SCS SSC10S/SSC10D SSC50S/SSC50D SSC60S/SSC60D SSC57S/SSC57D Model of the safety control unit In the User's Manuals, the following abbreviations may be used to describe functions of these SCS as a whole.
vi SCSV1: Abbreviation of SCSV1-S SCSP1: Abbreviation of SCSP1-S SCSP2: Abbreviation of SCSP2-S SCSU1: Abbreviation of SCSU1-S
Copyright and Trademark Notices vii All Rights Reserved The copyright of the programs and online manuals contained in the software medium of the Software Product shall remain with YOKOGAWA. You are allowed to print the required pages of the online manuals for the purposes of using or operating the Product; however, reprinting or reproducing the entire document is strictly prohibited by the Copyright Law. Except as stated above, no part of the online manuals may be reproduced, transferred, sold, or distributed to a third party in any manner (either in electronic or written form including, without limitation, in the forms of paper documents, electronic media, and transmission via the network). Nor it may be registered or recorded in the media such as films without permission. Trademark Acknowledgments CENTUM, ProSafe, Vnet/IP, and STARDOM are registered trademarks of YOKOGAWA. Microsoft, Windows, Windows Vista, Windows Server, Visual Basic, Visual C++, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Adobe, Acrobat, and Adobe Reader are registered trademarks of Adobe Systems Incorporated. Ethernet is a registered trademark of Xerox Corporation. HART is a registered trademark of the HART Communication Foundation. Modicon and Modbus are registered trademarks of Schneider Electric SA. All other company and product names mentioned in the User's Manuals are trademarks or registered trademarks of their respective companies. TM or mark are not used to indicate trademarks or registered trademarks in the User's Manuals. Logos and logo marks are not used in the User's Manuals.
Toc-1 ProSafe-RS System Test Reference 4th Edition CONTENTS 1. Overview of ProSafe-RS system tests...1-1 1.1 Test procedure... 1-5 1.2 Overview of the test support functions... 1-6 1.3 Hardware/software environment...1-8 1.4 SCS project for the test...1-11 2. Logic simulation test operations... 2-1 3. SCS simulation tests...3-1 3.1 Engineering of SCS simulation tests...3-3 3.1.1 Engineering procedure before executing SCS simulation tests...... 3-5 3.1.2 Engineering procedure after SCS simulation tests...3-8 3.2 SCS Test Function window...3-10 3.2.1 Structure of the SCS Test Function window... 3-11 3.2.2 Procedure to launch the SCS Test Function window... 3-13 3.2.3 Procedure to close the SCS Test Function window...3-17 3.3 Execution of SCS simulation tests... 3-18 3.3.1 Operations unique to SCS simulators... 3-19 3.3.2 Preparation for executing SCS simulation tests... 3-24 3.3.3 Test support functions in SCS simulation tests... 3-27 3.3.4 SCS Maintenance Support Tool in SCS simulation tests... 3-31 3.3.5 Virtual HIS in SCS simulation tests... 3-34 3.3.6 Downloading to SCS simulators...3-35 3.4 Expanded test functions...3-36 3.4.1 Operation environment of the expanded test functions...3-38 3.4.2 Executing SCS simulation tests using the expanded test functions...... 3-41 3.5 Tests using multiple SCS simulators...3-47 3.5.1 Test environment for inter-scs safety communication/scs link transmission safety communication... 3-48 3.5.2 Testing inter-scs safety communication/scs link transmission safety communication...3-51 3.6 Testing CENTUM integration in virtual tests...3-53 4. Target tests... 4-1 4.1 Overview of target tests...4-2
Toc-2 4.2 Target test operation (in case online change download is not possible)......4-3 4.3 Target test operation (in case online change download is possible)......4-6 5. Test function tools...5-1 5.1 Test Project Creating Tool...5-2 5.2 Project Attribute Tool... 5-4
1. Overview of ProSafe-RS system tests SEE The purpose of the test functions of ProSafe-RS is to support testing operations of applications created by users. In ProSafe-RS tests, you can select a test target and check whether applications and devices operate correctly with respect to the target using the test support functions. For more information about overview of the test functions, refer to: 4.1, Types of Test in Engineering Guide (IM 32Q01C10-31E) <1. Overview of ProSafe-RS system tests > 1-1 Types and scopes of SCS test functions The SCS test functions include "target tests," where tests are executed using one or more actual SCSs, as well as "SCS simulation tests" and "logic simulation tests," where tests are executed using only a PC. SCS test functions Target test Use an actual SCS SCS simulation test (*1) Logic simulation test Use a PC only *1: It is possible to execute expanded tests using multiple PCs by adding an optional package. Figure 1-1 Classification of ProSafe-RS tests Scope of target tests In a target test, it is possible to test all applications if appropriate hardware is implemented and connected. Scope of SCS simulation tests An SCS simulation test includes the inter-scs safety communication function and the external connection function. With this test, you can test the integration between a virtual HIS of CENTUM VP and ProSafe-RS, on a PC. It is also possible to run multiple SCS simulators on a single PC to perform testing between multiple SCSs. Note that SCS simulation tests can only be executed in an environment integrated with CENTUM VP. IMPORTANT Do not execute SCS simulation tests using a PC connected to a control bus (V net and Vnet/IP) that actually executes plant operations.
<1. Overview of ProSafe-RS system tests > 1-2 TIP SCS simulation tests cannot be performed in combination with CS 3000. For SCSP2, they can be performed only when the system is combined with CENTUM VP R4.02 or later. If you cannot perform SCS simulation tests, perform target tests instead. The applications that can be run on SCS and FCS are different. For this reason, the following CENTUM test functions are not supported. Table 1-1 Functions not supported by ProSafe-RS I/O Disconnect/Connect Wiring Step Execution Function Profiler (CPU Load Ratio) Profiler (All Blocks Completion Times) Profiler (Data Access) Function Block One-shot Execution Message One-shot Output Change Scan Period Magnification Save/Load Snapshot Input/Output Error Test Other Station Communication Reception Data Setting FF Faceplate Block Test Overview Connects or disconnects each I/O module Simulates input data using output data Executes specified number of scans from paused condition Displays execution rates of basic control and SEBOL Detects scan omissions Saves history of access from other stations Operates a function block once Generates specified type of messages Extends virtual time without changing scan period Saves and restores database status Sets data status Presents access to other stations as normal Writes to tag data and sets data status Changes alarm status, mode and so on Scope of SCS simulation tests (expanded tests) When executing a simulation test of multiple SCSs using expanded test functions, it is possible to launch several SCS simulators on multiple PCs. This is used to test large-scale project configurations. TIP The SCS simulation test (expanded test) for SCSP2 can be performed only when the system is integrated with a CENTUM VP R4.02 or newer system. SEE For more information about expanded test functions, refer to: 3.4, Expanded test functions on page 3-36 Scope of logic simulation tests Logic simulation tests are restricted to testing application logics using logic simulators. Positioning of each test The tests are positioned as follows, based on the possible testing range.
<1. Overview of ProSafe-RS system tests > 1-3 Table 1-2 Test types and positioning Test type Target test SCS simulation test Logic simulation test Positioning Test of connection with actual field devices Test of connection with actual hardware Integration test of entire system Integration test of POUs Integration test of SCSs Test of CENTUM integration (test of connection with HIS and FCS) Test of each POU IMPORTANT In ProSafe-RS, target tests are mandatory. The user must eventually execute an operational test of all applications using target tests. However, in order to construct a proper environment for target tests, facilities, locations and time are required. Be sure to conduct sufficient application unit tests and integration tests using the simulators on PC in order to execute application debugging and operational tests efficiently. To perform simulation tests on PC, use either logic simulation tests or SCS simulation tests to their respective best uses, according to the test purpose. Builder definition and test ranges You can use the following tests to check the validity of definitions created on the SENG. Table 1-3 Items that can be checked in each test Builder definition Target test (*1) Validity of application logics of FBD, LD, etc. Definition of inter-scs safety communication binding SCS simulation test (*1) Yes Yes (*2) Yes (*2) Yes Yes No SCS link transmission definition Yes Yes No SCS link transmission wiring definition Yes Yes No I/O wiring Yes Yes No I/O parameter definition (module definition and channel definition) Definition of subsystem communication input/output Wiring of subsystem communication input/output Yes No No Yes No No Yes Yes No Modbus address definition Yes No No Tag Name Builder definition Yes Yes No Data setting and reference from FCS Yes Yes No Graphic definition created with HIS Yes Yes No Alarm priority level definition Yes Yes No Alarm processing table Yes Yes No Logic simulation test(*1)
<1. Overview of ProSafe-RS system tests > 1-4 *1: Yes: Can be tested No: Cannot be tested *2: Certain restrictions apply depending on the application.
1.1 Test procedure In ProSafe-RS tests, logic simulators and SCS simulators on PC should first be used to execute tests sufficiently, and then actual SCSs should be used to execute target tests. Test procedure using the test functions ProSafe-RS tests are performed according to the following procedure. Tests using SCS simulators can only be executed in CENTUM integration environments. Start <1.1 Test procedure > 1-5 1. Engineering and testing using PC only (Logic simulation test and SCS simulation test) Application logic definition Debugging in logic simulation tests Debugging CENTUM integration, inter-scs safety communication and SCS link transmission in SCS simulation tests 2. Testing using actual devices (Target test) Application logic tests CENTUM integration tests Inter-SCS safety communication and SCS link transmission tests Tests of communication interface for subsystem communication (can only be tested on actual devices) Modbus slave interface tests (can only be tested on actual devices) Testing I/O parameters (can only be tested on actual devices) Fault insertion tests (can only be tested on actual devices) Performance/reaction time tests (can only be tested on actual devices) Integration tests 3. FAT Figure 1.1-1 Test procedure End
1.2 Overview of the test support functions In ProSafe-RS test functions, the following test support functions are supported. These can be used for target tests, SCS simulation tests and logic simulation tests. Forcing function Application debug function Online monitoring function Test support functions ProSafe-RS provides functions for supporting various application tests, for the purpose of improving efficiency of debugging and testing applications. Among these, some functions are dedicated to application tests, while others are common with functions used during plant operation and maintenance work. The test support functions that can be used in each test type are as follows: Table 1.2-1 Items that can be tested in each test support function Test support function Forcing function Application debug function Online monitoring function *1: Yes: Can be tested Detail Lock/unlock (each variable) Variable value setting (each variable) Target test (*1) SCS simulation test (*1) Yes Yes Yes Yes Yes Yes I/O Lock Window Yes Yes(*2) No Communication I/O Lock Window SCS Link Transmission Lock Window Inter-SCS Communication Lock Window Execution mode specification (Cycle To Cycle / Real Time, Execute one Cycle) Break point setting/step execution Cycle time specification Display of variable values in SCS Manager <1.2 Overview of the test support functions > 1-6 Yes Yes (*2) No Yes Yes (*2) No Yes Yes (*2) No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Logic simulation test (*1) Overview The lock function fixes the data value of a variable to the current value. This function changes the data value of a variable to a value specified by the user. It is possible to lock input/output variables of each input/output module. In the locked state, it is possible to change values and statuses. It is possible to lock communication data of each communication I/O module. In the data locked state, it is possible to change values and statuses. It is possible to lock data of each communication station. In the data locked state, it is possible to change values and statuses. It is possible to lock data related to each communication station. In the data locked state, it is possible to change values and statuses. It is possible to pause or resume fixed period scan processing. It is also possible to execute a single scan while paused. It is possible to pause execution with any logic by setting break points in POUs written in Ladder and/or Structured Text. This function changes the scan period dynamically. This function displays the data value of an application logic variable.
<1.2 Overview of the test support functions > 1-7 No: Cannot be tested *2: In an SCS simulation test, multiple data values can be set at once.
1.3 Hardware/software environment This section explains the hardware/software environment required for executing each test. Logic simulation tests Logic simulation tests are performed on an SENG. Hardware environment A PC is required. The hardware requirements are the same as those for the PC on which the SENG runs. Software environment Apply the license for the ProSafe-RS safety system generation and maintenance function (CHS5100) to the PC. SCS simulation tests SEE To perform SCS simulation tests, an SENG set up for integration with CENTUM VP is required. Hardware environment <1.3 Hardware/software environment > 1-8 The hardware requirements are the same as those for the PC on which the SENG runs. For more information about hardware environment for using the expanded test functions, refer to: PC environment required for the expanded test functions on page 3-38 Software environment The software environment should comply with the specifications of the OS allowed on the PC on which the SENG runs. You need to install the control bus driver on the PC for running SCS simulation tests. Licenses of the following software packages must be granted to the PC: Table 1.3-1 Software environment required for SCS simulation tests: SCSP1/SCSV1 System Package name Model Remark ProSafe-RS Safety System Generation and Maintenance CHS5100 R1.03 or later CENTUM VP/CS 3000 Integration Engineering CHS5200 R1.03 or later CENTUM VP Standard Operation and Monitoring Function LHS1100/LHM1101 R4.01 or later Standard Builder Function LHS5100/LHM5100 R4.01 or later Test Function LHS5420/LHM5150 R4.01 or later Table 1.3-2 Software environment required for SCS simulation tests: SCSP2 System Package name Model Remark ProSafe-RS Safety System Generation and Maintenance CHS5100 R2.03 or later CENTUM VP/CS 3000 Integration Engineering CHS5200 R2.03 or later Continues on the next page
<1.3 Hardware/software environment > 1-9 Table 1.3-2 Software environment required for SCS simulation tests: SCSP2 (Table continued) System Package name Model Remark Standard Operation and Monitoring Function LHS1100/LHM1101 R4.02 or later CENTUM VP Standard Builder Function LHS5100/LHM5100 R4.02 or later Test Function LHS5420/LHM5150 R4.02 or later SEE For more information about software environment for using the expanded test functions, refer to: Software environment of the expanded test functions on page 3-38 SEE Environment required for SCS simulation tests SCS simulation tests can only be executed in an environment integrated with CENTUM VP. Up to 8 stations including SCS simulators and FCS simulators can be launched at the same time on a single PC. If you need to launch more, use the expanded test functions of CENTUM VP and execute tests on multiple PCs. However, the maximum number of simulators that can be launched on a PC decreases, depending on the capability of the CPU of the PC and the load caused by other running software. Note that this capacity is a logical restriction and does not provide any performance guarantees. For more information about capacity of SCS simulation tests, refer to: Capacity in 4.2, SCS Simulation Test in Engineering Guide (IM 32Q01C10-31E) Minimum configuration PC CENTUM VP ProSafe-RS Standard Builder Function Creation CENTUM project data CENTUM VP/CS 3000 Integration Engineering Standard Operation and Monitoring Function Copy test DB Safety System Generation and Maintenance Test Function SCS project Creation Figure 1.3-1 Test environment for single PC Since several simulators can be launched on a single PC, most application debugging tasks can be handled using a single PC. Tests related to referencing/setting data from an FCS can also be executed by launching the FCS simulator. However, only one SCS Manager can be used at the same time on a PC. Tests of inter-scs safety communication and SCS link transmission can be executed by switching between target SCSs on SCS Manager. When testing multiple SCSs, it is recommended to use the expanded test functions on two or more PCs so that the tests are performed more efficiently.
<1.3 Hardware/software environment > 1-10 PC SCS Manager Launch Operation and Monitoring SCS simulator SCS 0101 SCS simulator SCS 0102 FCS simulator FCS 0103 Inter-SCS safety communication Data reference/setting SCS link transmission Figure 1.3-2 SCS simulation test with single PC Target tests To execute a target test, an SENG is required along with the actual devices to be tested. Hardware environment The hardware requirements are the same as those for the PC on which the SENG runs. The SCS to be tested is also required. Software environment Install the ProSafe-RS Safety System Generation and Maintenance function (CHS5100). In addition, the SENG software package required for engineering the test target SCS is necessary.
1.4 SCS project for the test In order to execute a test, it is necessary to set up an SCS project for test. The attributes for SCS projects and test types that can be executed in each project vary. It is thus necessary to set project attributes according to test phase. It is also necessary to generate and create a database for each test, which is done by setting SCS resource properties according to the test to be executed. SCS project attributes SEE The following three attributes can be set for SCS projects. Default project Current project User-defined project Default project The default attribute is set for an SCS project which is newly created in SCS Manager. Current project When offline download is successfully completed for a default project, the attribute of the SCS project is changed from default to current. SCS projects on which SCS actual operations are performed are specified as current projects. User-defined project A user-defined project is an SCS project created by the Test Project Creating Tool in order to execute SCS simulation tests. Generally, it is created to execute an SCS simulation test on an SCS project for which offline download has been executed. For more information about Test Project Creating Tool, refer to: 5.1, Test Project Creating Tool on page 5-2 For more information about project attributes, refer to: <1.4 SCS project for the test > 1-11 SCS Project Attribute in 1.3, Type of Project in Engineering Guide (IM 32Q01C10-31E) Test database Test databases are related to individual tests in the following manner. A target test is executed using the database used for actual operation of SCSs. An SCS simulation test is executed using the database for SCS simulation tests. A logic simulation test can be executed using both the database for SCS simulation tests and the database used for actual operation. Creation of test database To create a test database, specify the Target name in Resource Properties of SCS Manager and execute a build operation. In the case of actual operation of SCS (target tests possible): SCS_TARGET In the case of SCS simulation tests: SCS_SIMULATOR
SEE For more information about Resource Properties dialog box, refer to: <1.4 SCS project for the test > 1-12 Setting a Resource in 3.1.1, SCS Project Creation Procedure in Engineering Reference (IM 32Q04B10-31E) Operations that can be executed for each SCS project attribute SEE The types of tests that can be executed vary depending on the SCS project attributes. The following section explains the tests that can be executed for each SCS project attribute setting, along with the corresponding operational procedures. Default project When the default attribute is set to the SCS project, logic simulation tests and SCS simulation tests can be executed. To execute an SCS simulation test, first set the Target name of Resource Properties to SCS_SIMULATOR and then perform a build operation. When both types of tests have been completed, set the Target name of Resource Properties to SCS_TARGET, perform a build operation and then offline download operation on an SCS. Current project When the current attribute is set to the SCS project, logic simulation tests and target tests can be executed. SCS simulation tests cannot be executed. When the current attribute is set to the SCS project, the Target name cannot be changed. To execute SCS simulation tests, use the Test Project Creating Tool to generate a userdefined project. User-defined project When the user-defined project attribute is set, logic simulation tests and SCS simulation tests can be executed. Target tests cannot be executed. When the user-defined project attribute is set, it is not possible to communicate with the actual SCS. To execute an SCS simulation test, first set the Target name of Resource Properties to SCS_SIMULATOR and then perform a build operation. If the Target name of Resource Properties is SCS_TARGET, only logic simulation tests can be executed. When the user-defined project attribute is set, offline download cannot be performed. When a test using a simulator is completed and a target test is to be executed, it is necessary to reflect the data of the user-defined project to the current project. For more information about procedure for applying user-defined project information to a current project, refer to: Operations required after SCS simulation tests (user-defined project) on page 3-8 Specific test procedures This section explains the practical test procedures using two examples: a new SCS project and existing SCS project.
<1.4 SCS project for the test > 1-13 New SCS project SEE The project attribute of a newly created SCS project is automatically set to default. 1. Using the default project, execute a logic simulation test. 2. Change the Target name from SCS_TARGET to SCS_SIMULATOR to perform a build operation and execute an SCS simulation test. 3. To perform offline download to the actual SCS after an SCS simulation test is completed, change the Target name from SCS_SIMULATOR to SCS_TARGET and build again. 4. After offline download is performed with the default project attribute, the project attribute changes to current. SCS project to which offline download has been executed The project attribute of an SCS project to which offline download has already been completed is set to current. The procedure to perform engineering tasks on a current project and execute an SCS simulation test on a modified project, is as follows: 1. Use the Test Project Creating Tool to generate a user-defined project. 2. Build the user-defined project. 3. Execute an SCS simulation test with the user-defined project. 4. Export the files of current project that will be needed in the current project. 5. Import the exported files that are needed into a current project. For more information about specific engineering procedures for SCS simulation test projects, refer to: 3.1, Engineering of SCS simulation tests on page 3-3
2. Logic simulation test operations SEE You can use Logic simulator to test application logics in SCS Projects of all attributes. Logic simulator cannot run simultaneously with the SCS simulator. Use the Logic simulator to test mainly programs, function blocks, or functions (that is POU). This chapter describes how to operate Logic simulation tests. For more information about important points when testing, refer to: 4.4, Precautions for Tests in Engineering Guide (IM 32Q01C10-31E) <2. Logic simulation test operations > 2-1 Generate an SCS database for a logic simulation test After creating an application logic, execute a build operation on the application logic to generate an SCS database. An SCS database for the logic simulator is automatically created at the same time. IMPORTANT Right click the resource title bar of the Link Architecture View, and choose [Properties] from the pop-up menu. And then confirm that the [Code for simulation] on the "Code" tab of Resource Properties dialog box is checked. And then start to generate the SCS database. SEE For more information about build operations, refer to: Building SCS Project in 5.4, Procedure after Creating Application Logic in Engineering Reference (IM 32Q04B10-31E) Start a logic simulation test In order to start a logic simulation test, go to the logic simulation test mode in SCS Manager. Open the SCS project to be tested in SCS Manager and select [Simulation] of [Debug] menu in SCS Manager. The SCS simulator automatically launches and then goes to the logic simulation mode. Debug and test Debug and test the applications that run on the logic simulator using the application debug, forcing and online monitoring functions. You can debug and test application logic by using application debug, forcing and online monitoring functions. The forcing function is available from Dictionary View and Multi-Language Editor. SCS maintenance support tool cannot be used for logic simulation test.
SEE For more information about application debug function, refer to: "Debugging" under "Workbench" in the Workbench User's Guide For more information about Dictionary View, refer to: "Dictionary View" under "Workbench" in the Workbench User's Guide For more information about Multi-Language Editor, refer to: "Multi-Language Editor" under "Workbench," "Language Editor" in the Workbench User's Guide. For more information about online monitoring, refer to: <2. Logic simulation test operations > 2-2 Online Monitoring in Relationships among Functions of SCS Maintenance Support Tool in 3., SCS Maintenance Support Tool in Utilities and Maintenance Reference (IM 32Q04B20-31E) Check items in logic simulation tests The following table lists information about tests that you can run in logic simulation tests. Table 2-1 Items checked in logic simulation tests Items to be tested Generic application logics Application enabling operations and monitoring from HIS (such as Override FB, Manual operation FB, and External communication FB) Application logics that use System FB Inter-SCS safety communications/scs link transmission FCS application that views/sets data in SCS Graphic windows related to SCS Communication input /output tests SCS start actions Performance test Actions on abnormal calculation Logic simulation tests Using Forcing function, lock the input variable(s) and internal variable(s), change the values, and check the behavior of the logic using online monitoring. Operations and monitoring from HIS are not available, so check the logic by using Forcing function on the internal variable(s). SCS Simulation test recommended. Only normal behavior can be checked. SCS Simulation test and Target test recommended. Check the logic by using Forcing function on the internal variable(s). SCS Simulation test recommended. Check the logic by using Forcing function on the internal variable(s). SCS Simulation test recommended. SCS Simulation test recommended. Conduct tests by using Forcing function on the output parameters. For the communications with subsystem devices, conduct Target tests. SCS Simulation test recommended. The feature for Automatic scan period extension is disabled. It is recommended to test the performance on the actual SCS. In the logic simulation test, the following actions occur when there is an abnormal calculation. These differ from the actions on the actual unit. On division by zero and accessing the outside of an array All the POUs will pause (change to Cycle To Cycle mode.) Operation of the POUs needs to be resumed using SCS Manager. On overflow in the floating-point calculation The calculation result becomes infinity. The calculations that use this abnormal result will produce abnormal results. However, POU will not stop. On overflow in type conversion The calculation result becomes abnormal. If a REAL value outside the range of DINT is passed to ANY_TO_DINT, a negative maximum value will result. However, the POU will not stop.
<2. Logic simulation test operations > 2-3 End the logic simulation test Select [Stop Simulation] of [Debug] menu in SCS Manager or Multi-Language Editor. The logic simulator exits automatically and the mode transits from the logic simulation mode to the edit mode.
3. SCS simulation tests An SCS simulation test is executed by launching SCS simulators that simulate operations of SCSs on a PC. SCS simulation tests can only be executed in an environment integrated with CENTUM VP. In systems that are configured only with ProSafe-RS, SCS simulation tests cannot be executed. Use logic simulation tests and target tests instead. This section explains engineering procedures for SCS simulation tests, along with the test procedures and test support functions that can be used during testing. What is SCS simulation test? This section provides an overview of SCS simulation tests and explains items that can be checked with SCS simulation tests. Intended use of SCS simulators SCS simulators can be used for the following two purposes. Debugging applications In an SCS simulation test, it is possible to use SCS simulators to debug SCS applications without using actual SCS hardware or control bus communication cards. Note that, since SCS simulators do not have the input/output interface with the field devices, they cannot be used for the purpose of controlling actual plants. Plant training system It is possible to incorporate SCS simulators in a plant training system created with interfaces provided by the Exatif CS 3000 package, thus achieving a training system integrating the CENTUM and ProSafe-RS systems. The SCS simulator has an interface function for the plant operation training system. For information regarding the function for interfacing with the plant operation training system, refer to the manual for the plant operation training simulator. Overview of SCS simulator functions <3. SCS simulation tests > 3-1 An SCS simulator simulates operations of an SCS on a PC. Since no actual hardware is used, it always simulates normal status for areas related to input/output processing, but other than this, it operates in almost exactly the same way as an actual SCS. It is possible to use engineering functions and test support functions provided on a PC for SCS simulators. It is possible to operate and monitor an SCS simulator via the operation and monitoring functions of CENTUM (virtual HIS). It is possible to perform communication among multiple SCS simulators as well as with FCS simulators. A PC on which SCS simulators are running cannot communicate with actual SCS and FCS. SCS simulators are unable to communicate with actual SCSs. For this reason, tests that involve both actual SCSs and SCS simulators cannot be performed. An SCS simulator is launched from the SCS Test Function window. The SCS Test Function window can be launched either from SCS Manager or System View. IMPORTANT Do not execute logic simulation tests while running SCS simulators.
<3. SCS simulation tests > 3-2 Items that can be checked with SCS simulation tests The following table lists information about tests that you can run in SCS simulation tests. Table 3-1 Items that can be checked in SCS simulation tests Items to be tested Generic application logics Application enabling operations and monitoring from HIS (such as Override FB, Manual operation FB, and External communication FB) Application logics that use System FB Inter-SCS safety communication SCS link transmission FCS application that views/sets data in SCS Graphic windows related to SCS Communication input /output tests SCS start actions SCS simulation test Test input/output variables upon setting initial data values using the data value batch setting function in the I/O Lock Window. Check operations using online monitoring. It is possible to use a virtual HIS to execute the same tests as when using actual SCSs. After launching SCS simulators, call and operate a faceplate using the tag name as the key from a virtual HIS. Operations of system FB can only be checked partly with target tests. The Inter-SCS Communication Lock Window is available. Checking of operations including communication is possible by launching multiple SCS simulators. If SCS simulators to communicate with are not launched, communication results become abnormal. Tests involving a single SCS simulator are performed using the same procedure as for logic simulation tests. The SCS Link Transmission Lock Window is available. Checking of operations including communication is possible by launching multiple SCS simulators. If SCS simulators to be communicated with are not launched, communication results become abnormal. Tests involving a single SCS simulator are performed using the SCS Link Transmission Lock Window. Execute a test by launching FCS simulator at the same time. Graphic views not related to hardware can be tested from a virtual HIS. Execute a test using the Communication I/O Lock Window. Communication with subsystems shall be checked using target tests. Starting up processes can be tested by rebooting an SCS simulator. Outline of SCS simulation test procedure An SCS simulation test is executed according to the following procedure: 1. Engineering of an SCS project 2. Engineering of a CENTUM project 3. Calling the SCS Test Function window 4. Setting initial data to an SCS simulator 5. Executing a test using the test support functions 6. Engineering after testing
<3.1 Engineering of SCS simulation tests > 3-3 3.1 Engineering of SCS simulation tests In order to execute an SCS simulation test, it is necessary to perform engineering tasks in preparation for the test. After completion of the test, it is necessary to reflect the test result in the actual SCS and engineering tasks for this are thus required as well. This section explains the engineering procedures to be performed before and after executing an SCS simulation test. Overview of SCS simulation test procedure The procedure for launching the SCS Test Function window and executing an SCS simulation test is as follows. ProSafe-RS Start CENTUM Start Create a test project Create a test project Set CENTUM project path Build Run analyzers Launch the SCS Test Function window Create SCS tag list Test Test Close the SCS Test Function window Perform engineering tasks after test End End Figure 3.1-1 Procedure for executing an SCS simulation test The "create a test project" and "perform engineering tasks after test" steps in the previous figure are different for new SCS projects and SCS projects for which an offline download has already been performed. SCS simulation test procedure (newly created SCS project) The attribute of a newly created SCS project is set to default. An SCS simulation test using a SCS project with default attribute is performed according to the following procedure. 1. Creating a new SCS project and creating engineering data 2. Creating a test project on the CENTUM side 3. Changing the target name 4. Setting of a CENTUM project folder path 5. Build 6. Running analyzers
7. Creating an SCS tag list on the CENTUM side 8. Launching the SCS Test Function window 9. Debugging and executing a test 10. Ending debugging 11. Closing the SCS Test Function window 12. Changing target names 13. Build 14. Running analyzers 15. Offline download to the actual SCS SCS simulation test procedure (SCS project for which offline download has been completed) The attribute of an SCS project for which offline download has been completed is set to current. It is not possible to execute an SCS simulation test with a current SCS project. Instead, generate a user-defined project with the Test Project Creating Tool and execute an SCS simulation test with the generated project. 1. Creating a test SCS project (using the Test Project Creating Tool) 2. Creating a test project on the CENTUM side 3. Build 4. Running analyzers 5. Creating an SCS tag list on the CENTUM side 6. Launching the SCS Test Function window 7. Debugging and executing a test 8. Ending debugging 9. Closing the SCS Test Function window 10. Exporting project data using a user-defined project 11. Importing and reflecting test results to the current project <3.1 Engineering of SCS simulation tests > 3-4
3.1.1 Engineering procedure before executing SCS simulation tests This section explains engineering tasks required on the ProSafe-RS side as well as the CENTUM side in order to execute an SCS simulation test. Engineering tasks required to execute an SCS simulation test are different for newly created SCS projects and SCS projects for which offline download to an SCS has already been completed. Each procedure is explained in the following. Step 1 Creating a test SCS project SEE <3.1 Engineering of SCS simulation tests > 3-5 The procedure for creating test SCS projects is different for newly created SCS projects and SCS projects for which offline download to an SCS has already been completed. In the case of a newly created SCS project (default project) The attribute of a newly created SCS project is set to default until offline download to an SCS is completed. With a default project, it is possible to execute an SCS simulation test without creating a test SCS project. For more information about the procedure for creating a new SCS project, refer to: 3.1, Creation of New SCS Projects in Engineering Reference (IM 32Q04B10-31E) In the case of a project for which offline download to an SCS has been completed (current project) It is not possible to execute an SCS simulation test with a current project. It is thus necessary to generate a user-defined project for an SCS simulation test. To generate a user-defined project, use the Test Project Creating Tool. TIP An SCS simulation test cannot be executed with SCS projects created with the version earlier than R1.03. Create SCS projects again. SEE For more information about Procedure for creating a user-defined project using the Test Project Creating Tool, refer to: 5.1, Test Project Creating Tool on page 5-2 Step 2 Creating a test project on the CENTUM side SEE In order to execute an SCS simulation test, an SCS must have been registered with System View of a CENTUM project on a PC on which an SCS simulator is launched. The attribute set for the CENTUM project must be default or user-defined. When no test target SCS is created in a CENTUM project If no SCS to be tested is created in the target CENTUM project, an SCS to be tested must be created with System View. For more information about the procedure to create an SCS with System View, refer to: 2.2.1, SCS creation in Integration with CENTUM VP/CS 3000 (IM 32Q01E10-31E)