You are on page 1of 40

Vnet/IP

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

CENTUM VP Document Map
Installation
CENTUM VP License CENTUM VP
Installation Management Security Guide
IM 33K01C10-50E IM 33K01C20-50E IM 33K01C30-50E

Engineering

Field Control Stations Function Blocks Function Blocks Function Blocks
Reference Overview Reference Vol.1 Reference Vol.2
IM 33K03E10-50E IM 33K03E21-50E IM 33K03E22-50E IM 33K03E23-50E

Function Blocks Human Interface Human Interface Engineering
Reference Vol. 3 Stations Reference Vol. 1 Stations Reference Vol. 2 Reference Vol. 1
IM 33K03E24-50E IM 33K03F21-50E IM 33K03F22-50E IM 33K03G21-50E

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

SEBOL Communication with Communication with Communication
Reference Subsystems Using RIO Subsystems Using FIO Devices Reference
IM 33K03K10-50E IM 33K03L10-50E IM 33K03L20-50E IM 33K03M10-50E

Optional Functions Communication with Compliance with Generic Subsystem
Reference PROFIBUS Systems FDA: 21CFR Part 11 Gateway Reference
IM 33K03N10-50E IM 33K03P10-50E IM 33K03Q10-50E IM 33K03R10-50E

System Integration Unified Gateway Engineering Test
OPC Station Reference Station Reference Vnet/IP Guide
IM 33K03R20-50E IM 33K03R30-50E IM 33K10A10-50E IM 33K10H20-50E

Engineering CENTUM FOUNDATION fieldbus
Tutorial APCS Data Access Library Reference
IM 33K02E10-50E IM 33K15U10-50E IM 33K15P10-50E IM 33K20T10-50E

FOUNDATION fieldbus
Engineering Guide
IM 33K20T20-50E

Operation and Monitoring

HIS Operation Operating Messages

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

Communication Devices Migrated-FCS(FIO)

IM 33K50D10-50E IM 33K55W10-50E

IM 33K10A10-50E 5th Edition : Aug.08,2014-00

Protection. • The following symbols are used in the Product and User's Manuals to indicate the accom- panying safety precautions: Indicates that caution is required for operation. the protection pro- vided by the Product may be impaired. • If the Product is used in a manner not specified in the User's Manuals. However. and Modification of the Product • To protect the system controlled by the Product and the Product itself and to ensure safe operation. • If any protection or safety circuit is required for the system controlled by the Product or for the Product itself. which may be caused by accidents. • Thoroughly read and understand the information in the User's Manuals before using the Product. This terminal is used for grounding other than protective grounding. such as electrical shocks resulting from operational mistakes. Indicates an AC supply. Before using the Product. In the User's Manuals. Identifies a protective conductor terminal. n Notes on Handling User's Manuals • Hand over the User's Manuals to your end users so that they can keep the User's Man- uals on hand for convenient reference. Do not use the Product and its accessories for any purpose other than as intended by YOKOGAWA. • Do not use the Product and its accessories such as power cords on devices that are not approved by YOKOGAWA. please install it externally. the purpose of the User's Manuals is not to warrant that the Product is suitable for any particular purpose but to describe the functional details of the Product. • For the avoidance of doubt. you will find the precautions necessary to prevent physical injury or death. please observe the safety precautions described in this Manual. Yokogawa Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe the safety precautions and instructions when operating the Product. Indicates the ON position of a power on/off switch. Identifies a functional grounding terminal. you must ground the protective conductor terminal to avoid electric shock. Before using the Product. • Every effort has been made in the preparation of the User's Manuals to ensure the accu- racy of their contents. you must ground this terminal.08. A terminal marked "FG" also has the same function. iii Safety Precautions for Use n Safety.2014-00 . Indicates the OFF position of a power on/off switch. contact IM 33K10A10-50E 5th Edition : Aug. should you have any questions or find any errors. • Modification of the Product is strictly prohibited. • Use only spare parts that are approved by YOKOGAWA when replacing parts or consum- ables of the Product. • Contents of the User's Manuals are subject to change without notice. This symbol is labeled on the Prod- uct to refer the user to the User's Manuals for necessary actions or behaviors in order to protect the operator and the equipment against dangers such as electrical shocks. Indicates a DC supply.

or converting the Soft- ware Product to human-readable format may be performed for the Software Product. it is deemed as an infringement of YOKOGAWA's Intellectual Property rights. reverse compiling. or sublet for use by any third-party. converted. • No copy of the Software Product may be made for any purpose other than backup. • Please purchase the appropriate number of licenses of the Software Product according to the number of computers to be used. with respect to the Soft- ware Product's merchantability or suitability for any particular purpose. n Notes on Software • YOKOGAWA makes no warranties.2014-00 . IM 33K10A10-50E 5th Edition : Aug. iv us or your local distributor. • YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either using or not being able to use the Product. • No part of the Software Product may be transferred. The User's Manuals with incorrectly ordered pages or missing pages will be replaced. except as speci- fied in the warranty terms. n Warning and Disclaimer • Except as specified in the warranty terms. reverse assembling. without prior written consent from YOKOGAWA. other- wise. • Keep the software medium of the Software Product in a safe place. either expressed or implied.08. • No reverse engineering. YOKOGAWA shall not provide any warranty for the Product.

