0% found this document useful (0 votes)

113 views715 pages

Im32p01c10 01en

This engineering guide for ProSafe-RS provides an overview of its functions and essential precautions for designing, manufacturing, operating, and maintaining safety equipment systems. The document is divided into multiple parts covering specifications, application design, maintenance, emergency procedures, and more. It emphasizes the importance of adhering to safety precautions and proper handling of the product to ensure safe operation.

Uploaded by

alli latif

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

113 views715 pages

Im32p01c10 01en

Uploaded by

alli latif

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 715

User's

Manual
Engineering Guide Vol. 1

IM 32P01C10-01EN

IM 32P01C10-01EN
5th Edition
i

Introduction
This manual is the engineering guide of ProSafe-RS.
This document explains an overview of ProSafe-RS functions and the cautionary notes which
needs to be considered for engineering, based on the basic flow of engineering such as de-
sign, manufacturing, operation and maintenance of a safety equipment system by using
ProSafe-RS.
Please refer to the Engineering Guide Vol.2 for the steps and precautions to take for creating
application logic using ProSafe-RS engineering.
See the Appendix in the ProSafe-RS User Guide for the terminology in the descriptions of
ProSafe-RS.
Notes and precautions regarding SCSP1 described in this document also apply to SCSU1.
This document is composed of the following parts.
• Part A Specifications and functions that are needed to design applications
This part describes the specifications and functions that are needed to design a ProSafe-
RS application. It describes the control bus, system time synchronization, and the engi-
neering specifications and functions with a focus on ProSafe-RS and Control Station.
• Part B Designing applications
This part describes the main points of the design specifications of ProSafe-RS systems.
• Part C Basics of creating applications
This part describes the common work flow, precautions and common procedures to cre-
ate a ProSafe-RS application.
• Part D Procedures to create applications using the I/O list engineering method
This part gives an overview of the procedures of the automated design organizer when
using I/O list engineering and the procedures when using iDefine.
• Part E Changing applications
This part describes the steps to change applications online, the function that can export
the application data to external folder and import the exported external file.
• Part F Installation and start-up
This part explains the installation of ProSafe-RS system, the connection to field devices,
a procedure of start-up including tests, commissioning and precautions for the start-up.
• Part G Emergency procedures
This part describes the actions to be taken in an emergency situation during plant opera-
tion, behavior of SCS at error occurrence, and recovery procedures.
• Part H Monitoring the status of SCS
This part describes the management of the SCS status. It explains the method to view
the SCS status registered in RS projects, the detailed status of the specified SCS, and
the detailed status of I/O module by using the IOM Report. It also mentions how to verify
the diagnostic information message that is generated in the SCS.
• Part I Maintenance
This part explains cautionary points and steps to maintain ProSafe-RS devices (such as
I/O modules) and field devices.
• Appendix
This part describes the setting items of nodes, modules and channels, RS original engi-
neering, cautionary points and maintenance of ProSafe-RS prior to R4, and maintenance
of sales discontinued products.

5th Edition : Aug. 2018 (YK) IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

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.
• Be sure to confirm the specifications and required settings of the devices that are used in
combination with the Product by referring to the instruction manual or other documents of
the devices.
• 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 when handling the equipment. This symbol is la-
beled on the Product to indicate the possibility of dangers such as electric shock
on personnel and equipment, and also indicate that the user must refer to the Us-
er's Manuals for necessary actions. In the User's Manuals, this symbol is used to-
gether with a signal word "WARNING" or "CAUTION" at the locations where pre-
cautions for avoiding dangers are described.
<French> Signale qu'il faut faire preuve de prudence pendant la manutention de
l'équipement. Ce symbole, apposé sur le produit, signale les risques potentiels
tels qu’une électrocution du personnel ou de l’équipement, et demande à
l'opérateur de se reporter aux manuels de l'utilisateur pour savoir les actions
nécessaires. Dans les manuels de l'utilisateur, ce symbole est utilisé conjointe-
ment avec le mot « WARNING » ou « CAUTION » aux emplacements où des
précautions doivent être observées pour éviter les dangers décrits.

Indicates that caution is required for hot surface. Note that the devices with this
symbol become hot. The risk of burn injury or some damages exists if the devices
are touched or contacted.
<French> Signale qu'il faut faire preuve de prudence avec la surface brûlante. Les
appareils sur lesquels est apposé ce symbole risquent de devenir brûlants. Tout
contact physique ou matériel avec ces appareils risque de provoquer des brûlures
ou des dommages.
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.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

iii
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.
• 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.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

Documentation Conventions
n Symbols
The following symbols are used in the User's Manuals.
Indicates precautions to avoid a danger that may lead to death or
WARNING severe injury.

Indicates precautions to avoid a danger that may lead to minor or

CAUTION moderate injury or property damage.

IMPORTANT Indicates important information required to understand operations or

functions.
Indicates additional information.

Indicates referenced content.

In online manuals, you can view the referenced content by clicking
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

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

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 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 Definitions of Node and Module Terms

In the User's Manuals, nodes and modules are referred to by using collective terms, another
terms, or abbreviations based on the following definitions:
• Definitions of nodes
• Node: A node is a collective term for an FIO node and an N-IO node.
• FIO node: This is a collective term for a safety control unit, a safety node unit, and a
unit for optical ESB bus repeater module.
• CPU node: This is another term for a safety control unit. The abbreviation of safety
control unit is SCU.
• I/O node: This is another term for a safety node unit. The abbreviation of safety node
unit is SNU.
• N-IO node: This is a collective term for a node interface unit and an N-IO I/O unit.
The abbreviation of node interface unit is NIU.
• Definitions of modules
• I/O module: This is a collective term for an FIO I/O module and an N-IO I/O module.
• FIO I/O module: This is a collective term for an analog I/O module and a digital I/O
module for FIO, and a communication module.
• N-IO I/O module: This is a collective term for the modules that can be mounted on an
N-IO I/O unit.
• AIO/DIO module: This is a collective term for an analog I/O module, a digital I/O mod-
ule, and a universal type I/O module.
• Analog I/O module: This is a collective term for an analog input module and an ana-
log output module.
• Digital I/O module: This is a collective term for a digital input module and a digital out-
put module.
• Universal type I/O module: This is a collective term for the I/O modules for which the
channel signal category can be changed by software.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

vi
• Input module: This is a collective term for an analog input module, digital input mod-
ule, and a universal type I/O module with defined input channels.
• Output module: This is a collective term for an analog output module, digital output
module, and a universal type I/O module with defined output channels.
• Communication module: This is a collective term for a serial communication module,
an Ethernet communication module, and a fire and gas communication module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

TocApp.-1

Engineering Guide Vol. 1

IM 32P01C10-01EN 5th Edition

CONTENTS
Appendix
Appendix 1. Settings for node, module, and channel.......................App.1-1
Appendix 1.1 Setting items for nodes.............................................................. App.1-2
Appendix 1.2 Settings for modules.................................................................. App.1-5
Appendix 1.3 Settings for channel items......................................................... App.1-8
Appendix 1.3.1 Common display items for channels.............................. App.1-9
Appendix 1.3.2 Settings for the AI channel........................................... App.1-11
Appendix 1.3.3 Settings for the AO channel......................................... App.1-25
Appendix 1.3.4 Settings for the DI channel........................................... App.1-31
Appendix 1.3.5 Settings for the DO channel......................................... App.1-34
Appendix 2. RS original engineering..................................................App.2-1
Appendix 2.1 Operations on SCS projects that are not registered in the AD
project.......................................................................................... App.2-2
Appendix 2.2 Definitions of inputs/outputs..................................................... App.2-3
Appendix 2.2.1 I/O Wiring View...............................................................App.2-5
Appendix 2.2.2 I/O Parameter Builder...................................................App.2-12
Appendix 3. Precautions related to main specification additions and
modifications...................................................................App.3-1
Appendix 3.1 The major changes in R1........................................................... App.3-2
Appendix 3.2 The major changes in R2........................................................... App.3-3
Appendix 3.3 The major changes in R3......................................................... App.3-13
Appendix 3.4 Major changes in R4................................................................. App.3-15
Appendix 4. Maintenance of sales discontinued products.............. App.4-1
Appendix 4.1 Time synchronization of SCSV1................................................ App.4-2
Appendix 4.2 Inter-SCS safety communication in a V net domain................ App.4-7
Appendix 4.3 Precautions when engineering CENTUM systems for using BCV
and CGW......................................................................................App.4-8
Appendix 4.4 System expansion with V net router connection..................... App.4-9

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A. Specifications and functions that are needed to design applications> A-1

A. Specifications and functions that

are needed to design applications
This part describes the following specifications and functions that are needed to design a
ProSafe-RS application:
• Vnet/IP network
• Security of ProSafe-RS
• Time synchronization
• SCS software configuration, hardware, I/O, performance and scan period, RAS, and ap-
plication capacity
• Safety system generation function
Read this to understand the specifications and functions when engineering or doing the feasi-
bility study prior to designing.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1. Overview of Vnet/IP network> A1-1

A1. Overview of Vnet/IP network

Vnet/IP is a control communication network that is used in ProSafe-RS systems that conform
to the IEEE802.3 standards. It is a highly reliable network built in dual-redundant configura-
tions.
Vnet/IP supports 1 Gbps or 100 Mbps transmission speed.
A Vnet/IP network is built by using network devices such as Layer 2 switches and Layer 3
switches, and transmission media such as UTP (Unshield Twist Pair) cables and optical fiber
cables.

n Communication paths of control communication

A Vet/IP network is a redundant network for control communication. In Vnet/IP, redundant
buses are configured with independent subnets of bus 1 and bus 2.
Control communication is the communication for transferring control data.
Normally, bus 1 is used for control communication. When bus 1 fails due to a communication
error, control communication is continued on bus 2.
An Ethernet network apart from the Vnet/IP is used for file transfer and data communication
except for control communication.

n Connecting Ethernet devices

Ethernet devices that do not use control communication are connected to an Ethernet net-
work that was installed separately from the Vnet/IP.
SEE
ALSO For more information about the Vnet/IP-Upstream network that is used in a FAST/TOOLS integrated environ-
ment, refer to:
A., “Integration with FAST/TOOLS function” in Integration with FAST/TOOLS (IM 32P56H20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.1 Vnet/IP network system configuration> A1-2

A1.1 Vnet/IP network system configuration

This section describes the system configuration and components of the Vnet/IP network.

n Vnet/IP network system configuration

The following figure shows an example of the Vnet/IP network system configuration.
Ethernet

Vnet/IP domain

HIS/ENG SENG

A wide area connection

via dedicated network is
available.
Max.7 levels
for Layer 2
Switch
Bus 1 Layer 3
V net router Switch
Layer 2
V net Switch Vnet/IP Vnet/IP
domain Bus 2 domain domain
Layer 2
Switch
Layer 3
Switch
FCS SCS

Wide Area Vnet/IP

Network domain
WAC Router WAC Router

Figure A1.1-1 System components of a Vnet/IP network

SENG and HIS set up in the virtual machine on the virtualization platform are also connected
to the Vnet/IP network.
SEE
ALSO For more information about system structure example on virtualization platform, refer to:
A6.2, “System configuration of virtualization platform” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)
For more information about precautions related to Vnet/IP communication on the virtualization platform, refer
to:
A6.4.1, “Precautions related to Vnet/IP communication on the virtualization platform” in ProSafe-RS Us-
er’s Guide (IM 32P01B10-01EN)

n Components of Vnet/IP network

The components of the Vnet/IP network are as follows:

l Vnet/IP station
A Vnet/IP device equipped station that is connected to a Vnet/IP network is referred to as a
Vnet/IP station. A Vnet/IP station in a domain is connected to Layer 2 switches provided one
for each bus. Vnet/IP stations are described below.
• SENG
SENG is a Safety Engineering PC. It is connected to a Vnet/IP network through a VI702/
VI701 Vnet/IP interface card installed in the PC. The VI702/VI701 card has two ports and
each port is connected to a transmission cable for Vnet/IP to support redundant Vnet/IP
buses.
• SCS

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.1 Vnet/IP network system configuration> A1-3
The S2SC70S/S2SC70D (SCSP3), SSC60S/SSC60D (SCSP2), or SSC50S/SSC50D
(SCSP1) is used as a safety control station to connect with Vnet/IP. The transmission
speed of the SCSP3, SCSP2, or SCSP1 is 100 Mbps.
• V net router
A V net router is a device dedicated for connecting a Vnet/IP domain with a V net domain.
It performs the frame conversion and filtering between Vnet/IP and V net. The V net rout-
er is a station of CENTUM system.
• Wide Area Communication Router (WAC router)
The wide area communication router is a hardware device dedicated for the communica-
tions between Vnet/IP domains distributed in remote areas through a wide area network.
The wide area communication router is a device of CENTUM systems.
• HIS
HIS (Human Interface Station) is an operation and monitoring station of CENTUM. The
HIS is used for operation and monitoring of SCS. The CENTUM system builders are re-
quired for engineering and maintenance for the HIS and V net routers. The system build-
ers can be installed on the HIS.
TIP SENG and HIS set up in the virtual machine on the virtualization platform are referred to as a virtual Vnet/IP
station. In order to connect the virtual Vnet/IP station to the Vnet/IP network, a software license for the
Vnet/IP interface package is required.

SEE
ALSO For more information about the procedures and precautions when adding a Vnet/IP station, refer to:
“n Procedures and precautions for adding a Vnet/IP station” on page I5-1

l Vnet/IP domain
A Vnet/IP domain consists of two independent subnets of bus 1 and bus 2. Each domain can
have a maximum of 64 Vnet/IP stations (SENG, SCSP2, etc.).
If a safety system is integrated with a CENTUM system, the integrated system can have a
maximum of 16 Vnet/IP and V net domains.
SEE
ALSO For more information about the procedures and precautions when adding a Vnet/IP domain, refer to:
“n Procedures and precautions for adding a Vnet/IP domain” on page I5-2

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 domains on each bus.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.2 Device Connections in a Vnet/IP Domain> A1-4

A1.2 Device Connections in a Vnet/IP Domain

The devices in the Vnet/IP domain are connected in a star topology by using a 1-Gbps layer 2
switch as the hub. The connections among the layer 2 switches should be in a star topology
or ring topology. A ring topology can be used with a CENTUM integration configuration only. It
cannot be used with a configuration consisting of a ProSafe-RS system only, or a FAST/
TOOLS integration configuration.
Because the redundant Vnet/IP buses are separated as independent subnets of each bus,
each bus should have its own layer 2 switch as the hub.

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.
The following describes the impact when the Layer 2 switch power supply becomes faulty:
• 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 stop, 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 Specification when connecting devices in a Vnet/IP domain

The specification when connecting devices in a Vnet/IP domain is as follows:
• Number of Vnet/IP stations connected : Max. 64 Stations
(Vnet/IP stations including V net routers)
• Distance between Vnet/IP stations : Max. 40 km
• Distance between Layer 2 switch and station : Max. 100 m (when UTP cable is
used)
• Connection distance between Layer 2 switches: : Max. 5 km (when optical fiber cable
is used)
• Levels of Layer 2 switches: : Max. 7 levels
TIP • For the redundant stations such as the SCS and Vnet router, the respective CPU module and the Layer
2 switch at the control side and the standby side are connected by a UTP cable. The number of connec-
ted Vnet/IP stations is counted as one unit.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.2 Device Connections in a Vnet/IP Domain> A1-5
SENG

UTP cable
Max. 100 m

Bus 1 side Bus 2 side

L2SW L2SW

Optical fiber Optical fiber

cable cable
Max. 5 km Max. 5 km

L2SW L2SW

UTP cable
Max. 100 m

SCS
L2SW: Layer 2 switch

Figure A1.2-1 Example of connections in a Vnet/IP domain

IMPORTANT
When connecting layer 2 switches with a star topology, do not connect in such a way that mul-
tiple communication paths exist between any two stations. Otherwise, normal communication
is not performed.
SCS SCS

L2SW L2SW

L2SW

Figure A1.2-2 Example of an incorrect connection

n Communication between SENG and SCS

The engineering and maintenance of SCS are performed via Vnet/IP from SENG.
You can perform safety communication between SENG and the SCS of Vnet/IP domains.
The communicable network range is the same as the range in which Inter-SCS safety com-
munication can be performed.
You must connect one or more SENGs to the Vnet/IP network that allows communications
with the SCS.

n Communication between HIS/FCS and SCS

It is possible to communicate with an SCS in a V net domain or a Vnet/IP domain from an
HIS/FCS. The communicable network range is the same as for executing Inter-SCS safety
communication.
This communication has no impact on safety functions executed in SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.3 Connection between Vnet/IP domains> A1-6

A1.3 Connection between Vnet/IP domains

1-Gbps layer 3 switches are used for connections among the Vnet/IP domains. For a redun-
dantly configured Vnet/IP network, each bus should have a layer 3 switch for the connection
of the domains. By using a leased line as the transmission path, the domains can be connec-
ted through the wide area networks.
Connection between Vnet/IP domains is supported only in a CENTUM integration configura-
tion or a FAST/TOOLS integration configuration. It is not supported in a ProSafe-RS only sys-
tem.

IMPORTANT
It is strongly recommended to provide an uninterruptible power supply (UPS) to protect Layer
3 switches so that the Layer 3 switches do not stop upon power failure.

TIP Wide area communication routers can also be used to connect Vnet/IP domains through a wide area network.

n Specifications when connecting Vnet/IP domains

The specification of connection between Vnet/IP domains is as follows:
• Multi-level connection of Vnet/IP domains: Max. 15 levels (16 Layers) of Layer 3
Switches
• Transmission delay between any domains: Less than 80 ms

IMPORTANT
Do not connect in such a way that multiple communication paths exist between any two do-
mains. Otherwise, normal communication is not performed. However, with a CENTUM inte-
gration configuration, it is possible to configure the connections among the layer 3 switches
connecting adjacent domains in a ring topology.

Domain 1 L3SW Domain 2 L3SW Domain 3

L3SW

Figure A1.3-1 Example of incorrect connection

n Connection between Vnet/IP domains

There are three types of connections between Vnet/IP domains: bi-directional, hierarchical
and bridge connections. It is possible to configure a network coexisting these three types of
connections. Set the connection types in Domain Properties for each domain using CENTUM
engineering builders. The connection type may be selected in accordance with the upper and
lower relationships that should be set between connected domains. Decide on the connection
type after investigating whether or not message reception, SCS TCP communication or time
synchronization is required between connected domains.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.3 Connection between Vnet/IP domains> A1-7

Bi-Directional Bi-Directional
Domain 4 Domain 5

L3SW L3SW

Domain 1 L3SW Domain 2 L3SW Domain 3

L3SW Bridge
Hierarchical

Domain 6
L3SW: Layer 3 switch

Figure A1.3-2 Domain connection types in Vnet/IP

l Setting of TCP/IP communication relay processing

When the system consists of multiple Vnet/IP domains, you must configure the [FCS TCP]
setting, which is a domain property setting of a CENTUM system builder. Setting it to ON al-
lows TCP/IP broadcast frames to be relayed in both directions. This function enables the
TCP/IP communication between SENG and SCS to be performed across domains.

l Bi-directional connection
This connection type does not differentiate the upper and lower relationships between Vnet/IP
domains. This type of connection can be established by setting the domain to receive HIS
messages, FCS messages and FCS TCP communication frames from other domains. More-
over, when the domain is set to receive FCS messages, it can also receive SCS messages
(such as system alarm messages). If the domain is set to receive FCS TCP frames, it can al-
so receive the SCS TCP communication frames. By the default settings on the Domain Prop-
erties dialog box, the domain is set to receive all the transmissions.

l Hierarchical connection
This connection type differentiates the upper and lower relationships between Vnet/IP do-
mains. This type of connection can be established by setting a lower domain not to receive
HIS messages, FCS messages and FCS TCP communication frames from upper domains;
but all the stations in the upper domains can receive HIS messages, FCS messages, and
FCS TCP communication frames from the lower domain. Moreover, when the domain is set to
receive FCS messages, it can also receive SCS messages (such as system alarm messag-
es). If the domain is set to receive FCS TCP frames, it can also receive the SCS TCP commu-
nication frames.

l Bridge connection
This connection configuration emphasizes the independence among the Vnet/IP domains. In
this configuration, the domain properties are configured such that the domains do not receive
messages from each other. If time synchronization among the domains is not required, 0 is
set in the time group.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.3 Connection between Vnet/IP domains> A1-8

IMPORTANT
• If the SCS exists in a Vnet/IP domains that are different from SENG, you need to config-
ure such that the FCS TCP communication is receivable in both domains in order to engi-
neer and maintain the SCS by using SENG.
• When performing inter-SCS safety communication between different Vnet/IP domains,
you need to configure such that the FCS TCP communication is receivable in both do-
mains.
• If an SCS that performs inter-SCS safety communication exists in the Vnet domain, you
need to configure such that the FCS TCP communication is receivable in both domains.
In this case, you need to configure the Vnet router, bus converter (BCV), and communica-
tion gateway (CGW) in such a way that the FCS TCP communication is receivable.

TIP • Even if you select any of these communication configurations, you can access the SCS function block
and variables from the CENTUM station across domains by using the tag name.
• You can also set the domain properties so that the domain receives only one type among HIS messag-
es, FCS messages, and FCS TCP communication frames.

n System expansion with WAC routers

WAC routers can be used to expand the system by connecting two or more Vnet/IP domains
in remote sites using a wide-area network.
You can engineer WAC router by using the System Builders of CENTUM VP. You cannot engi-
neer WAC routers by using the SENG.
Therefore, if you plan to add WAC routers to the system that consists of only SENG and SCS,
and connect the system to a wide-area network, the System Builders of CENTUM VP are re-
quired.
Moreover, when connecting SCS with wide-area network through WAC routers, install an
SENG in each Vnet/IP domain that are connected by WAC routers. Engineering operations
such as offline download to SCS must be performed from the SENG that is connected to each
Vnet/IP domain. Similarly, install an AD server for each Vnet/IP domain.
The following figure shows an example of system expansion using WAC routers.
The illustrated SENG includes AD Organizer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A1.3 Connection between Vnet/IP domains> A1-9

An SENG is required in each Another WAN is required for connection

Vnet/IP domain connected via between Ethernet, separately from Vnet/IP
WAC routers.
WAN WAN
Ethernet Ethernet Ethernet

SNTP SENG HIS ENG SNTP SENG HIS ENG SNTP SENG HIS ENG

Vnet/IP Vnet/IP Vnet/IP

AD AD AD
Server FCS SCS Server FCS SCS Server FCS SCS

WAC WAC WAC WAC

Domain 1 Domain 2 Domain 3

WAN WAN

Up to 2 hops are allowed to connect

Vnet/IP domains via WAC routers

Figure A1.3-3 Example of system expansion with WAC routers

SEE
ALSO For more information about how to configure the WAC router with CENTUM VP R6, refer to:
8, "Wide Area Communication Router" in Communication Devices Reference (IM 33J20B10-01EN)
For more information about how to configure the WAC router with CENTUM VP R5, refer to:
8, "Wide Area Communication Router" in Communication Devices Reference (IM 33K03M10-50E)

l Precautions when engineering CENTUM VP systems for using WAC router

A WAC router is engineered on the CENTUM VP side. When connecting the WAC router to
ProSafe-RS, be careful of the following points.

l Priority control of the Inter-SCS safety communication

A WAC router has the function to give priority to the inter-SCS safety communication, if the
communication traffic between Vnet/IP domains exceeds the limit of bandwidth specified in
the builder. When performing inter-SCS safety communication through WAC routers, be sure
to set WAC routers to enable this function.

n Network connection through a wide area network

Connection between Vnet/IP domains can be established through a wide area network for
communicating with remote Vnet/IP domains. This type of connection can be established
when integrated with CENTUM.

IMPORTANT
If you intend to connect Vnet/IP domains through a wide area network without using wide
area communication routers, the following conditions have to be met.
• The transmission delay between any two Vnet/IP domains must be less than 80 ms.
• If inter-SCS safety communications are performed between domains connected through
a wide area network, the recommended bandwidth of the wide area network is 100 Mbps
or faster.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2. ProSafe-RS security> A2-1

A2. ProSafe-RS security

ProSafe-RS has the following security functions to prevent access to the system by unauthor-
ized users and devices, and unintended changes caused by operation mistakes made by
users.
• Security for the project database
You can configure the SENG function so that the user is required to enter a password
when changing the project data with SCS Manager. (Recommended)
• Security for access to SCS
You can limit access to SCS from the outside based on the SCS security level. The user
is required to enter a password when changing the SCS security level. (Mandatory).
• Security for the SCS Maintenance Support Tool
On SENG, you can limit writing to SCS with the SCS Maintenance Support Tool by setting
a password. (Recommended)
• Access control and operation history management
Access control and operation history management can be performed on projects that are
saved in the AD Server. You can also use the Access control and operation history man-
agement package.
• Countermeasures against threats to IT security
ProSafe-RS security threats include attacks via the network, direct attacks by executing
actions on an SENG, and analysis of important data carried out by stealing an SENG.
The security features are designed to take measures against these types of security
breaches.
This section provides an overview of the ProSafe-RS security function, and the main proce-
dures for setting passwords and implementing security relating to unauthorized access and
protection against unintended operations.

SENG SCS

Security Function

Security for
Verify password SCS project Project Database

SCS Manager Verify password Security for

Access to SCS

SCS Maintenance Security for the

Verify password Support Tool SCS Maintenance
Support Tool

Setting
information

Figure A2-1 Password-based security functions

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.1 Overview of ProSafe-RS security> A2-2

A2.1 Overview of ProSafe-RS security

The figure below illustrates the security management of SCS and SENG in ProSafe-RS.

AD Server SENG

User management
Access control Logon control

System Structure
Navigator Access control and operation history management

Operation history
Access control management
Safety I/O Editor

Security of Database Security of SCS Security of

Safety SCS Maintenance
Communication support tool
I/O Editor
Database Protection against
access control unintended
IOM operation
Definition editor

Modification Access control Error detection

RS generation management management
for SCS

History
management

ModPack-based
change management SCS Access
Control

SCS

Figure A2.1-1 Overview of security management

n IT security
This section describes the requirements for IT security.
For SENG, Windows OS is used as a platform. Therefore, it is necessary to prevent, detect,
and recover from computer viruses and attacks from the external through the network. For ex-
ample, there are countermeasure such as network access control using firewall and system
backup.
In the CENTUM Integration Structure, it is necessary to consider comprehensive IT security
including ProSafe-RS system and CENTUM system.
You can harden the security of the PC designated as a SENG terminal to enhance the
ProSafe-RS IT security (PC hardening). This section describes the details regarding PC hard-
ening and the setting guidelines.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.1 Overview of ProSafe-RS security> A2-3
TIP When integrating ProSafe-RS with CENTUM VP, configure the security settings during installation of ProSafe-
RS and installation of CENTUM VP, respectively.
When integrating ProSafe-RS with CS 3000, select Legacy model in IT security tool.
Configure the IT security of the computer that has iDefine installed by referring to iDefine Security Manual
(PR03076-MAN-981_01).
If your security model is a legacy model, anyone will be able to start iDefine Test Manager.
If your security model is a standard or strengthened model, any user that belongs to the PSF_ENGINEER or
PSF_ENGINEER_LCL group will be able to start iDefine Test Manager.

SEE
ALSO For more information about security configurable on the PC, refer to:
2., “Security Models” in ProSafe-RS Security Guide (IM 32P01C70-01EN)

l An example of registering a user to the user account

IT security enhancement for a PC can protect the ProSafe-RS system from the illegal access
by any user other than the user of ProSafe-RS user groups. For protecting the ProSafe-RS
system from the accidental mistaken accesses by the users of ProSafe-RS groups, the
ProSafe-RS Security features should be used. By combining IT security enhancement for a
PC and ProSafe-RS Security, you can fortify security of ProSafe-RS.
The typical examples of registering a ProSafe-RS user to the user groups are shown as fol-
lows:
(A) ProSafe-RS Engineer (Integrated with CENTUM VP)
ProSafe-RS Engineer user should be assigned to both PSF_ENGINEER group of
ProSafe-RS and CTM_ENGINEER group of CENTUM VP.
(B) ProSafe-RS Engineer (Not Integrated with CENTUM VP)
ProSafe-RS Engineer user should be assigned only to the PSF_ENGINEER group.
(C) Maintenance and service persons
The user who requires the role for upgrading SENG software to newer versions, main-
taining or changing the hardware components such as I/O modules should be assigned
only to the PSF_MAINTENANCE group.
(D) Network and System Administrator (User who is responsible for network maintenance)
This user is considered as the administrative user of Windows environment in SENG.
This user needs to be assigned only to the PSF_MAINTENANCE group.
(E) User account for emergency attention (For domain or parallel management in standard
model)
When ProSafe-RS system is running in an Windows domain environment, if the domain
controller encounters an abnormality, no one can logon to the SENG with the domain
account. You need to prepare the user accounts who are assigned to the PSF_MAINTE-
NANCE_LCL group for an emergency attention. If the domain controller encounters an
abnormality, user can logon to the SENG with this user account, then maintain and op-
erate ProSafe-RS.
Though the users in the above groups are all granted with the Write permission to all the Proj-
ect folders, in the cases of (C) and (D), the Write permission is not required. An engineer
should define a password by using the security feature of the project database and keep the
password as secret to the users whom you do not grant the Write permission so as to protect
the project database. Moreover, ProSafe-RS provides security features for accessing the SCS
and for Maintenance Support Tool. These security features can be utilized in accordance with
the role of the users so as to protect the database and SCS from the accidental operation
mistakes.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.1 Overview of ProSafe-RS security> A2-4

n Database security management

The database has the following security functions.

l Access control of the SCS project database

It is possible to set a password for the database used in an SCS project; so that only users
who know the password are allowed to make changes to the database. It is also possible to
set whether or not to allow users who do not know the password to refer to the database.

l Security for AD projects

The following security functions are available for AD projects:
• Management of users who are permitted to access AD projects
• Access control of AD project data

l Modification management
This function manages the changes made to SCS projects. It has the following functions:
• Backup
SCS projects are registered and managed in AD Server.
• Version management
This function manages the history of changes made to SCS projects.
• Master database management
SENG always maintains the backup SCS project that keeps the same SCS database with
the one running on the SCS.
• Saving modification files
When you use the Access Control and Operation History Management Package, the
changes made to the project database downloaded to the SCS are saved.

n Security management of SCS

The SCS has the following security functions.
SEE
ALSO For more information about security of SCS, refer to:
B3., “Security of SCS” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

l Prevention of SCS operation mistakes made by users

When a user attempts to perform the following operations on the SCS, the user is prompted
to confirm the execution of the operation in order to prevent operational mistakes.
• Offline download
• Online change download
• Master database offline download
• IOM download
• I/O lock
• SCS security level change

l Access control to SCS

• Access control based on the security level

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.1 Overview of ProSafe-RS security> A2-5
Access from outside to SCS is controlled by SCS security levels. Password must be set
for changing the SCS security levels (to Level 1 or Level 0). The SCS security level can
only be operated using the SCS security level operation function, by users who know the
password.
• Access control for each user
When the Access Control and Operation History Management Package is applied, you
can control operations on SCS for each user.

n Security management of SCS Maintenance Support Tool

In SCS Maintenance Support Tool, write access to SCS is controlled by setting a password. If
the Access Control and Operation History Management Package is used, operations of the
SCS Maintenance Support Tool can be controlled for each user.
SEE
ALSO For more information about how to set a password for SCS Maintenance Support Tool, refer to:
“n How to enter SCS Maintenance Support tool password” on page A2-10

l SCS Status Overview window, Diagnostic Information window, Setup Tool

The SCS Status Overview window, Diagnostic Information window and Setup Tool are protec-
ted by passwords. Each of these functions is launched as read-only unless the correct pass-
word is specified.
In the case of the SCS Status Overview window, the password is checked when calling this
window from SCS Manager. The Diagnostic Information window and Setup Tool inherit the
password of the SCS Status Overview window when they are launched.
When the Access Control and Operation History Management Package is applied, enter the
name and password of the engineer.

l Message Cache Tool

Message Cache Tool is protected by a password. It is launched as read-only unless the cor-
rect password is specified.

l SOE Viewer
No password is set up for SOE Viewer because no writing operations to an SCS are per-
formed on SOE Viewer.

n Access control of AD server

You can control access to individual files and functions of an AD project for each user. You
can also set access rights to the files and folders in AD Server according to the role of the
user.

l System Structure Navigator

You can set the rights to register, unregister, back up, and restore RS projects, edit RS project
comments, and delete SCS.

l Safety I/O Editor

You can set the rights to create and delete safety I/O lists and assign safety I/O.

l Safety Communication I/O Editor

You can set the rights to create and delete safety communication I/O lists and assign safety
communication I/O.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.1 Overview of ProSafe-RS security> A2-6

l IOM Definition Editor

You can set the rights to create and delete nodes and I/O modules.

l RS generation
You can set the rights to run RS generation.

l History management
You can set the rights to set and delete labels.

l ModPack change management

You can set the rights to perform operations for each ModPack operation category.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.2 Security for project database> A2-7

A2.2 Security for project database

This section describes security for project databases.

n Setting a password for project databases

You can assign a password to a database to prevent unauthorized users from making
changes to the database in SCS projects. Users without entering the password can be given
permission for read only operation.
Passwords can be specified for the following.
• For each SCS Project
• For each POU
The reading and writing right for the whole project and the access right for each POU can be
controlled using the security function of the SCS project and the security function of each
POU.
Set a different password for each SCS Project.
If higher level of security is required, set a password for each important POUs.
You need to set different passwords for each SCS project. These passwords should be differ-
ent from the one for the SCS security level.
Database files in RS projects should not be changed from tools other than the ProSafe-RS
software.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.3 Security of SCS Maintenance Support tool > A2-8

A2.3 Security of SCS Maintenance Support tool

SCS Maintenance Support Tool has a security by setting a password to be entered when
starting related windows. A password is set for each SENG.
This section describes how to set passwords for the SCS Maintenance Support Tool.
The password described in this section is not applicable if the Access Control and Operation
History Management Package is used. Instead, the user enters the password that is set for
each user in the Access Control and Operation History Management Package when starting
the SCS Maintenance Support Tool.

SENG
SCS engineering functions
SCS Maintenance Support Tool
Security functions
SCS Manager
Verification

Windows Password Windows related to

setting Setup Password SCS Maintenance
[Start] menu information
function Support Tool
Verification

Windows are opened in the

read/write status or the read-only
status based on the password
verification result

Figure A2.3-1 Security functions of Maintenance Support tool

TIP No security is set in order to use SOE Viewer as it only displays information.

n Setting a password for the SCS Maintenance tool

The SCS Maintenance Support Tool requires a password entry every time you start a window
to ensure the security of the SCS access. Password needs to be set for each SENG.
Each tool in the SCS Maintenance Support Tool can be operated for security by entering a
password at the start of each tool. When the password entry is cancelled, the tools' opera-
tions are disabled for security and the window is in the read-only mode.
The following table shows whether tools can be operated or not when the password is en-
tered and when password entry is cancelled.

Table A2.3-1 Operation of SCS Maintenance Support tool

Operations provided se- Without inputting a
Tool Inputting a password
curity password
IOM Download Enabling operation Read Only
Output Enable Operation Enabling operation Read Only
SCS State Management
Window Output Module Start Op-
Enabling operation Read Only
eration
Setting Time Enabling operation Read Only
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.3 Security of SCS Maintenance Support tool > A2-9
Table A2.3-1 Operation of SCS Maintenance Support tool (Table continued)
Operations provided se- Without inputting a
Tool Inputting a password
curity password
Confirmation and Dele-
Diagnostic Information
tion of Diagnostic infor- Enabling operation Read Only
Window
mation
Setting and change of
display font, color and
Setup Tool operating methods for Enabling operation Read Only
confirming or deleting
messages
Display of events of SCS
SOE Viewer Enabling operation Enabling operation
and generation of report
Setting of message col-
lection, initialization of
Message Cache Tool TRIP information in SCS Enabling operation Read Only
and storage and deletion
of cache data.

n How to set and change a password for SCS Maintenance Support

tool
The Change Maintenance Support Password dialog box is used to specify or change the
password that the user must enter when starting the SCS Maintenance Support Tool.
To use SCS Maintenance Support Tool, make sure to set the password first.
TIP No password is set automatically after installing SENG. Make sure to set a password at this stage.

Password: ********

OK Cancel Change Password…

Figure A2.3-2 Input Maintenance Support Password dialog box

2. Click the [Change Password] button.

The Change Maintenance Support Password dialog box appears.
Change Maintenance Support Password

Old Password: ********

New Password: ********

Confirm New Password: ********

OK Cancel

Figure A2.3-3 Change Maintenance Support Password dialog box

3. Enter the current password in the [Old Password:] field. Enter a new password in the
[New Password:] field, and once again in the [Confirm New Password:] field.
The passwords you have entered appear as a series of asterisks (*).

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.3 Security of SCS Maintenance Support tool > A2-10
4. Click [OK].
The password is set.

l Specification for passwords

• A password is 16 alphanumeric characters(*1)consisting of 1 through 16 alphanumeric
characters which are case sensitive.
• Set a password for each SENG-installed PC.
• There is no password when SENG is installed for the first time.
• Set a password when starting the SCS Maintenance Support Tool for the first time.
*1: Including a space character and
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` | ~

n How to enter SCS Maintenance Support tool password

To start SCS Maintenance Support Tool, the correct password must be entered.
Once you enter the correct password, you are allowed to perform writing and customization
operations using SCS Maintenance Support Tool.

IMPORTANT
If you fail to enter the correct password, SCS Maintenance Support Tool is started in the read-
only status.

1. Open the window related to SCS Maintenance Support Tool from SCS Manager or [Start]
menu of Windows.
When the window requiring a password is opened, the Input Maintenance Support Pass-
word dialog box appears.
If the current window is called from another window of SCS Maintenance Support Tool,
the Input Maintenance Support Password dialog box does not appear, because the se-
curity is inherited.

Input Maintenance Support Password

Password: ********

OK Cancel Change Password…

Figure A2.3-4 Input Maintenance Support Password dialog box

2. Enter a password in [Password:] text box.

All characters you enter are displayed as asterisks (*).
3. Click the [OK] button.
If you enter the correct password, the window is opened in the read/write status.
Click the [Cancel] button to start the window related to SCS Maintenance Support Tool in
the read-only status.
Click the [Change Password] button to display the Change Maintenance Support Pass-
word dialog box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A2.4 Access control and history management> A2-11

A2.4 Access control and history management

When using the Access Control and Operation History Management Package, the functions
that can be used by a user are restricted based on the access rights for that user.
SEE
ALSO For more information about the Access Control and Operation History Management Package, refer to:
E., “Access Control/Operation History Management functions” in Engineer's Reference Manual (IM
32P04B10-01EN)

n User management
The package has a function that enables management of the users who work with SCS Man-
ager and the SCS Maintenance Support Tool. In AD Suite, you can set access rights to the
targets of operation for each user role. The user management function is used to register and
delete engineers and manage the passwords of engineers. It also keeps records of the opera-
tions that were performed by each user.

n Access control
The access control function enables you to check engineers who operate the SENG, restrict
login or operations on the SENG, and control authorization of engineering operations.
In AD Suite, you can define access rights to files and folders on the AD Server and various
functions for all users who perform engineering and maintenance of ProSafe-RS.

n Operation history management

This function enables to keep a log of the operations performed by an engineer on the SENG
and save the changed project information when a download to an SCS is performed.
In AD Suite, operation history management is available for the following editors and features:
• Safety I/O Editor, Safety Communication I/O Editor, and IOM Definition Editor of AD Or-
ganizer
• SCS Manager, builders, and tools including the SCS Maintenance Support Tool
• RS Generation Manager
The change history on all builders and editors is saved on the AD Server and can be viewed
in the history window of AD Organizer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A3. Time synchronization> A3-1

A3. Time synchronization

SCS is capable of synchronizing the time among SCSs, SCS and DI modules to make the
event log accurate.

n Time synchronization method

SCS for Vnet/IP: Vnet/IP time synchronization is the only option.

Table A3-1 Time synchronization methods

Type Target SCS Description
The system time of SCSs that are connected on Vnet/IP is
synchronized with the Vnet/IP network time. If an SNTP
server is installed, it is possible to achieve highly accurate
time synchronization with the absolute time. The time syn-
Vnet/IP time synchronization For Vnet/IP chronization status can be checked in the SCS State Man-
agement window of the SCS Maintenance Support Tool on
SENG, or in the SCS Status Display view on HIS. In Vnet/IP
time synchronization, all the stations in one time group that
are connected with control bus have the same time data.

l Vnet/IP time synchronization method configuration

The following describes the configuration for Vnet/IP time synchronization method.
SENG

Vnet/IP time

Time Time
master notification Time
notification
Standard time
SNTP Vnet/IP
server domain 1
(Installed as necessary)

Time
notification SCS

CPU
Vnet/IP time

Time
setting
DI module

Vnet/IP time

Figure A3-1 Synchronization with Vnet/IP time

• The SCS system time is synchronized with the Vnet/IP network time. When using the
synchronization with Vnet/IP time, all stations in the same time group on the Vnet/IP net-
work have the same time information as the clock master. If an SNTP server is installed,
the SCS system time is synchronized with the standard time of the SNTP server.
• If the SCS system time is synchronized with the SNTP server time, any time change set-
ting from the SENG or HIS is ignored.
• If the SNTP server is shut down or the SNTP server is not synchronized with the standard
time, the SCS system time is automatically synchronized with the clock master of the

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A3. Time synchronization> A3-2
same time group (synchronized with internal clock). Accuracy with the standard time
drops, but time accuracy between stations is maintained.

l Time broadcast to DI modules

The CPU broadcasts the time to DI modules mounted in the station every second.

l Selection of Time synchronization method

You can set this method by using the SCS Constants Builder.
For SCSP1/SCSP2/SCSP3, the Vnet/IP time synchronization method is automatically selec-
ted as the time synchronization method.

n Precautions when changing the time in Vnet/IP time synchronization

• If the Vnet/IP time synchronizes with the SNTP server, time setting from SENG or HIS is
ignored.
• Changing the Vnet/IP time may cause the SOE generation order to be reversed. Be sure
to take the timing to set the time and the difference of the time into consideration when
setting the V net time.

IMPORTANT
Do not change the Vnet/IP time from more than one SENG or HIS concurrently. It may cause
the following errors:
• Self-diagnosis function detects a clock error on the running non-redundant SCS and a
system alarm is raised.
• Self-diagnosis function detects a clock error on one of the running redundant SCS and
the control right is switched to the standby CPU module.
As a rule, time changes from an HIS/SENG should be made when both buses in the Vnet/IP
network are in a normal state. If you change the time from an HIS/SENG during a network
failure, there may be stations on which the time does not change immediately, depending on
which area of the network has failed and the circumstances of the failure.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A4. Overview of SCS software configuration > A4-1

A4. Overview of SCS software

configuration
SCS is equipped with an application logic execution function for detecting dangerous situa-
tions and executing control to prevent or mitigate such situations and an external connection
function inclusive of functions for integration with CENTUM which is the production control
system of Yokogawa Electric. Note that these functions exchange data with a station on the
control bus via a control bus communication function which serves as an interface. In particu-
lar, when data is being written into the application logic execution function, the memory inside
the SCS is protected with various functions for ensuring safety with such as security levels.
CENTUM
PRM
(managing HART devices)
SENG HIS FCS

Control bus
SCS
DCS of other companies
Control bus communication function (Higher-level System)

Modbus
Application logic Communication
execution function External
communication function Subsystem
Application logic
execution Modbus
Communication
AIO/DIO data
input/output function ProSafe-SLS

Communication data ProSafe-SLS

input/output function
Communication
Inter-SCS safety
communication function

SCS Link Fire and Gas

Transmission function Communication

Diagnostic function HART Device

SENG: Station that handles engineering and maintenance of SCS

HIS: Station that executes operation and monitoring of CENTUM
FCS: Control station of CENTUM
PRM: Plant Resource Manager

Figure A4-1 Overview of SCS function configuration

n Application logic execution function

This function monitors the safety condition of the plant and makes the process shift to the
safety state on detecting any hazards. It mainly performs the following processing.
• Receiving Analog Input (AI)/Digital Input (DI) data from the field
• Execution of user-defined application logic
• Sending Analog Output (AO)/Digital Output (DO) data to the field
• Inter-SCS safety communication

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A4. Overview of SCS software configuration > A4-2
• SCS link transmission
• Communication data I/O (subsystem communication function, safety subsystem commu-
nication function)
• Self-diagnosis

l Application logic
An SCS executes application logic written in the IEC 61131-3 program language. The applica-
tion logic is defined by the user using Multi Language Editor and downloaded to the SCS.
An SCS supports the following three languages of IEC 61131-3:
• Function Block Diagram (FBD)
• Ladder Diagram (LD)
• Structured Text (ST)
TIP The application logic execution function explained here is not simply a name for a function that handles exe-
cution of the application logic; rather, it is a generic name for all the functions explained above, including the
actual execution of the application logic. In this manual, this term is used in the following explanation as well.

SEE
ALSO For more information about Function Block Diagram (FBD), Ladder Diagram (LD), refer to:
1., “Overview of POU” in POU Reference Manual (IM 32P03B20-01EN)
For more information about Structured Text (ST), refer to:
2., “Structured text” in POU Reference Manual (IM 32P03B20-01EN)

n External communication function

This is a function for exchanging information with external systems connected to an SCS and
it does not influence the application logic execution function. Main operations are as follows:
• Diagnostic information collection function
• SOER function
• CENTUM Integration Function
• FAST/TOOLS integration function (SCSP1, SCSP2 and SCSU1)
• Modbus slave communication function
• PRM-supported HART On-demand Communication
• DNP3 communication function (SCSU1 only)

l PRM-supported HART on-demand communication

On-demand communication with a HART device is implemented by PRM issuing a HART
command, and then receiving a response from the HART device via the SCS. Analog Input/
Output modules with HART function serve as communication relays. Specifically, they receive
HART communication frames from PRM and send them directly to HART devices, while re-
ceiving HART communication frames from HART devices and returning them directly to PRM.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-1

A5. SCS hardware

This section describes the hardware configuration in the SCS, and the important points to de-
termine the configuration.

n Safety control unit

The following types of safety control units are available:

Table A5-1 Types of safety control unit

Safety control
Model Name
unit fan
S2SC70D-S Duplexed safety control unit (for N-IO/FIO, rack mountable type) No
Duplexed safety control unit (for N-IO/FIO, rack mountable type, wide-
S2SC70D-F Yes
range temperature type)
S2SC70S-S Safety control unit (for N-IO/FIO, rack mountable type) No
Safety control unit (for N-IO/FIO, rack mountable type, wide-range tem-
S2SC70S-F Yes
perature type)
Duplexed safety control unit (for Vnet/IP, rack mountable type, stand-
SSC60D-S No
ard type)
Duplexed safety control unit (for Vnet/IP, rack mountable type, wide-
SSC60D-F Yes
range temperature type)
SSC60S-S Safety control unit (for Vnet/IP, rack mountable type, standard type) No
Safety control unit (for Vnet/IP, rack mountable type, wide-range tem-
SSC60S-F Yes
perature type)
Duplexed safety control unit (for Vnet/IP-Upstream, rack mountable
SSC57D-S No
type, standard type)
Duplexed safety control unit (for Vnet/IP-Upstream, rack mountable
SSC57D-F Yes
type, wide-range temperature type)
Safety control unit (for Vnet/IP-Upstream, rack mountable type, stand-
SSC57S-S No
ard type)
Safety control unit (for Vnet/IP-Upstream, rack mountable type, wide-
SSC57S-F Yes
range temperature type)
Duplexed safety control unit (for Vnet/IP, rack mountable type, stand-
SSC50D-S No
ard type)
Duplexed safety control unit (for Vnet/IP, rack mountable type, wide-
SSC50D-F Yes
range temperature type)
SSC50S-S Safety control unit (for Vnet/IP, rack mountable type, standard type) No
Safety control unit (for Vnet/IP, rack mountable type, wide-range tem-
SSC50S-F Yes
perature type)
Duplexed safety control unit (for Vnet, rack mountable type, standard
SSC10D-S No
type)
Duplexed safety control unit (for Vnet, rack mountable type, wide-
SSC10D-F Yes
range temperature type)
SSC10S-S Safety control unit (for Vnet, rack mountable type, standard type) No
Safety control unit (for Vnet, rack mountable type, wide-range tempera-
SSC10S-F Yes
ture type)

l Combination of the safety control unit and CPU module

The following shows the applicable combinations of safety control unit models and CPU mod-
ules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-2
Table A5-2 Applicable combinations of safety control unit models and CPU modules
Safety control unit model CPU module
SSC10S/SSC10D SCP401
SSC50S/SSC50D SCP451
SSC57S/SSC57D SCP451
SSC60S/SSC60D SCP461(*1)
S2SC70S/S2SC70D SCP461 (Style 2)
*1: Style 1 and style 2 can be used. When the CPU module is made redundant, these styles can be mixed.

l Definition of SCS station types

Define a station type matching the hardware in the SCS Project Properties window called
from SCS Manager. If a CPU module not supported by the defined station type is installed on
the control side of SCS, a warning is displayed at offline download. The CPU module will not
start even if offline download is executed ignoring the warning. If a correct CPU module is in-
stalled on the control side but a CPU module different from the definition is installed on the
standby side, the CPU module on the standby side will not start.

n SCS hardware configuration

If the safety control unit is S2SC70D or S2SC70S (SCSP3), these three following methods
are available to connect the I/O node to the SCSP3:
• N-IO nodes only connection
• Safety node units only connection
• Combined connection of N-IO nodes and safety node units
If the safety control unit is SSC60D or SSC60S (SCSP2), only the safety node unit can be
connected.

l N-IO node only connection

The following configuration are used when connecting only the N-IO nodes to the safety con-
trol unit.
When connecting the safety control unit and N-IO nodes by using the N-ESB bus, the
S2EN402/S2EN404 is mounted to the safety control unit, and S2EN501 to the N-IO node.
When connecting the safety control unit and N-IO node by using the optical ESB bus, the
SEC401/SEC402 is mounted to the safety control unit, and S2EN501 to the N-IO node.
The connection between N-IO nodes must be connected with the N-ESB bus or the optical
ESB bus.
The following figure shows an example of configuration with N-IO nodes-only connection.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-3

SPW48x: Power supply module for SCU and SNU ESB bus
SCP461 S2: Processor module
S2EN40x: N-ESB bus coupler module SCU
S S S S
PSM: Power supply module for N-IO node 2 2 S S S S C C S S SCSP3
S2EN501: N-ESB bus module E E N N E E
N N T T C C P P P P
N-IO: N-IO I/O module 4 4 4 4 4 4 4 4 W W
SNT4x1: Optical bus repeater master module 0 0 x x 0 0 6 6 4 4
x x 1 1 x x 1 1
SNT5x1: Optical bus repeater slave module 8 8
SEC40x: ESB bus coupler module S S x x
2 2
SSB401: ESB bus slave module
FIO: FIO I/O module
N-ESB bus Optical ESB bus

N-IO node N-IO node

S S S S
2 2 2 2
E E P P E E P P
N N N N
N N S S - - N N S S - -
5 5 M M 5 5 M M
0 0 I I 0 0 I I
1 1 O O 1 1 O O
N-ESB bus Optical ESB bus

N N N N N N N N
- - - - - - - -
I I I I I I I I
O O O O O O O O

N-IO node N-IO node

S S S S
2 2 2 2
E E P P E E P P
N N N N
N N S S - - N N S S - -
5 5 M M 5 5 M M
0 0 I I 0 0 I I
1 1 O O 1 1 O O

N N N N N N N N
- - - - - - - -
I I I I I I I I
O O O O O O O O

Figure A5-1 Configuration example of an N-IO node-only connection

Table A5-3 SCS main hardware

Name Description Note
CPU CPU module SCP461 (SSC60 only), SCP461 S2
FIO FIO I/O module -
N-IO NIO I/O module -
PSM Power supply module Model SPW48x, always redundant
SEC401/ ESB bus coupler module Used when SNU and N-IO nodes are used.
SEC402 Installed in slots 7 and 8 of SCU (always re-
dundant).
SSB401 ESB bus interface module Always redundant
SCU Safety control unit S2SC70D/S2SC70S
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-4
Table A5-3 SCS main hardware (Table continued)
Name Description Note
SNU Safety node unit SNB10D
N-IO node Node for installing N-IO Configured with node interface unit and N-IO
I/O unit.
ESB bus Bus to connect SCU and SNU
N-ESB bus Bus to connect SCU and N-IO node
Optical ESB Bus to connect SCU, SNU, and N-IO
bus node

l Safety node unit only connection

The following configuration are used when connecting only the safety node units to the safety
control unit.
When connecting the safety control unit and safety node unit by using the ESB bus, the
SEC401/SEC402 is mounted to the safety control unit, and SSB401 to the safety node unit.
When connecting the safety control unit and safety node unit by using the optical ESB bus,
the SEC401/SEC402 and SNT401/SNT411 is mounted to the safety control unit, and
SNT501/SNT511 and SSB401 to the safety node unit.
The connection between the safety node units must be connected with an ESB bus, or an op-
tical ESB bus through SNT401/SNT411 and SNT501/SNT511.
The following figure shows a configuration example of a safety node units-only connection.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-5

SPW48x: Power supply module for SCU and SNU ESB bus
SCP461 S2: Processor module
S2EN40x: N-ESB bus coupler module
S S SCU
PSM: Power supply module for N-IO node S S S S C C S S SCSP2/SCSP3
S2EN501: N-ESB bus module F F F F N N E E
T T C C P P P P
N-IO: N-IO I/O module I I I I 4 4 4 4 4 4 W W
SNT4x1: Optical bus repeater master module x x 0 0 6 6 4 4
O O O O 1 1
1 1 x x 8 8
SNT5x1: Optical bus repeater slave module
SEC40x: ESB bus coupler module S S x x
2 2
SSB401: ESB bus slave module
FIO: FIO I/O module
Optical ESB bus ESB bus

SNU SNU

S S S S S S S S S S S S
F F F F N N N N S S P P F F F F F F F F S S P P
T T T T B B B B
I I I I 5 5 4 4 4 4 W W I I I I I I I I 4 4 W W
O O O O x x x x 0 0 4 4 O O O O O O O O 0 0 4 4
1 1 1 1 1 1 8 8 1 1 8 8
x x x x

ESB bus
ESB bus
Optical ESB bus

SNU SNU

S S S S S S S S S S
F F F F F F N N S S P P F F F F F F F F S S P P
T T B B B B
I I I I I I 5 5 4 4 W W I I I I I I I I 4 4 W W
O O O O O O x x 0 0 4 4 O O O O O O O O 0 0 4 4
1 1 1 1 8 8 1 1 8 8
x x x x

ESB bus

Figure A5-2 Configuration example of a safety node units-only connection

l Combined connection of N-IO node and safety node unit

N-IO nodes and safety node units can be connected to a single safety control unit. To use
both nodes together, you can connect the N-IO node and safety node unit, or separate them.
• Connecting N-IO nodes and safety node units together
When connecting the safety control unit together with the safety node units and N-IO no-
des, connect with the following configuration.
When connecting the safety control unit and N-IO node using the optical ESB bus, the
SEC401/SEC402 and SNT401/SNT411 are mounted to the safety control unit, and
S2EN501 to the N-IO node.
N-IO node and safety node unit are connected through an optical ESB bus. SNT501/
SNT511 and SSB401 are installed to the safety node unit.
The following figure shows a configuration example of an N-IO node and safety node unit
connection.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-6
ESB bus
SPW48x: Power supply module for SCU and SNU
SCP461 S2: Processor module
S2EN40x: N-ESB bus coupler module S S SCU
S S S S C C S S
PSM: Power supply module for N-IO node E E SCSP3
F F F F N N
P P P P
S2EN501: N-ESB bus module T T C C
4 4 W W
I I I I 4 4 4 4
N-IO: N-IO I/O module 0 0 6 6 4 4
O O O O x x
1 1
SNT4x1: Optical bus repeater master module 1 1 x x 8 8
SNT5x1: Optical bus repeater slave module S S x x
SEC40x: ESB bus coupler module 2 2
SSB401: ESB bus slave module
FIO: FIO I/O module
Optical ESB bus

N-IO node

S S
2 2
E E P P
N N
N N S S - -
5 5 M M
0 0 I I
1 1 O O

N N N N
- - - -
I I I I
O O O O

Optical ESB bus

SNU

S S S S S S
F F F F F F N N S S P P
T T B B
I I I I I I 5 5 4 4 W W
O O O O O O x x 0 0 4 4
1 1 1 1 8 8
x x

ESB bus

Figure A5-3 Configuration example of an N-IO node and safety node unit connection

• Separating N-IO nodes and safety node units, and connecting them together
When N-IO nodes and safety node units are separated from each other, and they are
connected with the safety control unit, the N-IO nodes-only connection and the safety
node units-only connection are combined.
The following figure shows a configuration example when N-IO node and safety node unit
are separated and connected together.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-7
SPW48x: Power supply module for SCU and SNU
SCP461 S2: Processor module
S2EN40x: N-ESB bus coupler module S S S S SCU
2 2 S S C C S S
PSM: Power supply module for N-IO node E E SCSP3
F F F F E E P P P P
S2EN501: N-ESB bus module N N C C
4 4 W W
I I I I 4 4 4 4
N-IO: N-IO I/O module 0 0 6 6 4 4
O O O O 0 0
1 1
SNT4x1: Optical bus repeater master module x x x x 8 8
SNT5x1: Optical bus repeater slave module S S x x
SEC40x: ESB bus coupler module 2 2
SSB401: ESB bus slave module
FIO: FIO I/O module
N-ESB bus ESB bus

N-IO node SNU

S S S S S S
2 2 F F F F F F F F S S P P
E E P P B B
N N I I I I I I I I 4 4 W W
N N S S - - 0 0 4 4
5 5 O O O O O O O O
0 0
M M I I 1 1 8 8
1 1 O O x x

N N N N
- - - -
I I I I
O O O O

Figure A5-4 Configuration example when N-IO node and safety node unit are separated and connec-
ted together

n Restrictions on installation of hardware

There are the following restrictions on the installation of hardware on the SCS.
• To connect a safety node unit, you need to install SEC401 in slots 7 and 8 of the safety
control unit. If you want to connect 10 or more safety node units with SCSP2 or SCSP3,
install SEC402 instead. If I/O expansion is not required, you can install I/O modules in
slots 7 and 8.
• When installing redundant I/O modules in a safety node unit, you can install the modules
in pairs into slots 1 and 2, slots 3 and 4, slots 5 and 6, or slots 7 and 8.
• Up to 8 fire and gas communication modules (S2LP131) can be installed per SCS.
• For subsystem communication, a maximum of four (up to two pairs in redundant configu-
ration) serial communication modules (ALR111, ALR121) and Ethernet communication
modules (ALE111) can be installed per SCS.
• For Modbus slave communication, a total maximum of two modules among serial com-
munication modules (ALR111, ALR121) and Ethernet communication module (ALE111)
can be installed.
• In SCSU1, up to two ALE111 modules can be installed for communication as a DNP3
slave.
• A total maximum of eight serial communication modules (ALR111, ALR121) and Ethernet
communication modules (ALE111) can be installed per SCS of type SCSU1, and a total
maximum of six per SCS of other types of SCS.
• You cannot install the serial communication modules (ALR111, ALR121) and the Ethernet
communication module (ALE111) for Modbus slave communication in the safety node unit
that is located beyond 5 km by using the optical ESB bus repeater module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-8
SEE
ALSO For more information about implementation restrictions of the N-IO I/O module, refer to:
ProSafe-RS Outline of I/O Modules (for N-IO) (GS 32P06F10-01EN)
For more information about installation restrictions of the FIO I/O module, refer to:
ProSafe-RS Outline of I/O Modules (for FIO) (GS 32P06K60-01EN)
For more information about operating temperature of the safety control unit, refer to:
ProSafe-RS Installation Guidance (TI 32P01J10-01EN)

l I/O module types

The available types of I/O modules include analog I/O module (AIO: Analog Input/Analog Out-
put), discrete I/O module (DIO: Digital Input/Digital Output), and a universal type I/O module
where the signal category for channels can be changed by software. In addition, communica-
tion modules are available for communications with external devices.
TIP If the SCS project was created by SENG of the software release number that does not support the module
you want to use, you cannot use that I/O module in the SCS project. To use the I/O module, you must create
a new SCS project on the SENG of the software release number that supports the module and perform offline
download to the SCS.

The following table shows the AIO/DIO modules for which input/output can be defined and
communication modules.

Table A5-4 AIO/DIO modules for which input/output can be defined and communication modules
Redundancy
Model Type AIO/DIO
(*1)
SAI143 4 to 20 mA, 16-channel, module isolation Analog Input Yes
SAV144 1 to 5 V/1 to 10 V, 16-channel, module isolation Analog Input Yes
SAT145 Thermocouple/mV, 16-channel, isolated channels Analog Input Yes
SAR145 RTD, 16-channel, isolated channels Analog Input Yes
SAI533 4 to 20 mA, 8-channel, module isolation Analog Output Yes
SDV144 24 V DC, 16-channel, module isolation Digital Input Yes
SDV521 24 V DC, 4-channel, module isolation Digital Output Yes
SDV526 100-120 V AC, 4-channel, module isolation Digital Output Yes
SDV531 24 V DC, 8-channel, module isolation Digital Output Yes
SDV53A 48 V DC, 8-channel, module isolation Digital Output Yes
SDV541 24 V DC, 16-channel, module isolation Digital Output Yes
S2MMM843 (*2) 16-channel, module isolation AI/AO/DI/DO Yes
S2MDV843 (*2) 16-channel, module isolation DI/DO Yes
ALR111 Serial communications module (RS-232C, 2-port) - Yes (*3)
Serial communications module (RS-422/RS-485, 2-
ALR121 - Yes (*3) (*4)
port)
ALE111 (*5) Ethernet communication module (10BASE-T, 1-port) - Yes (*6)
Fire and gas communication module (100BASE-TX,
S2LP131 (*2) - No
1-port)
*1: Yes : Possible
No : Impossible
*2: Can use SCSP3 only.
*3: If redundant configuration is required for the Modbus slave communication, you need to use two serial communication mod-
ules and control the communication route by the Modbus master.
*4: When ALR121 is used for ProSafe-SLS communication function, the redundant configuration cannot be set by using two
modules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-9
*5: When the CPU node of SCS is SSC10D or SSC10S, do not define ALE111.
*6: If redundant configuration is required for the Modbus slave communication, you need to use two Ethernet communication
modules and control the communication route by the Modbus master. For DNP3 slave function, the redundant configuration
cannot be set by using two modules.

l Analog Input/Output modules

Analog input/output modules are used to input/output analog signals indicating electrical cur-
rent, voltage, etc. The types (models) of analog input/output modules are shown as follows.

Table A5-5 Specification of analog Input/Output modules

Number of Redundan-
Classification Type Description SIL support
channels cy
Analog input SAI143 4 to 20 mA, isolated. 16 Allowed 3
SAV144 1 to 10 V, isolated. 16 Allowed 3
Thermocouple/mV, isolated
SAT145 16 Allowed 3
channels
Resistance temperature de-
SAR145 16 Allowed 3
tector, isolated channels
Analog output SAI533 4 to 20 mA, isolated. 8 Allowed 3

• SAI143
An analog input module for electrical current. Modules whose suffix code is SAI143-H
support HART communication and are indicated as SAI143H in the SCS State Manage-
ment Window on the SENG or the Status Display view on the HIS. SAI143-H can be used
with software release number of R1.02.00 or later.
• SAV144
An analog input module for electrical voltage.
• SAT145
An analog input module for thermocouple (TC)/mV. This module can be used with soft-
ware release number R3.01.00 or later.
• SAR145
An analog input module for the resistance temperature detector (RTD). This module can
be used with software release number R3.01.00 or later.
• SAI533
An analog output module for electrical current. This module can be used with software re-
lease number of R1.02.00 or later. These modules are indicated as SAI533H in the SCS
State Management Window on the SENG or the Status Display view on the HIS. This
module supports HART communication.

l Discrete Input/Output modules

Discrete inputs and outputs are process inputs and outputs that use discrete on/off signals.
The following shows the I/O module types (model names) that can be used for discrete inputs
and outputs.

Table A5-6 Specification of discrete Input/Output modules

Number of Redundan-
Classification Type Description SIL support
channels cy
Discrete input SDV144 24 V DC, module isolation 16 Possible 3
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-10
Table A5-6 Specification of discrete Input/Output modules (Table continued)
Number of Redundan-
Classification Type Description SIL support
channels cy
Discrete output SDV521 24 V DC, module isolation 4 Possible 3
SDV531 24 V DC, module isolation 8 Possible 3
SDV531-L 24 V DC, module isolation 8 Possible 3
SDV53A 48 V DC, module isolation 8 Possible 3
SDV541 24 V DC, module isolation 16 Possible 3
100-120 V AC, module isola-
SDV526 4 Possible 3
tion

• SDV144
A discrete input module. This module provides SOER (Sequence of Events Recorder)
function.
• SDV521
This module is for 4-channel discrete output.
• SDV531
A 8-channel discrete output module.
• SDV531-L
This module is for 8-channel discrete output for long distance.
• SDV53A
This module is for 8-channel 48 V DC discrete output.
• SDV541
This module is for 16-channel discrete output.
• SDV526
This module is for 4-channel 100-120 V AC discrete output.
TIP • Short circuits between channels cannot be detected in SDV526. In addition, the following faults cannot
be detected while the output is OFF.
• Short circuits in output wiring
• Output overload (faults in field devices that cause short circuits or overcurrent when the module's out-
put is set to ON)
• Satisfy either of the following conditions when creating an application logic which repeatedly outputs ON
and OFF with SDV526.
• The signal value is maintained for at least 1 s with each ON signal.
• The signal value is maintained for at least 1 s with each OFF signal.
These are conditions required in order to detect wiring errors and internal failures and correctly notify
diagnosis information. There are no restrictions for cases involving the output of single-shot pulses.

l Universal type I/O module

The signal category of the universal type I/O module can be switched by software.
The following table shows the types (models) of the universal type I/O module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-11
Table A5-7 Universal type I/O module specifications
Model Name Description Number of Redun- Compati-
channels dancy ble SIL
S2MMM8 Analog digital I/O 16 channel, module Isolation 16 Allowed 3
43 module Analog I/O (AI/AO): 4 to 20 mA,
HART compatible
Digital I/O (DI/DO): 24V DC
You can switch the signal category
to AI, AO, DI, or DO for each
channel.
To use analog output (AO), it is 8
channels for every I/O module.
For digital output (DO), a high cur-
rent output function that combines
two or three consecutive channels
is supported. 1.3 A, 2.0 A
S2MDV84 Digital I/O Module 16 channel, module Isolation 16 Allowed 3
3 Digital I/O (DI/DO): 24V DC
You can switch the signal category
to DI or DO for each channel.
For digital output (DO), a high cur-
rent output function that combines
two or three consecutive channels
is supported. 1.3 A, 2.0 A

TIP Satisfy either of the following conditions when creating an application logic which repeatedly outputs ON and
OFF with the DO of S2MMM843 or S2MDV843:
• The signal value is maintained for at least 0.5 s with each ON signal.
• The signal value is maintained for at least 2 s with each OFF signal.
However, there are no restrictions for cases involving the output of single-shot pulses.
Failure detection may not be available in cases when ON/OFF signals are continuously modified in cycles
which never satisfy either one of the conditions.
Example of a case where failure detection will be unavailable: An application logic which repeatedly outputs
an ON signal for 0.3 s and an OFF signal for 0.3 s
Examples of cases where failure detection will be available:
• An application logic which repeatedly outputs an ON signal for 0.5 s and an OFF signal for 0.5 s
• An application logic which repeatedly outputs an ON signal for 0.3 s and an OFF signal for 2 s
The DO of S2MMM843 and S2MDV843 performs a diagnosis of short circuits and disconnected wiring upon
the output of a signal. However, a certain amount of time is required from when the output has changed to
when the diagnosis result is refreshed.
• When the signal has changed from OFF to ON, a maximum of 0.5 s is required from when the output has
changed to when the diagnosis result is refreshed.
• When the signal has changed from ON to OFF, a maximum of 2 s is required from when the output has
changed to when the diagnosis result is refreshed.
When a change of output is repeated in a shorter interval than the time required to refresh the diagnosis re-
sults, a state where the diagnosis results are not updated will continue. Refrain from creating such applica-
tion.

l Serial communication modules

Serial communication modules are used to implement Modbus slave communication, where
an SCS acting as a Modbus slave communicates with an external device acting as the Mod-
bus master, and are also used to implement subsystem communication, where an SCS com-
municates with a subsystem.
• ALR111: Serial communication module (RS-232C)
It is an interference-free communication module with an RS-232C interface.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-12
• ALR121: Serial communication module (RS-422/RS-485)
It is an interference-free communication module with an RS-422 or RS-485 interface.
Take note on the following cautions when using the serial communication modules:
• You need to prepare separate modules for Modbus slave communication and subsystem
communication.
• When used for Modbus slave communication, serial communication modules cannot
have a redundant configuration. If redundancy is required, use two serial communication
modules and provide redundancy using a user application.
• Serial communication modules can be configured as redundant modules if used for sub-
system communication.
• In a safety control station, the serial communication module for Modbus slave communi-
cation cannot be implemented in the safety node unit that is installed at a distance longer
than 5 km by using an optical ESB bus repeater module.

l Ethernet communication module

The Ethernet communication module is used to establish the Modbus slave communication
that connects the external device of the Modbus master with the SCS of the Modbus slave,
and the subsystem communication that connects the SCS with the subsystem. It is also used
for the DNP3 communication in SCSU1.
• ALE111: Ethernet communication module
It is an interference-free communication module with a 10BASE-T interface.
Take note on the following cautions when using the Ethernet communication module:
• When used for Modbus slave communication, the Ethernet communication modules can-
not have redundant configuration. If redundancy is required, you need to use two Ether-
net communication modules and provide redundancy through user application.
• The modules can be configured as redundant modules if used for subsystem communica-
tion.
• The Ethernet communication module used for Modbus slave communication or DNP3
communication cannot be installed in the FIO node that is located beyond 5 km by using
the optical ESB bus repeater module.

l Fire and gas communication module

The fire and gas communication module can be used for fire and gas communication to con-
nect to gas detectors.
• S2LP131: Fire and gas communication module
A communication module with a 100BASE-TX interface.
Take note on the following cautions when using a fire and gas communication module:
• The modules cannot have a redundant configuration.

l Devices related to optical ESB bus repeater

ProSafe-RS allows for locating I/O nodes at remote places by using Optical ESB Bus Repeat-
er modules. I/O nodes are connected on the ESB bus (the I/O bus of the SCS) network which
is extended by using Optical ESB Bus Repeater master modules (SNT401/SNT411) and Opti-
cal ESB Bus Repeater slave modules (SNT501/SNT511). Both the demand reaction time and
fault reaction time are the same as those when I/O nodes are connected with non-optic ESB
bus cables.
The following is an outline of the Optical ESB Bus Repeater connection functions.
• Maximum number of nodes (CPU node not included)
When SEC401 is used (SCSV1/SCSP1/SCSP2): 9 /SCS

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-13
When SEC402 is used (SCSP2/SCSP3 with FIO): 13 /SCS
When SEC402 is used (SCSP3 with N-IO): 32 /SCS
• Topology: Chain, star, or a mix of the two
• Maximum optical fiber cable extension distance (*1): In SCSV1, it is 5 km, and in
SCSP1/SCSP2/SCSP3, it is 50 km.
• Maximum distance between SNT401 and SNT501 (length of fiber-optic cable between
layers): 5 km
• Maximum distance between SNT411 and SNT511 (length of fiber-optic cable between
layers): 50 km
• Maximum number of layers in fiber-optic cable connection: 2
For SCSP1/SCSP2/SCSP3, a combination of SNT401 and SNT501 or SNT411 and
SNT511 is both allowed. For example, it is possible to connect 2 layers of SNT401 and
SNT501, 5 km each, to extend the distance up to 10 km.
It is also possible to use SNT401/SNT501 for the first layer (5 km), and use SNT411/
SNT511 for the second layer (45 km) for extension to a total of 50 km.
• Where to install Optical ESB Bus Repeater modules: Slots 1 to 6 of CPU nodes, slots 1
to 8 on I/O nodes, and slots 1 to 10 on the Unit for Optical ESB Bus Repeater module
(SNT10D)
• Redundancy: Both Optical ESB Bus Repeater module and fiber-optic cable are always
redundant. (*2)
• Maximum distance of ESB bus cable connection: 10 m; 10 m each for the upper and
lower connectors respectively when SEC402 is used.
*1: The “maximum extension distance of fiber-optic cable” refers to the total extension distance of fiber-optic cable from the CPU
node to the last I/O node connected.
*2: It is recommended to set the same length for left and right fiber-optic cables as a general rule.

ESB bus cable: 10 m max.

ESB bus cable

CPU node I/O node I/O node

Fiber-optic
cable

ESB bus cable

Maximum extension I/O node I/O node I/O node I/O node
distance of
fiber-optic cables
1st layer in fiber-optic cable connection
Fiber-optic
cable

I/O node I/O node I/O node

2nd layer in fiber-optic cable connection

ESB bus cable: 10 m max.

Figure A5-5 Overview of the optical ESB bus repeater connection function (example of connection in
SEC401) with FIO

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-14
N-ESB bus cable: N-ESB bus cable:
100 m max. 100 m max.

CPU node N-IO node N-IO node

N-ESB bus cable N-ESB bus cable

Fiber-optic
cable

Maximum N-ESB bus cable

extension
distance of N-IO node N-IO node
N-IO node N-IO node
fiber-optic
cables
1st layer in fiber-optic cable connection

Fiber-optic
cable

N-ESB bus cable N-ESB bus cable

N-IO node N-IO node N-IO node

2nd layer in fiber-optic cable connection

N-ESB bus cable: N-ESB bus cable:

100 m max. 100 m max.

Figure A5-6 Overview of the optical ESB bus repeater connection function (example of connection in
SEC401) with N-IO

N-ESB bus cable: N-ESB bus cable:

100 m max. 100 m max.

CPU node N-IO node N-IO node

N-ESB bus cable N-ESB bus cable

Fiber-optic
cable

Maximum N-ESB bus cable

extension
distance of N-IO node N-IO node
N-IO node N-IO node
fiber-optic
cables
1st layer in fiber-optic cable connection

Fiber-optic
cable

FIO node FIO node FIO node

2nd layer in fiber-optic cable connection

ESB bus cable: 10 m max.

Figure A5-7 Overview of the optical ESB bus repeater connection function (example of connection in
SEC401) N-IO+FIO

The following table shows the hardware used in relation to the Optical ESB Bus Repeater.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-15
Table A5-8 Hardware related to optical ESB bus repeater
Model Name Description Remarks
Unit dedicated for mounting Optical ESB Bus Re-
peater modules. This unit has redundant power
Unit for Optical ESB Bus
SNT10D supply modules mounted. 10 slots are provided for -
Repeater Module
mounting SNT401s/SNT501s and SNT501s/
SNT511s.
Master module for extending ESB bus with fiber-
Optical ESB Bus Repeater optic cable(s). The distance between SNT401 and
SNT401 -
Master Module SNT501 can be extended up to 5 km (two layers
total, up to 10 km for SCSP1/SCSP2/SCSP3).
Optical ESB Bus Repeater Slave module for extending ESB bus with fiber-op-
SNT501 -
Slave Module tic cable(s).
Master module for extending ESB bus with fiber-
Optical ESB Bus Repeater These mod-
SNT411 optic cable(s). The distance between SNT411 and
Master Module ules cannot
SNT511 can be extended up to 50 km.
be installed
Optical ESB Bus Repeater Slave module for extending ESB bus with fiber-op- in SCSV1
SNT511
Slave Module tic cable(s).

SEE
ALSO For more information about the specifications and installation restrictions of hardware used in relation to the
optical ESB bus repeater, refer to:
ProSafe-RS Safety Instrumented System Overview (for Vnet/IP) (GS 32P01B10-01EN)

l Precautions for mounting the optical ESB bus repeater module

When using SCSU1, observe the same precautions as those for SCSP1.
• The optical attenuation between SNT411 and SNT511 must satisfy the conditions listed in
the following table. If the conditions are not met, use an attenuator to ensure that the con-
ditions are met.

Table A5-9 Required optical attenuation between SNT411 and SNT511

SNT411/SNT511 style Required attenuation
Style S2 and above 3 dB or more
Style S1 1 dB or more

• For SCSP1/SCSP2/SCSP3, the time accuracies for SOE data (discrete inputs) are as fol-
lows:

Table A5-10 Time accuracies of SOE data (discrete inputs) (for SCSP1/SCSP2/SCSP3)
Distance of extension by Optical ESB Bus Repeater
(One of the two target SCSs, whichever the extension distance is lon- Time accuracies
ger.)
No extension ± 1 ms
Extension within 25 km ± 2 ms
Extension from 25 km to 50 km ± 3 ms

• As the load on the SCS increases when the distance of ESB bus extended by the Optical
ESB Bus Repeater module becomes longer, the number of I/O modules that can be in-
stalled may be restricted. The time required for IOM download or communication module
startup becomes longer compared to the cases where the Optical ESB Bus Repeater
module is not used.
The following definitions must be specified when using the optical ESB bus repeater module.
Items to be defined vary depending on the SCS type.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-16
• Required settings in SCSV1 and problems that occur if settings are not made
In SCS Constants Builder, set [Optical ESB Bus Repeater] to [Yes] and specify the cor-
rect maximum extension distance in [Maximum Extension Distance]. If the Optical ESB
Bus Repeater modules are used without these settings, the node data and SOE data will
not be updated correctly.
• Settings required in SCSP2/SCSP3 and issues that arise if the settings are not made
In SCSP2/SCSP3, set the I/O parameter [Extends Node Bus] to [Yes] and specify the
ESB bus distance from the CPU node to the relevant node in [Extends To] for all connec-
ted nodes that are extended through the optical ESB bus repeater modules. Communica-
tion errors may occur between the nodes if the optical ESB bus repeater modules are
used without configuring the nodes settings correctly. If this error occurs, the data of the
I/O module installed in the corresponding nodes and SOE data are not updated correctly.
As a result, the output modules output the output value at fault.
• Settings required for SCSP1 and problems that will occur if settings are not configured
Configure the settings with the following builders.

Table A5-11 Settings required in SCSP1

Builder to be set Required settings Precautions
up
SCS Constants Set [Optical ESB Bus Repeater] to [Yes] If the Optical ESB Bus Repeater modules
Builder and specify the correct maximum exten- are used without these settings, the node
sion distance in [Maximum Extension Dis- data and SOE data will not be updated
tance]. correctly.
I/O Parameter Set the node setting item [Extends Node If you do not specify the distance to the
Builder or Safety I/O Bus] to [Yes] and specify the actual node node, the system behaves as if the corre-
Editor distance on the ESB bus from the CPU sponding I/O node is located at the maxi-
node in [Extends To] for all nodes connec- mum extension distance. Although I/O
ted through optical ESB bus repeater modules function correctly, the CPU load
modules. fluctuation may become large if abnormal-
ities occur. Be sure to specify the node
distance in order to reduce CPU load fluc-
tuation at abnormality occurrence.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A5. SCS hardware > A5-17

IMPORTANT
For Modbus slave communication or, DNP3 communication
The following precautions should be observed for nodes on which Optical ESB Bus Repeater
modules are mounted.
• You must specify the node extension distance in an I/O parameter of the I/O node which
mounts ALR111, ALR121 or ALE111 in SCSP1/SCSP2/SCSP3.
• ALR111, ALR121, or ALE111 cannot be mounted on I/O nodes located at a distance of 5
km or further.
Precautions when mounting SNT401/SNT411 and SNT501/SNT511
• When mounting on SNT10D, you need to set the DIP switch 1 (mounting unit setting) of
SNT401/SNT411 and SNT501/SNT511 to "0". If the switch is set to 1, one-sided errors
of the SNT10D power module will not be reported. (*1)
• When mounting on the CPU node or FIO node, you need to set DIP switch 1 (mounting
unit setting) on the SNT401/SNT411 and SNT501/SNT511 to "1". If it is set to "0", one-
sided errors of the power modules of CPU node or FIO node will cause errors in the
SNT401/SNT411 and SNT501/SNT511 on one side. (*1)
*1: The default setting of DIP switch 1 is 0. This setting status can be checked on the LED display on the front of the module. If
DIP switch 1 is set to 1, the LED display "NODE-1" is turned on in green.

Precaution when performing HART communication

• If the Optical ESB Bus Repeater node extension distance exceeds 25 km on SCSP1 and
HART communication is performed periodically, the scan period must be set to 100 ms or
longer.
Precautions when using a barrier for Digital Input
• When using a barrier for Digital Input, the delay time of the barrier will be added to the
time precision.

SEE
ALSO For more information about delay time of barrier, refer to:
specifications and manual of barrier for Digital Input being used

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6. Inputs and outputs of SCS > A6-1

A6. Inputs and outputs of SCS

This section describes the flow and processing of Analog I/O data and Digital I/O data
(AIO/DIO data), and I/O variables in the SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.1 Flow of AIO/DIO data > A6-2

A6.1 Flow of AIO/DIO data

The following figure illustrates the flow of AIO/DIO data in an SCS.
CPU

Application logic

Function Blocks

Input variable Output variable

Output
enable/disable

I/O Image Input data Status information Output data

Area

Legend
Input module Output module Data Value
Data Status

Sensor device Devices such as valves or lamps

Figure A6.1-1 Flow of AIO/DIO data

1. Data sent from sensor devices or other sources is read from each channel of a connected
input module.
2. The CPU copies the data stored in the input module to the I/O image area at the start of
scanning. At this point, the data value and data status are determined based on the infor-
mation from the input module. If the input data is erroneous, the data status is set to
"BAD" and the data value is set to the "Input value at error occurrence" specified in an I/O
parameter by the user.
TIP The following I/O parameters are used for "Input value at error occurrence", which is used when input data is
erroneous.
• [Input Processing at Fault] of AI and DI modules
• [Input Processing at Transmitter Fault] of an AI module
This manual uses the term "input value at error occurrence" in the following explanation as a generic term.

3. The CPU stores the input data in the I/O image area in the input variables of the applica-
tion logic. It also updates the data status of the output variables.
4. The application logic references the data value and data status from the input variables
and monitors the process conditions and input device status.
5. The result of the application logic processing is stored in the output variables and then
sent to the output module via the I/O image area.
6. The output module outputs the data to devices such as valves or lamps connected to
each of the channels.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.1 Flow of AIO/DIO data > A6-3

n Data value at AIO/DIO module dual-redundant configuration

If dual-redundant input modules are used, the input values from the active module are stored
in the input variables. If dual-redundant output modules are used, the data values of the out-
put variables are sent to both active and standby modules, but the data is only output to the
field from the active module. In the case of SDV526, the data values are output to the field
from both modules.

n Conversion of analog input data

Analog data of either 4 to 20 mA or 1 to 5 V/ 1 to 10 V is converted to normalized data of 0 to
100% in the CPU process data input processing and stored in the input variables.
All data that requires normalization, such as measurements from differential pressure trans-
mitters, is automatically processed in the process data input processing in this way. Subse-
quent conversion from normalized data to data using engineering units can be performed
freely in the application logic. Analog data of either thermocouple or resistance temperature
detector is converted to the data (physical quantity or normalized data) specified in the input
signal conversion for each channel and stored in the input variables.

n Flow of analog output data

Data of 0 to 100% set in IO_REAL type output variables from the application logic are conver-
ted to electrical current of 4 to 20 mA by each output module and output.

n Output enable and output disable

Output channels of an SCS can be in the Output Enable and Output Disable states. The Out-
put Enable and Output Disable states are managed by each channel; the output states of all
the output channels of an SCS do not always match.
• Output Enable is a status where the output values from the application logic are output
from the output module as is.
• Output Disable is a status where the output values from the application logic are not out-
put from the output module.

l Output enable operation

Output enable operation means connecting outputs from the application logic to the output
channels. If you perform the output enable operation from the I/O Channels Status dialog box
of SCS Maintenance Support Tool on the SENG, all modules are placed in the Output Enable
status simultaneously (not individually). Once the output enable operation is performed, all
output channels are in the Output Enable status and output values of the application logic are
output from the output channels. Channels that continue to generate errors remain in the Out-
put Disable status. The following processing is also performed in the output enable operation
implemented immediately after an SCS is started:
• Start sending data in inter-SCS safety communication
• Start SCS Link Transmission
• Start outputting data in subsystem communication

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.2 I/O variable > A6-4

A6.2 I/O variable

This section explains the I/O variables, and their data value and the data status.

n What are I/O variables?

Input variable
input module

Physical data Logical data

Input data Input data Input data

Data status Data status Data status

Lock/unlock variable

Output variable

Logical data Physical data

Output module
Output data Output data Output data

Data status Data status Data status

Lock/unlock variable

Figure A6.2-1 Input variable and output variable

The variables carrying the input values or output values of input/output modules are called I/O
variables. There are two types of I/O variables: input variables and output variables. I/O varia-
bles contain two types of data, logical data and physical data. When I/O variables are defined,
both logical data and physical data are automatically created.

Table A6.2-1 Input variable and output variable

Type Data Description
Input variable Physical data Data set from the I/O image area.
Logical data Data viewed by the application logic. (*1)
Output variable Physical data Data set in the I/O image. (*2)
Logical data Data set by the application logic.
*1: If the input data is erroneous, the input value at error specified by the user in advance is set.
*2: This is the value set to the output module.

The application logic can basically handle logical data only. In the normal status, the same da-
ta is stored in the logical data and physical data; the user does not need to be aware of the
difference between these two types of data. Note, however, that physical data needs to be ref-
erenced from the SCS Manager window when locking I/O variables via the forcing function, or
if both data are not connected due to input/output module failures, etc.
Both the logical data and physical data are composed of data value and data status. In order
to handle data value and data status, I/O variables provide IO_BOOL type for handling
BOOL-type data and IO_REAL type for handling real number-type data, which can be used
according to the data type of the data value.
The data value and data status can be referenced using the application logic. Use the syntax
"I/O variable name.v" and "I/O variable name.status" in order to read only the data value or
the data status from an I/O variable, respectively.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.2 I/O variable > A6-5

l Data status of I/O variables

The data status of I/O variables is expressed as a BOOL value.

Table A6.2-2 Data status that can be referenced by user applications

BOOL val- Status Meaning
ue
TRUE GOOD Status where no error has occurred in input/output modules. In the case of an in-
put variable, this means the data value is from the field.
FALSE BAD This indicates that a normal data value cannot be obtained from or a value cannot
be set to the I/O module due to failure of the module. In the case of an input varia-
ble, the data stored is the input value at error occurrence that is specified in an I/O
parameter.

n I/O variable condition and data value/data status

l Timing at which data status is created
The data status of the I/O variables is created based on the I/O status information. If the I/O
variables are not locked, the data statuses of the physical data and the logical data are the
same. If the I/O variables are locked, only the data status of the physical data is updated.
In the case of an output variable, the update timing and transmission direction are different for
the data value and the data status. Moreover, in the Output Disable status, the data values of
the physical data and the logical data are different but the data status matches.
Lock/unlock status of I/O variables, Output Enable/Output Disable status and data value/data
status in each status can be summarized as shown in the following tables.

l Data value and data status of input variables

Table A6.2-3 Data value and data status of input variables

Status Physical data Logical data
Unlocked status The data value takes the input value from The data value matches with that of the
(at normal in- an input module. The data status is GOOD. physical data. The data status matches with
put) that of the physical data.
Unlocked status The data value takes the input value from The data value becomes the input value at
(at erroneous an input module. The previous value is error occurrence that is defined in an I/O
input) maintained if there is no response. The data parameter. The data status matches with
status is BAD. that of the physical data.
Locked status Same as for unlocked status for both the The data value and data status immediately
data value and data status before locking are retained. They can be
changed from the SCS Manager.

l Data value and data status of output variables

Table A6.2-4 Data value and data status of output variables

Status Physical data Logical data
Unlocked Output The data value matches with that of the The data value is set to the result of
Status Enabled logical data. The status of the output mod- the application logic processing. The
ule is reflected in the data status at each data status matches with that of the
interval. physical data.
Output The data value becomes the fail-safe val-
Disabled ue that is defined in an I/O parameter. The
status of the output module is reflected in
the data status at each interval.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.2 I/O variable > A6-6
Table A6.2-4 Data value and data status of output variables (Table continued)
Status Physical data Logical data
Locked sta- Output The data retains the value immediately The data value is set to the result of
tus Enabled before locking and the value can be the application logic processing. The
changed from the SCS Manager. The sta- data status is retained immediately
tus of the output module is reflected in the before locking and the status can be
data status at each interval. changed from the SCS Manager.
Output The data value retains the previous value.
Disabled However, the fail-safe value is set by the
CPU when the output is disabled. (The
value can be changed from the SCS Man-
ager.) The status of the output module is
reflected in the data status at each inter-
val.

l Logical data and physical data of analog output

The relationship of logical data and physical data of analog output is shown below. Analog
output processing consists of discrete output operation, plus limiter processing and tight-shut/
full-open processing.

LD: Logical data

Locked/output
PD: Physical data enabled
PD.
Output disabled status
or locked

Value GOOD I/O

from Limiter Tight-shut/full-open Output
LD.v PD.v image module
application processing processing area
logic Unlocked/
output BAD
enabled

Output value
at fault

Forcing

Figure A6.2-2 Flow of logical data and physical data of analog output

The following processing is performed until the logical data is output as physical data from the
analog output module.
• Output is limited to a range of -17.19 to 118.75 [%].
• If tight-shut/full-open is specified, the tight-shut value is set when the logical data is 0.0 or
below, or the full-open value is set when the data is 100.0 or above.
• If output is disabled or locked, the last physical data value is retained.
• If an error occurs, the output value at fault is set or the last value is retained in accord-
ance with the output processing at fault.

n Data status at AIO/DIO module dual-redundant configuration

In the case of dual-redundant input modules, the data status of each input variable is deter-
mined based on the I/O status information of the active input module. The same rule applies
to dual-redundant output modules as well.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A6.3 High current output function > A6-7

A6.3 High current output function

This high current output function combines consecutive DO channels of an N-IO I/O module,
and supplies a large current to the connected devices. This function is used to connect to de-
vices such as beacon and sounder.
You need to determine the number of channels to be used according to the current that is re-
quired by a connected device.
• Connecting to a device that requires a current of 1.3A: Use two consecutive channels
• Connecting to a device that requires a current of 2.0A: Use three consecutive channels
Combined channels can be categorized as primary channel and non-primary channel.
• Primary channel: The channel to which I/O variable can be assigned among the com-
bined channels. This is the lowest number channel among the selected channels.
• Non-primary channel: The channel to which I/O variable cannot be assigned among the
combined channels.
If an error occurs in the combined channels, it is notified as error in primary channels.
For example, if the channels are set to be combined on engineering, and if the combined
channels are insufficient or their numbers are misplaced, it is notified as error due to open cir-
cuit in the primary channel. In this case, the output that is set in engineering becomes fail-safe
value for both primary and non-primary channels in the same manner as in the output channel
error. In addition, the primary channel will be in output disable status.
You need to specify the primary channel when you execute output enable operation and forc-
ing function for the combined channels. A non-primary channel is handled in the same way as
a channel that is not being used.
You can check the position of the faulty channel in the IOM Report.

IMPORTANT
The high current output function cannot be used when using an intrinsically safe barrier.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7. Performance and scan period in the SCS > A7-1

A7. Performance and scan period in the

SCS
There are two types of scan periods of SCS, the scan period of the application logic execution
function and the scan period of the external communication function. The scan period of the
application logic execution function can be changed online.
SCS has the automatic extension function for the scan period of the application logic execu-
tion function. This function automatically extends the scan period of the application logic exe-
cution function when the load on SCS becomes high. Use the SCS Constants Builder to spec-
ify whether or not to use this function.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.1 Definition of SCS scan period > A7-2

A7.1 Definition of SCS scan period

This section describes the definition of the SCS Scan period and how to define it.

n Scan periods in SCS

The periodic processing for SCS falls into two types: Application Logic Execution Function
and External Communication Function. They are executed at their respective scan periods.

Application Logic
Execution Function

A scan period for Application Logic Execution Function

External Communication
Function

A scan period for External Communication Function

Idle time

Figure A7.1-1 Scan periods of SCS

The Application Logic Execution Function is the function having a top priority among SCS
functions.
The External Communication Function is executed in a part where the Application Logic Exe-
cution Function is not executed in the CPU processing period. If the External Communication
Function finishes its processing before a scan period ends, the remaining time becomes the
idle time on CPU.

l Processing of the Application logic execution function

The Application Logic Execution Function is executed in the order presented as follows.

1 2 3 4 5 1 2 3 4 5

Scan period

Figure A7.1-2 Processing of the Application logic execution function

Table A7.1-1 Processing of the Application logic execution function

Order Processing Name Description
1 Input AI/DI data, Self-diagnosis Collects AI/DI data from input modules, and generates data val-
ues and data status. Stores the generated data in the input varia-
bles. Generates status of output modules and the self-diagnos-
tics are also executed at the same time.
2 Receive data from other SCS Receives the data from other SCSs, and stores them to the vari-
ables. (Applicable to inter-SCS safety communication and SCS
link transmission)
3 Execute Application Logic Executes application logic in FBD and LD.
4 Transmit Data to other SCS Transmits data to other SCSs. (Applicable to inter-SCS safety
communication and SCS link transmission)
5 Output AO/DO data, Self-diagno- Collects the data from output variables, and writes the data to
sis the output modules. The self-diagnostic processing is executed
at this timing.

The processing time of the Application Logic Execution Function may be prolonged by about
20% at maximum because of the increase in the CPU load caused by communication for tag
data access or some other processing.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.1 Definition of SCS scan period > A7-3

l Processing of the external communication function

The External communication function is a general name for functions of communicating infor-
mation of SCS with external systems. CENTUM Integration Function and Modbus Slave Com-
munication Function are included in it.

n Specification of scan period of the application logic execution

function
The scan period of the application logic execution function is specified on the Link Architec-
ture View of SCS Manager. From [Edit] > [Properties], Call the Resource Properties dialog
box, enable the "Trigger cycles" check box in the "Settings" tab, and specify the value in "Cy-
cle timing."
• The scan period can be specified in the range from 50 ms to 1000 ms in increments of
10 ms.
• The specified scan period can be changed online. (*1)
*1: Supported in the SCS of SCS system program R2.03 or later.

SEE
ALSO For more information about Link Architecture View, refer to:
"Run-time Settings" in "Editing resource Properties" in "Link Architecture view" in "Workbench" in the
Workbench User's Guide

n Specification of scan period of the external communication function

The scan period of the external communication function is specified in the SCS Constants
Builder. Specify the value in [Scan Period for External System] in the [Communication] tab.
• Either 1 second or 2 seconds can be specified.
• The default value is 1 second.
• Offline download is required to change the specified scan period.

n Watching scan run time

While the SCS system program runs successfully, the Watch Dog Timer (WDT) is periodically
reset. The WDT is for self-diagnosing the cyclic operations.

n Confirmation of CPU processing time and consideration of idle time

l CPU processing time
The actual processing time of the Application Logic Execution Function can be checked on
the SCS State Management window of SENG or Status Display View of HIS. It can also be
referred with the application logic by using the SYS_SCAN system function block.
Application execution time is the period of time required for processing the application logic
within a scan period. Instantaneous value (%) in each scan calculated by 10 ms resolution is
displayed.
CPU idle time is the period of time when the CPU has no task including the External Commu-
nication Function. Idle time per 60 seconds is displayed.
These displayed times tend to fluctuate depending on the communication load since the CPU
of SCS processes the communication with SENG and communication requests from DCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.1 Definition of SCS scan period > A7-4

l Consideration of CPU idle time

You must confirm the above-mentioned Application Logic Execution time and CPU idle time
when creating, adding, or changing an application logic for the SCS. The appropriate CPU
idle time is necessary to ensure the external communication, the online change, etc.
You can take the following measures when the CPU idle time is insufficient.
• Reduce application logic.
• Lengthen the scan period.
• Divide application logic into two SCS.

l Influence on application logics according to the increase of

communication load
Processes on communication with SENG (online monitoring, I/O lock window operation, etc.)
and communication request from DCS are done by the CPU of SCS so that they consume its
idle time. Upon the increase of the frequency of such communication requests, SCS restricts
the communication requests to accept to a certain amount. Thus those communications may
be delayed.
Therefore when there is no communication, securing the idle time of the CPU to be more than
30 % is recommended to keep the influence on the communication to minimum upon the tem-
porary increase of the communication load.

l Influence when the execution load of the application logic is large

Even if the time taken for the processing of application logic execution occupies large portion
of the SCS scan period and therefore CPU idle time is steadily less than 30%, the application
logic can still be executed when there are no communications with SENG (online monitoring,
I/O lock window operation, etc.) nor with DCS. However, if the communication load increases
this situation, the following phenomenon will be observed.
• When the idle time is not sufficient
• Updating the data displayed on HIS window, communication with SENG and FCS
may be delayed.
• Process alarms and annunciator alarm may be delayed.
• Modbus slave communication may become an error.
As the idle time lessens, the above phenomenon will become more obvious.
• When there is hardly any idle time and the application logic execution time is equal to
scan period
• Updating the data displayed on HIS window, communication with SENG and FCS
may be stopped.
• Sending process alarms and annunciator messages may be stopped.
• Modbus slave communication may become an error.
• When there is no idle time and the application logic execution time is steadily longer than
scan period
• Inter-SCS safety communication will not be performed properly and timeout errors
may be detected on the receiving side. Such phenomenon does not occur in SCS
link transmission safety communication because the communication mechanism is
different.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.2 Automatic extension function for scan period of the application logic execution function >
A7-5

A7.2 Automatic extension function for scan

period of the application logic execution
function
In such a case as when the SCS has to perform very large amount of communication to ac-
cess tag data, the processing time of the Application Logic Execution Function may be pro-
longed. If the amount of application is large and there is insufficient idle time before the next
scan period starts, the SCS does not have sufficient time for the processing of communica-
tion on the control bus and for the External Communication Function that is done during the
intervals between executions of the Application Logic Execution Function.
In such conditions, some functions such as the CENTUM integration function are affected. If
high-load conditions continue steadily, inter-SCS safety communication may also be affec-
ted.
To avoid such adverse effects, you need to design the application logic so as to ensure the
recommended CPU idle time given in the Engineering Guide.
If you anticipate that the SCS cannot maintain sufficient CPU idle time because of underesti-
mating the amount of application logic at initial engineering or the modification of the SCS
project, you can specify the use of the automatic scan period extension function in order to
avoid the adverse effects (*1)
*1: Supported in the SCS of SCS system program R2.03 or later.

IMPORTANT
The purpose of this function is to temporarily avoid occurrences of erroneous conditions in
SCS. SCS cannot maintain the assumed process safety time if the automatic scan period ex-
tension function is executed. Thus, take permanent measures such as reducing the amount of
application logic in order to lower the CPU load on the SCS.
It is possible to check if the scan period has been automatically extended on the SENG or
Status Display view of HIS as well as via diagnostic information messages. It is also possible
to create application logic for confirming the state of scan period extension.

n Automatic scan period extension function

The purpose of this function is to extend the scan period of the application logic automatically
in order to prevent communication functions, such as inter-SCS safety communication, from
stopping when the execution of application logic takes longer than the scan period defined in
the SENG as a result of online changes of application software that contains engineering mis-
takes for example. This function can be enabled or disabled on the SCS Constants Builder. It
is disabled by default.

IMPORTANT
If a demand occurs while scan period is extended, it can affect safety because, for example,
the reaction time may become longer than the process safety time. You need to judge careful-
ly whether or not to enable the automatic scan period extension, taking the process safety
time into consideration. If the scan period is extended while the automatic scan period exten-
sion is enabled, promptly take countermeasures such as reducing the amount of application
logic by online change.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.2 Automatic extension function for scan period of the application logic execution function >
A7-6

l Overview of automatic extension of scan period

If the processing of the Application logic Execution Function is prolonged and almost occupies
the whole scan period of the Application logic Execution Function defined in SCS Manager,
the SCS cannot perform the processing for the communication on the control bus and for the
External Communication Function that is done during the intervals between executions of the
Application Logic Execution Function.
Processing of Application logic Processing for control bus communication and
Execution Function External Communication Function

At normal condition

Scan period of Application logic

Execution Function
Processing time for control bus communication and
External Communication Function is not enough.
At high-load
(Before extension)

Scan period of Application logic

Execution Function

Figure A7.2-1 Example of the case when the scan period is automatically extended

The automatic scan period extension function automatically extends the scan period of the
Application logic Execution Function when high-load conditions occur and ensures sufficient
time for the processing of communication on the control bus and for the External Communica-
tion Function that is done during the intervals between executions of the application logic.
Scan period of Application logic Execution Function is extended
to ensure sufficient processing time for control bus processing
and External Communication Function.

At high-load
(After extension)

Scan period of Application logic

Execution Function
Extension

Figure A7.2-2 State in which the scan period is automatically extended

By using the automatic scan period extension function, the time for the communication pro-
cessing related to the following features are ensured.
• Inter-SCS safety communication
• Integration with CENTUM
• Communication with SENG
• Diagnostic information message, process alarm notification

l Conditions of starting scan period extension

When both of the following conditions are satisfied in a state at once, it is defined as a high
load status.
• The total time to execute the application logic execution function and to process inter-
SCS safety communications exceeds 80% of the original scan period of the application
logic execution function.
• The CPU idle time becomes 0.
In this case, you can estimate the processing time for inter-SCS safety communication with
the following formula:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.2 Automatic extension function for scan period of the application logic execution function >
A7-7
Processing time for inter-SCS safety communication = (number of consumer groups +
number of producer groups) × T [ms]

The values of T are as shown in the following table according to the configuration of the CPU
module.

Table A7.2-1 Values of T

CPU module T
SCP401/SCP451 (Dual-redundant) 5.0
SCP401/SCP451 (Single) 2.5
SCP461 (Dual-redundant) 3.0
SCP461 (Single) 1.5

If this high load status continues for 1 second or longer, the scan period of the application log-
ic execution function is automatically extended.
The new scan time is obtained by adding 20% of the original scan period of the application
logic execution function to the actual measurement of the application execution time at that
time.

l Influence until activation of scan period extension

The following situations may occur before the automatic scan period extension period is acti-
vated after the SCS is placed under high load status.
• Stopping of CENTUM integration data update
• Delay of diagnostic information message notification
• Stopping of forcing data update
• Stopping of status display in the SCS State Management window

l Upper limit of scan period extension

The upper limit of scan period extension is 200% of the original scan period of the application
logic execution function. Note that the extended scan period will never exceed the upper limit
value of 1 second.

l Cancellation of scan period extension

If both high load conditions explained in item "Conditions of Starting Scan Period Extension"
are removed, the scan period becomes shorter by each scan in decrements of 20% of the
original scan period of the application logic execution function. Note that the scan period will
never become shorter than the scan period of the application logic execution function defined
in SCS Manager.

n Notification of execution/cancellation of automatic scan period

extension
• If the automatic scan period extension function is activated on the SCS, it is notified via
the diagnostic information message (No. 4143). The cancellation of extension is notified
via the diagnostic information message of automatic scan period extension cancellation
(No. 4144).

• If automatic scan period extension is continuously activated for a certain period of time
or longer, the diagnostic information message indicating the start of the automatic scan
period extension function is notified to give warning again. The re-warning interval is 10
minutes by default.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.2 Automatic extension function for scan period of the application logic execution function >
A7-8
The interval of re-warning can be changed using the SYS_SCANEXT system function
block.
• The system function block (SYS_SCANEXT) can be used to determine whether the au-
tomatic scan period extension function is being executed via application logic. (*1)
• If the scan period of the application logic execution function is changed via online
change download while the scan period is being automatically extended, the scan period
extension status is cancelled after the completion of the online change download and
the diagnostic information message on cancellation of scan period automatic extension
is notified. However, if the high CPU load continues even after the scan period is
changed and if the conditions for automatic scan period extension are met, the scan pe-
riod is extended automatically.
• The SCS State Management window of SENG and the Status Display view of HIS (*2)
display both the scan period of the application logic execution function defined in SCS
Manager and the actual scan period of the application logic execution function of SCS.
*1: The SYS_SCANEXT system function block can be used in new SCS databases created by SENG of R2.03.00 or later.
*2: Supported in CENTUM VP R4.02 or later.

SEE
ALSO For more information about SYS_SCANEXT, refer to:
12.26, “SYS_SCANEXT (scan period extension indicator)” in POU Reference Manual (IM
32P03B20-01EN)
For more information about Diagnostic information messages, refer to:
Message Number 4143 in 2.1, “System Alarms (Message Numbers 4101 through 4220)” in Messages
Reference Manual (IM 32P02B10-01EN)

n Precautions when using Automatic scan period extension function

The fact that the SCS is running with an automatically extended scan period is important safe-
ty information. In projects where no HIS is connected, it is necessary to use the SYS_SCA-
NEXT function block to notify the user that the SCS is running with an automatically extended
scan period.

n Influence of automatic extension of scan period

Automatic extension of the scan period has the following influence.

l Influence on process safety time

Since the reaction time is determined based on the scan period of the application logic execu-
tion function, the time also becomes longer accordingly if the scan period is extended.
SEE
ALSO For more information about precautions upon engineering related to automatic extension of scan period, refer
to:
A7., “Performance and scan period in the SCS” on page A7-1

l Influence on test functions

The automatic scan period extension function does not operate in SCS simulation tests and
logic simulation tests.

l Influence on Function Blocks

• SYS_SCAN function block
The current scan period of the application logic execution function of SCS is output to the
output parameter SCAN of the SYS_SCAN function Block.
• Function blocks handling time

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.2 Automatic extension function for scan period of the application logic execution function >
A7-9
There is no influence of changes in scan period on the operations of function blocks han-
dling time. Those function blocks operate according to the actual time even if the scan
period is changed.
• Function blocks handling execution count
In the case of function blocks whose output is determined by the number of calls, the
number of outputs within the unit time decreases if the scan period is extended.
Targets: CTU, CTD, CTUD, FILTER, FILTER_S

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.3 Locking of internal variables and performance in SCSP3/SCSP2> A7-10

A7.3 Locking of internal variables and

performance in SCSP3/SCSP2
It is important to note that the application run time becomes longer (i.e., the CPU load increa-
ses) if any internal variable is locked in SCSP3/SCSP2. You should lock internal variables for
engineering and maintenance purposes only.
You must investigate whether there is a need to use the automatic extension function for scan
period of the application logic execution function as a countermeasure to prevent high CPU
load.
SEE
ALSO For more information about automatic extension of the scan period of the application logic execution function,
refer to:
A7.2, “Automatic extension function for scan period of the application logic execution function” on page
A7-5

n Internal variables that affect performance

Internal variables whose lock status affects the performance are those defined in the Diction-
ary. I/O variables and the variables that are locked in the Communication I/O Lock window,
SCS Link Transmission Lock window and Inter-SCS Communication Lock window do not af-
fect the performance.

n Locking of internal variables

• In SCSP3/SCSP2, you can lock internal variables only when [Extend Scan Period Auto-
matically] is set to [Yes], and [Locking of Internal Variables] is set to [Enable] in the SCS
Constants Builder. If you need to lock internal variables, you need to set [Extend Scan
Period Automatically] to [Yes], change [Locking of Internal Variables] to [Enable], and
download to the SCS. Once the required lock operations are complete, you need to set
these specifications back to the original settings and download to the SCS. Note that the
locking of internal variables can be canceled regardless of these specifications.
• When the SCS security level is at Level 0, internal variables can be locked only if [Extend
Scan Period Automatically] is set to [Yes], and [Locking of Internal Variables] is set to [En-
able]. However, at Level 0, the application run time may get extended not only when the
internal variables are locked, but also when the break point function of the application de-
bugging function is used. If you use the break point function once, the application execu-
tion time does not return to the original length even if you cancel all break points.
• The locked internal variables can be checked with the diagnostic information messages
of SENG or system alarm messages of HIS.

n CPU load due to locking of internal variables

• If you lock internal variables when the CPU idle time is small, the execution time of the
CPU may exceed the specified scan period. In such cases, the automatic scan period ex-
tension function may be activated in order to extend the scan period so that external com-
munication processing and similar are not affected.
• Even if you lock one internal variable, the CPU load increases by 20% to 30% compared
to the status where no internal variables are locked.(The rate of CPU load increase de-
pends on the application)
• If you unlock all internal variables, the application execution time automatically returns to
the original value before the internal variables are locked.
• It is recommended to set [Locking of internal variable] to [Disable] on the SCS Constants
Builder while the SCS is running in normal operation. This is because there is a risk of

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A7.3 Locking of internal variables and performance in SCSP3/SCSP2> A7-11
locking internal variables without considering the increase of CPU load if [Locking of In-
ternal Variable] is set to [Enable].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8. RAS (Reliability, Availability, Serviceability) functions of SCS > A8-1

A8. RAS (Reliability, Availability,

Serviceability) functions of SCS
This section explains functions related to reliability, availability and serviceability of the SCS
(hereinafter referred to as RAS in this manual). Moreover, it is a function that implements
safety. The function includes the ability to shift to a safe state in a fast and reliable manner
when an error occurs in the plant or system.
The RAS functions of the SCS are as follows:
• Operating mode
• Security level
• Diagnostic management function, diagnostic information messages
• Operation during start, and operation during error
• Dual redundancy
SEE
ALSO For more information about SCS status monitoring functions, refer to:
H., “Monitoring the SCS status” on page H-1
For more information about Operations and recovery procedures during the SCS error occurrence, refer to:
G2., “Operations and recovery procedures during the SCS error occurrence” on page G2-1

n Positioning of RAS function

RAS stands for Reliability, Availability and Serviceability, and is an important index when eval-
uating the system performance. Reliability means robustness against error occurrence, avail-
ability means shortness of downtime and serviceability means ease of repair at failure.

l Functional relation of software

The RAS function diagnoses whether hardware and software are running normally and han-
dles maintenance of them if any errors are detected. Since this function is able to shut the
system down and change the SCS status as required, it is one of the most essential SCS
functions.

l Relationship with other hardware

The RAS function collects hardware error information concerning the I/O modules and other
components in the station. The RAS function organizes hardware error information and exe-
cutes pre-defined safety operations accordingly, such as shutting down. Error information is
sent to the SENG and HIS as diagnostic information messages. The SCS saves diagnostic
information generated internally. And the information can be referenced from SENG. You can
delete saved diagnostic information messages from SENG.
The figure below shows how the RAS function of the SCS is positioned.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8. RAS (Reliability, Availability, Serviceability) functions of SCS > A8-2

SENG HIS

V net

Diagnosis
System Alarms
Information

Download,
Changing
SCS FCS
Actions

RAS
function

Error I/O module

Information shutdown

Input/output
modules

Figure A8-1 Positioning of RAS function

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.1 SCS operating mode > A8-3

A8.1 SCS operating mode

The operating mode indicates the operation status of an SCS. Operations of the functions that
are implemented by the system program of the SCS are determined by the operating mode.
The operating mode is outlined as follows:
• The operating mode indicates the overall operating status of SCS, not the status of indi-
vidual output modules.
• The operating mode indicates the status of a single SCS, regardless of whether the CPU
configuration of the SCS is single or dual-redundant.
• For an SCS with dual-redundant CPU, the operating mode remains the same before and
after a control right switchover of the CPU.
There are five SCS operating modes: Stop mode, Loading mode, Initial mode, Waiting mode,
and Running mode
The following figure shows the transitions between operating modes. Note that it is possible to
shift to the Stop mode from all other modes, but the arrows indicating these shifts are omitted
for the sake of clarity.

Loading
Mode

The request of Finish of

Offline Download Offline Download
start from notified from
SCS Manager SCS Manager

Can be transferred
from all other modes
SCS stopped

Figure A8.1-1 Transitions between operating modes

n Stop mode (stopped status)

This is the initial state of the SCS.

n Loading mode (during offline download)

In this mode, program and database are being downloaded from the SCS Manager to the
SCS.

n Initial mode (initializing status)

In this mode, the SCS is initializing databases, processing the diagnostic at startup, and start-
ing the I/O modules as follows:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.1 SCS operating mode > A8-4
• Input modules
If started successfully, input values are set to applicable input variables. If the startup of
any module has failed, an error is recognized for the module.
• Output modules
The outputs of all channels remain disabled after the startup is completed, so that the
output values from the application logic will not be sent to the field immediately.
• Subsystem communication modules
Receives only the input from subsystems while having an output that is invalid.
• Fire and gas communication modules
If the startup process is successfully completed, fire and gas communication modules re-
ceive only the input from subsystems. If the startup process ends in an error, the SCS
handles the fire and gas communication modules as erroneous.

n Waiting mode (waiting for output enable request)

Application logic is periodically executed on each scan period. However, the output channel
will not output the application logic value if the status is set to "Output Disable". The waiting
mode status can be checked in the SCS State Management window and the LED display of
the CPU module.
When "Output enable operation" is performed, the outputs on the normal channels of output
modules are enabled. If you execute the "Output enable operation" just after starting up the
SCS, the SCS also enables the output of inter-SCS safety communication, SCS link transmis-
sion and subsystem communication.
TIP • Failure on the output channel should be removed, then perform "Output enable operation".
• Even when the channel is set to "Output Disabled", if the physical data is rewritten using the forcing
function, the output value from the output channel changes.

SEE
ALSO For more information about the output enable operation, refer to:
C8., “Output enable operation” on page C8-1
For more information about relationship between forcing function and I/O variable data value/data status, re-
fer to:
“n I/O variable condition and data value/data status” on page A6-5

n Running mode (controlling status)

This mode indicates that the SCS is running normally. All output channels of output modules
are outputting the output values from the application logic. The Running mode status can be
checked with the SCS State Management Window and LED display of the CPU module.

l Output status monitoring

All output channels of output modules are monitored. If any of the channels becomes Output
Disable status due to a failure in the corresponding module or in the output channel itself, or
after adding new channels during online modification, the SCS will change its operating mode
to the Waiting mode. The operating mode changes to the Running mode when the cause of
the channel failure is removed, the output enable operation is completed and all output chan-
nels are placed in the Output Enable status.

n Checking of operation mode

The operating mode of SCS can be checked with the following methods.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.1 SCS operating mode > A8-5
• It is possible to check that the operating mode is either the Waiting or Running mode with
the SCS State Management window of the SCS Maintenance Support Tool, the SCS Sta-
tus Display view of HIS and the LED display of a CPU module.
• If the operating mode is either the Waiting or Running mode, the operating mode can be
referenced from the application logic as well.

n Influence on operating mode

Engineering and occurrence of errors can affect the operating mode as follows.
• The operating mode is not affected even if a subsystem communication error, safety sub-
system communication error, or communication module error occurs.
• Occurrence of errors in SCS link transmission has no influence on the operating mode.
• If output modules/channels are added via online change download, the added modules/
channels are started from the Output Disable status. If the operation mode was the Run-
ning mode before online changes, the mode changes to the Waiting mode. Perform the
output enable operation.
• If channels in the Output Disable status or output modules including such channels are
deleted via online changes and there are no longer any channels in the Output Disable
status in SCS, the operating mode shifts from the Waiting mode to the Running mode.
• If a single output module is changed to dual redundant configuration by online change
download, IOM download is executed in order to initialize the modules. The outputs of the
target modules become disabled after downloading. Since some channels are in the Out-
put Disable status, the operating mode of SCS shifts to the Waiting mode. Perform the
output enable operation after the output modules recover to normal.
• It is possible to perform the output enable operation regardless of the status of communi-
cation modules.
• It is possible to perform the output enable operation even if the status of communication
with sub-systems is BAD. In this case, only outputs that are ready to communicate will
start.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-6

A8.2 Security level of SCS

The security level of SCS indicates the level of protection against erroneous writing to the
memory in SCS from the connected stations or devices. An overview of SCS security level is
as follows:
• One SCS has one security level.
• The security level can be confirmed from LED on the CPU module and the SCS State
Management window of SCS Maintenance Support Tool or Status Display View of HIS.
• SCS limits changes made from the outside according to security level.
• Security level can be referred to by applicable logic.
• Security level can be changed by an authorized user with the password using the SCS
Manager.
• Using the system function block (SYS_SEC_CTL) makes it possible to control whether or
not to allow security level change operations from an SENG with an external hardware
switch or similar.
• Security level can be changed under the following conditions:
• The SCS is either in the Waiting or Running mode,
AND
• The SYS_SEC_CTL is set to allow security level changes or is not used.
The following figure illustrates the transition of states of the security level.
Offline Download or SCS Restart or Master database offline download

Online Levels Offline Level

[ SYS_SEC_CTL
check (*1) ]
Level 2 Level 1 Level 0
[ Level 0
[ Level 1 password check
password check & SYS_SEC_CTL
& SYS_SEC_CTL check ] check ]

*1: It is allowed to reset the security level from Level 1 to Level 2 via the RST input in the SYS_SECURE block,
regardless of the security level change enable/disable status of SYS_SEC_CTL.

Figure A8.2-1 Transition of security level status

n Definition of each security level

There are two classifications of levels; online level and offline level. The Online level is used
when SCS is in normal operation. The Offline level is used when SCS is not in normal opera-
tion.

l Online level
The Online Level is a security level to be used when normal operation is performed in SCS.
The SCS itself provides security of the Online Level by controlling access to the memory from
the outside.
The Online Level is separated into two levels according to limits of functions which can be
used.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-7
Table A8.2-1 Online level
Level Description
Level 2 The highest security level. SCS is usually operated at this security level.
Level 1 A temporary security level used by engineers or authorized users for maintenance of
equipment or changing applications online

l Offline level
The Offline Level is a security level to be used when a regular operation is not performed in
SCS. This is displayed as "Level 0" on the LED of SCS or the SCS State Management win-
dow of SENG. In the Offline Level, SCS does not limit access to SCS from the outside. How-
ever, information which was used at test may be stored in SCS databases depending on op-
erations performed by those tools.

IMPORTANT
To restore an SCS to Online Level from Offline Level, restart the SCS or do offline download.
This ensures that the system returns to the security level for normal operation.

n Relationship of operational items with SCS security levels

The following are the list of operational items in each security level. It is also possible to write
information which is not related to any reference or safety function of the SCS, at any level.

Table A8.2-2 SCS related operations and the required security levels
Security level (*1) Operation
SCS related writing operation
Level 2 Level 1 Level 0 side
Override from HIS OK OK OK HIS
Operation for password block from HIS OK OK OK HIS
Operation for manual operation block OK OK OK HIS
Executing the reset function of a function block for fire
OK OK OK HIS
and gas devices from HIS
Confirmation of process alarm OK OK OK HIS
Setting operation mark on mapping block/mapping ele-
OK OK OK HIS
ment
Confirming and deleting the diagnostic information OK OK OK SENG
Setting Vnet time OK OK OK HIS/SENG
Change of security level OK OK ERROR SENG
IOM Download (*2) OK OK OK SENG
Resetting of trip signal file OK OK OK SENG
Change of passwords for security level OK OK OK SENG
Locking/unlocking of variables ERROR OK OK SENG
On-demand communication for device management OK OK OK PRM
Change of variable value with forcing function ERROR OK OK SENG
Online change of applications ERROR OK OK SENG
I/O lock function ERROR OK OK SENG
Communication I/O lock function ERROR OK OK SENG
Switching control right for redundant AIO/DIO modules ERROR OK OK SENG
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-8
Table A8.2-2 SCS related operations and the required security levels (Table continued)
Security level (*1) Operation
SCS related writing operation
Level 2 Level 1 Level 0 side
Enabling NIU maintenance port (*3) ERROR OK OK SENG
Offline download ERROR ERROR OK SENG
Application debugging function ERROR ERROR OK SENG
Restarting the SCS from SENG ERROR ERROR OK SENG
Output enable operation OK OK OK SENG
Save/download operation marks OK OK OK SENG
Start output module operation OK OK OK SENG
Locking and unlocking variables, changing variable val-
ERROR ERROR OK iDefine
ues, and locking I/O by using iDefine
*1: OK: Operation allowed
ERROR: Operation failed
*2: You can download only on failed I/O modules.
*3: Can run only SCSP3 which supports NIU maintenance.

l Security level at the start of SCS

The security level is Level 2 when SCS starts normally.

n Operation of security level

l Change operation of security level
To change the security level from Level 2 to Level 1 or to Level 0 or from Level 1 to Level 0,
entering a password from SENG is required. When the security level is changed, SCS notifies
the user of the change of the security level with the Diagnostic Information Message.
You can change the security level from Level 1 to Level 2 without a password. To change the
security level from Level 0 to Level 2, you must restart the SCS.

l Protection of security level by hardware switch

It is possible to use SYS_SEC_CTL to control whether or not to allow changing the security
level from a SENG using an external hardware switch or similar.
• When the SYS_SEC_CTL is used, it is not allowed to change security level by password
entry from SENG if the FIX parameter input of the SYS_SEC_CTL is set to TRUE. To
change the security level of the SCS, the user needs to operate an external key switch or
similar and change to the status where security level change operations are allowed (set
the FIX parameter of the SYS_SEC_CTL to FALSE), and enter the appropriate password
from a SENG.
• The SYS_SEC_CTL also controls whether it is allowed to reset the security level from
Level 1 to Level 2 (even though password entry is not required).
• If the security change enable/disable status is changed by the SYS_SEC_CTL, the status
is notified to user via a diagnostic information message.
• Resetting of the security level to Level 2 via RST input in the SYS_SECURE block and
resetting of the security level to Level 2 via the CPU's restart switch are not affected by
the security change enable/disable status of the SYS_SEC_CTL.

IMPORTANT
The situation when the FIX parameter of the SYS_SEC_CTL is constantly set to TRUE by er-
roneous applications should be surely avoided.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-9

l Reset function for security level

When a fault occurs in SENG or the communication line while the security level (Level 1) is
being changed, it is required to reset the security level (back to Level 2) as soon as possible
to ensure security of SCS. The SYS_SECURE block in the application logic can reset the se-
curity level with RST input.
• It is possible to reset from Level 1 in the SYS_SECURE block, not from Level 0.
• Connecting a discrete input signal to RST makes it possible to reset the security level
with a key switch or a button. When this is not necessary, set FALSE to RST.
• The SYS_SECURE block detects the change of RST input from FALSE to TRUE and re-
sets the security level.

l Monitoring function of security level

When the security level of an SCS is in Level 1, the SYS_SECURE block monitors duration of
the status. If the status of Level 1 continues longer than the time specified by the CHKT input
in the SYS_SECURE block, a diagnostic information message occurs. After notifying the di-
agnostic information message, the duration is monitored again. The status of Level 0 is not
monitored.
The following figure shows an example of application using the SYS_SECURE.

SCS

SYS_SECURE
NO
input
PB DI0001 RST LVL

External reset PB t#600s CHKT TUP

Figure A8.2-2 Example of application using security block

n Passwords for changing security level

l Specification for passwords
• Passwords for the security level are controlled in SCS.
• A password for the security level is set for each security level.
It is necessary to set the password to change to Level 1 and Level 0 respectively. A
password is not necessary to change to Level 2.
• A password is 16 alphanumeric characters (*1)at maximum, which is upper/lower case
sensitive.
• Passwords are maintained during a power cut and restart of SCS.
• Passwords are deleted by SCS offline download.
*1: Including a space character and
! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ ¥ ] ^ _ ` { | } ~

l Setting and changing passwords

• Change passwords on the SCS Manager in SENG.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-10
• Passwords can be changed when SCS is in operation.
• To change a password, user must enter the old password before it is changed.
• When a password has been changed, SCS notifies its change with the Diagnostic Infor-
mation Message.
SEE
ALSO For more information about operations for changing the SCS security level and setting the password, refer to:
B3., “Security of SCS” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

n Precautions when changing SCS security level

• Set different passwords for each SCS.
• Set a different password for each security level.
• When the security Level of SCS has been changed, confirm that the change is made to
an appropriate level with the SCS State Management Window.
• Do not set the security levels to Level 1 or Level 0 for several SCSs at the same time
when SCSs are in operation.
• If setting a password to SCS during APC (All Program Copy), APC restarts. It takes about
10 minutes from setting a password, after offline download, to restarting the operation of
the dual-redundant system.
Do not change passwords during APC except the changes required for after offline down-
load.

IMPORTANT
• When a password is not set, entering characters in the Password Entry Dialog causes an
error. Considering safety as the safety system, always set passwords to use.
• Power failure or restart does not change or delete passwords.
• Passwords are deleted when offline download is performed. As there is no password after
offline download, set new passwords after performing offline download.
• Passwords cannot be referred to after setting them. User should remember the set pass-
word. Also, Password should be controlled so that unauthorized users do not know it.

n Precautions when using the SYS_SEC_CTL

The SYS_SEC_CTL block can control whether or not to enable the security level change by
password entry from SENG. In general, an application containing the following blocks should
be created.
Level change disable
Toggle switch SYS_SEC_CTL lamp display
DI001.v FIX STS DO001.v

Figure A8.2-3 General application example

Connect the toggle switch signal for controlling the security level change output from a DI
module to the FIX parameter input of the SYS_SEC_CTL block. This makes it possible to
switch the security change permission status via the external toggle switch. By connecting the
output parameter to a lamp or similar, the security level change permission status can be dis-
played on an external device.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.2 Security level of SCS > A8-11
If the external toggle switch is connected to SYS_SEC_CTL, make sure to examine all possi-
ble states of the DI module or channel to which the toggle switch signal is input.
If an error occurs in the DI module or channel, SYS_SEC_CTL controls the security level
change permission status as follows according to the setting of the I/O parameter Input Pro-
cessing at Fault.

Table A8.2-3 Security level change control operations

Input Processing at
Operation at Errors
Fault
Changing security level by password entry via a SENG is disabled until the fault
is corrected. (*1)
1 (TRUE) If a fault occurs in Level 1, it is possible to reset to the same security level by the
SYS_SECURE block (*2) or reset to Level 2 by restarting the SCS. It is, howev-
er, not possible to change to a lower level until the fault is corrected. (*3)(*4)
During a fault, it is possible to change security level by password entry via a
0 (FALSE)
SENG.
The operation performed before the fault occurred resumes. In other words, if an
error occurs in the status where security change is unavailable (FIX is set to
TRUE), the status where security change is not allowed is retained after the error
occurrence. If an error occurs in the status where security change is allowed (FIX
HOLD is set to FALSE), the status where security change is allowed is retained after the
error occurrence.
If an error occurs in the status where security change is unavailable (FIX is set to
TRUE), it is necessary to take the same precautions as when inputting TRUE at
Input Processing at Fault.
*1: Do not lock the input/output variables connected to FIX and change the security level to Level 2. The variables will not be
unlocked even after the causes of errors are removed. (In this case, it is necessary to restart the SCS or reset by
SYS_FORCE.)
*2: Use separate DI modules for the DI module for inputting the reset signal of the SYS_SECURE block and the DI module for
inputting a toggle switch for security control of the SYS_SEC_CTL block.
*3: It is not necessary to lower the security level during recovery operations. If a DI module fails, replace the module and perform
IOM download.
*4: It is necessary to take measures such as incorporating an application in order to avoid situations where the security level
cannot be reset to Level 2 due to DI module errors when the security level is Level 1.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.3 Operations at SCS startup > A8-12

A8.3 Operations at SCS startup

An SCS always performs the initial cold start processing when it starts up. It does not have a
function that allows it to resume the operating mode it was in before stopping. The operating
mode at startup is always the Stop mode.
SEE
ALSO For more information about Operating mode, refer to:
A8.1, “SCS operating mode” on page A8-3

n Types of SCS startup methods

An SCS can start up in one of the following three ways.

l Power recovery start

An SCS starts up in this way when the power supply is resumed after power failure.

l Start after offline download

An SCS starts up in this way when the user performs offline download from the SCS manag-
er.

l Manual restart
An SCS restarts when the restart switch of the CPU module is pressed or the user performs
SCS restart operation from SCS Manager of the SENG.
TIP • After starting SCS, the operation requests from the SENG and Workbench will be ignored until the oper-
ating mode of the SCS changes to Waiting mode. The same error will occur to the communications with
FCS or HIS for the CENTUM integration as well as Modbus slave communication. The operating mode
of the SCS can be checked on the SCS State Management Window or identified through the LED of the
SCS CPU module.
• A diagnostic information message notifying a failure/recovery may generate twice when the SCS is re-
started. This does not present any problem in practical operations or on safety.

n Internal data at SCS startup

Since an SCS always performs initial cold start when it starts up, all operation areas and vari-
able values maintained dynamically by the SCS are initialized. System programs and databa-
ses that were downloaded offline and changes made online are saved in the flash memory
and restored at start up.
Moreover, when the SCS is started, data saved in the memory with battery backup may re-
main without being initialized. This battery backup memory can hold data for approximately
300 hours even if the power supply to the SCS is stopped. If the data is lost, it will be reset to
the initialized status.
The following are examples of data stored in the battery backup memory.
• System log information
• Diagnostic information (200)
• SOE data log information (1000)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.3 Operations at SCS startup > A8-13
Table A8.3-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.

n System alarms for the Inter-SCS safety communications and link

transmission at the SCS startup
During SCS startup, no system alarm is raised for an error in the inter-SCS safety communi-
cations and SCS link transmission. System alarm is sent for the first error after the startup
procedure and the error during the startup procedure turns to normal. System alarms related
to inter-SCS safety communications and SCS link transmission are sent from the receiving
station only.
At SCS startup, make sure that both the inter-SCS safety communications and link transmis-
sion are normal.
Do the following to check the normalcy:
• Check the communication status of the receiving function block (NR status of CONS FB,
STS of LTRCV FB, and STS of LTFCS FB).
• Check the CMER of the system function block, SYS_DIAG.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.4 Diagnostic information management > A8-14

A8.4 Diagnostic information management

The SCS detects hardware and software errors through self-diagnosis. It also notifies and
saves diagnostic information by using the diagnostic management function. This section ex-
plains the diagnostic management function of the SCS.

n Overview of self-diagnosis of SCS and diagnostic management

function
An SCS performs self-diagnosis regularly to detect hardware and software errors. It analyzes
detected errors and system configuration to determine the error level according to the error
occurred and executes error-handling operations according to the error level.
The diagnostic management function saves/manages diagnostic information messages gen-
erated by self-diagnosis and manages the SCS status. Moreover, it notifies the operation sta-
tus of the SCS to the SENG and HIS.

n Functional relation of diagnostic management function

The following figure illustrates the flow of error information detected by the SCS diagnostic
functions. Error information is composed of SCS statuses indicating faulty locations/error cau-
ses and diagnostic information messages used to notify the user about the errors. In the case
of a CENTUM integration structure, the HIS treats diagnostic information messages as sys-
tem alarms.
SENG HIS

SCS Diagnostic
Diagnostic System alarm display
Information Operation
information
SCS Status Display SCS Status Display

Diagnostic
SCS status information
SCS status message
SCS

Diagnostic
information Diagnostic
Error information management function
Status Processings Status
Self-diagnosis

Diagnosis

IOM FAULT

Figure A8.4-1 Functions related to SCS error information and flow of information

n Management of diagnostic information

An SCS manages diagnostic information in the following manner.
• The SCS saves diagnostic information messages it sends in its memory as diagnostic in-
formation. It sends the saved message information in response to requests from SENG
windows that handle diagnostic information.
• The buffer in the SCS that stores diagnostic information message has the capacity limit.
In order to save all diagnostic information messages, it is necessary to collect diagnostic
information messages from the SENG. The SCS can save up to 5000 diagnostic informa-

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.4 Diagnostic information management > A8-15
tion messages. If the SCS buffer becomes full, diagnostic information messages are de-
leted starting from the oldest one.
• In the event of power failure, the SCS saves the latest diagnostic information to a memo-
ry backed up by a battery. It will restore the saved information upon restart.

n Notification of SCS diagnostic information

The diagnostic management function notifies SCS diagnostic information in response to re-
quests from windows that handle diagnostic information. This allows checking and manipulat-
ing the information from the SENG and HIS.
• It is possible to check diagnostic information for each failed part from the Diagnostic Infor-
mation Window of the SENG.
• It is possible to acknowledge/delete diagnostic information messages from the Diagnostic
Information Window of the SENG.
• It is possible to see diagnostic information as a list of system alarm messages in SOE
Viewer of the SENG and HIS.
• It is possible to check the state of the SCS, including how the CPU module is operating in
the SCS Report dialog box of the SCS State Management Window of the SENG.

n Notification of diagnostic information to Function Blocks

System status function blocks notify errors that are detected by the system diagnosis. As a
result, you can make an application logic that uses the diagnostic information as reference
and takes action when errors occur.
SEE
ALSO For more information about Safety system function blocks, refer to:
12., “Safety system function blocks” in POU Reference Manual (IM 32P03B20-01EN)
For more information about interference-free system function blocks, refer to:
13., “Interference-free system function blocks” in POU Reference Manual (IM 32P03B20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.5 Diagnosis for hardware> A8-16

A8.5 Diagnosis for hardware

The SCS carries out diagnosis at the following timing to check whether various types of hard-
ware including I/O modules are in the normal state:
• At the start of the hardware
• At specified periodical intervals during operation
This section describes the HKU function in the CPU module, and the cabinet status monitor-
ing function in the N-IO node.

n HKU (House Keeping Unit)

The HKU function in the CPU module monitors the operation environment of the CPU mod-
ule. An error in the CPU operating environment is notified to the user via diagnostic informa-
tion messages and status display window. The following items are monitored by the HKU
function.
• Fan status in the safety control unit
• Surrounding temperature of the safety control unit
• Battery temperature

n Cabinet status monitoring

The N-ESB bus module of N-IO node monitors the operating environment of the cabinet. An
error in the operating environment of the cabinet is notified to the user via diagnostic informa-
tion messages and status display window.

l Temperature monitoring
The SCS monitors the surrounding temperature of the N-ESB module, as well as the upper
limit and lower limit value in the hardware. It monitors whether the temperature exceeds the
prescribed value or not.

l Power supply diagnosis

The SCS monitors the status of the power supply unit (PSU) connected to the N-ESB module
unit. The following are the methods in diagnosing a power supply:
• PSU output stop diagnosis
The SCS monitors the output voltage in redundant PSUs. It is judged as an error if output
in either of the PSUs stops.
• Output over-voltage diagnosis
The SCS monitors the output voltage of the PSUs, as well as the upper limit and lower
limit value in the hardware. It monitors whether the output voltage exceeds the prescribed
value or not. It is judged as an error if it exceeds the maximum value.

l Input monitoring from external devices

By inputting a single point of discrete signal from an external device, which can detect power
supply and fan abnormalities, in an external alarm input of the base plate, errors from the ex-
ternal device can be notified.
The safety control unit outputs the diagnostic information message according to the discrete
signal that is inputted from the external device.
Because this function is interference-free, it cannot be used for safety logic.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-17

A8.6 Dual-redundancy in the SCS

ProSafe-RS supports dual-redundant configurations of SCS CPU modules and input/output
modules. With the dual-redundant configuration, the continuous controllability and operating
efficiency can be improved. Moreover, with dual-redundantly configured hardware, the con-
tinuity of plant safety monitoring will be guaranteed by switching the control rights when an
error occurs in the SCS hardware.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-18

A8.6.1 Redundant configuration in SCS

In SCS, redundant configuration can be selected for the CPU module and I/O modules. The
control bus, power supply module, ESB bus, ESB bus interface module, optical ESB bus re-
peater module, N-ESB bus, N-ESB bus module, and F-SB bus are always in redundant con-
figurations.

n CPU module
• The CPU module on the standby side performs the same control processing as the con-
trol side even while it is in the standby status. For this reason, it is possible to take over
outputting data immediately after the control right is switched. Moreover, the operating
mode of the SCS does not change.
• Only the CPU on the control side accesses the hardware composing the SCS and the
CPU on the standby side always sets the equivalent value as the processing result.
Therefore, the CPU modules on both sides always perform processing using the same
data.
• In redundant configuration, if the CPU module on the standby side is not in the STBY sta-
tus and the control right cannot be switched, the same operation as single configuration
CPU module is performed.
• SOE data related to discrete inputs might be lost when the control right is switched be-
tween the CPU modules.
• With the CPU module of SCSP2, the data loaded with the previous scan may be used
instead of updating the data with the value from the input module when performing a scan
immediately after a control right switchover of the CPU. Also note that data loaded from 1
or 2 scans earlier may be used with subsystem communication modules.
• With the CPU module of SCSP3, the data loaded with the previous scan may be used
instead of updating the data with the value from the input module or fire and gas commu-
nication module when performing a scan immediately after a control right switchover of
the CPU. Also note that data loaded from 1 or 2 scans earlier may be used with subsys-
tem communication modules.

n FIO I/O modules

Redundant configuration is possible in the FIO node(*1) by mounting the same type of FIO
I/O module to two adjacent slots. In the case of redundant configuration, one side becomes
the control side and the other becomes the standby side. Switching of the control right is per-
formed by input/output modules. The switching has no influence on the application logic.
*1: An odd-numbered slot and the even-numbered slot obtained by adding 1 to the odd slot number

• It is not allowed to have redundant configuration across two nodes.

• SOE data related to discrete inputs might be lost when the control right is switched be-
tween the input modules even though the frequency is low.
• A HART communication error may occur when the control right is switched between ana-
log input/output modules that support HART communication.

Table A8.6.1-1 Operation of redundant AIO/DIO modules

AIO/DIO module Redundant operation
Analog input module The input data of the input module on the control side is stored in the
Discrete input module input variable.
Analog output module The SCS outputs the same value for output modules on both the control
Discrete output module and standby sides. Only the output module on the control side outputs
signals to the field. If an error occurs on the module on the control side,
the control right is switched and outputting is continued

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-19
SEE
ALSO For more information about duplexing subsystem communication, refer to:
D1.2, “Dual-redundant communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

n NIO I/O modules

Redundant configuration is possible in the N-IO node by mounting the same type of N-IO I/O
module to two adjacent slots. In the case of redundant configuration, one side becomes the
control side and the other becomes the standby side. Switching of the control right is per-
formed by input/output modules. The switching has no influence on the application logic.
• SOE data related to discrete inputs might be lost when the control right is switched be-
tween the input modules even though the frequency is low.
• A HART communication error may occur when the control right is switched between ana-
log input/output modules that support HART communication.

Table A8.6.1-2 Redundant operation in N-IO I/O modules

Signal type Redundant operation
AI/DI The input data of the input module on the control side is stored in the
input variable.
AO/DO The SCS outputs the same value for output modules on both the control
and standby sides. Only the output module on the control side outputs
signals to the field. If an error occurs on the module on the control side,
the control right is switched and outputting is continued

n Optical ESB bus repeater module

The optical ESB bus repeater modules are always used in a redundant configuration.

n Power supply module

A redundant power supply module is installed on each of CPU nodes, I/O nodes, and N-IO
nodes of the SCS. The SCS monitors the status of the power supply at regular intervals and,
if an error occurs, it notifies the user about the error via the SCS State Management window
of the SENG, the Status Display view of the HIS, and diagnostic information messages. If one
of the two power supplies mounted on the CPU node has generated an error, it notifies two
diagnostic information messages; one corresponding to the error of the power supply module
on the CPU node and the other corresponding to the error of the power supply module on
node 1.

n ESB bus and ESB bus interface module

The ESB bus is redundant. The two ESB buses are connected to their corresponding ESB
bus interface modules. The following operations also apply when optical ESB bus repeater
devices are present along the communication route.
• Normally, redundant ESB buses are used in an alternating fashion.
• If an error occurs in either ESB bus interface module, the user is notified of the error with
a diagnostic information message. If both buses fail, the error is treated as a node failure.
• If an error occurs in one ESB bus or ESB bus interface module, the SCS continues com-
munication by using only the other ESB bus that is normal.
• An erroneous bus is monitored for normal recovery at regular intervals.
• Errors in communication with all I/O nodes, except CPU node, are judged to be ESB bus
error.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-20

n N-ESB bus and N-ESB bus module

The ESB bus has redundant configuration. Each N-ESB bus module is connected to N-ESB
bus, respectively.
• Normally, redundant N-ESB buses are used in an alternating fashion.
• If an error occurs on either N-ESB bus module, the error is notified to the user via a diag-
nostic information message. If both buses fail, the error is treated as a node failure.
• If an error occurs in either N-ESB bus or N-ESB bus module, the SCS continues commu-
nication using only the normal ESB bus on the other side.
• An erroneous N-ESB bus is monitored for normal recovery at regular intervals.

n F-SB bus
The F-SB bus has redundant configuration.
• The F-SB bus is normally used at the same time on both sides.
• If an error occurs in either F-SB bus, the SCS continues communication using only the
normal ESB bus on the other side.
• An erroneous F-SB bus is monitored for normal recovery at regular intervals.

n Vnet/IP communication
Vnet/IP is redundant. Independent subnets using bus 1 and bus 2 comprise redundant buses.
Normally, bus 1 is used for control communication. If a communication error occurs on bus 1,
bus 2 is used to perform control communication.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-21

A8.6.2 CPU redundant status

The availability of an SCS can be improved by making CPUs redundant. Each of the redun-
dant CPUs can be in either control or standby states, which are unique to the CPU.

n CPU status
In order to show the status of a redundant configuration, it is necessary to indicate the status
of each CPU separately. The operating status of the CPU is called the CPU status.
• The CPU status indicates the operating status of the CPU.
• The processing of the SCS references the CPU status as necessary. The user can check
the CPU status via the CPU's LED, the SCS State Management window of the SENG,
and the Status Display view of HIS.
• If an error occurs in the standby CPU, the FAIL status is notified to the application logic
via a system block.
The figure below illustrates the CPU status shift. Note that in order to explain the CPU status,
the operating modes it can shift to the Initial mode are called "CTRL" and "STBY." These indi-
cate whether the CPU has the control right and are specific to the redundant status, i.e., not
related to the operating mode.

CPU Fail
CTRL

Remove the cause Program

of CPU Fail Start
Control
FAIL RDY
Change
Program
CPU Fail
Start

STBY
CPU Fail

Figure A8.6.2-1 CPU status

l FAIL (CPU stopped)

The power is supplied to the CPU, but the software is not running in this status.

l RDY (CPU initializing status)

The system program is being set in the main memory in this status.

l CTRL (control status)

The system program runs inside the CPU and the CPU has the right to access input/output
modules in this status.

l STBY (standby status)

The system program runs inside the CPU but the CPU does not have the right to access in-
put/output modules in this status.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-22

n CPU status shift in redundant configuration

The figure below illustrates each CPU status and how it may shift in redundant configuration.
The thick arrows from (a) to (d) indicate the flow from the startup to normal operation in redun-
dant configuration. Note that the figure below does not represent the status by the mounting
positions of the CPUs. Even if the states of the two CPUs are switched, the indication in the
figure shows them in the same status.

(a)
(e)
FAIL CTRL control side
CTRL
FAIL CPU status
FAIL
stand-by side
STBY
CPU status

(b) (c) APC (d)

RDY CTRL CTRL

FAIL RDY STBY

Single Operation

Figure A8.6.2-2 States at redundant configuration

Table A8.6.2-1 CPU status

Status Description
(a) CPUs on the both sides stopped.
(b) The controlling CPU starts up and sets programs and databases in the main memory.
(c) (*1) The controlling CPU obtains the control right and starts up the standby CPU. Upon launching, the
standby CPU copies the image of the main memory of the controlling CPU into its main memory
(this status is displayed as "APC" and not the same as status (e)). The controlling CPU executes
the user application.
(d) Both the controlling and standby CPUs operate normally in redundant configuration. This status
is called the redundant control status.
(e) (*1) In this status, the standby CPU is stopped in redundant configuration, or the controlling CPU is
stopped and the control right is switched. The same operation as in single configuration is per-
formed.
*1: Single operating status.

The CPU shifts to each status in the following manner.

Table A8.6.2-2 Conditions of CPU status shift

Before After Shifting conditions
(a) (b) • The power supply to the SCS is started.
• SCS offline download is completed.
• The system is restarted.
(b) (c) The controlling CPU started normally.
(c) (d) APC of the standby CPU is completed.
(d) (e) The control right is switched due to a failure of the controlling CPU hardware or the
standby CPU failed.
(e) (c) The standby CPU is replaced or a CPU recovered from transient failure.
(b) (a) An error occurred in the self-diagnosis at startup.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.6 Dual-redundancy in the SCS > A8-23
Table A8.6.2-2 Conditions of CPU status shift (Table continued)
Before After Shifting conditions
(c) (a) A fatal error occurred while operating in single CPU operation.
(d) (a) Power failure occurred in the SCS (including momentary power failure).
(e) (a) A fatal error occurred while operating in single CPU operation.

l APC status
The APC status refers to the status where the data in the CPU memory is being copied from
the control side to the standby side.
The APC status can be checked by the LED on the CPU, the SCS Status Display window of
the SENG or the Status Display view on the HIS. The start and end of the APC status are
notified via a diagnostic information message.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.7 NIU status and security> A8-24

A8.7 NIU status and security

The N-ESB bus module (S2EN501) that is installed in the node interface unit (NIU) is equip-
ped with a maintenance port.
For the security reason, you should disable the maintenance port when operating the system.
The status of the NIU is determined by the status of the NIU maintenance port and operating
mode of the NIU. This section describes the status of the NIU maintenance port, NIU operat-
ing mode, and shifting of the NIU status.

n Overview of the NIU status and tools

The status of the NIU is determined by the status of the NIU maintenance port and operating
mode.
• Status of the NIU Maintenance Port
The status of the NIU maintenance port can be either enabled or disabled. The status of
the maintenance port can be switched between enabled and disabled by using the NIU
maintenance port settings tool that is called from the SCS State Management window in
the SCS Maintenance Support Tool.
• Operation mode of the NIU
The NIU operation mode can be either online mode or maintenance mode. The operation
mode can be switched between online mode and maintenance mode by using the N-IO
maintenance tool in the computer that is connected to the maintenance port.
The N-IO maintenance tool can be used if the NIU maintenance port is enabled.

IMPORTANT
The Node number setting tool and Fieldmate Validator are included in the N-IO maintenance
tool.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.7 NIU status and security> A8-25

A8.7.1 Status of the NIU maintenance port

You can run the NIU maintenance port settings tool and enable or disable access from an ex-
ternal device such as a computer connected to the maintenance port of the N-ESB bus mod-
ule.

n Disabled status
The disabled status of the maintenance port prohibits access from the maintenance port.
N-ESB bus /
Optical ESB bus

Maintenance NIU
port

Disabled status

F-SB bus : Route of access

Figure A8.7.1-1 Disabled status of the maintenance port

n Enabled status
The enabled status of the maintenance port allows access from the maintenance port.
N-ESB bus /
Optical ESB bus

Maintenance NIU
port

Enabled status
(Changing to maintenance mode
enables access to N-IO I/O modules.)
F-SB bus : Route of access

Figure A8.7.1-2 Enabled status of the maintenance port

SEE
ALSO For more information about how to enable/disable the maintenance port, refer to:
I4.4, “NIU maintenance port setting tool” on page I4-41

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.7 NIU status and security> A8-26

A8.7.2 Operation mode of the NIU

The NIU operation mode can be either online mode or maintenance mode.

n Online mode
In online mode, you can access the N-IO I/O modules from the N-ESB bus or the optical ESB
bus.
You cannot access the N-IO I/O modules from the maintenance port.
N-ESB bus /
Optical ESB bus

Maintenance NIU
port

Online mode

F-SB bus : Route of access

Figure A8.7.2-1 Online mode

n Maintenance mode
In maintenance mode, you can access the N-IO I/O modules from the maintenance port.
You cannot access the N-IO I/O modules from the N-ESB bus or the optical ESB bus.
N-ESB bus /
Optical ESB bus

Maintenance NIU
port

Maintenance mode

F-SB bus : Route of access

Figure A8.7.2-2 Maintenance mode

n Switching between operation modes

This section describes how to switch between the NIU operation modes.
• Switching from the online mode to the maintenance mode

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.7 NIU status and security> A8-27
When the maintenance port is enabled, perform the "maintenance instructions" operation
from the N-IO maintenance tool connected to the maintenance port to switch from the on-
line mode to the maintenance mode.
• Switching from the maintenance mode to the online mode.
Perform on of the following to switching from the maintenance mode to the online mode.
• Perform the "release maintenance instructions" operation from the N-IO maintenance
tool connected to the maintenance port.
• Disconnect the USB cable that is connected to the maintenance port
• Turn off the power of the NIU, then turn it on

IMPORTANT
When the node number setting tool is used as a N-IO maintenance tool, the unit will switch to
the maintenance mode when a node address is configured. After the node address is config-
ured, the unit will switch to the online mode.

TIP • Switching the maintenance mode of the dual-redundant N-ESB bus modules
Because the N-ESB bus modules are dual-redundant, when you change the operation mode on one
side, the operation mode of the other side will switch accordingly.

SEE
ALSO For more information about Node Number Setting Tool, refer to:
F2.1.1, “Using the Node Number Setting Tool” on page F2-3
For more information about FieldMate Validator, refer to:
Manual of FieldMate Validator

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A8.7 NIU status and security> A8-28

A8.7.3 Shifting the Status of the NIU

The following figure shows the status and the operation mode of the NIU maintenance port,
and the status shift with regards to external access.
Access to N-IO from the N-ESB Access to N-IO from the
Bus or the optical ESB Bus Maintenance Port
Power OFF / ON

Online / The access to NIU

Disabled cannot be accepted

Switching to the enabled status

by issuing the switching command By performing one of the following procedures.
from the NIU maintenance port • Switching to the disabled status by issuing
The access to N-IO via setting tool under the security the switching command from the NIU
NIU can be accepted level to 1 or less. maintenance port setting tool.
Power OFF / ON • The security level is returned to 2

Online /
Enabled
(Setting at the time of the
shipment of NIU)
By performing one of the following procedures.
• Issue the switching command from the
Switching to the maintenance mode N-IO maintenance tool connecting to the
by issuing the switching command maintenance port. The access to NIU
from the N-IO maintenance tool • Remove the USB cable connecting to can be accepted
the maintenance port.
• Set the power supply of NIU to ON from OFF.

The access to
The access to N-IO via Maintenance /
N-IO via NIU
NIU cannot be accepted Enabled can be accepted

Mode / Mode : Operation Mode of NIU

Port Status Port Status : The Status of the Maintenance Port

Figure A8.7.3-1 NIU status shift

The following table shows the factory settings of the N-ESB bus modules (S2EN501) that are
installed in the NIU.

Table A8.7.3-1 NIU factory settings

Target Setting Status
Operation mode Online mode The CPU module accesses the N-IO modules
from the N-ESB bus and optical ESB bus through
the NIU.
Status of the maintenance Enable You can access the NIU from the N-IO mainte-
port nance tool.
Node number Not set The NIU is not operating correctly. You need to
set the node number before connecting to the
SCU.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A9. Capacity of SCS applications> A9-1

A9. Capacity of SCS applications

This section shows the application capacity related to the SCS.

Table A9-1 Capacity of SCS applications

SCSP3
Max. capacity SCSV1,
SCSP2 SCSP1,
Types Items When When Max. capacity Note
SCSU1
using using Max. capacity
N-IO FIO
I/O Number of no- 32 13 13 9 CPU node is not included
des in the number of nodes.
Number of units 6 - - - Maximum 108 units per
SCS
Number of slots 2 8 8 8 When connecting I/O
node, the maximum slot
number of CPU nodes is
6.
Number of I/O 108 110 110 110 The total number of FIO
modules non- and N-IO I/O modules can
re- be up to 110. However,
dun- the total can only be up to
dant 109 when the total num-
mod- ber of ESB bus coupler
ules, modules and N-ESB bus
or coupler modules is 4 sets.
108 The number of I/O mod-
pairs ules is the number of sets
of re- in a redundant configura-
dun- tion and the number of
dant modules in a single con-
mod- figuration. Communication
ules modules are included in
the number of FIO I/O
modules.
Number of com- 2 2 2 For Modbus Slave Com-
munication mod- munication
ules
- - 2 For communication as a
DNP3 slave (SCSU1 only)
4 4 4 For Subsystem Communi-
cation
8 - - For safety subsystem
communication
Number of I/O 1500 1500 1500 (800 in 1000 (500 in The numbers are provided
points (1500 (800 redundant I/O redundant I/O only as a guide.
in re- in re- modules) modules)
dun- dun-
dant dant
I/O I/O
mod- mod-
ules) ules)
Number of Sub- 2000 data 2000 data 500 data Per SCS
system Commu- (SCSV1)
nication Data 2000 data
(SCSP1,
SCSU1)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A9. Capacity of SCS applications> A9-2
Table A9-1 Capacity of SCS applications (Table continued)
SCSP3
Max. capacity SCSV1,
SCSP2 SCSP1,
Types Items When When Max. capacity Note
SCSU1
using using Max. capacity
N-IO FIO
I/O Number of safety 2000 data - - Per SCS
subsystem com- The safety subsystem
munication data communication I/O area is
4000 words and the mini-
mum unit of data that can
be assigned to this area is
2 words. For this reason
the maximum number of
data is 2000 data.
The maximum number of
data when only GS01 is
connected is approximate-
ly 1350 data. (*1)
Application Number of pro- Max. 500 Max. 500 Max. 500 When more than 500
logic grams and user- POUs are defined in the
defined FU/FB SCS Manager, an error
(number of occurs in building. It may
POUs) not be possible to define
500 POUs depending on
the type and number of
FU/FB or LD elements. A
restriction may be im-
posed depending on SCS
performance.
Definable num- 1500 I/O 1500 I/O 1000 I/O The numbers are provided
ber of variables variables. variables. variables. only as a guide.
4500 internal 4500 internal 3000 internal It may not be possible to
variables variables variables. define the maximum num-
ber of variables shown in
the left columns depend-
ing on each type of de-
fined variables and the
performance of SCS.
Inter-SCS Send data 200 data 200 data 200 data This is the maximum num-
Safety Com- ber of send data per SCS.
munication
Receive data 200 data 200 data 200 data This is the maximum num-
ber of receive data per
SCS.
SCS Link Send data 128 data 128 data 128 data This is the maximum num-
Transmission ber of send data per SCS.
Receive data 1000 data 1000 data 1000 data This is the maximum num-
ber of receive data per
SCS.
CENTUM in- Annunciators 2000 2000 1000 -
tegration (%AN)
function,
FAST/TOOLS Common 800 300 200 All are system switches.
integration switches (%SW)
function (*2) External Com- (*3) (*3) (*3) (*4) -
munication FB
External commu- - - (*4) SCSU1 only. The maxi-
nication FB (with mum capacity is limited by
data retaining the size of the area for da-
function) ta retention.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A9. Capacity of SCS applications> A9-3
Table A9-1 Capacity of SCS applications (Table continued)
SCSP3
Max. capacity SCSV1,
SCSP2 SCSP1,
Types Items When When Max. capacity Note
SCSU1
using using Max. capacity
N-IO FIO
Gas flow rate Gas flow rate - - 1 SCSU1 only
calculation calculation FB
function (Total of AGA_*)
Report data cre- - - 1 SCSU1 only
ation FB
(AGA_R)
Mapping Analog input Total 2700 Total 2700 Total 1800 -
block blocks (*5) (*5) (*6)
(ANLG_S, ANL-
GI, HSDTR,
GASDTR)
Velocity alarm -
blocks (VEL)
Maintenance OVR_B, OVR_I, OVR_R,
override blocks OVR_IB, OVR_IR,
(OVR_*, GOV_*) GOV_B, GOV_IB
Password blocks -
(PASSWD)
Manual opera- MOB_11, MOB_21,
tion blocks MOB_RS, MOA
(MOB_*, MOA)
Gas flow rate - - -
calculation
blocks (AGA_3,
AGA_7, AGA_R)
Annunciator 2000 2000 1000 Mapping to %AN element
blocks (ANN,
ANN_FUP)
Communica- Overall size of 4000 Words 4000 Words 4000 Words 1 Word = 16 Bits
tion I/O area %W
%W: For map- 200 Words 200 Words 200 Words 1 data = 2 words, 100 da-
ping (BOOL) (3200 Bits) (3200 Bits) (3200 Bits) ta
%W: For map- 1800 Words 1800 Words 1800 Words 900 data
ping (32-bit ana-
log data)
%W: For subsys- 1000 Words 1000 Words 1000 Words Up to 2000 data in total of
tem communica- bit data and analog data
tion can be assigned.
%W: Not used 1000 Words 1000 Words 1000 Words
Safety sub- %X: For safety 4000 Words - - 1 Word = 16 Bits
system com- subsystem com- The minimum unit of data
munication munication that can be assigned to
I/O area the safety subsystem
communication I/O area is
2 words. For this reason
the maximum number of
data is 2000 data.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A9. Capacity of SCS applications> A9-4
Table A9-1 Capacity of SCS applications (Table continued)
SCSP3
Max. capacity SCSV1,
SCSP2 SCSP1,
Types Items When When Max. capacity Note
SCSU1
using using Max. capacity
N-IO FIO
Modbus Coil 1000 Bits 1000 Bits 1000 Bits -
Slave
Input relay 4000 Bits 4000 Bits 4000 Bits -
Input register 4000 Words 4000 Words 4000 Words 1 word = 16 bits, 1 data =
2 words, 2000 data
Holding register 1000 Words 1000 Words 1000 Words 500 data
SOE SOE storage 15000 events 15000 events 15000 events -
area (RAM)
Back up area on Last 1000 Last 1000 Last 1000 -
power failure events events events
(nonvolatile
RAM)
Trip signal file 2 trip signal 2 trip signal 2 trip signal -
(nonvolatile files of up to files of up to files of up to
RAM) 1500 events 1500 events 1500 events
Diagnostic in- Area for saving 5000 mes- 5000 mes- 5000 mes- -
formation diagnostic infor- sages sages sages
message mation messag-
es (RAM)
Back up on pow- Last 200 Last 200 Last 200 -
er failure (nonvo- messages messages messages
latile RAM)
Data buffer- Number of buf- - - 135000 SCSU1 only
ing fers
Area for data Size of area for - - 6 Kbyte SCSU1 only
retention data retention
*1: Example of when 3 definitions (1 definition of data used with safety communication where the number of data is 2 with 8
words, 2 definitions of data used with an interference-free function where the number of data is 1 with 2 words) are used with
a single GS01. The formula is: (4000 words / 12 words) x 4 data = approximately 1350 data. In this case, the number of GS01
units connected is approximately 300 units (4000 words / 12 words).
*2: The CENTUM integration function can be used with SCS of types SCSP3, SCSP2, SCSP1, and SCSV1. FAST/TOOLS inte-
gration function can be used with SCS of types SCSP2, SCSP1, and SCSU1.
*3: For SCS other than SCSU1, the maximum capacity can be defined as follows:
• When using Modbus, the maximum definable number of external communication FB is up to 1000 for ECW_B and 500 for
ECW_I and ECW_R in combination.
• In tag assignment, up to 3200 Boolean internal variables and ECW_B FB in combination can be defined.
• In tag assignment, up to 900 DINT and REAL internal variables, input variables of IO_REAL and FB of ECW_I and
ECW_R in combination can be defined.
*4: For SCSU1, the maximum capacity can be defined as follows:
• When using Modbus, ECW_B and ECWR_B can be defined up to 1000 in total. ECW_I, ECWR_I, ECW_R, and ECWR_R
can be defined up to 500 in total.
• Up to 3200 tag names can be defined in total for Boolean internal variables and function blocks of ECW_B and ECWR_B.
• Up to 900 tag names can be defined in total for DINT and REAL internal variables, input variables of IO_REAL, and func-
tion blocks of ECW_I, ECWR_I, ECW_R, and ECWR_R.
*5: In FAST/TOOLS integration, HSDTR, GASDTR, OVR_*, GOV_*, PASSWD, MOB_*, and MOA cannot be used.
*6: For SCSU1, this is the total including AGA_3 or AGA_7 and AGA_R.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10. Outline of the safety system generation function> A10-1

A10. Outline of the safety system

generation function
This section gives an overview of the tools used to configure and maintain a safety system.
It also describes the different types of applications that can be created by using ProSafe-RS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.1 SCS Manager > A10-2

A10.1 SCS Manager

You can call SCS Manager from AD Organizer. You can create a new SCS project by using
SCS Manager and call the SCS engineering and maintenance tools.
From the [Tools] menu of SCS Manager, three launchers can be started.
From each launcher, various engineering functions such as builders, SCS related tools and
SCS Maintenance Support Tool can be launched. This section mainly explains the precau-
tions when closing and opening SCS projects and launchers started from SCS Manager.

n Precautions when opening SCS projects

IMPORTANT
SCS projects cannot be opened if you cancelled password input (except when read-only ac-
cess is permitted without entering a password) or failed to enter the correct password three
times while attempting to open SCS projects for which passwords are set. Close SCS Manag-
er and try opening it again.

Projects that have not been created as databases to be edited in SCS Manager of ProSafe-
RS cannot be opened.
It is not possible to open the same SCS project in SCS Manager, Version Control Tool and
Master Database Restoring Function at the same time.

n Precautions when closing SCS projects

This section describes the precautions when closing SCS Manager.
• Closing SCS Manager closes the currently opened SCS project.
• When you close SCS Manager, all the related builders, Safety Analyzer and launchers
close. If the security level is not Level 2 when closing, a message prompting the user to
return to Level 2 appears. Set the SCS’s security level to Level 2 by using the SCS Se-
curity Level Management Function.
• SCS Maintenance Support Tool is not closed even if SCS Manager is closed.
TIP The SCS project opened in SCS Manager cannot be opened in Version Control Tool or Master Database Re-
storing Function. To use these tools, close SCS Manager.

SEE
ALSO For more information about how to operate the SCS security level operation function, refer to:
B3., “Security of SCS” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

n Starting and closing launchers

From the [Tools] menu of SCS Manager, the following three launchers can be started.
• [Engineering]
Starts the Engineering launcher such as builders.
• [Controller]
Starts the SCS launcher.
• [Maintenance]
Starts the Maintenance launcher.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.1 SCS Manager > A10-3
TIP The menu items for starting launchers are also displayed in the pop-up menu opened by right-clicking when a
configuration and/or resource are selected in SCS Manager or Dictionary View is opened.

l Starting launchers
Each launcher is started from the [Tools] menu. If the same launcher has already been star-
ted, a new launcher is not started; instead, the already started launcher is displayed on the
foreground and given the focus.
The Engineering launcher and the Maintenance launcher have a push-pin icon. If you place
the push-pin icon in the pressed status, the corresponding launcher is always displayed on
the foreground without being hidden by other windows. If you disable the push-pin icon, the
launcher may be hidden by other windows.
The Controller launcher is always displayed on the foreground.
If two or more launchers are set to be displayed on the foreground, the launcher started up
later is displayed on the foreground.

l Closing launchers
Each launcher is closed if you click "Close" button of the launcher or close SCS Manager. If
you close a launcher by clicking "Close" button, only the launcher is closed and windows
opened from the launcher are not closed.
The Controller launcher closes if a menu is selected and the corresponding tool is started.

n Engineering launcher
The table below shows builders and tools that can be started from the Engineering launcher.

Table A10.1-1 Engineering launcher menu

Menu item Operation
SCS Project Properties Opens the SCS Project Properties dialog box
SCS Constants Builder Starts SCS Constants Builder
I/O Parameter Builder Starts I/O Parameter Builder
Communication I/O Builder Starts Communication I/O Builder
SCS Link Transmission Builder Starts SCS Link Transmission Builder
Modbus Address Builder Starts Modbus Address Builder
DNP3 Communication Builder (*1) Starts DNP3 Communication Builder
Tag Name Builder (*2) Starts Tag Name Builder
Alarm Priority Builder (*2) Starts Alarm Priority Builder
Alarm Processing Table Builder (*2) Starts Alarm Processing Table Builder
Integrity Analyzer Starts Integrity Analyzer
Cross Reference Analyzer Starts Cross Reference Analyzer
Database Validity Check Starts Database Validity Check Tool
SCS Information Opens the SCS Information dialog box
*1: DNP3 Communication Builder is displayed only for the SCS projects of SCSU1 that are created by the software version
R3.02.20 or later.
*2: Only opened in the case of CENTUM integration structures.

If a library project is open in SCS Manager, only the [SCS Project Properties] and [Integrity
Analyzer] menu items are displayed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.1 SCS Manager > A10-4

n Controller launcher
The table below shows tools that can be started from the Controller launcher.

Table A10.1-2 Controller Launcher Menu

Menu item Operation
Save Operation Marks (*1) Save the operation marks set on CENTUM HIS to SENG
Download Operation Marks (*1) Download the saved operation marks to SCS
Restart SCS Restarts an SCS
Reset SCS Master Database Offline
Performs master database offline download
Download
*1: Only opened in the case of CENTUM integration structures.

If a library project is open in SCS Manager, the Controller launcher cannot be started.

n Maintenance launcher
The table below shows tools that can be started from the Maintenance launcher.

Table A10.1-3 Maintenance launcher menu

Menu item Operation
Starts the SCS Status Overview of SCS Maintenance Support
SCS Status Overview
Tool
Starts the SCS State Management of SCS Maintenance Sup-
SCS State Management
port Tool
Set SCS Security Level Opens the Set SCS Security Level dialog box.
I/O Lock Window Starts the I/O Lock Window
Communication I/O Lock Window Starts the Communication I/O Lock Window
SCS Link Transmission Lock Window Starts SCS Link Transmission Lock Window
Inter-SCS Communication Lock Window Starts Inter-SCS Communication Lock Window
SCS Test Function (*1) Starts SCS Test Function
Update SCS Test Database (*1) Updates SCS Test Database
*1: In the case of CENTUM integration structures, this menu item is displayed when the SCS project is a default project or a
user-defined project.

If a library project is open in SCS Manager, the Maintenance launcher cannot be started.

IMPORTANT
If SCS Manager is in the logic simulation mode, the I/O Lock window, Communication I/O
Lock window, SCS Link Transmission Lock window, and Inter-SCS Communication Lock win-
dow cannot be started.

n Show/hide SCS Manager toolbars

If you launch SCS Manager or Multi-Language Editor, the displayed toolbar will be the same
as that before, when you closed last time. The toolbar display is retained per each Safety En-
gineering PC (SENG) and cannot be set per each user. If you hid the toolbar last time you
used the SCS Manager or Multi-Language Editor and if you want the toolbar to show this
time, for example, change the show/hide status of the toolbar.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.1 SCS Manager > A10-5
Follow the steps below to show or hide the toolbar.
1. On the [Options] menu, click [Layout].
The Layout dialog box appears.
Layout

Main Toolbar
Option Toolbar
Debug Toolbar
Window Buttons Toolbar
Status bar

Zoom: 200% 100% 50% Other: 0

OK Cancel

Figure A10.1-1 Layout dialog box

2. Select the check boxes of the toolbar you want to show.

If you want to hide the toolbar, clear all the check boxes.
3. Click [OK].
To change the docking or floating status of the toolbar, drag it to the position you like.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.2 Safety application definition> A10-6

A10.2 Safety application definition

Safety applications are created with tools and builders called from the AD Organizer and the
SCS Manager.
When using AD Suite to perform I/O list engineering, you need to use the editors in AD Or-
ganizer to set the items instead of using I/O Wiring View, I/O Parameter Builder, and Commu-
nication I/O Builder.
If you select I/O list engineering and use iDefine, you can create the application logic by using
iDefine based on the ProSafe-RS I/O file that was exported from AD Organizer. The ProSafe-
RS I/O file is a file generated for engineering with iDefine based on the safety I/O list, safety
communication I/O list, and IOM definition.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.2 Safety application definition> A10-7
Plant information Safety I/O list Safety Communication I/O List iDefine

IOM information (*3)

(*2)
AD Suite
AD Organizer
Safety
Safety I/O Editor Communication IOM Definition Editor
I/O Editor

RS Generation Manager

(*1)

SENG
SCS Manager

Link Hardware
Binding List View Dictionary View I/O Wiring View
Architecture View Architecture View

SCS Link
Multi-Language SCS Project I/O Parameter Communication SCS Constants
Transmission
Editor Properties Builder Builder I/O Builder Builder

SCS

Input variables SOER Time synchronization

POU method
Output variables I/O action on a failure SCS common
SOER constants
Internal variables Input

Output Passwords

Safety subsystem
SCS project Link transmission communication
Binding SCS parameters
attribute definition definition I/O definition

SCS

Binding Link transmission

definition

*1 : In the case of I/O list engineering, you can reflect the safety I/O list, safety communication I/O list, and IOM definition to the SCS
Manager builder by running the reflection process through RS Generation Manager. If you run the reflection process on the
engineering data that was created by using iDefine through RS Generation Manager, the application data can be reflected to the
Multi-Language Editor and SCS.
*2 : AD Organizer exports the data that was created from the safety I/O list, safety communication I/O list, and IOM definition to iDefine.
*3 : AD Organizer imports the engineering data that was created by using iDefine.
Legends
: Builder or editor
: Definition, file, parameter, or variable
: Group of definitions or files
: Download of builder definitions
: Communication

Figure A10.2-1 Overview of safety application definition

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.2 Safety application definition> A10-8

n AD Organizer
AD Organizer is installed in the SENG computer. You can perform the ProSafe-RS engineer-
ing by using AD Organizer. AD Organizer comes with some built-in engineering tools, and
SCS Manager is one of them.

l Safety I/O Editor

This is an engineering tool that can be used from AD Organizer.
The tool is used to create safety I/O lists based on plant information data and import them as
engineering data.
It is also used to define variables that are related to the safety I/O. You specify the SCS node
and IOM applicable to the P&ID tag and the associated connection information based on the
information that is displayed in the Safety I/O Editor.
With this editor, you can export a file containing data for engineering with iDefine.

l Safety Communication I/O Editor

This is an engineering tool that can be used from AD Organizer.
This tool is used to create safety communication I/O lists based on plant information data and
import them as engineering data.
It is also used to define variables that are related to the safety communication I/O. You specify
the SCS node and IOM applicable to the P&ID tag and the associated connection information
based on the information that is displayed in Safety Communication I/O Editor.
With this editor, you can export a file containing data for engineering with iDefine.

l IOM Definition Editor

This is an engineering tool that can be started from AD Organizer.
In the IOM Definition Editor, a list of nodes and I/O modules are displayed with their proper-
ties.
You can use the IOM Definition Editor to define the I/O module configuration and set the prop-
erties of nodes and I/O modules. If I/O module assignment information is not defined in the
safety I/O list or safety communication I/O list, you can define the assignment of I/O modules
to nodes by using IOM Definition Editor.

l ADMDB
This is the server database that stores all the engineering data that is included in the AD
Server. The revision history of the engineering data and the hardware configuration informa-
tion are also stored in this database.
The AD Server manages the engineering data.

l Generation Manager
For SCS projects that are created with I/O list engineering, Generation Manager reflects the
information of the safety I/O lists, safety communication I/O lists, and I/O module configuration
and builds SCS projects.

n SCS Manager
This is installed in the computer of SENG. It is an environment for creating application logic.

l Hardware Architecture View

• Set the configuration name.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.2 Safety application definition> A10-9
• Define the IP address of the SCS.

l Link Architecture View

• Configuring the security settings of the SCS project.
• Defining the POU.(*1)
• Adding variable groups.
• Starting the Multi-Language Editor to edit the POU that you have defined.
*1: POU: Program Organization Unit It is a generic term for the programs, function blocks (FB), and functions (FU) that are writ-
ten with the function block diagram (FBD) and ladder diagram (LD)

l SCS Project Properties

Defining Project properties including station type, domain number, and station number of SCS
Designating location of the integrated CENTUM project folder, in the case of CENTUM Inte-
gration Configuration

l SCS Constants Builder

Settings SCS common constants and time synchronization method

l Dictionary View
If you select the RS original engineering method, the Dictionary View is used to set the pa-
rameters of FUs and FBs and define project variables. If you select the I/O list engineering
method, the variables that were defined by using AD Organizer and iDefine are read-only in
Dictionary View.

l Multi-Language Editor
Edit the POUs for the LBD, LD, and ST.
POUs that were defined by using iDefine are read-only in Multi-Language Editor.

l Binding List View

Binding variables from the producer to the consumer of Inter-SCS safety communication

l SCS Link Transmission Builder

Defining SCS link transmission safety communication and SCS global switch communication

l I/O Wiring View

In the SCS project where the RS original engineering method is selected, the I/O Wiring View
is used to define the following:
• Analog I/O modules, discrete I/O modules, universal type I/O modules (these three types
of modules are collectively called "AIO/DIO modules"), and communication modules
• Wiring between I/O module channels and I/O variables
If you select I/O list engineering, this builder is read-only.

l I/O Parameter Builder

In the SCS project where the RS original engineering method is selected, I/O Parameter
Builder is used to configure the node, module, and channel parameters, including the settings
for the operation when a fault is detected in an I/O module or channel, and to define SOER
collection through DI/DO.
If you select I/O list engineering, this builder is read-only.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.2 Safety application definition> A10-10

l Communication I/O Builder

For SCS projects for which I/O list engineering is selected, this builder becomes read-only.
Use Safety Communication I/O Editor when you assign communication I/O data for safety
subsystem communication and perform wiring of communication I/O variables. The contents
of Safety Communication I/O Editor will be reflected in this builder by running a reflection from
AD Organizer.

n iDefine
iDefine is an external engineering tool. Using iDefine, you can create application logic based
on data such as the safety I/O list, safety communication I/O list, and IOM information ob-
tained from AD Organizer.
Once data related to the application logic that was created using iDefine is exported to a file
and then imported using AD Organizer, the content can be reflected in SCS Manager by using
RS Generation Manager.
The safety I/O list, safety communication I/O list, and IOM information created with AD Organ-
izer are read-only in iDefine.
The engineering data that were created in iDefine and reflected in SCS Manager are read-
only in SCS Manager.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.3 CENTUM integration application definition> A10-11

A10.3 CENTUM integration application definition

The following figure shows the outline of CENTUM integration application definition and the
associated builders.
These builders are opened from the engineering launcher of the SCS Manager.
• Tag Name Builder
This builder defines tag names for FBs and variables which can be used for CENTUM In-
tegration Configuration, and also defines annunciator messages.
Defining a tag name results in the creation of a mapping block for CENTUM Integration
Configuration.
When engineering by using iDefine, you can also define the tag names for FBs and varia-
bles by using iDefine. Use the reflection process from Generation Manager to reflect the
definitions in Tag Name Builder. Tag names that were defined by iDefine are read-only in
Tag Name Builder.
• Alarm Priority Builder
This builder defines alarm priority. The condition of alarm activation is set to each alarm
priority as in CENTUM.
• Alarm Processing Table Builder
The Alarm Processing Table Builder is used to import the ‘Alarm Processing Table de-
fined in CENTUM’ to SCS project.
This table determines the priority of process alarms that are generated from mapping
blocks when integrating with CENTUM.
When engineering by using iDefine, you can also configure the tag names in iDefine. The tag
names are read-only except for configured tools.
In a CENTUM integration structure, the application of ProSafe-RS needs to be defined with
those builders. Furthermore, engineering of CENTUM including SCS definition and tag list
generation needs to be executed on CENTUM ENG. This allows HIS to access SCS data with
a tag name and to display annunciator messages.
The following figure provides an overview of CENTUM Integration Application Definition.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.3 CENTUM integration application definition> A10-12
Definition
iDefine

SENG
Definition
Tag Name Builder AD Suite
Reflection

Import Definition
Alarm Processing Alarm Priority
Table Builder Builder

SCS

Safety Application CENTUM Integration

Application
Alarm
Priority
Tag Data
Map Mapping
Information Variables Blocks/Elements Alarm
Processing Table

Communication

ENG HIS

Download
SCS Tag list Builder SCS Tag list

Alarm Processing Table

Figure A10.3-1 Outline of CENTUM Integration Application Definition

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.4 Defining applications that use communication modules> A10-13

A10.4 Defining applications that use

communication modules
In ProSafe-RS, you can create an application that exchanges data with other system through
a communication module. Modbus slave communication, Modbus subsystem communication,
and safety subsystem communication are supported. Safety subsystem communication can
be used with SCSP3 only. In addition, you can create DNP3 communication applications in
SCSU1. Modbus slave communication and Modbus subsystem communication are interfer-
ence-free functions. Safety communication is included in safety subsystem communication.
The following builder is used for Modbus slave communication:
• Modbus Address Builder
It defines the Modbus device address.
The following figure shows the outline of the definitions of Modbus slave communication appli-
cation.

SENG

Modbus Address
Builder

Definition

SCS

Modbus
Safety Slave
Application Communication
Application Other System
(Modbus Master)
Map
Modbus devices Communication
Variables Application
defined virtually

Figure A10.4-1 Outline of Modbus slave communication application definition

The following builder or editor is used for subsystem communication:

• Communication I/O Builder (for RS original engineering)
• Safety Communication I/O Editor of AD Organizer (for I/O list engineering)
It defines the communication data, and allocates the communication I/O FB there.
The following two types of subsystem communication are supported:
• Using the serial communication module, you can create an application for subsystem
communication between SCS and Modbus PLC. By creating an application for subsystem
communication between SCS and ProSafe-SLS, you can acquire events and data of
ProSafe-SLS.
• Using Ethernet communication module, you can create an application for the subsystem
communication between the SCS and Modbus/TCP PLC.
The following editor is used for fire and gas communication:
• Safety Communication I/O Editor of AD Organizer
Define communication data and assign the PROFINET communication I/O FB and fire
and gas communication FB to the communication data.
Using fire and gas communication modules, you can create an application for safety sub-
system communication between the SCS and fire and gas devices.
The following builder is used to define DNP3 communication applications:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.4 Defining applications that use communication modules> A10-14
• DNP3 Communication Builder
This builder enables SCS to act as a DNP3 slave station and associates DNP3 data with
application logic variables.
The following figure shows the outline of the DNP3 communication application definitions.

SCADA

DNP3 Ethernet
Defined by DNP3 client
Communication Builder Defined by
IOM Definition Editor,
Key: DNP3 data type and index or I/O wiring view and
I/O Parameter Builder

SCS ALE111 module

IEC application DNP3 communication application
parameters parameters

FB DNP3 data
Instances

Figure A10.4-2 Outline of DNP3 communication application definition

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.5 Definition of FAST/TOOLS integration application> A10-15

A10.5 Definition of FAST/TOOLS integration

application
The following describes the builder and outline of the FAST/TOOLS integration application
definitions. FAST/TOOLS integration is an interference-free function.
In FAST/TOOLS integration, you can define I/O modules and create function blocks in addi-
tion to using the following builders and tools:
• Domain Properties Setting Tool
It selects the operating mode of Vnet/IP-Upstream.
• Message Cache Tool
A group is defined when the network configuration of Vnet/IP-Upstream is in the narrow-
band mode.
• Tag Name Builder
You can enter tag name, and other information to the data to be handled in FAST/
TOOLS.
When engineering by using iDefine, you can also define the tag names for FBs and varia-
bles by using iDefine. Use the reflection process from Generation Manager to reflect the
definitions in Tag Name Builder. Tag names that were configured by using iDefine are
read-only in Tag Name Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.6 Engineering tools> A10-16

A10.6 Engineering tools

The following describes the tools that are used after you have created a ProSafe-RS applica-
tion:

n Integrity Analyzer
The Integrity Analyzer is used to analyze the safety of existing created application logics. It
detects unauthorized FB /FU as the safety function, and outputs results of analyzing on
screen or on the analysis report.

n Cross Reference Analyzer

It shows, on screen or on the analysis report, the difference between the application previous-
ly downloaded (which runs currently on SCS) and the application to be downloaded soon as
well as the extent of impact in case of downloading. The Cross Reference Analyzer is for limit-
ing the scope of retesting when application logic is modified.

n Self-Documentation function
This is for printing user applications. The entire definitions of an SCS project or any parts can
be selected as a printed item.

n Project Attribute Tool

This tool can be used to display the attribute of an SCS project.

n Test Project Creation Tool

This tool can be used to copy a project that is running at a plant site and create a project for
test purpose.

n Import/Export function
Import or export functions can be used to import or export SCS project data. Therefore, these
data can be used for test functions or for reusing applications.

n Project Comparing Tool

This tool can be used to detect the difference between two specified SCS projects and to dis-
play and print the result.

n Version Control Tool

This is for controlling the version history of an SCS project to support the project updates by
users.
By using Version Control Tool, you can save (check-in) the project data of an SCS project at a
certain point upon adding a version number and restore (check-out) project data of a certain
version. If you are performing I/O list engineering, start this tool from AD Organizer. If you
start it from the Start menu, the data of AD Suite cannot be handled by the tool.
SEE
ALSO For more information about precautions for handling an SCS project engineered by I/O list engineering that
was checked in with Version Control Tool of a revision earlier than R4.03.10, refer to:
“n Precautions for handling an SCS project that was checked in with Version Control Tool of a revision
earlier than R4.03.10” on page C3-2

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<A10.6 Engineering tools> A10-17

n Master Database Restoring Function

This function is used to restore the contents of the master database as the work database.
Use this function to discard changes made to the work database and use the master data-
base as the data subject to engineering (work database). If you are performing I/O list engi-
neering, start this tool from AD Organizer. If you start it from the Start menu, the data of AD
Suite cannot be handled by the tool.
SEE
ALSO For more information about precautions for restoring an SCS project that was generated by RS generation
with AD Organizer of a revision earlier than R4.03.10, refer to:
“n Precautions for restoring an SCS project that was generated by RS generation with AD Organizer of
a revision earlier than R4.03.10” on page C3-2

n Database Validity Check Tool

The Database Validity Check Tool is used to check the integrity of the database in the work
database and master database of SCS project, and SCS database in SCS. The master data-
base can be repaired if the master database has lost validity due to such as an error that has
occurred during online change download. This repair function of the tool repairs the master
database by replacing it with the work database.

n SCS Information
This function is used to display and print SCS project usage conditions such as POUs used
within the SCS and the number of variables. This function can also be used to check the data-
base revisions in the SCS project, number of project I/O licenses and their usage. You need
to build an SCS project before using this function.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B. Designing applications> B-1

B. Designing applications
In the basic design of ProSafe-RS system configuration, you must consider the safety func-
tions, architecture, installation method, and field I/O devices of the systems, as well as the
management of documents and software.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B1. Key points of basic design> B1-1

B1. Key points of basic design

Having a proper basic design is very important for designing and building a safety instrumen-
ted system.
This section explains the important points to be considered for the basic design.
When the user has set a requirement for the safety integrity level (SIL), the requirement
should be reviewed before calculating the PFD (Probability of Failure on Demand) of each
safety loop in order to create a basic design that meets the required SIL.

n Independence of safety instrumented system and process control

system function
Establish independence of safety functions in a ProSafe-RS system and of control functions
in a Process control system such as DCS.

n Safety function and safety integrity

Consider the following items for Safety Function and Safety Integrity.
• Whether Redundancy for ProSafe-RS is needed or not (CPU and I/O modules)
• The failure rate of each component comprising the safety loop (Sensors, transmitters, re-
lays, logic solver and final elements)
• Requirements for SIL and PFD value of a loop
• Interval between proof tests
• The possibility to easily perform validity check and proof tests for the applied system

n Safety applications that can be used in ProSafe-RS

The ProSafe-RS system can primarily be used for the following applications.
• Emergency Shutdown System (ESD)
• Fire and Gas System (FGS)
• Burner Management System (BMS)
ProSafe-RS is capable of handling both applications configured of a combination of a NC
(Normally-Closed) input and a DTS (De-energized-To-Safe) output and applications config-
ured of a combination of a NO (Normally-Open) input and an ETS (Energized-To-Safe) out-
put.

n Architecture (basic functions)

Consider the following items for Architecture.
• Choice of “Normally Open (NO)” or “Normally Close (NC)”
• Choice of "Energized-to-Safe state principle (ETS)" or "De-energized-to-Safe state princi-
ple (DTS)"

IMPORTANT
It is recommended that SCS be separated into two SCSs. : One SCS with applications com-
prised of NC inputs and DTS outputs are performed. The other SCS with applications com-
prised of NO inputs and ETS outputs are performed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B1. Key points of basic design> B1-2
• Redundant structure of safety loops
• Actions under fault conditions
• Safety time and scan period for process
• Requirements for Sequence Of Event Recorder (SOER) Data Collection and Time Syn-
chronization System
• Man Machine Interface
• Requirements for each communication line
• Consideration for maintenance
• Maintenance override and bypass

n Power supply and grounding

See and follow the ProSafe-RS Installation Guidance for installation.
SEE
ALSO For more information about power supply and grounding, refer to:
ProSafe-RS Installation Guidance (TI 32P01J10-01EN)

n Common cause failure

Consider the distribution of functions of the ProSafe-RS system in order to deal with common
cause failures.

n Field input devices (sensors, transmitters and signal converters)

Consider the following items for field input devices:
• Number of points for each signal type (DI or AI)
• Independence from control system
• Process parameter in normal operation and trip point
• Redundancy of input devices: 1oo1, 1oo2, 2oo3 and 2oo4
• Failure rate of input devices, especially the dangerous failure rate
• Whether Wiring Check is needed or not

n Field output devices (actuator, solenoid valve, shutdown valve, etc.)

Consider the following items for field output devices:
• Number of points for each signal type.(DO or AO, voltage value and current value sepa-
rately)
• Independence from control system
• Choice of Actuator and final element, and their speed of actions (Open direction and
Close direction)
• Redundancy of actuators and final elements
• Considering the case of using relay output
• Failure rate of actuators and final elements, especially the dangerous failure rate
• Whether Wiring Check is needed or not

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B1. Key points of basic design> B1-3

n Man machine interface

Consider the following items for the Man Machine Interface.
• For Operator Interface
• Screens such as CRT and LCD
• Annunciators:
size of display/actions/colors/sounds
• Switches and lamps for a monitoring board
• Print items of a printer
• Manual shutdown
• Reset function on recovery
• Interface for maintenance and engineering
• Configuration definition of system hardware
• Building application logics and downloading them to SCS
• Modification, testing and monitoring of the application logics
• Maintenance override
• Monitoring system status of SCS and diagnostic information
• Controlling SCS security level
• SOER

n Management for design documents and software

Consider the following items.
• Print and storage management of design documents
• Management of changes for hardware and software
TIP If you use iDefine, you can use the functional safety management (FSM) function of iDefine.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B2. Procedure for engineering> B2-1

B2. Procedure for engineering

The regular engineering procedures from design to actually starting the operation, including
production, inspection and commissioning, vary depending on the engineering method that
you select and the type of nodes to be used.
In the case of RS original engineering, SCUs and FIO or N-IO equipment are engineered and
delivered altogether.
In the case of I/O list engineering where N-IO is used, N-IO equipment can be delivered earli-
er than SCUs, allowing the loop checks between N-IO equipment and field devices to be con-
ducted at the site in advance. The adjustment of the entire system is performed after SCUs
are delivered.
RS original engineering I/O list engineering when N-IO is used

Start designing Start designing

1. Basic design 1. Basic design

2. Design of detailed function 2. Design of detailed function

3. Creation of application software 3. Creation of application software

Manufacturing of hardware Manufacturing of hardware

4. Functional
4. Functional test *1
Test
6ʼ. Priority delivery
of N-IO
5. Factory Acceptance
5. Factory Acceptance Test (FAT) Test (FAT)
(SCS only)
7ʼ. Adjustment
in a plant
(at I/O level)
6. Delivery 6. Delivery

7. Adjustment in a plant 7. Adjustment in a plant (System) *2

8. Site Acceptance Test (SAT) 8. Site Acceptance Test (SAT)

Stop Stop

*1: You can flexibly decide the timing of priority delivery in a range from step 3 to 5
depending on the customer's request.
*2: Perform the remaining functional test items.

Figure B2-1 Procedure for engineering

1. In Basic Design, the following items should be decided based on user’s requirements and
specifications.
• The making of safety specification
• System configuration and hardware

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B2. Procedure for engineering> B2-2
• The number of I/Os
• Safety Integrity Level (SIL) of loops
• Signal interface with another system
The following documents are made as a result of these work.
• Diagrams of the system structure
• Hardware specifications
• System basic design document
• Safety I/O list
• Safety communication I/O list
• List of interfaces with other systems (items not included in the safety communication
I/O list)
2. Prepare a functional specifications document based on the user's requirements and spec-
ifications. Detailed logics such as shutdown logic and others are included in the functional
specifications.
3. Create ProSafe-RS projects and applications on a computer installed with the SENG
function. The hardware is also manufactured.

IMPORTANT
When prioritizing the N-IO delivery, you can flexibly decide the priority delivery timing in a
range from step 3 to 5 depending on the customer's request.

4. Functions of the created application are checked. After making a document about the
Test Specification, usually testing of functions is conducted in the following order.
(1) Desk test
The created applications are checked with self documents on the desk.
↓
(2) Unit test-1
Verify the created logic operations. You can use the SCS simulation test and logic simu-
lation test environments on the computer for verification.
↓
(3) Unit test-2
In the target test using SCS, the overall logic etc. are verified.
↓
(4) Integration test
The integrated final test is conducted on the SCS target. Before the test, it is required to
provide an environment, where SCS can be used, in combination with panel, console, a
host computer and other subsystems. The testing for system failure such as hardware
failure is also conducted.
5. Conduct the hardware and software Factory Acceptance Test (FAT) in the presence of
the user. When prioritizing N-IO delivery, perform the Factory Acceptance Test (FAT) only
for the SCS.
6'. When prioritizing N-IO delivery, deliver the N-IO hardware.
6. Deliver the hardware and software after they are confirmed by the users during FAT.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B2. Procedure for engineering> B2-3
7'. When prioritizing N-IO delivery, calibrate the N-IO hardware that is installed on site.
7. Adjust the hardware and software that are installed on site through the system. When pri-
oritizing N-IO delivery, perform tests on the remaining items of the function inspection.
8. Hand over the system to the user after conducting a final Site Acceptance Test (SAT).
TIP iDefine can be used to create and test applications.

SEE
ALSO For more information about the engineering flow when using iDefine, refer to:
“n Engineering flow when using iDefine” on page C2-15

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B3. Guidelines for selecting an engineering method> B3-1

B3. Guidelines for selecting an

engineering method
The engineering method of the project should be selected based on one of the following
guidelines:
If a safety I/O list that is consistent with the SCS project exists, or if you are engineering by
using a newly created safety I/O list, the I/O list engineering method is recommended. Select
an I/O list engineering when you use iDefine as an engineering tool.
Also, when performing engineering for safety subsystem communication, select I/O list engi-
neering.
If a safety I/O list that is consistent with the SCS project does not exist, or if you are using a
SCS project that was created by using an SCS with RS original engineering, choose the RS
original engineering method instead.
TIP If you upgrade to version R4, the metered license is applied regardless of the engineering method that you
select.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B4. Example of ProSafe-RS system configuration> B4-1

B4. Example of ProSafe-RS system

configuration
This chapter describes the standard configuration of ProSafe-RS systems.

n ProSafe-RS basic configuration

The basic configuration of ProSafe-RS consists of SENG and SCS. The following figure illus-
trates an example of the basic configuration of ProSafe-RS consisting of one SENG and two
SCSs.
SCS and SENG are connected via control buses. Safety communication through control
buses allows data to be sent and received between SCSs.
In SCS, I/O can be expanded by increasing the number of I/O nodes.
In the following figure, each of two SCSs has a Safety Control Unit (CPU node) which is con-
nected to two Safety Node Unit (I/O nodes). I/O modules may also be installed in the CPU
node.

l Example of Vnet/IP system configuration

The following figure shows an example of the basic configuration of a ProSafe-RS system on
a Vnet/IP network.
SENG

Vnet/IP

Bus1 Bus2
L2SW L2SW Vnet/IP
Vnet/IP

SCSP2 SCSP2

CPU Node
(for Vnet/IP) ESB Bus

I/O Node

SCSP2: Safety Control Station to perform safety applications (for Vnet/IP)

SENG: PC for engineering functions like editing applications, downloading, tests and for maintenance.
L2SW: Layer 2 Switch

Figure B4-1 Example of a ProSafe-RS configuration

l CENTUM integration configuration

The structure of a ProSafe-RS connected with CENTUM projects is called CENTUM Integra-
tion Configuration.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B4. Example of ProSafe-RS system configuration> B4-2
Host computer

Ethernet

SENG ENG/HIS HIS

Control bus

SCS SCS FCS FCS

SCS: Control Station to perform safety applications

SENG: PC for engineering functions like editing applications, downloading, tests, and for maintenance.
FCS: Field Control Station to execute process control.
HIS: Human Interface Station
PC which provides interfaces for operators who monitor and operate the plant
ENG: PC installing CENTUM engineering function

Figure B4-2 CENTUM integration configuration

• For CENTUM Integration Configuration, both FCS and SCS can be operated and moni-
tored from HIS.
FCS can read or write data in SCS via Control bus. But the SCS is designed so that its
safety function is not affected even when data is written by FCS.
• SCS engineering is performed from SENG. FCS and HIS engineering is performed from
ENG. Engineering of CENTUM integration function is performed from both SENG and
ENG.
SENG functions, ENG functions and HIS functions can be installed in several PCs as well
as to the same PC.
• The Exaopc OPC interface package of CENTUM (for installation on HIS) on HIS enables
a host computer for production management, to access the data of FCS and SCS by us-
ing the OPC Interface.
Moreover, using the ProSafe-RS SOE OPC interface package allows access to SOE in-
formation in SCS from the host computer.
• As a type of the CENTUM Integration Configuration, it is possible to connect only HIS
function to ProSafe-RS.
In this case, the structure is the same as in the previous figure without FCS.
• SENG is connected to control buses in CENTUM integration configuration. In addition,
SENG, HIS and ENG terminals are connected via Ethernet.

n Structure of connection with other systems

The SCS supports the Modbus slave communication function, subsystem communication
function, safety subsystem communication function, and DNP3 communication function as
functions for connecting with other systems. The Modbus slave communication function, sub-
system communication function, and DNP3 communication function are interference-free
functions. Safety subsystem communication is a safety communication but includes partially
interference-free communication.
Connections with other systems are realized by installing communication modules in the SCS
nodes. Application logic that is created for the communication functions of the Modbus slave

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B4. Example of ProSafe-RS system configuration> B4-3
communication function, subsystem communication function, and DNP3 communication func-
tion cannot be used in safety loops.
The functions and configurations for connection are as follows.
• Modbus slave communication function
In this configuration, an external system acts as an Modbus master and the SCS acts as
a Modbus slave. You can, for example, construct an operator interface in other system by
accessing data in the SCS from the other system that acts as the communication master.
You can make redundant Modbus slave communication by creating a user application on
the Modbus master.
Serial communication modules or Ethernet communication modules need to be installed
in the SCS nodes to be connected to other systems.
• Subsystem communication function
The subsystem communication function allows the SCS to act as the communication
master and communicate with other systems. The subsystem communication function of
the SCS supports Modbus protocol. By using the SCS that acts as a communication mas-
ter, you can read and set I/O data in the subsystems from the SCS. The subsystem com-
munication can be made redundant.
Serial communication modules or Ethernet communication modules need to be installed
in the SCS nodes to be connected to other systems.
• Safety subsystem communication function
The function within the safety subsystem communication function where the SCS serves
as the communication master and connects with field devices by using fire and gas com-
munication is referred to as the fire and gas communication function. This is a safety
communication function which connects field devices with the SCS via communication
modules and field wireless control stations, etc. Communication modules cannot be re-
dundantly configured.
Fire and gas communication modules are installed in SCS nodes to connect with field de-
vices.
• DNP3 slave function
The function using the DNP3 open protocol wherein the SCS operates as a DNP3 slave
and communicates with a DNP3 master such as SCADA is referred to as the DNP3 slave
function.
The Ethernet communication module is installed in SCS nodes to connect to the DNP3
master.
The following figure shows an example of connection.
SENG

Other system
(higher level system)

Control bus

SCS
Other system
(safety subsystem) Modbus slave communication
(Serial communication, Ethernet
communication)

Other system
(subsystem)
Subsystem communication
Fire and Gas (Serial communication, Ethernet
communication communication)

Figure B4-3 Connection with systems except CENTUM

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B4. Example of ProSafe-RS system configuration> B4-4

n Stand-alone SCS configuration

You can construct a stand-alone SCS configuration system environment without connecting to
the Vnet/IP network when operating the SCS. The SCS and SENG can be connected tempo-
rarily via network while performing engineering and maintenance. The following figure shows
a stand-alone SCS configuration system.
SCSP2
SENG Bus 1 side
Vnet/IP
Bus 2 side
CPU Node

Standby
Control
(for Vnet/IP)

L2SW
ESB bus

I/O
node

Figure B4-4 Stand-alone SCS configuration system

• Prepare an environment where an SENG can be connected to a stand-alone SCS for its
maintenance. When connecting an SENG in a stand-alone SCS configuration environ-
ment, connect it to the SCS via a Layer 2 switch (L2SW).
• For maintenance, you need to connect an SENG to the SCS. Use network cables that are
long enough for connection of the SENG.

IMPORTANT
• System status and errors should be notified by outputting them on a hardware-wired pan-
el, or should be checked on the SCS State Management window on a connected SENG.
• In order to enable outputs automatically without using an SENG after turning on the pow-
er of the SCS, it is necessary to use SYS_STAT to perform the output enable operation
from the application logic. The output module status is available through parameters such
as the NRO parameter of SYS_IOALLST.
• While operating in a stand-alone configuration, the SCS itself becomes the Vnet/IP time
master and its time may gradually deviate from the absolute time. Check the system time
and adjust it accordingly when the SCS is connected to an SENG for maintenance and so
forth.
• In a stand-alone SCS configuration system, do not turn on the power to the SCS when
the battery of the CPU module has run out. If you do so, the date setting in the SCS will
be changed to January 1st, 1970.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B4. Example of ProSafe-RS system configuration> B4-5

n Size of system
The number of maximum connectable stations in the system which consists of ProSafe-RS
stations only and in ProSafe-RS integrated with CENTUM system is shown below respective-
ly.Each system can be expanded as follows:

l Number of stations (ProSafe-RS integrated with CENTUM)

• Connectable control bus: V net or Vnet/IP
• Domains that can be connected: 16
• Stations that can be connected in a domain: 64
• Stations that can be connected: 256
• Hierarchy: three-level hierarchy (three levels of control bus) (Up to two BCVs or two pairs
of CGWs)
For HIS, 16 stations/domain at maximum.
For multiple domains, system generation function of CENTUM is required. In addition, V net
requires BCVs and Vnet/IP requires Layer 3 switches.

l Number of stations (consists of only ProSafe-RS stations)

• Connectable control bus: V net or Vnet/IP
• Number of domain: 1
• Stations that can be connected in a domain: 64
A system consisting of only ProSafe-RS stations cannot be configured as a multiple-domain
system. Only single-domain configuration is supported.

l Vnet/IP domain connection specifications (when integrated with CENTUM)

Connect between Vnet/IP domains with a Layer 3 switch (L3SW) on each bus. This also re-
quires the CENTUM system builder function.
• Number of connectable domains: 16 (Total of Vnet/IP domains and V net domains)
• Number of Layer 3 switches (L3SW) allowed: 15 levels

l Connection specifications in a Vnet/IP domain (when integrated with

CENTUM)
• Number of connectable Vnet/IP stations: Max. 64 (Vnet/IP stations including V net rout-
ers)
• General-purpose Ethernet communication devices: Max. 124 (PCs, Routers, etc.)
• Distance between stations in a Vnet/IP domain: Max. 40 km
• Distance between Layer 2 switch and a station: Max. 100 m (for Unshielded Twisted Pair
(UTP))
• Distance between Layer 2 switches: Max. 5 km (for fiber-optic cable)
• Number of connectable Layer 2 switches in a domain: Max. 7 per each Bus. (Multilayer
by cascade connection allowed)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B5. System reaction time> B5-1

B5. System reaction time

This section describes Reaction Time and PFD Calculation.

n System reaction time

The system reaction time of SCS consists of the reaction time for the external demand (De-
mand reaction time) and the reaction time when a fault is detected in the SCS (Fault reaction
time).
• Tr: system reaction time
• Tscan: scan period for application logic execution

l Demand reaction time

The demand reaction time differs as follows, depending on whether the loop includes safety
communication.
• When not using the inter-SCS safety communication

Sensor SCS Actuator

Figure B5-1 Reaction time 1

Tr = Tscan x 2 + Input processing time + Output processing time-Idle time

Idle time = Tscan - Application logic execution time
The output module processing time is shown in the following table.

Table B5-1 Output response time of the output module

Output module Output response time
SDV531 30 ms
S2MMM843 110 ms for AO mode (90% response)
30 ms for DO mode
S2MDV843 30 ms

• When using the inter-SCS safety communication

When using the inter-SCS safety communication, the calculation formula varies depend-
ing on the relation between the scan periods of producer SCS and consumer SCS.
• If Tscan on the producing side > Tscan on the consuming side:
Tr = Tscan on the producing side x 2 + Tscan on the consuming side x 2 + transmis-
sion delay
• If Tscan on the producing side ≤ Tscan on the consuming side:
Tr = Tscan on the producing side x 2 + Tscan on the consuming side x 3 + transmis-
sion delay
Transmission delay (For Vnet)
• No BCV/CGW used: 10 ms
• BCV/CGW used: number of BCV used x 50 ms + number of pairs of network levels
via CGWs x 500 ms
Transmission delay (Vnet/IP)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B5. System reaction time> B5-2
Table B5-2 Transmission delay in the case of Vnet/IP
Range Mandatory values
Within a Vnet/IP domain 10 ms
Between Vnet/IP domains without a wide area con- 50 ms (Regardless of the number of L3SWs)
nection (*1)
Between Vnet/IP domains with a wide area connec- 250 ms (Regardless of the number of L3SWs and
tion existence of WAC routers)
If the Vnet/IP domain and V net domain are connec- Number of the hops of V net router x 50 ms
ted using a V net router
*1: Connecting two domains through wide-area network is called "wide area connection."

Inter-SCS
Safety
communication
Sensor SCS SCS Actuator

Figure B5-2 Reaction time 2

• When using SCS link transmission safety communication

Tr= Sender Tscan x 2 + Receiver Tscan x 2 + Transmission Delay
Transmission Delay: 100 ms
• When fire and gas communication is being used
The demand reaction time is the total value of the following items (1) through (6):

Table B5-3 Demand reaction time when fire and gas communication is being used
Item Description
(1) Time until GS01 detects the gas con- Refer to the GS01 User Manual.
centration
(2) SCS reaction time SCS reaction time = Tscan x 2 + Input processing time + Out-
put processing time - Idle time
Input processing time = 100 ms (for S2LP131)
Idle time = Tscan - Application logic execution time
(3) Time until communication between 5 seconds. This time includes the 1 second for switching of
S2LP131 and YFGW410 is restored after YFGW410 to be completed.
control rights of a redundant YFGW410 is In the following cases, this time will be 0 seconds:
switched over • When YFGW410 is of a single configuration
• When assuming that detection of gas and switching of
YFGW410 will not occur at the same time
(4) PROFIsafe communication time from 8 seconds is recommended.
the SCS to GS01
(5) PROFIsafe communication time from Always 2 seconds.
GS01 to the SCS
(6) SCS reaction time Same as the description for (2).

l Fault reaction time

How to calculate the fault reaction time of the ProSafe-RS system is shown as follows:
• In the case of faults within the Safety Control Station
Basically, fault reaction time (maximum) is calculated by the following formula:
Tr = (Fault detection time) + Tscan × 2 + Output module processing time - Idle time
In the formula, the maximum value (of fault detection time) is as follows for each module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B5. System reaction time> B5-3
Table B5-4 Fault detection dime of each I/O module
I/O module types Fault detection time
SDV144, SDV521, SDV531, 520 ms
SDV526, SDV541, SDV53A
SAI143, SAI533 600 ms
SAV144 1360 ms
SAT145, SAR145 2100 ms
S2MMM843 600 ms for AI mode, AO mode
520 ms for DI mode, DO mode
S2MDV843 520 ms

The fault reaction time for the fault in communication between CPU module and output
module is shown in the following formulas:
• Tr = 1 s (Tscan =< 250 ms)
• Tr = Tscan x 2 + 0.5 s (Tscan > 250 ms)
After the time (Tr above) passed since the faults, the output module outputs the fail safe
value.
• For failures involving a field device or wiring
You need to enter the values specified in following table in the (fault detection time) of the
previously mentioned formula only when calculating the fault reaction time for the follow-
ing types of faults. Both are maximum values.

Table B5-5 Fault detection time of field wiring and devices

Type of Fault Module Fault detection time (Maximum)
Short circuit between channels SDV144, SDV521, SDV531, 1.46 s (*1)
SDV53A, SDV541
SAI533 0.6 s
Short circuit in output wiring (while SDV531, SDV541 1.46 s (*1)
outputting OFF signals)
SDV521 10 s (*1) (*2)
SDV53A 10 s (*1) (*3)
DO mode of S2MMM843, 1.6 s(*4)
S2MDV843
Open circuit SAT145, SAR145 1.5 s(*5)
DO mode of S2MMM843, 1.6 s(*6)
S2MDV843
Inputting the signal out of the SDV144 1.02 s (*7)
range
DI mode of S2MMM843, 1.02 s (*7)
S2MDV843
Open circuit or short circuit with SDV526 302 s
the power supply line (while send-
ing OFF signal)
Overload of field device SDV526 1.5 s
*1: Can be detected only when the pulse test is enabled.
*2: Value for style S3 and above.
*3: Value for style S2 and above.
*4: Can be detected only when low voltage pulse test (on) is enabled.
*5: Can be detected only when burnout detection is enabled.
*6: Can be detected only when detect disconnection and low voltage pulse test (on) is enabled.
*7: This value applies when the modules are in dual redundant configuration. The value for non-redundant configuration is 520
ms as noted in the above explanation.

• Inter-SCS safety communication

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B5. System reaction time> B5-4
The reaction time while using inter-SCS safety communication is the timeout period that
is specified in the FB for inter-SCS safety communication.
Tr = OUTT + DLYT
• OUTT: Reception Interval Timeout value
• DLYT: Transmission Delay Timeout Value
• SCS link transmission safety communication
The reaction time while using SCS link transmission safety communication is the timeout
period that is specified for the receiver SCS.
Tr = OUTT + DLYT
• OUTT: Reception Interval Timeout value
• DLYT: Transmission Delay Timeout Value
• Fire and gas communication
The fault reaction time when fire and gas communication is being used is the total value
of the following items (1) through (3):

Table B5-6 Fault reaction time when fire and gas communication is being used
Item Description
(1) PROFIsafeWatchDogTime with com- 30 to 60 s
munication immediately prior to the gas
concentration being reflected onto the out-
put value of GS01
(2) PROFIsafeWatchDogTime with com- 30 to 60 s
munication after the gas concentration be-
ing reflected onto the output value of GS01
(3) SCS reaction time SCS reaction time = Tscan x 2 + Input processing time + Out-
put processing time - Idle time
Input processing time = 100 ms (for S2LP131)
Idle time = Tscan - Application logic execution time

SEE
ALSO For more information about setting OUTT and DLYT, refer to:
• “● Inter-SCS safety communication timeout settings” in “■ Precaution for engineering” in A7., “Inter-
SCS safety communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)
• “● Time out settings of SCS link transmission safety communication” in “■ Precaution for engineer-
ing” in A6.2, “Data structure and definition of the SCS link transmission” in Engineering Guide Vol. 2
(IM 32P01C20-01EN)

l Example of calculating the Fault Reaction Time (Tr)

Conditions:
Scan period of application logic
Idle time: 30%
DO module: SDV531 (output response time = 30 ms)
• Case 1 (Fault with the DI module)
Tr (max.) = 520 ms + 200 ms x 2 + 30 ms – (200 ms x 0.3) = 890 ms
• Case 2 (Communication fault between the CPU module and the output module)
Tr (max.) = 1 s (because Tscan < 250 ms)
• Case 3 (Short circuit fault between DI channels)
Tr (max.) = 1460 ms + 200 ms x 2 + 30 ms – (200 ms x 0.3) = 1830 ms

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<B5. System reaction time> B5-5

n PFD calculation
The average PFD (System PFDavg) of a system is calculated with the model in the following
figure.
System PFDavg = Sensors PFDavg + Controller PFDavg + Valves PFDavg

Sensor ProSafe-RS (Logic solver)

Transmitters Controller Valves

Figure B5-3 PFD calculation model

When the interval between proof tests is 10 years and the DIO module is used, the Controller
PFDavg is indicated as follows.
Controller PFDavg = 6.63×10 -6
Further information about PFD calculation is available on request.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C. Basics of creating applications> C-1

C. Basics of creating applications

This part describes the preparations common to all engineering methods of ProSafe-RS, the
procedures for creating applications for each engineering method, precautions, analysis tools,
and test methods in the following order:
1. Preparing the project
This section describes how to prepare the AD Server to create a new project for SCS en-
gineering and register the project in the AD Server.
2. Work flow for creating applications
The work flow to define I/O and creating applications differs depending on the engineer-
ing method used. This section describes the work flow and main points of creating appli-
cations for each engineering method.
3. Precautions when creating applications
This section describes the precautions when creating applications.
4. Procedures for generating a database
After creating the application, generate a database. This section describes the method
and precautions for generating a database.
5. Testing with the Safety Analyzer
After generating the database, test the application by using the Safety Analyzer. This sec-
tion describes the Safety Analyzer.
6. Simulation tests
Run tests using simulators if necessary. This section describes simulation tests.
7. Offline download to the system
Offline download the created application to SCS. This section describes the offline down-
load.
8. Output enable operation
After performing the output enable operation, values from the application are sent from
the output module. This section describes the enable output operation.
9. Target tests
The created application must undergo target testing. This section describes target tests.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1. Preparing the project> C1-1

C1. Preparing the project

After the preparation for the AD Server is complete, prepare the project. This section explains
the type of projects that need to be prepared and how to prepare them.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-2

C1.1 Type of project

ProSafe-RS has the following types of projects:
• AD project
It is a project for managing multiple RS projects in the AD Server.
• RS project
It is a project for managing multiple SCS projects. You can view the status of SCS proj-
ects which are included in the same RS project by using the SCS Maintenance Support
Tool.
• SCS project
It is a project that corresponds to a single SCS and is the smallest project unit.
The following figure shows the relationship between the actual SCS and each project type.

PC
(AD Server)

SENG

Network Configuration

SCS1 SCS2 SCS3 SCS4

SCS SCS SCS SCS

Project 1 Project 2 Project 3 Project 4
Projects
RS Project 1 RS Project 2

AD Project 1

SCS Maintenance Support Tool

User Display

Figure C1.1-1 Relationship between the actual SCS and each project type

For integration with a CENTUM system, a definition to associate the CENTUM Project with
SCS Project is required.
In addition to these projects, there are library projects where the engineering data can be
used as a library. You can also register library projects in AD projects.

n Relationship between SCS project and RS project

An SCS project is included in an RS project. One SCS project, which is always included in
one RS project, is not shared with another RS project. In addition, an RS project is not inclu-
ded in another RS project.

n Folder configuration of SCS project and RS project

The SCS projects that constitute an RS project are specified by the folder configuration.
• RS Project
A folder created in Windows Explorer

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-3
• SCS Project
A folder created by using the SCS Manager under an RS project folder. It is placed as
one folder.
Explorer
RS Project
MYRSPJT
SCS Project
SCSddss (*1)
Configuration Name
SCSddss
(*2)
YOKOGAWA_SCS
YOKOGAWA_Master (*3)

*1: The folder name must be identical to the SCS project name. (dd: Domain number, ss: Station number)
*2: This is a work database.
*3: This is a master database.

Figure C1.1-2 Folder configuration of SCS project and RS project

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-4

C1.1.1 AD project
It is a project for managing multiple RS projects. The engineering data of AD Suite is man-
aged per AD project.
I/O licenses are counted for all SCSs contained in the RS projects that are registered in one
AD project.
The following figure shows the relationship between the ProSafe-RS license project and the
AD project.
License project 1 License project 2 License project 1
for ProSafe-RS for ProSafe-RS for CENTUM VP

PC PC
(AD Server) (AD Server)

SENG PJTCOM SENG PJTCOM HIS PJTCOM

SCS1 SCS2 SCS3 SCS4 SCS5 SCS6 FCS1 FCS2 FCS3 FCS4

SCS SCS SCS SCS SCS SCS VP project 1

project 1 project 2 project 3 project 4 project 5 project 6
RS project 1 RS project 2 RS project 3
AD project 1 AD project 2

Figure C1.1.1-1 Relationship between the ProSafe-RS license project and the AD project

If the number of I/O points exceed the number of licenses, you will not be able to download
SCS projects to the SCS. Use the SCS information display function to check the number of
licenses.
SEE
ALSO For more information about the SCS information display function, refer to:
“■ Checking the usage status of I/O licenses” in F1., “Display SCS information” in Engineer's Reference
Manual (IM 32P04B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-5

C1.1.2 RS project
An RS project is a combination of several SCS projects in order to bundle engineering data of
SCS projects. Defining an RS project permits the collective monitoring of the status of the
constituent SCSs by using the SCS Maintenance Support Function.
You must register all RS projects that involve the SCSs to which a license of the same license
project is assigned in a single AD project.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-6

C1.1.3 SCS projects

You need to define one SCS project for each SCS. An SCS has an attribute and contains the
following databases:
• Work database (SCS database and source files)
• Master database (running SCS database and source files)

n SCS project attribute

An SCS project will be defined with the following three attributes.
The attributes of a project determine whether it can be downloaded to actual SCS and wheth-
er it can be tested by SCS simulation. However, a logic simulation test can be preformed for
any project regardless of its attribute.

l Default project
A new project created in the SCS Manager will be the default project. The default project
should be a project that has not been downloaded to the actual SCS. Engineering works for a
new project are always carried out on the default project.
Downloading to the actual SCS: Always use offline download
Testing by SCS simulation test: Available
After offline download to the actual SCS has been completed successfully, the attribute of the
project will change from Default Project to Current Project automatically.

l Current project
If the offline download to the actual SCS is completed successfully at least once, the attribute
of the project will change to Current Project.
Downloading to the actual SCS: Available
Testing by SCS simulation test: Unavailable

l User-defined project
The attribute of a project created by using the Test Project Creation Tool is User-Defined Proj-
ect.
SCS simulation tests cannot be run on the current project. To check the changes made to the
application through the SCS simulation test, copy the current project by using the Test Project
Creation Tool and test the changes using the copied project. Based on the scale of the
changes made, decide whether to make a copy after modifying the current project or modify
the project after copying.
Downloading to the actual SCS: Unavailable
Testing by SCS simulation test: Available
SEE
ALSO For more information about reflecting the changes made to a user-defined project in the current project, refer
to:
“■ Operations required after SCS simulation tests (user-defined project)” in 3.1.2, “Engineering proce-
dure after SCS simulation tests” in Test Function Guide (IM 32P04B30-01EN)

n Configuration of SCS project database

In ProSafe-RS, one SCS project is defined and managed for each SCS. The following data
are stored in each SCS project folder.
• Work Database (SCS database and source files to define SCS)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-7
• Master Database (Current SCS database and source files to define SCS)
In SENG, you can edit only one SCS project at a time by using SCS Manager. AD Organizer
is also used for I/O list engineering. You cannot open multiple SCS Managers on one SENG
at the same time.
You can use one SENG to edit the SCS projects that are stored on another SENG. However,
you cannot operate the same SCS project from several SENGs at the same time.
The following figure shows the configuration of an SCS project.

SENG

SCS Manager

Definition
Management Edit

SCS Project

Work Database Master Database Master Database

Save

Source Files Source Files

Validity Check

SCS Database Master Database SCS Database

Restoration

Validity Check Validity Check

Repair Database
Offline Download Master Database Offline Download
Online Change Download IOM Download
SCS

SCS Database

Figure C1.1.3-1 Configuration of SCS project

You can edit the work database of an SCS project by using SCS Manager. AD Organizer can
also be used for I/O list engineering. Once the editing is completed in AD Organizer, you need
to reflect it to the work database by using the RS Generation. The edited work database is
automatically saved as the master database in the SCS project of SENG when being down-
loaded to the SCS via offline download or online change download.
The Master Database Restoring Function deletes the SCS database being edited in the work
database and replaces it with the master one.
The Database Validity Check Tool is used to check the validity of the master database, work
database, and the SCS database that is downloaded to the SCS, and to eliminate any incon-
sistencies in the databases.

l Work database
SCS project and its files stored in SENG are called Work database. When applications are
stored after being edited using SCS Manager, Multi-Language Editor, or Builders, the Work
database is updated.
If [Build] is executed on the application and the application is downloaded to an SCS, the SCS
database in the SCS is overwritten with the SCS database of the Work database in SENG.
And a copy of the Work database is created in SENG as a Master database.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-8

l Master database
The master database refers to the running SCS database and a group of its base source file
group at the time when the SCS database is downloaded to the SCS via offline change down-
load or online change download.
The following engineering functions are related to the master database.
• Master database saving function
This function automatically saves the master database within an SCS project when the
SCS database is downloaded to the SCS via offline change download or online change
download, and retains it at all times in the SENG. Therefore you do not need to upload
the database from the SCS to SENG.
• Master database restoring function
This function is used to restore the contents of the master database to the work data-
base. This function can also perform offline download of the master database to an SCS.
The master database is also used to detect differences from the work database by both online
change download and Cross Reference Analyzer.
The master database saving function and master database restoring function allow the user
to perform the following operations.
• The user can perform monitoring based on the database running on an SCS regardless
of whether the work database is being modified or not.
• The user can save the SCS projects including the master database in external media
such as CD-ROM.
• Even if an SCS hardware failure occurs and a CPU module and/or input/output module
require replacement, the user can restore the SCS application by master database offline
download and IOM download.
• The user can restore the work database from the master database in order to cancel
changes made to the SCS project.

IMPORTANT
Do not edit the master database using Windows explorer.

SEE
ALSO For more information about the function for downloading the master database onto SCS, refer to:
• I4.3, “Master database offline download” on page I4-40
• F4., “Master Database Restoring Function” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about precautions for restoring an SCS project that was generated by RS generation
with AD Organizer of a revision earlier than R4.03.10, refer to:
“n Precautions for restoring an SCS project that was generated by RS generation with AD Organizer of
a revision earlier than R4.03.10” on page C3-2

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.1 Type of project> C1-9

C1.1.4 Library project

A library project is a project database that can be used as a library independent of the specific
SCS. Library projects can be used for creating application logics and can be debugged only
by a logic simulation test. (An individual library project cannot be tested by SCS simulation
test or by target test for debugging.)
The functions and function blocks that are used among two or more SCSs can be created as
library projects and be copied to each SCS project.
When engineering by using iDefine, library projects cannot be used.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-10

C1.2 Procedures for creating projects

Follow these steps to prepare the project data. Use the same steps for both the RS original
engineering method and the I/O list engineering method.
1. Set the location of ADMDB by using the ADS Administration Tool.
2. Create an AD project by using the ADS Administration Tool.
3. Configure the user management and access control by using the ADS Administration
Tool.
4. Connect to the AD project by using the ADS Administration Tool.
5. Create an RS project folder by using Windows Explorer.
6. Register the RS project to the AD project by using AD Organizer.
7. Create an SCS project by using AD Organizer.
TIP When creating an SCS project, you select a station type and an engineering method. You cannot change the
engineering method later.

SEE
ALSO For more information about ADMDB location configuration, refer to:
C1.1.4, “Setting the location of the ADMDB” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about creating AD projects, refer to:
C1.2.1, “Creating and deleting AD projects” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about configuring user management and access control, refer to:
C1.2.2, “Controlling access to AD projects” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about procedures to connect AD projects to the AD Server, refer to:
C1.2.1, “Connecting to AD projects” on page C1-11
For more information about creating RS projects, refer to:
C1.2.2, “Creating RS projects” on page C1-12
For more information about procedures for registering RS projects in an AD project, refer to:
C1.2.3, “Registering RS projects in the AD project” on page C1-13
For more information about SCS project creation procedure, refer to:
C1.2.4, “Creating SCS projects” on page C1-15

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-11

C1.2.1 Connecting to AD projects

After you complete the project registration, user management, and definition of access control
on the AD Server, you must configure the settings for connection from AD Organizer to the
AD project.
You need to perform the following procedure for setting:
1. Start AD Organizer.
When AD Organizer is started for the first time, the Select AD Project dialog box appears.
2. When AD Organizer is not started for the first time, select [File] > [Change AD Project]
from the menu bar on AD Organizer.
The Select AD Project dialog box appears.
3. Enter the computer name or IP address of the AD Server, and then click [Connect].
A connection is established to the specified AD Server and a list of AD projects that are
found on the corresponding AD Server is displayed.
4. Select the target AD projects, and then click [Save Settings].
If a logged-in user of AD Organizer is registered in the target project, the connection re-
quest succeeds, the Select AD Project dialog box closes, and the project information is
displayed in AD Organizer.
SEE
ALSO For more information about project registration with AD Server, refer to:
“● Project registration” in “■ Server processing and status of the ADMDB at the time of the ADMDB loca-
tion setting” in C1.1.3, “ADMDB location setting” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about defining user management and access control with AD Server, refer to:
C1.2.2, “Controlling access to AD projects” in Engineer's Reference Manual (IM 32P04B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-12

C1.2.2 Creating RS projects

When you install ProSafe-RS software, a folder for an RS project is automatically created.
You can also create another RS project.
You need to set the folder of the RS project as a shared folder.

n Initial status of RS projects

When you install ProSafe-RS software, one RS project is automatically created as the "C:\RS-
Projects\MYRSPJT" folder. When this folder is used as is, you do not need to create a new
RS project.

n Creation of new RS projects

It is possible to create new RS projects in addition to the RS project created at the installation.
In this case, use Windows Explorer to create a folder with the name of new RS project. The
folder name is used as the name of the RS project. The following restrictions apply to the fold-
er name.
• Folder name: Up to 8 characters, starting with an upper case alphabet character
• Characters that can be used: Upper case alphabet characters, numerals, underscore and
hyphen.
• Absolute path of the folder: Up to 16 characters (except for \, /, :, ;, *, ?, " , <, >, |, . and
space)

n Operations when sharing an RS project

You need to specify the automatically created RS-Projects folder of C:\RS-Projects as a
shared folder, or create an RS project under a shared folder.
If you create an RS project under a shared folder, you need to use Windows Explorer to cre-
ate a folder by using the same name as the name of RS project to be created. The folder
name is used as the name of the RS project. The specifications regarding string and number
of characters are as follows:
• Folder name: Up to 8 characters, starting with an upper case alphabet character
• Characters that can be used: Upper case alphabet characters, numerals, underscore and
hyphen.
• Absolute path of the folder: Up to 16 characters (except for \, /, :, ;, *, ?, " , <, >, |, . and
space)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-13

C1.2.3 Registering RS projects in the AD project

After creating a folder of RS projects, you can use AD Organizer to register RS projects in the
AD project.
You must register all RS projects that involve SCSs to which a license of the same license
project is assigned in the same AD project. This registration enables you to correctly count
the number of I/Os in the scope of the ProSafe-RS license project. After registering the RS
project to an AD project, do not copy, move, or delete the RS project using Windows Explorer.
In addition, make sure to use AD Organizer when you create a backup of the RS project.
You need to perform the following procedure to register RS projects in the AD project:
1. Start AD Organizer.
2. On the System Structure Navigator, select [Register System Project] from the sub menu.
The System Project Registration dialog box appears.

Figure C1.2.3-1 Project registration screen

3. Configure the settings as follows:

System type Select ProSafe-RS.
Project A folder that is created for RS projects is displayed. You cannot configure
the settings.
Location Set the location of RS projects.
4. Click the [Register] button.

n Editing RS project properties

You need to perform the following procedure to edit the properties of the RS project:
1. Select the RS project displayed on the System Structure Navigator and select [Proper-
ties] in context menu.
The Properties tab appears.
2. Edit items.
3. Click the [OK] button.

n Unregistering RS projects
You need to perform the following procedure to unregister RS projects:
1. In the System Structure Navigator, select the RS project.
2. From the sub menu, select [Unregister System Project].
The RS project in the AD project is unregistered.

n Reflecting the changes in RS projects to the data in AD Organizer

The settings such as RS project definition and station are edited in SCS Manager and saved
in ADMDB and RS project database. After registering or unregistering an RS project or editing

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-14
its properties, you need to perform the following operation to update the system information of
System Structure Navigator in AD Organizer.
• From the menu bar of AD Organizer, select [View] > [Refresh].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-15

C1.2.4 Creating SCS projects

You need to start SCS Manager from the System Configuration Navigator of AD Organizer
and use the new SCS project creation function to create a new SCS Project.
The generated information is stored in the RS project database and ADMDB. In AD Organiz-
er, when the update is done by using the System Structure Navigator, the latest status ap-
pears.

n SCS project creation procedure

This section describes the procedures to create an SCS project.
To create a new SCS project, launch SCS Manager from AD Organizer and configure the fol-
lowing settings:
Do not use Windows Explorer functions to copy or move the SCS projects that you have cre-
ated.
1. Setting an SCS project folder
Set a folder in which to store the SCS project data.
2. Setting SCS project items
Set Domain number and Station number etc. of the SCS project. Some of the items can
only be specified in the process of creating a new SCS project and others can be
changed later.
3. Setting a resource
A resource refers to a set of SCS application logics. In this step, the resource name and
resource number are specified. In ProSafe-RS, one resource can be set for one SCS.
4. Setting a configuration
A configuration refers to a software object corresponding to one SCS. The configuration
name is specified in this step. In ProSafe-RS, one configuration can be set for one SCS.
A configuration includes a resource.
5. Setting an IP address
Specify an address related to TCP/IP communication of the SCS.

l Setting an SCS project folder

Follow these steps to create an SCS project:
1. From AD Organizer, start SCS Manager and select [File] > [New Project/Library] from the
menu bar.
The New dialog box appears.
2. Enter the following details:
Destination folder: Folder where the SCS project is saved
Name: SCS project name SCSddss
dd denotes Domain number, and ss denotes Station number.
Comment: 64 characters or less
Template: SCS_Default_Target
The path to the SCS project folder cannot contain the following characters:
Space, \, /, :, ;, *, ?, “, <, >, |, .
SEE
ALSO For more information about details on SCS project folder settings, refer to:
"Working with projects" in "Workbench" in the Workbench User's Guide

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-16

l Setting SCS project items

When the SCS project folder has been configured, the SCS Project Properties dialog box ap-
pears. Configure the settings related to the SCS and project on the [SCS] tab and the [Proj-
ect] tab of this dialog box.
In the SCS Project Properties dialog box, the [I/O List Engineering] check box appears. This
check box becomes available when you select a Station Type to which I/O list engineering is
applicable. If you select the check box, the I/O list engineering is applied. If you create an
SCS with this check box clear, RS original engineering is applied. You cannot change the en-
gineering method later.
SCSP1/SCSP2/SCSP3/SCSU1 can be a target of I/O list engineering.
When the system is integrated with CENTUM, specify a CENTUM project folder on the [Proj-
ect] tab.

l Setting a resource
A resource refers to a set of application logics created by the user. Multiple programs can be
run in one resource. Only one resource can be run in one SCS.
Right click the resource on Link Architecture View and then choose [Properties] from the pop-
up menu so as to display the Resource Properties dialog box. The resource name and the
resource number can be defined on the General tab. Specify "SCSddss" for the resource
name and "ddss" (dd: domain number, ss: station number) for the resource number.
SEE
ALSO For more information about details on resource settings, refer to:
"Resources" in "Link architecture view" in "Workbench" in the Workbench User's Guide

l Setting a configuration
In order to execute an application logic set, it is necessary to specify the hardware configura-
tion of each SCS.
Right click the configuration on Hardware Architecture View and then choose [Properties]
from the pop-up menu so as to display the Configuration Properties dialog box. The configu-
ration name can be defined on General tab.
Specify "SCSddss" (dd: domain number, ss: station number) for the configuration name.
SEE
ALSO For more information about details on configuration settings, refer to:
"Configuration properties" in "Hardware Architecture View" in "Workbench" in the Workbench User's
Guide

l Setting an IP address
The IP address can be defined on Hardware Architecture View. Double click "Connection" so
as to display Connection - Properties dialog box. The IP address needs to be set for "Value"
item.
In the standard, the IP address sets "172.16.dd.ss" (dd: domain number, ss: station number).
SEE
ALSO For more information about details on IP address settings, refer to:
"Connections" in "Hardware Architecture View" in "Workbench" in the Workbench User's Guide

l Setting SCS constants

Specify constant values for SCS and parameters for communicating with external systems in
SCS Constants Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-17

C1.2.5 SCS Project Properties dialog box

The SCS Project Properties dialog box is used to make various basic settings for an SCS, in-
cluding domain number and station number.

n Calling the SCS Project Properties dialog box

The SCS Project Properties dialog box appears if you perform the following operations in
SCS Manager.
• When a new SCS project is created
The SCS Project Properties dialog box appears automatically when the SCS project fold-
er settings are completed.
• When a menu is selected from the Engineering launcher menu of SCS Manager
To edit an SCS project after it is created, select [Engineering] from the [Tools] menu of
SCS Manager. The Engineering launcher menu appears; select [SCS Project Properties].

n Components of the SCS Project Properties dialog box

The SCS Project Properties dialog box has the following components.

l SCS tab
SCS Project Properties [Pjt: SCS0101]

SCS Project

Type
Station Type: S2SC70D-S Duplexed Safety Control Unit

Database Type: General-purpose

Station Address
Domain Number: 1

Station Number: 1

Network Parameters
IP Address: 172.16.0.0

Component Number: 1

I/O List Engineering

Import Export OK Cancel

Figure C1.2.5-1 SCS tab

The table below shows the components of the "SCS" tab.

Table C1.2.5-1 Setting items in the "SCS" tab

Item Setting (*1) Description
Only possible
when a new
Station Type Specify the model of the SCS station.
project is cre-
ated
Database Type Display only Database type is displayed.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-18
Table C1.2.5-1 Setting items in the "SCS" tab (Table continued)
Item Setting (*1) Description
Select the check box to allow setting the domain number and station
number.
Station Address Yes The check box is selected by default when a new project is created.
The check box is not selected by default when this dialog box is
opened from the Engineering launcher menu.
Specify the domain number. Select a value using the spin box or enter
Domain Number Yes a character string directly. A value in the range from 1 to 31 can be
specified.
Specify the station number. Select a value using the spin box or enter
Station Number Yes a character string directly. A value in the range from 1 to 64 can be
specified.
IP Address Display only The IP address set in Hardware Architecture View is displayed.
Component Num- Enter the component number. (*2) Up to 4 characters, which can be
Yes
ber any alphanumeric characters, can be entered.
You can con-
figure the set-
I/O List Engineer-
tings only Specify whether to use the I/O list engineering method
ing
when creating
a new project.
*1: Yes: Setting possible
*2: This is a number assigned to identify the devices belonging to an RS project. It is assigned when installing an SCS in a cabi-
net, etc., and used to show the connection origin and destination of each cable when wiring cables.

IMPORTANT
• Make sure to specify the station type and engineering method when creating a new SCS
project. They cannot be changed later.
• After you have defined the station address (domain number and station number), try not
to change it if possible. Changing the station address deletes the master database.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-19

l Project tab
SCS Project Properties [Pjt: SCS0101]

SCS Project

SCS Project database

Version:

CENTUM Connection
CENTUM Project Folder: Browse...

SCS Project Current Project

Originally Created: R3.02.10

Import Export OK Cancel

Figure C1.2.5-2 Project tab

The table below shows the components of the "Projects" tab.

Table C1.2.5-2 Setting items in the projects tab

Item Setting (*1) Description
The version number is displayed if the versions of the project data are
Version Display only maintained. The field is blank in the case of an SCS project that has
never been checked in with Version Control Tool.
Specify the top folder of the CENTUM project. Enter the path directly or
specify the path from the Folder Selection dialog box that is displayed
CENTUM Project
Yes by clicking [Browse]. (*2) (*3)
Folder
This is valid only when a license for the CENTUM VP Integration Pack-
age has been assigned to the PC.
Displays SCS project attribute.
SCS Project Display only
Project Attribute: Default Project, Current Project, User-Defined Project
Display only Displays the software revision number of the SENG that the project was
Originally Created
(*4) created from.
*1: Yes: Setting possible
*2: If the entire length of the specified path cannot be displayed in the text edit box, the middle part of the path is omitted and
displayed as [...].
*3: A path specified in the local drives format is automatically converted to a path in UNC format.
*4: If the project was created in SENG with a software revision number prior to R1.03, the software revision number cannot be
displayed.

TIP SCS Project Properties dialog box is available for both SCS project and Library project. It differs in the SCS
project properties dialog box of Library project as follows:
• This dialog box will not automatically start when the project is newly created.
• When started from SCS Manager, only "Project" tab will be displayed.
• There is no need to specify [CENTUM Project Folder].
• [Default Project] will be displayed as SCS Project.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-20

C1.2.6 SCS Constants Builder

SCS Constants Builder is used to specify constant values for SCS and parameters for com-
municating with external systems.

n Calling SCS Constants Builder

Choose [Engineering] from [Tools] menu of SCS Manager. The Engineering launcher menu
appears; select [SCS Constants Builder] and launch SCS Constants Builder.
Menu Bar Toolbar

SCS Constants Builder - [Pjt:SCS0101 File:StnDef-i.edf]

File Edit View Tool Window

Interval of SCS Communication

Repeated

Interval of Repeated Warning Alarms 600 sec.

Synchronous Mode V net

Scan Period for External System 1 sec.

Modbus Word Order Direct

16-bit Modbus Master Support Mode Disable

Alarm Notify Action when AOF Released No

PV Status of S_ANLG_S Yes

Ready

Data Menu Area Workspace

Status Bar

Figure C1.2.6-1 Communication tab of SCS Constants Builder window

SCS Constants Builder contains the following tab sheets:

• SCS tab
For setting parameters related to Optical ESB Bus Repeater
• Communication tab
For setting parameters related to communication with external systems
SEE
ALSO For more information about menu bar, toolbar, data menu area, and message display area, refer to:
A3.1, “Window components common to builders” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

n SCS tab
On the SCS tab, you can set the following items:

l Optical ESB Bus Repeater: SCSV1/SCSP1

Select [Yes] if you use the Optical ESB Bus Repeater. [No] if not. The initial setting is [No].

l Maximum Extension Distance: SCSV1/SCSP1

Set the Maximum Extension Distance for the Optical ESB Bus Repeater.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-21
If Optical ESB Bus Repeater is set to [Yes] for SCSP1, the maximum distance can be set
within the range from 5 to 50 km in 5 km units. If Optical ESB Bus Repeater is set to [Yes] for
SCSV1, [5 km] can be set. The initial setting is 5 km.

SCS Constants Builder - [Pjt:SCS0101 File:StnDef-i.edf]

File Edit View Tool Window

Maximum SCS Communication

Extension
5:5km
Optical ESB Bus Repeater
Optical ESB Bus Repeater Yes
Maximum Extension Distance 5

Items Changed by Online Change Download

Extend Scan Period Automatically No

Behavior at Abnormal Calculation SCS fails

Automatic IOM Download Disable
Device Power-Off Period 1 sec.

Ready

Figure C1.2.6-2 SCS tab of SCS Constants Builder

SEE
ALSO For more information about specifying the SCSP1 node extension distance, refer to:
Appendix 1.1, “Setting items for nodes” on page App.1-2

l Extend Scan Period Automatically

Select [Yes] or [No] to set whether to adjust the scan period of the application logic automati-
cally. The default setting is [No]. If set to [Yes], the scan period will be extended automatically
when the execution time of the application logic has extended the scan period specified on
the SENG for some reasons. This prevents the communication performed by the SCS, for ex-
ample, inter-SCS safety communication, from being discontinued. This setting is changeable
by online change download.
SEE
ALSO For more information about details on setting and checking the scan period of the application logic, refer to:
A7.2, “Automatic extension function for scan period of the application logic execution function” on page
A7-5

l Behavior at Abnormal Calculation

Select [SCS fails] or [SCS continues] to set the behavior of the SCS when an abnormal calcu-
lation has occurred in the application logic. The default setting is [SCS fails]. This setting is
changeable by online change download.
SEE
ALSO For more information about details on specifying the behavior at abnormal calculation, refer to:
G2.1.3, “Behavior at abnormal calculation” on page G2-7

l Locking of Internal Variables: SCSP2/SCSP3

You can select [Enable] or [Disable] to set whether to enable locking of internal variables that
are used in the application logic. This setting is displayed only when the SCS type is SCSP2
or SCSP3 and also [Extend Scan Period Automatically] is set to [Yes]. By default, it is set to
[Disable]. You can change this setting by online change download.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-22
SEE
ALSO For more information about details on locking internal variables, refer to:
“■ Locking internal variables” in F8.1, “Variable locking” in Engineer's Reference Manual (IM
32P04B10-01EN)

l Automatic IOM Download

Select [Enable] or [Disable] to set whether to enable automatic IOM download. The default
setting is [Disable]. This setting is changeable by online change download.
SEE
ALSO For more information about Automatic IOM download details, refer to:
“n Automatic execution of IOM download” on page I4-45

l Device Power-Off Period

This item is used to reset the Smoke and Heat Detector.
You can set the number of seconds until the power ON command is output from when the
function block HSDTR outputs a power OFF command. This is the number of seconds for
which the Smoke and Heat Detector is power OFF. This setting is changeable by online
change download.
• Setting range: 1 to 10 (seconds) (default: 1)
TIP This setting is displayed when using an SCS project newly created with a version of SENG that is R4.03.00 or
later. However, this is not displayed with SCSV1. When importing an SCS project created with a version of
SENG that is earlier than R4.03.00, an import error will occur with this item and the value will be set to 1.

l Device Startup Waiting Period

This item is used to reset the Smoke and Heat Detector.
You can set the number of seconds until startup is completed from when the power of the
Smoke and Heat Detector is turned ON. When there are multiple types of devices and equip-
ment in the station, enter the maximum number of seconds. This setting is changeable by on-
line change download.
• Setting range: 0 to 60 (seconds) (default: 0)
TIP This setting is displayed when using an SCS project newly created with a version of SENG that is R4.03.00 or
later. However, this is not displayed with SCSV1. When an SCS project created with a version of SENG that
is earlier than R4.03.00 is imported, this value is set to 0.

l Alarm Suppression During Device Reset

This item is used to suppress the alarm during the reset status of the Smoke and Heat Detec-
tor.
You can set whether or not to suppress the display of system alarms and process alarms
while the Smoke and Heat Detector is in the reset status. Set the value to [Enable] to sup-
press the display of system alarms and process alarms, or set the value to [Disable] to not
suppress the display. This item cannot be changed by online change download.
TIP This setting is displayed when using an SCS project newly created with a version of SENG that is R4.03.00 or
later. However, this is not displayed with SCSV1 and SCSU1. When an SCS project created with a version of
SENG that is earlier than R4.03.00 is imported, this value is set to [Disable].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-23
SEE
ALSO For more information about engineering for resetting the Smoke and Heat Detector, refer to:
A3.4.4, “Engineering regarding the device reset function and alarm suppression during device reset” in
Engineering Guide Vol. 2 (IM 32P01C20-01EN)

l Command Line
TIP Specify the command line with no more than 256 single-byte characters. If the command line is not set, the
default value is used for each applicable item. The format is as follows:
Item name = Data value, Item name = Data value, ...

• PSINITIM (Fire and gas communication startup time)

This item is the time required to initialize fire and gas communication during the SCS
start-up processing. Before the initialization of fire and gas communication is completed,
the data status of the data obtained by the communication is BAD. Therefore, specify this
time to delay the completion of the startup of SCS. This setting is applicable to SCS in
which one or more S2LP131 are defined.
The number entered here is the communication cycle for GS01. The conversion from the
GS01 communication cycle to the fire and gas communication startup time is implemen-
ted internally within the SCS.
The formula is as follows:
Fire and gas communication startup time (s) = 20 + (GS01 communication cycle + 8) x 4
When the GS01 communication cycle is 12 seconds, the fire and gas communication
startup time is 100 seconds.
• Format
PSINITIM=12
• Parameter
The configurable range is 8 to 30 seconds. The default value is 12 seconds.

n Settings with the Communication Tab

On the Communication tab, you can set the following items:

l Interval of Repeated Warning Alarms

This item should be set in the case of a CENTUM integration structure.
Set the time from the occurrence of a process alarm to the next occurrence of the same
alarm. Repeated warning alarms are intended to notify the engineer that serious process
alarms are existing continuously.
If the cause of an alarm still persists after a certain time has elapsed from the occurrence of
the alarm, the process alarm message is sent again, regardless of whether or not the alarm is
acknowledged.
The interval of repeated warning alarms can be specified in the range from 0 to 3600 sec-
onds. The initial setting is 600 seconds.
If 0 is specified for the interval of repeated warning alarms, repeated warning alarms are disa-
bled.

l Synchronous Mode
This item allows specifying the method of synchronizing system time. The time of the SCS is
used for the time stamps of messages recorded in SOERs.
For SCSV1, two options [IRIG-B] and [V net] are provided for time synchronization. The de-
fault is [V net].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-24
For SCSP1/SCSP2/SCSP3, it is Vnet/IP time synchronization.

Table C1.2.6-1 Time Synchronous Mode

Method Description
The time information is acquired from the externally installed GPS clock through IRIG-
IRIG-B time syn- B and set to the CPU and I/O module. The GPS clock and CPU nodes of all SCSs are
chronization connected by IRIG-B. Specify this option when highly accurate synchronization is re-
quired for discrete input module time between different SCSs.
V net time synchro- This method sets Vnet time to the CPU and I/O module. The Vnet time is also recor-
nization ded in SOER.
This method sets Vnet/IP time to the CPU and I/O module. The Vnet/IP time is also
Vnet/IP recorded in SOER. If the SNTP server is connected to Vnet/IP network, the Vnet/IP
time synchronizes with the SNTP server time.

l Scan Period for External System

Specify the scan period used when connecting to external systems such as CENTUM. The
scan period for external system setting refers to the operating period at which the connection
function is executed.
Select either 1 second or 2 seconds. Default: 1 second.

l Modbus Word Order

When establishing a connection with an external system and acquiring 32-bit data from the
external system, the order of the most significant word and least significant word can be
changed. Select either the order of the most significant word and then the least significant
word, or the reverse order. The reverse order is used generally in Modbus. [Direct] is selected
by default.
32-bit data
Most significant Least significant
word Word

Direct 40001 40002

Reverse 40002 40001

Figure C1.2.6-3 Modbus Word Order

l 16-bit Modbus Master Support Mode

This item specifies whether to allow the following accesses by the external Modbus master in
Modbus slave communications.
These accesses are allowed when 16-bit Modbus master support mode is set to [Enable]. By
default, it is set to [Disable].
• Write to a single holding register
Function code is 06.
• Read 16-bit data
Function codes are 03 and 04.
• Write 16-bit data
Function code is 16.

l Alarm Notify Action when AOF Released

This item should be set in the case of a CENTUM integration structure.
Specify to (or not to) output the suppressed messages when AOF is deactivated.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C1.2 Procedures for creating projects> C1-25
When you output the suppressed process alarm message, you need to set this setting to
[Yes], otherwise, you can set this setting to [No]. By default, this setting is [No].
SEE
ALSO For more information about activating/deactivating alarm suppression, refer to:
B8.2.5, “Alarm inhibition (AOF)” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

l PV Status of S_ANLG_S
This setting item is used for a CENTUM integration structure.
With this setting, whether to keep the PV status on the mapping block (S_ANLG_S) of
ANLG_S (Analog Input Block with Data Status) can be defined. If you want to have BAD data
status on the mapping block S_ANLG_S when the data status of IN terminal of ANLG_S
block is BAD, you need to set this setting to [Yes], otherwise, you can set this setting to [No].
By default, this setting is [Yes].

l The first number of annunciator messages with tag name

You can specify the first number of annunciator messages with tag name (%AN).
The numbers from the specified number up to the maximum number of annunciator messag-
es are used for annunciator messages with tag name.
However, if you specify 0 as the first number, all the numbers are used for annunciator mes-
sages instead of annunciator messages with tag name.
• For SCSP1/SCSU1: 0 to 1000
• For SCSP2/SCSP3: 0 to 2000
The initial setting is 0. It is not displayed in SCSV1.

l DNP3 Slave Function

When you use the DNP3 slave function, you need to set it to Enable, otherwise, you can set it
to Disable. By default, it is set to Disable.
TIP This setting is displayed only for the SCS projects of SCSU1 that are created by the software version
R3.02.20 or later. When the SCS projects that are created by the software prior to R3.02.20 are imported, this
setting is set to Disable.

n Change process alarm name of Analog Input Block with Data Status
The alarm name of the ANLG_S (Analog Input Block with Data Status) can be changed so as
to match the alarm name on the diagnosis information window and SOE Viewer with the
alarm name of CENTUM.
Before changing the alarm name, the CENTUM process alarm text strings need to be modi-
fied first. For more information about defining the process alarm text strings, please contact
Yokogawa agents.

IMPORTANT
When applying this feature, if the SCS project to be monitored on CENTUM contains both
ANLGI and ANLG_S blocks, the ANLGI blocks should be changed to ANLG_S blocks.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2. Work flow of creating applications for each engineering method > C2-1

C2. Work flow of creating applications

for each engineering method
After preparing the project, create applications by using the engineering functions.
The procedures for creating applications differ for each engineering method.
This chapter explains the engineering procedures and main points for each engineering meth-
od.
The engineering methods for ProSafe-RS is as follows:
• I/O list engineering
This is an engineering method that uses AD Organizer and SCS Manager, and can be
used together with iDefine as well.
When using the safety subsystem communication function, I/O list engineering can be
performed.
• RS original engineering
This is an engineering method that only uses SCS Manager.
For modifying the application, it is necessary to analyze any effects caused by the modifica-
tions in advance and take the required measures against the effects.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-2

C2.1 Work flow of I/O list engineering

This chapter explains the engineering flow of the I/O list engineering method. I/O list engi-
neering is used even when you use iDefine as an engineering tool. Read the following section
if you are using iDefine.
The following figure shows the engineering flow when using the AD Suite, SCS Manager, and
FieldMate Validator. This flow describes only the differences from the flow of RS original engi-
neering. By using FieldMate Validator, you can configure and adjust the I/O channels of uni-
versal type I/O modules without using the SCU.

ADS Administration Tool

Create an AD project

AD Organizer

Registration with SCS project Create an SCS project

Registration with AD project

Safety I/O list (*1) Creating an safety I/O

not yet fixed list (*1), RS generation Create application logic
(Reflection process)

Test using
logic simulator
Fixed
safety I/O list (*1)
Editing the safety I/O Modify the application
list (*1), RS generation and test it by using logic
(Reflection process) simulator

Test using
FieldMate Validator Download to the target
SCS

Target test

Importing the updated

Updated safety safety I/O list
RS generation Go back to the required
I/O list phase
(Build process of the
SCS project)

SAT

*1: In this figure, safety I/O list means the safety I/O list or safety communication I/O list.
Legends
: Safety I/O list or safety
Communication I/O list
: Engineering task

Figure C2.1-1 Engineering flow in AD Suite

SEE
ALSO For more information about operations that are necessary when using iDefine, refer to:
C2.2, “Work flow of I/O list engineering with iDefine” on page C2-11

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-3

n Engineering using a safety I/O list and safety communication I/O list
The safety application is a function element that can operate and control the plant in a safe
manner, and is built mostly by using application logics based on input/out variables.
You can start building an application logic with the I/O variables being reflected onto Diction-
ary View from a safety I/O list and safety communication I/O list as long as you do not use
iDefine as the engineering tool.

n Handling of the safety I/O list and safety communication I/O list
The user can use the safety I/O list or safety communication I/O list to make definitions based
on the P&ID tag name in the application, and proceed to build the application without having
to wait for the detailed design of I/O modules or data communication.
The required information varies depending on whether the I/O addresses are set in the safety
I/O list or safety communication I/O list.
When the I/O address is not set, the following information is required to create an application
logic by using the safety I/O list or safety communication I/O list.
• Information required for the safety I/O list
• P&ID tag name
• I/O type (AI, AO, DI, DO)
• I/O Tag
• Signal Type
• P&ID Group
Information required to reflect variables onto Dictionary View is as follows:
• P&ID tag name
• I/O type (AI, AO, DI, DO)
• I/O Tag
• Data Type
• P&ID Group
• Information required for the safety communication I/O list
• P&ID tag name
• I/O type (AI, AO, DI, DO)
• Signal Protocol
• I/O Tag
• P&ID Group
Information required to reflect variables onto Dictionary View is as follows:
• P&ID tag name
• I/O type (AI, AO, DI, DO)
• Data Type
• Signal Protocol
• P&ID Group
The type of the FB is decided as soon as the following information is decided:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-4
• I/O type (AI, AO, DI, DO)
• Signal Protocol
• Data Type
The P&ID tag name and the I/O type are mandatory to save the safety I/O list and safety com-
munication I/O list.
When a safety I/O list or safety communication I/O list that contains I/O addresses is read by
AD Organizer, IOM definitions are created by operating Create Node & IOM in IOM Definition
Editor. The required information is as follows:
• Information required for the safety I/O list
• SCS project name
• RS project name
• Node type
• Node number
• IOM category
• IOM type
• Unit number
• Slot number
• Terminal number
• Signal type
• Information required for the safety communication I/O list
• SCS project name
• RS project name
• Node type
• Node number
• IOM category
• IOM type
• Slot number
TIP Even in a situation where the IOM definitions are not yet complete, the user can perform the reflection proc-
ess in order to be able to define variables of safety I/O in POUs in the SCS project.

IMPORTANT
When using S2MMM843 or S2MDV843 in an explosion protection system, refer to Explosion
Protection (For ProSafe-RS) (TI 32S01J30-01E) without fail. The approved values of the ex-
plosion protection parameters are different depending on the type of signal.

l P&ID tag and P&ID group

The P&ID tag is a name that identifies an I/O point. The I/O points are identified by using the
P&ID tag as the key while defining the I/O information for each line in the safety I/O list. The
P&ID tag needs to be uniquely defined in the P&ID group.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-5
The P&ID group is the label name required for identifying the safety I/O list or safety commu-
nication I/O list. The P&ID group name is used as the file name that is created under the I/O-
List folder of the system configuration navigator of AD Organizer.

l I/O Tag
The I/O Tag is a name that identifies an I/O point. The I/O Tag needs to be uniquely defined.

n Engineering procedures for I/O design

This section describes the work flow for engineering regarding inputs/outputs.

Start

Define safety
YES NO
I/O list and safety
communication
I/O list first?

Create a new safety I/O list

and
safety communication I/O list Create new nodes and Create a new safety I/O list
I/O modules and safety communication I/O list

Define the safety I/O list

and
safety communication I/O list Define the nodes and Define the safety I/O list
I/O modules and safety communication I/O list

Save the safety I/O list

and safety communication
I/O list and check-in them Save the nodes and I/O Save the safety I/O list
modules and check-in them and safety communication I/O list
and check-in them

Create nodes and I/O modules

based on the safety I/O list and
safety communication I/O list

Save the nodes and I/O

modules and check-in them

End design I/O

Figure C2.1-2 Work flow for engineering regarding inputs/outputs

The safety I/O list and safety communication I/O list can be created before or at the same
time as an I/O module. By creating the safety I/O list and safety communication I/O list in ad-
vance, an application can be built alongside an I/O design.

n Editor and tools that are used for I/O list engineering
The following table shows the editors and tools used when performing I/O list engineering.
You can start the SCS Manager from the System Structure Navigator in AD Organizer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-6
Table C2.1-1 Editor and tools that are used in I/O list engineering
Category Operation Means to Editor or tool name Remarks
operate edi-
tors and
tools
SCS Man-
ager/AD Or-
ganizer
Safety ap- Safety logic definition SCS Man- Multi-Language Editor -
plication ager (*1)
Variables and parameters SCS Man- Dictionary View (*1) I/O variables are auto-
definition ager matically created from
the safety I/O list. Instan-
ces of subsystem com-
munication I/O FB, PRO-
FINET communication in-
put FB, and fire and gas
communication input FB
are automatically gener-
ated from the safety com-
munication I/O list. Inter-
nal variables and FB in-
stances can be defined
by iDefine.
I/O I/O list definition AD Organ- Safety I/O Editor The following information
izer Safety Communication is generated:
I/O Editor • Dictionary View
• I/O Wiring View
• I/O Parameter Builder
• Communication I/O
Builder
Node/IOM detailed defini- AD Organ- IOM Definition Editor The information for the
tion izer following is created:
• I/O Wiring View
• I/O Parameter Builder
System Creation of SCS projects SCS Man- SCS Manager The contents will be re-
ager flected in the AD Organ-
izer.
SCS project attribute SCS Man- SCS Project Properties
ager
SCS constant definition SCS Man- SCS Constants Builder -
ager
SCS parameter setting SCS Man- Hardware Architecture -
ager View
POU definition SCS Man- Link Architecture View -
ager (*1)
Safety communication SCS Man- Binding List View -
association ager
SCS Link transmission SCS Man- SCS Link Transmission -
data definition ager Builder
RS genera- Database generation AD Organ- RS Generation Manager -
tion izer
Authorize SCS Man- Integrity Analyzer -
ager
SCS Man- Cross Reference Ana- -
ager lyzer
Test Start test function SCS Man- SCS Manager (*1) -
ager
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-7
Table C2.1-1 Editor and tools that are used in I/O list engineering (Table continued)
Category Operation Means to Editor or tool name Remarks
operate edi-
tors and
tools
SCS Man-
ager/AD Or-
ganizer
Download Offline download SCS Man- SCS Manager -
ager
Online download SCS Man- SCS Manager -
ager
CENTUM Tag and annunciator defi- SCS Man- Tag Name Builder (*1) -
integration nition ager
Alarm definition SCS Man- ProSafe-RS Alarm Priori- -
ager ty Builder / Alarm Pro-
cessing Table Builder
MODBUS Definition of addresses of SCS Man- Modbus Address Builder -
communi- Modbus devices ager
cation
Subsystem Communication I/O data AD Organ- Safety Communication -
communi- definition izer I/O Editor
cation
Safety sub- Communication I/O data AD Organ- Safety Communication -
system definition izer I/O Editor
communi-
cation
DNP3 com- DNP3 slave definition SCS Man- DNP3 Communication -
munication ager Builder
*1: iDefine can be used as well.

n Procedure for I/O list engineering without iDefine

The procedure for building a safety application without using iDefine is described as follows.
The AD project is defined as a prerequisite.
1. Configure the I/O modules and I/O variables.
Import the safety I/O list or safety communication I/O list and then add or modify I/O varia-
bles by using AD Organizer. Define the I/O modules and I/O parameters as well.
2. When using the fire and gas communication function, define fire and gas communication
modules and fire and gas communication.
3. Select an SCS project and run Reflection.
4. Use the Multi-Language Editor and Link Architecture View of SCS Manager to create and
modify POUs for the safety application.
5. Create applications other than the application logic and generate the databases to down-
load to SCS.
6. Examine the created application by using Safety Analyzer.
SEE
ALSO For more information about details on how to create an application logic, refer to:
A., “Configuring application” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-8

n Creating a communication I/O list for a subsystem communication

module
For SCS projects created in R4.01 to R4.03.00, you must enable the setting items of the sub-
system communication modules to be handled in a safety communication I/O list.
SEE
ALSO For more information about how to create a safety communication I/O list, refer to:
“n Communication I/O List Output Tool” on page App.3-15

n Engineering for fire and gas communication modules

Engineering for fire and gas communication modules can be implemented with I/O list engi-
neering only.
Fire and gas communication modules are used for safety communication with Gas Detector
GS01 from GasSecure AS. The following figure shows an example of device configuration.

AD Server

Ethernet
SENG
(SCS Manager,
HIS/ENG
AD Organizer,
PROFINET Configurator)
Vnet/IP

S2LP131 SCS (SCSP3)

(single)

FWMC

Layer 2 switch Field network

(PROFINET) (*1)
Layer 2
switch Ethernet

YFGW410 YFGW410

Field wireless backbone network

YFGW510 YFGW510

Field wireless network

(ISA100.11a) (*1)

GS01 GS01 GS01

Fire and gas communication

(PROFIsafe) (*1) GS01 Configurator

*1: For fire and gas communication, PROFINET is used as the field network between SCS and YFGW410 and
ISA100.11.a as the field wireless network. In addition, the PROFIsafe protocol is used for the safety layer of
fire and gas communication.

Figure C2.1-3 Example of system configuration using fire and gas communication modules

Fire and gas communication modules can be defined with Safety Communication I/O Editor
and used in SCS projects of SCSP3.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-9

l Overall flow of engineering for fire and gas communication

The following figure shows the flow of engineering for fire and gas communication.

ProSafe-RS Engineering Field Wireless Network Wireless Field Device

(AD Suite, SENG) Engineering Set parameters
(FWMC) (GS01 Configurator)

System Design

Create AD project,
RS project,
SCS project
Wireless Configuration and
Device Provisioning•Parameter
Download
File Settings
to YFGW410
Create S2LP131
Provisioning
File
GSDML
file Create safety Set up of
communication Wireless - YFGW510
I/O list PROFINET
Mapping File
Device installation
Reflect to SCS project
from AD project YFGW410, YFGW510
Installation

Create application logic

Build SCS project

Offline Download Check and adjust

to Host system wireless connection

Check and adjust

Wireless network
connection

Loop check

Operation /
Device Management / Maintenance

Figure C2.1-4 Flow of engineering for fire and gas communication

The following engineering is required to build a system for fire and gas communication:
• Engineering for SCS
• Engineering for a field wireless network
• Engineering for wireless field devices

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.1 Work flow of I/O list engineering > C2-10
SEE
ALSO For more information about details of ProSafe-RS engineering, refer to:
E1.5, “Engineering for fire and gas communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-11

C2.2 Work flow of I/O list engineering with

iDefine
In the case of I/O list engineering, you can use iDefine for part of the engineering and testing
process. This section explains the following important points for using iDefine:
• System configurations of ProSafe-RS and iDefine
• ProSafe-RS engineering functions and iDefine interface
• Engineering flow when using iDefine

n System configuration when using iDefine

The following figure shows the system configuration when using iDefine.

AD Server PC

AD Server

ADMDB
Engineering Data
Ethernet

Test Command
iDefine PC AD Organizer & SENG PC

AD Organizer
ProSafe-RS I/O File
(I/O, IOM Data)
iDefine

SCS Manager

iDefine-config File
(Application Data) SCS Project
iDefine Project Test Manager

Vnet/IP

SCS

Figure C2.2-1 System configurations of ProSafe-RS and iDefine

n Relationship between ProSafe-RS engineering functions and iDefine

The following describes the relationship between ProSafe-RS engineering functions and
iDefine when using iDefine.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-12
AD Organizer
Safety I/O Editor
Export Safety Communication
Import I/O Editor
I/O & IOM
ProSafe-RS I/O File Export to iDefine
(xlsx)

RS Generation Manager
iDefine Export Import iDefine ModPack
Configuration
Generation Revision History
iDefine-config File
(XML)

iDefine
Test Manager

Logic Simulation Test

SCS Simulation
Test
Logic SCS
Target Test Simulator Project

SCS SCS Manager

Simulator

SCS

Figure C2.2-2 Relationship between ProSafe-RS engineering functions and iDefine

iDefine is used in the following ways in the application creation phase:

• iDefine can manage the data from multiple SCS projects. The engineer should decide
how best to manage and associate iDefine projects with ProSafe-RS projects.
• The IOM definition, safety I/O list, and safety communication I/O list are managed in AD
Suite and exported for iDefine as a ProSafe-RS I/O file in the xlsx format.
• The user creates an application in iDefine. Using information on the I/O of SCS, the
ProSafe-RS I/O file that was generated from AD Organizer is imported and put to use.
Engineering results are written as iDefine-config files in XML format for each SCS.
• The iDefine-config files that were generated are imported to AD Suite and reflected in
SCS projects.
• Data created by using iDefine such as POU and variables become read-only after it is re-
flected in SCS Manager.
• The run sequence of the POUs that were created by using the Multi-Language Editor can
be changed in the Multi-Language Editor. The run sequence of the POUs that were cre-
ated by using iDefine can be changed in iDefine.
• iDefine-config files can be assigned to ModPack in AD Suite. The history of iDefine-config
files is also managed.
Logic simulation tests, SCS simulation tests, and target tests can be run from the iDefine test
function.
• Launch iDefine Test Manager in AD Suite.
• iDefine can be connected with the logic simulator and SCS simulator of SCS Manager,
and the actual SCS through iDefine Test Manager.
• Tests can be run using the iDefine test function.

l Interface between ProSafe-RS and iDefine

ProSafe-RS I/O file and iDefine-config file serve as the interface between ProSafe-RS and
iDefine.
• ProSafe-RS I/O file

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-13
It includes information on the safety I/O list, safety communication I/O list, and I/O mod-
ules that are saved in ADMDB.
The following items must be configured in the safety I/O list:
• P&ID Tag
• I/O Type (AI, AO, DI, DO)
• I/O Tag
• Signal Type
• P&ID Group
The following items must be configured in the safety communication I/O list:
• P&ID Tag
• I/O Type (AI, AO, DI, DO)
• Signal Protocol
• I/O Tag
• P&ID Group
Data that is checked-in to the AD Server is exported.
The file is in the xlsx format with five worksheets.
The following table shows the relationship between each worksheet and each iDefine edi-
tor.

Table C2.2-1 Relationship between the worksheets in ProSafe-RS I/O file and iDefine editors
Worksheet iDefine editor
CIO worksheet Client IO Table
IO worksheet Client IO Table
IO Parameter worksheet ProSafe-RS IO Parameter
Node worksheet ProSafe-RS IO Node
IOM worksheet ProSafe-RS IO Module

The content defined with Safety I/O Editor is not exported to the CIO worksheet.
The content defined with Safety Communication I/O Editor is not exported to the IO work-
sheet and the IO Parameter worksheet.
The following table shows the conditions for reflecting the data that is managed in AD
Suite in each worksheet in the ProSafe-RS I/O file based on the rules for assigning infor-
mation.

Table C2.2-2 Conditions for definitions of Safety I/O Editor being reflected onto the ProSafe-RS I/O file
Definition status of the I/O signal Worksheet in the ProSafe-RS I/O Are definitions reflected onto the
file worksheet?
The I/O module to which the I/O IO worksheet Yes
signal is to be assigned is deter-
mined and the node to which the IO Parameter worksheet Yes
I/O module is to be assigned is al- Node worksheet Yes
ready defined in IOM Definition
Editor. IOM worksheet No
However, the I/O module is not de-
fined in IOM Definition Editor.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-14
Table C2.2-2 Conditions for definitions of Safety I/O Editor being reflected onto the ProSafe-RS I/O file
(Table continued)
Definition status of the I/O signal Worksheet in the ProSafe-RS I/O Are definitions reflected onto the
file worksheet?
The I/O module to which the I/O IO worksheet Yes
signal is to be assigned is deter-
mined. IO Parameter worksheet Yes
However, the node to which the Node worksheet No
I/O module is to be assigned is not
defined in IOM Definition Editor. IOM worksheet No
The I/O module to which the I/O IO worksheet Yes
signal is to be assigned is not de-
termined yet. For example, one of IO Parameter worksheet Yes (*1)
the following columns in Safety I/O Node worksheet No
Editor is empty:
• RS Project IOM worksheet No
• SCS
• Node Type
• Node
• IOM Category
• IOM Type
• Unit (For N-IO)
• Slot
• Terminal
The I/O Tag is not defined in the IO worksheet No
I/O signal.
IO Parameter worksheet No
Node worksheet No
IOM worksheet No
*1: When a value has been entered for IOM Type

Table C2.2-3 Conditions for definitions of Safety Communication I/O Editor being reflected onto the
ProSafe-RS I/O file
Definition status of the I/O signal Corresponding worksheet I/O signal definitions reflected?
The communication I/O module to CIO worksheet Yes
which the communication I/O sig-
nal is to be assigned is determined Node worksheet Yes
and the node to which the commu- IOM worksheet No
nication module is to be assigned
is already defined in IOM Defini-
tion Editor.
However, the communication mod-
ule is not defined in IOM Definition
Editor.
The I/O Tag is defined in the com- CIO worksheet Yes
munication I/O signal and the com-
munication module to which the Node worksheet No
communication I/O signal is to be IOM worksheet No
assigned is determined.
However, the node to which the
communication module is to be as-
signed is not defined in IOM Defi-
nition Editor.
The I/O Tag is not defined in the CIO worksheet No
communication I/O signal.
Node worksheet No
IOM worksheet No

• iDefine-config file
This includes the POU, defined words, internal variables, FB instances, tag names, and
parameters that were created by using iDefine.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-15
The file is in XML format.

l Data from iDefine that is reflected in SCS Manager

When you import the iDefine-config file exported from iDefine into AD Organizer and run Re-
flection from RS Generation Manager, the data is reflected in the SCS Manager view and
builders.

Table C2.2-4 Where data included in the iDefine-config file is reflected

Data in the iDefine-config file Destination
POU Link Architecture View
Internal variables and user defined FB instances (*1) Dictionary View
Defined words Dictionary View
Tag names and parameter Tag Name Builder (*2)
*1: I/O variables and communication FB instances are not generated by iDefine. These are generated based on definitions of AD
Organizer. The variables for instances of subsystem communication I/O FB can be defined with Safety Communication I/O
Editor.
*2: It is reflected only when the CENTUM VP integration package or the FAST/TOOLS Integration Package is enabled.

l Selecting a FB with an instance name

From the function blocks that were defined in the POU that was created by using iDefine, you
can set according to type a function block with an instance name when importing to the SCS
project. The user selects a function block with an instance name when importing the iDefine-
config file to AD Organizer.

n Engineering flow when using iDefine

Applications can be created in iDefine by using the I/O list engineering method. The engineer-
ing flow when using iDefine is as follows:
SEE
ALSO For more information about the details of engineering using iDefine, refer to:
iDefine User Guide (PR03076-MAN-970_01)

l Work flow from the start of engineering until the end of Typical test
iDefine breaks into parts the typical logic, such as the common input and output processes of
application logics, and registers them as a template in Typical. Unit tests can be run on regis-
tered Typicals by using the emulator on iDefine, but sometimes the test function in SCS Man-
ager is also used for testing to prevent engineering regression. However, it is possible that the
specification for the application logic and I/O definition have not been finalized at this stage. In
such a case, you need to configure a dummy I/O and logic, which is the bare minimum re-
quired to run a Typical test. The following figure explains the tasks that need to be done in
SCS Manager, AD Suite, and iDefine in order to run a Typical test by using SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-16

SCS Manager AD Suite iDefine

Create an AD project Create an iDefine project

Import safety I/O list (*1) Create or import

and safety communication user-defined FB and Typical
I/O list (*1)

Test user-defined FB
and Typical
(by using the iDefine emulator)
ProSafe-RS I/O file

Export safety I/O list, Import safety I/O list,

Create an SCS project safety communication I/O list, safety communication I/O list,
and IOM definition and IOM definition

Edit safety I/O list, Create C&E modules and

safety communication I/O list,
and IOM definition SA modules for Typical tests

iDefine-config file
Run the Safety Analyzer
Import Output Export Output
Configuration Configuration

Run logic simulation tests

and SCS simulation tests
if necessary Reflection process and build

Offline download to SCS Create a Typical test case

Target test for Typical

*1: Data that is required to test Typical is included, as well as a tentative safety I/O list

Figure C2.2-3 Work flow for running a Typical test

l Work flow for engineering and testing the POU and I/O data of the SCS
After you have completed the Typical test, engineer using the safety I/O list or safety commu-
nication I/O list after the specifications have been defined and run a target test by using SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.2 Work flow of I/O list engineering with iDefine> C2-17

SCS Manager AD Suite iDefine

Create POUs that cannot be Edit safety I/O list,
configured in iDefine safety communication I/O list,
if necessary and IOM definition
ProSafe-RS I/O file

Set the inter-SCS Export safety I/O list, Import safety I/O list,
safety communication, safety communication I/O list, safety communication I/O list,
Modbus slave communication, etc. and IOM definition and IOM definition

Modify the POU run sequence Create C&E modules

if necessary and SA modules

Build Define tag names

iDefine-config file

Run the Safety Analyzer Import Output Configuration Export Output Configuration

Run logic simulation tests

and SCS simulation tests Reflection process and build
if necessary

Offline download to SCS Create target tests for C&E

modules and SA modules

Target tests for C&E modules

and SA modules

Figure C2.2-4 Work flow for running a target test

SEE
ALSO For more information about POUs that can be created in iDefine, refer to:
“n Functions and function blocks” on page D5-7

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-18

C2.3 Work flow for RS original engineering

The following figure shows the engineering flow from the creation of an RS project and SCS
project to the backing up of the projects (check-in) after completion in RS original engineering.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-19
Procedure for
creating application

Are RS Project and NO

SCS Project already created?

(H) Passwords
levels.

(I) Operation (1) Download Operation Marks

Marks

(1) Confirm values and data status of

(J) Enable Output output variables.
(2) Operate “Enable Output”

(1) Print out self-document

(K) Self-Document
of the entire SCS project

(1) Confirm diagnostic information

(L) Check in messages
Project
(2) Check in SCS project

End

Figure C2.3-1 Procedure of creating an application

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-20

n Detailed procedure for creating a new application

l (A) Opening the project

Table C2.3-1 Procedure for opening the project

Item Description
(1) Check out SCS project • When check-in is performed by temporarily discontinuing on-going
creation of an application, you can check out the created SCS project
by using the Version Control Tool.
(2) Open SCS project • Launch the SCS Manager.
• Open the SCS project.
• Enter the password for the SCS project.
(3) Validate SCS project • Run the Database Validity Check Tool and check that the CRC codes
and generation times of the databases are consistent between the
SCS and SCS project.
• Repair a database if there is a discrepancy in the database.

l (B) Creating a new project

Table C2.3-2 Procedure for creating a new project

Items Description
(1) Create an AD project Perform the following tasks by using the ADS Administration Tool:
• Set the ADMDB location
• Create an AD project
(2) Create an RS project • Only one folder of RS project is automatically created when the engi-
neering function is installed. You need to set the folder of the RS
project as a shared folder.
• Then you can use AD Organizer to register the RS project in the AD
project.
(3) Create an SCS project To create a new SCS project, you need to configure the following set-
tings by using SCS Manager:
• Folder for SCS project
• Properties of SCS project
• Resource
• Configuration
• IP address

l (C) Creating an application

Table C2.3-3 Procedure for creating an application

Items Description
(1) Define Input/Output • Define I/O variables.(Dictionary View)
• Define I/O modules.(I/O Wiring View)
• Perform wiring of channels and I/O variables (I/O Wiring View).
• Set parameters for nodes, I/O modules and channels.(I/O Parameter
Builder)
(2) Create and modify POU • Open POU which you want to create and modify.
• Edit POU.
• Save POU.
• Print POU.
• Confirm that the logic entered in Multi-Language Editor is the same
as the logic printed by using the self-document function.
• Confirm that the execution order of FB/FU is correct.
(3) Generate database • Perform build.
• Analyze and confirm that the safety applications such as FU/FB are
correct in terms of safety by using the Integrity Analyzer.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-21
Table C2.3-3 Procedure for creating an application (Table continued)
Items Description
(4) Specify the range of testing • Run the Cross Reference Analyzer to check the changed Program
Organization Unit (POU) and the affected POU and then authorize
them. Then, visually check the following setting items, which are criti-
cal for safety, to be sure that there are no unintended changes, be-
cause changes in these items cannot be detected by the Cross Ref-
erence Analyzer.
[Cycle Timing] in Resource Properties of SCS Manager
Items in SCS Constants Builder:
• [Optical ESB Bus Repeater] (for SCSP1/SCSV1)
• [Maximum Extension Distance] (for SCSP1/SCSV1)
• [Extend Scan Period Automatically]
• [Behavior at Abnormal Calculation]
• [Automatic IOM Download]
• [Locking of Internal Variables] (for SCSP2/SCSP3)
• [Device Power-Off Period] (for SCSP1/SCSP2/SCSP3/SCSU1)
• [Device Startup Waiting Period] (for SCSP1/SCSP2/SCSP3/
SCSU1)

SEE
ALSO For more information about Integrity Analyzer, refer to:
C5.1, “Integrity Analyzer” on page C5-2
For more information about Cross Reference Analyzer details, refer to:
C5.2, “Cross Reference Analyzer” on page C5-19

l (D) Testing the application with the SCS simulation test or Logic
simulation test function
Test the user application by using the SCS simulation test or logic simulation test.
SEE
ALSO For more information about details of SCS simulation test and logic simulation test, refer to:
C6., “Simulation tests” on page C6-1

l (E) Offline download

Table C2.3-4 Procedure for offline download

Items Description
(1) Change Security Level • Start the SCS Maintenance Support Tool which monitors the SCS
from the SCS Manager.
• Set the SCS security level to 0. Entering a password is required.
• Confirm that the SCS Security Level is 0 on the SCS State Manage-
ment window of the SCS Maintenance Support Tool.
• Confirm the diagnostic information message indicating the security
level at 0 with the SCS Maintenance Support Tool.
(2) Execute Offline Download • Execute offline download.
• When integrated with CENTUM, choosing offline downloading menu
will pop up a dialog box to prompt for saving the operation marks.
The operation marks may be saved as necessary.
• Confirm that SCS has started normally on the SCS State Manage-
ment window of the SCS Maintenance Support Tool.
(3) Validate SCS project • Start the Database Validity Check Tool to check that CRC and gener-
ation time of four kinds of databases for SCS and SCS project are
correct.
• Repair a database if there is a discrepancy in the database.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-22
SEE
ALSO For more information about offline download operations, refer to:
“n Procedure for offline download” on page C7-2
For more information about repairing a database, refer to:
“■ Repair database” in F3., “Database Validity Check Tool” in Engineer's Reference Manual (IM
32P04B10-01EN)

l (F) Target tests

Perform the output enable operation and test the user application on the target SCS.
SEE
ALSO For more information about details of target test, refer to:
C9., “Target tests” on page C9-1

l (G) Offline download

Table C2.3-5 Procedure for offline download

Items Description
(1) Execute Clean Project and • Before you execute offline download, you should perform Clean Proj-
Build ect.
Then perform build to create the database for downloading.
(2) Execute Offline Download • Execute offline download.
• When integrated with CENTUM, choosing offline downloading menu
will pop up a dialog box to prompt for saving the operation marks.
Save the operation marks as necessary.
• Confirm that SCS has started normally on the SCS State Manage-
ment window of SCS Maintenance Support Tool.
(3) Validate SCS project • Run the Database Validity Check Tool and check that the CRC codes
and generation times of the databases are consistent between the
SCS and SCS project.
• Repair a database if there is a discrepancy in the database.

SEE
ALSO For more information about clean project, refer to:
Cleaning Projects” in “Build” in “Code Generator” in “Workbench” in the Workbench User’s Guide

l (H) Setting passwords

Table C2.3-6 Procedure for setting passwords

Items Description
Set passwords for Security Levels • Set passwords for security levels 1 and 0 from the SCS Manager.
• Confirm the diagnostic information message from SCS for which
passwords for the security levels have been set with the SCS Mainte-
nance Support Tool.

l (I) Download operation marks

Table C2.3-7 Procedure for downloading operation marks

Items Description
Download Operation Marks • In the case of the CENTUM integration structure, the operation
marks saved in advance are downloaded to the SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C2.3 Work flow for RS original engineering> C2-23

l (J) Enabling output

Table C2.3-8 Procedure for enabling output

Items Description
(1) Confirm values and data sta- • Confirm which output channels are disabled on the SCS State Man-
tus of output variables agement window of SCS Maintenance Support Tool.
• Start the I/O Lock Window.(This can be performed at security level
2.)
• Confirm that values and statuses of logical data and physical data for
output variables are correct.
(2) Operate “Enable Output” • Perform the Output Enable Operation for output modules on the SCS
State Management window of SCS Maintenance Support Tool.
• Confirm that the diagnostic information message on the Output Ena-
ble Operation for output modules is displayed.
• Confirm that Output Channels are enabled on the SCS State Man-
agement window.
• Confirm that the SCS operating mode is "Running" on the SCS State
Management window.

SEE
ALSO For more information about Output enable operation details, refer to:
“n Enable Output operation” on page C8-2

l (K) Self-document

Table C2.3-9 Procedure for self-document

Items Description
(1) Print out whole SCS project • In preparation for the desk check performed at application software
using self-document changes in the future, print out the latest SCS project database as
self-documents.

l (L) Checking in project

Table C2.3-10 Procedure for checking in a project

Items Description
(1) Confirm the diagnostic infor- • Confirm whether any diagnostic information messages you have not
mation message confirmed are displayed or not with the SCS Maintenance Support
Tool.
(2) Check in SCS project • Close the SCS Manager.
• Check in the SCS project with the Version Control Tool.

SEE
ALSO For more information about check-in operations, refer to:
F5.3, “Checking in project data” in Engineer's Reference Manual (IM 32P04B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C3. Precautions when creating applications > C3-1

C3. Precautions when creating

applications
The tools and builders that can be used to define variables, POU, tag names are not the
same due to differences in the engineering method. This section explains the precautions for
handling them.

n Precautions for handling variables in I/O list engineering

In the case of I/O list engineering, the variables can be defined by using Safety I/O Editor,
Safety Communication I/O Editor, and SCS Manager. Variables defined by using other tools
are read-only. iDefine can also be used to define variables if you are using the tool.
The differences are as follows:
• Safety I/O Editor
This is used to define I/O variables.
• Safety Communication I/O Editor
The following can be defined:
• Instances of subsystem communication I/O FB
• Instances of PROFINET communication FB
• Instances of fire and gas communication FB
In addition, the following variables can be assigned to the communication I/O data area:
• FB instances defined with Safety Communication I/O Editor
• Local FB instances defined with SCS Manager
• FB instances of user defined FB parameters defined with SCS Manager or iDefine
The communication I/O data area is shown in Communication I/O Builder on the Comm.
I/O Wiring tab or Safety Comm. I/O Wiring tab.
• iDefine
This is used to define internal variables and FB instances.
• SCS Manager
This is used to define internal variables and FB instances.

n Precautions for handling POU

• Notes on handling POU with online changes
A new POU cannot be added by using online changes, so we recommend that you create
a spare POU in advance and change the name of the POU online as necessary.
• Handling POU when using iDefine
You can create POU by using iDefine or the Multi-Language Editor. However, POUs that
were created by using iDefine are read-only in Multi-Language Editor. POUs that were
created by using the Multi-Language Editor can only be changed in the Multi-Language
Editor. However, if you create a POU by using iDefine with the same name as a POU that
is already registered in the Link Architecture View, you can overwrite the existing POU
with confirmation when you run Reflection in RS Generation Manager.

n Precautions for handling tag names

You can define tag names by using iDefine or the Tag Name Builder. Tag names that were
defined by using iDefine are read-only in the Tag Name Builder. Tag names that were defined

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C3. Precautions when creating applications > C3-2
by using iDefine can only be changed in iDefine. Tag names that were defined by using the
Tag Name Builder can only be changed in the Tag Name Builder.

n Precautions on communication I/O definitions

When performing I/O list engineering with a version of SENG that is R4.03.10 or later, engi-
neering for subsystem communication and safety subsystem communication is all implemen-
ted with Safety Communication I/O Editor and IOM Definition Editor of AD Organizer. Commu-
nication I/O Builder will be used as read-only. Engineering for Modbus slave communication
and the DNP3 slave function is implemented with SCS Manager.
When reusing engineering data related to subsystem communication I/O created with version
earlier than R4.03.10, convert the data into a safety communication I/O list by using Commu-
nication I/O List Output Tool.
SEE
ALSO For more information about communication I/O List Output Tool, refer to:
“n Communication I/O List Output Tool” on page App.3-15

n Precautions for handling an SCS project that was checked in with

Version Control Tool of a revision earlier than R4.03.10
When you check out an SCS project that was checked in with Version Control Tool of a revi-
sion earlier than R4.03.10 and is handled by I/O list engineering, perform the task of restoring
the safety I/O list and IOM information within AD Organizer to the content labeled at the time
of the previous download.

n Precautions for restoring an SCS project that was generated by RS

generation with AD Organizer of a revision earlier than R4.03.10
If you have used Master Database Restoring Function to restore an SCS project that was
generated by RS generation with AD Organizer of a version earlier than R4.03.10 and down-
loaded to the SCS, you must also restore the safety I/O list and IOM information to the correct
contents. By using AD Organizer, recover the safety I/O list and IOM information that are la-
beled at the time of downloading last time.

n Precautions for managing SCS projects in AD Server

SCS projects are managed in an AD Server. The following describes the precautions for han-
dling SCS projects:
• Creation of new SCS projects
The selection of station type and I/O list engineering method should be determined at the
time of SCS project creation, and cannot be changed afterwards.
• Deleting SCS projects
To delete an SCS project, you must clear all items under the SCS project folder by using
Windows Explorer. After that, delete the SCS project by using AD Organizer.
• Moving SCS projects
For the SCS projects created with I/O list engineering, you need to move the SCS proj-
ects by using export/import function of AD Organizer. In the destination folder, do not du-
plicate the SCS project name and station address. Do not move the SCS project in Win-
dows Explorer.
• Modification of SCS project names
You need to use the SCS project export/import function of AD Organizer. You need to
specify a new SCS project name at the time of importing. Do not rename the SCS project
in Windows Explorer.
• Backup of SCS projects and RS projects

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C3. Precautions when creating applications > C3-3
You need to use the backup function of AD Organizer. You cannot run backup from Win-
dows Explorer.
• Test Project Creating Tool
In the case of SCS projects created with I/O list engineering, the safety I/O list, safety
communication I/O list, and IOM information are registered in AD Organizer, while various
setting files are included in SCS projects managed by SCS Manager.
In case of creating a test project from the current project, you need to create a separate
AD project for testing.
• I/O definition
In the case of RS original engineering, you need to define I/O by using I/O Parameter
Builder and I/O Wiring View. When performing I/O list engineering, I/O Parameter Builder,
I/O Wiring View, and Communication I/O Builder are read-only. By using IOM Definition
Editor of AD Organizer, you need to make additions and changes in the I/O list and IOM
information, and then reflect these into the SCS Manager by using Generation Manager.
Configuration tools for each I/O definition item and engineering method are shown in the
following table.

Table C3-1 List of functions for I/O definition

I/O definition Configuration tool in RS original Configuration tool in I/O list en-
engineering gineering
Structure definition of I/O module You can define the structure of I/O IOM Definition Editor
modules by using I/O Wiring View.
You can specify module type
name, mounting position and du-
plication.
Wiring of channels and input/ You can assign I/O variables to IOM Definition Editor
output variables channels by using I/O Wiring View. Safety I/O Editor
Parameter setting for the node You can specify parameters for the IOM Definition Editor
node by using I/O Parameter
Builder.
Parameter settings for modules You can specify parameters for the IOM Definition Editor
modules by using I/O Parameter Safety Communication I/O Editor
Builder. (*1)
Parameter settings for each chan- You can specify parameters for the IOM Definition Editor
nel channels by using I/O Parameter Safety I/O Editor
Builder.
Definitions of communication in- Define communication inputs/ Safety Communication I/O Editor
puts/outputs outputs and the communication
protocol by using Communication
I/O Builder.
*1: Some of the parameters for S2LP131 are defined using PROFINET Configurator started from Safety Communication I/O Edi-
tor.

• License management
You can check whether the I/O number has exceeded the number of I/O licenses by us-
ing the SCS information display function.
If a module is added, you need to confirm the license count at the time of RS generation

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C4. Procedures for generating a database> C4-1

C4. Procedures for generating a

database
After creating the application, generate a database. This chapter describes the steps for gen-
erating a database.

n Generating a database
After creating the application, build it and generate a database for SCS.
• Generating a database in I/O list engineering
In the case of I/O list engineering, run RS Generation from AD Organizer. The reflection
process of RS Generation reflects the engineering result of AD Organizer in SCS Manag-
er. If you have specified the build, after the reflection process has been completed suc-
cessfully, the application is built and the database is generated.
When an SCS project for which I/O list engineering is selected has been built successful-
ly, labels are set to the safety I/O list, safety communication I/O list, and IOM information
of AD Suite. Label names are as follows:
SCS project name-Build-Time
• Generating a database in I/O list engineering with iDefine
By using AD Organizer, import the relevant SCS iDefine-config file that was generated
from iDefine and perform RS Generation. To adjust the POU run sequence, run the re-
flection process only, change the sequence by using the Link Architecture View, and build
by using SCS Manager. To adjust the POU run sequence, run the build process for SCS
projects by using RS Generation Manager.
• Generating a database from SCS Manager.
From the menu bar of SCS Manager, click [Project] > [Build Project], or run build project
from the tool bar of SCS Manager. This method is used to build and generate a database
in the case of RS original engineering. The message from database creation function ap-
pears in SCS Manager.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5. Testing with the Safety Analyzers> C5-1

C5. Testing with the Safety Analyzers

The following tools are provided for the purpose of analyzing application logic.
• Integrity Analyzer
• Cross Reference Analyzer
Integrity Analyzer is used to analyze application logics and detect functions whose use is not
permitted in terms of safety. If unauthorized functions are used, operations for acknowledging
the use are required.
Cross Reference Analyzer is used to analyze areas affected by modifications and display the
test area when the application logic is modified. It is required to perform acknowledgement
operation for this test area.

IMPORTANT
Make sure to perform the acknowledgement operations for both analyzers before download-
ing the application logic to an SCS. If acknowledgement by both analyzers has not been com-
pleted, offline download and online change download to SCS cannot be performed.
It is recommended to perform the acknowledgement operation with Integrity Analyzer first and
then with Cross Reference Analyzer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-2

C5.1 Integrity Analyzer

Integrity Analyzer analyzes application logics, detects "functions that are not allowed to be
used" for the functions for safety and displays them in the window by highlighting for visual
emphasis.
The user can check whether or not functions prohibited from use for safety applications are
used. You can also print the analysis results.
If there is a program that intentionally makes use of functions prohibited from use for applica-
tion, the user can acknowledge their use for each program upon examining the program
based on the results of the analysis.
If functions prohibited from use for safety applications are used unintentionally, the application
logic must be modified. Make changes to the application logic, perform a build operation and
then analyze the application logic with Integrity Analyzer again.

IMPORTANT
• Before downloading application logic to SCS or before performing the SCS simulation
test, run Integrity Analyzer and Cross Reference Analyzer, check and acknowledge the
analysis results.
• It is possible to execute an application logic on a PC in logic simulation tests even if it has
not been analyzed by both analyzers.
• Even when logic simulation tests are used, make sure to check that only functions whose
use is permitted for safety applications and interference-free functions are used in an ap-
plication logic by Integrity Analyzer at the appropriate time in order to detect errors in the
application logic.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-3

C5.1.1 Methods for checking analysis results

This section explains how to check results of analysis by Integrity Analyzer.

n Starting Integrity Analyzer

1. After a build operation, select [Engineering] from the [Tools] menu of SCS Manager.
The Engineering launcher menu appears.
2. Select [Integrity Analyzer] from the Engineering launcher menu.
Integrity Analyzer starts up and analyzes the application logic in question.

IMPORTANT
• Start Integrity Analyzer after modifying and saving an application logic and performing a
build operation. Integrity Analyzer analyzes the databases generated by the build opera-
tion.
• If Integrity Analyzer has already been started when you attempted to perform a build or
download operation, a dialog box prompting to close Integrity Analyzer appears. In this
case, neither the build nor the download operation is performed.

n Procedure for using Integrity Analyzer

The procedure for using Integrity Analyzer is explained below.
1. Checking functions prohibited from use in terms of safety in Project Tree
The results of analyzing the application logic with Integrity Analyzer are displayed in Proj-
ect Tree. Check whether or not functions prohibited from use in terms of safety are used.
2. Checking with analysis result report
Check the Integrity Analysis Report showing the analysis results, either directly in a win-
dow or by printing it out.
3. Acknowledgement of functions prohibited from use in terms of safety
If there are programs that use interference-free functions intentionally, acknowledge the
use of those functions for each program in the Acknowledge Non-Compliance dialog box
upon examining the programs based on the analysis results.
If interference-free functions are used unintentionally or prohibited functions are used, it is
necessary to modify the application logic in question. Close Integrity Analyzer without ap-
proving the functions, modify the application logic, perform a build operation and then an-
alyze the application logic by Integrity Analyzer again.
4. Saving and printing analysis results
Save the analysis results and print them if necessary.

n Checking functions prohibited from use in terms of safety in project

tree
Project Tree allows checking whether or not functions that are prohibited from use in terms of
safety exist in an application logic.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-4
Integrity Analyzer [Pjt:SCS0101]
File Analyze Options

SCS0101 Summary
SCS0101 Errors
SCS0101
PROG1
PROG1 Unacknowledged non-compliances
Language
PROG4
Size
Functions
Variables
PROG2
Language
Size
Functions
Variables
PROG3
PROG4

Project Tree

Figure C5.1.1-1 Project tree of Integrity Analyzer

The graphical analysis results can only be viewed in the window; it cannot be printed out.

l How to understand icon colors

Project Tree displays SCS projects, configurations, resource and programs in a tree structure.
Double-click a program icon to display icons for [Language], [Size], [Functions] and [Varia-
bles]. Analysis results are shown using colored icons placed to the left of the labels in the
tree.

Table C5.1.1-1 Meaning of colors of icons on the left side of project tree
Icon color Description
Errors. Red icons indicate that prohibited functions are used. For example, using AND with
17 or more input parameters or using arrays in FBD or LD fall under this classification. It is
Red necessary to modify programs for which red icons are displayed and remove the prohibited
functions. It is not possible to download application logics to an SCS if they contain prohibi-
ted functions.
Warnings. Yellow icons indicate that interference-free functions are used. For example, SIN
and COS functions cannot be used in safety applications but can be used in other applica-
tions (control logics that do not influence safety). Check that the areas where the interfer-
Yellow
ence-free functions exist are outside the range of safety applications. Alternatively, check
that there is no influence on safety applications. Once the use of interference-free functions
is acknowledged, the applications can be downloaded to an SCS.
No error. Green icons indicate that a program is created using only the functions for safety
Green (safety applications are created). Though acknowledgement is not required, the acknowl-
edgement status needs to be saved.

If you select an individual icon in Project Tree, detailed analysis information of items to be
checked is displayed in the right pane of the window. The right pane shows analysis results of
an item selected in Project Tree using one of the following icons.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-5
Table C5.1.1-2 Meaning of icons in the right pane
Icon Meaning

(red) Error. Prohibited functions are used.

Warning. Interference-free functions are used.

(yellow)

No error. A program is created using only the functions for safety.

(green)

SEE
ALSO For more information about details on how to read the analysis results of the program in Project Tree, refer to:
C5.1.3, “Confirmation of analysis results by project tree” on page C5-12

n Checking with Analysis report

The Integrity Analysis Report organizes and summarizes all the information in analysis re-
sults. It can be displayed in a window, printed or saved in a file (using RTF or TEXT format) as
a report.
The Integrity Analysis Report is used mainly for the following two applications.
• It provides more detailed information than the information obtained by expanding Project
Tree.
• The Integrity Analysis Report can be used as a part of operation records or application
construction documentation, by printing it out or saving it to a file. The Integrity Analysis
Report also includes information about whether or not acknowledgement is made in the
Acknowledge Non-Compliance dialog box, along with comments. In order to record ac-
knowledged items, print or save the report in a file after acknowledgement.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-6

Application Logic Integrity Analysis Report

Project : SCS0101
Configuration : SCS0101
Resource : SCS0101 (101)
Project Build Date : 12/05/2007 10:45:30 AM
Project Analysis Date : 12/05/2007 10:54:53 AM
Report Date : 12/05/2007 10:55:24 AM
User : MATSUI

PROG1
Language Usage
Pass PROG1 FBD (Function Block Diagram)

Program Size
Pass PROG1 524 Limits 0..4000

Function Usage
Pass

Variable Usage
Pass

PROG2
Language Usage
Pass PROG2 LD (Ladder Diagram)

Program Size
Pass PROG2 1044 Limits 0..4000

Function Usage
Pass

Variable Usage
Pass

Acknowledgement Status
Program Status
PROG1 Pass
PROG2 Pass
PROG3 Pass
PROG4 Pass
PROG5 Warning Acknowledged by MATSUI 12/05/2007 10:54:59 AM

Number of programs with integrity errors: 0

Number of programs requiring acknowledgement: 0

Figure C5.1.1-2 Example of Integrity Analysis report

n Saving and displaying Analysis report

1. Select a resource in Project Tree and select [Save Analysis] from the [File] menu. Alter-
natively, click "Save current analysis history" button in the toolbar;
the analysis results are saved.
2. Select [Report] from the [Analyze] menu.
The saved analysis results are displayed as an analysis report.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-7

IMPORTANT
Make sure to save the analysis results before creating an analysis report.
If the current analysis results and acknowledgement history are not saved before creating an
analysis report, a message prompting you to save the history is notified. If you click [Yes] but-
ton in the message box, the current analysis results and acknowledgement history are saved,
overwriting the history saved before in the process, and an analysis report is created. An
analysis report is not created if you click [No] button.

n Acknowledgement of interference-free functions

If the analyzed application logic includes programs using interference-free functions, it is nec-
essary to acknowledge such programs one by one in the Acknowledge Non-Compliance dia-
log box.
Acknowledge Non-compliance

The program(s) listed below have

failed one or more integrity checks.
Click on the check box to
acknowledge and accept them as
non-hazardous.

Non-compliant Programs
Program Resource Configuration
PROG1 SCS0101 SCS0101
PROG3 SCS0101 SCS0101
PROG4 SCS0101 SCS0101

Comment

Use of AND(4) authorized - omitted from allowed

function list

OK Cancel

Figure C5.1.1-3 Acknowledge Non-compliance dialog box

l Displaying the Acknowledge Non-compliance dialog box

Select [Authorize] in the [Analyze] menu. Alternatively, click "Display program non-compliance
dialog" button in the toolbar. The Acknowledge Non-Compliance dialog box appears.

l Acknowledgement of programs and displayed icons

This dialog box shows analysis results of each program with one of the following icons.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-8
Table C5.1.1-3 Meaning of icons
Icon (color) Description
A program uses prohibited functions. This icon has the same meaning as the red program
(red) icon displayed in Project Tree. Modify the program and remove the prohibited functions.
This program cannot be acknowledged.
A program uses interference-free functions. This icon has the same meaning as the yellow
program icon displayed in Project Tree. In order to download the programs to an SCS, it is
(yellow) necessary to check each check box of all the programs marked with this icon and acknowl-
edge them.

Before approving, confirm that only the functions for safety are used in the safety application
using Project Tree or by checking the Integrity Analysis Report.
The reasons why interference-free functions are used, results of analysis for the purpose of
acknowledgement, etc., can be entered as comments. The Integrity Analysis Report includes
information about whether or not acknowledgement was made along with any comments en-
tered.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-9

C5.1.2 Integrity Analyzer window structure

This section explains the window structure of Integrity Analyzer.
Menu Bar
Tool Bar
Integrity Analyzer [Pjt:SCS0101]
File Analyze Options

SCS0101 Summary
SCS0101 Errors
SCS0101
PROG1
PROG1 Unacknowledged non-compliances
Language
PROG4
Size
Functions
Variables
PROG2
Language
Size
Functions
Variables
PROG3
PROG4

Project Tree

Figure C5.1.2-1 Integrity Analyzer window structure

n Menu bar
The menu bar provides the following menus.
• [File] menu
• [Analyze] menu
• [Options] menu
The menu items of each menu are explained below.

Table C5.1.2-1 File menu

Menu item Description
Print Report Prints an analysis report saved by [Save Analysis]
Save Report Creates an analysis report and saves it in a file (RTF or TEXT format)
Save Analysis Saves analysis results and acknowledgement status.
Exit Closes Integrity Analyzer

Table C5.1.2-2 Analyze menu

Menu item Description
Performs analysis and compares with the results of previous warning ac-
knowledgement and analysis. If the areas acknowledged in the previous
With history
analysis are not modified this time, it is regarded as if they have already
Start been acknowledged.
Performs analysis without comparing it with results of previous acknowl-
Without history
edgement and analysis
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-10
Table C5.1.2-2 Analyze menu (Table continued)
Menu item Description
Creates and displays the analysis report in the Integrity Analysis Report
Report
window
Authorize Displays the Acknowledge Non-Compliance dialog box.

Table C5.1.2-3 Options menu

Menu item Description
Settings Displays the Settings dialog box

n Toolbar
The toolbar provides the following buttons.

Table C5.1.2-4 Toolbar buttons

Button Name Description

Save current analysis history Saves analysis results and acknowledgement status.

Print report for a selected re-

Prints analysis reports.
source
Display program non-compliance
Displays the Acknowledge Non-Compliance dialog box.
dialog
Selects the icon of the previous interference-free element or ele-
Previous non-compliance ment not allowed in terms of safety relative to the currently se-
lected icon in Project Tree (the upward direction in the tree).
Selects the icon of the next interference-free element or element
Next non-compliance not allowed in terms of safety in Project Tree relative to the cur-
rently selected icon (the downward direction in the tree).

n Project tree
Project Tree is displayed on the left pane of the Integrity Analyzer window.
SCS0101
SCS0101
SCS0101
PROG1
PROG2

Figure C5.1.2-2 Project tree

Each level of Project Tree can be expanded or collapsed by double-clicking an icon or text
label, or clicking the +/- button on the left edge.
Analysis results of an item selected in Project Tree are displayed in the right pane of the win-
dow.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-11
The display arrangement of Project Tree can be defined in Settings dialog box.

n Displaying the Settings dialog box

On the [Options] menu, click [Settings]. The Settings dialog box appears.

Settings

View

Project Tree
Sort as workbench

Sort by name

Keep On Top

OK Cancel

Figure C5.1.2-3 Settings dialog box

• Project Tree
Sort as workbench: Contents displayed on Project Tree are sorted along with Workbench.
Sort by name: Contents displayed on Project Tree are sorted by names alphabetically.
• Keep On Top
Integrity Analyzer window is kept always on top.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-12

C5.1.3 Confirmation of analysis results by project tree

This section explains how to understand the detailed information displayed when the following
layers below the resource (the SCS project) are selected in Project Tree.
• Resource (list of program errors and unacknowledged warnings in a resource)
• Program (program classification and analysis results)
• Language (language usage information of a program)
• Size (size information of a program)
• Functions (results of analyzing program source code and object code)
• Variables (results of analyzing variables in a program)

n Displaying analysis results of Functions and Function Blocks

Project Tree displays analysis results of FUs and FBs as part of the summary for the program
that calls the FUs and FBs.
That is, if you expand an icon of a program name, not only the analysis results of the program
itself, but also the analysis results for the FUs and FBs called by the program are displayed.

n Checking resources
A list of analysis statuses of resources (SCS projects) is displayed in the right pane of the win-
dow. The list displays detected errors and unacknowledged warnings.

Integrity Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Summary
SCS0101 Errors
SCS0101
PROG1
PROG1 Unacknowledged non-compliances
Language
PROG4
Size
Functions
Variables
PROG2
Language
Size
Functions
Variables
PROG3
PROG4

Project Tree

Figure C5.1.3-1 Analysis results of resource

The analysis results of the selected resource are classified into errors and unacknowledged
warnings, and displayed in a tree structure in the right pane. Errors and unacknowledged
warnings can be expanded or collapsed.
These graphical analysis results can only be viewed in the window; they cannot be printed
out.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-13

n Checking programs
When you select a program name in Project Tree, a list of analysis results of the program is
displayed in the right pane of the window. The classification of the program and the result of
analysis (Pass, Fail, Warning) are displayed.

Integrity Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Summary
SCS0101 Classification: Safety Related
SCS0101 Integrity analysis: Fail
PROG1
Language
Size
Functions

Figure C5.1.3-2 Analysis results of a program for which error occurred

These graphical analysis results can only be viewed in the window; they cannot be printed
out.

n Checking program languages

If you select [Language] in Project Tree, the language used for the program is displayed in the
right pane of the window. If the program includes user-defined FUs or user-defined FBs, the
languages used for them are shown as well.

Table C5.1.3-1 Icons displayed on the left side of program names and meaning
Icon (color) Meaning
POUs are created using permitted languages
(green)
POUs are created using languages that are not allowed (*1)
(red)
*1: When using ST to write a program other than FU and FB, an error will occur.

Integrity Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 POU Language Type

SCS0101 PROG1 FBD Program
SCS0101 Fb2 FBD Function Block
PROG1 Func2 LD Function
Language
Size
Functions
Variables
PROG2

Figure C5.1.3-3 Results of checking languages used in programs

The screenshot example above shows the result of analyzing languages used in PROG1.
PROG1 uses a function block called Fb2 and a function called Func2. PROG1, Fb2 and
Func2 are written with permitted languages.
These graphical analysis results can only be viewed in the window; they cannot be printed
out.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-14

n Checking program size

IMPORTANT
If the program size exceeds the specified limit, a warning is displayed. However, even if the
warning is displayed, you can still use the program for a safety function after sufficiently con-
firming the validity of the program through some testing.

If you select [Size] in Project Tree, the size of the program and the specified upper limit size
are displayed in the right pane of the window. If the program includes user-defined FUs or
user-defined FBs, their program sizes are shown as well.
For the FB created with ST, the number of lines excluding the comment lines and blank lines
as well as the maximum number of lines is displayed.

Table C5.1.3-2 Icon displayed on the left side of program names and meaning
Icon (color) Meaning
The program size exceeded the warning range
(yellow)

Integrity Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 POU Size Limit

SCS0101 PROG1 91528 0..4000
SCS0101 Func2 5206 0..4000
PROG1
Language
Size
Functions
Variables
PROG2

Figure C5.1.3-4 Program size information

These graphical analysis results can only be viewed in the window; they cannot be printed
out.

n Checking program source code and object code

If you select [Functions] in Project Tree, the results of analyzing the source code and object
code of the program are displayed as a list of unauthorized FUs or FBs used in the right pane
of the window.
An icon displayed to the left of a function name or function block name indicates that the FU
or FB is not allowed in terms of safety.

Table C5.1.3-3 Icons displayed on the left side of Function names/Function Block names and meaning
Icon (color) Meaning
The FU or FB in question is not classified as safe or interference-fee and its use
(red) caused an error
The FU or FB in question is classified as interference-free and its use in a safety pro-
(yellow) gram requires acknowledgement

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-15
Integrity Analyzer [Pjt:SCS0101]
File Analyze Options

SCS0101 Function Location Non-compliance

SCS0101 FBDFB_A.AVERAGE Source Multiple execution (gAv)
SCS0101 FBDFB_C.AVERAGE Source Multiple execution (Av)
PROG1 AVERAGE Source Multiple execution (gAv)
Language FBDFB_A Source Multiple execution (gFBA)
Size CountBlock.LIMIT Object
Functions CountBlock.LIMIT (0) Source
Variables ST_FB_A.REPEAT Source Prohibited (line 20)
PROG2 ST_FB_B.FOR Source Excessive iteration (line 30)

Figure C5.1.3-5 Information of Function usage in the program

Integrity Analyzer searches in one or multiple POUs for the functions calling the same FB in-
stance and displays the functions as the analysis result. If the same FB instance in a POU is
called by multiple functions from different locations, the related functions and POUs will be
displayed with respective warning messages. The above figure illustrates the result of the
analysis.
In the message displayed in the "Function" column of the preceding figure, FBDFB_A is the
name of the POU and AVERAGE is the type of the FB. The instance name or parameter
name is displayed in parentheses in the "Non-compliance" column.
In LD source code analysis, the existence and usage of EN inputs inside the program are also
detected. An EN input refers to the first BOOL-type input that is automatically appended when
the type of the first input for FUs or FBs is BOOL in LD.
If libraries are used, the source files of the libraries are also analyzed.
A number in ( ) following a function name or function block name indicates the number of in-
puts. However, EN inputs are not included in this number.
In case of a library, a function name is displayed as "library name.program name.function
name" and a function block name is displayed as "library name.program name.function block
name."
Note that the graphical view of the analysis results in the above figure is only available on the
screen. The printout is text only.
If unrecognizable statements or scripts with incorrect syntax are found in ST, the following
messages are displayed in the "Non-compliance" column.

Table C5.1.3-4 Non-compliance messages when error or warning occurs

Message in
Icon (color) Message in Non-Compliance Description
Function(*1)
ST_FB.WHILE Prohibited (line xx) (*2) WHILE must not be used.
(red)
ST_FB.RE- Prohibited (line xx) (*2) REPEAT must not be used.
(red) PEAT
ST_FB.FOR Loop nesting (line xx) (*2) Nested loop in FOR loop must not be
(red) used.
ST_FB.FOR Variable iteration count (line xx) Initial value, end condition or step num-
(red) (*2) ber in FOR loop must use a constant.
ST_FB.FOR Iteration counter overflow (line xx) FOR loop index counter range overflow.
(red) (*2)
ST_FB.EXIT Outside loop (line xx) (*2) EXIT must not be used outside FOR
(red) loop.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-16
Table C5.1.3-4 Non-compliance messages when error or warning occurs (Table continued)
Message in
Icon (color) Message in Non-Compliance Description
Function(*1)
ST_FB.RET Interference Free (line xx) (*2) Interference-free. Due to RETURN be-
(yellow) ing used.
ST_FB.FOR Excessive iterations (line xx) (*2) Due to the number of iterations in FOR
(yellow) loop exceeding 500.
ST_FB.FBD_F Function Block Call (*3) Due to ST calling FB.
(yellow) B
ST_FB.FBD_F FB Parameter Access (*4) Due to ST accessing FB parameter.
(yellow) B
ST_FB.= Exact comparison (line xx) (*5) Exact comparison should not be used to
(yellow) FBD_FB.<> compare real numbers.
*1: The messages of ST_FB here are the examples of functions and function blocks. FBD_FB is a function block name example,
not an instance name.
*2: xx in (line xx) will be replaced by the line number that are applicable to the message.
*3: The message will be displayed once even though the same FB is called many times by ST.
*4: The message will be displayed once even though same parameters in the same FB or different parameters in the same FB
are accessed many times by ST.
*5: xx in (line xx) will be replaced by all the line numbers that are related to the ST message.

Even comparing the two real numbers using an equal operator or not equal operator in FBD
or LD is classified as interference-free, and the message "Exact Comparison" will be dis-
played once per POU in the "Non-compliance" column.
SEE
ALSO For more information about precautions on the structure when describing FU and FB with the ST language,
refer to:
2., “Structured text” in POU Reference Manual (IM 32P03B20-01EN)

n Checking analysis results of variables in programs

If you select [Variables] in the project tree, variables that do not satisfy the requirements of the
program, such as naming rules and data type, are displayed in the right pane of the window.
The right pane displays names of variables that may cause errors or warnings and the pro-
grams, FUs or FBs to which those variables belong. Moreover, detailed information about er-
rors and warnings is also displayed.

Integrity Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Variable POU Non-compliance

SCS0101 gVarA FBST Multiple writes
SCS0101 gIO1 FBD_WrStatus Invalid write (status)
PROG1 gIO2 FBD_WrStatus Invalid write (status)
Language Durp [1. . 7] FBD_FB Array not allowed
Size strArray [1..10] ST_FB Bad array type (String)
Functions
Variables
PROG2

Figure C5.1.3-6 Example of variable analysis results

The Integrity Analyzer checks POUs to detect illegal writings: multiple writing to a variable,
within a POU or by different POUs, and writing to output variable statuses. The preceding fig-
ure illustrates the result of the analysis. In the [POU] column, names of the POUs performing
the illegal writing are displayed. If a POU contains multiple writing to the same variable, a
warning message will be displayed for that POU. If multiple POUs are writing to the same var-
iable, a warning message will be displayed for each of the POUs.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-17
TIP • Integrity Analyzer does not detect multiple writing to the same variable in ST objects. Such usage should
be checked through a code review or unit test. However, multiple writing to the same variable by a cer-
tain ST object and other POU will be detected.
• Integrity Analyzer does not detect multiple writing to arrays or array elements.

Error messages will be displayed for the POUs that are writing to the status of output varia-
bles.
• Integrity Analyzer detects writing to the .status member of the IO_BOOL or IO_REAL vari-
ables having output attribute.
For example, an error message is displayed in the following case: The value of internal
variable bool1 (type BOOL) is written to the .status member of output variable DO010101
(type IO_BOOL).

bool1 DO010101.status

Figure C5.1.3-7 Example where error message is displayed for POU (1)

• Integrity Analyzer detects writing to the entire IO_BOOL or IO_REAL variables having
output attribute. Integrity Analyzer also detects the cases where the output (type
IO_BOOL or IO_REAL) of an function block, such as B_TO_IB, is connected to an output
variable.
For example, an error message is displayed in the following cases:
The value of internal variable IO_BOOL1 (type IO_BOOL) is written to the .status mem-
ber of output variable DO010102 (type IO_BOOL).

IO_BOOL1 DO010102

Figure C5.1.3-8 Example where error message is displayed for POU (2)

The value of Q (type IO_BOOL), which is the output of function block B_TO_IB, is written
to the .status member of output variable DO010103 (type IO_BOOL).

B_TO_IB

bool_v V
Q DO010103
bool_sts STS

Figure C5.1.3-9 Example where error message is displayed for POU (3)

Table C5.1.3-5 Error Messages Displayed in Non-Error Messages Displayed in Non-Compliance Col-
umnompliance Column
Indication in [Varia- Message in Non-Compli-
Icon (color) Description
ble] ance

Multiple writing to this variable was detec-

(yel- gVarA (*1) Multiple writes
ted.
low)
Writing to the status of this output variable
(red) gI01 (*2) Invalid write(status) (*3)
was detected.
*1: Variable name or FB instance name plus parameter name is displayed.
*2: Variable name is displayed.
*3: In parentheses ( ), the member name (i.e. status) or type name of the variable is displayed.

Note that the graphical view of the analysis results in the above figure is only available on the
screen. The printout is text only.
If prohibited variables are used in ST, the following messages will be displayed as Non-Com-
pliances.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.1 Integrity Analyzer > C5-18
Table C5.1.3-6 Error messages displayed in Non-compliance column
Message in Vari- Message in Non-Compli-
Icon (color) Description
able ance
bAr- Array size Number of array elements exceeds 500.
(red) rayB[1..10000]
MultiArray[1..10] Array dimensions Multiple dimension arrays cannot be used.
(red) [1..10]
bArrayC[10..20] Array bounds The array initial index must be 1.
(red)
strArray[1..10] Bad array type({TYPE}) Array cannot contain prohibited data type
(red) (Detail is displayed in {TYPE}).
DO1 Bad type({TYPE}) Prohibited global variable cannot be used
(red) (Detail is displayed in {TYPE}).
COM_BOOL1 Bad local type({TYPE}) Prohibited local variable cannot be used
(red) (Detail is displayed in {TYPE}).
COM_BOOL2 Bad parameter Prohibited input/output parameter cannot
(red) type({TYPE}) be used (Detail is displayed in {TYPE}).
(*1) Array check error The analyzer detected a defect of a mech-
(red) anism which checks the access outside
the range of array.
*1: Message cannot be displayed.

If prohibited variables are used in FBD or LD, the following messages will be displayed as
Non-Compliances.

Table C5.1.3-7 Error messages displayed in Non-compliance column

Message in Varia- Message in Non-Compli-
Icon (color) Description
ble ance
bArrayA[1..10] Array not allowed Array must not be used in FBD or LD.
(red)

These graphical analysis results can only be viewed in the window; it cannot be printed out.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-19

C5.2 Cross Reference Analyzer

Cross Reference Analyzer displays the differences between the previously downloaded appli-
cation (the application currently running in an SCS) and the application to be downloaded,
and the extent to which the download will affect the operation in a window by highlighting
them visually, in order to limit the range of retesting caused by changes in an application logic.
You can check programs that require retesting. You can also print the analysis results.
Cross Reference Analyzer detects programs that depend on the modified program. You
should retest the detected programs. A list of programs requiring retesting is displayed; they
can be acknowledged upon checking the analysis results of each program.
If unintended program changes and dependencies are detected, the application logic must be
modified. Modify the application logic, perform a build operation and then analyze the applica-
tion logic with Cross Reference Analyzer again.
If no program is found for retesting, retesting will not be performed. However, since the modifi-
cations on a certain items may not be discovered for retesting, these modified items need to
be tested accordingly.

IMPORTANT
• Before downloading application logic to SCS, run Integrity Analyzer and Cross Reference
Analyzer and acknowledge.
• Cross Reference Analyzer detects the differences between the application currently run-
ning in an SCS and the application to be downloaded.
It does not detect differences with an application running in a virtual test.
In a virtual test, it is possible to execute and test an application logic on a PC without hav-
ing to perform analysis by both analyzers.

Cross Reference Analyzer also has the function to compare an SCS database with the mas-
ter database of other SCS project with the same domain number and station number. Using
this function, you can verify that a project created from an existing project is exactly the same
in functionality as the original project. This eliminates the need to test all the POUs when you
regenerate a project.
SEE
ALSO For more information about the items that require retesting but not detected by Cross reference Analyzer, re-
fer to:
C5.2.5, “Precautions on Cross Reference Analyzer” on page C5-46

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-20

C5.2.1 Methods for checking analysis results

This section explains how to check results of analysis by Cross Reference Analyzer.

n Starting Cross Reference Analyzer

1. After a build operation, select [Engineering] from the [Tools] menu of SCS Manager.
The Engineering launcher menu appears.
2. Select [Cross Reference Analyzer] from the Engineering launcher menu.
Cross Reference Analyzer starts up, automatically analyzes the application logic in ques-
tion and displays the analysis results.
TIP Cross Reference Analyzer displays or prints the differences between the previously downloaded application
logic and the application logic to be downloaded, and the extent of the differences. If an application logic has
never been downloaded, there is no equivalent to a previously downloaded application logic. In this case,
Cross Reference Analyzer displays all programs as new.

IMPORTANT
If Cross Reference Analyzer has already started when you attempted to perform a build or
download operation, a dialog box prompting to close Cross Reference Analyzer appears. In
this case, neither the build nor the download operation is performed.

n Procedure for using Cross Reference Analyzer

The procedure for using Cross Reference Analyzer is explained below.
1. Checking programs in Dependency Tree
Check the results of analysis by Cross Reference Analyzer in Dependency Tree to identi-
fy the programs requiring retesting. The programs requiring retesting are those with
changes and those that depend on the changed programs.
2. Checking with analysis result report
Check the Cross Reference Analysis Report showing the analysis results, either directly
in a window or by printing it out.
3. Acknowledgement of differences between application logics and extent of influence
A list of programs requiring retesting is displayed in the Acknowledge Dependencies dia-
log box; acknowledge them upon checking the analysis results of each program.
If unintended changes and independencies are detected or the application requires modi-
fication, close Cross Reference Analyzer without approving the programs. Modify the ap-
plication logic, perform a build operation and then analyze the application logic by Cross
Reference Analyzer again.
4. Saving and printing analysis results
Save the analysis results and print them if necessary.

n Checking programs in Dependency tree

Dependency Tree allows checking the results of comparing the application logic running on
an SCS and the application logic to be downloaded, as well as programs that depend on the
changes. These programs are the ones that require retesting and review.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-21

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Program dependencies

SCS0101 Program Variable
SCS0101 PROG1 Count
PROG1 PROG5 Deleted
PROG2 PROG7 VAL
Programs
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG5
PROG6
PROG7
PROG8

Dependency Tree

Figure C5.2.1-1 Example of program analysis result by Cross Reference Analyzer

These graphical analysis results can only be viewed in the window; they cannot be printed
out.

l How to understand icon colors

Dependency Tree displays SCS projects, configurations, resource and programs in a tree
structure. Double-click a program icon to display icons for [Programs], [Functions], [Function
Blocks], [Variables], [Defined Words], [I/O Parameters] and [Bindings]. Analysis results are
shown using colored icons placed to the left of the labels in the tree.

Table C5.2.1-1 Meaning of colors of icons on the left side of Dependency tree
Icon color Description
Red icons indicate that programs or function blocks and functions used in the program have
Red
been changed.
Yellow icons indicate dependencies on changed programs. Although the programs them-
selves have not been changed, it is necessary to retest or examine the code in order to
Yellow check that it is not affected by changes made to the dependent programs.
A yellow icon may also indicate that the program name was changed. Retesting is not re-
quired in this case.
Green icons indicate that the changes do not affect other programs. Neither retesting nor
Green
review is required.

If you select an individual icon in Dependency Tree, detailed analysis information of the item
to be checked is displayed on the right pane of the window. The right pane shows the status
of changes of the item selected in Dependency Tree and the extent of influence of the
changes.
If you select an individual icon below the program layer, the following colored icons are dis-
played next to the corresponding program components in the right pane of the window.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-22
Table C5.2.1-2 Meaning of icons in the right pane of the window when an icon below the program icon
is selected
Icon (color) Meaning
An item in the right pane is dependent on the program selected in Dependen-
(green) cy Tree but not affected directly by the changes.
An item in the right pane is dependent on the program selected in Dependen-
cy Tree and affected by the changes. In other words, the item was directly
(red)
changed or newly created, or is dependent on the changed areas.
An item in the right pane used to depend on the program selected in Depend-
(green) ency Tree but the dependency was eliminated by the change.

SEE
ALSO For more information about details on how to read the analysis results of the program in Dependency Tree,
refer to:
C5.2.3, “Confirmation of analysis results by Dependency tree” on page C5-30

n Checking with Analysis report

The Cross Reference Analysis Report organizes and summarizes all the information in analy-
sis results. It can be displayed in a window, printed or saved in a file (RTF or TEXT format) as
a report.
The Cross Reference Analysis Report is used mainly for the following two applications.
• It provides more detailed information than the information obtained by expanding De-
pendency Tree.
• The Cross Reference Analysis Report can be used as a part of operation records or ap-
plication construction documentation, by printing it out or saving it to a file. The Cross
Reference Analysis Report also includes information about whether or not acknowledge-
ment is made in the Acknowledge Dependencies dialog box, along with comments. In or-
der to record acknowledged items, print or save the report in a file after acknowledge-
ment.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-23
Application Logic Cross Reference Analysis Report
Project : SCS0101
Configuration : SCS0101
Resource : SCS0101 (101)
Project Build Date : 12/05/2007 10:45:30 AM
Project Analysis Date : 12/05/2007 1:18:27 PM
Report Date : 12/05/2007 1:19:02 PM
User : MATSUI
Programs in previous version : 8
Programs in current version : 8
Variables in previous version : 66
Variables in current version : 66
Shared variables in previous version : 57
Shared variables in current version : 57
Modified Programs
Name Change
PROG2 Modified
PROG3 Deleted
PROG5 I/O Changed
PROG7 Modified I/O Changed
PROG8 Function block modified, Variable changed, Defined Word changed
WASPROG4 Renamed

Modified Functions
Name Change
Func4 Modified
Modified Function Blocks
Name Change
Fb1 Modified
Modified Variables
Name Change
IN1 Type Changed, Intial Changed
IN2 Scope Changed
OUT1 Type Changed

Modified Defined Words

defConst Equivalent Changed
I/O Parameter Changes
Variable Comment
AI001 1-3 SAV144[01] Channel
DI001 1-5 SDV144[01] Channel
DI002 1-5 SDV144[02] Channel
DI003 1-5 SDV144[03] Channel
DI007 1-5 SDV144[07] Channel

Dependency Cross Reference

Current Version Bound Variable Usage

Program Bound variables
PROG1 C01001 C01002 C01003
PROG2 C01001 C01003 CONSU2 P02002
PROG5 C01001 P03001 P03002 P030003
PROG6
PROG7 LP0001@PROG7
PROG8
WASPROG4
Current Version Bound Variable Cross Reference
Bound Variable Used
C01001 PROG1 PROG2 PROG5
C01002 PROG1
C01003 PROG1(2) PROG2 Unmatched name (P02005)
C0NSU2 PROG2 Unmatched name (P02006)
LP0001@PROG7 PROG7(3)
P02002 PROG2
P03001 PROG5
P03002 PROG5
P03003 PROG5

Acknowledgement Status
Program Status
PROG1 Not Modified Not acknowledged
PROG2 Modified Not acknowledged
PROG5 IO Changed Not acknowledged
PROG7 Modified IO Changed Acknowledged by SUZUKI 12/05/2007 09:10:23
PROG8 Function block modified, Variable changed, Defined Word changed
Not acknowledged
Number of programs requiring acknowledgement : 4

Figure C5.2.1-2 Example of Cross Reference report (RTF format file)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-24

n Displaying Analysis report

1. Select a resource in Dependency Tree and select [Save Analysis] in the [File] menu. Al-
ternatively, click [Save current analysis history] button in the toolbar;
the analysis results are saved.
2. Select [Report] from the [Analyze] menu.
The saved analysis results are displayed as an analysis report.

n Displaying previous Analysis report

By running [Previous Report] in the [Analyze] menu, you can display the report of the analysis
result for the previously downloaded application. The report file is saved in .rtf format. The re-
port date of the previous analysis report is the date that the analysis report was last saved
before downloading.

n Acknowledgement of program dependencies

If the analyzed application logic contains programs requiring retesting because they were
changed or depend on the changed programs, it is necessary to acknowledge these pro-
grams one by one in the Acknowledge Dependencies dialog box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-25
Acknowledge Dependencies

The following program(s) contain

dependencies with modified
program(s). Click on the check
boxes to acknowledge
and accept them as non-hazardous.

Programs with Dependencies

Program Resource Configuration
PROG1 SCS0101 SCS0101
PROG2 SCS0101 SCS0101
PROG5 SCS0101 SCS0101
PROG7 SCS0101 SCS0101
PROG8 SCS0101 SCS0101

Authorize download

Comment

Permit download for initial testing only

OK Cancel

Figure C5.2.1-3 Acknowledge Dependencies dialog box

l Displaying the Acknowledge Dependencies dialog box

Select [Authorize] in the [Analyze] menu. Alternatively, click "Display program dependency ac-
knowledge dialog" button in the toolbar. The Acknowledge Dependencies dialog box appears.

l Acknowledgement of programs with changes and dependencies

The Acknowledge Dependencies dialog box displays programs indicated with red or yellow
icons in Dependency Tree. In order to download the application logic to an SCS, it is necessa-
ry to acknowledge all the programs displayed in the dialog box.
The user must confirm the following items and then check the check box for each program.
• Retesting and review must be planned and executed for programs indicated by red and
yellow icons.
• No unintended modifications are included.
• No unintended dependencies (e.g., unintended sharing of global variables) are included.

l Authorize download check box

Selecting this check box allows downloading the application logic to an SCS without acknowl-
edging individual program dependencies.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-26

IMPORTANT
• Use this check box only at the beginning of application development such as during de-
bugging an application logic.
• While the SCS is in use for actual plant, acknowledge the dependencies of individual pro-
grams without selecting this check box.
• It is recommended to enter the reasons in the comment field when the Authorize Down-
load check box is selected.

l Comment
Memos related to changed areas, results of analysis for the purpose of acknowledgement,
etc. can be entered as comments. The Cross Reference Analysis Report includes information
about whether or not programs are acknowledged, along with comments.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-27

C5.2.2 Cross Reference Analyzer window structure

This section explains the window structure of Cross Reference Analyzer.
Menu Bar
Toolbar

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101
SCS0101 Modified Programs
SCS0101 PROG2 (Modified)
PROG1 PROG3 (Deleted)
PROG2 PROG5 (I/O Changed)
Programs PROG7 (Modified, I/O Changed)
Functions PROG8 (New)
Function Blocks Modified Functions
Variables Func4
Defined Words Modified Function Blocks
I/O Parameters Fb1
Bindings Modified Variables
PROG5 Modified Defined Words
PROG6
I/O Parameter Changers
PROG7
DI001 (1-1 SDV144 [01] Module)
PROG8 DI002 (1-1 SDV144 [02] Module)

Dependency Tree

Figure C5.2.2-1 Cross Reference Analyzer window structure

n Menu bar
The menu bar provides the following menus.
• [File] menu
• [Analyze] menu
• [Options] menu
The menu items of each menu are explained below.

Table C5.2.2-1 File menu

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-28
Table C5.2.2-2 Analyze menu
Menu item Description
Performs analysis and compares it with the results of previous acknowl-
edgement and analysis. If the areas acknowledged in the previous analysis
With History
are not modified this time, it is regarded as if they have already been ac-
Start knowledged.
Performs analysis without comparing it with results of previous acknowl-
Without History
edgement and analysis
Creates and displays the analysis report in the Cross Reference Analysis
Report
Report window
Previous Report Displays previous analysis report.
Authorize Displays the Acknowledge Dependencies dialog box.
Compare with Original Project Compares a work database with the master database of another project

Table C5.2.2-3 Options menu

Menu item Description
Settings Displays the Settings dialog box

n Toolbar
The toolbar provides the following buttons.

Table C5.2.2-4 Toolbar buttons

Button Name Description

Save current analysis history Saves analysis results and acknowledgement status.

Print report for a selected re-

Prints analysis reports.
source
Display program dependency ac-
Displays the Acknowledge Dependencies dialog box
knowledgement dialog
Selects the icon of the previous element that was changed or af-
Previous dependency change fected relative to the currently selected icon in Dependency Tree
(the upward direction in the tree).
Selects the icon of the next element that was changed or affec-
Next dependency change ted relative to the currently selected icon in Dependency Tree
(the downward direction in the tree).

n Dependency tree
Dependency Tree is displayed on the left pane of the Cross Reference Analyzer window.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-29
SCS0101
SCS0101
SCS0101
PROG1
Programs
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG2
PROG3

Figure C5.2.2-2 Displaying Dependency tree

Each level of Dependency Tree can be expanded or collapsed by double-clicking an icon, or

text label, or clicking the +/- button on the left edge.
Analysis results of an item selected in Dependency Tree is displayed in the right pane.
The display arrangement of Dependency Tree can be defined in Settings dialog box.

n Displaying the Settings dialog box

On the [Options] menu, click [Settings]. The Settings dialog box appears.

Settings

View

Project Tree
Sort as workbench

Sort by name

Keep On Top

OK Cancel

Figure C5.2.2-3 Settings dialog box

• Project Tree
Sort as workbench: the Dependency Tree is displayed in the same order as the display
with Workbench.
Sort by name: Contents displayed on Dependency Tree are sorted by names alphabeti-
cally.
• Keep On Top
Cross Reference Analyzer window is kept always on top.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-30

C5.2.3 Confirmation of analysis results by Dependency tree

This section explains how to understand the detailed information displayed when layers below
resources (SCS projects) are selected in Dependency Tree.

n Checking resources
If you select a resource (SCS projects) in Dependency Tree, a list of analysis results of the
resource is displayed in the right pane of the window. The list displays changes related to the
selected SCS project.

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

Figure C5.2.3-1 Dependency tree of Cross Reference Analyzer

The analysis results of the selected SCS project are displayed in a tree structure in the right
pane. The modifications are displayed as classified groups of modified programs, modified
functions, modified function blocks and input/output parameter changes.
Each category can be expanded and collapsed by clicking the +/- button to the left of the cate-
gory.

l Icon colors and classifications of program names

The following table explains icon colors of program names in Dependency Tree and classifi-
cations displayed to the right of program names in the "Modified Programs" tree.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-31
Table C5.2.3-1 Icon colors and classifications of program names
Icon color of pro- Display in the
gram name in De- Classification Description right pane
pendency Tree (*1)
Modified The program itself has been changed. Yes
Instruction The program itself has not been changed, but the
Yes
modified (*2) database downloaded to SCS has been changed.
The program itself has not been changed, but de-
Function modi-
pendent FUs have been changed. Or user-defined Yes
fied
FB is changed to user-defined FU.
The program itself has not been changed, but de-
Function block
pendent FBs have been changed. Or user-defined Yes
modified
FU is changed to user-defined FB.
Variable The settings of variable or function block instance
Yes
changed used in the POU is changed.
Red
Defined Word The value of Defined word used in the POU is
Yes
changed changed.
The program itself has not been changed, but a de-
pendent input/output has been changed. Otherwise,
information regarding a dependent subsystem com-
I/O changed munication I/O FB, information regarding a PROFI- Yes
NET communication input FB, information regarding
a fire and gas communication input FB, or SCS link
transmission I/O FB has been changed.
The program itself has been newly added. Programs
New added by importing are also regarded as being new- Yes
ly added.
The program became dependent as it shares varia-
bles with a program requiring code review. The pro-
Not modified No
gram itself, dependent functions, function blocks and
inputs/outputs have not been changed.
Yellow
The program name has been changed. No influence
other than the name change. Program name change
Renamed Yes
does not require acknowledgement on the Acknowl-
edge Dialog box.
Green (none) The program is not affected by changes. No
None (*3) Deleted The program has been deleted. Yes
*1: Yes: Displayed in the right pane.
No: Not displayed in the right pane.
*2: When "Instruction modified" is displayed, please contact Yokogawa's service department.
*3: The program has been deleted and the program name is not displayed in Dependency Tree.

TIP If the execution order of programs is changed, or a program is inserted or deleted, all the subsequent pro-
grams are regarded as being changed. Their icons therefore become red, and retesting of the programs is
required.

l Displaying analysis results of Functions and Function Blocks

Dependency Tree displays results of analyzing FUs and FBs as part of the summary for the
program that calls the FUs and FBs.
• Dependency Tree displays only icons for program names. Icons for FUs and FBs are not
displayed.
• If you expand an icon of a program name, the analysis results for the FUs and FBs called
by the program are displayed, in addition to the analysis results of the program itself.
• If FUs and FBs have been changed, the icon of the program name that calls these FUs
and FBs becomes red.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-32
• If a program on which FUs and/or FBs are dependent has been changed, the icon of the
program that calls the FUs and FBs becomes yellow even if no change has been made to
the FUs and FBs themselves.
• If you select a resource (SCS project) in Dependency Tree, "Modified Functions" and
"Modified Function Blocks" in the right pane display changed FUs and FBs, respectively.

n Judging dependencies between POUs

Cross Reference Analyzer judges that there are dependencies between POUs in the following
cases. If dependent POUs have been changed, retesting or review is required even if the pro-
gram itself has not been changed.

l Shared global variables

POUs that share global variables are dependent on each other. POUs are considered to be
sharing global variables in the following cases.
• POUs are reading and writing directly to/from global variables.
• POUs are reading and writing to/from global variables within called FBs.
If multiple POUs satisfy one of the two conditions above for the same global variable, the
POUs are dependent on each other.
The relationship between the global variables and program is displayed in the Current Version
Shared Variable Changes Cross Reference item of the Cross Reference Analysis Report. If
FBs read and write to/from the same global variables, only the name of the program that uses
those FBs is displayed; the names of the FBs are not displayed.

l Use of functions or Function Blocks

If a program calls FUs or FBs, there is a dependency between the calling side and the called
side. For example, if A calls B and B calls C, not only A and B, and B and C that have direct
calling relations, but also A and C, which only have an indirect calling relation, are considered
to be dependent on each other.

n Checking programs (POU)

When you select a program name in Dependency Tree, a list of program statuses is displayed
in the right pane of the window. The list displays the cross reference status (e.g. New, Modi-
fied, Binding Error, Function modified, Function block modified) and acknowledgement status
of the program.

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Program Summary

SCS0101 Status: Modified
SCS0101 Not acknowledged
PROG1
PROG2
Programs
Functions
Function Blocks
Variables
Defined Words

Figure C5.2.3-2 Analysis results of a programs (POU)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-33
Table C5.2.3-2 Meaning of icons displayed on the left side of program names
Icon color Meaning
The program itself or items that are directly depending on it (FU, FB, input/output) have
Red
been changed.
Dependencies requiring review are present in the program (the program has not been
Yellow
changed).
Green The program has not been affected by changes.

n Checking programs
If you select [Programs] in the Dependency Tree, programs dependent on the selected pro-
gram are displayed in a column in the right pane of the window. If multiple variables are
shared among programs, all the variables shared in the programs are displayed in the "Varia-
ble" column.
Check to see if there is any unintended dependencies. For example, if global variables are
shared unintentionally, modify the program to eliminate the dependencies. The programs that
have dependencies but not have been changed are displayed with green icons. It is necessa-
ry to check programs displayed with green icons as well.

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Program Dependencies

SCS0101 Program Variable
SCS0101 PROG1 Count
PROG1 PROG5 Deleted
PROG2 PROG7 VAL
Programs
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG5
PROG6
PROG7
PROG8

Figure C5.2.3-3 Analysis results of programs

In the preceding figure, PROG2 is selected in the Dependency Tree, and dependencies and
changes related to PROG2 are displayed in the right pane of the window.
PROG2 has dependencies on PROG1 and PROG 7. PROG1 has been changed, while
PROG7 has not been changed. Although PROG2 had a dependency on PROG5, the depend-
ency on PROG5 is eliminated in the application to be downloaded.

n Checking functions
If you select [Functions] in the Dependency Tree, FUs and library FUs directly changed or in-
directly affected by changes are displayed in the right pane of the window.
Note that simply changing the order of FUs is irrelevant for the analysis.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-34

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Function Dependencies

SCS0101 Function Comments
SCS0101 Func4
PROG1 Lib1.Func1
PROG2
Programs
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG5
PROG6
PROG7
PROG8

Figure C5.2.3-4 Results of analyzing functions

The preceding figure indicates that PROG2 uses Func4 and Func1 defined in library Lib1.
Func4 has been changed, while Lib1.Func1 has not been changed.
TIP FUs of libraries are displayed using the format "library name.function name."

n Checking Function Blocks

If you select [Function Blocks] in the Dependency Tree, FBs and library FBs directly changed
or indirectly affected by changes are displayed in the right pane of the window.
Note that simply changing the order of FBs is irrelevant for the analysis.

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Function Block Dependencies

SCS0101 Function block Comments
SCS0101 FbOld
PROG1
PROG2
Programs
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG5
PROG6
PROG7
PROG8

Figure C5.2.3-5 Results of analyzing Function Blocks

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

Figure C5.2.3-8 Results of analyzing input/output parameters

The preceding figure shows the following.

• PROG2 uses the variable DI0003.
• The input/output parameters related to DI0003 have been changed.
SEE
ALSO For more information about details on how to check the input/output parameters, refer to:
“n Checking when input/output parameters have been changed” on page C5-40

l Explanation of entries in the Comments column

The format of the entries in the Comments column is explained below.
• For FIO
<Node number>-<slot number><module model>[<channel number>]<wiring informa-
tion><parameter information>
• For N-IO
<Node number>-<unit number><slot number><module model>[<channel number>]<wir-
ing information><parameter information>
Wiring information (omitted if there are no changes)
• New addition: Wiring-Added
• Change: Wiring-Changed
Parameter information (omitted if there are no changes)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-38
• Parameters common to modules have been changed: Module
• Channel parameters have been changed: Channel
• Both are changed: Module Channel

l Extent of influence of input/output parameter changes

The table below shows the influence that changes made to input/output parameters have on
an application logic.

Table C5.2.3-5 Influence of I/O parameters

Classification Example Influence on application logic
Specification of Input Member v of the IO_BOOL and IO_REAL structure of in-
Changes affecting data
Processing at Fault put/output variables is influenced.
Specification of discon-
Member status of the IO_BOOL and IO_REAL structure
Changes affecting data nection detection
of input/output variables, or the system FB notifying the
status specification of short-
status of an inputs and outputs is influenced.
circuit detection
Changes not affecting
Comment No influence on an application logic
application logic

SEE
ALSO For more information about influence on system FBs notifying the status of inputs and outputs, refer to:
“n Influence of input/output changes” on page C5-46

l Changing Scan period

If you change the scan period of an application logic, the system automatically changes all
internal parameters of the N-IO module common area of an SCS. As a result, the analysis re-
sults of Cross Reference Analyzer become as follows.
• The analysis results of all programs accessing the I/O variables that are wired to an N-IO
module become "I/O Changed" and the color of the corresponding program icons be-
comes red.
• "I/O Parameter changes" in the right pane of the window and the "Current Version I/O Pa-
rameter Changes Cross Reference" item of the Cross Reference Analysis Report display
"Module" indicating changes (I/O module common area) for all I/O variables that are
wired to an N-IO module.

n Checking binding variables

If you select [Bindings] in the Dependency Tree, binding variables depending on the selected
program (PROG2 in the following figure) are displayed in the right pane of the window.
These binding variables are used by the program or FBs called by the program.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-39

Cross Reference Analyzer [Pjt:SCS0101]

File Analyze Options

SCS0101 Bindings
SCS0101 Variable Comments
SCS0101 C0101001
PROG1 C0101003
PROG2 CONSU2 Unmatched name (P0102005)
Programs P0102002 Unmatched name (P0102006)
Functions
Function Blocks
Variables
Defined Words
I/O Parameters
Bindings
PROG5
PROG6
PROG7
PROG8

Figure C5.2.3-9 Results of analyzing bindings

The preceding figure shows the following.

• Four variables are used in PROG2 for inter-SCSsafety communication.
• Binding is set properly for C0101001 and C0101003.
• For CONSU2 and P0102002, binding is set with variables that do not match the specified
names.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-40

C5.2.4 Checking with Analysis report

An analysis report displays analysis results in the same order as in Dependency Tree. It also
displays the acknowledgement status set in the Acknowledge Dependencies dialog box. An
analysis report can also be printed.
This section describes how to check dependencies for the following cases:
• When I/O parameters have been changed
• When information related to a subsystem communication I/O FB has been changed
• When information related to a PROFINET communication input FB or fire and gas com-
munication input FB has been changed
• When settings of SCS link transmission have been changed
• When inter-SCS safety communication is used

n Checking when input/output parameters have been changed

The results of analysis when input/output parameters have been changed are displayed in the
"Current Version I/O Parameter Changes Cross Reference" item of the Cross Reference
Analysis Report as a dependency between the input/output variables whose parameters were
changed and programs.
An example of a case where input/output parameters have been changed is shown below.
Example:
DO modules (SDV531) are mounted on slots 3 and 5 of node 2 of an SCS
(1) Parameters in the module common area of slot 3 are changed
(2) Channel parameters of channel 5 of slot 3 and channel 7 of slot 3 are changed
(3) Wiring is added for channel 2 of slot 3 and channel 1 of slot 5
(4) Wiring is changed for channel 3 of slot 3 and channel 2 of slot 5
Assuming the changes outlined in (1) to (4) are made, the Cross Reference Analysis Report
displays as follows:
Current Version I/O Parameter Changes Cross Reference
Variable Comments Used
V020301 2-3 SDV531 [01] Module PROG5 ........................(1)
V020302 2-3 SDV531 [02] Wiring-Added Module PROG5 ........................(3)+(1)
V020303 2-3 SDV531 [03] Wiring-Changed Module PROG5 ........................(4)+(1)
V020304 2-3 SDV531 [04] Module PROG5 PROG6 ..........(1)
V020305 2-3 SDV531 [05] Module Channel PROG6 ........................(2)+(1)
V020306 2-3 SDV531 [06] Module PROG6 ........................(1)
V020307 2-3 SDV531 [07] Module PROG6 ........................(1)
V020308 2-3 SDV531 [08] Module PROG5 PROG6...........(1)
V020501 2-5 SDV531 [01] Wiring-Added PROG7 ........................(3)
V020502 2-5 SDV531 [02] Wiring-Changed PROG7 ........................(4)
V020507 2-5 SDV531 [07] Channel PROG7 ........................(2)
• Variable column
Names of input/output variables.
• Comments column

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-41
The comments are displayed in the following formats:
• For FIO
<Node number>-<slot number><module model>[<channel number>]<wiring informa-
tion><parameter information>
• For N-IO
<Node number>-<unit number><slot number><module model>[<channel num-
ber>]<wiring information><parameter information>
Wiring information (omitted if there are no changes)
• New addition: Wiring-Added
• Change: Wiring-Changed
Parameter information (omitted if there are no changes)
• Parameters common to modules have been changed: Module
• Channel parameters have been changed: Channel
• Both have been changed: Module Channel
• Used column
Displays names of programs accessing relevant input/output variables. If FBs are reading
or writing to/from the input/output variables, only the names of programs using the FBs
are displayed and the names of the FBs are not displayed.

n Checking when information related to a subsystem communication

I/O FB, PROFINET communication input FB, or fire and gas
communication input FB has been changed
After analyzing the changed settings which are relevant to a subsystem communication I/O
FB, PROFINET communication input FB, or fire and gas communication input FB, the
changed settings and their crossed references with programs will be displayed in the section
for "Current Version I/O Parameter Changes Cross Reference" in the Cross Reference Analy-
sis Report.
Example:
A communication module (ALR111M) is located at SCS Node 1, Slot 3 and the follow-
ing variable names are defined:
• Definition 1: SCI_B01 - SCI_B04
• Definition 2: SCO_B01 - SCO_B03
• Definition 3: SCO_I01 - SCO_I04
In this case, implement the following changes.
(1) Parameters for definition 1 are changed (Node1-Slot3).
(2) A wiring for SCO_B04 is added to definition 2 (Node1-Slot3).
(3) A wiring for SCO_I01 of definition 3 is changed (Node1-Slot3).
(4) A new communication module (ALR111M) is added to Node2-Slot4 with a new defi-
nition and wiring SCO_R01 added.
After (1) to (4) are implemented, the Cross Reference Analysis Report display will be
as follows.
Current Version I/O Parameter Changes Cross Reference
Variable Comments Used
SCI_B01 1-3 ALR111M Comm.Def PROG4........................(1)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-42
SCI_B02 1-3 ALR111M Comm.Def PROG4........................(1)
SCI_B03 1-3 ALR111M Comm.Def PROG4........................(1)
SCI_B04 1-3 ALR111M Comm.Def PROG4 PROG6.......(1)
SCO_B04 1-3 ALR111M Wiring-Added PROG7........................(2)
SCO_I01 1-3 ALR111M Wiring-Changed PROG1........................(3)
SCO_R01 2-4 ALR111M Wiring-Added Module PROG1........................(4)
Comm.Def
• Variable column
Names of FB variables.
• Comments column
The format of the entries in the Comments column is explained below.
<Node Number> - <Slot Number> <Module Model> <Wiring Information> <Parameter In-
formation>
Wiring information (omitted if there are no changes)
• New addition: Wiring-Added
• Change: Wiring-Changed
Parameter information (omitted if there are no changes)
• Communication parameters have been changed: Comm.def
• Module parameters have been changed: Module (*1)
*1: For a newly added communication module, Comm.def is shown in addition to Module.

The wiring information and parameter information regarding the changes are indicated as fol-
lows:

Table C5.2.4-1 Wiring information and parameter information regarding the changes
Changes Wiring Information Parameter Information
A communication module has been added (when a
communication definition is added and wired FB is Wiring-Added Module Comm.Def
used in the POU)
Settings for transmission are changed. - -
A communication definition has been added (when
Wiring-Added Comm.Def
wired FB is used in the POU)
A communication definition is deleted. - -
A communication definition is changed. - Comm.Def
An FB has been added Wiring-Added - (*1)
Wiring of a FB has been changed Wiring-Changed - (*1)
An FB has been deleted - -
*1: Comm.def will be displayed if communication definition is changed.

• Used column
The names of programs accessing the corresponding FB variables are shown. When the
FB variables are subject to reading or writing, only the names of the programs using the
FB are shown and the names of the FB are not shown.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-43

n Checking when the settings of SCS link transmission have been

changed
The results of analysis when settings of SCS Link Transmission have been changed are dis-
played in the "Current Version I/O Parameter Changes Cross Reference" item of the Cross
Reference Analysis Report as a dependency between the SCS Link Transmission I/O FBs
whose parameters were changed and programs.
Example:
In SCS Link Transmission Builder, the variables with the following variable names are
defined in Station 2.
• LTSND02001 for the first bit, LTSND02002 for the second bit of Station 2 (Self
Station)
• LTRCV04001 for the first bit, LTRCV04002 for the second bit, LTRCV04003 for
the third bit of Station 4 (SCS)
• LTRCV05001 for the first bit of Station 5 (SCS)
• LTFCS06001 for the first bit, LTFCS06002 for the second bit of Station 6 (FCS)
In this case, implement the following changes.
(1) Add wiring definition (LTSND02003) for the third bit of Station 2.
(2) Change reception timeout of Station 4.
(3) Change input processing at fault in wiring definition (LTRCV04002) for the sec-
ond bit of Station 4.
(4) Move wiring definition (LTRCV04003) for the third bit of Station 4 to the fourth
bit.
(5) Add definition (LTFCSXX04003) for the third bit of Station 4.
(6) Change input processing at fault in wiring definition (LTRCV05001) for the first
bit of Station 5.
(7) Move wiring definition (LTFCS06002) for the second bit of Station 6 to the third
bit.
(8) Add Station 7 (SCS), add wiring definition LTRCV07001 and LTRCV07002 for
the first bit and the second bit of Station 7.
After (1) to (8) are implemented, the Cross Reference Analysis Report display will
be as follows.
Current Version I/O Parameter Changes Cross Reference
Variable Comments Used
LTSND02003 LT02-003 Wiring-Added PROG7...(1)
LTRCV04001 LT04-001 Station PROG4...(2)
LTRCV04002 LT04-002 Station LinkTrans.Def PROG4...(2) + (3)
LTFCSXX04003 LT04-003 Wiring-Added Station PROG4...(2) + (5)
LTRCV04003 LT04-004 Wiring-Changed Station PROG4...(2) + (4)
LTRCV05001 LT05-001 LinkTrans.Def PROG6...(6)
LTFCS06002 LT06-003 Wiring-Changed PROG2...(7)
LTRCV07001 LT07-001 Wiring-Added Station PROG3...(8)
LTRCV07002 LT07-002 Wiring-Added Station PROG3...(8)
• Variable column
Variable names of SCS Link Transmission I/O FBs

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-44
• Comments column
The notational convention in the Comments column is explained below.
LT<SCS Station Number (2 digits)> - <Bit Number (3 digits)><Wiring Information><Pa-
rameter Information>
Wiring information (omitted if there are no changes)
• New addition: Wiring-Added
• Change: Wiring-Changed
Parameter information (omitted if there are no changes)
• Change of reception timeout, transmission timeout or pre-alarm set point: Station
• Change of input processing at fault: LinkTrans.Def
• Both: Station LinkTrans.Def
The wiring information and parameter information regarding the changes are indicated as fol-
lows:

Table C5.2.4-2 Wiring information and parameter information regarding the changes
Change Wiring Parameter Remarks
Add Station Wiring-Added Station Detect when wired FB is used in POU
Delete Station - - Do not detect
Change Station Type Wiring-Added Station Detect when wired FB is used in POU
Change Station Param- Change of reception timeout, transmission
- Station
eter timeout or pre-alarm set point

Add SCS Link Trans- -(*1) Detect when wired FB is used in POU
mission I/O FB varia- Wiring-Added Change of reception timeout, transmission
bles to Wiring Definition Station (*1)
timeout or pre-alarm set point
Delete SCS Link Trans-
mission I/O FB varia-
- - Do not detect
bles from Wiring Defini-
tion

Move SCS Link Trans- -(*1) Detect when wired FB is used in POU
Wiring-
mission I/O FB varia- Change of reception timeout, transmission
Changed Station (*1)
bles of Wiring Definition timeout or pre-alarm set point
LinkTrans.Def Change of input processing at fault
Change Wiring Parame- Change of input processing at fault, recep-
- Station Link-
ter tion timeout, transmission timeout or pre-
Trans.Def
alarm set point
*1: When adding a wiring, changing a wiring or changing the input processing at fault, LinkTrans.Def will be omitted.

• Used column
Displays names of the programs accessing the variables of SCS Link Transmission I/O
FBs. When accessing the SCS Link Transmission I/O FBs from FU or FB, only the names
of programs using the FUs or FBs are displayed and the names of the FUs or FBs are not
displayed.

n Identification of programs when Inter-SCS safety communication is

used
Inter-SCS safety communication is implemented using FBs for communication and binding
functions. In a communication configuration, the SCS sending data is called the producing
side and the SCS receiving data is referred to as the consuming side.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-45

PROD_B CONS_B

X IN BVAR OUT Y
Binding Association Binding
BOOL variable (binding) variable VAL BOOL
variable variable
BVAR P0101001 C0101001 OUTT
DLYT NR

SCS 1 (producing side) SCS 2 (consuming side)

Figure C5.2.4-1 Inter-SCS communication (Example of BOOL-type variable)

The producing side and the consuming side share data using inter-SCS safety communica-
tion; they are thus dependent on each other. For this reason, if a program on the producing
side has been changed, it is necessary to perform retesting or review of programs on the con-
suming side.
The procedure for identifying programs that may be affected is shown below.
1. Check programs displayed with red or yellow icons in Dependency Tree on the producing
side.
2. Check variables for inter-SCS safety communication used in these programs.
The "Current Version Bound Variable Usage" item of the Cross Reference Analysis Re-
port shows binding variables used in each program. Variables starting with the letter P are
variables on the producing side.
3. Check whether or not specified data has been changed for variables starting with the let-
ter P in each program.
If there are no changes in the specified data, the review of binding variables is finished.
4. Variables on the consuming side corresponding to binding variables whose data has been
changed (variables starting with the letter P) have the same names as the binding varia-
bles, except that P is replaced with C.
5. Check the programs starting with the letter C that use the binding variables explained in
step 4 in the "Current Version Bound Variable Usage" item of the Cross Reference Analy-
sis Report.
These programs and dependent programs are the targets of retesting or review.
6. Dependent programs are displayed in Dependency Tree by expanding the [Programs].
Current Version Bound Variable Usage
Program Bound variables
PROG1 P0101001
PROG2 P0101002 P0101003
PROG5
PROG6
PROG7 P0101004
PROG8

Figure C5.2.4-2 Current Version Bound Variable Usage of Cross Reference Analysis report (Example
of producing side)

Current Version Bound Variable Cross Reference

Bound variables Used
C0101001 PROGA
C0101002 PROGA
C0101003 PROGB
C0101004 PROGC

Figure C5.2.4-3 Current Version Bound Variable Cross-Reference item of Cross Reference Analysis
report (Example of consuming side)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-46

C5.2.5 Precautions on Cross Reference Analyzer

Cross Reference Analyzer cannot detect certain changes.
This section explains changes that are not detected by Cross Reference Analyzer and actions
to be taken, and shows examples of procedures for checking such changes.
The user must check the following for SCS projects.
• Influence of input/output changes
• Change in tag name defined to allow manipulation from HIS
• Other changes not detectable by Cross Reference Analyzer
If library projects have been changed, it must be checked whether or not there are changes
for the library projects as well.

n Influence of input/output changes

Cross Reference Analyzer detects changes of input/output parameters and shows dependen-
cies related to input/output variables.
However, it does not detect dependencies between inputs/outputs and system FBs that indi-
cate input/output status.
These system FBs show the status of I/O corresponding to the node numbers, unit numbers,
slot numbers and channel numbers specified for I/O variables.

Table C5.2.5-1 System Function Blocks related to inputs/outputs

Type name Description
SYS_NODEST I/O channel data status indicator in FIO node
SYS_N_NODEST All I/O channel data status indicator in N-IO node
SYS_NODEINF FIO node status notification
SYS_N_NODEINF N-IO node status notification
SYS_OUTST, SYS_OUTST16 FIO output module data status
SYS_N_IOST16 N-IO I/O module data status for 16 channels
SYS_INST Detects fault in input module channels
SYS_CHST Detects fault in channels
SYS_IOSD Shuts down FIO output module output
SYS_N_IOSD Shuts down N-IO I/O module output
SYS_OUTEN FIO output module output enabled status
SYS_N_OUTEN N-IO I/O module output enabled status
SYS_IOMDSP FIO module status notification
SYS_N_IOMDSP N-IO module status notification
SYS_ALRDSP Outputs status of subsystem communication modules
SYS_LTSTS SCS link transmission reception status monitor (*1)
*1: SYS_LTSTS will be affected by the setting change of SCS Link Transmission definition instead of the setting change of I/O.

If you change input/output parameters, the status of the inputs/outputs may change, which
means that the output of these system FBs may change. In other words, such inputs/outputs
and system FBs are dependent on each other.
Cross Reference Analyzer is unable to show dependencies between changes to input/output
parameters and system FBs. If you are going to change input/output parameters, check
whether or not performing such changes to input/output parameters affect other system com-

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-47
ponents before downloading them to an SCS. An example of checking procedure is shown
below.
1. Select a resource (SCS project) name in Dependency Tree of Cross Reference Analyzer.
2. Check "I/O Parameter Changes" displayed in the right pane of the window.
If no input/output variables are changed, checking is finished.
3. If there are input/output variables that have been changed, check programs that use sys-
tem FBs related to the inputs/outputs, and then judge whether the changes of the input/
output parameters affect them. If it is judged that the FBs are affected, check the pro-
grams depending on the program in question by expanding relevant [Programs] in De-
pendency Tree and retest the programs depending on the program in question.

n Change in tag name defined to allow for manipulation from HIS

From HIS instrument faceplates for "Override FB", "Grouping Override FB", "Password FB"
and "Manual operation FB", you can change the variables in the application logic.
To allow manipulation from HIS, tag names for those FBs are set by Tag Name Builder. Even
if a user changes the tag name, the change is not detected by Cross Reference Analyzer.
Check whether or not tag names have been changed. Whether or not tag names have been
changed can be checked by comparing the modified project data to the master database by
means of Project Comparing Tool. Check can also be made by using output of self-documen-
tation. An example of checking procedure by using output of self-documentation is shown be-
low.

l Preparation
Prepare the information before changes are made. That is, printout of the tag names of over-
ride FBs, grouping override FBs, password FBs, manual operation FBs and their correspond-
ing internal variables (including POU names), which was printed by using the self-documenta-
tion function.

l Checking procedure at online change download

1. If you change a tag name, a diagnostic information message is displayed to notify the tag
name change at online change download. Check whether or not messages indicating tag
name changes are displayed in the Diagnostic Information window of SCS Maintenance
Support Tool.
If no diagnostic information messages notifying tag name changes are displayed, no tag
names have been changed. Checking is finished.
2. If diagnostic information messages notifying tag name changes are displayed, check that
the tag names in the messages match with the intended changes.
3. Check programs of the application logic corresponding to the changed tag names in Dic-
tionary View of SCS Manager. Test the checked program, as well as the programs that
depend on the checked program. Check dependent programs by expanding the relevant
[Programs] in Dependency Tree of Cross Reference Analyzer.
4. Print and store the printed documents for the next offline download.

l Checking procedure at offline download

In case of offline download, compare the printed and saved list of tag names using the self-
documentation function and the current status, and check the differences.
1. Display the current list of tag names in Tag Name Builder. Alternatively, print the list by
using the self-documentation function.
2. Compare the current tag names with the tag names printed and saved in advance.
If there are no differences, checking is finished.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-48
3. If there are differences, check programs of the application logic corresponding to the
changed tag names in Dictionary View of SCS Manager. Test the checked program, as
well as the programs that depend on the checked program. Check dependent programs
by expanding the relevant [Programs] in Dependency Tree of Cross Reference Analyzer.
4. Print and store the printed documents for the next offline download.

n Other changes not detectable by Cross Reference Analyzer

Cross Reference Analyzer does not detect differences in items other than the definitions of
the application logic. So, you need to check for changes using Project Comparing Tool or the
output of self-documentation. Especially for the following definitions that are significant on
safety, the user must check for changes before downloading to an SCS.
• Scan period for the application logic execution functions (defined in the Settings tab of
Resources Properties in Link Architecture View)
• Use of optical ESB bus repeaters and their maximum extension distance (defined on
SCS Constants Builder and I/O Parameter Builder)
• Extend scan period automatically (defined on SCS Constants Builder)
• Locking of internal variables (defined for SCSP2 on SCS Constants Builder)
• Behavior at abnormal calculation (defined on SCS Constants Builder)
• Automatic IOM download (defined on SCS Constants Builder)
• Device Power-Off Period (defined with SCS Constants Builder)
• Device Startup Waiting Period (defined with SCS Constants Builder)
• Alarm Suppression During Device Reset (defined with SCS Constants Builder)
• Fire and gas communication startup time (defined with SCS Constants Builder)
An example of checking procedure by using the output of self-documentation is shown below.

l Preparation
Prepare the information before changes are made. That is, printout of the settings of Resour-
ces Properties in Link Architecture View and definitions made on SCS Constants Builder,
which was printed by using the self-documentation function.

l Procedure before download

1. On SCS Manager, open Resources Properties in Link Architecture View and click the
[Settings] tab. The scan period (cycle time) is shown in the tab page; so compare it with
the scan period in the printout you kept to see if there is difference.
2. Open SCS Constants Builder. In the [SCS] tab page, the above mentioned definitions are
shown. Compare them with those in the printout you kept and check for difference.
3. To be prepared for the next time, use the self-documentation function to print out the SCS
project properties and definitions made on SCS Constants Builder and keep it.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-49

C5.2.6 Comparison with the original project

Cross Reference Analyzer has the function to compare the work database with the master da-
tabase of another SCS project, which allows you to verify that there is no difference between
the regenerated SCS project and the original project.
This function eliminates the need to retest all the POUs in the case, for example, when an
existing project is recreated in order to add a newly supported input/output module to it.
Place the original project at a location that is accessible by the SENG and specify it as the
project to be compared; then run the analysis by Cross Reference Analyzer. You don't need to
open the original project on SCS Manager or re-set the paths to the libraries.
An example of the comparison procedure is shown below.

n Procedure for comparison with the original project

From the [Analyze] menu of the Cross Reference Analyzer, select [Compare with Original
Project]. When Compare with Original Project starts up, a dialog box appears, prompting you
to specify the top path to the SCS project which you want to compare. Specifying the path to
the SCS project and clicking [OK] starts the comparison. The work database of the project
you are working with on SCS Manager is compared with the master database of the project
you have specified.

Browse for Folder

Select SCS Project For Analysis

Microsoft Works
Microsoft.NET
Movie Maker
MSBuild
MSDN
MSN Gaming Zone
MSXML 4.0
MSXML 6.0
NetMeeting
NextFTP
NOS
Online Service
Outlook Express
ProSafe-RS
Projects
Shared

OK Cancel

Figure C5.2.6-1 Dialog box for selecting the path to the original project

However, note that the comparison is performed only when the target names (SCS_TARGET/
SCS_SIMULATOR) match between the project you are working with on SCS Manager and
the project specified for comparison. If the target names do not match, Cross Reference Ana-
lyzer regards it as an error and the analysis fails. When all POUs have been acknowledged
through comparison with the original project, you can download the project to an SCS. After
downloading is completed, if you display the analysis results using the previous analysis re-
sult displaying function of Cross Reference Analyzer, the results of comparison with the origi-
nal project will be shown.

n Indication on Cross Reference Analyzer

If you have run the analysis by using the [Compare with Original Project] command, the indi-
cation on the Cross Reference Analyzer window and the printout of the analysis report will be
as shown below. You can identify the original project that is used for comparison from these
indications.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C5.2 Cross Reference Analyzer > C5-50
• Path to the original project is shown on the title bar.

Cross Reference Analyzer [Pjt: SCS0214] [Pjt2: C\RS-Projects\MYRSPJT\SCS0214]

File Analyze Options

Figure C5.2.6-2 Title bar

• Path to the original project is printed in the report

Application Logic Cross Reference Analysis Report

Project : SCS0214
Original Project Path: C:\RS-Projects\MYRSPJT\SCS0214
Configuration : SCS0214
Resource : SCS0214 (214)
Project Build Date : 2009/12/24 9:10:32
Project Analysis Date : 2009/12/25 14:14:19
Report Date : 2009/12/25 14:17:27
User : user1

Figure C5.2.6-3 Report

n Notes on comparison
If you add or delete programs after you creating a new project and importing data to it, all the
programs following the added or deleted program will be regarded as changed programs dur-
ing comparison with other project. When you create a new project and import data to it, use
Cross Reference Analyzer to compare the created project with the original project and down-
load it to the SCS before you make any further changes.

n Checking the regenerated project

Use Cross Reference Analyzer to verify the equivalence between the regenerated project and
the original project. For the data that cannot be verified by Cross Reference Analyzer, you
need to check that the regenerated SCS project and the original SCS project are the same by
means of Project Comparing Tool. If you have made further changes to the regenerated proj-
ect, perform checking using Cross Reference Analyzer and self-documentation output to
make sure the range of retesting, as should be done with the earlier revisions.
SEE
ALSO For more information about procedures for checking a regenerated project and the definition items of the proj-
ect that need to be checked, refer to:
• E3.3, “Data transfer procedure during SCS project regeneration” on page E3-9
• C5.2.5, “Precautions on Cross Reference Analyzer” on page C5-46

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C6. Simulation tests> C6-1

C6. Simulation tests

Applications should be tested in the simulator running on SENG by using the logic simulation
test or the SCS simulation test. When running an SCS simulation test on SCS projects with
Current Project attribute, create an SCS project for testing by using the Test Project Creation
Tool as preparation for the test. Register the SCS project for testing in an AD project for test-
ing.
Application logic can be debugged with the Application Debug Function, Forcing of I/O varia-
ble and Online Monitoring Function. In the logic simulation test or the SCS simulation test, I/O
channels are equivalent to being locked all the time. In the logic simulation test or the SCS
simulation test, connect iDefine by using the iDefine Test Manager and you can use the
iDefine test functions to test the parts created in iDefine.
SEE
ALSO For more information about logic simulator test operations, refer to:
2., “Logic simulation test operations” in Test Function Guide (IM 32P04B30-01EN)
For more information about preparing and running SCS simulation tests, refer to:
3., “SCS simulation tests” in Test Function Guide (IM 32P04B30-01EN)
For more information about the operations for using iDefine in simulation tests, refer to:
6., “Using iDefine in tests” in Test Function Guide (IM 32P04B30-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-1

C7. Offline download to the target SCS

During offline download, the SCS database, which contains all the information required for op-
eration of an SCS, is transmitted from the SENG to the SCS; meanwhile, the SCS functions
are stopped. The SCS database is downloaded via the control bus and stored in the flash
memory of the SCS and the non-volatile memory of input/output modules. The SCS database
downloaded to the SCS is saved as the master database together with the source files in the
SENG.

n Downloaded items
• SCS system programs
• Application database
The application database created by the Safety application definition function and
CENTUM integration function is downloaded to the CPU module.
• I/O configuration information
The parts of the database created by the I/O definition function related to input/output
modules are downloaded to the input/output modules.

SENG

Hard disk
Application database
I/O
configuration information SCS system programs

SCS

I/O configuration I/O configuration SCS system Application

information information program database

Non-volatile memory Non-volatile memory Flash memory

Input/output module Input/output module CPU module

Figure C7-1 Offline download

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-2

CAUTION
Following operations are performed if you execute offline download. Preventive actions to pre-
vent false trip are required before executing offline download.
• Functions running on the SCS stop, and all the output modules output the fail-safe values
that are specified in I/O parameters.
• Inter-SCS safety communication is disconnected.
• The forcing function is cancelled.
• Override from the HIS is cancelled.
• Break points set by the target test function are cancelled.
• SOEs and diagnostic information collected so far in the SCS are deleted (they are saved
in the battery backup memory, though).
• Password for changing the SCS security level is deleted.

n Procedure for offline download

This section describes procedures from building an application logic to performing offline
download.

IMPORTANT
Perform Clean Project in a timely manner; specifically, before FAT (Factory acceptance tests)
or SAT (Site acceptance tests). Before you execute offline download, we recommend you per-
form Clean Project.

SEE
ALSO For more information about clean project, refer to:
Cleaning Projects” in “Build” in “Code Generator” in “Workbench” in the Workbench User’s Guide

l What to do before offline download

Build the application logic and analyze it by using Integrity Analyzer and Cross Reference An-
alyzer.
TIP The items that may require retesting but not detected by Cross Reference Analyzer must be checked by the
user.

IMPORTANT
Call up the SCS Information dialog box and confirm that the number of logical I/O points in
use does not exceed the number of assigned I/O licenses.

If the target SCS is running, set the SCS security level to Level 0 by using the SCS Security
Level Management Function.

l Start the offline download

1. From the [Debug] menu of SCS Manager, select [Download].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-3
On the CENTUM Integration, a dialog box asking you if you want to save Operation Mark
or not appears.
2. Save Operation Mark if necessary.
TIP • If Integrity Analyzer or Cross Reference Analyzer has already been launched when you start offline
download, a message prompting to close the analyzer is notified and the download ends with an error.
• If the SCS security level is Level 1 or Level 2 when you start offline download, a message prompting to
set Level 0 is notified and the download ends with an error. Set the SCS security level to "0" and start
offline-downloading.
• If the I/O Lock window or Inter-SCS Communication Lock window is left open when you start offline
download, an error message appears and the download processing ends.

3. A dialog box asking you if you are sure to start an offline download appears. Click [OK].
A dialog box for setting a password for changing the SCS security level appears. After
that, a dialog box prompting you to manage versions of the SCS project appears.
When an offline download completes, SCS is restarted. The SCS database offline down-
loaded to the SCS is automatically stored in SENG as a master database together with
source files.
4. On the CENTUM Integration, download the database of the CENTUM project also.

l Dealing with the offline download confirmation dialog box

The system checks to see if there is a possibility that the online change variables area in the
database has been used before executing the offline download. If the online change variables
area is used, a confirmation dialog box appears. This situation can be solved by performing a
clean project and a build.
In the confirmation dialog box, select [Cancel] to terminate the offline download processing.
Perform a clean project and a build, and then execute offline download. The offline download
starts when you click [OK] in the confirmation dialog box.

l Offline download process in I/O list engineering

When you execute an offline download of an SCS project that was created with I/O list engi-
neering, the status of the safety I/O list, safety communication I/O list, and the IOM informa-
tion are checked. More specifically, whether the safety I/O list, safety communication I/O list,
and IOM information were edited after the builds by Generation Manager succeeded is
checked. If it corresponds to the check items, an error occurs and the offline download stops.
If the safety I/O list, safety communication I/O list, and IOM information cannot be checked
due to disrupted communication with the AD Server, a warning will appear but you will still be
able to download the project. After the connection with the AD Server is restored, the system
will check whether any offline download was run during the connection interruption if either of
the following measures is taken:
• Use the System Structure Navigator in AD Organizer and execute the update function of
the Revision History Utility.
• Use SCS Manager to open the SCS project.
If an offline download is performed during the connection interruption, a warning appears
when the corresponding SCS project is opened in SCS Manager. This warning will disappear
if the build and download are performed.
When the offline download succeeds, labels are set to the safety I/O list, safety communica-
tion I/O list, and IOM information. The label represents a character string as mentioned below.
SCS Project Name-Download-Date and Time

l End the offline download

Set the passwords used when changing the SCS security level.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-4
Manage the operation history by using the operation history management utility of AD Organ-
izer. Check-in the SCS project with the Version Control Tool.
SEE
ALSO For more information about the operation history management utility of AD Organizer, refer to:
C2.6, “Operations of the revision history function” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about the version control tool, refer to:
F5., “Version control” in Engineer's Reference Manual (IM 32P04B10-01EN)

n Security of SCS
SCS security levels provide adequate security through specifying the passwords. Passwords
for different security levels can be set for each SCS.
• Setting and changing passwords
• Changing SCS security levels
Note that it is necessary to return the SCS security level to Level 2 before closing an SCS
project.
This section describes how to set passwords for changing SCS security levels and how to
change the levels.

IMPORTANT
No password has been set after executing offline download and master database offline
download. Make sure to set passwords again.

TIP The access to SCS is controlled by SCS itself according to its security level. Operations on the SENG is not
be prohibited according to the SCS security level, however.

l How to set and change passwords

The password that is used to change the SCS security level is stored within the SCS. This
password can be set or changed from the Set SCS Security Level dialog box.

IMPORTANT
No password has been set after executing offline download and master database offline
download. Make sure to set a password at this stage.

1. Select [Maintenance] from the [Tools] menu of SCS Manager.

The Maintenance Launcher menu appears.
2. Select [Set SCS Security Level] from the Maintenance Launcher menu.
The Set SCS Security Level dialog box appears.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-5
Set SCS Security Level

Current Level: 2

New Level: 1

Password: ****************

OK Cancel Change Password...

Figure C7-2 Set SCS Security Level dialog box

3. Click the [Change Password] button.

The Change SCS Security Level Password dialog box appears.

Change SCS Security Level Password

Level: 1

Old Password: ****************

New Password: ****************

Confirm New Password: ****************

OK Cancel

Figure C7-3 Change SCS Security Level Password dialog box

4. Select the security level for which you set a password in [Level:].
It is necessary to set one password for changing to Level 1 and one for Level 0, respec-
tively.
5. Enter the current password in the [Old Password:] field.
6. Enter a new password in the [New Password:] field, and once again in the [Confirm New
Password:] field.
The passwords you have entered appear as a series of asterisks (*).
You must enter a combination of up to 16 alphanumeric one byte characters and ASCII
symbols(*1). You need to Distinguish between capital letters and small letters. You do
not need to enter [Old Password:] if you have not set any password before, or if you
have just executed an offline download or a master database offline download.
*1: ASCII symbols include the space character and the following one byte characters:
! " # $ % & ’ ( ) * + , - . / : ; < = > ?@ [ \ ] ^ _ ` { | } ~

7. Click the [OK] button.

The confirmation dialog box appears.

SCS Manager

The password will be changed. OK?

Domain : 01
Station : 24

OK Cancel

Figure C7-4 Confirmation dialog box

8. Click the [OK] button.

Both new and old passwords will be sent to SCS. If the password is successfully
changed, the dialog box notifying the success appears. The new password becomes val-
id. If the password change fails, a dialog box will be displayed to notify the failure.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-6

l How to change SCS security levels

The SCS security level can be changed in the Set SCS Security Level dialog box of SCS
Manager.
The table below shows the combinations of levels for which security level changes are al-
lowed via operations on the Set SCS Security Level dialog box.

Table C7-1 Security levels that can be changed through operations in the Set SCS Security Level dia-
log box
Current SCS security New SCS security level (*1)
level Level 2 Level 1 Level 0
Level 2 - Yes (*2) Yes (*2)
Level 1 Yes (*2) - Yes (*2)
Level 0 Yes(*3) No -
*1: Yes: The security level can be changed.
No: The security level cannot be changed.
*2: The security level can be changed to the target SCS security level.
*3: Security level changes can be made only in SCS simulator.

To change the security level, you need to enter the password. However, you don’t need to en-
ter a password when changing the security level from Level 1 to Level 2.
You cannot raise the security level from Level 0 to Level 2 from the Set SCS Security Level
dialog box. In SCS Simulator of SCS Test Functions, however, you can raise from Level 0 to
Level 2 on the Set SCS Security Level dialog box. This operation does not require a pass-
word.

CAUTION
To set the SCS security level back to Level 2 after changing to Level 0, you must restart the
SCS, execute offline download, or execute master database offline download. In particular, be
sure to execute offline download if you used break points in debugging of the application log-
ic.
These operations require stopping of the system. When you change the security level to Level
0, do so very carefully considering the consequences of the system stop.

The SCS security level can be changed in the following procedure.

1. In SCS Manager, open an SCS project whose security level you want to change.
2. Select [Maintenance] from the [Tools] menu of SCS Manager.
The Maintenance Launcher menu appears.
3. Select [Set SCS Security Level] from the Maintenance Launcher menu.
The Set SCS Security Level dialog box appears. The current security level is displayed in
[Current Level:]; this item is display only and cannot be changed.

Set SCS Security Level

Current Level: 2

New Level: 1

Password: ****************

OK Cancel Change Password...

Figure C7-5 Set SCS Security Level dialog box

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-7
4. Select the security level you want in [New Level:] and enter the password for the level
you want in [Password:] text box.
All characters you enter are displayed as asterisks (*).
5. Click the [OK] button.
The confirmation dialog box appears.

SCS Manager

Is it OK to set to Level 1 ?
Domain : 01
Station : 24

OK Cancel

Figure C7-6 Confirmation dialog box (when changing to Level 1 or Level 2)

SCS Manager
Is it OK to set to Level 0 ?
WARNING: [Restart SCS] or [Offline Download] is mandatory
to switch back to Level 2 (normal operation) later.
This will turn all output channels OFF.
Domain : 01
Station : 24
OK Cancel

Figure C7-7 Confirmation dialog box (when changing to Level 0)

6. Click the [OK] button.

When changing the security level to Level 0, the following dialog box appears to confirm
the change again. When you set the level back to Level 2 from Level 0, the system stops.
Confirm that this does not cause any problems. To proceed with the change, click [OK].

Set SCS Security Level

[Restart SCS] or [Offline Download] is mandatory for user to
set to Level 2 from 0.
WARNING: This will turn all output channels OFF when switching
back to normal operation.
Is it really OK?
OK Cancel

Figure C7-8 Dialog box confirming change to Level 0

If the security level of SCS is changed, the message showing the result of change is dis-
played.
The error message is displayed if the security level could not be changed.

l Confirming the SCS security level reset by SCS Manager

If the security level of SCS project currently opened in SCS Manager is not Level 2, the confir-
mation dialog box prompting to reset the security level to Level 2 appears when closing it.

IMPORTANT
This dialog box is for confirmation only. Open the corresponding SCS project again and
change the security level using the Set SCS Security Level dialog box.

The confirmation dialog box appears in the following timings.

• When closing an SCS project by exiting SCS Manager

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C7. Offline download to the target SCS > C7-8
SCS Manager

Security level remains at Level1.

Figure C7-9 Example of Confirmation dialog box (when closing by exiting SCS Manager)

Clicking the [OK] button to exit SCS Manager leaves the security level unchanged.
• When closing an SCS project by opening another SCS project

SCS Manager

Security level remains at Level1.

Close SCS project?

OK Cancel

Figure C7-10 Example of Confirmation dialog box (when closing by opening another SCS project)

Click the [OK] button to close the currently opened SCS project without changing its se-
curity level, and then open another SCS project.
Click the [Cancel] button to keep the currently opened SCS project opened, and another
SCS project will not open.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C8. Output enable operation> C8-1

C8. Output enable operation

How to enable the outputs, the detailed procedure and how to start the output module will be
explained in this section.
TIP In this document, I/O shutoff switch and DO shutoff switch of the universal type I/O module are referred to as
an output shutoff switch.

n Overview on Output enable operation

When the operating mode of SCS is Waiting mode, some output channels are in Output Disa-
ble status, so that they cannot output the application logic results. Moreover, after SCS is star-
ted, the inter-SCS safety communication cannot send data to consumer side, the SCS Link
Transmission and the subsystem communication cannot function either.
The Output Enable Operation will enable the output channels to output the application logic
results, will start the inter-SCS safety communication, the SCS link transmission and the sub-
system communications.
Output Enable operation can be performed for the whole SCS only. The output channel can-
not be specified individually. Therefore, you cannot enable only one of the inter-SCS safety
communication, SCS Link Transmission or subsystem communication.

n Enabling output
Click the [Output enabled] button in the I/O Channel Status dialog box; the processing result
of the application logic is output to the field and the SCS operating mode changes to the Run-
ning mode. Note that all nodes, all output modules and all channels must be in normal status
in order for the SCS to be changed to the Running mode. If there is any error, the status does
not change even if you perform the Output Enable Operation.
SEE
ALSO For more information about I/O Channel Status dialog box, refer to:
H4., “Displaying I/O channel status” on page H4-1

n Start output module operation

If an error serious enough to activate the Output Shutoff switch occurs, there is a case where
the output module stops its output and waits for the Output Module Start depending on an er-
ror cause. Perform the Start Output Module operation to start the output modules whose out-
put is stopped.
The Start Output Module operation is performed individually. It can be performed regardless
of the SCS security level.
The SCS continues to be in the Waiting mode even after the Start Output Module operation is
completed. The channel in the Output Disable status will not change to Output Enable, either.
Perform the Output Enable operation to change channels in the output disabled state to the
output enabled state.
Note that this Start Output Module operation does not influence the output modules of which
the Output Shutoff switch has not been actuated.
1. Select the output module whose output is stopped in Hardware Configuration Tree View
of the SCS State Management window. Click [Start output module] button on the toolbar.
After this is confirmed using the Confirmation dialog box, the selected output module
starts up. The output from all channels will continue to be "0" even after the output mod-
ule starts up.
2. Perform the output enable operation.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C8. Output enable operation> C8-2
The output module is connected to the output of application logic and the result of the ap-
plication logic is output from the module.

n Enable Output operation

• Each output channel of SCS has two statuses, Enabled Output and Output Disabled,
when the output is disabled, the output from application logic is not connected to the ac-
tual output channel, and OFF or pre-specified fail safe value is output to the field.
Perform the Enable Output Operation to connect the output values from the application
logic to the output channels. All normal outputs (DO module channels, AO module chan-
nels, Subsystem Communication output) are enabled by the output enable operation from
an SENG.
When SCS starts, all output channels are in the output disabled status.
• Transmission is started in the inter-SCS safety communication and subsystem communi-
cation output by the first output enable operation after SCS startup.
• When an output module fails, all output channels on the output module enter the output
disabled status.
When an output channel fails, the output channel enters the output disabled status.
• In the case of subsystem communication, it does not result in the output disabled status
even if an error occurs in the subsystem communication (communication module error or
communication error).
• The output enable operation can be performed from the application logic using a system
function block. There are two types of function blocks that can perform the output enable
operation: SYS_STAT, which enables safety outputs and outputs in inter-SCS safety com-
munication, and SYS_STAT_SC, which enables subsystem communication outputs. Use
these system function blocks and perform the output enable operation if it is desired to
have different output start timings for output modules and the subsystem communication.
SEE
ALSO For more information about specifications of SYS_STAT, refer to:
12.1, “SYS_STAT (SCS status management)” in POU Reference Manual (IM 32P03B20-01EN)
For more information about specifications of SYS_STAT_SC, refer to:
13.13, “SYS_STAT_SC (subsystem communication output status indicator)” in POU Reference Manual
(IM 32P03B20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<C9. Target tests> C9-1

C9. Target tests

In a target test, the application logic is tested on the actual SCS. SCS Manager is used to
perform test operations and display the statuses and the results. Testing by overriding from
HIS is performed in an environment where ProSafe-RS is integrated with CENTUM. The tar-
get test function of CENTUM can be used as necessary. For the parts that were created by
using iDefine, connect iDefine and SCS through the iDefine Test Manager in AD Organizer
and run the test using the iDefine test function.

IMPORTANT
Target tests are mandatory for ProSafe-RS. The user must test the application in target tests
at the final stage.

To use all the functions provided in the test function instead of simply monitoring, set the SCS
security level to Level 0. The same applies when using the iDefine test function.
• Application logic can be debugged with the Application Debug Function, Forcing of I/O
variable and Online Monitoring Function.
• Application can be executed without mounting I/O modules or wiring field devices when
the Forcing Function for the I/O modules is used.
• Application logic can be debugged using the Forcing Function for I/O variables by chang-
ing conditions of the application logic.
By using the target hardware, perform tests on all signal paths and logics (FU/FB).
SEE
ALSO For more information about target test operations, refer to:
4., “Target tests” in Test Function Guide (IM 32P04B30-01EN)
For more information about the operations for using iDefine in target tests, refer to:
6.4, “Using iDefine in target tests” in Test Function Guide (IM 32P04B30-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D. Procedures to create applications using the I/O list engineering method> D-1

D. Procedures to create applications

using the I/O list engineering
method
This part gives an overview of the procedures of AD Organizer when using I/O list engineer-
ing and the procedures when using iDefine.
The safety I/O list and safety communication I/O list are used in the engineering process. Ac-
quire the safety I/O list and safety communication I/O list from the customer or create a new
one.
The user can use the safety I/O list to make definitions based on the P&ID tag name in the
application, and proceed to build the application without having to wait for the detailed design
of the I/O module or the data communication. By using a safety communication I/O list, you
can define communication modules and proceed with building the application.
In the Safety I/O Editor, you can import and edit the safety I/O list that you have prepared in
advance or create a new safety I/O list.
In the Safety Communication I/O Editor, you can import and edit the safety communication I/O
list that you have prepared in advance or create a new safety communication I/O list.
In the IOM Definition Editor, you can assign SCS nodes and input/output modules.
The changes made in AD Organizer editors can be reflected in SCS projects by using Gener-
ation Manager.
With I/O list engineering, you can also use iDefine to create application logics.
Create an application logic by using iDefine based on the IOM information that was defined in
AD Organizer and reflect the application logic in SCS by using AD Organizer.
SEE
ALSO For more information about Generation Manager, refer to:
D4., “Overview of RS generation” on page D4-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1. Engineering based on the safety I/O list> D1-1

D1. Engineering based on the safety I/O

list
In I/O list engineering, you can create and edit safety I/O lists by using AD Organizer.
The engineering data is reflected in the SCS project by using the RS Generation Manager of
AD Organizer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.1 Overview of I/O list engineering> D1-2

D1.1 Overview of I/O list engineering

You can create a safety I/O list based on the I/O information list, containing information about
AIO, DIO, and so on, that is obtained from the plant designer.
A safety I/O list is created by defining safety I/O in the Safety I/O Editor and then importing
the I/O information list. In the Safety I/O Editor, one row is displayed for each I/O point, show-
ing the information that identifies whether it is input or output.
Follow these steps to create a safety I/O list:
1. Start up the Safety I/O Editor.
2. Import the I/O information list to the safety I/O list.
When imported, the setting items in the I/O information list, which is provided in Microsoft
Excel.xlsx format, are mapped to the setting items of the safety I/O list. You can save and
reuse the mapping information.
3. Define I/O module assignments.
By using the grid rule function, you can perform a bulk edit and detailed check of the I/O
module assignment information.
For use in the grid rule function, setting items that users can freely define as reference
information are provided. These setting items are called User Define.
4. Compare the I/O information lists before and after the import and reflect the differences to
the existing data.
TIP You can export the safety I/O list file. The exported file is in the Microsoft Excel.xlsx format.

5. Check the I/O module assignment results.

The following information appears:
• IOM configuration
• Details of safety I/O connection for each IOM
6. Save and check in the safety I/O list.
7. When engineering by using iDefine, export the safety I/O list and IOM definition data for
iDefine.
SEE
ALSO For more information about the procedures to export files for iDefine from AD Organizer, refer to:
D5.1, “Exporting the ProSafe-RS I/O file from AD Organizer” on page D5-2

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.2 Creating a new safety I/O list> D1-3

D1.2 Creating a new safety I/O list

Follow these steps to create a new safety I/O list:
1. Select the I/O-List folder of the System Structure Navigator.
2. From the context menu, select [New Safety I/O List].
The newly created safety I/O list is displayed in the System Structure Navigator in edit
mode.
3. Enter unique safety I/O list name.
The safety I/O list name that is entered is referred to as the P&ID group.
A new safety I/O list is created. Once it is newly created, it is automatically checked in to
the server.

n Folder location of the safety I/O list definition

When RS project, SCS project, node, slot, and terminal numbers have not yet been defined,
safety I/O lists are defined as the files under the I/O-List folder. Once these are defined, the
safety I/O lists are copied to the I/O_definition folder under the N-IO folder or FIO folder of
each SCS.
After the definition of the safety I/O list has been copied, you can select the safety I/O list from
under the FIO or N-IO folder of SCS and start Safety I/O Editor from the context menu. Only
the contents that are defined in the corresponding file are shown in each editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.3 Operating a safety I/O list> D1-4

D1.3 Operating a safety I/O list

This section describes how to rename and delete a safety I/O list.

n Changing the name of the safety I/O list

Follow these steps to change the name of the safety I/O list:
1. Right-click on the safety I/O list in the System Structure Navigator and select [Rename].
The P&ID group of the safety I/O list name appears in the edit status.
2. Enter a new P&ID group.
The name of the safety I/O list changes.

n Deleting the safety I/O list

You need to delete the safety I/O list after deleting all I/O information that is assigned to the
I/O module. Follow these steps to delete the safety I/O list:
• Select the safety I/O list to delete using System Structure Navigator and click [Delete] on
the tool bar of AD Organizer.
TIP • When the Safety I/O Editor is started, the safety I/O list cannot be deleted.
• You can delete only one safety I/O list at a time.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-5

D1.4 Defining I/O information by using Safety

I/O Editor
This section describes how to use Safety I/O Editor to edit a safety I/O list.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-6

D1.4.1 Starting the Safety I/O Editor

You can start the Safety I/O Editor from the System Structure Navigator in AD Organizer. The
modes of the Safety I/O Editor are edit mode, revision history mode and read-only mode.
You can open two windows simultaneously with the following combination:
• Edit mode and read-only mode
• Revision history mode and read-only mode
You cannot open two windows with the combination of edit mode and revision history mode.

n Starting the Safety I/O Editor for editing

Depending on the operation purpose, the startup method of the Safety I/O Editor varies.

IMPORTANT
To edit I/O information for each SCS, you can start the Safety I/O Editor after setting the sta-
tion configuration and defining the I/O module assignment information in the safety I/O list.

• Perform one of the following operations using the System Structure Navigator to start the
Safety I/O Editor:
• When editing I/O information for each P&ID group
Select and double-click the safety I/O list in the [I/O-List] folder.
• When editing I/O information for each applicable RS project
Right-click the RS project and select [Open] > [Safety I/O Editor].
• When editing I/O information for each applicable SCS
Right-click the target SCS and select [Safety I/O Editor].
• When editing I/O information for each applicable module
Double click the [I/O definition] under the applicable module folder.
The Safety I/O Editor appears in the document window area.

Safety I/O Editor starts with

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-10
Table D1.4.1-1 List of setting items of the Safety I/O Editor (Table continued)
Category No. Column name Description Manda- SCS Manager item
tory set- where the setting
ting or is reflected
not (*1) through RS Gener-
ation
I/O description 23 Signal Conversion Signal Conversion Type 3 Relevant setting
(IOM Builder de- items of I/O Param-
scription) eter Builder
24 Signal LO Low limit of the field I/O signal 1 Relevant setting
items of I/O Param-
eter Builder
25 Signal HI High limit of the field I/O signal 1 Relevant setting
items of I/O Param-
eter Builder
26 Signal Unit Engineering unit of the field 1 Relevant setting
I/O signal items of I/O Param-
eter Builder
27 Wire type Wire type 3 Relevant setting
items of I/O Param-
eter Builder
28 Device OFF-ON Device OFF-ON Variable 3 Relevant setting
Variable Name Name items of I/O Param-
Variable names for instructing eter Builder
a reset of fire and gas equip-
ment
29 Reset Group ID Reset Group ID 3 Relevant setting
Collection of fire and gas items of I/O Param-
equipment subject to being re- eter Builder
set simultaneously with a sin-
gle reset operation
30 Input Processing at Specify input value at fault 3 Relevant setting
Fault items of I/O Param-
eter Builder
31 Input Value at Fault Input value at fault 3 Relevant setting
% items of I/O Param-
eter Builder
32 Input Processing at Specify input at transmitter 3 Relevant setting
Transmitter Fault fault items of I/O Param-
eter Builder
33 Detect IOP (High) Detect IOP (High) 3 Relevant setting
items of I/O Param-
eter Builder
34 Detect IOP (Low) Detect IOP (Low) 3 Relevant setting
items of I/O Param-
eter Builder
35 IOP High Limit Threshold of IOP (High) % 3 Relevant setting
items of I/O Param-
eter Builder
36 IOP Low Limit Threshold of IOP (Low) % 3 Relevant setting
items of I/O Param-
eter Builder
37 Detect Transmitter Detect Transmitter Fault 3 Relevant setting
Fault (High) (High) items of I/O Param-
eter Builder
38 Detect Transmitter Detect Transmitter Fault (Low) 3 Relevant setting
Fault (Low) items of I/O Param-
eter Builder
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-11
Table D1.4.1-1 List of setting items of the Safety I/O Editor (Table continued)
Category No. Column name Description Manda- SCS Manager item
tory set- where the setting
ting or is reflected
not (*1) through RS Gener-
ation
I/O Description 39 Threshold of Trans- Threshold of Transmitter Fault 3 Relevant setting
(IOM Builder de- mitter Fault (High) (High) % items of I/O Param-
scription) % eter Builder
40 Threshold of Trans- Threshold of Transmitter Fault 3 Relevant setting
mitter Fault (Low) (Low) % items of I/O Param-
% eter Builder
41 Field Power Diag- Field Power Diagnosis 3 Relevant setting
nosis items of I/O Param-
eter Builder
42 Reference junction Reference junction compen- 3 Relevant setting
compensation sation items of I/O Param-
eter Builder
43 Burnout Specify burnout 3 Relevant setting
items of I/O Param-
eter Builder
44 Time to Chattering Time to Chattering Recovery 3 Relevant setting
Recovery Notice Notice items of I/O Param-
(s) Monitoring time from when eter Builder
chattering ends to normal re-
covery
45 I/O Shutoff Switch Shutoff Switch for AI/AO/ 3 Relevant setting
DI(NIO) items of I/O Param-
eter Builder
46 Output Shutoff Specify output shutoff switch 3 Relevant setting
Switch of FIO items of I/O Param-
Specify DO shutoff switch of eter Builder
N-IO
47 Output Processing Specify Output Processing at 3 Relevant setting
at Fault Fault items of I/O Param-
eter Builder
48 Output Value at Output Value at Fault 3 Relevant setting
Fault % items of I/O Param-
eter Builder
49 Tight-shut/Full- Specify Tight-shut/Full-open 3 Relevant setting
open items of I/O Param-
eter Builder
50 Tight-shut Value % Tight-shut Value 3 Relevant setting
items of I/O Param-
eter Builder
51 Full-open Value % Full-open Value 3 Relevant setting
items of I/O Param-
eter Builder
52 Detect Short Circuit Detect Short Circuit 3 Relevant setting
items of I/O Param-
eter Builder
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-12
Table D1.4.1-1 List of setting items of the Safety I/O Editor (Table continued)
Category No. Column name Description Manda- SCS Manager item
tory set- where the setting
ting or is reflected
not (*1) through RS Gener-
ation
I/O description 53 Detect Disconnec- Detect Disconnection 3 Relevant setting
(IOM Builder de- tion items of I/O Param-
scription) eter Builder
54 Detect LFD Detect LFD 3 Relevant setting
items of I/O Param-
eter Builder
55 Pulse Test Pulse Test 3 Relevant setting
items of I/O Param-
eter Builder
56 Pulse Test (OFF) Pulse Test (OFF) 3 Relevant setting
items of I/O Param-
eter Builder
57 Pulse Test (ON) Pulse Test (ON) 3 Relevant setting
items of I/O Param-
eter Builder
58 Low Voltage Pulse Low Voltage Pulse Test (ON) 3 Relevant setting
Test (ON) items of I/O Param-
eter Builder
59 SOER (Setting for SOER Setting 3 Relevant setting
SOER) items of I/O Param-
eter Builder
60 Trip Signal (Setting Specify Trip Signal 3 Relevant setting
for SOER) items of I/O Param-
eter Builder
61 Command Command Line 3 Relevant setting
items of I/O Param-
eter Builder
Connection De- 62 Device Com Type Device Communication Proto- - -
vice Info col
(Enter HART/Conventional,
etc.)
63 Device Tag Device Tag - -
64 Device Tag Com- Device Tag Comment - -
ment
65 Device ID Device Serial Number - -
66 Device Address Device Address - -
67 Device Manufactur- Device Manufacturer ID - -
er ID
68 Device Type ID Device Type ID - -
69 Device Revision Device Revision Number - -
70 Device Route Info Device Communication Topol- - -
1 ogy Information
71 Device Route Info Device Communication Topol- - -
2 ogy Information (when IOM is
redundant)
72 Device Installed Device Installed Location - -
Location
73 Device Parameter Device Parameter - -
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-13
Table D1.4.1-1 List of setting items of the Safety I/O Editor (Table continued)
Category No. Column name Description Manda- SCS Manager item
tory set- where the setting
ting or is reflected
not (*1) through RS Gener-
ation
For I/O list man- 74 Component ID Component ID - -
agement
75 Intrinsic Safe Intrinsic Safe - -
76 External Power to External Power to transmitter - -
transmitter
77 Instrument Type Instrument Type - -
78 Instrument Type Instrument Type Description - -
Description
79 Loop Name Loop Name - -
80 Panel Name Panel Name - -
81 Junction Box Name Junction Box Name - -
FieldMate Vali- 82 FieldMate Valida- FieldMate Validation Status - -
dator tion Status
83 Validation Status Validation Status Update Time - -
Update Time
84 Left IOM Validation Left IOM Validation Status - -
Status
85 Right IOM Valida- Right IOM Validation Status - -
tion Status
86 Field Device Vali- Field device Validation Status - -
dation Status
87 Channel Configura- Channel Configuration Upda- - -
tion Updated Time ted Time
88 Overwrite Status Update Status by Using Editor - -
I/O Setting Pro- 89 Protect Protection that prevents the - -
tection I/O settings from being
changed
User Define Col- 90 UDC1 to UDC40 User-defined column - -
umn to
129
For I/O list man- 130 P&ID Group P&ID Group Name 1 -
agement Specify a unique range for the
P&ID tag.
The name that is set at the
time of creating the I/O list in
System Structure Navigator is
automatically reflected.
*1: Whether column settings are required or not are indicated in the following categories:
• 1: Always set
• 2: Set after assigning the I/O to SCS and IOM
• 3: Configuration is required after assigning the I/O to SCS and IOM
• -: Setting not required
*2: These columns are not reflected in the SCS project through RS Generation Manager.
*3: For N-IO, 2
For other than N-IO, -

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-14

D1.4.2 Importing the I/O information list

You need to prepare the I/O information in Microsoft Excel xlsx format. Follow these steps to
import the I/O information:
1. Select the Sub menu button from the Safety I/O Editor, and select Import.
The Import wizard appears.

Figure D1.4.2-1 Import wizard

2. In the File box, specify the Microsoft Excel file in xlsx format of the I/O information to be
imported.
Sheet Name shows the sheet name of the I/O information list, Header Row Position
shows the first row number, and Target P&ID Group shows the P&ID group name that is
present in the I/O information list.
3. Select the sheet to be imported in Sheet Name.
4. Enter the row number in which the setting item is entered in Header Row Position.
5. Set the following details in Settings if necessary.
More specific instructions are given later.
• If the setting item of the I/O information list to be imported does not match the setting
item of the safety I/O list, click the [Column Mapping] button to map the setting items.
• If the setting item of the I/O information list to be imported cannot be mapped to the
setting item of the safety I/O list, click the [User Define Column] button, and after add-
ing the new setting item to the safety I/O list, perform the mapping to these new
items.
6. Click [Next].
The screen will switch to the Comparison and Setting screen.
Then, the I/O information list is imported, and the safety I/O list is checked out.

n Mapping the setting items of the I/O information list to the setting
items of the safety I/O list
The operations for mapping are the same with safety communication I/O lists. When mapping
setting items of a safety communication I/O list, replace safety I/O list with safety communica-
tion I/O list.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-15
To import the I/O information list, not all of the setting item names may necessarily match.
Thus, it is necessary to map the setting items of the I/O information list so that they match the
setting items of the safety I/O list. Follow these steps to perform mapping:
1. In the Import wizard, click [Column Mapping].
The Column Mapping dialog box appears. The setting items that do not match the setting
items of the safety I/O list are displayed in [Unmapped], while the setting items that match
are displayed in [Mapped]. [Client] shows the setting items of the I/O information list,
while [AD Suite] shows the setting items of the safety I/O list.

Figure D1.4.2-2 Column Mapping dialog box

2. In [Unmapped], select the setting items of the I/O information list and the setting items of
the safety I/O list that are to be mapped.
3. Click the [Map] button.
The setting items of the I/O information list and the setting items of the safety I/O list are
mapped and displayed in [Mapped].
4. Click the [OK] button.
The mapping information is created.
5. Click the [Next] button in the Import wizard.
The I/O information list is imported based on the mapping information.
TIP You can export the mapping information to a Microsoft Excel xlsx format file. You can also import the exported
file and map the setting items based on this information.

n Exporting mapping information

You can export the mapping information of the I/O information list and the safety I/O list to a
Microsoft Excel xlsx format file in the Column Mapping dialog box. Follow these steps to ex-
port the mapping information:
1. In the Column Mapping dialog box, click [Export].
The Select a location and set a file name dialog box appears.
2. Specify the export location and file name, and click the [OK] button.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-16

n Importing mapping information

You can import the exported mapping information. Follow these steps to import the mapping
information:
1. In the Column Mapping dialog box, click [Import].
The File Selection dialog box appears.
2. Specify the Microsoft Excel xlsx file of the mapping information to be imported, and click
[OK].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-17

D1.4.3 Comparing and reflecting the I/O information before

and after import
Follow these steps to compare the I/O information before and after import and reflect it in the
safety I/O list:
1. Select the [Mode] settings of the Comparison and Settings screen in the Import wizard
from the following options.
• To compare the added, modified, and deleted I/O information, select [All Check (Add/
Update/Delete)].
• To compare the added and modified I/O information, select [Part Check (Add/
Update)].
2. Click [Finish].
The Safety I/O Editor switches to Deviation mode.
The imported I/O information is displayed on the left pane of the Safety I/O Editor, while
the current safety I/O list is displayed on the right pane. In this case, the differences in the
I/O information are displayed in blue color.
Signal filter Column filter

Figure D1.4.3-1 Safety I/O Editor for Deviation mode during import

TIP The comparison of I/O information before and after import is performed by using the P&ID tag as the key. If
there is no relevant P&ID tag for the current safety I/O list, a new row is added to the safety I/O list.

3. You need to select the operation to reflect the imported I/O information list to the safety
I/O list from the following.
• To reflect only the selected I/O information, click the [Reflect Selected Area] button of
the Safety I/O Editor tool bar in Deviation mode. The differences present in the selec-
ted range are reflected in the safety I/O list.
• To reflect the entire I/O information, click the [Reflect All (regardless of selection)] but-
ton of the Safety I/O Editor tool bar in Deviation mode. All differences present are re-
flected in the safety I/O list.
TIP If the safety I/O list is not checked out, it will be checked out.

n Switching the safety I/O list display in Deviation mode

You can switch the Safety I/O Editor display in Deviation mode.
• Displaying for each edited content
The display of the safety I/O list in Deviation mode can be switched for each I/O point.
You need to perform one of the following operations to switch the display.
• Displaying all I/O points
Select [All Signal] in the signal folder of the Safety I/O Editor in Deviation mode.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-18
• Displaying only the edited I/O points
Select [Different Signal Only] in the signal folder of the Safety I/O Editor in Deviation
mode.
• Displaying for each setting item
The safety I/O list display can be switched in Deviation mode for each setting item. You
need to perform one of the following operations to switch the display.
• Displaying all setting items
Select [All Column] in the column folder of the Safety I/O Editor tool bar in Deviation
mode.
• Displaying only the imported setting items
Select [Imported Column Only] in the column folder of the Safety I/O Editor tool bar in
Deviation mode.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-19

D1.4.4 Editing a safety I/O list

You can use the following methods to edit a safety I/O list:
• Edit a new safety I/O list directly without importing an I/O information list
With this method, you add a row of settings for each I/O point one by one.
• Import an I/O information list
With this method, you import an I/O information list file and edit as required.

n Creating a safety I/O list without importing an I/O information list

The user can directly edit the safety I/O list by using the Safety I/O Editor.
1. Open the System Structure Navigator.
2. Create a new safety I/O list.
3. Edit the safety I/O list.
The data can be edited in two ways: you can edit each row manually, or edit the data in
batch by using grid rules.

n Editing a safety I/O list

Follow these steps to edit a safety I/O list:
You can add I/O points to the safety I/O list if you start the Safety I/O Editor for a P&ID group
or a target module.
1. Double-click the cell of the safety I/O list.
A dialog box appears, asking you to confirm the check-out.
2. Click [Yes].
The I/O points are checked out, and check-out icons appear in the safety I/O list.
3. Edit the cells of the safety I/O list.
TIP • When assigning the input points to the I/O module, define RS Project, SCS, Node Type, Node, IOM Cat-
egory, IOM Type, Unit, Slot, Terminal, and Duplex. When these values are defined, the I/O points are
copied to the I/O_definition file under the SCS folder. In this case, if the node, I/O module folder, and I/
O_definition file do not exist, they are created automatically.
• If you set I/O points for which the I/O module assignment information is not defined, all I/O points for
which the P&ID group is the same, and for which the I/O module assignment information is not defined
are checked out. When I/O information is entered in the I/O points for which the I/O module assignment
information is defined, all I/O points which are assigned to the same I/O module are checked out.

l Adding I/O points to the safety I/O list

Follow these steps to add the I/O points to the safety I/O list:
1. Select I/O points from the safety I/O list. You can select I/O points in the following ways:
• Select one or more rows
• Select only one cell
2. Click the [Add Row] button on the tool bar.
When one or more rows have been selected, the selected number of rows are added
above the selected rows.
When only one cell has been selected, one row is added below the last row. The added
I/O points are checked out.
TIP The I/O points can be added to the safety I/O list when the Safety I/O Editor is started up for each P&ID group
or target module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-20

l Deleting I/O points to the safety I/O list

Follow these steps to delete the I/O points to the safety I/O list:
1. Select the I/O points to be deleted in the safety I/O list.
2. Click the [Delete Row] button on the tool bar.
The selected I/O points are deleted.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-21

D1.4.5 Exporting the I/O information in the safety I/O list

The I/O information of the safety I/O list can be exported to a Microsoft Excel xlsx format file.
Follow these steps to export the I/O information in the safety I/O list:
1. Select the [Sub menu] button from the Safety I/O Editor, and select [Export].
The Export dialog box appears.

Figure D1.4.5-1 Export dialog box

2. Click [Export].
The Select a location and set a file name dialog box appears.

Figure D1.4.5-2 Select a location and set a file name dialog box

TIP When the [Change column names to client's definition] check box is selected, and [Export] is clicked, the set-
ting item name of the safety I/O list is changed based on the mapping information that is set while importing
the I/O information list.

3. Specify the export location and file name, and click [OK].

n Export file format

The exported file is created in the following format.
• File format
Microsoft Excel .xlsx file
• Sheet name
It will be the P&ID group name.
• Sheet description
It is created in the following format.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-22
Setting item names in the safety I/O list

A B C D ... CM CN ... DZ EA
1 Area P&ID Sheet P&ID Tag I/O Type ... UDC1 UDC2 ... UDC40 P&ID Group
2 XXX XXX XXX XXX ... XXX XXX ... XXX XXX
3 XXX XXX XXX XXX ... XXX XXX ... XXX XXX
4 XXX XXX XXX XXX ... XXX XXX ... XXX XXX

I/O information of individual I/O points

Figure D1.4.5-3 Sheet description

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.4 Defining I/O information by using Safety I/O Editor> D1-23

D1.4.6 Purpose of user definition and changing user-

defined name
In addition to the default setting items, 40 setting items that users can define freely are provi-
ded in the safety I/O list. The I/O information that is included in the user-defined settings items
is reference information. This I/O information is not reflected to the SCS project. However,
when engineering by using iDefine, the user-defined I/O information is included in the
ProSafe-RS I/O file. As such, it is recommended that you configure the trip threshold value,
Typical, ID, and other information that you want to refer to when creating an application logic
by using iDefine here.
You can use the user-defined setting items as reference information when using the grid
rules.
Any name can be specified for the user-defined setting items. Follow these steps to specify
any name for the user-defined setting items:
1. Select User Define Column Setting from the sub menu of the safety I/O list.
The User Define Column Setting dialog box appears.
The initial value of the setting item name is displayed in User Definition Column.

Figure D1.4.6-1 User Define Column Setting dialog box

2. Enter the name that needs to be changed in [Alias], and click [Save].
The new name is displayed in the user-defined setting item of the safety I/O list.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D1.5 Saving the safety I/O list and performing check-in> D1-24

D1.5 Saving the safety I/O list and performing

check-in
You can save the safety I/O list and perform check-in. By performing this operation, the safety
I/O list is stored in the AD project.

n Saving the safety I/O list

Follow these steps to save the safety I/O list:
1. Select the Safety I/O Editor.
2. On the tool bar of AD Organizer, click the [Save] button.
TIP • When the I/O module assignment information of the safety I/O list is edited, the safety I/O list (I/O_defini-
tion) in the I/O module of the assignment destination is automatically checked out, and the content of the
definition is reflected.
• When the Safety I/O Editor is in Deviation mode, you cannot save the safety I/O list.

n Performing check-in of the safety I/O list

In the Check-in window, check in the defined safety I/O list.
The check-out icon of the safety I/O list disappears.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2. Engineering based on the safety communication I/O list> D2-1

D2. Engineering based on the safety

communication I/O list
The I/O information of the safety communication I/O list can be defined, browsed, or edited by
using Safety Communication I/O Editor. With the safety communication I/O list, you can man-
ually enter I/O information or import and edit an I/O information list obtained from a plant de-
signer. The items subject to definitions of the safety communication I/O list are the following
communication categories and module types amongst the FIO.

Table D2-1 Items subject to definitions of the safety communication I/O list
Communication category Module type
Serial ALR111M, ALR121M (for subsystem communication)
Ethernet ALE111M (for subsystem communication)
PROFINET S2LP131 (for safety subsystem communication)

With the safety communication I/O list, you can configure Ethernet communication I/O, serial
communication I/O, and fire and gas communication I/O for each I/O point.
The following shows the work flow of engineering for the safety communication I/O list.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2. Engineering based on the safety communication I/O list> D2-2

Create a new
safety communication I/O list

The following basic information is necessary:

- P&ID Tag
- I/O Type (AI, AO, DI, DO)
Enter or import - Signal Protocol
the basic information - I/O Tag (Strings that are used as variable names
to the signal definition list In Dictionary View after reflection to SCS project)

Perform for
each P&ID group. You can do the following tasks after setting
the station configuration of the project.
Enter or import I/O module Enter the following I/O module assignment
assignment information information
to the signal definition list - RS Project
- SCS Project
- Node Type
- Node
- IOM Category
- IOM Type
- Slot

Enter data structure information Decide the structure of the communication

in the signal definition list definition data that is acquired from the
subsystem in a single communication
transaction (bit type data, analog type data).
Enter the following structure information:
- Data type
- Program group
- Communication group
The structure of communication definition data
is determined by assigning the same name to
Perform for the program group and communication group.
each P&ID group,
RS project, or SCS. Define or import
program groups Assign an area for storing communication
definition data for each subsystem.

Define or import Assign an area for storing communication

definition data that is acquired from the
communication groups
subsystem in a single communication transaction.

Save
the safety communication I/O list
and check-in it

Calculate the size and offset for program groups

Fix the element names and communication groups and fix the element
of communication I/O names of communication I/O.

Perform for
each SCS.
Save
the safety communication I/O list
and check-in it

Figure D2-1 Work flow of engineering for the safety communication I/O list

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2. Engineering based on the safety communication I/O list> D2-3
SEE
ALSO For more information about operations for every P&ID group and SCS, refer to:
“n Starting the Safety Communication I/O Editor for editing” on page D2-6
For more information about data structures, program groups, and communication groups, refer to:
D2.5.1, “Overview of definitions for communication with subsystems” on page D2-24

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.1 Creating a new safety communication I/O list> D2-4

D2.1 Creating a new safety communication I/O

list
Follow these steps to create a safety communication I/O list:
1. Select the I/O-List folder of System Structure Navigator.
2. From the context menu, select [New Safety Communication I/O].
The newly created safety communication I/O list appears in the edit mode in System
Structure Navigator.
3. Enter a unique safety communication I/O list name.
A new safety communication I/O list is created. Once the list is newly created, it is auto-
matically checked in to the server.
TIP The safety communication I/O list name that is entered is referred to as the P&ID group.

SEE
ALSO For more information about how to change the name of a safety communication I/O list after creating the
safety communication I/O list, refer to:
“n Changing the name of the safety communication I/O list” on page D2-5
For more information about the maximum number of safety communication I/O lists, refer to:
A4., “Application capacity of AD Suite” in Engineer's Reference Manual (IM 32P04B10-01EN)

n Folder location of the safety communication I/O list definition

After RS Project and SCS Project are set in the safety communication I/O list, a file containing
the I/O information for an individual SCS is copied to the Comm_I/O folder under the corre-
sponding SCS folder.
Thereafter, you can select the Comm_I/O folder to start Safety Communication I/O Editor from
the context menu. Only the contents that are defined in the corresponding file are shown in
the editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.2 Operating a safety communication I/O list > D2-5

D2.2 Operating a safety communication I/O list

This section describes how to rename and delete a safety communication I/O list.

n Changing the name of the safety communication I/O list

Follow these steps to change the name of the safety communication I/O list:
1. Right-click on the safety communication I/O list in System Structure Navigator and select
[Rename].
The P&ID group of the safety communication I/O list name appears in the edit status.
2. Enter a new P&ID group.
The name of the safety communication I/O list changes.

n Deleting the safety communication I/O list

You need to delete the safety communication I/O list after deleting all I/O information that is
assigned to the I/O module. Follow these steps to delete the safety communication I/O list:
• Select the safety communication I/O list in System Structure Navigator and click [Delete]
on the tool bar of AD Organizer.
TIP • When the Safety Communication I/O Editor is running, the safety communication I/O list cannot be de-
leted.
• You can delete only one safety communication I/O list at a time.

TIP • In the safety communication I/O list, Ethernet communication I/O and serial communication I/O for sub-
system communication and fire and gas communication I/O for safety subsystem communication are
each shown with a line for every I/O point.
• The program group definition list and communication group definition list are defined for each SCS re-
gardless of how Safety Communication I/O Editor is started.
• When Safety Communication I/O Editor is started, information of the source from which you started the
editor is shown in the window title.

The functions that you can use will vary depending on the project and definition items that
were selected prior to starting Safety Communication I/O Editor. The following table shows
the differences.

Table D2.3-1 Differences of functions depending on how the editor is started

Definition item or Export function (*1) Import function (*1) Size/Element auto- Editing of the Wir-
project selected matic calculation ing column
upon startup
P&ID group (I/O-list) Yes Yes No Read-only
RS project Yes No No Read-only
SCS project Yes No Yes Write-only
*1: Indicates whether or not the function will operate.
Yes: The function can be operated
No: The function cannot be operated

n Starting the Safety Communication I/O Editor for read-only

Depending on the operation purpose, method for starting Safety Communication I/O Editor
varies.
• Perform one of the following operations using the System Structure Navigator to start the
Safety Communication I/O Editor in read-only mode:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-8
• When reading definitions for each P&ID group
Right-click the safety communication I/O list in the [I/O-List] folder and select [Open
(Read-Only)].
• When reading definitions for each applicable RS project
Right-click the RS project and select [Open (Read-Only)] > [Safety Communication
I/O Editor].
• When reading definitions for each applicable SCS
Right-click the [Comm I/O] under the applicable SCS and select [Open (Read-Only)].
The Safety Communication I/O Editor appears in the document window area in read-only
mode.
TIP If content is being edited in the edit mode editor, the contents being edited are also reflected in the read-only
mode editor. However, the update is manual.

n Switching the display of the safety communication I/O list

You can switch the display of the safety communication I/O list for each I/O type. Perform the
following operation to switch the display:
• From the drop-down list on the upper-left pane of the safety communication I/O list, select
the items you wish to display.

Figure D2.3-2 Drop-down list for switching the display

Only the selected items are shown.

n Setting items of Safety Communication I/O Editor

The following lists are defined with Safety Communication I/O Editor:
• Signal definition list
• Program group definition list
• Communication group definition list
The following figure shows where the lists are defined.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-9
I/O information about each I/O
Safety Communication I/O list point is displayed in a row.

Signal
Definition
list

Program
Group
Definition list

Communica-
tion Group
Definition list

Figure D2.3-3 Window configuration of Safety Communication I/O Editor

The following table shows each of the setting items.

Table D2.3-2 List of setting items of the "signal definition list"

Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Editing status - Checked-out Denotes the check-out - -
Status status of the relevant
signal definition.
- Modification Denotes the change - -
Status status (with unsaved
changes/with warning/
with error) of the rele-
vant signal definition
For I/O list man- 1 Area Area name - -
agement
2 P&ID Sheet P&ID sheet name - -
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-10
Table D2.3-2 List of setting items of the "signal definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
I/O list common 3 P&ID Tag P&ID tag name 1 -
Key information re-
quired to identify each
I/O.
The P&ID tag must be
unique within the
P&ID group.
4 I/O Type The I/O type. Select 1 -
from the following:
AI, AO, DI, DO
5 Signal Protocol The signal type. Se- 1 -
lect from the following:
MODBUS
MODBUS (SLS)
PROFINET
PROFIsafe
6 Comment The variable comment - Dictionary View: Com-
of the IO variable that ment
is defined in Dictionary Communication I/O Build-
View. er (Comm. I/O Wiring,
With I/O list engineer- PROFINET Comm. I/O
ing, you can also use Wiring)
iDefine to create appli-
cation logics.
Create an application
logic by using iDefine
based on the IOM in-
formation that was de-
fined in AD Organizer
and reflect the appli-
cation logic onto the
SCS by using AD Or-
ganizer.
7 Range LO Low limit - -
8 Range HI High limit - -
9 Eng unit Engineering unit - -
10 I/O Tag I/O tag name 1 Dictionary View: Name
Normally, set the Communication I/O Build-
same name as the er (Comm. I/O Wiring,
P&ID tag, or an abbre- PROFINET Comm. I/O
viated form thereof. Wiring)
The I/O tag must be
unique within the
SCS.
A character string that
will become the varia-
ble name in Dictionary
View after reflection
onto the SCS project.
Otherwise, a variable
name that will be
wired with Communi-
cation I/O Builder.
11 Variable Group Variable Group - Dictionary View
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-11
Table D2.3-2 List of setting items of the "signal definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Communication 12 Program Group The program group to 2 -
I/O definitions which this signal be-
longs
13 Communication The communication Communication I/O Build-
Group definition group to er (PROFINET Comm.
which this signal be- I/O Definition)
longs
14 PN-Data Valid only when using Communication I/O Build-
PROFINET. er (PROFINET Comm.
Data name prescribed I/O Definition)
with the PROFIBUS
GSD file.
15 Wiring Specifies whether to Communication I/O Build-
newly register this var- er (Comm. I/O Definition,
iable to Dictionary Comm. I/O Wiring, PRO-
View or to assign it to FINET Comm. I/O Defini-
a variable that has al- tion, PROFINET Comm.
ready been registered. I/O
Select from the follow-
ing:
(Global)/List of FB in-
stances of local varia-
bles and FB instances
of user-defined FB pa-
rameters
16 Position The order of %WW or -
%WB within a single
communication group
17 Bit Position Defines the Bit posi- -
tion when using %WB
18 Comm Device & Addresses of other Communication I/O Build-
Address devices er (Comm. I/O Definition)
19 Data Type Data Type Communication I/O Build-
Select from the follow- er (Comm. I/O Definition,
ing: Comm. I/O Wiring, PRO-
U8/I8/U16/I16/U32/I32 FINET Comm. I/O Defini-
/F32/Bit tion, PROFINET Comm.
I/O Wiring)
20 Element Element number 3 Communication I/O Build-
This can normally be er (Comm. I/O Definition,
calculated automati- PROFINET Comm. I/O
cally. Definition)
21 Fix Element A setting for fixing the 3 -
element number.
Select either Yes/No.
When Yes is selected,
the element number
does not change even
when Update Element
is pressed.
22 Reverse Reverse data 2 Communication I/O Build-
er (Comm. I/O Definition)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-12
Table D2.3-2 List of setting items of the "signal definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
IOM assignment 23 RS Project The SCS and IOM as- - The content defined here
information signment information is taken into IOM Defini-
24 SCS to which this signal is tion Editor and then re-
25 Node Type being assigned. flected onto I/O Wiring
By defining the Pro- View when implementing
26 Node gram Group column, RS Generation.
the corresponding pro-
27 IOM Category
gram group definitions
28 IOM Type are reflected and then
later become read-on-
29 Slot ly.
I/O description 30 Input Process- Input Processing at - Communication I/O Build-
ing at Fault Fault er: Input Processing at
Fault
31 Input Value at Input value at fault Communication I/O Build-
Fault er: Input Value at Fault
Connection De- 32 Device Com Device Communica- - -
vice Info Type tion Protocol
33 Device Tag Device Tag
34 Device Tag Device Tag Comment
Comment
35 Device ID Device Serial Number
36 Device Address Device Address
37 Device Manu- Device Manufacturer
facturer ID ID
38 Device Type ID Device Type ID
39 Device Revision Device Revision Num-
ber
40 Device Route Device Communica-
Info 1 tion Topology Informa-
tion
41 Device Route Device Communica-
Info 2 tion Topology Informa-
tion (when IOM is re-
dundant)
42 Device Installed Device Installed Loca-
Location tion
43 Device Parame- Device Parameter
ter
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-13
Table D2.3-2 List of setting items of the "signal definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
For I/O list man- 44 Component ID Component ID - -
agement
45 IS Intrinsic Safe
46 Ext Power External Power to
transmitter
47 Instrument Type Instrument Type
48 Instrument De- Instrument Type De-
scription scription
49 Loop Name Loop Name
50 Panel Name Panel Name
51 Junction Box Junction Box Name
Name
User-defined 52 UDC1 User Define Column - -
columns
... ...
91 UDC40
For I/O list man- 92 P&ID Group P&ID Group Name 1 -
agement Specify a unique
range for the P&ID
tag.
The name that is set
upon creation of the
I/O list in System
Structure Navigator is
automatically reflec-
ted.
*1: Whether column settings are required or not are indicated in the following categories: Meaning of the Mandatory setting or not
column
• 1: Configuration is always required
• 2: Configuration is required after assigning the I/O to SCS and IOM
• 3: Configuration is preferred after assigning the I/O to SCS and IOM
• -: Configuration is not required

Table D2.3-3 List of setting items of the "program group definition list"
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Editing status - Checked-out Denotes the check-out - -
Status status of the relevant
program definition
- Modification Denotes the change - -
Status status (with unsaved
changes/with warning/
with error) of the rele-
vant program defini-
tion
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-14
Table D2.3-3 List of setting items of the "program group definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Program defini- 1 Program Group Defines the program 3 -
tion group name
2 Program Proto- This is read-only. The -
col value is selected from
the following:
• Serial (RS-232C)
• Serial (RS-422)
• Serial (RS-485)
• Serial (RS-422/
RS-485)
• Ethernet
• PROFINET
3 Size The size of this pro- Communication I/O Build-
gram definition er: Buffer size (program)
This becomes the
area of %XW.
4 Offset Specifies the begin- Communication I/O Build-
ning position of this er: Buffer
program definition as
the offset from the be-
ginning of the SCS
communication I/O
area.
This becomes the first
number of %XW.
5 RS Project The name of the RS -
project to which this
program definition will
be assigned
6 SCS The SCS number to -
which this program
definition will be as-
signed
7 Node Type The node type to -
which this program
definition will be as-
signed (only "ESB
Bus/Optical ESB Bus"
can be selected).
8 Node The node number to I/O Wiring View, I/O Pa-
which this program rameter Builder
definition will be as-
signed
9 IOM Category The IOM category to -
which this program
definition will be as-
signed.
PROFINET for fire
and gas devices
10 IOM Type The IOM type to which I/O Wiring View, I/O Pa-
this program definition rameter Builder
will be assigned
11 Slot The slot number to I/O Wiring View, I/O Pa-
which this program rameter Builder
definition will be as-
signed
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-15
Table D2.3-3 List of setting items of the "program group definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Program defini- 12 Duplex The specification for 3 I/O Parameter Builder:
tion redundancy of the Module
IOM to which this pro-
gram definition will be
assigned
Program defini- 13 IOM Host Name This is read-only. The - I/O Parameter Builder:
tion (*2) device tag name of Module
S2LP131 (reflected
from the definition by
PROFINET Configura-
tor).
14 IOM Address This is read-only. I/O Parameter Builder:
The IP address of Module
S2LP131 (reflected
from the definition by
PROFINET Configura-
tor).
15 IOM Subnet This is read-only. The I/O Parameter Builder:
Mask subnet mask of Module
S2LP131 (reflected
from the definition by
PROFINET Configura-
tor).
16 IOM Default This is read-only. I/O Parameter Builder:
Gateway The default gateway Module
of S2LP131 (reflected
from the definition by
PROFINET Configura-
tor).
17 Connection De- Select from the follow- I/O Parameter Builder:
vice Type ing: Module
• Modbus
• ProSafe-SLS
• PROFINET
Safety commu- 18 P&ID Group This is read-only. The - -
nication I/O list value for the same
management column name of the
program group defini-
tion.
*1: Whether column settings are required or not are indicated in the following categories: Meaning of the Mandatory setting or not
column
• 1: Configuration is always required
• 2: Configuration is required after assigning the I/O to SCS and IOM
• 3: Configuration is preferred after assigning the I/O to SCS and IOM
• -: Configuration is not required
*2: PROFINET Configurator can be started from Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-16
Table D2.3-4 List of setting items of the "communication group definition list"
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Editing status - Checked-out Denotes the check-out - -
Status status of the relevant
program definition
- Modification Denotes the change - -
Status status (with unsaved
changes/with warning/
with error) of the rele-
vant program defini-
tion
Communication 1 Program Group The program group to 3 -
definition which this communi-
cation definition be-
longs
2 Communication Defines the communi- 3 Communication I/O Build-
Group cation group name er (PROFINET Comm.
I/O Definition)
3 Size The size of this com- 3 Communication I/O Build-
munication definition er (Comm. I/O Definition,
PROFINET Comm. I/O
Definition)
4 Offset Specifies the begin- 3 -
ning position of this
communication defini-
tion as the offset from
the beginning of the
program definition.
5 RS Project This is read-only. The - -
value indicates the
6 SCS IOM to which this -
7 Node communication defini- I/O Wiring View
tion will be assigned.
8 Slot By defining the Pro- I/O Wiring View
gram Group column,
the corresponding pro-
gram group definitions
are reflected.
9 IP Address The IP address 3 Communication I/O Build-
er (PROFINET Comm
Definition
2 nd IP Address The IP address for du- 3 Communication I/O Build-
plex subsystems er: 2nd IP Address
10 Connection De- The name of the de- - Communication I/O Build-
vice Tag vice having the IP ad- er (PROFINET Comm
dress Definition)
11 Connection De- The comment for the - -
vice Tag Com- previous device
ment
12 Port The port number 3 Communication I/O Build-
er: Port
13 Station The station number 3 Communication I/O Build-
er (Comm. I/O Definition)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-17
Table D2.3-4 List of setting items of the "communication group definition list" (Table continued)
Category No Column name Description Mandatory SCS Manager item
setting or where the setting is re-
not (*1) flected through RS Gen-
eration
Communication 14 SLSEVENT SLSEVENT (*2) 3 Communication I/O Build-
definition The default value is er (Comm. I/O Definition)
No. When changing
this to Yes, the size
will be fixed at 24.
15 PN-Device Slot This is read-only. The 3 Communication I/O Build-
Tag definition of PROFI- er (PROFINET Comm
NET Configurator. Definition)
16 Subnet Mask (Reflected from the
17 Default Gateway definition by PROFI-
NET Configurator.)
18 PN-Updating
Time
Communication 19 PN-Watchdog This is read-only. The 3 Communication I/O Build-
definition (*3) Time definition of PROFI- er (PROFINET Comm.
NET Configurator. I/O Definition)
20 PN-Slot (Reflected from the
21 PN-Module definition by PROFI-
NET Configurator.)
22 PN-Sub Slot
Communication 23 PN-Submodule This is read-only. The 3 Communication I/O Build-
definition (*3) definition of PROFI- er (PROFINET Comm.
24 PN-Signal Infor- NET Configurator. I/O Definition)
mation (Reflected from the
definition by PROFI-
NET Configurator.)
25 F_Check_iPar This is read-only. 3 Communication I/O Build-
PROFIsafe related er (PROFINET Comm.
26 F_SIL definition (Reflected I/O Definition)
27 F_CRC_ Length from the definition by
PROFINET Configura-
28 F_CRC_ Seed tor).
29 F_Passivation
30 F_Block_ID
31 F_Par_Version
32 F_Source_Add
33 F_Dest_Add
34 F_WD_Time
35 F_WD_Time_2
36 F_iPar_CRC
37 F_Par_CRC
Safety commu- 38 P&ID Group This is read-only. The - -
nication I/O list value for the same
management column name of the
program group defini-
tion.
*1: Whether column settings are required or not are indicated in the following categories: Meaning of the Mandatory setting or not
column
• 1: Configuration is always required
• 2: Configuration is required after assigning the I/O to SCS and IOM
• 3: Configuration is preferred after assigning the I/O to SCS and IOM
• -: Configuration is not required
*2: When defining SLSEVENT, set only the program definition and communication definition without setting the signal definition.
A signal cannot be associated with a communication group for the SLSEVENT definition. An error will occur when trying to
save if a signal is defined.
*3: PROFINET Configurator can be started from Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.3 Starting Safety Communication I/O Editor > D2-18
SEE
ALSO For more information about PROFINET Configurator, refer to:
E1.5.2, “Applying settings by using PROFINET Configurator” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.4 Entering I/O information in the signal definition list> D2-19

D2.4 Entering I/O information in the signal

definition list
Define I/O information in the signal definition list. When the SCS and communication modules
to be assigned to the I/O points are decided, define this information as well.

n Editing the signal definition list

Follow these steps to edit the I/O information of the signal definition list:
1. Select the safety communication I/O list in System Structure Navigator and click [Check-
out] on the tool bar of AD Organizer.
The safety communication I/O list is checked out.
2. Select the signal definition list of Safety Communication I/O Editor and click [Add Row] on
the tool bar.
An I/O point is added to the signal definition list.
3. Enter I/O information into the cells in the signal definition list.
SEE
ALSO For more information about setting items of the signal definition list, refer to:
“n Setting items of Safety Communication I/O Editor” on page D2-8

l Editing the I/O information of the signal definition list

Follow these steps to edit the I/O information of the signal definition list:
1. Select a cell in the signal definition list.
A dialog box appears, asking you to confirm the check-out.
2. Click [Yes].
The I/O point is checked out and the icon for the item of [Checked-out Status] in the sig-
nal definition list changes.
3. Enter I/O information into the cells in the signal definition list.
TIP I/O points can be added to the signal definition list when Safety Communication I/O Editor is started for each
P&ID group or target SCS.

SEE
ALSO For more information about setting items of the signal definition list, refer to:
“n Setting items of Safety Communication I/O Editor” on page D2-8

l Adding an I/O point to the signal definition list

Follow these steps to add I/O points to the signal definition list when the safety communica-
tion I/O list is not checked out:
1. Select an I/O point from the signal definition list.
2. Click [Add Row] on the tool bar.
An I/O point is added above the selected I/O point and this added I/O point is checked
out.
TIP I/O points can be added to the signal definition list when Safety Communication I/O Editor is started for each
P&ID group or target SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.4 Entering I/O information in the signal definition list> D2-20

l Initializing the I/O information of an edited signal definition list

Follow these steps to return the I/O information of an edited signal definition list to its initial
values:
1. Select one or more cells of the signal definition list.
2. Right-click on the selected cell and select [Reset to Default].

l Deleting an I/O point from the signal definition list

Follow these steps to delete an I/O point from the signal definition list:
1. Select the I/O point to delete from the signal definition list.
2. Click [Delete Row(s)] on the tool bar.
The selected I/O points are deleted.

n Entering basic information of I/O points

Enter the following items as basic information of the signal definition list:
• P&ID Tag
• I/O Type
• Signal Protocol
• I/O Tag
• Data type
Refer to the following table for settings of the Signal Protocol, I/O Type, and Data type.

Table D2.4-1 Relationship between the Signal Protocol and the Data type
Signal Protocol I/O Type Data type
MODBUS AI U16
AO I16
I32
F32
DI Bit
DO
MODBUS (SLS) AI U16
AO
DI Bit
DO
PROFINET AI U8
I8
U16
I16
U32
I32
F32
PROFIsafe AI U8
I8
U16
I16
U32
I32
F32

As needed, define the following items for defining the data structure to obtain from the sub-
system being connected to:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.4 Entering I/O information in the signal definition list> D2-21
Program Group : The program group to which the I/O point belongs.
Communication Group : The communication definition group to which the I/O point
belongs.
Position / Bit Position : The order of %WW and %XW in the communication defini-
tion group. Bit Position defines the bit position of %WW.
Comm Device & Address : The addresses of other devices.
Position denotes the order of %WW and %XW within a single communication group. Bit Posi-
tion is the bit position when the Data type of DI or DO is Bit. These items are used when de-
ciding the numbers for %WW and %XW.
TIP %WW is an area assigned to communication modules for subsystem communication while %XW is an area
assigned to communication modules for safety subsystem communication.

IMPORTANT
Do not define SLSEVENT, a data type used with ProSafe-SLS communication, in the signal
area and configure only the program group definition and communication definition group. A
signal cannot be associated with a communication group for the SLSEVENT definition. An er-
ror will occur when trying to save.

n Entering I/O module assignment information of the signal definition

The following are precautions when assigning an I/O points of the signal definition to an I/O
module.
• When assigning I/O points to an I/O module, define RS Project, SCS, Node Type, Node,
IOM Category, IOM Type, and Slot. When these values are defined, the I/O points are
copied to the Comm_I/O file under the SCS folder.
• When I/O information is entered to I/O points for which the I/O module assignment infor-
mation is not defined, all I/O points for which I/O module assignment information is not
defined are checked out. When I/O information is entered to I/O points for which the I/O
module assignment information is defined, all I/O points which are assigned to the same
SCS are checked out.

n Purpose of user definition and changing user-defined name

In addition to the default setting items, 40 setting items that users can define freely are provi-
ded in the safety communication I/O list. The I/O information that is included in the user-de-
fined settings items is reference information. This I/O information is not reflected to the SCS
project. However, when engineering by using iDefine, the user-defined I/O information is in-
cluded in the ProSafe-RS I/O file. As such, it is recommended that you configure the trip
threshold value, Typical, ID, and other information that you want to refer to when creating an
application logic by using iDefine here.
You can use the user-defined setting items as reference information when using the grid
rules.
Any name can be specified for the user-defined setting items. Follow these steps to specify
any name for the user-defined setting items:
1. From the sub menu of the safety communication I/O list, select [User Define Column Set-
ting].
The User Define Column Setting dialog box appears.
The initial values of the setting item names are displayed in User Definition Column.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.4 Entering I/O information in the signal definition list> D2-22

Figure D2.4-1 User Define Column Setting dialog box

2. Enter the name that needs to be changed in [Alias], and click [Save].
The new name is displayed in the user-defined setting item of the safety communication
I/O list.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-23

D2.5 Converting I/O information into a data

structure that can be communicated with
subsystems
This section describes how to convert I/O information into a data structure that can be com-
municated with subsystems being connected by using Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-24

D2.5.1 Overview of definitions for communication with

subsystems
In order to communicate with subsystems, after assigning a communication I/O data area for
each subsystem being connected, you must set what kind of data to obtain from the connec-
ted subsystems and in which part of the connected subsystems the data will be written. With
this setting, each assigned area is split into units of data which can be obtained or set with a
single round of communication with the connected subsystem and then defined for how each
of these will communicate by using Safety Communication I/O Editor. The following figure
shows an overview of communication definitions for subsystems.

Only contact I/O data

Communication
I/O data area
%WW0001
Program group %WW0002 Communication
group
:
Acquired through a single Communication
communication definition data 1
Bit type
data Communication I/O
: data area assigned
to connection
Analog subsystem
type data
Communication
definition data 3

Connected subsystem
Only analog
I/O data Specified by
Communication is the relative
executed in position
accordance with the within the
defined contents and region
data is acquired.

Figure D2.5.1-1 Overview of communication definitions

n Element numbers in the communication I/O data area

The following figure shows an example of the assignment of element numbers in the commu-
nication I/O data area.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-25

Communication I/O C The first element number of

data area communication group 2
= 1+ A + B
%WW0001
A %WW0002
: The element number of
The offset of program group 1 :
: communication group 2
(Example: 1000) :
= C + The total size for up to
the previous I/O point
Start position

%WW1001
B The offset of The size of
communication
group 2 %WW1002 communication group 1
(Example: 2) (*2) (Example: 2)

%WW1003
%WW1004 The size of
The size of program group 1 communication group 2
%WW1005 (*2) (Example: 4)
(*1) (Example: 14) %WW1006

%WW1007
%WW1008
%WW1009
The size of
%WW1010 communication group 3
%WW1011 (*2) (Example: 8)
%WW1012
%WW1013
%WW1014

*1: The total size for the communication groups assigned to program group 1
*2: The total size for the I/O points assigned to each communication group

Figure D2.5.1-2 Example of assignment of element numbers in the communication module I/O data
area

n Flow of definitions for communication with subsystems

Follow these steps when converting I/O information into a data structure that can be commu-
nicated with subsystems:
1. Decide the data structure.
2. Assign a communication I/O data area for each subsystem being connected.
• Define program groups.
• Define communication groups.
3. Establish the element number of the communication I/O.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-26

D2.5.2 Deciding the data structure

The data structures obtained from connected subsystems consist of bit-type data and analog-
type data. This section describes the definitions of each type of data structure.

n Defining the bit-type data structure

Bit-type data is configured of only the I/O points of bit data. Follow these steps to define the
structure of this bit-type data:
1. In the signal definition list, enter the same program group name to the Program Group of
the I/O points to include in a single set of the bit-type data.
2. In the signal definition list, enter the same communication group name to the Communi-
cation Group of the I/O points to include in a single set of the bit-type data.

Figure D2.5.2-1 Bit-type data structure definition

n Defining the analog-type data structure

Analog-type data is configured of only the I/O points of the same data type amongst analog
I/O data. Follow these steps to define the structure of this analog-type data:
1. In the signal definition list, enter the same program group name to the Program Group of
the I/O points to include in a single set of the analog-type data.
2. In the signal definition list, enter the same communication group name to the Communi-
cation Group of the I/O points to include in a single set of the analog-type data.

Figure D2.5.2-2 Analog-type data structure definition

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-27

D2.5.3 Defining program groups

By defining program groups, you can configure I/O information for each connected subsys-
tem. A maximum of 12 program groups can be defined. The breakdown is as follows:
• Up to 4 subsystem communication I/O (Models: ALR111M/121M/ALE111M) groups
• Up to 8 safety subsystem communication (Model name: S2LP131) groups
Follow these steps to define the program groups:
1. Click [Program] on the tool bar of Safety Communication I/O Editor.
The program group set with Program Group of the signal definition list is added to the
program group definition list, and the I/O information is configured for each connected
subsystem. At this time, the default value for Size is 2 while the default value for Offset is
blank.

Figure D2.5.3-1 Program group definition

2. On the tool bar of AD Organizer, click [Save].

SEE
ALSO For more information about setting items of the program group definition list, refer to:
“n Setting items of Safety Communication I/O Editor” on page D2-8

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-28

D2.5.4 Defining communication group

By defining communication groups, you can configure I/O information for each set of commu-
nication definition data. Follow these steps to define the communication groups:
1. Click [Communication] on the tool bar of Safety Communication I/O Editor.
The communication group set with Communication Group of the signal definition list is
added to the communication group definition list and the I/O information is configured for
each set of communication definition data. At this time, the default value for Size is 1
while the default value for Offset is 0.

Figure D2.5.4-1 Communication group definition

TIP The maximum number of communication groups that can be assigned to a single program group is as fol-
lows:
• 128 per program group for program protocols other than PROFINET
• With SCSP3, program groups for the PROFINET protocol can be defined in addition to the above making
the maximum 200 per program group

2. On the tool bar of AD Organizer, click [Save].

SEE
ALSO For more information about setting items of the communication group definition list, refer to:
“n Setting items of Safety Communication I/O Editor” on page D2-8

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-29

D2.5.5 Fixing the element numbers of the communication

I/O
After defining or editing the basic information, I/O module assignment information, and data
structure information with the signal definition list, you must fix the element numbers of the
communication I/O.

IMPORTANT
• After defining RS Project and SCS of the I/O points for which to fix element numbers with
the signal definition list, start Safety Communication I/O Editor by selecting the target
SCS in the System Structure Navigator.
• When Fix Element of the signal definition list is set to [Yes], I/O information cannot be
changed. If you want to change the I/O information, change Fix Element to [No].

Follow these steps to decide the element numbers of communication I/O:

1. Click [Calculate] on the communication group definition list.
The size of the communication group is calculated and appears under Size in the com-
munication group definition list.
2. Check Size in the communication group definition list and enter the size of the communi-
cation group under Offset.
3. Click [Calculate] on the program group definition list.
The size of the program group is calculated and appears under Size in the program group
definition list.
4. Check Size in the program group definition list and enter the size of the program group
under Offset.
5. Click [Update Element] on the tool bar of Safety Communication I/O Editor.
The consistency of the I/O information is checked and element numbers of the communi-
cation I/O are set.
TIP When Fix Element of the signal definition list is set to [Yes], the element numbers of the communication I/O
become fixed.

SEE
ALSO For more information about setting items of the safety communication I/O list, refer to:
“n Setting items of Safety Communication I/O Editor” on page D2-8

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-30

D2.5.6 Procedure for creating and wiring communication

I/O variables
A communication I/O is wired to an instance of a subsystem communication I/O FB or fire and
gas communication FB. The FB instance is defined as a global variable, local variable, or pa-
rameter of a user-defined FB instance.
Global variables are defined by using Safety Communication I/O Editor of AD Organizer and
can be created when the reflection process is run for the target SCS by using Generation
Manager.
I/O Tag in the signal definition of the safety communication I/O list will become the variable
name in Dictionary View after reflection onto the SCS project. In addition, this will be the vari-
able name that is wired in Communication I/O Builder.
The description shown in the following table can be used as a method for describing the vari-
able name to be wired.

Table D2.5.6-1 How to describe a variable name

Variable name Scope Description
VAR1 Global (*1) Global variable
VAR2@PROG1 PROG1 Local variable of a function of
PROG1
FB01.VAR3 Global (*1) Parameter VAR3 of instance FB01
of a user-defined function block
FB01.VAR3@PROG1 PROG1 Parameter VAR3 of user-defined
FB instance FB01 locally defined
to the function of PROG1
FB01.FB2.VAR3 Global (*1) Parameter VAR3 of instance FB2
of a user-defined FB used within
instance FB01 of a user defined
FB (limit for nesting of FB)
*1: In order to handle variables other than global variables with the safety communication I/O list, the information of the variables
and parameters of subsystem communication I/O FB included in the POU created with iDefine or SCS Manager is required.
In order to handle this information with the safety communication I/O list, do not describe global variables in the Wiring col-
umn of signal definitions.

TIP The options for the Wiring column are updated upon obtaining information from the iDefine setting file and
SCS project at the timings shown below when the safety communication I/O list for an SCS is opened in
Safety Communication I/O Editor:
• When the safety communication I/O list is opened
• When Refresh is clicked

When a local variable or user-defined FB instance parameter has been specified in the Wiring
column of the signal definition, Generation Manager does not create a global variable descri-
bed in the I/O Tag column. Local variables or user-defined FB instance parameters created
with iDefine or SCS Manager are used. Variables defined with iDefine cannot be edited with
SCS Manager.
Variables other than global variables are applied to communication definitions using the appli-
cable communication module in Safety Communication I/O Editor. The applicable variables
and parameter types are the FB for the communication of each.
These variables and FB parameters can be wired to communication I/O by defining Wiring of
Signal Definition in the Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.5 Converting I/O information into a data structure that can be communicated with subsystems >
D2-31
This section describes the work flow for creating all FB instances as global variables and wir-
ing them to communication I/Os, then wiring some of the communication I/Os to local varia-
bles or FB parameters.
1. The default value for Wiring of the signal definition is [(Global)]. Select [(Global)] for Wir-
ing of the signal definition, and then run the reflection process with Generation Manager.
Global variables are created in Dictionary View with the variable names specified in I/O
Tag.
If Element is set, the relevant variable is set in Variable Name for the specified data area
on the Comm. I/O Wiring tab of Communication I/O Builder.
TIP The options for Wiring are updated upon obtaining information from the iDefine setting file and SCS project at
the timings shown below when the safety communication I/O list for an SCS is opened in Safety Communica-
tion I/O Editor:
• When the safety communication I/O list is opened
• When [Refresh] is clicked

2. Create local variables and parameters of user-defined FB instances with SCS Manager
or iDefine, and import the iDefine-config file containing the definitions to AD Organizer.
The local variables and parameters of user-defined FB instances are displayed in Wiring.
3. Select the local variable or the parameter of a user-defined FB instance you want to wire.

IMPORTANT
Wiring is editable when Safety Communication I/O Editor is started for a selected SCS. When
the editor is started upon selecting I/O-list or RS project, Wiring is read-only.

4. Using Generation Manager, run the reflection process.

The global variables that you created in step 1 are deleted.
If Element is set, the local variable or parameter of a user-defined FB instance specified
in Wiring is set in Variable Name for the specified data area on the Comm. I/O Wiring tab
of Communication I/O Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.6 Importing I/O information into the safety communication I/O list> D2-32

D2.6 Importing I/O information into the safety

communication I/O list
You can import a list of I/O information obtained from a plant designer into the safety commu-
nication I/O list. When the list of I/O information contains program group definitions and com-
munication group definitions, these are imported as well.
TIP You can import I/O information into the safety communication I/O list when Communication I/O Editor is star-
ted for each P&ID group.

n Import file format

Create the file to be imported in the following format:
• File format
.xlsx file for Microsoft Excel
• Sheet name
Set a name of your choice.
• Sheet description
Lines of setting item names and I/O information corresponding to these items must be en-
tered. Enter one line of I/O information at a time for each type of I/O information. The fol-
lowing shows an example of the content of the sheet.
Names of setting items in the I/O information list
Types of I/O information (Header row of the list to be imported)

A B C D E ... BQ BR ... DD DE ... DP

Management Common Communication I/O Reference Information
I/O List Label
1 Information Information definition Information (Not RS Generation)
2 ROW_TYPE Area P&ID Sheet P&ID Tag I/O Type ... UDC1 UDC2 ... UDC40 P&ID Group ... F_Par_CRC
3 XXX XXX XXX XXX ... XXX XXX ... XXX XXX ... XXX
4 SG XXX XXX XXX XXX ... XXX XXX ... XXX XXX ... XXX
5 PG ... ... ...
6 CG ... ... ... XXX

I/O information of different types of I/O information

Figure D2.6-1 Example of sheet description

The following table shows the input values corresponding to the types of I/O information.

Table D2.6-1 Types and input values of I/O information

Type of I/O information Input value
Signal definition SG or blank
Program group definition PG
Communication group definition CG

TIP When a value other than SG, PG, or CG is entered in ROW_TYPE, the type of I/O information being imported
will be interpreted as signal definition.

SEE
ALSO For more information about types of I/O information, refer to:
D2.5, “Converting I/O information into a data structure that can be communicated with subsystems” on
page D2-23

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D2.6 Importing I/O information into the safety communication I/O list> D2-33

n Importing the I/O information list

You need to prepare the I/O information file in the xlsx format of Microsoft Excel. Follow these
steps to import the I/O information file in the xlsx format for Microsoft Excel:
1. Click [Sub menu] in Safety Communication I/O Editor and select [Import].
The Import wizard appears.

Figure D2.6-2 Import wizard

Figure D3.3-1 Property Group Selection dialog box

2. Select the check box of the setting item that needs to be displayed in the data grid area,
and click the [OK] button.
Only the selected setting item is displayed in the data grid area.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.4 Creating the node and I/O module > D3-5

D3.4 Creating the node and I/O module

There are two ways to create the node and I/O module.
• Creating the node and I/O module based on safety I/O list
You need to create the node and I/O module after defining the I/O module assignment in-
formation.
• Creating nodes and I/O modules without using the safety I/O list and safety communica-
tion I/O list
You need to define the I/O module assignment information in the safety I/O list and safety
communication I/O list after creating the nodes and I/O modules.
TIP It is necessary to manually input the settings of SEC401, SEC402, S2EN402, S2EN404, and the communica-
tion module based on the node settings.
It is also necessary to create the CPU node (FIO node number 1) manually even if you are creating nodes
and I/O modules based on the safety communication I/O list.

n Creating the node and I/O module based on safety I/O list
Follow these steps to create the node and I/O module based on the safety I/O list:
1. Click the [Create Node & IOM] button on the IOM Definition Editor tool bar.
The Create Node & IOM window appears, and the I/O module assignment information is
displayed in the list.

Figure D3.4-1 Create Node & IOM window

2. Select the check box of the assignment information of the node and I/O module that are
to be created or deleted, and click [Proceed].
The SCS name, node type, node number, slot number, unit number, I/O module category,
and the I/O module type that are defined in the safety I/O list are assigned, and the node
and I/O module are created.
The node and I/O module that are created are added to the data grid area of the IOM
Definition Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.4 Creating the node and I/O module > D3-6
TIP • You can check whether the assignment information of the node and I/O module that are to be created is
defined in the safety I/O list or not in Status.
• If the I/O module assignment information is defined in the safety I/O list, New is displayed. If the I/O
module assignment information is not defined in the safety I/O list, and if the node and I/O module are
created manually by using the IOM Definition Editor, Unused is displayed.
• When the check box of the assignment information of the node and I/O module, whose Status is Un-
used, is selected, and the [Proceed] button is clicked, the specified node and I/O module are deleted.

l Setting items and status when creating nodes and IOMs based on the
safety I/O list
The following table describes the setting items for creating nodes and IOMs based on the
safety I/O list.

Table D3.4-1 Setting items for creating nodes and IOMs based on the safety I/O list
Setting item Description
SCS Location information of node or IOM
Node Location information of node or IOM
Unit Location information of node or IOM (Only N-IO)
Slot Location information of node or IOM
IOM Definition Detailed description is displayed in the tool tip
I/O List Signal type of I/O
Duplex Yes, for redundant
Blank, for non-redundant

The following table describes the status when creating nodes and IOMs based on the safety
I/O list.

Table D3.4-2 Status of the Create Node & IOM window

Status Description
New The I/O module assignment information is defined in the safety I/O list
Unused The I/O module assignment information is not defined in the safety I/O list, and the
node and I/O module are created manually by using the IOM Definition Editor

l Creating a node
Follow these steps to create a node without using the safety I/O list:
1. Click the [Create New Node] button on the IOM Definition Editor tool bar.
The Create Node dialog box appears.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.4 Creating the node and I/O module > D3-7

Figure D3.4-2 Create Node dialog box

2. Click the [OK] button after entering the setting items.

The Create Node dialog box closes, and the node is added to the data grid area of the
IOM Definition Editor.

l Creating an I/O module

Follow these steps to create an I/O module without using the safety I/O list:
TIP It is necessary to manually input the settings of SEC401, SEC402, S2EN402, S2EN404, and the communica-
tion module based on the node settings.

1. Click the [Create New IOM] button on the IOM Definition Editor tool bar.
The Create IOM dialog box appears.

Figure D3.4-3 Create IOM dialog box

TIP When [Duplex] check box is selected, the adjacent slot is occupied when the I/O module is created.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.4 Creating the node and I/O module > D3-8
2. Click the [OK] button after entering the setting items.
The Create IOM dialog box will close, and the I/O module is added to the data grid area
of the IOM Definition Editor.

n Setting items when creating nodes and I/O modules without using
the safety I/O list or safety communication I/O list
The types of I/O modules that you can add vary depending on the type of the node.
The following table shows the relationship between the SCS type and the node that can be
added.

Table D3.4-3 Relationship between the SCS type and the node that can be added
Node type Type of SCS (*1)
SSC60x SSC50x SSC57x S2SC70x
FIO FIO FIO FIO N-IO
SNB10x Yes Yes Yes Yes No
S2NN30D No No No No Yes
*1: Yes: Can be added.
No: Cannot be added.

The following table describes the setting items for creating a node.

Table D3.4-4 Setting items for creating a node

Setting item Description
SCS Name of the SCS in which the node is installed
Type Type of the node that is added
Set ESB Bus/Optical ESB Bus, or N-ESB Bus
Folder IOM folder
Set FIO, or N-IO
Node Node number
Comment Node related comments

The following table describes the setting items for creating an I/O module.

Table D3.4-5 Setting items for creating an I/O module

Setting item Description
SCS Name of the SCS in which the node is added
Node Node number
Folder Name of the folder in which the node is installed
Unit Unit number
Slot Slot number
Category Category of the IOM that is added
Type Type of the IOM that is added
Duplex Make the adjacent IOM dual redundant
Device index Device index of IOM
Comment Node related comments

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.5 Editing the setting items of the node and I/O module > D3-9

D3.5 Editing the setting items of the node and

I/O module
Follow these steps to edit the setting items of the node and I/O module:
1. In the IOM Definition Editor list, double-click an editable cell.
A dialog box appears, asking you to confirm the check-out.
2. Click [Yes].
The corresponding node definitions and I/O module definitions are checked out, and
check-out icons appear in the list.
3. In the cells of the IOM Definition Editor list, enter the values of the setting items of the
node and I/O module.
4. The Duplex setting of I/O modules must match the setting in the safety I/O list. To change
the Duplex setting of the I/O module in the IOM Definition Editor, follow these steps:
a. In the System Structure Navigator, select a file under the I/O-List folder and start the
Safety I/O Editor. Clear [RS Project] of the definitions for which you want to change
the Duplex setting and perform a check-in.
b. In the list of the IOM Definition Editor, select the row of the target I/O module, change
the [Duplex] setting, and then perform a check-in.
c. In the System Structure Navigator, select a file under the I/O-List folder and start the
Safety I/O Editor. Restore the [RS Project] that you cleared in step a and perform a
check-in.

n Bulk editing of the IOM definition

The user can perform bulk definition of multiple IOM definition elements by using the design
results of Safety I/O Editor or Safety Communication I/O Editor.

l Checking/resolving the issues in the I/O module assignment information

You can check the details of the I/O module assignment information by utilizing the check
function of the grid rules by using Safety I/O Editor or Safety Communication I/O Editor.
If issues are found in the I/O module assignment information, you can correct the design rela-
ted details by using Safety I/O Editor or Safety Communication I/O Editor, or create and edit
the node and IOM which the design information requests by using IOM Definition Editor.

l Generating the I/O module assignment information by using IOM

You need to perform the following procedure.
1. Click the [Create Node & IOM] button on the IOM Definition Editor.
The generation and update process of the IOM are executed.
Once the generation and update process of the IOM end, the IOM Definition Editor ap-
pears. The default value is applied to the properties of the node and IOM that are created
based on the design information.
2. After setting the node and IOM properties, click [Save] in the IOM Definition Editor.
3. Check in the changes from the Check-in window.
The editing is completed, and the details in the System Structure Navigator are updated.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.6 Deleting the node or I/O module> D3-10

D3.6 Deleting the node or I/O module

Follow these steps to delete the node or the I/O module:
1. Select the node or the I/O module in the IOM Definition Editor, and click the [Delete Row]
button on the IOM Definition Editor tool bar.
When the node is deleted, the IOM under the node is also deleted. When the IOM is de-
leted, the information is not deleted from the safety I/O list, and only the IOM data is de-
leted.
2. Check in the changes from the Check-in window.
The details in the System Structure Navigator are updated.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D3.7 Saving the node and I/O module and performing check-in> D3-11

D3.7 Saving the node and I/O module and

performing check-in
You can save the node and I/O module and perform a check-in. By doing this operation, the
node and the I/O module are stored in the AD project.

n Saving the node and I/O module

Follow this step to save the node and the I/O module:
• On the tool bar of AD Organizer, click [Save] while the focus is on the IOM Definition Edi-
tor.

n Checking in the node and I/O module

• In the Check-in window, check in the created node and I/O module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4. Overview of RS generation> D4-1

D4. Overview of RS generation

The reflection process and the SCS project build process are available as part of RS genera-
tion.
After creating engineering data by using iDefine, import the iDefine-config file with AD Organ-
izer and check in before running the reflection process.
• Reflection process
The safety I/O list, safety communication I/O list, and IOM information that were edited in
AD Organizer and the iDefine-config file are acquired from the AD Server and converted
into an SCS project file (hereinafter referred to as a conversion). Once the reflection proc-
ess has been successfully completed, the data of the safety I/O list, safety communica-
tion I/O list, IOM information, and iDefine-config file are reflected onto the SCS database.
The iDefine-config file is obtained when engineering is performed using iDefine.
• Build process of the SCS project
You can run the SCS project build. If the reflection process is required, the build process
is run after the reflection process is automatically run. The SCS project build process
builds the entire SCS project while including the following engineering data in addition to
the setting items related to the safety I/O list, safety communication I/O list, and IOM in-
formation:
• Function blocks edited with SCS Manager or other builders
• Subsystem settings
• Engineering data in the iDefine-config file
Be sure to perform the build process of the SCS project when downloading the data to
SCS.
The target information for RS generation is as follows:
• Safety I/O list created by the Safety I/O Editor
• Safety communication I/O lists created with Safety Communication I/O Editor
• IOM information created by the IOM Definition Editor
• iDefine-config file
The related builders are as follows:
• Dictionary View (Variable)
• I/O Wiring View
• I/O Parameter Builder
• Tag Name Builder
• Link Architecture View
• Multi-Language Editor
• Communication I/O Builder

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.1 Reflection process > D4-2

D4.1 Reflection process

Conversion and import are performed as part of the reflection process.

n Conversion
When engineering is performed with the safety I/O list, safety communication I/O list, IOM in-
formation, and iDefine from AD Server, the iDefine-config file is also obtained and the file that
is to be entered in SCS Manager and the builders is generated.
In the conversion process, you can perform the column check related to the FieldMate Valida-
tor or check the items added to the current setting information.

l Column check related to the FieldMate Validator

You can check the details of the columns related to the FieldMate Validator of the safety I/O
list. When the FieldMate Validation Status and Overwrite Status turn to the following, warning
appears.
FieldMate Validation Status is Assigned, or Overwrite Status is Updated
The warning shows the channel in question. The user can verify the details and proceed with
the conversion.

l Checking added items in the Dictionary view

You can check the current setting information. If the user has defined the same variable name
as the additional item, it will result in error. The following message appears and the check is
terminated.
Dictionary View: Same variable name exists. (Variable name: xxxx)

n Import
You can import the converted file to SCS Manager and the builder.
The contents that were defined in AD Organizer and iDefine are reflected in SCS Manager
and the builders. During the import process, the operation history and changed files are not
saved.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.2 Build process of the SCS project > D4-3

D4.2 Build process of the SCS project

The SCS project build process obtains the safety I/O list, safety communication I/O list, IOM
information, and the iDefine-config file and then runs a build.
The iDefine-config file is obtained when engineering is performed with iDefine. If a reflection is
required, you need to run the build after running the reflection.
If there is nothing in the modified list of Generation Manager, you cannot run the build.
After the build succeeds, you cannot run the reflection process and the build again.

n Difference between the reflection process and the SCS project build
process
The difference between the reflection process and the SCS project build process is that the
reflection process does not run the SCS project build.
Even if the IOM definition or the assignment is not completed in AD Organizer, you can create
the Program Organization Unit (POU). The reason for this is because it is possible to proceed
with the creation of the application logic by using the I/O variables of the safety I/O list and
safety communication I/O list.
The I/O variables are reflected onto Dictionary View when the reflection process is performed.
SEE
ALSO For more information about items that should be configured in the safety I/O list and safety communication
I/O list to run the reflection process, refer to:
“n Handling of the safety I/O list and safety communication I/O list” on page C2-3

n Build in Generation Manager and SCS Manager

Both the Generation Manager build and SCS Manager build create a database for SCS, but
they have the following differences:
If the build succeeds in Generation Manager, the corresponding safety I/O list, safety commu-
nication I/O list, and IOM information of AD Organizer are reflected onto the SCS database
via SCS Manager. When the safety I/O list, safety communication list, and IOM information
are edited by using AD Organizer, the modifications are not imported into the SCS database.
Therefore, it is necessary to perform the build with Generation Manager.
On the other hand, when performing a build by using SCS Manager, the status of the safety
I/O list, safety communication I/O list, and IOM information of AD Organizer is not taken into
account. When downloading to the SCS, the download cannot be done if the safety I/O list,
safety communication I/O list, and IOM information of AD Organizer have not been reflected
onto the SCS database. You can run the analyzer and launch the SCS simulator.
Therefore, when the safety I/O list, safety communication I/O list, and IOM information are
edited, it is necessary to run the build successfully once in Generation Manager.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.3 Generation Manager window configuration > D4-4

D4.3 Generation Manager window configuration

Generation Manager screen is shown in the following figure.

Area for specifying

the project for
generation

Change information list

Message display area

Figure D4.3-1 Generation Manager window configuration

n RS project
The target RS project can be selected from the drop-down list box. You can select the RS
project that is registered in the AD project.

n SCS project
The SCS project that is defined in the RS project can be selected from the drop-down list. The
SCS project that is displayed in the list box is the SCS project that is created by using the
safety I/O list or safety communication I/O list of AD Organizer from the SCS project proper-
ties. The list is displayed in descending order sequence of the domain number and station
number. If the RS project is switched in the drop-down list of the RS project, the station at the
topmost position in the list will be in the selected state.

n Change information list

Only the information related to the SCS project that is selected from the drop-down list box of
the SCS project is displayed in the change Information list.
Soon after Generation Manager is started up, the RS project and the SCS project that were
selected in the System Structure Navigator during start-up will be in selection status.
The details that are displayed in the change information list is shown in the following table.

Table D4.3-1 Column specification of the change information list

Item name Description
Modified Target Displays the name of the build which needs to be changed.
When changes need to be made, the builders are shown in the order of
Dictionary View, I/O Wiring View, I/O Parameter Builder, Communica-
tion I/O Builder, Dictionary View (iDefine), Tag Name Builder, and POU.
Modified Date The date and time of file update are displayed.
Reflection Result The results of reflection are displayed.
• Succeed: Successful
• Fail: Failure
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.3 Generation Manager window configuration > D4-5
Table D4.3-1 Column specification of the change information list (Table continued)
Item name Description
Build Result The results of the build are displayed.
• Succeed: Successful
• Fail: Failure

n Previous result
The progress status message of the last RS generation is displayed.

n Skipping reflection of a program POU

This option is used when the engineering is performed by using iDefine. This option is appli-
cable to SCS projects that use subsystem communication or safety subsystem communica-
tion, and you can use the option as necessary when you change the POU included in an SCS
for which downloading is already performed.
When the reflection process is performed after loading the iDefine-config file with AD Organiz-
er, changes made to the POUs, variables, FB instances, and tag name information are all re-
flected together onto the SCS project.
For example, if any changes are made to a user-defined FB that uses a subsystem communi-
cation FB, you may want to download only the changed user-defined FB and the changes in
the relevant subsystem communication to the SCS first and check the operation of the FB by
using the program POU that is already downloaded.
In this case, when the reflection process is performed upon selecting this check box, changes
will be reflected onto the SCS project except for the changes in the program POU and tag
names in the iDefine-config file. However, even if user-defined FBs or user-defined FUs are
deleted in iDefine, they will not be deleted from the SCS project. This is because, if such FBs
or FUs are deleted from the SCS project, a build error will result when the FBs or FUs are
used in the program POU that is already downloaded.
After testing of user-defined FBs that use a subsystem communication FB and other subsys-
tem communication related functions is finished, clear the check box and run the reflection
and build process again. By doing so, you can reflect all changes that were made with iDefine
onto the SCS project.
The following table shows the changes of the status icon for the iDefine Configuration folder
shown in System Structure Navigator after selecting the check box or clearing it and perform-
ing the build process:

Table D4.3-2 Status icon of the iDefine Configuration folder after the build process
Check box Status icon after the build process
Selected The work status is retained even if the build is successful. The work status icon
remains shown next to the iDefine configurator folder of System Structure navi-
gator.
The user can continue to perform the reflection process.
Cleared The work status icon next to the iDefine configurator folder of System Structure
Navigator disappears when the build process is successful.

n Message display area

The message display area displays the execution result of RS generation.

n Reflection button
When you click the Reflection button, conversion is run and the converted file is imported to
SCS Manager and the builders.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.3 Generation Manager window configuration > D4-6
While performing the conversion, the safety I/O list, safety communication I/O list, and IOM
information file, and the iDefine-config file as well when engineering by using iDefine, are ac-
quired and then the file for import is created.
When importing, the file that was generated through conversion is imported to SCS Manager
and the builders. The progress status appears in the message display area.
When there is nothing in the modified information, you cannot run the reflection process.
The successfully converted safety I/O list, safety communication I/O list, IOM information file,
and iDefine-config file are imported to SCS Manager and the builders.
If the reflection process fails, you can run the reflection process once again. Run the process
from the conversion stage again. When the reflection process is canceled by using the Cancel
button, the result will be the same as the case when reflection fails.
• In the reflection process, the input/output modules are wired to the existing input/output
variables. A check is then run to make sure that it is consistent with the IOM definition.
Regardless of whether it is an input/output variable, the following values are compared in
the iDefine-config file and AD Suite:
• I/O Tag
• I/O Type
• Node
• Unit
• Slot
• IOM Type
• Terminal
If the value is different, an error dialog box appears and the reflection process is stopped.
• If a tag name is included in the iDefine-config file and a CENTUM VP integration package
or a FAST/TOOLS integration package is not enabled, a message stating that the tag
name definition is not reflected appears in the message display area.

n Build button
This button runs the SCS project build process. After the reflection process succeeds, the
SCS project build process is executed.
The safety I/O list, safety communication I/O list, and IOM information file, as well as the
iDefine-config file when engineering by using iDefine, are all acquired from the AD Server, the
reflection is performed when it is required, and then the SCS project build is run.
If there is nothing in the change information, you cannot run the SCS project build process.

n Cancel button
This button cancels the reflection process and the SCS project build process. It is enabled on-
ly when the reflection process and the SCS project build process are executed. If the cancel
button is clicked during the execution of the reflection process and the SCS project build proc-
ess, the reflection process and the SCS project build process will be terminated.
When the cancel button is clicked, [Fail] is displayed in the [Reflection Result] or [Build Result]
of the change information.
Once the import to SCS Manager and the build are executed, the cancel button will be disa-
bled.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.3 Generation Manager window configuration > D4-7

n Process when the RS project and SCS project were switched in the
RS Generation Manager
When the RS project and SCS project are switched in the Generation Manager dialog box,
the screen is refreshed. The safety I/O list, safety communication I/O list, and IOM information
file, and the iDefine-config file as well when engineering by using iDefine, of the SCS project
that was newly selected are acquired from the AD Server, and the change information list
shows which builder requires modifications.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.4 Operating procedure of RS generation > D4-8

D4.4 Operating procedure of RS generation

The RS generation flow is shown in the following figure.

Start of RS generation

Get safety I/O lists, safety communication I/O lists,

and IOM information files from the AD Server
If iDefine is used, also get iDefine-config file

Conversion
Reflection
Import

Build SCS projects

Reflect to the AD Server

End of RS generation

Figure D4.4-1 RS generation process

n Starting Generation Manager

1. In the System Structure Navigator of AD Organizer, select SCS.
2. Perform either of the following operations:
• Right-click and select [RS Generation Manager] from the context menu.
• Form the sub menu of the System Structure Navigator, select [ProSafe-RS] > [RS
Generation Manager].
Generation Manager starts, and the builder that requires modifications is displayed in the
change Information list.

n Executing the reflection process

1. You need to select the target RS project and SCS project for RS generation.
2. Check the change information, and click the [Reflection] button.
If the Access Control and Operation History Management Package is enabled, the Engi-
neer Authentication dialog appears once the import starts.
If the security of the SCS project is set, the Password Input dialog box appears for the
project.
3. Enter the required fields in the Engineer Authentication dialog box and the Password In-
put dialog box of the SCS project. If the Engineer Authentication and the Password Input
dialog boxes do not appear, no action is required.
The conversion is performed, and the safety I/O list, safety communication I/O list, and
IOM information are imported to the AD Server.
If the reflection process succeeds, Succeed is displayed in Reflection Result.
If the reflection process fails, Fail is displayed in Reflection Result.
TIP When the reflection process is performed, you can only use the [Cancel] button.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.4 Operating procedure of RS generation > D4-9

n Reflecting the POU that was defined by using iDefine

When running the reflection process, the POU that was defined by using iDefine is reflected in
SCS Manager. The run sequence of the POUs that were defined by using iDefine and SCS
Manager is sorted in the Link Architecture View of SCS Manager. POUs that were defined in
SCS Manager are not reflected in iDefine. In iDefine, only the run sequence of the POUs that
were defined in iDefine is shown.
This section describes the rules for reflecting POUs in SCS Manager after running the reflec-
tion process after adding, switching, or deleting POUs in iDefine.
• When POU was added by using iDefine
POUs that were defined in iDefine and the following POUs that were defined in SCS
Manager are treated as a series of the same run sequence; POUs that were added by
using iDefine are added below that.
Example:
The following example shows how A1, UD1, and UD2 are treated as a series of
the same run sequence and A2 is added below that.

iDefine iDefine

Add by using iDefine

Reflection process Reflection process

SCS Manager SCS Manager

Define by using
SCS Manager
Reflect in SCS Manager

Figure D4.4-2 Reflecting POUs that were added by using iDefine in SCS Manager

• When the POU sequence was changed by using iDefine

POUs that have had their sequence changed in iDefine and the following POUs that were
defined in SCS Manager are treated as a series of the same run sequence, and their se-
quence in SCS Manager is also changed.
Example:
The following example shows how A1, UD1, and UD2, and B1 and UD3 are trea-
ted as a series of the same run sequence and how their run sequence is changed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.4 Operating procedure of RS generation > D4-10
iDefine iDefine

Switch the sequence

by using iDefine

Reflection process Reflection process

SCS Manager SCS Manager

Define by using
The sequence is changed
SCS Manager

Figure D4.4-3 Reflecting POUs that have had their sequence changed by using iDefine in SCS Manag-
er

• When POU was deleted by using iDefine

POUs that were deleted by using iDefine are deleted in SCS Manager.

n Reflecting the ANN and ANN_FUP tag names that were defined by
using iDefine
When running the reflection process, configurations related to the tag names corresponding
to the ANN and ANN_FUP instances that were configured by using iDefine are reflected in
the Tag Name Builder. Once the instance name has been reflected, it is reflected in the same
Element Name in the Tag Name Builder for as long as it exists. New instances that were add-
ed by using iDefine are reflected in the unused Element Names in ascending order.

n Running the SCS project build process

1. Click the [Build] button in Generation Manager.
The safety I/O list, safety communication I/O list, and IOM information, as well as the
iDefine-config file when engineering by using iDefine, are all acquired from the AD Serv-
er, the reflection is performed when it is required, and then the SCS project build process
is run.
The results of the SCS project build process is displayed in the message display area.
• If the SCS project build process succeeds, Succeed is displayed in Build Result of
the change information list. The safety I/O list, safety communication I/O list, IOM in-
formation file, and iDefine-config file for which the build is successful are reflected on-
to the AD Server. You cannot run the reflection process and the build again.
• If the SCS project build process fails, Fail is displayed in Build Result of the change
list. Even if the build fails, the safety I/O list, safety communication I/O list, IOM infor-
mation, and iDefine-config file are reflected onto SCS Manager as long as the reflec-
tion process is successful.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.5 Error messages in Generation Manager > D4-11

D4.5 Error messages in Generation Manager

This section describes the error messages in Generation Manager.

n Error during startup

An error message appears when a communication error occurs during startup. Generation
Manager will not start up.

n Error during check-out

If the check-out of the safety I/O list, safety communication I/O list, and IOM information file
from the AD Server fails when the conversion begins, the name of the file that failed check-
out is shown in the message display area.
When a communication error occurs during check-out, the following message is displayed in
the message display area.
[Cannot connect to the server.]

n Error during unlock

An error message is displayed if a communication error occurs when the reflection process or
SCS project build process fails and the check-out is canceled. To release the lock, restart
Generation Manager after connecting to the server.

n Error during check-in

An error message is displayed if a communication error occurs during check-in to the AD
Server after the reflection process and SCS project build process have succeeded. To per-
form a check-in, restart Generation Manager after connecting to the server.

n Error when there is no conversion object

If the reflection button is clicked even though there is nothing in the change information list,
the following messages are displayed.

Figure D4.5-1 Error during conversion

After the build has succeeded, this error is displayed when the reflection is performed once
again.

n Engineer authentication error

When the User Authentication screen of the Access Control and Operation History Manage-
ment Package appears, and if the engineer group associated with the engineer does not have
the required access rights for Dictionary View, I/O Wiring View, I/O Parameter Builder and the

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.5 Error messages in Generation Manager > D4-12
build, the following message appears in the message display area and the reflection process
results in an error.
[ERROR: Don't have access right for the operation.]

n SCS project security error

If three failed password entry are made for the project in the SCS project security, the follow-
ing message is displayed in the message display area. Then, the reflection will result in error.
[ERROR: Cannot open the project.]

n Error during the reflection process and the SCS project build
process
If SCS Manager is started during the reflection process and SCS project build, the following
error message is displayed and the processing is terminated.
SCS Manager is being executed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D4.6 Engineering after changing the safety I/O list and safety communication I/O list> D4-13

D4.6 Engineering after changing the safety I/O

list and safety communication I/O list
The user can proceed with engineering by using the safety I/O list or safety communication
I/O list before the I/O information is fixed. Once the information is fixed, the changes can be
reflected in the engineering data by loading the updated safety I/O list or safety communica-
tion I/O list at a later stage.
If the safety I/O list is modified, you need to load the safety I/O list into the Safety I/O Editor,
check the differences, and reflect them to the database. Once the safety I/O list is imported,
you need to use the IOM Definition Editor to define the IOM.
If the safety communication I/O list is modified, you need to load the safety communication I/O
list into Safety Communication I/O Editor, check the differences, and reflect them onto the da-
tabase. Once the safety communication I/O list is imported, you need to use IOM Definition
Editor to define the IOM.
When the safety I/O list has been changed, if the engineered results are exported to
FieldMate Validator to be tested and are modified, you must import the updated I/O list and
reflect the changes onto the SCS project. Once the changes are reflected to the SCS project,
you must return to the previous step of engineering and proceed with the task according to
the updated details.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5. Engineering by using iDefine> D5-1

D5. Engineering by using iDefine

This section describes the engineering procedure in iDefine after creating an iDefine project
and using the file exported for iDefine from AD Organizer.
1. Export the ProSafe-RS I/O file from AD Organizer.
2. Import the ProSafe-RS I/O file by using iDefine and create an application. Export the re-
sult as an iDefine-config file.
3. Import the iDefine-config file by using AD Organizer. It is recommended that you back up
the iDefine project at this step.
SEE
ALSO For more information about the procedures to export files for iDefine from AD Organizer, refer to:
D5.1, “Exporting the ProSafe-RS I/O file from AD Organizer” on page D5-2
For more information about the engineering flow when using iDefine, refer to:
C2.2, “Work flow of I/O list engineering with iDefine” on page C2-11
For more information about specific operations in iDefine, refer to:
iDefine User Guide (PR03076-MAN-970_01)
For more information about tests that are run using iDefine test functions, refer to:
6., “Using iDefine in tests” in Test Function Guide (IM 32P04B30-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.1 Exporting the ProSafe-RS I/O file from AD Organizer> D5-2

D5.1 Exporting the ProSafe-RS I/O file from AD

Organizer
If you are using iDefine, export the safety I/O list, safety communication I/O list, and I/O mod-
ule configurations as a ProSafe-RS I/O file in AD Organizer. The exported file is known as
ProSafe-RS I/O file. A ProSafe-RS I/O file is created for each SCS project.
Follow these steps to export the ProSafe-RS I/O file:
If there are any files being edited in Safety I/O Editor, Safety Communication I/O Editor, or
IOM Definition Editor, check-in the files and export them. Contents that are being edited are
not exported.
1. In the System Structure Navigator of AD Organizer, right-click the SCS project to be ex-
ported in the System Structure Navigator and select [Safety I/O Editor] or [Safety Com-
munication I/O Editor].
TIP If you launch the Safety I/O Editor in the following ways, the files to be exported for iDefine cannot be expor-
ted.
• Double-clicking the [I/O definition] under the module folder.
• In the Change Set Detail dialog box, right-clicking the file and selecting [Launch Editor] from the context
menu.
• Launching the editor in read-only mode.

2. Select [Export to iDefine] from the sub-menu of Safety I/O Editor or Safety Communica-
tion I/O Editor.
The File Selection dialog box appears.
3. Specify the export location, and click [OK].
The file is exported.
TIP The same data is exported whether you use Safety I/O Editor or Safety Communication I/O Editor. However,
different data will be exported depending on what is selected when you start the editor. The relationship be-
tween the selection and exported data is as follows:
• When an I/O list is selected
Safety I/O of all P&ID groups
Safety communication I/O of all P&ID groups
Node and I/O module data for all P&ID groups
• When an RS project is selected
Safety I/O of all SCSs included in the selected RS project
Safety communication I/O of all SCSs included in the selected RS project
Node and I/O module data for all SCSs included in the selected RS project
• When an SCS project is selected
Safety I/O of the selected SCS
Safety communication I/O of the selected SCS
Node and I/O module data for the selected SCS

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.2 Creating applications by using iDefine > D5-3

D5.2 Creating applications by using iDefine

Follow these steps to create applications by using iDefine:
1. Import the ProSafe-RS I/O file.
2. Use the following logic editor to create an application template.
This task can be performed at the same time as the engineering of the I/O list by using
AD Organizer, so you can perform this task before importing the ProSafe-RS I/O file.
• Function Block / Function
• Typical
a. In the ProSafe-RS IO Tag Name window, create the parameter pattern for each type
to define the tag name.
b. From the variables or function block instances that were defined in Typical, set the
created parameter pattern to the one that you wish to assign a tag name.
3. For each I/O Tag, assign the corresponding Typical.
4. Use the following logic editor to create an application logic:
• Group Typical
• Cause and Effect module
• State Analysis module
5. Build by using the Output Configuration and create the variables, tags and an executable
program in FBD format.
6. Export the iDefine-config file.
SEE
ALSO For more information about the procedure to import ProSafe-RS I/O files to iDefine, refer to:
10., "IMPORT FROM AD SUITE" in iDefine User Guide (Yokogawa Extensions) (PR12002-
MAN-980_01)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.3 Import the iDefine-config file by using AD Organizer> D5-4

D5.3 Import the iDefine-config file by using AD

Organizer
Import the iDefine-config file that was exported from iDefine to AD Organizer. The iDefine-
config file contains the POU, I/O Tag, and variables that were defined in iDefine.
Follow these steps to import the iDefine-config file:
1. In the System Structure Navigator of AD Organizer, select the SCS project for which you
want to import the file, and select [Import iDefine configuration] from the context menu.
The Import dialog box appears.

Figure D5.3-1 Import dialog box of the iDefine-config file

TIP If you select an SCS project with a folder that has an exclamation mark, multiple SCS projects, or an SCS
project that was created in RS original engineering, you cannot select [Import iDefine configuration].

2. Specify the iDefine-config file that will serve as the import source.
3. Perform either of the following operations:
• If you do not want to change the settings for FBs with an instance name, skip to step
4.
• If you want to change the settings for FBs with an instance name, follow the steps
described in the next section "■ Selecting a FB with an instance name."
4. In the Import dialog box, click [OK].
The iDefine-config file is checked-out.
5. On the Check-in window, check in the iDefine-config file.
The iDefine-config file is imported.
TIP Regardless of whether the settings for FBs with an instance name are changed, the FB instance setting file is
checked-out and checked-in together with the iDefine-config file.

n Selecting a FB with an instance name

The instance names of all the FBs that are used in application logics that were created by us-
ing iDefine are configured separately. Using this dialog box, you can select whether to assign
instance names to the FBs to be reflected in SCS projects for each FB type.
Change the setting to use SCS Manager to assign instance names to any unique FB types
that do not have an instance name configured by default or to reduce the number of variables
that are registered in the Dictionary View.
Follow these steps to change the settings for FB with an instance name.
1. To change the settings for FBs with an instance name, select the [Show advanced set-
ting] check box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.3 Import the iDefine-config file by using AD Organizer> D5-5
In the Import dialog box, the [Instances] button appears.

Figure D5.3-2 Import dialog box with advanced settings

2. Click [Instances].
The FB Selection dialog box appears.

Figure D5.3-3 FB Selection dialog box

3. When importing, select the FB with an instance name check box.

• The function block is categorized; clicking the triangle on the left-hand of a category
shows the function blocks contained within that category. You can select all of the
check boxes of the function blocks that are contained within a category at the same
time by selecting the check box for that category.
• Clicking [Reset to Default] returns the FB selection status to its initial state.
4. Click [Save].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.4 Precautions when performing engineering by using iDefine > D5-6

D5.4 Precautions when performing engineering

by using iDefine
This section describes the terms used in ProSafe-RS and iDefine and the setting items that
have any difference in specifications as the precautions for using iDefine in the engineering
work.
You must understand these precautions before you start engineering.

n I/O Wiring
The following table compares the I/O Wiring information that is displayed in ProSafe-RS and
iDefine.

Table D5.4-1 Comparison of terms between ProSafe-RS and iDefine (I/O Wiring information)
iDefine term ProSafe-RS term Description
Ch - Chassis Node iDefine identifies if the Node is for N-IO or FIO by adding a pre-
fix.
Format: [F/N][Node no.]
F: Indicator for FIO, N: Indicator for N-IO
Sl - Slot Unit iDefine combines the information for Unit and Slot in the case of
N-IO.
Slot Format for FIO: [Slot no.]
Format for N-IO: [Unit no.][Slot no.]
Pt - Point Channel or Terminal Channel in the I/O Parameter Builder, and Terminal in AD Or-
ganizer

n Variables
The following table compares the variables terms displayed in ProSafe-RS and iDefine.

Table D5.4-2 Comparison of terms between ProSafe-RS and iDefine (Variables)

iDefine term ProSafe-RS term Description
Tag Variable (Global Global variables of ProSafe-RS are called "Tag" or "TriTag" in
Scope) iDefine. In iDefine, Tags are defined in Client IO Table and Typi-
cal. The defined Tags are reflected in Dictionary View of
ProSafe-RS as variables.
Variable Variable (Local In ProSafe-RS, variables and parameters are defined by Dic-
Scope) tionary View. In iDefine, those are defined by Typical, Function
Parameter Block, or Structured Text. Local variables and parameters of
ProSafe-RS are called “Variable” in iDefine.

n Variable types
In iDefine, Tag types are specified in Client IO Table. The Tags will be reflected in Dictionary
View as global variables. The following table shows the mapping between Tag types in iDefine
and variable types in ProSafe-RS.

Table D5.4-3 Mapping of terms between ProSafe-RS and iDefine (Tag types in iDefine and variable
types in ProSafe-RS)
Tag type in iDefine Variable type in Description
ProSafe-RS
RI IO_REAL -
RO IO_REAL -
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.4 Precautions when performing engineering by using iDefine > D5-7
Table D5.4-3 Mapping of terms between ProSafe-RS and iDefine (Tag types in iDefine and variable
types in ProSafe-RS) (Table continued)
Tag type in iDefine Variable type in Description
ProSafe-RS
DI IO_BOOL -
DO IO_BOOL -
IM DINT -
DM BOOL -
RM REAL -
DEVICE N/A Variable will not be created in Dictionary View of ProSafe-RS for
Tags of this type. This Tag type is used to assign a Typical to a
Tag and instantiate the Typical.
IC COM_DINT Binding variable for inter-SCS safety communication
RC COM_REAL Binding variable for inter-SCS safety communication
DC COM_BOOL Binding variable for inter-SCS safety communication

n Functions and function blocks

The following table shows the functions and function blocks that have different names in
iDefine and ProSafe-RS, or those available only in either of them.

Table D5.4-4 Mapping of functions and function blocks between iDefine and ProSafe-RS
ProSafe-RS
Category iDefine name Description
name
IEC61131-3 standard ADD + Supported parameter data types are different be-
functions tween iDefine and ProSafe-RS.
When you perform engineering by using iDefine,
use parameters of the data type DINT, REAL,
STRING, or TIME, which are supported by
ProSafe-RS. If parameters of types other than
DINT, REAL, STRING, and TIME are used, a
build error will occur.
DIV / -
GE >= -
GT > -
LE <= -
LT < -
MOVE 1 GAIN -
MUL * -
NE <> -
SUB - -
TIS function NUMBITS - Exported as user-defined function (ST) NUM-
BITS8 or NUMBITS16.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.4 Precautions when performing engineering by using iDefine > D5-8
Table D5.4-4 Mapping of functions and function blocks between iDefine and ProSafe-RS (Table contin-
ued)
ProSafe-RS
Category iDefine name Description
name
StateModule function TIS_CALCST - Exported as user-defined function block (ST).
blocks (*1)
TIS_COND2 - Exported as user-defined function block (ST).
TIS_COND3 -
TIS_GST - Exported as user-defined function block (FBD).
TIS_SE - Exported as user-defined function block (ST).
TIS_SE_FIRS -
T
TIS_SE_NT -
TIS_SEP4 - Exported as user-defined function block (ST).
This creates AND_DWORD and OR_DWORD
user-defined functions (ST) together.
TIS_TMR - Exported as user-defined function block (ST).
StateModule functions TIS_SEP1 - Exported as user-defined function (ST).
(*2)
Gas flow rate calcula- - ACCUM Not supported in iDefine.
tion function blocks (In-
terference-free) - AGA_3
- AGA_7
- AGA_R
- ECWR_B
- ECWR_I
- ECWR_R
Data buffering function - BUF_DIF_B Not supported in iDefine.
blocks (Interference-
free) - BUF_DIF_I
- BUF_DIF_R
- BUF_TIM_I
- BUF_TIM_R
- BUF_TRIG_B
- BUF_TRIG_I
- BUF_TRIG_R
DNP3 communication - DNP3_AI_16 Not supported in iDefine.
function blocks (Inter-
ference-free) - DNP3_AI_32
- DNP3_AI_SF
- DNP3_AO_16
- DNP3_AO_32
- DNP3_AO_SF
- DNP3_BI
- DNP3_BO
- DNP3_CT_16
- DNP3_CT_32
*1: Function blocks that are created when an SA module is converted to FBD
*2: Functions that are created when an SA module is converted to FBD

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<D5.4 Precautions when performing engineering by using iDefine > D5-9

n Differences of terminology during test operations

The terminology during test operations vary between iDefine and ProSafe-RS. The following
table shows the correspondence between the varying terminologies.

Table D5.4-5 Correspondence chart for test operation terminology of iDefine and ProSafe-RS
iDefine Terminology ProSafe-RS Terminology
Disable Lock
Enable Unlock
Set Write
Single Step One Cycle
Start Debug Start Debug Mode
Stop Debug Stop Debug Mode
Start Target Simulation
Stop Simulator Stop Simulation Mode
Cycle Scan Time Cycle Timing

n Notes on the reflection process for the iDefine-Config file

When the reflection process is performed after loading the iDefine-config file including sub-
system communication FB or safety subsystem communication FB with AD Organizer, the
POU and FB are all downloaded together onto the SCS project. In order to verify the subsys-
tem communication FB or safety subsystem communication FB alone before downloading the
application, use the function for skipping reflection of the program POU onto the SCS project.
SEE
ALSO For more information about how to skip reflection of a program POU onto an SCS project, refer to:
“n Notes on the reflection process for the iDefine-Config file” on page D5-9

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E. Changing application > E-1

E. Changing application
This section describes the procedure for online change of applications, procedure of import/
export, and the procedure to reuse SCS project database.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1. Online change of applications> E1-1

E1. Online change of applications

This chapter describes the procedure for online change of applications.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.1 Online change download> E1-2

E1.1 Online change download

Online change download changes a part of an application without interrupting SCS functions.
In SCS, the data stored in main memory of the CPU module is updated and changes are stor-
ed in flash memory of the CPU module as well. When performing online change download of
I/O definitions, changes are also reflected in the non-volatile memory of the input/output mod-
ules. Data downloaded to an SCS is also saved in the master database on the SENG.
TIP The SCS operating mode will not be changed when online-change downloading is performed.

n Items for which online change download is allowed

SCS engineering tasks may include items for which online change download is allowed and
items for which offline download is necessary.

IMPORTANT
• Builders allow generating parts of database where online change download is not al-
lowed.
If you make changes exceeding the range where online change is possible, you will be
notified that the downloading is impossible after performing the download operation.
If it is notified that online change download is not possible, close SCS Manager once and
use Master Database Restoring Function to revert the modified data to the same status
as the data in the SCS.
• When engineering by using iDefine, you cannot check whether you can make changes
online in iDefine. As such, make sure you confirm which items to change before changing
anything. You will not be able to perform changes online after the changes have been re-
flected in SCS Manager; if you use the Master Database Restoring Function, the iDefine
project database must also be restored to its previous state. As such, it is recommended
that you back up the iDefine project database before making changes in iDefine.
• When modifying the logic, the related output channels should be locked-out on the I/O
Lock Window.
• When performing online changes for POUs, make sure to consider the items related to
"Miscellaneous limitations" of the "Online changes" description in the "Debug" section of
the "Workbench" chapter in the Workbench User's Guide.

n Procedure for online change download

This section describes procedures from building application logic to storing SCS project after
an online change download.

l What to do before online change download

IMPORTANT
Call up the SCS Information dialog box and confirm that the number of logical I/O points in
use does not exceed the number of granted I/O licenses.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.1 Online change download> E1-3
Use the SCS security level operation function to set the SCS security level to Level 1.
After that, open the I/O Lock window and lock the input and output modules to be affected by
online change downloading.

l Start the online change download

1. From the [Debug] menu in SCS Manager, select [Online Change: Download]. Alternative-
ly, click the [Online change download] button on the toolbar.
The Online Change Download Confirmation dialog box appears.
TIP • If Integrity Analyzer or Cross Reference Analyzer has already been launched when you start online
download, a message prompting to close the analyzer is notified and the download ends with an error.
• If the SCS security level is set to Level 2 when the online change download starts, a message prompting
you to change the security level appears and the program aborts. Set the security level to Level 1 and
start an online change download.
• If the I/O Lock window or Inter-SCS Communication Lock window is left open when you start online
change download, an error message appears and the download processing stops.

2. Click [OK].
A dialog box prompting to confirm the version control appears.

l When the Scan period of the application logic is changed

If the scan period of the application logic has been changed, a confirmation dialog box ap-
pears when you start online change download. If there are any changes that take long time in
downloading, another confirmation dialog box appears.

l Check the application logic and end online change download

Using SCS Manager, change the SCS mode to Target test mode and test the changes you
made. After the test, unlock the input and output modules which were previously locked using
the I/O Lock window. And perform the output enable operation.
From the Set SCS Security Level dialog box, change the security level to Level 2. After that,
save the SCS project using the Version Control Tool.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-4

E1.2 Entire procedure of online change of

application
This section describes a procedure for online change of an application.

n Procedure for online change of an application

Before performing an online change of an application, you need to analyze possible effects
caused by the change carefully and take the appropriate measures. This section describes
procedures for online change of application for both the following cases: online change of ap-
plications with addition or change of I/O modules, and online change of applications without
addition or change of I/O modules.

l Online change of applications with addition or change of I/O modules

The following describes the procedure for online change of applications without addition or
change I/O modules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-5

Procedure for online change of

an application

(1) Check out SCS project

(A) Open Project (2) Open SCS project
(3) Validate SCS project

(1) Modify POU (*1)

(B) Create (2) Generate a database
Application
(3) Specify the test range

Run logic simulation test NO

or SCS simulation test?

YES

(C) Test the application with logic

simulation test or SCS simulation test (*1)

NO
Test results OK?

YES

(D) Online (1) Change Security Level to 1

Change (2) Lock the outputs
Download
(3) Run Online Change Download

(E) Test the application with Target

Test function (Forcing Function) (*1)

NO
Test results OK?

YES
(1) Unlock the locked outputs
(F) Completion of
Online Change (2) Confirm locked variables
(3) Change security level to 2.

(G) Self-Document (1) Print out self-document of changes

(1) Confirm diagnostic information

(H) Check in messages
Project
(2) Check in SCS project

End

*1: You can use iDefine functions when you use I/O list engineering with iDefine.

Figure E1.2-1 Procedure for online change of an application

l Online change of applications with addition or change of I/O modules

The following describes the procedure for online change of applications with addition or
change I/O modules.
Before performing the following procedure, you need to install the I/O modules in the nodes
and complete the required hardware setups such as field wiring and connection of power sup-

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-6
ply. Then, by using the following procedure, you need to make sure that all data of the added
channels are normal, and generate the application or implement the changes.
Procedure for changing
an application

(1) Check out SCS project

(A) Open Project (2) Open SCS project
(3) Validate SCS project

(1) Define I/O modules and

(*1) add channel wiring
(I) Add I/O Module
Information (2) Set I/O Parameters

(3) Generate a database

(*1) (D)’ Online (1) Change SCS Security Level to 1

Change Download (3) Online Change Download

All channel data of the added I/O NO Recovery of

(*1) modules can be read properly? abnormal data

YES

(1) Modify POU (*3)

(B) Create
Application (2) Generate a database
(3) Specify the test range

Run logic simulation test NO

or SCS simulation test?

YES
(C) Test the application with logic
simulation test or SCS simulation test (*3)

NO
Test results OK?

YES

(1) Change Security Level to 1

(D)’ Online
(*1) Change Download (2) Lock the outputs
(3) Run Online Change Download

(E) Test the application with Target

Test function (Forcing Function) (*3)

NO
Test results OK?

YES

(F) Completion of (1) Unlock the locked outputs

Online Change (2) Confirm locked variables
(3) Change security level to 2

(1) Confirm values and data status of

(J) Enable output variables
Output(*2)
(2) Perform Output Enable Operation

(G) Self-Document (1) Print out self-document of changes

(1) Confirm diagnostic information

(H) Check in messages
Project
(2) Check in SCS project

End

*1: These steps are different from the procedure for online change without adding input/output modules.
*2: This is required only when you add output channels or output modules.
*3: You can use iDefine functions when you use I/O list engineering with iDefine.

Figure E1.2-2 Procedure for online change of an application (with addition and change of I/O mod-
ules)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-7
SEE
ALSO For more information about changing hardware, refer to:
E., “Maintaining the SCS” in Hardware User's Guide (IM 32P06C10-01EN)

l (A) Opening the project

Table E1.2-1 Procedure for opening a project

Item Description
(1) Check out SCS project • Check out the existing SCS project with the Version Control Tool.
(2) Open SCS project • Start SCS Manager from AD Organizer.
• Open the SCS project.
• Enter the password for the SCS project.
(3) Validate SCS project • Run the Database Validity Check Tool and check that the CRC co-
des and generation times of the databases are consistent between
the SCS and SCS project.
• Repair a database if there is a discrepancy in the database.

SEE
ALSO For more information about precautions for handling an SCS project engineered by I/O list engineering that
was checked in with Version Control Tool of a revision earlier than R4.03.10, refer to:
“n Precautions for handling an SCS project that was checked in with Version Control Tool of a revision
earlier than R4.03.10” on page C3-2

l (B) Creating an application

Table E1.2-2 Procedure for creating an application

Items Description
(1) Modify POU If you are not using iDefine:
• Open the POU that you want to change.
• Edit POU.
• Save POU.
• Print POU.
• Confirm that the logic entered in Multi-Language Editor is the same
as the logic printed by using the self-document function.
If you are using iDefine:
• Export the ProSafe-RS I/O file from AD Organizer and import it in
iDefine.
• Change the POU, variables and tag-related definitions by using
iDefine.
• Export the iDefine-config file from iDefine and import it in AD Or-
ganizer.
• Run Reflection by using RS Generation Manager.
Confirm that the run sequence for FB and FU is correct.
(2) Generate database • Perform Build.
• Analyze and confirm that the safety applications such as FU/FB are
correct in terms of safety by using the Integrity Analyzer.
• Call up the SCS Information dialog box and confirm that the number
of logical I/O points in use does not exceed the number of granted
I/O licenses.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-8
Table E1.2-2 Procedure for creating an application (Table continued)
Items Description
(3) Specify the range of testing • Check the modified POU and the affected POU with the Cross Ref-
erence Analyzer and then authorize them.
• Use the Project Comparing Tool to confirm that the following set-
tings (for which Cross Reference Analyzer cannot confirm the exis-
tence of changes, which are critical in terms of safety, and through
which online change download is made possible) are not uninten-
tionally changed.
Item in Resource Properties window:
• [Cycle Timing]
Items in SCS Constants Builder:
• [Extend Scan Period Automatically] (*1)
• [Behavior at Abnormal Calculation] (*1)
• [Automatic IOM Download] (*1)
• [Locking of Internal Variables] (*1) (for SCSP2/SCSP3)
• [Device Power-Off Period] (*2) (For SCSP1/SCSP2/SCSP3/
SCSU1)
• [Device Startup Waiting Period] (*2) (for SCSP1/SCSP2/SCSP3/
SCSU1)
Items in I/O Parameter Builder
• [Extends Node Bus] (*1)
• [Extends To (km)] (*1)
*1: The corresponding item may not exist or the configurable value may be different depending on the software release number
of the system or SCS type. Such items may therefore be picked up as discrepancies by the Project Comparing Tool.
*2: This item can be used with SCS projects created using a version of SENG that is R4.03.00 or later.

l (C) Testing applications with logic simulation test functions and SCS
simulation test functions
Test the user application with the logic simulation test functions or SCS simulation test func-
tions.
SEE
ALSO For more information about details of logic simulation test and SCS simulation test, refer to:
C6., “Simulation tests” on page C6-1

l (D) (D’) Online change download

Table E1.2-3 Procedure for online change download

Items Description
(1) Change SCS Security Level • Start the SCS Maintenance Support Tool which monitors the SCS
from the SCS Manager.
• Set the security level to 1. Entering a password is required.
• Confirm that the SCS Security Level is 1 on the SCS State Manage-
ment window of SCS Maintenance Support Tool.
• Confirm the diagnostic information message indicating the security
level at 1 with the SCS Maintenance Support Tool.
(2) Fix the output • Locks all the channels of the output modules connected to the modi-
fied POU or to be modified POU.
• Use the SCS Maintenance Support Tool to confirm that a diagnostic
information message is output, indicating that the abovementioned
modules have been locked.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-9
Table E1.2-3 Procedure for online change download (Table continued)
Items Description
(3) Online Change Download • Perform online change download.
• Establish a communication. Confirm that no communication error oc-
curs.
• Confirm that the diagnostic information message is not issued,
which is caused by a write error to the flash memory of SCS. If it is
issued, perform Offline download.
• Use the Database Validity Tool to confirm that CRC and generation
time of four kinds of databases for SCS project databases are cor-
rect. Confirm that CRC of four kinds of databases and generation
time are correct.
• Repair a database if there is a discrepancy in the database.
• Confirm that the total number of POU notified in the diagnostic infor-
mation message about the change of resources (No.4172) is identi-
cal to the total number of POU shown in the Database Validity Tool.
• If downloaded to Output module, validate the output after the down-
load.

CAUTION
I/O Lock is a function to prevent unnecessary shutdowns in the following conditions:
• System malfunction caused by unintended errors in application programs
• Temporary halt of the I/O module when the I/O module settings are changed
If you lock the output, you can conduct target tests to check the behavior of a modified logic.
However, if you are sure in advance that the above mentioned system malfunction or tempo-
rary halt does not occur, or that even if it occurs it will cause no problem, there is no need to
lock I/O.
The explanations in Instruction Manuals (IM) for ProSafe-RS rest on the premise that you use
the I/O Lock function.

SEE
ALSO For more information about repairing a database, refer to:
“■ Repair database” in F3., “Database Validity Check Tool” in Engineer's Reference Manual (IM
32P04B10-01EN)
For more information about precautions for online change, refer to:
E1.5, “Precautions for online change” on page E1-20

l (E) Target test functions

Perform the output enable operation and test the user application on the target SCS.
SEE
ALSO For more information about details of target test, refer to:
C9., “Target tests” on page C9-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-10

l (F) Completion of online change

Table E1.2-4 Procedure for completion of online change

Items Description
(1) Unlock the locked outputs • Confirm that, for the digital output modules concerned, the values
and statuses of logical data agree with those of physical data.
• Unlock the output modules concerned.
• Confirm that the diagnostic information message which indicates
the output modules concerned have been unlocked is output with
the SCS Maintenance Support Tool.
• Disable the bypass to the actuator.
(2) Confirm locked variables • Confirm the number of locked variables is 0 with the SCS Mainte-
nance Support Tool.
• Confirm that no diagnostic information message is issued except for
one you confirmed, with the SCS Maintenance Support Tool.
(3) Change the security level to 2 • Set the security level to 2.
• Confirm that the security level is 2 in the SCS State Management
window of the SCS Maintenance Support Tool.
• Confirm the diagnostic information message which indicates that
the security level went back to 2 with the SCS Maintenance Support
Tool.

l (G) Self-document

Table E1.2-5 Procedure for Self-document

Items Description
(1) Print out modified parts of the • In preparation for the desk check performed at application software
project using self-document changes in the future, print out the latest SCS project database as
self-documents.

l (H) Check in project

Table E1.2-6 Procedure for checking in a project

Items Description
(1) Confirm the diagnostic informa- • Confirm that diagnostic information message other than one you
tion message confirmed is not issued with the SCS Maintenance Support Tool.
(2) Check in the SCS project • Close the SCS Manager.
• Check in the SCS project.

l (I) Adding I/O module information

Table E1.2-7 Procedure for adding I/O module information

Items Description
(1) Define I/O modules and add For I/O list engineering
channel assignment • Obtain the latest safety I/O list and import it by using Safety I/O Edi-
tor. Alternatively, obtain the latest safety communication I/O list and
import it by using Safety Communication I/O Editor.
• Use Safety I/O Editor, Safety Communication I/O Editor, and IOM
Definition Editor to define I/O modules and I/O parameters.
• If this affects the applications created by using iDefine, export the
ProSafe-RS I/O file from AD Organizer and import it in iDefine to re-
pair the iDefine application.
For RS original engineering
• Define I/O variables with the Dictionary.
• Add I/O module definitions and define parameters.
• Connect I/O variables to channels.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.2 Entire procedure of online change of application> E1-11
Table E1.2-7 Procedure for adding I/O module information (Table continued)
Items Description
(2) Specification of I/O parameter For RS original engineering
• Define all parameters of nodes, units, modules, and channels.
(3) Generate a database • For I/O list engineering
After changing the application by using iDefine, export the iDefine-
config file from iDefine and import it to AD Organizer.
Start the Generation Manager from AD Organizer and execute re-
flection or RS generation process.
• For RS original engineering
Perform Build.
• Analyze and confirm that the safety applications such as FU/FB are
correct in terms of safety by using the Integrity Analyzer.
• Use the SCS Information dialog to confirm that I/O license is availa-
ble.

l (J) Enabling output

Table E1.2-8 Procedure for enabling output

Items Description
(1) Confirm values and data status • Confirm which output channels are disabled on the SCS State Man-
of output variables agement window of SCS Maintenance Support Tool.
• Start the I/O Lock Window.(This can be performed at security level
2.)
• Confirm that values and statuses of logical data and physical data
for output variables are correct.
(2) Operate “Enable Output” • Perform the Output Enable Operation for output modules on the
SCS State Management window of SCS Maintenance Support Tool.
• Confirm that the diagnostic information message on the Output En-
able Operation for output modules is displayed.
• Confirm that Output Channels are enabled on the SCS State Man-
agement window.
• Confirm that the SCS operating mode is "Running" on the SCS
State Management window.

SEE
ALSO For more information about details of the enable output operation, refer to:
“n Enable Output operation” on page C8-2

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-12

E1.3 List of applicable items for online change

This section describes the items for which you can perform online change download and
those which require offline download. If stopping SCS control is not allowed, setting items that
require offline download must not be changed.

IMPORTANT
If you change setting items that require offline download, even if you reverse the change, on-
line change download is not allowed. If this happens, use Master Database Restoring tool to
recover the database to a state where online change download is allowed. When engineering
by using iDefine, you must restore the iDefine project database as well.

SEE
ALSO For more information about online change availability for SCS operating on a SCS system program revision
of R2.02 or earlier, refer to:
“n Possibilities of online change download” on page App.3-5
For more information about operations of the Master Database Restoring function, refer to:
F4., “Master Database Restoring Function” in Engineer's Reference Manual (IM 32P04B10-01EN)

n Online change of POU information

There are changes that enables you to execute online change download or offline download
according to each POU type.

l Changing POU
The following table shows whether POU can be changed online: for operations on POU, on-
line change download can be used for changes of Program name only. If you try to perform
online download change on the item that No is described in the table, an error is notified at
the time of online change download.

Table E1.3-1 Whether or not online change can be used for POU operations
Type of POU Changing a name Creating, deleting
Program Yes No
User-defined FU No No
User-defined FB No No

Since a new program can not be created online, we recommend that you create dummy pro-
grams in advance and change the name of the program online as you need.

l Changing POU logic

When you perform a change operation on POU described in the following table, you can per-
form an online change download to SCS.

Table E1.3-2 Logic change operations that can be changed online on POU
Corrected item Description
Adding/deleting the standard FU call -
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-13
Table E1.3-2 Logic change operations that can be changed online on POU (Table continued)
Corrected item Description
Adding/deleting the user-defined FU call Including FU defined in the library. A project that is
created with the revision earlier than R3.02.00 will be
in the same condition as R3.02.00 when clean proj-
ect is executed. Therefore, you can perform an on-
line change download.
Changing logic -

l Changing a library
When a library is added to or deleted from SCS project, offline download is needed. A warn-
ing is displayed at the build operation, and an error occurs at online change download opera-
tions.
A project that is created with the revision earlier than R3.02.00 will be in the same condition
as R3.02.00 when clean project is executed. Therefore, you cannot perform online change
download when the library is added or deleted.

l Changing program
The following table shows the operations that can perform online change download to SCS
for global variables, global instances, local variables, and local instances that are used in Pro-
gram.

Table E1.3-3 Operations that can be changed online for variables and instances used in program
Corrected item Description
Adding/deleting a variable -
Deleting variables and adding variables with the -
same names as the deleted variables
Changing the types of variables -
Changing attributes of variables -
Adding/deleting I/O variables -
Adding/deleting the standard FB instances -
Adding/deleting the user-defined FB instances Including FB defined in the library. A project that is
created with the revision earlier than R3.02.00 will be
Deleting FB instances and adding FB instances with in the same condition as R3.02.00 when clean proj-
the same names as the deleted ones ect is executed. Therefore, you can perform online
Changing the types of FB instances change download.

l Changing user-defined FB
The following table shows the corrections that need offline download to SCS for the parame-
ters of user-defined FB. A warning is displayed at the build operation when performing the
correction in the table. An error occurs at online change download operations.

Table E1.3-4 Operation of parameters that need offline download in user-defined FB

Modification Description
Adding/deleting a parameter -
Deleting parameters and adding parameters with the -
same names as the deleted parameters
Changing the types of parameter -
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-14
Table E1.3-4 Operation of parameters that need offline download in user-defined FB (Table continued)
Modification Description
Changing the attributes of parameter As the attributes of user-defined FB parameters, the
following items cannot be changed online. Direction,
() (specification of the number of characters for
STRING variables: [Not supported]), Dimension
Adding/deleting the standard FB instances If you add FB instances without names (not appear-
ing in the Dictionary) in user-defined FB, the FB in-
stances become parameters and thus cannot be
changed online.
Adding/deleting the user-defined FB instances -
Deleting FB instances and adding FB instances with
the same names as the deleted ones
Changing the types of FB instances

The following table shows the corrections that you can execute online change download to
SCS for the global variables and the global instances used in user-defined FBs.
TIP Normally, global variables and global instances are not used in user-defined FBs.

Table E1.3-5 Operations that can be changed online for global variables and global instances used in
user-defined FB
Modification Description
Adding/deleting a variable -
Deleting variables and adding variables with the -
same names as the deleted variables
Changing the types of variables -
Changing the attributes of variables -
Adding/deleting the standard FB instances -
Adding/deleting the user-defined FB instances Including FB defined in the library. A project that is
created with the revision earlier than R3.02.00 will be
in the same condition as R3.02.00 when clean proj-
ect is executed. Therefore, you can perform online
change download. When adding user-defined
FU/FB, the added user-defined FU/FB must be tes-
ted. When adding pre-validated user-defined FB,
testing of the FB itself is not required.
Deleting FB instances and adding FB instances with Including FB defined in the library. A project that is
the same names as the deleted ones created with the revision earlier than R3.02.00 is in
the same state as R3.02.00 when clean project is
Changing the types of FB instances executed. Therefore, it can perform online change
download.

l Changing user-defined FU
The corrections that you can execute online change download for parameters or local varia-
bles in user-defined FU are as follows:
• Adding/deleting
• Deleting variables and adding variables with the same names as the deleted variables
• Changing the types of variables
However, when the type of output parameter is changed, offline download is required.
• Changing attributes of local variables

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-15
SEE
ALSO For more information about the precautions that should be taken when deleting a variable or function block
and then adding it again, refer to:
"Declared Variables" in "Variables" in "Online Change" in "Debug" in "Workbench" of "Workbench User's
Guide"

n I/O module information that is changeable online

The following table shows whether each item of I/O module related information can be
changed by online change downloading.

Table E1.3-6 I/O module

Modification Online change (*1)
Adding nodes Yes
Deleting nodes Yes
Changing parameters of nodes Yes
Adding a unit Yes
Deleting a unit Yes
Adding I/O modules Yes
Deleting I/O modules Yes
Changing redundant I/O modules Yes
Changing parameters of I/O modules Yes
Change in the mounting position (node, unit, and slot) of N-IO I/O module Yes
Change in the signal category of N-IO I/O modules. Yes
Changing parameters of channels Yes
Change in parameters of serial communication modules or Ethernet communication
Yes
modules
Defining wiring between a variable and an idle channel Yes
Deleting wiring between a channel and a variable Yes
Changing wiring between a channel and a variable Yes
Addition, change or deletion of subsystem communication definitions Yes
Changing wiring of communication input/output FBs Yes
Addition or deletion of ESB bus coupler modules Yes
Add, change or delete a fire and gas communication definition Yes
Changing a fire and gas communication FB wiring Yes
*1: Yes: Online change download is possible.

SEE
ALSO For more information about changing hardware, refer to:
• E4., “Replacing FIO node components” in Hardware User's Guide (IM 32P06C10-01EN)
• E5., “Replacing N-IO node components” in Hardware User's Guide (IM 32P06C10-01EN)

n Constants and network information that are changeable with online

The following table shows whether the setting can be changed by online change downloading
in the constant and network related items.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-16
Table E1.3-7 Constant and network
Classification Modification Online Change (*1)
Configuration Name No
Password No (*2)
Resource Name No
Resource Number No
Cycle Timing Yes
Memory size for online changes No
Memory size for temporary variable No
Network IP address No
Station address No
Inter-SCS safety Communication No
(Binding)
*1: Yes: Online change download is possible.
No: Offline download is required.
*2: Setting and changing passwords is ignored.

n Builder definitions that are changeable with online

The following table shows whether online change download is possible after definition infor-
mation has been changed using builders.

Table E1.3-8 Builder definitions that are changeable with online

Item Online Change (*1)
SCS Constants Builder Yes (*2)
I/O Parameter Builder Yes
Communication I/O Builder Yes
SCS Link Transmission Builder Yes
Modbus Address Builder Yes
DNP3 Communication Builder (*3) Yes (*4)
Tag Name Builder Yes
Alarm Priority Builder No
Alarm Processing Table Builder No
*1: Yes: Online change download is possible.
No: Offline download is required.
*2: Some items can be changed online. "Table of SCS Constants Builder online change" shows which items can or cannot be
changed online.
*3: Usable only for SCSU1
*4: Some items can be changed online. "Table of DNP3 Communication Builder online change" shows which items can or cannot
be changed online.

Table E1.3-9 SCS Constants Builder online change

Item Online Change (*1)
Interval of Repeated Warning Alarms No
Synchronous Mode No
Scan Period for External System No
Modbus Word Order No
16-bit Modbus master support mode No
Alarm Notify Action when AOF Released No
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.3 List of applicable items for online change> E1-17
Table E1.3-9 SCS Constants Builder online change (Table continued)
Item Online Change (*1)
PV Status of S_ANLG_S No
The first number of annunciator messages with tag name No
DNP3 Slave Function (*2) No
Optical ESB Bus Repeater No
Maximum Extension Distance No
Extend Scan Period Automatically Yes
Behavior at Abnormal Calculation Yes
Locking of Internal Variables (*3) Yes
Automatic IOM Download Yes
Device Power-Off Period (*4) Yes
Device Startup Waiting Period (*4) Yes
Alarm Suppression During Device Reset (*5) No
Command Line No
*1: Yes: Online change download is possible.
No: Offline download is required.
*2: Displayed only for SCSU1
*3: Only for SCSP2/SCSP3
*4: Displayed for SCSP1/SCSP2/SCSP3/SCSU1
*5: Displayed for SCSP1/SCSP2/SCSP3

Table E1.3-10 DNP3 Communication Builder online change

Items Online Change (*1)
DNP3 slave station address Yes
DNP3 master station address Yes
Timeout value for Select Before Operate (sec) Yes
Binary Input event buffer size No
Binary Output event buffer size No
Binary Counter event buffer size No
Frozen Counter event buffer size No
Analog Input event buffer size No
Analog Output event buffer size No
Event to be removed when event buffer overflows Yes
Generate an event when Freeze and Clear command changes data values Yes
Include Frozen Counters in Class 0 response Yes
Type of response message fragmentation Yes
*1: Yes: Online change download is possible.
No: Offline download is required.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.4 Online change of scan period of the application logic execution function > E1-18

E1.4 Online change of scan period of the

application logic execution function
The scan period of the application logic execution function can be changed online in the case
of SCS with SCS system program R2.03 or later.

n Overview of scan period online change

Change the scan period of the application logic execution function with SCS Manager and ex-
ecute online change download under security level 1 or lower. The SCS will then operate with
the specified scan period after download completes. If automatic extension of scan period has
been enabled on the SCS, the automatic scan period extension status is cancelled after the
completion of online change download and the SCS resumes operation with the scan period
specified with the online change.

n Limitations on online change

The allowable range of change is the same as the allowable range of specification, i.e., from
50 ms to 1000 ms in increments of 10 ms. Note that in online change, it is not allowed to set a
scan period longer than the scan period before change by more than 250 ms. If such changes
are made, an error occurs at online change download.
Example:
It is possible to change the scan period from 250 ms to 500 ms. Change from 250 ms
to 550 ms is not allowed because it represents an increase of 300 ms.
When changing to a shorter scan period, a dialog box appears, showing the expected CPU
idle time after the scan period is changed. You cannot download if the expected CPU idle time
is 0 second.
TIP On the SCS Simulator, the expected CPU idle time is not estimated. Only a dialog box is displayed, informing
that the scan period has been changed.

n Occurrence of IOM download at online change download

If the scan period defined before or after execution of online change is longer than 250 ms,
IOM download processing is executed for all AIO/DIO modules used in the given SCS to noti-
fy the change of fallback time. In this case, a confirmation dialog box appears at the start of
online change download.
• There is no influence on control operation during online change download because the
control of AIO/DIO modules continues.
• Online change download on SENG is completed after the completion of IOM download to
all AIO/DIO modules. IOM download takes approximately 5 seconds per module.
If an online change download that changes the scan period is executed, IOM download is
executed for all N-IO modules used in the SCS.
• While IOM continuous download is in progress for N-IO modules, control of the N-IO
modules continue. Safety loops will not be affected by the execution of IOM downloads.
• After the IOM downloads for all N-IO modules are completed, the online change down-
load is regarded as completed on the SENG. The IOM download for N-IO modules takes
about two seconds per module.
SEE
ALSO For more information about the results of analysis by Cross Reference Analyzer when the scan period is
changed, refer to:
“l Changing Scan period” on page C5-38

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.4 Online change of scan period of the application logic execution function > E1-19

n Notification of scan period online change

When online change download performed at scan period change is completed, the diagnostic
information message of scan period online change (No. 4152) is notified, in addition to the di-
agnostic information message of online change download completion.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-20

E1.5 Precautions for online change

This section describes precautions for online change of an application.

n Cross Reference Analyzer

• User should confirm locations required for a retest by checking the output of Cross Refer-
ence Analyzer.
• For interference -free applications, it is also required to analyze and test parts that are po-
tentially affected by application modifications as with safety applications.

n Online change download

• When Online Change Download is executed on I/O modules, confirm that download is
executed on the correct I/O modules by checking the diagnostic information message
from SCS.
• In CENTUM Integration engineering, even if the correspondence of an instance name
and tag name is changed, the modified location may not be displayed in the Cross Refer-
ence Analyzer nor in the diagnostic information message. Users must conduct tests very
carefully.
• After performing an online change, confirm that the CPU idle time of SCS is sufficient and
the scan timing is appropriate.
• When the CPU module is in a dual-redundant configuration, avoid performing online
change download during APC (All Program Copy) whenever possible. If online change is
executed during APC, the APC is interrupted and starts over again after the online
change is finished, which requires longer time to complete APC. This prolongs the dura-
tion of operation with a single CPU. This behavior has no impact on safety. The status of
APC operation can be confirmed with LED on CPU, SCS State Management window of
SENG or Status Display View of HIS. The start and end of APC are notified by diagnostic
information messages.
• The maximum number of tag names that can be assigned for monitoring to the annuncia-
tors (ANN/ANN_FUP) and function blocks (such as ANLG_S and PASSWD) that allow
the assignment of mapping blocks are as follows:
• Up to 2600 tag names can be assigned when using SCSP1/SCSV1
• When SCSP2/SCSP3 is used, maximum 4500 tag names can be assigned.
The maximum number of online changes that can be made to these tag names and pa-
rameters of the mapping blocks and elements at one time is 200. However, online change
download may not succeed even if the above condition is met. In this case, the following
error message appears in the message display area of SCS Manager.
Too much modified data. Make fewer changes, then load.

The limit on the number of function blocks when using SCSP1/SCSV1 is as follows:
(Number of mapping blocks) + (number of annunciator blocks with tag names) + (total
number of mapping blocks/elements changed online at one time) ≤ 2800
When using SCSP2/SCSP3, the minimum number is as follows:
(Number of mapping blocks) + (number of annunciator blocks with tag names) + (total
number of mapping blocks/elements changed online at one time) ≤ 4700
If this condition is not met, an error occurs in the check performed before online change
and the following error code is displayed in the message display area of the SCS Manag-
er.
Error Code:0x9443:0x8ec9

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-21
or
Error Code:0x9448:0x8ec9

Note that tag names are not mandatory for annunciators. It is recommended to set tag
names only for those that are referenced by tag names.
• If online change download is executed while the Communication I/O Lock Window is
open, close the Communication I/O Lock Window after the completion of the online
change download. Then, open the Communication I/O Lock Window again. A database
mismatch error may occur if the Communication I/O Lock Window is not closed.
• If you change the range of an input channel that is defined in I/O parameters and execute
an online change download, the input value on that channel changes during the down-
load and IOP may occur.
• While an Output Value at Fault is being output, if you change any I/O parameter related to
the Output Value at Fault and execute an online change download, the output value on
the channel to which the change was made may change during the download.

n SCS actions after changing the types of FB instances

The SCS actions during online change download after the types of FB instances or variables
are changed are as follows:
• When integrated with CENTUM
SCS data keeps the values before online change download. When reading with the Tag
Name interface from CENTUM station, the read values are the values before executing
online change download. Values cannot be written from CENTUM station.
• Modbus Slave Communication
Loading/writing values from the Modbus master causes an error. The error code is 13
(hexadecimal).
SEE
ALSO For more information about the error code in Modbus slave communication, refer to:
“● Response message under abnormal conditions” in “■ Response message from SCS” in F1.7, “Mes-
sages communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

n Precautions for changing instance name in online change

If you add/change/delete Instance name(s) to/in/from a function block used in POU and on-
line change download, it affects the behavior of the changed function block.(*1) Do not make
unnecessary changes to Instance name(s). Adding of Instance name(s) to a function block is
required only if External communication function is used.
*1: Each function block is affected differently by online change. Adding/changing/deleting Instance name(s) involves deleting the
existing Instance name(s) together with its previous input/output value and internal status, which affects the behavior of FB.
Function Blocks that require measures against instance name changes are as follows:

Table E1.5-1 Impact of instance name change(s)

Function Block Impact How to Recover/Avoid
OVR_B, OVR_I, OVR_R, OVR_IB, If Override is on, it turns off. Override is repeated from HIS.
OVR_IR,
GOV_B, GOV_IB
PASSWD If activated, it gets deactivated. Activate it again from HIS.
PROD_B, PROD_I, PROD_R An Inter-SCS communication error Before online change download,
and recovers later. lock the output of Consume side.
MOB_11, MOB_21, MOA If Data Manual Operation is ena- Before online change download,
bled, output gets FALSE or “0.” lock the variable of OUT connec-
ted to MOB_* or MOA.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-22

n Precautions for reusing instances

If you delete an instance of an FB or instance of a variable from a Program and perform on-
line change downloading without deleting it (instance of FB or variable) from the Dictionary
and then add it again to the Program, the data in the instance are those before the deletion. If
you need to initialize the instance data, restart the SCS.

n Precautions related to initial values of variables

Initial values of variables and FB instance parameters are used when fixing values without re-
writing them via logic and specifying values before execution of the first scan after starting
SCS.
If Type, Dimension, Scope, and Direction, among types and attributes of variables, are
changed online, the values are initialized to the initial values specified by Init.Value of the Dic-
tionary. Changes to values are not reflected if only Init.Value of the Dictionary is changed and
online change is executed in order to change the initial values.
If you wish to change only the initial values of variables or FB instance parameters via online
changes, change the variable names or delete the variables or FB instances once, perform
online change download and then perform online change download to add them again.

n Writing to flash memory of SCS

• If an error occurs during writing operation to a flash memory, offline download is required.
• If writing operation to the flash memory is interrupted by pulling out the CPU module or
cutting off the power, hardware of the flash memory may fail. Before removing the CPU
module or cutting off power, confirm that the LED on the CPU module indicating the flash
memory writing status, is lit up (not writing).

n Online change of scan period

• You can change the scan period of the application logic execution function by using the
online change download. When you shorten the scan period, a confirmation dialog box
displays the estimated CPU idle time of the SCS after changing the scan period during
performing online change download. For the estimated idle time that is displayed, only
the change in scan period is considered and the impact due to application change is not
considered.
• Do not change both the scan period of the application logic execution function and appli-
cations (e.g., addition of logics and I/O modules) at the same time in a single online
change download operation. First, change the scan period and perform online change
download, check the CPU load of SCS and then change applications.

n Reception Interval Timeout Value (OUTT) for Inter-SCS safety

communication
In principle, if you set a longer scan period, the transmission interval of inter-SCS safety com-
munication becomes longer. When you change the scan period by online change download,
you need to re-adjust the reception interval timeout values (OUTT) of the SCSs that communi-
cate, by inter-SCS safety communication with the SCS for which the scan period is changed.
(This includes the case where the SCS for which the scan period is changed receives data by
inter-SCS communication.)
SEE
ALSO For more information about precautions when setting OUTT, refer to:
“● Inter-SCS safety communication timeout settings” in “■ Precaution for engineering” in A7., “Inter-SCS
safety communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-23

n Reception Interval Timeout Value (OUTT) for SCS link transmission

safety communication
If you set a longer scan period, the transmission interval of SCS link transmission safety com-
munication becomes longer. Therefore, you also need to re-adjust the OUTT for SCS link
transmission safety communication, as should be done for inter-SCS safety communication.
SEE
ALSO For more information about precautions when setting OUTT, refer to:
“● Time out settings of SCS link transmission safety communication” in “■ Precaution for engineering” in
A6.2, “Data structure and definition of the SCS link transmission” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)

n Online change of single/dual-redundant specification of AIO/DIO

modules
You need to perform the following procedure to change two adjacent AIO/DIO modules in sin-
gle configuration implemented in FIO node into dual-redundant configuration by using online
change download.
1. Disconnect the I/O cables (or terminal blocks) of the modules.
2. If you change two adjacent existing single modules into dual-redundant configuration, pull
out one of the modules and then insert it again.
3. Change the definition of dual redundancy specification, and perform online change down-
load.
4. Connect the I/O cables (or terminal blocks).
Immediately after the online change download, the AIO/DIO modules go into the status de-
scribed in the following warning; however, the state is restored when I/O cables (or terminal
blocks) are connected.

CAUTION
• Input module
An IOM fail occurs and the “input values at error occurrence” specified as the I/O parame-
ters are set to all input channels. The data status changes to BAD.
• Output module
An IOM fail occurs and the “output value at fault” specified as the I/O parameters are set
to the physical data of all output channels. The module goes to an output disable status.

n Online change of I/O module device index

In order to change the device index of an I/O module, you must delete the I/O module and
define it again. At the point I/O modules are deleted, the lock status of each channel of the
modules is also canceled.
If you change a device index for a module of the same model installed in the same position by
online change download, in the case of input modules, 0s (0 for DI and 0.0 for AI) are input to
the application logic at first and then the values from the field are input. In the case of output
modules, the channels' outputs are disabled. FALSE for DO and tight-shut value for AO are
output. After performing “output enabled operation”, the modules start to output the values of
application logic.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-24

n Online change of the device index and element numbers for a fire
and gas communication module
If you change the device index of a fire and gas communication module (model: S2LP131)
and execute online change download, the S2LP131 restarts. The target S2LP131 will be un-
locked upon executing the online change download even if you lock the S2LP131 before exe-
cuting the online change download. Take appropriate measures against restarting of the com-
munication module, such as to lock the outputs of the application logic that is using the data
obtained through the target S2LP131.
When you change the element number of a %XW element, lock the outputs of the application
logic that is using the FB wired to the element for which the element number will be changed.
This is because if you change the element number of a %XW, an unknown value will be input
to the FB that is wired to that element.

n Online change of channel wirings

This section explains the system behavior when channel assignment is added, deleted, or
changed and then online change download is executed. Note that the following cases are al-
so included, in addition to simply adding, deleting, or changing channel assignments.
• When AIO/DIO module definitions are added, channel assignments are also performed at
the same time
• When AIO/DIO module definitions are deleted, channel assignments are deleted
• When AIO/DIO module models are changed (when AIO/DIO module definitions are de-
leted once, then new AIO/DIO module definitions are added, and channel assignments
are also performed at the same time)

IMPORTANT
• If you change the channel assignment and download the change, IOM downloading will
not start automatically. However, if the I/O parameters are also changed, IOM download-
ing may automatically start depending on which parameters have been changed.
• When using S2MMM843 or S2MDV843 in an explosion protection system, refer to Explo-
sion Protection (For ProSafe-RS) (TI 32S01J30-01E) without fail. The approved values of
the explosion protection parameters are different depending on the type of signal.

l Online change of input channels

After online changing the input channel assignments, the logical data values of the assigned
input variables will be set with the initial value of 0 (DI:FALSE; AI:0.0).Then, the values from
the I/O modules will be used.

IMPORTANT
If you add the input channel assignment and the application accessing the input variable, and
then the two are online change downloaded at once to SCS, 0 is set to the input variable for
an instant before the actual values.

In this case, do the online change according to the procedure below:

1. Run online change downloading right after adding input channels.
2. Lock input variables.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-25
3. Run online change downloading right after changing applications.
When the variable names of the previously assigned input variables are changed and online
change downloaded, the input variables will immediately take the values from the I/O mod-
ules.

l Online change of output channels

When the output channel assignments are added online, the added channels will not be able
to output the logic values. The logic values can be output only after performing the “Output
enable operation.”
When the output channel assignments are changed, after online change downloading, the
output values may be different from the previous values.
In this case, do the online change downloading according to the procedure below:
1. Lock the output variables.
2. Run online change downloading.
When the variable names of the previously assigned output variables are changed and online
change downloaded, the output channels will continuous to output the values through I/O
modules.

l Lock status at online changing of channels

When a locked channel is deleted from the assignment, the lock status of that channel will be
released and deleted from the total number of locked channels of the whole station. Once a
locked channel is deleted from the assignment and online change downloaded, the lock sta-
tus of the channel will not be kept even when the channel is added to the assignment and
online downloaded again.

l Channel status at online changing

If the definition of assigned channels is deleted in online change to make them unassigned,
the changed channels behave same as the other channels that are unassigned. As the result,
channel status outputs for the system function block (such as CHn of SYS_OUTST or Q of
SYS_CHST) become FALSE. Also the changed channels are excluded from representative
alarm for the system function block (such as NRAL of SYS_OUTST, NRO of SYS_IOALLST,
IOER of SYS_DIAG) and are not considered for diagnostic information marks on the SCS
State Management window.

l System alarm messages at online changing

When a channel that is causing an error is deleted from the assignment and online change
downloaded, the recovery message for the channel will not be raised.

l Operating mode at online changing

When an output disabled channel is deleted from the assignment and then online change
downloaded, and the operating mode of the station may become Running due to the station
does not have any output disabled channel. When an output channel is added to a station
that in Running mode, and then online change downloaded the assignment, the status of the
station may become Waiting due to the added channel is started in the output disabled status.

n Online change of SCS link transmission

• Sequence of Adding and Deleting
When adding a new data, it should be added first on the sender station. When deleting a
data, it should be deleted from the receiver station. Doing this way is to avoid the applica-
tion to access the deleted data.
• Lock the Link Transmission Data

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-26
The link transmission data can only be locked together for the whole station. Locking one
link transmission data, all the link transmission data in the station will be locked.
Thus, when performing online change (adding or deleting) for link transmission data, the
influence of the change to the logics should be properly checked, and then lock the prop-
er variables at the proper places (such as link transmission data of sender station, link
transmission data of receiver station or other individual internal variables).

IMPORTANT
For applications that require individual lock, connect the internal variable to lock them as fol-
lows:
• On Sender Station: Connect an internal variable to the input parameter of the link trans-
mission output FB, and then lock it.
Sender SCS Link Transmission
Data Output FB
Lock Operation
LTSND

Logic Internal Variable V

Figure E1.5-1 Lock on sender station

• On Receiver Station: Connect an internal variable to the output parameter of the link
transmission input FB, and then lock it.
Receiver SCS
Link Transmission
Data Input FB Lock Operation
LTRCV

V Internal Variable Logic

STS

Figure E1.5-2 Lock on receiver station

• Add a logic that uses a link transmission data input FB

IMPORTANT
Do not add a link transmission data input FB and the logics connected to the FB at the same
time during the online change. The influence to other logics may occur even if the link trans-
mission received data are properly locked.

In this case, do the online change according to the procedure below:

1. Create a link transmission data input FB.
2. Online Change Download
3. Add a logic connecting to the link transmission data input FB.
• Change the Link Transmission Data Input FB Instance Name
When a link transmission data input FB instance name is online changed, note that the
output of the FB may become different.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-27
When changing the instance name online is necessary, do it according to the procedure
below:
1. Lock the internal variable that connected to the link transmission data input FB.
2. Online Change Download
If you cannot find a proper internal variable to lock, you need to add an internal variable
to the output parameter of the link transmission data input FB, and then lock the variable.
Then you can online change the instance name.
• Delete Link Transmission Data Output FB
When a Link Transmission Data Output FB is deleted, the output data will be reset to 0.
Even if the local station is locked to avoid bad influence, the receiver side is still affected
since the linked data is reset to 0. Therefore, the FB in the receiver side should be de-
leted first.
• When Sending Definition of the SCS Link Transmission is Disabled
When sending definition of the SCS link transmission is disabled during online change,
data sending to other stations will stop. If another station is receiving data from the stop-
ped station, the actions are shown as follows.

Table E1.5-2 Actions of Receiver Station

Receiver Station Description
Since the updating of the safety information (such as sequence numbers or transmis-
SCS sion timestamps) sent through the link transmission are stopped, an error will be indi-
cated. The statuses of related input data will become BAD.
The last received data will be kept. The statuses of the related data will not become
FCS
BAD.

Moreover, when the transmission size of the sender FCS is online changed to 0, the re-
ceiver station on SCS side will keep the last received data values. The data statuses will
not become BAD.

n Locking Inter-SCS safety communication and SCS link transmission

data at online change
False trips caused by online changes can be prevented by locking inter-SCS safety communi-
cation data or link transmission data on the station where online change is performed. It is not
necessary to lock data on the stations that receive data from the station where online change
is performed.
The following figure illustrates an overview and the procedure for performing online changes.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-28

• Data • Data OUT

IN PD • Safety OUT IN • Safety LD
Lock NR
LD information information
PD
Producer FB Consumer FB

Write input only to Set values held in

LD (logical data) PD (physical data)
in binding variables

OUT • Data • Data

LD IN OUT PD IN
NR • Safety • Safety
Lock
information information LD
PD
Consumer FB Producer FB

Output values held in Write input only to PD

LD to OUT and NR

SCS1: Station where online change download is performed SCS2

Figure E1.5-3 Example of locking Inter-SCS safety communication at online change

Follow these steps to perform online changes:

1. Set the security level of the SCS for which online change is to be performed to 1.
Check that the SCS’s security level has changed to 1 with diagnostic information messag-
es.
2. Open the Inter-SCS Communication Lock Window or SCS Link Transmission Window of
the SCS for which online change is to be performed and lock the sending and receiving
data.
Check that inter-SCS safety communication or link transmission safety communication
has been locked with diagnostic information messages.
3. Execute online change download.
4. Check that the logical data and physical data match and that the data status is GOOD in
the Inter-SCS Communication Lock window or SCS Link Transmission Lock window.
5. Unlock the sending and receiving data in the SCS in the Inter-SCS Communication Lock
window or SCS Link Transmission Lock window.
Check that the inter-SCS safety communication is unlocked with diagnostic information
messages.
6. Set the security level of the SCS for which online change has been performed to 2.
Check that the SCS’s security level has changed to 2 with diagnostic information messag-
es.

n Online change download of input/output modules

In the online change download, you can perform changes in the redundant configuration, ad-
dition and deletion of I/O modules. If I/O modules are added through online change download,
diagnostic information messages are issued to notify failure of I/O modules (No. 0081) and
normal recovery of I/O modules (No. 0082).

n Online change download of AIO/DIO module settings

When you perform online change download after you have made changes to the settings rela-
ted to I/O parameter of AIO/DIO modules, IOM download may also take place depending on

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.5 Precautions for online change> E1-29
the setting items you have changed. The AIO/DIO module continues its I/O operations when
IOM download also takes place along with the online change download. The behavior of the
SCS is as follows:
• The target modules continue their input/output operations.
• For AIO/DIO modules in redundant configuration, control rights are retained.
• The diagnostic information message of IOM Fail is not output.

n Precautions related to fire and gas communication modules when

downloading an online change onto SCS
Before online change downloading onto SCS, a dialog box asking the lock of S2LP131 may
appear. In such case, before online change downloading onto the SCS, lock the S2LP131
shown in the dialog box. Lock by locking all inputs or by locking all communication definitions.
When not locking all inputs or all communication definitions, the following phenomenon will
occur:
• The status of the LD (logical data) of Safety and Non-Safety data obtained via S2LP131
changes to Error.
• The locks of communication definitions partially locked may be released.
As these issues will lead to an unnecessary shutdown of the plant, lock S2LP131 before on-
line change downloading.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-30

E1.6 Precautions for online change download

of N-IO
This section describes the I/O operation and extent of impact when online change is per-
formed for definitions related to N-IO. Other than the online change of definitions in regard to
N-IO, precautions are the same as those for online change download of FIO.

SEE
ALSO For more information about precautions for online change download of FIO, refer to:
E1.5, “Precautions for online change” on page E1-20

n Changing N-ESB bus coupler modules

When you add/delete N-ESB bus coupler module to/from the CPU node, the I/O operations at
the I/O modules, other than the N-IO nodes at the connection destination, remain unaffected.

n Changing N-IO nodes

When you add or delete an N-IO node, the I/O operations at the I/O modules, other than the
related nodes, remain unaffected.
Even when you perform online change for the setting values of N-IO nodes, I/O of the related
nodes remain unaffected.

n Changing I/O modules of N-IO nodes

The configuration information of an I/O module is downloaded in either of the following ways:
• IOM continuous download: A download wherein the I/O operations at the points other
than the changed points continue.
• IOM initialization download: A download wherein the I/O operations of all points of
changed I/O modules stop.
In the online change with IOM download, IOM continuous download is executed. During the
IOM continuous download, the I/O operations continue.
When you add an I/O module, IOM initialization download is executed. After the IOM initial
download, the operation at the IOM startup is executed.
When you add or delete an I/O module, only the I/O operations of the related I/O module are
affected.
The deleted I/O module will be in the fall-back state due to being separated from the CPU.
This is the same as when the I/O module of the FIO node is deleted.

n Changing the channels of the I/O module of the N-IO node

When changing the signal type of the channels of the universal type I/O module, you need to
reassign I/O variables that are appropriate for the type of signal to which the change is being
made.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-31
When the channel being deleted (subject to deletion of variable assignment) is locked, the
locked status will be released after the channel is deleted.
Changing the channel assignment is the same as with the I/O module of the FIO node with
the exception of the status of the deleted channel.
TIP The deleted channel will be in an undefined state with the universal type I/O module.

SEE
ALSO For more information about change of channel wirings, refer to:
“n Online change of channel wirings” on page E1-24

n Changing the signal category of channels (only for universal type

I/O modules)
When changing the signal category of the channels of the I/O module, you need to reassign
I/O variables that are appropriate for the category of signal the change is being made to.
When you have changed the signal category of channels, IOM download is executed. The op-
eration of the I/O module after download is completed is as follows:

l Changing to a different signal category input

When you change the channel of I/O module to input of a different signal category, after the
internal change process in the I/O module completes, the values are newly read from the
fields.
TIP The logical data that is configured to the channel will differ depending on the signal category before and after
the change.
• When changing from AO to DI, DO to AI, AI to DI, or DI to AI
After "0" (FALSE for DI, 0.0 for AI) is configured for the logical data, the input value from the channel is
reflected.
• When changing from AO to AI, DO to DI, AI to AI, or DI to DI
After the value from before the change is configured for the logical data, the input value from the channel
is reflected.

When you change the signal category from current input (AI) to current input with HART
(AI_HART), or, from current input with HART (Al_HART) to current input (Al), the channels
continue their operation even during IOM download. In this case, you do not need to reassign
the I/O variables.

l Changing to a different signal category output

When you change the channel of I/O module to output of a different signal category, after in-
ternal change process in the I/O module completes, DO outputs 0 and AO outputs tight-shut
output value to the field. The output values from the application logic will be output to the field
after you perform the output enable operation.
When you change the signal category from current output (AO) to current output with HART
(AO_HART), or, from current output with HART (AO_HART) to current output (AO), the chan-
nels continue their operation even during IOM download. In this case, you do not need to re-
assign the I/O variables.

l Changing to a high current output

You can change from a high current output type signal to a signal of other type or category by
online change.
• When changing from status output (DO) to high current output (DO_1.3A or 2A), or, from
high current output (DO_1.3A or 2A) to status output (DO), you do not need to reassign
the I/O variables.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-32
• When changing from the output other than status output (AI, AO, DI) to high current out-
put (DO_1.3A or 2A), or, from high current output (DO_1.3A or 2A) to the output other
than status output (AI, AO, DI), you must reassign the I/O variables.

IMPORTANT
If the second and the third channel of the channels that you try to define in DO of high current
output are already defined as a different channel, the intended channels cannot be defined in
the high current output.

The channels that are changed to high current output (DO_1.3A or 2A) will output 0 and go
into output disable status. The output values from the application logic will be output to the
field after you perform the output enable operation. Only the channels that are targeted for on-
line change are affected.

l Operating mode upon online change of the channel signal category

The changes of the operating mode upon online change of the channel signal category are as
follows:
• When changing to AO or DO
The change is the same as when an output channel assignment is added. As the channel
for which assignment has been changed will start in a state where output is disabled, the
operating mode will be Waiting.
• When changing to AI or DI
The change is the same as when an output channel assignment is deleted. When output
disabled channels no longer exist in the station, the operating mode becomes Running.
SEE
ALSO For more information about operating mode upon change of channel wirings, refer to:
“l Operating mode at online changing” on page E1-25

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-33

E1.6.1 Procedure for online change download of signal

category of channels
There are the following three cases for online change download of the signal category (AI,
AO, DI, DO) of channels in the universal type I/O module:
• Change from other than DO to other than DO
• Change from other than DO to DO
• Change from DO to other than DO

IMPORTANT
• You must follow this procedure when performing online change download of the signal
category of channels. Otherwise, it may lead to the failure of field devices at the connec-
tion destination.
• When you change the signal category from/to DO for a module that is installed on a base
plate with disconnecting terminal, disable the ON pulse diagnosis (pulse test (ON) or low
voltage pulse test (ON)), set the DO to OFF, and then open or close the disconnecting
terminal.
• In the Zone2/Div2 area, removal or installation of barrier cards while they are powered is
prohibited. Do not remove or install barrier cards.

n Changing the signal category from other than DO to other than DO

Follow these steps to change and online change download the signal category of channels
from other than DO to other than DO:
1. Lock the channels to be changed.
2. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
Open the disconnecting terminals of the channels to be changed.
• For a base plate with barrier
Remove the barriers of the channels to be changed from the base plate.
3. On SENG, change the signal category of the channels.
4. Run online change download from SENG.
When the download is successful, confirm that no abnormality is found in the I/O modules
by checking the SCS status display or the LED lamps of the I/O modules.
5. Replace the field devices that are connected to the channels that have been changed.
6. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
Close the disconnecting terminals of the channels that have been changed.
• For a base plate with barrier
Install the barriers of the channels that have been changed on the base plate.
7. Unlock the locked channels.
8. For an output channel, perform output enable operation.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-34

n Changing the signal category from other than DO to DO

Follow these steps to change and online change download the signal category of channels
from other than DO to DO:
1. Lock the channels to be changed.
2. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
Open the disconnecting terminals of the channels to be changed.
• For a base plate with barrier
Remove the barriers of the channels to be changed from the base plate.
3. On SENG, change the signal category of the channels to DO. At the same time, disable
the ON pulse diagnosis of the channels.
4. Execute online change download from SENG.
When the download is successful, confirm that no abnormality is found in the I/O modules
by checking the SCS status display or the LED lamps of the I/O modules.
5. Replace the field devices that are connected to the channels that have been changed.
6. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
Close the disconnecting terminals of the channels that have been changed.
• For a base plate with barrier
Install the barriers of the channels that have been changed on the base plate.
7. As necessary, enable ON pulse diagnosis.
8. Execute online change download from SENG.
9. Unlock the locked channels.
10. Perform the output enable operation.

n Changing the signal category from DO to other than DO

Follow these steps to change and online change download the signal category of channels
from DO to other than DO:
1. Lock the channels to be changed. When the high current output is set, you need to lock
the primary channel only.
2. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
a. Disable the ON pulse diagnosis of the DO channels.
b. Execute online change download from SENG.
When the download is successful, confirm that no abnormality is found in the I/O
modules by checking the SCS status display or the LED lamps of the I/O mod-
ules.
c. Perform the output enable operation for the channels that have been changed
d. Open the disconnecting terminals of the channels to be changed. When the high
current output is set, you need to perform the operation for all target channels.
• For a base plate with barrier
Remove the barriers of the channels to be changed from the base plate.
3. On SENG, change the signal category of the channels.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.6 Precautions for online change download of N-IO > E1-35
4. Run online change download from SENG.
When the download is successful, confirm that no abnormality is found in the I/O modules
by checking the SCS status display or the LED lamps of the I/O modules.
5. Replace the field devices that are connected to the channels that have been changed.
6. Perform the following operation based on the type of the base plate used:
• For base plate with disconnecting terminal
Close the disconnecting terminals of the channels that have been changed.
• For a base plate with barrier
Install the barriers of the channels that have been changed on the base plate.
7. Unlock the locked channels.
8. For an output channel, perform output enable operation.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.7 Online change of subsystem communication modules> E1-36

E1.7 Online change of subsystem

communication modules
This section describes online changes such as the addition/deletion/dual-redundancy specifi-
cation of subsystem communication modules, changes to settings relating to communication
inputs and outputs, the addition/deletion of subsystem communication I/O FBs, and changes
to wiring for subsystem communication I/O FBs.
SEE
ALSO For more information about precautions during online changes of a subsystem communication module, refer
to:
“n Precautions related to fire and gas communication modules when downloading an online change on-
to SCS” on page E1-29

n Locking of subsystem communication data

By locking subsystem communication data, you can reduce the impact of online changes on
the application logic or prevent erroneous outputs to subsystems resulting from application
logic correction errors.
Subsystem communication data cannot be locked once an online change download is started.
Lock subsystem communication data before starting an online change download.
To change a communication input/output definition from any SCS Manager window or builder,
close the Communication I/O Lock window first. After the online change is completed, display
the Communication I/O Lock window again, if necessary.

Table E1.7-1 Relationship of online changes and locking of communication modules

Content of change Lock
Change a transmission definition
Add, change or delete a communication definition
Add a subsystem communication I/O FB
Required (inputs/outputs need to be locked).
Change the wiring of a subsystem communication
I/O FB
Change an error handling action(*1)
Delete a subsystem communication I/O FB Not required.
*1: If a setting is changed while an error occurs, input values will change. Subsystem communication outputs are not affected.

n Online change procedure

The procedure for making an online change is as follows:
1. Change the application logic and perform build.
2. Check the application logic for consistency using Integrity Analyzer.
3. Check the range to be tested using Cross Reference Analyzer.
4. Change the SCS's security level to Level 1.
5. Lock the inputs/outputs of subsystem communication data in accordance with what you
have changed.
6. Close the Communication I/O Lock window.
7. Perform an online change download.
8. Open the Communication I/O Lock window.
9. Test the modified application logic.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.7 Online change of subsystem communication modules> E1-37
10. Unlock the inputs/outputs of subsystem communication data.
11. Reset the SCS's security level to Level 2.
12. Save the SCS project using Version Control Tool.

n Addition, deletion, and dual-redundant specifications of subsystem

communication modules
Addition, deletion, and dual-redundant specifications of subsystem communication modules
can be changed online.

n Online changes relating to communication inputs/outputs

When changing a communication I/O setting in the Communication I/O Builder or Safety Com-
munication I/O Editor, also change the wiring of the subsystem communication I/O FB affec-
ted by the change.

l Online change download

If an online change download is to be performed after a communication input/output data or
subsystem communication module setting has been changed, the subsystem communication
data of the target subsystem communication module needs to be locked before commencing
the online change download. If the subsystem communication data of the target module is not
locked, the application logic will be affected by a restart of the subsystem communication
module.
The subsystem communication module will restart after the online change download is com-
pleted. After the subsystem communication module has been restarted, unlock the subsystem
communication data of the module.

n Online changes relating to subsystem communication I/O FBs

l Adding a subsystem communication I/O FB
If a subsystem communication I/O FB is added, the FB also needs to be wired. If the FB is not
wired, a build error will occur.
Before performing an online change download to add a subsystem communication I/O FB, the
communication I/O data of the target subsystem communication module needs to be locked.
An online change download to add a subsystem communication I/O FB is performed as a ser-
ies of multiple scans. Specifically, the subsystem communication I/O FB is added first, and
then the wiring is changed. As a result, the added FB is not wired while the online change
download is in progress. The subsystem communication I/O FB temporarily assumes the fol-
lowing status during the download:
• Subsystem communication input FB: The data value is 0. The data status is FALSE.
• Subsystem communication output FB: The data value is ignored. The data status is
FALSE.
The subsystem communication module will restart after the online change download is com-
pleted. Once the subsystem communication module has been restarted, unlock the subsys-
tem communication data of the module.

l Deleting a subsystem communication I/O FB

When deleting a subsystem communication I/O FB, also delete the wiring of the FB.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E1.7 Online change of subsystem communication modules> E1-38

l Changing a wiring
Before performing an online change download, the subsystem communication data of the tar-
get subsystem communication module needs to be locked. To change the wiring of a subsys-
tem communication I/O FB between two subsystem communication modules, subsystem
communication data needs to be locked for the subsystem communication module that con-
tains the wired communication data before the change, as well as the subsystem communica-
tion module that will contain the wired communication data after the change. If the data of
both modules is not locked, subsystem communication data will be immediately input to the
application logic after the online change download is completed, and outputs from the applica-
tion logic will also be output to subsystems immediately after the download.
Each subsystem communication module will restart after the online change download is com-
pleted. Once the subsystem communication module has been restarted, unlock the subsys-
tem communication data of the module.

n Changing a POU that includes subsystem communication output FB

To change a POU containing a subsystem communication output FB, the communication out-
put data of the subsystem communication module wired to the applicable subsystem commu-
nication output FB needs to be locked.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2. Import/Export function> E2-1

E2. Import/Export function

The application data of a project can be exported to an external file, and the application data
in an exported file can also be imported to a project. This function can be used when diverting
or regenerating SCS projects during SCS expansion or reformation.
This function cannot be used together with iDefine projects. Application data that was created
by using iDefine need to be controlled under the project management by iDefine.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.1 Precautions concerning import/export> E2-2

E2.1 Precautions concerning import/export

This section summarizes the precautions to take when you perform an import or export. You
must observe these precautions when carrying out the actual operation.

n Outline of import/export
The import/export functions support modifying and reusing SCS project databases. Import/
export should be executed from AD Organizer or SCS Manager, depending on the purpose.
For example, execute import/export by using SCS Manager for data that is managed by SCS
Manager.
However, some of the targets of import/export using SCS Manager will differ depending on
the engineering method.

n Precautions on compatibility (including import from builders)

• When importing the files created in the previous software release number of SENG, the
setting values for the new items supported only in the newer software release number of
SENG will be the default values.
• The files exported from the project created on newer software release number SENG
cannot be imported to the project opened on the older software release number SENG.

n Precautions on password
When importing a project to replace an old project, the passwords of project and POUs are
also imported and the old passwords will be replaced.
Therefore, when using export and import, you should manage the project password and the
passwords of POUs for exported project.
Importing Source Project Importing Project

PJT1'
PJT1 Export Import (Original A
(Password:A)
Password:B)
Export File Replaced after
POU1' Importing
POU1
(Original a
(Password:a)
Password:b)

Figure E2.1-1 Passwords replaced after importing

The effects regarding passwords after importing are shown as follows:

• When importing the exported project files with passwords, the passwords of exported
project and POUs are also imported and the existing passwords will be replaced. After
importing, the passwords of the imported project will be required to open the project, with-
out the passwords, the imported project cannot be opened for editing.
• When importing those POUs that are protected by passwords, the passwords of the exist-
ing POUs will be replaced by the passwords of the imported POUs. So, after importing,
the passwords of the imported POUs will be required to open the POUs, without the
passwords, the imported POUs cannot be opened for editing.

n How imported POUs are handled in Cross Reference Analyzer

If the POU to be imported has an identical name with an existing POU, the Cross Reference
Analyzer will act as follows:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.1 Precautions concerning import/export> E2-3
If the POU to be imported is exactly the same as the existing POU, the Cross Reference Ana-
lyzer will mark the POU as "Unchanged POU" and display it in green icon. If the POU to be
imported is discrepant from the existing POU, the Cross Reference Analyzer will mark the
POU as "Changed POU" and display it in red (Modified) icon.

n How to check when project data is migrated by export or import

How to check differences in the imported data after migration of project data by import/export
is as follows:

Table E2.1-1 Builder definitions and how to verify

Builder Data How to Verify
SCS Manager POU Cross Reference Analyzer
I/O Wiring Cross Reference Analyzer
Binding Cross Reference Analyzer
SCS Project Properties Domain/Station number Project Comparing Tool
CENTUM Project Folder Project Comparing Tool
Configuration Properties Target Project Comparing Tool
Memory size for temporary variables Project Comparing Tool
Connections IP Address Project Comparing Tool
Resource Properties Resource Number Project Comparing Tool
Cycle Timing Project Comparing Tool
Memory size for online changes-Code (Fixed value) (*1)
Memory size for online changes-User Project Comparing Tool
variable size
SCS Constants Builder Interval of Repeated Warning Alarms Project Comparing Tool
Synchronous Mode Project Comparing Tool
Scan Period for External System Project Comparing Tool
Modbus Word Order Project Comparing Tool
Alarm Notify Action when AOF Re- Project Comparing Tool
leased
PV Status of S_ANLG_S Project Comparing Tool
Optical ESB Bus Repeater/Maximum Project Comparing Tool
Extension Distance (*1) SCS Con-
stants Builder
Extend Scan Period Automatically (*1) Project Comparing Tool
Behavior at Abnormal Calculation (*1) Project Comparing Tool
Automatic IOM Download (*1) Project Comparing Tool
Locking of Internal Variables (*1) Project Comparing Tool
Device Power-Off Period (*2) Project Comparing Tool
Device Startup Waiting Period (*2) Project Comparing Tool
Alarm Suppression During Device Re- Project Comparing Tool
set (*2)
Fire and Gas Communication Startup Project Comparing Tool
Time
16-bit Modbus master support mode Project Comparing Tool
DNP3 Slave Function (*3) Project Comparing Tool
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.1 Precautions concerning import/export> E2-4
Table E2.1-1 Builder definitions and how to verify (Table continued)
Builder Data How to Verify
I/O Parameter Builder Node Parameter (Extends Node Bus/ Project Comparing Tool
Extends To (Km) of Optical ESB Bus
Repeater) (*1)
Module parameter Cross Reference Analyzer
Channel parameter Cross Reference Analyzer
Communication I/O Builder Communication I/O definition Cross Reference Analyzer
Communication I/O wiring Cross Reference Analyzer
SCS Link Transmission SCS Link transmission data definition Cross Reference Analyzer
Builder
Wiring definition Cross Reference Analyzer
Modbus Address Builder - Project Comparing Tool
DNP3 Communication Build- - Project Comparing Tool
er (*3)
Tag Name Builder - Project Comparing Tool
Alarm Priority Builder - Project Comparing Tool
Alarm Processing Table - Project Comparing Tool
Builder
*1: The corresponding item may not exist or the configurable value may be different depending on the software release number
of the system or SCS type. Such items may therefore be picked up as discrepancies by the Project Comparing Tool.
*2: This item can be used with SCS projects created using a version of SENG that is R4.03.00 or later.
*3: It can be used in SCSU1 database created by SENG R3.02.20 or later.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.2 Export/import using AD Organizer> E2-5

E2.2 Export/import using AD Organizer

This section describes the procedures for exporting/importing SCS project data by using AD
Organizer and the procedure for deleting an SCS project by using AD Organizer.
TIP When engineering by using iDefine, the engineering data that was defined by using iDefine is also imported
and exported to SCS projects. In addition, the setting information on FB types to be converted to instances is
also included. The iDefine project itself is not imported or exported.

n Exporting SCS projects

You can export SCS projects to a specified location. The export file includes SCS project in-
formation defined in SCS Manager, the safety I/O, safety communication I/O, nodes, and IOM
definitions under the corresponding SCS project in AD Organizer but does not include history
information. Follow these steps to export an SCS project:
1. On the System Structure Navigator, select one or multiple SCS projects.
2. Right-click and select [Export SCS].
The Select Folder dialog box appears.
3. Specify the folder to which the project is to be exported and click [OK].
When the export is complete, the following result appears.
• All exported SCS projects
• List of files at the export destination
• List of SCS projects for which export failed and reasons of failure

n Importing SCS projects

You can import the exported SCS projects. You can specify the SCS projects that were expor-
ted from the same AD project or different AD projects, and import them into the RS project.
You need to perform the following procedure to import the project:
1. On the System Structure Navigator, select the RS project folder.
2. Right-click and select [Import SCS].
The Import SCS dialog box appears.

Figure E2.2-1 Example of SCS project import settings

3. Click the […] button on the right side of [File] text entry box and select one SCS project to
be imported.
If you want to import the SCS data other than the data of the SCS project in the specified
folder, select the [Exclude SCS Project Files] check box.
4. Perform either of the following operations:
• From the [SCS] drop-down list, select the SCS name of the import destination.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.2 Export/import using AD Organizer> E2-6
• Enter a new SCS name.
5. Click the [Import] button.
If you selected an SCS name from the [SCS] drop-down list, the existing SCS project is
overwritten.
If you entered a new SCS name, a new SCS project is created. Using SCS Manager,
change the setting items of the new SCS project to the appropriate values.

n Responding to an error when importing an SCS project

• If an error occurs when you import an SCS project, do the following:
• If the error is due to duplicate P&ID tags, the corresponding safety I/O list and safety
communication I/O list are imported in a checked-out state. Start Safety I/O Editor or
Safety Communication I/O Editor, correct the P&ID tag, and then perform a check-in.
• If the error is due to a missing P&ID group, create a safety I/O list or safety communi-
cation I/O list with the name of the P&ID group that you want to set under the [I/O-
List] folder in System Structure Navigator.

n Deleting SCS projects

You need to perform the following procedure to delete the SCS project:
1. Use the Windows function to delete the SCS project data to be deleted from the RS proj-
ect folder.
2. From the menu bar of the System Structure Navigator in AD Organizer, select [Display] >
[Update].
The status of the target SCS is updated. The SCS projects created with RS original engi-
neering are deleted.
3. To delete the SCS project created with I/O list engineering, specify the target SCS project
under the RS project in the System Structure Navigator and click [Delete] on the toolbar.
All the data under the deleted project of the RS project database is deleted, and the IOM
definition information related to the deleted project is deleted from AD Organizer.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.3 Importing and exporting data that is managed by SCS Manager > E2-7

E2.3 Importing and exporting data that is

managed by SCS Manager
By using SCS Manager, you can export/import the application data that is managed in SCS
Manager to/from external files. In addition to SCS Manager, some builders also support ex-
porting to and importing from external files.
TIP In I/O list engineering, both SCS Manager and AD Organizer are used to import/export project data.

This section describes the importable and exportable files, and whether online change down-
load is possible after the import.

n SCS project application data exportable by SCS Manager

The units of application data of an SCS project that can be exported by the SCS Manager and
the menu item names displayed under [Export] of the [File] menu are as follows.

Table E2.3-1 Specifying export data and Export menu items

Specifiable export data Menu item Detailed menu item
Project Entire SCS project Project Entire Project (*1)
Defined words Defined words
Resource Resource properties Resource Properties
I/O device instances (*2) I/O Device Instances
Global variables (*2) Global Variables
Wiring variables (*3)(*2) Wiring Variables
External bindings (*4) External Binding
POU POU
Variables (*5) Variables
Defined words Defined words
SCS Project Properties - (*6)
*1: If you select this item, all the data shown in the table other than SCS project properties are exported.
*2: The function for exporting data in the format of a PXF file cannot be used while implementing I/O list engineering.
*3: Only wired variables among global and local variables are exportable.
*4: Only binding variables among global variables and binding groups are exportable.
*5: When I/O list engineering is being implemented and data is being exported in the CSV format, the variables reflected from
Generation Manager will not be exported while all other variables will be exported.
*6: You cannot use the [File] menu to export SCS Project Properties. To export SCS Project Properties, start the Engineering
Launcher in SCS Manager, and use the [Export] button in the SCS Project Properties dialog box.

n Application data imported by SCS Manager

When you import data from data files of an SCS project using SCS Manager, you can import
all of the exported data as a whole or selectively import data by specifying only the lower-level
data units you want to import. When you import data from other data files, all of their exported
data will be imported. However, if any of the project name, configuration name or resource
name in the data file for import do not match their counterparts in the destination project, an
error dialog box appears and the import ends up in a failure.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.3 Importing and exporting data that is managed by SCS Manager > E2-8
Table E2.3-2 Application data selectable for import
File format Exported data file Data unit selectable for import
Project
Entire SCS project
POU (you can select multiple POUs)
Defined words Defined words
Resource properties Resource properties
Binary (PXF format) I/O device instances I/O device instance (*1)
Global variables Global variable (*1)
Wiring variables Wiring variable (*1)
External bindings External bindings
POU POU
Variables Variable (*2)
Text (CSV format) Defined words Defined words
SCS Project Properties (*3) SCS Project Properties
*1: The import function cannot be used while implementing I/O list engineering.
*2: When performing I/O list engineering, variables of the same name as the variables reflected from Generation Manager will
not be imported while all other variables will be imported.
*3: The operations to import SCS Project Properties differ from those for other data. Import using the [Import] button of the SCS
Project Properties dialog box.

IMPORTANT
Files with the same software revision number for SENG can be imported. Using SENG to
open an SCS project created with an earlier version will make it possible to import that file as
well.

Whether the 'Online change download' is applicable to the imported application data or not is
determined by the items of its source data. If the source data before import is online-changea-
ble, the imported data is also online-changeable.

n Builders supporting import/export

The table below shows a list of builders that support Import/Export and whether the 'online
change download' is allowed for the imported builder files.

Table E2.3-3 Builders supporting import/export and online-changeability of their files

Builders supporting Import/Export Online change download (*1)
SCS Constants Builder No (*2)
I/O Parameter Builder Yes
Communication I/O Builder Yes
SCS Link Transmission Builder Yes
Modbus Address Builder Yes
DNP3 Communication Builder (*3) No (*4)
Tag Name Builder Yes
Alarm Priority Builder No
Alarm Processing Table Builder No
*1: Yes: Online change downloading possible
No: Online change downloading not possible

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.3 Importing and exporting data that is managed by SCS Manager > E2-9
*2: Among the setting items of the SCS Constants Builder, Extend Scan Period Automatically, Locking of Internal Variables
(SCSP2 only), Behavior at Abnormal Calculation, Automatic IOM Download, Device Power-Off Period, and Device Startup
Waiting Period are changeable by online change download.
*3: Export/Import is possible only for the SCS projects of SCSU1 that are created by the software version R3.02.20 or later.
*4: Among the items that are set by DNP3 Communication Builder, DNP3 slave station address, DNP3 master station address,
Timeout value for Select Before Operate [sec.], Event to be removed when event buffer overflows, Generate an event when
Freeze and Clear command changes data values, Include Frozen Counters in Class 0 response, and Type of response mes-
sage fragmentation are changeable by online change download.

IMPORTANT
If you import text files that were exported from builders, do not edit the exported files before
you import them. Only the text files that were exported from builders are importable; do not
import other files.

Exporting a Builder file: On the [File] menu, click [External File] and then click [Export]. The
data of the Builder file of the currently opened Builder is exported to an external file.
Importing a Builder file: On the [File] menu, click [External File] and then click [Import]. The
data that was exported to the external file is imported and the data of the imported Builder file
is shown in the currently opened builder window.

n Precautions on handling CSV files

Do not edit CSV files that are exported from SCS project data by using an editor. If you import
an edited CSV file in SCS project data, the operations are not guaranteed.

n Precautions on the importing sequence

When importing individual global variables or individual POUs, the sequence of importing is
as follows:
1. POU (Function Block)
2. POU (Other than Function Block)
3. Global Variables
• If you import global variables before importing the POU (Function Block), the Type infor-
mation regarding the imported global FB instance may be missing. As a result, "???" will
be shown in the Type column of Dictionary.
• If you import POU (other than Function Block) before importing the POU (Function Block),
the Type information regarding the imported local FB instance may be missing. As a re-
sult, "???" will be shown in the Type column of Dictionary.
• If a user-defined function block (such as FB1) is using another user-defined function
block (FB2) as a local parameter and FB1 is imported before FB2, the Type information
regarding the imported local parameter type may be missing. As a result, "???" will be
shown in the Type column of the parameter in Dictionary. The function blocks used as pa-
rameters should be imported before.
If the above sequence is not observed when importing the individual global variables or
POUs, a build error will occur. In this case, import again in the above-mentioned order.

n Unit for exporting and sequence of importing

This section describes the file formats that are used when exporting SCS project data and ac-
tions that are carried out while importing. SCS projects can be exported as binary (PXF for-
mat) files. SCS project properties and SCS constant data can be exported in CSV files.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.3 Importing and exporting data that is managed by SCS Manager > E2-10

l Import/export in PXF format

Even if you have exported data for individual SCS projects in binary (PXF format) files, you
can import data selectively (you can import the POUs you need) from the exported data.
The actions during importing are shown in the following table.

Table E2.3-4 Actions during importing

Imported Contents Actions during Importing
Project Deletes the existing project first and then adds the imported project in PXF files.
Importing projects is only possible when the project name, configuration name
and resource name of the source project match with those of the existing proj-
ect.(*1)
POU • Deletes the existing POU with the identical name when adding the POUs
from PXF files.
• POU name can be changed during importing.
• When you import multiple POUs at one time, you can choose whether to im-
port them without changing their name (by deleting any existing POUs and
adding them with the same name) or by automatically renaming any POUs
with the same name to non-duplicate names.
• When importing a local instance where the FB is not defined in the existing
project, the variables with unknown types will be generated and build error
will occur. To solve this problem, you can either define a new FB before im-
porting or import the FB.
Resource properties Overwrites all the existing properties of the resource.
I/O device instances (*2) • If the imported I/O device has different index number with the existing I/O
modules, the imported I/O device will be added as a new I/O module.
• If the imported I/O device has an identical index number with the same type
of existing I/O module, the IOM parameters (node address, slot numbers and
redundancy setting) of the imported I/O device will be added to replace the
existing I/O module.
• If the imported I/O device has an identical index number with a different type
of existing I/O module, a warning message will be displayed and the I/O de-
vice will not be imported. The existing I/O module will not be changed.
Global variables (*2) • If the imported variable is different from the existing variable, the imported
variable will be added as a new variable.
• If the name and scope of the imported variable are identical with the existing
variable, the imported variable will be added to replace the existing variable.
• If the existing variable is wired with other variable in the same channel, the
imported variable will replace the existing variable and be wired with the oth-
er variable.
• When importing an instance where the FB is not defined in the existing proj-
ect, the variable with an unknown type will be generated and a build error will
occur. To solve this problem, you can either define a new FB before importing
or import the FB.
Wiring variables (*2) • If the imported variable is different from the existing variable, the imported
(I/O variables) variable will be added as a new variable.
• If the name and scope of the imported variable are identical with the existing
variable, the imported variable will be added to replace the existing variable.
• If the existing variable is wired with other variable in the same channel, the
imported variable will replace the existing variable and be wired with the oth-
er variable.
• When importing an instance where the FB is not defined in the existing proj-
ect, the variable with an unknown type will be generated and a build error will
occur. To solve this problem, you can either define a new FB before importing
or import the FB.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E2.3 Importing and exporting data that is managed by SCS Manager > E2-11
Table E2.3-4 Actions during importing (Table continued)
Imported Contents Actions during Importing
Binding • If the imported binding group has a different group ID from the existing bind-
ing group (either Consumer Group or Producer Group), the imported group
will be added as a new group.
• If the imported binding group has an identical group ID to an existing binding
group (either Consumer Group or Producer Group), the imported group will
be added to replace the existing group.
• If the imported binding variable has different name from the existing binding
variable, the imported binding variable will be added in a binding group.
Defined words • If the imported defined words have a different name from the existing defined
words, the imported defined words will be added as a new defined words.
• If the imported defined words have an identical name with the existing de-
fined words, the imported defined words will be added to replace the existing
defined words.
*1: When importing the entire projects, an error dialog box appears if any one of the project name, configuration name and re-
source name of the importing source project does not match with that of the existing project.
For instance, if the entire SCS project of SCS0101 is exported, it is not allowed to import the entire project as SCS0102. If
you wish to export the entire project and import it to an SCS project with a different name, create a new project with the same
name as the importing source project, perform import operation, and then change the project name, configuration name and
resource name to the desired names before using the project.
*2: Cannot be imported when I/O list engineering is applied.

l Import/export of SCS Project Properties

You can export SCS Project Properties as a CSV file, but this does not mean that all of the
data will be applied when you import it. Actions during import are shown in the following table:

Table E2.3-5 Actions when importing SCS Project Properties

Items Actions during Import
Station Type Reflected only when importing during new project creation
Database Type Not reflected
Station Address Reflected
Domain Number Reflected
Station Number Reflected
IP Address Not reflected
Component Number Reflected
Version Not reflected
CENTUM Project Folder Reflected
SCS Project Attribute Not reflected
Originally Created Not reflected

l Import/export of SCS constants

SCS constants can be exported in a CSV file. However, when you import the constants, the
default value may be used if the setting does not exist, depending on the software release
number of your system and the SCS type. If the settable values are different, they will need to
be changed. If you do not change them, an error will occur at build time.
SEE
ALSO For more information about importing/exporting PXF files and CSV files, refer to:
E2.3, “Importing and exporting data that is managed by SCS Manager” on page E2-7

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3. Modification and reuse of SCS project database> E3-1

E3. Modification and reuse of SCS

project database
This section describes the procedures for expanding or remodeling an existing SCS project,
recreating an SCS project, and so on by using the import/export functions.
The source project and the destination project for import must be registered in different AD
projects.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.1 Data transfer procedure during expansions/remodeling in modifications where online change is
possible> E3-2

E3.1 Data transfer procedure during

expansions/remodeling in modifications
where online change is possible
This section describes the procedure for applying the results of making a modification that
can be changed online from a user-defined project to the current project. This procedure in-
volves exporting the results from the user-defined project and only importing the data that has
been modified into the current project.
TIP If all the changes were made by using iDefine and none was made by using SCS Manager when engineering
by using iDefine, importing the same iDefine-config file to the current project reflects all the changes.

IMPORTANT
• Do not forget to import all the modified content.
• Confirm that the current project has not been changed manually before importing.
• Modifications with a newly added POUs cannot be made through online change down-
loads. Carry out the expansions/remodeling by offline download.

The overall flow of the procedure is as follows:

1. If a POU included in a library has been modified, first update the original library project
with the modifications required, and then copy the modifications to the library of the cur-
rent project.
2. If an SCS project has been modified, apply the modifications from the user-defined proj-
ect to the current project.
3. Perform an online change download of the SCS project.
SEE
ALSO For more information about importing/exporting PXF files and CSV files, refer to:
E2.3, “Importing and exporting data that is managed by SCS Manager” on page E2-7

n Library POU data transfer in modifications where online change is

possible
If you are using library POUs, use the Import/Export function to apply the modifications from
the library in the user-defined project to the original library.
• By way of preparation, back up the original library using the Version Control Tool.

l Exporting library POU source data where online change is possible

Export the library Program Organization Unit (POU) source data.
• Export the data from the library of the project at the origin of the import to create the fol-
lowing PXF file or CSV file.
• A PXF file of the entire library project.
• When reflecting the addition/modification of a global variable being used in the li-
brary project, create a PXF file or CSV file of the global variable. (*1)
• When reflecting the addition/modification of a definition word being used in the li-
brary project, create a PXF file or CSV file of the global variable (*1)
*1: When performing RS original engineering, create a PXF file. When performing I/O list engineering, create a CSV file.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.1 Data transfer procedure during expansions/remodeling in modifications where online change is
possible> E3-3

l Importing library POU data where online change is possible

1. Open the original library with SCS Manager and import the required data from the expor-
ted PXF or CSV files.
1-1 In the Import dialog, specify the PXF file containing the entire exported library proj-
ect and import only the modified POUs (*1)
1-2 When importing global variables, in the Import dialog box, specify the PXF file or
CSV file (*2)that contains global variables and perform the import. Import the data
upon making a specification in the import dialog box.
1-3 When importing defined words, specify the PXF file or CSV file of the defined word
in the import dialog box and import (*2)
*1: In the course of importing, if the POU contains any FB that does not exists in the current project, the following warning
message will be displayed. In such a case, a build error will occur when building the project.
Warning: Type 'UFB' for symbol 'iUFB' was not found in this project.
or
Warning: Type 'UFB1' for Parameter 'iUFB1' was not found in this project.
'UFB', 'UFB1': FB Name
'iUFB', 'iUFB1': FB Instance Name
*2: When performing RS original engineering, import the PXF file. When performing I/O list engineering, import the CSV
file.

2. Delete any global variables and defined words that are not required after importing. The
variables that are not used in POU can be checked in the Browser. Start the Browser and
generate (or refresh) the cross-reference information for checking the unused variables.
3. Perform build.
4. Validate the contents on the Integrity Analyzer.
5. Copy the original library to the LIBRARIES folder of the current project.

n SCS project data transfer in modifications where online change is

possible
Apply the modifications from the modified user-defined project to the current project using the
Import/Export function.
• By way of preparation, back up the current project using the Version Control Tool.

l Exporting SCS project source data where online change is possible

Export the SCS project data from the import source project.
1. Using SCS Manager, export the data from the project at the origin of the import and cre-
ate the following PXF file or CSV file.
• A PXF file of the entire project
• When reflecting the addition/modification of a global variable, create a PXF file or
CSV file of the global variable. (*1)
• When reflecting the addition/modification of a definition word, create a PXF file or
CSV file of the global variable(*1)
*1: When performing RS original engineering, create a PXF file. When performing I/O list engineering, create a CSV file.

2. If you have modified "Component Number" or "CENTUM Project Folder" in the SCS Proj-
ect Properties, export the SCS Project Properties to a CSV file. Items other than "Compo-
nent Number" and "CENTUM Project Folder" cannot be modified via an online change in
SCS Project Properties.
3. When performing I/O list engineering, use AD Organizer to export the SCS project at the
origin of the import.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.1 Data transfer procedure during expansions/remodeling in modifications where online change is
possible> E3-4
SEE
ALSO For more information about procedures for exporting an SCS project using System Structure Navigator of AD
Organizer, refer to:
“n Exporting SCS projects” on page E2-5

l Importing SCS project data where online change is possible

1. Open the original current project with SCS Manager and import the required data from
the exported PXF files.
1-1. In the Import dialog, specify the PXF file containing the entire exported project and
import only the modified POUs (*1)
1-2. To import the global variables, in the import dialog box, specify the PXF file contain-
ing the global variables, and import.
1-3. To import the defined-words, in the import dialog box, specify the PXF file contain-
ing the defined-words, and import.
*1: In the course of importing, if the POU contains any FB that does not exists in the current project, the following warning
message will be displayed. In such a case, a build error will occur when building the project.
Warning: Type 'UFB' for symbol 'iUFB' was not found in this project.
or
Warning: Type 'UFB1' for Parameter 'iUFB1' was not found in this project.
'UFB', 'UFB1 ': FB Name
'iUFB', 'iUFB1': FB Instance Name

2. After importing, the unnecessary global variables and defined words should be deleted.
The variables that are not used in POU can be checked on the Browser. Start the Brows-
er and generate (or refresh) the cross-reference information to check the unused varia-
bles.
3. If you have modified "Extends Scan Period Automatically", "Behavior at Abnormal Calcu-
lation", "Locking of Internal Variables", "Automatic IOM Download", "Device Power-Off
Period", or "Device Startup Waiting Period" of SCS Constants Builder, correct each of
them in the builder. There are no other items in SCS Constants Builder that can be modi-
fied via an online change.
4. Regarding the following builders, import the builder files if required.

Table E3.1-1 Builder files for import (modifications where online change is possible)
Builder Builder File Location (*1)
I/O Parameter Builder (*2) SCS Project\YOKOGAWA_SCS\SAFETY\IOM\IOMDEFSB.edf
Communication I/O Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\CommIO.edf
(*2)
Link Transmission Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\LinkTrans.edf
Modbus Address Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION\Modbus-
Def.edf
DNP3 Communication SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION
Builder (*3) \DNP3Def.edf
Tag Name Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\TAG\TAG.edf
*1: Relative path under SCS project top directory
*2: In the case of I/O list engineering, it is not necessary to import the builder files using I/O Parameter Builder and Communica-
tion I/O Builder.
*3: Because the event buffer size cannot be modified by an online change, import the event buffer size, and then restore and
save the original value.

The builder files of the Alarm Priority Builder and Alarm Processing Table Builder cannot
be modified by online change. Do not import them.
5. If "Component Number" or "CENTUM Project Folder" have been changed in the SCS
Project Properties, import the CSV file that you exported to in advance.
6. Perform the following operations when performing I/O list engineering:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.1 Data transfer procedure during expansions/remodeling in modifications where online change is
possible> E3-5
6-1 Run an SCS import using System Structure Navigator of AD Organizer to reflect the
safety I/O list, safety communication I/O list, and IOM information onto the SCS
project at the destination of the import.
In the SCS Import dialog box, select the [Exclude SCS Project Files] check box and
perform the import.
6-2 If changes have been made with the safety I/O list, safety communication I/O list,
and IOM information, perform the build process with RS Generation Manager.
SEE
ALSO For more information about build processes of SCS project using Generation Manager, refer to:
D4.4, “Operating procedure of RS generation” on page D4-8
For more information about importing an SCS project using System Structure Navigator of AD Organizer, re-
fer to:
“n Importing SCS projects” on page E2-5

l Online change downloads during SCS project expansions/remodeling

When you have applied the library POU data and SCS project data to the current project, run
the online change download.
1. Perform build.
2. Use the Project Comparing Tool to check that the original project after import is the same
as the source user-defined project.
a. Launch the Project Comparing Tool and clear the [compare imported project] check
box to compare the original project after import and the source user-defined project
and check that there are no discrepancies. When you do so, check the project path
display area of the Project Comparing Tool or the printed discrepancies summary re-
port to make sure that the project paths that you are comparing are correct.
b. If a discrepancy is found, check that it is appropriate.
3. On Integrity Analyzer, validate the contents.
4. On Cross Reference Analyzer, validate the modified contents. Modifications must also be
tested after download.
5. Perform online change downloading.
SEE
ALSO For more information about procedures for an online change download, refer to:
E1., “Online change of applications” on page E1-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.2 Data transfer procedure during expansions/remodeling in modifications requiring offline download>
E3-6

E3.2 Data transfer procedure during

expansions/remodeling in modifications
requiring offline download
This section describes the procedure for making a modification that requires offline download
and importing the results of testing in the import source project into the current project on a
project-by-project basis. Offline download is necessary because the entire project is being im-
ported.
The overall flow of the procedure is as follows:
1. If a POU included in a library has been modified, first apply the modifications to the library
project to the original library project, and then copy the modifications to the library of the
current project.
2. If the import source project has been modified, apply the modifications to the current proj-
ect.
3. Download the SCS project offline.

n Library POU data transfer in modifications requiring offline

download
Apply the modifications from the library in the import source project to the original library and
copy it to the LIBRARIES folder of the current project.
• By way of preparation, back up the original library using the Version Control Tool.
1. Open the library of the importing source project side on the SCS Manager, and change
the target name to SCS_TARGET and then save the change.
2. Export the entire project containing the library to PXF files.
3. Use the SCS Manager to open the original library, specify the PXF files thus created in
the Import dialog, and then import the whole project containing the library.
4. Execute the build of the original library.
5. Check the integrity of the original library using the Integrity Analyzer.
6. Copy the original library to the LIBRARIES folder of the current project.

n SCS project data transfer in modifications requiring offline

download
Reflect the modifications on the current project from the modified importing source project.
• By way of preparation, back up the current project using the Version Control Tool.

l Exporting SCS project source data requiring offline download

1. Open the importing source project on the SCS Manager, and change the target name to
SCS_TARGET and then save the change.
2. Export the entire source project to PXF files.
3. If you have modified "Component Number" or "CENTUM Project Folder" in the SCS Proj-
ect Properties of the import source project, export the SCS Project Properties to a CSV
file.
4. If you have modified SCS Constants Builder in the import source project, export it to a
CSV file.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.2 Data transfer procedure during expansions/remodeling in modifications requiring offline download>
E3-7

l Importing source SCS project data that requires offline download

1. In SCS Manager, open the current project, import the whole project specifying the PXF
file exported from the source project.
2. Redefine the library path to the current project.
3. Import the CSV file if there is an exported CSV file of the SCS Constants Builder.
4. Import the builder files if required.

Table E3.2-1 Builder files for import

Builder Builder File Location (*1)
I/O Parameter Builder (*2) SCS Project\YOKOGAWA_SCS\SAFETY\IOM\IOMDEFSB.edf
Communication I/O Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\CommIO.edf
(*2)
Link Transmission Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\LinkTrans.edf
Modbus Address Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION\Modbus-
Def.edf
DNP3 Communication SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION
Builder \DNP3Def.edf
Tag Name Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\TAG\TAG.edf
Alarm Priority Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION\Alm-
Pri.edf
Alarm Processing Table SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION
Builder \AlmTbl.edf
*1: (relative path under SCS project top directory).
*2: In the case of I/O list engineering, it is not necessary to import the builder files using I/O Parameter Builder and Communica-
tion I/O Builder.

5. Import the CSV file if there is an exported CSV file of the SCS Project Properties of
source SCS project.
6. Perform the following operations when performing I/O list engineering:
a. Using AD Organizer, reflect the safety I/O list, safety communication I/O list, and IOM
information onto the SCS project at the destination of the import.
b. If changes have been made with the safety I/O list, safety communication I/O list, and
IOM information, perform the build process with RS Generation Manager.
SEE
ALSO For more information about build processes of SCS project using Generation Manager, refer to:
D4.4, “Operating procedure of RS generation” on page D4-8
For more information about importing an SCS using System Structure Navigator of AD Organizer, refer to:
“n Importing SCS projects” on page E2-5

l Offline download during expansions/remodeling

Execute offline download in an SCS project that you have finished importing.
1. Perform build.
2. Use the Project Comparing Tool to check that the original project after import is the same
as the source user-defined project.
2-1. Launch the Project Comparing Tool and clear the [compare imported project] check
box to compare the original project after import and the source user-defined project
and check that there are no discrepancies. When you do so, check the project path

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.2 Data transfer procedure during expansions/remodeling in modifications requiring offline download>
E3-8
display area of the Project Comparing Tool or the printed discrepancies summary
report to make sure that the project paths that you are comparing are correct.
2-2. If a discrepancy is found, check that it is appropriate.
3. Validate the contents on the Integrity Analyzer.
4. Validate the modified contents on the Cross Reference Analyzer. Modifications must also
be tested after download.
5. Perform offline download.
TIP • Possibilities of online change download
Whether or not it is possible to perform online change download when the current project has been
modified by import is the same as when the same modifications are made manually on the current proj-
ect. Therefore, in some cases, online change download is possible even when the entire project has
been imported. Whether or not it is possible to perform online change download is found when you run a
build or try to run online change download after importing.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-9

E3.3 Data transfer procedure during SCS

project regeneration
In order to apply the new features on the newer SENG software release number to the exist-
ing SCS project or to reuse the existing project, the existing project needs to be ported (or
regenerated).
When porting (or regenerating) a project, the original project needs to be entirely exported in-
to PXF format binary files. Then import the PXF files into a new project.
When performing I/O list engineering, in addition to using SCS Manager, it is necessary to ex-
port/import the SCS project by using AD Organizer.
The overall flow of the procedure is as follows:
1. If the library needs to be regenerated, regenerate the library first.
2. Regenerate the SCS project.
3. Check that the regenerated project is equivalent to the original project.
SEE
ALSO For more information about importing/exporting PXF files and CSV files, refer to:
E2.3, “Importing and exporting data that is managed by SCS Manager” on page E2-7

n Regenerating library data when regenerating an SCS project

Implement the following procedure if you need to regenerate a library as part of regenerating
an SCS project.
1. Back up the original library on the Version Control Tool if necessary.
2. Open the source library in SCS Manager and export the whole project containing the li-
brary to PXF files.
3. In Windows Explorer, delete the original library, or move it to a different place.
4. Create a new library by using the same name as the source library, and change the rela-
ted resource names and configuration names to the same names that are used in the
source library.
5. In the SCS Manager, import the whole project containing the source library. In the Import
dialog, specify the PXF files to which the project has been exported.
6. Build the library.
7. Check the integrity of the library using the Integrity Analyzer.

n Regenerating an SCS project with the new revision

Follow these steps to regenerate an SCS project with the new revision:
1. Using SCS Manager, export all of the data in the source SCS project.
2. If you are upgrading an SCS project that was created by I/O list engineering with a soft-
ware revision R4.01.00 through R4.03.00, create an safety communication I/O list for the
target SCS by using Communication I/O List Output Tool.
3. In System Structure Navigator of AD Organizer, select the target SCS and execute an ex-
port of the SCS.
4. In Windows Explorer, move the source SCS project to a work folder.
5. From the menu bar of AD Organizer, select [View] > [Refresh].
The display of System Structure Navigator is refreshed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-10
6. In System Structure Navigator of AD Organizer, select the target SCS and start the Safety
I/O Editor, then delete all I/O rows, save, and check in.
7. If there is no Comm_I/O under the target SCS, proceed to the next step. If there is a
Comm_I/O under the target SCS, select the Comm_I/O and start Safety Communication
I/O Editor. Delete all rows of Program Definition, Communication Definition, and Signal
Definition, save the list, and then check in.
8. In System Structure Navigator, select the target SCS and click [Delete].
9. Using SCS Manager, create a new SCS project by using the same SCS name and loca-
tion as the source SCS project, and change the related resource names and configura-
tion names to the same names that are used in the source project.
10. Copy any libraries used in the source SCS project to the LIBRARIES folder of the newly
created SCS project. Also copy any libraries that you have regenerated.
TIP When engineering by using iDefine, you do not need to copy the iDefine-config file.

11. In SCS Manager, open the newly created SCS project and import the data that you ex-
ported in step 1.
12. Import the builder files of the source project.
13. If you are performing I/O list engineering, select [View] > [Refresh] from the menu bar of
AD Organizer.
The display of System Structure Navigator is refreshed.
14. When performing I/O list engineering, use System Structure Navigator of AD Organizer to
select the target RS project and execute an import of the SCS.
As the files to import, specify the files that you exported in step 3.
In the SCS Import dialog box, select the [Exclude SCS Project Files] check box and per-
form the import.
15. If you are upgrading an SCS project that was created by I/O list engineering with a soft-
ware revision R4.01.00 through R4.03.00, import the safety communication I/O list that
you created in step 2.
16. From AD Organizer, start Generation Manage and run the SCS project build process.
SEE
ALSO For more information about build processes of SCS project using Generation Manager, refer to:
D4.4, “Operating procedure of RS generation” on page D4-8
For more information about the procedure for exporting source SCS project data using SCS Manager, refer
to:
“l Exporting SCS project data when regenerating an SCS project” on page E3-11
For more information about the procedure for exporting an SCS project using System Structure Navigator of
AD Organizer, refer to:
“n Exporting SCS projects” on page E2-5
For more information about the procedure to import source SCS project data by using SCS Manager, refer to:
“l Importing SCS project data when regenerating an SCS project” on page E3-11
For more information about the procedure for importing an SCS using System Structure Navigator of AD Or-
ganizer, refer to:
“n Importing SCS projects” on page E2-5
For more information about Communication I/O List Output Tool, refer to:
“n Communication I/O List Output Tool” on page App.3-15

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-11

l Exporting SCS project data when regenerating an SCS project

1. Back up the original project on the Version Control Tool if necessary.
2. Open the original project on the SCS Manager, and export the whole project and create
the PXF files.
3. Export the SCS Project Properties from the source project to create a CSV file.
4. Export the SCS Constants Builder data from the source project to create a CSV file.

l Importing SCS project data when regenerating an SCS project

Follow these steps to import data of the source SCS project to the destination SCS project:
1. In SCS Manager, open the newly created SCS project, specify the PXF file to which the
whole source project was exported, and import the whole project.
2. Open the SCS Constants Builder and import the exported CSV file in the source project.
3. Import the builder files of the builders that are shown in the following table:

Table E3.3-1 Builder files to be imported (project regeneration)

Builder Builder File Location (*1)
I/O Parameter Builder (*2) SCS Project\YOKOGAWA_SCS\SAFETY\IOM\IOMDEFSB.edf
Communication I/O Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\CommIO.edf
(*2)
Link Transmission Builder SCS Project\YOKOGAWA_SCS\SAFETY\CONFIGURATION\LinkTrans.edf
Modbus Address Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION\Modbus-
Def.edf
DNP3 Communication SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION
Builder \DNP3Def.edf
Tag Name Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\TAG\TAG.edf
Alarm Priority Builder SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION\AlmPri.edf
Alarm Processing Table SCS Project\YOKOGAWA_SCS\INTEGRATION\CONFIGURATION
Builder \AlmTbl.edf
*1: (relative path under the SCS project top directory)
*2: In the case of I/O list engineering, it is not necessary to import the builder files using I/O Parameter Builder and Communica-
tion I/O Builder.

4. Open SCS Project Properties and import the exported CSV file in the source project.

n Regenerating an SCS project with a different station type

Follow these steps to regenerate an SCS project with a different station type:
TIP If the source SCS project was created by I/O list engineering with a software version earlier than R4.03.10,
create a safety communication I/O list of the source SCS by using Communication I/O List Output Tool and
load it into Safety Communication I/O Editor in advance.

1. Using SCS Manager, export the entire source SCS project.

2. When performing I/O list engineering, record the IOM definition details of the SCS project
at the origin of the migration. To record the IOM definition details, follow these steps:
a. In System Structure Navigator of AD Organizer, select the source SCS and start IOM
Definition Editor.
b. Record the node and IOM definition details.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-12
Record the definition details by such as copying the setting items of IOM Definition
Editor and pasting these onto the editor.
c. In System Structure Navigator of AD Organizer, select a file under the I/O-List folder,
start Safety I/O Editor, perform a save after clearing the RS Project column of the I/O
assigned to the target SCS, and check in.
d. In System Structure Navigator of AD Organizer, if there is a Comm_I/O, select it and
start Safety Communication I/O Editor, then clear the RS Project column of the pro-
gram definitions assigned to the target SCS. Because fire and gas communication re-
lated definitions are allowed only for S2SC70, delete all such definitions, save the list,
and check in.
3. When engineering by using iDefine, specify the iDefine-config file that was imported to
the target SCS and save it.
You can specify the iDefine-config file that was imported to the target SCS by using the
revision management function of iDefine.
4. In Windows Explorer, move the source SCS project to a work folder.
5. From the menu bar of the System Structure Navigator in AD Organizer, select [Display] >
[Update].
The display of System Structure Navigator is refreshed.
6. Select the target SCS, and click the [Delete] button on the toolbar.
7. Because the type of SCS is being changed, re-assign licenses to the SCS.
8. In SCS Manager, create a new SCS project with the same SCS name under the original
RS project. Definitions of the configuration name and resource number should be the
same as the source station.
9. Copy any libraries used in the source SCS project to the LIBRARIES folder of the newly
created SCS project. Also copy any libraries that you have regenerated.
TIP When engineering by using iDefine, you do not need to copy the iDefine-config file.

10. Using SCS Manager, import the PXF files of the SCS that you exported in step 1 to the
destination SCS project. However, exclude the POUs that cannot be defined in the desti-
nation SCS.
11. Import the builder files of the source project.
12. From the menu bar of the System Structure Navigator in AD Organizer, select [Display] >
[Update].
The display of System Structure Navigator is refreshed.
13. If you are performing I/O list engineering, in the System Structure Navigator, select a file
under the I/O-List folder and start Safety I/O Editor, and then perform the following opera-
tions:
a. In the RS Project column, enter the same data as that of the source SCS project. De-
lete the data that is not supported in the regenerated station, save the list, and check
in.
14. If you are performing I/O list engineering, select Comm_I/O, if it is defined in the System
Structure Navigator, and start Safety Communication I/O Editor, then perform the follow-
ing operation:
a. In the RS Project column, enter the same data as that of the source SCS project. De-
lete the data that is not supported in the regenerated station, save the list, and check
in.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-13
15. If you are performing I/O list engineering, select the destination SCS in the System Struc-
ture Navigator and start IOM Definition Editor.
a. Click the [Create Node & IOM] button, and create nodes and IOMs.
b. Change the node and IOM definition details to the values that you recorded in step
2b.

IMPORTANT
• If you export the entire SCSP1/SCSV1 project and import it to a newly created project of
SCSP2/SCSP3, the values of the source project are applied to the following definitions
related to application capacity. After importing, you need to change the values to the fixed
values or default values of SCSP2/SCSP3.

Table E3.3-2 Definition items related to application capacity

Definition item Value of SCSP1/SCSV1 Value of SCSP2 Remarks
Online change 1700000 (fixed value) 2550000 (fixed value) A build error will occur if the
code size (*1) value is not changed after im-
porting.
Online change user 32768 (default) 131072 (default) A value different from the de-
variable size (*2) 8192 to 65536 (allowable 8192 to 262144 (al- fault SCSP2 value is set after
specification range) lowable specification importing.
range)
Constant/tempora- 32768 (default) 131072 (default) A value different from the de-
ry variable size (*3) 8192 to 65536 (allowable 8192 to 262144 (al- fault SCSP2 value is set after
specification range) lowable specification importing.
range)
*1: [Code size] in the Advance settings dialog box of the Settings tab in Resource Properties of the SCS Manager
*2: [User variable size] in the Advanced settings dialog box of the Settings tab in the Resource Properties of the SCS Manager
*3: [Memory size for temporary variables] in the Target tab of Resource Properties in the SCS Manager or [Memory size for tem-
porary variables] in the Hardware tab of Configuration Properties in the SCS Manager

• If you are performing RS original engineering and have imported the project data of
SCSP1/SCSV1 to an SCSP2/SCSP3 project that uses optical ESB bus repeater, config-
ure the node settings of the I/O Parameter Builder for all FIO nodes connected to the
CPU node through the optical ESB bus repeater modules. If [Extends Node Bus] is set to
[No], change it to [Yes] and specify the actual node distance to [Extends To (Km)].
• If you import SCSP2/SCSP3 applications to an SCSP1 project, do not import the entire
project. Instead, import the engineering data individually, for example, in POU units.

16. From AD Organizer, start Generation Manage and run the build process for the SCS.
SEE
ALSO For more information about how to create nodes & IOM, refer to:
“n Creating the node and I/O module based on safety I/O list” on page D3-5
For more information about build processes of SCS using Generation Manager, refer to:
D4.4, “Operating procedure of RS generation” on page D4-8
For more information about how to use Communication I/O List Output Tool, refer to:
“n Communication I/O List Output Tool” on page App.3-15
For more information about the procedure to export SCS project data, refer to:
“l Exporting SCS project data when regenerating an SCS project” on page E3-11
For more information about the procedure to export SCS project data by using SCS Manager, refer to:
“l Importing SCS project data when regenerating an SCS project” on page E3-11

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.3 Data transfer procedure during SCS project regeneration> E3-14

n Confirming a regenerated project

Check that the regenerated project is equivalent to the original project using the following pro-
cedure.
1. Open the regenerated SCS project on the SCS Manager and perform build.
2. Check the validity using the Integrity Analyzer.
3. Using the function of Cross Reference Analyzer for comparison with the original project,
check that all POUs are equivalent to those of the original project.
Open the regenerated SCS project on the SCS Manager and compare it with the original
SCS project using the Cross Reference Analyzer. Confirm that all POUs are displayed in
green (retesting or review is not required). At this point, check whether the path in the title
bar of Cross Reference Analyzer or in the report is correct.
4. For data that cannot be checked with Cross Reference Analyzer, use the Project Com-
paring Tool to ensure that the regenerated SCS project is equivalent to the original SCS
project. When doing so, select the [compare imported project] check box of the Project
Comparing Tool.
Launch the Project Comparing Tool and compare the regenerated SCS project with the
original SCS project, so that there is no difference in all items. When you do so, check
that the project paths which you are comparing are correct in the project path display
area of Project Comparing Tool or in the printed summary report of the discrepancies.
• If no difference is detected with the Cross Reference Analyzer or the Project Compar-
ing Tool, re-test of SCS application is not required.
• If the following differences are detected with the Project Comparing Tool, check the
details and modify as needed:
• If you import an SCS project that is created using a SENG with an older software
release number, definitions that do not exist in the original project are set to the
default values in the regenerated project. These items are picked up as discrep-
ancies by the Project Comparing Tool. When you change the default value, the
items must be tested.
• If you import an SCS project that is created for a different model, definitions that
do not exist on the model used for the original project are set to the default val-
ues in the regenerated project. Moreover, definitions with different configurable
values will produce an error at build in the regenerated project.
5. Perform an offline download to the SCS and make sure that the SCS starts.
TIP If you have modified a regenerated project after verifying that the regenerated project is equivalent to the orig-
inal project by using the Cross Reference Analyzer and Project Comparing Tool, ascertain the range for re-
testing in the usual manner by using the Cross Reference Analyzer, Project Comparing Tool, or the self-docu-
ment printout, and conduct the tests.

SEE
ALSO For more information about how to check project data migrated by export or import, refer to:
“n How to check when project data is migrated by export or import” on page E2-3

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.4 Reusing SCS project data> E3-15

E3.4 Reusing SCS project data

This section describes the procedures of operations to perform with the SCS project in order
to reuse an existing SCS project database. Do not use Windows Explorer to copy SCS proj-
ects because, if you do so, you can no longer register the SCS project in an AD project.

n Duplicating an SCS project

Using AD Organizer, you can duplicate an SCS project by exporting the SCS project to be du-
plicated, changing the SCS name, and then importing that project. Follow these steps to du-
plicate an SCS project:
TIP If the original SCS project was created by I/O list engineering with a software version earlier than R4.03.10,
create a safety communication I/O list of the original SCS by using Communication I/O List Output Tool and
load it into Safety Communication I/O Editor in advance.

1. Export an SCS project.

2. Import the exported SCS project. In the SCS name field of the Import SCS dialog box,
enter a new name of the duplicate SCS.
3. If you are performing I/O list engineering, edit the imported safety I/O list and safety com-
munication I/O list and check these in.
You cannot check in a duplicated safety I/O list or safety communication I/O list because
the P&ID Group name and P&ID Tag are the same as the original. You need to change
the P&ID Tag name and P&ID Group name to separate the Group. After making the
change, you can check in the safety I/O list and safety communication I/O list by using
the Check-in window.
4. Perform the following operations when engineering by using iDefine:
a. Export the ProSafe-RS I/O file of the target SCS from AD Organizer.
b. After the ProSafe-RS I/O file is imported in iDefine and the engineering is complete,
export the created application as an iDefine-config file.
c. Import the iDefine-config file to AD Organizer.
d. Run the reflection process and the SCS project build process by using Generation
Manager.
5. Using SCS Manager, open the SCS project that you have imported.
6. Change the following settings of the SCS project to the appropriate values.

Table E3.4-1 Settings that you need to change values

Dialog box Tab Setting item
Configuration Properties dialog box in Hardware Ar- General tab Name
chitecture View
Connection Properties dialog box in Hardware Archi- Network Param- IP address
tecture View eters tab
Resource Properties dialog box in Link Architecture General tab Name, Resource number
View
SCS Project Properties dialog box SCS tab Domain number, Station number
Project tab CENTUM project folder
Add/Remove dependencies dialog box - Dependencies

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.4 Reusing SCS project data> E3-16
TIP When an SCS project is copied to another location, the library project will also be copied together. The SCS
project at the copy destination will still reference the library at the copy source. For this reason, the depend-
ency of the SCS project and library project will become inappropriate. It is necessary to reconfigure the path
of the library project at the copy destination with the Add/Remove Dependencies dialog.

7. Save the SCS project.

8. Using Document Generator, change the title string for the cover page of the document to
print.
In the Customize dialog box that is opened from the [Option] menu of SCS Manager,
clear the [Enhanced printing style] check box, change the title string, and then select the
check box again.
SEE
ALSO For more information about the procedures for importing/exporting SCS project data, refer to:
E2., “Import/Export function” on page E2-1
For more information about how to use Communication I/O List Output Tool, refer to:
“n Communication I/O List Output Tool” on page App.3-15
For more information about how to change the title string for the cover page of the document, refer to:
“● Header/Footer” in “■ Options tab” in F2.5, “Customizing print settings (backward-compatible mode)” in
Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about the procedure to import ProSafe-RS I/O files to iDefine, refer to:
10., "IMPORT FROM AD SUITE" in iDefine User Guide (Yokogawa Extensions) (PR12002-
MAN-980_01)

n Modifying an application
The following modifications to the application are required on the copied station.
1. Modification of inter-SCS safety communication
Modify the inter-SCS safety communication application.
a. The domain number and station number on the consumer and producer will change.
Modify the variable names accordingly.
b. Delete the existing binding table and regenerate it.
2. Modification of SCS link transmission
Modify the receiving station as appropriate.

n Checking the projects that are created by reusing data

Check that the copied SCS project is equivalent to the original project.
1. Perform build for the copied SCS project.
2. Run the Integrity Analyzer to validate the contents.
3. Launch the Cross Reference Analyzer and check that all Program Organization Units
(POU) are equivalent to those of the project before the project was copied. If you are
comparing with a project with a different station address, proceed to step 4.
a. Use the Cross Reference Analyzer's function for comparison with the original project
to compare the copied SCS project with the original SCS project. Check that all
POUs are displayed in green, excluding the sections in which you have modified the
inter-SCS safety communication and related areas. At this point, check whether the
path in the title bar of Cross Reference Analyzer or in the report is correct.
b. Validate the modified content.
Each modification must be tested at an appropriate timing.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<E3.4 Reusing SCS project data> E3-17
4. For data that cannot be checked with the Cross Reference Analyzer, use the Project
Comparing Tool to ensure that the copied SCS project is equivalent to the original SCS
project.
a. Launch the Project Comparing Tool, clear the [compare imported project] check box,
and compare the copied SCS project with the original SCS project. Ensure that there
are no discrepancies, except in sections that you have modified. When you do so,
check in the results printed from the Project Comparing Tool for the project path dis-
play area and the summary of discrepancies to make sure that the project paths that
you are comparing are correct.
b. If a discrepancy is found, check that it is appropriate.
5. Perform an offline download to the SCS and make sure that the SCS starts.
TIP If the copied SCS project contains any modifications, except those in inter-SCS safety communication and
SCS link transmission, ascertain the range for retesting in the usual manner by using Cross Reference Ana-
lyzer, Project Comparing Tool, self-document printout, or other appropriate means.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F. Installation and start-up> F-1

F. Installation and start-up

This chapter describes the installation of ProSafe-RS system, the wiring to field devices, a
procedure of start-up including tests, commissioning and precautions for the start-up.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F1. Procedure of installation and start-up > F1-1

F1. Procedure of installation and start-

up
This section describes a general procedure of the start-up of ProSafe-RS system ranging
from the installation of equipment to the completion of commissioning.

n Installing and getting started with ProSafe-RS

The regular procedure from the installation of equipment to the completion of commissioning
is as follows.
START

1. Cable Installation

2. Equipment Installation

3. Cable Wiring

4. Power Supplying

5. Equipment Set up

6. Check of Equipment

7. Check of Loops

8. Sequence Test

9. Trial Operation

End

Figure F1-1 Workflow for installing and getting started with ProSafe-RS

1. Install control bus, optical cables and cables between panels.

2. Install ProSafe-RS and other equipment. When performing wireless communication with
subsystems, configure the initial settings of the wireless devices on the subsystem side.
3. Wire for networks such as V net and ESB buses, as well as I/O modules and field devi-
ces.
4. Supply power to ProSafe-RS and other equipment.
5. Turn on ProSafe-RS and other equipment to start.
6. Check individual hardware of ProSafe-RS and other equipment (including I/O modules).
7. Check loops from the field to I/O modules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F1. Procedure of installation and start-up > F1-2
8. Test application logic of ProSafe-RS.
9. Perform a trial operation for the entire system to confirm actions of the ProSafe-RS sys-
tem itself.
SEE
ALSO For more information about engineering of fire and gas communication, refer to:
E1.5, “Engineering for fire and gas communication” in Engineering Guide Vol. 2 (IM 32P01C20-01EN)

l Commissioning
In commissioning, procedures from No.6 “Check of Equipment” to No. 9 “Trial Operation” in
the flowchart of “Installation and start-up” are performed. Confirm the following items in this
series of procedures.
• All modules in SCS, wiring to field devices and wiring of power supply are correctly instal-
led.
• All modules in SCS, field devices and power supply work without faults.
• Sensor measurement values are correct.
• Input values to SCS and output values from SCS are correct. (Including tests of high/low
limits)
• Application logic works correctly according to changes of input values.
• Operations for failure occurrence take place as intended on the basis of each field device
and SCS module.
• Safety application logic works correctly between actual SCSs when Inter-SCS safety
communication is used.
• Confirm Demand Reaction Time.
• Confirm actions against a fault (a failure in SCS).

l Precautions
• When executing offline download on a suspended SCS, confirm that the SCS is being
suspended with the SCS State Management window in SENG so as not to download the
database to a different SCS by mistake.
• Confirm that the SCS works normally after offline download with the SCS State Manage-
ment window in SENG.
• Confirm that database is downloaded correctly with the Database Validity Check Tool in
SENG.
• Set new passwords for security levels 0 and 1 after offline download.
• Precautions for LED display of CPU of SCS
LEDs of CPU have a structure which switches between V net or Vnet/IP address display
and SCS Status Display. Set LED to the SCS Status Display when SCS is in operation.
• While SDV526 is outputting Off signals, it takes max. 5 minutes to detect an open circuit.
It takes max. 2 minutes to detect the recovery.
Because of this, if any of the following event occurs before the cause of open circuit error
is eliminated after a diagnosis information message of an abnormal status caused by the
open circuit is generated, a diagnosis information message of recovery is generated first.
And after about 5 minutes, a diagnosis information message of an abnormal status is
generated again.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F1. Procedure of installation and start-up > F1-3
TIP If you perform output enable operation before the abnormal status is re-detected, open circuit is detected
about 5 minutes after a diagnosis information message of recovery is informed if the output signal is OFF. If
the signal is ON, open circuit is immediately detected.

• SDV526 recovers from power supply error (the power to the I/O node or the field
power supply is turned off and on.)
• Dismounting and remounting of SDV526 or re-connection of a cable connector that
was disconnected (both modules in redundant configuration.)
• Recovery of ESB bus communication. (SDV526 recovers from a state where it out-
puts fail-safe values.)
• In the case of SDV521 (style S3 or above)/SDV53A (style S2 or above), if a short circuit
has occurred while the module is outputting an Off signal, it takes max. 10 seconds to de-
tect the short circuit.
• In the case of SDV521 (style S3 or below)/SDV53A (style S2 or below), if a short circuit is
detected while the module is outputting an Off signal and a diagnosis information mes-
sage indicating the abnormal status is generated, a diagnosis information message of re-
covery may be generated if either of the following events occurs before the short circuit is
repaired.
• The module is powered off and on (due to dismounting and remounting of the module
or turning on and off the power to the I/O node)
• Switch over to the standby module (when modules are in redundant configuration)
Also note that if the module is powered on while it has a short circuit, the short circuit may
not be detected. After the short circuit is repaired, it becomes possible to detect short cir-
cuits that occur afterward.
• In the case of SDV521/SDV53A, if a short circuit is detected while the module is output-
ting an On signal and a diagnosis information message indicating the abnormal status is
generated, a diagnosis information message of recovery may be generated before the
short circuit is repaired. Even after the recovery message is generated, an Off signal is
output to the channel and the channel remains in the output disabled status.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2. Preparation before installation and start-up of N-IO nodes > F2-1

F2. Preparation before installation and

start-up of N-IO nodes
You need set a node number for N-IO nodes by using the Node Number Setting Tool. When
performing the I/O list engineering, you can connect the FieldMate Validator to N-IO nodes to
perform connection tests between the devices and I/O modules in advance.

n Preparing N-IO nodes earlier than the upper equipment

You can prepare N-IO nodes that contain N-IO I/O modules earlier than the upper equipment
such as SENG, HIS, SCU.
1. Set the node numbers of all N-IO nodes.
2. Use the FieldMate Validator to perform the loop checking, to check the functionalities and
to configure the field device and N-IO I/O module under the N-IO node.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2.1 Configuring the N-IO node interface unit > F2-2

F2.1 Configuring the N-IO node interface unit

For the N-IO node interface unit, you can set the node number by connecting the computer
and maintenance port of the node interface unit. This section describes the tool to configure
the node number.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2.1 Configuring the N-IO node interface unit > F2-3

F2.1.1 Using the Node Number Setting Tool

You can use the Node Number Setting Tool to set a node number for N-IO nodes. This sec-
tion describes the Node Number Setting Tool.

n Outline of the node number setting operation

Node number is not set for the N-ESB bus module that is installed in the node interface unit of
the N-IO node when the module is shipped from the factory. You must set a node number for
the N-ESB bus module before connecting it to the SCU.
You need to connect the computer to the maintenance port of N-ESB bus module to set the
node number by using the software on the computer.
The software required to set the node number is available in the installation medium of
ProSafe-RS.

n Items to be prepared
The following items are required to set the node numbers:

l Software medium of ProSafe-RS

It includes USB drivers and Node Number Setting Tool required to set the node number. You
need to install this software on the computer that you use to set the node number.

l Computer
The computer must have the following specifications:
• Hardware
Compliant with the hardware requirement of Windows 10, Windows 8.1, or Windows 7.
• Software
Windows 10 Pro (64bit)
Windows 8.1 Professional (64bit, 32bit)
Windows 7 Professional SP1 (64bit, 32bit)

l USB cable
Use the MicroUSB Micro-B connector for the N-ESB bus module side.

n Preparing the computer that sets the node number

You need to install the required software on the computer that sets the node number.

l Installing USB drivers

1. Insert ProSafe-RS installation medium in computer drive.
2. On the explorer, open the following folder of ProSafe-RS installation medium:
<ProSafe-RS software medium drive>:\ProSafe-RS\NIO_TOOLS
3. Double click and run the Setup.exe.
The User Account Control dialog box appears.
4. Click [Yes].
A dialog box for confirming the setup details appears.
5. Select [Install] and click [OK].
A dialog box for confirming the installation start appears.
6. Click [OK].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2.1 Configuring the N-IO node interface unit > F2-4
7. When the Windows Security dialog box appears, click [Install].
8. When the dialog box notifying the completion of installation appears, click [OK].
TIP • When the dialog box prompting for computer restart appears, click [OK] to restart the computer.
• You can install the USB drivers after connecting the computer and N-ESB bus module.

l Copying the Node Number Setting Tool

1. Insert the ProSafe-RS installation medium in the computer drive.
2. On the explorer, open the following folder of ProSafe-RS software medium:
<ProSafe-RS software medium drive>:\ProSafe-RS\NIO_TOOLS
3. Copy NodeNumSetting.exe of the folder to any folder on the computer.

n Setting node numbers

The procedure to set node numbers is as follows:

l Checking before setting the node numbers

Before setting the node numbers, confirm that the status lamp of the N-ESB bus module is
ON.
Remove all N-ESB bus cables and optical ESB bus cables from both N-ESB bus modules to
disable the bus communication.

l Removing the N-ESB bus modules

If the node numbers are already set in the N-ESB bus modules, remove one of the two N-
ESB bus modules from the node interface unit. You can remove any of the two N-ESB bus
modules.
If the node numbers are yet to be set (ADRS lamp is OFF), you do not need to remove the N-
ESB bus module.

l Connecting the computer and N-ESB bus module

With the USB cable, connect the USB port of the computer (which is used to set node num-
bers) and the maintenance port of the powered N-ESB bus module on the node interface unit.
Maintenance port N-ESB bus module

USB cable

Computer

Node interface unit

Figure F2.1.1-1 Connecting the computer and N-ESB bus module

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2.1 Configuring the N-IO node interface unit > F2-5

l Tool operation
1. Double click and run the NodeNumSetting.exe command on the computer.
The Node Number Setting Tool window appears.

Figure F2.1.1-2 Node Number Setting Tool

2. Select a node number and click [Set].

A confirmation dialog box appears, showing the currently set node number and node
number to be set.
3. Click [Yes].
The node number is set to the N-ESB bus module. A dialog box displaying setting com-
pletion appears.
4. Confirm the node numbers in the ADRS lamp of the N-ESB bus module.

l Setting the node numbers of the other N-ESB bus module

If you removed the other N-ESB bus module, perform the following operations for the re-
moved N-ESB bus module. If you did not remove the other N-ESB bus module, proceed to
the next procedure.
1. Install the removed N-ESB bus module on the node interface unit.
The node number is copied from the N-ESB bus module that was already installed.
2. You need to confirm the node numbers in the ADRS lamp of the N-ESB bus module.

l Procedure after node number setting

1. Close the Node Number Setting Tool.
2. Remove the USB cable from the N-ESB bus module.
3. Connect all N-ESB bus cables and optical ESB bus cables to both N-ESB bus modules to
enable the communication with the SCU.
TIP The maintenance port of the N-ESB bus module is enabled when shipping. Before starting operation, you
must disable the port by using the NIU maintenance port setting tool on SENG.

SEE
ALSO For more information about NIU maintenance port setting tool, refer to:
I4.4, “NIU maintenance port setting tool” on page I4-41

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F2.2 Testing by using FieldMate Validator > F2-6

F2.2 Testing by using FieldMate Validator

You can use FieldMate Validator to test the N-IO modules that are defined in the safety I/O
list, and import the information once again after testing. When using FieldMate Validator, you
must enable the maintenance port and disable the maintenance port after use.

n Outline of testing by using FieldMate Validator

Outline of testing by using FieldMate Validator is as follows:
1. Export the IOM information to be tested to FieldMate Validator.
a. From the sub menu of the Safety I/O Editor, select [Export to FieldMate Validator] to
export the data of each safety I/O list.
b. Import the exported safety I/O list data into FieldMate Validator.
2. Test the data by using FieldMate Validator.
3. Import the test results from FieldMate Validator.
a. Export the information containing the test results from the FieldMate Validator in the
safety I/O list format.
b. From the sub menu of the Safety I/O Editor, select [Import from FieldMate Validator]
to import the data exported from FieldMate Validator.
4. Confirm that the status of test result has changed with the changes in the settings of the
safety I/O list.
When you change the IOM settings by using the Safety I/O Editor, it is indicated that that
the I/O setting used for the previous test result is changed.
SEE
ALSO For more information about operating FieldMate Validator and linking with AD Suite, refer to:
manual of FieldMate Validator

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F3. Overview of procedures to construct/maintain a stand-alone SCS configuration system>
F3-1

F3. Overview of procedures to

construct/maintain a stand-alone
SCS configuration system
This section explains each of the main steps of constructing and maintaining a stand-alone
SCS configuration system.
To do the following steps, you need to connect SENG to the Vnet/IP, but note that while a
SENG is connected, one of the buses (bus 2) is in an error status.
• Startup of SCS
• Re-connection of SENG
• Disconnection of SENG
• Replacement of one of the redundant CPU modules.

IMPORTANT
Always connect a SENG during maintenance and make sure that you check the following be-
fore you disconnect it.
• SCS is normally started.
• SCS inputs and outputs are all normal.
• There is no diagnostic information message indicating errors of the SCS.

n Getting started with SCS

The following information explains the procedure for starting SCS for the first time (offline
download).
SENG SENG SENG
CPU CPU CPU

Standby

(A)
Control

Control

(B) SCS SCS SCS

L2SW L2SW L2SW

(Status 1) (Status 2) (Status 3)

Figure F3-1 Getting started with SCS

1. Perform the following connections using network cables while the SCS is powered off.
(Status 1)
a. (A) Connection between SENG and L2SW, and powering them on
b. (B) Connection of bus 1 connectors on both CPU modules to L2SW
c. (C) Connection between bus 2 connectors on both CPU modules
2. Turn on the power of the SCS and perform offline download from SENG.
3. After the offline download is completed, wait until one of the CPU module enters the con-
trol state and the other enters the standby state, and then remove the cable between the
bus 1 connector of the standby-side CPU module and L2SW (Status 2) (Status 2)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F3. Overview of procedures to construct/maintain a stand-alone SCS configuration system>
F3-2
4. Disconnect the bus 1 cable of the control-side CPU module from L2SW and connect it to
the bus 1 connector of the standby-side CPU module (Status 3) (Status 3)

n Reconnection of SENG
Use the following procedure to connect an SENG to an operating stand-alone SCS for the
purpose of maintenance and so forth.
SENG SENG SENG
CPU CPU CPU

SCS SCS SCS

Standby

Standby
Control

Control

Control
L2SW L2SW L2SW

(Status 1) (Status 2) (Status 3)

Figure F3-2 Procedure for connecting stand-alone SCS to SENG

(Status 1) above shows SCS operating in stand-alone configuration. At this timing, SENG is
not powered and L2SW should be powered.
1. Disconnect the cable from the bus 1 connector of the standby-side CPU module and con-
nect it to L2SW. (Status 2)

IMPORTANT
When you make this connection, if the cable between the bus 1 connectors of the two CPU
modules of SCS is not long enough to be connected to the L2SW, you may remove the cable
and use a longer cable. However, you must be very careful not to misconnect the cable.

2. Connect the bus 1 connector of the standby-side CPU module to the L2SW with a cable.
Then, power on the SENG. (Status 3)

n Disconnection of SENG
The SENG can be disconnected after completion of maintenance and other intended opera-
tions in the following procedure.
SENG SENG SENG
CPU CPU CPU

SCS SCS SCS

Standby

Standby
Control

Control

L2SW L2SW L2SW

(Status 1) (Status 2) (Status 3)

Figure F3-3 Procedure of disconnecting SENG

(Status 1) above shows a status where SCS and SENG are connected.
1. Remove the cable between the bus 1 connector of the standby-side CPU module and
L2SW (Status 2) (Status 2)
2. Disconnect the bus 1 cable of the control-side CPU module from L2SW and connect it to
the bus 1 connector of the standby-side CPU module (Status 3) (Status 3)

n Replacement of one of the redundant CPU modules

Use the following procedure to replace one of the redundant CPU modules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<F3. Overview of procedures to construct/maintain a stand-alone SCS configuration system>
F3-3
SENG CPU SENG CPU SENG CPU

SCS SCS SCS

Replaced

Replaced
L2SW L2SW L2SW

Control

Control
(Status 1) (Status 2) (Status 3)

SENG CPU SENG CPU SENG CPU

(A)
(B)
SCS New (standby) SCS SCS

New
L2SW L2SW L2SW

Control
Control

Control
(Status 6) (Status 5) (Status 4)

Figure F3-4 Procedure of replacing one of the redundant CPU modules

(Status 1) above shows a status where an SENG is connected for the purpose of checking
diagnostic information.
1. Remove the cable between the bus 1 connector of the CPU module to be replaced
(standby-side) and L2SW. (Status 2)
2. Remove the cable between the bus 2 connectors on both CPU modules. (Status 3)
3. Remove the CPU module to be replaced from the node. (Status 4)
4. Prepare a new CPU module as a replacement and perform the following connections.
(Status 5)
a. (A) Connection between bus 1 connector of the new CPU module and L2SW
b. (B) Connection between bus 2 connectors on both CPU modules
5. Install a new CPU module in the node. (Status 6)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G. Emergency procedures> G-1

G. Emergency procedures
It is required to plan the operation procedure beforehand for emergencies including the occur-
rence of a shutdown demand or an equipment failure.
An emergency operation is required in case of the following. Referring to these operation
flows, plan the emergency operation specifically.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G1. Operation flow during the error occurrence> G1-1

G1. Operation flow during the error

occurrence
This section describes the operation flow when an error occurs in the system.

n Operation when SCS issues a pre-alarm because of a signal from

the field
START

1. Notice the alarm

2. Eliminate the fault

3. Check recovery

END

Figure G1-1 Operation when SCS issues a pre-alarm because of a signal from the field

1. Confirm the alarm with an alarm panel or HIS (for CENTUM Integration Structure).
2. Operate the DCS or field devices to eliminate the fault by following the operation manual.
3. Confirm the recovery of normal operation at the plant or DCS.

n Operation when plant is shutdown because of a demand from the

field
START

1. Check the on-site circumstances

2. Analyze the cause for shutdown

3. Remove the cause

4. Execute shutdown reset

5. Resume Operation

END

Figure G1-2 Operation when plant is shutdown because of a demand from the field

1. Maintenance personnel check the present state in the plant.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G1. Operation flow during the error occurrence> G1-2
2. An engineer analyzes a cause of the shutdown with the SOE Viewer in SENG. The engi-
neer identifies the cause of the fault with the diagnostic information message at the time
when a diagnostic fault occurs and event information is displayed in the SOE Viewer. For
CENTUM Integration structure, the engineer can display the process alarm message is-
sued by SCS as a historical message on the SOE Viewer to facilitate the identification of
the cause. The engineer then makes a procedure for removing the cause of the fault for
recovery. The messages can also be stored as a record by outputting them to a file.
3. The maintenance personnel remove the cause of the fault according to the work proce-
dure.
4. The maintenance personnel execute a shutdown reset operation from the ESD console.
5. Confirm the state of the plant again to restart the plant according to the operation manual.

n Operation when a user manually executes a shutdown

START

Does the hazard require a NO

shutdown? (The operator decides)

YES

1. Activate ESD PB

2. Analyze the cause for the hazard

3. Remove the cause

4. Execute shutdown reset

5. Resume Operation

END

Figure G1-3 Operation when a user manually executes a shutdown

1. Maintenance personnel confirm the state in the plant and operate ESD PB (Emergency
shutdown button) installed in the ESD console in order to avoid dangerous accidents.
2. The engineer analyzes the cause of the hazard with historical messages or trend data of
the DCS and the SOE Viewer in SENG, and makes a work procedure for removing the
cause of the fault.
3. The maintenance personnel remove the cause of the fault according to the work proce-
dure.
4. The maintenance personnel operate a shutdown reset from the ESD console.
5. Confirm the state of the plant again to restart the plant according to the operation manual.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G1. Operation flow during the error occurrence> G1-3

n Operation when ProSafe-RS equipment fails

START

1. Identify the location of the failure

2. Check diagnostic information

3. Contact YOKOGAWA service personnel

END

Figure G1-4 Operation when ProSafe-RS equipment fails

1. The engineer starts the SCS State Management window from SENG of the SCS where a
fault occurs and confirms the present status on the display. A diagnostic information mark
is displayed for I/O modules having a diagnostic fault. The engineer selects the I/O mod-
ule, and display Diagnostic Information window of the I/O modules to confirm a Diagnos-
tic Information Message related to the I/O modules.
2. The engineer confirms the messages generated by the diagnostic function of SCS. Dou-
ble-click the message for the corresponding measures. This opens the Help dialog box in
which the measures are indicated. Clicking a relevant message in the Diagnostic Informa-
tion Window and then a [confirmation] button on the Toolbar opens the Confirmation dia-
log box. Diagnostic Information Messages can be confirmed by pressing the [confirma-
tion] button on this dialog box (Operation for confirming individual messages).
3. Inform the service section at YOKOGAWA of the above information.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2. Operations and recovery procedures during the SCS error occurrence> G2-1

G2. Operations and recovery

procedures during the SCS error
occurrence
This chapter explains the action taken when an error occurs in the system and the recovery
procedures. If an error occurs in the system, operations corresponding to the error level are
performed.
There are the following three error levels.
• Fatal error
• Major error
• Minor error
TIP In this document, I/O shutoff switches and DO shutoff switches of the universal type I/O module are referred
to as an output shutoff switch.

SEE
ALSO For more information about operations at minor error occurrence and recovery procedure, refer to:
G2.3, “Actions taken at minor error occurrence and recovery procedure” on page G2-34

n Overview of system operations at occurrence of fatal errors and

major errors
The following provides an overview of system operations corresponding to the different SCS
error levels.

l Actions taken at fatal error occurrence

A fatal error disables hardware and/or software so that operation cannot be continued. Both
sides of a redundant CPU module stop and all output modules output the fail-safe value.

l Actions taken at major error occurrence

When a major error occurs, some hardware cannot continue the ordinary operation. When an
error occurs, the system takes action which you have configured in advance for the failure of
hardware. The application logics that handle major errors must also be configured.

l Shutdown operations
The shutdown operations fix the output status from an SCS. There are the following three
types of operations:
• Shutdown executed by a user-defined application logic
• Shutdown where the CPU fixes the output values of areas with failures
• Shutdown executed by an output module when it detects an error in the host system
(CPU)
When a fatal error occurs, the CPU stops and all output modules shut down; this is called all
output shutdown.

l Output value at fault

When an output module detects an error, the predefined fail-safe values will be used as the
output values. The fail-safe value of each output channel is referred to as the "Output Value at

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2. Operations and recovery procedures during the SCS error occurrence> G2-2
Fault." This value can be set in an I/O parameter for each DO or AO channel. For a DO chan-
nel, this action depends on the setting of [Output Value in Detecting Error] and for an AO
channel, depends on the settings of [Output Processing at Fault] and [Output Value at Fault].
(Only the setting item of [Output Value at Fault] cannot validate this action.)
However, the output module does not output the "Output Value at Fault" in following status:
• The output module being initialized
• The output module with Output Shutoff switch and the switch is energized.
• The malfunctioning output channel or the output module
TIP The descriptions in the later chapters will have the explanations regarding the tight-shut values may become
the output values of the analog output modules when the Tight-Shut/Full-Open function is enabled with an I/O
parameter. However, if the Tight-Shut/Full Open function is disabled, the output value of the module becomes
the "default initial value upon power-on" instead of the tight-shut value.

SEE
ALSO For more information about “Tight-shut/full-open” functions and “output value upon power-on”, refer to:
“n Tight-shut/Full-open” on page App.1-26

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-3

G2.1 Actions taken at fatal error occurrence and

recovery procedure
The CPU stops if a fatal error occurs in it. If the CPU module is in redundant configuration and
the control right is switched to the CPU module on the standby side, the error is treated as a
minor error. If the error affects the entire system, no output can be made, but in other cases,
communication from the CPU is stopped; all output modules output the fail-safe value at CPU
error. The fail-safe value is the value defined by the user in advance in an I/O parameter as
the value output by output modules when the CPU fails.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-4

G2.1.1 Operations and recovery procedures during the

error occurrence in the entire SCS
This is an operation which is performed when electric supply is started or stopped for the en-
tire SCS including CPU modules and I/O modules.

n Actions taken at error occurrence

Regardless of the duration of a power failure, the initial start processing is performed when
the power supply to the CPU nodes is renewed. Once the power is supplied to the system,
I/O module startup processing is performed and the operating mode shifts to the Waiting
mode. After the starting the I/O module, "0" is output from the DO channel while the tight-shut
value is output from the AO channel to the field.

n Recovery procedure
The user should perform the output enable operation from the SENG after confirming that all
output modules have been started successfully. Once the output enable operation is per-
formed, output values of the application logic are output to the field. When all outputs are
placed in the Output Enable status, the operating mode shifts to the Running mode.
User operation Start supplying power Output enable operation

Output from CPU Stop Periodic output

Output modules processing start

Output from (*2) Result of application logic processing

(*1)
output modules

*1: “0” for DO modules, and “0.0 [mA]” for AO modules.

*2: “0” for DO modules, and the tight-shut value for AO modules

Figure G2.1.1-1 Recovery from errors affecting the entire system

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-5

G2.1.2 Actions taken at CPU module error occurrence and

recovery procedure
If an error occurs in the hardware of the CPU module, CPU node or software, only the CPU
stops. If the CPU module is placed in redundant configuration, it is judged that a fatal error
has occurred when both CPUs fail.
The CPU also stops when offline download is performed to an operating SCS.

n Actions taken at error occurrence

If the CPU does not create any data output for a certain length of time, the connected output
modules will assume that the CPU is in a status where it cannot set an output value, and all
output modules will output each fail-safe value specified by the user in advance. (This is
called as "All output shutdown.") Input modules, on the other hand, are not affected by CPU
errors. In the case of redundant CPU modules, the same operation as for a single CPU mod-
ule configuration is performed if the module on the standby side fails.

n Recovery procedure
In order to recover from an error occurred in the CPU module, the CPU module replacement
may or may not be necessary.

l Recovery procedure by replacing a failed CPU module

The following figure illustrates the output values from the SCS after the CPU module has
been replaced, based on a single CPU module configuration.
Start of master
CPU
User operation database offline
replacement Output enable operation
download

Completion of
download to input
/output modules

Output from CPU Stop Periodic output

Output modules processing start

Output from Fail-safe value (*2) Result of application logic processing

output modules

*1: In the master database offline download, configuration information is downloaded to the I/O modules.
*2: “0” for DO modules, and the tight-shut value for AO modules.

Figure G2.1.2-1 Recovery after CPU module replacement

SEE
ALSO For more information about the procedure for replacing the CPU module, refer to:
I1.2, “Maintenance for ProSafe-RS equipment” on page I1-9

l Recovery procedure after the CPU module is restarted

Follow the recovery procedure below if the CPU module is restarted when the CPU and soft-
ware are normal.
1. Fail-safe values are being output to the field from output modules. When the CPU starts
up, the states of input/output modules are checked and the operating mode shifts to the
Waiting mode.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-6
2. Perform the output enable operation from the SCS Maintenance Support Tool of the
SENG.
When output modules are placed in the Output Enable status, the result of the application
logic processing is output to the field. The operating mode shifts to the Running mode.
User operation CPU restart Output enable operation

Output from CPU Stop Periodic output

Output modules processing start

Output from
Fail-safe value Result of application logic processing
output modules

Figure G2.1.2-2 Recovery when the CPU module is restarted

n Offline download
If you perform offline download to the running SCS, the CPU stops temporarily.
Also, IOM download is performed to all I/O modules.
Once an offline download is started, the output values from output modules will conform to the
Figure "Recovery after CPU Module Replacement."

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-7

G2.1.3 Behavior at abnormal calculation

If there are mistakes in the application logic, intended control can no longer be performed.
For the sake of safety, such mistakes must be completely removed before starting the actual
operation, by thoroughly checking and testing in advance.
If there is any mistake that is left undeleted, causing overflow and other abnormal calcula-
tions during execution of the application logic, SCS stops because correct control cannot be
continued. However, by making specifications with a builder, it is possible to avoid stoppage
of SCS and continue the operation (*1). Diagnostic information messages are generated at
occurrence of abnormal calculation and upon recovery respectively.
*1: Supported in the SCS of SCS system program R2.03 or later.

IMPORTANT
The purpose of this function is to temporarily avoid the error conditions of SCS. If an abnor-
mal calculation occurs, review the application logic as soon as possible and modify the logic
such that the abnormal calculation will not recur.

The SCS automatically recovers if the cause of abnormal calculation is removed or resolved.

n Specification of behavior at abnormal calculation

Use the SCS Constants Builder to specify the behavior at abnormal calculation.
If "Continue operations" is specified, the SCS will not fail and will continue operations even if
any of the following abnormal calculations occur.
• Division by zero
• Access to the outside of an array
• Overflow in floating-point calculation
• Overflow in casting
SEE
ALSO For more information about how to specify the behavior upon abnormal calculation with SCS Constants Build-
er, refer to:
C1.2.6, “SCS Constants Builder” on page C1-20

n Occurrence of division by zero

A division-by-zero calculation error occurs under the following conditions and is processed as
follows.

l Occurrence conditions
The denominator is zero in a division of DINT or REAL type data.

l SCS processing at error occurrence

If "SCS fails" is specified in SCS Constants Builder, SCS fails.
But if "SCS continues" is specified and this error occurs, the maximum value of the applicable
type (the maximum negative value if the value is negative) is assigned to the variable of the
operation result. The POU (program) where the calculation error occurred does not stop but
operates until the end.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-8

n Access to the outside of an array

An access to the outside of an array occurs under the following conditions and it is processed
as follows.

l Occurrence conditions
An index of an array variable points to the outside of the array.

l SCS processing at error occurrence

If "SCS fails" is specified in SCS Constants Builder, SCS fails. But if "SCS continues" is speci-
fied and this illegal access occurs, the corresponding POU (function/function block) is stopped
immediately. The POU is executed in the next and subsequent scans as well, but the execu-
tion is stopped at the same location unless the problem is resolved.
The POU (program/function/function block) that called the function/function block in which the
calculation error exists is executed until the end.

l SCS processing at error occurrence when SCS continues the control

(details)
If you specify a value exceeding an array size for an index of an array variable in a user-de-
fined function or user-defined function block described in the ST language, an error of access-
ing outside the array range occurs. The processing of the user-defined function or user-de-
fined function block that caused the error is terminated immediately.
• The return value of the user-defined function is zero (in the case of DINT, REAL or TIME
type) or FALSE (BOOL type).
• In the case of user-defined function blocks, the output parameters that were written be-
fore the occurrence of access to the outside of an array maintain the written values, and
the output parameters that were not written maintain the previous values. The same rule
applies to the local parameters as well.
• The values above are passed to the POU that called the user-defined function or user-
defined function block where the illegal access occurred and the POU is executed until
the end.

n Overflow in floating-point calculation

An overflow in floating-point calculation occurs under the following conditions and is pro-
cessed as follows.

l Occurrence conditions
An overflow occurs in calculation between REAL type operands(*1)
*1: An overflow in integer calculation is not regarded as abnormal calculation.

l SCS processing at error occurrence

If "SCS fails" is specified in SCS Constants Builder, SCS fails.
But if "SCS continues" is specified and this error occurs, the maximum value of the given type
is assigned to the variable of the operation result. The maximum negative value is assigned if
the first operand is negative in the case of addition/subtraction as well as if the signs of first
and second operands are different in the case of multiplication/division.
The POU (program) where the calculation error occurred does not stop but operates until the
end.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-9

n Overflow in casting
An overflow in casting occurs under the following conditions and is processed as follows.

l Occurrence conditions
When casting REAL type data to BOOL, DINT or TIME type, the resultant value exceeds the
maximum value that can be expressed by the variable.

l SCS processing at error occurrence

If "SCS fails" is specified in SCS Constants Builder, SCS fails.
But if "SCS continues" is specified and this error occurs, the following values are assigned to
the variables of the calculation results.

Table G2.1.3-1 Value of the variable to which the result of calculation is assigned
Variable type Value
BOOL TRUE
Maximum value of the DINT type (the maximum negative value if the value is nega-
DINT
tive)
TIME Maximum value of the DINT type

The POU (program) where the calculation error occurred does not stop but operates until the
end.

l SCS processing at error occurrence when SCS continues the control

(details)
• Casting from REAL type variable to DINT type
When casting a value of a REAL type variable to DINT type using the ANY_TO_DINT op-
erator, if the original value is greater than the maximum value that can be expressed by
DINT type, the calculation result is replaced by the maximum DINT value (the maximum
negative DINT value if the original value is negative).
• Casting from REAL type variable to TIME type variable
When casting a value of a REAL type variable to TIME type using the ANY_TO_TIME op-
erator, if the original value is greater than the maximum value that can be expressed as
an unsigned 32-bit integer, the calculation result is replaced by the maximum value of an
unsigned 32-bit integer. Although the TIME type can express up to 24 hours, truncation is
not performed immediately when an overflow occurs; truncation is performed in the sub-
sequent arithmetic calculation. (The TIME type does not take a negative value, but if a
negative value is assigned in ANY_TO_TIME, the value is converted to a signed 32-bit
integer once and then treated as TIME type keeping the bit sequence.)

n Notification of abnormal calculation occurrence/recovery

Occurrence of abnormal calculations and recovery from them are notified via diagnostic infor-
mation messages if SCS continues the control. By using the system function block
(SYS_CERR), whether a calculation error has occurred or not can be handled in the applica-
tion logic.

l Notification of abnormal calculation occurrence

If a calculation error occurs, it is notified by the diagnostic information message (No. 4145)
that indicates an occurrence of abnormal calculation. If calculation errors occur in multiple
POUs (programs), a diagnostic information message is generated for each POU (program).

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.1 Actions taken at fatal error occurrence and recovery procedure > G2-10
If different types of calculation errors occur in the same POU (program) at the same time, a
diagnostic information message is generated for each type of calculation error.

l Re-notification of abnormal calculation occurrence

If the abnormal calculation status continues for a certain period of time or longer, the diagnos-
tic information message notifying the abnormal calculation is generated repeatedly as warn-
ing. The re-warning interval is 10 minutes by default.
The re-warning interval can be changed using SYS_CERR.

l Handling of abnormal calculation status with application logic

The abnormal calculation status can be handled in the application logic by using the system
function block (SYS_CERR). (*1)
*1: SYS_CERR can be used in SCS databases created by SENG of R2.03.00 or later.

l Notification of recovery from abnormal calculation

If the POU (program) that previously caused a calculation error is executed normally until the
end, the calculation error of the POU (program) is regarded to have been cancelled and the
diagnostic information message indicating recovery from abnormal calculation (No. 4146) is
notified. The diagnostic information message indicating recovery is generated for each diag-
nostic information message notifying error occurrence.

n Behavior in test functions

In logic simulation tests and SCS simulation tests, behaviors at abnormal calculation are dif-
ferent from those in the actual system.
SEE
ALSO For more information about the behavior upon occurrence of an abnormal calculation with the test function,
refer to:
“● Actions on abnormal calculation” in “■ Debug and test” in 2., “Logic simulation test operations” in Test
Function Guide (IM 32P04B30-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-11

G2.2 Actions taken at major error occurrence

and recovery procedure
This section explains the operations of an SCS when a major error occurs and the recovery
procedure, for the cases where errors occur in the following locations.
• Input module
• Output module
• Universal type I/O module
• Input channel
• Output channel
• Communication path between the CPU module and input/output modules
• Optical ESB bus repeater devices
• N-IO related hardware
• Safety subsystem communication paths, safety subsystem communication, and fire and
gas communication modules

n Notification of error status

An SCS notifies the application logic of the fact that an error occurred. It also notifies errors to
the user via the SCS State Management Window of the SENG, the Status Display view of the
HIS, and diagnostic information messages.
Since the following processing is performed, the user can create a shutdown application logic
based on these conditions to determine desired output values for each output module.
• The status of channels belonging to the area with the failure becomes BAD.
• The status is reflected in the system function block.
• In the case of errors related to input modules and/or channels, the input value is set to
the "Input value at error occurrence." The "Input value at error occurrence" is provided to
the application logic instead of the actual process value if an error is detected in input
module . The user must define in advance the "Input value at error occurrence" for each
channel with an I/O parameter.
SEE
ALSO For more information about the items to be defined as I/O parameters, refer to:
Appendix 1.3, “Settings for channel items” on page App.1-8

n Recovery from error state

The following subsections explain the recovery measure to be taken for I/O modules when a
major error occurs.
The following operations are needed to recover from an error.
• IOM download
• Output enable operation (for output modules only)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-12

G2.2.1 Actions taken at input module error occurrence and

recovery procedure
If there is a malfunction in an input module hardware, SCS treats it as an input module error.
In the case of a redundant input module, the control rights switches, but the application logic
continues running. This is considered as a minor error. The following explains the operations
performed when an error occurs in the case of modules in single configuration or single oper-
ation status.

n Actions taken at error occurrence

• CPU processing
When an input module fails, the CPU sets the pre-defined values in the I/O parameters to
all channels of the module and force the data status to BAD. The application logic should
handle these changes in the inputs and statuses as errors. In order to prevent the plant
from the fatal damages caused by input module failures, application logics for detecting
the failures and handling the errors should be created.
• Error notification
A module error is notified via a diagnostic information message (alarm class 1). In the
SCS State Management Window on the SENG or the Status Display view on the HIS, the
failed module is shown in red to indicate an error.

n Recovery procedure
1. Investigate the cause of the failure based on the error code shown in the IOM Report.
2. If the input module itself is faulty, replace the module.
If the cause of the failure is on the field side, remove the abnormality on the field side.
3. From the SCS Maintenance Support Tool of the SENG, execute IOM download.
The CPU starts up the input module, and once the input value is acquired normally, the
data status returns to GOOD.
User operation Module replacement IOM download

Logical 1
BAD GOOD
data status 0
Logical
data value Input value at error occurrence Identical to the physical value

Physical 1
BAD GOOD
data status 0

Physical
(*1) Field value
data value

*1: The value varies with the input module type and status.

Figure G2.2.1-1 Input module error

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-13

G2.2.2 Actions taken at input channel error occurrence and

recovery procedure
An input channel error typically occurs in two cases, when there is an error on the field side or
when there is a hardware failure in individual channels of an input module.

n Actions taken at error occurrence

• CPU processing
The CPU sets the input value at error occurrence, which is a value defined by the user in
advance in an I/O parameter, for the faulty input channel and sets the data status to BAD.
Sensor Input Module Output Module Valve

Logic

Input value at
error occurrence

Fault Logic
Action

Action

Input modules fault is taken

account by application logic
as a demand.

Figure G2.2.2-1 Overview of operation when an input channel error is detected

• Error notification
A channel error is notified via a diagnostic information message (alarm class 1). However,
the SCS State Management Window of the SENG and the Status Display view of the HIS
display the module where channel error has occurred in the color that indicates normal.

n Recovery procedure
The type of recovery procedure to be used depends on whether or not the error occurred on
the module side.

l Recovery procedure in the case of error on the module side

If a hardware error occurred in one or more channels of an input module, the input module
needs to be replaced. The module replacing procedure for single module configuration is as
follows:
1. Fix the input values sent to the application logic from the related input variables. Use the
locking operation of the forcing function or maintenance override in order to fix the input
variables. This minimizes the impact at module replacement.
2. After replacing the module, perform IOM download.
The input module starts up normally.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-14
Locking Module Unlocking IOM
User operation IOM download
input variables replacement input variables

1
Logical
data status 0 BAD Hold GOOD

Logical Input value at

error occurrence Hold Physical data value
data value
Faulty channel
Physical 1
BAD GOOD
data status 0

Physical
(*1) Field value
data value

Logical 1
GOOD Hold GOOD
data status 0

Logical
Physical data value Hold Physical data value
data value
Normal channel
Physical 1
GOOD BAD GOOD
data status
0
Physical
Field value (*1) Field value
data value

*1: The value varies with the input module type and status.

Figure G2.2.2-2 Input module replacement (with locking operation)

SEE
ALSO For more information about operations for locking input variables, refer to:
F8.8, “Windows used for forcing of I/O variables” in Engineer's Reference Manual (IM 32P04B10-01EN)

l Recovery procedure in a case where the module is normal

If a failure is discovered in the field or input module connection, remove the cause of the fail-
ure. Removing the cause of the failure allows the channel with the failure status to go back to
using the field value, and the data status changes to GOOD.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-15

G2.2.3 Actions taken at output module error occurrence

and recovery procedure
The result of the application logic processing is set to the logical data and physical data of the
relevant output variables, and this data is then written to each channel of the corresponding
output module via the I/O driver. On the other hand, the CPU acquires the status of the output
module as well as the status of each channel of the output module, and sends diagnostic in-
formation messages or reflects the state information in the system function block used for
channel status display. By using a system function block, module/channel statuses can be
monitored via the application logic. The figure below illustrates the relationship between the
CPU and output module.
CPU Locked status Output disable status

Output module
I/O driver
Logical data Physical data
CH1
Output CH2
Application shutoff switch
logic CH3
Data
update

Composed of data CH8

value and data status

Figure G2.2.3-1 Overview of CPU and output module

n Actions taken at error occurrence

If any output module has failed, the SCS performs failure diagnosis and switches the control
right and/or sends diagnostic information messages. If the control right of the duplexed mod-
ules has been switched, the actions corresponding to a minor error is taken.
If the output module was operating in the single operation mode, the following actions are tak-
en.
• CPU processing
The CPU sets the fail-safe value, which is predefined in an I/O parameter, to the physical
data of each output channel of the faulty output module and places all the output chan-
nels in the Output Disable status. At this point, the operating mode shifts to the Waiting
mode. Writing to the output module is stopped thereafter. The data statuses of all chan-
nels of the output module become BAD. The user can configure the application logic so
that other associated outputs are shut down automatically based on data status changes
of specific output channels to BAD.
• Error notification
A module error is notified via a diagnostic information message (alarm class 1). In the
SCS State Management Window on the SENG or the Status Display view on the HIS, the
failed module is shown in red to indicate an error.

n Recovery procedure
The procedure for recovery from an output module error is as follows:
1. Investigate the cause of the failure based on the error code shown in the IOM Report.
If a system function block for output status display is used, the failure location can be
checked.
2. If the output module itself is faulty, replace the module.
If the cause of the failure is on the field side, remove the abnormality on the field side.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-16
3. From the SCS Maintenance Support Tool of the SENG, execute IOM download.
After the IOM download, the CPU performs startup processing of the output module. If
the startup processing is completed, the output module is recognized as normal and data
update starts. After the module returns to normal, "0" is output for DO modules, while the
tight-shut value is output for AO modules, from all channels of the output modules.
4. Test the output module.
5. From the SCS Maintenance Support Tool of the SENG, perform the output enable opera-
tion.
Output values of the application logic will be output. Once all output channels are placed
in the Output Enable status, the operating mode shifts to the Running mode.
The figure below illustrates the flow from a failure of an output module to the recovery.
Module IOM Output
User operation
replacement download enable operation The logical data value is
set to the result of the
application logic processing.

1
Logical data status BAD GOOD
0

Physical data value Fail-safe value (*2) Logical data value

1
Physical data status BAD GOOD
0

Output modules processing start

Output from IOM (*1) Physical data value

*1: “0” for DO modules, and “0.0 [mA]” for AO modules.

*2: “0” for DO modules, and the tight-shut value for AO modules.

Figure G2.2.3-2 Recovery from output module error with module replacement

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-17

G2.2.4 Actions taken at output channel error occurrence

and recovery procedure
An output channel error typically occurs in two cases, when there is an error on the field side
or when there is a hardware failure in individual channels of an output module. Depending on
the cause of the failure, the Output Shutoff switch in the output module may be activated and
an output module failure may occur, in which case the action take at error occurrence and re-
covery procedure may be different from those applicable to an output channel error.
To prepare for output channel failures, an application logic must be created in advance for
each output channel using a function block for system status indication.
Actuator
Sensor Input Module Output Module
/Valve

Logic
Fault

Node System Action

Status
Function Action
Slot
Block

Figure G2.2.4-1 Description of logic related to output failure

SEE
ALSO For more information about function blocks for system status indication, refer to:
12., “Safety system function blocks” in POU Reference Manual (IM 32P03B20-01EN)

n Actions taken at error occurrence

The actions taken at error occurrence are explained for each of the following two cases: when
the Output Shutoff switch is activated and when an error occurs in a single output channel
without activating the Output Shutoff switch.

l Channel errors accompanied by activation of the Output Shutoff switch

Even when the failure concerns only a certain output channel, the entire output module may
be affected if the Output Shutoff switch in the output module is activated. In this case, "0" and
"0.0 [mA]" are output from all output channels for the DO modules and AO modules, respec-
tively.
The targets of output shutoff operation include dangerous failures (such as DO module chan-
nels are clutched to ON status) and failures where internal module protection is required
(such as overcurrent of AO modules). However, the user can define in an I/O parameter
whether to activate the output shutoff switch for dangerous failures where module protection
is not required by the system.
The user must determine if the failure occurred in the field or in the module, based on the de-
tailed error information provided in the Diagnostic Information window and IOM Report dialog
box.
SEE
ALSO For more information about IOM Report, refer to:
H3.1, “IOM Report of AIO/DIO modules” on page H3-2

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-18

l Operation at occurrence of output channel errors

Errors that do not activate the Output Shutoff switch, such as disconnection on the field side,
are notified as failures of individual output channels. The following operations are performed if
errors occur in individual output channels.
• CPU processing
The CPU sets the fail-safe value, which is predefined in an I/O parameter, in the physical
data of the faulty output channel and places the channel in the Output Disable status. At
this point, the operating mode shifts to the Waiting mode. Other normal output channels
output the result of the application logic processing. The CPU continues updating the da-
ta of the output module.
• Error notification
An output channel error is notified via a diagnostic information message (alarm class 1).
The data status of the faulty output channel is set to BAD. In the SCS State Management
Window on the SENG and the Status Display view on the HIS, the output module is
shown in the color indicating a normal state. The status of each channel can be checked
in the Diagnostic Information window of SCS Maintenance Support Tool of the SENG.

n Recovery procedure
If a channel error occurred, check the following in the SCS State Management Window and
IOM Report dialog box in the SCS Maintenance Support Tool to determine an appropriate re-
covery measure.
• Has the Output Shutoff switch been activated? Does the error concern only one channel?
• Is it a hardware failure in the module or an error on the field side?

l Single channel errors (disconnection and other errors on the field side)
1. Investigate the cause of the failure and recover the field side.
When the output module recovers, a recovery message is output and the fail-safe value,
which was defined by the user in advance, is output from the relevant output channel.
2. After confirming that the output module has recovered to normal, perform the output ena-
ble operation from SCS Maintenance Support Tool of the SENG.
Output values of the application logic will be output.

User operation Complete recovery Output enable

of area with a failure operation The logical data value is
set to the result of the
application logic processing.

Logical 1
data status BAD GOOD
0

Physical
Faulty channel Fail-safe value Logical data value
data value
Physical 1
data status BAD GOOD
0

Output from output module (*1) Physical data value

*1: “0” for DO modules, and “0.0 [mA]” for AO modules.

Figure G2.2.4-2 Recovery from channel errors

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-19

l In the case of errors on a single channel (module channel hardware

failure)
If any of the channels on the module side is judged to be erroneous, the output module must
be replaced. The figure below illustrates the recovery procedure and the data value and data
status at each timing.
User Output lock Module Output lock Output
IOM download
operation operation replacement cancellation enable operation

Logical 1
BAD GOOD
data status 0

Faulty Physical
Fail-safe value (*3) Logical data value
channel data value

Physical 1
BAD GOOD
data status 0

Logical 1
data status 0 GOOD

Normal Physical (*3)

channel data value Logical data value Hold Fail-safe value Logical data value

Physical 1
data status 0 GOOD BAD GOOD

Output modules processing start

Output from
faulty channel Fail-safe value (*1) (*2) Physical data value

Output from Physical data value (*2) Physical data value

normal channel

*1: Fail-safe value (This value may be set to “0” for DO modules and “0.0 [mA]” for AO modules, depending on the failure
condition.)
*2: “0” for DO modules, and “0.0 [mA]” for AO modules.
*3: “0” for DO modules, and the tight-shut value for AO modules.

Figure G2.2.4-3 Recovery from channel errors (with module replacement)

l When the Output Shutoff switch has been activated

If the Output Shutoff switch has been activated, the following values are output from all the
channels of the module.
• DO module: 0
• AO module: 0.0 [mA]
If the Output Shutoff switch has been activated, check the module status color shown in the
SCS State Management Window.
• When the module status is red
If the module status is shown in red, the possible causes of failure are as follows:
• Hardware failure of module channels
• Error on the field side
See the IOM Report and identify which is the case. In both cases, the recovery measures
are the same as the procedures taken after an error concerning an individual channel.
Follow the recovery procedure for errors on the field side or hardware failure depending
on the situation.
• When the module status is blue

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-20
If the module status is shown in blue, the output module is in the startup wait status. In
this case, perform the following recovery procedure.
1. Investigate the cause of the failure and recover the field side.
2. When the recovery procedure has completed, perform the "Start output module" from
the SCS Maintenance Support Tool of the SENG.
The CPU performs the startup processing of the output module. When the output
module recovers to normal status, the data status returns to normal.
3. From the SCS Maintenance Support Tool of the SENG, perform the output enable
operation.
Output values of the application logic will be output.
SEE
ALSO For more information about starting output module operation, refer to:
“n Start output module operation” on page C8-1
For more information about procedures for recovery from an error on the field side, refer to:
“l Single channel errors (disconnection and other errors on the field side)” on page G2-18
For more information about procedures for recovery from a channel hardware failure, refer to:
“l In the case of errors on a single channel (module channel hardware failure)” on page G2-19

n Operation and recovery procedure when overload state is detected

while SDV526 is outputting ON signal
This section explains the operations of the SDV526 module and the recovery procedure for
the cases where an output overload state (*1) has occurred while SDV526 is outputting ON
signals. When SDV526 is in a redundant configuration, signals are output from both mod-
ules. So, the operation on detection of an overload state and the recovery procedure are ex-
plained separately for the active module and standby module.
The operation of SDV526 in a non-redundant configuration is the same as the active module
in a redundant configuration.
*1: An overload state occurs when the connected field device has a fault that causes a short circuit or overcurrent when the out-
put from the module is set to ON.

l Behavior of SCS and recovery procedure when the active module in

redundant configuration or module in non-redundant configuration has
failed
• Behavior
• If an overload state is detected only in the active module of redundant configuration,
the control right is transferred to the standby module and the operation continues.
(*1)If an overload state is detected on both modules, the standby module goes to
IOM Fail and the control right is not transferred.
• The module sets the output signal of the error channel to OFF, and the channel
goes to an Output Disable status.
• The channel is released from the error but it remains in the Output Disable status.
*1: In this case, recover the error module that has become a standby module by carrying out the recovery procedure for a
standby module.

• Recovery procedure
1. Clear the cause of overload state to recover the field device.
2. Use the SCS maintenance support tool on SENG and perform the output enable op-
eration.
This allows the output value of the application logic to be output.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-21

l Behavior of SCS and recovery procedure when the standby module in

redundant configuration has failed
• Behavior
• The output shutoff switch is activated and the standby module goes to IOM Fail.
• In the SCS State Management Window of the SCS maintenance support tool, the
module's status is shown in blue (startup wait status).
• Recovery procedure
1. Clear the cause of overload state to recover the field device.
2. Use the SCS maintenance support tool on SENG and perform the output module
startup operation.
The module starts up and operates as a standby module.

n Behavior of SDV521 or SDV53A and recovery procedure when a

short circuit is detected
This section explains the behavior of the SDV521 or SDV53A module and the recovery proce-
dure for the cases where a short circuit has occurred in the field wiring of the module.
• Behavior
• The module sets the output signal of the error channel to OFF, and the channel goes
to an Output Disable status.
• The channel may be released from the error but it remains in the Output Disable sta-
tus.
• Recovery procedure
1. Clear the cause of short circuit to recover the wiring on the field side.
2. Use the SCS maintenance support tool on SENG and perform the output enable op-
eration.
This allows the output value of the application logic to be output.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-22

G2.2.5 Operations and recovery procedures during the

error occurrence in the universal type I/O module
If there is a malfunction in the hardware of I/O module, an error occurs in universal type I/O
module. If the I/O module is redundant, the control rights are switched, and the application
logic continues running. This is considered as a minor error. The following explains the opera-
tions performed when an error occurs during the single configuration or single operation.

n Operations during error occurrence in the I/O module

Operations during the error occurrence in the I/O module differ depending on the set channel
type.
If the channel of the I/O module is set to input, operations are similar to when an error occurs
in the input module.
If the channel of the I/O module is set to output, operations are similar to when an error oc-
curs in the output module.

n I/O module recovery procedures

Recovery procedures for the I/O module differ depending on the set channel type.
If the channel of the I/O module is set to input, recovery operations are similar to when an
error occurs in the input module.
If the channel of the I/O module is set to output, recovery operations are similar to when an
error occurs in the output module.
SEE
ALSO For more information about operations at input module error occurrence and recovery procedure, refer to:
G2.2.1, “Actions taken at input module error occurrence and recovery procedure” on page G2-12
For more information about operations at output module error occurrence and recovery procedure, refer to:
G2.2.3, “Actions taken at output module error occurrence and recovery procedure” on page G2-15

n Operations at input channel error occurrence and recovery

procedure
Operations and recovery procedures during input channel error occurrence in the universal
type I/O module are the same as those for input channel error occurrence in an input module.
SEE
ALSO For more information about operations at input channel error occurrence and recovery procedure, refer to:
G2.2.2, “Actions taken at input channel error occurrence and recovery procedure” on page G2-13

n Operations at output channel error occurrence and recovery

procedure
This section describes the operations and recovery procedures when an output channel of the
universal type I/O module has failed under the following conditions:
• When the Output Shutoff switch is activated
• When an output channel fails without activating the Output Shutoff switch

l Output shutoff switch of the universal type I/O module

The output shutoff switch in the universal type I/O module is different depending on the set
channel signal type.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-23
• DO channel : DO shutoff switch
• AO channel: I/O shutoff switch
The following shows the channel operations when a DO shutoff switch and I/O shutoff switch
have been activated.
• When DO shutoff switch is activated due to malfunction detection by DO channel:
An error occurs with all DO channels in the universal type I/O module and the output of
the corresponding channels are shut off.
• When an I/O shutoff switch has been activated upon detection of a failure by the AO
channel
An error occurs with all AI (2-wire), AO, DI, and DO channels in the universal type I/O
module and the input and output of the corresponding channels are shut off.

l Channel errors during output shutoff switch operation

When DO shutoff switch in the universal type I/O module is activated during the error occur-
rence, the output of all DO channels in the I/O module becomes 0, even if the error occurs
only in a certain output channel.
Similarly, when an internal I/O shutoff switch in the universal type I/O module is activated, the
outputs of all AO channels in the I/O module become 0.0 [mA] and the output of the DO chan-
nel becomes 0. If the universal type I/O module has an input, the inputs of all AI (2-wire)
channels and DI channels in the I/O module become the input value at error occurrence.
At this time, the system alarm of channel error is sent for the channels that are shut off.
The output shutoff is activated for dangerous failures, such as DO module channels are stuck
in the ON status, and failures where internal module protection is required, such as overcur-
rent of AO modules. However, the user can define in an I/O parameter whether to activate the
output shutoff switch for dangerous failures where module protection is not required by the
system.
The user must determine if the failure occurred in the field or in the module, based on the de-
tailed error information that is provided in the Diagnostic Information window and IOM Report
error.

l Operation at occurrence of output channel errors

Operations and recovery procedures during output channel error occurrence in the universal
type I/O module are the same as those for output channel error occurrence in an output mod-
ule.
SEE
ALSO For more information about operations at error occurrence on an individual output channel and recovery pro-
cedure, refer to:
G2.2.4, “Actions taken at output channel error occurrence and recovery procedure” on page G2-17

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-24

G2.2.6 Actions taken at errors between CPU and Input/

Output module and recovery procedure
Errors between the CPU and input/output module refer to errors on both sides of the SB bus
and errors on both sides of the communication module of a node.
The value output from output channels when a system error is detected must be specified in
advance as a fail-safe value in an I/O parameter.
SEE
ALSO For more information about behavior upon occurrence of an error when using an optical ESB bus repeater,
refer to:
G2.2.7, “Actions taken at error occurrence for optical ESB bus repeater devices” on page G2-26

n Actions taken at error occurrence

If a node error or bus error occurs, both the CPU and input/output module perform actions
taken at error occurrence, respectively.

l CPU processing
• The input value at error occurrence is set for input variables corresponding to all the input
channels that do not respond.
• The fail-safe value is set for the physical data of output variables corresponding to all the
output channels that do not respond, and they are placed in the Output Disable status.
• The input value at error occurrence set for the input variables and the fail-safe value set
for the output variables are specified in I/O parameters.
• The CPU stops updating data of the relevant output module.
SEE
ALSO For more information about the items to be defined as I/O parameters, refer to:
Appendix 1.3, “Settings for channel items” on page App.1-8

l Error notification
• A channel error is notified via a diagnostic information message (alarm class 1). The data
status of all the channels is set to BAD.
• When a node encounters an error, a diagnostic information message regarding the node
error will be generated. When the node returns to normal, a diagnostic information mes-
sage (alarm class 1) is notified to indicate recovery from the I/O module error.

n Recovery procedure
In order to make an output of an output module recover after handling a hardware failure, it is
necessary to perform the output enable operation from SCS Maintenance Support Tool of the
SENG.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-25
User operation Complete recovery Output enable
of area with a failure operation
The logical data value is
set to the result of the
application logic processing
Logical 1
BAD GOOD
data status 0
All channels of an output
module connected to Physical
Fail-safe value Logical data value
an area with a failure data value

Physical 1
BAD GOOD
data status 0

Output from output modules Fail-safe value Physical data value

Figure G2.2.6-1 Output module recovery from communication path errors

TIP Input modules resume using input values from the field and their data status becomes GOOD once the cause
of failure is removed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-26

G2.2.7 Actions taken at error occurrence for optical ESB

bus repeater devices
This section explains the actions taken at error occurrence to the following optical ESB bus
repeater devices.
• SNT401/SNT411 and SNT501/SNT511 (Optical ESB bus repeater modules)
• SNT10D (Unit for optical bus repeater module)

n Actions taken at errors of optical ESB bus repeater/fiber-optic cable

The actions to be taken for a failure of optical ESB bus repeater module or abnormality of fi-
ber-optic cable is the same as the actions taken at an ESB bus error.
• In the event of a failure in one of the optical ESB bus repeater modules in a redundant
configuration, or disconnection or other abnormality in any fiber-optic cable connecting
these modules, a "diagnostic information message indicating a SSB401 error (Message
No. 0065)" is notified as the event of the I/O node connected via the applicable failure lo-
cation.
Example:
0065 SCS0101 SBS Fail FIO NODE 02 SBS RIGHT
CPU Node (Node1)
S S
I I I I I I E E S S
O O O O O O C C C C
M M M M M M 4 4 P P P P
0 0 X X S S
1 1 X X U U
X X

SNT10D
S S S S S S
N N N N N N
T T T T T T
4 4 4 4 4 4 P P
0 0 0 0 0 0 S S
1 1 1 1 1 1 U U

Node2 Node4
S S S S S S S S
I I I I I I N N S S I I I I I I N N S S
O O O O O O T T B B O O O O O O T T B B
M M M M M M 5 5 4 4 P P M M M M M M 5 5 4 4 P P
0 0 0 0 S S 0 0 0 0 S S
1 1 1 1 U U 1 1 1 1 U U

Node3
S S
I I I I I I I I S S
O O O O O O O O B B
M M M M M M M M 4 4 P P
0 0 S S
1 1 U U

: Fiber-optic cable

Figure G2.2.7-1 Connection example

The actions taken at errors of optical ESB bus repeater modules is explained using the above
figure showing a connection example.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-27
Nodes 2 and 3 are accessed via SNT401 and SNT501 modules. Therefore, a failure in any
SNT401 or SNT501 module relaying Node 2/3 will disable communication with Nodes 2 and
3.
• A diagnostic information message indicating an SSB401 error (Message No. 0065) is no-
tified for Nodes 2 and 3 in either of the following cases:
• In the SNT10D shown in the figure, one of the SNT401 modules connecting Nodes 2
and 3 fails.
• One of the SNT501 modules installed in Node 2 fails.
• If both of the SNT401 modules or SNT501 modules fail, a node error occurs in each I/O
node connected via the failed optical ESB bus repeater modules. If both of the SNT501
modules installed in Node 2 fail, Nodes 2 and 3 connected via the SNT501s generate an
error. Similarly if both of the SNT401 module installed in the SNT10D fail, Nodes 2 and 3
also generate an error.
TIP A diagnostic information message indicating an ESB bus error (Message No. 0063) is issued only when an
error occurs in all I/O nodes excluding the CPU node. In a configuration where optical ESB bus repeater mod-
ules are used to provide multiple ESB bus lines, this diagnostic information message (Message No. 0063) is
not issued in the event of an error in only one line.
For example, assume a system configuration that partially uses optical ESB bus repeater modules. Even if
errors are occurred in bus 1 of all I/O nodes those are connected to the ESB bus but are not connected to
fiber-optics, the aforementioned diagnostic information message indicating an ESB bus error (Message No.
0063) is not issued.
The same rule applies when the SEC402 is used to connect nodes to both the upper and lower sides. For
example, the diagnostic information message No. 0063 is not notified if errors occurred in only one side of the
duplicated buses of all I/O nodes connected via the upper connector.

n Actions taken at errors of node power supply

l Installing optical ESB bus repeater modules in a unit for optical bus
repeater module
If optical ESB bus repeater modules are installed in a unit for optical bus repeater module
(SNT10D), set hardware setting switch [1] (installation unit setting DIP switch 1) on the optical
ESB bus repeater modules to "0: Installation in unit for optical bus repeater module." When
the switch is set this way, an error in one of the SNT10D power-supply modules will be noti-
fied as a failure of the I/O nodes connected via the optical ESB bus repeater modules.
• If an error occurs in one of the power-supply modules of the SNT10D in which the optical
ESB bus repeater modules are installed, the optical ESB bus repeater modules of the
corresponding side stop communicating. If the error occurred in the left power-supply
module, the optical ESB bus repeater modules installed in odd-number slots stop com-
munication. If the error occurred in the right power-supply module, the optical ESB bus
repeater modules installed in even-number slots stop communication. Because communi-
cation stops from the optical ESB bus repeater module on one side, "diagnostic informa-
tion messages indicating the SSB401 error (Message No. 0065)" for all I/O nodes con-
nected via the applicable optical ESB bus repeater modules are notified.
• In the event of an error in both of the power-supply modules of the SNT10D in which the
optical ESB bus repeater modules are installed, an error occurs in all I/O nodes connec-
ted via the optical ESB bus repeater modules installed in the applicable SNT10D.

l Installing optical ESB bus repeater modules in a CPU node or I/O node
If optical ESB bus repeater modules are installed in a CPU or I/O node, set hardware setting
switch [1] (installation unit setting DIP switch 1) to "1: Installation in node (safety control unit
or safety node unit)."

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-28
• If SW [1] is set to "1," the optical ESB bus repeater modules will continue to operate with-
out being affected, even if an error occurs in one of the power-supply modules of the
node in which the optical ESB bus repeater modules are installed.
• In the event of an error in both of the power supply modules of the node in which the opti-
cal ESB bus repeater modules are installed, an error occurs in this node and all I/O no-
des connected via the applicable optical ESB bus repeater modules.

IMPORTANT
• When installing optical ESB bus repeater modules in a SNT10D, set the installation unit
setting DIP switch 1 to "0." If this switch is set to "1," an error in one of the power-supply
modules of the SNT10D will not be notified as a failure of the I/O nodes connected via the
optical ESB bus repeater modules.
• When installing optical ESB bus repeater modules in a CPU or I/O node, set the installa-
tion unit setting DIP switch 1 to "1." If this switch is set to "0," an error occurring in one of
the power-supply modules of the CPU or I/O will cause an error in the optical ESB bus
repeater modules on one side.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-29

G2.2.8 Operations during hardware error occurrence

related to N-IO
This section describes the operations when hardware errors related to N-IO occur. It also ex-
plains the recovery monitoring operation for the point where the malfunction occurred.

n N-ESB bus
• Error detection
The SCS performs N-ESB bus diagnosis when accessing the I/O module of the N-IO
node. If one side of N-ESB bus is faulty, it is considered as minor error. If both the sides
of N-ESB buses are faulty, it is considered as major error, and all N-IO nodes that are
connected to the corresponding N-ESB bus are considered as errors.
• Recovery monitoring
The SCS monitors the recovery status of N-ESB bus periodically. When the bus has re-
covered, the N-ESB bus status in the SCS returns to normal. Then, the SCS switches
over both buses alternately while communicating with NIU.

n N-IO node
• Error detection
The SCS monitors the status of N-ESB bus module periodically. If one side of N-ESB bus
module is faulty, it is considered as minor error If both the sides of N-ESB bus module are
faulty, the corresponding N-IO node and all N-IO nodes under it are considered as major
errors. The bus types that connect the subordinate N-IO nodes, irrespective of whether
they are N-ESB bus or optical ESB bus, are considered as major errors.
The following figure shows the effective range of the N-IO node when it is abnormal.
S S S S SCU
2 2 S S C C S S S2SC70D
E E E E
N N C C P P P P
4 4 4 4 4 4 W W
0 0 0 0 6 6 4 4
x x x x 1 1
8 8
S S x x
2 2

N-ESB bus

S S S S S S
2 2 2 2 2 2
E E P P E E P P E E P P
Failure N N S S N N S S N N
5 5 5 5 5 5 S S
0 0 M M 0 0 M M 0 0 M M
1 1 1 1 1 1

N N N N N N
- - - - - -
I I I I I I
O O O O O O

Node 1 Node 2 Node 3

N-IO N-IO N-IO

Figure G2.2.8-1 Effective range of the abnormal N-IO node

Node2 and Node3 communicate with the SCS through S2EN501 of Node1. If S2EN501
of Node1 that communicate with the SCS is faulty at both sides or has power failure, the
communication to all I/O module of Node 2 and Node 3 is disabled.
• Recovery monitoring
The SCS periodically monitors the recovery of abnormal N-IO node. When the N-IO node
has recovered, the N-IO node status in the SCS returns to normal.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-30

n Power supply module of the N-IO node

• Error detection
The SCS monitors the status of the power supply module of the N-IO node periodically. If
the power supply module is faulty at one side, the N-IO node is considered to have a mi-
nor error. If the power supply module is faulty at both sides, the N-IO node is considered
to have a major error.
• Recovery monitoring
The SCS monitors the recovery of the power supply module of the abnormal N-IO node
periodically. When the module has recovered, the power supply module status in the SCS
returns to normal.

n F-SB bus
• Error detection
The SCS performs diagnosis of the F-SB bus between NIU and I/O unit when accessing
the I/O module of the N-IO node. If one side of F-SB bus is faulty, it is considered as mi-
nor error. If both sides of F-SB bus are faulty, the I/O modules of the corresponding NIU
becomes error, and it is considered as a major error.
• Recovery monitoring
The SCS monitors the recovery status of F-SB bus periodically. When the bus has recov-
ered, the F-SB bus status in the SCS returns to normal. Then, NIU communicates with
the I/O module by using both buses simultaneously.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-31

G2.2.9 Operations at fire and gas communication error

occurrence and recovery procedure
This section explains the operations upon occurrence of an S2LP131, fire and gas device, or
fire and gas communication error and recovery procedure therefor.
The CPU sets the communication data to the value upon error specified by the user and
changes the data status to BAD with the timing described below. The timing of status change
will vary between data used with safety communication and data used with interference-free
functions.
• Data used with safety communication
The timing at which the Safety Layer of the SCS uses the Safety Measure of PROFIsafe
and detects an error
• Data used with interference-free functions
The timing at which the S2LP131 uses the communication status of PROFINET and de-
tects an error of the communication path

n Operations at error occurrence along path between the CPU and

S2LP131 and recovery procedure
Errors along the path between the CPU and S2LP131 are errors of the FIO node and errors
on both sides of the SB bus and ESB bus from the CPU to the S2LP131. This sections ex-
plains the operations at error occurrence and recovery procedures therefor.

l Operation at error occurrence

• CPU processing
The CPU sets values specified in advance as I/O Parameters by the user to all communi-
cation data in the range of the error. The user can specify in advance whether to use the
value immediately before the error is detected or to use the preset “input value at error
occurrence.”
• Error notification
The CPU notifies a message containing diagnosis information for the FIO node error. In
addition, an IOM error and recovery diagnosis message is notified upon recovery. The
CPU sets the data status of all communication data in the range of the failure to BAD
while the error is occurring.
In the SCS State Management window of SENG or the Status Display view of HIS, the
location of the error is shown in red. This will switch to green upon recovery from the er-
ror.

l Recovery procedures
Remove the cause of the error. After removing the cause of the error, you do not need to per-
form output enable operation from SENG.

n Operations at S2LP131 error occurrence and recovery procedure

S2LP131 errors are hardware failures, communication board errors, disconnection from the
node, and configuration errors.

l Operation at error occurrence

• CPU processing
The CPU sets values specified in advance as I/O Parameters by the user to all communi-
cation data obtained via the S2LP131. The user can specify in advance whether to use
the value immediately before the error is detected or to use the preset “input value at er-
ror occurrence.”

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-32
• Error notification
The CPU notifies a message containing diagnosis information for the IOM error. The CPU
sets the data status of all communication data obtained via the S2LP131 to BAD while
the error is occurring.
In the SCS State Management window of SENG or the Status Display view of HIS, the
S2LP131 is shown in red. This will switch to green upon recovery from the error.

l Recovery procedures
Remove the cause of the error. After removing the cause of the error, you do not need to per-
form output enable operation from SENG.

n Operations at error occurrence along path between the S2LP131

and fire and gas devices and recovery procedure
Errors along path between the S2LP131 and fire and gas devices are S2LP131 port errors,
YFGW410 failures, path errors between S2LP131 and YFGW410, and path errors between
YFGW410 and GS01.
SEE
ALSO For more information about operations at safety communication error occurrence and recovery procedure, re-
fer to:
“n Operations at error occurrence regarding safety communication between the CPU and fire and gas
devices and recovery procedure” on page G2-32

l Operation at error occurrence

• CPU processing
The CPU sets values specified in advance as I/O Parameters by the user to data used
with interference-free functions in the range of the error. The user can specify in advance
whether to use the value immediately before the error is detected or to use the preset “in-
put value at error occurrence.”
• Error notification
The CPU notifies a message containing diagnosis information indicating a communication
error of the S2LP131. The CPU sets the data status of the data used with interference-
free functions in the range of the error to BAD while the error is occurring.
In the SCS node status display dialog box of HIS, "1C" is shown in red. The display will
disappear upon recovery from the error.

l Recovery procedures
Remove the cause of the error. After removing the cause of the error, you do not need to per-
form output enable operation from SENG.

n Operations at error occurrence regarding safety communication

between the CPU and fire and gas devices and recovery procedure
Errors regarding safety communication are CRC errors between the CPU and fire and gas de-
vices and errors such as timeouts.

l Operation at error occurrence

• CPU processing
The CPU sets values specified in advance as I/O Parameters by the user to data used
with safety communication in the range of the error. The user can specify in advance
whether to use the value immediately before the error is detected or to use the preset “in-
put value at error occurrence.”
• Error notification

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.2 Actions taken at major error occurrence and recovery procedure > G2-33
The CPU notifies a message containing diagnosis information for the fire and gas com-
munication error. The CPU sets the data status of the data used with safety communica-
tion of fire and gas devices to BAD while the error is occurring.
In the SCS node status display dialog box of HIS, "1C" is shown in red. The display will
disappear upon recovery from the error.

l Recovery procedures
Remove the cause of the error. After removing the cause of the error, you do not need to per-
form output enable operation from SENG.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<G2.3 Actions taken at minor error occurrence and recovery procedure > G2-34

G2.3 Actions taken at minor error occurrence

and recovery procedure
A minor error does not affect the application logic execution function itself. For example, "one-
side" failure of a redundant hardware applies to this.
When an error occurs in a device that has been configured for dual redundancy, the control
rights get transferred to the device on standby so processing can continue. Such errors are
regarded as minor. After switching the control right, the same operation as for single configu-
ration system is performed. The fact that the control right is switched due to a failure is noti-
fied via a diagnostic information message. Since the SCS can continue controlling in this
case, the data status is not changed nor is any error status notification to system function
blocks performed. Confirm that the failed hardware is switched to standby side and then re-
place the failed hardware.

IMPORTANT
Observe the following precautions when one of the redundant pair of I/O modules has failed
and you must fix it:
• If you pull out the failed I/O module, do not insert it again.
• When you replace the I/O module, do not insert an I/O module that is not assured as nor-
mal.
If you do not observe these precautions, the field side may be adversely affected if the inser-
ted module is faulty.

SEE
ALSO For more information about the procedures for replacing ProSafe-RS devices, refer to:
I1.2, “Maintenance for ProSafe-RS equipment” on page I1-9

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H. Monitoring the SCS status > H-1

H. Monitoring the SCS status

You can monitor the SCS status from the following windows:
• The SCS Status Overview window can be used to view the status of SCSs that are regis-
tered in the RS project.
• The State Management window can be used to check the detailed status of the specified
SCS.
• The IOM Report can be used to check the detailed status of I/O modules.
• The Diagnostic Information window can be used to check the diagnostic information mes-
sages that are generated in SCS.
TIP • In this manual, the safety control unit and the safety node unit are called as CPU node and FIO node,
respectively.
• In this document, I/O shutoff switches and DO shutoff switches of the universal type I/O module and are
referred to as an output shutoff switch.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1. SCS status display> H1-1

H1. SCS status display

The status of SCS is displayed in the following windows:
• SCS Status Overview window
• SCS State Management window
This section describes how to display and operate these windows.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.1 SCS status overview> H1-2

H1.1 SCS status overview

The SCS Status Overview window displays a list of SCSs assigned to the given RS project. In
addition to the current operating conditions of SCSs, it also displays if there is any diagnostic
information messages from any of the SCS diagnostic functions; it is easy to know which SCS
has errors.

n How to display the SCS Status Overview window

The SCS Status Overview window can be launched using the following two methods:
• From the Launcher menu of SCS Manager
• From the [Start] menu of Windows

l From the Launcher Menu of SCS Manager

1. Select [Maintenance] from the [Tools] menu of SCS Manager.
The Maintenance Launcher menu appears.
2. Select [SCS Status Overview] from the Maintenance Launcher menu.
3. Enter your password.
Password entry is not required when the Access Control and Operation History Manage-
ment Package is used.
The SCS Status Overview window is displayed.

l From the Start menu of windows

1. Start SCS Status Overview.
2. Enter your password.
When Windows authentication mode is set, enter a password. When the Access Control
and Operation History Management Package is applied, enter the name and password of
the engineer.
The SCS Status Overview window is displayed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.1 SCS status overview> H1-3

n SCS Status Overview window structure

RS project name Toolbar Domain number Status of control bus with SENG

SCS Status Overview

File View Window Tool

MYRSPJT Domain:01 Vnet/IP 1 Vnet/IP 2

Station SCS Status CPU Status Comment

 SCS0101 Ready Ready
SCS0102 R-Fail

Diagnostic
information mark Station name SCS status CPU status Station Comment

Figure H1.1-1 SCS Status Overview window structure

The components of the window are explained as follows.

n Toolbar
The following buttons are provided on the toolbar.

Table H1.1-1 Toolbar buttons

Button Name Description
Open Call up Project Selection dialog box.

Diagnostic Information Call up Diagnostic Information window.

Time Setup Call up Adjust Time dialog box.

(*1)
Setup Tool Call up Setup Tool.

*1: Not available when using SCS Simulator.

l Call up Project Selection dialog box

Click this button to open the Project Selection dialog box, where you can switch between RS
projects.

l Call up Diagnostic Information window

Click this button to open the Diagnostic Information window related to the SCS selected in the
SCS Status Overview window. The Diagnostic Information window allows you to perform con-
firmation, deletion, printing and saving to file operations on the diagnostic information man-
aged by SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.1 SCS status overview> H1-4

l Call up Adjust Time dialog box

The Adjust Time dialog box allows you to set the system date and time. In the case of a
CENTUM integration structure, the system time on the CENTUM side is also changed.
But in the following cases, the system time cannot be changed:
• When an SNTP server is connected on the Vnet/IP network and the system time is
synchronized with the standard time, the system time cannot be changed from the SENG.
• When a V net router style below S3 is used, the system time of the Vnet/IP network can-
not be changed from the SENG in the V net domain.
SEE
ALSO For more information about time setting, refer to:
I3., “Setting system time” on page I3-1

l Call up Setup Tool

Setup Tool allows you to customize the operating environment of SCS Maintenance Support
Tool.
SEE
ALSO For more information about setup tool, refer to:
A5.3, “Customization of the SCS Maintenance Support Tool window” in ProSafe-RS User’s Guide (IM
32P01B10-01EN)

n System status list view

This view shows a list of operation information of SCSs (whole status and CPU status) in a
RS project. The operating status of the control bus connected from the SENG is displayed in
the upper part of the list view.
Diagnostic information marks are displayed to the left of SCS names for which diagnostic in-
formation messages have been generated. If any of the diagnostic information messages is
not acknowledged, the diagnostic information marks flash.
If you double-click a line of an SCS in the Station name column, the SCS State Management
window for the corresponding SCS opens.

Table H1.1-2 Items displayed in System status list view

Item Description
RS Project name RS project name
Domain number Domain number to which the local SENG belongs
V net or Vnet/IP status Status of the control bus to which the local SENG is connected
Diagnostic information Presence of diagnostic information messages and their acknowledgement sta-
mark tus
Station name Station name of an SCS
SCS status Status of an SCS
CPU status Status of the SCS’ CPU
Station comment SCS station comments

l Control bus status

Indicates the name and status of the control bus on which the SENG is connected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.1 SCS status overview> H1-5
Table H1.1-3 Display of V net or Vnet/IP status
Status Display Display color
Normal Green
Error × Red

l Diagnostic information mark

These are used to indicate whether there are any diagnostic information messages, and their
acknowledgement status.

Table H1.1-4 Display of diagnostic information marks

Status Display Display color
Indicates that the diagnostic information messages exist.
Red
Flashes if unacknowledged messages exist.
Indicates that all messages are acknowledged and errors ex-
Red
ist in nodes or input/output modules.
Indicates that all messages are acknowledged and deleted,
(No display)
and no error exists in nodes or input/output modules.

l SCS status
Indicates the status of entire SCS.

Table H1.1-5 Display of SCS status

Status Display Display color
Normal Ready
Copying Copy Blue
Communication Error Communication Error (*1) Red
SCS Simulator is running Test
*1: "Communication Error" is displayed when SCS stops. It indicates that the connection for communication is not established.

l CPU status
Indicates status of SCS CPU.

Table H1.1-6 Display of CPU status

Status Display Display color
Normal. CPUs on both sides are normal in the case of duplex
Ready
configuration.
Abnormal. CPUs on both sides are abnormal in the case of du-
Fail Red
plex configuration.
CPU on the right side is abnormal in the case of duplex config-
R-Fail Red
uration
CPU on the left side is abnormal in the case of duplex configu-
L-Fail Red
ration

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-6

H1.2 SCS State Management window

The SCS State Management window displays detailed information about the operating status
of CPU modules and input/output modules for a single SCS. If there is an error, the erroneous
area is shown using a different color. It also displays whether or not there are any messages
that have not been acknowledged.
The SCS State Management window allows you to perform the following operations:
• IOM Download operation, Output Enable Operation and Start Output Module operation
• Display of detailed information of each input/output module

n How to display the SCS State Management window

The SCS State Management window can be launched using the following two methods:
• From the Launcher menu of SCS Manager
• From the SCS Status Overview window

l From the Launcher menu of SCS Manager

1. From the menu bar of SCS Manager, select [Tools] > [Maintenance].
The Maintenance Launcher menu appears.
2. Select [SCS State Management] from the Maintenance Launcher menu.
3. Enter your password.
Password entry is not required when the Access Control and Operation History Manage-
ment Package is used.
The SCS State Management Window is displayed.
SEE
ALSO For more information about security-related operations of the SCS Maintenance Support Tool, refer to:
B5., “Security of SCS Maintenance Support tool” in ProSafe-RS User’s Guide (IM 32P01B10-01EN)

l From the SCS Status Overview window

Double-click the station name of an SCS in the SCS Status Overview window. The SCS State
Management window for that SCS appears.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-7

n SCS State Management window structure

RS project name Domain number Hardware Configuration Tree View
Diagnostic
information mark Control bus status Component/Module List View

Upper
part

Lower
part

Figure H1.2-1 SCS State Management window structure

TIP SEC401, SEC402, SNT401, SNT411, SNT501, SNT511 and SNT10D are not displayed.

The components in the window are explained as follows.

n Toolbar
The following buttons are provided on the toolbar.

Table H1.2-1 Toolbar buttons

Button Name Description
Open Call up Project Selection dialog box.

Diagnostic Information Call up Diagnostic Information window.

Common Diagnostic Call up Diagnostic Information window (common).

Information
IOM Load Call up IOM Download tool
(*1)
Start output module Output Module Start
(*1)
Disable Maintenance Call up the NIU maintenance port setting tool. To dis-
(*1) port able the port.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-8
Table H1.2-1 Toolbar buttons (Table continued)
Button Name Description
Enable Maintenance Call up the NIU maintenance port setting tool. To ena-
(*1) port ble the port.
I/O Channel Status Call up I/O Channel Status dialog box.

System Report Call up System Report dialog box.

(*1)
Time Setup Call up Adjust Time dialog box.
(*1)
Setup Tool Call up Setup Tool.

SCS Status Overview Call up SCS Status Overview window.

*1: Not available when using SCS Simulator.

l Call up Project Selection dialog box

Click this button to open the Project Selection dialog box, where you can switch between RS
projects.

l Call up Diagnostic Information window

Click the following buttons to open the Diagnostic Information window. The icon on the button
changes if there are diagnostic information messages.
• [Diagnostic Information] Button
This button calls up all diagnostic information messages from the hierarchy tree selected
in Hardware Configuration Tree View, to be displayed in the Diagnostic Information win-
dow. For example, if you click this button when selecting a node, all diagnostic informa-
tion messages common to this node and those for all input/output modules for the node
and nodes below it are displayed together.
• [Common Diagnostic Information] Button
This button calls up only diagnostic information messages for the tree selected in Hard-
ware Configuration Tree View to be displayed. For example, if you click this button when
selecting a node, only diagnostic information messages common to this node will be dis-
played in the Diagnostic Information window.
The [Common Diagnostic Information] button can be used when a station or a node is se-
lected on Hardware Configuration Tree View.
The Diagnostic Information window allows you to perform acknowledgement, deletion, print-
ing and saving to file operations on diagnostic information managed by the SCS.
SEE
ALSO For more information about Diagnostic information window, refer to:
H5.2, “Diagnostic Information window” on page H5-3

l Call up IOM Download tool

The IOM Download tool is used to recover when input/output modules are replaced or input/
output modules fail.
If the user does not have the authority to write, the [IOM Load] button is grayed out and disa-
bled.
SEE
ALSO For more information about IOM download tool, refer to:
I4.5, “IOM Download tool” on page I4-44

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-9

l Output module start

l Call up I/O Channel Status dialog box

The I/O Channel Status dialog box displays the statuses of the channels of all input/output
modules of the SCS in list format. This dialog box also allows you to enable the output of
channels whose output are disabled (Output Enable Operation).
SEE
ALSO For more information about Output enable operation, refer to:
C8., “Output enable operation” on page C8-1
For more information about I/O channel status, refer to:
H4., “Displaying I/O channel status” on page H4-1

l Call up NIU maintenance port setting tool

The NIU maintenance port setting tool is called to enable or disable the NIU maintenance
port. It can be called after selecting the following components in Hardware Configuration Tree
View. You can also called it from menu bar.

Table H1.2-2 Setting method to enable or disable the NIU maintenance port
Objective How to start the tool
Disable the maintenance port of all the nodes of Select the station from Hardware Configuration Tree
each station collectively. View, and then select [Operation] > [Disable Mainte-
nance port]. Or, click the [Disable Maintenance port]
button on the tool bar.
Disable the maintenance ports on a per node basis Select the N-IO node from Hardware Configuration
Tree View, and then select [Operation] > [Disable
Maintenance port]. Or, click the [Disable Mainte-
nance port] button on the tool bar.
Enable the maintenance ports on a per node basis Select the N-IO node from Hardware Configuration
Tree View, and then select [Operation] > [Enable
Maintenance port]. Or, click the [Enable Maintenance
port] button on the tool bar.

l Call up System Report dialog box

The SCS Report dialog box displays the status of the displayed SCS as character strings.
IOM Report dialog box also displays the status of the displayed input/output modules. This
function allows printing reports and save them in files in text format.
SEE
ALSO For more information about system reports, refer to:
H2., “System reports” on page H2-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-10

l Call up Adjust Time dialog box

Click this button to open the Adjust Time dialog box.
SEE
ALSO For more information about time setting, refer to:
I3., “Setting system time” on page I3-1

l Call up Setup Tool

l Call up SCS Status Overview window

Click this button to return to the SCS Status Overview window.

n Hardware Configuration tree view

This view displays the hardware configuration of a single SCS in tree format. The upper part
of the tree view shows the status of the control buses connected to the SCS.
The CPU node displays the CPU module, power supply module and I/O module. The I/O
module of the CPU node also includes the N-ESB bus coupler module. The FIO node dis-
plays the power supply module and the I/O module. The N-IO node displays the power supply
module, I/O module and N-ESB bus module. If there is any diagnostic information message
for any hardware components displayed in tree format, a diagnostic information mark is dis-
played at the left of each component. Since diagnostic information marks are displayed on the
alarm layer, if an error is detected in an I/O module, a diagnostic information mark will also
appear in the I/O node and SCS of the upper components. In this way, the user can simply
display the upper components to check whether any lower diagnostic information messages
exist in the alarm layer. If an error is detected in the upper component, the lower components
show the status that is obtained before the error has occurred in the upper component.
In the case of dual redundant input/output modules, diagnostic information messages for both
sides are displayed regardless of which input/output module you select.
If there are any diagnostic information messages that have not been acknowledged, the diag-
nostic information mark flashes.
Double-click the name of component or input/output module to display detailed information of
the selected item in Component/Module List View.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-11

SCS0133
Component number

CPU Node(1) CB000001

IOM

N-ESB bus coupler module model name(1)

N-ESB bus coupler module model name(2)

CPU(L)
CPU(R)
PSU(L) N-ESB bus coupler
PSU(R) module is mounted at the
Component number I/O slot in CPU node.
I/O Node(2) CB000001
FIO node
I/O Node(3) CB000001 N-IO node

N-IO Node(1) CB000002

Component number
IOM

Unit(1)

N-IO module model name(1)

N-IO module model name(2)

Unit(2)

N-ESB bus module model name(L)

N-ESB bus module model name(R)
PSU(1)
PSU(2)
N-IO Node(2) CB000002

Figure H1.2-2 Hardware Configuration tree view

Table H1.2-3 Items displayed in Hardware Component tree view

Display items Description
RS Project name RS project name
Domain number Domain number to which the SCS belongs
V net or Vnet/IP Status Status of the control bus to which the SCS is connected
Diagnostic information mark Presence of diagnostic information messages and their
acknowledgement status
Component name or module name Node or I/O module names (*1)
*1: If ALR111M is set when the I/O module is defined, ALR111 is displayed in the SCS State Management window.
Similarly ALR121 is displayed for ALR121M and ALE111 is displayed for ALE111M.

l Control bus status

It displays the status of the control bus where the SCS is connected. The following table
shows the relationship between the status, display, and display colors of the control bus.

Table H1.2-4 Display of V net or Vnet/IP status

Status Display Display color
Normal Green
Error × Red

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-12

l Diagnostic information mark

The relationship between the status, display, and the display colors of the diagnostic informa-
tion mark is shown in the following table.

Table H1.2-5 Display of Diagnostic information mark

Status Display Display color
Indicates that diagnostic information messages exist. Flashes if un-
Red
acknowledged messages exist.
Indicates that all messages are acknowledged and errors exist in
Red
nodes or input/output modules.
Indicates that all messages are acknowledged and deleted, and no
(No display)
error exists in nodes or input/output modules.

l Component name or module name

The relationship between component name or module name and the display colors is shown
in the following table.

Table H1.2-6 Display of component name or module name status

Status Display Remark
color
When using SCS Simulator, the components and modules are displayed as
Normal
Normal even though they are not physically installed.
Error Red
Standby Yellow
Hardware This status indicates that an APC is being executed in the case of CPU mod-
Blue
ready ule, and information is being copied from the control side to the standby side.
This status indicates that information is being copied from the control side to
Copying Blue
the standby side in the case of SCS.
Waiting for In the case of output module, this status indicates that the output module is
Blue
startup waiting for startup.

Component names or module names are displayed with one of the following characters at-
tached to the right of the name.

Table H1.2-7 Characters attached to the component name and module name
Component name, module Displayed char- Attached character
name. acters
CPU node CPU Node Node number (1)
FIO node I/O Node Node number (2) to (14)
N-IO node N-IO Node Node number (1) to (32)
Component Number Set component number
(L) or (R) for the CPU node. Automatically attached after
CPU module CPU the redundancy is determined from the SCS station mod-
el.
(L) or (R) for the CPU node and FIO nodes (1) or (2) for
Power supply module PSU
N-IO nodes
Unit Unit Unit number (1) to (6) for N-IO nodes
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-13
Table H1.2-7 Characters attached to the component name and module name (Table continued)
Component name, module Displayed char- Attached character
name. acters
For the CPU node and FIO nodes, the module model and
slot number (1) to (8) are attached under IOM. For N-IO
Input/output module
nodes, the module model and (1) to (2) are attached un-
der Unit.
For the CPU node and FIO nodes, the module model and
ESB bus module
control bus number (1) or (2) are attached.
For the CPU node, the module model and control bus
N-ESB bus coupler module
number (1) or (2) are attached.
For N-IO nodes, the module model and (L) or (R) are at-
N-ESB bus module
tached.

n Upper part of Component/Module list view

The following items are always displayed in the upper part of the list view.
• SCS Status
• CPU Status
• Operating mode
• SCS security level
• Number of variables locked by the forcing function
• Number of stations locked in the SCS Link Transmission
• Subsystem Communication Data Locking/Unlocking
• Number of locked stations in the inter-SCS safety communication
• Number of safety subsystem communication I/O locks (only for S2SC70)
• Status of the NIU maintenance port (only for S2SCS70)

n Lower part of Component/Module list view

The lower part of the list view displays detailed information about the operating status of the
component or module selected by double-clicking in Hardware Configuration Tree View.
Content enclosed in [ ] indicates an index.
The display for each item varies depending on the component or input/output module selec-
ted in Hardware Configuration Tree View.

l Lower part of list view when a station is selected

The following table shows the contents that are displayed in the lower part of the list view
when a station is selected.

Table H1.2-8 Status display (When a station is selected)

Item Description
Station name Station name of the SCS
Station comment Station comments for the SCS
Station Address Shown in the form of "Domain number-Station number".
Station Type SCS station type
System Revision Release number of the system program loaded on the SCS
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-14
Table H1.2-8 Status display (When a station is selected) (Table continued)
Item Description
SCS Status Status of SCS
CPU Status Status of CPU of the SCS
[Ready] is displayed while in the normal state, and [Writing] (blue) is displayed if
Flash Access
the flash memory is being written.
Date and Time when the POU DB, Variable DB, System DB and Integration DB
Generation Date/Time
were created.
Application time (*1) Actual scan period (msec), set scan period (msec), and program execution time
(*2) (%)
CPU Idle Time (*1) Idle time (sec)
Communication Load
Average value (%) and current value (%)
(*1)
Control Status Displayed as [Run] when running and as [Stop] (red) when stopped.
Operating Mode The operating mode of SCS is displayed in the corresponding color.
Displays the security level of SCS. The security level is displayed in blue for Levels
Security Level
1 and 0.
Displays the number of variables that have been locked using the forcing function.
Number of Forcing
The number is displayed in blue if one or more locked variables exists.
Number of stations
Displays the number of stations being locked in the SCS Link Transmission. The
locked in the SCS Link
number and [Stn] are displayed in blue if there is one or more locked stations.
Transmission
Number of locked sta-
Displays the number of stations that are locked in the inter-SCS safety communica-
tions in the inter-SCS
tion. The number and "Stn" are displayed in blue if locked stations exist.
safety communication
[YES](blue) is displayed if the subsystem communication data are locked and [No]
Lock of subsystem
is displayed if the subsystem communication data are not locked. If the SCS does
communication data
not have any communication module, [No] is displayed.
Number of safety sub- Displays the number of communication definitions locked with safety subsystem
system communication communication. The number is displayed in blue if one or more locked communica-
I/O locks (*3) tion definitions exist.
Status of the NIU When NIU maintenance port is enabled, "Enable" is displayed in red; when it is dis-
maintenance port (*3) abled, "Disable" is displayed.
*1: When SCS Simulator is running, the program execution time is displayed as 100, and CPU idle time and communication load
are displayed as 0.
*2: In the case of SCS with R2.02 or earlier system program, actual scan period is not displayed. The set scan period is dis-
played in the position of actual scan period.
*3: Displayed only for S2SCS70.

• SCS Status

Table H1.2-9 Display of station status

Status Display Display color
Normal Ready
Copying Copy Blue
Communication Error (*1) Communication Error Red
SCS Simulator is running Test
*1: "Communication error" is also displayed when SCS is stopped.

• CPU Status

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-15
Table H1.2-10 Display of CPU status
Status Display Display color
Normal. CPUs on both sides are normal Ready
in the case of duplex configuration.
Abnormal. CPUs on both sides are ab- Fail Red
normal in the case of duplex configura-
tion.
CPU on the right side is abnormal in the R-Fail Red
case of duplex configuration
CPU on the left side is abnormal in the L-Fail Red
case of duplex configuration

• Operating Mode

Table H1.2-11 Display of Operating mode

Status Display Display color
Stop status (*1) Stop Red
Offline Downloading (*1) Loading Red
Initialized status Initial Red
Waiting for output enable request Waiting Blue
Operating Running
*1: Normally, these states are not displayed.

l Lower part of list view when a CPU node is selected

The following table describes the contents that are displayed in the lower part of the list view
when the CPU node is selected.

Table H1.2-12 Status display (when a CPU node is selected)

Item Description
Node Number Displays the node number (always = "1").
Component Number The component number is displayed. (*1)
Node Comment Displays comments for the node.
[Ready] is displayed when the status is normal, [Fail] (red) is displayed if
Node Status the status is abnormal, and [Communication Error] (red) is displayed if the
communication status is abnormal.
Displayed only when IRIG-B time synchronization is applied. [Ready] is
IRIG-B Status displayed if the status is normal and [Fail] (red) is displayed if the status is
abnormal.
Indicates the time synchronization status. [Vnet/IP] is shown if not
Time Sync synchronized with the time on the SNTP server; [SNTP] is shown if
synchronized.
Intake Air Temperature
Exhaust Air Temperature
Battery Temperature [Ready] is displayed when the status is normal and [Fail] (red) is displayed
SCU Fan (*2) if the status is abnormal.

Battery Status
ESB Bus Status (*3)
*1: Displayed only for S2SCS70.
*2: Not available if the model of SCS does not have a fan.
*3: Not displayed for the SCS that is the CPU node only or for S2SC70.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-16

l Lower part of the list view when the CPU module of the CPU node is
selected
The following table shows the contents that are displayed in the lower part of the list view
when the CPU module of the CPU node is selected.

Table H1.2-13 Status display (When a CPU module is selected)

Item Status Display Display color
Normal Ready
Error Fail Red
Standby Stand-By Yellow
CPU Status
Hardware ready Hard Ready Blue
Communication Er-
Communication Error Red
ror
Normal Ready
Bus Status
Error Fail Red

l Lower part of list view when a CPU node power supply module is selected
The following table shows the contents that are displayed in the lower part of the list view
when the power supply module of the CPU node is selected.

Table H1.2-14 Contents of the status display (when PSU is selected)

Item Status Display Display color
Normal Ready
Error Fail Red
PSU Status
Communication Er-
Communication Error Red
ror
Normal Ready
24 V DC Power Supply Status
Error Fail Red

l Lower part of the list view when the N-ESB bus coupler module of the CPU
node is selected
The following table shows the contents that are displayed in the lower part of the list view
when the N-ESB bus coupler module of the CPU node is selected.

Table H1.2-15 Contents of the status display (when the N-ESB bus coupler module of the CPU node is
selected)
Item Status Display Display color
I/O module model Input module model
I/O module status Normal Ready
Error Fail Red
Transmission error Communication Error Red
Bus status Normal Ready
Error Fail Red

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-17

l Lower part of the list view when the representative I/O module of the CPU
node is selected
In the CPU node, the status of the I/O module or N-ESB bus coupler module can be displayed
in the representative I/O module. The following table shows the contents that are displayed in
the lower part of the list view when the representative I/O module with N-ESB bus coupler
module installed is selected in the CPU node.

Table H1.2-16 Contents of the status display (when the representative IOM of the CPU node is selec-
ted: N-ESB bus coupler module)
Item Status Display Display color
Representative I/O module status Normal Ready
Error I/O Fail Red
Transmission error Communication Error Red
Representative channel status Normal Ready

l Lower part of the list view when an FIO node is selected

The following table shows the contents that are displayed in the lower part of the list view
when an FIO node is selected.

Table H1.2-17 Status display (when an I/O node is selected)

Item Description
Node Number Displays the node number.
Component Number Content number is displayed (*1)
Node Comment Displays comments for the node.
Node Status Displays either normal or abnormal.
*1: When an FIO node is selected in S2SC70

• Node Status

Table H1.2-18 Display of Node status

Status Display Display color
Normal Ready
Error Fail Red
Communication Error Communication Error Red

l Lower part of the list view when the ESB bus interface module of an FIO
node is selected
The following table shows the contents that are displayed in the lower part of the list view
when the ESB bus interface module of an FIO node is selected.

Table H1.2-19 Status display (when an I/O node ESB bus interface module is selected)
Item Status Display Display color
Normal Ready
ESB-S Status Error Fail Red
Communication Error Communication Error Red

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-18

l Lower part of the list view when the power supply module of an FIO node
is selected
The following table shows the contents that are displayed in the lower part of the list view
when the power supply module of an FIO node is selected.

Table H1.2-20 Status display (when an I/O node power supply module is selected)
Item Status Display Display color
Normal Ready
PSU Status Error Fail Red
Communication Error Communication Error Red

24 V DC Power Supply Normal Ready

Status Error Fail Red

l Lower part of the list view when an N-IO node is selected

The following table shows the contents that are displayed in the lower part of the list view
when an N-IO node is selected.

Table H1.2-21 Content of the status display (when an N-IO node is selected)
Item Status Display Display color
Node number Node number
Component number Component number
Node comment Node comment
Normal Ready
Error Fail Red
Node status
During maintenance Maintenance Blue
Transmission error Communication Error Red

NIU maintenance port Enable Enable Red

status Disable Disable
Normal Ready
Error Fail Red
External alarm input
Diagnosis by external Blank
alarm input is disabled
Normal Ready
Temperature status
Error HI, LO Red

l Lower part of the list view when the N-ESB bus module of an N-IO node is
selected
The following table shows the contents that are displayed in the lower part of the list view
when the N-ESB bus module of the N-IO node is selected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-19
Table H1.2-22 Contents of the status display (when the N-ESB bus module of an N-IO node is selec-
ted)
Item Status Display Display color
Normal Ready
Error Fail Red
During maintenance Maintenance Blue
N-ESB-S status
Error due to maintenance Fail (Due to maintenance Red
of one module of one module)
Transmission error Communication Error Red

NIU maintenance port Enable Enable Red

status Disable Disable

l Lower part of the list view when the power supply module of an N-IO node
is selected
The following table shows the contents that are displayed in the lower part of the list view
when the power supply module of an N-IO node is selected.

Table H1.2-23 Contents of the status display (when PSU of an N-IO node is selected)
Item Status Display Display color
Normal Ready
PSU status Error Fail Red
Transmission error Communication Error Red
Normal (*1)
PSU stopped supplying Power Off Red
Detail
power
PSU output over voltage Overvoltage Red
*1: The PSU is normal, or not in the power off or over voltage status.

l Lower part of the list view when a unit of an N-IO node is selected
The following table shows the contents that are displayed in the lower part of the list view
when a unit of an N-IO node is selected.

Table H1.2-24 Contents of the status display (when a unit of an N-IO node is selected)
Item Status Display Display color
Unit number Unit number
Normal Ready
Bus status Error Fail Red
Communication error Communication Error Red

l Lower part of list view when the representative Input/Output module is

selected
I/O module of each node can be grouped, and the group status can be displayed in the list
view as a representative I/O module. Individual I/O modules are displayed under the repre-
sentative I/O module in tree format.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-20
Table H1.2-25 Contents of the status display (when the representative IOM of a node is selected)
Item Status Display Display color
Normal Ready
Representative
Input/Output Module Sta- Error I/O Fail Red
tus
Communication Error Communication Error Red

Status of Representative Normal Ready

Channel Error Channel Fail Red

l Lower part of the list view when an individual I/O module of the CPU node
or an FIO node is selected
The following table shows the contents that are displayed in the lower part of the list view
when an individual I/O module of the CPU node or an FIO node is selected.

Table H1.2-26 Contents of the status display (when an individual I/O module of the CPU node or an
FIO node is selected)
Item Status Display Display color
Input/Output Module Type I/O module model (*1)
Normal Ready
Waiting Stand-by Yellow
Input/Output Module Sta-
Error Fail Red
tus
Waiting for startup Waiting Blue
Communication Error Communication Error Red
For each bus, [Ready] is displayed when the status is normal and [Fail] (red) is
Bus Status
displayed if the status is abnormal.
Normal Ready
Port status (*2)
Error (*3) Error Red
Normal Ready
IOP+ (*4) IOP+ Red
IOP- (*4) IOP- Red
Channel Status Transmitter failure+ (*5) TRNS+ Red
Transmitter failure- (*5) TRNS- Red
Analog input error OvrRange Red
Error Ch Fail Red
*1: If ALR111M is set when the I/O module is defined, ALR111 is displayed in the SCS State Management window.
Similarly ALR121 is displayed for ALR121M and ALE111 is displayed for ALE111M.
*2: Displayed only when a communication module used for communicating with a subsystem is selected.
*3: With S2LP131, an error is a state where either one or both of a safety subsystem communication path error (SS-SCPATH)
and a safety subsystem communication error (SS-SCOM) are occurring.
*4: This is only if an analog input module is used.
*5: Displayed only when an analog input module other than the one for TC/RTD is selected.

l Lower part of the list view when an individual I/O module of an N-IO node
is selected
The following table shows the contents that are displayed in the lower part of the list view
when an individual I/O module of an N-IO node is selected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-21
Table H1.2-27 Contents of the status display (when an individual I/O module of an N-IO node is selec-
ted)
Item Status Display Display color
I/O module model I/O module model
Normal Ready
Standby Standby Yellow
I/O module status
Error Fail Red
Transmission error Communication Error Red
Normal Ready
Bus status
Error Fail Red
Normal Ready Red
IOP+ (*2) IOP+ Red
IOP- (*2) IOP- Red
Transmitter failure+ (*2) TRNS+ Red
Transmitter failure- (*2) TRNS- Red
Analog input error (*2) OvrRange Red
Channel status (*1) Barrier missing (*3) IS Barrier Disconnected Red
Barrier connection error IS Barrier Configuration Red
(*3) Error
I/O open circuit error (*4) Open Circuit Red
I/O short circuit error (*5) Short Circuit Red
Field failure Field Side Error Red
Error Ch Fail Red
Not used Blank
Current input (IN) Current
(IN) Current - IS (*3)
Current input (HART) (IN) Current - HART
(IN) Current - HART - IS
(*3)
Status input (IN) Status
(IN) Status - IS (*3)
Current output (OUT) Current
(OUT) Current - IS (*3)
Channel signal type
Current output (HART) (OUT) Current - HART
(OUT) Current - HART -
IS (*3)
Status output (OUT) Status
(OUT) Status - IS (*3)
1.3 A status output (OUT) Status 1.3A*
(OUT) Status 1.3A* - IS
(*3)
2.0 A status output (OUT) Status 2.0A*
(OUT) Status 2.0A* - IS
(*3)
*1: Does not display the status of those channels where an I/O variable are not allocated.
*2: Displayed only if an analog input module is selected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H1.2 SCS State Management window> H1-22
*3: Displayed only when the intrinsic safety barrier is used.
*4: Displayed only when open circuit detection is set.
*5: Displayed only when "Detect Short Circuit" is set.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H2. System reports> H2-1

H2. System reports

System report includes SCS Report window and IOM Report window in the SCS State Man-
agement Window. The above two windows can be used for displaying SCS status and input/
output module status respectively. When abnormality occurs, the details displayed on these
windows can help analyzing the causes of problems. The reports can be printed out or saved
into text files.

n SCS Report
SCS Report displays the SCS status.
Select a device item other than the input/output modules in Hardware Configuration Tree
View of the SCS State Management window, and then click [System Report] button on the
toolbar. The SCS Report dialog box will be displayed.

SCS Report

10/31/2013 3:06:16 PM

Station name : SCS0101

Type : SSC10S-S
Address : 01-01
Status : Ready
Revision : R3.02.10
Generation:
POU DB : 10/31/2013 11:00:01 AM
Variable DB : 10/31/2013 11:00:01 AM
System DB : 10/31/2013 11:00:01 AM
Integration DB : 10/31/2013 11:00:01 AM
CPU Idle Time : 27sec
Comm Load Ave : 0%
Cur : 0%
Control Status : RUN
Scan Period : 100msec
Scan Period Setup : 100msec
Execution Time : 0%
Operating Mode : Runnig
Security Level : 1
Forcing : 0
Link Trans Lock : 3stn
Inter-SCS Comm Lock : 2stn
Comm I/O Lock : No
IRIG-B :
Time Sync :
Temperature:
Air in : Ready
Air out : Ready
Battery:
L : Ready
R : Ready
Battery:
L : Fail
R : Ready
CPU Card Status :

Print File Close

Figure H2-1 SCS Report dialog box

l Display example of the SCS report of the system that has a combination of
FIO and N-IO
In the SCS report of the system that has a combination of FIO and N-IO, the node status is
displayed in the following order: CPU node, FIO node, and N-IO node.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H2. System reports> H2-2
**********************
FIO Node Status: * Discrimination from N-IO node
Line No. :
Node No. :
Comment :
Component No. :0001 * Component number
Com Status (L) :Ready / Fail
(R) :Ready / Fail
PSU Status (L) :Ready / Fail
(R) :Ready / Fail
I/O Unit :Ready / Fail
Slot No. Type Status Bus1 Bus2 Port1 Port2 Port3 Port4 Channel
1 XXXXXX Ready / Fail ("XXXXXX" is an IOM model name.)
2 XXXXXX Ready / Fail
**********************

**********************
N-IO Node Status: * Discrimination from the existing FIO node
Node No. :
Comment :
Component No. :0001 * Component number
NIU Status (L) :Ready / Fail / Fail (Only one module is under maintenance) / Maintenance
(R) :Ready / Fail / Fail (Only one module is under maintenance) / Maintenance
Maintenance Port (L) :Enabled / Disabled * NIU maintenance port L/R enable/disable
(R) :Enabled / Disabled
PSU Status 1 :Ready / Fail * PSU Status 1/2
2 :Ready / Fail
I/O Unit :Ready / Fail
Diagnosis : * The detected error information is separated with comma for each error and displayed.
Unit No: 1 * Unit No: 1 - 6
BUS Status 1 :Ready * F-SB bus between NIU and IOM Unit
2 :Ready
Slot No. Type Status In-Bus1 In-Bus2 Channel * In-Bus1/2
1 XXXXXX Ready / Fail ("XXXXXX" is an IOM model name. )
2 XXXXXX Ready / Fail
Unit No: 2
:
omitted
:
**********************

l Operations in the SCS Report dialog box

Use the following buttons to perform operations.

Table H2-1 Explanation of button names and operations

Button Description
Print Print the display of the SCS Report dialog box.
File Save the display of the SCS Report dialog box (text format).
Close Close the SCS Report dialog box.

n IOM Report
The input/output module status or the communication module status detected by the SCS
CPU module is displayed in the IOM Report window.
Select the input/output module or the communication module in Hardware Configuration Tree
View of the SCS State Management window, and then click [System Report] button on the
toolbar. The IOM Report dialog box will be displayed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H2. System reports> H2-3

IOM Report
08/26/2011 3:07:08 PM

I/O Module :
Node : 1
Slot : 2
Type : SDV531 (2)
IOM Model : SDV531-S23 S1U0H00-F00-
Serial No : xxxxxxxxxx

IOM Fail
First Error Code : 08/26/2011 2:52:22 PM IOM Restart (0x0000 5106)
Last Error Code : 08/26/2011 2:52:22 PM IOM Restart (0x0000 5106)
IOM Start : IOM Restart (Power-On) (0x0301 5547)

Channel
01: Normal
02: Normal
03: Normal
04: Normal
05: Normal
06: Normal
07: Normal
08: Normal
09: Normal
10: Normal
11: Normal
12: Normal
13: Normal
14: Normal
15: Normal
16: Normal

Print File Close

Figure H2-2 IOM Report dialog box

l Operations in the IOM Report dialog box

Use the following buttons to perform operations.

Table H2-2 Explanation of button names and operations

Button Description
Print Print the display of the IOM Report dialog box.
File Save the display of the IOM Report dialog box (text format).
Close Close the IOM Report dialog box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3. Checking diagnostic information by using IOM Report> H3-1

H3. Checking diagnostic information by

using IOM Report
This chapter explains the following items regarding the diagnostic information relating to
AIO/DIO modules and communication modules that are displayed in the IOM Report dialog
box called from the SCS Maintenance Support Tool.
• Format of diagnostic information displayed in the IOM Report dialog box
• Details of diagnostic information displayed in the IOM Report dialog box
SEE
ALSO For more information about IOM Report for the serial communication module, refer to:
H3.2, “IOM Report of communication modules” on page H3-19

n Calling the IOM Report

In the Hardware configuration tree view within the SCS State management window of the
SCS Maintenance support tool, select an input/output module and click the "System report"
button on the tool bar; the IOM Report dialog box appears.
SEE
ALSO For more information about the structure and operations of the IOM Report dialog box, refer to:
H2., “System reports” on page H2-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-2

H3.1 IOM Report of AIO/DIO modules

This section explains the IOM Report for the analog input/output modules (AIO modules) and
the discrete input/output modules (DIO modules). In the explanation of these items, AIO/DIO
modules are referred to as input/output modules.

n Display content in the IOM Report

The IOM Report displays the diagnostic information regarding input/output module errors. The
input/output module errors are categorized and displayed as follows:
• Cause of the input/output module error (CPU detection)
This is a display of the input/output module error status detected by the CPU module of
the SCS. The input/output module status as viewed from the CPU (such as No response
and HRDY OFF) and other information are displayed. The detailed cause of the input/
output module failure is displayed under "Error information inside the input/output mod-
ule."
• Error information inside the input/output module
Causes of an error and a recovery are collected from the input/output module, and then
displayed.
• Cause of the channel error
Channel error status is displayed. IOP errors detected by the CPU module and channel
errors detected by the input/output module are displayed. If an IOM module becomes er-
ror due to an error in an I/O channel, multiple error messages regarding the channel of
the I/O module maybe displayed.
TIP If a bus error occurs between an input/output module and a CPU module, the following codes indicating the
source of the error are reported in the IOM Report generated after operations are restored.
• Cause of the input/output module error (CPU Detection)
No response from the input/output module. CPU is unable to retrieve error information from the input/
output module.
• Error information inside the input/output module
Communication cannot be established with the host CPU or bus for the input/output module, resulting in
a host failure error and a fallback operation.
Note also that if there is an input/output module hardware failure, HRDY OFF is displayed in Cause of the
input/output module error (CPU Detection) and you can identify the cause of the failure from the error infor-
mation in the input/output module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-3

H3.1.1 Display format for the IOM Report of FIO

If the I/O module of FIO is used, the IOM report is displayed in the following format.

I/O Module:
Node :2
Slot :1
Type : SAI143S
IOM Model : SAI143-S03 S1U0H00- F00-
Serial No : XXXXXXXX

(Current status) : (Current error information (CPU detection))

First Error Code : (Information for first error)
Last Error Code : (Information at recovery)
(Error information inside the input/output module)

Channel
1: (Channel status) (The latest channel error)
(Cause of the channel error detected by the input/output module)
2: (Channel status) (The latest channel error)
(Cause of the channel error detected by the input/output module)
.
.

16: (Channel status) (The latest channel error)

(Cause of the channel error detected by the input/output module)

(4 kbyte dump display)

n An example of I/O module error

This is the explanation of the example of the IOM Report that appears when you select a
module and call it under the following circumstance.
Time T1 Time T2 Time T3

Input/output module
status as viewed IOM normal
IOM normal Error A Error B Error C
from the CPU (IOM recovered)

(Current status)

Error A Error C
First Error Cause 0 (Time of occurrence T1) (Time of occurrence T3)

Last Error Error B

Cause 0 Not displayed Not displayed
(Time of recovery T2)

Pattern Pattern Pattern Pattern

(1) (2) (3) (4)

Figure H3.1.1-1 Input/Output module error

The following information will be displayed in each of the situations shown in the figure.
• Pattern (1)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-4
This is a state where there is no input/output module error after the initial cold start of the
CPU. In this case, the current status (normal) will be displayed. The first and last error
code lines will display the time when the input/output module was started and the cause
(Cause 0), respectively.
• Pattern (2)
This is a state where there is an input/output module error. The current status and the
current error content, as well as the time of the first error occurrence (T1) and the first
error (Error A), will be displayed. The last error will not be displayed. (The last error code
line will not be displayed.)
• Pattern (3)
This is a state where the input/output module has recovered from the error. The current
status (normal), the time of the first error occurrence (T1), the first error (Error A), the time
of recovery (T2), and the last error (Error B) will be displayed.
• Pattern (4)
This is a state where there is an input/output module error. The time of the first error oc-
currence (T3) and the first error (Error C) will be displayed.

n Display format details (I/O module details)

Cause of the input/output module error and error information inside the input/output module
are displayed in the following format.

Table H3.1.1-1 Cause of the Input/Output module error and error information inside the Input/Output
module
Display item Description
The current IOM status will be displayed in the following format.
Current status
IOM Normal/IOM Fail/IOM Fail (Output Shutoff)
The cause of the current input/output module error detected by the CPU
will be displayed with error code.
Current error information (CPU
Example: No response (0x0000 5101)
detection)
Display condition: The information is displayed when there is an input/
output module error.
The time of the first error occurrence detected by the CPU (when the in-
put/output module status changed from normal to error) and the error in-
formation will be displayed with error code.
Information for first error
Example: 20/4/2005 12:34:56 IOM Fail (HRDY OFF) (0x0000 5105)
Display condition: The information is displayed when an error occurs
with the input/output module even once.
The recovery time of the I/O module and the latest error information will
be displayed with error code.
Error information at recovery Example: 20/4/2005 12:50:56 IOM Restart (0x0000 5106)
Display condition: The I/O module is currently normal and the displayed
information is the latest error in the past.
How the input/output module was started and the error code inside the
input/output module will be displayed.
When the input/output module is normal
Example 1:
IOM Start: IOM Restart (Power On) (0x0301 5547)
Information of errors within the I/O
When there is an input/output module error
module (*1)(*2) Example 2:
IOM Fail: IOM Readback Error (0x0101 5502)

Display condition: The information is displayed when the cause of the

error is stored inside the input/output module, and the input/output mod-
ule information can be obtained.
*1: The "Information of errors within the I/O module" lists the details of factors of the "Current status" that are due to the I/O mod-
ule. The status information for individual channels is not included here.
*2: The "starting factors" displayed in the "Information of errors within the I/O module" are detailed factors upon the previous start
of the I/O module or recovery from an error.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-5

n Display format details (channel details)

The details of a channel error will be displayed as follows:

Table H3.1.1-2 Cause of the channel error

Display item Description
The current channel status will be displayed. If the I/O module is dual-
redundantly configured, the channel status on the control side module
Channel status (*1) will be displayed.
- (When the channel is not in use) / Normal / IOP+ / IOP- / TRNS+ /
TRNS- / Ovr Range / Ch Fail
This part displays the time that the channel recovered from the error
and the latest error information. If the I/O module is dual-redundantly
Latest channel error (*1) configured, the latest error on the control side module will be displayed.
This item is displayed only when the channel status is normal.
Example: Normal (21/6/2005 12:50:56 Last Error: IOP+)
The last-saved channel error in the I/O module will be displayed. If mul-
tiple errors are kept in the I/O module, the multiple errors may be dis-
played. Even if the I/O module is in dual-redundant configuration, the er-
Cause of the channel error detec-
ror of the module will be displayed anyway.
ted by the input/output module(*2)
Example :
Open Circuit (0x0401 5561)
Short Circuit (0x0401 5562)
*1: The channel status during IOM Failure is the status right before the IOM fails.
*2: If the IOM failure is caused by the abnormality of a channel, the error of the channel will be displayed in IOM Report.

Example 1: Channel Failed

1: IOP+
2: Ch Fail
Open Circuit (0x0401 5561)

Example 2: Channel Recovered

3: Normal (22/8/2011 12:50:56 Last Error :IOP+)
4: Normal (22/8/2011 12:50:56 Last Error :Ch Fail)
Open Circuit (0x0401 5561)

TIP The channel status and the last error of a pair of dual-redundantly configured input/output modules will be
collected from the active input/output module. If the input/output module is placed in a redundant configura-
tion, read the descriptions regarding the IOM Report of the active input/output module for details.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-6

H3.1.2 Display format for the IOM report of N-IO

The section explains the IOM Reports in the N-IO hardware for N-ESB bus coupler module,
N-ESB bus module, and I/O module.

n N-ESB bus coupler module (S2EN40x)

The IOM report of S2EN402 and S2EN404 is displayed in the following format.
YYYY/MM/DD HH:MM:SS
(Status)
Bus Coupler Module:
Node : 2
Slot : 1
Type : S2EN404
IOM Model : S2EN404
FPGA Revision : 8033

(Current Status)
Port1 Status : Link Up
Port2 Status : Link Up
Port3 Status : Link Up
Port4 Status : Link Up

Port 1 Live List : 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16

Port 2 Live List : 17, 18, 19, 20, 21, 22, 23, 24
Port 3 Live List : 25, 26, 27, 28, 29, 30
Port 4 Live List : 31, 32

(256 byte dump display)

Table H3.1.2-1 Display items of S2EN40x

Item Description
YYYY/MM/DD Date and time when the IOM Report is displayed
HH:MM:SS
Status Acquisition status of the IOM Report (*1)
Type Module type: Bus Coupler Module
Node Node number
Slot Slot number: 1 to 8
Type Representative model of the module: Model of the module defined in SENG
IOM Model Manufacturing information and firmware revision of the module
Representative model of the module that is implemented
FPGA Revision Revision of FPGA (Field Programmable Gate Array)
Current status The IOM status is displayed.
IOM Normal: Normal
IOM Fail: Failure
Port n Status Link status of N-ESB port n (n=1 to 4)
Link Up: Transmission possible
Link Down: Communication not possible (*2)
Port n Live List Live list information of the N-IO node that is connected under the N-ESB port n
(n=1 to 4)
Addresses of N-IO nodes that support the communication from S2EN40x are lis-
ted
Scope: 1 to 32, ascending order, maximum 16 nodes; addresses that are not in
succession are displayed close to each other. (*3)
*1: Blank when it is normal.
• When implementing a module different from the defined module: This IOM differs from the model name which the engi-
neering function defined.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-7
• When module cannot be accessed: Cannot get the memory information in this IOM.
*2: In S2EN402, Link Down is always displayed for port 3 and port 4.
*3: In S2EN402, no node address is displayed for port 3 and port 4.

n N-ESB bus module (S2EN501)

The IOM report of S2EN501 is displayed in the following format.
YYYY/MM/DD HH:MM:SS
(Status)
Node Interface Unit:
Node : 2
Slot : Left
Type : S2EN501
IOM Model : S2EN501-S11 S0U0H0
FPGA Revision : 8033
Serial No. : xxxxxxx

(Current Status)
Maintenance Port : Enabled
PSU 1 Status : Normal
PSU 2 Status : Fail (OVERVOLTAGE: 25.1V)
Temperature : Normal (24C)
External Equipment: Normal

(256 byte dump display)

Table H3.1.2-2 Display items of S2EN501

Item Description
YYYY/MM/DD Date and time when the IOM Report is displayed
HH:MM:SS
Status Acquisition status of the IOM Report (*1)
Type Module type: Node Interface Unit
Node Node number
Slot Slot number: Left or Right
Type Representative model of the module: Model of the module defined in SENG
IOM Model Manufacturing information and firmware revision of the module
Representative model name, basic specification code and hardware revision of
the module that is installed
FPGA Revision Revision of FPGA (Field Programmable Gate Array)
Serial No. Serial No. : Serial No. of the module that is actually installed.
Current status Displays the status of NIU.
NIU Normal: Normal
NIU Fail: Failure
NIU Fail (Due to maintenance of one module): Failure due to maintenance of
one module (*2)
NIU Maintenance: Under maintenance
Maintenance Port Displays the status of the maintenance port
Disabled: Inactive
Enabled: Active
PSU 1 Status The status of PSU 1
Normal: Normal
Fail: Failure
The results of the power diagnosis and voltage value are shown in ().
POWER OFF: Stops PSU function
OVERVOLTAGE: PSU output shows over-voltage
CODE = XXXX: Error with code XXXX has occurred
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-8
Table H3.1.2-2 Display items of S2EN501 (Table continued)
Item Description
PSU 2 Status The status of PSU 2
Redundant power: same as PSU 1
Single power: -
Temperature Temperature around S2EN501
Normal: Normal
HI: HI alarm
LO: LO alarm
Temperature (Celsius) is shown in ().
External Equipment The status of the discrete input from external devices
Normal: Normal
Fail: Failure
*1: Same as S2EN40x.
*2: This status indicates that one module of the NIU is normal and the other is under maintenance.

n N-IO I/O module (example for S2MMM843)

The IOM report is displayed in the following format.
YYYY/MM/DD HH:MM:SS
(Status)
I/O Module:
Node : 2
Unit : 1
Slot : 1
IOM Type : S2MMM843
IOM Model : S2MMM843-S00 S0U0H0-- F0--
Serial No. : xxxxxxx
Base Plate Type : S2BN1D
Base Plate Model : S2BN1D

F-SB Status
Bus S2EN501 Status
1 L Normal
1 R Normal
2 L Normal
2 R Normal

(Current status) : (Current error (CPU detection))

First Error Code : (First error)
Last Error Code : (Error at recovery)
(Error information in IOM)

Channel
1 : (Channel type)
(Channel Status) (Cause of Last Error)
(History of Error Cause in IOM)
(Skip)
16 : (Channel type)
(Channel Status) (Cause of Last Error)
(History of Error Cause in IOM)
(6k byte dump display)

Table H3.1.2-3 Display Items of the N-IO I/O Module

Item Details Description
YYYY/MM/DD Date and time when the IOM Report is displayed
HH:MM:SS
Status Acquisition status of the IOM Report (*1)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-9
Table H3.1.2-3 Display Items of the N-IO I/O Module (Table continued)
Item Details Description
Type Module type: I/O Module
Node Node number
Unit I/O Unit number: 1 to 6
Slot Slot number: 1 to 2
Type Representative model of the module: Model of the module de-
fined in SENG
IOM Model Manufacturing information and firmware revision of the module
Representative model name, basic specification code, hardware
revision, and firmware revision of the module that is installed
Serial No. Serial No. : Serial No. of the module that is actually installed.
Base Plate Type Representative model of the base plate: Model of the base plate
defined in SENG
Base Plate Model Base plate information: information of the mounted base plate
(model)(*2)
F-SB Status IN-Bus Flexible-SB bus number seen from IOM (1, 2): 1 or 2
S2EN501 Slot position of S2EN501: L (left) or R (right)
Status Communication status between S2EN501 and IOM
Normal: Normal
Fail: Failure
(Main cause of error Current status Displays the current status of IOM.
in IOM) IOM Normal: Normal
IOM Fail: Failure
IOM Fail (Output Shutoff): Error in output shutoff switch opera-
tion
Current error details Displays the current cause of the IOM error that is detected by
the CPU in character strings and error code.
Displayed when there is an error in IOM.
Example: No response (0x0000 5101)
First Error (*3) Displays the first error code detected by the CPU in character
strings, error code, and time (time of error occurrence).
First error indicates the change of IOM status from normal to er-
ror.
It appears when an error occurs even once.
Example: 2016/2/24 12:34:56 IOM Fail (HRDY OFF) (0x0000
5105)
Last Error (*3) Displays date and time of recovery, last error code and startup
cause.
Displays in the normal state of IOM after recovery from error.
Example: 2016/2/24 12:50:56 IOM Restart (0x0000 5106)
Information of errors Displays the IOM internal error code and startup cause.
within the IOM (*4) This is displayed when IOM information is obtained and the er-
(*5) ror cause is stored.
Example 1: IOM in normal state
IOM Normal: IOM Restart (Power On) (0x0301 5547)
Example 2: IOM in error state
IOM Fail: IOM Readback Error (0x0101 5502)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-10
Table H3.1.2-3 Display Items of the N-IO I/O Module (Table continued)
Item Details Description
Channel Displays the following information for each channel.
The number of channels depends on the IOM type.
S2MMM843, S2MDV843: 1 to 16 channels
Channel type Displays the signal type of the I/O channel defined in IOM Build-
er.
Channel status (*6) Displays the current channel status.
(*7) If IOM is redundant, channel status of the control side is dis-
played.
- (Unused) / Normal / IOP+ / IOP- / TRNS+ / TRNS- / Rang
Over / Ch Fail, etc.
Cause of Last Error Displays date and time of recovery from channel error, and
(*6) cause of the last error. .
If IOM is redundant, cause of the last error that has occurred in
the module of the control side is displayed.
It is displayed only when the channel is normal.
Example: Normal (2015/6/21 12:50:56 Last Error: IOP+)
Display of history of Cause of the last error saved in IOM is displayed (if there are
IOM error causes multiple errors, they are individually displayed).
(*7) Even when IOM is redundant, error cause (cause of error detec-
ted in the corresponding module) of the corresponding module
is displayed.
Example 1: Open Circuit (0x0401 5561)
Example 2: Short Circuit (0x0401 5562)
*1: Same as S2EN40x.
*2: In the base plate for intrinsic safety barrier, the basic specification code (-xxxC/ -xxxD) is displayed at the end of base plate
model. Only a character (4th character = position of terminal) is displayed according to the base plate while others are dis-
played as xxx.
*3: The current status of IOM and display pattern of First Error/Last Error are similar to SSC60 FIO.
*4: The "Information of errors within the IOM" lists the details of factors of the "Current status" that are due to the I/O module. The
status information for individual channels is not included here.
*5: The "starting factors" displayed in the "Information of errors within the IOM" are detailed factors upon the previous start of the
I/O module or recovery from an error.
*6: The status before the error occurrence is retained during the IOM error occurrence.
*7: When the "Channel status" is Normal, this indicates that the "Display of history of IOM error causes" is a history of errors from
the past. The channel status can be confirmed from the SCS State Management Window and HIS due to being notified to the
operating status and system alarm.

SEE
ALSO For more information about signal types of the channels, refer to:
“l Lower part of the list view when an individual I/O module of an N-IO node is selected” on page H1-20
For more information about IOM error causes, channel status, and details displayed in history of errors, refer
to:
H3.1.3, “Code system for causes of errors in the IOM Report” on page H3-12

l High current output

The IOM report is displayed in the following format when the signal type of the channel is set
to high current output with S2MMM843 or S2MDV843.
Channel
1 : (OUT) Status 2.0A*
Ch Fail
2 : (OUT) Status 2.0A
-
3 : (OUT) Status 2.0A
-
Open Circuit (0x0401 5561)
This section describes the IOM Report when there is an error in the non-primary channel.
Channel error information is displayed in the part that shows the channel status of the IOM
report. For example, if failure occurs in non-primary channel 3 of combined 1 to 3 channels,

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-11
information is displayed in both the primary channel of the IOM report and the non-primary
channel where error occurred.
When the high current output is set, “Cause of last error” of the primary channel indicates the
compound causes of the primary channel and non-primary channel. When the high current
output is set, check the “Cause of last error” of the primary channel.
“Channel status” is displayed in the primary channel. “Cause of last error” is also displayed if
error occurred in the past. Actual error cause is displayed in “Error cause history of IOM” in
the non-primary channel. However, "-" is displayed in “channel status” to indicated that the
channel is not used.
If an error occurs only in the primary channel, information is displayed only in the number of
the primary channel.

Table H3.1.2-4 Display items of high current output

Signal type Character string Description
Status output (OUT) Status 1.3A* Primary channel
(1.3A output)
(OUT) Status 1.3A Non-primary channel
Status output (OUT) Status 2.0A* Primary channel
(2A output)
(OUT) Status 2.0A Non-primary channel

The "Display of history of IOM error causes" displays the latest information on the causes of
errors that have occurred anytime in the past leading to the present. With the large current
output (DO), even in a case when an error has occurred with a certain channel, information of
occurrence in the past may be remaining in the error cause history of a different channel that
is currently normal.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-12

H3.1.3 Code system for causes of errors in the IOM Report

The display format and the code system in the IOM Report to indicate the causes of errors
are as follows:

n Display format
Category of input/output module errors ∆ Category of causes of errors

n Code system for category of Input/Output module errors

• 0x00XX
Error detected by the CPU
• 0x01XX
Input/Output Module Hardware Failure
• 0x02XX
Input/output module setting error (such as a disconnected connector on the field side)
• 0x03XX
Recovery from an input/output module error (such as when the input/output module was
recovered from 0x02 above, or recovered after the fallback operation was executed upon
detecting a host side error)
• 0x04XX
Channel error (In this case, there is an error with the applicable channel. It indicates a
wiring error or a channel hardware failure when the input/output module is in a single con-
figuration. If the input/output module is in a redundant configuration, the channel hard-
ware failure will be displayed as the category 0x01XX "Input/output module hardware fail-
ure.")

n Code system for category of causes of errors

• 0x51XX
Content of error detected by the CPU
• 0x55XX
Content of error detected by the input/output module (including cause of recovery)

n Cause of the Input/Output module error (CPU detection)

The following explains the details of the codes used to indicate the cause of the input/output
module error detected by the CPU. The IOM Report will display these codes as "Current error
information (CPU detection)," "Information for first error," or "Error information at recovery."

Table H3.1.3-1 Details of codes for cause of Input/Output module error (CPU detection)
Code (hexadeci-
Display Description
mal)
A no-response error has occurred during the communica-
tion between the CPU and the input/output module.
0000 5101 No response
The error occurred is either with the input/output module
or in the communication path to the input/output module.
The model name of the input/output module defined in the
SENG does not match that of the input/output module in-
0000 5102 IOM model Code Error
stalled.
Verify the model name of the input/output module.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-13
Table H3.1.3-1 Details of codes for cause of Input/Output module error (CPU detection) (Table contin-
ued)
Code (hexadeci-
Display Description
mal)
The setting information defined in the I/O parameter build-
er does not match the input/output module setting infor-
0000 5103 IOM Configuration Error
mation.
Perform IOM download.
An input/output module hardware failure has been detec-
ted. An error occurred and the HRDY on the I/O module
0000 5104 IOM Fail (HRDY OFF) turned OFF.
Check the error information inside the input/output mod-
ule for the detailed cause of the error.
The error may have been generated because the connec-
tor is disconnected and field power not supplied, or IOM
0000 5105 I/O Error (AP READY-OFF) download was performed.
Check the error information inside the input/output mod-
ule for the detailed cause of the error.
The input/output module has recovered from the error
state.
0000 5106 IOM Restart
Check the error information inside the input/output mod-
ule for the detailed cause of the error.
An error occurred and the Output Shutoff switch was acti-
vated due to a reason other than output module failure
(the HRDY does not turn OFF). Check the IOM Report for
0000 5107 (*1) Output Shutoff the detailed cause of the error.
If this type of error occurs, perform the output module
start operation after the cause of the error has been elimi-
nated.
0000 5111
0000 5112
An error has been detected in the data check of the com-
0000 5113 munication between the CPU and the input/output mod-
ule.
0000 5108 (*2) Communication Error
This error may have been caused due to a failure with the
0000 5109 (*2) input/output module or the communication path between
the CPU and the input/output module.
0000 511d (*2)
0000 511e (*2)
0000 5114 An error has been detected in the redundancy control part
of the I/O module. Replace the I/O module. However,
when two I/O modules of single definition are changed to
redundant in the FIO node and online change download
is performed, this error may occur if the connector is con-
IOM Redundant Control Fail nected only to the I/O module of either side. In this case,
0000 5115 you need to connect the connector to the I/O modules of
both sides. Recovery can be checked by system alarm
message No.0082 "Normal recovery of I/O modules". In
this case, it is not necessary to replace the input/output
module.
0000 5116 An error has been detected in the input/output module.
Replace the input/output module.
However, if the IOM Error (0000 5117) occurred after the
IOM Error
0000 5117 IOM downloading or during the SCS restarts after offline
downloading, there is no need to replace the input/output
module.
*1: SDV531-S13 only
*2: N-IO only

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-14

l Differences in output results as a result of differences in AIO/DIO module

firmware
If the following errors occur and an IOM report is displayed, either "0000 5103" or "0000 5105"
will be displayed, depending on the version of the AIO/DIO module.
• Download in progress for input/output module initialization
• Front connector disconnected
• Failure in the power supply from the front connector
When an error addressed as “0000 5103” remains unsolved although you perform IOM down-
load as the corrective action against “0000 5103” error, the actual error is possibly one of
these three errors because they are originally “0000 5105” errors. Confirm that the front con-
nector is properly connected.

n Error information inside the Input/Output module

The following explains the details of the codes for the cause of error detected by the input/
output module in the channel common area of the input/output module, or in the channel area
if the input/output module is in a redundant configuration. The IOM Report will display these
codes as "Error information inside the input/output module."

l Input/Output module hardware failure

The following explains the details of the codes for hardware failure in the channel common
area of the input/output module, or in the channel area if the input/output module is in a re-
dundant configuration.

Table H3.1.3-2 Details of codes for Input/Output hardware failure

Code (hexadeci-
Display Description
mal)
01xx 5501 There has been a failure in the channel common area of
(xx: Internal IOM Channel Common Fail the input/output module.
code) Replace the input/output module.
An error has been detected in the readback process for
the output value.
Check the field wiring of the analog output module for any
abnormality (for example, short-circuits between chan-
0101 5502
nels), and also confirm that the total resistance of all con-
0401 5502 Output Readback Error
nected cables and devices does not exceed the value of
(*1)
the allowable output load resistance for output modules
that is written in the GS (General Specification).
If the wiring and resistance are appropriate, replace the
output module.
0101 5503
An error has been detected in the channel power supply.
0401 5503 Internal Power Supply Fail
Replace the input/output module.
(*1) (*2)
A failure that the output channel is unable to change from
0101 5504 ON to OFF has been detected.
0401 5504 Output Channel Stuck at ON Check the field wiring for any abnormality (for example,
(*1) short-circuits between channels).
If there is no field wiring error, replace the output module.
With the input channel, a failure where the input signal
does not turn ON has been detected.
0101 5505
With the output channel, a failure where the output signal
0401 5505 I/O Channel Stuck at OFF
cannot be turned ON has been detected.
(*1)
If there are not errors with the field wiring, replace the I/O
module.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-15
Table H3.1.3-2 Details of codes for Input/Output hardware failure (Table continued)
Code (hexadeci-
Display Description
mal)
0101 5506 An overcurrent failure has been detected inside the input/
0401 5506 Over Current output module.
(*1) Replace the input/output module.
There have been some errors with the channel area of
01xx 5507
the input/output module.
04xx 5507
Check if there is an input of a signal value at a level be-
(xx: Internal IOM Channel Fail
tween ON and OFF or chattering has occurred.
code)
If the input signal level is normal or chattering has not oc-
(*1)
curred, replace the input/output module.
*1: For a channel failure, the error code and the error status will vary depending on whether the I/O module is of a duplex config-
uration or a single configuration.
• The upper error code is for a redundantly configured I/O module, while the lower error code is for a non-redundantly con-
figured I/O module.
• If the input/output module is in a redundant configuration, this error will be an IOM Fail error. In a non-redundant configura-
tion, the error will occur only to the failed channel.
*2: FIO only

SEE
ALSO For more information about allowable load resistance of the analog output module, refer to:
Analog I/O module (for ProSafe-RS) (GS 32Q06K30-31E)

l Input/Output module setting error

The following explains the details of the codes for input/output module setting error.

Table H3.1.3-3 Details of codes for Input/Output module setting error

Code (hexadeci-
Display Description
mal)
Connector on Field Side The connector on the field side is disconnected. Check
0201 5521 (*1)
Disconnected the connector.
There has been a voltage error with the field power sup-
ply. Check if there are any errors with the field power sup-
0201 5522 (*1) Field Power Supply Error
ply or the wiring. If there is no error, replace the input/
output module.
0201 5523 Execution of Download IOM download is being executed.
There has been an error with the transmitter power sup-
ply inside the input/output module. Check if there are any
0201 5524 errors with the transmitter, the field wiring and the input/
0401 5524 Transmitter Power Error output module setting. The error may have been caused
(*1) (*2) because the two-wire/four-wire setting of the current input
module and the pin setting of the input/output module do
not match.
The I/O module has been stopped due to a request from
0201 5525 (*3) IOM Disabled
a higher level.
The model of the base plate for IOM that is defined in the
Base Plate Model Code Er-
0201 5526 (*4) builder and the model of the actually mounted base plate
ror
do not match. Check the model of the base plate.
The I/O module has detected an error in the communica-
02xx 5542 (xx:
tion with the host, and the fallback operation was execu-
Internal code) Fallback
ted. Check the communication path between the CPU
(*4)
and I/O module.
*1: FIO only
*2: For a channel failure, the error code and the error status will vary depending on whether the I/O module is of a duplex config-
uration or a single configuration.
• The upper error code is for a redundantly configured I/O module, while the lower error code is for a non-redundantly con-
figured I/O module.
• If the input/output module is in a redundant configuration, this error will be an IOM Fail error. In a non-redundant configura-
tion, the error will occur only to the failed channel.
*3: Only style S4 or later of SAI143

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-16
*4: N-IO only

l Recovery from Input/Output module error

The following explains the details of the codes for recovery from input/output module error.

Table H3.1.3-4 Details of codes for recovery from Input/Output module error
Code (hexadeci-
Display Description
mal)
Connector on Field Side The input/output module has recovered from the discon-
0301 5541 (*1)
Recover nection error of the field side connector.
03xx 5542
(xx: Internal Fallback The I/O module has recovered from fallback.
code)
0301 5543 Field Power Supply Recover The field power supply has recovered to a normal state.
0301 5544 Download Completed IOM download has been completed.
The I/O module has recovered from being stopped due to
0301 5545 (*2) IOM Enabled
a request from a higher level.
The output shutoff switch has recovered from operation.
0301 5546 (*1) Output Shutoff
Follow the recovery procedures.
The input/output module started after turning the power
0301 5547 IOM Restart (Power-On)
on.
The transmitter power supply has recovered to a normal
0301 5548 (*1) Transmitter Power Recover
state.
*1: FIO only
*2: Only style S4 or later of SAI143

n Cause of the channel error

The following explains the details of the codes related to channel error. The IOM Report will
display these codes as "Channel status", "The latest channel error" and "Cause of the chan-
nel error detected by the input/output module" in the area where causes of channel errors are
to be displayed.

l Channel status, the latest channel error

"Channel status" in the IOM Report will display the channel status (cause of a channel error)
detected by the CPU. The "latest channel error" is the last error that CPU detected. The de-
tails of the codes are explained in the following table.

Table H3.1.3-5 Details of codes for channel status

Code (hexadeci-
Display Description
mal)
0000 5121 TRNS+ A transmitter high limit error has occurred.
0000 5122 TRNS- A transmitter low limit error has occurred.
0000 5123 IOP+ An input high limit error has occurred.
0000 5124 IOP- An input low limit error has occurred.
Replace the input module.
• SAI143 or SAV144 module
There has been an internal error that the analog input
0000 5125 value is out of the range between -25 % and 125 %.
Ovr Range
0000 5126 • SAT145 or SAR145 module
There has been an internal error that the input value is
either not a number, an infinity or out of the range that
the module can handle.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-17
Table H3.1.3-5 Details of codes for channel status (Table continued)
Code (hexadeci-
Display Description
mal)
A channel error has occurred. Check the display of cause
0000 5127 Ch Fail of the channel error detected by the input/output module
for the cause of the error.
Disconnection of intrinsic safety barrier has been detec-
0000 5128 (*1) IS Barrier Disconnected ted.
Check the connection of intrinsic safety barrier.
Setting error of intrinsic safety barrier has occurred.
IS Barrier Configuration Er-
0000 5129 (*1) Settings information defined in the builder and the con-
ror
nected intrinsic safety barrier may be different.
An error has occurred due to open circuit. Check the field
0000 512a (*1) Open Circuit wiring. A short circuit error is suspected if a barrier is
used.
An error has occurred due to short circuit. Check the field
0000 512b (*1) Short Circuit
wiring.
Other errors (open circuit/short circuit detection by intrin-
0000 512c (*1) Field Side Error sic safety barrier, etc.) have been detected on the field
side. Check the error cause in detailed cause.
*1: N-IO only

l Cause of channel error detected by the Input/Output module (Input/Output

module detection and the details of channel error)
"Cause of channel error detected by the input/output module" will display channel errors de-
tected by the input/output module. Details of the codes are explained.

Table H3.1.3-6 Details of codes for cause of channel error detected by the Input/Output module
Code (hexadeci-
Display Description
mal)
An error has occurred due to open circuit. Check the field
wiring.
0401 5561 Open Circuit In SDV526, open circuit occurs due to a channel fuse
burnout caused by a short circuit. Check the field wiring
and channel fuses.
An error has occurred due to short circuit. Check the field
0401 5562 Short Circuit
wiring.
Short circuit between chan- There is short circuiting between channels. Check if there
0401 5563 (*1)
nels are any field wiring errors.
An output overload has been detected. Check if there are
0401 5564 (*1) Output Overload
any errors with the field wiring or the loading device.
0401 5567 (*1) This is an input error of reference junction compensation
(RJC) in the SAT145. The cause is likely a failure in the
RJC Error thermistor for the reference junction compensation for the
0401 5568 (*1) terminal board. Check if there are any errors in the termi-
nal board.
There has been a voltage error with the field power sup-
0401 5522 (*2) Field Power Supply Error
ply. Check the field power supply and wiring.
Detected an error that activated the DO shutoff switch in
0401 5570 (*2) DO Shutoff the DO channel of S2MMM843 or S2MDV843. Check the
error cause of the DO channel in IOM.
Detected an error that activated the I/O shutoff switch in
0401 5571 (*2) I/O Shutoff the AO channel of S2MMM843. Check the error cause of
the AO channel in IOM.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.1 IOM Report of AIO/DIO modules > H3-18
Table H3.1.3-6 Details of codes for cause of channel error detected by the Input/Output module (Table
continued)
Code (hexadeci-
Display Description
mal)
Open circuit or short circuit is detected in the intrinsic
0401 5572 (*2) Line Fault Detection
safety barrier. Check the field wiring.
Setting error of intrinsic safety barrier has occurred. Set-
IS Barrier Configuration Er-
0401 5573 (*2) tings information defined in the builder and the connected
ror
intrinsic safety barrier may be different.
Disconnection of intrinsic safety barrier has been detec-
0401 5576 (*2) IS Barrier Disconnected ted.
Check the connection of intrinsic safety barrier.
*1: FIO only
*2: N-IO only

If the status of the input/output module is single, the code 04xx xxxx error explained on the
Input/output module hardware failure page is displayed as the cause of the channel error de-
tected in the input/output module.
SEE
ALSO For more information about causes of channel errors, refer to:
“l Input/Output module hardware failure” on page H3-14

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-19

H3.2 IOM Report of communication modules

This section explains the IOM Report on the following communication modules.
• Serial communication module (Modbus slave communication)
• Serial communication module (Subsystem communication)
• Ethernet communication module (Modbus slave communication or DNP3 communication)
• Ethernet communication module (Subsystem communication)
• Fire and gas communication modules (Fire and gas communication)

n Display format of IOM Reports on serial communication modules

(Modbus slave communication)
The display format of IOM Reports when an ALR111 or ALR121 is used for Modbus slave
communication is as follows:
I/O Module:
Node: 2
Slot: 6
Type: ALR111
IOM Model: ALR111-S03 S0U0H0-- F0--

(4-kbyte dump display)

n Display format of IOM Reports on serial communication modules

(subsystem communication)
The display format of IOM Reports when an ALR111 or ALR121 is used for subsystem com-
munication is as follows.
TIP Information of the specified communication module is displayed even when the module is configured as a re-
dundant module.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-20

I/O Module:
Node: 2
Slot: 4
Type: ALR111
IOM Model: ALR111-S03 S0U0H0-- F0--
Serial No: XXXXXXXX

Subsystem Name: (Subsystem name)

Revision: (Subsystem package revision)

IOM Status: (Communication module status) (Detail cause)

Port1 Status: (Port communication status)
Port2 Status: (Port communication status)

Communication Status
1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
11 0000 A3B0 A3B0 A3B0 0000 0001 0001 0001 0001 0001
.
.
(4-kbyte dump display)

In the above example, communication definitions 1 to 11 indicate a normal status, while com-
munication definitions 12 to 14 indicate an A3B0 error. After the communication definition 16,
there is no communication definition or corresponding communication is not performed.

Table H3.2-1 Display items for ALR111/ALR121 in subsystem communication

Display item Description Remark
The name of the subsystem package currently loaded
Subsystem name to the ALR111/ALR121 is displayed. -
(Example) Subsystem Name: S_MODBUS
Subsystem package re- The release number of the subsystem package in the
-
lease number ALR111/ALR121 is displayed.
The status of the communication module is displayed.
• Control: Normal (at single configuration), control
side in the case of a redundant module Refer to the Diagnostic
Detailed causes of com-
• Stand-by: Stand-by side in the case of a redundant information message
munication module sta-
module No. 0081 for the content
tuses
• Fail: Error of the error cause code.
If the module status is "Fail," the detail cause of the er-
ror (error cause code) is displayed.
Displays the port status of port 1 and port 2. "Ready" is
displayed in the case of communication module error.
Port 1/2 communication
• Ready: The serial communication status is normal, -
statuses
or there is no communication definition.
• Error: A serial communication error has occurred.
The communication status is displayed for each com-
munication definition. This item is invalid if the commu-
Communication Status nication module has generated an error. The status in-
(Communication error formation for 128 definitions is displayed.
code for communication 0x0000: The communication status is normal. -
definition n: 1 <= n <=
There is no communication definition, or
128) 0x0001:
communication is not performed.
0xA3XX: Communication error code
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-21
Table H3.2-1 Display items for ALR111/ALR121 in subsystem communication (Table continued)
Display item Description Remark
The area for two definitions is required for SLSEVENT
Communication Status type communication definition for ProSafe-SLS event
(for SLSEVENT type collection.
communication defini- The communication status is
0x0000 0x0000:
tion when subsystem normal. -
communication program
Communication is not per-
S_SLSMOD is used in 0x0001 0x0000:
formed.
ALR121)
0xA3XX 0x0000: Communication error code

SEE
ALSO For more information about Diagnostic information messages, refer to:
Message Number 0081 in 3.1, “Safety Control Station Error Occurrence and Recovery Messages (Mes-
sage Numbers 0001 through 0094)” in Messages Reference Manual (IM 32P02B10-01EN)
For more information about communication error codes displayed under Communication Status, refer to:
• manual for the connected Modbus system
• “■ Communication error code” in D2.1, “Communication specifications” in Engineering Guide Vol. 2
(IM 32P01C20-01EN)

l Reading communication status when using ProSafe-SLS communication

function
When ALR121 is used for ProSafe-SLS communication function, communication status may
be read in a particular way. Communication status for SLSEVENT type communication defini-
tion for ProSafe-SLS event collection is displayed in 4-kbyte that is equal to two definitions of
other type. The detailed example is as follows:

Communication definition of SLSEVENT type

Communication Status
1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
11 0000 A3B0 A3B0 A3B0 0000 0001 0001 0001 0001 0000
21 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
.
.
(4-kbyte dump display)

The circled 14th communication definition is SLSEVENT type and other communication defi-
nitions are types other than SLSEVENT type. Each communication definition corresponds to
the following communication status:

Table H3.2-2 Correspondence between communication definition and communication status

Communication defini- Communication status
tion
1st to 11th Normal communication
12th to 13th Communication error (No response from subsystem)
14th Communication error in SLSEVENT type (No response from subsystem)
15th to 18th No communication
19th to 29th Normal communication

Confirm the correspondence relation between each communication definition and communi-
cation status on the Comm. I/O Definition tab of Communication I/O Builder or the Communi-
cation Group Definition list of Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-22

n Display format of IOM Reports on Ethernet communication modules

(Modbus slave communication or DNP3 communication)
The display format of IOM Reports when an ALE111 is used for Modbus slave communication
or DNP3 communication is as follows:
I/O Module:
Node: 2
Slot: 1
Type: ALE111
IOM Model: ALE111-S03 S0U0H0-- F0--
Serial No: XXXXXXXX

(4-kbyte dump display)

n Display format of Ethernet communication module (Subsystem

communication) IOM report
The following shows the display format of the IOM report if ALE111 is used for subsystem
communication.
TIP Information of the specified communication module is displayed even in the case of redundancy.

I/O Module :
Node : 2
Slot : 1
Type : ALE111
IOM Model : ALE111-S03 S0U0H0-- F0--
Serial No : XXXXXXXX

Subsystem Name : (Subsystem name)

Revision : (Subsystem package revision)

IOM Status : (Communication module status) (Detail cause)

Port Status : (Port communication status)

Communication Status
1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
11 0000 A3B0 A3B0 A3B0 0000 0001 0001 0001 0001 0001
:

(4-kbyte dump display)

In this example, communication definition from 1 to 11 shows “normal”, 12 to 14 shows "A3B0
error" and 16 onwards shows "Communication is not performed”.

Table H3.2-3 ALE111 display items for subsystem communication

Display items Display contents Remarks
Subsystem name Displays the name of the subsystem package that is loaded in
ALE111.
(Example) Subsystem Name: S_MODTCP
Subsystem package Displays the package revision of the subsystem in ALE111.
revision (Example) Revision: R4.01.00
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-23
Table H3.2-3 ALE111 display items for subsystem communication (Table continued)
Display items Display contents Remarks
IOM status The IOM status is displayed. Refer to System
Detailed cause Control: Normal status of non-redundant module, or control side Alarm Message
of redundant modules No.0081 for con-
Stand-by: Standby side of redundant modules tents of error cause
Fail: Failure code.
Detailed causes (error code) of the error are displayed in the
case of "Fail".
Port status The communication status of the port is displayed. Note that
“Ready” is displayed in the case of IOM error.
Ready: Communication is normal or undefined
Error: Communication error has occurred
Communication er- The communication status for each communication definition is
ror code for each displayed. Not valid in the case of IOM error. Displays for 128
communication defi- definitions.
nition 0x0000: Normal communication
0x0001: Undefined communication or no communication
0xA3XX: Communication error code

n Display format for the IOM Report of fire and gas communication
modules
The display format for the IOM Report of S2LP131 is as follows:
I/O Module :
Node : 2
Slot : 1
Type : S2LP131
IOM Model : S2LP131-S01 S0U0H0--F0--
Serial No : xxxxxxxx

Subsystem Name : (Subsystem package name)

Revision : (Subsystem package revision)

IOM Status : (Communication module status) (Detail cause)

Port Status : (Port communication status)

Communication Status
Number Communication Group SS-SCPATH SS-SCOM
1 GS01-001 PV 0000 0000
2 GS01-001 DIAGSTATUS 0000
:
101 GS01-50 PV 0000 0000
102 GS01-50 DIAGSTATUS 0000
:
200

(14-kbyte dump display)

Table H3.2-4 Display items of S2LP131

Display item Description Remarks
Subsystem package Displays the name of the subsystem package that is loaded in
name S2LP131.
(Example) Subsystem Name: S_FGCOM
Subsystem package Displays the revision of the subsystem package in S2LP131.
revision (Example) Revision: R1.01.00
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H3.2 IOM Report of communication modules> H3-24
Table H3.2-4 Display items of S2LP131 (Table continued)
Display item Description Remarks
IOM status The IOM status is displayed. Refer to System
Detailed cause Control: Normal Alarm Message
Fail: Error No.4209 and
Detailed causes (error cause code) of the error are displayed in No.4211 for con-
the case of "Fail". tents of the error
cause codes.
Port status The communication status of the port is displayed. Note that
“Ready” is displayed in the case of IOM Fail. However, “Error” is
displayed when an SS-SCOM error has occurred.
Ready: Communication is normal or undefined
Error: Communication error has occurred
Communication er- The communication status for each communication definition is
ror code for each displayed. Invalid in the case of an IOM error. Displays codes
communication defi- for 200 definitions.
nition 0x0000: Normal communication
0x0001: No communication (*1)
0xA3XX: Communication error code (SS-SCPATH)
0x5AXX: Communication error code (SS-SCOM)
Blank: There is no corresponding data. (*2)
*1: This error code will not be displayed for SS-SCOM. PROFIsafe communication between SCS and GS01 does not have a
status indicating that communication is not completed. Therefore, in the case of SS-SCOM, either 0x0000, which indicates
normal communication, or 0x5AXX, which indicates a communication error, is displayed.
*2: The SS-SCOM column is blank for non-safety data.

SEE
ALSO For more information about Diagnostic information messages, refer to:
• Message Number 4209 in 2.1, “System Alarms (Message Numbers 4101 through 4220)” in Mes-
sages Reference Manual (IM 32P02B10-01EN)
• Message Number 4211 in 2.1, “System Alarms (Message Numbers 4101 through 4220)” in Mes-
sages Reference Manual (IM 32P02B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H4. Displaying I/O channel status> H4-1

H4. Displaying I/O channel status

The I/O Channel Status dialog box displays the states of channels of all input/output modules
of the relevant SCS in the list format.
Channels whose output is disabled can be changed to the output enabled condition as long
as the status is normal, by clicking the [Output enabled] button in this dialog box. Once output
channels are placed in the output enabled condition, the output values of the application logic
are output to the field.

n I/O Channel Status dialog box

On the tool bar of the SCS State Management window, click [I/O Channel Status]. The I/O
Channel Status dialog box appears. If both N-IO I/O modules and FIO I/O modules are instal-
led in SCSP3, their respective status is displayed in the [N-IO] tab and the [FIO] tab.

FIO N- IO

Node Unit Slot Type Comment I/ O 1 . . . . . .8 9 . . . . . . 16

1 1 1 S2MDV843 Dual-Redundant IN . . F
OUT D .F . . .
2 S2MDV843 Dual-Redundant IN
OUT
2 1 S2MMM843 Dual-Redundant IN ........
OUT ........
2 S2MMM843 Dual-Redundant IN
OUT
3 1 S2MMM843 IN F F F F F
OUT F F F F F F F F

Figure H4-1 I/O Channel Status dialog box

l Display of I/O Channel status

Table H4-1 Display of I/O Channel status

Status Character Display color
Normal .
Error F Red
Output Disabled D Blue

The error status indicates that the single channel is faulty and/or the error that activates the
Output Shutoff switch inside the output module has occurred.
The output disable status indicates that the channel is normal but the output value from the
application logic is not sent to the field.
If the I/O module has redundant configuration, the channel status of the control side is dis-
played in the odd number slot, irrespective of the control status during operation. The chan-
nels on the even-number slot are displayed as blank. If the I/O module has redundant config-
uration, Dual-Redundant is displayed in the Comment column.
The status of the primary channel is displayed, if multiple channels are combined in N-IO I/O
module for high current output.
The number of read node configuration information is displayed in the status bar. ALL shows
that configuration information of all the nodes is read.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H4. Displaying I/O channel status> H4-2

l Precautions for forcing functions

Use the following buttons to perform operations in the dialog box.

Table H4-2 Explanation of button names and operations

Button Description
Output enabled Place all channels whose outputs have been disabled in the output enabled state within
the station.
Report Displays the same contents of the I/O Channel Status dialog box in the report dialog box.
Close Close the I/O Channel Status dialog box.

SEE
ALSO For more information about enabling output, refer to:
C8., “Output enable operation” on page C8-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H5. Displaying SCS diagnostic information> H5-1

H5. Displaying SCS diagnostic

information
SCS diagnostic information messages can be checked in the Diagnostic Information window.
The Diagnostic Information window displays diagnostic information messages maintained by
the SCS. Diagnostic information messages are the notifications to the users regarding the di-
agnosis as well as the required necessary actions and maintenance records. From these di-
agnostic information messages, the location where the error occurred, the cause of the error,
the degree of risk, etc., can be identified.
The engineers check the diagnostic information messages for hardware errors, communica-
tion errors, etc., in the safety system, and can examine the error causes by referencing the
diagnostic information message help function.
Usage of SCS diagnostic information is described below.

n Analysis of causes
The Diagnostic Information window allows the user to check diagnostic information messages
generated by the SCS’ diagnostic function to obtain information on how to handle errors from
the Help function. In this way, they are helpful in analysis of causes and maintenance opera-
tions.

n Classifying potential risks

Each Diagnostic information message has an alarm class that is determined by an error con-
dition, the importance of devices, etc. An engineer can classify the degree of potential risk of
the current situation.

n Acknowledgement of diagnostic information

Diagnostic information messages maintained by the SCS can be acknowledged and deleted
in the Diagnostic Information window.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H5.1 Diagnostic Information window> H5-2

H5.1 Diagnostic Information window

The Diagnostic Information window displays diagnostic information messages in a list format
collected from the SCS.

n How to display the Diagnostic Information window

Select a station, I/O node or input/output module, and click [Diagnostic Information] button on
the toolbar of the SCS Status Overview window or the SCS State Management window. Only
diagnostic information messages related to the selected device are displayed in the Diagnos-
tic Information window.
Up to five Diagnostic Information windows can be displayed at the same time, each window
showing the information of an individual station, an input/output module, etc.

n Security of the Diagnostic Information window

If you entered the password for the SCS Maintenance Support Tool when launching the origi-
nal window from which the Diagnostic Information Window was opened, you can perform con-
firmation and deletion operations. If the original window was displayed in read-only status, the
Diagnostic Information window is also opened in read-only status, and operations such as
checking and deleting cannot be performed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H5.2 Diagnostic Information window> H5-3

H5.2 Diagnostic Information window

The Diagnostic Information window is shown as follows.
Toolbar Diagnostic Information
Message

Diagnostic Information-[SCS0101 1.3]

File View Operation Help

Number Date Class Message

4125 12/20/2009 10:26:19.720 AM 1 SCS0101 IOM Channel Error NO.

4125 12/20/2009 10:26:19.720 AM 1 SCS0101 IOM Channel Error NO.
0082 12/20/2009 10:26:17.620 AM 3 SCS0101 IOM Recover F10 NODE
0476 12/20/2009 10:26:09.131 AM 4 SCS0101 IOM Download Complete.
0475 12/20/2009 10:26:04.235 AM 4 SCS0101 IOM Download Start F10.
0082 12/20/2009 10:25:55.320 AM 3 SCS0101 IOM Recover F10 NODE
0459 12/20/2009 10:25:55.320 AM 4 SCS0101 IOM In Service F10 NO.
Information 0476 12/20/2009 10:25:51.931 AM 4 SCS0101 IOM Download Complete.
0475 12/20/2009 10:25:48.388 AM 4 SCS0101 IOM Download Start F10.
Warning 0047 12/20/2009 10:25:36.851 AM 2 SCS0101 LEFT Battery Alarm
4129 12/20/2009 10:25:33.328 AM 2 SCS0101 GPS Interface Unit Error
Alarm marks
0081 12/20/2009 10:25:33.320 AM 1 SCS0101 IOM Fail FIO NODE 0.

Number Date Class Message

30/95

Status bar Number of currently

generated messages

Figure H5.2-1 Diagnostic Information window

The components of the window are explained next.

n Toolbar
The following buttons are provided on the toolbar.

Table H5.2-1 Toolbar buttons

Button Name Description
Print Print diagnostic information messages.

Print preview Display print preview.

Acknowledgement Acknowledge diagnostic information messages.

Deletion Delete diagnostic information messages.

Update Update diagnostic information message display.

Divide the window and display deleted messages in the lower part
Historical
(historical display).
Save Save diagnostic information messages in CSV format.

Help Display help related to the selected diagnostic information message.

n Status bar
The status bar shows the number of currently displayed diagnostic information message and
the total number of generated messages in the following format:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H5.2 Diagnostic Information window> H5-4
• Last number of the currently displayed diagnostic information messages/total number of
generated diagnostic information messages

n Configuration of diagnostic information message

A diagnostic information message consists of the following items.

Table H5.2-2 Items displayed in the Diagnostic Information window

Displayed item Description
Alarm mark Mark corresponding to the alarm class
Number Message number
Time of occurrence The time when a message occurred
Class Alarm class determined within an SCS based on the diagnostic status
Message Diagnostic Information message

IMPORTANT
• With the Diagnostic Information window open and if the number of Diagnostic Information
messages of SCS to be displayed exceeds 5000, there are cases where old Diagnostic
Information messages remain undeleted. If this occurs, click the [Refresh] button on the
tool bar or re-display the Diagnostic Information window.
• Diagnostic Information window shows the messages acquired from the SCS memory by
SENG and the messages sent to SENG by the SCS. After the window is displayed,
SENG starts acquiring messages from the SCS memory (About 15 messages per sec-
ond). The messages acquired and sent by the SCS after the window display are listed on
top of the list, i.e., the list is not in chronological order. To sort the list based on the time,
use the Sort function in the Diagnostic Information window. If you re-display the window
after all the Diagnostic Information is collected, the list is displayed in chronological order.

l Categories of diagnostic information messages

There are two message categories: warning (including recovery) and information. Diagnostic
information messages included in the information category are only notified to the user, for ex-
ample, they include messages that do not notify recovery messages and messages notifying
the number of variables being locked by the forcing function.

l Alarm mark display and diagnostic information message display color

The alarm marks attached to diagnostic information messages vary depending on the alarm
class: the alarm marks flash as long as the messages have not been acknowledged and re-
main illuminated once the messages have been acknowledged. The character strings for di-
agnostic information messages (number, time of occurrence, class and message) are dis-
played in different colors according to the alarm class. The background color and text color
can be specified using Setup Tool.

Table H5.2-3 Message character colors

Alarm mark Category Alarm class Character display color in diagnostic informa-
tion messages
Warning 1 Red

Warning 2 Red

Warning 3 Green

Information 4 (*1)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H5.2 Diagnostic Information window> H5-5
*1: The color set as the text color of Setup Tool (the default color is black).

SEE
ALSO For more information about setup tool, refer to:
A5.3, “Customization of the SCS Maintenance Support Tool window” in ProSafe-RS User’s Guide (IM
32P01B10-01EN)

l Acquisition of diagnostic information messages

Open the Diagnostic Information window to acquire and display one by one from the oldest
messages in the SCS.
Messages generated after opening the window are displayed when they are generated.

l Updating diagnostic information messages

Click [Update] button on the toolbar of the Diagnostic Information window to refresh informa-
tion related to diagnostic information messages and diagnostic information status; the infor-
mation is acquired from the SCS again and the display is refreshed.

l Sorting diagnostic information messages

Click one of the columns in the list view of the Diagnostic Information window to sort diagnos-
tic information messages.
If you click a column once, the messages are sorted in the ascending order. If you click once
again, the messages are sorted in the descending order.
For example, if you want a list of Diagnostic Information messages in reverse chronological
order, click the [Date] column.

l Historical display of diagnostic information messages

Clicking [Historical] button on the toolbar of the Diagnostic Information window split the Diag-
nostic Information window into two parts and the 10 most recently deleted diagnostic informa-
tion messages will be displayed in the lower part. If you click [Historical] button again, the win-
dow split will be released and the display returns to the original.

l Outputting diagnostic information messages to external files

Diagnostic information messages can be saved in files in CSV format.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6. Monitoring by diagnostic information message> H6-1

H6. Monitoring by diagnostic

information message
SCS sends diagnostic information messages for detected faults and for the operation on the
safety functions to notify user of events.
You can confirm the time when a fault occurred and the outline of the cause of the fault by
reading the information provided in the diagnostic information message.
Diagnostic information messages can be checked as system alarm on SENG and HIS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.1 Notification of error level through diagnostic information messages > H6-2

H6.1 Notification of error level through

diagnostic information messages
SCS generates a diagnostic information message to notify you that an error has occurred.
You can view the diagnostic information messages on the HIS and SENG. However, if a fatal
error occurs on an SCS, the CPU of SCS stops; in this case, some diagnostic information
messages may not be sent. Diagnostic information messages contain information regarding
the level of the error detected on the SCS.

n Notification of error level and error status

The status of SCS errors is reported to users through diagnostic information messages. It is
also reported to Application logic. The SCS notification process and details for each error lev-
el is shown as follows:

Table H6.1-1 Error level types and the error status notification process
Error level Diagnostic Information Messages Notification to application logic
Diagnostic information message may not Notification is not possible because the
Fatal error
be notified because the CPU stops. CPU is stopped.
The failure location, cause of error and
Major error The error and output status is notified.
other information are notified.
A representative error state is notified, in-
The failure location, cause of error and stead of an individual error state. An appli-
Minor error
other information are notified. cation logic that utilizes this notification can
be created.

SEE
ALSO For more information about behavior upon the occurrence of an error, refer to:
G2., “Operations and recovery procedures during the SCS error occurrence” on page G2-1

n Alarm classes and diagnostic information messages

Failures of devices and SCS operation information are notified to the user as diagnostic infor-
mation messages. The user can obtain information about the time and location of the error
occurrence as well as the error type from the messages.
• The SCS adds information of the alarm class based on the error level when sending a
diagnostic information message. The SENG displays messages with color according to
the alarm class.

Table H6.1-2 Alarm class

Alarm class Correspondence Meaning of alarm class Example
with error level
Class 1 (serious Fatal error (*1) An error that may cause sys- Error notification of IOM in sin-
alarm) Major error tem shutdown occurs and im- gle configuration.
mediate action by the user is
required.
Class 2 (minor Minor error Notification that requires • Notification of a error of an
alarm) prompt action by the user, IOM on one side of the re-
such as hardware replacement dundant configuration
and remedy of user operation • Notification of variable lock
mistakes although the func- status by the forcing func-
tions for safety continue to tion continuing for longer
work than the specified time
• Alarm sent by the HKU
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.1 Notification of error level through diagnostic information messages > H6-3
Table H6.1-2 Alarm class (Table continued)
Alarm class Correspondence Meaning of alarm class Example
with error level
Class 3 (light alarm) - Notification of recovery from an -
error
Class 4 (notification - Notification of status other than Notification of change of the
alarm) SCS errors to the user security level
*1: Because the CPU stops when a fatal error occurs, the system may fail to generate a diagnostic information message that
indicates the error.

• The time displayed in a diagnostic information message is the time when the SCS detec-
ted an error. The minimum unit of time is millisecond.
• The time information set for an diagnostic information message has the same high accu-
racy as the time information set for SOE information.
SEE
ALSO For more information about the alarm class added to diagnostic information messages, refer to:
Appendix 1., “Alarm Class” in Messages Reference Manual (IM 32P02B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.2 Acknowledging and deleting diagnostic information messages> H6-4

H6.2 Acknowledging and deleting diagnostic

information messages
Diagnostic information messages can be acknowledged and deleted on the toolbar of the Di-
agnostic Information window. If you acknowledge or delete a message, the information about
the operation is written to the SCS.
Messages can be acknowledged/deleted individually or in a batch. The method of acknowl-
edging/deleting messages can be specified using Setup Tool. During the plant operation, ac-
knowledge or delete messages individually.

IMPORTANT
• In the Diagnostic information tab of the Setup tool, if you select [Group] to specify batch
acknowledgement or batch deletion, all diagnostic information messages displayed in the
screen become the target of the acknowledging/deleting operation. Do not use this set-
ting in normal plant operation. Use it only temporarily when testing, etc.
• If the data in the battery backed-up memory on the CPU module is deleted, or if the CPU
module is replaced, be sure to restart the SENG. If not, there are cases where some
messages remain unacknowledged or undeleted in the Diagnostic Information window.

SEE
ALSO For more information about setup tool, refer to:
A5.3, “Customization of the SCS Maintenance Support Tool window” in ProSafe-RS User’s Guide (IM
32P01B10-01EN)

n Operation to acknowledge or delete individual diagnostic

information messages
Acknowledging and deleting the individual messages can be performed using the toolbar on
the Diagnostic Information window.

l Acknowledging individual message

In the Diagnostic Information window, select one diagnostic information message and click
the [Acknowledgement] button; the Acknowledgement dialog box appears.
Click the [OK] button in the Acknowledgement dialog box to acknowledge.
The flashing of the alarm mark stops in the Diagnostic Information window.

Acknowledgement

12/20/2009 9:00:19.501 AM SCS0101 LEFT Battery Alarm

Acknowledge?

OK Cancel

Figure H6.2-1 Acknowledgement dialog box

l Deleting individual message

In the Diagnostic Information window, select one acknowledged diagnostic information mes-
sage and click the [Deletion] button; the Deletion dialog box appears.
Click the [OK] button to delete the diagnostic information message.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.2 Acknowledging and deleting diagnostic information messages> H6-6
After you click the [Deletion] button, the [Acknowledgement] button and [Deletion] button are
disabled for two seconds.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.3 Diagnostic information message help function> H6-7

H6.3 Diagnostic information message help

function
The diagnostic information message help function includes of the Help dialog box provided by
the system and a user-defined action guide.

n Help dialog box

The Help dialog box displays information stored in the Help files related to diagnostic informa-
tion messages (message number, print example, meaning, cause, and so on) provided by the
system.
The Help dialog box can be called in the following manners:
• Select the diagnostic information message in the Diagnostic Information window, and
then click [Help] button on the toolbar.
• Double-click the diagnostic information message in the Diagnostic Information window.
Help information related to the diagnostic information message you double-clicked is dis-
played in the Help dialog box.

Help

Find key

Message number 0046

Recovery from power supply module alarm of safety control station

Example: SCS0101 RIGHT PSU Recover
Meaning: The power supply module of a CPU node (right side in the above
example) of the safety control station (station name = SCS0101)
recovered normally. (This is a recovery message of No.0045.)

Display Guide Cancel

Figure H6.3-1 Help dialog box

• Guide
The [Guide] button is enabled if a user-defined action guide has been defined. Click the
[Guide] button to display the user-defined action guide corresponding to the relevant
message number.

n User-defined action guide

Engineers can share knowledge, information about actions to be taken, know-how’s, etc.
about the given situation by describing them in the user-defined action guide. It is also possi-
ble to attach images to the user-defined action guide.

l Displaying a User-defined action guide

Click the [Guide] button in the Help dialog box to display the User-defined Action Guide.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.3 Diagnostic information message help function> H6-8

l Creating a User-defined action guide

Preparation
Copy the default user-defined action guide on the "Diagnostic Information" tab of "Setup Tool" window.
And then edit the copied default file. Initial file contains comments as a sample.

Create Guide File

The Guide file corresponds to each message can be created with a text editor. The file is html format file so
that images and links with other web pages can be easily put into the file.

Save
It is necessary to keep the file in an external media so as to protect from unpredictable troubles of the system.

Figure H6.3-2 Create User-defined action guide

To display the file corresponding to the relevant message number by clicking the [Guide] but-
ton, it is necessary to label the created guide file with the corresponding message number.
For example, (name="@0001") for message number 0001.
An example of a user-defined action guide file is shown as follows.

Table H6.3-1 User-defined action guide file

<b><a name="@0001"> Message Number: 1</a></b><BR>
CPU module error<BR>
Action: Replace the CPU module. <BR>
Memo: Please contact Mr. XX. xxx-xxxx-xxx

An example of display result of a user-defined action guide file is shown below.

Table H6.3-2 Display result of a User-defined action guide file

Message Number: 1
CPU module error
Action: Replace the CPU module.
Memo: Please contact Mr. XX. xxx-xxxx-xxx

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H6.4 Printing diagnostic information messages> H6-9

H6.4 Printing diagnostic information messages

The diagnostic information message displayed in a window can be printed out. Click [Print]
button on the toolbar of Diagnostic Information window. The class 1 and 2 alarms are printed
out in red and class 3 and 4 alarms are printed out in black.
The information that is printed is described below.

n Title
Window name, printing time and page number are printed on the title bar at the top of the
page.

n Header area
Search condition, message format and description of alarm condition are printed on the first
page only.

n Message
A printing image of a diagnostic information message is shown as follows.

12/20/2009 2:02:44 PM page 1/1

Search condition SCS0101 1.3

Format Alarm mark,Message number,Date,Class,Message

Alarm mark New Alarm:No mark,Acknowledged:A,Deleted:D

4129 12/20/2009 9:00:15.987 AM 2 SCS0101 GPS Interface Unit Error

0081 12/20/2009 9:00:15.980 AM 1 SCS0101 IOM Fail FIO NODE 01 SLOT 05 Code = 5103
0083 12/20/2009 9:00:15.980 AM 2 SCS0101 IOM Configuration Error FIO NODE 01 SLOT 05
0081 12/20/2009 9:00:15.980 AM 1 SCS0101 IOM Fail FIO NODE 01 SLOT 03 Code = 5103
0083 12/20/2009 9:00:15.980 AM 2 SCS0101 IOM Configuration Error FIO NODE 01 SLOT 03
0081 12/20/2009 9:00:15.980 AM 1 SCS0101 IOM Fail FIO NODE 01 SLOT 01 Code = 5103
0083 12/20/2009 9:00:15.980 AM 2 SCS0101 IOM Configuration Error FIO NODE 01 SLOT 01
0451 12/20/2009 9:00:00.465 AM 2 SCS0101 LEFT Control
0005 12/20/2009 9:00:00.465 AM 2 SCS0101 Power ON (Cold Start)

Figure H6.4-1 Printing image of diagnostic information messages

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H7. Vnet/IP bus status> H7-1

H7. Vnet/IP bus status

This chapter explains how to check the Vnet/IP bus communication status

n Overview of Vnet/IP bus status

On the SCS State Management window of the SCS Maintenance Support Tool of SENG, the
bus communication status of the SCSs in a domain can be displayed. Using an application
logic with the control bus status indicator function block (SYS_NETST) can output the bus er-
ror alarm to external alarm lamps for notification.
If integrated with CENTUM system, statuses of all stations of all the domains connected to the
Vnet/IP network as well the routing devices among the domains can be displayed. Vnet/IP
bus status is displayed in the Network Status Display dialog box of the CENTUM HIS. When
the bus status changes, a system alarm message will be generated and output to the HIS.

IMPORTANT
When the network switches are connected in a ring topology, even if one of the cables con-
necting between the switches is disconnected, the Vnet/IP bus status remain normal and no
bus error system alarm will be issued.
To be notified of a ring status, you need to build an FCS application that uses the ring status
signals from the network switches.

TIP For more information about how to build such an FCS application, contact YOKOGAWA.

n Elements of the Vnet/IP bus status

The Vnet/IP bus status shows the communication status of the stations in all domains con-
nected to the Vnet/IP network as well as the devices (such as Layer 3 switches) connecting
domains.
The Vnet/IP bus status consists of the following three elements:
• Bus status in own domain
• Communication status of devices connected between domains
• Bus statuses of other domains

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H7. Vnet/IP bus status> H7-2

The information of a domain is not

Vnet/IP
bus status broadcasted to stations beyond the
domain except the bus status signals.
However, an HIS in another domain
can access the information.

Bus status in Bus status of

own domain other domains

Communication Communication Communication

status between status of devices status between
stations in connected stations in
own domain between domains other domains

Figure H7-1 Elements of the Vnet/IP bus status

l Displaying the station communication status of a domain

Each station in a Vnet/IP domain diagnoses bus statuses mutually using bus 1 and bus 2.
Communication statuses for a station are shown as follows. A dual-redundant station with du-
al CPU modules has the following four types of communication status.
• Control side (*1) communication status between stations
• Communication status between control side (*1) station and standby side station
• Communication status between standby side (*1) station and control side station
• Standby side communication status between the stations
*1: Including non-redundant stations (such as SENG, HIS, SCSP2 with single CPU).

Based on this diagnostic information the communication statuses of all stations in a domain
can be displayed on the HIS Network Status Display dialog box.

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

The Vnet/IP domains communicate with each other using bus 1 and bus 2 and the communi-
cation status can be monitored. On the HIS Network Status Display dialog box, the communi-
cation statuses of devices on different domains can be displayed.
The bus status of one domain is broadcasted to all stations in all domains through the com-
munication between domains.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<H7. Vnet/IP bus status> H7-3

n Priority of the Vnet/IP bus status

The Vnet/IP bus status represents a summary of all communication statuses in the following
order:
• Bus Status in Own Domain
If the bus status of own domain is abnormal, it is reflected in the Vnet/IP bus status. In
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 han-
dled 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 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.
• 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 bus status. However, even if a differ-
ent bus is abnormal in different domains, the Vnet/IP bus statuses of both buses are not
handled as abnormal, and only the status of the bus in which abnormality is detected first
is handled as abnormal.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I. Maintenance> I-1

I. Maintenance
This section describes the procedures and precautions when maintaining ProSafe-RS devi-
ces and field devices, and how to set the system time. It also describes the tools that you can
use during maintenance.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1. Maintenance of devices> I1-1

I1. Maintenance of devices

You must follow the procedures, precautions and all other information specified in this section
with care and consideration when maintaining the ProSafe-RS equipment, software or field
devices.
Before starting the maintenance work of devices, you need to take prior measures to avoid
impact on the field devices due to maintenance. You can use the forcing function and override
function for the prior measures and maintenance.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-2

I1.1 Utilizing the forcing and override functions

during maintenance
For the purpose of SCS maintenance, it may be necessary to fix or forcibly change the input/
output values or values used in application logics. In such cases, the forcing and override
functions can be used.
Forcing allows fixing channel input/output values of I/O modules (locking values) from the
SCS Manager of SENG and forcibly changing the values (setting values). The following items
are the targets of forcing.
• Input/output channels of AIO/DIO modules
• Subsystem communication data
• Safety subsystem communication data
• Variable included in application logic
• Inter-SCS safety communication data
• SCS link transmission data
In addition, it is possible to monitor the lock status in the application logics and forcibly cancel
the lock status by using system function blocks (SYS_FORCE, SYS_FORCE_LT,
SYS_FORCE_BD, SYS_FORCE_SC, SYS_FORCE_SF).
In the case of integration with CENTUM, variable values can be set by overriding them from
HIS.
The following table shows the difference between forcing and override.

Table I1.1-1 Difference between forcing and override

Items where there
is a difference be-
Forcing Override
tween the two
functions
Purpose Maintenance of SCS and debugging of Maintenance of SCS through HIS in the
applications that are done through SENG CENTUM Integration Structure
SCS Security Lev- The security level has to be set to 1 or 0. An override is executable when the security
el level is 2.
Necessity of Pro- Programming is not necessary. Application logic needs to be programmed
gramming with override function blocks.
Designation of Output values can be specified in the I/O When an override is activated during execu-
output values Lock Window, etc. tion of application, the preprogrammed value
is output as an overridden value.
Conditions for Whether or not forcing can be performed A program can be written that enables and
locking a variable depends on the SCS security level. disables override by using a mechanical key
switch or other means.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-3

I1.1.1 Override
In the CENTUM Integration structure, I/O values can be set to a specified value that is differ-
ent from the actual I/O value by operation from HIS while the system is controlled normally by
SCS. This operation is called override.
Override can be executed at an SCS security level of 2.
Executing override requires to create application logic with the override FB.
• There are two types of override FBs. One type is grouping override FB which can handle
override actions in a group. The other is override FB which does not handle override in a
group.
• If the total number of override FBs and grouping override FBs in the ready state for over-
riding exceeds the limit specified by the SYS_OVR function block, a diagnostic informa-
tion message is issued to inform user of it.
• If the total number of overridden override FBs and grouping override FBs exceeds the
limit specified beforehand by the SYS_OVR function block, a diagnostic information mes-
sage is issued to inform user of it.
• If the duration in the ready state for overriding exceeds the limit specified beforehand by
the SYS_OVR function block, a diagnostic information message is issued to inform user
of it.
• If the duration of override exceeds the limit specified beforehand by the SYS_OVR func-
tion block, a diagnostic information message is issued to inform user of it.
• Using the SYS_OVR FB can forcefully cancel override for all variables.
SEE
ALSO For more information about details on managing the override FBs, refer to:
B4.5, “Status management of function blocks used for override” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-4

I1.1.2 Utilization of the forcing function in SCS

maintenance
The forcing function can be used for the following purposes, after all wiring is completed but
before the start of actual operation, as well as during maintenance after starting the actual op-
eration.
• Disconnection of Input/Output Modules
• Maintenance of Input/Output Channels
• Prevention of nuisance tripping caused by inter-SCS safety communication during online
change downloading or offline downloading
SEE
ALSO For more information about prevention of nuisance tripping caused by inter-SCS safety communication during
online change downloading or offline downloading, refer to:
“n Locking Inter-SCS safety communication and SCS link transmission data at online change” on page
E1-27

n Precautions for forcing functions

IMPORTANT
If you lock any internal variable in SCSP3/SCSP2, the application run time becomes longer,
that is, the CPU load increases. You should lock internal variables for engineering and main-
tenance purposes only.

• When physical data of an output channel are changed by forcing, consider possible ef-
fects on the field before performing forcing.
• During forcing, you should avoid conflict with the override operation from HIS.
Check the output values of the SYS_OVR function block to see whether any overridden
instances and instances in a status where they can be overridden exist.
Check the diagnostic information messages indicating that the switch input of an override
FB was turned ON and the diagnostic information messages showing that values were
overridden, and make sure not to affect the same loop unintentionally.
• When displaying variable names in a system alarm, no more than 80 single-byte charac-
ters can be displayed. Choose variable names that do not exceed this maximum length,
so that variables can be identified when locking/unlocking forcing and overriding.
SEE
ALSO For more information about CPU load when internal variables are locked, refer to:
A7.3, “Locking of internal variables and performance in SCSP3/SCSP2” on page A7-10

n Example of procedure for setting data with forcing

1. Set the security level of SCS to 1.
Check that the security level of SCS is set to 1 with the Diagnostic Information Message
2. Lock I/O variables or internal variables.
Check that the names of the locked variables are correct with the Diagnostic Information
Message.
3. Set a value to the I/O variables or internal variables.
Check that the variable names and the data set are correct with the Diagnostic Informa-
tion Message.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-5
4. Check applications with the set data.
5. Set the I/O variables and the internal variables so as not to cause any effects on the ap-
plications when another value to the variables are unlocked.
• Check that the variable names and the data set are correct with the Diagnostic Infor-
mation Message.
• Check that the logical data of I/O variables are the same as the physical data and the
data status is GOOD.
6. Unlock the I/O variables or the internal variables.
Check that the unlocked variable names are correct with the Diagnostic Information Mes-
sage.
7. Set the security level of SCS back to 2.
Check that the security level of SCS is set to 2 with the Diagnostic Information Message

n Locking for online change download

If online change of an I/O module and application logic is required while SCS is in operation,
you must investigate whether there is a need to lock the I/O module to prevent a false trip,
and lock the I/O module if necessary.
The following figure shows the procedure to lock the I/O module prior to online change down-
load.

START

1. Change definition of IOM and applications

2. Set SCS Security Level to 1

3. Lock I/O modules

4. Online Change Download

5. Test modified parts

6. Unlock I/O modules

7. Set SCS Security Level to 2

END

Figure I1.1.2-1 Procedure to lock I/O module prior to online change download

1. The engineer modifies the SCS database with the SCS Manager of SENG and uses the
Integrity Analyzer and Cross Reference Analyzer to analyze the modified application. If
the application logic has also been modified, use the logic simulation test to check the
modifications.
2. Change the SCS security level to Level 1 by using the SCS Security Level Operation Dia-
log.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-6
3. Locking all I/O modules related to online change with the I/O Lock Window is recommen-
ded.
4. Perform an online change download.
5. Start the Debug mode for checking the modified parts.
6. Unlock all locked I/O modules with the I/O Lock Window. At this time, check with great
care whether the output values are changed or not. Finish the Debug mode after unlock-
ing the I/O modules.
7. Return the SCS security level to Level 2 by using the SCS Security Level Operation Dia-
log.

CAUTION
If you change some settings of an output module and perform an online change download to
an SCS in R2.01 or earlier system program release number, you need to prevent the system
from an unexpected shutdown when the value of the output module becomes 0. Preventive
measure should be taken on the field device side in advance.

n Maintenance of input/output channels

When performing maintenance of input/output channels, the forcing function is used to fix the
values of the corresponding channels so as to prevent adverse effect on the operation of oth-
er applications.

n Prevention of nuisance tripping when replacing a faulty module

If a channel of the input module fails in single configuration, the replacement of input module
is required. The forcing function is used to fix input values of all channels to the current values
to prevent nuisance tripping.
Similarly, if a channel of the output module fails in single configuration, the replacement of
output module is required. The forcing function is used to fix the data status of all channels of
the output module to the current values to prevent nuisance tripping in other output modules
that refer to this channel.

n Prevention of nuisance tripping due to online change download

When downloading online changes to the application logic or input/output modules, the forc-
ing function is used to fix output values of all channels that may be influenced by this change,
in order to prevent nuisance tripping.
In downloading online changes to an input/output module online, the forcing function is used
to fix the input/output values of all channels of the corresponding input/output module to the
current values in order to prevent nuisance tripping.

CAUTION
• For the output modules targeted for online change download, field bypasses are required
so as to prevent plant shutdown.
• In online change download of output modules, if the channel status of the module is used
as a reference by another output module, the channel of another output module may mis-
takenly generate a trip signal. To prevent this, the output modules linked to the online-
changed module should be locked during online maintenance.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-7

n Prevention of nuisance tripping due to Inter-SCS safety

communication errors at download
Nuisance tripping due to inter-SCS safety communication errors can be prevented by locking
inter-SCS safety communication when performing online change download and offline down-
load.

CAUTION
Be sure to check that LD (Logical Data) and PD (Physical Data) match when unlocking after
the completion of download operation.
Unlocking in the status where LD and PD do not match may cause nuisance tripping.

l At online change download

In the case of online change download, launch the Inter-SCS Communication Lock Window
from an SCS project in which online change download is to be performed, and then lock sta-
tions on the producing and consuming sides. Nuisance tripping caused by online changes can
be prevented.

l Using Inter-SCS safety communication data lock function at offline

download
When executing offline download of the producer SCS of inter-SCS safety communication, it
is possible to prevent false trips caused by the offline download by locking inter-SCS safety
communication at the consumer stations of the inter-SCS safety communication.
An overview of the locking and the procedure for executing offline download is described as
follows.

OUT • Data IN OUT IN

LD • Safety
NR Lock
information
Offline download
PD
Consumer FB

Output values held Write input only to PD

in LD to OUT and NR

SCS1 SCS2: Station that execute offline download

Figure I1.1.2-2 Example of locking Inter-SCS safety communication at offline download

1. Set the security level of SCS that receives inter-SCS safety communication data from the
SCS that executes offline download to 1.
Check that the security level of SCS is set to 1 with the diagnostic information messages.
2. Lock the consumer FB of the station where offline download is performed using the Inter-
SCS Communication Lock window of the SCS that receives inter-SCS safety communica-
tion data.
Check that inter-SCS safety communication has been locked with diagnostic information
messages.
3. Set the security level of SCS that executes offline download to 0.
Check that the security level of SCS is set to 0 with the diagnostic information messages.
4. Execute offline download.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.1 Utilizing the forcing and override functions during maintenance> I1-8
5. Perform the output enable operation on the SCS that executed offline download.
Check the output enabled status with diagnostic information messages.
6. Check that the logical data and physical data match and that the data status is GOOD in
the Inter-SCS Communication Lock window of the SCS that receives inter-SCS safety
communication data.
7. Unlock the consumer FB in the Inter-SCS Communication Lock window.
Check that the inter-SCS safety communication is unlocked with diagnostic information
messages.
8. Set the security level of the SCS that receives inter-SCS safety communication data to 2.
Check that the security level of SCS is set to 2 with the diagnostic information messages.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-9

I1.2 Maintenance for ProSafe-RS equipment

With SCS, procedures for maintenance vary depending on faults such as when dual-redun-
dant CPU module or I/O module is replaced because of a fault or when a module in a single
configuration fails. Take care for the maintenance procedure not to cause a nuisance tripping
when maintenance is performed during running the plant.

n Actions to be taken upon device errors

When you detect hardware errors by system alarms on HIS or alarm devices such as alarm
lamps that indicate generation of diagnostic information messages, follow these steps:
1. Use the SCS Maintenance Support Tool of the SENG to identify the failed location and
the cause for the error.
2. Repair the failed location.
When a CPU module or I/O module of an SCS stops, you may be required to replace the
module. Replace the module by following the procedure and precautions specified in the
user's manual.
3. Confirm that all hardware devices are working properly either from the SCS State Man-
agement window or by ensuring that the alarm devices have been reset.

l Precautions for ProSafe-RS device maintenance

During the maintenance of ProSafe-RS devices, you must be careful because the devices be-
have as follows:
• It takes about 8 seconds for an I/O module to get back to the normal state when it recov-
ers from a failure such as when applying the power to I/O modules.
• When executing the APC operation for dual-redundant SCS, a COPY message is issued
twice.
• When one power supply module of the "CPU node" fails, not only the CPU node but also
I/O node 1 generates a signal that indicates failure of one power supply module. As a re-
sult, two diagnostic information messages are issued.

n Maintenance of CPU modules

The procedure to be taken when the CPU module fails varies depending on whether the CPU
module is of single configuration or dual-redundant configuration.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-10

l CPU module failure (Single configuration)

START

1. Check failure details

2. Replace module

3. Offline Download

4. Check the date on databases

5. Check normal operation of equipment

6. Enable Output Operation

END

Figure I1.2-1 CPU module failure (Single configuration)

1. The engineer starts the SCS State Management window from SENG of the SCS where a
fault occurs and confirms the diagnostic information message. Confirm the measures
against the fault with the Help Dialog of Diagnostic Information Message and determine
whether to replace the CPU module.
2. If the module needs to be replaced as a result of the step 1, the maintenance personnel
removes the failed CPU module from the node and installs a new CPU module.
3. The engineer executes master database offline download from SENG. (If downloading to
the CPU module has been executed even once, the last application remains in the flash
memory of the CPU module. Be sure to execute master database offline download after
replacing the CPU module.)
4. The CPU module starts after the download is completed.
The engineer displays date of each database for POU DB, Variable DB, System DB and
Integration DB on the Database Validity Check Tool, when the SCS is in waiting mode, to
confirm that latest version is loaded.
5. The maintenance personnel confirm that the CPU module has started normally from the
SCS State Management window in SENG or from LED of the CPU module. Furthermore,
the engineer confirms that all SCS equipment are in normal state with the SCS State
Management window.
6. The maintenance personnel perform the enable output operation from the SCS State
Management window.
SEE
ALSO For more information about details of Output enable operation, refer to:
C8., “Output enable operation” on page C8-1

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-11

l CPU module failure (Dual-redundant configuration)

START

1. Check failure details

2. Replace modules

3. Check normal operation of modules

END

Figure I1.2-2 CPU module failure (Dual-redundant configuration)

IMPORTANT
Do not pull out the CPU module online and turn off the power while the module is writing to
the flash memory. Whether the CPU module is writing can be confirmed by using LED of the
CPU module.

l Password setting in replacing CPU

• If CPU is in dual-redundant configuration and you must replace the standby side, there is
no need to re-set passwords for the work. After the Standby side is replaced, the pass-
words for changing Security level stored in the control side are automatically copied to
the standby side.
• In a single CPU configuration, if the CPU is replaced and programs remain in the memory
on the new CPU module, the CPU starts. Its Operating mode is Waiting, so output value
of application logic is not output to the field.
In this status, press Reset switch, stop the CPU, and offline download the master data-
base. After completion of the download and the CPU is started, set the passwords. The
passwords in the memory on the CPU module is initialized, so there is no need to enter
the previous passwords.
• In a single CPU configuration, if the CPU is replaced and no program remains in the CPU
memory on the new CPU module, the CPU is in a halt status. In that status, offline down-
loads the master database. After completion of the download and the CPU is started, set
the passwords. There is no need to enter the previous passwords.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-12

n Maintenance of I/O modules

If the I/O module generates an error, you must use the IOM Report to investigate the cause
before commencing troubleshooting. Maintenance procedures vary depending on the error
code reported in the IOM Report.
SEE
ALSO For more information about details on IOM Report, refer to:
H3., “Checking diagnostic information by using IOM Report” on page H3-1

l Overview of I/O module maintenance procedure and precautions

The precautions and maintenance procedure when an I/O module has stopped are described
as follows:

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-14
Table I1.2-1 IOM Report error codes possibly caused by failures on the field side
Code (hexadeci- Display Description
mal)
0101 5502 Output Readback Error An error has been detected in the readback process
0401 5502 for the output value.
(*1) Check the field wiring of the analog output module for
any abnormality such as inter-channel short circuit,
and also confirm that the total resistance of all connec-
ted cables and devices does not exceed the allowable
output load resistance of the output module, which is
specified in the General Specifications (GS).
0101 5504 Output Channel Stuck at ON A failure that the output channel is unable to change
0401 5504 from ON to OFF has been detected.
Check if there are any field wiring errors such as inter-
channel short circuit.
0107 5507 IOM Channel Fail There have been some errors with the channel area of
0407 5507 the input/output module.
(*1) Check if there is any input of a signal value at a level
between ON and OFF or chattering.
*1: For a channel failure, the error code and the error status will vary depending on whether the I/O module is of a duplex config-
uration or a single configuration.
• The upper error code is for a redundantly configured I/O module, while the lower error code is for a non-redundantly con-
figured I/O module.
• If the input/output module is in a redundant configuration, this error will be an IOM Fail error. In a non-redundant configura-
tion, the error will occur only to the failed channel.

l Troubleshooting procedure when error is possibly caused by failures on

the field side
If the IOM Report shows an error code that may be caused by a failure on the field side, fol-
low these steps to restore the I/O module:
1. Search for wiring error or failure on the field side.
2. Repair the wiring error or failure on the field side to remove the cause of error corre-
sponding to the error code.
TIP If the cause of error is not on the field side, it is a hardware failure of the I/O module. Follow the procedure for
when the I/O module is faulty.

3. Reset the I/O module that has stopped. Perform one of the following actions based on the
system program release number of the SCS:
• SCS system program release number is R3.02.00 or later
Select the stopped I/O module and execute IOM download manually. IOM reset is
performed at the same time.
TIP IOM reset only covers AIO/DIO modules in non-redundant configuration and standby AIO/DIO modules in du-
al-redundant configuration whose HRDY lamp is off.

• SCS system program release number is earlier than R3.02.00

Pull out and insert the I/O module again. IOM reset is performed.
4. Check that the I/O module has recovered to normal in the SCS State Management win-
dow.
5. After an output module has recovered to normal, perform the output enable operation in
the SCS State Management window.
SEE
ALSO For more information about IOM Download operations, refer to:
I4.5, “IOM Download tool” on page I4-44

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-15

l Procedure for when the I/O module is faulty

Follow these steps when you have determined that there is an I/O module hardware failure:
1. Replace the faulty I/O module with one that operates normally.
2. After replacing the module, perform IOM download.
However, when replacing the standby side of the redundant AIO/DIO modules, you do not
need to execute the IOM download manually if the automatic IOM download is enabled in
the SCS.
TIP To enable automatic IOM download, you must set "Automatic IOM Download" to Enable in the SCS Con-
stants Builder. Once it's set, the SCS automatically downloads configuration information from the control side
module to the standby side module after the module is replaced.

3. Confirm that the replaced module is working properly either from the SCS State Manage-
ment window or by ensuring that the alarm device has been reset.
SEE
ALSO For more information about how to replace the I/O module of the FIO node, refer to:
E4.7, “Replacing FIO I/O modules” in Hardware User's Guide (IM 32P06C10-01EN)
For more information about how to replace the I/O module of the N-IO node, refer to:
E5.3, “Replacing N-IO I/O modules” in Hardware User's Guide (IM 32P06C10-01EN)

n Replacing a fire and gas communication module

Follow these steps when you have determined that there is a fire and gas communication
module failure:
1. In the Communication I/O Lock Window, lock the fire and gas communication module.
2. Remove the failed fire and gas communication module form the node.
3. Insert a new fire and gas communication module in the node.
4. Perform IOM download.
5. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
6. Release the lock of the fire and gas communication module.

n Procedures for changing the single/redundant specification of

AIO/DIO modules installed on the FIO node
Follow these steps to offline change the single/redundant specification of AIO/DIO modules
installed on the FIO node:
1. Disconnect the I/O cables (or terminal blocks) of the modules.
2. If you change two adjacent existing single modules to dual-redundant configuration, pull
out one of the modules and insert it again.
3. Perform either of the following operations:
Operations differ, depending on the engineering method.
• If you are performing RS original engineering, change the definition by using I/O Wir-
ing View and perform offline download.
• If you are performing I/O list engineering, change the definition by using the IOM Def-
inition Editor and perform offline download.
4. Connect the I/O cables (or terminal blocks).

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-16

n Maintenance specific to N-IO nodes

You can perform the following maintenance tasks for N-IO nodes through the NIU mainte-
nance port.

l Periodic maintenance
Follow these steps to stop the SCU for the periodic maintenance of the plant and perform
maintenance of N-IO nodes:

IMPORTANT
Set the security level to 1 or below before stopping the SCU, and then enable the mainte-
nance port.

1. Enable the maintenance port of NIU in the target NIU nodes for maintenance.
2. Perform maintenance work of N-IO nodes, which have an NIU with an enabled mainte-
nance port, by using the FieldMate Validator.
3. Disable the maintenance port of the target NIU after the completion of the maintenance
work, and prohibit access from the maintenance port.
4. Verify that the maintenance ports of all NIU are disabled on SENG or HIS.

l Adding N-IO nodes

Follow these steps to add N-IO nodes to the existing SCU:
1. Configure the node numbers of the N-ESB bus and optical ESB bus in all NIUs that have
been supplied.
2. Use the FieldMate Validator to perform the loop checking, to check the functionalities and
to configure the field device and N-IO I/O module under the N-IO node.
3. Connect to the existing SCU.
4. Disable the maintenance port of the extended NIU to prohibit access from the mainte-
nance port.
5. Verify that the maintenance ports of all NIU are disabled on SENG or HIS.

l Replacing a faulty N-ESB bus module

When one of the redundant N-ESB bus modules installed on NIU has failed, follow these
steps to replace the faulty module:
1. Remove the faulty N-ESB bus module from NIU.
2. Insert the replacement N-ESB bus module to NIU.
3. Disable the maintenance port of the replacement N-ESB bus module to prohibit access
from the maintenance port.
Note that the maintenance port of NIU is automatically disabled if the security level is 2.
However, if the maintenance port is in the maintenance status, the maintenance port re-
tains the maintenance status and does not go into the disabled state even when the se-
curity level is set to 2.
4. Verify that the maintenance ports of all NIU are disabled on SENG or HIS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.2 Maintenance for ProSafe-RS equipment> I1-17

n Behaviors during N-IO node maintenance mode and recovery

procedure
This section describes the system behaviors when an N-IO node is placed in maintenance
mode and the procedure when the node recovers from the maintenance mode.

l Operations during the maintenance mode

When an N-IO node is placed in maintenance mode, the system operates as follows:
• CPU processing
The CPU sets the "input value at error occurrence," which is the value pre-defined in an
I/O parameter by the user, for all input channels of the I/O modules that were installed in
the N-IO node (which is in maintenance mode), and changes the data status to "BAD".
The CPU sets the fail-safe value, which is the value pre-defined in an I/O parameter by
the user, on the physical data for all output channels of the I/O modules that were instal-
led in the N-IO node (which is in maintenance mode), and places the output channels in
output disable status. It also changes the data status to "BAD".
The CPU stops the data update to the I/O module that was installed in the N-IO node
(which is in maintenance mode).
• Error notification
It sends a message when the safety control station status is changed to the maintenance
mode. It also sends a message on recovery that the maintenance mode of the safety
control station status is canceled.

l Recovery procedures
1. Switch the N-IO node from the maintenance mode to the online mode.
Data status returns to GOOD and a maintenance mode cancellation message is sent.
Execute following operation if the output module is installed in the N-IO node.
2. From the SCS Maintenance Support Tool of the SENG, run the output enable operation.
Output values from the application logic are output.
Maintenance mode Output enable
User Operation cancellation operation

Logical 1
data status BAD GOOD
0
All channels of Physical
the N-IO Node Fail-safe value Logical data value
data value

Physical 1
data status BAD GOOD
0

Output from output

Fail-safe value Physical data value
channel of the IOM

Figure I1.2-4 Operations during maintenance mode cancellation

TIP Effective range of recovery operations are limited to I/O modules of N-IO nodes that are connected to NIU in
maintenance mode. Other NIUs that are connected to the target NIU in a daisy chain are not affected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.3 Maintenance of field devices> I1-18

I1.3 Maintenance of field devices

For maintenance of field devices, it is necessary to take measures on the ProSafe-RS side so
as not to cause a nuisance tripping due to field signals changed by maintenance.
The procedure for maintenance of filed devices is as follows.
1. Take required bypass to avoid generating a nuisance tripping due to maintenance.
2. Perform maintenance of field devices.
3. Test field devices.
4. Remove the bypass taken in step 1.
In ProSafe-RS, I/O values related to maintenance are locked with either of the following ways
to avoid a nuisance tripping during maintenance.
• Forcing from SENG
• Override from HIS in CENTUM Integration Structure

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-19

I1.4 Maintenance of field wireless system

devices
The section describes the procedures for maintenance of field wireless system devices.

IMPORTANT
When you download settings to YFGW410 by using FWMC, the YFGW410, wireless field de-
vices on the field wireless subnet, or GS01 may restart, depending on the changes made to
the YFGW410 settings. Therefore, use FWMC to find the devices that will restart and lock the
relevant communication data before you download settings to YFGW410 from FWMC.
A field wireless subnet refers to a field wireless network that consists of YFGW510 and its
subordinate wireless field devices.
The devices that restart and the data to be locked are as follows:
• When YFGW410 will restart
All communication data that is obtained through the YFGW410 that will restart
• When wireless field devices on the field wireless subnet will restart
All communication data that travels through the wireless field devices that will restart
• When GS01 will restart
All communication data of the GS01 that will restart

SEE
ALSO For more information about how to configure YFGW410 and functions of the field wireless management con-
sole (FWMC), refer to:
YFGW410 Field Wireless Management Station (IM 01W02D01-01EN)
For more information about tasks related to field wireless system devices, refer to:
YFGW410 Field Wireless Management Station Read Me First (IM 01W02D01-11EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-20

I1.4.1 Changing the setting information of YFGW410

You must change the setting information of YFGW410 when you change the name of the
PROFINET network name, the update cycle or Watch Dog Timer for PROFINET communica-
tion, or the PROFINET modules to assign to the YFGW410.
To change the setting information of YFGW410, you must download configuration data to
YFGW410 by using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
Follow these steps to change the setting information of YFGW410.
1. Reflect the information of the YFGW410 onto the safety communication I/O list, PROFI-
NET definitions, communication definitions, and applications, etc.
2. In the Communication I/O Lock Window, lock the S2LP131 connected to the YFGW410.
3. Perform an online change download with SCS Manager.
4. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
5. Release the lock of the S2LP131 connected to the YFGW410.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-21

I1.4.2 Replacing YFGW410

To replace YFGW410 when one of a redundant pair of YFGW410 has failed, you do not need
to provide any curing measure on the ProSafe-RS system side.
When both of a redundant pair of YFGW410 have failed, you can replace the YFGW410 by
using the same procedure that you follow to replace a non-redundant YFGW410.
Follow these steps to replace a non-redundant YFGW410:
1. In the Communication I/O Lock Window, lock all of the communication definitions applica-
ble to the YFGW410 being replaced.
2. Remove the failed YFGW410.
3. Attach the new YFGW410.
4. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
5. Release the lock of all of the communication definitions applicable to the YFGW410 that
was replaced.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-22

I1.4.3 Replacing YFGW510

To replace YFGW510 when one YFGW510 in a DuoCast configuration has failed, you do not
need to provide any curing measure on the ProSafe-RS system side.
When both YFGW510 in a DuoCast configuration have failed, you can replace the YFGW510
by using the same procedure that you follow to replace a non-DuoCast YFGW510.
Follow these steps to replace a non-DuoCast YFGW510:
1. In the Communication I/O Lock Window, lock the communications for all communication
definitions relevant to the YFGW510 to be replaced.
2. Remove the failed YFGW510.
3. Install a new YFGW510.
4. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
5. Release the lock of the communications for all communication definitions relevant to the
YFGW510 that was replaced.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-23

I1.4.4 Removing YFGW510

When you remove YFGW510, you must download configuration data to the relevant
YFGW410 by using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
When you make a maintenance plan, consider that it will take a maximum of two minutes after
S2LP131 is stopped until it restarts in order to update PROFINET definitions.
Follow these steps to remove a YFGW510:
1. Delete YFGW510 from the safety communication I/O list, PROFINET definitions, commu-
nication definitions, and other lists and definitions, and application logic.
2. In the Communication I/O Lock Window, lock the S2LP131 connected to the YFGW510
being removed.
TIP The reason for locking S2LP131 is because S2LP131 will be restarted to delete the relevant communication
definitions. The communication definitions must be deleted for the following reasons:
• It is assumed that GS01 is also removed when YFGW510 is removed. If GS01 is removed, communica-
tion definitions for gas concentration or other data must be deleted.
• Even if GS01 is not removed, deletion of communication definitions is required if the system is obtaining
BBR_STATUS of YFGW510.

3. Remove the YFGW510.

4. Using SCS Manager, execute an online change download.
5. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
6. Release the lock of the S2LP131.
SEE
ALSO For more information about how to change PROFINET definitions, refer to:
E1.5.2, “Applying settings by using PROFINET Configurator” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-24

I1.4.5 Adding YFGW510

When you add YFGW510, you must download configuration data to the relevant YFGW410
by using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
When you make a maintenance plan, consider that it will take a maximum of two minutes after
S2LP131 is stopped until it restarts in order to update PROFINET definitions.
Follow these steps to add a YFGW510.
1. Reflect the information of the YFGW510 being added onto the safety communication I/O
list, PROFINET definitions, communication definitions, and application logic.
2. Before you execute an online change download to the SCS, in the Communication I/O
Lock Window, lock the S2LP131 that is connected to the YFGW510 being added.
3. Using SCS Manager, execute an online change download.
4. In the Communication I/O Lock Window, confirm that the physical data status of the input
data is normal.
5. Release the lock of the S2LP131.
SEE
ALSO For more information about how to change PROFINET definitions, refer to:
E1.5.2, “Applying settings by using PROFINET Configurator” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-25

I1.4.6 Changing the setting information (F-Parameter,

communication period) of GS01
The setting information of GS01 includes F-Parameter, which needs to be downloaded to
S2LP131, and the communication period, which needs to be downloaded to YFGW410.
TIP When you change only F-Parameters, downloading of configuration data to YFGW410 is not required.

l Changing F-Parameter
Follow these steps to change the F-Parameter:
1. Reflect the setting information of GS01 onto the safety communication I/O list, PROFI-
NET definitions, and other lists and definitions.
2. In the Communication I/O Lock Window, lock the S2LP131 connected to the GS01.
3. Using SCS Manager, execute an online change download.
4. When the online change download is complete, check that the physical data status of the
input data is GOOD in the Communication I/O Lock Window.
5. Unlock the S2LP131 that you locked in step 2.

l Changing the wireless communication period

When you change the wireless communication period, you must download configuration data
to the relevant YFGW410 by using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
TIP When you change the wireless communication period, you do not need to make any changes in the engineer-
ing of ProSafe-RS. Downloading to SCS and S2LP131 is not required, either.

Follow these steps to change the wireless communication period:

1. Before you download the configuration data to YFGW410 by using FWMC, lock the com-
munication data of the GS01 for which you are changing the communication period from
the Communication I/O Lock Window.
2. When the downloading of configuration data from FWMC is complete, check that the
physical data status of the input data is GOOD in the Communication I/O Lock Window.
3. Unlock the communication data of GS01 that you locked in step 1.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-26

I1.4.7 Replacing GS01

When you replace GS01, you must download configuration data to the relevant YFGW410 by
using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
Follow these steps to replace GS01 when it has failed:
1. In the Communication I/O Lock Window, lock all of the communication definitions applica-
ble to the GS01 being replaced.
2. Remove the failed GS01.
3. Attach the new GS01.
4. In the Communication I/O Lock Window, check that the physical data status of the input
data is GOOD.
5. Release the lock of all of the communication definitions applicable to the GS01 that was
replaced.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-27

I1.4.8 Removing GS01

When you replace GS01, you must download configuration data to the relevant YFGW410 by
using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
Follow these steps to remove a GS01:
1. Delete GS01 from the safety communication I/O list, PROFINET definitions, communica-
tion definitions, and other lists and definitions, and application logic.
2. In the Communication I/O Lock Window, lock the S2LP131 connected to the GS01 being
removed.
3. Remove the GS01.
4. Perform an online change download with SCS Manager.
5. When the online change download is complete, check that the physical data status of the
input data is GOOD in the Communication I/O Lock Window.
6. Release the lock of the S2LP131.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-28

I1.4.9 Adding GS01

Follow these steps to add a GS01. This section explains the procedures for using a user-de-
fined FB to which GASDTR, PSI_I, and PSI_R as shown in the following figure are embedded
as an application for monitoring the gas concentration of GS01 and using the same user-de-
fined FB with the GS01 being added as well.

User definition FB image

PSI_R GASDTR
Convert
V into
Concentration of gas IO_REAL
STS IN HTRP
GS01
LTRP

PSI_I Logic for creating

data status
V
Status of data quality STS

Figure I1.4.9-1 Image of user-defined FB

The flow of tasks is as follows. However, specific operation procedures vary depending on
whether or not iDefine is used.
To add GS01, you must configure YFGW410 as well as ProSafe-RS. Therefore, you must
download configuration data to the relevant YFGW410 by using FWMC.
When to download should be decided through discussion with the engineer of the field wire-
less system.
The wok flow for adding GS01 is described below. If you add GS01 without following this work
flow, the operation starts from the state where GASDTR has latched a trip signal.
1. Perform an online download onto the SCS for a POU other than the one including the
GS01 being added.
2. Perform a forcing of the communication definition being added.
3. Perform an online download onto the SCS for the POU that includes the GS01.
SEE
ALSO For more information about how to configure YFGW410, refer to:
• YFGW410 Field Wireless Management Station Read Me First (IM 01W02D01-11EN)
• YFGW410 Field Wireless Management Station (IM 01W02D01-01EN)

n When using iDefine

Follow these steps when adding a GS01 by using iDefine. Step 1 is a task to be performed
before heading to the site. Step 2 and subsequent steps are tasks performed at the site.
1. Export the SCS project by using AD Organizer.
2. Import the SCS project by using AD Organizer.
In the SCS Import dialog box, select the [Exclude SCS Project Files] check box and per-
form the import.
3. Using RS Generation Manager, select the check box for [Skip the reflection of program
POUs] and then click [Build].

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-29
4. In the Communication I/O Lock Window of SCS Manager, lock the S2LP131 including the
GS01 being added.
Lock all inputs in bulk or lock all communication definitions.
5. Perform an online change download with SCS Manager.
Release the lock of the existing GS01 at any time after this upon confirming that commu-
nication has been restored.
6. In the Communication I/O Lock Window of SCS Manager, run a forcing of the communi-
cation data wired to the GS01 being added into a normal value. At this time, check that
the gas concentration with the physical data in the Communication I/O Lock Window is
within a normal range.
The values subjected to forcing are as follows:
• PSI_R.v (gas concentration): A value which does not exceed the High/Low trip levels
of GASDTR
• PSI_R.sts (status of fire and gas communication): TRUE
• PSI_I.v (data quality status of gas concentration): 128
• PSI_I.sts (status of fire and gas communication): TRUE
7. Click [Build] in RS Generation Manager.
A build process runs for the SCS project.
8. Using Project Comparing Tool, check that the following projects match.
• The original SCS project exported in step 1
• The SCS project that is to be downloaded at the site
9. Perform an SCS online change download by using SCS Manager.
10. Release the lock for every communication definition for which communication with the
added GS01 has been restored.
SEE
ALSO For more information about exporting SCS projects, refer to:
“n Importing SCS projects” on page E2-5
For more information about how to operate RS Generation Manager, refer to:
D4., “Overview of RS generation” on page D4-1
For more information about how to operate Communication I/O Lock Window, refer to:
F8.11, “Communication I/O Lock window” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about Project Comparing Tool, refer to:
F6.3, “Comparing two SCS projects” in Engineer's Reference Manual (IM 32P04B10-01EN)

n When not using iDefine

Follow these steps when adding a GS01 without using iDefine. Procedure 1 is a task to be
performed before heading to the site. Procedure 2 and beyond are tasks performed at the
site.
1. Perform the following tasks:
• Export the SCS project by using AD Organizer.
• Using SCS Manager, export the CSV file of Dictionary, the CSV file of Tag Name
Builder, and the PXF file of the entire project.
2. Perform the following tasks:
• Import the SCS project by using AD Organizer. In the SCS Import dialog box, select
the [Exclude SCS Project Files] check box and perform the import.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I1.4 Maintenance of field wireless system devices > I1-30
• Using SCS Manager, import Dictionary.
• Using RS Generation Manager, run the build process.
3. In the Communication I/O Lock Window of SCS Manager, lock the S2LP131 including the
GS01 being added.
Lock all inputs in bulk or lock all communication definitions.
4. Perform an online change download by using SCS Manager.
Release the lock of the existing GS01 at any time after this upon confirming that commu-
nication has been restored.
5. In the Communication I/O Lock Window of SCS Manager, run a forcing of the communi-
cation definition wired to the GS01 being added.
The values subjected to forcing are as follows:
• PSI_R.v (gas concentration): A value that does not exceed the setting level for the HI
and LO trips of GASDTR
• PSI_R.sts (status of fire and gas communication): TRUE
• PSI_I.v (data quality status of gas concentration): 128
• PSI_I.sts (status of fire and gas communication): TRUE
6. Using SCS Manager, import the PXF file of the entire project.
7. Using SCS Manager, import the CSV file of Tag Name Builder.
8. Perform the build by using SCS Manager.
9. Using Project Comparing Tool, check that the following projects match.
• The original SCS project exported in step 1
• The SCS project that is to be downloaded at the site
10. Perform an SCS online change download by using SCS Manager.
11. Release the lock for every communication definition for which communication with the
added GS01 has been restored.
SEE
ALSO For more information about exporting SCS projects, refer to:
“n Importing SCS projects” on page E2-5
For more information about how to operate RS Generation Manager, refer to:
D4., “Overview of RS generation” on page D4-1
For more information about how to operate Communication I/O Lock Window, refer to:
F8.11, “Communication I/O Lock window” in Engineer's Reference Manual (IM 32P04B10-01EN)
For more information about Project Comparing Tool, refer to:
F6.3, “Comparing two SCS projects” in Engineer's Reference Manual (IM 32P04B10-01EN)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I2. Maintenance of the system> I2-1

I2. Maintenance of the system

This section explains proof tests necessary for maintenance of the system and tests for im-
proving the rate of operation.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I2.1 Proof test> I2-2

I2.1 Proof test

Proof tests are periodic tests for verifying that the functions of safety loops consisting of sen-
sors, logic solvers, and final elements are functioning without failure.
This section explains the proof test for logic solvers (ProSafe-RS).
The subject of this proof test is the operation of each channel of input/output modules.
Change the input value or output value of each channel of the modules and check if the mod-
ules work as intended.
For dual-redundant configurations, conduct the check on both modules.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I2.2 Tests for improving the rate of operation> I2-3

I2.2 Tests for improving the rate of operation

For dual-redundant configurations, check that the dual-redundant switchover takes place
properly in order to improve the rate of operation. This section explains how to check the du-
al-redundant switchover of the CPU module and I/O modules.

n Checking the dual-redundant switchover of the CPU module

1. Press the [START/STOP switch] on the front of the control-side CPU module once to stop
it and make a switchover.
2. Press the [START/STOP switch] of the stopped CPU module again to restart it and place
it in the standby mode.
SEE
ALSO For more information about details on the START/STOP switch of the CPU module and the status display,
refer to:
B4.2, “Processor module” in Hardware User's Guide (IM 32P06C10-01EN)

n Checking the dual-redundant switchover of I/O modules

Using IOM Control Right Switching Tool, check the control right switchover of an AIO/DIO
module in a dual-redundant configuration.
By using this tool, the AIO/DIO module on the control side will switch over to the standby side
while the AIO/DIO module on the standby side will switch over to the control side.
This tool is launched from SENG.
SEE
ALSO For more information about details on the IOM Control Right Switching Tool, refer to:
I4.6, “IOM Control Right Switching Tool” on page I4-47

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I3. Setting system time> I3-1

I3. Setting system time

The system date and time can be set using the Adjust Time dialog box. The date and time
specified in the Adjust Time dialog box are reflected on the SCS connected to the same do-
main and other SENGs. In the case of the CENTUM integration structure, the set date and
time are also reflected on its FCS and HIS. Moreover, when multiple domains are connected
through BCV or CGW and it so specified by the builder, the same date and time can be ap-
plied to the stations in the connected domains too.
The set date and time is applied to the following connected stations:
• Date/time of the local SENG (Windows date/time)
• Date/time of all SCS, FCS and HIS
• Date/time of other SENGs
If an HIS is connected, the time settings made on the HIS are applied to these stations as
well.

IMPORTANT
• If Vnet/IP is applied as the control bus, using SNTP server standard time for time syn-
chronization cannot change the system time from SENG and HIS.
• If V net is applied as the control bus, the Adjust Time dialog box should be used to set
time regardless of what type of time synchronization is applied. When a V net network
and a Vnet/IP network are connected through a V net router that is earlier than style S3, if
the V net router system time transfer is set to [Transfer lower], the system time cannot be
changed from an SENG or HIS on the V net. Moreover, if multiple domains are connected
together through BCV or CGW, and if the BCV system time transfer is set to [Transfer
lower], or the CGW is set to [Receive System Time], the system time cannot be changed
from an SENG or HIS in the lower level domain.

n Adjust Time dialog box

Click [Time Setup] button on the toolbar of the SCS Status Overview window or the SCS
State Management window. The Adjust Time dialog box appears.
Adjust Time

Current

Date 12/20/2009

Time 11:57:57 AM

Setting

Date 12/20/2009

Time 11:58:54 AM

OK Cancel

Figure I3-1 Adjust Time dialog box

The following items are displayed in the Adjust Time dialog box:
• Current
The current system time is displayed in this area.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I3. Setting system time> I3-2
• Setting
The system time can be set in this area.

n How to set the system date and time

The system date and time can be adjusted using the spin boxes in the dialog box and then
click the [OK] button. Click the [Cancel] button if you want to cancel the setting.
If you set the date/time, the date/time of the stations connected to the system are changed.
Note that the date/time format conforms to the Windows standard.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4. Tools for operations and maintenance > I4-1

I4. Tools for operations and

maintenance
You can use the following tools and functions for cause investigation when a system abnor-
mality occurs, or while maintaining SCS devices.
• Message Cache Tool
You can use this tool for carrying out the collection settings of diagnostic information mes-
sages, which are displayed in the Diagnostic Information window or SOE Viewer.
• SOE Viewer
You can use this tool to examine SOE events that are generated in the SCS.
• Master database offline download
You can use this to perform offline download of the SENG master database to the SCS.
• NIU maintenance port setting tool
You can use this tool for switching between the enable and disable status of the NIU
maintenance port.
• IOM Download Tool
You can use this tool to download the configuration information that is stored in the Mas-
ter database to the I/O module.
• IOM Control Right Switching Tool
You can use this tool for switching the control rights of AIO/DIO modules that are operat-
ing in a redundant configuration.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-2

I4.1 Message Cache Tool

Diagnostic information messages displayed in the Diagnostic Information window, and SOE
event messages and trip information displayed in the SOE Viewer, are collected from SCS
stations using the Message Cache Service.
Message Cache Tool is used to display the status of collecting diagnostic information mes-
sages, SOE event information and tripping information, to make various settings of Message
Cache Service and to maintain cache data collected by Message Cache Service including
storage and deletion. It also allows checking the volume of cache data stored on the hard
disk.

SENG, HIS

Diagnostic Information
SOE Viewer
window (SENG only)

Display

Message Cache Tool

Cache data display/

manipulation
Initialization of
tripping information Message Cache Service Cache data

SCS

Figure I4.1-1 Positioning of Message Cache Tool

n Message Cache tool

Message Cache Tool allows you to make the following settings and maintenance operations:
• Setting stations
This setting is required only when caching the messages collected by other stations. The
settings for the local station were completed beforehand.
• Acquisition setting
Make settings related to the SCS selected as the target of collection by Message Cache
Service and the volume of the hard disk to be used
• Display of data acquisition status
Display acquisition status of diagnostic information messages, SOE event messages and
tripping information collected from the SCS by Message Cache Service
• Initialization of tripping information
Initialize tripping information in the SCS
• Manipulation of cache data
Store cache data collected by Message Cache Service in a different folder or delete the
data

n How to launch Message Cache Tool

1. Start Message Cache Tool.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-3
Before the tool is launched, a password check for SCS Maintenance Support Tool is per-
formed.
2. Enter your password.
When Windows authentication mode is set, enter a password. When the Access Control
and Operation History Management Package is applied, enter the name and password of
the engineer.

n Message Cache Tool window

The Message Cache Tool window is shown in the figure as follows.
Message Cache Tool
Menu bar
File View Operation
Toolbar

– STN0162
Diagnostic Information 1/11
– Data Acquisition

SCS0101 9%

– DISK Cache Client area

SCS0101 Event 2/2

– HIS0124
100%
Status of Data Acquisition

DISK Cache
Trip File 1 0/1500

Trip File 2 0/1500

Tree view

Figure I4.1-2 Data Acquisition Status window of Message Cache Tool

The components of the window are explained next.

n Menu bar
The following menus are provided on the menu bar:
• [File] Menu
• [View] Menu
• [Operation] Menu
Menu items provided on each menu are explained as follows.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-4

l File menu

Table I4.1-1 File menu

Menu item Function
Display a dialog box for making various settings related to Message Cache
Setup
Service.
Close Close the Message Cache Tool.

l View menu

Table I4.1-2 View menu

Menu item Function
Toolbar Hide/show the toolbar
Status Bar Hide/show the status bar
Display the Station Setup dialog box for selecting one or more stations on which
Station Setup
Message Cache Service should run
Update Update the window display to the latest status

l Operation menu

Table I4.1-3 Operation menu

Menu item Function
Display the Initialize Trip Information dialog box for the initialization of tripping
Initialize Trip Information
information maintained in SCS.
Display the Save Disk Cache dialog box for saving the contents of the disk
Save Disk Cache
cache in an arbitrary folder.
Display the Delete Disk Cache dialog box for deleting the contents of the disk
Delete Disk Cache
cache.

IMPORTANT
Do not delete the disk cache. If disk cache is deleted by selecting the [Delete Disk Cache]
menu, the cached diagnostic messages and the SOE events will be lost and cannot be dis-
played.

SEE
ALSO For more information about Initialize Trip Information dialog box, refer to:
I4.1.5, “Initialization of tripping information” on page I4-12
For more information about the Save DISK Cache dialog box, refer to:
I4.1.6, “Saving disk cache” on page I4-13

n Toolbar
The following buttons are provided on the toolbar.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-5
Table I4.1-4 Toolbar buttons
Button Name Description
Update Same function as [Update] on the [View] menu

Setup Same function as [Setup] on the [File] menu

Initialize Trip Information Same function as [Initialize Trip Information] on the [Operation] menu

Save Disk Cache Same function as [Save Disk Cache] on the [Operation] menu

Delete Disk Cache Same function as [Delete Disk Cache] on the [Operation] menu

IMPORTANT
Do not delete the disk cache. If disk cache is deleted by selecting the menu [Delete Disk
Cache], the cached diagnostic messages and the SOE events will be lost and cannot be dis-
played.

n Tree view
The tree view displays a list of stations (SENG, HIS) on which Message Cache Service runs.
The following items are displayed for each station.

Table I4.1-5 Display of tree view

Item Description
Click this item to display a list of SCSs that are targets of engineering or opera-
Data Acquisition tion and monitoring on each station (SENG or HIS). Click the name of an SCS
to display the acquisition status of data of the selected SCS in the client area.
Click this item to display a list of SCSs that are targets of engineering or opera-
tion and monitoring on each station (SENG or HIS). Click [Disk Cache] to dis-
DISK Cache play the disk cache usage status (all) for the entire station in the client area on
the right side. Click the name of an SCS to display the disk cache usage status
(SCS) of the selected SCS in the client area.

n Client area
The display in the client area varies depending on the target selected in the tree view.

Table I4.1-6 Display of Client area

Selected target Display
Data Acquisition- SCS Displays the data acquisition status for each SCS.
Displays the disk cache usage status (all) for all SCSs defined as data ac-
Disk Cache
quisition targets.
Disk Cache - SCS Displays the disk cache usage status (SCS) for each SCS.

SEE
ALSO For more information about the details displayed in the data acquisition status, refer to:
I4.1.3, “Displaying data acquisition status” on page I4-8
For more information about the details displayed in the disk cache usage status, refer to:
I4.1.4, “Displaying disk cache usage status” on page I4-9

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-6

I4.1.1 Setting stations

This setting is required only when caching the messages collected by other stations. The set-
tings for the local station were completed beforehand.

n Displaying the Station Setup dialog box

Select [Station Setup] from the [View] menu; the Station Setup dialog box appears.

Station Setup

Computer name
Add

STN0162 Delete
HIS0124

OK Cancel

Figure I4.1.1-1 Station Setup dialog box

n Station setting operations

l Adding stations
1. To add the station (SENG or HIS), enter the computer name of the station in the [Comput-
er name] field.
2. Click the [Add] button.
3. Click the [OK] button.
The computer name of the station you entered is added to the tree view.

l Deleting stations
1. Click one of the computer names displayed in the list in the Station Setup dialog box.
2. Click the [Delete] button.
3. Click the [OK] button.
The selected station is deleted from the tree view.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-7

I4.1.2 Setting Message Cache Service

Message Cache Service collects diagnostic information messages, SOE event messages and
tripping information from the displayed SCS while the Diagnostic Information window or SOE
View is running. If an SCS is set as the target of automatic data acquisition, data is automati-
cally acquired regardless of the running of these windows.
The SCS to be the target of automatic acquisition and the maximum disk cache usage are set
in the Setup dialog box.

n Displaying the Setup dialog box

From the [File] menu of the Message Cache Tool window, select [Setup]. The Setup dialog
box appears.

n Setting items
The following describes the Items that should be set in the Setup dialog box.
• Target of automatic acquisition
Specify an SCS to be the target of acquisition by Message Cache Service. Diagnostic in-
formation messages and SOE event messages of the SCS specified here are collected at
the same time Message Cache Service starts up.
• Maximum Capacity of Disk
The maximum message cache service size needs to be specified according to the actual
usage. Up to the maximum disk capacity can be used for Message Cache Service.

IMPORTANT
Make sure that the disk used for DISK Cache by the Message Cache Service always has
enough free space. (Default Max. Disk capacity: 800 MB) Monitoring for the Maximum Ca-
pacity is performed every 30 seconds. If the disk usage for the disk cache exceeds the Maxi-
mum Capacity, oldest files are deleted to keep the usage rate of the disk cache at 98 % to
100 %. For your information, 1 MB can contain about 8000 Diagnostic Information messages
or 16000 events. The cache file is stored for each station. "SOE including Trip" and "Diagnos-
tic Information messages" are stored separately in the cache file. If you want to keep the old
cache files undeleted, save the files in a separate folder or media from the Save Disk Cache
dialog box. To view the disk cache usage rate, use the Message Cache Tool: click [DISK
Cache] in the tree view.

SEE
ALSO For more information about the details displayed in the disk cache usage status, refer to:
I4.1.4, “Displaying disk cache usage status” on page I4-9
For more information about Saving disk cache, refer to:
I4.1.6, “Saving disk cache” on page I4-13

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-8

I4.1.3 Displaying data acquisition status

Acquisition status of diagnostic information messages, SOE event messages and tripping in-
formation collected from an SCS by Message Cache Service are displayed.

n How to display data acquisition status

To display the data acquisition status, click and expand [Data Acquisition] in the tree view on
the left pane of the window, and then click the name of SCS. The acquisition status of data
collected from the selected SCS by Message Cache Service is displayed in the client area on
the right.

Message Cache Tool

File View Operation

– STN0162
Diagnostic Information 1/11
– Data Acquisition

SCS0101 9%

– DISK Cache

SCS0101 Event 2/2

– HIS0124
100%
Data Acquisition

DISK Cache
Trip File 1 0/1500

Trip File 2 0/1500

Figure I4.1.3-1 Data acquisition status

n Items displayed for data acquisition status

The table below shows the items displayed for data acquisition status.

Table I4.1.3-1 Items displayed for data acquisition status

Displayed item Description
Displays the type of cache data (diagnostic information messages, SOE event
Data Type
messages and two types of tripping information).
Displays the number of items of diagnostic information messages, SOE event
Acquisition Status (Val- messages and tripping information acquired by Message Cache Service before
ue) "/", the diagnostic information messages, SOE event messages and tripping infor-
mation that can be maintained by the SCS are displayed after the "/."
Displays the percentage of data acquired by Message Cache Service with a bar.
Acquisition Status (Bar If no data is maintained by the SCS, "0%" is displayed on the bar. And, the bar is
Display) grayed out if data maintained by the cache service has not been updated for a
certain period of time.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-9

I4.1.4 Displaying disk cache usage status

With Message Cache Service, the cache data is stored on the hard disk until the data volume
reaches the maximum disk cache usage set in the Setup dialog box. This function allows
monitoring the disk cache (hard disk) usage status of Message Cache Service for all SCSs or
each SCS managed by the station (SENG or HIS).

n How to display disk cache usage status

The disk cache usage status is displayed using the following procedure for all or individual
SCSs.
• Display for all SCSs
Click [Disk Cache] in the tree view; the disk cache usage status for all SCSs managed by
the station (SENG or HIS) is displayed.
• Display for each SCS
Select the name of an SCS from the list of SCSs displayed by clicking [Disk Cache] in the
tree view; the disk cache usage status for the selected SCS will be displayed.

n Display for all SCSs

The disk cache usage status for the entire Message Cache Service running on each station
(SENG or HIS) is displayed.

Message Cache Tool

File View Operation

– STN0162

– Data Acquisition DISK Cache (Overall)

SCS0101
0%
– DISK Cache

SCS0101
Maximum capacity 800MB
– HIS0124

Data Acquisition Used size 150.12KB

DISK Cache

Tree view

Figure I4.1.4-1 Disk cache usage status (display for all SCSs)

The table below shows the items displayed for the total disk cache usage status.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-10
Table I4.1.4-1 Disk cache (display for all SCSs)
Displayed item Description
Status of use (Bar
Displays the percentage of the currently used disk space with a bar.
Display)
Displays the maximum disk space that can be used as disk cache. The maximum
Maximum capacity
capacity is set in the Setup dialog box.
Used size Displays the currently used disk cache space.

SEE
ALSO For more information about the Setup dialog box, refer to:
I4.1.2, “Setting Message Cache Service” on page I4-7

n Display for each SCS

The disk cache usage status for the selected SCS is displayed.

Message Cache Tool

File View Operation

– STN0162

– Data Acquisition DISK Cache (SCS0101) :

SCS0101
0%
– DISK Cache

SCS0101
Maximum capacity 800MB
– HIS0124

Data Acquisition Used size 150.12KB

DISK Cache
Diagnostic Information 146.37KB

Event 3.75KB

Figure I4.1.4-2 Disk Cache usage status (Display for each SCS)

The table below shows the items displayed for the each disk cache usage status.

Table I4.1.4-2 Disk cache (Display for each SCS)

Displayed item Description
Status of use (Bar Dis- Displays the percentage of data acquired from the selected SCS out of the disk
play) space with a bar.
Displays the maximum disk space that can be used as disk cache. The maximum
Maximum capacity
capacity is set in the Setup dialog box.
Used size Displays the volume of cache data acquired from the selected SCS.
Diagnostic Information Displays the disk cache space used for diagnostic information messages.
Event Displays the disk cache space used for SOE event messages.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-11
SEE
ALSO For more information about the Setup dialog box, refer to:
I4.1.2, “Setting Message Cache Service” on page I4-7

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-12

I4.1.5 Initialization of tripping information

Use the Initialize Trip Information dialog box to initialize the two types of tripping information
held by the SCS.
After initialization, the SCS will get ready for collecting the tripping information in case the
SCS trip occurs again.

n Displaying the Initialize Trip Information dialog box

Select [Initialize Trip Information] from the [Operation] menu. The Initialize Trip Information di-
alog box appears.

Initialize Trip Information

Station name
SCS0101

Initialization Close

Figure I4.1.5-1 Initialize Trip Information dialog box

n Initialize trip information operation

1. Select the SCS whose tripping information you want to initialize from the drop-down list
box.
2. Click the [Initialization] button.
3. Click the [OK] button in the confirmation dialog box to initialize the tripping information.

IMPORTANT
When initializing the tripping information in a SCS, two files of SCS tripping information will be
initialized together. Before initialization, make sure that the tripping information is saved in the
SENG.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.1 Message Cache Tool > I4-13

I4.1.6 Saving disk cache

Use this function to save the disk cache maintained in Message Cache Service to a separate
folder or medium. The storage destination folder of the disk cache is specified by the Save
Disk Cache dialog box. Saved disk cache can be viewed from SOE Viewer.

n Displaying the Save DISK Cache dialog box

Select [Save Disk Cache] from the [Operation] menu. The Save DISK Cache dialog box ap-
pears.

Save DISK Cache : STN0162

Station name
SCS0101

Cache file
File name SCS Time Stamp Maximum SCS Time Stamp Minimum Select all
0101-02-00-0001.dat 12/20/2009 9:00:15 AM 12/05/2007 9:00:15AM

Folder for storage (a folder with SCS name is added.)

D:\RS-PROJECTS\SCS0101\ Browse...

Save Close

Figure I4.1.6-1 Save DISK Cache dialog box

n How to specify the disk cache storage destination

1. Select a station name in the "Station name" field.
Specify [All SCSs] in the "Station name" box to save the cache data of all SCSs.
2. Select the cache file to be saved from the "Cache file" field.
Specify [Select All] to select all cache files of the specified SCS.
If you have specified [All SCSs] in the "Station name" box , the cache files are grayed out.
3. Select a destination folder in which the disk cache is saved in the "Folder for storage"
field. The folder with the selected SCS name is automatically created.
4. Click the [Save] button.
The disk cache is saved in the specified folder.

SEE
ALSO For more information about how to view the saved disk cache data, refer to:
“l Server Connection” on page I4-27

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-14

I4.2 SOE Viewer

On the SOE Viewer, events of ProSafe-RS can be analyzed. The event log in the specified
SCS is uploaded to be displayed as event messages.
The SOE Viewer functions are as follows.
• The Event log (SOE event information and Diagnostic Information message) stored in
SCS is uploaded to be displayed as event messages.
• Data sources of eight SCSs (including HIS for CENTUM Integration Structure) can be
specified.
• Only event messages that you want to see can be filtered.
• A trip report can be generated. The report can be printed or exported as a CSV file.
• In case of CENTUM Integration Structure, process alarm messages from SCS can also
be displayed.
The SOE Viewer has the following operation modes.
• Event Mode Operation
It displays a list of event messages of SCS.
In the case of CENTUM Integration Structure, HIS historical messages (process alarm
messages of SCS) can also be displayed.
• Trip Mode Operation
It displays a list of trip events of SCS. Detailed information about trip signals are also dis-
played.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-15

I4.2.1 SOE Viewer window

The information managed by SOE Viewer is displayed in either the event mode or the trip
mode. The window structure used in the event and trip modes is the same. This section ex-
plains the structure used for both modes.

n Displaying SOE Viewer

Select [YOKOGAWA ProSafe] > [SOE Viewer].
SOE Viewer is displayed in the event mode.
Menu bar Toolbar Column header

ProSafe-RS SOE Viewer

File Action View
E T
Event Trip Query Filter No Filt Clear Prev Next Up Trip Trip Setup Print Export
Timestamp Quality Type ID Resource Reference Message Scroll bar
12/20/08 19:19:46.094 BSYS 0083-2 SCS0101 SCS0101 SCS0101 IOM Configuration Error FI...
12/20/08 19:19:43.963 BSYS 0081-1 SCS0101 SCS0101 SCS0101 IOM Fail FIO NODE 01 SL... Message
12/20/08 19:19:43.963 BSYS 0083-2 SCS0101 SCS0101 SCS0101 IOM Configuration Error FI... record list
T 12/20/08 19:19:43.963 SOER EVT_TRUE SCS0101 Tank-A Level LLL
T 12/20/08 19:19:43.963 SOER EVT_TRUE SCS0101 Tank-A Press... LLL
12/20/08 19:19:43.963 BSYS 4129-2 SCS0101 SCS0101 SCS0101 GPS Interface Unit Error
12/20/08 19:19:43.963 BSYS 0047-2 SCS0101 SCS0101 SCS0101 LEFT Battery Alarm Status bar

Events 116 to 133 of 270 Sorted by Timestamp Query at 12/20/08 19:20:41 Event Mode

Figure I4.2.1-1 SOE Viewer (Event mode)

After starting the SOE Viewer, no event message is displayed in the message record list since
no data source is specified. The event messages are displayed only after specifying the data
source and running the query.
SEE
ALSO For more information about setting the data source, refer to:
I4.2.2, “SOE Viewer configuration” on page I4-23

n Menu bar
The menu bar provides the following menus.
• [File] menu
• [Action] menu
• [View] menu
Some of the commands in the menu bar are also provided in the toolbar. In addition to the
commands available in the toolbar, the menu bar allows loading and saving property setting
information (SOE Viewer configuration file) of SOE Viewer as well as setting the maximum
number of message records.

l File menu

Table I4.2.1-1 File menu

Menu item Description
Loads the settings made in the SOE Viewer Properties dialog box, which was saved
Load Configuration
by Save Configuration
Saves current settings (SOE Viewer configuration) made in the SOE Viewer Proper-
Save Configuration
ties dialog box
Print Prints all or selected records from the message record list
Export List to file Exports all records from the message record list to a CSV format file
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-16
Table I4.2.1-1 File menu (Table continued)
Menu item Description
Exit Closes SOE Viewer

l Action menu

Table I4.2.1-2 Action menu

Menu item Description
Executes queries based on the current settings made in the SOE Viewer Properties
Execute Query
dialog box because the message record list is not updated automatically
Clear List Deletes the current message record list
Applies filtering set in the SOE Viewer Properties dialog box to the current message
Filter Results
record list
No Filter/Remove
Removes filter restrictions from the current message record list
Filter
Sets the maximum number of message records that can be retrieved by a query from
one data source. If this limit is exceeded, remaining records are discarded and a
Set Max Records
warning message is generated (the setting range is from 10 to 65535, the default val-
ue is 10000). (*1)
*1: The following dialog box appears if this menu item is selected.
Set Max Records per DataSource

OK
10000
Cancel

l View menu

Table I4.2.1-3 View menu

Menu item Description
Event Mode Changes the SOE Viewer display to the event mode
Trip Mode Changes the SOE Viewer display to the trip mode
Prev Page Scrolls the list to display records in the previous page
Next Page Scrolls the list to display records in the next page
Go up one level Returns the display to the trip mode from the trip detail display
Prev Trip Displays trip detailed display of the previous trip trigger event
Next Trip Displays trip detailed display of the next trip trigger event
Toolbar Shows or hides the toolbar
Status Bar Shows or hides the status bar
Warning/Error Log Displays the Warning/Error Log dialog box of SOE Viewer
Properties Displays the SOE Viewer Properties dialog box

n Toolbar
The toolbar of SOE Viewer has the following buttons.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-17
Table I4.2.1-4 Toolbar buttons
Button Name Button Name

E [Event Mode] Button [Next Page] Button

Event Next

T [Trip Mode] Button [Up to Trigger List] Button

Trip Up

Query
[Execute Query] Button Trip
[Prev Trip Detail] Button

[Filter data] Button Trip

[Next Trip Detail] Button
Filter

[Clear Filter] Button [Properties] Button

No Filt Setup

Clear
[Clear List ] Button Print
[Print] Button

Prev
[Prev Page] Button Export
[Export data] Button

l Event Mode button

This button provides the same function as [Event Mode] in the [View] menu.
The [Event Mode] button switches the display of SOE Viewer to the event mode. SOE Viewer
remains in the event mode until the [Trip Mode] button is clicked. The [Event Mode] button
cancels the operation activated by clicking the [Trip Mode] button. In the event mode, if a
query is made, messages are retrieved from up to eight data sources specified in advance.
SEE
ALSO For more information about Event mode, refer to:
I4.2.3, “Event mode operation” on page I4-32

l Trip Mode button

This button provides the same function as [Trip Mode] in the [View] menu.
The [Trip Mode] button switches the display of SOE Viewer to the trip mode. SOE Viewer re-
mains in the trip mode until the [Event Mode] button is clicked. The [Trip Mode] button cancels
the operation activated by clicking the [Event Mode] button. In the trip mode, if a query is
made, trip trigger events are retrieved from the trip signal file of SCS and displayed.
SEE
ALSO For more information about Trip mode, refer to:
I4.2.4, “Trip mode operation” on page I4-35

l Execute Query button

This button provides the same function as [Execute Query] in the [Action] menu.
The [Execute Query] button uploads all event logs matching the date/time and data source
parameters specified in the SOE Viewer Properties dialog box from an SCS. Event logs are
filtered and displayed in the message record list of SOE Viewer as event messages.
If one or more data sources have been set, the [Execute Query] button can be used in both
the event mode and the trip mode.

l Filter Data button

This button provides the same function as [Filter Results] in the [Action] menu.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-18
The [Filter data] button displays in the message record list only event messages matching the
filter parameters specified in the SOE Viewer Properties dialog box. If the filtering is set anew
or changed, it is applied to the result of the current query and the display is updated. The
[Filter data] button is only enabled when there are event messages in the message record list.

l Clear Filter button

This button provides the same function as [No Filter/Remove Filter] in the [Action] menu.
The [Clear Filter] button displays all event logs uploaded from an SCS as the result of the pre-
vious query as event messages in the message record list. It is not necessary to perform a
query anew. The [Clear Filter] button is only enabled when the display has been filtered.

l Clear List button

This button provides the same function as [Clear List] in the [Action] menu.
The [Clear List] button deletes the message record list. Generate a new query command to
retrieve and display event messages from an SCS again.
The [Clear List] button is only enabled when there are messages in the message record list.

l Prev Page button

This button provides the same function as [Prev Page] in the [View] menu.
The [Prev Page] button scrolls the display so that the records in the previous page of the
message record list are shown.

l Next Page button

This button provides the same function as [Next Page] in the [View] menu.
The [Next Page] button scrolls to the records on the next page of the message record list.

l Up to Trigger List button

This button provides the same function as [Go up one] level in the [View] menu.
The [Up to Trigger List] button returns the display from the trip detail display to the trip mode.
The [Up to Trigger List] button is active in the Trip Detail display only.

l Prev Trip Detail button

This button provides the same function as [Prev Trip] in the [View] menu.
The [Prev Trip Detail] button displays the previous trip trigger event generated in the trip detail
display. The [Prev Trip Detail] button is active in the Trip Detail display only.

l Next Trip Detail button

This button provides the same function as [Next Trip] in the [View] menu.
The "Next Trip Detail" button displays the next trip trigger event generated in the trip detail
display. The "Next Trip Detail" button is active in the Trip Detail display only.

l Properties button
This button provides the same function as [Properties] in the [View] menu.
The ["Properties] button displays the SOE Viewer Properties dialog box. This dialog box is
used to configure properties for the operations of SOE Viewer.
SEE
ALSO For more information about the SOE Viewer Properties dialog box, refer to:
I4.2.2, “SOE Viewer configuration” on page I4-23

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-19

l Print button
This button provides the same function as [Print] in the [File] menu.
The [Print] button prints out event messages included in the message record list. The [Print]
button is only enabled when there are messages in the message record list.
SEE
ALSO For more information about Print button, refer to:
“n Printing” on page I4-32

l Export data button

This button provides the same function as [Export List to file] in the [File] menu.
The [Export data] button exports event messages included in the message record list, to a
CSV format file. The [Export data] button is only enabled when there are messages in the
message record list.
SEE
ALSO For more information about Export button, refer to:
“n Exporting” on page I4-33

n Message record list

The message record list executes queries and displays event messages uploaded from an
SCS in response to the queries. Each line represents one event message.

l Message color
The messages of trip trigger events are colored so that they can easily be distinguished from
other event messages. User can specify the colors in the SOE Viewer Properties dialog box.
Trip Trigger T 12/20/08 12.2... Alarm Legend 1 22

Figure I4.2.1-2 SOE message color code

Table I4.2.1-5 SOE message colors

Record type Background color Icon Text color
Trip Trigger Yellow (default) Yellow circle with black "T" Black
All Others White (Windows default color) None Black

SEE
ALSO For more information about the SOE Viewer Properties dialog box, refer to:
I4.2.2, “SOE Viewer configuration” on page I4-23

l Sorting messages
Messages can be sorted in ascending or descending order using the upward and downward
arrows in the column header.
Timestamp

Figure I4.2.1-3 Sorting by timestamp (sorting in ascending order)

Timestamp

Figure I4.2.1-4 Sorting by timestamp (sorting in descending order)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-20

l Changing column width

If the width of a column or column header is too narrow to display the entire data and/or cap-
tion, as many characters as possible are displayed and the omitted characters are represen-
ted by an omission symbol (...).
The width of the columns can be changed by dragging the vertical boundary line between col-
umn headers.
Double-click the boundary line between column headers to adjust to the optimum width.

l Changing display order of a column

To change the display order of a column, click the column header, keep the mouse button
pressed and drag and drop it to the desired position.
TIP The specified sorting order, column width and column order are saved in the SOE configuration file. These
settings are restored when the SOE Viewer configuration file is uploaded using [Load Configuration] of the
[File] menu.

n Status bar
Events 1 to 6 of 424 [F] Sorted by Timestamp Query at 12/20/08 09:25:28 Event Mode

Figure I4.2.1-5 Status bar

The status bar is displayed at the bottom of the window. The status bar has four frames that
display information related to the currently displayed message record list. The user can
change the display width of the frames.
The information shown in each frame is explained as follows, starting from the leftmost frame.
• The total number of messages uploaded by a query from an SCS and the range of mes-
sages currently displayed
If one or more filters are applied to the event messages displayed in the message record
list, [F] is added at the end of the first status bar frame.
For example, if a filter restricts the records to be displayed to 424 messages and each
page displays 6 messages, the first frame of the status bar shows "Events 1 to 6 of 424
[F]."
• The column name currently used as the sorting key
• Date and time when the query was executed
• Display mode
There are two display modes: fixed messages and temporary messages.
The fixed messages indicate the current operating mode.

Table I4.2.1-6 Fixed messages

Message Description
Event Mode Indicates that SOE Viewer is in the event mode.
Trip Trigger Mode Indicates that SOE Viewer is in the trip mode.
Trip Detail Indicates that SOE Viewer displays trip details. Reference information related
[Reference] to the current trip trigger event is also displayed.

The temporary messages indicate the current status during execution of a query.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-21
Table I4.2.1-7 Temporary messages
Message Description
A query to a data source is being executed and SOE Viewer is waiting for the query
Processing Query..
result.
Results of a query have been received and the Viewer is loading the messages into
Loading Data..
the dedicated memory.
Filtering Data.. The Viewer is filtering messages for display.

If a warning or error condition is generated during the operation of SOE Viewer, an exclama-
tion mark icon is displayed in the display mode frame of the status bar.
Double-click the exclamation icon; the Warning/Error Log dialog box appears and displays
warning and error message information. Click a message displayed in the Warning/Error Log
dialog box to see the detailed information.

Figure I4.2.1-6 Exclamation icon

SEE
ALSO For more information about warnings and error messages, refer to:
I4.2.5, “Troubleshooting SOE Viewer” on page I4-37

n Event Detail dialog box

The Event Detail dialog box displays detailed information about event messages selected in
the message record list. To display the Event Detail dialog box for messages displayed in the
event mode or the Trip Detail Display window, double-click an event message or press the
[Enter] key on the keyboard in the message record list.
Event Detail

Date: 12/20/08 15:02:33:310

Previous
Quality:
Next
Type: BSYS
Server: SCS0101 [SCS]
ID: 0081-1
Resource: SCS0101
Reference: SCS0101

Message:
SCS0101 IOM Fail FIO NODE 01 SLOT 01 Code=5103

Figure I4.2.1-7 Event Detail dialog box

The information of data sources displayed in the Event Detail dialog box is summarized as
follows.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-22
Table I4.2.1-8 Event detail items
SOE event information
Event de- Diagnostic in- HIS historical
Description Internal
tail items DI DO AI formation information
variable
Date and time
when a message is
generated. The
date format is
specified in the
SOE Viewer Prop-
erties dialog box. Time at which Time at which
The time is dis- Time at which the SOE event informa- the alarm is the alarm is
Date (*1)
played using the tion was generated in the SCS generated in generated in
format hh:mm:ss:ttt an SCS an SCS
where:
hh = hours (24
hours),
mm = minutes,
ss = seconds
and ttt = ms.
Time synchroniza-
I, B, V,
tion information
Quality <Blank> - - -
when an event oc-
(*2)
curs
BSYS (diag- Message cat-
nostic infor- egory (Exam-
Type Message type SOER (SOE event information)
mation mes- ple: BSYS,
sage) BPRO) (*3)
Name and type of
Server SCSddss HIS computer
the server that out- SCSddss [SCS](*4)
[Type] [SCS] (*4) name [HIS]
put a message
Message ID-
Message ID-
EVT_TRUE alarm class or
ID Message identifier alarm class
EVT_FALSE alarm priority
(e.g., 0047-2)
(e.g., 1101-1)
Message reference
Resource Station name (SCSddss) (*4)
station name
Comment entered Any character
Special reference Station name,
Reference for the input/output string assigned to Station name
point of message tag name
variable a function block
Data
Data
value,
value,
numeri-
Data value, numeri- charac- Message Message
cal val-
Message Message itself cal value (TRUE, ter character character
ue,
FALSE) string string string
BOOL,
(e.g.,
DINT,
HTRP)
REAL
*1: "Timestamp" is displayed in the SOE Viewer window either in event mode or trip mode.
*2: The status of time synchronization on DI event generation is indicated with the following characters.
I: Not synchronized with the standard time.
B: Synchronized with the standard time but synchronization signals are not provided for some reason.
V: Not synchronized with the time on the SNTP server.
<Blank>: Synchronized with the IRIG-B signal when connected to an IRIG-B. Synchronized with the time on the SNTP server
when an SNTP server is used on Vnet/IP.
*3: BSYS indicates a system alarm message and BPRO indicates a process alarm message.
*4: In SCSddss, dd indicates the domain number and ss indicates the station number.

To see event details of the previous message in the message record list, click the [Previous]
button or press the [P] key on the keyboard. To see event details of the next message in the
message record list, click the [Next] or press the [N] key on the keyboard. Click the [Close]
button to close the Event Detail dialog box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-23

I4.2.2 SOE Viewer configuration

The data source settings for SOE Viewer is made in the SOE Viewer Properties dialog box.
This section explains the operations performed in the SOE Viewer Properties dialog box:
specifying of data sources and date ranges, filtering standards to be applied and general set-
tings for SOE Viewer.

n How to display the SOE Viewer Properties dialog box

Click [Properties] button in the toolbar or select [Properties] in the [View] menu; the SOE
Viewer Properties dialog box appears.

n General tab
The following items are specified in the "General" tab.
• Display or hide the Toolbar
• Select the toolbar icons to use small or large
• Display or hide the Status Bar
• Choose the SOE message color settings
• Display/suppress the Warning/Error Log dialog box
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

Tool Bar Settings

Display tool bar

E
Size: E Small Large
Event

Status Bar Settings

Display status bar

SOE Message Color

SOE-H Message [foreground]

Trip Trigger [background]

Messages
Display warnings as popup messages

OK Cancel Apply

Figure I4.2.2-1 General tab of SOE Viewer Properties dialog box

l Tool bar settings

To display the toolbar, select the [Display tool bar] check box. To display only tool buttons on
the toolbar, select the [Small] radio button for "Size." To display tool buttons along with an
identifying caption, select the [Large] radio button for "Size."

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-24

Figure I4.2.2-2 Small button

Query

Figure I4.2.2-3 Large button

l Status bar settings

To display the status bar, check the [Display status bar] check box.

l SOE message color

Select the background color of trip trigger events in this section. Click the downward arrow to
display the color picker. Use the color picker to select the desired color. The default back-
ground color for trip trigger events is yellow.

Other...

Figure I4.2.2-4 Color picker

l Messages
Select the [Display warnings as popup messages] check box to notify about query warnings
via an interactive pop-up dialog box. If this check box is not selected, it becomes necessary to
display the Warning/Error Log dialog box to view query warnings.

n Date/Time tab
The "Date/Time" tab is used to specify the range of date and time of messages uploaded from
an SCS by the query in the event mode or the trip mode. The date/time format is also speci-
fied in this tab.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-25
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

Date/Time Filter

All
Specified Range

MM/dd/yy HH:mm:ss
Start: 12/20/08 00:00:00
End: 12/20/08 15:14:00

Past 24 Hours

Date Format

Selected date format will be used for both display and data entry
purposes.Time display will always default to HH:mm:ss.nnn

MM/dd/yy

OK Cancel Apply

Figure I4.2.2-5 Date/Time tab of the SOE Viewer Properties dialog box

l Date/Time Filter
The date/time filter can be specified in the following manners:
• [ALL]
• No date range is specified. All event messages that have occurred within the past one
year are displayed as a result of query for each data source. Note that the number of
event messages displayed is limited by the maximum number of records. When the num-
ber of total messages exceeds the maximum number of records for display, the latest
messages cannot be displayed. In this case, a criterion with specified dates should be
used for displaying the messages. Select [Specified Range] or [Past] if you want to dis-
play messages that have occurred within a specific period.
• [Specified Range]
A specific date/time range is specified as the target period of queries. This range can be
specified by the start date/time or the end date/time, or both. To include a start or end
date/time in the definition of the specific range, select the relevant check box. If the start
date/time is not specified, the date/time of the oldest event saved in an SCS is set as the
start date/time. If the end date/time is not specified, the date/time of the most recently
generated event message is set as the end date/time.
To change the start or end date, enter a new date or click the downward arrow on the
right side of date/time; a calendar appears. The current date is highlighted in red. Click
the desired date.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-26
July, 2009
Sun Mon Tue Wed Thu Fri Sat
28 29 30 1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31 1
2 3 4 5 6 7 8
Today:7/24/09

To change the start time or end time, enter the time using 24-hour format.
Figure I4.2.2-6 Calendar

TIP The values of currently selected date/time unit (i.e., hours or minutes) can be increased or decreased by
pressing the [+] or [-] key on the keyboard.

• [Past]
A range of messages generated in the past is specified as the target period of queries as
the time span of hours or days. The time span is specified in units of minutes, hours, or
days. If 0 days are specified, events and alarms generated at 0:00 a.m. of the current day
and onward are uploaded from the SCS in question. If a number of days is specified, the
target hours start from 0:00 of the day. For example, if 1 day is specified, the target hours
start from 0:00 a.m. the day before.

l Date Format
All dates within SOE Viewer are displayed using the date format specified here. Select a de-
sired date format from the pop-up list. The following formats are available.
MM/dd/yy, dd/MM/yyyy, MM/dd/yyyy,
d-MMM-yy, dd/MM/yy, d-MMM-yyyy
Example 1: 30/10/2009
Example 2: 30-OCT-2009
TIP If the message record list or the Event Detail dialog box is being displayed, the setting of the date format is
reflected the next time a query is executed.

n Data Source tabs

Eight "Data Source" tabs are prepared for the data sources; they are used to specify the data
source and type of event messages.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-27
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

1 2 3 4 5 6 7 8

Server Connection

Not Used

Used Server: SCS0101

Type: SCS Events

User ID (UID): sa

Password (PWD):

Use Specific Database

Database:

Message Source(s)
Alarms Events

OK Cancel Apply

Figure I4.2.2-7 Data Source tab of SOE Viewer Properties dialog box

TIP To disable a server temporarily, select [Not Used]. Other settings made for the server are not deleted.

l Server Connection
A data source is specified by entering a station name of an SCS. When the user executes a
query, event logs are uploaded from the specified SCS and displayed in the event mode in
SOE Viewer as event messages. To specify a data source, select [Used Server].
In the case of a CENTUM integration structure, HIS historical information (process alarms of
an SCS) can also be specified as the data source. To do so, enter the computer name of HIS
into the [Used Server] field. If you want to view the cached data saved using the Message
Cache Tool, enter into the [Used Server] field the full path to the folder where the cash data is
stored.
The setting items for Server Connection are shown in the table as follows.

Table I4.2.2-1 Server Connection setting items

Setting item SCS event message HIS historical information
Used Server SCSddss (*1) or full path to the folder HIS computer name
where the cash data is stored
Type SCS Events CENTUM HIS Log
*1: Specify a domain number for dd and a station number for ss in SCSddss.

If the data source is not used, select [Not Used] to avoid a generation of error messages.

l Message Source(s)
Specify the type of event messages retrieved from an SCS by a query.
If the [Alarms] check box is selected, diagnostic information messages are the target of col-
lection. If the [Events] check box is selected, SOE event information are the target of collec-
tion. Select either the [Alarms] or [Events] check box, or both. Both check boxes are selected
by default.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-28

n Source Filter tab

If a query is executed with the date range specified in the "Date/Time" tab while one or more
filter parameters are specified, the filter is applied to event messages displayed in the mes-
sage record list. Filter parameters can be specified for each data source. These filter parame-
ters are automatically applied to the current query result. It is not necessary to execute a
query anew in SOE Viewer even if filter parameters are changed.

l Server Connection
This section displays the server name and the type of data source related to the filter speci-
fied in this tab. These fields are grayed out and cannot be changed.
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

1 2 3 4 5 6 7 8

Server Connection
Server: HIS1649 Type: CENTUM HIS Log

Message Type
All BSYS
Selected BPRO
BSEQ
All Types
No Types

Patterns
Not Used Used
Message ID

Resource

Reference

Message Body

OK Cancel Apply

Figure I4.2.2-8 Source Filter tab of SOE Viewer Properties dialog box (example when Server Type is
CENTUM HIS log)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-29
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

1 2 3 4 5 6 7 8

Server Connection
Server: SCS0101 Type: SCS Events

Message Type Quality Type

All SOER All (Normal)
Selected BSYS Selected

All Types All Types

No Types No Types

Patterns
Not Used Used
Message ID

Resource

Reference

Message Body

OK Cancel Apply

Figure I4.2.2-9 Source Filter tab of SOE Viewer Properties dialog box (example when Server Type is
SCS events)

l Message Type
It is possible to select the messages displayed in SOE Viewer according to the specific mes-
sage types. The lists of event messages to which the message type selections are applied
are automatically executed from the data source during a query.
• [All]
Select all message types without restrictions.
• [Selected]
Restrict the display to only the specified message type. Check the check box of the de-
sired type.
[All Types]: Select all message types at once.
[No Types]: Deselect all message types at once.

l Quality Type
This filter is only valid when the server type is SCS Events.
It is possible to select the event messages displayed according to the quality of the attached
time stamp information.
• [All]
Select all quality types without restriction.
• [Selected]
Restrict the display to only the specified quality type. Check the check box of the desired
type.
[All Types]: Select all quality types at once.
[No Types]: Deselect all quality types at once.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-30

l Patterns
It is possible to select the event messages displayed to those including the character string
pattern specified in the relevant field.

Patterns
Not Used Used
Message ID 1101* 1102*

Resource *SCS0101

Reference

Message Body 1 System

Figure I4.2.2-10 Source Filter tab (Patterns)

• [Not Used]
No selections related to character string patterns are applied.
• [Used]
Selections related to character string patterns are applied. Specify the desired patterns to
be matched.
It is possible to use wildcards of asterisks (*) and question marks (?) in the character string
patterns. "*" placed in front of a character string indicates any number of arbitrary characters
before the character string. If an asterisk is placed after a character string, the wildcard indi-
cates any number of characters after the character string. "?" is a wildcard indicating one arbi-
trary character.
If multiple character string patterns are specified for one pattern type (e.g., multiple character
string patterns are specified for Message ID only), the filtering result includes all messages
matching any of the specified patterns (patterns are combined using OR condition).
If two or more pattern types are specified (e.g., a character string pattern is specified for Mes-
sage ID and Resource), the result includes only messages that match all of the specified pat-
terns (patterns are combined using AND condition).
In the pattern example shown in the previous figure, all messages satisfying the following
conditions are displayed:
Message(s) "whose message ID starts with 1101 or 1102" and "whose resource name ends
with SCS0101" and "whose message text includes ‘1’ or ‘System’ somewhere in the mes-
sage."
TIP Specified filter patterns are not deleted by selecting [Not Used] in order to avoid re-entering conditions from
scratch in case the specified filter patterns may be needed again. If the patterns are needed again, change
the option to [Used].

n Trip Report tab

The "Trip Report" tab is used to specify the trip source. It is only valid when the server type is
SCS Events. To display messages in the trip mode in SOE Viewer, specify the trip source in
the "Trip Report" tab and execute a query.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-31
SOE Viewer Properties

General Date/Time Data Source Source Filter Trip Report

Server Connection

Not Used

Used Server: SCS0101

Type: SCS Events

User ID (UID): sa

Password (PWD):

Use Specific Database

Database

Automatic Trip Report

Periodic Search
CSV File Output
CSV File Output and Print

OK Cancel Apply

Figure I4.2.2-11 Trip Report tab of the SOE Viewer Properties dialog box

l Server Connection
Specify the destination of the trip source. To specify a trip source, select [Used Server]. Speci-
fy SCSddss (dd: domain number, ss: station number) for the server name. Select [SCS
Events] from the drop-down list of [Type].

n Saving settings
Click the [OK] button to save the changes to settings made in the SOE Viewer Properties dia-
log box and close the dialog box.
Click the [Cancel] button to close the dialog box without saving the changes.
To retain the configured property settings for use in future SOE View sessions, select [Save
Configuration] in the [File] menu.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-32

I4.2.3 Event mode operation

In this mode, SOE Viewer displays event messages of an SCS in a list format. This allows
analyzing events from relevant information using filtering. This section explains typical opera-
tions in the event mode of SOE Viewer.

n Activating the Event mode

When you start SOE Viewer, the event mode is automatically activated. When you start up
SOE Viewer for the first time, no data source is setup. Specify one or more data sources in
the SOE Viewer Properties dialog box.
Properties can be set by reading an SOE Viewer configuration file set and saved in advance.
If an SOE Viewer configuration file is read, the name of the file is displayed in the title bar of
SOE Viewer.
If it is desired to change the display to the event mode while SOE Viewer is in the trip mode,
click [Event Mode] button on the toolbar. Alternatively, select [Event Mode] in the [View] menu.
SOE Viewer switches to the event mode.

n Data source query

If a query is executed, event messages matching the date/time and the data source parame-
ters specified in the SOE Viewer Properties dialog box are acquired, up to the maximum num-
ber of records. The event messages are displayed in the message record list of SOE Viewer.
In order to execute a query, click [Execute Query] button on the toolbar. Alternatively, select
[Execute Query] in the [Action] menu.

n Message filtering
The filtering function is used to select only messages of interest among the displayed mes-
sages. Filtering by data source is performed based on the message type, message status and
filtering pattern settings in the "Source Filter" tab of the SOE Viewer Properties dialog box. It
is possible to set different filtering settings for each data source.
In order to apply filtering, click [Filter data] button on the toolbar. Alternatively, select [Filter
Results] in the [Action] menu. The results of the current query are filtered automatically; it is
not necessary to execute a query anew.
To view all messages without applying filtering, click [Clear Filter] button on the toolbar. Alter-
natively, select [No Filter/Remove Filter] in the [Action] menu.

n Printing
It is possible to print messages displayed in the message record list. Select [Print] button on
the toolbar or [Print] in the [File] menu. The standard Windows print dialog box appears.
The orders of columns and sorting used for the printout match with the display in SOE Viewer.
The following example shows a printout from SOE Viewer.
Query at 12/20/08 13:51:42 SOE Viewer Report Page1

Timestamp Quality Type ID Resource Reference Message

12/20/08 14:52:27.740 BSYS 4125-1 SCS0101 SCS0101 SCS0101 IOM Channel Error ...
* 12/20/08 14:52:27.740 SOER EVT_TRUE SCS0101 Tank-A Level LLL
* 12/20/08 14:52:27.740 SOER EVT_TRUE SCS0101 Tank-A Pressure LLL
12/20/08 14:52:43.244 BSYS 4180-4 SCS0101 SCS0101 SCS0101 Security Level=1 ...
12/20/08 14:52:44.644 BSYS 4173-4 SCS0101 SCS0101 SCS0101 Writing Security Pa ...
12/20/08 14:52:48.744 BSYS 4180-4 SCS0101 SCS0101 SCS0101 Security Level=0 ...
All Messages from [Begin] to [END]

Figure I4.2.3-1 Example of printout

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-33
TIP "*" (asterisk) in the Timestamp column indicates a trip trigger event.

A footer is combined from the following character strings according to the messages printed,
and then attached to the printed pages.
"All" or "Selected" or "Filtered" + "Messages from" + "StartDate" to "EndDate"
Either one of the "All," "Selected" or "Filtered" is printed out.
• All
Indicates that all event messages in the printing range are specified.
• Selected
Indicates that only event messages selected in the printing range are specified.
• Filtered
Indicates that event messages are filtered.
• StartDate
Indicates the start date/time of a query request.
[Begin] means that no specific start date is specified.
• EndDate
Indicates the end date/time of a query request.
[End] means that no specific end date is specified.

n Exporting
It is possible to export data displayed in the message record list to a CSV format file. It is also
possible to specify whether or not to apply filtering when exporting the data.
Select the [Export data] button on the toolbar or [Export List to file] in the [File] menu.
The Export SOE Viewer data dialog box appears. Specify the name and location of a file and
click [Save].
Export SOE Viewer data

Save in: Viewer

x s. soe_export.csv

File name: soe_export Save

Save as type: CSV Files (.csv,.txt) Cancel

Figure I4.2.3-2 Export SOE Viewer Data dialog box

The first line of a CSV file describes the output column format. The order of columns of an
exported file is always the same, even if the column order has been changed in SOE Viewer.
The header line is as follows.
Timestamp, Quality, Type, ID, Alarm State, Resource, Reference, Message

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-34
Timestamp,Quality,Type,ID,Alarm State,Resource,Reference,Message
*12/05/07 15:02:33.310,,SOER,EVT_TRUE,,SCS0101,Tank-A Level,LLL
*12/05/07 15:02:33.310,,SOER,EVT_TRUE,,SCS0101,Tank-A Pressure,LLL
12/05/07 15:02:33.317,,BSYS,4129-2,,SCS0101,SCS0101,SCS0101 GPS Interface Unit Error
12/05/07 15:02:33.310,,BSYS,0083-2,,SCS0101,SCS0101,SCS0101 IOM Configuration Error FIO NODE 01 SLOT 01
12/05/07 15:02:33.310,,BSYS,0083-2,,SCS0101,SCS0101,SCS0101 IOM Configuration Error FIO NODE 01 SLOT 03
12/05/07 15:02:33.310,,BSYS,0083-2,,SCS0101,SCS0101,SCS0101 IOM Configuration Error FIO NODE 01 SLOT 05
12/05/07 15:02:33.310,,BSYS,0081-1,,SCS0101,SCS0101,SCS0101 IOM Fail FIO NODE 01 SLOT 01 Code = 5103
12/05/07 15:02:33.310,,BSYS,0081-1,,SCS0101,SCS0101,SCS0101 IOM Fail FIO NODE 01 SLOT 03 Code = 5103
12/05/07 15:02:33.310,,BSYS,0081-1,,SCS0101,SCS0101,SCS0101 IOM Fail FIO NODE 01 SLOT 05 Code = 5103
12/05/07 15:02:26.841,,BSYS,0047-2,,SCS0101,SCS0101,SCS0101 LEFT Battery Alarm
12/05/07 15:02:16.801,,BSYS,0451-2,,SCS0101,SCS0101,SCS0101 LEFT Control
12/05/07 15:02:16.801,,BSYS,0011-2,,SCS0101,SCS0101,SCS0101 LEFT Fail (V STOP Code= 0814 0000 0000 0000)
12/05/07 15:02:16.801,,BSYS,0001-2,,SCS0101,SCS0101,SCS0101 LEFT Manual Reset Start
12/05/07 15:01:57.610,,BSYS,4173-4,,SCS0101,SCS0101,SCS0101 Writing Security Password to Flash Memory Succeeded
12/05/07 15:01:48.510,,BSYS,4173-4,,SCS0101,SCS0101,SCS0101 Writing Security Password to Flash Memory Succeeded

Figure I4.2.3-3 Example of CSV file

TIP "*" (asterisk) in the Timestamp column indicates a trip trigger event.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-35

I4.2.4 Trip mode operation

In this mode, SOE Viewer displays only trip trigger events specified as trip signals in a list for-
mat. It also displays detailed information generated near a specified trip trigger event for anal-
ysis. This section provides an overview of the trip mode of SOE Viewer and information dis-
played in the trip detail display.

n Activating the Trip mode

Click [Trip Mode] button on the toolbar or select [Trip Mode] in the [View] menu. SOE Viewer
switches to the trip mode.
The trip trigger event list is blank until a query is executed. Once a query is executed, trip sig-
nals in the specified date range are uploaded from the specified data source and the trip trig-
ger events are displayed in the trip trigger event list. This data is displayed again when the trip
mode is activated again.
ProSafe-RS SOE Viewer
File Action View
E T
Event Trip Query Filter No Filt Clear Prev Next Up Trip Trip Setup Print Export
Timestamp Quality Type ID Resource Reference Message
Trip trigger
12/05/07 19:19:26.083 SOER EVT_TRUE SCS0101 Z031101 TRUE
12/05/07 19:19:26.147 SOER EVT_TRUE SCS0102 Z032101 TRUE
event list
12/05/07 19:19:30.086 SOER EVT_TRUE SCS0101 Z031102 TRUE
12/05/07 19:19:30.149 SOER EVT_TRUE SCS0102 Z032102 TRUE
12/05/07 19:19:34.088 SOER EVT_TRUE SCS0101 Z031103 TRUE
12/05/07 19:19:58.100 SOER EVT_TRUE SCS0101 Z031104 TRUE

Events 1 to 18 of 18 Sorted by Timestamp Query at 12/05/07 19:46:06 Trip Trigger Mode

Figure I4.2.4-1 SOE Viewer (Trip mode)

n Trip detail display

The Trip Detail Display window displays detailed trip records related to the trip trigger event
selected in the trip mode of SOE Viewer. If you double-click a trip trigger event in the trip
mode or press the [Enter] key on the keyboard, a query is automatically executed for the
specified data source. The time range to be displayed in the Trip Detail Display window is de-
termined based on the selected trip trigger event and approximately 500 events and 1000
events before and after the selected trip trigger event, respectively, and all the events gener-
ated in the time range, including other SCS events, are displayed as detailed trip records.
The initial display of the trip detail record list is a page that includes the selected trip trigger
event.
The display mode frame of the status bar shows Trip Detail followed by the Reference infor-
mation related to the current trip trigger event.
In the Trip Detail Display window, the [Up to Trigger List], [Prev Trip Detail] and [Next Trip De-
tail] buttons are enabled on the toolbar.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-36
ProSafe-RS SOE Viewer
File Action View
E T
Event Trip Query Filter No Filt Clear Prev Next Up Trip Trip Setup Print Export
Timestamp Quality Type ID Resource Reference Message
12/05/07 19:19:27.955 SOER EVT_TRUE SCS0101 Z031108 TRUE
12/05/07 19:19:27.955 SOER EVT_TRUE SCS0102 Z032109 TRUE
12/05/07 19:19:27.955 SOER EVT_TRUE SCS0101 Z031110 TRUE Detailed trip
T 12/05/07 19:19:30.086 SOER EVT_TRUE SCS0102 Z032101 TRUE record list
12/05/07 19:19:30.088 SOER EVT_TRUE SCS0101 Z031102 TRUE related to trip
12/05/07 19:19:30.090 SOER EVT_TRUE SCS0101 Z031103 TRUE
trigger events
12/05/07 19:19:30.092 SOER EVT_TRUE SCS0101 Z031104 TRUE
12/05/07 19:19:30.094 SOER EVT_TRUE SCS0101 Z031105 TRUE
12/05/07 19:19:30.096 SOER EVT_TRUE SCS0101 Z031106 TRUE
Status bar
Events 28 to 37 of 480 Sorted by Timestamp Query at 12/05/07 20:47:47 Trip Detail [Z032101]

Reference

Figure I4.2.4-2 Trip Detail Display window

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-37

I4.2.5 Troubleshooting SOE Viewer

SOE Viewer displays warnings and error messages in the Warning/Error Log dialog box. Er-
rors occur in file input/output or database access operations. This section explains how warn-
ings and error messages are displayed and the actions to be taken.

n Notification via the Warning/Error Log dialog box

If a warning or error condition occurs during operation of SOE Viewer, an exclamation icon is
displayed in the display mode field of the status bar at the bottom of the SOE Viewer window.
If you double-click the icon, the Warning/Error Log dialog box appears. This dialog box also
appears by selecting [Warning/Error Log] in the [View] menu.
Click a message in the Log column of the Warning/Error Log dialog box to view detailed infor-
mation about the message in the [Detail] area. Up to 1000 warning/error messages can be
displayed. If more than 1000 messages have been recorded, messages are deleted starting
from the oldest message.

Figure I4.2.5-1 Exclamation icon

Warning/Error Log

Log:
Close
12/05/07 17:37:15:WRN:No matching records found for SCS Ev
Clear

Detail:
12/05/07 17:37:15:WRN:No matching records found for SCS
Event Source on SCS0101. Requested Range [BEGIN] to
[END].

Figure I4.2.5-2 Warning/Error Log dialog box

Click the [Clear] button to delete all messages displayed in the Warning/Error Log dialog box.
Click the [Close] button to close the dialog box.
The tables below show error messages and warning messages that may be generated.

Table I4.2.5-1 Error messages

Message Explanation Action
Check that the specified file name
Error loading configuration file [Fil- Uploading the specified SOE and path name are correct and
ename] Viewer configuration file failed. perform the upload operation
again.
Upload settings from a normal
Error on file [Filename] Uploading the specified SOE
SOE Viewer configuration file or
Cause: An attempt was made to Viewer configuration file failed.
use the SOE Viewer Properties di-
access The file was found but the data or
alog box to make the settings
Event past its end. format of the file is illegal.
manually.
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-38
Table I4.2.5-1 Error messages (Table continued)
Message Explanation Action
Check that the specified server
name and path name are correct.
Check that network communica-
Unable to connect to HIS server: SOE Viewer failed to make a
tion between the HIS server and
[ServerName] query for messages from the
SOE Viewer PC is functioning cor-
Error 0x20000116 on HIS Open- specified HIS server.
rectly. Check also that there is at
Log( ) An HIS log file cannot be opened.
least one "Daily Hishist log" file in
the HIS corresponding to the re-
quested date range.
The message cache service is not
running and/or in the process of
Could not obtain Cache Data. Cache data could not be acquired.
starting up. Wait for a while and try
again.
The problem may be solved by re-
installing the ProSafe-RS pack-
SOE viewer package of ProSafe- The ProSafe-RS package has not
age. If the error persists even if the
RS not installed. been installed.
package is re-installed, contact the
service department.
Check that the correct server
Could not obtain V net address. Network address of the control bus
name is entered in the [Used Serv-
Check [Used Server:]. could not be acquired.
er] field.
The problem may be solved by re-
installing the ProSafe-RS pack-
librhhmscache.dll is damaged. A program file is damaged. age. If the error persists even if the
package is re-installed, contact the
service department.

Table I4.2.5-2 Warning messages

Message Explanation Action
This occurs under normal circum-
No matching records found for No record was found in the date
stances as well. Expand the date
[SCS/HIS] Event Source on [Serv- range requested in the specified
range of messages on which quer-
erName] server.
ies are performed as necessary.
The number of records in the date Make the requested date range of
Results from [SCS/HIS] Event range requested for the specified messages smaller or make the
Source on [ServerName] excee- server exceeded the specified lim- maximum number of records
ded limit. it. Records outside the range are (MaxRecordsPerSource) as large
discarded. as possible.
Enter the correct SCS name. The
Input a correct SCS name into
The format of the entered SCS correct SCS name format is
[Used Server:]. (For example,
name is illegal. SCSddss (dd: domain number, ss:
SCS0101) (*1)
station number).
*1: Warnings are notified via pop-up dialog boxes even if the [Display warnings as popup messages] check box is disabled.

n Notification in the Error dialog box and the Warning dialog box
If an error or warning is generated, a pop-up dialog box appears to notify about the error mes-
sage or warning message at the time of occurrence.
Messages displayed in the Error and Warning dialog boxes can also be viewed in a list in the
Warning/Error Log dialog box.

l Error message display

Errors generated during operation of SOE Viewer are notified via the Error pop-up dialog box.
If an error occurs while executing a query, the user can cancel the query request or retry the
query for the next specified data source.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.2 SOE Viewer> I4-39
SOE Viewer

Error loading configuration file SoeViewerProp

Retry Cancel

Figure I4.2.5-3 Error dialog box

Click the [Retry] button to retry the query for the next specified data source and click the [Can-
cel] button to cancel the query request.

l Warning message display

Warnings generated while executing a query for a data source are also notified via the Warn-
ing pop-up dialog box. The Warning dialog box appears if you select the [Display warnings as
popup messages] check box in the "General" tab of the SOE Viewer Properties dialog box.
SOE Viewer

Results from SCS Event Source on SCS0101 exceeded limit.Requested Range [BEGIN] to [END].

Figure I4.2.5-4 Warning dialog box

Click the [OK] button to close the Warning dialog box.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.3 Master database offline download> I4-40

I4.3 Master database offline download

During master database offline download, the master database stored in the SENG is loaded
to an SCS. Since the downloaded SCS database is identical to the master database, it is pos-
sible to download the information downloaded previously to the SCS even while changing the
work database of an SCS project.
Use this download function to once again download the database that was previously down-
loaded; in the case, for example, when the CPU module of an SCS is replaced. This down-
load is not required when one of a pair of redundant CPU modules is replaced.

n Procedure for master database offline download

l What to do before master database offline download
Use the SCS security level operation function to set the SCS security level to Level 0.

l Start the master database offline download

1. Select [Controller] from the [Tools] menu of SCS Manager.
The [Controller] launcher menu appears.
2. From the Controller Launcher menu, select [Reset SCS] > [Master Database Offline
Download].
The master database offline download confirmation dialog box appears.
TIP • If the SCS security level is Level 1 or Level 2, a message prompting to set the security level to Level 0 is
notified and the download ends with an error. Set the security level to Level 0, and start the master data-
base offline download.
• If the I/O Lock window or Inter-SCS Communication Lock window is left open when you start master da-
tabase offline download, an error message appears and the download processing ends.

3. Click [OK].
4. Set a new password for changing the SCS security level.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.4 NIU maintenance port setting tool > I4-41

I4.4 NIU maintenance port setting tool

The NIU maintenance port setting tool is used in the following cases:
• To disable the NIU maintenance ports of all N-IO nodes on a per station basis in a batch
• To disable the NIU maintenance ports on a per node basis
• To enable the NIU maintenance ports on a per node basis
This section describes how to use the NIU maintenance port setting tool.

n Rights to execute the NIU maintenance port setting tool

The NIU maintenance port setting tool can be executed by the logged-in Windows user who
belongs to any of the following Windows groups: PSF_MAINTENANCE, PSF_MAINTE-
NANCE_LCL, PSF_ENGINEER and PSF_ENGINEER_LCL.

n To disable the NIU maintenance ports of all N-IO nodes on a per

station basis in a batch
1. On the Hardware Configuration Tree View of the SCS State Management window, select
the station for which the maintenance ports of NIU are to be disabled in a batch.
2. Select [Disable Maintenance port] in the [Operation] menu. Or, click the [Disable Mainte-
nance port] button on the toolbar.
The NIU Maintenance Port Setting Tool window appears.

Figure I4.4-1 NIU Maintenance Port Setting Tool window

The execution result is displayed in the message area once the processing is complete.
3. Click [Close].
The NIU Maintenance Port Setting Tool window is closed.

n To disable the NIU maintenance ports on a per node basis

1. On the Hardware Configuration Tree View of the SCS State Management window, select
the N-IO node for which the maintenance port of NIU is to be disabled.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.4 NIU maintenance port setting tool > I4-42
2. Select [Disable Maintenance port] in the [Operation] menu. Or, click the [Disable Mainte-
nance port] button on the toolbar.
The NIU Maintenance Port Setting Tool window appears.
The execution result is displayed in the message area once the processing is complete.
3. Click [Close].
The NIU Maintenance Port Setting Tool window is closed.

n To enable the NIU maintenance ports on a per node basis

1. Check that the SCS security level is Level 1 or 0 by using the SCS security level opera-
tion function.
2. On the Hardware Configuration Tree View of the SCS State Management window, select
the N-IO node for which the maintenance port of NIU is to be enabled.
3. Select [Enable Maintenance port] in the [Operation] menu. Or, click the [Enable Mainte-
nance port] button on the toolbar.
The NIU Maintenance Port Setting Tool window appears.
The execution result is displayed in the message area once the processing is complete.
4. Click [Close].
The NIU Maintenance Port Setting Tool window is closed.

IMPORTANT
Set the security level of the SCS to 1 or 0 to enable the maintenance port of NIU. You cannot
enable the maintenance port of NIU when the security level is 2.

n Display of execution results

The following execution results are displayed in the message area when the NIU mainte-
nance port setting tool is executed.

Table I4.4-1 Display of execution results

Display Description
Succeeded Successfully completed the configuration process of the maintenance port.
Skipped Skipped the configuration process of the maintenance port.
Failed Failed in the configuration process of the maintenance port.

When a node is specified (example):

Disabling NIU Maintenance Port start 2015/12/11 18:02:00
Station:SCS0101 Node:1 … Succeeded.
Disabling NIU Maintenance Port end 2015/12/11 18:02:01

When all nodes are set at a time (example):

Disabling NIU Maintenance Port start 2015/12/11 18:03:00
Station:SCS0101 Node:1 … Succeeded.
Station:SCS0101 Node:2 … Skipped.
Station:SCS0101 Node:3 … Skipped.
Disabling NIU Maintenance Port end 2015/12/11 18:02:03

When disabling the port for all nodes, the result is displayed only for the nodes that are de-
fined.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.4 NIU maintenance port setting tool > I4-43
The following cases result in Skipped or Failed, and an error message is displayed.
• Specified port is already enabled/disabled
• NIU is in maintenance mode
• Node failure
• N-ESB bus failure

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.5 IOM Download tool> I4-44

I4.5 IOM Download tool

The IOM Download tool enables you to configure input/output modules by downloading input/
output configuration information from the master database of an SCS project to the modules.
Use the IOM Download tool in the following cases.
• After replacing failed input/output modules with normal modules.
• When resetting AIO/DIO modules for recovery from errors in the field. This is only appli-
cable with SCS system program release number R3.02 or later.
The correct operation procedure, when to use the IOM Download tool, and precautions are
included in the topic of the input/output module maintenance. Use the IOM Download tool ac-
cording to the instructions of reference documents in this section.
TIP With SCS system program release number R2.03 or later, you can choose to enable automatic download of
configuration information whenever stand by AIO/DIO module in a dual redundant configuration is replaced.
This setting is available in the SCS Constants Builder. If the automatic download is executed, you do not have
to use the IOM Download tool.

SEE
ALSO For more information about input module recovery procedure, refer to:
G2.2.1, “Actions taken at input module error occurrence and recovery procedure” on page G2-12
For more information about output module recovery procedure, refer to:
G2.2.3, “Actions taken at output module error occurrence and recovery procedure” on page G2-15
For more information about I/O module maintenance procedure, refer to:
“n Maintenance of I/O modules” on page I1-12
For more information about how to replace the I/O module of the FIO node, refer to:
E4.7, “Replacing FIO I/O modules” in Hardware User's Guide (IM 32P06C10-01EN)
For more information about how to replace the I/O module of the N-IO node, refer to:
E5.3, “Replacing N-IO I/O modules” in Hardware User's Guide (IM 32P06C10-01EN)

n Configuring Input/Output modules by using the IOM Download tool

The IOM Download tool must be used for modules where the hardware is working properly.
Follow these steps to configure an input/output module:
TIP The input/output configuration information stored in the master database of the SCS project is downloaded by
IOM download. So the information previously downloaded to the input/output module is downloaded again
even if the SCS project is being changed.

1. In the SCS State Management window, select an input/output module whose status is
Fail .
2. On the tool bar, click [IOM Load].
The IOM Load dialog box appears.
3. Click [OK].
The input/output configuration information is downloaded to the selected input/output
module. The downloaded information is stored in the non-volatile memory of the input/
output module. After that, the SCS starts the input/output modules.
4. Check the results of the IOM Download tool execution in the diagnostic information mes-
sages.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.5 IOM Download tool> I4-45

IMPORTANT
• The channels of the output module are in the Output Disable status after the module
starts. To output signals from the module, put the channels to be in the Output Enable
status by performing the Output enable operation. After all channels go into the Output
Enable status, SCS operating mode is changed from Waiting Mode to Running Mode.
• When the IOM Download tool is executed, the communication program is downloaded to
the communication module, and the module restarts. The Output Enable Operation is un-
necessary for the communication module because the communication begins automati-
cally.

SEE
ALSO For more information about how to view diagnostic information messages, refer to:
H5.1, “Diagnostic Information window” on page H5-2
For more information about Output enable operation, refer to:
C8., “Output enable operation” on page C8-1

n Automatic execution of IOM download

After replacing I/O module, you need to perform IOM download in order to set configuration
information. However, you can specify automatic execution of IOM download in following
conditions.
When automatic execution of IOM download is specified, and if a standby side of a duplexed
AIO/DIO module is replaced in the SCS that is running for a purpose such as maintenance,
the configuration information is automatically downloaded from the module on the control
side to the replaced module. This operation is possible only when specification is done with
the SCS Constants Builder. If it is not specified, manual IOM download is required after re-
placing the module on the standby side. You need to perform manual IOM download when
replacing both sides of redundant AIO/DIO modules or AIO/DIO modules of single configura-
tion.
Automatic IOM download is not performed for communication modules.
SEE
ALSO For more information about setting procedures using SCS Constants Builder, refer to:
C1.2.6, “SCS Constants Builder” on page C1-20

l IOM download automatic execution conditions

If a redundant module on the standby side is replaced, IOM download is automatically exe-
cuted if the following conditions are met.
• Automatic IOM download is enabled in the SCS Constants Builder.
• The redundant AIO/DIO module on the control side is operating normally.
• The replaced redundant module on the standby side failed due to configuration error (*1)
*1: Except the case where the model names on the control and standby sides are different or the case of hardware failure (the
STATUS LED of the module is OFF).

l Operations during automatic IOM download

The SCS operates as follows while automatic IOM download is being executed.
• If multiple AIO/DIO modules on the standby side are replaced, the processing of automat-
ic IOM download is executed sequentially on a one-by-one basis.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.5 IOM Download tool> I4-46
• Diagnostic information messages (No. 0475 and 0476) are notified at the start and com-
pletion of automatic IOM download.
• If an error occurs during automatic execution of IOM download, the diagnostic information
message indicating erroneous termination of automatic IOM download (No. 477) is noti-
fied and the IOM download processing is aborted.

IMPORTANT
Do not remove and put back the applicable AIO/DIO module while automatic IOM download is
being executed. If it is removed and put back, a major failure may occur in the module (the
STATUS LED of the module becomes OFF).
Automatic download is completed in approximately 30 seconds after inserting the module on
the standby side, and the diagnostic information message indicating completion of IOM down-
load (No. 0476) is output. If you need to remove and put back a module, check the diagnostic
information message indicating completion of IOM download in the Diagnostic Information
window of the SCS Maintenance Support Tool before doing so.
If a major failure occurs due to erroneous removal and reinsertion, perform IOM download
manually to the applicable AIO/DIO module, and then remove and reinsert the module after
the completion.

• Automatic IOM download is not executed on AIO/DIO modules to which online change
download of input/output parameters or manual IOM download are being executed. How-
ever, automatic IOM download to a different module is executed in parallel.
• If it is attempted to execute online change download of input/output parameters or man-
ual IOM download on the applicable AIO/DIO modules for which automatic IOM download
is being executed, an error occurs in the manual download.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.6 IOM Control Right Switching Tool > I4-47

I4.6 IOM Control Right Switching Tool

The IOM Control Right Switching Tool is used for switching between the control side and the
standby side of the pair of AIO/DIO modules placed in redundant configuration. However, this
tool can not be used for the redundantly configured communication modules.
This section explains the operation procedures.

n Overview of the IOM Control Right Switching Tool

The IOM Control Right Switching Tool is used for switching between the control side and the
standby side of the pair of AIO/DIO modules for which redundant configuration is specified. It
is possible to perform a switching operation for one AIO/DIO module pair or one node in one
operation.
This tool can be used when the SCS security level is 1 or 0.
TIP The IOM Control Right Switching Tool is not used to display the status of AIO/DIO modules or to perform op-
erations related to the status of AIO/DIO modules.

l Precautions at starting the IOM Control Right Switching Tool

The IOM Control Right Switching Tool can be used even if the SCS project is opened in SCS
Manager.
Note, however, that if a download operation and an AIO/DIO module control right switching
operation are performed at the same time, an error occurs in one of the operations. Moreover,
the control right of AIO/DIO modules cannot be switched during checking in/out in Version
Control or executing the Master Database Restoring Function.

n How to start the IOM Control Right Switching Tool

Double-click the following command in Windows Explorer to start the tool.
(ProSafe-RS installation top folder) Specify \ProSafe-RS\YOKOGAWA\scs\tool\RHEToolIOS-
witch.exe or, from the [Start] menu of Windows, select [Run...] and specify "RHEToolIOS-
witch.exe." The main window of the IOM control right switching tool appears.
SCS project path display area
Switch continue mode specification area
AIO/DIO module display area (tree view)
IOM Control Right Switching Tool

SCS Project Folder:

C:\RS·Projects\RS1\SCS0102 Browse...

When switching one module fails , other modules can be switched,

Acknowledgement No Acknowledgement

SCS0101
FIO
Node(1)
SAI143(1)
SAV144(3)
N-IO
Node(1)
S2MMM843(1-1)
S2MMM843(2-1)

Switch Close

Figure I4.6-1 Main window of the IOM Control Right Switching Tool

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I4.6 IOM Control Right Switching Tool > I4-48

n Procedure to switch the control right of AIO/DIO modules

1. Specify the top folder of the SCS project in the SCS project path display area. The speci-
fied SCS project should be the one downloaded to the SCS. You can also select a folder
from the folder selection dialog box that is displayed by clicking [Browse].
2. In the switch continue mode specification area, select [Acknowledgement] or [No Ac-
knowledgement].
You can select whether to display a confirmation dialog that appears during switching
multiple AIO/DIO modules if switching fails for a certain AIO/DIO module, and the next
AIO/DIO module is to be switched in continuation.
3. The redundant AIO/DIO modules in the SCS project, which is specified in the SCS project
path display area, are displayed in a tree format in the AIO/DIO module display area.
You can select either the AIO/DIO module or node for which the control rights are to be
switched. Only one AIO/DIO module or one node can be selected at a time. You cannot
select a station name, FIO or N-IO.
4. Click the [Switch] button. A confirmation dialog box appears.

IOM Control Right Switching Tool

Switch the next module?

Node(1) SAI 143(1)
Node(1) SAV144(3)
Node(1) SAV144(5)

OK Cancel

Figure I4.6-2 Confirmation dialog box

5. Click [OK]. The control right switching process of the AIO/DIO module starts, and the
Message Display dialog box appears.
Message Display

Start Switching. Node=1 Slot=3 IOM SDV53A 2009/10/07 14:57:13

Succeeded
Finish switching. Node=1 Slot=3 IOM SDV53A 2009/10/07 14:57:13

Figure I4.6-3 Message Display dialog box

The Message Display dialog box shows the AIO/DIO module targeted for switching and
the processing results, etc.
TIP Select [Select All] from the pop-up menu displayed by right-clicking the mouse in order to select data dis-
played in the Message Display dialog box. Select [Copy] to copy the data.

6. When the switching operation is completed, click the [Close] button in the Message Dis-
play dialog box.
7. Click [Close] in the main window to exit the IOM Control Right Switching Tool.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I5. Procedures and precautions for adding a station or domain> I5-1

I5. Procedures and precautions for

adding a station or domain
This section describes the procedures and precautions that must be followed when you add a
station or a domain to a Vnet/IP network in a star topology.
TIP For information about the procedures and precautions when you add a station or a domain to a Vnet/IP net-
work in a ring topology, contact YOKOGAWA.

SEE
ALSO For more information about the procedures and precautions for adding stations or adding domains in a FAST/
TOOLS integration configuration, refer to:
C5.2, “Procedures and precautions for adding a station or domain” in Integration with FAST/TOOLS (IM
32P56H20-01EN)

n Procedures and precautions for adding a Vnet/IP station

When adding a station to Vnet/IP network, follow the following procedure:

IMPORTANT
• 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. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
2. Make sure that the additional station is not powered.
3. Connect the Vnet/IP connector for BUS1 of the additional station to the Layer 2 switch
for BUS1 with a cable. If the port on the Layer 2 switch is disabled, enable the port.
4. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
5. Connect the Vnet/IP connector for BUS2 of the additional station to the Layer 2 switch
for BUS2 with a cable. If the port on the Layer 2 switch is disabled, enable the port.
6. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
7. Turn on the power of the additional station.
8. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Over-
view or SCS State Management) of SCS Maintenance Support Tool on an SENG to check the bus status. When you call up
the SCS status display window, select the project of a running SCS and then call up the window.

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
existing Layer 2 switches)
First, 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.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I5. Procedures and precautions for adding a station or domain> I5-2
1. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
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.
6. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
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.
11. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
12. Add a station according to the procedure for "Case 1".
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Over-
view or SCS State Management) of SCS Maintenance Support Tool on an SENG to check the bus status. When you call up
the SCS status display window, select the project of a running SCS and then call up the window.

n Procedures and precautions for adding a Vnet/IP domain

Follow these steps when you want to add a domain to a Vnet/IP network.

IMPORTANT
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

existing Layer 3 switches)
First, carry out steps 1 to 5 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.”
1. In the Network Status Display dialog box on HIS, check that both buses are normal.(*1)
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.
3. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
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.
5. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
6. Add stations for the new domain by following the procedures in "Procedures and Pre-
cautions for Adding a Vnet/IP Station."

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<I5. Procedures and precautions for adding a station or domain> I5-3
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Over-
view or SCS State Management) of SCS Maintenance Support Tool on an SENG to check the bus status. When you call up
the SCS status display window, select the project of a running SCS and then call up the window.

l Case 2: When you need to add Layer 3 switches (no ports are available on
existing Layer 3 switches)
First, 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.”
1. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
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.
4. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
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 to an existing Layer 2 or Layer 3 switch
for BUS2 with a cable.
7. In the Network Status Display dialog box on HIS, check that both buses are normal. (*1)
8. Add stations for the new domain by following the procedures in "Procedures and Pre-
cautions for Adding a Vnet/IP Station."
*1: In the case of a system consisting of only ProSafe-RS stations, use an SCS status display window (either SCS Status Over-
view or SCS State Management) of SCS Maintenance Support Tool on an SENG to check the bus status. When you call up
the SCS status display window, select the project of a running SCS and then call up the window.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1. Settings for node, module, and channel> App.1-1

Appendix 1. Settings for node, module,

and channel
This section explains the settings for node, module, and channel. These settings can be done
in the Safety I/O Editor or in IOM Definition Editor; however, this section explains how to do it
in each tab of I/O Parameter Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.1 Setting items for nodes > App.1-2

Appendix 1.1 Setting items for nodes

The following are the node settings of the Node tab in I/O Parameter Builder for input/output.
• Node number:
• Component Number
• Node Interface Unit
• Extends node bus
• Extends to
• N-IO Node Connection
• Enable External Alarm Input
• Normal Value
• Comment
Each node setting item is explained in detail as follows.

n Node Number
This is the node number for which the module is mounted.

n Component Number
This is a comment related to node layout information. Any character string of up to 8 single-
byte characters or 4 double-byte characters can be entered.
This setting item is not downloaded to an SCS.
This item can be changed online.

n Node Interface Unit: SCSP3, N-IO node

This is the model name of the bus module for node interface unit.

n Extends Node Bus: SCSP2, SCSP3

You can specify whether or not to extend nodes by the optical ESB bus repeater. For the re-
mote node installed via the optical ESB bus repeater, you must select [Yes] and specify the
distance in [Extends To]. If you do not make this setting, the data from the nodes and SOE
data will not be updated correctly. If [Yes] is set for this item on CPU nodes, a build error will
occur.
• Yes: Node extension by an optical ESB bus repeater is applied
• No: Node extension by an optical ESB bus repeater is not applied (default)
This setting item can be changed online.

n Extends To: SCSP2, SCSP3

You can specify the distance from a CPU node to a safety node unit and to an N-IO node. It is
only valid if [Yes] is selected in the specification of node extension distance [Extends Node
Bus].
• Range: 5 to 50 km (default: 5 km)
• Setting unit: 5 km
This item can be changed online.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.1 Setting items for nodes > App.1-3

n Extends Node Bus : SCSP1

You can specify whether or not to extend nodes by the optical ESB bus repeater. To extend a
node, select [Yes] and specify the distance in [Extends To]. A build error will occur if you se-
lect [Yes] for this item when [Optical ESB Bus Repeater] on the SCS Constants Builder is set
to [No]. A build error will also occur if [Yes] is set for this item on CPU nodes.
• Yes: Node extension by an optical ESB bus repeater is applied
• No: Node extension by an optical ESB bus repeater is not applied (default)
This setting item can be changed online.
TIP In the case of nodes equipped with ALR111, ALR121, or ALE111 for Modbus slaves, if 10 km or longer is
specified in [Maximum Extension Distance] on the SCS Constants Builder, select [Yes] and specify the node
extension distance in [Extends To].

n Extends To: SCSP1

You can specify the distance from a CPU node to a safety node unit. It is only valid if [Yes] is
selected in the specification of node extension distance [Extends Node Bus].
A build error will occur if the node extension distance is longer than [Maximum Extension Dis-
tance] defined on the SCS Constants Builder.
If default (0) is specified, it is regarded as if the node is at the position specified by [Maximum
Extension Distance] defined on the SCS Constants Builder.
• Range: 0 to 50 km (default: 0)
• Setting unit: 5 km
This item can be changed online.

IMPORTANT
Be sure to specify the extension distance according to the actual node extension distance. If
no specification is made for SCSP1, load fluctuation of CPU becomes large if input/output
modules and/or bus fail.

n N-IO Node Connection: SCSP3, FIO node

You can specify whether to connect the N-IO node to the path from the CPU node to FIO
node.
• Yes: Connects the N-IO node to the path from the CPU node to FIO node.
• No: Does not connect the N-IO node to the path from the CPU node to FIO node (de-
fault).
This setting can be changed online.

n Enable External Alarm Input: SCSP3, N-IO node

You can specify whether or not to use alarm input from an external device.
• Yes: Alarm input from an external device is used.
• No: Alarm input from an external device is not used (default).
This setting can be changed online.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.1 Setting items for nodes > App.1-4

n Normal Value: SCSP3, N-IO node

You can specify the normal value to 0 or 1 for the alarm input if [Yes] is specified for [Enable
External Alarm Input].
• 0: 0 is the normal value.
• 1: 1 is the normal value (default).
This setting can be changed online.

n Comment
This is a comment related to the node. Any character string of up to 24 single-byte characters
or 12 double-byte characters can be entered.
This setting item is downloaded to an SCS.
This setting item can be changed via online change download.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.2 Settings for modules > App.1-5

Appendix 1.2 Settings for modules

The following are the settings in the module tab of I/O Parameter Builder.

n Node Number
This item displays the node number in which the I/O module is mounted.

n Unit Number: N-IO I/O module

This item displays the unit number in which the I/O module is mounted.

n Slot Number
This item displays the slot number in which the I/O module is mounted.

n Device
The model name of the I/O module is displayed.

n Base Plate: N-IO I/O module

You can select the base plate model for which the I/O module is mounted.

Table Appendix 1.2-1 Available base plate models

I/O module model Base plate model Description
S2MMM843, S2BN1D Standard base plate (default)
S2MDV843
S2BN_D Base plate for barrier

TIP If the base plate model is changed, all the channel items set for the module are initialized.

n Dual-Redundant
This item displays whether the input/output module is placed in single configuration or redun-
dant configuration. Input/output modules are placed in redundant configuration using an odd-
numbered slot and the adjacent even-numbered slot (the odd number + 1).

n Device Index
This is the device index assigned to the I/O module.

n Comment
This is a comment related to the input/output module. Any character string of up to 24 single-
byte characters or 12 double-byte characters can be entered.
This setting item is not downloaded to an SCS, so changing the definition does not affect in-
put/output processing.
This item can be changed online.

n Device Reset Function (per module): SAI143

This item specifies whether or not to use the device reset function.
• Enable: Uses the device reset function.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.2 Settings for modules > App.1-6
• Disable: Does not use the device reset function. (Default)
This setting is displayed when using an SCS project newly created with a version of SENG
that is R4.03.00 or later.
SEE
ALSO For more information about engineering for resetting the Smoke and Heat Detector, refer to:
A3.4.4, “Engineering regarding the device reset function and alarm suppression during device reset” in
Engineering Guide Vol. 2 (IM 32P01C20-01EN)

n Command Line: analog output module

TIP Specify the command line using up to 256 single-byte characters. If the command line is not set, the default
value will be used for each applicable item. The format is as follows.
Item name = Data value, Item name = Data value, ...

l SOOP (Output open detection level setting)

This item specifies an output open (OOP) detection level. An open circuit error is recognized
when the readback value of an output falls below the set value. The default is 0.00085 A.
Format
• SOOP=0.001
Parameter
• Output open detection level
You need to specify an output open detection level in amperes (A).
SOOP < Output value at fault (fail-safe value)
If tight-shut output is specified : SOOP < Tight-shut output value
If tight-shut output is not specified : SOOP < Power-on output value (0.00125 A)
• This item can be changed via online change download. Note, however, that IOM down-
load is also performed at the same time.

n Software Filter: digital input module, N-IO I/O module (DI channel
only)
The software filter is applied for reducing the influence of noises. An integer between 0 and
10 can be selected as the filter setting value. The default setting is 1.
With this filter, the discrete input chattering signals can be sifted out so as to prevent from er-
ror actions.
The filter setting value multiplied by 10 ms (sampling period) is the filter time. The chattering
signals occurred within this filter time will be eliminated.
As an example, if the filter setting value is 2, the chattering signals shorter than 20 ms (2x10
ms) will be eliminated.
• If the filter setting value is 0, the noise signals will not be filtered thus PV varies with the
noise signals. In general, the filter setting value should not be set to 0.
This item can be changed via online change download. Note, however, that IOM download is
also performed at the same time.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.2 Settings for modules > App.1-7

n Automatically Delete Noisy Events (Automatically delete SOE

event): digital input module, N-IO I/O module (DI channel only)
You can specify whether or not to delete events automatically if many events that are targets
of SOER occur.
If a channel repeatedly generates too many events, the events from other channels may be
lost. This function can be used to restrict events per channel and the above problem can be
avoided. If the number of events that have occurred during the time specified in [SOE Dele-
tion Schedule] exceeds the number of events specified in [Number of SOE Events], all subse-
quent events are discarded. For example, if [SOE Deletion Schedule] is set to 1.0 second and
[Number of SOE Events] is set to 3, and if three or more events have occurred within 1 sec-
ond, then the fourth and subsequent events occurring within 1 second are automatically dis-
carded. However, if the last event is different from the current status of the DI, a pseudo event
is generated to indicate the DI status.
• Yes (Delete):
Automatically delete events if many events occur.
• No (Do not delete):
Do not delete events even if many events occur (default).
This item can be changed via online change download. Note, however, that IOM download is
also performed at the same time.

n SOE Deletion Schedule (SOE event period): digital input module, N-

IO I/O module (DI channel only)
You can specify the time period setting for [Automatically Delete Noisy Events] in units of sec-
onds. This setting is enabled if [Yes (Delete)] is selected for [Automatically Delete Noisy
Events].
Select either 0.5, 1.0, 1.5, 2.0, 2.5, 3.0 or 3.5 seconds. The default value is 1.0 second.
This item can be changed via online change download. Note, however, that IOM download is
also performed at the same time.

n Number of SOE Events: digital input module, N-IO I/O module (DI
channel only)
You can specify the number of events for [Automatically Delete Noisy Events]. This setting is
enabled if [Yes (Delete)] is selected for [Automatically Delete Noisy Events].
Select either 3 or 5. The default value is 3 events.
This item can be changed via online change download. Note, however, that IOM download is
also performed at the same time.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-8

Appendix 1.3 Settings for channel items

The following are the settings in the channel tab of I/O Parameter Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-9

Appendix 1.3.1 Common display items for channels

The following items are displayed commonly for all AIO/DIO modules with channel parame-
ters in I/O Parameter Builder.

n Channel Number
This is the channel number displayed in I/O Wiring View of SCS Manager. It is sequential
number starting from 1.

n Wiring Position
This is the channel name that is displayed in I/O Wiring View of SCS Manager. It is deter-
mined by device index and channel identification number. The channel identification number
used for wiring position is sequential number starting from 0. The wiring position of the input
modules is prefixed with %IU while the wiring position of the output modules is prefixed with
%QU.
Example:
In the case of a 16-channel input module: %IU1.0, %IU1.1, ... %IU1.14, %IU1.15
In the case of a 8-channel output module: %QU3.0, %QU3.1, ... %QU3.6, %QU3.7

n I/O Variable Name

This is the name of I/O variables assigned to the channel.

n Direction: AIO/DIO module of FIO

This item indicates whether a signal is an input or output signal.

n Comment
This is a comment for an I/O variable specified in Dictionary View (*1)of SCS Manager.
*1: The comment for the I/O variable specified in Dictionary View of SCS Manager is displayed as the comment for the wired
channel. Up to 64 characters can be specified for the variable comment, but only 32 characters are retained in SCS data-
base; therefore, make sure not to specify more than 32 characters. Channel comments for unused channels (unconnected
channels) are not displayed.
Comments for DI/DO variables are the variables used as identifiers of SOE.

TIP If comments for DI/DO variables are changed in Dictionary View of SCS Manager, discrepancies occur due to
the input/output definition changes, and it becomes necessary to perform online change download to the
SCS. Since this changes only the definitions in the databases of the SCS (no changes are made to the pa-
rameters of the DI/DO modules themselves), the inputs and outputs are not influenced by the online change
download.

n Signal Type: AIO/DIO module of N-IO

This item specifies type and direction of the I/O signal. Selection of the signal type can be dif-
ferent depending on the classified signal category that is specified.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-10
Table Appendix 1.3.1-1 Signal type
Signal
Signal type Description
category
AI Current Input Select this item if HART communication function is not used
(default).
Current Input (HART Commu- Select this item if HART communication function is used.
nication)
AO Current Output Select this item if HART communication function is not used
(default).
Current Output (HART Com- Select this item if HART communication function is used.
munication)
DI Status Input Only one DI signal type (default)
DO Status Output Use one channel (default).
1.3A Status Output Use two consecutive channels. When the settings for one chan-
nel (for example channel no. 3) are configured, the same con-
tents are set automatically for the succeeding channel (for ex-
ample channel no. 4). This item cannot be selected for the mod-
ule mounted in the base plate for barrier.
2.0A Status Output Use three consecutive channels. When the settings for one
channel (for example channel no. 3) are configured, the same
contents are set automatically for the two succeeding channels
(for example channels no. 4, 5). This item cannot be selected
for the module mounted in the base plate for barrier.

n P&ID Tag Name

This is a comment that the user can specify in order to make it easy to identify information
drawn on a P&ID drawing with the channel.
The comment should be written within 16 single-byte characters or 8 double-byte characters.
This setting item can be omitted.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-11

Appendix 1.3.2 Settings for the AI channel

The following are the settings for the AI channel in I/O Parameter Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-12
Table Appendix 1.3.2-1 Settings for the AI channel (Table continued)
Online change
Setting items IOM download (*2) Remarks
download (*1)
Detect Transmitter Fault (Low)
Yes No -
(Specify Detect Transmitter Fault (Low))
Threshold of Transmitter Fault (High) %
(Specify Threshold of Transmitter Fault Yes No -
(High) %)
Threshold of Transmitter Fault (Low) %
(Specify Threshold of Transmitter Fault Yes No -
(Low) %)
Field Power Diagnosis
Yes Yes -
(Specify Field Power Diagnosis)
Reference Junction Compensation
(Specify Reference Junction Compensa- Yes Yes -
tion)
Burnout
Yes Yes -
(Specify Burnout)
P&ID Tag Name
Yes No -
(Specify P&ID Tag Name)
Command Line
Yes No -
(Specify Command Line)
*1: Indicates whether the setting can be changed by online change downloading.
Yes: The setting can be changed by online change downloading.
No: Online change downloading is not required.
- : Not a target
*2: Indicates whether the IOM downloading is performed with the online change downloading.
Yes: The IOM downloading is performed together with the online change downloading.
No: The IOM downloading is not performed together with the online change downloading.
- : Not a target

Each of setting items that are not explained as common items is explained as follows.

n Time to Chattering Recovery Notice (s) (Time to Chattering

Recovery Notice)
This item is used to suppress the chattering alarm.
Set the time by which to delay display of the system alarm for recovery of a channel error of
an input module. When an error is recovered during the alarm suppression period, SCS moni-
tors whether the normal status persists for the amount of time set for this item. Alarm suppres-
sion is continued if an error occurs during the set time, while an error recovery system alarm
is displayed if an error does not occur.
The chattering alarm suppression function is disabled when this time is set to 0.
Setting range: 0 to 120 seconds
Default: 0

IMPORTANT
This item can be used with SCS projects created using version R4.03.00 or later with SENG
on which a CENTUM integration configuration license has been reflected.

n Connection Method: AIO/DIO module of N-IO

• For the AIO/DIO module that is mounted in the standard base plate
You can set the connection method between field device and AIO/DIO module. The de-
fault is 2-Wire.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-13
• For the AIO/DIO module that is mounted in the standard base plate for barrier
You can set the connection method between barrier and AIO/DIO module. The default is
4-Wire.

n Device OFF-ON Variable Name: SAI143, SAV144, S2MMM843

You can specify a BOOL-type variable to switch OFF/ON of the power supply of the Smoke
and Heat Detector. The fault detection status is reset by switching the device off and on. With
S2MMM843, you can only set the variable when the connection method is 2-Wire.
When using SAI143 or SAV144, this item is displayed when using an SCS project newly cre-
ated with a version of SENG that is R4.03.00 or later.
SEE
ALSO For more information about engineering for resetting the Smoke and Heat Detector, refer to:
A3.4.4, “Engineering regarding the device reset function and alarm suppression during device reset” in
Engineering Guide Vol. 2 (IM 32P01C20-01EN)

n Reset Group ID: SAI143, SAV144, S2MMM843

An ID used, when multiple Smoke and Heat Detectors are to be reset, to interpret the chan-
nels of the Smoke and Heat Detectors being reset at the same time as being in the reset sta-
tus. SCS manages whether the channels are in the reset status in units of each reset group
ID. With S2MMM843, you can only set this ID when the connection method is 2-Wire.
Set the same reset group ID for channels to be interpreted as being in the reset status at the
same time. Even in cases when there are no Smoke and Heat Detectors to be reset at the
same time, set a reset group ID that is not in use with other channels. However, set this value
to 0 if you will not be using the alarm suppression function during device reset nor the function
block HSDTR.
This setting is displayed when using an SCS project newly created with a version of SENG
that is R4.03.00 or later.
• Setting range: 0 to 1000 (default: 0)
SEE
ALSO For more information about engineering for resetting the Smoke and Heat Detector, refer to:
A3.4.4, “Engineering regarding the device reset function and alarm suppression during device reset” in
Engineering Guide Vol. 2 (IM 32P01C20-01EN)

n Input Processing at Fault

This item specifies an input processing to be used when an input fault is detected or when
[Input Processing at Fault] is selected in [Input Processing at Transmitter Fault].
You can specify [Hold] or [Fixed Value].
The input faults that can be detected include the following: Errors on both sides of the path
from the CPU to an analog input module, errors in analog input modules, channel errors, IOP
and field wiring errors (transmitter errors are not included).
• Hold:
The value before the fault was detected is retained.
• Fixed Value (specified input value):
The input value specified in [Input Value at Fault] is set (default).

n Input value at fault (%)

This is the value set as an input value instead of process value if [Fixed Value] is selected in
[Input Processing at Fault] (the value is used as an input value at error occurrence).

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-14

l For SAI143, SAV144, and S2MMM843

You can specify the input value at error occurrence (%) in the range from -25.0 to 125.0. The
default value is 0.0 %.
Even if the [Signal Conversion] is set to [SQRT], this setting value is used as the input value
at error occurs. (The value set here will not be square-rooted when used as the input value.)

l For SAT145 and SAR145

You can specify the input value at error occurrence (%) in the range from -1000.0 to 1000.0.
The default is 100.0%.

n Input Processing at Transmitter Fault: SAI143, SAV144, S2MMM843

This is the value set as the input value if a transmitter error is detected (a value used as an
input value at error). This item is only enabled for current inputs.
• Input Processing at Fault:
Follow the setting of [Input Processing at Fault] if a transmitter error occurs (default).
• Raw Data:
The raw data from the input module is set as the input value.

n Signal Conversion
You can specify the conversion method of the input signal.

l For SAI143, SAV144, and S2MMM843

• LINEAR (No Conversion):
The physical range specified by the "Low Limit" and "High Limit" (mA or V) is converted to
0 to 100 (%) data (default).
• SQRT:
After LINEAR conversion, input range checks are performed (against the IOP high
limit/low limit and transmitter fault high limit/low limit). Then, the square root is calculated
and the result is converted to a data value of 0 to 100 (%).
The square-root conversion is illustrated as follows:
Input signal
(converted value)
100%

SL : [Lower Limit] (4 mA for current input)

SH: [High Limit] (20 mA for current input)

0%
SL SH Input signal
(raw data)

Figure Appendix 1.3.2-1 SQRT

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-15

l For SAT145 and SAR145

Table Appendix 1.3.2-2 Input signal conversion for the thermocouple/mV input module (SAT145)
Selection Explanation of signal conversion
Type K Temperature conversion Type K (default)
Type E Temperature conversion Type E
Type T Temperature conversion Type T
Type J Temperature conversion Type J
Type R Temperature conversion Type R
Type S Temperature conversion Type S
Type B Temperature conversion Type B
Type N Temperature conversion Type N
mV Input -20 to 80 mV No temperature conversion. However, the physical range (mV) set in "High Limit"
(%) and "Low Limit" is converted to 0 to 100% data.
mV Input -100 to 150
mV (%)
mV Input -5 to 25 mV
(%)
TC Input -20 to 80 mV No temperature conversion. Voltage value entries are directly applied to input val-
(V) uables.
TC Input -100 to 150
mV (V)
TC Input -5 to 25 mV
(V)

Table Appendix 1.3.2-3 Input signal conversion for the resistance temperature detector input module
(SAR145)
Selection Explanation of signal conversion
PT100 Temperature conversion Type PT100 (default)
JPT100 Temperature conversion Type JPT100
PT50 Temperature conversion Type PT50
PT200 Temperature conversion Type PT200
PT500 Temperature conversion Type PT500
PT1000 Temperature conversion Type PT1000
Ni100 (DIN) Temperature conversion Type Ni100 (DIN)
Ni120 (MINCO) Temperature conversion Type Ni120 (MINCO)
RTD Input 0 to 800 ohm (%) No temperature conversion. However, the physical
range (ohm) set in "High Limit" and "Low Limit" is
RTD Input 0 to 4000 ohm (%) converted to 0 to 100% data.
RTD Input 0 to 800 ohm (ohm) No temperature conversion. Resistor value entries
are directly applied to input valuables.
RTD Input 0 to 4000 ohm (ohm)

n High Limit/Low Limit

These are the upper limit values and lower limit values of the measured range in the terminal.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-16

l For SAI143, SAV144, and S2MMM843

Values between 0 and 100% are assigned to the specified measurement range. The meas-
urement range can only be changed for voltage input modules.

Table Appendix 1.3.2-4 High Limit value/Low Limit value

Input type Module model Low limit value of range High limit value of range
Current input SAI143 4 20
S2MMM843 4 20
Voltage input SAV144 1.000 to 10.000 1.000 to 10.000
(default is 1) (default is 5)

l For SAT145 and SAR145

The upper and lower limits are determined based on the combination of the signal conversion
type and the engineering unit symbol. They are shown according to the module type and en-
gineering unit symbol.

Table Appendix 1.3.2-5 Range upper and lower limits for the thermocouple/mV input module (SAT145)
(engineering unit symbol C)
Signal conversion Low limit value of range High limit value of range
Type K -200 1200
Type E -200 900
Type T -200 350
Type J -40 750
Type R 0 1600
Type S 0 1600
Type B 600 1700
Type N -200 1200

Table Appendix 1.3.2-6 Range upper and lower limits for the thermocouple/mV input module (SAT145)
(engineering unit symbol F)
Signal conversion Low limit value of range High limit value of range
Type K -300 2200
Type E -300 1700
Type T -300 650
Type J -40 1400
Type R 0 2900
Type S 0 2900
Type B 1100 3100
Type N -300 2200

Table Appendix 1.3.2-7 Range upper and lower limits for the thermocouple/mV input module (SAT145)
(engineering unit symbol K)
Signal conversion Low limit value of range High limit value of range
Type K 100 1500
Type E 100 1200
Type T 100 600
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-17
Table Appendix 1.3.2-7 Range upper and lower limits for the thermocouple/mV input module (SAT145)
(engineering unit symbol K) (Table continued)
Signal conversion Low limit value of range High limit value of range
Type J 200 1000
Type R 250 1900
Type S 250 1900
Type B 900 2000
Type N 100 1500

Table Appendix 1.3.2-8 Range upper and lower limits for the thermocouple/mV input module (SAT145)
(engineering unit symbol mV)
Signal conversion Low limit value of range High limit value of range
mV Input -20 to 80 mV (%) -20 (default) to 80 -20 to 80 (default)
mV Input -100 to 150 mV (%) -100 (default) to 150 -100 to 150 (default)
mV Input -5 to 25 mV (%) -5 (default) to 25 -5 to 25 (default)
TC Input -20 to 80 mV (V) -20 (default) to 80 -20 to 80 (default)
TC Input -100 to 150 mV (V) -100 (default) to 150 -100 to 150 (default)
TC Input -5 to 25 mV (V) -5 (default) to 25 -5 to 25 (default)

Table Appendix 1.3.2-9 Range upper and lower limits for the resistance temperature detector input
module (SAR145) (engineering unit symbol C)
Signal conversion Low limit value of range High limit value of range
PT100 -200 850
JPT100 -200 500
PT50 -200 850
PT200 -200 850
PT500 -200 850
PT1000 -200 850
Ni100 (DIN) -60 250
Ni120 (MINCO) -80 320

Table Appendix 1.3.2-10 Range upper and lower limits for the resistance temperature detector input
module (SAR145) (engineering unit symbol F)
Signal conversion Low limit value of range High limit value of range
PT100 -300 1500
JPT100 -300 900
PT50 -300 1500
PT200 -300 1500
PT500 -300 1500
PT1000 -300 1500
Ni100 (DIN) -50 450
Ni120 (MINCO) -100 600

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-18
Table Appendix 1.3.2-11 Range upper and lower limits for the resistance temperature detector input
module (SAR145) (engineering unit symbol K)
Signal conversion Low limit value of range High limit value of range
PT100 100 1100
JPT100 100 750
PT50 100 1100
PT200 100 1100
PT500 100 1100
PT1000 100 1100
Ni100 (DIN) 250 500
Ni120 (MINCO) 200 550

Table Appendix 1.3.2-12 Range upper and lower limits for the resistance temperature detector input
module (SAR145) (engineering unit symbol ohm)
Signal conversion Low limit value of range High limit value of range
RTD Input 0 to 800 ohm (%) 0 (default) to 800 0 to 800 (default)
RTD Input 0 to 4000 ohm (%) 0 (default) to 4000 0 to 4000 (default)
RTD Input 0 to 800 ohm (ohm) 0 (default) to 800 0 to 800 (default)
RTD Input 0 to 4000 ohm (ohm) 0 (default) to 4000 0 to 4000 (default)

n Unit
This is the unit for input signal.

l For SAI143, SAV144, and S2MMM843

This is determined by the type of input module.

l For SAT145 and SAR145

The available types depend on symbol conversion.
• Thermocouple/mV input module (SAT145)

Table Appendix 1.3.2-13 Engineering unit symbols for the thermocouple/mV input module (SAT145)
Engineering unit symbol Description Symbol conversion
C Celsius (default) Type K, Type E, Type T, Type J,
Type R, Type S, Type B, Type N
F Fahrenheit
K Kelvin
mV Millivolt mV input (%), TC input (V)

• Resistance temperature detector input module (SAR145)

Table Appendix 1.3.2-14 Engineering unit symbols for the resistance temperature detector input mod-
ule (SAR145)
Engineering unit symbol Description Symbol conversion
C Celsius (default) PT100, JPT100, PT50, PT200,
PT500, PT1000, Ni100 (DIN),
F Fahrenheit Ni120 (MINCO)
K Kelvin
ohm Ohm RTD input (%), RTD input (Ω)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-19

n Detect IOP (High)

This item specifies whether to detect an input open status when the process value (the value
after the input signal was converted (0 to 100%)) exceeds the threshold. When the signal con-
version setting is [SQRT], the value prior to the square-root calculation is used as the process
value (hereinafter referred to as "process value"). The input value at fault is the value speci-
fied by the setting item "Input Processing at Fault".
• No:
An input open circuit error is not detected.
• Yes:
If a process value exceeds the threshold value, an input open circuit error is detected and
the data status of the input variable connected to the applicable channel becomes BAD
(default). The threshold value is specified with [Threshold of IOP (High) %].

n Detect IOP (Low)

This item specifies whether or not to detect an input open circuit error if a process value falls
below the threshold value. The input value at fault is the value specified by the setting item
"Input Processing at Fault."
• No:
An input open circuit error is not detected.
• Yes:
If a process value falls below the threshold value, an input open circuit error is detected
and the data status of the input variable connected to the applicable channel becomes
BAD (default). The threshold value is specified with [Threshold of IOP (Low) %].

n Threshold of IOP (High) %

This item specifies the upper limit level at which an input open circuit is detected. This item
can only be enabled when [Yes] is specified for [Detect IOP (High)]. The process value ex-
ceeding the Detect IOP (High) level means input open.

l For SAI143, SAV144, and S2MMM843

The default value is 112.5% (for current input) and 106.3% (for voltage input).
Note that the following checks are performed even if [No] is specified for [Detect IOP (High)]:
• An error occurs if a value is entered such that the value of [Threshold of IOP (High) %]
becomes equal to or smaller than the value of [Threshold of Transmitter Fault (High) %].
• An error occurs if a value outside the setting range of the analog input module is entered.
«Setting range»
Current input: -18.75% to 118.75% (1 to 23 mA)
However, in the case of SAI143-H style S3 or later or S2MMM843, -23.75% to 118.75%
(0.2 to 23 mA)
Voltage input: Varies depending on the range specification (0.1 to 11 V).
• If the range is set to 1 to 10 V: -10% to 111.1% (0.1 to 11 V)
• If the range is set to 1 to 5 V: -22.5% to 125% (0.1 to 6 V)
In addition to the above checks, the following inputs are checked:
• Number of characters: Up to 7 single-byte characters
• Number of decimal places: Within 2 digits

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-20

l For SAT145 and SAR145

The default value is 106.3%.
Note that the following checks are performed even if [No] is specified for [Detect IOP (High)]:
• If you input a value outside of the -1000.0% to 1000.0% range, an error occurs.
• If you input a value outside of the -25.0% to 125% range, a warning is displayed when
saving.
In addition to the above checks, the following input checks are performed:
• Number of characters: Up to 7 single-byte characters
• Number of decimal places: Within 2 digits

n Threshold of IOP (Low) %

This item specifies the lower limit level at which an input open circuit is detected. This item
can only be enabled when [Yes] is specified for [Detect IOP (Low)]. The process value less
than the Detect IOP (Low) level means input open.

l For SAI143, SAV144, and S2MMM843

Specify a value between -25.0% to 125.0%. The default value is -6.3%.
Note that the following checks are performed even if [No] is specified for [Detect IOP (Low)].
• An error occurs if a value is entered such that the value of [Threshold of IOP (Low) %]
level becomes equal to or greater than the value of [Threshold of Transmitter Fault (Low)
%].
• An error occurs if a value outside the setting range of the analog input module is entered.
«Setting range»
Current input: -18.75% to 118.75% (1 to 23 mA)
However, in the case of SAI143-H style S3 or later or S2MMM843, -23.75% to 118.75%
(0.2 to 23 mA)
Voltage input: Varies depending on the range specification (0.1 to 11 V).
• If the range is set to 1 to 10 V: -10% to 111.1% (0.1 to 11 V)
• If the range is set to 1 to 5 V: -22.5% to 125% (0.1 to 6 V)
In addition to the above checks, the following inputs are checked:
• Number of characters: Up to 7 single-byte characters
• Number of decimal places: Within 2 digits

l For SAT145 and SAR145

Specify a value between -1000.0% to 1000.0%. The default value is 0.0% for resistance tem-
perature detector input and -6.3% for thermocouple input.
Note that the following checks are performed even if [No] is specified for [Detect IOP (Low)].
• If you input a value outside of the -1000.0% to 1000.0% range, an error occurs.
• If you input a value outside of the -25.0% to 125% range, a warning is displayed when
saving.
In addition to the above checks, the following input checks are performed:
• Number of characters: Up to 7 single-byte characters

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-21
• Number of decimal places: Within 2 digits

n Detect Transmitter Fault (High): SAI143, SAV144, S2MMM843

This item specifies whether or not to detect a transmitter error if a process value exceeds the
threshold value. This item is only enabled for current inputs. The input value at fault is the val-
ue specified by the setting item "Input Processing at Transmitter Fault".
• No:
A transmitter error is not detected.
• Yes:
If the process value exceeds the threshold value, a transmitter error is detected and the
data status of the input variable connected to the applicable channel becomes BAD (de-
fault). The threshold value is specified with [Threshold of Transmitter Fault (High) %].

n Detect Transmitter Fault (Low): SAI143, SAV144, S2MMM843

This item specifies whether or not to detect a transmitter error if a process value falls below
the threshold value. This item is only enabled for current inputs. The input value at fault is the
value specified by the setting item "Input Processing at Transmitter Fault".
• No:
A transmitter error is not detected.
• Yes:
If the process value falls below the threshold value, a transmitter error is detected and the
data status of the input variable connected to the applicable channel becomes BAD (de-
fault). The threshold value is specified with [Threshold of Transmitter Fault (Low) %].

n Threshold of Transmitter Fault (High) %: SAI143, SAV144,

S2MMM843
This item specifies the upper limit level at which a transmitter error is detected. This item is
enabled only when [Yes] is specified for [Detect Transmitter Fault (High)]. This item is only en-
abled for current inputs. It is judged that a transmitter error has occurred if the process value
exceeds this setting.
The default value is 106.3%.
Note that the following checks are performed even if [No] is specified for [Detect Transmitter
Fault (High)]:
• An error occurs if a value is entered such that the value of [Threshold of IOP (High) %]
becomes equal to or smaller than the value of [Threshold of Transmitter Fault (High) %].
• An error occurs if a value outside the setting range of the analog input module is entered.
«Setting range»
Current input: -18.75% to 118.75% (1 to 23 mA)
However, in the case of SAI143-H style S3 or later or S2MMM843, -23.75% to 118.75%
(0.2 to 23 mA)

n Threshold of Transmitter Fault (Low) %: SAI143, SAV144,

S2MMM843
This item specifies the lower limit level at which a transmitter error is detected. This item is
enabled only when [Yes] is specified for [Detect Transmitter Fault (Low) ]. This item is only
enabled for current inputs. It is judged that a transmitter error has occurred if the process val-
ue falls below this setting.
The default value is -1.25%.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-22
Note that the following checks are performed even if [No] is specified for [Detect Transmitter
Fault (Low) ]:
• An error occurs if a value is entered such that the value of [Threshold of IOP (Low) %]
level becomes equal to or greater than the value of [Threshold of Transmitter Fault (Low)
%].
• An error occurs if a value outside the setting range of the analog input module is entered.
«Setting range»
Current input: -18.75% to 118.75% (1 to 23 mA)
However, in the case of SAI143-H style S3 or later or S2MMM843, -23.75% to 118.75%
(0.2 to 23 mA)
TIP If it is specified to detect input open (IOP+, IOP-) and transmitter errors (TRNS+, TRNS-), diagnostic informa-
tion messages indicating the occurrence of an alarm and the recovery are notified as follows:
• If the PV value changes, causing the alarm status to change, a diagnostic information message corre-
sponding to the status after change is notified.
• The diagnostic information message indicating recovery from the generated alarm is notified only when the
alarm status recovers to NR (normal). Messages indicating recovery from individual alarms, IOP+/IOP-/
TRNS+/TRNS-, are not notified.
Following (1) to (7) are the Diagnostic information messages that are notified at the change of the PV value:

IOP+

IOP upper limit detection level

TRNS+
Transmitter error upper limit detection level
(2) (3)

(1) (4) (5) (6)

Transmitter error lower limit detection level

TRNS-
IOP lower limit detection level

IOP-
(7)

○ PV value before change

● PV value after change
(1) Occurrence of TRNS+
(2) Occurrence of IOP+ (No messages indicating recovery from TRNS+ are generated.)
(3) Occurrence of TRNS+ (No messages indicating recovery from IOP+ are generated.)
(4) Recovery from channel error
(5) Occurrence of IOP+ (No messages indicating occurrence of/recovery from TRNS+ are generated.)
(6) Recovery from channel error
(7) Occurrence of IOP+ (No messages indicating recovery from IOP- are generated.
No messages indicating occurrence of/recovery from TRNS- are generated.
No messages indicating occurrence of/recovery from TRNS+ are generated.)

Figure Appendix 1.3.2-2 Generation of diagnostic information messages

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-23

n Field Power Diagnosis: SAI143, SAV144

You need to specify the wiring type. It is used to determine the method of power supply diag-
nosis of the FIO input modules. Based on this setting, current input modules perform self-di-
agnosis on whether or not the power is supplied correctly to the field. This item is only ena-
bled for current inputs.

IMPORTANT
Make sure that this setting matches with the 2-wire/4-wire setting that is made by using the
setting pins in the analog input module. If the settings are different from those of the hard-
ware, a channel error occurs in the case of single input for FIO module, or the control shifts to
the standby module in the case of a dual-redundant input module configuration.

• None:
Do not perform field power supply diagnosis.
• 2 wire:
2-wire (Default: Diagnose that the power is supplied to the field. Diagnosis indicates nor-
mal if the power is supplied to the field device.) The input value at fault is the value speci-
fied by the setting item "Input Processing at Fault".
• 4 wire:
4-wire (Diagnose that no power is supplied to the field. Diagnosis indicates normal if no
power is supplied to the field device.) The input value at fault is the value specified by the
setting item "Input Processing at Fault."

n Reference Junction Compensation: SAT145, SAR145

Specify whether or not to perform reference junction compensation. This item is only available
in the thermocouple input module. However, it is not available when [mV Input], [TC Input], or
[Type B] is specified for signal conversions.
• No:
Reference junction compensation is not performed.
• Yes:
Reference junction compensation is performed (default).

n Burnout: SAT145, SAR145

Specify the input operation when there is a disconnection. When detection of input open cir-
cuit errors is enabled and an input open circuit error is detected, the value specified in Input
Processing at Fault is set as the input variable.
• Burnout upscale:
Clamps the input to the upper limit specified by the module when there is a disconnection
(default).
• Burnout downscale:
Clamps the input to the lower limit specified by the module when there is a disconnection.
• No:
Disables the burnout operation.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-24

n Command Line: AIO/DIO module of N-IO

TIP Specify the command line with no more than 250 single-byte characters. If the command line is not set, the
default value is used for each applicable item. The format is as follows:
Item name = Data value, Item name = Data value, ...

l HARTPRI (HART communication master priority order setting)

You can specify whether to consider AIO/DIO module of N-IO as the primary master or the
secondary master.
• Format
HARTPRI=Yes
• Parameter
Yes: The module is set as the primary master. (Default)
No: The module is set as the secondary master.
For example, you can set the handy terminal as the secondary master when the module is set
as the primary master.

l HARTEVENT (notification setting for the changed status of HART device )

You can specify whether or not to notify the changed status of HART device. If No is set, the
changed status that is received by N-IO I/O module is not notified to the SCS. If Current Input
(HART Communication) or Current Output (HART Communication) is selected as signal type,
the default is Yes. If other signal type is selected, the default is No.
• Format
HARTEVENT=No
• Parameter
Yes: The changed status of HART device is notified.
No: The changed status of HART device is not notified.

l HARTPERIOD (setting of detection period by I/O module for the changed

status of HART device)
This item sets the period in which the AIO/DIO module of N-IO detects detailed information of
HART device by using Command #48. This can be set only when HARTEVENT=Yes.
• Format
HARTPERIOD=30
• Parameter
Select either 15, 30, 45, or 60 seconds. The default is 30 seconds.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-25

Appendix 1.3.3 Settings for the AO channel

The following are the settings for the AO channel in I/O Parameter Builder.

Table Appendix 1.3.3-1 Items set for each channel of analog output module
Online change IOM
Setting items Remarks
download (*1) download (*2)
Channel Number
- - -
(Specify Channel Number)
Wiring Position
- - -
(Specify Wiring Position)
I/O Variable Name
- - -
(Specify I/O Variable Name)
Direction
- - -
(Specify Direction)
Comment
- - -
(Specify Comment)
I/O Shutoff Switch
Yes Yes -
(Specify I/O Shutoff Switch)
Output Shutoff Switch
Yes Yes -
(Specify Output Shutoff Switch)
Output Processing at Fault
(Specify Output Value in Detecting Er- Yes Yes -
ror)
Output Value at Fault
Yes Yes -
(Specify Output Value at Fault)
Tight-shut/Full-open
Yes Yes(*3) -
(Specify Tight-shut/Full-open)
Tight-shut Value
Yes Yes -
(Specify Tight-shut Value)
Full-open Value
Yes No -
(Specify Full-open Value)
Detect Short Circuit
Yes Yes -
(Specify Detect Short Circuit)
Detect Disconnection
Yes Yes -
(Specify Detect Disconnection)
P&ID Tag Name
Yes No -
(Specify P&ID Tag Name)
For the AIO/DIO
Command Line module of N-IO, the
Yes Yes
(Specify Command Line) IOM download does
not take place.
*1: Indicates whether the setting can be changed by online change downloading.
Yes: The setting can be changed by online change downloading.
No: Online change downloading is not possible
- : Not a target
*2: Indicates whether the IOM downloading is performed with the online change downloading.
Yes: The IOM downloading is performed together with the online change downloading.
No: The IOM downloading is not performed together with the online change downloading.
- : Not a target
*3: IOM downloading may be performed according to the modified contents.

The setting items that are not explained above as common items are explained below.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-26

n I/O Shutoff Switch: AIO/DIO module of N-IO

Specifies whether or not to activate the I/O shutoff switch when a critical malfunction that can
prevent normal output has occurred. If the I/O shutoff switch is activated, all channels of the
corresponding module other than the AI channel (4-wire) are shut off.
• Enable:
Activates the I/O shutoff switch when a critical malfunction such as an overcurrent occurs
(default).
• Disable:
Does not activate the I/O shutoff switch even when a critical malfunction occurs.

n Output Shutoff Switch: analog output module of FIO

The output shutoff switch can be used to shutoff all the outputs of the module when the mod-
ule encounters a critical malfunction for properly outputting signals, and the whole module be-
comes failure mode (Module HRDY OFF). Enable or disable this switch needs to be specified.
• Enable:
Activate the Output Shutoff switch if a dangerous failure occurs (default).
• Disable:
Do not activate the Output Shutoff switch even if a dangerous failure occurs.

n Output Processing at Fault

This item needs to be specified so that when an error occurs in CPU module (both CPU mod-
ules in redundant configuration) or in the path from CPU to output module, the output module
can act the specified processing for the output from the output channel to the field device.
• Hold:
Hold the outputs upon detection of an error.
• Fixed Value:
Change each output value to the value specified in [Output Value at Fault] upon detection
of an error (default).

n Output Value at Fault

This value is used as a fail-safe value (i.e., output value at fault) when [Output Processing at
Fault] is set to [Fixed Value].
• Specify the value to be output upon error, in a range of -17.19 to 117.19 (%). The default
value is -17.19 %. This setting is effective only when [Output Processing at Fault] is set to
[Fixed Value].
The following input checks are performed.
• Range: -17.19 to 117.19 (%)
• Permitted characters: Single-byte numbers, decimal point, negative sign (-)
• Number of characters: Up to 6 single-byte characters
• Number of decimal places: Within 2 digits

n Tight-shut/Full-open
Tight-shut/full-open is a function that reduces the actual output value to 0% or below when the
manipulated output value is 0%, or increases the actual output value to 100% or above when

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-27
the manipulated output value is 100%, in order to fully close or open the control valve firmly.
Specify whether or not to enable this function.
If PRM (Plant Resource Manager) is used, set "Tight-shut/Full-open" to "Yes" and determine
an appropriate tight-shut value for the connected device.
• Yes:
Enable the tight-shut/full-open function (default). Specify a tight-shut value in [Tight-shut
Value], and a full-open value in [Full-open Value].
The initial output value of the module (i.e., default initial value upon power-on) will be the
same value of the tight-shut output.
• No:
Disable the tight-shut/full-open function. The initial output value of the module (default ini-
tial value upon power-on) is fixed to -17.19% (1.25 mA).
The following graphs show the relationships of logical data (LD) and physical data (PD) when
the data is normal, output is enabled, and output variable is not locked.
<Relationship of LD and PD with tight-shut specification> <Relationship of LD and PD without tight-shut specification>

PD.v[%] Full-open output value PD.v[%] Full-open output value

(default: 106.25%) (default: 106.25%)
118.75
106.25 106.25
100.0 100.0

0.0 -17.19 0.0

100.0 117.19 LD.v[%] 100.0 118.75 LD.v[%]
Tight-shut output value
(default: -17.19%)
-17.19 -17.19

Figure Appendix 1.3.3-1 The following graphs show the relationships of logical data (LD) and physical
data (PD) when the data is normal, output is enabled, and output variable is not locked.

n Tight-shut Value
This item specifies in a range of -17.19 to 0 (%) the actual value to be output when the tight-
shut/full-open function is specified and the output value is 0 %. The default is -17.19 % (1.25
mA). This setting is possible only when [Tight-shut/Full-open] is set to [Yes].
The following input checks are performed.
• Range: -17.19 to 0 (%)
• Permitted characters: Single-byte numbers, decimal point, negative sign (-)
• Number of characters: Up to 6 single-byte characters
• Number of decimal places: Within 2 digits

n Full-open Value
This item specifies in a range of 100 to 117.19 (%) the actual value to be output when the
tight-shut/full-open function is specified and the output value is 100%. The default is 106.25%
(21 mA). This setting is possible only when [Tight-shut/Full-open] is set to [Yes]. To implement
"reverse output", create the necessary application using the application logic.
The following input checks are performed.
• Range: 100 to 117.19 (%)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-28
• Permitted characters: Single-byte numbers, decimal point
• Number of characters: Up to 6 single-byte characters
• Number of decimal places: Within 2 digits

n Detect Short Circuit

This item specifies whether or not to detect short circuit. If a base plate for the barrier is used,
it is fixed to No.
• Yes: Detect short circuit (default).
• No: Do not detect short circuit.

n Detect Disconnection
This item specifies whether or not to detect open circuit.
• Yes: Detect disconnection (default).
• No: Do not detect disconnection.

n Command Line
TIP For the analog output module of FIO, specify the command with no more than 256 single-byte characters. For
the AIO/DIO module of N-IO, specify the command with no more than 250 single-byte characters. If the com-
mand line is not set, the default value is used for each applicable item. The format is as follows:
Item name = Data value, Item name = Data value, ...

l SCREG (short circuit detection level)

This item specifies a short circuit detection level. A short circuit is detected when the wiring
resistance falls below the set value. By specifying a value greater than the wiring resistance
as the short circuit detection level, a short circuit on a device terminal can be detected. The
default value is 70 Ω.
• Format
SCREG=100
• Parameter
Specify an integer value for SCREG. The unit is ohms (Ω) and the specifiable range is 60
to 750 Ω. SCREG must satisfy the following condition:
SCREG (short circuit detection level setting) > Wiring resistance (*1)
*1: Add the resistance of KS cables, etc. to the wiring resistance.

IMPORTANT
If the current output value falls below -6.25 % (3 mA) due to the settings in [Output Value at
Fault] and [Tight-shut Value], the short circuit detection operation becomes unstable in the
range of SCREG setting ±20 Ω.
Therefore, considering the above characteristic and the actual wiring resistance, you need to
set an appropriate SCREG value that allows the short circuit detection to be performed with-
out fail.
If the default SCREG setting (SCREG=70) is used without setting the command line, a short
circuit is not detected if the wiring resistance reaches or exceeds 90 Ω. However, a short cir-
cuit is detected without fail when the wiring resistance is 50 Ω or below.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-29
Example:
When a device is connected by using a KS cable and SCREG is set to 70 Ω

Terminal Output
Device
block module

Wiring KS cable

Figure Appendix 1.3.3-2 Example of a device connection by using a KS cable

• Add the resistance of a KS cable to the wiring resistance.

• If SCREG is set to 70 Ω, the following operations are performed according to the
output current value:
• 3 mA (-6.25%) or above
There is an error of ±10 Ω. A short circuit is always detected if the wiring re-
sistance is 60 Ω or below. A short circuit is not detected if the wiring resist-
ance is 80 Ω or above.
• 1 mA (-18.75%) or above, but below 3 mA
There is an error of ±20 Ω. A short circuit is always detected if the wiring re-
sistance is 50 Ω or below. A short circuit is not detected if the wiring resist-
ance is 90 Ω or above.
• Below 1 mA
A short circuit is not detected.
TIP The resistance value of a KS cable is 230 Ω/km while the resistance value of a standard cable (such as
AWG20) is 23 to 50 Ω/km.

l SOOP (Output open detection level): AIO/DIO module of N-IO

l HARTPRI (HART communication master priority order settings): AIO/DIO

module of N-IO
You can specify whether to consider AIO/DIO module of N-IO as the primary master or the
secondary master.
• Format
HARTPRI=Yes
• Parameter
Yes: The module is set as the primary master. (Default)

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-30
No: The module is set as the secondary master.
For example, you can set the handy terminal as the secondary master when the module is set
as the primary master.

l HARTEVENT (notification settings for the changed status of HART device):

AIO/DIO module of N-IO
You can specify whether or not to notify the changed status of HART device. If No is set, the
changed status that is received by N-IO I/O module is not notified to the SCS. If Current Input
(HART Communication) or Current Output (HART Communication) is selected as signal type,
the default is Yes. If other signal type is selected, the default is No.
• Format
HARTEVENT=No
• Parameter
Yes: The changed status of HART device is notified.
No: The changed status of HART device is not notified.

l HARTPERIOD (setting of detection period by I/O module for the changed

status of HART device): AIO/DIO module of N-IO
This item sets the period in which the AIO/DIO module of N-IO detects detailed information of
HART device by using Command #48. This can be set only when HARTEVENT=Yes.
• Format
HARTPERIOD=30
• Parameter
Select either 15, 30, 45, or 60 seconds. The default is 30 seconds.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-31

Appendix 1.3.4 Settings for the DI channel

The following are the settings for the DI channel in I/O Parameter Builder.

Table Appendix 1.3.4-1 Items set for each channel of a discrete input module
Online change IOM
Setting items Remarks
Download (*1) Download (*2)
Channel Number
- - -
(Specify Channel Number)
Wiring Position
- - -
(Specify Wiring Position)
I/O Variable Name
- - -
(Specify I/O Variable Name)
Direction
- - -
(Specify Direction)
Comment
- - -
(Specify Comment)
Input Processing at Fault
Yes No -
(Specify Input Processing at Fault)
Detect Disconnection
Yes Yes -
(Specify Detect Disconnection)
Detect Short Circuit
Yes Yes -
(Specify Detect Short Circuit)
Detect LFD
Yes Yes -
(Specify Detect LFD)
Pulse Test
Yes Yes -
(Specify Pulse Test)
SOER (Setting for SOER)
Yes Yes -
(Specify Trip Signal)
Trip Signal (Setting for SOER)
Yes No -
(Specify Trip Signal)
P&ID Tag Name
Yes No -
(Specify P&ID Tag Name)
*1: Indicates whether the setting can be changed by online change downloading.
Yes: The setting can be changed by online change downloading.
No: Online change downloading is not required.
- : Not a target
*2: Indicates whether the IOM downloading is performed with the online change downloading.
Yes: The IOM downloading is performed together with the online change downloading.
No: The IOM downloading is not performed together with the online change downloading.
- : Not a target

Each of setting items that are not explained as common items is explained as follows.

n Input Processing at Fault

This item specifies a value that will be passed to the application logic instead of the input from
the field if an error is detected in the input of the channel, including channel errors, DI module
errors and errors in the path from the CPU to the DI module.
• 0: The input value is set to 0 at error detection (default).
• 1: The input value is set to 1 at error detection.
• Hold: The value immediately before the error was detected is retained when an error is
detected.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-32

n Detect Disconnection (Open Circuit)

This item specifies whether to detect disconnection (open circuit). If a base plate for the barri-
er is used, it is fixed to [No].
• Yes: Detect disconnection.
• No: Do not detect disconnection (default). When the disconnection occurs, input value
is 0 and the status is GOOD.

IMPORTANT
If [Yes] is set for [Detect Disconnection], disconnection errors can be detected. Make sure,
however, to connect a wiring check adapter (SCB100) on the channel if you specify [Yes]. If
you specify [Yes] without connecting the adapter, the SCS erroneously detects a disconnec-
tion error whenever the input value is OFF.

n Detect Short Circuit

This item specifies whether or not to detect a short circuit in the wiring. If a base plate for the
barrier is used, it is fixed to [No].
• Yes: Detect short circuit (default).
• No: Do not detect short circuit. When the short-circuit error occurs, input value is 1 and
the status is GOOD.

IMPORTANT
If [Yes] is set for Detect Short Circuit, short-circuit errors can be detected (assuming short cir-
cuit with the power supply line). However, if you specify [Yes] , ensure to install a wiring check
adapter (SCB110) in the channel. If you specify [Yes] without connecting the adapter, the SCS
erroneously detects a short-circuit error whenever the input value is ON.

n Detect LFD: AIO/DIO module of N-IO

This item specifies whether or not to detect line fault in the barrier.
• Type A, Type B: Line fault is detected.
• No: Line fault is not detected.

n Pulse Test: digital input module of FIO

This item specifies whether or not to perform a pulse test (wiring check between the input
channels using pulse output).
• Yes: Perform a pulse test (default)
• No: Do not perform the pulse test

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-33

IMPORTANT
If [Yes] is set for [Pulse Test], wiring short-circuit errors between input channels can be detec-
ted. Make sure, however, to connect a wiring check adapter (SCB110) to the channel if you
specify [Yes] for a channel which receives NC input signals.. If you specify [Yes] without con-
necting the adapter, the SCS cannot detect inter-channel short circuit when the input value is
ON.

n SOER (setting for SOER)

This item specifies whether or not to accumulate events for SOER when a signal changes.
• Yes: Accumulate SOE events when a signal changes (default).
• No: Do not accumulate SOE events.

n Trip Signal (setting for SOER)

This item specifies whether or not to regard an event as a trip occurrence. This setting is only
enabled if [Yes] is set for [SOER].
• No (0):
Changes are not regarded as a trip signal (default).
• OFF TRIP (1):
A change to OFF is regarded as a trip signal and SOE data before and after a trip is stor-
ed in an SCS.
• ON TRIP (2):
A change to ON is regarded as a trip signal and SOE data before and after a trip is stored
in an SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-34

Appendix 1.3.5 Settings for the DO channel

The following are the settings for the DO channel in I/O Parameter Builder.

Table Appendix 1.3.5-1 Items set for each channel of a discrete module
Online change IOM
Setting items Remarks
download (*1) download (*2)
Channel Number
- - -
(Specify Channel Number)
Wiring Position
- - -
(Specify Wiring Position)
I/O Variable Name
- - -
(Specify I/O Variable Name)
Direction
- - -
(Specify Direction)
Comment
- - -
(Specify Comment)
Output Shutoff Switch
Yes Yes -
(Specify Output Shutoff Switch)
DO Shutoff Switch
Yes Yes -
(Specify DO Shutoff Switch)
Output Value in Detecting Error
(Specify Output Value in Detecting Er- Yes Yes -
ror)
Detect Disconnection
Yes Yes -
(Specify Detect Disconnection)
Detect LFD
Yes Yes -
(Specify Detect LFD)
Pulse Test (OFF)
Yes Yes -
(Specify Pulse Test (OFF))
Pulse Test (ON)
Yes Yes -
(Specify Pulse Test (ON))
Low Voltage Pulse Test (On)
Yes Yes -
(Specify Low Voltage Pulse Test (On))
SOER (Setting for SOER)
Yes No -
(Specify Trip Signal)
Trip Signal (Setting for SOER)
Yes No -
(Specify Trip Signal)
P&ID Tag Name
Yes No -
(Specify P&ID Tag Name)
Command Line This item does not
No No
(Specify Command Line) need to be entered.
*1: Indicates whether the setting can be changed by online change downloading.
Yes: The setting can be changed by online change downloading.
No: Online change downloading is not required.
- : Not a target
*2: Indicates whether the IOM downloading is performed with the online change downloading.
Yes: The IOM downloading is performed together with the online change downloading.
No: The IOM downloading is not performed together with the online change downloading.
- : Not a target

Each of setting items that are not explained as common items is explained as follows.

n Output Shutoff Switch: digital output module of FIO

The output shutoff switch can be used to shutoff all the outputs of the module when the mod-
ule encounters a critical malfunction such as the output is clutched to ON status, and the

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-35
whole module becomes failure mode (Module HRDY OFF). If the Output Shutoff switch is ac-
tivated, the output of all DO channels of the relevant module is set to OFF. This setting is not
affected in the event of short circuit. For SDV526, this setting is fixed at Disable and cannot
be changed.
• Enable:
Activate the Output Shutoff switch if a dangerous failure such as the output getting stuck
in the ON status occurs (default).
• Disable:
Do not activate the Output Shutoff switch even if a dangerous failure occurs.

n DO Shutoff Switch: AIO/DIO module of N-IO

You can specify whether or not to activate the DO shutoff switch if a critical malfunction that
can prevent normal output has occurred to the module. If the DO shutoff switch is activated,
all DO channels of the corresponding modules are shut off.
• Enable:
Activate the DO shutoff switch if a critical malfunction such as output stuck occurs (de-
fault).
• Disable:
Do not activate the DO shutoff switch even if a critical malfunction occurs.

n Output Value in Detecting Error

This item specifies a value output from the channel to the field if an error occurs on the CPU
module (both CPU modules in redundant configuration) or in the path from CPU to output
module. This definition is used as the fail-safe value set for the output variables. For SDV526,
this setting is fixed at the default value and cannot be changed.
• 0: Output 0 to the field at error detection (default).
• 1: Output 1 to the field at error detection.
• Hold: The value immediately before the error was detected is maintained.

n Detect Disconnection (Open Circuit detection)

This item specifies whether to detect disconnection (open circuit). If a base plate for the barri-
er is used, it is fixed to No. To detect disconnection for AIO/DIO modules of N-IO, also set
Low Voltage Pulse Test (On) to Yes.
• Yes: Detect disconnection (default)
• No: Do not detect disconnection

n Detect LFD: AIO/DIO module of N-IO

This item specifies whether or not to detect line fault in the barrier.
• Type A, Type B: Line fault is detected.
• No: Line fault is not detected.

n Pulse Test (OFF)

This item specifies whether to implement the off-edge pulse test. This item enables the use of
the off-edge pulse output to test the wiring of the channel that may be clutched to ON status.
For SDV526, this setting is fixed to No. For digital output modules other than SDV526, faults

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 1.3 Settings for channel items > App.1-36
that can be detected are clutched-to-ON faults and short circuits between channels. Only
clutched-to-ON faults can be detected for S2MMM843 and S2MDV843.
• Yes: Perform the off-edge pulse test (default)
• No: Do not perform the pulse test

n Pulse Test (ON)

This item specifies whether to implement the on-edge pulse test. This item enables the use of
the on-edge pulse output to test the wiring of the channel that may be clutched to OFF status.
For SDV526, this setting is fixed to No. For digital output modules other than SDV526, faults
that can be detected are clutched-to-OFF faults, short circuits between channels, and short
circuits while an OFF signal is being output. Only clutched-to-OFF faults can be detected for
S2MMM843 and S2MDV843.
• Yes: Perform the on-edge pulse test
• No: Do not perform the pulse test (default)

n Low Voltage Pulse Test (On): AIO/DIO module of N-IO

This item specifies whether to implement low voltage pulse test (on). This item enables the
use of the on-edge pulse output (5V) to test the wiring in order to detect open circuit and short
circuit while an OFF signal is being output. To detect disconnection, set Detect Disconnection
to Yes.
• Yes: Conduct the low voltage pulse test (on) (default)
• No: Do not conduct the low voltage pulse test

n SOER (setting for SOER)

This item specifies whether or not to accumulate events for SOER when a signal changes.
• Yes: Accumulate SOE events when a signal changes.
• No: Do not accumulate SOE events (default).

n Trip signal (setting for SOER)

n Command Line
This item does not need to be entered.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2. RS original engineering> App.2-1

Appendix 2. RS original engineering

RS original engineering is performed for SCSs whose SCS project is not registered in the AD
Suite and for SCS projects to which I/O list engineering is not applied. This section describes
the engineering methods that are unique to RS original engineering. If you select the RS origi-
nal engineering method, you cannot engineer using iDefine.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.1 Operations on SCS projects that are not registered in the AD project > App.2-2

Appendix 2.1 Operations on SCS projects that

are not registered in the AD
project
This section describes the operations of SCS projects that are not registered in the AD proj-
ect:
• Starting SCS Manager
• Backing up SCS Projects

n Starting SCS Manager

Select [YOKOGAWA ProSafe] > [Workbench]. SCS Manager starts up.
TIP • With Windows 10, select [ProSafe] > [Workbench].
• It is not possible to open SCS Manager and Version Control Tool, or to open SCS Manager and Master
Database Restoring Function at the same time.
• For SCS projects that are engineered in RS original engineering and are registered in an AD project, you
can start SCS Manager from AD Organizer. In System Structure Navigator, select the SCS and click the
button for calling SCS Manager.

n Backing up RS projects
When you back up all the folders under an RS project folder, all the SCS projects containing
the implementation data of an application are also backed up.
The RS project backup shall be saved in external media, by saving folders below the RS proj-
ect folder using Windows Explorer.

IMPORTANT
The RS project backup operation must be performed when the engineering function and SCS
Maintenance Support Tool are not used.
When you choose the standard model of IT security, you need to logon to the PC with a user
account that is authorized to access the ProSafe-RS related folders so as to perform back-
ups.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-3

Appendix 2.2 Definitions of inputs/outputs

When defining inputs and outputs, use Dictionary View, I/O Wiring View and I/O Parameter
Builder to set the following items.

Table Appendix 2.2-1 Definitions of inputs and outputs

Definition Description Tool used
Input/output variable definition Define input/output variables. Dictionary View
Define the configuration of input/output
modules. Specify the model and mounting
Input/output module definition
position (node number and slot number)
of a module, as well as redundancy. I/O Wiring View

Wiring of channels and input/output

Assign input/output variables to channels.
variables
Node parameter setting Set parameters for nodes.
Input/output module parameter setting Set parameters for input/output modules. I/O Parameter Builder
Channel parameter setting Set parameters for channels.

I/O Parameter Builder I/O Wiring View Dictionary View

Input/output module Wiring of channels and
definition input/output variables
Node parameter setting
Input/output module parameter setting Internal variable definition
Channel parameter setting Parameter definition
Wiring of channels
and input/output POU definition
variables
Node FBD/LD/ST (*1)

Input module
Logic
Input variable
Channel 1

Channel 2

Internal variable

Parameter
Output module

Output variable
Channel 1

Channel 2

*1: ST can be used for user-defined FB/FU only.

Figure Appendix 2.2-1 Definitions of inputs/outputs

SEE
ALSO For more information about Dictionary View details, refer to:
"Dictionary View" in "Workbench" in the Workbench User's Guide

n Input/Output definition operations

Input/output definitions are made using Dictionary View, I/O Wiring View and I/O Parameter
Builder.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-4

IMPORTANT
If you changed I/O definitions and saved them in I/O Wiring View, make sure to save them
also in I/O Parameter Builder.

Make input/output definitions according to the following procedure.

1. Input/output variable definition
Define input/output variables using Dictionary View.
2. Definitions of I/O modules
You need to define I/O modules by using I/O Wiring View, and set the mounting positions
of I/O modules (node number and slot number, or unit number) and whether to make
them redundant or not.
3. Wiring of channels and input/output variables
Use I/O Wiring View to associate the channels of the input/output module with the input/
output variables.
4. Parameter settings
Use I/O Parameter Builder to set parameters for nodes, input/output modules and chan-
nels.
TIP Steps “1. Definitions of I/O variables” and “2. Definitions of I/O modules” can be performed independently;
however, both steps must be performed before “3. Wiring of channels and I/O variables."
Steps “3. Wiring of channels and I/O variables” and “4. Parameter settings” can be performed independently
in FIO I/O modules; however, steps must be performed in a sequence in universal type I/O modules. This is
because the signal category is determined by wiring the channel and I/O variable in the universal type I/O
module. You cannot set the parameter when the signal category is not determined because the parameter
settings vary depending on the signal category.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-5

Appendix 2.2.1 I/O Wiring View

I/O Wiring View is used to define input/output modules.
Make the following definitions in I/O Wiring View.
• Creation and deletion of input/output modules
• Specification of mounting positions of input/output modules
• Selection of redundant and single input/output module configurations
• Wiring of variables and channels

IMPORTANT
• When editing definitions in I/O Wiring View, close I/O Parameter Builder first.
• If you changed I/O definitions and saved them in I/O Wiring View, make sure to save
them also in I/O Parameter Builder.

n How to display I/O Wiring View

Select [I/O Wiring] from the [Project] menu of SCS Manager; I/O Wiring View appears.

n I/O Wiring View window structure

I/O Wiring View consists of I/O Wiring Tree View that lists input/output modules and I/O Wiring
Grid View that lists input/output variables that can be wired to channels.
[Add Device] Button Toolbar

ProSafe-RS - [SCS0101(* ) - I/O Wiring - 111:SCS0101( *) ]

File Edit Options Window Help

1: ProSafe: SCS: SDV144(* Digital Input Mod) Unwired variables - Type: IO_BOOL - Dire
2: ProSafe: SCS: SDV531(* Digital Output Mod Name Alias Comment
3: ProSafe: SCS: SAV144(* Analog Input Mod)
4: ProSafe: SCS: SDV144(* Digital Intput Mo

Parameters
NodeNo=1(* *)
SlotNo=4(* *)
IsRedundant=FALSE(* *)
%IU4.0 = DI010401
%IU4.1 = DI010402
%IU4.2 = DI010403
%IU4.3 = DI010404
%IU4.4 = DI010405

I/O Wiring Tree View I/O Wiring Grid View

Figure Appendix 2.2.1-1 I/O Wiring View

SEE
ALSO For more information about Dictionary View details, refer to:
"I/O Wiring View" in "Workbench" in the Workbench User's Guide

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-6

n Setting items in I/O Wiring View

You need to set the following items in I/O Wiring View:
• Model of input/output module
• Device index
• Node number
• Unit number (for N-IO I/O module)
• Slot number
• Specification of redundancy
• Wiring of channels and input/output variables
However, to change the model of input/output module or device index, you need to first delete
the model and then add the new setting.

n Creation of Input/Output modules

To add input/output modules, click "Add Device" button in the toolbar. The Device Selection
dialog box appears.
Device Selection

Target: SCS_TARGET

ProSafe: SCS: SDV531(* Digital Output Module (8-channel,24V DC,Module iso)*)

Device index: 2

Number of channels: 8

Help OK Close

Figure Appendix 2.2.1-2 Device Selection dialog box

l Adding AIO/DIO modules or communication modules

When adding an AIO/DIO module or communication module, specify the model of the module
in I/O Wiring View.
AIO/DIO modules that can be specified are as follows:

Table Appendix 2.2.1-1 AIO/DIO modules that can be specified

AIO/DIO module model Description
SAI143 Analog input module (4 to 20 mA, 16-channel, module isolation)
Analog input module (4 to 20 mA, 16-channel, module isolation, with HART com-
SAI143H
munication)
SAV144 Analog input module (1 to 5 V/1 to 10 V, 16-channel, module isolation)
SAT145 Analog input module (thermocouple/mV, 16-channel, isolated channels)
SAR145 Analog input module (RTD, 16-channel, isolated channels)
Analog output module (4 to 20 mA, 8-channel output, module isolation, with HART
SAI533H
communication)
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-7
Table Appendix 2.2.1-1 AIO/DIO modules that can be specified (Table continued)
AIO/DIO module model Description
SDV144 Digital input module (16-channel, module isolation)
SDV521 Digital output module (4-channel, module isolation)
SDV526 Digital output module (4-channel, module isolation)
SDV531 Digital output module (8-channel, module isolation)
SDV53A Digital output module (8-channel, module isolation)
SDV531L Digital output module (8-channel, module isolation, long distance type)
SDV541 Digital output module (16-channel, module isolation)
S2MMM843 Analog digital I/O modules (16-channel, module isolation)
S2MDV843 Digital I/O modules (16-channel, module isolation)
SEC402/SEC401 (*1) ESB bus coupler module
S2EN402/S2EN404 (*1) N-ESB bus coupler module
*1: Set SEC402/SEC401 and S2EN402/S2EN404 to connect the CPU node and the node by using ESB bus or N-ESB bus.
These are not AIO/DIO modules; however, they are described in the same table.

Communication modules that can be specified are as follows. The communication modules
that can be specified differ depending on the communication type.

Table Appendix 2.2.1-2 Communication modules that can be specified

Communication modules that
can be specified
Communication
Description For Modbus For subsystem
module
slave communi- communication
cation (*1)
ALR111 RS-232C communication module (2-Port) ALR111 ALR111M
ALR121 RS-422/RS-485 communication module (2-Port) ALR121 ALR121M
ALE111 (*2) Ethernet communication module (10BASE-T, 1-Port) ALE111 ALE111M
*1: In I/O Wiring View and I/O Parameter Builder, names are displayed in this way. However, in other SENG windows and the
HIS status display view, the final “M” is not displayed.
*2: When the CPU node of SCS is SSC10D or SSC10S, do not define ALE111.

TIP You can use SSB401, S2EN501, SNT401, SNT411, SNT501, and SNT511, without setting in the I/O Wiring
View.

l Device index
This is an identifier that is attached to I/O modules. Set a unique numeric value in the range of
0 to 65535. Mounting position of the I/O modules is independent; however, it is recommend to
specify the relevant number for the indexes.

IMPORTANT
The index cannot be changed after creating I/O modules.

l Number of channels
The number of channels in the defined input/output module is displayed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-8

n Mounting position of Input/Output module and setting of

redundancy
In I/O wiring tree view of I/O Wiring View, double-click [Parameters] of an I/O module. The I/O
Parameters dialog box appears.
Set the mounting position (node number, unit number, and slot number) and whether or not to
use a redundant configuration. You cannot set a redundant configuration for ALR121 that is
used in ProSafe-SLS communication function.
I/O Parameters - SAI143

Name Value Comment Format

NodeNo 2 WORD
SlotNo 1 WORD
IsRedundant FALSE BOOLEAN

Default OK Cancel

Figure Appendix 2.2.1-3 I/O Parameters dialog box

IMPORTANT
The I/O Parameters dialog box is used to specify the mounting position and redundancy. Pa-
rameters of input/output modules are specified in I/O Parameter Builder.

l Node number (NodeNo), unit number (UnitNo), and slot number (SlotNo)
You need to set the mounting position of the I/O module. The allowed range of the node num-
ber, unit number, and slot number is as follows.

Table Appendix 2.2.1-3 Allowed range of the node number, unit number, and slot number
Allowed range
Setting item FIO I/O module
N-IO I/O module
SCSV1/SCSP1 SCSP2 SCSP3
Node number 1 to 32 1 to 10 1 to 14
Unit number 1 to 6 -
Slot number 1 to 2 (*1) 1 to 8
*1: For single configuration, only one module can be defined in a unit. Either of the slot numbers can be used.

To connect the FIO node, or connect the N-IO node by using optical ESB bus, set the ESB
bus coupler module (SEC402/SEC401) in slot number 7 of node number 1. Because the ESB
bus coupler module has a redundant configuration, an I/O module cannot be set in slot num-
ber 8.
If the N-IO node is connected by using N-ESB bus, set the N-ESB bus coupler module
(S2EN402/S2EN404) in an odd slot number of node number 1. Because the N-ESB bus cou-
pler module has a redundant configuration, an I/O module cannot be set in the adjacent slot
number (odd slot number + 1).

l Is Redundant (switching between redundant and single Input/Output

module configurations)
You can specify whether or not to make the I/O module redundant. You need to specify TRUE
for redundant configuration and FALSE for single configuration. Redundancy can be specified
only for I/O modules that are set in odd slot numbers. Note that the adjacent slot number (the

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-9
odd slot number + 1) must be left unspecified as it is used by the other I/O module in the re-
dundant configuration.

IMPORTANT
• Start I/O Parameter Builder and check that redundant and single configurations are set
correctly for the input/output module and then save the definitions. When switching be-
tween redundant and single configurations, the change is reflected in the SCS after per-
forming offline download or online change download.
• Set the mounting positions in accordance with node numbers, unit numbers, slot num-
bers, and redundancy specifications so that they do not overlap. Overlaps of mounting
position cause errors when building SCS projects.

n Wiring of channels and input/output variables

Wiring is an operation where channels are associated with input/output variables. Assign one
input variable or output variable to one channel.

IMPORTANT
Make sure to use input/output variables in order to access channel data from the application
logic.

Define in I/O Define in

Wiring View Dictionary View

Input module Program

Channel
(application logic)
Channel Input variable
Channel

Input module
Channel Input variable
Channel
Channel

Output module
Channel Output variable
Channel
Channel

Figure Appendix 2.2.1-4 Wiring of channels and input/output variables

When you select a channel in I/O wiring tree view, a list of I/O variables that can be wired to
the channel is displayed in I/O wiring grid view. Double-click the I/O variable for which you
want to set the wiring, and set the wiring of channels. To assign the AO channel to
S2MMM843, do not specify more than eight channels in a module.
The result of wiring is displayed in I/O Wiring Tree View. It is also displayed in the parameter
setting view of each channel in I/O Parameter Builder and Dictionary View.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-10
ProSafe-RS - [SCS0101(* *) - I/O Wiring - 111:SCS0101(* *) ]
File Edit Options Window Help

%IU4.0=DI01 Unwired variables - Type: IO_BO

%IU4.1 Name Alias Comm...
%IU4.2 DI02
DI03
%IU4.3 DI04
Double-click
%IU4.4
%IU4.5 %IU4.0=DI01
%IU4.6 %IU4.1=DI02
%IU4.7 %IU4.2
The association between
%IU4.8 %IU4.3 the channel and input/output
%IU4.4 variable is displayed in
%IU4.9
Tree View
%IU4.10 %IU4.5
%IU4.11 %IU4.6

Figure Appendix 2.2.1-5 Example of wiring between a channel and input/output variable

TIP Deletion of wiring is also performed in I/O Wiring View.

In the AIO/DIO module of FIO, the signal category of the channel is determined based on the
module that is used.
In the universal type I/O module, if you wire the channel and the I/O variable, the signal cate-
gory of the channel is determined. If the signal category changes after re-wiring, all setting
items will be initialized. If the signal category does not change even after re-wiring, the earlier
setting items are retained.
Relationship between the channel and I/O variable is as follows.

Table Appendix 2.2.1-4 Relationship between the channel and I/O variable
Signal category of the Signal type
Type of input/output variable
channel (For universal type I/O modules)
Type: IO_REAL
Current input
AI Direction: Input
Current input (HART communication)
Attribute: Read
Type: IO_REAL
Current output
AO Direction: Output
Current output (HART communication)
Attribute: Write or Free
Type: IO_BOOL
DI Direction: Input Status input
Attribute: Read
Type: IO_BOOL Status output
DO Direction: Output 1.3 A status output (*1)
Attribute: Write or Free 2.0A status output (*1)
*1: You cannot select the modules mounted on the base plate for barrier.

n Settings prohibited in I/O Wiring View

The following settings are not allowed in I/O Wiring View. Even if you make these settings, the
operations of an SCS do not change.
• Channel filtering
Filtering should be set as a channel parameter using I/O Parameter Builder.
• Channel mapping
The functions provided in the Channels Map dialog box cannot be used. Even if you
specify the mapping in I/O Wiring View, the setting is ignored in the SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-11
• Virtual device
It is not allowed to switch to virtual device. If you specify a device as a virtual device in I/O
Wiring View, an error occurs at building.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-12

Appendix 2.2.2 I/O Parameter Builder

I/O Parameter Builder is used to specify parameters for input/output modules defined in I/O
Wiring View.
Make the following settings in I/O Parameter Builder.
• Node parameters
• Input/output module parameters
• Channel parameters

IMPORTANT
When editing settings in I/O Parameter Builder, close I/O Wiring View first.

n How to display I/O Parameter Builder

1. Select the [Engineering] launcher from the [Tools] menu of SCS Manager.
The Engineering launcher menu appears.
2. The Engineering launcher menu appears; select [I/O Parameter Builder]
and launch I/O Parameter Builder.

n I/O Parameter Builder window structure

In I/O Parameter Builder, you need to set parameters for nodes or I/O modules that are selec-
ted on the I/O structure display panel. The tab sheet configuration of the workspace changes
depending on the I/O module model.
Menu Bar Toolbar
I/O Parameter Builder - [Pjt:SCS0101 File:IOMDEFSB.edf]
File Edit View Tool Window

I/O Module Channel

FIO
Node1 Channel Number Wiring Position I/O Variable Name Direction Comment

1-1 SDV144(Device=1) 1 %IU1.0 DI010101 Input ESD SW

1-2 SDV531(Device=2) 2 %IU1.1 DI010102 Input Valve 1 Open
1-3 SAV144(Device=3) 3 %IU1.2 DI010103 Input Valve 2 Open
1-4 SDV144(Device=4)
4 %IU1.3 DI010104 Input Valve 3 Open
1-7 SEC401(Device=7,Redundant)
5 %IU1.4 DI010105 Input Tank A Pressure
Node2
6 %IU1.5 DI010106 Input Tank B Pressure
2-1 ALR111(Device=21)
2-3 SAI533H(Device=23) 7 %IU1.6 DI010107 Input Tank C Pressure
N-IO 8 %IU1.7 DI010108 Input Tank A Pressure
Node1
Message

Ready

Data Menu Area Status Bar Message Display Area Workspace

(I/O Structure Display Pane)

Figure Appendix 2.2.2-1 I/O Parameter Builder

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-13

l Display channel switching commands in layer (indicating CPU nodes in

the View menu on the menu bar)
In I/O Parameter Builder, the following menu items are displayed on the View menu of the
menu bar. This is enabled only when the channel tab is selected on the workspace after se-
lecting the universal type I/O module on the I/O structure display panel.

Table Appendix 2.2.2-1 Display channel switching commands in the View menu
Menu item Description
AI Setting Items Displays AI channels
AO Setting Items Displays AO channels
DI Setting Items Displays DI channels
DO Setting Items Displays DO channels

l AI/AO/DI/DO buttons on the toolbar

In I/O Parameter Builder, the following buttons appear on the toolbar. This is enabled only
when the channel tab is selected on the workspace after selecting the universal type I/O mod-
ule on the I/O structure display panel.

Table Appendix 2.2.2-2 AI/AO/DI/DO buttons on the toolbar

Button Assigned function
AI Same as AI Setting items of the View menu
AO Same as AO Setting items of the View menu
DI Same as DI Setting items of the View menu
DO Same as DO Setting items of the View menu

l Data Menu Area (I/O Structure Display panel)

The I/O structure display panel displays the I/O structure specified in I/O Wiring View. Select
one target (node or input/output module) for which you want to specify a parameter from this
panel. Once you select the target, the corresponding tab appears in the workspace.
The hierarchical structure of the I/O structure display panel is shown below.

Table Appendix 2.2.2-3 Hierarchy of the I/O Structure Display Panel

Layer Description
I/O Displayed as the top layer under which all inputs and outputs are arranged.
Layer indicating types of nodes and I/O modules. FIO and N-IO are displayed.
Type
They are displayed only in SCSP3.
Layer indicating the CPU node, safety node units, and N-IO nodes. Node num-
Node
bers are displayed.
Layer indicating I/O modules. Mounting position, I/O module models, device in-
Module
dex, and classification of redundant and single configurations are displayed.

l Workspace
In the workspace, items that can be specified for the node or I/O module selected on the I/O
structure display panel are classified into separate tabs and displayed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 2.2 Definitions of inputs/outputs> App.2-14
Table Appendix 2.2.2-4 Items displayed in the workspace
Types of the tabs dis-
Setting target Description
played
Node Node tab Parameter setting for the node
Setting of module parameters for the analog input
Module tab
module
Analog input module
Setting of channel parameters for the analog input
Channel tab
module
Setting of module parameters for the analog output
Module tab
module
Analog output module
Setting of channel parameters for the analog output
Channel tab
module
Setting of module parameters for the discrete input
Module tab
module
Digital input module
Setting of channel parameters for the discrete input
Channel tab
module
Setting of module parameters for the discrete output
Module tab
module
Digital output module
Setting of channel parameters for the discrete output
Channel tab
module
Setting of module parameters for the universal type
Module tab
Universal type I/O mod- I/O modules
ule Setting of channel parameters for the universal type
Channel tab
I/O modules
Settings for common parameters of serial communi-
Module tab
cation modules
Serial communication Settings for parameters of Port 1 of serial communi-
Port1 tab
modules cation modules
Settings for parameters of Port 2 of serial communi-
Port2 tab
cation modules
Ethernet communication Settings for parameters of the Ethernet communica-
Module tab
module tion module
Display of parameters for fire and gas communica-
Fire and gas communication modules. The content set with Safety Communi-
Module tab
tion modules cation I/O Editor is shown. You cannot configure the
settings.

TIP No information will be displayed in the workplace even if SEC402/SEC401 or S2EN402/S2EN404 is selected
on the I/O structure display panel.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3. Precautions related to main specification additions and modifications> App.3-1

Appendix 3. Precautions related to main

specification additions and
modifications
This section describes about the cautions and overview of important items for engineering
and maintaining of specification changes and additions that were implemented in the past.
In the SCS, the operation differs with the release number. The operation is determined by the
following conditions:
• The release number of the SENG software where SCS projects are newly created
• The release number of the SCS system program that is downloaded to the SCS. The
SCS system program can be changed by offline downloading to the SCS.
The release number of the SENG software, where SCS projects are newly created, can be
found in the SCS Project Properties dialog box. The release number of the SCS system pro-
gram that is downloaded to the SCS can be found in the SCS State Management window.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.1 The major changes in R1 > App.3-2

Appendix 3.1 The major changes in R1

The following table shows the important contents as a compatibility information after the spec-
ification changes and additions have been implemented in R1.

Table Appendix 3.1-1 The important specification changes in R1

Release number Revised content
R1.02 After R1.02, Variable DB is downloaded to the SCS via online change download only
when variable definitions are modified. Therefore, the time and CRC of Variable DB in
the work database are reflected to the master database and SCS only when variable
definitions are modified.
R1.03 The item Originally Created in SCS Project Properties does not display the revision
number of project data that is created by SENG with a software version prior to
R1.03.
R1.03 The SCS Constants Builder displays PV Status of S_ANLG_S in SCS projects that
are newly created with a software version R1.03 or later. The setting is configured to
No in SCS projects that are created with a software version prior to R1.03 or earlier.
The setting is configured to Yes if this SCS project is imported to the software with a
version R1.03 or later.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-3

Appendix 3.2 The major changes in R2

This section describes the important contents as a compatibility information after the specifi-
cation changes and additions have been implemented in R2.

n List of the important specification changes in R2

The following table shows the important contents as a compatibility information after the spec-
ification changes and additions have been implemented in R2. Detailed description is provi-
ded in the separate section, as necessary.

Table Appendix 3.2-1 The important specification changes in R2

Release number Revised content
R2.01 Security models can be selected with the IT Security Configuration Tool.
R2.01 In the case of SCS with system program R2.01 or earlier, the operation of AIO/DIO
modules stops when changes are made to I/O parameters that require IOM download.
When you perform online change download after modifying such parameter settings,
the output may become 0 depending on the changes made. In order to avoid shutdown
in case when output is 0, measures are required at field side.
R2.02 In the case of SCS with system program R2.02 or later, the operation of AIO/DIO mod-
ules continues even if changes are made to I/O parameters that require IOM down-
load.
R2.02 In SCS with system program before R2.02, the operation of CASE statement of ST
was incorrect. When using SCS projects that are newly created by SENG before
R2.02, there are precautions on when you first perform online change download after
upgrading SENG.
R2.02 The checking operation in Integrity Analyzer has been changed. When using SCS proj-
ects that are newly created by SENG before R2.02, there are precautions on when you
first use Integrity Analyzer after upgrading SENG.
R2.02 The self document operation has been changed. Engineering can be performed for
compatibility with versions before R2.02.
R2.03 In the SCS with SCS system program R2.03 or later, the measured value for scan cy-
cle is displayed in the SCS State Management window and SCS State Display View of
CENTUM HIS. For SCS with system program R2.02 or earlier, the set scan period is
displayed.
R2.03 In SCS with SCS system program R2.03 or later, the scan period for application logic
execution function can be modified by online change download.
R2.03 In SCS with SCS system program R2.03 or later, the addition and deletion of I/O mod-
ules can be performed by online change download. Other items that can be modified
by online change download have also been added.
R2.03 In the SCS with SCS system program R2.03 or later, you can execute automatic IOM
download.
R2.03 In the SCS with SCS system program R2.03 or later, you can use the automatic scan
period extension function. When using this function, use SYS_SCANEXT FB to notify
the state that the scan period is extended by using the automatic scan period exten-
sion function If the SCS projects are created by SENG R2.03 or later, you can define
SYS_SCANEXT.
R2.03 In the SCS with SCS system program R2.03 or later, you can specify the SCS behav-
ior at abnormal calculation. When using this function, use SYS_CERR FB to notify the
occurrence of abnormal calculation and detect that the SCS is continuing the operation
even if the abnormalities have occurred in calculation. If the SCS projects are created
in SENG R2.03 or later, you can define SYS_CERR.
R2.03 With R2.03 or later, the system checks to see if there is possibility that the online
change variables area in the database has been used before executing the offline
download.
R2.03.59 The behaviors of inter-SCS safety communication have been changed. R2.03.59 is the
official version of operations modified at R2.03.51.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-4

n Notes on online change download after upgrading SENG

In R2.02, the problem that the FB for which you have specified a minus value for a label in a
CASE statement does not run properly (*1) has been fixed. Because of this, the behavior of
online change downloading after you have upgraded the SENG to R2.02 will be as follows.
After you have upgraded the SENG to R2.02, if you perform a build for a project created in a
version before R2.02 and execute online change downloading, all the FBs containing any
CASE statement in the ST language will be downloaded (*2) even if no changes have been
made to the logic. Once you rebuild a project of a version earlier than R2.02 on a R2.02 sys-
tem and execute online change downloading, FBs with no logic change will not be downloa-
ded in the subsequent online change downloading.
You can use the Database Validity Check Tool, as necessary, to find out which FBs will be
downloaded before you execute online change downloading.
In a revision before R2.02, FBs containing any CASE statement in which a minus value is
specified for a label do not run correctly, so they can be spotted and removed in the system
test. Therefore, no such FBs should exist in a project. However, if such FBs do exist, the FBs
may start to run normally after downloading.
To avoid such unexpected change in behavior, you should check the project to see if there
are any FBs containing a CASE statement in which a minus value is specified for a label.
• If any FBs using a minus value for a label of CASE statement are found, make sure that
the change in behavior does not cause any adverse effects on the system. (*3)(*4)
• If FBs using a minus value for a label of CASE statement are not found, all the FBs us-
ing CASE statements will be downloaded but the system behavior remains the same; so
you do not need to perform tests again.
*1: If you specify a minus value for a label in a CASE statement in ST, an incorrect database which causes unexpected behavior
may be generated. In the following example, if variable1 is neither “1” nor “2”, “3” is always assigned to aaa.
CASE variable1 OF
1: aaa := 1;
2: aaa := 2;
-1: aaa := 3; (* When the variable1 is neither 1 nor 2, this line is always executed.*)
-2: aaa := 4;
ELSE aaa := 5;
END_CASE;
*2: In this case, Cross Reference Analyzer does not detect the difference of the FBs using CASE statements.
*3: In this case, Cross Reference Analyzer does not detect the difference of the FBs using a minus value for a label of CASE
statement.
*4: To find the locations where CASE statements are used, open multiple STs in Multi-Language Editor and search for “CASE”.

n Behavior of AIO/DIO modules at online change download

If you perform online change download after using I/O Parameter Builder to modify setting
items that require IOM download, AIO/DIO modules continue to operate in SCS system pro-
gram R2.02 or later. However, it stops operation with versions before R2.02.

IMPORTANT
If AIO/DIO module stops operation, a message appears notifying the possible occurrence of
IOM Fail before starting the online download.
You can confirm the system program release number of SCS in the SCS State Management
Window of the SCS maintenance support tool.

This section explains the behaviors of AIO/DIO modules when the SCS system program revi-
sion is earlier than R2.02.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-5

l Behavior of Input modules

• At the time of online change, the data status of all channels of the target module become
BAD, and the diagnostic information message “IOM Fail” appears. The input signals of all
channels of the module are processed according to the [Input Processing at Fault] set-
tings.
• If on-demand HART communication with PRM is performed, the HART communication is
discontinued during the “IOM Fail” status.
• On completion of online change download, the channels’ data automatically return to the
values input to the channels and all data statuses become GOOD.
• A diagnostic information message indicating that the input module has recovered to nor-
mal is output.
• For dual-redundantly configured I/O modules, the odd-numbered module takes the con-
trol right.
TIP If any setting items that require IOM download and the setting of [Input Processing at Fault] or [Input Value at
Fault] are changed online simultaneously, the input value will conform to the changed settings of [Input Pro-
cessing at Fault] and [Input Value at Fault].

l Behavior of Output modules

• At the time of online change, the data status of all channels of the target module be-
come BAD, and the diagnostic information message “IOM Fail” appears. The output val-
ues on all channels change to 0 if the target module is a discrete output module, and
change to the tight-shut output values (*1) if the target module is an analog output mod-
ule.
• If on-demand HART communication with PRM is performed, the HART communication
is discontinued during the “IOM Fail” status.
• On completion of online change download, the data status of all channels become
GOOD, while the output values still remain 0 with a discrete output module or remain the
tight-shut output values with an analog output module.
• A diagnostic information message indicating that the output module has recovered to
normal is output.
• For dual-redundantly configured output modules, the odd-numbered module takes the
control right.
• If the user performs the output enable operation, outputs of the application logic are out-
put from the output module.
*1: A tight-shut output value can be set for each channel using the I/O Parameter Builder.

n Possibilities of online change download

The online change downloadable information for the SCS with a system program before
R2.03 is as follows:

l POU information that is changeable online

There are changes that enables you to execute online change download or offline download
according to each POU type.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-6
Table Appendix 3.2-2 POU information
Modification Online Change (*1)
Program User-Defined FB User-Defined FU
Adding/deleting variables Yes Yes (*2) Yes (*3)
Adding a variable to be named the same No No No
as that of a deleted variable
Changing attributes of variables No No No
Adding/deleting I/O variables Yes - -
Adding/deleting FU Yes Yes Yes
Adding/deleting user-defined FU (*4) Yes Yes Yes
Adding/deleting FB instances Yes No -
Adding/deleting the user-defined FB in- Yes No -
stances (*4)
Adding a FB to be named the same In- No - -
stance as that of a deleted FB
Changing logic Yes Yes (*2) Yes (*2)
Creating/deleting programs Changing pro- No (*5)
gram names
Creating/deleting user-defined Function No (*5)
Blocks Changing user-defined Function
Block names
Creating/deleting user-defined Functions No (*5)
Changing user-defined Function names
*1: Yes: Changeable by online change download.
No: Offline download is required.
*2: It is not allowed to increase/decrease parameter values or change attributes. They cause an error when the database is
downloaded.
*3: An error occurs during downloading.
*4: When user-defined FU/FB are added, they need to be tested. Pre-validated user-defined FU/FB do not need to be tested.
*5: Online change is only possible for local variables.

l I/O module information that is changeable online

The following table shows whether each item of I/O module related information can be
changed by online change downloading.

Table Appendix 3.2-3 I/O module information

Modification Online Change (*1)
Adding nodes No
Deleting nodes No
Changing parameters of nodes Yes
Adding I/O modules No
Deleting I/O modules No
Changing redundant I/O modules No
Changing parameters of I/O modules Yes
Changing parameters of channels Yes
Changing subsystem communication definitions Yes
Defining link between a variable and an idle channel Yes
Deleting link between a channel and a variable Yes
Changing link between a channel and a variable Yes
Continues on the next page

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-7
Table Appendix 3.2-3 I/O module information (Table continued)
Modification Online Change (*1)
Adding, changing or deleting subsystem communica- Yes
tion definitions
Changing wiring of communication input/output FBs Yes
*1: Yes: Changeable by online change download.
No: Offline download is required.

l Constants and network information that are changeable online

The following table shows whether the setting can be changed by online change downloading
in the constant and network related items.

l Builder definitions that are changeable online

The following table shows whether online change downloading is possible after you have
changed definitions using builders.

Table Appendix 3.2-5 Online change download

Builders Online Change (*1)
SCS Constants Builder No
I/O Parameter Builder Yes
Communication I/O Builder Yes
SCS Link Transmission Builder Yes
Modbus Address Builder Yes
Tag Name Builder Yes
Alarm Priority Builder No
Alarm Processing Table Builder No
*1: Yes: Changeable by online change download.
No: Offline download is required.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-8

n Behaviors at abnormal calculation in application logic

If abnormal calculation occurs in the application logic of an SCS with a system program be-
fore R2.03, the SCS stops.

l About behaviors of SCS at abnormal calculation

• If an overflow or division by zero occurs in operations with REAL-type variables, or divi-
sion by zero in operations with integer-type variables, SCS stops.
• When floating-point data is converted to a DINT number by the ANY_TO_DINT function,
if the resultant number exceeds the maximum or falls below the minimum integer values
(i.e. overflow occurs), the SCS stops.
• For the input to ANY_TO_TIME, use a DINT type value in the range from 0 to 86400000.
If a value beyond this range is used, it cannot return a proper time. Note that when a real
number value greater than 4294967295 (the maximum number of the unsigned 32-bit in-
teger) or smaller than -2147483648 (the minimum number of the unsigned 32-bit integer)
is used, the SCS stops.
• If access to the outside of an array occurs, the SCS stops.

n Enhanced checking by Integrity Analyzer

l Checking for multiple writing to the same variable
Multiple writing to the same variable can reduce the program readability and end up down-
loading of programs that cause unintended behavior. Integrity Analyzer in R2.02 detects multi-
ple writing to the same variable and displays a warning message.
This warning message is not output with the revisions before R2.02, but it will be displayed
after you have upgraded to R2.02 when the program contains any multiple writing to the same
variable. If this warning message is displayed, examine the program to find out if you can
eliminate the multiple writing.
If you find that the multiple writing is necessary, acknowledge the results of analysis in Integri-
ty Analyzer and you can download the program to SCS without change. In this case, the pro-
gram can be used as a function allowed for safety application after verifying its validity in user
tests.

l Checking for multiple calls to the same FB instance

Multiple calls to the same function block (FB) instance can lead to an unexpected state in the
system and the program may not behave as intended. Integrity Analyzer in R2.02 detects
multiple calls to the same FB instance and displays a warning message.
This warning message is not output with the revisions before R2.02, but it will be displayed
after you have upgraded to R2.02 when the program contains multiple calls to the same FB
instance. If this warning message is displayed, examine the program to find out if you can
eliminate the multiple calls. If you find that the multiple calls are necessary, acknowledge the
results of analysis in Integrity Analyzer and you can download the program to SCS without
change. In this case, the program can be used as a function allowed for safety application af-
ter verifying its validity in user tests.

l Checking for writing to output variable status

I/O variable statuses (.status) are the data that reflect the actual statuses (normal/abnormal)
of I/O channels. Therefore, they should not be changed by user logic. Integrity Analyzer in
R2.02 detects writing to output variable statuses and raises an error.
In revisions before R2.02, no such error is raised. But this error will be raised after you have
upgraded to R2.02 when there is any program that writes to any output variable status. If an

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-9
error message is displayed, change the program to eliminate the writing to output variable
statuses.

n Specification changes made in SCS system program (Release

number R2.03.51)
l Overview of specification changes
After the SCS system program release number R2.03.51, information on system time is no
longer used to diagnose delay in inter-SCS safety communication and SCS link transmission
safety communication. Specifically, there is no need to consider the gap in the system times
of related SCSs when determining the DLYT value.

IMPORTANT
In order to operate inter-SCS safety communication and SCS link transmission safety commu-
nication with the specification of R2.03.51 or later, upgrade the revision of all SCS system
programs that communicate each other to R2.03.51 or later. If either the revision of the trans-
mission or reception side has not been upgraded, the system operates with the method be-
fore the change, which uses the system time for diagnosis of delay. If the communication is
performed with the method before the change, take the gap in the system times among in-
volved SCSs as the DLYT value as in the past.

l Calculation method of DLYT in Inter- SCS safety communication

How to calculate DLYT in inter-SCS safety communication in case of revisions earlier than
R2.03.51 is explained below.
Reception interval timeout value (OUTT) and inter-FB transmission delay timeout value
(DLYT) are used to set the timeout monitoring time of inter-SCS safety communication.
Temporary transmission delay errors can be detected by monitoring the communication with
OUTT. In addition, you can set DLYT to detect constant transmission delay errors.
DLYT detects not only transmission delay but also time gap among SCSs. For this reason,
determine the set value of DLYT taking generation of erroneous trips due to time gap into con-
sideration as well.
• Reception interval timeout value (OUTT)
An FB for communication on the consumer side (CONS_*) checks the interval of data re-
ception. If the data reception interval exceeds the reception interval timeout value
(OUTT), a communication error occurs and a failsafe value (VAL) is output.
• Transmission delay timeout value (DLYT)
DLYT checks the time from the time an FB for communication on the producer side
(PROD_*) transmits data to the time an FB for communication on the consumer side
(CONS_*) receives the data. This time interval is called inter-FB transmission delay time.
If the status where this interval exceeds the inter-FB transmission delay timeout value
(DLYT) of CONS_* continues for the time indicated by OUTT, a communication error oc-
curs and a failsafe value (VAL) is output.
The guidelines of timeout value settings are given in the following.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-10

• Setting of Reception Interval Timeout Value (OUTT)

OUTT=(select the longer scan period of either the producer or the consumer) x 8 +
(Additional Delay)
Additional Delay
V net Delay
No BCV/CGW used: 0 s
Via BCV/CGW: the number of BCV used x 1 s +
the number of pairs of CGWs used x 2 s
Vnet/IP Delay
Within a Vnet/IP domain: 0 s
Between Vnet/IP domains (No wide area network):
0 s (Regardless of the number of L3SWes)
Between Vnet/IP domains (Wide area network):
1 s (Regardless of the number of L3SWes)
Vnet/IP – V net: V net delay + Vnet/IP delay + V net router delay (1 s)
V net(1) – Vnet/IP – V net(2): V net(1) delay + Vnet/IP delay + V net(2) delay +
Two V net routers’ delay (2 s)
Set 3 seconds to OUTT when the calculated OUTT is shorter than 3 seconds.

• Setting of the Transmission Delay Timeout Value (DLYT)

1. In cases of Inter-SCS safety communications between:
- SCSs in the same domain
- SCSs synchronized with GPS time
- SCSPs synchronized with a Vnet/IP network time
- An SCSP synchronized with SNTP server and an SCSV synchronized with GPS time:
DLYT= (scan period of the producer) + (scan period of the consumer) + (Additional
Delay)
Additional Delay
V net Delay
No BCV/CGW used: 300 ms
Via BCV/CGW: the number of BCV used x 1.3 s +
the number of pairs of CGWs used x 2.3 s
Vnet/IP Delay
Within a Vnet/IP domain: 300 ms
Between Vnet/IP domains (No wide area network):
300 ms (Regardless of the number of L3SWes)
Between Vnet/IP domains (Wide area network):
1.3 s (Regardless of the number of L3SWes)
Vnet/IP – V net: V net delay + Vnet/IP delay + V net router delay (1.3 s)
V net(1) – Vnet/IP – V net(2): V net(1) delay + Vnet/IP delay + V net(2) delay +
Two V net routers’ delay (2.6 s)
Set 3 seconds to DLYT when the calculated DLYT is shorter than 3 seconds.
2. In case of Inter-SCS safety communications between SCSs synchronized with V net time
in SCS in different domains:
DLYT= (the number of BCV used) x 5 s
3. If there are V net routers between SCSs synchronized with V net time in the Inter-SCS
safety communications,
DLYT= (BCV/number of V net router layers) x 5 s

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-11

IMPORTANT
If you set 0 seconds to DLYT and bypass inter-FB transmission check, it is not possible to use
reception data of the given inter-SCS safety communication for the safety purpose.

• In both cases, set the value of OUTT as the DLYT value if OUTT is smaller than DLYT.
• The timeout value is used for calculating system reaction time.

l Precautions when setting DLYT for Inter- SCS safety communication

Precautions to be followed when setting DLYT for inter-SCS safety communication in software
versions R2.03.51 or earlier are given below.
• If IRIG-B time synchronization method is selected, be sure to take the time gap due to
failure of GPS and IRIG-B interface into consideration.
• In the case of SCSs connected to Vnet/IP, time gap due to the SNTP server must be tak-
en into consideration.
• Unify the time synchronization method among SCSs that perform inter- SCS safety com-
munication and determine the setting value such that erroneous trips do not occur due to
time gap among SCSs.
If you set DLYT among SCSs over multiple domains, the following points must also be
taken into consideration.
• If V net time synchronization method is selected, delay of up to 5 seconds in the first level
of BCV-V and 10 seconds in the second level may occur. It is recommended to select
IRIG-B time synchronization if it is found that the gap is outside the allowable range.
• If domains are connected via a gateway for broadband connection, it is recommended to
synchronize V net time of each domain within the allowable range or select IRIG-B time
synchronization.

l Precautions when setting DLYT for SCS link transmission safety

communication
How to calculate DLYT of SCS link transmission safety communication for revisions R2.03.51
or earlier is explained below.
Reception interval timeout value (reception timeout, hereinafter referred to as OUTT) and in-
ter-SCS transmission delay timeout value (transmission timeout, hereinafter refer red to as
DLYT) are used to set the timeout monitoring time of SCS link transmission safety communi-
cation.
Temporary transmission delay errors can be detected by monitoring the communication with
OUTT. In addition, you can set DLYT to detect constant transmission delay errors.
DLYT detects not only transmission delay but also time gap among SCSs. For this reason,
determine the set value of DLYT taking generation of erroneous trips due to time gap into con-
sideration as well.
• Reception interval timeout value (OUTT)
It is valid only when the station on the transmission side is an SCS.
The reception interval refers to the time interval of receiving data by an SCS. Specify the
reception interval timeout value (OUTT) for each communication target. If normal data
cannot be received within the reception interval timeout value (OUTT), a communication
error occurs and a failsafe value is output.
• Inter-SCS transmission delay timeout value (DLYT)
It is valid only when the station on the transmission side is an SCS.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.2 The major changes in R2 > App.3-12
Inter-SCS transmission delay time is the time duration from the time an SCS on the trans-
mission side sends data to the time an SCS on the reception side receives the data. If the
inter-SCS transmission delay timeout value exceeds the DLYT timeout value and the sta-
tus continue for the time specified by OUTT or longer, a communication error occurs and
a failsafe value is output.
The guidelines of timeout value settings are given in the following.
• Setting of reception interval timeout value (OUTT)
OUTT = (Scan frequency on the transmission or reception side, whichever longer) X~ 8
If OUTT is 3 seconds or less, set 3 seconds.
• Guidelines of setting value of transmission delay timeout value (DLYT)
If the time synchronization method employed is V net time synchronization or Vnet/IP
time synchronization, set 3 seconds for DLYT.
In the case of IRIG-B time synchronization, determine DLYT as follows:
DLYT = (Scan frequency on transmission side) + (Scan frequency on the reception side)
+ (Delay addition) + (Time gap addition)
Delay addition: 100 ms
Time gap addition: Determine the setting value so that erroneous trips do not occur due
to time gap.
If DLYT is 3 seconds or less, set 3 seconds.
If 0 seconds are set for DLYT, checking of transmission delay by DLYT is bypassed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.3 The major changes in R3 > App.3-13

Appendix 3.3 The major changes in R3

This section describes the important contents as a compatibility information after the specifi-
cation changes and additions have been implemented in R3. Detailed description is provided,
as necessary.

n List of the important specification changes in R3

The following table shows the important contents as a compatibility information after the spec-
ification changes and additions have been implemented in R3. Detailed description is provi-
ded in the separate section, as necessary.

Table Appendix 3.3-1 The important specification changes in R3

Release number Revised content
R3.01 The specifications for the operation of the ANLG1OO2D, ANLGVOTER, ANLG_S,
ANLGI, and VEL functions blocks have been modified.
R3.02 In the SCS with SCS system program R3.02 or later, you can use the IOM reset func-
tion. To use the IOM reset function, execute IOM download from the IOM download
tool.
R3.02 IT security is strengthened in SOE OPC server R3.02 or later.
R3.02 When using ALE111 in order to perform Modbus slave communication via Modbus
TCP protocol, you must use the style S1 module with unit revision U:2 or later.
R3.02 For SCS projects created by SENG before R3.02.00, the POU related online change
download may be enabled when Clean project is performed.
R3.02.10 In SCS Constants Builder, the definition item name Writing to a Single Holding Register
has been changed to 16-bit Modbus master support mode.

n Function Block parameters

The function block operation specifications have been changed in the SCS system program
release number R3.01.

l Support for Analog Input modules for Thermocouple/RTD

In revisions earlier than R3.01, the following function blocks were able to handle normalization
data from 0 to 100% only with their parameters.

Table Appendix 3.3-2 Function Blocks whose parameters were changed in R3.01
Function block Parameter
ANLG1OO2D IN1, IN2, DEL, VAL, OUT
ANLGVOTER IN1, IN2, IN3, DEL, VAL, OUT
ANLG_S IN, HYS
ANLGI IN, HYS
VEL IN, VL, HYS

l ANLG1OO2D
Due to the specification changes of ANLG1OO2D parameters, the operations of VAL on SCS
are changed as shown in the following table.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.3 The major changes in R3 > App.3-14
Table Appendix 3.3-3 Specification of VAL
Earlier than R3.01 R3.01 or later
-25 to 125%. If you specify a value smaller than Specify as % or engineering units. (No restrictions on
-25.0%, it is processed as -25.0%. If you specify a range in VAL.)
value greater than 125%, it is processed as 125 %.

l ANLGVOTER
Due to the specification changes of ANLGVOTER parameters, the operations of VAL on SCS
are changed as shown in the following table.

Table Appendix 3.3-4 Specification of VAL

Earlier than R3.01 R3.01 or later
-25 to 125%. If you specify a value smaller than Specify as % or engineering units. (No restrictions on
-25.0%, it is processed as -25.0%. If you specify a range in VAL.)
value greater than 125%, it is processed as 125 %.

n Specification of SCS constant "Writing to a Single Holding Register"

has been changed in R3.02.10
"Writing to a Single Holding Register" is a setting item of SCS Constants Builder that was
added in R3.02.00. In R3.02.10, the specification of this setting item has been changed as fol-
lows:
• The item name has been changed from "Writing to a Single Holding Register" to "16-bit
Modbus master support mode".
• When "16-bit Modbus master support mode" is set to Disable, there is no difference in the
behavior between R3.02.00 and R3.02.10.
• The following table describes the behaviors when the SCS system program release num-
ber is R3.02.00 and when the SCS system program release number is R3.02.10 with "16-
bit Modbus master support mode" set to Enable. There is no difference in writing to a Pre-
set Single Register between R3.02.00 and R3.02.10.

Table Appendix 3.3-5 SCS system program release number and the behavior when "16-bit Modbus
master support mode" is set to "Enable"
SCS system program release number Behavior when "16-bit Modbus master support
mode" is set to "Enable"
R3.02.00 (*1) • Preset Single Register (function code 06) is avail-
able.
• If a multiple-register read/write command (function
code 03, 04, or 16) is used specifying an even
number for the beginning reference number or an
odd number for the size of data, the error code 10
or 11 (hex.) is returned.
R3.02.10 • Preset Single Register (function code 06) is avail-
able.
• Data access is possible by using multiple-register
read/write commands (function codes 03, 04, and
16) specifying an even number for the beginning
reference number and/or an odd number for the
size of data. Error code 10 or 11 (hex.) is not re-
turned even if an even number is specified for the
beginning reference number or an odd number is
specified for the size of data.
*1: This means the case when the version of SENG is R3.02.00 and the case when SENG is upgraded to R3.02.10 but offline
downloading to SCS is not yet performed.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.4 Major changes in R4 > App.3-15

Appendix 3.4 Major changes in R4

This section describes important contents as compatibility information after the specification
changes and additions implemented for R4. Detailed descriptions are provided as necessary.

n List of important specification changes in R4

The following table shows important contents as compatibility information after the specifica-
tion changes and additions implemented for R4. Detailed descriptions are provided in sepa-
rate sections as necessary.

Table Appendix 3.4-1 Important specification changes in R4

Release number Revised content
R4.01 Engineering using AD Suite has been enabled.
R4.02 Engineering using iDefine when selecting I/O list engineering has been enabled.
R4.03.10 With SCS projects for which I/O list engineering has been selected, engineering for
communication I/O has been modified to be implemented with Safety Communication
I/O Editor instead of with Communication I/O Builder.

n Communication I/O List Output Tool

Communication I/O List Output Tool is a tool for creating a safety communication I/O list
based on the information of %W included in an SCS project created upon selecting I/O list
engineering with a version between R4.01 through R4.03.00. %W is defined as information on
communication I/O definitions and communication I/O wiring by using Communication I/O
Builder.
When this tool creates a safety communication I/O list, the information of Dictionary View and
I/O Wiring View is referenced as well.
The following packages are required to run this tool:
• RS4E5100 safety system engineering and maintenance function
• RS4E5210 I/O list engineering package
Also note that this tool can only be used by users that belong to the PSF_MAINTENANCE
group.

l Using Communication I/O List Output Tool

In R4.03.10 or later, when performing communication I/O related engineering with an SCS
project for which I/O list engineering has been selected, use Safety Communication I/O Editor
started from AD Organizer. Communication I/O Builder will be used as read-only.
When you change the communication I/O-related engineering data of an SCS project that
was created with a software version from R4.01 through R4.03.00, create a safety communi-
cation I/O list by using this tool and load it into Safety Communication I/O Editor.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 3.4 Major changes in R4 > App.3-16

IMPORTANT
When the engineering is performed by using iDefine, follow these steps after upgrading the
software:
1. Create a safety communication I/O list by using this tool, and import it to an empty safety
communication I/O list.
2. Among the data defined in the Client I/O table of iDefine, enter the data to be mapped to
the user-defined columns of Safety Communication I/O Editor to the the user-defined col-
umns of Safety Communication I/O Editor.
If you import the ProSafe-RS I/O file to iDefine without performing this task, the corre-
sponding data in the Client I/O table of iDefine will be lost.
This is because, in the safety communication I/O list created with this tool, user-defined
columns are empty.
3. Run Export to iDefine.
4. Import the ProSafe-RS I/O file to iDefine.

l Creating a safety communication I/O list

A list cannot be created if the SCS project for which the safety communication I/O list is being
created is in use. Close SCS Manager of the applicable SCS project.
1. Click (ProSafe-RS installation folder)\YOKOGAWA\eng\Tool\RHECIOOutput4310.exe.
The following dialog box appears.

Figure Appendix 3.4-1 Communication I/O List Output Tool screen

2. In the text box for SCS Project Path, specify the path of the SCS project for which the
safety communication I/O list is being created. You can also select the path of the SCS
project by clicking [Browse].
3. In the text box for Communication I/O List, specify the file name of the safety communica-
tion I/O list in the xlsx format of Microsoft Excel. Specify the path where the safety com-
munication I/O list is to be generated by clicking [Browse].
4. Click [Execute].
The safety communication I/O list is generated in the specified folder.

l Format of data included in the safety communication I/O list

When the safety communication I/O list is generated, the SCS project name is added to the
beginning of the P&ID Tag, Program Group, and Communication Group.
Example) If the SCS project name is SCS0101 and the Communication Group is C001, the
Communication Group in the list becomes SCS0101_C001.
For this reason, the safety communication I/O lists of multiple SCS projects included in the
same AD project can be loaded in order in Safety Communication I/O Editor of the same AD
project.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4. Maintenance of sales discontinued products> App.4-1

Appendix 4. Maintenance of sales

discontinued products
This section describes information that is essential for maintenance of "sales discontinued
products".

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.1 Time synchronization of SCSV1 > App.4-2

Appendix 4.1 Time synchronization of SCSV1

SCSV1 is connected on V net. This section describes the specifications and precautions rela-
ted to the time synchronization of SCSV1.

n Time synchronization methods for SCSs connected to V net

There are the following two time synchronization methods, from which the user can select the
more appropriate one for the given application.

Table Appendix 4.1-1 Time synchronization method

Method Description Setting method
Synchronization Uses the mechanism for synchronizing time of each Select "V net" as the time synchro-
with V net time station connected to V net. nization method in SCS Constants
(standard) Builder. (*1)
IRIG-B time syn- Uses the GPS unit as the standard time server. If this Connect a commercially available
chronization output (IRIG-B) is connected to each SCS, the GPS unit and a connector on the
(optional) standard time (date, hour, minute, second) and the CPU node with IRIG-B. Select
synchronization timing are distributed. Each SCS is "IRIG-B" as the time synchroniza-
synchronized with this timing. Since GPS is used, it tion method in SCS Constants
is possible to acquire events with high time accuracy. Builder.
*1: The standard time is specified by the user using SCS Maintenance Support Tool of the SENG or the Adjust Time dialog box
of an HIS.

l Synchronization with V net time

When synchronization with V net time is applied, the user can set the time using SCS Mainte-
nance Support Tool of the SENG or the Adjust Time dialog box of an HIS.

V net time master

(SENG or HIS) HIS FCS

V net time V net time V net time

Time synchronization V net

SCS Other SCSs

CPU CPU

V net time V net time

Time setting

DI module
V net time

Figure Appendix 4.1-1 Synchronization with V net time

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.1 Time synchronization of SCSV1 > App.4-3
TIP If the diagnostic information message, "GPS Interface Unit Error" is notified when synchronization with V net
time, the CPU module need not be replaced if the following conditions are met. Since this message does not
present any problem in practical operations or on safety, you can continue to operate the system.
• If the message is generated only on the control-side CPU module in the redundant configuration immedi-
ately after completion of APC:
If the recovery message, "GPS Interface Unit Recover" is displayed for the control-side CPU module im-
mediately thereafter, the module is not faulty.
• If the V net configuration is unstable:
In a condition where the V net is not connected correctly, such as at startup, a bus configuration error
may occur. In this case, the V net controller in CPU module cannot read time information and this mes-
sage will be notified as a result. Reconnect the bus correctly and start the SCS. If the message no lon-
ger appears, the module is recovered.

l IRIG-B time synchronization

In IRIG-B time synchronization, the time is acquired from the standard time receiver. The
IRIG-B time is used for time stamps of events and alarms set in the CPU. This method produ-
ces more accurate timing for events among SCSs, compared to synchronization with V net
time. The time of the CPU module and DI modules are synchronized to the IRIG-B time.
V net
SCS Other SCSs

CPU
Standard
IRIG-B IRIG-B
time IRIG-B time IRIG-B time
receiver

Time setting

DI module
IRIG-B time

Figure Appendix 4.1-2 IRIG-B time synchronization

n Precautions for time synchronization

Precautions regarding time synchronization of SCSs that are connected on V net are descri-
bed as follows:

l When the V net time synchronization is selected

Changing the V net time may cause the SOE generation order to be reversed. Be sure to take
the timing to set the time and the difference of the time into consideration when setting the V
net time.

l When the IRIG-B time synchronization is selected

• It is necessary to synchronize V net clock with IRIG-B clock.
• If the input of the IRIG-B signal fails, SCS updates the time based on the IRIG-B time im-
mediately before the failure. (No synchronization with V net time)
• When the input of the IRIG-B signal recovers, the displayed time may be set back to syn-
chronize with the IRIG-B time again. In this is case, if you want to check the messages
and events raised before the recovery, do not sort the messages and events until you fin-
ish your check.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.1 Time synchronization of SCSV1 > App.4-4

l If a Vnet/IP domain and a V net domain are connected via a V net router
The following precautions apply in a situation where a V net domain and a Vnet/IP domain are
connected via a V net router and the V net time synchronization and the Vnet/IP time syn-
chronization are selected as their respective time synchronization methods.
• If you are using a V net router of style S3 or above and have enabled the Transfer system
time ([Transfer higher] or [Transfer lower]) in the V net router property of System View for
CENTUM VP R5.01 or later, it is not possible to change the time from a SENG in the do-
main to which the time is transferred.
• If you are using a V net router of a style below S3 and have enabled the [Transfer lower]
of Transfer system time ([Transfer System Time - Transfer lower] for CENTUM VP earlier
than R5.01), it is not possible to change the time from a SENG in the V net domain that
constitutes a lower domain.

l Time discrepancy when multiple domains are connected

You need to consider the following points when connecting multiple domains:
• The time discrepancy that occurs between each connected domain depends on the num-
ber of connected BCV-V units. The discrepancy is a maximum of 5 seconds for the first
level BCV-V and a maximum of 10 seconds for the second level. Estimate these devia-
tions and if they are not acceptable, consider applying IRIG-B time synchronization.
• If a domain is connected through the wide area network gateway units (CGW), you need
to take the measure to keep the differences of the V net time among the domains within
an allowable range. Alternatively, consider applying IRIG-B time synchronization.

n Actions taken at error occurrence in IRIG-B time synchronization

The IRIG-B time synchronization status can be checked in the SCS State Management Win-
dow of the SCS Maintenance Support Tool on the SENG, or in the SCS Status Display view
on the HIS.

l Reasons for time synchronization error

A time synchronization error occurs for the following reasons.
• Disconnected IRIG-B cable connector
• IRIG-B interface unit failure in the SCS
• No time notification due to GPS receiver failure
TIP Examples of GPS receiver failure are listed below.
• Failure in the communication route from the GPS antenna to the GPS receiver
• Antenna failure or receiving problem
What happens when the GPS receiver fails is determined by the specification of the selected GPS receiver.
The following is an example of what might happen when the GPS receiver fails.
• Since GPS signals are no longer received, the GPS receiver operates based on its clock.
• If reception problem continues more than a specified period, the GPS receiver stops operating on its clock
and also stops notifying time information to the connected devices.
Once time notification is stopped, the SCS outputs a diagnostic information message notifying an IRIG-B er-
ror.

l Notification of time synchronization error

• If the IRIG-B time synchronization state has become abnormal when the IRIG-B time syn-
chronization is selected, the SYNC LED on the SCS's CPU module turns off and a diag-

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.1 Time synchronization of SCSV1 > App.4-5
nostic information message indicating an error is notified. If the SCS adopts a redundant
CPU module configuration, diagnostic information messages regarding both modules are
notified.
• Once the IRIG-B time synchronization state returns to normal, a diagnostic information
message indicating a recovery is notified.

l SCS actions taken upon time synchronization error

If time synchronization with IRIG-B stops, the SCS does not synchronize with the V net time.
Instead, the SCS's CPU module updates the time based on the time information input imme-
diately before the error. This condition is called "non-synchronized state." The time is updated
continuously by the CPU module, but time accuracy still drops. Therefore, it is necessary to
recover the IRIG-B error to normal as soon as possible.
While the "not-synchronized state" continues, the SCS takes actions as follows.
• In the not-synchronized state, the difference from the standard time and the time discrep-
ancy among SCSs gradually becomes larger as the time elapses. The difference from the
standard time can reach up to ± 4.32 seconds/day and the time discrepancy among
SCSs can reach up to 8.64 seconds/day. When debugging applications that require high
time precision, it is recommended to connect a GPS simulator to prevent the system from
entering the not-synchronized state.
• If the IRIG-B is not connected at the start of the SCS that uses the IRIG-B time synchroni-
zation, the SCS enters a not-synchronized state where the CPU module updates the time
based on the V net time that was input when the SCS was started.
• If the IRIG-B is not connected at the start of the SCS that uses the IRIG-B time synchroni-
zation, a diagnostic information message notifying the cause of the last CPU shutdown
and a diagnostic information message regarding the switching of the CPU control right,
both of which are normally output when the SCS is started, will not be output.
Once the SCS has been started or CPU control right switched, however, subsequent
messages will be output correctly.
• You can connect normal IRIG-B signals to recover from the error state while the SCS is in
a not-synchronized state. Once the signals are connected, the SCS will operate based on
the correct time information input from the IRIG-B.

IMPORTANT
If the IRIG-B time synchronization is selected, connect the GPS unit via the IRIG-B first, and
then start the SCS.

l Time discrepancy caused by GPS failure

With stations connected to the V net where time synchronization among SCSs is performed
by the IRIG-B time synchronization, a time discrepancy will occur if the GPS or IRIG-B inter-
face fails because time synchronization by V net will not be carried out, either.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.1 Time synchronization of SCSV1 > App.4-6
Table Appendix 4.1-2 Abnormality and time discrepancy
Abnormality Phenomenon Predicted Discrepancy
Antenna When antenna error occurs, the stand- Discrepancy varies with the model of
ard time receiver will count the time standard time receiver. It is necessary
based on its own clock. If the antenna to query the vendor of the recover.
error prolonged, the discrepancy may in-
crease.
If multiple SCSs are using the same re-
ceiver for time synchronization, the dis-
crepancy will not occur for the SCSs.
However, if they use different receivers
for time synchronization, the time dis-
crepancy among the SCSs may occur.
The Standard Time Re- When abnormality occurs, each SCS will The time discrepancy among SCSs
ceiver count the time based on its own clock. If may occur. The maximum discrepancy
IRIG-B Cable abnormality is prolonged, the discrepan- is 8.64 sec/day.
IRIG-B Interface cy from the standard time and the dis-
crepancy among SCSs may increase.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.2 Inter-SCS safety communication in a V net domain> App.4-7

Appendix 4.2 Inter-SCS safety communication

in a V net domain
It is possible to perform Inter-SCS Safety Communication between SCS stations in the same
V net domain or different V net domains to a range of up to 2 BCV or CGW hops.
If Inter-SCS safety communication is executed between the SCSs whose system program re-
lease number is prior to R1.02 in the different V net domains, the communication path cannot
include Vnet/IP domains.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.3 Precautions when engineering CENTUM systems for using BCV and CGW> App.4-8

Appendix 4.3 Precautions when engineering

CENTUM systems for using BCV
and CGW
BCV and CGW engineering are performed by CENTUM ENG. In this case, follow the precau-
tions below.

n TCP/IP communication relay processing

In the CENTUM Integration Configuration, enable the “Transfer TCP/IP to FCS” in the setting
items of BCV or CGW (one of the settings of the CENTUM system builder function), to allow
the BCV or CGW to relay TCP/IP broadcast frames in both directions. This function allows the
TCP/IP communication between the SENG and SCS to be performed across domains.

n Time-related function
BCV and CGW have the function of transferring the time setting when time is set in the Adjust
Time dialog on HIS or SENG.
SEE
ALSO For more information about TCP/IP communication relay processing and time-related functions, refer to:
• Communication Devices Reference (IM 33J20B10-01EN)
• Communication Devices Reference (IM 33K03M10-50E)

n Time discrepancy between domains

A maximum time discrepancy of 5 seconds occurs between two domains connected via a
BCV. Times are not synchronized automatically when the time discrepancy increases be-
tween two domains connected via CGWs. One way to reduce the time discrepancy in either
case is to synchronize each domain with an external absolute time. In this case, ensure that
you do not transfer the time by BCV or receive the system time via CGW.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-9

Appendix 4.4 System expansion with V net

router connection
It is possible for SENG and/or SCS in a Vnet/IP domain to access an SCS in a V net domain.
It is also possible to access an SCS in a V net domain from a CENTUM system and/or
Exaopc client in a Vnet/IP domain via a V net router. The V net router is engineered by using
the system builders of CENTUM.
When connecting a V net router, make sure to check that the load on the V net router caused
by communication passing through the V net router will not become excessive.
TIP V net routers (AVR10D) are classified into two types of behavioral specification, based on their hardware style
and system software revisions. In this document, the two types are defined as "V net router of style S3 or
above" and "V net router of a style below S3" as follows.
• V net router of style S3 or above
The style of AVR10D is S3 or above and the "operating mode" of V net router is set to [Standard mode]
in the System View of CENTUM VP R5.01 or later.
• V net router of a style below S3
For all cases other than the condition described in "V net router of style S3 or later"
If no style is mentioned in explanations about the operation of the V net router in this document, the operation
is common to all AVR10D styles and ProSafe-RS/CENTUM VP software revisions.

The following functions are implemented in the V net router connection configuration.
• Perform engineering and maintenance of SCS in a V net domain from SENG in a Vnet/IP
domain
• Perform engineering and maintenance of SCS in a Vnet/IP domain from SENG in a V net
domain
• Perform safety communication between SCS in a Vnet/IP domain and SCS in a V net do-
main
• Perform operation and monitoring of SCS in a V net domain from an HIS in a Vnet/IP do-
main
• Perform operation and monitoring of SCS in a Vnet/IP domain from an HIS in a V net do-
main
• Refer to data in an SCS in a V net domain and write data to an external communication
FB from an FCS in a Vnet/IP domain
• Refer to data in an SCS in a Vnet/IP domain and write data to an external communication
FB from an FCS in a V net domain
• Collect and display SOE and diagnostic information of an SCS in a V net domain from the
CENTUM Sequence of Events Manager or ProSafe-RS SOE Viewer installed on an HIS
in a Vnet/IP domain
• Install the ProSafe-RS SOE OPC Interface package on a PC in a Vnet/IP domain or V net
domain and use the HIS or SENG as an OPC server to display SCS events on an OPC
client (e.g., Exaquantum) in a Vnet/IP domain.
• Set up an Exaopc server in a Vnet/IP domain or V net domain and access data on the
SCS from an OPC client (e.g., Exapilot) in a Vnet/IP domain.
• V net router of style S3 or above: Connect multiple Vnet/IP domains on a single V net
domain
• V net router of style S3 or above: Execute SCS global switch communication (link trans-
mission between FCS and SCS stations) between a V net domain and a Vnet/IP domain
connected to a V net router.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-10
• V net router of style S3 or above: Effect a time transfer from a V net domain to a Vnet/IP
domain with the V net domain as the clock master, or vice versa
• The following specifications are applied when using a V net router of a style below S3
The V net domain cannot be made the clock master, which means that you cannot
change the time on the Vnet/IP domain even if you set the time from a SENG or HIS on
the V net domain

n Precautions when engineering CENTUM systems for using V net

routers
V net routers are engineered using CENTUM ENG. Take the following precautions when engi-
neering the routers.

l TCP/IP communication relay processing

When the system consists of V net domains and Vnet/IP domains, enable [Transfer TCP/IP to
FCS] in the setting items of the V net router (one of the settings of the CENTUM system build-
er function) to allow the V net router to relay the TCP/IP broadcast frames in both directions.
This function allows the TCP/IP communication between the SENG and SCS to be performed
across domains.

l Transferring system time

• If you are using a V net router style S3 or above, open the "V net router" property from
System View in CENTUM VP R5.01 or later, and specify the Transfer system time
([Transfer upper] or [Transfer lower]). This allows the time on either the V net domain or
the Vnet/IP domain connected to the V net router to be transferred to another domain as
the master.
• In the case of using a V net router style below S3, the Vnet/IP domain is always the upper
domain. It is not possible to transfer the time from the lower domain to the upper domain.

l Time discrepancy between domains

A maximum time discrepancy of 5 seconds occurs between two domains connected via a V
net router. One way to reduce the time discrepancy is to synchronize each domain with an
external absolute time rather than effecting a time transfer via the V net router.

n Inter-SCS safety communication in systems in which a V net domain

and a Vnet/IP domain are connected
Inter-SCS Safety Communications have different network reach ranges according to the spec-
ifications of V net router to be applied.
• Network range for style S3 or above
In a communications route between two stations, network reach is up to 4 hops for con-
nections between a V net domain and a Vnet/IP domain via a V net router, and up to 2
hops for connections between V net domains via a BCV or CGW.
The following figure shows the domain configuration for the maximum network range
when V net routers of style S3 or above are used.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-11

Vnet/IP

AVR10D

Vnet
Vnet Vnet/IP

AVR10D AVR10D

Vnet/IP Vnet

AVR10D BCV

Vnet Vnet
BCV

Network range
Figure Appendix 4.4-1 Network range when a V net router of style S3 or above is used

• Network range for style below S3

The network reach range for inter-SCS Safety Communications is up to 2 hops for con-
nections between V net domains via a BCV or CGW. It is not possible to have a V net
domain on a mid-stream route communicating between Vnet/IP stations. That is, the con-
figuration of SCSs on two Vnet/IP domains with a V net domain in between is not al-
lowed.
The following figure shows the domain configuration for the maximum network range
when V net routers of a style below S3 are used.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-12

Vnet

AVR10D

Vnet/IP Vnet

AVR10D BCV

Vnet Vnet
BCV

Network range
Figure Appendix 4.4-2 Network range when a V net router of a style below S3 is used

n Virtual domain link transmission

If you are using a V net router style S3 or above, SCS Link Transmission Global Switch Com-
munication is possible within a virtual domain by deploying the V net domain and Vnet/IP do-
main connected to that V net router as a single virtual domain.
To enable this feature, you must set up the V net router by using the CENTUM system builder
function.

l Issues to consider when using Virtual domain link transmission

The following are issues to consider when making a virtual domain link transmission.
• If you are using a V net router style S3 or above and CENTUM VP R5.01 or later, you can
enable and disable virtual domain link transmission using the V net router settings inclu-
ded in the system generation function in CENTUM. If you set virtual domain link transmis-
sion for the V net router to [Enabled], link transmission is enabled between the V net do-
main and Vnet/IP domain connected to the V net router.
• To change the Enable/Disable setting for virtual domain link transmission, you will need to
perform an offline download to the V net router.
• The guaranteed reach for virtual domain link transmission is within the same virtual do-
main as the sending station.
• Link transmission is not available between separate virtual domains. When connecting
Vnet/IP domain A and B via V net, for example, Vnet/IP(A) – V net and Vnet/IP(B) – V net
are discrete virtual domains. Consequently, link transmission can not be made between
Vnet/IP(A) and Vnet/IP(B). When connecting V net domain A and B via Vnet/IP, V net(A)
– Vnet/IP and V net(B) – Vnet/IP are discrete virtual domains likewise. Consequently, link
transmission can not be made between V net(A) and V net(B).
• When you make a virtual domain link transmission, there must be no duplication of the
station numbers inside the virtual domain.
• When two or more virtual domains are connected by a domain added to two or more vir-
tual domains, station numbers must be unique in all these virtual domains.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-13

l Example use of Virtual domain link transmission

Virtual domain link transmission is useful in situations such as when migrating part of a V net
domain and changing it to a Vnet/IP domain. The following figure shows an example configu-
ration.

V net domain

FCS0101 FCS0102 SCS0103 SCS0104

Link transmission

Figure Appendix 4.4-3 Example of the configuration of a Link transmission in a V net domain

The following figure shows an example of a migration in which part of a V net domain is split
into a Vnet/IP domain and an FCS0102 and SCS0104 are added to the Vnet/IP domain.

Vnet/IP domain
FCS0202 SCS0204

L2SW

AVR10D

SCS0103
FCS0101
V net domain

Figure Appendix 4.4-4 An example of a V net domain split into V net and Vnet/IP domains

The following figure shows an implementation of a link transmission.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

<Appendix 4.4 System expansion with V net router connection> App.4-14

FCS0202 SCS0204

OK OK
OK
NG (*1)
L2SW

AVR10D
Link
transmission

SCS0103
FCS0101
Virtual domain

*1: Virtual link transmission between SCSs (SCS link transmission safety communication) can not be executed.

Figure Appendix 4.4-5 Example of a Virtual domain link transmission

If the global switch for an SCS that has been migrated from V net to Vnet/IP is referenced by
an FCS, it may, depending on the referencing method, be necessary to re-engineer the appli-
cation concerned with the global switch in the FCS.
• If the global switch in the SCS is referenced by specifying the FCS as %GSnnnss (nnn:
%GS number, ss: station number)
You must re-engineer the FCS application if the SCS station number has been changed.
It is not necessary to re-engineer the application if only the SCS domain number has
been changed.
Example: In the figure above, if FCS0101 references %GS001 in SCS0204, it is not nec-
essary to change "%GS00104" referred to in the FCS0101 application.
• If the global switch in the SCS is referenced by specifying the FCS as %GSnnnSddss
(nnn: %GS number, dd: domain number, and ss: station number)
You must re-engineer the FCS application if the SCS domain number or station number
has been changed.
Example: In the figure above, if FCS0101 references %GS001 in SCS0204, it is necessa-
ry to change "%GS001S0104" referred to in the FCS0101 application to
"%GS001S0204."
• If the global switch for an FCS that has been migrated from V net to Vnet/IP is referenced
by an SCS.
Provided that the station number does not change, it is not necessary to re-engineer the
application concerned with the SCS link transmission. If the station number has been
changed, you must change the station type in the Other Stations tab sheet of the SCS
link transmission definition in SCS Link Transmission Builder, and redefine the wiring in
Data Wiring Definition.

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

Rev-1

Revision information
Title : Engineering Guide Vol. 1
Manual No. : IM 32P01C10-01EN
Aug. 2018/5th Edition/R4.04 or later
Introduction Updated description of registered trademarks of YOKOGAWA.
A1.1, I5 Changed description due to supporting virtualization platform.
C1.2.4, C2.1, Appendix2.1 Changed explanations due to changing the SCS Manager start-up
method.
D1.4.1, D2.3, D5.1 Added descriptions due to adding the Safety I/O Editor mode and
the Safety Communication I/O Editor mode.
D1.4, D2.3, D3.2 Updated the figure due to adding the SCS Manager start-up icon.
Appendix 1.3.2 Changed explanations due to changing the IOP upper/lower limit
detection level of SAI143-H and S2MMM843.
Appendix 1.3.2 Changed explanations due to changing the transmitter error upper/
lower limit detection level of SAI143-H and S2MMM843.
Oct. 2017/4th Edition/R4.03.10
Entire manual Added Safety Communication I/O List and Safety Communication
I/O Editor.
Introduction Added the fire and gas communication module.
A2, A4, A5, A8, A9, A10, B4, B5, Added and updated descriptions regarding the safety subsystem
C2, C3, C5, H1, I1.1, C5, communication function.
G2.2.9, F1
A5, A8, A9, G2.2, G2.2.9, H3.2, Added descriptions regarding the fire and gas communication
I1.2, Appendix 2.2 module.
A10.6, C1.1, C3, E1.2 Updated descriptions due to functional enhancement of Version
Control Tool and Master Database Restoring Function.
C1, E1.3 Added descriptions of Command Line.
Part D Added descriptions of engineering based on the safety communi-
cation I/O list. Deleted descriptions of grid rules and moved them
to Engineering Guide Vol. 2 (IM 32P02C10-01EN). Added and up-
dated descriptions of RS Generation Manager. Added precautions
when performing engineering by using iDefine.
D Added descriptions of settings with PROFINET Configurator.
E1.5 Added precautions related to the fire and gas communication mod-
ule when performing online change download.
H3.1.2 Added FPGA revision to the IOM Report display format.
I1.4 Added descriptions regarding maintenance of field wireless system
devices.
I2 Reorganized the descriptions of proof tests and tests for improving
the rate of operation.
Appendix 3.4 Added descriptions of major changes in R4.
May 2017/3rd Edition/R4.03
Entire manual Changed description regarding the start menu
Introduction Deleted Windows Vista from explanation of trademarks
A1.2, A1.3, H7, I4.7 Added explanation of Vnet/IP ring topology

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

Rev-2
A5, B5, E1.6, H3.1.2, H3.1.3, Added explanation of S2MDV843 and changed explanations in ac-
H4, Appendix 1.2, Appendix 1.3, cordance with addition of S2MDV843
Appendix 2.2
C1.2.5, C2.3, C5.2.5, D1.1.2, Added explanation of the fire and gas equipment transmitter power
E1.2, E1.3, E2.1, E2.3, E3.1, OFF/ON function
A1.2, A1.3.2
C2.3, D1.1.2, E1.3, E2.1, A1.3.2 Added explanation of the chattering alarm suppression function
D2.4 Changed explanation of function blocks
E3.1, E3.2, E3.3, E3.4 Added explanation of the Project Comparing Tool
F2.1.1 Added specifications of the Node Number Setting Tool
Oct. 2016/2nd Edition/R4.02
Entire manual Changed the symbols that indicate warning and caution.
Introduction Updated descriptions in "■ Safety, Protection, and Modification of
the Product," "■ Symbols," and "■ Trademark Acknowledgments."
Added a new term in "■ Full Names and Simplified Terms."
A2.1, B1, B2, C1.2, C2.1, C2.2, Added explanations on iDefine
D1, D1.1, D1.2, D1.3, D1.3.4,
D2, D2.1, D2.2, D2.3, D2.4,
E2.2
Part A, Part C, Part D, Appendix Changed layout
2, Appendix 3
A6, A10, A10.2, A10.3, A10.5, Changed explanations
C2.3, C3, C6, C7, C9, D1.1,
E1.2, E1.5, Appendix 2, Appen-
dix 2.1
Dec. 2015/1st Edition/R4.01
Newly published

n For Questions and More Information Online Query: A query form is available on the fol-
lowing 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

IM 32P01C10-01EN 5th Edition : Aug.31,2018-00

Prosafers
No ratings yet
Prosafers
207 pages
Function Blocks Overview CENTUM VP PDF
No ratings yet
Function Blocks Overview CENTUM VP PDF
286 pages
Mapeh 5 Curriculum - Map Q1 Q4
100% (1)
Mapeh 5 Curriculum - Map Q1 Q4
37 pages
Im32p01b10 01en
No ratings yet
Im32p01b10 01en
142 pages
Function Blocks Reference Vol.2
100% (1)
Function Blocks Reference Vol.2
499 pages
CENTUM - VP Function Blocks Reference Vol1 PDF
100% (1)
CENTUM - VP Function Blocks Reference Vol1 PDF
440 pages
Im32p01c20 01en
No ratings yet
Im32p01c20 01en
726 pages
QUIZ 1 - CHAPTERS 7 AND 8. - Revisión Del Intento
No ratings yet
QUIZ 1 - CHAPTERS 7 AND 8. - Revisión Del Intento
25 pages
VeriLog RTL Design
100% (1)
VeriLog RTL Design
32 pages
Im33j01c10-01en 008 PDF
100% (1)
Im33j01c10-01en 008 PDF
642 pages
Automation Design Suite - Basics
No ratings yet
Automation Design Suite - Basics
176 pages
AeschylusSophoclesEuripides, ACarson PDF
100% (3)
AeschylusSophoclesEuripides, ACarson PDF
135 pages
Im32p01c50 01en
No ratings yet
Im32p01c50 01en
277 pages
Security Guide
No ratings yet
Security Guide
95 pages
S03B1021
100% (1)
S03B1021
492 pages
Im32p01a50 01en
No ratings yet
Im32p01a50 01en
49 pages
Im32p01a50 01en
No ratings yet
Im32p01a50 01en
49 pages
Im32p01a50 01en
No ratings yet
Im32p01a50 01en
44 pages
02.centum VP Installation
100% (1)
02.centum VP Installation
541 pages
Im32q01c10 31e
No ratings yet
Im32q01c10 31e
362 pages
Im32p01b10 01en
No ratings yet
Im32p01b10 01en
141 pages
Poem 1 - Mending Wall
100% (1)
Poem 1 - Mending Wall
2 pages
Branch List As On 30.11.2023
No ratings yet
Branch List As On 30.11.2023
540 pages
Im32p01c50 01en
No ratings yet
Im32p01c50 01en
288 pages
Im33j01c40 01en
No ratings yet
Im33j01c40 01en
78 pages
CS 3000 Installation: User's Manual
No ratings yet
CS 3000 Installation: User's Manual
9 pages
Im33j20b10-01en 007
No ratings yet
Im33j20b10-01en 007
284 pages
License Management: User's Manual
No ratings yet
License Management: User's Manual
90 pages
Ecube Engineering Manual
No ratings yet
Ecube Engineering Manual
111 pages
S02B1021 PDF
100% (1)
S02B1021 PDF
75 pages
Im32q05b10 31e
No ratings yet
Im32q05b10 31e
294 pages
Im32q56h20 31e PDF
No ratings yet
Im32q56h20 31e PDF
214 pages
Im32p01c60 01en
No ratings yet
Im32p01c60 01en
109 pages
S01C5021 PDF
No ratings yet
S01C5021 PDF
243 pages
683920-V12.0.2.04000248 Release Documentation - Jan 2025 - DRAFT
No ratings yet
683920-V12.0.2.04000248 Release Documentation - Jan 2025 - DRAFT
33 pages
Action Replay Codes
No ratings yet
Action Replay Codes
4 pages
Messages: User's Manual
No ratings yet
Messages: User's Manual
72 pages
S56H1021
No ratings yet
S56H1021
50 pages
Prosafe-Rs System Test Reference: User'S Manual
No ratings yet
Prosafe-Rs System Test Reference: User'S Manual
93 pages
Mobile Offensive Security Pocket Guide: A Quick Reference Guide For Android And iOS
From Everand
Mobile Offensive Security Pocket Guide: A Quick Reference Guide For Android And iOS
James Stevenson
1/5 (1)
S01C1021
No ratings yet
S01C1021
281 pages
Safety Manual
No ratings yet
Safety Manual
25 pages
Konica Minolta QMS 3260-4032 Chap11to16 Service Manual
No ratings yet
Konica Minolta QMS 3260-4032 Chap11to16 Service Manual
218 pages
Stardom Plant Resource Manager: User's Manual
No ratings yet
Stardom Plant Resource Manager: User's Manual
26 pages
Ev By Asper
From Everand
Ev By Asper
Asper
No ratings yet
S04B2021 PDF
No ratings yet
S04B2021 PDF
172 pages
Centum VP HIS Operation
No ratings yet
Centum VP HIS Operation
94 pages
Mixed Models Theory and Applications With R 2nd Edition Complete Ebook Edition
100% (16)
Mixed Models Theory and Applications With R 2nd Edition Complete Ebook Edition
17 pages
S01e1021 PDF
No ratings yet
S01e1021 PDF
83 pages
Migrated-FCS (FIO) : User's Manual
No ratings yet
Migrated-FCS (FIO) : User's Manual
19 pages
Engineering Test Guide: User's Manual
No ratings yet
Engineering Test Guide: User's Manual
9 pages
HIS Operation: User's Manual
No ratings yet
HIS Operation: User's Manual
9 pages
Operating Messages: User's Manual
No ratings yet
Operating Messages: User's Manual
9 pages
Engineering Tutorial: User's Manual
No ratings yet
Engineering Tutorial: User's Manual
9 pages
Trig Functionsof Special Angles
No ratings yet
Trig Functionsof Special Angles
23 pages
S06H1021
No ratings yet
S06H1021
90 pages
S56H2021
No ratings yet
S56H2021
55 pages
Prosafe Rs Installation Procedure
No ratings yet
Prosafe Rs Installation Procedure
306 pages
Arabic 101 Labels Guide
No ratings yet
Arabic 101 Labels Guide
7 pages
S02B1021
No ratings yet
S02B1021
75 pages
Prosafe-Rs Vnet/Ip: User'S Manual
No ratings yet
Prosafe-Rs Vnet/Ip: User'S Manual
50 pages
Module 5 (LAB)
No ratings yet
Module 5 (LAB)
3 pages
DAA Unit 5
No ratings yet
DAA Unit 5
22 pages
BSBTEC301 Student Assessment Tasks
No ratings yet
BSBTEC301 Student Assessment Tasks
27 pages
Soran Bushi: Section 1 - Musical Analysis - Traditional Japanese Song
No ratings yet
Soran Bushi: Section 1 - Musical Analysis - Traditional Japanese Song
15 pages
Im32q01e10 31e
No ratings yet
Im32q01e10 31e
86 pages
PH Primary-Setup-Tool en v4p2p1 PDF
No ratings yet
PH Primary-Setup-Tool en v4p2p1 PDF
24 pages
SAFETY IN PETROLEUM FACILITIES TURNAROUND MAINTENANCE
From Everand
SAFETY IN PETROLEUM FACILITIES TURNAROUND MAINTENANCE
Chidi V. Efobi
No ratings yet
List 500 Korean Verbs
No ratings yet
List 500 Korean Verbs
15 pages
Week - 11
No ratings yet
Week - 11
24 pages
Prosafe Rs Im32q01s10 31e
No ratings yet
Prosafe Rs Im32q01s10 31e
27 pages
W004.
No ratings yet
W004.
2 pages
E-Card Lock Manual in English (9.3)
No ratings yet
E-Card Lock Manual in English (9.3)
22 pages
Téléchargements Asterisk
No ratings yet
Téléchargements Asterisk
6 pages
Assignment No 1 (Data Science) - Ashber
No ratings yet
Assignment No 1 (Data Science) - Ashber
9 pages
06 Stability Analysis - Routh Criterion
No ratings yet
06 Stability Analysis - Routh Criterion
14 pages
Week - 9
No ratings yet
Week - 9
28 pages
CRIx 3 LH MZ Ia 98 NR E6 PPC S6 Ip Jol 5 C Xfe Rfo BLP EL
No ratings yet
CRIx 3 LH MZ Ia 98 NR E6 PPC S6 Ip Jol 5 C Xfe Rfo BLP EL
2 pages
Mulesoft MCD Level 2 Dumps by Farrell 05 04 2024 7qa Braindumpscollection
No ratings yet
Mulesoft MCD Level 2 Dumps by Farrell 05 04 2024 7qa Braindumpscollection
9 pages
Design of Light Intensity Detection System Based On STM32: Yunhua Zhou
No ratings yet
Design of Light Intensity Detection System Based On STM32: Yunhua Zhou
5 pages
Critical Response
No ratings yet
Critical Response
3 pages
Challenges and Approaches for Selecting, Assessing and Qualifying Commercial Industrial Digital Instrumentation and Control Equipment for Use in Nuclear Power Plant Applications
From Everand
Challenges and Approaches for Selecting, Assessing and Qualifying Commercial Industrial Digital Instrumentation and Control Equipment for Use in Nuclear Power Plant Applications
IAEA
No ratings yet
Essay Questions - Winter Exam 2014
No ratings yet
Essay Questions - Winter Exam 2014
2 pages
Essay Criteria 101, 2019 Spring Semester
No ratings yet
Essay Criteria 101, 2019 Spring Semester
2 pages
Regulatory Oversight of Ageing Management and Long Term Operation Programme of Nuclear Power Plants
From Everand
Regulatory Oversight of Ageing Management and Long Term Operation Programme of Nuclear Power Plants
IAEA
No ratings yet
Major Solution Components of Industrial Automation: Industrial Automation, #2
From Everand
Major Solution Components of Industrial Automation: Industrial Automation, #2
The Digital Allchemist
No ratings yet
Powerpoint Moral
No ratings yet
Powerpoint Moral
18 pages
Chainsaw Operator's Manual: Chainsaw Safety, Maintenance and Cross-cutting Techniques
From Everand
Chainsaw Operator's Manual: Chainsaw Safety, Maintenance and Cross-cutting Techniques
ForestWorks
5/5 (1)
Safe Use of Smart Devices in Systems Important to Safety in Nuclear Power Plants
From Everand
Safe Use of Smart Devices in Systems Important to Safety in Nuclear Power Plants
IAEA
No ratings yet
Modernité de Shakespeare - Hamlet, Vengeance and The Last of Us Part II
No ratings yet
Modernité de Shakespeare - Hamlet, Vengeance and The Last of Us Part II
6 pages
Geometry: Chapter - 4
No ratings yet
Geometry: Chapter - 4
25 pages
Framework for SCADA Cybersecurity
From Everand
Framework for SCADA Cybersecurity
Richard Clark
5/5 (1)
InduSoft Application Design and SCADA Deployment Recommendations for Industrial Control System Security
From Everand
InduSoft Application Design and SCADA Deployment Recommendations for Industrial Control System Security
Richard Clark
No ratings yet
Practical, Made Easy Guide To Building, Office And Home Automation Systems - Part One
From Everand
Practical, Made Easy Guide To Building, Office And Home Automation Systems - Part One
Kerwin Mathew
No ratings yet