Prosafe-Rs Vnet/Ip: User'S Manual

User's
Manual
ProSafe-RS
Vnet/IP
IM 32Q56H10-31E
IM 32Q56H10-31E
4th Edition
i
Introduction
Vnet/IP is a control communication network that conforms to the IEEE802.3 standards.
The ProSafe-RS can configure a safety control system using Vnet/IP as its control bus.
This manual describes the Vnet/IP network and its engineering.
This manual provides information for systems consisting of ProSafe-RS alone or systems
where ProSafe-RS is integrated with CENTUM VP/CS 3000.
The structure of this manual is as follows:
• PART A
Vnet/IP Network
This part describes an overview of a Vnet/IP network, system configuration, connection,
and time synchronization.
• PART B
Engineering
This part describes how to use the system builders to create Vnet/IP domains.
With the release of CENTUM VP R5.01 and ProSafe-RS R3.01, the guidelines have been
changed so that Vnet/IP networks are used for control communications and other communi-
cations are performed on information networks other than Vnet/IP. This manual covers this
change.
SEE
ALSO For more information about legacy guide, refer to:
Vnet/IP Network Construction Guide (Legacy Edition) (TI 30A10A10-01E)
For more information about integration of ProSafe-RS with FAST/TOOLS (Yokogawa SCADA system), refer
to:
A., “Integration with FAST/TOOLS function” in Integration with FAST/TOOLS (IM 32Q56H20-31E)
Media No. IM 32Q56H10-31E (CD) 4th Edition : Jan. 2015 (YK) IM 32Q56H10-31E 4th Edition : Jan.30,2015-00
All Rights Reserved Copyright © 2011, Yokogawa Electric Corporation
ii
Safety Precautions for Use

n Safety, Protection, and Modification of the Product
• To protect the system controlled by the Product and the Product itself and to ensure safe
operation, please observe the safety precautions described in this Manual. Yokogawa
Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe
the safety precautions and instructions when operating the Product.
• If the Product is used in a manner not specified in the User's Manuals, the protection pro-
vided by the Product may be impaired.
• If any protection or safety circuit is required for the system controlled by the Product or for
the Product itself, please install it externally.
• Use only spare parts that are approved by YOKOGAWA when replacing parts or consum-
ables of the Product.
• Do not use the Product and its accessories such as power cords on devices that are not
approved by YOKOGAWA. Do not use the Product and its accessories for any purpose
other than those intended by YOKOGAWA.
• Modification of the Product is strictly prohibited.
• The following symbols are used in the Product and User's Manuals to indicate the accom-
panying safety precautions:
Indicates that caution is required for operation. This symbol is labeled on the Prod-
uct to refer the user to the User's Manuals for necessary actions or behaviors in
order to protect the operator and the equipment against dangers such as electric
shock. In the User's Manuals, you will find the precautions necessary to prevent
physical injury or death, which may be caused by accidents, such as electric
shock resulting from operational mistakes.
Identifies a protective conductor terminal. Before using the Product, you must
ground the protective conductor terminal to avoid electric shock.
Identifies a functional grounding terminal. A terminal marked "FG" also has the
same function. This terminal is used for grounding other than protective grounding.
Before using the Product, you must ground this terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates the ON position of a power on/off switch.
Indicates the OFF position of a power on/off switch.
n Notes on Handling User's Manuals

• Hand over the User's Manuals to your end users so that they can keep the User's Man-
uals on hand for convenient reference.
• Thoroughly read and understand the information in the User's Manuals before using the
Product.
• For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that the
Product is suitable for any particular purpose but to describe the functional details of the
Product.
• Contents of the User's Manuals are subject to change without notice.
IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

iii
• Every effort has been made to ensure the accuracy of contents in the User's Manuals.
However, should you have any questions or find any errors, contact us or your local dis-
tributor. The User's Manuals with unordered or missing pages will be replaced.
n Warning and Disclaimer

• Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for
the Product.
• YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either
using or not being able to use the Product.
n Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the Soft-
ware Product's merchantability or suitability for any particular purpose, except as speci-
fied in the warranty terms.
• Purchase the appropriate number of licenses of the Software Product according to the
number of computers to be used.
• No copy of the Software Product may be made for any purpose other than backup; other-
wise, it is deemed as an infringement of YOKOGAWA's Intellectual Property rights.
• Keep the software medium of the Software Product in a safe place.
• No reverse engineering, reverse compiling, reverse assembling, or converting the Soft-
ware Product to human-readable format may be performed for the Software Product.
• No part of the Software Product may be transferred, converted, or sublet for use by any
third-party, without prior written consent from YOKOGAWA.

iv
Documentation Conventions
n Symbols
The following symbols are used in the User's Manuals.
Identifies instructions that must be observed to avoid physical
injury, electric shock, or death.
Identifies instructions that must be observed to prevent damage

to the software or hardware, or system failures of the Product.
Identifies important information required to understand opera-

tions or functions.
Identifies additional information.
Identifies referenced content.

In online manuals, you can view the referenced content by click-
ing the links that are in green text. However, this action does not
apply to the links that are in black text.
n Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
l Commonly Used Conventions throughout the User's Manuals

• Δ Mark
Indicates that a space must be entered between character strings.
Example:
.ALΔPIC010Δ-SC
• Character string enclosed by braces { }
Indicates character strings that may be omitted.
Example:
.PRΔTAG{Δ.sheet name}
l Conventions Used to Show Key or Button Operations

• Characters enclosed by brackets [ ]
When characters are enclosed by brackets in the description of a key or button operation,
it indicates a key on the keyboard, a button name in a window, or an item in a list box
displayed in a window.
Example:
To alter the function, press the [ESC] key.
l Conventions of a User-defined Folder

• User-defined folder name enclosed by parenthesis ( )
User definable path is written in a pair of parentheses.
Example:
(RS Project Folder)\SCS0101

v
If the RS Project Folder is C:\MYRSPJT, the above path becomes C:
\MYRSPJTSCS0101.
n Drawing Conventions
Drawings used in the User's Manuals may be partially emphasized, simplified, or omitted for
the convenience of description.
Drawings of windows may be slightly different from the actual screenshots with different set-
tings or fonts. The difference does not hamper the understanding of basic functionalities and
operation and monitoring tasks.
n Integration with CENTUM

The Product can be integrated with CENTUM VP or CENTUM CS 3000. In the User's Man-
uals, the integration with CENTUM VP or CENTUM CS 3000 is referred to as "Integration with
CENTUM."
In the User's Manuals, the explanations for integrating the Product with CENTUM VP or
CENTUM CS 3000, the glossary for various features of CENTUM VP is used instead of the
glossary for CENTUM CS 3000. For example, the term "CENTUM VP System Alarm View" is
used instead of "CENTUM CS 3000 System Alarm window." Nevertheless, if the features for
integrating the Product with CENTUM VP and CENTUM CS 3000 are different, both features
will be explained separately.
SEE
ALSO For more information about the functions and usage of CENTUM VP components for integrating the Product
with CENTUM VP, refer to:
User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM VP
For more information about the features and usage of CENTUM CS 3000 components for integrating the
Product with CENTUM CS 3000, refer to:
User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM CS 3000
n Explanation of Hardware and Software Behaviors in the User's

Manuals
In the User's Manuals, system behaviors are explained assuming that the latest versions of
YOKOGAWA software and hardware at the time of publication of the User's Manuals are in-
stalled.
If additional precise information about the safety of legacy versions of software or hardware is
required, a link to the corresponding explanation is provided. Please refer to the information
according to your system.
n Station Types
A safety control station (hereafter referred to as SCS) is named according to the type of the
safety control unit used in it.
Table Info-1 Names of SCS and Safety Control Unit Used

Name of SCS Model of the safety control unit
SCSV1-S SSC10S/SSC10D
SCSP1-S SSC50S/SSC50D
SCSP2-S SSC60S/SSC60D
SCSU1-S SSC57S/SSC57D
In the User's Manuals, the following abbreviations may be used to describe functions of these
SCS as a whole.

vi
• SCSV1: Abbreviation of SCSV1-S
• SCSP1: Abbreviation of SCSP1-S
• SCSP2: Abbreviation of SCSP2-S
• SCSU1: Abbreviation of SCSU1-S