ALΔPIC010Δ-SC • Character string enclosed by braces { } Indicates character strings that may be omitted. or death. While operating an engineering window. Identifies instructions that must be observed to avoid physical injury. Example: . or system failures of the Product.0 • ▼ Mark This symbol indicates the description for an item for which you should make a setting in the product's engineering window. v Documentation Conventions n Symbol Marks The following symbols are used throughout the User's Manuals. In the online manuals. clicking on the reference link shown in green displays the referenced content.2014-00 . Identifies important information required to understand opera- tions or functions. This action does not ap- ply to the reference link shown in black. Example: . Identifies additional information. n Typographical Conventions The following typographical conventions are used throughout the User's Manuals.SV=50. Identifies referenced content.08. electric shock. l Commonly Used Conventions throughout the User's Manuals • Character string to be entered The characters that must be entered are shown in monospace font as follows: Example: FIC100. the help information for the selected item can be accessed from "Builder Definition Items" in the Help menu.sheet name} IM 33K10A10-50E 5th Edition : Aug. Identifies instructions that must be observed to prevent dam- ages to the software or hardware. Example: ▼ Tag Name. Listing more than one defini- tion item after this symbol implies that the paragraph on the page describes more than one definition items.PRΔTAG{Δ. Station Name • Δ Mark Indicates that a space must be entered between character strings.

<output value>…] • Characters enclosed by separators | | Indicates character strings that can be selected from more than one option. it indicates a key on the keyboard. vi l Conventions Used to Show Key or Button Operations • Characters enclosed by brackets [ ] When characters are enclosed by brackets in the description of a key or button operation. IM 33K10A10-50E 5th Edition : Aug.. l Conventions Used in Command Syntax or Program Statements The following conventions are used within a command syntax or program statement format: • Characters enclosed by angle brackets < > Indicate character strings that user can specify freely according to certain guidelines. <output value>. Example: #define <Identifier> <Character string> • ". <element number> 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. a key on the operation keyboard... Example: Imax (arg1. Example: sysalarm <format character string> [. 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. press the [ESC] key.08." Mark Indicates previous command or argument that may be repeated. Example: opeguide <format character string> [. or an item in a list box displayed in a window. arg2.] OG.2014-00 . a button name in a window..) • Characters enclosed by brackets [ ] Indicate character strings that may be omitted. Example: To alter the function.

• Memocon-SC is a registered trademark of Yaskawa Electric Corporation. electronic media. reprinting or reproducing the entire document is strictly pro- hibited by the Copyright Law. • Java is a registered trademark of Oracle Corporation. in the forms of paper documents. • Modicon and Modbus are registered trademarks of Schneider Electric SA. Exaopc. n Trademark Acknowledgements • CENTUM.2014-00 . Vnet/IP. transferred. Acrobat. Visual Basic. • Microsoft. You are allowed to print the required pages of the online manuals for the purposes of using or operating the Product. and Vis- ual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. or distributed to a third party in any manner (either in electronic or written form including. however. • EtherNet/IP is a trademark of the Open DeviceNet Vendor Association (ODVA). • SIEMENS and SIMATIC are registered trademarks of Siemens Industrial Automation Ltd. • PROFIBUS is a registered trademark of the PROFIBUS User Organization. • MELSEC is a registered trademark of Mitsubishi Electric Corporation. Visual C++. IM 33K10A10-50E 5th Edition : Aug. with- out limitation. • SYSMAC is a registered trademark of OMRON Corporation. ProSafe. • Ethernet is a registered trademark of Xerox Corporation. • in fieldbus is a registered trademark of Fieldbus Foundation. Nor it may be registered or recorded in the media such as films without permission. and transmission via the network). and Adobe Reader are registered trademarks of Adobe Systems Incor- porated. sold. • 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. Windows Server. and STARDOM are registered trademarks of YOKOGAWA. Windows Vista. Windows. • We do not use logos in the User's Manuals. Except as stated above. • SmartPlant is a registered trademark of Intergraph Corporation. • Adobe. no part of the online manuals may be reproduced. vii Copyright and Trademark Notices n All Rights Reserved The copyright of the programs and online manuals contained in the software medium of the Software Product shall remain in YOKOGAWA. • HART is a registered trademark of the HART Communication Foundation. PRM.08.

Blank Page .

2-2 2......... Procedures and Precautions for Adding a Station or Domain.................. Time Synchronization of Vnet/IP........................................................................................................................... 2-8 3.3 Vnet/IP Bus Status.. Overview of Vnet/IP Network....... Vnet/IP Network Connections.2-5 2....4-1 IM 33K10A10-50E 5th Edition : Aug............................................... Toc-1 Vnet/IP IM 33K10A10-50E 5th Edition CONTENTS 1............4 Connections with Other Control Bus Domains......................................................2 Connection between Vnet/IP Domains..1 Connection of Devices in a Vnet/IP Domain......3-1 4....1-1 2..2014-00 ............................. 2-3 2................................ 2-1 2............................................08..................................

Blank Page .

