S04B3021

Users
Manual
ProSafe-RS
System Test
Reference
IM 32S04B30-21E
IM 32S04B30-21E
3rd Edition
Introduction
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 32S01C10-21E) first. Read the appropriate sections of this manual to examine related
information, learn about operation details and obtain deeper understanding.
The structure of this manual is shown below.
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. IM 32S04B30-21E (CD)

3rd Edition : Dec. 2009 (YK)
All Rights Reserved Copyright 2008, Yokogawa Electric Corporation
IM 32S04B30-21E
3rd Edition : Dec.22,2009-00
ii
ProSafe-RS Document Map

Safety System
Safety Manual
Engineering
Guide
IM 32S01S10-21E
IM 32S01C10-21E
Software
Safety Control Station
Reference
IM 32S03B10-21E
Integration with
CENTUM VP/CS 3000
Open Interfaces
IM 32S01E10-21E
IM 32S05B10-21E
Engineering
Reference
Utilities and
Maintenance
Reference
IM 32S04B20-21E
Messages
IM 32S02B10-21E
Integration with
FAST/TOOLS
Workbench Users Guide
IM 32S04B10-21E
ProSafe-RS
System Test
Reference
IM 32S04B30-21E
IM 32S56H20-21E
Hardware
Vnet/IP
Safety Control
Stations
(Hardware)
IM 32S06C10-21E
Communication
Devices
ProSafe-RS
Vnet/IP
IM 32S06H10-21E
IM 32S56H10-21E
Installation
Installation
Manual
Software Help
IM 32S01C50-21E
Read Me First
IM 32S04B30-21E
2nd Edition : Dec.15,2008-00
iii
Safety Precautions
n Safety, Protection, and Modification of the Product
In order to protect system controlled by this product, the product itself and ensure safe
operation, observe the safety precautions described in this users manual. We assume no
liability for safety if users fail to observe these instructions when operating the product.
You must use this product according to the instructions described in user manuals. If not,
protective functions of this product may not work as expected.
If any protection or safety circuit is required for system controlled by the product or for the
product itself, prepare it separately.
Be sure to use the parts approved by Yokogawa Electric Corporation (hereafter simply
referred to as YOKOGAWA) when replacing parts or consumables.
Modification of the product is strictly prohibited.
The following symbols are used on the product and in this user manual to indicate that
safety precautions are required:
Indicates that user must take caution. The symbol on the equipment refers the user to the
relevant manual to avoid potentially hazardous situations that may result in injury or death.
The symbol appears next to the cautionary information in user manuals required to avoid
harm to personnel and to the equipment.
Indicates a protective grounding terminal. Before using the product, ground the terminal.
Indicates a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates that main switch is ON.
Indicates that main switch is OFF.
IM 32S04B30-21E
1st Edition : May 30,2008-00
iv
n Notes on Handling User Manuals
Please hand over user manuals to your end users so that they can have them on hand for
convenient reference.
Please read the user manuals thoroughly before using the product.
The purpose of these user manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
YOKOGAWA reserves the right to make improvements in the user manuals and product at
any time, without notice or obligation.
If you have any questions, or you find mistakes or omissions in the user manuals, please
contact our sales representative or your local distributor.
n Warning and Disclaimer

The product is provided on an as is basis. YOKOGAWA shall have neither liability nor
responsibility to any person or entity with respect to any direct or indirect loss or damage arising
from using the product or any defect of the product that YOKOGAWA can not predict in advance.
n Notes on Software
YOKOGAWA makes no warranties, either expressed or implied, with respect to the
softwares merchantability or suitability for any particular purpose, except as specified in the
terms of warranty.
This software may be used on one machine only. If you need to use the software on another
machine, you must purchase another copy of the software.
It is strictly prohibited to reproduce the product except for the purpose of backup.
Store the CD-ROM (the original medium) in a safe place.
It is strictly prohibited to perform any reverse-engineering operation, such as reverse
compilation or reverse assembling on the product.
No part of the product may be transferred, converted or sublet for use by any third party,
without prior written consent from YOKOGAWA.
IM 32S04B30-21E
Documentation Conventions
n Typographical Conventions
The following typographical conventions are used throughout the user manuals:
l Commonly used Conventions throughout User manuals:

Character strings in the following font and style:
Indicate that user must enter them in the relevant field or text box in the context.
Example:

FIC100.SV=50.0
Mark:
Indicates a space between character strings that must be entered.
Example: Calling the tuning view with the tag name of S0001 on HIS (Human Interface Station of
the integrated CENTUM).

S0001 TUN
Character string enclosed by brackets ({ }):

Indicates an option that can be omitted.
Example: Parameters for calling the tuning view on HIS

Tagname TUN {-Window size} {=Display position}
l Conventions used to show Key or Button Operations:

Characters enclosed by square brackets ([ ]):
Characters enclosed by square brackets within any description of a key or button operation,
indicate either a key on the keyboard, a button name on a window, or an item displayed on a
window.
Example:

Click the [OK] button.
l Conventions of User Defined Folder

User-Defined Folder Name
If the path of a folder can be defined by users, it is written within parentheses.
Example: (RS Project Folder) \SCS0101
If the RS Project Folder is C: \MYRSPJT, the above path becomes: C: \MYRSPJT\SCS0101
IM 32S04B30-21E
vi
n Symbol Marks
Throughout this user manual, you will find that several types of symbols are used to identify
different sections of text. This section describes these icons.
CAUTION:

Indicates instructions that must be observed in order to prevent physical injury and death of
operator.
WARNING :

Indicates instructions that must be observed in order to prevent software or hardware from
being damaged or system from becoming faulty.
IMPORTANT :

Indicates important information required to understand operations or functions.
TIP:

Indicates additional information.
SEE :
ALSO

Indicates a source to be referred to.
Clicking a reference displayed in green can call up its source, while clicking a reference
displayed in black cannot.
n Drawing Conventions
Some drawings in the user manual may be partially emphasized, simplified, or omitted, for the
convenience of description.
Note that screen images in user manuals may be slightly different from the actual ones (for
example, display positions and case differences), and some show only example images.
n Integration with CENTUM

ProSafe-RS can be used by integrating with CENTUM VP or CENTUM CS 3000. In the Users
Manuals of ProSafe-RS, the integration with CENTUM VP or CENTUM CS 3000 is referred to as
Integration with CENTUM.
For the same features of CENTUM VP and CENTUM CS 3000 that have different feature names,
the name used in CENTUM VP will be referred to in the explanations. (For example, CENTUM
CS 3000 System Alarm Window and CENTUM VP System Alarm View have the same functions,
but only System Alarm View will be referred to when explaining this feature.) Nevertheless,
if there is any difference in functionality according to whether ProSafe-RS is integrated with
CENTUM VP or CENTUM CS 3000, the feature will be explained separately for both cases.
SEE
ALSO
For information about the functions and usage of CENTUM VP components, see CENTUM VP Users
Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
For information about the functions and usage of CENTUM CS 3000 components, see CENTUM CS 3000
Users Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
IM 32S04B30-21E
vii
n Regarding the Descriptions on System Actions
In this document, the integrations with the latest software and hardware products of Yokogawa up
to the publishing of this document will be explained.
If the important software or hardware safety features of the previous versions are not described in
this document, the links for the descriptions will be indicated in this document. Readers can go to
the linked descriptions according to the used systems.
n Regarding the Station Types

The safety control stations (SCS) are named in accordance with the combination of installed
CPU node (SSCX0S/SSCX0D) and CPU modules (SCP4X1). The names are as follows:
SCSV1-S: SSC10S/SSC10D SCS with SCP401 modules installed in CPU node
SCSP1-S: SSC50S/SSC50D SCS with SCP451 modules installed in CPU node
SCSP2-S: SSC60S/SSC60D SCS with SCP461 modules installed in CPU node
In order to explain the SCS features in details, the following abbreviations may be used when
describe all types of SCS or the specific types of SCS.
SCS: Stands for all types of SCS
SCSV: Stands for the SCS with V net connection (same as SCSV1-S)
SCSP: Stands for the SCS with Vnet/IP connection (same as SCSP1-S or SCSP2-S)
SCSV1: Abbreviation of SCSV1-S
SCSP1: Abbreviation of SCSP1-S
SCSP2: Abbreviation of SCSP2-S
IM 32S04B30-21E
viii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the DVD-ROM or CD-ROM shall
remain in Yokogawa.
You are allowed to print out the required pages of the online manuals for using the product,
however, you are not allowed to print out the entire document.
Except as stated above, no part of the online manual may be reproduced, either in electronic
or written form, registered, recorded, transferred, sold or distributed (in any manner including
without limitation, in the forms of paper documents, electronic media, films or transmission via the
network).
n Trademark Acknowledgments
CENTUM, ProSafe, Vnet/IP and STARDOM are registered trademarks of YOKOGAWA.
Microsoft, Windows, Windows Vista, Visual Basic, Visual C++ and Visual Studio are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
Adobe, Acrobat and Acrobat Reader are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Ethernet is a registered trademark of XEROX Corporation.
Modicon and Modbus are registered trademarks of Schneider Electric SA.
PLC is a registered trademark of Rockwell Automation, Inc.
HART is a registered trademark of the HART Communication Foundation.
All other company and product names mentioned in this users manual are trademarks or
registered trademarks of their respective companies.
We do not use TM or mark to indicate those trademarks or registered trademarks used in
this users manual.
IM 32S04B30-21E
Toc-1
ProSafe-RS
System Test Reference
IM 32S04B30-21E 3rd Edition
CONTENTS
1.
Overview of ProSafe-RS System Tests................................................... 1-1

1.1
Test Procedure................................................................................................... 1-4
1.2
Overview of the Test Support Functions......................................................... 1-5
1.3
Hardware/Software Environment..................................................................... 1-6
1.4
SCS Project for the Test.................................................................................. 1-10
2.
Logic Simulation Test Operations........................................................... 2-1
3.
SCS Simulation Tests............................................................................... 3-1

3.1
3.2
3.3
3.4
3.5
3.6
Engineering of SCS Simulation Tests............................................................. 3-4

3.1.1
Engineering Procedure before Executing SCS Simulation Tests....... 3-6
3.1.2
Engineering Procedure after SCS Simulation Tests......................... 3-10
SCS Test Function Window ........................................................................... 3-12

3.2.1
Structure of the SCS Test Function Window.................................... 3-13
3.2.2
Procedure to Launch the SCS Test Function Window..................... 3-15
3.2.3
Procedure to Close the SCS Test Function Window........................ 3-20
Execution of SCS Simulation Tests............................................................... 3-21

3.3.1
Operations Unique to SCS Simulators............................................. 3-21
3.3.2
Preparation for Executing SCS Simulation Tests............................. 3-26
3.3.3
Test Support Functions in SCS Simulation Tests ............................ 3-29
3.3.4
SCS Maintenance Support Tool in SCS Simulation Tests................ 3-34
3.3.5
Virtual HIS in SCS Simulation Tests................................................. 3-37
3.3.6
Downloading to SCS Simulators...................................................... 3-38
Expanded Test Functions............................................................................... 3-39

3.4.1
Operation Environment of the Expanded Test Functions................. 3-41
3.4.2
Executing SCS Simulation Tests Using the Expanded

Test Functions................................................................................... 3-44
Tests Using Multiple SCS Simulators............................................................ 3-50

3.5.1
Test Environment for Inter-SCS Safety Communication/

SCS Link Transmission Safety Communication............................... 3-50
3.5.2
Testing Inter-SCS Safety Communication/

SCS Link Transmission Safety Communication............................... 3-54
Testing CENTUM Integration in Virtual Tests............................................... 3-56
IM 32S04B30-21E
Toc-2
4.
5.
Target Tests................................................................................................ 4-1

4.1
Overview of Target Tests................................................................................... 4-1
4.2
Target Test Operation (In Case On-line Change Download is not

Possible)............................................................................................................. 4-2
4.3
Target Test Operation (In Case On-line Change Download is Possible)..... 4-5
Test Function Tools................................................................................... 5-1

5.1
Test Project Creating Tool................................................................................. 5-1
5.2
Project Attribute Tool......................................................................................... 5-3
IM 32S04B30-21E
1.
1-1
<1. Overview of ProSafe-RS System Tests>
Overview of ProSafe-RS System

Tests
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.
In the case of SCS projects integrated with CENTUM VP/CS 3000, it is possible to execute
tests that also involve the CENTUM VP/CS 3000 (hereinafter referred to as CENTUM) test
function.
SEE
ALSO
For the overview of test functions, see the following:

4.1, Types of Test of the Engineering Guide (IM 32S01C10-21E)
n 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
SCS simulation test (*1)
Use an actual SCS

Use a PC only

010001E.ai
*1:
It is possible to execute expanded tests using multiple PCs by adding an optional package.
Figure Classification of ProSafe-RS Tests
l Scope of Target Tests

In a target test, it is possible to test all applications if appropriate hardware is implemented and
connected.
l Scope of SCS Simulation Tests

An SCS simulation test can test inter-SCS safety communication and external connection
functions; with this test, it is possible to execute integration test with virtual HISs of CENTUM on
a PC. It is also possible to run multiple SCS simulators on a single PC to execute integration test
for multiple SCSs. Note, however, that a CENTUM integration environment is required to execute
SCS simulation tests.
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.
TIP
The SCS simulation test for SCSP2 can be performed only when the system is integrated with a CENTUM VP
R4.02 or newer system.
IM 32S04B30-21E
TIP
1-2
Since applications that can be executed on SCS and FCS are different, the following test functions of CENTUM
are not supported in ProSafe-RS.
Table
Functions not Supported by ProSafe-RS

Function
Overview
I/O Disconnect/Connect
Connects or disconnects each I/O module
Wiring
Simulates input data using output data
Step Execution
Executes specified number of scans from paused condition
Profiler (CPU Load Ratio)
Displays execution rates of basic control and SEBOL
Profiler (All Blocks Completion Times)
Detects scan omissions
Profiler (Data Access)
Saves history of access from other stations
Function Block One-shot Execution
Operates a function block once
Message One-shot Output
Generates specified type of messages
Change Scan Period Magnification
Extends virtual time without changing scan period
Save/Load Snapshot
Saves and restores database status
Input/Output Error Test
Sets data status
Other Station Communication Reception Presents access to other stations as normal

Data Setting
Writes to tag data and sets data status
FF Faceplate Block Test
Changes alarm status, mode and so on
l 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.
SEE
ALSO
For more information about expanded test functions, see the following:
3.4, Expanded Test Functions
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.
l Scope of Logic Simulation Tests

Logic simulation tests are restricted to testing application logics using logic simulators.
IM 32S04B30-21E
1-3
n Positioning of Each Test

Each test is positioned as follows according to the scopes in which tests are possible.
Table
Test Types and Positioning

Test type
Positioning
Target test
Test of connection with actual field devices

