S56H2021

Users
Manual
Integration with
FAST/TOOLS
IM 32S56H20-21E
IM 32S56H20-21E
2nd Edition

Introduction
ProSafe-RS can be integrated with FAST/TOOLS, a Yokogawa SCADA system. When ProSafe-
RS is integrated with FAST/TOOLS, the SCSs of ProSafe-RS system can be accessed by FAST/
TOOLS through Vnet/IP network. In this document, how to integrate ProSafe-RS with FAST/
TOOLS will be explained. It is important to fully understand the contents of this document for your
engineering and maintenance works.
Regarding the engineering details of FAST/TOOLS, you can refer to the Users Manual of
FAST/TOOLS. The document of ProSafe-RS Vnet/IP (IM 32S56H10-21E) provides information
about Vnet/IP in a standalone ProSafe-RS system and integrated system of ProSafe-RS and
CENTUM. For information on Vnet/IP when ProSafe-RS is integrated with FAST/TOOLS, please
read chapter 4 of Integration with FAST/TOOLS (this document).
This document consists of the following chapters:

Chapter 1
This chapter describes an overview on integration of ProSafe-RS and FAST/TOOLS
Chapter 2
This chapter explains the functions of the SCS in an integrated system of ProSafe-RS and FAST/
TOOLS.
Chapter 3
This chapter explains the engineering works regarding integration of ProSafe-RS and FAST/
TOOLS.
Chapter 4
This chapter explains the Vnet/IP network in an integrated system of ProSafe-RS and FAST/
TOOLS.
Media No. IM 32S56H20-21E (CD) 2nd Edition : Dec. 2009 (YK) IM 32S56H20-21E 2nd Edition : Dec.22,2009-00
All Rights Reserved Copyright 2008, Yokogawa Electric Corporation
ii
ProSafe-RS Document Map

Safety System
Engineering
Safety Manual
Guide
IM 32S01S10-21E IM 32S01C10-21E
Software
Safety Control Station Integration with Open Interfaces

Reference CENTUM VP/CS 3000
IM 32S03B10-21E IM 32S01E10-21E IM 32S05B10-21E
Engineering Utilities and Messages

Reference Maintenance
Reference
IM 32S04B10-21E IM 32S04B20-21E IM 32S02B10-21E
ProSafe-RS
Integration with
System Test
FAST/TOOLS Workbench Users Guide
Reference
IM 32S04B30-21E IM 32S56H20-21E
Hardware Vnet/IP
Safety Control
Communication ProSafe-RS
Stations
Devices Vnet/IP
(Hardware)
IM 32S06C10-21E IM 32S06H10-21E IM 32S56H10-21E
Installation
Installation Manual
Software Help
IM 32S01C50-21E
Read Me First
IM 32S56H20-21E 1st 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.

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.

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).
S0001TUN
Character string enclosed by brackets ({ }):

Indicates an option that can be omitted.
Example: Parameters for calling the tuning view on HIS.
Tag name 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

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).

vii
n About Explanation of System Behavior

In this manual, system behavior is explained assuming the use of the latest software and
hardware that Yokogawa provides at the publication of the manual. Wherever a topic needs
explanation of earlier revisions of software or hardware, a link to the required explanation is
provided so that you can read them according to your system.
n About Station Types

Safety control stations (SCS) are named as follows according to the CPU node (SSCx0S/
SSCx0D) and CPU module (SCP4x1) mounted in them.
SCSV1-S : SCS that uses SSC10S/SSC10D (SCP401 is installed)
SCSP1-S : SCS that uses SSC50S/SSC50D (SCP451 is installed)
SCSP2-S : SCS that uses SSC60S/SSC60D (SCP461 is installed)
To explain the functions of these different types of SCS, the following generic terms or
abbreviations may be used in this manual.
SCS : Generic term that denotes all types of SCS
SCSV : SCS connected on V net (this denotes SCSV1-S)
SCSP : SCS connected on Vnet/IP (this denotes SCSP1-S and SCSP2-S)
SCSV1 : Abbreviation for SCSV1-S
SCSP1 : Abbreviation for SCSP1-S
SCSP2 : Abbreviation for SCSP2-S
IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

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.

Toc-1
ProSafe-RS
Integration with FAST/TOOLS
IM 32S56H20-21E 2nd Edition
CONTENTS
1. Overview on Integration with FAST/TOOLS........................................... 1-1
2. SCS Functions Regarding FAST/TOOLS................................................ 2-1
2.1 SCS in FAST/TOOLS Integrated Environment................................................ 2-1
2.2 Tag Name Interface for FAST/TOOLS.............................................................. 2-2
3. Engineering Works for Integration with FAST/TOOLS.......................... 3-1
3.1 Domain Properties Setting Tool....................................................................... 3-2
3.1.1 Starting and Exiting the Tool............................................................... 3-2
3.1.2 Setting Domain Properties.................................................................. 3-6
3.1.3 Downloading Domain Properties........................................................ 3-8
3.1.4 Obtaining Actual Domain Property Settings....................................... 3-9
3.2 Definition of Tag Names.................................................................................. 3-10
4. Vnet/IP Network in FAST/TOOLS Integrated Environment................... 4-1
4.1 Overview of Vnet/IP Network............................................................................ 4-1
4.2 Vnet/IP Network System Configuration........................................................... 4-2
4.3 Vnet/IP Network Connections.......................................................................... 4-4
4.3.1 Connection within a Vnet/IP Domain.................................................. 4-4
4.3.2 Connection between Vnet/IP Domains............................................... 4-7
4.3.3 Vnet/IP Bus Status.............................................................................. 4-8
4.4 Time Synchronization of Vnet/IP.................................................................... 4-11
4.5 Engineering of Vnet/IP..................................................................................... 4-15
4.5.1 Setting Addresses on Hardware....................................................... 4-16
4.5.2 Setting the IP Addresses................................................................... 4-17
4.5.3 Procedures and Precautions for Adding a Station or Domain.......... 4-20

<1. Overview on Integration with FAST/TOOLS> 1-1
1. Overview on Integration with FAST/

TOOLS
The SCADA systems formed with FAST/TOOLS (a SCADA system) and STARDOM FCN/
FCJ autonomous controllers are applied to widely scattered oil wells and pipelines for
monitoring and controlling purposes.
By integrating the ProSafe-RS and FAST/TOOLS using the FAST/TOOLS Integration
Engineering Package, FAST/TOOLS can monitor and operate the safety control stations
(SCS) of the ProSafe-RS for a system like this.
Vnet/IP network is used for communications and by expanding the domain scale for
wider area, monitoring and controlling points scattered over a broad area can be linked.
If STARDOM devices are connected on the Vnet/IP network, open communication with
STARDOM is available.
The environment in which ProSafe-RS and FAST/TOOLS are integrated is referred to as
FAST/TOOLS integrated environment.
n System Configuration
A system configuration of FAST/TOOLS and ProSafe-RS integrated system is shown below.
STARDOM PRM Server/Field Domain A
SNTP Server Engineering Communication
FAST/TOOLS SENG
PC Server PRM Client
Vnet/IP (100 Mbps or more)
SCS SCS
SCS FCN/FCJ
L2SW
L2SW L2SW
FAST/TOOLS
(Redundant Server)
FCN/FCJ FCN/FCJ
1000 km
FAST/TOOLS: YOKOGAWA SCADA System

PRM: YOKOGAWA Plant Asset Management 1000 km 1000 km
System
SNTP Server: SCS SCS Domain B Domain C
Simple Network Time Protocol Server
FCN/FCJ: STARDOM Controller
L3SW L2SW L3SW L2SW
FCN/FCJ FCN/FCJ
010001E.ai
Figure FAST/TOOLS Integrated System

n Outlines of FAST/TOOLS Integrated System

The outlines of FAST/TOOLS integrated system is as follows:
Install the FAST/TOOLS Integration Engineering Package to the safety engineering PC
(SENG). Then define the domain properties and the tag names for the function blocks used
by FAST/TOOLS to access SCSs.
From FAST/TOOLS, the data of STARDOM FCN/FCJ and ProSafe-RS SCS can be
comprehensively monitored.
Vnet/IP is used as the communication bus for linking ProSafe-RS, FAST/TOOLS,
STARDOM and PRM.
The field devices connected to STARDOM and the field devices connected to ProSafe-RS
can be comprehensively managed through PRM.
IMPORTANT
Integration with FAST/TOOLS is certified as Interference-Free. The system should be configured
so that abnormalities in SCS and the devices connected to SCS are all detected by the ProSafe-
RS system, and the diagnosis information upon detection of abnormality should be confirmed on
SENG.
n Vnet/IP Network of FAST/TOOLS Integrated System
l Number of Domains
Up to 31 domains can be connected. (However, domains that include any CENTUM station
cannot be connected.)
l Standard Domain and Wide-Area Domain