Layer 2 switches. n What is Vnet/IP Vnet/IP is a redundantly configured control communication network. The typical system configuration is shown below.3 and UDP/IP communication standards.08. Overview of Vnet/IP Network Vnet/IP achieves a high-speed control network while conforms to the IEEE802. Control communication is the communication for transferring control data. Layer 3 switches. redundant buses are configured with independent subnets of bus 1 and bus 2. As for the hardware of a Vnet/IP network. It supports a transmission speed of 1 Gbps.2014-00 .3 and UDP/IP Vnet/IP is a network that conforms to the IEEE802. Wide Area Communication router can also be used for the connection between Vnet/IP domains. IM 33K10A10-50E 5th Edition : Aug. The file transfer. data exchange and all the communica- tions other than control communication are performed by other networks (Ethernet networks).01.3 and UDP/IP communication standards. refer to the Integrated Pro- duction Control System CENTUM VP System Overview (Vnet/IP Edition) (GS 33K01A10-50E) n System Components of Vnet/IP Network The following describes the system components of a Vnet/IP network. In Vnet/IP. <1. the layer 3 switch is used for the connection between Vnet/IP domains. use Ethernet communication devices such as trans- mission media (Ethernet cables). the guidelines are changed so that Vnet/IP is used as a network for control communications. TIP For more information about Vnet/IP related CENTUM VP system specifications. With the release of CENTUM VP R5. bus 2 is used for control communications. and other communications are performed on an in- formation network other than Vnet/IP. Normally. As shown in the figure below. Overview of Vnet/IP Network> 1-1 1. This document is customized to address this change. bus 1 is used for control communications. n Network Conforming to IEEE802. Vnet/IP is a redundant network composed of bus 1 and bus 2. When bus 1 fails for some reason.

Table 1-1 List of Vnet/IP Stations Name Hardware General-purpose PC + VI702 HIS: Operation and monitoring station Console type HIS IM 33K10A10-50E 5th Edition : Aug. l Layer 3 Switch (L3SW) The layer 3 switches are used for communications among Vnet/IP domains. combining Vnet/IP and V net/VL net domains. The following table shows a list of Vnet/IP stations. If a Vnet/IP system consists of multiple domains. "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.08. In the CENTUM VP. Layer 3 switch is a network switch that has router functions. Overview of Vnet/IP Network> 1-2 Ethernet PRM Console type HIS General-purpose HIS/HIS equipped GSGW/UGS/ field communication Ethernet device with system builders Exaopc SIOS/APCS server Firewall Bus 1 side L3SW Vnet/IP Vnet/IP Intranet domain 1 domain 2 Bus 2 side L3SW Bus 1 side Bus 2 side L3SW L3SW FFCS-V V net router FFCS-L V net/VL net Vnet/IP domain 4 domain 3 L3SW: Layer 3 switch Figure 1-1 System Components of Vnet/IP Network SEE ALSO For more information about Wide Area Communication Router. <1. l Vnet/IP Station A Vnet/IP station in a domain is connected to a layer 2 switch in each bus. To each domain. The layer 2 switches with 1 Gbps communication speed are used for Vnet/IP. The layer 3 switches with 1 Gbps communication speed are used for Vnet/IP. up to 64 Vnet/IP stations can be connected. refer to: 8. up to 16 domains can be set. the communications among the domains are relayed by the layer 3 switches.2014-00 . l Layer 2 Switch (L2SW) The layer 2 switches are used for connecting the devices within a Vnet/IP domain.

