S56H1021 PDF

Users
Manual ProSafe-RS
Vnet/IP
IM 32S56H10-21E
IM 32S56H10-21E
3rd Edition

Introduction
Vnet/IP is a network that conforms to the IEEE802.3 and TCP/IP communication standards.
The ProSafe-RS can configure a safety control system using Vnet/IP as its control bus.
This manual describes the network and engineering of Vnet/IP.
This manual provides information for systems consisting of ProSafe-RS alone or systems where
ProSafe-RS is integrated with CENTUM VP/CS 3000.
SEE
ALSO If you integrate ProSafe-RS with FAST/TOOLS (Yokogawa SCADA system), read the following instead of this
manual.
4, Vnet/IP in FAST/TOOLS-Integrated Configuration in Integration with FAST/TOOLS (IM 32S56H20-21E)
The structure of this manual is as follows:
PART A: Vnet/IP Network

This part describes an overview of Vnet/IP, system configuration and time synchronization.
PART B: Engineering
This part describes how to use the system builders to perform engineering.
Media No. IM 32S56H10-21E (CD) 3rd Edition : Dec. 2009 (YK) IM 32S56H10-21E 3rd 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 32S56H10-21E 2nd Edition : Dec.15,2008-00

iii
Safety Precautions
n Safety, Protection, and Modification of the Product
In order to protect system controlled by this product, the product itself and ensure safe
operation, observe the safety precautions described in this users manual. We assume no
liability for safety if users fail to observe these instructions when operating the product.
You must use this product according to the instructions described in user manuals. If not,
protective functions of this product may not work as expected.
If any protection or safety circuit is required for system controlled by the product or for the
product itself, prepare it separately.
Be sure to use the parts approved by Yokogawa Electric Corporation (hereafter simply
referred to as YOKOGAWA) when replacing parts or consumables.
Modification of the product is strictly prohibited.
The following symbols are used on the product and in this user manual to indicate that
safety precautions are required:
Indicates that user must take caution. The symbol on the equipment refers the user to the
relevant manual to avoid potentially hazardous situations that may result in injury or death.
The symbol appears next to the cautionary information in user manuals required to avoid
harm to personnel and to the equipment.
Indicates a protective grounding terminal. Before using the product, ground the terminal.
Indicates a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates that main switch is ON.
Indicates that main switch is OFF.
IM 32S56H10-21E 1st Edition : May 30,2008-00

iv
n Notes on Handling User Manuals

Please hand over user manuals to your end users so that they can have them on hand for
convenient reference.
Please read the user manuals thoroughly before using the product.
The purpose of these user manuals is not to warrant that the product is well suited to any
particular purpose but rather to describe the functional details of the product.
YOKOGAWA reserves the right to make improvements in the user manuals and product at
any time, without notice or obligation.
If you have any questions, or you find mistakes or omissions in the user manuals, please
contact our sales representative or your local distributor.
n Warning and Disclaimer

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

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
Tagname TUN {-Window size} {=Display position}
l Conventions used to show Key or Button Operations:
Characters enclosed by square brackets ([ ]):

Characters enclosed by square brackets within any description of a key or button operation,
indicate either a key on the keyboard, a button name on a window, or an item displayed on a
window.
Example:
Click the [OK] button.
l Conventions of User Defined Folder

User-Defined Folder Name
If the path of a folder can be defined by users, it is written within parentheses.
Example: (RS Project Folder) \SCS0101
If the RS Project Folder is C: \MYRSPJT, the above path becomes: C: \MYRSPJT\SCS0101

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 32S56H10-21E 3rd 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.

TocA-1
ProSafe-RS
Vnet/IP
IM 32S56H10-21E 3rd Edition
CONTENTS
PART-A Vnet/IP Network
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 Connection in a 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-6
A3.4 Network Connection through Public Communication Lines..................... A3-9
A3.5 Vnet/IP Bus Status........................................................................................ A3-10
A4. Time Synchronization of Vnet/IP...........................................................A4-1

TocB-1
ProSafe-RS
Vnet/IP
IM 32S56H10-21E 3rd Edition
CONTENTS
PART-B Engineering
B1. Overview of Engineering........................................................................B1-1
B2. Network Engineering..............................................................................B2-1
B2.1 Setting Addresses on Hardware................................................................... B2-2
B2.2 Setting the IP Addresses................................................................................ B2-3
B2.3 Procedures and Precautions for Adding a Station or Domain.................. B2-6
B3. Engineering of Safety Control Stations on SENG...............................B3-1
B4. Engineering on CENTUM........................................................................B4-1
B4.1 Engineering of Safety Control Stations on CENTUM................................. B4-2
B4.2 Set Domain Properties................................................................................... B4-3
B4.3 Set V net Router.............................................................................................. B4-4

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