vii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the software medium of the
Software Product shall remain with YOKOGAWA.
You are allowed to print the required pages of the online manuals for the purposes of using or
operating the Product; however, reprinting or reproducing the entire document is strictly pro-
hibited by the Copyright Law.
Except as stated above, no part of the online manuals may be reproduced, transferred, sold,
or distributed to a third party in any manner (either in electronic or written form including, with-
out limitation, in the forms of paper documents, electronic media, and transmission via the
network). Nor it may be registered or recorded in the media such as films without permission.
n Trademark Acknowledgments
• CENTUM, ProSafe, Vnet/IP, and STARDOM are registered trademarks of YOKOGAWA.
• Microsoft, Windows, Windows Vista, Windows Server, Visual Basic, Visual C++, and Vis-
ual Studio are either registered trademarks or trademarks of Microsoft Corporation in the
United States and other countries.
• Adobe, Acrobat, and Adobe Reader are registered trademarks of Adobe Systems Incor-
porated.
• Ethernet is a registered trademark of Xerox Corporation.
• HART is a registered trademark of the HART Communication Foundation.
• Modicon and Modbus are registered trademarks of Schneider Electric SA.
• All other company and product names mentioned in the User's Manuals are trademarks
or registered trademarks of their respective companies.
• TM or ® mark are not used to indicate trademarks or registered trademarks in the User's
Manuals.
• Logos and logo marks are not used in the User's Manuals.

TocA-1
ProSafe-RS Vnet/IP
IM 32Q56H10-31E 4th Edition
CONTENTS
PART-A Vnet/IP network................................................A-1
A1. Overview of Vnet/IP network.............................................................A1-1
A2. Vnet/IP network system configuration.............................................A2-1
A2.1 System with ProSafe-RS only................................................................... A2-4
A2.2 System integrated with CENTUM............................................................. A2-5
A3. Vnet/IP network connections............................................................A3-1
A3.1 Connect devices included in Vnet/IP domain..........................................A3-2
A3.2 Connection between Vnet/IP domains..................................................... A3-4
A3.3 Connection between Vnet/IP and V net domains....................................A3-7
A3.4 Network connection through a wide area network............................... A3-11
A3.5 Vnet/IP bus status.................................................................................... A3-12
A4. Time synchronization of Vnet/IP...................................................... A4-1

TocB-1
ProSafe-RS Vnet/IP
IM 32Q56H10-31E 4th Edition
CONTENTS
PART-B Engineering......................................................B-1
B1. Overview of engineering................................................................... B1-1
B2. Network engineering......................................................................... B2-1
B2.1 Setting addresses on hardware................................................................B2-2
B2.2 Procedures and precautions for adding a station or domain................B2-3
B3. Engineering safety control stations on SENG................................ B3-1
B4. Engineering on CENTUM.................................................................. B4-1
B4.1 Engineering safety control stations on CENTUM................................... B4-2
B4.2 Setting domain properties.........................................................................B4-3
B4.3 Setting V net routers..................................................................................B4-4
B4.4 Setting up wide area communication routers......................................... B4-5

<A. Vnet/IP network > A-1
A. Vnet/IP network
This part describes an overview of a Vnet/IP network, system configuration, connection, and
time synchronization.

<A1. Overview of Vnet/IP network> A1-1
A1. Overview of Vnet/IP network

Vnet/IP is a control communication network that conforms to the IEEE802.3 standards.
Vnet/IP is a high reliability network built in dual-redundant configurations.
Vnet/IP supports 1 Gbps or 100 Mbps transmission speed.
A Vnet/IP network is built by using network devices such as Layer 2 switches and Layer 3
switches, and transmission media such as UTP (Unshield Twist Pair) cables and optical fiber
cables.
n Communication paths of control communication

A Vet/IP network is a redundant network for control communication. In Vnet/IP, redundant
buses are configured with independent subnets of bus 1 and bus 2.
Control communication is the communication for transferring control data.
Normally, bus 1 is used for control communication. When bus 1 fails due to a communication
error, control communication is continued on bus 2. An Ethernet network apart from the
Vnet/IP is used for file transfer and data communication except for control communication.
SEE
ALSO For more information about the specification of ProSafe-RS system on Vnet/IP, refer to:
ProSafe-RS Safety Instrumented System Overview (for Vnet/IP) (GS 32Q01B10-31E)

<A2. Vnet/IP network system configuration> A2-1
A2. Vnet/IP network system

configuration
In this chapter, configuration of a system with Vnet/IP network as well as the network compo-
nents will be explained.
n System components of a Vnet/IP network

The system components of a Vnet/IP network are illustrated in the following figure.
The example of the system configuration is shown as follows.
Ethernet
Console type HIS or

HIS Installed with
System Builders General-purpose HIS or HIS Installed
SENG Ethernet device with System Builders Exaopc Firewall
Intranet
Bus 1 side
SCSP2 L3SW
L2SW L2SW L2SW Vnet/IP

L2SW L2SW L2SW domain 2
Bus 2 side
Vnet/IP L3SW
domain 1
L3SW L3SW
Bus 1 side Bus 2 side
Vnet/IP
V net router
FCS domain 3
V net domain 4
SCSV1
SENG: Safety engineering PC

SCSP2, SCSV1: Safety control station
V net router: Router that connects a V net domain with a Vnet/IP domain
HIS: CENTUM operation and monitoring station
FCS: CENTUM field control station
Exaopc: OPC server
L2SW: Layer 2 switch
Figure A2-1 System components of a Vnet/IP network
TIP There are two types of Safety Control Stations that connect to Vnet/IP: SCSP2 and SCSP1. In this manual,
SCSP2 is the representative station unless otherwise specified.

l Vnet/IP station
A Vnet/IP device equipped station that is connected to a Vnet/IP network is referred to as a
Vnet/IP station. A Vnet/IP station in a domain is connected to Layer 2 switches provided one
for each bus. Vnet/IP stations are described below.
• SENG
SENG is a Safety Engineering PC. It is connected to a Vnet/IP network through a VI702/
VI701 Vnet/IP interface card installed in the PC. The VI702/VI701card has two ports and
each port is connected to a transmission cable for Vnet/IP to support redundant Vnet/IP
buses.
• SCS
The Safety Control Stations that can be connected to a Vnet/IP network are SC60S/
SSC60D (SCSP2) and SSC50S/SSC50D (SCSP1). The transmission speed of SCSP2/
SCSP1 is 100 Mbps.
• V net router (AVR10D)
A V net router is a device dedicated for connecting a Vnet/IP domain with a V net domain.
It performs the frame conversion and filtering between Vnet/IP and V net. The V net rout-
er is a station of CENTUM system.
TIP V net routers (AVR10D) are classified into two types of behavioral specification, based on their hardware style
and system software revisions. In this document, the two types are defined as "V net router style S3 or
above" and "V net router style below S3", as follows.
• V net router style S3 or above
AVR10D is style S3 or above and the "operating mode" of V net router is set to [Standard mode] in the
System View of CENTUM VP R5.01 or later.
• V net router style below S3
Cases that do not meet the conditions of "V net router style S3 or above".
If no style is mentioned in explanations about the operation of the V net router in this document, the operation
is common to all AVR10D styles and ProSafe-RS/CENTUM VP software revisions.
• Wide area communication router (AW810D)

The wide area communication router is a hardware device dedicated for the communica-
tions between Vnet/IP domains distributed in remote areas through a wide area network.
The wide area communication router is a device of CENTUM systems.
• HIS
HIS (Human Interface Station) is an operation and monitoring station of CENTUM. The
HIS is used for operation and monitoring of SCS. The CENTUM system builders are re-
quired for engineering and maintenance for the HIS and V net routers. The system build-
ers can be installed on the HIS.
SEE
ALSO For more information about Vnet/IP stations of a CENTUM system, refer to:
• "System Components of Vnet/IP Network" in 1, "Overview of Vnet/IP Network" of the CENTUM VP
Vnet/IP (IM 33K10A10-50E)
• "System Components of Vnet/IP Network" in A1, "Overview of Vnet/IP Network" of the CENTUM
VP Vnet/IP (IM 33L01A10-40E)
• "System Components of Vnet/IP Network" in A1, "Overview of Vnet/IP Network" of the CS 3000
Vnet/IP (IM 33Q06H90-31E)
For more information about the wide area communication router, refer to:
8, "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E)