You can select the scale of a domain either as standard or wide-area according to the distance
between stations in the domain. This selection can be made by using the Domain Properties
Setting Tool of ProSafe-RS.
If you select wide-area, the specifications of the domain will be as follows:
Communication speed: 100 Mbps or more
Distance between stations: Up to 1000 km (transmission delay is 40 ms or less)
If you select standard, the specifications of the domain will be as follows:
Communication speed: 1 Gbps
Distance between stations: Up to 40 km
l Redundancy of Open Communication

In the Vnet/IP network of a FAST/TOOLS integrated system, you can connect devices of open
communications (Vnet/IP open communication and TCP/IP open communication) also to Vnet/IP
bus 1. This enables dual-redundant communication between STARDOM FCN/FCJ and FAST/
TOOLS.
SEE
ALSO For more information about Vnet/IP network of a FAST/TOOLS integrated system, see the following:
4, Vnet/IP Network in FAST/TOOLS Integrated Environment

n Time Synchronization
There are two modes of Vnet/IP network time synchronization:
Vnet/IP time synchronization that uses the Vnet/IP time master for time synchronization
SNTP time synchronization that uses the time of the SNTP server connected to the Vnet/IP
network.
If STARDOM is connected to the network, SNTP time synchronization must be used.
SEE
ALSO For more information about connecting an SNTP server, see the users manual of STARDOM.
n Software Environment
The software that can be used for a FAST/TOOLS integrated system is as follows:
ProSafe-RS: R2.02 or later
FAST/TOOLS: R9.02 or later
STARDOM (FCN/FCJ): R2.01 or later
PRM: R3.03 or later
n Hardware Environment
For communications of the FAST/TOOLS integrated system, all the stations on the network that
include the following Vnet/IP-related hardware must support the wide-area domain specification.
VI702/VI701 (Vnet/IP nterface card installed in PC components such as SENG)
Firmware revision (F) should be 12 or later.
SCP461 (Processor module installed in SSC60S/SSC60D)
Any firmware revision.
SCP451 (Processor module installed in SSC50S/SSC50D)
Firmware revision (F1) should be 12 or later.
n Notes on Integration with FAST/TOOLS

The following items need to be noted when integrating ProSafe-RS and FAST/TOOLS.
IMPORTANT
Install FAST/TOOLS and SENG in different PCs.
Do not install CENTUM VP/CS 3000 Integration Engineering Package and FAST/TOOLS
Integration Engineering Package in the same PC.
Do not install any CENTUM software in SENG.
The Vnet/IP network of a CENTUM system and the Vnet/IP network of a FAST/TOOLS
integrated system must be physically segregated. Connection via a switch or a router is not
allowed, either.
Cannot be connected to a ProSafe-RS system built on a V net network.
Cannot be connected via Exaopc interface.

<2.1 SCS in FAST/TOOLS Integrated Environment> 2-1
2. SCS Functions Regarding FAST/

TOOLS
In this chapter, the SCS functions regarding the FAST/TOOLS integrated system will be
explained. FAST/TOOLS can access SCS data through the tag name (*1) interface.
*1: Tag names are the names given to the variables of SCS application logic to allow access by FAST/TOOLS.
2.1 SCS in FAST/TOOLS Integrated

Environment
SCS monitors the safety conditions of a plant and performs various controls to meet
various needs that require safety control. When using SCS in a FAST/TOOLS integrated
environment, the following points should be noted.
n Function Blocks Not Available in FAST/TOOLS Integrated Environment

In FAST/TOOLS integrated environment, the following SCS function blocks cannot be used. If
used, errors will occur when a build is performed on the SCS project.
Override: OVR_B, OVR_I,OVR_R, OVR_IB, OVR_IR, GOV_B, GOV_IB
Password: PASSWD
Manual Operation: MOB_21, MOB_11, MOB_RS, MOA
n System Common Switches

The status of SCS system common switch can be accessed from FAST/TOOLS by specifying
the element number (%SWXXXX).
SEE
ALSO For information on the accessible system common switches, see the following:
l Common Switches (Common Switches for System) in n Software Inputs/Outputs in D1, Integration
with CENTUM in the Safety Control Station Reference (IM 32S03B10-21E)
n Process Alarms
Process alarms should be managed by using the alarm management feature of FAST/TOOLS.
n System Alarms
System alarms should be confirmed on SENG using the SCS Maintenance Support Tools
Diagnostic Information window. However, system alarms can also be confirmed on FAST/TOOLS
SEE
ALSO For more information about alarm management on FAST/TOOLS, see the users manual of FAST/TOOLS.

<2.2 Tag Name Interface for FAST/TOOLS> 2-2
2.2 Tag Name Interface for FAST/TOOLS

If you define a tag name using Tag Name Builder for a function block or variable of SCS
that is accessible from FAST/TOOLS, a mapping block or mapping element is created for
it. FAST/TOOLS can read and write data through the tag name interface. However, some
mapping blocks and mapping elements are read-only.
n List of Mapping Blocks/Elements

FAST/TOOLS can automatically import the tag names defined on Tag Name Builder. However,
some mapping blocks/elements are not supported by FAST/TOOLS, and the tag names for
unsupported mapping blocks/elements cannot be imported. Even if the tag names are not
imported, their data can be accessed by FAST/TOOLS using the tag definition engineering
feature of FAST/TOOLS. The mapping blocks/elements that can be accessed by FAST/TOOLS
are as follows:
Table Mapping Blocks/Elements that can be Accessed by FAST/TOOLS
Type of Variable Defined in Application Logics Mapping Blocks/Elements

Access by FAST/
and Function Block/Element
Class Type Class TOOLS (*1)
Block Symbol
BOOL Internal variable BOOL Mapping element %WB
Integer (32-bit) Internal variable DINT Mapping element %WB R
Integer (32-bit) Internal variable REAL Mapping element %WB
Discrete I/O I/O structure IO_BOOL Mapping element %Z
R
Analog I/O I/O structure IO_REAL Mapping element %WB
Data Set (BOOL) Function block ECW_B Mapping element %WB
Data Set (Integer) Function block ECW_I Mapping element %WB R/W
Data Set (Real) Function block ECW_R Mapping element %WB
Analog Input with
Function block ANLG_S Mapping block S_ANLG_S R
Data Status
Analog Input
Function block ANLGI Mapping block S_ANLGI
indicator
Velocity Alarm Function block VEL Mapping block S_VEL
Annunciator Function block ANN Mapping element %AN R
First-up Alarm
Function block ANN_FUP Mapping element %AN R
Announciator
Subsystem
Communication Function block SCI_B Mapping element %WB R
Input (BOOL)
Subsystem
Communication Function block SCI_I Mapping element %WB
Input (Integer)
Subsystem
Communication Function block SCI_R Mapping element %WB R
Input (Real)
Subsystem
Communication Function block SCO_B Mapping element %WB R
Output (BOOL)
Subsystem
Communication Function block SCO_I Mapping element %WB
Output (Integer)
Subsystem
Communication Function block SCO_R Mapping element %WB R
Output (Real)
*1: R stands for Read, while W stands for Write. indicates that the tag name cannot be imported to FAST/TOOLS but can be
accessed by FAST/TOOLS after a specific engineering work is performed on FAST/TOOLS.

n Data Items of Mapping Blocks/Elements

FAST/TOOLS can access the following data items of mapping blocks/elements. The items are
indicated with R (Read) and W (Write) to show that FAST/TOOLS can read or write the data
items.
SEE
ALSO For more information about the data items of mapping elements, see the following:
D2, Tag Name Interfaces for CENTUM in the Safety Control Station Reference (IM 32S03B10-21E)
l Internal Variables
To access different types of internal variables, use the following data items of the corresponding
mapping element.
Table Accessible Data Items of Mapping Elements for Internal Variables
Type (Mapping Element) Data Item Range R/W
BOOL (%WB) PV 0, 1 R
DINT (%WB) PVI32 32-bit signed integer R
REAL (%WB) PVF32 Single-precision real R
l I/O Variables
To access different types of I/O variables, use the following data items of the corresponding
mapping element.
Table Accessible Data Items of Mapping Elements for I/O Variables
IO_BOOL (%Z) PV 0, 1 R
IO_REAL (%WB) PVF32 Single-precision real R
l External Communication Function Block

To access data of function blocks, use the following data items of the corresponding mapping
element.
Table Accessible Data Items of Mapping Elements for External Communication Function Blocks
ECW_B (%WB) PV 0, 1 R
ECW_I (%WB) PVI32 32-bit signed integer R
ECW_R (%WB) PVF32 Single-precision real R