Vnet/IP achieves a high-speed control network while conforms to the IEEE802.3 and
TCP/IP communication standards. It is designed as a duplexed network; it conducts open
communication using two communication systems of bus 1 and bus 2, and the various
standard protocols of control communication and Ethernet. When configuring a network,
you can use commercially available Ethernet communication devices.
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
paths, control communication and open communication.
Control communication is the communication for transferring control data. The inter-SCS safety
communication is also a kind of control communication.
Open communication is the communication conducted by using the various standard protocols of
Ethernet.
As for the hardware of a Vnet/IP network, such as transmission media (Ethernet cables), Layer 2
switches, Layer 3 switches and routers, commercially available general-purpose communication
devices can be used.
n Communication Paths of Control Communication and Open

Communication
Vnet/IP is designed as a duplexed network. In Vnet/IP, a duplexed bus is configured with
independent subnets of bus 1 and bus 2.
If both buses are normal, bus 1 is used for control communication, and bus 2 is used for open
communication. If bus 1 fails, control communication is performed using bus 2. In this case,
because open communication is also performed using bus 2, control communication and open
communication coexist. Therefore, to secure the band for control communication, the band for
open communication will be restricted.

<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
components 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 below.
Console type HIS or

HIS Installed with
System Builders HIS or HIS Installed
Exaopc
SENG with System Builders
Vnet/IP
domain 3
Bus 1 side Bus 1 side
SCSP L3SW L3SW
L2SW L2SW L2SW Vnet/IP

L2SW L2SW L2SW domain 2
Bus 2 side L3SW
Vnet/IP L3SW Bus 2 side
domain 1
Router Bus 2 side
V net router General-purpose

FCS Ethernet device
V net domain 4
Vnet/IP network
Intranet
SCSV
SENG: Safety engineering PC
SCSP, SCSV: 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 control station
Exaopc: OPC server
L2SW: Layer 2 switch
A020001E.ai
Figure System Components of Vnet/IP Network
TIP
In this manual, the safety control station connected in a Vnet/IP network is referred to as SCSP, and the safety
control station connected in V net is referred to as SCSV.

