Im32q56h20 31e PDF

User's
Manual
Integration with FAST/
TOOLS
IM 32Q56H20-31E
IM 32Q56H20-31E
4th Edition
i
Introduction
ProSafe-RS can be integrated with FAST/TOOLS, a Yokogawa SCADA system. When Pro-
Safe-RS is integrated with FAST/TOOLS, the SCSs of ProSafe-RS system can be accessed
by FAST/TOOLS through Vnet/IP-Upstream network.
This document describes FAST/TOOLS Integration. When you perform engineering works
and maintenance works for FAST/TOOLS Integration, you should fully understand Part-C in
this document.
Regarding the engineering details of FAST/TOOLS, please refer to the User's Manual of
FAST/TOOLS.
For engineering works in a non-integrated environment or engineering works for CENTUM in-
tegrated system, read ProSafe-RS Vnet/IP (IM 32Q56H10-31E).
Note that the term "Vnet/IP" that has been traditionally used in FAST/TOOLS Integration is
described as "Vnet/IP-Upstream" in R3.02.10 and later. When you refer to ProSafe-RS IM
other than this document, replace the network name "Vnet/ IP with "Vnet/IP-Upstream."
In this document, the system whose type of safety control unit connected to Vnet/IP-Upstream
in FAST/TOOLS Integration is only SSC57 is called "Upstream system." Also, the station con-
nected to Vnet/IP-Upstream and equipped with a Vnet/IP device is called "Vnet/IP station."
This document abbreviates "function block" as "FB" in order to reduce the number of charac-
ters displayed in tables and figures.
This document consists of the following chapters:
• Part A Functions of FAST/TOOLS Integration
This chapter describes the network configuration and system configuration of FAST/
TOOLS Integration and the shared items between FAST/TOOLS Integration and Up-
stream system functions. In addition, a FAST/TOOLS Integration network can operate in
Standard mode, Wide-area mode and Narrowband mode. This chapter describes the
specifications of each network mode, too.
• Part B Functions of Upstream system
This chapter describes the functions and hardware of Upstream system. The functions of
Upstream system include Data buffering function and AGA Gas flow rate calculation func-
tion.
• Part C Engineering and maintenance works
This chapter describes the engineering works for FAST/TOOLS Integration system. It ex-
plains how to operate Domain Properties Setting Tool, how to access the data of the SCS
application logic's variables and function block from FAST/TOOLS, and how to define a
Narrowband mode group. It also introduces specific system maintenance methods.
• Appendix
This chapter describes the function blocks, mapping blocks, and mapping elements of
Upstream system.
Media No. IM 32Q56H20-31E (CD) 4th Edition : Jan. 2015 (YK) IM 32Q56H20-31E 4th Edition : Jan.30,2015-00
All Rights Reserved Copyright © 2011 , Yokogawa Electric Corporation
ii
Safety Precautions for Use

n Safety, Protection, and Modification of the Product
• To protect the system controlled by the Product and the Product itself and to ensure safe
operation, please observe the safety precautions described in this Manual. Yokogawa
Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe
the safety precautions and instructions when operating the Product.
• If the Product is used in a manner not specified in the User's Manuals, the protection pro-
vided by the Product may be impaired.
• If any protection or safety circuit is required for the system controlled by the Product or for
the Product itself, please install it externally.
• Use only spare parts that are approved by YOKOGAWA when replacing parts or consum-
ables of the Product.
• Do not use the Product and its accessories such as power cords on devices that are not
approved by YOKOGAWA. Do not use the Product and its accessories for any purpose
other than those intended by YOKOGAWA.
• Modification of the Product is strictly prohibited.
• The following symbols are used in the Product and User's Manuals to indicate the accom-
panying safety precautions:
Indicates that caution is required for operation. This symbol is labeled on the Prod-
uct to refer the user to the User's Manuals for necessary actions or behaviors in
order to protect the operator and the equipment against dangers such as electric
shock. In the User's Manuals, you will find the precautions necessary to prevent
physical injury or death, which may be caused by accidents, such as electric
shock resulting from operational mistakes.
Identifies a protective conductor terminal. Before using the Product, you must
ground the protective conductor terminal to avoid electric shock.
Identifies a functional grounding terminal. A terminal marked "FG" also has the
same function. This terminal is used for grounding other than protective grounding.
Before using the Product, you must ground this terminal.
Indicates an AC supply.
Indicates a DC supply.
Indicates the ON position of a power on/off switch.
Indicates the OFF position of a power on/off switch.
n Notes on Handling User's Manuals

• Hand over the User's Manuals to your end users so that they can keep the User's Man-
uals on hand for convenient reference.
• Thoroughly read and understand the information in the User's Manuals before using the
Product.
• For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that the
Product is suitable for any particular purpose but to describe the functional details of the
Product.
• Contents of the User's Manuals are subject to change without notice.
IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

iii
• Every effort has been made to ensure the accuracy of contents in the User's Manuals.
However, should you have any questions or find any errors, contact us or your local dis-
tributor. The User's Manuals with unordered or missing pages will be replaced.
n Warning and Disclaimer

• Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for
the Product.
• YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either
using or not being able to use the Product.
n Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the Soft-
ware Product's merchantability or suitability for any particular purpose, except as speci-
fied in the warranty terms.
• Purchase the appropriate number of licenses of the Software Product according to the
number of computers to be used.
• No copy of the Software Product may be made for any purpose other than backup; other-
wise, it is deemed as an infringement of YOKOGAWA's Intellectual Property rights.
• Keep the software medium of the Software Product in a safe place.
• No reverse engineering, reverse compiling, reverse assembling, or converting the Soft-
ware Product to human-readable format may be performed for the Software Product.
• No part of the Software Product may be transferred, converted, or sublet for use by any
third-party, without prior written consent from YOKOGAWA.
n Notes on Hardware
l Appearance and Accessories
Check the following items when you receive the Product:
• Appearance
• Standard accessories
Contact us or your local distributor in the following cases:
• The Product coating is peeling off.
• The Product itself is damaged.
• Any accessories are missing.
If the following label turns dirty and the information on it becomes illegible, or if the label is
peeling off, order a new one with the part number T9029BX to replace it.
: Label attached to the Products such as the power supply module.
l Model and Suffix Codes

The name plate on the Product contains the model and suffix codes. Verify the model and suf-
fix codes with those in the General Specifications (GS) to ensure that the Product matches
the order specifications. Should you have any questions, contact us or your local distributor.

iv
Documentation Conventions
n Symbols
The following symbols are used in the User's Manuals.
Identifies instructions that must be observed to avoid physical
injury, electric shock, or death.
Identifies instructions that must be observed to prevent damage

to the software or hardware, or system failures of the Product.
Identifies important information required to understand opera-

tions or functions.
Identifies additional information.
Identifies referenced content.

In online manuals, you can view the referenced content by click-
ing the links that are in green text. However, this action does not
apply to the links that are in black text.
n Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
l Commonly Used Conventions throughout the User's Manuals

• Δ Mark
Indicates that a space must be entered between character strings.
Example:
.ALΔPIC010Δ-SC
• Character string enclosed by braces { }
Indicates character strings that may be omitted.
Example:
.PRΔTAG{Δ.sheet name}
l Conventions Used to Show Key or Button Operations

• Characters enclosed by brackets [ ]
When characters are enclosed by brackets in the description of a key or button operation,
it indicates a key on the keyboard, a button name in a window, or an item in a list box
displayed in a window.
Example:
To alter the function, press the [ESC] key.
l Conventions of a User-defined Folder

• User-defined folder name enclosed by parenthesis ( )
User definable path is written in a pair of parentheses.
Example:
(RS Project Folder)\SCS0101

v
If the RS Project Folder is C:\MYRSPJT, the above path becomes C:
\MYRSPJTSCS0101.
n Drawing Conventions
Drawings used in the User's Manuals may be partially emphasized, simplified, or omitted for
the convenience of description.
Drawings of windows may be slightly different from the actual screenshots with different set-
tings or fonts. The difference does not hamper the understanding of basic functionalities and
operation and monitoring tasks.
n Integration with CENTUM

The Product can be integrated with CENTUM VP or CENTUM CS 3000. In the User's Man-
uals, the integration with CENTUM VP or CENTUM CS 3000 is referred to as "Integration with
CENTUM."
In the User's Manuals, the explanations for integrating the Product with CENTUM VP or
CENTUM CS 3000, the glossary for various features of CENTUM VP is used instead of the
glossary for CENTUM CS 3000. For example, the term "CENTUM VP System Alarm View" is
used instead of "CENTUM CS 3000 System Alarm window." Nevertheless, if the features for
integrating the Product with CENTUM VP and CENTUM CS 3000 are different, both features
will be explained separately.
SEE
ALSO For more information about the functions and usage of CENTUM VP components for integrating the Product
with CENTUM VP, refer to:
User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM VP
For more information about the features and usage of CENTUM CS 3000 components for integrating the
Product with CENTUM CS 3000, refer to:
User's Manuals (IM), Technical Information (TI), and General Specifications (GS) of CENTUM CS 3000
n Explanation of Hardware and Software Behaviors in the User's

Manuals
In the User's Manuals, system behaviors are explained assuming that the latest versions of
YOKOGAWA software and hardware at the time of publication of the User's Manuals are in-
stalled.
If additional precise information about the safety of legacy versions of software or hardware is
required, a link to the corresponding explanation is provided. Please refer to the information
according to your system.
n Station Types
A safety control station (hereafter referred to as SCS) is named according to the type of the
safety control unit used in it.
Table Info-1 Names of SCS and Safety Control Unit Used

Name of SCS Model of the safety control unit
SCSV1-S SSC10S/SSC10D
SCSP1-S SSC50S/SSC50D
SCSP2-S SSC60S/SSC60D
SCSU1-S SSC57S/SSC57D
In the User's Manuals, the following abbreviations may be used to describe functions of these
SCS as a whole.

vi
• SCSV1: Abbreviation of SCSV1-S
• SCSP1: Abbreviation of SCSP1-S
• SCSP2: Abbreviation of SCSP2-S
• SCSU1: Abbreviation of SCSU1-S

vii
Conformity Standards and Cautions

n Conformity Standards
The Product conforms to various standards.
SEE
ALSO For more information about the standards that the Product conforms to, refer to:
General Specifications (GS) for the Product
l Standards
The standards that the Product conforms to are described in the following table:
Table Info-2 Standards

Category Standard
Functional safety standards IEC 61508
(*1) (*2)
Programmable controllers (*1) IEC 61131-2
(*2)
Safety Standards (*2) (*3) (*4) [CSA]
• CAN/CSA-C22.2 No.61010-1 [100-120 V AC power supply]
[CE Marking] Low Voltage Directive
• EN 61010-1 [100-120 V AC (*5), 220-240 V AC, and 24 V DC power
supply]
[EAC Marking] (*6)
• CU TR 004
EMC Standards (*2) [CE Marking] EMC Directive
• EN 55011 Class A Group 1[100-120 V AC (*5), 220-240 V AC, and 24 V
DC power supply] (*7)
• EN 61000-6-2[100-120 V AC (*5), 220-240 V AC, and 24 V DC power
supply] (*8)
• EN 61000-3-2 [220-240 V AC power supply] (*9)
• EN 61000-3-3 [220-240 V AC power supply]
[RCM]
• EN 55011 Class A Group 1 [220-240 V AC and 24 V DC power supply]
(*7)
[KC Marking]
• Korea Electromagnetic Conformity Standard [100-120 V AC (*10),
220-240 V AC, and 24 V DC power supply]
[EAC Marking] (*6)
• CU TR 020
*1: Safety control stations comply with this standard.

*2: The devices must be installed in a metal cabinet with lock and key to meet the safety standards and EMC Standards.
*3: To ensure that all the hardware devices satisfy the safety standards, the dedicated breakers conforming to the following spec-
ifications must be installed in the power supply distribution board:
• [CSA] CSA C22.2 No.5 or UL 489
• [CE Marking] EN 60947-1 and EN 60947-3
*4: The Product must be grounded to a protective grounding system that is suitable for the power distribution system or must
conform to the safety standards of the country or region where the Product is used.
*5: SSC10S/SSC10D (100-120 V AC power supply) are excluded from CE Marking conformity.
*6: The EAC mark is as follows:
*7: Class A hardware devices are designed for use in an industrial environment.
*8: Regarding surge immunity, a lightning arrester or an equivalent equipment must be installed.
*9: Regarding the requirements on the limits for harmonic current emissions, the active filter circuitry or an external power supply
unit with proper harmonic filters should be used.
*10: SSC10S/SSC10D (100-120 V AC power supply) are excluded from KC Marking conformity.
In relation to the CE Marking, the manufacturer and the authorised representative for Pro-
Safe-RS in the EEA are indicated below:
• Manufacturer:

viii
YOKOGAWA Electric Corporation (2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, Ja-
pan)
• Authorised representative in the EEA:
Yokogawa Europe B.V. (Euroweg 2, 3825 HD Amersfoort, The Netherlands)
SEE
ALSO For more information about selecting a power supply unit that enables safe usage of the Product, refer to:
“n Guidelines for Selecting a Power Supply Unit” on page xii
For more information about selecting and wiring power cables, refer to:
ProSafe-RS Installation Guidance (TI 32S01J10-01E)
n Installation and Maintenance Notes

l Installation Method
Observe the following guidelines to ensure that devices meet safety and performance require-
ments:
• Install rack-mountable devices in a lockable metal cabinet to meet their respective stand-
ards.
• If devices are housed in a cabinet, keep the cabinet door closed during operation.
• Ensure that all the empty slots of the devices are covered with the covers provided. Place
an order for the required covers.
• Ensure that all cables are firmly fixed with cable ties.
• Prepare a dedicated breaker in the same room as the system so that it can shut off the
power supply when an abnormality occurs. Use this breaker to turn off the power supply
for the devices of the system when a device abnormality occurs.
SEE
ALSO For more information about installation method, refer to:
l Requirements for Installation

When installing a device, the requirements for the device should be satisfied.
In addition, to satisfy safety standards, the device should be installed under the following con-
ditions:
Installation height: Altitude of up to 2000 m
Installation category based on IEC 61010-1: II (*1)
Pollution degree based on IEC 61010-1: 2 (*2)
*1: The installation category, also referred to as an overvoltage category, defines the standard for impulse withstand voltage. Cat-
egory II applies to the electrical device that is directly connected to the lower-voltage power supply.
*2: Pollution degree indicates the adhesion level of foreign matter in a solid, liquid, or gaseous state that can reduce dielectric
strength. Degree 2 refers to a pollution level equivalent to the general indoor environment.
SEE
ALSO For more information about installation specifications, refer to:
l Measurement Categories
The specifications for measurement inputs of devices are as follows.

ix
Devices included in the Product belong to the measurement categories of No.1, which are
shown in the following table. The rated transient overvoltage of the measurement categories
of No.1 is 1500 V.
WARNING
Devices included in the Product belong to the measurement categories of No.1, which are
shown in the following table. Do not use the devices for measurements that belong to the
measurement categories of No.2, No.3, and No.4.
The following table describes the standard numbers and measurement categories.
Table Info-3 Standard Numbers and Measurement Categories

Standard number
No. IEC/EN/CSA EN 61010-2-030 Description
61010-1:2001
No.1 Measurement category I O (Other) Measurements performed on circuits not di-
rectly connected to MAINS.
No.2 Measurement category II Measurement category II Measurements performed on circuits direct-
ly connected to the low-voltage installation.
No.3 Measurement category III Measurement category III Measurements performed in a building in-
stallation.
No.4 Measurement category IV Measurement category IV Measurements performed at the source of
the low-voltage installation.
l Tightening Torque of Screws
CAUTION
The recommended tightening torque for the Product is shown in the following table. However,
if the tightening torque of the screw is specified in the User's Manuals, follow the instructions
described in the User's Manuals.
Table Info-4 Recommended Tightening Torque

Nominal diameter of a screw M2.6 M3 M3.5 M4 M5 M6 M8 M10
Recommended tightening tor- 0.35 0.6 0.8 1.2 2.8 3.0 12.0 24.0
que (N·m)
SEE
ALSO For more information about each nominal diameter of a screw, refer to:

x
l Power Cable Wiring
CAUTION
Connect the power cables according to the procedure specified in the User’s Manuals of the
device.
Power cables must conform to the safety standards of the country where the device is instal-
led.
SEE
ALSO For more information about power cables wiring, refer to:
• ProSafe-RS Installation Guidance (TI 32S01J10-01E)
• User's Manuals of each device
l Grounding
CAUTION
The Product requires the protective grounding defined by the safety standards.
You must ground the Product according to the procedure specified in the User's Manuals to
prevent electric shock and to minimize the effect of noise.
SEE
ALSO For more information about grounding, refer to:
l I/O Cable Wiring
CAUTION
Wire I/O cables according to the procedure specified in the User’s Manuals.
SEE
ALSO For more information about I/O cables wiring, refer to:

xi
l Connected Devices
CAUTION
To ensure CSA standard conformity for the entire system of the Product, all the devices con-
nected to the system of the Product should conform to CSA standards.
l Maintenance
CAUTION
• The Product maintenance should be performed only by personnel who have undergone
specialized training.
• When a device turns dirty, use a vacuum cleaner or a soft dry cloth to clean it.
• During maintenance, wear a wrist strap and follow Electrostatic Discharge (ESD) precau-
tions.
• If any existing caution label is peeling off, or is dirty and illegible, order a new one with the
part number T9029BX to replace it.
SEE
ALSO For more information about maintenance, refer to:
l Modules, Cards, Cables, and Connectors
CAUTION
When the power is on, only modules, cards, cables, and connectors that are allowed in the
User's Manuals can be replaced, removed, or installed.
SEE
ALSO For more information about replacing, and removing or installing modules, cards, cables, and connectors, re-
fer to:

xii
l Batteries
CAUTION
• You must use only YOKOGAWA-designated batteries.
• When mounting or replacing batteries, you must follow the procedure specified in the Us-
er's Manuals of the device.
• When replacing batteries while the power supply is on, do not put your hands inside the
device to prevent electric shock.
SEE
ALSO For more information about batteries, refer to:
l Fuses
CAUTION
• Use only YOKOGAWA-designated fuses for replacement.
• Turn off the power supply before replacing the fuses.
SEE
ALSO For more information about fuses, refer to:
l Fan Unit
CAUTION
When replacing the fan unit while the power supply is on, do not put your hands inside the
device to prevent electric shock.
SEE
ALSO For more information about fan unit, refer to:
n Guidelines for Selecting a Power Supply Unit

Regarding the system of the Product, you must take note of the following precautions by us-
ing a power supply unit to satisfy the various requirements of the EMC regulations:

xiii
• Prevent power supply problems such as power failure or short interruptions.
• Protect the power supply unit against power line noise and lightning surge.
• Suppress power supply harmonic current from devices.
You must consult with the power supply unit suppliers, and then select and install a suitable
power supply unit with the considerations described in the following sections.
l Notices on Deciding the Output Capacity of Power Supply Unit

Consult with the power supply unit suppliers and decide a suitable output capacity of the pow-
er supply unit with the following considerations:
• Power consumption
Power consumed in both volt-ampere (VA) and watt (W).
• Device crest factor
Ratio of the peak value to the effective value of input current supplied to each device.
• Device inrush current
The maximum inrush current when power is turned on.
• Power failure backup time
Time required to back up the devices when power fails.
• Reserve capacity
An extra power capacity for additional devices and so on.
SEE
ALSO For more information about power consumption (VA/W) and inrush current, refer to:
l Crest Factor
The crest factor refers to the ratio of the peak value to the effective value of any input current
of a device.
Input voltage waveform
Input current waveform Approximately 5 ms

Peak value
Effective value
Peak value
Crest factor =
Effective value
Figure Info-1 Input voltage and current waveforms
Crest Factor=Peak value of the current supplied to the device / Effective value of the current
When selecting a power supply unit, you need to estimate the power supply output capacity,
based on the crest factor of the input current supplied to every connected device. Estimate
the device crest factors by using the following approximate values when selecting a power
supply unit:
• 100 V system: Crest factor about 3

xiv
• 220 V system: Crest factor about 6
l How to Decide the Power Supply Unit

The commonly used methods for determining the power supply unit capacity with considera-
tion of the crest factor are shown below. Note that the power supply unit capacity should be
finally decided after consulting with the power supply unit supplier:
• If the power unit crest factor is larger than the device crest factor, the power unit can be
used to its full rated capacity. However, factors such as device inrush current, backup
time, and reserve capacity must be taken into consideration separately.
• If the power unit crest factor is smaller than the device crest factor, the power unit capaci-
ty must be calculated using the following formula. Factors such as device inrush current,
backup time, and reserve capacity must be taken into consideration separately.
Power unit output capacity = Total device power consumption × Capacity coeff
icient
Capacity coefficient = Device crest factor/Power unit crest factor
l Inrush Current
When a device is turned on, the large inrush current flows in because of the momentary
charging current for capacitors. Therefore, the minimum requirement is that the inrush current
produced by turning on some devices should not cause any voltage fluctuations that may af-
fect other devices. For turning on all devices together, a soft start or switching to uninterrupti-
ble backup power should be required.
When the power is turned on, the inrush current can trip the overload protector, and then may
switch to the backup power or commercial power supply. You should select a power supply
unit that can automatically and seamlessly recover the normal power supply when overload-
ing ends.
l Suppressing Harmonic Current

To suppress the power supply harmonic current that flows to a low-voltage distribution sys-
tem, a power supply unit or an active filter as described below should be installed between a
device and the low-voltage distribution system:
• A power supply unit that can suppress the power supply harmonic current, such as a high
power factor inverter-type uninterruptible power unit
• An active filter unit for suppressing the power supply harmonic current
For Europe, you must select a power supply unit that can meet the requirements on the limits
for harmonic current emissions of the EMC Directives.
Aside from determining the output capacity of the power supply unit, you should also deter-
mine the capacity of the harmonic current suppressing unit after consultation with the supplier
of your power supply unit.

xv
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the software medium of the
Software Product shall remain with YOKOGAWA.
You are allowed to print the required pages of the online manuals for the purposes of using or
operating the Product; however, reprinting or reproducing the entire document is strictly pro-
hibited by the Copyright Law.
Except as stated above, no part of the online manuals may be reproduced, transferred, sold,
or distributed to a third party in any manner (either in electronic or written form including, with-
out limitation, in the forms of paper documents, electronic media, and transmission via the
network). Nor it may be registered or recorded in the media such as films without permission.
n Trademark Acknowledgments
• CENTUM, ProSafe, Vnet/IP, and STARDOM are registered trademarks of YOKOGAWA.
• Microsoft, Windows, Windows Vista, Windows Server, Visual Basic, Visual C++, and Vis-
ual Studio are either registered trademarks or trademarks of Microsoft Corporation in the
United States and other countries.
• Adobe, Acrobat, and Adobe Reader are registered trademarks of Adobe Systems Incor-
porated.
• Ethernet is a registered trademark of Xerox Corporation.
• HART is a registered trademark of the HART Communication Foundation.
• Modicon and Modbus are registered trademarks of Schneider Electric SA.
• All other company and product names mentioned in the User's Manuals are trademarks
or registered trademarks of their respective companies.
• TM or ® mark are not used to indicate trademarks or registered trademarks in the User's
Manuals.
• Logos and logo marks are not used in the User's Manuals.

TocA-1
Integration with FAST/TOOLS
IM 32Q56H20-31E 4th Edition
CONTENTS
PART-A Integration with FAST/TOOLS function...............
...........................................................................A-1
A1. FAST/TOOLS Integration configuration........................................... A1-1
A1.1 Outlines of FAST/TOOLS integrated system........................................... A1-2
A1.2 Overview of a Vnet/IP-Upstream network................................................ A1-8
A1.3 Time synchronization of FAST/TOOLS Integration.................................A1-9
A1.4 Vnet/IP-Upstream bus status.................................................................. A1-14
A2. Vnet/IP-Upstream Standard/Wide-area modes................................A2-1
A2.1 Network configuration in Standard and Wide-area modes.................... A2-2
A2.2 Network connection in Standard and Wide-area modes........................A2-3
A2.2.1 Connect devices included in Vnet/IP-Upstream domain..............A2-4
A2.2.2 Connection between Vnet/IP-Upstream domains........................ A2-6
A2.3 Outline of station setup............................................................................. A2-7
A3. Vnet/IP-Upstream Narrowband mode.............................................. A3-1
A3.1 Network configuration in Narrowband mode.......................................... A3-2
A3.2 Functions and configuration of Vnet/IP-Upstream in Narrowband mode....
..................................................................................................................... A3-3

TocB-1
CONTENTS
PART-B Functions of Upstream systems.................... B-1
B1. Data buffering function..................................................................... B1-1
B1.1 Details of the data buffering function...................................................... B1-2
B1.2 Engineering for data buffering..................................................................B1-3
B2. Gas flow rate calculation function................................................... B2-1
B2.1 Functional configuration of the Gas flow rate calculation function.............
..................................................................................................................... B2-2
B2.2 Function blocks used for gas flow rate calculation function................ B2-6
B2.2.1 Outline of function of gas flow rate calculation function block.............
..................................................................................................... B2-7
B2.2.2 Outline of function of report data creation function block.............B2-9
B2.2.3 Function blocks that use data retaining function........................B2-12
B2.3 Structures, mapping blocks, and mapping elements of function blocks
for gas flow rate calculation function.................................................... B2-14
B2.3.1 Structures that are used by gas flow rate calculation function block...
................................................................................................... B2-15
B2.3.2 Mapping blocks and mapping elements for gas flow rate calculation
function...................................................................................... B2-16
B3. Hardware of SCS for Upstream system........................................... B3-1
B3.1 Configuration and name of the hardware................................................ B3-2
B3.1.1 Configuration of Safety Control Unit............................................ B3-3
B3.1.2 Configuration of devices connected to the Safety Control Unit...........
..................................................................................................... B3-6
B3.2 Installing Devices.......................................................................................B3-7
B3.3 Cable Connection.......................................................................................B3-8
B3.4 Function of the units..................................................................................B3-9
B3.5 Signal Cable Connection to Input/Output Modules.............................. B3-10
B3.6 Control bus interface card.......................................................................B3-11
B3.7 Maintenance of ProSafe-RS Hardware...................................................B3-12
B3.8 Relay Board.............................................................................................. B3-13
CMPL 32Q06D25-31E (SSC57S, SSC57D).......................................CMPL B1-1

TocC-1
CONTENTS
PART-C Engineering and maintenance....................... C-1
C1. Workflow for engineering of a FAST/TOOLS Integration system..........
............................................................................................................. C1-1
C1.1 SCS Engineering works for FAST/TOOLS Integration............................C1-2
C1.2 Notes on engineering works..................................................................... C1-3
C1.3 Testing in a FAST/TOOLS integrated environment................................. C1-5
C2. Domain Properties Setting Tool........................................................C2-1
C2.1 Starting and exiting the tool......................................................................C2-2
C2.2 Setting domain properties.........................................................................C2-5
C2.3 Downloading domain properties.............................................................. C2-8
C2.4 Obtaining actual domain property settings.............................................C2-9
C3. Defining narrowband groups............................................................C3-1
C3.1 Narrowband mode settings and precautions for narrowband group
definition..................................................................................................... C3-2
C3.2 Display and operation of the Narrowband Group Definition window...........
..................................................................................................................... C3-3
C3.3 Editing SCSs that belong to a narrowband group.................................. C3-7
C3.4 Setting the number of SCSs that can communicate...............................C3-8
C3.5 Quick reference table of the settings in the Narrowband Group Definition
window........................................................................................................ C3-9
C3.6 Setting start and stop of data acquisition............................................. C3-10
C3.7 Procedure for offline download in the Narrowband mode...................C3-12
C3.8 Collecting data from SCSs in a narrowband system in the same way as in
the Standard and Wide-area modes....................................................... C3-13
C4. Defining tag names............................................................................C4-1
C4.1 Overview of tag name definition...............................................................C4-2
C4.2 Definition of the tag name at the gas flow rate calculation..................C4-11
C5. Maintenance of FAST/TOOLS integrated system (environment)..........
............................................................................................................. C5-1
C5.1 Maintenance in Vnet/IP-Upstream network............................................. C5-2
C5.2 Procedures and precautions for adding a station or domain................C5-3