l Analog Input with Data Status
To access data of function block ANLG_S, use the following data items of mapping block S_
ANLG_S.
Table Data Items of Mapping Block (S_ANLG_S) for ANLG_S
Data Item Range R/W
MODE Mode of the block R
ALRM Alarm status R
AOFS 0, 1 R/W (*1)
INV 0 - 100% R
PV Engineering unit data range after scale conversion R
HH (*2) R
PH (*2) R
PL (*2) R
LL (*2) R
HYS (*2) R
SH (*3) R
SL (*3) R
*1: Writing to this data item does not change the SCS action. The value is reset to 0 after restarting SCS.
*2: The value of the data item of ANLG_S with the same name is reflected as is.
*3: The value defined on Tag Name Builder.
l Annunciator
To access data of function block ANN or ANN_FUP, use the following data items of %AN. Use
Tag Name Builder to define the annunciator message.
Table Data items of Mapping Element (%AN) for ANN/ANN_FUP
Data Item Range R/W
ALRM Alarm status R
AOFS 0, 1 R/W
PV 0, 1 R
l Subsystem Communication I/O Function Blocks

To access data of the subsystem communication I/O function blocks, use the following data items
of the corresponding mapping element.
Table Data Items of Mapping Elements for Subsystem Communication I/O Function Blocks
SCI_B (%WB) PV 0, 1 R
SCI_R (%WB) PVF32 Single-precision real R
SCO_B (%WB) PV 0, 1 R
SCO_R (%WB) PVF32 Single-precision real R

<3. Engineering Works for Integration with FAST/TOOLS> 3-1
3. Engineering Works for Integration

with FAST/TOOLS
When the FAST/TOOLS Integration Engineering Package is installed, the following
engineering functions are available:
Domain Properties Setting Tool
Tag Name Builder (Including self-documentation)
To integrate ProSafe-RS with FAST/TOOLS, you need to do the following engineering
works using these functions:
Set up domain properties using Domain Properties Setting Tool
Define tag names using Tag Name Builder.
This chapter will describe how to use the above engineering tool and builder to perform
the engineering works.
n Notes on Engineering Works

When performing engineering works for integration with FAST/TOOLS, the following items must
be noted:
l SCS Constant Builder

In the FAST/TOOLS integrated environment, the following SCS process alarm settings have no
effect:
Interval of Repeated Warning Alarms
Alarm Notify Action When AOF Released
l Interface with PRM

If you install the SOE OPC interface package to SENG PC, PRM can obtain all the SENG
diagnostic information messages through the OPC server for SENG. Since CENTUM HIS is not
connected, those system alarms that would be generated on HIS in a CENTUM system cannot
be obtained (for example, system alarms regarding Vnet/IP network are not obtainable).
n Testing in a FAST/TOOLS Integrated Environment

In a FAST/TOOLS integrated system, SCS simulator cannot be used. The actions can be
checked through logic simulation test or target test.
SEE
ALSO For more information about logic simulation test and target test, see the following chapters in ProSafe-RS
System Test Reference (IM 32S04B30-21E).
2, Logic Simulation Test Operations
4, Target Tests

<3.1 Domain Properties Setting Tool> 3-2
3.1 Domain Properties Setting Tool

Domain Properties Setting Tool is used to define the properties of the Vnet/IP domains for
a project where ProSafe-RS is integrated with FAST/TOOLS. You can define the maximum
distance between stations, the time groups, and IP addresses of the SNTP server as
domain properties and download them to the Vnet/IP domains.
3.1.1 Starting and Exiting the Tool

The procedure to start and exit the Domain Properties Setting Tool is shown below:
Obtain domain property settings from Check to see if the settings on the Domain Properties Setting Tool
stations and check them match the actual settings.
Set domain properties
Save the settings
Download the settings
Obtain domain property settings from Make sure that the new settings on the tool have been
stations and check them downloaded properly.
030101E.ai
Figure Procedure of Using Domain Properties Setting Tool

n Start Domain Properties Setting Tool

1. From the Windows Start menu, choose [YOKOGAWA ProSafe] [Domain Properties
Setting Tool] (*1).
*1: [Domain Properties Setting Tool] only appears on [YOKOGAWA ProSafe] menu when the FAST/TOOLS Integration Engineering
Package (CHS5700) is installed.
2. When the dialog box for browsing the folder is displayed, choose an RS-Project folder.
Browse for Folder
Select the RS project.
Computer
Floppy Disk Drive (A:)
Local Disk (C:)
Program Files
RS-Projects
RSPJT_1
MYRSPJT
Users
Windows
OK Cancel
030102E.ai
Figure Browse for Folder Dialog Box
When you start the Domain Properties Setting Tool for the second time or more, the Browse
for Folder dialog box opens with the path to the previously selected RS-Project folder being
selected.
If you choose a folder that is not an RS-project folder and click the [OK] button, an error
message will be displayed. In this case, choose an RS-Project folder in the dialog box.
3. Click the [OK] button. And then Domain Properties Setting Tool will start.

n Components of Domain Properties Setting Tool Window

This section describes the components of Domain Properties Setting Tool.
List of domain properties
Domain Properties Setting Tool - [RSPjt:MYRSPJT File:DomainProperty.l]

File Load View
In-use Domain Time Group Area SNTP Bus 1 SNTP Bus 2 Comment
01 1 Wide-area
02 1 Wide-area
03 1 Wide-area
04 1 Standard
05 1 Standard
06 1 Standard
07 1 Standard
08 1 Standard
09 1 Standard
10 1 Standard
11 1 Standard
12 1 Standard
13 1 Standard
14 1 Standard
15 1 Standard
16 1 Standard
Message
--- Error = 0 Warning = 0 ---
Ready Position: Line 1 Column 1
Message display area

030103E.ai
Figure Domain Properties Setting Tool

l Tools Menus and Buttons
The functions available from the tools menu bar and the buttons on the tool bar are explained
below.
Table Tools Menus and Buttons
Menu Button Description
Specifies an RS project.
Use this button to choose another RS project for which you wish
Open to set domain properties.
When you specify a new RS project, the current window is
closed and a new window opens for the specified RS project.
File Save Saves the settings you have made on the tool.
Print Prints the settings you have made on the tool.
Exit Domain Properties

Exits the tool.
Setting Tool
Download Downloads the settings of the selected domain.
Load Download to all Domains Downloads the settings of all domains.
Get Domain Statuses Uploads the domain property settings from all domains.
l List of Domain Properties

The property settings of all domains are listed. You can enter property settings on the list. The
details of each setting item will be explained in the next section.
l Message Display Area

Messages are displayed in this area when you execute downloading or uploading of the settings.
n Exiting the Tool

Choose [File] [Exit Domain Properties Setting Tool] from menu bar or click the Close button at
the upper-right corner of the tool window to exit the tool.
If the edited contents have not been saved, a dialog box will be displayed to prompt for saving the
contents. Save the changes if necessary and then exit the tool.

3.1.2 Setting Domain Properties

In the list of domain properties, first select the domain number check box of a domain,
and then define the properties of the domain.
n Property Items
l In-Use
Specifies whether the domain is used or not. You need to select the domain number check box
of a domain for use. You can set the properties of the domains specified for use. By default, this
check box is not selected.
l Time Group
Sets the time group (0 to 7) of the domain. If a number between 1 and 7 is set, this domain will
synchronize its clock with other domains of the same group. If 0 is set, the domain will only
synchronize the clocks within the domain.
SEE
ALSO For more information about the time group, see the following:
n Time Group in 4.4, Time Synchronization of Vnet/IP
l Area
Selects the size of a domain area, i.e., the distance between stations. If Standard is selected, the
maximum distance between stations is 40 km. If Wide-Area is selected, the maximum distance
between stations is 1000 km. The default setting is Standard.
l SNTP Bus 1
Sets the IP address of the SNTP server connected to Bus 1. To set the IP address, click the cell
and enter the IP address in the form of nnn.nnn.nnn.nnn. If the entered address is beyond the
range, the cell will turn red and an error message is displayed.
l SNTP Bus 2
Sets the IP address of the SNTP server connected to Bus 2. To set the IP address, click the cell
and enter the IP address in the form of nnn.nnn.nnn.nnn. If the entered address is beyond the
range, the cell will turn red and an error message is displayed.
SEE
ALSO For more information about the IP address of SNTP server, see the following:
n SNTP Server in 4.4, Time Synchronization of Vnet/IP
l Comment
You can set a comment for each domain. A comment may be up to 32 alphanumeric characters
long.
Click the cell and then enter the comment.

n Saving Domain Properties

After entering all the settings of the domain properties, save the properties you have set. Choose
[File] [Save] from menu bar or click the Save button on the toolbar. The properties are saved for
each RS project.
n Print Defined Properties

Choose [File] [Print] from the menu bar or click the Print button on the toolbar to print the
domain properties you have set. The properties of the domains specified for use will be printed
out.
Domain properties Mon Jun 09 10:20:26 2008
RS Project Path : \\PC1\RS-Projects\MYRSPJT
Domain Time Group Area SNTP Bus 1 SNTP Bus 2 Comment

