6 Introduction to the Workbench

Copyright Ó2005 Yokogawa System Center Europe B.V.

Table of contents

6 Introduction to the Workbench.....................................................................................6-1

6.1 Introduction to the Workbench................................................................................. 6-3
6.1.1 Chapter Objectives ............................................................................................... 6-4
6.1.2 What is the ProSafe-RS Workbench...................................................................... 6-5
6.1.3 Installing the Workbench software on a PC........................................................... 6-6
6.1.3.1 Workbench Files and Directories......................................................................6-7
6.1.3.2 The Workbench................................................................................................6-8
6.1.3.3 Opening a New Project ....................................................................................6-9
6.1.3.4 Properties of a SCS project.............................................................................6-10
6.1.3.5 Opening an existing project ............................................................................6-11
6.1.3.6 The Main Screen of the Workbench – Link Architecture ................................6-12
6.1.3.7 The Hardware Architecture Window ..............................................................6-18
6.1.4 Variables (Local, Global, I/O)..............................................................................6-19
6.1.4.1 Declaring variables, parameters, types and defined words...............................6-21
6.1.4.2 I/O configuration............................................................................................6-30
6.1.5 The Multiple Language Editor .............................................................................6-51
6.1.6 Appearance of the Multi-language editor .............................................................6-52
6.1.6.1 Example: How to use the Multi-Language editor ............................................6-59
6.1.7 Compiling/Building the Program .........................................................................6-64
6.1.7.1 Building A POU.............................................................................................6-65
6.1.7.2 Building a Resource .......................................................................................6-66
6.1.8 Downloading/On-line change...............................................................................6-67
6.1.8.1 Procedure for Off-Line download...................................................................6-69
6.1.8.2 On-line Change Download .............................................................................6-70
6.1.8.3 Procedure for the Master Database Off-line download ....................................6-71
6.1.9 Libraries, including Libraries in Projects..............................................................6-72
6.1.9.1 How to create a Library with user created Function Blocks.............................6-73
6.1.9.2 Including Libraries in a SCS project ...............................................................6-79
6.1.9.3 Making modifications to an included FB (from a library) ...............................6-83
6.1.9.4 Distributing/maintaining Libraries..................................................................6-84
6.1.10 Debugging & Simulating .....................................................................................6-85
6.1.10.1 Simulation .....................................................................................................6-86
6.1.10.2 Debug ............................................................................................................6-91

6-2 RSWB rev 1.2

6.1 Introduction to the Workbench
ProSafe-RS Workbench is the software program used to configure the ProSafe-RS system.
In the Online Documentation the name ‘SCS Manager’ is also used instead of Workbench. In this
training manual we only use the last name.
This section gives an overview of the set-up and structure of the ProSafe-RS configuration program.
Once the software program is explained, the focus of the discussion will be the Link Architecture
Screen and Hardware Architecture Screen. Topics to be covered include the information available
from these screens and techniques for working with items on the Architecture Screens.

RSWB rev 1.2 6-3

6.1.1 Chapter Objectives
After completing this section, the student will be able to:
· Explain the purpose of the ProSafe-RS Workbench software program.
· Install the ProSafe-RS Software on a PC.
· Identify the directories and files created and used by ProSafe-RS Workbench.
· Access and edit a pre-existing configuration.
· Describe the purpose of the Link Architecture Screen and Hardware Architecture Screen and
the information presented on it.
· Obtain ProSafe-RS diagnostic information.
· Know the characteristics of a new project.
· Know what variables are and their parameters.
· The relation between variables and physical input/output channels.
· How the program can be built (compiled).
· How the program can be downloaded.

In the chapter Tutorial a step by step example of a project can be found. This chapter shows the
relations between different screens and builders.

6-4 RSWB rev 1.2

6.1.2 What is the ProSafe-RS Workbench
The Workbench is used to configure the ProSafe-RS system.

The Workbench also provides the user with the ability to:
· Transfer configurations to the PLC.
· Edit a Project.
· View and update variables.
· Perform system troubleshooting.
· Produce documentation for a configuration.

The Workbench is a Windows application and is designed to run on any IBM compatible PC.
The Workbench can print to any printer supported by Windows. It uses the Windows print spooler.

Two languages are available for configuring the ProSafe-RS system:

1. Function Block Diagrams

2. Ladder Logic Diagrams

Both languages can be used together and integrated into a single application.

RSWB rev 1.2 6-5

6.1.3 Installing the Workbench software on a PC
Follow the prompts in the installation programs and installation manual.
Reference:
· Title: Installation
· Manual No.: IM 32S01C50-01E

· During Installation the Virus Checker should be switched off.

· The system will ask if there is a next key code floppy disk (you must have inserted the floppy
into the system), answer NO on this question.

6-6 RSWB rev 1.2

6.1.3.1 Workbench Files and Directories
As shown in the figure below, the files that are needed to run the Workbench are contained in several
directories: Projects, Shared, Users, Workbench and Yokogawa.
The following directories and sub-directories need special attention:

Figure 6-1

RSWB rev 1.2 6-7

6.1.3.2 The Workbench
In this paragraph the following options will be described:
· Opening of a new SCS project
· Properties of a SCS project
· Opening an existing SCS project
· The main screen of the Workbench (Link Architecture)
· The Hardware Architecture
· Builders

Projects can function as library in other

projects.
Often called typicals.
E.g. input typicals and output typicals

Figure 6-2

6-8 RSWB rev 1.2

6.1.3.3 Opening a New Project
If a new Project is selected, the following information (see next figure) must be inserted:
· The destination folder:
o The path of the folder must not be longer then 256 character and should not include
spaces.
o For example: C:\RS-Projects\MY_FIRST_PR.

Figure 6-3

RSWB rev 1.2 6-9

6.1.3.4 Properties of a SCS project
The properties of a SCS project will be displayed after you create a new project, or can be changed
later (select the menu option: Tools -> Engineering -> SCS Project).

Figure 6-4

The IP address is an option which can be found in the Hardware Architecture.

The domain and station number must also be changed in the hardware architecture.

6-10 RSWB rev 1.2

6.1.3.5 Opening an existing project
A RS project (which is only a directory) can contain more then 1 SCS project. SCS project names
start with SCS followed with a ddss number (domain and station).

Figure 6-5

RSWB rev 1.2 6-11

6.1.3.6 The Main Screen of the Workbench – Link Architecture
If a new or existing project has been opened, the main window of the workbench will appear. This
window is called the Link Architecture.
At the top of the next figure you will find a description of the symbols in the Link Architecture.

6-12 RSWB rev 1.2

 External binding list for
Link Architecture, to configure connections to for example Switches an application to
the application CS3000 debug mode

Hardware Architecture, to Builds the current project, Switches an application to

configure resources library simulation mode

Dictionary View, for editing Performs an Online Change,

Builds the current resource
external or internal variables Download
IO wiring View, to connect
physical IO to defined Builds a Program Adds/Removes dependensies
variables
Downloads resource code to
DO NOT USE
targets

Blue:
Editing mode

Green:
Realtime, debug or Simulation

Computer
User name
name

Figure 6-6

RSWB rev 1.2 6-13

6.1.3.6.1 The menu option Project in Link Architecture

Figure 6-7

6-14 RSWB rev 1.2

6.1.3.6.2 The menu option Tools in Link Architecture

Figure 6-8

RSWB rev 1.2 6-15

6.1.3.6.3 The menu option Debug in Link Architecture

Accesses the Download editor from where you download resources into
target nodes
Starts the project in test mode

Starts the project in simulation mode

