Im32p01a50 01en

User's ProSafe-RS
Manual ProSafe-RS Lite
ProSafe-RS Release
Information
IM 32P01A50-01EN
IM 32P01A50-01EN
7th Edition
i
Introduction
This brochure is the release note that comes with the ProSafe-RS electronic documents. It
provides supplementary information that is not included in the ProSafe-RS electronic docu-
ments. The structure of this document is as follows:
Chapter 1: Usage Notes for R4.06
This chapter explains the points to be noted when applying ProSafe-RS R4.06.
7th Edition : Feb. 2021 (YK) IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

All Rights Reserved. Copyright © 2015, Yokogawa Electric Corporation
ii
Safety Precautions for Use

n Safety, Protection, and Modification of the Product
• To protect the system controlled by the Product and the Product itself and to ensure safe
operation, please observe the safety precautions described in this Manual. Yokogawa
Electric Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe
the safety precautions and instructions when operating the Product.
• If the Product is used in a manner not specified in the User's Manuals, the protection pro-
vided by the Product may be impaired.
• If any protection or safety circuit is required for the system controlled by the Product or for
the Product itself, please install it externally.
• 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. This symbol for the Product indicates the possi-
bility of dangers such as electric shock on personnel and equipment, and also indi-
cates that the user must refer to the User’s Manuals for necessary actions. In the
User’s Manuals, this symbol is used together with a word “CAUTION” or “WARN-
ING” at the locations where precautions for avoiding dangers are described.
<French> Signale qu’il faut faire preuve de prudence. Ce symbole pour le produit
signale la possibilité d’un danger pour le personnel et l’équipement comme un
choc électrique, et signale également que l’utilisateur doit se référer au Manuel de
l’utilisateur afin de prendre les mesures nécessaires. Dans le Manuel de l’utilisa-
teur, ce symbole est utilisé conjointement avec la mention «CAUTION» ou
«WARNING» aux endroits où sont décrites les précautions pour éviter les
dangers.
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 32P01A50-01EN 7th Edition : Feb.24,2021-00

iii
Indicates that a component such as a power supply switch is turned ON.
Indicates that a component such as a power supply switch is turned OFF.
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.

iv
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

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.

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.
n Full Names and Simplified Terms

In the User’s Manuals, simplified terms listed in the following table are used.
Table Info-1 Full Names and Simplified Terms

Full Name Simplified Term
Automation Design Suite AD Suite
Automation Design Organizer AD Organizer
Automation Design Server AD Server
Automation Design project AD project
Automation Design Master Database ADMDB
Automation Design Suite Administration Tool ADS Administration
Tool
iDefine for ProSafe-RS iDefine
Modification Package ModPack
SCSV1-S SCSV1
(SCS supporting the SSC10S/SSC10D safety control units)
SCSP1-S SCSP1
SCSP2-S SCSP2
SCSP3-S SCSP3
(SCS supporting the S2SC70S/S2SC70D safety control units)
SCSL2-S SCSL2
(SCS supporting the L1SC70S/L1SC70D safety control units)
SCSU1-S SCSU1

vii
Copyright and Trademark Notices

n All Rights Reserved
The copyright of the programs and online manuals contained in the software medium of the
Software Product shall remain with YOKOGAWA.
You are allowed to print the required pages of the online manuals for the purposes of using or
operating the Product; however, reprinting or reproducing the entire document is strictly pro-
hibited by the Copyright Law.
Except as stated above, no part of the online manuals may be reproduced, transferred, sold,
or distributed to a third party in any manner (either in electronic or written form including, with-
out limitation, in the forms of paper documents, electronic media, and transmission via the
network). Nor it may be registered or recorded in the media such as films without permission.
n Trademark Acknowledgments
• CENTUM, ProSafe, Vnet/IP, PRM, Exaopc, FieldMate Validator, and STARDOM are reg-
istered trademarks or trademarks of Yokogawa Electric Corporation.
• The names of corporations, organizations, products and logos herein are either regis-
tered trademarks or trademarks of Yokogawa Electric Corporation and their respective
holders.

Toc-1
ProSafe-RS Release Information
IM 32P01A50-01EN 7th Edition
CONTENTS
1. Usage Notes for R4.06......................................................................... 1-1
1.1 Safety Control Stations................................................................................ 1-2
1.2 Engineering................................................................................................. 1-11
1.3 AD Suite.......................................................................................................1-20
1.4 SCS Maintenance Support Tool................................................................ 1-25
1.5 Integration with CENTUM...........................................................................1-26
1.6 SOE (Sequence of Events).........................................................................1-27
1.7 Access Control and Operation History Management Package.............. 1-28
1.8 Installation...................................................................................................1-30
1.9 Security........................................................................................................1-32
1.10 License Management................................................................................. 1-35
1.11 Vnet/IP Interface Package.......................................................................... 1-36
1.12 Miscellaneous............................................................................................. 1-37

<1. Usage Notes for R4.06 > 1-1
1. Usage Notes for R4.06

This chapter explains the points to be noted when applying ProSafe-RS of revision number
R4.06.
SEE
ALSO For more information about operation of Workbench, refer to:
Workbench User's Guide

<1.1 Safety Control Stations > 1-2
1.1 Safety Control Stations

This section describes the notice for using the safety control stations.
n Behavior of SDV526/L1DV526 (100-120 VAC DO Module) in Dual-

Redundant Configuration
If the standby-side SDV526/L1DV526 module recovers (for example, after it is replaced) while
the application logic is sending an ON signal to the dual-redundant SDV526/L1DV526 mod-
ules and the signal from the application logic changes to OFF immediately (within two sec-
onds) after the recovery, it takes a maximum of two seconds until the output signal to the field
changes from ON to OFF.
n Cautions on Input Signals to DI Channels

The DI channels of DI modules and universal type I/O modules have a software filter for filter-
ing the input signals. The chattering signals from the field are filtered out so as to prevent in-
correct actions. Principally, only the signals that hold longer than the filter setting value should
be input to the DI channels.
When the transient signal with the pulse shorter than the filter setting value (such as a chat-
tering signal) repeats and prolongs, this phenomenon can be taken as a channel failure.
When the DI modules or universal type I/O modules with DI channels defined are in dual-re-
dundant configuration, either the control-side or standby-side module fails due to channel fail-
ure.
If an error occurs in a channel but no abnormality is found in field cables and I/O modules, it is
necessary to check whether the signal itself is correct or not.
n Cautions on Replacing SAI143/L1A143 (AI Module)

When replacing dual-redundantly configured AI modules (SAI143/L1A143) during mainte-
nance, the 2-wire/4-wire pin-set on SAI143/L1A143 should be properly positioned according
to the actual setting on the active module. If the settings on the two modules are different,
both modules may fail.
n Lock Status at Online Change of I/O Modules

Locking of I/O modules will be cancelled when the following changes are made by online
change download.
• The model of I/O modules are changed.
• I/O modules are deleted.
• Device index is changed due to the following definition changes of I/O modules: (*1)
• Deletion-and-addition of I/O modules
• Two single I/O modules are change into dual-redundant configuration.
• Dual-redundant I/O modules are changed into two single modules.
• The installation position or dual-redundant specification of communication modules are
changed. (*2)
*1: Whether or not a locked I/O module stays locked after online change download is based on Device index. A locked module
will stay locked if its model and Device index remain the same after the deletion-and-addition, even if the node number or slot
number is changed.
*2: If a serial communication module that is defined to be single configuration and installed in an even-numbered slot is changed
to dual-redundant configuration starting with an odd-numbered slot, it is regarded as "change in installation position."

n Deleting-and-Adding an I/O Module

In the case, for example, where an I/O module is deleted by mistake on I/O Wiring View and a
module definition is added for recovery, the Device index may be changed. If online change
download is performed with a changed Device index, the locking and the inputs/outputs of the
module are discontinued, even if its model, node number, and slot number are unchanged. To
continue the I/O module operation, set the Device index back to the value before deletion and
then perform online change download.
SEE
ALSO For more information about the behavior when online change download is performed with changed Device
indexes, refer to:
“■ Online change of I/O module device index” in E1.5, “Precautions for online change” in Engineering
Guide Vol. 1 (IM 32P01C10-01EN)
n Values under Forcing when Single/Dual-redundant Specification of

the AIO/DIO Module is Changed
When the single/dual-redundant configuration definition of an AIO/DIO module is changed by
online change download, IOM download takes place and the target AIO/DIO module is stop-
ped and initialized. Therefore, the module's values under forcing will be initialized even if the
module is locked (the input values start from the values input from the field and the output
values start from the "default initial value upon power-on")
n Adding Communication Modules by Online Change Download

In a single online change download operation, you cannot add modules for different communi-
cation functions together. This limitation comes from the inability to simultaneously download
different types of communication programs to SCS, which is attempted when you try to add
modules for different types of communication in a single online change download.
If you try to add two or more types of communication modules online, the following error may
occur.
No. 0477: Error in database download to I/O module
Example:
SCS0101 IOM Download Error FIO NODE 01 SLOT 01 Error=A731
A731: Simultaneous downloading of different types of communication programs was a

ttempted.
Workaround:
Ensure to add communication modules for only one type of communication in a single online
change download.
The following table shows the types of communication and the corresponding communication
modules of ProSafe-RS.
Table 1.1-1 Types of communication and communication modules

Type of communication Communication module to use
Subsystem communication Serial ALR111, ALR121
Ethernet ALE111
ProSafe-SLS communi- ALR121
cation
Continues on the next page

Table 1.1-1 Types of communication and communication modules (Table continued)
Type of communication Communication module to use
Modbus slave communication Serial ALR111, ALR121
Ethernet ALE111
DNP3 communication ALE111
For example, you must add only ALR111 or ALR121, which is for Modbus slave communica-
tion, in a single online change download.
Restoration:
From the SCS State Management window, run IOM download for the communication module
that caused the download error.
n Online Change Download of SCS Constants Builder Definitions

