S03B1021
S03B1021
S03B1021
Manual
Safety Control
Station Reference
IM 32S03B10-21E
IM 32S03B10-21E
3rd Edition
Introduction
Safety Control Station (SCS) is a station for safety control. The SCS monitors the plant safety
status, and carries out safety controls according to various safety demands.
Provided as a reference to be checked for the necessary information when needed, this
document explains the SCS configuration, safety control, the functions and function blocks that
comprise the application logics for safety control, and the external communication function of
the SCS, such as the integration structure with CENTUM VP or CENTUM CS 3000 (hereinafter
referred to as CENTUM). The SCS engineering or maintenance personnel should well
understand the contents of this document.
Media No. IM 32S03B10-21E (CD) 3rd Edition : Dec. 2009 (YK) IM 32S03B10-21E 3rd Edition : Dec.22,2009-00
All Rights Reserved Copyright 2008, Yokogawa Electric Corporation
ii
Engineering
Safety Manual
Guide
IM 32S01S10-21E IM 32S01C10-21E
Software
ProSafe-RS
Integration with
System Test
FAST/TOOLS Workbench Users Guide
Reference
IM 32S04B30-21E IM 32S56H20-21E
Hardware Vnet/IP
Safety Control
Communication ProSafe-RS
Stations
Devices Vnet/IP
(Hardware)
IM 32S06C10-21E IM 32S06H10-21E IM 32S56H10-21E
Installation
Installation Manual
Software Help
IM 32S01C50-21E
Read Me First
Safety Precautions
n Safety, Protection, and Modification of the Product
In order to protect system controlled by this product, the product itself and ensure safe
operation, observe the safety precautions described in this users manual. We assume no
liability for safety if users fail to observe these instructions when operating the product.
You must use this product according to the instructions described in user manuals. If not,
protective functions of this product may not work as expected.
If any protection or safety circuit is required for system controlled by the product or for the
product itself, prepare it separately.
Be sure to use the parts approved by Yokogawa Electric Corporation (hereafter simply
referred to as YOKOGAWA) when replacing parts or consumables.
Modification of the product is strictly prohibited.
The following symbols are used on the product and in this user manual to indicate that
safety precautions are required:
Indicates that user must take caution. The symbol on the equipment refers the user to the
relevant manual to avoid potentially hazardous situations that may result in injury or death.
The symbol appears next to the cautionary information in user manuals required to avoid
harm to personnel and to the equipment.
Indicates a protective grounding terminal. Before using the product, ground the terminal.
Indicates a functional grounding terminal. Before using the product, ground the terminal.
Indicates an AC supply.
Indicates a DC supply.
n Notes on Software
YOKOGAWA makes no warranties, either expressed or implied, with respect to the
softwares merchantability or suitability for any particular purpose, except as specified in the
terms of warranty.
This software may be used on one machine only. If you need to use the software on another
machine, you must purchase another copy of the software.
It is strictly prohibited to reproduce the product except for the purpose of backup.
Store the CD-ROM (the original medium) in a safe place.
It is strictly prohibited to perform any reverse-engineering operation, such as reverse
compilation or reverse assembling on the product.
No part of the product may be transferred, converted or sublet for use by any third party,
without prior written consent from YOKOGAWA.
Documentation Conventions
n Typographical Conventions
The following typographical conventions are used throughout the user manuals:
Mark:
Indicates a space between character strings that must be entered.
Example: Calling the tuning view with the tag name of S0001 on HIS (Human Interface Station of
the integrated CENTUM).
S0001TUN
n Symbol Marks
Throughout this user manual, you will find that several types of symbols are used to identify
different sections of text. This section describes these icons.
CAUTION:
Indicates instructions that must be observed in order to prevent physical injury and death of
operator.
WARNING :
Indicates instructions that must be observed in order to prevent software or hardware from
being damaged or system from becoming faulty.
IMPORTANT :
Indicates important information required to understand operations or functions.
TIP:
Indicates additional information.
SEE :
ALSO
n Drawing Conventions
Some drawings in the user manual may be partially emphasized, simplified, or omitted, for the
convenience of description.
Note that screen images in user manuals may be slightly different from the actual ones (for
example, display positions and case differences), and some show only example images.
SEE
ALSO For information about the functions and usage of CENTUM VP components, see CENTUM VP Users
Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
For information about the functions and usage of CENTUM CS 3000 components, see CENTUM CS 3000
Users Manuals (IM) and related Technical Information (TI) and General Specifications (GS).
n Trademark Acknowledgments
CENTUM, ProSafe, Vnet/IP and STARDOM are registered trademarks of YOKOGAWA.
Microsoft, Windows, Windows Vista, Visual Basic, Visual C++ and Visual Studio are either
registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
Adobe, Acrobat and Acrobat Reader are either registered trademarks or trademarks of
Adobe Systems Incorporated in the United States and/or other countries.
Ethernet is a registered trademark of XEROX Corporation.
Modicon and Modbus are registered trademarks of Schneider Electric SA.
PLC is a registered trademark of Rockwell Automation, Inc.
HART is a registered trademark of the HART Communication Foundation.
All other company and product names mentioned in this users manual are trademarks or
registered trademarks of their respective companies.
We do not use TM or mark to indicate those trademarks or registered trademarks used in
this users manual.
ProSafe-RS
Safety Control Station Reference
IM 32S03B10-21E 3rd Edition
CONTENTS
PART A SCS Common
A1. Overview of SCS......................................................................................A1-1
A2. SCS Hardware..........................................................................................A2-1
A3. Scan Period and Time Synchronization of SCS..................................A3-1
A3.1. Scan Period of SCS......................................................................................... A3-1
A3.1.1 Definition of SCS Scan Period..........................................................A3-2
A3.1.2 Automatic Extension Function for Scan Period of the
Application Logic Execution Function . ............................................A3-4
A3.1.3 Online Change of Scan Period of the Application
Logic Execution Function . ...............................................................A3-9
A3.2 Time Synchronization of SCS...................................................................... A3-10
A4. Process Data Inputs and Outputs.........................................................A4-1
A4.1 Flow of Process Data Inputs and Outputs................................................... A4-1
A4.2 Input and Output Variables............................................................................ A4-4
A4.3 Common Setting Items for Process Data Inputs and Outputs................ A4-10
A4.4 Items Set for Analog Inputs......................................................................... A4-14
A4.5 Items Set for Analog Outputs...................................................................... A4-23
A4.6 Items Set for Discrete Inputs....................................................................... A4-29
A4.7 Items Set for Discrete Outputs.................................................................... A4-34
A5. Inter-SCS Safety Communication.........................................................A5-1
A6. SCS Link Transmission..........................................................................A6-1
A6.1 Overview of SCS Link Transmission............................................................ A6-2
A6.2 Actions Taken for SCS Link Transmission when SCS is Unsteady.......... A6-7
A6.3 Forcing of SCS Link Transmission Data.....................................................A6-11
A7. SOER........................................................................................................A7-1
A7.1 Overview of SOER.......................................................................................... A7-1
A7.2 Event Collection.............................................................................................. A7-4
A7.3 Event Storage.................................................................................................. A7-8
A7.4 Management of Event Information when SCS is Unsteady......................A7-11
ProSafe-RS
Safety Control Station Reference
IM 32S03B10-21E 3rd Edition
CONTENTS
PART B RAS (Reliability, Availability, Serviceability)
B1. What is RAS (Reliability, Availability and Serviceability) of SCS?.....B1-1
B2. Operating Mode.......................................................................................B2-1
B3. Diagnostic Management Function and Diagnostic Information
Message...................................................................................................B3-1
B3.1 Diagnostic Management Function of SCS................................................... B3-2
B3.2 Notification of Diagnostic Information Messages....................................... B3-4
B4. Notification of Diagnostic Information using the IOM Report............B4-1
B4.1 IOM Report of AIO/DIO Modules . ................................................................. B4-2
B4.2 IOM Report of Serial Communication Modules......................................... B4-12
B5. Operations at SCS Startup.....................................................................B5-1
B6. Actions Taken at Error Occurrence and Recovery Procedure...........B6-1
B6.1 Actions Taken at Fatal Error Occurrence and Recovery Procedure......... B6-3
B6.1.1 Actions Taken at Occurrence of Errors Affecting the Entire System
and Recovery Procedure..................................................................B6-3
B6.1.2 Actions Taken at CPU Module Error Occurrence
and Recovery Procedure .................................................................B6-4
B6.1.3 Behavior at Abnormal Calculation....................................................B6-6
B6.2 Actions Taken at Major Error Occurrence and Recovery Procedure..... B6-10
B6.2.1 Actions Taken at Input Module Error Occurrence
and Recovery Procedure................................................................B6-11
B6.2.2 Actions Taken at Input Channel Error Occurrence
and Recovery Procedure................................................................B6-12
B6.2.3 Actions Taken at Output Module Error Occurrence
and Recovery Procedure................................................................B6-14
B6.2.4 Actions Taken at Output Channel Error Occurrence
and Recovery Procedure................................................................B6-16
B6.2.5 Actions Taken at Errors between CPU
and Input/Output Module and Recovery Procedure.......................B6-22
B6.2.6 Actions Taken at Error Occurrence for Optical ESB Bus Repeater
Devices ..........................................................................................B6-24
B7. Dual Redundancy....................................................................................B7-1
B7.1 Redundant Configuration in SCS.................................................................. B7-1
B7.2 CPU Redundant Status.................................................................................. B7-4
B7.3 Automatic Execution of IOM Download....................................................... B7-7
ProSafe-RS
Safety Control Station Reference
IM 32S03B10-21E 3rd Edition
CONTENTS
PART C POU (Program Organization Unit)
C1. Overview of POU.....................................................................................C1-1
C1.1 Types of Functions and Function Blocks.................................................... C1-1
C1.2 Common Specifications................................................................................. C1-7
C2. Safety Functions.....................................................................................C2-1
C2.1 MUXBOOL4 (BOOL-Type Multiplexer with 4 Entries)................................. C2-1
C2.2 MUXBOOL8 (BOOL-Type Multiplexer with 8 Entries)................................. C2-3
C2.3 MUXREAL4 (Real-Type Multiplexer with 4 Entries)..................................... C2-4
C2.4 MUXREAL8 (Real-Type Multiplexer with 8 Entries)..................................... C2-5
C2.5 SCALER (Scaler)............................................................................................. C2-6
C2.6 SEL_R (Real-Type Binary Selector).............................................................. C2-8
C2.7 SEL_T (TIME-Type Binary Selector).............................................................. C2-9
C2.8 IB_TO_V (Converter (IO_BOOL to Data Value))......................................... C2-10
C2.9 IB_TO_S (Converter (IO_BOOL to Data Status))........................................C2-11
C2.10 IR_TO_V (Converter (IO_REAL to Data Value))......................................... C2-12
C2.11 IR_TO_S (Converter (IO_REAL to Data Status))........................................ C2-13
C3. Safety Function Blocks..........................................................................C3-1
C3.1 REPEATTIMER (Repeat Timer)...................................................................... C3-1
C3.2 FILTER (First-Order Lag Filter)...................................................................... C3-4
C3.3 FILTER_S (First-Order Lag Filter with Data Status).................................... C3-6
C3.4 ANLG1OO2D (1oo2D Analog Voter).............................................................. C3-9
C3.5 ANLGVOTER (IO_REAL-Type Analog Voter)............................................. C3-15
C3.6 BOOLVOTER (IO_BOOL-Type BOOL Voter).............................................. C3-22
C3.7 ANLG_S (Analog Input Function Block with Data Status)....................... C3-25
C3.8 ANLGI (Analog Input)................................................................................... C3-33
C3.9 VEL (Velocity Limit Alarm)........................................................................... C3-38
C3.10 CTU (Count Up Counter).............................................................................. C3-41
C3.11 CTD (Count Down Counter)......................................................................... C3-43
C3.12 CTUD (Count Up/Down Counter)................................................................ C3-45
C3.13 B_TO_IB (Converter (Data Value and Status to IO_BOOL-Type Data)).. C3-47
C3.14 R_TO_IR (Converter (Data Value and Status to IO_REAL-Type Data)) .. C3-48
C3.15 ANN_FUP (First-up Alarm Annunciator).................................................... C3-49
C3.16 FUP_RST (First-up Alarm Annunciator Reset).......................................... C3-52
ProSafe-RS
Safety Control Station Reference
IM 32S03B10-21E 3rd Edition
CONTENTS
PART D Integration with CENTUM
D1. Integration with CENTUM.......................................................................D1-1
D2. Tag Name Interfaces for CENTUM.........................................................D2-1
D2.1 Overview of Tag Name Interfaces................................................................. D2-2
D2.2 Tag Name Interfaces for Internal Variables
and Input/Output Variables............................................................................ D2-8
D2.3 Tag Name Interfaces of Function Blocks................................................... D2-12
D3. Override Operation from HIS.................................................................D3-1
D3.1 Overview of Override FB................................................................................ D3-2
D3.2 Tag Name Interfaces and Process Alarms of
Override Function Blocks.............................................................................. D3-4
D3.3 Overview of Grouping Override Function Block......................................... D3-9
D3.4 Tag Name Interfaces and Process Alarms of
Grouping Override Function Block............................................................. D3-13
D3.5 Status Management of Function Blocks Used for Override.................... D3-16
D3.6 Permission for Override by Password FB................................................. D3-18
D3.7 Tag Name Interfaces and Process Alarms of
Password Function Blocks.......................................................................... D3-22
D4. Manipulation of Manual Operation Function Blocks from HIS..........D4-1
D4.1 HIS Interfaces of MOB_11 and MOB_21
(BOOL-Type Data Manual Operation Function Block with Answerback) D4-3
D4.1.1 Manual Operation Permission Function.......................................... D4-8
D4.1.2 Password at Manual Operations..................................................... D4-9
D4.1.3 Output Enable Status Display Function......................................... D4-10
D4.1.4 Answerback Check Function..........................................................D4-11
D4.1.5 Monitoring IOP and OOP............................................................... D4-16
D4.1.6 Tag Name Interfaces and Process Alarms of MOB_11
and MOB_21.................................................................................. D4-17
D4.2 HIS Interfaces of MOB_RS
(Auto-Reset BOOL-Type Data Manual Operation).................................... D4-22
D4.2.1 Operations of MOB_RS from HIS.................................................. D4-22
D4.2.2 Tag Name Interfaces and Process Alarms of MOB_RS................ D4-27
D4.3 HIS Interfaces of MOA (Analog-Type Data Manual Operation)................ D4-30
D4.3.1 Operations of MOA from HIS......................................................... D4-30
D4.3.2 Tag Name Interfaces and Process Alarms of MOA....................... D4-32
PC
Control bus
SCS
Communication function
DCS of other
companies
(Higher-level System)
Application logic
execution function External
communication function
RS-232C
Application logic
/RS-422
execution
/RS-485
Process data Subsystem
input/output function
Diagnostic function
A010101E.ai
l Application Logic
An SCS executes application logic written in the IEC 61131-3 program language. The application
logic is defined by the user using Multi Language Editor and downloaded to the SCS.
An SCS supports the following three languages of IEC 61131-3:
Function Block Diagram (FBD)
Ladder Diagram (LD)
Structured Text (ST)
SEE
ALSO For more information about Function Block Diagram (FBD) and Ladder Diagram (LD), see the following:
PART-C POU
For more information about Structured Text (ST), see the following:
2.5, Structured Text of the Engineering Guide (IM 32S01C10-21E)
TIP
The application logic execution function explained here is not simply a name for a function that handles execution
of the application logic; rather, it is a generic name for all the functions explained above, including the actual
execution of the application logic. In this manual, this term is used in the following explanation as well.
n SCS Databases
SEE
ALSO For details on SCS database types, see the following:
2.6, Capacity of SCS Applications of the Engineering Guide (IM 32S01C10-21E)
SEE
ALSO For the scan period and processing timings, see the following:
2.7, Performance and Scan Period in SCS of the Engineering Guide (IM 32S01C10-21E)
For the time synchronization, see the following:
2.14, Time Synchronization of the Engineering Guide (IM 32S01C10-21E)
For the clock setting operation, see the following:
3.1.5, Setting System Time of the Utilities and maintenance Reference (IM 32S04B20-21E)
SEE
ALSO For the SCS hardware configuration and hardware devices that comprise the overall system, see the
following:
2.2, Hardware Configuration of the Engineering Guide (IM 32S01C10-21E)
For the system size and hardware installation conditions, see the following:
2.3, Requirements for the Size of System and Installation of Hardware of the Engineering Guide (IM
32S01C10-21E)
For the SCS hardware configuration changes those can be performed by online change download, see the
following:
5.2, List of Applicable Items for On-line Change of the Engineering Guide (IM 32S01C10-21E)
n CPU Module
SCP461/SCP451
The following information is displayed in the LEDs of the CPU module (SCP461) installed in
the SSC60S/SSC60D and the LEDs of the CPU module (SCP451) installed in the SSC50S/
SSC50D.
Table LEDs of SCP461/SCP451
LED Quantity On (*1) Off
HRDY 1 The CPU hardware is normal A CPU hardware failure has occurred
RDY 1 Control is possible A fatal hardware/software failure has occurred
CTRL 1 The CPU module is in the CTRL status The CPU module is in the RDY or STBY status
COPY 1 During APC Not during APC
RCV 2 Vnet/IP bus 1/bus 2 receiving Vnet/IP bus 1/bus 2 not receiving
SND 2 Vnet/IP bus 1/bus 2 sending Vnet/IP bus 1/bus 2 not sending
The time synchronization function of the CPU
SYNC 1 Synchronized to the Vnet/IP time (*2)
module is faulty.
SCTY 1 Online level (*3) Offline level (*3)
*1: The RCV and SND LED blink.
*2: Whether or not an SNTP server is connected to the network does not affect the LED On condition.
*3: Security level 0 corresponds to offline level and security levels 1 and 2 correspond to online level.
The following communication statuses are indicated by combinations of RCV and SND statuses
(blinking or off). If a communication error has occurred, the network location where the error
occurred can be identified easily using the Network Status Display dialog box on the HIS.
Table SND/RCV LED Statuses and Communication Statuses
SND RCV Communication Status
Off Off Communication disconnected
Blinking Blinking Normal (within the network connected by the layer 2 switch)
No other communication station is available (including a situation where only one SCS is
Blinking Off
connected to the network and its CPU module is operating in the single operation status)
Off Blinking The CPU module is faulty
SEE
ALSO For more information about the LED display of a CPU module, see the following:
4.2.2, LED Display of the Safety Control Stations (Hardware) (IM 32S06C10-21E)
COPY LED
CTRL LED
RDY LED
HRDY LED
A020001E.ai
The STATUS LEDs 1 to 8 can display either the status information or the domain/station number
of SCS depending on the display setting switch.
The meaning of each LED when the status information of the SCS is displayed is summarized in
the table below. The SCS can be judged as operating normally if all the LEDs from 1 to 8 are lit.
Table LEDs Indicating SCS Status
LED Display Description
Running mode: Both LED 1 and LED 2 turn on.
1, 2 Display of the operating mode Waiting mode: LED 1 turns off and LED 2 turns on.
Other modes: Both LED 1 and LED 2 turn off.
3 Tentative change of the security level LED 3 turns on only when the security level is 2.
LED 4 turns off if an error that does not involve user
4 An SCS error occurred (*1) operations has occurred in the system.
LED 4 turns on if there is no error.
5 to 7 Not used Always lit
Indicates a status of writing to the
8 LED 8 turns off while writing to the flash memory.
flash memory
*1: LED4 is interlocked with the output of the SYS_DIAG function block.
SEE
ALSO For more information about how to set LEDs 1 to 8 to display the V net address, see the following:
4.2.3, Setting Switches of the Safety Control Stations (Hardware) (IM 32S06C10-21E)
TIP
In the explanation in this document, analog input/output modules and discrete input/output modules are
collectively referred to as AIO/DIO modules. Analog input modules and discrete input modules are collectively
referred to as input modules, while analog output modules and discrete output modules are collectively referred
to as output modules.
SAI143
An analog input module for electrical current. Modules whose suffix code is SAI143-H
support HART communication and are indicated as SAI143H in the SCS State Management
Window on the SENG or the Status Display view on the HIS. SAI143-H can be used with
software release number of R1.02.00 or later.
SAV144
An analog input module for electrical voltage.
SAI533
An analog output module for electrical current. This module can be used with software
release number of R1.02.00 or later. These modules are indicated as SAI533H in the SCS
State Management Window on the SENG or the Status Display view on the HIS. This
module supports HART communication.
SDV144
A discrete input module. This module provides SOER (Sequence of Events Recorder)
function.
SDV521
A 4-channel discrete output module. This module can be used with software release number
of R1.03.00 or later.
SDV526
A 4-channel 100-120 V AC discrete output module. This module can be used with software
release number R2.02 or later.
TIP
In the case of SDV526, short circuits between channels cannot be detected. In addition, the following faults
cannot be detected while SDV526 is outputting OFF signals.
- Short circuits in output wiring
- Output overload (faults in field devices that cause short circuits or overcurrent when the modules output
is set to ON)
The signals (ON or OFF) output to SDV526 by the application logic must be held for at least one second so
as to ensure detection of faults inside the module or notification of diagnostic information.
SDV531
An 8-channel discrete output module.
SDV531-L
An 8-channel discrete output module for long distance. This module can be used with
software release number of R1.03.00 or later.
SDV53A
An 8-channel 48 V DC discrete output module. This module can be used with software
release number of R2.03.00 or later.
SDV541
A 16-channel discrete output module. This module can be used with software release
number of R1.02.00 or later.
SEE
ALSO For more information about the SOER function of a DI module, see the following:
A7.2, Event Collection
SEE
ALSO For details on Modbus slave connection, see the following:
B1, Modbus Slave Connection of the Open Interfaces (IM 32S05B10-21E)
For details on using a serial communication module for subsystem communication, see the following:
Subsystem Communication Function in 2.16, Connection with Other Systems via Serial
Communication of the Engineering Guide (IM 32S01C10-21E)
Note the following cautions when implementing the serial communication modules.
Modbus slave communication and subsystem communication cannot be performed
simultaneously within a single serial communication module.
When used for Modbus slave communication, serial communication modules cannot have a
redundant configuration. If redundancy is required, use two serial communication modules
and provide redundancy using a user application.
A serial communication module can be configured as a redundant module if used for
subsystem communication.
The serial communication module for Modbus slave communication cannot be installed to
an I/O node that is connected with the optical ESB bus repeater module and installed at a
distance longer than 5 km on the SCSP network.
Application Logic
Execution Function
External Communication
Function
The Application Logic Execution Function is the function having a top priority among SCS
functions. The External Communication Function is executed in a part where the Application
Logic Execution Function is not executed in the CPU processing period. If the External
Communication Function finishes its processing before a scan period ends, the remaining time
becomes the idle time on CPU.
1 2 3 4 5 1 2 3 4 5
Scan period
A030102E.ai
The processing time of the Application Logic Execution Function may be prolonged by about
20% at maximum because of the increase in the CPU load caused by communication for tag
data access or some other processing.
SEE
ALSO For more information about the Link Architecture View, see the following in the Workbench of the Workbench
Users Guide:
Runtime Setting in Editing Resource Properties of Link Architecture View
IMPORTANT
The purpose of this function is to temporarily avoid occurrences of erroneous conditions in
SCS. SCS cannot maintain the assumed process safety time if the automatic scan period
extension function is executed. Thus, take permanent measures such as reducing the amount of
application logic in order to lower the CPU load on the SCS.
It is possible to check if the scan period has been automatically extended on the SENG or Status
Display view of HIS as well as via diagnostic information messages. It is also possible to create
application logic for confirming the state of scan period extension.
SEE
ALSO For more information about how to specify automatic extension of scan period on the SCS Constants Builder, see
the following:
3.1.3, SCS Constants Builder of the Engineering Reference (IM 32S04B10-21E)
At normal condition
Figure Example of the Case when the Scan Period is Automatically Extended
The automatic scan period extension function automatically extends the scan period of the
Application logic Execution Function when high-load conditions occur and ensures sufficient
time for the processing of communication on the control bus and for the External Communication
Function that is done during the intervals between executions of the application logic.
Scan period of Application logic Execution Function is extended
to ensure sufficient processing time for control bus processing
and External Communication Function.
At high-load
(After extension)
By using the automatic scan period extension function, the time for the communication
processing related to the following features are ensured.
Inter-SCS safety communication
CENTUM integration
Communication with SENG
Diagnostic information message, process alarm notification
If this high load status continues for 1 second or longer, the scan period of the application logic
execution function is automatically extended.
The new scan time is obtained by adding 20% of the original scan period of the application logic
execution function to the actual measurement of the application execution time at that time.
SEE
ALSO For more information about diagnostic information messages, see the following of the Messages (IM 32S02B10-
21E):
No. 4143 Start of automatic scan period extension
No. 4144 Cancellation of automatic scan period extension
If automatic scan period extension is continuously activated for a certain period of time or
longer, the diagnostic information message indicating the start of the automatic scan period
extension function is notified to give warning again. The default interval of re-warning is 10
minutes.
The interval of re-warning can be changed using the SYS_SCANEXT system function
block.
The system function block (SYS_SCANEXT) can be used to determine whether the
automatic scan period extension function is being executed via application logic (*1).
*1: The SYS_SCANEXT system function block can be used in new SCS databases created by SENG of R2.03.00 or later.
SEE
ALSO For more information about SYS_SCANEXT, see the following:
C9.21, SYS_SCANEXT (Scan Period Extension Indicator)
If the scan period of the application logic execution function is changed via online change
download while the scan period is being automatically extended, the scan period extension
status is cancelled after the completion of the online change download and the diagnostic
information message on cancellation of scan period automatic extension is notified.
However, if the high CPU load continues even after the scan period is changed and if
the conditions for automatic scan period extension are met, the scan period is extended
automatically.
The SCS State Management window of SENG and the Status Display view of HIS (*1)
display both the scan period of the application logic execution function defined in SCS
Manager and the actual scan period of the application logic execution function of SCS.
*1: Supported in CENTUM VP R4.02 or later.
SEE
ALSO For precautions on engineering related to automatic expansion of scan period, see the following:
2.7, Performance and Scan Period in SCS of the Engineering Guide (IM 32S01C10-21E)
When changing to a shorter scan period, a dialog box appears, showing the expected CPU idle
time after the scan period is changed. You cannot download if the expected CPU idle time is 0
second.
SEE
ALSO For more information about the diagnostic information message, see the following:
No. 4152 On-line change of scan period of the Messages (IM 32S02B10-21E)
*1: The standard time is specified by the user using SCS Maintenance Support Tool of the SENG or the Adjust Time dialog box of an
HIS.
SEE
ALSO For more information about time setting operations, see the following:
3.1.5, Setting System Time of the Utilities and Maintenance Reference (IM 32S04B20-21E)
For more information about SCS Constants Builder, see the following:
3.1.3, SCS Constants Builder of the Engineering Reference (IM 32S04B10-21E)
SEE
ALSO For details on Vnet/IP time synchronization, see the following:
A4, Time Synchronization of Vnet/IP of the ProSafe-RS Vnet/IP (IM 32S56H10-21E)
CPU CPU
Time setting
DI module
V net time
A030201E.ai
TIP
If the diagnostic information message, GPS Interface Unit Error is notified when the V net time synchronization
is selected, the CPU module need not be replaced if the following conditions are met. Since this message does
not present any problem in practical operations or on safety, you can continue to operate the system.
If the message is generated only on the control-side CPU module in the redundant configuration
immediately after completion of APC:
If the recovery message, GPS Interface Unit Recover is displayed for the control-side CPU module
immediately thereafter, the module is not faulty.
If the V net configuration is unstable:
In a condition where the V net is not connected correctly, such as at startup, a bus configuration error may
occur. In this case, the V net controller in CPU module cannot read time information and this message will
be notified as a result. Reconnect the bus correctly and start the SCS. If the message no longer appears,
the module is recovered.
CPU
Standard
IRIG-B IRIG-B
time IRIG-B time IRIG-B time
receiver
Time setting
DI module
IRIG-B time
A030202E.ai
Time Time
master notification Time
notification
SCSP
Standard time
CPU
SNTP Vnet/IP Vnet/IP Vnet/IP
domain 1 domain 2 Vnet/IP time
server
Time
(Installed as necessary) notification
Time
notification SCSP SCSP
CPU CPU
Vnet/IP time Vnet/IP time
Time
setting
DI module
Vnet/IP time
A030203E.ai
TIP
Examples of GPS receiver failure are listed below.
Failure in the communication route from the GPS antenna to the GPS receiver
Antenna failure or receiving problem
What happens when the GPS receiver fails is determined by the specification of the selected GPS receiver. The
following is an example of what might happen when the GPS receiver fails.
Since GPS signals are no longer received, the GPS receiver operates based on its clock.
If reception problem continues more than a specified period, the GPS receiver stops operating on its clock
and also stops notifying time information to the connected devices.
Once time notification is stopped, the SCS outputs a diagnostic information message notifying an IRIG-B error.
IMPORTANT
If the IRIG-B time synchronization is selected, connect the GPS unit via the IRIG-B first, and then
start the SCS.
SEE
ALSO For details on the time synchronization, see the following:
2.14, Time Synchronization of the Engineering Guide (IM 32S01C10-21E)
Application logic
Function Blocks
Output
enable/disable
Legend
Input module Output module Data Value
Data Status
1. Data sent from sensor devices or other sources is read from each channel of a connected
input module.
2. The CPU copies the data stored in the input module to the I/O image area at the start
of scanning. At this point, the data value and data status are determined based on the
information from the input module. If the input data is erroneous, the data status is set to
BAD and the data value is set to the Input value at error occurrence specified in I/O
Parameter Builder by the user.
tip
The following settings defined in I/O Parameter Builder are used for Input value at error occurrence, which is
used if input data is erroneous.
[Input Processing at Fault] of AI and DI modules
[Input Processing at Transmitter Fault] of an AI module
This manual uses the term input value at error occurrence in the following explanation as a generic term.
3. The CPU stores the input data in the I/O image area in the input variables of the application
logic. It also updates the data status of the output variables.
4. The application logic references the data value and data status from the input variables and
monitors the process conditions and input device status.
5. The result of the application logic processing is stored in the output variables and then sent
to the output module via the I/O image area.
6. The output module outputs the data to devices such as valves or lamps connected to each
of the channels.
SEE
ALSO For more information about the output enable operation, see the following:
3.1.6, Output Enable Operation of the Utilities and Maintenance Reference (IM 32S04B20-21E)
Lock/unlock variable
Output variable
Output module
Output data Output data Output data
Lock/unlock variable
A040201E.ai
Variables that handle input values and output values of input/output modules are referred to as
input and output variables, respectively. Input and output variables contain two types of data,
logical data and physical data. When input and output variables are defined, both logical data
and physical data are automatically created.
Table Input Variable and Output Variable
Type Data Description
Physical data Data set from the I/O image area
Input variable
Logical data Data referenced by the application logic (*1)
Physical data Data set in the I/O image area (*2)
Output variable
Logical data Data set by the application logic
*1: If the input data is erroneous, the input value at error specified by the user in advance is set.
*2: This is the value set to the output module.
Both the logical data and physical data are composed of data value and data status. In order to
handle data value and data status, input/output variables provide IO_BOOL type for handling
BOOL-type data and IO_REAL type for handling real number-type data, which can be used
according to the data type of the data value.
The data value and data status can be referenced using the application logic. Use the syntax
input/output variable name.v and input/output variable name.status in order to read only the
data value or the data status from an input/output variable, respectively.
SEE
ALSO For more information about the forcing function, see the following:
A8, Forcing
See the following for the detailed explanation about locking input/output variables:
A8.1, Variable Locking
SEE
ALSO For more information about input/output variable lock operation, see the following:
2.1, I/O Lock Window of the Utilities and Maintenance Reference (IM 32S04B20-21E)
Lock/unlock status of input/output variables, Output Enable/Output Disable status and data
value/data status in each status can be summarized as shown in the following tables.
SEE
ALSO For details on how data values and statuses change upon occurrence of an input error, see the followings:
B6.2.1, Actions Taken at Input Module Error Occurrence and Recovery Procedure
B6.2.2, Actions Taken at Input Channel Error Occurrence and Recovery Procedure
SEE
ALSO For more information about the output enable operation, see the following:
3.1.6, Output Enable Operation of the Utilities and Maintenance Reference (IM 32S04B20-21E)
For details on how data values and statuses change upon occurrence of an output error, see the followings:
B6.2.3, Actions Taken at Output Module Error Occurrence and Recovery Procedure
B6.2.4, Actions Taken at Output Channel Error Occurrence and Recovery Procedure
Output value
at fault
Forcing
A040102E.ai
The following processing is performed until the logical data is output as physical data from the
analog output module.
Output is limited to a range of -17.19 to 118.75 [%].
If tight-shut/full-open is specified, the tight-shut value is set when the logical data is 0.0 or
below, or the full-open value is set when the data is 100.0 or above.
If output is disabled or locked, the last physical data value is retained.
If an error occurs, the output value at fault is set or the last value is retained in accordance
with the output processing at fault.
l R2.02 or later
The target AIO/DIO module continues its input/output operations during IOM download. The
behavior of SCS is as follows:
The target modules continue their input/output operations.
AIO/DIO modules in redundant configuration retain their control rights.
The diagnostic information message of IOM Fail is not output.
WARNING
If the system program release number of the target SCS is earlier than R2.02, the target AIO/DIO
modules will be stopped during IOM download even if the software release number of SENG is
R2.02 or later. In this case, a message indicating that the target AIO/DIO module will be stopped
(IOM Fail) is displayed before the online download is started.
You can confirm the system program release number of SCS in the SCS State Management
Window of the SCS maintenance support tool.
SEE
ALSO For the behavior of SCS with a system program earlier than R2.02, see the following:
9.6.2 Compatibility with Earlier Revisions of the Installation (IM 32S01C50-21E)
SEE
ALSO For the behavior of SCS with Modbus slave connection, see the following:
B1.1 Overview of Modbus Slave Connection of the Open Interface (IM 32S05B10-21E)
For the behavior of SCS in Subsystem communication, see the following:
C1.7 On-line Change of the Open Interface (IM 32S05B10-21E)
SEE
ALSO For more information about how to change application online, see the following:
5, On-line Change of Applications of the Engineering Guide (IM 32S01C10-21E)
For more information about input/output values when serial communication modules for sub-system
communication are added via online change download, see the following:
C1.3, Error Handling Actions of the Open Interfaces (IM 32S05B10-21E)
l Node Number
This item displays the node number in which a module is mounted. It is defined in I/O Wiring View
of SCS Manager.
This item is only for display and cannot be edited in the tab.
l Component Number
This is a comment related to node layout information. Any character string can be entered.
This setting item is not downloaded to an SCS.
This setting item can be changed online.
TIP
In the case of nodes equipped with ALR111 or ALR121 for Modbus slaves, if 10 km or longer is specified in
[Maximum Extension Distance] on the SCS Constants Builder, select [Yes] and specify the node extension
distance in [Extends To (Km)].
IMPORTANT
Be sure to specify the extension distance according to the actual node extension distance. If no
specification is made for SCSP1, load fluctuation of CPU becomes large if input/output modules
and/or bus fail.
l Comment
This is a comment related to the node. Any character string of up to 24 single-byte characters or
12 double-byte characters can be entered.
This setting item is downloaded to an SCS.
This setting item can be changed via online change download.
SEE
ALSO For more information about node setting operation, see the following:
4.4, I/O Parameter Builder of the Engineering Reference (IM 32S04B10-21E)
l Node Number
This item displays the node number in which the input/output module is mounted. It is defined in
I/O Wiring View of SCS Manager.
This item is only for display and cannot be edited in the tab.
l Slot Number
This item displays the slot number in which the input/output module is mounted. It is defined in
I/O Wiring View of SCS Manager.
This item is only for display and cannot be edited in the tab.
l Device
This item displays the model name of the input/output module. It is defined in I/O Wiring View of
SCS Manager.
This item is only for display and cannot be edited in the tab.
l Dual-Redundant
This item displays whether the input/output module is placed in single configuration or redundant
configuration. It is defined in I/O Wiring View of SCS Manager. Input/output modules are placed
in redundant configuration using an odd-numbered slot and the adjacent even-numbered slot
(the odd number + 1).
This item is only for display and cannot be edited in the tab.
l Device Number
This is the device number assigned to the input/output module. It is defined in I/O Wiring View of
SCS Manager.
This item is only for display and cannot be edited in the tab.
l Comment
This is a comment related to the input/output module. Any character string of up to 24 single-byte
characters or 12 double-byte characters can be entered.
This setting item is not downloaded to an SCS, so changing the definition does not affect input/
output processing.
This item can be changed online.
l Channel Number
This is the channel number displayed in I/O Wiring View of SCS Manager. It is sequential number
starting from 1.
This item is only for display and cannot be edited.
l Wiring Position
This is the channel position displayed in I/O Wiring View of SCS Manager. It is determined by
device number and channel identification number. The channel identification number used for
wiring position is sequential number starting from 0. The wiring position of the input modules is
prefixed with %IU while the wiring position of the output modules is prefixed with %QU.
This item is only for display and cannot be edited.
Example: In the case of a 16-channel input module: %IU1.0, %IU1.1, ... %IU1.14, %IU1.15
In the case of a 8-channel output module: %QU3.0, %QU3.1, ... %QU3.6, %QU3.7
l Direction
This item indicates whether a signal is an input or output signal.
This item is only for display and cannot be edited.
l Comment
This is a comment for an input/output variable specified in Dictionary View (*1) of SCS Manager.
This item is only for display and cannot be edited.
*1: The comment for the input/output variable specified in Dictionary View of SCS Manager is displayed as the comment for the
wired channel. Up to 64 characters can be specified for the variable comment, but only 32 characters are retained in SCS
database; therefore, make sure not to specify more than 32 characters. Channel comments for unused channels (unconnected
channels) are not displayed.
Comments for DI/DO variables are the variables used as identifiers of SOE.
TIP
If comments for DI/DO variables are changed in Dictionary View of SCS Manager, discrepancies occur due to the
input/output definition changes, and it becomes necessary to perform online change download to the SCS. Since
this changes only the definitions in the databases of the SCS (no changes are made to the parameters of the
DI/DO modules themselves), the inputs and outputs are not influenced by the online change download.
SEE
ALSO For more information about common setting items for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
The setting items that are not explained above as common items are explained below.
l Command Line
This item does not need to be entered.
SEE
ALSO For more information about common setting items for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
0%
SL SH Input signal
(raw data)
A040401E.ai
Figure SQRT
l Unit
This is the unit of the input signal and determined by the type of input module.
In addition to the checks above, the following input checks are performed.
Number of input characters: Up to 7 single-byte characters
Number of decimal places: Up to 2 digits
In addition to the checks above, the following input checks are performed.
Number of input characters: Up to 7 single-byte characters
Number of decimal places: Up to 2 digits
PV
IOP+
NR
TRNS-
IOP lower limit detection level
IOP-
(7)
IMPORTANT
Make sure that this setting matches with the 2-wire/4-wire setting made using the setting pins
in the analog input module. If the settings made here are different from those of the hardware, a
channel error occurs in the case of single input module configuration and the control shifts to the
standby module in the case of a dual-redundant input module configuration.
SEE
ALSO For more information about common setting items for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
The setting item that is not explained above as common item is explained below.
Command Line
TIP
Specify the command line using up to 256 single-byte characters. If the command line is not set, the default value
will be used for each applicable item. The format is as follows.
Item name = Data value, Item name = Data value,
SEE
ALSO For more information about common setting items for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
The setting items that are not explained above as common items are explained below.
Tight-shut/Full-open
Tight-shut/full-open is a function that reduces the actual output value to 0% or below when the
manipulated output value is 0%, or increases the actual output value to 100% or above when the
manipulated output value is 100%, in order to fully close or open the control valve firmly. Specify
whether or not to enable this function.
If PRM is used, set [Tight-shut/Full-open] to [Yes] and determine an appropriate tight-shut value
for the connected device.
Yes:
Enable the tight-shut/full-open function (default). Specify a tight-shut value in [Tight-shut
Value], and a full-open value in [Full-open Value].
The initial output value of the module (i.e., default initial value upon power-on) will be the
same value of the tight-shut output.
No:
Disable the tight-shut/full-open function. The initial output value of the module (default initial
value upon power-on) is fixed to -17.19% (1.25 mA).
Tight-shut Value
This item specifies in a range of -17.19 to 0 (%) the actual value to be output when the tight-shut/
full-open function is specified and the output value is 0%. The default is -17.19% (1.25 mA).
This setting is possible only when [Tight-shut/Full-open] is set to [Yes].
The following input checks are performed.
Range: -17.19 to 0 (%)
Permitted characters: Single-byte numbers, decimal point, negative sign (-)
Number of characters: Up to 6 single-byte characters
Number of decimal places: Up to 2 digits
Full-open Value
This item specifies in a range of 100 to 117.19 (%) the actual value to be output when the tight-
shut/full-open function is specified and the output value is 100%. The default is 106.25% (21 mA).
This setting is possible only when [Tight-shut/Full-open] is set to [Yes]. To implement reverse
output, create the necessary application using the application logic.
The following input checks are performed.
Range: 100 to 117.19 (%)
Permitted characters: Single-byte numbers, decimal point, negative sign (-)
Number of characters: Up to 6 single-byte characters
Number of decimal places: Up to 2 digits
Detect Disconnection
This item specifies whether or not to detect open circuit.
Yes:
Detect open circuit (default).
No:
Do not detect open circuit.
IMPORTANT
If the current output value falls below -6.25% (3 mA) due to the settings of [Output Value at Fault]
and [Tight-shut Value], the short circuit detection operation becomes unstable in the range of
SCREG setting 20 ohms.
Therefore, consider the above characteristics and actual wiring resistance and set an appropriate
SCREG value that allows short circuit detection to be performed without fail.
If the default SCREG setting (70) is used without setting the command line, short circuit is not
detected if the wiring resistance reaches or exceeds 90 . However, short circuit is detected
without fail when the wiring resistance is 50 or below.
(Example) A device is connected using a KS cable and the short circuit detection level is set
to 70
Terminal Output
Device
block module
Wiring KS cable
A040502E.ai
TIP
(Reference)
The resistance values of respective cables are as follows:
KS cable: 230 /km
Standard cables (AWG20, etc.): 23 to 50 /km
SEE
ALSO For more information about common setting items for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
Each of setting items that are not explained as common items is explained below.
l Software Filter
The software filter is applied for reducing the influence of noises. An integer between 0 and 10
can be selected as the filter setting value. The default setting is 1.
With this filter, the discrete input chattering signals can be sifted out so as to prevent from error
actions.
The filter setting value multiplied by 10 ms (sampling period) is the filter time. The chattering
signals occurred within this filter time will be eliminated.
As an example, if the filter setting value is 2, the chattering signals shorter than 20 ms (2x10 ms)
will be eliminated.
If the filter setting value is 0, the noise signals will not be filtered thus PV varies with the
noise signals. In general, the filter setting value should not be set to 0.
SEE
ALSO For more information about SOE, see the following:
A7, SOER
SEE
ALSO For more information about items set commonly for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
IMPORTANT
If [Yes] is set for [Detect Disconnection], disconnection errors can be detected. Make sure,
however, to connect a wiring check adapter (SCB100) on the channel if you specify [Yes]. If you
specify [Yes] without connecting the adapter, the SCS erroneously detects a disconnection error
whenever the input value is OFF.
IMPORTANT
If [Yes] is set for [Detect Short Circuit], short-circuit errors can be detected (assuming short circuit
with the power supply line). Make sure, however, to connect a wiring check adapter (SCB110)
on the channel if you specify [Yes]. If you specify [Yes] without connecting the adapter, the SCS
erroneously detects a short-circuit error whenever the input value is ON.
IMPORTANT
If [Yes] is set for [Pulse Test], wiring short-circuit errors between input channels can be detected.
Make sure, however, to connect a wiring check adapter (SCB110) to the channel if you specify
[Yes] for a channel whose input signal is normally ON. If you specify [Yes] without connecting the
adapter, the SCS cannot detect inter-channel short circuit when the input value is ON.
SEE
ALSO For more information about items set commonly for process data inputs and outputs, see the following:
A4.3, Common Setting Items for Process Data Inputs and Outputs
l Command Line
This item does not need to be entered.
SEE
ALSO Always read the following IM when implementing safety communication between SCSs that are connected to the
Vnet/IP network:
ProSafe-RS Vnet/IP (IM 32S56H10-21E)
SEE
ALSO For more information about Inter-SCS safety communication and precaution for engineering, see the followings:
2.8, Inter-SCS Safety Communication of the Engineering Guide (IM 32S01C10-21E)
Binding (*3)
Binding Binding
variable variable
Control bus
A050001E.ai
IMPORTANT
The output enable operation is required in order for the SCS on the producing side to perform
transmission. The function block on the consuming side outputs the specified fail-safe values
and communication status (parameter NR) becomes abnormal (FALSE) until the output enable
operation is performed.
SEE
ALSO For more information about setting a fail-safe value of the function block on the consuming side, see the
followings:
For BOOL type data, see the following:
C4.4, CONS_B (Inter-SCS Safety Communication BOOL-Type Data Consumer)
For DINT type data, see the following:
C4.5, CONS_I (Inter-SCS Safety Communication INTEGER-Type Data Consumer)
For REAL type data, see the following:
C4.6, CONS_R (Inter-SCS Safety Communication REAL-Type Data Consumer)
The following operations are performed if the system recovers from a communication error.
The data value received from the producing side is output from the function block on the
consuming side.
The communication status (parameter NR) becomes normal (TRUE).
A diagnostic information message notifying about the recovery is output.
The operations performed for each error status are summarized below.
SEE
ALSO For the basic functions of SCS link transmission, see the following:
2.9, SCS Link Transmission of the Engineering Guide (IM 32S01C10-21E)
For the engineering of SCS link transmission, see the following:
5.3, SCS Link Transmission Definition of the Engineering Reference (IM 32S04B10-21E)
For details regarding SCS Global Switch Communication, see the following:
D6, SCS Global Switch Communication
FCS0101 SCS0102
Control bus
FCS data
input FB Logic
Application logic
SCS0103
A060001E.ai
l Send Data
Send data of SCS link transmission has data value only and no data status. There is only one
type of output FB, regardless of whether the send destination is SCS or FCS.
SEE
ALSO For details of each function block, see the following:
C4.8, LTRCV (Safety Link Transmission Data Input)
C4.7, LTSND (Link Transmission Data Output)
C6.5, LTFCS (Interference-free Link Transmission Data Input)
C9.3, SYS_FORCE_LT (SCS Link Transmission Lock Status Monitor)
C9.5, SYS_LTSTS (SCS Link Transmission Reception Status Monitor)
TIP
At all SCSs in the domain where it is permitted to receive SCS link transmission from the station for which
sending is defined, the application regarding receive data can be changed freely, and such changes do not affect
other stations.
IMPORTANT
If data with no wiring definition at the sending station is referenced at the receiving side station,
data status will be GOOD and data value will be FALSE.
SEE
ALSO For items to note on setting OUTT, DLYT and PALT, see the following:
n Precaution for Engineering of 2.9, SCS Link Transmission of the Engineering Guide (IM 32S01C10-
21E)
Reception interval
Time
A060002E.ai
IMPORTANT
If both PALT and DLYT are set to 0, the receive data of SCS link transmission cannot be used for
safety purposes.
IMPORTANT
If wiring of the receive data from a nonexistent station is defined, the data status will always be
BAD and the data value will be the input value at error occurrence.
SEE
ALSO For actions taken for SCS global switch communication when the SCS is unsteady, see the following:
D6, SCS Global Switch Communication
l Start of Reception
When the SCS is started, reception of SCS link transmission starts.
Figure SCS Link Transmission Safety Communication Receive Data during SCS Startup
TIP
After the output enable operation is performed, sending of SCS link transmission will not be placed in the Output
Disable status until the SCS is stopped.
SEE
ALSO For details on diagnostic information messages, see the following:
No. 4133 in 2.1, System Alarms of the Messages (IM 32S02B10-21E)
SEE
ALSO For details on diagnostic information messages, see the following:
No. 4134 in 2.1, System Alarms of the Messages (IM 32S02B10-21E)
TIP
Forcing of SCS link transmission data can be performed only from the SCS Link Transmission Lock window.
Forcing (lock operation, viewing lock status, setting values) cannot be performed by selecting link transmission-
related function blocks in Dictionary View.
SEE
ALSO For the SCS Link Transmission Lock Window, see the following:
2.2, SCS Link Transmission Lock Window of the Utilities and Maintenance Reference (IM 32S04B20-21E)
SCS
SCS link transmission data management
Receive/Send buffer
Output Enabled/
Disabled status
Physical data area Physical data area
A060201E.ai
SCS link transmission data has logical data and physical data, like input/output variables.
These data can be referenced from the SCS Link Transmission Lock window.
If the SCS link transmission is locked, logical data of the receive data and physical data of
the send data can be set to any value from the SCS Link Transmission Lock window.
Locked status
Logic
Value setting
A060202E.ai
TIP
In the Output Disable status, data will not be sent even when the send data is locked and the data value is set. If
the output enable operation is performed in the locked status, the set data will be sent.
SEE
ALSO For SYS_FORCE_LT, see the following:
C9.3, SYS_FORCE_LT (SCS Link Transmission Lock Status Monitor)
The locked status of SCS link transmission data is managed separately from locked input/
output modules or variables. Locking the SCS link transmission data does not affect the
SYS_FORCE or SYS_FORCE_SC system function blocks.
SEE
ALSO For diagnostic messages regarding SCS link transmission lock/unlock, see the following:
No. 4135 and No. 4136 in 2.1, System Alarms of the Messages (IM 32S02B10-21E)
SCS0103
Ready
Change
application logic
F060203E.ai
A7. SOER
SOER (Sequence of Events Recorder) is a function for recording events detected by an
SCS so that they can be used in analyses. In ProSafe-RS, it can be used in such a way
that users can analyze causes of events based on event information obtained before/after
tripping.
This chapter explains SCS functions related to the SOER function. Refer to related
explanations for engineering tasks of SOER, SOE Viewer and the host interfaces.
SEE
ALSO For the items to note when configuring a SOER, see the following:
2.13, Configuration of the SOER of the Engineering Guide (IM 32S01C10-21E)
For SOER engineering tasks, see the following:
7, SOER Collection Definition of the Engineering Reference (IM 32S04B10-21E)
For SOE Viewer, see the following:
4, SOE Viewer of the Utilities and Maintenance Reference (IM 32S04B20-21E)
For the host interfaces, see the following:
A1, SOE OPC Interface of the Open Interfaces (IM 32S05B10-21E)
n ProSafe-RS SOER
l Configuration
The SOER function of ProSafe-RS can be used for a minimum system configuration, i.e., one
SENG and one SCS.
l Event Collection
The SOER function of ProSafe-RS can collect changes of not only discrete inputs (DI) but
also discrete outputs (DO) as event information.
Analog input values can also be collected as event information.
By creating FBs for SOER, changes of analog output values and application logics can be
collected as event information. By doing so, changes of communication data with other
SCSs can also be recorded.
l SOE Viewer
Event information saved in an SCS can be read by the SOE Viewer function in an SENG via
the control bus.
SOE Viewer allows filtering the event information so that only the information the user wants
to see is shown.
SOE Viewer can display diagnostic information messages as well.
Control bus
Download Upload
CPU Module
Time synchronization Event collection Event storage
function function function
Download
Time setting
SCS
A070101E.ai
Figure Relationship between SCS and SENG (Time Synchronization with IRIG-B)
The user defines items related to SOER on an SENG. The defined information is downloaded
to the CPU of an SCS as well as to discrete input modules in the system. The event information
collected/saved in the SCS is uploaded to SOE Viewer in the SENG or HIS.
With SCSs connected to the V net, IRIG-B time synchronization can be selected.
With SCSs connected to the Vnet/IP, time synchronization is implemented based on the Vnet/IP
time.
n Event Targets
An SCS can save the following data as event information by user specification.
Events related to discrete inputs (DI) are collected by the input modules; other events are
collected by the CPU.
ANLG_S
IN OUT
SH STS
SL NHTR
HH NHHH
PH NLLL
PL NLTR
LL
HYS
TRDT
PADT
SOER
ID
A070201E.ai
An ANLG_S function block collects events when the following outputs change their status from
FALSE to TRUE, or from TRUE to FALSE:
NHTR (HI trip flag)
NHHH (HI pre-alarm flag)
NLLL (LO pre-alarm flag)
NLTR (LO trip flag)
When the event occurred can be checked in the ID field of the SOE Viewer.
Table ANLG_S Event IDs
ID in SOE Viewer Occurrence timing of event
EVT_TRUE When an alarm recovered (when output status change from FALSE to TRUE).
EVT_FALSE When an alarm generated (when output status change from TRUE to FALSE).
IN
TRP
ID
A070202E.ai
SOE_I
IN
TRIG
TRP
ID
A070203E.ai
SOE_R
IN
TRIG
TRP
ID
A070204E.ai
n Event Time
Event information records include a time stamp indicating when the event occurred. The event
generation time varies depending on the event type (object).
Table Event Time
Object Time information of event
Discrete input (DI) The current time of a discrete input (DI) module at event generation is recorded.
The current SCS time is stamped to the signal right before outputting it through the
Discrete output (DO)
output module.
The current time of the SCS right before the execution timing of a function block is
Variable
recorded.
CPU
Application logic
Events of DO
and variables
Event of DI
DI module
A070301E.ai
Since event information from a discrete input (DI) module is automatically stored in the DI event
temporary storage memory of the CPU, both the DI event in this memory and event information
collected in the application logic are stored in the SOER event information storage memory.
n Trip Signal
Trip signals are particularly important events in the plant. Since they are key events when
engineers attempt to analyze the causes of tripping, they must be securely stored in the
SCS together with the events generated before and after them.
Either ON edge or OFF edge can be specified as the trip signal. However, both edges can
be specified as ignored.
Users can specify trip signals in input/output definitions or in function blocks for SOE. There
is no restriction on the number of trip signals that can be specified, but it is necessary to
examine trip signal settings thoroughly in order to record useful event information.
SEE
ALSO For the initialization of trip signal files, see the following:
3.4.5, Initialization of Tripping Information of the Utilities and Maintenance Reference (IM 32S04B20-21E)
SEE
ALSO For more information on SOE event collection when the module control right is switched, see the following:
B7.1, Redundant Configuration in SCS
A8. Forcing
Forcing is used in the maintenance of SCSs and debugging of applications. Specifically,
a user interface is provided that can be used to lock I/O modules, variables and FB
parameters, and set desired values. Forcing can be used when the SCS security is Level 1
or below.
SEE
ALSO For the items to note when performing engineering work relating to forcing, see the following:
7.2.3, Forcing and Override of the Engineering Guide (IM 32S01C10-21E)
For the forcing operations, see the following:
2, Forcing Function of the Utilities and Maintenance Reference (IM 32S04B20-21E)
For forcing of subsystem communication data, see the following:
C1.5, Forcing of Subsystem Communication Data of the Open Interfaces (IM 32S05B10-21E)
For forcing of SCS link transmission data, see the following:
A6.3, Forcing of SCS Link Transmission Data
This chapter explains forcing of variables, parameters of function blocks, and inter-SCS
safety communication as well as applications of forcing.
In the case of an input variable, the value on the input side is the input from the input channel and
is called physical data. The value of an input variable on the output side is read by the application
logic and is called logical data.
An input variable consists of input data and data status.
In the case of an output variable, the value of the input side is the result of application logic
processing and is called logical data. The value of the output side of an output variable is the
output to the output channel and is called physical data. An output variable also consists of output
data and data status, in the same way as an input variable.
WARNING
When unlocking input/output variables, make sure to check the logical data and physical
data of input/output data and data status. Check that there will be no adverse effects
of unlocking on the system, such as a value changing abruptly after canceling the lock,
causing nuisance tripping.
While the forcing function is executed, the systems safety functions are disabled. If you use
the forcing function for the purpose of maintenance after starting the actual operation, quit
the forcing function immediately after the completion of system maintenance and enable the
systems safety functions so that they operate normally. At the completion of a target test
or when quitting SCS Manager during a target test, a dialog box appears to call attention
to locked variables. In this case, display a list of the locked variables using the I/O Lock
window or other means and cancel the lock status of these variables.
Input channel
A080102E.ai
If an input variable is locked, its logical data will no longer be overwritten with the value of the
physical data. The value of the logical data matches the value of the physical data at the time of
locking for both the input data and data status. The locked variable values can be changed after
the lock operation.
SEE
ALSO For more information about variable value setting, see the following:
A8.2, Variable Value Setting
SEE
ALSO For more information about acknowledging diagnostic information messages, see the following:
3.2, Displaying SCS Diagnostic Information of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
Output module
Output channel
Output data Output data Output data
A080103E.ai
SEE
ALSO For more information about acknowledging diagnostic information messages, see the following:
3.2, Displaying SCS Diagnostic Information of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
SEE
ALSO For more information about the relationship between locking of internal variables with SCSP2 and performance of
SCS, see the following:
n Locking of Internal Variables and Performance: SCSP2 in 2.7, Performance and Scan Period in SCS
of the Engineering Guide (IM 32S01C10-21E)
In the case of internal variables, the value on the input side is called physical data and the value
on the output side is called logical data.
Internal variable
If an internal variable is locked, its logical data will no longer be overwritten with the value of the
physical data. The value obtained by reading the internal variable is fixed with the value of logical
data. The value of the logical data matches the value of the physical data when locked.
SEE
ALSO For more information about acknowledging diagnostic information messages, see the following:
3.2, Displaying SCS Diagnostic Information of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
Input variable
Locked status
Input module
Unlocked status
A080201E.ai
If a variable is locked
The physical data is always updated with the value actually input from the input channel.
The value of the logical data, on the other hand, is fixed to the set value because the
physical data and the logical data are disconnected. In the application logic, the value fixed
for the logical data is used, rather than the actual input value.
If a variable is not locked
When changing the data status or data value, an error will occur and the value cannot be
changed.
b y
Output variable
...
Locked status
Output module
Variable value setting Variable value setting
b y
...
...
Unlocked status
A080202E.ai
If a variable is locked
The logical output data is always updated with the value calculated by the application logic.
The value of the physical data, on the other hand, is fixed to the set value because the
physical data and the logical data are disconnected. The value fixed for the physical data
is actually output to the output channel. Note that only values in a range of -17.19 to 118.75
(%) can be set for output variables connected to AO modules. Any attempt to set a value
outside this range generates an error.
The physical data status is always updated with the value actually input from the output
channel. The value of logical data status, on the other hand, is fixed to the set value
because the physical data and the logical data are disconnected. In the application logic, the
value fixed for the logical data is used, rather than the actual input value.
If a variable is not locked
When changing the data status or data value, an error will occur and the value cannot be
changed.
x y
Physical data Logical data
Locked status
Error
x x
Physical data Logical data
If a variable is locked
The physical data is always updated with the value written from application logic. The logical
data, on the other hand, is fixed to the set value because the physical data and the logical
data are disconnected. The value set for the logical data can be obtained by reading the
value of the variable.
If a variable is not locked
When the SCS security level is Level 1, an attempt to set a value will result in an error, the
value cannot be changed. While, if the SCS security level is Level 0, setting a value will
not trigger any error. However, since the values of the internal variables in the logic are
constantly overwritten by newer values, lock the variables before setting values.
SEE
ALSO For more information about acknowledging diagnostic information messages, see the following:
3.2, Displaying SCS Diagnostic Information of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
TIP
When using a forcing function for a parameter without name or an instance without instance name, the variable
name column of the diagnostic information message will indicate its internal name assigned in the SCS Manager.
IMPORTANT
Forcing of inter-SCS safety communication data can be performed only from the Inter-SCS
Communication Lock Window. Do not perform forcing operations (lock operation, referencing
lock status, value setting) on function blocks related to inter-SCS safety communication from the
Dictionary View. Performing lock operation from the Dictionary View causes a communication
error.
SEE
ALSO For more information about the Inter-SCS Communication Lock window, see the following:
2.3, Inter-SCS Communication Lock Window of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
SENG SCS0101
SCS project of Producing side function block
SCS0101
Inter-SCS Communication Logical data Physical data
Lock Window Application logic Binding data
Data value Data value
ng
Lock
tti
se
SCS0101
e
lu
Va
Lock
Inter-SCS safety
Control bus
communication
SCS0102
Consuming side
Application logic Binding data
function block
SENG SCS0101
SCS project of
SCS0102 Producing side
Application logic Binding data
Inter-SCS Communication function block
Lock Window
Lock
SCS0101
Control bus Inter-SCS safety
communication
SCS0102
Consuming side function block
Va
lue Logical data Physical data
set
ting
Data value Data value
Application logic Binding data
ing Status Status
sett
Value
Lock
A080402E.ai
IN PD Data
OUT
Safety
information
LD
Input values are written only to The value stored in PD is set to the
LD if the function block is locked. value of the binding variable.
A080403E.ai
Error LD
Data
IN check OUT OUT
Safety information processing NR
NR
PD
OUT
NR
If a function block on the consuming side is locked, only the status of LD (Logical Data) is passed
to the application logic that is connected to the function block on the consuming side. For this
reason, if an error occurs on the communication path while the function block is locked, it is not
possible to detect the error with the application logic. Note that errors on the communication
path detected by the function block on the consuming side are notified via diagnostic information
messages even while the function block is locked. The error status is output correctly from CMER
of the SYS_DIAG function block.
Output module
Input module
internal variable
Logic Logic
Output module
Input module
WARNING
It is necessary to bypass the field control signals and separate them from the output
modules so as to prevent plant shutdown.
In online modifications of output modules, if the channel status of the module is used as a
reference by another output module, the channel of another output module may mistakenly
generate a trip signal. To prevent this, the output modules linked to the online-changed
module should be locked during online maintenance.
SEE
ALSO For more information about whether to lock or unlock the inputs or outputs, see the following:
(D) (D) On-line Change Download in Procedure for On-line Change of an Application in 5.1, Entire
Procedure of On-line Change of Application of the Engineering Guide (IM 32S01C10-21E)
WARNING
Be sure to check that LD (Logical Data) and PD (Physical Data) match when unlocking after the
completion of download operation. Unlocking in the status where LD and PD do not match may
cause nuisance tripping.
l At Off-line Download
In the case of off-line download, launch the Inter-SCS Communication Lock Window for an SCS
project receiving data from the SCS which will perform off-line download (e.g., SCS0101), and
then lock SCS0101 so as to lock the function block on the consuming side. Nuisance tripping
caused by off-line download can be prevented.
SEE
ALSO For details on Modbus slave connection, see the following:
B1, Modbus Slave Connection of the Open Interfaces (IM 32S05B10-21E)
For details on subsystem communication, see the following:
Part C, Subsystem Communication Interfaces of the Open Interfaces (IM 32S05B10-21E)
SEE
ALSO For the security management function of the SCS, see the following:
2.12, Security of the Engineering Guide (IM 32S01C10-21E)
For the operations to set SCS security levels, see the following:
1.3, Security of SCS of the Utilities and Maintenance Reference (IM 32S04B20-21E)
SENG HIS
V net
Diagnosis
System Alarms
Information
Download,
Changing
SCS FCS
Actions
RAS
funciton
Input/output
modules
B010001E.ai
Loading
Mode
Can be transferred
from all other modes
SCS stopped
B020001E.ai
SCS Diagnostic
Diagnostic System alarm display
Information Operation
information
SCS Status Display SCS Status Display
Diagnostic
SCS status information
SCS status message
SCS
Diagnostic
information Diagnostic
Error information management function
Status Processings Status
Self-diagnosis
Diagnosis
IOM FAULT
B030001E.ai
SEE
ALSO For more information about manipulation of diagnostic information messages from SCS Maintenance Support
Tool of SENG, see the following:
3.2, Displaying SCS Diagnostic Information of the Utilities and Maintenance Reference (IM 32S04B20-
21E)
SEE
ALSO For more information about system status function blocks, see the followings:
For Safety system function blocks, see the following:
C9. Safety System Function Blocks
For interference-free system function blocks, see the following:
C10. Interference-free System Function Blocks
The table below summarizes the diagnostic information messages and error notifications to the
application logic corresponding to different levels of errors that may generate in the SCS.
Table Error Levels and Notifications of Diagnostic Information Messages
Error level Diagnostic information message Notification to application logic
Diagnostic information message may not be Notification is not possible because the CPU is
Fatal error
notified because the CPU stops. stopped.
The failure location, cause of error and other
Major error The error and output status is notified.
information are notified.
A representative error state is notified, instead
The failure location, cause of error and other
Minor error of an individual error state. An application logic
information are notified.
that utilizes this notification can be created.
SEE
ALSO For details on actions taken at error occurrence, see the following:
B6, Actions Taken at Error Occurrence and Recovery Procedure
The time displayed in a diagnostic information message is the time when the SCS detected
an error. The minimum unit of time is millisecond.
The time information set for an diagnostic information message has the same high accuracy
as the time information set for SOE information.
SEE
ALSO For IOM Reports on serial communication modules, see the following:
B4.2, IOM Report of Serial Communication Modules
SEE
ALSO For the structure and operation of the IOM Report dialog box, see the following:
3.1.3, System Reports of the Utilities and Maintenance Reference (IM 32S40B20-21E)
TIP
If a bus error occurs between the input/output module and the CPU module, the CPU of the SCS will detect a
No response error with the input/output module. In such a case, this will be treated as a host side (such as the
CPU, bus between the CPU and the input/output module) failure in the input/output module. If the input/output
modules give no response to the CPU, the CPU cannot collect the error information from the input/output module.
However, once the input/output module recovers from this state, the cause of the input/output module error (No
response) detected by the CPU and the error information inside the input/output module (fallback due to the host
side error) will be displayed so that the cause of the error can be identified.
Note also that if there is an input/output module failure, HRDY OFF will be displayed as the cause of the input/
output module error detected by the CPU of the SCS, and the cause of the failure can be identified based on the
Error information inside the input/output module.
I/O Module :
Node :2
Slot :1
Type : SAI143S
IOM Model : SAI143-S03 S1U0H00-F00-
Serial No : XXXXXXXX
Channel
1 : (Channel status) (The latest channel error)
(Cause of the channel error detected by the input/output module)
2 : (Channel status) (The latest channel error)
(Cause of the channel error detected by the input/output module)
16 : (Channel status) (The latest channel error)
(Cause of the channel error detected by the input/output module)
(4 Kbyte dump display)
Input/output module
status as viewed IOM normal
IOM normal Error A Error B Error C
from the CPU (IOM recovered)
(Current status)
Error A Error C
First Error Cause 0 (Time of occurrence T1) (Time of occurrence T3)
B040101E.ai
The following information will be displayed in each of the situations shown in the figure.
Pattern (1)
This is a state where there is no input/output module error after the initial cold start of the
CPU. In this case, the current status (normal) will be displayed. The first and last error code
lines will display the time when the input/output module was started and the cause (Cause
0), respectively.
Pattern (2)
This is a state where there is an input/output module error. The current status and the
current error content, as well as the time of the first error occurrence (T1) and the first error
(Error A), will be displayed. The last error will not be displayed. (The last error code line will
not be displayed.)
Pattern (3)
This is a state where the input/output module has recovered from the error. The current
status (normal), the time of the first error occurrence (T1), the first error (Error A), the time of
recovery (T2), and the last error (Error B) will be displayed.
Pattern (4)
This is a state where there is an input/output module error. The time of the first error
occurrence (T3) and the first error (Error C) will be displayed.
*1: The channel status during IOM Failure is the status right before the IOM fails.
*2: If the IOM failure is caused by the abnormality of a channel, the error of the channel will be displayed in IOM Report.
Example 1: Channel Failed
1: IOP+
2: Ch Fail
Open Circuit (0x0401 5561)
Example 2: Channel Recovered
3: Normal (21/6/2005 12:50:56 Last Error : IOP+)
4: Normal (21/6/2005 12:50:56 Last Error : Ch Fail)
Open Circuit (0x0401 5561)
TIP
The channel status and the last error of a pair of dual-redundantly configurated input/output modules will be
collected from the active input/output module. If the input/output module is placed in a redundant configuration,
read the descriptions regarding the IOM Report of the active input/output module for details.
l Display Format
Category of input/output module errors Category of causes of errors
*1: For a channel failure, the error codes and the statuses of failures vary depending on whether the input/output module is in the
redundant configuration or non-redundant configuration.
The upper error code is for a redundantly configured I/O module, while the lower error code is for a non-redundantly configured
I/O module.
If the input/output module is in a redundant configuration, this error will be an IOM Fail error. In a non-redundant configuration,
the error will occur only to the failed channel.
*2: Code xx07 5507 errors may occur upon input of a signal value at a level between ON and OFF or due to chattering.
SEE
ALSO For the allowable output resistance of the analog output module, refer to Analog I/O Modules (for ProSafe-RS)
(GS 32S06K30-01E).
*1: For a channel failure, the error codes and the statuses of failures vary depending on whether the input/output module is in the
redundant configuration or non-redundant configuration.
The upper error code is for a redundantly configured I/O module, while the lower error code is for a non-redundantly configured
I/O module.
If the input/output module is in a redundant configuration, this error will be an IOM Fail error. In a non-redundant configuration,
the error will occur only to the failed channel.
SEE
ALSO If the I/O module is non-redundantly configured, as for the cause of the channel error, error with code 04xx xxxx
explained in the Input/Output Module Hardware Failure section will be displayed as the cause of the channel error
detected by the input/output module.
For the cause of the channel error, see the following:
Input/Output Module Hardware Failure in Error Information inside the Input/Output Module
TIP
Information of the specified communication module is displayed even when the module is configured as a
redundant module.
I/O Module:
Node: 2
Slot: 4
Type: ALR111
IOM Model: ALR111-S03 S0U0H0-- F0--
Serial No: XXXXXXXX
Communication Status
1 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
11 0000 A3B0 A3B0 A3B0 0000 0001 0001 0001 0001 0001
.
.
(4-kbyte dump display)
In the above example, communication definitions 1 to 11 indicate a normal status, while
communication definitions 12 to 14 indicate an A3B0 error. After the communication definition 16,
there is no communication definition or corresponding communication is not performed.
SEE
ALSO For the Diagnostic information messages, see the following:
No. 0081 of 3.1, Safety Control Station Error Occurrence and Recovery Messages of the Messages (IM
32S02B10-21E)
For the communication error codes displayed under Communication Status, see the manual for the
connected Modbus system and the following:
Communication Error Code in C3.1, Communication Specifications of the Open Interfaces (IM
32S05B10-21E)
SEE
ALSO For more information about the operating mode, see the following:
B2, Operating Mode
l Manual Restart
An SCS restarts when the restart switch of the CPU module is pressed or the user performs SCS
restart operation from SCS Manager of the SENG.
TIP
After starting SCS, the operation requests from the SENG and Workbench will be ignored until the
operating mode of the SCS changes to Waiting mode.
The same error will occur to the communications with FCS or HIS for the CENTUM integration as well
as Modbus slave communication. The operating mode of the SCS can be checked on the SCS State
Management Window or identified through the LED of the SCS CPU module.
A diagnostic information message notifying a failure/recovery may generate twice when the SCS is
restarted. This dose not present any problem in practical operations or on safety.
Moreover, when the SCS is started, data saved in the memory with battery backup may remain
without being initialized. This battery backup memory can hold data for approximately 300 hours
even if the power supply to the SCS is stopped. If the data is lost, it will be reset to the initialized
status.
The following are examples of data stored in the battery backup memory.
System log information
Diagnostic information (200)
SOE data log information (1000)
SEE
ALSO For more information about system error detection by the self-diagnostic function, see the following:
B3, Diagnostic Management Function and Diagnostic Information Message
l Shutdown Operations
The shutdown operations fix the output status from an SCS. There are the following three types
of operations:
Shutdown executed by a user-defined application logic
Shutdown where the CPU fixes the output values of areas with failures
Shutdown executed by an output module when it detects an error in the host system (CPU)
When a fatal error occurs, the CPU stops and all output modules shut down; this is called all
output shutdown.
Tip
The descriptions in the later chapters will have the explanations regarding the tight-shut values may become the
output values of the analog output modules if the [Tight-Shut/Full-Open] is enabled on the I/O Parameter builder.
However, if the [Tight-Shut/Full-Open] is disabled on the I/O Parameter builder, the output value of the module
becomes the default initial value upon power-on instead of the tight-shut value.
SEE
ALSO For more information about tight-shut/full-open and default initial value upon power-on, see the following:
Tight-shut/Full-open in Items Set for Each Channel (Analog Output) in A4.5, Items Set for Analog
Outputs
n Recovery Procedure
The user should perform the output enable operation from the SENG after confirming that all
output modules have been started successfully. Once the output enable operation is performed,
output values of the application logic are output to the field. When all outputs are placed in the
Output Enable status, the operating mode shifts to the Running mode.
User operation Start supplying power Output enable operation
n Recovery Procedure
In order to recover from an error occurred in the CPU module, the CPU module replacement may
or may not be necessary.
SEE
ALSO For the CPU module replacement procedure, see the following:
7.2.1, Maintenance for ProSafe-RS Equipment of the Engineering Guide (IM 32S01C10-21E)
The figure below illustrates the output values from the SCS after the CPU module has been
replaced, based on a single CPU module configuration.
Start of master
CPU
User operation database off-line
replacement Output enable operation
download
Completion of
download to input
/output modules
*1: In the master database off-line download, configuration information is downloaded to the I/O modules.
*2: 0 for DO modules, and the tight-shut value for AO modules.
Figure Recovery after CPU Module Replacement
Output from
Fail-safe value Result of application logic processing
output modules
B060103E.ai
n Off-line Download
If you perform off-line download to the running SCS, the CPU stops temporarily. Also, IOM
download is performed to all I/O modules. Once an off-line download is started, the output values
from output modules will conform to the Figure Recovery after CPU Module Replacement.
IMPORTANT
The purpose of this function is to temporarily avoid the error conditions of SCS. If an abnormal
calculation occurs, review the application logic as soon as possible and modify the logic such that
the abnormal calculation will not recur.
SEE
ALSO For more information about how to specify the behavior at abnormal calculation with the SCS Constants Builder,
see the following:
3.1.3, SCS Constants Builder of the Engineering Reference (IM 32S04B10-21E)
If SCS Continues is specified as the behavior at abnormal calculation, the SCS will not fail even
if any of the abnormal calculation below occurs, and the SCS continues the operation.
Division by zero
Access to the outside of an array
Overflow in floating-point calculation
Overflow in casting
l Occurrence Conditions
The denominator is zero in a division of DINT or REAL type data.
l Occurrence Conditions
An index of an array variable points to the outside of the array.
l Occurrence Conditions
An overflow occurs in calculation between REAL type operands (*1).
*1: An overflow in integer calculation is not regarded as abnormal calculation.
n Overflow in Casting
An overflow in casting occurs under the following conditions and is processed as follows.
l Occurrence Conditions
When casting REAL type data to BOOL, DINT or TIME type, the resultant value exceeds the
maximum value that can be expressed by the variable.
The POU (program) where the calculation error occurred does not stop but operates until the
end.
l SCS Processing at Error Occurrence when SCS Continues the Control (Details)
Casting from REAL type variable to DINT type
When casting a value of a REAL type variable to DINT type using the ANY_TO_DINT
operator, if the original value is greater than the maximum value that can be expressed by
DINT type, the calculation result is replaced by the maximum DINT value (the maximum
negative DINT value if the original value is negative).
Casting from REAL type variable to TIME type variable
When casting a value of a REAL type variable to TIME type using the ANY_TO_TIME
operator, if the original value is greater than the maximum value that can be expressed as
an unsigned 32-bit integer, the calculation result is replaced by the maximum value of an
unsigned 32-bit integer. Although the TIME type can express up to 24 hours, truncation
is not performed immediately when an overflow occurs; truncation is performed in the
subsequent arithmetic calculation. (The TIME type does not take a negative value, but if
a negative value is assigned in ANY_TO_TIME, the value is converted to a signed 32-bit
integer once and then treated as TIME type keeping the bit sequence.)
SEE
ALSO For more information about the diagnostic information messages, see the following:
No. 4145 Abnormal calculation occurred of the Messages (IM 32S02B10-21E)
SEE
ALSO For more information about the diagnostic information messages, see the following:
No. 4146 Recovery from abnormal calculation of the Messages (IM 32S02B10-21E)
SEE
ALSO For more information about abnormal calculation occurrence in test functions, see the following in the ProSafe-
RS System Test Reference (IM 32S04B30-21E):
n Debug and Test in 2, Logic Simulation Test Operations
n Other Differences in Operations between SCS Simulator and Actual SCS in 3.3.1, Operations Unique
to SCS Simulators
SEE
ALSO For more information about items to be defined in I/O Parameter Builder, see the followings:
A4.3, Common Setting Items for Process Data Inputs and Outputs
A4.4, Items Set for Analog Inputs
A4.5, Items Set for Analog Outputs
A4.6, Items Set for Discrete Inputs
A4.7, Items Set for Discrete Outputs
SEE
ALSO For the procedures of IOM download and output enable operation, see the following:
3.1.7, IOM Download of the Utilities and Maintenance Reference (IM 32S04B20-21E)
3.1.6, Output Enable Operation of the Utilities and Maintenance Reference (IM 32S04B20-21E)
n Recovery Procedure
Investigate the causes of the failure and replace the input module. When you perform IOM
download from the SENG, the CPU starts up the input module. Once the input value is acquired
normally, the data status returns to GOOD.
User operation Module replacement IOM download
Logical 1
BAD GOOD
data status 0
Logical
data value Input value at error occurrence Identical to the physical value
Physical 1
BAD GOOD
data status 0
Physical
(*1) Field value
data value
B060201E.ai
*1: The value varies with the input module type and status.
Figure Input Module Error
Logic
Input value at
error occurrence
Fault Logic
Action
Action
B060202E.ai
Error notification
A channel error is notified via a diagnostic information message (alarm class 1). However,
the SCS State Management Window of the SENG and the Status Display view of the HIS
display the module where channel error has occurred in the color that indicates normal.
n Recovery Procedure
The type of recovery procedure to be used depends on whether or not the error occurred on the
module side.
1
Logical
data status 0 BAD Hold GOOD
Physical
(*1) Field value
data value
Logical 1
GOOD Hold GOOD
data status 0
Logical
Physical data value Hold Physical data value
data value
Normal channel
Physical 1
GOOD BAD GOOD
data status
0
Physical
Field value (*1) Field value
data value
B060203E.ai
*1: The value varies with the input module type and status.
Figure Input Module Replacement (with Locking Operation)
SEE
ALSO For more information about locking input variables, see the following:
A8, Forcing
Output module
I/O driver
Logical data Physical data
CH1
Output CH2
Application shutoff switch
logic CH3
Data
update
B060204E.ai
n Recovery Procedure
1. Investigate the cause of the failure and replace the output module.
If a system function block for output status display is used, the failure location can be
checked.
2. Perform IOM download from the SCS Maintenance Support Tool of the SENG. After the
IOM download, the CPU performs startup processing of the output module. If the startup
processing has been completed successfully, the output module is recognized as normal
and data update starts. After the module returns to normal, 0 is output for DO modules,
while the tight-shut value is output for AO modules, from all channels of the output modules.
3. Test the output module.
4. Perform the output enable operation from the SCS Maintenance Support Tool of the SENG.
Output values of the application logic will be output.
Once all output channels are placed in the Output Enable status, the operating mode shifts
to the Running mode.
The figure below illustrates the flow from a failure of an output module to the recovery.
Module IOM Output
User operation
replacement download enable operation The logical data value is
set to the result of the
application logic processing.
1
Logical data status BAD GOOD
0
1
Physical data status BAD GOOD
0
Logic
Fault
B060206E.ai
SEE
ALSO For more information about function blocks for system status indication, see the following:
C9, Safety System Function Blocks
The operation and recovery procedure for the case when an overload state has occurred
to an SDV526 module while it is outputting ON signals will be explained separately from
those for other output channel errors.
SEE
ALSO For detailed error information provided in the IOM Report dialog box, see the following:
B4.1, IOM Report of AIO/DIO Modules
n Recovery Procedure
If a channel error occurred, check the following in the SCS State Management Window and IOM
Report dialog box in the SCS Maintenance Support Tool to determine an appropriate recovery
measure.
Has the Output Shutoff switch been activated? Does the error concern only one channel?
Is it a hardware failure in the module or an error on the field side?
l Single Channel Errors (Disconnection and Other Errors on the Field Side)
1. Investigate the cause of failure and remove it so that the field can recover from the failure.
When the output module recovers, a recovery message is output and the fail-safe value,
which was defined by the user in advance, is output from the relevant output channel.
2. After confirming that the output module has recovered to normal, perform the output enable
operation from SCS Maintenance Support Tool of the SENG.
The result of the application logic processing is output.
User operation Complete recovery Output enable
of area with a failure operation The logical data value is
set to the result of the
application logic processing.
Logical 1
data status BAD GOOD
0
Physical
Faulty channel Fail-safe value Logical data value
data value
Physical 1
data status BAD GOOD
0
Logical 1
BAD GOOD
data status 0
Faulty Physical
Fail-safe value (*3) Logical data value
channel data value
Physical 1
BAD GOOD
data status 0
Logical 1
data status GOOD
0
Physical 1
data status GOOD BAD GOOD
0
Output from normal channel Physical data value (*2) Physical data value
B060207E.ai
*1: Fail-safe value (This value may be set to 0 for DO modules and 0.0 [mA] for AO modules, depending on the failure condition.)
*2: 0 for DO modules, and 0.0 [mA] for AO modules.
*3: 0 for DO modules, and the tight-shut value for AO modules.
Figure Recovery from Channel Errors (with Module Replacement)
SEE
ALSO For the recovery procedure from channel hardware failures, see the following:
In the Case of Errors on a Single Channel (Module Channel Hardware Failure)
For the recovery procedure from errors on the field side, see the following:
Single Channel Errors (Disconnection and Other Errors on the Field Side)
Check the SCS State Management Window and if the module is shown in blue, the output
module is in the startup wait status. In this case, perform the following recovery procedure.
1. Investigate the cause of the failure and recover the field side.
2. When the recovery procedure has completed, perform the Start output module from the
SCS Maintenance Support Tool of the SENG.
The CPU performs startup processing of the output module. When the output module
recovers to normal status, the data status returns to normal.
3. Perform the output enable operation from the SCS Maintenance Support Tool of the SENG.
Output values of the application logic will be output.
SEE
ALSO For details on the Start output module, see the following:
Starting Output Modules of 3.1.6, Output Enable Operation of the Utilities and Maintenance
Reference (IM 32S04B20-21E)
l Actions Taken for the Active Module in Redundant Configuration and the
Module in Non-Redundant Configuration
1. If an overload state is detected only in the active module of redundant configuration, the
control right is transferred to the standby module and the operation continues (*1). If an
overload state is detected on both modules, the standby module goes to IOM Fail and the
control right is not transferred.
*1: In this case, recover the error module that has become a standby module by carrying out the recovery procedure for a standby
module.
2. The module sets the output signal of the error channel to OFF, and the channel goes to an
Output Disable status.
3. The channel is released from the error but it remains in the Output Disable status.
Recovery Procedure
1. Clear the cause of overload state to recover the field device.
2. Use the SCS maintenance support tool on SENG and perform the output enable operation.
This allows the output value of the application logic to be output.
Recovery Procedure
1. Clear the cause of overload state to recover the field device.
2. Use the SCS maintenance support tool on SENG and perform the output module startup
operation. The module starts up and operates as a standby module.
SEE
ALSO For the actions taken at error occurrence when an optical ESB bus repeater is used, see the following:
B6.2.6 Actions Taken at Error Occurrence for Optical ESB Bus Repeater Devices
l CPU processing
The input value at error occurrence is set for input variables corresponding to all the input
channels that do not respond.
The fail-safe value is set for the physical data of output variables corresponding to all the
output channels that do not respond, and they are placed in the Output Disable status.
The input value at error occurrence set for the input variables and the fail-safe value set for
the output variables are specified in I/O Parameter Builder.
The CPU stops updating data of the relevant output module.
SEE
ALSO For more information about items defined in I/O Parameter Builder, see the followings:
A4.3, Common Setting Items for Process Data Inputs and Outputs
A4.4, Items Set for Analog Inputs
A4.5, Items Set for Analog Outputs
A4.6, Items Set for Discrete Inputs
A4.7, Items Set for Discrete Outputs
l Error notification
A channel error is notified via a diagnostic information message (alarm class 1). The data
status of all the channels is set to BAD.
When a node encounters an error, a diagnostic information message regarding the node
error will be generated.
When the node returns to normal, a diagnostic information message (alarm class 1) is
notified to indicate recovery from the I/O module error.
n Recovery Procedure
In order to make an output of an output module recover after handling a hardware failure, it is
necessary to perform the output enable operation from SCS Maintenance Support Tool of the
SENG.
User operation Complete recovery Output enable
of area with a failure operation The logical data value is
set to the result of the
application logic processing
Logical 1
BAD GOOD
data status 0
All channels of an output
module connected to Physical
Fail-safe value Logical data value
an area with a failure data value
Physical 1
BAD GOOD
data status 0
TIP
Input modules resume using input values from the field and their data status becomes GOOD once the cause of
failure is removed.
SEE
ALSO For the recovery measure to be taken at errors of an optical ESB bus repeater, see the following:
Recovery Procedure in B6.2.5, Actions Taken at Errors between CPU and Input/Output Module and
Recovery Procedure
SNT10D
S S S S S S
N N N N N N
T T T T T T
4 4 4 4 4 4 P P
0 0 0 0 0 0 S S
1 1 1 1 1 1 U U
Node2 Node4
S S S S S S S S
I I I I I I N N S S I I I I I I N N S S
O O O O O O T T B B O O O O O O T T B B
M M M M M M 5 5 4 4 P P M M M M M M 5 5 4 4 P P
0 0 0 0 S S 0 0 0 0 S S
1 1 1 1 U U 1 1 1 1 U U
Node3
S S
I I I I I I I I S S
O O O O O O O O B B
M M M M M M M M 4 4 P P
0 0 S S
1 1 U U
: Fiber-optic cable
B060211E.ai
TIP
A diagnostic information message indicating an ESB bus error (Message No. 0063) is issued only when an error
occurs in all I/O nodes excluding the CPU node. In a configuration where optical ESB bus repeater modules are
used to provide multiple ESB bus lines, this diagnostic information message (Message No. 0063) is not issued in
the event of an error in only one line. For example, assume a system configuration that partially uses optical ESB
bus repeater modules. Even if errors are occurred in bus 1 of all I/O nodes those are connected to the ESB bus
but are not connected to fiber-optics, the aforementioned diagnostic information message indicating an ESB bus
error (Message No. 0063) is not issued.
The same rule applies when the SEC402 is used to connect nodes to both the upper and lower sides. For
example, the diagnostic information message No. 0063 is not notified if errors occurred in only one side of the
duplicated buses of all I/O nodes connected via the upper connector.
Installing Optical ESB Bus Repeater Modules in a Unit for Optical Bus
Repeater Module
If optical ESB bus repeater modules are installed in a unit for optical bus repeater module
(SNT10D), set hardware setting switch [1] (installation unit setting DIP switch 1) on the optical
ESB bus repeater modules to 0: Installation in unit for optical bus repeater module. When the
switch is set this way, an error in one of the SNT10D power-supply modules will be notified as a
failure of the I/O nodes connected via the optical ESB bus repeater modules.
If an error occurs in one of the power-supply modules of the SNT10D in which the
optical ESB bus repeater modules are installed, the optical ESB bus repeater modules
of the corresponding side stop communicating. If the error occurred in the left power-
supply module, the optical ESB bus repeater modules installed in odd-number slots stop
communication. If the error occurred in the right power-supply module, the optical ESB
bus repeater modules installed in even-number slots stop communication. Because
communication stops from the optical ESB bus repeater module on one side, diagnostic
information messages indicating the SSB401 error (Message No. 0065) for all I/O nodes
connected via the applicable optical ESB bus repeater modules are notified.
In the event of an error in both of the power-supply modules of the SNT10D in which the
optical ESB bus repeater modules are installed, an error occurs in all I/O nodes connected
via the optical ESB bus repeater modules installed in the applicable SNT10D.
Installing Optical ESB Bus Repeater Modules in a CPU Node or I/O Node
If optical ESB bus repeater modules are installed in a CPU or I/O node, set hardware setting
switch [1] (installation unit setting DIP switch 1) to 1: Installation in node (safety control unit or
safety node unit).
If SW [1] is set to 1, the optical ESB bus repeater modules will continue to operate without
being affected, even if an error occurs in one of the power-supply modules of the node in
which the optical ESB bus repeater modules are installed.
In the event of an error in both of the power supply modules of the node in which the optical
ESB bus repeater modules are installed, an error occurs in this node and all I/O nodes
connected via the applicable optical ESB bus repeater modules.
IMPORTANT
When installing optical ESB bus repeater modules in a SNT10D, set the installation unit
setting DIP switch 1 to 0. If this switch is set to 1, an error in one of the power-supply
modules of the SNT10D will not be notified as a failure of the I/O nodes connected via the
optical ESB bus repeater modules.
When installing optical ESB bus repeater modules in a CPU or I/O node, set the installation
unit setting DIP switch 1 to 1. If this switch is set to 0, an error occurring in one of the
power-supply modules of the CPU or I/O will cause an error in the optical ESB bus repeater
modules on one side.
n CPU Module
The CPU module on the standby side performs the same control processing as the
control side even while it is in the standby status. For this reason, it is possible to take over
outputting data immediately after the control right is switched. Moreover, the operating mode
of the SCS does not change.
Only the CPU on the control side accesses the hardware composing the SCS and the CPU
on the standby side always sets the equivalent value as the processing result. Therefore,
the CPU modules on both sides always perform processing using the same data.
In redundant configuration, if the CPU module on the standby side is not in the STBY status
and the control right cannot be switched, the same operation as single configuration CPU
module is performed.
SOE data related to discrete inputs might be lost when the control right is switched between
the CPU modules.
CPU modules of the SCSP2 may not update data from analog input/discrete input modules
in the scan executed immediately after switching the CPU control right, but use data
read in the previous scan. Data read in 1 or 2 scans earlier may be used for sub-system
communication modules.
n Input/Output Modules
In an SCS, it is possible to mount input/output modules of the same type in two adjacent slots (*1)
to make them redundant. In the case of redundant configuration, one side becomes the control
side and the other becomes the standby side. Switching of the control right is performed by input/
output modules. The switching has no influence on the application logic.
*1: An odd-numbered slot and the even-numbered slot obtained by adding 1 to the odd slot number
SEE
ALSO For more information about redundant communication modules, see the following:
2.16, Connection with Other Systems via Serial Communication of the Engineering Guide (IM 32S01C10-
21E)
n V net Communication
The SCS V net communication is redundant. The communication couplers are also redundant.
The CPU has a communication interface that supports the redundant V net. An SCS performs
communication while switching the bus to be used at regular intervals.
n Vnet/IP Communication
Vnet/IP is redundant. Independent subnets using bus 1 and bus 2 comprise redundant buses.
If both buses are normal, bus 1 is used for control communication, while bus 2 is used for open
communication. If a communication error occurs in bus 1, bus 2 is used to perform control
communication.
SEE
ALSO For details on Vnet/IP communication, see the following:
A1, Overview of Vnet/IP Network of the ProSafe-RS Vnet/IP (IM 32S56H10-21E)
SEE
ALSO For details on the actions taken at errors of optical ESB bus repeater devices, see the following:
B6.2.6, Actions Taken at Error Occurrence for Optical ESB Bus Repeater Devices
n SB Bus
The SB bus is a backboard bus that connects the SSB401 and each input/output module. The
SB buses are redundant. Since each bus is connected to one SSB401 in a one-to-one fashion,
the SB bus is switched whenever an SSB401 is switched.
If an error occurs in one SB bus, the error is notified to the user via a diagnostic information
message. If both buses fail, the error is treated as a node failure.
In the case of one-side failure of an SB bus, only the ESB bus connected to the normal SB
bus is used.
n CPU Status
In order to show the status of a redundant configuration, it is necessary to indicate the status of
each CPU separately. The operating status of the CPU is called the CPU status.
The CPU status indicates the operating status of the CPU.
The processing of the SCS references the CPU status as necessary. The user can check
the CPU status via the CPUs LED, the SCS State Management window of the SENG, and
the Status Display view of HIS.
If an error occurs in the standby CPU, the FAIL status is notified to the application logic via a
system block.
The figure below illustrates the CPU status shift. Note that in order to explain the CPU status,
the operating modes it can shift to from the Initial mode are called CTRL and STBY. These
indicate whether the CPU has the control right and are specific to the redundant status, i.e., not
related to the operating mode.
CPU Fail
CTRL
STBY
CPU Fail
B070201E.ai
(a)
(e)
FAIL CTRL control side
CTRL
FAIL CPU status
FAIL
stand-by side
STBY
CPU status
Single Operation
B070202E.ai
l APC Status
The APC status refers to the status where the data in the CPU memory is being copied from the
control side to the standby side. The APC status can be checked by the LED on the CPU, the
SCS Status Display window of the SENG or the Status Display view on the HIS. The start and
end of the APC status are notified via a diagnostic information message.
SEE
ALSO For more information about specification methods in the SCS Constants Builder, see the following:
3.1.3, SCS Constants Builder of the Engineering Reference (IM 32S04B10-21E)
IMPORTANT
Do not remove and put back the applicable AIO/DIO module while automatic IOM download
is being executed. If it is removed and put back, a major failure may occur in the module (the
STATUS LED of the module becomes OFF).
Automatic download is completed in approximately 30 seconds after inserting the module on the
standby side, and the diagnostic information message indicating completion of IOM download
(No. 0476) is output. If you need to remove and put back a module, check the diagnostic
information message indicating completion of IOM download in the Diagnostic Information
window of the SCS Maintenance Support Tool before doing so.
If a major failure occurs due to erroneous removal and reinsertion, perform IOM download
manually to the applicable AIO/DIO module, and then remove and reinsert the module after the
completion.
Automatic IOM download is not executed on AIO/DIO modules to which online change
download of input/output parameters or manual IOM download are being executed.
However, automatic IOM download to a different module is executed in parallel.
If it is attempted to execute online change download of input/output parameters or manual
IOM download on the applicable AIO/DIO modules for which automatic IOM download is
being executed, an error occurs in the manual download.
SEE
ALSO For more information about POUs, see the following of the Workbench in the Workbench Users Guide:
POUs (Program Organization Units) of Link Architecture View
For more information about the ProSafe-RS applicable POU types and notices on using the POUs, see the
following:
2.4, Overview of POU of the Engineering Guide (IM 32S01C10-21E)
SEE
ALSO For more details about Structured Text, see the following:
2.5, Structured Text of the Engineering Guide (IM 32C01C10-21E)
n Common Constants
In ProSafe-RS, the following constants have been defined in advance. These constants can be
used when creating an application for the purpose of making the application easier to read.
Users can add constants as required. Do not change the following constants, however.
Table Pre-defined Constants
Name Value Description
TRIP_NONE 0 Do not regard signals as tripping signals
TRIP_OFF 1 Regard the falling edge of a signal (TRUE to FALSE) as a tripping signal
TRIP_ON 2 Regard the rising edge of a signal (FALSE to TRUE) as a tripping signal
SEE
ALSO For how to create user-defined FUs and FBs, see the following of the Workbench in the Workbench Users
Guide:
POUs (Program Organization Units) of Link Architecture View
SEE
ALSO For the information about safety functions not explained in this chapter, see the following of the Workbench in
the Workbench Users Guide:
Standard Functions of Language Reference
SELC
IN1
IN2
IN3
IN4 Q
C020101E.ai
Figure MUXBOOL4
n Arguments
Table Arguments of MUXBOOL4
IN/OUT Arguments Data type Description
SELC DINT Selector value (0 to 3)
IN1 BOOL Input value 1
IN IN2 BOOL Input value 2
IN3 BOOL Input value 3
IN4 BOOL Input value 4
Output value
= Input value 1 (SELC = 0)
= Input value 2 (SELC = 1)
OUT Q BOOL
= Input value 3 (SELC = 2)
= Input value 4 (SELC = 3)
= FALSE (SELC is a value other than the above)
n Description
The MUXBOOL4 function is a 4-input multiplexer for BOOL-type data. It selects one value out of
four input values.
If a value other than 0 to 3 is specified for SELC, the output value becomes FALSE.
SELC
IN1
IN2
IN3
IN4
IN5
Q
IN6
IN7
IN8
C020201E.ai
Figure MUXBOOL8
n Arguments
Table Arguments of MUXBOOL8
IN/OUT Arguments Data type Description
SELC DINT Selector value (0 to 7)
IN1 BOOL Input value 1
IN IN2 BOOL Input value 2
:
IN8 BOOL Input value 8
Output value
= Input value 1 (SELC = 0)
= Input value 2 (SELC = 1)
OUT Q BOOL
:
= Input value 8 (SELC = 7)
= FALSE (SELC is a value other than the above)
n Description
The MUXBOOL8 function is an 8-input multiplexer for BOOL-type data. It selects one value out of
eight input values.
If a value other than 0 to 7 is specified for SELC, the output value becomes FALSE.
SELC
IN1
IN2
IN3
IN4 Q
C020301E.ai
Figure MUXREAL4
n Arguments
Table Arguments of MUXREAL4
IN/OUT Arguments Data type Description
SELC DINT Selector value (0 to 3)
IN1 REAL Input value 1
IN IN2 REAL Input value 2
IN3 REAL Input value 3
IN4 REAL Input value 4
Output value
= Input value 1 (SELC = 0)
= Input value 2 (SELC = 1)
OUT Q REAL
= Input value 3 (SELC = 2)
= Input value 4 (SELC = 3)
= 0.0 (SELC is a value other than the above)
n Description
The MUXREAL4 function is a 4-input multiplexer for real number-type data. It selects one value
out of four input values.
If a value other than 0 to 3 is specified for SELC, the output value becomes 0.0.
SELC
IN1
IN2
IN3
IN4
IN5
IN6 Q
IN7
IN8
C020401E.ai
Figure MUXREAL8
n Arguments
Table Arguments of MUXREAL8
IN/OUT Arguments Data type Description
SELC DINT Selector value (0 to 7)
IN1 REAL Input value 1
IN IN2 REAL Input value 2
:
IN8 REAL Input value 8
Output value
= Input value 1 (SELC = 0)
= Input value 2 (SELC = 1)
OUT Q REAL
:
= Input value 8 (SELC = 7)
= 0.0 (SELC is a value other than the above)
n Description
The MUXREAL8 function is an 8-input multiplexer for real number-type data. It selects one value
out of eight input values.
If a value other than 0 to 7 is specified for SELC, the output value becomes 0.0.
IN OUT
SH
SL
C020501E.ai
Figure SCALER
n Arguments
Table Arguments of SCALER
IN/OUT Arguments Data type Description
IN REAL Input value (a value in the range from 0.0 to 100.0)
IN SH REAL Scale high limit value (output value when input value = 100 [%])
SL REAL Scale low limit value (output value when input value = 0 [%])
OUT OUT REAL Output value
n Description
The SCALER function converts input data (0 to 100%) to the specified scale.
The calculation formula of OUT is as follows:
IN (SH - SL)
OUT = + SL
100.0
C020502E.ai
n Remarks
The OUT calculation formula is the same even if SH < SL. In this case, OUT is calculated as
a linear function with a negative gradient.
Set the SH and SL values such that 32-bit floating point data overflow does not occur when
calculating the output value of OUT, by taking the possible range of IN data (-25% to 125%
in the case of analog input) into consideration.
n Example
If IN = 60.0 [%], SH = 2000.0 and SL = 1000.0, OUT = 1600.0.
OUT
SH=2000.0
OUT=1600.0
SL=1000.0
0.0
0.0 IN=60.0 100.0 IN
C020503E.ai
SEL_R
SELC
IN1
Q
IN2
C020601E.ai
Figure SEL_R
n Arguments
Table Arguments of SEL_R
IN/OUT Arguments Data type Description
SELC BOOL Selector value
IN IN1 REAL Input value 1
IN2 REAL Input value 2
Either IN1 or IN2 is output.
OUT Q REAL Input value 1 is output if SELC is FALSE.
Input value 2 is output if SELC is TRUE.
n Description
The SEL_R function is a real-number type selector.
It selects and outputs IN1 or IN2 according to the value of SELC.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
SEL_T
SELC
IN1
Q
IN2
C020701E.ai
Figure SEL_T
n Arguments
Table Arguments of SEL_T
IN/OUT Arguments Data type Description
SELC BOOL Selector value
IN IN1 TIME Input value 1
IN2 TIME Input value 2
Either IN1 or IN2 is output.
OUT Q TIME Input value 1 is output if SELC is FALSE.
Input value 2 is output if SELC is TRUE.
n Description
The SEL_T function is a TIME type selector.
It selects and outputs IN1 or IN2 according to the value of SELC.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
IB_TO_V
IN V
C020801E.ai
Figure IB_TO_V
n Arguments
Table Arguments of IB_TO_V
IN/OUT Arguments Data type Description
IN IN IO_BOOL Input value of IO_BOOL type
OUT V BOOL Data value
n Description
The IB_TO_V function acquires data values from IO_BOOL-type input values and outputs the
acquired values.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
IB_TO_S
IN STS
C020901E.ai
Figure IB_TO_S
n Arguments
Table Arguments of IB_TO_S
IN/OUT Arguments Data type Description
IN IN IO_BOOL Input value of IO_BOOL type
OUT STS BOOL Data status
n Description
The IB_TO_S function acquires data status from IO_BOOL-type input values and outputs the
acquired status.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
IR_TO_V
IN V
C021001E.ai
Figure IR_TO_V
n Arguments
Table Arguments of IR_TO_V
IN/OUT Arguments Data type Description
IN IN IO_REAL Input value of IO_REAL type
OUT V REAL Data value
n Description
The IR_TO_V function acquires data values from IO_REAL-type input values and outputs the
acquired values.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
IR_TO_S
IN STS
C021101E.ai
Figure IR_TO_S
n Arguments
Table Arguments of IR_TO_S
IN/OUT Arguments Data type Description
IN IN IO_REAL Input value of IO_REAL type
OUT STS BOOL Data status
n Description
The IR_TO_S function acquires data status from IO_REAL-type input values and outputs the
acquired status.
n Remarks
This function can be used in new SCS databases created by SENG of R1.01.30 or later.
SEE
ALSO For the information about safety function blocks not explained in this chapter, see the following of the
Workbench in the Workbench Users Guide:
Standard Function Blocks of Language Reference
REPEATTIMER
RUN Q
STF
ONT
OFFT
C030101E.ai
Figure REPEATTIMER
n Arguments
Table Arguments of REPEATTIMER
IN/OUT Arguments Data type Description
RUN BOOL Output activation switch
Start status flag
STF BOOL TRUE: Start from OFF
IN FALSE: Start from ON
ONT TIME ON period (a multiple of the scan period)
OFFT TIME OFF period (a multiple of the scan period)
OUT Q BOOL Output value
n Description
The REPEATTIMER function block executes a repeat timer function.
The REPEATTIMER function block outputs ON and OFF alternately as long as the output start
switch (RUN) is TRUE. It outputs TRUE as the output value (Q) during the period specified by the
ON period (ONT) and FALSE during the period specified by the OFF period (OFFT). The repeat
interval is the value obtained by adding the ON period and OFF period (ONT + OFFT).
If the output start switch (RUN) becomes FALSE, the output value (Q) is set to FALSE.
If STF is TRUE, the timer starts from the OFF period. If STF is FALSE, the timer starts from the
ON period.
When ONT = 500 msec, OFFT = 1000 msec and scan period = 500 msec
500
msec
RUN
C030102E.ai
Figure Relationship between the Output Start Switch (RUN) and Output Value (Q) (ONT and OFFT are
integral multiples of the scan period)
n Remarks
The ON and OFF periods must be set to integral multiples of the scan period.
The output value (Q) is calculated in each scan period and does not change until the next
scan. For this reason, if the ON/OFF period is set to a value that is not a multiple of the scan
period, the output value (Q) will switch at intervals different from the specified ON/OFF time.
(Whether the period of Q becomes longer or shorter than the specified value depends on
the timing.)
If either the ON period or OFF period is set to 0, the output does not alternate between ON
and OFF; the default value specified with STF is always output.
If the ON period is shorter than the scan period, the ON period is rounded up to the scan
period. The same rule applies to the OFF period as well.
FILTER
IN OUT
CFT
C030201E.ai
Figure FILTER
n Arguments
Table Arguments of FILTER
IN/OUT Arguments Data type Description
IN REAL Input value
IN
CFT DINT Filter number (0 to 4)
OUT OUT REAL Output value
n Description
The FILTER function block executes a first-order lag filter function.
The first-order lag filter is used to reduce noise in input signals from the process.
The FILTER function block calculates the output according to the following arithmetic expression.
Yn = (1 - ) X + Yn - 1
: Filter constant
X : Input value
Yn : Output value
Yn - 1 : Previous output value (The default value is 0.0.)
If the filter number is a value other than the ones listed above, it is treated as filter number 0.
Value IN
OUT (=0.5)
Scan period
Time
C030202E.ai
n Remarks
The time constant of the filter is determined as a combination of the filter number (filter constant)
and the scan period. The larger the filter constant, the longer it takes, and the time constant is
proportional to the scan period.
(Time constant = scan period, where is the filter constant)
1-
C030203E.ai
FILTER_S
IN OUT
CFT VAL
C030301E.ai
Figure FILTER_S
n Arguments
Table Arguments of FILTER_S
IN/OUT Arguments Data type Description
IN IO_REAL Input value (with data status)
IN
CFT DINT Filter number (0 to 4)
OUT IO_REAL Output value (with data status)
OUT
VAL REAL Output value (data value only)
n Description
The FILTER_S function block executes a first-order lag filter function.
The first-order lag filter is used to reduce noise in input signals from the process.
The data type of the input value (IN) and output value (OUT) is IO_REAL. The value of the data
status of the input value is set as the data status of the output value as is. VAL is the data value of
OUT.
A FILTER_S function block calculates the output according to the following arithmetic expression.
The value of status does not affect the output calculation.
Yn = (1 - ) X + Yn - 1
: Filter constant
X : Input value
Yn : Output value
Yn - 1 : Previous output value (The default value is 0.0.)
If the filter number is a value other than the ones listed above, it is treated as filter number 0.
Value
IN
OUT (=0.5)
Scan period
Time
C030302E.ai
n Remarks
Use the FILTER function block if the input value is a real number type. The processing is the
same.
The time constant of the filter is determined as a combination of the filter number (filter constant)
and the scan period. The larger the filter constant, the longer it takes, and the time constant is
proportional to the scan period.
(Time constant = scan period, where is the filter constant)
1-
C030303E.ai
ANLG1OO2D
IN1 OUT
IN2 NR
DEL NR1
VAL NR2
DLT DIF
C030401E.ai
Figure ANLG1OO2D
n Arguments
Table Arguments of ANLG1OO2D
IN/OUT Arguments Data type Description
IN1 IO_REAL Input value 1 (with data status, 0 to 100%)
IN2 IO_REAL Input value 2 (with data status, 0 to 100%)
Allowable range for difference. A range of allowable difference
DEL REAL
between two input values (DEL > 0; UNIT: %)
IN
Fail-safe value. The value output in case the input value is
VAL REAL
erroneous (-25.0 to 125%)
Allowable time. The time to wait for the difference between
DLT TIME the input values to converge to the allowable range (DEL) (an
integral multiple of the scan period)
OUT REAL Output value (value selected with 1oo2D, 0 to 100%)
Indicates whether or not the input value is normal
NR BOOL TRUE: Normal
FALSE: Abnormal (The fail-safe value is output.)
Indicates whether or not input value 1 (IN1) is normal
TRUE: Normal
NR1 BOOL
OUT FALSE: The data status is BAD or the difference between the
input values is larger than the allowable range.
Indicates whether or not input value 2 (IN2) is normal
TRUE: Normal
NR2 BOOL
FALSE: The data status is BAD or the difference between the
input values is larger than the allowable range.
DIF REAL Absolute value of the difference between the two input values
n Description
The ANLG1OO2D function block is a 2-input analog voter with diagnostics. It receives two inputs
with data status and determines the output value using the voting method of 1oo2D (one-out-of-
two with diagnostics). By using the ANLG1OO2D function block, it is possible to detect not only
input module failures, but also input value errors.
l Input
IN1 and IN2 are analog inputs (IO_REAL type) with data status. The ANLG1OO2D function
block examines each data status and the difference between input values IN1 and IN2, and
determines the output value (OUT).
DEL is the range of allowable difference between the two input values (DIF). Since the two
input values are measurement values of the same target, they are expected to have almost
the same value. If one of the inputs becomes erroneous, the two values have different
values and an error can be detected. If DEL is set as DEL <= 0%, as long as a difference
exists between the two inputs, no matter how small it is, the input signal will be treated as a
signal exceeds the deviation limit.
DLT is a filter value used in ANLG1OO2D function block to allow the difference between
the two input values (DIF) that exceeds the deviation limit (DEL) elapse for a specified time.
If DLT is set with 0, as soon as one input is different from another input, the fail-safe value
will be output. By setting an appropriate value for DLT, it is possible to avoid the input of
the function block becomes error over the transient noises. If the input of the function block
becomes error, the fail-safe value will be output.
VAL is the value output if the ANLG1OO2D function block judges an input error. Specify a
value in the range from -25.0 to 125% for VAL. If a value smaller than -25.0% is specified, it
is treated as -25.0%. If a value larger than 125% is specified, it is treated as 125%.
l Output
OUT is the output value created by the ANLG1OO2D function block according to the 1oo2D
vote. If the ANLG1OO2D function block considers the input to be normal, the output value
of either IN1 or IN2 is created. If the ANLG1OO2D function block considers the input to be
abnormal, the fail-safe value (VAL) is used to create the output. The initial value of OUT is
IN1.
NR is the resulting output of the ANLG1OO2D function blocks judgment of whether the
inputs are normal or abnormal. If the inputs are normal, NR is set to TRUE. If the inputs
are judged abnormal, NR is set to FALSE and OUT produces output based on the fail-safe
value (VAL).
NR1 is the resulting output of the ANLG1OO2D function blocks judgment of whether the
input value 1 (IN1) is normal or abnormal. If the data status of input value 1 (IN1) is GOOD
and the difference between the two input values (DIF) is within the acceptable range, input
value1 (IN1) is considered as normal and NR1 is set to TRUE. If input value 1 (IN1) is
considered as abnormal, NR1 is set to FALSE.
NR2 is the resulting output of the ANLG1OO2D function blocks judgment of whether input
value 2 (IN2) is normal or abnormal. The classification of normal or abnormal is the same as
for NR1.
DIF is the absolute value of the difference between input value 1 (IN1) and input value 2
(IN2). The ANLG1OO2D function block calculates the difference between the input values
regardless of each status of the input values.
If the inputs are normal, the ANLG1OO2D function block outputs the input value closer to the
previous output value. Since output value (OUT) is normal, NR is set to TRUE. Moreover, since
both input values (IN1 and IN2) are normal, both NR1 and NR2 are set to TRUE.
value
IN1
IN2
Output
value
(OUT)
DEL
DIF
time
NR,NR1,NR2 T
F
C030402E.ai
If the data status of both inputs becomes BAD, the ANLG1OO2D function block outputs the fail-
safe value (VAL). NR, NR1 and NR2 become FALSE.
The figure below shows an example of output when the data status of both inputs becomes BAD.
value
Output
value
(OUT)
IN1
IN2
Fail-safe value
(VAL)
time
T
IN1.status
F
T
IN2.status
F
T
NR
F
T
NR1
F
T
NR2
F
Scan period
C030403E.ai
Note that when the absolute value of the difference between the input values exceeds the
allowable range and the data status of the input (IN1 or IN2) becomes BAD, the time period in
which the input is BAD is not included in the calculation of time where the difference exceeds the
allowable range. If the allowable range is still exceeded when the data status of the input (IN1 or
IN2) recovers to GOOD, the elapsed time before the data status became BAD is added to the
calculation of time where the difference exceeds the allowable range.
value
IN1
Output
IN2 value
(OUT)
Fail-safe value
(VAL)
DEL
DLT
DIF
time
T
NR, NR1,NR2
F
Scan period
C030404E.ai
Figure Operation when the Difference between Input Values Exceeds the Allowable Range
n Remarks
Set values such that the input value at error occurrence in each input channel and the fail-
safe value (VAL) of the ANLG1OO2D function block match each other. This should be done
because the ANLG1OO2D function block uses the fail-safe value (VAL) rather than the input
value at error occurrence set for an input channel if the input channel becomes abnormal.
Specify an integral multiple of the scan period for the allowable time (DLT). If the specified
value is not an integral multiple of the scan period, the fail-safe value is output after a time
equivalent to the first integral multiple of the scan period has passed since DLT elapsed.
ANLGVOTER
IN1 OUT
IN2 NR
IN3 NR1
DEL DIF1
VAL NR2
DLT DIF2
NR3
DIF3
C030501E.ai
Figure ANLGVOTER
n Arguments
Table Arguments of ANLGVOTER
IN/OUT Arguments Data type Description
IN1 IO_REAL Input value 1 (with data status, 0 to 100%)
IN2 IO_REAL Input value 2 (with data status, 0 to 100%)
IN3 IO_REAL Input value 3 (with data status, 0 to 100%)
Allowable range (allowable error). Tolerant deviation between an
DEL REAL
IN input and the medium value (DEL > 0%; 0% -100%).
Fail-safe value. The value output in case the input value is
VAL REAL
erroneous (-25.0 to 125%)
Allowable time. The time to wait for the difference between
DLT TIME the input values to converge to the allowable range (DEL) (an
integral multiple of the scan period)
OUT REAL Output value (medium value selected with 2oo3, 0 to 100%)
Indicates whether or not the output value is normal
NR BOOL TRUE: Normal
FALSE: Abnormal (The fail-safe value is output.)
Indicates whether or not input value 1 (IN1) is normal
TRUE: Normal
NR1 BOOL
FALSE: The data status is BAD or the difference between the
output value and input value 1 is larger than the allowable range.
Difference between the output value (OUT) and input value 1
DIF1 REAL
(IN1)
OUT Indicates whether or not input value 2 (IN2) is normal
TRUE: Normal
NR2 BOOL
FALSE: The data status is BAD or the difference between the
output value and input value 2 is larger than the allowable range.
Difference between the output value (OUT) and input value 2
DIF2 REAL
(IN2)
Indicates whether or not input value 3 (IN3) is normal
TRUE: Normal
NR3 BOOL
FALSE: The data status is BAD or the difference between the
output value and input value 3 is larger than the allowable range.
Difference between the output value (OUT) and input value 3
DIF3 REAL
(IN3)
n Description
The ANLGVOTER function block is a 3-input analog voter. It receives three inputs with data
status and determines the medium value to be output using the voting method of 2oo3 (two-out-
of-three). By using an ANLGVOTER function block, it is possible to detect input module failures.
IN1, IN2 and IN3 are analog inputs (IO_REAL type) with data status.
DEL is the range of acceptable differences between the median value and each of the
input values. Since the three input values are measurement values of the same target, they
are expected to have almost the same value. If one of the inputs becomes erroneous, a
distinctive difference is generated between the input value and the median value so that an
error can be detected.
Input n is regarded as normal if the difference between input value INn and the median
value is as follows.
-DEL/2 DIFn +DEL/2
DIFn = INn - median value {n = 1, 2 or 3}
If DEL <= 0%, as long as a difference exists between an input and the median value, no
matter how small it is, the input signal will be treated as a signal that it has exceeded the
deviation limit.
VAL is the value output if the ANLGVOTER function block judges an input error. Specify a
value in the range from -25.0 to 125% for VAL. If a value smaller than -25.0% is specified, it
is treated as -25.0%. If a value larger than 125% is specified, it is treated as 125%.
DLT is a filter value used in ANLGVOTER function block to allow the deviation exceeds the
deviation limit (DEL) elapse for a specified time. If DLT is set with 0, as soon as the deviation
between an input and the medium value exceeds the deviation limit between an input and
the medium value, the fail-safe value will be output. By setting an appropriate value for DLT,
it is possible to avoid the input of the function block becomes error over the transient noises.
FALSE FALSE
BAD for two or more inputs Fail-safe value (VAL) FALSE
(*2) (*2)
*1: The medium value of the fail-safe value, IN2 and IN3 is output; as a result, either IN2 or IN3 is output.
*2: If the data status is GOOD only for one input, it is not possible to judge that the data value is correct; FALSE is output for NR1,
NR2 and NR3.
If the inputs are normal, the ANLGVOTER function block selects the medium value of the three
input values and calculates the difference between the medium value and each of the input
values (DIFn {n = 1, 2 and 3}). Since all DIFn values are within the allowable range (-DEL2
DIFn +DEL/2), all the input values are judged normal and the medium value is selected as
the output value (OUT). Since the normal output value (OUT) is output, NR is set to TRUE.
Moreover, since all the inputs are normal, NR1, NR2 and NR3 are set to TRUE.
Example: If IN1 = 10.0, IN2 = 12.0, IN3 = 13.0, and DEL = 6.0, the medium value becomes
12.0 (value of IN2). The difference from the medium value is: DIF1 = -2.0, DIF2 = 0.0 and DIF3
= 1.0. Since -DEL/2 DIF1 +DEL/2, IN1 is regarded as normal. Similarly, IN2 and IN3 are
also regarded as normal. The ANLGVOTER function block judges all the inputs as normal, and
outputs OUT = 12.0, NR = TRUE, NR1 = TRUE, NR 2 = TRUE and NR3 = TRUE.
Output
value
value
(OUT)
IN1
IN2
IN3
+DEL/2
DIF1
DIF2
0 time
DIF3
-DEL/2
NR,NR1,NR2,NR3 T
F
C030502E.ai
If the data status of one input becomes BAD, the ANLGVOTER function block examines the
difference between the two input values whose data status is GOOD and outputs one of them
(specifically, the medium value of the remaining two input values and the fail-safe value becomes
the output value (OUT)).
If the difference between the input values whose data status is GOOD is within the allowable
range, the output value is normal, thus NR becomes TRUE. NRn corresponding to the abnormal
input value becomes FALSE and NRm corresponding to the two normal input values become
TRUE {n, m = 1, 2 or 3}.
If the status where the difference between the input values whose data status is GOOD exceeds
the allowable range (|difference between GOOD input values| > DEL) continues longer than
the allowable time (DLT), the ANLGVOTER function block judges that the inputs have become
abnormal and outputs the fail-safe value (VAL). FALSE is output for NR and NRn {n = 1, 2 and 3}.
If the data status of two or more inputs is BAD, the ANLGVOTER function block judges that a
normal value cannot be output and outputs the fail-safe value (VAL).
Since the output value is abnormal, NR becomes FALSE. Moreover, all NRn becomes FALSE {n
= 1, 2 and 3}.
value
Output
value
IN1 (OUT)
IN2
IN3
VAL
time
T
IN1.status
F
T
IN2.status
F
T
NR
F
NR1 T
F
IN3.status and NR3
T are omitted.
NR2
F
C030503E.ai
If the status where the difference between only one input value and the medium value (DIFn)
exceeds the allowable range (|DIFn| > DEL/2) continues longer than the allowable time (DLT),
the ANLGVOTER function block judges that only the input value in question is erroneous and
outputs the medium value.
NRn corresponding to the input value (INn) that is significantly different from the medium value
becomes FALSE. Since the output and other input values are normal, NR and NRm become
TRUE {n, m = 1, 2, 3 and n m}.
If the status where the difference between the medium value and two out of the three input values
(DIFn) {n = 1, 2, or 3} exceeds the allowable range (|DIFn| > DEL/2) continues longer than the
allowable time (DLT), the ANLGVOTER function block outputs the fail-safe value (VAL) {n = 1, 2
or 3}.
Since the output and all input values are abnormal, NR, NR1, NR2 and NR3 become FALSE.
Note that when the difference between the input values and the medium value (DIFn) exceeds
the allowable range and the data status of the input values (INn) becomes BAD, the time period
in which the input is BAD is not included in the calculation of time where the difference exceeds
the allowable range. If the allowable range is still exceeded when the data status of the input
(INn) recovers to GOOD, the elapsed time before the data status became BAD is added to the
calculation of time where the difference exceeds the allowable range.
value
IN1
IN2 Output
value
IN3 (OUT)
VAL
DLT
+DEL/2
DIF1
DIF2
0 time
DIF3
-DEL/2
DLT
NR, NR1,NR2 T
F
NR3 T
F
C030504E.ai
Figure Operation when the Difference between Input Values Exceeds the Allowable Range
n Remarks
Set values such that the input value at error occurrence in each input channel and the
fail-safe value (VAL) of the ANLGVOTER function block match each other. This should be
done because the ANLGVOTER function block uses VAL rather than the input value at error
occurrence set for an input channel if the input channel becomes abnormal.
Specify an integral multiple of the scan period for the allowable time (DLT). If the specified
value is not an integral multiple of the scan period, the fail-safe value is output after a time
equivalent to the first integral multiple of the scan period has passed since DLT elapsed.
BOOLVOTER
IN1 Q
IN2 NR
IN3 NR1
VAL NR2
NR3
C030601E.ai
Figure BOOLVOTER
n Arguments
Table Arguments of BOOLVOTER
IN/OUT Arguments Data type Description
IN1 IO_BOOL Input value 1 (with data status)
IN2 IO_BOOL Input value 2 (with data status)
IN IN3 IO_BOOL Input value 3 (with data status)
Fail-safe value. The value output in case the data status of input
VAL BOOL
value is not GOOD.
Q BOOL Output value (value selected with 2oo3)
Indicates whether or not output value is normal
NR BOOL TRUE: Normal
FALSE: Abnormal (The fail-safe value is output.)
Indicates whether or not input value 1 (IN1) is normal
TRUE: Normal
NR1 BOOL
FALSE: The data status is BAD or the data value is different
from the other input values.
OUT
Indicates whether or not input value 2 (IN2) is normal
TRUE: Normal
NR2 BOOL
FALSE: The data status is BAD or the data value is different
from the other input values.
Indicates whether or not input value 3 (IN3) is normal
TRUE: Normal
NR3 BOOL
FALSE: The data status is BAD or the data value is different
from the other input values.
n Description
A BOOLVOTER function block is a 3-input BOOL voter. It receives three input values with data
status and outputs one value selected as the value of at least two out of the three inputs (two-
out-of three: 2oo3) via the output (Q). By using the BOOLVOTER function block, it is possible to
detect not only input module failures, but also errors in input values INn {n = 1, 2 or 3} received
from sensors.
IN1, IN2 and IN3 are Boolean inputs (IO_BOOL type) with data status.
If the status of input INn is BAD, NRn is set to FALSE.
The data status of an input signal is determined by the input modules under normal
circumstances. The BAD data status indicates that an input processing error was detected
in the input module.
If the data status of all the inputs is GOOD and all the input values are the same, the output
is the same value as the inputs. NR and all NRn become TRUE. This is the normal status {n
= 1, 2 and 3}.
If the data status of two inputs is GOOD and their input values are the same, that value is
output. NR and NRn of the inputs whose data status is GOOD become TRUE. NRm of the
input whose data status is BAD becomes FALSE {n, m = 1, 2 or 3}.
If the data status of two inputs is GOOD but the inputs have different values, the VAL value
is output from Q. NR and all NRn become FALSE {n = 1, 2 or 3}.
If the data status of two or more inputs is BAD, the VAL value is output from Q. NR and all
NRn become FALSE {n = 1, 2 and 3}.
n Remarks
Set values such that the input value at error occurrence in each input channel and the fail-safe
value (VAL) of the BOOLVOTER function block match each other. This should be done because
the BOOLVOTER function block uses VAL rather than the input value at error occurrence set for
an input channel if the input channel becomes abnormal.
ANLG_S
IN OUT
SH STS
SL NHTR
HH NHHH
PH NLLL
PL NLTR
LL
HYS
TRDT
PADT
SOER
ID
C030701E.ai
Figure ANLG_S
n Arguments
Table Arguments of ANLG_S
IN/OUT Arguments Data type Description
IN IO_REAL Analog input (data value: 0 to 100%)
SH REAL Scale high limit (engineering data)
SL REAL Scale low limit (engineering data)
HH REAL Setting level of HI trip (engineering data)
PH REAL Setting level of HI pre-alarm (engineering data)
PL REAL Setting level of LO pre-alarm (engineering data)
LL REAL Setting level of LO trip (engineering data)
Hysteresis (HYS 0; unit is %). If HYS is set as HYS < 0, it acts as
HYS REAL
HYS = 0.
IN
The minimum time period treated as trip occurrence (Must be an
integer multiple of the scan period)
TRDT TIME
If a trip event continues for the time period specified here, the trip
Occurred is stored in NHTR and NLTR.
The minimum time period treated as pre-alarm occurrence (Must be
an integer multiple of the scan period)
PADT TIME
If a pre-alarm event continues for the time period specified here, the
trip Occurred is stored in NHHH and NLLL.
SOER BOOL SOER setting
Character string of up to 32 single-byte or 16 double-byte characters
ID STRING
specified for SOER
OUT REAL Analog output (scale already converted)
Data status (data status of IN)
STS BOOL TRUE: GOOD
FALSE: BAD
HI trip occurrence flag
NHTR BOOL TRUE: Normal
FALSE: Occurred
OUT HI pre-alarm occurrence flag
NHHH BOOL TRUE: Normal
FALSE: Occurred
LO pre-alarm occurrence flag
NLLL BOOL TRUE: Normal
FALSE: Occurred
LO trip occurrence flag
NLTR BOOL TRUE: Normal
FALSE: Occurred
n Description
An ANLG_S function block converts the scale of the analog input (IN), and then outputs the
converted analog output (OUT) and data status (STS) corresponding to the analog input (IN). It
compares this output value (OUT) with four types of threshold values (HH, PH, PL and LL) and
outputs an alarm status (NHTR, NHHH, NLLL or NLTR). Each alarm condition is only set as
having occurred (FALSE) if the alarm condition continues for a specified period of time (TRDT
or PADT) or longer. If TRUE is specified for SOER, an SOE event is generated when a trip/pre-
alarm occurs or the system recovers from it.
It can be referenced using a tag name from CENTUM by defining the tag name for the instance
of the ANLG_S function block. If the data status (STS) becomes FALSE (BAD), an IOP process
alarm is generated, which can be confirmed on an HIS.
l Scale Conversion
IN is normalized data in the range from 0.0 to 100.0%. The ANLG_S function block uses scale
high limit (SH) and scale low limit (SL) to convert IN into physical units and outputs this value as
OUT.
IN.v x (SH - SL)
OUT = + SL
100.0
C030702E.ai
HH
HYS (SH - SL)
100.0
TRDT
TRDT
time
T
NHTR
F
T
NLTR
F
C030703E.ai
The ANLG_S function block sets NHHH to TRUE if OUT becomes equal to or smaller than the
HI pre-alarm detection value obtained by subtracting the hysteresis value during a HI pre-alarm
occurrence. Similarly, it sets NLLL to TRUE if OUT becomes equal to or greater than the LO
pre-alarm detection value obtained by subtracting the hysteresis value during a LO pre-alarm
occurrence.
The table below shows the conditions for NHHH and NLLL values to change.
Table Relationship between OUT and NHHH/NLLL
Argument Condition Value
The condition of OUT > PH continues for the time period specified by PADT or longer FALSE
NHHH OUT PH HYS x (SH - SL)/100.0 TRUE
Other hold
The condition of OUT < PL continues for the time period specified by PADT or longer FALSE
NLLL OUT PL + HYS x (SH - SL)/100.0 TRUE
Other hold
PADT (minimum time period treated as pre-alarm occurrence) is applied only at pre-alarm
occurrence. HYS (hysteresis) is applied at recovery from an pre-alarm.
If it is desired to set NHHH to TRUE (Normal) at all times, set PH greater than the maximum
value the OUT value can take.
If it is desired to set NLLL to TRUE (Normal) at all times, set PL smaller than the minimum
value the OUT value can take.
PH
HYS (SH - SL)
100.0
PADT
PADT
time
T
NHHH
F
T
NLLL
F
C030704E.ai
n SOER Specification
If the argument SOER (SOER setting) is set to TRUE, the ANLG_S function block generates
an event at the timing of alarm (HI/LO pre-alarm or trip) occurrence and recovery. The type of
generated event can be identified in the Message column of SOE Viewer.
Table SOE Events Generated by ANLG_S
Event generation timing ID Message
NHTR value changes from TRUE to FALSE EVT_FALSE
HTPn
NHTR value changes from FALSE to TRUE EVT_TRUE
NHHH value changes from TRUE to FALSE EVT_FALSE
HHHn
NHHH value changes from FALSE to TRUE EVT_TRUE
NLLL value changes from TRUE to FALSE EVT_FALSE
LLLn
NLLL value changes from FALSE to TRUE EVT_TRUE
NLTR value changes from TRUE to FALSE EVT_FALSE
LTPn
NLTR value changes from FALSE to TRUE EVT_TRUE
The character string specified in the ID input parameter is attached to these SOE events.
The character string information is displayed in the Reference column of SOE Viewer.
The STS output parameter (data status of IN) cannot be specified as SOE event. There is
no SOE event related to generation of IOP (input open).
The table below shows process alarm notifications at generation of/recovery from HI and LO pre-
alarms and HI and LO trips.
Table Process Alarms at Generation of HI and LO Pre-alarms and Trips
Event generation timing Process alarm
NHTR value changes from TRUE to FALSE HTRP generation
NHTR value changes from FALSE to TRUE HTRP recovery
NHHH value changes from TRUE to FALSE HHH generation
NHHH value changes from FALSE to TRUE HHH recovery
NLLL value changes from TRUE to FALSE LLL generation
NLLL value changes from FALSE to TRUE LLL recovery
NLTR value changes from TRUE to FALSE LTRP generation
NLTR value changes from FALSE to TRUE LTRP recovery
IMPORTANT
As shown in above table, in ANLG_S, the parameter names indicating conditions of alarm
occurrence and character strings in process alarms indicating generation of / recovery from HI
and LO pre-alarms and trips are different.
SEE
ALSO For the specification of mapping blocks, see the following:
n Data Items of Mapping Blocks Associated with Analog Input Function Blocks with Data Status (ANLG_
S) in D2.3, Tag Name Interfaces of Function Blocks
n Remarks
Since the ANLG_S function block performs scale conversion, there is no need to connect a
SCALER function before ANLG_S.
To filter an analog input, connect a FILTER or FILTER_S function block before ANLG_S.
This function block can be used in new SCS databases created by SENG of R1.02.00 or
later.
n Example
SEE
ALSO For examples of applications of the ANLG_S function block, see the following:
3.3.1, Use of Analog Input Value of the Engineering Guide (IM 32S01C10-21E)
ANLGI
IN OUT
SH HTRP
SL HHH
HH LLL
PH LTRP
PL
LL
HYS
SOER
ID
C030801E.ai
Figure ANLGI
n Arguments
Table Arguments of ANLGI
IN/OUT Arguments Data type Description
IN REAL Input value (0 to 100%)
SH REAL Scale high limit (engineering data)
SL REAL Scale low limit (engineering data)
HH REAL Setting level of High trip (engineering data)
PH REAL Setting level of High pre-alarm (engineering data)
IN PL REAL Setting level of Low pre-alarm (engineering data)
LL REAL Setting level of Low trip (engineering data)
Hysteresis (HYS 0; 0% -100%). If HYS is set as HYS < 0, it acts
HYS REAL
as HYS = 0.
SOER BOOL SOER setting
Character string of up to 32 single-byte or 16 double-byte
ID STRING
characters specified for SOER
OUT REAL Output value (value after scale conversion)
High trip occurrence flag
HTRP BOOL TRUE: Occurring
FALSE: Not occurred
High pre-alarm occurrence flag
HHH BOOL TRUE: Occurring
OUT FALSE: Not occurred
Low pre-alarm occurrence flag
LLL BOOL TRUE: Occurring
FALSE: Not occurred
Low trip occurrence flag
LTRP BOOL TRUE: Occurring
FALSE: Not occurred
n Description
The ANLGI function block converts the scale of the input value (IN) and calculates the output
value (OUT). It compares this output value with four types of threshold values (HH, PH, PL and
LL) and outputs an alarm status (HTRP, HHH, LLL or LTRP). An SOE event can be generated by
an alarm occurrence. Moreover, it can be referenced using a mapping block from CENTUM by
defining a tag name for the instance of the function block.
If it is desired to set HTRP to FALSE at all times, set HH greater than the maximum value the
OUT value can take.
If it is desired to set LTRP to FALSE at all times, set LL smaller than the minimum value the OUT
value can take.
To prevent the chattering of the trip which is caused by the input value fluctuation around the trip
detection level, specify the hysteresis value (HYS). Specify it as a percentage of the scale. The
recommended value is 2.0%.
HH
HYS(SH-SL)
100.0
HYS(SH-SL)
100.0
LL
time
T
HTRP
F
T
LTRP
F
C030803E.ai
If it is desired to set HHH to FALSE at all times, set PH greater than the maximum value the OUT
value can take.
If it is desired to set LLL to FALSE at all times, set PL smaller than the minimum value the OUT
value can take.
OUT
PH
HYS (SH - SL)
100.0
time
T
HHH
F
T
LLL
F
C030804E.ai
SEE
ALSO For the mapping blocks, see the following:
n Data Items of Mapping Blocks Associated with Analog Input Function Blocks (ANLGI) in D2.3, Tag
Name Interfaces of Function Blocks
n Remarks
Since the ANLGI function block performs scale conversion, there is no need to connect a
SCALER function before ANLGI. To filter an analog input, connect a FILTER or FILTER_S
function block before ANLGI.
VEL
IN OUT
VL VELP
HYS VELM
CT
C030901E.ai
Figure VEL
n Arguments
Table Arguments of VEL
IN/OUT Arguments Data type Description
IN REAL Input value (0 to 100%)
VL REAL Velocity limit alarm setting level (VL > 0%)
IN
HYS REAL Hysteresis (HYS 0). If HYS is set as HYS < 0, it acts as HYS = 0.
CT TIME Sampling interval
OUT REAL Output value
VEL + alarm occurrence flag
VELP BOOL TRUE: Occurring
OUT FALSE: Not occurred
VEL - alarm occurrence flag
VELM BOOL TRUE: Occurring
FALSE: Not occurred
n Description
The VEL function block monitors the rate of change of the input value and judges whether or not
the specified rate of change is exceeded. Moreover, it can be referenced using a mapping block
from CENTUM by defining a tag name for the instance in question.
The VEL function block monitors the input value (IN) at the sampling intervals (CT) and judges
that the rate of change is exceeded if the absolute value of the amount of input change ( IN)
exceeds the velocity limit alarm setting level (VL). If VL is set as VL 0%, as long as a velocity
exists, no matter how small it is, the input signal will be treated as a signal exceeds the velocity
limit. If IN is greater than VL, the VEL function block outputs TRUE for the VEL + alarm
occurrence status (VELP). If IN is smaller than -VL, the VEL function block outputs TRUE for
the VEL - alarm occurrence status (VELM).
If IN becomes equal to or smaller than VL - HYS while a VEL + alarm is detected, the VEL
function block outputs FALSE for the VEL + alarm occurrence status (VELP).
If IN becomes equal to or greater than - (VL - HYS) while a VEL - alarm is detected, the VEL
function block outputs FALSE for the VEL - alarm occurrence status (VELM).
Using the VEL function block allows detecting a sudden change of the process state and errors in
sensors and transmitters.
IN
< VL - HYS
> VL
time
CT
T
VELP
F
C030902E.ai
SEE
ALSO For the mapping blocks, see the following:
n Data Items of Mapping Blocks Associated with Velocity Limit Alarm Function Blocks (VEL) in D2.3, Tag
Name Interfaces of Function Blocks
n Remarks
The data type of the IN input argument of a VEL function block is REAL. If it is desired to monitor
velocity limit alarms between an analog input variable (with data status) and an ANLGVOTER
function block, place a FILTER_S function block before the VEL function block and connect the
VAL output argument of the FILTER_S function block to the IN input terminal of the VEL function
block.
The VEL function block must be placed before scale conversion (before a SCALER function or
an ANLGI function block).
IMPORTANT
If a value of a variable connected to the IN input terminal of the VEL function block is changed
via forcing or override, the input value of the VEL function block may change suddenly and a
velocity limit alarm may be generated. To avoid this, be careful not to change the input value of
the VEL function block suddenly when performing the forcing or override operation on a variable
connected to the IN input terminal of the VEL function block.
CTU
CU
Q
RESE
CV
PV
C031001E.ai
Figure CTU
n Arguments
Table Arguments of CTU
IN/OUT Arguments Data type Description
CU BOOL Count input (count up while CU is TRUE)
IN RESE BOOL Reset command (given higher priority than CU)
PV DINT Maximum counter value
Q BOOL TRUE at overflow (CV PV)
OUT
CV DINT Count result
n Description
The CTU function block counts up in increments of 1 at each scan from 0 to the maximum
counter value (PV) as long as the count input (CU) is TRUE. The count result is output for
CV and the default value is 0.
When the counter reaches the maximum value (CV PV), the CTU function block stops
counting up and outputs TRUE for Q.
RESE is a reset command. If RESE becomes TRUE, the counter is reset, Q becomes
FALSE and CV becomes 0. As long as RESE is TRUE, the CTU function block does not
count up even if CU becomes TRUE.
n Remarks
IMPORTANT
The CTU function block of ProSafe-RS and the standard CTU function block of IEC 61131-3
have different count-up conditions, which requires some precaution. The standard CTU function
block of IEC 61131-3 counts up at each rising edge of the count input (CU).
In order to count up the counter value at rising edge, combine an R_TRIG function block and a
CTU function block.
CD
Q
LOAD
CV
PV
C031001E.ai
Figure CTD
n Arguments
Table Arguments of CTD
IN/OUT Arguments Data type Description
CD BOOL Count input (count down while CD is TRUE)
IN LOAD BOOL Load command (given higher priority than CD)
PV DINT Initial counter value
Q BOOL TRUE at underflow (CV 0)
OUT
CV DINT Count result
n Description
The CTD function block counts down in decrements of 1 at each scan from the initial
counter value (PV) to 0 as long as the count input (CD) is TRUE. The count result is output
for CV and the default value is the initial counter value (PV).
When the counter reaches 0 (CV 0), CTD stops counting down and outputs TRUE for Q.
LOAD is a load command. If LOAD becomes TRUE, the counter is loaded, Q becomes
FALSE and CV is reset to PV. As long as LOAD is TRUE, the CTD function block does not
count down even if CD becomes TRUE.
n Remarks
IMPORTANT
The CTD function block of ProSafe-RS and the standard CTD function block of IEC 61131-
3 have different count-down conditions, which requires some precaution. The standard CTD
function block of IEC 61131-3 counts down at each rising edge of the count input (CD).
In order to count down the counter value at rising edge, combine an R_TRIG function block and a
CTD function block.
CU
CD
RESE QU
LOAD QD
PV CV
C031201E.ai
Figure CTUD
n Arguments
Table Arguments of CTUD
IN/OUT Arguments Data type Description
CU BOOL Count-up input (count up as long as CU is TRUE)
CD BOOL Count-down input (count down as long as CD is TRUE)
Reset command (given higher priority than CU and CD) (CV = 0
IN RESE BOOL
if RESE is TRUE)
LOAD BOOL Load command (CV = PV if LOAD is TRUE)
PV DINT Maximum counter value
QU BOOL TRUE at overflow status (CV PV)
OUT QD BOOL TRUE at underflow status (CV 0)
CV DINT Count result (0 CV PV)
n Description
The CTUD function block is a counter that can count both up and down. The count result is
output for CV and the default value is 0.
The CTUD function block counts up in increments of 1 at each scan up to the maximum
counter value as long as the count-up input (CU) is TRUE.
It counts down in decrements of 1 at each scan down to 0 as long as the count-down input
(CD) is TRUE.
When the counter reaches the maximum value (CV PV), the CTUD function block stops
counting up and outputs TRUE for QU.
When the counter reaches 0 (CV 0), the CTUD function block stops counting down and
outputs TRUE for QD.
RESE is a reset command. If RESE becomes TRUE, the counter is reset, QU becomes
FALSE and CV becomes 0. As long as RESE is TRUE, the CTUD function block does not
count up or down.
LOAD is a load command. If LOAD becomes TRUE, the counter is loaded, QD becomes
FALSE and CV is reset to PV.
n Remarks
IMPORTANT
The CTUD function block of ProSafe-RS and the standard CTUD function block of IEC 61131-3
have different count-up/down conditions, which requires some precaution. (The standard CTUD
function block of IEC 61131-3 counts up/down at each rising edge of the count input (CU/CD).)
In order to count up/down the counter value at rising edge, combine an R_TRIG function block
with a CTUD function block.
Do not set both count-up input (CU) and count-down input (CD) to TRUE at the same time. If both
are set to TRUE, the CTUD function block counts up. If CV reaches PV, however, CV outputs
values of PV and PV - 1 repeatedly at each scan.
C031301E.ai
Figure B_TO_IB
n Arguments
Table Arguments of B_TO_IB
IN/OUT Arguments Data type Description
V BOOL Data value
IN
STS BOOL Status
OUT Q IO_BOOL Value converted to IO_BOOL type
n Description
The B_TO_IB function block converts input data values and status to IO_BOOL type and outputs
the converted data.
n Remarks
This function block can be used in new SCS databases created by SENG of R1.01.30 or later.
C031401E.ai
Figure R_TO_IR
n Arguments
Table Arguments of R_TO_IR
IN/OUT Arguments Data type Description
V REAL Data value
IN
STS BOOL Status
OUT Q IO_REAL Value converted to IO_REAL type
n Description
The R_TO_IR function block converts input data values and status to IO_REAL type and outputs
the converted data.
n Remarks
This function block can be used in new SCS databases created by SENG of R1.01.30 or later.
ANN_FUP
IN OUT
SS OUT2
GR
C031501E.ai
Figure ANN_FUP
n Arguments
Table Arguments of ANN_FUP
IN/OUT Arguments Data type Description
IN BOOL Alarm condition input
Safe state specification
IN SS BOOL TRUE: ETS
FALSE: DTS
Group number: 1 to 256
GR DINT
Enter a fixed value for the group number.
First-up alarm output
OUT BOOL TRUE: First-up alarm status
FALSE: Not in first-up alarm status
OUT
Second output
OUT2 BOOL TRUE: Second to reach safe state
FALSE: Not the second to reach safe state
n Description
The ANN_FUP function block has the following functions.
IMPORTANT
Typographical errors in group number specification cannot be detected by the system. Therefore,
during the logic test, if the group numbers have been properly specified or not must be carefully
inspected.
n Remarks
Specify a value in the range from 1 to 256 for the group number (GR). If a value outside
the range (0 or less or 257 or more) is specified to GR, OUT is always FALSE and no
annunciator messages are notified.
Up to 256 groups can be used for a single SCS.
There is no limit to the number of ANN_FUP function blocks that can be specified in one
group.
This function block can be used in new SCS databases created by SENG of R2.03.00 or
later.
FUP_RST
IN SSI
GR SSO
C031601E.ai
Figure FUP_RST
n Arguments
Table Arguments of FUP_RST
IN/OUT Arguments Data type Description
IN BOOL Reset input (valid only at change from FALSE to TRUE)
IN
GR BOOL ANN_FUP group number to be reset (1 to 256)
Whether or not there are any function blocks whose IN and SS match
within the same group
SSI BOOL
TRUE: One or more blocks where IN = SS exist
FALSE: No blocks where IN = SS exist
OUT
Whether or not there are function blocks in the first-up alarm status in the
specified group
SSO BOOL
TRUE: There is at least one function block in the first-up alarm status
FALSE: No function block in the first-up alarm status
n Description
The FUP_RST function block is used to reset the first-up alarm status set by ANN_FUP.
Specify the group number to be reset to GR of the FUP_RST. By changing the reset input (IN)
from FALSE to TRUE, it functions as the reset signal of the first-up alarm status of the target
group. Note that OUT of ANN_FUP in the first-up alarm status is actually reset only when the
reset signal is generated from the FUP_RST function block under the conditions where IN and
SS do not match in all function blocks in the same group.
When the ANN_FUP in the first-up alarm status is reset, an annunciator message is generated to
notify recovery from the alarm status.
l Example
Occurrence of first-up alarm status
(annunciator message notification) Recovery from first-up alarm status
IN T
ANN_FUP[A] F
SS = T
GR = 1 OUT T
F
IN T
ANN_FUP[B] F
SS = T
GR = 1 OUT2 T
F
IN T
ANN_FUP[C] F
SS = T
GR = 1 OUT T
F
FUP_RST IN T
GR = 1 F
t1 t2 t3 t4 t5 t6 t
1scan
C031602E.ai
ANN_FUP [A] first detects matching of IN and SS at t1 and OUT changes to TRUE.
When ANN_FUP [B] detects matching of IN and SS at t2, OUT2 becomes TRUE because
the function block is the second one in the group to detect the matching.
Even if ANN_FUP [C] detects matching of IN and SS at t3, both OUT and OUT2 remain
FALSE because the function block is the third one in the group to detect the matching.
If a reset signal is generated at t4, OUT of ANN_FUP [A] and OUT2 of ANN_FUP [B] remain
TRUE because IN and SS match for all ANN_FUP function blocks.
If a reset signal is generated again at t5, IN and SS of ANN_FUP [A] do not match but IN
and SS of other ANN_FUP function blocks remain matched. Thus, OUT of ANN_FUP [A]
and OUT2 of ANN_FUP [B] remain TRUE.
If a reset signal is generated at t6, IN and SS do not match for all ANN_FUP function blocks.
Thus, OUT of ANN_FUP [A] and OUT2 of ANN_FUP [B] become FALSE.
IMPORTANT
The execution order of ANN_FUP and FUP_RST and the change of signals have the following
relationships.
If FUP_RST is executed first
OUT (OUT2) of ANN_FUP becomes FALSE within the same scan where the IN input
changes from FALSE to TRUE in FUP_RST.
SSO of FUP_RST becomes FALSE in the next scan.
If FUP_RST is executed later
OUT (OUT2) of ANN_FUP becomes FALSE in the next scan after the IN input changes from
FALSE to TRUE in FUP_RST.
SSO of FUP_RST becomes FALSE in the next scan executed after OUT of ANN_FUP
becomes FALSE, meaning 2 scans after IN of FUP_RST becomes TRUE.
l Output
SSI and SSO of FUP_RST are representative values of the input and output statues of all ANN_
FUP function blocks in the group specified by GR. It is possible to use the value of SSO in the
application logic to indicate whether the reset operation is successful or not.
n Remarks
Specify a numerical value in the range from 1 to 256 for the group number (GR). If a value
outside the range for GR (0 or less or 257 or larger) is specified, resetting is not performed.
This function block can be used in new SCS databases created by SENG of R2.03.00 or
later.
The following function blocks are provided for SCS link transmission safety
communication.
Link Transmission Data Output Block (LTSND)
Safety Link Transmission Data Input Block (LTRCV)
SEE
ALSO For more information about inter-SCS safety communication, see the following:
A5, Inter-SCS Safety Communication
For more information about SCS link transmission safety communication, see the following:
A6, SCS Link Transmission
PROD_B
IN
BVAR
C040101E.ai
Figure PROD_B
n Arguments
Table Arguments of PROD_B
IN/OUT Arguments Data type Description
IN IN BOOL Input value (data transmitted to communicating SCSs)
OUT BVAR COM_BOOL Binding variable for sending BOOL-type data
n Description
The PROD_B function block converts BOOL-type data to a binding variable for sending BOOL-
type data in order to send data to an SCS on the consuming side. This function block is linked
with the output enable operation; no valid data is set to the binding variable at the connection
destination until the output enable operation is performed.
Information on whether or not the transmission succeeded is not notified to this function block.
Use a SYS_DIAG function block to check for error occurrence.
SEE
ALSO For the SYS_DIAG function block, see the following:
C9.6, SYS_DIAG (Diagnostic Information Output)
n Remarks
Make sure that the data type and the numerical value part of the binding variable name in
question match between the sending side and receiving side.
PROD_I
IN
BVAR
C040201E.ai
Figure PROD_I
n Arguments
Table Arguments of PROD_I
IN/OUT Arguments Data type Description
IN IN DINT Input value (data transmitted to communicating SCSs)
OUT BVAR COM_DINT Binding variable for sending DINT-type data
n Description
The PROD_I function block converts DINT-type data to a binding variable for sending DINT-type
data in order to send data to an SCS on the consuming side. This function block is linked with the
output enable operation; no valid data is set to the binding variable at the connection destination
until the output enable operation is performed.
Information on whether or not the transmission succeeded is not notified to this function block.
Use a SYS_DIAG function block to check for error occurrence.
SEE
ALSO For the SYS_DIAG function block, see the following:
C9.6, SYS_DIAG (Diagnostic Information Output)
n Remarks
Make sure that the data type and the numerical value part of the binding variable name in
question match between the sending side and receiving side.
IN
BVAR
C040301E.ai
Figure PROD_R
n Arguments
Table Arguments of PROD_R
IN/OUT Arguments Data type Description
IN IN REAL Input value (data transmitted to communicating SCSs)
OUT BVAR COM_REAL Binding variable for sending REAL-type data
n Description
The PROD_R function block converts REAL-type data to a binding variable for sending REAL-
type data in order to send data to an SCS on the consuming side. This function block is linked
with the output enable operation; no valid data is set to the binding variable at the connection
destination until the output enable operation is performed.
Information on whether or not the transmission succeeded is not notified to this function block.
Use a SYS_DIAG function block to check for error occurrence.
SEE
ALSO For the SYS_DIAG function block, see the following:
C9.6, SYS_DIAG (Diagnostic Information Output)
n Remarks
Match data type and the numerical value of binding variable names handled between the
sending side and receiving side.
BVAR OUT
VAL
OUTT
DLYT NR
C040401E.ai
Figure CONS_B
n Arguments
Table Arguments of CONS_B
IN/OUT Arguments Data type Description
BVAR COM_BOOL Binding variable for receiving BOOL-type data
VAL BOOL Fail-safe value output at error occurrence
Reception interval timeout value: 100 ms to 30 seconds
If a value outside the range is specified, it is treated as 100 ms or
OUTT TIME 30 seconds, whichever is closer.
IN Generates a communication error if reception interval exceeds
OUTT.
Transmission delay timeout value
Generates a communication error if transmission delay time
DLYT TIME
exceeds DLYT.
Transmission delay is not checked if DLYT is set to 0. (*1)
OUT BOOL Output value
OUT The communication status is output.
NR BOOL TRUE: GOOD
FALSE: BAD (including cases where data is not received)
*1: When DLYT is set to 0, the communication cannot be used for safety purpose.
n Description
This function block receives BOOL-type data sent from a PROD_B function block of a producing
side SCS and outputs it via OUT. The communication status is output via NR.
If a communication error occurs, the CONS_B function block generates a diagnostic information
message indicating the communication error and outputs the fail-safe value specified in VAL
via OUT. When the system recovers from the communication error, it generates a diagnostic
information message indicating the recovery and the reception data is output via OUT again.
Create logic for latching and canceling of the output at error occurrence in the application logic.
TRUE
OUT
FALSE
Output fail- Output the value Output fail- Output the value
safe value from the producing safe value from the producing
side side
TRUE
NR
FALSE
Communication Demand from Occurrence Recovery from
start the producing of communi- communication
side cation error error
C040402E.ai
The transmission delay is the time after the function block on the producing side transmits data
until the function block on the consuming side receives the data. If the transmission delay time
exceeds the time specified by the transmission delay timeout value (DLYT), it is regarded as
a communication error. If the transmission delay time is shorter than the allowable time error
(negative value), it is also treated as a communication error.
The transmission delay is affected not only by the delays in the communication path, but also by
the scan period of the SCS on the producing side and that of the SCS on the consuming side. A
time discrepancy between the SCS on the producing side and the SCS on the consuming side
can cause errors in the calculation of transmission delay. Set an appropriate value for DLYT
according to the time synchronization method of SCSs.
The normal range of transmission delay is as follows.
Transmission
delay
Reception
interval
Time
C040403E.ai
SEE
ALSO For more information about notices on determining DLYT value, see the following:
Precaution for Engineering of 2.8, Inter-SCS Safety Communication of the Engineering Guide (IM
32S01C10-21E)
n Remarks
Make sure that the data type and the numerical value part of the binding variable name in
question match between the producing side and consuming side.
BVAR OUT
VAL
OUTT
DLYT NR
C040501E.ai
Figure CONS_I
n Arguments
Table Arguments of CONS_I
IN/OUT Arguments Data type Description
BVAR COM_DINT Binding variable for receiving DINT-type data
VAL DINT Fail-safe value output at error occurrence
Reception interval timeout value: 100 ms to 30 seconds
If a value outside the range is specified, it is treated as 100 ms or
OUTT TIME 30 seconds, whichever is closer.
IN Generates a communication error if OUTT becomes smaller
than the reception interval.
Transmission delay timeout value
Generates a communication error if DLYT becomes smaller than
DLYT TIME
transmission delay.
Transmission delay is not checked if DLYT is set to 0. (*1)
OUT DINT Output value
OUT The communication status is output.
NR BOOL TRUE: Normal
FALSE: Abnormal (including non-received data)
*1: When DLYT is set to 0, the communication cannot be used for safety purpose.
n Description
This function block receives DINT-type data sent from a PROD_I function block of a sending SCS
and outputs it via OUT. The communication status is output via NR.
If a communication error occurs, the CONS_I function block generates a diagnostic information
message indicating the communication error and outputs the fail-safe value specified in VAL
via OUT. When the system recovers from the communication error, it generates a diagnostic
information message indicating the recovery and the reception data is output via OUT again.
Create logic for latching and canceling of the output at error occurrence in the application logic.
OUT
Output fail- Output the value Output fail- Output the value
safe value from the producing safe value from the producing
side side
TRUE
NR
FALSE
Communication Occurrence Recovery from
start of communi- communication
cation error error
C040502E.ai
SEE
ALSO For the reception interval timeout value (OUTT) and transmission delay timeout value (DLYT), see the following:
n Description in C4.4, CONS_B (Inter-SCS Safety Communication BOOL-Type Data Consumer)
n Remarks
Make sure that the data type and the numerical value part of the binding variable name in
question match between the sending side and receiving side.
BVAR OUT
VAL
OUTT
DLYT NR
C040601E.ai
Figure CONS_R
n Arguments
Table Arguments of CONS_R
IN/OUT Arguments Data type Description
BVAR COM_REAL Binding variable for receiving REAL-type data
VAL REAL Fail-safe value output at error occurrence
Reception interval timeout value: 100 ms to 30 seconds
If a value outside the range is specified, it is treated as 100 ms or
OUTT TIME 30 seconds, whichever is closer.
IN Generates a communication error if OUTT becomes smaller
than the reception interval.
Transmission delay timeout value
Generates a communication error if DLYT becomes smaller than
DLYT TIME
transmission delay.
Transmission delay is not checked if DLYT is set to 0. (*1)
OUT REAL Output value
OUT The communication status is output.
NR BOOL TRUE: Normal
FALSE: Abnormal (including non-received data)
*1: When DLYT is set to 0, the communication cannot be used for safety purpose.
n Description
This function block receives REAL-type data sent from a PROD_R function block of a sending
SCS and outputs it via OUT. The communication status is output via NR.
If a communication error occurs, the CONS_R function block generates a diagnostic information
message indicating the communication error and outputs the fail-safe value specified in VAL
via OUT. When the system recovers from the communication error, it generates a diagnostic
information message indicating the recovery and the reception data is output via OUT again.
Create logic for latching and canceling of the output at error occurrence in the application logic.
OUT
Output fail- Output the value Output fail- Output the value
safe value from the producing safe value from the producing
side side
TRUE
NR
FALSE
Communication Occurrence Recovery from
start of communi- communication
cation error error
C040602E.ai
SEE
ALSO For the reception interval timeout value (OUTT) and transmission delay timeout value (DLYT), see the following:
n Description in C4.4, CONS_B (Inter-SCS Safety Communication BOOL-Type Data Consumer)
n Remarks
Make sure that the data type and the numerical value part of the binding variable name in
question match between the sending side and receiving side.
C040701E.ai
Figure LTSND
n Arguments
Table Arguments of LTSND
IN/OUT Arguments Data type Description
IN V BOOL Input value
n Description
The BOOL type datum specified for input parameter V will be sent to other stations in the same
domain.
Information on whether or not the transmission succeeded is not notified to this function block.
Use a SYS_DIAG function block to check for error occurrence.
SEE
ALSO For more information about SYS_DIAG function block, see the following:
C9.6, SYS_DIAG (Diagnostic Information Output)
n Remarks
For other POU to use the set datum, the input signal needs to be diverged. And the diverged
signal should be connected to a global variable, and the global variable should be used.
This function block can be used in new SCS databases created by SENG of R1.03.00 or
later.
LTRCV
STS
C040801E.ai
Figure LTRCV
n Arguments
Table Arguments of LTRCV
IN/OUT Arguments Data type Description
V BOOL Output value
OUT Data status (SCS link transmission data receiving)
STS BOOL TRUE: Normal
FALSE: Abnormal (including cases where data is not received)
n Description
The output parameter V is to output the data sent from other SCSs in the same domain.
The output parameter STS is to output the reception status of SCS link transmission safety
communication.
When a communication error occurs, a value which specified in the [Input Processing at
Fault] item in Wiring Definition of SCS Link Transmission Builder will be output from V. When
communication error recovers, the output will recover to normal value.
Create application logics for latching and unlatching the output to manage the error occurrence.
n Remarks
This function block can be used in new SCS databases created by SENG of R1.03.00 or later.
SEE
ALSO For outline of the actions of the override function block, see the following:
D3.1, Overview of Override FB
For more information about the tag name interface and the process alarm of the override function block,
see the following:
D3.2, Tag Name Interfaces and Process Alarms of Override Function Blocks
OVR_B
IN OUT
VAL STS
SW
C050101E.ai
Figure OVR_B
n Arguments
Table Arguments of OVR_B, OVR_I, OVR_R, OVR_IB, OVR_IR
IN/OUT Arguments Data type Description
IN (*1) Input
VAL (*1) Override value
IN
TRUE: Override allowed. Override releasable
SW BOOL
FALSE: Override not allowed. Override not releasable
OUT (*1) Output
OUT TRUE: Overridden and OUT outputs the value specified in VAL
STS BOOL
FALSE: Not overridden and OUT outputs data input to IN
*1: The data type varies with the FB models. See the table of Types of Override Function Blocks.
n Description
The override function blocks output the data input from input parameter IN as is via output
parameter OUT as long as no overriding operation is performed. If an override instruction is set
from an HIS, on the other hand, the override function blocks output the data specified in input
parameter VAL via output parameter OUT. In short, data is fixed to the value defined in input
parameter VAL in advance. If the override operation is canceled from the HIS, the override
function blocks resume outputting data input from input parameter IN via output parameter OUT.
n Remarks
SW is a parameter that permits overriding. However, an override instruction is not canceled
even if the SW input changes from TRUE to FALSE while the override operation is
performed from an HIS.
It is possible to control the status of the override function blocks with a SYS_OVR system
function block.
SEE
ALSO For the SYS_OVR system function block, see the following:
C9.9, SYS_OVR (Override Function Blocks Management)
SEE
ALSO For more information regarding the table of Types of override Function Blocks, see the following:
Types of Override Function Blocks in Override Function Blocks
SEE
ALSO For more information about overview of grouping override function block, see the following:
D3.3, Overview of Grouping Override Function Block
For more information about tag name interfaces and process alarms of grouping override function blocks,
see the following:
D3.4, Tag Name Interfaces and Process Alarms of Grouping Override Function Block
GOV_B
IN OUT
GRP STS
VAL ENS
SW
C050201E.ai
Figure GOV_B
n Arguments
Table Arguments of GOV_B, GOV_IB
IN/OUT Arguments Data type Description
IN (*1) Input
Group number: 0 to 128
GRP DINT Enter a fixed value as the group number.
Enter a 0 to disable grouping.
IN
VAL BOOL Override value
Override permit switch
SW BOOL TRUE: Override permission
FALSE: Override prohibition
OUT (*1) Output
TRUE: Overridden and OUT outputs the value specified in VAL
STS BOOL
FALSE: Not overridden and OUT outputs data input to IN
OUT TRUE: Override executable.
If GRP is 0 and SW is TRUE, ENS will be TRUE.
ENS BOOL When overridden, ENS will be TRUE.
FALSE: Override disabled.
If GRP is less than 0 or greater than 128, ENS will be FALSE.
*1: The data type varies with the FB models. See the table of Types of Grouping Override Function Blocks.
n Description
The grouping override function blocks output the data input from input parameter IN as is via
output parameter OUT as long as no overriding operation is performed.
If the SW of the input parameter is TRUE and no other function block within the group is
running override, the output parameter ENS will be TRUE.
If an override operation is performed from an HIS, the grouping override function block
output the data specified in input parameter VAL via output parameter OUT.
This means to fix the datum using the value previously defined to the input parameter
VAL. In this case, the ENS of other override function blocks in the same group will become
FALSE.
If the override operation is canceled from the HIS, the grouping override function block
resume outputting data input from parameter IN via parameter OUT.
In this case, the ENS of the override function blocks in the same group will become TRUE
as long as the FBs SW is TRUE.
When override is being executed, the status of the output parameter OUT (IO_BOOL type)
of GOV_IB will be GOOD. When override is not being executed, the data status of input
parameter IN will be output as the data status of OUT.
n Remarks
The multiple override function blocks in the same group can not be executed override at the
same time.
The group number (GRP) should be specified with a constant of 0 to 128.
The function block with a group number of 0 can perform multiple override actions.
For a function block that is running override, if the SW parameter changes from TRUE to
FALSE, the override status will be released, and ENS parameter will become FALSE.
For GOV_IB during the override execution, if the SW parameter changes from TRUE to
FALSE, or if SYS_OVR issues a forced cancellation command, the override status will be
canceled even if IN data status is BAD.
It is possible to manage the status of the grouping override function blocks with a SYS_OVR
system function block.
These function blocks can be used in new SCS databases created in the software version
of R1.03.00 or later.
SEE
ALSO For more information regarding the table of Types of Grouping Override Function Blocks, see the following:
Types of Grouping Override Function Blocks in Grouping Override Function Blocks
PASSWD
PSWD OUT
C050301E.ai
Figure PASSWD
n Arguments
Table Arguments of PASSWD
IN/OUT Arguments Data type Description
Character
IN PSWD Password character string (up to 16 single-byte characters)
Constant
TRUE: TRUE is set via a mapping block
OUT OUT BOOL
FALSE: FALSE is set via a mapping block
n Description
A password character string entered on the faceplate of an HIS is transmitted to the PASSWD
function block via a mapping block. If this character string matches with the character string
specified for input parameter PSWD, a data value set to either TRUE or FALSE is received. As a
result, the PASSWD function block outputs the same value (TRUE or FALSE) as the data set via
the mapping block, to its output parameter OUT.
The default value of output parameter OUT of the PASSWD function block is FALSE. Make sure
to configure the PASSWD function block such that it outputs FALSE under normal circumstances
and TRUE when data requiring password authentication is set from an HIS when performing
processing (e.g., allow override operation).
SEE
ALSO For more information about how to use the PASSWD function block in override operation from an HIS, see
the following:
D3.6, Permission for Override by Password FB
For more information about tag name interface and process alarm of PASSWD FB, see the following:
D3.7, Tag Name Interfaces and Process Alarms of Password Function Blocks
n Remarks
Specify a password as a character string constant for the PSWD input parameter. A character
string of up to 16 alphanumeric characters can be specified for the PSWD input parameter. If a
character string exceeding 16 characters is specified for the PSWD input parameter, only the first
16 characters become the target of comparison and other characters are ignored.
It is recommended to specify a different password character string for each PASSWD function
block and make each password unique within the system.
It is possible to manage the status of the PASSWD function block with a SYS_PSWD
system function block.
It is possible to forcibly return the output of all PASSWD function blocks within an SCS to
FALSE by the SYS_PSWD function block.
SEE
ALSO For the SYS_PSWD system function block, see the following:
C9.10, SYS_PSWD (Password Function Blocks Management)
If it is desired to hide a password, apply the security setting for each POU that uses a PASSWD
function block (POUs in which a password character string is written) in the Workbench. As
a result, the POUs cannot be opened, nor can the self-documentation be printed, unless the
password specified for the security setting for each POU is entered.
MOB_11
SHDN OUT
SS NANP
IN NANM
SW
AIN
MTM
IOP
OOP
OTEN
PSWD
C050401E.ai
Figure MOB_11
n Arguments
Table Arguments of MOB_11
IN/OUT Arguments Data type Description
Shutdown signal
SHDN BOOL
The meaning of the signal is determined by the value of SS.
Safe state specification
SS BOOL TRUE: ETS
FALSE: DTS
Value specified to be output when manual operation is prohibited
IN BOOL The value specified in this parameter is output to OUT if SW is
FALSE.
Toggle switch permitting and prohibiting manual operation
SW BOOL TRUE: The operation output value from an HIS is output to OUT
FALSE: The value set in IN is output to OUT
Answerback input value (*1)
AIN BOOL TRUE: Open status
IN FALSE: Close status
Answerback check mask time (Must be an integer multiple of the
MTM TIME
scan period)
Signal for monitoring input status
IOP BOOL TRUE: Normal status
FALSE: Abnormal status
Signal for monitoring output status
OOP BOOL TRUE: Normal status
FALSE: Abnormal status
Signal indicating output enable status
OTEN BOOL TRUE: Output is enabled
FALSE: Output is disabled
Character
PSWD Password character string (up to 16 single-byte characters)
constant
Open/close operation output value (*1)
OUT BOOL TRUE: Open instruction
FALSE: Close instruction
Answerback status on the open side (*1)
OUT NANP BOOL TRUE: Normal status
FALSE: Abnormal status
Answerback status on the close side (*1)
NANM BOOL TRUE: Normal status
FALSE: Abnormal status
*1: With the assumption that the manipulated target is a valve, Open and Close are used in the description of the argument.
n Description
An MOB_11 function block is used to perform manual operations from an HIS at starting up and
maintaining a plant. It outputs BOOL type values.
The MOB_11 function has input parameters (SHDN and SS) for receiving shutdown events and
outputs shutdown logic signals with the highest priority if a shutdown event occurs.
It is possible to switch between permitting and prohibiting manual operations from an HIS by
the input to SW. If TRUE is input to SW, the MOB_11 function block outputs a manual operation
output value from the HIS to OUT. If FALSE is input to SW, it outputs the IN value as is to OUT.
It also performs answerback checks based on the answerback input value (AIN) and OUT and
outputs the results to NANP and NANM.
MOB_11 has the following functions.
Shutdown signals output
Manual operation permission
Manual operation authenticated by password
Output enable status display
Answerback check
IOP/OOP monitoring
CENTUM integration
SEE
ALSO For more information about MOB_11, see the following:
D4.1, HIS Interfaces of MOB_11 and MOB_21 (BOOL-Type Data Manual Operation Function Block with
Answerback)
n Remarks
This function block can be used in new SCS databases created by SENG of R1.02.00 or later.
MOB_21
SHDN OUT
SS NANP
IN NANM
SW NPER
AINP
AINM
MTM
IOP
OOP
OTEN
PSWD
C050501E.ai
Figure MOB_21
n Arguments
Table Arguments of MOB_21
IN/OUT Arguments Data type Description
Shutdown signal
SHDN BOOL
(The meaning of the signal is determined by the value of SS.)
Safe state specification
SS BOOL TRUE: ETS
FALSE: DTS
Value specified to be output when manual operation is prohibited
IN BOOL The value specified in this parameter is output to OUT if SW is
FALSE.
Toggle switch between permitting and prohibiting manual operation
SW BOOL TRUE: The operation output value from HIS is output to OUT.
FALSE: The value set in IN is output to OUT.
Answerback input value on the open side (*1)
AINP BOOL TRUE: Full-open status
FALSE: Not full-open status
Answerback input value on the close side (*1)
IN
AINM BOOL TRUE: Full-close status
FALSE: Not full-close status
Answerback check mask time
MTM TIME
(Must be an integer multiple of the scan period)
Signal for monitoring input status
IOP BOOL TRUE: Normal status
FALSE: Abnormal status
Signal for monitoring output status
OOP BOOL TRUE: Normal status
FALSE: Abnormal status
Signal indicating output enable status
OTEN BOOL TRUE: Output is enabled
FALSE: Output is disabled
Character
PSWD Password character string (up to 16 single-byte characters)
constant
Open/close operation output value (*1)
OUT BOOL TRUE: Open instruction
FALSE: Close instruction
Answerback status on the open side (*1)
NANP BOOL TRUE: Normal status
FALSE: Abnormal status
OUT
Answerback status on the close side (*1)
NANM BOOL TRUE: Normal status
FALSE: Abnormal status
Answerback pattern
NPER BOOL TRUE: Normal status
FALSE: Abnormal status
*1: With the assumption that the manipulated target is a valve, Open and Close are used in the description of the argument.
n Description
An MOB_21 function block is used to perform manual operations from an HIS at starting up and
maintaining a plant. It outputs BOOL type values.
The MOB_21 function block has input parameters (SHDN and SS) for receiving shutdown events
and outputs shutdown logic signals with the highest priority if a shutdown event occurs.
It is possible to switch between permitting and prohibiting manual operations from an HIS by
the input to SW. If TRUE is input to SW, the MOB_21 function block outputs a manual operation
output value from the HIS to OUT. If FALSE is input to SW, it outputs the IN value as is to OUT.
It also performs answerback checks based on OUT and the answerback input values (AINP and
AINM) for opening and closing, respectively, and outputs the results to NANP, NANM and NPER.
MOB_21 has the following functions.
Shutdown signals output
Manual operation permission
Manual operation authenticated by password
Output enable status display
Answerback check
IOP/OOP monitoring
CENTUM integration
SEE
ALSO The shutdown signals output function is the same as for MOB_11; see the following:
n Shutdown Output Operation in C5.4, MOB_11 (BOOL-Type Data Manual Operation Function Block
with Two-Position Answerback)
For the detailed explanations of other functions, see the following:
D4.1, HIS Interfaces of MOB_11 and MOB_21 (BOOL-Type Data Manual Operation Function Block with
Answerback)
n Remarks
This function block can be used in new SCS databases created by SENG of R1.02.00 or later.
MOB_RS
SW OUT
AIN NANM
ADIR
MTM
C050601E.ai
Figure MOB_RS
n Arguments
Table Arguments of MOB_RS
IN/OUT Arguments Data type Description
Toggle switch between permitting and prohibiting manual operation
SW BOOL TRUE: The operation output value from HIS is output to OUT.
FALSE: FALSE is output to OUT.
AIN BOOL Answerback input value
IN Answerback operation direction specification
ADIR BOOL TRUE: Forward operation
FALSE: Reverse operation
Answerback check mask time
MTM TIME
(Must be an integer multiple of the scan period)
OUT BOOL Operation output value for logic reset (pulse signal)
OUT Answerback status
NANM BOOL TRUE: Normal status
FALSE: Abnormal status
n Description
An MOB_RS function block outputs signals according to manual operations from an HIS and has
the function to automatically recover the output value after one SCS scan period. It can be used
as a switch to reset shutdown status at restoration of a plant if the plant is shut down by shutdown
logic signals.
It is possible to switch between permitting and prohibiting manual operations from an HIS by
the input to SW. If TRUE is input to SW, manual operations from the HIS are allowed. If MV is
changed from 0 to 2 via manual operations from the HIS, the MOB_RS function block outputs
TRUE to OUT. The value of OUT is automatically reset to FALSE after one scan.
If FALSE is input to SW, manual operations from the HIS are prohibited and the MOB_RS
function block outputs FALSE to OUT.
SEE
ALSO For manual operation permission and automatic reset functions, see the following:
n Overview of Processing MOB_RS in D4.2.1, Operations of MOB_RS from HIS
For the answerback check function, see the following:
n Answerback Check in D4.2.1, Operations of MOB_RS from HIS
For the CENTUM integration function, see the following:
D4.2.2, Tag Name Interfaces and Process Alarms of MOB_RS
n Remarks
This function block can be used in new SCS databases created by SENG of R1.02.00 or later.
MOA
SHDN OUT
SDV
IN
SW
FV
OOP
OTEN
PSWD
C050701E.ai
Figure MOA
n Arguments
Table Arguments of MOA
IN/OUT Arguments Data type Description
Shutdown signal
SHDN BOOL TRUE: Normal processing is performed
FALSE: Shutdown processing is performed
SDV REAL Shutdown output value (0 to 100%)
Value specified to be output when manual operation is prohibited (0 to
IN REAL 100%)
The value specified in this parameter is output to OUT if SW is FALSE.
Toggle switch between permitting and prohibiting manual operation
SW BOOL TRUE: The operation output value from HIS is output to OUT.
IN FALSE: The value set in IN is output to OUT.
FV REAL Feedback input value
Signal for monitoring output status
OOP BOOL TRUE: Normal status
FALSE: Abnormal status
Signal indicating output enable status
OTEN BOOL TRUE: Output is enabled
FALSE: Output is disabled
Character
PSWD Password character string (up to 16 single-byte characters)
constant
OUT OUT REAL Analog operation output value (0 to 100%)
n Description
Using an MOA function block, it is possible to monitor/change values of analog output variables
from an HIS.
The MOA function block has input parameters (SHDN and SDV) for receiving shutdown events
and outputs shutdown logic signals with the highest priority if a shutdown event occurs.
It is possible to switch between permitting and prohibiting manual operations from an HIS by the
input to SW. If TRUE is input to SW, the MOA function block outputs a manual operation output
value from the HIS to OUT. If FALSE is input to SW, it outputs the IN value as is to OUT.
Note that MOA outputs the actual value as is to OUT even if the shutdown output value (SDV) or
IN value are outside the range from 0 to 100%.
MOA has the following functions.
Shutdown signals output
Manual operation permission
Manual operation authenticated by password
Feedback
Output enable status display
OOP monitoring
CENTUM integration
SEE
ALSO For the shutdown output and manual operation permission functions, see the following:
n Overview of Processing MOA in D4.3.1, Operations of MOA from HIS
For the feedback function, see the following:
n Feedback Input in D4.3.1, Operations of MOA from HIS
For the OOP function, see the following:
n OOP Detection in D4.3.1, Operations of MOA from HIS
The output enable status display function is common with MOB_11 and MOB_21; see the following:
D4.1.3, Output Enable Status Display Function
The password function is common with MOB_11 and MOB_21; see the following:
D4.1.2, Password at Manual Operations
For more information about the CENTUM integration function, see the following:
D4.3.2, Tag Name Interfaces and Process Alarms of MOA
n Remarks
This function block can be used in new SCS databases created by SENG of R1.02.00 or later.
ANN
IN
C060101E.ai
Figure ANN
n Arguments
Table Arguments of ANN
IN/OUT Arguments Data type Description
IN IN BOOL Input value
n Description
The ANN function block generates annunciator messages when an HIS is connected.
It generates an annunciator message notifying that an alarm has been generated if the input
value (IN) changes from FALSE to TRUE. If the input value (IN) changes from TRUE to FALSE,
it generates an annunciator message notifying that the function block has recovered from the
alarm. Message character strings are specified in Tag Name Builder. The default value for IN
when starting an SCS is FALSE.
SEE
ALSO For more information about the annunciator message definition in Tag Builder, see the following:
2.1.4, Definition of Tag Names in the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
n Remarks
The ANN function block is an interference-free function block.
IN
TRP
ID
C060201E.ai
Figure SOE_B
n Arguments
Table Arguments of SOE_B
IN/OUT Arguments Data type Description
IN BOOL Input value
Trip signal specification
TRIP_NONE: Do not regard as a trip signal
TRP DINT
IN TRIP_OFF: Regard as a trip signal if IN changes from TRUE to FALSE
TRIP_ON: Regard as a trip signal if IN changes from FALSE to TRUE
Event identification character string constant (constant of up to 32
ID STRING
single-byte or 16 double-byte characters)
n Description
The SOE_B function block collects SOE data of BOOL type.
The SOE_B function block collects events at the timing when input value IN changes. If the trip
signal specification is set to a value other than TRIP_NONE, events collected with the SOE_B
function block are treated as trip signals. ID is event identification information and displayed in
SOE Viewer. Specify a character string (up to 32 single-byte or 16 double-byte characters) in
order to identify the event.
SEE
ALSO For the trip signals, see the following:
n Trip Signal in A7.3, Event Storage
n Remarks
The SOE_B function block is an interference-free function block. Specify a character string
constant for ID.
TRIP_NONE, TRIP_OFF and TRIP_ON have been defined in an SCS project in advance as
constants with the values 0, 1 and 2, respectively. Do not change predefined constants.
SOE_I
IN
TRIG
TRP
ID
C060301E.ai
Figure SOE_I
n Arguments
Table Arguments of SOE_I
IN/OUT Arguments Data type Description
IN DINT Input value
TRIG BOOL Trigger signal
Trip signal specification
IN TRIP_NONE: Do not regard as a trip signal
TRP DINT
TRIP_OFF: Triggers a trip signal when TRIG changes from TRUE to FALSE.
TRIP_ON: Triggers a trip signal when TRIG changes from FALSE to TRUE
Event identification character string constant (constant of up to 32 single-byte
ID STRING
or 16 double-byte characters)
n Description
The SOE_I function block collects SOE data of integer type.
The SOE_I function block collects events at the timing when the trigger signal value changes.
If the trip signal specification is set to TRIP_ON or TRIP_OFF, events collected with the SOE_I
function block are treated as trip signals. ID is event identification information and displayed on
SOE Viewer. Specify a character string (up to 32 single-byte or 16 double-byte characters) in
order to identify the event.
SEE
ALSO For the trip signals, see the following:
n Trip Signal in A7.3, Event Storage
n Remarks
The SOE_I function block is an interference-free function block. Specify a character string
constant for ID.
TRIP_NONE, TRIP_OFF and TRIP_ON have been defined in an SCS project in advance as
constants. Do not change already defined constants.
SOE_R
IN
TRIG
TRP
ID
C060401E.ai
Figure SOE_R
n Arguments
Table Arguments of SOE_R
IN/OUT Arguments Data type Description
IN REAL Input value
TRIG BOOL Trigger signal
Trip signal specification
IN TRIP_NONE: Do not regard as a trip signal
TRP DINT
TRIP_OFF: Triggers a trip signal when TRIG changes from TRUE to FALSE.
TRIP_ON: Triggers a trip signal when TRIG changes from FALSE to TRUE.
Event identification character string constant (constant of up to 32 single-byte
ID STRING
or 16 double-byte characters)
n Description
The SOE_R function block collects SOE data of real number type.
The SOE_R function block collects events at the timing when the trigger signal value changes.
If the trip signal specification is set to TRIP_ON or TRIP_OFF, events collected with the SOE_R
function block are treated as trip signals. ID is event identification information and displayed on
SOE Viewer. Specify a character string (up to 32 single-byte or 16 double-byte characters) in
order to identify the event.
SEE
ALSO For the trip signals, see the following:
n Trip Signal in A7.3, Event Storage
n Remarks
The SOE_R function block is an interference-free function block. Specify a character string
constant for ID.
TRIP_NONE, TRIP_OFF and TRIP_ON have been defined in an SCS project in advance as
constants. Do not change already defined constants.
LTFCS
GSV
STS
C060501E.ai
Figure LTFCS
n Arguments
Table Arguments of LTFCS
IN/OUT Arguments Data type Description
GSV BOOL Output value (value of %GS)
OUT Data status
STS BOOL TRUE: Normal
FALSE: Abnormal (including cases where data is not received)
n Description
LTFCS is a function block for receiving the link transmission data (Global Switches) sent from
FCSs (including APCS and GSGW) in the same domain.
The output parameter GSV outputs the BOOL type data of the received global switches.
The output parameter STS outputs the data status of the received link transmission data.
When a communication error occurs, GSV will output a fail-safe value previously specified on the
SCS Link Transmission Builder.
When the communication recovers from the erroneous status, the block will return to output the
receiving data. Create application logics for latching and unlatching the output to manage the
error occurrence.
n Remarks
The LTFCS function block is an interference-free function block.
This function block can be used in new SCS databases created by SENG of R1.03.00 or
later.
SCI_B
V
STS
C070101E.ai
Figure SCI_B
n Arguments
Table Arguments of SCI_B
IN/OUT Arguments Data type Description
V BOOL Data value
n Description
The SCI_B function block inputs the BOOL-type communication data and data status received
from subsystems to the application logic.
The data value (V) is a value input from a subsystem.
The data status (STS) indicates whether or not the data was acquired from the applicable
subsystem (*1). It becomes TRUE if the data was acquired, and FALSE if it could not be
acquired.
*1: Errors in subsystems, such as an error of a subsystems input terminal or wiring error between a subsystems input terminal and
a sensor, cannot be detected. These errors need to be handled in the applicable subsystem.
n Remarks
The SCI_B function block is an interference-free function block. Do not use it to input data to
safety loops.
The SCI_B is a function block that assumes use of communication inputs. Create instances
and wire them to communication inputs using the Communication I/O Builder.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
SEE
ALSO For more information about operation in SCS simulation test, see the following:
3.3, Execution of SCS Simulation Tests of the ProSafe-RS System Test Reference (IM 32S04B30-21E)
SCI_I
V
STS
C070201E.ai
Figure SCI_I
n Arguments
Table Arguments of SCI_I
IN/OUT Arguments Data type Description
V DINT Data value
OUT Data status
STS BOOL TRUE: GOOD (Communication data reception was successful)
FALSE: BAD (Communication data reception failed)
n Description
The SCI_I function block inputs the integer-type communication data and data status received
from subsystems to the application logic.
The data value (V) is a value input from a subsystem.
The data status (STS) indicates whether or not the data was acquired from the applicable
subsystem (*1). It becomes TRUE if the data was acquired, and FALSE if it could not be
acquired.
*1: Errors in subsystems, such as an error of a subsystems input terminal or wiring error between a subsystems input terminal and
a sensor, cannot be detected. These errors need to be handled in the applicable subsystem.
n Remarks
The SCI_I function block is an interference-free function block. Do not use it to input data to
safety loops.
The SCI_I is a function block that assumes use of communication inputs. Create instances
and wire them to communication inputs using the Communication I/O Builder.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
SEE
ALSO For more information about operation in SCS simulation test, see the following:
3.3, Execution of SCS Simulation Tests of the ProSafe-RS System Test Reference (IM 32S04B30-21E)
SCI_R
V
STS
C070301E.ai
Figure SCI_R
n Arguments
Table Arguments of SCI_R
IN/OUT Arguments Data type Description
V REAL Data value
OUT Data status
STS BOOL TRUE: GOOD (Communication data reception was successful)
FALSE: BAD (Communication data reception failed)
n Description
The SCI_R function block inputs the real number-type communication data and data status
received from subsystems to the application logic.
The data value (V) is a value input from a subsystem.
The data status (STS) indicates whether or not the data was acquired from the applicable
subsystem (*1). It becomes TRUE if the data was acquired, and FALSE if it could not be
acquired.
*1: Errors in subsystems, such as an error of a subsystems input terminal or wiring error between a subsystems input terminal and
a sensor, cannot be detected. These errors need to be handled in the applicable subsystem.
n Remarks
The SCI_R function block is an interference-free function block. Do not use it to input data to
safety loops.
The SCI_R is a function block that assumes use of communication inputs. Create instances
and wire them to communication inputs using the Communication I/O Builder.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
SEE
ALSO For more information about operation in SCS simulation test, see the following:
3.3, Execution of SCS Simulation Tests of the ProSafe-RS System Test Reference (IM 32S04B30-21E)
SCO_B
V RDBK
STS
C070401E.ai
Figure SCO_B
n Arguments
Table Arguments of SCO_B
IN/OUT Arguments Data type Description
IN V BOOL Data value
RDBK BOOL Reserved: Always FALSE
OUT Data status
STS BOOL TRUE: Communication with the subsystem was successful.
FALSE: Communication with the subsystem failed.
n Description
The SCO_B function block is used to output BOOL-type values of the application logic to
subsystems.
The data value (V) is a value output to a subsystem.
The data status (STS) indicates whether or not communication with the applicable
subsystem was successful (*1) (*2). It becomes TRUE if communication was successful,
and FALSE if communication failed.
*1: Errors in subsystems, such as an error of a subsystems output terminal or wiring error between a subsystems output terminal
and a device, cannot be detected. These errors need to be handled in the applicable subsystem.
*2: The data status becomes TRUE as long as communication was successful, even when the output enable operation is not yet
performed.
n Remarks
The SCO_B function block is an interference-free function block. Do not use it to input or
output data to/from safety loops.
The SCO_B is a function block that assumes use of communication outputs. Create
instances and wire them to communication outputs using the Communication I/O Builder.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
SCO_I
V RDBK
STS
C070501E.ai
Figure SCO_I
n Arguments
Table Arguments of SCO_I
IN/OUT Arguments Data type Description
IN V DINT Data value
RDBK DINT Reserved: Always 0
OUT Data status
STS BOOL TRUE: Communication with the subsystem was successful.
FALSE: Communication with the subsystem failed.
n Description
The SCO_I function block is used to output integer-type values of the application logic to
subsystems.
The data value (V) is a value output to a subsystem.
The data status (STS) indicates whether or not communication with the applicable
subsystem was successful (*1) (*2). It becomes TRUE if communication was successful,
and FALSE if communication failed.
*1: Errors in subsystems, such as an error of a subsystems output terminal or wiring error between a subsystems output terminal
and a device, cannot be detected. These errors need to be handled in the applicable subsystem.
*2: The data status becomes TRUE as long as communication was successful, even when the output enable operation is not yet
performed.
n Remarks
The SCO_I function block is an interference-free function block. Do not use it to input or
output data to/from safety loops.
The SCO_I is a function block that assumes use of communication outputs. Create
instances and wire them to communication outputs using the Communication I/O Builder.
When SCO_I is applied for outputting a 16-bit integer (singed 16-bit integer or unsigned
16-bit integer) as communication datum of an analog output, if the value set to the SCO_I
is beyond the range of the 16-bit integer, the value will not be written to the communication
output image area (for outputting to subsystem) and the data status (STS) will become
FALSE.
Range of 16-bit integer (communication data of analog output):
Singed 16-bit integer: -32768 to 32767
Unsigned 16-bit integer: 0 to 65535
It is necessary to scheme the applications, such as checking the STS signal, prevent from
setting the value that exceeds the range of 16-bit integer to SCO_I.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
SCO_R
V RDBK
STS
C070601E.ai
Figure SCO_R
n Arguments
Table Arguments of SCO_R
IN/OUT Arguments Data type Description
IN V REAL Data value
RDBK REAL Reserved: Always 0.0
OUT Data status
STS BOOL TRUE: Communication with the subsystem was successful.
FALSE: Communication with the subsystem failed.
n Description
The SCO_R function block is used to output real number-type values of the application logic to
subsystems.
The data value (V) is a value output to a subsystem.
The data status (STS) indicates whether or not communication with the applicable
subsystem was successful (*1) (*2). It becomes TRUE if communication was successful,
and FALSE if communication failed.
*1: Errors in subsystems, such as an error of a subsystems output terminal or wiring error between a subsystems output terminal
and a device, cannot be detected. These errors need to be handled in the applicable subsystem.
*2: The data status becomes TRUE as long as communication was successful, even when the output enable operation is not yet
performed.
n Remarks
The SCO_R function block is an interference-free function block. Do not use it to input or
output data to/from safety loops.
The SCO_R is a function block that assumes use of communication outputs. Create
instances and wire them to communication outputs using the Communication I/O Builder.
This function block can be used in new SCS databases created by SENG of R1.01.30 or
later.
The following figures illustrate the three types of external communication function blocks.
ECW_B
OUT
BOOL-type data
ECW_I
OUT
DINT-type data
ECW_R
OUT
REAL-type data
C080001E.ai
SEE
ALSO For more information about how to use external communication function blocks, see the following:
D5, Data Setting Using External Communication Function Blocks
n Description
The external communication function blocks are used to set data from the Modbus master via
Modbus slave connection or to set data in a CENTUM integration structure.
n Remarks
The external communication function blocks are interference-free function blocks. To use data
set with ECW_B, ECW_I and ECW_R function blocks in the safety functions, it is necessary to
incorporate Safety Measure (various functions for securing safety) with a user application.
SYS_STAT
RUN MODE
C090101E.ai
Figure SYS_STAT
n Arguments
Table Arguments of SYS_STAT
IN/OUT Arguments Data type Description
Output enable operation
IN RUN BOOL FALSE TRUE: Perform the output enable operation
Other: Nothing happens
Operating mode
OUT MODE DINT 3: Waiting mode
4: Running mode
n Description
The SYS_STAT system function block shows the operating status of an SCS.
The output enable operation on output modules is normally performed from an SENG, but it can
be performed from an application logic by using the SYS_STAT system function block. The SYS_
STAT system function block performs the output enable operation when RUN input changes from
FALSE to TRUE. Set RUN to FALSE if the output enable operation is not performed.
n Remarks
This function block does not affect the Output Enable status of subsystem communication. It only
affects safety outputs and outputs in inter-SCS safety communication immediately after an SCS
start.
SYS_FORCE
UNLK LOCK
CHKT NUM
FORC TUP
NOV
C090201E.ai
Figure SYS_FORCE
n Arguments
Table Arguments of SYS_FORCE
IN/OUT Arguments Data type Description
Forcibly cancel the forcing status of all variables
UNLK BOOL FALSE TRUE: Perform forced cancellation
Other: Nothing happens
IN Watching time of Forcing
CHKT TIME
0 may disable the watching timer
Maximum number of variables that can be forced at the same time
FORC DINT
FORC < 0 equivalent to FORC = 0
Existence of forced variables
LOCK BOOL FALSE: None
TRUE: At least one
NUM DINT Total number of forced variables
Indicates whether or not the locked status has continued exceeding the
OUT monitoring time
TUP BOOL
FALSE: The monitoring time is not exceeded
TRUE: The monitoring time is exceeded
Indicates whether or not the number of locked variables has exceeded
the maximum allowable number
NOV BOOL
FALSE: The maximum allowable number is not exceeded
TRUE: The maximum allowable number is exceeded
n Description
The SYS_FORCE system function block controls the forcing status.
l Input
UNLK is an input for forcibly cancelling the forced status of all variables. If UNLK changes
from FALSE to TRUE, all variables locked with the forcing function are forcibly unlocked. Set
UNLK to FALSE if this operation is not performed.
Specify the monitoring time of the forcing status for CHKT. If the status where one or
more variables are locked continues longer than the monitoring time specified by CHKT,
a diagnostic information message is generated to inform the user. Diagnostic information
messages are re-generated at intervals corresponding to the monitoring time specified by
CHKT.
Specify the maximum number of variables that can be locked at the same time for FORC.
If NUM becomes greater than FORC, a diagnostic information message is generated to
inform the user that the specified maximum number is exceeded. Note that if NUM becomes
equal to or smaller than FORC, a diagnostic information message notifying about the
recovery is generated.
l Output
LOCK is an output that indicates whether or not there are any variables that are locked.
LOCK becomes TRUE if any variable is locked.
NUM is the number of locked variables.
TUP is an output that indicates whether or not there are any variables that have remained
locked longer than the monitoring time specified by CHKT.
NOV is an output that indicates whether or not the number of locked variables has
exceeded the maximum allowable number specified by FORC.
n Remarks
The variables handled by this function block do not contain subsystem communication data.
SYS_FORCE_LT
UNLK LOCK
CHKT NUM
FORC TUP
NOV
C090301E.ai
Figure SYS_FORCE_LT
n Arguments
Table Arguments of SYS_FORCE_LT
IN/OUT Arguments Data type Description
Forcibly unlocks all the locked SCS Link Transmission data.
UNLK BOOL FALSE TRUE: Perform forced cancellation
Other: Nothing happens
Monitors the locked time of SCS link transmission data.
When the SCS link transmission data are locked for a time
CHKT TIME longer than CHKT time, a diagnostic information message will
IN be generated and sent to the user.
0 may disable this time monitoring.
Maximum number of stations that can be forced at the same time.
When the number of the stations locked SCS link transmission
FORC DINT data is greater than FORC, a diagnostic information message
will be generated and sent to the user. FORC < 0 equivalent to
FORC = 0
Existence of locked stations
LOCK BOOL FALSE: None
TRUE: At least one
NUM DINT Total number of locked stations
Indicates that the locked time has reached the time-up
OUT TUP BOOL FALSE: Before time-up
TRUE: After time-up
Indicates whether or not the number of locked stations has
exceeded the maximum allowable number
NOV BOOL
FALSE: The maximum allowable number is not exceeded
TRUE: The maximum allowable number is exceeded
n Description
SYS_FORCE_LT is a function block for forcing management of SCS link transmission data.
l Input
UNLK is an input terminal for the signal to unlocking all the locked SCS link transmission
data. When UNLK changes from FALSE to TRUE, all the locked data of the stations will be
forcibly unlocked. Set FALSE to UNLK, if unlocking will not be performed.
Specify the monitoring time of the locking status to CHKT. If the status where one or
more stations are locked continues longer than the monitoring time specified by CHKT, a
diagnostic information message is generated to inform the user. Diagnostic information
messages are re-generated at intervals corresponding to the monitoring time specified by
CHKT.
FORC is used as the maximum number of simultaneously locked SCS link transmission
data of a station.
If NUM becomes greater than FORC, a diagnostic information message is generated to
inform the user that the specified maximum number is exceeded. Note that if NUM becomes
equal to or smaller than FORC, a diagnostic information message notifying about the
recovery is generated.
l Output
LOCK is used to indicate if there is any station that contains the locked SCS link
transmission data. Even a single locked station exists, LOCK will be come TRUE.
NUM indicates the number of locked stations. This is the number of all the locked stations
including the sending and receiving stations. A station means either FCS or SCS.
TUP indicates the status that the locked time at least in one station has exceeded the set
value of CHKT.
NOV is an output that indicates whether or not the number of locked stations has exceeded
the maximum allowable number specified by FORC.
n Remarks
This system function block can be used in new SCS databases created by SENG of R1.03.00 or
later.
SYS_FORCE_BD
UNLK LOCK
CHKT NUM
FORC TUP
NOV
C090401E.ai
Figure SYS_FORCE_BD
n Arguments
Table Arguments of SYS_FORCE_BD
IN/OUT Arguments Data type Description
Forcibly cancel locking of all function blocks for inter-SCS safety
communication
UNLK BOOL
From FALSE to TRUE: Forcibly cancel
Other: Do nothing
Monitoring time of locking status of function block for inter-SCS safety
communication. If the time elapsed after locking inter-SCS safety function
CHKT TIME
IN block exceeds CHKT, a diagnostic information message is notified to the
user. If 0 is specified, exceeded time is not checked.
The maximum number of stations for which locking is permitted at the same
time. If the number of stations whose inter-SCS safety communication
FORC DINT function block is locked exceeds FORC, the fact is notified to the user
via diagnostic information messages. If FORC < 0 is specified, the block
functions as if FORC = 0 is specified.
Presence of locked stations
LOCK BOOL FALSE: None
TRUE: 1 or more stations
NUM DINT The total number of locked stations
Indicates if the elapsed time after locking exceeds the monitoring time
OUT (CHKT)
TUP BOOL
FALSE: Not exceeded
TRUE: Exceeded
Indicates if the number of locked stations exceeds the maximum allowed
number (FORC)
NOV BOOL
FALSE: Not exceeded
TRUE: Exceeded the allowed maximum number
n Description
The SYS_FORCE_BD function block is used to manage the lock status of inter-SCS safety
communication function blocks.
l Input
UNLK is an input to forcibly cancel the lock status of all inter-SCS safety communication
function blocks. If the value of UNLK changes from FALSE to TRUE, all locked stations
are forcibly unlocked. UNLK should remain at FALSE if it is desired not to perform forced
cancellation.
Specify the time to monitor lock status for CHKT. If there is at least one station where the
inter-SCS safety communication function blocks are locked for a period longer than the
monitoring time specified for CHKT, the condition is notified to the user via a diagnostic
information message. Diagnostic information messages are resent at the interval of the
monitoring time specified for CHKT if the inter-SCS safety communication function blocks
remain locked. If CHKT = 0, the elapsed time after locking is not monitored.
For FORC, specify the maximum number of stations whose inter-SCS safety
communication function blocks can be locked at the same time. If NUM becomes greater
than FORC, a diagnostic information message is generated to notify that the specified
maximum number is exceeded. Note that when NUM returns to equal to FORC or smaller, a
diagnostic information message indicating recovery is notified.
l Output
LOCK is an output indicating whether or not any station has locked inter-SCS safety
communication function blocks. If any station is locked, the value of LOCK becomes TRUE.
NUM indicates the number of locked stations.
TUP becomes TRUE if there is at least one station with inter-SCS safety communication
function blocks that continue to be locked for a period longer than the monitoring time
specified with CHKT.
NOV becomes TRUE if the number of locked stations exceeded the maximum allowed
number specified with FORC.
n Remarks
This system function block can be used in new SCS databases created by SENG of R2.03.00 or
later.
SYS_LTSTS
STN STS
DIAG
PALM
C090501E.ai
Figure SYS_LTSTS
n Arguments
Table Arguments of SYS_LTSTS
IN/OUT Arguments Data type Description
IN STN DINT The station number (1 to 64) of the monitored station
Indicates the reception data status
STS BOOL TRUE: GOOD
FALSE: BAD
Diagnosis notification on the reception station
OUT DIAG BOOL TRUE: Communication data error occurred
FALSE: Communication data error not occurred
Transmission delay pre-alarm on the reception station
PALM BOOL TRUE: Transmission delay occurred
FALSE: Transmission delay not occurred
n Description
SYS_LTSTS is a function block for monitoring the reception status of SCS link transmission data
of a station.
l Input
A station number (1 to 64) needs to be specified for STN.
When a number smaller than 1 or greater than 64 is specified, the STS will become FALSE,
DIAG will become TRUE and PALM will become FALSE.
l Output
STS indicates the data status of logical data in link transmission data area.
The data status output from STS is the same as the output of STS in LTFCS and LTRCV
blocks.
The STS will be held when the link transmission data of the designated station are locked.
DIAG indicates the diagnosis result for the SCS link transmission data input to the station.
The reception status of the link transmission data will be indicated by DIAG regardless if the
SCS link transmission data are locked or not.
PALM is the pre-alarm of SCS link transmission delay. This alarm is initiated before the
delay reaches the time-up value (DLYT).
To initiate the pre-alarm, set the value of the pre-alarm (PALT) on the SCS Link
Transmission Builder.
When the SCS link transmission delay reaches PALT, PALM will become TRUE. If PALT is
set with 0, the pre-alarm will be disabled. Thus PALM will be fixed as FALSE.
l If the Specified Station is not Defined as Receive Station (including the local
station)
If a station not defined as a receiving station on SCS Link Transmission Builder is specified, the
STS will become FALSE, DIAG will become TRUE and PALM will become FALSE.
n Remarks
This system function block can be used in new SCS databases created by SENG of R1.03.00 or
later.
SYS_DIAG
DIAG
IOER
VNER
IRER
CMER
OTER
C090601E.ai
Figure SYS_DIAG
n Arguments
Table Arguments of SYS_DIAG
IN/OUT Arguments Data type Description
Presence of errors in the entire system, other than users operation
mistakes
DIAG BOOL
FALSE: Normal status
TRUE: Abnormal status
Presence of I/O related errors
IOER BOOL FALSE: Normal status
TRUE: Abnormal status
Presence of control bus related errors
VNER BOOL FALSE: Normal status
TRUE: Abnormal status (communication impossible)
OUT Presence of IRIG-B related errors (fixed to FALSE if IRIG-B is not
specified for the time synchronization method)
IRER BOOL
FALSE: Normal status
TRUE: Abnormal status
Presence of inter-SCS safety communication errors (Consumer error
only) or SCS Link Transmission errors
CMER BOOL
FALSE: Normal status
TRUE: Abnormal status
Presence of other errors
OTER BOOL FALSE: Normal status
TRUE: Abnormal status
n Description
The SYS_DIAG system function block detects the presence of errors in the entire system, other
than users operation mistakes. It outputs the current status regardless of the operations in the
Diagnostic Information window of the SENG.
DIAG indicates the presence of errors in the entire system. This output is the logical OR of
all other output arguments.
IOER indicates presence of errors related to inputs and outputs (including all AIO/DIO
modules and communication modules). It indicates abnormal status (TRUE) if nodes or
input/output modules do not exist as defined as well.
VNER indicates the presence of errors related to the control bus communication. It indicates
TRUE (communication failure) if the control bus communication has completely failed.
SEE
ALSO For detecting the abnormality on each bus of the redundant buses, SYS_NETST can be used. For more
information, see the following:
C10.4, SYS_NETST (Control Bus Status Indicator)
IRER indicates the presence of errors related to IRIG-B. It indicates normal status (FALSE)
if IRIG-B is not specified for the time synchronization method.
CMER indicates the presence of errors in inter-SCS safety communication and SCS link
transmission.
If all the reception data of inter-SCS safety communication consumer FBs are normal
(*1) and all the reception data of SCS link transmission are normal (*2), CMER will output
FALSE (normal status).
*1: It takes it as normal when the consumer side does not have any consumer FB.
*2: It takes it as normal when the reception of SCS link transmission is not defined. SCS link transmission includes SCS link
transmission safety communication and SCS global switch communication.
OTER indicates the presence of other errors (*1). It indicates abnormal status (TRUE) if
HKU does not exist as defined as well.
*1: If CPU modules are redundantly configured, one module shows failure.
FAN is abnormal (If FAN exists in the configuration).
CPU node IN/OUT temperature is abnormal.
Battery is abnormal.
Battery switch is off.
n Remarks
Use SYS_FORCE system function blocks to detect users mistakes in lock operations, SYS_
OVR system function blocks to detect mistakes in override operations, SYS_PSWD system
function blocks to detect mistakes in operating switches with passwords, and SYS_SECURE
system function blocks to detect operation mistakes at the security level.
Any error status can be detected by referencing the SYS_DIAG system function block with the
system function blocks described above.
SYS_SECURE
RST LVL
CHKT TUP
C090701E.ai
Figure SYS_SECURE
n Arguments
Table Arguments of SYS_SECURE
IN/OUT Arguments Data type Description
RST BOOL Security level reset input (reset only at change from FALSE to TRUE)
IN Watching time of Security level
CHKT TIME
0 may disable the watching timer
LVL DINT Current security level
OUT Security level monitoring time overrun
TUP BOOL FALSE: The monitoring time is not exceeded
TRUE: The monitoring time is exceeded
n Description
The SYS_SECURE system function block controls the security level of an SCS.
The SYS_SECURE system function block monitors the security level. If Level1 continues
longer than the monitoring time specified by input argument CHKT, the SYS_SECURE system
function block generates a diagnostic information message and sets TUP to TRUE. Diagnostic
information messages are regenerated at intervals corresponding to the monitoring time
specified by CHKT as long as Level1 continues.
n Remarks
The status of security level 0 (offline level) is not monitored.
SYS_SEC_CTL
FIX STS
C090801E.ai
Figure SYS_SEC_CTL
n Arguments
Table Arguments of SYS_SEC_CTL
IN/OUT Arguments Data type Description
Specifies whether or not to disable security level
change.
TRUE: Disable change operations via password entry
IN FIX BOOL
from the SENG.
FALSE: Enable change operations via password entry
from the SENG.
Indicates whether or not security level change via
password entry is disabled.
OUT STS BOOL
TRUE: Security level change is disabled.
FALSE: Security level change is enabled.
n Description
The SYS_SEC_CTL system function block can be used to disable operations to change the
security level of a given SCS via password entry from the SENG. This system function block
permits stricter control of security-level change operations targeting SCS.
If the input parameter FIX of the SYS_SEC_CTL system function block is TRUE, all
attempts to change the security level via password entry from the SENG are disabled. The
applicable SCS returns an error to SENG from which a security-level change request was
received.
The SYS_SEC_CTL system function block also controls security level reset to level 2.
Changing the security level of a given SCS via password entry from the SENG is actually
enabled or disabled from the next scan period after the FIX value was changed.
Enabling/disabling of security-level change operations is notified by a diagnostic information
message.
Even when security-level change operations via password entry are disabled, passwords
assigned for security level change can still be changed.
n Remarks
Whether security level changes via password entry from the SENG are enabled or disabled
is not notified on the SCS State Management Window.
Even when security level changes to an SCS are disabled by the SYS_SEC_CTL system
function block, the security level of the SCS can still be reset to level 2 using the RST input
from the SYS_SECURE system function block or via the restart switch operation of the CPU
module.
This system function block can be used in new SCS databases created by SENG of
R1.01.30 or later.
SYS_OVR
UNOV OVR
CKTO NUMO
OVRC TUPO
CKTS
NOVO
SWC
SWON
NUMS
TUPS
NOVS
C090901E.ai
Figure SYS_OVR
n Arguments
Table Arguments of SYS_OVR
IN/OUT Arguments Data type Description
Override forced cancellation command (only at change from FALSE to
UNOV BOOL
TRUE)
Time to monitor existence of instances in the override status. CKTO=0
CKTO TIME
disables the watching timer
Maximum number of instances that can be placed in the override
OVRC DINT status at the same time
IN
OVRC < 0 equivalent to OVRC = 0
Time to monitor existence of instances in the status where override
CKTS TIME
operation is allowed. CKTS=0 disables the watching timer
Maximum number of instances that can be placed in the status where
SWC DINT override operation is allowed at the same time
SWC < 0 equivalent to SWC = 0
Indicates whether or not any instances are in the override status
OVR BOOL FALSE: None
TRUE: At least one instance
NUMO DINT Number of instances in the override status
Indicates whether or not any instances have been in the override
status longer than the monitoring time
FALSE: There are no instances in the override status exceeding the
TUPO BOOL
monitoring time
TRUE: There are instances in the override status exceeding the
monitoring time
Indicates whether or not the number of instances in the override status
at the same time exceeds the maximum number
NOVO BOOL
FALSE: The maximum number is not exceeded
TRUE: The maximum number is exceeded
OUT Indicates whether or not any instances are in the status where override
operation is allowed
SWON BOOL
FALSE: None
TRUE: At lease one instance
NUMS DINT Number of instances in the status where override operation is allowed
Indicates whether or not any instances have been in the status where
override operation is allowed longer than the monitoring time
FALSE: There are no instances in the status where override operation
TUPS BOOL
is allowed exceeding the monitoring time
TRUE: There are instances in the status where override operation is
allowed exceeding the monitoring time
Indicates whether or not the number of instances in the status where
override operation is allowed at the same time exceeds the maximum
NOVS BOOL number
FALSE: The maximum number is not exceeded
TRUE: The maximum number is exceeded
n Description
The SYS_OVR system function block is used to manage all instances of override function blocks
and grouping override function blocks within an SCS. It allows forced cancellation of the override
status, alarm setting for the override operation and status output.
SEE
ALSO For more information about the actions of the parameters, see the following:
D3.5, Status Management of Function Blocks Used for Override
SYS_PSWD
UNPW PSWD
CHKT NUM
PSWC TUP
NOV
C091001E.ai
Figure SYS_PSWD
n Arguments
Table Arguments of SYS_PSWD
IN/OUT Arguments Data type Description
Forcibly sets the OUT outputs of all password function block instances
UNPW BOOL
to FALSE (only at change from FALSE to TRUE)
Time to monitor the status where active password function block
CHKT TIME instances outputs TRUE from the OUT output
IN
0 disables the watching timer
Maximum number of active password function block instances that can
PSWC DINT output TRUE from the OUT output at the same time
PSWC < 0 equivalent to PSWC = 0
Indicates whether or not there are any active password function block
instances that output TRUE from the OUT output
PSWD BOOL
FALSE: None
TRUE: At least one FB
Total number of active password function block instances that output
NUM DINT
TRUE from the OUT output
Flag indicating whether or not a password function block instance has
been outputting TRUE from the OUT output longer than the monitoring
OUT time specified by CHKT
TUP BOOL FALSE: There are no password function block instances outputting
TRUE longer than the monitoring time
TRUE: There are password function block instances outputting TRUE
longer than the monitoring time
Flag indicating whether or not the number of active password function
block instances outputting TRUE from the OUT output exceeds the
NOV BOOL maximum number specified by PSWC
FALSE: The maximum number is not exceeded
TRUE: The maximum number is exceeded
n Description
The SYS_PSWD system function block is used to manage all instances of the password function
blocks. It allows forced cancellation of the OUT output of all instances, alarm setting for instance
operation and status output.
If UNPW changes from FALSE to TRUE, the OUT outputs of all instances of the password
function blocks are forcibly set to FALSE. Each instance whose OUT output was changed
generates a system alarm.
PSWD indicates whether or not there are password function block instances that output
TRUE from the OUT output.
NUM outputs the number of password function block instances that output TRUE from the
OUT output.
Specify the maximum number of password function block instances that can output TRUE
from the OUT output at the same time for PSWC. A system alarm is generated if NUM
becomes greater than PSWC. Although a system alarm is generated, it is still possible for
more instances to output TRUE than the maximum number specified by PSWC. If NUM
becomes equal to or smaller than PSWC, a system alarm notifying about the recovery is
generated.
NOV indicates whether or not more password function block instances than the maximum
number specified by PSWC output TRUE from OUT.
A system alarm is generated if the status where at least one password function block
instance outputs TRUE from the OUT output continues longer than the monitoring time
specified by CHKT. System alarms are re-generated at intervals corresponding to the
monitoring time specified for CHKT if this status continues.
TUP indicates whether or not there are password function block instances that have been
outputting TRUE from OUT longer than the monitoring time specified by CHKT.
SYS_ALLSD
NTRG
C091101E.ai
Figure SYS_ALLSD
n Arguments
Table Arguments of SYS_ALLSD
IN/OUT Arguments Data type Description
Shutdown execution switch
IN NTRG BOOL TRUE: Do not shut down
FALSE: Shut down
n Description
A SYS_ALLSD system function block shuts down all output channels of safety output modules
defined in a station at the same time.
Shutdown is not executed as long as TRUE is input to NTRG. However, as soon as the value of
NTRG changes from TRUE to FALSE, all output channels in a station are shut down at once.
As long as FALSE is input to NTRG, all the target output channels are placed in disable status
and all output modules output Output value at fault. Output enable operation is not executed as
long as FALSE is input to NTRG; instead, the output disable status is retained.
n Remarks
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
The targets of shutdown are limited to safety output modules (AO and DO) only. This system
function block has no effect on modules other than AO and DO. SYS_ALLSD does not
operate if no output modules are defined in I/O Wiring View.
The shutdown processing is not performed on channels of safety output modules that are
locked even if the value of NTRG changes from TRUE to FALSE. The current output value
is retained for these channels. If the value of an output variable of a locked output module is
changed via forcing, the changed value is output.
SYS_IOSD
NTRG
NODE
SLOT
C091201E.ai
Figure SYS_IOSD
n Arguments
Table Arguments of SYS_IOSD
IN/OUT Arguments Data type Description
Shutdown execution switch
NTLG BOOL TRUE: Do not shut down
FALSE: Shut down
IN
NODE DINT Node number (1 to 14)
SLOT DINT Output module installation slot number (1 to 8)
n Description
A SYS_IOSD system function block shuts down all output channels of a safety output module
specified by a node number (NODE) and slot number (SLOT) at the same time.
Shutdown is not executed as long as TRUE is input to NTRG. However, as soon as the value
of NTRG changes from TRUE to FALSE, all output channels of the specified output module are
shut down at once.
As long as FALSE is input to NTRG, all the target output channels are placed in disable status
and this module outputs the Output value at fault. Output enable operation is not executed as
long as FALSE is input to NTRG; instead, the output disable status is retained.
Define only one SYS_IOSD system function block in the case of redundant output modules.
In order to shut down redundant output modules, specify an odd slot number. By default, a
SYS_IOSD system function block shuts down an output module that has the control right.
n Remarks
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
The targets of shutdown are limited to safety output modules (AO and DO) only. This
system function block has no effect on modules other than AO and DO. SYS_IOSD does
not operate if the specified module is not defined in I/O Wiring View.
If the value of NTRG changes from TRUE to FALSE while a safety output module is locked,
the shutdown processing is not performed. The current output value is retained for that
output module. If the value of an output variable of a locked output module is changed via
forcing, the changed value is output.
SYS_IOALLST
NRO
NRI
C091301E.ai
Figure SYS_IOALLST
n Arguments
Table Arguments of SYS_IOALLST
IN/OUT Arguments Data type Description
Indicates whether or not the data statuses of all output channels are
normal
NRO BOOL
TRUE: All channels are normal
FALSE: At least one channel is abnormal
OUT
Indicates whether or not the data statuses of all input channels are
normal
NRI BOOL
TRUE: All channels are normal
FALSE: At least one channel is abnormal
n Description
The SYS_IOALLST system function block indicates the data status of all input channels and all
output channels of all AIO/DIO modules of an SCS. The SYS_IOALLST system function block
can be used when creating applications that treat errors in one or more channels as demands.
NRO indicates whether or not the data statuses of all output channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are excluded
from the targets of judgment.
NRI indicates whether or not the data statuses of all input channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are excluded
from the targets of judgment. The statuses of communication modules are ignored.
*1: Channels not used refer to channels to which input/output variables are not assigned.
n Remarks
The SYS_IOALLST system function block references the data status of the logical data of input/
output variables. For this reason, the outputs of the SYS_IOALLST system function block are
affected by the lock operation of modules. Please be aware that if modules/channels and input/
output variables are locked, the outputs may differ from the physical states.
SYS_NODEST
NODE NRO
NRI
C091401E.ai
Figure SYS_NODEST
n Arguments
Table Arguments of SYS_NODEST
IN/OUT Arguments Data type Description
IN NODE DINT Node number (1 to 14)
Indicates whether or not the data statuses of all output channels
within the node are normal
NRO BOOL
TRUE: All channels are normal
FALSE: At least one channel is abnormal
OUT
Indicates whether or not the data statuses of all input channels within
the node are normal
NRI BOOL
TRUE: All channels are normal
FALSE: At least one channel is abnormal
n Description
The SYS_NODEST system function block indicates the data status of all input channels and
all output channels of AIO/DIO modules within the specified node. The SYS_NODEST system
function block can be used when creating applications that treat errors in one or more channels in
the specified node as demands.
NRO indicates whether or not the data statuses of all output channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are excluded
from the targets of judgment.
NRI indicates whether or not the data statuses of all input channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are excluded
from the targets of judgment. The statuses of communication modules are ignored.
*1: Channels not used refer to channels to which input/output variables are not assigned.
n Remarks
The SYS_NODEST system function block references the data status of the logical data of input/
output variables. For this reason, the outputs of the SYS_NODEST system function block are
affected by the lock operation of modules. Please be aware that if modules/channels and input/
output variables are locked, the outputs may differ from the physical states.
If no node corresponds to the node number specified to IN, the outputs of NRO and NRI will
become FALSE to indicate error.
SYS_OUTST
NODE NRAL
SLOT NROR
CH1
CH2
CH3
CH4
CH5
CH6
CH7
CH8
C091501E.ai
Figure SYS_OUTST
n Arguments
Table Arguments of SYS_OUTST
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Slot number of the output module (1 to 8)
Indicates whether or not the data statuses of all channels are normal
NRAL BOOL TRUE: All channels are normal
FALSE: At least one channel is abnormal
Indicates whether or not the data status of one or more channels is
normal
NROR BOOL
TRUE: At least one channel is normal
FALSE: All channels are abnormal
Indicates the data status of CH1
OUT CH1 BOOL TRUE: GOOD
FALSE: BAD
Indicates the data status of CH2
CH2 BOOL TRUE: GOOD
FALSE: BAD
: :
Indicates the data status of CH8
CH8 BOOL TRUE: GOOD
FALSE: BAD
n Description
The SYS_OUTST system function block indicates the data status of all channels of the specified
output module.
l Input
Specify a value in the range from 1 to 8 for the slot number (SLOT). Specify an odd slot number
for redundant output modules. The SYS_OUTST system function block indicates the status of
the output module with the control right. Define only one SYS_OUTST system function block
even when output modules are placed in redundant configuration.
l Output
NRAL indicates whether or not the data statuses of all channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are
excluded from the test object.
NROR indicates whether or not the data status of at least one channel is normal. It only
becomes FALSE if the data statuses of all the channels are abnormal. Channels not used
(*1) are excluded from the test object.
CH1 to CH8 indicate the data status of each channel. Abnormal status (FALSE) is output for
channels not used (*1).
*1: Channels not used are the channels to which input/output variables are not assigned.
If a 4-channel output module is specified, CH5 to CH8 are treated as unused channels as well.
n Remarks
The SYS_OUTST system function block references the data status of the logical data of output
variables. For this reason, the outputs of the SYS_OUTST system function block are affected by
the lock operation of modules. Please be aware that if modules/channels and output variables
are locked, the outputs may differ from the physical data status.
If no module is defined in the specified position, or if the defined module is not an output module
or is a communication module, the abnormal status (FALSE) will be output to NRAL, NROR and
CH1 to CH8. Use a SYS_INST or SYS_CHST system function blocks for input modules.
SYS_OUTST16
NODE NRAL
SLOT NROR
CH1
CH2
CH3
CH4
CH5
CH6
CH7
CH8
CH9
CH10
CH11
CH12
CH13
CH14
CH15
CH16
C091601E.ai
Figure SYS_OUTST16
n Arguments
Table Arguments of SYS_OUTST16
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Output module installation slot number (1 to 8)
Whether or not the data statuses of all channels are normal
NRAL BOOL TRUE: All channels are normal
FALSE: At least one channel is abnormal
Whether or not the data status of at least 1 channel is normal
NROR BOOL TRUE: At least one channel is normal
FALSE: All channels are abnormal
Indicates the data status of CH1
CH1 BOOL TRUE: GOOD
OUT FALSE: BAD
Indicates the data status of CH2
CH2 BOOL TRUE: GOOD
FALSE: BAD
: :
Indicates the data status of CH16
CH16 BOOL TRUE: GOOD
FALSE: BAD
n Description
A SYS_OUTST16 system function block outputs the data statuses of all channels of an output
module specified by a node number and slot number. Use this FB for 16-channel output modules.
n Input
Specify a value in the range from 1 to 8 for the slot number (SLOT). Specify an odd slot number
for redundant output modules. A SYS_OUTST16 system function block outputs the status of an
output module that has the control right. Define only one SYS_OUTST16 system function block
in the case of redundant output modules.
n Output
NRAL indicates whether or not the data statuses of all channels are normal. It outputs TRUE
if the data statuses of all channels are normal. The data statuses of unused channels (*1)
are not judged.
NROR indicates whether or not the data status of at least one channel is normal. It outputs
FALSE only if the data statuses of all channels are abnormal. The data statuses of unused
channels (*1) are not judged.
CH1 to CH16 output data status of each channel. They output FALSE for unused channels
(*1).
*1: Unused channels are the channels to which no output variable is assigned.
Under the following circumstances, some channels may be treated as unused channels.
CH5 to CH16 channels will be treated as unused channels if a 4-channel output module is specified.
CH9 to CH16 channels will be treated as unused channels if an 8-channel output module is specified.
n Remarks
A SYS_OUTST16 system function block refers to the data status of logical data of an
output variable. For this reason, the output of the SYS_OUTST16 system function block is
influenced by module lock operation. Note that the output value may be different if a module,
channel or output variable is locked, compared to when it is not locked.
FALSE is output to NRAL, NROR and CH1 to CH16 if a module is not defined in the
specified location in I/O Wiring View, or the specified module is not an output module, e.g., a
communication module. Use SYS_INST or SYS_CHST for input modules.
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
SYS_INST
NODE NRAL
SLOT NROR
C091701E.ai
Figure SYS_INST
n Arguments
Table Arguments of SYS_INST
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Input module mounting slot number (1 to 8)
Indicates whether or not the data statuses of all channels are normal
NRAL BOOL TRUE: All channels are normal
FALSE: At least one channel is abnormal
OUT Indicates whether or not the data status of one or more channels is
normal
NROR BOOL
TRUE: At least one channel is normal
FALSE: All channels are abnormal
n Description
The SYS_INST system function block indicates the representative data status of all channels of
the specified input module.
l Input
Specify a value in the range from 1 to 8 for the slot number (SLOT). Specify an odd slot number
for redundant input modules. The SYS_INST system function block indicates the status of the
input module with the control right. Define only one SYS_INST system function block even when
input modules are placed in redundant configuration.
l Output
NRAL indicates whether or not the data statuses of all channels are normal. It becomes
TRUE if the data statuses of all the channels are normal. Channels not used (*1) are
excluded from the targets of judgment.
NROR indicates whether or not the data status of at least one channel is normal. It only
becomes FALSE if the data statuses of all the channels are abnormal. Channels not used
(*1) are excluded from the targets of judgment.
*1: Channels not used are the channels to which input variables are not assigned.
n Remarks
The SYS_INST system function block references the data status of the logical data of input
variables. For this reason, the outputs of the SYS_INST system function block are affected by
the lock operation of modules. Please be aware that if modules/channels and input variables are
locked, the outputs may differ from the physical data status.
If no module is present in the specified position, or if the present module is not an input module
or is a communication module, the abnormal status (FALSE) will be output to NRAL and NROR.
Use a SYS_OUTST or SYS_CHST system function blocks for output modules.
SYS_CHST
NODE Q
SLOT
CHNO
C091801E.ai
Figure SYS_CHST
n Arguments
Table Arguments of SYS_CHST
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN SLOT DINT AIO/DIO module mounting slot number (1 to 8)
CHNO DINT Channel number (1 to 16)
Data status of the channel
OUT Q BOOL TRUE: GOOD
FALSE: BAD
n Description
The SYS_CHST system function block indicates the data status of the specified channel of the
specified AIO/DIO module. If a communication module is specified, FALSE will be output.
l Input
Specify a value in the range from 1 to 8 for the slot number (SLOT). Specify an odd slot
number for redundant AIO/DIO modules. The SYS_CHST system function block indicates
the status of the AIO/DIO module with the control right.
Specify a value in the range from 1 to 16 for the channel number (CHNO).
l Output
Q indicates the data status of the specified channel. If a nonexistent channel is specified, Q
indicates abnormal status (FALSE). Q also indicates abnormal status (FALSE) for channels not
used (*1).
*1: Channels not used refer to channels to which input/output variables are not assigned.
n Remarks
The SYS_CHST system function block references the data status of the logical data of input/
output variables. For this reason, the outputs of the SYS_CHST system function block are
affected by the lock operation of modules. Please be aware that if modules/channels and input/
output variables are locked, the outputs may differ from the physical data status.
SYS_OUTEN
NODE CH1
SLOT CH2
CH3
CH4
CH5
CH6
CH7
CH8
CH9
CH10
CH11
CH12
CH13
CH14
CH15
CH16
C091901E.ai
Figure SYS_OUTEN
n Arguments
Table Arguments of SYS_OUTEN
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Output module installation slot number (1 to 8)
Output enable/output disable status of CH1
CH1 BOOL TRUE: Output enabled
FALSE: Output disabled
Output enable/output disable status of CH 2
CH2 BOOL TRUE: Output enabled
OUT FALSE: Output disabled
: :
Output enable/output disable status of CH16
CH16 BOOL TRUE: Output enabled
FALSE: Output disabled
n Description
A SYS_OUTEN system function block outputs output enable/output disable status of a 16-
channel output module. If an 8-channel output module is specified, outputs from CH1 to CH8 are
enabled. Outputs from CH9 to CH16 are disabled and output disabled (FALSE) is always output.
n Input
Specify a value in the range from 1 to 8 for the slot number (SLOT). Specify an odd slot number
for redundant output modules. A SYS_OUTEN system function block outputs the status of an
output module that has the control right. Define only one SYS_OUTEN system function block in
the case of redundant output modules.
n Output
A SYS_OUTEN system function block outputs output enable/output disable status of each
channel. Depending on the specified modules, some of the output terminals may be disabled
(FALSE).
If 16-channel, 8-channel or 4-channel output module is specified, SYS_OUTEN outputs the
followings.
16-channel output module
For CH1 to CH16, the output enable/output disable status of each channel is output. Output
disabled (FALSE) is output for channels to which no output variable is assigned.
8-channel output module
- Use the output values of CH1 to CH8. Outputs from CH9 to CH16 are disabled.
- For CH1 to CH8, the output enable/output disable status of each channel is output.
Output disabled (FALSE) is output for channels to which no output variable is assigned.
- Output disabled (FALSE) is always output for CH9 to CH16.
4-channel output module
- Use the output values of CH1 to CH4. Outputs from CH5 to CH16 are disabled.
- For CH1 to CH4, the output enable/output disable status of each channel is output.
Output disabled (FALSE) is output for channels to which no output variable is assigned.
- Output disabled (FALSE) is always output for CH5 to CH16.
n Remarks
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
The targets of SYS_OUTEN are limited to safety output modules (AO and DO) only. It
outputs output disabled (FALSE) for modules other than AO and DO.
Output enable operation for output modules are normally performed from a SENG, but this
is also possible via the application logic using SYS_STAT.
IMPORTANT
When the SYS_CERR function block is executed within a user-defined function block, if an
access to outside array range error occurs before executing SYS_CERR in that function block,
SYS_CERR is not executed. Be careful about the execution order of SYS_CERR if it is used in a
user-defined function block.
SYS_CERR
DIVZ
CHKT XARR
FOVF
COVF
C092001E.ai
Figure SYS_CERR
SEE
ALSO For the SCS behavior when an abnormal calculation occurs, see the following:
B6.1.3, Behavior at Abnormal Calculation
n Arguments
Table Arguments of SYS_CERR
IN/OUT Arguments Data type Description
Computation error re-warning interval
No re-warning is generated if 0 is specified.
IN CHKT TIME
The default re-warning interval when SYS_CERR is not created is 10
minutes.
Presence of POU with division-by-zero error
DIVZ BOOL FALSE: There are no POUs with division-by-zero error.
TRUE: There are POUs with division-by-zero error.
Presence of POU with access to the outside of an array error
FALSE: There are no POUs with access to the outside of an array
XARR BOOL
error.
OUT TRUE: There are POUs with access to the outside of an array error.
Presence of POU with overflow in floating-point calculation
FOVF BOOL FALSE: There are no POUs with overflow in floating-point calculation.
TRUE: There are POUs with overflow in floating-point calculation.
Presence of POU with overflow in casting
COVF BOOL FALSE: There are no POUs with overflow in casting.
TRUE: There are POUs with overflow in casting.
n Description
The SYS_CERR function block checks computation error conditions. Its output parameters allow
checking occurrence conditions of each computation error type. If one or more computation
errors occur within the SCS, the condition is notified via diagnostic information messages in
10-minute interval by default. The re-warning interval can be changed using the input parameter
CHKT.
n Remarks
This system function block can be used in new SCS databases created by SENG of R2.03.00 or
later.
SYS_SCANEXT
CHKT EXT
ESCA
OSCA
C092101E.ai
Figure SYS_SCANEXT
n Arguments
Table Arguments of SYS_SCANEXT
IN/OUT Arguments Data type Description
Re-warning interval when the scan period is being extended
automatically.
IN CHKT TIME No re-warning is made if 0 is specified.
The default re-warning interval when SYS_SCANEXT is not created
is 10 minutes.
Execution status of scan period automatic extension
EXT BOOL FALSE: Scan period is not extended.
TRUE: Scan period is extended.
OUT
ESCA TIME Actual scan period. (unit: ms)
The scan period of the application logic execution function specified
OSCA TIME
in the Link Architecture View of SCS Manager (unit: ms)
n Description
The SYS_SCANEXT function block checks execution status of the scan period automatic
extension.
If the scan period of the application logic execution function is extended longer than a certain
period of time (10 minutes by default), the condition is notified via diagnostic information
messages. The re-warning interval can be changed using the input parameter CHKT.
If the scan period automatic extension is enabled, ESCA outputs the actual scan period.
OSCA outputs the scan period of the application logic execution function specified in the
Resource Properties window of the Link Architecture View of SCS Manager.
n Remarks
This system function block can be used in new SCS databases created by SENG of R2.03.00 or
later.
SYS_SCAN
RST SCAN
ACT
AVE
MX
FREE
C100101E.ai
Figure SYS_SCAN
n Arguments
Table Arguments of SYS_SCAN
IN/OUT Arguments Data type Description
IN RST BOOL Reset switch (reset at change from FALSE to TRUE)
SCAN TIME Scan period (ms)
ACT TIME Actual operating time of application logic (ms)
OUT AVE TIME Average operating time of application logic (ms)
MX TIME Maximum operating time of application logic (ms)
FREE DINT Ratio of CPU idling time (%)
n Description
The SYS_SCAN system function block outputs the operating time of an application logic and the
ratio of CPU idling time.
The scan period (SCAN) refers to the current scan period of the application logic execution
function of SCS.
The application logic operating time (ACT) is the time from reading to outputting of process data.
AVE is the average of ACT for 10 scans.
The ratio of CPU idling time (FREE) is the percentage of idling time, which is defined as 1 second
minus the sum of ACT and the processing time of the external communication function.
The SYS_SCAN system function block clears the maximum operating time of application logic
(MX) if it detects changes of the reset switch (RST) from FALSE to TRUE.
n Remarks
The SYS_SCAN system function block is an interference-free function block. Do not use it for
input to a safety loop.
The scan period (SCAN) refers to the current scan period of the application logic execution
function of SCS. If the scan period automatic extension is enabled, SYS_SCAN outputs the scan
period that is currently used in the SCS as a result of automatic extension instead of the scan
period specified in the Resource Properties window of SCS Manager. Use the SYS_SCANEXT
function block to acquire the scan period specified in the Resource Properties window in the
application logic.
SYS_TIME
YR
MO
DY
HR
MN
SC
C100201E.ai
Figure SYS_TIME
n Arguments
Table Arguments of SYS_TIME
IN/OUT Arguments Data type Description
YR DINT Current calendar year
MO DINT Current month (1 to 12)
DY DINT Current date (1 to 31)
OUT
HR DINT Current hour (0 to 23)
MN DINT Current minute (0 to 59)
SC DINT Current second (0 to 59)
n Description
The SYS_TIME is a system function block used to output the current time recognized by an SCS
according to Coordinate Universal Time (UTC).
n Remarks
The SYS_TIME system function block is an interference-free function block. Do not use it for
input to a safety loop.
SYS_ALARM
SUM
CLS1
CLS2
CLS3
C100301E.ai
Figure SYS_ALARM
n Arguments
Table Arguments of SYS_ALARM
IN/OUT Arguments Data type Description
Logical OR of diagnostic information message generation status for alarm
SUM BOOL
classes 1 to 3
Diagnostic information message generation status of alarm class 1
CLS1 BOOL FALSE: No alarm has occurred
TRUE: At least one alarm has occurred
OUT Diagnostic information message generation status of alarm class 2
CLS2 BOOL FALSE: No alarm has occurred
TRUE: At least one alarm has occurred
Diagnostic information message generation status of alarm class 3
CLS3 BOOL FALSE: No alarm has occurred
TRUE: At least one alarm has occurred
n Description
The SYS_ALARM is a system function block used to detect diagnostic information message
generation status.
This system function block indicates the diagnostic information message generation status of
the entire SCS for each alarm class. If each output value is TRUE, it means that a diagnostic
information message of the corresponding alarm class has occurred.
These outputs are affected by operations in the Diagnostic Information window of an SENG. If
all diagnostic information messages of a given class are deleted from the Diagnostic Information
window of the SENG, the corresponding output value returns to FALSE.
n Remarks
The SYS_ALARM system function block is an interference-free function block. Do not use it for
input to a safety loop.
SYS_NETST
BUS1
BUS2
TSYC
C100401E.ai
Figure SYS_NETST
n Arguments
Table Arguments of SYS_NETST
IN/OUT Arguments Data type Description
Status on the bus 1 side
BUS1 BOOL TRUE: Abnormal
FALSE: Normal
Status on the bus 2 side
BUS2 BOOL TRUE: Abnormal
OUT FALSE: Normal
Time synchronization status (only when connected to Vnet/IP, always FALSE
when connected to V net)
FALSE: Synchronized with external clock (synchronized to the SNTP server
TSYC BOOL
time)
TRUE: Synchronized with internal clock (not synchronized to the SNTP
server time)
n Description
A SYS_NETST system function block outputs the status of control buses to which a station is
connected and the time synchronization status of the station. Control buses used in ProSafe-RS
include V net and Vnet/IP. In the case of a station connected to V net, the time synchronization
status (TSYC) is always fixed to FALSE.
Table Difference in Meaning when BUS1 and BUS2 Output TRUE Due to Difference of Control Bus
Control bus Meaning of abnormal (TRUE)
Vnet/IP (*1) At least one error occurred in a Vnet/IP network system.
V net A bus within the domain in which the applicable station is included is abnormal.
*1: Errors occurring in all domains connected via Vnet/IP are displayed. Note that statuses of V net domains connected via V net
routers are not included.
SCSP SCSP
(A) (C)
V net router
Scope of Vnet/IP network
In the case of stations connected to V net (SCSV(X), SCSV(Y)), a SYS_NETST system function
block is able to detect bus statuses within the V net domain to which the station is connected
(domain 4 in the figure above).
In the case of an SCSP connected to Vnet/IP, on the other hand, a SYS_NETST system function
block is able to detect the representative bus status of the entire Vnet/IP network (domains 1,
2 and 3 above). The status of V net buses beyond V net routers (domain 4 in the figure above)
cannot be detected with the SCSPs SYS_NETST function block.
In case a SYS_NETST system function block is used in the application logic of SCSP (A), which
is connected to domain 1, if bus 1, which is connected to the SCSP of domain 2, fails, the output
value of BUS1 of the SYS_NETST system function block becomes TRUE (abnormal). Even if
bus 2, which is connected to domain 3, fails before bus 1 recovers from the failure, the output
value of BUS2 of the SYS_NETST system function block does not become TRUE. Once bus 1
recovers from the failure, the output value of BUS2 becomes TRUE.
n Remarks
The SYS_NETST system function block is an interference-free function block. Do not use it
for input to a safety loop.
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
In the case of SCSPs connected to Vnet/IP, the output values of BUS1 and BUS2 of SYS_
NETST indicate the representative bus status. Even if it is judged that multiple bus failures
occurred based on the output result of SYS_NETST, communication may be possible in
some cases depending on the route to the communication destination.
In the case of SCSPs connected to Vnet/IP, if a bus failure on one side is detected by the
output of SYS_NETST, repair the failed location immediately.
SYS_ESBINF
NRL
NRR
C100501E.ai
Figure SYS_ESBINF
n Arguments
Table Arguments of SYS_ESBINF
IN/OUT Arguments Data type Description
Status of ESB bus on the left side (bus 1)
NRL BOOL TRUE: Normal status
FALSE: Abnormal status
OUT
Status of ESB bus on the right side (bus 2)
NRR BOOL TRUE: Normal status
FALSE: Abnormal status
n Description
A SYS_ESBINF system function block indicates the status of redundant ESB buses of a station
individually.
The ESB bus status can be detected for each side separately. NRL outputs the status of the ESB
bus (bus 1) on the left side and NRR outputs the status of the ESB bus (bus 2) on the right side.
When a SYS_ESBINF system function block indicates that one of the ESB buses is abnormal,
this means that the ESB buses on one side of all I/O nodes, except for CPU nodes, are
abnormal. The target I/O nodes include I/O nodes connected via optical ESB bus repeater
modules.
If the ESB bus status output parameters (NRL and NRR) are in conditions where communication
with at least one I/O node is possible via the ESB bus on the left or right side whichever is the
target, normal status (TRUE) is output. If they are unable to communicate with any I/O node,
abnormal status (FALSE) is output.
Note that FALSE is always output to NRL and NRR if no I/O node is defined within a station (in
case there is no node other than CPU nodes).
n Remarks
The SYS_ESBINF system function block is an interference-free function block. Do not use it
for input to a safety loop.
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
A SYS_ESBINF system function block indicates normal if at least one node can
communicate via each ESB bus. For stations configured with optical ESB bus repeater
modules and when you need to know the error of a specific node for the following cases,
use the SYS_NODEINF system function block:
- Detect only ESB bus errors of a specific I/O node directly connected to SEC402/SEC401
without going through an optical ESB bus repeater module.
- Detect only ESB bus errors of a specific I/O node connected via optical ESB bus repeater
modules.
SEE
ALSO For more information about SYS_NODEINF, see the following:
C10.6, SYS_NODEINF (Node Status Indicator)
SYS_NODEINF
NODE NRL
NRR
C100601E.ai
Figure SYS_NODEINF
n Arguments
Table Arguments of SYS_NODEINF
IN/OUT Arguments Data type Description
IN NODE DINT Node number (2 to 14)
Status of communication with the specified node via the ESB bus on
the left side (bus 1)
NRL BOOL
TRUE: Normal status
FALSE: Abnormal status
OUT
Status of communication with the specified node via the ESB bus on
the right side (bus 2)
NRR BOOL
TRUE: Normal status
FALSE: Abnormal status
n Description
A SYS_NODEINF system function block indicates the status of communication with an I/O node
specified by a node number (NODE).
The SYS_NODEINF system function block outputs the status of communication with the
specified node via the left ESB bus (bus 1) to NRL and the status of communication with the
specified node via the right ESB bus (bus 2) to NRR, respectively.
The SYS_NODEINF function block outputs TRUE (normal status) if communication with the
specified I/O node is possible via the ESB bus indicated by the output parameter (NRL or NRR),
and FALSE (abnormal status) if communication is not possible.
Abnormal statuses are notified in the following cases.
In the case of failure of ESB bus interface module SSB401 of the specified node on the side
where an error is notified
In the case of failure of establishing a route to the specified node from the ESB bus on the
side where an error is notified (for instance, due to failures of SEC402/SEC401 as well as
failures of optical ESB bus repeater modules in the case of nodes connected via optical
ESB bus repeater modules).
n Remarks
The SYS_NODEINF system function block is an interference-free function block. Do not use
it for input to a safety loop.
This system function block can be used in new SCS databases created by SENG of
R1.02.00 or later.
NRL and NRR always return FALSE if a CPU node (node number 1) is specified.
NRL and NRR always return FALSE if a node number for which no node is defined is
specified.
SYS_IOMDSP
NODE RDY
SLOT CTL
C100701E.ai
Figure SYS_IOMDSP
n Arguments
Table Arguments of SYS_IOMDSP
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Slot number (1 to 8)
Indicates whether or not the input/output module is normal.
RDY BOOL FALSE: Abnormal status
TRUE: Normal status
OUT Indicates whether or not the input/output module is on the control side
(*1).
CTL BOOL
FALSE: Standby side
TRUE: Control side
*1: Activated only when the module is in a dual-redundant configuration. If the module is defined as a non-redundant configuration in
I/O Wiring View, CTL will be always TRUE regardless of the module status.
n Description
The SYS_IOMDSP is a system function block used for outputting the operating statuses of input/
output modules.
n Remarks
Use the SYS_DIAG system function block to detect all SCS diagnostic information including
input/output modules.
The SYS_IOMSDP system function block is an interference-free function block. Do not use it for
input to a safety loop.
SYS_ALRDSP
NODE MDS
SLOT P1S
P2S
C100801E.ai
Figure SYS_ALRDSP
n Arguments
Table Arguments of SYS_ALRDSP
IN/OUT Arguments Data type Description
NODE DINT Node number (1 to 14)
IN
SLOT DINT Slot number (1 to 8)
Module status
MDS BOOL TRUE: No error
FALSE: Error (Faulty module)
Port 1 status
OUT P1S BOOL TRUE: No error
FALSE: Error (Communication error)
Port 2 status
P2S BOOL TRUE: No error
FALSE: Error (Communication error)
n Description
The SYS_ALRDSP is a system function block used for referencing the status of subsystem
communication module.
Occurrence of communication errors can be referenced for an entire module or for each port.
The status of the specified subsystem communication module is referenced regardless of
the redundant configuration of the module.
Errors in the communication with subsystems are detected regardless of the lock status of
subsystem communication data.
If no ALR111 or ALR121 subsystem communication module is present at the specified node
or slot, or when an ALR111 or ALR121 for Modbus slave communication is specified, all
outputs will become FALSE (error).
If the specified module is in an error state (MDS = FALSE), an error status will be output to
ports 1 and 2.
To use communication statuses in the application logic, the data statuses obtained by
function blocks that handle subsystem data, such as SCI_B and SCO_B, should be
referenced.
When node error (including the case that both ESB buses failed) occurs, MDS, P1S and
P2S will hold the previous values.
n Remarks
The SYS_ALRDSP system function block is an interference-free function block. Do not use
it to input data to safety loops.
This system function block can be used in new SCS databases created by SENG of
R1.01.30 or later.
SYS_FORCE_SC
UNLK LOCK
CHKT TUP
C100901E.ai
Figure SYS_FORCE_SC
n Arguments
Table Arguments of SYS_FORCE_SC
IN/OUT Arguments Data type Description
Forcibly unlocks all subsystem communication data.
UNLK BOOL FALSE TRUE: Forcibly unlock the data.
Other: Nothing happens
IN
The time during which to monitor the lock status of subsystem
CHKT TIME communication data.
Elapse of time is not checked if 0 is specified.
Presence of locked subsystem communication data
LOCK BOOL FALSE: None.
TRUE: At least one data item is locked.
OUT Indicates whether or not the time during which subsystem
communication data has remained locked exceeds the monitoring
TUP BOOL time (CHKT).
FALSE: CHKT is not exceeded.
TRUE: CHKT is exceeded.
n Description
The SYS_FORCE_SC is a system function block used for performing forcing management of
subsystem communication data.
n Inputs
UNLK is an input that forcibly unlocks all subsystem communication data. If UNLK changes
from FALSE to TRUE, all subsystem communication data currently locked by the forcing
function will be forcibly unlocked. If you do not want all subsystem communication data to be
unlocked, set it to FALSE.
In CHKT, specify the time during which to monitor the lock status. If at least one subsystem
communication data remains locked beyond the monitoring time specified in CHKT,
a diagnostic information message will be generated to notify the user. This diagnostic
information message is generated every time the monitoring time specified in CHKT
elapses. Time is not monitored if CHKT is set to 0.
n Outputs
The output of LOCK indicates whether or not subsystem communication data is locked. If
any part of the subsystem communication data is locked, LOCK becomes TRUE.
The output of TUP indicates whether or not any subsystem communication data has
remained locked beyond the monitoring time specified in CHKT.
n Remarks
The SYS_FORCE_SC system function block is an interference-free function block. Do not
use it to input data to safety loops.
This system function block can be used in new SCS databases created by SENG of
R1.01.30 or later.
SYS_STAT_SC
RUN OTEN
C101001E.ai
Figure SYS_STAT_SC
n Arguments
Table Arguments of SYS_STAT_SC
IN/OUT Arguments Data type Description
Output enable operation in subsystem communication
FALSE TRUE: Perform the output enable operation in subsystem
IN RUN BOOL
communication.
Other: Nothing happens.
Output enable status in subsystem communication
OUT OTEN BOOL TRUE: Output is enabled.
FALSE: Output is disabled
n Description
The SYS_STAT_SC is a system function block used for managing the output status in subsystem
communication. The output enable operation is normally performed from the SENG. By using
a SYS_STAT_SC block, only the subsystem communication outputs can be enabled from the
application logic.
The output enable operation is performed when the input of RUN has changed from FALSE to
TRUE. If you dont want the output enable operation to be performed, set FALSE.
To enable safety outputs or outputs in inter-SCS safety communication, use the SYS_STAT
system function block.
n Remarks
The SYS_STAT_SC system function block is an interference-free function block. Do not use
it to input data to safety loops.
This system function block can be used in new SCS databases created by SENG of
R1.01.30 or later.
This chapter explains the SCS functions for integrating with CENTUM.
SEE
ALSO For CENTUM integration, see the following:
1. Overview of CENTUM Integration of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
n Software Inputs/Outputs
Two of the software inputs/outputs supported by FCSs, common switch and annunciator, are
available for use in SCSs.
Table Software Inputs and Outputs Available in SCSs
Name Support in SCS Element
Common Switches x %SW
Global switch %GS
Annunciator x %AN
Printout message (with printing, Historical) %PR
Printout message (without printing, Historical) %PR
Operation guide message %OG
Multimedia start message %VM
Sequence message request %RQ
Supervisory computer event message %CP
Supervisory computer message output for PICOT %M3
Signal event message %EV
SFC/SEBOL return event message output %RE
X: Supported
Blank: Not supported
TIP
The sent and received data through SCS Link Transmission cannot be accessed from HIS as accessing a %GS
element. For accessing from HIS, an internal variable should be placed in application logics. The examples below
show how to connect the internal variable with SCS Link Transmission FB, and then define the variable with a tag
name on the Tag Name builder.
For accessing the value of a sent data, the data connected to the sending FB should be branched so as to
connect to a variable.
For accessing the value of a received data, the output parameter of the receiving FB for the data value
should be connected with a variable.
For accessing the data status of a received data, the output parameter of the receiving FB for the data
status should be connected with a variable.
l Update Interval
The SCS internal status is reflected in common switches for the system at the intervals of the
scan period of the external communication function.
n Plant Hierarchy
The mapping blocks and elements assigned with tag names can be handled as the equipment
objects in CENTUM plant hierarchies. By specifying the tag names of the SCS, the process
alarm filtering and security settings for operation and monitoring can be performed on HIS
according to the plant hierarchy definition.
SEE
ALSO For details of the plant hierarchy, see the following:
E10, Plant Hierarchy of CS 1000/CS 3000 Reference HIS (IM 33S01B30-01E)
E7, Plant Hierarchy of CENTUM VP Reference HIS (IM 33M01A30-40E)
For how to perform engineering tasks related to the plant hierarchy, see the following:
2.1.8, Plant Hierarchy of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
l Changing UAID
The upper level equipment names of mapping blocks and mapping elements can be
changed via online change download as well. UAIDs of mapping blocks and mapping
elements newly added via online change download take the values corresponding to the
upper level equipment names defined in the Tag Name Builder.
UAIDs managed by the SCS can be changed via operations from an HIS, SEBOL of FCS,
and OPC.
UAIDs cannot be changed from an SCSs application logic.
IMPORTANT
If UAIDs do not match between the HIS and SCS, the security management on the HIS and
process alarm filtering according to the plant hierarchy definitions no longer function correctly.
If UAIDs are set from an HIS, FCS or OPC, be sure to set the UAIDs again from the HIS, FCS or
OPC after SCS off-line download or resetting and restarting the HIS and/or SCS.
V net
SCS
D020001E.ai
SEE
ALSO For variables, elements and function blocks for which tag names can be defined, see the following:
List of Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l Input/Output Terminals
No input/output terminals are used for mapping blocks/elements of an SCS. Mapping blocks/
elements are used to exchange data with variables and function blocks of the corresponding
application block, and not for connection between with mapping blocks/elements.
l AF (Alarm Detection)
This data item is not supported. Do not change the data of this item from CENTUM.
n Process Alarms
Process alarms notify process errors detected by the application logic as alarm messages for
CENTUM. Though the process alarms are sent by mapping blocks, when the process alarms
are displayed on HIS window to indicate abnormality or recovery events, the timestamps of the
events will be the reception time that HIS receives the alarms.
Each mapping block provides the following process alarms. Check the explanation of individual
function blocks associated with mapping blocks for details of process alarms.
Table Process Alarms Generated from Mapping Blocks
S_OVR_* S_GOV_* S_
S_ANLGI S_ANLG_S S_VEL S_MOB_21 S_MOB_11 S_MOB_RS S_MOA
(*1) (*2) PASSWD
NR x x x x x x x x x x
IOP x x x
OOP x x x
HTRP x x
LTRP x x
HHH x x
LLL x x
OVR x x
PWON x
PERR x
ANS+ x x x
ANS- x x x x
VEL+ x
VEL- x
x: The corresponding process alarm is generated.
Note: NR is the status set when other process alarms are not generated. Process alarms are displayed on an HIS in the order in the
table with the highest priority on the top item.
*1: Indicates S_OVR_B, S_OVR_I, S_OVR_R, S_OVR_IB or S_OVR_IR.
*2: Indicates S_GOV_B or S_GOV_IB.
SEE
ALSO For a detailed explanation of OPMK (operation mark), see the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
SEE
ALSO For a detailed explanation of OPMK (operation mark), see the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l Specification Syntax
%Znnusmm
%Z: Process input/output identifier (fixed to %Z)
nn: Node number (01 to 14)
u: Slot number (1 to 8)
s: Segment number (fixed to 1)
mm: Terminal number (01 to 16)
SEE
ALSO For physical data and logical data, see the following:
A4.2, Input and Output Variables
The data read by tag name interfaces is logical data. The table below shows how to access data
via mapping elements associated with input/output variables.
Table Access to Logical Data of Input/Output Variables via Tag Names
Discrete Analog
Tag name defined for a discrete input/output
Tag name defined for an analog
Reading (logical data) variable (%Z)
input variable (%WB)
Process input/output terminal number (%Z)
Writing Not possible Not possible
Dictionary View of SCS Manager can display both physical data and logical data of input/output
variables.
It is possible to define tag names for IO_BOOL-type and IO-REAL type variables in Tag Builder.
The table below shows whether or not tag names can be defined with the Direction attribute. Tag
names can be defined for variables with either the Input or Output attribute.
Table Direction Attribute of Variables and Tag Name Assignment
Direction
Input Output Internal
IO_REAL OK OK NG
IO_BOOL OK OK NG
OK: Tag name can be specified
NG: Tag name cannot be specified
: Not applicable
SEE
ALSO See the following for tag name interfaces of other function blocks.
For override function blocks, see the following:
D3.2, Tag Name Interfaces and Process Alarms of Override Function Blocks
For more information about the Grouping Override FB, see the following:
D3.4, Tag Name Interfaces and Process Alarms of Grouping Override Function Block
For password function blocks, see the following:
D3.7, Tag Name Interfaces and Process Alarms of Password Function Blocks
For BOOL-type data manual operation function blocks with answerback, see the following:
D4.1.6, Tag Name Interfaces and Process Alarms of MOB_11 and MOB_21
For auto-reset BOOL-type data manual operation function blocks, see the following:
D4.2.2, Tag Name Interfaces and Process Alarms of MOB_RS
For analog-type data manual operation function blocks, see the following:
D4.3.2, Tag Name Interfaces and Process Alarms of MOA
For external communication function blocks, see the following:
D5.2, Tag Name Interfaces of External Communication Function Blocks
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
TIP
To affix the data status, the item [PV Status of S_ANLG_S] on SCS tab of SCS Constants Builder needs to
be defined.
When the database is created, the PV data are affixed with data status signals at default setting. However,
if the above setting is not defined, when CENTUM station read the PV, even though the PV has data status
signal, the PV will be always marked as Normal regardless the actual data status.
In the SCS database created by R1.02, the PV of ANLG_S does not have data status signal.
Range
The range of engineering unit data after scale conversion
Default
The default value of SL (scale low limit) of ANLG_S is reflected in the default value of PV.
l HYS (Hysteresis)
This data item is associated with the HYS parameter (hysteresis) of ANLG_S. The HYS value of
ANLG_S is reflected in this item.
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l HYS (Hysteresis)
This data item is associated with the HYS parameter (hysteresis) of ANLGI. The HYS value of
ANLGI is reflected in this item.
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l PV (Output Value)
This data item is associated with the OUT parameter (output value) of VEL. It is displayed in the
parameter display area of instrument faceplate and will be a target of data collection for tuning
trend.
Range
The range of PV is from 0 to 100%.
Default
The default value of PV is the SL (scale low limit) value, i.e., 0.0.
l HYS (Hysteresis)
This data item is associated with the HYS parameter (hysteresis) of VEL. The HYS value of VEL
is reflected in this item.
SEE
ALSO For a detailed explanation on AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user
application ID), see the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l PV (Input Value)
This data item is associated with the IN parameter (input value) of ANN. It is displayed in the HIS
tuning view and the parameter display area of instrument faceplate, and will be a target of data
collection for tuning trend. Data entry from an HIS is not allowed.
Range
The range of PV is 0 or 1.
Default
The default value of IN (0) of ANN is reflected for the default value of PV.
SEE
ALSO For a detailed explanation of the OPMK (operation mark) data item of subsystem communication inputs/outputs,
see the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
l %WB Data Items Associated with SCI_B and SCO_B (PV: BOOL Data)
Mapping elements of SCI_B and SCO_B function blocks have PV (BOOL data) data items.
This data item displays BOOL-type data of the function blocks. It is displayed in the HIS tuning
view and the parameter display area of instrument faceplate, and will be a target of data
collection for tuning trend. Data entry from an HIS is not allowed.
The range is 0 or 1.
l %WB Data Items Associated with SCI_R and SCO_R (PVF32: Real Number
Data)
Mapping elements of SCI_R and SCO_R function blocks have PVF32 (real number data) data
items.
This data item displays the real number data value of the associated function block. It is
displayed in the HIS tuning view and the parameter display area of instrument faceplate. Data
entry from an HIS is not allowed.
The range is all single precision real numbers.
The following figure illustrates an example where an input variable is overridden using an
override function block for IO_BOOL-Type variable (OVR_IB). In the example of overriding
an input variable, the override function block is positioned immediately after the variable to be
overridden.
OVR_IB
D030101E.ai
In the normal status where the variable is not overridden, the OVR_IB function block outputs the
data input via input parameter IN as is from output parameter OUT. When an override operation
is specified from the HIS via the mapping block, the OVR_IB function block outputs the value
specified for input parameter VAL (TRUE in this case) from output parameter OUT. During
overriding, the data status of output parameter OUT is always TRUE (GOOD). If the override
operation is canceled from the HIS, the OVR_IB function block outputs the data input via input
parameter IN as is from output parameter OUT again.
A BOOL-Type variable is specified for input parameter SW of the OVR_IB function block. Under
normal circumstances, this BOOL-Type variable is set to be an input variable from a key switch.
If the user operates the key switch, the BOOL-Type variable value changes. If the BOOL-Type
variable becomes TRUE, input parameter SW of OVR_IB also becomes TRUE, and an override
operation is permitted. If the variable becomes FALSE, the override operation is prohibited.
Note that the override operation is not canceled even if input parameter SW changes from TRUE
to FALSE while the override instruction is active; output parameter OUT keeps on outputting the
value specified for input parameter VAL.
TIP
It is possible to change values of BOOL-Type variables by entering data along with the correct password from the
faceplate of an HIS by using the password function block. Utilizing this mechanism, it can be specified whether or
not to allow override operations using the password function instead of using hardware such as a key switch.
SEE
ALSO For the password function block, see the following:
C5.3, PASSWD (Password)
OVR_IR
Override permission
(BOOL-Type variable) SW
D030102E.ai
When the override operation of the function block is activated, the data status of output
parameter OUT is fixed to TRUE (GOOD) but the data status of input variables connected to
input parameter IN is not influenced. If the override function block is placed in the override status,
only output parameters OUT and STS change.
SEE
ALSO For the procedure to define mapping blocks of override function blocks, see the following:
2.1.5, Engineering for Overriding from HIS of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-
21E)
SEE
ALSO For a detailed explanation of items defined in the Tag Name Builder, see the following:
2.1.4, Definition of Tag Names of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
SW (Switch)
This data item is associated with the SW parameter of an override function block. The range is 0
or 1. Override operations are permitted when the value of SW is 1. The SW value of an override
function block is reflected in this item.
n Process Alarm
Mapping blocks of the override function blocks generate two types of process alarms, override
ON and answerback error alarms. It can be specified in Tag Name Builder whether or not the
override function blocks should generate process alarms.
MV PV BOOL
<BOOL data> IN OUT
variable
ON TRUE VAL
<BOOL data> SW
STS
OVR_B
MV PV PV
OFF Mapping
block
Faceplate
SCS
D030201E.ai
Figure Flow of Data between Override Function Block and Mapping Block
If you perform an override operation from the faceplate of the HIS, the mapping block stores
the value 1, which means instruct override, in its own data item MV. The data of MV is then
set to the internal variable of the override function block. The override function block examines
the validity of the set data. If the data is considered valid, the override function block goes into
override condition and changes the STS from FALSE to TRUE.
The mapping block reads the STS value of the override function block into the PV of the mapping
block at the next scan period.
The scan period of the mapping block is the same as the scan period of the external
communication function. The default value is 1 second.
If the value (MV) instructed by the mapping block and the status value (PV) read back from
the STS output of the override function block do not match, the mapping block generates an
answerback error alarm. If they match later, the mapping block recovers from the answerback
error alarm.
An answerback error alarm is generated under the following conditions.
ON side answerback error alarm (ANS+)
MV = 1 and PV 1
OFF side answerback error alarm (ANS-)
MV = 0 and PV 0
The mapping block recovers from an answerback error alarm under the following conditions.
ON side answerback error alarm (ANS+)
When PV changes to 1 or MV changes to a value other than 1
OFF side answerback error alarm (ANS-)
When PV changes to 0 or MV changes to a value other than 0
The system recovers from an override ON alarm under the following conditions.
PV = 0 (STS of the override function block is FALSE)
n Group Function
By using a grouping override function block, it is possible to restrict the override operation of
multiple data items that are defined as a group to only one at a time. Multiple groups can be
defined within an SCS. The override operations can be performed simultaneously to grouping
override function blocks that belong to separate groups.
There are no limits to the number or types of grouping override function blocks that can be
defined as a group. Both GOV_B and GOV_IB can be included in a same group.
If the override operation is performed for a grouping override function block in a group, the
operation cannot be performed on other function blocks in the same group until it completes.
When the override operation is attempted simultaneously on another function block within
the same group, the override operation for that function block will be disabled.
It is also possible to enable the override operation for individual function blocks, without
grouping, using a grouping override function block.
l Group Number
Group number is defined for GRP. Multiple groups can be defined by assigning different group
numbers.
Up to 128 groups can be managed by a single SCS. Specify a group number (1 to 128) for
GRP.
When the group number is set to 0, that grouping override function block does not belong
to any group. The number limitation on simultaneous operations will be invalid, and the
override operation can be performed without being affected by the exclusive control on the
override operations for other grouping override function blocks.
The override operation cannot be performed if the group number is set to a negative number
or a number equal to or greater than 129.
TIP
When the group number is 0
When the group number is set to 0, if the override permit switch (SW) is TRUE, the override enable status
(ENS) is always TRUE. MODE indicated on the HIS instrument faceplate is MAN.
When the group number is negative, or 129 or greater
When a value outside the range is specified as the group number, the override enable status (ENS) is fixed
to FALSE regardless of the state of override permit switch (SW). The override operation is not allowed.
MODE indicated on the HIS instrument faceplate is always AUT.
n Block Mode
The override enable status can be checked from the block mode (MODE) by specifying the
tag name assigned to a grouping override function block and then calling the HIS instrument
faceplate. The block mode reflects the state of the function blocks override enable status
(ENS). MODE becomes MAN when ENS is TRUE, and AUT when FALSE.
The override operation is allowed only when MODE is MAN. When the override operation is
not permitted because the override permit switch (SW) is FALSE, or when override is being
executed for another function block in the same group, MODE indicates AUT.
TIP
The override status is canceled under the following conditions as well.
When a forced cancellation command is issued from the SYS_OVR block
When the group number is changed (The group number should be set to a fixed value. The online change
download during the override operation is prohibited.)
l Execution of Override
Grouping override function block outputs the data input from IN as is from OUT when there is no
override execution.
1. Set the override permit switch (SW) to TRUE.
2. If there are no function blocks for which override is being executed within the group,
MODE of tag assigned to the function block becomes MAN, the override operation can be
performed. If the override operation is not allowed, MODE stays AUT.
3. If MV is set to 1 from the HIS instrument faceplate and PV of answerback signal changes to
1, data specified by VAL will be output from OUT of the grouping override function block. At
this time, the mode of other function blocks that belong to the same group will be AUT.
TIP
When the override operation is disabled, or when the override status is canceled by setting SW to FALSE, MV will
be reset to 0 and PV of answerback signal will be 0 as well.
l End of Override
When MV is set to 0 from an HIS and the override status is canceled, the data input from IN will
be output again from OUT of the grouping override function block. At this time, the mode of all
function blocks that belong to the same group becomes MAN (*1).
*1: Even if it belongs in the same group, the mode of the function block whose override permit switch (SW) is set to FALSE stays
AUT.
Permit switch Block A override Block A override Block A override Permit switch
changed to TRUE execution cancellation execution changed to FALSE
Block A SW T
F
ENS T
F
MV (PV)
Mapping block A
MODE AUT MAN AUT
OUT IN
Block B SW T
F
T
ENS
F
Block A is the function block for which override is executed, while block B is another
function block within the same group.
D030302E.ai
SEE
ALSO For details regarding the items defined in Tag Name Builder, see the following:
2.1.4, Definition of Tag Names in the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
n Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name
Interfaces
l SW (Switch)
This data item is associated with the SW parameter (override permit switch) of a grouping
override function block.
Range
The range of SW is 0 or 1. The SW value of a grouping override function block is reflected in
this item.
Operations by SW changes
Override operations are permitted only if the SW value is 1. However, the override operation
can actually be performed for the function block only when the MODE is MAN.
When SW changes from 1 to 0, the override status is canceled.
n Process Alarm
Override ON alarms are notified from grouping override function blocks.
l Override ON Alarm
Override ON alarms can be used to notify an operator that a function block is being overridden.
A mapping block generates an override ON alarm if an override function block is placed in the
override status. Once the override status is canceled, the mapping block recovers from the
override ON alarm.
An override ON alarm is generated under the following condition.
PV = 1 (STS of the override function block is 1)
The mapping block recovers from an override ON alarm under the following condition.
PV = 0 (STS of the override function block is 0)
SEE
ALSO For details of SYS_OVR, see the following:
C9.9, SYS_OVR (Override Function Blocks Management)
TIP
If there is a grouping override function block with a group number outside the specification range, the override
permission signal operation for that function block is considered a part of the override enable status management.
SWON
SWON indicates whether or not there is a function block in the override enable status.
NUMS
NUMS indicates the number of override function blocks in the override enable status.
For instance, if a common override permission signal is input to all the grouping override
function blocks that comprise a group of 10 function blocks, setting the override permission
signal to 1 makes NUMS to be 10.
MV PV
PV
OFF
Mapping
Faceplate
block
Control
bus
Override FB
TAG0301 TAG0301
OVR_IB
MV Internal
variable
MV PV Input <IO_BOOL
IN OUT
ON variable data>
PV TRUE VAL
MV PV OVRSW SW STS
OFF
Mapping
Faceplate block
Override FB
TAG0303 TAG0303
OVR_IB
MV Internal
MV PV variable
Input <IO_BOOL
ON IN OUT
variable data>
PV TRUE VAL
MV PV
OVRSW SW STS
OFF
Mapping
Faceplate block
D030301E.ai
Start
Operations of HIS/SCS
User operation
from HIS
Perform the
override operation
D030602E.ai
*1: If there are any problems during checks by the password function block, the password function block outputs a system alarm that
includes a tag name and aborts the processing.
*2: System alarm messages include the password function block instance name and tag name.
End the
override operation
Operations of HIS/SCS
User operation
from HIS
YES
The soundness and correctness MV of the faceplate
of password character string changes from OFF to ON
entered is checked by the
password function block (*1)
End
D030603E.ai
*1: If there are any problems during checks by the password function block, the password function block outputs a system alarm that
includes a tag name and aborts the processing.
*2: System alarm messages include the password function block instance name and tag name.
SEE
ALSO For the detailed specifications about the SYS_PSWD system function block, see the following:
C9.10, SYS_PSWD (Password Function Blocks Management)
SEE
ALSO For a detailed explanation of items defined in the Tag Name Builder, see the following:
2.1.4, Definition of Tag Names of the Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
n Process Alarms
The mapping block of PASSWD FB can initiate a process alarm for Password ON. It is possible
to specify whether or not to initiate this process alarms using the Tag Name Builder.
l Password ON Alarm
Password ON alarms can be used to notify an operator that the PASSWD function block is
currently outputting TRUE. A mapping block generates a password ON alarm if the PASSWD
function block outputs TRUE via output parameter OUT. The system recovers from the password
ON alarm if 0 is set with password from the faceplate.
A password ON alarm (PWON) is generated under the following conditions.
PV = 1 (OUT of the PASSWD function block is TRUE)
SEE
ALSO See the following for each of the manual operation function blocks.
For a detailed explanation of MOB_11, see the followings:
C5.4, MOB_11 (BOOL-Type Data Manual Operation Function Block with Two-Position Answerback)
D4.1, HIS Interfaces of MOB_11 and MOB_21 (BOOL-Type Data Manual Operation Function Block with
Answerback)
For a detailed explanation of MOB_21, see the followings:
C5.5, MOB_21 (BOOL-Type Data Manual Operation Function Block with Three-Position Answerback)
D4.1, HIS Interfaces of MOB_11 and MOB_21 (BOOL-Type Data Manual Operation Function Block with
Answerback)
For a detailed explanation of MOB_RS, see the followings:
C5.6, MOB_RS (Auto-Reset BOOL-Type Data Manual Operation)
D4.2, HIS Interfaces of MOB_RS (Auto-Reset BOOL-Type Data Manual Operation)
For a detailed explanation of MOA, see the followings:
C5.7, MOA (Analog-Type Data Manual Operation)
D4.3, HIS Interfaces of MOA (Analog-Type Data Manual Operation)
D040001Eai
SEE
ALSO See the following for other functions of MOB_11 and MOB_21.
For an explanation of parameters of MOB_11, see the following:
C5.4, MOB_11 (BOOL-Type Data Manual Operation Function Block with Two-Position Answerback)
For an explanation of parameters of MOB_21, see the following:
C5.5, MOB_21 (BOOL-Type Data Manual Operation Function Block with Three-Position Answerback)
SEE
ALSO For detailed explanation of FCS switch instruments, see the following:
D3.4, Switch Instrument Block and Enhanced Switch Instrument Block of the CS 1000/CS 3000
Reference Function Block Details (IM 33S01B30-01E)
D3.4, Switch Instrument Block and Enhanced Switch Instrument Block of the CENTUM VP Reference
Function Block Details (IM 33M01A30-40E)
MAN
NR
CENTUM
MODE
SCS
ALRM
MV
PV
Shutdown logic SHDN
FALSE SS
OUT Output logic
Output logic in AUT mode IN
Manual operation SW
permission logic
LIMSW_OPEN AIN
NANP
T#5000ms MTM
NANM
AIN_DSTS IOP
OUT_DSTS OOP
OUT_Enabled OTEN
'password' PSWD
D040101E.ai
Figure Usage Example of BOOL-Type Data Manual Operation Function Block with Two-Position
Answerback
MAN
NR
CENTUM
MODE
SCS
ALRM
MV
PV
Shutdown logic SHDN
FALSE SS
Output logic in AUT mode IN
OUT Output logic
Manual operation SW
permission logic
LIMSW_OPEN AINP
LIMSW_CLS AINM
NANP
T#5000ms MTM
NANM
AIN_DSTS IOP
NPER
OUT_DSTS OOP
OUT_Enabled OTEN
'password' PSWD
D040102E.ai
Figure Usage Example of BOOL-Type Data Manual Operation Function Block with Three-Position
Answerback
The associated parameter values of SCS function blocks are sent to indicate the block mode
(MODE), process alarms (ALRM) and answerback input values (PV) on the CENTUM side
via mapping blocks. The value of OUT is displayed as MV on HIS instrument faceplate and
operations on MV from the HIS are sent to OUT of the SCS in the manual mode (MAN).
HIS
Flow of control
Display actual field value
SS
SHDN equal to SS
OUT
SW
SHDN not equal to SS
IN
SW equal to FALSE
Comparison AIN
AIN
with OUT
Answerback input
Limit swich
D040103E.ai
Shutdown Processing
If the input value of SHDN (shutdown signal) matches the safe state specified by the input value
of SS, the safe state is output from OUT. At this point, all data settings from input parameters
other than SHDN and SS as well as an HIS are ignored.
Answerback Check
Regardless of whether the input to SW is TRUE or FALSE, it is checked whether the OUT value
and answerback input value match as an answerback input check.
For example, by connecting OUT to the output signal to a valve and the answerback input value
(AIN for MOB_11) to the limit switch of the valve, it is possible to confirm that the output result
of OUT is correctly transmitted to the process. It is also possible to bypass the answerback
input value check for a fixed period of time only after changing the value of OUT, taking into
consideration the time that the valve requires to change from full open to full close.
SEE
ALSO See the following for the examples of using MOB_11 and MOB_21.
3.3.5, Example of using Bool-type Data Manual Operation Function Block (MOB_*) of the Engineering
Guide (IM 32S01C10-21E)
MOB_11
IN
OUT
SW
D040104E.ai
n Password Processing
The following parameters are related to password entry when manual operations are permitted.
MOB_11
SW
OUT
PSWD
D040105E.ai
Overview
Set a password in PSWD when you create POU.
If the input to SW is TRUE, manual operations from an HIS are permitted and entry of a
password is required when an operator enters a value for MV. Manipulations of MV are
permitted only if the set password and the input password match.
Operation in HIS
If the input to SW is TRUE, i.e., the system is in the manual mode (MAN), a user is allowed to
perform manual operations from an HIS. In this case, the user is required to enter a password.
The entered password is checked within the SCS function block. If the password is incorrect, a
warning message for the illegal operation will be displayed and the MV will be unchanged.
If a communication error with an HIS occurs during manual operations, OUT retains the current
value.
MOB_11
OTEN
OUT
D040106E.ai
MOB_11
AIN
OUT
MTM
NANP
NANM
D040107E.ai
T
OUT
F
T
AIN
F
Mask MTM
Timer 0
T
NANP
F
T
NANM
F
D040108E.ai
When OUT changes, the mask timer for answerback check will be started. The mask for
answerback check will continue until the time specified by MTM has elapsed. Within this
masked time period, the answerback error will be ignored.
Immediately after the value of OUT is changed, TRUE (normal) is set to NANP and NANM
once. Process alarms of answerback errors are also canceled once.
MOB_21
AINM
OUT
AINP
NANP
MTM
NANM
NPER
D040109E.ai
T
OUT
F
AINP T
Open side
answerback F
AINM T
Close side
answerback F
MTM
Mask timer
0
NANP
T
Error of open side
answerback F
NANM T
Error of close side
answerback F
NPER T
Answerback
pattern error F
2
1
PV 0
Hold previous value
D040110E.ai
When OUT changes, the mask timer for answerback check will be started. The mask for
answerback check will continue until the time specified by MTM has elapsed. Within this
masked time period, the answerback error will be ignored.
Immediately after the value of OUT is changed, TRUE (normal) is set to NANP and NANM
once. Process alarms of answerback errors are also canceled once.
In the case of an answerback pattern error (NPER is FALSE), the answerback statuses on
both the open and close sides (NANP and NANM) are retained.
In detection of answerback pattern errors (NPER), answerback check mask is ignored.
FALSE (abnormal) is thus output to NPER as soon as the conditions for pattern error are
met (AINP = TRUE and AINM = TRUE).
When the answerback check is masked and the answerback pattern error occurs, the
answerback check mask will be disabled. If the answerback pattern error is recovered and
the answerback check is performed, the results will be available in NANP and NANM.
MOB_11
IOP
OOP
D040111E.ai
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
Process Alarms
MOB_11 and MOB_21 notify process alarms of answerback error and IOP/OOP.
If the system recovers from an answerback error, a process alarm is notified. The notification is
made when the parameters of a function block change under the following conditions.
Recovery notification of answerback error on the open side (ANS+ cancellation):
At a rising edge of NANP
Recovery notification of answerback error on the close side (ANS- cancellation):
At a rising edge of NANM
Recovery notification of answerback pattern error (PERR cancellation):
At a rising edge of NPER
The notification of recovery is made if the parameters of the function blocks change under the
following conditions.
Input error recovery alarm: At a rising edge of IOP
Output error recovery alarm: At a rising edge of OOP
SEE
ALSO For an explanation of parameters of MOB_RS, see the following:
C5.6, MOB_RS (Auto-Reset BOOL-Type Data Manual Operation)
MAN
NR
CENTUM
MODE
SCS
MV
PV
Application logic
Manual operation SET
permission logic SW
Q1
AIN OUT RESET1
FALSE ADIR
NANM ANSV
T#1s MTM
D040201E.ai
The associated parameter values of the SCS function block are sent to indicate the block mode
(MODE) and answerback input value (PV) on the CENTUM side via the mapping blocks. The
value of OUT is displayed as MV on the HIS instrument faceplate and operations on MV from the
HIS are sent to OUT of the SCS in the manual mode (MAN).
FALSE
SW equal to FALSE
Pulse
generator OUT
SW equal to TRUE
Value from
HIS (MV)
This variable always follows the valve of OUT except
when the data from HIS is received.
D040202E.ai
Answerback Check
The following parameters are related to answerback check of MOB_RS.
MOB_RS
AIN
ADIR
OUT
MTM
NANM
D040203E.ai
MV PV
MV PV
2
MV 0
T
OUT
F
T
AIN
F
SW T
F D040204E.ai
The data items of CENTUM and parameter values of MOB_RS are related in the following ways.
The AIN parameter (answerback input value) of MOB_RS is associated with PV on the
CENTUM side. PV=2 if AIN=TRUE and PV=0 if AIN=FALSE.
The OUT parameter of MOB_RS is associated with MV on the CENTUM side. OUT=TRUE
if MV=2 and OUT=FALSE if MV=0.
1. At normal status, MV=0 and FALSE is output to OUT of MOB_RS.
2. Create application logic such that AIN of MOB_RS is latched to TRUE at the occurrence of a
demand. If AIN becomes TRUE, PV becomes 2.
3. If MV is changed to 2 from an HIS to reset the latch, OUT of MOB_RS changes to TRUE.
OUT returns to FALSE after one scan (automatic reset).
4. Create application logic such that the latch is reset upon changes of OUT from FALSE to
TRUE and AIN returns to FALSE. PV becomes 0 if AIN becomes FALSE.
MV PV
MV PV
2
MV
0
T
OUT
F
T
AIN
F
SW T
F
D040205E.ai
A reverse operation is normal if the values of PV and MV are opposite in the HIS instrument
faceplate.
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
SW (Switch)
This data item displays the status of the manual operation permit/prohibit toggle switch of a
function block. Data entry from an HIS is prohibited.
Associating parameters of function blocks
The SW parameter (manual operation permit/prohibit toggle switch) of a function block is
associated with SW. The SW value of MOB_RS is reflected in this item.
Range
The range of SW is 0 or 1.
Process Alarms
MOB_RS notifies answerback error alarms.
SEE
ALSO See the following for other functions of MOA.
For an explanation of parameters of MOA, see the following:
C5.7, MOA (Analog-Type Data Manual Operation)
The management of passwords for permitting manual operations is the same as for MOB_11 and MOB_21;
see the following:
D4.1.2, Password at Manual Operations
For output enable status display, see the following;
D4.1.3, Output Enable Status Display Function
MAN
NR
CENTUM
MODE
SCS
ALRM
MV
FV
Manual operation
permission logic SW
FEEDBACK FV
AOVAR.status OOP
OUTEN OTEN
'password' PSWD
D040301E.ai
The associated parameter values of the SCS function block are sent to indicate the block mode
(MODE), process alarms (ALRM) and feedback input value (FV) on the CENTUM side via the
mapping blocks. The value of OUT is displayed as MV on the HIS instrument faceplate and
operations on MV from the HIS are sent to OUT of the SCS in the manual mode (MAN).
OUT
SW
SHDN equal to TRUE
IN SW equal to FALSE
Value from
SW equal to TRUE
HIS (MV)
D040302E.ai
Shutdown Processing
If the input value of SHDN (shutdown signal) becomes FALSE, the value of SDV (shutdown
output value) is output from OUT. At this point, all data settings from input parameters other than
SHDN and SDV as well as an HIS are ignored.
The SHDN input of MOA supports only DTS logic (normal: TRUE, abnormal: FALSE). Connect
a reversed shutdown logic signal to SHDN in the case of ETS logic (normal: FALSE, abnormal:
TRUE).
Feedback Input
The feedback input (FV: data type is REAL) can be used for the purpose of checking the result
of manipulating MV from an HIS on instrument faceplate and so on. Input a signal indicating the
degree of opening of a valve or similar connected to the output variable channel connected to
OUT, to FV.
It is not checked that the values of OUT and FV match.
The value of FV is used for checking purposes only in an HIS. It has no influence on the
output behavior of OUT.
OOP Detection
It is possible to use OOP (whose data type is BOOL) to check whether or not an output signal is
normal. Input the data status of an output signal (output variable connected to OUT) or similar
to OOP. Process alarms are notified on the CENTUM side according to the change of the OOP
value.
The value of OOP has no influence on the output behavior of OUT.
TIP
When a block is in a block mode that the manual operation is not allowed (MODE=AUT), the output from OUT will
not be affected by the output high and low limits or the output scale high and low limits. The values specified by
the parameters of IN or SDV of MOA will be intact and directly outputted.
SEE
ALSO For a detailed explanation on MODE (block mode), AFLS (alarm flashing status), AF (alarm detection
specification), AOFS (alarm inhibition specification), OPMK (operation mark) and UAID (user application ID), see
the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
SW (Switch)
This data item displays the status of the manual operation permit/prohibit toggle switch of MOA.
Data entry from an HIS is not allowed. Operations on MV from an HIS are permitted when the
value of SW is 1 and MODE becomes MAN.
Associating parameters of function blocks
The SW parameter (manual operation permit/prohibit toggle switch) of MOA is associated
with SW. The SW value of MOA is reflected in this item.
Range
The range of SW is 0 or 1.
Process Alarms
MOA notifies process alarms of OOP.
OOP
If you connect a signal indicating whether or not the output signal is normal to the OOP
parameter of MOA, output errors are notified as process alarms. The notification is made if the
parameter of MOA changes under the following condition.
Output error occurrence alarm: At a falling edge of OOP
The notification of recovery is made if the parameter of MOA changes under the following
condition.
Output error recovery alarm: At a rising edge of OOP
Tag name interfaces use the same data item names for referencing and setting data. For
example, if the tag name TAG0702 is defined for an ECW_I function block, the specification
TAG0702.PVI32 can be used when both referencing and setting data of this function block. If
the tag name TAG0703 is set for an ECW_R function block, TAG0703.PVF32 is used to access
data.
FCS
CENTUM Application logic
integration function
TAG0701.PV
TAG0701 OUT
Tag name interface Internal variable
SFC mapping <BOOL data>
ECW_B
block element (%WB)
TAG0702.PVI32
TAG0702
Tag name interface Internal variable OUT
mapping <DINT data>
element (%WB) ECW_I
Control bus
TAG0703 OUT
Application Tag name interface Internal variable <REAL data>
mapping
accessing data TAG0703.PVF32 ECW_R
element (%WB)
by the tag name
HIS
SCS
D050001E.ai
Figure Data Setting Using Tag Name Interfaces of External Communication Function Blocks
FCS SCS
Control bus
D050002E.ai
Figure Example of Application that Checks Data Setting Using Readback Variable
Connect the variable READBACK (DINT-type variable) to the OUT variable so that the output
from the OUT variable can be read back with a user application. By doing so, it can be confirmed
that the data has been set correctly.
The procedure to set DINT-type data is shown below.
1. Define a tag name for data setting for an ECW_I (external communication function block)
(WT003 in the example).
2. Define a tag name for data readback for the variable that will be used for reading the desired
data back (RB003 in the example).
3. Set data from the external device (FCS in this example) using the specification <tag name
for data setting>.PVI32. In the example, data is set via WT003.PVI32.
4. Read the data back to the external device (FCS in the example) using the specification
<tag name for data readback>.PVI32. In the example, data is read back via RB003.PVI32.
SEE
ALSO For a detailed explanation of OPMK (operation mark), see the following:
Data Items Common to Mapping Blocks/Mapping Elements in D2.1, Overview of Tag Name Interfaces
SCS
Logic
LTFCS FB
(Interference-free)
Sender FCS
D060001E.ai
SEE
ALSO For details on diagnostic information messages, see the following:
No. 4133 in 2.1, System Alarms of the Messages (IM 32S02B10-21E)
SEE
ALSO For details on diagnostic information messages, see the following:
No. 4134 in 2.1, System Alarms of the Messages (IM 32S02B10-21E)
SCS
Logic
LTSND FB
(Safety)
D060002E.ai
SEE
ALSO For engineering procedure flow, see the following:
n SCS Link Transmission in 2.1.6, Settings for Exchanging Data between FCS and SCS of the
Integration with CENTUM VP/CS 3000 (IM 32S01E10-21E)
For engineering function details required for engineering, see the following:
5.3, SCS Link Transmission Definition of the Engineering Reference (IM 32S04B10-21E)
For points to note on FCS data setting, see the following:
2.9, SCS Link Transmission of the Engineering Guide (IM 32S01C10-21E)
Revision Information
Title : Safety Control Station Reference
Manual No. : IM 32S03B10-21E