Downloads only the changes made since the last download for the selected
running resource. The download includes the symbol table (complete or
reduced as selected in the resource's compilation options).

Do not use

Do not use
Do not use
Do not use
Do not use
Do not use
Accesses the Diagnosis window displaying general and status information for the
selected resource
Updates the resource status information, appearing in the title bar, for all resources

Switches between real time and cycle to cycle mode for the selected resource

Executes one cycle at a time, while in cycle to cycle mode

Accesses the Cycle Time editor where you set
the cycle time for the selected resource
Executes the current line and then steps to the next
Executes the current line and then steps into the next
Shows the current step

Figure 6-9

6-16 RSWB rev 1.2

6.1.3.6.4 The Resource Window Workspace in the Link Architecture

Figure 6-10

RSWB rev 1.2 6-17

6.1.3.7 The Hardware Architecture Window
The Hardware architecture window is used to define, change or modify hardware specific parameters.
The window can be activated from the Link Architecture window.

Figure 6-11

6-18 RSWB rev 1.2

6.1.4 Variables (Local, Global, I/O)
Within the workbench the following terms will be used in relation with variables:
· Dictionary
The dictionary contains all variables. This includes variables which are bound or unbound to
physical IO. In this dictionary it is possible to define variables into variable groups.

· Local Variables
Local variables are variables which are unique only within a POU. In a resource the same
name but referring to different variables could occur in other POU’s.

· Global
Global variables are unique within a resource.

· IO
IO signal is unique within a resource.

· Variable group
A variable group contains variables with a specific relation to each other. A User will define
this group and the variables in the group.

· Producer/Consumer Variable Group

To perform the Inter-SCS safety communication. For this communication dedicated Function
Blocks are available, for the sender (producer) and receiver (consumer). Variables called
‘binding variables’ are used to relate each variable of the sender and the receiver.

· External variable bindings

are bindings between variables of resources belonging to different projects.

· Variable grid
The variable groups are shown in the variables Tree, their contents are defined within the
Dictionary variables grid.

Variable names must be conform to the following rules:

1. Names cannot exceed 16 characters.

2. The first character must be a letter (or _ underscore).
3. Subsequent characters can be letters, digits or the underscore character.
4. Global variable names may not be duplicated within a resource.
5. Local variable names:
a. may not be duplicated within a POU
b. may not have the same name as a global variable

RSWB rev 1.2 6-19

 Figure 6-12

In the figure above you see the relation between variables and variables which are used outside the
current SCS.
o For variables used in CS3000 you need the tagname builder (Tools-> Engineering ->
tagname builder).
o For variables used in other systems which communicates over ModBus the Modbus Builder
must be used ( Tools -> Engineering -> Modbus Builder).

6-20 RSWB rev 1.2

6.1.4.1 Declaring variables, parameters, types and defined words
In the workbench the following terms will be used:
1. variables which can be local, global, IO
2. parameters as the nubs of a user-created function block
3. types as we know them, for example IO_BOOL or IO_REAL
4. defined words, for example: “yes is true” or “switched-off is false”
Variables can be declared in the Variable Grid. The variable grid is a tab in the dictionary.

In the figure overleaf the options available in the variable grid can be found.
1. how to open the dictionary
2. no further action, just zoomed in
3. the variable grid, in this grid you define variables
4. parameter grid, for function blocks. If you have to define a User Defined FB with several
input and output parameters, the parameters must be defined in this grid.
5. type grid
In the type grid you can see how a type has been constructed. It is not possible to create
your own types.
6. defined word grid
The defined word grid is useful if an alias has to be defined.

RSWB rev 1.2 6-21

 Figure 6-13

6-22 RSWB rev 1.2

6.1.4.1.1 The variable grid

The variable grid is used to define variables. There are two types of variables: Locals and Globals.
Local variables are only available within a POU. Global variables are available throughout all POUs.
Every variable has some specific extra information, for example the type (BOOL, REAL,..). This
extra information is also called ‘parameters’ (don’t confuse them with the Parameter tab for functions
and function blocks).
All these parameters can be filled in during definition but can also be changed in a later stage of the
configuration.

Figure 6-14

Figure 6-15

The parameters for the variables:

Common for all types
[Name]: Variable name consisting of up to 16 alphanumerical characters starting with
an alphabetic character (or underscore)
The name is recommended as follows:
Analog inputs: Ainnsscc
Digital inputs: Dinnsscc

RSWB rev 1.2 6-23

 Digital outputs: DOnnsscc
nn:Node No. ss:Slot No. cc:Channel No.
[Alias]: Alias name for the ladder diagram up to 16 alphanumerical characters
[Group]: Group name or "None"
[Type]: BOOL, DINT, SINT, REAL, TIME, STRING, COM_BOOL, COM_DINT,
COM_REAL, IO_BOOL, IO_REAL, Function Blocks
[( )]: Character length when Type is “STRING”
[Dimension]: Dimension for array variables (not available)
[Attribute]: Read/Write/Free
[Scope]: Global/Local
[Direction]: Input/Output/Internal
[Init.value]: Initial value of the variable
[Wiring I/O]: wiring information (only displayed)
[Comment]: User comment up to 64 alphanumerical characters
[Retain]: Yes /No Setting 'No' is recommended.
When ‘Yes’ is specified, the value present when CPU stops is retained and
this retained value is used on restart.
[Address]: Optional address ($1 to $FFFF)
It is available from external applications for access to variables on a SCS
target.

Below specific information concerning the different types can be found.

Analog Inputs
The following items should be specified on analog inputs.
[Name] : Variable name e.g. AI010101
[Type] : IO_REAL
[Attribute] : Read
[Direction] : Input

Digital Inputs
The following items should be specified on digital inputs.
[Name] : Variable name e.g. DI010201
[Type] : IO_BOOL
[Attribute] : Read

6-24 RSWB rev 1.2

 [Direction] : Input

Digital Outputs
The following items should be specified on digital outputs.
[Name] : Variable name e.g. DO010301
[Type] : IO_BOOL
[Attribute] : Write
[Direction] : Output

RSWB rev 1.2 6-25

6.1.4.1.2 The parameter grid

In the system you will find standard functions and function blocks. It is also possible to create your
own function. How to define a function or function block will be explained in the chapter Tutorial. A
function block can have several input nubs and output nubs (a function only has 1 output nub). Before
you start programming the inside of a function block you will define the parameters.

Figure 6-16

The parameters available

[Name]: Variable name consisting of up to 16 alphanumerical characters starting with

an alphabetic character (or underscore)
[Short name]: Alias name for the ladder diagram up to 16 alphanumerical characters
[Type]: BOOL, DINT, SINT, REAL, TIME, STRING, COM_BOOL, COM_DINT,
COM_REAL, IO_BOOL, IO_REAL, Function Blocks
[Direction]: Input or Output
[Comment]: Used for more detailed information
[( )]: Character length when Type is “STRING”
[Dimension]: Dimension for array variables (not available)

6-26 RSWB rev 1.2

 Figure 6-17

RSWB rev 1.2 6-27

6.1.4.1.3 The type grid (only for viewing not for defining new types)

Figure 6-18

The parameters available:

[Name]: Name consisting of up to 16 alphanumerical characters starting with an

alphabetic character (or underscore)
[Elt.Type]: Alias name up to 16 alphanumerical characters
[()]:
[Comment]: Used for more detailed information

6-28 RSWB rev 1.2

6.1.4.1.4 The defined word grid

The defined word grid can be used to create terms which are clearer to the user in Ladder or in
Function block logic.
The term ‘Switch_closed’ would probably be more meaningful than TRUE.

Figure 6-19

The parameters available:

[Word]: Name consisting of up to 16 alphanumerical characters starting with an

alphabetic character (or underscore)
[Equivalent]: Alias name up to 16 alphanumerical characters
[Comment]: Used for more detailed information

RSWB rev 1.2 6-29

6.1.4.2 I/O configuration
I/O configuration is more than only declaring a variable and attaching it to a physical I/O point.
After the creation of these I/O signals you also have to deal with I/O specific parameters, for example
what to do with Short Circuits or Input Processing Faults.
In the following figure the steps (from right to left) of the advised order for defining I/O signals is
depicted.
It also relates to the sub-sections in this paragraph. The dictionary view has already been explained
previously in this chapter and will not be repeated here.

Figure 6-20

6-30 RSWB rev 1.2

6.1.4.2.1 Connecting declared variables to physical I/O points

The first step for connecting variables to physical I/O points can be done in the I/O wiring View
window.
Select the icon for I/O wiring from the Link Architecture window or select the option I/O wiring from
the Window Workspace.

Figure 6-21

In the I/O wiring view the first step is to add devices.

You can select out of the analog input devices (4-20 mA, 1-5V, 1-10V), discrete inputs or discrete
outputs.
The other options are the RS232 or RS422/485 communication modules.
The device number is a unique number in the configuration which is not the slot number. The slot
number can be changed using the parameters of the device.
Once the devices has been added, the option at the top are the parameters. See the figure below.

RSWB rev 1.2 6-31

 Figure 6-22

6-32 RSWB rev 1.2

6.1.4.2.2 Using the IO parameter builder to set parameters for physical IO
points

The “I/O parameter builder” can be selected from the Link or Hardware Architecture window, by
selecting the option Tools -> Engineering -> I/O parameter builder.
The figure below is an example of this builder.
The I/O parameter builder is not suitable for defining I/O cards. This must be done in the I/O wiring
view.
After an I/O card has been defined and the variables have been connected to the physical I/O points,
this builder can be used to set various physical parameters related to this I/O point. The amount of
information will be different for every I/O card.
In the right side of the builder 2 tabs are available: Module or Channel.
In the Module tab only a few parameters, for example comment, can be changed. All other
information is set in the I/O wiring screen.
The Channel tab is divided in multiple columns. The first 3 columns have a fixed position, and
contain information as: Channel number, Wiring positions and I/O variable name. The columns after
the third column varies depending of the selected IO card.

Figure 6-23

Common Settings for Inputs and Outputs (Digital and Analog)

Some of the setting items for process data inputs and outputs of an SCS are common for all
input/output types and some are different for each input/output type. This section explains setting
items for nodes and common setting items for input/output modules.
Common Setting Items for Input/Output Modules
The following setting items are common for each input/output module parameter tab of I/O Parameter
Builder.

RSWB rev 1.2 6-33

 · 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.

· 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.

· 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.

· 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.
· 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.
· 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 via on-line change download.
· Channel Common Information
The following items are common for all modules with channel parameters.
· Channel Number
This is a list of the channel numbers displayed in I/O Wiring View of SCS Manager. They are
sequential numbers starting from 1.
This item is only for display and cannot be edited.

· Wiring Position
This is a list of the channel names displayed in I/O Wiring View of SCS Manager. They are
determined by device number and channel identification number. The channel identification
numbers used for channel names are sequential numbers starting from 0. The channel
numbers of the input modules are prefixed with %IU while the channel numbers of the output
modules are 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.2, ... %IU1.14,
%IU1.15
In the case of a 8-channel output module: %QU3.0, %QU3.1, ... %QU3.6, %QU3.7

6-34 RSWB rev 1.2

 · I/O Variable Name
This is a list of the names of input/output variables assigned to channels in I/O Wiring View
of SCS Manager.
This item is only for display and cannot be edited.

· Direction
This item indicates whether a signal is an input or output signal.
This item is only for display and cannot be edited.

· Comment
This is a comment for an input/output variable specified in the Dictionary View of SCS
Manager. Any character string can be entered.
This item is only for display and cannot be edited.
A variable comment for an input/output variable defined in Dictionary View of SCS Manager
is displayed as a channel comment of a wired channel. Up to 64 characters can be used for the
definition of this comment, but only up to 32 characters can be used in SCS databases;
therefore make sure not to use more than 32 characters. Channel comments for unused
channels (unwired channels) are not displayed. Comments for DI/DO are set for SCS
databases and used as identifiers of SOE.

· TIP
If comments for DI/DO variables are changed in the Dictionary View of the SCS Manager,
discrepancies may occur due to the input/output definition changes, and it becomes necessary
to perform on-line change download to the SCS. Since this changes only the definitions in the
databases of the SCS (no changes are made to the setting information of the input/output
modules themselves), the inputs and outputs are not influenced by an on-line change.

RSWB rev 1.2 6-35

6.1.4.2.3 The parameters for Analog Inputs

Figure 6-24

· Input Processing at Fault

This item specifies an input value that will be used if input errors other than transmitter errors
are detected. The faults that can be detected include errors on both sides of the path from the
CPU to an analog input module, errors in analog input modules, channel errors, IOP and field
wiring errors (transmitter errors are not included).

· [Hold]:
The value immediately before the fault was detected is maintained when an error is
detected.

· [Fixed Value]:
The specified input value is set when an error is detected (default).
This setting item can be changed via on-line change download.

· Input Value at Fault

If a fault (Input Processing) is detected the defined fixed value will be used. Specify the input
value at error (in %) in the range from -25.0 to 125.0. The default value is 0.0%.

6-36 RSWB rev 1.2

 This item is enabled only when [Input Processing at Fault] is selected. If the input processing
of the channel is set to SQRT, this setting value will used directly as the input value when
error occurs. (The value set here will not be square-rooted when used as the substitute input
value.)
This item can be changed via on-line change download.
· Input Processing at Transmitter Fault
This is a value set the same as with the input value, if a transmitter error is detected (a value
used as an input value at error). This item is only enabled for current inputs.
[Input Value at Fault]:
Follow the setting of [Input Processing at Fault] if a transmitter error occurs (default).
[Raw Data]:
The raw I/O data is set as the input value.
This item can be changed via on-line change download.

· Signal Conversion
This item specifies the conversion method of the input signal.
[LINEAR]:
The physical range specified by the low limit value and high limit value of the range (mA or
V) is converted to 0 to 100 (%) data (default).
[SQRT]:
The input signal will be checked before square-root conversion. If the signal is normal, the
square-rooted datum will be a 0-100% datum. The square-root conversion is illustrated as
follows:
This item can be changed via on-line change download.

· High Limit/Low Limit

These items refer to the upper limit value and lower limit value of the terminal measurement
range.
Values between 0 and 100% are assigned to the specified measurement range. The
measurement range can only be changed for voltage input modules.
This item can be changed via on-line change download. Note, however, that IOM download
is also performed at the same time.

· Unit
This is the unit of the input signal and determined by the type of input module.
This item is only for display and cannot be edited.

· Detect IOP (High)

This item specifies whether or not to detect an input open circuit error if a process value
exceeds the threshold value.

RSWB rev 1.2 6-37

 [No]:
An input open circuit error is not detected.
[Yes]:
An input open circuit error is detected if a process value exceeds the threshold value (default).
The threshold value is specified with [Threshold of IOP (High) %].
This item can be changed via on-line change download.

· Detect IOP (Low)

This item specifies whether or not to detect an input open circuit error if a process value falls
below the threshold value.
[No]: An input open circuit error is not detected.
[Yes]: An input open circuit error is detected if a process value falls below the threshold
value (default).
The threshold value is specified with [Threshold of IOP (Low) %].
This item can be changed via on-line change download.

· Threshold of IOP (High) %

This item specifies the upper limit level at which an input open circuit error is judged. This
item is only enabled when [Yes] is specified for [Detect IOP (High)]. An input open circuit
error is judged if the process value exceeds the threshold of IOP (High level).
The default value is 112.5% (at current input) and 106.3% (at voltage input).
Note that the following checks are performed even if [No] is specified for [Detect IOP
(High)].

An error occurs if a value is entered such that the value of [Threshold of IOP (High) %]
becomes equal to or smaller than the value of [Threshold of Transmitter Fault (High) %].
An error occurs if a value outside the range -25% to 125% is entered.
An error occurs if a value outside the analog input module accuracy guarantee range is
entered.

[Accuracy guarantee range]

Current input: -18.75% to 118.75% (1 to 23 mA)
Voltage input: Varies depending on the range specification (0.1 to 11 V)
If the range is set to 1 to 10 V: -10% to 111.1%
If the range is set to 1 to 5 V: -22.5% to 125%

In addition to the checks above, the following input checks are performed.

6-38 RSWB rev 1.2

 Range: -25% to 125%
Number of input characters: Up to 7 single-byte characters
Number of decimal places: Up to 2 digits
This item can be changed via on-line change download.

· Threshold of IOP (Low) %

This item specifies the lower limit level at which an input open circuit error is judged. This
item is enabled only when [Yes] is specified for [Detect IOP (Low)]. An input open circuit
error is judged if the process value falls below the threshold of IOP (Low level).
Specify a value between -25.0% and 125.0%. The default value is -6.3%.
Note that the following checks are performed even if [No] is specified for [Detect IOP
(Low)].
An error occurs if a value is entered such that the value of [Threshold of IOP (Low) %]
becomes equal to or greater than the value of [Threshold of Transmitter IOP (Low) %].

An error occurs if a value outside the range -25% to 125% is entered.

An error occurs if a value outside the analog input module accuracy guarantee range is
entered.

[Accuracy guarantee range]

Current input: -18.75% to 118.75% (1 to 23 mA)
Voltage input: Varies depending on the range specification (0.1 to 11 V)
If the range is set to 1 to 10 V: -10% to 111.1%
If the range is set to 1 to 5 V: -22.5% to 125%

In addition to the checks above, the following input checks are performed.
Range: -25% to 125%
Number of input characters: Up to 7 single-byte characters
Number of decimal places: Up to 2 digits
This item can be changed via on-line change download.

· Detect Transmitter Fault (High)

This item specifies whether or not to detect a transmitter error if a process value exceeds the
threshold value. This item is only enabled for current inputs.
[No]:
A transmitter error is not detected.
[Yes]:

RSWB rev 1.2 6-39

 A transmitter error is detected if a process value exceeds the threshold value (default). The
threshold value is specified with [Threshold of Transmitter Fault (High) %].
This item can be changed via on-line change download.

· Detect Transmitter Fault (Low)

This item specifies whether or not to detect a transmitter error if a process value falls below
the threshold value. This item is enabled only for current inputs.
[No]:
A transmitter error is not detected.
[Yes]:
A transmitter error is detected if a process value falls below the threshold value (default).
The threshold value is specified with [Threshold of Transmitter Fault (Low) %].
This item can be changed via on-line change download.

· Threshold of Transmitter Fault (High) %

This item specifies the upper limit level at which a transmitter error is judged. This item is
enabled only when [Yes] is specified for [Detect Transmitter Fault (High)]. A transmitter
error is judged if the process value exceeds the threshold of transmitter fault (High level).
This item is only enabled for current inputs.
The default value is 106.3%.
Note that the following checks are performed even if [No] is specified for
[Detect Transmitter Fault (High)].

An error occurs if a value is entered such that the value of [Threshold of IOP (High) %]
becomes equal to or smaller than the value of [Threshold of Transmitter Fault (High) %].
An error occurs if a value outside the range -25% to 125% is entered.
An error occurs in I/O Parameter Builder if a value outside the analog input module accuracy
guarantee range is entered.

(Accuracy guarantee range)

Current input: -18.75% to 118.75% (1 to 23 mA)
This item can be changed via on-line change download.

· Threshold of Transmitter Fault (Low) %

This item specifies the lower limit level at which a transmitter error is judged. This item is
enabled only when [Yes] is specified for [Detect Transmitter Fault (Low)]. A transmitter error

6-40 RSWB rev 1.2

 is judged if the process value falls below the threshold of transmitter fault (Low level). This
item is only enabled for current inputs.
The default value is -1.25%.
Note that the following checks are performed even if [No] is specified for [Transmitter failure
low limit detection].

An error occurs if a value is entered such that the value of [Threshold of IOP (Low) %] level
becomes equal to or greater than the value of [Threshold of Transmitter Fault (Low) %].
An error occurs if a value outside the range -25% to 125% is entered.
An error occurs if a value outside the analog input module accuracy guarantee range is
entered.
(Accuracy guarantee range)
Current input: -18.75% to 118.75% (1 to 23 mA)
This item can be changed via on-line change download.

· Field Power Diagnosis

Specify the type of wiring for this item. It is used to determine the method of power supply
diagnosis for the input modules. Current input modules perform self-diagnosis of whether or
not the power is supplied correctly to the field according to this setting. This item is only
enabled for current inputs.

IMPORTANT
Make sure that this setting matches with the 2-wire/4-wire system setting made using the
setting pins in an 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.
None: Do not perform field power supply diagnosis.
2-wire:
2-wire system (Default: Diagnose that the power is supplied to the field. Diagnosis indicates
normal if the power is supplied to the filed device.)
4-wire:
4-wire system (Diagnose that no power is supplied to the field. Diagnosis indicates normal if
no power is supplied to the filed device.)
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· P&ID Tag Name

This is a comment that the user can supply in order to make it easy to identify information
drawn on a P&ID drawing with a given channel. The comment should be written using up to
16 single-byte characters or 8 double-byte characters.

RSWB rev 1.2 6-41

 This setting item can be omitted.
This item can be changed via on-line change download.

6-42 RSWB rev 1.2

6.1.4.2.4 The parameters for Discrete Inputs

Some items among these setting items can be online modified and downloaded. However, IOM
download is required after online downloading. The IOM downloading behaves as follows:
When online maintenance starts, the data status of all channels will become BAD and the input
signals of all channels of the module are processed according to [Input Processing at Fault] settings.
· When online maintenance finishes, the input values will be automatically put to the channels
thus the data status of all channels becomes GOOD.
· For dual-redundantly configured I/O modules, the odd-numbered module takes the control
right first.

Figure 6-25

Parameters to set in the Module Tab

· Software Filter
The software filter is applied for reducing the 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 spurious
error actions.
The filter setting value multiplied by 10ms (sampling period) is the filter time. The chattering
signals occurred within this filter time will be eliminated. For an example, if the filter setting
value is 2, the chattering signals shorter than 20ms (2x10ms) will be eliminated.
If the filter setting value is 0, the noise signals will not be filtered thus PV varies with the
noise signals. In general, the filter setting value should not be set to 0.
This setting item can be modified and downloaded online and, however, followed with IOM
downloading.

· Automatically Delete Noisy Events

RSWB rev 1.2 6-43

 This item specifies whether or not to delete events automatically, if many events that are
targets of SOER occur.
If a channel repeatedly generates too many events, the events from other channels may be
lost.
With this option, the number of repeated events per channel can be limited. If the number of
events generated in a channel exceeds the specified number in [Number of SOE Events]
within a specified time period, the events beyond the limit will be automatically deleted. For
an example, if 3 is set to [Number of SOE Events] and more than 3 events occurred within a
specified time period, the 4th and subsequent events within a specified time period will be
automatically deleted.
However, if the last event is contradictory with the current status of the DI, a stimulatory
event will be generated to indicate the DI status.
Yes: Automatically delete events if many events occur.
No: Do not delete events even if many events occur (default).
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· SOE Deletion Schedule

This item specifies the time setting for [Automatically Delete Noisy Events] in units of
seconds.
This setting item is enabled if [Yes] is selected for [Automatically Delete Noisy Events].
Select 0.5, 1.0, 1.5, 2.0, 2.5, 3.0 or 3.5 seconds. The default value is 1.0 second.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· Number of SOE Events

This item specifies the number of events for [Automatically Delete Noisy Events]. This
setting item is enabled if [Yes] is selected for [Automatically Delete Noisy Events].
Select either 3 or 5. The default value is 3 events.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

6-44 RSWB rev 1.2

 Figure 6-26

Parameters to set in the Channel tab

· Input Processing at Fault
This item specifies a value that will be passed to the application logic instead of the input
from the field if an error is detected in the input of the relevant channel, including channel
errors, discrete input module errors and errors in the path from the CPU to the relevant
discrete input module.
0: The input value is set to 0 at error detection (default).
1: The input value is set to 1 at error detection.
Hold: The value immediately before the error was detected is maintained when an error is
detected.
This item can be changed via on-line change download.

· Detect Disconnection (Open Circuit)

This item specifies whether or not to detect disconnection in the wiring.
Yes: Detect disconnection.
No: Do not detect disconnection (default). When the disconnection occurs, input value is 0
and the status is Good.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.
IMPORTANT
If [Yes] is set for [Detect Disconnection], disconnection errors can be detected. Make sure,
however, to mount a wiring check adapter (SCB100) on the relevant channel if you specify
[Yes]. If you specify [Yes] without mounting the adapter, the SCS erroneously recognizes a
disconnection error whenever the input value is OFF.

· Detect Short Circuit

This item specifies whether or not to detect short circuit in the wiring.

RSWB rev 1.2 6-45

 Yes: Detect short circuit (default).
No: Do not detect short circuit. When the short-circuit error occurs, input value is 1 and the
status is Good.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.
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 mount a wiring check adapter
(SCB110) on the relevant channel if you specify [Yes]. If you specify [Yes] without mounting
the adapter, the SCS erroneously recognizes a short-circuit error whenever the input value is
ON.

· Pulse Test
This item specifies whether or not to perform a pulse test (wiring check between the input
channels using pulse output).
Yes: Perform a pulse test (default).
No: Do not perform a pulse test.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.
IMPORTANT
If [Yes] is set for [Pulse Test], wiring short-circuit errors between input channels can be
detected. Make sure, however, to mount a wiring check adapter (SCB110) to the relevant
channel if you specify [Yes] for a channel whose input signal is always ON. If you specify
[Yes] without mounting the adapter, the SCS cannot detect inter-channel short circuit when
the input value is ON.

· SOER (Setting for SOER)

This item specifies whether or not to accumulate events for SOER when a signal changes.
Yes: Accumulate SOE events when a signal changes (default).
No: Do not accumulate SOE events.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

Trip Signal (Setting for SOER)

This item specifies whether or not to regard an event as a trip occurrence. This setting is only
enabled if [Yes] is set for [SOER].
OFF TRIP (1):
A change to OFF is regarded as a trip signal and SOE data before and after a trip is stored in
an SCS.
ON TRIP (2):

6-46 RSWB rev 1.2

 A change to ON is regarded as a trip signal and SOE data before and after a trip is stored in an
SCS.
No (0): Do not include in the targets of the trip signal (default).
This item can be changed via on-line change download.

· P&ID Tag Name

This is a comment that the user can supply in order to make it easy to identify information
drawn on a P&ID drawing with a given channel.
The comment should be written using up to 16 single-byte characters or 8 double-byte
characters.
This setting item can be omitted.
This item can be changed via on-line change download.

RSWB rev 1.2 6-47

6.1.4.2.5 Parameters for Discrete Outputs

Figure 6-27

· Output Shutoff Switch

This item specifies whether or not to activate the Output Shutoff switch if a dangerous failure
such as the output getting stuck in the ON status occurs. If the Output Shutoff switch is
activated, the output of all DO channels of the relevant module is set to OFF. If an error
leading to IOM error (e.g., overcurrent error due to short circuit) occurs, the Output Shutoff
switch is activated unconditionally regardless of the setting of this item.
Enable:
Activate the Output Shutoff switch if a dangerous failure such as the output getting stuck in
the ON status occurs (default).
Disable:
Do not activate the Output Shutoff switch even if a dangerous failure occurs.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· Output Value in Detecting Error

This item specifies a value output from a channel to the field if an error occurs on either side
of the CPU module or in the path to IOM. This definition is used as the fail-safe value set for
the output variables.

6-48 RSWB rev 1.2

 0: Output 0 to the field at error detection
1: Output 1 to the field at error detection
Hold: The value immediately before the error was detected is maintained when an error is
detected (default).
This item can be changed via on-line update download. Note, however, that IOM download is
also performed at the same time.

· Detect Disconnection
This item specifies whether or not to detect disconnection.
Yes: Detect disconnection (default).
No: Do not detect disconnection.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· Pulse Test (OFF)

This item specifies whether to perform the off-edge pulse test so as to use the off-edge pulse
to test the wiring of the channel that maybe switched to on status (when the contact is
switched on or short-circuits occurred among channels).
Yes: Perform the off-edge pulse test (default).
No: Do not perform the pulse test.
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· Pulse Test (ON)

This item specifies whether to perform the on-edge pulse test so as to use the on-edge pulse to
test the wiring of the channel that maybe clutched to off status (when the contact is switched
off or short-circuits occurred among channels).
Yes: Perform the on-edge pulse test
No: Do not perform the pulse test (default).
This item can be changed via on-line change download. Note, however, that IOM download is
also performed at the same time.

· SOER (Setting for SOER)

This item specifies whether or not to accumulate events for SOER when a signal changes.
Yes: Accumulate SOE events when a signal changes (default).
No: Do not accumulate SOE events.
This item can be changed via on-line change download.

· Trip Signal (Setting for SOER)

This item specifies whether or not to regard an event as a trip occurrence. This setting is only
enabled if [Yes] is set for [SOER].

RSWB rev 1.2 6-49

 OFF TRIP (1):
A change to OFF is regarded as a trip signal and SOE data before and after a trip is stored in
an SCS.
ON TRIP (2):
A change to ON is regarded as a trip signal and SOE data before and after a trip is stored in an
SCS.
No (0): Do not include in the targets of the trip signal (default).
This item can be changed via on-line change download.

· P&ID Tag Name

This is a comment that the user can supply in order to make it easy to identify information
drawn on a P&ID drawing with a given channel.
The comment should be written within 16 single-byte characters or 8 double-byte characters.
This setting item can be omitted.
This item can be changed via on-line change download.

6-50 RSWB rev 1.2

6.1.5 The Multiple Language Editor

The Multi-language editor has editing functions for graphical and textual languages.

Within the ProSafe-RS the Structured Text language is not supported.

These editing functions are automatically launched when an FBD or LD program is opened from the
Workbench.

The editor only allows new elements to be inserted if the current position is valid. Use the mouse or
cursor keys to move the current position around within the Workspace.

From the editor, you can perform several tasks:

o Build the current Program code (to check your Program and prepare the code for building the
Resource code)
o Print programs
o Launch the Dictionary for inserting/deleting/modifying new variables, parameters and defined
words

Note: Before creating new programs, you need to close the Dictionary.

When printing programs, the fonts used in the diagram are the same as for the editor. The FBD and
LD diagrams are scaled to fit the width of the printed page format (portrait or landscape). To adjust
the font for printed diagrams, you need to modify the font used for the editor.

To subsequently open another program, from the Multi-language editor

· From the File menu, choose Open (CTRL+O).

To add a description to a program

· From the File menu, choose Description.

RSWB rev 1.2 6-51

6.1.6 Appearance of the Multi-language editor
If you open a POU (Program Organisation Unit) the Multi-Language editor will appear
With this editor you can edit FBD (Function Block Diagrams) and LD (Ladder Diagrams). Function
Block Diagram and Ladder Diagrams are explained in the Chapter: “IEC 61131-3: Function Block
Diagram and Ladder Diagram”.

Figure 6-28

The editor has been split op in: title bar, menu bar, toolbar, workspace and message area. All these
items will be explained below.

Title bar
In the title bar the name of the SCS resource + name of the POU will be displayed

The Menu bar

Here you will find also options like
[File]:

· Build program, Dictionary

[Edit]:

6-52 RSWB rev 1.2

 · Insert Identifier = for example changing the type of Function Block, or changing the
input variable.
[Tools]:

· Show the execution order = the order in which the logic will be executed
· Show guidelines = the workspace has been divided in headers (Inputs, From,
Logic….). This can be made visible or not.
[Debug]:

· You can Debug (on the target machine) or Simulate (the program runs on the SENG
[Options]:

· Layout
In the layout window you can set the layout of your screen.

Figure 6-29

RSWB rev 1.2 6-53

Customize
With customize you can set for example the colors or the font of the text.

Figure 6-30

· Change the target code settings (the Resource Properties)

· Switch between Auto Input and Manual Input
When you have selected Auto Input, the system will respond with a variable pop-up
window if you are entering a variable
If you have selected Manual Input you can enter manually the variable name. During
Build the names will checked. Sometimes this option is easy to use if you want
to enter constants like True, False
· Numerical display
Here you can specify if you wish to see variables values presented in Hex or Dec
notation. Also the number of numeric characters can be entered.
· Hide/Show Variable comments
During variable definition you can enter comments. These comments can be made
visible in the workspace.

The Toolbar
Besides the normal symbols like save, print, undo, etc. there also options with relation to the FBD or
LD editor. The following sub-sections “a” until “g” explains the functionality of these options:

6-54 RSWB rev 1.2

 a. This part of the editor is typically used for FBD, but can also be inserted in LD
rungs. The following symbols are used:
Use of variables, I/O, locals, globals or fixed values

Definition of function blocks

If you have selected this option a pop-up window will appear.

Figure 6-31

From this window you can select a Function Block (1). The
amount of inputs can be defined in (2). In ProSafe-RS it is
not possible (at this moment) to give a FB an instance name
(4).

Lines

Line with negation

Make a corner or a split in a line, in other words: create a connection

point.

RSWB rev 1.2 6-55

 o In the figure above 2 corner point have been drawn. Now it is
possible to connect these points with a line. These points can be
drawn somewhere on the workspace or on a line.
Jump to a certain place (a label) on a sheet

The label where to jump to

Return to the requesting jump

b. The following symbols are used for LD (ladder Diagrams).

In LD you have a Left Power Rail and a Right Power Rail. The LD lines (Rungs)
must be connected to these rails otherwise they won’t work.
In LD it is also possible to use Function Blocks and Jumps. For more detailed
information please study chapter “IEC61131-3, FBD and LD”.
The following symbols have the following meaning

Left Power Rail

Input Contact

Vertical Connections

Coil (the output of a Rung)

Right Power Rail

c. Symbols for Comments and Execution Order

With this symbol you can include comments on your sheet. This also
possible by using (*this is comment*)

You can show the order of execution in the form of numerical tags
for the following elements in a FBD program: coils, returns, jumps,
instances of function blocks (declared or not), and variables where a
value is assigned in the program. When the order cannot be
determined, the tags display question marks (?). You can perform this
task from the menu bar, the toolbar, or keyboard shortcut (Ctrl+W).

d. Insert Identifier

This symbol lets you select a variable from the Select Variable
window

6-56 RSWB rev 1.2

 e. Build Program

Only the current POU will be compiled. If there is no Message

Window open the system will open one itself.

f. Debug

Debug (check the program on errors) is only possible on the Target

(SCS) system. If a test has to be performed on the SENG it will be
called Simulation

g. Simulation

Simulation is normally done to test the program before it will be

downloaded to the SCS or in case of changes.

Workspace (drawing area)

The drawing area is divided in Columns for the benefits of the user.
o Inputs
In this column you define the Physical Inputs
o From
Signals coming from another POU or from another SCS system.
Example: Intertrip signals.
o Logic
The application
o To
Signals to another POU or other SCS.
o Outputs
Physical outputs.

The workspace area is using a grid. If you move your mouse over the screen you will see on the status
line the position.

The first digit is the horizontal position and the second digit is the vertical.

RSWB rev 1.2 6-57

Message Window
You can make the Message area visible or not. It is also possible to clear the output. The system will
remember the messages from the last time you closed the editor.

6-58 RSWB rev 1.2

6.1.6.1 Example: How to use the Multi-Language editor
In the example below an AND gate with 2 inputs will be created. The variables are already available
and can be selected from the list.
1. Add a new POU. Use FBD as template.

Figure 6-32

2. Enter the name of the POU. In this example we use multilang

Figure 6-33

Double click on the new created POU

The system will respond with a remark that the architecture has been modified and if you
want to Save. Press <Yes>

RSWB rev 1.2 6-59

 Figure 6-34

3. The Multi-language window will appear.

Figure 6-35

4. First define the AND Function Block. Select the symbol for FBs and position the mouse on
the desired place.

6-60 RSWB rev 1.2

 Figure 6-36

5. The Select Blocks window appears. Select the AND Function Block and enter also the desired
number of inputs (default = 2). Press <OK>.

Figure 6-37

6. The AND block will appear.

RSWB rev 1.2 6-61

 Figure 6-38

7. Now the inputs and output must be connected to the nubs.

Select the Variable symbol.

Figure 6-39

8. If you move your mouse over the drawing area (keep the mouse pressed!) you will see a
rectangle with a v inside. Connect the two nubs to each other (1). Then drag and
drop the rectangle to the desired position (2) (the input to the input column, the output to the
output column)
9. If you release the mouse-button the Select Variable window will appear. Select the
<tagname>.v variable. The .v is the value. Perform the same action for all three variables (2
inputs and 1 output).

6-62 RSWB rev 1.2

 Figure 6-40

10. The result should look like the figure below. Now the POU can be built.

Figure 6-41

RSWB rev 1.2 6-63

6.1.7 Compiling/Building the Program

What is build
Building can be done on different levels:
1. Building a POU
2. Building the Resource
3. Building the Project
Before downloading code onto your target systems, you must first build the code of the whole project.
This operation builds the code of all resources of the project, and builds information used to recognize
your systems on networks. You cannot build projects open in the read-only mode.

You can choose to clean projects. However, after cleaning a project, you cannot perform online
changes. Therefore, to retain the ability to perform online changes, you can rebuild a project rather
than cleaning then building it.

While performing builds, the security state of unlocked resources and resources having no access
control switches to read-only mode. The security state of unlocked POUs and POUs having no access
control also switches to read-only mode. Locked resources and locked POUs remain locked.

To build the project

From the Project menu, choose Build Project or click on the Standard toolbar. If the hardware
architecture view is not changed, building resource code is enough to update.

6-64 RSWB rev 1.2

6.1.7.1 Building A POU

Figure 6-42

RSWB rev 1.2 6-65

6.1.7.2 Building a Resource

Figure 6-43

6-66 RSWB rev 1.2

6.1.8 Downloading/On-line change
The downloading functions transfer SCS execution data, which is a database containing the
specifications of an application logic, to an SCS.
The SCS execution data is saved as the master database in the SENG and the same data as in the SCS
is maintained at all times. There is no function to upload the SCS execution data to the SENG because
the SCS execution data is already saved in the SENG as the master database.
In the ProSafe-RS we know 4 types of downloads:

Figure 6-44

1. Off-line Download
This function downloads a database generated by building based on an application logic
created in the SENG. During the download, the functions running on the SCS stop and
resume the operation after the completion of downloading.

2. On-line Change Download

This function downloads only those application logics created in the SENG that were updated
since the last download. The functions running on the SCS keep operating during the
download as well. Note that on-line change download may not be possible depending on the
content of the updates.

3. Master Database Off-line Download

This function downloads the execution data that was active in an SCS again after replacing a
CPU module. The SCS database saved in the master database on the SENG is downloaded.
This download is performed when replacing hardware. In the case of a redundant CPU
module, this download is not required if only one module is replaced.

4. IOM Download

RSWB rev 1.2 6-67

 This function downloads the execution data that was active in an input/output module to a
new input/output module after replacing it. The data of the input/output module (part of the
SCS database) saved in the master database on the SENG is downloaded. This download can
only be performed when replacing hardware of input/output modules.

6-68 RSWB rev 1.2

6.1.8.1 Procedure for Off-Line download

1. Perform the building operation; an SCS database is generated based on application logic.
2. Launch Integrity Analyzer and analyze the database.
3. Launch Cross Reference Analyzer and analyze the database.
TIP
User should check the items that may require retesting for errors not detected by Cross
Reference Analyzer.
4. Use the SCS security level operation function to set the SCS security level to Level 0.
5. Select [Download] from the [Debug] menu of SCS Manager. The off-line download
confirmation dialog box appears.
TIP
If Integrity Analyzer or Cross Reference Analyzer has already been launched when you start
off-line download, a message prompting to close the analyzer is notified and the download
ends with an error.
If the SCS security level is Level 1 or Level 2 when you start off-line download, a message
prompting to set
Level 0 is notified and the download ends with an error. Set the security level to Level 0 again
and perform step 5 again.

6. Click the [OK] button.

For changing the SCS security level, a dialog box prompting for the new password will be
displayed. And a dialog box prompting to confirm the version control will also be displayed.
After off-line download is completed, the SCS restarts. The SCS database downloaded to the
SCS is automatically saved as the master database on the SENG together with the source
files.

7. Specify the password used when changing the SCS security level.
8. Use Version Control Tool to save the SCS project.

RSWB rev 1.2 6-69

6.1.8.2 On-line Change Download
1. Perform the building operation; an SCS database is generated based on an application logic.
2. Launch Integrity Analyzer and analyze the database.
3. Launch Cross Reference Analyzer and analyze database.

TIP
User should check the items that may require retesting for errors not detected by Cross
Reference Analyzer.

4. Use the SCS security level operation function to set the SCS security level to Level 1.
5. After shifting to the Target Test mode, the input/output modules subject to the online-change
downloading should be locked out on the I/O Lock Window of SCS Maintenance Support
Tool.
6. When the Target Test mode is finished, choose [On-line Change: Download] from the
[Debug] menu of SCS Manager or click the “On-line change download” button on the
toolbar.
The on-line change download confirmation dialog box appears.

TIP
If Integrity Analyzer or Cross Reference Analyzer has already been launched when you start
off-line download, a message prompting to close the analyzer is notified and the download
ends with an error.
If you perform on-line change download of output definitions, the related output modules
output zeros (0).

7. Click the [OK] button. A dialog box prompting to confirm the version control appears.
8. After shifting to the Target Test mode, the modified items need to be tested.
9. Release the lockout to the related input/output modules and exit from Target Test mode. And
then perform the output enable operation.
10. Use the SCS security level operation function to return the SCS security level to Level 2.
11. Use Version Control Tool to save the SCS project.

6-70 RSWB rev 1.2

6.1.8.3 Procedure for the Master Database Off-line download
1. Use the SCS security level operation function to set the SCS security level to Level 0.
2. Select [Controller] from the [Tools] menu of SCS Manager. The [Controller] launcher menu
appears.
3. Select [Master Database Off-line Download] of [Reset SCS] from the [Controller] launcher
menu. The master database off-line download confirmation dialog box appears.

TIP
If the SCS security level is Level 1 or Level 2, a message prompting to set the security level
to Level 0 is notified and the download ends with an error. Set the security level to Level 0
again, and repeat step 3.

4. Click the [OK] button.

5. For changing the SCS security level, a dialog box prompting for the new password will be
displayed.
6. Specify the password used when changing the SCS security level.

RSWB rev 1.2 6-71

6.1.9 Libraries, including Libraries in Projects
During the development of new projects, standards will be created. Standards like Input Typicals,
Output Typicals or other Safety standard logic.
Standards can be saved in user created Function Blocks, which are part of a Library.
A library looks a lot like a normal SCS project, with the difference that there is no connection to
physical hardware (resource, I/O cards).
The advantage of using libraries is that you need only to create them once and can use them multiple
times.

In this paragraph you will find:

o how to create a library with user created Function Blocks
o how to include them into an existing SCS project
o how to modify used Function Blocks (from Libraries)
o how to use libraries in other projects, in other words how to copy them

6-72 RSWB rev 1.2

6.1.9.1 How to create a Library with user created Function Blocks

RSWB rev 1.2 6-73

6.1.9.1.1 Creating a new Library

In the following figure steps a, b and c are depicted for creating a new Library. After a Library is
created you can open it as you do with a normal SCS project.
a. After you have started the Workbench select from the menu option File the
option New Project/Library.
b. If you create a SCS project the name should look like “SCS0102”.
For libraries you can use any name (off course not more then 8 characters,
starting with an alphabetic character and should not include spaces).
It is not necessary to have the libraries installed on the same directory as the
projects have been installed. As long the file is reachable at building time.
It is recommended to create a separated directory where you save the libraries. In
the example below the directory ProSafe_RS_Libraries has been created.
c. Select for template instead of SCS_Default_Target the option SCS_library

Figure 6-45

After the Library has been created the Link Architecture window appears with the Resource Window
Workspace. Now the user created Function blocks can be added.
In a Library you do not have to change the properties of the project like resource number. Changing
the IP address is (of course) not an option, otherwise the Library could not be used multiple times.

6-74 RSWB rev 1.2

6.1.9.1.2 Adding user created Function Blocks in a Library

The following steps (which are a repeat from the paragraph “How to create user defined Function
Blocks) in the next figure show how to create a new function block.
a. Select “Function blocks” and press the right-mouse button on the Resource
Workspace Window.
b. From the list select LD (Ladder Diagram) or FBD (Function block Diagram).
c. Enter the appropriate name for the function block

Figure 6-46

When the Function Block has been created you can use the Multiple Language Editor for entering the
logic (either in LD or in FBD).

RSWB rev 1.2 6-75

6.1.9.1.3 Use the Multiple Language Editor to create the logic in the Function
Block

a. Select “Function blocks” and press the right-mouse button on the Resource
Workspace Window.

Figure 6-47

b. In the dictionary select the option Parameters

Figure 6-48

6-76 RSWB rev 1.2

 c. (See previous figure)
Unfold the parameter list until you find the appropriate Function Block (in the
used example input_typ)
d. Enter the variables which are used in the Function Block.
The short name will be displayed in the function block; the direction defines if
the variable is positioned on the left or right side of the block.
It is also possible to use local variables within the block. These are not shown on
the Function Block.
e. After you have added all the variables, Save the dictionary. After you have saved,
close the dictionary.

Figure 6-49

f. From the Resource Workspace Window select the Function Block and open it

Figure 6-50

In the Multiple Language editor create your logic (FBD or LD). In the figure
below first the AND and OR block are placed.

RSWB rev 1.2 6-77

 g. Instead of using real I/O variables in the Select variable window which will pop-
up if you are entering variables, you should select Parameters

Figure 6-51

h. The Select variable window shows the defined variables available for this
Function Block
After the logic is finished and built (check for errors), close the library.
It is now ready for use.

6-78 RSWB rev 1.2

6.1.9.2 Including Libraries in a SCS project
Libraries which have been created can be included in a SCS project.
The following symbol is used in Link Architecture window to indicate that a Library is included:

Figure 6-52

The following procedure must be used to get the Libraries in the current SCS project.
Because it is not necessarily the case that a library project has been created on the same computer, the
following procedure shows also how to distribute the created Library (could be from another
computer) to the folder of the current SCS project. In this project folder a special Library folder is
available.

a. Create a new or open an existing SCS project.

b. Select from the Link Architecture window the option Tools. From the the Pull-
down menu select the option Add/Remove dependencies

Figure 6-53

RSWB rev 1.2 6-79

 c. In the form Add/Remove dependencies press the Add button

Figure 6-54

d. In the Open window select the library file (the .mdb file) and.
e. press the Open button
f. In the Add/Remove Dependencies window the selected Library is listed
g. Press OK to confirm.
h. Now the Function Blocks which have been defined in the library are available in
the current SCS project. Also the Library symbol should be displayed in lower-
right corner of the Link Architecture window.

6-80 RSWB rev 1.2

6.1.9.2.1 Selecting Function Blocks from the included Library

Function Blocks which have been created and stored in a Library project can be used in POUs.
The following example shows how to insert these FBs in a FBD POU.
a. Open the POU where you want to use the defined FB (out of the Library) from
the Resource Workspace window
b. Select from the Multiple Language Editor the option to Select Function Blocks.
The Select Blocks window will appear.

Figure 6-55

c. Select from the list the Function Block which have been created during the
library project. In front of the FB the following symbol should be displayed
d. Press the OK button to confirm the selection.
e. Now the function block is positioned in the editor.

Note:
Function Blocks which have been included from a library can not be opened from the SCS project, in
other words: the logic inside a FB can only be reviewed from the library itself.

RSWB rev 1.2 6-81

When you Build the SCS project, warnings will occur. Because in the library certain types have been
declared automatically (like IO_BOOL and IO_REAL) which are also available in the SCS project
where the library has been included, these types are defined double. In the figure below you find an
example of the message box.

Figure 6-56

6-82 RSWB rev 1.2

6.1.9.3 Making modifications to an included FB (from a library)
If you make modifications to a library which has been included in a SCS project you must build the
Library but also the projects where the Library is used. Otherwise the old version will be still active.

The logic inside Function Blocks can be changed without deleting the function block from the POU
where it has been used.
If you are increasing/decreasing the amount of input/output nubs you must delete the FB from the
sheet where it has been used.

Recommendation:
It is strongly advised that a Typical Test is performed before start implementing the project (and all
the FBs from the Libraries are used). If for example a certain FB has been used 100 times and a
modification is required (amount of input/output nubs will change), each of the 100 FBs must be
deleted and inserted again.

RSWB rev 1.2 6-83

6.1.9.4 Distributing/maintaining Libraries
Often a central directory on the development environment has been appointed to save the Libraries.
From this central directory the libraries can be distributed to the SCS projects.
In the example below this distribution is illustrated.

Figure 6-57

6-84 RSWB rev 1.2

6.1.10 Debugging & Simulating
If you have created a new RS project or made a modification, in all situations you have to perform a
test before the system will run with the new application.
Testing can be done on the SENG, which actually means that only the application can be tested, this
test is called the Virtual Test.
The other test must be performed on a SCS or in a network of SCS systems, this is the TARGET test
Within the ProSafe-RS you can Debug or Simulate.

o Debug
where you test your application on real SCS systems. The debugger establishes the
connections with remote configurations. Execution errors and warnings can appear in the
Output Window. For this mode, ***** TARGET ***** is displayed in the title bar. In the
example below the header of the Link Architecture window displays that debug is on (the
Target, which means the real SCS).
The header in the Resource Workspace window is giving the warning that there is no code
available, this because there is no SCS connected.

Figure 6-58

o Simulation
where you simulate the running of the project on a SENG.
You can only start 1 simulator on a SENG. In other words: If you want to simulate inter SCS
communication, for example exchange of shutdown signal, you do need 2 Windows
platforms.
For this mode, SIMULATION is displayed in the title bar.

Figure 6-59

RSWB rev 1.2 6-85

6.1.10.1 Simulation
Before simulating a resource, the code for the simulation has to be generated for each resource. By
default, this option is checked in a resource's compilation/build options.
For simulation on a virtual machine the security of a system is not an issue.

When switching an application to Simulation mode, the Workbench verifies the coherency between
the current resource definitions and the resources' compiled code. The Workbench also verifies the
coherency between all versions of the resource code. You can access version information for a
resource.
If there is a difference between for example the logic in a certain POU and the compiled code in the
POU, the system will respond with a warning if you start up the simulator.

Figure 6-60

6-86 RSWB rev 1.2

6.1.10.1.1 Starting the Simulator

The Simulator can be started from the Link Architecture window using the symbol or from the
debug menu.

Figure 6-61

If the project is not built, the system will perform this build before going in simulation mode.

Be sure the option Code for Simulation has been selected in the Resource Properties before you build
the project. (The Resource Properties can be reached by selecting the header of the Resource
Workspace window and active the right-mouse button)

Figure 6-62

RSWB rev 1.2 6-87

Once the simulator has been started in the Task Bar of your screen a few foreground processes will
appear.

6-88 RSWB rev 1.2

6.1.10.1.2 Simulating the Application

Once the Simulator has been started, the application logic can be tested by opening the POUs. You
can change the value of variables (local, global, I/O) from the sheet itself. I/O signals can also be
changed by using the I/O panel simulation window in your Task bar.
In the figure below the following information can be found:
a. In the sheets values are displayed in Colors. Red for FALSE and blue for TRUE.
If you want to change the value of a variable double click on this variable. The
result will be a Pop-up window in where you can write the new value.
b. If values are not- or partially displayed you have 2 options to fix that.
1. Make the blocks in the editor broader, therefore you should stop
the simulator
2. Use the menu option-> customize. In the customize window you
can change the font, size, colors, etc.
c. This button can be used for stopping the simulation
d. This button is for switching the visibility of values on/off (show/hide)
e. Button to clear the output window

Figure 6-63

RSWB rev 1.2 6-89

Simulating the I/O can also be done by using the I/O Panel Simulation
This window will give you all the I/O cards in the resource which is currently simulated.
In the next figure the following information can be found:
a. The I/O cards of the selected SCS.
b. Values can be changed by double clicking on the appropriate value
c. Option to show the tree bar in the window (where the I/O cards are displayed)
d. To display (or not) the tagnames per channel
e. To display the value as Hexadecimal or Decimal
f. The precision of the presented value (exponent/decimals)

Figure 6-64

6-90 RSWB rev 1.2

6.1.10.2 Debug
While in Simulation mode, the security state of unlocked resources and resources having no access
control, switches to read-only mode. The security state of unlocked POUs and POUs having no access
control also switches to read-only mode. Locked resources and locked POUs remain locked.

RSWB rev 1.2 6-91

 This page intentionally left blank.

6-92 RSWB rev 1.2