Do not download changes in the SCS Constants Builder definitions and other changes togeth-
er in a single online change download operation. You need to download changes in SCS Con-
stants Builder definitions first and then download other changes such as those made to the
application logic. If you download them at the same time by online change download, the be-
havior of the SCS will be as follows because the SCS processes the changes in application
logic first.
Example 1:
If you change the setting of [Behavior at Abnormal Calculation] from [SCS fails] to [SCS con-
tinues] and also make changes and additions to the application logic and download all the
changes together by online change download, the SCS will stop if any abnormal calculation
occurs in the added of modified application logic.
Example 2:
If you change the setting of [Extend Scan Period Automatically] from [No] to [Yes] and also
make changes and additions to the application logic and download all the changes together
by online change download, the automatic scan period extension function will not work during
the downloading. This means that the online change download may not be completed if the
execution time of the application logic exceeds the scan period of the application logic execu-
tion functions as a result of adding a large amount of application logic.
n Configuration Errors Immediately after Offline Download

Even if the IOM download is performed normally during offline download, the I/O module
whose front connector is left open may cause a configuration error while the SCS starts up
after the offline download.
If such a configuration error occurred, plug the connector cable to the front connector of the
I/O module and if necessary, supply power to the module from an external power source.
If the configuration error still remains after plugging in the front connector, there is a possibility
that the IOM download to the I/O module had failed. In this case, use the [IOM Load] com-
mand on the SCS State Management window to execute IOM download manually.
n Configuration Errors after Online Download to Universal Type I/O

Modules
Even when the online downloading to universal type I/O modules (hereafter, referred to as
I/O modules) finished normally, No. 0083 IOM Configuration Error may occur in I/O modules
to which 24 V is not supplied from an external power source on completion of the online
download.(*1) If the error occurs, supply 24 V to the I/O modules from an external power
source.

If the configuration error is not turned off even if 24 V is supplied, the downloading to the I/O
modules may have failed with an error. In this case, execute IOM download for the modules
manually by using the IOM Load command in the SCS State Management window.
*1: This configuration error occurs in the standby-side modules of redundant I/O module pairs that meet all of the following condi-
tions:
• The I/O module has DO channels and is mounted on a base plate with disconnecting terminal, or the module is mounted
on a base plate for barrier.
• The control-side module is installed in slot 1 and the standby-side module is installed in slot 2.
The configuration error does not occur when the standby-side module is installed in slot 1 and the control-side module is in-
stalled in slot 2 and when the I/O module is not redundant.
n Execution of Automatic IOM Download

If you have replaced the standby-side module of dual-redundant I/O modules while the CPU
of the SCS is stopped, IOM download does not take place automatically when you start up
the SCS. (*1)
In this case, use the [IOM Load] command on the SCS State Management window to exe-
cute IOM download manually or retry automatic IOM download by doing one of the following
operations:
• Pull out the I/O module and insert it again.
• Turn off the power to the node where the I/O module is installed and turn it on again.
• Disconnect the ESB bus, N-ESB bus, or optical ESB bus line of the node where the I/O
module is installed and connect it again.
*1: Automatic IOM download does not take place if a configuration error of I/O module has occurred when the CPU modules of
the SCS start up.
n Breakpoint Usage in Target Tests

When using breakpoints on SCS Manager during target tests, the CPU module of the SCS
should be in single configuration. With dual-redundant CPU modules, the following phenom-
ena may occur.
l Control Right Switching

When the CPU modules are in dual-redundant configuration and execution of the application
logic is stopped at a breakpoint, the control-side CPU module may fail and therefore control
right switching is caused. This tends to occur when the scan period of the application logic
execution function is short (for example, 50 ms). When the scan period is 100 ms or longer,
this phenomenon does not occur unless tag data are referenced from CENTUM HIS or other
system.
Workaround:
There is no workaround for this problem.
Restoration:
If the control-side CPU module fails, it automatically restarts once. If the CPU module does
not restart, restart it manually.
l APC Does Not End

If the execution of the application logic is stopped at a breakpoint while APC is running, the
APC may not be completed. However, this rarely happens. It should also be noted that APC
may not be completed if it is started while the application logic is stopped at a breakpoint. In
these cases, the APC does not end even if you delete the breakpoints.
Workaround:
There is no workaround for this problem. Use breakpoints after APC is completed.
Restoration:

Delete the breakpoints, and then restart the standby-side CPU module so that APC runs
again.
n Messages Output upon Control Right Switching of Dual-redundant

CPU Modules: SCSP2, SCSP3, SCSL2
In SCSP2, SCSP3, or SCSL2, if a control right switching of the CPU module occurs during
failure of one of the power supply modules of an I/O node or failure of one of the back board
buses (SB bus) of any I/O module, the following diagnostic information messages may be
generated.
• Recovery (No. 0068) and failure (No. 0067) of a power supply module of a node
• Recovery (No. 0086) and occurrence (No. 0085) of a communication error in an I/O mod-
ule
Also note that, if a control right switching of the CPU module occurs when one of the ESB
buses connected to a node has failed and an I/O module is pulled out, the following diagnos-
tic information message may be generated for the module that is pulled out.
• I/O module database error occurred (No. 0083)
Workaround:
Restoration:
You do not need to take action because only the diagnostic information messages are gener-
ated.
n Messages Output when Standby-side CPU Module is Inserted:

SCSP2, SCSP3
When a stand by-side CPU module (SCP461) is inserted while the SSC60D-F or S2SC70D-F
(Duplexed Safety Control Unit (for Vnet/IP, Wide Range Temperature Type)) is running with a
single CPU module, the following diagnostic information messages may be generated:
• Safety control station fan alarm (No. 0041)
• Recovery from safety control station fan alarm (No. 0042)
If the recovery message is generated, you do not need to take action.
n Behavior at Start Up of an SCS: SCSP2, SCSP3, SCSL2

When an SCSP2, SCSP3, or SCSL2 starts up, a diagnostic information message indicating
module failure (No.0081 Code = C580) is generated for each ALR111/ALR121/ALE111 de-
fined for Modbus slave communication and then a recovery message is generated (No. 0082)
for each of the modules.
Workaround:
Restoration:
You do not need to take action because the SCS recovers from the error by itself.
n Note on the Use of Communication Module for Modbus Slave

Communication: SCSP2, SCSP3, SCSL2
If any ALR111/ALR121/ALE111 is used for Modbus slave communication in SCSP2, SCSP3,
or SCSL2, the scan period for application logic execution functions should be set to 100 ms or
longer.

Setting a scan period shorter than 100 ms may result in an error in Modbus slave communica-
tion.
n Replacement of CPU Module in Stand-alone SCS Configuration

When you replace one of the dual-redundant CPU module of the SCS that is running in stand-
alone SCS configuration, a diagnostic information message informing "GPS interface unit er-
ror" (No. 4129) may be generated regardless of whether GPS is used or not. However, you do
not need to take any action because the SCS is normal even if this message appears. A re-
covery message (No. 4130) is generated after the replacement of the CPU module is finished.
n Notice on Supplying Power to One of a Pair of Power Modules of a

Node
In the case, for example, when an SCS is configured to be powered by dual-line power sup-
ply, if power to the paired power modules in the SCS or its node is turned on one by one, the
digital input or output modules (For SIL 3 SCS: SDV144, SDV521, SDV531, and SDV541. For
SIL 2 SCS: L1DV144, L1DV521, L1DV531, and L1DV541) may fail to start. This problem oc-
curs very rarely.
Under this situation, you will find the message "IOM model Code Error (0x0000 5102)" on the
IOM Report of SCS Maintenance Support Tool.
This problem may occur when power is supplied one by one for each side of the paired power
modules in an SCS where a node is installed with more than three analog input or output
modules (For SIL 3 SCS: SAI143, SAV144, or SAI533. For SIL 2 SCS: L1AI143, L1AV144, or
L1AI533).
Nevertheless, it does not mean that the I/O modules are abnormal.
Avoidance:
Turn on the power to both of the dual-redundant power modules at the same time.
Restoration:
If the digital input or output modules in a node fail to start when power is turned on one by one
for the power modules, and "IOM model Code Error(0x0000 5102)" is indicated in the IOM
Report, turn on the power supplies again before enabling the output of the SCS (before exe-
cuting the Output Enable operation).
n Behavior When an invalid IP Address is Specified in Inter-SCS

Safety Communication
In inter-SCS safety communication, if an invalid IP address is specified on the producer SCS,
the consumer SCS does not start.
If the specified IP address of SCS has any unwanted non-numeric characters following the
valid IP address, an error will result at the build in the case of SCSP3 or SCSL2. In the case
of SCS other than SCSP3 or SCSL2, a warning message appears at the build.
Example: 172.16.dd.ss. (dd: domain number; ss: station number)
This IP address has an unwanted non-numeric character "." (dot) after the station number.
Restoration:
Correct the IP address of the producer SCS, and then perform offline download. Execute a
build for the consumer SCS and perform offline download.
TIP If an invalid IP address is specified in the consumer SCS, inter-SCS safety communication is performed nor-
mally.

n Precautions When Reading the IOM Report of Universal Type I/O

Modules
If one of the following lines are displayed as "Error information in IOM" in the IOM Report of a
universal type I/O module, it is showing "First Error" of the error cause.
• 0201 5522 Field Power Supply Error (Error in the field power supply)
• 0201 5523 Execution of Download (Download was executed)
• 0201 5526 Base Plate Model Code Error (Base plate model code does not match)
In this case, you can confirm the current error information with "Current error information
(CPU detection)" of "Current status."
After recovery, the information in this area will be cleared when a new error occurs.
Example of display:
This is an example of IOM Report when a base plate with disconnecting terminal is defined
while S2MMM843 is mounted on a base plate for barrier. The I/O module detects a base plate
model code error after IOM download is executed to download the database. Therefore, "First
Error" in the module is "Execution of Download." The base plate model code error can be
confirmed with "IOM Configuration Error" that is displayed as the current status.
I/O Module :
Node : 30
Unit :3
Slot :1
Type : S2MMM843(1)
IOM Model : S2MMM843-SS1030S1U000000
Serial No. : C3RJ01022X
Base Plate Type : S2BN1D
Base Plate Model : S2BN5D-xxxC
F-SB Status
Bus S2EN501 Status
1 L Normal
1 R Normal
2 L Normal
2 R Normal
IOM Fail : IOM Configuration Error(0x0000 5103)