TIP For more information about the Safety Control Station (Vnet/IP) of ProSafe-RS system. refer to: 8. To connect these control buses to Vnet/IP. • 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. while a FFCS-V may have up to 14 nodes including FCU node. n Connecting General-Purpose Ethernet Devices General-purpose Ethernet devices are not connected to Vnet/IP but an Ethernet network.) SEE ALSO For more information about Wide Area Communication Router. Each FFCS-L or FFCS-V station may have up to 3 standard FIO type I/O nodes. RL bus) cannot be connected directly to a Vnet/IP domain. Overview of Vnet/IP Network> 1-3 Name Hardware FFCS-L: Control station AFV10S/AFV10D FFCS-V: Control station AFV30S/AFV30D. IM 33K10A10-50E 5th Edition : Aug. • 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.2014-00 . <1. Furthermore. It performs the frame conversion and filtering between Vnet/IP and V net or between Vnet/IP and VL net. it must go through a bus converter (BCV-H. The VI702 card contains two ports of connec- tors to connect Vnet/IP communication cables to support redundant Vnet/IP buses. FFCS-V FFCS-L and FFCS-V are control stations connected to Vnet/IP network. It can also connect the V net domain of the CENTUM CS. "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E) n Connecting Control Buses Prior to the CENTUM CS Control buses prior to the CENTUM CS (HF bus. including the FCU node.08. BCV-L) of V net connected via a V net router. the total number of nodes is 4. refer to the ProSafe- RS Vnet/IP (IM 32Q56H10-31E. AFV40S/AFV40D SCS: Safety control station SSC60S/SSC60D. SSC50S/SSC50D APCS: Advanced process control station GSGW: Generic subsystem gateway SIOS: System Integration OPC Station UGS: Unified gateway station General-purpose PC + VI702 Exaopc PRM: Field communication server SENG: Safety engineering PC Wide Area Communication router AW810D V net router AVR10D (duplexed V net/VL net. In this case. single V net/VL net) • FFCS-L. • 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. a FFCS-L with application ca- pacity expansion package may consist of up to 15 nodes including FCU node.

Blank Page .

• Connection of devices in a Vnet/IP domain • Connection between Vnet/IP domains • Bus status of Vnet/IP • Connection with other control bus domain n Outline of Vnet/IP Network Connections An overview of Vnet/IP network connection in the CENTUM VP is shown below. re- fer to: 8. "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E) IM 33K10A10-50E 5th Edition : Aug. <2. 100 m L2SW levels leased line 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-H HF bus FFCS-L L2SW: Layer 2 switch domain FFCS-V L3SW: Layer 3 switch Figure 2-1 Outline of Network System Elements Connections TIP Wide Area Communication router can also be used for the connection between Vnet/IP domains. HIS/GSGW/UGS/ SIOS/APCS/Exaopc Broadband connection 1000BASE-T Up to seven is also possible using a Max. SEE ALSO For more information about connection between Vnet/IP domains using Wide Area Communication router.08.2014-00 . Vnet/IP Network Connections This chapter describes the various connections to configure a Vnet/IP network and the com- munication status of the control bus. Vnet/IP Network Connections> 2-1 2.

Therefore. each bus should have its own layer 2 switch as the hub. a communication error will occur. it may take several dozens of seconds to recover the station communications. If the layer 2 switches of both buses stop due to power failure. Also.08. IMPORTANT Multiple stations will be connected to the layer 2 switch. n Specification when Connecting Devices in a Vnet/IP Domain IMPORTANT Do not connect in such a way that multiple communication paths exist between any stations. if a layer 2 switch is restar- ted by momentary power failure.1 Connection of Devices in a Vnet/IP Domain The devices in the Vnet/IP domain are connected in a star topology using a layer 2 switch as the hub.1 Connection of Devices in a Vnet/IP Domain> 2-2 2. refer to: • Integrated Production Control System CENTUM VP System Overview (Vnet/IP Edition) (GS 33K01A10-50E) • Vnet/IP Network Construction Guide (TI 30A10A05-01E) IM 33K10A10-50E 5th Edition : Aug. Connections among the devices within a Vnet/IP domain determined according to the cable types and the distances between the connected devices. Normal communication will not be performed. TIP For more information about connections among the devices within a Vnet/IP domain. 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.2014-00 . <2. Because the redundant Vnet/IP buses are separated as independent subnets of each bus.

It is possible to configure a network coexisting these three types of connections. Set the connection types in Domain Properties for each domain. Normal communication will not be performed. By leasing the dedicated lines as the transmission paths among the domains.2014-00 .2 Connection between Vnet/IP Domains> 2-3 2. SEE ALSO For more information about connection between Vnet/IP domains using Wide Area Communication router. Also. The specification of connection between Vnet/IP domains using Wide Area Communication router is as follows: • Multi-level connection of Vnet/IP domains: Max.08. 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 n Connection between Vnet/IP Domains There are three types of connections between Vnet/IP domains: bi-directional. hierarchical and bridge connections. TIP Wide Area Communication router can also be used for the connection between Vnet/IP domains. the communication errors will occur. For a redundantly configured Vnet/IP network. <2. it may take several dozens of seconds to recover the domain communications. "Wide Area Communication Router" in the Communication Devices Reference (IM 33K03M10-50E) n Specification when Connecting between Vnet/IP Domains IMPORTANT When the layer 3 switches are used for connecting the multiple Vnet/IP domains. IM 33K10A10-50E 5th Edition : Aug. IMPORTANT If the layer 3 switches stop due to power failure. re- fer to: 8. Therefore. each bus should have a layer 3 switch for the connection of the domains. the connec- tion scheme should avoid the plural communication routes exist between any two domains.2 Connection between Vnet/IP Domains The layer 3 switches are used for connections among the Vnet/IP domains. 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. if the layer 3 switches are restarted by momentary power failure. the connections can be established through the wide area network.

but the upper domain can receive them from the lower domain. This type of connection can be established by setting the domain properties not to re- ceive FCS messages. TIP When setting Domain Properties. "File Menu of System View" in the Engineering Reference Vol. By the default setting. refer to: "■ Vnet/IP Domain Properties" in 2. it is also possible to set so as to receive only one of HIS messages. l Hierarchical Connection This connection type differentiates the upper and lower relationships between Vnet/IP do- mains.1 (IM 33K03G21-50E) IM 33K10A10-50E 5th Edition : Aug. This type of connection can be established by setting the domain properties of the domains for receiving the FCS messages.1. HIS messages and FCS TCP communication frames from another domain. HIS messages and FCS TCP communication frames from the other domains. l Bridge Connection This connection type guarantees the independence of a domain. HIS messages and FCS TCP communication frames from the upper domain.2 Connection between Vnet/IP Domains> 2-4 Bi-directional Bi-directional Domain 4 Domain 5 L3SW L3SW Domain 1 L3SW Domain 2 L3SW Domain 3 L3SW Hierarchical Bridge Domain 6 L3SW: Layer 3 switch Figure 2. a domain will receive all from the other domains.1. This type of connection can be established by setting the domain properties of the domain not to receive FCS messages.08. FCS messages and FCS TCP communication. SEE ALSO For more information about Domain Properties. <2.2-1 Domain Connection Types in Vnet/IP l Bi-Directional Connection This connection type does not differentiate the upper and lower relationships between Vnet/IP domains.2014-00 .

02. If the bus communi- cation status changes. n Elements of the Vnet/IP Bus Status In V net.02.3 Vnet/IP Bus Status The Vnet/IP bus status shows the bus communication status of the stations in all domains connected to a Vnet/IP network as well as the devices connected among domains.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. the bus status indicates an abnormality. in Vnet/IP. TIP For an example. 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 IM 33K10A10-50E 5th Edition : Aug. the system behaves as follows: • In the case that the version of System View is R5. The Vnet/IP bus status is reflected in the Network Status Display dialog box.00 or newer and the version of Vnet/IP is Rev. it is output on an HIS as a system alarm message. if a station in domain 5 has encounters bus 1 problem.00: • If Vnet/IP and V net are connected through AVR10D. *1: The version of Vnet/IP firmware is marked on the label sealed on VI70x card. It acts as follows when abnormality occurs: • In the case that the version of CENTUM VP software is R5. It is irrelevant to the bus communication status of other domains. any bus in any domain becomes abnormal.08. This bus status includes the statuses of all stations. • In other cases: No matter what domain the HIS belongs.2014-00 . • 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 bus status shows the bus communication status in one domain. • In other cases: No matter what domain the bus abnormality occurs.00 or newer and the ver- sion of Vnet/IP firmware (*1)is Rev. layer-2-switches(L2SW) and com- munication devices among the domains.13 or newer: Bus abnormal status means the bus in the domain that the HIS belongs is abnormal.3 Vnet/IP Bus Status> 2-5 2. and what domain the HIS belongs. <2. the Vnet/IP bus abnormality status will be indicated The following behaviors are unchanged in the system prior or after R5. the displayed bus status may indicate different communication status vary with the version combination of CENTUM VP software and Vnet/IP firmware.02. On the other hand. a bus 1 abnormality occurred in the Vnet domain will be notified as if the bus 1 abnormality in Vnet/IP domain. when viewing the system status of domain 1 on System View.

1 (IM 33K03F21-50E) l Bus Status in a Domain The bus status in a domain is created from the communication status between stations in each domain. refer to: 4.02. • Both buses failure Only the communication status of the bus that encountered the communication error first indicates error. Bus status of 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 *1: From R5.3 Vnet/IP Bus Status> 2-6 (”1) Vnet/IP The information of a domain is not bus status broadcasted to the stations beyond the domain. Figure 2. Each station holds the following four types of communication status: • Communication status between control sides of stations(*1) • Communication status between control sides of stations(*1) and standby sides of sta- tions • Communication status between standby sides of stations and control sides of sta- tions(*1) • Communication status between standby sides of stations *1: The control side communication status of stations also indicates the communication status of non-redundant stations and HISs. its meaning varies with the type of failure: • Single bus failure Communication status of the abnormal network bus indicates error. If the bus status shows abnormality. SEE ALSO For more information about communication status. Based on the diagnosed information. IM 33K10A10-50E 5th Edition : Aug. except the bus status signals. the other one does not. TIP If both buses cannot communicate with a specific station. and the bus status will not be handled as abnormal. it is determined that the station itself has failed. However. "FFCS-V Status Display View" in the Human Interface Stations Reference Vol. communication statuses of all sta- tions on one bus for each station in a domain can be displayed.9. the displayed bus status does not indicate the bus status of other domains.08.00 or newer and Vnet/IP Rev.3-1 Elements of Vnet/IP Bus Status l Displaying the Communication Status between Stations in a Domain Bus 1 and bus 2 of each station in a Vnet/IP domain perform communication alternately while diagnose each other.2014-00 . the HIS in an external domain can access the information.13 or newer versions. <2.

only the status of the bus that encountered the communication error first indicates error. the communication statuses of devices be- tween domains are reflected in the Vnet/IP bus status. The communication statuses of devices connected between domains are indicated by a two-dimensional table of all domains for each bus. the status of that bus indicates error. If both buses fail. • Communication Statuses of Devices Connected between Domains If the bus status of own domain is normal. by this communication between domains. the other one does not. • Bus Statuses of Other Domains If the communication statuses of all devices connected between domains are normal. 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. the bus statuses of other domains are reflected in the Vnet/IP bus status. If a single bus fails. only the status of the bus that encountered the communication error first indicates error. the bus statuses of other domains are notified to an HIS. the status of that bus indicates error.08. If both buses fail. the other one does not. IM 33K10A10-50E 5th Edition : Aug.2014-00 . the Vnet/IP bus statuses of both buses are not handled as abnormal. it is reflected in the Vnet/IP bus status. If a single bus fails. Also.3 Vnet/IP Bus Status> 2-7 l Communication Statuses of Devices Connected between Domains The communication status between domains is checked by performing mutual communication using bus 1 and bus 2 between Vnet/IP domains. <2. However. even if a different bus becomes abnormal in different domains. and only the status of the bus in which abnormality is detected first is handled as abnormal.

2014-00 . • Configuring of the V net router can be performed on either V net side or Vnet/IP side.4 Connections with Other Control Bus Domains To connect between a Vnet/IP domain and V net. and between a Vnet/IP domain and a VL net domain. and integrate the multiple projects using the package for connecting multiple projects. the upper level Vnet/IP domain and lower level V net domain should be specified. it is possible to operate and monitor the control stations of other domains.01 or later version system builders. Configuring the V net router should be performed on the upper level Vnet/IP domain side. the V net control communications are linked through the V net router. Ethernet HIS HIS HIS HIS Vnet/IP network V net V net router FFCS-L FCS FFCS-V Figure 2. <2.4 Connections with Other Control Bus Domains> 2-8 2.4-1 Connection with V net If the HISs of multiple domains are communicating through the V net routers. When conducting engineering. It is also possible to put Vnet/IP and V net to separate projects.08. When V net router is used. Because the connection between Vnet/IP and V net domains is bi-directional. an Ethernet net- work should be used to link the V net and Vnet/IP domains. The following features are available for engineering if the V net router of Style S3 or newer is used with the CENTUM VP R5. one project may contain both Vnet/IP and V net domains. • Either Vnet/IP domain or V net domain can be specified as the upper level domain. n Connection between Vnet/IP and V net Domains To connect a Vnet/IP network and V net domains. a V net router is used. IM 33K10A10-50E 5th Edition : Aug.

4-3 Connection with Other Control Bus IM 33K10A10-50E 5th Edition : Aug. The CENTUM CS 1000 does not require Ethernet. connect a Vnet/IP network and VL net domains using a V net router. They can be integrated using the Multiple Project Connection function. and VL net will be a CENTUM CS 1000 project.08. and further routing through a bus converter (BCV-H. Layer 3 switch Vnet/IP domain Vnet/IP domain Layer 3 switch V net router V net domain BCV-H HF bus domain Figure 2.4-2 Ethernet Connections of HISs n Connection between Vnet/IP and VL net Domains Similar to the connection with V net. BCV-L). it is necessary to configure a network by connecting to a V net domain via a V net router. At that time. In the case of VL net single. Besides Vnet/IP.2014-00 . the project on the CENTUM VP side will always be an upper project. <2. an Ethernet network should be prepared. however. it is required when connecting to Vnet/IP. the VL net coupler of the V net router will be single.4 Connections with Other Control Bus Domains> 2-9 Ethernet HIS HIS HIS HIS Vnet/IP Vnet/IP domain 2 domain 3 V net router V net router V net domain 1 Figure 2. Vnet/IP will be a CENTUM VP project. n Connection with HF Bus/RL Bus The HF bus and RL bus used in control systems prior to the CENTUM CS cannot directly be connected to Vnet/IP. To connect Vnet/IP with these control buses.

4 Connections with Other Control Bus Domains> 2-10 IMPORTANT Allocate only one path from a Vnet/IP network to a specific control bus domain via a V net router. Otherwise. of Max. the V net router should not be counted. • If the V net domain is higher than Vnet/IP domain. of No. <2. you can establish the connection between the Vnet/IP domain and an existing control bus that is two levels of bus converters away from the V net router. If a V net router is defined so that two or more paths exist as paths to a specific control domain. No.08. of No. l Restrictions on Multi-Level Connection of Control Buses A station on Vnet/IP network can access a station on the other control bus. of levels = 0 levels = 1 levels = 1 levels = 2 levels = 1 Figure 2. • Communication frames to nonexistent domains converge depending on the definition of the routing of the V net router. The method to count the number of levels in multi-level connection of control buses is as fol- lows: • Do not count the Vnet/IP domains on an access path into the network levels.2014-00 . • A bus converter for connecting other control buses can be counted as a network level. of levels = 2 No. Thus. HIS HIS HIS HIS HIS HIS HIS 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 FCS EFCS MFCD FCS No.4-4 Connection with Other Control Bus IM 33K10A10-50E 5th Edition : Aug. a V net router can be counted as one level (up to two levels). No. of Max. the following problems will occur: • The path from the Vnet/IP side to the corresponding V net domain changes randomly. up to two levels of bus converters beyond the V net router.

08. refer to: • 1. IM 33K10A10-50E 5th Edition : Aug. V net domain 3 V net FCS Counted as one level router V net/IP domain 4 Lower domain HIS Figure 2. "Bus Converter for VL net" in the Communication Devices Reference (IM 33K03M10-50E) • 4. For more information about the replacement. "Bus Converter for RL Bus" in the Communication Devices Reference (IM 33K03M10-50E) • 5. existing communication gateway units (CGWs) for wide area communication can be replaced with layer 3 switches. contact Yokogawa service agents. "Frame Mode Communication Gateway Unit" in the Communication Devices Reference (IM 33K03M10-50E) l Replacing Communication Gateway Units (CGWs) for Wide Area Communication By utilizing connection between Vnet/IP domains. router this router is not counted. "Bus Converter for HF Bus" in the Communication Devices Reference (IM 33K03M10-50E) • 6. <2.2014-00 . "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. "Text Mode Communication Gateway Unit" in the Communication Devices Reference (IM 33K03M10-50E) • 7.4-5 V net domains and Vnet/IP domains SEE ALSO For more information about the V net router and the bus converter.4 Connections with Other Control Bus Domains> 2-11 HIS Upper domain V net domain 1 V net Counted as one level router V net/IP domain 2 V net Since V net is lower FCS than Vnet/IP.

Blank Page .

Between domains The relative time accuracy deteriorates in proportion to transmission delay time variations between domains. The relative time accuracies of the network time are shown below: Table 3-1 Accuracies of Network Time Station Relative time accuracy ±1 msec. there is a method to connect an SNTP server. This time is referred to as the network time. When an SNTP server is connected to Vnet/IP. When one bus is abnormal. Define a time group in domain units. a group called a time group is defined. and time synchronization is performed in time group units.2014-00 . <3. The hardware of Vnet/IP performs time synchronization in the entire Vnet/IP network. the accuracy may become worse In a domain than ±1 msec. In the Vnet/IP network. IM 33K10A10-50E 5th Edition : Aug. to specify the reference time for synchronization. An overview of time synchronization in Vnet/IP is shown below. n Overview of Time Synchronization Time synchronization in a Vnet/IP network is performed in time group units. Time Synchronization of Vnet/IP> 3-1 3. Time Synchronization of Vnet/IP Time synchronization is performed between Vnet/IP stations connected to a Vnet/IP network. each station in Vnet/IP synchronizes with universal time of convention (UTC) of the SNTP server. To synchronize each station in a Vnet/IP network with UTC. ±5 msec. Time management is performed via a control bus. Time group 1 Time group 2 SNTP server SNTP server HIS Time accuracy in a HIS domain ±1 msec L3SW Vnet/IP L3SW Vnet/IP domain 1 domain 3 HIS L3SW L3SW L3SW L3SW FCS FCS Vnet/IP domain 2 Time accuracy between domains ±5 msec FCS L3SW: Layer 3 switch Figure 3-1 Time Synchronization of Vnet/IP n Accuracy of Time Synchronization The Time Management function of a Vnet/IP station is the same as the V net system of the CENTUM VP.08. Also. connect an SNTP server in each time group. the accuracy may become worse than ±5 msec. When one bus is abnormal.

the relative time accuracy rea- ches 1 second.08. and connect an SNTP server to each time group. n Time Synchronization between V net and Vnet/IP Domains Time Synchronization between V net and Vnet/IP domains act differently under the following circumstances: • When Style 2 or an earlier version V net router is used: IM 33K10A10-50E 5th Edition : Aug. 0.5 sec checked. Specify a time group using a number from 0 to 7.<128 + domain number>. the time of that station gradually approaches the network time of the same time group. The default time group number is 1.168. Within 5 seconds after system startup. If there is a deviation of on general-purpose PC 0. and within 5 minutes. The system time always synchro- FCS. Time Synchronization of Vnet/IP> 3-2 The system software of a Vnet/IP station references the network time. The entire Vnet/IP network can be defined on one time group. the deviations between the system time and the network time are as shown below: Table 3-2 Accuracies of System Time Station type Error from network time Time adjustment method The deviation between the net- work time and the system time is HIS or GSGW stations operating Max. For example. and adjusts its own system time to the network time. separate time synchroniza- tion between domains by defining time groups. 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.254 n Time Synchronization after Powering On a Station After a station is powered on. <3. by separating domains in the same Vnet/IP network into time groups. the system time is adjusted to the network time. one of Vnet/IP stations in a time group will act as a time master. Generally.254 • IP address of an SNTP server connected to bus 2 of Vnet/IP 192.168.<domain number>. the range in which time synchronization is per- formed can be limited. V net router None nizes with the network time. To per- form time synchronization only in a domain. n SNTP Server To synchronize the network time of a Vnet/IP station with the absolute time. set the time group number to 0. connect an SNTP server to bus 1 of Vnet/IP. Only one SNTP server can be connected to each bus within the same time group. and other stations in the same time group will synchronize with the network time of the time master. Because of the differences in the time adjustment methods. add one SNTP server to bus 2 of Vnet/IP. On the other hand.5 sec or more. If an SNTP serv- er does not exist in a time group.2014-00 . To duplex SNTP servers. the relative time accuracy within the same domain rea- ches ±1 msec. n Time Group The time group denotes a range in which time synchronization is performed. connect an SNTP server in each time group. if the deviation in relative time due to variations in trans- mission delay time between Vnet/IP domains cannot be ignored.

Time Synchronization of Vnet/IP> 3-3 The clock on Vnet/IP side holds the master time. the clock on V net side will be forced to follow the master time of Vnet/IP. IM 33K10A10-50E 5th Edition : Aug. Moreover. If the time difference between the two is greater than 5 seconds and continues for two comparisons. If the time difference between the two is greater than 5 seconds and continues for two comparisons. • When Style 3 or a newer version V net router is used: The clock on either V net side or Vnet/IP side can be designated for holding the master time. The clock on V net side cannot be set to be a master. the V net router compares the two clocks on V net side and Vnet/IP side peri- odically with an interval of two minutes. the time synchronization will be per- formed. Moreover. <3. the time synchronization will be per- formed to correct the time of V net domain. the V net router compares the two clocks on V net side and Vnet/IP side peri- odically with an interval of two minutes.2014-00 .08.

Blank Page .

2014-00 . In the Network Status Display dialog box on an HIS. Turn on the power of the Layer 2 switch that you have added. Procedures and Precautions for Adding a Station or Domain> 4-1 4. The procedures for two cases are provided below. enable the port. 4. 8. you can add a station to Layer 3 switches directly instead of Layer 2 switches. Next. Connect the BUS1 port of the additional station to the Layer 2 switch for BUS1 with a ca- ble. l Case 2: When you need to add Layer 2 switches (existing Layer 2 switches do not have unused ports) Firstly. enable the port. n Procedures and Precautions for Adding a Vnet/IP Station Follow these steps to add a station to a Vnet/IP network. Disconnect the cable between any one of the existing stations and a Layer 2 switch for BUS1. 2. 5. check that both buses are normal. check that both buses are normal. Make sure that the additional station is not powered. In the Network Status Display dialog box. 6. If the port on the Layer 2 switch is disabled. 2. l Case 1: When using existing Layer 2 switches (Layer 2 switches have unused ports) 1. • Turn off the power of the additional station before you connect the cables. IM 33K10A10-50E 5th Edition : Aug. 3. Connect the existing station that you have disconnected at step 2 to the newly added Layer 2 switch for BUS1 with a cable. In the Network Status Display dialog box. Connect the BUS2 port of the additional station to the Layer 2 switch for BUS2 with a ca- ble. check that both buses are normal. Connect the additional Layer 2 switch for BUS1 to the existing Layer 2 switch for BUS1 with a cable. TIP Alternatively. check that both buses are normal. 1. In the Network Status Display dialog box on an HIS. 4. In the Network Status Display dialog box. check that both buses are normal. 7. Procedures and Precautions for Adding a Station or Domain This section describes the procedures and precautions that must be followed when you add a station or a domain to a Vnet/IP network. Turn on the power of the additional station. make sure that there are no duplicate station addresses. 5. If the port on the Layer 2 switch is disabled. IMPORTANT • Before you add a station. carry out the procedure for “Case 1” above to add a station. <4. 3. carry out steps 1 to 11 as shown below to add Layer 2 switches for BUS1 and BUS2.08.

carry out the procedure for “Case 1” to add a station. 8. check that both buses are normal. Disconnect the cable between any one of the existing stations and a Layer 2 switch for BUS2. Next. 7. In the Network Status Display dialog box.08. check that both buses are normal. <4.2014-00 . Now. IM 33K10A10-50E 5th Edition : Aug. Make the necessary settings on the existing Layer 3 switch for BUS2.” 1. IMPORTANT Make sure that there are no duplicate station addresses (domain number + station number) in the system.” 1. carry out steps 1 to 7 as shown below to add Layer 3 switches for BUS1 and BUS2.” l Case 2: When you need to add Layer 3 switches (existing Layer 3 switches do not have unused ports) Firstly. enable the port. check that both buses are normal. Next. This completes the configuration of Layer 3 switches. In the Network Status Display dialog box. If the port on the Layer 3 switch is disabled. Make the necessary settings on the existing Layer 3 switch for BUS1. Now. n Procedures and Precaution for Adding a Vnet/IP Domain Follow these steps when you want to add a domain to a Vnet/IP network. l Case 1: When using existing Layer 3 switches (Layer 3 switches have unused ports) Firstly. In the Network Status Display dialog box on an HIS. 11. 9. 2. In the Network Status Display dialog box on an HIS. add stations by following the procedures in “■ Procedures and Precautions for Adding a Vnet/IP Station. check that both buses are normal. If the port on the Layer 3 switch is disabled. Procedures and Precautions for Adding a Station or Domain> 4-2 6. add stations for the new domain by following the procedures in “■ Procedures and Pre- cautions for Adding a Vnet/IP Station. carry out steps 1 to 5 as shown below to configure Layer 3 switches for BUS1 and BUS2. check that both buses are normal. Connect the additional Layer 2 switch for BUS2 and the existing Layer 2 switch for BUS2 with a cable. Turn on the power of the Layer 2 switch that you have added. Connect the existing station that you have disconnected at step 7 to the newly added Layer 2 switch for BUS2 with a cable. 3. 5. check that both buses are normal. 10. This completes the addition of Layer 2 switches. Make the necessary settings on the Layer 3 switch for BUS1 that you are going to add. add stations by following the procedures in “■ Procedures and Precautions for Adding a Vnet/IP Station. In the Network Status Display dialog box. 4. 2. enable the port. In the Network Status Display dialog box. The procedures for two cases are provided below.

In the Network Status Display dialog box. This completes the addition of Layer 3 switches. Connect the additional Layer 3 switch for BUS2 and an existing Layer 2 or Layer 3 switch for BUS2 with a cable.08. Now. 6.2014-00 . Procedures and Precautions for Adding a Station or Domain> 4-3 3. check that both buses are normal. Connect the additional Layer 3 switch for BUS1 to an existing Layer 2 or Layer 3 switch for BUS1 with a cable. <4.” IM 33K10A10-50E 5th Edition : Aug. check that both buses are normal. 5. Make the necessary settings on the Layer 3 switch for BUS2 that you are going to add. add stations for the new domain by following the procedures in “■ Procedures and Pre- cautions for Adding a Vnet/IP Station. 7. In the Network Status Display dialog box. 4.

Blank Page .

............................. 3-1 B V Bus Status ...................................2014-00 ....................... Ind-1 Vnet/IP IM 33K10A10-50E 5th Edition INDEX Time Synchronization ..........2-5 Vnet/IP Network .......................3-2 T Time Group............................................................................................08.............. 3-2 IM 33K10A10-50E 5th Edition : Aug........................... 1-1 S SNTP Server.........

Blank Page .

Apr.20 or later Preface Description of the caution symbol was modified.03.: IM 33K10A10-50E Aug. 2.00 or later 1. and deleted. Rev-1 Revision Information Title: Vnet/IP Manual No. modified. 2. 2. A figure was deleted. Jun. 2012/2nd Edition/R5.3 Descriptions on bus abnormality indications were modified. 2. The section "● Layer 2 Switch (L2SW)" was added. 2014/5th Edition/R5. Descriptions were modified.01 or later Newly published IM 33K10A10-50E 5th Edition : Aug. 1.03 or later Preface The preface text was modified. Descriptions were added. Jun.04 or Earlier" was deleted.2014-00 .02. The revised contents are valid until the next edition is issued. Preface Descriptions of grounding are modified.4 Descriptions were modified.08. Descriptions were added. 2. The “■ Printed by” was deleted.1 Descriptions were modified. Sep. Postface The "■ For Questions and More Information" was changed. The section "■ Connection with V net Domains of CENTUM CS 3000 R3.2 Descriptions were added. 2014/4th Edition/R5.04 or later* * : Denotes the release number of the Software Product corresponding to the contents of this Manual.4 Descriptions were modified. A figure and a table were modified. 2011/1st Edition/R5.1 Descriptions were deleted. 2. The section "■ Compatibility between Vnet/IP and V net" was deleted. 2013/3rd Edition/R5. 2.

yokogawa. JAPAN IM 33K10A10-50E 5th Edition : Aug.2014-00 . Rev-2 n For Questions and More Information Online Query: A query form is available from the following URL.com/dcs/ n Written by Yokogawa Electric Corporation n Published by Yokogawa Electric Corporation 2-9-32 Nakacho.08. Tokyo 180-8750. Musashino-shi. http://www.