Test of connection with actual hardware
Integration test of entire system
SCS simulation test
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.
l Builder Definition and Test Ranges

The validity of definitions made in SENG can be checked by the appropriate test listed below.
Table
Items that can be Checked in Each Test

Builder definition
Target
SCS simulation
Logic simulation
Validity of application logics of FBD, LD, etc.
X (*1)
X (*1)
Definition of inter-SCS safety communication binding
SCS link transmission definition
SCS link transmission wiring definition
I/O wiring
I/O parameter definition (module definition and channel

definition)
Definition of subsystem communication input/output
Wiring of subsystem communication input/output
Modbus address definition
Tag Name Builder definition
Data setting and reference from FCS
Graphic definition created with HIS
Alarm priority level definition
Alarm processing table
X:
Can be tested
Blank: Cannot be tested
*1:
Certain restrictions apply depending on the application.
IM 32S04B30-21E
1.1
1-4
<1.1 Test Procedure>
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.
n Test Procedure Using the Test Functions

Tests of ProSafe-RS shall be performed according to the following procedure. Tests using SCS
simulators can only be executed in CENTUM integration environments.
Start
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
End
010101E.ai
Figure Test Procedure
IM 32S04B30-21E
1.2
1-5
<1.2 Overview of the Test Support Functions>
Overview of the Test Support Functions
In test functions of ProSafe-RS, the following test support functions are provided, which
can be used for target tests, SCS simulation tests and logic simulation tests.
Forcing function
Application debug function
Online monitoring function
n 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 listed below.
Table
Items that can be Tested in Each Test Support Function
Test support
function
Detail
Application debug
function
Logic
simulation
Overview
Lock/unlock
(each variable)
The lock function fixes the data value of a

variable to the current value.
Variable value setting

(each variable)
This function changes the data value of a

variable to a value specified by the user.
X
(*1)
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.
X
(*1)
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.
SCS Link Transmission

Lock Window
X
(*1)
Inter-SCS
Communication Lock
Window
X
(*1)
Execution mode
specification
(Cycle To Cycle / Real
Time, Execute one
Cycle)
It is possible to pause or resume fixed period

scan processing. It is also possible to execute
a single scan while paused.
Break point setting/step

execution
It is possible to pause execution with any

logic by setting break points in POUs written
in Ladder and/or Structured Text.
Cycle time specification
This function changes the scan period

dynamically.
This function displays the data value of an

application logic variable.
I/O Lock Window
Forcing function
SCS
Target simulation
Communication I/O
Lock Window
Display of variable
Online monitoring
values in SCS
function
Manager
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.
X:
Can be tested
Blank: Cannot be tested
*1:
In an SCS simulation test, multiple data values can be set at once.
IM 32S04B30-21E
1.3
1-6
<1.3 Hardware/Software Environment>
Hardware/Software Environment
This section explains the hardware/software environment required for executing each
test.
n Logic Simulation Tests

Logic simulation tests are executed on a general-purpose PC on which SENG functions are
installed.
l Hardware Environment
A general-purpose PC is required. The hardware requirements are the same as for a generalpurpose PC on which SENG is installed.
l Software Environment
Install the ProSafe-RS Safety System Generation and Maintenance Function Package
(CHS5100).
n SCS Simulation Tests

SCS simulation tests are executed on a general-purpose PC on which SENG functions are
installed. To execute an SCS simulation test, CENTUM integration environment is required.
A standard PC is required. PC environment for Windows Vista/Windows Server 2008 is the same
as that of a standard PC with SENG installed.
For Windows XP/Windows Server 2003, see the following table.
Table
Hardware Environment Required for SCS Simulation Tests (Windows XP/Windows Server 2003)
Type
TIP
SEE
ALSO
Specification
CPU
Pentium 4, 1.8 GHz or more
Main memory
512 MB + (number of SCS/FCS simulators) x 10 MB or more
Hard disk
User disk space of 10 GB or more
Display resolution
1024 x 768 or more, 1280 x 1024 are recommended, 65536 colors or more
(at least 4 MB of video memory)
Monitor
15" or more, 17" or more is recommended
Other
3.5" FDD and CD-ROM drive are required at installation
It does not affect the operations of SCS simulators whether a control bus communication card is mounted in the
general-purpose PC or not.
For the hardware environment required to use the expanded test functions, see the following:
n PC Environment Required for the Expanded Test Functions in 3.4.1, Operation Environment of the
Expanded Test Functions
IM 32S04B30-21E
1-7
Specifications of the OS are the same as that of SENG PC.
The control bus driver is required even if the PC does not have the control bus interface card.
The following software packages must be installed on the PC.
Table
Software Environment Required for SCS Simulation Tests: SCSP1/SCSV1
System
ProSafe-RS
CENTUM VP
CS 3000
Table
Package name
Model
Remark
Safety System Generation and Maintenance
CHS5100
R1.03 or later
CENTUM VP/CS 3000 Integration Engineering
CHS5200
R1.03 or later
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
LHS1100/LHM1101
R3.08.50 or later
LHS5100/LHM5100
R3.08.50 or later
Test Function
LHS5420/LHM5150
R3.08.50 or later
Software Environment Required for SCS Simulation Tests: SCSP2
System
ProSafe-RS
CENTUM VP
Package name
Model
Remark
Safety System Generation and Maintenance
CHS5100
R2.03 or later
CENTUM VP/CS 3000 Integration Engineering
CHS5200
R2.03 or later
LHS1100/LHM1101
R4.02 or later
LHS5100/LHM5100
R4.02 or later
Test Function
LHS5420/LHM5150
R4.02 or later
Note: SCSP2 cannot be connected with CS 3000.
TIP
SEE
ALSO
It is necessary to install CFS9153 Modbus Communication Package (for ALR111 and ALR121) on the PC which
executes engineering of SCS simulation tests for the SCS that defines subsystem communication.
For the software environment required to use the expanded test functions, see the following:
n Software Environment of the Expanded Test Functions in 3.4.1, Operation Environment of the
l Environment Required for SCS Simulation Tests

SCS simulation tests can only be executed in CENTUM integration environments.
Up to 8 stations, running either SCS simulator or FCS simulator, can be launched at the
same time on a single PC. However, it should be noted that the maximum number of stations
decreases depending on the CPU power of the PC and the load caused by other software being
executed at the same time. Note that this capacity is a logical restriction and does not provide
any performance guarantees.
If the number of simulators launched is more than this restriction, it is necessary to use the
expanded test functions of CENTUM to execute tests on multiple PCs.
SEE
ALSO
For the capacity of the SCS simulation test, see the following:
n Capacity in 4.2, SCS Simulation Test of the Engineering Guide (IM 32S01C10-21E)
IM 32S04B30-21E
1-8
l Minimum Configuration
PC
CENTUM
ProSafe-RS
Creation
CENTUM
project data
Standard Operation and

Monitoring Function
CENTUM VP/CS 3000

Integration Engineering
Copy
test DB
Test Function
SCS project
Safety System Generation

and Maintenance
Creation
010301E.ai
Figure 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.
PC
SCS Manager
Launch
SCS simulator
SCS 0101
Operation and Monitoring
SCS simulator
SCS 0102
Inter-SCS safety
communication
FCS simulator
FCS 0103
Data reference/setting
SCS link transmission

010302E.ai
Figure SCS Simulation Test with Single PC
IM 32S04B30-21E
1-9
n Target Tests
To execute a target test, an SENG is required along with the actual devices to be tested.
A general-purpose PC is required. The hardware requirements are the same as for the generalpurpose PC on which SENG is installed.
The SCS to be tested is also required.
Install the ProSafe-RS Safety System Generation and Maintenance Package (CHS5100).
In addition, the SENG software package required for engineering the test target SCS is
necessary.
IM 32S04B30-21E
1.4
1-10
<1.4 SCS Project for the Test>
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.
n SCS Project Attributes

The following three attributes can be set for SCS projects.
Default project
Current project
User-defined project
l Default Project
The default attribute is set for an SCS project which is newly created in SCS Manager.
l Current Project
When off-line 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.
l 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 off-line download has been executed.
SEE
ALSO
For details of project attributes, see the following:

n SCS Project Attribute in 1.3, Type of Project of the Engineering Guide (IM 32S01C10-21E)
For details of the Test Project Creating Tool, see the following:
5.1, Test Project Creating Tool
IM 32S04B30-21E
1-11
n 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.
l 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
ALSO
For details of Resource Properties dialog, see the following:

n Setting a Resource in 3.1.1, SCS Project Creation Procedure of the Engineering Reference (IM
32S04B10-21E)
n Operations that can be Executed for Each SCS Project Attribute

The types of tests that can be executed vary depending on the SCS project attributes. The tests
that can be executed for each SCS project attribute setting are explained below along with the
corresponding operational procedures.
l 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 off-line download operation on an
SCS.
l 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.
IM 32S04B30-21E
1-12
l 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, off-line 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.
SEE
ALSO
For details on how to reflect the data of a user-defined project to a current project, see the following:
n Operations Required after SCS Simulation Tests (User-defined Project) in 3.1.2, Engineering
Procedure after SCS Simulation Tests
n Specific Test Procedures

This section explains the practical test procedures using two examples: a new SCS project and
existing SCS project.
l New SCS Project

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 off-line 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 off-line download is performed with the default project attribute, the project attribute
changes to current.
l SCS Project to which Off-line Download has been Executed

The project attribute of an SCS project to which off-line 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.
SEE
ALSO
Use the Test Project Creating Tool to generate a user-defined project.
Build the user-defined project.
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 the specific procedure of engineering tasks on projects for executing SCS simulation tests, see the following:
3.1, Engineering of SCS Simulation Tests
IM 32S04B30-21E
2.
2-1
<2. Logic Simulation Test Operations>
Logic Simulation Test Operations

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.
SEE
ALSO
For the information about precautions for tests, see the following:
4.4, Precautions for Tests of the Engineering Guide (IM 32S01C10-21E)
n 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.
SEE
ALSO
For more information about the build operation, see the following:
Building SCS Project in 5.4, Procedure after Creating Application Logic of the Engineering Reference
(IM 32S04B10-21E)
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.
n 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.
IM 32S04B30-21E
2-2
n 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 can not be used for
logic simulation test.
SEE
ALSO
For information about the application debug function, see the following section of Workbench of
Workbench Users Guide:

Debug
For information about Dictionary View, see the following section of Workbench of Workbench Users
Guide:

Dictionary View
For information about Multi-Language Editor, see the following section of Workbench of Workbench
Users Guide:

Multi-Language Editor of Language Editors
For information about online monitoring, see the following:

3.3, Online Monitoring of the Utilities and Maintenance Reference (IM 32S04B20-21E)
l Check items in Logic simulation tests

The table below lists items that are checked in Logic simulation tests.
Table
Items Checked in Logic Simulation Tests

Items to be tested
Logic simulation tests
Generic application logics
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.
Application enabling operations and

monitoring from HIS (such as Override
FB, Manual operation FB, and External
communication FB)
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
Application logics that use System FB
Only normal behavior can be checked.

SCS Simulation test and Target test recommended
Inter-SCS safety communications/SCS link

transmission
Check the logic by using Forcing function on the internal

variable(s).
Check the logic by using Forcing function on the internal

FCS application that views/sets data in SCS variable(s).
Graphic windows related to SCS
Communication input /output tests
Conduct tests by using Forcing function on the output

parameters. For the communications with subsystem devices,
conduct Target tests.
SCS start actions
Performance test
The feature for Automatic scan period extension is disabled.

It is recommended to test the performance on the actual SCS.
IM 32S04B30-21E
2-3
l Actions on Abnormal Calculation

On the logic simulation test, the behaviors at abnormal calculation are different from the actions
on an actual SCS.
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.
n 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.
IM 32S04B30-21E
3.
3-1
<3. SCS Simulation Tests>
SCS Simulation Tests

An SCS simulation test is executed by launching SCS simulators that simulate operations
of SCSs on a PC. The test can only be executed in CENTUM integration environments. In
systems that are configured only with ProSafe-RS, SCS simulation tests cannot be executed. Use logic simulation tests and target tests instead.
This chapter explains engineering procedures for SCS simulation tests, along with the
test procedures and test support functions that can be used during testing.
n 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.
l 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.
SEE
ALSO
SCS simulators are equipped with functions for interfacing with plant operation training systems. For detailed
information, refer to the plant operation training simulator manual.
IM 32S04B30-21E
3-2
l Overview of SCS Simulator Functions

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.
l Items that can be Checked with SCS Simulation Tests

SCS simulation tests can test the following items.
Table
Items that can be Checked with SCS Simulation Tests

Items to be tested
SCS simulation test
Generic application logics
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 on-line monitoring.
Application enabling operations and

monitoring from HIS (such as Override
FB, Manual operation FB, and
External communication FB)
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.
Application logics that use System FB Operations of system FB can only be checked partly with target tests.
Inter-SCS safety communication
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.
SCS link transmission
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.
FCS application that views/sets data

in SCS
Execute a test by launching FCS simulator at the same time.
Graphic windows related to SCS
Graphic views not related to hardware can be tested from a virtual HIS.
Communication input /output tests
Execute a test using the Communication I/O Lock Window.

Communication with subsystems shall be checked using target tests.
SCS start actions
Starting up processes can be tested by rebooting an SCS simulator.

IM 32S04B30-21E
3-3
n 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
IM 32S04B30-21E
3.1
3-4
<3.1 Engineering of SCS Simulation Tests>
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.
n 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
030101E.ai
Figure Procedure for Executing an SCS Simulation Test
The steps to create a test project and perform engineering tasks after test above are different
for new SCS projects and SCS projects for which off-line download has already been performed.
IM 32S04B30-21E
3-5
l 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. Off-line download to the actual SCS
l SCS Simulation Test Procedure (SCS Project for which Off-line Download has
been Completed)
The attribute of an SCS project for which off-line 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
IM 32S04B30-21E
3.1.1
3-6
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 off-line download to an SCS has already
been completed. Each procedure is explained in the following.
n Step 1 Creating a Test SCS Project

The procedure for creating test SCS projects is different for newly created SCS projects and SCS
projects for which off-line download to an SCS has already been completed.
l In the Case of a Newly Created SCS Project (Default Project)

The attribute of a newly created SCS project is set to default until off-line 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.
SEE
ALSO
For the procedure for creating a new SCS project, see the following:
3.1, Creation of New SCS Projects of the Engineering Reference (IM 32S04B10-21E)
l In the Case of a Project for which Off-line 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.
SEE
ALSO
For how to use the Test Project Creating Tool to generate a user-defined project, see the following:
5.1, 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.
IM 32S04B30-21E
3-7
n Step 2 Creating a Test Project on the CENTUM Side

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.
l 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.
SEE
ALSO
For detailed information about the procedure to create an SCS with System View, see the following:
2.2.1, SCS Creation of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
l When the Attribute of a CENTUM Project is Set to Current