TocApp.-1
CONTENTS
Appendix
Appendix 1. Function blocks for Upstream systems........................App.1-1
Appendix 1.1 Function blocks for data buffering function.............................App.1-2
Appendix 1.1.1 BUF_DIF_B (buffering when BOOL-type data changes)............
....................................................................................... App.1-3
Appendix 1.1.2 BUF_DIF_I (buffering when INTEGER-type data changes).......
....................................................................................... App.1-5
Appendix 1.1.3 BUF_DIF_R (buffering when REAL-type data changes)............
....................................................................................... App.1-7
Appendix 1.1.4 BUF_TIM_I (periodic buffering of INTEGER-type data)..............
....................................................................................... App.1-9
Appendix 1.1.5 BUF_TIM_R (periodic buffering of REAL-type data)...................
......................................................................................App.1-11
Appendix 1.1.6 BUF_TRIG_B (buffering BOOL-type data on trigger detection)..
..................................................................................... App.1-13
Appendix 1.1.7 BUF_TRIG_I (buffering INTEGER-type data on trigger
detection)......................................................................App.1-15
Appendix 1.1.8 BUF_TRIG_R (buffering REAL-type data on trigger detection)..
..................................................................................... App.1-17
Appendix 1.2 Function blocks for gas flow rate calculation function.........App.1-19
Appendix 1.2.1 AGA_3 (AGA3 calculation)...........................................App.1-21
Appendix 1.2.2 AGA_7 (AGA7 calculation)...........................................App.1-29
Appendix 1.2.3 AGA_R (Report data creation)..................................... App.1-35
Appendix 1.2.4 ECWR_B (external communication with BOOL-type Data
retaining function).........................................................App.1-41
Appendix 1.2.5 ECWR_I (External communication with INTEGER-type data
Appendix 1.2.6 ECWR_R (External communication with REAL-type data
Appendix 1.2.7 ACCUM (Accumulation)............................................... App.1-44
Appendix 1.2.8 Error code.....................................................................App.1-47
Appendix 2. Structure of function blocks of gas flow rate calculation
function............................................................................App.2-1
Appendix 3. Mapping blocks and mapping elements for FAST/TOOLS
Integration....................................................................... App.3-1

<A. Integration with FAST/TOOLS function> A-1
A. Integration with FAST/TOOLS

function
In a system integrated with FAST/TOOLS, ProSafe-RS SCSs can be accessed from FAST/
TOOLS via Vnet/IP-Upstream network.
A network with FAST/TOOLS Integration function works in the Standard, Wide-area, or Nar-
rowband mode. Specifications, including the network mode and network configuration depend
on the type of the Safety Control Unit in SCS that is connected to the Vnet/IP-Upstream net-
work.
FAST/TOOLS Integration function includes functions that are common in all network modes,
and functions for the Narrowband mode only.
Functions including the gas flow rate calculation and the data buffering are available in
SCSU1 as well as the conventional FAST/TOOLS Integration function.

<A1. FAST/TOOLS Integration configuration> A1-1
A1. FAST/TOOLS Integration

configuration
The SCSs that can be used for FAST/TOOLS integration are SCSP1, SCSP2, and SCSU1.
FAST/TOOLS Integration network using SCSP1 and SCSP2 can be set to Standard mode
and Wide-area mode.
FAST/TOOLS Integration network using SCSU1 can be set to Standard mode, Wide-area
mode and Narrowband mode. Narrowband mode has limits on the number of windows that
can be displayed and the number of SCSs that can be connected.
n Notes on integration with FAST/TOOLS

Precautions for FAST/TOOLS Integration are as follows:
IMPORTANT
• Install FAST/TOOLS and SENG in different computers.
• You cannot grant licenses for both CENTUM VP/CS 3000 Integration Engineering Pack-
age and FAST/TOOLS Integration Engineering Package to the same computer.
• Do not install CENTUM software in computers that use FAST/TOOLS Integration Engi-
neering Package.
• The Vnet/IP network of a CENTUM system and the Vnet/IP-Upstream network of a FAST/
TOOLS Integration system must be physically segregated. Connection via a switch or a
router is not allowed, either.
• ProSafe-RS systems built on a V net network cannot be integrated with FAST/TOOLS.
Therefore, the V net router (AVR10D) cannot be used also.
• Connection via Exaopc interface is not allowed in a system integrated with FAST/TOOLS.
• The Standard mode and Wide-area mode can be set for each domain. However, the Nar-
rowband mode cannot be set for each domain and must be set to all domains. It cannot
be used together with other modes.

<A1.1 Outlines of FAST/TOOLS integrated system> A1-2
A1.1 Outlines of FAST/TOOLS integrated

system
The following describes the functions in the FAST/TOOLS Integration system and the system
configuration:
• On a safety engineering PC (SENG) having a license for the FAST/TOOLS Integration
Engineering Package, you can define domain properties and the tag names for the data
of SCSs accessed by FAST/TOOLS.
• From FAST/TOOLS, the data of STARDOM FCN/FCJ and ProSafe-RS SCS can be com-
prehensively monitored.
• Vnet/IP-Upstream is used as the control bus for linking ProSafe-RS, FAST/TOOLS,
STARDOM and PRM.
• The field devices connected to STARDOM and the field devices connected to ProSafe-
RS can be comprehensively managed through PRM.
• Since SCSU1 supports SCS data buffering and the gas flow rate calculation, you can
configure the system without STARDOM.
IMPORTANT
• FAST/TOOLS integration is certified as Interference-Free.
• The system should be configured so that abnormalities in SCS and the devices connec-
ted to SCS are all detected by the ProSafe-RS system, and the diagnostic information
upon detection of abnormality should be confirmed on SENG.
n System configuration
The following illustrates a sample system configuration in Wide-area mode/Narrowband mode
of Vnet/IP-Upstream network in FAST/TOOLS Integration configuration.
The SCSs that can be used for FAST/TOOLS Integration configuration are SCSP1, SCSP2,
and SCSU1.

STARDOM PRM Server/Field Domain A
SNTP Server Engineering Communication
FAST/TOOLS SENG
Computer Server PRM Client
Vnet/IP-Upstream (100 Mbps or more)
SCS SCS
SCS FCN/FCJ
L2SW
L2SW L2SW
FAST/TOOLS
(Redundant Server)
FCN/FCJ FCN/FCJ
FAST/TOOLS: YOKOGAWA SCADA System

PRM: Plant Resource Manager
SNTP Server:
Simple Network Time Protocol Server Domain B SCS SCS Domain C
FCN/FCJ: STARDOM Controller
L3SW L2SW L2SW L3SW L2SW
Vnet/IP-Upstream (100 Mbps or more)

FCN/FCJ FCN/FCJ
Figure A1.1-1 Sample Vnet/IP network system configuration in Wide-area mode
PRM Server/Field Domain A

SNTPServer Communication
FAST/TOOLS
SENG Server PRM Client
Vnet/IP-Upstream
(2 Mbps or more but less than 100 Mbps)
SCSU1 SCSU1
SCSU1 L2SW
L2SW L2SW
FAST/TOOLS
(Redundant Server)
FAST/TOOLS: YOKOGAWA SCADA System

PRM: Plant Resource Manager
SNTP Server: Domain B SCSU1 SCSU1 Domain C
Simple Network Time Protocol Server
L3SW L2SW L2SW L3SW L2SW
Vnet/IP-Upstream
(2 Mbps or more but less than 100 Mbps)
Figure A1.1-2 Sample Vnet/IP network system configuration in Narrowband mode

n Recommended environments
The following sections show the recommended software and hardware environments for
FAST/TOOLS Integration.
l Software environment
The software environments for FAST/TOOLS Integration configuration depend on the type of
SCS that you use. The software environments for FAST/TOOLS Integration configuration of
each SCS are as follows:
For SCSP1 and SCSP2
• ProSafe-RS: R2.02 or later for SCSP1 and R2.03 or later for SCSP2
• FAST/TOOLS: R9.02 or later
• STARDOM (FCN/FCJ): R2.01 or later
• PRM: R3.03 or later for SCSP1 and R3.04 or later for SCSP2
For SCSU1
• ProSafe-RS: R3.02.10 or later
• FAST/TOOLS: R9.05 SP2 or later
• PRM: R3.12 or later
l Hardware environment
To communicate with FAST/TOOLS Integration configuration, hardware that configures the
network for the following system is required:
• Hardware necessary for the Standard and the Wide-area modes
• VI702/VI701 (Vnet/IP interface card installed in PC components such as SENG)
Firmware revision (F): 12 or later
• SCP461 (Processor module installed in SCSP2)
Any firmware revision.
• SCP451 (Processor module installed in SCSP1 and SCSU1)
Firmware revision (F1) for SCSP1: 12 or later
Firmware revision (F1) for SCSU1: 19 or later
• Hardware necessary for the Narrowband mode
• VI702/VI701 (Vnet/IP interface card installed in PC components such as SENG)
Firmware revision (F): 19 or later
• SCP451 (Processor module installed in SCSU1)
Firmware revision (F1): 19 or later
n Upstream system SCS overview

SCSU1 is provided as an SCS for building an Upstream system. If the type of SCS connect-
ing to Vnet/IP-Upstream network includes only SCSU1, Vnet/IP-Upstream network can be
used in Narrowband mode. Also, the Gas flow rate calculation FB is supported only in
SCSU1.

n Data when starting SCS

The data specification for SCSU1 is the same as other SCS's. SCSU1 has data retaining
function that stores retainable data in memory with battery backup that is not supported by
other SCSs.
The following describes the in-memory data status when SCS is started after offline down-
load, started after power is restored, and manually restarted.
l Data status when starting SCS
Table A1.1-1 Data status when starting SCS

Started after offline down- Started after power is re-
Data stored in... Data in SCS
load stored/Manually restarted
Main memory Variable in application log- Initial value Initial value
ic
Data in function block Function block performs ini- Function block performs in-
tialization itialization
Security level Level 2 Level 2
Lock status of the variable Reset Reset
Data of CENTUM integra- Initial value Initial value
tion function
Flash memory (*1) System program Loaded programs Returns to the program
used before the outage/
stoppage.
Database Loaded database Returns to the database
used before the outage/
stoppage.
Contents of online modifi- Changes made before the
cation outage/stoppage are still
valid.
Password for changing the The password used before The password used before
security level loading is invalid (should be the outage/stoppage are
initialized). still valid.
Memory with bat- Specific log information The log information before The log information before
tery backup loading is not initialized. outage/stoppage is not ini-
tialized. (*2)
Retainable data Initial value (*3) The retained data before
outage/stoppage is not ini-
tialized, but the data will be
restored after SCS is star-
ted.
*1: This assumes that you have written into the flash memory.
*2: If the outage time exceeds about 300 hours, the data in the memory will be lost.
*3: It will not be initialized for master database offline download.
SEE
ALSO For more information about actions at SCS startup, refer to:
B5., “Operations at SCS startup” in Safety Control Station Reference (IM 32Q03B10-31E)
n Components of FAST/TOOLS Integration system

The following are necessary components to connect a FAST/TOOLS integrated ProSafe-RS
system to a Vnet/IP-Upstream network.

l Vnet/IP station
A station in which a component with a Vnet/IP interface is installed is called a Vnet/IP station.
The Vnet/IP station in a domain is connected to Layer 2 switch in each bus.
• SENG
An SENG is connected to the Vnet/IP-Upstream network through a Vnet/IP interface card
(VI702/VI701) installed on the computer. The VI702/VI701 card has two ports for connec-
tion to the UTP cables to support Vnet/IP-Upstream bus redundancy.
• SCS
SCS is used as a safety controller for the FAST/TOOLS Integration system. The Safety
Control Stations that can be connected to Vnet/IP-Upstream include SSC60S/SSC60D
(SCSP2), SSC50S/SSC50D (SCSP1), and SSC57S/SSC57D (SCSU1).
l Vnet/IP-Upstream domain
A Vnet/IP-Upstream domain consists of two independent subnets on each bus.
You can define up to 31 Vnet/IP-Upstream domains. A Vnet/IP-Upstream domain cannot han-
dle a Vnet station.
l Layer 2 switch
Vnet/IP stations and general-purpose Ethernet communication devices in a domain are con-
nected to Vnet/IP buses through the Layer 2 switches (L2SW). At least one L2SW is required
for bus1 and bus 2 respectively.
l Layer 3 switch
A layer 3 switch (L3SW) is used to connect between Vnet/IP-Upstream domains on each bus.
l Router
This is used to connect Vnet/IP-Upstream domains in a wide-area network.
l Ethernet device
STARDOM stations and general-purpose Ethernet communication devices in which a Vnet/IP
interface card is not installed are connected to bus 2 of Vnet/IP-Upstream.
IMPORTANT
• When the bandwidth used by Vnet/IP-Upstream is 100 Mbps, control the traffic flowing
from general-purpose Ethernet devices into a Vnet/IP-Upstream network according to the
engineering guidelines of FAST/TOOLS.
• When the bandwidth used by Vnet/IP-Upstream is 1 Gbps, use a hub to control the traffic
flowing from general-purpose Ethernet devices to a Vnet/IP-Upstream network so as to
prevent it from exceeding 300 Mbps (for example, three 100 Mbps ports).
To connect Vnet/IP-Upstream network to an external network such as wide-area network,

separate the network using a router.

IMPORTANT
In a system using open communication on bus 2 of Vnet/IP-Upstream, when you connect
SCSs in Vnet/IP-Upstream network where general-purpose Ethernet devices are connected,
use intelligent switches such as Layer 2 switches in order to prevent multi-casting of open
communication from flowing into the SCSs.
l STARDOM Controller
Open communication is performed between a STARDOM controller (FCN/FCJ) and a FAST/
TOOLS station. A network of STARDOM controllers can be configured for redundancy by us-
ing bus 2 as the primary bus and bus 1 as the secondary bus.
l SNTP server
This can be a reference for network time.
In addition to an SNTP server connected to Vnet/IP-Upstream network, a reference for net-
work time can also be an SNTP server that STARDOM references.

<A1.2 Overview of a Vnet/IP-Upstream network> A1-8
A1.2 Overview of a Vnet/IP-Upstream network

Vnet/IP-Upstream is the name of a network for control communication and is compliant with
IEEE802.3 standards. This is a reliable network as redundancy is achieved using Bus 1 and
Bus 2.
The transmission speed depends on the network mode used. The Standard mode supports 1
Gbps, the Wide-area mode supports 100 Mbps or more, and the Narrowband mode supports
2 Mbps up to less than 100 Mbps.
A Vnet/IP-Upstream network is built by using network devices such as Layer 2 and Layer 3
switches, and transmission media such as UTP (Unshielded Twisted Pair) cables and optical
fiber cables.
n Communication channels of control communication and open

communication
A Vet/IP-Upstream network is a redundant network for control communication. In Vnet/IP-Up-
stream, redundant buses are configured with independent subnets of bus 1 and bus 2.
Normally, bus 1 is used for control communication. When bus 1 fails for some reason, bus 2 is
used for control communication. Ethernet communication is performed by either installing an
Ethernet network apart from the Vnet/IP-Upstream or using bus 2 of the Vnet/IP-Upstream.
Ethernet communication using bus 2 of the Vnet/IP-Upstream is referred as open communica-
tion. Open communication always uses bus 2. Note that, if bus 1 fails, bus 2 is used for both
control communications and open communications. In this situation, the bandwidth for open
communication is restricted in order to secure the bandwidth for control communication.
If an Ethernet network is installed in your system, replace the phrase "connect to bus 2 of the
Vnet/IP-Upstream" with "connect to the installed Ethernet" when you read the following de-
scriptions, as long as the phrase is used in the context of performing open communications.

<A1.3 Time synchronization of FAST/TOOLS Integration> A1-9
A1.3 Time synchronization of FAST/TOOLS

Integration
Time synchronization is performed among stations connected to the FAST/TOOLS integrated
Vnet/IP-Upstream network. If you connect an SNTP server to Vnet/IP-Upstream network, you
can specify reference time to synchronize. The stations (hereafter referred to as Vnet/IP sta-
tion) connected to Vnet/IP-Upstream network, which is equipped with a Vnet/IP device, can
have their time synchronized by using the time synchronization mechanism of Vnet/IP-Up-
stream network.
n Types of time synchronization

There are two modes of Vnet/IP-Upstream network time synchronization:
• Synchronization with Vnet/IP time that uses the Vnet/IP-Upstream network time master
for time synchronization
• A method that synchronizes to the SNTP server connected to the Vnet/IP-Upstream net-
work
Use the method that synchronizes to the SNTP server, if you connect STARDOM to a
Vnet/IP-Upstream network.
SEE
ALSO For more information about connecting an SNTP server, refer to:
The user's manual of STARDOM
n Overview of time synchronization

Time synchronization in a Vnet/IP-Upstream network is performed for each time group. A time
group is defined for each domain. The time for the entire Vnet/IP-Upstream network can be
standardized by setting the same time group number for all domains. When synchronizing the
stations in a Vnet/IP-Upstream network with UTC (Universal Time Coordinated), an SNTP
server needs to be connected in each time group.
If the SNTP server is not connected or the time of SNTP server is not synchronized with the
standard time, Vnet/IP station is synchronized in the Vnet/IP time method. One Vnet/IP sta-
tion in the time group is the time master station, and all of the Vnet/IP stations in the time
group are synchronized with the time master station.
When the SNTP server is connected to the Vnet/IP-Upstream network, the engineering work
is required by using the Domain Properties Setting Tool on SENG and the Vnet/IP stations in
the time group are automatically synchronized with the SNTP server.

Time group 1 Time group 2

SNTP server SNTP server
SENG SENG
L3SW
Vnet/IP-Upstream L3SW Vnet/IP-Upstream
domain 1 domain 3
L3SW
L3SW L3SW
L3SW
SCS SCS
Vnet/IP-Upstream
domain 2
SCS
L3SW: Layer 3 switch
Figure A1.3-1 Time synchronization of Vnet/IP-Upstream network
SEE
ALSO For more information about precautions for time synchronization, refer to:
“■ Precautions for Time Synchronization” in 2.15, “Time Synchronization” in Engineering Guide (IM
32Q01C10-31E)
n Accuracy of time synchronization

Time management of Vnet/IP stations is performed through Vnet/IP-Upstream network.
A Vnet/IP station performs time synchronization for the entire Vnet/IP-Upstream network. This
reference time is referred to as the network time. Relative accuracy of network time by the
action mode is as follows:
Table A1.3-1 Accuracy of network time in the Standard mode

Station Relative time accuracy
±1 ms. When one bus is abnormal, the accuracy may become worse than ±1 ms
In a domain
due to heavy open communication traffic.
Among domains due to heavy open communication traffic. The relative time accuracy deteriorates
in proportion to transmission delay time variations among domains.
Table A1.3-2 Accuracy of network time in the Wide-area mode

In a domain/Among do-
due to heavy open communication traffic. The relative time accuracy deteriorates
mains
in proportion to transmission delay time variations among domains.
Table A1.3-3 Accuracy of network time in the Narrowband mode

In a domain/Among do-
±500 ms
mains
The system software of a Vnet/IP station references the network time, and adjusts the station
system time according to the network time. Because the method of time adjustment is differ-

ent in each station type, the gap at the system time and the network time is as follows respec-
tively.
Table A1.3-4 Accuracies of the system time

Deviation from
Station type Time adjustment method
network time
The deviation between the network time and the system
SENG or other stations oper- time will be checked all the time. If the deviation ex-
Maximum 500 ms
ating on a computer ceeds 500 ms, the system time will be adjusted to the
network time.
The system time always synchronizes with the network
SCSP2/SCSP1/SCSU1 None
time.
n Time groups
The time group denotes a range in which time synchronization is performed. The entire
Vnet/IP-Upstream network can be defined on one time group. On the other hand, by separat-
ing domains in the same Vnet/IP-Upstream network into time groups, the range in which time
synchronization is performed can be limited.
The time group number to which the domain belongs is 0 to 7. The default time group number
is 1. To perform time synchronization only within a domain, set the time group number to 0.
If an SNTP server does not exist in a time group, one of the Vnet/IP stations in a time group
will act as the time master station, and other Vnet/IP stations in the same time group will syn-
chronize with the time of the time master station.
n Engineering on time group

A time group can be defined using the Domain Properties Setting Tool on SENG.
SEE
ALSO For more information about the time group settings, refer to:
“l Time Group” on page C2-5
n Connection and redundancy of SNTP server

To synchronize the network time of a Vnet/IP station with the standard time, connect an SNTP
server in each time group. Only one SNTP server is connected within the same time group.
Generally, an SNTP server is connected to bus 1 of Vnet/IP-Upstream network. However, if
time synchronization is done with the devices that perform open communication, connect the
SNTP server to bus 2.
For the dual-redundant SNTP servers, one SNTP server needs to be added and connected to
both bus 1 and bus 2. In this case, the time master station in the Vnet/IP network will syn-
chronize the time with the SNTP server that is synchronized with the standard time. If the
SNTP server being referenced fails, the time synchronization will be performed with the other
SNTP server that is normal.
IMPORTANT
If there is a notification that the SNTP server that exists in a time group is not synchronized
with the standard time, all the stations in the time group will synchronize their times with the
time master station in the Vnet/IP network. When the SNTP server time is synchronized again
with the standard time, all the stations in the time group will synchronize their times with the
standard time, instead of the time master station in the Vnet/IP network, at once.

The default IP address of an SNTP server connected to Vnet/IP-Upstream network is as fol-
lows.
• IP address of an SNTP server connected to bus 1 of Vnet/IP-Upstream network:
192.168.<domain number>.254
• IP address of an SNTP server connected to bus 2 of Vnet/IP-Upstream network:
192.168.<128 + domain number>.254
n Time synchronization using FAST/TOOLS as an SNTP server

In Vnet/IP-Upstream Narrowband mode, a computer on which FAST/TOOLS is installed can
be used as an SNTP server instead of installing an SNTP server that is synchronized with the
absolute time. In this case, the OS clock on the computer on which FAST/TOOLS is installed
will be used as reference. Devices that adopts open communication are synchronized with
this SNTP server.
This reference time is communicated to the Time master station within the same time group
with up to 500 ms error by a Vnet/IP-Upstream network time synchronization service and is
reflected on the network time. Therefore, up to 500 ms differences may exist between the
Vnet/IP station time and the time of the open communication devices.
n Time synchronization after powering on Vnet/IP station in Vnet/IP-

Upstream Standard mode
In Vnet/IP-Upstream Standard mode, after a Vnet/IP station is powered on, the time of the
station inches closer to the network time of the same time group. Within 5 seconds after the
station startup, the relative time accuracy becomes 1 second, and within 5 minutes, it be-
comes ±1 ms.
n Time synchronization of SCS connected to Vnet/IP-Upstream

network
The system time of SCS that is connected to Vnet/IP-Upstream network is synchronized with
the network time of the Vnet/IP-Upstream network. Moreover, the DI module installed in the
SCS also synchronizes its time with this network time through SB/ESB buses.
If an SNTP server is available in the network, the SCS stations is synchronized with the
standard time. The accuracy of the synchronization with the standard time depends on the
SNTP server. If the SNTP server is not installed, the SCS is synchronized with the network
time, that is, the time of the time master station of Vnet/IP-Upstream network.
The state of the time synchronization of SCS stations, whether it is synchronized with the
standard time of SNTP server or not synchronized with the standard time but is synchronized
with the time master station, can be found using the following function block or monitored on
the following window.
• Output of the system function block (SYS_NETST)
• SCS State Management window of the SCS Maintenance Support Tool of SENG. The
time synchronization state of SCSP1/SCSP2/SCSU1 is displayed in Time Sync of the list
view when the CPU node is selected.
Even if the state of the time synchronization with the SCS time changes, no diagnostic infor-
mation massage or system alarm is output to notify this event. If the time synchronization
event needs to be notified, create an application logic using the SYS_NETST function block to
output the event to an external alarm lamp or to an annunciator.
Note, however, that the Synchronous Mode of SCS stations on the Communication tab of the
SCS Constants Builder should be set to Vnet/IP regardless the SNTP sever is available or
not.

SEE
ALSO For more information about SOER function in SCS station, refer to:
A7., “SOER” in Safety Control Station Reference (IM 32Q03B10-31E)
For more information about SYS_NETST, refer to:
C11.5, “SYS_NETST (control bus status indicator)” in Safety Control Station Reference (IM
32Q03B10-31E)
For more information about SCS Constants Builder, refer to:
3.1.3, “SCS Constants Builder” in Engineering Reference (IM 32Q04B10-31E)
n SCS SOER functions connected to the Vnet/IP-Upstream network

SCS SOER functions and behavior have no differences between when they are connected to
the Vnet/IP-Upstream network and when they are connected to the Vnet/IP network. In addi-
tion, SCSU1 SOER functions are not different from those of SCSP1. For more information re-
garding SCSU1 SOER functions, refer to the descriptions on SCSP1.
However, in Narrowband mode, the SOE event collection function is restricted in SENG be-
cause the network bandwidth is reduced.
SEE
ALSO For more information about the SOE event collection function of SENG in the Narrowband mode, refer to:
A3.2, “Functions and configuration of Vnet/IP-Upstream in Narrowband mode” on page A3-3
For more information about SOER in SCS station, refer to:
A7., “SOER” in Safety Control Station Reference (IM 32Q03B10-31E)

<A1.4 Vnet/IP-Upstream bus status> A1-14
A1.4 Vnet/IP-Upstream bus status

This chapter explains how to check the Vnet/IP-Upstream bus communication status
n Overview of Vnet/IP-Upstream bus status

In the SCS State Management window of the SCS Maintenance Support Tool on SENG, the
communication status of the buses in the domain that contains the SCS can be checked. By
creating an application logic using the system function block (SYS_NETST) that outputs the
bus status, the bus status can be output to an external alarm lamp for notification.
n Elements of the Vnet/IP-Upstream bus status

The Vnet/IP-Upstream bus status shows the communication status of the entire Vnet/IP-Up-
stream network, i.e., the stations in all the connected domains, as well as the devices (such
as Layer 3 switches) connecting the domains. For example, if abnormality occurs in bus 1 of a
station in domain 5 while you are monitoring through the SCS State Management window on
an SENG of domain 1, you can see the status of bus 1 of Vnet/IP-Upstream indicating abnor-
mality.
The Vnet/IP-Upstream bus status consists of the following three elements:
• Bus status in own domain
• Communication status of devices connecting the domains
• Bus status of other domains
Vnet/IP-Upstream
bus status
Information of domains is not
broadcasted beyond domains
except the bus status.
Bus status of Bus status of

the local domain other domains
Communication status Communication status Communication status

between stations in of devices connecting between stations in
the local domain the domains other domains
Figure A1.4-1 Elements of the Vnet/IP-Upstream bus status
l Indication of the status of communication between stations in a domain

Each station in a Vnet/IP-Upstream domain diagnoses bus statuses mutually by using bus 1
and bus 2. For the dual-redundant station, the control side and standby side diagnose bus
statuses alternately. Each station in a domain indicates the communication status of all sta-
tions for each bus based on the diagnostic information.
Communication statuses for a station are shown as follows.
• Communication status between stations from the control side (*1) to the control side
(*1).
• Communication status between stations from the control side (*1) to the standby side.
• Communication status between stations from the standby side to the control side (*1).
• Communication status between stations from the standby side to the standby side.

<A1.4 Vnet/IP-Upstream bus status> A1-15
*1: Including non-redundant station such as SENG, SCS station with single CPU.
l Bus status in a domain

The bus status in a domain is created from the communication status among stations in each
domain. If the bus status shows abnormality, the meaning varies with the type of failure:
• Either bus failure (either bus 1 or bus 2)
When either bus 1 or bus 2 encounters communication error, the status of the bus will be
indicated as abnormal.
• Both bus failure (both bus 1 and bus 2)
If both buses encounter errors, the first one will be indicated as abnormal. Failure of both
buses cannot be indicated.
TIP If both buses are failed to communicate with a specific station, it will be indicated as the station failure, and
the bus status will not be indicated as abnormal.
l Communication statuses of devices connecting domains

Between Vnet/IP-Upstream domains, communication is performed and monitored by bus 1
and bus 2. Communication status of the devices connecting domains are held as a matrix of
status for all combinations of domains for each bus.
The bus status of one domain can be broadcasted to all the stations in the Vnet/IP-Upstream
network through the communication between the domains.
n Priority of the Vnet/IP-Upstream bus status

The Vnet/IP-Upstream bus status represents a summary of all communication statuses in the
following order:
• Bus Status in Own Domain
If the bus status of own domain is abnormal, it is reflected in the Vnet/IP-Upstream bus
status. In case of either bus failure, the status of the failed bus is handled as abnormal. In
case of both bus failures, only the status of the bus in which abnormality is detected first
is handled as abnormal.
• Communication Statuses of Devices Connecting Domains
While the bus status of own domain is normal, the communication statuses of devices
connecting domains are reflected in the Vnet/IP-Upstream bus status. In case of either
bus failure, the status of the failed bus is handled as abnormal. In case of both bus fail-
ures, only the status of the bus in which abnormality is detected first is handled as abnor-
mal.
• Bus Statuses of Other Domains
If the communication statuses of all devices connecting domains are normal, the bus sta-
tuses of other domains are reflected in the Vnet/IP-Upstream bus status. However, even
if a different bus is abnormal in different domains, the Vnet/IP-Upstream bus statuses of
both buses are not handled as abnormal, and only the status of the bus in which abnor-
mality is detected first is handled as abnormal.

<A2. Vnet/IP-Upstream Standard/Wide-area modes> A2-1
A2. Vnet/IP-Upstream Standard/Wide-

area modes
Vnet/IP-Upstream network works in the Standard, Wide-area, or Narrowband mode. The net-
work configuration and the connection topology depend on the network mode respectively.
Use the Vnet/IP-Upstream Standard and Wide-area modes for a network bandwidth of 100
Mbps or more.
When a Vnet/IP-Upstream domain is created, engineering work is allowed after configuring
the computer as SENG. Set the address, the domain number, and the station number of hard-
ware using a network configuration and a connection topology for your desired network mode.

<A2.1 Network configuration in Standard and Wide-area modes> A2-2
A2.1 Network configuration in Standard and

Wide-area modes
This section describes the components of the systems that constitute a Vnet/IP-Upstream
network in Standard/Wide-are modes.
IMPORTANT
In the ProSafe-RS system where the FAST/TOOLS Integration Package is used, ensure that
no path connects to a V net or CENTUM Vnet/IP network.
n Network configuration overview in Standard and Wide-area modes

To put Vnet/IP-Upstream network into Standard/Wide-area modes, set the network mode by
using Domain Properties Setting Tool.
l Number of domains
Up to 31 domains can be connected. (However, domains that have any CENTUM station can-
not be connected.)
l Specifications of the network in Standard and Wide-area modes

You can select the scale of a domain either as "Standard" or "Wide-area" according to the dis-
tance between stations in the domain. This selection can be made by using the Domain Prop-
erties Setting Tool of ProSafe-RS.
If you select "Wide-area," the specifications of the domain will be as follows:
Communication speed: 100 Mbps or more
Distance between stations: Up to 1000 km (transmission delay is 40 ms or less)
If you select "Standard," the specifications of the domain will be as follows:
Communication speed: 1 Gbps
Distance between stations: Up to 40 km (transmission delay is 1 ms or less)
l Redundancy of open communication

In the Vnet/IP-Upstream network of a FAST/TOOLS integrated system, you can connect the
devices performing Vnet/IP-Upstream open communication and TCP/IP open communication,
not only to Vnet/IP-Upstream bus 2 but also to bus 1. This enables dual-redundant communi-
cation between STARDOM FCN/FCJ and FAST/TOOLS.

<A2.2 Network connection in Standard and Wide-area modes> A2-3
A2.2 Network connection in Standard and Wide-

area modes
This section describes the various types of connections required to build a Vnet/IP-Upstream
network.
• Connect devices included in Vnet/IP-Upstream domain
• Connection between Vnet/IP-Upstream domains

A2.2.1 Connect devices included in Vnet/IP-Upstream

domain
Devices in a Vnet/IP-Upstream domain are connected in a star topology using a Layer 2
switch as the central device. Since the redundantly configured Vnet/IP-Upstream buses must
be separated as independent subnets on each bus, it is necessary to install a Layer 2 switch
for each bus.
IMPORTANT
Multiple stations are connected to Layer 2 switches. It is strongly recommended to provide an
uninterruptible power supply (UPS) for Layer 2 switches so that they will not stop due to pow-
er failure.
If the Layer 2 switches stop due to power failure, there will be the following effects:
• A communication error will occur if Layer 2 switches for the buses stop due to power fail-
ure.
• For dual-redundant SCS, if the Layer 2 switches for both buses fail, the control will be
switched to the standby CPU in rare cases, causing the dual-redundant SCS to operate
in non-redundant mode.
• If a Layer 2 switch is restarted after momentary power failure, it takes several tens of sec-
onds for the communications between stations to recover.
n Specifications of connection within a Vnet/IP-Upstream domain

Standard or Wide-area setting can be selected as the extended specification of the Vnet/IP-
Upstream.
The specifications of network connection within a Vnet/IP domain are shown below:
l When Wide-area domain is selected

Distance between Vnet/IP stations: Up to 1000 km
Transmission delay: 40 ms or less
Levels of Layer 2 switches: No limit
l When Standard domain is selected

Distance between Vnet/IP stations: Up to 40 km
Levels of Layer 2 switches: Up to 7 levels
Distance between Layer 2 switch and station: Up to 100 m (when using
UTP cable)
Up to 5 km (when optical fiber
cable is used)
Connecting distance between Layer 2 switches: Up to 5 km (when optical fiber
cable is used)

IMPORTANT
Avoid the connection in which multiple communication routes exist between any two stations.
Otherwise, the communication may not be properly performed.
SCS SCS
L2SW L2SW
L2SW
Figure A2.2.1-1 Improper connection
TIP As for a dual-redundant SCS, both the controlling-side and standby-side CPU modules are connected to a
Layer 2 switch with UTP cables, but the SCS is counted as one station.

A2.2.2 Connection between Vnet/IP-Upstream domains

A Layer 3 switch is required for the connection between Vnet/IP-Upstream domains. Install a
Layer 3 switch for each of the dual-redundant Vnet/IP-Upstream buses and connect it to other
domains. By connecting multiple domains using a leased line, a network of domains can be
established over a broad area.
IMPORTANT
Multiple stations are connected to Layer 3 switches. It is strongly recommended to provide an
Uninterruptible Power Supply (UPS) for Layer 3 switches so that they will not stop due to
power failure.
n Specification when connecting between Vnet/IP-Upstream domains

The specification of connection between Vnet/IP-Upstream domains is as follows:
• Multi-level connection of Vnet/IP-Upstream domains: Max. 15 levels (16 layers) of
Layer 3 switches
• Transmission delay between any domains: Under 250 ms
IMPORTANT
• Avoid the connection in which multiple communication routes exist between any two do-
mains. Otherwise, the communication may not be properly performed.
Domain 1 L3SW Domain 2 L3SW Domain 3
L3SW
Figure A2.2.2-1 Improper connection
• If inter-SCS safety communications are performed among domains in a wide-area net-

work, it is recommended that the bandwidth for communication be 100 Mbps or greater.
SEE
ALSO For more information about configuring a wide-area network among domains, refer to:
“■ Extended Network Configuration” in 2.23, “FAST/TOOLS Integrated Configuration” in Engineering
Guide (IM 32Q01C10-31E)

<A2.3 Outline of station setup> A2-7
A2.3 Outline of station setup

Engineering work to create Vnet/IP-Upstream domains is performed on an SENG. Before
starting the engineering work, you need to set up a computer for use as an SENG.
The engineering for building a system of Vnet/IP-Upstream domain is as follows:
• Network Engineering
Select devices that configures Vnet/IP-Upstream network. In addition, set IP address.
• Engineering for SCSP2/SCSP1/SCSU1 stations on SENG
On an SENG, define the SCSP2/SCSP1/SCSU1 stations and create the applications.
IMPORTANT
In a system using open communication on bus 2 of Vnet/IP-Upstream, when you connect
SCSs in Vnet/IP-Upstream network where general-purpose Ethernet devices are connected,
use intelligent switches as Layer 2 switches in order to prevent multicasting of open communi-
cation from flowing into the SCSs.
SEE
ALSO For more information about engineering for SCS stations on SENG, refer to:
C., “Engineering and maintenance” on page C-1
For more information about procedure to set up SENG, refer to:
B3., “Setting Up the SENG” in Installation (IM 32Q01C50-31E)
n Setting addresses on hardware

This section explains the hardware address, domain number, station number and other set-
ting items for Vnet/IP stations.
l SCS Hardware setting items

SCS hardware setting items include the domain number and the station number for each
Vnet/IP station. The Vnet/IP-Upstream address will be automatically determined according to
the domain number and the station number set on the hardware.
If the station has dual-redundant CPU modules, the same domain and station numbers
should be set on both the control side and stand-by side. If the control side and standby side
have different numbers, the CPU of the standby side cannot start for dual-redundant opera-
tion.
Usually, set the FIX switch on the CPU module of the SCS to OFF. OFF means Auto Negotia-
tion. By default, OFF is set.
SEE
ALSO For more information about the hardware setting, refer to:
• 4.2, “Processor Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
• 6.7, “Setting the Vnet/IP Interface Card Station Address” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
l Domain number
The Vnet/IP-Upstream domain number needs to be set within the range from 1 to 31.
The domain number can be set by the DIP switch on the hardware.

<A2.3 Outline of station setup> A2-8
l Station number
The Vnet/IP station number needs to be set within the range of 1 to 64. The station numbers
in the same domain should not be identical.
The station number can be set by the DIP switch on the hardware.

<A3. Vnet/IP-Upstream Narrowband mode> A3-1
A3. Vnet/IP-Upstream Narrowband

mode
Vnet/IP-Upstream network is the network to distribute small-sized control systems and safety
systems over wells and pipelines distributed in broad areas. Vnet/IP-Upstream network is
used in order to integrate FAST/TOOLS and ProSafe-RS.
In Narrowband mode of Vnet/IP-Upstream network that uses SCSU1 only, SCSs can be in-
stalled at wells distributed in wider area, because network with narrower bandwidth is suppor-
ted.
In Narrowband mode, unnecessary functions are limited depending on usage conditions of
the line.
SEE
ALSO For more information about the Ethernet devices constituting a the Narrowband system, refer to:
“l Ethernet device” on page A1-6
For more information about actions on error detection, refer to:
“■ Actions on Error Detection” in 2.10, “Diagnosis Function of SCS” in Engineering Guide (IM
32Q01C10-31E)

<A3.1 Network configuration in Narrowband mode> A3-2
A3.1 Network configuration in Narrowband

mode
This section describes the components and specification of the system that is built on a
Vnet/IP-Upstream network.
n Connection specifications in Narrowband mode

To use Vnet/IP-Upstream network in Narrowband mode, you need to set the network mode by
using the Domain Properties Setting Tool.
l Details of connection specifications

The following specification applies when "Narrowband" mode is set using the Domain Proper-
ties Setting Tool of ProSafe-RS. For the items that are not shown below, specification is the
same as when set to "Standard" mode.
Bandwidth: 2 Mbps or more
Distance between Vnet/IP stations: 10000 km or less
Transmission delay: 500 ms or less
Levels of Layer 2 switches within a domain: No limit

<A3.2 Functions and configuration of Vnet/IP-Upstream in Narrowband mode> A3-3
A3.2 Functions and configuration of Vnet/IP-

Upstream in Narrowband mode
When the Vnet/IP-Upstream network is used in Narrowband mode, automatic collection of
SOE events and diagnostic information messages that occurred in SCSs are suspended or
window display is restricted to use the narrow band effectively.
For these purposes, when you use the Vnet/IP-Upstream network in Narrowband mode,
group SCSs and SENGs that have the same narrowband network in their communication
paths, and restrict communication for each of these groups. The grouped unit is called "Nar-
rowband group." Configuring the Narrowband groups is called "Narrowband group definition."
n Overview of the communication procedure in Narrowband mode for

SCS Maintenance Support Tool
This section describes an overview of the communication procedure in Narrowband mode,
comparing with the procedure in Standard/Wide-area modes.
In Standard/Wide-area modes, Message Cache Service periodically creates a list of SCSs it
actually communicate with, and will communicate with all the SCSs in the list one by one.
In Narrowband mode, Message Cache Service creates a list of SCSs to communicate with,
and then verifies each SCS in the list referring to the narrowband group definition information.
As a result of verification, the SENG will communicate only with the SCSs that meet all the
following conditions:
• The SCS belongs to a narrowband group.
• The number of SCSs allowed for communication that is set for the narrowband group to
which the SCS belongs is not exceeded.
• Automatic data acquisition is not suspended for the narrowband group to which the SCS
belongs.
• Automatic data acquisition is enabled for the SCS, or the SCS is included in the back-
ground data acquisition.
For SENG in Narrowband mode, there is a limit on the number of windows that can be dis-
played by using SCS Maintenance Support Tool.
In Standard/Wide-area modes, the SENG is collecting data from SCSs while the SCS Mainte-
nance Support Tool window is displayed. As for SOE viewer and the Diagnostic Information
window, the data collection from the SCSs displayed in the window will continue in the back-
ground even after the window is closed. The automatic data acquisition function of Message
Cache Tool periodically collects SOE events and diagnostic information messages from
SCSs.
In Narrowband mode, you can start only one SOE viewer and only one Diagnostic Information
window. For the collection of SOE events and diagnostic information messages, there are lim-
its on the number of SCSs and limits of timing in which you can perform collection simultane-
ously. If you close the Diagnostic Information window or SOE viewer, collection in the back-
ground is stopped.
SEE
ALSO For more information about background collection and auto collection, refer to:
“n Acquisition of SOE events and diagnostic information messages occurred in SCS” on page A3-4
n Tips for using Narrowband communication line

The following functions of the SCS maintenance support tool are subject to restricted commu-
nication when used in Narrowband mode:
• Collection of SOE events and diagnostic information messages occurred in SCS

• SCS status display
• Display of SOE events and diagnostic information messages
With ProSafe-RS, you can collect SOE events and diagnostic information messages that oc-
curred in SCSs as well as display the SCS status, SOE events, and diagnostic information
messages.
In Narrowband mode, because the communication line bandwidth is narrower than in the
Standard or Wide-area mode, communication for data collection and display functions are
kept minimized.
n Acquisition of SOE events and diagnostic information messages

occurred in SCS
SOE events and diagnostic information messages occurred in SCSs are automatically ac-
quired. Background data acquisition will continue even after SOE Viewer is closed. In the Nar-
rowband mode, automatic data acquisition and background data acquisition can be limited. In
the context of the Narrowband mode, automatic data acquisition and background data acquis-
ition are collectively referred to as "data acquisition."
l Background data acquisition

Background data acquisition is started when a query is run in SOE viewer or when a Diagnos-
tic Information window is displayed.
It will not collect newly generated SOE events or diagnostic information messages after back-
ground collection completes.
Background data acquisition collects data from SCSs displayed in the SOE viewer or Diag-
nostic Information window. It will continue the execution until it collects all the SOE events and
diagnostic information messages that SCS retains. Background collection stops if it collects
all, and will not be resumed until you run a query again in the SOE viewer or until you redis-
play the Diagnostic Information window.
TIP The Diagnostic Information window receives and displays not only the diagnostic information messages col-
lected in the background but also the diagnostic information messages broadcast from SCS. The window dis-
plays the latest diagnostic information messages even after the background data acquisition is completed. It
does not display the diagnostic information messages that it could not receive. In addition, broadcasted mes-
sages are not stored as cache data but only displayed in the Diagnostic Information window.
l Automatic data acquisition

The message collection configured as automatic acquisition (hereafter referred to as automat-
ic acquisition) is started for an SCS when you set the SCS as a target of automatic acquisition
by using the Message Cache Tool. Once automatic acquisition is started, the message cach-
ing service periodically checks if a new SOE event and diagnostic information message are
generated for the preset SCS. If any new SOE event or diagnostic information message exist
in the SCS, auto collection will collect the SOE events and or its diagnostic information mes-
sages and store them as cached data.
n Behaviors in Narrowband mode

If you set the network mode to Narrowband mode by using the Domain Properties Setting
Tool, SCS maintenance support tool will also operate in narrowband mode.
l SCS status display in the Narrowband mode

In the Standard and Wide-area modes, the update cycle of SCS Status Overview window of
SCS Maintenance Support Tool is 1 second. In the Narrowband mode, because the number
of SCSs allowed for communication per display update cycle to retrieve status information is

limited; therefore, updating of the status display is delayed depending on the limited number
of communicated SCSs for each narrowband group.
The behaviors of SCS Status Overview window in the Narrowband mode are as follows:
• The SCS Status Overview window obtains SCS statuses through periodical communica-
tion with SCSs within the number of SCSs allowed for communication per display update
cycle, which is set using the SCS Maintenance Support Tool.
Example:
When 20 SCSs are displayed in the SCS Status Overview window and the num-
ber of SCSs allowed for communication per display update cycle is set to 10, the
SENG communicates with 10 SCSs every second to obtain the status. As a result,
the status display for each SCS is updated at two second intervals.
TIP The number of SCSs allowed for communication per display update cycle is limited by the setting in the Nar-
rowband Group Definition window. Therefore, even if an alarm occurs in an SCS, the status of the SCS may
be displayed as normal until the communication for obtaining the status of that SCS is completed.
Example:
Even if a diagnostic information message indicating Fail is broadcasted and displayed for a certain
SCS, the status of that SCS remains READY.
• Blank will be displayed for the "SCS Status," "CPU Status" and "Comment" of the SCS
whose status is not obtained.
• When navigating from SCS State Management window to SCS Status Overview window
and then returning to SCS State Management window again, the statuses are obtained
from the beginning of the SCS list of the SCS Status Overview window.
• The Diagnostic Information button for SCS whose status is not obtained is displayed in
gray until the status is obtained, but the button is operational. Clicking the button displays
the Diagnostic Information window to enable to check received messages.
• Even if the status in the SCS Status Overview window is not updated, SCS State Man-
agement window can be called for the SCS.
• If a narrowband group where automatic acquisition is paused exists in the Narrowband
Group Definition window of the Message Cache Tool, "(Pause)" is displayed at the head
of the window title of the SCS Status Overview window.
• The Suspended data acquisition checkbox does not affect update of the SCS Status
Overview window. Display of SCS state list is also updated even for SCS that belongs to
a narrowband group with pause state. The purpose of the Suspended data acquisition
checkbox is to pause the collection of SOE events and diagnostic information messages.
• The SENG only obtains the status of SCSs that are displayed in the SCS Status Over-
view window and also contained in the SCS list of a narrowband group. The SENG does
not communicate with SCSs that became hidden as a result of scrolling or resizing the
SCS Status Overview window.
• When the SCS displayed at the top of the list is changed by scroll operation or change of
the window size, statuses are obtained again from the SCS that newly comes to the top
of the list.
• When the SCS that is displayed at the top of the list is not changed by changing the win-
dow size, including by stretching the window downward to expand the display area, sta-
tuses are not obtained again from the top SCS but update of statuses is continued from
the SCS next to the one that was updated before the change of the window size.
• When a displayed SCS is deleted from a narrowband group, the SCS Status Overview
window continues to display the status before the SCS is deleted.
If you have deleted an SCS or a narrowband group definition in the Narrowband Group
Definition window, display the window again to display the latest state.

SEE
ALSO For more information about sample displays in which automatic acquisition is suspended, refer to:
“n Pausing and starting data acquisition process” on page C3-10
l Behaviors of Message Cache Tool in Narrowband mode

Behaviors of the Message Cache Tool in Narrowband mode are as follows:
• Cache data that is stored in other SENG cannot be referred. The controls on Setup dialog
box that adds other SENG to be referred is disabled.
For example, you cannot add stations in the Setup dialog box in Narrowband mode.
• The Narrowband Group Definition Window button on the Setup dialog box becomes ac-
tive.
• If a narrowband group where the automatic acquisition is paused exists in the Narrow-
band Group Definition window of the Message Cache Tool, "(Pause)" is displayed at the
head of the window title of the Message Cache Tool.
l Behaviors of the Diagnostic Information window in the Narrowband mode

The following are limitations on the Diagnostic Information window in Narrowband mode:
• Only one Diagnostic Information window can be displayed.
• When the Diagnostic Information window is closed, the background acquisition of diag-
nostic information messages on the displayed SCS is stopped.
To display the latest diagnostic information messages on SCS for which automatic data
acquisition is not specified in the Narrowband Group Definition window of the Message
Cache Tool, keep the Diagnostic Information window opened.
• Because the number of SCSs allowed for communication in each data acquisition cycle is
limited, the Narrowband mode takes more time to display all the previous diagnostic infor-
mation messages, compared to Standard mode and Wide-area mode.
• Because the number of SCSs allowed for communication in each data acquisition cycle is
limited, if the SENG fails to receive any latest diagnostic information messages, the Nar-
rowband mode takes more time to display the missing messages in the Diagnostic Infor-
mation window, compared to Standard mode and Wide-area mode.
• If a narrowband group where automatic acquisition is paused exists in the Narrowband
Group Definition window of the Message Cache Tool, "(Pause)" is displayed at the head
of the title of the Diagnostic Information window.
• When an SCS is deleted from a narrowband group while its diagnostic information mes-
sage is being displayed, the messages of that SCS will no longer be updated in the Diag-
nostic Information window. In this situation, ACK and DEL operations have no effect on
the messages of the deleted SCS.
When you have deleted an SCS or a narrowband group definition in the Narrowband
Group Definition window, display the window again to display the latest state.
• Diagnostic information messages of SCSs that do not belong to any narrowband group
are not displayed. For such SCSs, cached messages and broadcast messages are not
displayed, either.
l Behaviors of SOE viewer in the Narrowband mode

Behaviors of the SOE Viewer in the Narrowband mode are as follows:
• Only one window of SOE viewer can be displayed.
• Background data acquisition for the SCS displayed in SOE viewer is stopped after the
viewer is closed. To display the latest diagnostic information messages of SCS not speci-
fied for automatic data acquisition, keep the SOE viewer window opened.

• If SOE viewer is kept opened, collection from the SCSs for which automatic data acquisi-
tion is enabled delays because the number of SCSs allowed for communication in each
data collection cycle is limited.
• Since the number of SCSs allowed for communication in each data collection cycle is
limited, it takes more time to display the latest SOE events, compared to the Standard or
Wide-area mode.
• If there is any narrowband group where data acquisition is paused, "(Pause)" is displayed
on title bar of the SOE Viewer.
l Behaviors of SOE OPC interface in the Narrowband mode

Behaviors of the SOE OPC interface in the Narrowband mode are as follows:
• The SCSs specified in the SOE OPC interface setting receive a request for data collec-
tion from the OPC server via the message cache service at a fixed cycle. Therefore, such
SCSs are in the same condition as the SCS for which automatic data acquisition by the
message cache service is specified.
The SCS specified in the SOE OPC interface setting must be added to a narrowband
group beforehand.
• Up to 100 SCSs can be specified in the SOE OPC interface setting.
• The timing of data collection depends on the number of SCSs allowed for communication
that is specified in the Narrowband Group Definition window of the Message Cache Tool.
Therefore, it takes more time in the Narrowband mode, compared to the Standard or
Wide-area mode.
n Avoiding the limitation on the number of windows that can be

displayed
On the SENG in narrowband system, there is a limit on the number of windows of the SCS
Maintenance Support Tool that can be displayed.
In some cases, however, you can avoid the limitation on the number of windows that can be
displayed by configuring the settings regarding the acquisition of SOE events and diagnostic
information messages in the Narrowband Group Definition window.
SEE
ALSO For more information about configuring the Message Cache Tool's settings to avoid limitation on the number
of windows that can be displayed, refer to:
C3.8, “Collecting data from SCSs in a narrowband system in the same way as in the Standard and
Wide-area modes” on page C3-13
n Log of pause and resumption of automatic data acquisition

Pause and resumption of data acquisition are subject to SENG operation history manage-
ment. In an environment where the Access Control and Operation History Management Pack-
age is installed, the pause and resumption of automatic data acquisition are recorded in the
Common operation log database. They are not recorded in the operation log database for
each SCS project.

<B. Functions of Upstream systems> B-1
B. Functions of Upstream systems

SCSU1 is a model of SCS for use in Upstream systems. SCSU1 can be connected to narrow-
band network and supports buffering of SCS data and calculation of gas flow rate.
This part describes the data buffering function, gas flow rate calculation function and the hard-
ware of SCSU1.

<B1. Data buffering function> B1-1
B1. Data buffering function

This section describes the overview and engineering of the data buffering function.
Data buffering function can be used only in SCSU1.
IMPORTANT
When DNP3 slave function is enabled, the data buffering function cannot be used.
SEE
ALSO For more information about DNP3 slave function, refer to:
D., “DNP3 slave function” in Open Interfaces (IM 32Q05B10-31E)

<B1.1 Details of the data buffering function> B1-2
B1.1 Details of the data buffering function

The data buffering function saves application logic data of SCS with time stamps and allows
FAST/TOOLS to collect the data. Even if the communication between FAST/TOOLS and
SCSs is disconnected, the data buffering function enables you to view the change in data dur-
ing disconnected communication through the operator interface of FAST/TOOLS after the re-
covery of communication. This function is useful for an environment where the communication
between the FAST/TOOLS and the SCS is unstable or FAST/TOOLS is used in Narrowband.
The following figure shows the configuration of the data buffering function.
SENG FAST/TOOLS (Server) FAST/TOOLS (Client)

Multi-Language Buffered data Trend
Item data
Editor read function Store Refer
read t to
Vnet/IP-Upstream
Do
wn
s
Reque
lo
ad
SCSU1
Data buffering Buffered data
function collection function
Sto fer
re Re
Data buffer
(rotary buffer)
Figure B1.1-1 Configuration of the data buffering functions

<B1.2 Engineering for data buffering > B1-3
B1.2 Engineering for data buffering

To use the data buffering function, perform the following engineering:
• Estimating the communication bandwidth
• Engineering ProSafe-RS SENG for data buffering
• Engineering FAST/TOOLS for data buffering
SEE
ALSO For more information about estimating the communication bandwidth and engineering ProSafe-RS SENG
and FAST/TOOLS for data buffering, refer to:
“■ Engineering for Data Buffering” in 9.5, “Details of the data buffering function” in Engineering Guide (IM
32Q01C10-31E)
n Event buffering period of data buffering function blocks and number

of events that can be buffered
By connecting a variable of the application logic to a data buffering function block, the SCS
stores information on the variable in the data buffer of the SCS as an event. To the function
block, you must input the ID number of the variable in addition to the value of the variable.
Use any of the following as the trigger for the buffering:
• Change in the data value
• Fixed cycle
• Detection of a trigger
Information saved as an event is as follows:
• Value of application logic variable
• Time-stamp of variable
• ID number of variable
Time-stamp is the current time of the SCS at the beginning of the scan period of the func-
tion block.
The size of an event saved by the data buffering function block is all the same. The data buf-
fer of SCS can store up to 135000 events. FAST/TOOLS collects 100 events at one time. Ad-
just and set the collection period of FAST/TOOLS to avoid SCS data overflow. When the max-
imum number is exceeded, a new event is sequentially saved by overwriting the oldest event.
The data buffer is initialized when the SCS starts up, including the cases where the SCS is
restarted intentionally or restarted due to offline downloading. Events that were saved in the
data buffer before the SCS stops are erased.
SEE
ALSO For more information about details of the function block of data buffering, refer to:
Appendix 1.1, “Function blocks for data buffering function” on page App.1-2
n FAST/TOOLS engineering for event collection and items to specify

FAST/TOOLS collects events that are buffered in SCSs. To collect events, determine the fol-
lowing in the engineering of FAST/TOOLS:
• Event scan interval
• Catch up scan interval
To associate a data item of FAST/TOOLS with a variable of the SCS application logic, specify
the following for the data item:
• Tag name of the variable

<B1.2 Engineering for data buffering > B1-4
• ID number of the variable
Once the ID number of a variable is specified for a data item, the data buffering function will
collect data for the data item.
SEE
ALSO For more information about limit of the number of events stored in the buffer, refer to:
“■ Limitation on the Number of Events Saved in the Buffer” in 9.5, “Details of the data buffering function”
in Engineering Guide (IM 32Q01C10-31E)

<B2. Gas flow rate calculation function> B2-1
B2. Gas flow rate calculation function

Gas flow rate calculation function calculates the gas flow rate pursuant to American Gas As-
sociation (hereafter called "AGA") and creates report data. Using the Gas flow rate calculation
function, daily or hourly report data, including the total amount of gas flow, can be created
from the gas flow rate calculation result based on the AGA specifications. The Gas flow rate
calculation function is Interference-free. This must not be used for safety functions.
The gas flow rate calculation function can be used only in SCSU1.
ProSafe-RS provides the gas flow rate calculation function that has the following features:
• Perform gas flow rate calculation and create report data, based on AGA Report No.3
• Perform gas flow rate calculation and create report data, based on AGA Report No.7
• Calculate compressibility factors based on AGA Report No.8
• Calculate the speed of sound based on AGA Report No.10
• Data retaining function

<B2.1 Functional configuration of the Gas flow rate calculation function> B2-2
B2.1 Functional configuration of the Gas flow

rate calculation function
The Gas flow rate calculation function consists of the following:
• Gas flow rate calculation function of SCS
• Report data creation function of SCS
• Data buffering function of SCS
• Data retaining function of SCS
• External communication function block with the data retaining function of SCS
• Functions and Function blocks for supporting user-defined gas flow rate calculation in
SCS
• Mapping blocks and mapping elements of SCS
• Gas flow rate calculation-related function of SENG
• Gas flow rate calculation-related function of FAST/TOOLS
SENG FAST/TOOLS
Basic HMI Engineering
FAST/TOOLS Client (HMI)
Tag name
Diagnostic
builder
information Tag name Configuration
Operating information
Multi Language FTExcha
Function FAST/TOOLS Server
Editor nge
Diagnostic SCS
information databases Tag access Data buffering
Interface Interface
SCS
Mapping elements / Mapping FBs / Data buffering function
Parameters / Parameters /
Parameters Report data
Calculated data Calculated data
(Process Process Gas flow Report

inputs) data rate data
calculation Report data
External comm. function
Param creation
FB with data (FB)
eters function
Retaining func.
(FB)
External comm.
Param
FB with data Application
eters
retaining func. logic
Parameters Calculated data
Data retaining function
Figure B2.1-1 Functional configuration of the Gas flow rate calculation function
n Gas flow rate calculation function

Gas flow rate calculation function calculates gas flow rate, coefficient of compressibility, and
speed of sound based on AGA specification. For gas flow rate calculation, AGA_3 and
AGA_7 function blocks are used.

n Report data creation function

Report data creation function accumulates and averages the output values of gas flow rate
calculation function blocks and creates daily/hourly closing data for gas flow rate and so on.
For report data creation, AGA_R function block is used.
n Data buffering function

Data buffering function saves SCS application logic data with time stamps and allows FAST/
TOOLS to collect the data.
SEE
ALSO For more information about details of the data buffering functions, refer to:
B1.1, “Details of the data buffering function” on page B1-2
n Data retaining function

The data retaining function retains retainable data at SCS restart. It is realized by storing the
values of retainable data in the battery backed-up memory and restoring it at SCS restart.
The data retaining function is provided in the function blocks related to the gas flow rate cal-
culation function, and used for the following purpose:
• Retain parameter values set to the SCS from external devices such as FAST/TOOLS:
Use the external communication function block with data retaining function
• Retain intermediate results before the closing processing, the last daily closing data, and
the last hourly closing data: Use the report data creation function block
Even if the SCS is restarted before the data are collected by FAST/TOOLS, the closing
data is not lost because the calculation of accumulated values and the average values
continues from the data immediately before the restart.
n External communication function block with the data retaining

function
External communication function blocks with data retaining function enables data setting to
the application logic of the SCS from an external device. External communication function
blocks with data retaining function are ECWR_B, ECWR_I, and ECWR_R.
By using the external communication function blocks with data retaining function, the parame-
ter values to be input to function block of the gas flow rate calculation function can be set from
an external device such as FAST/TOOLS, and the set parameters can be retained.
n Supporting for user defined gas flow calculation

The following FUs and FB are provided to support user-defined gas flow calculation:
• ACCUM
• POWE
• LOGE

SEE
ALSO For more information about ACCUM (Accumulation), refer to:
Appendix 1.2.7, “ACCUM (Accumulation)” on page App.1-44
For more information about POWE (exponential function with base e), refer to:
C6.2, “POWE (exponential function with base e)” in Safety Control Station Reference (IM
32Q03B10-31E)
For more information about LOGE (natural logarithm), refer to:
C6.1, “LOGE (natural logarithm)” in Safety Control Station Reference (IM 32Q03B10-31E)
n Mapping blocks/elements
Mapping blocks/elements are the interface function used to access SCS data from FAST/
TOOLS by specifying tag names. The Gas flow rate calculation function generates mapping
blocks for gas flow rate calculation function blocks and report data creation function blocks. It
also generates, mapping elements that correspond to external communication function blocks
with data retaining function.
n Gas flow rate calculation-related function of SENG

The gas flow rate calculation-related function on SENG uses the engineering function and the
SCS maintenance support tool on the SENG.
By using the engineering function, you need to engineer the following items regarding the
SCS gas flow rate calculation:
• Creating application logic
• Defining tag names
• Exporting tag name information
SCS maintenance support tool displays diagnostic information messages from SCSs.
l Information about gas flow rate calculation-related function displayed in

the SCS Information dialog box
On the SCS tab of the SCS Information dialog box, the number of AGA_3, AGA_7, and
AGA_R function blocks used and the information about the memory used by the data retain-
ing function are displayed only for SCSU1.
Table B2.1-1 Information about gas flow rate calculation-related function displayed on the SCS tab
Item Description
AGA FB The number of AGA_3 and AGA_7 function block instances is shown.
This includes the number of instances defined as parameters of user-
defined function blocks.
AGA Report FB The number of AGA_R function block instances is shown. This includes
the number of instances defined as parameters of user-defined function
blocks.
Retainable Data The size of retainable data used is shown in bytes. This is determined
based on the number of instances of function blocks with data retaining
function (AGA_R, ACCUM, ECWR_B, ECWR_I, ECWR_R).
SEE
ALSO For more information about information about the SCS Information dialog box, refer to:
5.3, “Display SCS Information” in Utilities and Maintenance Reference (IM 32Q04B20-31E)

n Gas flow rate calculation-related function of FAST/TOOLS

FAST/TOOLS collects and sets application logic data and internal parameters of function
blocks regarding gas flow rate calculation.
FAST/TOOLS collects the gas flow rate calculation result data, including closing data, from
SCSs. You can make use of the collected data by creating and running the required applica-
tions on FAST/TOOLS.
You can perform engineering of FAST/TOOLS efficiently by using a tool of FAST/TOOLS to
import the files that are exported with the Tag Name Builder.

<B2.2 Function blocks used for gas flow rate calculation function> B2-6
B2.2 Function blocks used for gas flow rate

calculation function
Dedicated function blocks for gas flow rate calculation are provided in SCS. Moreover, some
of the function blocks use data retaining function that SCS supports. The following function
blocks can be used for gas flow rate calculation.
• Function blocks of gas flow rate calculation
• Function block of report data creation
• Function blocks that use data retaining function
SEE
ALSO For more information about example of an application logic in the gas flow rate calculation, refer to:
“■ Examples of Gas Flow Rate Calculation Application Logic” in 9.6, “Gas Flow Rate Calculation Func-
tion” in Engineering Guide (IM 32Q01C10-31E)
For more information about example of an application for creating report data, refer to:
“■ Example of an Application to Create a Report” in 9.6, “Gas Flow Rate Calculation Function” in Engi-
neering Guide (IM 32Q01C10-31E)

B2.2.1 Outline of function of gas flow rate calculation

function block
For gas flow rate calculation, AGA_3 and AGA_7 function blocks are used. The following ta-
ble shows the descriptions of the gas flow rate calculation function blocks.
Table B2.2.1-1 Gas flow rate calculation function blocks

Function block type Description
AGA_3 Performs the AGA Report No.3 and No.8-defined calculations and
computes the gas flow rate.
AGA_7 Performs the AGA Report No.7, No.8, and No.10-defined calculations
and computes the gas flow rate.
The gas flow rate calculation function is compliant with the specifications of the following re-
ports:
Table B2.2.1-2 Reports supported by the Gas flow rate calculation function
Report Number Title Note
AGA Report No.3 Orifice Metering of Natural Gas Part 3: Natural Gas Applications -
(1992)
AGA Report No.7 Measurement of Natural Gas by Turbine Meters (1996) -
AGA Report No.8 Compressibility Factor of Natural Gas and Related Hydrocarbon -
Gases (1992)
AGA Report No.10 Speed of Sound in Natural Gas and Other Related Hydrocarbon -
Gases (2003)
GPA Standard 2172-96 Calculation of Gross Heating Value, Relative Density and Com- Dry only
pressibility Factor for Natural Gas Mixtures from Composition Anal-
ysis
The gas flow rate calculation function block consists of the following functions:
Table B2.2.1-3 Functions that gas flow rate calculation function block provides
Function AGA_3 AGA_7 Note
Calculation execution con- Yes Yes -
trol
Reading parameters Yes Yes As the process input data and input parameters are differ-
ent between AGA_3 and AGA_7, the processing is differ-
Closing action at the Yes Yes ent.
change of a parameter
Process input processing Yes Yes
Reading gas composition Yes Yes -
data
Detecting gas production Yes Yes As the process input data and input parameters are differ-
stop ent between AGA_3 and AGA_7, the processing is differ-
ent.
Compressibility calculation Yes Yes -
(AGA8)
Gas flow rate calculation Yes No -
(AGA3)
Gas flow rate calculation No Yes -
(AGA7)
Calculation of Speed of No Yes -
sound (AGA10)
Continues on the next page

Table B2.2.1-3 Functions that gas flow rate calculation function block provides (Table continued)
Function AGA_3 AGA_7 Note
Heating value calculation Yes Yes -
(GPA2172)
Energy calculation Yes Yes -
SEE
ALSO For more information about details of the AGA_3 function block functions, refer to:
Appendix 1.2.1, “AGA_3 (AGA3 calculation)” on page App.1-21
For more information about details of the AGA_7 function block functions, refer to:
Appendix 1.2.2, “AGA_7 (AGA7 calculation)” on page App.1-29

B2.2.2 Outline of function of report data creation function

block
The following table shows the report data creation function block type name and function.
Table B2.2.2-1 Function block of report data creation

Function block type name Function
AGA_R Calculates the accumulated value and average value of the gas flow
rates produced by AGA_3 or AGA_7. Also performs the closing proc-
ess to create the daily and hourly closing data of gas flow rate as report
data.
n Functions provided by Report data creation function block

Report data creation function block provides the following functions:
• Calculation execution control
• Reading parameters
• Closing action at the change of a parameter
• Accumulated value calculation
• Average value calculation
• Gas production time calculation
• Closing processing
• Data retaining processing
SEE
ALSO For more information about details of the AGA_R function block functions, refer to:
Appendix 1.2.3, “AGA_R (Report data creation)” on page App.1-35
n Report data to be created

The report data creation function creates the following report data based on the closing tim-
ing:
• Daily closing data
• Hourly closing data
To create daily closing and hourly closing report data, SCS is holding daily and hourly current
data. Current data is the data after the previous closing but before the next closing process-
ing. The current data is updated at every scan period of application logic. SCS saves the cur-
rent data as closing data at the closing timing and current data is initialized. However, only
ACCUM_ VOLUME of the current data is initialized at the monthly closing. Report data crea-
tion function also outputs the monthly current data. SCS initializes the monthly current data at
monthly closing.
l Closing data (daily closing data and hourly closing data)

Closing data includes daily closing data and hourly closing data. Data contained in the daily
closing and hourly closing data is shown in the following table:
Table B2.2.2-2 Closing data

Data name Type Remarks
TOTAL_FLOW Totalization Total flow

Table B2.2.2-2 Closing data (Table continued)
RAW_VOLUME Totalization Total uncorrected flow
TOTAL_ENERGY Totalization Total energy
PULSES Totalization Pulse
ACCUM_VOLUME Totalization Accumulated flow at end (*1)
AVE_SP Average Average static pressure
AVE_DP Average Average differential pressure
AVE_TEMP Average Average temperature
AVE_FLOW Average Averaged flow rate at base condition
AVE_FLOW_RAW Average Averaged flow rate at flowing condition
AVE_ENERGY Average Average energy
AVE_COMPOSITION Average Averaged normalized gas composition
AVE_CALCULATED_REAL_SG Average Averaged Calculated Specific Gravity (Real)
AVE_CALCULATED_SG Average Averaged Calculated Specific Gravity (Ideal)
AVE_CALCULATED_HV Average Averaged Calculated Heating Value
AVE_CALCULATED_ID_HV Average Averaged Calculated Ideal Heating Value
PRODUCTION_TIME Others Gas production time
SHUT_TIME Others Gas production stop time
TIMESTAMP_SEC Others Time stamp
*1: Accumulated flow at end is the accumulated value for the current month (cumulative from the previous monthly closing up to
the last accumulation).
l Current data (daily data and hourly data prior to closure)

Data contained in the daily and hourly current data is shown in the following table:
Table B2.2.2-3 Current data (daily data and hourly data prior to closure)
RAW_VOLUME Totalization Total uncorrected flow
TOTAL_ENERGY Totalization Total energy
PULSES Totalization Pulse
ACCUM_VOLUME Totalization Accumulated flow at end (*1)
AVE_SP Average Average static pressure
AVE_DP Average Average differential pressure
AVE_TEMP Average Average temperature
AVE_FLOW Average Averaged flow rate at base condition
AVE_FLOW_RAW Average Averaged flow rate at flowing condition
AVE_ENERGY Average Average energy
AVE_COMPOSITION Average Averaged normalized gas composition
AVE_CALCULATED_REAL_SG Average Averaged Calculated Specific Gravity (Real)
AVE_CALCULATED_SG Average Averaged Calculated Specific Gravity (Ideal)
AVE_CALCULATED_HV Average Averaged Calculated Heating Value
AVE_CALCULATED_ID_HV Average Averaged Calculated Ideal Heating Value

Table B2.2.2-3 Current data (daily data and hourly data prior to closure) (Table continued)
PRODUCTION_TIME Others Gas production time
SHUT_TIME Others Gas production stop time
*1: Accumulated flow at end is the accumulated value for the current month (cumulative from the previous monthly closing up to
the last accumulation).
l Current data (monthly data before closing)

The following table shows the data contained in the current monthly data.
Table B2.2.2-4 Current data (monthly data before closing)


B2.2.3 Function blocks that use data retaining function

The data retaining function is a function that retains the values of retainable data and restores
the retained data when the SCS is restarted. Using a function block with the data retaining
function enables the application logic to run using the values before the restart of SCS. The
data retaining function is an interference-free function that can be used only in SCSU1.
n Retainable data and size

The data that can be retained are some of the internal parameters of the function blocks hav-
ing data retaining function.
• The maximum size of the retainable data per SCS is 6 KB.
• SENG checks the size of retainable data used on the SCS during build. In addition, the
amount of retainable data used appears on the SCS Information dialog box.
The following table shows the function blocks that have retainable data and the size of the
retainable data they use.
Table B2.2.3-1 Function blocks that have retainable data and the size of the retainable data used
Function block name Size of retainable data used by one function block
instance (Byte)
AGA_R 1900
ACCUM 8
ECWR_B 4
ECWR_I 4
ECWR_R 4
n Retaining and restoring retainable data in SCS

Retainable data are stored in battery-backed up memory at every scan period of the applica-
tion logic. Retainable data is restored at the first scan after SCS starts up. When off-line
download other than master database offline download is performed from SENG, the retaina-
ble data is not restored and initialized.
When the retainable data is initialized, the following system alarm is output.
"No. 4151 SCS0101 Retain Data Initialized"
TIP SCS also checks the build time of the SCS database when restoring the retainable data. When a build is per-
formed on SENG, the build time of the database is updated even if the application logic is not changed. When
performing off-line download of database of which build time is changed, the SCS considers it as database
mismatch and does not restore the retainable data.
SEE
ALSO For more information about details on system alarms, refer to:
Message Number 4151 in 2.1, “System Alarms (Message Numbers 4101 through 4199)” in Messages
(IM 32Q02B10-31E)
n External communication function block with data retaining function

External communication function blocks with data retaining function consist of ECWR_B,
ECWR_I, and ECWR_R.
• Using external communication function blocks with data retaining function enables setting
and referencing of data in the SCS from an external device by means of tag name specifi-
cation or Modbus slave communication.

• The external communication function blocks with data retaining function handles a setting
value that comes from outside the SCS as retainable data. The setting value that comes
from outside the SCS can be restored at the restart of the SCS.
• The external communication function blocks with data retaining function are interference-
free function blocks that can be used exclusively on SCSU1. Do not use them for input to
a safety loop.
SEE
ALSO For more information about details of the function block with external communication with BOOL-type data
retaining function, refer to:
Appendix 1.2.4, “ECWR_B (external communication with BOOL-type Data retaining function)” on page
App.1-41
For more information about details of the external communication function block with INTEGER-type data re-
taining function, refer to:
Appendix 1.2.5, “ECWR_I (External communication with INTEGER-type data retaining function)” on
page App.1-42
For more information about details of the external communication function block with REAL-type data retain-
ing function, refer to:
Appendix 1.2.6, “ECWR_R (External communication with REAL-type data retaining function)” on page
App.1-43
n Precautions when using the data retaining function

Precautions for using the data retaining function are as follows:
• Do not use an instance of function block that uses the data retaining function in two or
more places. Moreover, an instance must be executed once every period. The number of
executions must not be affected by loops, conditional branches, jumps, etc.
• Change the application logic online. When online change or master database offline
download is performed, the retain data of the SCS is retained.
• When you offline download an SCS database after modifying the application logic or per-
forming a build on the SENG, the data retained in the SCS are initialized. If the currently
retained data is important, save it into FAST/TOOLS before performing offline download.
• The system alarm No.4151 is also output when the SCS starts up for the first time after
the battery backed-up memory is lost.
TIP By using the Database Validity Check Tool of SENG before offline download, it is possible to check the build
time and CRC of the database.
SEE
ALSO For more information about process alarms, refer to:
“n Process alarms” on page C1-2
For more information about details on system alarms, refer to:
Message Number 4151 in 2.1, “System Alarms (Message Numbers 4101 through 4199)” in Messages
(IM 32Q02B10-31E)

<B2.3 Structures, mapping blocks, and mapping elements of function blocks for gas flow rate calculation
function> B2-14
B2.3 Structures, mapping blocks, and mapping

elements of function blocks for gas flow
The function blocks for gas flow rare calculation and report data creation handles some data
as a structure. In addition, mapping blocks and mapping elements are provided as the inter-
face with FAST/TOOLS.

function> B2-15
B2.3.1 Structures that are used by gas flow rate calculation

function block
The structures of function blocks for gas flow calculation function are shown below. These
structures are used by gas flow rate function blocks and report data creation function blocks.
• AGA_3_PARAM structure
• AGA_3_OUTPUT structure
• AGA_7_PARAM structure
• AGA_7_OUTPUT structure
• AGA_COMPOSITION structure
• AGA_R_PARAM structure
• AGA_CALC_DATA structure
• AGA_RP_H structure
• AGA_RP_D structure
• AGA_RP_M structure
SEE
ALSO For more information about details of the gas flow rate calculation function's function block structure , refer to:
Appendix 2., “Structure of function blocks of gas flow rate calculation function” on page App.2-1

function> B2-16
B2.3.2 Mapping blocks and mapping elements for gas flow

The variables and data of function blocks for gas flow rate calculation function are accessible
to FAST/TOOLS through the interface of mapping blocks and mapping elements.
SEE
ALSO For more information about details of mapping blocks/elements for FAST/TOOLS integrated system (environ-
ment), refer to:
Appendix 3., “Mapping blocks and mapping elements for FAST/TOOLS Integration” on page App.3-1

<B3. Hardware of SCS for Upstream system> B3-1
B3. Hardware of SCS for Upstream

system
This section describes the SCS hardware used for Upstream systems.

<B3.1 Configuration and name of the hardware> B3-2
B3.1 Configuration and name of the hardware

This section describes the hardware configuration of SCSU1.
• Safety control unit (For upstream systems)
Table B3.1-1 Safety control unit (For Upstream systems)

Name Model
Standard type safety control unit SSC57S-S
Wide range temperature type safety control unit SSC57S-F
Duplexed standard type safety control unit SSC57D-S
Duplexed wide range temperature type safety control unit SSC57D-F
• Safety node unit (Rack mountable type) (Model: SNB10D)

• Unit for optical ESB bus repeater module (Rack mountable type) (Model: SNT10D)
• I/O modules
• Devices relating to I/O modules
In the safety control unit (also called as CPU node), processor module and I/O module can be
installed in the same nest.
The hardware configuration of SSC57 is the same as SSC50.
n Restrictions on Module Installation

Restrictions are applied on the number of I/O modules installed in the safety control unit and
safety node unit, and the number of optical ESB bus repeater modules installed in the unit for
optical bus repeater module.
When you read the relevant GS documents for reference, replace the term "SSC50" with
"SSC57".
SEE
ALSO For more information about restrictions on I/O module installation, refer to:
Overview of ProSafe-RS I/O modules (GS 32Q06K20-31E)
For more information about restrictions on ESB bus optical repeater module installation, refer to:
ESB bus optical repeater modules (GS 32Q06L15-31E, GS32Q06L16-31E)

B3.1.1 Configuration of Safety Control Unit

There are two types of safety control unit. The standard type safety control unit (Ambient
Temperature: -20 to 40 deg. C) and wide range temperature type safety control unit (Ambient
Temperature: -20 to 70 deg. C).
In this manual, the illustrations and descriptions are mainly focused on the standard type
safety control unit in which the cooling fans are not installed.
n Standard Type Safety Control Unit for Upstream system

The components of the standard type safety control unit (Model: SSC57S-S/SSC57D-S) are
shown in the following figure.
IMPORTANT
The operating temperature range for the standard type safety control unit is –20 to 40 deg. C.
Be sure to use it within the range.
Processor module Power supply module

Such as Input/Output module
Grounding
terminal Base unit (5 UNIT) (*1)
Utility unit (1 UNIT) (*1)
Cable tray External interface unit
*1: 1 UNIT=44.45 mm
Figure B3.1.1-1 Configuration of Safety Control Unit (SSC57D-S)
Table B3.1.1-1 Model Names of Safety Control Unit Components (Standard Type)
Standard type safety control unit
Name Single configuration Duplexed configuration
(SSC57S-S) (SSC57D-S)
Power supply module (100-120 V AC) SPW481 2pcs SPW481 2pcs
Power supply module (24 V DC) SPW484 2pcs SPW484 2pcs
SCP451 SCP451
Processor module 1pcs 2pcs
(*1) (*1)
Dummy cover (for processor module) (*2) T9083VB 1pcs - -
Dummy cover (for I/O module) (*3) SDCV01 as required SDCV01 as required
ESB bus coupler module(*4) SEC401 2pcs SEC401 2pcs
External interface unit for standard type safety con-
- 1pcs - 1pcs
trol unit
*1: The firmware revision number (F1) of the processor module must be 19 or later.

*2: For non-redundant configuration, used to cover the slot at right-hand side of the single processor module.
*3: Used to cover the empty I/O module slot.
*4: Required if the safety nodes are used.
n Wide Range Temperature Type Safety Control Unit for Upstream

system
The components of the wide range temperature type safety control unit (Model: SSC57S-F/
SSC57D-F) are shown in the following figure.
The cooling fan unit is added to the standard type control unit so that the control unit works in
wider range of ambient environments (–20 to 70 deg. C).
Processor
module Power supply module
Such as Input/Output module
Grounding
Base unit (5 UNIT) (*1)
terminal
External interface unit (*1)

Cable tray
Utility unit (1 UNIT) (*1)
Empty (1 UNIT) (*1)
Node fan unit (2 UNIT) (*1)
Power supply unit Power input Fan unit

for fan unit terminal
*1: 1 UNIT=44.45 mm
Figure B3.1.1-2 Configuration of Safety Control Unit (SSC57D-F)
Table B3.1.1-2 Model Names of Safety Control Unit Components (Wide Range Temperature Type)
Wide range temperature type safety control unit
Name Single configuration Duplexed configuration
(SSC57S-F) (SSC57D-F)
Power supply module (24 V DC) SPW484 2pcs SPW484 2pcs
SCP451 SCP451
Processor module 1pcs 2pcs
(*1) (*1)
Dummy cover (for processor module)(*2) T9083VB 1pcs - -
Dummy cover (for I/O module)(*3) SDCV01 as required SDCV01 as required
ESB bus coupler module(*4) SEC401 2pcs SEC401 2pcs
External interface unit for wide range temperature
- 1pcs - 1pcs
type safety control unit
Power supply unit for fan unit (100-120/220-240 V
S9159FA 2pcs S9159FA 2pcs
AC)
Power supply unit for fan unit (24 V DC) S9160FA 2pcs S9160FA 2pcs
Fan unit AIP602 2pcs AIP602 2pcs

*1: The firmware revision number (F1) of the processor module must be 19 or later.
*2: For non-redundant configuration, used to cover the slot at right-hand side of the single processor module.
*3: Used to cover the empty I/O module slot.
*4: Required if the safety nodes are used.

B3.1.2 Configuration of devices connected to the Safety

Control Unit
The following describes the configuration of devices connected to the Safety Control Unit:
⋅ Safety Node Unit
⋅ Unit for ESB bus optical repeater module
⋅ I/O module
⋅ I/O module-related product (pressure clamp terminal block, terminal board, etc.)
SEE
ALSO For more information about safety node unit configuration, refer to:
1.2, “Configuration of Safety Node Unit” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about configuration of the unit for ESB bus optical repeater modules, refer to:
1.3, “Configuration of Unit for Optical Bus Repeater Module” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
For more information about configuration of I/O modules, refer to:
1.4, “Input/Output Modules” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about configuration of I/O module-related products, refer to:
1.5, “Accessories Related to Input/Output Modules” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)

<B3.2 Installing Devices > B3-7
B3.2 Installing Devices

This section explains the procedure and precautions for installing each device.
• Installing rack mountable device
• Installing terminal boards
SEE
ALSO For more information about rack mount devices installation, refer to:
2.1, “Installing Rack Mountable Devices” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about terminal port installation, refer to:
2.2, “Installing a Terminal Board” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)

