1.

SYSTEM OVERVIEW

1. 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, it can
use commercially available Ethernet communication devices.

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

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.

YOKOGAWA TRAINING CENTRE

Page 1 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

System Components of Vnet/IP Network

The following describes the system components of a Vnet/IP network.
The typical system configuration is shown below.

Figure: System Components of Vnet/IP Network

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 and up to 124 other general-purpose Ethernet
communication devices (PCs, routers, etc.) can be connected.

Layer 3 Switch
A layer 3 switch is used to connect between Vnet/IP domains in each bus.

Router
A router with Security function to ensure the security of a Vnet/IP network is used to connect
the bus 2 side with an external network such as Intranet.

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.
Moreover, the safety control stations (Vnet/IP) of ProSafe-RS system can also be connected
on a Vnet/IP network.

YOKOGAWA TRAINING CENTRE

Page 2 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

Table: List of Vnet/IP Stations

•FFCS-L
This is a control station connected to Vnet/IP. The FFCS-L can connect up to 3 FIO type I/O
nodes as standard. In this case, the total number of nodes is 4 including an FCU.
Furthermore, by adding the Application Capacity Expansion Package, up to 15 I/O nodes can
be connected including an FCU. Only the FFCS-L can be connected to Vnet/IP as a control
station.

•General-Purpose PC + VI701 Card

A Vnet/IP station is connected to a Vnet/IP network by installing a VI701 card if a Vnet/IP
station uses a general-purpose PC as its platform. The VI701 card contains two ports of
connectors to connect Vnet/IP communication cables to support duplexed Vnet/IP buses.

•V net Router
The V net router is the hardware dedicated to connect a Vnet/IP domain and a V net/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/VL net.

Compatibility between Vnet/IP and V net

The upper protocol of the control communication of Vnet/IP is compatible with 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
HIS as its platform can connect to Vnet/IP by replacing the communication interface with a
Vnet/IP interface card (VI701).

Connecting Control Buses Prior to the CENTUM CS

Control buses prior to the CENTUM CS (HF bus, RL bus) cannot be connected directly to a
Vnet/IP domain. To connect these control buses to Vnet/IP, it must go through a bus
converter (BCV-H, BCV-L) of V net connected via a V net router.

Connecting General-Purpose Ethernet Devices

General-purpose Ethernet devices are connected to the bus 2 side of Vnet/IP.
To connect Vnet/IP with an external network such as an Intranet, separate the network using
a general-purpose router.

Use a hub to adjust the volume of communication to flow from a general-purpose Ethernet
device to a Vnet/IP network so that it will not exceed 300 Mbps (for example, up to three 100
Mbps ports).

YOKOGAWA TRAINING CENTRE

Page 3 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

1.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.
•Connection of devices in a Vnet/IP domain
•Connection between Vnet/IP domains
•Bus status of Vnet/IP
•Connection with other control bus domain

Outline of Vnet/IP Network Connections

An overview of Vnet/IP network connection in the CENTUM VP is shown below.

Figure: Outline of Network System Elements Connections

1.3. Connection of Devices in a Vnet/IP Domain

The devices in the Vnet/IP domain are connected in the star network using a layer 2 switch of
1 Gbps as the central device. Because duplexed Vnet/IP buses are separated as independent
subnets of each bus, it is necessary to install a layer 2 switch in each bus.

Multiple stations are connected to a 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 restarted by
momentary power failure, it takes several seconds for the communication with stations to
recover. 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

Specification when Connecting Devices in a Vnet/IP Domain

Do not connect in such a way that multiple communication paths exist between any stations.
Normal communication will not be performed.

YOKOGAWA TRAINING CENTRE

Page 4 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

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 router Max. 64 units
Other general-purpose Ethernet communication devices
(PCs, routers, etc.): Max. 124 units

Levels of layer 2 switches: Max. 7 levels

Max. 100 m
(when UTP is
Distance between layer 2 switch and station:
used)

Max. 5 km
(when optical
Connection distance between layer 2 switches:
fiber cable is
used)

It is possible to extend the distance between the layer 2 switches using the
optical fiber cable. It is also possible to use a connection faster than 1
Gbps

Figure: Connection Example of Devices in a Vnet/IP Domain

YOKOGAWA TRAINING CENTRE

Page 5 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

1.4. Connection between Vnet/IP Domains

A commercially available layer 3 switch is used to connect between Vnet/IP domains. Install a
layer 3 switch in each bus of duplexed Vnet/IP buses, and connect it to other domains. By
using a leased line as the transmission path between domains, broadband connection can be
achieved.

Specification when Connecting between Vnet/IP Domains

Do not connect in such a way that multiple communication paths exist between any two
domains. Normal communication will not be performed

The specification of connection between Vnet/IP domains is as follows:

•Multi-level connection of Vnet/IP domains: Max. 15 levels (16 layers)
•Transmission delay between any domains: 250 msec or less

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.

Figure: Domain Connection Types in Vnet/IP

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 FCS
messages, HIS messages and FCS TCP communication frames from another domain.
Note that the default settings of all domains are this type.

Hierarchical Connection
This connection type differentiates the upper and lower relationships between Vnet/IP
domains. This type of connection can be established by setting the lower domain not to
receive FCS messages, HIS messages and FCS TCP communication frames from the upper
domain; but the upper domain can receive them from the lower domain.

YOKOGAWA TRAINING CENTRE

Page 6 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

Bridge Connection
This connection type guarantees the independence of a domain. This type of connection can
be established by setting the domain not to receive FCS messages, HIS messages and FCS
TCP communication frames from another domain and by setting the time group to “0” so as
not to perform time synchronization.

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

1.5. 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. The
Vnet/IP bus status is reflected in the Network Status Display dialog box. If the bus
communication status changes, it is output on an HIS as a system alarm message.