If the attribute of a CENTUM project that includes test target SCSs is set to current, create a copy
of the CENTUM project with System View in order to create a user-defined project.
n Step 3 Changing the Target Name

In order to execute an SCS simulation test, it is necessary to create a database for SCS
simulation tests in the test SCS project (default or user-defined project) prepared in step 1. In
order to do so, change the Target name to SCS_SIMULATOR in the Resource Properties dialog
box of SCS Manager.
The Resource Properties dialog box is opened by selecting [Properties] from the pop-up menu
displayed by right-clicking the mouse on a resource in Link Architecture View.
Resource Properties
Network
General
Extended
Target
Security
Code
Settings
Target: SCS_TARGET
Help
Target Options
The following options apply to all resources in the project
having the same target.
Memory size for temporary variables:
OK
32768
Cancel
Apply
030102E.ai
Figure Setting Target Name
IM 32S04B30-21E
3-8
When changing the Target name, the following warning dialog box appears. Click the [OK] button
in the displayed dialog box.
SCS Manager
When target name is changed, the master database is deleted. Do you continue?
OK
Cancel
030103E.ai
Figure Warning Dialog Box Appearing when Changing Target Name
TIP
When performing a build operation after changing the Target name, the master database is deleted. Because the
master database is deleted, it is necessary to run Integrity Analyzer and Cross Reference Analyzer after the build
operation.
l When Library Projects are Used

In case of an SCS project using a library project, the Target name of the library project must be
changed to match that of the SCS project. If the Target names of the SCS project and library
project do not match, an error occurs during the build operation. Specifically, perform the
following operations.
TIP
1.
Open the library project, change the Target name and then build.
2.
Open the SCS project, change the Target name and then build.
In case of a current project, it is not possible to change the Target name to SCS_SIMULATOR.
IM 32S04B30-21E
3-9
n Step 4 Setting CENTUM Project Folder Path

Open the SCS Project Properties dialog box from SCS manager and in the Project tab, specify a
CENTUM project folder to [CENTUM Project Folder].
The CENTUM project is the default or user-defined project prepared in step 2.
SCS Project Properties [Pjt: SCS0101]
SCS
Project
SCS Project database

Version:
CENTUM Connection
CENTUM Project Folder: C:\CENTUMVP\eng\BkProject\SCSTest
SCS Project Attribute:
Current Project
Originally Created:
R2.01.00
OK
Browse...
Cancel
030104E.ai
Figure SCS Project Properties Dialog Box
n Step 5 Building and Running Analyzers

Build the SCS project whose Target name was changed in step 3 and create a database for SCS
simulation tests.
Before launching the SCS Test Function window, run Integrity Analyzer and Cross Reference
Analyzer.
IMPORTANT
Because the [Target] field of Resource Properties was changed in step 3, it is necessary to
perform a build operation and run the analyzers even if no changes were made to the application
logic.
n Step 6 Creating SCS Tag List on the CENTUM Side

Open the CENTUM project created in step 2 from System View and generate an SCS tag list.
SEE
ALSO
For generation of SCS tag lists, see the following:

2.2.2, SCS Taglist Generation of Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
IM 32S04B30-21E
3.1.2
3-10
Engineering Procedure after SCS Simulation Tests
This section explains engineering tasks performed when debugging and testing have
been completed and SCS project data is to be downloaded to the actual SCS.
n Operations Required after SCS Simulation Tests (Default Project)

This section explains the procedure for performing off-line download to an actual SCS after an
SCS simulation test is completed with a default project.
l Step 1 Changing the Target Name

To perform off-line download, change the Target name from SCS_SIMULATOR to SCS_TARGET
in Resource Properties dialog box of SCS Manager, and then build the project.
l Step 2 Running Analyzers

Since the Target name has been changed, it is necessary to run Integrity Analyzer and Cross
Reference Analyzer.
l Step 3 Performing Off-line Download

Perform off-line download. The project attribute will be changed from default to current.
n Operations Required after SCS Simulation Tests (User-defined

Project)
This section explains the procedure for reflecting test results to an actual SCS after an SCS
simulation test has been completed with a user-defined project.
You can reflect test results by performing either on-line change download or off-line download.
l Reflecting Results by On-line Change Download

The overview of the procedure is explained below.
SEE
ALSO
For detailed information about the procedure for reflecting data of a user-defined project to a current project within
the scope where on-line change download is possible, see the following:
Expansion or Reformation (In Case On-line Change is Possible) in Import Procedure of 2.19,
Import and Export of the Engineering Guide (IM 32S01C10-21E)
1.
Export the changes made in the user-defined project.
2.
Import the exported files into the current project. To reflect changes with on-line change
download, import changed POUs individually.
3.
Perform a build operation and run the analyzers on the current project and perform an online change download to the actual SCS.
IM 32S04B30-21E
3-11
l Reflecting Results by Off-line Download

The overview of the procedure is explained below.
SEE
ALSO
For detailed information about the procedure for reflecting data of a user-defined project to a current project with
off-line download, see the following:
Expansion or Reformation (In Case On-line Change is not Possible) in Import Procedure of 2.19,
Import and Export of the Engineering Guide (IM 32S01C10-21E)
1.
Change the Target name of a user-defined project to SCS_TARGET using Resource

Properties dialog box of SCS Manager.
2.
Export the entire user-defined project.
3.
Import all the files of the exported project into the current project.
IMPORTANT
If the files of the user-defined SCS project with the Target name of SCS_SIMULATOR, which is
exported in its entirety, are imported into a current project as it is, it will not be possible to build the
project immediately, because the Target name becomes SCS_SIMULATOR. In this case, change
the Target name of the current project to SCS_TARGET.
4.
Perform a build operation and run the analyzers on the current project and perform off-line
download to the actual SCS.
IM 32S04B30-21E
3.2
3-12
<3.2 SCS Test Function Window>
SCS Test Function Window
The SCS Test Function window is launched from either SCS Manager or System View. An
SCS simulator is launched from the SCS Test Function window and managed via the SCS
Test Function window.
This section explains the following items regarding the SCS Test Function window.
Structure of the SCS Test Function window
Procedure to start an SCS simulation test
Procedure to end an SCS simulation test
n Management of SCS Simulators via the SCS Test Function Window

An SCS simulator is managed as follows via the SCS Test Function window.
An SCS simulator is launched from the SCS Test Function window.
One SCS Test Function window corresponds to one SCS simulator.
An SCS simulator can be stopped and resumed at any time from the SCS Test Function
window.
When the SCS Test Function window is closed, the SCS simulator launched from the
window is also terminated.
IM 32S04B30-21E
3-13
3.2.1
Structure of the SCS Test Function Window
This section explains the structure of the SCS Test Function window.
n SCS Test Function Window

The SCS Test Function window is almost identical to the Test Function window of CENTUM. If
the menu and buttons are unavailable, they appear dimmed.
The SCS Test Function window looks like as follows.
Test Function - Pjt: PJT01
File
Operation View Settings Tools Window Help

Stn:SCS0107 (Targetless)
BRK
Starting other-station communication reception process...

SCS Simulator Startup Processing...
Create the SCS simulator database.
Vnet Communication Startup Processing ...
Checking SCS Status ...
Getting password...
Specifying test target...
Completed SCS test function start processing.
Ready
030201E.ai
Figure SCS Test Function Window
IM 32S04B30-21E
3-14
l Menu Bar
The main items displayed in the menu bar of the SCS Test Function window are as follows.
Table
Menu Bar
Menu bar item
Sub item
Description
Change Test Target Displays a dialog box for changing test target station.
File
Exit Test Function
Exits the Test Function window after terminating an SCS simulator.
Normal Execution
Launches an SCS simulator if it is stopped and makes it run

continuously. Displays the current operation status of the SCS
simulator with a check mark.
Stop
Stops an SCS simulator. Displays a confirmation dialog box before

stopping it. Displays the current operation status of the SCS
simulator with a check mark.
Hide
Hides the Test Function window and displays the common test
function toolbar in the hidden mode (floating display) only.
Display Message
Shows/hides the message display area. If the message display area

is displayed, a check mark is displayed at the left of this item.
Common Toolbar
Shows/hides the common test function toolbar. If the common test

function toolbar is displayed, a check mark is displayed at the left of
this item.
Toolbar
Displays a dialog box (toolbar display dialog box) where it can be set
whether to show or hide the toolbar.
Operation
View
l Toolbar
Table
Common Test Function Toolbar

Item
Description
Run
Same as [Normal Execution] in the menu bar. Displays the operation status of an
SCS simulator.
Stop
Same as [Stop] in the menu bar. Displays the stop status of an SCS simulator.
Target Status Display Area
Displays a character string with the following format.

Stn : ${SCS-Stn} (${Target})
${SCS-Stn} is the name of the SCS station to be tested and ${Target} is either the
string target or the string virtual (no tool tips are displayed for this item only).
Hide/Show
Switches between hiding and showing the Test Function window. All Test Function
windows are hidden when the hidden mode is selected, and a floating toolbar with
the [Run], [Stop], [View], [Pause] and [Step] buttons and the Target Status Display
Area is shown.
l Pop-up Menu
Table
Toolbar Pop-up Menu

Item
Description
Display Message
Shows/hides the message display area. If the message display area is displayed,
a check mark is displayed at the left of this item.
Common Toolbar
Shows/hides the common test function toolbar. If the common test function toolbar
is displayed, a check mark is displayed at the left of this item.
Toolbar
Displays a dialog box (toolbar display dialog box) where it can be set whether to
show or hide the toolbar.
IM 32S04B30-21E
3-15
3.2.2
Procedure to Launch the SCS Test Function Window
The SCS Test Function window can be launched either from SCS Manager or from System
View.
For instance, the SCS Test Function window for an SCS mainly used for debugging is
launched from SCS Manager, whereas an SCS simulator to be used in a communication
test can be launched from System View.
When an SCS Test Function window is launched, an SCS simulator is launched simultaneously on a PC. The status of the SCS simulator can be checked from the SCS
Maintenance Support Tool of SENG or a virtual HIS.
n Launching the SCS Test Function Window from SCS Manager

The SCS Test Function window is launched from SCS Manager according to the following
procedure.
1.
Select [Maintenance] from the [Tools] menu of SCS Manager and launch the Maintenance
Launcher.
2.
Select [SCS Test Function] to display the Test Function Startup Confirmation dialog box.
Dialog
Change operation and monitoring function to
virtual test mode. OK?
HIS Station:
HIS0124
SCS Start Computer Name: LOCAL HOS
....
No Connect to Other PC
OK
Cancel
030203E.ai
Figure Test Function Startup Confirmation Dialog Box
TIP
In the [HIS Station] field, a virtual HIS to be launched at the same time as the SCS Test Function window can be
selected. The drop-down list shows HISs that are registered in the connected CENTUM project. Click [NONE] to
launch an SCS simulator only, without launching a virtual HIS.
3.
Click the [OK] button in the Test Function Startup Confirmation dialog box to display the
SCS Test Function window.
IM 32S04B30-21E
3-16
l Cases where Errors Occur when Launching the SCS Test Function Window
In the following cases, an error occurs when launching the SCS Test Function window.
A database has not been created for an SCS simulation test (the Target name is SCS_
TARGET).
A test target SCS has not been registered as a test project on the CENTUM side.
CENTUM project path is not properly specified in the SCS Project Properties dialog box.
The CENTUM project specified in a CENTUM project path is a current project.
TIP
In the following cases the [SCS Test Function] menu is not displayed in the Maintenance Launcher.
The CENTUM VP/CS 3000 Integration Engineering package is not installed.
The SCS project has a current attribute.
Note, however, that when off-line download is performed for a default project and the project attribute is changed
to current, the menu of the Maintenance Launcher being displayed is not changed dynamically. When the
Maintenance Launcher is displayed again, [SCS Test Function] is no longer displayed.
IM 32S04B30-21E
3-17
l Processing Performed after Launching the SCS Test Function Window

The following processing is performed after the SCS Test Function window is launched from SCS
Manager.
The database for the latest SCS simulation test is copied to the project folder on the
CENTUM side.
The SCS Test Function window automatically launches an SCS simulator.
An icon indicating the project attribute and the Target name is displayed in the left corner of
SCS Manager.
ProSafe-RS-[SCS0107 (* *)-Link architecture]
File Edit Insert Project Tools Debug Options Window Help
100%
107: SCS0107
Parameters
Variable Groups
Programs
Untitled FBD
Functions
Function blocks
FBD1
SENG001
NUM
030204E.ai
Figure Example of the Project Status Display Icon
An icon indicating the combinations of project attribute and the Target name is shown in the table
below.
Table
Icon Display by Project Attribute and Target Name

Project
Target name
SCS_TARGET
SCS_SIMULATOR
Current project
Default project
User-defined project
Library project
IM 32S04B30-21E
3-18
n Launching the SCS Test Function Window from System View

SCS Test Function windows can be launched for multiple SCSs from System View.
It is thus possible to use SCS Test Function windows depending on the situation. For instance,
the SCS simulator mainly used for debugging is launched from SCS Manager, whereas a
simulator of a station (SCS simulator/FCS simulator) to be used in a communication test can be
launched from System View.
PC
ProSafe-RS
SCS Manager
System View
Launch an SCS
simulation test
SCS Test
Function window
Start an FCS
virtual test
SCS Test
Function window
Start/stop an
SCS simulator
SCS
simulator
HIS
FCS Test
Function window
Start/stop an
SCS simulator
Start/stop an
FCS simulator
SCS
simulator
FCS
simulator
Start
Data flow
030206E.ai
Figure Combined Test with Multiple Simulators
l Starting Procedure
1.
Start System View for a user-defined project or a default project of the CENTUM to be
tested.
2.
Select [Test Function] from the [FCS] menu. Alternatively, right-click an SCS in the tree view,
select [Test Function] and launch the SCS Test Function window.
l Cases where Errors Occur when Launching the SCS Test Function Window
An error message appears and the SCS Test Function window is not launched if you attempt to
start the test function from System View on a PC where the current project is opened by SCS
Manager.
IMPORTANT
If the generation time of an SCS project and that of the SCS test database do not match, a
warning dialog box appears when launching the SCS Test Function window. If the procedure is
continued, testing is not performed correctly even though the SCS Test Function window can be
launched. In this case, select [Update SCS Test Database] in SCS Manager and then stop and
start the SCS simulator from the SCS Test Function window.
IM 32S04B30-21E
3-19
n Updating Database for Testing

When launching the SCS Test Function window from System View, the database for testing is not
copied to the project folder on the CENTUM side. Instead, the database copied in the previous
test is used. For this reason, if the SCS project has been changed with SCS Manager after the
previous test, it is necessary to update the database for testing. To put the latest SCS project data
to the project folder on the CENTUM side, use [Update SCS Test Database].
If [Update SCS Test Database] is selected from Maintenance Launcher of SCS Manager, the
SCS test database is copied to in the CENTUM project.
l Cases where Errors Occur when Updating Database for Testing