<B3.3 Cable Connection > B3-8
B3.3 Cable Connection

The types of cable connections to the safety control unit, safety node unit and terminal board
which has already been installed are as follows:
• Power Cable Wiring
• Grounding
• Connecting Control Bus Cables
• Connecting ESB Bus Cables
• Connecting ESB Bus Fiber-Optic Cables
When referring to the IM using the reference links below, replace the terms "Vnet/IP" with
"Vnet/IP-Upstream", "SSC50" with "SSC57" and "SCSP1" with "SCSU1".
SEE
ALSO For more information about power supply cabling, refer to:
3.1, “Power Cable Wiring” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about grounding, refer to:
3.2, “Grounding” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about control bus cable connection, refer to:
3.3, “Connecting Control Bus Cables” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about ESB bus cable connection, refer to:
3.4.1, “Connecting ESB Bus Cable” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about ESB bus optical fiber cable connection, refer to:
3.4.2, “Connecting ESB Bus Fiber-Optic Cable” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)

<B3.4 Function of the units> B3-9
B3.4 Function of the units

This section describes the functions of modules and units making up the Safety Control Unit
and the Safety Node Unit, as well as the status of their LED indicator lamps, and setting ele-
ments.
• Power supply module
• Processor module
SSC57 uses processor module SCP451.
• ESB bus coupler module
• ESB bus interface module
• ESB bus optical repeater module
• External interface unit
• Node fan unit
• Power distribution unit
When referring to the IM using the reference links below, replace "Vnet/IP" with "Vnet/IP-Up-
stream", "SSC50" with "SSC57" and "SCSP1" with "SCSU1".
SEE
ALSO For more information about power supply module, refer to:
4.1, “Power Supply Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about processor module, refer to:
4.2, “Processor Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about ESB bus coupler module, refer to:
4.3, “ESB Bus Coupler Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about ESB bus interface module, refer to:
4.4, “ESB Bus Interface Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about ESB bus optical repeater module, refer to:
4.5, “Optical ESB Bus Repeater Module” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about external interface unit, refer to:
4.7, “External Interface Unit” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about node fan unit, refer to:
4.8, “Node Fan Unit” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)
For more information about power distribution unit, refer to:
4.9, “Power Distribution Unit” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)

<B3.5 Signal Cable Connection to Input/Output Modules > B3-10
B3.5 Signal Cable Connection to Input/Output