l Vnet/IP Station
A Vnet/IP station in a domain is connected to a Layer 2 switch in each bus. The Vnet/IP stations
are the following below. Stations of a CENTUM system on a Vnet/IP network are also the network
components for system configuration.
SENG
SENG is a Safety Engineering PC. It is a Vnet/IP station connected to the Vnet/IP network
through a VI702/VI701 card. The VI702/VI701 card contains two ports of connectors to
connect Vnet/IP communication cables to support duplexed Vnet/IP buses.
SCSP (SSC60S, SSC60D, SSC50S, SSC50D)
SCSP is a Safety Control Station connected on the Vnet/IP network. The transmission
speed of SCSP is 100Mbps.
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 router is a
device of CENTUM system.
HIS
HIS is an Operation and monitoring station of CENTUM, in which, the CENTUM engineering
builders should be installed. If the V net routers are used in the system, the engineering
builders are required for engineering and maintenance for the V net routers. The HIS
hardware configuration is similar to SENG. Same as the V net router, the HIS is also a
station of CENTUM system.
SEE
ALSO For more information about Vnet/IP stations of CENTUM system, see the following:
System Components of Vnet/IP Network in A1, Overview of Vnet/IP Network of the CS 3000 Vnet/IP
(IM 33Q06H90-31E).
System Components of Vnet/IP Network in A1, Overview of Vnet/IP Network of the CENTUM VP
Vnet/IP (IM 33L01A10-40E).
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 and 124 general-purpose Ethernet devices (PCs,
routers, 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
The Vnet/IP stations and general-purpose Ethernet devices in a domain are connected to the
Vnet/IP buses through the Layer 2 switches. At least two Layer 2 switches are required for bus1
and bus 2 respectively.
l Layer 3 Switch
Layer 3 switches are used to connect among Vnet/IP domains on each bus.
l Router
Routers with security capabilities are used for connecting bus 2 with external network such as
Intranet so as to ensure the security of the Vnet/IP network.

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. Also, a station that uses a PC such as an SENG
and an HIS as its platform can connect to Vnet/IP by replacing the communication interface with
a Vnet/IP interface card (VI702/VI701).
n Connecting General-Purpose Ethernet Devices

General-purpose Ethernet devices are connected to bus 2 of Vnet/IP.
To connect Vnet/IP with an external network such as an Intranet, separate the network using a
router.
IMPORTANT
Use a hub to adjust traffic of communication flow from general-purpose Ethernet devices
to a Vnet/IP network so as to prevent it from exceeding 300 Mbps (for example, up to three
100 Mbps ports).
On the Vnet/IP network, SCSP stations that are connected to general-purpose Ethernet
devices should use Layer 2 switches. The Layer 2 switches should be the intelligent
switches that can prevent the open communication multicasts from flowing into the SCSP
stations.
SEE
ALSO For more information about selecting the Layer 2 switches for network configuration, see the Vnet/IP Network
Configuration Guide (TI 33P01B10-31E).

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

This section explains a system configured solely with ProSafe-RS. In this type of system,
Vnet/IP network 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, SCSP stations and Layer 2 switches.
The open communication among SENGs is performed using Vnet/IP bus 2. The dedicated
Ethernet cable is not required.
The system consists of a single Vnet/IP domain.
The clocks in the SCSP and SENG stations are synchronized via Vnet/IP Time
Synchronization. An SNTP (Simple Network Time Protocol) server can be deployed for
standard time synchronization.
IMPORTANT
Under the following circumstances, the ProSafe-RS should be integrated with CENTUM system:
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 Notice on System with One SCSP Station Only

If a system is configured with SENG and one SCSP 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 SCSP station is running for normal operation while SENG power is off.
- The SCSP CPU is non-redundantly configured, or if one of the CPU fails on the SCSP
with dual-redundantly configured CPU.

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

When integrated with CENTUM, a system configured by placing the SCSP stations and
an SENG on a Vnet/IP network; and placing the SCSV stations and an SENG on a V net
network
ProSafe-RS/CENTUM integrated system cannot only be connected with other RS projects
but also with multiple CENTUM projects.
n Overview of a System Integrated with CENTUM

The overview of a system integrated with CENTUM is as follows:
The SENG on a Vnet/IP network can perform engineering or maintenance works for SCSP
stations on Vnet/IP network and the SCSV stations on a V net network.
Communications between stations on Vnet/IP network and stations on V net network are
smooth when going through V net routers as if barriers did not exist.
Inter-SCS safety communications can be performed through the following routes:
Within a Vnet/IP domain
Between Vnet/IP domains (Vnet/IP domain Layer 3 switch Vnet/IP domain)
Between V net domain and Vnet/IP domain (V net domain V net router Vnet/IP domain)
Between two V net domains separated by a Vnet/IP domain
(V net domain V net router Vnet/IP domain - V net router - V net domain)
The open communications between SENGs and between SENG and HIS are carried out
through the Vnet/IP bus 2. The dedicated Ethernet cable is not required.
The time of SCSP stations and SENG on a Vnet/IP network can be synchronized using the
Vnet/IP network time together with CENTUM stations. By connecting to an SNTP server,
synchronizing with standard time is possible.
The engineering and maintenance works for SCSP stations on Vnet/IP network and
SCSV stations on V net can be performed from the SENG on the V net. However, the time
changed from the SENG on the V net does not affect the time on the Vnet/IP network.
On the Network Status Display dialog box of HIS, the communication status among the
stations in the domain, and the communication status among the domains can be displayed
and referenced.
IMPORTANT
The inter-SCS safety communication between SCSP stations cannot be established if the two
stations located in two Vnet/IP domains are separated by a V net domain.
SEE
ALSO For more information about system expansion, see the following:
Expandability of System in 2.1.1, Overview of the System Configuration in the Engineering Guide (IM
32S01C10-21E)
For more information about time synchronization, see the following:
A4, Time Synchronization of Vnet/IP
For more information about the displaying SCS status, see the followings:
3.1.2, Management of SCS States in the Utilities and Maintenance Reference (IM 32S04B20-21E)
3.1.4, SCS Station Status Display View in the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)

<A3. Vnet/IP Network Connections> A3-1
A3. Vnet/IP Network Connections

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

An illustration of Vnet/IP network connection 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 SCSP L2SW: Layer 2 switch
A030001E.ai
Figure Illustration of Vnet/IP Network Connection

<A3.1 Connection in a Vnet/IP Domain> A3-2
A3.1 Connection in a Vnet/IP Domain

Devices in a Vnet/IP domain are connected in the star network using Layer 2 switches
of 1 Gbps as the key devices. Since the redundantly configured Vnet/IP buses are also
functioning as independent subnets of 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 protect Layer
2 switches with an uninterruptible power supply (UPS) so that Layer 2 switches will not stop due
to power failure.
If the Layer 2 switches stop due to power failure, there will be the following effects:
Communication error will occur.
For dual-redundant SCSP or FCS stations, when both buses fail, the controlling CPU will
also fails 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 by momentary power failure, it takes several seconds for the
communication with 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 (Vnet/IP stations including V net routers):
Max. 64 Stations
Other general-purpose Ethernet devices (PCs, routers, etc.):
Max. 124 devices
Distance between Vnet/IP stations: Max. 40 km
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)
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 should avoid multiple routes.
Otherwise, the communication may not be properly performed.
SCSP SCSP
L2SW L2SW
L2SW
A030101E.ai