In the following case, an error occurs when updating the database for testing ([Update SCS Test
Database]).
The project attribute set for the SCS project is default or user-defined and no database has
been created for the SCS simulation test (the Target name is SCS_TARGET).
TIP
In the following cases, the [Update SCS Test Database] menu is not displayed in the Maintenance Launcher.
The CENTUM VP/CS 3000 Integration Engineering package is not installed.
The attribute of the SCS project is current.
Note, however, that when off-line download is performed for a default project and the project attribute is changed
to current, the menu of the Maintenance Launcher being displayed is not changed dynamically. When the
Maintenance Launcher is displayed again, [Update SCS Test Database] is no longer displayed.
IM 32S04B30-21E
3.2.3
3-20
Procedure to Close the SCS Test Function Window
When the SCS Test Function window is closed, the SCS simulator launched from the window is terminated as well.
n Closing the SCS Test Function Window

The SCS Test Function window can be closed with the following methods:
Click [File] - [Exit] in the SCS Test Function window.
A test function exit confirmation dialog box appears for the SCS Test Function window
selected to be closed.
Close System View
Test Function Exit Confirmation dialog boxes appear for all SCS Test Function windows
launched on the corresponding PC.
Test Function
Exit Test Function?

SCS Simulator Database
Test Environment
Save
Save
Delete
Delete
OK
Cancel
030208E.ai
Figure Test Function Exit Confirmation Dialog Box
When the [OK] button in the Test Function Exit Confirmation dialog box is clicked, the SCS Test
Function window is closed and the SCS simulator launched from the window is terminated.
TIP
If an FCS simulator was launched from System View, the FCS simulator is terminated when System View is
closed.
The SCS Test Function window is not automatically closed even if SCS Manager from which it was
launched is closed. With this arrangement, it is possible to launch SCS Manager for another station and
launch multiple SCS simulators.
IM 32S04B30-21E
3.3
<3.3 Execution of SCS Simulation Tests>
3-21
Execution of SCS Simulation Tests
After launching an SCS simulator, set the initial values for the SCS simulator and execute
the test using the test support functions, SCS Maintenance Support Tool and so on.
Certain operations of the SCS simulator are different from the actual SCS, however. This
section explains the following items.
Differences between an SCS simulator and actual SCS
Preparation for executing an SCS simulation test
Use of test support functions
Use of SCS Maintenance Support Tool
Use of virtual HISs
On-line changes of an SCS simulation test
3.3.1
Operations Unique to SCS Simulators
An SCS simulator simulates the operations of an SCS as accurately as possible, but some
of the operations are different from those of the actual SCS.
This section explains the main differences. Use a target test to check items that cannot be
checked with an SCS simulator.
n Input/Output Functions
An SCS simulator does not process inputs/outputs of input/output modules.
l Processing for Input/Output Modules

An SCS simulator does not process inputs/outputs of input/output modules. Input/output modules
are all simulated as being in normal status. Tests of communication involving field equipment
must be performed via target tests using actual devices.
SEE
ALSO
For data values of input/output variables and the initial value of data status, see the following:
3.3.2, Preparation for Executing SCS Simulation Tests
l HART Communication
An SCS simulator cannot perform HART communication. Tests of connection with PRM must be
performed via target tests using actual devices.
n Subsystem Communication
An SCS simulator cannot communicate with actual subsystems. The initial values for the entire
communication input/output range are 0 for the data value and GOOD for the data status. Tests
of communication with subsystems must be performed via target tests using actual devices.
n Modbus Slave Functions

In an SCS simulation test, communication with the device used as the Modbus master cannot be
performed. Tests of communication involving the Modbus master must be performed via target
tests using actual devices.
IM 32S04B30-21E
3-22
n Inter-SCS Safety Communication/SCS Link Transmission

An SCS simulator cannot communicate with the actual devices.
An SCS simulator does not diagnose errors related to the timing of the inter-SCS
safety communication/SCS link transmission safety communication. Tests involving
communication errors must be performed via target tests using actual devices.
SEE
ALSO
For detailed information about tests on inter-SCS safety communication/SCS link transmission safety
communication using SCS simulators, see the following:
3.5.2, Testing Inter-SCS Safety Communication/SCS Link Transmission Safety Communication
For detailed information about tests of SCS global switch communication combining SCS simulators and
FCS simulators, see the following:
3.6, Testing CENTUM Integration in Virtual Tests
n Specification for Scan Period and Execution Timing

The scan periods of both the application logic and the external connection function are fixed to 1
second for SCS simulators.
l Scan Period for Application Logic Execution Function

An SCS simulator operates the application logic with a 1 second period even if the actual SCS
being executed operates at a faster scan period. In this case, the operation timing is different
from the actual SCS.
Moreover, automatic scan period extension is disabled.
l FB Execution Timing
If the Scan Period for Application Logic Execution Function is specified less than 1 second,
the timing of the time-out occurrence is delayed for TIME-type input parameters of standard
function blocks such as TON and TOFF on the SCS simulator. For example, if the scan
period is set to 200 ms in the actual SCS, and the time-out value for a parameter is specified
to T#5s, the simulated time-out occurs after 25 scans, that is, 25 seconds. If the time-out
value is specified to T#400ms, the time-out occurs after 2 scans, that is, 2 seconds, and so
forth.

Applicable FBs:
TON, TOF, TP, VEL, ANLG_S, REPEATTIMER, ANLG1oo2D, ANLGVOTER, MOB_11,
MOB_21, MOB_RS, SYS_FORCE, SYS_FORCE_SC, SYS_SECURE, SYS_OVR, SYS_
PSWD, SYS_FORCE_BD
The output of function blocks whose output is determined by the number of calls, such as
CTU and CTD, is updated 5 times per second in the actual SCS if the scan period is 200
ms, but only once per second in the simulator.

Applicable FBs: CTU, CTD, CTUD, FILTER, FILTER_S
l Scan Period of the External Connection Function

The scan period of the external connection function, such as the CENTUM integration function,
is one second or two seconds, depending on the specification set in the actual SCS during
engineering. However, the scan period of an SCS simulator is always one second, regardless of
the specification set in the actual SCS.
IM 32S04B30-21E
3-23
n System Function Blocks

ProSafe-RS provides various system function blocks for the purpose of notifying the SCS status.
Some of these system function blocks behave differently in an SCS simulator than in the actual
SCS, however. The operations of application logic related to these system function blocks must
be checked with target tests.
Table
System Function Blocks those Operations are Different from the Actual SCS
System FB
SCS simulator operations
SYS_FORCE
Lock monitoring time operations are different.
SYS_PSWD
Password monitoring time operations are different.
SYS_OVR
Override monitoring time operations are different.
SYS_DIAG
IOER, VNER and IRER always output normal.
SYS_IOALLST
NRO and NRI are changed by the status of logical data.
SYS_NODEST
NRO and NRI are changed by the status of logical data.
SYS_OUTST
NRAL and NROR are changed by the status of logical data. CH1 to CH8 are changed by
the status of logical data.
SYS_OUTST16
NRAL and NROR are changed by the status of logical data. CH1 to CH16 are changed by
the status of logical data.
SYS_INST
NRAL and NROR are changed by the status of logical data.
SYS_CHST
Q is changed by the status of logical data. CH1 to CH8 are changed by the status of logical
data.
SYS_ESBINF
Always output normal status.
SYS_NODEINF
SYS_IOMDSP
Always output normal status. CTL is TRUE for odd slots and FALSE for even slots.
SYS_ALRDSP
SYS_SCAN
The output of CPU idle time is 0 second and the output of execution time is 100%.
SYS_TIME
PC time is displayed.
SYS_SCURE
Security level monitoring time operations are different.
SYS_NETST
SYS_CERR
Floating point overflow errors can not be detected.
SYS_SCANEXT
Outputs a fixed scan period value because automatic scan period extension is disabled..
n Security Level
Immediately after launching an SCS simulator, its security level is set to 0, which is not
the case for the actual SCS. Since the SCS simulator is not directly related to the plant
operation, it is not necessary to change to level 2.
In the actual SCS, the SCS security level is changed from 0 to 2 via off-line download or
by restarting the SCS, whereas in the case of an SCS simulator, the security level can be
changed to 2 without entering a password by starting the Maintenance Launcher from SCS
Manager and selecting [Set SCS Security Level].
l Password for Changing Security Level

Password is cleared when launching an SCS simulator.
IM 32S04B30-21E
3-24
n Hardware Diagnosis
An SCS simulator simulates all hardware as normal in the diagnosis.
l CPU
Always simulated as normal.
In the case of duplicated CPUs, the left CPU is simulated as being in control status, while
the right CPU is simulated as being in standby mode.
Since the simulation does not involve actual hardware, APC status does not exist.
l Power Supply Status

Always simulated as normal.
l Status of Input/Output Modules

Input/output modules and communication modules are always simulated as normal.
Communication bus and node status are always simulated as normal.
In case of input/output modules and communication modules in redundant configuration,
the module with the smaller slot number is simulated as being the control side.
l Status of Control Bus

The status of a control bus is always simulated as normal.
l HKU Functions
All items, including temperature, fan status and battery, are simulated as normal.
n Notifications of Self-diagnosis and Diagnostic Information

Certain diagnostic information messages that may be generated in an actual system are not
generated in case of an SCS simulator.
l System Switch (%SW)

The system switch that shows information related to hardware is always normal (0).
l Diagnostic Information Messages

Some of the self-diagnosis functions related to safety are not executed in SCS simulators.
Since self-diagnosis result is always simulated as normal, some of the diagnosis information
messages related to self-diagnosis are not generated.
Diagnostic information messages related to hardware, including modules and channels, are
not generated.
Certain system alarms, e.g., hardware failures, are not generated.
Diagnostic information generated before stopping is not restored when starting an SCS
simulator.
IM 32S04B30-21E
3-25
n Other Differences in Operations between SCS Simulator and Actual

SCS
In addition to those already explained, the following are differences in operations compared to the
actual SCSs.
l SCS Simulator Launch Timing

Since no actual input/output modules exist in an SCS simulator, I/O module startup processing
is not performed. Since flash memory is not accessed either, the completion timing of the initial
processing is different from that of the actual SCS.
l Difference in Operation due to Difference of CPU

Different CPUs are used for the actual SCS and the Windows PC that runs an SCS simulator.
Specifically in the case of application logic that handles floating point calculations, rounding
errors between the actual SCS and SCS simulator may occur in the calculations due to the
processor differences.
l SOE Events
There are no DI module events.
SOE events that occurred before the previous stop are not restored when starting an SCS
simulator.
l Time Synchronization
An SCS simulator operates based on the local PC clock regardless of the specification of
time synchronization. Note that if the expanded test functions are used to launch several SCS
simulators on different PCs, the time is not synchronized between the PCs.
The time synchronization status is always displayed as normal.
If Vnet/IP time synchronization is specified as the synchronization method, the time
synchronization status is always displayed as being synchronized relative to Vnet/IP.
l Behavior at Abnormal Calculation

The operation on the SCS simulator differs from that on an actual SCS only in the case of an
overflow that occurs in floating-point calculation of REAL numbers.
On an actual SCS, the CPU stops upon an overflow in floating-point calculation if "SCS
continues" is not specified as the behavior at abnormal calculation. If "SCS continues" is
specified, the calculation result is replaced with the maximum value of of REAL numbers.
On the SCS simulator, if an overflow occurs in floating-point calculation, the calculation result
becomes infinity. The calculations that use this abnormal result produce abnormal results, but the
POU does not stop.
SEE
ALSO
For more information about the behavior at abnormal calculation on an actual SCS, see the following:
B6.1.3, "Behavior at Abnormal Calculation" of the Safety Control Station Reference (IM 32S03B10-21E)
IM 32S04B30-21E
3-26
3.3.2
Preparation for Executing SCS Simulation Tests
Some operations of an SCS simulator are different from those of the actual SCS. For example, input/output processing of input/output modules is not performed in simulations.
Thus, when executing a test using SCS simulators, it is necessary to use the forcing function of the test support functions to set initial values required for the test.
Set the initial values required for each test according to the scope of testing.
SEE
ALSO
For detailed information about tests related to inter-SCS safety communication/SCS link transmission
safety communication, see the following:
3.5, Tests Using Multiple SCS Simulators
For detailed information about tests of CENTUM integration using SCS simulators, see the following:
3.6, Testing CENTUM Integration in Virtual Tests
n Status of Each Data Item in SCS simulators Immediately after

Launching SCS Simulators
The following are the status of data items immediately after starting of an SCS simulator.
Table
Status Immediately after Launching SCS Simulators

Item
Specifications when launching SCS simulators
Difference from the actual SCS
Internal variable
Initial value 0 is set.
Same as actual SCS
Input/output variable
The data value returns to the initial value in

the same way as at the initial cold start of the
actual SCS. On the other hand, the data status
becomes GOOD.
The actual device reflects the data

value and status of the plant.
Lock status
All locks are cancelled.
Same as actual SCS
Output enabled status
Outputs are invalid.
Same as actual SCS
Operating mode
Status is switched to the Waiting mode.
Same as actual SCS
Security level
Security level becomes 0.
The security level status becomes 2

in the actual SCS.
Password for changing

security level
Password is cleared.
Same status as after off-line

downloading
Operation mark
Returns to 0.
Same as actual SCS
UAID
Returns to initial value specified in the builder.
Same as actual SCS
Process alarm
Reflects status at launch.
Same as actual SCS
Diagnostic information
Diagnostic information before stopping a

simulator is not restored.
SOE
Diagnostic information before stopping a

simulator is not restored.
System alarm
A system alarm notifying the causes of SCS

simulator stopping is not sent.
Same operation as battery backup

switch is set to OFF
Same as immediately after off-line
downloading
IM 32S04B30-21E
3-27
n Initial Values of Data and Data Status for Input/Output Variables

Since an SCS simulator cannot be connected with input/output modules, input/output variables
take the following initial values of data and data status.
l Physical Data
Data values of physical data of input/output variables and data status of physical data of input/
output variables cannot be changed.
Table
Initial Values of Data and Data Status for Input/Output Variables

Data
Digital input
Digital output
Analog input
Analog output
Physical data
Data value/data status
Value
Data values are fixed to FALSE.
Data status
Fixed to GOOD
Value
FALSE at launch of the simulator
Data status
Fixed to GOOD
Value
Fixed to 0.0
Data status
Fixed to GOOD
Value
Tight-shut value at launch of the simulator
Data status
Fixed to GOOD
l Logical Data
The initial value of logical data is the same as the corresponding physical data.
TIP
When launching an SCS simulator, input/output variables are not locked in the same way as for the actual SCS.
To change an input value, lock the corresponding variable from I/O Lock Window and set an input value for the
logical data.
When the lock is cancelled, the value and status returns to those of the physical data.
n Setting Initial Values for Input/Output Variables