Modules
The connections between the I/O modules and the field devices can be established by directly
wiring the cables from the field devices to the terminals of I/O modules, connecting through
the terminal boards using signal cables and connectors or using the user-prepared MIL ca-
bles.
This chapter describes how to apply pressure clamp terminal blocks, connection cables, and
other I/O module related peripherals.
SEE
ALSO For more information about I/O module signal connection, refer to:
5., “Signal Cable Connection to Input/Output Modules” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)

<B3.6 Control bus interface card> B3-11
B3.6 Control bus interface card

In ProSafe-RS, install the control bus interface card in an SENG to connect to the safety con-
trol station (SCS). The control bus interface card is a communication card installed in PC/AT
compatible computers.
• To connect an SENG to Vnet/IP-Upstream, use a Vnet/IP interface card (Model: VI702/
VI701). VI701 supports PCI bus and VI702 supports PCI Express respectively. As the
function is the same between VI701 and VI702, the following is described for VI702.
There are two ports on VI702 to support dual-redundant Vnet/IP-Upstream. Install the
VI702 on the computer where the SENG software is installed, and connect the Vnet/IP-
Upstream cables to the VI702. This enables the engineering and maintenance of SCS
from an SENG through Vnet/IP-Upstream.
• Use VI702/VI701 with the firmware version (F) 19 or higher as the control bus interface
card for connection to Vnet/IP-Upstream.
When referring to the IM using the reference links below, replace "Vnet/IP" with "Vnet/IP-Up-
stream."
SEE
ALSO For more information about front panel of the Vnet/IP interface card, refer to:
6.6, “Front Panel of the Vnet/IP Interface Card” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
For more information about setting of the Vnet/IP interface card station address, refer to:
6.7, “Setting the Vnet/IP Interface Card Station Address” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
For more information about installation to and removal from the PC of the Vnet/IP interface card, refer to:
6.8, “Installing the Vnet/IP Interface Card in a PC” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)
For more information about attachment of the Vnet/IP-Upstream station address seal, refer to:
6.9, “Attaching the Vnet/IP Station Address Label” in Safety Control Stations (Hardware) (IM
32Q06C10-31E)

<B3.7 Maintenance of ProSafe-RS Hardware> B3-12
B3.7 Maintenance of ProSafe-RS Hardware

The maintenance of the ProSafe-RS hardware and parts replacement procedures such as in-
stalling and removing the common modules or node units are explained in this chapter.
When referring to the IM using the reference links below, replace the terms "Vnet/IP" with
"Vnet/IP-Upstream" and "SSC50" with "SSC57."
SEE
ALSO For more information about Vnet/IP-Upstream system hardware maintenance, refer to:
7., “Maintenance of ProSafe-RS Hardware” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)

<B3.8 Relay Board > B3-13
B3.8 Relay Board

This section explains the parts, cable connections and maintenance of the relay board for
ProSafe-RS.
SEE
ALSO For more information about relay board, refer to:
8., “Relay Board” in Safety Control Stations (Hardware) (IM 32Q06C10-31E)

CMPL B1-1
Customer Models SSC57S and

Maintenance SSC57D
Parts List Safety Control Unit
CMPL 32Q06D25-31E Duplexed Safety Control Unit
Model or
Item Part No. Qty Description
1 SSC57S — Safety Control Unit (with ISA standard G3)
SSC57D Duplexed Safety Control Unit (with ISA standard G3)
2 — — Node Fan Unit (wide range temperature type,
with fan unit and ISA standard G3)
Figure CMPL B1-1
CAUTION
• The Customer Maintenance Parts List (CMPL) is provided as a reference for ordering maintenance parts. Customers should not
assemble or disassemble the products by themselves using this CMPL, but should contact Yokogawa's sales agents for parts
replacement. YOKOGAWA assumes no liability to any party for damages caused through disassembly or assembly.
• Parts numbers on Parts Lists are subjected to change.
All Rights Reserved. Copyright © 2013, Yokogawa Electric Corporation CMPL 32Q06D25-31E
Subject to change without notice Printed in Japan 1st Edition : Oct. 2013 (YK)
2nd Edition : Apr. 2014 (YK)
CMPL B1-2
6 A
5
17
4
10
9
8
12
11
13 To A
16 15 14
Figure CMPL B1-2
All Rights Reserved. Copyright © 2013, Yokogawa Electric Corporation CMPL 32Q06D25-31E 2nd Edition : Apr.2014-00
CMPL B1-3
Qty
SSC57D
SSC57S
Model or Model
Item Part No. Description
1 - 1 1 CPU Node Unit
2 T9082QE 1 1 Cable Tray
3 Y9306LB 4 4 B.H.Screw, M3 × 6
4 SCP451 1 1 Processor Module with firmware (F1) revision number 19 or later
5 T9083UB 1 1 Cover
6 S9185FA 1 1 Battery Assembly

7 SCP451 1 Processor Module with firmware (F1) revision number 19 or later
8 T9083UB 1 Cover
9 S9185FA 1 Battery Assembly
10 T9083VB 1 Dummy Cover
11 Below 2 2 Power Supply Module

SPW481 for 100 to 120 V AC Power Supply
SPW482 for 220 to 240 V AC Power Supply
SPW484 for 24 V DC Power Supply
12 T9083UX 2 2 Cover
13 S9473FA 1 1 CPU Node External Interface Unit (with fan)

14 S9474FA 1 1 CPU Node External Interface Unit (without fan)
15 T9083TR 1 1 Plate
16 Y9306LE 2 2 B.H.Screw, M3 × 6
17 S9049PM 8 8 Insulating Bushing (accessory)
Figure CMPL B1-3
CMPL B1-4
Node Fan Unit
4 3
Model or
Item Part No. Qty Description
1 S9475FA 1 Node Fan Unit
2 S9528VK 2 Fuse
3 Below 2 Fan Power Module
S9159FA for 100 to 120 V and 220 to 240 V AC Power Supply Unit
S9160FA for 24 V DC Power Supply Unit
4 AIP602 2 Fan Assembly

5 S9049PM 4 Insulating Bushing (accessory)
Figure CMPL B1-4
Subject to change without notice Printed in Japan
<C. Engineering and maintenance> C-1
C. Engineering and maintenance

On an SENG PC with a license for FAST/TOOLS Integration Engineering Package, execute
the following engineering:
• Set up domain properties by using Domain Properties Setting Tool
• Perform engineering for the Narrowband mode in a system that operates in the Narrow-
band mode
• Create application logic by using Multi-Language Editor and download to SCS
• Define tag names using Tag Name Builder.
• Export tag name data to FAST/TOOLS
Execute a test when engineering ends.
Use the SCS Maintenance Support Tool also for the maintenance of FAST/TOOL Integration
configuration. The SCS Maintenance Support Tool can be used both in Vnet/IP-Upstream net-
work and Vnet/IP network in the same way. In addition, information of SCSU1 can be handled
in the same way as SCSP1. However, there is some limitation on the behaviors of the SCS
Maintenance Support Tool in the Narrowband mode.

<C1. Workflow for engineering of a FAST/TOOLS Integration system> C1-1
C1. Workflow for engineering of a FAST/

TOOLS Integration system
For a FAST/TOOL integrated system (environment), the workflow for ProSafe-RS engineering
is as follows:
1. Select the mode of the Vnet/IP-Upstream network suitable for the environment of your
system with the Domain Properties Setting Tool.
2. For a Narrowband mode system, define narrowband groups with the Message Cache
Tool.
3. Perform the basic engineering for SCSs.
4. When using function blocks for gas flow rate calculation in SCSU1, design data necessa-
ry for the gas flow rate calculation.
5. Create application logic by using the Multi-Language Editor. In that case, create external
communication function blocks or external communication function blocks with data re-
taining function for value setting from external equipment such as FAST/TOOLS or Mod-
bus master station, etc.
6. Use the Tag Name Builder to enter information on tag names etc. for the data to be ac-
cessed by FAST/TOOLS. When using function blocks for gas flow rate calculation, define
to associate them with external communication function blocks or external communication
function blocks with data retaining function.
7. Test the engineering result.
8. Export the data of the Tag Name Builder for FAST/TOOLS.

<C1.1 SCS Engineering works for FAST/TOOLS Integration> C1-2
C1.1 SCS Engineering works for FAST/TOOLS

Integration
On a system with FAST/TOOLS integrated, the SCS can also be used to monitor the safety of
the plant and control the plant based on individual requirements which require safety control,
therefore, follow the standard procedures for SCS basic engineering. However, additional en-
gineering is required when FAST/TOOLS is used to display an alarm or allow PRM to control
devices.
n System common switches

The status of SCS system common switch can be accessed from FAST/TOOLS by specifying
the element number (%SWXXXX) in FAST/TOOLS.
SEE
ALSO For more information about the accessible system common switches, refer to:
“● Common switches (Common switches for system)” in “■ Software inputs/outputs” in D1., “Integration
with CENTUM” in Safety Control Station Reference (IM 32Q03B10-31E)
n Process alarms
Process alarms should be managed by using the alarm management feature of FAST/
TOOLS.
n System alarms
System alarms should be confirmed on SENG using the SCS Maintenance Support Tool's Di-
agnostic Information window. The following alarms are effective for maintenance of devices:
• No. 4125 (I/O module channel error occurred)
• No. 4126 (Recovery from I/O module channel error)
SEE
ALSO For more information about alarm management on FAST/TOOLS, refer to:
The user's manual of FAST/TOOLS
n Interface with PRM

If you grant a license for the SOE OPC interface package to an SENG PC, PRM can obtain
all the SENG diagnostic information messages through the OPC server for SENG. Since
CENTUM HIS is not connected, those system alarms that would be generated on HIS in a
CENTUM system cannot be obtained (for example, system alarms regarding Vnet/IP-Up-
stream network are not obtainable).

<C1.2 Notes on engineering works> C1-3
C1.2 Notes on engineering works

When performing engineering works for FAST/TOOLS Integration configuration, the following
items must be noted: configuration for Vnet/IP-Upstream network in Standard mode is the
same as that for Vnet/IP network. Also, follow the notes on SCSP1 for SCSU1, because the
basic engineering works and notes for SCSU1 are shared with SCSP1.
n SCS Constant Builder

On SENG installed with FAST/TOOLS Integration Engineering Package (CHS5700), the fol-
lowing SCS process alarm settings in Communication tab can be ignored:
• Interval of Repeated Warning Alarms
• Alarm Notify Action When AOF Released
In Vnet/IP-Upstream, specify Synchronization with Vnet/IP time for Synchronous Mode in the
Communication tab.
If you use ESB optical bus repeater in SCSU1, as in SCSP1, set Yes for Optical ESB Bus
Repeater in the SCS tab and specify a distance for Maximum Extension Distance.
SEE
ALSO For more information about SCS Constant Builder, refer to:
3.1.3, “SCS Constants Builder” in Engineering Reference (IM 32Q04B10-31E)
n I/O parameter builder

When you use ESB optical bus repeater for SCSU1, configure the setting items for the node
in the same way as for SCSP1 in the I/O parameter builder.
SEE
ALSO For more information about setting method for I/O Parameter Builder node, refer to:
A4.3, “Common input/output setting items” in Safety Control Station Reference (IM 32Q03B10-31E)
n Considerations when using function blocks for FAST/TOOLS

Integration
On SENG installed with FAST/TOOLS Integration Engineering Package (CHS5700), the fol-
lowing SCS function blocks cannot be used. If used, errors will occur when you build the SCS
project.
• Override: OVR_B, OVR_I,OVR_R, OVR_IB, OVR_IR, GOV_B, GOV_IB
• Password: PASSWD
• Manual Operation: MOB_21, MOB_11, MOB_RS, MOA
In addition, the behaviors of SYS_NETST and SYS_SETTIME function blocks in Vnet/IP-Up-
stream network are the same as those of SYS_NETST and SYS_SETTIME in Vnet/IP net-
work.
SEE
ALSO For more information about actions of SYS_NETST function block in Vnet/IP, refer to:
C11.5, “SYS_NETST (control bus status indicator)” in Safety Control Station Reference (IM
32Q03B10-31E)
For more information about actions of SYS_SETTIME function block in Vnet/IP, refer to:
C11.3, “SYS_SETTIME (SCS time setting)” in Safety Control Station Reference (IM 32Q03B10-31E)

<C1.2 Notes on engineering works> C1-4
n Using Modbus slave communication module in FAST/TOOLS

Integration
The notes when using a communication module for Modbus slave communication in FAST/
TOOLS Integration are the same as for SCSP1. If the I/O nodes are extended at a distance of
more than 5 km by using an ESB optical bus repeater module, you cannot use a serial com-
munication module or Ethernet communication module for Modbus slave communication.
SEE
ALSO For more information about precautions for using Modbus slave communication module in SCSP1, refer to:
• “● Serial communication modules” in “■ Types of input/output modules” in A2., “SCS hardware” in
Safety Control Station Reference (IM 32Q03B10-31E)
• “● Ethernet communication module” in “■ Types of input/output modules” in A2., “SCS hardware” in
For more information about execution of sub system communication in FAST/TOOLS Integration, refer to:
“● Ethernet communication module” in “■ Types of input/output modules” in A2., “SCS hardware” in

<C1.3 Testing in a FAST/TOOLS integrated environment> C1-5
C1.3 Testing in a FAST/TOOLS integrated

environment
In a FAST/TOOLS integrated system, SCS simulator cannot be used. The actions can be
checked through logic simulation test or target test.
In the logic simulation test, the data buffering function and data retaining function are unavail-
able.
SEE
ALSO For more information about logic simulation test, refer to:
2., “Logic simulation test operations” in ProSafe-RS System Test Reference (IM 32Q04B30-31E)
For more information about target test, refer to:
4., “Target tests” in ProSafe-RS System Test Reference (IM 32Q04B30-31E)

<C2. Domain Properties Setting Tool> C2-1
C2. Domain Properties Setting Tool

Domain Properties Setting Tool can be used to define the properties of Vnet/IP-Upstream do-
mains for a project where ProSafe-RS is integrated with FAST/TOOLS and download them to
the Vnet/IP-Upstream domains.

<C2.1 Starting and exiting the tool> C2-2
C2.1 Starting and exiting the tool

The following figure shows the procedure for using the Domain Properties Setting Tool.
Obtain domain property settings from Check to see if the settings on the Domain Properties Setting Tool
stations and check them match the actual settings.
Set domain properties
Save the settings
Download the settings
Obtain domain property settings from Make sure that the new settings on the tool have been
stations and check them downloaded properly.
Figure C2.1-1 Procedure for using Domain Properties Setting Tool
n Start Domain Properties Setting Tool

1. From the Windows Start menu, choose [All Program] > [YOKOGAWA ProSafe] > [Domain
Properties Setting Tool].
[Domain Properties Setting Tool] appears on [YOKOGAWA ProSafe] menu only on an
SENG PC having a license for the FAST/TOOLS Integration Engineering Package
(CHS5700).
A folder that stores the RS project appears on the Browse for Folder dialog box.
The Browse for Folder dialog box appears with the path to the RS project selected at the
previous use of the tool.
Figure C2.1-2 Browse for Folder dialog box
2. Select an RS project folder.

If the RS project folder located on a remote computer is not shown on the Browse for
Folder dialog box, enter a path to the RS project folder.
If you choose a folder that is not an RS project folder and click the [OK] button, an error
message appears. In this case, choose an RS project folder in the dialog box.

3. Click the [OK] button.
And then Domain Properties Setting Tool will start.
n Components of Domain Properties Setting Tool window

This section describes the components of the Domain Properties Setting Tool.
List of domain properties
Domain Properties Setting Tool - [RSPjt:MYRSPJT File:DomainProperty.l]

File Load View
In-use Domain Time Group Network Mode SNTP Bus 1 SNTP Bus 2 Comment
□ 01 1 Wide-area
□ 02 1 Wide-area
□ 03 1 Wide-area
□ 04 1 Standard
□ 05 1 Standard
□ 06 1 Standard
□ 07 1 Standard
□ 08 1 Standard
□ 09 1 Standard
□ 10 1 Standard
□ 11 1 Standard
□ 12 1 Standard
□ 13 1 Standard
□ 14 1 Standard
□ 15 1 Standard
□ 16 1 Standard
Message
--- Error = 0 Warning = 0 ---
Ready Position: Line 1 Column 1
Message display area
Figure C2.1-3 Domain Properties Setting Tool
l Tool's menus and buttons

The following menus and buttons are provided on the menu bar and toolbar:
Table C2.1-1 Tool's menus and buttons

Menu Button Description
Specifies an RS project.
Use this button to choose another RS project for which you wish to
Open set domain properties. When you specify a new RS project, the cur-
rent window is closed and a new window opens for the specified RS
project.
Save Saves the settings you have made on the tool.

File
Print Prints the settings you have made on the tool.
Exit Do-
main
Properties - Exits the tool.
Setting
Tool

Table C2.1-1 Tool's menus and buttons (Table continued)
Menu Button Description
Download Downloads the settings of the selected domain.
Download
to All Do- Downloads the settings of all in-use domains.
Load
mains
Get Do-
main Sta- Acquires the domain property settings of all in-use domains.
tuses
l List of domain properties

The settings of all domains are listed. You can enter the settings on the list. The details of
each setting item will be explained in the next section.
l Message display area

Messages are displayed in this area when you execute downloading or uploading of the set-
tings.
n Exiting the tool

Choose [File] > [Exit] from menu bar or click the Close button at the upper-right corner of the
tool window to exit the tool.
If you are still editing a content, a dialog box will be displayed to prompt for saving the con-
tents. Save the changes if necessary and then exit the tool.

<C2.2 Setting domain properties> C2-5
C2.2 Setting domain properties

In the list of domain properties, first select the domain number checkbox of your domain, and
then define the properties of the domain.
n Setting items
This section describes the types and values of the settings for the Vnet/IP-Upstream domain
properties.
l In-Use
Specifies whether the domain is used or not.
You need to select the domain number checkbox of a domain for use. You can set the proper-
ties for the selected domain. By default, this checkbox is not selected.
l Time Group
Sets the time group (0 to 7) of the domain. If a number from 1 to 7 is set, this domain will
synchronize its clock with other domains of the same group. If 0 is set, the domain will only
synchronize the clocks within the domain.
SEE
ALSO For more information about Time Group, refer to:
“n Time groups” on page A1-11
l Network mode
Specifies the distance between stations and the bandwidth in a domain.
Specify either Standard, Wide-area, or Narrowband. The default setting is Standard.
IMPORTANT
If you change the network mode of a certain domain to Narrowband mode from other mode, a
confirmation message appears, asking you if it is alright to change the mode. If you click the
[OK] button, the mode of all other domains are changed to Narrowband mode. Likewise, if
you change from Narrowband mode to Standard mode for a certain domain, a confirmation
message appears, asking you if it is alright to change the mode. If you click the [OK] button,
the mode of all other domains are changed to Standard mode.
l SNTP Bus 1
Sets the IP address of the SNTP server connected to Bus 1.
To set the IP address, click the cell and enter the IP address in the form of "nnn.nnn.nnn.nnn."
If the entered address is beyond the range, the cell will turn red and an error message ap-
pears.
l SNTP Bus 2
Sets the IP address of the SNTP server connected to Bus 2.
To set the IP address, click the cell and enter the IP address in the form of "nnn.nnn.nnn.nnn."
If the entered address is beyond the range, the cell will turn red and an error message ap-
pears.
SEE
ALSO For more information about SNTP Server, refer to:
“n Connection and redundancy of SNTP server” on page A1-11

l Comment
You can enter a comment for each domain. A comment may be up to 32 alphanumeric char-
acters long.
Click the cell and then enter the comment.
n Saving domain properties

Saves all the settings of the domain properties.
Choose [File] > [Save] from menu bar or click the [Save] button on the toolbar. The properties
are saved for each RS project.
n Print domain properties

To print the set domain properties, select [File] > [Print]from the menu bar or click the [Print]
button on the toolbar. The properties of the domains whose [In-Use] check box is selected are
printed out.
Domain properties Mon Aug 22 10:20:26 2013
RS Project Path : \\PC1\RS-Projects\MYRSPJT
Domain Time Group Network Mode SNTP Bus 1 SNTP Bus 2 Comment
------------------------------------------------------------------------------------------------------------------------------------------
01 1 Wide-area Site-A1
02 1 Wide-area 192.168.2.220 192.168.130.220 Site-A2
03 1 Wide-area Site-A3
11 1 Standard Site-B1
Figure C2.2-1 Sample Printout of Wide-area mode and Standard mode

Domain properties Tue Dec 24 10:20:26 2013
RS Project Path : \\PC1\RS-Projects\MYRSPJT2
Domain Time Group Network Mode SNTP Bus 1 SNTP Bus 2 Comment
------------------------------------------------------------------------------------------------------------------------------------------
01 1 Narrowband Site-C1
02 1 Narrowband 192.168.2.220 192.168.130.220 Site-C2
Figure C2.2-2 Sample Printout of Narrowband mode

<C2.3 Downloading domain properties> C2-8
C2.3 Downloading domain properties

The defined domain properties need to be downloaded to the corresponding domains.
You can download the properties for an individual domain or for all the domains. You can
check the download result in the message display area. Before downloading, it is necessary
to save the domain properties.
n Downloading the properties of one domain

1. In the list of domain properties, choose the line of the domain for downloading. The line
will be highlighted.
(You cannot choose multiple domains.)
2. Choose [Load] > [Download] from menu bar or click the [Download] button on the toolbar.
3. Click [OK] in the confirmation dialog box for downloading. Downloading to the selected
domain starts.
If the properties have not yet been saved, a message will be displayed to prompt for sav-
ing the properties. Click [OK] to save and continue the downloading.
n Downloading the properties of all domains

1. Choose [Load] > [Download to All Domains] from the menu bar or click the [Download to
All Domains] button on the toolbar.
A confirmation dialog box appears prompting to download.
Downloading starts for all the domains with checkboxes on the "In-Use" column selected.
If the properties have not yet been saved, a message box will be displayed to prompt for
saving the properties. Click [OK] to save and continue the downloading.
n Download error
When starting download under the following situations, an error message appear in the mes-
sage display area and the download cannot continue.
Table C2.3-1 Error during download

Error messages Reason that cannot be downloaded and corrective actions
Domain Properties cannot be downloaded The domain for downloading is not a Vnet/IP domain.
because Domain <domain number> is not
Vnet/IP.
Wide-area cannot be supported because "Wide-area" is specified for the network mode but the domain
Domain <domain number> contains old contains a Vnet/IP device that does not support wide-area do-
firmware. main (i.e. the firmware revision is earlier than Rev.12).
Cannot download narrowband configura- The firmware of the Vnet/IP interface card of SENG does not
tion data because the firmware of the support the narrowband function (earlier than Rev.19), and the
Vnet/IP interface card is old. network mode for "Narrowband" is specified.
Cannot download narrowband configura- The Vnet driver of SENG does not support the narrowband
tion data because the V net driver is old. function (provided by the installation media earlier than Pro-
Safe-RS R3.02.10), and the network mode for "Narrowband" is
specified.
When Narrowband mode is specified, install the Vnet driver that
is bundled to the installation media of ProSafe-RS R3.02.10 or
later.

<C2.4 Obtaining actual domain property settings> C2-9
C2.4 Obtaining actual domain property settings

You can acquire the domain properties that are actually set in the domains and check if they
match the settings made on the tool.
n Procedure to obtain domain properties

1. Choose [Load] > [Get Domain Statuses] from the menu bar or click the [Get Domain Sta-
tuses] button on the toolbar.
A confirmation dialog box appears.
2. Click [OK] button in the Confirmation dialog box.
The property settings start to be acquired from all the domains for which "In-Use" check-
box is selected.
The acquired domain properties will be displayed in the message display area as follows:
Dom:01 Group:1 Network Mode:Standard SNTP Bus 1: SNTP Bus 2: WideAreaSupport:No NarrowbandSupport:-
Dom:02 Group:1 Network Mode:WideArea SNTP Bus 1:192.168.2.220 SNTP Bus 2:192.168.130.220 WideAreaSupport:Yes NarrowbandSupport:No
Figure C2.4-1 Example of acquired domain properties
(If narrowband mode is set)
Dom:01 Group:1 Network Mode:NarrowBand SNTP Bus 1: SNTP Bus 2: WideAreaSupport:Yes NarrowbandSupport:-
Dom:02 Group:1 Network Mode:NarrowBand SNTP Bus 1:192.168.2.220 SNTP Bus 2:192.168.130.220 WideAreaSupport:Yes NarrowbandSupport:Yes
Figure C2.4-2 Example of acquired domain properties
The following table describes the properties that are displayed:
Table C2.4-1 Description of displayed properties

Displayed property Description
Network Mode Standard Standard mode
Wide-area Wide-area mode
NarrowBand Narrowband mode
SNTP Bus 1 IP address of The IP address assigned to the SNTP server is displayed.
SNTP Bus 2 SNTP server
Blank The IP address of an SNTP server is not assigned.
WideAreaSupport Yes All the Vnet/IP stations in the domain support wide-area
domains.
No Some Vnet/IP stations in the domain do not support wide-
area domains.
NarrowbandSupport Yes The SENG running the Domain Properties Setting Tool
supports Narrowband mode.
No The SENG running the Domain Properties Setting Tool
does not support Narrowband mode.
- The SENG running the Domain Properties Setting Tool is
not located in the domain.

<C3. Defining narrowband groups> C3-1
C3. Defining narrowband groups

A set of SCSs that share the same narrowband communication paths is defined as a narrow-
band group. The following figure shows the position of a narrowband group definition.
FAST/TOOLS
SENG
Server
Vnet/IP-Upstream
L2SW L3SW L2SW
Narrowband group Narrowband group
Narrowband Narrowband
50 Mbps L3SW 10 Mbps
L2SW L2SW L2SW
SCS0101 SCS0102 SCS0201 SCS0202 SCS0301 SCS0302
Domain 1 Domain 2 Domain 3
Legend
Domain
Narrowband group
Figure C3-1 Position of a narrowband group definition
SCSs connected in a narrowband system must belong to a narrowband group. It is not possi-
ble to display the status or collect SOE events and diagnostic information massages from an
SCS that does not belong to a narrowband group.
In a narrowband group definition, the following items should be specified to restrict communi-
cation for each narrowband group in consideration of network load:
• SCS name included in the narrowband group
• Number of SCSs that can communicate per acquisition cycle of the message caching
service
• Number of SCSs that can communicate per display update cycle of the SCS Status Over-
view window.

<C3.1 Narrowband mode settings and precautions for narrowband group definition> C3-2
C3.1 Narrowband mode settings and

precautions for narrowband group
definition
The Narrowband mode can be configured by switching the network mode to the Narrowband
mode in the Domain Properties Setting Tool.
After the mode is switched to the Narrowband mode, the followings can be configured accord-
ing to the communication bandwidth of each narrowband group.
• Number of SCSs from which data are collected per acquisition cycle
• Number of SCSs that can communicate per display update cycle of the SCS Status Over-
view Window.
• Define narrowband groups and add, change, or delete SCSs
• Settings of automatic data acquisition from SCSs
• Pause and start of the data acquisition
Automatic data acquisition and background data acquisition are collectively referred to as
"data acquisition".
When there is not enough bandwidth, pause the data acquisition for some SCSs, and if suffi-
cient bandwidth becomes available, then you can perform offline download to a target SCS.
n Notes on definitions of a Narrowband group

Observe the following conditions when defining SENG and SCS in a Narrowband group in
Narrowband mode:
• SCSs that are connected to two or more narrowband lines can be included in one narrow-
band group. However, if the bandwidth differs in each narrowband line, configure the nar-
rowband group definition considering the slowest communication speed.
• Do not group SCSs that are routed through the same narrowband line into two or more
narrowband groups.
• When two Vnet/IP-Upstream domains are connected to one narrowband line, include the
SCSs of the two domains in one narrowband group.
• Do not define one Narrowband group in more than one SENG.
SEE
ALSO For more information about a sample narrowband group definitions, refer to:
“■ Examples of Narrowband Group Definition” in 9.3, “Defining narrowband groups” in Engineering
Guide (IM 32Q01C10-31E)

<C3.2 Display and operation of the Narrowband Group Definition window> C3-3
C3.2 Display and operation of the Narrowband

Group Definition window
A narrowband group is defined on the Narrowband Group Definition window. The Narrowband
Group Definition window can be displayed when the network mode is set to the Narrowband
mode. On the Narrowband Group Definition window, you can:
• Add, change, or delete a Narrowband group
• Add, change, or delete SCSs for each Narrowband group
• Enable or disable data acquisition
• Specify the number of SCSs that can communicate per acquisition cycle suitable for the
communication bandwidth of each narrowband
• Specify the number of SCSs that can communicate per display update cycle of the SCS
Status Overview Window
n Display items and menu items of the Narrowband Group Definition

window
You can start the Narrowband Group Definition window from Message Cache Tool. The fol-
lowing figure shows an example of the display of the Narrowband Group Definition window
immediately after it is started. The computer name of the SENG and the names of the narrow-
band groups are displayed.
• Narrowband group list pane
The computer name of the SENG and the names of the narrowband groups are dis-
played.
A list of the added narrowband group definitions is displayed in a tree view format. The
computer name of the SENG is displayed in the root section.
Up to 31 narrowband group definitions can be added.
There is no relation between the order of the narrowband groups displayed in the tree
and the order of acquisition by the message caching service.
The tree view cannot be collapsed.
• Narrowband group defined SCS list pane
All SCSs that are defined in the narrowband groups in the SENG are displayed.
Narrowband group list pane Narrowband group defined SCS list pane
Figure C3.2-1 Display example 1 of the Narrowband Group Definition window
When you click on a narrowband group name, the following panes appear in the right side of
the window:

• Number of SCSs setting pane
You can start or stop data acquisition and set the number of SCSs that can communicate
in each cycle of data acquisition by the message caching service, and the number of
SCSs that can communicate in each display update cycle of the SCS Status Overview
window. The setting items in this pane are applied only to the narrowband group selected
in the Narrowband group list pane.
• SCS list pane
You can add, change or delete the SCSs belonging to a narrowband group, and enable or
disable the automatic data acquisition.
The following figure shows an example of the display of the Narrowband Group Definition win-
dow when a narrowband group name is selected in the narrowband group list pane.
Number of SCSs setting pane
SCS list pane
Figure C3.2-2 Display example 2 of the Narrowband Group Definition window
n Working with narrowband group definitions

The Narrowband Group Definition window can be used to define narrowband groups. To add
an SCS to a narrowband group, the name of the group needs to be defined first. You can
check or change the defined settings.
You can change the defined group names. You can add, delete and save the group defini-
tions.
Definitions edited on the Narrowband Group Definition window are fixed when you save them.
l Starting the Narrowband Group Definition window

• From the Message Cache Tool, select [File] > [Setup] and click the [Narrowband Group
Definition] button.
The Narrowband Group Definition window appears. The computer name at the top of the
tree view is selected immediately after the window is displayed.
l Displaying a list of SCSs already defined in narrowband groups

• Click the computer name of the SENG in the Narrowband group list pane.
The right pane displays the list of SCSs already defined in narrowband groups.
l Adding a new narrowband group

You can add up to 31 narrowband groups.
To add a narrowband group, perform the following task:
1. From the menu bar, select [Narrowband] > [Add narrowband group].

A new narrowband group is added to the Narrowband group list pane. The name of the
added narrowband group is displayed as "Narrowband Group" by default in editing status.
2. Change the group name.
Each narrowband group name must be unique. If the group name is redundant, name en-
try is requested again. "*" is added to at the beginning of the added narrowband group
name.
l Deleting a narrowband group

To delete a narrowband group, perform the following task:
1. Click the narrowband group you want to delete on the Narrowband group list pane.
2. From the menu bar, select [Narrowband] > [Delete narrowband group].
3. Select [Yes] or [No].
When you select [Yes], the selected narrowband group is deleted. When you save the
narrowband group setting, data of the SCSs defined in the deleted narrowband group is
no longer collected.
When you select [No], the deletion process is stopped.
l Changing a narrowband group name

To change a narrowband group name displayed in the tree view of the Narrowband group list
pane, perform the following procedures:
1. Double-click the narrowband group name.
The narrowband group name becomes editable.
2. Change the name and then press the [Enter] key.
The change is applied.
TIP • Instead of pressing the [Enter] key, you can also shift the focus to another position to apply the change.
• You cannot change the name of the SENG in the tree view.
l Saving narrowband group definitions

If you try to close the Narrowband Group Definition window without saving a narrowband
group definitions, a confirmation dialog box for saving appears. "*" mark is displayed for the
narrowband group names for which settings are not saved. To save the settings, perform the
following task:
• From the menu bar, select [File] > [Save].
The settings are saved. "*" disappears from the narrowband group names for which set-
tings were not saved. The narrowband group names are sorted in alphabetical order.
After the settings are saved, data acquisition from the SCSs and display updating of the
status display window start.
l Finishing narrowband group definition

To close the Narrowband Group Definition window, perform the following task:
1. From the menu bar, select [File] > [Exit].
If the settings of a narrowband group definition are already saved, the Narrowband Group
Definition window is closed.
If you try to close the window without saving the narrowband group definition settings, a
confirmation dialog box that prompts to save or not to save the settings appears.
2. Click the button in the dialog box accordingly.
The Narrowband Group Definition window is closed.

l Checking the settings of a narrowband group

To check the settings of a narrowband group, perform the following task:
• Click the narrowband group you want to check on the Narrowband group list pane.
The information of the selected narrowband group appears on the right pane.

<C3.3 Editing SCSs that belong to a narrowband group> C3-7
C3.3 Editing SCSs that belong to a narrowband

group
When you add, edit or delete SCSs that belong to a narrowband group, the edited results are
reflected to the narrowband group definition when you save them.
n Adding SCSs to a narrowband group

To add an SCS to the narrowband group you selected on the Narrowband group list pane,
perform the following task:
1. In the SCS list pane, click a blank cell in the SCS name column.
This enables you to edit it.
2. Enter an SCS name in "SCSddss" format and then press the [Enter] key.
For "SCSddss", "dd" is a domain number, and "ss" is a station number.
An icon appears in the SCS name field. If the SCS has already been assigned to another
narrowband group, or the input format is wrong, an error occurs and re-entry is required.
n Deleting an SCS name that is defined in a narrowband group

To delete an SCS name defined in the narrowband group that you selected on the Narrow-
band group list pane, perform the following task:
1. Click the SCS name you want to delete in the SCS name column.
2. Clear the SCS name, and then click the [Enter] key.
The SCS is deleted. The SCS names on the rows under the deleted SCS name are sor-
ted by domain number and station number in ascending order.
TIP The SCS names are not sorted when you click the SCS name column title.
n Changing an SCS name that is defined in a narrowband group

To change an SCS name that is defined in the narrowband group you selected on the Narrow-
band group list pane, perform the following task:
1. Click the SCS name you want to change in the SCS name column of the SCS list pane.
2. Change the SCS name in "SCSddss" format and then press the [Enter] key.
For "SCSddss", "dd" is a domain number, and "ss" is a station number.
If it is overlapped with a SCS name that belongs to other narrowband group definition, or
the input format is wrong, an error occurs. Change it to a name that is not overlapped, or
the correct input format.

<C3.4 Setting the number of SCSs that can communicate> C3-8
C3.4 Setting the number of SCSs that can

communicate
You can set the number of SCSs that can communicate in one acquisition cycle or display up-
date cycle on the Number of SCS setting pane. When there are more SCSs to communicate
than the number set for the narrowband group, communication with the remaining SCSs is
performed in the second cycle or later. The types and methods of communication that can be
set are as follows:
• Number of SCSs from which data are collected by the message caching service
The default value of “0” is displayed for a new narrowband group. Set the number of
SCSs to communicate in each data acquisition cycle in the entry box of the Number of
SCSs for data acquisition.
• Number of SCSs for which the display on the SCS Status Overview window is updated in
each update cycle.
The default value of “0” is displayed for a new narrowband group. Set the number of
SCSs for which the display is updated in 1 second on the entry box of the Number of
SCSs for display update.

<C3.5 Quick reference table of the settings in the Narrowband Group Definition window> C3-9
C3.5 Quick reference table of the settings in the

Narrowband Group Definition window
The setting items and their setting contents and initial values of a narrowband group definition
are shown in the following table. The settings will take effect when you save them.
Table C3.5-1 List of the setting items of narrowband group definition

Setting item Setting charac- Initial value Mandatory Purpose and note
ter, setting val-
ue, setting
range
Narrowband group Up to 256 bytes Narrowband Yes Enter a name so that a user can
name including single- Group identify the narrowband group.
byte and double- Overlapped names cannot be de-
byte characters fined. You can use only characters
that can be used as a file name and
folder name on Windows Explorer.
Suspend data acquisi- Select or clear Clear Yes Use this option when bandwidth
tion must be secured such as the case
when you perform offline download.
You can start or stop background
data acquisition and automatic data
acquisition.
Number of SCSs for 0 to 100 0 Yes For the selected narrowband group,
data acquisition specify the number of SCSs from
which data are collected in one ac-
quisition cycle. Not collected if 0 is
specified.
Number of SCSs for 0 to 100 0 Yes For the selected narrowband group,
display update specify the number of SCSs for
which the status display is updated
in one display update cycle. Not up-
dated if 0 is specified.
SCS name Up to 7 bytes in Blank Yes Enter the SCS name that is to be
single-byte char- added to the selected narrowband
acters group in SCSddss format. dd is the
domain number. ss is the station
number.
Automatic data acquisi- Select or clear Selected No Select whether to perform automat-
tion ic acquisition. Automatic acquisition
is performed when selected. Auto-
matic acquisition is not performed
when clear.

<C3.6 Setting start and stop of data acquisition> C3-10
C3.6 Setting start and stop of data acquisition

You can set start or stop of data acquisition for the narrowband group selected on the Narrow-
band group list pane.
Stop data acquisition when you perform offline download or master database offline download
to an SCS that belongs to a narrowband group.
Even if the data acquisition is stopped, the display of the SCS status is updated.
n Pausing and starting data acquisition process