------------------------------------------------------------------------------------------------------------------------------------------
01 1 Wide-area Site-A1
02 1 Wide-area 192.168.2.220 192.168.130.220 Site-A2
03 1 Wide-area Site-A3
11 1 Standard Site-B1
030104E.ai
Figure Printout of Domain Properties

3.1.3 Downloading Domain Properties

The defined domain properties need to be downloaded to the corresponding domains.
Downloading can be performed for an individual domain or for all the domains. The result
of downloading will be displayed in the message display area. Before downloading, it is
necessary to save the defined properties.
n Downloading the Properties of One Domain

1. In the list of domain properties, choose the line of the domain for downloading. The line will
be highlighted. (You cannot choose multiple domains.)
2. Choose [Load] [Download] from menu bar or click the Download button on the toolbar.
3. Click [OK] in the confirmation dialog box for downloading. Downloading to the selected
domain starts. If the properties have not yet been saved, a message will be displayed to
prompt for saving the properties. Click [OK] to save and continue the downloading.
n Downloading the Properties of All Domains

1. Choose [Load] [Download to All Domains] from the menu bar or click the Download to All
Domains button on the toolbar.
2. Click [OK] in the confirmation dialog box for downloading. Downloading starts for all the
domains specified for use. If the properties have not yet been saved, a message box
will be displayed to prompt for saving the properties. Click [OK] to save and continue the
downloading.
n Error Messages
If you start downloading under the following circumstances, an error message will be displayed in
the message display area and the downloading cannot continue.
The domain for downloading is not a Vnet/IP domain.
The domain for downloading is a Wide-Area domain but the domain contains any Vnet/IP
station that does not support wide-area domain (i.e. the firmware revision is earlier than
Rev.12).

3.1.4 Obtaining Actual Domain Property Settings

You can upload the domain properties that are actually set in the domains and check if
they match the settings made on the tool.
n Procedure to Obtain Domain Properties

1. Choose [Load] [Get Domain Statuses] from the menu bar or click the Get Domain
Statuses button on the toolbar.
2. Click [OK] in the confirmation dialog box. The actually used properties are uploaded from
the domains specified for use.
The obtained domain properties will be displayed in the message display area as follows:
Dom: 01 Group: 1 Area: Standard SNTP Bus 1: SNTP Bus 2: WideAreaSupport: No
Dom: 02 Group: 1 Area: WideArea SNTP Bus 1: 192.168.2.220 SNTP Bus 2: 192.168.130.220 WideAreaSupport: Yes
030105E.ai
Notes: If the Wide-Area Support option is indicated as Yes, it means that all the Vnet/IP hardware-installed stations in that domain
are supporting Wide-Area domain.
If blank is indicated for SNTP Bus 1 or SNTP Bus 2, it means that the default SNTP server address is used.
Figure Example of Obtained Domain Properties

<3.2 Definition of Tag Names> 3-10
3.2 Definition of Tag Names

To allow FAST/TOOLS to access SCS application logic variables and function blocks, tag
names must be defined using Tag Name Builder.
n Overview of Tag Name Definition

Use Tag Name Builder to define tag names for the variables and function blocks in the application
logic that need to be accessed from FAST/TOOLS.
With a tag name defined, the function block or variable is associated with its corresponding
mapping block or element, and becomes accessible from FAST/TOOLS by designating in the
form Tag name.Data item.
The procedure for defining tag names is as follows:
1. Define the application logic variables and function block instances in Dictionary View of SCS
Manager.
2. Define tag names and parameters in Tag Name Builder.
To start the Tag Name Builder, do the following:
From the SCS Manager, click [Tools] [Engineering] to start the Engineering Launcher, and
select [Tag Name Builder] from the menu.
3. Execute a build on SCS Manager to generate SCS databases and download them to SCS.
4. In order to pass the contents defined on Tag Name Builder to FAST/TOOLS, export the
contents defined on Tag Name Builder into a CSV file and import this CSV file into FAST/
TOOLS.
IMPORTANT
Changes made to the definitions for a tag name that is already imported will not be reflected in
FAST/TOOLS by the above mentioned procedure. To change the definitions for already imported
tag names, you need to work on both Tag Name Builder and FAST/TOOLS.

n Window of Tag Name Builder

The following figure shows the main window of Tag Name Builder:
Title bar Menu bar Tool bar
Tag Name Builder - [Pjt:SCS1020 File:TAG.edf]

File Edit View Tool Window
ECW_R
Variable Name BOOL/ECW_B DINT/REAL/ECW_I/ECW_R ANLGI/ANLG_S VEL ANN

ABS001_Q@Select1FB Variable Name Tag Name Unit Level
ABS002_Q@Select1FB
ABS001_IN@Select1FBD ABS001_IN % 4 Gener
ACOS_Q@Interference
ANLGI001_HYS@HISIF ABS002_IN@Select1FBD % 4 Gener
ANLGI001_IN@HISIFFB ACOS_IN@InterferenceF % 4 Gener
ANLGI001_LL@HISIFFB
ANLGI001_HH@HISIFFB % 4 Gener
ANLGI001_OUT@HISIF
ANLGI001_PH@HISIFF % 4 Gener
ANLGI001_PL@HISIFFB
ANLGI001_SH@HISIFF
ANLGI002_HH@HISIFF
Message
Ready Position: Line 5 Column 1 Change
Status bar Data menu area Workspace Message display area
030201E.ai
Figure Main Window of Tag Name Builder

n Setting Items of Tag Name Builder

This section describes the items you need to set on Tag Name Builder for a FAST/TOOLS
integrated system.
The following table shows the items on Tag Name Builder that have effect in a FAST/TOOLS
integrated system. Other items are displayed in gray and cannot be set. The Tag Name Builder
window comprises tab pages provided for each group of variable types shown in this table.
The settings you have made can be printed out by self-documentation.
Table Variable Types and Items on Tag Name Builder
Variable Type
DINT
Item BOOL REAL ANN SCI_B SCI_R
ANLG_S IO_REAL IO_BOOL
ECW_B ECW_I ANN_FUP SCO_B SCO_R
ECW_R
Variable Name x x x x x x x x
Element Name

(*1)
Type (*2)
Comment (*3)
Tag Name x x x x (*4) x x x x
Tag Comment x x x x x x x
Annunciator
Message x
Low Limit x
High Limit x
Unit x x x x
x: Settable
: Read-only
Blank: Not available
*1: This item is only displayed in the ANN/ANN_FUP tab, and the element names %AN0001 to %AN1000 are listed for SCSP1 and
%AN0001 to %AN2000 for SCSP2.
*2: The variable types defined on Dictionary View are displayed. This item is not displayed in the tabs for a single variable type.
*3: The variable comments defined on Dictionary View are displayed.
*4: Tag name specification is optional. FAST/TOOLS can access ANN or ANN_FUP by using element names instead of tag names.
Element names are %AN0001 to %AN1000 for SCSP1, and %AN0001 to %AN2000 for SCSP2.

Each setting item will be explained below.
l Variable Name
Among the variables created on SCS Manager, specify the variable name you want to assign
a tag name. To assign a tag name to a function block instance, enter the instance name as the
variable name. A tag name can be defined regardless of the scope of the variable.
In the case of a local variable, enter a scope name after @. In the case of an internal variable of
a user-defined function block, assign an instance name using Dictionary View of SCS Manager.
The variable name is specified in the format of [InstanceName].[Internal Variable Name], and
up to two nests are permitted in each variable to which a tag name is assigned.
Table Examples of Variable Name Specification
Variable Name Scope Description
VAR1 Global Global variable
VAR2@PROG1 PROG1 Local variable of PROG1 function
FB01.VAR3 Global Internal variable VAR3 of user-defined function block instance FB01
Internal variable VAR3 of user-defined function block instance FB01
FB01.VAR3@PROG1 PROG1
defined locally in PROG1 function
Internal variable VAR3 of user-defined function block instance FB2,
FB01.FB2.VAR3 Global which is used in user-defined function block instance FB01 (maximum
limit of function block nesting)
Note: The variable name can contain up to 69 single-byte characters. Tag Name Builder also checks the following items:
The variable name consists only of alphanumeric characters and @, . or _. Otherwise, an error will occur.
The variable name begins with an alphabetic character or _; otherwise, an error will occur.
In the above table, FB01.VAR3 and FB01.VAR3@PROG1 have one nest, while FB01.FB2.VAR3 has two nests. Three
nests or more will result in an error.
l Tag Name
A name used to access each application logic variable from FAST/TOOLS. A tag name can
contain up to 16 single-byte alphanumeric characters including _ and -. Note that tag names
cannot begin with _ or -. All characters are converted to uppercase as they are entered. Tag
names must be unique within an SCS.
l Tag Comment
A comment assigned to each tag name. A tag comment can be defined using up to 24 single-byte
characters.
l Annunciator Message
A message used by an ANN or ANN_FUP function block. An annunciator message can be
defined using up to 80 single-byte characters.
Default: None
l Unit
A symbol indicating the engineering unit of data such as flow rate and pressure. A unit can be
defined using up to six single-byte characters.
Default: %