First Error Code : 2015/11/16 11:21:03 I/O Error(AP READY-OFF)(0x0000 5105)
IOM Fail : Execution of Download(0x0201 5523)
Channel
1: (IN) Current
Normal
2: -
n Notice on Uninstalling the USB Driver for N-ESB bus Module

In a computer running Windows 8.1 or Windows 10, when the USB driver for N-ESB bus mod-
ule is uninstalled using the installer "Setup.exe" of ProSafe-RS medium, the wizard of unin-
stallation is completed properly. But the USB driver cannot be deleted from the OS. Windows
8.1 is supported only for FieldMate Validator and Node number setting tool.
Avoidance: None.
Restoration:
Even if the USB driver for N-ESB bus module remains, it is not harmful. But if deletion is nec-
essary, delete the USB driver by using the device manager. The name of the USB driver is
"Yokogawa Electric Corporation NIU."

n Key points to note when using N-IO maintenance tool

When you use N-IO maintenance tool, you must connect the computer on which the N-IO
maintenance tools are installed to N-ESB bus module by using a USB cable. In case of
FieldMate Validator, after starting the FieldMate Validator, you must check whether the MAINT
lamp of N-ESB bus module is lit. In case of Node number setting tool, when you set the node
address, you must check whether the MAINT lamp of N-ESB bus module is lit.
When the MAINT lamp of N-ESB bus module is lit, you should not remove and insert the N-
ESB bus module. Before you remove and insert the N-ESB bus module, disconnect the com-
puter from the maintenance port. If you have disconnected the N-ESB bus module by mis-
take, you must repeat the connection procedure of FieldMate Validator or Node number set-
ting tool from the beginning.
If the maintenance port of one of the redundant N-ESB bus modules is disabled, the N-ESB
bus module with disabled maintenance port will not enter maintenance mode when you try to
place the N-ESB bus modules into maintenance mode from FieldMate Validator. If you per-
form the maintenance work in this condition, the I/O modules cannot receive data from
FieldMate Validator correctly, resulting in unstable behavior. In this case, you can place the N-
ESB bus modules in maintenance mode by following these steps:
1. Disconnect the USB cable from the N-ESB bus module.
2. On SCS State Management Window of the Maintenance Support Tool, use the NIU main-
tenance port setting tool to enable the maintenance port of both N-ESB bus modules.
3. Connect the N-ESB bus module and the computer where FieldMate Validator is installed
again, start FieldMate Validator, and confirm that the MAINT lamp is lit on both N-ESB
bus modules.
n Operation of Fire and Gas Communication Module S2LP131 when

port state changes: SCSP3
In very rare cases, the fire and gas communication module S2LP131 may fail due to the fol-
lowing events.
The “Device” stated here refers to either an L2 switch or YFGW410. It does not include GS01.
• The Ethernet cable between the active S2LP131 and the Device was disconnected and
connected.
• The Device connected to the active S2LP131 by Ethernet cable was stopped and started.
• Inactive S2LP131 was connected to an activated Device by Ethernet cable, and then the
S2LP131 was activated.
Workaround:
Restoration:
If S2LP131 fails, first check that the Ethernet cable is connected to the S2LP131 and the De-
vice and that the Device is operating. Next, remove the S2LP131 from the slot, wait at least 2
seconds, and then return it to the slot.
If the S2LP131 failed due to the above events, it will recover to normal, but if the S2LP131 is
faulty, it will remain failed.
n Fire and gas communication system start-up operation: SCSP3

When establishing communication paths (*1) between the fire and gas communication mod-
ule S2LP131 and 9 or more (*2) YFGW410s simultaneously, the connection between the
S2LP131 and the already connected YFGW410s may be severed.

A system alarm may be generated for a disconnected YFGW410.
The severed connection between the S2LP131 and YFGW410 is automatically restored.
*1: Communication path is established when S2LP131 and YFGW410 are started, and when communication path between
S2LP131 and YFGW410 recovers after it is severed.
*2: If the YFGW410 is redundant, count 1 per redundant pair.
Workaround:
Ensure that the number of YFGW410s that establish communication path with S2LP131 si-
multaneously is 8 or less.
For example, when starting up a fire and gas communication system, turn on the power of the
YFGW410s in 8 or less units.
If you need to turn on the power of 9 or more YFGW410s simultaneously, confirm that com-
munication with all YFGW410s and GS01s has been established, and then start the operation
of the plant, considering the possibility that some of the YFGW410s may experience a tempo-
rary communication error. To verify that the communication has been established, check that
there are no system alarms regarding the connections with YFGW410 and GS01.
Restoration:
The severed connection between the S2LP131 and YFGW410 is restored automatically.

<1.2 Engineering > 1-11
1.2 Engineering
In this section the cautions regarding engineering work are explained.
n Project Comparing Tool

l Differences between POUs
If there are POUs that are written in FBD and have no differences except comments for varia-
bles indicated in a diagram and Short Name (a name representing a parameter) for user-de-
fined FU/FB, difference detection between them concludes as no modifications, which results
in being unable to show or print details.
However, the above differences will be marked if POUs have differences other than the
above.
Restoration:
Confirm whether comments for variables or Short Name are different when you perform differ-
ence detection in a variable overview or a parameter overview.
n Online Change Download

l Online Change the Definition of Bindings for the Inter-SCS Safety
Communication
The definition of bindings for the inter-SCS safety communication cannot be changed online.
If a definition of binding is added or deleted, a warning message will be displayed when run-
ning build. And the online change downloading will end with an error.
However, if you perform any of the following operations for the SCS project for which build
and offlilne downloading or online change downloading have not yet been performed after an
upgrade from R4.01.00 or earlier to R4.02.00 or later, no warning message will be displayed
when running build. And the online change downloading will end normally though the
changed bindings will not properly function for the inter-SCS safety communications.
So, the following operations must be avoided before performing online change downloading:
• Moves a consuming side binding variable to a different binding group on the consuming
side.
• Moves or copies a producing side binding variable to a different binding group on the pro-
ducing side.
• Excludes a consuming side binding variable from the consuming side binding group and
deletes the variable.
• Excludes a producing side binding variable from the producing side binding group and
deletes the variable.
Restoration:
If the above changes were performed, offline downloading should be performed instead of on-
line change downloading.
n Online Monitoring
l Online Monitoring after Upgrading SENG
After upgrading SENG to R1.01.30 or a later revision and running build, when starting Debug
Mode without downloading to SCS (either online or offline), the following error messages will
occur for online monitoring:

FI20861.LTRP: Adding variable for spy has failed! No symbol table for debug found
!
FI20861.OUT: Adding variable for spy has failed! No symbol table for debug found!
Workaround/Restoration:
After upgrading SENG to R1.01.30 or a later revision and running build, it is necessary to per-
form downloading to SCS (either online or offline) before starting Debug Mode.
l Windows for Online Monitoring

When performing online monitoring, do not use window other than those below:
• I/O Lock Window
• Multi-Language Editor
• Dictionary
• Spy List Window
l Generate Debug Information

After offline downloading, if the [Generate debug information] of a POU is changed from OFF
to ON and then online downloaded, the "Call stack is in overflow" error dialog box may be dis-
played twice for each step when the Workbench is in Debug mode and running the step de-
bugging.
Workaround:
If you change the setting of [Generate debug information], perform offline downloading. If you
are executing the SCS Simulator, you should restart it.
Restoration:
Perform offline downloading. If you are executing the SCS Simulator, you should restart it.
l Online Monitoring FBD

At first, you use Multi-Language Editor to open an FBD and change a function block into a
function or an operator. Then save the modified contents only once, build and download the
FBD. When you execute online monitoring of the FBD, the output of the modified function or
operator may be indicated with "???."
Workaround:
After changing a function block into a function or an operator, the modified contents need to
be saved twice. And then build and download.
The same phenomenon of "???" indication also occurs in Logic Simulator and SCS Simulator.
Therefore, it is necessary to confirm on the Logic Simulator and SCS Simulator that the "???"
indication is not existing, and then start downloading.
Restoration:
Open the FBD that calls the erroneous function or operator, and then save the FBD and build.
And then perform online download the FBD.
l Drag and Drop on Link Architecture View

On Link Architecture View, when you change a user-defined function block into a user-defined
function with drag and drop operation, and then build and offline download without opening
and saving the POUs that call the modified user-defined function, the output of the modified
user-defined function will be displayed "???" at monitoring.
Workaround:
Before build and offline download, the POUs that call the dragged and dropped function need
to be saved. And then run build and offline download.

The same phenomenon of "???" indication also occurs in Logic Simulator and SCS Simulator.
Therefore, it is necessary to confirm on the Logic Simulator and SCS Simulator that the "???"
indication is not existing, and then start downloading.
Restoration:
Open the POUs that call the erroneous function, and then save and build the POUs and then
perform online download of the POUs.
n I/O Lock Window

l Online Change Download
If you perform an Online change download, close the I/O Lock Window.
n Workbench
l POU Name
The POU names (including FU/FB, user-defined FU/FB, libraries registered FU/FB and pro-
gram) should be unique to each other.
l Interruption from Keyboard during Data Transmission

Do not perform unnecessary keyboard operation during data transmission such as saving da-
ta to the hard disk or sending data to SCS by Workbench.
Do not type any key on the keyboard especially during the following operations:
• Build
• Offline Download
• Master Database Offline Download
• Online Change Download
• IOM Download
• Restore Master Database
• Version Control Check-In/Check-Out
l Display in Dictionary View

When you are using Dictionary View in Debug/Simulation mode while [Locked variables] or
[Unlocked variables] is selected for filtering, the display in the Dictionary View will be as fol-
lows if you change the variable group or variable scope on the tree shown in the left pane.
• Filtering is disabled and all the variables that belong to the selected variable group or
scope are displayed regardless of whether the variables are locked or not.
• The filter status indicated in the upper right of the window remains unchanged even after
the filter is disabled.
Workaround:
There is no workaround for this problem. You can find out whether the variables are locked or
not by the yes (locked) or no (not locked) indication in the [Locked] column of the Dictionary
View.
Restoration:
After you have changed the variable group or variable scope, always select [All variables] to
cancel the filtering and then re-select the filter ([Locked variables] or [Unlocked variables]) you
want to use.