Automatic data acquisition and background data acquisition are collectively referred to as da-
ta acquisition. By changing and saving the setting of the Suspend data acquisition check box
on the Number of SCS setting pane of the Narrowband Group Definition window, you can
pause or restart communication for data acquisition.
To prevent forgetting to release the pause status, "(Pause)" appears on the title bar of certain
windows when you pause the data acquisition.
If you find "(Pause)" displayed on the title bar of a window, it means that there are some nar-
rowband groups where data acquisition is paused.
To start or stop data acquisition, perform the following task:
1. Select or clear the Suspend data acquisition check box on the Number of SCS setting
pane of the Narrowband Group Definition window.
When you select the check box, data acquisition is stopped. When you clear the check
box, data acquisition is resumed.
2. From the menu bar, select [File] > [Save].
The data acquisition is stopped or resumed.
While data acquisition is stopped, "(Pause)" is displayed on the title bar of the following
windows:
• Message Cache Tool
• SOE Viewer
• SCS Status Overview window
• SCS State Management window
• Diagnostic Information window
The following figure shows an example of the display of a window while data acquisition
is in the paused status.
Figure C3.6-1 Display example of the SCS State Management window in the "(Pause)" status
n Setting the SCS automatic data acquisition process

• In the Number of SCS setting pane of the Narrowband Group Definition window, select
the check box to the right of the name of the SCS for which you want to perform automat-
ic data acquisition.

<C3.6 Setting start and stop of data acquisition> C3-11
When you select the Automatic data acquisition check box on the Number of SCS setting
pane, automatic data acquisition is performed for all the SCSs in the SCS list pane.
When you clear the Automatic data acquisition check box on the Number of SCS setting
pane, all the check boxes to the right of the name of the SCSs in the SCS list pane are
cleared. Automatic data acquisition is not performed on them.

<C3.7 Procedure for offline download in the Narrowband mode> C3-12
C3.7 Procedure for offline download in the

Narrowband mode
When there is no free network bandwidth of 1.2 Mbps or more in the Narrowband mode, se-
cure the bandwidth by pausing the communication for data acquisition to perform offline
download to SCS through the narrowband network. Master database offline download is also
considered as offline download.
To perform offline download from an SENG in the Narrowband mode, perform the following
task:
1. Check the narrowband group where the SCS for offline download is defined.
2. Start the Message Cache Tool on SENG that uses the narrowband network checked in
step 1.
3. From the menu bar of the Message Cache Tool, select [File] > [Setup] and click on the
[Narrowband Group Definition] button.
The Narrowband Group Definition window appears.
4. Click the narrowband group name on the Narrowband group list pane, which was
checked in step 1, and then select the [Suspend data acquisition] check box on the Num-
ber of SCS setting pane.
5. From the menu bar of the Narrowband Group Definition window, select [File] > [Save]
The settings are saved and data acquisition is paused.
"(Pause)" is displayed at the title bar of certain windows on the SENG such as the Diag-
nostic Information window.
6. Perform steps 2 through 5 on all the SENG you checked in step 1.
7. On FAST/TOOLS, stop the periodic data acquisition from SCSs and SENGs of ProSafe-
RS. For how to stop the data acquisition, refer to the user's manual of FAST/TOOLS.
8. From the menu bar of the SCS Manager, select [Debug] > [Download] to perform offline
download.
The downloading starts.
When the offline download is completed, a dialog box appears , prompting you to resume
the paused data acquisition. Click the [OK] button.
10. On all SENG relevant to the narrowband group you checked in step 1, clear the Suspend
data acquisition check box on the Number of SCS setting pane of the Narrowband Group
Definition window, and then select [File] > [Save] on the menu bar.
The paused data acquisition is resumed. "(Pause)" on the window title bar disappears.

<C3.8 Collecting data from SCSs in a narrowband system in the same way as in the Standard and Wide-area
modes> C3-13
C3.8 Collecting data from SCSs in a

narrowband system in the same way as in
the Standard and Wide-area modes
When there is no narrowband line in the communication path between SENG and certain
SCSs connected on a Vnet/IP-Upstream network in the Narrowband mode, you can configure
the Narrowband Group Definition window so that SOE events and diagnostic information
messages are collected from the SCSs in the same way as in the Standard and Wide-area
modes.
To collect data from SCSs in the same way as in the Standard and Wide-area modes when
there is no narrowband line in the communication path to the SCSs, perform the following pro-
cedure.
1. Create narrowband group in the Narrowband group list pane of the Narrowband Group
Definition window.
2. Click the created narrowband group and, in the SCS list pane, add all SCSs whose com-
munication path is not a narrowband line to the narrowband group.
3. Select the Automatic data acquisition check box so that all SCSs are selected.
4. In the Number of SCS setting pane, enter the number of all SCSs that were added to the
narrowband group in step 2 in both the Number of SCSs for data acquisition box and the
Number of SCSs for display update box.

<C4. Defining tag names> C4-1
C4. Defining tag names

To allow FAST/TOOLS to access SCS application logic variables and function blocks, you
need to define tag names using the Tag Name Builder.

<C4.1 Overview of tag name definition> C4-2
C4.1 Overview of tag name definition

Use Tag Name Builder to define tag names for the variables and function blocks in the appli-
cation logic that need to be accessed from FAST/TOOLS. With a tag name defined, the func-
tion block or variable is associated with its corresponding mapping block or element, and be-
comes accessible from FAST/TOOLS by designating in the form "Tag name.Data item." The
procedure for defining tag names is as follows:
1. Define the application logic variables and function block instances in Dictionary View of
SCS Manager.
2. Define tag names and parameters in Tag Name Builder.
To start the Tag Name Builder, do the following: From the SCS Manager, click [Tools] >
[Engineering] to start the Engineering Launcher, and select [Tag Name Builder] from the
menu.
3. Execute a build on SCS Manager to generate SCS databases and download them to
SCS.
4. In order to pass the contents defined on Tag Name Builder to FAST/TOOLS, export the
contents defined on Tag Name Builder into a CSV file and import this CSV file into FAST/
TOOLS.
IMPORTANT
Changes made to the definitions for a tag name that is already imported will not be reflected
in FAST/TOOLS by the above mentioned procedure. To change the definitions for already im-
ported tag names, you need to work on both Tag Name Builder and FAST/TOOLS.
SEE
ALSO For more information about variables whose tag names you can define and the detail of definition items, refer
to:
“n Settings of the Tag Name Builder” on page C4-4
For more information about mapping blocks/elements, refer to:
C9., “External communication function blocks” in Safety Control Station Reference (IM 32Q03B10-31E)
n Window of Tag Name Builder

The following figure shows the Tag Name Builder main window:

Title bar Menu bar Tool bar
Tag Name Builder - [Pjt:SCS1020 File:TAG.edf]

File Edit View Tool Window
ECW_R
Variable Name BOOL/ECW_B DINT/REAL/ECW_I/ECW_R ANLGI VEL ANN/ANN_FUP IO_RE

ABS001_Q@Select1FB Variable Name Tag Name Unit Level
ABS002_Q@Select1FB
ABS001_IN@Select1FBD ABS001_IN % 4 Gener
ACOS_Q@Interference
ANLGI001_HYS@HISIF ABS002_IN@Select1FBD % 4 Gener
ANLGI001_IN@HISIFFB ACOS_IN@InterferenceF % 4 Gener
ANLGI001_LL@HISIFFB
ANLGI001_HH@HISIFFB % 4 Gener
ANLGI001_OUT@HISIF
ANLGI001_PH@HISIFF % 4 Gener
ANLGI001_PL@HISIFFB
ANLGI001_SH@HISIFF
ANLGI002_HH@HISIFF
Message
Ready Position: Line 5 Column 1 Change
Status bar Data menu area Workspace Message display area
Figure C4.1-1 Main window of the Tag Name Builder
You can register a variable name in Tag Name Builder by dragging the variable name from
Dictionary View and dropping it into a variable name field in Tag Name Builder. When multiple
variable names are dragged and dropped, the variable names are registered in multiple varia-
ble fields starting from the top field. If a variable name is already registered in the variable
name field, the variable name field is overwritten.

