CS3000 R3

Engineering Course
Day 1

Yokogawa Engineering Asia

Singapore Training Centre

Introduction
Instructor: Ivan Choo
Email:
Ivan.Choo@sg.yokogawa.com
Lesson:
9:00am ~ 4:30pm
Tea Break:
10:00 ~ 10:15am
2:45 ~ 3:00pm
Lunch:
11:45am ~ 1:00pm
Page.2

Table of Contents
Day 1
1.
2.
3.
4.

CS 3000 System Overview

Project Creation
Projects Attribution Utility
Project Common Definition

Laboratory: Project Creation, Attribution Utility,

Common Definition
Page.3

Table of Contents

1.
2.
3.
4.
5.

Day 2
FCS Configuration
I/O Module Configuration
Software Switches Configuration
Message Definition
Control Drawing Builder

Laboratory: Process I/O Definition, Switches Configuration,

Message Definition
Page.4

Table of Contents
Day 3
1. Regulatory Control
2. Sequence Control

Laboratory: Creation of Regulatory Control Function,

Creation of Sequence Control Function
Page.5

Table of Contents
Day 4
1. HIS Configuration
2. Windows Configuration

Laboratory: HIS Configuration and Windows Configuration

Page.6

Table of Contents
Day 5
1. Graphic Builder

Laboratory: Graphics Generation

Page.7

Centum CS 3000 System

Overview

HIS
Human Interface
Station

FCS
Field Control
Station

Process I/Os

HIS is mainly used for operation

and monitoring:
1. Desktop
2. Console :
Enclosed Display
Open Display

ENG: The PC with

engineering functions used
to perform CENTUM CS
3000 system generation and
maintenance management.

FCS performs process control,

and manages communication
with subsystems such as
PLCs.
Transmitters, Valves, etc

FIO : Fieldnetwork
RIO : Remote I/O
Refer to Page A-1 & A-2
Page.8

System Specifications
System

CS 1000

CS 3000

Max. no. of monitoring tags 8000

100 000

Max. no. of stations

24

256

Max. no. of domains

16

Max. no. of stations per

domain

HIS (8)
FCS (16)

64 (HIS (16) , FCS, BCV,

CGW)

Refer to Page A-22

Page.9

Network
Network

Vnet

VL Net

Transmission Speed

10 Mbps (real-time control bus)

10 Mbps (real time control bus)

Cable Types

10 Base 2 (for HIS)

10 Base 5 (for FCS, CGW, etc)

10 Base 2 cable ( for stations)

Transmission distance

185 m/segment (for 10 Base 2)

500 m/segment (for 10 Base 5)

185 m/segment (for 10 Base 2)

Access Method

Token Passing

Token Passing

Repeater - Coaxial Cable

- Optical Fiber

Max. 1.6 km, 8 repeaters

Max. 20 km, 4 repeaters

Max. 1.6 km, 8 repeaters

Max. 20 km, 4 repeaters

Token Passing is a technique in which only that system can communicate that has token. Token is
a sort of control mechanism that gives authority to the system to communicate or use the resources
of that network. Once the communication is over, the token is passed to next candidate in a
sequential manner.

Page A-20
Page.10

Domain
Domain: A group of stations
linked by V net cables. When the
no of stations reaches a
maximum of 64 in a domain, a
new domain has to be started.
Bus Converter:
i) Link two domains
ii)
Link CENTUM CS 3000 system
to previous systems (CENTUM
CS, CENTUM XL, CENTUM V,
CENTUM CS 1000 & XL)
Communications Gateway:
This links the V net to the
Ethernet (to a supervisory PC).
By CGW wide area
communication function, two
CENTUM CS3000 V nets can
be linked in different places
using a dedicated telephone line.
Page A-23
Page.11

Field Control Stations

KFCS

Extended Serial
Backboard bus

Remote
I/O Bus

LFCS

Enhanced
Remote bus

PFCS

FFCS

CENTUM CS3000
Integrated Production
Control System
System Overview
Page 2-10
Page.12

Standard Field Control Station

for FIOs (KFCS)
Max no. of
nodes: 10
5 nodes

5 nodes

Refer to Page A-7

Page.13

Standard Field Control Station

for RIOs (LFCS)
Max. no.
of nodes: 8

3 nodes

3 nodes

Another 2 nodes
installed in another
cabinet, if required
Refer to page A-6
Page.14

Standard Field Control Station

(KFCS)

Refer to Page A-7

Page.15

Standard Field Control Station

(LFCS)

Refer to Page A-6

Page.16

Compact Field Control Station

for FIOs (FFCS)

Page.17