l Use of LD Element OR in FBD

If the LD element, OR(LD Vertical OR Connection) is used in FBD, incorrect database which
does not behave as expected may be generated.
b01 b02 b04
b07
b03 b05 b06
LD Vertical OR Connection
Figure 1.2-1 Error example
Use the OR operator instead of the LD Vertical OR Connection.
OR OR
b01 b02 b04
b07
b03 b05 b06
OR Operator
Figure 1.2-2 Correction
l Character-string Constant
If you want a '$' to be denoted in a character-string constant, it should be '$$' according to the
rule. But if a character-string constant ends with a '$', a Build error is raised.
If you need to end a character-string constant with '$$' to denote '$', use '$24' for the '$$'.
n Error Messages Displayed on Workbench

The operation messages displayed on Workbench are explained below.
l Build a Project without POU

When building a project without POU for the second time, the following error message will be
displayed.
ERROR: GetFileAttributesEx (File Path)\Symbols_Target.xtc.
ERROR: CRHESymAccess::Load error 0x2.
Generation was aborted.
Workaround:
Create a POU before build the project.
Restoration:
Choose [Clean Project] from [Project] menu of Workbench, then the error message will not be
displayed.
l Build
Suppose, an FB (referred to as FB-B) and another FB (referred to as FB-A) that uses the FB-
B as parameters exist.

If the FB-B is deleted from the POU tree on the Resource window (it also means that the FB-
B no longer exists), but the parameters used on FB-A are not deleted, the following message
will occur when running build:
Error: A Type of variable is empty.
Under this circumstance, the FB-B parameters (including instances) used in FB-A should all
be deleted and then run build again.
Check the FB hierarchies so as to understand their relationship and then delete the FB prop-
erly.
l Initializing Arrayed Variables in ST

If initial value is set to only part of elements in an array with local variables in FU, the following
build error is raised. Specify an initial value to all the elements in the array.
Err 0059-0000:(2):,:unexpected statement
l Online Change Download Error

If you exit the Debug mode while Workbench is running and try to execute online change
download, the online change download may fail with the following error message.
ERROR:On-line change download is not executed under Debug or Simulation mode.
This error occurs if you start the Debug mode on Multi-Language Editor and immediately (be-
fore data monitoring starts on Multi-Language Editor) exit the Debug mode from Workbench.
Workaround:
After you start the Debug mode, do not exit the Debug mode until the data monitoring display
starts.
Restoration:
Exit Workbench and start it again.
l Build execution without wiring the I/O variables to the I/O module
If you execute a build without wiring the I/O variables to the I/O module, an error message like
the one shown below is displayed.
Error: Within resource "101:SCS0101": The Variable "AI001" is unwired.
If there is more than one such message, the number of errors counts as one and does not
match the number of errors that is displayed last.
SCS0101: 1 error(s), 0 warning(s)
l Precautions when opening a project and exporting PXF files

When you start the Workbench and do any of the following operations, a message "Encoun-
tered an improper argument" may appear or Workbench may close.
• Open a project
• Export a PXF file
In both cases, this phenomenon occurs at the time when a File Selection dialog box appears
and the intended operation is not executed. However, the File Selection dialog box of the
Consumer Binding List can be opened. After the File Selection dialog box is opened, this phe-
nomenon no longer occurs.
This phenomenon occurs if you have started the Print dialog box and Document Generator
before performing any of the above listed operations for the first time after Workbench is star-
ted. However, once this phenomenon has occurred, it may occur even if you do not start the
Print dialog box after the next Workbench launch.

Workaround:
Display the File Selection dialog box once before starting Document Generator.
Restoration:
Restart Workbench.
l Precautions when downloading after modifying and building in Workbench

After checking out SCS project or AD Suite data with the Version Control Tool started from AD
Organizer or restoring SCS project data or AD Suite data by using Master Database Restor-
ing Function, the following warning message appears unexpectedly when modifying, building
and downloading in Workbench.
Safety I/O List, IOM Definition or iDefine Configuration is modified. User is rec
ommended to perform ‘Build’ in Generation Manager. Do you want to continue to dow
nload?
If you click [OK] at this time, the download will take place. However, even if you start RS Gen-
eration Manager as prompted by the warning message, nothing will be displayed as modified
targets.
Workaround:
Restoration:
Using AD Organizer, make any change to the data of AD Suite, and build it in RS Generation
Manager.
n Cross Reference Analyzer

l REAL Type Constant in POU
If a REAL type constant is used in a POU, there will be a discrepancy between R2.01 and
previous versions databases. However, this discrepancy will be indicated in green on Cross
Reference Analyzer. There is no need to test it again.
However, if REAL type constant is used in an expression with (=) or (<>) comparator, the true
or false result may be different from the expected result.
If accurate comparison operation (=, <>) on REAL type is detected, Integrity Analyzer displays
a warning. In this case, you need to check the expression and make sure if the program
needs to be enhanced using "smaller than (<)" or "greater than (>)." If the expression in the
POU is correct and there is no need to modify the program, you can ignore the warning mes-
sage on Integrity Analyzer and you can download it to SCS.
l "Instruction modified" Notification

According to the technical specification, from R1.01.30, upon the following operations, the
Cross Reference Analyzer will display the “Instruction modified” notification. Thus, the POU
should be tested.
• When upgrading SENG from R1.01.00/R1.01.10 to R1.01.30 or a later revision, the "In-
struction modified" will be notified for the user-defined FU that contains local variables.
• If you switch the setting of [Generate debug information] (*1) of a POU described in LD
or ST, the message "Instruction modified" will be notified to all the POUs containing a
user-defined FU or a user-defined FB.
• When checking or un-checking the [Generate symbols monitoring information] (*2) of a
POU, the "Instruction modified" will be notified for the POU.
*1: [Generate debug information] is on the [Code Generation] tab of the POU properties sheet.
*2: [Generate symbols monitoring information] is on the [Code Generation] tab of the POU properties sheet.

n Self-Documentation
l Modifying Character Strings for the Cover Page
The character strings to be printed in the cover page of the document can only be modified in
backward-compatible mode. Use the following procedure to modify them.
1. In the Customize dialog box, deselect the checkbox of [Enhanced printing style] to select
backward-compatible mode.
2. Launch Document Generator.
3. In the [Options] tab page, click the [Edit] button in the [Header/Footer] group box to open
the Header/Footer dialog box.
4. In the Header/Footer preview of the Header/Footer dialog box, edit the second and third
lines of the title strings and click [OK].
If you do not use the backward-compatible mode any longer, close Document Generator and
select the checkbox of [Enhanced printing style] in the Customize dialog box.
n Library Project
l Debugging Library Project
While the SCS project is being debugged, if a step-in is made to the FU/FB in LD or ST de-
fined in the library project, no yellow arrow is shown to indicate where in the FU/FB in the Li-
brary project is being executed. That is, where in the Library FU/FB is being executed is not
shown, also you cannot set a breakpoint in the FU/FB defined in the library project.
Workaround:
If you want to debug FU/FB defined in the library project, open the library project using the
Workbench and change the mode to 'Simulation' before you start debugging.
n Importing and Exporting

l Put Tested Contents of User-Defined Project to Current Project
When using Test Functions, you may make a user-defined project that uses a Library project.
After testing, the tested contents need to be put into the current project.
When you put the tested contents from the user-defined project created by Test Project Creat-
ing Tool, use the following procedure to export and then import to the current project.
1. Change the target name of the user-defined project into SCS_TARGET.
2. On the user-defined project, change its library path to the path for LIBRARIES of the cur-
rent project.
3. Export the entire user-defined project.
4. Import the entire project exported in step 3 to the current project.
l Import of I/O Device Instances

When you import only I/O device instances, if the importing project contains a different type of
I/O module that having the same Device index, the definitions of that module will be overwrit-
ten. As a result, the wiring of the original I/O module in the importing project is lost. Incom-
plete wiring results in build errors; so if this problem occurred, check the I/O modules in the
source project and the importing project and make the correct definitions.
Workaround:

If the Device index value of the I/O module to be imported is already used in the importing
project and you don't want the existing I/O module to be overwritten, change (delete-and-add)
the Device index to a value that is not used in the importing project before you export the I/O
device instance.
Restoration:
If the existing module definition is overwritten with the definition of a different type of module,
the wiring is lost. In this case, delete the unwanted I/O module, re-create an I/O module you
need, and then make the necessary wiring.
n Test Project Creating Tool

l Project Path
On Test Project Creating Tool, the path for copying the project to the target project should not
contain any space character.
If the path contains any space character, an error message dialog box will be displayed when
generating the copying target project.
If the project path contains any space character, the project cannot be opened on SCS Man-
ager.
n Tag Name Builder

If the tag name of the IO_BOOL variable is defined in Tag Name Builder and the wiring of the
IO_BOOL variable is changed in SCS Manager after saving Tag Name Builder, the following
error may occur during build. (*1)
ERROR:CCmpTag::ConvertToTagData() Invalid Elem Type. ElemType 0
*1: One of the following changes applies:
• Wire from the unwired state.
• Change the wiring from FIO IOM to N-IO IOM or from N-IO IOM to FIO IOM.
This problem may occur when performing the procedure to recreate the SCS project from SIL
2 SCS to SIL 3 SCS or from SIL 3 SCS to SIL 2 SCS. In this case, perform the following re-
storation.
Workaround:
If you change the wiring of the IO_BOOL variable whose tag name is defined in Tag Name
Builder, open Tag Name Builder and save it, and then build it.
Restoration:
Open Tag Name Builder and save it again, and then rebuild it.
n Printing Function when using Windows 10 Enterprise 2019 LTSC