<A3.1 Connection in a Vnet/IP Domain> A3-3
TIP
It is also possible to use a connection faster than 1 Gbps for the connection between Layer 2 switches.
For dual-redundantly configured stations such as SCSP 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
cable
Max. 5 km
L2SW L2SW
SCSP
A030102E.ai
Figure Connection Example of Devices in a Vnet/IP Domain

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

A Layer 3 switch is required for the connection between Vnet/IP domains. Install a Layer 3
switch in each bus of dual-redundantly configured Vnet/IP buses and connect it to other
domains. By using a leased line as the transmission path, the domains can be connected
through the wide area networks.
The connection of multiple domains is supported in the CENTUM integration structure. A
system with ProSafe-RS only does not support the connection of multiple domains.
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: 250 ms or less
IMPORTANT
The connection between any two communicating domains should avoid multiple routes.
Otherwise, the communication may not be properly performed.
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW
A030201E.ai
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.
Bi-Directional Bi-Directional
Domain 4 Domain 5
Bridge L3SW L3SW
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW
Hierarchical
Domain 6
A030202E.ai
Figure Domain Connection Types in Vnet/IP

<A3.2 Connection between Vnet/IP Domains> A3-5
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. Moreover,
when a domain is set to receive FCS messages, it can also receive SCS messages (such as
system alarm messages). If a domain is set to receive FCS TCP frames, it can also receive SCS
TCP communication frames. By the default settings on the Domain Properties 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 domains.
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 messages). If the domain
is set to receive FCS TCP frames, it can also receive the SCS TCP communication frames.
l Bridge Connection
This connection type guarantees the independence of a domain. It can be established by
setting 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 SCSP stations are located in 2 different Vnet/IP domains, both domains
should be set to allow the reception of FCS TCP communication for engineering and
maintenance purpose.
When two SCSP 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.
SEE
ALSO For more information about Domain Properties, see the following:
B2.3, Setting Domain Properties in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
B2.3, Setting Domain Properties in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
For more information about time group, see the following:
Time Group in A4, Time Synchronization of Vnet/IP
TIP
To access the tag names of function blocks or variables from the CENTUM stations across the domains is
possible regardless the type of connections.
When setting domain properties, it is also possible to set the domain to receive HIS messages only, FCS
messages only or FCS TCP communication only.

<A3.3 Connection between Vnet/IP and V net Domains> A3-6
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 must be done from the HIS on the Vnet/IP domain.
Because the connection of a Vnet/IP domain and V net domain is bi-directional, it is possible to
perform the operation and monitoring of SCSs or FCSs from either domain.
When conducting engineering of CENTUM, all stations on both Vnet/IP and V net networks can
be handled by one project. It is also possible to handle them as separate projects, but using the
Multiple Project Connection package to connect these projects.
On SENG, the SCSP stations of an SCS project on Vnet/IP network and the SCSV stations 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 SCSP and SCSV stations are
displayed together.
The information bus of a V net domain (i.e., the Ethernet for linking the SENG and HIS) must be
connected to Vnet/IP bus 2 via a router.
Router
SENG HIS Ethernet
SENG HIS
Connect to bus 2
Vnet/IP
network V net
V net router
SCSV
SCSP FCS FCS

A030301E.ai
Figure V net Connection
IMPORTANT
Allocate only one path from a Vnet/IP network to a specific control bus 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 control 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 two Vnet/IP domains are separated by a V net domain, communication cannot be performed
between the two Vnet/IP 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 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 from the View of Vnet/IP Stations

The communication reach from the view of Vnet/IP stations is shown below:
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 250 ms.)
[GW 2 Level]
Between Vnet/IP domains.
[GW 0 Level]
: SCSP
: SCSV

AVR: V net router
BCV: Bus converter
CGW: Communication gateway unit
A030302E.ai
Figure Communication Reach from the View of Vnet/IP Stations

l Communication Reach from the View of V net Stations
The communication reach from the view of V net stations is shown below:
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]
: SCSP
: SCSV
AVR : V net router

