S1 System Overview

5/24/2018 S1 System Overview

1/31

YOKOGAWA TRAINING Section 1. CS3000 System Overview

SECTION 1

CS3000

SYSTEM OVERVIEW

CONTENTS

1 CS3000 HARDWARE CONFIGURATION__________________________ 1-2

1.1 Operating Environment of System Generation Function _______________ 1-2

1.2 HIS Human Interface Station____________________________________ 1-31.2.1 Hardware Operating Environment________________________________________ 1-31.2.2 V net Interface Card___________________________________________________ 1-4

1.3 Control Station Overview_________________________________________ 1-81.3.1 Configuration of PFCS ________________________________________________ 1-91.3.2 Configuration of Rack Mountable LFCS (CS3000) _________________________ 1-10

1.3.3 Configuration of a Rack Mountable FFCS ________________________________ 1-111.3.4 Configuration of Rack Mountable KFCS (CS3000) ___________________________ 1-12

1.4 LFCS - I/O CONFIGURATION __________________________________ 1-131.4.1 LFCS - The RIO Bus Network _________________________________________ 1-131.4.2 LFCS/PFCS - Types of I/O Module Nests ________________________________ 1-141.4.3 LFCS/PFCS - Combination of I/O Nests and I/O Modules____________________ 1-21

1.5 KFCS/FFCS - I/O CONFIGURATION ____________________________ 1-231.5.1 KFCS - The FIO Bus Network _________________________________________ 1-231.5.2 FFCS I/O Bus Network _____________________________________________ 1-251.5.3 KFCS/FFCS - Types of Nodes _________________________________________ 1-261.5.4 KFCS/FFCS FIO Modules ___________________________________________ 1-271.5.5 FIO Module Connection ______________________________________________ 1-29

1.6 Other Hardware _______________________________________________ 1-301.6.1 Bus Converter ______________________________________________________ 1-301.6.2 Optical Bus Repeaters ________________________________________________ 1-31

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-1


2/31


1 CS3000 HARDWARE CONFIGURATION

1.1 Operating Environment of System Generation Function

The CS 3000 system consists of the HIS (Human Interface Station) that handles the

operation and monitoring functions, the FCS (Field Control Station) that carries out

the control function, and control bus (V net) that connects those stations. The system

generation functions work in the HIS and general-purpose PCs.

Vnet - Speed: 10Mb/s- Type: Token Passing

Number of Stations per Domain = 64

Number of Domains = 16 (CS3000 only)

HIS 16 Maximum per Domain

FCS 48 Maximum per Domain

BCV 1,000 Tags per Second (approx.)

Figure 1.1 Basic Configuration

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-2


3/31


1.2 HIS Human Interface Station

1.2.1 Hardware Operating Environment

The CS3000 Operator Station and Engineering functions run on a standard PC under

Windows 2000. The requirements for the PC are listed below.

Main Memory, Hard Disk Capacity

Main memory and hard disk size required for the PC depends on the installed

packages as indicated in the table below.

Table 1.2 Required Main Memory Size

Table 1.3 Required Hard Disk Size

Software Environment:Windows 2000, Service Pack 1 or 2

See Installation Manual,

Section 3 for more details.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-3


4/31


1.2.2 V net Interface Card

V net interface card (VF701) is a communication card which is installed to a PC/AT-

compatible personal computer. The VF701 has two ports in order to support dual

communication. The operation and monitoring function by personal computer is

feasible by installing a VF701 to the PCI slot of a personal computer with the PCsoftware installed and by connecting a V net cable to the VF701.

1.2.2.1 Front panel of the V net interface card

RCV lamp

This lamp illuminates when the communication carrier is received from the V

net. It is turned off otherwise.

SND lamp

This lamp illuminates when the data is transmitted to the V net and is turned

off other-wise.

BNC connector

VL net and VF701 is connected here. It is necessary to connect a T-connector

to this BNC connector.

Figure 1.5 Front panel of the V net interface card

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-4


5/31


1.2.2.2 Setting the V net station address

The station address of a V net is defined by a combination of a domain number

and a station number. The DIP switches for setting the domain number and

station number are located on the printed circuit board of the VF701. (Refer to

the figure.)