l Vnet/IP domain
A Vnet/IP domain consists of two independent subnets of bus 1 and bus 2. Each domain can
have a maximum of 64 Vnet/IP stations (SENG, SCSP2, etc.).
If a safety system is integrated with a CENTUM system, the integrated system can have a
maximum of 16 Vnet/IP and V net domains.
l Layer 2 switch
Vnet/IP stations and general-purpose Ethernet communication devices in a domain are con-
nected to Vnet/IP buses through the Layer 2 switches (L2SW). At least one L2SW is required
for bus1 and bus 2 respectively.
l Layer 3 switch
A layer 3 switch (L3SW) is used to connect between Vnet/IP domains on each bus.
n Compatibility between Vnet/IP and V net

The upper protocol of the control communication of Vnet/IP is compatible with that of V net.
Therefore, a Vnet/IP station connected to Vnet/IP and a V net station connected to V net can
communicate with each other via a V net router. Computer-based stations, such as SENG
and HIS, can be connected to either Vnet/IP or V net by selecting the communication inter-
face card according to the type of the network.
n Connecting general-purpose Ethernet devices

General-purpose Ethernet devices typified by a PC are connected to an Ethernet network in-
stalled apart from the Vnet/IP.

<A2.1 System with ProSafe-RS only> A2-4
A2.1 System with ProSafe-RS only

This section explains a system only configured with ProSafe-RS, where Vnet/IP is used as
the control network.
n Overview of a System with ProSafe-RS only

The overview of a system with ProSafe-RS only is as follows:
• A system can be configured with SENG, SCSP2 stations and Layer 2 switches.
• The system consists of a single Vnet/IP domain.
• The time of SCSP2 and SENG is synchronized with the Vnet/IP time. You can also install
an SNTP (Simple Network Time Protocol) server to synchronize the time with the stand-
ard time.
IMPORTANT
Under the following circumstances, the ProSafe-RS should be integrated with CENTUM sys-
tem:
• When ProSafe-RS stations on a V net domain are communicating with other ProSafe-RS
stations on a Vnet/IP domain through V net routers.
• When ProSafe-RS stations on multiple Vnet/IP domains are communicating with each
other through Layer 3 switches.
n Precautions for systems that include only one SCSP2 station

If a system is configured with SENG and one SCSP2 station only, notice the followings:
• Two layer 2 switches (with power supplies) are required for bus 1 and bus 2.
• The system function block SYS_DIAG will give error notice on VNER (presence of control
bus related errors) if all of the following conditions are met.
• The SCSP2 station is running for normal operation while SENG power is off.
• The SCSP2 CPU is non-redundantly configured, or if one of the CPU fails on the
SCSP2 with dual-redundantly configured CPU.

<A2.2 System integrated with CENTUM> A2-5
A2.2 System integrated with CENTUM

When ProSafe-RS is integrated with CENTUM, according to a system configuration, it is pos-
sible to place either SCSP2 and SENG stations on a Vnet/IP or SCSV1 and SENG stations
on a V net.
When ProSafe-RS is integrated with CENTUM, it is possible to connect between Vnet/IP do-
mains and between a Vnet/IP domain and a V net domain.
n Overview of functionality supported by connecting Vnet/IP domains

Layer 3 switches or wide area communication routers are required for connection between
Vnet/IP domains. The following functionality can be supported by stations on the Vnet/IP do-
main.
• Inter-SCS safety communication
Inter-SCS safety communication that crosses domains can be performed.
• Engineering and maintenance of SCS stations from an SENG
Normally, the SENG and SCS should be located in the same domain. When a connection
between domains is made through wide area communication routers, SCSs and the
SENG that is used for the maintenance of the SCSs must be placed in the same domain.
If the SENG and SCSs are located in different Vnet/IP domains, both domains must be
set to allow bi-directional reception of FCS TCP communication between these domains
for engineering and maintenance of SCSs from the SENG.
• Checking of communication status
In the Network Status Display dialog box of CENTUM HIS, the communication status
within a domain and between domains can be referenced.
n Overview of functionality supported by connecting Vnet/IP domains

and V net domains
A Vnet/IP domain can be connected with a V net domain via a V net router. The following
functionality can be supported via a V net router between stations on the V net domain and
stations on the Vnet/IP domain.
Between Vnet/IP domain and V net domain (Vnet/IP-V net)
Between V net domains with a Vnet/IP (V net-Vnet/IP-V net)
• Engineering and maintenance of SCS stations from an SENG
Engineering of an SCS on a Vnet/IP can be performed from an SENG on a V net, and
engineering of SCS on a V net can be performed from an SENG on a Vnet/IP.
At least one SENG should be connected on the V net allowing communications with SCS.
The range of communication-enabled domain hierarchy is the same as control for inter-
SCS safety communication.
The supported range varies depending on the style of V net router. The following functionality
can be achieved when using V net router style S3 or above.
Between V net domains through a Vnet/IP domain (V net-Vnet/IP-V net)
• Virtual domain link transmission
A V net domain and a Vnet/IP domain connected to a V net router may be considered as
one virtual domain. SCS global switch communication between SCS and FCS is possible
within a virtual domain.

<A2.2 System integrated with CENTUM> A2-6
SEE
ALSO For more information about the connection between Vnet/IP domain and V net domain, refer to:
A3.3, “Connection between Vnet/IP and V net domains” on page A3-7
For more information about virtual domain link transmission, refer to:
“■ Virtual Domain Link Transmission” in 2.9, “SCS Link Transmission” in Engineering Guide (IM
32Q01C10-31E)

<A3. Vnet/IP network connections> A3-1
A3. Vnet/IP network connections

This chapter describes various connections to configure a Vnet/IP network and the communi-
cation status of the control bus.
• Connection in a Vnet/IP domain
• Connection between Vnet/IP domains
• Connection between a Vnet/IP domain and a V net domain
• Network Connection through Public Communication Lines
• Vnet/IP Bus Status
n Outline of Vnet/IP network connections

An illustration of Vnet/IP network connections for a CENTUM integration structure is shown
below.
SENG, HIS
Can be connected to WAN

Up to seven via dedicated communication
L2SW levels lines.
L3SW
Bus 1
V net router
V net L2SW L2SW L2SW Vnet/IP Vnet/IP
domain Bus 2 domain domain
L2SW L2SW L2SW
Vnet/IP domain L3SW
BCV
V net BCV: Bus converter

domain SCSP2 L2SW: Layer 2 switch
Figure A3-1 Outline of Vnet/IP network connections
TIP Wide area communication routers can also be used to connect Vnet/IP domains through a wide area network.
SEE
ALSO For more information about connection between Vnet/IP domains using the wide area communication router,
refer to:

<A3.1 Connect devices included in Vnet/IP domain> A3-2
A3.1 Connect devices included in 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 inde-
pendent 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 pow-
er 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 fail-
ure.
• For dual-redundant SCS, if the Layer 2 switches for both buses fail, the control will be
switched to the standby CPU in rare cases, causing the dual-redundant SCS to operate
in non-redundant mode.
• If a Layer 2 switch is restarted after momentary power failure, it takes several tens of sec-
onds for the communications between stations to recover.
n Specification when connecting devices in a Vnet/IP domain

The specification when connecting devices in a Vnet/IP domain is as follows:
• Number of Vnet/IP stations connected : Max. 64 Stations
(Vnet/IP stations including V net routers)
• Distance between Vnet/IP stations : Max. 40 km
• Distance between Layer 2 switch and station : Max.100 m (when UTP cable is
used)
Max. 5 km (when optical fiber cable
is used)
• Connection distance between Layer 2 switches: : Max. 5 km (when optical fiber cable
is used)
• Levels of Layer 2 switches: : Max. 7 levels
IMPORTANT
The connection between any two communicating stations must avoid multiple routes. Other-
wise, the communication may not be properly performed.
SCSP2 SCSP2
L2SW L2SW
L2SW
Figure A3.1-1 Example of an incorrect connection

<A3.1 Connect devices included in Vnet/IP domain> A3-3
TIP • It is also possible to use a faster switch more than 1 Gbps between Layer 2 switches.
• For dual-redundantly configured stations such as SCSP2 stations or V net routers, though two CPU
modules are separately connected with UTP cables to Layer 2 switches, both CPU modules are counted
as one communication station or one communication device.
SENG
UTP cable
Max. 100 m
Bus 1 side Bus 2 side

L2SW L2SW
Optical fiber Optical fiber

cable cable
Max. 5 km Max. 5 km
L2SW L2SW
UTP cable
Max. 100 m
SCSP2
Figure A3.1-2 Example of connections in a Vnet/IP domain