Lock variables using the I/O Lock Window. Set the initial values of data and data status using the
same window as well.
n Setting Initial Value for Communication Input/Output Variable

It is not possible to test communication with the actual subsystem using an SCS simulator.
The initial values of the communication input/output area are set to 0 for the data values and
GOOD for data status of all communication I/O data.
To test application logic related to communication inputs/outputs, initial values required for the
test must be set by the user.
Lock variables using the Communication I/O Lock Window. Set initial values of data and data
status using the same window as well.
IM 32S04B30-21E
3-28
n Execution of Output Enable Operation

When an SCS simulator has been launched, its output is invalid in the same way as for the actual
SCS. Enable the output from the I/O Channel Status Display dialog box of the SCS Maintenance
Support Tool. Outputs of all channels are enabled and values start to be output.
In the same way as for the actual SCS, inter-SCS safety communication and SCS link
transmission are also started with this operation.
l Status Change of Operating Mode

After completing the start-up process of an SCS simulator, the operating mode status is the
Waiting mode. The status changes to the Running mode after outputs are enabled.
TIP
Since an SCS simulator always simulates output modules as normal, the output changes from enabled status to
an invalid status only when a shutdown system function block (SYS_ALLSD, SYS_IOSD) is activated.
IM 32S04B30-21E
3.3.3
3-29
Test Support Functions in SCS Simulation Tests
After launching an SCS simulator, use the test support functions according to the test
purpose and start testing.
This section explains what types of test support functions can be used and how do they
work during SCS simulation tests.
n SENG Functions at SCS Simulation Tests

The operations of some of the functions that can be used in SENG for the actual SCS are
different when used for SCS simulators. The differences are summarized below.
l SENG Functions Available in SCS Simulation Tests

The main SENG functions that can be used in SCS simulation tests are as follows.
Debug function of SCS Manager (on-line monitoring, forcing, etc.)
On-line change download
Operation mark save/load
Integrity Analyzer
Cross Reference Analyzer
Database validity check tool
SCS Information dialog box
Security level setting
I/O Lock Window
Communication I/O Lock Window
SCS Link Transmission Lock Window
Inter-SCS Communication Lock Window
l SENG Functions Unavailable in SCS Simulation Tests

The following SENG functions cannot be used in SCS simulation tests. These functions cause
errors if called.
Off-line download
Launching the SCS simulator itself corresponds to the off-line downloading of the actual
SCS.
Master database off-line download
SCS restart
Stopping and resuming of an SCS simulator from the SCS Test Function window
corresponds to the restarting of the actual SCS.
IOM control right switching tool
IM 32S04B30-21E
3-30
n Forcing Function
The forcing function can be used when setting initial values and testing application logic. The I/O
Lock Window, Communication I/O Lock Window, SCS Link Transmission Lock Window and InterSCS Communication Lock Window allow setting multiple values at once in SCS simulation tests.
l Locking/Unlocking Each Variable

The operation conditions are the same as for the actual SCS. Each variable can be locked/
unlocked from Dictionary View, and so on. If the security level is 2, change it to 1 or 0.
l I/O Lock Window

In an SCS simulation test, multiple process input/output data can be set at the same time.
If the security level is 2, change it to 1 or 0.
When multiple data is set at the same time, diagnostic information messages for each of the
set data items are transmitted.
When large amounts of data are set at the same time, it will take some time before the
setting is completed. Be sure that the data setting is completed before starting the test.
SEE
ALSO
For detailed information about operations in the I/O Lock Window, see the following:
2.1, I/O Lock Window of the Utilities and Maintenance Reference (IM 32S04B20-21E)
l Communication I/O Lock Window

In an SCS simulation test, multiple communication input/output data can be set at the same time.
SEE
ALSO
For detailed information about operations in the Communication I/O Lock Window, see the following:
C1.6, Communication I/O Lock Window of the Open Interfaces (IM 32S05B10-21E)
IM 32S04B30-21E
3-31
l SCS Link Transmission Lock Window

In an SCS simulation test, multiple link transmission communication data can be set at the same
time.
SEE
ALSO
For detailed information about the SCS Link Transmission Lock Window, see the following:
2.2, SCS Link Transmission Lock Window of the Utilities and Maintenance Reference (IM 32S04B20-21E)
l Inter-SCS Communication Lock Window

In SCS simulation tests, multiple binding valuables can be set at the same time.
If the security level of the SCS is 2, change it to 1 or 0.
When multiple data are collectively set set at the same time, a diagnostic information
message is transmitted for each of the data item that has been set.
If large amounts of data are set at the same time, it will take some time before the setting is
completed. Be sure that the data setting is completed before starting the test.
SEE
ALSO
For detailed information about the Inter-SCS Communication Lock Window, see the following:
2.3, Inter-SCS Communication Lock Window of the Utilities and Maintenance Reference
(IM 32S04B20-21E)
n Application Debug Function

The application debug function is executed from the menu of SCS Manager. The following
functions can be used in SCS simulation tests.
Pause/pause cancellation (Cycle To Cycle/Real Time)
One-cycle execution (Execute one Cycle)
Break point (Break Point)
Step Execution
IMPORTANT
When using these functions, make sure to pay attention to the differences in operations from the
actual SCS, especially concerning scan period and execution timing.
SEE
ALSO
For detailed information about differences in operations between an SCS simulator and actual SCS due to
differences of scan period, see the following:
n Specification for Scan Period and Execution Timing in 3.3.1, Operations Unique to SCS Simulators
IM 32S04B30-21E
3-32
l Pause/Pause Cancellation (Cycle To Cycle/Real Time)

The execution procedure is the same as for target tests. The function is operated from SCS
Manager.
Once a request to pause is received, the application logic scan period processing is
bypassed and the periodic processing of the application logic is stopped.
When a test is paused, execution of application logic is never stopped in the middle. It is
always stopped after the execution of all logic within a scan is completed.
When a test is paused, the periodic processing of the external connection function is also
stopped. Specifically, updating of the alarm masking timer and the warning repetition timer
of process alarms is stopped. This is different from the actual SCS.
When the test is paused, counting of the warning repetition timer of mapping blocks is
stopped. However, the warning alarm repetition timer of annunciator messages is not
stopped.
The time information of an SCS simulator is updated even in paused status.
Communication from other simulators is received even in paused status.
The paused status/pause canceled status can be checked from the SCS Test Function
window as well.
l Differences of FB Operations in the Cycle To Cycle Mode

The operations of TON, TOF and TP function blocks in SCS simulator tests are different from the
operations in target tests/logic simulation tests.
In the actual SCS, these function blocks continue timekeeping even in the Cycle To Cycle
mode (while paused). For this reason, the output may become TRUE (in the case of TON)
immediately when the mode is switched to Execute one Cycle or Real Time.
In the case of an SCS simulator, the time during which the test is paused in the Cycle
To Cycle mode is not included in timekeeping. When the Execute one Cycle function is
performed during the Cycle To Cycle mode, the internal clock of TON and similar function
blocks advances by the time corresponding to one scan only.
If instance names are assigned to TON, TOF and TP function blocks and the same instance
is called in multiple locations, the actual SCS keeps the actual time. An SCS simulator,
however, operates as if the time advanced corresponding to the number of instances called.
(For example, if a TON instance with a delay time of 10 seconds is called at 2 locations, it
times out in 5 seconds.)
l One-cycle Execution (Execute one Cycle)

In one-cycle execution, the operation procedure is the same as for target tests and the function
is operated from SCS Manager. The external connection function is also included among
the targets of one-cycle execution (the operations are different from those of the actual SCS,
however).
l Break Point, Step Execution

The execution procedure is the same as for target tests; the function is operated from SCS
Manager.
IM 32S04B30-21E
3-33
l Changing Scan Period (Set Cycle Time)

The execution procedure is the same as for target tests; the function is operated from SCS
Manager.
In an SCS simulation test, the scan period of all application logic is fixed to 1 second regardless
of the specification for the actual SCS (the operations are different from those of the actual SCS,
however).
n On-line Monitoring Function

By placing SCS Manager in debug mode, it is possible to read variable data values of application
logic being operated in the launched SCS simulator, even during an SCS simulation test.
SEE
ALSO
For detailed information about on-line monitoring, see the following:

IM 32S04B30-21E
3-34
3.3.4
SCS Maintenance Support Tool in SCS Simulation

Tests
The status of an SCS simulator can be managed in the SCS Status Overview window and
the SCS State Management window of the SCS Maintenance Support Tool.
In an SCS simulation test, the following functions of the SCS Maintenance Support Tool
cannot be used.
Output module start
System report
IOM Report
IOM download
Time setting
n Operation when Starting/Ending SCS Simulation Tests

This section explains the operations of the SCS Maintenance Support Tool when starting and
ending an SCS simulation test.
If any of the following windows of the SCS Maintenance Support Tool are opened when starting
or ending an SCS simulation test, they are forcibly closed.
SCS Status Overview window
SCS State Management window
Diagnostic Information window
Message Cache Tool
n SCS Status Overview Window

The operations in the SCS Status Overview window that can be carried out during SCS
simulation tests are described below.
During SCS simulator operation, Test is displayed as SCS status.
During a simulation test, the communication status of the SCS other than SCS simulator is
displayed as Communication Error.
The bus name is always displayed as V net.
l Tool Buttons
The table below lists whether or not each tool button can be operated during SCS simulator
operation.
Table
Operability of Tool Buttons

Tool button
Operability
Call Project Selection dialog box
Call Diagnostic Information window
Call Time Setting dialog box

Call Setup Tool
Remark
This tool button is unavailable.

x
x:
Can be operated
Blank: Cannot be operated
IM 32S04B30-21E
3-35
n SCS State Management Window

While an SCS simulator is operating, the SCS State Management window displays the status of
the SCS simulator. Almost the same information as that of the actual SCS is displayed, but there
are the following differences.
Non-existing hardware such as input/output module is always displayed as normal.
The CPU idle time is displayed as 0 seconds and the communication load as 0%. The
program execution time is always displayed as 100%.
l Tool Buttons
The table below lists whether or not each tool button can be operated during SCS simulator
operation.
Table
Operability of Tool Buttons

Tool button
Operability
Call Project Selection dialog box

(common)
IOM download
Output module start

Call I/O Channel Status dialog box
Remark

x
Always displayed as normal.
Call System Report Display dialog box
Call Time Setting dialog box
Call Setup Tool
Call SCS Status Overview window
x:
Can be operated
Blank: Cannot be operated
n Diagnostic Information Window

While an SCS simulator is operating, the Diagnostic Information window displays diagnostic
information messages for the SCS simulator. The display specification is the same as for the
actual SCS.
The Ack/Del operations for diagnostic information are the same as for the actual SCS.
The diagnostic information mark is displayed in the same way as for the actual SCS.
l Tool Buttons
While an SCS simulator is operating, the tool buttons are available in the same way as for the
actual SCS.
IM 32S04B30-21E
3-36
n SOE Viewer
While an SCS simulator is operating, SOE Viewer displays events and diagnostic information
messages of the SCS simulator. The display specification is the same as for the actual SCS.
An SCS simulator does not generate events of DI modules.
l Tool Buttons
actual SCS.
n Message Cache Tool

While an SCS simulator is launched, the data acquisition status and disk cache usage status of
the SCS simulator are displayed.
l Tool Buttons
actual SCS.
n SCS SOE OPC Interfaces

Events and diagnostic information messages generated from an SCS simulator while the SCS
simulator is running are received by an OPC client.
IMPORTANT
Please note that on the OPC client side, it cannot distinguish whether the data acquisition
destination is an actual SCS or an SCS simulator.
IM 32S04B30-21E
3.3.5
3-37
Virtual HIS in SCS Simulation Tests
SCS simulators can be operated and monitored from virtual HIS.
n System Status Display View

Operations carried out in the System Status Display view while an SCS simulator is operating are
described below.
In the System Status Display view, a test function mark is displayed on the SCS icon while
an SCS simulator is operating.
In the list display, the computer name of the PC on which the SCS simulator is running is
displayed.
n SCS Status Display View

While an SCS simulator is operating, the SCS Status Display view displays the status of the
SCS simulator. Operations carried out in the SCS Status Display view while an SCS simulator is
operating are described below.
Non-existing hardware is always displayed as normal.
The CPU idle time is displayed as 0 seconds and the communication load as 0%. The
program execution time is always displayed as 100%.
While an SCS simulator is operating, a cyan colored frame is displayed in the Node Status
Display dialog box.
n Other Windows
An SCS simulator can be operated and monitored in various windows just like the actual SCS.
IM 32S04B30-21E
3-38
3.3.6
Downloading to SCS Simulators
Changes to applications made during an SCS simulation test can be reflected in the SCS
simulator. In order to reflect these changes, it is necessary to execute a build operation
and run the analyzers.
Changes in the range where on-line changes are possible can be reflected in on-line
change download to the SCS simulator.
An SCS simulator does not support off-line download. Instead, restarting an SCS simulator corresponds to off-line download.
n Execution of On-line Change Download to SCS Simulators

The conditions under which on-line change download is allowed to SCS simulator are the
same as for the actual SCS.
In the same way as for the actual SCS, on-line change download can only be executed
when the SCS security level is 1 or less. (Note, however, that the default security level at
launching an SCS simulator is set to 0 by default, and it is thus possible to perform on-line
change download without having to change the security level.)
IOM download to input/output modules is not executed. Normal completion messages are
always generated.
TIP
If the status is changed such that on-line change is not possible, on-line change download cannot be performed
in the same way as for the actual SCS. Stop the SCS simulator once and restart the SCS simulator from the SCS
Test Function window. Note that if the SCS simulator was started from System View, it is necessary to launch
SCS Manager first and execute [Update SCS Test Database] before starting the SCS simulator.
l On-line Changes from Debug Mode Status

SCS Manager is placed in the debug mode while forcing variables, changing scan period or
pausing. In this status, on-line change download of applications cannot be performed.
Use the following procedure to exit the debug mode before changing application settings.
1.
End the application debug function being executed from SCS Manager.
2.
From the [Debug] menu of SCS Manager, select [Stop Debug/Simulation] to cancel the
debug mode.
IM 32S04B30-21E
3.4
<3.4 Expanded Test Functions>
3-39
Using expanded test function package of CENTUM, it is possible to perform SCS simulation tests using multiple PCs.
In this way, it becomes possible to launch SCS Manager on several PCs at one time. In
tests where multiple SCSs are involved, such as inter-SCS safety communication tests,
it becomes possible to set values by forcing, in an SCS simulator that is mainly used for
debugging purposes, as well as in SCS simulators that are used in communication tests.
Thus, using the expanded test functions allows debugging to be performed efficiently
under various conditions.
IMPORTANT
Do not use _ (underscore) in the host name of a PC on which the expanded test functions
are executed. If _ is used for the host name of the PC on which an SCS simulator or virtual
HIS is launched, an error may be generated at startup, or communication between the SCS
simulator and virtual HIS may not be possible.
If an SCS simulator has been launched in a domain different from the domain of a virtual
HIS before launching the HIS, it may take up to one minute until the communication
between the virtual HIS and the SCS simulator is enabled.
A virtual HIS and an SCS simulator in the same domain will start communicating within one
minute regardless of the launching order.
In the expanded test functions, time is not synchronized among PCs.
Overview of the Expanded Test Functions