Compact type FCS (PFCS/SFCS)

Page A-8
Page.18

Setting Domain Number:

LFCS/KFCS
To set domain number from 1 to 16
Total no. of 1s from bit 4 to bit 8 is odd => Bit 1 = 0
Total no. of 1s from bit 4 to bit 8 is even => Bit 1 = 1
0

1
0
0
0
0
1
1
0

1
2
3
4
5
6
7
8

2 2
4 +2=6
Total no. of 1s from bit 4
to bit 8 is even.
Page.19

Page A-16

Setting Station Number:

LFCS/KFCS
To set station number from 1 to 64
Total no. of 1s from bit 2 to bit 8 is odd => Bit 1 = 0
Total no. of 1s from bit 2 to bit 8 is even => Bit 1 = 1
0

1
0
0
1
0
0
0
1

1
2
3
4
5
6
7
8

24
16

1
20

Total no. of 1s from bit

2 to bit 8 is even.
Page.20

1 = 17
Page A-17

Dual-Redundant Architecture of
FCU: KFCS
Results do not match, collator declares
Right unit
in control

CPU1 & CPU2

perform same
control
computation
Collator checks
computational
results from
both CPUs
Results match,
collator sends
data to main
memory & ESB
bus interface
ErrorCorrecting
Code repairs
transient bit
inversion errors

computational error, control right

transferred to left unit
Standby unit performs the same computation
as control unit, has the capability to take over
the control immediately
Error unit performs self-diagnostics, no
CPU error implies transient computational
error, unit goes to standby state
Standby unit performs same control
computation concurrently with control unit;
it can take over the control at any point of
time without interruption, even for a very
short time
LFCS same as above except that ESB
Bus Interface (SB301) is replaced by
RIO Bus Interface(RB301).

Page A-11
Page.21

Dual-Redundant Architecture of
FCU: SFCS
Same principle as in KFCS
WDT (Watch Dog Timer) in the processor unit
supervises the execution of control transferring, in
the event of an abnormality in the processor in
control.
The PI/O bus interface has the function to run the
PI/O executions on control side and to diagnose
the PI/O performance by itself. The same
diagnostic function is also running in standby
side PI/O bus interface.
When an abnormality occurs in the control side
PI/O bus, the control right is immediately
switched to the standby side PI/O, thus the PI/O
executions may be continued.
PFCS same as above except that Vnet Interface is replaced by VL Net Interface.
Page A-12
Page.22

Dual-Redundant Architecture of
FCU: FFCS
Same principle as in KFCS
If an abnormality is detected in the selfdiagnostics of the I/O controller inside
the controlling processor module, the
control right is transferred to the standby
processor module.
Inside the processor modules, faults of
the SB buses are diagnosed by accessing
each others processor module via the SB
buses between duplexed processor
modules.
If all local nodes are abnormal, it is
assumed as an ESB bus failure.

Page.23

Test Function
The Test Function is a group of tools (option packages) for efficiently debugging
FCS software created by the user.
The Test Functions allow combinations of monitoring/operation and control functions
to be tested before being put into operation. There are two types of test functions:
. Virtual tests
Two types
of tests
:
. Target
tests

Test Function

Virtual test
Target test

I/O disconnection (Use virtual I/O)

Use real I/O

Page B-1
Page.24

Test Function Virtual Test

Virtual Test
Virtual test uses an FCS simulator instead of an actual FCS. The FCS simulator
simulates the functions and operation of the FCS and runs under an HIS.

Page B-1
Page.25

Test Function Target Test

Target Test
Target test uses an actual FCS. When there are no I/O modules and I/O test
devices, an FCS input and output can be simulated by using the I/O Disconnect
and Wiring Functions.

Page B-2
Page.26

Concurrent Engineering
Using Windows File sharing, several people can share an Engineering
database on a network; concurrent engineering is possible.

Page B-2
Page.27

Virtual Test Function

Start Virtual Test Function by :
Start Programs YOKOGAWA CENTUM System View

Page.28

Virtual Test Function

Page.29

After Virtual Test Function

Page.30

Project
A project is a unit that manages the engineering database of the FCS and the HIS created by the user.

PageC-2
Page.31

Steps to Project Creation

Page C-3
Page.32

Steps to Project Creation

LFCS

The default location

in which to store the
project .

KFCS

Page C-4 ~ Page C-5

Page.33

After Project Creation

Page.34

Projects Attribute

Page C-6
Page.35

Projects Attribute

Page C-6
Page.36

Projects Attribute

Page C-6
Page.37

Registering a Project

Select project

Select project attribute

Page.38

Projects Attribute - Differences

Default