ProSafe-RS - [SCS0101 (*Binding error management*) - Dictionary - Variables]
File Edit Debug Tools Options Window Help
ComplexTest
Variables
Name Alias Type
Main (Config1)
BoundVariable UserAcknowledge BOOL
BindingError OUT01 BOOL
Any Group InitBindText BOOL
InitOK BOOL
All variabl
OK1 BOOL
Global var
OK3 BOOL
Addition (
OK2 BOOL
Main (*si
ManualReset OK1 BOOL
Binding Te OKStart OK3 BOOL
ComplexT OKStop OK2 BOOL
Test (Config1) CopyOfval31 DINT
CopyOBesAdd1 DINT
SENG001
Tag Name Builder - [ Pjt:SCS0101 File:Tag.edf ]

File Edit View Tools Window
Variable Name BOOL/ECW_B DINT/ECW_I/REAL/ECW_R IO_REAL ANN/ANN_FUP
AV_NR@An Variable Name Tag Name Type Tag Commen

NR1@Analo
NR2@Analo T101 ECW_B
NR3@Analo OK1 BOOL
Permission
OK2 BOOL
OK3 BOOL
Message
Ready Position: Line 1 Column 3
Figure C4.1-2 Dragging and dropping from the Dictionary View
n Settings of the Tag Name Builder

The following describes the types of variables for which you can define a tag name in Tag
Name Builder. The setting items in Tag Name Builder differ for each variable type.
Table C4.1-1 Variable types for which you can define a tag name in Tag Name Builder.
Type Description
BOOL BOOL type variables

Table C4.1-1 Variable types for which you can define a tag name in Tag Name Builder. (Table continued)
Type Description
DINT Integer type variables
REAL Real type variables
ANLG_S Instance of an analog (with status) input function block
ANLGI Instance of an analog input function block
VEL Instance of a rate of change alarm function block
ANN Instance of an annunciator function block
ANN_FUP Instance of a first-up alarm annunciator
IO_REAL Real type analog input variable
IO_BOOL BOOL type tangent point I/O variable
ECW_B Instance (of BOOL type) of external communication function block
ECW_I Instance (of integer type) of external communication function block
ECW_R Instance (of real type) of an external communication function block
SCI_B Instance of subsystem communication function block (BOOL type input variable)
SCO_B Instance of subsystem communication function block (BOOL type output variable)
SCI_I Instance of subsystem communication function block (integer type input variable)
SCO_I Instance of subsystem communication function block (integer type output variable)
SCI_R Instance of subsystem communication function block (real type input variable)
SCO_R Instance of subsystem communication function block (real type output variable)
AGA_3 Gas flow rate calculation function block (AGA Report No. 3 calculation function)
AGA_7 Gas flow rate calculation function block (AGA Report No. 7 calculation function)
AGA_R Gas flow rate calculation function block (Reporting function)
ECWR_B Instance variable (of BOOL type) of an external communication function block with data retain-
ing function.
ECWR_I Instance variable (of integer type) of an external communication function block with data re-
taining function.
ECWR_R Instance variable (of real type) of an external communication function block with data retaining
function.
The following describes the setting items of Tag Name Builder and whether to modify each
item online. In addition to the setting items, there are reference items for checking the values
in Dictionary View or I/O Wiring View. The reference items cannot be changed in Tag Name
Builder. Note that all the items can be printed.
Table C4.1-2 Setting items

Online
modifi-
Item Remarks
cation
(*1)
Variable Name Yes -
Displayed only in the ANN/ANN_FUP tab.
Element Name No (For SCSP2: %AN0001 to %AN2000, other-
wise: %AN0001 to %AN1000)
The variable types defined on the Dictionary
Type No View are displayed. This is not displayed when
the tab has only one type name.

Table C4.1-2 Setting items (Table continued)
Online
modifi-
Item Remarks
cation
(*1)
The variable comments defined in the Diction-
Comment No
ary View are displayed.
Displays the wiring position for a channel wired
Wiring Position No with the variable in I/O Wiring View. It is dis-
played only for an I/O variable.
ANN and ANN_FUP can be accessed by speci-
fying an element name without specifying a tag
Tag Name Yes
name. When a tag name is not specified, Tag
Name is printed in blank.
Tag Comment Yes -
Annunciator Message Yes -
Low Limit Yes -
High Limit Yes -
Unit Yes -
AGA FB Instance Name (AGA FB instance Instance name of AGA FB (AGA_3, AGA_7,
Yes
name)(*2) AGA_R) defined in SCS Manager.
AGA FB Type (*2) No AGA FB type name
AGA Parameter Name (*2) Yes AGA parameter name
Level (function constraint level) (*3) No -
Label (label format) Yes -
Button 1 (color of Button 1) Yes -
Button 2 (color of Button 2) Yes -
Button Top (color of Button top) Yes -
Button Bottom (color of Button bottom) Yes -
Switch Position Label Yes -
*1: Yes: Online modification can be available.

No: N/A
*2: Displayed only for SCSU1.
*3: This is grayed out and cannot be set.
The following describes whether or not the advanced setting items of Tag Name Builder can
be modified online. Select [View] > [Detailed Setting Items] on the menu bar to display the ad-
vanced setting items.
Table C4.1-3 Advanced setting items

Online
modifi-
Item Remarks
cation
(*1)
Tag Mark (*2) No -
Alarm Level Yes Specify 1 to 16 level.
Upper Window (*2) No -
Help (help number) (*2) No -
Scale Reverse Yes -
Scale-division Yes -
Double Authentication Yes -

Table C4.1-3 Advanced setting items (Table continued)
Online
modifi-
Item Remarks
cation
(*1)
Alarm in Overriding Yes -
Answer back Alarm (Answer back error alarm) Yes -
Password ON Alarm Yes -
Output High Limit (%) Yes -
Output Low Limit (%) Yes -
Output Scale High Limit (%) Yes -
Output Scale Low Limit (%) Yes -
Upper Equipment Name Yes -
*1: Yes: Online modification can be available.

No: N/A
*2: This is grayed out and cannot be set.
This section describes the items you need to set in Tag Name Builder in FAST/TOOLS Inte-
gration configuration. The following table describes the items on Tag Name Builder that are
valid in FAST/TOOLS Integration configuration. Other items are displayed in gray and cannot
be set.
A Tag Name Builder window consists of tab pages grouped by variable types shown in the
following table.
The settings you have made can be printed out by self-documentation.
Table C4.1-4 Variable types and items on the Tag Name Builder
Variable type(*1)
DINT
REAL
BOOL SCI_I
Item ECW_I ANN AGA_3
ECW_B ANLG_ IO_RE- IO_BOO SCI_B SCO_I
ECW_R ANN_F AGA_7
ECWR_ S AL L SCO_B SCI_R
ECWR_I UP AGA_R
B SCO_R
ECWR_
R
Variable Name Yes Yes Yes Yes Yes Yes Yes Yes Yes
Element Name
- - - No - - - - Yes
(*2)
Type (*3) No No - - - - No No Yes
Comment (*4) No No No No No No No No -
Tag Name Yes Yes Yes Yes (*5) Yes Yes Yes Yes -
Tag Comment Yes Yes Yes - Yes Yes Yes Yes -
Annunciator Mes-
- - - Yes - - - - -
sage
Low Limit - - Yes - - - - - -
High Limit - - Yes - - - - - -
Unit - Yes Yes - Yes - - Yes -
AGA FB Instance
Yes (*6) Yes (*6) - - - - Yes (*6) Yes (*6) -
Name
AGA Parameter
Yes (*6) Yes (*6) - - - - Yes (*6) Yes (*6) -
Name
*1: Yes: Settable

No: Read-only
-: Not available

*2: The following element name is displayed only for the ANN/ANN_FUP tab:
For SCSP2: %AN0001 to %AN2000, otherwise: %AN0001 to %AN1000
*3: The variable types defined on the Dictionary View are displayed. This item is not displayed in the tabs for a single variable
type.
*4: The variable comments defined on the Dictionary View are displayed.
*5: Tag name specification is optional. FAST/TOOLS can access ANN or ANN_FUP by using element names instead of tag
names; For SCSP1: %AN0001 to %AN1000; otherwise: %AN0001 to %AN2000.
*6: Displayed only for SCSU1.
SEE
ALSO For more information about the mapping blocks and mapping elements of FAST/TOOLS, refer to:
Appendix 3., “Mapping blocks and mapping elements for FAST/TOOLS Integration” on page App.3-1
l Variable Name
To assign a tag name to a function block instance, enter the [instance name] as the variable
name. From among the variables created in SCS Manager, specify the variable name you
want to assign a tag name. A tag name can be defined regardless of the scope of the varia-
ble.
In case of a local variable, enter a scope name after "@."
In case of an internal variable of a user-defined function block, assign an instance name using
Dictionary View of SCS Manager. The variable name is specified in the format of "[Instance
Name].[Internal Variable Name]." Up to two nests are permitted in each variable to which a
tag name is assigned.
Table C4.1-5 Examples of variable specification

Variable name (*1) Scope Description
VAR1 Global Global variable
VAR2@PROG1 PROG1 Local variable of PROG1 function
FB01.VAR3 Global Internal variable VAR3 of user-defined function block instance
FB01
FB01.VAR3@PROG1 PROG1 Internal variable VAR3 of user-defined function block instance
FB01 defined locally in PROG1 function
FB01.FB2.VAR3 Global Internal variable VAR3 of user-defined function block instance
FB2, which is used in user-defined function block instance FB01
(maximum limit of function block nesting)
*1: The variable name can contain up to 69 single-byte characters. Tag Name Builder also checks the following items:
• The variable name consists only of alphanumeric characters and "@," "." or "_". If any other character is used, an error will
occur.
• The variable name begins with an alphabetic character or "_"; otherwise, an error will occur.
• Three or more nests in a variable will result in an error. The variables "FB01.VAR3" and "FB01.VAR3@PROG1" have one
nest, while "FB01.FB2.VAR3" has two nests.
l Tag Name
A name used to access each application logic variable from FAST/TOOLS. A tag name can
contain up to 16 single-byte alphanumeric characters including "_" and "-". Note that tag
names cannot begin with "_" or "-". All characters are converted to uppercase as they are en-
tered. Tag names must be unique within the same station (SCS).
l Tag Comment
A comment assigned to a tag name. It can be defined within 24 single-byte characters.
l Annunciator Message
A message notifying the process error. You can define any string within 80 single-byte charac-
ters.
Default: None

l Unit
A symbol indicating the engineering unit of data such as flow rate and pressure. A unit can be
defined within 6 single-byte characters .
Default: %
l Low Limit
A low limit (SL) is the lowest point of engineering data scale. It can be defined using up to
seven digits including a sign and decimal point. This setting is referenced by FAST/TOOLS
only for display purposes and not used in calculation or alarm processing of the SCS. Enter
the same value as the low limit set on Multi-Language Editor, although a different value can
be set.
Default: 0.0
l High Limit
A high limit (SH) is the highest point of engineering data scale. It can be defined using up to
seven digits including a sign and decimal point. This setting is referenced by FAST/TOOLS
only for display purposes and not used in calculation or alarm processing of the SCS. Enter
the same value as the "High limit" set on Multi-Language Editor, although a different value can
be set.
Default: 100.0
TIP When a builder file (*.edf), a file saved with another name (*.sva), or a CSV file (*.csv) is imported on Tag
Name Builder, the setting items that cannot be used on FAST/TOOLS are not imported and the default values
will be used.
l AGA FB Instance Name

Set an instance of AGA FB (AGA_3, AGA_7, AGA_R) defined with the SCS Manager. Allo-
cate a variable of the row to a configured AGA FB instance parameter. Use an AGA FB pa-
rameter name item to name the parameter that is allocated.
Default: Blank
Can contain up to 69 single-byte characters. In addition, Tag Name Builder also checks the
following items:
• The instance name consists only of alphanumeric characters and "@", "." or "_". Other-
wise, an error will occur.
• The instance name begins with an alphabetic character or "_"; otherwise, an error will oc-
cur.
• Two nests or more will result in an error.
In addition, an error occurs when saving the AGA parameter if the AGA Parameter Name is
set without AGA FB Instance Name specified.
l AGA Parameter Name

Specify the parameter name of AGA FB instance to which a variable will be allocated.
Default: Blank
The type of the parameter name to be allocated depends on the type of AGA FB that is set
with AGA FB Instance Name and the type of a variable to be allocated.
An error occurs when saving the AGA parameter if AGA FB Instance Name is specified but
the parameter name that corresponds to the type of AGA FB or type of a variable to be alloca-
ted is not selected.

l Tag name interface for FAST/TOOLS

If you define a tag name using Tag Name Builder for a function block or variable of SCS that
is accessible from FAST/TOOLS, a mapping block or mapping element is created for it.
FAST/TOOLS can read and write data through the tag name interface. However, some map-
ping blocks and mapping elements are read-only.
An external communication function block is used to specify a parameter on the FAST/TOOLS
graphic window in the AGA gas flow rate calculation. An external communication function
block with the Data retaining function can be used alternatively. Use the Tag Name Builder to
build the relationship of an external communication function block used to enter a value with
AGA function block parameters.
l List of mapping blocks/elements

FAST/TOOLS can automatically import the tag names defined on Tag Name Builder. Howev-
er, some mapping blocks/elements are not supported by FAST/TOOLS, and the tag names for
unsupported mapping blocks/elements cannot be imported. Even if the tag names are not im-
ported, their data can be accessed by FAST/TOOLS using the tag definition engineering fea-
ture of FAST/TOOLS.
SEE
ALSO For more information about the mapping blocks/elements that can be accessed by FAST/TOOLS, refer to:
“n Mapping blocks/elements that can be accessed by FAST/TOOLS” on page App.3-1

<C4.2 Definition of the tag name at the gas flow rate calculation> C4-11
C4.2 Definition of the tag name at the gas flow

rate calculation
For parameters used for the gas flow rate calculation to be entered from a FAST/TOOLS op-
erator interface, enter a tag name in a parameter that is expected to be handled by ProSafe-
RS Tag Name Builder. To use an FB for the gas flow rate calculation, use the Tag Name
Builder to associate the FB for the gas flow rate calculation with an external communication
FB or an external communication function block with data retaining function.
This section defines the tag name at the gas flow rate calculation.
n Relation of variables that set AGA parameter and a value

In the application logic of SCS, bind a variable to receive a value from an outside device such
as FAST/TOOLS with a parameter of AGA FB instance to set a value through a variable . In
the Tag Name Builder, give a name to the variable and then specify the parameter name the
AGA FB instance to be set a value from the variable.
The type of AGA parameter name that can set the value through the variable is different ac-
cording to variable type used to set the type and the value of AGA FB set by the AGA FB
instance name.
The following table shows the type of AGA parameter name that can set a value through vari-
able:
Table C4.2-1 Type of AGA parameter name that can set value through variable
Type of Variable type to set a Type of AGA parameter name that Example of AGA param-
AGA FB value (*1) can be set eter name
AGA_3 BOOL, ECW_B, EXEC EXEC
ECWR_B, SCI_B
SET SET
DINT, ECW_I, Parameter name of structure AGA8_METHOD_SE-
ECWR_I,SCI_I AGA_3_PARAM (DINT type) LECT
REAL, ECW_R, Parameter name of structure FIXED_ATMPRESS
ECWR_R, SCI_R AGA_3_PARAM (REAL type)
Parameter name of structure METHANE
AGA_COMPOSITION (REAL type)
AGA_7 BOOL, ECW_B, EXEC EXEC
ECWR_B, SCI_B
SET SET
DINT, ECW_I, Parameter name of structure FLOW_CAL_SELECT
ECWR_I,SCI_I AGA_7_PARAM (DINT type)
REAL, ECW_R, Parameter name of structure FIXED_ATMPRESS
ECWR_R, SCI_R AGA_7_PARAM (REAL type)
Parameter name of structure METHANE
AGA_COMPOSITION (REAL type)
AGA_R BOOL, ECW_B, EXEC EXEC
ECWR_B, SCI_B
SET SET
Parameter name of structure INIT_CURH_DATA_Q
AGA_R_PARAM (BOOL type)
DINT, ECW_I, Parameter name of structure CONTRACT_HOUR
ECWR_I,SCI_I AGA_R_PARAM (DINTtype)
*1: BOOL, DINT, REAL: For monitor

ECW_B, ECWR_B, ECW_I, ECWR_I, ECW_R, ECWR_R: Access by FAST/TOOLS
SCI_B, SCI_I, SCI_R: For access from Modbus
If AGA FB instance name is set without selecting a parameter name that is appropriate to the
combination of variable types used for AGA FB type and the value setting, an error occurs.

n Sample tag name definition when calculating gas flow rate

When you calculate a gas flow rate, associate Gas flow rate calculation FB with External com-
munication FB, or Gas flow rate calculation FB with External communication FB with data re-
taining function. Also, use Tag Name Builder to specify AGA FB Instance Name, AGA Param-
eter Name, External communication FB Instance Name, and tag names.
l Example of the application logic

The following figure shows the example of application logic that uses AGA_3. The argument
in the halftone screen of the gray in the figure is an argument of the structure type.
AGA3_EXEC_INST
ECW_B
AGA3_EXEC
ANLG_S AGA3_INST AGAR_INST

AGA_3 AGA_R
SP IN OUT
:
STS EXEC EXEQ EXEC
:
SP CDAT CDAT
ANLG_S SP_S NOFL NOFL
DP IN OUT DP ERCD SET

:
STS DP_S CDT2 PARA
: T PARO
ANLG_S T_S CMPO
T IN OUT
:
STS
:
AGA3_SET_INST
ECWR_B
AGA3_SET SET
User Define PARA

AGA3_SP_MNT_INST Function Block
ECWR_R COMP
AGA3_PARA
CP_S
:
ECWR_R
User Define
AGA3_METHANE_INST Function Block
ECWR_R
VAR_COMP
:
ECWR_R
Figure C4.2-1 Example of the application logic of AGA_3

TIP Debug the application using the gas flow rate calculation function with a logic simulator or a SCS real ma-
chine.
The value of the parameter cannot be set to ECW_*/ECWR_* by the tag name interface, if there is no debug-
ging environment under which FAST/TOOLS is combined with a SCS real machine. In this case, set a value
in the following way.
• Set an appropriate value to the initial value of ECWR_*, and perform off-line download
• Change variable value at the output destination of ECW_*/ECWR_* by debugging function or the forcing
function of Multi-Language Editor.
Place the variable between ECW_*/ECWR_* and AGA_* so that forcing can change the output destination of
ECW_*/ECWR_*. When ECW_*/ECWR_* is connected to EXEC or SET directly, a value cannot be changed
during debugging.
SEE
ALSO For more information about sample application logic of gas flow rate calculation, refer to:
“■ Examples of Gas Flow Rate Calculation Application Logic” in 9.6, “Gas Flow Rate Calculation Func-
tion” in Engineering Guide (IM 32Q01C10-31E)
l Example of defining the Tag Name Builder

The example of entry to the Tag Name Builder in the application logic of AGA_3 is as follows:
Example of defining EXEC and SET in the Tag Name Builder
• Instance name of AGA_3 that is a target for external communication FB with the data re-
taining function shown in the following table: AGA3_INST
• Parameter name of AGA_3 that sets a value from FAST/TOOLS through external com-
munication FB with data retaining function: EXEC, SET
Table C4.2-2 External communication with data retaining function for value setting
Type Variable name Tag name
ECW_B AGA3_EXEC_INST EXEC
ECWR_B AGA3_SET_INST SET
Tag Name Builder
AGA Parameter Name BOOL/ECW_B/ECWR_B ... AGA_3/AGA_7/AGA_R

EXEC Variable Name Tag Name Type AGA FB name AGA Parameter Name
AGA8_METHOD_SELECT AGA3_EXEC_INST EXEC ECW_B AGA3_INST EXEC
ATMPRESS_CAL_SELECT
AGA3_SET_INST SET ECWR_B AGA3_INST SET
SG_CAL_SELECT
COMP_NORMALIZE_SELECT
DEFAULT_TEMP_SELECT
ENERGY_CAL_SELECT
HV_Z_SELECT
SP_SELECT
UNIT_SELECT
UNIT_CONV_SELECT
COMP_INPUT_SELECT
INPUT_PROCESS_SELECT
CONF_TIMER
FIXED_ATMPRESS
REF_TMP
DP_CUTOFF
DEFAULT_TEMP
Figure C4.2-2 Example of defining the Tag Name Builder (EXEC, SET)
Example of defining SP_MNT and METHANE in the Tag Name Builder

• Instance name of AGA_3 that is a target for external communication FB with the data re-
taining function shown in the following table: AGA3_INST
• Parameter name of AGA_3 that sets a value from FAST/TOOLS through external com-
munication FB with data retaining function: SP_MNT, METHAN
Table C4.2-3 External communication with data retaining function for value setting
Type Variable name Tag name
ECWR_I AGA3_SP_MNT_INST SP_MNT
ECWR_R AGA3_METHANE_INST METHANE
Tag Name Builder
AGA Parameter Name BOOL/... REAL/DINT/ECW_I/ECW_R/ECWR_I/ECWR_R AGA_3/AGA_7/AGA_R
AGA8_METHOD_SELECT Variable Name Tag Name Type AGA FB name AGA Parameter Name
ATMPRESS_CAL_SELECT AGA3_SP_MNT_INST
SP_MNT ECWR_I AGA3_INST SP_MNT
SG_CAL_SELECT AGA3_METHANE_INST
METHANE ECWR_R AGA3_INST METHANE
COMP_NORMALIZE_SELECT
DEFAULT_TEMP_SELECT
ENERGY_CAL_SELECT
HV_Z_SELECT
SP_SELECT
UNIT_SELECT
COMP_INPUT_SELECT
SP_MNT
DP_MNT
T_MNT
PIPE_MATERIAL
ORIFICE_MATERIAL
TAP_LOCATION
WET_ANALYSIS
Figure C4.2-3 Example of defining the Tag Name Builder (SP_MNT, METHANE)
TIP • SP_MNT is one of parameter names of AGA_3_PARAM structure. In the example of the application log-
ic, it is included in the argument named PARA of AGA_3 FB.
• METHANE is one of parameter names of AGA_COMPOSITION structure. In the example of the applica-
tion logic, it is included in the argument named COMP of AGA_3 FB

<C5. Maintenance of FAST/TOOLS integrated system (environment)> C5-1
C5. Maintenance of FAST/TOOLS

integrated system (environment)
In the FAST/TOOLS integrated system(environment) the SCS maintenance support tool is al-
so used for the maintenance of an SCS including confirmation of status displays and diagnos-
tic information messages. SCS maintenance support tool handles the Vnet/IP network and
the Vnet/IP-Upstream network the same way. However, the behavior of the SCS maintenance
support tool is restricted due to the narrow communication bandwidth in Narrowband mode of
the Vnet/IP-Upstream network.

<C5.1 Maintenance in Vnet/IP-Upstream network> C5-2
C5.1 Maintenance in Vnet/IP-Upstream network

Even when you connect SCSU1 or SCSP1 to Vnet/IP-Upstream network, you maintain it with
the SCS Maintenance Support Tool. In SCS Maintenance Support Tool, there are places
where Vnet/IP-Upstream network is displayed as Vnet/IP.
SEE
ALSO For more information about SCS Maintenance Support Tool, refer to:
3., “SCS Maintenance Support Tool” in Utilities and Maintenance Reference (IM 32Q04B20-31E)
n SCS Maintenance Support Tool

When you use SCS Maintenance Support Tool in FAST/TOOLS integrated system (environ-
ment), bear the following in mind:
l System Status List View in SCS Status Overview window

In SCS Status Overview window, Vnet/IP is displayed in the label of the icon that indicates the
control bus status of the SENG.
SEE
ALSO For more information about SCS Status Overview window, refer to:
“● SCS Status Overview Window, Diagnostic Information Window, Setup Tool” in “■ Security of SCS
Maintenance Support Tool” in 3., “SCS Maintenance Support Tool” in Utilities and Maintenance Refer-
ence (IM 32Q04B20-31E)
l SCS State Management window

In SCS Status Management window, Vnet/IP is displayed in the label of the icon that indicates
the status of the control bus.
SEE
ALSO For more information about SCS State Management window, refer to:
“■ SCS Status Overview Window Structure” in 3.1.1, “SCS Status Overview” in Utilities and Maintenance
Reference (IM 32Q04B20-31E)
l Component/Module list view in SCS State Management window

If you select a CPU node in SCS State Management window, the status of the CPU node is
displayed in Component/Module list view. The content of Time Sync will be displayed even if
the CPU node is SSC57S/SSC57D. It will be displayed as Vnet/IP when the CPU node is not
synchronized with the time of the SNTP server, but as SNTP otherwise.
SEE
ALSO For more information about component/Module list view in SCS State Management window, refer to:
“● Lower Part of List View when a CPU Node is Selected” in “■ Lower Part of Component/Module List
View” in 3.1.2, “Management of SCS States” in Utilities and Maintenance Reference (IM 32Q04B20-31E)
n Set time from SENG

Network time in the Vnet/IP-Upstream network can be changed from Adjust Time dialog box.
Follow the procedure to call the Adjust Time dialog box:
1. Call the SCS Status Overview window from the SENG.
2. Click the Time Setup icon on the toolbar.
The Adjust Time dialog box appears.
When you set the time, the time on the Vnet/IP station in the same time group is also
changed. However, if an SNTP server exists in the time group and the SNTP server is
synchronized with the standard time, setting time from the SENG is ignored.

<C5.2 Procedures and precautions for adding a station or domain> C5-3
C5.2 Procedures and precautions for adding a

station or domain
This section describes the procedure when adding a station to an existing Vnet/IP-Upstream
network and the procedure and precautions when adding a domain to Vnet/IP-Upstream net-
work.
n Procedures and precautions for adding a Vnet/IP station

When adding a station to Vnet/IP-Upstream network, follow the following procedure:
WARNING
• Before you add a station, make sure that there are no duplicate station addresses.
• Turn off the power of the additional station before you connect the cables.
l Case 1: When using existing Layer 2 switches (ports are available on

existing Layer 2 switches)
1. On an SENG, select the project of a running SCS and call up an SCS status display win-
dow (either SCS Status Overview or SCS State Management) of the SCS Maintenance
Support Tool. In the SCS status display window, check that both buses are normal.
2. Make sure that the additional station is not powered on.
3. Connect the BUS1 port of the additional station to the Layer 2 switch for BUS1 with a ca-
ble. If the port on the Layer 2 switch is disabled, enable the port.
4. In the SCS status display window, check that both buses are normal.
5. Connect the BUS2 port of the additional station to the Layer 2 switch for BUS2 with a ca-
ble. If the port on the Layer 2 switch is disabled, enable the port.
7. Turn on the power of the additional station.
TIP Alternatively, you can add a station to Layer 3 switches directly instead of Layer 2 switches.
l Case 2: When you need to add Layer 2 switches (no ports are available on
Firstly, carry out steps 1 to 11 as shown below to add Layer 2 switches for BUS1 and BUS2.
Next, carry out the procedure for "Case 1" above to add a station.
2. Disconnect the cable between any one of the existing stations and a Layer 2 switch for
BUS1.
3. Connect the additional Layer 2 switch for BUS1 to the existing Layer 2 switch for BUS1
with a cable.
4. Turn on the power of the Layer 2 switch that you have added.

5. Connect the existing station that you have disconnected at step 2 to the newly added
Layer 2 switch for BUS1 with a cable.
7. Disconnect the cable between any one of the existing stations and a Layer 2 switch for
BUS2.
8. Connect the additional Layer 2 switch for BUS2 and the existing Layer 2 switch for BUS2
with a cable.
9. Turn on the power of the Layer 2 switch that you have added.
10. Connect the existing station that you have disconnected at step 7 to the newly added
Layer 2 switch for BUS2 with a cable.
12. Carry out the procedure for "Case 1" to add a station.
n Procedures and precautions for adding a Vnet/IP-Upstream domain

Follow these steps when you want to add a domain to a Vnet/IP-Upstream network.
WARNING
Make sure that there are no duplicate station addresses (domain number + station number) in
the system.
l Case 1: When using existing Layer 3 switches (ports are available on

Firstly, carry out steps 1 to 5 as shown below to configure Layer 3 switches for BUS1 and
BUS2. Next, add stations by following the procedures in "■ Procedures and precautions for
adding a Vnet/IP station."
2. Make the necessary settings on the existing Layer 3 switch for BUS1. If the port on the
Layer 3 switch is disabled, enable the port.
4. Make the necessary settings on the existing Layer 3 switch for BUS2. If the port on the
Layer 3 switch is disabled, enable the port.
6. Add stations for the new domain by following the procedures in "■ Procedures and pre-
cautions for adding a Vnet/IP station."
l Case 2: When you need to add Layer 3 switches (no ports are available on
Firstly, carry out steps 1 to 7 as shown below to add Layer 3 switches for BUS1 and BUS2.
Next, add stations by following the procedures in "■ Procedures and precautions for adding a
Vnet/IP station."

2. Make the necessary settings on the Layer 3 switch for BUS1 that you are going to add.
3. Connect the additional Layer 3 switch for BUS1 to an existing Layer 2 or Layer 3 switch
for BUS1 with a cable.
5. Make the necessary settings on the Layer 3 switch for BUS2 that you are going to add.
6. Connect the additional Layer 3 switch for BUS2 and an existing Layer 2 or Layer 3 switch
for BUS2 with a cable.
8. Add stations for the new domain by following the procedures in "■ Procedures and pre-
cautions for adding a Vnet/IP station."

<Appendix 1. Function blocks for Upstream systems> App.1-1
Appendix 1. Function blocks for

Upstream systems
Function blocks for Upstream system are unique to ProSafe-RS and Interference-free (which
means that they do not affect the safety function). Function blocks for Upstream systems are
only available with SCSU1.
Function blocks for Upstream systems are:
• Function blocks for data buffering function
• Function blocks for gas flow rate calculation function

<Appendix 1.1 Function blocks for data buffering function > App.1-2
Appendix 1.1 Function blocks for data buffering

function
This Appendix describes the function blocks for data buffering function.
• Buffering BOOL-type data on a value change (BUF_DIF_B)
• Buffering INTEGER-type data on a value change (BUF_DIF_I)
• Buffering REAL-type data on a value change (BUF_DIF_R)
• Periodic buffering of INTEGER-type data (BUF_TIM_I)
• Periodic buffering of REAL-type data (BUF_TIM_R)
• Buffering BOOL-type data on trigger detection (BUF_TRIG_B)
• Buffering INTEGER-type data on trigger detection (BUF_TRIG_I)
• Buffering REAL-type data on trigger detection (BUF_TRIG_R)

Appendix 1.1.1 BUF_DIF_B (buffering when BOOL-type

data changes)
BUF_DIF_B is a function block that stores BOOL-type data in the buffer when the data
changes.
BUF_DIF_B
IN STS
IDNO
Figure Appendix 1.1.1-1 BUF_DIF_B
n Arguments
Table Appendix 1.1.1-1 Arguments of BUF_DIF_B
IN/OUT Argu- Data type Description
ment
IN IN BOOL Input value
IDNO DINT Identification number. (1 to 60000)
OUT STS BOOL Data status.
It becomes TRUE during the scan period when the data is stor-
ed. During other timing, it is FALSE.
n Description
• Monitor an input value (IN) at every scan period and stores the value in the buffer when
the input value changed from the previous buffered value. The input value is stored in the
buffer at an initial scan after the SCS starts.
• IDNO indicates the data identification number. The identification number allowed ranges
from 1 to 60000. Data will not be stored in the buffer if a number less than 0 or larger than
60001 is specified.
• Data status (STS) is TRUE only during the scan period when data is stored in the buffer,
and otherwise it is FALSE. A sample output is shown in the following figure:
1s t s c an Stored v alue
TR U E
IN
FA L S E
TR U E
STS
FA L S E
Sc an
period
Figure Appendix 1.1.1-2 Sample output of BUF_DIF_B
n Remarks
• BUF_DIF_B is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_DIF_B can be used only in SCSU1 running R3.02.10 or later.

• Do not specify the same identification number for different variables. Specifying the same
identification number causes FAST/TOOLS to display a trend incorrectly.
n Specification difference between simulators on a computer and

actual SCS
l Behavior in SCS simulation test
BUF_DIF_B cannot be used in the SCS simulator.
l Behavior in the logic simulation test

Data buffering function is unavailable. Data cannot be stored in the buffer. However, STS be-
comes TRUE during the scan period when the conditions for storing the data in the buffer are
met.

Appendix 1.1.2 BUF_DIF_I (buffering when INTEGER-type

data changes)
BUF_DIF_I is a function block that stores INTEGER-type data in the buffer when the data
changes beyond the specified range.
BUF_DIF_I
IN STS
DEL
IDNO
Figure Appendix 1.1.2-1 BUF_DIF_I
n Arguments
Table Appendix 1.1.2-1 Arguments of BUF_DIF_I
ment
IN IN DINT Input value
DEL DINT Deadband for DEL >= 0.
If DEL < 0, the FB will operate with DEL as 0.
IDNO DINT Identification number (1 to 60000)
n Description
the absolute value of the amount in the input value changed from the previous stored val-
ue exceeded deadband (DEL). If DEL < 0 is specified, the value is stored in the buffer
assuming the absolute value exceeded deadband at the change of the input value. The
input value is stored in the buffer at an initial scan after the SCS starts.
60001 is specified.
• Data status (STS) is TRUE only during the scan period when the data is stored in the buf-
fer; otherwise it is FALSE. A sample output is shown in the following figure:

1s t s c an
Stored v alue
IN
D IF:
The difference between the
input value (IN) and the value
stored in the buffer last time.
DEL
D IF
TR U E
STS
FA L S E
Sc an
period
Figure Appendix 1.1.2-2 Sample output of BUF_DIF_I
n Remarks
• BUF_DIF_I is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_DIF_I can be used only in SCSU1 running R3.02.10 or later.

actual SCS
BUF_DIF_I cannot be used in the SCS simulator.

met.

Appendix 1.1.3 BUF_DIF_R (buffering when REAL-type

data changes)
BUF_DIF_R is a function block that stores REAL-type data in the buffer when the data
changes beyond the specified range.
BUF_DIF_R
IN STS
DEL
IDNO
Figure Appendix 1.1.3-1 BUF_DIF_R
n Arguments
Table Appendix 1.1.3-1 Arguments of BUF_DIF_R
ment
IN IN REAL Input value
DEL REAL Deadband for DEL >= 0.
If DEL < 0, the FB will operate with DEL as 0.
n Description
the absolute value of the amount in the input value changed from the previous stored val-
ue exceeded deadband (DEL). If DEL < 0 is specified, the value is stored in the buffer
assuming the absolute value exceeded deadband at the change of the input value. The
60001 is specified.
fer; otherwise it is FALSE.
n Remarks
• BUF_DIF_R is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_DIF_R can be used only in SCSU1 running R3.02.10 or later.


actual SCS
BUF_DIF_R cannot be used in the SCS simulator.

met.

Appendix 1.1.4 BUF_TIM_I (periodic buffering of INTEGER-

type data)
BUF_TIM_I is a function block that stores INTEGER-type data in the buffer in a specified cy-
cle.
BUF_TIM_I
IN STS
CT
IDNO
Figure Appendix 1.1.4-1 BUF_TIM_I
n Arguments
Table Appendix 1.1.4-1 Arguments of BUF_TIM_I
ment
CT TIME Buffering period
IDNO DINT Identification number (1 to 60000 )
It becomes TRUE at a scan in which the data is stored. The oth-
er timing, it is FALSE.
n Description
• Stores the input value (IN) in the buffer with buffering period (CT) specified. When 0 s is
specified in CT, it is not stored in the buffer. If the specification of CT is not divisible by the
scan period, the input value is stored in the buffer when the accumulation of the scan pe-
riod exceeds CT. The accumulated scan period will be reset at a scan beyond CT. The
The following figure shows the example when the scan period is 200 ms and 300 ms is
specified in CT.
When CT = 300 ms and scan period = 200 ms
1s t s c an 2nd 3rd 4th 5th 6th
TR U E
STS
FA L S E
200 ms
CT
CT CT
(= 300 ms)
Store Not s tore Store Not s tore Store Not s tore

(First scan) (CT > 200) (CT < 400) (CT > 200) (CT < 400) (CT > 200)
Figure Appendix 1.1.4-2 Output example of BUF_TIM_I
• IDNO is an identification number of data. The identification number allowed ranges from 1
to 60000. Data will not be stored in the buffer if a number less than 0 or larger than 60001
is specified.
• Data status (STS) is TRUE only at the scan for which the data is stored in the buffer; oth-
erwise it is FALSE.

n Remarks
• BUF_TIM_I is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_TIM can be used only in SCSU1 running R3.02.10 or later.
identification number causes FAST/TOOLS to display an incorrect trend.

actual SCS
BUF_TIM_I cannot be used in the SCS simulator.

met.

Appendix 1.1.5 BUF_TIM_R (periodic buffering of REAL-

type data)
BUF_TIM_R is a function block that stores REAL-type data in the buffer in a specified cycle.
BUF_TIM_R
IN STS
CT
IDNO
Figure Appendix 1.1.5-1 BUF_TIM_R
n Arguments
Table Appendix 1.1.5-1 Arguments of BUF_TIM_R
ment
CT TIME Buffering period
ed. The other timing, it is FALSE.
n Description
• Stores the input value (IN) in the buffer with buffering period (CT) specified. When 0 s is
specified in CT, it is not stored in the buffer. If the specification of CT is not divisible by the
scan period, the input value is stored in the buffer when the accumulation of the scan pe-
riod exceeds CT. The accumulated scan periods will be reset at a scan beyond CT. The
to 60000. Data will not be stored if a number less than 0 or larger than 60001 is specified.
n Remarks
• BUF_TIM_R is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_TIM_R can be used only in SCSU1 running R3.02.10 or later.

actual SCS
BUF_TIM_R cannot be used in the SCS simulator.


met.

Appendix 1.1.6 BUF_TRIG_B (buffering BOOL-type data on

trigger detection)
BUF_TRIG_B is a function block that stores BOOL-type data in the buffer when the trigger
signal value becomes TRUE.
BUF_TRIG_B
IN STS
TRIG
IDNO
Figure Appendix 1.1.6-1 BUF_TRIG_B
n Arguments
Table Appendix 1.1.6-1 Arguments of BUF_TRIG_B
ment
IN IN BOOL Input value
TRIG BOOL Trigger signal
n Description
• When the trigger signal (TRIG) changes from FALSE to TRUE, this stores the input value
(IN) in the buffer.
to 60000. Data will not be stored in the buffer if a number less than 0 or larger than 60001
is specified.
• Data status (STS) is TRUE during the scan period when the data is stored in the buffer;
otherwise it is FALSE. A sample output is shown in the following figure:
1s t s c an
TR U E
T R IG
FA L S E
TR U E
STS
FA L S E
Sc an
period
Figure Appendix 1.1.6-2 Sample output of BUF_TRIG_B
n Remarks
• BUF_TRIG_B is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_TRIG_B can be used only in SCSU1 running R3.02.10 or later.


actual SCS
BUF_TRIG_B cannot be used in the SCS simulator.

met.

Appendix 1.1.7 BUF_TRIG_I (buffering INTEGER-type data

on trigger detection)
BUF_TRIG_I is a function block that stores INTEGER-type data in the buffer when the trigger
BUF_TRIG_I
IN STS
TRIG
IDNO
Figure Appendix 1.1.7-1 BUF_TRIG_I
n Arguments
Table Appendix 1.1.7-1 Arguments of BUF_TRIG_I
ment
n Description
(IN) in the buffer.
• IDNO is the identification number of data. The identification number allowed ranges from
1 to 60000. Data will not be stored in the buffer if a number less than 0 or larger than
60001 is specified.
n Remarks
• BUF_TRIG_I is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_TRIG_I can be used only in SCSU1 running R3.02.10 or later.

actual SCS
BUF_TRIG_I cannot be used in the SCS simulator.


met.

Appendix 1.1.8 BUF_TRIG_R (buffering REAL-type data on

trigger detection)
BUF_TRIG_R is a function block that stores REAL-type data in the buffer when the trigger
BUF_TRIG_R
IN STS
TRIG
IDNO
Figure Appendix 1.1.8-1 BUF_TRIG_R
n Arguments
Table Appendix 1.1.8-1 Arguments of BUF_TRIG_R
ment
n Description
(IN) in the buffer.
• IDNO is the identification number of data. The identification number allowed ranges from
1 to 60000. Data will not be stored in the buffer if a number less than 0 or larger than
60001 is specified.
n Remarks
• BUF_TRIG_R is an interference-free function block. Do not use it to input data to safety
loops.
• BUF_TRIG_R can be used only in SCSU1 running R3.02.10 or later.

actual SCS
BUF_TRIG_R cannot be used in the SCS simulator.


met.

<Appendix 1.2 Function blocks for gas flow rate calculation function> App.1-19
Appendix 1.2 Function blocks for gas flow rate

calculation function
This section describes the function blocks used in the gas flow rate calculation function.
A list of function blocks for gas flow rate calculation function is shown in the following table.
These function blocks are interference-free and available only in SCSU1.
Table Appendix 1.2-1 List of function blocks for gas flow rate calculation function
Type of function block Function Outline of the functions Supported
block name from (*1)
Gas flow rate calcula- AGA_3 Perform calculation defined in AGA Reports No. R3.02.10
tion 3 and AGA Report No.8.
AGA_7 Perform calculation defined in AGA Reports No. R3.02.10
7, No.8, and No.10.
Report data creation AGA_R Create AGA report data R3.02.10
External communica- ECWR_B Function block with external communication with R3.02.10
tion with date retaining BOOL-type data retaining function
function
ECWR_I Function block with external communication with R3.02.10
INTEGER-type data retaining function
ECWR_R Function block with external communication with R3.02.10
REAL-type data retaining function
Supporting user de- ACCUM Perform accumulation R3.02.10
fined gas flow calcula-
tion
*1: Function blocks can be used in the SCS data base that is newly created by SENG of the software release number or later
shown in the table.
n Function blocks of gas flow rate calculation

The gas flow rate calculation function blocks calculate the gas flow rate, compressibility factor,
speed of sound, etc. according to the specification of AGA.
• AGA_3 (AGA3 calculation)
• AGA_7 (AGA7 calculation)
n Function block of report data creation

The function block for report data creation calculates the accumulated value and average val-
ue of the gas flow rates produced by the gas flow rate function block. It also performs the
closing process to create the daily and hourly closing data of gas flow rate as report data.
• AGA_R (Report data creation)
n External communication function blocks with data retaining

function
The external communication function block with data retaining function outputs setting values
from FAST/TOOLS or Modbus master station to which the SCS is connected as a Modbus
slave. The following function blocks are provided for different data types:
• ECWR_B (External communication with BOOL-type data retaining function)
• ECWR_I (External communication with INTEGER-type data retaining function)
• ECWR_R (External communication with REAL-type data retaining function)

n Function block supporting user defined gas flow calculation

The function block that supports user defined gas flow calculation is used for the unique gas
flow calculation that is different from the AGA specification.
• ACCUM (Accumulation)

Appendix 1.2.1 AGA_3 (AGA3 calculation)

AGA_3 is a function block that calculates the gas flow rate specified in AGA Report No.3 and
the compressibility factor specified in AGA Report No.8.
AGA_3
EXEC EXEO
SP CDAT
SP_S NOFL
DP ERCD
DP_S CDT2
T PARO
T_S CMPO
SET
PARA
COMP
CP_S
Figure Appendix 1.2.1-1 AGA_3
n Arguments
Table Appendix 1.2.1-1 Argument of AGA_3
ment
IN EXEC BOOL Calculation execution flag
Starts calculation at the rising from FALSE to TRUE.
SP REAL Static pressure
Unit: psi (US), kPa (SI)
SP_S BOOL Status of SP
TRUE: GOOD
FALSE: BAD
DP REAL Differential pressure
Unit: inH2O (US), kPa (SI)
DP_S BOOL Status of DP
TRUE: GOOD
FALSE: BAD
T REAL Flow temperature
Unit: degF (US), degC (SI)
T_S BOOL Status of T
TRUE: GOOD
FALSE: BAD
SET BOOL Flag to specify whether to read PARA and COMP
TRUE: Read PARA and COMP.
FALSE: Do not read PARA and COMP.
PARA AGA_3_PARAM AGA3 input parameters
COMP AGA_COMPOSI- AGA gas composition
TION
CP_S BOOL AGA gas composition status
TRUE: GOOD
FALSE: BAD

Table Appendix 1.2.1-1 Argument of AGA_3 (Table continued)
ment
OUT EXEO BOOL Calculation execution flag
Output an value of EXEC
CDAT AGA_CALC_DATA Data after calculation
Used for report data creation
NOFL BOOL Gas production suspended flag
TRUE: Gas production suspended
FALSE: Gas being produced
ERCD DINT Error cause
An error code is set when an error occurred.
CDT2 AGA_3_OUTPUT AGA3 output data
PARO AGA_3_PARAM AGA3 input parameters
Output PARA that is read into AGA3.
CMPO AGA_COMPOSI- AGA gas composition
TION Output COMP that is read into AGA3.
n Description
AGA_3 uses process input data (SP, DP, T), parameter (PARA), and gas composition data
(COMP) to calculate the gas flow rate. AGA_3 consists of the following functions to calculate
the gas flow rate defined in AGA Reports No.3 and No.8:
• Parameter load processing
• Closing operation on change of parameter
• Process input processing
• Gas composition data load processing
• Detection of halt to gas production
• Unit designation
• Compressibility calculation (AGA Report No.8)
• Gas flow rate calculation (AGA Report No.3, SP, DP, and T as standard)
• Heating value calculation (GPA2172)
• Energy calculation
l Calculation execution control

Calculation starts when the calculation execution flag (EXEC) changes from FALSE to TRUE.
Follow these steps to start the calculation:
1. Specify the values of AGA3 input parameters (PARA) and gas composition (COMP) pa-
rameters.
2. Set the read flag (SET) to TRUE.
Parameters that are set are loaded into the function block.
3. Set the calculation execution flag (EXEC) to TRUE.
The calculation starts.

TIP • After the calculation is started, the calculation proceeds even if the calculation execution flag (EXEC) is
turned off to FALSE.
• Before EXEC is set to TRUE, the parameters are loaded but the calculation is not performed.
l Parameter load processing

When the read flag (SET) is set to TRUE, AGA3 input parameters (PARA) and Gas composi-
tion (COMP) are loaded. The loaded parameters are used for calculation and also output to
PARO and CMPO. PARO and CMPO can be used to refer parameters by using the data buf-
fering function. The initial value of the parameters before the first loading is 0 or FALSE.
PARA and COMP are structure-type input arguments.
Follow these steps when you change the values of multiple parameters in PARA and CMPO
at a time.
1. Turn off the read flag (SET) to FALSE.
2. Change the values of AGA7 input parameters (PARA) and Gas composition (COMP).
TIP Some of the parameters contained in PARA or COMP are linked with each other. If two or more parameters
are changed while SET is TRUE, calculation may be performed while the relation between parameters is con-
flicting.
l Closing operation on change of parameter

AGA_3 detects online or manual modification of calculation parameters. If it detects a change,
it sets the Configuration changed flag (CONF_Q) in the data after calculation (CDAT) to
TRUE. AGA_R will perform the closing processing due to parameter change detection when
CONF_Q in its input parameters becomes TRUE.
Note that, when parameters are read under the following conditions, parameter changes will
not be detected:
• Parameters are loaded before EXEC is set to TRUE.
• The parameters are loaded for the first time immediately after the SCS is restarted or off-
line downloaded.
SEE
ALSO For more information about the parameters for which changes are detected, refer to:
“n AGA_3_PARAM structure” on page App.2-1
l Process input processing (SP, DP, T)

The process input processing determines an input value used for calculation according to the
setting of input data, status, and parameters.
• Input processing of static pressure (SP) and differential pressure (DP)
The following figure shows the input processing of static pressure (SP) and differential
pressure (DP):

START
SP_MNT
(DP_MNT)
2: User entered value 0: No
1: Last good value

SP_S
BAD
(DP_S)
GOOD
SP (DP) used for calculation

= User entered value SP (DP) used for calculation SP (DP) used for calculation
(SP(DP)_MNT_VALUE) = Last good value of SP (DP) = SP (DP) at this scan
END
Figure Appendix 1.2.1-2 Process input processing (SP, DP)
• AGA_3 determines the static pressure (SP) by using Static Pressure Maintenance
mode (SP_MNT) of the parameters (PARA) and the SP status (SP_S). It also deter-
mines the differential pressure (DP) by using Differential Pressure Maintenance
mode (DP_MNT) of the parameters (PARA) and the DP status (DP_S).
• In case of abnormal input (the status is BAD), AGA_3 calculates using the latest nor-
mal value (the input value when the status is normal the last time). Since the latest
normal value is not available immediately after SCS startup, it is treated as gas pro-
duction suspended.
• In the maintenance mode, it is possible to continue the gas flow rate calculation while
fixing the input value during maintenance and calibration of a field device.
• Input processing of flow temperature (T)
The following figure shows the input processing of the flow temperature (T):

START
3: Always DEFAULT_TEMP 1: No
_SELECT
2: If input fails T_MNT

0: No
2: User entered value
1: Last good value
BAD T_S BAD T_S
GOOD
GOOD
T_MNT
1: Last good value
T used for calculation T used for calculation T used for calculation T used for calculation
= Default value = Last good value of T = User entered value = T value input at this scan
(DEFAULT_TEMP) (T_MNT_VALUE)
T used for calculation T used for calculation

= User entered value T used for calculation
= T value input at this scan = Last good value of T
(T_MNT_VALUE)
END
Figure Appendix 1.2.1-3 Process input processing (TP)
AGA_3 determines the flow temperature (T) by using Default Temperature Selection (DE-
FAULT_TEMP_SELECT) and Flow Temperature Maintenance mode (T_MNT) of the pa-
rameters (PARA) and the T status (T_S).
• Calculation process of absolute pressure
The following figure shows the calculation process of absolute pressure:

START
SP_SELECT 1: Absolute
2: Gauge
ATMPRESS_CAL
_SELECT
1: Calculated 2: Manual
Calculate atmospheric Use

pressure from FIXED_ATMPRESS
Use SP as is.
LATITUDE for
and ALTITUDE. atmospheric pressure.
Add
atmospheric pressure
to SP.
END
Figure Appendix 1.2.1-4 Calculation process of absolute pressure
SP is converted into the absolute pressure according to the specifications of Static Pres-
sure Selection (SP_SELECT) and Atmospheric Pressure Calculation Selection (ATM-
PRESS_CAL_SELECT) of the parameters (PARA).
SEE
ALSO For more information about the behavior while gas production is suspended, refer to:
“l Detection of halt to gas production” on page App.1-26
l Gas composition data load processing

To load the gas composition data contained in Gas composition (COMP), follow the following
methods:
• When gas composition data is manually set from an external device of the SCS:
Set Composition Input Selection (COMP_INPUT_SELECT) of the parameters (PARA) to
1: Manual. The gas composition data in COMP will be loaded when SET is set to TRUE
in the same way as with PARA. In this case, always set the COMP data status (CP_S) to
TRUE.
• When gas composition data is dynamically set via subsystem communication:
2: Live. The gas composition data in COMP will be loaded at every scan interval regard-
less of the SET value. When CP_S is set to FALSE (BAD), the data of COMP at the pre-
vious scan will be used.
l Detection of halt to gas production

When Differential Pressure (DP) < Differential Pressure Cutoff (DP_CUTOFF of PARA),
AGA_3 regards that no gas is flowing. In this case, AGA_3 sets the gas production suspen-
ded flag (NOFL) to TRUE.
When NOFL in the input parameters is TRUE, AGA_R adds this time of the scan to gas pro-
duction downtime, but does not add the flow rate to the accumulation or average value.

l Unit designation
Unit system for process input values and parameter settings is specified using Input Unit Se-
lection (UNIT_SELECT) in the parameters (PARA). The unit system designated in UNIT_SE-
LECT and the unit system for process input values and parameter setting should be consis-
tent.
l Compressibility calculation (AGA Report No.8)

This function block calculates the compressibility factor of each meter based on AGA Report
No. 8 standards.
The type of calculation method for compressibility factor are shown in the following table:
Table Appendix 1.2.1-2 Type of calculation methods for compressibility factor

Type of calculation Compressibility factor calculation
DCM (Detail Characterization Method) Calculate the compressibility factor based on the
composition information given by the COMP argu-
ment.
GCM1 (Gross Characterization Method 1) Calculate the compressibility factor based on CAR-
BON_DIOXIDE given by the COMP argument.
GCM2 (Gross Characterization Method 2) Calculate the compressibility factor based on NITRO-
GEN and CARBON_DIOXIDE given by the COMP
argument.
AGA8 calculation method selection (AGA8_METHOD_SELECT) of the parameter (PARA) is

used to specify the type of calculation.
l Gas flow rate calculation (AGA Report No.3, SP, DP, and T as standard)
Based on AGA Report No. 3 specifications, AGA_3 calculates the gas flow rate of the orifice
plate flow meter.
l Heating value calculation (GPA2172)

This function block calculates the heating value of gas based on GPA2172 specifications. This
function block calculates only the heating value of dry gas.
TIP The calculation conditions are as follows:
• Determine Calculated Ideal Heating Value (CALCULATED_ID_HV) by using the table under Standard
Condition (60 deg F, 14.696 psia) stipulated in GPA2172. In this calculation, the pressure under Base Con-
dition (BASE_PRESS) is considered, but the temperature is fixed to 60 deg F.
• Calculated Ideal Heating Value (CALCULATED_HV) will be determined based on the influence of actual
gas.
l Energy calculation
This function block calculates gas energy by using the following formula:
Energy = flow rate at base condition * real heating value
For the heating value, this function block uses the calculation result of GPA2172. You can use
the gross method heating value (GROSS_HV) in the parameter (PARA) by specifying "0:
Manual" for Energy calculation (ENERGY_CAL_SELECT) in PARA.
l Behavior at abnormal calculation

Calculation does not work correctly if the calculation execution flag (EXEC) is set to TRUE
when parameters are not configured correctly.

Abnormal calculation such as division by zero due to mis-configuration of a parameter will be
checked beforehand and detected as an error. In this case, an error code is set to the Error
cause (ERCD) and TRUE is set to the gas production suspended flag (NOFL). Do not use the
output parameters when an error code is set in ERCD.
If an error occurs in AGA_3, NOFL is set to TRUE and the connected AGA_R ignores the da-
ta of the scan period in which the error occurred.
SEE
ALSO For more information about error codes set in ERCD, refer to:
Appendix 1.2.8, “Error code” on page App.1-47
n Remarks
• AGA_3 is an interference-free function block. Do not use it to input data to safety loops.
• AGA_3 can be used only in SCSU1 running R3.02.10 or later.

actual SCS
AGA_3 cannot be used in the SCS simulator.

• I/O parameters operate as in the actual SCS system.
• FAST/TOOLS cannot reference data by using a tag name.

Appendix 1.2.2 AGA_7 (AGA7 calculation)

AGA_7 is a function block that calculates the gas flow rate specified in AGA Report No.7. It
also calculates internally the compressibility factor specified in AGA Report No.8 and the
speed of sound specified in AGA Report No.10.
AGA_7
EXEC EXEO
SP CDAT
SP_S NOFL
T ERCD
T_S CDT2
PULS PARO
P_S CMPO
SET
PARA
COMP
CP_S
Figure Appendix 1.2.2-1 AGA_7
n Arguments
Table Appendix 1.2.2-1 AGA_7 arguments
ment
SP REAL Static pressure
Unit: psi (US), kPa (SI)
SP_S BOOL Status of SP
TRUE: GOOD
FALSE: BAD
T REAL Flow temperature
Unit: degF (US), degC (SI)
T_S BOOL Status of T
TRUE: GOOD
FALSE: BAD
PULS REAL Pulse count per Scan period
P_S BOOL Status of PULS
TRUE: GOOD
FALSE: BAD
SET BOOL Flag to specify whether to read PARA and COMP
TRUE: Read PARA and COMP.
FALSE: Do not read PARA and COMP.
PARA AGA_7_PARAM AGA7 input parameters
COMP AGA_COMPOSI- AGA gas composition
TION
CP_S BOOL AGA gas composition status
TRUE: GOOD
FALSE: BAD

Table Appendix 1.2.2-1 AGA_7 arguments (Table continued)
ment
OUT EXEO BOOL Calculation execution flag
Output an value of EXEC
CDAT AGA_CALC_DATA Data after calculation: Used for report data creation
An error code is set when an error occurred.
CDT2 AGA_7_OUTPUT AGA7 output data
PARO AGA_7_PARAM AGA7 input parameters
Output PARA that is read into AGA7.
CMPO AGA_COMPOSI- AGA gas composition
TION Output COMP that is read into AGA7.
n Description
AGA_7 uses process input data (SP, T, PULS), parameters (PARA), and gas composition da-
ta (COMP) to calculate the gas flow rate. AGA_7 consists of the following functions to calcu-
late the gas flow rate defined in AGA Reports No.7, No.8 and No.10:
• Process input processing
• Gas composition data load processing
• Detection of halt to gas production
• Unit designation
• Compressibility calculation (AGA Report No.8)
• Gas flow rate calculation (AGA Report No.7, SP, DP, and PULS as standard)
• Calculation of speed of sound (AGA Report No.10)
• Heating value calculation (GPA2172)
• Energy calculation

Follow these steps to start the calculation:
1. Specify the values of AGA7 input parameters (PARA) and gas composition (COMP) pa-
rameters.
Parameters that are set are loaded into the function block.
3. Set the calculation execution flag (EXEC) to TRUE.
The calculation starts.

• Before EXEC is set to TRUE, the parameters are loaded but the calculation is not performed.

When the read flag (SET) is set to TRUE, AGA7 input parameters (PARA) and Gas composi-
tion (COMP) are loaded. The loaded parameters are used for calculation and also output to
PARO and CMPO. PARO and CMPO can be used to refer parameters by using the data buf-
fering function. The initial value of the parameters before the first loading is 0 or FALSE.
PARA and COMP are structure-type input arguments.
Use the following procedure when you change the values of multiple parameters in PARA and
CMPO at a time.
2. Change the values of AGA7 input parameters (PARA) and Gas composition (COMP).
TIP Some of the parameters contained in PARA or COMP are linked with each other. If two or more parameters
are changed while SET is TRUE, calculation may be performed while the relation between parameters is con-
flicting.

AGA_7 detects online or manual modification of calculation parameters. If it detects a change,
it sets the Configuration changed flag (CONF_Q) in the data after calculation (CDAT) to
TRUE. AGA_R will perform the closing processing due to parameter change detection when
CONF_Q in its input parameters becomes TRUE.
not be detected:
line downloaded.
SEE
ALSO For more information about the parameters for which changes are detected, refer to:
“n AGA_7_PARAM structure” on page App.2-5
l Process input processing (PULS)

The process input processing determines an input value used for calculation according to the
setting of input data, status, and parameters.
The following figure shows the input processing for the pulse counter (PULS):

START
PULS_MNT
1: Last good value
BAD P_S
GOOD
PULS used for calculation

PULS used for calculation PULS used for calculation
= User entered value
= Last good value of PULS = PULS at this scan
(PULS_MNT_VALUE)
END
Figure Appendix 1.2.2-2 Process input processing (PULS)
• AGA_7 uses Pulse Maintenance mode (PULS_MNT) of the parameters (PARA) and the
PULS status (P_S) to determine the pulse count per scan period (PULS).
• If an abnormal input (with the status BAD) is detected, AGA_7 uses the latest normal val-
ue (input value when the latest status was normal) for calculation. Since the latest normal
value is not available immediately after the SCS activation, it is assumed as the gas pro-
duction suspended.
• If you use using the maintenance mode, you can fix the input value while doing the main-
tenance or calibration of the field devices in order to continue the gas flow rate calcula-
tion.
SEE
ALSO For more information about the input processing of the static pressure (SP) and flow temperature (T), refer to:
“l Process input processing (SP, DP, T)” on page App.1-23
For more information about the behavior while gas production is suspended, refer to:
“l Detection of halt to gas production” on page App.1-32
l Gas composition data load processing

To load the gas composition data contained in Gas composition (COMP), follow the following
methods:
• When gas composition data is manually set from an external device of the SCS:
1: Manual. The gas composition data in COMP will be loaded when SET is set to TRUE
in the same way as with PARA. In this case, always set the COMP data status (CP_S) to
TRUE.
• When gas composition data is dynamically set via subsystem communication:
2: Live. The gas composition data in COMP will be loaded at every scan interval regard-
less of the SET value. When CP_S is set to FALSE (BAD), the data of COMP at the pre-
vious scan will be used.
l Detection of halt to gas production

When Pulse Count per Scan period (PULS) < Total Pulse Cutoff (PULSE_CUTOFF of PARA),
AGA_7 regards that no gas is flowing. In this case, AGA_7 sets the gas production suspen-
ded flag (NOFL) to TRUE and notifies it to AGA_R.

In turn, AGA_R adds this time of the scan to gas production downtime, but does not add the
flow rate to the accumulation or average value.
l Unit designation
Unit system for process input values and parameter settings is specified using Input Unit Se-
lection (UNIT_SELECT) in the parameters (PARA). The unit system designated in UNIT_SE-
LECT and the unit system for process input values and parameter setting should be consis-
tent.
l Compressibility calculation (AGA Report No.8)

This function block calculates the compressibility factor of each meter based on AGA Report
No. 8 standards.
The type of calculation method for compressibility factor are shown in the following table:
Table Appendix 1.2.2-2 Type of calculation methods for compressibility factor

Type of calculation Compressibility factor calculation
DCM (Detail Characterization Method) Calculate the compressibility factor based on the
composition information given by the COMP argu-
ment.
GCM1 (Gross Characterization Method 1) Calculate the compressibility factor based on CAR-
BON_DIOXIDE given by the COMP argument.
GCM2 (Gross Characterization Method 2) Calculate the compressibility factor based on NITRO-
GEN and CARBON_DIOXIDE given by the COMP
argument.
AGA8 calculation method selection (AGA8_METHOD_SELECT) of the parameter (PARA) is

used to specify the type of calculation.
l Gas flow rate calculation (AGA Report No.7, SP, T, and PULS criteria)
Based on AGA Report No. 7 specifications, AGA_7 calculates the gas flow rate of the turbine
flow meter.
l Speed of sound calculation (AGA Report No.10)

Based on the gas composition, AGA _7 calculates the speed of sound within the gas, accord-
ing to Report No.10 specifications.
l Heating value calculation (GPA2172)

This function block calculates the heating value of gas based on GPA2172 specifications. This
function block calculates only the heating value of dry gas.
TIP The calculation conditions are as follows:
• Determine Calculated Ideal Heating Value (CALCULATED_ID_HV) by using the table under Standard
Condition (60 deg F, 14.696 psia) stipulated in GPA2172. In this calculation, the pressure under Base Con-
dition (BASE_PRESS) is considered, but the temperature is fixed to 60 deg F.
• Calculated Ideal Heating Value (CALCULATED_HV) will be determined based on the influence of actual
gas.
l Energy calculation
This function block calculates gas energy by using the following formula:
Energy = flow rate at base condition * real heating value

For the heating value, this function block uses the calculation result of GPA2172. You can use
the gross method heating value (GROSS_HV) in the parameter (PARA) by specifying "0:
Manual" for Energy calculation (ENERGY_CAL_SELECT) in PARA.

cause (ERCD) and TRUE is set to the gas production suspended flag (NOFL). Do not use the
output parameters when an error code is set in ERCD.
If an error occurs in AGA_7, NOFL is set to TRUE and the connected AGA_R ignores the da-
ta of the scan period in which the error occurred.
SEE
n Remarks
• AGA_7 is an interference-free function block. Do not use it to input data to safety loops.
• AGA_7 can be used only in SCSU1 running R3.02.10 or later.

actual SCS
AGA_7 cannot be used in the SCS simulator.


Appendix 1.2.3 AGA_R (Report data creation)

AGA_R is a function block that provides the report function of the gas flow rate calculation
function. In addition, it implements the data retaining function.
AGA_R
EXEC CURH
CDAT PREH
NOFL TDAY
SET YDAY
PARA CURM
HRLY
DYLY
MNLY
CNFC
CMPC
ERCD
PARO
Figure Appendix 1.2.3-1 AGA_R
n Arguments
Table Appendix 1.2.3-1 AGA_R arguments
ment
CDAT AGA_CALC_DATA Data after AGA calculation
SET BOOL Flag to specify whether to read PARA
TRUE: Read PARA.
FALSE: Do not read PARA.
PARA AGA_R_PARAM AGA REPORT input parameters
OUT CURH AGA_RP_H Report data (current hourly data)
PREH AGA_RP_H Report data (last hourly closing data)
TDAY AGA_RP_D Report data (current daily data)
YDAY AGA_RP_D Report data (last daily closing data)
CURM AGA_RP_M Report data (current monthly data)
HRLY DINT Hourly closing execution counter
DYLY DINT Daily closing execution counter
MNLY DINT Monthly closing execution counter
CNFC DINT Parameter change counter
CMPC DINT Gas composition data change counter
PARO AGA_R_PARAM AGA report input parameters
Output PARA that is read into AGA_R.

n Description
AGA_R creates and outputs report data based on the data after AGA calculation (CDAT) and
the report data creation parameters (PARA). Report data includes closing data (daily closing
data, hourly closing data) and the current data (hourly, daily, monthly). Average values and
accumulated values of the gas flow rate are saved as the closing data or current data.
AGA_R consists of the following functions:
• Calculation of accumulated values
• Calculation of average values
• Calculation of gas production time
• Closing processing
• Data retaining processing

• Before the calculation is started, AGA_R reads the preset parameters and stores and restores retainable
data, but it does not perform accumulation, averaging, and closing processing.

When the read flag (SET) is set to TRUE, AGA report input parameters (PARA) are loaded.
The loaded parameters are used for calculation and also output to PARO. PARO can be used
to refer parameters by using the data buffering function. The initial value of the parameters
before the first loading is 0 or FALSE.
PARA is a structure-type input argument.
Use the following procedure when you change the values of multiple parameters in PARA at a
time.
2. Change the values of AGA report input parameters (PARA).
TIP Some of the parameters contained in PARA are linked with each other. If two or more parameters are
changed while SET is TRUE, calculation may be performed while the relation between parameters is conflict-
ing.

AGA_3 and AGA_7 detect online or manual modification of calculation parameters. If they de-
tect a change, they set the Configuration changed flag (CONF_Q) in the data after AGA cal-
culation (CDAT) to TRUE. AGA_R also detects online or manual modification of calculation
parameters. AGA_R performs the closing processing due to parameter change detection by
AGA_3, AGA_7 and AGA_R.

not be detected:
line downloaded.
l Calculation of accumulated values

AGA_R calculates the accumulated values of the data included in CDAT (data after AGA cal-
culation) and outputs them to CURH (current hourly data), TDAY (current daily data), and
CURM (current monthly data).
AGA_R does not calculate accumulated values while NOFL (gas production suspended flag)
is set to TRUE.
SEE
ALSO For more information about the timing of accumulated value initialization, refer to:
“l Closing processing” on page App.1-37
For more information about accumulated values that are output, refer to:
“n AGA_R_PARAM structure” on page App.2-8
l Calculation of average values

AGA_R calculates the average values included in CDAT (data after AGA calculation) and out-
puts it to CURH (current hourly data) and TDAY (current daily data). The way of the calcula-
tion of the average value is based on the specification by PARA. The average value calcula-
tion is based on the gas production time.
AGA_R does not calculate average values while NOFL (gas production suspended flag) is set
to TRUE.
The following two types of calculation are supported:
• Flow-dependant time-weighted linear
• Flow-weighted linear
SEE
ALSO For more information about the timing of average value initialization, refer to:
“l Closing processing” on page App.1-37
For more information about average values that are output, refer to:
“n AGA_R_PARAM structure” on page App.2-8
l Calculation of gas production time

AGA_R uses NOFL (gas production under suspension) to calculate gas production time. If
NOFL is FALSE, the scan period is added to the gas production time. If it is TRUE, the scan
period is added to the gas production downtime.
The gas production time included in CURH (current hourly data) and TDAY (current daily da-
ta) are initialized on execution of the hourly closing processing and the daily closing process-
ing, respectively.
l Closing processing
Closing process closes the accumulation value and average value on a monthly/daily/hourly
basis and produces report data.
On hourly closing, CURH (current hourly data) is reflected in PREH (hourly closing data). In
the next scan, the accumulated values and average values that are output to CURH will be
calculated from their initial values, except for ACCUM_VOLUME.

On daily closing, TDAY (current daily data) is reflected in YDAY (daily closing data). In the
next scan, the accumulated values and averaged values that are output to TDAY will be cal-
culated from their initial values, except for ACCUM_VOLUME.
On monthly closing, CURM (current monthly data) and ACCUM_VOLUME of CURH and
TDAY are initialized.
In most cases, it is performed when the current time (Universal Time Coordinated: UTC) that
SCS recognizes becomes the planned closing time (date and time) that your parameter has
specified. It is also performed when the planned closing time has expired at SCS startup and
the calculation execution flag (EXEC) becomes TRUE.
In addition, there is a special closing process that is forcibly performed when FORCE_CLOSE
parameter (PARA) is changed from FALSE to TRUE. Closing process is also conducted when
AGA_3, AGA_7 and AGA_R parameters are changed.
Note that, even when the special closing process has been performed, the timing of the next
closing process will not be changed; The regular closing process will be conducted at the
same time in point as when the special closing process would not have been performed.
The following table describes the types and causes of closing and their relationship with plan-
ned closing time:
Table Appendix 1.2.3-2 Types of closing processing

Closing type Trigger of closing Target Update of sched-
uled closing time
Regular closing When the scheduled closing time Hourly closing data when Yes
comes. the hourly closing time
comes.
Daily closing data when the
daily closing time comes.
Monthly closing data when
the monthly closing time
comes.
Start processing The scheduled closing time has al- Hourly closing data when Yes
ready passed when the SCS starts. the hourly closing time
comes.
Daily closing data when the
daily closing time comes.
Monthly closing data when
the monthly closing time
comes.
Forced closing FORCE_CLOSE has been changed Hourly, daily, and monthly No
from FALSE to TRUE. closing
Parameter The parameters of AGA_3, AGA_7 or Hourly, daily, and monthly No
change AGA_R has been changed. closing
The following table describes the relationships of closing targets to closing times:
Table Appendix 1.2.3-3 Closing targets and closing times

Closing target Closing time
Monthly closing 0 min. 0 sec. at the time specified by Contract hour and on the day specified by
Contract day
Daily closing 0 min. 0 sec. at the time specified by Contract hour
Hourly closing 0 min. 0 sec. every hour
The following table shows the timing of report data initialization:

Table Appendix 1.2.3-4 Timing of report data initialization
Target data Timing of initialization
CURH (current hourly da- Upon hourly closing (other than for ACCUM_VOLUME), monthly closing, or
ta) when the initialization flag (INIT_CURH_DATA_Q or INIT_ALL_DATA_Q in
PARA) is set.
PREH (hourly closing da- When the initialization flag (INIT_PREH_DATA_Q or INIT_ALL_DATA_Q in
ta) PARA) is set.
TDAY (current daily data) Upon daily closing (other than for ACCUM_VOLUME), monthly closing, or when
the initialization flag (INIT_TDAY_DATA_Q or INIT_ALL_DATA_Q in PARA) is
set.
YDAY (daily closing data) When the initialization flag (INIT_YDAY_DATA_Q or INIT_ALL_DATA_Q in
PARA) is set.
CURM (current monthly Upon monthly closing or when the initialization flag (NIT_CMON_DATA_Q or IN-
data) IT_ALL_DATA_Q in PARA) is set.
l Closing counter
Executing the closing processing updates a closing counter. The closing counter is incremen-
ted by one when the closing processing is executed regardless of a closing trigger factor.
The closing counter is equipped with the following counters:
• Hourly closing execution counter (HYLY)
• Daily closing execution counter (DYLY)
• Monthly closing execution counter (MNLY)
The closing counter provides retainable data. The value is kept retained after the SCS is re-
started. When the closing counter reaches up to the maximum value, it starts counting over
again from 1. The closing counter showing 0 indicates that the closing processing has not yet
been executed even once.
l Data retaining processing

Data retaining function is used to retain the accumulation value, average value, gas produc-
tion time, and closing data for the last cycle that are used to create the current data. It re-
stores these data in the first scan after SCS is started.
The following output data will be calculated continuously by using the values before SCS is
restarted:
CURH, PREH, TDAY, YDAY, CURM, HRLY, DYLY, MNLY

cause (ERCD). Do not use the output parameters when an error code is set in ERCD.
If an error is detected while AGA_R is calculating, the calculation is continued as a state
where gas production is suspended, like the case where NOFL is set as TRUE.
SEE
n Remarks
• AGA_R is an interference-free function block. Do not use it to input data to safety loops.

• AGA_R can be used only in SCSU1 running R3.02.10 or later.

actual SCS
AGA_R cannot be used in SCS simulator.


Appendix 1.2.4 ECWR_B (external communication with

BOOL-type Data retaining function)
ECWR_B is a function block for External communication with BOOL-type data retaining func-
tion.
ECWR_B
VAL OUT
Figure Appendix 1.2.4-1 ECWR_B
n Arguments
Table Appendix 1.2.4-1 Arguments of ECWR_B
ment
IN VAL BOOL Initial value
OUT OUT BOOL Output value
n Description
ECWR_B is a function block for external communication with BOOL-type data retaining func-
tion. The external data received in ECWR_B is periodically stored as retained data. When the
function have receive external data, the received data is output.
Until the first external data is received after the SCS is start-up, this function block outputs the
following values:
• The value set for VAL, if the data in the memory backed up by a battery is lost or if re-
tained data is initialized by offline download.
• Data stored by Data retaining function, if SCS was restarted or if master database offline
download was run.
n Remarks
• ECWR_B is an interference-free function block. Do not use it to input data to safety loops.
• ECWR_B can be used only in SCSU1 running R3.02.10 or later.

actual SCS
ECWR_B cannot be used in the SCS simulator.

• Data retaining function does not work under a logic simulation test environment.
• The value set in VAL is output to OUT.

Appendix 1.2.5 ECWR_I (External communication with

INTEGER-type data retaining function)
ECWR_I is a function block for external communication with INTEGER-type data retaining
function.
ECWR_I
VAL OUT
Figure Appendix 1.2.5-1 ECWR_I
n Arguments
Table Appendix 1.2.5-1 Arguments of ECWR_I
ment
IN VAL DINT Initial value
OUT OUT DINT Output value
n Description
ECWR_I is a function block that external communication with INTEGER-type data retaining
function. The external data received in ECWR_I is periodically stored as retained data. When
the function have receive external data, the received data is output.
following values:
download was run.
n Remarks
• ECWR_I is an interference-free function block. Do not use it to input data to safety loops.
• ECWR_I can be used only in SCSU1 running R3.02.10 or later.

actual SCS
ECWR_I cannot be used in the SCS simulator.


Appendix 1.2.6 ECWR_R (External communication with

REAL-type data retaining function)
ECWR_R is a function block for external communication with REAL-type data retaining func-
tion.
ECWR_R
VAL OUT
Figure Appendix 1.2.6-1 ECWR_R
n Arguments
Table Appendix 1.2.6-1 Arguments of ECWR_R
ment
IN VAL REAL Initial value
OUT OUT REAL Output value
n Description
ECWR_R is a function block for external communication with REAL-type data retaining func-
tion. The external data received in ECWR_R is periodically stored as retained data. When the
function block have receive external data, the received data is output.
following values:
download was run.
n Remarks
• ECWR_R is an interference-free function block. Do not use it to input data to safety
loops.
• ECWR_R can be used only in SCSU1 running R3.02.10 or later.

actual SCS
ECWR_R cannot be used in the SCS simulator.

• FAST/TOOLS cannot reference data by using a tag name

Appendix 1.2.7 ACCUM (Accumulation)

ACCUM accumulates input values on a specified accumulation unit basis.
ACCUM
IN
STS OUT
RST
SW
LCSW
LCUT
LMT
Figure Appendix 1.2.7-1 ACCUM
n Arguments
Table Appendix 1.2.7-1 Argument of ACCUM
ment
IN IN REAL Input value to be accumulated
STS BOOL Status of an input value
TRUE: GOOD
FALSE: BAD
RST BOOL Reset an accumulated value
Reset by rising from FALSE to TRUE
SW DINT Totalizer specification switch
0: Does not accumulate
1: Accumulation in second
2: Accumulation in minute
3: Accumulation in hour
4: Accumulation in day
LCSW BOOL Low-Input Cut Switch
TRUE: Cut low input using the Low input cut switch
FALSE: Does not cut low input
LCUT REAL Low input cut value
Positive value (including 0): Does not execute accumulation
processing for input values that is less than the low input cut
value (negative input value is also ignored).
Negative value: Does not execute accumulation processing for
input values when the absolute value of the input value is less
than the absolute value of the low input cut value
LMT REAL Upper limit of accumulation value
When the absolute value of accumulated value is higher than
the upper limit value, the accumulated value is reset to 0, and
accumulation continues.
OUT OUT REAL Accumulated value
n Description
ACCUM is a function block that accumulate input values.
The following is the accumulation calculation formula:

Ts
SUMn = X × + SUMn-1
Tk
X: Input value
SUMn: Totalized value
SUMn-1: Previous totalized value
Ts: Scan period (seconds)
Tk: Time scale conversion coefficient
A time scale conversion constant is determined by the totalizer specification switch (SW). The
relationship of the totalizer specification switch with the time scale conversion constant is
shown in the following table: If another value or 0 is specified in SW, the input value (IN) is not
accumulated.
Table Appendix 1.2.7-2 Totalizer specification switch and time scale conversion constant
Totalizer specification switch (SW) Time scale conversion constant (Tk)
1: Accumulation in second 1
2: Accumulation in minute 60
3: Accumulation in hour 3600
4: Accumulation in day 86400
You should configure the Totalizer specification switch (SW) according to the unit of the input
value (IN). For example, if the unit of IN is m3/min, set the Totalizer specification switch (SW)
to "2: Accumulation in minute."
l Accumulation action
An accumulated value is retainable data.
A negative value is allowed to accumulate when the input value is negative. In this case, AC-
CUM accumulates without changing the sign of the input value. An accumulated value incre-
ments when the input value is positive and decrements when it is negative. However, accu-
mulation of a negative value is valid when the Low-Input Cut Switch (LCSW) is set to "Does
not cut low input" or a negative value is set as the Low input cut value.
When the absolute value of the accumulate value exceeds the upper limit, the value is reset
to 0 and the accumulation continues. Specify a value ranging from 1.0E-12 to 1.0E12 as the
upper limit value. If a value outside this range is specified, the upper limit value is set to
1.0E8.
The accumulation does not take place when the status of the input value is set to BAD.
l Resetting operation
RST (Reset an accumulated value) functions as a switch to reset the calculation result of the
accumulation value. ACCUM resets the accumulation value to 0 in the scan period when it
detects RST transitioning from FALSE to TRUE, and accumulates IN values.
n Remarks
• ACCUM is an interference-free function block. Do not use it to input data to safety loop.
• Make your application so that the calculation result does not cause an overflow.
• ACCUM can be used only in SCSU1 running R3.02.10 or later.


actual SCS
ACCUM cannot be used in the SCS simulator.

Data retaining function does not work under a logic simulation test environment.

Appendix 1.2.8 Error code

Error codes that are output to output argument ERCD for AGA_3, AGA_7, and AGA_R are
shown in the following table:
Table Appendix 1.2.8-1 List of error codes that are output to ERCD
Error code Description
0 Normal calculation
-3 Gas composition does not add up to 1.0 (100%)
-4 Bad tap location
-5 Compressibility check failed
-6 Pressure ratio out of range
-7 Flow temp out of range when retrieving linear coefficient of thermal expansion
-9 Division by zero error (AGA3)
-12 Invalid calculation type selection
-13 Invalid atmospheric pressure calc. selection
-14 Invalid specific gravity calc. selection
-15 Invalid orifice plate material
-16 Invalid pipe material
-17 Invalid static pressure tap location
-23 Orifice diameter >= pipe diameter
-25 Incorrect compressibility calculation selection
-26 Bad heating value
-27 Bad reference temperature for heating value
-28 N2, CO2, H2, and CO cannot all be zero
-29 N2, CO2, H2, or CO cannot all be less than zero
-30 Bad specific gravity
-31 Bad reference temperature for specific gravity
-32 Bad reference pressure for specific gravity
-34 GPA2172 Gas composition does not add up to 1.0 (100%)
-35 GPA2172 Division by zero error (base pressure)
-36 AGA3 flow calculation is failed.
-37 N2 and CO2, or CO2 is out of range.
-102 Division by zero error (AGA Report)
-103 Bad PULSE
-104 Bad reference pressure for molar density

<Appendix 2. Structure of function blocks of gas flow rate calculation function > App.2-1
Appendix 2. Structure of function blocks

of gas flow rate calculation
function
The structure of function blocks of gas flow calculation function are as follows: A structure is a
combination of the basic data types.
Table Appendix 2-1 Structure of function blocks of gas flow rate calculation function
Data type Description
AGA_3_PARAM AGA_3_PARAM type
The structure used in AGA_3 block.
AGA_3_OUTPUT AGA_3_OUTPUT type
AGA_7_PARAM AGA_7_PARAM type
AGA_7_OUTPUT AGA_7_OUTPUT type
AGA_COMPOSITION AGA_COMPOSITION type
The structure used in AGA_3, AGA_7, AGA_R blocks.
AGA_R_PARAM AGA_R_PARAM type
The structure used in AGA_R block.
AGA_CALC_DATA AGA_CALC_DATA type
The structure used in AGA_3, AGA_7, AGA_R blocks.
AGA_RP_H AGA_RP_H type
AGA_RP_D AGA_RP_D type
AGA_RP_M AGA_RP_M type
n AGA_3_PARAM structure
The following table describes the configuration of AGA_3_PARAM structure.
Table Appendix 2-2 AGA_3_PARAM structure

Parameter name Data type Description Unit Closing
US SI process
upon pa-
rameter
change
METER_NAME STRING Meter Name. - - Yes
(16)
AGA8_METHOD_SE- DINT AGA8 calculation method - - Yes
LECT selection:
0: Detail
1: Gross Method1
2: Gross Method2
ATMPRESS_CAL_SE- DINT Atmospheric pressure - - Yes
LECT calculation selection:
1: Calculated
2: Manual

Table Appendix 2-2 AGA_3_PARAM structure (Table continued)
US SI process
upon pa-
rameter
change
SG_CAL_SELECT DINT Specific gravity calcula- - - Yes
tion selection:
1: Calculated
2: Manual
COMP_NORMAL- DINT Normalize composition: - - Yes
IZE_SELECT 0: No
1: Yes
DEFAULT_TEMP_SE- DINT Default temperature se- - - No
LECT lection:
1: No
2: If input fails
3: Always
ENERGY_CAL_SELECT DINT Energy calculation: - - Yes
0: Manual
2: GPA2172
HV_Z_SELECT DINT Compressibility Factor - - No
Selection:
0: AGA8
1: GPA2172
SP_SELECT DINT Static pressure selection: - - Yes
1: Absolute
2: Gauge
UNIT_SELECT DINT Input unit selection: - - Yes
1: US
2: SI
COMP_INPUT_SELECT DINT Composition input selec- - - No
tion:
1: Manual
2: Live
FIXED_ATMPRESS REAL Atmospheric pressure psia kPa No
REF_TEMP REAL Reference temperature deg. F deg. C No
DP_CUTOFF REAL Differential pressure cut- inH2O kPa Yes
off
DEFAULT_TEMP REAL Default temperature deg. F deg. C No
AGA3_CF REAL AGA3 Correction Factor - - Yes
SP_MNT DINT Static pressure Mainte- - - No
nance mode:
0: No
1: Last good value
DP_MNT DINT Differential pressure - - No
Maintenance mode:
0: No
1: Last good value
T_MNT DINT Flow temperature Mainte- - - No
nance mode:
0: No
1: Last good value

US SI process
upon pa-
rameter
change
SP_MNT_VALUE REAL Static pressure at mainte- psi kPa No
nance mode
DP_MNT_VALUE REAL Differential pressure at inH2O kPa No
maintenance mode
T_MNT_VALUE REAL Flow temperature at deg. F deg. C No
maintenance mode
LATITUDE REAL Latitude Degree Degree Yes
ALTITUDE REAL Altitude ft m Yes
BASE_TEMP REAL Base temperature deg. F deg. C Yes
BASE_PRESS REAL Base pressure psia kPa Yes
PIPE_DIAMETER REAL Meter diameter in mm Yes
ORIFICE_DIAMETER REAL Orifice diameter in mm Yes
PIPE_MATERIAL DINT Meter material: - - Yes
1: Stainless steel
2: Monel
3: Carbon steel
ORIFICE_MATERIAL DINT Orifice material: - - Yes
1: Stainless steel
2: Monel
3: Carbon steel
TAP_LOCATION DINT Static pressure tap loca- - - Yes
tion:
1: Upstream
2: Downstream
ISENTROPIC_K REAL Isentropic expansion - - Yes
VISCOSITY REAL Viscosity lbm/(ft*sec) cP Yes
FIXED_SG REAL User entered specific - - Yes
gravity
GROSS_HV REAL Gross method Heating BTU/ft3 kJ/m3 Yes
Value
GROSS_REFTEMP_HV REAL Gross method reference deg. F deg. C Yes
temperature for heating
value.
GROSS_REFTEMP_MD REAL Gross method reference deg. F deg. C Yes
temperature for molar
density
GROSS_REFTEMP_SG REAL Gross method reference deg. F deg. C Yes
temperature for relative
density
GROSS_REF- REAL Gross method reference psia kPa Yes
PRESS_MD pressure for molar densi-
ty
PRESS_SG pressure for relative den-
sity
RELATIVE_HUMIDITY REAL GPA2172 Relative hu- - - No
midity

US SI process
upon pa-
rameter
change
HUMIDITY_OF_GAS REAL GPA2172 Humidity of gas - - No
FRACTION_OF_EX- REAL GPA2172 Fraction of ex- - - No
CESS_AIR cess air
WET_ANALYSIS DINT GPA2172 Saturated - - No
Analysis:
0: Dry Gas
OPT01 DINT Reserved. Always set up - - No
0.
0.
OPT03 REAL Reserved. Always set up - - No
0.0.
0.0.
Closing process upon parameter change

Yes: Execute the closing processing when a parameter value is changed.
No: Does not execute the closing processing when a parameter value is changed.
n AGA_3_OUTPUT structure
The configuration of AGA_3_OUTPUT structure is shown in the following table:
Table Appendix 2-3 AGA_3_OUTPUT structure

Parameter name Data type Description Unit
US SI
Z_FLOW REAL Compressibility at flowing - -
condition
Z_BASE REAL Compressibility at base con- - -
dition
CALCULATED_AP REAL Calculated Atmospheric psia kPa
Pressure
COMP_TOTAL REAL Total of composition (should - -
be 1.00 or so)
MRHO_BASE REAL Molar density at base condi- lb-mol/ft3 kmol/m3
tion
RHO_BASE REAL Mass density at base condi- lbm/ft3 kg/m3
tion
MRHO_FLOW REAL Molar density at flowing con- lb-mol/ft3 kmol/m3
dition
RHO_FLOW REAL Mass density at flowing con- lbm/ft3 kg/m3
dition
AGA3_Y1 REAL AGA3 Upstream expansion - -
factor
AGA3_CD REAL AGA3 Coefficient of dis- - -
charge

Table Appendix 2-3 AGA_3_OUTPUT structure (Table continued)
US SI
AGA3_EV REAL AGA3 Velocity of approach - -
factor
FPV REAL Legacy factor Fpv - -
n AGA_7_PARAM structure
The configuration of AGA_7_PARAM structure is as follows:
Table Appendix 2-4 AGA_7_PARAM structure

US SI process
upon pa-
rameter
change
METER_NAME STRING Meter Name - - Yes
(16)
FLOW_CAL_SELECT DINT Flow calculation algo- Yes
rithm
2: Turbine (AGA7)
5: Ultrasonic
AGA8_METHOD_SE- DINT AGA8 calculation method - - Yes
LECT selection
0: Detail
1: Gross Method1
2: Gross Method2
ATMPRESS_CAL_SE- DINT Atmospheric pressure - - Yes
LECT calculation selection
1: Calculated
2: Manual
SG_CAL_SELECT DINT Specific gravity calcula- - - Yes
tion selection
1: Calculated
2: Manual
COMP_NORMAL- DINT Normalize composition - - Yes
IZE_SELECT 0: No
1: Yes
DEFAULT_TEMP_SE- DINT Default temperature se- - - No
LECT lection
1: No
2: If input fails
3: Always
ENERGY_CAL_SELECT DINT Energy calculation - - Yes
0: Manual
2: GPA2172
HV_Z_SELECT DINT Compressibility Factor - - No
Selection
0: AGA8
1: GPA2172
SP_SELECT DINT Static pressure selection - - Yes
1: Absolute
2: Gauge
UNIT_SELECT DINT Input unit selection - - Yes
1: US
2: SI

US SI process
upon pa-
rameter
change
COMP_INPUT_SELECT DINT Composition input selec- - - No
tion
1: Manual
2: Live
FIXED_ATMPRESS REAL Atmospheric pressure psia kPa No
PULSE_CUTOFF REAL Total Pulse cutoff - - Yes
DEFAULT_TEMP REAL Default temperature degF degC No
AGA3_CF REAL Meter Factor - - Yes
SP_MNT DINT Static pressure Mainte- - - No
nance mode
0: No
1: Last good value
T_MNT DINT Flow temperature Mainte- - - No
nance mode
0: No
1: Last good value
PULS_MNT DINT Pulse Maintenance mode - - No
0: No
1: Last good value
SP_MNT_VALUE REAL Static pressure at mainte- psi kPa No
nance mode
T_MNT_VALUE REAL Flow temperature mainte- degF degC No
nance mode
PULS_MNT_VALUE REAL Pulses at maintenance - - No
mode
LATITUDE REAL Latitude Degree Degree Yes
ALTITUDE REAL Altitude ft m Yes
BASE_TEMP REAL Base temperature degF degC Yes
BASE_PRESS REAL Base pressure psia kPa Yes
FIXED_SG REAL User entered specific - - Yes
gravity
GROSS_HV REAL Gross method Heating BTU/ft3 kJ/m3 Yes
Value
GROSS_REFTEMP_HV REAL Gross method reference degF degC Yes
temperature for heating
value
GROSS_REFTEMP_MD REAL Gross method reference degF degC Yes
temperature for molar
density
GROSS_REFTEMP_SG REAL Gross method reference degF degC Yes
temperature for relative
density
PRESS_MD pressure for molar densi-
ty

US SI process
upon pa-
rameter
change
PRESS_SG pressure for relative den-
sity
PULSE_K REAL Pulse input K factor Pulses/ft3 Pulses/m3 Yes
RELATIVE_HUMIDITY REAL GPA2172 Relative hu- - - No
midity
HUMIDITY_OF_GAS REAL GPA2172 Humidity of gas - - No
FRACTION_OF_EX- REAL GPA2172 Fraction of ex- - - No
CESS_AIR cess air
WET_ANALYSIS DINT GPA2172 Saturated - - No
Analysis
0: Dry Gas
0.
0.
0.0.
0.0.

n AGA_7_OUTPUT structure
The configuration of AGA_7_OUTPUT structure is shown in the following table:
Table Appendix 2-5 AGA_7_OUTPUT structure

US SI
Z_FLOW REAL Compressibility at flowing - -
condition
Z_BASE REAL Compressibility at base con- - -
dition
CALCULATED_AP REAL Calculated Atmospheric psia kPa
Pressure
COMP_TOTAL REAL Total of composition (should - -
be 1.00 or so)
SOS REAL AGA10 calculated speed of ft/s m/s
sound
MRHO_BASE REAL Molar density at base condi- lb-mol/ft3 kmol/m3
tion
RHO_BASE REAL Mass density at base condi- lbm/ft3 kg/m3
tion

Table Appendix 2-5 AGA_7_OUTPUT structure (Table continued)
US SI
MRHO_FLOW REAL Molar density at flowing con- lb-mol/ft3 kmol/m3
dition
RHO_FLOW REAL Mass density at flowing con- lbm/ft3 kg/m3
dition
AGA7_QF REAL Uncorrected flow in ft3/day - -
FPV REAL Legacy factor Fpv - -
n AGA_COMPOSITION structure
The following table describes the configuration of AGA_COMPOSITION structure.
Table Appendix 2-6 AGA_COMPOSITION structure

Parameter name Data type Description
METHANE REAL Methane CH4
NITROGEN REAL Nitrogen N2
CARBON_DIOXIDE REAL Carbon dioxide C02
ETHANE REAL Ethane C2H6
PROPANE REAL Propane C3H8
WATER REAL Water H2O
HYDROGEN_SULFIDE REAL Hydrogen sulphide H2S
HYDROGEN REAL Hydrogen H2
CARBON_MONOXIDE REAL Carbon monoxide CO
OXYGEN REAL Oxygen O2
I_BUTANE REAL i-Butane IC4H10
N_BUTANE REAL n-Butane NC4H10
I_PENTANE REAL i-Pentane IC5H10
N_PENTANE REAL n-Pentane NC5H10
N_HEXANE REAL n-Hexane C6H14
N_HEPTANE REAL n-Heptane C7H16
N_OCTANE REAL n-Octane C8H18
N_NONANE REAL n-Nonane C9H20
N_DECANE REAL n-Decane C10H22
HELIUM REAL Helium He
ARGON REAL Argon Ar
n AGA_R_PARAM structure
The configuration of AGA_R_PARAM structure is as follows:

Table Appendix 2-7 AGA_R_PARAM structure
Parameter name Data type Description Closing proc-
ess upon pa-
rameter change
CONTRACT_HOUR DINT Contract hour: 0-23 (Daily close No
hour)
CONTRACT_DAY DINT Contract day: 1-31 (Monthly close No
day)
SP_AVE_SELECT DINT Average method for SP Yes
1: Flow-dependent time-weighted
linear
2: Flow-weighted linear
DP_AVE_SELECT DINT Average method for DP Yes
linear
TEMP_AVE_SELECT DINT Average method for TEMP Yes
linear
COMP_AVE_SELECT DINT Average method for gas composi- Yes
tion
0: Scan count
linear
INIT_CURH_DATA_Q BOOL Initialize current hour data. (Reset No
current SUM and average)
Reset by rising from FALSE to
TRUE.
INIT_PREH_DATA_Q BOOL Initialize previous hour data. (Re- No
set PREH_* variables)
TRUE.
INIT_TDAY_DATA_Q BOOL Initialize today data. (Reset today No
SUM and average)
TRUE.
INIT_YDAY_DATA_Q BOOL Initialize yesterday data. (Reset No
YDAY_* variables)
TRUE.
INIT_CMON_DATA_Q BOOL Initialize current month data. (Re- No
set current month variables)
TRUE.
INIT_ALL_DATA_Q BOOL Initialize all report data. (SUM, No
Production time etc.)
TRUE.
FORCE_CLOSE BOOL Forced closing flag No
When a rise is detected, average
value calculation and integrated
value calculation are closed. How-
ever the next closing time is not
updated.
OPT01 DINT Reserved. Always set up 0. No
OPT02 DINT Reserved. Always set up 0. No

n AGA_CALC_DATA structure
AGA_CALC_DATA structure is used to connect AGA_3 or AGA_7 to AGA_R.
Table Appendix 2-8 AGA_CALC_DATA structure

US SI
METER_NAME STRING (16) Meter Name - -
FLOW_CAL_SELECT DINT Flow calculation algorithm - -
1: Orifice (AGA3)
2: Turbine (AGA7)
5: Ultrasonic
SP_IN REAL Static pressure psi kPa
DP_IN REAL Differential pressure inH2O kPa
T_IN REAL Temperature degF degC
Q_BASE REAL Calculated,Daily flow rate mmcf/d e3m3/d
(Q_BASE)
ENERGY REAL Energy mbtu/d GJ/d
Q_FLOW REAL Calculated,Daily flow mmcf/d e3m3/d
Q_MASS REAL Reserve: Always 0. - -
PULSE_TOTAL REAL Total pulses (AGA7 calcula- - -
ted)
UNIT_SELECT DINT Input unit selection - -
1: US
2: SI
CALCULATED_SG REAL Calculated specific gravity - -
(Ideal)
CALCULATED_REAL_SG REAL Calculated specific gravity - -
(Real) (Compressibility of air
@ 60 degF 14.696 psia)
CALCULATED_HV REAL Calculated Heating Value btu/ft3 MJ/m3
CALCULATED_ID_HV REAL Calculated Ideal Heating Val- btu/ft3 MJ/m3
ue
COMPOSITION AGA_COM- Normalized gas composition - -
POSITION
CONF_Q BOOL Configuration changed - -
COMP_Q BOOL Composition changed - -
n AGA_RP_H structure
AGA_RP_H structure is used for the output parameters in the AGA_R block: It stores hourly
closing report data.

Table Appendix 2-9 AGA_RP_H structure
US SI
AVE_SP REAL Average static pressure psi kPa
AVE_DP REAL Average differential pressure inH2O kPa
AVE_TEMP REAL Average temperature degF degC
AVE_FLOW REAL Average flow rate mmcf/d e3m3/d
AVE_FLOW_RAW REAL Averaged flow rate at flowing mmcf/d e3m3/d
condition
AVE_ENERGY REAL Average energy mbtu/d GJ/d
AVE_MASS REAL Reserved: Always 0. - -
TOTAL_FLOW REAL Total flow mmcf e3m3
RAW_VOLUME REAL Total uncorrected flow mmcf e3m3
TOTAL_ENERGY REAL Total energy mbtu/d GJ/d
TOTAL_MASS REAL Reserved: Always 0. - -
PRODUCTION_TIME REAL Production time min min
SHUT_TIME REAL Shut in time min min
PULSES REAL Pulse - -
ACCUM_VOLUME REAL Accumulated flow at end mmcf e3m3
TIMESTAMP_SEC DINT Time stamp - -
AVE_COMPOSITION AGA_COM- Normalized gas composition - -
POSITION (Averaged)
AVE_CALCULATED_RE- REAL Averaged calculated specific - -
AL_SG gravity (Real)
AVE_CALCULATED_SG REAL Averaged calculated specific - -
gravity (Ideal)
AVE_CALCULATED_HV REAL Averaged calculated heating btu/ft3 MJ/m3
value
AVE_CALCULATED_ID_HV REAL Averaged calculated ideal btu/ft3 MJ/m3
heating value
n AGA_RP_D structure
AGA_RP_D structure is used for the output parameters in the AGA_R block: It stores daily
closing report data.
Table Appendix 2-10 AGA_RP_D structure

US SI
AVE_SP REAL Average static pressure psi kPa
AVE_DP REAL Average differential pressure inH2O kPa
AVE_TEMP REAL Average temperature degF degC
AVE_FLOW REAL Average flow rate mmcf/d e3m3/d
AVE_FLOW_RAW REAL Averaged flow rate at flowing mmcf/d e3m3/d
condition
AVE_ENERGY REAL Average energy mbtu/d GJ/d
AVE_MASS REAL Reserved: Always 0. - -

Table Appendix 2-10 AGA_RP_D structure (Table continued)
US SI
TOTAL_FLOW REAL Total flow mmcf e3m3
RAW_VOLUME REAL Total uncorrected flow mmcf e3m3
TOTAL_ENERGY REAL Total energy mbtu/d GJ/d
TOTAL_MASS REAL Reserved: Always 0. - -
PRODUCTION_TIME REAL Production time min min
SHUT_TIME REAL Shut in time min min
PULSES REAL Pulse - -
ACCUM_VOLUME REAL Accumulated flow at end mmcf e3m3
TIMESTAMP_SEC DINT Time stamp - -
AVE_COMPOSITION AGA_COM- Normalized gas composition - -
POSITION
AVE_CALCULATED_RE- REAL Averaged calculated specific - -
AL_SG gravity (Real)
AVE_CALCULATED_SG REAL Averaged calculated specific - -
gravity (Ideal)
AVE_CALCULATED_HV REAL Averaged calculated heating btu/ft3 MJ/m3
value
AVE_CALCULATED_ID_HV REAL Averaged calculated ideal btu/ft3 MJ/m3
heating value
n AGA_RP_M structure
AGA_RP_M structure is a structure used for the output parameter of AGA_R block. This con-
tains monthly report data.
Table Appendix 2-11 AGA_RP_M structure

US SI
TOTAL_FLOW REAL Total flow lbm/d kg/d

<Appendix 3. Mapping blocks and mapping elements for FAST/TOOLS Integration> App.3-1
Appendix 3. Mapping blocks and

mapping elements for FAST/
TOOLS Integration
This section describes the mapping blocks and mapping elements for FAST/TOOL Integra-
tion.
n Mapping blocks/elements that can be accessed by FAST/TOOLS

The mapping blocks/elements that can be accessed by FAST/TOOLS using a tag name are
as follows:
Table Appendix 3-1 Mapping blocks/elements that can be accessed by FAST/TOOLS

Class Description Defined in application log- Mapping blocks/elements Access
ics availa-
Class Type Class Block/ bility (*1)
element sym-
bol
Simple varia- Boolean type Simple varia- BOOL Mapping ele- %WB R
ble ble ment
Integer type con- Simple varia- DINT Mapping ele- %WB R
tinuous value (32 ble ment
bits)
Actual number Simple varia- REAL Mapping ele- %WB R
type continuous ble ment
value (32 bits)
I/O variables Contact point I/O structure IO_BOOL Mapping ele- %Z R
ment
Analog I/O structure IO_REAL Mapping ele- %WB R
ment
Data setting Data Set (BOOL) FB ECW_B Mapping ele- %WB R/W
from an exter- ment
nal device
Data Set (Integer) FB ECW_I Mapping ele- %WB R/W
ment
Data Set (Real) FB ECW_R Mapping ele- %WB R/W
ment
Data setting with FB ECWR_B Mapping ele- %WB R/W
Data retaining ment
function (BOOL)
(*2)
Data setting with FB ECWR_I Mapping ele- %WB R/W
Data retaining ment
function (Integer)
(*2)
Data setting with FB ECWR_R Mapping ele- %WB R/W
Data retaining ment
function (Real) (*2)
Analog Input Analog Input indi- FB ANLGI Mapping S_ANLGI R
indicator cator block
(*3)
Analog input block FB ANLG_S Mapping S_ANLG_S R
with data status block

Table Appendix 3-1 Mapping blocks/elements that can be accessed by FAST/TOOLS (Table continued)
Class Description Defined in application log- Mapping blocks/elements Access
ics availa-
Class Type Class Block/ bility (*1)
element sym-
bol
Change rate Velocity Limit FB VEL Mapping S_VEL R
Alarm Block (*4) block
Annunciator Annunciator FB ANN Mapping ele- %AN R
ment
First-up Alarm An- FB ANN_FUP Mapping ele- %AN R
nunciator ment
Subsystem Subsystem Com- FB SCI_B Mapping ele- %WB R
Communica- munication Input ment
tion I/O (BOOL)
Subsystem Com- FB SCI_I Mapping ele- %WB R
munication Input ment
(Integer) (*5)
Subsystem Com- FB SCI_R Mapping ele- %WB R
munication Input ment
(Real)
Subsystem Com- FB SCO_B Mapping ele- %WB R
munication Output ment
(BOOL)
Subsystem Com- FB SCO_I Mapping ele- %WB R
(Integer) (*5)
Subsystem Com- FB SCO_R Mapping ele- %WB R
(Real)
Gas flow rate AGA3 calculation FB AGA_3 Mapping S_AGA_3 R
calculation (*2) block
AGA7 calculation FB AGA_7 Mapping S_AGA_7 R
(*2) block
Report data crea- FB AGA_R Mapping S_AGA_R R
tion (*2) block
Tag name of -- -- -- System SW %SW R
system SW
(*6)
*1: Access availability from FAST/TOOLS to mapping blocks/elements

R: Readable
W: Writable
*2: Available SCSU1 only.
*3: ANLG_S retains the equivalent function. Special engineering is necessary on the FAST/TOOLS side to access from FAST/
TOOLS though ANLGI can be referred.
*4: VEL can be referred but special engineering is necessary on the FAST/TOOLS side to access from FAST/TOOLS. Or, VEL
can be substituted by logic.
*5: Special engineering is necessary on the FAST/TOOLS side to access from FAST/TOOLS because SCI_I and SCO_I can be
referred but cannot generate data items (PVI16, PVI32, PVU16) automatically.
*6: %SW cannot be defined. Accessible only with system element name (%SWxxxx).
n Data items of mapping blocks/elements

FAST/TOOLS can access the following data items of mapping blocks/elements. The items are
indicated with R (Read) and W (Write) to show that FAST/TOOLS can read or write the data
items.

SEE
ALSO For more information about the data items of mapping elements, refer to:
D2., “Tag name interfaces for CENTUM” in Safety Control Station Reference (IM 32Q03B10-31E)
l Internal variables
To access different types of internal variables, use the following data items of the correspond-
ing mapping element.
Table Appendix 3-2 Accessible data items of mapping elements for internal variables
Type (mapping ele-
Data item Range R/W
ment)
BOOL (%WB) PV 0, 1 R
DINT (%WB) PVI32 32-bit signed integer R
REAL (%WB) PVF32 Single-precision real R
l I/O variables
To access different types of I/O variables, use the following data items of the corresponding
mapping element.
Table Appendix 3-3 Accessible data items of mapping elements for I/O variables
Type (mapping ele-
Data item Range R/W
ment)
IO_BOOL (%Z) PV 0, 1 R
IO_REAL (%WB) PVF32 Single-precision real R
l External communication function block

To access data of function blocks, use the following data items of the corresponding mapping
element.
Table Appendix 3-4 Data items of mapping elements for external communication function block and
external communication function block with data retaining function
Type (mapping ele-
FB type Data item Range R/W
ment)
ECW_B (%WB) PV 0, 1 R/W
External
communica- ECW_I (%WB) PVI32 32-bit signed integer R/W
tion FB
ECW_R (%WB) PVF32 Single-precision real R/W
External ECWR_B (%WB) PV 0, 1 R/W
communica-
tion function ECWR_I (%WB) PVI32 32-bit signed integer R/W
block with
data retain- ECWR_R (%WB) PVF32 Single-precision real R/W
ing function
l Analog Input with Data Status

To access data of function block ANLG_S, use the following data items of mapping block
S_ANLG_S.
Table Appendix 3-5 Data items of mapping block (S_ANLG_S) for ANLG_S
Data item Range R/W
MODE Mode of the block R

Table Appendix 3-5 Data items of mapping block (S_ANLG_S) for ANLG_S (Table continued)
Data item Range R/W
ALRM Alarm status R
AOFS 0, 1 R/W (*1)
INV Normalized data (0 to 100%) or range of physical quantity R
Normalized data after scale conversion (0 to 100%) or
PV R
range of physical quantity
HH (*2) R
PH (*2) R
PL (*2) R
LL (*2) R
HYS (*2) R
SH (*3) R
SL (*3) R
*1: Writing to this data item does not change the SCS action. The value is reset to 0 after restarting SCS.
*2: The value of the data item of ANLG_S with the same name is reflected as it is.
*3: The value defined on Tag Name Builder.
l Annunciator
To access data of function block ANN or ANN_FUP, use the following data items of %AN. Use
Tag Name Builder to define the annunciator message.
Table Appendix 3-6 Data items of mapping element (%AN) for ANN/ANN_FUP
Data item Range R/W
ALRM Alarm status R
AOFS 0, 1 R/W
PV 0, 1 R
l Subsystem communication I/O function blocks

To access data of the subsystem communication I/O function blocks, use the following data
items of the corresponding mapping element.
Table Appendix 3-7 Data items of mapping elements for subsystem communication I/O function
blocks
Type (mapping ele-
Data item Range R/W
ment)
SCI_B (%WB) PV 0, 1 R
SCI_R (%WB) PVF32 Single-precision real R
SCO_B (%WB) PV 0, 1 R
SCO_R (%WB) PVF32 Single-precision real R
n Data item that can be referenced and set

Data item that can be referenced and set by FAST/TOOLS includes:
• Mapping blocks (AGA_3/AGA_7)
• Mapping blocks (AGA_R)

l Mapping block (AGA_3 and AGA_7)
Table Appendix 3-8 Data item that can be referenced and set by AGA_3 and AGA_7 mapping block
Data Item Accessibility (*1) Parameter to map Description Parameter
AGA_3 AGA_7 (*2)
MODE R R - - -
ALRM R R - Always NR -
EXEC R R EXEC (*3) Calculation execution IN
status
(0: Stopped, 1: Calcu-
lating)
SP R R SP Static pressure IN
Status of SP
DP R - DP Differential pressure IN
Status of DP
T R R T Flow temperature IN
Status of T
PULS - R PULS Pulse count per Scan IN
Period
Status of PULS
SET R R SET PARA and COMP ac- IN
ceptance flags
CPS R R CP_S Status of COMP IN
NOFL R R NOFL Gas production sus- OUT
pended flag
ERCD R R ERCD Error code OUT
METERNM R R METER_NAME Meter Name Internal
FLSEL R R FLOW_CAL_SELECT Flow calculation algo- Internal
rithm
1: Orifice (AGA3)
2: Turbine (AGA7)
5: Ultrasonic
AGA8SEL R R AGA8_METHOD_SE- AGA8 calculation Internal
LECT method selection
0: Detail
1: Gross Method1
2: Gross Method2
ATMSEL R R ATM- Atmospheric pressure Internal
PRESS_CAL_SE- calculation selection
LECT 1: Calculated
2: Manual
SGSEL R R SG_CAL_SELECT Specific gravity calcu- Internal
lation selection
1: Calculated
2: Manual
CMPNRSL R R COMP_NORMAL- Normalize composi- Internal
IZE_SELECT tion
0: No
1: Yes
DFTMPSL R R DEFAULT_TEMP_SE- Default temperature Internal
LECT selection
1: No
2: If input fails
3: Always

(Table continued)
AGA_3 AGA_7 (*2)
ENRGYSL R R ENERGY_CAL_SE- Energy calculation Internal

LECT 0: Manual
2: GPA2172
HVZSEL R R HV_Z_SELECT Compressibility Factor Internal
Selection
0: AGA8
1: GPA2172
SPSEL R R SP_SELECT Static pressure selec- Internal
tion
1: Absolute
2: Gauge
UNITSEL R R UNIT_SELECT Input unit selection Internal
1: US
2: SI
CMPINSL R R COMP_INPUT_SE- Composition input se- Internal
LECT lection
1: Manual
2: Live
FIXDATM R R FIXED_ATMPRESS Atmospheric pressure Internal
REFTEMP R - REF_TEMP Reference tempera- Internal
ture
DPCTOFF R - DP_CUTOFF Differential pressure Internal
cutoff
PLCTOFF - R PULSE_CUTOFF Total Pulse cutoff Internal
DEFTEMP R R DEFAULT_TEMP Default temperature Internal
AGA3CF R R AGA3_CF (AGA_3) AGA3 Cor- Internal
rection Factor/
(AGA_7) Meter Factor
SPMNT R R SP_MNT Static pressure Main- Internal
tenance mode
0: No
1: Last good value
DPMNT R - DP_MNT Differential pressure Internal
Maintenance mode
0: No
1: Last good value
TMNT R R T_MNT Flow temperature Internal
Maintenance mode
0: No
1: Last good value
PULSMNT - R PULS_MNT Pulses Maintenance Internal
mode
0: No
1: Last good value
SPMNTVL R R SP_MNT_VALUE Static pressure at Internal
maintenance mode
DPMNTVL R - DP_MNT_VALUE Differential pressure at Internal
maintenance mode

(Table continued)
AGA_3 AGA_7 (*2)
TMNTVAL R R T_MNT_VALUE Flow temperature at Internal

maintenance mode
PLMNTVL - R PULS_MNT_VALUE Pulses at mainte- Internal
nance mode
LATITUD R R LATITUDE Latitude Internal
ALTITUD R R ALTITUDE Altitude Internal
BSTEMP R R BASE_TEMP Base temperature Internal
BSPRESS R R BASE_PRESS Base pressure Internal
PIPEDMT R - PIPE_DIAMETER Meter diameter Internal
ORFCDMT R - ORIFICE_DIAMETER Orifice diameter Internal
PIPEMTR R - PIPE_MATERIAL Meter material Internal
1: Stainless steel
2: Monel
3: Carbon steel
ORFCMTR R - ORIFICE_MATERIAL Orifice material Internal
1: Stainless steel
2: Monel
3: Carbon steel
TAPLOC R - TAP_LOCATION Static pressure tap lo- Internal
cation
1: Upstream
2: Downstream
ISTRPCK R - ISENTROPIC_K Isentropic expansion Internal
VISCSTY R - VISCOSITY Viscosity Internal
FIXEDSG R R FIXED_SG User entered specific Internal
gravity
GRSHV R R GROSS_HV Gross method Heating Internal
Value
GRSRTHV R R GROSS_RE- Gross method refer- Internal
FTEMP_HV ence temperature for
heating value
GRSRTMD R R GROSS_RE- Gross method refer- Internal
FTEMP_MD ence temperature for
molar density
GRSRTSG R R GROSS_RE- Gross method refer- Internal
FTEMP_SG ence temperature for
relative density
GRSRPMD R R GROSS_REF- Gross method refer- Internal
PRESS_MD ence pressure for mo-
lar density
GRSRPSG R R GROSS_REF- Gross method refer- Internal
PRESS_SG ence pressure for rela-
tive density
PULSEK - R PULSE_K Pulse input K factor Internal
RLHMDTY R R RELATIVE_HUMIDI- GPA2172 Relative hu- Internal
TY midity
HMDTYGS R R HUMIDITY_OF_GAS GPA2172 Humidity of Internal
gas

(Table continued)
AGA_3 AGA_7 (*2)
FREXAIR R R FRACTION_OF_EX- GPA2172 Fraction of Internal

CESS_AIR excess air
WTANLYS R R WET_ANALYSIS GPA2172 Saturated Internal
Analysis
0: Dry Gas
METHAN R R METHANE Methane CH4 Internal
NTRGN R R NITROGEN Nitrogen N2 Internal
CBNDXD R R CARBON_DIOXIDE Carbon dioxide C02 Internal
ETHANE R R ETHANE Ethane C2H6 Internal
PROPAN R R PROPANE Propane C3H8 Internal
WATER R R WATER Water H2O Internal
HYDSLF R R HYDROGEN_SUL- Hydrogen sulphide Internal
FIDE H2S
HYDRGN R R HYDROGEN Hydrogen H2 Internal
CBNMNX R R CARBON_MONOX- Carbon monoxide CO Internal
IDE
OXYGEN R R OXYGEN Oxygen O2 Internal
IBUTAN R R I_BUTANE i-Butane IC4H10 Internal
NBUTAN R R N_BUTANE n-Butane NC4H10 Internal
IPENTN R R I_PENTANE i-Pentane IC5H10 Internal
NPENTN R R N_PENTANE n-Pentane NC5H10 Internal
NHEXAN R R N_HEXANE n-Hexane C6H14 Internal
NHEPTN R R N_HEPTANE n-Heptane C7H16 Internal
NOCTAN R R N_OCTANE n-Octane C8H18 Internal
NNONAN R R N_NONANE n-Nonane C9H20 Internal
NDECAN R R N_DECANE n-Decane C10H22 Internal
HELIUM R R HELIUM Helium He Internal
ARGON R R ARGON Argon Ar Internal
SPIN R R CDAT.SP_IN Static pressure OUT
DPIN R R CDAT.DP_IN Differential pressure OUT
TIN R R CDAT.T_IN Temperature OUT
QBASE R R CDAT.Q_BASE Calculated,Daily flow OUT
rate (Q_BASE)
ENERGY R R CDAT.ENERGY Energy OUT
QFLOW R R CDAT.Q_FLOW Calculated,Daily flow OUT
PLSTTL R R CDAT.PULSE_TOTAL Total pulses (AGA7 OUT
calculated)
CALCSG R R CDAT.CALCULA- Calculated specific OUT
TED_SG gravity (Ideal)
CLCRLSG R R CDAT.CALCULA- Calculated specific OUT
TED_REAL_SG gravity (Real) (Com-
pressibility of air @ 60
degF 14.696 psia)

(Table continued)
AGA_3 AGA_7 (*2)
CALCHV R R CDAT.CALCULA- Calculated Heating OUT

TED_HV Value
CLCIDHV R R CDAT.CALCULA- Calculated Ideal Heat- OUT
TED_ID_HV ing Value
NMETHAN R R CDAT.COMPOSI- Methane CH4 OUT
TION.METHANE
NNTRGN R R CDAT.COMPOSI- Nitrogen N2 OUT
TION.NITROGEN
NCBNDXD R R CDAT.COMPOSI- Carbon dioxide C02 OUT
TION.CARBON_DI-
OXIDE
NETHANE R R CDAT.COMPOSI- Ethane C2H6 OUT
TION.ETHANE
NPROPAN R R CDAT.COMPOSI- Propane C3H8 OUT
TION.PROPANE
NWATER R R CDAT.COMPOSI- Water H2O OUT
TION.WATER
NHYDSLF R R CDAT.COMPOSI- Hydrogen sulphide OUT
TION.HYDRO- H2S
GEN_SULFIDE
NHYDRGN R R CDAT.COMPOSI- Hydrogen H2 OUT
TION.HYDROGEN
NCBNMNX R R CDAT.COMPOSI- Carbon monoxide CO OUT
TION.CAR-
BON_MONOXIDE
NOXYGEN R R CDAT.COMPOSI- Oxygen O2 OUT
TION.OXYGEN
NIBUTAN R R CDAT.COMPOSI- i-Butane IC4H10 OUT
TION.I_BUTANE
NNBUTAN R R CDAT.COMPOSI- n-Butane NC4H10 OUT
TION.N_BUTANE
NIPENTN R R CDAT.COMPOSI- i-Pentane IC5H10 OUT
TION.I_PENTANE
NNPENTN R R CDAT.COMPOSI- n-Pentane NC5H10 OUT
TION.N_PENTANE
NNHEXAN R R CDAT.COMPOSI- n-Hexane C6H14 OUT
TION.N_HEXANE
NNHEPTN R R CDAT.COMPOSI- n-Heptane C7H16 OUT
TION.N_HEPTANE
NNOCTAN R R CDAT.COMPOSI- n-Octane C8H18 OUT
TION.N_OCTANE
NNNONAN R R CDAT.COMPOSI- n-Nonane C9H20 OUT
TION.N_NONANE
NNDECAN R R CDAT.COMPOSI- n-Decane C10H22 OUT
TION.N_DECANE
NHELIUM R R CDAT.COMPOSI- Helium He OUT
TION.HELIUM
NARGON R R CDAT.COMPOSI- Argon Ar OUT
TION.ARGON

(Table continued)
AGA_3 AGA_7 (*2)
ZFLOW R R CDT2.Z_FLOW Compressibility at OUT

flowing condition
ZBASE R R CDT2.Z_BASE Compressibility at OUT
base condition
CALCAP R R CDT2.CALCULA- Calculated Atmos- OUT
TED_AP pheric Pressure
CMPTTL R R CDT2.COMP_TOTAL Total of composition OUT
(should be 1.00 or so)
SOS - R CDT2.SOS AGA10 calculated OUT
speed of sound (ft/s or
m/s)
MRHOBS R R CDT2.MRHO_BASE Molar density at base OUT
condition (mol/ft3 or
kmol/m3)
RHOBASE R R CDT2.RHO_BASE Mass density at base OUT
condition (lbm/ft3 or
kg/m3)
MRHOFLW R R CDT2.MRHO_FLOW Molar density at flow- OUT
ing condition (mol/ft3
or kmol/m3)
RHOFLOW R R CDT2.RHO_FLOW Mass density at flow- OUT
ing condition (lbm/ft3
or kg/m3)
AGA3Y1 R - CDT2.AGA3_Y1 AGA3 Upstream ex- OUT
pansion factor
AGA3CD R - CDT2.AGA3_CD AGA3 Coefficient of OUT
discharge
AGA3EV R - CDT2.AGA3_EV AGA3 Velocity of ap- OUT
proach factor
AGA7QF - R CDT2.AGA7_QF Uncorrected flow in OUT
ft3/day
FPV R R CDT2.FPV Legacy factor Fpv OUT
*1: R: Readable
W: Writable
-: Not accessible
*2: Type of the function block parameter to be mapped and its mapped value
IN: Value of the input parameter of the function block
OUT: Value of the output parameter of the function block
Internal: Value of the internal parameter the function block uses for calculation (structures AGA_3_PARAM , AGA_7_PAR-
AM , and GA_COMPOSITION)
*3: The value of the internal parameter that indicates whether the function block is calculating is reflected, not the value of an
input/output parameter.
l Mapping block (AGA_R)
Table Appendix 3-9 Data items of AGA_R mapping block that can be referenced and set
Data item Accessibili- Mapping-from parame- Description Parameter
ty (*1) ter (*2)
MODE R - - -
ALRM R - Always NR -

Table Appendix 3-9 Data items of AGA_R mapping block that can be referenced and set (Table contin-
ued)
ty (*1) ter (*2)
EXEC R EXEC (*3) Calculation execution IN
(status 0: Stopped, 1:
Calculating)
SET R SET Flag specifying to accept IN
PARA.
HRLY R HRLY Hourly closing execution OUT
counter
DYLY R DYLY Daily closing execution OUT
counter
MNLY R MNLY Monthly closing execu- OUT
tion counter
CNFC R CNFC Configuration change OUT
counter
CMPC R CMPC Composition change OUT
counter
ERCD R ERCD Error code. OUT
METERNM R CDAT.METER_NAME Meter Name. IN
CNTRCTH R CONTRACT_HOUR Contract hour (0-23) Internal
(Daily close hour).
CNTRCTD R CONTRACT_DAY Contract hour (1-31) Internal
(Monthly close day).
SPAVSEL R SP_AVE_SELECT Average method for SP: Internal
1: Flow-dependent time-
weighted linear
2: Flow-weighted linear.
DPAVSEL R DP_AVE_SELECT Average method for DP: Internal
weighted linear
TMPAVSL R TEMP_AVE_SELECT Average method for Internal
TEMP:
weighted linear
CMPAVSL R COMP_AVE_SELECT Average method for gas Internal
composition:
0: Scan count
weighted linear
INITCQ R INIT_CURH_DATA_Q Flag specifying the cur- Internal
rent hour's report data to
be reset.
INITPQ R INIT_PREH_DATA_Q Flag specifying the previ- Internal
ous hour's report data to
be reset.
INITTQ R INIT_TDAY_DATA_Q Flag specifying today's Internal
report data to be reset.
INITYQ R INIT_YDAY_DATA_Q Flag specifying the previ- Internal
ous day's report data to
be reset.

ued)
ty (*1) ter (*2)
INITMQ R INIT_CMON_DATA_Q Flag specifying the cur- Internal
rent month's report data
to be reset.
INITAQ R INIT_ALL_DATA_Q Flag specifying the data Internal
of all the reports to be re-
set.
FRCCLS R FORCE_CLOSE Forced closing flag Internal
AVESP R CURH.AVE_SP Average static pressure. OUT
AVEDP R CURH.AVE_DP Average differential pres- OUT
sure.
AVETMP R CURH.AVE_TEMP Average temperature. OUT
AVEFLW R CURH.AVE_FLOW Average flow rate. OUT
AVEFLR R CURH.AVE_FLOW_RAW Averaged flow rate at OUT
flowing condition.
AVEENG R CURH.AVE_ENERGY Average energy. OUT
TTLFLW R CURH.TOTAL_FLOW Total flow. OUT
RAWVLM R CURH.RAW_VOLUME Total uncorrected flow. OUT
TTLENG R CURH.TOTAL_ENERGY Total energy. OUT
PRDTIM R CURH.PRODUC- Production time. OUT
TION_TIME
SHTTIM R CURH.SHUT_TIME Shut in time. OUT
PULSES R CURH.PULSES Pulse OUT
ACMVLM R CURH.ACCUM_VOL- Accumulated flow at end. OUT
UME
TSTMPS R CURH.TIME- Time stamp. OUT
STAMP_SEC
METHAN R CURH.AVE_COMPOSI- Methane CH4. OUT
TION.METHANE
NTRGN R CURH.AVE_COMPOSI- Nitrogen N2. OUT
TION.NITROGEN
CBNDXD R CURH.AVE_COMPOSI- Carbon dioxide C02. OUT
TION.CARBON_DIOX-
IDE
ETHANE R CURH.AVE_COMPOSI- Ethane C2H6. OUT
TION.ETHANE
PROPAN R CURH.AVE_COMPOSI- Propane C3H8. OUT
TION.PROPANE
WATER R CURH.AVE_COMPOSI- Water H2O. OUT
TION.WATER
HYDSLF R CURH.AVE_COMPOSI- Hydrogen sulphide H2S. OUT
TION.HYDROGEN_SUL-
FIDE
HYDRGN R CURH.AVE_COMPOSI- Hydrogen H2. OUT
TION.HYDROGEN
CBNMNX R CURH.AVE_COMPOSI- Carbon monoxide CO. OUT
TION.CARBON_MON-
OXIDE

ued)
ty (*1) ter (*2)
OXYGEN R CURH.AVE_COMPOSI- Oxygen O2. OUT
TION.OXYGEN
IBUTAN R CURH.AVE_COMPOSI- i-Butane IC4H10. OUT
TION.I_BUTANE
NBUTAN R CURH.AVE_COMPOSI- n-Butane NC4H10. OUT
TION.N_BUTANE
IPENTN R CURH.AVE_COMPOSI- i-Pentane IC5H10. OUT
TION.I_PENTANE
NPENTN R CURH.AVE_COMPOSI- n-Pentane NC5H10. OUT
TION.N_PENTANE
NHEXAN R CURH.AVE_COMPOSI- n-Hexane C6H14. OUT
TION.N_HEXANE
NHEPTN R CURH.AVE_COMPOSI- n-Heptane C7H16. OUT
TION.N_HEPTANE
NOCTAN R CURH.AVE_COMPOSI- n-Octane C8H18. OUT
TION.N_OCTANE
NNONAN R CURH.AVE_COMPOSI- n-Nonane C9H20. OUT
TION.N_NONANE
NDECAN R CURH.AVE_COMPOSI- n-Decane C10H22. OUT
TION.N_DECANE
HELIUM R CURH.AVE_COMPOSI- Helium He. OUT
TION.HELIUM
ARGON R CURH.AVE_COMPOSI- Argon Ar. OUT
TION.ARGON
AVRLSG R CURH.AVE_CALCULA- Averaged calculated spe- OUT
TED_REAL_SG cific gravity (real).
AVESC R CURH.AVE_CALCULA- Averaged calculated spe- OUT
TED_SG cific gravity (ideal).
AVEHV R CURH.AVE_CALCULA- Averaged calculated OUT
TED_HV heating value.
AVIDHV R CURH.AVE_CALCULA- Averaged calculated ideal OUT
TED_ID_HV heating value.
PAVESP R PREH.AVE_SP Average static pressure. OUT
PAVEDP R PREH.AVE_DP Average differential pres- OUT
sure.
PAVETMP R PREH.AVE_TEMP Average temperature. OUT
PAVEFLW R PREH.AVE_FLOW Average flow rate. OUT
PAVEFLR R PREH.AVE_FLOW_RAW Averaged flow rate at OUT
flowing condition.
PAVEENG R PREH.AVE_ENERGY Average energy. OUT
PTTLFLW R PREH.TOTAL_FLOW Total flow. OUT
PRAWVLM R PREH.RAW_VOLUME Total uncorrected flow. OUT
PTTLENG R PREH.TOTAL_ENERGY Total energy. OUT
PPRDTIM R PREH.PRODUC- Production time. OUT
TION_TIME
PSHTTIM R PREH.SHUT_TIME Shut in time. OUT

ued)
ty (*1) ter (*2)
PPULSES R PREH.PULSES Pulse OUT
PACMVLM R PREH.ACCUM_VOL- Accumulated flow at end. OUT
UME
PTSTMPS R PREH.TIMESTAMP_SEC Time stamp. OUT
PMETHAN R PREH.AVE_COMPOSI- Methane CH4. OUT
TION.METHANE
PNTRGN R PREH.AVE_COMPOSI- Nitrogen N2. OUT
TION.NITROGEN
PCBNDXD R PREH.AVE_COMPOSI- Carbon dioxide C02. OUT
TION.CARBON_DIOX-
IDE
PETHANE R PREH.AVE_COMPOSI- Ethane C2H6. OUT
TION.ETHANE
PPROPAN R PREH.AVE_COMPOSI- Propane C3H8. OUT
TION.PROPANE
PWATER R PREH.AVE_COMPOSI- Water H2O. OUT
TION.WATER
PHYDSLF R PREH.AVE_COMPOSI- Hydrogen sulphide H2S. OUT
TION.HYDROGEN_SUL-
FIDE
PHYDRGN R PREH.AVE_COMPOSI- Hydrogen H2. OUT
TION.HYDROGEN
PCBNMNX R PREH.AVE_COMPOSI- Carbon monoxide CO. OUT
TION.CARBON_MON-
OXIDE
POXYGEN R PREH.AVE_COMPOSI- Oxygen O2. OUT
TION.OXYGEN
PIBUTAN R PREH.AVE_COMPOSI- i-Butane IC4H10. OUT
TION.I_BUTANE
PNBUTAN R PREH.AVE_COMPOSI- n-Butane NC4H10. OUT
TION.N_BUTANE
PIPENTN R PREH.AVE_COMPOSI- i-Pentane IC5H10. OUT
TION.I_PENTANE
PNPENTN R PREH.AVE_COMPOSI- n-Pentane NC5H10. OUT
TION.N_PENTANE
PNHEXAN R PREH.AVE_COMPOSI- n-Hexane C6H14. OUT
TION.N_HEXANE
PNHEPTN R PREH.AVE_COMPOSI- n-Heptane C7H16. OUT
TION.N_HEPTANE
PNOCTAN R PREH.AVE_COMPOSI- n-Octane C8H18. OUT
TION.N_OCTANE
PNNONAN R PREH.AVE_COMPOSI- n-Nonane C9H20. OUT
TION.N_NONANE
PNDECAN R PREH.AVE_COMPOSI- n-Decane C10H22. OUT
TION.N_DECANE
PHELIUM R PREH.AVE_COMPOSI- Helium He. OUT
TION.HELIUM
PARGON R PREH.AVE_COMPOSI- Argon Ar. OUT
TION.ARGON

ued)
ty (*1) ter (*2)
PAVRLSG R PREH.AVE_CALCULA- Averaged calculated spe- OUT
PAVESC R PREH.AVE_CALCULA- Averaged calculated spe- OUT
PAVEHV R PREH.AVE_CALCULA- Averaged calculated OUT
PAVIDHV R PREH.AVE_CALCULA- Averaged calculated ideal OUT
TAVESP R TDAY.AVE_SP Average static pressure. OUT
TAVEDP R TDAY.AVE_DP Average differential pres- OUT
sure.
TAVETMP R TDAY.AVE_TEMP Average temperature. OUT
TAVEFLW R TDAY.AVE_FLOW Average flow rate. OUT
TAVEFLR R TDAY.AVE_FLOW_RAW Averaged flow rate at OUT
flowing condition.
TAVEENG R TDAY.AVE_ENERGY Average energy. OUT
TTTLFLW R TDAY.TOTAL_FLOW Total flow. OUT
TRAWVLM R TDAY.RAW_VOLUME Total uncorrected flow. OUT
TTTLENG R TDAY.TOTAL_ENERGY Total energy. OUT
TPRDTIM R TDAY.PRODUC- Production time. OUT
TION_TIME
TSHTTIM R TDAY.SHUT_TIME Shut in time. OUT
TPULSES R TDAY.PULSES Pulse OUT
TACMVLM R TDAY.ACCUM_VOLUME Accumulated flow at end. OUT
TTSTMPS R TDAY.TIMESTAMP_SEC Time stamp. OUT
TMETHAN R TDAY.AVE_COMPOSI- Methane CH4. OUT
TION.METHANE
TNTRGN R TDAY.AVE_COMPOSI- Nitrogen N2. OUT
TION.NITROGEN
TCBNDXD R TDAY.AVE_COMPOSI- Carbon dioxide C02. OUT
TION.CARBON_DIOX-
IDE
TETHANE R TDAY.AVE_COMPOSI- Ethane C2H6. OUT
TION.ETHANE
TPROPAN R TDAY.AVE_COMPOSI- Propane C3H8. OUT
TION.PROPANE
TWATER R TDAY.AVE_COMPOSI- Water H2O. OUT
TION.WATER
THYDSLF R TDAY.AVE_COMPOSI- Hydrogen sulphide H2S. OUT
TION.HYDROGEN_SUL-
FIDE
THYDRGN R TDAY.AVE_COMPOSI- Hydrogen H2. OUT
TION.HYDROGEN
TCBNMNX R TDAY.AVE_COMPOSI- Carbon monoxide CO. OUT
TION.CARBON_MON-
OXIDE