In environments where the expanded test function package is installed, it is possible to start
multiple PCs used for testing by specifying connection with other PCs when the SCS Test
Function window is launched. If the SCS Test Function window is launched in a test environment
showing items to be tested is shown in light green (default), and with CS 3000, the window border
is green (default). This indicates that the test environment is ready for communications with other
PCs. The expanded test functions enable the following.
Communication among Multiple PCs

Executing tests using multiple PCs makes it possible to test large-scale plant environments.
TIP
It is not possible to engineer a single SCS with multiple PCs simultaneously.

SCS Manager does not have functions to communicate with multiple PCs. To use the test support functions
for the SCS simulators running on other PCs from SCS Manager, it is necessary to run a virtual HIS or FCS
simulator at the same time on a PC on which SCS Manager is launched.
IM 32S04B30-21E
3-40
Configuration Avoiding Interference among Multiple PCs

The specification of connecting with other PC at launching the SCS Test Function window
must be set for each PC. Even when launching a simulator for a station of the same CENTUM
project, it is possible to avoid connecting with specific PCs only. If disconnected with other PCs,
the background of the pane showing items to be tested of SCS Test Function window is shown in
light red (default) with CENTUM VP, and the window border is in red (default) with CS 3000.
Remote Launching and Stopping an SCS simulator

It is possible to start/stop SCS simulators on other PCs from the SCS Test Function window.
Launching an Virtual HIS Alone

It is possible to launch a virtual HIS only, without launching the SCS Test Function window and/or
an SCS simulator. Background color of System Message Banner in the virtual HIS launched
alone is shown in yellow green (default) with CENTUM VP, the window border of virtual HIS
launched alone is in green (default) with CS 3000.
Tests of OPC Communication

It is possible to connect the ExaOPC package running on a PC. Thus, it becomes possible to
include ExaOPC stations in the scope of SCS simulation tests.
IM 32S04B30-21E
3-41
3.4.1
Operation Environment of the Expanded Test

Functions
This section explains the hardware and software environments required for the expanded
test functions.
n PC Environment Required for the Expanded Test Functions

A Windows PC is required.
If more than three PCs are connected, be sure to prepare a PC with Windows Server
installed as the PC where CENTUM project data is stored.
An Ethernet interface card is required on the PC.
PC environment for Windows Vista/Windows Server 2008 is the same as that of a standard
PC with SENG installed. For Windows XP/Windows Server 2003, see the following table.
Table
PC Environment Required for Expanded Tests (Windows XP/Windows Server 2003)

Type
Specification
CPU/OS
Pentium 4, 1.8 GHz or more
Main memory
512 MB + (number of SCS and/or FCS simulators) x 10 MB or more
Hard disk
User disk space of 10 GB or more
Display resolution
1024 x 768 or more, 1280 x 1024 are recommended, 65536 colors or more
(at least 4 MB of video memory)
Monitor
15" or more, 17" or more is recommended
Ethernet port
(On the PC that is not
connected to Vnet/IP)
Other
At least 1 port (in the case of a plant operation training system, 100 Mbps or 1 Gbps
Ethernet is required)
3.5" FDD and CD-ROM drive are required at installation.
IMPORTANT
To launch an SCS simulator remotely using the expanded test functions, do not install control bus
Interface card on a PC that runs SCS simulators. This is necessary to avoid communicating with
a PC that is communicating with an actual SCS by mistake.
IM 32S04B30-21E
3-42
n Software Environment of the Expanded Test Functions

The expanded test functions are required whenever it is necessary to execute an SCS simulation
test using multiple PCs. In order to use the expanded test functions, it is necessary to install the
CENTUM packages. Select the package to be installed according to the usage purpose of the
PC tests. Moreover, the control bus driver is required even if the PC does not have the control
bus interface card.
l Software Configuration of PCs that Run SCS Expanded Tests

This section provides an example where the expanded tests are executed in the following
configuration.
PC1
PC2
Ethernet
Start an SCS simulator

for debugging purposes
Start the programs (simulaters etc.)

that communicates with PC1
030401E.ai
Figure Example of Configuration of PCs for Executing Expanded Tests
Here, the main PC used by the engineer for debugging applications is called PC1. The PC that
communicates with the test function running on PC1 is denoted PC2. The usage purpose of PC2
can be outlined via patterns PC2-A to PC2-C listed below.
PC2-A: Remotely launch SCS simulators/FCS simulators on PC2 from PC1.
PC2-B: Launch a virtual HIS that monitors the SCS simulators launched into PC1.
PC2-C: Launch ProSafe-RSs SCS Manager to use the SCS Maintenance Support Tool for the
SCS simulators launched on PC1 (*1).
*1:
In order to launch the SCS Maintenance Support Tool for the SCS simulators launched on PC1, it is necessary to launch the HIS
simulator in PC2-C at the same time.
Install the following packages on each PC.

Table
Usage Purpose of PCs in Tests and Required Packages
Product
CENTUM (*1)
ProSafe-RS
(*2)
Package name
PC1
Standard Operation and Monitoring

LHS1100/LHM1101
Function
LHS5100/LHM5100
Test Function
LHS5420/LHM5150
LHS5425
FCS Simulator Package
LHS5426
HIS Simulator Package
LHS5427
Safety System Generation and

Maintenance Package
CENTUM VP/CS 3000 Integration
Engineering Package
PC2-A
(*3)
PC2-B PC2-C
x
CHS5100
CHS5200
x:
Required
Blank: Not required
*1:
For CENTUM VP, R4.01 or later and for CS 3000, R3.08.50 or later.
SCSP2 can be connected with CENTUM VP R4.02 or later. It can not be tested with CS 3000 system.
*2:
Install the related subsystem communication packages as well on PCs that are used to engineer SCS projects for which
subsystem communication is defined.
*3:
To operate SCS simulators, it is necessary to use the installation media of ProSafe-RS to install the SCS simulators.
IM 32S04B30-21E
3-43
For SOE OPC Interface package (CHS2200) to display the values of SCS simulator correctly,
the PC must have at least one of the following CENTUM packages installed: Test Functions,
Expanded Test Functions, FCS Simulator, and HIS Simulator.
l Configuration Involving 3 or More PCs

It is possible to launch multiple simulators on a single PC, but it is necessary to take the CPU
load of each PC, as well as the communication load between the PCs, into consideration when
configuring a large-scale system.
It is possible to distribute the load by using the expanded test functions to divide the tasks
between each PC involved and by installing software packages as shown below.
PC 2
PC 1
ProSafe-RS
CENTUM
Safety System Generation

and Maintenance

Monitoring Function
CENTUM VP/CS 3000

Integration Engineering

SCS
project
Test Function
CENTUM
project data
CENTUM
FCS Simulator (*1)
Ethernet
PC 4
PC 3
CENTUM
HIS Simulator Package
Monitoring Function
CENTUM
FCS Simulator Package
(*1) (*2)
030402E.ai
PC1:
PC2:
PC3:
PC4:
PC with a CENTUM project database (Windows Server)

PC on which SCS Manager is launched, mainly used for debugging applications
PC that performs operation and monitoring via a virtual HIS
PC used for remotely launching SCS simulators only
*1:
*2:
The SCS Simulator program is bundled to the FCS simulator Package.

To operate SCS simulators, it is necessary to use the installation media of ProSafe-RS to install the Common Functions of
ProSafe-RS Software.
Figure PC Software Configuration Example Taking Load Distribution into Consideration
IMPORTANT
The PC with a CENTUM project database (PC1 in the figure above) is accessed from other PCs
and its load is thus likely to be high. Do not operate HIS simulators, FCS simulators and SCS
simulators on PC1.
IM 32S04B30-21E
3-44
3.4.2
Executing SCS Simulation Tests Using the Expanded

Test Functions
This section explains the basic points in the expanded test function and how to execute
SCS simulation tests using the expanded test functions through specific configuration
examples.
SEE
ALSO
The basic points of the expanded test functions required for carrying out SCS simulation tests are explained in
this section. For more information about each function, see the following:

PART D, Expand Test Functions of the CS 3000 Engineering Test Guide (IM 33S01N10-01E)
PART D, Expand Test Functions of the CENTUM VP Engineering Test Guide (IM 33M10D20-40E)
n Examples of Executing Tests Using Multiple PCs

By using the expanded test functions, it is possible to execute an SCS simulation test using
multiple PCs. An example procedure for executing such a test is explained below.
PC1 and PC2 are used as follows, respectively.
PC1:
This PC is used to launch the SCS Test Function window from SCS Manager, as well as to
launch an SCS simulator and a virtual HIS on PC1.
PC2:
This PC is used to launch an SCS simulator and a virtual HIS from System View on PC2.
PC1
Virtual HIS
SCS Test
Function window
Control bus
communication emulation
CENTUM
PJT
DB
SCS Manager
SCS0109
PJT DB
Shared
PC2
Shared
Virtual HIS
SCS0109
PJT DB
SCS Test
Function window
SCS0109
simulator
System View
CENTUM
PJT
DB
030403E.ai
Figure SCS Simulation Test Using 2 PCs
IM 32S04B30-21E
3-45
A test is started and ended according to the procedure shown below.
l Step 1 Open the SCS Test Function Window on PC1

On PC1, launch an SCS simulator from SCS Manager.
Select [SCS Test Function] from the Maintenance Launcher of SCS Manager. The following Test
Function Startup Confirmation dialog box appears.
Dialog
HIS Station:
HIS0124
....
[Browse] button
OK
Cancel
030404E.ai
l Step 2 Select Simulation Targets on PC1
TIP
1.
Use the [HIS Station] field to select the name of the virtual HIS station launched on the local
PC (PC1).
2.
Use the [SCS Start Computer Name] field to select the name of the PC on which SCS
simulator of an SCS project is launched. In the example, select [LOCALHOST] as the
simulator is launched on the local PC.
It is possible to select the PC on which the simulators are launched by clicking the [Browse] button.
3.
Clear [No Connect to Other PC] if selected.
4.
Click the [OK] button. The virtual HIS and SCS simulator are launched on PC1.
l Step 3 Open the SCS Test Function Window from System View on PC2
On PC2, launch the SCS simulator from System View.
1.
Select the SCS you want to launch in System View of the CENTUM project to be tested and
select [Test Function] from the [FCS] menu. The Test Function Startup Confirmation dialog
box appears.
2.
The subsequent procedure is the same as l Step 2 Select Simulation Targets on PC1.
IM 32S04B30-21E
3-46
l Ending an Expanded Test

When the test is completed, close the expanded test functions according to the following
procedure. The SCS simulator launched from the corresponding window is stopped.
1.
Close the SCS Test Function window.
2.
When the last SCS Test Function window on the local PC is closed, it becomes possible
to select or deselect the check box for stopping the virtual HIS on the Test Function Exit
Confirmation dialog box. It is selected by default.
2-A If this check box is selected, the virtual HIS is closed at the same time as the test function is
ended.
2-B If this check box is cleared, the virtual HIS is not closed even if the test function is ended.
Test Function
Exit test function?
SCS simulator database
Test environment
Save
Save
Delete
Delete
Stop Virtual His

Cancel
OK
030405E.ai
Figure Test Function Exit Confirmation Dialog Box
n Example of Remotely Launching SCS Simulators on Another PC

This section explains the procedure for remotely launching an SCS simulator on another PC. The
procedure for launching a virtual HIS only and the procedure for closing a virtual HIS launched
alone are also explained.
PC1:
Open the SCS Test Function window from SCS Manager and launch an SCS simulator and
a virtual HIS. In addition, specify PC2 and launch an SCS simulator from System View.
PC2:
Launch the single virtual HIS.
PC1
PC2
Virtual HIS
SCS Test
Window
System View
Rem
SCS0101
simulator
SCS0101
PJT DB
SCS0109
PJT DB
SCS0109
PJT DB
Control bus
communication emulation
ote la
SCS Manager
Virtual HIS
unch
SCS0109
simulator
CENTUM
PJT
DB
CENTUM
PJT
DB
Shared
030406E.ai
Figure Remote Launch
IM 32S04B30-21E
3-47
l Step 1 Open the SCS Test Function Window on PC1

Select [SCS Test Function] from the Maintenance Launcher of SCS Manager. The following Test
Function Startup Confirmation dialog box appears.
Dialog
HIS Station:
HIS0124
....
[Browse] button
OK
Cancel
030407E.ai
l Step 2 Select Simulation Targets on PC1
TIP
1.
Use the [HIS Station] field to select the name of the virtual HIS station launched on the local
PC (PC1).
2.
Use the [SCS Start Computer Name] field to select the name of the PC on which SCS
simulators of an SCS project are launched. In the example, select [LOCALHOST] as the
simulator is launched on the local PC.
3.
Clear [No Connect to Other PC] if selected.
4.
Click the [OK] button. The virtual HIS and SCS simulator are launched on PC1.
l Step 3 Launch the Test Function from System View on PC1

1.
Select the SCS which you want to launch the SCS simulator from System View of the
CENTUM test project and select [Test Function] from the [FCS] menu.
2.
Since the virtual HIS has already been launched on PC1, the following Test Function Startup
Confirmation dialog box appears.
Dialog
Start Virturl Test Function.
OK?
OK
....
Cancel
030408E.ai
Figure Test Function Startup Confirmation Dialog Box (when the Second Test Function is Launched)
IM 32S04B30-21E
3-48
l Step 4 Select the Simulation Target on PC1

1.
TIP
Use [SCS Start Computer Name] to select the name of the PC that launches the SCS
simulator of the selected SCS project. In the example, select the computer name of PC2
because the simulator is launched on PC2.
2.
Click the [OK] button. The SCS simulator is launched on PC2.
l Step 5 Launch a Single Virtual HIS on PC2

If the expanded test functions are installed on a PC, you can launch a virtual HIS, without starting
the SCS Test Function window and SCS simulators.
The method of launching a virtual HIS alone varies depending on whether the system generation
function of CENTUM is installed on a PC or not.
l Step 5-A If the System Generation Function is Installed on PC2