l Low Limit
A low limit (SL) is the lowest point of engineering data scale. It can be defined using up to seven
digits including a sign and decimal point. This setting is referenced by FAST/TOOLS only for
display purposes and not used in calculation or alarm processing of the SCS. Enter the same
value as the Low limit set on Multi-Language Editor, although a different value can be set.
Default: 0.0
l High Limit
A high limit (SH) is the highest point of engineering data scale. It can be defined using up to
seven digits including a sign and decimal point. This setting is referenced by FAST/TOOLS only
for display purposes and not used in calculation or alarm processing of the SCS. Enter the same
value as the High limit set on Multi-Language Editor, although a different value can be set.
Default: 100.0
TIP
When a builder file (*.edf), a file saved with another name (*.sva), or a CSV file (*.csv) is imported on Tag Name
Builder, the setting items that cannot be used on FAST/TOOLS are not imported and the default values will be
used.

<4.1 Overview of Vnet/IP Network> 4-1
4. Vnet/IP Network in FAST/TOOLS

Integrated Environment
4.1 Overview of Vnet/IP Network

Vnet/IP achieves a high-speed control network while conforming to the IEEE802.3 and
TCP/IP communication standards. It is designed as a redundant network and conducts
control communication and open communication using the standard Ethernet protocols
on two communication channels of bus 1 and bus 2. You can use commercially available
Ethernet communication devices to configure a network.
n Network Conforming to IEEE802.3 and TCP/IP

Vnet/IP is a network that conforms to the IEEE802.3 and TCP/IP communication standards.
It supports a transmission speed of 1 Gbps or 100 Mbps. It has two independent communication
channels for control communication and open communication.
Control communication is the communication for transferring control data. The inter-SCS safety
communication is performed as control communication.
Open communication is the communication conducted by using the various standard protocols of
Ethernet.
Open communications can take place in two types: Vnet/IP open communication and general
open communication.
Vnet/IP open communication is performed by the devices in which a Vnet/IP interface card is
installed. General open communication is performed by general-purpose Ethernet devices in
which a Vnet/IP interface card is not installed.
Commercially available general purpose communication devices such as transmission media
(Ethernet cables), Layer 2 switches, Layer 3 switches and routers can be used as the hardware
for a Vnet/IP network.
n Communication Channels of Control Communication and Open

Communication
Vnet/IP is designed as a redundant network. In Vnet/IP, redundancy is achieved with
independent subnets on bus 1 and bus 2.
For the communication between Vnet/IP stations, they normally use bus 1 for the control
communication. If a communication error occurs on bus 1 for some reason, they use bus 2
for control communication. Since bus 2 is normally used for open communication, control
communication and open communication coexist on bus 2. In this situation, the band for open
communication is restricted in order to secure the band for control communication.
Basically, open communication is performed using bus 2. However, open communications can
be made redundant if bus switching is done by an application. In this case, the band for open
communication will be restricted because control communication and open communication
coexist on bus 1.

<4.2 Vnet/IP Network System Configuration> 4-2
4.2 Vnet/IP Network System Configuration

In this section, devices in the system that forms a Vnet/IP network will be explained.
IMPORTANT
In the ProSafe-RS system where the FAST/TOOLS Integration Package is installed, ensure that
no path connects to a V net or CENTUM Vnet/IP network.
n System Configuration
l Vnet/IP Station
The Vnet/IP station in a domain is connected to a Layer 2 switch in each bus.
SENG
A general-purpose PC is connected to the Vnet/IP network through a Vnet/IP interface
card (VI702/VI701) installed in it. The VI702/VI701 card has two ports of connectors for
connection to the Vnet/IP communication cables to support redundancy of Vnet/IP buses.
SCSP (SSC60S, SSC60D, SSC50S, SSC50D)
SCSP is a Safety Control Station that can be connected in the Vnet/IP network.
PRM
PRM is an asset management system provided by Yokogawa Electric Corporation.
FAST/TOOLS
FAST/TOOLS is a SCADA system provided by Yokogawa Electric Corporation.
l Vnet/IP Domain
A Vnet/IP domain consists of two independent subnets on each bus.
l Layer 2 Switch
The Vnet/IP stations and general-purpose Ethernet devices in a domain are connected to each
bus through Layer 2 switches (L2SW). At least one Layer 2 switch is required for each bus.
l Layer 3 Switch
Layer 3 switches (L3SW) are used to connect Vnet/IP domains and provided for each bus.
l Router
Routers with security capabilities should be used if you connect bus 2 with an external network
such as Intranet to ensure security of the Vnet/IP network.

<4.2 Vnet/IP Network System Configuration> 4-3
l Ethernet Device
STARDOM stations and general-purpose Ethernet devices in which a Vnet/IP interface card is
not installed are connected to bus 2 of Vnet/IP.
IMPORTANT
When the band used by Vnet/IP is 100 Mbps, control the traffic flowing from general-
purpose Ethernet devices into a Vnet/IP network according to the engineering guidelines of
FAST/TOOLS.
When the band used by Vnet/IP is 1 Gbps, use a hub to control the traffic flowing from
general-purpose Ethernet devices to a Vnet/IP network so as to prevent it from exceeding
300 Mbps (for example, three 100 Mbps ports).
STARDOM Controller
Open communication is performed between a STARDOM controller (FCN/FCJ) and a
ProSafe-RS station (SCSP or SENG), and control communication is not performed.
A network of STARDOM controllers can be configured for redundancy by using bus 2 as the
primary bus and bus 1 as the secondary bus.
General-purpose Ethernet Device
To connect Vnet/IP with an external network such as Intranet, separate the network using a
router.
IMPORTANT
When you connect SCSPs in a network where general-purpose Ethernet devices are
connected, use intelligent switches as Layer 2 switches in order to prevent multicasting of open
communication from flowing into the SCSPs.
SEE
ALSO For more information about selecting Layer 2 switches for use in the network, see the Vnet/IP Network
Configuration Guide (TI 33P01B10-31E).

<4.3 Vnet/IP Network Connections> 4-4
4.3 Vnet/IP Network Connections

This section describes the various types of connections required to build a Vnet/IP
network and the communication statuses of the control bus.
Connection in a Vnet/IP domain
Connection between Vnet/IP domains
4.3.1 Connection within a Vnet/IP Domain

Devices in a Vnet/IP domain are connected in a star topology using a Layer 2 switch as
the central device. Since the redundantly configured Vnet/IP buses must be separated as
independent subnets on each bus, it is necessary to install a Layer 2 switch for each bus.
IMPORTANT
Multiple stations are connected to Layer 2 switches. It is strongly recommended to provide an
uninterruptible power supply (UPS) for Layer 2 switches so that they will not stop due to power
failure.
If the Layer 2 switches stop due to power failure, there will be the following effects:
A communication error will occur if Layer 2 switches for the buses stop due to power failure.
For dual-redundant SCSP, when the Layer 2 switches for both buses fail, the controlling
CPU will also fail and the control will be switched to the standby CPU. Then the dual-
redundant stations will run in non-redundant mode.
If a Layer 2 switch is restarted after momentary power failure, it takes several seconds for
the communication with stations to recover.

n Specifications of Network Connection within a Vnet/IP Domain

Standard or wide-area setting can be selected as the extended specification of the Vnet/IP
domain.
The specifications of network connection within a Vnet/IP domain are shown below for each
case:
l Number of Units that can be Connected

Number of Vnet/IP stations: Max. 64 stations
Ethernet devices (PCs, routers, STARDOM controllers etc.): Max. 124 devices
l When Wide-area Domain is Selected

Distance between Vnet/IP stations: Max. 1000 km
Transmission delay: 40 ms or less
Levels of Layer 2 switches: No limit
l When Standard Domain is Selected

Distance between Vnet/IP stations: Max. 40 km
Levels of Layer 2 switches: Max. 7 levels
Distance between Layer 2 switch and station:
Max. 100 m (when UTP (Unshielded Twisted Pair) cable is used),
Max. 5 km (when optical fiber cable is used)
Connecting distance between Layer 2 switches:
Max. 5 km (when optical fiber cable is used)
IMPORTANT
Avoid the connection in which multiple communication routes exist between any two stations.
Otherwise, the communication may not be properly performed.
SCSP SCSP
L2SW L2SW
L2SW
040301E.ai
Figure Improper Connection
TIP
As for a dual-redundantly configured SCSP station, both the controlling-side and standby-side CPU modules are
connected to a Layer 2 switch with UTP cables, but the SCSP is counted as one station.

SENG
UTP cable
Bus 1 side Bus 2 side

L2SW L2SW
Optical fiber
cable
L2SW L2SW
SCSP
L2SW: Layer 2 switch

040302E.ai
Figure Example of Connecting Devices in a Vnet/IP Domain