This precaution applies only when running SENG on Windows 10 Enterprise 2019 LTSC.
If you click the [Print] button in the SCS information dialog box, select Microsoft Print to PDF
or Microsoft XPS Document Writer as the printer name in the Print dialog box that appears,
and click the [OK] button, the SCS information dialog box will go into unresponsive state and
you will not be able to operate it.
This problem also occurs with the [Print] button in the I/O license usage dialog box that is
launched from the SCS information dialog box.
Workaround:
Select the actual printer as the printer name and print.
Restoration:
Forcibly terminate the unresponsive window and restart it.

n Precautions when Placing the SCS Project on Another PC such as a

File Server
If the SCS project is placed on a PC (server PC) such as a file server that is different from the
SENG PC (client PC) that operates the SCS project, the files in the SCS project database
(PrjLibrary.accdb) may be corrupted during SCS project operations on the client PC.
At this time, the following error dialog box appears and the SCS project cannot be used.
Figure 1.2-3 Example of the error dialog box
If you open an SCS project in this state in Workbench, you will not see an error and you will
not be able to operate it.
Workaround:
Do not access the files on the server PC from other PCs while performing the following work-
arounds on the server PC.
This workaround can be performed even if SENG is installed on the server PC.
On the server PC where the SCS project is placed, run the following files on the ProSafe-RS
installation medium with administrative rights, and restart the server PC.
(Media drive name):\ProSafe-RS\TOOLS\AddDisableLease.bat
How to stop this workaround:
On the server PC, run the following files on the ProSafe-RS installation medium with adminis-
trative rights, and restart the server PC.
(Media drive name):\ProSafe-RS\TOOLS\DelDisableLease.bat
Note:
After applying this workaround, if you use Workbench or AD Organizer on the client PC to
read or write the SCS project placed on the server PC, the processing time may take longer.
This problem affects the following operations. The processing time will be about 10 to 30%
longer than usual.
• Export and import in Workbench
• Build in Workbench
• Reflection build in AD Organizer
Restoration:
If you have not applied the above workaround and the SCS project database is corrupted, you
will not be able to open the SCS project on the Workbench. Use the Master database restor-
ing function or Version Control Tool to restore the SCS project. However, if you restore it with
Version Control Tool, and if the master database does not match the SCS database, an offline
download is required.

<1.3 AD Suite> 1-20
1.3 AD Suite
This section describes the precautions when using AD Suite.
n Software Revisions of AD Suite Included in the ProSafe-RS Software

The software revision number of AD Suite included in the ProSafe-RS software differs for
each ProSafe-RS software revision. The following table shows the AD Suite software revi-
sions corresponding to the ProSafe-RS software revisions.
Table 1.3-1 AD Suite software revisions corresponding to ProSafe-RS software revisions

ProSafe-RS software revision AD Suite software revision
R4.06.00 R1.08.00
R4.05.00 R1.07.00
R4.04.00 R1.06.00
R4.03.10 R1.05.10
R4.03.00 R1.05.00
R4.02.00 R1.04.00
R4.01.00 R1.02.00
SEE
ALSO For more information about the software revision of AD Suite included in the CENTUM VP software, refer to:
“■ Software Revisions of Automation Design Suite Included in the CENTUM VP Software” in CENTUM
VP Release Information (IM 33J01A50-01EN)
n Precautions When CENTUM VP Standard Engineering Function and

ProSafe-RS Safety System Engineering and Maintenance Function
are Installed on the Same Computer
When you install the CENTUM VP Standard Engineering Function and the ProSafe-RS Safe-
ty System Engineering and Maintenance Function, the common functions of AD Suite inclu-
ded in the software packages are also installed. If you install the CENTUM VP Standard Engi-
neering Function and the ProSafe-RS Safety System Engineering and Maintenance Function
on one computer, the common functions of the newer revision AD Suite will be installed re-
gardless of the order of installation.
If your CENTUM VP and ProSafe-RS have AD Suite of different revisions, refer to the IM of
the product with the newer revision for information about the common functions of AD Suite.
The common functions are as follows:
• ADS Administration Tool
• Dialog windows that are commonly used in AD Organizer, such as the dialog boxes for
checking out, searching, and filtering
• System Structure Navigator
• Properties window
• Check-in window
• Message window
• Revision History window
• ModPack Editor, ModPack Navigator, ModPack List window

<1.3 AD Suite> 1-21
n Precautions When Managing AD Projects of CENTUM VP and

ProSafe-RS by Using an AD Server Computer
When you manage AD projects of CENTUM VP and ProSafe-RS by using an AD Server com-
puter, the revision number of the AD Server must be identical to the revision number of the
newer AD Suite.
n Precautions When ProSafe-RS and CENTUM VP are Installed on the

Same Computer
When ProSafe-RS and CENTUM VP are installed on the same computer, if you uninstall the
product which includes the newer revision AD Suite, you will not be able to start AD Organizer
and AD Server.
Workaround:
When ProSafe-RS and CENTUM VP are installed on the same computer, do not uninstall on-
ly one of the product.
Also note that, if ProSafe-RS and CENTUM VP are installed on an AD Server computer, you
cannot separate ProSafe-RS and CENTUM VP onto different computers.
Restoration:
• If you have uninstalled one of the products in an environment where AD Organizer is in-
stalled
1. Uninstall the remaining product.
2. Install the required software.
Example:
When ProSafe-RS R4.03.10 and CENTUM VP R6.04 are installed on the same computer
and you want to have only CENTUM VP R6.04 installed, uninstall both products and then
re-install CENTUM VP R6.04.
• If you have uninstalled one of the products in an environment where only AD Server or
both AD Organizer and AD Server are installed on the same computer
Re-install the uninstalled product. Then, delete the unnecessary licenses.
Example:
When ProSafe-RS R4.03.10 and CENTUM VP R6.04 had been installed on the same
computer and you have uninstalled ProSafe-RS, re-install ProSafe-RS R4.03.10. Then,
delete the unnecessary licenses of ProSafe-RS R4.03.10.
n Format of the Path to the Project to be Registered in AD Organizer

The path to the RS project that is to be registered in AD Organizer must be specified in the
UNC (Universal Naming Convention) format. At the same time, the library project to be refer-
enced from SCS projects must also be specified with a UNC format path. If you specify the
path to the library project in the local folder format, an error will result at download.
Workaround and restoration:
Correct the path to the library project to be referenced from SCS projects into UNC format.
n Precautions When Restarting the AD Server

Before you restart your AD Server, make sure the following:
• AD Organizer is closed.

<1.3 AD Suite> 1-22
• SCS Manager and builders that are accessing the data of SCS projects registered in an
AD project are closed.
If you restart the AD Server without closing AD Organizer, SCS Manager, or builders, a con-
nection error will result on them. If this happens, restart AD Organizer, SCS Manager, or the
builder.
n Precautions when Configuring Encryption Settings for ADMDB

You can set up encryption of the ADMDB by configuring the option settings of the ADS Ad-
ministration Tool. Note the following points when you change the encryption settings:
• After you change the ADMDB encryption settings, restart the AD Server computer. En-
cryption or decryption processing runs when the computer restarts.
• Depending on the database size, it may take a long time (a few tens of minutes) for the
AD Server computer to restart.
• While the computer is restarting, you cannot perform any operation from AD Organizer. In
addition, you cannot perform operations that make changes to the data of RS projects
registered in an AD project from SCS Manager or builders.
n Precautions When Changing the Computer Name, IP Address, or

Port Number of the AD Server
If you have changed any one of the computer name, IP address, and port number of the AD
Server where RS projects are registered, start Revision History Utility from the System Struc-
ture Navigator of AD Organizer. In Revision History Utility, you do not need to do any opera-
tion. Just close it. Then, you can perform operations that make changes to project data
through SCS Manager and builders.
If you do not perform the above operation, an error will result when you try to perform opera-
tions that make changes to project data from SCS Manager. In addition, builders will start in
reference-only mode.
n Precautions About Automatic Refreshing of Windows

Some windows in AD Organizer, such as the System Structure Navigator and Check-in win-
dow, are not refreshed automatically, preventing users from confirming the result of operation
they perform. The following table shows the users who suffer this problem, operations for
which certain window is not refreshed automatically to show the result of operation, and the
windows that are not refreshed.
Table 1.3-2 Users of AD Organizer, operations, and windows that are not refreshed automatically
Window that is not refreshed
User of AD Organizer Operation
automatically
User performing the op- The following operations in the IOM Definition System Structure Navigator
eration Editor:
• Create a node or I/O module
• Delete a node or I/O module
User performing the op- Save data in individual editors Check-in window
eration
User performing the op- Add a label Revision History window
eration
Other users All operation All windows
To confirm the latest view of the windows, you must refresh the window manually. Follow ei-
ther of these steps to refresh the window manually:
• From the menu bar of AD Organizer, select [View] > [Refresh].

<1.3 AD Suite> 1-23
• Press the [F5] key.
n Precautions When Editing Files by Using AD Organizer

In AD Organizer, checked out files are editable only on the computer where they were
checked out. Even the user who checked out the file cannot edit the file on different comput-
ers. This means that if the user who checked out a file logs on to a different computer and try
to edit the file, it is regarded that the file is already checked out by other user.
If the computer where the file was checked out fails, for example, and so the checked-out sta-
tus of files must be canceled, use the ADS Administration Tool to forcibly cancel the checked-
out status of the files. When you cancel the status, the data that was being edited on the origi-
nal computer is lost.
n Precautions When Entering I/O Information in the Safety I/O Editor

In the Safety I/O Editor of AD Organizer, if you copy an entire row of the safety I/O list and
paste it to other row, the data in the Area column and P&ID Sheet column is not reflected in
the destination cells. In such a case, select the entire row and paste it again. This time, the
data is also copied to the Area column and P&ID Sheet column.
n Precautions When Adding Rows

In the table format editors of AD Organizer, you cannot add rows while the sorting function is
applied. You must unsort the table and then add rows.
While the sorted result is displayed, a small ▲ or ▼ is displayed in the column heading. With
each click on a column heading, the column contents are sorted in ascending order (▲), de-
scending order (▼), and then unsorted.
n Precaution about Data Entry