BCV : Bus converter
CGW: Communication gateway unit
A030303E.ai
Figure Communication Reach from the View of V net Stations
SEE
ALSO For more information about the number of levels of bus converters that connect other control buses, see the
following:
L1.1, Outline of Bus Converter for V net in Communication Devices of CS 3000 Reference (IM 33S01B30-
01E)
L1.1, Outline of Bus Converter for V net in Communication Devices of CENTUM VP Reference (IM
33M01A30-40E)

<A3.4 Network Connection through Public Communication Lines> A3-9
A3.4 Network Connection through Public

Communication Lines
Connection between Vnet/IP domains can be established through the public
communication lines for communicating with remote Vnet/IP domains. This type of
connection can be established when integrated with CENTUM system.
IMPORTANT
Same as the general transmission delay between any two Vnet/IP domains, the
transmission delay here should also be less than 250 ms.
If inter-SCS safety communications are performed between domains connected over a
wide area, it is recommended that the public communication lines should be faster than
100Mbps.
n Wide Area Network Connection

A system can be connected to the wide area network by placing the Vnet/IP network at the
upper level and the V net network at the lower level and then using V net routers to replace
the communication gateway units (CGWs). Moreover, if the lower level is changed to Vnet/IP
network, the V net routers will not be required. Though required when connecting V net network
to wide area networks, the following devices are not required for Vnet/IP network.
HIS in each domain for engineering CGW.
Ethernet for the builder to communicate with HIS that is in remote location.
Wide area connection Change upper level into Change lower level into
of V net Vnet/IP network Vnet/IP network
Ethernet
HIS/SENG SCSP HIS/SENG SCSP
HIS/SENG SCSV
V net Vnet/IP Vnet/IP

domain A domain A
CGW Router Router Router Router Router
Router Router Router Router

CGW Router
V net Vnet/IP Vnet/IP

domain B domain B
SCSV HIS
Ethernet V net SCSP SENG
router
V net
SCSV SENG
A030401E.ai
Figure Wide Area Network Connection

<A3.5 Vnet/IP Bus Staus> A3-10
A3.5 Vnet/IP Bus Status

How to check the Vnet/IP bus status will be explained in this chapter.
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 error 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. The Vnet/IP
network bus status can be displayed in the System Status Overview window, the SCS Status
Display window and 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

This status shows the communication status of the stations in the entire Vnet/IP network, i.e., in
all connected domains as well as the devices (such as Layer 3 switches and so on) connecting
domains. For example, when referencing the HIS System Status Overview window of domain
1, if abnormality occurs in bus 1 of a station in domain 5, the status of bus 1 of Vnet/IP indicates
abnormality.
The Vnet/IP bus status consists of the following three elements:

Bus status in own domain
Communication status of devices connected between domains
Bus status 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
A030501E.ai
Figure Elements of the Vnet/IP Bus Status

l Displaying Station Communication Status of a Domain
Each station in a Vnet/IP domain performs diagnostic communications alternatively using bus 1
and bus 2 to detect the communication errors.
A dual-redundant station with dual CPU modules has the following four types of communication
status.
Control side (*1) communication status of the stations.
Control side (*1) and Standby side communication status of the stations.
Standby side and Control side (*1) communication status of the stations.
Standby side communication status of the stations
*1: Including SENG, HIS and the non-redundant stations (such as SCS with single CPU module).
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, see the following:
C2, Network Status Display Dialog Box in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
C2, Network Status Display Dialog Box in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
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:
Single failure (either in bus 1 or in bus 2)
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

The Vnet/IP domains are communicated with each other using bus 1 and bus 2 alternatively and
the communication status can be monitored. On the HIS Network Status Display dialog box, the
communication statuses of devices on different domains can be displayed.
The bus status of one domain can be broadcasted to all the stations of the domains through the
communication among 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 of own domain is normal, the communication statuses of devices
connecting domains are reflected in the Vnet/IP bus status. In case of a single failure, the
status of that bus is handled as abnormal. In 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.

<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. An SNTP server can be used to get the reference time for the time
synchronization.
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. When synchronizing the stations in a Vnet/IP network with UTC (Universal
Time Coordinated), an SNTP server needs to be connected to the time group.
When an SNTP server is connected, while no engineering work is performed in ProSafe-RS or
CENTUM stations, all the stations of the time group will automatically synchronize the time with
the SNTP server.
An overview of time synchronization for a Vnet/IP network is shown below.

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-redundantly
structured.
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 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
SCSP SCSP
Vnet/IP
domain 2
Time accuracy between

domains 5 msec
SCSP
A040001E.ai
Figure Time Synchronization of Vnet/IP
SEE
ALSO For more information about time synchronization, see the following:
Precautions for Time Synchronization in 2.14, Time Synchronization in the Engineering Guide
(IM32S01C10-21E).