4.3.2 Connection between Vnet/IP Domains

A Layer 3 switch is required for the connection between Vnet/IP domains. Install a Layer 3
switch for each of the dual-redundantly configured Vnet/IP buses and connect it to other
domains. By connecting multiple domains using a leased line, a network of domains can
be established over a broad area.
n Specification when Connecting between Vnet/IP Domains

The specification of connection between Vnet/IP domains is as follows:
Multi-level connection of Vnet/IP domains: Max. 15 levels (16 layers) of Layer 3 switches
Transmission delay between any domains: Less than 250 ms
IMPORTANT
Avoid the connection in which multiple communication routes exist between any two
domains. Otherwise, the communication may not be properly performed.
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW
040303E.ai
Figure Improper Connection
If inter-SCS safety communications are performed among domains in a wide-area network,

it is recommended that the band for communication be 100 Mbps or greater.
SEE
ALSO For more information about configuring a wide-area network among domains, see the following:
n Extended Network Configuration: SCSP in 2.22, FAST/TOOLS Integrated Configuration of the
Engineering Guide (IM 32S01C10-21E)
IM 32S56H20-21E 3rd Edition : Dec.22,2009-00

4.3.3 Vnet/IP Bus Status

How to check the Vnet/IP bus status will be explained in this section.
n Overview of Vnet/IP Bus Status

In the SCS State Management window of the SCS Maintenance Support Tool on SENG, the
communication status of the buses in the domain that contains the SCSP can be checked. By
creating an application logic using the system function block (SYS_NETST) that outputs the bus
status, the bus status can be output to an external alarm lamp for notification.
n Elements of the Vnet/IP Bus Status

The Vnet/IP bus status shows the communication status of the entire Vnet/IP network, i.e.,
the stations in all the connected domains, as well as the devices (such as Layer 3 switches)
connecting the domains. For example, if abnormality occurs in bus 1 of a station in domain 5
while you are monitoring through the SCS State Management window on an SENG of domain 1,
you can see the status of bus 1 of Vnet/IP indicating abnormality.
The Vnet/IP bus status consists of the following three elements:

Bus status in own domain
Communication status of devices connecting the domains
Bus status of other domains
Vnet/IP bus status

The information of a domain is
not broadcasted to stations beyond
the domain except the bus status.
Bus status in Bus status of

own domain other domains
Communication status Communication status Communication status

between stations of devices connected between stations
in own domain between domains in other domains
040304E.ai
Figure Elements of the Vnet/IP Bus Status

l Indication of the Status of Communication between Stations in a Domain
Each station in a Vnet/IP domain performs diagnosis of buses alternately using bus 1 and bus 2.
The communication status of one station includes the following types. A dual-redundant station
with dual CPU modules has the following four types.
A status of communication between the control side CPU module (*1) and the control side
CPU module of the station communicating with.
A status of communication between the control side CPU module (*1) and the stand-by side
CPU module of communicating with.
A status of communication between the stand-by side CPU module and the control side
CPU module (*1) of communicating with.
A status of communication between the standby side CPU module and the stand-by side
CPU module of communicating with.
*1: Including SENG and non-redundant stations (such as SCSP with single CPU module).
l Bus Status in a Domain

The bus status in a domain is created from the statuses of communications between stations in
each domain. If the bus status shows abnormality, the meaning varies with the type of failure as
follows:
Single failure (either bus 1 or bus 2 has failed)

When either bus 1 or bus 2 encounters communication error, the status of the bus will be
indicated as abnormal.
Multiple failures (both in bus 1 and bus 2)
If both buses encounter errors, the first one will be indicated as abnormal. Failure of both
buses cannot be indicated.
TIP
If both buses failed to communicate with a specific station, it will be indicated as the station failure, and the bus
status will not be indicated as abnormal.
l Communication Statuses of Devices Connecting Domains

Between Vnet/IP domains, communication is performed using bus 1 and bus 2, and the status of
communication between domains can be monitored.
The bus status of one domain can be broadcasted to all the stations in the Vnet/IP network
through the communication between the domains.

n Priority of the Vnet/IP Bus Status

The Vnet/IP bus status represents a summary of all communication statuses in the following
order:
Bus Status in Own Domain
If the bus status of own domain is abnormal, it is reflected in the Vnet/IP bus status. In the
case of a single failure, the status of that bus is handled as abnormal. In the case of multiple
failures, only the status of the bus in which abnormality is detected first is handled as
abnormal.
Communication Statuses of Devices Connecting Domains
If the bus status in own domain is normal, the communication statuses of devices
connecting domains are reflected in the Vnet/IP bus status. In the case of a single failure,
the status of that bus is handled as abnormal. In the case of multiple failures, only the status
of the bus in which abnormality is detected first is handled as abnormal.
Bus Statuses of Other Domains
If the communication statuses of all devices connecting domains are normal, the bus
statuses of other domains are reflected in the Vnet/IP bus status. However, even if a
different bus becomes abnormal in different domains, the Vnet/IP bus statuses of both
buses are not handled as abnormal, and only the status of the bus in which abnormality is
detected first is handled as abnormal.

<4.4 Time Synchronization of Vnet/IP> 4-11
4.4 Time Synchronization of Vnet/IP

Time synchronization is performed among stations connected to the Vnet/IP network.
An SNTP server connected to Vnet/IP can be used to get the reference time for time
synchronization.
n Overview of Time Synchronization

Time synchronization in a Vnet/IP network is performed in time group units. A time group is
defined for each domain. The time for the entire Vnet/IP network can be standardized by setting
the same time group number for all domains. When synchronizing the stations in a Vnet/IP
network with UTC (Universal Time Coordinated), an SNTP server needs to be connected in each
time group.
When an SNTP server is to be connected, engineering work is required using the Domain
Properties Setting Tool on SENG. The Vnet/IP stations in the time group to which an SNTP
server is connected will automatically synchronize with the SNTP sever time.
An overview of time synchronization for a Vnet/IP network is shown below.

Set up a time group for each domain.
The clocks in the SCSP and SENG stations are synchronized via the Vnet/IP time
synchronization.
If the SNTP server is not connected to the network or if the clock in the SNTP server is not
synchronized with the standard time, a Vnet/IP station within the time group becomes the
time master station. All the other stations within the time group will synchronize their times
with this time master station.
Time group 1 Time group 2

SNTP server SNTP server
SENG SENG
L3SW
Vnet/IP L3SW Vnet/IP
domain 1 domain 3
L3SW
L3SW L3SW
L3SW
SCSP SCSP
Vnet/IP
domain 2
SCSP
L3SW: Layer 3 switch
040401E.ai
Figure Time Synchronization of Vnet/IP
SEE
ALSO For more information about time synchronization, see the following:
n Precautions for Time Synchronization in 2.14, Time Synchronization in the Engineering Guide (IM
32S01C10-21E)

n Accuracy of Time Synchronization

Time management of Vnet/IP stations is performed through the control network.
All devices on a Vnet/IP network use a reference time to perform time synchronization for the
entire Vnet/IP network. This reference time is referred to as the network time. The relative
accuracies of the network time are separately explained for the cases where the wide-area
domain is selected and where the standard domain is selected.
Table Accuracy of Network Time (wide-area domain)
Station Relative time accuracy
5 ms. When one bus is abnormal, the accuracy may become worse than 5 ms due
In a domain/Among to heavy open communication traffic.
domains The relative time accuracy deteriorates in proportion to transmission delay time
variations among domains.
Table Accuracies of Network Time (standard domain)

Station Relative time accuracy
In a domain
to heavy open communication traffic.
to heavy open communication traffic.
Among domains
The relative time accuracy deteriorates in proportion to transmission delay time
variations among domains.
The system software of a Vnet/IP station references the network time, and adjusts its own system
time according to the network time. Because of the differences in the time adjustment methods,
the deviations between the system time and the network time are as shown below:
Table Accuracies of the System Time
Deviation from network
Station type Time adjustment method
time
The deviation between the network time and the
SENG or other stations
system time will be checked all the time. If the
operating on general- Max. 0.5 s
deviation exceeds 0.5 s, the system time will be
purpose PC
adjusted to the network time.
The system time always synchronizes with the
SCSP None
network time.
n Time Group
The time group denotes a range in which time synchronization is performed. The entire Vnet/IP
network can be defined as one time group. Alternatively, the range in which time synchronization
is performed can be limited by separating domains in the same Vnet/IP network into different time
groups.
Specify a time group using a number from 0 to 7. The default time group number is 1.
To perform time synchronization only in a domain, set the time group number to 0.
If an SNTP server does not exist in a time group, one of Vnet/IP stations in a time group will act
as the time master station, and other stations within the same time group will synchronize with
the network time of the time master station.

n Engineering on Time Group