If an invalid value is entered, the entry area is displayed in red. In this state, you cannot close
the editor or AD Organizer.
Workaround:
None.
Restoration:
Revert the entered value of the error cell to the original value by pressing the [ESC] key, and
then close the editor or AD Organizer.
n Precautions When Running Reflection in RS Generation Manager

If the software revision of ProSafe-RS that was used when creating the SCS project is older
than the current revision in use, the setting items related to the features that were added after
the software revision used to create the SCS project will be ignored when you run Reflection
and will not be reflected.
Example when the ProSafe-RS software revision is R4.03.00
When you run Reflection for an SCS project that was created in R4.01.00, the following items,
which have been added in R4.03.00 software, will not be reflected:
• I/O Parameter
IOM Definition: Device Reset Function
Safety I/O: Device OFF-ON Variable Name, Reset Group ID, Time to Chattering Recov-
ery Notice(s)
• Tag Name: Time to Chattering Recovery Notice(s)

<1.3 AD Suite> 1-24
• IOM: S2MDV843 (Digital Input Output Module (16-channel, Module Isolation))
• FB: HSDTR, GASDTR
You can check the revision number of the SCS database in the Properties window of AD Or-
ganizer.
Workaround and restoration:
None.
SEE
ALSO For more information about how to check the revision number of an SCS database, refer to:
B3.1.2, “Properties window” in Engineer's Reference Manual (IM 32P04B10-01EN)
n Notes on runtime errors when running Reflection

When you run Reflection in RS Generation Manager for an SCS project that has a project
password, a dialog box may be displayed indicating a runtime error.
Runtime error '3031': Invalid password.
If you click [OK], the result of reflection is displayed as success, but it has actually failed. This
causes the build to fail.
Workaround:
Restoration:
Restart RS Generation Manager to run Reflection. If the error dialog box appears again, re-
peat the operation until the error dialog box no longer appears.
n Notes on the Safety I/O Editor when the name of Safety I/O
parameter profile was changed
The following phenomena occur if the safety I/O definition refers to the Safety I/O parameter
profile.
In a case of changing the name of referred Safety I/O parameter profile, if you specify the his-
tory or a label which is before the change of the name and start the Safety I/O Editor, the
name after the change is displayed in the I/O Parameter Profile column.
If the Safety I/O parameter profile was deleted, the internal ID (for example:
4EE3C611-903E-400D-903F-A82CC2A347A1) is displayed in the I/O Parameter Profile col-
umn.
In both cases, the parameter values that were specified in the Safety I/O parameter profile be-
fore it was changed or deleted are properly displayed.
Workaround:
None.
Restoration:
None.

<1.4 SCS Maintenance Support Tool > 1-25
1.4 SCS Maintenance Support Tool

This section explains cautionary notes on using SCS Maintenance Support Tool.
n SCS System Report Display

The following are limitations on the information displayed in the SCS Report that is called up
from the SCS State Management window.
SCSP1:
• In dual-redundant operation, no information is displayed for [VEHICLE Revision] of the
standby-side CPU module ("..." is displayed). You can find out the revision from the indi-
cation of "F2" on the label on the CPU module.
• When the standby-side CPU module is not in the standby state (stopped or APC is run-
ning), information on the standby-side CPU module is not displayed.
SCSP2, SCSP3, SCSL2:
No limitations
n Printing function when using Windows 10 Enterprise 2019 LTSC

This precaution applies only when running SENG on Windows 10 Enterprise 2019 LTSC.
If you click the [Print] button in the SCS Report dialog box on the SCS State Management
window, select Microsoft Print to PDF or Microsoft XPS Document Writer as the printer name
in the Print dialog box that appears, and click the [OK] button, the SCS State Management
window will go into unresponsive state and you will not be able to operate it.
This problem also occurs with the following functions:
• [Print] button on the Report dialog box displayed by clicking the [Report] button on the I/O
Channel Status dialog box on the SCS State Management window
• [Print] button on the preview screen switched by selecting the [Print preview] from the
menu bar in the Diagnostic Information window
• [Print] in the menu bar and the [Print] button on the toolbar in the Diagnostic Information
window
Workaround:
Save it to a file once, and output it to Microsoft Print to PDF or Microsoft XPS Document Writ-
er with the print function of another application such as Notepad.
Follow these steps to save to a file:
• For the SCS Report dialog box and the Report dialog box that is appeared from the I/O
Channel Status dialog box, click the [File] button to output it to a text file.
• For the Diagnostic Information window, select [Save to file] from the menu bar to output to
a CSV file.
Restoration:
Forcibly terminate the unresponsive window and restart it.

<1.5 Integration with CENTUM > 1-26
1.5 Integration with CENTUM

In this section, cautions on Integration with CENTUM are explained.
n Accessing the SCS Global Switch Communication Data Received by

FCS on HIS
The FCS application can handle the SCS global switch communication data sent from SCS
as %GS, but the %GS data received by FCS cannot be accessed on HIS.
If you need to confirm the %GS data on HIS, check its source data, SCS global switch com-
munication data.
If you want to access data received by FCS on HIS, change the data to another element such
as %SW using the FCS application. Or connect to the switch instrument block and access the
data on it.
The behavior when the %GS of FCS corresponding to the SCS global switch communication
data is accessed on HIS is as follows:
• If you try to call the %GS from the NAME Input dialog box or Graphic windows and so on,
an error message appears and its faceplate is not shown.
• %GS cannot be used for accessing process data.
• %GS cannot be used for accessing process data through OPC.
• If you use the %GS in a sequence table, FCS processes it correctly. However you dou-
ble-click the tag name in the Sequence Table View on HIS, neither error message nor
faceplate for the tag name is shown.
SEE
ALSO For more information about how to confirm the SCS global switch communication data on HIS, refer to:
“■ Software inputs/outputs” in B1., “Overview of CENTUM integration” in Engineering Guide Vol. 2 (IM
32P01C20-01EN)
n SCS System Report Display

The following are limitations on the SCS Report that is displayed on a CENTUM HIS.
SCSP1:
• In dual-redundant operation, no information is displayed for VEHICLE Revision of the
standby-side CPU module ("..." is displayed). You can find out the revision from the indi-
cation of "F2" on the label on the CPU module.
• When the standby-side CPU module is not in the standby state (stopped or APC is run-
ning), information on the standby-side CPU module is not displayed.
SCSP2, SCSP3, SCSL2:
No limitations

<1.6 SOE (Sequence of Events) > 1-27
1.6 SOE (Sequence of Events)

In this section, notes on SOE usage are explained.
n SOE OPC Interface Package

l Setting IT Security
Ensure to execute the IT security tool from the start menu after you activate a license for the
SOE OPC interface package.
l When Microsoft Visual Studio is Used

If the SOE OPC Interface Package is installed on a PC where the Microsoft Visual Studio is
already installed, a dialog box with the following message may appear when the PC is shut
down. This dialog box may also appear after installing ProSafe-RS to the same PC.
"ZOPHDA.exe Application Error The instruction at XXXX referenced memory at XXXX."
Workaround:
The SOE OPC Interface package should not be installed to the PC where the Microsoft Visual
Studio is installed.
Restoration:
Click the [OK] button on the message dialog box.
l Note on PRM Client

PRM client and SOE OPC Interface Package software must be installed separately on differ-
ent PCs. If they are installed on the same PC, the SOE OPC server function will stop.
l Note on Virtualization Platform Environment

In the virtualization platform environment, a setup tool for OPC client cannot be created be-
cause RHHCopyOPC.exe does not operate properly. For that reason, connection with OPC
clients that require the setup tool is not available. Connection with Exaquantum is available
because Exaquantum does not use a setup tool.
Workaround: None.
Restoration: None.

<1.7 Access Control and Operation History Management Package > 1-28
1.7 Access Control and Operation History

Management Package
n Browsing Modification Files
When you start operation history management without upgrading the revision of SCS project
which has been created in a SENG running R2.01 or below, you can not browse modification
files of POUs in the operation history database.
Workaround:
If an SCS project is created in a SENG running R2.01 or below, you need to upgrade revision
of project data before you start operation history management.
Restoration:
Perform the following steps to restore.
1. Stop operation history management.
2. Delete the affected modification file database in the operation history database.
3. Open the SCS project on SCS Manager to upgrade the revision.
4. Start operation history management.
n Operation Logging
l Operation Logs of IOM Download Operations
For IOM download operations, the strings shown in the message display area are not recor-
ded in the log file.
Workaround:
For the details of the results of operation, refer to the corresponding diagnostic information
messages.
You can use SOE Viewer to check the diagnostic information generated in the past.
If SOE Viewer is not available, you can use the Diagnostic Information window to save the
diagnostic information in a file.
Restoration:
n Modification Files Viewer

When Resource Content data containing POU overview information is displayed, numbers to
indicate the execution order of Programs are not indicated. Therefore, you cannot tell whether
the order of Program execution is different even though you perform difference detection be-
tween two Resource Contents.
Workaround:
When Resource Content data is displayed not in the difference display mode, Programs are
shown in the order of execution. Confirm the execution order from the displayed order.
Restoration:

<1.7 Access Control and Operation History Management Package > 1-29
n Precautions When Changing the Password of an Engineer

If you try to change the password of an engineer when the access control function is used
and all of the following conditions are met, a message "Ask the administrator to access a
password file" appears, preventing you from changing the password.
• ProSafe authentication mode is used.
• The engineers' account file is placed in a folder under the folder with a share name RS-
Share on a remote PC.
• After the Standard model or Strengthened model is set with the IT Security Tool, the [OK]
or [Apply] button is not clicked in the Operation History Management Settings Tool.
Workaround:
After you have set or changed to the Standard model or Strengthened model with the IT Se-
curity Tool, ask the system administrator to open the Operation History Management Settings
Tool and click the [OK] or [Apply] button.
Restoration:
Ask the system administrator to open the Operation History Management Settings Tool and
click the [OK] or [Apply] button.

<1.8 Installation > 1-30
1.8 Installation
Notes on installation are explained as follows.
n Installation of ProSafe-RS Software Package