<A3.2 Connection between Vnet/IP domains> A3-4
A3.2 Connection between Vnet/IP domains

Layer 3 switches are required for connection between Vnet/IP domains. Install Layer 3
switches in each bus of dual-redundantly configured Vnet/IP buses and connect them to other
domains. By using a leased line as the transmission path, the domains can be connected
through the wide area networks.
Connection of multiple domains is only supported in a CENTUM integrated system. It is not
supported in a ProSafe-RS only system.
IMPORTANT
Multiple stations are connected to a Layer 3 switch. It is strongly recommended to protect
Layer 3 switches with an uninterruptible power supply (UPS) so that Layer 3 switches will not
stop due to power failure.
TIP Wide area communication routers can also be used to connect Vnet/IP domains through a wide area network.
SEE
ALSO For more information about connections between Vnet/IP domains using the wide area communication router,
refer to:
n Specifications when connecting 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 80 ms
IMPORTANT
The connection between any two communicating domains must avoid multiple routes. Other-
wise, the communication may not be properly performed.
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW
Figure A3.2-1 Example of incorrect connection
n Connection between Vnet/IP domains

There are three types of connections between Vnet/IP domains: bi-directional, hierarchical
and bridge connections. It is possible to configure a network coexisting these three types of
connections. Set the connection types in Domain Properties for each domain using CENTUM
engineering builders. The connection type may be selected in accordance with the upper and
lower relationships that should be set between connected domains. Decide on the connection
type after investigating whether or not message reception, SCS TCP communication or time
synchronization is required between connected domains.

Bi-Directional Bi-Directional
Domain 4 Domain 5
L3SW L3SW
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW Bridge
Hierarchical
Domain 6
Figure A3.2-2 Domain connection types in Vnet/IP
l Bi-directional connection
This connection type does not differentiate the upper and lower relationships between Vnet/IP
domains. This type of connection can be established by setting the domain to receive HIS
messages, FCS messages and FCS TCP communication frames from other domains. More-
over, when the domain is set to receive FCS messages, it can also receive SCS messages
(such as system alarm messages). If the domain is set to receive FCS TCP frames, it can al-
so receive the SCS TCP communication frames. By the default settings on the Domain Prop-
erties dialog box, the domain is set to receive all the transmissions.
l Hierarchical connection
This connection type differentiates the upper and lower relationships between Vnet/IP do-
mains. This type of connection can be established by setting a lower domain not to receive
HIS messages, FCS messages and FCS TCP communication frames from upper domains;
but all the stations in the upper domains can receive HIS messages, FCS messages, and
FCS TCP communication frames from the lower domain. Moreover, when the domain is set to
receive FCS messages, it can also receive SCS messages (such as system alarm messag-
es). If the domain is set to receive FCS TCP frames, it can also receive the SCS TCP commu-
nication frames.
l Bridge connection
This connection type guarantees the independence of a domain. It can be established by set-
ting the domain not to receive HIS messages, FCS messages and FCS TCP communication
frames from another domain and by setting the time group to "0" so as not to perform time
synchronization.
IMPORTANT
• If the SENG and the SCSP2 stations are located in 2 different Vnet/IP domains, both do-
mains should be set to allow the reception of FCS TCP communication for engineering
and maintenance purpose.
• When two SCS stations in two domains are performing inter-SCS safety communication,
both domains should be set to allow the reception of FCS TCP communication.
• When two SCS stations in two domains are performing inter-SCS safety communication
and one domain is a V net domain, both domains should be set to allow the reception of
FCS TCP communication. Moreover, the V net router, the bus converter (BCV) and the
communication gateway (CGW) should also be set to allow the reception of FCS TCP
communication.

TIP • With any type of connections, function blocks and variables of SCSP2 stations can be accessed by tag
names from CENTUM stations across domains.
• You can also set the domain properties so that the domain receives only one type among HIS messag-
es, FCS messages, and FCS TCP communication frames.
SEE
ALSO For more information about Time Group, refer to:
“n Time groups” on page A4-2
For more information about domain properties, refer to:
• "Vnet/IP Domain Properties" in 2.1.1, "File Menu of System View" of the CENTUM VP Engineering
Reference Vol.1 (IM 33K03G21-50E)
• B2.3, “Setting Domain Properties” in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• B2.3, “Setting Domain Properties” in the CS 3000 Vnet/IP (IM 33Q06H90-31E)

<A3.3 Connection between Vnet/IP and V net domains> A3-7
A3.3 Connection between Vnet/IP and V net

domains
A Vnet/IP domain can be connected with a V net domain via a V net router. When integrated
with CENTUM system, this type of connection can be applied.
n Overview of a network connection between Vnet/IP and V net

domains
To connect a Vnet/IP domain and a V net domain, a V net router needs to be used for routing
the connection. The engineering of a V net router style below S3 must be done from the
CENTUM system builders on the Vnet/IP side. The engineering of a V net router style S3 or
above can be done also on the V net side using the system builders of CENTUM VP R5.01 or
later. Because the connection of a Vnet/IP domain and V net domain is bi-directional, it is pos-
sible to perform the operation and monitoring of SCSs and FCSs from either domain.
When performing CENTUM engineering, Vnet/IP domains and V net domains may be inclu-
ded in one project. It is possible to handle them as separate projects, but using the Multiple
Project Connection package to connect these projects.
On SENG, the SCSP2 station of an SCS project on Vnet/IP network and the SCSV1 station of
an SCS project on a V net network can be handled as one RS project. In the SCS Status
Overview window of the SCS Maintenance Support Tool, statuses of SCSP2 and SCSV1 sta-
tions are displayed together.
Ethernet
SENG HIS
SENG HIS
Vnet/IP
network V net
V net router
SCSV1
SCSP2 FCS FCS
Figure A3.3-1 V net connection
IMPORTANT
Allocate only one path from a Vnet/IP network to a specific V net domain via a V net router. If
a V net router is defined so that two or more paths exist as paths to a specific V net domain,
the following problems will occur:
• The path from the Vnet/IP side to the corresponding V net domain changes randomly.
• Communication frames to nonexistent domains converge depending on the definition of
the routing of the V net router.
If a V net router style below S3 is used, communication between Vnet/IP domains cannot be
performed through a V net domain.

With V net routers style S3 or above, network configuration like the one in the following figure
is possible by connecting a V net domain and Vnet/IP domains. To perform Ethernet commu-
nication between PCs across domains, install an Ethernet network and connect all the PCs.
Ethernet
SENG HIS SENG SENG
Vnet/IP Vnet/IP
domain 2 domain 3
V net router V net router
V net domain 1
Figure A3.3-2 Installation of Ethernet that crosses domains
n Restrictions on multi-level connection of control buses

A station on a Vnet/IP network can access a station on another control bus, up to two levels
of bus converters (BCVs) or communication gateway units (CGWs) beyond the V net router.
Thus, you can establish connection between the Vnet/IP domain and an existing V net control
bus that is two levels of BCV or CGW away from the V net router.
Consider the following while counting the number of levels in a multi-level connection of V net:
• Do not count the number of levels of Vnet/IP domains on an access path.
• Do not count the number of levels of V net routers.
• Count the number of levels of BCV or CGW that connect to other V nets, as usual.
l Communication reach by Vnet/IP stations

The following figure indicates the range in which the Vnet/IP station can communicate.

L2SW Max. 7 Levels. Vnet/IP Vnet/IP

1 Level L2SW L2SW domain domain
Max. 5km using
optic fiber cable Via AVR (V net router) between Vnet/IP and
between L2SWs. V net domains
L2SW (The Max. L3SW
AVR
distance of the
two stations in Vnet/IP V net
the same domain domain
[GW 0 Level] BCV/CGW
is 40 km.) BCV/
BCV/
L2SW Max. 2
L3SW CGW Levels.
[GW 0 Level] V net (Not counting
the Vnet/IP
L3SW and AVR
BCV/
levels.)
Within same Vnet/IP domain. L3SW Max. CGW
Vnet/IP 15 Levels.
[GW 0 Level] domain [GW 1 Level] V net
(The transmission
delay between
any two stations
is less than 80 ms.)
[GW 2 Level]
Between Vnet/IP domains.
[GW 0 Level]
: SCSP2
: SCSV1