A time group can be defined using the Domain Properties Setting Tool on SENG.
n SNTP Server
To synchronize the network time of a Vnet/IP station with the standard time, connect an SNTP
server in each time group. Only one SNTP server is connected within the same time group.
Generally, an SNTP server is connected to bus 1 of Vnet/IP. However, if time synchronization is
necessary with the devices that perform open communication, connect the SNTP server to bus 2.
For the dual-redundant SNTP servers, one more SNTP server needs to be added and connected
to the other bus. In this case, the time master station in the Vnet/IP network will synchronize the
time with the SNTP server that is synchronized with the standard time. If the SNTP server being
referenced fails, the time synchronization will be performed with the other SNTP server that is
normal.
IMPORTANT
If there is a notification that the SNTP server that exists in a time group is not synchronized with
the standard time, all the stations in the time group will synchronize their times with the time
master station in the Vnet/IP network. When the SNTP server time is synchronized again with
the standard time, all the stations in the time group will synchronize their times with the standard
time, instead of the time master station in the Vnet/IP network, at once.
The default IP address of an SNTP server connected to Vnet/IP is as follows.
IP address of an SNTP server connected to bus 1 of Vnet/IP:

192.168.<domain number>.254
IP address of an SNTP server connected to bus 2 of Vnet/IP:
192.168.<128 + domain number>.254
n Time Synchronization after Powering On

After a station is powered on, the time of that station gradually approaches the network time
of the same time group. In 5 seconds after the system startup, the relative time accuracy is 1
second, and in 5 minutes, the relative time accuracy becomes 1 ms.

n Time Synchronization of SCSP Stations

The system time of an SCSP station is synchronized with the Vnet/IP network time. Moreover,
the DI module installed in the SCSP also synchronizes its time with this network time through
SB/ESB buses.
If an SNTP server is available in the network, the SCSP stations can be synchronized with the
standard time. The accuracy of the synchronization with the standard time depends on the SNTP
server. If an SNTP server is not available in the network, the SCSP stations synchronize times
with the Vnet/IP network time master station.
The state of the time synchronization of SCSP stations, whether it is synchronized with the
standard time of SNTP server or not synchronized with the standard time but is synchronized
with the Vnet/IP time master station, can be found using the following function block or monitored
on the following window.
Output of the system function block (SYS_NETST)
SCS State Management window of the SCS Maintenance Support Tool of SENG
Even if the state of the time synchronization with the network time changes, no diagnostic
massage or system alarm is output to notify this event. If the time synchronization event needs to
be notified, create an application logic using the SYS_NETST function block to output the event
to an external alarm lamp or to an annunciator.
Note, however, that the Synchronous Mode of SCSP stations on the Communication tab of the
SCS Constants Builder should be set to [Vnet/IP] regardless the SNTP sever is available or not.
SEE
ALSO For more information about SOE in SCSP station, see the following:
A7, SOER in the Safety Control Station Reference (IM 32S03B10-21E)
For more information about SYS_NETST, see the following:
C10.4, SYS_NETST (Control Bus Status Indicator) in the Safety Control Station Reference (IM
32S03B10-21E)
For more information about SCS Constants Builder, see the following:
3.1.3, SCS Constants Builder in the Engineering Reference (IM 32S04B10-21E)
n Set Time from SENG

From the Set Time dialog box of the SCS Maintenance Support Tool on SENG, the network time
can be changed.
The times of all stations in the same time group can be adjusted. However, if an SNTP server
exists in the time group and the SNTP server is synchronized with the standard time, setting time
from SENG is ignored.

<4.5 Engineering of Vnet/IP> 4-15
4.5 Engineering of Vnet/IP

Engineering work to create Vnet/IP domains is performed on the SENG.
Prior to starting engineering, the following operations must be complete:
Install the ProSafe-RS system builders
Setup after installation
SEE
ALSO For more information about installation for creating Vnet/IP domains, see the following:
3.4, Installation and Setup of Vnet/IP in the Installation (IM 32S01C50-21E)
n Engineering for Building a System of Vnet/IP Domain

The engineering for building a system of Vnet/IP domain is as follows:
Network Engineering
Select the devices for building the Vnet/IP network, and then decide the IP addresses of the
devices.
Engineering for SCSP stations on SENG
On an SENG, define the SCSP stations and create the applications.
In this section, how to do the network engineering and setting the Vnet/IP addresses will be
explained.
IMPORTANT
For the SCSP stations on the Vnet/IP network that is connected with general-purpose Ethernet
devices, SCSP stations should be connected on the Layer 2 switches and the Layer 2 switches
should be the intelligent switches that can prevent the open communication multicasts flow into
the SCSP stations.
SEE
ALSO For more information about network configuration and Layer 2 switch, see the Vnet/IP Network
Configuration Guide (TI 33P01B10-31E).
For more information about the engineering for SCSP stations on SENG, see the following:
3, Engineering Works for Integration with FAST/TOOLS

4.5.1 Setting Addresses on Hardware

In this section, how to set the hardware addresses for Vnet/IP stations and the setting
items will be explained.
n Hardware Setting Items

The hardware setting items include the domain number and station number for each Vnet/IP
station. The Vnet/IP address will be automatically determined according to the domain number
and the station number set on the hardware.
If the station has dual-redundant CPU modules, the same domain and station numbers should be
set on both the control side and standby side. If the control side and standby side have different
numbers, the standby side cannot be started for dual-redundancy.
When setting the Vnet/IP link mode switch (FIX) on the CPU module of the SCSP station, Auto-
negotiation should be set as enabled.
By default, Auto-negotiation is enabled.
SEE
ALSO For more information about the hardware setting, see the following sections in the Safety Control Stations
(Hardware) (IM 32S06C10-21E):
4.2, Processor Module
6.7, Setting the Vnet/IP Interface Card Station Address
n Domain Number
The Vnet/IP domain number needs to be set within the range of 1 to 31.
The domain number can be set by the DIP switch on the hardware.
n Station Number
The Vnet/IP station number needs to be set within the range of 1 to 64. The station numbers in
the same domain should not be identical.
The station number can be set by the DIP switch on the hardware.

4.5.2 Setting the IP Addresses

This section describes how to set the IP addresses of a Vnet/IP station.
The following two types of IP addresses should be set by the user for the stations
connected on the Vnet/IP network.
Open Communication IP Address
This is the IP address used for various standard protocols of Ethernet.
Control Bus TCP/IP Protocol IP Address
This is the IP address used exclusively for TCP/IP applications over control bus
among SENG and SCSPs.
IMPORTANT
The IP address used by Vnet/IP station must not be identical with the IP address of other
communication device.
When SENG is sharing database with other SENG, if the network addresses of devices are
different, the names of other PCs in the hosts file should be edited for name resolution.
n Setting Open Communication IP Address

When performing communications using various standard protocols of Ethernet on a Vnet/IP
station, you need to set the open communication IP address for the station.
Set the open communication IP address for the Vnet/IP station mounted with the Vnet/IP
interface card (VI702/VI701). You can set the IP address using Windows Network Properties
dialog box, just like setting the general-purpose Ethernet ports.
The open communications are carried out on bus 2 or bus 1 of Vnet/IP network. The IP address
and the subnet mask for open communications are as follows:
Open Communication IP Address:

192.168.<128 + domain number>.<130> to 192.168.<128 + domain number>.<253>
Subnet mask: 255.255.255.0
l Example of Open Communication IP Address

An example of open communication IP address of SENG is described below:
[Example]
For the SENG with domain number 1, station number 64 and host address 200, the open
communication IP address of the SENG is as follows:
Open communication IP address = 192.168.<128 + domain number>.<host address>
= 192.168.129.200
Subnet mask = 255.255.255.0
SEE
ALSO For more information about setting SENG open communication IP address, see the following sections in the
Installation (IM 32S01C50-21E):
3.4.5, Setting Vnet/IP Network Connection (Windows Vista/Windows Server 2008)
3.4.6, Setting Vnet/IP Network Connection (Windows XP/Windows Server 2003)

TIP
IP Addresses of Vnet/IP Stations
A private address space from 192.168.1.0 to 192.168.255.255 is used as IP addresses for Vnet/IP stations.
The IP address for the control communication is automatically determined by the domain number, station number
and the bus system.
Therefore, you do not need to set the IP address for the control communication.
The IP addresses of Vnet/IP stations are described below:
Network Addresses
As the table below shows, the network address is determined by the bus system and domain number.
The subnet mask is 255.255.255.0.
Table Relationship between Bus System and IP Network Addresses

Bus system IP network address
Bus 1 192.168.<domain number>.<host address>
Bus 2 192.168.<128 + domain number>.<host address>
Host Addresses
The host address for the control communication of Vnet/IP is determined by the station number, and 2 to
129 are used. Other host addresses are used for the following purposes:
1: Reserved
130 to 253: For open communications
254: For SNTP sever
Example of Control Communication IP Addresses of Vnet/IP Station

