Amb Training Yokogawa PDF

TRAINING CENTRE
(SINGAPORE)
STUDENT TRAINING TEXTBOOK
Name :
Company :
Course Period :
Document No: CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

Document No: CKEG_R3_Vnet/IP_TB Ed. 3 September 2007
COURSE : CS 1000 & CS 3000 ENGINEERING (Vnet/IP)
NAME OF COURSE MATERIAL USED : CS 1000 & CS 3000 ENGINEERING (Vnet/IP)
Edition Date Revised Item Rev. No.* Author

0 September 2001 - R3.01 Jessie Chong
1 December 2004 Contents (Page 1) R3.04 Jessie Chong
Add F3, FFCS (Page 1-10)
2 March 2006 Revised Materials to Vnet/IP R3.06 Jessie Chong
3 September 2007 Revision R3.07 Ivan Choo
This document is maintained by : Wendy Kok Initial: Wendy Kok Date: September 2007
Note: Instruction Manual is updated/controlled by YHQ.

* - Denotes the release no. of the software corresponding to the contents of this instruction
manual. The revised contents are valid until the next edition is issued.
WELCOME TO YOKOGAWA TRAINING CENTRE

Yokogawa Training Centre in Singapore commenced operation in 1986. For the past
years, we have been actively involved in training customers in area of
instrumentation and control. To date, we have trained a total of more than 10,000
participants from over 480 organisations based in Asia, Middle East, Africa, Europe
and America.
We welcome you to attend this course and trust that you will benefit from the training
session. Feel free to approach the staff or instructors should you need any
assistance.
The following information may be helpful to you during this course period.
General Information
Address : 5 Bedok South Road, Singapore 469270
Telephone No.: 62493654
Fax No. : 62419537
Schedule
Session : 0900 – 1630
Tea break : 1000 – 1015

1445 – 1500
Lunch : 1130 – 1245
General Rules & Regulation

• Be punctual for all sessions.
• Avoid entering restricted premises – Factory Acceptance Test area & staff offices
• Smoking is strictly confined to smoking areas only.
• No consumption of beverages and food in the classroom to ensure cleanliness of
the training environment.
Others
Trainees can bring along a jacket to keep themselves warm as the training
environment may be cold.
YOKOGAWA SINGAPORE TRAINING CENTRE
CKEG_R3_Vnet/IP_TB Ed. 3 September 2007


COURSE OUTLIINE
COURSE OUTLINE
OBJECTIVE : This course enables participants to learn to perform
generation of CENTUM CS 1000/3000 regulatory control
functions, sequence control functions and Human Interface
Station.
DURATION : 5 days
PARTICIPANTS : For engineers involved in software generation or modification

on the CENTUM CS 1000/3000 system.
PREREQUISITE : Participants should have attended CENTUM CS 1000/3000

Operation course.
COURSE CONTENTS :
DAY 1
Centum CS 1000/3000 system specification
Project creation and attribute utility
Project common definition
DAY 2
FCS configuration
I/O module configuration
Software switches configuration
Message definition
Control drawing builder
DAY 3
Regulatory Control Function Definition
Sequence Control Function Definition
DAY 4
HIS configuration
Windows configuration
DAY 5
Graphics builder

COURSE OUTLIINE

TABLE OF CONTENTS
TABLE OF CONTENTS
A. SYSTEM OVERVIEW A1
A1. System Components A1
A1.1 Types of HIS A3
A1.2 Types of FCS A5
A2. FCS Hardware Description A15
A3. Network A20
A4. System Specifications A22
A5. Hardware Configuration A25
A6. System Components of Vnet/IP Network A27
A7. Field Control Station [Vnet/IP] A30
A7.1 FFCS-L Hardware Description A31
A8. Transmission Path Specification [VnetIP] A32
A9. Questions A33
A10. Exercises A33
B. ENGINEERING ENVIRONMENT B1
B1. Test Function B1
B1.1 Virtual Test B1
B1.2 Target Test B2
B2. Concurrent Engineering B3
B3. Engineering Work Flow B4
B4. Questions B5
C. PROJECT CREATION C1
C1. Types of Project C1
C2. Creating a Default Project C2
C3. Project Attribute Utility C6
C3.1 Start Project Attribute Utility C6
C3.2 Start Project Attribute Utility C8
C3.3 Changing the Attribute of a Project C9
C3.4 Deleting a Project C10
C4. Questions C11
C5. Exercise C12
YOKOGAWA SINGAPORE TRAINING CENTRE Page 1 of 15

TABLE OF CONTENTS
D. PROJECT COMMON ITEMS D1

D1. Alarm Builder D1
D1.1 System-Fixed Alarm Status Character String D3
D1.2 User-Defined Alarm Status Character String D4
D1.3 Alarm Processing D5
D1.4 Alarm Priority D6 D2.
Plant Hierarchy Builder D10
D3. Engineering Unit Symbol Builder D12
D4. Switch Position Label Builder D13
D5. Multiple Projects Connection Builder D15
D6. Operation Mark Builder D17
D7. Station Configuration Viewer D20
D8. Status Change Command Character String Builder D21
D9. Security Builder D22
D9.1 User Definition D22
D9.2 Advanced Security Settings D25
D9.3 Security Level D31
D10. Exercise D36
E1. FIO SYSTEM OVERVIEW E1-1

E1.1 ESB and ER Bus E1-3
E1.2 System Configuration E1-4
E1.3 Network Specifications E1-5
E2. FIO SYSTEM OVERVIEW (Vnet/IP) E2-1

E2.1 Network Specifications E2-2
E2.2 Connection With Other Control Bus Domains E2-3
E2.2.1 Connection Between Vnet/IP and Vnet Domains E2-3
E2.2.2 Connection Between Vnet/IP and VLnet Domains E2-3
E2.2.3 Connection with HF Bus/RL Bus Domains E2-4
E2.2.4 Connection with Vnet Domains of Revisions R3.04 E2-4
or Earlier

TABLE OF CONTENTS
F1. LFCS CONFIGURATION F1-1

F1.1 LFCS Property - Constant F1-1
F1.1.1 Fast Scan/Medium-Speed Scan Period F1-1
F1.1.2 Pulse Width and Serial Startup Interval for F1-2
MC Instrument Block
F1.1.3 MLD-SW Block AUT/CAS F1-2
F1.1.4 SEBOL Statement F1-2
F1.1.5 User-Defined block F1-3
F1.1.6 IOM Online Updating F1-3
F1.1.7 Options F1-3
F1.1.8 PID Pulse Width Output F1-4
F1.1.9 PI-HLD Action after Hold F1-4
F1.1.10 Sequence Table Algorithm F1-4
F1.1.11 dPV/dCPV Output from SUB Becomes F1-5
Zero Right After IOP
F1.112 Accept Batch-End during EMST F1-6
F1.2 LFCS Property - Constant 2 F1-9
F1.2.1 SS-DUAL PV Update during Deviation F1-9
Alarm
F1.2.2 Alarm Notify Action when All AOF Released F1-10
F1.2.3 Specify Reference Station for Tag List F1-10
F1.2.4 Annunciator Message with Data F1-10
F1.2.5 Increase Number of System Common F1-11
Switches
F1.2.6 Preset MV Valid Immediately F1-11
F1.3 LFCS Property – State Transition F1-12
F1.3.1 State Transition Matrix F1-12
F1.4 LFCS Property – Line 1 F1-13
F1.4.1 Make RIO Bus Dual Redundant F1-13
F1.4.2 Repeater Connection F1-13
F1.5 LFCS Property - Network F1-14
F1.5.1 VLnet TCP/IP Settings, Vnet TCP/IP F1-15
Settings
F1.6 LFCS Station Definition F1-15
F1.6.1 Definitions F1-15
F1.6.2 Scan Transmission F1-19
F1.6.3 Detailed Settings F1-20

TABLE OF CONTENTS
F2. KFCS CONFIGURATION F2-1

F2.1 KFCS Property - Constant F2-1
F2.1.1 Fast Scan/Medium-Speed Scan Period F2-1
F2.1.2 Pulse Width and Serial Startup Interval F2-2
for MC Instrument Block
F2.1.3 MLD-SW Block AUT/CAS F2-2
F2.1.4 SEBOL Statement F2-2
F2.1.5 User-Defined block F2-3
F2.1.6 IOM Online Updating F2-3
F2.1.7 Options F2-3
F2.1.8 PID Pulse Width Output F2-4
F2.1.9 PI-HLD Action after Hold F2-4
F2.1.10 Sequence Table Algorithm F2-4
F2.1.11 dPV/dCPV Output from SUB Becomes Zero F2-5
Right After IOP
F2.1.12 Accept Batch-End during EMST F2-6
F2.2 KFCS Property – Constant 2 F2-9
F2.2.1 SS-DUAL PV Update during Deviation Alarm F2-9
F2.2.2 Alarm Notify Action when All AOF Released F2-10
F2.2.3 Specify Reference Station for Tag List F2-10
F2.2.4 Annunciator Message with Data F2-10
F2.2.5 Increase Number of System Common Switches F2-11
F2.2.6 Preset MV Valid Immediately F2-11
F2.3 KFCS Property – State Transition F2-12
F2.3.1 State Transition Matrix F2-12
F2.4 KFCS Property – KFCS Property – Line 1 F2-13
F2.4.1 Make I/O Bus Dual Redundant F2-13
F2.4.2 Interface Card Type F2-13
F2.5 KFCS Property - Network F2-14
F2.5.1 VLnet TCP/IP Settings, Vnet TCP/IP Settings F2-15
F2.6 KFCS Station Definition F2-15
F2.6.1 Definitions F2-15
F2.6.2 Scan Transmission F2-19
F2.6.3 Detailed Settings F2-20
F3. Field Control Unit for FIO (Rack Mountable) F3-1

- FFCS (FFCS Compact FCS)
F3.1 Configuraton of Field Control Unit F3-2
F3.2 Duplexed Structure of the FFCD F3-3
F3.3 Create a New FFCS F3-7
F3.4 Input/Output F3-8
F3.4.1 Creating a New Node: FFCS F3-9
F3.4.2 Creating a New I/O Module: FFCS F3-10

TABLE OF CONTENTS
F4. Field Control Unit for Vnet/IP for FIO F4-1

(19” Rack Mountable) – FFCS-L
F4.1 Configuraton of Field Control Unit F4-2
F4.2 Hardware Configuration of FFCS-L F4-3
F4.3 Create a new FFCS-L F4-4
F4.4 Input/Output F4-5
F4.4.1 Creating a New Node: FFCS-L F4-6
F4.4.2 Creating a New I/O Module: FFCS-L F4-7
G1. INPUT/OUTPUT FUNCTIONS(LFCS) G1-1

G1.1 FCS Input and Output Interfaces G1-1
G1.2 Process Input/Output G1-2
G1.2A Creating a New Node: LFCS G1-2
G1.2.1 Type Tab – Node Number G1-3
G1.2.2 Dual Redundant Power Supply G1-3
G1.2.3 HKU Set G1-3
G1.2.4 Installation Pattern G1-3
G1.2.5 Component Number G1-3
G1.2.6 Node Comment G1-3
G1.2.7 Unit Tab – Start Mode G1-3
G1.2.8 High Speed Read G1-3
G1.3 Creating a New I/O Module : LFCS G1-4
G1.3.1 IOM Type G1-5
G1.3.2 Installation Position G1-7
G1.3.3 Duplicate Next Card G1-8
G1.3.5 IOM Comment G1-8
G1.4 IOM Builder G1-9
G1.4A Analog I/O Module Nest (AMN11) Configuration G1-9
G1.4.1 Terminal G1-9
G1.4.2 Signal G1-10
G1.4.3 Conversion G1-10
G1.4.4 Service Comment G1-11
G1.4.5 Low Limit/High Limit G1-11
G1.4.6 Unit G1-11
G1.4.7 Set Details G1-12
G1.4.8 Dual G1-12
G1.4.9 P&ID Tag Name G1-13
G1.4.10 Label (User-defined label) G1-13
G1.4B Detailed Setting of Analog I/O Module G1-13
G1.4.1 Detect IOP G1-14
G1.4.2 IOP Detection Level G1-14
G1.4.3 Square Root G1-15
G1.4.4 OOP Clear G1-15
G1.4.5 Detect OOP G1-15
G1.4.6 Fallback, Maintain Current Value G1-16
G1.4.7 Pulse Input G1-16
G1.4.8 Resistance G1-16

TABLE OF CONTENTS
G1.4.9 Cold Junction Compensation G1-16

G1.4.10 Command G1-17
G1.4C Digital I/O Module (ADM51T) Configuration G1-18
G1.4.2 Mode G1-19
G1.4.4 Tag Name G1-19
G1.4.5 Tag Comment G1-19
G1.4.6 Switch Position Label G1-20
G1.4.7 Label G1-20
G1.4.8 Button1, Button 2 G1-20
G1.4.9 Level G1-20
G1.4.10 Tag Mark G1-21
G1.4.11 Upper Window G1-21
G1.4.12 Help G1-21
G1.5 Exercise G1-22
G2. INPUT/OUTPUT FUNCTIONS (KFCS) G2-1

G2.1 FCS Input/Output Interfaces G2-1
G2.2 Process Input/Output G2-2
G2.2A Creating a New Node: KFCS G2-2
G2.2.1 Type G2-3
G2.2.2 Node G2-3
G2.2.3 Master G2-3
G2.2.4 Power Supply Unit G2-4
G2.2.6 Node Comment G2-4
G2.3 Creating a New I/O Module: KFCS G2-5
G2.3.1 IOM Type G2-6
G2.3.2 Installation Position G2-8
G2.3.4 Output Type G2-9
G2.4 IOM Builder G2-10
G2.4A Analog I/O Module (AAI141-S) Configuration G2-10
G2.4.2 Conversion G2-11
G2.4.3 Service Comment G2-12
G2.4.4 Low Limit/High Limit G2-12
G2.4.5 Unit G2-13
G2.4.6 Set Details G2-15
G2.4.8 Label G2-16
G2.4B Detailed Setting of Analog I/O Module G2-16
G2.4.1 Detect IOP G2-17
G2.4.2 IOP Detection Level G2-18
G2.4.3 Cold Junction Compensation G2-19
G2.4.4 Fallback G2-20

TABLE OF CONTENTS
G2.4.5 Pulse Input G2-20

G2.4C Digital I/O Module (ADV551-P) Configuration G2-22
G2.4.2 Mode G2-22
G2.4.3 P&ID Tag N ame G2-23
G2.4.4 Tag Name G2-23
G2.4.6 Switch Position Label G2-23
G2.4.7 Label G2-23
G2.4.9 Button1, Button2 G2-24
G2.4.10 Level G2-24
G2.4.11 Tag Mark G2-24
G2.4.12 Upper Window G2-24
G2.4.13 Help G2-25
G3. INPUT/OUTPUT FUNCTIONS (FFCS) G3-1

G3.1 FCS Input/Output Interfaces G3-1
G3.2 Process Input/Output (FFCS) G3-2
G3.3 Creating a New Node: FFCS G3-3
G3.3.1 Type G3-4
G3.3.2 Node G3-4
G3.3.3 Remote Node G3-4
G3.3.4 Power Supply Unit – Dual-Redundant Power Supply G3-4
G3.3.5 Power Supply Capacity – Power Supply G3-5
G3.3.7 Node Number G3-5
G3.4 Creating a New I/O Module: FFCS G3-6
G3.4.1 Installation Position – Slot, High Speed Read, G3-6
IOM Comment
G3.4.3 Output Type G3-9
G3.4.4 High Speed Type G3-9
G3.5 Creating a New EB 401 (ER Bus Interface Master G3-10
Module: FFCS)
G3.5.1 IOM Type (Type and Position Tab) G3-10
G3.5.2 Installation Position (Type and Position Tab) G3-10
G3.5.3 Duplicate Next Card – Remote Node G3-11
Communication
G3.5.4 Maximum Number of Nodes (Set Details Tab) G3-11
G3.5.5 Communication Protocol (Set Details Tab) G3-12
G3.5.6 Communication Base Period (Set Details Tab) G3-12
G3.5.7 Node Response Timeout (Set Details Tab) G3-12
G3.5.8 Number of Retries Upon Node Response Timeout G3-12
(Set Details Tab)

TABLE OF CONTENTS
H. SOFTWARE INPUT/OUTPUT FUNCTIONS H1

H1. Identification of Software Input/Output H3
H2. Internal Switches H4
H2.1 Common Switches (%SW) H4
H2.1.1 Condition Testing and Status Operation H5
H2.1.2 Common Switch Builder H6
H2.2 Global Switches (%GS) H9
H2.2.1 Condition Testing and Status Operation H11
H2.2.2 Global Switch Builder H12
H3. Message Output Functions H15
H3.1 Annunciator Messages (%AN) H15
H3.1.1 Condition Testing and Status H15
H3.1.2 Annunciator Builder H16
H3.2 Operator Guide Messages H20
H3.2.1 Operator Guide Builder H20
H3.3 Printout Messages H22
H3.3.1 Printout Builder H22
H3.4 Sequence Message Request H24
H3.4.1 Sequence Message Request Builder H25
H3.5 Help Messages H27
H4. Message Types H29
H4.1 System Alarm Messages H29
H4.2 Process Alarm Messages H30
H5. Questions H31
H6. Exercises H32
I. CONTROL DRAWING BUILDER I1

I1. Control Drawing Environment I2
I1.1 Function Block I2
I1.2 Text I3
I1.3 Wiring I3
I1.4 Data Link Block I3
I2. Toolbar Buttons I4
I3. File Import and Export I10
I3.1 Text File Import and Export I10
I3.2 CS Source File Import I10
I4. Exercise I11

TABLE OF CONTENTS
J. REGULATORY CONTROL FUNCTION J1

J1. Function Block Processing Functions J3
J2. Detail Specifications of PID Block J5
J2.1 Basic J5
J2.2 Tag J10
J2.3 Input J12
J2.4 Alarm J14
J2.5 Control Calculation J20
J2.6 Output J30
J2.7 Connection J33
J2.8 Others J34
J3. Other Function Blocks J36
J4. Question J37
K. SEQUENCE CONTROL FUNCTION K1

K1.1 Sequence Table Block K1
K1.2 Sequence Table Configuration K2
K1.2.1 Number of Signals K3
K1.2.2 Sequence Table Elements K4
K2.1 Step Sequence Table K7
K2.2 Non-Step Sequence Table K10
K3. Logic Chart K12
K3.1 Logic Chart Configuration K13
K3.1.1 Logic Chart Elements K13
K3.1.2 Input Element Symbol K15
K3.1.3 Output Element Symbol K15
K3.1.4 Logic Operation Element Symbol K16
K4. Exercise K21
L. HIS FUNCTION L1
L1.1 HIS Properties - Type L1
L1.1.1 Station Type L1
L1.1.2 Station Address L2
L1.1.3 Component L2
L1.2 HIS Properties - Constant L3
L1.3 HIS Properties - Network L4
L1.3.1 Control Bus TCP/IP Settings L5
L1.3.2 Setting Ethernet TCP/IP Settings L5
L1.3.3 Setting Vnet/IP Network L6

TABLE OF CONTENTS
M. HIS CONFIGURATION M1
M1.1 HIS Constants M1
M1.1.1 Station Type M1
M1.1.2 Closing Process M2
M1.1.3 Long Term Data Save M4
M1.1.4 Message Print Wait Time M5
M1.1.5 Instrument Diagram Operation M5
M1.1.6 Security M6
M1.1.7 Multiple Projects M7
N. FUNCTION KEYS N1
N1. Function Keys Assignment N2
N1.1 Function N2
N1.1.1 Assigning Window Call to a Function Key N3
N1.1.2 Assigning a System Function to a Function N3
Key
N1.1.3 Assigning Trend Data Acquisition Function N6
To a Function Key
N1.1.4 Assigning LED to a Function Key N7
N1.1.5 Assigning a Program Executing to a N7
Function Key
N1.1.6 Assigning a Multimedia to a Function Key N8
N1.1.7 Assigning Panel Set Call Function to a N8
Function Key
N1.1.8 Assigning the Function of Calling up a N9
Window from a Different Station to a
Function Key
N1.1.9 Assigning the Function of Calling up a N10
Remote Window by Window Name to a
Function Key
N1.1.10 Assigning the Function of Copying a N11
Currently Displayed Window Set to a
Function Key
N1.1.11 Assigning the Function of Clearing a N11
Window on the Remote CRT to a
Function Key
N1.2 LED N12
N1.3 Change Privilege/Change Authorization over the N13
Functions Assigned to the Function Keys
N2. Emulate Function Keys in Operation and Monitoring N14
N2.1 Enabling Shortcut Keys N14
N2.2 Shortcut Actions N15
N2.3 Cautions on Using Shortcut Keys N15
N2.4 Reserved Shortcut Functions N16

TABLE OF CONTENTS
O. SCHEDULER O1
O1. Scheduler Builder O1
O1.1 Function O1
O1.2 Start Method, Start Month, Start Date, Period, O2
Times of Repeat
O1.3 Comment O2
O2. Exercise O3
P. SEQUENCE MESSAGE REQUEST P1

P1. Sequence Message Request Builder P1
P1.1 Function P1
P1.2 Station Name P1
P2. Exercise P3
Q. PANEL SET Q1
Q1. Panel Set Builder Q1
Q1.1 Panel Set Q1
Q1.2 Display Window Q1
Q1.3 Calling up the Panel Set Q2
Q1.4 HIS Notification Q2
R. TREND ACQUISITION PEN ASSIGNMENT R1

R1. Structure of Trend R1
R2. Sampling Period and Recording Span of Trend Data R3
R3. Trend Acquisition Pen Assignment Builder R4
R3.1 Trend Format R5
R3.2 Long Term Data Save R7
R4. Trend Group Definition R8
R4.1 Acquisition Data, Data Axis Span Change, R8
Low/High Limit Value
R4.2 Data Type R8
R5. Export Trend Data to CSV File R9
S. HIS WINDOW CREATION S1

S1. HIS Window Creation S1
S1.1 Window Types S2
S1.2 Window Name S3
S1.3 Help Message Number S3
S1.4 Window Comment S3
S2. Set Details Tab S4
S2.1 Window Operation and Monitoring Authority S4
S2.2 Disable Scaling S5

TABLE OF CONTENTS
T. CONTROL GROUP WINDOW DEFINITION T1

T1. HIS Window Creation T1
T1.1 Control Group (8-loop) T2
T1.2 Control Group (16-loop) T3
T1.3 Console Control (8-loop) T3
T2. Instrument Diagram Definition T4
T2.1 General Tab T4
T2.2 Instrument Diagram Tab T5
T2.3 Data Bind T6
U. OVERVIEW WINDOW DEFINITION U

U1. HIS Window Creation U1
U1.1 Overview U2
U2. Overview Window Definition U3
U2.1 General Tab U3
U2.2 Overview Tab U4
U2.3 Function Tab U6
U2.4 Data Bind Tab U8
V. HELP MESSAGE WINDOW V

V1. System Alarm Help V1
V2. User-Defined Help V1
V3. System Window Help V1
V4. Help Window Creation V2
V4.1 Help Message Number V3
V4.2 Help Message Comment V3
V5. Help Window Definition V3
W. GRAPHICS BUILDER W
W1. Graphics Builder Environment W1
W1.1 Graphics W2
W2. Toolbars W3
W2.1 Standard Toolbar W3
W2.2 Draw Toolbar W4
W2.3 HIS Functions Toolbar W5
W2.3.1 Process Data - Character W6
W2.3.1A General Tab W6
W2.3.1B Text Tab W8
W2.3.1C Graphic Modify Tab W9
W2.3.1D Modify Coordinates Tab W13
W2.3.1E Process Data - Character Tab W15
W2.3.1F Data Bind Tab W18
W2.3.2 Process Data - Bar W21
W2.3.2B Fill Tab W22

TABLE OF CONTENTS
W2.3.2E Process Data - Bar Tab W25

W2.3.3 Process Data - Arrow W27
W2.3.3E Process Data - Arrow Tab W31
W2.3.4 Process Data - Circle W34
W2.3.4E Process Data - Circle Tab W38
W2.3.5 Touch Target W40
W2.3.5B Function Tab W41
W2.3.5C Data Bind Tab W42
W2.3.6 Push Button W43
W2.3.6B Text Tab W44
W2.3.6C Label Tab W45
W2.3.6D Function Tab W46
W2.3.6E Graphic Modify Tab W47
W2.3.7 Faceplate W49
W2.3.7B Faceplate Block Button Tab W50
W2.3.8 Instrument Diagram W52
W2.3.8B Instrument Diagram Tab W54
W2.3.9 Window W56
W2.3.9B Window Tab W58
W2.3.10 Message W60
W2.3.10C Message Tab W63
W2.3.10D Data Bind Tab W64
W2.3.11 Dialog Name W65
W2.3.10C Dialog Name Tab W68

TABLE OF CONTENTS
W2.3.12 Trend W70

W2.3.12B Trend Tab W72
W2.3.13 Overview W74
W2.3.13C Function Tab W78
W2.3.14 Control W80
W2.3.14B Control Tab W82
W2.4 Format Toolbar W83
W2.5 Edit Object Toolbar W84
W2.6 Parts Toolbar W85
W2.6.1 Parts W85
W2.6.2 Linked Part W87
W2.7 Background Screen Bitmap and Soft Key W91
W2.7.1 Background Screen Bitmap W91
W2.7.2 Soft Key W91
W2.7.2A Soft Key Tab W91
W2.7.2C Function Tab W94
W3. Graphic Builder Operation Mode W95
W4. File Properties W96
W5. Setting the Options W101
W6.1 Debug Function on the Graphic Builder W103
W6.2 Debug Dialog W104
X. TEST FUNCTION X
X1. Types Of Test X1
X2. Operating EnXironment X3
X3. Test Procedures X6
X4. Function Of Test Function Main Menu Window X7
X5. I/O Disconnect/Connect X7
X5.1 I/O Disconnect Setup Dialog Box: PFCS/SFCS X8
X5.2 I/O Disconnect Setup Dialog Box: LFCS X8
X5.3 I/O Disconnect Setup Dialog Box: KFCS X9
X6. Wiring Function X10
X6.1 Wiring Edit Functions X10
X6.1.1A Types of Wiring X11
X6.1.1B Wiring Definition Items X13
X6.1.1C Automatic Data Wiring Creation X15
X6.1.1D Wiring Data Storage X15
X6.1.1E Wiring Data Downloading X16
X6.2 Wiring Operation Functions X17
X6.2.1A Display Cycle Change X18
X6.2.1B Wiring On/Off X18
X6.2.1C Wiring Execution X18

TABLE OF CONTENTS
X6.2.1D Wiring Continuous Execution X18

X6.2.1E Wiring Stop X18
X6.2.1F Wiring Pause X18
X6.2.1G Suspend X18
X6.2.1H Wiring Change X18
X7. Test Target Station Operation Functions X21
X8. Step Execution Function X21
X9. Breakpoint X22
X9.1 Breakpoint Setting X22
X9.2 Breakpoint Setup X22
X9.3 Breakpoint Operation and Monitoring X24
X9.3.1A Display Cycle Change X24
X9.3.1B Breakpoint Monitoring X25
X10. One-Shot Execution Function X26
X10.1 Function Blocks to which One-Shot Execution X26
may be applied
X10.2 Message One-Shot Output X27
X10.2.1 One-Shot Output Messages X28
X11. Profiler X30
X11.1 CPU Load Display X31
X11.2 All Blocks Completion Times X32
X11.3 Function Blocks Profile Data Display X33
X12. I/O Error Test X35

TABLE OF CONTENTS

A. SYSTEM OVERVIEW
A. SYSTEM OVERVIEW
A1. System Components

This chapter describes each of the CENTUM CS 1000/3000 system components.
Human Interface Stations (HIS)

The HIS is mainly used for operation and monitoring – it displays process variables, control
parameters, and alarms necessary for users to quickly grasp the operating status of the plant.
It also incorporates open interfaces so that supervisory computers can access trend data,
messages, and process data.
Hardware Requirements
PC model: A recommended personal computer
Main Memory: Varies according to the software to be installed:
YOKOGAWA SINGAPORE TRAINING CENTRE Page A1 of A33

A. SYSTEM OVERVIEW
Peripherals: CD-ROM drive and 3.5-inch FDD. An MO drive, a DAT drive, or a backup hard
disk should also be made available for the backup of the system, databases, and engineering
data. In order to connect the PC with peripherals, SCSI card may be required to be installed
in the PC.
Software Environment
Operating system:
Windows 2000, Service Pack4 (recommended),
Windows XP, Service Pack1, Service Pack2,
Windows Server 2003 or
Windows 2000 Server, Service Pack4
Color pallet:
Above High color (65536). With at least 8MB of VRAM, 16000000 colors can be specified.
Virtual memory paging size: 300 MB. (Not to use System Builders)
400 MB. (To use System Builders)
Software Compatibility
The CS 3000 software is compatible with the commercial software listed below, with which
the compatibility has been confirmed:

A. SYSTEM OVERVIEW
Compatibility cannot be guaranteed for any commercial software other than those listed
above.
Revision Numbers of Report Package and Microsoft Excel

When using the report package in the release R3.03 or later, inconsistency with the
Microsoft products service releases may occur.
A1.1 Types of HIS

Two types of HIS:
• Desktop Type
Uses a general purpose PC.
• Console Type
Consists of a console assembly and a general purpose PC. Two types of console
type HISs:

A. SYSTEM OVERVIEW

A. SYSTEM OVERVIEW
Engineering PC (ENG)
The PC with engineering functions used to perform CENTUM CS 3000 system generation
and maintenance management.
A1.2 Types of FCS

Field Control Station (FCS)
FCS performs process control, and manages communication with subsystems such as
PLCs. The control station is used to generate the control function where the process
variables are read and control calculation is carried out in the processor cards to
determine the control output to be sent to the field.
• FCS for FIO

This FCS uses the Fieldnetwork I/O (FIO) modules, which are compact and
consist of various lineups such as the connector types and so forth. According to
the application capacity, there are the standard model and the enhanced model.
• Compact FCS for FIO

This is a compact FCS with I/O modules integrated into the Field Control Unit.
• FCS for RIO

This FCS uses the Remote I/O (RIO) modules, which have many installation
bases and M4 screw terminals to connect signal cables. According to the
application capacity, there are the standard model and the enhanced model.
• Compact FCS for RIO

This controller is usually installed near the equipment or process it controls, and
is ideal for communicating with subsystems.

A. SYSTEM OVERVIEW
Standard FCS (Main Memory 16 MB)

Model Type
AFS10S Field Control Station (19” rack mountable type)
AFS10D Duplexed Field Control Station (19” rack mountable type)
AFS20S Field Control Station (with cabinet)
AFS20D Duplexed Field Control Station (with cabinet)
AFS30S Field Control Station (for FIO, 19” rack mountable type)
AFS30D Duplexed Field Control Station (for FIO, 19” rack
mountable type)
AFS40S Field Control Station (for FIO, with cabinet)
AFS40D Duplexed Field Control Station (for FIO, with cabinet)
Enhanced FCS (Main Memory 32 MB)
Model Type
AFG10S Field Control Station (19” rack mountable type)
AFG10D Duplexed Field Control Station (19” rack mountable type)
AFG20S Field Control Station (with cabinet)
AFG20D Duplexed Field Control Station (with cabinet)
AFG30S Field Control Station (for FIO, 19” rack mountable type)
AFG30D Duplexed Field Control Station (for FIO, 19” rack
mountable type)
AFG40S Field Control Station (for FIO, with cabinet)
AFG40D Duplexed Field Control Station (for FIO, with cabinet)
Compact type FCS (SFCS) – Available in both CS1000 and CS3000 Systems.
A compact type FCS model (SFCS) connects to RIO directly, not via RIO bus.
Compact FCS (PFC : Main Memory 8 MB/16 MB,

AFF 0 : Main Memory 32 MB)
Standard type PFCS in the CS 3000

Model Type
PFCS-H Field Control Station (compact type)
PFCD-H Duplexed Field Control Station (compact type)
AFF50S Field Control Unit (for FIO, 1” Rack Mountable)
AFF50D Duplexed Field Control Unit (for FIO, 19: Rack Mountable)
Standard type PFCS in the CS 1000

Model Type
PFCS-S Field Control Station (standard type)
PFCD-S Duplexed Field Control Station (standard type)
PFCS-E Field Control Station (enhanced type)
PFCD-E Duplexed Field Control Station (enhanced type)
Configuration of a Control System with different types of FCSs:

A. SYSTEM OVERVIEW

A. SYSTEM OVERVIEW

A. SYSTEM OVERVIEW
• Cabinet Type LFCS2/LFCS

A. SYSTEM OVERVIEW
• Rack Mountable LFCS2/LFCS

A. SYSTEM OVERVIEW
• Cabinet type KFCS2/KFCS

A. SYSTEM OVERVIEW
• Rack Mountable KFCS2/KFCS

A. SYSTEM OVERVIEW
• Compact type FCS (PFCS/SFCS)

A. SYSTEM OVERVIEW
• Compact type FCS (FFCS)

A. SYSTEM OVERVIEW
A2. FCS Hardware Description

Power Supply Unit
For the LFCS, the main power distribution board receives a specified power supply and
distributes it to the power distribution boards in the front and two node power distribution
boards in the rear.
Nest power distribution boards distribute the power to the power supply unit(s) of the
FCU and nodes on the front side of the cabinet.
FCU power distribution boards distribute the power to the power supply unit(s) of the FCU.
Node power distribution boards distribute the power to the nodes on the rear side of the
cabinet.
The power unit in an FCU receives power supply from the power distribution
Board, converts it to an isolated direct-current voltage, and supplies that DC power to each
unit and card in the FCU.
The KFCS node power distribution boards are used to distribute the power from the main
power distribution board to node and FCU power distribution board.
This unit supplies power to the common part of the PFCS/SFCS.
A power supply module is connected to a 100 to 120V AC or 220 to 240V AC or 24V

DC main source and supplies insulated +5V and +24V to each installed I/O module through
the back board. The +5V and +24V outputs support dual-redundant insulated output
operation. - FFCS
Battery Unit in FCU

Back-up period: 72 hours maximum
Backs up the memory in the processor card during a power failure.
Battery life Temperature

3 years 30° C or less
1.5 years 40° C or less
9 months 50° C or less
Control Bus Coupler Unit

The coupler is where the Vnet or VLnet cable is installed into the FCS. It performs signal
isolation and signal level conversion.
RIO Bus Distribution Unit (LFCS)

RIO bus distribution units are provided in the front and rear sides of an LFCS with cabinet.
Each RIO bus distribution unit connects up to three nodes to the same RIO bus.
The standard RIO bus distribution unit can be used for either a single or dual RIO Bus.
RIO Bus Interface Card (LFCS)

The RIO bus interface card performs data communication via the RIO bus coupler unit
between multiple nodes connected on the RIO bus.
RIO Bus Coupler Unit (LFCS)

The RIO bus coupler unit couples the RIO bus interface card installed in the FCU to the RIO
bus by modulating and demodulating the signals.

A. SYSTEM OVERVIEW
ESB Bus Interface Card (KFCS)

The ESB bus interface card (SB301) performs data communication via the SB401 on node
unit for FIO between I/O modules.
ESB Bus Coupler Unit (KFCS)

The ESB bus coupler unit couples the ESB bus interface card installed in the FCU to the ESB
bus by modulating and demodulating the signals.
ESB Bus Coupler Unit (FFCS)

ESB bus coupler module (Model: EC401) is installed in field control unit and used for
communicating with the ESB bus interface module (Model: SB401) of local node.
This module has one ESB bus port. Dual-redundant bus schemes can be configured with the
two modules.
Fan Units
Used to suppress an increase of the temperature inside the cabinet and prevent a
temperature increase from causing malfunctions and faster deterioration of the parts in the
FCU and nodes.
Node Interface Unit

The NIU offers an interface function to send analog and contact I/O signals from the field to
the Field Control Unit via a RIO bus, and it offers the function to supply power to the
input/output units.
Node
Signal processing devices that convert process input/output signals to or from the field
equipment and transmits them to the field control unit (FCU).
Process Input/Output
Used to exchange signals between field devices and FCSs.
An FCS can receive signals from process detectors and output signals to process control
signals to process control elements.
Processor Card in FCU

The processor card performs control calculations as well as monitors its own CPU and power
supply.
External Interface Unit

The external interface unit outputs the result of the self-diagnostics by the processor card to
the contact output terminals on the power distribution board.

A. SYSTEM OVERVIEW
Dual-Redundant Architecture of FCU: KFCS
• Each processor card unit has two CPUs, which perform the same control
computation. The computation results are compared by a collator during each
computation cycle. If the computation results from the two CPUs match, the collator
determines that the computation is normal and sends data to main memory and bus
interface unit.
• Because the main memory has an ECC (Error-Correcting Code), transient bit
inversion errors occurring in the main memory can be repaired.
• If computation results from CPU1 and CPU2 do not match, the collator decides that
a computation error has occurred, and the control right is transferred to the standby
card.
• The standby processor unit card performs the same computation as the control one,
even though it is in the standby state. Therefore, it can immediately resume the
output of control computation data to the bus interface when it takes over the control
right.
• Self-diagnostics will be executed on the processor unit in which an error has

occurred. If no CPU error is detected as a result of diagnostics, the error will be
taken as a transient computation error, and the unit returns from error state to
standby. The processor unit on standby performs the same computation
concurrently with the control side.
Therefore, CPUs within the same unit collate each other’s computation data, being
sure to detect any computation errors. Because the unit on standby performs the
same control computation concurrently with the control unit, it can take over the
control computation at any point without interruption, even for a very short time.
**NOTE: LFCS same as above except that ESB Bus Interface

(SB301) is replaced by RIO Bus Interface (RB301).

A. SYSTEM OVERVIEW
Dual-Redundant Architecture of FCU: SFCS
• At the Vnet interface, a communication interface supporting dual-redundancy is

mounted on the CPU and connected to the dual-redundant control bus.
• At the processor unit, control side and standby side CPUs synchronize each other to
perform the same control computation. If an error occurs at the control side CPU,
the synchronous execution hot standby system will transfer the control right to the
standby side CPU without interruption.
• If an invalid access is detected against the main memory or the standby side in the
control side processor unit, processing on the control side will stop immediately and
the control right will be transferred to the standby side. This prevents the destruction
of data inside the local system, as well as at the destination site due to CPU
malfunctions.
• There is a WDT (Watch Dog Timer) in the processor unit to supervise the execution
of control function. Whenever the abnormality in control function is detected, the
control right is switched from control side to the standby side, as if the abnormality is
in the control side processor.
• In the main memory, error-correction coding (ECC) function is provided so that the
transient bit inversion error in the main memory may be repaired.
• The PI/O bus interface has the function to run the PI/O executions on control side
and to diagnostic 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.
**NOTE: PFCS same as above except that Vnet Interface is

replaced by VL Net Interface.

A. SYSTEM OVERVIEW
Dual-Redundant Architecture of FCU: FFCS
• There are two processors on each processor module. Each CPU performs the same
control computations, and the results are compared each calculation. If the results
agree, then the module is assumed to be normal and the results are transmitted to
memory and bus interface module. The main memory uses ECC (error-correcting
code) which can correct transient reversed-bit errors.
• If the results from CPU1 and CPU2 do not agree, then the comparator takes this as
“CPU abnormal”, and switches to the standby processor module.
• A Watch Dog Timer is used to detect if the active processor module is abnormal,
which results in a switch from active to standby processor module.
• The standby processor module is performing the same computations as the active
module, and when it is switched to active status then the results it has just computed
are transferred to the bus interface there is no interruption in control.
• If a “CPU abnormal” error is detected in a CPU module, a self-diagnostic check is

performed on the module; if the hardware is not abnormal, then the error is treated as
a transient error and the module reverts from “abnormal” to “standby” status.
• The V net and V net interface are dual redundant.

A. SYSTEM OVERVIEW
A3. 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 2 cable ( for stations)
10 Base 5 (for FCS, CGW, etc)
Transmission 185 m/segment (for 10 Base 2) 185 m/segment (for 10 Base 2)
distance 500 m/segment (for 10 Base 5)
Access Method Token Passing Token Passing
Repeater Max. 1.6 km, 8 repeaters Max. 1.6 km, 8 repeaters
- Coaxial Cable Max. 20 km, 4 repeaters Max. 20 km, 4 repeaters
- Optical Fiber
Ethernet
HIS and ENG, HIS and supervisory systems can be connected by an Ethernet LAN;
supervisory computers and personal computers on the Ethernet LAN can access messages
and trend data in the CENTUM CS 3000 system. The Ethernet can also be used for sending
trend data files from the HIS to supervisory computers, for equalizing HIS databases and for
acquiring trend date for other stations, eliminating the load on the V net.

A. SYSTEM OVERVIEW
Vnet/VLnet versus Ethernet

A system with only a single HIS, with engineering functions installed, does not need Ethernet
but in general Ethernet (and corresponding network engineering) is required.
Also, instead of equalizing HIS databases and acquiring trend date for other stations via the
VL net, these can be performed via Ethernet, reducing the load on the VL net. (Installing
Ethernet requires optional network engineering).

A. SYSTEM OVERVIEW
A4. System Specifications
System CS 1000 CS 3000 CS 3000 with

Vnet/IP
Maximum number of 8000 100 000 100 000
monitoring tags (When using LHS4000, (When using LHS4000,
up to 1,000,000 per up to 1,000,000 per
system) system)
Total number of stations in - 256 -
multi-domain systems
Total number of 1 16 16 (Vnet/IP domains +
interconnected domains Vnet domains)
Total number of stations per HIS (8) 64 (HIS (16) , FCS, 64 (HIS, FCS, APCS,
domain FCS (16) BCV, CGW) GSGW, Exaopc, PRM ,
Vnet Router)
**Note : No limit on
number of HIS stations
HIS: Human Interface Station

BCV: Bus Converter
CGW: Communication Gateway Unit
FCS: Field Control Station
APCS: Advanced Process Control Station
GSGW: Generic Subsystem Gateway Package
Exaopc: OPC Interface Package
PRM: Field Communications Server for Plant Resource Manager
AVR10D: Vnet Router
● Bus Converter (BCV)

With the CS 1000 system, the bus converter (BCV) connects the station on the VL
net and the µXL control unit on the RL bus.

A. SYSTEM OVERVIEW
With the CS 3000 system, the BCV connects the station on the V net and station(s)
on other domain(s).
A domain is a logical V net bus segment. You can use a Bus Converter to link
CENTUM CS 3000 domains, or link to previous systems (CENTUM CS, CENTUM-
XL, CENTUM CS 1000, etc).
When you reach the maximum of 64 stations in a domain, you can start a new
domain and link the two domains using a Bus Converter.
Functional Overview - Bus Converter for V net

The Bus Converter for V net is used to connect one domain V net to a CS 3000 system or a
system with CS 3000 and CENTUM CS constructed on other domain V net. It acts as an
intermediary in communication between the two, upper level and lower level, V nets. It
facilitates communication with a hierarchical structure so that all stations connected to the
lower level V net can be put under the integrated supervision of the stations of the upper level
V net. When CS 3000 is connecting to a CENTUM CS system, CS 3000 will be in upper level
and CENTUM CS will be in lower level.
● Communication Gateway Unit (CGW)

The communication gateway unit is a gateway that connects the supervisory
computer with the VL net or V net, which are the control communication networks for
the CS 1000 system and CS 3000 system, respectively.

A. SYSTEM OVERVIEW

A. SYSTEM OVERVIEW
A5. Hardware Configuration

Setting the Domain Number: LFCS/KFCS/PFCS/SFCS/FFCS/FFCS-L
A domain stands for a range of stations connected by a single train of the V net.
Set the domain number to a value from 1 to 16.
To set a domain number, set the dip switches as follows.
Bits 2 and 3 must always be zeros (0s).

A. SYSTEM OVERVIEW
Setting the Station Number: LFCS/KFCS/PFCS/SFCS/FFCS

Set station number specified following range.
• Within the range of 1 to 24 (*1)
• Within the range of 1 to 64 (*2)
To set a station number, set the dip switches as follows.

A. SYSTEM OVERVIEW
A6. System Components of Vnet/IP Network

The specification when connecting devices in a Vnet/IP domain is as follows:
• Number of Vnet/IP stations connected: Max. 64 units
Vnet/IP stations including V net router
• Other general-purpose Ethernet communication devices

(PCs, routers, switches etc.): Max. 124 units
• Levels of layer 2 switches: Max. 7 levels
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
● Vnet/IP Domain
A Vnet/IP domain consists of two independent subnets of bus 1 and bus 2. In the
CENTUM CS 3000, 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.

A. SYSTEM OVERVIEW
● 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.
● Human Interface Station (HIS)

An HIS serves as a human interface for operation, monitoring, and engineering. For
connections to the Vnet/IP, a VI701 Control Bus Interface Card is used.
● FFCS-L
The FCS performs process control and manages communications with subsystems such
as PLCs. Two types of field control stations for Vnet/IP and FIO are available:
AFV10S: Field Control Unit (for Vnet/IP, FIO, rackmounted)
AFV10D: Duplexed Field Control Unit (for Vnet/IP, FIO, rack-mounted)
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.
● Layer 2 Switch
This is a device to connect equipment within the Vnet/IP domain.
● Advanced Process Control Station (APCS)

An APCS advanced process control station implements control functions with a general-
purpose PC connected to a Vnet/IP, aimed at improving advanced control and plant
efficiency. Use VI701 Control Bus Interface Card for connection to Vnet/IP.
● Generic Subsystem Gateway Package (GSGW)

With a general-purpose PC connected to a Vnet/IP, GSGW packages can collect and set
data of various types of subsystems using an OPC DA server. They can easily collect and
set subsystem data without creating dedicated communications programs.
Use VI701 Control Bus Interface Card for connections to Vnet/IP.

A. SYSTEM OVERVIEW
● 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.
A Vnet router is a device to connect a Vnet/IP domain and a Vnet domain for relaying
control communications. This router realizes operation and monitoring of a control station
in one domain from another domain by connecting the Vnet/IP and Vnet domains. The
following product is available:
AVR10D: Duplexed Vnet Router (for redundant use of communications and power supply
modules)
● Layer 3 Switch
A general-purpose 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.

A. SYSTEM OVERVIEW
A7. Field Control Station (Vnet/IP)

The FFCS-L is a control station that can only be connected to Vnet/IP. The types of function
blocks and I/O cards that can be connected are the same as those of the FFCS.
The FFCS-L is available in the following station types:

• AFV10S Field Control Unit (for Vnet/IP, for FIO, 19-inch rack mountable)
• AFV10D Duplexed Field Control Unit (for Vnet/IP, for FIO, 19-inch rack mountable)
Next, specify the database type. The following database types are available:
• General-purpose type
• Expanded type (To use an expanded type database, the following package is
required: LFS1530 Application Capacity Expansion Package (for AFV10 )
When a new FFCS-L is created, the control bus type of that domain will automatically
be Vnet/IP.

A. SYSTEM OVERVIEW
A7.1 FFCS-L Hardware Description

Power Supply Module
A power supply module is connected to a 100 to 120V AC or 220 to 240V AC or 24V
DC main source and supplies isolated +5V and +24V to installed I/O modules through the
back board. The +5V and +24V outputs support dual-redundant isolated output operation.
Battery Pack
Back-up period: 72 hours maximum
The battery unit is used for backing up the main memory of the processor module when
power failure occurs.
Battery life Temperature

3 years 30° C or less
1.5 years 40° C or less
9 months 50° C or less
Processor Module
Control algorithm calculations are performed in the processor module.
The processor module has diagnostic capability, when the CPU or power supply
encounters abnormalities, a signal can be output through external interface unit.
ESB Bus Coupler Module (EC401)

ESB bus coupler module (Model: EC401) is installed in field control unit and used for
communicating with the ESB bus interface module (Model: SB401) of local node.
This module has one ESB bus port. Dual-redundant bus schemes can be configured with
the two modules.
External Interface Unit

The external interface unit has terminals for connecting the specified power supply, and
distributes the power through the output connectors.

A. SYSTEM OVERVIEW
A8. Transmission Path Specification (Vnet/IP)

Network Topology: Star formation
Transmission Path Redundancy: Available (control bus communications only)
Transmission Cable: Unshielded twisted pair (UTP) at enhanced category 5 or greater.

A. SYSTEM OVERVIEW
A9. Questions
Q1. Which station does the necessary calculation and processes the input/output
electrical signal from the field?
Q2. Which station is used for monitoring and operation of the field tags and
Instrument, displaying the necessary process variable, output variable?
Q3. What is the network cable for signal transmission between FCS and HIS for CS3000
and CS1000?
Q4. What software platform is CS 1000 and CS 3000 installed in the HIS and ENG?
Q5. What will happen to the FCS memory when there is power failure to the FCS?
Q6. What is a node in LFCS?
Q7. What is the maximum of HIS stations in a CS 1000/CS 3000?
Q8. What is the difference between an ENG and a HIS?
A10. Exercises
1. Configure the following FCS dip switches for station FCS0305.

A. SYSTEM OVERVIEW

B. ENGINEERING ENVIRONMENT
The CENTUM CS 1000/CS 3000 engineering functions are used for system generation – for
creating the databases necessary for monitoring, operation and control – and for
maintenance.
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
. Target tests
Test Function Virtual test
Target test I/O disconnection (Use virtual I/O)
Use real I/O
B1. Test Function
B1.1 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.
It uses FCS simulation (virtual FCS) to test the system configuration on a single Personal
Computer. You can operate several virtual FCS at the same time.
YOKOGAWA SINGAPORE TRAINING CENTRE Page B1 of B5

B1.2 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.
These use actual HIS and FCS for the test. Actual field wiring is not required, or – if it
exists
– you can specify that it be ignored (I/O switching).

B2. Concurrent Engineering

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

B3. Engineering Work Flow

The engineering work flow for this course is as shown:
Start
Start System View
Step 1: Project Creation

. Create necessary folders for target system.
Step 2: Defining Project Common Items

. Define security function.
. Define operation marks.
Step 3: Defining FCS Control Functions

. Define FCS station configuration.
. Define Process I/O modules.
. Define Software I/O.
. Define Messages.
. Define Regulatory Control Functions.
. Define Sequence Control Functions.
Step 4: Defining HIS Functions

. Define HIS station configuration.
. Define HIS constants.
. Define Function Keys assignment.
. Define Scheduler Function.
. Define Trend Recording Functions.
. Define Sequence Message.
. Define User-defined windows.
. Define Help Dialog.
Step 5: Conducting Test Function

. Run a Virtual Test Function.

B4. Questions
Q1. What is the difference between a virtual test and target test?
Q2. How is concurrent engineering done?


C. PROJECT CREATION
C. PROJECT CREATION
Create a project, which is the basic unit of the engineering database management.
A project is a unit manages the database of the FCS and the HIS created by the user. All
builder files defined by various builders are managed under the project.
C1. Types of Project

There are three types of project; the default project, the current project and the user-defined
project.
The project attribute (default, current, and user-defined) may be changed using the Project
Attribute Change Utility.
. Default Project
The project created the first time when the System View starts is referred to as the default
project.
The characteristics of the default project are as follows:
. This project is downloadable to the FCS.
. The virtual test with the FCS simulator can be performed for this project.
. This project is downloadable to the HIS.
. This project is downloadable off-line to the FCS of the target system.
. Current Project
When any one of the FCS’s created in a default project is successfully downloaded, the
attribute of the project changes from the default project to a current project.
Online engineering becomes enabled.
The current project can perform the target test using the Test Function.
The characteristics of the current project are as follows:
. Multiple current projects cannot be created.
. The target test can be performed for this project.
. This project is downloadable to the HIS.
. This project is downloadable to the FCS of the target system.
. User-Defined Project
A project copied either from the default project or from the current project is referred to as
a user-defined project.
This project cannot be loaded to the HIS. This project is used when engineering using
virtual tests or making a backup copy of the current project.
The characteristics of the user-defined project are as follows:
. Multiple user-defined projects can be created in System View.
. The virtual test with the FCS simulator can be performed for this project.
. This project is not downloadable to the FCS or HIS of the target system.
YOKOGAWA SINGAPORE TRAINING CENTRE Page C1 of C14

C. PROJECT CREATION
C2. Creating a Default Project

A project is created when System View is executed for the first time after the builders are
installed. The project created has the attribute of “the default project” at this stage. Once this
project is downloaded to the FCS of the target system, the project’s attribute is changed from
“the default project” to the current project.
1. Start System View
Start
Programs
YOKOGAWA CENTUM
System View
2. Start Default Project Creation

When the System View could not identify an existing current or default project, it will
prompt the user to create a default project with the dialog box as shown below. Click
[YES] to create the default project.
3. Project Outline

C. PROJECT CREATION
The project information area allows the project creator to enter arbitrary characters.
Enter information on the process and the person in charge of DCS to manage the
project.
4. Project Property
Project name is an alphanumeric character string less than 8 characters.
The comment within 32 alphanumeric characters or 16 double-byte characters may
be entered as the project description.
Moreover, an alias can be created for a project. An alias of project can be defined
with 8 alphanumeric characters.
The project position is the project folder’s location in the hard disk. The default
location in which to store the project is shown below. If more than one hard disk
exists, the storage drive may be specified accordingly such as D:\.
Default location in CS 3000: C:\CS3000\ENG\BkProject\
5. Creating an FCS folder

A folder for the first FCS database files is created when the default project is created.

C. PROJECT CREATION
Assign the correct station type and station address as they cannot be modified upon
confirmation. Additional FCS can be created in future for more FCSs.
6. Creating a HIS folder

A folder for the first HIS database files is created when the default project is created.

C. PROJECT CREATION
Assign the correct station type and station address as they cannot be modified upon
confirmation. Additional HIS can be created in furture for more HISs.
7. Project folders
The project consists of 3 basic folders – Common, FCS and HIS.
Additional FCS, HIS or other stations can be created under the pull down menu.
Select project
Right click on project
Create New
HIS or FCS

C. PROJECT CREATION
C3. Project Attribute Utility

The Project’s Attribution Utility is an engineering tool that makes it convenient to register a
project created from other PC, to change a project’s properties or to remove the registration of
a project.
Before using the Project Attribute Change Utility, check that System View is not running. If it
is running, the Project Attribute Change Utility cannot run.
Only one project can exist as the default project or current project in System
View.
C3.1 Start Project Attribute Utility

Start Project’s Attribution Utility
Start
Programs
YOKOGAWA CENTUM
Project’s Attribution Utility

C. PROJECT CREATION
Click
Click

C. PROJECT CREATION
C3.2 Registering a Project

To register a new project in the System View, select [Register] in the Project’s Attribution
Utility.
Click

C. PROJECT CREATION
C3.3 Changing the Attribute of a Project

To change the attribute of a project, select [Change] in the Project’s Attribution Utility.
Click
C3.4 Deleting a Project

C. PROJECT CREATION
To delete a project, select [Delete] in the Project’s Attribution Utility.
Click

C. PROJECT CREATION
C4. Questions
1. Describe the major difference between

. Default Project
. Current Project
. User-defined Project

C. PROJECT CREATION
C5. Exercise
1. Create a project name [TESTPJT] with the following folders:

. FCS0101 (AFS40D /AFV10D)
. HIS0164 [Based on the installed Vnet/ Vnet/IP card (VF701/VI701)
configuration.]
2. Change the project [TESTPJT] attribute to Current.
3. Change the project [TESTPJT] attribute back to User-defined.
4. Delete the project [TESTPJT] without deleting it from the hard disk.
5. Restore the project [TESTPJT] back to System View window.
6. Remove the project [TESTPJT] from the hard disk in the System View window.
7. Before proceeding to the next chapter, do the following:

. Change project [TRAIN3] back as Default project.
. Delete any other projects from the System View window.
8. Start a Virtual Test Function of Project TRAIN3/VNETIP based on the following steps:
Click Start
Programs
YOKOGAWA CENTUM
System View
In System View, select FCS0101 from TRAIN3 / VNETIP.

From the pull-down menu, choose Test Function.
Select the HIS station for emulation.

C. PROJECT CREATION
At this stage, the FCS simulation will start based on the chosen FCS and HIS station.
The FCS simulation box called Test Function will appear. Minimise the box without
closing it.
Minimise the System View window and the Virtual Test Function HIS monitoring and
operation window is ready to be used for testing.

C. PROJECT CREATION

D. PROJECT COMMON ITEMS

The items to be commonly used in the project are defined. If the [COMMON] folder under the
project folder is selected in System View, a listing of builder/ viewer file names will be
displayed in List View. Each of the builders/viewers can be started by double-clicking the
builder/viewer file name.
In this chapter, the definitions of the following common items are explained:
• Alarm Builders
- Alarm Priority Builder
- Alarm Processing Table Builder
- System-fixed Status Character String Viewer
- User Defined Status Character String Builder
• Plant Hierarchy Builder
• Engineering Unit Symbol Builder
• Switch Position Label Builder
• Multiple Projects Connection Function Builder
• Operation Mark Builder
• Station Configuration Viewer
• Status Change Command Character String Builder
• Security Builder
D1. Alarm Builder

Upon occurrence of the alarm, the color of the tag mark for the function block corresponding
to the alarm changes to the alarm color. The alarm status is displayed in a character string,
and the alarm is processed in a predetermined manner.
The alarm status character string can be either a system-fixed character string or a
user defined character string.
Designating the Alarm Status

To engineer the alarm status, designate the following:
1. Alarm status character string (alarm name) or System-fixed Status Character String Viewer
Designate the alarm status character string in the User-Defined Status Character String
Builder.
The alarm status character strings available for each function block are in the system-fixed
character string viewer.
2. Alarm priority
Designate alarm priorities one by one in the Alarm Priority Builder. Multiple alarm priorities at
the same level cannot be designated for each function block simultaneously
3. Alarm processing table

Designate the alarm processing table in the Alarm Processing Table Builder.
4. Alarm processing level for each function block

Designate the alarm processing level in the Function Block Overview Builder, the
Function Block Detail Builder, the Control Drawing Builder, the Annunciator Builder, and the
Tag List Builder.
YOKOGAWA SINGAPORE TRAINING CENTRE Page D1 of D36


D1.1 System-Fixed Alarm 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.
The table below shows the alarm status character strings available for each function
block:

D1.2 User-Defined Alarm Status Character String

USER9 (Faceplate Block), USER10 (SFC Block), USER11 to 16 (Unit Instrument)
There are eight tables (USER9 to USER16) for alarm status character strings that the
user can designate in the User-Defined Status Character String Builder for user-defined
blocks.
The function blocks that can use the alarm status 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:

D1.3 Alarm Processing
The user can designate the alarm display color and priority to process each alarm of
function blocks in the Alarm Processing Table Builder.
The alarm status conforms to the designation performed in the Alarm Processing Table
Builder and the User-Defined Status Character String Builder.
The alarm status bit positions in the Alarm Processing Table Builder correspond to the
character string Nos. in the User-Defined Status Character String Builder.
Alarm status bit positions 1 to 6 are not displayed in a window because they are system
fixed.
Alarm processing levels Nos. 1 to 4 are also system-fixed.
The user can designate the color and the priority for alarm processing level Nos. 5 to 16
for alarm status bit positions 7 to 32. The user can change alarm status bit positions 7
and 8 that are for existing control stations.

D1.4 Alarm Priority

The alarm processing level is defined for each function block. The output operation for
each alarm priority can be selected.
The HIS performs alarm output action according to the alarm processing level.
The Operation and Monitoring executes the following alarm processing according to the
alarm priority:
¾ Display in a window (CRT)

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.

¾ Printout to a Printer (PRT)

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.
¾ Log to a File (Historical File)

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.
¾ Alarm Action
The alarm output actions by the HIS include messages output on the window screen and
the LED flashing.
Basically, the alarm flashing action starts upon receiving a message that indicates
occurrence of an alarm. The action stops upon receiving a message that indicates
returning to a normal status, or when acknowledgment operation is performed by the
operator.
The alarm actions are classified into the following types based on the flashing actions that
correspond to alarm occurrence, returning to a normal status and acknowledgment
operation:
• Lock type (Default for high-priority and medium-priority alarms)

• Non-lock type (Default for low-priority alarms)
• Self-acknowledge type (Default for logging alarms and reference alarms)

1. Lock Type
Until the operator performs acknowledgment operation, flashing continues even after
the alarm status returns to normal (NR).
2. Non-Lock Type
Without any acknowledgment operation performed by the operator, flashing stops
when the alarm status returns to normal (NR).
3. Self-Acknowledge Type
The system performs acknowledgment operation automatically upon occurrence of
an alarm. Thus, there is no flashing.
Tag mark Change in indication

Locking Keeps flashing until you acknowledge the alarm even after the alarm
has returned to normal.
Acknowledgement Return to normal
Return to normal Acknowledgement

(Acknowledgement of
alarm occurrence)
Non-locking Turns back to normal color when the alarm returns to normal
irrespective of your acknowledgement.
Acknowledgement Return to normal
Return to normal
Self No flashing and turns to the normal color when the self-
acknowledgement acknowledgement function is activated.
Self-acknowledgement Return to normal
Alarm Dependent Notifies you of return to normal and keeps flashing until you
acknowledge it.
Acknowledgement Return to normal Acknowledgement
Return to normal
(Acknowledgement of
return to normal)

¾ Rewarning
The repeated warning alarm can be issued to remind the user of the occurrence of the
alarm,
The repeated warning alarm reminds the operator of the alarming status still present.
The repeated warning alarms are issued for the process alarms designated as “high
priority alarms.”
If multiple process alarms for which repeated warning alarms can be issued occur in one
function block simultaneously, a repeated warning alarm will be issued only for the
process alarm with the highest priority.
To designate the output interval of the repeated warning alarm, use the FCS
Constant Builder of each control station.
When Repeated Warning Alarm Period is designated as 0, the alarm does not
repeat.
¾ System Recovery Notification Actions (NR)

When the statuses of all alarms in one function block return to normal (NR), flashing
starts to notify the operator of the status change. The actions can be designated only for
high priority alarms. The actions when alarms recover to normal include two types: “Alarm
Occurrence Dependent (Exception Lock)” type and “Non-Lock (Recovery Notification)”
type.
● Dependent on the Alarm in Action (XL: eXeption Lock Type)

When the statuses of all alarms return to normal, the flashing status continue; the
alarms will continue to flash if they were flashing, and they will not flash if they were
not flashing when the statuses of all alarms return to normal.
● Non-Lock Type (System Recovery Type)

When the statuses of all alarms return to normal, the normal display starts to flash.
The occurrence of a new alarm will stop the flashing, even if the new alarm has not
been acknowledged.
The non-lock type notifies the operator that a function block has returned to normal.

D2. Plant Hierarchy Builder

If you need equipment that is specifically designed to meet the unique operating needs of
your plant, you can register the custom equipment using the Plant Hierarchy Builder. The
custom equipment allows for a hierarchical structure that caters to the user’s application
needs.
Up to 1,000 equipment IDs can be assigned for custom equipment. There are no limits on the
number of function blocks and elements to be contained in a single equipment object.
¾ Equipment ID
A unique ID number is assigned for each equipment. The equipment ID range is 1 to 32767
with default and custom equipment combined. The equipment ID is assigned when the
equipment name is specified in the Plant Hierarchy Builder. The equipment ID is added to the
message generated by the FCS as a UAID (User Application ID).
¾ Equipment Name
The equipment name is assigned for each equipment object registered in the plant hierarchy.
The name is specified using up to 16 alphanumeric characters. Make sure no equipment
name conflicts with another within the same project. However, when registering the custom
unit equipment, specify an identical equipment name for both the default and custom unit
equipment.
The following cannot be used as the equipment name:
• ALL
• NONE
• Names that begin with “%DR.”
The following characters cannot be used for the equipment name:
• , (comma)
• @ (at mark)
• * (asterisk)
• : (colon)
• Single-byte space

¾ Comment
The comment can be entered using 12 double-byte characters or 24 single-byte characters.
This comment is not displayed in the operation and monitoring window.
For default equipment, the comment for corresponding equipment is attached as the
equipment comment. For example, the station comment is attached as the station equipment
comment, and the control drawing comment is attached as the control drawing equipment
comment. For custom equipment, the user can freely define a desired comment.
¾ Equipment Format
The equipment format indicates the hierarchical layer in which an equipment object is located.
The following lists the equipment format in descending order of hierarchy:
• Site
• Area
• Cell
• Unit
• Equipment
¾ Upper Equipment Name

The upper equipment name refers to the name of the equipment object located in the next
upper layer of an equipment object in a plant hierarchy. Specifying an upper equipment name
via the Plant Hierarchy Builder determines the location of an equipment object in the plant
hierarchy.
Only custom equipment names can be specified as the upper equipment name.
The upper equipment name is specified using the Plant Equipment Builder.
The upper equipment name can be chosen from a selection of registered names using the
menu area or combo box. The upper equipment name can also be entered using up to 16
single-byte alphanumeric characters.
The following cannot be used as the equipment name:
• ALL
• NONE
• Names that begin with “%DR.”
The following characters cannot be used for the equipment name:

• , (comma)
• @ (at mark)
• * (asterisk)
• : (colon)
• Single-byte space

D3. Engineering Unit Symbol Builder

The engineering unit symbol is a unit symbol attached to a data value including a flowrate and
pressure, and is used on all the projects.
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.
The engineering unit symbol is case-sensitive.
Multiple engineering unit symbols can be defined.
Engineering unit symbols Nos.1 to 8 cannot be changed or deleted.

Define the engineering unit symbol starting at No.9.
Default values are predefined for Nos.9 to 126. No default values are predefined for the
subsequent numbers.
Note that the following characters cannot be used to define the engineering unit symbol:
, (comma), | (pipe), ‘ (single quotation mark), “ (double quotation mark), @, \ ((backslash),
and #

D4. Switch Position Label Builder

The switch position labels refer to character strings displayed as labels for switches on the
switch instruments, the operations, the logic operation blocks, etc.
Up to 64 switch position labels can be defined for one project.
One set consists of four labels (label 1, label 2, label 3, and label 4).
The label 4 character string is not displayed on the instruments with up to three switches.
Define a unique character string for each set.
Switch position labels Nos.1 and 2 cannot be changed or deleted.

Define the switch position label starting at No.3.
Default values are predefined for Nos.3 to 13.No default values are predefined for the
subsequent numbers.
Note that the following characters cannot be used to define the switch position label:
, (comma), | (pipe), ‘ (single quotation mark), “ (double quotation mark), @, \ ((backslash),
and #

The figure is an example of the label for switch position specified

[ON, ,OFF, ON] in direct format.
Label 1
Label 3

D5. Multiple Projects Connection Builder

The Multiple Project Operation and Monitoring allows a project to operate and monitor
another project that has been connected using the Multiple Project Connection.
When multiple projects are connected in the bi-directional format, the projects can operate
and monitor each other.
When projects are connected in the hierarchical structure, the upper project is allowed to
operate and monitor the lower project, but the lower project cannot operate or monitor the
upper project.
The Multiple Project Operation and Monitoring will operate on HISs of the upper and lower
projects for a bi-directional connection, but only on the HIS of the upper project for a
hierarchical connection.
¾ Identical Tag Names

If tag names between integrated projects are identical, a project ID will be added to the tag
name as a suffix in order to avoid identical tag names between projects. Project ID can be
defined in Multiple Projects Connection Builder of the upper project, with two alphanumeric
characters.
Project ID Attachment Format

“Tag Name” + “@” + “Project ID” (a maximum of 16 characters)
(Example) FIC100@P1
A tag can be called without the use of suffixes within the range in which tag names are all
unique. However, suffixes are required if all tag names are not unique. This rule regarding the
tag name call applies to the CS1000/CS3000 system. Examples of tag name calls include
calling instruments and tuning windows in the Operation and Monitoring, and handling tag
names via the Graphic Builder and Trend Collection Pen Assignment Builder in the
Engineering.

¾ Project Name
Define a list of all projects to be connected in the “Projects” tab. Up to 16 projects can be
defined including the current project.
Enter the project name using up to 8 characters.
¾ Alias of Project Name

If there are duplicate project names, enter an alias. Enter the project name set in the
properties of that project as the alias.
¾ Project ID
Enter the project ID using up to 2 characters. The project ID must be unique across all
projects.
¾ Product Name
Select an applicable product name from “CS,” “CS1000,” or “CS3000.”
¾ PC Name
This field is enabled only when “CS 1000” or “CS 3000” is selected in the Product Name.
Enter the computer name of the HIS in which the project is located.
¾ Host Name
This field is enabled only when “CS” is selected in the Product Name. Enter the EWS host
name.
¾ IP Address
This field is enabled only when “CS” is selected in the Product Name. Enter the EWS IP
address.
¾ User Name
This field is enabled only when “CS” is selected in the Product Name. Enter the user name of
the CS Project.
¾ Alias of Host Name

This field is enabled only when “CS” is selected in the Product Name. Enter an alias of the
host name using up to 8 characters when EWS host name conflict with a station name in CS
1000/CS 3000 project.

D6. Operation Mark Builder

To attach or remove a tag mark on a function block may temporarily enable or disable the
operation restriction on the instrument faceplate.
When an operation mark is attached to a function block, a comment label can be added to the
function block or the write access right on the block can be changed temporarily during plant
operation. When the operation mark is removed, the access right returns to the original
setting.
. Tag label
Up to 4 double-byte characters or 8 characters can be entered as the text on the label
(string).
The operation mark label may be temporarily changed during the operation on the HIS Setup
window.
. Color
The following colors may be used on operation marks.
The color of the operation mark may be temporarily changed on the HIS Setup window.

. Tag Level
The write access right on function blocks can be changed.
However, if the security level 1 exerted by operation mark is assigned to a Function Block, the
original function block security setting is intact.
The security levels exerted by operation marks and the types of operation marks are
displayed as follows.
• 1 (Comment type)
Operation can be performed within the security scope defined by the set function
security level of the function block itself.
• 2 (Roles of S2 and S3)

Users of privilege level S2 or S3 can perform operation within their respective
authority (privilege) scope.
• 3 (Role of S3)
Users of privilege level S3 can perform operation within the authority (privilege)
scope.
• 4 (Operation restriction type)

Only alarm acknowledgment can be performed.
•5
The same as 2 (S2, S3 Privileges) above.
•6
The same as 3 (S3 Privilege) above.
• 7, 8
The same as 4 (Operation Guard Type) above.

. Install/Remove
The privilege level required for a user to attach/remove the operation mark.
The relationship between user’s privilege level and the operation on uninstalling/ removing
operation mark authority is shown below:

D7. Station Configuration Viewer

The Station Configuration Viewer displays the overview of the station configured for the
project and a printout can be generated. However, modification to the configuration is not
allowed in this viewer.

D8. Status Change Command Character String Builder

The character strings for user-defined status change commands can be specified in tables of
CUSER1 to CUSER8 in Status Change Command Character String builder.
The user-defined status change command character strings (CUSER1 to CUSER8) can be
used only when they are designated in State Transition Matrix builder.
A character string for a status change command can be defined using up to 8 alphanumeric
characters including underscore ( _ ) started with an alphabet letter. The identical character
strings can not defined in the same table. The reserved strings [RUN], [STOP] and [PAUS]
can not be defined.
The following default character strings for status changes commands can not be changed by
user:
String Number 1 PSTART

String Number 2 STEP
String Number 3 SCOMP
String Number 4 EXECERR
String Number 21 MSTART
String Number 22 ABORT
When character string table CUSER1 is modified, the default State Transition Matrix
(Matrix1) will change its action accordingly.

D9. Security Builder

The security policy is set to prevent illegal operations and other problems and ensuring the
safety of the system.
The security policy restricts the scope of operation and monitoring permitted for an operator,
and masks certain alarms of which the operator need not be notified.
The following two types of policies are available in CS 1000/CS 3000:
• HIS Security Policy

HIS security policy stipulates the scope of operation and monitoring allowed on the
Human Interface Station. Regardless of the logon users, the operation performed to a
device or to a function block data item may be restricted.
• User Security Policy

User security policy stipulates the scope of operation and monitoring for the users.
Each user is restricted to operate or monitor a certain scope of devices and function
block data items.
The scope of operation and monitoring permitted for an operator is determined by a

combination of HIS security and user security settings.
D9.1 User Definition

The operators performing the operation and monitoring functions are classified based on
their privilege level (authority). This classification is called user.

. User Name
Each user name must be unique, consisting of eight alphanumeric characters or fewer
and is not case-sensitive.
Up to 100 users and 250 users can be defined for CS 1000 and CS 3000 systems
respectively.
Up to 32 characters or 16 double-byte characters may be entered as comment for each
user name.
. 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.
15 user groups or 50 user groups may be assigned to one project for CS1000 or CS3000
respectively.
User group may be used to classify the messages sent to different printers.
● Combining Inclusive and Exclusive Definitions

You may combine inclusive and exclusive definitions to specify various scopes. The
following are examples of combination:
• If operation and monitoring are possible at the FCS0101 and FCS0102;

Specify FCS0101 and FCS0102 at the inclusive definition, and NON at the
exclusive definition.
• If operation and monitoring are possible at other stations excluding

FCS0103;
Specify ALL at the inclusive definition and FCS0103 at the exclusive
definition.
• If operation and monitoring are possible at the FCS0101 and FCS0102, but
not at the UNIT A;
Specify FCS0101 and FCS0102 at the inclusive definition and UNITA at the
exclusive definition.

. Privilege Level
The users’ operation and monitoring rights are defined according to privilege levels.
The following default privilege levels are available in HIS.

The three levels are shown as follows:
When the HIS console is connected with an operation keyboard, the privilege level of the
user may be changed temporarily using the mode selection key on the keyboard.
. Automatic User-Out Time

When an automatic user out-time is defined, the user automatically changes to the
OFFUSER when the automatic user-out time elapsed.
The automatic user-out time may be set between 30 minutes to 24 hours.
An example of automatic user-out:

D9.2 Advanced Security Settings

Three default privilege levels, S1, S2 and S3, are provided for the system. The rights
given to S1, S2 and S3 are fixed for the system. It is possible to define up to seven
additional privilege levels, U1 to U7 (user-defined privilege levels)
It is possible to define the following security features for the user-defined privilege levels:
• Window monitoring rights
• Window operation rights
• Whether to display the Tuning and Faceplate windows of a function block
• Whether to allow writing to data items in a function block
• Operation mark security levels
• Operation mark install/remove attributes
• Password control mode
The following tabs constitute the detailed setting items:
• Window Monitoring tab

In this tab whether the windows are displayed or not are specified for each user-defined
privilege level and at each window access level.
With CS 1000/CS 3000 security policy, the operation and monitoring authority can be set
for each window. By setting the operation and monitoring authority on graphic windows,
changing the instrument faceplate assignment or acknowledging of alarm blinking can be
prohibited.
On the Trend Window, the change of trend pens assignment and the start/stop of batch
trends can be prohibited. On the HIS Setup Window, the change of function key
assignment definition can also be prohibited.

The following types of operation and monitoring authorities can be set for windows:
- General window
- Important window
- System operation window
- 4 to 8
> Users of privilege level S1 or S2 cannot start System View from the system
message window, but can start and operate System View from [Start Menu].
> Users of privilege level S1 can operate and monitor general windows. However,
they can only monitor important windows and system operation windows excluding
System View.
> Users of privilege level S2 can operate and monitor general and important windows.
However, they can only monitor system operation windows excluding System View.
> Users of privilege level S3 can operate and monitor all windows.
The following windows are referred to as system operation windows:

- System status overview window
- System alarm window
- FCS status window
- HIS setup window
- System View

• Window Operation tab

In this tab whether the users assigned to each user-defined privilege level and at each
window access level are allowed to operate windows or not is specified.
¾ Batch trend starting and stopping in the Trend window

¾ Starting and stopping of control station and downloading to IOM in the system
maintenance window
• Tag View tab

In this tab whether Tuning and Faceplate windows are displayed or not is specified for
each user-defined privilege level and at each security level of a function block.

• Item Operation tab

In this tab whether the users are allowed to write to data items of a function block or not is
specified for each user-defined privilege level and each data item definition table number.

Example of Setting the Security Level through Advanced Settings

If the privilege level U1 that allows data write to SV of a PID controller block with security
level 5 is to be created, the following definitions should be made in the Item Operation tab
of Security Builder. The data item definition table number for data item SV at security
level 5 is 4. Specify Y for data item definition level 4 of user-defined privilege level U1.
If the definition is made as shown in the figure above, the operation and monitoring
authorities of security level 5 will be as follows:

• Operator Action tab

In this tab the operation rights of a function block is defined for each operation mark
security level and for each user-defined privilege level.
In the case of this example, the users assigned to privilege level U1 are allowed
to write not only to SV but also to all data items with data item definition table
number 4.
• Operation-mark On tab
In this tab whether the operation marks can be installed or removed is defined for each
user-defined privilege level and for each operation mark installing/removal attribute.

• Password tab
In this tab the password control mode for an operator to logon to the HIS is defined.
There are two modes for controlling passwords: Local control and Common control.
When the control mode is switched from Local to Common, all passwords are
initialized (deleted). Therefore, you need to register the passwords again in
this case.
When the password control mode is set to 0, the passwords of each HIS are controlled
individually. When the password control mode is set to 1, the passwords of all HISs are
controlled comprehensively. The default control mode is 0(Local password control).
• Invalid User tab

In the case that the Access Administrator Package (FDA:21 CFR Part11 compliant) is
installed and a registered user is deleted, the user is deleted from the Valid User tab and
moved to the Invalid User tab. In this tab, there is no item to be defined by a user.
D9.3 Security Level

An attribute called “security level” is assigned to the function blocks.
The security policy is set to prevent illegal operations and other problems and ensuring
the safety of the system.
The security policy restricts the scope of operation and monitoring permitted for an
operator, and masks certain alarms of which the operator need not be notified.
Each tag is assigned with a function block security level in the Function Block Detail
Builder. Based on the User Security type of the username and the assigned function
block security level, the restriction of monitoring and operation is imposed on the function
block faceplate.

9.3.1 Data Item Definition Table Numbers

Data item definition table number indicates the security level regarding data write and
read of a function block by a number between 1 and 8.
A data item definition table number defines whether write and read of data items are
allowed or not for each privilege level, as shown in the table below.
Whether writing is allowed or not for the user-defined privilege levels (U1 to U7) can
be changed. The table below shows the default settings for the user-defined privilege
levels.
A data item definition table number has been assigned for each function block
security level and for data item classification categorized according to function
and purpose. This assignment cannot be changed.
For example, rights to read and write SV of a PID controller block with security level 4
can be determined from data item definition table number 2. This means that users
with S1 rights cannot write data to SV, but users with S2 or S3 rights can write data to
SV.

The following tables show the operation and monitoring rights for each security level.
The default settings are shown for the user-defined privilege levels (U1 to U7).



D10. Exercise
Set the following in the project [TRAIN3]:
1. Configure the following:
Tag Label Color Tag

Level
Caution Red 1
Calibrat Blue 2
Maint White 3
Service Cyan 4
No touch Green 5
Assign these operation marks to a tag in the tuning panel and examine its effect on the
tag security in operation and monitoring.
2. Configure the following Operation Mark:
Label: ENGUSR
Color: Violet
Tag Level: 3
Install/ Remove: 3
Such that in the operation mode, it can only be assigned by an ENGUSER.
3. Create the following user functions:
Username Usergroup Privilege Comment

Levels
Mathew JOPR S1 Junior
Operator
Mark JOPR S1 Junior
Operator
Luke SOPR S2 Senior
Operator
John ENGR S3 Engineer
In the HIS System Message area, log in using the different user names created
above and take note of the different access level of each user when Control Group
window [SECURITY] is called up.
4. Configure the following Advanced Security Settings for U1:
Tag View Item

Operation
U1 Y N
5. Create the following user with U1 as privilege level:
Username Usergroup Privilege Comment

Levels
Peter ADMIN U1 Special
In the HIS System Message area, log in as Peter and note the monitoring and access
level on the different tags in Control Group window [SECURITY].

E1. FIO SYSTEM OVERVIEW
E1. FIO System Overview

The FIO is an I/O system that is connected to a control station via an ESB (Extended Serial
Backboard) bus.
A maximum of 10 Node Units (Node Unit for ESB Bus and Node Unit for ER (Enhanced
Remote) Bus) can be connected to the ESB bus.
ESB Bus Node Units are called “Local Nodes,” whereas ER Bus Node Units are called
“Remote Nodes.”
A Node Unit consists of a Base Unit, Power Supply Modules, either ESB Bus Interface
Modules (SB401) or ER Bus Interface Modules (EB501), and I/O Modules (FIO).
Node units (sometimes simply called nodes) are signal processing devices that convert
process input/output signals to or from the field equipment and transmit them to the field
control unit (FCU).
The Remote Nodes can be connected by installation of ER Bus Interface Master Modules
(EB401) in a Local Node. A maximum of eight Remote Nodes can be connected per Field
Control Unit (FCU).
The correspondence between bus interface modules and device types are as follows.
• SB401: ESB bus slave interface module (installed in ANB10S/ANB10D)
• EB401: ER bus master interface module (installed in ANB10S/ANB10D)
• EB501: ER bus slave interface module (installed in ANR10S/ANR10D)
YOKOGAWA SINGAPORE TRAINING CENTRE Page E1-1 of E1-5

• Cabinet Installation Type Node Unit
Slot Names of Node Unit

The slots in a node unit are named according to their positions shown as follows.
The figure below shows the slot names and installable modules.
• For the single node unit, the SB401 or EB501 is installed to B1. For dual-
redundant node unit, the SB401 or EB501 for bus 1 is installed in B1 and the
SB401 or EB501 for bus 2 is installed in B2.
• EB401 can be installed to slot IO1 to IO8.
• The slot can be identified by the characters screen-printed on the
backboard (printboard). However, the characters can not be seen after the
I/O modules are installed.
B1 indicates the slot is for bus 1 while B2 for bus 2.

E1.1 ESB Bus and ER Bus

The ESB bus (Extended Serial Backboard bus) is a communication bus used in
connecting the local nodes, which are installed in the same cabinet for FCU, with the
FCU.
This bus can be dual-redundant.
Maximum transmission distance is 10 meters.
The ER bus (Enhanced Remote bus) is a communication bus used in connecting the
remote nodes with the FCU by way of the ER bus interface module installed on the local
node.
This bus can also be dual-redundant. Using this bus, the nodes can be installed in the
same cabinet for FCU or at locations away from the cabinet.
Its maximum transmission distance is 185 meters using a Ethernet-compatible 10-Base-2
coaxial cable or 500 meters using a 10-Base-5 coaxial cable, or up to 2 kilometers using
general-purpose optical bus repeaters.

E1.2 System Configuration

FIO is an I/O system connected to a control station via an ESB bus, consisting of two
types of node units on two types of buses: node units on an ESB bus referred to as local
nodes, and those on an ER bus referred to as remote nodes.

E1.3 Network Specifications

The ESB bus connects the processing unit of an FCS to node units, which are thus called
Local Node units.
The ER bus connects a node unit that is directly connected to an FCS’s processing unit
via ESB bus, to remote node units.
ESB Bus ER Bus

Network Topology Bus Type Bus Type
Transmission Path Redundancy Available Available
Transmission Speed 128 Mbps 10 Mbps
Transmission Distance Maximum 10 m Maximum 185m (YCB141)
Maximum 500m (YCB311)
Maximum 2 km (Using
Ethernet repeaters - Can
use 2 (a set of) Ethernet
repeaters per ER bus)
Connectable Devices Local node units Max. 4 remote node units
per FCU
The number of local node units that can be connected to an ESB bus varies according to
models and databases selected.
Model Maximum Number of Local Total Number of Local

Nodes and Remote Node
Units (*1)
Compact-type FCS (for 3 3
FIO) (*2)
Enhanced FCS with 10 15
expanded databases
Other than the above 10 10
*1: The total number of remote and local nodes should not exceed this number.
*2: If local and remote node units are used, ESB Bus Coupler module (EC401) should
be installed in slot 7 and slot 8 and also Node Expansion Package for Compact Field
Control Unit (for FIO) is needed.
The number of local node units that can be connected to an ER bus varies according to
models and databases selected.
Model Maximum Number of Local Total Number of Local

Nodes and Remote Node
Units (*1)
Compact-type FCS (for 3 3
FIO) (*2)
Enhanced FCS with 14 (*3) 15
expanded databases
Other than the above 9 (*3) 10
*1: The total number of remote and local nodes should not exceed this number.
*2: If local and remote node units are used, ESB Bus Coupler module (EC401) should
be installed in slot 7 and slot 8 and also Node Expansion Package for Compact Field
Control Unit (for FIO) is needed.
*3: Up to 8 remote nodes per ER bus can be connected.


E2. FIO SYSTEM OVERVIEW (VNET/IP)
Open
E2. FIO System Overview (Vnet/IP) Reliable

Real-
time
Vnet/IP is a control network with high reliability and quick response and achieves steady
response with little delay even under heavy load. Using general-purpose network equipment
conforming to IEEE802.3 and UDP/IP standards, it realizes open-based communications.
Vnet/IP can connect to a Vnet system with a Vnet router.
FFCS-L field control unit is a model of CENTUM CS 3000 field control station (model name:
AFV10S/AFV10D) that applies Vnet/IP to the control bus.
With one FFCS-L field control unit, up to I/O 14 nodes can be connected. The cables of the
Vnet/IP control bus should be the enhanced Category 5 UTP cables, hereinafter, referred to
as CAT5e cables.

E2.1 Network Specifications

An ESB bus is an I/O communications bus that connects the processing unit of an FCS to
a local node.
An ER bus is a remote I/O communications bus to connect an FCU or local node unit to a
remote node.
ESB Bus ER Bus

Network Topology Bus Formation Bus Formation
Transmission Path Redundancy Available Available
Transmission Speed 128 Mbps 10 Mbps
Transmission Distance Maximum 10 m Maximum 185m (YCB141)
Maximum 500m (YCB311)
Maximum 2 km (Using
Ethernet repeaters - Can
use 2 (a set of) Ethernet
repeaters per ER bus)
Connectable Devices Local node units Max. 4 remote node units
per FCU
The number of local node units that can be connected to an ESB bus varies according to
the database selected.
Database Maximum Number of Local Total Number of Local

Nodes and Remote Nodes (*1)
Control Function for 3 3
Standard Field Control
Unit
Unit plus Application
Capacity Expansion
Package
*1: The total should not exceed this number

*2: If local node units are connected to an AFV10S or AFV10D FCU, ESB Bus
Coupler Modules (EC401) should be installed in slots 7 and 8.
The number of remote node units that can be connected to an ER bus varies according to
the model and database selected.
Database Maximum Number of Total Number of Local

Remote Nodes and Remote Nodes (*1)
Unit
Unit plus Application
Capacity Expansion
Package
*1: The total should not exceed this number

*2: Up to eight remote nodes per ER bus can be connected.

E2.2 Connection 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.
E2.2.1 Connection between Vnet/IP and Vnet 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.
E2.2.2 Connection between Vnet/IP and VLnet 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 CS 3000 project, and VL net will be a 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.

E2.2.3 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).
E2.2.4 Connection with Vnet Domains of Revisions R3.04 or Earlier

To connect with V net domains of Revisions 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
R3.04 or earlier has the following restrictions. However, the HIS function on the
Vnet/IP side has no restrictions.
• 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.

F1. LFCS CONFIGURATION
F1. LFCS Configuration

With the release of Centum CS 3000 R3, new FCSs are now available. In this chapter, FCS
Configuration for LFCS (Field Control Station) is explained.
F1.1 LFCS Property - Constant

In System View, right click on [FCS0101] [Properties] View [Constant].
F1.1.1 Fast Scan/ Medium-Speed Scan Period

Scan period determines a period for the periodic execution of the function block.
Individual scan period can be defined in each function block based on the required
response time.
Basic scan : 1 second (fixed)

Medium-Speed scan : 50 ms, 100 ms, 200 ms or 500 ms. (50ms or 100ms
may be specified with keystrokes.)
Default is 500 ms. (Available for CS 3000 only)
High-Speed scan : 50 ms, 100 ms, 200 ms or 500 ms. (50ms or 100ms
Default is 200 ms.
YOKOGAWA SINGAPORE TRAINING CENTRE Page F1-1 of F1-21

F1.1.2 Pulse Width and Serial Startup Interval for MC Instrument

Block
The settings related to motor control blocks (MC-2 and MC-3) may be set.
The time of ON for contact output for the converted signal of “2-position Pulsive
Output ” or “3-position Pulsive Output ” may be defined in each FCS.
Pulse Width: 1 to 100 Sec. (The default setting is 1 second.)
The serial start function puts the motor control blocks (MC-2, MC-3) of the same
control station into groups and starts multiple motor control blocks (MC-2, MC-3) in
the same group sequentially at a specified interval when start requests are issued to
these blocks simultaneously.
Serial start interval: 0 to 9999 seconds. (The default setting is 0 second.)
F1.1.3 MLD-SW Block AUT/CAS
MLD-SW is a Manual Loader Block with Auto/Man SW to manually operate final

control elements such as control valves. As the lowest downstream block in the
control loops that consist of multiple function blocks, the mode of the block may be
set as CAS or AUT.
Whether to set the cascade (CAS)mode or automatic (AUT)block mode for outputting
the result obtained by control computation processing of the value input from other
function block,may be selected for each control station on the property setting box of
the FCS:
MLD-SW AUT/CAS: Check “CAS” or “AUT.” (The default setting is [AUT].)
F1.1.4 SEBOL statement
The “drive” statement executes the output operation with respect to the motor control
block or switch instrument block and waits until the function block completes an
answer back check.
This check to see if output and operation with respect to the function blocks, are
possible according to the block mode and action type. There are three action types as
shown below:
Table Action Type of the “drive” Statement
For more detailed information, please refer to SEBOL (IM 33S01B30-01E) Page 110
onwards.

F1.1.5 User-Defined block

When using the blocks with user-defined data items (SFC block, unit instrument), a
specific area needs to be specified.
[Number of Block Type] displays the allowed number of block types for the current
type of FCS database.
[Block-type start number] may be set with reference of the [Number of Block Type].
For example, if the allowed number of block types is 20 for both FCS0101 and
FCS0102, and the [Block-type start number] for FCS0101 is set to 0, the areas from 0
to 19 is reserved for FCS0101. Thus, the [Block-type start number] for FCS0102, may
be set to 20 or greater.
F1.1.6 IOM Online Updating

When downloading to an I/O module, the behavior of function blocks connected to the
module may be specified as IOP (input open) or not.
F1.1.7 Options
When using option programs, the programs need to be registered on the FCS
properties\setting box.
Select an option program then click [Add] button to register the program
. OFFSITE (Offsite block) (*1)

. VPMON (Valve pattern monitor) (*1)
. GC1000 (Communicating with Gas chromatography) (*2)
. MELSEC_E (MELSEC-A Ethernet) (*3)
. ZACMWDPX (For dual-redundant configuration communication modules) (*4)

F1.1.8 PID Pulse Width Output

If no feedback is set, the MV displays in the following two styles at the AUT mode:
• Hold Previous MV
When no pulse is output (or the output pulse width smaller than threshold), the
displayed MV keeps the previous MV. When pulse output restarts, if the restarted
output is in the same direction of the previous output, the displayed MV equals to
the previous MV plus the _MV for increment or previous MV minus the _MV for
decrement. However, if the restarted output is in reversed direction, the displayed
MV equals to 50% plus or minus the _MV for increment or decrement.
• Display 50% MV (CENTUM-V Compatible)

displayed MV returns to 50%. When pulse output restarts, the displayed MV
equals to the 50% plus the _MV for increment or 50% minus the _MV for
decrement. Whenever the _MV reverses from positive to negative or vice versa,
the displayed MV returns to 50% then plus or minus the _MV for increment or
decrement respectively.
The MV display style when no feedback for pulse width output and the block is at
AUT mode can be set on FCS properties sheet. Check the check box of [CENTUM-V
compatible MV Display] in the column of [PID Pulse Width Output]. When this option
is checked, the displayed MV returns to 50% when no pulse is output. Otherwise, the
displayed MV keeps the previous MV. This check box is unchecked by default.
F1.1.9 PI-HLD Action after Hold

When PI-HLD starts the control calculation after its Hold period elapsed, the previous
process variable is used as the PVn-1 in proportional term computation, and the
following two methods can be selected:
• Use the PV right before the Hold status as the PVn-1

• Use the current PV as the PVn-1 (Same as the PI-HLD in CENTUM-XL)
The two calculation methods can be selected on FCS properties sheet. Check the
check box of [CENTUM-XL compatible] in the column of [PI-HLD Control Action after
Hold]. When this option is checked, the PVn-1 in the control algorithm uses the
current process variable PVn. Otherwise; the PVn-1 in the control algorithm uses the
process variable right before the Hold started. By default, [CENTUM-XL compatible]
is not checked.
F1.1.10 Sequence Table Algorithm

When the check box of [CENTUM-XL Compatible Sequence Tables] in the
[Sequence Table Algorithm] setting area of [Constant] tab on FCS Properties sheet is
checked (*1), if the step00 exists in the same table of the execution step, both the
step00 and the execution step will be activated at the same time after the condition
testing. If the table is expanded to another table and the execution step is on the
expansion table, the condition of the step00 will be tested first and then the action of
the step00 will be activated before testing and activating the execution step.
However, if the check box of [CENTUM-XL Compatible Sequence Tables] is not
checked, the condition of the step00 will be tested first and then the action of the
stepp00 will be activated before testing and activating the execution step even when
the sequence table is not expanded.
By default, this check box is not checked.

When the check box of [THEN/ELSE Has Higher Precedence] in the [Sequence
Table Algorithm] setting area of [Constant] tab on FCS Properties sheet is checked
(*1), if the next step is directed by THEN/ELSE, the next step directed in the action
rule will be ignored. However, if the next step is not directed by THEN/ELSE, the next
step directed in the action rule will be activated. Vice versa, when the check box of
[THEN/ ELSE Has higher Precedence] is not checked, the next step directed in the
action rule will be activated and the next step directed by THEN/ELSE will be ignored.
*1: The check boxes of [CENTUM-XL Compatible Sequence Tables] and [THEN/ELSE Has Higher
Precedence] are available in the [Sequence Table Algorithm] setting area of Constant tab on FCS
Properties sheet of KFCS2, FFCS, FFCS-L and LFCS2 only.
F1.1.11 dPV/dCPV Output from SUB Becomes Zero Right After IOP
Auxiliary Output (_PV) When PV Data Status is BAD: KFCS2/FFCS/FFCS-L

LFCS2
According to the [PV Overshoot] setting of the Regulatory Controller Block set on the
Function Block Detail Builder, the PV will overshoot when the data status becomes
bad (BAD). Under such circumstance, the _PV output from the SUB terminal can be
set to output either 0 or the actual delta PV i.e. the increment or decrement between
the current scan PV and the previous-scan PV.
For the DPV output, an option [dPV/dCPV Output from SUB Becomes Zero Right
After IOP] can be checked on FCS Properties sheet. When the option is checked, the
DPV output becomes 0 immediately after IOP. Otherwise, the actual DPV will be
output from the SUB terminal. By default, this option is not checked.
Auxiliary Output (_CPV) When CPV Data Status is Bad : KFCS2/FFCS/

LFCS2
Function Block Detail Builder, when the data status becomes bad (BAD), the _CPV
output from the SUB terminal can be set to output either 0 or the actual delta CPV i.e.
the increment or decrement between the current-scan CPV and the previous-scan
CPV.
For the DCPV output from SUB terminal, an option [dPV/dCPV Output from SUB
Becomes
Zero Right After IOP] can be checked on FCS Properties sheet. When the option is
checked, the DCPV output from SUB becomes 0 immediately after IOP. Otherwise,
the actual DCPV will be output from the SUB terminal. By default, this option is not
checked.
However, for the calculation block that the setting item [Calculated Input Value Error
Detected] is specified for no reaction on the error, the DCPV output terminal will be
the actual delta CPV value in accordance with the [PV Overshoot] setting even if the
option [dPV/dCPV Output from SUB Becomes Zero Right After IOP] is checked.

F1.1.12 Accept Batch-End during EMST

The following section explains the basic operation of the Totalizing Batch Set Blocks
at each control step (ZONE):
1. ZONE10: Batch start (Block status: STRT)

Sets data to the set parameters including batch setpoint (BSET) prior to
batch start. If the command switch is set to start (SW=1) while in the
automatic (AUT) block mode, the current control step moves to ZONE10 and
the block starts batch operation after resetting the totalized value (SUM) to 0.
Once batch starts, the control step moves to ZONE1.
2. ZONE1: Initial batch (Block status: IBCH)

After batch start, outputs the low flowrate setpoint (ML) as the manipulated
output value (MV) until the totalized value (SUM) reaches the initial forecast
value (ILST). The output velocity limiter does not operate. When the totalized
value (SUM) exceeds ILST, the control step moves to ZONE2.
The “low flowrate setpoint (ML)” and “initial forecast value (ILST)” are set
from the operation and monitoring functions as set parameters.
• Low flowrate setpoint (ML):

Set engineering unit data within the manipulated output value (MV) scale
range.
The default is the manipulated output value (MV) scale’s low limit.
• Initial forecast value (ILST):

Set data in the same unit as the totalized value (SUM).
The default is 0.
The set value consists of 8 digits or less.
3. ZONE2: Setup (Block status: STUP)

Changes the manipulated output value (MV) to the high flowrate setpoint
(MH) value during the Ramp Up time (TU). The high flowrate setpoint (MH) is
an output value in a steady state.
When the set TU time elapses in the setup mode, the control step moves to
ZONE3.
The “high flowrate setpoint (MH)” and “Ramp Up time (TU)” are set from the
operation and monitoring functions as set parameters.
• High flowrate setpoint (MH):

range.
• Ramp Up time (TU):

Set a value between 0 and 10000 seconds.
The default is 0 second.
4. ZONE3: Steady (Block status: STDY)

Outputs the high flowrate setpoint (MH) as the manipulated output value
(MV). When the totalized value (SUM) reaches the value of batch setpoint
(BSET) less pre-batch setpoint (PLST), the control step moves to ZONE4.
The “batch setpoint (BSET)” and “pre-batch setpoint (PLST)” are set from the

• Batch setpoint (BSET): Set data in the same unit as the totalized value
(SUM).
The default is 0.
Specify a numeric value consisting of 8 digits or less.
• Pre-batch setpoint (PLST): Set data in the same unit as the totalized value
(SUM).
The default is 0.
5. ZONE4: Early (Block status: ERLY)

In the course of Ramp Down time (TD), the manipulated output value (MV) is
changed to PRE (pre-batch flowrate setpoint) on the gradient that leads to
the low-flowrate setpoint (ML). When the manipulated output value (MV)
becomes the same value as the pre-batch flowrate setpoint (PRE), the
control step moves to ZONE5.
The “pre-batch flowrate setpoint (PRE)” and “Ramp Down time (TD)” are set
• Pre-batch flowrate setpoint (PRE):

Set engineering unit data within the MV scale range.
• Ramp Down time (TD):

6. ZONE5: Pre-batch (Block status: PBCH)

Outputs the pre-batch flowrate setpoint (PRE) as the manipulated output
value (MV).
When the totalized value (SUM) reaches the value of batch setpoint (BSET)
less leakage predictive value (LPV), the control step moves to ZONE7.
The “leakage predictive value (LPV)” is set from the operation and monitoring
functions as a set parameter.
• Leakage predictive value (LPV):

The default is 0.
Specify a numeric value of 4 digits or less.
7. ZONE7: Batch end (Block status: END)

Batch operation ends after the manipulated output value (MV) is reset to “0.”
When the batch end wait time (TW) elapses in the batch end mode, the block
mode changes to manual (MAN) and the control step moves to ZONE0. At
this time, the totalized value
(SUM) is added to the cumulative totalized value (SUM1). However, this
addition will not take place in the manual (MAN) mode.
The “batch end wait time (TW)” is set from the operation and monitoring
• Batch end wait time (TW): Set a value between 0 and 10000 seconds.
8. ZONE0: Batch operation stop (Block status: NCNT)

In this mode, batch Control Action stops and a manually manipulated variable
can be output.

9. ZONE6: Reset (Block status: RSET)

When the command switch is set to Abort (SW=3) during batch operation, the
control step moves to ZONE6 and the manipulated output value (MV) is
brought down to 0 % at a speed of changing it from the high flowrate setpoint
(MH) to low flowrate setpoint (ML) over the Ramp Down time (TD).
When the manipulated output value reaches 0 %, the control step moves to
ZONE7.
When the totalized value exceeds the value of batch setpoint (BSET) less
leakage predictive value (LPV), the status changes to batch end and
generates an alarm (BEND). The batch ends other than this way does not
generate batch end alarm (BEND).
10. ZONE8: Emergency stop (Block status: EMST)

When the emergency command switch is set to emergency stop (EMSW=1),
or when the command switch is set to emergency stop (SW=4), the control
step moves to ZONE8, and the manipulated output value (MV) is brought
down to 0 % at a speed of changing it from the high flowrate setpoint (MH) to
low flowrate setpoint (ML) over TD (Ramp Down time). When the
manipulated output value (MV) reaches 0 %, the control step moves to
ZONE9.
Even when the block is in Emergency Stop (EMST) status, if the totalized
value (SUM) reaches the batch setpoint (BSET) Value minus the leakage
predictive value (LPV), the control step may shift to ZONE7. However, this
behavior is alternative by changing the setting of [Accept Batch-End during
EMST] on the FCS properties sheet. By default, this check box is checked.
11. ZONE9: Emergency stop complete (Block status: EEMS)

less leakage predictive value (LPV) during emergency stop, the control step
moves to ZONE7.
However, if the option of [Accept Batch-End during EMST] on the FCS
properties sheet is not checked, it will not move to ZONE7 but stays in
ZONE9.
12. ZONE11: Restart (Block status: RSTR)

When the command switch is set to restart (SW=2) during the emergency
stop complete mode (ZONE9), the control stop moves to ZONE2 via
ZONE11.

F1.2 LFCS Property – Constant 2

In System View, right click on [FCS0101] [Properties] View [Constant 2].
F1.2.1 SS-DUAL PV Update during Deviation Alarm

When SS-DUAL block signal selector switch is at the position 3, both input1 and
input2 will be monitored. If one of them is not normal, the switch will select the normal
side input. If a deviation alarm occurs, to update PV or to hold the current PV can be
set by checking this option.
When checking the option box for [SS-DUAL PV Update During Deviation Alarm], if a
deviation alarm occurs when the switch position is 3, the data status of PV will
become BAD but the PV itself will continue to update vary with the selected input
signal.
The default setting does not check this option, so that when a deviation alarm occurs,
The SS-DUAL will hold its current PV.

F1.2.2 Alarm Notify Action when All AOF Released

When alarm inhibition (AOF) of all function blocks are released, if the existing alarm
gives an output or not can be specified by checking this option box.
When checking [Alarm Notify Action When All AOF Released] option box, all the
existing alarms will output when their inhibitions (AOF) are released all together.
By default setting, this option box is not checked, so that the existing alarms will not
output when AOF released.
F1.2.3 Specify Reference Station for Tag List
The tag list of a designated station can be referenced when checking this option box.
After checking [Specify Reference Station for Tag List] option box, designating a
station for referencing the tag list will be enabled. When this option is not checked,
the stations start from smallest domain number and the smallest station number will
be listed in ascending order and set as the default stations for referencing tag list.
F1.2.4 Annunciator Message with Data

Annunciator Message Head Number
When an annunciator is initiated, the data assigned for the annunciator can be
referenced for the printing message.
The annunciators from the designated annunciator head number will correspond one
by one to the printing messages from the designated printing message head number.
Printing Message Head Number

When the setting for annunciator message head number or for printing message
head number is not correct, an error will be displayed in the dialog box and the setting
will become invalid.

F1.2.5 Increase Number of System Common Switches

Common switches are internal switches used by various control functions to save the
shared logical values in an FCS.
The logical value of a common switch is not directly output to an external FCS, but is
used by various control functions in an FCS for condition testing and status
manipulation.
Common switches with element number %SW0001 to %SW0400 are fixed as system
switches. However, if the number of system common switches is not increased, the
element numbers of the system common switches are from %SW0001 to %SW0200
(*1).They are used to indicate the different statuses of the FCS. Only a few of
switches can be defined by users.
Common switches in the CS 3000 with element number %SW0401 to %SW4000 (If
the number of system common switches is not increased, %SW0201 to %SW4000)
may be freely defined by users.
*1: • The number of system common switches of SFCS is fixed between %SW0001 and
%SW0200. The user-definable common switches are from %SW0201 to %SW4000.
• The number of system common switches of PFCS is fixed between %SW0001 and
%SW0200. The user –definable common switches are from %SW0201 to %SW1000.
Changing the number of system common switches can be performed on FCS

properties sheet (*2) by checking the option box [Increase Number of System
Common Switches]. By default setting, this option is checked.
*2: The option for increasing the number of system common switches is not available for SFCS
and PFCS.
F1.2.6 Preset MV Valid Immediately:

Preset MV Valid immediately setting for a regulatory control blocks has two options,
[Preset MV valid by Preset Switch] and [Preset MV valid at next scan]. When a preset
MV switch (PSW) is activated by an external command such as from a sequence
control block, the preset MV can be output immediately.
For pulse width output, [Preset MV valid immediately] Option cannot be set to
[Preset MV valid immediately] .
Preset MV valid timing can be specified on FCS properties sheet. When checking the
option of [Preset MV valid by Preset Switch] , the preset MV will be immediately
forced to the MV output instead of waiting for the next scan; while when checking the
option of [Preset MV valid at next scan], the preset MV will be forced to the MV output
at the next scan. The Default is [Preset MV valid at next scan].

F1.3 LFCS Property – State Transition

In System View, right click on [FCS0101] [Properties] View [State Transition].
F1.3.1 State Transition Matrix

When the FCS database is a type of database for unit configuration, state transition
matrix can be defined.
Maximum Specification Number

Indicates the total number of state transition matrixes. This is only an indication and
cannot be edited.
Designating a State Transition Matrix

In the matrix list, the matrixes registered in the project as well as the matrixes
removed from the project but had been registered as the state transition matrix before
removal are available for selection. If choose a matrix already removed from the
project as the state transition matrix, an error will occur.

F1.4 LFCS Property – Line 1

In System View, right click on [FCS0101] [Properties] View [Line 1].
F1.4.1 Make RIO Bus Dual Redundant
The RIO bus dual-redundant configuration may be specified even for single CPU
FCS.
In RIO bus Dual-Redundant Configuration RIO buses is usually alternatively used. If
an error occurs in one bus, the other bus will be used for communication. Error
recovery in the buses will be monitored periodically.
F1.4.2 Repeater Connection
Allowed transmission distance of the RIO bus may be extended by connecting a bus
repeater.
Specify whether to connect a bus repeater to the RIO bus.

F1.5 LFCS Property - Network

In System View, right click on [FCS0101] [Properties] View [Network].

F1.5.1 VLnet TCP/IP Settings, V net TCP/IP Settings

Normally there is no need to change the TCP/IP protocol setting for the control
bus.
Control Bus IP Address

The IP addresses on the control bus are used to logically identify the HIS for
communication among HISs on the control bus.
The bus type, domain number and station number of an IP address on the control bus
is automatically determined. In normal situation, the automatically determined setting
should be used.
Control Bus Subnet Mask

The control bus subnet mask is set to “255.255.0.0” as the default setting. In normal
situations, this default setting should be used.
F1.6 LFCS Station Definition

F1.6.1 Definitions
“FCS start operation” refers to all the actions performed through the process of FCS’s
changing its status from operation stop status to normal operation status.
It includes “Initial cold start” and “Restart.”
Which operation to be performed is determined by “Cause of start,” “Start condition,”
and “Power failure time and Momentary Power Failure tolerant time.”
Start condition

The start condition determines which method to be used, initial cold start or restart, to
initiate the FCU, upon turning on the power to FCU which was in the power shutoff
status.
FCS performs either initial cold start or restart according to the specified start
condition.
The default is “MAN (Initial Cold Start).”
When the FCS in station STOP status executes the start operation, the initial cold
start must be executed regardless of start condition.
Momentary Power Failure Tolerant Time

When “TIME” is selected as the start condition, “Momentary Power Failure Tolerant
Time” should be specified.
“Momentary Power Failure Tolerant Time” is a definition item used to determine the
type of start operation based on the power failure time.
. Momentary Power Failure Tolerant Time: Set 0.0 to 4.0 (sec).
(The default is 2.0 sec.)

Node Momentary Power Failure Tolerant Time

Two types of start operation–“initial cold start” and “restart”–are available for the
nodes (local node and remote node). These two types of start operation are executed
when a node that is not responding is recovered after the occurrence of an error. The
type of start operation to be executed is determined by the duration the node does
not respond.
“Momentary power failure tolerant time” can be set in the range between 0 and 4
seconds. If 0 is set, the start operation of the node is always set to the “initial cold
start.” The default value is 2 seconds.
When the no-response time of the node is longer than the “momentary power failure
tolerant time,” it is called prolonged node power failure.
When the no-response time of the node is shorter than the “momentary power failure
tolerant time,” it is called momentary node power failure.
For more detailed information, please refer to Field Control Station Basics
(IM 33S01B30-01E) Page 209 onwards.
Digital Filter
The digital filter is a function to remove the noises from process input signals.
The following is the computational expression for the digital filter:
Shown below is the step response of digital filtering process.

There are three kinds of digital filter coefficients:
. Digital Filter Coefficient 1: 0 to 1.00 (0.01 unit)

The defaults for these digital filter coefficients are set to the values indicated below:
• Digital Filter Coefficient 1: 0.5

(When the digital filter coefficient is 0.5 and scan period is 1 second, the time
constant\is 1 second)

constant is 3 seconds)


F1.6.2 Scan Transmission
To transfer/receive the values of global switches between stations.
Self Station
Define the communication buffer size to transfer the values of global switches
assigned to the present station to other stations.
. Buffer Size: Define 32 (bytes) to transfer the values, or 0 not to transfer them.
(The default is 0.)
Station Scan Transmission

Define whether to receive the values of global switches from other stations.
. Station: Choose “0: No Scan Transmission,” or

“1: Internal Station Scan Transmission.”
(The default is 0.)
When you choose “Internal Station Scan Transmission,” define the communication
buffer size to receive data from its station.
. Individual Station Definition (stations 1 to 64):

Define 32 (bytes) (same value as the buffer size of the present station defined at
the sending station) to receive data, or 0 not to receive data.

F1.6.3 Detailed Settings
Wind Up Time
Windup operation is a preparatory processing for organizing time-series data that are
required for control operations. The function block’s input processing, control
processing, calculation processing and alarm processing executed during windup
operation are executed in the same manner as in normal operation. All output signal
processing, except for the one that outputs control output signals to the process
output terminal, are executed in the same manner as in normal operation.
Sequence table blocks and logic chart blocks don’t operate while windup operation is
running.
. Wind Up Time: Set 0 to 100 (sec.).

(Default is 60 sec.)
SEBOL/User C Ratio
The setting of the processing executed in the idle time in FCS’s CPU is defined in
“SEBOL/User C time ratio” on the FCS Constants Builder. This time ratio is set as
“100 %” as default, means the total idle time of FCS’s CPU is used by SEBOL.
Interval of Repeated Warning Alarms

The repeated warning alarm retransmits a process alarm message to notify the
operator that a critical alarm status is continuing.
Only the high-priority alarm can be reissued as repeated warning alarm. If the
definition item of repeated warning alarm cycle is defined as zero second, repeated
warning alarm does not effect.
. Repeated warning alarm period: The setting value is between 0 to 3600
seconds. When 0 is set, repeated warning alarm function is disabled. Default is
600 seconds
Alarm Mask for Initial Cold Start

The repeated warning alarm has a function in which at initial cold start (include
recovery from a long period of power failure) of the FCS, only the high-priority alarms
are picked up from all the alarms and issued to the operation and monitoring
consoles.
With mask: Only the alarms that were newly activated and high priority alarms will
issue the alarm messages when the FCS initiates cold start.
Without mask: Every alarm that is in progress will be classified as newly activated,
and the process alarm messages will be issued at initial cold start.
Inter-Station Data Link Communication Period

The inter-station communication period is a time required to complete all inter-station
data link processing within a FCS. The default is one second.
The number of inter-station communications points, C, executed in one second is

shown below:
C = (Effective inter-station data link points)

(Inter-station communication period)
The effective inter-station data link points are the points of the inter-station data link
actually wired in Control Drawing Builder or in Function Block Detail Builder or in
Function Block Overview Builder within each FCS.
Re-Transmission Skip when Inter-Station Data Link Error

When a communication error is detected during inter-station data link processing,
inter-station communication transmission skips for a period of time then retry the
transmission in the interval of this skip period. This re-transmission skip period is
expressed as follows:
Re-transmission skip period =

(Inter-station communication period) • (re-transmission skip times)
Default for the re-transmission skip times is 60.


F2. KFCS CONFIGURATION
F2. KFCS Configuration

With the release of Centum CS 3000 R3, new FCSs are now available. In this chapter, FCS
Configuration for KFCS (Field Control Station) is explained.
F2.1 KFCS Property - Constant

In System View, right click on [FCS0101] [Properties] View [Constant].
F2.1.1 Fast Scan/ Medium-Speed Scan Period

Individual scan period can be defined in each function block based on the required
response time.
Basic scan : 1 second (fixed)

Medium-Speed scan : 50 ms, 100 ms, 200 ms or 500 ms. (50ms or 100ms
Default is 500 ms. (Available for CS 3000 only)
High-Speed scan : 50 ms, 100 ms, 200 ms or 500 ms. (50ms or 100ms
Default is 200 ms.

F2.1.2 Pulse Width and Serial Startup Interval for MC Instrument

Block
The settings related to motor control blocks (MC-2 and MC-3) may be set.
The time of ON for contact output for the converted signal of “2-position Pulsive
Output ” or “3-position Pulsive Output ” may be defined in each FCS.
Pulse Width: 1 to 100 Sec. (The default setting is 1 second.)
The serial start function puts the motor control blocks (MC-2, MC-3) of the same
control station into groups and starts multiple motor control blocks (MC-2, MC-3) in
the same group sequentially at a specified interval when start requests are issued to
these blocks simultaneously.
Serial start interval: 0 to 9999 seconds. (The default setting is 0 second.)
F2.1.3 MLD-SW Block AUT/CAS
MLD-SW is a Manual Loader Block with Auto/Man SW to manually operate final

control elements such as control valves. As the lowest downstream block in the
control loops that consist of multiple function blocks, the mode of the block may be
set as CAS or AUT.
Whether to set the cascade (CAS)mode or automatic (AUT)block mode for outputting
the result obtained by control computation processing of the value input from other
function block,may be selected for each control station on the property setting box of
the FCS:
MLD-SW AUT/CAS: Check “CAS” or “AUT.” (The default setting is [AUT].)
F2.1.4 SEBOL statement
The “drive” statement executes the output operation with respect to the motor control
block or switch instrument block and waits until the function block completes an
answer back check.
This check to see if output and operation with respect to the function blocks, are
possible according to the block mode and action type. There are three action types as
shown below:
Table Action Type of the “drive” Statement
For more detailed information, please refer to SEBOL (IM 33S01B30-01E) Page 110
onwards.

F2.1.5 User-Defined block

When using the blocks with user-defined data items (SFC block, unit instrument), a
specific area needs to be specified.
[Number of Block Type] displays the allowed number of block types for the current
type of FCS database.
[Block-type start number] may be set with reference of the [Number of Block Type].
For example, if the allowed number of block types is 20 for both FCS0101 and
FCS0102, and the [Block-type start number] for FCS0101 is set to 0, the areas from 0
to 19 is reserved for FCS0101. Thus, the [Block-type start number] for FCS0102, may
be set to 20 or greater.
F2.1.6 IOM Online Updating

When downloading to an I/O module, the behavior of function blocks connected to the
module may be specified as IOP (input open) or not.
F2.1.7 Options
When using option programs, the programs need to be registered on the FCS
properties\setting box.
Select an option program then click [Add] button to register the program
. OFFSITE (Offsite block) (*1)

. VPMON (Valve pattern monitor) (*1)
. GC1000 (Communicating with Gas chromatography) (*2)
. MELSEC_E (MELSEC-A Ethernet) (*3)
. ZACMWDPX (For dual-redundant configuration communication modules) (*4)

F2.1.8 PID Pulse Width Output

If no feedback is set, the MV displays in the following two styles at the AUT mode:
• Hold Previous MV
displayed MV keeps the previous MV. When pulse output restarts, if the restarted
output is in the same direction of the previous output, the displayed MV equals to
the previous MV plus the _MV for increment or previous MV minus the _MV for
decrement. However, if the restarted output is in reversed direction, the displayed
MV equals to 50% plus or minus the _MV for increment or decrement.
• Display 50% MV (CENTUM-V Compatible)

displayed MV returns to 50%. When pulse output restarts, the displayed MV
equals to the 50% plus the _MV for increment or 50% minus the _MV for
decrement. Whenever the _MV reverses from positive to negative or vice versa,
the displayed MV returns to 50% then plus or minus the _MV for increment or
decrement respectively.
The MV display style when no feedback for pulse width output and the block is at
AUT mode can be set on FCS properties sheet. Check the check box of [CENTUM-V
compatible MV Display] in the column of [PID Pulse Width Output]. When this option
is checked, the displayed MV returns to 50% when no pulse is output. Otherwise, the
displayed MV keeps the previous MV. This check box is unchecked by default.
F2.1.9 PI-HLD Action after Hold

When PI-HLD starts the control calculation after its Hold period elapsed, the previous
process variable is used as the PVn-1 in proportional term computation, and the
following two methods can be selected:
• Use the PV right before the Hold status as the PVn-1

• Use the current PV as the PVn-1 (Same as the PI-HLD in CENTUM-XL)
The two calculation methods can be selected on FCS properties sheet. Check the
check box of [CENTUM-XL compatible] in the column of [PI-HLD Control Action after
Hold]. When this option is checked, the PVn-1 in the control algorithm uses the
current process variable PVn. Otherwise; the PVn-1 in the control algorithm uses the
process variable right before the Hold started. By default, [CENTUM-XL compatible]
is not checked.
F2.1.10 Sequence Table Algorithm

When the check box of [CENTUM-XL Compatible Sequence Tables] in the
[Sequence Table Algorithm] setting area of [Constant] tab on FCS Properties sheet is
checked (*1), if the step00 exists in the same table of the execution step, both the
step00 and the execution step will be activated at the same time after the condition
testing. If the table is expanded to another table and the execution step is on the
expansion table, the condition of the step00 will be tested first and then the action of
the step00 will be activated before testing and activating the execution step.
However, if the check box of [CENTUM-XL Compatible Sequence Tables] is not
checked, the condition of the step00 will be tested first and then the action of the
stepp00 will be activated before testing and activating the execution step even when
the sequence table is not expanded.

When the check box of [THEN/ELSE Has Higher Precedence] in the [Sequence
Table Algorithm] setting area of [Constant] tab on FCS Properties sheet is checked
(*1), if the next step is directed by THEN/ELSE, the next step directed in the action
rule will be ignored. However, if the next step is not directed by THEN/ELSE, the next
step directed in the action rule will be activated. Vice versa, when the check box of
[THEN/ ELSE Has higher Precedence] is not checked, the next step directed in the
action rule will be activated and the next step directed by THEN/ELSE will be ignored.
*1: The check boxes of [CENTUM-XL Compatible Sequence Tables] and [THEN/ELSE Has Higher
Precedence] are available in the [Sequence Table Algorithm] setting area of Constant tab on FCS
Properties sheet of KFCS2, FFCS, FFCS-L and LFCS2 only.
F2.1.11 dPV/dCPV Output from SUB Becomes Zero Right After IOP
Auxiliary Output (_PV) When PV Data Status is BAD: KFCS2/FFCS/FFCS-L

LFCS2
Function Block Detail Builder, the PV will overshoot when the data status becomes
bad (BAD). Under such circumstance, the _PV output from the SUB terminal can be
set to output either 0 or the actual delta PV i.e. the increment or decrement between
the current scan PV and the previous-scan PV.
For the DPV output, an option [dPV/dCPV Output from SUB Becomes Zero Right
After IOP] can be checked on FCS Properties sheet. When the option is checked, the
DPV output becomes 0 immediately after IOP. Otherwise, the actual DPV will be
output from the SUB terminal. By default, this option is not checked.
Auxiliary Output (_CPV) When CPV Data Status is Bad : KFCS2/FFCS/

LFCS2
Function Block Detail Builder, when the data status becomes bad (BAD), the _CPV
output from the SUB terminal can be set to output either 0 or the actual delta CPV i.e.
the increment or decrement between the current-scan CPV and the previous-scan
CPV.
For the DCPV output from SUB terminal, an option [dPV/dCPV Output from SUB
Becomes
Zero Right After IOP] can be checked on FCS Properties sheet. When the option is
checked, the DCPV output from SUB becomes 0 immediately after IOP. Otherwise,
the actual DCPV will be output from the SUB terminal. By default, this option is not
checked.
However, for the calculation block that the setting item [Calculated Input Value Error
Detected] is specified for no reaction on the error, the DCPV output terminal will be
the actual delta CPV value in accordance with the [PV Overshoot] setting even if the
option [dPV/dCPV Output from SUB Becomes Zero Right After IOP] is checked.

F2.1.12 Accept Batch-End during EMST

The following section explains the basic operation of the Totalizing Batch Set Blocks
at each control step (ZONE):
1. ZONE10: Batch start (Block status: STRT)

Sets data to the set parameters including batch setpoint (BSET) prior to
batch start. If the command switch is set to start (SW=1) while in the
automatic (AUT) block mode, the current control step moves to ZONE10 and
the block starts batch operation after resetting the totalized value (SUM) to 0.
Once batch starts, the control step moves to ZONE1.
2. ZONE1: Initial batch (Block status: IBCH)

After batch start, outputs the low flowrate setpoint (ML) as the manipulated
output value (MV) until the totalized value (SUM) reaches the initial forecast
value (ILST). The output velocity limiter does not operate. When the totalized
value (SUM) exceeds ILST, the control step moves to ZONE2.
The “low flowrate setpoint (ML)” and “initial forecast value (ILST)” are set
• Low flowrate setpoint (ML):

range.
• Initial forecast value (ILST):

The default is 0.
The set value consists of 8 digits or less.
3. ZONE2: Setup (Block status: STUP)

Changes the manipulated output value (MV) to the high flowrate setpoint
(MH) value during the Ramp Up time (TU). The high flowrate setpoint (MH) is
an output value in a steady state.
When the set TU time elapses in the setup mode, the control step moves to
ZONE3.
The “high flowrate setpoint (MH)” and “Ramp Up time (TU)” are set from the
• High flowrate setpoint (MH):

range.
• Ramp Up time (TU):

4. ZONE3: Steady (Block status: STDY)

Outputs the high flowrate setpoint (MH) as the manipulated output value
(MV). When the totalized value (SUM) reaches the value of batch setpoint
(BSET) less pre-batch setpoint (PLST), the control step moves to ZONE4.
The “batch setpoint (BSET)” and “pre-batch setpoint (PLST)” are set from the

• Batch setpoint (BSET): Set data in the same unit as the totalized value
(SUM).
The default is 0.
• Pre-batch setpoint (PLST): Set data in the same unit as the totalized value
(SUM).
The default is 0.
5. ZONE4: Early (Block status: ERLY)

In the course of Ramp Down time (TD), the manipulated output value (MV) is
changed to PRE (pre-batch flowrate setpoint) on the gradient that leads to
the low-flowrate setpoint (ML). When the manipulated output value (MV)
becomes the same value as the pre-batch flowrate setpoint (PRE), the
control step moves to ZONE5.
The “pre-batch flowrate setpoint (PRE)” and “Ramp Down time (TD)” are set
• Pre-batch flowrate setpoint (PRE):

Set engineering unit data within the MV scale range.
• Ramp Down time (TD):

6. ZONE5: Pre-batch (Block status: PBCH)

Outputs the pre-batch flowrate setpoint (PRE) as the manipulated output
value (MV).
less leakage predictive value (LPV), the control step moves to ZONE7.
The “leakage predictive value (LPV)” is set from the operation and monitoring
• Leakage predictive value (LPV):

The default is 0.
Specify a numeric value of 4 digits or less.
7. ZONE7: Batch end (Block status: END)

Batch operation ends after the manipulated output value (MV) is reset to “0.”
When the batch end wait time (TW) elapses in the batch end mode, the block
mode changes to manual (MAN) and the control step moves to ZONE0. At
this time, the totalized value
(SUM) is added to the cumulative totalized value (SUM1). However, this
addition will not take place in the manual (MAN) mode.
The “batch end wait time (TW)” is set from the operation and monitoring
• Batch end wait time (TW): Set a value between 0 and 10000 seconds.
8. ZONE0: Batch operation stop (Block status: NCNT)

In this mode, batch Control Action stops and a manually manipulated variable
can be output.

9. ZONE6: Reset (Block status: RSET)

When the command switch is set to Abort (SW=3) during batch operation, the
control step moves to ZONE6 and the manipulated output value (MV) is
brought down to 0 % at a speed of changing it from the high flowrate setpoint
(MH) to low flowrate setpoint (ML) over the Ramp Down time (TD).
When the manipulated output value reaches 0 %, the control step moves to
ZONE7.
When the totalized value exceeds the value of batch setpoint (BSET) less
leakage predictive value (LPV), the status changes to batch end and
generates an alarm (BEND). The batch ends other than this way does not
generate batch end alarm (BEND).
10. ZONE8: Emergency stop (Block status: EMST)

When the emergency command switch is set to emergency stop (EMSW=1),
or when the command switch is set to emergency stop (SW=4), the control
step moves to ZONE8, and the manipulated output value (MV) is brought
down to 0 % at a speed of changing it from the high flowrate setpoint (MH) to
low flowrate setpoint (ML) over TD (Ramp Down time). When the
manipulated output value (MV) reaches 0 %, the control step moves to
ZONE9.
Even when the block is in Emergency Stop (EMST) status, if the totalized
value (SUM) reaches the batch setpoint (BSET) Value minus the leakage
predictive value (LPV), the control step may shift to ZONE7. However, this
behavior is alternative by changing the setting of [Accept Batch-End during
EMST] on the FCS properties sheet. By default, this check box is checked.
11. ZONE9: Emergency stop complete (Block status: EEMS)

less leakage predictive value (LPV) during emergency stop, the control step
moves to ZONE7.
However, if the option of [Accept Batch-End during EMST] on the FCS
properties sheet is not checked, it will not move to ZONE7 but stays in
ZONE9.
12. ZONE11: Restart (Block status: RSTR)

When the command switch is set to restart (SW=2) during the emergency
stop complete mode (ZONE9), the control stop moves to ZONE2 via
ZONE11.

F2.2 KFCS Property – Constant 2

In System View, right click on [FCS0101] [Properties] View [Constant 2].
F2.2.1 SS-DUAL PV Update during Deviation Alarm

When SS-DUAL block signal selector switch is at the position 3, both input1 and
input2 will be monitored. If one of them is not normal, the switch will select the normal
side input. If a deviation alarm occurs, to update PV or to hold the current PV can be
set by checking this option.
When checking the option box for [SS-DUAL PV Update During Deviation Alarm], if a
deviation alarm occurs when the switch position is 3, the data status of PV will
become BAD but the PV itself will continue to update vary with the selected input
signal.
The default setting does not check this option, so that when a deviation alarm occurs,
The SS-DUAL will hold its current PV.

F2.2.2 Alarm Notify Action when All AOF Released

When alarm inhibition (AOF) of all function blocks are released, if the existing alarm
gives an output or not can be specified by checking this option box.
When checking [Alarm Notify Action When All AOF Released] option box, all the
existing alarms will output when their inhibitions (AOF) are released all together.
By default setting, this option box is not checked, so that the existing alarms will not
output when AOF released.
F2.2.3 Specify Reference Station for Tag List
The tag list of a designated station can be referenced when checking this option box.
After checking [Specify Reference Station for Tag List] option box, designating a
station for referencing the tag list will be enabled. When this option is not checked,
the stations start from smallest domain number and the smallest station number will
be listed in ascending order and set as the default stations for referencing tag list.
F2.2.4 Annunciator Message with Data

Annunciator Message Head Number
When an annunciator is initiated, the data assigned for the annunciator can be
referenced for the printing message.
The annunciators from the designated annunciator head number will correspond one
by one to the printing messages from the designated printing message head number.
Printing Message Head Number

When the setting for annunciator message head number or for printing message
head number is not correct, an error will be displayed in the dialog box and the setting
will become invalid.

F2.2.5 Increase Number of System Common Switches

manipulation.
switches. However, if the number of system common switches is not increased, the
element numbers of the system common switches are from %SW0001 to %SW0200
(*1).They are used to indicate the different statuses of the FCS. Only a few of
switches can be defined by users.
Common switches in the CS 3000 with element number %SW0401 to %SW4000 (If
the number of system common switches is not increased, %SW0201 to %SW4000)
may be freely defined by users.
*1: • The number of system common switches of SFCS is fixed between %SW0001 and
%SW0200. The user-definable common switches are from %SW0201 to %SW4000.
• The number of system common switches of PFCS is fixed between %SW0001 and
%SW0200. The user –definable common switches are from %SW0201 to %SW1000.
Changing the number of system common switches can be performed on FCS

properties sheet (*2) by checking the option box [Increase Number of System
Common Switches]. By default setting, this option is checked.
*2: The option for increasing the number of system common switches is not available for SFCS
and PFCS.
F2.2.6 Preset MV Valid Immediately:

Preset MV Valid immediately setting for a regulatory control blocks has two options,
[Preset MV valid by Preset Switch] and [Preset MV valid at next scan]. When a preset
MV switch (PSW) is activated by an external command such as from a sequence
control block, the preset MV can be output immediately.
For pulse width output, [Preset MV valid immediately] Option cannot be set to
[Preset MV valid immediately] .
Preset MV valid timing can be specified on FCS properties sheet. When checking the
option of [Preset MV valid by Preset Switch] , the preset MV will be immediately
forced to the MV output instead of waiting for the next scan; while when checking the
option of [Preset MV valid at next scan], the preset MV will be forced to the MV output
at the next scan. The Default is [Preset MV valid at next scan].

F2.3 KFCS Property – State Transition

In System View, right click on [FCS0101] [Properties] View [State Transition].
F2.3.1 State Transition Matrix

When the FCS database is a type of database for unit configuration, state transition
matrix can be defined.
Maximum Specification Number

Indicates the total number of state transition matrixes. This is only an indication and
cannot be edited.
Designating a State Transition Matrix

In the matrix list, the matrixes registered in the project as well as the matrixes
removed from the project but had been registered as the state transition matrix before
removal are available for selection. If choose a matrix already removed from the
project as the state transition matrix, an error will occur.

F2.4 KFCS Property – Line 1

In System View, right click on [FCS0101] [Properties] View [Line 1].
F2.4.1 Make I/O Bus Dual Redundant
Specify whether or not the ESB bus is made dual-redundant in an FCS in which only
one CPU card is used.
When this checkbox is checked to make the ESB bus dual-redundant, the ESB buses
will usually be used alternatively. If an error occurs in one of the ESB buses, the other
ESB bus will be used for communication. Error recovery monitoring of an abnormal
ESB bus will be performed periodically.
F2.4.2 Interface Card Type
Specify the type of the ESB bus interface card (SB301/SB302). To use the CENTUM-
XL cabinet, specify SB302. To use a rack mountable type, specify SB301.

F2.5 KFCS Property - Network

In System View, right click on [FCS0101] [Properties] View [Network].

F2.5.1 VLnet TCP/IP Settings, V net TCP/IP Settings

Normally there is no need to change the TCP/IP protocol setting for the control
bus.

The bus type, domain number and station number of an IP address on the control bus
is automatically determined. In normal situation, the automatically determined setting
should be used.

The control bus subnet mask is set to “255.255.0.0” as the default setting. In normal
situations, this default setting should be used.
F2.6 KFCS Station Definition

F2.6.1 Definitions
“FCS start operation” refers to all the actions performed through the process of FCS’s
changing its status from operation stop status to normal operation status.
It includes “Initial cold start” and “Restart.”
Which operation to be performed is determined by “Cause of start,” “Start condition,”
and “Power failure time and Momentary Power Failure tolerant time.”
Start condition

The start condition determines which method to be used, initial cold start or restart, to
initiate the FCU, upon turning on the power to FCU which was in the power shutoff
status.
FCS performs either initial cold start or restart according to the specified start
condition.
The default is “MAN (Initial Cold Start).”
When the FCS in station STOP status executes the start operation, the initial cold
start must be executed regardless of start condition.
Momentary Power Failure Tolerant Time

When “TIME” is selected as the start condition, “Momentary Power Failure Tolerant
Time” should be specified.
“Momentary Power Failure Tolerant Time” is a definition item used to determine the
type of start operation based on the power failure time.
. Momentary Power Failure Tolerant Time: Set 0.0 to 4.0 (sec).
(The default is 2.0 sec.)

Node Momentary Power Failure Tolerant Time

Two types of start operation–“initial cold start” and “restart”–are available for the
nodes (local node and remote node). These two types of start operation are executed
when a node that is not responding is recovered after the occurrence of an error. The
type of start operation to be executed is determined by the duration the node does
not respond.
“Momentary power failure tolerant time” can be set in the range between 0 and 4
seconds. If 0 is set, the start operation of the node is always set to the “initial cold
start.” The default value is 2 seconds.
When the no-response time of the node is longer than the “momentary power failure
tolerant time,” it is called prolonged node power failure.
When the no-response time of the node is shorter than the “momentary power failure
tolerant time,” it is called momentary node power failure.
For more detailed information, please refer to Field Control Station Basics
(IM 33S01B30-01E) Page 209 onwards.
Digital Filter
The digital filter is a function to remove the noises from process input signals.
Shown below is the step response of digital filtering process.

There are three kinds of digital filter coefficients:

The defaults for these digital filter coefficients are set to the values indicated below:

constant\is 1 second)



F2.6.2 Scan Transmission
To transfer/receive the values of global switches between stations.
Self Station
. Buffer Size: Define 32 (bytes) to transfer the values, or 0 not to transfer them.
(The default is 0.)
Station Scan Transmission

Define whether to receive the values of global switches from other stations.
. Station: Choose “0: No Scan Transmission,” or

“1: Internal Station Scan Transmission.”
(The default is 0.)
When you choose “Internal Station Scan Transmission,” define the communication
buffer size to receive data from its station.
. Individual Station Definition (stations 1 to 64):


F2.6.3 Detailed Settings
Wind Up Time
Windup operation is a preparatory processing for organizing time-series data that are
required for control operations. The function block’s input processing, control
processing, calculation processing and alarm processing executed during windup
operation are executed in the same manner as in normal operation. All output signal
processing, except for the one that outputs control output signals to the process
output terminal, are executed in the same manner as in normal operation.
Sequence table blocks and logic chart blocks don’t operate while windup operation is
running.
. Wind Up Time: Set 0 to 100 (sec.).

(Default is 60 sec.)
SEBOL/User C Ratio
The setting of the processing executed in the idle time in FCS’s CPU is defined in
“SEBOL/User C time ratio” on the FCS Constants Builder. This time ratio is set as
“100 %” as default, means the total idle time of FCS’s CPU is used by SEBOL.
Interval of Repeated Warning Alarms

The repeated warning alarm retransmits a process alarm message to notify the
operator that a critical alarm status is continuing.
Only the high-priority alarm can be reissued as repeated warning alarm. If the
definition item of repeated warning alarm cycle is defined as zero second, repeated
warning alarm does not effect.
. Repeated warning alarm period: The setting value is between 0 to 3600
seconds. When 0 is set, repeated warning alarm function is disabled. Default is
600 seconds
Alarm Mask for Initial Cold Start

The repeated warning alarm has a function in which at initial cold start (include
recovery from a long period of power failure) of the FCS, only the high-priority alarms
are picked up from all the alarms and issued to the operation and monitoring
consoles.
With mask: Only the alarms that were newly activated and high priority alarms will
issue the alarm messages when the FCS initiates cold start.
Without mask: Every alarm that is in progress will be classified as newly activated,
and the process alarm messages will be issued at initial cold start.
Inter-Station Data Link Communication Period

The inter-station communication period is a time required to complete all inter-station
data link processing within a FCS. The default is one second.
The number of inter-station communications points, C, executed in one second is

shown below:
C = (Effective inter-station data link points)

(Inter-station communication period)
The effective inter-station data link points are the points of the inter-station data link
actually wired in Control Drawing Builder or in Function Block Detail Builder or in
Function Block Overview Builder within each FCS.
Re-Transmission Skip when Inter-Station Data Link Error

When a communication error is detected during inter-station data link processing,
inter-station communication transmission skips for a period of time then retry the
transmission in the interval of this skip period. This re-transmission skip period is
expressed as follows:
Re-transmission skip period =

(Inter-station communication period) • (re-transmission skip times)
Default for the re-transmission skip times is 60.


F3. FFCS
F3. Field Control Unit for FIO (Rack Mountable) –

FFCS (FFCS Compact FCS)
The FFCS is a scalable, compact FCS for the Fieldnetwork I/O (FIO) which is used as the
inputs and outputs of the FFCS.
The FFCS is suited for small- to mid-size systems, whereas the Standard FCS for FIO
(KFCS) and Enhanced FCS for FIO (KFCS2) are suited for mid- to large-size systems.
FFCS may be configured as a compact type field control unit with 3 I/O nodes. The control
bus is V net (10BASE-2).

F3. FFCS
F3.1 Configuration of Field Control Unit
The type and number of the module to be installed in AFF50S/AFF50D vary with model
name and specification code of AFF50S/AFF50D.

F3. FFCS
F3.2 Duplexed Structure of the FFCD

The FFCD contains duplexed control bus communication couplers, processor modules
(CP401s) of the FCU, extended serial backboard buses (ESB buses), enhanced remote
buses (ER buses) and I/O modules. It also can contain duplexed power supply units for
the FCU, local node and remote node.
Figure: Example of Signal Connections When Applicable Component Units of the

FFCD are Duplexed

F3. FFCS
Duplexing the Processor Modules (CP401s) of the FCU
• Each processor module has two MPUs. Each MPU performs the identical control
computation. The computation results of the two MPUs are compared using a collator
during each control computation cycle.
• If the computation results of the two MPUs match, the collator determines that the
computation is normal and sends data to the main storage and the bus interface unit.
• Because the main storage has an ECC (Error Correcting Code), it corrects transient
bit inversion errors occurring inside the main storage.
• If computation results between the MPU1 and MPU2 do not match, the collator
determines that a computation error has occurred, and then the control right is
transferred to the standby processor module.
• The standby processor module performs the same control computation as the
controlling processor module even when it is in the standby state. Therefore, the
standby processor module can immediately resume the output of control computation
data to the bus interface when it takes over the control right.
• Self-diagnostics is executed on the processor module in which a computation error

has occurred. If no abnormality is detected in the error causing MPU as a result of
diagnostics, the error is determined as a transient computation error, and the module
is recovered from the error state and placed in the standby state. The processor
module in standby state performs the same control computation synchronous with the
controlling processor module.
• If an abnormality is detected in the self-diagnostics 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 other’s processor module via the SB buses between duplexed
processor modules.
• If all local nodes are abnormal, it is assumed as an ESB bus failure.

F3. FFCS
Duplexing the Extended Serial Backboard Buses (ESB Buses)
ESB buses can be duplexed regardless whether the processor module (CP401) has a
single or dual-redundant configuration. Duplexed ESB buses consist of two ESB bus
coupler modules (EC401s) mounted in slots 7 and 8 of the FCU, two ESB buses, and two
ESB bus slave interface modules (SB401s) mounted in local nodes.
Duplexing EC401s, ESB Buses and SB401s

Connect the EC401 in slot 7 of the FCU with the left SB401 in the local node via an ESB
bus. Connect the EC401 in slot 8 of the FCU with the right SB401 in the local node via an
ESB bus.
The duplexed ESB buses are used alternately in normal situation. If an abnormality
occurs in one set of an EC401, ESB bus and SB401, the other ESB bus is used to
perform communication.
The error recovery monitoring of an abnormal ESB bus is performed periodically.

F3. FFCS
Duplexed Enhanced Remote Buses (ER Buses)

The duplexing procedure of enhanced remote buses (ER buses) of the FFCS is the same
as that of the KFCS2.
When referencing the “Dual-Redundant Configuration of Enhanced Remote I/O Bus (ER
Bus)” of the KFCS2 above, please be aware of the following item:
• ER buses can also be duplexed by mounting two adjacent EB401s in the I/O
module section of the FCU.

F3. FFCS
F3.3 Create a New FFCS

Select [Create New] - [FCS] from the File menu of System View while selecting a project
folder or Select the project folder and right click [Create New] [FCS].
There are two station types for the FFCS:
• AFF50S Field Control Unit (for FIO, Rack Mountable)

• AFF50D Duplexed Field Control Unit (for FIO, Rack Mountable)

F3. FFCS
F3.4 Input/Output
Input/Output Function is the function that exchanges data within the FFCS as well as
between the FFCS and non-FFCS devices.

F3. FFCS
F3.4.1 Creating a New Node: FFCS

A node can be created from System View by right clicking on [IOM]
[Create New] [Node]
Define the FCU’s I/O module section as node 1 (node number 1) in the Create New
FIO Node dialog box. [Type] is fixed to [Local] for node 1.
Node 1 cannot be deleted.
To newly create a local node as an expanded node, an I/O module must not be
defined for slots 7 and 8 of the FCU’s I/O module section since an ESB bus coupler
module (EC401) is installed in one or both of these slots.
To newly create a remote node as an expanded node, it is necessary to define an

EB401 (ER bus master module) for the FCU’s I/O module section or local node to
which the newly created remote node will be connected.
Specify the node number of an expanded node between 2 and 4.

F3. FFCS
F3.4.2 Creating a New I/O Module: FFCS

Create an I/O module (IOM) to be installed to the FFCS in the Create New IOM dialog
box.
To use a local node as an expanded node, slots 7 and 8 of the FCU’s I/O module
section must be vacant in order to install an ESB bus coupler module (EC401) in one
or both of these slots.
If only a single ESB bus is used, install an EC401 in slot 7. Although slot 8 will be
vacant, no I/O module can be defined for slot 8.

F4. FFCS_L (Vnet/ IP)
F4. Field Control Unit for Vnet/ IP Open
for FIO (19” Rack Mountable) – FFCS-L Reliable

Real-
time
The FFCS-L is a control station that can only be connected to Vnet/IP. The types of function
blocks and I/O cards that can be connected are the same as those of the FFCS.
FFCS-L field control unit is a model of CENTUM CS 3000 field control station (model name:
AFV10S/ AFV10D) that applies Vnet/ IP to the control bus.

F4.1 Configuration of Field Control Unit
The type and number of the modules to be installed in AFV10S/AFV10D vary with model
name and specification code of AFV10S/AFV10D.

F4. 2 Hardware Configuration of FFCS-L

The following shows the hardware configuration of the FFCS-L.
The FFCS-L hardware is different from the FFCS hardware in the following points. Other
hardware components are the same as those of the FFCS.
● CPU Card (CP451)

This CPU card supports Vnet/IP communication. Other hardware specifications such
as the processor and the main memory size are the same as those of the CPU card
(CP401) of the FFCS.
● V net Coupler
The Vnet/IP bus is directly connected to the RJ-45 communication port located in the
front of the CP451 on the control side and the standby side. There is no V net coupler
in the CPU nest.

F4. 3 Create a new FFCS-L

Select [Create New] - [FCS] from the File menu of System View while selecting a project
folder or Select the project folder and right click [Create New] [FCS].
The following shows the available FFCS-L station types.

F4. 4 Input/Output
Input/Output Function is the function that exchanges data within the FFCS as well as
between the FFCS and non-FFCS devices.

F4. 4.1 Create a New Node- FFCS-L

A node can be created from System View by right clicking on [IOM]
[Create New] [Node]
The node number 1 is reserved for Field Control Unit.
When connecting a Local Node to FCU, install ESB Bus Coupler Module (EC401) to
FCU.
EC401 must be installed in slot 7 and slot 8. To make single configuration, EC401
must be installed in slot 7, and Slot 8 must be empty.
Set the node number of FFCS-L in the range of 2 to 15.

F4.4.2 Creating a New I/O Module : FFCS-L

Create an I/O module (IOM) to be installed to the FFCS in the Create New IOM dialog
box.
To use a local node as an expanded node, slots 7 and 8 of the FCU’s I/O module
section must be vacant in order to install an ESB bus coupler module (EC401) in one
or both of these slots.
If only a single ESB bus is used, install an EC401 in slot 7. Although slot 8 will be
vacant, no I/O module can be defined for slot 8.


G1. INPUT/OUTPUT FUNCTIONS (LFCS)
G.1 INPUT/OUTPUT FUNCTIONS (LFCS)

The input and output interfaces support the internal data exchange inside a field control
station and external data exchange between a field control station and equipment.
The input and output interfaces consist of Software I/O, Process I/O, Communication I/O and
Fieldbus I/O.
G1.1 FCS Input and Output Interfaces

A field control station can access internal and external data via these I/Os.
The following figure illustrates the I/O interfaces in basic control architecture.
There are two types of I/O functions:

. Process I/O
Process I/O stands for the interface for the signal communication between Field
Devices and field control station. An FCS receives signals from field process detection
devices and send control signals to field control devices.
. Software I/O
Software input and output is a function to carry out the virtual input and output
connection inside of FCS by software.
YOKOGAWA SINGAPORE TRAINING CENTRE Page G1-1 of G1-22

G1.2 Process Input/Output

Process inputs/outputs are used to exchange signals between field equipment and an
FCS. Using process inputs/outputs, an FCS can receive signals from process detectors
and output signals to process control elements.
Signals can be received from the process detecting element (transmitter) to the FCS, and
can be output from the FCS to the process control element (valve).
When the station type of an FCS is either KFCS or LFCS, a node for installing an I/O
module must be created prior to creating an I/O module.
G1.2A Creating a New Node: LFCS
A node for holding I/O modules can be created from System View, right click on [IOM]
[Create New] [Node].

G1.2.1 Type Tab – Node Number

The node number is a number to identify a node, which is set from 1 to 8. The
default is 1.
G1.2.2 Dual Redundant Power Supply

Select “Yes” or “No” for dual-redundant power supply. The default is “No.”
G1.2.3 HKU Set

Select “Yes” if you use a housekeeping unit (HKU), “No” if you do not. The default
is “No.”
G1.2.4 Installation Pattern

Select “Cabinet” or “Rack” to install nodes. The default is “Cabinet.”
G1.2.5 Component Number

The component number is a number given to the cabinet to install FCS units,
which is used to identify where to connect a cable. Up to 8 characters can be
used for the number.
The component number setting can be omitted.
G1.2.6 Node Comment

Up to 24 single-byte characters can be used for the node comment. No
characters are entered at the default.
The node comment setting can be omitted.
G1.2.7 Unit Tab – Start Mode

This is the start mode on I/O units. Set time within 1 to 16,000 msec, or select
“MAN” (manual).
The default is 2,000 msec.
G1.2.8 High Speed Read

Select “Yes” or “No” for reading data of I/O units at high-speed. The default is
“No.”

G1.3 Creating a New I/O Module: LFCS

An I/O Module can be created from System View, right click on [Nodex]
[Create New] [IOM].
NOTE:

G1.3.1 IOM Type

Category shows types of I/O module nests, as the table below shows:
Type shows the different types of I/O modules that may be installed based on
different I/O module nests selected.


G1.3.2 Installation Position

The IOM position can be specified. Unit positions for LFCS are shown below:
No. 1
No. 1 No. 2
No. 2 No. 3
No. 3 No. 4
No. 4 No. 5
Slot positions are shown below for different I/O Module Nest.
Slot 4
Slot 1 Slot 1 Slot 2 Slot 3
Slot 2
Slot 1

G1.3.3 Duplicate Next Card
The two I/O modules installed next to each other (odd numbered slot and the odd
number + 1 slot) can be configured as dual-redundant.
When the option [Duplicate the next card] is checked, a dual-redundant I/O module
(u-s IOM name Dup) will be created.
On the IOM module property sheet, check the mark “Duplicate Next Card.”
Normally, the module with slot number 1 is the control side and the module with slot
num-ber 2 is the standby side. If the module on control side fails, the module that was
on the standby side will take over the control. Function blocks will read data from the
new control side module.
The IOMs allowed to be defined dual redundant are listed below:
• Status input
• Status output
• Analog input
• Analog output (only current output module AAM51 or AAM50)
Checking the [High Speed Read] option with only one I/O module installed in one unit
will enable the FCU to read from I/O module at high speed.
This option is available for Package Communication modules (ACM11/ACM12) and
the Fieldbus Communication module (ACF11).
G1.3.5 IOM Comment
Up to 24 alphanumeric characters can be put as IOM comment text.

The comment can be omitted.

G1.4 IOM Builder

The 2 basic IOM modules are explained here.
• Analog I/O Module
• Contact I/O Module
G1.4.A Analog I/O Module Nest (AMN11) Configuration

The IOM Builder for AMN11 can be opened from
System View, click on [Nodex] Double click on [AMN11]
[Show/Hide Detailed Settings Items] button
Click
G1.4.1 Terminal
A terminal of a process I/O or a Fieldbus I/O can be numbered in accordance with its
physical position and the I/O module location.
The format of a terminal number is as follows:

G1.4.2 Signal
This item is used to specify the IOM type.
The following IOM types can be selected.
• Current input (AAM11)
• Voltage input (AAM11)
• Current input (AAM11B)
• Voltage input (AAM11B)
• Current input/Single function (AAM10)
• Voltage input/Single function (AAM10)
• mV input (AAM21)
• Thermocouple input (AAM21)
• Resistance temperature detector input (AAM21)
• Potentiometer input (AAM21)
• Pulse input (APM11)
• Current output (AAM51)
• Voltage output (AAM51)
• Current output/Single function (AAM50)
G1.4.3 Conversion
The selection list varies with the IOM type.
The selection list and default value for each IOM type are shown in the table below.

G1.4.4 Service Comment

A character string consisting of up to 40 characters can be entered.
The service comment setting is optional and can be left blank.
G1.4.5 Low Limit/ High Limit

Values which can be selected as the high-limit and low-limit vary with the IOM type
and signal conversion type.
For more detailed information, please refer to Field Control Station Basics - Range
High/Low Limit (IM 33S01B30-01E) Page 62 & 63.
G1.4.6 Unit
Selectable units of measurement range vary with the IOM type.
The unit selection list and default value for each IOM type are shown in the table
below.

G1.4.7 Set Details

Selectable items vary with the IOM type.
The selection list and default value for each IOM type are shown in the table on next
page.
G1.4.8 Dual
The dual redundant can be designated to the current output module AAM51 or
AAM50, only for the odd numbered IOM. The IOM is called duplex source.
If the Dual redundant is defined as “Enable” to the IOM, the signal of the duplex
source will be copied to its corresponding duplex destination. Once the signal is
copied, definition change on the duplex destination IOM becomes impossible.
The table below shows the relationship between terminal numbers of duplex source
IOMs and destination IOMs.

G1.4.9 P&ID Tag Name

A P&ID tag name of up to sixteen characters can be specified in the IOM Builder. The
setting is optional, and blank as the default.
G1.4.10 Label (User-defined label)

A user-defined label of up to 16 characters (as the name of the function block’s
input/output terminal) can be specified in the IOM Builder.
The setting is optional, and blank as the default.
The entry format of user-defined labels is as follows:
G1.4.B Detailed Setting of Analog I/O Module

Select a card , eg. AAM11 Current Input, and select from Pull-Down Menu,
[Tools] [Set Details]

G1.4.1 Detect IOP

The detection for wire breakage (input open) of the input signal can be defined in the
IOM Builder.
The default is “Enabled.”
The IOMs allowed to select for detecting IOP are listed below:

• Current input (Simplified) (AAM10)
• Voltage input (Simplified) (AAM10)
G1.4.2 IOP Detection Level

The default setting is “Disabled.” When disabled, the IOP will be detected at the
default levels, i.e., scale high limit is 106.3 % and scale low limit is -6.3 %.
The IOMs allowed to select IOP Detection Level are listed bellow:

• Current input (Simplified) (AAM10)
• Voltage input (Simplified) (AAM10)
High Limit
The level can be defined within a range of -25.0 to 125.0 (max. 5 digits, in %). If the
high-limit is defined lower than the low-limit , an error will occur. The default is
“+106.3.”
Low Limit
The level can be defined within a range of -25.0 to 125.0 (max. 5 digits, in %). If the
lower-limit is defined higher than the high-limit, an error will occur. The default is “-
6.3.”

G1.4.3 Square Root

The default is “Disabled.”
The IOMs allowed to select Square Root are listed below:

Low-Input Cut
The low input cut value for square root extraction can be defined in the IOM Builder.
When the input signal is below the low input cut value, the square root extraction will
not be performed, the output equals to the input value.
The default is “0.6” (%).
G1.4.4 OOP Clear

OOP output clear may be specified so that to make the output into tight-shut state
automatically when a certain time period elapsed after OOP occurs.
The default setting is that the item [OOP Clear] is not checked.
The IOMs allowed to select OPCLS are listed below:

• Current output (Simplified) (AAM50)
Clear Time
OOP output clear time is the time limit to make the output into tight-shut state
automatically after OOP occurred.
OOP output clear time may be defined in an up to 4 digits value in the range of 0 to
25.5 (unit: seconds).
The default setting is 4 seconds.
G1.4.5 Detect OOP

The detection for wire breakage (output open) of the output signal can be defined in
the IOM Builder.
The default is “Enabled.”
The IOMs allowed to select Output Open Detection are listed below.

G1.4.6 Fallback, Maintain Current Value

The default setting is no fallback.
• When check the “Set Fallback” item, and then it is required to check the option
button for either “Maintain Current Value” or “Output data.” The default option is
“Maintain Current Value.”
• When not check the “Set Fallback” item, the current value will be held when the
processor unit or the interface of the processor unit fails. However, the
occurrence of the abnormality will not be notified even when the failed processor
unit or the interface of the processor unit return to normal state.
The IOMs allowed to select Fallback are below:

• Voltage output (AAM51)
Output
Up to 5 digits may be used for fallback- output, the range for current output is -17.2 to
112.5 while the range for voltage output is -25.0 to 225.0 (unit: %).
There is no default setting.
G1.4.7 Pulse Input
Input Filtering
The default is “Disabled.”
The IOMs allowed to select pulse input filtering are listed below:
• Pulse input (APM11)
Transmitter Power
The voltage of the pulse input transmitter power supply (APM11) can be defined in
the IOM Builder.
The voltage is defined to either [12] or [24] (V). The default is [12].
G1.4.8 Resistance
The total resistance of potentiometers may be defined on the IOM Builder.
All resistance values (RESIST) may be defined in up to 7 digits number in the range
of 0 to 3000 (unit: ohm). When value is not defined, the high limit of the total
resistance value will be used. There is no default setting.
The IOM allowed to select resistance is listed below:
G1.4.9 Cold Junction Compensation

The cold junction compensation can be defined in the IOM Builder.
The default is “Enabled” for signal conversion other than [Type B], and is [Disabled]
for [Type B].
The IOM allowed to select cold junction compensation is listed below:

G1.4.10 Command
The optional setting for each I/O module can be set by entering a line of command
script.
The command scripts for control I/O modules (AAM11, AAM11B, AAM10, AAM21,
APM11, AAM51, AAM50) are shown as follows:
The applicable commands for I/O modules are different. The details are shown as
follows:

G1.4.C Digital I/O Module (ADM51T) Configuration

The IOM Builder for ADM51T can be opened from
System View, click on [Nodex] Double click on [ADM51T]
Click
G1.4.1 Terminal

G1.4.2 Mode
The available selections for the point mode and the default setting vary according to
the input/output type as shown in the table below.

A P&ID tag name of with up to 16 alphanumeric can be specified in the IOM Builder.
The setting is optional, there is no default setting.
G1.4.4 Tag Name

A tag name of up to 16 alphanumeric characters can be specified in the IOM Builder.
The setting is optional, and blank as the default.
G1.4.5 Tag Comment

Up to 24 alphanumeric characters (12 double-byte characters) may be defined as tag
comment.
The setting is optional and blank as the default is blank.

G1.4.6 Switch Position Label

The switch position labels refer to character strings displayed as labels for switches.
It can be selected from a list in data entry area.
G1.4.7 Label
Set “Direct” or “Reverse.” The default is “Direct.”
G1.4.8 Button1, Button 2

The button colors can be specified. The default setting for each label is “R” (red). The
following shows the available selections.
R: Red N: Black G: Green Y: Yellow

B: Blue M: Magenta C: Cyan W: White
SB: Steel blue PK: Pink SG: Spring green OR: Orange
YG: Yellow green VO: Violet DB: Deep sky blue GR: Gray
G1.4.9 Level
The security level of the module data can be defined.
Select the level from 1 to 8. The default is level 4.

G1.4.10 Tag Mark

The following are the available selections. The default setting is “General.”
Tag Importance Important General Auxiliary 1 Auxiliary 2
Tag mark
Action type 1 5 2 6 3 7 4 8
Confirm O X X O X O X O
Data Entry Confirmation/Alarm Acknowledge

O: required
X: Not required (automatic when status reverts to normal)
G1.4.11 Upper Window

The name of the window to be called up as the window upper in the hierarchy is
specified in the IOM Builder.
The window name must be 16 uppercase alphanumeric characters.
This setting is optional.
G1.4.12 Help
The name of the Help message number defined by the user must be specified in the
IOM Builder. The setting is optional. The help message may be identified by
assigning the help message number a unique ID.
The help message number can be omitted.
The entry format of the Help message number name is as follows:

G1.5 Exercise
1. Configure an Analog I/O Nest (AMN11) in the 3rd unit of the LFCS.
2. Configure the following Analog I/O cards in AMN11 unit.

All output cards are 4-20mA, Linear.
All input cards are 4-20mA, Linear.
AAM11
AAM51
AAM11
AAM51
AAM51
AAM11
AAM51
AAM51
Blank
Blank
Blank
Blank
Blank
Blank
Blank
Blank
3. According to the above configuration, which output card can be configured as a

standby card?
4. Configure a Contact I/O Module, ADM51T in the 4th unit of the LFCS such that
every output has a redundancy.
5. Configure two contact output points with the following display formats.

G2. INPUT/OUTPUT FUNCTIONS (KFCS)

Fieldbus I/O.

A field control station can access internal and external data via these I/Os.
There are two types of I/O functions:
. Process I/O
Process I/O stands for the interface for the signal communication between Field
Devices and field control station. An FCS receives signals from field process detection
devices and sends control signals to field control devices.
. Software I/O
Software input and output is a function to carry out the virtual input and output
connection inside of FCS by software.

G2.2 Process Input/Output

Process inputs/outputs are used to exchange signals between field equipment and an
FCS. Using process inputs/outputs, an FCS can receive signals from process detectors
and output signals to process control elements.
Signals can be received from the process detecting element (transmitter) to the FCS, and
can be output from the FCS to the process control element (valve).
When the station type of an FCS is either KFCS or LFCS, a node for installing an I/O
module must be created prior to creating an I/O module.
G2.2.A Creating a New Node: KFCS
A node for holding I/O modules can be created from System View, right click on [IOM]
[Create New] [Node].

G2.2.1 Type
Two selections, Local and Remote, are available for Type.
To create a remote node, it is necessary to define an EB401 (ER bus interface
master module) for a local node to which that remote node is to be connected in
advance.
G2.2.2 Node
The node number is used to identify a node unit. Specify a node number between 1
and 10. The default node number is 1.
A maximum of 10 local nodes, a maximum of eight remote nodes, and a total of 10
local and remote notes when they are mixed can be connected.
Also, a maximum of four ER buses can be connected to each KFCS.
G2.2.3 Master
Create a new EB401 (ER bus interface master module) for connecting a remote node
in a local node. System View, right click on [Node] [Create New] [IOM].
Select the installation position of the EB401 (ER bus interface master module) to
which a remote node is to be connected.) Specify this item only when the node
type is remote). The installation position is expressed in the following format:
NODE\EB401
n: Node number
s: Slot number

G2.2.4 Power Supply Unit

Dual-Redundant Power Supply
Specify whether or not to make the power supply unit dual-redundant. To make the
power supply unit dual-redundant, check this check box. This check box is unchecked
by default.
The power supply unit has two options, 80W or 40W.
When using 80W power supply unit, up to six modules (*1) which can supply power to
field transmitter can be installed in one node unit.
If 40 W power supply unit is used, the external power supply is required when the I/O
modules provides power to the field transmitters. In this case, check the check box of
[24VDC from External Power Unit].
If the installed I/O modules do not supply power to the field transmitters, do not check
the check box of [24VDC from External Power Unit]. Thus the 24VDC will not be
supplied to the field transmitters.

Enter the component number within eight single-byte characters. This field is blank by
default. The component number is a number assigned to a cabinet that houses an
FCS.
The specification of the component number may be omitted.
G2.2.6 Node Comment

Enter a comment on the node up to 24 single-byte characters. This field is blank by
default.
The specification of the node comment may be omitted.

G2.3 Creating a New I/O Module: KFCS

An I/O Module can be created from System View, right click on [NodeX]
[Create New] [IOM].
NOTE:

G2.3.1 IOM Type

Category, Type
The items to be set by the process input/output definition vary depending on the I/O
module type. The following shows the categories and types of I/O modules, and the
corresponding I/O module names.
FIO Analog Input/Output: KFCS

FIO Contact Input/Output: KFCS

G2.3.2 Installation Position

Slot positions are shown below:
Up to 10 node units for FIO can be installed for each FCU, and up to eight I/O
modules can be installed for each node unit.

G2.3.3 Duplicate next card

After checking the option “Duplicate Next Card,” a duplicated IOM (sIOM name Dup)
is created.
The IOMs allowed to be defined dual redundant are listed below:
• Contact Input/Output
This item is not available for the contact I/O modules that do not support dual-
redundant configuration and Status/Pulse Output modules (ADV157, ADV557).
• Multi-Point Analog input/Output
Duplicate Next Card - Remote Node Communication

The ER bus can be made dual-redundant by installing two EB401 cards. Install the
deal-redundant EB401 card in the adjoining even slot at the right. To make the ER
bus dual-redundant, check [Duplicate Next Card]. When it is checked, a file named
slot number EB401Dup will be created. This check box is unchecked by default.
G2.3.4 Output Type

Output type can be specified to the analog input/output modules and analog output
modules. Different output type makes the output to the modules or to the EB401 at
different timings.
Output in a lump: Output when all highest scan function blocks in the FCS complete
their processing.
Output immediately: Output when the connected function block is performing output
process.

When check the option box [High Speed Read], CPU reads the data at high speed
from the I/O module. However, the I/O modules for communication with remote
nodes, and the I/O modules for Fieldbus communication, High Speed Read option
are not available.
G2.3.6 IOM Comment

Up to 24 alphanumeric characters or up to 12 double-byte characters can be put as
IOM comment text.
The IOM comment can be omitted. There is not comment text by default.

G2.4 IOM Builder

The 2 basic IOM modules are explained here:
• Analog I/O Module

• Contact I/O Module
G2.4.A Analog I/O Module (AAI141-S) Configuration

The IOM Builder for AAI141-S can be opened from
System View, click on [NodeX] Double click on [AAI141-S]
Click
G2.4.1 Terminal

G2.4.2 Conversion
The selection list of the signal conversion varies depending on the type of the I/O
module.
The following lists the selection list and default values of the signal conversion:

G2.4.3 Service Comment

A string of up to 40 alphanumeric characters or 20 double-byte characters can be
entered.
The setting of the service comment may be omitted. Nothing is set by default.
G2.4.4 Low Limit/High Limit

The values that can be selected as the lower and upper limits of the range vary
depending on the I/O module type, signal conversion type, and terminal position.
For more detailed information, please refer to Field Control Station Basics - Range
High/Low Limit (IM 33S01B30-01E) Page 112 - Page 114.

G2.4.5 Unit
The values that can be selected as the unit symbols of the range vary depending on
the I/O module type, signal conversion type, and terminal position.
The following lists the selection list and default values of the unit of the range:


G2.4.6 Set Details

The items that can be selected vary depending on the I/O module type.
The following lists the selection list and default values of the details of the I/O
modules.

A string of up to 16 alphanumeric characters or 8 double-byte characters can be
entered.
The setting of the P&ID tag name may be omitted. Nothing is set by default.

G2.4.8 Label
The user-defined label is set with IOM Builder. The user-defined label can be set for
terminals.
Nothing is set by default.
Up to 16 byte alphanumeric characters can be entered.
The setting of the user-defined label may be omitted.
The following shows the specification format of the user-defined label:
G2.4.B Detailed Setting of Analog I/O Module

Select a terminal, eg. %Z011101and select from Pull-Down Menu,
[Tools] [Set Details]

G2.4.1 Detect IOP

Whether or not to detect the disconnection of input signals (IOP: input open) is set in
the details setting dialog box of IOM Builder.
The default setting is [Enabled.]
The IOPE can only be set for the signals (terminals) of the following I/O modules:

G2.4.2 IOP Detection Level

High Limit
Numeric values of up to five digits can be set for the HIIOP in the range from -25.0 to
125.0 (unit: %). The default setting is +106.3.If a value smaller than the value set in
the low limit detection level is specified, an error will occur.

Low Limit
Numeric values of up to five digits can be set for the LOIOP in the range from -25.0 to
125.0 (unit: %). The default setting is -6.3. However the default setting for AAR181-S
and AAR145-S I/O modules is zero “0”.
G2.4.3 Cold Junction Compensation

The default when a value other than “Type B” has been set as the signal conversion
of the thermocouple input is “Enabled”. When “Type B” has been set, it is fixed at
“Disabled.”
The cold junction compensation can only be set for the signals (terminals) of the
following I/O modules:

G2.4.4 Fallback
Applicable to Analog Output Cards.
Maintain Current Value

Specify either “Maintain Current Value” or “Output.” The default is “Maintain Current
Value.”
The Fallback can only be set for the signals (terminals) of the following I/O modules:
Output
A value in the range between -17.1875 and 112.5 (unit: %) can be set for the FBOUT.
The default setting is -17.1875.
G2.4.5 Pulse Input

Input Filtering
The default setting is “not checked on the check box.”
The pulse input filter can only be set for the signals (terminals) of the following I/O
module:
Transmitter Power
Set either [12] or [24] (unit: V). The default setting is [12].
Command
Specify a special setting for each I/O module signal (terminal) in a command line.

The following lists whether the command line input is enabled or disabled for each I/O
module signal (terminal):

G2.4.C Digital I/O Module (ADV551-P) Configuration

The IOM Builder for ADM51T can be opened from
System View, click on [NodeX] Double click on [ADV551-P]
Click
G2.4.1 Terminal
G2.4.2 Mode
The selection list of the point modes varies depending on the I/O module type.
The following table lists the correspondence between the module types and point
modes:


A string of up to 16 byte characters or 8 double-byte characters can be entered.
The setting of the P&ID tag name may be omitted. Nothing is set by default.
G2.4.4 Tag Name
A string of up to 16 byte characters can be entered for the tag name.

The setting of the tag name may be omitted. Nothing is set by default.
G2.4.5 Tag Comment

The setting of the tag comment may be omitted. Nothing is set by default.
G2.4.6 Switch Position Label
The switch position labels refer to character strings displayed as labels for switches.
G2.4.7 Label
Set “Direct” or “Reverse.” The default is “Direct.”
G2.4.8 Tag Comment

The setting of the tag comment may be omitted. Nothing is set by default.

G2.4.9 Button1, Button2

The button colors can be specified. The default setting for each label is “R” (red). The
following shows the available selections.

G2.4.10 Level
Security level may be set from level 1 to level 8. Level 4 is the default security level
set for the function blocks.
G2.4.11 Tag Mark

This mark indicates the tag priority level of the displayed function block.
Tag mark
Action type 1 5 2 6 3 7 4 8

O: required
G2.4.12 Upper Window

An upper window can be specified for each function block and connection I/O in the
System Builders beforehand.

G2.4.13 Help
There are system-fixed help dialog and user-definable help dialog for defining help
message.
The setting is optional. The help message may be identified by assigning the help
message number a unique ID.


G3. INPUT/OUTPUT FUNCTIONS (FFCS)

Fieldbus I/O.

The input and output interfaces consist of Software I/O, Process I/O, Communication I/O
and Fieldbus I/O. A field control station can access internal and external data via these
I/Os.

G3.2 Process Input/Output (FFCS)

The I/O units used by process control stations vary with the FCS models, I/O module
location, and communication bus and so on.
Process I/O stands for the interface for the signal communication between Field devices
and field control station. An FCS receives signals from field process detection devices
and sends control signals to field control devices.
The installation types of FFCS process I/O modules are as follows:
• The process I/O modules are directly installed to the same rack of Field Control Unit
(FCU).
• The Process I/O modules are installed to the local node, which is linked to the Field
Control Unit (FCU) through ESB (Extended Serial Backbord) bus.
• The process I/O modules are installed to the remote node, which is linked to the
Field Control Unit (FCU) or linked to the local node through ER (Enhanced remote)
bus.
The installation of I/O modules in FCU, local node and remote node are illustrated as
follows:

G3.3 Creating a New Node: FFCS

When the station type of an FCS is KFCS2, KFCS, FFCS, LFCS2 or LFCS, a node for
installing an I/O module must be created prior to creating an I/O module.
A node for holding I/O modules can be created.

G3.3.1 Type
Two selections, Local and Remote, are available for Type.
Specify the type of a node to be created.
• For the I/O Modules Inserted in the Slots of FCU

The node for the I/O modules inserted in the slots of FCU is defined as a local
node and the node number is 1. This is fixed and cannot be redefined.
• A Local Node Extended From FCU

When creating a local node extended from FCU, the ESB bus couple modules
(EC401) must be available in the 7th and 8th slots of FCU. In this case, the 7th
and 8th slots of the FCU should not be defined for any other I/O modules.
If the 7th and 8th slots of FCU are defined for other I/O modules while creating a
new local node, a warning dialog box will be displayed.
• A Remote Node Extended From A Local Node

When creating a remote node extended from a local node, the ER bus coupler
Modules (EB401) must be available in the local node. When creating a new
remote node while no ER bus couple module (EB401) has been defined on the
local node, a warning dialog box will be displayed.
G3.3.2 Node
The node number is used to identify a node unit.
Specify a node number between 1 and 4. The node number 1 is reserved for the
node that holding the I/O modules inserted in the slots of FCU.
The nodes extended form this node can be numbered in between 2 and 4.
G3.3.3 Remote Node

Select the installation position of the EB401 (ER bus interface master module) to
which a remote node is to be connected. Specify this item only when the node type is
remote. The installation position is expressed in the following format:
NODEn\sEB401
n: Node number
s: Slot number
G3.3.4 Power Supply Unit - Dual-Redundant Power Supply

Specify whether or not to make the power supply unit dual-redundant for the
extended node. For the node 1 (the node that holding the I/O modules in the slots of
FCU) the power supply capacity cannot be changed. Since the power supply capacity
is already determined when creating the FCU.
To make the power supply unit dual-redundant for an extended node, check this
check box.
By default, this check box is checked (dual-redundant power supply unit).

G3.3.5 Power Supply Capacity - Power Supply Unit

The power supply unit has two options, 80W or 40W. When using 80W power supply
unit, up to six modules (*1) which can supply power to field transmitter can be
installed in one node unit.
If 40 W power supply unit is used, the external power supply is required when the I/O
modules are providing power to the field transmitters. In this case, check the check
box of [24VDC from External Power Unit]. If the installed I/O modules do not supply
power to the field transmitters, do not check the check box of [24VDC from External
Power Unit]. Thus the 24VDC will not be supplied to the field transmitters.

Enter the component number within eight single-byte characters. This field is blank by
default.
The component number is a number assigned to a cabinet that houses an FCS. This
number is used to indicate the connecting source and destination of each cable when
the cables are wired.
The specification of the component number may be omitted.
G3.3.7 Node Number

Enter a comment on the node within 24 single-byte or 12 double-byte characters.
This field is blank by default. The specification of the node comment may be omitted.

G3.4 Creating a New I/O Module: FFCS

Input and output modules for the FCS can be created.
An I/O Module can be created from System View, right click on [NodeX]
[Create New] [IOM].
NOTE:
G3.4.1 Installation Position – Slot, High Speed Read, IOM Comment

There are two tabs on the Create New IOM dialog box. [Type and Position] tab and
[Set Details] tab. The setting items in the tabs may vary with the types of module.
• Type and Position tab:

IOM Type, Installation Position, Duplicate Next Card, Output Type and High
Speed Read options can be selected. IOM comment text can be entered on this
tab.
• Set Details tab:

The detailed settings of each IOM can be set on this tab.

The following table lists the types of I/O modules:

G3.4.2 Duplicate Next Card

After checking the option “Duplicate Next Card,” a duplicated IOM (sIOM name Dup)
is created. If uncheck this option, the duplicated IOM (sIOM name Dup) will be
removed.
The properties of the duplicated IOM (sIOM name Dup) can not be modified.
The property sheet and the contents in the property sheet can not be accessed.
When the original IOM is modified, the same modification will be automatically
duplicated to the duplicated IOM (sIOM name Dup).

G3.4.3 Output Type

Output type can be specified to the analog input/output modules and analog output
modules. Different output type makes the output to the modules or to the EB401 at
different timings.
Output in a lump: Output when all highest scan function blocks in the FCS complete
their processing.
Output immediately: Output when the connected function block is performing output
process.
Function blocks send their output data to process I/O image at the time of the function
blocks performing output processing.
By comparing the outputs with the I/O memory image, the processor unit puts the
difference to the output modules in the local nodes, and the output modules and
remote node communication interface modules (EB401) inserted in the slots of FCU
at the following timing:
The output data in the EB401 sent from process I/O image are periodically written to
remote nodes.
For analog output in KFCS2, KFCS or FFCS:
• The timings for writing the output data in process I/O image to I/O modules vary
with the designated options [Output in a Lump] and [Output immediately].
When option [Output in a Lump] is designated, the output data are written from
process I/O image to I/O modules at the completion of the highest scan of
function blocks.
When option [Output Immediately] is designated, the output data are written from
process I/O image to I/O modules right after the data are outputted from the
function blocks.
For contact output in KFCS2, KFCS or FFCS:
• The contact output data are written from process I/O image to I/O modules at
the completion of the highest scan of function blocks.
The highest scan period means that if the FCS is applied with High-Speed scan,
the High-Speed scan is the highest scan of FCS, and otherwise the Medium-
Speed scan is. If the FCS is applied with basic scan only, the basic scan is the
highest scan period.
When option [Output immediately] is designated, it takes 1 or 2 milliseconds of

processor unit to perform the task of writing from process I/O image to I/O
modules, thus the CPU load is added.
It is recommended to choose [Output in a Lump] option instead of choosing
[Output immediately] option unless it is necessary. With [Output in a Lump]
option, the output data can also be sent from process I/O image to I/O modules at
high-speed scan period if the high speed scan is specified.

When check the option box [High Speed Read], CPU reads the data at high speed
from the I/O module. However, the I/O modules for communication with remote
nodes, and the I/O modules for Fieldbus communication, High Speed Read option
are not available.

G3.4.5 IOM Comment

Up to 24 alphanumeric characters or up to 12 double-byte characters can be put as
IOM comment text. The IOM comment can be omitted. There is no comment text by
default.
G3.5 Creating a New EB 401 (ER Bus Interface Master Module : FFCS
Create a new EB401 (ER bus interface master module) for connecting a remote node in a
local node. While selecting the FCS folder - IOM folder - NODExx folder in the data tree
section of System View, select [Create New] - [IOM] from the [File] menu. The Create
New IOM dialog box will be displayed:
G3.5.1 IOM Type (Type and Position Tab)

Specify the category and type of the IOM. For Category, select [Remote Node
Communication] from the list. When [Remote Node Communication] is selected for
Category, [EB401 ER Bus Interface Master Module] will be entered automatically in
the Type field.
G3.5.2 Installation Position (Type and Position Tab)

Specify the number of the slot in which the EB401 will be installed. Specify an odd
number. Another I/O module can not be installed in the slot at the right of the slot in
which the EB401 has been installed.

G3.5.3 Duplicate Next Card - Remote Node Communication (Type

and Position Tab)
The ER bus can be made dual-redundant by installing two EB401 cards. Install the
dual redundant EB401 card in the adjoining even slot at the right.
To make the ER bus dual redundant, check [Duplicate Next Card]. When it is
checked, a file named slot number EB401Dup will be created. This check box is
unchecked by default.
G3.5.4 Maximum Number of Nodes (Set Details Tab)

Specify the maximum number of remote nodes to be connected to the EB401. Select
from 2, 4 and 8. The default setting is 4.

G3.5.5 Communication Protocol (Set Details Tab)

Specify the communication protocol between the EB401 and the node. Select either
[Constant Sending Period] or [Wait for Receiving]. The default setting is [Wait for
Receiving].
Do not change the default setting unless it is necessary to do so.
[Constant Sending Period] starts the next transmission at every [Communication
Basic Period] even when the response to the previous transmission has not been
completed.
Therefore, even if one node does not respond, it will not affect the data update
periods of other nodes.
[Wait for Receiving] starts the next transmission only when the response to the
previous transmission has been received or when [Node No Response Monitoring
Time] has been reached.
G3.5.6 Communication Base Period (Set Details Tab)

This item is set when [Constant Sending Period] is specified as the communication
protocol.
Set the communication basic period between the EB401 and the remote node within
the range from 10 to 1000 msec. The default setting is 10 msec.
G3.5.7 Node Response Timeout (Set Details Tab)

When the time it takes for the EB401 to start transmission until it completes reception
exceeds the value set in [No Response Timeout], that node is judged to be not
responding.
Set the node response timeout according to the table below. If a remote node is
connected via an optical repeater, add 6 milliseconds to the node response timeout
as compensation for the transmission delay time due to the optical repeater.
G3.5.8 Number of Retries upon Node Response Timeout (Set

Details Tab)
Set the number of retries for communication to a non-responding node within the
range from 0 to 7 times. The default setting is 3.

H. SOFTWARE INPUT/OUTPUT FUNCTIONS

Software inputs/outputs are virtual inputs/outputs that are provided by the FCS’s internal
software.
Two types of software inputs/outputs are available:
• “Internal Switch”
Used to exchange logical values between function blocks and other application functions,
• “Message Outputs”
Used to inform the occurrence of an event.
YOKOGAWA SINGAPORE TRAINING CENTRE Page H1 of H34

The software inputs/outputs that can be referenced and set from the sequence control blocks
are shown in the table below:

H1. Identification of Software Input/Output

Software inputs/outputs are identified by their element serial numbers.
The classification of element numbers for the CS 3000 is shown below:
Software input/output element numbers of CS 3000 are shown in the table below:

Software input/output element numbers of CS 1000 are shown in the table below:
H2. Internal Switches

The following internal switches are explained:
• Common Switches
• Global Switches
H2.1 Common Switches (%SW)

manipulation.
switches. They are used to indicate the different statuses of the FCS.
Common switches in the CS 1000 with element number %SW0201 to %SW1000 may
be freely defined by users.
Common switches in the CS 3000 with element number %SW0201 to %SW4000 may
be freely defined by users.
● PFCS/SFCS
The data for common switches %SW0001 to %SW0007 that are used as the station
start ID switches and %SW0031, which is used as an extension common switch in a
PFCS/SFCS, are written by users.
Common switches %SW0097 to %SW0200 are valid only when the extension
common switch is set to 1 (valid).

● LFCS/LFCS2, KFCS/KFCS2, FFCS, FFCS-L

Only the data for common switches %SW0001 to %SW0007 that are used as station
start ID switches in a CS 3000 LFCS/LFCS2, KFCS/KFCS2 and FFCS, are written by
users.
For more detailed information on System Common Switches, please refer to Field
Control Station Basics (IM 33S01B30-01E) Common Switch tab.
H2.1.1 Condition Testing and Status Manipulation

When common switch ON/OFF status is applied as a condition test signal to a
sequence table block and logic chart block or to a designated function block in
sequence connection via its signal input terminal, the testing of the condition
establishment is referred to as common switch condition testing.
The syntax form for condition testing is shown below:
When common switch ON/OFF status is applied as a manipulated signal from a

sequence table block and logic chart block or from a designated function block in
sequence connection via its signal output terminal, the common switch status
reflecting the manipulated signal status is referred to as common switch status
manipulation.
Two types of manipulation signal outputs are available: a “latched” type and a
“non-latched” type.
The syntax form for status manipulation is shown below:

H2.1.2 Common Switch Builder

Common Switch Builder can be accessed from System View, [FCS0101]
[SWITCH] double click on [SwitchDef].
Note: [SwitchDef] - %SW0001 ~ %SW1000

[SwitchDef2] - %SW1001 ~ %SW2000
● Element Number
Name Element Number Element Number Convention

Common Switch %SWnnnn nnnn: Serial no.(0001 to 4000)
(0001 to 1000) (for PFCS)
● Tag Name
Tag names may be defined by users.
A user defined tag name is a string up to 16 alphanumeric characters (capital
letters only for the English alphabet), [ _ ] (underscore) and [-] (hyphen). However,
a [ _ ] (underscore) and [-] (hyphen) may not be placed at the beginning of a tag
name.
Here is an example of a tag name:

Example: FIC1000
● Tag Comment
An explanatory description for each function block can be defined with up to 24
single-byte characters or 12 double-byte characters.
● Switch Position Label

Up to 64 sets numbered Nos.1 to 64 of switch position labels can be defined for
one project. One set consists of four labels (label 1, label 2, label 3, and label 4).

● Label
There are two types of label display formats for switch position; direct formal and
reverse format.
The figure below is an example of the label for switch position specified [ON,,OFF,
ON] in direct format.
● Btn1, Btn2
Any of the following 16 colors can be specified for each switch position label:
The button color changes when the button (switch) is pressed.
● Level
Security level may be set from level 1 to level 8. Level 4 is the default security
level set for the function blocks.

● Tag Mark
The table below shows the relationship between tag marks and tag priority levels:
Tag mark
Action type 1 5 2 6 3 7 4 8

O: required
● Upper Window
An upper window can be specified for each function block and connection I/O in
the System Builders beforehand. The specified upper window can be called up by
pushing the graphic button or the upper graphic key while the function block is
selected.
● Help
The user-definable help dialog messages are treated as dialog names that
may be specified as HW0001 to HW9999.

H2.2 Global Switches (%GS)

A global switch is an internal switch with the same logical value on all stations in the
same domain.
Up to 256 write-enable global switches can be assigned to each station.
The defined value is broadcasted to each station in the system via V net scan
transmission when data transfer to other stations is defined at Scan Transmission
Definition on the FCS Constants Builder.
When the values of global switches under the control of other stations are sent via
scan transmission, the global switch on the present station is updated when data
receipt is defined at Scan Transmission Definition on the FCS Constants Builder. The
values of global switches are updated at the same time mostly on all stations in the
system. The values are updated by 100 msec, which is fixed.

To transfer/receive the values of global switches between stations, the scan

transmission definitions on the FCS Constants Builder must be defined.
● Present Station Definition – Self Station

• Present station buffer size:

Define 32 (bytes) to transfer the values, or 0 not to transfer them.
The default is 0.
● Station Definition - Station

Define whether to receive the values of global switches under the control of other
stations if transferred.
• Station definition type:

Choose “0: Not communicate” or “1: Individual Station Communication.”
The default is 0.
When you choose “Individual Station Communication,” define the communication
buffer size to receive data from its station every sender.
• Individual Station Definition:

• When you duplicated an FCS on System View, redefine Station Definition of

Scan Transmission Definitions.
• If the value smaller than 32 bytes is defined for the buffer size of the present
station, global switches will not work.

H2.2.1 Condition Testing and Status Operation

Condition testing for global switches is to test whether conditions are satisfied:
The ON/OFF state or data status of global switches are tested as conditional
signals of sequence table blocks and logic chart block or function blocks for which
sequence connection is specified to its input terminals.
The following formats must be used for condition testing for global switches:
Status operation for global switches is to change the ON/OFF state of global
switches by action signals from sequence blocks and logic chart block or function
blocks for which sequence connection is specified to its output terminals.
Status operation is applicable to global switches of present station only.
There are two output types of action signals for global switches: “latched type”
and “non-latched type.”
The following formats must be used for status operation of global switches:

H2.2.2 Global Switch Builder

Global Switch Builder can be accessed from System View, [FCS0101]
[SWITCH] double click on [GSwitchDef].
● Element Number
Name Element Number Element Number Convention

Global Switch %GSnnnmm nnnn: Serial no.(001 to 256)
mm: Station no.(01 to 64)
● Tag Name
Tag names may be defined by users.
A user defined tag name is a string up to 16 alphanumeric characters (capital
letters only for the English alphabet), [ _ ] (underscore) and [-] (hyphen).
However, a [ _ ] (underscore) and [-] (hyphen) may not be placed at the beginning
of a tag name.
Here is an example of a tag name:

Example: FIC1000
● Tag Comment

Up to 64 sets numbered Nos.1 to 64 of switch position labels can be defined for
one project. One set consists of four labels (label 1, label 2, label 3, and label 4).

● Label
There are two types of label display formats for switch position; direct format and
reverse format.
The figure below is an example of the label for switch position specified
[ON,,OFF, ON] in direct format.
● Btn1, Btn2
Any of the following 16 colors can be specified for each switch position label:
The button color changes when the button (switch) is pressed.
● Level
Security level may be set from level 1 to level 8. Level 4 is the default security
level set for the function blocks.

● Tag Mark
Tag mark
Action type 1 5 2 6 3 7 4 8

O: required
● Upper Window
the System Builders beforehand. The specified upper window can be called up by
selected.
● Help
The user-definable help dialog messages are treated as dialog names that
may be specified as HW0001 to HW9999.

H3 Message Output Functions

The contents of the following messages are user-defined and explained here.
• Annunciator Messages
• Operator Guide Messages
• Printout Messages
• Sequence Message Request
• Help Messages
H3.1 Annunciator Messages (%AN)

These special message outputs are used to simulate the annunciator panels of the
instrument panels. Unlike other message outputs, annunciator message outputs store
alarm-occurrence statuses as logical values.
When the alarm occurrence status changes, the annunciator message informs the
HIS of the occurrence or recovery of the message.
When an alarm occurs, the alarm symbol will flash to prompt the operator for
acknowledgement. The alarm symbol will stop flashing once it has been
acknowledged.
Annunciator message outputs are processed at the basic scan cycles only.
H3.1.1 Condition Testing and Status Manipulation

When annunciator message ON/OFF status is applied as a condition test signal
to a sequence table block and logic chart block or to a designated function block
in sequence connection via its signal input terminal, the testing of the condition
establishment is referred to as annunciator message condition testing.
The syntax form for condition testing is shown below.
When annunciator message ON/OFF status is applied as a manipulated signal

from a sequence table block and logic chart block or from a designated function
block in sequence connection via its signal output terminal, the annunciator
message status reflecting the manipulated signal status is referred to as
annunciator message status manipulation.
Two types of condition signal outputs are available: a “latched” type and a “non-
latched” type.
The syntax form for status manipulation is shown below.
In the case of latched annunciator messages, recovery can be made by N-status

manipulation of the sequence table. The following syntax form is for the recovery
of an annunciator message output.
%ANnnnn.PV.H -----N

H3.1.2 Annunciator Builder

Annunciator Builder can be accessed from System View, [FCS0101]
[Message] double click on [AN0101].
● Element Number
Name Element Element Number Convention

Number
Annunciator %ANnnnn nnnn: Serial no.(0001 to 0500)
Message (0001 to1000) (for KFCS2, FFCS, FFCS-L
or LFCS2)
(0001 to 0200 (for PFCS)
● Message
Annunciator message is used to notify the operator of errors in the process.
Up to 24 alphanumeric characters (12 double-byte characters) may be defined in
the Annunciator Message Builder by user.

The occurrence of annunciator messages is shown as below:
● Tag Name
A tag name can be assigned to each annunciator element number. A tag name
defined here can be used in place of the annunciator element number
(%AN000n) that has been assigned that tag name.


The switch position labels refer to character strings displayed as labels for
switches.
● Label
Specify direct format or reverse format.
● Level
Select a security level from level 1 to 8.

● Tag Mark
Select a tag mark type from the following 8 types.
Tag mark
Action type 1 5 2 6 3 7 4 8

O: required
● Alarm Level
The Alarm Processing is a message processing function performed by the HIS
when alarm occurs during plant operation.
Select an alarm processing level from [High], [Medium], [Low], [Logging],and
alarm levels defined in the Alarm Processing Table Builder.
● Upper Wndow
When an annunciator message occurs and if it is required to call up a related
window to the alarm acknowledged, define that window as upper window.
With the upper window defined, selecting the displayed annunciator message and
then pressing the upper window call-up button, or the upper window call-up key
on the operation keyboard can display that window.
the System Builders beforehand.
● Help
There are system-fixed help dialog and user-definable help dialog for defining
help message.
The setting is optional. The help message may be identified by assigning the help
message number a unique ID.

● Upper Equipment Name

The upper equipment name refers to the name of the equipment object located in
the next upper layer of an equipment object in a plant hierarchy. Specifying an
upper equipment name via the Plant Hierarchy Builder determines the location of
an equipment object in the plant hierarchy.
H3.2 Operator Guide Messages

Operator guide message outputs alert the operator to the operator guide window in
real-time situations.
The syntax form for an operator-guide message output specification is shown below.
H3.2.1 Operator Guide Builder

Operator Guide Builder can be accessed from System View, [FCS0101]
[Message] double click on [OG0101].
● Element Number

Number
Operator %OGnnnn nnnn: Serial no.(0001 to 0200)
Guide (0001 to0500) (for KFCS2, FFCS or LFCS2)
Message (0001 to 0100 (for PFCS)
● Message
Define the character strings to transmit as an operator guide message.
Up to 70 alphanumeric characters are used.

The occurrence of operator guide messages is shown as below:
● Color
Display color of character strings in operator guide messages
(Default color: white (W))
● Related Window Name

Name of linked window
With the related window defined, clicking the message displayed in the Operator
Guide Message window will display the related window in the defined format.

● Label
User-defined labels are names that can be defined for the analog process I/O and
for messages. User-defined label may be defined up to 16 alphanumeric
characters. The format for a user-defined label is given as below.
Labels may be omitted.
H3.3 Printout Messages

Print messages are triggered by the Sequence Control Function to print out the
message to indicate certain timing of the process.
When a print message request is sent from a field control station to an HIS, the
Operation and Monitoring Functions print the character string that corresponds to the
message number, then saves the print message to the historical message log file.
The syntax form for a print message output specification is shown below:
H3.3.1 Printout Builder

Printout Builder can be accessed from System View, [FCS0101] [Message]
double click on [SD0101].

● Element Number

Number
Print %PRnnnn nnnn: Serial no.(0001 to 0200) (for PFCS)
Message (0001 to0400) (for KFCS or LFCS)
(0001 to 1000) (for KFCS2, FFCS, FFCS-L,
or LFCS2)
(0001 to 0100 (for PFCS)
● Message
Up to 80 alphanumeric characters (40 double-byte characters)may be defined as
print message. When printing process data, the data may be indicated by
symbol. The data values are printed in the order of data items (data1, data2,
data3).
The occurrence, transmission and output of print messages are shown as below:
● Data1, Data2, Data3

Data may be defined in the format of TagName.DataItem.
For array data,TagName.DataItem [subscript1,subscript2 ] may be specified. The
data may be specified less than 34 alphanumeric characters.

● Format1, Format2, Format3

Specify the format of the print message. Integer data value and the real number
data value are right justified and the character strings are left justified when
printed out.
The print format is as follows:
[Leading Zeros ] [Total Digits ].[Digits after DP ] [Conversion ]
The table below shows the default and user-defined print formats:
● Label
User-defined labels are names that can be defined for the analog process I/O and
for messages. User-defined label may be defined up to 16 alphanumeric
characters. The format for a user-defined label is given as below.
Labels may be omitted.
H3.4 Sequence Message Request

The sequence message request is sent by the Process Sequence Control Function at
certain process timing to an HIS to execute certain Operation and Monitoring
Functions.
After the Operation and Monitoring Functions’ execution, the request messages are
logged into the historical message log files.
Sequence message requests enable the operator to start or run the HIS functions
from an FCS.
The syntax form for a sequence message request specification is shown below:

H3.4.1 Sequence Message Request Builder

Sequence Message Request Builder can be accessed from System View,
[HIS0164] [Configuration] double click on [MsgReqDef].
In the above example, the Process Alarm window displaying the process alarm
generated at station 01 is called up as a medium-size window.
● Number

Number
Sequence %PRnnnn nnnn: Serial no.(0001 to 0200)
Message (0001 to0100) (for PFCS)
Request

● Function
The following functions may be specified to a sequence message request:
• Calling up windows
• Executing a program assigned to the function key
• Operation keyboard LED ON/OFF/flash
• Run a designated program
• Multimedia
• Calling up a panel set (*1)
• Printing reports
The trigger of request messages is shown as below:
● Station Name
The sequence message request is managed in an HIS.
Usually, ALL is specified in the station name item thus, the request received from
all FCSs may be executed.
If a station name is designated, only the request from the designated station is
executed.

H3.5 Help Messages

Help messages guide the user through monitoring the operation of the plant.
These messages are either pre-defined in the system or definable by the user and
are displayed in help dialog boxes.
They are system alarm help, user-defined help and system window help.
● System Alarm Help

This is a help message that provides detailed information about the system alarm
message.
The system alarm help is pre-defined in the system.
Using the message number of the system alarm message as a keyword, search for
the corresponding system alarm help can be performed.
● User-Defined Help
This is a help message that the user can freely define. The user can define help
messages to explain the function and operating procedure for user-defined windows
or help messages to explain the function block.
The user can search for user-defined help by entering the window name, tag name or
help number as the keyword.
The user-definable help message is defined in the Help Message Builder.
Define a number between HW0001 to HW9999 as help number.
The maximum size of one help message is 21 lines; each line can contain 70 single-
byte characters.
Help messages are defined on the Help Builder. Help Builder can be created from
System View, [HIS0164] [Help] Right click [Create New Window] [OK]

Double click on [HW0001] to edit the help file.
[File] [Download] to the [HIS0164].
The Help dialog box may be called up from an active operation and monitoring
window, or from a window in which a function block is displayed or a system alarm
message is selected.
The dialog box will be closed simultaneously when the operation and monitoring
window from which the dialog box was called up is closed.
Only one Help dialog box may be called up for one operation and monitoring
window.
● System Window Help

These are help messages that explain the functions of the system window. The
system window help is pre-defined in the system.
Using the window name as keyword, the corresponding system window help can be
searched.

H4 Message Types
Each message has a number to identify the message type.
The following messages have system-fixed identification numbers and contents:
• System Alarm Messages

• Process Alarm Messages
H4.1 System Alarm Messages

System alarm messages notify the operator of the hardware errors in the control
station or an HIS as well as errors in communication. The type and contents of the
system alarm are predetermined.
Alarm messages are displayed in the System Alarm window.
The trigger of system alarm messages is shown as below:

H4.2 Process Alarm Messages

Process alarm message is used to notify the status of a process alarm to the
operator.
The process alarm notifies operator of the occurrence and recovery of abnormality in
the process. The type and contents of the process alarm are predetermined.
A process alarm message is the general term for messages that are output
corresponding to the process alarm.
The annunciator message is included in the process alarm category. User can define
the trigger signal and contents of the annunciator message.
The occurrence of a process alarm message is shown as below:

H5. Questions
Q1. What is the main difference between Process I/O and Software I/O?
Q2. What is the function of a Software I/O switch?
Q3. Name the 2 types of Software I/O switches.
Q4. What is the difference between a Common Switch and a Global Switch?
Q5. Describe the functions of the following message outputs:
• Annunciator Messages
• Operator Guide Messages
• Printout Messages
• Sequence Message Request
• Help Messages
• System Alarm Messages
• Process Alarm Messages
Q6. Which type of alarm priority have repeated warning alarm feature?

H6. Exercises
1. Configure a user-defined common switch with the following display:

2. Call up sequence block [MSG]. The annunciator messages, operator guide

messages and printout messages are configured in this sequence table as
outputs.
a) Start Test Function of [FCS0101] of project [TRAIN3] and call up tag

MSG TABLE.
b) In the MAN mode, adjust the MV value of FIC 200 to approximately 50.
c) Adjust the LL of [FIC200] to 20 and PL to 25.
d) Change the mode of [FIC200] to AUT.
e) Bring the SV of [FIC200] to 24 i.e. below PL.
f) Observe what happens when the PV drops below LO setting.
g) Check to see if the message generated is correct.
From the above sequence block [MSG] , annunciator messages in figure 1, operator
guide messages in figure 2 and printout messages in figure 3 will appear when the
[FIC200] is in LO alarm.
Figure 1: Annunciator Message

Figure 2: Operator Guide Message
Figure 3: Printout Message
Before proceeding to the next chapter, resolve all alarms and change the mode of
[MSG] to MAN.

I. CONTROL DRAWING BUILDER

The Control Drawing Builder is used to configure the basic control functions of the FCS. With
the Control Drawing Builder, operations such as registering function blocks in the drawing file
and determining the flow of data between function blocks can be performed graphically.
• CS 1000 contains 50 control drawings.
• CS 3000 contains 200 control drawings.
The Control Drawing Builder can be started by selecting a file from the System View.
[FCS0101] [Function Block] double click on [DR0002].
YOKOGAWA SINGAPORE TRAINING CENTRE Page I1 of I11

I1. Control Drawing Environment

With the Control Drawing Builder, the basic control functions of the FCS can be
configured in the window by combining objects.
Text
Function
Block
Symbol
Wiring
Up to 100 function blocks can be defined in one control drawing (*1).
I1.1 Function Block

The object that represents the function block is called function block symbol.
Terminal name
Tag
name
Function Block Type
Function Block Symbol

I1.2 Text
This object represents an arbitrary character string.
I1.3 Wiring
This object represents the flow of data between function blocks or between a function
block and a data link block.
I1.4 Data Link Block

As with the function block, the object that represents the data link block is called data
link block symbol. The data link block is used when connecting a function block with
another function block or connecting a process I/O or software I/O.
Two types of data link blocks are available: I/O data link block and external data link
block.
An I/O data link block can connect to a process I/O or software I/O.
An external data link block can connect to a function block defined in other control
drawings or a function block defined on other control stations.
I/O data link block External data link block

I2 Toolbar Buttons
I2.1 Drawing Toolbar
Select Mode
Text
Function Block

Wiring
This object represents the flow of data between function blocks or between a function
block and a data link block.
Click on point a and double click on point b. Wiring is drawn automatically with a
green bold line. As seen above, the colour of the wiring is purple.
For wiring drawn manually from point a to point b, the colour of the wiring will be light
blue.

The two methods for drawing wiring are shown below:
• Automatic wiring
• Manual wiring
• Automatic Wiring
Seleect button at the toolbar.
Specify two points representing an output connection terminal and an input

connection terminal of block symbols in the drawing pane. The wiring route is
automatically determined and the wiring is drawn. The color of the wiring is
purple.
• Manual Wiring
Select button at the toolbar.
Specify an output connection terminal, the point(s) of wiring connection, and input
connection terminal of a symbol block. Wiring will be drawn along the specified
points. The color of the wiring is light blue.
• Branching of the Wiring

Multiple destinations can be specified for a function block or data link block. In
this case, the wiring will automatically branch when it is drawn.

Wiring that has already been drawn can also be modified to branch off. In the
wiring already drawn, specify the point where branching should occur and specify
the wiring destination.
• Line Type for Wiring

Select the line type for forward wiring or backward wiring.
Forward wiring means wiring that follows the control sequence in the control
drawing.
Backward wiring means wiring in the reverse direction from the control sequence.
The forward wiring permits the connected blocks to execute the control action in
the same scan period.
The backward wiring makes the lower stream access the upper steam’s previous
scan signal. For example, in the above drawing, the process of A is behind the
process of B, so that B can only process the signal of A availed from the previous
scan.

• Changing Terminal Name

Clicking on the terminal name entry area of a block symbol in the drawing pane
changes the status of the area and entering text becomes possible. After the
terminal name is entered from the keyboard and the [Return] key pressed or
another area clicked, the entry is confirmed.
A pop-up menu appears when the right mouse button is clicked inside the
terminal name entry area. The terminal name can also be selected from this
menu.
Figure: Changing Terminal Name from Pop-Up Menu

• Displaying Block Comment

Select a block symbol then click the right mouse button inside the block symbol
area, and select the item to be displayed from the pop-up menu that appears.
The content of the detail definition corresponding to the selected item is displayed
as a block comment.
However, if nothing is set for the selected detail definition item of the function
block, the item name of the detail definition will be displayed.
Example of Block Comment Tag comment
No block comment can be displayed for data link blocks.

I3. File Import and Export
I3.1 Text File Import and Export

On the Control Drawing Builder, the information of a control drawing can be exported
into a text file, vice-versa, a text file of control drawing can be imported. Thus the
control drawing files can be created by external tools or exported files from the builder
can be used.
Nevertheless, the parameters of the function blocks can not be imported or
exported.
The information of a control drawing can be exported from

[File] [External File] [Export]
I3.2 CS Source File Import

A CENTUM CS control drawing source file can be imported and reused as CS 1000
or CS 3000 control drawing file.
Nevertheless, CENTUM CS can not use the text file exported from CS 1000 or
CS 3000 Control Drawing Builder.

I4. Exercise
1. Open [DR0060] and create the following control drawing of a cascade loop.
Make sure that the necessary I/O modules are defined. [Save] to check for errors.


J. REGULATORY CONTROL FUNCTION

The regulatory control function performs control computation processing using analog
process values for process monitor and process control. The function blocks that provide the
regulatory control function are referred as “regulatory control blocks.”
The regulatory control blocks support the following types of processing: input processing,
control computation processing, output processing and alarm processing.
The regulatory control is one of the basic controls in the FCS and performs control
computation processing to monitor and control processes.
YOKOGAWA SINGAPORE TRAINING CENTRE Page J1 of J37

This chapter explains the function of the regulatory control block in detail.
The figure below shows a function block diagram of a general regulatory control block:
The regulatory control blocks have the following four processing functions:
Input Processing
Receives a signal from the input terminal and outputs a process variable (PV).
Control Computation Processing

Performs control computation processing by reading the process variable (PV) and outputs a
manipulated output value (MV).
Output Processing
Reads the manipulated output value (MV) and outputs the result of control computation
processing to the output terminal as an output signal.
Alarm Processing
Detects an abnormality in the process variable (PV) or manipulated output value (MV) and
notifies the operation and monitoring functions.

J1. Function Block Processing Functions

Upon creation of the function block, some of the processing function parameters are
specified in different panels.
1. Tuning Panel
Some of the parameters of the processing function can be specified in the tuning
panel of the function block, for example, SV, MV, alarm settings and tuning
parameters. It also depends on the security level of the individual blocks.

2. Function Block Properties

In the control drawing builder, highlight the function block and right click on
[Properties] to display the following window that allows further function parameters to
be specified.
3. Function Block Detail Specifications
In the control drawing builder, highlight the function block and click on
The detail specification window appears for more properties of the function block to
be specified. Notice that the different tab headings contains the different
specifications.

J2. Detail Specifications of PID Block

Different function blocks have different item specifications. For training purpose, we will
use a common function block – PID as a reference for our explanation of the individual
parameters.
J2.1 BASIC
● Tag Comment
● Lvl (Security Levels)

Specify the security level for the function block. The security level can be selected
from 1 to 8.
● Scan Period
There are three types of scan periods: basic scan, medium-speed scan (*1) and
high-speed scan.
. Basic Scan
The basic scan is a standard scan period which is common to function
blocks.
The basic scan period is fixed to 1 second. This cannot be changed.
Medium-Speed Scan : KFCS2/KFCS/FFCS/LFCS2/LFCS

The medium-speed scan is a scan period suited for the process control that
requires quicker response than what can be achieved with the basic scan
setting.
Select “200 ms” or “500 ms.” “50 ms”, “100 ms” or “250 ms” can also be used
by direct entry from keyboard.
The default is “500 ms.”
High-Speed Scan
The high-speed scan is a scan period suited for the process control that
requires high speed response.
Select “200 ms” or “500 ms.” “50 ms”, “100 ms” or “250 ms” can also be used
by direct entry from keyboard.
The default is “200 ms.”
● Open/Close Mark
This mark indicates the open/close status of a device in response to manipulated
output.
“OPN” indicates the open status and “CLS ” indicates the close status.

● Input Signal Conversion

The input signal conversion is the function that converts the input signal read
from the input module or other function blocks into process variable (PV) or
calculated input value (RV) according to the signal type.
There are five kinds of common input signal conversion for the Regulatory
Control Blocks and Calculation Blocks.
In addition, there are input signal conversion methods specific to particular
function blocks.
Select from “No Conversion,” “Square Root,” “Pulse-train,” “Control Priority Type
Pulse Train Input”, “Exact Totalization Pulse Train Input” and “Communications”.
The default setting is “No Conversion.”
● Totalizer Time Unit

The following is the computational expression for the integration:
The time scale conversion coefficient (Tk) is set corresponding to the totalizer
time unit.
The totalizer time unit must be set in the same unit as the measurement value
(PV). For example, if the unit of PV is “m3/min,” set the totalizer time unit to
“minute”.
Up to 8 digits for integrator value can be used.

Engineering unit is used.
The totalizer time unit can be defined on the Function Block Detail Builder.
• Totalizer Time Unit

Select “Second”, “Minute”, “Hour”, “Day” or “None”.
The default setting is “None”.
If “None” is specified as the totalizer time unit, integration will not be executed.

● Low-Input Cut
• If the low-input cut value is positive (including 0):

Integration is not executed for the input signal (including negative value) less
than the low-input cut value.
• If the low-input cutoff value is negative:

Integration is not executed for the input signal if the absolute value of the
input signal is less than that of the low-input cut value.
When the integration of the reverse direction flow measurement (negative value
input) is allowed, integration cannot be executed for small flow in either direct or
reverse direction if a negative value is set to the low-input cut value.
The low-input cut value can be specified on the Function Block Detail Builder.
• Totalizer Low-Input Cut Value:
Set the data in the same unit of integrator value (PV), or percentage value for
the PV scale span.
If a percentage value is used, add % after the value.
The default setting is 0 %.
● Control Action
The control action direction function switches between direct action and reverse
action that reflect the increase or decrease of manipulated output value.
• Direct action
The control action in which the manipulated output value (MV) increases as
the process variable (PV) increases, or decreases as the process variable
decreases.
• Reverse action
The control action in which the manipulated output value (MV) decreases as
The process variable (PV) increases, or increases as the process variable
decreases.
● Measurement Tracking
The process variable tracking function prevent the abrupt changes in the
manipulated output value (MV) when change from the manual (MAN) mode to
automatic (AUT) mode, by forcing the setpoint value (SV) to agree with the
process variable (PV).
Characteristics of Process Variable Tracking

When switching from the manual (MAN)mode to automatic (AUT)mode,the
existence of a large deviation is harmful, since it makes the manipulated output
change (MV) very large.
If force the setpoint value (SV)to agree with the process variable (PV)in manual
mode operation via process variable tracking,abrupt Control Action can be
avoided when the mode switches to automatic (AUT).
Suppose a primary loop is in cascade connection and controls in the automatic

(AUT) or cascade (CAS) mode. If the mode of the secondary loop in the cascade
connection switches from cascade (CAS) to automatic (AUT), the cascade
connection becomes open and the control action of the primary side loop can
stop. In this situation, the setpoint value (SV) of the primary loop can be forced to
agree with the process variable (PV) by the process variable tracking function.

● Output Signal Conversion

This process converts the result of calculation process into an output format for
the output modules or other function blocks.
Here is the outline of the output signal conversion processes that are common to
the Regulatory Control Blocks:
No-Conversion Output
The manipulated output value (MV) resulted from the control-calculation
process is No-Conversion output.
Pulse Width Output Conversion

The changes of manipulated output value (_MV) is output after converted into
a pulse width signal.
Communication Output Conversion

The manipulated output value (MV) resulted from the control-calculation
process is converted into the format compatible with the destination
subsystem.

● Tight-Shut and Full-Open Function

In order to tightly shut a valve the manipulated output (MV) can be decreased to a
value smaller than 0% and fully open the valve, while to fully open the valve, the
manipulated output (MV) can be increased to a value greater than 100%.
• Tightly-shut/fully-open:
Choose “Yes” or “No.” The default setting is “Yes.”
• Output Value for tight-shut (Ms):

The actual output value for tight-shut when the manipulated output (MV)
indicates 0%.
Setting range is -17.19 to 117.19 % (5 significant figures). By default, the
tight-shut value is -17.19%.
• Output Value for full-open (Mf):

The actual output value for full-open when the manipulated output (MV)
indicates 100%.
Setting range is -17.19 to 117.19 % (5 significant figures). By default, the full-
open value is 106.25%.
Now we use a current output module as an example to explain how the

actual output current (mA) corresponds to the actual tight-shut output (Ms)
and actual full-open output (Mf).
When the output direction of an analog output module is not reversed, the
actual output current (mA) corresponds to the manipulated values (MV) 0%
and 100% with 4 mA and 20mA.
Output Current = (0.16MV + 4) mA
In this case, we can find out that when the default tight-shut MV is -17.19, the
current output for tight-shut (Ms) will become 1.25mA, while when the default
full-open MV is 106.25, the current output for full-open (Mf) will become
21mA.
If the output direction of the analog output module is reversed, the actual
output current (mA) corresponds to the manipulated values (MV) 0% and
100% with 20 mA and 4mA.
Output Current = (-0.16MV + 20) mA
In this case, we can find out that when the default tight-shut MV is -17.19%,
the current output for tight-shut (Ms) will become 22.75mA (corresponds to
117.19%), while when the default full-open MV is 106.25, the current the
current output for full-open (Mf) will become 3 mA (corresponds to -6.25%).

J2.2 TAG
● Tag Mark
The user can specify whether the priority for each tag mark should be
acknowledged or not.
● Double Authentication
When manipulating the important function blocks, other than the logged-on user,
one more user’s confirmation may be required. In this case, the confirmation may
be performed on the Double Authenticated Confirmation dialog box.
In order to activate the double authentication for confirmation, [Double
Authentication] setting on the Function Block Detail Builder must be set to [Yes]
and the tag mark of the function block must be set as [Important].
There is no requirement that the user of [Name1] is superior to the user of
[Name2] and vice versa. Any users, excluding the user of [Name1] and the
default users (OFFUSER/ONUSER/ENGUSER) can be act as the user of
[Name2] for double authentication.
The user names of [Name1] and [Name2] and reasons for operation (Reason)
are recorded in the operation log message of the Double Authenticated
Confirmation dialog box.
The operation log message on [Name2] is recorded as a part of character strings

typed in for [Reason] of the [Name2]. Therefore, the filtering cannot be performed
by [Name2].

● Status Change Message Bypass

When function blocks such as sequence control blocks change block mode, the
event recording function sends the status change message from FCS to HIS to
inform the operator.
• Status Change Message Bypass:
Select “Yes” or “No.”
The default is “No.”
In case of the sequence table block (ST16), the default is “Yes.”
When status change message is set as Bypass, the message of status change is
not recorded in the historical message file in HIS.
When the status change is performed manually on HIS, the status change
message will all be recorded in the historical message file in HIS regardless the
setting of bypass.
● Upper Window
the System Builders beforehand.The specified upper window can be called up by
selected.
● Help
The user-definable help dialog messages are treated as dialog names that may
be specified as HW0001 to HW9999.
● MV Display on Faceplate
The manipulated output value (MV)may be displayed in percentage (%)or real
amount. The real amount display is the same way as process variable (PV)and
setpoint value (SV) that reflects the amount in a specific engineering unit. When
displayed in percentage (%), the MV is converted into percentage and displayed
in %MV. When %display is defined, the following parameters are displayed in
percentage (%):
MV,OPHI,OPLO,MH,PMV
● CAS Mark
This mark indicates that the function block displayed on the instrument faceplate
may be set to cascade mode.
However, the definition may be set AUTO to let system decide according to
function block’s real connection.
● Kind of CAS Mark

When connecting terminals between an FCS and an APCS, it is possible to use
an APCS mark that indicates a function block on the FCS side receiving output
from the APCS.
● CMP Mark
This mark indicates that the block mode of the function block displayed on the
instrument faceplate is RCAS (remote cascade)or ROUT (remote output).

● Scale Reverse Display (Scale Low/High Limit)

When the reverse scale display is specified, the low limit is displayed at the top of
the scale and the high limit at the bottom of the scale.
● MV Reverse Display
In the standard display of a function block faceplate, the high limit displays at the
top and the low limit displays at the bottom. MV reverse-display will display
upside-down. In this case, the pointer of manipulated output value (MV) behaves
oppositely in accordance to the digital value of parameters.
This designation only changes the display of function block’s faceplate and does
not relate to the actual output value.
● Index
This function displays indexes that show the permissible range of the manually
manipulated values at the normal operation.
The manipulated output index is only available for Regulatory Control
Blocks.
This function displays two indexes in the manipulated output value (MV) scale on
the operation monitoring window of the operation and monitoring function. These
are called the manipulated output indexes.
They can be used as manipulation guides in the manual mode, or as guides for
verifying normal status in the automatic mode.
● Scale – division
The scale divisions may be specified as 1, 2, 3, 4, 5, 7 divisions. Auto-division
may be used.
● Upper Equipment Name

The upper equipment name refers to the name of the equipment object located in
the next upper layer of an equipment object in a plant hierarchy.
Specifying an upper equipment name via the Plant Hierarchy Builder determines
the location of an equipment object in the plant hierarchy.
J2.3 INPUT
● Process Variable Range
The engineering unit and scale range of raw input signals (RAW) input to an IN
terminal agree with the engineering unit and scale range of data at the connected
destination of the IN terminal. A raw input signal turns into a process variable
(PV) after input processing.
High and low limits:

Numerical values of seven digits or less, where the sign or decimal point
takes one digit each.
The default is “100.0” for the upper limit and “0.0 ” for the lower limit.

● Engineering Unit Symbol

The engineering unit symbol is a unit symbol attached to a data value including a
flowrate and pressure, and is used on all the projects.
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 or three double-byte characters.
● Input Signal Filtering

The digital filter is a function in which the input signal is processed by the first-
order lag filter in order to reduce input signal noise.
In the Regulatory Control Blocks, the filtering process is executed for input signal
(main input signal) read from the IN terminal only, following input signal
conversion.
There are three kinds of digital filter coefficients.

• Digital Filter Coefficient 1: 0 to 1.00 (0.01 unit)
The defaults for these digital filter coefficients are set to the values indicated
below.
constant is 1 second)

(When the digital filter coefficient is 0.75 and scan period is 1 second, the
time constant is 3 seconds)

(When the digital filter coefficient is 0.875 and scan period is 1 second, the
time constant is 7 seconds)

● PV Overshoot
Select “Overshoot PV” or “Holding PV.”
The default setting is “Holding PV.”
When the data status of input signal becomes invalid (BAD), the PV overshoot
function overshoots the process variable (PV), or upscales it to scale high-limit or
downscales it to scale low-limit.
The PV overshoot is supported only for the Regulatory Control Blocks.
Since the PV overshoot is for process input signal, it is executed when the I/O
connection type is process I/O.
The following table shows the relationship between the cause for invalidity (BAD)
and process variable (PV) when the PV overshoot is used.
With “Holding PV,” when the data status of process variable (PV) becomes
invalid, the last good process variable is held.
Furthermore, when the input signal is not a process input signal, the operation
becomes “Holding PV” even though “Overshoot PV” is specified.
J2.4 ALARM
● Alarm level
Designating an alarm processing level to a function block or an element, the
alarms from the function block or the element will have the designated priority
and display the designated color.
The definitions for level 1 to level 4 are fixed for a whole system.
The alarm priorities and colors for level 5 to level 16 can be defined by users.
The alarm priority defined for the first 4 levels of alarm processing are:
• Level1
All alarms initiated from the function block or the element are “High-priority
alarms.”
• Level2
All alarms initiated from the function block or the element are “Medium-priority
alarms.”
• Level3
All alarms initiated from the function block or the element are “Low-priority
alarms.”
• Level4
All alarms initiated from the function block or the element are “Logging
alarms.”

● Input Open Alarm

The input open alarm check may generate an alarm to indicate that the input
signal is in high limit or low limit input open alarming status (IOP, IOP-).
The high and low limit input open alarm (IOP, IOP-) indicates that a failure such
as severed wires in the detection terminal or transmitter has occurred.
The Input open alarm check is performed by the I/O module.
The types of input open alarm checks are listed below.
• Both input open alarms enabled
• High limit open alarms enabled
• Low limit input open alarms enabled
• Input open alarms disabled
The default setting is “both input open alarms enabled.”
● PV High-High/Low-Low Limit Alarm

The input high-high and low-low limit alarm check is a function that determines
whether the input process variable (PV) is out of the range of the high-high and
low-low limit alarm setpoint value (HH, LL). The types of the high-high and low-
low limit alarm checks are listed below.
• Both high-high and low-low limit alarm
• High-high limit only
• Low-low limit only
• No alarm
The default is to check both the high-high and low-low limit alarms.
If the input process variable (PV) exceeds the high-high limit alarm setpoint value,
the high-high limit alarm (HH) is activated. When in alarm state, if the process
variable (PV) becomes smaller than the value obtained by subtracting the alarm
hysteresis value (HYS) from the high-high limit alarm setpoint value (HH), the
system recovers from the high-high limit alarm.
Similarly, when the process variable is below the low-low limit alarm setpoint
value (LL), the low-low limit alarm (LL) is activated. When in alarm state, if the
process variable (PV) becomes greater than the value obtained by adding the
alarm hysteresis value (HYS) to the low-low limit alarm setpoint value (LL), the
system recovers from the low-low limit alarm.

● PV High/Low Limit Alarm

The input high and low limit alarm check is a function that determines whether the
process variable (PV) is within the range of the high and low limit alarm setpoint
values (PH, PL). The types of input high and low limit alarm check are listed
below.
• Both high and low limit alarms
• High limit only
• Low limit only
• No alarm
The default is set as “both high and low limit alarms”.
If the process variable (PV) exceeds the high limit setpoint value, the high limit
alarm (HI) is activated. When in alarming state, if the process variable (PV)
becomes smaller than the value obtained by subtracting the alarm hysteresis
value (HYS) from the high limit alarm setpoint value (PH), the system recovers
from the high limit alarming state.
Similarly, when the process variable (PV) is below the low limit alarm setpoint
value (PL), the low limit alarm (LO) is activated. If the process variable (PV)
becomes greater than the value obtained by adding the alarm hysteresis value
(HYS) to the low limit alarm setpoint value (PL), the system recovers from the low
limit alarming state.
● Hysteresis
The alarm recovery point above or below the low/low-low or high/high-high limit.
Engineering unit data within the range of 0 to PV scale span, or percentage data
for the PV scale span.
When specifying percentage data, add % after the numeric value. The default is
2.0 %.

● Input Velocity Limit Alarm

The input velocity alarm check is a function that determines whether the changes
in the process variable (PV) over a specified time exceed the velocity alarm
setpoint value (VL).
The following types of input velocity alarm checks are available:
• Detection of both directions:

Monitors velocity in both directions, positive and negative
• Detection of single direction:
Monitors velocity only in positive direction or negative direction
• No Detection:
Detection is not conducted
The default is “detection of both directions.”
The value of sampling time interval

(T) is calculated using the set
sampling interval (Tp) and the scan
period of the function block (Ts).
T = Ts●Tp
When it is determined that the changes in the process variable (PV) over a
specified time exceed the velocity alarm setpoint value (VL), the velocity alarm in
the positive direction (VEL+) is activated if the changes are in the increasing
direction. Similarly, if the changes are in the decreasing direction, the velocity
alarm in the negative direction is activated (VEL-).
The system will recover from the alarm status if the change in the process
variable (PV) falls into the range in which the alarm hysteresis value (HYS) is
subtracted from the velocity alarm setpoint value during the alarm status.
The input velocity alarm indicates abrupt changes in the process condition and
abnormalities in the detectors or the transmitters.
● Number of Samples (N)

1 to 12 points
The default setting is 1 point
● Sampling Interval (Tp)

1 to 10,000
Unit is scan interval
The default setting is 1

● Hysteresis
for the PV scale span. When specifying percentage data, add % after the numeric
value. The default is 2.0 %.
● Deviation Alarm
The deviation alarm check is a function that determines whether the absolute
value of the deviation (DV=PV-SV) between the process variable (PV) and the
setpoint value (SV) exceeds the absolute value of the deviation alarm setpoint
value (DL).
The types of deviation alarm checks are listed below.
• Detection of both directions:
Monitors deviation in both directions
• Detection of single direction:
Monitors deviation in only one direction, positive or negative
• No detection:
Detection is not conducted
The default is “detect both directions.”
● Deviation Check Filter

To prevent occurrence of the undesired alarm caused by abrupt set value change
or set value ramp, the velocity change speed (derivative value) of the setpoint
value (SV) is used as the deviation alarm setpoint value correction factor (r) to
compensate the deviation alarm setpoint value (DL). The compensated deviation
alarm setpoint value (DLe) is the value that adding the deviation alarm setpoint
value correction factor (r) to the deviation alarm setpoint value (DL).

DV Check Filter Gain

0.000 to 10.000
Default is 0.
DV Check Filter Time Constant

0 to 10,000 seconds
Default is 0.
For more detailed information, please refer to CS 1000/CS 3000 Reference

Function Block Details (IM 33S01B30-01E) C5.6 Deviation Alarm Check
● Hysteresis
for the PV scale span. When specifying percentage data, add % after the
numeric value. The default is 1.0 %.
● Output Open Alarm

The output open alarm check may generate an alarm to indicate that the output is
open (OOP).
This alarm indicates that the control output line has been physically severed.
Choose from “Yes” or “No”

Default is “Yes.”
The output open alarm check is a function that determines the data status
received from the I/O module.
The output open alarm is activated only in the function block that is directly
connected to the I/O module.
● Output High/Low Limit Alarm

The output high and low limit alarm check is a function that determines whether
the manipulated output value (MV) exceeds the range of the manipulated output
variable high-limit/low-limit setpoint (MH, ML) for the output limiter.
The types of output high and low limit alarm checks are listed below.
• Both high and low limit alarms: Output high and low limit alarm check
enabled
• High-limit alarm only: Output high-limit alarm check enabled
• Low-limit alarm only: Output low-limit alarm check enabled
• Alarms disabled: No alarm checking
The default is set as “high and low limit alarms.”
When it is determined that the manipulated output value (MV) exceeds the
manipulated output variable high limit setpoint(MH), an output high limit alarm
(MH) is activated. Similarly, when it is lower than the manipulated variable low
limit setpoint (ML), an output low limit alarm (MLO) is activated.
● Hysteresis
for the PV scale span. When specifying percentage data, add % after the
numeric value. Default is 2.0 %.

● Bad Connection Alarm

Bad connection status alarm check may generate an alarm to indicate that the
connection is bad (CNF).
The bad connection status alarm check is a function that determines whether
there is a faulty connection to the function block or data at the I/O connection
destination.
Choose from “Yes” or “No”

The bad connection is judged as follows.

• The connected destination function block is in out of service (O/S) mode.
• The connection information is abnormal, and the data reference or data set
cannot be performed.
• The connected destination function block’s data type is invalid (cannot be
convert to the appropriate data type).
J2.5 CONTROL CALCULATION
● PID Control Algorithm

The PID control computation is the core of the PID control computation
processing,calculating a manipulated output change ( MV)by using the PID
control algorithms.
The PID control computation expression used in a regulatory control system

(analog control system):
If we use the sampling value derived at each interval of the control period for the
above expression, the differential expression of the PID control computation is
transformed as follows:
The subscripts “n” and “n-1” represent the sample against the control period, it
stands for the nth sample or n-1th sample.

The above differential expression calculates a change in manipulated output

(difference). A new output value is obtained by adding the current change in
manipulated output (∆MV ⁿ ) to the previous manipulated output value (MV n – 1 ).
The PID Controller Block uses the following five PID control algorithms to perform
PID control computation.The actions vary with the characteristics of a controlled
system and the purpose of control.
The table below shows the PID control algorithms and the input variable of each
term:
● Basic Type PID Control Algorithm (PID)

This algorithm is used when the process time constant is long and the control is
oriented on the prompt response to the change in the setpoint value.
The computational expression of the basic type PID control algorithm ((PID):
The process variable (PV) and setpoint value (SV) used in the computation are
both engineering unit data. The manipulated output change ( MV) obtained in an
engineering unit by the range conversion performed via the scale conversion
coefficient (Ks).

● PV Proportional and Derivative Type PID Control Algorithm (I-PD)

The PV proportional and derivative type PID control algorithm (I-PI)differs from
the basic type that it performs only integral actions when the setpoint value
changes.
This algorithm ensures stable control characteristics even when the setpoint
value changes abruptly when the SV is set via numerical value entry. At the
same time, the algorithm ensures proper control in response to the characteristic
changes occurring in controlled processes, load variations and disturbances by
performing proportional, derivative and integral Control Action accordingly.
The computational expression of the PV proportional and derivative type PID
control algorithm (I-PD):
● PV Derivative Type PID Control Algorithm (PI-D)

The PV derivative type PID control algorithm (PI-D) only performs proportional
and integral Control Action when setpoint value changes, but not derivative
Control Action. This algorithm is used in the situations where the better follow up
to the setpoint value change is required, such a downstream control block in a
cascade control loop.
The computational expression of the PV derivative type PID control algorithm:
● Automatic Determination Type

When a PID Controller Block is in cascade (CAS) or remote cascade (RCAS)
mode, it uses the PV derivative type PID control algorithm (PI-D) to perform
computation so that the follow-up the setpoint value change can be improved.
When the block is in automatic (AUT) mode, it uses the PV proportional and
derivative type PID control algorithm (I-PD) to perform computation so that stable
control characteristics can be ensured in the event that an abrupt change occurs
in the setpoint value due to a numeric value setting.
● Automatic Determination Type 2

When a PID Controller Block is in cascade (CAS) mode, it uses the PV derivative
type PID control algorithm (PI-D) to perform computation. When the block is in
remote cascade (RCAS) mode or automatic (AUT) mode, it uses the PV
proportional and derivative type PID control algorithm (I-PD) to perform
computation.
In the cascade (CAS) mode, the automatic determination type 2 orients to the
follow-up capability to setpoint value (CSV) change. In the remote cascade
(RCAS) mode, it orients to prevent the abrupt change in the output due to an
abrupt change in the remote setpoint value (RSV).

● Control Period
The controller block executes the input processing per scan period. However, the
control calculation and output processing are executed per each control period.
The control period of the controller block is a time period that the controller
block executes control calculation and output processing during automatic
operation (AUT, CAS, RCAS). The control period of the controller block is always
an integer multiple of the scan period.
The only processing that the controller block always performs for each
scan period is input processing and alarm processing. Control calculation
and output processing are performed once per each control period.
● Control Period of Regulatory Control Action

Control calculation is executed at every control period in regulatory control action.
The figure below shows the controller block’s control period in the regulatory
control action.
● Control Period in Intermittent Control Action

In intermittent control action, control calculation and output processing are
executed only once in the scan period in which the control switch (CSW) is turned
ON during the automatic operation (AUT, CAS, RCAS). After the execution, the
control switch (CSW) is turned OFF. The control switch (CSW) can be set to ON
by other function blocks such as the sequence control blocks.
The figure below shows the control period of the controller block in the
intermittent control action.
The intermittent control action is used for the sampling control with a sampling
value to be measured at the timing determined by outside of the controller block.

Select from “fixed control period - 1, 2, 4, 8, 16, 32 or 64 seconds”, “automatic

determination” or “intermittent control action.”
When the automatic determination is selected, the control period is decided by

the following rules:
When the fixed control period or the automatic determination is selected, it is

operated with the control period of the regulatory control action. When the
intermittent control action is selected, it is operated with the control period of the
intermittent control action.
● I/O Compensation
The Input or Output Compensation function adds the compensation value (VN)
received from outside to the input signal or output signal of PID control
computation, while the controller block is operating automatically in the automatic
(AUT), cascade (CAS), or remote cascade (RCAS)mode.
Select “No,” “Input Compensation” or “Output Compensation.”

The compensation value (VN) is reset to “0” automatically at the beginning of

each control period. This prevents the previous external compensation value is
added to (VN) when the external compensation data not exist.
Normally, the external data is set directly to the compensation value (VN) from
other function block. However, the external data from other function block can be
connected to the compensation input terminal (BIN), then set to the
compensation value (VN).
For manual operation, the manually set manipulated output value (MV) is not
affected by the Input or Output Compensation.
Set Parameters of I/O Compensation

The parameters of the I/O compensation:
• I/O compensation gain (CK): -10.000 to +10.000.
The default is 1.000.
• I/O compensation bias (CB): Arbitrary engineering unit data.
The default is 0.0.

● Input Compensation
The input compensation is a control action that adds the compensation value
(VN)received from outside to the input signal of PID control computation
respectively.
The computational expression of the input compensation:
Example Using Input Compensation

The input compensation is used to improve the controllability of a process with a
long dead time, by subtracting from the input signal the signal from the Dead-
Time Compensation Block (DLAY-C) to perform PID control computation (Smith
Dead Time Compensation).
The figure below shows an example of dead time compensation:

● Output Compensation
The input compensation is a control action that adds the compensation value
(VN)received from outside to the input signal of PID control computation
respectively.
The computational expression of the input compensation:
● Example of Using the Output Compensation

The output compensation is used for feedforward control that adds the
feedforward signal to the control output signal, or for non-interacting control that
adds the output signal from the interacting loop to the control output signal.
The figure below shows an example of feedforward control:

● Non-linear Gain
The non-linear gain function changes the proportional gain in accordance with the
deviation of the process variable (PV) from the setpoint value (SV)in the control
computation. As a result, a non-linear relationship is formed between the
manipulated output change (MV) and the deviation of the process variable (PV)
from setpoint value (SV).
The non-linear gain function is used for pH control,in which the process gain often
becomes too high near the target value, or for buffer tank level control, whose
purpose is to stabilize the discharge volume while maintaining the tank level
within the limits.
Select “No,” “Gap Action ” or “Squared Deviation Action.”

The non-linear gain function calculates the control output change (∆MV), using
the effective proportional gain (Kpe) obtained through non-linear correction of
proportional gain (Kp).
The figure below shows a flow of the non-linear gain.
● Gap Action
The gap action moderates control effects by lowering the proportional gain when
the deviation is within the preset gap width (GW).
● Non-Linear Gain Characteristics of Gap Action

If a non-linear gain coefficient (Knl) has been set, the effective proportional gain
(Kpe) is obtained by the following expression when the deviation is within the gap
width (GW):

• Gap Gain: Select “1.0,” “0.5,” “0.25” or “0.”

The default is “1.0.”
● Squared Deviation Action

The squared deviation action changes the proportional gain in proportion to the
degree of deviation when the deviation is within the preset gap width (GW).
● Non-Linear Gain Characteristics of Squared Deviation Action

If a gap width (GW) has been set, the effective proportional gain (Kpe) is obtained
by the following expression when the deviation is within the gap width (GW):

● Deadband
The deadband action stops the manipulated output value (MV) from changing
while the deviation (DV)is within the preset deadband (DB) range, by causing the
manipulated output change (MV)to be “0.”
The deadband action causes the manipulated output change (∆MVn) to be “0”
when the absolute value of the deviation (DV) minus the hysteresis value
becomes smaller than the deadband width (DB). When the absolute value of
deviation (DV) increases greater than the deadband width (DB), the manipulated
output change after the deadband action (∆MVn) will be brought back to the
manipulated output change before the deadband action (∆MVn0).
The figure below shows the characteristics of the deadband action:
Select “Yes ” or “No.”

● Hysteresis
Engineering unit data between 0 and the PV scale span range limit must be set.
The default is the value equivalent to 1.0 %of the PV scale span.

● AUT Fallback
The AUT fallback is an error processing function that switches the block mode
from cascade (CAS)or primary direct (PRD)to automatic (AUT)when the AUT
fallback condition is established. Thus the set value of the control loop can be set
by the operator.
Select “Yes” or “No.”

The AUT fallback condition is established when the data status of the cascade
setpoint value (CSV) become invalid (BAD) or communication error (NCOM).
● Computer Backup Mode

When the computer fail is detected, the function block suspends the action in the
remote cascade (RCAS)mode or remote output (ROUT)mode temporarily and
switches to the computer backup mode.
Select “MAN,” “AUT” or “CAS ” as the mode to be switched to when the computer
is down. The default is “MAN.”
J2.6 OUTPUT
● Output Change
Output Velocity Limiter

It is a function to limit the amount of change between the previous and
current output values, so as to prevent abrupt changes in the output value.
The output velocity limit is a permissible amount of output change over one
scan period.
Engineering unit data or percentage within the range from 0 to the MV scale
span setting in positive values only (six significant figures).
The default setting is 100.0 %.
MAN Mode Output Velocity Limiter Bypass

The output velocity limiter can be disabled by setting the bypass for the MAN-
mode output velocity limiter.
Selectable between “Yes” and “No.”

Default is “No.”

● Auxiliary Output
The auxiliary output is used when output a signal through the SUB terminal to a
destination other than the final control element. The signal is often used as
compensation data to other function blocks, or to the indicator outside of the FCS,
etc.
Output Data/Output Type
Output Data:
Selectable from “PV” , “DPV“, “MV” and “DMV”.
Default is “PV.”
Output Type:
Selectable from “Positional Output Action” and “Velocity Output Action”
Default is “Positional Output Action.”
When the output action for auxiliary output is set to “Positional Output Action,”
the output values (MV, ∆MV, PV, or ∆PV) can be set in the connection
destination as it is. Also, when set to the “Velocity Output Action” type, the
value read back from the connection destination is added to the output value
and set in the connection destination.
● MV Display Style
Select “Automatic Determination” or “User Define.”
The default is “Automatic Determination.”
When “Automatic Determination” is selected, the engineering unit and scale

range of the manipulated output value (MV )change according to the connected
destination of the OUT terminal.
• If the connection destination is a process I/O, the scale range and

engineering unit of the manipulated output value (MV) is fixed to “0 to 100”
and “%,” respectively. However, this rule does not apply if the connection
destination is a Fieldbus block.
• When outputting to a cascade setpoint value (CSV) in a case where the

connection destines to a SET terminal of another function block (cascade
connection), the engineering unit and scale range of the manipulated output
value (MV) agree with those of the cascade setpoint value (CSV) of the
output destination.
When the connection destination is an input terminal of another function
block than SET terminal, “self determination” must be selected.

When “User Define” is selected, set the engineering unit and scale range for the
manipulated output value (MV).
• MV Engineering Unit Symbol:

Consists of six or less standard-width characters or three double-width
characters.
The default is “%.”
• MV Range:
High and low limits.
Numerical values of seven digits or less, where the sign and decimal point
occupy one digit each.
The default is “100.0” for the upper limit and “0.0” for the lower limit.
● Limit Output in direction when clamped

Selectable from “Yes” and “No.”
When the data status of the cascade connection destination is CLP+ or CLP-, the
output direction of the manipulated output value (MV) is restricted, i.e., the value
cannot be changed to exceed or falls below the present output value, so that only
the manipulated output value (MV) in the direction that cancels CLP+ or CLP- is
output.
● Control Calculation Output Type

Selectable from “positional” or “velocity.”
Default is the “positional” action.
A Regulatory Control Block outputs its manipulated output value (MV) or the
vicissitude of that value (∆MV).
There are two types output action: positional and velocity:
• In positional output action, the output value connects to its destinations

unchanged.
Adds the current manipulated output change (∆MV) to the previous output
value (MVn-1) and determines the manipulated output value (MVn).
• In velocity output action, the amount of change for the current output (∆MV)
is added to the value read back from the connection destination of the output
terminal.
Adds the current manipulated output change (∆MV) to the value readback
from the output destination (MVrb) and determines the manipulated output
value (MVn).

J2.7 CONNECTION
The connection functions establish data transfer between the instruments. There are
3 different kinds of connection:
A Process connection: connection to or from I/O cards.
B
Interterminal connection: connection between instrument terminals.
C Data connection: connection to or from the instruments without

connection through terminals. (data setting, data referencing
function.) All sequence elements such as digital inputs/outputs,
internal switches, etc, should be connected by data connection.
C (Reference) PVI-DV
IN OUT
SET
PID
IN MV OUT
B
A (Input) SET
PID A (Output)
IN P OUT
BDSET-1
I/O Card I/O Card
J04
C (Setting)
1 to 5 V 4 to 20 mA

J2.8 Others
● Constant
Constants are preset tuning parameters. Up to 1,024 alphanumeric characters
can be used for each constant.
Upon online downloading to an FCS, the constants are always substituted for the
current tuning parameters for any changed function block. The saved tuning
parameters take precedence over the constants upon offline downloading to an
FCS, while the constants take precedence over the unsaved tuning parameters
upon initial offline downloading to an FCS.
● Syntax
The syntax for setting a constant is DataItemName = Constant
If the constant is a character string, enclose the string in " " double quotation
marks.
The syntax for setting a constant for array data is DataItemName[Subscript1] =
Constant or DataItemName[Subscript1, Subscript2] = Constant.
When setting multiple constants, separate them with a , (a comma).
Example of setting constants.
● Data Items for Which Constants can not be Set

Constants can not be set for some data items as their settings. The table below
lists the data items for which constants can not be set, and the function blocks
with these data items:


J3. Other Function Blocks
Input Indicator Block (PVI) Manual Loader Block (MLD)
Ratio Set Block (RATIO)
Addition Block (ADD)

J4 Question
1. What is the main difference between Process I/O and Software I/O?


K. SEQUENCE CONTROL FUNCTIONS
K. SEQUENCE CONTROL FUNCTION

Sequence Control Blocks which execute the sequence control include Sequence Table
Blocks, Logic Chart Blocks, SFC Blocks, Switch Instrument Blocks, Sequence Element
Blocks, and Valve Monitoring Block.
This chapter explains details of Sequence Table Blocks and Logic Charts.
K1.1 Sequence Table Block

Sequence Table Block (ST16, ST16E) is a decision table type function block that
describes the relationship between input signal and output signal in a Y/N (yes/no)
fashion. By making sequence connection with other function blocks, they control the
monitoring of processing and phase step sequences.
The conditions and operations are arranged in the table format and specify which
operation is performed by the combination of conditions. This is suitable for the
description of all sequences such as the parallel operation, interlock operation and
sequence operation.
The following two models of blocks are categorized as Sequence Table Block:
• Sequence Table Block (ST16)

It has a sequence control function that handles a total of 64 I/O signals, 32 rules.
• Rule Extension Block (ST16E)

This function block is used for rule extensions of the Sequence Table Block (ST16).
It connects to an extending Sequence Table Block (ST16) as an extended sequence
table to form a sequence table group. Non step-type Sequence Table Blocks (ST16)
cannot be connected.
The figure below shows the function block diagram of Sequence Table Blocks (ST16,
ST16E):
YOKOGAWA SINGAPORE TRAINING CENTRE Page K1 of K21

K1.2 Sequence Table Configuration

Sequence tables consist of condition signals, action signals, rule numbers, condition
rules, action rules and step labels.

K1.2.1 Number of Signals

However, allocation of the number of signals can be changed in the 8-signal unit
using the signal selection dialog.

K1.2.2 Sequence Table Elements

Condition Signal
Enter the element symbol and data item into the Tag name. Data item column as the
input connection information, then enter the condition specification to Data column.
Action Signal
Enter the element symbol and data item into the Tag name. Data item column as the
input connection information then enter the action specification to Data column.
Rule Number
Up to 32 rules per block may be used. The output is based on each rule condition
and condition testing result.
Condition Rule
Describe the Y/N (Y:true, N:false) pattern (combination) to condition rule. If the
testing result of condition signal corresponds with the Y/N pattern, the condition of the
rule is satisfied.
Action Rule
Describe the Y/N (Y:Positive action; N:Negative action) pattern (combinations) to
action rule .Perform manipulated output according to the Y/N pattern of the action
rule for the rule number whose condition is satisfied.
Step Label (▼STEP)

Labels that are attached for phase identification purposes when performing step
sequence control using a sequence table. Step labels are character strings that
combine two or less alphanumeric characters (A to Z, 0 to 9).
If two characters are combined while one is not alphanumeric and the other is
alphanumeric, the label is managed as the same step name, even if the order of
characters is reversed (e.g.,“_A ” and “A_”).
Up to 100 steps can be described in one sequence table group. However, same step
labels cannot be described at multiple locations inside the sequence table group.
The step labeled 00 is activated every scan cycle.
Next Step Label (▼THEN, ELSE)

Describe the step label that is to be executed in the next scan. Described by 16 or
less alphanumeric characters.
Next step labels include THEN and ELSE labels according to case conditions being
true or false. If both labels are blank, the step does not transfer.
• THEN label
Describe the next step label when the corresponding rule condition status is true.
Transition to the step described in the THEN label is executed after the
manipulated output is completed.
• ELSE label
Describe the next step label when the corresponding rule status is false.
Tag Name.Data Item

Describe the input connection information of the condition signal or the output
connection information of the action signal.
Data
Describe the condition specification of the condition signal or the operation
specification of the action signal.

Comment
Comments are defined by users for the condition and action signals. The meaning of
symbols and the contents of status manipulation may be put in these texts, by using
up to 24 single-byte alphanumeric characters, or 12 double-byte characters.
By clicking the task [Referencing Signal Comment] from the [Tool] menu, the user-
defined comment text may be displayed at the right area of signals.
The comment text for the referenced signals can not be edited on the sequence
table editing window.
The user-defined comment text (tag comments) may be displayed at the right area of
signals based on the steps indicated below.
Processing Timing
The processing timing of a sequence table consists of start timing and output timing.
Start timing refers to the timing at which control algorithms of the sequence table are
executed upon receipt of input signals.
Output timing indicates the conditions under which action signals are output at the
time a periodic start type or one-shot start type sequence table is executed.
• Start Timing:
Select either
“Periodic Execution Type (T),”
“One-shot Processing Type (O),”
“Startup at Initial Cold Start/Restart (I)” or
“Restricted Initial Execution Type (B).”
• Output Timing:
Select either
“Output Only When Conditions Change (C)” or
“Output Each Time Conditions are Satisfied (E).”

Scan Period
Periodic start sequence tables are activated at defined scan period.

“Scan Period,” “Control Period,” and “Control phase” can be defined for each
sequence table.
• Scan Period: Select from “Basic Scan ”,“Medium-speed Scan ” (*1) or
“High-speed Scan.”
• Control Period: 1 to 16 seconds.
• Control Phase: 0 to 15 seconds.
Scan Period
Periodic start sequence tables are activated at defined scan period.

“Scan Period,” “Control Period,” and “Control phase” can be defined for each
sequence table.
• Scan Period: Select from “Basic Scan” or “High-speed Scan.”
Extension Rule Tag Name (▼NEXT)

Described by 16 or less alphanumeric characters.

K2.1 Step Sequence Table

In a step sequence table, the process control sequence of a phase-step process is
divided into the smallest phase units (steps) of the condition monitoring and operation,
and then these steps are executed one by one.
In a step sequence table, only step label 00 and the rule corresponding to the current
step number are subject to condition testing and operation. The following shows the
action of a step sequence table.
• Step label 00 is executed during each period. Step 00 may only be described at the
head of a sequence table group. Step 00 cannot be described as a next step label.
• For step sequences, the next execution step label must be described in
THEN/ELSE in order to advance the steps. The step will not be advanced if both next
step labels in
THEN/ELSE are blank. If there is no description for the next step label, the same step
is executed each time, the sequence does not move step.
• The next step specified in THEN is the step to advance when the condition test
result in positive. When all operations for the corresponding rules are completed, the
step proceeds to the next step.
• The next step specified in ELSE is the step to advance when the condition test
result in negative. When conditions for the corresponding rules are established, the
step proceeds to the next step without executing the operation rules.
• If there are multiple requests for step transition in the same step, the step advances
to the next step label that is described for the smallest rule number.
• When a step is advanced, the conditions for the rules are initialized once. In other
words, all the conditions become false with respect to the previous execution.
• The timing in which the next step is actually executed after a step is advanced is the
next scan period.

Example of a Step Sequence that Uses the Sequence Table

This figure shows an example of the phase step sequences that combines the water
injection processing and drains processing.
Push the start button, valve A opens to fill water to the tank. When the tank is full, switch
A becomes ON, the valve is closed.
Push the start button again when the tank is full, then the valve B opens.
When the drain process ends, switch B becomes ON, the valve B closes.

In the above sequence table, rule numbers 01 and 02 are step A1. Rule numbers 03 and
up are step A2. Rule numbers 05 and beyond do not have any description for the
condition rule, operation rule or move-destination step label, so they are not subject to
condition testing nor operation.
Step A1 monitors the conditions for rule numbers 01 and 02 simultaneously. Of rule
numbers
01 and 02, whichever the condition is satisfied will be executed. Executing the operation
of rule 01 does not advance the step, since there is no designation in the move-
destination step label. After executing the operation, A1 resumes monitoring rule numbers
01and 02 again. On the other hand, if the condition for rule number 02 becomes true, the
operation of rule 02 will be executed, and the step advances to A2 because the move-
destination step label has a designation.

K2.2 Non- Step Sequence Table

In a non-step sequence table, all 32 rules are subject to condition testing, and the
operation is performed according to the conditions. The following shows the operation of
a non-step sequence table.
As for condition testing, a condition is satisfied when all conditions (Y or N) for the same
rule number are true. A sequence table whose rule columns are all blank is considered
true unconditionally.
Operations are executed according to the operation contents of Y or N described for the
rule number whose conditions are satisfied.
When the output timing is specified as “Output Only When Conditions Change,” the
operation is executed only once when the condition is switched from false to true.
However, if non-latched output is specified for the operation signal, the operation changes
when the condition is switched from true to false.
When the output timing is specified as “Output Each Time Conditions are Satisfied”, the
operation is executed during each period as long as the condition remains true.

Example of the Non-Step Format Sequence Using the Sequence Table

An example of the sequence that normally monitors operations to prevent the buffer tank
in the processing piping system from overflow is shown in the following figure. In this
sequence, LI100 (indication block) alarm status is used.
The sequence table in the figure shown above monitors the conditions in rule numbers 01
to 04 simultaneously. Any condition in one of the 4 rules becomes true; the operation in
the same rule will be executed again. The monitoring continues after the execution.

K3. Logic Chart

Logic Chart Block (LC64) may combine or arrange the signals of other function blocks,
process I/O and software I/O into an application for interlock sequence control.
It is the function block that describes the relations of the input signals, the output signals
and the logic calculation operators in the interlock diagram form, so that it can perform its
main function, the interlock sequence control using the same expressions as those used
on the logic chart blue prints.
Architecture of LC64 Logic Chart Block is shown as follows.

K3.1 Logic Chart Configuration

A logic chart consists of condition signals, action signals and logic operators. LC64 block
is a sequence control function block with 32 input and 32 output signal channels and it
can handle 64 logic operators.
A general outlook of a logic chart is shown as follows:
K3.1.1 Logic Chart Elements

Processing Timing
The processing timing of a logic chart consists of start timing and output timing.
Start timing refers to the timing at which control algorithm of the logic chart is
executed upon receipt of input signal.
Output timing indicates the conditions under which action signals are output at the
time a periodic start type or one-shot start type logic chart is executed.
The output timing of logic charts is fixed to “output each time.” If the logical value
acquired by logic operation is true, output signals are output whenever started.
•Start timing:
Select from
“Periodic Execution Type (T),”
“One-shot Processing Type (O),”
“Startup at Initial Cold Start/Restart (I)” or
“Restricted Initial Execution Type (B).”
•Output timing:
“Output Each Time Conditions are Satisfied ”

Scan Period
Periodic start logic charts are activated in each scan period as defined here. Among
the periodic started logic charts, the logic charts activated in the basic period have the
items “Control Period” and “Control Phase” to be defined in addition to scan period.
“Scan period,” “control period,” and “control phase” can be defined for each logic
chart.
• Scan Period: Select from “Basic Scan ”,“Medium-speed Scan ” (*1) or
“High-speed Scan.”
Scan Period
Periodic start logic charts are activated at each defined scan period. Among the
periodic started logic charts, the logic charts activated in the basic period have the
items “Control Period” and “Control Phase” to be defined in addition to scan period.
“Scan Period,” “Control Period,” and “Control phase ” can be defined for each logic
chart.
• Scan Period: Select from “Basic Scan” or “High-speed Scan.”

● Order of Logic Calculation

For the execution order of logic calculation, the matrix expansion or manual
expansion can be selected.
• Matrix expansion
Logic operators in logic charts are executed from the left column to the right, and
from the upper element to the lower in the same column.
• Manual expansion
The execution order automatically assigned to the logic operation elements
according to their position can be manually changed.
The default setting for the execution order is matrix expansion.
● Condition Signals
The input information such as tag names and data items or other specific condition
scripts should be entered for condition signals.
● Comment
For the input signals or output signals, their service comments can be described
using up to 24 alphanumeric characters or 12 double-byte characters. A comment
corresponding to a condition or action signal can be automatically entered.
● Logic Chart Area

The logic calculation process can be expressed in logic chart diagram form.

● Action Signals
The output information such as tag names and data items or other specific
manipulation scripts should be entered for action signals.
K3.1.2 Input Element Symbol

The input element symbols include those that only describe condition signals, and
those that describe both condition signals and comments.
Comments are described in the comment description area of the input element
symbol.
Syntax of Condition Signal Description:

[Tag name] . [Data item name] . (=) [Condition specification]
Example:
LIC100.ALRM.HH
Condition signal description area
Comment description area Condition signal description area
K3.1.3 Output Element Symbol

The output element symbols include those that only describe action signals and those
that describe both action signals and comments.
Comments are described in the comment description area of the output element
symbol.
Syntax of Action Signal Description

[Tag name] . [Data item name] . (=) [Action specification]
Example:
SW0001.PV.L
Action signal description area
Comment description area Action signal description area

K3.1.4 Logic Operation Element Symbol

The logic chart is described with combinations of logic elements in the logic chart
block.
AND: Logic Product

It gives one output based on multiple inputs. When all the inputs are True, the output
becomes True. The maximum number of inputs is 21.
OR: Logic Sum

It gives one output based on multiple inputs. When any of inputs is True, the output
becomes True. The maximum number of inputs is 21.
NOT: Negation
It gives the inverse of the input as an output.
SRS1-R (1 output), SRS2-R (2 outputs): Flip-Flop (Reset-Dominant)

It gives one output or two outputs shown in the following truth table based on the set
and reset input signals.
One flip-flop operation is counted as two logic operation elements.

SRS1-S (1 output), SRS2-S (2 outputs): Flip-Flop (Set-Dominant)

It gives one output or two outputs shown in the following truth table based on the set
and reset input signals.
One flip-flop operation is counted as two logic operation elements.
WOUT: Wipeout
It gives an output which is an inverse of reset signal when reset signal is true,
otherwise, it gives the set signal as output, shown in the following truth table based
on the set and reset input signals.
One wipeout operation is counted as two logic operation elements.
Its symbol is shown below.

OND: On-Delay Timer

When the input status changes from 0 to 1, the internal timer starts. When the set
time t elapsed, its output changes from 0 to 1. When the input status changes to 0,
the output will be reset to 0 immediately.
OFFD: Off-Delay Timer

When the input status changes from 1 to 0, the internal timer starts. When the set
time t elapsed, ts output changes from 1 to 0. When the input status changes to 1,
the output will be reset to 1 immediately.

TON: One-Shot (Rise Trigger)

When the input status changes from 0 to 1, it gives an output 1 for a one scan cycle.
The output is always 0 except for that 1 scan cycle.
TOFF: One-Shot (Fall Trigger)

When the input status changes from 1 to 0, it gives an output 1 for a one scan cycle.
The output is always 0 except for that 1 scan cycle.
CMP-GE: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1
is greater than or equal to input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.

CMP-GT: Comparator
is greater than input 2, otherwise it gives an output 0.
CMP-EQ: Comparator
is equal to input 2, otherwise it gives an output 0.

K4. Exercise
1. To activate a digital output after a period of time.
Start
SEQ
ST16
False S1
%SW0300.PV.ON
TIMER
TM
True
PH = 30
%SW0300.PV.H = N
DO0001.PV.H = N
TIMER.OP.START = Y
False S2
TIMER.BSTS.CTUP
True
DO0001.PV.H=Y


L. HIS FUNCTION
L. HIS FUNCTION
In this chapter, the HIS properties are explained here.
L1.1 HIS Properties – Type

In System View, right click on [HIS0164] [Properties]
L1.1.1 Station Type

• PC with Operation and Monitoring Functions
• YPCKIT Open Display Style Console Type HIS
• LPCKIT Enclosed Display Style Console Type HIS

• HIS-TSE HIS with Server for Remote Operation and monitoring function
YOKOGAWA SINGAPORE TRAINING CENTRE Page L1 of L6

L. HIS FUNCTION
L1.1.2 Station Address
Domain Number
Set a domain number for a new HIS to be created. Set a domain number in the range
of 1 to 16. The domain number can not be changed once it is set.
Station Number
Station numbers are used to identify the devices in the same domain of the system.
The station number may be set for each domain in the range of 1 to 64. The
station number can not be changed once it is set.
The station number may be set in the range of 1 to 24. The station number can
not be changed once it is set.
L1.1.3 Component
Component numbers are used to indicate the connection origin or connection
destination component numbers when wiring the devices.
Component number settings may be omitted.
Station Comment
If more information about each station is required, the station comment may be input
for each station. The station comment may be omitted.
Alias of Station
An alias can be used as an alternative of station name.
After setting aliases, the stations displayed on the HIS will be indicated by their
aliases.
An alias of a station can be defined with up to 8 alphanumeric characters.
Station Status Display

A window can be designated to display the station status on HIS instead of using the
HIS station status display panel. The name of this window can be designated using
up to 16 alphanumeric characters.
Upper Equipment Name

The name of the higher-level process equipment group in plant hierarchy can be
designated.

L. HIS FUNCTION
L1.2 HIS Properties - Constant

Buzzer ACK ID
The buzzer ACK ID is an ID that allows buzzers on other HISs with the same buzzer ACK
ID to be reset when a buzzer is acknowledged on one HIS.
The buzzer ACK ID can be set with up to eight single-byte characters.
Operation Group Identifier

The operation group identifier is used for the identification if different operation groups
exist. Up to eight single-byte characters may be used for an identifier. The first two
characters are identifier characters, the rest are comment text.
The default setting is [A1].
A wild card [*] may be used as the operation group identifier.

L. HIS FUNCTION
L1.3 HIS Properties - Network

When the Vnet/ IP check box is checked, the control bus type is set to Vnet/IP; when it is
unchecked, the control bus type is set to V net.
However, some stations may be created in either Vnet/ IP or V net.
When the control bus type is changed, download the project common section.

L. HIS FUNCTION
L1.3.1 Control Bus TCP/IP Settings
Control Bus Host Name

The control bus host name is automatically determined according to the bus type,
domain number and station number. In normal situations, the automatically
determined host name should be used.

The IP address on the control bus is automatically determined according to the
bus type, domain number and station number. In normal situations, the
automatically determined setting should be used.

The control bus subnet mask is set to “255.255.0.0” by default.
In normal situations, this default setting should be used.
L1.3.2 Ethernet TCP/IP Settings
Ethernet Hostname
The Ethernet Hostname will be automatically determined according to the bus
type, domain number and station number. In normal situations, the automatically
determined hostname should be used.

L. HIS FUNCTION
Ethernet IP Address
Ethernet IP addresses are used to logically identify the HIS connected to the
Ethernet.
The Ethernet IP addresses are automatically determined according to the bus
type, domain number and station number. In normal situations, the automatically
determined setting should be used.
Ethernet Subnet Mask

The Ethernet subnet mask is set to “255.255.0.0” by default. Normally, this
default setting should be used.
L1.3.3 Setting Vnet/ IP Network

This section describes how to set the IP address of a Vnet/IP station.
● IP Addresses
IP address for Control Bus Network and for Open Communication Network need
to be respectively configured.
Both the subnet masks for Control Bus Network and for Open Communication
Network also need to be respectively configured.
Example of IP Address: 172.16.1.64 (Control Bus Network)

192.168.129.193 (Open Communication Network)
● Subnet Mask
Same as IP addresses, the subnet masks for Control Bus Network and for Open
Communication Network are important communication settings.
Example of Subnet Mask: 255.255.0.0 (Control Bus Network)

255.255.255.0 (Open Communication Network)
The IP address and subnet mask for the Open Communication Network are user
definable.
The default settings are as follows:
• IP Address: 192.168.<128+dd>.<129+ss>(dd: Domain Number; ss:

Station Number)
• Subnet Mask: 255.255.255.0
The default IP address and subnet mask for Control Bus Network are:
172.16.dd.ss and 255.255.0.0

M. HIS CONFIGURATION
In this chapter, the HIS properties are explained here.
M1.1 HIS Constants

In System View, select project, [HIS0164], select [CONFIGURATION] and double click on
[OpeconDef].
M1.1.1 Printer Tab
HIS Printer Name

Message output may be assigned to different printers, according to the message
type.
The default setting is all types of message are assigned to MSG1.
As the above example, since the process alarm message, and messages in response
to the sequence message request are assigned to the same printer MSG2, both
types of message are printed out from the same printer in the order of their arising.
The HIS printer name here requires to be assigned a real printer, and this may be
defined on HIS Setup window.
YOKOGAWA SINGAPORE TRAINING CENTRE Page M1 of M7

User Group Name

When printing, the scope of operation and monitoring of the designated user group
decides the scope of the message to print out. The message outside of the operation
and monitoring scope can not be printed.
The default user group is DEFGRP (all), messages of all stations may be printed out.
M1.1.2 Closing Process

The Closing Process creates closing data for statistical processing, such as average
values and total values, based on trend data acquired by the Trend Recording.
The Closing Process calculates the data acquired from Trend Recording into the
statistical data for report function such as the hourly, daily or monthly average, sum or
other type of closing data.
The closing data saved as files can be used via OPC interface or DDE interface for
Report Report Package) or other functions.
Furthermore, via OPC interface or DDE interface, Microsoft Excel or other MS

Windows’ application can access the saved data.
The following figure shows the positioning of the Closing Process:
Up to 200 data items (*1)(hourly, daily and monthly closing data)can be processed
per HIS.

Closing
The trend data defined in the builders as follows may be used for the closing
processing:
• Sampling period of 1 minute, 2 minutes, 5 minutes or 10 minutes are specified

in property of the Trend Acquisition Pen Assignment Builder.
• The trend data assigned as a trend gathering pen in the Trend Acquisition Pen
Assignment Builder, and specified as closing data.
Hourly Closing
In the hourly closing data process, the trend data of the previous one hour are
gathered from the saved trend data file, in which the trend gathering pens specified
for closing processing are also saved. The hourly closing data such as the average,
total, maximum and minimum values are calculated for this one hour based on the
gathered valid data.
Hourly closing data process is performed at the closing time of every hours.
The number of data points used for the hourly closing processing varies depending
on the trend sampling period.
•Trend of 1-minute sampling period

Trend of 1-minute sampling period creates the hourly data using 60 points of
data.
data.
data.
data.
Daily Closing
In the daily closing data process, the hourly closing data of the previous 24 hours are
gathered and the daily closing data are calculated for the day, including the average,
total, maximum and minimum values.
The default daily closing time is 0:00 am. The daily closing time may be changed
using the closing processing tab of the HIS constants builder to meet the requirement
of the plant operation. Unlike the hourly and monthly closing times which are fixed by
the system, whether data acquired until the daily closing time is the data of the
closing day or that of the previous day may be specified, and the daily closing time
may be adjusted within the range of 0:00 to 23:00 (in hour units).
Monthly Closing
In the monthly closing process, the daily closing data of the previous one month are
gathered, and the monthly closing data are calculated for the month, including the
average, total, maximum and minimum values. Monthly closing processing is
performed after the daily closing processing on the last day of each month.
Disk Space Used

Each type of closing data may be saved for the following period:

M1.1.3 Long Term Data Save

The long-term data archive is intended for the long-term storage of trend data, closing
data and historical messages as necessity dictates. The stored data (long term data)
can be referenced from the Trend window or from an application program.
The long-term data archive function separately manages trend data, closing data and
historical messages that have been saved in the HIS console, and stores it for any
long-term period.
The following three types of data are subject to storage with the long-term data
archive:
• Trend data that is pen assigned with the Trend Acquisition Pen Assignment
Builder
• Closing data that has been specified for closing processing with the Trend
Acquisition Pen Assignment Builder
• All historical messages acquired using the message processing
After trend data, closing data and historical messages are saved using the HIS
standard function, they are automatically stored via the long-term data archive.
The storage period in the long-term archive depends on the data type and data
storage unit defined on the Trend Acquisition Pen Assignment Builder or on the HIS
Constants Builder.
So long the 5 % free space is reserved in the hard disk, the data storage may take as
much space as desired.

● Timing of Fetching Data to Long-Term Data Archive Files

Fetching the files of trend data, closing data and historical messages to Long-term
Data Archive files are carried out at the following timings.
Trend Data: When trend data file becomes full

Closing Data: When closing data file becomes full
Historical Messages: At 0:05 am. However, if the HIS is not running at this
moment, the data will not be fetched.
M1.1.4 Message Print Wait Time

The messages are not printed out until they are piled up to fit one page for print.
With definition of the queuing time, the message may be sent to printer when the
defined queuing time elapsed.
When queuing time is specified as 0, the auto print does not function.
Auto print queuing time may be defined on the HIS Message Print Wait Time
definition tab of the HIS Constant Builder.
Printer queuing time: Define in minutes per HIS printer
The default is 5 minutes.
M1.1.5 Instrument Diagram Operation

Operation Message Print Specification
The operation message output for the faceplate blocks may be specified.
Checking the corresponding items to enable or disable the operation message output.
Instrument Diagram Operation

The function blocks for display discrete data allow the two kinds of operation.
• Twice-Pressed operation
This is the standard operation type for operating the switch instrument
blocks.
• Two-Step operation
This is the standard operation type for operating the switch instrument blocks and
faceplate blocks.
This operation is performed with the mouse or by touching a window. (*1)
Clicking the push buttons may operate the block.
If reconfirmation or acknowledgment is required the corresponding dialog box will
appear, clicking the confirmation button may remove the guard frame then the
block may be operated.
*1: This operation can only be performed by touching a window on the console type HIS that supports touch
panel.
For faceplate blocks, only two-step operation may be specified.

• Operation guard frame in solid line

The switch with operation guard frame requires two-step operation to change the
switch ’s status. For the switches that requires operators ’ confirmation, the
operation on the switches may pop-out a confirmation dialog box. The operation
guard frame is in dotted line or in the solid line may be defined.
• Flashing to prompt for acknowledgment

• Color change to prompt for acknowledgment
• Guard frame color change to prompt for acknowledgment.
For two-step operation, define if the buttons start to flash or not when output
operation commands to the connected switches. To flash the label character
string of the switch or to flash the frame of the label or to flash both character
string and label frame may be specified. The color change while flashing may
also be specified.
The above specification is only valid for the switches with confirmation function.
M1.1.6 Security
HIS Attribute
Select the function security level of the HIS from the following two types:
• Dedicated monitoring machine
• Operation and monitoring machine (default)
If the HIS is set as a dedicated monitoring machine, a user can only perform
monitoring on the HIS regardless of privilege levels. Operations allowed on the HIS
set as an operation and monitoring machine vary depending on the user privilege
level and the access level of the operation target.
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
The operation and monitoring scope of the HIS can be set for each HIS.
The operation and monitoring scope of the HIS is unrelated with the operation and
monitoring scope set for each user group.
The default setting is “ALL” for INCLUDE and “NONE” for EXCLUDE.

M1.1.7 Multiple Projects

The Multiple Project Connection allows integrated operation and monitoring of
multiple plants.
The project connection will be used in the following cases:
• To perform distributed engineering on a large-scale plant, and operate/monitor

distributed systems.
• To perform an integrated operation and monitoring of multiple existing plants.


N. FUNCTION KEYS
N. FUNCTION KEYS
In this chapter, the assignment of function keys is explained here.
The function keys provided on the operation keyboard allow the users to define functions
freely.
Accompanying each key around the key surface are an LED that indicates alarms and
operation timings to the operator by the flashing of the lamp and a label that describes the
function assigned to the key.
Label
LED
Label
LED
YOKOGAWA SINGAPORE TRAINING CENTRE Page N1 of N16

N. FUNCTION KEYS
N1. Function Keys Assignment

In System View, select project, [HIS0164], select [CONFIGURATION] and double click on
[FuncKey].
N1.1 Function
The types of items assignable to the function keys include the following:
• Calling up of windows
Calls up the operation and monitoring windows.
• Execution of the system function keys

Executes the functions provided by the system function keys.
• Starting, stopping or restarting of trend data

Controls the starting, stopping or restarting of trend data acquisition targeted at
the specified trend groups.
• Flashing or turning ON/OFF of LED ’s

Controls the flashing or turning ON/OFF of LED ’s.
• Execution of programs by their file names

Executes programs by specifying their file names.
• Execution of the Multimedia

Plays the specified voice message files.

N. FUNCTION KEYS
For CS 3000, there are more items that are assignable to the function keys:
• Panel set calling

The pre-defined panel set may be called up.
• Calling up of a window to another station

Calls up the currently displayed active window to the specified HIS.
• Calling up of remote windows by window name

Calls up remote windows to the specified HIS. This function can be used on the
console type HIS.
• Copying of a currently displayed window set

Calls up to the specified HIS windows currently displayed on the CRT. This
function can be used on the console type HIS.
• Clearing of a window on the remote CRT

Clears a window called up on the specified HIS.
N1.1.1 Assigning Window Call to a Function Key
The window call is assigned using the format below:
(Example) O FIC101 TUN -SM =+200+100
In the above example, the Tuning window for displaying the tag name “FIC101” is
called as a medium-size window located at X coordinate 200 and Y coordinate
100 from the upper left edge of the screen.
N1.1.2 Assigning a System Function to a Function Key

A system function key is assigned using the format given below:
In the above example, the User-In dialog box is called.
Hard Copy (HDCP)

Outputs hard copy of the images of all windows displayed including Windows
general application windows.
Print (PRNT)
Prints the active window. This is valid only when there is a print button in the
operation and monitoring window to be printed.

N. FUNCTION KEYS
Message Printout (MSPR)

Forces all printers assigned to MSG1 to MSG5 to print messages currently
generated.
Buzzer Reset (BUZZ)

Executes buzzer reset operation. Stops all the buzzer output.
Stop Voice Play (VOIC)

Pauses the voice play for checking.
Window Set Store (WSSV)

Stores the Dynamic Window Set.
Window Set Delete (WSCL)

Deletes the Dynamic Window Set.
Window down (CRDN)

Moves the front window of the stack to the back. However, the primary window is
not affected.
Window up (CRUP)
Moves the back window of the stack to the front. However, the primary window is
not affected.
Focus (FOCS)
Switches the active window sequentially between the primary window and the
topmost auxiliary window. This key becomes effective only in full-screen mode.
Primary Window Focus (FCSF)

Makes the primary window the active window. This key becomes effective only in
full-screen mode.
Circulate (CIRC)
Transposes the front to back relationship between the operation and monitoring
window group and Windows-based application window group.
Acknowledgment (ACKN)
Acknowledges alarms for the active window.
Clear Windows (ERAS)

Closes all currently displayed windows.
Primary Window Hide (CLFS)

Clears and hides the primary window to allow access to the Windows desktop.
This function is valid only in the full screen mode.
Primary Window Clear (ERFS)

Clears the display contents of the primary window and displays it as an empty
window. This key becomes effective only in full-screen mode.
Active Window Erase (ERAW)

Closes the active window.
History File Calling forward (RECF)

Sequentially calls up the operation windows displayed in the past, starting with
the oldest one. Up to 30 windows can be called up.

N. FUNCTION KEYS
History File Calling backward (RECB)

Sequentially calls up the operation windows displayed in the past, starting with
the latest one. Up to 30 windows can be called up.
Navigator (NAVI)
Calls up the Navigator window.
User-In (USIN)
Calls up the User-In dialog box.
Clear (CLER)
Cancels the selection mode and input data.
Panel set (PSET)

Calls up the panel set related to the active window. The panel set in which the
active window is listed first of the group in the Panel Set Builder is called up.
Message Monitor Window (MSDW)

Calls up the Message Monitor window. When a message occurs, the LED in a
function key that has been assigned the function of calling up the Message
Monitor window turns on.
The LED turns off after the message is acknowledged.
The LED cannot be assigned to a function key that has been assigned the
function of calling up the Message Monitor window.
Isolate (ISOL)
Turn on/off “isolate” status.
The “isolate” function, as described below, prevents window calls from other HIS.
Changes only the “isolate” status of its own HIS and not other HIS.
•Request from another HIS to execute the panel set function.

•Request from another HIS to call up a window.
•Request to display a window automatically due to notification of process alarm
occurrence from a field control station.
•Request to display a window automatically due to occurrence of operator guide
message.
•Request to display a window due to sequence message request.
TIP
“Isolate” status may be switched by pressing [ALT] + [CTRL] + [F11].
Window Shift (SHFT)

Shifts the windows displayed in main monitor to sub monitor.
When using this function, the display in the sub monitor is replaced by the display
in the main monitor. The display in main monitor becomes empty after Window
Shift operation.
After running this function, the windows shifted from main monitor to sub monitor
may not be displayed in the same cascade sequence.
This Window Shift function is valid only when the package for multiple monitors is
installed.
If the package for multiple monitors is not installed, an error beep can be heard
when operating this function.

N. FUNCTION KEYS
Window Exchange (ECHG)

Exchanges the displays of main monitor and sub monitor.
After running this function, the windows shifted from main monitor to sub monitor
or vice versa may not be displayed in the same cascade sequence.
This Window Exchange function is valid only when the package for multiple
monitors is installed.
If the package for multiple monitors is not installed, an error beep can be heard
when operating this function.
Calling Related Builder Window (BDRA)

With this function, the function key can be used to call a related builder window of
the currently active operation and monitoring window.
Note: BDRA is valid only when the HIS is installed with basic builder package and
configured information reference package.
NOTE
BDRA is valid only when the HIS is installed with basic builder package and
Calling Related Control Drawing Builder Window (BDRD)

With this function, the function key can be used to call a related builder window of
the currently active control drawing window.
NOTE
BDRD is valid only when the HIS is installed with basic builder package and
N1.1.3 Assigning Trend Data Acquisition Function to a

Function Key
The trend data acquisition is assigned using the format given below:
(Example) T TG0101 START
In this example, trend data acquisition starts for the Trend window “TG0101”.

N. FUNCTION KEYS
N1.1.4 Assigning LED to a Function Key

When assigning a function to control the flashing and turning ON/OFF of LED’s to
the function keys,
The number for the LED to be controlled can be selected between 1 and 32 (*1).
*1: With the console type HIS, select between 1 and 64.
Assign the LED to the function keys in the following manner.
In this example, the LED of LED number 1 is turned on.
N1.1.5 Assigning a Program Executing to a Function Key

The program execution is assigned using the format given below:
Example 1:
In the above example, the report function is used to print the report “CYOHYO” to
the default printer, and at the same time the report is set as an object for
historical management.
Example 2:
In the above example, the Microsoft Word file “File1” in the “USER File ” folder is
started.

N. FUNCTION KEYS
N1.1.6 Assigning a Multimedia to a Function Key

The Multimedia is assigned using the format given below:
When designating multimedia file, an arbitrary and absolute path cannot be
specified.
Specify the relative path “\his \media \user” from the system installed directory.
In the above example, the voice message stored in the multimedia file
“buzz1.wav” is played two times according to the maximum (1)priority.
Select one of three types of Multimedia activation operations:

PLAY, REPEAT, or STOP.
N1.1.7 Assigning Panel Set Call Function to a Function Key
Assign the Panel Set Call to a function key in the following manner.
In the above example, the panel set “PSET001” is called up.
Define the panel set name defined in the process of the system generation.

N. FUNCTION KEYS
N1.1.8 Assigning the Function of Calling up a Window

from a Different Station to a Function Key
Assign the function of calling up a window from a different station to a function

key in the following manner.
Option
When omitted:
The currently active operation and monitoring window is called up on the
specified HIS.
-A:
All of the currently displayed operation and monitoring windows are called up on
the specified HIS. The windows on the source HIS remain on the display after
the windows are called up on the specified HIS.
Example 1:
Selecting and activating the window “GR001 ” in HIS0123 and then pressing the
function key that is assigned the function of calling up a window on another
station will call up “GR001 ” on “HIS0124 ”.
Example 2:
In the above example, all windows called up on HIS0164 are closed.

N. FUNCTION KEYS
N1.1.9 Assigning the Function of Calling up a Remote

Window by Window Name to a Function Key
Assign the function of calling up a remote window with up to 48 alphanumeric
characters in the following format:
Option
When omitted: the currently active operation and monitoring window will be called
up on the specified HIS. A window displayed on the CRT from which the
operation and monitoring window was called up remains in the same state
(remains displayed).
- S: the currently active operation and monitoring window will be called up on the
specified HIS. A window displayed on the CRT from which the operation and
monitoring window was called up closes.
- A: all the currently displayed operation and monitoring windows will be called up
on the specified HIS. A window displayed on the CRT from which the operation
and monitoring window was called up remains in the same state (remains
displayed).
- AS: all the currently displayed operation and monitoring windows will be called
up on the specified HIS. A window displayed on the CRT from which the
operation and monitoring window was called up closes.
Example 1:
In the above example, the large-size Process Alarm window is called up on

HIS0163.
A window displayed on the CRT from which the operation and monitoring window
was called up remains displayed.

N. FUNCTION KEYS
N1.1.10 Assigning the Function of Copying a Currently

Displayed Window Set to a Function Key
Assign the function of copying a currently displayed window set in the following
format:
In the above example, all windows currently displayed on the current CRT are
called up on HIS0163.
N1.1.11 Assigning the Function of Clearing a Window

on the Remote CRT to a Function Key
Assign the function of clearing a window on the remote CRT in the following
format:
In the above example, all windows currently called up on HIS0163 are cleared.
Specify the name of a station whose CRT will clear the displayed window.

N. FUNCTION KEYS
N1.2 LED
The following function blocks or windows can be set to the LED of the function keys
as LED flashing conditions.
• Alarm display by the tag name or an annunciator message.
• Alarm display by the window name.(Graphic window, Process Alarm window,

Operator Guide Message window, System Alarm window)
When the function block or window set as conditions for flashing changes to an alarm
state, the LED flashes. When the acknowledgment operation is performed, the LED
changes from a flashing display to a lit display. When the alarm returns to normal, the
LED turns off.
When the window name is set as the condition, an argument can be specified.
Arguments can be specified for windows (Process Alarm window, System Alarm
window, etc.) that accept arguments when called up.
Conditions for function

key LED flashing

N. FUNCTION KEYS
N1.3 Change Privilege /Change Authorization over the Functions

Assigned to the Function Keys
Specify whether or not the function key assignment can be temporarily changed in
the HIS Setup window, by using the following changing authorities provided by the
security.
• General
• Important
• System operation
The function key assignment may or may not be changed depending upon the above
change authorization specification and the privilege level of the logged-in user.
The table below shows operation and monitoring authorities on windows, indicating
which user can perform operation and monitoring using which types of windows:

N. FUNCTION KEYS
N2 Emulate Function Keys in Operation and Monitoring

Windows
Irrelevant to the applications and the active windows in the HIS, the functions assigned to
the function keys of the HIS operation keyboard can be executed through the shortcut
keys on the standard keyboard of PC.
The functions for the 20 function keys of the HIS operation keyboard are executable from
the designated shortcut keys.
N2.1 Enabling Shortcut Keys

On the Station tab of HIS Setup window, the option for enabling the shortcut keys
needs to be checked.
1. Call the HIS Setup window.
2. On Station tab, check the option of [Emulate Function Key] and then click [OK]
button.
3. Logoff the Windows and then logon again. The above setting will take effect
when the HIS is started again.

N. FUNCTION KEYS
N2.2 Shortcut Actions

The shortcut actions and the shortcut keys (on the standard PC keyboard) are
listed as follows:
● Emulated Functions of HIS Operation Keyboard

• Ctrl+F1; Function of PF01(*1)
• Ctrl+Shift+F1; Function of PF11(*1)
*1: PF01 to PF20 stand for the function keys of the HIS operation keyboard, and the
functions assigned to the keyboard are customizable.
N2.3 Cautions on Using Shortcut Keys

However, the main phenomena caused by the shortcut key conflicts are shown as
follows:
• Both the HIS shortcut key sequences and other applications key sequences are
executable.
• Only one set of shortcut key sequences is executable. Either HIS shortcut key
sequences or other application shortcut key sequences will become in valid.
• Both the HIS shortcut key sequences and other applications key sequences
become invalid.
When the conflicts occurred, the shortcut keys for emulating the function keys in HIS
operation keyboard should be disabled so as to avoid the troubles.

N. FUNCTION KEYS
N2.4 Reserved Shortcut Functions

The shortcut key actions and the corresponding functions are as follows:
• Ctrl+Alt+F11: Switches the console isolation mode

• Ctrl+Alt+F12: Displays a menu
• Ctrl+Alt+Backspace: Displays User-In dialog box

O. SCHEDULER
O. SCHEDULER
Scheduler controls the specified applications or tasks to run at the specified time. The running
schedule of tasks may be defined on the Scheduler Builder.
O1. Scheduler Builder

In System View, select project, [HIS0164], double click on CONFIGURATION and double
click on [Scheduler].
O1.1 Function
The following tasks can be controlled by the scheduler:
• Calling up windows
Calls up the operation and monitoring windows.
• Execution of the system function keys

Executes the functions assigned to the system function keys.
• Starting, stopping or restarting of trends

Starts, stops or restarts trend data acquisition targeted.
• Flashing or turning ON/OFF of LED

Controls the flashing or turning ON/OFF of LED.
• Startup of programs by file names

Starts up program by specifying the file name.
• Execution of the multimedia function

Plays the specified multimedia message.
• Calling up a panel set (*1)

The pre-grouped panel set may be called up.
• Calling up windows to other stations (*1)

The active window being displayed may be called up on other specified HIS
consoles.
YOKOGAWA SINGAPORE TRAINING CENTRE Page O1 of O3

O. SCHEDULER
O1.2 Start Method, Start Month, Start Date, Start Time, Period,
Times of Repeat
The scheduled tasks may be started by scheduler in the following manners:
• Execute once at the startup of the operation and monitoring functions.

• Execute once at the specified date every year.
• Execute once at the specified time on the specified day every month.
• Execute once at the specified time on the specified day every week.
• Execute at the specified time every day.
O1.3 Comment
Up to 32 single-bytes alphanumeric characters or 16 double-byte characters may be
defined as comment.

O. SCHEDULER
O2. Exercise
1. Configure the Scheduler so that 2 minutes from now the user defined graphics
window 3D-SAMPLE will appear.
2. Configure the Scheduler so that when HIS is started up, the first graphic to
appear is PRIORITY.

O. SCHEDULER
3.

P. SEQUENCE MESSAGE REQUEST

The sequence message request is sent by the Process Sequence Control Function at certain
process timing to an HIS to execute certain Operation and Monitoring Functions.
P1. Sequence Message Request Builder

click on [MsgReqDef].
P1.1 Function
The following functions may be specified to a sequence message request.
•Calling up windows
•Executing a program assigned to the function key
•Operation keyboard LED ON/OFF/flash
•Run a designated program
•Multimedia
•Calling up a panel set (*1)
•Printing reports
P1.2 Station Name

The sequence message request is managed in an HIS. Usually, ALL is specified in
the station name item thus, the request received from all FCSs may be executed. If a
station name is designated, only the request from the designated station is executed.
YOKOGAWA SINGAPORE TRAINING CENTRE Page P1 of P3

The trigger of request messages is shown as below:

P2. Exercise
1. Write a sequence table so that when FIC100 has a HI alarm, user defined
window CASCADECONTROL appears.

2.

Q. PANEL SET
Q. PANEL SET
With the panel set function, multiple windows can be called up together to multiple HISs.
Combination of several windows that are frequently used can be defined as a panel set and
the panel set can be called up with one-touch operation.
Q1. Panel Set Builder

Up to 200 Panel Sets can be defined per HIS.
Up to 5 windows can be defined per set.
In System View, select project, [HIS0164], double click on CONFIGURATION and then
double click on [PanelSet].
Q1.1 Panel Set

Panel set name can be defined with up to 8 single-byte characters.
Q1.2 Display Window

All the windows that can be called up by entering the window name can be defined as
a panel set.
Define the window name and the function type with up to 24 double-byte characters
or 48 single-byte characters as follows:
• Window name
Define the window name or the tag name
• Function type
Define any of the following:
TABLE: Sequence Table window

SFC: SFC window
DRAW: Control Drawing window
LOGIC: Logic Chart window
YOKOGAWA SINGAPORE TRAINING CENTRE Page Q1 of Q2

Q. PANEL SET
Q1.3 Calling up the Panel Set

The panel set defined in the Panel Set Builder can be called up in the following
manner:
• Assigning a function key

• Defining in the sequence message request
• Define in the Graphic Builder
• Entering a panel set name in the name entry dialog box
Enter “$ + panel set name” in the name entry dialog box.
Example: $PSET01
In the above example, the panel set “PSET01” is called up.
When the same window name is defined as the first window of more than one Panel
Set, the Panel Set with the smallest number is called up.
Q1.4 HIS Notification

When creating a system, notification to other HIS may be specified. With this
specification, if a Panel Set is called up, the related panel set names are notified to all
the other HIS defined in the Panel Set Builder. On receiving the panel set name, HIS
calls up the panel name according to the Panel Set definition of the same name
defined in its own HIS database. The figure below shows an example:
However, even if the notification to other HIS is specified, the sequence message
requests sent from an FCS are not passed to other HISs. If a set of panels needs to
be displayed at the same time on different HISs, the sequence messages requests
should be defined for the entire HISs for displaying the set of panels.
YOKOGAWA SINGAPORE TRAINING CENTRE Page Q2 of Q2

R. TREND ACQUISITION
R. TREND ACQUISITION PEN ASSIGNMENT

The Trend Data Acquisition periodically gathers process data from an FCS as tuning
parameter of the function block, in accordance with definitions for data acquisition, acquisition
type, sampling period and recording span. The acquired data may be displayed in Trend
windows and in Trend Point windows.
R1. Structure of Trend

The Trend Recording has a three-layer structure:
• Trend block
• Trend window
• Trend point window
1. Trend Block
A trend block is comprised of 16 units of Trend windows.
8 trend blocks per HIS.
The trend format and sampling period are defined for each trend block.
2. Trend Window
Eight-Pen trend data can be assigned to a Trend window.
128 Trend windows per HIS.
3. Trend Point Window

The Trend Point window is called up from the Trend window. One trend pen is
displayed in each Trend Point window.
1,024 Trend Point windows per HIS.
YOKOGAWA SINGAPORE TRAINING CENTRE Page R1 of R15

1. Trend Block
A trend block is comprised of 16 units of Trend windows.
There are 50 trend blocks per HIS.
Up to 20 of the 50 trend blocks can be defined in the rotary trend or batch trend format.
The remaining 30 trend blocks are defined as trend of other stations.
The trend format and sampling period are defined for each trend block.
2. Trend Window
Eight-Pen trend data can be assigned to a Trend window.
800 Trend windows per HIS.
3. Trend Point Window

The Trend Point window is called up from the Trend window. One trend pen is
displayed In each Trend Point window.
6,400 Trend Point windows per HIS.

R2. Sampling Period and Recording Span of Trend Data

The sampling period of process data are specified for each trend block. The sampling
period can be selected from 1 second, 10 seconds, 1 minute, 2 minutes, 5 minutes or 10
minutes.
No more than 18 blocks can be specified with the sampling periods of 1 minute, 2
minutes, 5 minutes and 10 minutes.(*1)
No more than 2 trend blocks can be specified with the sampling period of 1 second
or 10 seconds.
The recording span indicates the time to acquire 2,880 samples for each trend graph
maximum number of samples) in the specified sampling period.
The table below shows the relationship between trend sampling periods and recording
span:
For example, if the trend sampling period is 1 minute,

1 (minute) x 2880 samples =2,880 minutes =48 hours =2 days
2 days of process data may be recorded.

R3. Trend Acquisition Pen Assignment Builder

In System View, select project, [HIS0164], right click on CONFIGURATION
[Create New] [Trend acquisition pen assignment].
Right click on the newly created trend pen assignment and select properties

R3.1 Trend Format

The acquisition type of process data are defined for each trend block.
The data acquisition includes the following 4 types:
1. Continuous-Rotary Type
By this mode, process data are acquired constantly. Data acquisition starts
automatically after starting the HIS.Data acquisition stops when the HIS stops.
Acquired data will not be erased after the HIS stop. When the storage capacity
oldest data are deleted and replaced by new data.
2. Batch-Stop Type
By this type, data acquisition starts and stops according to the received stop
instruction is given, data acquisition will stop automatically when the storage
capacity becomes full.
The acquisition start and stop commands may be sent from:
•Button on the toolbar of the Trend windows

•Graphic window or function key
•Sequence Messages Request

3. Batch-Rotary Type
By this type, data acquisition starts and stops according to the received
command. If no stop instruction is given, data acquisition will continue until the
storage capacity becomes full. Once it is full, the oldest data are deleted and
replaced by new data.
The acquisition start and stop commands may be sent from:
•Button on the toolbar of the Trend window

•Graphic window or function key
•Sequence Messages Request
4. Trend Acquired by other HIS

By this type, trend data acquired by other HIS may be referenced in blocks.
On the Trend Acquisition Pen Assignment Builder, define the name of other
HIS and the number of trend block to be acquired.

R3.2 Long Term Data Save

The long-term data archive function separately manages trend data, closing data and
historical messages that have been saved with the HIS standard functions, and
stores it for any long-term period.
To apply this function, the long-term data archive package (LHS6510) is

required.
The disk space required for long-term data storage can be calculated from the
number of data points, data-sampling period and the number of days for storage.
Calculation of Disk Space Required

For example, the calculation of disk required for a datum with 256 samples (2
blocks) and 1 minute sampling period which is to be archived for 30 days is as
follows:
Space required = 10.8 x [(30 + 13)/ 7]*1

= 10.8 x 6.14*1
= 10.8 x 6
= 129.6MB

R4. Trend Group Definition

click on [TR0001].
R4.1 Acquisition Data, Data Axis Span Change, Low/High Limit

Value
Define the tag name and data item of process data in the following format:
TagName.DataItem
The data axis span refers to the display width along the data axis in the Trend
window. For each pen, user can specify whether or not to change data axis span.
When “data axis span change” is not specified, the range of the data item of the
function block which is assigned to the pen is applied.
Define the high limit value and low limit value each trend data displayed in Trend
window when data axis span changes.
R4.2 Data Type

The display data type of each trend gathering pen is defined to display data in the
Trend window.
• Default
Acquired data are displayed in the default data type in the instrument faceplate
showing the function block of the acquisition source.
• Analog type
Acquired process data are displayed in the data axis range 0 to 100 %of the trend
graph.
• Discrete type
Acquired ON/OFF data are displayed in the fixed data axis range 6 %of the trend
graph.
• Totalizer value (analog type)

Acquired process data are displayed in the data axis range 0 to 100 %of the trend
graph. Process data acquired are not single-precision data but double-precision
data.

R5. Export Trend Data to CSV File

The trend data can be exported to a CSV (Comma Separated Value) file.
Exporting Trend Data to CSV File

A designated trend group (eight trends) can be exported to a CSV file. When the data are
exported into a CSV file, the data can be easily used by third-party software for reading,
editing and parsing.
● Setting Items for Exporting Trend Data to CSV File

When exporting trend data to a CSV file, the following setting items need to be
defined:
• Designating the data to be exported: Trend Records, Pen Assignments or

Sampling Status.
• Designating the number of data to be exported
• Fetching the data between a time period
• Converting the archived trend data to CSV file
• Exporting the long-term trend data to CSV file
Start Exporting Trend Data to CSV File

Exporting trend data to CSV file can be started as follows:
• By a command script
• By assigning the command to a function key
• By calling from other programs
Command Details
The details of the command for exporting trend data to CSV file are explained as follows:
● Command Syntax
BKHTrCSV [-bpgdsBl] [-i id] [-t start_time end_time] [-n number] [-x form]
[-File_name] group_num | file_name
● Path
<CS1000/CS3000 folder>\Pogram\BKHTrCSV.exe
● Description
The trend data can be exported includes the collected trend data and archived
trend data. Data are exported in the order of their time stamps. The file name is
specified right after the option -F. If the file name is omitted, the file is saved as
follows:
<CS1000/CS3000 folder>\his\save\trend\TGbbgg.csv
bb: Trend block number
gg: Trend group number

● Command Options
The command to export trend data to CSV file has the following options:
-b: Export trend block configuration data (Block information: B_xxx record)
-p: Export trend pen assignment data (P_xxx record)
-g: Export trend acquisition attributes (G_xxx record)
-d: Export collected trend data (D record), in the order of the time stamps.
-s: Export collected trend data with data quality flags (BAD, QST).
-B: Export the designated trend block into 16 trend group files
(TGbb01 to TGbb16). When using this option, -F option becomes invalid.
-l: Export the archived long-term trend data. If the log-term archived data are not
available, the collected trend data are exported.
-i id: When exporting, the designated user ID is added to @ID record.
-t start_time end_time:
Export the trend data of a designated time period. The arguments of start_time
and end_time are the local time, the time adjustment and sun light saving time
change undergone in the past are calculated by the program, user does not
need to take care of, but simply to use the current local time.
The format of the arguments start_time and end_time are

MMDDhhmm[[CC][YY][.ss]]
MM: Month
DD: Day
hh: Hour (24-Hour Base)
mm: Minute
CC: The first two digits of the solar calendar year.
YY: The last two digits of the solar calendar year.
Ss: Second
When this option is used, the option -n becomes invalid. If this option is not
used, all data are exported.
-n number:
The number of data to be exported. The argument <number> is a value greater

than zero and the data are counted backward started from the latest acquisition
data.
-x form:
Based on the output conversion of C language, the collected trend data can be
exported with text format. The specified format can be applied to all the 8 trends
in the group. Since the data type of collected trend data is floating point, the f, e
and g arguments can be used.
Example: -x%.6g
If this option is omitted, the default %.nf will be used. In this case, n stands for the
specified number of digits after decimal point of the trend scales; it is also the
same number of digits after decimal displayed on the trend window.

-F file_name:
The file name is specified by this option. If the path is not specified, the file will be
stored in the following folder:
<CS1000/CS3000 folder>\his\save\trend\
If the file name is specified with the path, the folder of the path must exist, if the
folder does not exist, error occurs. If the file name is not specified, the exported
file will be saved as follows:
<CS1000/CS3000 folder>\his\save\trend\TGbbgg.csv
bb: Trend block number

gg: Trend group number
If the identical file name exists, the existing file will be overwritten. When -B
option is used, this option becomes irrelevant.
group_num:
Specifies a trend group in the format of bbgg; bb stands for trend block number
and gg stands for the trend group number.
file_name:
Specifies a file name that the exported data is stored. If the path is not specified,
it looks for the file in the following folder:
<CS1000/CS3000 folder>\his\save\trend\
If a file name and path are specified, it accesses the file from the specified folder.
However, if the file cannot be found, error will occur. The argument file_name
should not be used at the same time with group_num argument.
If none of -b, -p, -g, -d options is specified, all the options become valid.

CSV File Structure

The CSV file structure is explained as follows:
There are following records in the file:

ID Record
B_xxx Record
P_xxx Record
G_xxx Record
D Record
The first field of these records is used to indicate the record type.
If a datum string contains [,] or ["] character, the string is double-quoted with a pair of
double quotation marks, the ["] character in the string is doubled to [""].
Example:
ABC,DEF → "ABC,DEF"
ABC"DEF → "ABC""DEF"
The records in the file are as follows:
● @ID Record
Field 2: The character of the ID specified by -I option
● B_BLNO Record
Field 2: Group number
Field 3 to 5: Empty
Field 6 to 13: Block numbers of pen 1 to pen 8 (all the eight pens are the
same).
● B_PERD Record
Field 3 to 5: Empty
Field 6 to 13: Sampling periods of pen 1 to pen 8 (all the eight pens are the
same). If the block is not defined, these fields are empty.
● B_SMPL Record
Field 3 to 5: Empty
Field 6 to 13: Number of samples of pen 1 to pen 8 (all the eight pens are the
same). If the block is not defined, these fields are empty.
● B_TYPE Record
Field 3 to 5: Empty
Field 6 to 13: Trend type of pen 1 to pen 8 (all the eight pens are the same). If
the block is not defined, these fields are empty.
Trend type is indicted by R, B or R&B.

R: Rotary Type
B: Batch Type
R&B: Batch and Rotary Type

● P_ITEM Record
Field 3 to 5: Empty
Field 6 to 13: The plant names, tag names and item names of the trend pen 1
to pen 8. And the array data plant names and array numbers if
the array data exist. If the pen assignment is not defined, these
fields are empty.
● P_CMNT Record
Field 3 to 5: Empty
Field 6 to 13: Comment texts of the trend pen 1 to pen 8. If the pen assignment
is not defined, these fields are empty.
● P_DPLO Record
Field 3 to 5: Empty
Field 6 to 13: Scale low limits of the trend pen 1 to pen 8. If the pen
assignment is not defined, these fields are empty.
● P_DPHI Record
Field 3 to 5: Empty
Field 6 to 13: Scale high limits of the trend pen 1 to pen 8. If the pen
● P_DPDP Record
Field 3 to 5: Empty
Field 6 to 13: Number of digits after decimal point of the trend pen 1 to pen 8. If
the pen assignment is not defined, these fields are empty.
● P_EUNT Record
Field 3 to 5: Empty
Field 6 to 13: Engineering units of the trend pen 1 to pen 8. If the pen
● P_TYPE Record
Field 3 to 5: Empty
Field 6 to 13: Assignment types of the trend pen 1 to pen 8, such as Analog,
OnOff or Double. If the pen assignment is not defined, these
fields are empty.
● G_STAT Record
Field 3 to 5: Empty
Field 6 to 13: Data sampling state of pen 1 to pen 8 such as Gather or Stop (all
the eight pens are the same). If the block is not defined, these
fields are empty.
Gather: Sampling
Stop: Sampling is stopped.

● G_DNUM Record
Field 3 to 5: Empty
Field 6 to 13: Number of samples of pen 1 to pen 8 (all the eight pens are the
same).
● D Record
Field 3: Date (YYYY-MM-DD)
Field 4: Time (HH:MM:SS)
Field 5: Time Zone
Field 6 to 13: Data values of pen 1 to pen 8. If the data values are not available
these fields are empty.
Field 14 to 21: Data quality flags of pen 1 to pen 8 (valid only when -s option is
used). The flags are B, Q, BQ and NULL character.
B: BAD stands for bad data

Q: QST stands for questionable data
BQ: BAD and QST
NULL: Data are normal
When the HIS restarted, the trend configuration is modified or the trend sampling
is restarted, a dummy datum is stored. Date and time are not available thus the
field 3 to field 5 are empty.
Usage Samples of Command

A sample of exporting to CSV file is shown as follows:
● Exported File Sample 1

Command:
BKHTrCSV 0101
Export Source: TG0101
Export Records: Trend Definitions, Pen Assignments, Sampling Type, Sampled Data.
Export Data Range: Whole Range
Export to File: <CS1000/CS3000 folder>\his\save\trend\TG0101.csv
Print Sample:
B_BLNO,1,,,,1,1,1,1,1,1,1,1
B_PERD,1,,,,1,1,1,1,1,1,1,1
B_SMPL,1,,,,2880,2880,2880,2880,2880,2880,2880,2880
B_TYPE,1,,,,R,R,R,R,R,R,R,R
P_ITEM,1,,,,PID-S59.PV,PG-L13.MV,PLANT1:
PID.PV,PID.PV,PVI.PV,PID.PV,%SW001S0102.PV,
P_CMNT,1,,,, MV Index(NO),13-Zone Program Set Block, FCS1 AREA1 PID, PID
Controller
Block A, Indicater Block, PID Controller Block A, Common Switch 1,
P_DPLO,1,,,,0.0,0.0,0.0,0.0,0.0,0.0,0,
P_DPHI,1,,,,100.0,100.0,200.0,100.0,100.0,100.0,1,
P_DPDP,1,,,,1,1,1,1,1,1,0,
P_EUNT,1,,,,%,%,NM3/H,%,%,%,,
P_TYPE,1,,,,Analog,Analog,Analog,Analog,Analog,Analog,OnOff,
G_STAT,1,,,,Stop,Stop,Stop,Stop,Stop,Stop,Stop,Stop
G_DNUM,1,,,,2880,2880,2880,2880,2880,2880,2880,2880
D,1,2004-10-28,13:51:51,JST,0.0,66.7,,55.0,80.0,55.0,1,
D,1,2004-10-28,13:51:52,JST,0.0,53.3,,55.0,66.7,55.0,1,
D,1,2004-10-28,13:51:53,JST,0.0,40.0,,55.0,53.3,55.0,1,
...

Command:
BKHTrCSV -ds -i TG0101 -t 06121352 06121353 -F TG0101_01.csv 0101
Export Source: TG0101
Export Records: User Defined ID, Sampled Data.
Export Data Range: 2004-10-28 13:52:00 to 2004-10-28 13:53:00
Export to File: <CS1000/CS3000 folder>\his\save\trend\TG0101_01.csv
Print Sample:
@ID,TG0101
D,1,2004-10-28,13:52:00,JST,0.0,25.0,,55.0,15.0,55.0,1,,Q,,,Q,,Q,,
D,1,2004-10-28,13:52:01,JST,0.0,32.5,,55.0,25.0,55.0,1,,Q,,,Q,,Q,,
...
D,1,2004-10-28,13:53:00,JST,0.0,25.0,,55.0,15.0,55.0,1,,Q,,,Q,,Q,,

Command:
BKHTrCSV -d -n 3 TG0203.trf
Export Source: <CS1000/CS3000 folder>\his\save\trend\TG0203.trf (A trend file saved
with a different name.)
Export Records: Sampled Data.
Export Data Range: The latest three records
Export to File: <CS1000/CS3000 folder>\his\save\trend\TG0203.csv
Print Sample:
D,19,2004-10-28,14:39:48,JST,0.0,70.0,,55.0,65.0,55.0,1,
D,19,2004-10-28,14:39:49,JST,0.0,75.0,,55.0,70.0,55.0,1,
D,19,2004-10-28,14:39:50,JST,0.0,80.0,,55.0,75.0,55.0,1,


S. HIS WINDOWS
S. HIS WINDOW CREATION

In this chapter, the creation of different user-defined HIS window is explained.
S1. HIS Window Creation

In System View, select project, [HIS0164], right click on WINDOW [Create New]
[Window].
YOKOGAWA SINGAPORE TRAINING CENTRE Page S1 of S5

S. HIS WINDOWS
S1.1 Window Types

The operation and monitoring windows whose display content can be defined as
desired by the user at system generation are called “user-defined window.”
Graphic Window with Graphic Attribute

The Graphic window with graphic attribute is used to display process data along with
a process flow chart or to call various windows that are targets of operation and
monitoring.
It is the target of calling operation via the graphic button in the System Message
window or graphic key on the operation keyboard.
Graphic Window with Overview Attribute

The Graphic window with overview attribute is used to display the status of the
function blocks and to call various operation and monitoring windows can be
assigned to the Graphic window with overview attribute. The overall status of the
plant can be grasped at a glance.
It is a target for a Graphic window call and is a target of the calling operation via the
overview button of the System Message window and via the overview key on the
operation keyboard.
Graphic Window with Control Attribute

The Graphic window with control attribute is used to assign the instrument faceplate
in the Graphic window with control attribute. So user can operate the plant while
viewing the graphic image of it.
It is the target for the calling operation via the control button in the System Message
window or the control key on the operation keyboard.

S. HIS WINDOWS
Trend Window
The Trend window displays acquired trend data.
It is the target of the calling operation via the trend button in the System Message
window or the trend key on the operation keyboard.
From the Trend window, user can call up a Trend Point window that displays one of
the eight process data assigned to the Trend window.
A Trend Point window is automatically created when process data is assigned to the
Trend window.
S1.2 Window Name

For a user-definable window, the user can define the window name freely.
A user-defined window name is a string with up to 16 alphanumeric characters
(capital letters only for the English alphabet), [_] (underscore) and [-] (hyphen).
However, a [_] (underscore) and [-] (hyphen) may not be placed at the beginning of a
user-defined window name.
S1.3 Help Message Number

There are system-fixed help dialog and user-definable help dialog for defining help
message.
S1.4 Window Comment

An explanatory description for each user-defined window can be defined with up to 24

S. HIS WINDOWS
S2. Set Details Tab
S2.1 Window Operation and Monitoring Authority

With CS 1000/CS 3000 security policy, the operation and monitoring authority can be
set for each window.
The following three types of operation and monitoring authorities can be set for
windows:
• General window
• Important window
• System operation window

S. HIS WINDOWS
The table below shows operation and monitoring authorities on windows, indicating
which user can perform operation and monitoring using which types of windows:
S2.2 Disable Scaling

When the scaling attribute is set to “none”, the contents of the window display are
shown at the size when it was created, regardless of the size of the display window.
For a window with the scaling attribute, the display contents are adjusted to fit the
window display size.

S. HIS WINDOWS

T. CONTROL GROUP WINDOW
T. CONTROL GROUP WINDOW DEFINITION

There are 3 types of Control Group windows:
• Control Group (8-loop)

• Control Group (16-loop)
• Console Control (8-loop)
T1. HIS Window Creation

[Window].
YOKOGAWA SINGAPORE TRAINING CENTRE Page T1 of T6

T1.1 Control Group (8-loop)

In System View, select project, [HIS0164], [WINDOW] double click on CG8.

T1.2 Control Group (16-loop)

In System View, select project, [HIS0164], [WINDOW] double click on CG16.
T1.3 Console Control (8-loop)
In System View, select project, [HIS0164], [WINDOW] double click on CC8.

T2. Instrument Diagram Definition

In Graphic Builder (eg CG8),
Double click on [Instrument Diagram] OR
Right click on [Instrument Diagram] [Properties].
T2.1 General Tab

The General tab sets the object name, display position and size, as well as whether
the object can be used as a tag object.
Object Name
This sets the name of an object. The text of up to 15 double-width characters can be
entered as an object name. Use the name set here to search an object or to identify
an object for data input at debugging.
Position
This sets the display position of an object (x coordinate and y coordinate).
The coordinates (x coordinate and y coordinate) of the top left corner of a graphic
object will be the reference point of the graphic object display position.
Size
This sets the width and height of an object.

Activate Tag Object

However, tag objects are limited to the following objects to which a tag name
(process data) can be assigned.
• Graphic primitive object with modifier

• Data character display object
• Data bar display object
• Instrument diagram object
T2.2 Instrument Diagram Tab

The Instrument Diagram tab is used to set the function block instrument diagram to
be displayed on the Graphic window, its display contents, size, and tag name.
Display Format
• Normal
The entire display contents of the instrument diagram are displayed in full.
• Compact
The display contents of the instrument diagram are simplified. In compact type,
the digital display of data is no longer available.

Instrument Diagram Width

This sets whether the instrument diagram is displayed in default width (single-width)
or in double width.
However, even if the double width is specified, the actual HIS display may only be in
single-width (default size) depending on the type of an instrument faceplate.
Operation Control Key

The operation key (INC/DEC key) on the console type HIS may be specified for the
corresponding instrument faceplates on the display position 1 to 8.
Tag Name
Enter text for the tag name of an instrument diagram to be displayed.
T2.3 Data Bind

On Data Bind tab, the bindings, variants bound to the generic names of objects, can
be defined.

U. OVERVIEW WINDOW
U. OVERVIEW WINDOW DEFINITION

In this chapter, the Overview window definition is explained.
U1. HIS Window Creation

[Window].
YOKOGAWA SINGAPORE TRAINING CENTRE Page U1 of U8

U. OVERVIEW WINDOW
U1.1 Overview
In System View, select project, [HIS0164], [WINDOW] double click on OV0001.

U. OVERVIEW WINDOW
U2. Overview Window Definition
In Graphic Builder (eg OV0001),

Double click on [Overview] box OR
Right click on [Overview] box [Properties].
U2.1 General Tab

The General tab sets the object name, display position and size, as well as whether
the object can be used as a tag object.
Object Name
This sets the name of an object. The text of up to 15 double-width characters can be
entered as an object name. Use the name set here to search an object or to identify
an object for data input at debugging.
Position
This sets the display position of an object (x coordinate and y coordinate).
The coordinates (x coordinate and y coordinate) of the top left corner of a graphic
Size

U. OVERVIEW WINDOW
U2.2 Overview Tab

The Overview tab is used to set the monitoring target to be assigned to an overview
object. It also sets the properties of the display data and the presence/absence of an
alarm notification according to the selected monitoring target.
Type
This sets the type of a monitoring target to be assigned to an overview object. [Tag
name], [Tag name (with tag mark)], [Window name], [Annunciator] and [Comment]
can be selected as a monitoring target.

U. OVERVIEW WINDOW
The table below lists the types of monitoring targets and the setting items for each
target.
First Line Display Type

Select either a tag name or tag comment as a label to be displayed in the first line of
an overview object.
Alarm Specific Blinking

Checking the [Alarm-specific Blinking] check box will enable the overview objects to
indicate the blinking status of the tag name or the window name, allowing the alarm to
be acknowledged.
Specify Font
Checking [Specify font] check box enables to specify font displayed on overview
object.

U. OVERVIEW WINDOW
U2.3 Function Tab

The Function tab is used to set functions to be assigned to touch targets, push
buttons, and softkeys.
Function Type
The available function types are shown below:
• Call window
• Execute the system function key
• Start/Stop/Restart Trend
• Flash/Light/Turn OFF the LED
• Execute the Program by File Name
• Instrument Command Operation
• Call Data Input Dialog
• Call Menu Dialog
• Data-Item Dependent Menu Dialog
• Execute the Multimedia Function
• Report Printout
• Call Panel set (*1)
• Others

U. OVERVIEW WINDOW
Specify Window Size

This sets whether or not to specify a window size. When specifying a window size,
select a window size from [Large Size], [Medium Size], or [Special Size]. This item
may be disabled depending on the type of the window selected.
Specify Window Display Position

This sets the display position of a window to be called. Check the [Specify
Coordinate] check box.
The display position reference point is located at the top left corner of the drawing
area.
The “setting window display position” is optional. If it is not selected, the window
display position can not be specified.
Windows display position can be specified with a monitor number instead of the
coordi-nates.
If the HIS is installed with multiple monitoring packages, this setting is required.
Check [Specify Monitor No.] check box, and then spin the spin box for setting the
monitor number. 1 or 2 can be selected.
The function known as Multi-monitoring connects two monitors to one Human

Interface Station (HIS), and displays windows for the operation and monitoring on
each monitor. In this way two monitors can be handled as one large, logical desktop
area (virtual desktop area).
Display Cursor
Set whether or not to display the cursor movement sequence.
Cursor Movement Sequence

The cursor moves between created touch targets every time the arrow key is pressed
on the Graphic window.
The cursor normally moves from one touch target to the nearest target in order of the
target placement on the window, starting from the upper left corner. However, a
desired movement order can also be specified, canceling the order of target
placement.
The cursor movement order is specified by assigning priority numbers to the objects.
The movement order number can be set for the objects using an integer within the
range from 1to 5-digit value. The maximum number that can be set for the cursor
movement order may be set on the Graphic Builder, as well.

U. OVERVIEW WINDOW
U2.4 Data Bind Tab

On Data Bind tab, the bindings, variants bound to the generic names of objects, can
be defined.

V. HELP WINDOW
V. HELP MESSAGE WINDOW

Help messages guide the user through monitoring the operation of the plant.
These messages are either pre-defined in the system or definable by the user.
They are system alarm help, user-defined help and system window help.
V1. System Alarm Help

This is a help message that provides detailed information about the system alarm
message. The system alarm help is pre-defined in the system.
Using the message number of the system alarm message as a keyword search for the
corresponding system alarm help can be performed.
V2. User-Defined Help

This is a help message that the user can freely define. The user can define help
messages to explain the function and operating procedure for user-defined windows or
help messages to explain the function block.
The user can search for user-defined help by entering the window name, tag name or
help number as the keyword.
V3. System Window Help

These are help messages that explain the functions of the system window. The system
window help is pre-defined in the system.
Using the window name as keyword, the corresponding system window help can be
searched.
YOKOGAWA SINGAPORE TRAINING CENTRE Page V1 of V3

V. HELP WINDOW
V4. Help Window Creation

In System View, select project, [HIS0164], right click on HELP [Create New]
[Window].
Double click on the newly created help.

V. HELP WINDOW
V4.1 Help Message Number

Define a number between HW0001 to HW9999 as help number.
The maximum size of one help message is 21 lines; each line can contain 70 single-
byte characters.
V4.2 Help Message Comment

An explanatory description for each user-defined window can be defined with up to 24
V5. Help Window Definition

In System View, select project, [HIS0164], double click on HELP, and then on double click
on [HW0001].

V. HELP WINDOW

W. GRAPHIC BUILDER
W. GRAPHICS BUILDER
In this chapter, the features of the Graphics Builder are explained.
The Graphic Builder is used to create and edit graphic windows for operation and monitoring.
W1. Graphics Builder Environment

[Window].
YOKOGAWA SINGAPORE TRAINING CENTRE Page W1 of W105

W. GRAPHIC BUILDER
W1.1 Graphics
In System View, select project, [HIS0164], [WINDOW] double click on GR0001.

W. GRAPHIC BUILDER
W2. TOOLBARS
The Graphic Builder provides specific tools to create and edit graphic objects that
compose a Graphic window.
The graphics builder contains the following types of toolbars:
W2.1 Standard Toolbar

W. GRAPHIC BUILDER
W2.2 Draw Toolbar

W. GRAPHIC BUILDER
W2.3 HIS Functions Toolbar

W. GRAPHIC BUILDER
W2.3.1 Process Data – Character

Select [Data Display]-[Process Data-Character] from the [Insert] menu or
[Process Data-Character] button on the HIS functions tool bar to change the
cursor shape as shown below.
Click the mouse to draw a data character display object. The position clicked will
be the top left corner of the drawn object. At this time, the default will be
displayed as shown below.
RRRRRRR
In the graphic builder, while the data character display is selected, right click on
[Properties] or double click on the data character selected.
The property setting menu box of data characters display consists of the following
tabs.
W2.3.1A General Tab

This tab is used to set the attributes that are common to all graphic objects
created. The tab sets the object name, position and size, as well as whether the
object can be used as a tag object and whether data setting is possible during
debugging.

W. GRAPHIC BUILDER
Object Name
This sets the name of an object. The text of up to 15 double-width characters can
be entered as an object name. Use the name set here to search an object or to
identify an object for data input at debugging.
Position
This sets the display position of an object (x coordinate and y coordinate). The
coordinates (x coordinate and y coordinate) of the top left corner of a graphic
Object Size
Activate Tag Object

One of the methods to call a window from the Graphic window is to press the
window calling button after selecting an object. However, tag objects are limited
to the following objects to which a tag name (process data) can be assigned.
• Graphic primitive object with modifier
• Data character display object
• Data bar display object
• Instrument diagram object
These graphic objects can be used as tag objects once they are set as a tag
object in the tag object setting.
Set Data During Debugging

The display and action of graphic objects can be checked by using the debug
function of the Graphic window. The presence/absence of simulation data setting
during debugging can be set for graphic objects.

W. GRAPHIC BUILDER
W2.3.1B Text Tab

This tab is used to set the text format. The color of text itself as well as its
background can be set.
Fixed Pitch
Check Fixed Pitch, the font list will be filtered for displaying fixed-pitch font only.
TRUE Type
Check TRUE Type, the font list will be filtered for displaying true type font only.
Font
A font can be selected from all the fonts installed on the HIS.
Size
The font size can be set. The available size varies with the type of font.
Font Style
The bold, italic, and underline can be set for the text.
• Bold Font Formatting

This set whether or not to select a bold font.
• Italic Font Formatting

This sets whether or not to select a italic font.
• Underlined Formatting
This sets whether or not to select an underlined font.

W. GRAPHIC BUILDER
Text Color
One color can be selected from the color palette.
Background Color
One color can be selected from the color palette.
Transparent
This sets the color of text background to transparent.
Text Angle
This sets the angle of a character when moving the character with its bottom left
corner as the center of rotation. The default setting is 0.
[Text Angle] is not checked for default setting.
W2.3.1C Graphic Modify Tab

This tab is used to set change conditions for the attributes such as color, shape
and lighting/flashing status of a graphic object.
The graphic modify is a function that changes the object’s color, blinking status
and pattern based on the process data and the conditional formula.

W. GRAPHIC BUILDER
Change Type
This sets when to perform the testing on graphic modifier conditions. The
execution timing for the conditional testing can be selected from [Execute
Always], or [Execute First Time Only].
• Always Execute
While the conditional formula is true, change actions such as change color
and blinking or the default drawing are performed at any given time.
• Execute First Time Only

If the conditional formula is true when the Graphic window is called, change
actions such as change color and blinking is performed only once.
Conditional Formula
This sets the graphic modifier conditional formula to be used as the criteria of the
testing that is performed when modifying a graphic.
The following can be used for the graphic modifier conditional formula:
• Process data
(Example) PIC300.SV
• Integer constant
(Example) 100, 0
• Real number constant

(Example) 50.0, 0.50
• Hexadecimal constant
(Example) 0x0001
• Text constant
(Example) MAN, AUT
Continue the Conditional Formula Parsing

This sets whether or not to continue testing of the graphic modifier conditional
formula.
In the default setting, the testing is performed in sequence, starting from the
graphic modifier conditional formula of the condition number 1. If the condition is
satisfied, the change action will be executed and the graphic modifier conditional
formula testing is then completed.
When the continuation of testing is selected, the graphic modifier conditional
formula testing is continued even after the condition is satisfied. In this case, all
change actions associated with satisfied conditions are executed. However, when
multiple conditions with the same change action are satisfied, the execution of the
condition of a larger number will precede.

W. GRAPHIC BUILDER
Modify Condition
• Condition Number
Displays the condition number assigned to a graphic modifier condition
currently displayed.
• [Add] button to add a new graphic modifier condition. The [Add] button is
disabled when 8 conditional formulas already exist.
• [Change] button to reflect the contents of the graphic modifier condition

change to the data of current number.
• [Delete] button to delete the graphic modifier condition currently displayed. If

any of the condition numbers is freed, the remaining numbers will be
automatically reassigned.
Change Action
• Color Change
• Normal Change Color

This displays an object in the color specified. Select a color from the color
palette in the [Change Color].
• Change Alarm-specific Color

This displays an object in the alarm color of a function block. Set a tag
name of the function block in the conditional formula.
• Overview Color
This displays an object in the alarm color that is subject to monitoring
specified by the tag name or window name. The tag name or window
name is set in the conditional formula.
• Blink
• Yes
This enables an object to blink.
• Alarm Specific Blinking

This makes an object blink according to the alarm status of the
instrument diagram. Using the acknowledgment key may acknowledge
the alarm message.
• Screen Blinking
This makes an object blink. If this is selected, the object blinking will be
stopped when the acknowledgment operation is performed. If the status
of conditional formula changes after the acknowledgment operation, the
blinking will resume.

W. GRAPHIC BUILDER
• Overview Blinking
A tag name or a window name may be defined in the formula for
overview blinking test condition. The overview will have the same blinking
behavior as those for the tag name and the window name defined in the
formula.
When a tag name is defined in the formula, the graphic object shows
ON/OFF blinking in accordance to the ON/OFF alarm blinking of the
instrument faceplate with the tag name. The alarm blinking may be
acknowledged by acknowledgment operation.
Furthermore, the tag name defined may also be treated as a
representative tag name for the Graphic window.
• No
This disables an object from blinking.
• Modify String
Only available for text object.
This action changes a character string to another character string. Up to 16
alphanumeric characters for Modify String can be entered.
• Invert String
This sets the character string to be displayed in reverse video.
• Data Type
Specify the data type.
The data types include:
• Process Data
Process data can be used in conditional test formula for graphic modification.
The formula using process data is in “TagName.DataItem” syntax format.
Unary operators, comparison operators and brackets can be used for
conditional formulas.
• The applicable unary operators are shown below.

+, -, *, /, & (bitwise AND), | (bitwise OR), % (remainder)
• The comparison operators may be applied to conditional formulas are

shown below.
=, <> (not equal), >, <, >=, <=, and (AND conditional formulas), or (OR
conditional formulas)
• Actual notation examples are shown below:

FIC100.PV > 50.0
FIC100.PV + FIC300.PV <= FIC400.PV
FIC100.PV > 50.0 AND FIC200.PV < 20.0
FIC100.ALRM = “HI” or “HH”
%CI0001.PV & 0x00FF <> 0
One calculation formula may contain up to 8 data items and a total of 400
alphanumeric characters.
Examples of setting data and counting data items are shown below.
To display the average of process variables of the TIC100, TIC200, and
TIC300, specify as follows:
(TIC100.PV+TIC200.PV+TIC300.PV)/3

W. GRAPHIC BUILDER
• Recipe Data Unit Name Specification

When recipe data (Unit name specification) is the selected data type for
graphic object modification, the graphic calculation may be used. The syntax
is as follows:
UnitName.CommonBlockName.DataItem [X,Y]
( X, Y are array data.)
• Recipe Data Batch ID Specification

When recipe data (Batch ID specification) is the selected data type for graphic
object modification, the graphic calculation may be used. The syntax is as
follows:
BatchID.CommonBlockName.DataItem[X,Y]
( X, Y are array data.)
W2.3.1D Modify Coordinates Tab

This tab is used to set change conditions for the position of a graphic object.
The coordinate modifier is the function that moves the display position of a
graphic object according to the change in process data value.

W. GRAPHIC BUILDER
Coordinate Data of Coordinate Modifier

This reference coordinate data is used to determine the display position of a
graphic object.
The process data or conditional formula can be set for the coordinate data. In
addition, the high and low limits of the reference coordinate used for the change
range of each coordinate can also be set.
At least either one of the X-axis data or Y-axis data must be set. The graphic
object makes a 2-dimensional move when both axis data are set, and 1-
dimensional move when only either one of the coordinate data is set.
The following can be used for a coordinate data:
• Process data
(Example) PIC300.SV
(Example) 100, 0

(Example) 50.0, 0.50
(Example) 0x0001
• Recipe Data (Unit Name Specification)

(Example) UNIT01.SYSRCM.STATUS
• Recipe Data (Batch ID Specification)

(Example) 01-0041.SYSRCM.STATUS
The coordinate data used for coordinate modification vary with the data types.

W. GRAPHIC BUILDER
W2.3.1E Process Data- Character Tab

This tab is used to set the process data to be displayed as numeric values or
character strings. It is also used to set data type, display data format and display
data in order to display the process data or the array data as numeric values or
character strings.
The process data-character tab is specific to the data character display object.
Display Format Type

This sets the format, number of digits in integer portion and that in decimal point
portion of the data to be displayed.
The table below shows the numbers of digits in integer portion and decimal point
portion for each format

W. GRAPHIC BUILDER
• Numeric value
Numeric value is displayed.
• Percentage
Numeric data is normalized in its data span and displayed.
• Character strings
Character strings are displayed.
• Hexadecimal
Numeric data is converted into hexadecimal data and displayed.
(Example) 0x0001
• Date
Numeric data is converted into a date format and displayed.
(Example) 97/12/01
• Time
Numeric data is converted into a time format and displayed.
(Example) 15:38
• Tag-List
The display format, the number of digits before and after decimal point and
the process data are based on the settings of the Function Block Detail
Builder. While the recipe data (with unit name or batch ID) are based on the
settings of the Common Block Builder.
Number of Digits for Integer

From 1 to 99 digits can be set for the number of digits.
However, this item is not available when tag list is selected.
Number of Digits after the Decimal Point

This setting is available when numeric value or percent is selected for the display
format.
From 0 to 16 digits can be set for the number of digits.
Specify Position - Justification of Data Display

The base position of the displayed data.
The Right, Center, or Left Justified may be specified.
Leading Zero
When the digits of a datum less than the specified number of digits, the leading
zero may be specified to be placed before the valid numbers.
The leading zero may only be specified for the data with format type of [Number],
[Percent] or Hexadecimal].
Display Engineering Unit

To show or to hide the symbol of engineering unit symbol may be specified.

W. GRAPHIC BUILDER
Data Type
Set the data type of the data to be displayed.
• Process data
The following are examples of process data settings:
To display the setpoint value (SV) of the PIC300, specify “PIC300.SV.”
To display the alarm status of the PIC300, specify “PIC300.ALRM.”
To display the pushbutton text, specify “SW100.SWLB[2].”
To display the data displayed in the array, specify “FIC100.IJ[01,02].”
• Recipe data (unit name specification)
• Recipe data (batch ID specification)
• Tag Comment
The setting format when [Tag Comment] is selected as data type is as
follows:
“Tag Name”
• Graphic generic name

The syntax for data setting when [Graphic Generic Name] is selected as data
type is as follows. The same syntax may also be applied in a calculation
formula.
“Graphic Generic Name”
Display Data
This sets the data to be displayed as a data character display object.
• Process data
(Example) PIC300.SV
(Example) 100, 0

(Example) 50.0, 0.50
(Example) 0x0001
• Text constant
(Example) MAN, AUT
• recipe data (Batch ID)

(Example) 01-0041.SYSRCM.RECIPE

W. GRAPHIC BUILDER
W2.3.1F Data Bind Tab

This tab is used to bind different variants to graphic generic names.
Set No., Set Name, Comment

This sets the set name, set number and comment for graphic generic name set.
Set number can be defined in the range of 1 to 200.
For the set name, up to 16 alphanumeric characters can be used.
For the comment, up to 30 alphanumeric or 15 double-byte characters can be
used.
Set an individual generic name

Checking this item, the object graphic generic names and their corresponding
bindings can be defined.
When checking this [Set an Individual Generic Name] item, the bindings defined
on Data Bind tab for in file Properties tab can not be changed, the generic names
can not be modified any more.
Generic Name
The generic name selected from the list will be displayed.
A graphic generic name is an alias of tag name, item or value bound to a graphic
object. The representation of the alias is referred to as binding.

W. GRAPHIC BUILDER

W. GRAPHIC BUILDER
The syntax of a graphic generic name has a beginning letter $ (dollar sign)
followed by alphanumeric character 0 - 9, A - Z, _ (underscore), - (minus). Up to
16 alphanumeric characters, including $ sign; can be used to form a generic
name. Generic names are not case-sensitive. The graphic generic names start
with $_ (dollar and underscore) are system fixed graphic generic names, cannot
be defined by users.
Binding
The variant bound to the selected generic name will be displayed.
A variant to be bound to a graphic generic name can be the following 4 types of
data; a numeric value, a text string, a process variable or a recipe datum.
When binding a numeric value or a text string, the numeric value and the text
string can be directly used.
When binding process variables or recipe data, the following functions are
required.
• Function for Process Variable

@ProcessData()
Example @ProcessData(FIC100.ALARM)
• Function for Recipe Datum (according to Unit name)

@RecipeUnit()
Example @RecipeUnit(UT0100.DATA01.ITEM01)
• Function for Recipe Datum (according to Batch ID)

@RecipeBatchID()
Example @RecipeBatchID (01-0010.DATA01.ITEM01)
When Binding Process Data or Recipe Data

When a Graphic window is displayed, if a generic name bound with process data
or recipe data is changed, the communication data or the modified conditions
using the variants bound to the generic name will not be affected by the generic
name change.
This means that generic name changes during graphic display, but the process
data bound to the generic name are displaying the variants bound to the generic
name when the graphic window is initially opened.

W. GRAPHIC BUILDER
W2.3.2 Process Data – Bar

Select [Data Display]-[Data Bar Display]-[Rectangular Bar] from the [Insert] menu
or [Process Data-Bar] button on the HIS functions tool bar to change the cursor
shape as shown below.
A data rectangular bar display object can be drawn by dragging the mouse over
the area of the intended object. The default will be displayed as shown below.
To create a data rectangular bar display object from the center, position the
pointer at the center of the supposed object’s location and click the mouse. Drag
outward while holding down the [Ctrl] key.
Clicking the right mouse button while dragging cancels the drawing of the object.
The size of a drawn object can also be changed by dragging its handles.
In the graphic builder, while the process data- bar display is selected, right click
on [Properties] or double click on the process data- bar selected.
The property setting menu box of process data- bar display consists of the
following tabs.
W2.3.2A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.2B Fill Tab

This tab is used to set the fill type when filling a graphic object.
Fill Type
The four fill types include:
• Transparent
This sets the transparent color to fill an object.
• Fill
This fills an object with a single color. The color can be specified.
• Pattern
This fills an object with a pattern. The pattern’s style as well as its foreground
and background colors can be specified.
• Gradation
This fills an object with a gradient.
Fill Color
This is set when [Fill] is selected. One color can be selected from the color
palette.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER

graphic object according to the change in process data value. The Modify
Coordinates tab is used to set conditions for changing display positions of graphic
objects.

W. GRAPHIC BUILDER
W2.3.2E Process Data – Bar Tab

The Process Data-Bar tab is used to set display method and display data of the
rectangular bar in order to display process data or the array data in the form of a
rectangular bar.
Only one process data can be displayed in a rectangular bar.
Extending Direction of Bar

This sets the direction in which the rectangular bar data display area extends as
data increases: up, down, right or left.
U: High limit
L: Low limit

W. GRAPHIC BUILDER
Reference Point
This is the reference point for displaying process data using the rectangular bar.
Select either [0 point] in which the reference point is at one end of the rectangular
bar, or [Center] in which the reference point is at the center of the rectangular bar.
Data Type
The data types include [Process Data], [Recipe Data (Unit Name Specification)],
[Recipe Data (Batch ID Specification)].
Display Data
This sets the data to be displayed as a process data rectangular bar display
object.
The following can be used for display data of the process data rectangular bar
display:
• Process data
(Example) PIC300.SV
(Example) 100, 0
(Example) 50.0, 0.50
(Example) 0x0001
W2.3.2F Data Bind

On Data Bind tab, the bindings, variants bound to the generic names of objects,
can be defined.

W. GRAPHIC BUILDER
W2.3.3 Process Data – Arrow

Select [Data Display]-[Data Bar Display]-[Arrow Bar] from the [Insert] menu or
[Process Data-Arrow] button on the HIS functions tool bar to change the cursor
To draw an arrow process data bar display object, drag the mouse to draw the
moving range (line part of the arrow) of the intended object.
The moving range of the arrow bar displayed here will be either a line segment
that extends vertically or horizontally from the starting point.
To create an arrow process data bar display object from the center, position the
the mouse outward while holding down the [Ctrl] key.
Clicking the right mouse button while dragging cancels the drawing of the object .
In the graphic builder, while the process data - arrow display is selected, right
click on [Properties] or double click on the process data - arrow selected.
The property setting menu box of process data - arrow display consists of the
following tabs.

W. GRAPHIC BUILDER
W2.3.3A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.3B Fill Tab

This tab is used to set the fill type when filling a graphic object. There exist 3
types of fills, including transparent, solid color, and pattern.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER

graphic object according to the change in process data value. The Modify
Coordinates tab is used to set conditions for changing display positions of graphic
objects.
W2.3.3E Process Data - Arrow Tab

The Process Data-Arrow tab is used to set display method and display data of the
arrow bar in order to display process data in the form of an arrow bar.
Only one process data can be displayed in an arrow bar.
Move Arrow Direction

This sets the direction in which the data display arrow extends as data increases:
up, down, right or left.
U: High limit
L: Low limit

W. GRAPHIC BUILDER
Arrow Display Position

This is the relative position of the arrow to the display bar. The content of the
setting varies depending on the moving direction of an arrow.
When the arrow moves up and down, [Right Arrow] or [Left Arrow] can be
selected.
When the arrow moves sideways, [Up Arrow] or [Down Arrow] can be selected.
Data Type

W. GRAPHIC BUILDER
Display Data
This sets the data to be displayed on a graphic window as a process data arrow
bar display object.
The following can be used for the display data of a process data arrow bar
display:
• Process data
(Example) PIC300.SV
(Example) 100, 0
• Decimal point constant

(Example) 50.0, 0.50
(Example) 0x0001

can be defined.

W. GRAPHIC BUILDER
W2.3.4 Process Data - Circle

Select [Data Display]-[Data Bar Display]-[Circular Bar] from the [Insert] menu or
[Process Data-Circle] button on the HIS functions tool bar to change the cursor
To draw a data circle bar display object, drag the mouse from one end of the
intended object’s radius to the other. For this, the starting point becomes the
center of the circle. The default will be displayed as shown below.
To create an arrow process data bar display object from the center, position the
the mouse outward while holding down the [Ctrl] key.
In the graphic builder, while the process data- circle display is selected, right click
on [Properties] or double click on the process data- circle selected.
The property setting menu box of process data- circle display consists of the
following tabs.
W2.3.4A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.4B Fill Tab

This tab is used to set the fill type when filling a graphic object.
There exist 3 types of fill, including transparent, completely painted, or pattern.

W. GRAPHIC BUILDER

and lighting/flashing status of a graphic object.

W. GRAPHIC BUILDER

This tab is used to set change conditions for the position of a graphic object.

W. GRAPHIC BUILDER
W2.3.4E Process Data - Circle Tab

This tab is used to set the process data to be displayed in the data circle bar.
The process data-circle tab is specific to the data circle bar display object.
The Process Data-Circle tab is used to set data to be displayed in a circular bar
that indicates the data fluctuations by expanding or reducing its radius.
Data Type
Display Data
This sets the data to be displayed as a process data circular bar display object.
The following can be used for the display data of a process data circular bar
display:
• Process data
(Example) PIC300.SV
(Example) 100, 0
(Example) 50.0, 0.50
(Example) 0x0001

W. GRAPHIC BUILDER
High Limit Value, Low Limit Value

Set constants (9-digit numerical values) for the high and low limits of the data to
be displayed.
If display data has been set using process data, the settings of high and low limits
can be omitted. If the settings are omitted, high and low limits are taken from the
tag list.
If display data has been set using a conditional formula, high and low limits must
be set.


W. GRAPHIC BUILDER
W2.3.5 Touch Target

Select [Button]-[Touch Target] from the [Insert] menu or [Touch Target] button on
the HIS functions tool bar to change the cursor shape as shown below.
A touch target object can be drawn by dragging the mouse over the area of the
intended object. The default will be displayed as shown below.
To create a touch target object from the center, position the pointer at the center
of the supposed object’s location and click the mouse. Drag the mouse outward
while holding down the [Ctrl] key.
In the graphic builder, while the touch target is selected, right click on [Properties]
or double click on the touch target selected.
The property setting menu box of touch target display consists of the following
tabs.
W2.3.5A General Tab

The General tab is used to set basic attributes that are common to all objects
created.
The General tab sets the object name, display position and size, as well as
whether the object can be used as a tag object and whether data setting is
possible during debugging.

W. GRAPHIC BUILDER
W2.3.5B Function Tab

The Function tab consists of the area used for assigning functions and that for
setting the cursor movement sequence. The setting contents of the area vary with
the functions to be assigned.
Function Types
This sets the type of functions to be assigned to an object. Functions such as
system function key function and Graphic window specific function can be
assigned. The available function types are shown below:
• Call window
• Report Printout
• Others

W. GRAPHIC BUILDER
W2.3.5C Data Bind Tab

can be defined.

W. GRAPHIC BUILDER
W2.3.6 Push Button

Select [Button]-[Push Button] from the [Insert] menu or [Push Button] button on
the HIS functions tool bar to change the cursor shape as shown below.
A button object can be drawn by dragging the mouse over the area of the
intended object. The default will be displayed as shown below.
In the graphic builder, while the push button is selected, right click on [Properties]
or double click on the push button selected.
The property setting menu box of push button display consists of the following
tabs.
W2.3.6A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.6B Text Tab

This tab is used to set the text format. The colors of text itself and its background
can be set.

W. GRAPHIC BUILDER
W2.3.6C Label Tab

The setting can be performed in this tab only when drawing the push button
object. The tab is used to set the label to be attached to the push button, its color
and the safety guard.
Label Text String

This is the name displayed on the pushbutton. Up to 10 characters can be
entered for setting.
Attach Guard
This sets whether or not to attach a safety guard to a pushbutton. The pushbutton
with a guard becomes a two-push button. The first push releases the operation
guard, and the second push executes the function. The label character string is
grayed out when it is displayed with the operation disabled frame.
Figure Pushbutton with the Guard

W. GRAPHIC BUILDER
W2.3.6D Function Tab

This tab is used to set the functions to be assigned to a push button object. The
assignable functions include the window calling function, the function to control
the trend window that is specific to the graphic window, instrument command
operation and the menu window calling function.
Function Type
This sets the type of functions to be assigned to an object. Functions such as
system function key function and Graphic window specific function can be
assigned. The available function types are shown below:
• Call window
• Report Printout
• Others

W. GRAPHIC BUILDER
W.3.6E Graphic Modify Tab

and light-ing/ flashing status of a graphic object.
The push button can be hidden according to conditions.

W. GRAPHIC BUILDER
W2.3.6E Data Bind Tab


W. GRAPHIC BUILDER
W2.3.7 Faceplate
Select [Button]-[Face Plate Block Button] from the [Insert] menu or [Faceplate]
button on the HIS function tool bar to change the cursor shape as shown below.
A faceplate button object can be drawn by dragging the mouse over the area of
the intended object. The default will be displayed as shown below.
To create a faceplate button object from the center, position the pointer at the
center of the supposed object’s location and click the mouse. Drag the mouse
In the graphic builder, while the Faceplate Block Button is selected, right click on
[Properties] or double click on the Faceplate Block Button selected.
The property setting menu box of Faceplate Block Button display consists of the
following tabs.
W2.3.7A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.7B FacePlate Block Button Tab

This tab is used to set push buttons for the faceplate block to be assigned to a
faceplate block button object.
Parameter
This sets a tag name to be assigned to the faceplate block button. The following
are the input formats.
Display Cursor
Set whether the cursor movement sequence of the faceplate is displayed or not.

W. GRAPHIC BUILDER
Cursor Movement Sequence

The cursor moves between created touch targets every time the arrow key is
pressed on the Graphic window.
The cursor normally moves from one touch target to the nearest target in order of
target placement on the window, starting from the upper left corner. However, a
desired movement order can also be specified, overriding the cursor movement
order by target placement.
The cursor movement order is specified by assigning priority numbers to the
objects. The movement order number can be set for the objects using an integer
within the range from 1to 99999. Priority numbers can be set as many as the
number of the objects that have cursor function, drawn in a window.


W. GRAPHIC BUILDER
W2.3.8 Instrument Diagram

Select [Instrument Diagram] from the [Insert] menu or [Instrument Diagram]
button on the HIS functions tool bar to change the cursor shape as shown below.
An instrument diagram object can be drawn by dragging the mouse over the area
of the intended object. However, the vertical to horizontal size ratio of the
instrument diagram is fixed.
To create a instrument diagram object from the center, position the pointer at the
The default will be displayed as shown below.
In the graphic builder, while the Instrument Diagram is selected, right click on
[Properties] or double click on the Instrument Diagram selected.
The property setting menu box of Instrument Diagram display consists of the
following tabs.

W. GRAPHIC BUILDER
W2.3.8A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.8B Instrument Diagram Tab

This tab is used to set the function block displayed as an instrument diagram and
The display contents of the instrument diagram.
The instrument diagram tab is specific to the instrument diagram object.
Display Format
• Normal
The entire display contents of the instrument diagram are displayed in full.
• Compact
The display contents of the instrument diagram are simplified. In compact
type, the digital display of data is no longer available.
Instrument Diagram Width

This sets whether the instrument diagram is displayed in default width (single-
width) or in double width.
However, even if the double width is specified, the actual HIS display may only be
in single-width (default size) depending on the type of an instrument faceplate.
Operation Control Key

The operation key (INC/DEC key) on the console type HIS may be specified for
the corresponding instrument faceplate s on the display position 1 to 8.
For the double-width instrument faceplate, it may be specified to the adjacent two
positions. Thus, on position 8, the double-width instrument faceplate can not be
assigned. For example, if position 3 and 4 are available, it may be specified on
position 3.

W. GRAPHIC BUILDER
Tag Name
Enter text for the tag name of an instrument diagram to be displayed.


W. GRAPHIC BUILDER
W2.3.9 Window
To display a window that satisfies specific conditions, create a window object
using the window tool.
Select [Window] from the [Insert] menu or [Window] button on the HIS functions
tool bar to change the cursor shape as shown below.
A window object can be drawn by dragging the mouse over the area of the
intended object. However, when “Display in the default size” is set in the window
tab, the object is displayed in the default size regardless of the size of the object
drawn by dragging the mouth. The default will be displayed as shown below.
Clicking the right mouse button while dragging it cancels the drawing of the
object.
To create a window object from the center, position the pointer at the center of
the supposed object’s location and click the mouse. Drag the mouse outward
In the graphic builder, while the window object is selected, right click on
[Properties] or double click on the window object selected.
The property setting menu box of window object display consists of the following
tabs.

W. GRAPHIC BUILDER
W2.3.9A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.9B Window Tab

This tab is used to set the name for a window to be displayed and the conditions
to display windows.
The window tab is specific to the window object.
Window Name
Enter the name of the window to be called and displayed. Up to 48 characters
can be entered.
Display Timing
• Initial display
If “Initial display” is selected, the specified window will be displayed when the
window is called.
• Conditional display
When “Conditional display” is selected, the specified window will be displayed
if the condition based on the conditional formula is satisfied, and erased if
not.
Display in the Default Size

This sets whether or not to display the window in the HIS default size.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER
W2.3.10 Message
To display the messages sent from FCS on the Graphic window, create a
message object using the message tool.
Select [Message] from the [Insert] menu or [Message] button on the HIS functions
tool bar to change the cursor shape as shown below.
Drag the mouse in the area you want to display a message. The message object
will appear in the selected area. The number of the characters of the message
displayed in the message object is automatically determined by the size of the
message object. The default will be displayed as shown below.
The size of a drawn object can also be changed by dragging its handles.
To create a window display object from the center, position the pointer at the
In the graphic builder, while the message tool is selected, right click on
[Properties] or double click on the message tool selected.
The property setting menu box of message tool display consists of the following
tabs.

W. GRAPHIC BUILDER
W2.3.10A General Tab

debugging.

W. GRAPHIC BUILDER
W2.3.10B Text Tab

can be set.

W. GRAPHIC BUILDER
W2.3.10C Message Tab

This tab is used to set the message types and the search range for collecting
messages.
The message tab is specific to the message object.
Message Type
The three types of messages, [Process Alarm Message], [Operator Guide
Message], and [System Alarm Message] can be displayed in the Graphic window.
Number of Digits
A message can be displayed up to the full width of the drawing display area. This
sets the number of characters (number of digits) of a message to be displayed in
one line.
Number of Lines
This sets the number of lines used to display a message. The maximum number
of lines that can be set is up to the height of the window.
Message Range
This is the search range used when collecting messages. Select the range from
[Project], [Station], [Tag], [Plant Hierarchy], or [No specified]. If [No specification]
is selected, all messages generated will be collected.
Only [Project], [Station] and [No specification] can be set for message range
when the system alarm message is selected.

W. GRAPHIC BUILDER
Parameter
When specifying items other than [No specification] at the Message Range, enter
a project ID, a station name, a tag name or a plant hierarchy name as the scope
of retrieving data to acquire messages.
The maximum numbers of alphanumeric characters that can be entered for the
parameter are as follows:
• Project ID: Two

• Station name: Eight
• Tag name: 25
Message Number
This sets whether or not to specify a system alarm message to be displayed,
when the system alarm message is selected as a message type.
W2.3.10D Data Bind Tab


W. GRAPHIC BUILDER
W2.3.11 Dialog Name

To display on a Graphic window the name of a dialog that is required to be
displayed in a unit instrument etc., user may create a dialog name object using
the dialog name tool. It will be even more convenient if the dialog name is
combined with a push button.
Select [Dialog Name] from the [Insert] menu or [Dialog Name] button on the HIS
functions tool bar to change the cursor shape as shown below.
Click the mouse to draw a dialog name object. The position clicked will be the top
left corner of the drawn object. The default will be displayed as shown below.
To create a dialog name object from the center, position the pointer at the center
of the supposed object’s location and click the mouse. Drag the mouse outward
In the graphic builder, while the dialog name tool is selected, right click on
[Properties] or double click on the dialog name tool selected.
The property setting menu box of dialog name tool display consists of the
following tabs.

W. GRAPHIC BUILDER

debugging.

W. GRAPHIC BUILDER
W2.3.11B Text Tab

can be set.

W. GRAPHIC BUILDER
W.3.11C Dialog Name Tab

This tab is used to set the tag names associated with the dialog name object. The
dialog name tab is specific to the dialog name object.
Key Type
Set the key type to designate the function block to initiate a request to display a
dialog box.
As the key types, select the tag name or the batch ID.
Key
Set the function block that initiates a request to display a dialog box. Setting
method varies with the key type.
When [Tag Name] is selected, syntax check is performed on entered character
string.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER
W2.3.12 Trend
To display the trend data on the Graphic window, create a trend object using the
trend tool. The displayable trend data include the trend point and the trend group.
Select [Trend] from the [Insert] menu or [Trend] button on the HIS functions tool
bar to change the cursor shape as shown below.
A trend object can be drawn by dragging the mouse over the area of the intended
object. The default will be displayed as shown below.
To create a trend object from the center, position the pointer at the center of the
supposed object’s location and click the mouse. Drag the mouse outward while
holding down the [Ctrl] key.
In the graphic builder, while the dialog name tool is selected, right click on
[Properties] or double click on the dialog name tool selected.
The property setting menu box of dialog name tool display consists of the
following tabs.

W. GRAPHIC BUILDER

debugging.

W. GRAPHIC BUILDER
W2.3.12B Trend Tab

This tab is used to set the trend group name or the tag name that are the
acquisition source of the trend data to be displayed in the trend object.
The trend tab is specific to the trend object.
Display Type
Trend Point, Trend Group and Tuning Trend are the trend data types can be
displayed on Graphic windows.
Tag Name.Data Item

If the trend point is selected as a display type, select the trend data to be
displayed from the process data that have been assigned to the trend gathering
pen via the “trend gathering pen assignment definition builder,” and set it in the
“tag name.data item” format.
Sampling Period
This setting is available only when Display Type is set with [Trend Point].
When the same tag name is assigned to trend gathering pens in different
sampling period, specify the trend sampling period to particularize a trend
gathering pen.
Time Axis
Set a zoom level for Time Axis to this field.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER
W2.3.13 Overview
The overview object is a push button type object that has the functions to display
the statuses of function blocks and windows, and to call windows, etc. To create
an overview object, use the overview tool. Up to 64 overview objects can be
created per window.
Select [Overview] from the [Insert] menu or [Overview] button on the HIS
functions tool bar to change the cursor shape as shown below.
An overview object can be drawn by dragging the mouse over the area of the
Intended object. The default will be displayed as shown below.
To create an overview object from the center, position the pointer at the center of
the supposed object’s location and click the mouse. Drag the mouse outward
In the graphic builder, while the overview tool is selected, right click on
[Properties] or double click on the overview tool selected.
The property setting menu box of overview tool display consists of the following
tabs.

W. GRAPHIC BUILDER

created.
The tab sets the object name, position and size, as well as whether the object
can be used as a tag object and whether data setting is possible during
debugging.

W. GRAPHIC BUILDER
W2.3.13B Overview Tab

This tab is used to set the types of overview objects, process data to be
displayed, alarm notification, and windows to be called.
The overview tab is specific to the overview object.
Type
[Tag name], [Tag name (with tag mark)], [Window name], [Annunciator] and
[Comment] can be selected as a monitoring target.
The table below lists the types of monitoring targets and the setting items for
each target.

W. GRAPHIC BUILDER
Tag Name
Enter text for the tag name to be assigned to an overview object. Up to 25
characters can be entered.
Window Name
Enter text for the window name to be assigned to an overview object. Up to 16
Annunciator Name
Enter text for the annunciator message name to be assigned to an overview
object. Up to 25 characters can be entered.
Comment
Enter text for the comment name to be assigned to an overview object. Up to 16
First Line Display Type

Select either a tag name or tag comment as a label to be displayed in the first line
of an overview object.
Alarm-specific Blinking
Checking the [Alarm-specific Blinking] check box will enable the overview objects
to
Indicate the blinking status of the tag name or the window name, allowing the
alarm
to be acknowledged.
Specify Font
Checking [Specify font] check box enables to specify font displayed on overview
object. The following three items need to be defined.
• Font type
• Font size
• Font style

W. GRAPHIC BUILDER
W2.3.13C Function Tab

This tab is used to set the function to call other window from an overview object,
etc.

W. GRAPHIC BUILDER


W. GRAPHIC BUILDER
W2.3.14 Control
The control object is an object with Active X.
In order to change the cursor shape as shown below Select [Control] from the
[Insert] menu or [Control] button from the HIS functions tool bar.
Dragging the mouse causes the drawing of a control object according to the area
of the mouse movement, resulting in a four-sided object surrounded by a solid
white line. The default will be displayed as shown below.
For distinction from other four-sided objects, a four-sided object representing a

control object displays the type of the ActiveX control object inside itself. Clicking
the right mouse button while dragging cancels the drawing of the object.
To create a control object from the center, position the pointer at the center of the
Supposed object’s location and click the mouse. Drag the mouse outward while
holding down the [Ctrl] key.
In the graphic builder, while the control tool is selected, right click on [Properties]
or double click on the control tool selected.
The property setting menu box of control tool display consists of the following
tabs.

W. GRAPHIC BUILDER

created.
The tab sets the object name, position and size, as well as whether the object
can be used as a tag object and whether data setting is possible during
debugging.

W. GRAPHIC BUILDER
W2.3.14B Control Tab

This tab is used to set the types of ActiveX controls displayed as control objects.
The control tab is specific to the control objects.

W. GRAPHIC BUILDER
W2.4 Format Toolbar

W. GRAPHIC BUILDER
W2.5 Edit Object Toolbar

W. GRAPHIC BUILDER
W2.6 Parts Toolbar
W2.6.1 Parts
In the Graphic Builder, a portion of existing Graphic windows can be reused by
saving objects as parts. This is called part registration and quotation.
Select [Parts...] on the [Insert] menu may call out the Parts window or clicking the
Pars button on toolbar may call out the Parts window too.
Types of Parts File
• System
These system defined parts are given together with the CS3000 software by
default.
• User
To open an existing parts file, click [Open] on [File] menu, then choose the
file to be opened.

W. GRAPHIC BUILDER
To create a new parts file, choose [User] option on Parts Window, then click
[Create New] on [File] menu. Drag and drop the new parts from the graphic
builder.
The part registration and quotation are performed between the Parts window and
the Graphic window that is being created.
The part names registered in the Parts window are shown in the parts list.
• Part registration
To register parts in the user part file, select an object to be saved as a part
from the graphic builder, and drag it to the part image display area on the part
window.
• Part re-utilization
To re-utilize a part, drag it from the part image display area on the part
window to the graphic builder.

W. GRAPHIC BUILDER
Part Part
Re-Utilization Quotation
W2.6.2 Linked Part

Linked parts are the embedded parts whose states are linked to the sources of
the parts. The parts embedded in many kinds of windows and linked to the
sources are all called “linked parts.”
Multiple objects can be combined into a single part and that part can be
registered to allow it to be reused in the Graphic Builder. These registered parts
are called “parts.” The registered parts can be inserted as objects (hereinafter
referred to as “part objects”) in the graphic window. There are two types of parts:
“normal parts” and “linked parts.”

W. GRAPHIC BUILDER
Basic Operation Flow when using Linked Parts
Creating Linked Part
Inserting Linked Part

to Graphic Windows
Editing Linked Part Repeat the operations if needed.
Updating and downloading

Linked Part
• Creating Linked Part

Creates a new linked part.
After a linked part is created in the Linked-Part List Window, perform one or both
of the following operations:
• Register an object that exists in the Graphic Builder or register a normal part
as a linked part.
• Edit a linked part using the Linked-Part Editor Window.
• Inserting a Linked Part to Graphic Window

The Graphic Builder is used to insert a linked part to a graphic window.
• Editing Linked Parts

Existing linked parts can be edited if needed.
Perform one or both of the following operations:
• Re-register an object that exists in the Graphic Builder or register a normal

part as a linked part.
• Edit an existing linked part using the Linked-Part Editor Window.
• Update and Downloading Linked Part Object

After a linked part is modified, the inserted linked part object is updated in the
Graphic window.
After the update is complete, the builder file that embedded with the linked part
can be downloaded to the HIS.
Folder of Linked Part Files

The linked part files are stored in the following folder:
{Project Folder} \LinkParts
C:\CS1000\eng\BkProject\R3Project\LinkParts\Pumpt1.lpt
\Pimp2.lpt
\COMMON\Valve1.lpt
\Valve2.lpt
C:\CS3000\eng\BkProject\R3Project\LinkParts\Pumpt1.lpt
\Pimp2.lpt
\COMMON\Valve1.lpt
\Valve2.lpt

W. GRAPHIC BUILDER
Registering an Object as a Linked Part
1. Select [Linked Part...] from the [Insert] menu in the Graphic Builder, or click the
tool button that starts the Linked-Part List Window.
2. Select [Create New Folder] from the [File] menu in the Linked-Part List
Window, or click the [Create New Folder] button.
3. Select [Create New Linked Part] from the [File] menu in the Linked-Part List
Window, or click the [Create New Linked Part] button.
Double on the [New Part File] as shown above to create the new linked part.
4. Select [Save] from the [File] menu in the Linked-Part List Window.

W. GRAPHIC BUILDER
Inserting a Linked Part to Graphic Window

Select [Linked Part...] from the [Insert] menu in the Graphic Builder, or click the
tool button that starts the Linked-Part List Window.
Drag and Drop

W. GRAPHIC BUILDER
W2.7 Background Screen Bitmap and Soft Key

W2.7.1 Background Screen Bitmap
This function imports a bitmap file (*.bmp, *.dib) as a graphic object.
In the graphic builder, from the pull down menu, select [Insert] [Diagram] to
display bitmap file selection.
This function imports a bitmap file (*.bmp, *.dib) as a window background

image.
In the graphic builder, from the pull down menu, select
[Background Screen Bitmap] [Import] to display bitmap file selection.
W2.7.2 Soft Key

The softkeys are the push buttons that are displayed in the predetermined
positions.
Up to 8 softkeys can be assigned to a single Graphic window. The assigned
softkeys are always displayed so that their functions can be executed at all times.
W2.7.2A Soft Key Tab

Select the [Softkey...] from the [Insert] menu of the Graphic Builder to display the
dialog box in which to assign softkeys.
When the graphic window with softkeys assigned is displayed, the softkeys are
positioned outside of the drawing area (the area in which objects are drawn on
the Graphic window.)

W. GRAPHIC BUILDER
No.
The softkeys are already assigned numbers 1 to 8 according to the display
position.
• [Change] button: To reflect the change content of the softkey currently

set to the softkey of the current number.
• [Delete] button: To delete the softkey currently displayed.
Label
The text of up to 20 alphanumeric characters or 10 double-byte characters
can be set for the softkey label.
Attach Guard
A softkey with a guard becomes a two-push button. The first push releases
the operation disabled frame, and the second push executes the function
(two-step operation).
This sets whether or not to attach a safety guard to a softkey.

W. GRAPHIC BUILDER
W2.7.2B Text Tab

On the text tab of the soft key dialog box, the text scripts and text format may
be defined.
The Text tab is used to set the format, color and background color of the text.

W. GRAPHIC BUILDER
W2.7.2C Function Tab

On the function tab of the soft key dialog box, the function of the soft key may
be assigned.

W. GRAPHIC BUILDER
W3. Graphic Builder Operation Mode

The Graphic Builder is divided into the following two types of operating modes, depending
on the start up method.
• Engineering mode
The Graphic Builder becomes engineering mode when started directly from the
System View or via other builders from the System View.
• Windows mode
The Graphic Builder becomes Windows mode when started individually as a
Windows application.
The following table shows the differences between Graphic Builder functions in different
modes.

W. GRAPHIC BUILDER
W4. FILE PROPERTIES

The file property sheet is used to set the type, the display size, the refresh cycle, and the
background color for a Graphic window, and to bind a graphic generic name and the
window linked function.
In the graphic builder, from the pull down menu, click File [Properties].
The file property sheet consists of the following four types of tabs.
• Outline tab
Tab used to display a file name, a project name, file creation date/time, and update
date/time.

W. GRAPHIC BUILDER
• Attribute tab
Tab used to display or set properties related to the windows.
Panel Type
The three types of windows include: [Graphic window], [Overview window], and
[Control window].
Size
The size of new graphic windows can be set in dot units, using a slider. The following
shows the selection of sizes:
• 1600 X 1072
• 1280 X 858
• 1024 X 686 (Default)
• 800 X 536
• 640 X 429
When setting the window to a user defined size, the number of vertical pixels and
horizontal pixels can be set using the spin boxes.
The setting values can also be directly entered to the boxes.
Screen Refresh Period

This is the interval at which the entire graphic window display is updated. The unit for
update intervals is a multiple of the basic update cycle unit (1 Sec.) for HIS operation
and monitoring windows. The default setting is the same as the basic update cycle
unit.

W. GRAPHIC BUILDER
Window Background Color

This is the background color used when displaying Graphic windows. The
background color set here is also used in the work areas of the Graphic Builder.
Choose one color from 256-color palette for the background color.
• Data Bind tab

Tab used to set the Set name and comment, Generic name and data bound to the
graphic generic name.

W. GRAPHIC BUILDER
• Window Linked Function tab

The window linked function tab is used to enable the function of executing assigned
functions and its timing or tab used to set functions to be executed by linking with
Graphic windows.
No.
This is the number to assign to a function to be executed. Select from numbers 1 to 8
by using the spin box.
Execution Timing
This is the timing to execute the assigned function. Selected the execution timing
from display start or display end of Graphic windows.

W. GRAPHIC BUILDER
Function Definition
This sets the assigning function. Functions used in softkeys and touch target can be
set on this tab, as well.
The assigning function is set using the dialog displayed when the [Function Definition]
button is pressed.

W. GRAPHIC BUILDER
W5. SETTING THE OPTIONS

The option dialog box is used to set the Graphic Builder’s operating environment, such as
the properties that are used to create a new object.
From the graphic builder, from the pull down menu, click Tools [Options].
The Options dialog box consists of the Options and Debug tabs.
• Options Tab
Check if tag/ window name exist when saving

When saving a file, the system checks whether or not a tag name or window name
linked with an object on the graphic window exists, and determines whether or not to
display the result in the message area.
If the tag name or the window name linked with the object does not exist, such
objects will not properly function on the graphic windows.
Property during Draw

This is the setting for property values used to create a new graphic object.
Select one of the following:
• Default property value

• Property value when the previous graphic object was created.
Double Click
This is the setting for operation when an object is double-clicked.
Select either one of the following.
• Open the property setting menu dialog box for the double-clicked object.
• Start point correction of the double-clicked object.
Maximum levels of [Undo].

Set the number of times to undo the most recent actions by selecting the [Undo] on
the edit menu bar or standard tool bar. The maximum number of times that can be set
for valid “undo” operations is five.

W. GRAPHIC BUILDER
• Debug Tab
Specify Window Size

Set whether the size of the debug window is specified or not.
Window Size
Specify the size of the graphic window to start up.
Select one from [Large Size], [Medium Size], [Special Size].
Parameter
Specify the parameter to be passed to the graphic window by start command. Limited
to 2000 byte.

W. GRAPHIC BUILDER
W6.1 DEBUG FUNCTION ON THE GRAPHIC BUILDER

The debug function checks on how the operation and monitoring screen will display the
Graphic window that is being editing via the Graphic Builder. Action verification on several
functions can also be performed, by setting simulation data.
• Image Verification
The debug function checks the images of window background, object display, and
data display on the operation and monitoring screen.
• Window background
Checks the background color and background bitmap display.
• Object display
Checks the object display.
However, only the area indicating frame are displayed for the window display
(initial
display, conditional display), message, instrument faceplate, overview, trend,
dialog
name, and faceplate.
• Data display (Character display, data bar display, graph display)

For data character display, data bar display and graph display, an image to be
displayed can be checked by setting simulation data.
However, if the high and low limits are omitted in the tab for data bar display or
graph display, high and low limits of simulation data must be set.
• Action Verification
The debug function checks actions corresponding to the conditional formulas
specified in the graphic and coordinate modifiers, and the functions assigned to
buttons.
• Verification with the graphic and coordinate modifiers

For a graphic modifier, it checks whether the color and shape change, by
responding to the simulation data, as specified in the setting. For a coordinate
modifier, it checks whether the coordinates change, by responding to the
simulation data, as specified in the setting.
However, the above does not apply to the overview color change.
• Buttons (Pushbuttons and touch targets)

For buttons, a dialog indicating the definition contents is displayed.

W. GRAPHIC BUILDER
W6.2 DEBUG DIALOG

Select the [Debug] from the [Tools] menu of the Graphic Builder to start the Graphic
window and simultaneously display a dialog in which to set simulation process data for
debugging.
These buttons are used to end the debug function or to reflect simulation data to the
Display image.
• Exit Debug
This closes the Graphic window and debug dialog displayed for debugging.
• Update Data
This reflects the set simulation data to the Graphic window.
Data Setting Area

Simulation data required for debugging can be set for each object type.
Primitive Type
This is the type of the object, object name and display coordinates of an object that is
being set. This is displayed automatically when a data may be selected from the list
view.
Tag Name for Debug

The debug target may be specified in the format of Tag Name.Item. It can also be
selected on the list view displayed automatically when an object is selected.
The data display and action may be confirmed.
Simulation Data Type

This is the type of data to be set for simulation data. Select a type for setting from
[Numeric Value], [Character], and [Undefined].
Select “Undefined” if the debugging using simulation data is not performed.

W. GRAPHIC BUILDER
Simulation Data Value

This is the value set for simulation data. Use the text edit box to set the data value.
Data Type Display

When data is selected form the list view, the data type displays automatically.
High and Low Limits of Simulation Data

High and low limits of simulation data. If the settings for high and low limits of data are
omitted for the data bar display object or graph display object, the high and low limits
of simulation data must be set in order to verify actions of the object. Use the text edit
box to set the limits.
Function Block Alarm Name

This is the alarm name of the function block that is set for confirming the alarm color
change of the graphic modifier.
Setting the Blink

To confirm whether the blink by alarm on the graphic modifier is performing properly,
specify whether or not to set “blinking” for the alarm status of the function block.

W. GRAPHIC BUILDER

X. TEST FUNCTION
X. TEST FUNCTION
The Test Function is a group of tools (option packages) for efficiently debugging FCS
software created by the user.
This chapter covers the types of tests, operating environments, and test procedures.
X1. Types of Test

• Virtual tests
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.
• Target tests.
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.
YOKOGAWA SINGAPORE TRAINING CENTRE Page X1 of X35

X. TEST FUNCTION
Virtual Test and Target Test Functions List

Virtual tests and target tests execute different functions. The table below lists the virtual
test and target test functions.

X. TEST FUNCTION
X2. Operating Environment

The operating environments necessary to execute the Test Functions are the same
environments for the System Generation Functions.
Hardware Environment
Software Environment

X. TEST FUNCTION

X. TEST FUNCTION

X. TEST FUNCTION
X3. TEST PROCEDURES

X. TEST FUNCTION
X4. Functions of Test Function Main Menu Window

The Test Functions main menu window operates the test target FCS/FCS simulator and
calls the Test Function sub-windows.
Title bar Target status Target station
display area and test mode
Menu bar
Test function main

menu window
common toolbar
Sub-window
toolbar
Sub-window
displayed in
client area
Message
display area
X5. I/O Disconnect/Connect

The I/O Disconnect/Connect Function connects actual FCS process I/O units in the
Target Test mode. This function allows you to test the software without using an actual
I/O unit. The I/O Disconnect/Connect Function uses the I/O Disconnect/Connect setup
dialog box to disconnect and connect individual I/O units. You can simulate the process
input and output of a cut-off I/O unit by using the wiring function.
In the virtual test mode, I/O units are always cut-off. Therefore, it does not have an
I/O Disconnect/Connect Function.

X. TEST FUNCTION
X5.1 I/O Disconnect Setup Dialog Box : PFCS/SFCS
X5.2 I/O Disconnect Setup Dialog Box: LFCS

Use the I/O Disconnect Setup dialog box to disconnect/connect I/O.

X. TEST FUNCTION
X5.3 I/O Disconnect Setup Dialog Box: KFCS

Use the I/O Disconnect Setup dialog box to disconnect/connect I/O.
Dropdown list box to switch Process I/O setting

and Communication I/O setting
Dropdown list box for selecting node number
The present status of I/O unit
Type of I/O slot
I/O Slot number
FIO Node number of test target FCS using dropdown list box

X. TEST FUNCTION
X6. WIRING FUNCTION

Functions that perform virtual wiring at the process I/O terminals of an I/O module are
called “wiring functions.” These functions allow you test the FCS/FCS simulator control
operation without using an actual I/O unit.
Test function has two types of wiring functions:
X6.1 Wiring Edit Functions

To operate the wiring functions, the wiring must be defined and the wiring data must
be downloaded.
The wiring edit functions define the wiring, and consist of the functions listed below.

X. TEST FUNCTION
Use the wiring edit functions when changing the wiring data automatically created
during Test Function starting, and when defining wiring data for I/O units cut-off
during a test. Edit the wiring using the wiring edit sub-window.
You can define the wiring for up to 1024 points per target FCS/FCS simulator. (Total
number of defined records is 1024.)
X6.1.1A Types of Wiring

There are three types of wiring:
• Wiring between Terminals

“Wiring between terminals” converts the output signal from the process I/O terminal
and inputs it to the process input terminal. It means “Convert f(x) value x from the
output terminal and return value y=f(x) to the input terminal”. Where conversion f(x) is
called the “wiring type.” The wiring source output format and wiring destination input
format combination determines the wiring type.

X. TEST FUNCTION
• Time-Series Data Wiring

“Time-series data wiring” inputs time-series data created using a function to the
process input terminals. It means “Write the output value y=g of function g(t) that
created the time-series data to the input terminal.” Here t is the elapsed time.
The Test Function has the following four types of time-series data wiring function g(t):

X. TEST FUNCTION
• Simple Wiring
“Simple wiring” converts the MV value of the wiring source function block and inputs it
to the process input terminal.
If the wiring destination is an analog input terminal, you can define the wiring without
being conscious of the output terminal signal type.
X6.1.1B Wiring Definition Items

These items must be defined to use the wiring function. Define the wiring in record
units using the wiring edit sub-window.
The wiring definition items are:
• Wiring destination
This item specifies the wiring destination in one of the following formats:
•“Tag name” + “.” + “terminal name of function block to be linked”

• Process input terminal No. (%Z, %W), or tag name
• Wiring source
This item specifies the wiring source in one of the following formats:
•“Tag name” + “.”+ “terminal name of function block to be linked”

• Process input terminal No. (%Z, %W), or tag name

X. TEST FUNCTION
• Wiring type
This item specifies the wiring type matching the process I/O terminal signal type.
To specify the wiring type, select the applicable type from the table below
according to the signal types of the wiring source and wiring destination:
• Wiring constant
Wiring Constant is wiring type parameter. The table below shows the wiring
constants that can be specified.

X. TEST FUNCTION

X. TEST FUNCTION
X6.1.1C Automatic Data Wiring Creation

The automatic wiring data creation function automatically creates wiring definitions
based on the FCS definition contents, and creates wiring data in control drawing
units. The automatically created wiring data file (wiring file) uses the control drawing
name as its file name.
When automatic wiring data

creation function starts, first it
automatically determines the
wiring destination process input
terminal.
Then it makes that process input
terminal the start point and
searches for the process output
terminal by going from input side
to output side according to the
loop conditions.
The process output terminal
searched here becomes the
wiring source.
After the automatic wiring data
creation function determines the
wiring destination and wiring
source in this manner, it
automatically determines the
wiring type and wiring constant
for that wiring.
X6.1.1D Wiring Data Storage

This function stores the new data when the wiring data is changed using the wiring
edit function. There are two types of storage, “overwrite” and “Save as another file.”
Files that store wiring data is called wiring files.
•Overwrite
This function stores the wiring data under the currently opened name. Inspection
is per-formed at storage.
•Save as another File

This function displays a dialog box for storage file name specification and stores
the data with a new file name in this box. Verification will be performed after
saving.

X. TEST FUNCTION
X6.1.1E Wiring Data Downloading

When changing the wiring data using wiring edit function, the changed content can be
reflected in the FCS by wiring data downloading function.
This function reflects the changes to the FCS when the wiring data was changed
using the wiring edit function. When executed, this function performs overwriting and
displays a
Wiring Download dialog box for downloading the wiring data to the test target
FCS/FCS simulator. This function downloads the wiring data to the test target
FCS/FCS simulator in wiring file units. The wiring file to be downloaded is selected
using the Wiring Download dialog box.
When downloading wiring files,

the non-selected previously
downloaded wiring files are
removed from the test target
FCS or test FCS simulator.
Therefore, when downloading
the newly defined wiring file,
download it together with the
previously downloaded wiring
files.
X6.2 Wiring Operation Functions

The wiring operation functions display the wiring status of the FCS/FCS simulator
currently being tested and perform operations related to wiring during test execution.
The wiring operation functions use the Wiring Operation sub-window. The Test
Function has the following wiring operation functions:

X. TEST FUNCTION
X6.2.1A Display Cycle Change

This function changes (1 to 100 seconds) the wiring status display (status item)
refresh cycle of the test target FCS displayed in the Wiring Operation sub-window.
X6.2.1B Wiring On/Off

This function turns the wiring of the record selected in the Wiring Operation sub-
window on and off. It is enabled for both wiring between terminals and time-series
data wiring.
X6.2.1C Wiring Execution

This function creates time-series data for one cycle only. When performed, this
function continuously creates data until the elapsed time reaches the time-series data
cycle time.
When the elapsed time reaches the time-series data cycle time, this function stops
creating data. The data is stored when the elapsed time reached the cycle time.
X6.2.1D Wiring Continuous Execution

This function creates time-series data until the Stop or Pause operation is performed.
When the wiring type Inc or Dec is executed continuously, the following actions result.
When the wiring type is Inc, the elapsed time t=Cycle is also t=0 of the next cycle. As
a result, even though the elapsed time is t=Cycle, the generated data does not
become the value set in Gain, but becomes the value set in Bias.
Similarly, when the wiring type is Dec, even if the elapsed time becomes t=Cycle, the
generated data does not become the value set in Bias, but becomes the value set in
Gain.
X6.2.1E Wiring Stop

This function stops time-series data creation and resets the elapsed time and data to
the initial value.

X. TEST FUNCTION
X6.2.1F Wiring Pause

This function temporarily stops time-series data creation and stores the current
elapsed time and data.
You can resume time-series data creation from the paused point by performing the
Execution or Continuous Execution operation.
X6.2.1G Suspend
This function suspends all the test target FCS/FCS simulator wiring functions. The
suspended wiring functions can be returned to the active state.
X6.2.1H Wiring Change

This function directly changes the wiring defined for the current FCS.
The wiring change function is called from the Wiring Operation sub-window and is
performed at the Wiring Change dialog box in wiring record units.
The Wiring Change dialog box does not have an automatic wiring data creation
function.
Record No.
This is the record No. of the wiring file to be changed. When the record No. is changed,
the wiring data of the selected record is displayed.
To Terminal
Displays the wiring destination connection terminal in “tag name (element No.)” + “.” +
“connection terminal name, or data item name” format. The wiring destination can be
changed.
From Terminal
Displays the wiring source connection terminal in “tag name (element name)” + “.” +
“connection terminal name, or data item name” format. The wiring source can be
changed.
Wiring Type
Displays the wiring type. The wiring type can be changed.
Gain
Displays the gain for wiring between terminals wiring and simple wiring, and the upper
limit (High) of the time-series data for time-series data wiring. The gain can be changed
within the -999999.0 to 999999.0 range.

X. TEST FUNCTION
Bias
Displays the bias for wiring between terminals wiring and simple wiring, and the lower
limit (Low) of the time-series data for time-series data wiring. The bias can be
changed within the -999999.0 to 999999.0 range.
Pulse Rate
Displays the pulse rate. The pulse rate can be changed within the 1 to 99999 (Hz)
range.
Delay
Displays the dead time. The delay can be changed within the 1 to 99 (seconds)
range.
Lag
Displays the first-order lag. The lag can be changed within the 1 to 99 (seconds)
range.
Cycle
Displays the time-series data wiring cycle time. The cycle can be change within the 1
to
99999 (seconds) range.
NCP (Number of Continuous Wiring)

Specifies the number of wirings when the same wiring type is specified continuously
from the current input terminal.
For the St1DrSt1, St1RvSt1, LETOn, LETOff, TETOn, and TETOff wiring types, 1 to
32 can be specified. For the SetReset and ALTRNT wiring types, 1 to 16 can be
specified.

X. TEST FUNCTION
X7. TEST TARGET STATION OPERATION FUNCTIONS

These functions start, stop, and pause the test target FCS/FCS simulator.
FCS Start (Run)

In the virtual test mode, this function starts the FCS simulator and sets it to the
control execution state.
In the target test mode, this function starts the actual FCS and sets it to the control
execution state.
This function starts the test target FCS/FCS simulator from the stop state by reset
start and from the pause and step execution states by restart
FCS Pause (Pause)

This function switches an FCS/FCS simulator in the control execution or step
execution state to the pause state. To carry out the step execution or snapshot
save/download, the FCS/FCS simulator must be in the pause state.
Stop
This function switches an FCS/FCS simulator in the control execution, pause, or step
execution state to the stop state. Before switching to the control stop state, a
confirmation dialog box is displayed.
X8. Step Execution Function

The Step Execution function allows you to specify the number of times (1 to 100) control
is to be executed.
When Step Execution function is performed while the test target FCS/FCS simulator is in
the pause state, the test target FCS/FCS simulator executes control the specified number
of times, and then returns to the pause state. Step Execution is performed only when the
test target FCS/FCS simulator is in the pause state.
The number of step executions is changed using the Number of Step Executions Change
dialog box.
(*1)
(*1)
*1: only

X. TEST FUNCTION
X9. Breakpoint
The test function includes a function, called “breakpoint function.” that monitors operation
of the function block being tested.
A “breakpoint” is a monitoring point that is specified to monitor the operation of a function
block. When break conditions are set at a breakpoint, the FCS control function pauses
automatically when the break conditions are satisfied.
Up to eight breakpoints can be specified.
X9.1 Breakpoint Setting

To use the breakpoint function, the break conditions must be preset at the
Breakpoint Setting dialog box.
Reference button
Data of the condition 2 Data of the condition 2
Operator of the condition 2 Operator of the condition 2
X9.2 Breakpoint Setup

One or two break conditions can be set for one breakpoint. For breakpoints with two
Break conditions set, the AND of the two conditions establish the break condition.
The two break condition description formats are described below.
• Setting of One Break Condition for One Breakpoint

When condition 1 is established, the control function pauses.

X. TEST FUNCTION
• Setting Two Break Conditions for One Breakpoint

When condition 1 and condition 2 are established, the control function pauses.
When the conditions of two or more breakpoints are established, the OR of the
breakpoints causes the control function to pause.

X. TEST FUNCTION
X9.3 Breakpoint Operation and Monitoring

The Breakpoint sub-window is used to monitor the breakpoint status and to carry out
breakpoint operations.
Record No. (No)

Displays the record
numbers from 1 to 8.
Status
Displays the ON/OFF
status of each breakpoint.
X9.3.1A Breakpoint Operation

Breakpoint operation is used by the toolbar and menu bar.

X. TEST FUNCTION
X9.3.1B Breakpoint Monitoring

The Breakpoint sub-window is used for breakpoint monitoring. Record selector,
record No., status, and condition expression are displayed in the breakpoint area
of the Breakpoint sub-window. The breakpoint status is represented by display
color.

X. TEST FUNCTION
X10. One-Shot Execution Function

One-shot execution function can make a function block to run a [Block One-Shot
Execution] or to give a [Message One-Shot Output].
When block one-shot execution is performed, the specified function block is executed
once.
X10.1 Function Blocks to which One-Shot Execution may be

Applied

X. TEST FUNCTION
X10.2 Message One-Shot Output

When message one-shot output is performed, the specified message is output
from the test target FCS/FCS simulator once.

X. TEST FUNCTION
X10.2.1 One-Shot Output Messages

X. TEST FUNCTION

X. TEST FUNCTION
X11. Profiler Function

The Profile displays the test target FCS internal status (CPU load ratio, all blocks
completion times, data setting from other-station, etc.) in the Profile sub-window.
It can also output the data displayed in the window to a Comma Separated Value (CSV)
format file.
The following can be monitored by using the Profiler function:
• CPU Load
Monitors the proportion of one second that function blocks, SEBOL and system basic
functions occupy the CPU and displays the result on a graph as the moving average
CPU load ratio of 60 samples.
This function is used only for target testing.
The values displayed in virtual testing are meaningless.
• All Blocks Completion Times

Monitors the number of times all the function blocks of the FCS completed processing
in one basic cycle in 60 basic scans and displays the monitored result on a graph as
number of control function execution counts.
This function is used only for target testing.
The values displayed in virtual testing are meaningless.
• Function Block Profile Data

Monitors the data of the function block specified as the profile point, and displays the
station name, set data value, and time whenever another station accesses the data.
The tag name and data item name of up to four profile points can be specified.
• Log File Information Display

Displays the name and size of the profile file storing the CPU load ratio, number of all
function block completed processing, and the function block profile data, log
execution status, and log data items. One log file can hold the data of up to 3600
points.
• Profile Data Write

Stores the contents currently displayed in the profile sub-window to HIS hard disk in
CSV file format. The CPU Load display, All Blocks Completion Times display, and
Function Block Profile Data display data can be written.

X. TEST FUNCTION
X11.1 CPU Load Display

When the CPU load display mode is selected, the Profile sub-window displays the
CPU load ratio on a graph.
The Profiler function can store the CPU load ratio data to HIS disk as a log file for
display later. It can also output the data displayed in the current window to a CSV
format file.
Section for Graph

Data source display color and
data name

X. TEST FUNCTION
Display Refresh Cycle

There are two types of display refresh cycles: manual refresh and periodic refresh.
Select one of them.
When you selected periodic refresh, you can specify the display refresh cycle in 1 to
100 second intervals. The default is periodic refresh (pitch: 1 second).
Specify the display refresh cycle using the CPU Load Option dialog box.
X11.2 All Blocks Completion Times

When All Blocks Completion Times mode is selected, the Profiler window displays all
blocks completion times on a graph.
The Profiler function can store all blocks completion times data to HIS disk as a log
file for display later. It can also output the data displayed in the current window to a
CSV format file.
Section for Graph

Data source display color and
data name

X. TEST FUNCTION

There are two types of display refresh cycles: manual refresh and periodic refresh.
Select one of them.
When you selected periodic refresh, you can specify the display refresh cycle in 1 to
100 second intervals. The default is periodic refresh (pitch: 1 second).
X11.3 Function Blocks Profile Data Display

When the function block profile data display mode is selected, the Profile window
displays the function block data in a list.
The Profiler function can store the function block to HIS disk as a log file for display
later. It can also output the data displayed in the current window to a CSV format.
Function Block Profile Data

The client area can display up to 1000 lines of function block profile data. A colored is
displayed at the head of each data to discriminate the profile points. The profile data
is sequentially displayed from top to bottom, starting from the oldest data. When the
profile data exceeds 1000 lines, it is sequentially deleted, starting from the oldest
data.

X. TEST FUNCTION
Profile Points
The profile point display area in the client area can be selected one line at a time.
Double clicking on the selected profile point calls the Profile Point Setup dialog box.
One line is always selected at the profile point display area. The profile point selected
here can be deleted. Deleting a profile point deletes all its related data from the
window.

There are two types of display refresh: manual refresh and periodic refresh. Select
one of
them. When you selected periodic refresh, you can also specify the display refresh
internal
in an interval of 1 to 100 seconds. The default is periodic refresh (interval: 1 second).
Specify the display refresh cycle using the Function Block Profile Option dialog box.

X. TEST FUNCTION
X12. I/O ERROR TEST

An I/O error state such as IOP can be forcibly generated by writing the data status from
HIS to the function block connected via the process I/O.
Data status can be set in the Set Data dialog box.

Data status can be set only for the test target FCS/FCS simulator.
Data items other than data status can also be set in this dialog box.
Data Statuses that can be Set and Names of Data Items to be Specified
Six types of data statuses can be changed in the Set Data dialog box: BAD, NRDY,
PFAL, LPFL, IOP+, and IOP-.
Data items to be specified vary with the type of a function block or an element for which
the data status is to be changed. Specify the data items as follows:
• Specify RAW for a function block connected to the process I/O or the
communication I/O (%WW).
• Specify PV in the case of %WB (communication I/O bit data).
• Specify PV in the case of %Z defined as a contact input (DI) or a contact output

(DO).
• Specify PV in the case of %GS (global switch). only

X. TEST FUNCTION

Amb Training Yokogawa PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amb Training Yokogawa PDF

Uploaded by

Copyright:

Available Formats

TRAINING CENTRE

STUDENT TRAINING TEXTBOOK

Document No: CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

NAME OF COURSE MATERIAL USED : CS 1000 & CS 3000 ENGINEERING (Vnet/IP)

Edition Date Revised Item Rev. No.* Author

Note: Instruction Manual is updated/controlled by YHQ.

WELCOME TO YOKOGAWA TRAINING CENTRE

Tea break : 1000 – 1015

Lunch : 1130 – 1245

General Rules & Regulation

YOKOGAWA SINGAPORE TRAINING CENTRE

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

YOKOGAWA SINGAPORE TRAINING CENTRE

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

PARTICIPANTS : For engineers involved in software generation or modification

PREREQUISITE : Participants should have attended CENTUM CS 1000/3000

YOKOGAWA SINGAPORE TRAINING CENTRE

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

YOKOGAWA SINGAPORE TRAINING CENTRE

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

YOKOGAWA SINGAPORE TRAINING CENTRE Page 1 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

D. PROJECT COMMON ITEMS D1

E1. FIO SYSTEM OVERVIEW E1-1

E2. FIO SYSTEM OVERVIEW (Vnet/IP) E2-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 2 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

F1. LFCS CONFIGURATION F1-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 3 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

F2. KFCS CONFIGURATION F2-1

F3. Field Control Unit for FIO (Rack Mountable) F3-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 4 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

F4. Field Control Unit for Vnet/IP for FIO F4-1

G1. INPUT/OUTPUT FUNCTIONS(LFCS) G1-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 5 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

G1.4.9 Cold Junction Compensation G1-16

G2. INPUT/OUTPUT FUNCTIONS (KFCS) G2-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 6 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

G2.4.5 Pulse Input G2-20

G3. INPUT/OUTPUT FUNCTIONS (FFCS) G3-1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 7 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

H. SOFTWARE INPUT/OUTPUT FUNCTIONS H1

I. CONTROL DRAWING BUILDER I1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 8 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

J. REGULATORY CONTROL FUNCTION J1

K. SEQUENCE CONTROL FUNCTION K1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 9 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

YOKOGAWA SINGAPORE TRAINING CENTRE Page 10 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

P. SEQUENCE MESSAGE REQUEST P1

R. TREND ACQUISITION PEN ASSIGNMENT R1

S. HIS WINDOW CREATION S1

YOKOGAWA SINGAPORE TRAINING CENTRE Page 11 of 15

CKEG_R3_Vnet/IP_TB Ed. 3 September 2007

T. CONTROL GROUP WINDOW DEFINITION T1

U. OVERVIEW WINDOW DEFINITION U