Figure 1.6 Location of the DIP switches on the VF701

If necessary, change set the domain number and station number settings as

follows:

Figure 1.7 DIP switches for setting the station address

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-5


6/31


1.2.2.3 Setting the domain number

Set 1 to a single network system. Unless specified, the DIP switch is shipped

with all the bits OFF. Domain is a range of stations connected by single V net.

Set the domain number in the range of 1 to 16. Set the DIP switches as shown

in the following table to set the necessary domain number. Bit 2 and 3 of theDIP switches are always 0.

Switch Value

8

7

6

5

4

1

2

4

8

16

MSB: Most Significant Bit

LSB: Least Significant Bit

Figure 1.8 DIP switches for setting the domain number

Table 1.3 Domain numbers and the switch positions

Setting of the DIP switch

0: The switch is flipped to the right in the diagram above.1: The switch is flipped to the left in the diagram above.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-6


7/31


1.2.2.4 Setting the station number

Set the station number in the range of 1 to 64 (24 for CS1000). Set the DIP

switches as shown in the following table to set the necessary station number.

Switch Value8

7

6

5

4

3

2

1

2

4

8

16

32

64

MSB: Most Significant Bit

LSB: Least Significant Bit

Figure 1.9 DIP switches for setting the station number

Table 1.4 Station numbers and the switch positions

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-7


8/31


1.3 Control Station Overview

The hardware commonly used as field control stations in CENTUM CS 1000 and

CENTUM CS 3000 systems are the PFCS, LFCS and KFCS.

KFCS Distributed Field Control Station with fast remote I/O (FIO) FFCS Compact Field Control Station with FIO

PFCS Compact Field Control Station with local I/O.

LFCS Distributed Field Control Station with remote I/O (RIO)

These types are further divided into the following models:

AFG30S/D rack mountable field control station, FIO (KFCS)

AFG40S/D field control station with cabinet, FIO

AFF50S/D compact field control station (using FIO modules)

AFG7xS/D migration type field control station, RIO V, XL I/O

AFG8xS/D migration type field control station, FIO V, XL I/O

PFCS/D compact field control station, local I/O (using RIO modules)

AFG10S/D rack mountable field control station, RIO (LFCS)

AFG20S/D field control station with cabinet, RIO

(note: the AFS is similar to the AFG, but with the older style CPU)

All these field control station models are generically referred to as FCSs.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-8


9/31


1.3.1 Configuration of PFCS

The figure below shows the maximum configuration of a PFCS with an expansion

rack. The units composing a PFCS are listed in the table below the figure.

Figure1.10 Configuration of PFCS

Table1.5 Units Comprising PFCS

For more information, refer to

Instruction Manual 33Q6C20-01E,

Section A2.1

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-9


10/31


1.3.2 Configuration of Rack Mountable LFCS (CS3000)

The figure below shows the configuration of a rack mountable duplexed LFCS. For a

single CPU model, cards and units are installed in the right half of the nest. For the

units and cards composing an LFCS, see the table in Section 1.3.5.

Figure1.11 Configuration of Rack Mountable LFCS (CS3000)

Processor - AFS 25 MHz RISC processor

- AFG 133 MHz RISC processor



Section A2.2

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-10


11/31


1.3.3 Configuration of a Rack Mountable FFCS

The figure below shows a rack mountable duplexed compact FCS (FFCS). The I/O

cards that are plugged into this unit are the same as for the KFCS described below.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-11


12/31


1.3.4 Configuration of Rack Mountable KFCS (CS3000)

The figure below shows the configuration of a rack mountable duplexed KFCS. For a

single CPU model, cards and units are installed in the right half of the nest. For the

units and cards composing an KFCS, see the table in Section 1.3.5.

Figure1.11 Configuration of Rack Mountable KFCS (CS3000)

Processor - AFS 25 MHz RISC processor

- AFG 133 MHz RISC processor



Section A2.4

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-12


13/31


1.4 LFCS - I/O CONFIGURATION

1.4.1 LFCS - The RIO Bus Network

The Remote I/O Bus is a twisted pair communications bus used for transferring I/O