AVR: V net router
BCV: Bus converter
CGW: Communication gateway unit
Figure A3.3-3 Communication reach by Vnet/IP stations
SEE
ALSO For more information about the scope of implementation when combining multiple domains of Vnet/IP and V
net, refer to:
“● Inter-SCS Safety Communication in Systems in which a V net Domain and a Vnet/IP Domain are
Connected” in “■ Communicable Extent” in 2.1.1, “Overview of the System Configuration” in Engineering
Guide (IM 32Q01C10-31E)
l Communication reach by V net stations

The following figure indicates the range in which the V net station can communicate.

V net V net V net
BCV/ BCV/ AVR

CGW CGW
[GW 0 Level] V net V net
Vnet/IP domain
BCV/ AVR
CGW AVR
[GW 1 Level]
Vnet/IP domain
[GW 0 Level]
V net V net
AVR AVR BCV/

CGW BCV/CGW Max.
[GW 2 Level] [GW 0 Level] 2 Levels.
[GW 1 Level] V net V net (Not counting
Vnet/IP domain the Vnet/IP and
AVR levels.
AVR BCV/ BCV/

CGW CGW
[GW 1 Level] [GW 1 Level]
[GW 2 Level] V net V net V net
[GW 2 Level] [GW 2 Level] [GW 2 Level]
: SCSP2
: SCSV1
AVR : V net router

BCV : Bus converter
CGW: Communication gateway unit
Figure A3.3-4 Communication reach by V net stations
SEE
ALSO For more information about the number of levels of bus converters connecting a V net, refer to:
• 2.1, "Outline of Bus Converter for V net" in the CENTUM VP Communication Devices Reference
(IM 33K03M10-50E)
• L1.1, "Outline of Bus Converter for V net" in the CENTUM VP Communication Devices Refer-
ence(IM 33M01A30-40E)
• L1.1, "Outline of Bus Converter for V net" in the CS 1000/CS 3000 Reference Communication De-
vice (IM 33S01B30-01E)
For more information about the scope of implementation when combining multiple domains of Vnet/IP and V
net, refer to:
“● Inter-SCS Safety Communication in Systems in which a V net Domain and a Vnet/IP Domain are
Connected” in “■ Communicable Extent” in 2.1.1, “Overview of the System Configuration” in Engineering
Guide (IM 32Q01C10-31E)

<A3.4 Network connection through a wide area network> A3-11
A3.4 Network connection through a wide area

network
Connection between Vnet/IP domains can be established through a wide area network for
communicating with remote Vnet/IP domains. This type of connection can be established
when integrated with CENTUM.
IMPORTANT
If you intend to connect Vnet/IP domains through a wide area network without using wide
area communication routers, the following conditions have to be met.
• The transmission delay between any two Vnet/IP domains must be less than 80 ms.
• If inter-SCS safety communications are performed between domains connected through
a wide area network, the recommended bandwidth of the wide area network is 100 Mbps
or faster.
SEE
ALSO For more information about the specifications of connection between Vnet/IP domains using the wide area
communication router, refer to:
n Replacing communication gateway units (CGWs) for wide area

communication
By utilizing connection between Vnet/IP domains, existing communication gateway units
(CGWs) for wide area communication can be replaced with Layer 3 switches or wide area
communication routers.
For more information about the replacement, contact YOKOGAWA.

<A3.5 Vnet/IP bus status> A3-12
A3.5 Vnet/IP bus status

This chapter explains how to check the Vnet/IP bus communication status
n Overview of Vnet/IP bus status

On the SCS State Management window of the SCS Maintenance Support Tool of SENG, the
bus communication status of the SCSs in a domain can be displayed. Using an application
logic with the control bus status indicator function block (SYS_NETST) can output the bus er-
ror alarm to external alarm lamps for notification.
If integrated with CENTUM system, statuses of all stations of all the domains connected to the
Vnet/IP network as well the routing devices among the domains can be displayed. Vnet/IP
bus status is displayed in the Network Status Display dialog box of the CENTUM HIS. When
the bus status changes, a system alarm message will be generated and output to the HIS.
n Elements of the Vnet/IP bus status

The Vnet/IP bus status shows the communication status of the stations in all domains con-
nected to the Vnet/IP network as well as the devices (such as Layer 3 switches) connecting
domains.
The Vnet/IP bus status consists of the following three elements:
• Bus status in own domain
• Communication status of devices connected between domains
• Bus statuses of other domains
The information of a domain is not

Vnet/IP
bus status broadcasted to stations beyond the
domain except the bus status signals.
However, an HIS in another domain
can access the information.
Bus status in Bus status of

own domain other domains
Communication Communication Communication

status between status of devices status between
stations in connected stations in
own domain between domains other domains
Figure A3.5-1 Elements of the Vnet/IP bus status
l Displaying the station communication status of a domain

Each station in a Vnet/IP domain diagnoses bus statuses mutually using bus 1 and bus 2.
Communication statuses for a station are shown as follows. A dual-redundant station with du-
al CPU modules has the following four types of communication status.
• Control side (*1) communication status between stations
• Communication status between control side (*1) station and standby side station
• Communication status between standby side (*1) station and control side station
• Standby side communication status between the stations

<A3.5 Vnet/IP bus status> A3-13
*1: Including non-redundant stations (such as SENG, HIS, SCSP2 with single CPU).
Based on this diagnostic information the communication statuses of all stations in a domain
can be displayed on the HIS Network Status Display dialog box.
SEE
ALSO For more information about communication status, refer to:
• 4.9.4, "Network Status Display Dialog Box" in the CENTUM VP Human Interface Stations Refer-
ence Vol. 1 (IM 33K03F21-50E)
• C2, "Network Status Display Dialog Box" in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• C2, "Network Status Display Dialog Box" in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
l Bus status in a domain

The bus status in a domain is created from the communication status among stations in each
domain. If the bus status shows abnormality, the meaning varies with the type of failure:
• Either bus failure (either bus 1 or bus 2)
When either bus 1 or bus 2 encounters communication error, the status of the bus will be
indicated as abnormal.
• Both bus failure (both 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 are 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

The Vnet/IP domains communicate with each other using bus 1 and bus 2 and the communi-
cation status can be monitored. On the HIS Network Status Display dialog box, the communi-
cation statuses of devices on different domains can be displayed.
The bus status of one domain is broadcasted to all stations in all domains through the com-
munication between 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
case of either bus failure, the status of the failed bus is handled as abnormal. In case of
both bus failures, only the status of the bus in which abnormality is detected first is han-
dled as abnormal.
• Communication Statuses of Devices Connecting Domains
While the bus status of own domain is normal, the communication statuses of devices
connecting domains are reflected in the Vnet/IP bus status. In case of either bus failure,
the status of the failed bus is handled as abnormal. In case of both bus 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 sta-
tuses of other domains are reflected in the Vnet/IP bus status. However, even if a differ-
ent bus is 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.

<A4. Time synchronization of Vnet/IP> A4-1
A4. Time synchronization of Vnet/IP

Time synchronization is performed among Vnet/IP stations connected to the Vnet/IP network.
When an SNTP server is connected to the Vnet/IP network, the Vnet/IP stations are
synchronized with the standard time. The time on Vnet/IP stations are synchronized by the
synchronization mechanism for Vnet/IP networks.
n Overview of time synchronization

Time synchronization in a Vnet/IP network is performed in a time group. A time group can be
defined with domains. To synchronize the time of stations connected to a Vnet/IP network with
UTC (Coordinated Universal Time), an SNTP server must be connected for each time group.
An SNTP server can be connected without engineering of ProSafe-RS or CENTUM. Each sta-
tion time of the time group which is synchronized with the SNTP server will automatically syn-
chronize with the server time.
An overview of time synchronization for a Vnet/IP network is shown as follows.
• Define the domains into a time group.
• Connect the SNTP server to Vnet/IP bus 1.
• Connect both bus 1 and bus 2 to the SNTP server if the server needs to be dual-redun-
dantly structured.
• If the SNTP server is not connected to the network or if the time in the SNTP server is not
synchronized with the standard time, a Vnet/IP station of the time group becomes the
time master station.All the other stations will synchronize their times with this station.
Time group 1 Time group 2

SNTP server SNTP server
HIS Time accuracy in a HIS

SENG domain ± 1 ms SENG
L3SW
Vnet/IP L3SW Vnet/IP
domain 1 domain 3
HIS L3SW
L3SW L3SW
L3SW
SCSP2 SCSP2
Vnet/IP
domain 2
Time accuracy between

domains ± 5 ms
SCSP2
Figure A4-1 Time synchronization of Vnet/IP
SEE
ALSO For more information about precautions for time synchronization, refer to:
“■ Precautions for Time Synchronization” in 2.15, “Time Synchronization” in Engineering Guide (IM
32Q01C10-31E)
n Accuracy of time synchronization

Time management of a Vnet/IP station is performed through the Vnet/IP network.

All Vnet/IP stations on a Vnet/IP network use a reference time to perform time synchroniza-
tion for the entire Vnet/IP network. This reference time is referred to as the network time. The
relative accuracies of the network time are shown as follows:
Table A4-1 Accuracy of network time

Station Relative time accuracy
±1 ms, When one bus is abnormal, the accuracy may become worse
In a domain
than ±1 ms due to heavy open communication traffic.
±5 ms, When one bus is abnormal, the accuracy may become worse
Among domains (using L3 than ±5 ms due to heavy open communication traffic. The relative time
switches) accuracy deteriorates in proportion to transmission delay time varia-
tions among domains.
±5 seconds, if the time deviation between Vnet/IP domains continues to
be 5 seconds or more for two minutes, the wide area communication
router use a function for time synchronization between Vnet/IP domains
Among domains (using wide area
to allow the time in a destination domain to synchronize to the time of
communication routers)
Vnet/IP domain for reference. To keep the time deviation between
Vnet/IP domains within 5 seconds, install an SNTP server in both
Vnet/IP 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 A4-2 Accuracy of system time

Deviation from net-
Station type Time Adjustment
work time
The deviation between the network time and the sys-
SENG or HIS stations operat- tem time will be checked all the time. If the deviation
Max. 0.5 s
ing on general-purpose PC exceeds 0.5 s, the system time will be adjusted to
the network time.
The system time always synchronizes with the net-
SCSP2, FCS, V net router None
work time.
n Time groups
The time group denotes a range in which time synchronization is performed. The entire
Vnet/IP network can be defined on one time group. On the other hand, by separating domains
in the same Vnet/IP network into time groups, the range in which time synchronization is per-
formed can be limited.
The time group number to which the domain belongs is 0 to 7. The default time group number
is 1. To perform time synchronization only within a domain, set the time group number to 0.
If an SNTP server does not exist in a time group, one of the Vnet/IP stations in a time group
will act as the time master station, and other Vnet/IP stations in the same time group will syn-
chronize with the time of the time master station.
n Engineering time groups

A time group can be defined on the Domain Properties using CENTUM engineering builders.
If the system consists of ProSafe-RS only, no engineering work is required. Since the system
consists of only one domain, all stations in the domain will be in the same time group.

SEE
ALSO For more information about setting domain properties, refer to:
• B2.3, "Setting Domain Properties" in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• B2.3, "Setting Domain Properties" in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
For more information about precautions about time groups when performing inter-SCS safety communication,
refer to:
“■ Precaution for Engineering” in 2.8, “Inter-SCS Safety Communication” in Engineering Guide (IM
32Q01C10-31E)
n Connection and dual-redundancy of SNTP servers

To synchronize the network time of a Vnet/IP station with a standard time, connect an SNTP
server in each time group. One SNTP server can be connected to each bus within the same
time group. Generally, connect an SNTP server on bus 1 of the Vnet/IP network.
You can also add another SNTP server on bus 2 of the Vnet/IP network to implement dual-
redundant SNTP servers. After connecting the SNTP server, the time master station will syn-
chronize the time according to the SNTP server that is synchronized with the standard time. If
the SNTP server fails, the time synchronization will be performed with another SNTP server
on the other bus.
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 becomes ready for time
synchronization, all stations in the time group will synchronize their time with the SNTP server
instantly instead of the time master station.
The IP address of an SNTP server connected to a Vnet/IP network 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
Note that the configuration of SNTP server need not be performed from SENG or HIS. When
SNTP server is connected to the Vnet/IP network, the Vnet/IP stations will perform time syn-
chronization with the SNTP server automatically.
n Time synchronization after powering on Vnet/IP station

After a Vnet/IP station is powered on, the time of the station inches closer to the network time
of the same time group. Within 5 seconds after the station startup, the relative time accuracy
becomes 1 second, and within 5 minutes, it becomes ±1 ms.
n Time synchronization of SCS connected to Vnet/IP network

The system time of an SCS connected to the Vnet/IP network is synchronized with the
Vnet/IP network time. Moreover, the DI module with SOER (Sequence Of Event Records) in-
stalled in the SCS also synchronizes its time with this network time through SB/ESB buses.
If an SNTP server is available in the network, the SCSs can synchronize times with the stand-
ard time. The accuracy of synchronization with the standard time of an SCS depends on the

time accuracy of the SNTP server. If the SNTP server is not available in the network, the
SCSs synchronize times with the Vnet/IP network time master station.
The time of the SCS stations, whether it is synchronized with the SNTP server or synchron-
ized with the Vnet/IP time master station, can be found using the following function blocks or
monitored on the following windows.
• Output of the SYS_NETST system function block
• The SCS State Management Window of the SCS Maintenance Support Tool of SENG
• The SCS Status Display Window of HIS
Even if the state of the time synchronization of an SCS changes, no diagnostic message or
system alarm is output to notify this event. If the time synchronization event needs to be noti-
fied, an application logic should be created using the SYS_NETST function block to output
the event to an external alarm lamp or to an annunciator.
The SCS Synchronous Mode on the Communication tab of the SCS Constants Builder should
be set to Vnet/IP regardless of whether the SNTP server is available or not.
SEE
ALSO For more information about SOE functions of SCS, refer to:
A7., “SOER” in Safety Control Station Reference (IM 32Q03B10-31E)
For more information about SYS_NETST, refer to:
C11.5, “SYS_NETST (control bus status indicator)” in Safety Control Station Reference (IM
32Q03B10-31E)
For more information about SCS Constants Builder, refer to:
3.1.3, “SCS Constants Builder” in Engineering Reference (IM 32Q04B10-31E)
n Time synchronization with a V net domain

Time synchronization when a Vnet/IP domain and a V net domain are connected is as follows.
• When using a V net router style below S3
The time on the Vnet/IP side becomes the master, and the time of the V net domain syn-
chronizes to that. It is not possible to use the time on the V net as the master.
Also, the V net router compares the Vnet/IP network time with the V net time at 2-minute
intervals, and sets the Vnet/IP network time to the V net time if a deviation of 5 seconds
or more occurs twice consecutively.
On the properties dialog box of a V net router, the time synchronization of the V net do-
main can be set not to synchronize with the Vnet/IP network time. Uncheck the [Transfer
lower] option under “Transfer System Time” in CENTUM VP R5.01 or later. Uncheck the
"Transfer System Time - Transfer lower" option in CENTUM VP below R5.01.
• When using V net router style S3 or above
By setting the V net router properties, it is possible to select whether the Vnet/IP or V net
is the time master.
Also, the V net router compares the time of the master network and the time of the other
domains at 2-minute intervals, and performs time synchronization if a deviation of 5 sec-
onds or more occurs twice.
If neither [Transfer upper] nor [Transfer lower] of "Transfer System Time" is checked, time
synchronization will not be performed between the Vnet/IP and V net domain. (Both
[Transfer upper] and [Transfer lower] cannot be selected at the same time.)
By means of time synchronization methods using V net routers, SCSV1 stations can also syn-
chronize their time with the Vnet/IP network time instead of synchronizing with the V net time.
However, if SCSV1 stations on a V net use "synchronization with V net time", the system
times between SCSP2 stations on the Vnet/IP network and the SCSV1 stations on the V net
network may have up to a 5 second difference.

SEE
ALSO For more information about time synchronization when a Vnet/IP network and a V net domain are connected
by V net router style S3 or above, refer to:
“● Transferring System Time” in “■ Precautions when Engineering CENTUM Systems for Using V net
Routers: SCSP2/SCSP1” in 2.1.1, “Overview of the System Configuration” in Engineering Guide (IM
32Q01C10-31E)
For more information about setting V net router properties, refer to:
• 1.3, "Engineering of V net Router" in the CENTUM VP Communication Devices Reference (IM
33K03M10-50E)
• B2.5, "Setting the V net Router" in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• B2.5, "Setting the V net Router" in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
n Setting time from a SENG or HIS

From the Set Time dialog box of the SCS Maintenance Support Tool on SENG or the Set
Time dialog box on HIS, the network time can be changed.
For setting a Vnet/IP network time, the times of all stations in the same time group (including
the V net router) on the Vnet/IP network can be adjusted. However, if an SNTP server exists
in the time group and the SNTP server is available for synchronization, setting time from
SENG or HIS is ignored.
For setting a V net domain time from SENG or from HIS, the times of all stations, bus convert-
ers (BCV) and communication gateway units (CGW) that allow transferring time transmission
will be changed. However, the times of the Vnet/IP stations connected to a V net domain
through a V net router style below S3 will not be affected. Moreover, if the option of [Transfer
lower] of "Transfer System Time" on the router properties dialog box for a V net router style
below S3 is checked, the time synchronization will overwrite the time set from SENG or HIS.
SEE
ALSO For more information about time setting when a Vnet/IP network and a V net domain are connected by V net
router style S3 or above, refer to:
“● If a Vnet/IP Domain and a V net Domain are Connected via a V net Router” in “■ Precautions for Time
Synchronization” in 2.15, “Time Synchronization” in Engineering Guide (IM 32Q01C10-31E)
For more information about setting V net router properties, refer to:
• 1.3, "Engineering of V net Router" in the CENTUM VP Communication Devices Reference (IM
33K03M10-50E)

<B. Engineering > B-1
B. Engineering
This part describes an overview of engineering, network engineering, engineering of safety
control stations on SENG, and engineering on CENTUM.
SEE
ALSO For more information about the wide area communication router, refer to:
• B4.4, “Setting up wide area communication routers” on page B4-5
• 8, "Wide Area Communication Router" in the Communication Devices Reference (IM
33K03M10-50E)

<B1. Overview of engineering> B1-1
B1. Overview of engineering

This part describes an overview of engineering to create Vnet/IP domains.
Engineering work is performed on the SENG. When integrated with CENTUM system, an HIS
equipped with system builders is required.
Before stating the engineering work, you need to set up a computer for use as an SENG.
SEE
ALSO For more information about setting up an SENG, refer to:
B3., “Setting Up the SENG” in Installation (IM 32Q01C50-31E)
For more information about integration with CENTUM and installation for creating Vnet/IP domains, refer to:
CENTUM VP Installation (IM 33K01C10-50E)
n Engineering for building a system of Vnet/IP domains

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 SCSP2 Stations on SENG
On SENG, define the SCSP2 stations and create the applications.
• Engineering on CENTUM
Necessary when integrating ProSafe-RS with CENTUM.
Configure the system so that SCSP2 stations can be monitored from the SCS Status Dis-
play view on HIS. If multiple domains are connected, set the domains, or if the Vnet/IP
network is connected with a V net network, set the V net router accordingly.
If the system comprises only one domain and is not integrated with CENTUM system, it can
be built up by the network engineering and SCSP2 engineering on the SENG.
SEE
ALSO For more information about network engineering, refer to:
B2., “Network engineering” on page B2-1
For more information about the engineering of Safety Control Stations on SENG, refer to:
B3., “Engineering safety control stations on SENG” on page B3-1

<B2. Network engineering> B2-1
B2. Network engineering

This chapter explains precautions for network engineering.
SEE
ALSO For more information about network settings on SENG, refer to:
B3.3, “Configuring Network Settings” in Installation (IM 32Q01C50-31E)

<B2.1 Setting addresses on hardware> B2-2
B2.1 Setting addresses on hardware

This section explains the hardware address, domain number, station number and other set-
ting items for Vnet/IP stations.
n SCS Hardware setting items

SCS hardware setting items include the domain number and the station number for each
Vnet/IP station. The Vnet/IP address will be automatically determined according to the do-
main 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 stand-by side. If the control side and standby side
have different numbers, the CPU of the standby side cannot start for dual-redundant opera-
tion.
Usually, set the FIX switch on the CPU module of the SCSP2 to OFF. OFF means Auto Nego-
tiation. By default, OFF is set.
SEE
ALSO For more information about setting methods, refer to:
• 4.2, “Processor Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
• 6.7, “Setting the Vnet/IP Interface Card Station Address” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
For more information about setting V net router, refer to:
• E6.3, "Communication Module" in the CENTUM VP Communication Devices (IM 33K50D10-50E)
• D6.5.3, "Communication Modules" in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• D6.5.3, "Communication Modules" in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
n Domain number
The Vnet/IP domain number needs to be set within the range of 1 to 31 (When integrated with
CENTUM: 1 to 16). The domain numbers of the connected Vnet/IP network and V net net-
work should not be identical.
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.

<B2.2 Procedures and precautions for adding a station or domain> B2-3
B2.2 Procedures and precautions for adding a

station or domain
This section describes the procedure when adding a station to an existing Vnet/IP network
and the procedure and precautions when adding a domain to Vnet/IP network.
n Procedures and precautions for adding a Vnet/IP station

When adding a station to Vnet/IP network, follow the following procedure:
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.
l Case 1: When using existing Layer 2 switches (ports are available on

existing Layer 2 switches)
1. In the Network Status Display dialog box on an HIS, check that both buses are normal.
(*1)
2. Make sure that the additional station is not powered.
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 3 switch is disabled, enable the port.
(*1)
5. Connect the BUS2 port of the additional station to the Layer 2 switch for BUS2 with a
cable. If the port on the Layer 3 switch is disabled, enable the port.
(*1)
7. Turn on the power of the additional station.
(*1)
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Over-
view or SCS State Management) of SCS Maintenance Support Tool on an SENG to check the bus status. When you call up
the SCS status display window, select the project of a running SCS and then call up the window.
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
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.
(*1)
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.
(*1)
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.
(*1)
12. Add a station according to the procedure for "Case 1".
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.
l Case 1: When using existing Layer 3 switches (ports are available on

Firstly, carry out steps 1 to 5 shown below to configure Layer 3 switches for BUS1 and BUS2.
Next, add stations by following the procedures in "Procedures and Precautions for Adding a
Vnet/IP Station."
(*1)
2. Make the necessary settings on the existing Layer 3 switch for BUS1. If the port on the
Layer 3 switch is disabled, enable the port.
(*1)
4. Make the necessary settings on the existing Layer 3 switch for BUS2. If the port on the
Layer 3 switch is disabled, enable the port.
(*1)
6. Add stations for the new domain by following the procedures in "Procedures and Pre-
cautions for Adding a Vnet/IP Station."

l Case 2: When you need to add Layer 3 switches (no ports are available on
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 "Procedures and Precautions for Adding a
Vnet/IP Station."
(*1)
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.
(*1)
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 to an existing Layer 2 or Layer 3 switch
for BUS2 with a cable.
(*1)
8. Add stations for the new domain by following the procedures in "Procedures and Pre-
cautions for Adding a Vnet/IP Station."

<B3. Engineering safety control stations on SENG> B3-1
B3. Engineering safety control stations

on SENG
From the SENG on Vnet/IP network or the SENG on V net network, the engineering and off-
line downloading for SCSP2 stations can be performed. However, offline downloading is not
possible through a wide area communication router.
IMPORTANT
When passing data between SENG and HIS, or when SENG is sharing database with other
SENG, if the network addresses of the devices are different, the names of other devices or
PCs should be put into the hosts file for name resolution.
SEE
ALSO For more information about the wide area communication router, refer to:
• B4.4, “Setting up wide area communication routers” on page B4-5
• 8, "Wide Area Communication Router" in the Communication Devices Reference (IM
33K03M10-50E)
n Differences in engineering for SCS connected to Vnet/IP and SCS

connected to V net
The following settings differ in an SCS connected to a Vnet/IP and an SCS connected to a V
net. Set these items according to the control bus that is connected.
• Station models
• Time synchronization type setting in SCS Constant builder
SEE
ALSO For more information about creating SCS project, refer to:
3.1, “Creation of New SCS Projects” in Engineering Reference (IM 32Q04B10-31E)

<B4. Engineering on CENTUM> B4-1
B4. Engineering on CENTUM

In this chapter, how to define SCSP2 stations on CENTUM, and how to set the domain prop-
erties and the V net routers will be explained.
If the system configured with ProSafe-RS only, these engineering are unnecessary.

<B4.1 Engineering safety control stations on CENTUM> B4-2
B4.1 Engineering safety control stations on

CENTUM
The SCSP2/SCSP1 stations need to be defined on CENTUM engineering builders.
IMPORTANT
The domain number defined in the newly created SCS station should be the domain number
of the Vnet/IP domain instead of the V net domain. If the V net domain is defined, the station
needs to be deleted and then created again with the correct Vnet/IP domain number.
SEE
ALSO For more information about creating SCS project on CENTUM, refer to:
2.2, “Engineering on the CENTUM side” in Integration with CENTUM VP/CS 3000 (IM 32Q01E10-31E)
n Defining SCS stations on CENTUM

SCS stations need to be defined on CENTUM System View. The following types of SCS sta-
tions can be defined.
Table B4.1-1 SCS station types

Station Type Description
SSC60S-S, SSC50S-S Safety Control Unit (for Vnet/IP, rack-mounted, Standard Type)
SSC60S-F, SSC50S-F Safety Control Unit (for Vnet/IP, rack-mounted, Wide range Temperature Type)
SSC60D-S, SSC50D-S Redundant Safety Control Unit (for Vnet/IP, rack-mounted, Standard Type)
Redundant Safety Control Unit (for Vnet/IP, rack-mounted, Wide Range Temper-
SSC60D-F, SSC50D-F
ature Type)
SEE
ALSO For more information about defining SCS stations on CENTUM, refer to:
2.2.1, “SCS creation” in Integration with CENTUM VP/CS 3000 (IM 32Q01E10-31E)

<B4.2 Setting domain properties> B4-3
B4.2 Setting domain properties

When integrated with CENTUM, domain properties should be set and downloaded using
CENTUM engineering builders. The domain properties are downloaded right after changing
and downloaded with the project common files.
If a system consists of ProSafe-RS only, there will no need to set the domain properties, the
default settings should be used.
SEE
ALSO For more information about setting domain properties, refer to:
• B2.3, “Setting Domain Properties” in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
• B2.3, “Setting Domain Properties” in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
n Settings of domain properties

The setting items of Domain Properties are listed in the table below.
Table B4.2-1 Settings of domain properties

Setting item Setting (Default) Description
Domain number for this domain. Displays the domain
Domain number (*1) -
number of self-domain.
Time group number.
Time Group 0 to 7 (1) If 0 is specified, time synchronization between do-
mains will not be performed.
Con- Specify the IP address of SNTP server on bus 1. If
nect nnn.nnn.nnn.nnn (None) omitted, the preset IP address of 192.168.<domain
SNTP Server Bus 1 number>.254 will be used.
IP Address Con- Specify the IP address of SNTP server on bus 2. If
nect nnn.nnn.nnn.nnn (None) omitted, the preset IP address of 192.168.<128+do-
Bus 2 main number>.254 will be used.
Comment Up to 100 bytes (None) Comment of a domain. This is not displayed on HIS
All setting items of "Reception from Domains" are
Select All (*2) -
checked.
All setting items of "Reception from Domains", except
Clear All (*2) -
Re own domain, are unchecked.
ce Numbers of domains to be selected for reception.
pti Domain (*1) -
They include V net domains.
on
fro Checked/Unchecked: Specify whether HIS messages (operation history,
m HIS Message Receive/Not receive (Re- buzzer stop command, etc.) generated from the corre-
Do ceive) sponding domain will be received.
m Checked/Unchecked: Specify whether SCS and FCS messages (sequence
ain FCS Message Receive/Not receive (Re- messages, system alarms, etc.) generated from the
s ceive) corresponding domain will be received.
Checked/Unchecked: Specify whether to receive TCP communication to the
FCS TCP Receive/Not receive (Re- SCS and FCS of this domain from the corresponding
ceive) domain.
*1: Display only

*2: "Select All" and "Clear All" are buttons, cannot be used for setting.

<B4.3 Setting V net routers> B4-4
B4.3 Setting V net routers

When integrated with CENTUM, the communications between Vnet/IP domain and V net do-
main are performed through a V net router. Setting the V net router needs to be performed on
CENTUM engineering builders.
SEE
ALSO For more information about system engineering through V net router, refer to:
• “■ Precautions when Engineering CENTUM Systems for Using V net Routers: SCSP2/SCSP1” in
2.1.1, “Overview of the System Configuration” in Engineering Guide (IM 32Q01C10-31E)
• “■ Precautions when Engineering CENTUM Systems for Using Vnet/IP Domains: SCSP2/SCSP1”
in 2.1.1, “Overview of the System Configuration” in Engineering Guide (IM 32Q01C10-31E)
For more information about setting V net router, refer to:
• E6.3, "Communication Module" in the CENTUM VP Communication Devices (IM 33K50D10-50E)

<B4.4 Setting up wide area communication routers > B4-5
B4.4 Setting up wide area communication

routers
In a system integrated with CENTUM, the wide area communication router enables communi-
cations among Vnet/IP domains that are distributed in remote areas. Perform engineering of
wide area communication routers by using the engineering function of CENTUM.
SEE
ALSO For more information about precautions for CENTUM engineering when using wide area communication rout-
ers, refer to:
“■ Precautions when Engineering CENTUM VP Systems for Using WAC Router” in 2.1.1, “Overview of
the System Configuration” in Engineering Guide (IM 32Q01C10-31E)
For more information about settings of the wide area communication router, refer to:
8.2, "Engineering of the WAC Router" in the Communication Devices Reference (IM 33K03M10-50E)

Rev-1
Revision Information
Title : ProSafe-RS Vnet/IP
Manual No. : IM 32Q56H10-31E
Jan. 2015 / 4th Edition / R3.02.20 or later*
*: Denotes the release number of the Software Product corresponding to the contents of this Man-
ual. The revised contents are valid until the next edition is issued.
Introduction ProSafe-RS document map has been removed, descriptions of “Safety, Protection, and
Modification of the Product” have been modified.
Oct. 2013/3rd Edition/R3.02.10 or later
Introduction Description of station types has been changed.
A2, A2.2, A3, A3.2, A3.4, A4, Descriptions of the wide area communication router have been added.
B3, B4.4
A3.1 Descriptions of redundant configuration have been changed.
A3.2, A3.3, A3.4 Transmission delay time between Vnet/IP domains has been changed.
Dec. 2012/2nd Edition/R3.02 or later
A, B A summary page has been added.
A1, A2, B2 Descriptions of Ethernet have been changed due to elimination of Vnet/IP open commu-
nication-related descriptions.
A2, A3.3 Ethernet has been added to figures.
A3.4 A figure showing examples of wide area network connection has been deleted, and de-
scriptions have been changed.
Aug. 2011/1st Edition/R3.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
n Written by Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

Prosafe-Rs Vnet/Ip: User'S Manual

Uploaded by

Copyright:

Available Formats

Prosafe-Rs Vnet/Ip: User'S Manual

Uploaded by

Document Information

Original Title

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

Prosafe-Rs Vnet/Ip: User'S Manual

Uploaded by

Copyright:

Available Formats

User's

Safety Precautions for Use

Indicates the OFF position of a power on/off switch.

n Notes on Handling User's Manuals

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

n Warning and Disclaimer

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

Identifies instructions that must be observed to prevent damage

Identifies important information required to understand opera-

Identifies additional information.

Identifies referenced content.

l Commonly Used Conventions throughout the User's Manuals

l Conventions Used to Show Key or Button Operations

l Conventions of a User-defined Folder

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

n Integration with CENTUM

n Explanation of Hardware and Software Behaviors in the User's

Table Info-1 Names of SCS and Safety Control Unit Used

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

Copyright and Trademark Notices

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

IM 32Q56H10-31E 4th Edition

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

IM 32Q56H10-31E 4th Edition

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A1. Overview of Vnet/IP network

n Communication paths of control communication

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A2. Vnet/IP network system

n System components of a Vnet/IP network

Console type HIS or

L2SW L2SW L2SW Vnet/IP

SENG: Safety engineering PC

Figure A2-1 System components of a Vnet/IP network

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

• Wide area communication router (AW810D)

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

n Compatibility between Vnet/IP and V net

n Connecting general-purpose Ethernet devices

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A2.1 System with ProSafe-RS only

n Overview of a System with ProSafe-RS only

n Precautions for systems that include only one SCSP2 station

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A2.2 System integrated with CENTUM

n Overview of functionality supported by connecting Vnet/IP domains

n Overview of functionality supported by connecting Vnet/IP domains

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A3. Vnet/IP network connections

n Outline of Vnet/IP network connections

Can be connected to WAN

V net BCV: Bus converter

Figure A3-1 Outline of Vnet/IP network connections

IM 32Q56H10-31E 4th Edition : Jan.30,2015-00

A3.1 Connect devices included in Vnet/IP

n Specification when connecting devices in a Vnet/IP domain