Select the HIS you want to launch in a user-defined project from System View and select [Virtual
HIS] from the [HIS] menu. The Virtual HIS Startup Confirmation dialog box appears.
Confirm Switch
virtual test mode.
HIS Station:
OK
OK?
HIS0124
Cancel
030409E.ai
Figure Virtual HIS Startup Confirmation Dialog Box
The [HIS Station] field of the Virtual HIS Startup Confirmation dialog box displays the HIS station
name selected in System View. The HIS station name displayed in the [HIS Station] field cannot
be changed, nor is input allowed.
If the [OK] button is clicked in the Virtual HIS Startup Confirmation dialog box, the HIS selected in
System View starts up in the virtual mode.
IM 32S04B30-21E
3-49
l Step 5-B If the System Generation Function is not Installed on PC2

If the system generation function is not installed on a PC, a virtual HIS is launched from the
Virtual HIS Control window. To display the Virtual HIS Control window, select [Programs] [YOKOGAWA CENTUM] - [Virtual HIS Control] from the [Start] menu of Windows. Select an HIS
in a user-defined project in the Virtual HIS Control window and select [Virtual HIS] from the [HIS]
menu. The Virtual HIS Startup Confirmation dialog box appears.
The subsequent operations are the same as l Step 5-A If the system generation function is
installed on PC2 above.
Virtual HIS Control
File
Project
HIS
All Folders
-
SYSTEM VIEW
-
MYPJT
PJT06
HIS0164
HIS0663
HIS0664
Ready
030410E.ai
Figure Virtual HIS Control Window
l Closing an Individually Launched Virtual HIS

If a virtual HIS is launched alone on a PC, a virtual HIS icon appears on the task bar. Place the
mouse cursor on the virtual HIS icon and right-click the mouse to display a pop-up menu. Select
the [Exit Virtual HIS] menu item to display the Virtual HIS Stop Confirmation dialog box. Click the
[Yes (Y)] button in the Virtual HIS Stop Confirmation dialog box to close the virtual HIS.
Virtual HIS Icon
PM 10:40
030411E.ai
Figure Virtual HIS Icon

Virtual HIS stop confirmation screen
Shut down Virtual HIS.
Are you sure ?
Yes
No
030412E.ai
Figure Virtual HIS Stop Confirmation Dialog Box
IM 32S04B30-21E
3.5
3-50
<3.5 Tests Using Multiple SCS Simulators>
Tests Using Multiple SCS Simulators
Inter-SCS safety communication and SCS link transmission safety communication involve communication between multiple SCSs. They are thus tested using multiple SCS
simulators. It is possible to launch multiple SCS simulators on a single PC for simple
testing, but it is necessary to use the expanded test functions on multiple PCs when more
advanced functions such as the I/O Lock Window are used for each station in the testing.
3.5.1
Test Environment for Inter-SCS Safety

Communication/SCS Link Transmission Safety
Communication
This section explains the environment required to test inter-SCS safety communication
and SCS link transmission in an SCS simulation test. In addition, the procedure for changing SCS simulators to be tested is explained.
In order to test inter-SCS safety communication or SCS link transmission safety communication, it is necessary to launch multiple SCS simulators. However, since only one SCS
Manager can be launched on a single PC, it is not allowed to use the application debug
function for multiple SCSs at the same time. Thus, it is recommended to execute a multiple-SCS connection test using the expanded test functions on two or more PCs.
IM 32S04B30-21E
3-51
n Example of Testing on a Single PC

To debug inter-SCS safety communication or SCS link transmission safety communication with a
single PC, launch SCS simulators according to the following procedure.
SEE
ALSO
For specific operation method, see the following:

3.2.2, Procedure to Launch the SCS Test Function Window
SEE
ALSO
1.
Launch the SCS simulators of the SCS to be communicated with from SCS Manager or
System View.
2.
If the SCS simulators transmit data using inter-SCS safety communication as a producer, or
transmit data using SCS link transmission safety communication, use the SCS maintenance
Support Tool to perform the Enable Output operation.
For procedure of output enable operation, see the following:

3.1.6, Output Enable Operation of the Utilities and Maintenance Reference (IM 32S04B20-21E)
3.
If SCS Manager of the SCS simulator to be communicated is already open, close it at once.
4.
Open SCS Manager of the SCS to be mainly debugged, launch the SCS simulator
and perform debugging via the Inter-SCS Communication Lock Window or SCS Link
Transmission Lock Window.
l Changing Test Target SCS

It is possible to change between different SCS simulators to be tested without closing the SCS
Test Function window.
1.
Select [Change Test Target] from the [File] menu of the SCS Test Function window. The
Target Selection dialog box appears.
Select Test Target

Station of test target
FCS0102
FCS0103
FCS0104
FCS0105
SCS0107
OK
Cancel
030501E.ai
Figure Target Selection Dialog Box
2.
The Target Selection dialog box displays SCSs/FCSs defined in System View. Select the
SCS for which an SCS simulation test is executed.
3.
Click the [OK] button to display the Target Change Confirmation dialog box and click the
[Yes] button. The selected SCS simulator starts up.
IM 32S04B30-21E
3-52
n Example of Testing Inter-SCS Safety Communication/SCS Link

Transmission Safety Communication Using the Expanded Test
Functions
The following figure shows an example of PC configuration for testing inter-SCS safety
communication or the sending and receiving sides of SCS link transmission safety
communication at the same time.
shared
PC2
PC1
CENTUM
Standard
Builder Function
Standard Operation
and Monitoring
Function
ProSafe-RS
SCS0102
PJT DB
CENTUM
PJT DB
CENTUM
PJT DB
Safety System
Generation and
Maintenance
CENTUM VP/
CS 3000 Integration
Engineering
Test Function
Expanded
Test Functions
SCS0101
PJT DB
CENTUM
ProSafe-RS
Standard Operation
and Monitoring
Function
Safety System
Generation and
Maintenance
Test Function
CENTUM VP/
CS 3000 Integration
Engineering
FCS Simulator
SCS simulator
SCS0101
SCS0102
PJT DB
SCS simulator
SCS0102
Ethernet
030502E.ai
Figure Example of Testing Inter-SCS Safety Communication or SCS Link Transmission Safety
Communication Using Two PCs
l Startup Procedure
The procedure below shows how to test inter-SCS safety communication or SCS link
transmission safety communication using two PCs configured as shown above.
SEE
ALSO
1.
On PC1, launch SCS Manager for the SCS0101 project.
2.
From SCS Manager, launch the SCS Test Function window.
3.
From the SCS Test Function window, launch the SCS simulator for the SCS0101 project
and the virtual HIS.
4.
On PC2, launch SCS Manager for the SCS0102 project.
5.
From SCS Manager, launch the SCS Test Function window.
6.
From the SCS Test Function window, launch the SCS simulator for the SCS0102 project
and the virtual HIS.
7.
Use the test support functions on the respective PCs to set the initial values for the SCS
simulators and execute the test.
For the specific operation procedure using the expanded test functions, see the following:
3.4.2, Executing SCS Simulation Tests Using the Expanded Test Functions
IM 32S04B30-21E
3-53
l Changing Test Target SCSs in Expanded Tests

It is possible to change the test target SCS simulator without closing the SCS Test Function
window with the expanded test functions as well. It is not allowed to specify the PC that starts
up the SCS simulator, however. It is only possible to start up another SCS simulator on a PC on
which the SCS Test Function window is open.
IM 32S04B30-21E
3.5.2
3-54
Testing Inter-SCS Safety Communication/SCS Link

Transmission Safety Communication
This section explains precautions when executing SCS simulation tests of inter-SCS
safety communication or SCS link transmission safety communication.
n Precautions for SCS Simulation Tests of Inter-SCS Safety

Communication
It is possible to test inter-SCS safety communication between SCS simulators by starting up
multiple SCS simulators.
SCS simulators cannot communicate with actual SCSs.
After the SCS simulators are launched, start output communication with the output enable
operation in the same way as for the actual SCSs.
If there are any errors in the binding definitions for consumer FB (CONS_*), the value from
OUT retains its initial value and the value from NR becomes FALSE even after the output
is enabled. In this case, the applications should be reviewed. Note that messages notifying
about errors are not generated when the output enable operation is performed.
SCS simulators do not diagnose transmission delay timeout (DLYT) and reception interval
timeout (OUTT) via consumer FB (CONS_*). For this reason, an SCS simulator on the
consuming side will not detect an error even if an SCS simulator on the producing side is
paused.
Even if an SCS simulator on the producing side is stopped, the consuming side does not
detect an error. To perform testing in such abnormal cases, it is necessary to execute target
tests using the actual SCSs.
Table
Operation of Consumer FB when SCS Simulator Error on the Producing Side

Condition
SCS simulator does not exist on the

producing side
SCS simulator on the producing side stops
abruptly
Variable value of CONS_* at Diagnostic information meserror occurrence

sage
OUT: Initial value
Not output
NR: FALSE
OUT: Retained
Not output
NR: TRUE
Use the Inter-SCS Communication Lock Window and set values so as to check the validity
of the application logic.
IM 32S04B30-21E
3-55
n Precautions for SCS Simulation Tests of SCS Link Transmission

Safety Communication
The operations of SCS link transmission can be checked with SCS simulation tests.
Data of SCS link transmission can be communicated between SCS simulators, but diagnoses
related to time are not performed. Thus, testing at communication errors cannot be performed.
Testing at communication errors must be performed using the actual SCSs. In addition, it is
necessary to use target tests to check the following items as well.
Performance
Communication load, CPU load
Note that SCS simulators cannot communicate with actual SCSs via SCS link transmission.
It is recommended to use two or more PCs to perform communication tests of SCS link
transmission using SCS simulators.
l When a Single SCS Simulator is Launched

When an SCS simulator is launched, all data received via SCS link transmission becomes
erroneous (the data value is FALSE and the data status is BAD). Lock the received data in the
SCS Link Transmission Lock Window and check the validity of the logic while setting values.
l When Multiple SCS Simulators are Launched

Launch SCS simulators on the sending side, perform the output enable operation and start data
communication in the same way as for actual SCSs.
After the output is enabled for sending side SCS simulator, interfaces between stations can be
tested. Check that the data types match between the sending side and receiving side on the SCS
Link Transmission Lock Window.
IM 32S04B30-21E
3.6
3-56
<3.6 Testing CENTUM Integration in Virtual Tests>
Testing CENTUM Integration in Virtual Tests
It is possible to use virtual tests of CENTUM (virtual HIS and FCS simulator) and SCS
simulators in order to test CENTUM integration. This section explains the procedure until
the start of testing executed with a single PC.
n PC Configuration Example
When performing an SCS simulation test using a default project of CENTUM integration
configuration on a single PC, the PC is configured as follows.
PC1
Virtual HIS
System View
SENG
SCS simulator
FCS simulator
SCS simulation test
SCS0101-pjt
(Default SCS project)
CENTUM-pjt
(Default project)
SCS0101, HIS0164
030601E.ai
Figure SCS Simulation Test of CENTUM Integration Configuration
n Procedure of Launching the Test Function

When using a Default project, the test function is started up according to the procedure shown
below.
1.
Create an SCS project with default attribute and create the required application logic. Then
define the communication with SCS Link Transmission Builder in order to perform SCS
global switch communication with FCS.
2.
Using Tag Name Builder, define tag names for the applications that communicate data with
tag name interfaces to the CENTUM stations.
3.
Register the test target SCSs in a CENTUM default or user-defined project.
4.
Change the Target name to SCS_SIMULATOR in the Resource Properties dialog box of the
SCS Manager.
5.
Specify the CENTUM project path registered in step 3 in the SCS Project Properties dialog
box.
6.
Perform a build operation and run the analyzers on the SCS project.
7.
Generate a tag list in System View.
8.
Open the SCS Test Function window from SCS Manager. When launching the SCS
simulator, launch the virtual HIS as well.
9.
Launch the FCS simulator from System View as required.
10. Use the test support functions and HIS simulator of SENG to test CENTUM integration
applications.
IM 32S04B30-21E
4-1
<4.1 Overview of Target Tests>
4.
Target Tests
After Logic simulation tests or SCS Simulation tests, conduct Target tests.
Target tests must be conducted for the following cases:
The test conducted by connecting to actual hardware, the test conducted when abnormality occurs in inter-SCS communication or SCS Link Transmission, the test to check the
SCS performance.
4.1
Overview of Target Tests
In target tests, tests are conducted by running the application on the actual machine.
n Test items in Target test

The table below lists the items that are tested in the target tests
Table Test Items Included in Target Test
Test type
ALSO
Hardware except SCS

and external system
used in test
Disconnecting input/output modules, input/output

devices or input/output signal without jig (devices
simulating field signals)
Forcing (*1)
None
Tests of application logic using actual SCS

Test of application logic in single SCS or
covering multiple SCSs
Simulation test of operations at error detection
SOE collection test
Application debug, forcing (*1)
None
Input/output tests
Wiring check between channels and devices
Test of input/output devices (confirmation of
actual input values and operations)
Confirmation of performance
Test of SOE collection of discrete input/output
modules
Jig, device
Tests of CENTUM integration function

Test of access via tag name
Test of annunciator
Alarm test
Test of override from HIS
Target environment of
CENTUM system
Tests of Modbus connection definitions

Test of access via Modbus master
Modbus master device
Confirmation of overall operations of application

Operation check including inputs/outputs
Operation check including CENTUM
Operation check including Modbus master
Tuning of parameter values
Forcing (*1)
Whole system
*1:
SEE
Test-related function used
SCS security level must be Level 1 or 0 to execute Forcing function.
For more information about whether to lock or unlock the inputs or outputs, see the following:
(D) (D) On-line Change Download in Procedure for On-line Change of an Application in 5.1, Entire
Procedure of On-line Change of Application of the Engineering Guide (IM 32S01C10-21E)
For more information about testing CENTUM integration function, see the following:
2.3, Tests in the CENTUM Integration Structure of the Integration with CENTUM VP/CS 3000 (IM
32S01E10-21E)
IM 32S04B30-21E
4.2
4-2
<4.2 Target Test Operation (In Case On-line Change Download is not Possible)>
Target Test Operation (In Case On-line

Change Download is not Possible)
This section describes how to conduct target tests after a large-scale change is made to a
project disallowing on-line change download.
SEE
ALSO
For information about precautions for tests, see the following:

n Generate an SCS Database

After creating an application logic, execute a build operation on the application logic to generate
an SCS database. Generate a database for a CENTUM project as well if the system is connected
to CENTUM.
SEE
ALSO
n Building SCS Project in 5.4, Procedure after Creating Application Logic of the Engineering Reference
(IM 32S04B10-21E)
n Off-line Download
Before you start target tests, perform an off-line download to SCS.
l Change the SCS Security Level

Change the SCS security level to Level 0 using the SCS security level operation function.
SEE
ALSO
For information about changing the SCS security level, see the following:
1.3, Security of SCS of the Utilities and Maintenance Reference (IM 32S04B20-21E)
l Download the SCS Database