n Accuracy of Time Synchronization

The time clock of a Vnet/IP station performs time synchronization 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 shown below:
Table Accuracies of Network Time
Station Relative time accuracy
1 ms, When one bus is abnormal, the accuracy may become worse than 1 ms
In a domain
due to heavy open communication traffic.
5 ms, When one bus is abnormal, the accuracy may become worse than 5 ms
due 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 System Time
Station type Deviation from network time Time Adjustment
The deviation between the network time and the
SENG or HIS 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, FCS, V net router 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 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 performed can
be limited.
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 sever 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 in 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 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 the domain properties, see the following:
For more information about time group and the inter-SCS safety communication, see the following:
Precaution for Engineering in 2.8, Inter-SCS Safety Communication in the Engineering Guide (IM
32S01C10-21E)

n SNTP Server
To synchronize the network time of a Vnet/IP station with a standard time, connect an SNTP
server in each time group. Only one SNTP server can be connected to each bus within the same
time group. Generally, connect an SNTP server to bus 1 of Vnet/IP.
For the dual-redundant SNTP servers, one more SNTP server needs to be added and connected
to bus 2 of Vnet/IP. After connecting the SNTP server, the time master station in the Vnet/IP
network will synchronize the time according to the SNTP server on one bus. If the SNTP server
fails, the time synchronization will be performed with another SNTP server on the other bus.
IMPORTANT
After connecting an SNTP server in the time group if the SNTP server is not available for
synchronization, a notification will be broadcasted. Under this circumstance, all stations in the
time group will synchronize their time with the time master station of the time group. When
the SNTP server becomes ready for time synchronization, all stations in the time group will
synchronize their time with the SNTP server instead of the time master station.
The 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
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
synchronization with the SNTP server automatically.
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 station 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 with SOER (sequence of event records) installed 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 SCSP stations can synchronize times with the
SNTP server. The time accuracy depends on the time accuracy of the SNTP server. If the SNTP
server is not available in the network, the SCSP stations synchronize times with the Vnet/IP
network time master station.
The time of the SCSP stations, whether it is synchronized with the SNTP server or synchronized
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 with the network time changes, no diagnostic
message or system alarm to notify this event. If the time synchronization event needs to be
notified, 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.
However, the Synchronous Mode on the Communication tab of the SCS Constants builder
should be set to [Vnet/IP] regardless the SNTP server 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 Time Synchronization with V net Domain

When a V net domain is connected to a Vnet/IP network through a V net router, the time on the
Vnet/IP side will be used as the master, and the time of V net domain synchronizes with it. 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 each 2-minute,
and sets the Vnet/IP network time to the V net time if a deviation of 5 seconds or more occurs
twice.
SCSV stations can synchronize their time with the Vnet/IP network time instead of synchronizing
with the V net time. If SCSV stations on a V net is set to synchronize their time with the V net
time, the system times between SCSP stations on Vnet/IP network and the SCSV stations on V
net may have up to 5 second difference.
On the properties dialog box of a V net router, the time synchronization of the V net domain can
be set not to synchronize with the Vnet/IP network time by unchecking the option of [Transfer
System Time Transfer lower]. In this case, the V net domain time will not be synchronized with
the Vnet/IP network time. By default, this option is checked.
SEE
ALSO For more information about setting V net router properties, see the following:
B2.5, Setting the V net Router in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
B2.5, Setting the V net Router in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
n Set Time from 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 converters
(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 will not be affected. Moreover, if the option of [Transfer System Time Transfer lower] on
the router properties dialog box is checked, the time synchronization will overwrite the time set
from SENG or HIS.
SEE
ALSO For more information about setting V net router properties, see the following:

<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.
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)
For more information about integration with CENTUM and installation for creating Vnet/IP domains, see the
following:
11, Installation and Setup of Vnet/IP in the CS 3000 Installation (IM 33Q01C10-01E)
CENTUM VP Installation (IM 33M01A20-40E)
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.
Engineering on CENTUM
Necessary when integrating ProSafe-RS with CENTUM.
Configure the system so that SCSP stations can be monitored from the SCS Status Display
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 not integrated with CENTUM system, it can be built
up by the network engineering and SCSP engineering on the SENG.
SEE
ALSO For more information about network engineering, see the following:
B2, Network Engineering
For more information about the engineering of safety control stations on SENG, see the following:
B3, Engineering of Safety Control Stations on SENG

<B2. Network Engineering> B2-1
B2. Network Engineering

In this chapter, 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 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).

<B2.1 Setting Addresses on Hardware> B2-2
B2.1 Setting Addresses on Hardware

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