In ProSafe-RS system, Remote Desktop is prohibited to connect with a PC where the
ProSafe-RS software package is to be installed except for connections from thin client in virtu-
alization platform.
n Notes on Display of Program Icons in the Start Menu of Windows 10

If a user who does not have access rights to ProSafe-RS related programs expands the
ProSafe-RS folder in the Start menu, the program icons will not be displayed properly. After a
user without access rights to ProSafe-RS related programs expanded the folder, the Start
menu program icons will not be displayed properly even if a user with access rights to
ProSafe-RS related programs expands the folder.
Workaround:
• Users who do not have access rights to the ProSafe-RS related programs (users not a
member of PSF_XXXXXX group) must not expand the ProSafe-RS folder in the Start
menu.
• After a user is created, the user should begin to use ProSafe-RS after being added to a
PSF_XXXXX group.
Restoration:
1. Sign in as a user with administrative rights.
2. Open the Command Prompt.
3. Use the cd command to move to the target folder.
>cd C:\ProgramData\Microsoft\Windows\Start Menu\Program\ProSafe-RS
4. Run the following command.

>COPY /B * +,,
The time stamp of the shortcut to the program icon in the current directory is updated.
5. In the same manner, perform steps 3 and 4 for ProSafe-RS Maintenance, YOKOGAWA
AD Suite, and other folders for which restoration is required.
n Precautions for Start Menu Operation in Windows 10

Users who satisfy both of the following conditions may not be able to select the ProSafe-RS
menu items that appear in the Start menu of Windows 10.
• A user who had already signed in before ProSafe-RS was installed
• A user who is not the Install User of ProSafe-RS
Restoration:
Sign out and then sign in again.
n Precautions for Effect on Start Menu Caused by SOE OPC Interface

Package
If all of the following conditions are met, Start menu may not appear when you click on the
Start menu after the license of SOE OPC interface package is distributed.
• OS is Windows Server 2016 or Windows 10.

<1.8 Installation > 1-31
• Microsoft update programs released in January 2018 or later are applied.
Follow these precautions only when Default Authentication Level of DCOM can be operated
with [Connect] in a license-assigned station of SOE OPC interface package. If Legacy model
is selected or a station needs to be operated with [None] for Default Authentication Level of
DCOM due to other reasons, do not follow these precautions and do not apply the applicable
Microsoft update programs.
Workaround:
Follow either of these steps:
• Not to apply applicable Microsoft update programs.
• Apply applicable Microsoft update programs after the setup of SOE OPC interface pack-
age is completed.
Restoration:
Set Default Authentication Level of DCOM to [Connect] and then start IT Security Tool.
SEE
ALSO For more information about how to set the Default Authentication Level of DCOM to Connect, refer to:
“■ DCOM Settings” in B3.2.2, “Setting of Items Specific to Windows 10” in Installation Guide (IM
32P01C50-01EN)

<1.9 Security > 1-32
1.9 Security
Notes on securities are explained as follows.
n Notes on Selecting Standard Model of IT Security Settings

When standard model of IT security settings is selected, if the NetBIOS is not used, the name
of the computer where the ProSafe-RS project is located needs to be indicated by DNS or de-
scribed in LMHOSTS file for name solution.
LMHOSTS file can be found in the following path: %Systemroot%\system32\drivers\etc
%Systemroot% is the directory where the Windows operating system files are installed. If the
system drive is drive C, the path to the file is
C:\Windows\system32\drivers\etc
An example script in the LMHOSTS file is as follows, Assuming that the IP address of
STN0164 is 172.17.1.64.
########## lmhosts
172.17.1.64 STN0164 # PRE
n Precautions for Using Legacy Model in Windows 10 or Windows

Server 2016
If Legacy model is used for the security model in Windows 10 or Windows Server 2016, you
can apply Windows update programs released in December 2017 or earlier.
Do not apply Windows update programs released in January 2018 or later because the speci-
fication changes made by Windows update programs cause problems related to Windows op-
erations. As the result, response is not available for security concerns that are supposed to be
fixed by Windows update programs released in January 2018 or later. Also, response is not
available for issues such as modification of functions related to OS.
If Standard model is used for security model, this problem does not occur.
n Domain User Name and Password Entry when Restoring Security

Settings by IT Security Tool
If you log on to a PC connected in a domain as a local user and try to run the IT Security Tool
to restore the settings of standalone environment, the tool requires to enter a domain user
name and password despite that user management is standalone type. If required, enter the
domain user name and password.
n Cautions when Restoring IT Security Settings

When you use IT Security Tool to restore the IT security settings in a file that was saved on a
domain controller, the security settings cannot be restored as you expect if the user/group in-
formation at the time of restoration differs from that when the security settings were saved.
This applies to the cases, for example, where any of the following changes have been made
after the saving of IT security settings:
• Delete a user or group.
• Delete a user or group and create it again.
• Change the group to which a user belongs.
If you run the restoration in a situation different from that when the security settings were
saved, the security settings will be as shown below. Modify the IT security settings as neces-
sary.

• When groups existed at the time of saving exist on the current domain controller
The information on user assignments to the groups at the time of saving is added to the
user assignment information existing in the domain controller. You need to modify the IT
security settings so that the assignments of users to groups are consistent with the cur-
rent situation.
• When groups existed at the time of saving do not exist on the current domain controller
The groups existed at the time of saving is restored as local groups of the domain. The
local groups have no effect on system operations, but delete them if necessary.
• When users existed at the time of saving exist on the current domain controller
The information on user assignments to groups at the time of saving is added to the user
assignment information existing in the domain controller. You need to modify the IT secur-
ity settings so that the assignments of users to groups are consistent with the current sit-
uation.
• When users existed at the time of saving do not exist on the current domain controller
An error occurs. Even if the error has occurred, the IT security setting items other than
those related to users and groups are restored correctly.
n Precautions When Changing the User Management Type on a File

Server
If you change the user management type that is set by the IT Security Tool on a file server,
the existing users may remain members of groups that are invalid with the user management
type after change. The users who belong to an invalid group cannot access the share folder
on the file server.
Restoration:
For example, if both PSF_MAINTENANCE and PSF_MAINTENANCE_LCL groups exist on
the file server, follow these steps to delete the invalid groups and unnecessary users:
1. Open the Command Prompt as a user with administrative rights.
2. Insert the ProSafe-RS software medium into the drive.
3. According to the user management type that is applied, run the batch file in the software
medium.
• For Standalone management
<DVD drive>:\ProSafe-RS\TOOLS\SECURITY-SEC-0059_STA.bat
• For Domain management or Combination management
<DVD drive>:\ProSafe-RS\TOOLS\SECURITY-SEC-0059_DOM_CMB.bat
The users belonging to invalid groups are moved to valid groups, and the invalid groups
are deleted.
4. If there are any members of the valid groups who do not need to have the rights granted
to the group, delete them.
TIP Users will be moved between the groups in the following combinations:
• PSF_OPERATOR and PSF_OPERATOR_LCL
• PSF_ENGINEER and PSF_ENGINEER_LCL
• PSF_OPC and PSF_OPC_LCL
• PSF_MAINTENANCE and PSF_MAINTENANCE_LCL

n IT Security Precautions when PRM R4.04.00 is Installed on the Same

Computer
This is a precaution for problems that occur when ProSafe-RS and PRM R4.04.00 are instal-
led on the same computer.
Occurrence conditions:
This problem occurs when the following conditions are met:
• ProSafe-RS and PRM R4.04.00 are installed on the same computer.
• Used in the following security model and user management combinations:
• Security model: Standard Model or Strengthened Model
• User management: Standalone management or Linked domain management
The following events may occur if the conditions are met.
l A warning that it is different from the recommended value appears

When setting security in the IT Security Tool, even though it is as recommended, you may get
a warning that says the setting value of "Disabling NetBIOS over TCP/IP" is different from the
recommended value. Ignore the warning. There is no problem with the security settings.
Workaround:
None
Restoration:
Ignore the warning. There is no problem with the security settings.
l Unknown setting items are displayed on IT Security Tool

"Unlinked equal unselect 1" or "linked partlinked equal unselect 0" may be displayed on the
selection window of the setting item of the IT Security Tool. These setting items appear near
the top or bottom of the list.
If it is displayed, follow the procedure described in the workaround and the restoration respec-
tively.
Workaround:
Open the selection window of the setting item of the IT Security Tool, check the selection
state of the "Disabling NetBIOS over TCP/IP" check box, and change it to the value you want
to set. If you want to use the recommended values, see the following "Recommended value
for check box selection.”
Next, select/clear the check box of "unlinked equal unselect 1" or "linked partlinked equal un-
select 0" in the same setting as "Disabling NetBIOS over TCP/IP.”
Recommended value for check box selection:
• Standard Model-Standalone management: Clear
• Standard Model-Linked domain management: Select
• Strengthened Model: Select
If you did not take the above actions during the security settings, take the actions after the
security settings.
Restoration:
Same as the workaround.

<1.10 License Management > 1-35
1.10 License Management

Notes on license management are explained as follows.
n Tasks Required After the Station Configuration of a License Project

is Changed
If you have changed the station configuration of a license project, excluding the changes rela-
ted to FCS and SCS, perform the tasks shown in the following table. Note that changing the
station configuration refers to addition and deletion of stations and renaming of computers.
Table 1.10-1 Tasks Required After the Station Configuration of a License Project is Changed
Change in station con- Task
figuration
Add a station Distribute and accept licenses on the added station. Then, distribute master li-
censes to the other stations.
Then, distribute master licenses to the other stations.(*1)
Delete a station After deleting a station, distribute master licenses to all stations.(*1)
Rename a computer Distribute and accept the licenses on the station you have changed the comput-
er name.
Then, distribute master licenses to the other stations.(*1)
*1: Destinations of license distribution are PC-based stations such as HIS, PCs installed with system builders, APCS, GSGW,
SIOS, and UGS; FCS and SCS are not included. Distributing a master license does not require license acceptance on the
destination station or restarting of the destination station. Master license distribution is basically used to redistribute the li-
cense information that is already distributed to specified stations; however, only the station configuration is updated here.