Download the SCS database to the SCS using off-line download. The operating mode of the
SCS transits to the Waiting mode and the SCS security level changes to Level 2.
If the system is connected to CENTUM, download the database of the CENTUM project as well.
SEE
ALSO
For more information about off-line download, see the following:

9.1, Off-line Download of the Engineering Reference (IM 32S04B10-21E)
For information about engineering for CENTUM integration, see the following:
2, Engineering for CENTUM Integration of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
IM 32S04B30-21E
4-3
n Start a Target Test

To start a target test, you must do the following.

Change the SCS security level to the level that allows executing the desired test using the SCS
security level operation function.
SEE
ALSO
For information about security level required to conduct each test, see the following:
n Outline of Test Function in 4.1, Types of Test of the Engineering Guide (IM 32S01C10-21E)
l Transition to the Debug Mode

Open an SCS project you want to test in SCS Manager or Multi-Language Editor and select
[Debug] of [Debug] menu in SCS Manager.
The mode transits to the debug mode.
l Lock Inputs and Outputs

If some input/output modules are not installed or the field wiring is not completed, use the forcing
function to lock the corresponding input/output modules.
SEE
ALSO
For more information about whether to lock or unlock the inputs or outputs, see the following:
(D) (D) On-line Change Download in Procedure for On-line Change of an Application in 5.1, Entire
Procedure of On-line Change of Application of the Engineering Guide (IM 32S01C10-21E)
For information about how to lock input/output modules using the forcing function, see the following:
l Enable Outputs
Enable the channels of output modules for which output has been invalidated. Perform the output
enable operation from the SCS State Management window of SCS Maintenance Support Tool.
IMPORTANT
The output enable operation will be performed for each SCS, rather than for each channel. When
the output enable operation is performed, the inter-SCS safety communication producer side
and the SCS Link Transmission sender side become enabled and then the application logic can
output to the subsystem.
SEE
ALSO
For information about the output enable operation in the SCS State Management window, see the following:
3.1.6, Output Enable Operation of the Utilities and Maintenance Reference (IM 32S04B20-21E)
IM 32S04B30-21E
4-4
n Execute the Target Test

Debug and test the applications running on the SCS using the application debug function, the
forcing function and the online monitoring function.
SEE
ALSO
For information about the application debug function in the Target window, see the following section of
Workbench of the Workbench Users Guide:

Debug
For how to use I/O Lock Window for the forcing function, see the following:
For information about the online monitoring function, see the following:
n End the Target Test

The target test is stopped in different ways depending on whether the SCS security level is
changed from the offline level (Level 0) to the online level (Level 2) or the SCS security level is
changed from online level 1 to online level 2.
l If SCS Security Level is Changed from the Offline Level (Level 0) to the Online
Level (Level 2)
1.
Transit out of the debug mode

Select [Stop Debug/Simulation] of [Debug] menu in SCS Manager or Multi-Language Editor.
2.
Perform off-line download of the SCS database or restart the SCS

Download the database to the SCS using off-line download. Alternatively, restart the SCS
manually. When you used the breakpoint function, perform off-line download.
l If SCS Security Level is Changed from Online Level (Level 1) to Online Level
(Level 2)
1.
Unlock variables
Unlock variables that were locked during debugging and testing.
2.
Change the SCS security level

Change the SCS security level to Level 2.
3.

IMPORTANT
When debug mode is terminated, or when the SCS Manager is terminated while the debug
mode is active, if the locked variables (including the variables in the locked modules) exist, a
confirmation dialog box appears and then the debug mode or the SCS Manager ends. Unlock the
locked variables from Dictionary View or I/O Lock Window.
IM 32S04B30-21E
4.3
4-5
<4.3 Target Test Operation (In Case On-line Change Download is Possible)>
Target Test Operation (In Case On-line

Change Download is Possible)
This section describes how to conduct target tests after a small-scale change is made to a
project allowing for on-line change download.
SEE
ALSO
For information about precautions for tests, see the following:

n Change the SCS Database

After updating the application logic, execute a build operation on the application logic to generate
a SCS database.
SEE
ALSO
n Building SCS Project in 5.4, Procedure after Creating Application Logic of the Engineering Reference
(IM 32S04B10-21E)
n Start the Target Test

To start a target test, you must do the following.

Change the SCS security level to Level 1 using the SCS security level operation function if you
perform on-line change download.
SEE
ALSO
l Transition to the Debug Mode

Open an SCS project you want to test in SCS Manager or Multi-Language Editor and select
[Debug] of [Debug] menu in SCS Manager.
The mode transits to the debug mode.
IM 32S04B30-21E
4-6
n Perform SCS On-line Change Download and Confirm the Updates

The procedure to apply changed items in the target tests to the SCS by on-line change download
is as follows.
l Lock Input and Output Modules

Lock input/output modules that may be affected by on-line change download using the forcing
function.
SEE
ALSO
For information about how to lock input/output modules using the forcing function, see the following:
TIP
Consider the necessity of locks in inter-SCS safety communication and SCS Link Transmission.
l Perform On-line Change Download

Select [Stop Debug/Simulation] of [Debug] menu in SCS Manager or Multi-Language Editor.The
debug mode is closed.
Perform on-change download.
SEE
ALSO
For more information about on-line change download, see the following:
9.2, On-line Change Download of the Engineering Reference (IM 32S04B10-21E)
l Check Application Updates

Check that the operations of the updated areas are correct. After transition to the debug mode,
use the forcing function and the online monitoring function as necessary.
SEE
ALSO
For how to use I/O Lock Window for the forcing function, see the following:
For information about the online monitoring function, see the following:
IM 32S04B30-21E
4-7
n End the Target Test

1.
Unlock variables
Unlock variables that were locked during debugging and testing.
2.
Change the SCS security level

Change the SCS security level to Level 2.
3.

IMPORTANT
When debug mode is terminated, or when the SCS Manager is terminated while the debug
mode is active, if the locked variables (including the variables in the locked modules) exist, a
confirmation dialog box appears and then the debug mode or the SCS Manager ends. Unlock the
locked variables from Dictionary View or I/O Lock Window.
IM 32S04B30-21E
5.
5-1
<5.1 Test Project Creating Tool>
Test Function Tools

This chapter explains tools and windows used in engineering tasks for the test functions.
5.1
Test Project Creating Tool
This tool is used to create projects for SCS simulation tests.

The user-defined project attribute is set for SCS projects created with this tool.
The Test Project Creating Tool cannot be launched if SCS Manager is already running on
the PC. Close SCS Manager if it is running.
n Operations of Test Project Creating Tool

The Test Project Creating Tool is launched from the [Start] menu of Windows.
Select [All programs] - [YOKOGAWA ProSafe] - [Test Project Creating Tool] from the [Start] menu
of Windows.
The Test Project Creating Tool window is launched.
Test Project Creating Tool
RS Project
C:RS-Projects\MYRSPJT
Browse...
SCS Project
SCS0101
SCS0102
SCS0103
SCS0104
SCS0105
Select All
Copy To
C:\Test-Projects\TESTPJT
Browse...
CENTUM Project C:\CENTUMVP\BKProject\MYPJT
Browse...
OK
Close
050101E.ai
Figure Test Project Creating Tool
IM 32S04B30-21E
5-2
<5.1 Test Project Creating Tool>
l Procedure for Creating User-defined Projects
TIP
1.
Click the [Browse] button and select the target RS project folder.
When an RS project is selected, all SCS projects included in the RS project are displayed.
2.
Select the SCS project to be copied in the [SCS Project] field.

Select [Select All] to select all SCS projects included in the selected RS project.
3.
Specify the copy destination SCS project in the [Copy To] field.
It is also possible to click the [Browse] button to select the target RS project folder.
If no RS project folder exists in the copy destination, click the [OK] button to create a new RS project folder.
If an SCS project with the same name already exists in the RS project, an error dialog box appears if the
[OK] button is clicked and the project will not be copied.
4.
Specify the path of the CENTUM project to be connected with the SCS project to be created
with this tool in the [CENTUM Project] field.
It is also possible to click the [Browse] button to select the folder of the CENTUM project to
be connected.
Specify a path of either a default project or user-defined project for the CENTUM project
path name.
5.
Click the [OK] button to perform the following processing.
The selected SCS project is copied to the specified folder.
The Target name of the copy destination SCS project is automatically changed to SCS_
SIMULATOR. At this point, a dialog box with a message The copy destination master
database is deleted. Do you want to continue? is displayed. Click the [OK] button.
Library projects related to the copy source SCS project are copied to the copy destination
RS project.
The Target name of the copy destination library projects are automatically changed to
SCS_SIMULATOR.
The library projects referenced by the copy destination SCS project are automatically
switched to the copied library projects.
IM 32S04B30-21E
5.2
5-3
<5.2 Project Attribute Tool>
Project Attribute Tool
The Project Attribute Tool is used to display the status of test projects. The Project
Attribute Tool cannot be launched if SCS Manager is already running on the PC. Close
SCS Manager if it is running.
n Operations of Project Attribute Tool

The Project Attribute Tool is started from the [Start] menu of Windows.
Select [All programs] - [YOKOGAWA ProSafe] - [Project Attribute Tool] from the [Start] menu of
Windows.
The Project Attribute Tool window is launched.
Project Attribute Tool
RS Project
Station
SCS0101
SCS0102
SCS0103
SCS0104
C:\RS-Projects\MYRSPJT
Attribute
User Defined
User Defined
User Defined
User Defined
Target
SCS_SIMULATOR
SCS_TARGET
SCS_SIMULATOR
SCS_TARGET
Browse...
CENTUM Project
C:\CENTUMVP\..
C:\CENTUMVP\..
C:\CENTUMVP\..
C:\CENTUMVP\..
Close
050201E.ai
Figure Project Attribute Tool Window
l Operation Procedure
Click the [Browse] button next to the [RS Project] field and select the target RS project folder. The
statuses of SCS Projects that are included in the RS Project are displayed.
IM 32S04B30-21E
Rev-1
Revision Information
Title
: ProSafe-RS System Test Reference
Manual No. : IM 32S04B30-21E
Dec. 2009/3rd Edition/R2.03 or later*
*: Denotes the release number of the software corresponding to the contents of this users manual. The
revised contents are valid until the next edition is issued.
Introduction
Added the description
1.2
Added the description for using Inter-SCS Communication Lock Window.
1
Added the description for SCSP2.
1.3
Added the description for Windows Server 2008.
1.3
Changed the description for related CENTUM software release number.
1.3
Added the description for SCSP2.
1.3
Changed the description for testing the multiple SCSs.
2.
Added the description for the behavior at abnormal calculation in SCS.
2.
Added the description for automatic scan period extension in SCS.
3.
Added the description for using Inter-SCS Communication Lock Window.
3.3.1 Added the description for automatic scan period extension in SCS.
3.3.1 Added the description for new Function Block.
3.3.1 Added the description for the behavior at abnormal calculation in SCS.
3.3.3 Added the description for using Inter-SCS Communication Lock Window.
3.3.4 Added the description included in supplement.
3.4.1 Added the description for Windows Server 2008.
3.4.1 Changed the description for control bus interface cards.
3.4.1 Added the description for SCSP2.
3.4.1 Added the description included in supplement.
Dec. 2008/2nd Edition/R2.02 or later

Overall CS 3000 was changed to CENTUM to refer to both CENTUM VP and CS 3000.
Overall Changed according to the specifications of CENTUM VP.
May 2008/1st Edition/R2.01 or later
Newly published.
n For Questions and More Information

Online Query: A query form is available on the following URL for online query.
http://www.yokogawa.com/iss/
If you want more information about Yokogawa products, you can visit
Yokogawas homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by
Process Automation Product Marketing Dept.

Industrial Automation Systems Business Div.

Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation

2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN
IM 32S04B30-21E

S04B3021

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

S04B3021

Uploaded by

Copyright:

Available Formats

Users

Read this chapter to learn about these details.

Chapter 4 Target Tests

Media No. IM 32S04B30-21E (CD)

3rd Edition : Dec.22,2009-00

ProSafe-RS Document Map

Workbench Users Guide

2nd Edition : Dec.15,2008-00

Indicates that main switch is ON.

Indicates that main switch is OFF.

1st Edition : May 30,2008-00

n Warning and Disclaimer

1st Edition : May 30,2008-00

l Commonly used Conventions throughout User manuals:

Character string enclosed by brackets ({ }):

Tagname TUN {-Window size} {=Display position}

l Conventions used to show Key or Button Operations:

Click the [OK] button.

l Conventions of User Defined Folder

2nd Edition : Dec.15,2008-00

Indicates important information required to understand operations or functions.

Indicates additional information.

Indicates a source to be referred to.

n Integration with CENTUM

2nd Edition : Dec.15,2008-00

n Regarding the Station Types

3rd Edition : Dec.22,2009-00

Copyright and Trademark Notices

3rd Edition : Dec.22,2009-00

Overview of ProSafe-RS System Tests................................................... 1-1

Test Procedure................................................................................................... 1-4

Overview of the Test Support Functions......................................................... 1-5

Hardware/Software Environment..................................................................... 1-6

SCS Project for the Test.................................................................................. 1-10

Logic Simulation Test Operations........................................................... 2-1

SCS Simulation Tests............................................................................... 3-1

Engineering of SCS Simulation Tests............................................................. 3-4

Engineering Procedure before Executing SCS Simulation Tests....... 3-6

Engineering Procedure after SCS Simulation Tests......................... 3-10

SCS Test Function Window ........................................................................... 3-12

Structure of the SCS Test Function Window.................................... 3-13

Procedure to Launch the SCS Test Function Window..................... 3-15

Procedure to Close the SCS Test Function Window........................ 3-20

Execution of SCS Simulation Tests............................................................... 3-21

Operations Unique to SCS Simulators............................................. 3-21

Preparation for Executing SCS Simulation Tests............................. 3-26

Test Support Functions in SCS Simulation Tests ............................ 3-29

SCS Maintenance Support Tool in SCS Simulation Tests................ 3-34

Virtual HIS in SCS Simulation Tests................................................. 3-37

Downloading to SCS Simulators...................................................... 3-38

Expanded Test Functions............................................................................... 3-39

Operation Environment of the Expanded Test Functions................. 3-41

Executing SCS Simulation Tests Using the Expanded

Tests Using Multiple SCS Simulators............................................................ 3-50

Test Environment for Inter-SCS Safety Communication/

Testing Inter-SCS Safety Communication/

Testing CENTUM Integration in Virtual Tests............................................... 3-56

3rd Edition : Dec.22,2009-00

Target Tests................................................................................................ 4-1

Overview of Target Tests................................................................................... 4-1

Target Test Operation (In Case On-line Change Download is not

Test Function Tools................................................................................... 5-1

Test Project Creating Tool................................................................................. 5-1

Project Attribute Tool......................................................................................... 5-3