data between the nodes interface units (NIUs) and the FCS. This is required for the

LFCS only, as the I/O is integral to the PFCS.

Structure of the RIO bus network:

All I/O is installed in I/O Nests. These are installed in NIUs that

communicate on the RIO bus to the FCS. The system capacity is as follows:

NIUs: 8 per FCSNESTS: 5 per Node (see below for I/O limitations for each nest)

RIO Bus Specifications:

Type: Shielded Twisted Pair. Requested 750 Ohm terminator at each

end.

Length: 750m. Can be extended with repeaters.

Speed: 1 Mb/s

RIO Bus Function:

The RIO bus is controlled by the RB301 controller card in the FCS, and the

RB401 controller card in each node interface unit. The RB301 card scans the

bus every 18 msec, reading/writing 2 x 16 bit words from each nest of each

node every scan.Note:

1 Analog I/O = 1 Word

1 Digital I/O = 1 Bit

RIO Bus 1 Mbps

Figure 1.4.1 RIO Bus Network

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-13


14/31


1.4.2 LFCS/PFCS - Types of I/O Module Nests

There are eight types of I/O module nests, as the table below shows.

Table 1.8 I/O Module Nests

Models Model Names

AMN11 Nest for Analog I/O Modules

AMN12 (*1) High-Speed Nest for Analog I/O Modules

AMN21 Nest for Relay I/O Modules

AMN31 Nest for Terminal I/O Modules

AMN32 Nest for Connector I/O Modules

AMN33 Nest for Communication I/O Modules

AMN34 Nest for Multipoint Control Analog I/O Modules

AMN51 Nest for Communication I/O Cards

AMN52 Nest for PROFIBUS Communication ModulesAMN71(*2) Nest for Ethernet Communications Module

*1: Only applies to CS3000 LFCS

*2: Only applies to CS3000 PFCS

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-14


15/31


1.4.2.1 Model AMN11 Nest for Analog I/O Modules

The analog I/O module nest is a dedicated receptacle for multiple analog I/O

modules. One analog I/O module nest can accommodate up to 16 I/O

modules.

Figure 1.23 External View of Analog I/O Module Nest

Table List of I/O Modules Installable in Analog I/O Module Nest

Types Models NamesAAM10 Current/voltage input module (Simplified type)

AAM11 Current/voltage input module

Analog I/O modules AAM21 mV, thermocouple, RTS input module

APM11 Pulse input module

AAM50 Current output module

AAM51 Current/voltage output module

Wiring Details for Analog I/O Modules:

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-15


16/31


1.4.2.2 Model AMN21 Nest for Relay I/O Modules

Relay I/O modules are installed in relay I/O module nests. Either one of the

relay input module Model ADM15R or the relay output module Model

ADM55R can be installed in this nest.

Figure 1.24 External View of Relay I/O Module Nest

Table List of I/O Modules Installable in Relay I/O Module Nest

Types Models NamesRelay input module ADM15R Relay input module

Relay output module ADM55R Relay output module

Wiring diagram for Relay Inputs:

Wiring diagram for Relay Outputs

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-16


17/31


1.4.2.3 Model AMN31 Nest for Terminal I/O Modules

Multiplexer modules and digital I/O modules (terminal type) can be installed

in the terminal I/O module nest. Up to two I/O modules can be installed in the

nest. A combination of multiplexer modules and digital I/O modules, however,cannot be installed in the same nest.

Figure 1.25 External View of Terminal I/O Module Nest

Table List of I/O Modules Installable in Terminal I/O Module Nest

Types Models Names

AMM12T

Voltage input multiplexer module

Multiplexer module AMM22M mV input multiplexer module

AMM22T Thermocouple input multiplexer module

AMM22TJ Thermocouple input multiplexer module

AMM32T RTD input multiplexer module

AMM32TJ RTD input multiplexer module

AMM42T 2-wire transmitter input multiplexer module

AMM52T Current output multiplexer module

ADM11T Contact input module (16-point, terminal type)

Digital I/O module ADM12T Contact input module (32-point, terminal type)

ADM51T Contact output module (16-point, terminal type)

ADM52T Contact output module (32-point, terminal type)