ued)
ty (*1) ter (*2)
TOXYGEN R TDAY.AVE_COMPOSI- Oxygen O2. OUT
TION.OXYGEN
TIBUTAN R TDAY.AVE_COMPOSI- i-Butane IC4H10. OUT
TION.I_BUTANE
TNBUTAN R TDAY.AVE_COMPOSI- n-Butane NC4H10. OUT
TION.N_BUTANE
TIPENTN R TDAY.AVE_COMPOSI- i-Pentane IC5H10. OUT
TION.I_PENTANE
TNPENTN R TDAY.AVE_COMPOSI- n-Pentane NC5H10. OUT
TION.N_PENTANE
TNHEXAN R TDAY.AVE_COMPOSI- n-Hexane C6H14. OUT
TION.N_HEXANE
TNHEPTN R TDAY.AVE_COMPOSI- n-Heptane C7H16. OUT
TION.N_HEPTANE
TNOCTAN R TDAY.AVE_COMPOSI- n-Octane C8H18. OUT
TION.N_OCTANE
TNNONAN R TDAY.AVE_COMPOSI- n-Nonane C9H20. OUT
TION.N_NONANE
TNDECAN R TDAY.AVE_COMPOSI- n-Decane C10H22. OUT
TION.N_DECANE
THELIUM R TDAY.AVE_COMPOSI- Helium He. OUT
TION.HELIUM
TARGON R TDAY.AVE_COMPOSI- Argon Ar. OUT
TION.ARGON
TAVRLSG R TDAY.AVE_CALCULA- Averaged calculated spe- OUT
TAVESC R TDAY.AVE_CALCULA- Averaged calculated spe- OUT
TAVEHV R TDAY.AVE_CALCULA- Averaged calculated OUT
TAVIDHV R TDAY.AVE_CALCULA- Averaged calculated ideal OUT
YAVESP R YDAY.AVE_SP Average static pressure. OUT
YAVEDP R YDAY.AVE_DP Average differential pres- OUT
sure.
YAVETMP R YDAY.AVE_TEMP Average temperature. OUT
YAVEFLW R YDAY.AVE_FLOW Average flow rate. OUT
YAVEFLR R YDAY.AVE_FLOW_RAW Averaged flow rate at OUT
flowing condition.
YAVEENG R YDAY.AVE_ENERGY Average energy. OUT
YTTLFLW R YDAY.TOTAL_FLOW Total flow. OUT
YRAWVLM R YDAY.RAW_VOLUME Total uncorrected flow. OUT
YTTLENG R YDAY.TOTAL_ENERGY Total energy. OUT
YPRDTIM R YDAY.PRODUC- Production time. OUT
TION_TIME
YSHTTIM R YDAY.SHUT_TIME Shut in time. OUT