Current

Userdefined

Created the first time when

the System View starts

Yes

Virtual test with the FCS

simulator.

Yes

Yes but target

test

Yes

Yes but off

line

Yes but on line

No

Can be downloaded to HIS.

Yes

Yes

No

Multiple projects can be

created in System View.

No

No

Yes

Can be downloaded to the FCS

of the target system

When any one of the FCSs created in default project is successfully

downloaded, the attribute changes to a current project.

Page C-1
Page.39

Project Common

User defined

Page.40

Alarm Priority

Designate in the Alarm Priority Builder whether

or not the status change is to be displayed
in a window upon occurrence of the alarm or
upon recovery of the system.

Designate in the Alarm Priority Builder whether or

not the status change is to be printed out
to a printer upon occurrence of the alarm or upon
recovery of the system.

Designate in the Alarm Priority Builder whether or not the status change is to be logged in a
historical message save file upon occurrence of the alarm or upon recovery of the system.
A message logged in a historical message save file can be displayed in a Historical Message
Report window.

Page.41

Alarm Priority

Page.42

Alarm Priority

Page.43

Alarm Processing Table

Alarm status bit 1 6
not displayed, system
fixed

Alarm processing
levels 1- 4 system
fixed, 5 16 User
defined

e.g. NR is assigned
with green for
alarm processing
levels 1-4

Page.44

System-fixed Status Character

String

The alarm status character strings that are

output upon occurrence of the alarm are
available for each type of function block. The
character string can be confirmed with the
system fixed status character string viewer.

Page D-9 & D-10

Page D-9 & D-10
Page.45

System-fixed Status Character

String/ Alarm Processing Table/ Alarm
Priority

Page D-9 & D-10

Page.46

Project Common

Page.47

Engineering Unit
Up to 256 engineering unit symbols can be used for one project.

One engineering unit symbol can be defined with up to six alphanumeric

characters and it is case-sensitive
Nos.1 to 8 cannot be changed or deleted. Default values are predefined
for Nos.9 to 126.
Page D-7
Page.48

Switch Position Label

Up to 64 switch position labels can be used for one project.
Switch position labels Nos.1 and 2 cannot be changed or deleted.
Default values are predefined for Nos.3 to 13.

Page D-8
Page.49

Project Common

Page.50

Operation Mark
Attaching operation mark may temporarily change the write access right on the block during plant
operation. There are 64 operation marks available for configuration.
8 characters can
be entered as the
text on the label
(string)

Page D-5 ~ D-6

Page.51

Station Configuration
Overview of the station configured for the project.

Page D-1
Page.52

Project Common

Page.53

User Security

Valid User:
User Name
Set Automatic User Out Time
Comment
User Group
Automatic User Out Time [Hour]
Privilege Levels Automatic User Out Time [Minute]

Page D-2 ~ Page D-4

Page.54

User Name
Each user name must be unique, consisting of eight alphanumeric characters or fewer and is
not case-sensitive.
Up to 250 users can be defined for CS 3000 system.

Page D-2
Page.55

User Group
The users are classified into groups based on their operation and monitoring authorities. Each group is
called user group.
Each user group name must be unique and in 8 or less alphanumeric characters. 50 user groups may be
assigned to one project for CS 3000.

Page D-3
Page.56

Set Automatic User Out Time

Range of 0 hour 1 minute to 24 hours 0 minute

Range of 1 to 59 minutes

User may be automatically user-out under the following optional conditions:

Automatically User-Out Due to No Operation Timeout
If the keyboard or the mouse has not been touched for a designated time period, the user is
automatically user-out.
A Certain Time Elapsed since User-In
User may be automatically user-out after a certain time elapsed since the user-in.
By default, Automatic User-Out is not activated. OFFUSER is not subject to Automatic User-Out.

Page.57

User Group

Monitoring Range

Operation and Monitoring Range

Window Range

Acknowledgment

Process Message Receiving

System Alarm Receiving

Exclude Operation

Exclude Operation and Monitoring

Exclude Acknowledgment

Exclude Process Message

Exclude System Alarm

Comment

Specify a plant hierarchy

name/ station name.

When setting operation and monitoring rights on designated station names or window names, the wild
card character * can be used instead of part or all characters in a character string.
Page.58

END

END
OF
PRESENTATION
Page.59

User-defined Status Character

The function blocks that can use the alarm status
String

character strings designated here are faceplate blocks,

SFC blocks, and unit instruments. There is a table
reserved for each of these function blocks, used for
designating the alarm status character strings. The
figure below shows the relationship between the
alarm status character string and the bit position
(default) for each function block:

Page.60