An example of control communication IP addresses of SENG is described below.
These IP addresses will be automatically set in the SENG.
[Example]
For the SENG with domain number 1 and station number 64:
Network address of bus 1 = 192.168.<domain number>.0 = 192.168.1.0
Network address of bus 2 = 192.168.<128 + domain number>.0 = 192.168.129.0
The host address is determined by the following formula:
Host address = Station number x 2 = 64 x 2 = 128
Therefore, the IP addresses of the SENG for control communication are as follows:
Control communication IP address of bus 1 = 192.168.1.128
Control communication IP address of bus 2 = 192.168.129.128

n Setting the Control Bus TCP/IP Protocol IP Address

The control bus TCP/IP protocol IP address is the IP address used exclusively for TCP/IP
applications over control bus among SENG and SCSPs.
Set the control bus TCP/IP protocol IP address of SCSP using Hardware Architecture View of
SCS Manager.
Set the control bus TCP/IP protocol IP address of SENG using Windows Network Properties
dialog box.
The control bus TCP/IP protocol IP address can be determined according to its domain number
and station number as below:
Control Bus TCP/IP Protocol IP Address:

172.16.<domain number>.<station number>
Subnet mask: 255.255.0.0
SEE
ALSO For more information about setting SCS control bus TCP/IP protocol IP addresses, see the following:
n Setting an IP Address in 3.1.1, SCS Project Creation Procedure of the Engineering Reference (IM
32S04B10-21E)
For more information about setting SENG control bus TCP/IP protocol IP addresses, see the following
sections in the Installation (IM 32S01C50-21E):
3.4.5, Setting Vnet/IP Network Connection (Windows Vista)
3.4.6, Setting Vnet/IP Network Connection (Windows XP/Windows Server 2003)
n Setting the SNTP Server IP Address

Set the SNTP server IP address using the Domain Properties Setting Tool on SENG.
When the default IP address is used for the SNTP server, it is not necessary to enter an IP
address. (*1)
When the default IP address is not used, set the IP address.
*1: If the IP address field for the SNTP server is blank in the Domain Properties Setting Tool, it indicates that the default IP address is
being used.

4.5.3 Procedures and Precautions for Adding a Station or

Domain
This section describes the procedures and precautions that must be followed when you
add a station or a domain to a Vnet/IP network.
n Procedures and Precautions for Adding a Vnet/IP Station

Follow these steps to add a station to a Vnet/IP network.
WARNING
Before you add a station, make sure that there are no duplicate station addresses.
Turn off the power of the additional station before you connect the cables.
The procedures for two cases are provided below.
l Case 1: When using existing Layer 2 switches (ports are available on existing
Layer 2 switches)
1. On an SENG, select a project of a running SCS and call up an SCS status display window
(either SCS Status Overview or SCS State Management) of the SCS Maintenance Support
Tool. In the SCS status display window, check that both buses are normal.
2. Make sure that the additional station is not powered on.
3. Connect the BUS1 port of the additional station to the Layer 2 switch for BUS1 with a cable.
If the port on the Layer 2 switch is disabled, enable the port.
4. In the SCS status display window, check that both buses are normal.
5. Connect the BUS2 port of the additional station to the Layer 2 switch for BUS2 with a cable.
7. Turn on the power of the additional station.
TIP
Alternatively, you can add a station to Layer 3 switches directly instead of Layer 2 switches.

l Case 2: When you need to add Layer 2 switches (no ports are available on
existing Layer 2 switches)
Firstly, carry out steps 1 to 11 as shown below to add Layer 2 switches for BUS1 and BUS2.
Next, carry out the procedure for Case 1 above to add a station.
2. Disconnect the cable between any one of the existing stations and a Layer 2 switch for
BUS1.
3. Connect the additional Layer 2 switch for BUS1 to the existing Layer 2 switch for BUS1 with
a cable.
4. Turn on the power of the Layer 2 switch that you have added.
5. Connect the existing station that you have disconnected at step 2 to the newly added Layer
2 switch for BUS1 with a cable.
7. Disconnect the cable between any one of the existing stations and a Layer 2 switch for
BUS2.
8. Connect the additional Layer 2 switch for BUS2 and the existing Layer 2 switch for BUS2
with a cable.
9. Turn on the power of the Layer 2 switch that you have added.
10. Connect the existing station that you have disconnected at step 7 to the newly added Layer
2 switch for BUS2 with a cable.
This completes the addition of Layer 2 switches.

Now, carry out the procedure for Case 1 to add a station.

n Procedures and Precautions for Adding a Vnet/IP Domain

Follow these steps when you want to add a domain to a Vnet/IP network.
WARNING
Make sure that there are no duplicate station addresses (domain number + station number) in
the system.
The procedures for two cases are provided below.
l Case 1: When using existing Layer 3 switches (ports are available on existing
Layer 3 switches)
Firstly, carry out steps 1 to 5 as shown below to configure Layer 3 switches for BUS1 and BUS2.
Next, add stations by following the procedures in n Procedures and Precautions for Adding a
Vnet/IP Station.
2. Make the necessary settings on the existing Layer 3 switch for BUS1.
4. Make the necessary settings on the existing Layer 3 switch for BUS2.
This completes the configuration of Layer 3 switches.

Now, add stations for the new domain by following the procedures in n Procedures and
Precautions for Adding a Vnet/IP Station.

l Case 2: When you need to add Layer 3 switches (no ports are available on
existing Layer 3 switches)
Firstly, carry out steps 1 to 7 as shown below to add Layer 3 switches for BUS1 and BUS2. Next,
add stations by following the procedures in n Procedures and Precautions for Adding a Vnet/IP
Station.
2. Make the necessary settings on the Layer 3 switch for BUS1 that you are going to add.
3. Connect the additional Layer 3 switch for BUS1 to an existing Layer 2 or Layer 3 switch for
BUS1 with a cable.
5. Make the necessary settings on the Layer 3 switch for BUS2 that you are going to add.
6. Connect the additional Layer 3 switch for BUS2 and an existing Layer 2 or Layer 3 switch for
BUS2 with a cable.
This completes the addition of Layer 3 switches.

Now, add stations for the new domain by following the procedures in n Procedures and
Precautions for Adding a Vnet/IP Station.

Rev-1
Revision Information
Title : Integration with FAST/TOOLS
Manual No. : IM 32S56H20-21E
Dec.2009/2nd 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.
Chapter 1 Description in Hardware Environment was changed
2.2 First-up Alarm Announciator (ANN_FUP) was added.
3.2 Description was changed for newly added ANN_FUP. Description related to SCSP2 was added.
Chapter 4 SCS-IP was changed to SCSP.
4.2 VI702, SSC60S, and SSC60D were added.
4.5.3 Newly added (moved from supplement).
Dec.2008/1st Edition/R2.02 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

S56H2021

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

S56H2021

Uploaded by

Copyright:

Available Formats

Users

This document consists of the following chapters:

ProSafe-RS Document Map

Safety Control Station Integration with Open Interfaces

Engineering Utilities and Messages

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

Indicates that main switch is ON.

Indicates that main switch is OFF.

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

n Notes on Handling User Manuals

n Warning and Disclaimer

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

l Commonly used Conventions throughout User manuals:

Character strings in the following font and style:

Character string enclosed by brackets ({ }):

l Conventions used to show Key or Button Operations:

Characters enclosed by square brackets ([ ]):

l Conventions of User Defined Folder

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

Indicates a source to be referred to.

n Integration with CENTUM

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

n About Explanation of System Behavior

n About Station Types

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

Copyright and Trademark Notices

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

1. Overview on Integration with FAST/

Vnet/IP (100 Mbps or more)

FAST/TOOLS: YOKOGAWA SCADA System

L3SW L2SW L3SW L2SW

Figure FAST/TOOLS Integrated System

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

n Outlines of FAST/TOOLS Integrated System

n Vnet/IP Network of FAST/TOOLS Integrated System

l Standard Domain and Wide-Area Domain

l Redundancy of Open Communication

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

n Notes on Integration with FAST/TOOLS

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

2. SCS Functions Regarding FAST/

2.1 SCS in FAST/TOOLS Integrated

n Function Blocks Not Available in FAST/TOOLS Integrated Environment

n System Common Switches

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

2.2 Tag Name Interface for FAST/TOOLS

n List of Mapping Blocks/Elements

Type of Variable Defined in Application Logics Mapping Blocks/Elements

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

n Data Items of Mapping Blocks/Elements

l External Communication Function Block

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

l Subsystem Communication I/O Function Blocks

IM 32S56H20-21E 2nd Edition : Dec.22,2009-00

3. Engineering Works for Integration

n Notes on Engineering Works

l SCS Constant Builder

l Interface with PRM

n Testing in a FAST/TOOLS Integrated Environment

IM 32S56H20-21E 1st Edition : Dec.15,2008-00

3.1 Domain Properties Setting Tool

3.1.1 Starting and Exiting the Tool

Set domain properties