The hardware setting items include the domain address and station address for each Vnet/IP
station. The Vnet/IP address will be automatically determined according to the domain address
and the station address set on the hardware.
If the station has dual-redundant CPU modules, the same domain and station addresses should
be set on both the control side and standby side. If the control side and standby side have
different addresses, 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 chapters in the Safety Control Stations
(Hardware) (IM 32S06C10-21E)
4.2, Processor Module
6.7, Setting the Vnet/IP Interface Card Station Address
For more information about setting V net router, see the following:
D6.5.3, Communication Module in the CS 3000 Vnet/IP (IM 33Q06H90-31E)
D6.5.3, Communication Module in the CENTUM VP Vnet/IP (IM 33L01A10-40E)
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 network
should not be identical.
The domain number can be set by the DIP switch on the hardware.
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 Setting the IP Addresses> B2-3
B2.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.
IMPORTANT
The IP address used by Vnet/IP device must not be identical with the IP address of other
communication device.
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 the bus 2 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
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 bus system (bus 1 or bus 2).
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 domain number and bus system.
The subnet mask is 255.255.255.0.
Table 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 (On bus 2 only)
254: for SNTP server
Example of Control Communication IP Addresses
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
Therefore, the host address is as follows:
Host address = 64 x 2 = 128
The IP addresses of the SENG for control communication are as follows:
IP address of bus 1 = 192.168.1.128
IP address of bus 2 = 192.168.129.128

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 SCSs.
Set the control bus TCP/IP protocol IP address of SCS 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/Windows Server 2008)
3.4.6 Setting Vnet/IP Network Connection (Windows XP/Windows Server 2003)
IMPORTANT
Do not change the setting of Control Bus TCP/IP Protocol in the Network tab of Vnet/IP Station
Properties when working on CENTUM engineering builders.

<B2.3 Procedures and Precautions for Adding a Station or Domain> B2-6
B2.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 an existing Vnet/IP network.
n Procedures and Precautions for Adding a Vnet/IP Station

Follow these steps to add a station to an existing 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. 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 2 switch is disabled, enable the port.
4. In the Network Status Display dialog box, check that both buses are normal.(*1)
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.
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Overview
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
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 Precaution for Adding a Vnet/IP Domain

Follow these steps when you 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 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.

<B3. Engineering of Safety Control Stations on SENG> B3-1
B3. Engineering of 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 SCSP stations can be performed.
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.
n The Differences when Engineering for SCSP Stations and SCSV

Station
When engineering for SCSP stations and SCSV station, the following setting items are different.
Station models
Time synchronization type setting in SCS Constant builder
SEE
ALSO For more information about creating SCS project, see the following:
3.1, Creation of New SCS Projects in the Engineering Reference (IM 32S04B10-21E)

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

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

<B4.1 Engineering of Safety Control Stations on CENTUM> B4-2
B4.1 Engineering of Safety Control Stations on

CENTUM
The SCSP stations need to be defined on CENTUM engineering builders.
IMPORTANT
The domain number defined in the newly created SCSP 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, see the following:
2.2, Engineering of the CENTUM Side in the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
n Define SCSP Stations on CENTUM

SCSP stations need to be defined on CENTUM System View. The following types of stations can
be defined.
Table SCSP2 Station Types
Station Type Description
SSC60D-S Duplexed Safety Control Unit (for Vnet/IP, Standard Type)
SSC60D-F Duplexed Safety Control Unit (for Vnet/IP, Wide Range Temperature Type)
SSC60S-S Safety Control Unit (for Vnet/IP, Standard Type)
SSC60S-F Safety Control Unit (for Vnet/IP, Wide Range Temperature Type)
Table SCSP1 Station Types

Station Type Description
SSC50D-S Duplexed Safety Control Unit (for Vnet/IP, Standard Type)
SSC50D-F Duplexed Safety Control Unit (for Vnet/IP, Wide Range Temperature Type)
SSC50S-S Safety Control Unit (for Vnet/IP, Standard Type)
SSC50S-F Safety Control Unit (for Vnet/IP, Wide Range Temperature Type)
SEE
ALSO For more information about defining SCS stations on CENTUM, see the following:
2.2.1, SCS Creation in the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)

<B4.2 Set Domain Properties> B4-3
B4.2 Set 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, see the following:
n Setting Items of Domain Properties

