Professional Documents
Culture Documents
Im33k10a10 50e
Im33k10a10 50e
Im33k10a10 50e
IM 33K10A10-50E
IM 33K10A10-50E
5th Edition
i
Introduction
Vnet/IP is a network that conforms to the IEEE802.3 and UDP/IP communication standards.
The CENTUM VP can configure a control system using Vnet/IP as its control bus. This man-
ual describes the overview, the system configuration and the time synchronization of Vnet/IP.
The structure of this manual is as follows:
• Chapter 1. Overview of Vnet/IP Network
This chapter describes the overview of Vnet/IP network.
• Chapter 2. Vnet/IP Network Connections
This chapter describes the various connections to configure a Vnet/IP network and the
communication status of the control bus.
• Chapter 3. Time Synchronization of Vnet/IP
This chapter describes the time synchronization of Vnet/IP.
• Chapter 4. Procedures and Precautions for Adding a Station or Domain
This chapter describes the procedures and precautions that must be followed when you
add a station or a domain to a Vnet/IP network.
Media No. IM 33K10A10-50E (DVD) 5th Edition : Aug. 2014 (YK) IM 33K10A10-50E 5th Edition : Aug.08,2014-00
All Rights Reserved Copyright © 2011, Yokogawa Electric Corporation
ii
Engineering
Consolidated Alarm
Engineering Engineering Management Software Batch Management
Reference Vol. 2 Reference Vol. 3 Reference System Reference
IM 33K03G22-50E IM 33K03G23-50E IM 33K03H20-50E IM 33K03J10-50E
FOUNDATION fieldbus
Engineering Guide
IM 33K20T20-50E
IM 33K02D10-50E IM 33K02D20-50E
Hardware
Turbomachinery
Peripherals Field Control Stations Input & Output Modules I/O Modules
IM 33K50C10-50E IM 33K50E40-50E IM 33K50G10-50E IM 33K10U10-50E
IM 33K50D10-50E IM 33K55W10-50E
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.
• Please 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.
Documentation Conventions
n Symbol Marks
The following symbols are used throughout the User's Manuals.
Identifies instructions that must be observed to avoid physical
injury, electric shock, or death.
n Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
n Drawing Conventions
Drawings used in the User's Manuals may be partially emphasized or simplified for conven-
ience of description, so that the unnecessary parts are omitted from the drawings.
Drawings of the window may be slightly different from the actual screen shots with different
settings or fonts; the difference is not extended to the range that may hamper the understand-
ing of basic functionalities and operation and monitoring tasks.
n Trademark Acknowledgements
• CENTUM, ProSafe, Vnet/IP, PRM, Exaopc, 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.
• EtherNet/IP is a trademark of the Open DeviceNet Vendor Association (ODVA).
• in fieldbus is a registered trademark of Fieldbus Foundation.
• HART is a registered trademark of the HART Communication Foundation.
• Java is a registered trademark of Oracle Corporation.
• MELSEC is a registered trademark of Mitsubishi Electric Corporation.
• Memocon-SC is a registered trademark of Yaskawa Electric Corporation.
• Modicon and Modbus are registered trademarks of Schneider Electric SA.
• PROFIBUS is a registered trademark of the PROFIBUS User Organization.
• SIEMENS and SIMATIC are registered trademarks of Siemens Industrial Automation Ltd.
• SmartPlant is a registered trademark of Intergraph Corporation.
• SYSMAC is a registered trademark of OMRON Corporation.
• All other company and product names mentioned in the User's Manuals are trademarks
or registered trademarks of their respective companies.
• We do not use TM or ® mark to indicate those trademarks or registered trademarks in the
User's Manuals.
• We do not use logos in the User's Manuals.
Vnet/IP
CONTENTS
1. Overview of Vnet/IP Network...............................................................1-1
2. Vnet/IP Network Connections............................................................. 2-1
2.1 Connection of Devices in a Vnet/IP Domain.............................................. 2-2
2.2 Connection between Vnet/IP Domains....................................................... 2-3
2.3 Vnet/IP Bus Status........................................................................................2-5
2.4 Connections with Other Control Bus Domains......................................... 2-8
3. Time Synchronization of Vnet/IP.........................................................3-1
4. Procedures and Precautions for Adding a Station or Domain.........4-1
n What is Vnet/IP
Vnet/IP is a redundantly configured control communication network. 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 communications. When bus 1 fails for some reason, bus 2
is used for control communications. The file transfer, data exchange and all the communica-
tions other than control communication are performed by other networks (Ethernet networks).
With the release of CENTUM VP R5.01, the guidelines are changed so that Vnet/IP is used
as a network for control communications, and other communications are performed on an in-
formation network other than Vnet/IP. This document is customized to address this change.
TIP For more information about Vnet/IP related CENTUM VP system specifications, refer to the Integrated Pro-
duction Control System CENTUM VP System Overview (Vnet/IP Edition) (GS 33K01A10-50E)
Firewall
Bus 1 side
L3SW
Vnet/IP Vnet/IP
Intranet
domain 1 domain 2
Bus 2 side
L3SW
SEE
ALSO For more information about 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. In the CENTUM
VP, combining Vnet/IP and V net/VL net domains, up to 16 domains can be set.
To each domain, up to 64 Vnet/IP stations can be connected.
l Vnet/IP Station
A Vnet/IP station in a domain is connected to a layer 2 switch in each bus. The following table
shows a list of Vnet/IP stations.
• FFCS-L, FFCS-V
FFCS-L and FFCS-V are control stations connected to Vnet/IP network. Each FFCS-L or
FFCS-V station may have up to 3 standard FIO type I/O nodes. In this case, including the
FCU node, the total number of nodes is 4. Furthermore, a FFCS-L with application ca-
pacity expansion package may consist of up to 15 nodes including FCU node; while a
FFCS-V may have up to 14 nodes including FCU node.
• General-Purpose PC + VI702 Card
A Vnet/IP station is connected to a Vnet/IP network through a VI702 card if the Vnet/IP
station is built using a general-purpose PC. The VI702 card contains two ports of connec-
tors to connect Vnet/IP communication cables to support redundant Vnet/IP buses.
• Wide Area Communication router
The Wide Area Communication router is a hardware device dedicated for the communica-
tions among the devices distributed in a wide area through wide area communication
lines.
• V net router
The V net router is the hardware dedicated to connect a Vnet/IP domain and a V net or a
VL net domain. It can also connect the V net domain of the CENTUM CS. It performs the
frame conversion and filtering between Vnet/IP and V net or between Vnet/IP and VL net.
TIP For more information about the Safety Control Station (Vnet/IP) of ProSafe-RS system, refer to the ProSafe-
RS Vnet/IP (IM 32Q56H10-31E.)
SEE
ALSO For more information about Wide Area Communication Router, refer to:
8, "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E)
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-H
HF bus
FFCS-L L2SW: Layer 2 switch
domain
FFCS-V L3SW: Layer 3 switch
TIP Wide Area Communication router can also be used for the connection between Vnet/IP domains.
SEE
ALSO For more information about connection between Vnet/IP domains using Wide Area Communication router, re-
fer to:
8, "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E)
IMPORTANT
Multiple stations will be connected to the layer 2 switch. If the layer 2 switches of both buses
stop due to power failure, a communication error will occur. Also, if a layer 2 switch is restar-
ted by momentary power failure, it may take several dozens of seconds to recover the station
communications. Therefore, 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 supply
abnormality.
IMPORTANT
Do not connect in such a way that multiple communication paths exist between any stations.
Normal communication will not be performed.
Connections among the devices within a Vnet/IP domain determined according to the cable
types and the distances between the connected devices.
TIP For more information about connections among the devices within a Vnet/IP domain, refer to:
• Integrated Production Control System CENTUM VP System Overview (Vnet/IP Edition) (GS
33K01A10-50E)
• Vnet/IP Network Construction Guide (TI 30A10A05-01E)
IMPORTANT
If the layer 3 switches stop due to power failure, the communication errors will occur. Also, if
the layer 3 switches are restarted by momentary power failure, it may take several dozens of
seconds to recover the domain communications. Therefore, 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 supply abnormality.
TIP Wide Area Communication router can also be used for the connection between Vnet/IP domains.
SEE
ALSO For more information about connection between Vnet/IP domains using Wide Area Communication router, re-
fer to:
8, "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E)
IMPORTANT
When the layer 3 switches are used for connecting the multiple Vnet/IP domains, the connec-
tion scheme should avoid the plural communication routes exist between any two domains.
Normal communication will not be performed.
The specification of connection between Vnet/IP domains using Wide Area Communication
router is as follows:
• Multi-level connection of Vnet/IP domains: Max. 2 levels (3 layers)
• Transmission delay between any domains: 500 msec or less
The specification of connection between Vnet/IP domains using layer 3 switch is as follows:
• Multi-level connection of Vnet/IP domains: Max. 15 levels (16 layers)
• Transmission delay between any domains: 250 msec or less
Bi-directional Bi-directional
Domain 4 Domain 5
L3SW L3SW
L3SW
Hierarchical
Bridge
Domain 6
L3SW: Layer 3 switch
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 properties of the
domains for receiving the FCS messages, HIS messages and FCS TCP communication
frames from the other domains.
By the default setting, a domain will receive all from the other domains.
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 the domain properties not to re-
ceive FCS messages, HIS messages and FCS TCP communication frames from the upper
domain; but the upper domain can receive them from the lower domain.
l Bridge Connection
This connection type guarantees the independence of a domain. This type of connection can
be established by setting the domain properties of the domain not to receive FCS messages,
HIS messages and FCS TCP communication frames from another domain.
TIP When setting Domain Properties, it is also possible to set so as to receive only one of HIS messages, FCS
messages and FCS TCP communication.
SEE
ALSO For more information about Domain Properties, refer to:
"■ Vnet/IP Domain Properties" in 2.1.1, "File Menu of System View" in the Engineering Reference Vol.1
(IM 33K03G21-50E)
TIP For an example, when viewing the system status of domain 1 on System View, if a station in domain 5 has
encounters bus 1 problem, the system behaves as follows:
• In the case that the version of System View is R5.02.00 or newer and the version of Vnet/IP is Rev.13 or
newer:
Bus abnormality status will be indicated only on the HISs of domain 5 where the Vnet/IP bus 1 abnor-
mality occurred.
• In other cases:
No matter what domain the bus abnormality occurs, and what domain the HIS belongs, the Vnet/IP bus
abnormality status will be indicated
The following behaviors are unchanged in the system prior or after R5.02.00:
• If Vnet/IP and V net are connected through AVR10D, a bus 1 abnormality occurred in the
Vnet domain will be notified as if the bus 1 abnormality in Vnet/IP domain.
• If Vnet/IP and V net are connected through AVR10D, a bus 1 abnormality occurred in the
Vnet/IP domain will be notified as if the bus 1 abnormality in Vnet domain.
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
*1: From R5.02.00 or newer and Vnet/IP Rev.13 or newer versions, the displayed bus status does not indicate the
bus status of other domains.
SEE
ALSO For more information about communication status, refer to:
4.9, "FFCS-V Status Display View" in the Human Interface Stations Reference Vol.1 (IM 33K03F21-50E)
HIS HIS
HIS HIS
Vnet/IP
network V net
V net router
FFCS-L FCS
FFCS-V
If the HISs of multiple domains are communicating through the V net routers, an Ethernet net-
work should be used to link the V net and Vnet/IP domains.
Vnet/IP Vnet/IP
domain 2 domain 3
V net domain 1
Layer 3 switch
V net router
V net domain
BCV-H
HF bus domain
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.
Vnet/IP network
V net V net
router router
V net domain 5 V net domain 11
BCV-V
FCS or BCV-H CGW
BCV-Q
V net domain 6 HF bus domain 17
BCV-V
FCS or BCV-H EFCS MOPS CGW
BCV-Q
V net domain 7 HF bus RL bus V net domain 12
Domain 18 Domain 19
V net/IP
domain 2
Lower domain
HIS
SEE
ALSO For more information about the V net router and the bus converter, refer to:
• 1, "V net Router" in the Communication Devices Reference (IM 33K03M10-50E)
• 2, "Bus Converter for V net" in the Communication Devices Reference (IM 33K03M10-50E)
• 3, "Bus Converter for VL net" in the Communication Devices Reference (IM 33K03M10-50E)
• 4, "Bus Converter for RL Bus" in the Communication Devices Reference (IM 33K03M10-50E)
• 5, "Bus Converter for HF Bus" in the Communication Devices Reference (IM 33K03M10-50E)
• 6, "Text Mode Communication Gateway Unit" in the Communication Devices Reference (IM
33K03M10-50E)
• 7, "Frame Mode Communication Gateway Unit" in the Communication Devices Reference (IM
33K03M10-50E)
L3SW
Vnet/IP L3SW Vnet/IP
domain 1 domain 3
HIS L3SW
L3SW L3SW
L3SW
FCS FCS
Vnet/IP
domain 2
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 per-
formed can be limited. For example, if the deviation in relative time due to variations in trans-
mission delay time between Vnet/IP domains cannot be ignored, separate time synchroniza-
tion between domains by defining time groups, and connect an SNTP server to each time
group.
Specify a time group using a number from 0 to 7. The default time group number is 1. To per-
form time synchronization only in a domain, set the time group number to 0. If an SNTP serv-
er does not exist in a time group, one of Vnet/IP stations in a time group will act as a time
master, and other stations in the same time group will synchronize with the network time of
the time master.
n SNTP Server
To synchronize the network time of a Vnet/IP station with the absolute 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. To duplex SNTP
servers, add one SNTP server to bus 2 of Vnet/IP.
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
IMPORTANT
• 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 2: When you need to add Layer 2 switches (existing Layer 2 switches
do not have unused ports)
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. In the Network Status Display dialog box on an HIS, check that both buses are normal.
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.
IMPORTANT
Make sure that there are no duplicate station addresses (domain number + station number) in
the system.
l Case 2: When you need to add Layer 3 switches (existing Layer 3 switches
do not have unused ports)
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. In the Network Status Display dialog box on an HIS, check that both buses are normal.
2. Make the necessary settings on the Layer 3 switch for BUS1 that you are going to add.
Vnet/IP
INDEX
Time Synchronization ........................................ 3-1
B
V
Bus Status ..........................................................2-5
Vnet/IP Network ................................................. 1-1
S
SNTP Server.......................................................3-2
T
Time Group......................................................... 3-2
Revision Information
Title: Vnet/IP
Manual No.: IM 33K10A10-50E
Aug. 2014/5th Edition/R5.04 or later*
* : Denotes the release number of the Software Product corresponding to the contents of this Manual.
The revised contents are valid until the next edition is issued.
Preface Descriptions of grounding are modified.
Apr. 2014/4th Edition/R5.03.20 or later
Preface Description of the caution symbol was modified.
Postface The "■ For Questions and More Information" was changed.
The “■ Printed by” was deleted.
Jun. 2013/3rd Edition/R5.03 or later
Preface The preface text was modified.
1. Descriptions were added, modified, and deleted.
A figure and a table were modified.
The section "● Layer 2 Switch (L2SW)" was added.
The section "■ Compatibility between Vnet/IP and V net" was deleted.
2. Descriptions were added.
2.1 Descriptions were deleted. A figure was deleted.
2.2 Descriptions were added.
2.4 Descriptions were modified.
The section "■ Connection with V net Domains of CENTUM CS 3000 R3.04 or Earlier"
was deleted.
Jun. 2012/2nd Edition/R5.02.00 or later
1. Descriptions were modified.
2.1 Descriptions were modified.
2.3 Descriptions on bus abnormality indications were modified.
2.4 Descriptions were modified.
Sep. 2011/1st Edition/R5.01 or later
Newly published