Elements of the Vnet/IP Bus Status

In V net, the bus status shows the bus communication status in one domain. On the other
hand, in Vnet/IP, it shows the communication status of the stations in the entire Vnet/IP
network, i.e., in all connected domains as well as the devices (routers) connected between
domains. For example, when referencing the System Status Overview 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

Figure: Elements of Vnet/IP Bus Status

Displaying the Communication Status between Stations in a Domain

Each station in a Vnet/IP domain performs communication for the purpose of conducting
mutual bus diagnostics using bus 1 and bus 2. Based on this diagnostic information, each
station in a domain can display the communication statuses of all stations for each bus.
Each station holds the following four types of communication status:
•Communication status between control side (or single) stations
•Communication status between control side (or single) station and standby side station
•Communication status between standby side station and control side (or single) station
•Communication status between standby side stations

YOKOGAWA TRAINING CENTRE

Page 7 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

Bus Status in a Domain

The bus status in a domain is created from the communication status between stations in
each domain. If the bus status shows abnormality, its meaning varies with the type of failure:
•Single failure
The status of the bus generating communication abnormality due to failure is handled as
abnormal.
•Multiple failures
Not both buses are handled as abnormal; only the status of the bus in which abnormality is
detected first is handled as abnormal.

If both buses cannot communicate with a specific station, it is determined that the station itself
has failed, and the bus status will not be handled as abnormal

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. The communication statuses of devices
connected between domains are indicated by a two-dimensional table of all domains for each
bus. Also, by this communication between domains, the bus statuses of other domains are
notified to an HIS.

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 Connected between Domains
If the bus status of own domain is normal, the communication statuses of devices between
domains are reflected in the Vnet/IP bus status. In the case of a single failure, the status of
that bus is handled as abnormal. In the case of multiple failures, only the status of the bus in
which abnormality is detected first is handled as abnormal.
•Bus Statuses of Other Domains
If the communication statuses of all devices connected between 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.

YOKOGAWA TRAINING CENTRE

Page 8 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

1.6. 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, a V net router is used.

Connection between Vnet/IP and V net Domains

To connect a Vnet/IP network and V net domains, relay V net control communication using a
V net router. The engineering of a V net router must be done from the Vnet/IP side. Because
the connection form of a Vnet/IP network and V net domains is bi-directional, it is possible to
perform the operation and monitoring of the control stations of other domains.
When conducting engineering, it can be handled as one project in which Vnet/IP and V net
stations coexist. It is also possible to handle Vnet/IP and V net as separate projects, and
integrate multiple projects using the Multiple Project Connection function. Connect the
information bus (Ethernet connection between HISs) using bus 2 of Vnet/IP via a router.

Connection between Vnet/IP and VL net Domains

Similar to the connection with V net, connect a Vnet/IP network and VL net domains using a V
net router. In the case of VL net single, the VL net coupler of the V net router will be single.
The CENTUM CS 1000 does not require Ethernet as an information bus; however, it is
required when connecting to Vnet/IP. Connect the information bus to bus 2 of Vnet/IP via a
router.
Vnet/IP will be a CENTUM VP project, and VL net will be a CENTUM CS 1000 project. They
can be integrated using the Multiple Project Connection function. At that time, the project on
the Vnet/IP side will always be an upper project.

Figure: Connection with V net/VL net

YOKOGAWA TRAINING CENTRE

Page 9 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

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, it is necessary to
configure a network by connecting to a V net domain via a V net router, and further routing
through a bus converter (BCV-H, BCV-L).

Figure: Connection with Other Control Bus

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.

Restrictions on Multi-Level Connection of Control Buses

A station on Vnet/IP network can access a station on the other control bus, up to two levels of
bus converters beyond the V net router. Thus, 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.
The method to count the number of levels in multi-level connection of control buses is as
follows:
•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 bus converters that connect other control buses, as usual.

YOKOGAWA TRAINING CENTRE

Page 10 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

Figure: Connection with Other Control Bus

Replacing Communication Gateway Units (CGWs) for Wide Area Communication

By utilizing connection between Vnet/IP domains, existing communication gateway units
(CGWs) for wide area communication can be replaced with routers.

Similar to connection between regular Vnet/IP domains, the transmission delay between any
Vnet/IP domains must be less than 250 msec. Also, the communication band must be 100
Mbps or more

In V net wide area connection, HISs equipped with system builders for the engineering of
CGWs at the connection destination are required, and also Ethernet must be installed for
builder communication. However, by changing the upper network to a Vnet/IP network and
connecting it with V net in the lower network via V net routers, CGWs can be replaced with
the routers.

YOKOGAWA TRAINING CENTRE

Page 11 of 12

VPEG_R4_TB_Ed.1_October 2008
 1. SYSTEM OVERVIEW

Figure: Replacing CGWs

Connection with V net Domains of CENTUM CS 3000 R3.04 or Earlier

To connect with V net domains of CENTUM CS 3000 R3.04 or earlier, integrate them with
multiple projects in which Vnet/IP side projects are classified as upper projects.
To connect Vnet/IP domains with existing V net domains, the HIS function running in
CENTUM CS 3000 R3.04 or earlier has the following restrictions. However, the HIS function
on the Vnet/IP side has no restriction.
•The network type on the Vnet/IP side is displayed as “V net.”
•In the event of Vnet/IP bus status abnormality, a message indicating that control bus
communication failure in all domains of Vnet/IP is displayed.
•The running status of the control station FFCS-L (AFV10S/AFV10D) becomes the same as
the FFCS.
•The System Status Overview window of Vnet/IP domains calls up a window by window name
specification.

YOKOGAWA TRAINING CENTRE

Page 12 of 12

VPEG_R4_TB_Ed.1_October 2008