The setting items of Domain Properties are listed in the table below.
Table Setting Items 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
domains will not be performed.
Specify the IP address of SNTP server on bus 1. If
nnn.nnn.nnn.nnn
Connect Bus 1 omitted, the preset IP address of 192.168.<domain
(None)
SNTP Server number>.254 will be used.
IP Address Specify the IP address of SNTP server on
nnn.nnn.nnn.nnn
Connect Bus 2 bus 2. If omitted, the preset IP address of
(None)
192.168.<128+domain 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)
own domain, are unchecked.
Numbers of domains to be selected for reception.
Domain (*1)
They include V net domains.
Checked/Unchecked: Specify whether HIS messages (operation history,
Reception
HIS Message Receive/Not receive buzzer stop command, etc.) generated from the
from Domains
(Receive) corresponding domain will be received.
Checked/Unchecked: Specify whether SCS and FCS messages (sequence
FCS Message Receive/Not receive messages, system alarms, etc.) generated from the
(Receive) corresponding domain will be received.
Checked/Unchecked: Specify whether to receive TCP communication to the
FCS TCP Receive/Not receive SCS and FCS of this domain from the corresponding
(Receive) domain.
*1: Display only
*2: Select All and Clear All are buttons, cannot be used for setting.

<B4.3 Set V net Router> B4-4
B4.3 Set V net Router

When integrated with CENTUM, the communications between Vnet/IP domain and V
net domain 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, see in 2.1, System Configuration of
the Engineering Guide (IM 32S01C10-21E)
Precautions when Engineering CENTUM Systems for Using V net Routers: SCSP
Precautions when Engineering CENTUM Systems for Using Vnet/IP Domains: SCSP
For more information about setting V net router, see the following:

Rev-1
Revision Information
Title : ProSafe-RS Vnet/IP
Manual No. : IM 32S56H10-21E
Dec. 2009/3rd Edition/R2.03 or later*

*: Denotes the release number of the software corresponding to the contents of this users manual. The
revised contents are valid until the next edition is issued.
Overall VI702, SSC60S, and SSC60D added.
SCS-IP and SCS-V changed to SCSP and SCSV, respectively.
A3 Figure Illustration of Vnet/IP Network Connection changed.
B2.3 Newly added (moved from supplement).
Dec. 2008/2nd Edition/R2.02 or later

Overall CS 3000 was changed to CENTUM, which refers to both CENTUM VP and CS 3000.
May. 2008/1st Edition/R2.01 or later

Newly published.
n For Questions and More Information

Online Query: A query form is available on the following URL for online query.
http://www.yokogawa.com/iss/
If you want more information about Yokogawa products, you can visit
Yokogawas homepage at the following web site.
Homepage: http://www.yokogawa.com/
n Written by Process Automation Product Marketing Dept.
Industrial Automation Systems Business Div.
Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

S56H1021 PDF

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

S56H1021 PDF

Uploaded by

Copyright:

Available Formats

Users

The structure of this manual is as follows:

PART A: Vnet/IP Network

ProSafe-RS Document Map

Safety Control Station Integration with Open Interfaces

Engineering Utilities and Messages

IM 32S56H10-21E 2nd Edition : Dec.15,2008-00

Indicates that main switch is ON.

Indicates that main switch is OFF.

IM 32S56H10-21E 1st Edition : May 30,2008-00

n Notes on Handling User Manuals

n Warning and Disclaimer

IM 32S56H10-21E 1st Edition : May 30,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 32S56H10-21E 2nd Edition : Dec.15,2008-00

Indicates a source to be referred to.

n Integration with CENTUM

IM 32S56H10-21E 2nd Edition : Dec.15,2008-00

n About Explanation of System Behavior

n About Station Types

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

Copyright and Trademark Notices

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

A1. Overview of Vnet/IP Network

n Network Conforming to IEEE802.3 and TCP/IP

n Communication Paths of Control Communication and Open

IM 32S56H10-21E 1st Edition : May 30,2008-00

A2. Vnet/IP Network System Configuration

n System Components of a Vnet/IP Network

Console type HIS or

L2SW L2SW L2SW Vnet/IP

Router Bus 2 side

V net router General-purpose

Figure System Components of Vnet/IP Network

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

n Compatibility between Vnet/IP and V net

n Connecting General-Purpose Ethernet Devices

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

A2.1 System with ProSafe-RS Only

n Overview of a System with ProSafe-RS Only

n Notice on System with One SCSP Station Only

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

A2.2 System Integrated with CENTUM

n Overview of a System Integrated with CENTUM

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

A3. Vnet/IP Network Connections

n Illustration of Vnet/IP Network Connections

Can be connected to WAN

V net BCV: Bus converter

Figure Illustration of Vnet/IP Network Connection

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

A3.1 Connection in a Vnet/IP Domain

n Specification when Connecting Devices in a Vnet/IP Domain

IM 32S56H10-21E 3rd Edition : Dec.22,2009-00

Figure Connection Example of Devices in a Vnet/IP Domain