See IM 33Y6K01-01E, Section 4.2.3

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-17


18/31


1.4.2.4 Model AMN32 Nest for Connector I/O Modules

Voltage Multiplexer (connector type) and Digital I/O modules (connector

type) can be installed in the connector I/O module nest. Up to 4 I/O modules

can be installed in one nest.

Figure 1.26 External View of Connector I/O Module Nest

Table List of I/O Modules Installable in Connector I/O Module Nest

Types Models NamesADM11C Contact input module (16-point, connector type)Digital I/O module ADM12C Contact input module (32-point, connector type)

ADM51C Contact output module (16-point, connector type)

ADM52C Contact output module (32-point, connector type)

AMM12C Voltage input Multiplexer module

Multiplexer module AMM22C mV input Multiplexer module

AMM25C Thermocouple input Multiplexer module

AMM32C RTD input Multiplexer module

AMM32CJ RTD input Multiplexer module

/Wiring for 32 Point Digital I O

Wiring for 16 Point Digital I/O

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-18


19/31


1.4.2.5 Model AMN33 Nest for Communication Modules

Communication modules are installed in the communication module nest. Up

to two modules can be installed in one nest.

Figure 1.27 External View of Communication Module Nest

Table List of I/O Modules Installable in Communication Module Nest

Type Model NameACM11 RS-232C Communication module

Communication module ACM12 RS-422/RS-485 Communication module

ACF11 Fieldbus Communication Module

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-19


20/31


1.4.2.6 Model AMN34 Nest for Multipoint Control Analog I/O Modules

Multipoint control analog I/O modules are installed in the nest for multipoint control

analog I/O modules. Up to two modules can be installed in one nest.

Figure 1.28 External View of Nest for Multipoint Control Analog I/O Module

Table List of I/O Modules Installable in Multipoint Control Analog I/O Module Nest

Type Model NameMultipoint control analog I/O Module Multipoint control analog I/O Module AMC80

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-20


21/31


1.4.3 LFCS/PFCS - Combination of I/O Nests and I/O Modules

The different types of I/O modules may be installed in different I/O module nests. The

varies combinations are possible. The allowed combinations are listed in the

following table.

Table 1.9 List of Combinations and Max. No. Installable of I/O Module Nests and I/O Modules

(1)

*1: The multiplexer module and the digital I/O module cannot be installed in thesame I/O module nest.*2: PFCS/SFCS These modules can be installed in Slot 1 or 3 only. Other IOMscannot be installed in Slot 2 0r 4. These modules and AMM12C can be installed in

the same AMN32 Nest for Connector I/O Modules.*3: PFCS/SFCS This module can be combined with AMM12T, AMM22M orAMM22T in the same AMN32. Up to two AMM12C modules can be installed.*4: PFCS/SFCS This module can be installed in the PFCS or SFCS Field ControlStation.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-21


22/31


Table 1.10 List of Combinations and Max. No. Installable of I/O Module Nests and I/O Modules(2)

*1: The multiplexer module and the digital I/O module cannot be installed in the same I/O module

nest.*5: LFCS Only 1 module (Slot 1) can be installed when the operation mode of Model ADM52T is in

time proportioning ON/OFF (see table below).*6: LFCS Installation restrictions during operation mode are as shown in the table below (no modules

can be installed in Slots marked with N/A) Only 2 modules can be installed in Slots 1 and 3 when theoperation mode of ADM51C is in time proportioning ON/OFF.

However, when installing one module, a general connector type ADM can be installed in Slots 3 and 4.Only 2 modules can be installed in Slots 1 and 3 when the operation mode of ADM52C is in pulse

width output. However, when installing one module, a general connector type ADM can be installed inSlots 3 and 4. Only 1 slot can be installed when the operation mode of ADM52C is in timeproportioning ON/OFF.

*7: PFCS/SFCS May be installed in PFCS/SFCS.*8: PFCS/SFCS May be installed in PFCS/SFCS.

Model ACF11 and model ACM11 or ACM12 cannot be installed in the same AMN33 Nest forCommunication Modules.

Model ACM11 and ACM12 can be installed in the same AMN33.

Table Restrictions on Installation for Different Operation Mode