<1.11 Vnet/IP Interface Package> 1-36
1.11 Vnet/IP Interface Package

Notes on Vnet/IP Interface Package are explained as follows.
n Network time after virtual machine shutdown/recovery

Virtualization platforms allow server administrators to temporarily stop and recover virtual ma-
chines.
If the virtual machine is recovered after a period of outage (*1), the time of the virtual ma-
chine that was down may be set as the network time. As a result, the network time can be-
come unstable for a certain period of time.
Due to the instability, the time of functions using timestamps such as SOE is not displayed
correctly.
*1: Shutdown and recovery occur in the following cases:
1. Live migration is performed.

2. Used beyond the capabilities of the system.
Hard disk of the host is lacking free space.
3. Prohibitions stated in the user's manual are done.
4. Special failure (multiple) occurs.
About live migration
The amount of time required for live migration depends on the applications running on the vir-
tual machine and the operational state. Since outages are short, this problem does not occur
for most applications.
Workaround:
Restoration:
No action is required because the network time automatically recovers to the correct time af-
ter 10 seconds.

<1.12 Miscellaneous > 1-37
1.12 Miscellaneous
In this section, additional notes are explained.
n Printing the Workbench User's Guide

In the Workbench User's Guide, if you select [Print the selected heading and all subtopics] in
the Print Topics dialog box to print multiple topics, some figures may not be printed correctly
in rare cases.
Workaround:
Restoration:
From the tree in the left pane, select the topics containing the figures that were not printed
correctly, and then select [Print the selected topic] in the Print Topics dialog box to print them
individually.
n Pressure Clamp Terminal Block for Analog Signals, Dual-Redundant

Use
For the 'SAI143-H Analog input module with HART communication' that was newly supported
in the software revision R1.02.00, do not use the style 1 (S1) of the following 'Pressure clamp
terminal blocks for analog signals, dual-redundant use' ("S1" is appended to their model name
printed in the lower left corner of their surface):
• STA4D-00 S1 (Pressure clamp terminal block for analog signals, dual-redundant use
(without surge absorber))
• STA4D-10 S1 (Pressure clamp terminal block for analog signals, dual-redundant use
(with surge absorber))

Rev-1
Revision information
Title : ProSafe-RS Release Information
Manual No. : IM 32P01A50-01EN
Feb. 2021/7th Edition/R4.06 or later
1.1 Added IOM for SIL 2.
1.1, 1.4, 1.5 Added SCS for SIL 2.
1.2 Added “■ Tag Name Builder”, “■ Printing Function when using Windows 10 Enter-
prise 2019 LTSC”, and “■ Precautions when Placing the SCS Project on Another
PC such as a File Server.”
1.3 Deleted "■ Refreshing of the Check-in Window of AD Organizer”, and added de-
scription about R4.06.00 to “■ Software Revisions of AD Suite Included in the
ProSafe-RS Software.”
1.4 Deleted “■ Dialog box size reduction for Forced I/O Viewer and Forced I/O Viewer
Setup Tool”, and added “■ Printing Function when using Windows 10 Enterprise
2019 LTSC.”
1.9 Deleted “■ Precautions About the Users Who Configure IT Security Settings on a
File Server or Domain Controller”, and added “■ IT Security Precautions when
PRM R4.04.00 is Installed on the Same Computer.”
Dec. 2019/6th Edition/R4.05
Introduction Updated description of registered trademarks and trademarks.
1.1 Added “■ Operation of Fire and Gas Communication Module S2LP131 when port
state changes: SCSP3” and “■ Fire and gas communication system start-up oper-
ation: SCSP3.”
1.2 Deleted “● Show Details of POU.” Added “● Build execution without wiring the I/O
variables to the I/O module,” “● Precautions when opening a project and exporting
PXF files,” and “● Precautions when downloading after modifying and building in
Workbench.”
1.3 Added R4.05.00 to “■ Software Revisions of AD Suite Included in the ProSafe-RS
Software.” Added “■ Notes on runtime errors when running Reflection.” Added “■
Notes on the Safety I/O Editor when the name of Safety I/O parameter profile was
changed.”
1.4 Added “■ Dialog box size reduction for Forced I/O Viewer and Forced I/O Viewer
Setup Tool.”
1.11 Added as a section on Vnet/IP Interface Package.
1.12 Deleted “■ Workbench User's Guide” and added “■ Printing the Workbench User's
Guide.”
Aug. 2018/5th Edition/R4.04
Introduction Updated description of registered trademarks of YOKOGAWA.
1.2 Added “● Show Details of POU.”
1.3 Deleted “■ Variable Group” and added description about R4.04.00 to “■ Software
Revisions of AD Suite Included in the ProSafe-RS Software.”
1.6 Added “● Note on Virtualization Platform Environment.”
1.8 Deleted “● Precautions regarding Installation of Redistributable Modules on Win-
dows 10,” changed description in “● Installation of ProSafe-RS Software Pack-
age,” and added “■ Precautions for Effect on Start Menu Caused by SOE OPC In-
terface Package” and “■ Coexistence with PRM.”

Rev-2
1.9 Deleted “● Precautions When CENTUM VP R6.02 Is Installed on the Same Com-
puter” and added “■ Precautions for Using Legacy Model in Windows 10 or Win-
dows Server 2016.”
1.10 Deleted “● Notes on Status Display on License Manager.”
1.11 Added “■ Workbench User's Guide.”
Oct. 2017/4th Edition/R4.03.10
1.1 Deleted “■ Precautions When Using SCS Simulator in a Plant Training System.”
1.3 Added R4.03.10 to “■ Software Revisions of AD Suite Included in the ProSafe-RS
Software.” Added “■ Precautions When ProSafe-RS and CENTUM VP are Instal-
led on the Same Computer.”
1.8 Added “■ Precautions regarding Installation of Redistributable Modules on Win-
dows 10.”
May 2017/3rd Edition/R4.03
Entire manual Updated descriptions of the Start menu.
Introduction Deleted Windows Vista from “■ Trademark Acknowledgments.”
1.1 Added “■ Precautions When Using SCS Simulator in a Plant Training System.”
1.2 Deleted "● Comparing with an Imported Project" and "● When an Entire Project is
Imported to the Same Project or a Project is Updated After Being Edited with
iDefine.”
1.3 Deleted “■ Precautions when Starting AD Organizer.” Added "■ Software Revi-
sions of AD Suite That is Included in the ProSafe-RS Software," "■ Precautions
When CENTUM VP Standard Engineering Function and ProSafe-RS Safety Sys-
tem Engineering and Maintenance Function are Installed on the Same Computer,"
and "■ Precautions When Managing AD Projects of CENTUM VP and ProSafe-RS
by Using an AD Server Computer” and “■ Precautions When Running Reflection
in Generation Manager.”
1.8 Added "■ Notes on Display of Program Icons in the Start Menu of Windows 10,” “■
Precautions for Start Menu Operation in Windows 10,” “■ Precautions When
Changing the User Management Type on a File Server," "■ Precautions About the
Users Who Configure IT Security Settings on a File Server or Domain Controller,"
and "■ Precautions When CENTUM VP R6.02 Is Installed on the Same Comput-
er.”
Oct. 2016/2nd Edition/R4.02
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."
1.1 Deleted "■ Precautions When Changing the Tight-Shut Related Parameters for
AO Channels of S2MMM843" and "■ Behavior at event acquisition request on
DNP3 slave function: SCSU1".
1.2 Updated descriptions in "● Comparing with an Imported Project" and "● Online
Change the Definition of Bindings for the Inter-SCS Safety Communication." Add-
ed "● When an Entire Project is Imported to the Same Project or a Project is Up-
dated After Being Edited with iDefine."
1.3 Deleted "■ Precautions about Project Comparing Tool." Added "■ Refreshing of
the Check-in Window of AD Organizer."
1.9 Deleted "User's Manuals."
Dec. 2015/1st Edition/R4.01
Newly published

Rev-3
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

Im32p01a50 01en

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Im32p01a50 01en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Im32p01a50 01en

Uploaded by

Copyright:

Available Formats

User's ProSafe-RS

Manual ProSafe-RS Lite

7th Edition : Feb. 2021 (YK) IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

Safety Precautions for Use

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

Indicates that a component such as a power supply switch is turned OFF.

n Notes on Handling User's Manuals

n Warning and Disclaimer

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

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

IMPORTANT Indicates important information required to understand operations or

Indicates referenced content.

l Commonly Used Conventions throughout the User's Manuals

l Conventions Used to Show Key or Button Operations

l Conventions of a User-defined Folder

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

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

n Definitions of Node and Module Terms

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Full Names and Simplified Terms

Table Info-1 Full Names and Simplified Terms

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

Copyright and Trademark Notices

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

ProSafe-RS Release Information

IM 32P01A50-01EN 7th Edition

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

1. Usage Notes for R4.06

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

1.1 Safety Control Stations

n Behavior of SDV526/L1DV526 (100-120 VAC DO Module) in Dual-

n Cautions on Input Signals to DI Channels

n Cautions on Replacing SAI143/L1A143 (AI Module)

n Lock Status at Online Change of I/O Modules

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Deleting-and-Adding an I/O Module

n Values under Forcing when Single/Dual-redundant Specification of

n Adding Communication Modules by Online Change Download

A731: Simultaneous downloading of different types of communication programs was a

Table 1.1-1 Types of communication and communication modules

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Online Change Download of SCS Constants Builder Definitions

n Configuration Errors Immediately after Offline Download

n Configuration Errors after Online Download to Universal Type I/O

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Execution of Automatic IOM Download

n Breakpoint Usage in Target Tests

l Control Right Switching

l APC Does Not End

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Messages Output upon Control Right Switching of Dual-redundant

n Messages Output when Standby-side CPU Module is Inserted:

n Behavior at Start Up of an SCS: SCSP2, SCSP3, SCSL2

n Note on the Use of Communication Module for Modbus Slave

IM 32P01A50-01EN 7th Edition : Feb.24,2021-00

n Replacement of CPU Module in Stand-alone SCS Configuration

n Notice on Supplying Power to One of a Pair of Power Modules of a