ued)
ty (*1) ter (*2)
YPULSES R YDAY.PULSES Pulse OUT
YACMVLM R YDAY.ACCUM_VOLUME Accumulated flow at end. OUT
YTSTMPS R YDAY.TIMESTAMP_SEC Time stamp. OUT
YMETHAN R YDAY.AVE_COMPOSI- Methane CH4. OUT
TION.METHANE
YNTRGN R YDAY.AVE_COMPOSI- Nitrogen N2. OUT
TION.NITROGEN
YCBNDXD R YDAY.AVE_COMPOSI- Carbon dioxide C02. OUT
TION.CARBON_DIOX-
IDE
YETHANE R YDAY.AVE_COMPOSI- Ethane C2H6. OUT
TION.ETHANE
YPROPAN R YDAY.AVE_COMPOSI- Propane C3H8. OUT
TION.PROPANE
YWATER R YDAY.AVE_COMPOSI- Water H2O. OUT
TION.WATER
YHYDSLF R YDAY.AVE_COMPOSI- Hydrogen sulphide H2S. OUT
TION.HYDROGEN_SUL-
FIDE
YHYDRGN R YDAY.AVE_COMPOSI- Hydrogen H2. OUT
TION.HYDROGEN
YCBNMNX R YDAY.AVE_COMPOSI- Carbon monoxide CO. OUT
TION.CARBON_MON-
OXIDE
YOXYGEN R YDAY.AVE_COMPOSI- Oxygen O2. OUT
TION.OXYGEN
YIBUTAN R YDAY.AVE_COMPOSI- i-Butane IC4H10. OUT
TION.I_BUTANE
YNBUTAN R YDAY.AVE_COMPOSI- n-Butane NC4H10. OUT
TION.N_BUTANE
YIPENTN R YDAY.AVE_COMPOSI- i-Pentane IC5H10. OUT
TION.I_PENTANE
YNPENTN R YDAY.AVE_COMPOSI- n-Pentane NC5H10. OUT
TION.N_PENTANE
YNHEXAN R YDAY.AVE_COMPOSI- n-Hexane C6H14. OUT
TION.N_HEXANE
YNHEPTN R YDAY.AVE_COMPOSI- n-Heptane C7H16. OUT
TION.N_HEPTANE
YNOCTAN R YDAY.AVE_COMPOSI- n-Octane C8H18. OUT
TION.N_OCTANE
YNNONAN R YDAY.AVE_COMPOSI- n-Nonane C9H20. OUT
TION.N_NONANE
YNDECAN R YDAY.AVE_COMPOSI- n-Decane C10H22. OUT
TION.N_DECANE
YHELIUM R YDAY.AVE_COMPOSI- Helium He. OUT
TION.HELIUM
YARGON R YDAY.AVE_COMPOSI- Argon Ar. OUT
TION.ARGON

ued)
ty (*1) ter (*2)
YAVRLSG R YDAY.AVE_CALCULA- Averaged calculated spe- OUT
YAVESC R YDAY.AVE_CALCULA- Averaged calculated spe- OUT
YAVEHV R YDAY.AVE_CALCULA- Averaged calculated OUT
YAVIDHV R YDAY.AVE_CALCULA- Averaged calculated ideal OUT
MTTLFLW R CURM.TOTAL_FLOW Total flow. OUT
*1: R: Readable
W: Writable
*2: Type of the function block parameter to be mapped and its mapped value
IN: Value of the input parameter of the function block
OUT: Value of the output parameter of the function block
Internal: Value of the internal parameter the function block uses for calculation (structure AGA_R_PARAM)
*3: The value of the internal parameter that indicates whether the function block is calculating is reflected, not the value of an
input/output parameter.

Rev-1
Revision information
Title : Integration with FAST/TOOLS
Manual No. : IM 32Q56H20-31E
Jan. 2015 / 4th Edition / R3.02.20 or later*
*: Denotes the release number of the Software Product corresponding to the contents of this Man-
ual. The revised contents are valid until the next edition is issued.
Introduction Deleted the ProSafe-RS document map, and changed descriptions of precautions
for Safety, Protection, and Modification of the Product.
A1.1 Added PRM to Sample system configuration in Narrowband mode and the software
environment for SCSU1.
B1 Added a description of IMPORTANT.
B2.2 Changed the title of items in a section.
B2.3 Changed the title of items in a section. Changed the structure of items in a section.
Oct. 2013 / 3rd Edition / R3.02.10 or later
Introduction Descriptions of Station Types have been changed.
All Chapter composition has been changed into part composition.
Explanation of the Narrowband mode have been added.
Explanation of Upstream system functions have been added.
Explanation of SCS hardware used for Upstream systems and CMPL have been
added.
Dec. 2012/2nd Edition/R3.02 or later
4.1 Descriptions of Vent/IP overview have been changed.
Aug. 2011/1st Edition/R3.01 or later
Newly published
n For Questions and More Information

Online Query: A query form is available on the following URL for online query.
http://www.yokogawa.com/iss
n Written by Yokogawa Electric Corporation
n Published by Yokogawa Electric Corporation
2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN

Im32q56h20 31e PDF

Uploaded by

Copyright:

Available Formats

Im32q56h20 31e 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

Im32q56h20 31e PDF

Uploaded by

Copyright:

Available Formats

User's

Safety Precautions for Use

Indicates the OFF position of a power on/off switch.

n Notes on Handling User's Manuals

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

n Warning and Disclaimer

l Model and Suffix Codes

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Identifies instructions that must be observed to prevent damage

Identifies important information required to understand opera-

Identifies additional information.

Identifies referenced content.

l Commonly Used Conventions throughout the User's Manuals

l Conventions Used to Show Key or Button Operations

l Conventions of a User-defined Folder

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

n Integration with CENTUM

n Explanation of Hardware and Software Behaviors in the User's

Table Info-1 Names of SCS and Safety Control Unit Used

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Conformity Standards and Cautions

Table Info-2 Standards

*1: Safety control stations comply with this standard.

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

n Installation and Maintenance Notes

l Requirements for Installation

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Table Info-3 Standard Numbers and Measurement Categories

l Tightening Torque of Screws

Table Info-4 Recommended Tightening Torque

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

l Power Cable Wiring

l I/O Cable Wiring

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

l Modules, Cards, Cables, and Connectors

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

n Guidelines for Selecting a Power Supply Unit

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

l Notices on Deciding the Output Capacity of Power Supply Unit

Input current waveform Approximately 5 ms

Figure Info-1 Input voltage and current waveforms

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

l How to Decide the Power Supply Unit

l Suppressing Harmonic Current

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Copyright and Trademark Notices

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Integration with FAST/TOOLS

IM 32Q56H20-31E 4th Edition

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Integration with FAST/TOOLS

IM 32Q56H20-31E 4th Edition

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Integration with FAST/TOOLS

IM 32Q56H20-31E 4th Edition

IM 32Q56H20-31E 4th Edition : Jan.30,2015-00

Integration with FAST/TOOLS

IM 32Q56H20-31E 4th Edition