For detailed information

regarding I/O modules, refer

to Instruction Manual

33Y6K01-01E Section 3 & 4.

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-22


23/31


1.5 KFCS/FFCS - I/O CONFIGURATION

1.5.1 KFCS - The FIO Bus Network

The Fast I/O Bus comprises the ESB local bus and the ER remote bus and is a high

speed communications bus used for transferring I/O data between the node interface

units (Nodes) and the FCS.

Structure of the FIO bus network:

All I/O is installed in I/O Nests. These are installed in Nodes that

communicate on the ESB bus to the FCS. The system capacity is as follows:

Nodes: 10 per FCSSlots: 8 per Node (see below for I/O limitations for each nest)

ESB Bus Specifications:

Type: Parallel bus connection with internal terminators

Length: 10m, non-extendable.

Speed: 125 Mb/s

ER Bus Specifications:

Type: Co-ax, ethernet

Length: 128m (thin co-ax)/500m (thick co-ax), extendable with fibre-

optic repeaters.

Speed: 10 Mb/s

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-23


24/31


FIO Bus Configuration

The ESB is a high speed parallel local bus on which the Nodes reside. The ER

bus is a co-ax ethernet bus for long distance communications, and is connected

to the ESB via an ethernet card in a Node. The total of 10 Nodes applies to all

Nodes connected to the ESB and ER busses.

Figure 1.5.1 FIO Bus Network

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-24


25/31


1.5.2 FFCS I/O Bus Network

The FFCS is expandable to 3 extra nodes which can be connected using the ESB bus

or the remote ER bus. The specifications for these busses are the same as for the

KFCS bus. The following schematic shows how they can be configured:

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-25


26/31


1.5.3 KFCS/FFCS - Types of Nodes

There are two types of nodes, local and remote. The only difference between them is

the bus card that is plugged into them.

Figure 1.5.2 Node Layout

Figure 1.5.3 Physical Hardware Schematic

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-26


27/31


1.5.4 KFCS/FFCS FIO Modules

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-27


28/31



Instruction Manual 33Y06K01-01E,

Section B2

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-28


29/31


1.5.5 FIO Module Connection

Figure 1.5.4 Analog Module Connection Blocks

Figure 1.5.5 Digital Module Connection Blocks

Figure 1.5.5 Communication Module Connection Blocks

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-29


30/31


1.6 Other Hardware

1.6.1 Bus Converter

A Bus Converter allows a connection between two control buses, for example, two V

Net buses or V Net to RL Bus (uXL). It manages the flow of data between them be

means of a taglist resident within the bus converter.

On a plant, the V Net may be separated into 2 or more domain for several reasons:

1. The number of tags or stations in the system exceeds the capacity of the

DCS, requiring that it be split between several domains.

2. Isolation between separate areas of plant is required.

3. Two areas of identical plant with identical tagnames can be separated.

The bus converter provides a connection between two domains, and allows tag data tobe transferred between the two systems in a managed way. Thus data in one domain

can be monitored by a HIS in another domain.

Figure 1.29 Bus Converter Configuration

Specifications:

Dual redundancy: Processors

Power Supplies

V Net Connections

Capacity: 1000 Tags per second (approx.)

__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-30


31/31


__________________________________________________________________________________

TE 33AU1C3-01 Rev. 3.2 1-31

1.6.2 Optical Bus Repeaters

The optical bus repeater is designed to extend the communication bus (VL net, V net

and RIO bus) of the CS 1000 system or CS 3000 system. The use of optical bus

repeaters makes it possible to transmit through optical fiber cables over a long

distance. Being free of the effects of external noise and ground potential differences, itis suitable for outdoor transmission.

The repeater is available in four different models according to the transmission

distance and configuration:

YNT511S Single-configuration optical bus repeater (for 4 km, max.)

YNT511D Dual-redundant configuration optical bus repeater (for 4 km, max.)

YNT521S Single-configuration optical bus repeater (for 15 km, max.)

YNT521D Dual-redundant configuration optical bus repeater (for 15 km,

max.)

Figure 1.30 Configuration of Optical Bus Repeater

S1 System Overview

Documents

Transcript of S1 System Overview